eRAN18.1 LTE FDD Massive MIMO Solution User Guide

LTE FDD Massive MIMO Solution User Guide
Product Name Confidentiality Level

LTE INTERNAL
Product Version
Total 105 pages
eRAN18.1
LTE FDD Massive MIMO

Solution User Guide
(For Internal Use Only)
Prepared By Zhu Xiaolong, Qian Ying, Date 2020-11-16

Zheng Xiang, Li Xun,
Zhou Jiacong, and Lv
Fangfang
Reviewed By Hu Ning Date 2021-11-30
Version 18.1 Date 2021-11-30
Huawei Technologies Co., Ltd.

All rights reserved
2021-11-30 Page 1 of 105

Change History
Date Revision Chapter/Section Change Description Author

Version
2020-05-20 1.0 New Zhu Xiaolong
(00426150)
Qian Ying
(00333289)
Zheng Xiang
(00364479)
Li Xun (00398023)
Zhou Jiacong
(00380317)
2020-11-16 1.1 3 SMB Added the description of Li Xun (00398023)
downlink coverage Zheng Xiang
enhancement. (00364479)
6 Intelligent Beam Added the description of
Shaping beam number adjustment.
7 Intelligent Beam Added the description of
Scheduling precise power sharing.
2020-12-25 1.2 Added the description of Zheng Xiang
beam number adjustment 00364479
in 6 Intelligent Beam
Shaping.
2021-11-30 1.3 Added 10 Downlink Li Xun 00398023
Capacity Enhancement Lv Fangfang
Solution (eRAN18.1). 00286952
Added 11 Massive MIMO
Uplink Coverage Boost.
2021-11-30 Page 2 of 105

Contents
1 Introduction.......................................................................................................................8
1.1 Purpose and Scope......................................................................................................................... 8
1.1.1 Purpose.................................................................................................................................. 8
1.1.2 Scope..................................................................................................................................... 8
1.2 Lifecycle.......................................................................................................................................... 8
2 Overview of the FDD Massive MIMO Solution...............................................................8

2.1 Sector Split Group........................................................................................................................... 8
2.2 Sector Split Cell............................................................................................................................. 10
3 SMB..................................................................................................................................11
3.1 Basic Principles............................................................................................................................. 11
3.1.1 Definition and Principles....................................................................................................... 11
3.1.2 Benefits................................................................................................................................. 11
3.1.3 Gain Sources........................................................................................................................ 11
3.2 Application Scenarios and Site Selection.......................................................................................11
3.2.1 Application Scenarios............................................................................................................ 11
3.2.2 Site Selection Guidelines...................................................................................................... 12
3.3 Feature Activation.......................................................................................................................... 13
3.3.1 Feature Application Policies.................................................................................................. 16
3.3.2 KPI Monitoring...................................................................................................................... 16
3.3.3 Network Planning.................................................................................................................. 16
3.3.4 Hardware Requirements....................................................................................................... 20
3.3.5 Software Requirements........................................................................................................ 22
3.3.6 Engineering Requirements................................................................................................... 25
3.3.7 Parameter Settings............................................................................................................... 25
3.4 Benefits......................................................................................................................................... 27
3.4.1 Activation Verification............................................................................................................ 27
3.4.2 Gain Specifications and Evaluation Methods........................................................................27
3.4.3 Network Impact..................................................................................................................... 29
3.4.4 DT Analysis........................................................................................................................... 30
3.5 Feature Optimization..................................................................................................................... 30
3.5.1 Coverage Optimization......................................................................................................... 30
3.5.2 Load Balance Optimization................................................................................................... 31
3.5.3 Intra-eNodeB CSPC............................................................................................................. 31
4 DMB..................................................................................................................................33
4.1.2 Benefits................................................................................................................................. 37
2021-11-30 Page 3 of 105

4.2 Application Scenarios.................................................................................................................... 37

4.3.1 KPI Monitoring...................................................................................................................... 40
4.4 Benefits......................................................................................................................................... 41
4.4.3 Network Impact..................................................................................................................... 43
4.4.4 DT Analysis........................................................................................................................... 43
5 SCC Supporting TM9......................................................................................................44

5.1.2 Benefits................................................................................................................................. 45
5.3.1 KPI Monitoring...................................................................................................................... 46
5.4 Benefits......................................................................................................................................... 47
5.4.3 Network Impacts................................................................................................................... 47
5.4.4 DT Analysis........................................................................................................................... 48
6 Intelligent Beam Shaping...............................................................................................48

6.1.2 Benefits................................................................................................................................. 60
6.2.1 Pattern Adjustment and Its Enhancement.............................................................................61
6.2.2 Beam Number Adjustment.................................................................................................... 61
6.2.3 Base-Station-Level Joint Pattern Adjustment........................................................................61
2021-11-30 Page 4 of 105

6.3.1 KPI Monitoring...................................................................................................................... 66

6.4 Benefits......................................................................................................................................... 67
6.4.3 Network Impacts................................................................................................................... 68
6.4.4 DT Analysis........................................................................................................................... 68
7 Intelligent Beam Scheduling..........................................................................................69

7.1.2 Benefits................................................................................................................................. 74
7.3.1 KPI Monitoring...................................................................................................................... 77
7.3.3 Hardware.............................................................................................................................. 78
7.3.4 Software............................................................................................................................... 78
7.4 Benefits......................................................................................................................................... 79
7.4.3 Network Impacts................................................................................................................... 80
7.4.4 DT Analysis........................................................................................................................... 80
8 Precise Beamforming.....................................................................................................82
8.1.2 Benefits................................................................................................................................. 82
8.3.1 KPI Monitoring...................................................................................................................... 83
8.3.3 Hardware.............................................................................................................................. 83
8.3.4 Software............................................................................................................................... 84
2021-11-30 Page 5 of 105


8.4 Benefits......................................................................................................................................... 84
8.4.3 Network Impacts................................................................................................................... 85
8.4.4 DT Analysis........................................................................................................................... 85
9 Downlink Turbo Pilot......................................................................................................86

9.1 Principles....................................................................................................................................... 86
9.1.2 Benefits................................................................................................................................. 87
9.3.1 KPI Monitoring...................................................................................................................... 87
9.4 Benefits......................................................................................................................................... 88
9.4.3 Network Impact..................................................................................................................... 89
9.4.4 DT Analysis........................................................................................................................... 89
10 Downlink Capacity Enhancement Solution (eRAN18.1)...........................................91

10.1 Basic Principles........................................................................................................................... 91
10.1.1 Definition and Principles..................................................................................................... 91
10.1.2 Benefits............................................................................................................................... 92
10.2 Application Scenarios.................................................................................................................. 92
10.3 Feature Activation........................................................................................................................ 94
10.3.1 Feature Activation Policies and MML Command Examples................................................94
10.3.2 KPI Monitoring.................................................................................................................... 95
10.3.3 Network Planning................................................................................................................ 95
10.3.4 Hardware Requirements..................................................................................................... 95
10.3.5 Software Requirements...................................................................................................... 95
10.3.6 Engineering Requirements................................................................................................. 95
10.3.7 Parameter Settings............................................................................................................. 95
10.4 Benefits....................................................................................................................................... 95
10.4.1 Activation Verification.......................................................................................................... 95
10.4.2 Gain Specifications and Evaluation Methods......................................................................97
2021-11-30 Page 6 of 105

10.4.3 Network Impacts................................................................................................................. 97

10.4.4 DT Analysis......................................................................................................................... 97
10.5 Feature Optimization................................................................................................................... 97
11 Massive MIMO Uplink Coverage Boost......................................................................98

11.1 Basic Principles........................................................................................................................... 98
11.1.1 Definition and Principles...................................................................................................... 98
11.1.2 Benefits............................................................................................................................... 99
11.2 Application Scenarios.................................................................................................................. 99
11.3 Feature Activation........................................................................................................................ 99
11.3.1 KPI Monitoring.................................................................................................................. 100
11.3.2 Network Planning.............................................................................................................. 101
11.3.3 Hardware Requirements................................................................................................... 101
11.3.4 Software Requirements..................................................................................................... 101
11.3.5 Engineering Requirements................................................................................................101
11.3.6 Parameter Settings........................................................................................................... 102
11.4 Benefits...................................................................................................................................... 102
11.4.1 Activation Verification........................................................................................................ 102
11.4.2 Gain Specifications and Evaluation Methods....................................................................102
11.4.3 Network Impacts............................................................................................................... 102
11.4.4 DT Analysis....................................................................................................................... 103
11.5 Feature Optimization................................................................................................................. 104
12 Appendixes..................................................................................................................104
12.1 Appendix 1: FDD Massive MIMO Site Selection and Gain Evaluation......................................104
12.2 Appendix 2: FDD Massive MIMO Link Budget Tool...................................................................104
12.3 Appendix 3: Base Station Product Description..........................................................................104
12.4 Appendix 4: FDD Massive MIMO Feature Delivery Guide.........................................................105
2021-11-30 Page 7 of 105

1 Introduction
1.1 Purpose and Scope
1.1.1 Purpose
This document provides the application guidelines of the LTE FDD massive MIMO solution. It
describes the function combinations and end-to-end deliverability application of the FDD massive
MIMO solution and provides guidance for post-solution application and maintenance.
1.1.2 Scope
This document describes the application of the FDD massive MIMO solution.
1.2 Lifecycle
This document is drafted at TR4A.
This document will be updated and finalized at TR6.
2 Overview of the FDD Massive MIMO Solution

Massive MIMO is widely regarded as a key leading-edge multiple-antenna technology in the 4.5G
and 5G eras. As a new site form, massive MIMO uses more RF channels and antennas to
perform precise 3D beamforming and multi-layer multi-user multiplexing. This enables massive
MIMO to offer greater capacity than traditional multiple-antenna solutions (for example, 2T2R or
4T4R). Massive MIMO greatly improves the capacity of a single site, solves the pain points in site
obtaining and deployment, and significantly increases the single-user traffic to meet the ultimate
user experience demand for various services.
FDD massive MIMO uses AAU hardware to provide Static Multiple Beam (SMB) and Dynamic
Massive Beam (DMB) functions. By weighting the beams of each cell in a sector, this feature
adapts the beam deployment mode of each cell in the sector to UE distributions, receiving spatial
multiplexing gains and beamforming gains and improving network capacity in heavy-load
scenarios and UE-perceived throughput in non-light-load scenarios. For details about gains, see
the following document: http://3ms.huawei.com/documents/docinfo/1791137.
SMB and DMB described in this document apply only to the FDD massive MIMO solution and
antenna architecture. 3D beamforming and smart 8T8R have the same concepts but have
different antenna architectures, beam split capabilities, and beamforming capabilities. For details,
see the corresponding solution user guides.
Huawei provides beam deployment modes and weights in the beam weight file for typical UE
distribution scenarios. This file is integrated into the eNodeB software package. After the beam
weight file is activated, the SectorSplitGroup and SectorSplitCell MOs are used to configure
the beams of each cell in the sector.
2.1 Sector Split Group

The SectorSplitGroup MO specifies a beam group consisting of AAU sector equipment for a
carrier. The following table describes the parameters in this MO.
2021-11-30 Page 8 of 105

Table 2-1 Parameters in the SectorSplitGroup MO

Parameter
Parameter ID Description
Name
The value of this parameter is the same as the
number of sector split cells, that is, one beam
corresponds to one sector split cell.
SMB is enabled when the
Beam Template SectorSplitGroup.BeamTe SectorSplitGroup.BeamTemplateId
ID mplateId parameter is set to a value greater than 1. For
details, see 3 SMB.
DMB is enabled when the
SectorSplitGroup.BeamTemplateId
parameter is set to 1. For details, see 4 DMB.
When the combinations of different values of
Beam the BeamDeploymentMode and
SectorSplitGroup.BeamDe
Deployment BeamTemplateId parameters are used, the
ploymentMode
Mode eNodeB supports different beam patterns
described in Table 2-2 and Table 2-1.
TM4 Weight SectorSplitGroup.TM4Wei This parameter specifies the weight scheme
Scheme ghtScheme related to TM4.
Table 2-2 Beam patterns for sector beamforming (for modules with an 8-column antenna array)
Beam BeamDeploymentMod BeamDeploymentMode BeamDeploymentMode
Template e Set to MODE_0. Set to MODE_1. Set to MODE_2.
ID
1 Inner circle: 0 Not supported Not supported
Outer circle: 1
2 Not supported Inner circle: 0 Not supported
Outer circle: 2
(1) in Figure 2-2
Outer circle: 3
(2) in Figure 2-2
4 Not supported Not supported Inner circle: 0
Outer circle: 4
(3) in Figure 2-2
2021-11-30 Page 9 of 105

Figure 2-2 Beam patterns (for modules with an 8-column antenna array, BeamTemplateId > 1)
2.2 Sector Split Cell

The following table describes the parameters that must be set in the SectorSplitCell MO to
configure sector split cell information.
Table 2-1 Parameters in the SectorSplitCell MO

Parameter Name Parameter ID Description
SectorSplitCell.Cell This parameter specifies the beam
Cell Beam Index
BeamIndex index of each sector split cell.
This parameter specifies the integral
Cell Beam Tilt SectorSplitCell.CellBeamTilt part of the beam tilt of a sector split
cell.
This parameter specifies the fractional
Cell Beam Tilt SectorSplitCell.CellBeamTiltFra
part of the beam tilt of a sector split
Fraction Part ctionPart
cell.
This parameter specifies the horizontal
Cell Beam SectorSplitCell.CellBeamAzimut
beam azimuth offset of each sector
Azimuth Offset hOffset
split cell.
Each sector split cell is associated with a Cell MO. The following parameters must be set to the
same values for the cells (Cell) in the same sector split group (SectorSplitGroup):
 Uplink and downlink bandwidths: Cell.DlBandWidth and Cell.UlBandWidth
 Uplink and downlink frequencies: Cell.DlEarfcn, Cell.UlEarfcn, and Cell.UlEarfcnCfgInd
 Cell TX and RX mode: Cell.TxRxMode
 Number of CRS ports: Cell.CrsPortNum
 CPRI compression mode: Cell.CPRICompression
 Customized bandwidth configuration (Cell.CustomizedBandWidthCfgInd,
Cell.CustomizedUlBandWidth, and Cell.CustmizedDlBandWidth)
2021-11-30 Page 10 of 105

3 SMB
3.1 Basic Principles
3.1.1 Definition and Principles
SMB provides three functions: 32T32R massive MIMO SMB, PDCCH power resource
improvement, and intra-AAU inter-cell load balancing.
SMB is deployed based on AAUs. It forms multiple fixed beams (cells) on the horizontal and
vertical planes through beamforming. For SMB, UEs are independently scheduled on each beam.
In this way, time-frequency resources are reused between beams, improving cell capacity.
SMB forms multiple beams on the horizontal and vertical planes corresponding to multiple sector
split cells based on the settings of the parameters SectorSplitGroup.BeamTemplateId,
SectorSplitGroup.BeamDeploymentMode, and SectorSplitCell.CellBeamIndex. This function
requires that the SectorSplitGroup.BeamTemplateId parameter be set to 2, 3, or 4 and that the
SectorSplitGroup.BeamDeploymentMode parameter be set to MODE_0, MODE_1, or
MODE_2. The SectorSplitCell.CellBeamIndex parameter specifies the beam index of each
sector split cell. Assuming that four beams are to be configured, the
SectorSplitCell.CellBeamIndex parameter must be set to 0, 1, 2, and 3 for the beams. Each
beam corresponds to a cell.
The beam tilts can be set for SMB using the SectorSplitCell.CellBeamTilt and
SectorSplitCell.CellBeamTiltFractionPart parameters.
3.1.2 Benefits
When congestion cannot be solved by adding frequency bands or sites, SMB can be used to
satisfy the capacity demand in urban areas.
3.1.3 Gain Sources

 Resource doubling gains
SMB splits a cell into multiple cells. Therefore, the number of available PRBs increases by
folds.
 Beamforming gains
Cells generated through SMB form their waves through 32T32R beamforming, achieving
beamforming gains.
3.2 Application Scenarios and Site Selection

This chapter describes the application scenarios of the SMB function and how to select the sites
suitable for deploying SMB on the live network, and provides the site selection criteria.
3.2.1 Application Scenarios

When the network is heavily or moderately loaded, capacity is limited and user experience is
poor. If no other spectrum resources are available and site densification is difficult, SMB can be
used to offload traffic and reduce network load, improving capacity and user experience. The
typical scenarios for deploying SMB are as follows:
 Load
SMB can offer capacity gains only when network congestions occur. The gain is directly
proportionate to the network congestion severity.
2021-11-30 Page 11 of 105

 Inter-site distance
The distance between sites should not be too large. It is recommended that the function be
deployed in dense urban areas with capacity requirements.
 UE distribution
UEs in a cell are evenly distributed. Otherwise, split beams cannot effectively absorb traffic
after SMB is enabled, affecting performance.
 Area selection
There is no obstacle to the coverage area of a site. It is recommended that contiguous
coverage be formed so that SMB can be enabled for contiguous coverage. If only one site is
deployed and the surrounding networks are lightly loaded, the interference between split
cells generated through SMB is the main interference source, which affects the performance.
 Site height
The installation position of the AAU should be higher than surrounding buildings. It is
recommended that surrounding buildings cause no obstacles to the site. In the early stage,
SMB is recommended in the areas with the antenna height much greater than that of
surrounding buildings so that more gains can be offered. It is recommended that the site
height be greater than 20 m.
3.2.2 Site Selection Guidelines
Site Selection Criteria for AAU5711a/AAU5733/AAU5726/AAU5726e

For the frequencies to be reconstructed, select the sites that are suitable for deploying SMB from
the following hour-level and cell-level quantitative counters:
Threshold Threshold
Item Indicator Definition and Description
(4T3S) (4T6S)
Downlink RB L.ChMeas.PRB.DL.Used.Avg x 100 /
>= 70%
Usage (%) L.ChMeas.PRB.DL.Avail
DL Active User >= 8 L.Traffic.ActiveUser.DL.Avg

Traffic
congestion < 5 Mbps (20 MHz)
Downlink UE (L.Thrp.bits.DL –
throughput < 3.7 Mbps (15 MHz) L.Thrp.bits.DL.LastTTI) /
(Mbps) L.Thrp.Time.DL.RmvLastTTI
< 2.5 Mbps (10 MHz)
For 4T3S, the percentage of UEs in
≥ 10% *
>= 30% the minimum beam is estimated
UE Percentage of based on MRs.
(minimum (left or right
distribution UEs (%)
beam) cell) For 4T6S, the percentage of UEs in
the left or right cell is estimated
Minimum If the included angle between the
included angles normal lines of antennas of the same
Engineering
between >= 90 site is too small, the coverages of the
parameter
sectors main lobes may overlap, which
(degree) affects the gain.
NOTE
2021-11-30 Page 12 of 105


The preceding counters measure the average values in the two busiest hours in each of the four busiest
days in a week.

If multiple massive MIMO sectors are deployed on the same site, it is recommended that the included
angle be 120°.

The following values are used as the baseline of six-sector deployment: the average PRB usage of split
cells, the total number of active UEs in split cells, and the average user-perceived rate of split cells.

Sites can be sorted by indicators, including the number of hours during which requirements are met,
peak-hour user-perceived rate, number of active UEs, and spectral efficiency.

Site selection tool and guide: Solution GTM Toolkit on WINS Space
Site selection tool: http://winscloud-dongguan.huawei.com/winscloud-portal-website/#/portal (The

corresponding platform needs to be selected.)
Site selection guide: http://3ms.huawei.com/km/groups/3651517/blogs/details/6220613


The proportion of UEs in the minimum beam must be greater than or equal to 30% when two beams are
configured, 20% for three beams, and 10% for four beams.
Filtering Based on Engineering Parameters and Maps

Display the sites that meet the preceding requirements geographically on the map. You are
advised to deploy SMB on contiguous sites. For example, if a customer requires 100 sites,
select most sites (for example, 150 sites) based on the first two conditions, and then select
100 contiguous sites.
Other Precautions
 Site survey must be performed in a timely manner to determine whether the AAU can be
deployed. Check whether the pole type, antenna installation space, bearing capacity, and
power supply meet the requirements. For details and requirements, see AAU engineering
guidelines.
 Evaluate the site reconstruction solution, determine whether the BBU slots and transmission
bandwidth are sufficient, and check whether boards can be added or replaced.
3.3 Feature Activation

This chapter describes the procedures and policies for activating SMB for massive MIMO. Based
on site information, determine the version, deployment policy, and parameter setting.
Activation Command Examples

//Reconfiguring the following information as the RMV CELL command has been executed
//Adding an RRU chain (in RRU chain or load sharing configuration scenarios)
//RRU chain configuration scenarios

ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=0, HSN=3, HPN=0, CR=AUTO,
USERDEFRATENEGOSW=OFF;
//Load sharing configuration scenarios

ADD RRUCHAIN: RCN=0, TT=LOADBALANCE, HSRN=0, HSN=3, HPN=0, TSRN=0, TSN=3, TPN=1, CR=AUTO,
//Adding an AAU, without running the MOD RRUCHAIN command in RRU chain configuration scenarios
MOD RRUCHAIN: RCN=0, BRKPOS1=0, BRKPOS2=0;
ADD RRU: CN=0, SRN=100, SN=0, TP=TRUNK, RCN=0, PS=0, RT=AIRU, RS=LO, RXNUM=32, TXNUM=32,
MNTMODE=NORMAL, RFDCPWROFFALMDETECTSW=OFF, RFTXSIGNDETECTSW=OFF;
2021-11-30 Page 13 of 105

//Adding a sector
ADD SECTOR: SECTORID=100, ANTNUM=0, CREATESECTOREQM=FALSE;
//Adding sector equipment

ADD SECTOREQM: SECTOREQMID=100, SECTORID=100, ANTCFGMODE=BEAM, RRUCN=0, RRUSRN=100, RRUSN=0,
BEAMSHAPE=SEC_120DEG, BEAMLAYERSPLIT=None, BEAMAZIMUTHOFFSET=None;
//(Optional) Adding baseband equipment

ADD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, SN1=x;
//Adding cells (using four split cells served by a module with an 8-column antenna array as an example)
ADD CELL: LocalCellId=100, CellName="beam0", NbCellFlag=FALSE, FreqBand=3, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=1350, UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=100, PhyCellId=100,
FddTddInd=CELL_FDD, EuCellStandbyMode=ACTIVE, RootSequenceIdx=0, CustomizedBandWidthCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, CPRICompression=ENHANCED_COMPRESSION,
CrsPortNum=CRS_PORT_4, TxRxMode=32T32R, WorkMode=UL_DL;
MOD CELLMIMOPARACFG: LocalCellId=100, MimoAdaptiveSwitch=CL_ADAPTIVE, InitialMimoType=ADAPTIVE;
//Binding the cell to the sector equipment and setting the CELLBEAMMODE parameter. Determine whether to bind the
baseband equipment based on site conditions.
ADD EUCELLSECTOREQM: LocalCellId=100, SectorEqmId=100, CELLBEAMMODE=MASSIVE_MIMO_Ph2,
BASEBANDEQMID=0;
BASEBANDEQMID=0;
BASEBANDEQMID=0;
BASEBANDEQMID=0;
//(Optional) Modifying the setting of the cell system information switch (assuming that the cell with LocalCellId set to 100 is a
downlink-only cell)
MOD CELLSIMAP: LocalCellId=100, SiSwitch=ForbidCellSiSwitch-1;
//Adding an operator for each cell

ADD CELLOP: LocalCellId=100, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
2021-11-30 Page 14 of 105


ADD CELLOP: LocalCellId=103, TrackingAreaId=0, MMECFGNUM=CELL_MME_CFG_NUM_0;
//Setting PA, PB, and RS power (which is denoted by xxx in the following and can be set based on actual network conditions)
MOD CELLDLPCPDSCHPA: LocalCellId=100, PaPcOff=DB_3_P_A;
MOD PDSCHCFG: LocalCellId=100, Pb=1;
MOD PDSCHCFG: LocalCellId=100, ReferenceSignalPwr=xxx;
//(Optional, applicable to the AAU5711a/ AAU5733/AAU5726) Configuring a sector split group

ADD SECTORSPLITGROUP: SectorSplitGroupId=0, BeamTemplateId=4, BeamDeploymentMode=MODE_2,
TM4WeightScheme=DEFAULT_MODE;
//(Optional, applicable to the AAU5711a/AAU5733/AAU5726) Configuring a sector split group

//(Optional, applicable to the AAU5711a/AAU5726) Configuring sector split cells. The cell beam tilts and horizontal azimuth
offsets can be set based on network conditions.
ADD SECTORSPLITCELL: LocalCellId=100, SectorSplitGroupId=0, CellBeamIndex=0, CellBeamTilt=8,
CellBeamTiltFractionPart=0, CellBeamAzimuthOffset=0;
//(Optional, applicable to the AAU5711) Configuring sector split cells. The cell beam tilts and azimuth offsets can be configured
based on actual network conditions.
//Configuring SRS parameters if the SectorSplitGroup.BeamTemplateId parameter is set to 2

MOD SRSCFG: LocalCellId=100, SrsCfgInd=BOOLEAN_TRUE,
FddSrsCfgMode=DEFAULTMODE,SrsAlgoOptSwitch=SrsSubframeRecfgOptSwitch-0, SrsSubframeCfg=SC7;
MOD SRSCFG: LocalCellId=101, SrsCfgInd=BOOLEAN_TRUE,
FddSrsCfgMode=DEFAULTMODE,SrsAlgoOptSwitch=SrsSubframeRecfgOptSwitch-0, SrsSubframeCfg=SC8;
MOD CELLSRSADAPTIVECFG: LocalCellId=100, SrsPeriodAdaptive=OFF, UserSrsPeriod=ms320;
2021-11-30 Page 15 of 105

//(Optional, recommended) Turning on the DlCqiAdjDeltaOptSwitch to achieve better performance

MOD CELLALGOSWITCH: LocalCellId=100, CqiAdjAlgoSwitch=DlCqiAdjDeltaOptSwitch-1;
//Activating the cells

ACT CELL: LocalCellId=100;
//(Optional) (Recommended) Turning on the MM_SCC_TM9_MU_MIMO_SW in dual-band massive MIMO scenarios to achieve
better performance
MOD CELLMIMOPARACFG: LocalCellId=1, MimoSwitch=MM_SCC_TM9_MU_MIMO_SW-1;
//(Optional) Turning on the FREQ_DIFF_AMEND_SW in dual-band massive MIMO scenarios to achieve better performance if
the MM_SCC_TM9_MU_MIMO_SW is turned on
MOD CELLMIMOPARACFG: LocalCellId=1, MimoSwitch=FREQ_DIFF_AMEND_SW-1;
Deactivation Command Examples

N/A for 32T32R Massive MIMO SMB
3.3.1 Feature Application Policies

Massive MIMO is recommended when cell capacity or coverage needs to be improved. Massive
MIMO cell activation requires LEOFD-131301 Massive MIMO Introduction and LEOFD-131302
32T32R Massive MIMO Basic Package to be deployed.
3.3.2 KPI Monitoring

To facilitate a fair performance and KPI comparison before and after massive MIMO deployment
in reconstruction scenarios, you are advised to monitor the KPIs for at least one week and ensure
that the KPIs are stable and no other operations are performed on the entire network before
activating the massive MIMO feature.
In deployment scenarios, you are advised to observe related KPIs after massive MIMO is
deployed.
For details about counters, see the attachment.
3.3.3 Network Planning
Site Selection
Hotspot cells need to be identified before target cells for SMB are identified.
Step 1 Identify hotspot cells.
2021-11-30 Page 16 of 105

Based on the site selection criteria described in 3.2.2 Site Selection Guidelines, select
sites with traffic congestion in the entire network (or in a large area) and list hotspot cells
(or sites).
Step 2 Determine whether traffic is balanced after splitting for capacity expansion.
Collect all site selection data of hotspot cells and filter sites that meet user distribution
conditions through the site selection platform.
Step 3 Check the included angle.
It is recommended that the included angle between different sectors on the same site be
greater than or equal to 90° before splitting. If multiple massive MIMO sectors are
deployed on the same site, it is recommended that the included angle be 120°.
----End
The preceding site selection operations can be implemented by referring to WINS Cloud Product
Solution GTM Toolkit Delivery Guide. Network planning personnel only need to import data
sources and set parameters according to documents on the following website:
http://winscloud.huawei.com/winscloud-task-gtm-website/#/MarketToolKit
For the address of the WINSSpace and general site selection guidelines, see the WINSSpace
site selection planning document.
Basic RF Planning
Most massive MIMO cells are reconstructed based on 2T2R/4T4R cells. To ensure consistent
coverage, it is recommended that the antenna azimuth and total outer-circle tilt be consistent with
the baseline values. You are advised to preferentially adjust the mechanical downtilt. If the
mechanical downtilt cannot be adjusted, adjust the electrical downtilt. The following special
scenarios need to be considered separately:
 If massive MIMO is reconstructed from a 6-sector SFN cell, the azimuth is the average
azimuth of two split antennas.
 If the total tilts (mechanical downtilt and electrical downtilt) of two split antennas used in the
baseline are different, the tilt of the massive MIMO cell is consistent with that of the split
antenna with a smaller total tilt.
 The recommended electrical downtilt of the AAU5711 ranges from –5° to 11°. If the
Cell.CrsPortNum parameter is set to CRS_PORT_2, the downtilt 6° is recommended for
inner cells and 0°is recommended for outer cells. If there are only outer cells but no inner
cells, the downtilt 3° is recommended. If the Cell.CrsPortNum parameter is set to
CRS_PORT_4, you are advised to configure only outer cells and set the downtilt to 3° for
these cells.
 It is recommended that the electrical downtilt of the AAU5711a /AAU5733/AAU5726 be set to
8°. If the TM4WeightScheme parameter is set to COVERAGE_MODE_1, the electrical
downtilt that takes effect is 8° while the configured GUI value is invalid. If the
TM4WeightScheme parameter is set to COVERAGE_MODE_0 or COVERAGE_MODE_2,
the recommended adjustment range is 5° to 10°for the AAU5711a/AAU5733 or 6° to 9°for the
AAU5726.
 Tilt planning principles: Assume that the baseline mechanical downtilt plus electrical downtilt
is equal to N° (N < 8). Then, after reconstruction for massive MIMO, the downtilt supporting
arm needs to be installed in the position of the lower handle (as shown in part b of the
following figure) to ensure downtilt alignment. Here, the mechanical downtilt is equal to (N -
8)°.
2021-11-30 Page 17 of 105

The following uses the AAU5711a/AAU5733 module as an example:

Assume that the mechanical tilt is 4° and the electrical tilt is 1 degree before the reconstruction. If
there are inner and outer cells, the mechanical downtilt of the massive MIMO cell can be set to
5°, and the electrical downtilt is set to 0° for the outer cell and to 6° for the outer cell. If there is
only the outer cell but not the inner cell, the mechanical downtilt of massive MIMO can be set to
2° and the electrical downtilt of the outer cell can be set to 3°.
In case of a new SMB cell, it is recommended that frontline engineers perform network planning
before deploying the cell. This avoids performance problems caused by network planning issues.
PCI/RSI Planning
Sector addition has the following impacts on PCI planning: The original PCI planning and use
principles need to be planned and optimized again. PCIs must not conflict and PCI mod 3 values
must not be equal.
The increase in the number of sectors reduces the number of PCI reuse times and shortens the
PCI reuse distance, which leads to a higher probability of PCI conflicts. If there are a large
number of massive MIMO eNodeBs and they provide contiguous networks, PCI use principles
need to be adjusted and PCIs need to be replanned. If sites are interspersed on the network or
the solution is deployed only on a few eNodeBs providing contiguous coverage, PCIs can be
planned based on the original network plan and then PCI optimization is performed based on
network performance.
Currently, the U-Net tool is used by Huawei for neighboring cell planning. The U-Net is a network
planning tool and is maintained by a dedicated department.
You can also use the U-Net tool to plan the RSI.
Standalone U-Net version:
https://support.huawei.com/carrier/navi?coltype=software#col=software&detailId=PBI1-
22075382&path=PBI1-7851894/PBI1-8132365/PBI1-8132371/PBI1-21395144/PBI1-21576275
2021-11-30 Page 18 of 105

Figure 3-1 Standalone U-Net download
NOTE
 To apply for a license, contact He Kezhen (employee ID: hwx239314).
 To apply for antenna files for simulation, contact Wang Lei (employee ID: 00493692)
and Zhu Xiaolong (employee ID: 00426150) of the massive MIMO work team.
Power Configuration
You must be cautious of power configuration because comparison with original network KPIs is
involved during reconstruction from 2T to massive MIMO. In principle, the performance is
improved while the coverage remains unchanged.
Step 1 Calculate the reference signal power A. Generally, the recommended PA/PB
configuration is the same as that on the original network. If there is a big gap for inter-
frequency coverage, it is recommended that the PA/PB configuration be optimized. The
maximum output power of an AAU is fixed. However, the actual CRS power depends on
the beamforming configuration because the antenna port performs beamforming. For
details, see Appendix 2.
Step 2 Calculate the loss B of the feeder/combiner in the original network. Because the AAU is
mounted on the tower, the loss from some RRUs to the antenna (about 1.2 dBm for the
20 m 7/8 feeder) and the combiner loss (2–3 dB) can be reduced. Assume that the
feeder length is 100 m. The following table lists the feeder loss corresponding to
different feeder types and frequencies.
Table 3-1 Loss of common feeders

Feeder Type 1800 MHz 2000 MHz 2500 MHz
1/2 feeder 10.1 dB/100 m 10.7 dB/100 m 12.1 dB/100 m
½ soft feeder 16.6 dB/100 m 17.6 dB/100 m 19.2 dB/100 m
7/8 feeder 5.8 dB/100 m 6.1 dB/100 m 7.0 dB/100 m
⅞ soft feeder 6.2 dB/100 m 6.6 dB/100 m 7.5 dB/100 m
2021-11-30 Page 19 of 105

Step 3 Determine the beam gain C of the original antenna and the AAU.
The original antenna gain is queried based on the antenna file. The AAU beam gain is related to
beamforming. For details, see the Excel file in step 1.
----End
With reference to steps 1 to 3, the link budget of CRS transmissions equals A - B + C.
Neighboring Cell Planning

The principles for planning multi-sector neighboring cells are the same as those for planning
three-sector cells. The increase in the number of sectors requires reconfiguration and
optimization of original neighbor relationships and makes the upper limit on the number of
allowed neighboring cells a bottleneck.
SMB for massive MIMO introduces new cells to the original network. Neighboring cells can be
planned based on the following principles:
 All cells in the split sector group inherit the original neighbor relationships.
 All cells in a split sector group are added as intra-frequency neighboring cells of each other.
 All cells in the split sector group are added as the neighboring cells of nearby neighboring
cells and external cells.
NOTE
Consider intra-RAT and inter-RAT neighbor relationships at the same time when configuring the preceding
neighbor relationships.
In addition, ANR can be enabled to automatically add neighboring cells and set neighboring cell
priorities for supplement.
3.3.4 Hardware Requirements
AAU
Unlike traditional RRUs and passive antennas, an AAU is a module that has both antenna and
RF module functions. In addition to saving feeders and simplifying engineering, the AAU can also
reduce feeder loss and improve performance.
As the AAU has antennas, no additional antenna or feeder is required for deploying massive
MIMO. Each AAU port requires only one pair of optical fibers (one for receiving and the other for
transmitting) to connect to the BBP through the CPRI port, as shown in the following figure.
Figure 3-1 Networking diagram for deploying massive MIMO using an AAU
2021-11-30 Page 20 of 105

Currently, AAU5711a/AAU5733/ AAU5726 can be used for FDD massive MIMO.
Table 3-1 FDD Massive MIMO product specifications

Frequency Output
Module RAT Capacity
Band (MHz) Power (W)
AAU5711a 2 LTE carriers; bandwidth:5/10/15/20
LTE FDD 1800 160
(1.8 GHz) MHz
AAU5711a 2 LTE carriers; bandwidth: 5/10/15/20
LTE FDD 2600 160
(2.6 GHz) MHz
2 LTE carriers; bandwidth: 5/10/15/20
AAU5733 LTE FDD 2600 240
MHz
2 LTE FDD carriers; bandwidth:
LTE FDD 1800/2100
5/10/15/20 MHz.
2 UMTS carriers + 2 LTE FDD
UL 2100 carriers; LTE bandwidth: 5/10/15/20
MHz.
AAU5726 300 4 LTE FDD carriers, with a maximum

LTE FDD 1800+2100 of 2 carriers in each band; bandwidth:
5/10/15/20 MHz.
1800 MHz 2 UMTS carriers (MIMO) + 4 LTE
(LTE FDD) + FDD carriers (with a maximum of 2
UL
2100 MHz LTE FDD carriers in each band); LTE
(UL) bandwidth: 5/10/15/20 MHz.
Boards
 BBU: BBU3910, BBU5900, or BBU5900A
 BBP: UBBPg2a, UBBPg3, or later
 Main control board: UMPT
CPRI Specifications
Table 3-2 CPRI specifications
Item AAU5711a AAU5726
Number of CPRI ports 2 2
CPRI data rate 2x10.1 Gbit/s or 2x24.3 Gbit/s 10.1 Gbit/s or 24.3 Gbit/s
CPRI Topology Star or load sharing Star or load sharing

Maximum distance
20 km 20 km
from the BBU
2021-11-30 Page 21 of 105

If two CPRI optical fibers are required, they must be of the same length. The number of carriers,
system bandwidth, compression mode, and networking mode must not exceed the CPRI
capability of the BBP. For complex networking such as CPRI load sharing or CPRI compression,
a dedicated site solution design is recommended. For details, see FDD Massive MIMO Site
Solution.
Antenna Requirements
As the AAU has antennas, there are no additional antenna requirements for massive MIMO.
Figure 3-2 AAU hardware.
3.3.5 Software Requirements
Version Requirements
Use eRAN16.1 or a later software version.
License Constraints
To enable SMB for massive MIMO, you need to purchase the corresponding feature, hardware,
and power licenses.
 Feature license
To use this function, you need to purchase licenses for massive MIMO introduction and
32T32R massive MIMO package.
You are advised to purchase licenses for LOFD-001001, LOFD-001003, LOFD-001005, and
LOFD-001060.
2021-11-30 Page 22 of 105

Feature ID Feature Name Model Sales Unit

LEOFD-131301 Massive MIMO Introduction LT1SMAMIMO01 Per Cell
LEOFD-131302 32T32R Massive MIMO Package LT1S32MAMIMO Per Cell
LOFD-001001 DL 2x2 MIMO LT1S0D2I2O00 Per Cell
LOFD-001005 UL 4-Antenna Receive Diversity LT1S0U4ARD00 Per Cell
LOFD-001060 DL 4x4 MIMO LT1S0DMIMO00 Per Cell
Note
For Massive MIMO Introduction and 32T32R Massive MIMO Package, the sales unit "Per Cell" refers to
per sector split group specified by the SectorSplitGroup MO, and is unrelated to the number of sector
split cells in the group.
 Hardware and power licenses

Purchase hardware and power licenses based on live network configurations.
Model Description Configuration Principle
Configure this license item when massive MIMO is supported
and there are more than 16 channels. One license unit is
Massive MIMO required for every 16 transmit channels except for the 16 default
LT1SMM BB 16-Transmit baseband transmit channels per cell.
BB16T0 Channel Group Number of license units configured for each BBP = Number of
License(FDD) sectors with more than 16 transmit channels x (Number of
channels / 16 - 1) x Number of carriers
This applies only to boards that support massive MIMO.
and there are more than 16 channels. One license unit is
Massive MIMO required for every 16 receive channels except for the 16 default
LT1SMM BB 16-Receive baseband receive channels per cell.
BB16R0 Channel Group Number of license units configured for each BBP = Number of
License(FDD) sectors with more than 16 receive channels x (Number of
channels / 16 - 1) x Number of carriers
and there are more than 16 channels.
Massive MIMO
RF 16-Transmit One license unit is required for every 16 transmit channels
LT1SMM Channel Group except for the 16 default RF transmit channels.
RF16T0 License for Number of license units = Number of RRUs with more than 16
5000 transmit channels x (Number of working channels per RRU/16 -
Series(FDD) 1)
This applies to the AAU that supports massive MIMO.
LT1SMM Massive MIMO Configure this license item when massive MIMO is supported
RF16R0 RF 16-Receive and there are more than 16 channels.
Channel Group One license unit is required for every 16 receive channels
2021-11-30 Page 23 of 105

Model Description Configuration Principle

except for the 16 default RF receive channels.
License for Number of license units = Number of RRUs with more than 16
5000 receive channels x (Number of working channels per RRU/16 -
Series(FDD) 1)
Massive MIMO
20W Power One license unit is required for every 20 W except for the default
LT1S0M 20 W per RF module.
License for
M20P00
5000 Series RF This applies to the AAU that supports massive MIMO.
Module(FDD)
Configure one license unit for each cell with a bandwidth of 0 to
5 MHz.
Massive MIMO Configure two license units for each cell with a bandwidth of 10
5MHz Cell MHz.
LT1S0M Bandwidth
Configure three license units for each cell with a bandwidth of 15
M5CB00 License for
MHz.
5000 Series RF
Module(FDD) Configure four license units for each cell with a bandwidth of 20
MHz.
Massive MIMO
Multi-carrier One license unit is required for each carrier except for the one
LT1S00M default carrier per RF module.
License for
MMC00
5000 Series RF This applies to the AAU that supports massive MIMO.
Module(FDD)
Massive MIMO and TM9 MU-MIMO is supported in a cell.
DL 2-Layers
LT1SMM Number of license units configured for each BBP = Number of
Extended
DL2EPU massive MIMO cells x (Maximum number of TM9 MU-MIMO
Processing Unit
streams supported per cell / 2)
License(FDD)
Configuration Constraints
For details, see Massive MIMO (FDD) Feature Parameter Description.
Cooperation with Other Features

 CA
As a cell with SMB for massive MIMO is split into multiple cells, carrier aggregation with
other frequencies under the same coverage needs to be replanned.
For example, cell A is an inter-frequency cell of cell B, and cell B is split into two cells B1 and
B2 after massive MIMO is deployed.
− Configure two CA groups, one with cells A and B1 and the other with cells A and B2.
2021-11-30 Page 24 of 105

− The PCell priorities of cells B1 and B2 are higher than that of cell A. (If no anchor switch is
turned on, the priorities are not configured for the massive MIMO cells.)
− If cell B1 or B2 act as the PCell, the SCell blind configuration flag of cell A is set to TRUE.
(If two or more intra-frequency cells act as SCells, blind configuration is not configured.)
− If cell A acts as the PCell, the blind configuration flags of cells B1 and B2 are set to
FALSE (default).
3.3.6 Engineering Requirements
Feeder Requirements
Common RRUs have requirements on feeders, for example, in terms of the difference in the total
feeder length between different ports and the difference in the total feeder loss. Massive MIMO is
deployed based on the active ports on the AAU and therefore has no feeder requirements.
Connection Requirements
Common RRUs have requirements for connections, for example, in terms of line sequence.
Massive MIMO is deployed based on the active ports on the AAU and therefore has no
connection requirements.
Line Sequence Detection

When the AAU5711a and AAU5726 are used to deploy massive MIMO, line sequence detection
is not involved.
Installation Position Requirements

The width of an AAU is greater than that of other antennas. Therefore, to ensure sector coverage,
it is recommended that the AAU and the antennas of other frequencies are installed vertically.
(Deployment at the same height is not recommended.)
To compare the coverage difference before and after the reconstruction, the azimuth of the AAU
after the reconstruction must be consistent with that of the original baseline cell and the downtilt
angle of the outer cell must be consistent with that of the original baseline cell.
3.3.7 Parameter Settings

The FDD massive MIMO parameter configuration model is as follows:
2021-11-30 Page 25 of 105

In this figure:
 SectorSplitGroup: specifies a sector splitting cell, representing a massive MIMO carrier of a
physical sector.
− BeamTemplateId: specifies the ID of a beam template, which indicates the number of
beams of the same carrier in a sector. A beam template consists of the weight information
about a group of beams and corresponds to a beam template in XML format.
− BeamDeploymentMode: specifies a beam deployment mode, which indicates the
number of inner-cell and outer-cell beams of the same carrier. The specific mode is
closely related to the AAU model. For example, the AAU5711a can provide one to four
beams, corresponding to different distribution modes.
 SectorSplitCell: specifies a cell beam with an independent PCI in a sector (or a group of
beams with the same PCI).
− The SectorSplitCell MOs of the SectorSplitGroup MO must have the same sector
(sector equipment), RF module (AAU), frequency, uplink and downlink bandwidth,
CrsPortNum, and CPRI compression mode, but have different PCIs.
− LocalCellId: specifies a local cell ID.
− CellBeamIndex: specifies a cell beam index.
− CellBeamTilt: specifies the electrical downtilt angle of a cell beam.
 Cell:
− TxRxMode: specifies the number of physical antenna ports. Set it to 32T32R (a new
enumerated value) for FDD massive MIMO.
− CrsPortNum: Number of logical ports. You can set it to 2 or 4 for FDD massive MIMO.
 EuCellSectorEqm:
2021-11-30 Page 26 of 105

− CellBeamMode: specifies a cell beam mode. Set it to MASSIVE_MIMO_Ph2 for FDD

massive MIMO.
3.4 Benefits
After massive MIMO is deployed, you can evaluate the gains based on traffic statistics and DT
results.
3.4.1 Activation Verification

Run the DSP CELL command to check whether the massive MIMO cell is activated.
3.4.2 Gain Specifications and Evaluation Methods

It is recommended that traffic KPIs be used to evaluate the gains of massive MIMO. Drive tests
are not recommended.
Gain Specifications
For details about gain specifications, see the following document:
http://3ms.huawei.com/documents/docinfo/1791137
NOTE
The traffic and user-perceived rate gains are evaluated based on the right-most point of the trend line in the
scatter chart.
Evaluation Methods
The gains in cell throughput, user throughput, and PRB usage are usually considered. It is
recommended that feature gains be displayed in scatter charts. There are two types of scatter
charts: Traffic vs. PRB Usage Ratio, and User Throughput vs.Traffic, which reflect the capacity
gains and user-perceived throughput gains for given PRB usage and traffic. In addition, you can
observe the traffic KPIs in busy hours to check the actual traffic and average UE throughput
gains. This reflects the actual gains in the current phase, which is related to the PRB usage and
the number of UEs at each site.
 Improvement in the UE-perceived rate
Analyze the proportion by which the UE-perceived rate improves for given traffic. It is
recommended that the scatter chart regarding user throughput and traffic be used to obtain
the UE throughput increase when traffic is heaviest before the reconstruction, as shown in
Figure 3-1.
− Traffic in the original cell = L.Thrp.bits.DL
− Traffic after the reconstruction = Sum of the values of the L.Thrp.bits.DL counter for all
cells in a sector split group
− UE throughput of the original cell = (L.Thrp.bits.DL -
L.Thrp.bits.DL.LastTTI)/L.Thrp.Time.DL.RmvLastTTI
− UE throughput after reconstruction = (Sum of L.Thrp.bits.DL of all cells in a sector split
group – Sum of L.Thrp.bits.DL.LastTTI of all cells in a sector split group)/Sum of
L.Thrp.Time.DL.RmvLastTTI of all cells in a sector split group
2021-11-30 Page 27 of 105

Figure 3-1 Scatter chart of UE throughput and traffic
 Spectral efficiency improvement

Analyze the proportion by which traffic increases for a given PRB usage. It is recommended
that the scatter chart regarding downlink traffic and PRB usage be used to obtain the traffic
increase when the PRB usage reaches the maximum after the reconstruction, as shown in
Figure 3-2.
− Traffic in the original cell = L.Thrp.bits.DL
− Traffic after the reconstruction = Sum of the values of the L.Thrp.bits.DL counter for all
cells in a sector split group
− PRB usage of the original cell = L.ChMeas.PRB.DL.Used.Avg/L.ChMeas.PRB.DL.Avail
x 100%
− PRB usage after the reconstruction = Average PRB usage of all cells in a sector split
group
2021-11-30 Page 28 of 105

Figure 3-2 Scatter chart of traffic and PRB usage
 The gains of SMB for massive MIMO are closely related to whether the SMB cells provide
contiguous coverage and the user distributions of each cell in the sector split group. The
gains are great if cell coverage is contiguous and UEs are evenly distributed.
 The traffic gain and the user throughput gain are mutually constrained. Therefore, the
maximum value of the traffic gain and the user throughput gain cannot be met at the same
site.
3.4.3 Network Impact

 Downlink user-perceived throughput
In idle hours:
− If the original cell is a 2T2R one and the PRB usage is less than 20%, the user-perceived
throughput may decrease.
− If the original cell is a 4T4R one and the PRB usage is less than 40%, the user-perceived
throughput may decrease.
 Downlink peak data rate
In cells served by an eNodeB with a 2T2R/4T4R 3-sector configuration, using SMB increases
the proportion of times a small rank value is reported and therefore a lower percentage of
UEs that achieve their peak data rates with downlink 2x2 multiple-input multiple-output
(MIMO) enabled.
 Downlink coverage
On a network with non-contiguous coverage from cells generated by using SMB, if SMB
causes cell power to be lower than neighboring 2T2R/4T4R cell power, the local cell
coverage shrinks.
 Other network performance indicators
In an eNodeB with a 2T2R/4T4R 3-sector configuration, SMB causes an increase in the
number of cells. This may result in a lower handover success rate, more RRC connection
2021-11-30 Page 29 of 105

reestablishments, and a higher service drop rate than the performance indicators before SMB
is used.
3.4.4 DT Analysis
It is recommended that traffic KPIs be used to evaluate the gains of massive MIMO. The drive
test method is not recommended. It is recommended that drive tests, if required, be performed for
coverage comparison.
Analyze coverage changes based on the changes in PCIs, RSRP, SINR distribution, and average
values after SMB is enabled.
If the coverage remains unchanged after SMB is enabled, the average RSRP value is basically
the same as the baseline value. Compared with the baseline value, the SINR decreases due to
interference increases.
For drive tests, it is recommended that test routes cover the entire area as much as possible. If
there is a large proportion of test routes in the overlapping areas of beams generated for massive
MIMO SMB, the final test result is affected.
3.5 Feature Optimization

3.5.1 Coverage Optimization
Due to the restrictions on the antenna gain of the AAU and the AAU power, coverage shrinkage
may occur after massive MIMO is enabled on the live network. Currently, two optimization
methods are available:
1. Modify the RS power and power ratio.
2. Change the total downtilt angles for massive MIMO.
RS Parameter Modification
Modify the RS power and adjust the power ratio parameters [Pa, Pb] so that the transmit power of
a single port does not exceed the upper limit when the RS power is increased. The following is an
MML command example:
MOD PDSCHCFG: LocalCellId=x, ReferenceSignalPwr=***, Pb=****;
2021-11-30 Page 30 of 105

MOD CELLDLPCPDSCHPA: LocalCellId=x, PaPcOff=******;
Downtilt Angle Modification

Modify the total downtilt angles (mechanical downtilt plus electrical downtilt) of the outer cells so
that the coverage is approximately the same as that before SMB is enabled.
Coverage Mode 2
Coverage mode 2 effectively improves power utilization, beamforming gains, and coverage,
compared with coverage mode 1 and the default coverage mode.
Downlink Turbo Pilot

For details, see 9 Downlink Turbo Pilot.
3.5.2 Load Balance Optimization
Inter-Frequency or Inter-RAT Load Balancing

Modify the threshold for starting inter-frequency or inter-RAT measurement and change the cell
reselection priorities. The following is an MML command example:
MOD CELLRESEL: LocalCellId=x, SNonIntraSearch=****, CellReselPriority=*****;
Inter-Frequency Massive MIMO Load Steering

Inter-frequency massive MIMO load steering can be enabled in the multi-band LTE networking to
maximize the capacity of massive MIMO. For details, see Intra-RAT Mobility Load Balancing
Feature Parameter Description.
3.5.3 Intra-eNodeB CSPC

In massive MIMO SMB scenarios (where there are more than two beams, or there are two PCIs
and the intelligent beam scheduling or intelligent beam shaping switch is turned on), an increase
in the number of cells under an eNodeB leads to stronger intra-eNodeB intra-frequency
interference from neighboring cells. Intra-eNodeB CSPC can be used to optimize performance in
this scenario.
2021-11-30 Page 31 of 105

This function applies to UEs that experience interference mostly from intra-eNodeB intra-
frequency neighboring cells. Based on real-time information about the interference from the cells
in the cell set, a UE determines the difference between the interference status at the downlink
scheduling time and the interference status at the last CSI reporting time. The UE adjusts the CSI
accordingly. Based on the adjusted CSI, the eNodeB selects an MCS index that is more suitable
for downlink data transmission, improving the downlink spectral efficiency and data rates. For
details, see CSPC Feature Parameter Description.
The following is an MML command example:
MOD CELLCSPCPARA: LOCALCELLID=x, eCspcA3Offset=-12, IntraEnbCspcSw=ON;
2021-11-30 Page 32 of 105

4 DMB
DMB uses AAUs and beamforming to establish one cell. A cell can provide dedicated service
beams for multiple TM9 UEs at the same time. TM4 UEs are scheduled independently in a cell.
DMB forms a fixed beam to serve one cell based on the settings of the
SectorSplitGroup.BeamTemplateId, SectorSplitGroup.BeamDeploymentMode, and
SectorSplitCell.CellBeamIndex parameters. DMB requires that the
SectorSplitGroup.BeamTemplateId parameter be set to 1, the
SectorSplitGroup.BeamDeploymentMode parameter be set to MODE_0, and the
SectorSplitCell.CellBeamIndex parameter be set to 0. Figure 4-1 shows DMB.
Figure 4-1 DMB
Uplink 32-Antenna Receive Diversity

In the uplink, 32 receive channels can be used to receive the same signal of a given UE from
different directions to improve reception quality. The eNodeB performs beamforming to form
beams targeting specific areas and produce beamforming gains. DMB forms an optimal number
of receive beams through beamforming on 32 antennas in the uplink. For example, eight receive
beams are formed for the PUSCH. The subsequent processing is similar to that of uplink 8-
antenna receive diversity.
Downlink 32-Antenna Spatial Multiplexing

In the downlink, DMB forms one cell (beam) using 32 antennas. UEs in this cell are scheduled
independently. The Cell.CrsPortNum parameter can be set to CRS_PORT_2 or CRS_PORT_4
for the cell. The beam form is identical for all antenna ports of a given cell and is similar to the
beam form of 2T or 4T. DMB provides different functions based on cell configurations and UE
capabilities. Specifically:
2021-11-30 Page 33 of 105

If the TM9Switch option of the CellAlgoSwitch.EnhMIMOSwitch parameter is selected and

either of the following conditions is met, the eNodeB uses four antenna ports to transmit CSI-RSs
to TM9-capable UEs compliant with 3GPP Release 10 and supporting 4-port CSI-RS
transmission, allowing such UEs to work in TM9 mode.
 The CellCsiRsParaCfg.CsiRsSwitch parameter is set to FIXED_CFG.
 The CellCsiRsParaCfg.CsiRsSwitch parameter is set to ADAPTIVE_CFG, and the
proportion of PRBs used to schedule TM9-capable UEs in the cell exceeds the value of the
CellMimoParaCfg.PrbRatioThldForTm9SuMimo parameter.
To reduce the impact of CSI-RS configurations on network performance, it is recommended that
the CellCsiRsParaCfg.CsiRsSwitch parameter be set to ADAPTIVE_CFG. With this setting, the
eNodeB adaptively enables or disables TM9 in the downlink based on network conditions. If the
CellCsiRsParaCfg.CsiRsSwitch parameter is set to FIXED_CFG, the eNodeB always transmits
CSI-RSs, which produces more impact on network performance.
When the TM9Switch option under the CellAlgoSwitch.EnhMIMOSwitch parameter is selected
but neither of the preceding conditions is met:
 If the Cell.CrsPortNum parameter is set to CRS_PORT_2, downlink 2x2 MIMO takes effect.
 If the Cell.CrsPortNum parameter is set to CRS_PORT_4, downlink 4x2 MIMO or 4x4
MIMO takes effect.
If a cell meets the preceding conditions for supporting TM9, CSI-RSs can be transmitted to TM9-
capable UEs through four ports. The cell can provide multiple dedicated service beams for
multiple TM9 UEs at the same time to multiplex time-frequency resources between beams and
improve capacity. The eNodeB measures the RSRP of TM9 beams based on uplink SRS quality
and regards the beam with the largest RSRP value as the target beam of the UE. To improve
network performance:
 If line of sight (LOS) transmission prevails between the eNodeB and UEs, the UE feedback
information is accurate. In this situation, set the
CellMimoParaCfg.MuMimoWeightAdjStrategy parameter to FULL_ZERO_FORCING. The
eNodeB performs MU-MIMO pairing based on the UE feedback information.
 If NLOS transmission prevails between the eNodeB and UEs, the UE feedback information
cannot completely reflect channel conditions. To avoid negative impacts caused by weight
correction based on incomplete channel information, set the
CellMimoParaCfg.MuMimoWeightAdjStrategy parameter to NON_ZERO_FORCING.
When data is transmitted in MU-MIMO mode, the eNodeB does not modify the transmit
weight of each data flow, improving the downlink throughput.
Downlink 8-Layer MU-MIMO

This feature is controlled by the CellMimoParaCfg.MuMimoMaxPairLayer parameter. To enable
this function, set this parameter to EIGHT_LAYERS
This feature enables an eNodeB to pair two to eight UEs working in TM9 for MU-MIMO. Up to
eight data streams can be transmitted using the same OFDM time-frequency resource. When this
feature is enabled, the eNodeB performs the following operations: 1. Determines the UEs to be
paired and the number of data streams to be transmitted to each UE based on the UE pairing
conditions. 2. Generates the weight values for data streams. 3. Imposes weight on data symbols
and DM-RS symbols on each data stream based on the generated weight values. 4. Combines
these symbols and then transmits data over antenna ports. With this feature, multiple data
streams are transmitted using the same time-frequency resource, beamforming is implemented
on the data streams, and interference is mitigated between the streams, thereby increasing the
downlink spectral efficiency.
2021-11-30 Page 34 of 105

Downlink 16-Layer MU-MIMO

This feature is controlled by the CellMimoParaCfg.MuMimoMaxPairLayer parameter. To enable
this function, set this parameter to SIXTEEN_LAYERS.
This feature enables an eNodeB to pair 2 to 16 UEs working in TM9 for MU-MIMO. Up to 16 data
streams can be transmitted using the same OFDM time-frequency resource. When this feature is
enabled, the eNodeB performs the following operations:
1. Determines the UEs to be paired and the number of data streams to be transmitted to each
UE based on the UE pairing conditions.
2. Generates the weight values for data streams.
3. Imposes weight on data symbols and DM-RS symbols on each data stream based on the
generated weight values.
4. Combines these symbols and then transmits data over antenna ports.
With this feature, multiple data streams are transmitted using the same time-frequency resource,
beamforming is implemented on the data streams, and interference is mitigated between the
streams, thereby increasing the downlink spectral efficiency.
Adaptive SRS Resource Allocation

This function is controlled by the MM_SRS_ALLOC_OPT_SWITCH option of the
ENodeBAlgoSwitch.UlResManageOptSw parameter and the
CellSrsAdaptiveCfg.SrsPeriodAdaptive parameter.
Without this function, UE-specific SRS periods cannot change with the number of UEs in massive
MIMO cells with DMB enabled, which may affect network performance. With this function, an
SRS resource pool is generated for massive MIMO cells with DMB enabled. UE-specific SRS
periods in these cells are adaptively configured in the range of 40 ms to 320 ms. If there are a
small number of online UEs, shorter SRS periods are configured. As the number of admitted UEs
increases, the SRS periods are gradually increased.
Codebook Subset Adaptation

This function is controlled by the MASSIVE_MIMO_MU_RANK_OPT_SW option of the
CellMimoParaCfg.MimoSwitch parameter. Before this function is enabled, the number of
scheduled layers is determined by the RIs reported by UEs.
After this function is enabled, the eNodeB determines the target cell status based on information
such as the current load and pairing statistics, and optimizes the UE-reported codebook subsets
based on the judgment result.
 When the cell load is light and the number of paired layers is small, the eNodeB selects a
larger number of layers for a single UE based on the reported rank. This increases the total
number of spatial multiplexing layers.
 When the cell load is heavy and the number of paired layers is large, the eNodeB selects a
smaller number of layers for a single UE based on the reported rank. This ensures high
utilization of the interference suppression capability on the UE side and improves pairing
efficiency.
Codebook subset adaptation can take effect in DMB and intelligent beam scheduling scenarios.
Maximum-Pairing-Efficiency-based Scheduling
This function is controlled by the CellMimoParaCfg.MuMimoPairingStrategy parameter.
2021-11-30 Page 35 of 105

Before this function is enabled, the scheduling priority and inter-UE interference are considered
during UE pairing. The total post-pairing spectral efficiency is affected by channel information
quantization errors as channel information is reported based on quantized codebooks in an FDD
system. After this function is enabled, the total post-pairing spectral efficiency is considered, in
addition to the scheduling priority and inter-UE interference. This increases the downlink cell
capacity and downlink user-perceived rate.
Maximum-pairing-efficiency-based scheduling can take effect in DMB scenarios.
Adaptive Rank Detection

This function is controlled by the RANK_OPT_DETECTION_SWITCH option of the
SectorSplitGroup.SectorSplitSwitch parameter. Adaptive rank detection is an enhancement to
codebook subset adaptation. This function and codebook subset adaptation cannot be enabled at
the same time.
Before this function is enabled, the eNodeB determines the number of layers based on the RI
reported by the UE. After this function is enabled, the eNodeB determines the target cell status
based on information such as the current load and pairing statistics, and optimizes the UE-
reported codebook subsets based on the target cell status.
 When the cell load is light and the number of paired layers is small, the eNodeB selects a
larger number of layers for a single UE based on the reported rank. This increases the total
number of spatial multiplexing layers.
 When the cell load is heavy and the number of paired layers is large, the eNodeB selects a
smaller number of layers for a single UE based on the reported rank. This ensures high
utilization of the interference suppression capability on the UE side and improves pairing
efficiency.
In addition, the cell changes the codebook subset restriction state every minute and detects
another codebook subset. If the detected state results in an increase in the downlink cell
throughput, the cell remains in this state. If the detected state leads to a decrease in the downlink
cell throughput, the cell rolls back to the original state. During this procedure, the current
codebook subset restriction state is notified to the UE through RRC signaling over the air
interface. As the restriction state changes periodically, the amount of RRC signaling will increase.
Adaptive rank detection can take effect in DMB scenarios.
Adaptive Space-Domain Grouping and Pairing

This function is controlled by the ADAPT_SPATIAL_GROUPING_SWITCH option of the
SectorSplitGroup.SectorSplitSwitch parameter.
Before this function is introduced, UEs are preferentially paired in the frequency domain, from the
lowest to higher layers. This method requires that the start positions of paired UEs be aligned in
the frequency domain. Therefore, if the data packet sizes of paired UEs are inconsistent, there
will be idle resources.
After this function is enabled, UEs are classified into multiple groups based on inter-UE
correlations and then paired on a per group basis. This method does not require that the UE
positions be aligned in the frequency domain and therefore resource waste is eliminated.
Adaptive space-domain grouping and pairing can take effect in DMB scenarios.
2021-11-30 Page 36 of 105

4.1.2 Benefits
System capacity increases considerably in urban areas where there is contiguous coverage.
DMB gains (compared with 2T2R cells served by a three-sector eNodeB) are closely related to
the penetration rate of 3GPP Release10–compliant UEs supporting four-port CSI-RS
transmission and TM9, cell load, whether DMB cells cover a contiguous area, and the UE
distribution within a cell. Feature benefits are most noticeable when all of the following conditions
are met:
 DMB is enabled for cells that provide contiguous coverage.
 The cell load is high.
 The penetration rate of TM9-capable UEs is high.
 UEs are distributed evenly within the cells.
 There is a high percentage of large-packet services in the cells.
 Cell channel quality is stable.
You can use the following counter as a reference for the TM9-capable UE penetration rate.
Counter ID Counter Name Description

1526732723 L.Traffic.User.TM9.Avg(LTE TDD Average number of UEs that apply
eNodeB,LTE FDD eNodeB) TM9 in a cell
4.2 Application Scenarios

DMB 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 70%) or when SMB is not suitable.
DMB is recommended in light-load scenarios because inter-beam interference in SMB mode
causes user experience to be poorer than the baseline.

//Reconfiguring the following information as the RMV CELL command has been executed
//Configuring CPRI connections (in RRU chain or load sharing configuration scenarios)
//RRU chain configuration scenarios

ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=0, HSN=3, HPN=0, CR=AUTO,
//Load sharing configuration scenarios

ADD RRUCHAIN: RCN=0, TT=LOADBALANCE, HSRN=0, HSN=3, HPN=0, TSRN=0, TSN=3, TPN=1, CR=AUTO,
//Adding an AAU, without running the MOD RRUCHAIN command in RRU chain configuration scenarios
ADD RRU: CN=0, SRN=100, SN=0, TP=TRUNK, RCN=0, PS=0, RT=AIRU, RS=LO, RXNUM=32, TXNUM=32,
MNTMODE=NORMAL, RFDCPWROFFALMDETECTSW=OFF, RFTXSIGNDETECTSW=OFF;
2021-11-30 Page 37 of 105

//Adding a sector
ADD SECTOR: SECTORID=100, ANTNUM=0, CREATESECTOREQM=FALSE;
//Adding sector equipment

ADD SECTOREQM: SECTOREQMID=100, SECTORID=100, ANTCFGMODE=BEAM, RRUCN=0, RRUSRN=100, RRUSN=0,
BEAMSHAPE=SEC_120DEG, BEAMLAYERSPLIT=None, BEAMAZIMUTHOFFSET=None;
//Adding baseband equipment

ADD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, SN1=x;
//Adding a cell
//Binding the cell to the sector equipment and baseband equipment, and setting the CELLBEAMMODE parameter
BASEBANDEQMID=0;
//(Optional) Modifying the setting of the cell system information switch (assuming that the cell with LocalCellId set to 100 is a
downlink-only cell)
MOD CELLSIMAP: LocalCellId=100, SiSwitch=ForbidCellSiSwitch-1;
//Adding an operator for the cell

ADD CELLOP:LOCALCELLID=100,TRACKINGAREAID=0,MMECFGNUM=CELL_MME_CFG_NUM_0;
//Setting PA, PB, and RS power (which is denoted by xxx in the following and can be set based on actual network conditions)
//Configuring a sector split group

//Configuring sector split cells. The settings of the AAU5711a/AAU5733/AAU5726 are used as an example. The cell beam tilt
and horizontal beam azimuth offset can be set based on network conditions.
ADD SECTORSPLITCELL: LocalCellId=100, SECTORSPLITGROUPID=0, CELLBEAMINDEX=0, CellBeamTilt=8,
//Setting cell SRS parameters (If the SRSCFG.FddSrsCfgMode parameter is set to DEFAULTMODE, run the following
commands with the SRSCFG.SrsSubframeCfg parameter set as required.)
MOD SRSCFG: LocalCellId=100, SrsCfgInd=BOOLEAN_TRUE, FddSrsCfgMode=DEFAULTMODE,
SrsAlgoOptSwitch=SrsSubframeRecfgOptSwitch-0, SrsSubframeCfg=xx;
MOD CELLSRSADAPTIVECFG: LocalCellId=100, SrsPeriodAdaptive=ON;
MOD ENODEBALGOSWITCH: UlResManageOptSw=MM_SRS_ALLOC_OPT_SWITCH-1;
//(Optional) Setting an SRS measurement threshold for the sector split group so that inaccurate measurement results caused by
poor uplink quality can be discarded when the group experiences severe uplink interference from outside the group
MOD SECTORSPLITGROUP: SectorSplitGroupId=0, Tm9SrsMeasThreshold=-10;
2021-11-30 Page 38 of 105

//(Optional, recommended) Turning on the SRS period adaptation switch (If this switch is turned off, set the
CellSrsAdaptiveCfg.UserSrsPeriod parameter.)
//Activating the cell

//Setting cell-level MIMO parameters

MOD CELLMIMOPARACFG: LocalCellId=100, MuMimoMaxPairLayer=SIXTEEN_LAYERS,
MuMimoWeightAdjStrategy=FULL_ZERO_FORCING;
//Enabling TM9
MOD CELLALGOSWITCH: LocalCellId=100, EnhMIMOSwitch=TM9Switch-1;
//(Optional, recommended) Setting the PRB usage threshold for TM9 to take effect to 0 so that TM9 UEs can enter TM9 earlier
MOD CELLMIMOPARACFG: LocalCellId=110, PrbRatioThldForTm9SuMimo=0;
//Setting CSI-RS-related parameters

MOD CELLCSIRSPARACFG: LocalCellId=100, CsiRsSwitch=ADAPTIVE_CFG, CsiRsPeriod=ms20,
CsiRsAdaptBeamCount=CSI_RS_BEAM_10, CsiRsConfigUserNumTh=1, CsiRsConfigUserRatioTh=1,
CsiRsUnconfigUserRatioTh=0, CsiRsSetJudgeHysTimer=1, CsiRsSetJudgeTimer=1;
MOD CELLDLSCHALGO: LocalCellId=100, CsiRsSfSchStrSwitch=UnconfigCsiRsUeEnDeOrderSchSw-1;
//(Optional, recommended) Turning on the DlCqiAdjDeltaOptSwitch to achieve better performance

//(Optional, recommended) Enabling the frequency-difference-based correction function

//(Optional, recommended) Turning on the CSI adjustment switch to achieve better performance
MOD CELLMIMOPARACFG: LocalCellId=100, MimoSwitch=PRECISE_DL_CSI_SW-1;
//(Optional, recommended) Enabling fast Doppler measurement reporting so that UEs can enter TM9 earlier
MOD CELLULSCHALGO: LocalCellId=100, DopAlgoSwitch=FastReportDopSwitch-1;
//(Optional) Enabling codebook subset adaptation

MOD CELLMIMOPARACFG: LocalCellId=100, MimoSwitch=MASSIVE_MIMO_MU_RANK_OPT_SW-1;
//(Optional) Enabling maximum-pairing-efficiency-based scheduling

MOD CELLMIMOPARACFG: LocalCellId=100, MuMimoPairingStrategy=PAIRING_EFF_FIRST;
//(Optional) Enabling adaptive rank detection

MOD SECTORSPLITGROUP: LocalCellId=100, SectorSplitSwitch=RANK_OPT_DETECTION_SWITCH-1;
//(Optional) Enabling adaptive space-domain group and pairing

MOD SECTORSPLITGROUP: LocalCellId=100, SectorSplitSwitch=ADAPT_SPATIAL_GROUPING_SWITCH-1;

//(Optional) Deactivating adaptive SRS resource allocation
//(Optional) Disabling codebook subset adaptation

MOD CELLMIMOPARACFG: LocalCellId=100, MimoSwitch=MASSIVE_MIMO_MU_RANK_OPT_SW-0;
2021-11-30 Page 39 of 105

//(Optional) Disabling maximum-pairing-efficiency-based scheduling

MOD CELLMIMOPARACFG: LocalCellId=100, MuMimoPairingStrategy=DEFAULT;
//(Optional) Disabling adaptive rank detection

MOD SECTORSPLITGROUP: LocalCellId=100, SectorSplitSwitch=RANK_OPT_DETECTION_SWITCH-0;
//(Optional) Disabling adaptive space-domain group and pairing

MOD SECTORSPLITGROUP: LocalCellId=100, SectorSplitSwitch=ADAPT_SPATIAL_GROUPING_SWITCH-0;
//Deactivation is not involved for other functions.

KPI monitoring is the same as that for SMB. For details, see 3.3.2 KPI Monitoring.
4.3.2.1 Site Selection

In contrast with SMB, the following items need to be considered during site selection for DMB:
1. Hotspot cell identification: The downlink PRB usage is greater than or equal to 70%.
2. Penetration rate of TM9 UEs: A higher penetration rate of TM9 UEs leads to higher gains.
If gain specifications are met, a TM9 UE penetration rate of 70% or more is preferred.
4.3.2.2 Basic RF
When massive MIMO (DMB) is enabled on a network with 2T2R/4T4R cells, it is recommended
that the antenna azimuth and total tilt angle be consistent with those on the original network to
ensure that coverage remains unchanged.
4.3.2.3 Power Configuration

You must be cautious of power configuration because comparison with original network KPIs is
involved during reconstruction from 2T to massive MIMO (DMB). In principle, the performance
should be improved while the coverage remains unchanged.
For details, see the Excel files attached in the corresponding SMB section.

For details, see the corresponding SMB section.
4.3.4.1 Feature License

To use this function, you need to purchase licenses for massive MIMO introduction and 32T32R
massive MIMO package. You are advised to purchase licenses for LOFD-001001, LOFD-001003,
LOFD-001005, and LOFD-001060.
2021-11-30 Page 40 of 105

In DMB mode, downlink 8-layer MU-MIMO requires that TM9 be enabled and the license for
LEOFD-131303 be purchased; downlink 16-layer MU-MIMO requires that TM9 be enabled and
the licenses for LEOFD-131303 and LEOFD-131304 be purchased.

LEOFD-131301 Massive MIMO LT1SMAMIMO01 Per Cell
Introduction
LEOFD-131302 32T32R Massive MIMO LT1S32MAMIMO Per Cell
Package
LOFD-001005 UL 4-Antenna Receive LT1S0U4ARD00 Per Cell
Diversity
LEOFD-131303 DL 8-Layer MU-MIMO LT1S0D8MMIMO Per Cell
LEOFD-131304 DL 16-Layer MU-MIMO LT1SD16MMIMO Per Cell
For more information, see the corresponding SMB section.


4.4 Benefits
Check the status of the cells where DMB is enabled. If the cells are available and any of the
following counters is not 0, DMB has taken effect.

1526739778 L.ChMeas.MUBF.2ndLayer.Pair Average number of PRBs successfully paired for
PRB.Succ layer-2 UEs during MU beamforming
1526739779 L.ChMeas.MUBF.3rdLayer.Pair Average number of PRBs successfully paired for
1526739780 L.ChMeas.MUBF.4thLayer.Pair Average number of PRBs successfully paired for
2021-11-30 Page 41 of 105


1526745731 L.ChMeas.MUBF.10thLayer.Pai Average number of PRBs successfully paired for
rPRB.Succ layer-10 UEs during MU beamforming

You are advised to use traffic KPIs to evaluate the gains of DMB. DTs are not recommended.
4.4.2.1 Gain Specifications

The following table describes the traffic statistics gains for the AAU5711 (in a scatter chart).
Function Baseline for Capacity Average UE Throughput

Comparison Gain Gain
DMB for TM9-capable DL 2x2 150% to 150% to 200%
UEs complying with 3GPP 200%
Release 10
DMB for TM9-capable DL 4x2 110% to 110% to 150%
UEs complying with 3GPP 150%
Release 10
The following table describes the traffic statistics gains for the AAU5711a (in a scatter chart).
2021-11-30 Page 42 of 105

Description Baseline-based Capacity Average UE Throughput

Comparison Gain Gain
DMB for TM9-capable UEs DL 2x2 200% to 200% to 250%
complying with 3GPP 250%
Release 10
DMB for TM9-capable UEs DL 4x2 150% to 150% to 200%
complying with 3GPP 200%
Release 10
NOTE
The traffic and user-perceived rate gains are evaluated based on the right-most point of the trend line in the
scatter chart.
4.4.2.2 Evaluation Method

See 3.4.2 Gain Specifications and Evaluation Methods.

 TM9-incapable UEs experience performance deterioration because of periodic CSI-RS
transmission in the cell when TM9 and this function take effect. The level of the deterioration
is dependent on the TM9-capable UE penetration rate and the CSI-RS period.
 In addition, due to downlink MU-MIMO in TM9, more PDCCH symbols are used in the
downlink. As a result, the failure rate of allocating PDCCH resources to uplink scheduling
increases, and the average uplink UE throughput may decrease.
 Codebook subset adaptation: After this function is enabled, the proportion of high ranks in a
cell decreases because the base station proactively restricts codebook subsets.
 Maximum-pairing-efficiency-based scheduling: After this function is enabled, the proportion
of scheduled cell edge users (CEUs) may decrease in heavy-load scenarios according to
parameter configuration principles. As a result, the experience of CEUs remains unchanged
or slightly deteriorates.
 Adaptive rank detection: This function involves resource reconfiguration for admitted UEs. As
a result, the CPU usage increases during codebook subset detection for these UEs.
 Adaptive space-domain grouping and pairing: none
4.4.4 DT Analysis
DT analysis is the same as that for SMB.

N/A
2021-11-30 Page 43 of 105

5 SCC Supporting TM9

If DMB is enabled for a cell, the cell can provide dedicated traffic beams for many TM9 UEs at the
same time. Different beams can share time-frequency resources to improve capacity. This function
requires the configuration of uplink SRSs for the eNodeB. The eNodeB measures the Reference
Signal Received Power (RSRP) of TM9 beams based on uplink SRS quality and regards the beam
with the largest RSRP value as the target beam of the UE. If uplink CA is not supported or disabled,
an optimal beam cannot be selected because UEs on the SCC do not send SRSs. As a result, these
UEs cannot participate in MU-MIMO. This feature is controlled by the
MM_SCC_TM9_MU_MIMO_SW option of the CellMimoParaCfg.MimoSwitch parameter.
Figure 5-1 Figure1 Massive MIMO for SCells
Massive MIMO for SCells allows UEs in the massive MIMO SCell, which is served by the same AAU
as that serves the massive MIMO PCell and covers the same area as the massive MIMO PCell, to
share the beam selection result of the PCC. This function resolves the issue that UEs on the SCC do
not send SRSs and therefore no optimal beams can be selected for these UEs. This function allows
UEs in the massive MIMO SCell to participate in MU-MIMO. This function improves the spatial
multiplexing gains and spectral efficiency, and increases downlink throughput on the SCC. In heavy-
load scenarios, this function also reduces the network load and improves the user-perceived rate.
The SCC shares the optimal beam results of the PCC. Therefore, this function can be enabled only
when the massive MIMO cells involved in carrier aggregation are set up on the same AAU and cover
the same area. That is, the sector split cells in a sector split group involved in carrier aggregation
must meet the following conditions:
1. They are set up on the same AAU.
2. They have the same setting for the SectorSplitGroup.BeamDeploymentMode parameter.
3. They have the same setting (1 or 2) for the SectorSplitGroup.BeamTemplateId parameter.
 If the SectorSplitGroup.BeamTemplateId parameter is set to 1 for all the sector split cells in a
sector split group, the SectorSplitCell.CellBeamTilt parameter settings of the sector split cells
on the PCC and SCC must be the same.
2021-11-30 Page 44 of 105

 If the SectorSplitGroup.BeamTemplateId parameter is set to 2 for all the sector split cells in a
sector split group, the SectorSplitCell.CellBeamIndex and SectorSplitCell.CellBeamTilt
parameter settings of the sector split cells on the PCC and SCC must be the same.
If a downlink frequency is significantly different from the uplink frequency used for SRS reception,
using the same beam weight will lead to different beam directions for different frequencies. As a
result, there will be an error in downlink beam selection. To address this issue, a correction function
based on the difference between uplink and downlink frequencies is introduced. This function is
controlled by the FREQ_DIFF_AMEND_SW option of the CellMimoParaCfg.MimoSwitch
parameter. After this function is enabled, the eNodeB corrects the downlink beam selection result
based on the frequency difference to improve the accuracy of CSI-RS resource allocation. The
frequency-difference-based correction function applies only to DMB cells or scenarios where the
JOINT_SCHEDULING_SWITCH option of the SectorSplitGroup.IntelligentBeamSchSwitch
parameter is selected.
5.1.2 Benefits
With this feature, UEs on the SCC can enter TM9 mode, multiple data streams are transmitted using
the same time-frequency resource, beam shaping is implemented for data streams, and the data
streams are weighted. In this way, signal interference between data streams is mitigated, and the
downlink spectral efficiency and cell capacity improve.
The larger the spacing between the center frequencies of the PCC and SCC, the lower the user-
perceived rate. It is recommended that this function be enabled when the spacing is less than or
equal to 100 MHz.
The frequency-difference-based correction function improves the accuracy of CSI-RS resource
allocation. When the spacing between the downlink frequency of an SCell and the uplink frequency
of the PCell is greater than 100 MHz, it is recommended that the frequency-difference-based
correction function be enabled in the SCell to improve the accuracy of SCell channel information.
When the spacing between the downlink frequency of an SCell and the uplink frequency of the PCell
is not greater than 100 MHz, the frequency-difference-based correction function achieves lower gains
but has no negative impacts.

DMB is suitable for high-traffic scenarios in urban areas. It is recommended that DMB be enabled
when the penetration rate of TM9-capable UEs is high (for example, over 70%) or when SMB is not
suitable. DMB is also recommended in scenarios where cells with the same configurations and
working on different frequencies are set up on the same AAU and CA is enabled.

//Turning on the MM_SCC_TM9_MU_MIMO_SW for the corresponding SCells
//(Optional) Turning on the frequency-difference-based correction switch for the corresponding cells
2021-11-30 Page 45 of 105


//(Optional) Turning off the frequency-difference-based correction switch for the corresponding cells
//Turning off the MM_SCC_TM9_MU_MIMO_SW for the corresponding SCells


Select sites that meet both the site selection standards for DMB and the conditions in 5.1.1 Definition
and Principles.
Other planning items are the same as those for DMB.

Feature License
To use this feature, you need to purchase licenses for Massive MIMO Introduction, 32T32R Massive
MIMO Package, and massive MIMO for SCells. Massive MIMO for SCells is a subfeature and is
controlled by the license of LEOFD-151316 32T32R Massive MIMO Enhancement Package.

Package
LEOFD-151316 32T32R Massive MIMO LT1SMMIMOS00 Per Cell
Enhancement Package


2021-11-30 Page 46 of 105

5.4 Benefits
Check the status of the SCells where DMB is enabled. If the cells are available and the value of the
following counter is not 0, DMB has taken effect in the SCells.
Counter ID Counter Name

1526747680 L.Traffic.User.SCell.Active.DL.TM9.Avg

You are advised to use traffic KPIs to evaluate the gains of DMB. DTs are not recommended.
Calculate the following KPIs before and after function activation for comparison:
Counters related to activation verification are as follows.

1526728564 L.Thrp.bits.DL.CAUser
1526728565 L.Thrp.Time.DL.CAUser
1526729259 L.CA.Traffic.bits.DL.SCell
1526729004 L.CA.DL.SCell.Act.Dur

The gains on SCC traffic statistics are the same as those for DMB.
5.4.2.2 Evaluation Methods

5.4.3 Network Impacts

 TM9-incapable UEs experience performance deterioration because of periodic CSI-RS
transmission in the SCell when TM9 and this function take effect. The level of the deterioration is
dependent on the TM9-capable UE penetration rate and the CSI-RS period.
 In addition, due to downlink MU-MIMO in TM9, more PDCCH symbols are used in the downlink.
As a result, the failure rate of allocating PDCCH resources to uplink scheduling increases, and
the average uplink UE throughput may decrease.
2021-11-30 Page 47 of 105

5.4.4 DT Analysis
DT analysis is the same as that for SMB.

N/A
6 Intelligent Beam Shaping

In SMB, the number of configured beams, beam direction, and beamwidth are fixed in the baseline
beam file library. However, UE distributions in SMB sectors are different. Intelligent beam shaping
generates the beam direction and beamwidth online based on UE distributions in the SMB coverage
area, and adjusts the beam power based on the changed beam direction or beamwidth. This feature
improves the user-perceived rate in sectors.
Figure 6-1 Intelligent beam shaping
2021-11-30 Page 48 of 105

Beam adjustment is divided into static adjustment and dynamic adjustment.
Static Adjustment
− Azimuth
The mechanical azimuth of the antenna is used as the normal. The azimuth is a positive
number for clockwise deviation from the normal or a negative number for counterclockwise
deviation from the normal.
The value range is -60 to 60. Generally, the angle between beams must be greater than 24°.
− Beamwidth
The beamwidth of each cell can be adjusted based on the coverage requirement. The
supported beamwidths are 15°, 18°, 21°, 26°, 34°, 45°, and 70°.
− Power
Each cell can be configured with different power as long as the total power of the cells does
in the sector not exceed the sector power.
2021-11-30 Page 49 of 105

Automatic Horizontal Adjustment
Automatic Vertical Adjustment Based on MAE CCO

MAE-based LTE downlink coverage optimization increases the cell level, cell quality, and
CQIs to improve the coverage performance. It improves network KPIs such as the cell
service drop rate, access success rate, traffic volume, and UE throughput.
After pattern adjustment is enabled, MAE adjusts the tilts and azimuths in serial mode. For
details, see LTE CCO Feature Operation User Guide, which contains LTE DL Coverage
Optimization.
2021-11-30 Page 50 of 105

Beam Number Adjustment

When three or four beams are deployed for SMB and network load is light, there is pilot
interference between cells and therefore the user-perceived rate is lower than that when one
or two beams are deployed. To address this issue, beam number adjustment is introduced, as
shown in the following figure. When network load is heavy, the number of beams is increased
to improve network capacity. When network load is light, the number of beams is reduced to
improve user experience. Beam number adjustment is controlled by the
BEAM_NUM_ADJ_SWITCH option of the SectorSplitGroup.SectorSplitSwitch parameter.
The number of beams is adjusted based on the following 7 (days) x 24 (hours) beam number
status table, which can be imported or automatically generated using an algorithm.
No. Sun. Mon. Tue. Wed. Thur. Fri. Sat.
0 4 4 4 4 4 4 4
1 4 4 4 4 4 4 4
2 1 1 1 1 1 4 4
3 1 1 1 1 1 4 4
4 1 1 1 1 1 1 1
5 1 1 1 1 1 1 1
6 1 1 1 1 1 1 1
2021-11-30 Page 51 of 105

No. Sun. Mon. Tue. Wed. Thur. Fri. Sat.
7 2 2 2 2 2 1 1
8 2 2 2 2 2 1 1
9 2 2 2 2 2 1 1
10 2 2 2 2 2 1 1
11 2 2 2 2 2 2 2
12 2 2 2 2 2 2 2
13 2 2 2 2 2 2 2
14 2 2 2 2 2 2 2
15 2 2 2 2 2 2 2
16 2 2 2 2 2 2 2
17 2 2 2 2 2 2 2
18 4 4 4 4 4 4 4
19 4 4 4 4 4 4 4
20 4 4 4 4 4 4 4
21 4 4 4 4 4 4 4
22 4 4 4 4 4 4 4
23 4 4 4 4 4 4 4
The 7x24 status table is refreshed based on the actual traffic volume after initial parameters
are planned, beam number adjustment is enabled, and the
BeamNumAdjAlgo.BeamNumAdjMode parameter is not set to TABLE_MODE.
The following shows the status table update mode.
2021-11-30 Page 52 of 105

The base station checks whether the number of beams in the current hour is the same as
that in the next hour according to the 7x24 status table. If inconsistent, the base station
prohibits access to the sector split cells, transfers UEs to other cells through inter-frequency
handover, and then adjusts the number of beams. After the cells are restored, UEs can be
admitted or handed over to these cells again. Sector split groups with different beams as well
as sector split cells are configured in the MOs SectorSplitGroup, SectorSplitCell,
SectorSplitGroupExt, and SectorSplitCellExt.
When the beam number adjustment function is enabled and the
BeamNumAdjAlgo.BeamNumAdjMode parameter is set to TABLE_MODE, the
BeamNumAdjAlgo.BeamNumAdjTable parameter is set to 168 characters, which indicate
the numbers of beams in 7 x 24 hours. The start time is 00:00:00 every Sunday. Each
character can be 0, 1, 2, 3, or 4. The value 0 indicates that the baseline number of beams is
used. The value 1, 2, 3, or 4 indicates that the number of sector split beams specified by the
SectorSplitGroupExt.SectorSplitBeamNum parameter is used.
The static table can be generated by the WINS tool.

http://winscloud.huawei.com/
For the operation guide, see WINS Cloud Product Solution GTM Toolkit Delivery Guide.
2021-11-30 Page 53 of 105

2021-11-30 Page 54 of 105

Intelligent Beam Shaping Task

The MM_INTELLIGENT_BEAM_SHAPING_SW option of the SectorSplitGroup.SectorSplitSwitch
parameter specifies whether to enable intelligent beam shaping. If the
MM_INTELLIGENT_BEAM_SHAPING_SW option is deselected, all the sub-functions of intelligent
beam shaping are disabled, and SMB uses the weight file of the beam weight database in the
eNodeB software package. If this option is selected, you can select associated options under the
SectorSplitGroup.SectorSplitSwitch parameter to enable corresponding sub-functions of intelligent
beam shaping.
If... Then...
The The pattern adjustment function is enabled. The weight file of the
PATTERN_ADJ_SWI beam weight database in the eNodeB software package
TCH option is automatically becomes invalid. The eNodeB generates the static
selected beam weight file and power configuration online based on the real-
time UE distribution in a cell. The shortest period for beam
2021-11-30 Page 55 of 105

If... Then...
adjustment is 1 hour.
The SectorSplitGroup.MmBeamAzimuthAdjStep parameter
specifies the step for adjusting the beam azimuth.
The The pattern adjustment function is disabled. The eNodeB generates
PATTERN_ADJ_SWI a static beam weight file based on the beam direction and beam
TCH option is width set for the split sector.
deselected ●
The beam direction in the sector is specified by the
SectorSplitCell.CellBeamAzimuth parameter. If this parameter
is set to 255, the direction configured in the sector beam weight
database is used.
●
The beamwidth in the sector is specified by the
SectorSplitCell.CellBeamwidth parameter. If this parameter is
set to INVALID, the beamwidth configured in the sector beam
weight database is used.
The The power adjustment function is enabled. The eNodeB adaptively
POWER_ADJ_SWIT adjusts the values of the PDSCHCfg.ReferenceSignalPwr,
CH option is selected CellDlpcPdschPa.PaPcOff, and PDSCHCfg.Pb parameters for the
beam based on the principle that the beam coverage remains
unchanged before and after the adjustment. If the beam coverage
after the adjustment is still greater than that before the adjustment,
the remaining beam power is allocated to CEUs to improve the
transmission rate for them. The
SectorSplitCell.CellBeamPowerOffset parameter specifies the
CRS transmit power offset relative to the power before the
adjustment for a split sector.
The The power adjustment function is disabled. The eNodeB does not
POWER_ADJ_SWIT adjust the power allocated to CRSs and data transmission.
CH option is
deselected
The The pattern adjustment enhancement function is enabled. It
PATTERN_ADJ_EN enhances the performance of changing the main lobe direction of a
H_SWITCH option is multi- or single-frequency sector split cell based on UE distribution
selected and increases user-perceived data rates in the massive MIMO cell.
The The pattern adjustment enhancement function is disabled.
PATTERN_ADJ_EN
H_SWITCH option is
deselected
The The power allocation function is enabled. The reference signal power
POWER_ALLOCATI specified by the PDSCHCFG.ReferenceSignalPwr parameter
ON_SWITCH option becomes invalid. In this case, the reference signal power is
is selected. determined by the base station based on the cell power specified by
the SectorSplitCell.CellBeamPower parameter, and can be queried
using the DSP INTELLIGENTBEAMSHAPINGPWR command.
2021-11-30 Page 56 of 105

If... Then...
The The power allocation function is disabled.
POWER_ALLOCATI
ON_SWITCH option
is deselected.
To evaluate the gains of the PATTERN_ADJ_SWITCH, POWER_ADJ_SWITCH, and

PATTERN_ADJ_ENH_SWITCH options of the SectorSplitGroup.SectorSplitSwitch parameter, an
intelligent beam shaping task can be started using the STR INTELLIGENTBEAMSHAPING
command. The task period is two weeks. After the task is completed, if the gains estimated by the
intelligent beam shaping task are greater than the SectorSplitGroup.UserExpGainBHThreshold
and SectorSplitGroup.UserExpGainLHThreshold parameter values, the corresponding options
have taken effect. Otherwise, the corresponding options have not taken effect.
Figure 6-2 Task procedure
2021-11-30 Page 57 of 105

Figure 6-3 Gain evaluation
After an intelligent beam shaping task is started, it will be stopped if any of the following conditions is
met:
 The STP INTELLIGENTBEAMSHAPING command is executed.
 The switch setting of any of the following functions is changed: massive MIMO intelligent beam
shaping, pattern adjustment, power adjustment, pattern adjustment enhancement, and beam
number adjustment.
 The value of SectorSplitCell.CellBeamAzimuth or SectorSplitCell.CellBeamwidth is
changed. The value of SectorSplitCellExt.CellBeamAzimuth or
SectorSplitCellExt.CellBeamwidth is changed after beam number adjustment is enabled.
 The base station restarts, the main control board is reset, or the APP is reset.
 The ADD SECTORSPLITCELLEXT command is executed after beam number adjustment is
enabled.
After an intelligent beam shaping task is started, it will restart if any of the following conditions is met:
 The value of SectorSplitCell.CellBeamAzimuthOffset is changed.
 The value of SectorSplitCellExt.CellBeamAzimuthOffset is changed after beam adjustment is
enabled.
After an intelligent beam shaping task is started, pattern adjustment, power adjustment, or pattern
adjustment enhancement defined in the task takes effect one week later. Pattern adjustment or its
enhancement defined in the task can take effect only when all of the following conditions are met:
 The SectorSplitCell.CellBeamAzimuth parameter is set to 255.
 The SectorSplitCell.CellBeamwidth parameter is set to INVALID.
 The SectorSplitCellExt.CellBeamAzimuth parameter is set to 255 after beam number
adjustment is enabled.
2021-11-30 Page 58 of 105

 The SectorSplitCellExt.CellBeamwidth parameter is set to INVALID after beam number

adjustment is enabled.
After an intelligent beam shaping task is started, pattern adjustment enhancement defined in the task
can take effect only when one of the following conditions is met:
 Pattern adjustment has been enabled for the sector split group.
 Pattern adjustment has taken effect in the task.
Note:

If the PATTERN_ADJ_SWITCH option of the SectorSplitGroup.SectorSplitSwitch parameter is selected, there
will be changes in the effective reference signal power as well as the PA and PB values used when even power
allocation is applied to the PDSCH. The corresponding values can be queried using the DSP
MASSIVEMIMOPOWER command.

If the beamwidth of a sector changes, the eNodeB adaptively adjusts the value of the
PDSCHCfg.ReferenceSignalPwr parameter of the beam based on the principle that the beam coverage remains
unchanged before and after the adjustment.

The intelligent beam shaping task estimates the gains only based on one-hour or half-hour traffic statistics
subscribed on the OSS.
Base-Station-Level Joint Pattern Adjustment

The following situations may occur when SMB is deployed:
 When UEs are distributed in sector boundary areas, the pattern adjustment function cannot
adjust the beams to the optimal state as it takes effect within sectors.
 Loads are unbalanced among sectors. Specifically, heavily loaded sectors have insufficient
resources while lightly loaded sectors have many unused resources. As a result, the overall
resource usage is low, affecting user experience in heavily loaded sectors and the downlink
traffic volume.
The base-station-level joint pattern adjustment function is introduced to address these issues. With
this function, multiple sectors form an adjustment set and the base station adjusts the sector
coverage scope based on the UE distribution per adjustment set. The coverage scope of heavy-load
sectors is narrowed to reduce the number of UEs and network load in them, while the coverage
scope of light-load sectors is expanded to offload UEs from heavy-load sectors. This improves
resource utilization and base-station-level downlink user experience.
This function is controlled by the JOINT_PATTERN_ADJ_SW option of the
SectorSplitGroup.SectorSplitSwitch parameter. If this option is selected, the
Sector.ANTAZIMUTH parameter must be set to a value other than the default value 65535 for each
sector.
This function takes effect when all the following conditions are met:
 The switch of this function is turned on.
 The sector split groups are configured with the same joint pattern adjustment set ID (specified by
the SectorSplitGroup.JointPatternAdjSetId parameter), and the ID is not 255.
 Same frequencies are configured for the sector split groups that have the same joint pattern
adjustment set ID.
 The switch for beam number adjustment is turned off.
2021-11-30 Page 59 of 105

This function is recommended in the following scenarios:

 The sector split groups involved in joint adjustment are adjacent sectors at the same physical
site. Joint adjustment cannot be performed among sectors that are located at different physical
sites.
 This function applies only to two-sector or three-sector scenarios. If three sectors are involved,
the three sectors must be adjacent to each other to provide 360-degree coverage.
When base-station-level joint pattern adjustment takes effect, static pattern adjustment
configurations, including the beamwidth and beam azimuth, do not take effect.
After this function is enabled for the first time or is enabled after being disabled, the base station
starts to collect UE location data in its coverage area. It performs adjustment initially after 48 hours of
data collection and then performs adjustment at intervals specified by the
SectorSplitGroup.JointPatternAdjPeriod parameter. The base station clears the collected UE
location data and restarts this function if any of the conditions listed below is met. In this case, the
default sector boundary setting is used for AAUs in the base station and cells served by the AAUs
use the baseline beam weights and power configuration.
 The value of the SectorSplitCellExt.SectorSplitGroupId,
SectorSplitGroup.BeamTemplateId, or SectorSplitGroup.BeamDeploymentMode parameter
changes for an AAU.
 The value of the SectorSplitCellExt.CellBeamTilt parameter changes for a cell served by an
AAU.
 The value of the SectorSplitCellExt.CellBeamIndex, Cell.DlEarfcn, Cell.UlEarfcn, or
Cell.CrsPortNum parameter changes for a cell served by an AAU.
 The setting of the JOINT_PATTERN_ADJ_SW option of the
SectorSplitGroup.SectorSplitSwitch parameter or the value of the
SectorSplitGroup.JointPatternAdjSetId parameter changes for an AAU.
 The number of beams or the value of the SectorSplitCell.CellBeamwidth parameter changes
for a cell served by an AAU.

If the cell is restarted due to version upgrade or power-off, the adjustment result before the restart is used.

If a cell is automatically deactivated due to reasons such as energy saving and intermittent disconnection
(not including cell deactivation caused by DEA CELL execution), the collected UE location data will be
retained for 24 hours after the deactivation. Data will be cleared after 24 hours and be collected again after
the cell recovers.
6.1.2 Benefits
If intelligent beam shaping is enabled for SMB cells, the user-perceived rate in these cells can be
improved.
More unevenly distributed UEs among split cells and a larger distance between UEs and the antenna
normal line lead to more gains. Less unevenly distributed UEs among split cells and a smaller
distance between UEs and the antenna normal line lead to fewer gains.
When there are three or four baseline beams, enabling beam number adjustment can increase the
user-perceived rate in light-load scenarios. When there are one or two baseline beams, enabling
beam number adjustment can increase the user-perceived rate in heavy-load scenarios.
2021-11-30 Page 60 of 105

Base-station-level joint pattern adjustment improves the downlink user-perceived rate of the base
station if the following baseline conditions are met: (1) the number of beams is three or four; (2) the
number of UEs is imbalanced between sectors, or UEs are concentrated at sector boundaries. In
heavy-load cells, the number of UEs decreases, the downlink traffic decreases, and the downlink
user-perceived rate increases. In light-load cells, the number of UEs increases, the downlink traffic
increases, and the downlink user-perceived rate decreases.

6.2.1 Pattern Adjustment and Its Enhancement
Three or four beams are configured for SMB according to the following tables.
Table 6-1 Number of beams in the inner and outer circles supported by each sector split group
(AAU5711a/AAU5733/AAU5726)
Beam BeamDeploymentMode BeamDeploymentMode BeamDeploymentMode
Template ID Set to MODE_0 Set to MODE_1 Set to MODE_2
1 Not supported Not supported Not supported
2 Not supported Outer circle: 2 Not supported
Outer circle: 3
Outer circle: 4
Intelligent beam shaping also applies to scenarios where UEs are unevenly distributed in the
coverage area of SMBs.
6.2.2 Beam Number Adjustment

 Network load in busy hours differs greatly from that in off-peak hours. The user-perceived rate is
expected to increase during off-peak hours.
 The static table can be used when the network load is stable for a long time or the customer
expects to adjust the number of beams within a specified period.
 Dynamic adjustment is recommended when the network load is changing. In this case, you are
advised to set the beam number adjustment mode to ADAPTIVE_MODE_1_4 or
ADAPTIVE_MODE_2_4 so that the base station can adjust the beam number table based on
the actual network load.
6.2.3 Base-Station-Level Joint Pattern Adjustment

The number of UEs is imbalanced between sectors, or UEs are concentrated at sector boundaries. In
such scenarios, base-station-level joint pattern adjustment brings higher gains than intra-sector
pattern adjustment, as the latter cannot coordinate the beams of other sectors for adjustment.
2021-11-30 Page 61 of 105


 Dynamic adjustment for intelligent beam shaping
//(Only for the UMPTe and UMPTga) Setting the service mode and resetting the application for the configuration to take effect.
(The AID parameter value can be queried by running the DSP APP command. The following uses x as an example.)
MOD ENODEBRESMODEALGO: ServiceMode=AI_ENHANCEMENT_SWITCH-1;
RST APP: AID=x;
//Setting SRS-related parameters

MOD SRSCFG: LocalCellId=100, SrsCfgInd=BOOLEAN_TRUE, FddSrsCfgMode=DEFAULTMODE, SrsSubframeCfg=SC3;
MOD CELLALGOSWITCH: LocalCellId=100, SrsAlgoSwitch=SrsSubframeRecfSwitch-1;
//(Optional) Configuring the massive MIMO beam azimuth adjustment step

MOD SECTORSPLITGROUP: SectorSplitGroupId=0, MmBeamAzimuthAdjStep=60;
//Enabling method 1: Turning on the intelligent beam shaping switch for the sector split group
MOD SECTORSPLITGROUP: SectorSplitGroupId=0, SectorSplitSwitch=MM_INTELLIGENT_BEAM_SHAPING_SW-
1&PATTERN_ADJ_SWITCH-1&PATTERN_ADJ_ENH_SWITCH-1, MmBeamAzimuthAdjStep=60;
//Enabling method 2: Starting an intelligent beam shaping task for the split sector group and checking whether the specified
options bring gains. After the task is complete, if the gains are greater than the values of
SectorSplitGroup.UserExpGainBHThreshold and SectorSplitGroup.UserExpGainLHThreshold, the options bring gains.
Otherwise, the options do not bring gains.
MOD SECTORSPLITGROUP: SectorSplitGroupId=0, SectorSplitSwitch=MM_INTELLIGENT_BEAM_SHAPING_SW-1,
MmBeamAzimuthAdjStep=60;
STR INTELLIGENTBEAMSHAPING: SectorSplitGroupId=0, IntelliBeamShapingTask=PATTERN_ADJ_SWITCH-1
&PATTERN_ADJ_ENH_SWITCH-1, UserExpGainBHThreshold=0, UserExpGainLHThreshold=0;
 Static adjustment for intelligent beam shaping
//(Optional) Setting cell beam power values
1&POWER_ALLOCATION_SWITCH-1;
MOD SECTORSPLITCELL: LocalCellId=100, CellBeamPower=540;
//(Optional) Setting cell azimuths and beamwidths

MOD SECTORSPLITGROUP: SectorSplitGroupId=0, SectorSplitSwitch=MM_INTELLIGENT_BEAM_SHAPING_SW-1;
2021-11-30 Page 62 of 105

MOD SECTORSPLITCELL: LocalCellId=100, CellBeamAzimuth=-42, CellBeamwidth=BEAM_WIDTH_18_DEGREE;

MOD SECTORSPLITCELL: LocalCellId=101, CellBeamAzimuth=-12, CellBeamwidth=BEAM_WIDTH_18_DEGREE;
MOD SECTORSPLITCELL: LocalCellId=102, CellBeamAzimuth=12, CellBeamwidth=BEAM_WIDTH_18_DEGREE;
MOD SECTORSPLITCELL: LocalCellId=103, CellBeamAzimuth=42, CellBeamwidth=BEAM_WIDTH_18_DEGREE;
 Beam number adjustment for intelligent beam shaping

//(Optional) Setting extension parameters for a sector split group and sector split cells
ADD SECTORSPLITGROUPEXT: SectorSplitGroupId=1, SectorSplitBeamNum=2,
TM4WeightScheme=COVERAGE_MODE_2;
ADD SECTORSPLITCELLEXT: LocalCellId=1, SectorSplitGroupId=1, SectorSplitBeamNum=1, CellBeamIndex=0,
CellBeamTilt=6, CellBeamAzimuthOffset=0, CellBeamAzimuth=255,
CellBeamPower=200,MuMimoMaxPairLayer=FOUR_LAYERS, PaPcOff=DB1_P_A, Pb=2;
ADD SECTORSPLITCELLEXT: LocalCellId=2, SectorSplitGroupId=1, SectorSplitBeamNum=1, CellBeamIndex=1,
CellBeamTilt=6, CellBeamAzimuthOffset=0, CellBeamAzimuth=255, CellBeamPower=200,
MuMimoMaxPairLayer=FOUR_LAYERS, PaPcOff=DB1_P_A, Pb=2;
//Non-static table mode

MOD BEAMNUMADJALGO: SectorSplitGroupId=13, BeamNumAdjMode=ADAPTIVE_MODE_2_4,RemainingUeNum=4,
TrafficVariationThld=20, UeNumVariationThld=20;
//Static table mode

MOD BEAMNUMADJALGO: SectorSplitGroupId=0, BeamNumAdjMode=TABLE_MODE,
BeamNumAdjTable="12441244124412441244124412441244124412441244124412441244124412441244124412441244124
4124412441244124412441244124412441244124412441244124412441244124412441244124412441244";
//Setting cell SRS parameters by running the following commands if the SRSCFG.FddSrsCfgMode parameter is set to
DEFAULTMODE
MOD SRSCFG: LocalCellId=100, SrsSubframeCfg=SC3, SrsCfgInd=BOOLEAN_TRUE, FddSrsCfgMode=DEFAULTMODE;
//Enabling beam number adjustment

1&POWER_ALLOCATION_SWITCH-1&BEAM_NUM_ADJ_SWITCH-1;
 Base-station-level joint pattern adjustment

//(Only for the UMPTe and UMPTga) Setting the service mode, and resetting the application for the configuration to take effect
(where the AID parameter value, for example, x, can be queried by running the DSP APP command)
RST APP: AID=x;
2021-11-30 Page 63 of 105

//Configuring SRS-related parameters. (The following uses one split group as an example. Repeat this step for each split group
for which base-station-level joint pattern adjustment needs to be enabled.)
//(Optional) Running the following commands in FDD+TDD networking scenarios (not in FDD-only scenarios). (The following
uses one split group as an example. Repeat this step for each split group for which base-station-level joint pattern adjustment
needs to be enabled.)
MOD SRSCFG: LocalCellId=100, SrsAlgoOptSwitch=SrsSubframeRecfgOptSwitch-1;
//Configuring base-station-level joint pattern adjustment group IDs and adjustment periods
MOD SECTORSPLITGROUP: SectorSplitGroupId=0, JointPatternAdjSetId=0, JointPatternAdjPeriod=4;
//Configuring antenna azimuths based on site requirements

MOD SECTOR: SECTORID=0, ANTAZIMUTH=XX;
//Turning on the intelligent beam shaping switch and base-station-level joint pattern adjustment switch for the sector split
groups
1&JOINT_PATTERN_ADJ_SW-1;

 Dynamic adjustment for intelligent beam shaping
//Turning off the feature switch
0&PATTERN_ADJ_SWITCH-0&PATTERN_ADJ_ENH_SWITCH-0;
//Restoring the SRS-related parameter settings. The following parameter values are used as an example.
MOD SRSCFG: LocalCellId=100, SrsCfgInd=BOOLEAN_TRUE, FddSrsCfgMode=ADAPTIVEMODE, SrsSubframeCfg=SC3;
2021-11-30 Page 64 of 105


//(Only for the UMPTe and UMPTga) Restoring the service mode
 Static adjustment for intelligent beam shaping
//Setting cell beam powers and turning off the feature switches
0&POWER_ALLOCATION_SWITCH-0;
//Setting cell azimuths and beamwidths and turning off the feature switch
MOD SECTORSPLITCELL: LocalCellId=100, CellBeamAzimuth=255, CellBeamwidth=DEFAULT;
MOD SECTORSPLITGROUP: SectorSplitGroupId=0, SectorSplitSwitch=MM_INTELLIGENT_BEAM_SHAPING_SW-0;
 Beam number adjustment for intelligent beam shaping
//Disabling beam number adjustment
0&POWER_ALLOCATION_SWITCH-0&BEAM_NUM_ADJ_SWITCH-0;
//Removing the settings of extension parameters for the sector split cells and sector split group
RMV SECTORSPLITCELL: LocalCellId=1, SectorSplitGroupId=1, SectorSplitBeamNum=2;
RMV SECTORSPLITCELL: LocalCellId=2, SectorSplitGroupId=1, SectorSplitBeamNum=2;
RMV SECTORSPLITGROUPEXT: SectorSplitGroupId=1, SectorSplitBeamNum=2;
 Base-station-level joint pattern adjustment
//Turning off the base-station-level joint pattern adjustment switch
//Restoring the SRS-related parameter settings. If these parameter settings are required by other functions, skip this step. The
following uses only one sector split group as an example. Repeat this step for other groups.
2021-11-30 Page 65 of 105


//(Optional) Running the following commands in FDD+TDD networking scenarios (not in FDD-only scenarios). If these
parameter settings are required by other functions, skip this step. The following uses only one sector split group as an
example. Repeat this step for other groups.
//(Only for the UMPTe and UMPTga) Restoring the service mode. If these parameter settings are required by other functions,
skip this step.


N/A

For details, see the corresponding SMB section. This function requires the UMPTe or later.
6.3.4.1 Feature License

To use this function, you need to purchase licenses for massive MIMO introduction, 32T32R massive
MIMO package, and intelligent beam shaping.
You are advised to purchase licenses for LOFD-001001, LOFD-001003, LOFD-001005, and LOFD-
001060.

Introduction
2021-11-30 Page 66 of 105


Package
Diversity
LNOFD-151301 Intelligent Beam Shaping LT1S00SSBF00 Per
SectorSplitGroup
NOTE
One license unit is required for each sector split group.

N/A

6.4 Benefits
1. Run the DSP CELL command to query the value of Work Status of a cell in which SMB is
configured. If the value is Normal, SMB has been enabled.
2. Run the LST SECTORSPLITGROUP command to query the settings of the
MM_INTELLIGENT_BEAM_SHAPING_SW, PatternAdjSwitch,
PATTERN_ADJ_ENH_SWITCH, POWER_ALLOCATION_SWITCH, and
POWER_ADJ_SWITCH options of the Sector Split Switch parameter to check whether the
corresponding functions have been enabled.
3. If the PatternAdjSwitch or PATTERN_ADJ_ENH_SWITCH is turned on, observe the value of
the L.ChMeas.IntelligentBeamShaping.PatternAdjust.Dur counter. If the value is not 0, the
function has taken effect.
4. If the POWER_ALLOCATION_SWITCH or POWER_ADJ_SWITCH is turned on, run the DSP
MASSIVEMIMOPOWER command to query the configured cell beam power, the effective
reference signal power, and the PA and PB values used when even power allocation is applied
to the PDSCH.
5. If the beam azimuth and width are statically configured for a sector split cell, run the LST
SECTORSPLITCELL command to query the configuration.
6. After an intelligent beam shaping task is started or the base-station-level joint pattern adjustment
switch is turned on, you can run the DSP INTELLIGENTBEAMSHAPING command to check the
running status of the task.
2021-11-30 Page 67 of 105

7. If the beam number adjustment switch is turned on, you can run the DSP BEAMNUMADJALGO
command to query the adjustment status.
----End

You are advised to use traffic KPIs to evaluate the gains of intelligent beam shaping. DTs are not
recommended.

The efficiency of massive MIMO deployment and optimization improves.
The average downlink user-perceived rate of the sector increases by 5% to 20%.
The average uplink user-perceived rate of the sector increases by 1% to 10%.
In light-load scenarios, the user-perceived rate increases by 20% when the number of beams is
adjusted from four to one.


If UEs in split cells generated through SMB are evenly distributed, the downlink user-perceived rate
does not increase, and the uplink user-perceived rate decreases slightly if the number of UEs is less
than 150.
6.4.4 DT Analysis
This feature triggers beam adjustment every hour. Therefore, you are not advised to conduct DTs to
analyze feature gains.

N/A
2021-11-30 Page 68 of 105

7 Intelligent Beam Scheduling

SMB provides a fixed beam for each sector split cell. It does not provide dedicated traffic beams for
TM9 UEs, limiting the beamforming gains and spatial multiplexing gains for TM9 UEs. DMB provides
dedicated traffic beams for TM9 UEs. However, its capacity gains depend on a high proportion of
TM9 UEs. TM9-incapable UEs cannot obtain spatial multiplexing gains. Intelligent beam scheduling
is introduced as an integrated solution to offer SMB and DMB gains at the same time.
Intelligent beam scheduling, based on SMB, provides dedicated traffic beams for TM9 UEs to
improve beamforming gains. It also supports joint scheduling between different beams, improving the
user-perceived rates in sectors.
Figure 7-1 Intelligent beam scheduling
Intelligent beam scheduling provides the following functions:

 Beamforming: DMB is used for TM9 UEs to obtain higher beamforming gains.
In each SMB cell, appropriate narrow beams can be selected for TM9 UEs based on their
locations to obtain beamforming gains.
 Joint scheduling: power sharing + spatial multiplexing
 Power sharing is used between beams in a sector split group. After scheduling, the
remaining power can be allocated to TM9 UEs or TM4 QPSK UEs, improving the spectral
efficiency of UEs.
 MU-MIMO significantly improves spectral efficiency, cell capacity, and user experience.
 SMB is used for TM4, and DMB is used for TM9.
 Spatial multiplexing increases the number of DMRS ports and PDCCH capacity.
2021-11-30 Page 69 of 105

Figure 7-2 TM9 beamforming + power sharing
Figure 7-3 TM4 power sharing
Intelligent beam scheduling is controlled by the JOINT_SCHEDULING_SWITCH option of the

SectorSplitGroup.IntelligentBeamSchSwitch parameter. Enhanced intelligent beam scheduling is
controlled by the ENH_JOINT_SCHEDULING_SWITCH option of the
SectorSplitGroup.IntelligentBeamSchSwitch parameter. To provide dedicated traffic beams for
TM9 UEs, the following TM9-related parameters also need to be set:
 CSI-RS-related parameters such as CellCsiRsParaCfg.CsiRsSwitch and
CellCsiRsParaCfg.CsiRsPeriod: used to configure measurement signals for TM9 UEs.
 CellDlSchAlgo.CsiRsSfSchStrSwitch: used to enable TM9-incapable UEs to be scheduled in
CSI-RS subframes with smaller MCS indexes, improving user experience.
 SRS-related parameters such as SRSCfg.SrsCfgInd and SRSCfg.FddSrsCfgMode: used to
select appropriate dedicated beams for TM9 UEs.
TM9 Beam Optimization

As the penetration rate of TM9 UEs increases, TM9 beam optimization is introduced to coordinate
interference between TM9 UEs and between TM9 and TM4 UEs to continuously improve the overall
network performance. TM9 beam optimization takes effect when enhanced intelligent beam
scheduling is enabled and the PRB usage of the sector split group exceeds the threshold specified
by the SectorSplitGroup.BeamOptPrbUsageThld parameter.
 This function takes effect only when the PRB usage of the sector split group is greater than the
threshold for 10 consecutive minutes.
 After this function takes effect, TM9 beam in SMB cells need be controlled to reduce the
interference generated by TM9 beams and improve the overall performance.
2021-11-30 Page 70 of 105

Figure 7-4 Adaptive TM9 beam optimization
 After this function takes effect, the scheduler changes TM9 beams in each TTI to ensure that the
interference levels are lower than the threshold and the beams with relatively strong signals are
selected for TM9 UEs.
Figure 7-5 TTI-level TM9 beam reselection after TM9 beam optimization takes effect
It is recommended that the CellCsiRsParaCfg.CsiRsSwitch parameter be set to ADAPTIVE_CFG

and the CellCsiRsParaCfg.CsiRsAdaptBeamCount parameter be set to CSI_RS_BEAM_6. When
the penetration rate of TM9 UEs is lower than 10%, the number of CSI-RS beams for TM9 can be
decreased to prevent the impact on the performance of TM9-incapable UEs.
2021-11-30 Page 71 of 105

Inter-Carrier Power Sharing

Inter-carrier power sharing is introduced to intelligent beam scheduling in eRAN17.0. Multiple sector
split groups on the same multi-band AAU can share power, which further improves power utilization
and downlink user experience. A carrier can share a maximum of 50% of its power with others. A
carrier can receive a maximum of 50% of its power from others. Inter-carrier power sharing is
controlled by the INTER_CARRIER_PWR_SHR_SWITCH option of the
SectorSplitGroup.IntelligentBeamSchSwitch parameter.
CFI Adaptation
Power sharing requires that the number of PDCCH symbols in a cell that shares its power with
another cell be less than or equal to that in the cell that receives the shared power. If the PDSCH is
heavily loaded but the PDCCH is lightly loaded in the cell that requires the shared power, CFI
adaptation can be used in eRAN17.0. This function automatically increases the number of PDCCH
symbols by setting the CFI so that the cell can obtain more shared power, improving downlink user
experience. This function is controlled by the PWR_SHR_CFI_ADJ_SWITCH option of the
Mobility Evaluation
For TM9-capable UEs, mobility evaluation is performed before the UEs enter TM9 to prevent high-
speed UEs from entering TM9 mode and having negative impacts. For low-speed cells, the
TM9_MOBILITY_DECISION_SWITCH option of the SectorSplitGroup.IntelligentBeamSchSwitch
parameter can be selected to ignore mobility evaluation and reduce the delay for entering TM9.
2021-11-30 Page 72 of 105

When TM9-capable UEs are used for drive tests, there is a significant increase in the throughput of
cell-edge UEs indicated in the CDF curve.
Intelligent beam scheduling requires that all cells in the same sector split group meet the following
requirements:
 The SRSCfg.SrsCfgInd parameters must be set to BOOLEAN_TRUE.
 The SRSCfg.FddSrsCfgMode parameters must be set to the same value.
 The SRSCfg.SrsSubframeCfg parameters must be set to the same value when the
SRSCfg.FddSrsCfgMode parameters are set to DEFAULTMODE.
 The SrsSubframeRecfSwitch option settings of the CellAlgoSwitch.SrsAlgoSwitch
parameters must be the same when the SRSCfg.FddSrsCfgMode parameters are set to
DEFAULTMODE.
Precise Power Sharing

Precise power sharing considers more factors such as load, spectral efficiency, and power usage.
This function improves the use of the shared power by considering various factors. It increases the
downlink user-perceived rate under the same power configuration. Precise power sharing is
controlled by the PRECISE_PWR_SHR_SWITCH option of the
2021-11-30 Page 73 of 105

Power Sharing Enhancement for TM4 UEs

Power sharing enhancement for TM4 UEs enables rank-1 and low-MCS TM4 UEs to use the shared
power. This function is controlled by the RANK1_LOW_MCS_ENH_PWR_SHR_SW option of the
Dynamic Power Sharing for TM4 UEs

In TM4 mode, the difference between CRS power and PDSCH power is notified to UEs through RRC
signaling. Dynamic PDSCH power adjustment may cause the PDSCH demodulation performance of
UEs to deteriorate. Therefore, dynamic power sharing in earlier versions is applicable only to low-MCS
TM4 UEs. After dynamic power sharing for TM4 UEs is enabled, not only low- but also high-MCS TM4
UEs can enjoy power sharing gains.
For details, see10 Downlink Capacity Enhancement Solution (eRAN18.1).
7.1.2 Benefits
This feature increases the user-perceived rates in SMB cells. The downlink user-perceived rates
increase by 5% to 10% for TM4 UEs and 10% to 40% for TM9 UEs. The more uneven the distribution
of UEs among split cells and the higher the penetration rate of TM9 UEs, the higher the gains.
Inter-carrier power sharing and CFI adaptation increase the proportion of shared power and improve
user experience by 5% to 10% in medium- and heavy-load scenarios.
If the TM9 mobility evaluation switch is turned on, the delay for TM9-capable UEs to enter TM9 is
shortened, and the cell-edge throughput increases by about 10% during drive tests with TM9-capable
UEs.

Three or four beams are configured for SMB, as listed in the following table.
Table 7-1 Number of beams in the inner and outer circles supported by each sector split group
(AAU5711a/AAU5733/AAU5726)
Beam Template BeamDeploymentMod BeamDeploymentMod BeamDeploymentMod
ID e Set to MODE_0. e Set to MODE_1. e Set to MODE_2.
1 Outer circle: 1 Not supported Not supported
Note that only inter-
carrier power sharing is
supported under this
setting.
2 Not supported Outer circle: 2 Not supported
Outer circle: 3
2021-11-30 Page 74 of 105

Beam Template BeamDeploymentMod BeamDeploymentMod BeamDeploymentMod

ID e Set to MODE_0. e Set to MODE_1. e Set to MODE_2.
Outer circle: 4

Configure a sector split group and sector split cells for SMB. For details about how to activate sector
split cells, see the MML commands for SMB.
//Configuring SRS-related parameters (Run the following commands if the FddSrsCfgMode parameter is set to ADAPTIVEMODE.)
MOD SRSCFG: LocalCellId=100, SrsCfgInd=BOOLEAN_TRUE, FddSrsCfgMode=ADAPTIVEMODE;
//Configuring SRS-related parameters (running the following commands if the FddSrsCfgMode parameter is set to
DEFAULTMODE, and setting the SrsSubframeCfg parameter based on site requirements)
MOD SRSCFG: LocalCellId=100, SrsCfgInd=BOOLEAN_TRUE, FddSrsCfgMode=DEFAULTMODE, SrsSubframeCfg=xx;
//Turning on the intelligent beam scheduling switch for the sector split group
MOD CELLMIMOPARACFG: LocalCellId=100, MuMimoMaxPairLayer=TWO_LAYERS;
MOD SECTORSPLITGROUP: SectorSplitGroupId=0, IntelligentBeamSchSwitch=JOINT_SCHEDULING_SWITCH-
1&ENH_JOINT_SCHEDULING_SWITCH-1&PWR_SHR_CFI_ADJ_SWITCH-1&INTER_CARRIER_PWR_SHR_SWITCH-
1&TM9_MOBILITY_DECISION_SWITCH-1&PRECISE_PWR_SHR_SWITCH-1&RANK1_LOW_MCS_ENH_PWR_SHR_SW-1,
BeamOptPrbUsageThld=1, Tm9SrsMeasThreshold=-3;
//Setting CSI-RS-related parameters

2021-11-30 Page 75 of 105


//(Optional) It is recommended that the DlCqiAdjDeltaOptSwitch option be selected to achieve better performance.
//(Optional) Changing the offset relative to the maximum PA for the shared power received by TM9 UEs. If the RBLER increases
after the function is enabled, it is recommended that this parameter be adjusted from 0 to 30.
MOD SECTORSPLITGROUP: SectorSplitGroupId=0, PowerSharingTm9UeMaxPaOfs=xx;
//(Optional) After intelligent beam scheduling is enabled, narrow beams are used for TM9 UEs. As a result, the channel quality
improves, the reported CQI increases, and the aggregation level decreases. If the number of DTXs increases after the feature is
enabled, you can change the CELLPDCCHALGO.PdcchOutLoopAdjLowerLimit parameter setting from the default value -5 to -20 to
reduce the number of DTXs.
MOD CELLPDCCHALGO: LocalCellId=100, PdcchOutLoopAdjLowerLimit=-20;
//(Optional, recommended) Turning on the MM_SCC_TM9_MU_MIMO_SW

//(Optional, recommended) Enabling the frequency-difference-based correction function

//(Optional, recommended) Enabling fast Doppler measurement reporting so that UEs can enter TM9 earlier
//(Optional, recommended) Enabling the massive MIMO PUCCH short interval function if the load of the sector split group is heavy
MOD ENODEBALGOSWITCH: UlResManageOptSw=MM_PUCCH_PERIOD_OPT_SWITCH-1;

//Restoring the CSI-RS-related parameter settings. The following parameter values are used as an example.
2021-11-30 Page 76 of 105

MOD CELLCSIRSPARACFG: LocalCellId=100, CsiRsSwitch=ADAPTIVE_CFG,

CsiRsAdaptBeamCount=ADAPTIVE_BEAM_DISABLED, CsiRsConfigUserNumTh=10, CsiRsConfigUserRatioTh=50,
MOD CELLCSIRSPARACFG: LocalCellId=100, CsiRsSwitch=NOT_CFG;
//Turning off the intelligent beam scheduling switch for the sector split group
MOD SECTORSPLITGROUP: SectorSplitGroupId=0, IntelligentBeamSchSwitch=JOINT_SCHEDULING_SWITCH-
0&ENH_JOINT_SCHEDULING_SWITCH-0&PWR_SHR_CFI_ADJ_SWITCH-0&INTER_CARRIER_PWR_SHR_SWITCH-
0&TM9_MOBILITY_DECISION_SWITCH-0&PRECISE_PWR_SHR_SWITCH-0&RANK1_LOW_MCS_ENH_PWR_SHR_SW-0;

The following counters have been added on the basis of SMB.
Counter ID Counter Name Counter Description

1526732723 L.Traffic.User.TM9.Avg Average number of TM9 UEs in a cell
1526747667 L.ChMeas.PRB.TM9 Total number of PRBs used in downlink
TM9
1526747668 L.Traffic.DL.SCH.TB.TM9 Number of TBs transmitted in downlink
TM9
1526747669 L.Traffic.DL.SCH.TB.TM9.bits Number of bits transmitted in downlink
TM9
1526747670 L.Traffic.DL.SCH.TB.Retrans. Number of bits retransmitted in downlink
TM9.bits TM9
1526746986 L.PwrShare.PwrIn.TTI.Num Number of TTIs in which a cell receives
shared power
1526746987 L.PwrShare.PwrOut.TTI.Num Number of TTIs in which a cell shares its
power
2021-11-30 Page 77 of 105


N/A
7.3.3 Hardware
For details, see the description of SMB. BBPs must be UBBPg2a or UBBPg3.
7.3.4 Software
Feature License
This function requires the licenses for Massive MIMO Introduction, 32T32R Massive MIMO Package,
and intelligent beam scheduling. In addition, it requires the Massive MIMO DL 2-Layers Extended
Processing Unit License.
It is recommended that the licenses for LOFD-001001, LOFD-001003, LOFD-001005, and LOFD-
001060 be all purchased.

Introduction
Package
Diversity
LNOFD-151305 Intelligent Beam LT1S000SSS00 Per SectorSplitGroup
Scheduling
Massive MIMO DL 2- LT1SMMDL2EPU Per Cell
Layers Extended
Processing Unit License
(FDD)
a: One license unit of intelligent beam shaping is required for each sector split group. Intelligent
beam shaping is a subfeature and is controlled by the license for LNOFD-151301 Smart Massive
MIMO.
Note
2021-11-30 Page 78 of 105


License units for Massive MIMO Introduction and 32T32R Massive MIMO Package are consumed only
when Cell and SectorSplitGroup MOs are associated by running the ADD SECTORSPLITCELL
command. For Massive MIMO Introduction and 32T32R Massive MIMO Package, the sales unit "Per Cell"
refers to per sector split group specified by the SectorSplitGroup MO, and is unrelated to the number of
sector split cells in the group.

License units for intelligent beam scheduling are consumed only when the
JOINT_SCHEDULING_SWITCH option of the SectorSplitGroup.IntelligentBeamSchSwitch parameter
is selected.

For details about the capacity license usage of a massive MIMO cell, see License Management.

Apply for the Massive MIMO DL 2-Layers Extended Processing Unit License based on the number of
downlink layers in massive MIMO cells or SMB cells on each BBP. One license unit is required for every
two layers.

N/A

7.4 Benefits
1. Run the DSP CELL command to query the value of Work Status of a cell in which SMB is
enabled. If the value is Normal, SMB has been enabled.
2. Run the LST SECTORSPLITGROUP command to query the option settings of the Smart
Sector Scheduling Switch parameter. Check whether the corresponding functions have been
enabled.
3. Check the values of the following counters. If the values change, this feature has taken effect.
Function Counter Name Description
L.ChMeas.PRB.TM9 Number of PRBs used in TM9

TM9 beamforming
L.Traffic.User.TM9.Avg Number of TM9 UEs
Number of TTIs in which a cell

L.PwrShare.PwrIn.TTI.Num
receives shared power
Power sharing
Number of TTIs in which a cell shares
L.PwrShare.PwrOut.TTI.Num
its power
2021-11-30 Page 79 of 105


You are advised to use KPIs and drive tests to evaluate the gains of intelligent beam scheduling.
Gain Specifications
This feature increases the user-perceived rates in SSB cells. The higher the penetration rate of TM9
UEs, the higher the gains. For specific gains, see the following table.
Transmission Mode Average Downlink UE Throughput Gain
TM9 10% to 40%
TM4 5% to 10%
Note
 Penetration rate of TM9 UEs = L.Traffic.User.TM9.Avg (number of TM9 UEs) / L.Traffic.User.Avg
(average number of UEs in a cell)
 Within the preceding gain range, the higher the proportion of QPSK UEs on the live network, the
higher the gains. (Generally, the proportion of QPSK UEs is about 30% to 60%.)
 Within the preceding gain range, the more imbalanced the load between cells in a sector split
group, the higher the gains.
 Assume that the penetration rate of TM9 UEs is x. Then, the average downlink UE throughput
increases by 10% * x + 5% * (1 – x) to 40% * x + 10% * (1 – x).
For example, if the penetration rate of TM9 UEs is 50%, the average downlink UE throughput
increases by 7.5% to 25%.
Evaluation Methods

Intelligent beam scheduling requires the configuration of uplink SRS. The uplink user-perceived rate
decreases slightly when the number of UEs is less than 150.
7.4.4 DT Analysis
It is recommended that two UEs be used together for drive tests. It is expected that the downlink
throughput of TM9-capable UEs is 10% to 40% higher than that of TM9-incapable UEs.
Note
As background services fluctuate greatly, the resources and interference levels in the same serving cell of a UE
also fluctuate greatly in different drive test times. It is recommended that one TM9-capable UE and one TM9-
incapable UE of the same brand and model be used in drive tests to compare gains after intelligent beam
scheduling is enabled.
2021-11-30 Page 80 of 105

It is recommended that 2R UEs be used for drive tests. The gains for 4R UEs capable of TM9 are small.

N/A
2021-11-30 Page 81 of 105

8 Precise Beamforming
DMB depends on MU-MIMO pairing to schedule multiple UEs using the same time-frequency
resources in a cell. If UEs do not support 32-port channel information measurement and reporting,
two-level beamforming is used. For details, see the description of DMB. The eNodeB generates the
final beamforming weights for data transmission based on two-level beamforming weights. The first-
level beamforming weights are generated for CSI-RS transmission, and the second-level
beamforming weights are generated based on CSI-RS measurement and PMI reporting.
The first-level beamforming weights may have quantization errors. The beams used are preset and
evenly distributed in the coverage space. Beam direction quantization errors decrease the gains of
the final beamforming weights and affect MU-MIMO pairing and interference cancellation. To address
this issue, downlink weight adjustment based on statistical reciprocity is introduced. This function
adjusts the downlink channel beamforming weights based on the reciprocity of partial channel
information between uplink and downlink as well as the statistical uplink channel information. This
improves the downlink weight accuracy, spectral efficiency, and downlink throughput. This function is
applicable to DMB. It is recommended that the MU-MIMO Weight Adjustment Strategy parameter
be set to FULL_ZERO_FORCING to reduce the interference between UEs.
The second-level beamforming weights are generated based on the UE-reported wideband PMI. In
urban areas where most channels are non-line-of-sight (NLOS) channels, wideband information
cannot represent all sub-band information due to obvious channel frequency selectivity. As a result,
MU-MIMO pairing and interference cancellation are affected. Sub-band PMI reporting and sub-band
beamforming are introduced for large-packet UEs. This function configures and triggers aperiodic
sub-band PMI reporting for TM9 UEs, improving the downlink PMI weight accuracy, spectral
efficiency, and downlink throughput. This function is applicable to DMB and intelligent beam
scheduling.
Note
If aperiodic reporting triggered by sub-band beamforming conflicts with periodic reporting, aperiodic reporting is
delayed. In CA scenarios, if aperiodic reporting triggered by sub-band beamforming conflicts with periodic
reporting of each carrier in all reporting timeslots of the triggering period, aperiodic reporting is not triggered and
sub-band beamforming does not take effect.
Downlink weight adjustment based on statistical reciprocity is controlled by the

PRECISE_DL_CSI_SW option of the CellMimoParaCfg.MimoSwitch parameter.
Sub-band beamforming is controlled by the MASSIVE_MIMO_SUBBAND_BF_SW option of the
CellMimoParaCfg.MimoSwitch parameter.
8.1.2 Benefits
Downlink weight adjustment based on statistical reciprocity improves spectral efficiency and downlink
throughput, relieves network load, and increases user-perceived rates in heavy-load scenarios where
the penetration rate of TM9 UEs is high. There will be low gains in complex coverage scenarios with
NLOS propagation and many reflection paths. There will be high gains in simple coverage scenarios
with LOS propagation and few reflection paths.
2021-11-30 Page 82 of 105

Sub-band beamforming improves spectral efficiency and downlink throughput, relieves network load,
and increases user-perceived rates in heavy-load scenarios where the penetration rate of TM9 UEs
is high. There will be high gains in complex coverage scenarios with NLOS propagation and many
reflection paths. There will be low gains in simple coverage scenarios with LOS propagation and few
reflection paths.

DMB is enabled, or both SMB and intelligent beam scheduling are enabled.

//Turning on the switch for downlink weight adjustment based on statistical reciprocity (for each of the PCell and SCells in CA
scenarios)
MOD CELLMIMOPARACFG: LocalCellId=100, MimoSwitch= PRECISE_DL_CSI_SW-1;
//(Optional) You are advised to turn on the FULL_ZERO_FORCING switch for downlink weight adjustment based on statistical
reciprocity
MOD CELLMIMOPARACFG: LocalCellId=100, MuMimoWeightAdjStrategy=FULL_ZERO_FORCING;
//Turning on the sub-band beamforming switch

MOD CELLMIMOPARACFG: LocalCellId=100, MimoSwitch= MASSIVE_MIMO_SUBBAND_BF_SW-1;
//(Optional) You are advised to turn on the SimulAckNackAndCqiSwitch for sub-band beamforming
MOD CELLCQIADAPTIVECFG: LocalCellId=100, SimulAckNackAndCqiSwitch=ON;

//Turning off the switch for downlink weight adjustment based on statistical reciprocity (for each of the PCell and SCells in CA
scenarios)
MOD CELLMIMOPARACFG: LocalCellId=100, MimoSwitch= PRECISE_DL_CSI_SW-0;
//Turning off the switch for sub-band beamforming

MOD CELLMIMOPARACFG: LocalCellId=100, MimoSwitch= MASSIVE_MIMO_SUBBAND_BF_SW-0;


N/A
8.3.3 Hardware
For details, see the description of SMB. BBPs must be UBBPg2a or UBBPg3. RF modules must be
AAU5711a/AAU5733/ AAU5726.
2021-11-30 Page 83 of 105

8.3.4 Software
Feature License
This feature requires the licenses for massive MIMO introduction, 32T32R massive MIMO package,
and massive MIMO for SCells. Precise beamforming is a subfeature and is controlled by the license
for LEOFD-151316 32T32R Massive MIMO Enhancement Package. It requires the licenses for DMB
when working with DMB. It requires the licenses for SMB when working with SMB; in this case, it also
requires intelligent beam scheduling.

Package
LEOFD-151316 32T32R Massive MIMO LT1SMMIMOS00 Per Cell
Enhancement Package

N/A

8.4 Benefits
1. Run the LST CELLMIMOPARACFG command. If the MIMO Switch parameter has a value of
PRECISE_DL_CSI_SW:On, downlink weight adjustment based on statistical reciprocity has
been enabled.
2. Run the LST CELLMIMOPARACFG command. If the MIMO Switch parameter has a value of
MASSIVE_MIMO_SUBBAND_BF_SW:On, sub-band beamforming has been enabled.
----End

You are advised to use KPIs but not drive tests for evaluation. For details about gain evaluation
methods, see the descriptions of SMB and DMB.

Downlink weight adjustment based on statistical reciprocity: 5% to 15%
2021-11-30 Page 84 of 105

Sub-band beamforming: about 5%

For details, see 3.4.2 Gain Specifications and Evaluation Methods.

After sub-band beamforming is enabled, UEs occupy uplink resources for sub-band CSI feedback.
As a result, the uplink user-perceived rate slightly decreases.
8.4.4 DT Analysis
This feature improves the UE pairing efficiency by improving channel information accuracy.
Therefore, it is not recommended that drive tests be used for gain analysis.

N/A
2021-11-30 Page 85 of 105

9 Downlink Turbo Pilot

9.1 Principles
The downlink turbo pilot function increases the RSRP measured by UEs based on frequency-domain
power adjustment and UE measurement bandwidth configuration. It expands the downlink cell
coverage without changing the total power of the AAU in FDD massive MIMO scenarios.
This function is controlled by the SectorSplitGroup.TurboPilotPowerOffset parameter. If this

parameter is set to a non-zero value, the corresponding coverage enhancement value is used. The
power in the bandwidth center is increased. To improve the measurement results of UEs, a certain
measurement bandwidth must be configured for UEs in the local cell and neighboring cells.
Measurement bandwidth configuration is enabled by setting the CellResel.MeasBandWidthCfgInd
parameter to CFG. The measurement bandwidth is configured by setting the
CellResel.MeasBandWidth parameter to MBW6.
Some UEs have compatibility issues with measurement bandwidth configuration. To ensure stable
handover performance, the base station can determine whether to initiate a proactive handover for a
UE based on its channel quality. This function is controlled by the ACTIVE_HANDOVER_SW option
of the SectorSplitGroup.SectorSplitSwitch parameter. This option can be selected only when the
SectorSplitGroup.TurboPilotPowerOffset parameter is set to a value other than 0. Furthermore,
for UEs that have compatibility issues with ping-pong handovers due to air interface environment
fluctuations, the CellMimoParaCfg.DlTurboPilotCompatUeA3Ofs parameter can be used for
additional A3 measurement compensation. After an intra-frequency handover, if the UE sends an
intra-frequency A3 measurement report within the identification duration specified by
CellMimoParaCfg.DlTurboPilotCompatIdentTime and the strongest neighboring cell reported by
the UE is the originally serving cell, the UE is considered as a UE with compatibility issues.
2021-11-30 Page 86 of 105

Note
Each cell in a sector split group broadcasts a measurement bandwidth change request message to adjacent cells
through X2 interfaces when the downlink turbo pilot switch setting is changed; it also broadcasts the message
upon cell activation and every early morning. If a cell that receives the message determines that it is a
neighboring cell of the cell that broadcasts the message, it notifies UEs that the measurement bandwidth is
MBW6. The neighbor relationship status is updated every early morning after the message is broadcast, and the
status remains for 24 hours after the update.
On commercial networks, coverage performance depends on multiple types of uplink and downlink channels, and
uplink coverage is limited sometimes. This function improves only downlink pilot coverage but may not expand
cell coverage sometimes, especially in deep coverage scenarios.
9.1.2 Benefits
This function improves the RSRP/RSRQ measured by UEs, thereby improving the downlink
coverage. It increases the number of UEs in a cell while keeping the coverage consistent with the
baseline after the existing modules on the live network are replaced.

DMB or SMB is enabled.

 Activation Command Examples
//Configuring the turbo pilot power offset parameter as required.
MOD SectorSplitGroup: SectorSplitGroupId=100, TurboPilotPowerOffset=xx;
//Setting a UE measurement bandwidth

MOD CellResel: LocalCellId=100, MeasBandWidthCfgInd = CFG, MeasBandWidth = MBW6
//(Optional) Enabling proactive handover when the turbo pilot power offset parameter is set to a non-zero value
MOD SectorSplitGroup: SectorSplitGroupId=100, SectorSplitSwitch=ACTIVE_HANDOVER_SW-1
 Deactivation Command Examples
//Disabling the proactive handover function and the turbo pilot function
MOD SectorSplitGroup: SectorSplitGroupId=100, SectorSplitSwitch=ACTIVE_HANDOVER_SW-0, TurboPilotPowerOffset=0;
//(Optional) Restoring the UE measurement bandwidth based on the network plan

MOD CELLRESEL: LocalCellId=100, MeasBandWidthCfgInd=NOT_CFG, MeasBandWidth=MBWxx;


N/A

For details, see the description of SMB. BBPs must be UBBPg2a or UBBPg3. RF modules must be
AAU5711a/AAU5733/ AAU5726.
2021-11-30 Page 87 of 105


This feature requires the licenses for massive MIMO introduction and 32T32R massive MIMO
package.


N/A

9.4 Benefits
1. Run the DSP CELL command to query the value of Work Status. If the value is Normal, the
massive MIMO cell has been enabled.
2. Run the LST SECTORSPLITGROUP command to query the Turbo Pilot Power Offset setting
and the ACTIVE_HANDOVER_SW setting of Sector Split Switch to check whether the
functions have been enabled.
3. Observe the number of RRC_CONNECTED UEs in the cell and check whether the number
changes.
----End

N/A

Observe the changes in the number of UEs in a cell using KPIs. Alternatively, perform drive testing to
observe the cell edge and the RSRP/RSRQ measured by UEs.
For details about other network performance evaluation methods, see the descriptions of SMB and
DMB.
2021-11-30 Page 88 of 105


This function increases the proportion of cell edge UEs as it expands the cell coverage, but may
decrease the PRB usage, average spectral efficiency, and user-perceived rate. The decrease
depends on the traffic model and UE distribution.
Frequency-domain power control decreases the power of some frequency bands and therefore may
degrade user experience and decrease spectral efficiency for UEs scheduled in these frequency
bands. The decrease degree is less than 5%.
The measurement bandwidth of UEs in the local cell and neighboring cells must be set to the six RBs
in the middle. Otherwise, some UEs perform wideband measurements for neighboring cells and the
measured RSRP/RSRQ values remain unchanged. As a result, cell coverage expansion cannot be
achieved.
If some UEs are incompatible with measurement bandwidth configuration, the number of intra-
frequency cell handovers increases and the handover failure rate or service drop rate may increase.
It is recommended that proactive handover be enabled to prevent the service drop rate from
increasing due to handover delay.
9.4.4 DT Analysis
Perform drive testing to observe the cell edge and the RSRP/RSRQ measured by UEs.

For UEs that have compatibility issues with ping-pong handovers due to air interface environment
fluctuations, the CellMimoParaCfg.DlTurboPilotCompatUeA3Ofs parameter can be used for
additional A3 measurement compensation. After an intra-frequency handover, if the UE sends an
intra-frequency A3 measurement report within the identification duration specified by
CellMimoParaCfg.DlTurboPilotCompatIdentTime and the strongest neighboring cell reported by
the UE is the originally serving cell, the UE is considered as a UE with compatibility issues.
CellMimoParaCfg.DlTurboPilotCompatUeA3Ofs: Indicates the offset compensation value for the
serving cell in intra-frequency event A3 measurement report sent by UEs that are identified as UEs
with compatibility issues after the downlink turbo pilot function is enabled. If this parameter is set to 0,
only the power increase value in the middle of the bandwidth is compensated for the serving cell
offset in intra-frequency event A3 measurement report sent by UEs that are identified as UEs with
compatibility issues after the downlink turbo pilot function is enabled. If this parameter is set to a non-
zero value, in addition to the power increase value in the middle of the bandwidth, the value of this
parameter is compensated for the serving cell offset in intra-frequency event A3 measurement report
sent by UEs that are identified as UEs with compatibility issues after the downlink turbo pilot function
is enabled.
A smaller value of this parameter results in a smaller offset compensation value for the serving cell in
intra-frequency event A3 measurement report sent by such UEs. UEs of this type with significant
signal fluctuation are more likely to perform intra-frequency ping-pong handovers and the number of
intra-frequency handovers increases. A larger value of this parameter results in a larger offset
compensation value for the serving cell in intra-frequency event A3 measurement report sent by such
UEs. For UEs of this type with significant signal fluctuation, the number of intra-frequency ping-pong
handovers decreases. For UEs of this type with slight signal fluctuation, the probability of initiating
intra-frequency handovers is low, which may cause service drops.
2021-11-30 Page 89 of 105

CellMimoParaCfg.DlTurboPilotCompatIdentTime: Indicates the duration for identifying UEs with

compatibility issues after the downlink turbo pilot function is enabled. After an incoming intra-
frequency handover, if a UE sends an intra-frequency A3 measurement report within the identification
duration and the strongest neighboring cell reported by the UE is the serving cell before the
handover, the UE is considered as a UE with compatibility issues.
A smaller value of this parameter results in a lower probability that UEs with compatibility issues are
identified when the downlink turbo pilot function is enabled. As a result, some such UEs may not be
identified and the number of intra-frequency handovers increases significantly. A larger value of this
parameter results in a higher probability that UEs with compatibility issues are identified when the
downlink turbo pilot function is enabled. However, the probability that normal UEs are mistakenly
identified increases, which may cause service drops.
2021-11-30 Page 90 of 105

10 Downlink Capacity Enhancement Solution (eRAN18.1)

Channel-power-adaptive beamforming
Due to beam adjustment and interference control, different downlink beamforming weights are used
for antenna channels in some scenarios, causing power to differ between them. As the transmit
power of the base station depends on the antenna channel with the maximum power, the power of
the channels may need to be reduced proportionally. In this case, some channels may suffer from
power loss. This function adaptively uses normalized eigenvector beamforming (NEBF) and power-
limited eigenvector beamforming (PEBF) based on the scheduling and interference conditions to
achieve optimal balance between power control and interference control, thereby increasing the
downlink UE data rate. This function is controlled by the ADAPT_CHN_PWR_BF_SW option of the
SectorSplitGroup.SectorSplitSwitch parameter.
PMI Management
FDD massive MIMO uses SMB to deliver downlink spatial multiplexing gains. However, the logical
port architecture corresponding to the beamforming weights for reference signals is not always the
same as the architecture assumed during protocol codebook design. If they are inconsistent, the
accuracy of PMIs reported based on some codebooks is relatively poor. PMI management is
introduced to address this issue. It identifies the beamforming weights for reference signals and
proactively manages the sets of PMIs that can be reported by UEs, thereby increasing the downlink
UE data rate and downlink cell capacity. PMI management is controlled by the
PMI_MANAGEMENT_SW option of the SectorSplitGroup.SectorSplitSwitch parameter.
Rank Management
This function is controlled by the RANK_MANAGEMENT_SW option of the
SectorSplitGroup.SectorSplitSwitch parameter. The base station proactively controls rank
reporting of TM9 UEs in identified scenarios so that UEs that originally report both rank 1 and rank 2
now report only one rank. In this case, stable channel information can be obtained, which improves
the downlink UE data rate and downlink cell capacity. Rank management supports SMB and
depends on intelligent beam scheduling.

In TM4 mode, the difference between CRS power and PDSCH power is notified to UEs through RRC
signaling. Dynamic PDSCH power adjustment may cause the PDSCH demodulation performance of
UEs to deteriorate. Therefore, dynamic power sharing in earlier versions is applicable only to low-
MCS TM4 UEs. After dynamic power sharing for TM4 UEs is enabled, not only low- but also high-
MCS TM4 UEs can enjoy power sharing gains. This function extends the range of UEs that can use
the shared power, improving the downlink user-perceived rate of TM4 UEs and downlink cell
capacity. Dynamic power sharing for TM4 UEs is controlled by the DYNAMIC_TM4_PWR_SHR_SW
option of the SectorSplitGroup.IntelligentBeamSchSwitch parameter and depends on intelligent
2021-11-30 Page 91 of 105

beam scheduling. Power sharing can also take effect for TM3 UEs in the same way as for TM4 UEs.
After this function is enabled, power sharing conflicts may occur between cells that receive shared
power. If conflicts occur, the cells receiving shared power are sorted by the scheduling priorities of
the UEs served by them. A cell serving UEs with higher scheduling priorities preferentially uses
shared power. The probability of power sharing conflicts between cells is determined by the
CellDynPowerSharing.PwrInsuffTimeRateThld parameter.
Maximum-Pairing-Efficiency-based Scheduling (PEM2.0)

This function is controlled by the CellMimoParaCfg.MuMimoPairingStrategy parameter. Before this
function is enabled, the scheduling priority and inter-UE interference are considered during UE
pairing. The total post-pairing spectral efficiency is affected by channel information quantization
errors as channel information is reported based on quantized codebooks in an FDD system. If the
CellMimoParaCfg.MuMimoPairingStrategy parameter is set to ENH_MU_PAIRING, enhanced
maximum-pairing-efficiency-based scheduling takes effect. When maximum-pairing-efficiency-based
scheduling is used, candidate UEs are sorted for controlling the impact on CEUs. In this case, if the
downlink throughput of CEUs are considered, the pairing efficiency of cell center UEs (CCUs) is
significantly affected. When enhanced maximum-pairing-efficiency-based scheduling is used, the
packet size and priority of CEUs are considered to ensure the downlink throughput of CEUs while
mitigating the impact on the pairing efficiency of CCUs. This function supports DMB and SMB.
10.1.2 Benefits
The functions in this solution increase the downlink capacity and user-perceived rate by about 10% in
LTE FDD massive MIMO scenarios with light, medium, and heavy loads.

 Beneficial scenarios
Light Load Medium Load Heavy Load
Rank management √ √ √
PMI management √ √
Channel-power-adaptive beamforming √
PEM2.0 √ √
Dynamic power sharing for TM4 UEs √ √
Base-station-level beam adjustment √ √ √
 Impact factors
The following table lists the factors that have impacts on the downlink capacities of different functions
in MC and MM scenarios.
MC Scenarios
PRB Usage TM9 Proportion of Proportion of Number of
(Cell/Sector Penetration Rank 2 Unsatisfactory UEs in
Load) Rate PMIs Overlapping
2021-11-30 Page 92 of 105

Areas
Rank management N/A Proportional Proportional N/A N/A
Inversely
PMI management N/A N/A N/A N/A
proportional
Channel-power-
adaptive It does not take effect in MC scenarios.
beamforming
It takes effect
when the value
is greater than
PEM2.0 N/A N/A N/A N/A
or equal to
60%.
Proportional
It takes effect
when the value
Extreme power is less than or Inversely
N/A N/A N/A
sharing equal to 40%. proportional
Inversely
proportional
Base-station-level
joint pattern Proportional N/A N/A N/A Proportional
adjustment
* Proportional: The larger the factor value, the greater the feature gains.
* Inversely proportional: The larger the factor value, the smaller the feature gains.
MM Scenarios
Number of
PRB Usage TM9 Proportion of Proportion Number
Proportion UEs in
(Cell/Sector Penetration Unsatisfactory of Tail of Paired
of Rank 2 Overlapping
Load) Rate PMIs Packets Layers
Areas
Rank
It does not take effect in MM scenarios if beam number adjustment is disabled.
management
PMI Inversely
N/A N/A N/A N/A N/A N/A
management proportional
Channel-
power- Inversely
Proportional Proportional N/A N/A N/A N/A
adaptive proportional
beamforming
Proportiona
PEM2.0 Proportional N/A N/A N/A N/A N/A l
Extreme
Inversely Inversely
power N/A N/A N/A N/A N/A
proportional proportional
sharing
Base-station-
level joint
Proportional N/A N/A N/A Proportional N/A N/A
pattern
adjustment
2021-11-30 Page 93 of 105

* Proportional: The larger the factor value, the greater the feature gains.
* Inversely proportional: The larger the factor value, the smaller the feature gains.

10.3.1 Feature Activation Policies and MML Command Examples
The beneficial scenarios and impact factors of different functions in the solution have been described
in 10.2 Application Scenarios. There are no negative impacts in non-recommended scenarios.
Therefore, you are advised to enable the functions in all scenarios.
MML command examples
• Rank management
Activation command examples
//Turning on the rank management switch
MOD SECTORSPLITGROUP: SectorSplitGroupId=0, SectorSplitSwitch=RANK_MANAGEMENT_SW-1;
Deactivation command examples

//Turning off the rank management switch
MOD SECTORSPLITGROUP: SectorSplitGroupId=0, SectorSplitSwitch=RANK_MANAGEMENT_SW-0;
• PMI management
//Turning on the PMI management switch
MOD SECTORSPLITGROUP: SectorSplitGroupId=0, SectorSplitSwitch=PMI_MANAGEMENT_SW-1;

//Turning off the PMI management switch
MOD SECTORSPLITGROUP: SectorSplitGroupId=0, SectorSplitSwitch=PMI_MANAGEMENT_SW-0;
• Channel-power-adaptive beamforming
//Turning on the channel-power-adaptive beamforming switch
MOD SECTORSPLITGROUP: SectorSplitGroupId=0, SectorSplitSwitch=ADAPT_CHN_PWR_BF_SW-1;
MOD SECTORSPLITGROUP: SectorSplitGroupId=0, AcpbTbsIndexThld=11;

//Turning off the channel-power-adaptive beamforming switch
MOD SECTORSPLITGROUP: SectorSplitGroupId=0, SectorSplitSwitch=ADAPT_CHN_PWR_BF_SW-0;
• PEM2.0
//Enabling enhanced maximum-pairing-efficiency-based scheduling (PEM2.0)
MOD CELLMIMOPARACFG: LocalCellId=100, MuMimoPairingStrategy=ENH_MU_PAIRING;

//Disabling enhanced maximum-pairing-efficiency-based scheduling (PEM2.0)
MOD CELLMIMOPARACFG: LocalCellId=100, MuMimoPairingStrategy=DEFAULT;
• Dynamic power sharing for TM4 UEs
2021-11-30 Page 94 of 105


//Enabling dynamic power sharing for TM4 UEs
MOD SECTORSPLITGROUP: SectorSplitGroupId=0, SectorSplitSwitch=DYNAMIC_TM4_SHR_SW-1;

//Disabling dynamic power sharing for TM4 UEs
MOD SECTORSPLITGROUP: SectorSplitGroupId=0, SectorSplitSwitch=DYNAMIC_TM4_SHR_SW-0;

PKI monitoring is the same as that for SMB. For details, see 3.3.2 KPI Monitoring.

N/A

For details, see the corresponding description of SMB. BBPs must be UBBPg2a/UBBPg3. RF
modules must be AAU5711a/AAU5733/AAU5726.

Feature Licenses
This feature requires the licenses for Massive MIMO Introduction and 32T32R Massive MIMO
Package.


N/A

10.4 Benefits
Rank Management
 Using MML commands
Run the LST SECTORSPLITGROUP command to query the RANK_MANAGEMENT_SW
setting of the Sector Split Switch parameter. If the setting is On, the rank management function
is enabled. If the setting is Off, the function is disabled.
2021-11-30 Page 95 of 105

 Using Counters
After rank management takes effect, the value of the L.ChMeas.RI.Rank2 counter changes.
 Using internal CHRs
L2CellchrDlmumimoInfoStru *dlMumimoInfoChr
tm9Rank1LimitDlschCnt: number of times rank 1 scheduling is limited for TM9 UEs (including
SU- and MU-MIMO UEs)
tm9TotalDlschCnt: total number of times TM9 UEs are scheduled
Divide the first value by the second value to obtain the effective proportion of rank management.
PMI Management
Run the LST SECTORSPLITGROUP command to query the PMI_MANAGEMENT_SW setting
of the Sector Split Switch parameter. If the setting is On, the PMI management function is
enabled. If the setting is Off, the function is disabled.
Query the feature activation status.
DSP CELLDYNINFO: CommandCode1=39, CommandCode2=sector split group ID, CommandCode3=4;
/*crsWeightType. 0: invalid; 1: AA; 2: AB. */AA corresponds to weight form b, and AB corresponds to weight
form a.
rank2Pmilto8SchCnt: number of TTIs where rank 2 and PMI 1 to 8 are used in scheduling
totalSchCnt: total number of times cell-level scheduling is performed
Divide the first value by the second value to obtain the effective proportion of PMI management.
Channel-Power-Adaptive Beamforming
Run the LST SECTORSPLITGROUP command to query the ADAPT_CHN_PWR_BF_SW
setting of the Sector Split Switch parameter. If the setting is On, channel-power-adaptive
beamforming is enabled. If the setting is Off, the function is disabled.
nebfSchRbgCnt: number of RBGs where NEBF is used
pebfSchRbgCnt: number of RBGs where PEBF is used
PEM2.0
Run the LST CELLMIMOPARACFG command to query the value of the MU-MIMO Pairing
Strategy parameter. If the value is ENH_MU_PAIRING, PEM2.0 is enabled. If the value is
DEFAULT, PEM2.0 is disabled.
2021-11-30 Page 96 of 105


pem2McSchCnt: number of times PEM2.0 is used in SMB mode

Run the LST SECTORSPLITGROUP command to query the DYNAMIC_TM4_PWR_SHR_SW
setting of the Intelligent Beam Scheduling Switch parameter. If the setting is On, dynamic
power sharing for TM4 UEs is enabled. If the setting is Off, the function is disabled.
 Using Counters
After dynamic power sharing for TM4 UEs takes effect, the value of the
L.PwrShare.PwrOut.TTI.Num counter decreases.
Gain Specifications
The overall gain of this solution is over 10%.
Evaluation Methods
For details about other network performance evaluation methods, see the descriptions of SMB and
DMB.

After dynamic power sharing for TM4 UEs is enabled, channel power increases and some UEs that
originally always report rank 1 now alternatively report rank 1 and rank 2, causing possible user
experience deterioration of these UEs. It is recommended that dynamic power sharing for TM4 UEs
be used with PMI management. When the average PRB usage is less than 30% and the proportion
of QPSK UEs is less than 40%, the cell-level gains equal (1 – Proportion of TM9 UEs) x 5%.
10.4.4 DT Analysis
Same as that for SMB. For details, see 3.4.4 DT Analysis.

After dynamic power sharing for TM4 UEs is enabled, power sharing conflicts may occur between
cells that receive shared power. If conflicts occur, the cells receiving shared power are sorted by the
scheduling priorities of the UEs served by them. A cell serving UEs with higher scheduling priorities
preferentially uses shared power. The probability of power sharing conflicts between cells is
determined by the CellDynPowerSharing.PwrInsuffTimeRateThld parameter.
Other functions do not involve optimization.
2021-11-30 Page 97 of 105

11 Massive MIMO Uplink Coverage Boost

Massive MIMO uplink coverage boost applies to SMB scenarios (where three or four cells are
generated after a split) and includes the uplink full-antenna reception and uplink joint scheduling
functions.
Uplink Full-Antenna Reception

Uplink full-antenna reception enables UE-level 32R (instead of logical equivalent-cell-level 4R) on the
PUSCH, improving the received signal strength and interference suppression capability in the uplink,
as shown in Figure 11-1.
Figure 11-1 Uplink full-antenna reception
This function is controlled by the UL_COVERAGE_BOOST_SW option of the

SectorSplitGroup.SectorSplitSwitch parameter. If this option is selected, the uplink coverage boost
2021-11-30 Page 98 of 105

function takes effect. UE-level joint reception by multiple antennas is implemented on the PUSCH,
improving the uplink received signal quality.
Uplink Joint Scheduling

When two adjacent cells are allocated the same segment of RB resources, they cause interference
to each other, resulting in uplink performance deterioration. The uplink joint scheduling function is
introduced to solve this problem. Joint scheduling between sector split cells is performed with
staggered RBs allocated to CEUs in different sector split cells whenever possible. This reduces
interference between the cells and improves the uplink experience of CEUs. This function takes
effect when the UL_COVERAGE_BOOST_SW option of the SectorSplitGroup.SectorSplitSwitch
parameter is selected and the SectorSplitGroup.UlJointSchEdgeUeSinrThld parameter is set to a
value other than 255.
Note
A UE is considered as a CEU if its SINR is lower than the value of the

SectorSplitGroup.UlJointSchEdgeUeSinrThld parameter and the proportion of RBs allocated to this UE in the
uplink is lower than the value of the SectorSplitGroup.UlJointSchEdgeUeRbRateThld parameter.
Uplink joint scheduling achieves gains by avoiding interference to RB resources of CEUs. This may slightly affect
the performance of other UEs in the cell. To reduce this negative impact, the number of RBs scheduled for CEUs
is limited.
11.1.2 Benefits
This feature significantly improves the PUSCH coverage and user-perceive rate. Using all 32
antennas for reception provides greater beamforming gains and, during busy hours, brings obvious
interference suppression gains.


 Activation Command Examples
//Setting SRS-related parameters
//(Recommended) Configuring parameters related to SRS period adaptation

//(Recommended) Enabling SRS subframe reconfiguration

2021-11-30 Page 99 of 105


//Turning on the switch for uplink coverage boost

MOD SECTORSPLITGROUP:SectorSplitGroupId=4,SectorSplitSwitch=UL_COVERAGE_BOOST_SW-1;
//Turning on the switch for uplink joint scheduling

MOD SECTORSPLITGROUP: SectorSplitGroupId=4, UlJointSchEdgeUeRbRateThld=20, UlJointSchEdgeUeSinrThld=-1;
 Deactivation Command Examples

//Disabling uplink joint scheduling
MOD SECTORSPLITGROUP: SectorSplitGroupId=4, UlJointSchEdgeUeRbRateThld=20, UlJointSchEdgeUeSinrThld=255;
//Disabling uplink coverage boost

MOD SECTORSPLITGROUP: SectorSplitGroupId=4, SectorSplitSwitch=UL_COVERAGE_BOOST_SW-0;
//Restoring the settings of SRS-related parameters (the following values are examples)
//Restoring the settings of other SRS-related parameters as required


Observe the uplink performance improvement based on KPIs.
1. Collect statistics about the uplink SINR, uplink throughput, and MCS index of the PUSCH. After
uplink coverage boost is enabled, the throughput is expected to significantly increase, that is, the
distribution curve is expected to move rightwards.
Counter ID Counter Name Counter Description
1526743701 ~ L.UL.SINR.PUSCH.Index0 ~ Number of samples with
1526743708 L.UL.SINR.PUSCH.Index7 the PUSCH SINR falling
into range x
1526729435 ~ L.Thrp.UL.BitRate.Samp.Index0 ~ Number of samples with
1526729444 L.Thrp.UL.BitRate.Samp.Index9 the uplink throughput
falling into range x
1526727412 ~ L.ChMeas.PUSCH.MCS.0~28 Number of samples with
1526727440 the PUSCH MCS index
being x
The following figure shows the distribution curves before and after feature activation. The vertical
axis in the figure indicates the proportion of samples.
2021-11-30 Page 100 of 105

2. Average uplink edge-user-perceived rate

Average uplink edge-user-perceived rate = (L.Thrp.bits.UL.BorderUE –
L.Thrp.bits.UL.SmallPkt.BorderUE) / L.Thrp.Time.UL.RmvSmallPkt.BorderUE
3. Average uplink user-perceived rate
Average uplink user-perceived rate = (L.Thrp.bits.UL – L.Thrp.bits.UE.UL.SmallPkt) /
L.Thrp.Time.UE.UL.RmvSmallPkt

N/A

For details, see the description of SMB. BBPs must be UBBPg, and RF modules must be AAU5711a,
AAU5726, AAU5733, or AAU5726e.

Feature Licenses
This feature is used with SMB. For details about the license requirements for SMB, see 5.3.1 KPI
Monitoring. This feature also requires the following license.

LEOFD-11301 Massive MIMO LT1S00MMCB00 Per
Coverage Boost SectorSplitGroup

N/A
2021-11-30 Page 101 of 105


11.4 Benefits
1. Check the values of the counters listed in the following table. If the values are not 0, uplink
coverage boost has taken effect.
1526767259 L.UlCovBoostMMSplitCell.User.Avg
1526767258 L.ChMeas.PRB.PUSCH.UlCovBoostM
MSplit.Avg
2. On the MAE-Access, choose Monitor > Signaling Trace > Signaling Trace Management. In
the displayed Signaling Trace Management window, choose Trace Type > LTE > Cell
Performance Monitoring > Usage of RB Monitoring. If the value of Uplink Joint Sch Edge
UE RB Num is not 0, uplink joint scheduling has taken effect.
3. Observe the number of RRC_CONNECTED UEs in the cell and check whether the number
changes.
----End
Gain Specifications
N/A
Evaluation Methods
Observe the uplink performance improvement based on KPIs.

Function Name Function Switch Reference Description
Intra-BBP UL CoMP UlJointReceptionSwitc UL CoMP In massive MIMO SMB
h option of the scenarios (where three or
CellAlgoSwitch.Uplink four cells are generated
CompSwitch parameter after a split), after uplink
coverage boost is enabled
Intra-eNodeB inter- UlJointReceptionPhase UL CoMP for a massive MIMO sector
BBP UL CoMP IISwitch option of the split group, the cells in this
CellAlgoSwitch.Uplink group have a lower priority
CompSwitch parameter for functioning as CoMP
2021-11-30 Page 102 of 105

Function Name Function Switch Reference Description

UL CoMP based on UlJointReceptionOverB UL CoMP cooperating cells. In other
coordinated eNodeB BUsSwitch option of the words, they cooperate with
ENodeBAlgoSwitch.Ov other cells in best-effort
erBBUsSwitch mode on the precondition
parameter that their own coverage
improvement requirements
Inter-eNodeB UL UlNonVoiceJROverRel UL CoMP are met.
CoMP based on axedBHSw option of the
relaxed backhaul ENodeBAlgoSwitch.Ov If uplink full-antenna
erBBUsSwitch reception has taken effect
parameter for UEs, inter-eNodeB UL
CoMP based on relaxed
backhaul cannot be
performed for these UEs.
DMRS measurement NCellSrsMeasPara.NCell UL CoMP If uplink full-antenna
MeasSwitch reception has taken effect
on RBs in a massive MIMO
sector split group,
neighboring cell DMRS
measurement cannot be
performed on these RBs.
eMTC-and-LTE cell eMTC-and-LTE cell eMTC-and- Uplink full-antenna
LTE cell reception cannot take effect
for eMTC UEs in sector split
cells.
11.4.4 DT Analysis
In drive tests, enable the uplink coverage boost feature and observe the uplink coverage
improvement. The following figure shows the comparison result, where the horizontal axis indicates
the path loss obtained based on the downlink RSRP and the vertical axis indicates the geographic
average uplink UE throughput.
2021-11-30 Page 103 of 105


N/A
12 Appendixes
12.1 Appendix 1: FDD Massive MIMO Site Selection and Gain

Evaluation
 Site selection tool
Solution GTM Toolkit on WINS Space
http://winscloud-dongguan.huawei.com/winscloud-portal-website/#/portal (The corresponding
platform needs to be selected.)
 Site selection guide
http://3ms.huawei.com/km/groups/3651517/blogs/details/6220613
12.2 Appendix 2: FDD Massive MIMO Link Budget Tool
12.3 Appendix 3: Base Station Product Description

2021-11-30 Page 104 of 105

12.4 Appendix 4: FDD Massive MIMO Feature Delivery Guide

http://3ms.huawei.com/hi/group/9261/thread_7932068.html?
mapId=9731076&for_statistic_from=all_group_forum
2021-11-30 Page 105 of 105

eRAN18.1 LTE FDD Massive MIMO Solution User Guide

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

eRAN18.1 LTE FDD Massive MIMO Solution User Guide

Uploaded by

Copyright:

Available Formats

LTE FDD Massive MIMO Solution User Guide

Product Name Confidentiality Level

LTE FDD Massive MIMO

Prepared By Zhu Xiaolong, Qian Ying, Date 2020-11-16

Huawei Technologies Co., Ltd.

2021-11-30 Page 1 of 105

Date Revision Chapter/Section Change Description Author

2021-11-30 Page 2 of 105

2 Overview of the FDD Massive MIMO Solution...............................................................8

2021-11-30 Page 3 of 105

4.2 Application Scenarios.................................................................................................................... 37

5 SCC Supporting TM9......................................................................................................44

6 Intelligent Beam Shaping...............................................................................................48

2021-11-30 Page 4 of 105

6.3.1 KPI Monitoring...................................................................................................................... 66

7 Intelligent Beam Scheduling..........................................................................................69

2021-11-30 Page 5 of 105

8.3.6 Parameter Settings............................................................................................................... 84

9 Downlink Turbo Pilot......................................................................................................86

10 Downlink Capacity Enhancement Solution (eRAN18.1)...........................................91

2021-11-30 Page 6 of 105

10.4.3 Network Impacts................................................................................................................. 97

11 Massive MIMO Uplink Coverage Boost......................................................................98

2021-11-30 Page 7 of 105

2 Overview of the FDD Massive MIMO Solution

2.1 Sector Split Group

2021-11-30 Page 8 of 105

Table 2-1 Parameters in the SectorSplitGroup MO

2021-11-30 Page 9 of 105

2.2 Sector Split Cell

Table 2-1 Parameters in the SectorSplitCell MO

2021-11-30 Page 10 of 105

3.1.3 Gain Sources

3.2 Application Scenarios and Site Selection

3.2.1 Application Scenarios

2021-11-30 Page 11 of 105

3.2.2 Site Selection Guidelines

Site Selection Criteria for AAU5711a/AAU5733/AAU5726/AAU5726e

DL Active User >= 8 L.Traffic.ActiveUser.DL.Avg

2021-11-30 Page 12 of 105

Site selection tool: http://winscloud-dongguan.huawei.com/winscloud-portal-website/#/portal (The

Site selection guide: http://3ms.huawei.com/km/groups/3651517/blogs/details/6220613

Filtering Based on Engineering Parameters and Maps

3.3 Feature Activation

Activation Command Examples

//RRU chain configuration scenarios

//Load sharing configuration scenarios

2021-11-30 Page 13 of 105

MOD RRUCHAIN: RCN=0, BRKPOS1=255, BRKPOS2=255;

//Adding sector equipment

//(Optional) Adding baseband equipment

//Adding an operator for each cell

2021-11-30 Page 14 of 105

ADD CELLOP: LocalCellId=101, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;

//(Optional, applicable to the AAU5711a/ AAU5733/AAU5726) Configuring a sector split group

//(Optional, applicable to the AAU5711a/AAU5733/AAU5726) Configuring a sector split group

//Configuring SRS parameters if the SectorSplitGroup.BeamTemplateId parameter is set to 2

2021-11-30 Page 15 of 105

//(Optional, recommended) Turning on the DlCqiAdjDeltaOptSwitch to achieve better performance

//Activating the cells

Deactivation Command Examples

3.3.1 Feature Application Policies

3.3.2 KPI Monitoring