3D Beamforming (FDD) Feature Parameter Description: Issue Date
3D Beamforming (FDD) Feature Parameter Description: Issue Date
Issue Draft A
Date 2020-12-29
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: https://www.huawei.com
Email: support@huawei.com
Contents
1 Change History.........................................................................................................................1
1.1 eRAN17.1 Draft A (2020-12-29)........................................................................................................................................ 1
3 Overview....................................................................................................................................4
4 SSB...............................................................................................................................................5
4.1 Principles.................................................................................................................................................................................... 5
4.2 Network Analysis..................................................................................................................................................................... 5
4.2.1 Benefits.................................................................................................................................................................................... 5
4.2.2 Impacts.................................................................................................................................................................................... 6
4.3 Requirements............................................................................................................................................................................ 8
4.3.1 Licenses................................................................................................................................................................................... 8
4.3.2 Software.................................................................................................................................................................................. 9
4.3.3 Hardware.............................................................................................................................................................................. 10
4.3.4 Networking.......................................................................................................................................................................... 11
4.4 Operation and Maintenance............................................................................................................................................. 11
4.4.1 Data Configuration........................................................................................................................................................... 11
4.4.1.1 Data Preparation............................................................................................................................................................ 11
4.4.1.2 Using MML Commands............................................................................................................................................... 13
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 18
4.4.2 Activation Verification..................................................................................................................................................... 19
4.4.3 Network Monitoring......................................................................................................................................................... 19
5 DDB........................................................................................................................................... 20
5.1 Principles.................................................................................................................................................................................. 20
5.2 Network Analysis.................................................................................................................................................................. 21
5.2.1 Benefits................................................................................................................................................................................. 21
5.2.2 Impacts.................................................................................................................................................................................. 22
5.3 Requirements......................................................................................................................................................................... 24
5.3.1 Licenses................................................................................................................................................................................. 24
5.3.2 Software................................................................................................................................................................................25
5.3.3 Hardware.............................................................................................................................................................................. 27
5.3.4 Others.................................................................................................................................................................................... 28
5.4 Operation and Maintenance............................................................................................................................................. 28
5.4.1 Data Configuration........................................................................................................................................................... 28
5.4.1.1 Data Preparation............................................................................................................................................................ 28
5.4.1.2 Using MML Commands............................................................................................................................................... 31
5.4.1.3 Using the MAE-Deployment...................................................................................................................................... 34
5.4.2 Activation Verification..................................................................................................................................................... 34
5.4.3 Network Monitoring......................................................................................................................................................... 34
6 Parameters.............................................................................................................................. 35
7 Counters.................................................................................................................................. 36
8 Glossary................................................................................................................................... 37
9 Reference Documents...........................................................................................................38
1 Change History
Editorial Changes
Revised MML command examples. For details, see 5.4.1.2 Using MML
Commands.
This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve the desired gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this
document apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.
5 DDB
3 Overview
The amount of traffic in densely populated urban areas has been increasing.
Capacity requirements over the next few years are predicted to increase three to
six fold. This expected demand for increased capacity means that the spectrum
resources in the 1.8 GHz to 2.6 GHz bands are likely to become more valuable
than ever and they should be fully utilized.
This feature uses active antenna units (AAUs) or remote radio units (RRUs) to
provide Static Shared Beam (SSB) and Dynamic Dedicated Beam (DDB) functions.
If multiple carriers are configured on the same AAU or RRU, it is recommended
that they all use the same function: SSB or DDB.
● SSB generates two beams on the horizontal plane to serve two cells at each
8T8R AAU, as shown in Figure 3-1.
● DDB sets up an 8T8R cell to provide dedicated traffic beams for multiple UEs
simultaneously, as shown in Figure 3-2.
4 SSB
4.1 Principles
SSB splits one cell on an AAU into two 2T2R or 4T4R cells on the horizontal plane.
The two cells operate on the same frequency. SSB expands capacity at hotspots. It
is an option for operators that require more capacity but do not have additional
frequencies available.
4.2.2 Impacts
Network Impacts
● User-perceived downlink throughput
In 2T2R cells served by an eNodeB with a 3-sector configuration, using SSB
may decrease user-perceived throughput during idle periods (for example,
when the PRB usage is less than 20%) or when the left- and right-cell loads
are imbalanced.
● Other network performance indicators
For an eNodeB with a 2T2R 3-sector configuration, using SSB increases the
number of cells but decreases the SINR. Using SSB may result in a lower
handover success rate, more RRC connection reestablishments, and a higher
service drop rate than the performance indicators before SSB is used.
Function Impacts
Function Function Switch Reference Description
Name
4.3 Requirements
4.3.1 Licenses
To maximize SSB (generating 4T4R cells on the horizontal plane) performance, the
licenses for DL 4x2 MIMO and UL 4-Antenna Receive Diversity are required.
Feature ID Feature Name Model Sales Unit
To maximize SSB (generating 2T2R cells on the horizontal plane) performance, the
license for DL 2x2 MIMO is required.
4.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
Prerequisite Functions
None
4.3.3 Hardware
Boards
The BBPs must be UBBPe4/UBBPe6/UBBPg. When passive ports are used for 4T6S
reconstruction from a 3-sector eNodeB equipped with combined 2T2R or 4T4R
RRUs, the left and right cells must be bound to a UBBPe4, UBBPe6, or UBBPg
board. Otherwise, channel calibration cannot be performed.
RF Modules
SSB requires a specific model of AAUs working in the 1.8 GHz, 2.1 GHz, or 2.6 GHz
band.
AAUs of this specific model in the 1.8 GHz band contain both radio and antenna
modules. Power supplies must be directly connected to the AAUs, and those AAUs
must be connected to the BBUs of the eNodeBs through CPRI optical cables. The
AAUs in other bands contain only antenna modules. They must be connected to
external radio units. These AAUs supply power to the radio units, which are then
connected to BBUs through CPRI optical cables. AISG cables do not need to be
connected to the AAUs.
Typically, each eNodeB requires three AAUs, each of which will serve a pair of cells
for SSB. Therefore, each eNodeB will serve a total of six cells.
When AAUs of that specific model are used, the power per channel for each pair
of cells must be configured to meet the following requirements:
● For AAUs in the 1.8 GHz band, the power configuration for a 20 MHz cell is
with CRS power set at 16.9 dBm, PA at –3, and PB at 1.
● For AAUs in the 2.1 GHz or 2.6 GHz band, the power configuration for a 20
MHz cell is with CRS power set at 18.2 dBm, PA at –3, and PB at 1.
4.3.4 Networking
For each eNodeB, three cells will be replaced with six cells corresponding to the
beams on the horizontal plane, with each cell covering a 60-degree arc, as
illustrated in Figure 4-1.
RRU Slot No. SECTOREQM.RRUSN If active ports on the AAU are used
for this function, set this parameter to
the slot number of the AAU.
NOTE
The serial number of each RET antenna can be queried by running the SCN ALD
command.
● The following is an example of MML commands for SSB at passive ports on
an AAU that is used to transform a 3-sector eNodeB with 2T2R cells into a
2T6S eNodeB. On 8T8R AAUs, passive ports are always used together with
active ports. Therefore, by default, the cabinet, subrack, and slot numbers of
the RF modules that control RET antennas and RVDs are set to the cabinet,
subrack, and slot numbers of the AAUs that provide active ports.
//Removing original cell configurations
DEA CELL: LocalCellId=x;
RMV EUCELLSECTOREQM: LocalCellId=x, SecctorEqmId=0;
//Removing all the neighbor relationships with a cell before removing that cell (Otherwise, the cell
will fail to be removed.)
RMV CELL: LocalCellId=x;
RMV SECTOREQM: SECTOREQMID=0;
RMV SECTOR: SECTORID=0;
//Adding back the following information as RMV CELL has been executed
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=0, HSN=2, HPN=0;
//Adding AAUs
ADD RRU: CN=0, SRN=61, SN=0, TP=TRUNK, RCN=0, PS=0, RT=MRRU, RS=LO, RXNUM=2, TXNUM=2,
MNTMODE=NORMAL, RFDCPWROFFALMDETECTSW=OFF, RFTXSIGNDETECTSW=OFF;
ADD RRU: CN=0, SRN=62, SN=0, TP=TRUNK, RCN=0, PS=1, RT=MRRU, RS=LO, RXNUM=2, TXNUM=2,
MNTMODE=NORMAL, RFDCPWROFFALMDETECTSW=OFF, RFTXSIGNDETECTSW=OFF;
//Adding sectors
ADD
SECTOR:SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=2,ANT1CN=0,ANT1S
RN=61,ANT1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=61,ANT2SN=0,ANT2N=R0B,CREATESECTOREQM
=FALSE;
ADD SECTOR:
SECTORID=1,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=2,ANT1CN=0,ANT1SRN=62,A
NT1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=62,ANT2SN=0,ANT2N=R0B,CREATESECTOREQM=FALSE;
//Adding sector equipment
ADD SECTOREQM: SECTOREQMID=0, SECTORID=0, ANTNUM=2, ANT1CN=0, ANT1SRN=61,
ANT1SN=0, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=61, ANT2SN=0,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=1, SECTORID=1, ANTNUM=2, ANT1CN=0, ANT1SRN=62,
ANT1SN=0, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=62, ANT2SN=0,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
//Adding cells
ADD CELL: LocalCellId=x1, CellName="cell0", FreqBand=7, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=3040,
UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=61, PhyCellId=61,
FddTddInd=CELL_FDD, EuCellStandbyMode=ACTIVE, RootSequenceIdx=0,
CustomizedBandWidthCfgInd=NOT_CFG, WorkMode=UL_DL, UePowerMaxCfgInd=NOT_CFG,
MultiRruCellFlag=BOOLEAN_FALSE, CrsPortNum=CRS_PORT_2, TxRxMode=2T2R;
ADD CELL: LocalCellId=x2, CellName="cell1", FreqBand=7, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=3040,
UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=62, PhyCellId=62,
FddTddInd=CELL_FDD, EuCellStandbyMode=ACTIVE, RootSequenceIdx=0,
CustomizedBandWidthCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG,
MultiRruCellFlag=BOOLEAN_FALSE, CrsPortNum=CRS_PORT_2, TxRxMode=2T2R;
//Binding the sector equipment to the cells
ADD EUCELLSECTOREQM: LOCALCELLID=x1, SECTOREQMID=0;
ADD EUCELLSECTOREQM: LOCALCELLID=x2, SECTOREQMID=1;
//Configuring the PDSCH
MOD PDSCHCFG: LocalCellId=x1, ReferenceSignalPwr=182, Pb=1;
MOD CELLDLPCPDSCHPA:LOCALCELLID=x1,PAPCOFF=DB_3_P_A;
MOD PDSCHCFG: LocalCellId=x2, ReferenceSignalPwr=182, Pb=1;
MOD CELLDLPCPDSCHPA:LOCALCELLID=x2,PAPCOFF=DB_3_P_A;
//Adding RET antennas (Set SERIALNO to the scanned serial numbers.)
MOD ANTENNAPORT: CN=0, SRN=60, SN=0, PN=R0A, PWRSWITCH=ON;
ADD RET: DEVICENO=0, CTRLCN=0, CTRLSRN=60, CTRLSN=0, RETTYPE=SINGLE_RET,
SCENARIO=DAISY_CHAIN, VENDORCODE="HW", SERIALNO="M2194G30001B01Ty2";
ADD RET: DEVICENO=1, CTRLCN=0, CTRLSRN=60, CTRLSN=0, RETTYPE=SINGLE_RET,
SCENARIO=DAISY_CHAIN, VENDORCODE="HW", SERIALNO="M2194G30001B01Ty2";
//Setting an identical electrical downtilt angle for the RET antennas
MOD RETSUBUNIT: DEVICENO=0, SUBUNITNO=1, TILT=60;
MOD RETSUBUNIT: DEVICENO=1, SUBUNITNO=1, TILT=60;
//Setting AntennaForm to Multi-beam antenna
MOD RET: DEVICENO=0, CTRLCN=0, CTRLSRN=60, CTRLSN=0,
ANTENNAFORM=MULTIBEAM_ANTENNA;
MOD RET: DEVICENO=1, CTRLCN=0, CTRLSRN=60, CTRLSN=0,
ANTENNAFORM=MULTIBEAM_ANTENNA;
//Binding each RRU (only one port is required) to an RET antenna
MOD RETSUBUNIT: DEVICENO=0, SUBUNITNO=1, CONNCN1=0, CONNSRN1=61, CONNSN1=0,
CONNPN1=R0A, CONNCN2=0, CONNSRN2=62, CONNSN2=0, CONNPN2=R0A;
//Adding an RVD MO
ADD RVD: DEVICENO=2, CTRLCN=0, CTRLSRN=60, CTRLSN=0, SUBUNITNUM=1,
SCENARIO=DAISY_CHAIN, VENDORCODE="HW", SERIALNO="M2194G30001B01SDA";
//Binding the RRUs to the RVD
MOD RVDSUBUNIT: DEVICENO=2, SUBUNITNO=1, CONNCN1=0, CONNSRN1=61, CONNSN1=0,
CONNPN1=R0A, CONNCN2=0, CONNSRN2=62, CONNSN2=0, CONNPN2=R0A;
//Setting the software-defined antenna mode to be 4T4R with two beams
MOD RVDINFO: OPMODE=DEVICENO, DEVICENO=2, SDAMODE=BRA_4T4R_2BEAMS;
ADD CELLOP: LocalCellId=x1, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
ADD CELLOP: LocalCellId=x2, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
//Modifying cell downlink algorithm settings
MOD CELLDLSCHALGO: LocalCellId=x1, MaxMimoRankPara=SW_MAX_SM_RANK_2;
MOD CELLDLSCHALGO: LocalCellId=x2, MaxMimoRankPara=SW_MAX_SM_RANK_2;
//Activating the cells
ACT CELL: LocalCellId=x1;
ACT CELL: LocalCellId=x2;
the RF modules that control RET antennas and RVDs are set to the cabinet,
subrack, and slot numbers of the AAUs that provide active ports.
//Removing original cell configurations
DEA CELL: LocalCellId=x;
RMV EUCELLSECTOREQM: LocalCellId=x, SecctorEqmId=0;
//Removing all the neighbor relationships with a cell before removing that cell (Otherwise, the cell
will fail to be removed.)
RMV CELL: LocalCellId=x;
RMV SECTOREQM: SECTOREQMID=0;
RMV SECTOR: SECTORID=0;
//Adding back the following information as RMV CELL has been executed
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=0, HSN=2, HPN=0;
//Adding an AAU
ADD RRU: CN=0, SRN=61, SN=0, TP=TRUNK, RCN=0, PS=0, RT=MRRU, RS=LO, RXNUM=4, TXNUM=4,
MNTMODE=NORMAL, RFDCPWROFFALMDETECTSW=OFF, RFTXSIGNDETECTSW=OFF;
//Adding a sector
ADD
SECTOR:SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=4,ANT1CN=0,ANT1S
RN=61,ANT1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=61,ANT2SN=0,ANT2N=R0C,ANT3CN=0,ANT3SR
N=61,ANT3SN=0,ANT3N=R0D,ANT4CN=0,ANT4SRN=61,ANT4SN=0,ANT4N=R0B,CREATESECTOREQM=
FALSE;
//Adding sector equipment
ADD SECTOREQM: SECTOREQMID=0, SECTORID=0, ANTNUM=2, ANT1CN=0, ANT1SRN=61,
ANT1SN=0, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=61, ANT2SN=0,
ANT2N=R0C, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=1, SECTORID=0, ANTNUM=2, ANT1CN=0, ANT1SRN=61,
ANT1SN=0, ANT1N=R0D, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=61, ANT2SN=0,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
//Adding cells
ADD CELL: LocalCellId=x1, CellName="cell0", FreqBand=7, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=3040,
UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=61, PhyCellId=61,
FddTddInd=CELL_FDD, EuCellStandbyMode=ACTIVE, RootSequenceIdx=0,
CustomizedBandWidthCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG,
MultiRruCellFlag=BOOLEAN_FALSE, CrsPortNum=CRS_PORT_2, TxRxMode=2T2R;
ADD CELL: LocalCellId=x2, CellName="cell1", FreqBand=7, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=3040,
UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=62, PhyCellId=62,
FddTddInd=CELL_FDD, EuCellStandbyMode=ACTIVE, RootSequenceIdx=0,
CustomizedBandWidthCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG,
MultiRruCellFlag=BOOLEAN_FALSE, CrsPortNum=CRS_PORT_2, TxRxMode=2T2R;
//Binding the sector equipment to the cells
ADD EUCELLSECTOREQM: LOCALCELLID=x1, SECTOREQMID=0;
ADD EUCELLSECTOREQM: LOCALCELLID=x2, SECTOREQMID=1;
//Configuring the PDSCH
MOD PDSCHCFG: LocalCellId=x1, ReferenceSignalPwr=182, Pb=1;
MOD CELLDLPCPDSCHPA:LOCALCELLID=x1,PAPCOFF=DB_3_P_A;
MOD PDSCHCFG: LocalCellId=x2, ReferenceSignalPwr=182, Pb=1;
MOD CELLDLPCPDSCHPA:LOCALCELLID=x2,PAPCOFF=DB_3_P_A;
//Adding RET antennas (Set SERIALNO to the scanned serial numbers.)
MOD ANTENNAPORT: CN=0, SRN=60, SN=0, PN=R0A, PWRSWITCH=ON;
ADD RET: DEVICENO=0, CTRLCN=0, CTRLSRN=60, CTRLSN=0, RETTYPE=SINGLE_RET,
SCENARIO=DAISY_CHAIN, VENDORCODE="HW", SERIALNO="M2194G30001B01Ty2";
ADD RET: DEVICENO=1, CTRLCN=0, CTRLSRN=60, CTRLSN=0, RETTYPE=SINGLE_RET,
SCENARIO=DAISY_CHAIN, VENDORCODE="HW", SERIALNO="M2194G30001B01Ty2";
//Setting an identical electrical downtilt angle for the RET antennas
MOD RETSUBUNIT: DEVICENO=0, SUBUNITNO=1, TILT=60;
MOD RETSUBUNIT: DEVICENO=1, SUBUNITNO=1, TILT=60;
//Setting AntennaForm to Multi-beam antenna
MOD RET: DEVICENO=0, CTRLCN=0, CTRLSRN=60, CTRLSN=0,
ANTENNAFORM=MULTIBEAM_ANTENNA;
MOD RET: DEVICENO=1, CTRLCN=0, CTRLSRN=60, CTRLSN=0,
ANTENNAFORM=MULTIBEAM_ANTENNA;
//Binding the RRU to the RET antennas
MOD RETSUBUNIT: DEVICENO=0, SUBUNITNO=1, CONNCN1=0, CONNSRN1=61, CONNSN1=0,
CONNPN1=R0A, CONNCN2=0, CONNSRN2=61, CONNSN2=0, CONNPN2=R0B;
//Adding an RVD MO
ADD RVD: DEVICENO=2, CTRLCN=0, CTRLSRN=60, CTRLSN=0, SUBUNITNUM=1,
SCENARIO=DAISY_CHAIN, VENDORCODE="HW", SERIALNO="M2194G30001B01SDA";
//Binding the RRU to the RVD
MOD RVDSUBUNIT: DEVICENO=2, SUBUNITNO=1, CONNCN1=0, CONNSRN1=61, CONNSN1=0,
NOTE
When passive ports are used for 4T6S, active- and passive-port channel calibration can
be started only if calibration is enabled for both of the cells that are generated using
SSB.
When passive ports are used for 4T6S reconstruction from a 3-sector eNodeB
equipped with combined 2T2R or 4T4R RRUs, the left and right cells must be bound to
a UBBPe4, UBBPe6, or UBBPg board. Otherwise, channel calibration cannot be
performed.
Figure 4-2 Example scatter chart of PRB usage and traffic volume
5 DDB
5.1 Principles
DDB generates one or more 8T8R cells on an AAU or RRU. The cell bandwidth is
at least 5 MHz. In the uplink, 8-antenna receive diversity is available for all UEs in
the cells. In the downlink, the available functions depend on UE capabilities:
● For UEs not configured with TM9:
– If two CRS ports are configured, downlink 2x2 or 4x2 MIMO is available.
– If four CRS ports are configured, downlink 4x2 or 4x4 MIMO is available.
● For UEs configured with TM9 and capable of 8- or 4-port TM9, the available
functions vary depending on the TM9Switch option of the
CellAlgoSwitch.EnhMIMOSwitch parameter. If this option is deselected, the
available functions are the same as those for UEs not configured with TM9. If
this option is selected, the available functions are as follows:
– If the 8T4PortTM9EnhanceSwitch option of the
CellAlgoSwitch.EnhMIMOSwitch parameter is selected and one of the
following conditions is met, CSI-RSs are sent from eight ports to 8-port
TM9-capable UEs and from four ports to 4-port TM9-capable UEs. In
addition, single-user MIMO (SU-MIMO) using 8T in TM9 is available.
Otherwise, the available functions are the same as those for UEs not
configured with TM9.
▪ The modulation and coding scheme (MCS) index used for each of
the UEs is larger than the value of the
CellMimoParaCfg.MuPairingMcsThldForTm9 parameter.
5.2.1 Benefits
System capacity increases considerably in urban areas where there is contiguous
coverage. In each 2T2R cell served by an eNodeB with a 3-sector configuration,
using DDB increases the average downlink cell traffic volume by 70%–120% and
increases the average downlink UE throughput also by 40%–70%. These figures
assume that there is a 100% penetration rate of UEs capable of 8-port TM9 and
that LOFD-001003 DL 4x2 MIMO and LOFD-001005 UL 4-Antenna Receive
Diversity are both enabled. In a cell with only TM4 enabled, using DDB increases
the average downlink cell throughput by 20%–40%.
The gains provided by DDB for 4-port TM9-capable UEs are only 90% of the gains
for 8-port TM9-capable UEs, as the CSI feedback capabilities of 4-port TM9-
capable UEs are lower than those of 8-port TM9-capable UEs.
The benefits are most noticeable when specific conditions are all met. When any
of these conditions is not fulfilled, this function offers a smaller amount of gains
than expected but does not have a negative impact. The conditions are as follows:
● The 8T8R cells provide contiguous coverage.
● UEs are distributed evenly within the cells.
● There is a high percentage of large-packet services in the cells.
● Cell channel quality is stable.
This function is suitable for high-traffic scenarios in urban areas. It is
recommended when the penetration rate of TM9-capable UEs is high (for
example, over 50%) or when SSB is not suitable for use. You can use the
L.Traffic.User.TM9Capability.Avg counter as a reference for the TM9-capable UE
penetration rate.
Uplink 8-antenna receive diversity in 8T8R cells offers the following benefits over
uplink 2-antenna receive diversity.
The average uplink UE throughput For a single UE, the farther away it is
increases by 10% to 70%. from the cell center, the higher the
gains are.
For a cell, the more UEs far away from
the eNodeB there are, the higher the
gains.
5.2.2 Impacts
Network Impacts
Downlink SU-MIMO or MU-MIMO in TM9 takes effect when the DDB function is
used. The overhead for precoding matrix indication (PMI) reporting increases,
causing the following to occur:
● Interference on the physical uplink control channel (PUCCH) increases.
● Interference on the physical uplink shared channel (PUSCH) increases.
● The residual block error rate (RBLER) of the PUSCH slightly increases,
resulting in a slight increase in the packet loss rate for voice users.
● CPU usage increases. The service drop rate slightly rises when CPU usage is
high.
● TM9-incapable UEs experience performance deterioration because of periodic
CSI-RS transmission in the cell when TM9 takes effect. The level of the
deterioration depends on the TM9-capable UE penetration rate and the CSI-
RS period.
In addition, as downlink MU-MIMO in TM9 takes effect, more PDCCH symbols are
used in the downlink. As a result, the failure rate of uplink grant assignments over
the PDCCH increases, and the average uplink UE throughput may decrease by at
most 5%.
Function Impacts
Function Function Switch Reference Description
Name
5.3 Requirements
5.3.1 Licenses
This function requires the license for 3D Beamforming. To maximize the
performance of this function, the other licenses in the following table are also
recommended.
Feature ID Feature Name Model Sales Unit
5.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
Prerequisite Functions
None
GSM and LTE Zero GLZeroBufferZoneSwitch option of GSM and LTE Zero
Bufferzone the Bufferzone
CellAlgoSwitch.DynSpectrumShar-
eSwitch parameter
UL Refarming Zero AvoidUtranInterfSwitch option of UL Refarming Zero
Bufferzone the Bufferzone
CellAlgoSwitch.AvoidInterfSwitch
parameter
5.3.3 Hardware
Base Station Models
3900 and 5900 series base stations are compatible with this function.
Boards
The BBPs must be UBBPe4/UBBPe6/UBBPg.
RF Modules
DDB requires AAU5972 units, 2.1 GHz or 2.6 GHz 4T4R RRUs, or another specific
model of AAUs. The two 4T4R RRUs in each pair must be of the same model.
AAU5972 units and AAUs of that specific model in the 1.8 GHz band contain both
radio and antenna modules. Power supplies must be directly connected to the
AAUs, and those AAUs must be connected to the BBUs of the eNodeBs through
CPRI optical cables. The AAUs in other bands contain only antenna modules. They
must be connected to external radio units. These AAUs supply power to the radio
units, which are then connected to BBUs through CPRI optical cables. For details
about how to install AAU5972 units, see AAU5972 Installation Guide.
When AAU5972 units, 2.1 GHz or 2.6 GHz 4T4R RRUs, or AAUs of that specific
model are used, the maximum power per channel must be configured to meet the
following requirements:
● For AAU5972 units in the 1.8 GHz band, the power must not exceed 47.7
dBm. (The maximum power configuration is 4 x 60 W, for example, with CRS
power set at 19.9 dBm, PA at –3, and PB at 1 for a 20 MHz cell.)
● For AAU5972 units in other bands, the power must not exceed 49 dBm. (The
maximum power configuration is 4 x 80 W, for example, with CRS power set
at 21.2 dBm, PA at –3, and PB at 1 for a 20 MHz cell.)
5.3.4 Others
DDB requires 8-port TM9 UEs or 4-port TM9 UEs.
//(Optional) If the cabinet number, subrack number, and slot number of the AAU are different from those
of the original RRU, changing the following information and configuring the AAU
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=0, HSN=2, HPN=0;
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=0, PS=0, RT=AIRU, RS=LO, RXNUM=8, TXNUM=8,
MNTMODE=NORMAL, RFDCPWROFFALMDETECTSW=OFF;
//(Optional) If the cabinet number, subrack number, and slot number of the AAU are the same as those of
the original RRU, changing the RRU type to AIRU
MOD RRU: CN=0, SRN=60, SN=0, RT=AIRU;
//Adding an RVD MO
ADD RVD: DEVICENO=2, CTRLCN=0, CTRLSRN=60, CTRLSN=0, SUBUNITNUM=1, SCENARIO=DAISY_CHAIN,
VENDORCODE="HW", SERIALNO="M2194G30001B01SDA";
//Binding the RRU to the RVD
MOD RVDSUBUNIT: DEVICENO=2, SUBUNITNO=1, CONNCN1=0, CONNSRN1=60, CONNSN1=0,
CONNPN1=R0A, CONNCN2=0, CONNSRN2=60, CONNSN2=0, CONNPN2=R0B;
//Setting SDAMODE to BRA_8T8R_1BEAM
MOD RVDINFO: OPMODE=DEVICENO, DEVICENO=2, SDAMODE=BRA_8T8R_1BEAM;
ADD CELLOP: LocalCellId=x, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
//Configuring the PDSCH
MOD PDSCHCFG: LocalCellId=x, ReferenceSignalPwr=199, Pb=1;
MOD CELLDLPCPDSCHPA:LOCALCELLID=x, PAPCOFF=DB_3_P_A;
NOTE
The serial number of each RET antenna can be queried by running the SCN ALD command.
//Adding RET antennas (Set SERIALNO to the scanned serial numbers. Skip this step if RET antennas have
been added for the cells served by the active ports on the AAU.)
MOD ANTENNAPORT: CN=0, SRN=60, SN=0, PN=R0A, PWRSWITCH=ON;
ADD RET: DEVICENO=0, CTRLCN=0, CTRLSRN=60, CTRLSN=0, RETTYPE=SINGLE_RET,
SCENARIO=DAISY_CHAIN, VENDORCODE="HW", SERIALNO="M2194G30001B01Ty2";
//Adding the relationships between the RRUs and the RET antennas (Do not set the TILT parameter if it has
been specified for the cells served by the active ports on the AAU.)
MOD RETSUBUNIT: DEVICENO=0, SUBUNITNO=1, CONNCN1=0, CONNSRN1=61, CONNSN1=0,
CONNPN1=R0A, CONNCN2=0, CONNSRN2=62, CONNSN2=0, CONNPN2=R0A, TILT=60;
//Adding an RVD MO
ADD RVD: DEVICENO=2, CTRLCN=0, CTRLSRN=60, CTRLSN=0, SUBUNITNUM=1, SCENARIO=DAISY_CHAIN,
VENDORCODE="HW", SERIALNO="M2194G30001B01SDA";
//Binding the RRU to the RVD
MOD RVDSUBUNIT: DEVICENO=2, SUBUNITNO=1, CONNCN1=0, CONNSRN1=61, CONNSN1=0,
CONNPN1=R0A, CONNCN2=0, CONNSRN2=62, CONNSN2=0, CONNPN2=R0A;
//Setting SDAMODE to BRA_8T8R_1BEAM
MOD RVDINFO: OPMODE=DEVICENO, DEVICENO=2, SDAMODE=BRA_8T8R_1BEAM;
ADD CELLOP: LocalCellId=x, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
//Activating the cell (Cells served by the passive ports on an AAU can be activated only when the
relationships between the RRUs and the RET antennas have been added.)
ACT CELL: LOCALCELLID=x;
1526739778 L.ChMeas.MUBF.
2ndLayer.PairPRB.Succ
1526739779 L.ChMeas.MUBF.
3rdLayer.PairPRB.Succ
1526739780 L.ChMeas.MUBF.
4thLayer.PairPRB.Succ
6 Parameters
You can find the EXCEL files of parameter reference and used reserved parameter list for
the software version used on the live network from the product documentation delivered
with that version.
Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, LOFD-001016 or
TDLOFD-001016.
Step 3 Click OK. All parameters related to the feature are displayed.
----End
Step 1 Open the EXCEL file of the used reserved parameter list.
Step 2 On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT
columns to locate the reserved parameter, which may be only a bit of a parameter.
View its information, including the meaning, values, impacts, and product version
in which it is activated for use.
----End
7 Counters
The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● eNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.
----End
8 Glossary
9 Reference Documents