Documente Academic
Documente Profesional
Documente Cultură
Issue 01
Date 2019-06-06
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: http://www.huawei.com
Email: support@huawei.com
Contents
1 Change History.............................................................................................................................. 1
1.1 eRAN15.1 01 (2019-06-06)............................................................................................................................................1
1.2 eRAN15.1 Draft C (2019-05-10)....................................................................................................................................1
1.3 eRAN15.1 Draft B (2019-03-18)....................................................................................................................................2
1.4 eRAN15.1 Draft A (2019-01-05)................................................................................................................................... 2
3 Overview......................................................................................................................................... 6
4 SSB....................................................................................................................................................7
4.1 Principles........................................................................................................................................................................ 7
4.2 Network Analysis........................................................................................................................................................... 7
4.2.1 Benefits........................................................................................................................................................................ 7
4.2.2 Impacts.........................................................................................................................................................................8
4.3 Requirements.................................................................................................................................................................. 9
4.3.1 Licenses....................................................................................................................................................................... 9
4.3.2 Software.....................................................................................................................................................................10
4.3.3 Hardware....................................................................................................................................................................11
4.3.4 Networking................................................................................................................................................................ 11
4.4 Operation and Maintenance..........................................................................................................................................12
4.4.1 Data Configuration.................................................................................................................................................... 12
4.4.1.1 Data Preparation..................................................................................................................................................... 12
4.4.1.2 Using MML Commands......................................................................................................................................... 13
4.4.1.3 Using the CME....................................................................................................................................................... 19
4.4.2 Activation Verification.............................................................................................................................................. 19
4.4.3 Network Monitoring.................................................................................................................................................. 19
5 DDB................................................................................................................................................21
5.1 Principles...................................................................................................................................................................... 21
5.2 Network Analysis......................................................................................................................................................... 22
5.2.1 Benefits...................................................................................................................................................................... 22
5.2.2 Impacts.......................................................................................................................................................................23
5.3 Requirements................................................................................................................................................................ 25
5.3.1 Licenses..................................................................................................................................................................... 25
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......................................................................................................................................... 30
5.4.1.3 Using the CME....................................................................................................................................................... 33
5.4.2 Activation Verification.............................................................................................................................................. 33
5.4.3 Network Monitoring.................................................................................................................................................. 33
6 Parameters..................................................................................................................................... 34
7 Counters........................................................................................................................................ 35
8 Glossary......................................................................................................................................... 36
9 Reference Documents................................................................................................................. 37
1 Change History
This chapter describes changes not included in the "Parameters", "Counters", "Glossary", and
"Reference Documents" chapters. These changes include:
l Technical changes
Changes in functions and their corresponding parameters
l Editorial changes
Improvements or revisions to the documentation
Editorial Changes
Revised descriptions in this document.
Technical Changes
None
Editorial Changes
Revised descriptions in 5.1 Principles.
Technical Changes
Change Description Parameter Change Base Station
Model
Editorial Changes
None
Technical Changes
Change Description Parameter Change Base Station
Model
Added handling of 4-port TM9- Added the option 3900 and 5900
capable UEs in 8T scenarios. For 8T4PortTM9EnhanceSwitch to series base
details, see 5.1 Principles. the parameter stations
CellAlgoSwitch.EnhMIMOSwitc
h.
Editorial Changes
l Revised descriptions in this document.
l Revised the MML command examples. For details, see 4.4.1.2 Using MML Commands
and 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.
l SSB generates two beams on the horizontal plane to serve two cells at each 8T8R AAU,
as shown in Figure 3-1.
l 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.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 SSB increases
downlink cell traffic volume. When LOFD-001001 DL 2x2 MIMO, LOFD-001003 DL 4x2
MIMO, and LOFD-001005 UL 4-Antenna Receive Diversity are all enabled, the capacity can
be increased by 50% to 70% for reconstruction into 2T6S or by 70% to 100% for
reconstruction into 4T6S.
The increases are closely related to cell loads and whether the cells using SSB provide
contiguous coverage. The gains of SSB are higher if the cell load is higher, cell coverage is
more contiguous, and the percentage of UEs in each cell is closer to 50%.
It is recommended that SSB be used when specific conditions are all met, whereas DDB be
used when any of these conditions is not fulfilled. When any of these conditions is not
fulfilled, SSB offers a smaller amount of gains than expected but does not have a negative
impact. The conditions are as follows:
l The busy-hour downlink PRB usage is high (for example, above 70%).
l The left- and right-cell loads are relatively balanced (for example, the left-to-right cell
load ratio is less than 7:3).
l The azimuth between the target sector for SSB and its adjacent sectors is large (for
example, greater than 90°) before SSB is used.
l The penetration rate of UEs that support transmission mode 9 (TM9) is low (for
example, lower than 50%).
Downlink PRB usage = L.ChMeas.PRB.DL.Used.Avg/L.ChMeas.PRB.DL.Avail x 100%
4.2.2 Impacts
Network Impacts
l 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.
l 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
UL AvoidUtranInterfS- UL Refarming
Refarming witch option of the Zero
Zero CellAlgoSwitch.Avoid Bufferzone
Bufferzone InterfSwitch
parameter
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.
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
Base Station Models
3900 and 5900 series base stations are compatible with this function.
Boards
The baseband processing units (BBPs) must be UBBPe4, UBBPg, or UBBPe6 and be
configured to work only in FDD mode. 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, UBBPg, or UBBPe6 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:
l 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.
l 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.
l Neighboring cells
Increasing the number of cells results in more neighbor relationships. If the total number
of neighbor relationships for each cell reaches the maximum allowed, the existing
neighbor relationships will require re-planning.
l Physical random access channel (PRACH) root sequence indexes and physical cell
identifiers (PCIs)
Increasing the number of cells causes PCIs to be reused more frequently. PRACH root
sequence indexes change and the distance between cells reusing PCIs decreases. As a
result, PRACH root sequence index conflicts and PCI conflicts are more likely, calling
for re-planning of PRACH root sequence indexes and PCIs.
When re-planning these configurations, operators should also consider the reference signal
(RS) power per port before and after SSB is enabled:
l If the RS power remains relatively stable, SSB has little impact on network planning.
Network planning can then focus on neighboring cells, PRACH root sequence indexes,
and PCIs.
l If the RS power decreases, network planning and optimization should consider the RS
power and the PA and PB settings.
RRU Cabinet SECTOREQM.RRUCN If active ports on the AAU are used for this
No. function, set this parameter to the cabinet
number of the AAU.
RRU Subrack SECTOREQM.RRUSR If active ports on the AAU are used for this
No. N function, set this parameter to the subrack
number of the AAU.
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.
Antenna Config SECTOREQM.ANTCF If active ports on the AAU are used for this
Mode GMODE function, set this parameter to BEAM.
If passive ports on the AAU are used for
this function, set this parameter to
ANTENNAPORT.
Beam Shape SECTOREQM.BEAMS If active ports on the AAU are used for this
HAPE function, set this parameter to
SEC_60DEG.
If passive ports on the AAU are used for
this function, this parameter does not need
to be set.
Beam Azimuth SECTOREQM.BEAMA If active ports on the AAU are used for this
Offset ZIMUTHOFFSET function, set this parameter to
LEFT_HALF or RIGHT_HALF.
If passive ports on the AAU are used for
this function, this parameter does not need
to be set.
NOTE
The serial number of each RET antenna can be queried by running the SCN ALD command.
l 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,ANT
1SRN=61,ANT1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=61,ANT2SN=0,ANT2N=R0B,CREATESECTOR
EQM=FALSE;
ADD SECTOR:
SECTORID=1,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=2,ANT1CN=0,ANT1SRN=62
,ANT1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=62,ANT2SN=0,ANT2N=R0B,CREATESECTOREQM=FAL
SE;
//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, EmergencyAreaIdCfgInd=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, EmergencyAreaIdCfgInd=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="M2194G30002A01By1";
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;
l 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 4T4R RRUs 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 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,ANT
1SRN=61,ANT1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=61,ANT2SN=0,ANT2N=R0C,ANT3CN=0,ANT
3SRN=61,ANT3SN=0,ANT3N=R0D,ANT4CN=0,ANT4SRN=61,ANT4SN=0,ANT4N=R0B,CREATESECTOR
EQM=FALSE;
l The following is an example of MML commands for SSB at passive ports on AAUs that
are used to transform a 3-sector eNodeB with integrated 4T4R RRUs into a 4T6S
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=4,
TXNUM=4, 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=4,
TXNUM=4, MNTMODE=NORMAL, RFDCPWROFFALMDETECTSW=OFF, RFTXSIGNDETECTSW=OFF;
//Adding sectors
ADD SECTOR:
SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=4,ANT1CN=0,ANT1SRN=61
,ANT1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=61,ANT2SN=0,ANT2N=R0C,ANT3CN=0,ANT3SRN=62
,ANT3SN=0,ANT3N=R0A,ANT4CN=0,ANT4SRN=62,ANT4SN=0,ANT4N=R0C,CREATESECTOREQM=FAL
SE;
ADD SECTOR:
SECTORID=1,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=4,ANT1CN=0,ANT1SRN=61
,ANT1SN=0,ANT1N=R0B,ANT2CN=0,ANT2SRN=61,ANT2SN=0,ANT2N=R0D,ANT3CN=0,ANT3SRN=62
,ANT3SN=0,ANT3N=R0B,ANT4CN=0,ANT4SRN=62,ANT4SN=0,ANT4N=R0D,CREATESECTOREQM=FAL
SE;
//Adding sector equipment
ADD SECTOREQM: SECTOREQMID=0, SECTORID=0, ANTNUM=4, ANT1CN=0, ANT1SRN=61,
ANT1SN=0, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=61, ANT2SN=0,
ANT2N=R0C, ANTTYPE2=RXTX_MODE, ANT3CN=0, ANT3SRN=62, ANT3SN=0, ANT3N=R0A,
ANTTYPE3=RXTX_MODE, ANT4CN=0, ANT4SRN=62, ANT4SN=0, ANT4N=R0C,
ANTTYPE4=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=1, SECTORID=1, ANTNUM=4, ANT1CN=0, ANT1SRN=61,
ANT1SN=0, ANT1N=R0B, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=61, ANT2SN=0,
ANT2N=R0D, ANTTYPE2=RXTX_MODE, ANT3CN=0, ANT3SRN=62, ANT3SN=0, ANT3N=R0B,
ANTTYPE3=RXTX_MODE, ANT4CN=0, ANT4SRN=62, ANT4SN=0, ANT4N=R0D,
ANTTYPE4=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, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE,
CrsPortNum=CRS_PORT_4, TxRxMode=4T4R;
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, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE,
CrsPortNum=CRS_PORT_4, TxRxMode=4T4R;
//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="M2194G30002A01By1";
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
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, UBBPg, or
UBBPe6 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:
l 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.
l 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.
n The CellCsiRsParaCfg.CsiRsSwitch parameter is set to FIXD_CFG.
n The CellCsiRsParaCfg.CsiRsSwitch parameter is set to ADAPTIVE_CFG,
and the proportion of PRBs used to schedule 8-port TM9-capable UEs and 4-
port TM9-capable UEs in the cell exceeds the value of the
CellMimoParaCfg.PrbRatioThldForTm9SuMimo parameter.
– If the 8T4PortTM9EnhanceSwitch option of the
CellAlgoSwitch.EnhMIMOSwitch parameter is deselected and one of the
following conditions is met, CSI-RSs are sent from eight ports to 8-port TM9-
capable UEs. In addition, SU-MIMO using 8T in TM9 is available. Otherwise, the
available functions are the same as those for UEs not configured with TM9.
n The CellCsiRsParaCfg.CsiRsSwitch parameter is set to FIXD_CFG.
n The CellCsiRsParaCfg.CsiRsSwitch parameter is set to ADAPTIVE_CFG,
and the proportion of PRBs used to schedule 8-port TM9-capable UEs in the
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 70%–120%. 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 10%–30%, which is the same as the gains
produced by common 4T4R 3-sector configurations.
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:
l The 8T8R cells provide contiguous coverage.
l UEs are distributed evenly within the cells.
l There is a high percentage of large-packet services in the cells.
l 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 increases For a single UE, the farther away it is from
by 10% to 70%. 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.
The recommended CRS port configuration varies depending on the TM9 penetration rate.
l If the TM9 penetration rate is low, 4-port configuration is recommended. Most UEs,
which do not support TM9, can enjoy gains in User Downlink Average Throughput.
l If the TM9 penetration rate is high, 2-port configuration is recommended. Compared
with the 4-port configuration, the 2-port configuration does not change the cell coverage.
It causes the data channel power for TM9-incapable UEs to decrease by 3 dB and causes
User Downlink Average Throughput to decrease. However, the 2-port configuration
results in an increase of about 6% in TM9-capable UE throughput.
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:
l Interference on the physical uplink control channel (PUCCH) increases.
l Interference on the physical uplink shared channel (PUSCH) increases.
l The residual block error rate (RBLER) of the PUSCH slightly increases, resulting in a
slight increase in the packet loss rate for voice users.
l CPU usage increases. The service drop rate slightly rises when CPU usage is high.
l 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 two licenses in the following table are also recommended.
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 FDD GLDynSpectrumShareSwitch option GSM and LTE FDD
dynamic spectrum of the Dynamic Spectrum
sharing (LTE FDD) CellAlgoSwitch.DynSpectrumShareS- Sharing
witch parameter
CDMA and LTE AvoidCDMAInterfSwitch option of the CDMA and LTE Zero
Zero Bufferzone CellAlgoswitch.AvoidInterfSwitch Bufferzone
(LTE FDD) parameter
GSM and LTE Zero GLZeroBufferZoneSwitch option of GSM and LTE Zero
Bufferzone the CellAlgoSwitch.DynSpectrumShar- Bufferzone
eSwitch parameter
5.3.3 Hardware
Boards
The BBPs must be UBBPe4, UBBPg, or UBBPe6 and be configured to work only in FDD
mode.
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:
l 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.)
l 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.
//Setting the following data if the cabinet number, subrack number, and slot
number of the AAU are different from those of the previous RRU
//(Skip this command if the cabinet number, subrack number, and slot number of
the AAU are the same as those of the previous RRU.)
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=0, HSN=2, HPN=0;
//Adding an AAU
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;
//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
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 used to transform a 2T2R or 4T4R cell into
an 8T8R cell at passive ports on an AAU. 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.
//Deactivating the original cell
DEA CELL: LocalCellId=x;
//Removing the original antennas
RMV RET: DEVICENO=1, CTRLCN=0, CTRLSRN=61, CTRLSN=0, RETTYPE=SINGLE_RET,
SCENARIO=DAISY_CHAIN, VENDORCODE="HW";
//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="M2194G30002A01By1";
//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
The following hyperlinked EXCEL files of parameter reference match the software version
with which this document is released.
l Node Parameter Reference: contains device and transport parameters.
l eNodeBFunction Parameter Reference: contains all parameters 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 parameter reference for the software version used on the live network
from the product documentation delivered with that version.
FAQ: How do I find the parameters related to a certain feature from parameter
reference?
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
7 Counters
The following hyperlinked EXCEL files of performance counter reference match the software
version with which this document is released.
l Node Performance Counter Summary: contains device and transport counters.
l 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.
FAQ: How do I find the counters related to a certain feature from performance counter
reference?
Step 2 On the Counter Summary(En) 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 counters related to the feature are displayed.
----End
8 Glossary
9 Reference Documents