Massive MIMO (FDD) (eRAN15.1 - 01a)

eRAN
Massive MIMO (FDD) Feature

Parameter Description
Issue 01a
Date 2019-04-05
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2019. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 01a (2019-04-05) Copyright © Huawei Technologies Co., Ltd. i

eRAN
Massive MIMO (FDD) Feature Parameter Description Contents
Contents
1 Change History.............................................................................................................................. 1
1.1 eRAN15.1 01a (2019-04-05).......................................................................................................................................... 1
1.2 eRAN15.1 Draft C (2019-02-15)....................................................................................................................................1
1.3 eRAN15.1 Draft B (2019-01-05)....................................................................................................................................2
1.4 eRAN15.1 Draft A (2018-12-30)................................................................................................................................... 2
2 About This Document.................................................................................................................. 5

2.1 General Statements......................................................................................................................................................... 5
2.2 Applicable RAT.............................................................................................................................................................. 6
2.3 Features in This Document.............................................................................................................................................6
3 Overview......................................................................................................................................... 8
4 Basic Massive MIMO Functions.................................................................................................9
4.1 Principles........................................................................................................................................................................ 9
4.1.1 Sector Beamforming....................................................................................................................................................9
4.1.2 Massive MIMO Introduction.....................................................................................................................................12
4.2 Network Analysis......................................................................................................................................................... 13
4.2.1 Benefits...................................................................................................................................................................... 13
4.2.2 Impacts.......................................................................................................................................................................13
4.3 Requirements................................................................................................................................................................ 13
4.3.1 Licenses..................................................................................................................................................................... 14
4.3.2 Software.....................................................................................................................................................................14
4.3.3 Hardware................................................................................................................................................................... 14
4.4 Operation and Maintenance..........................................................................................................................................15
5 SSB..................................................................................................................................................16
5.1 Principles...................................................................................................................................................................... 16
5.2.1 Benefits...................................................................................................................................................................... 18
5.2.2 Impacts.......................................................................................................................................................................19
5.3 Requirements................................................................................................................................................................ 21
5.3.1 Licenses..................................................................................................................................................................... 21
5.3.2 Software.....................................................................................................................................................................22
5.3.3 Hardware................................................................................................................................................................... 27
5.3.4 Others.........................................................................................................................................................................27
Issue 01a (2019-04-05) Copyright © Huawei Technologies Co., Ltd. ii

eRAN

5.4.1 Data Configuration.................................................................................................................................................... 28
5.4.1.1 Data Preparation..................................................................................................................................................... 28
5.4.1.2 Using MML Commands......................................................................................................................................... 37
5.4.1.3 Using the CME....................................................................................................................................................... 40
5.4.2 Activation Verification.............................................................................................................................................. 40
5.4.3 Network Monitoring.................................................................................................................................................. 41
5.4.4 Possible Issues........................................................................................................................................................... 42
6 DDB................................................................................................................................................43
6.1 Principles...................................................................................................................................................................... 43
6.2.1 Benefits...................................................................................................................................................................... 45
6.2.2 Impacts.......................................................................................................................................................................46
6.3 Requirements................................................................................................................................................................ 47
6.3.1 Licenses..................................................................................................................................................................... 47
6.3.2 Software.....................................................................................................................................................................48
6.3.3 Hardware................................................................................................................................................................... 54
6.3.4 Others.........................................................................................................................................................................54
6.4.1.3 Using the CME....................................................................................................................................................... 57
6.4.4 Possible Issues........................................................................................................................................................... 59
7 Intelligent Beam Shaping.......................................................................................................... 60

7.1 Principles...................................................................................................................................................................... 60
7.2.1 Benefits...................................................................................................................................................................... 62
7.2.2 Impacts.......................................................................................................................................................................62
7.3 Requirements................................................................................................................................................................ 63
7.3.1 Licenses..................................................................................................................................................................... 63
7.3.2 Software.....................................................................................................................................................................64
7.3.3 Hardware................................................................................................................................................................... 70
7.3.4 Others.........................................................................................................................................................................70
7.4.1.3 Using the CME....................................................................................................................................................... 74
Issue 01a (2019-04-05) Copyright © Huawei Technologies Co., Ltd. iii

eRAN
8 Massive MIMO for SCells......................................................................................................... 76

8.1 Principles...................................................................................................................................................................... 76
8.2.1 Benefits...................................................................................................................................................................... 77
8.2.2 Impacts.......................................................................................................................................................................77
8.3 Requirements................................................................................................................................................................ 77
8.3.1 Licenses..................................................................................................................................................................... 77
8.3.2 Software.....................................................................................................................................................................78
8.3.3 Hardware................................................................................................................................................................... 78
8.4.1.3 Using the CME....................................................................................................................................................... 79
9 Parameters..................................................................................................................................... 81
10 Counters...................................................................................................................................... 82
11 Glossary....................................................................................................................................... 83
12 Reference Documents............................................................................................................... 84
Issue 01a (2019-04-05) Copyright © Huawei Technologies Co., Ltd. iv

eRAN
Massive MIMO (FDD) Feature Parameter Description 1 Change History
1 Change History
This chapter describes changes not included in the "Parameters", "Counters", "Glossary", and
"Reference Documents" chapters. These changes include:
l Technical changes
Changes in functions and their corresponding parameters
l Editorial changes
Improvements or revisions to the documentation
1.1 eRAN15.1 01a (2019-04-05)

This issue includes the following changes.
Technical Changes
Change Description Parameter Change Base Station Model
Added support for setting Added parameters: 3900 and 5900 series base
the TM4 weight and cell l SectorSplitGroup.TM4 stations
beam azimuth offset for WeightScheme
SSB and DDB. For details,
see 4.1.1 Sector l SectorSplitCell.CellBea
Beamforming. mAzimuthOffset
Editorial Changes
Revised descriptions in this document.
1.2 eRAN15.1 Draft C (2019-02-15)

Issue 01a (2019-04-05) Copyright © Huawei Technologies Co., Ltd. 1

eRAN
Technical Changes
Combined LNOFD-151301 None 3900 and 5900 series base

Smart Massive MIMO and stations
LNOFD-15130101
Intelligent Beam Shaping
into one feature:
LNOFD-151301 Intelligent
Beam Shaping. For details,
see 7 Intelligent Beam
Shaping.
Editorial Changes
1.3 eRAN15.1 Draft B (2019-01-05)

Technical Changes
None
Editorial Changes
1.4 eRAN15.1 Draft A (2018-12-30)

This issue introduces the following changes to eRAN13.1 04 (2018-10-20).

eRAN
Technical Changes
Added intelligent beam Added parameters: 3900 and 5900 series base
shaping. For details, see 7 l SectorSplitGroup.Secto stations
Intelligent Beam Shaping. rSplitSwitch
l SectorSplitGroup.MmB
eamAzimuthAdjStep
l SectorSplitCell.CellBea
mAzimuth
mwidth
mPowerOffset
l eNodeBResModeAl-
go.ServiceMode
Added massive MIMO for Added the 3900 and 5900 series base
SCells. For details, see 8 MM_SCC_TM9_MU_MI stations
Massive MIMO for SCells. MO_SW option to the
CellMimoParaCfg.MimoS
witch parameter.
Added support for None 3900 and 5900 series base

downlink-only cells in stations
massive MIMO scenarios.
For details about the
configuration requirements,
see 5.4.1.1 Data
Preparation and 5.4.1.2
Using MML Commands.
Removed the mutually None 3900 and 5900 series base

exclusive relationship stations
between intra-eNodeB
coordinated scheduling-
based power control (CSPC)
and static shared beam
(SSB). For details, see 5.2.2
Impacts and 5.3.2
Software.
Added the mutually None 3900 and 5900 series base

exclusive relationship stations
between massive MIMO
and DL CoMP with TM9.
For details, see 5.3.2
Software.

eRAN
Added intra-AAU inter-cell None 3900 and 5900 series base

load balancing. For details, stations
see 5.1 Principles.
Added support for massive None 3900 and 5900 series base
MIMO by the 2.6 GHz stations
AAU5711a.
Editorial Changes

eRAN
Massive MIMO (FDD) Feature Parameter Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
This document is intended to acquaint readers with:
l The technical principles of features and their related parameters
l The scenarios where these features are used, the benefits they provide, and the impact
they have on networks and functions
l Requirements of the operating environment that must be met before feature activation
l Parameter configuration required for feature activation, verification of feature activation,
and monitoring of feature performance
NOTE
This document only provides guidance for feature activation. Feature deployment and feature
gains depend on the specifics of the network scenario where the feature is deployed. To achieve
the desired gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this document
apply only to the corresponding software release. For future software releases, refer to the
corresponding updated product documentation.
Trial Features
Trial features are features that are not yet ready for full commercial release for certain
reasons. For example, the industry chain (terminals/CN) may not be sufficiently compatible.
However, these features can still be used for testing purposes or commercial network trials.
Anyone who desires to use the trial features shall contact Huawei and enter into a
memorandum of understanding (MoU) with Huawei prior to an official application of such
trial features. Trial features are not for sale in the current version but customers may try them
for free.
Customers acknowledge and undertake that trial features may have a certain degree of risk
due to absence of commercial testing. Before using them, customers shall fully understand not

eRAN
only the expected benefits of such trial features but also the possible impact they may exert on
the network. In addition, customers acknowledge and undertake that since trial features are
free, Huawei is not liable for any trial feature malfunctions or any losses incurred by using the
trial features. Huawei does not promise that problems with trial features will be resolved in
the current version. Huawei reserves the rights to convert trial features into commercial
features in later R/C versions. If trial features are converted into commercial features in a later
version, customers shall pay a licensing fee to obtain the relevant licenses prior to using the
said commercial features. If a customer fails to purchase such a license, the trial feature(s)
will be invalidated automatically when the product is upgraded.
2.2 Applicable RAT

This document applies to FDD.
2.3 Features in This Document

This document describes the following FDD features.
Feature ID Feature Name Section
LEOFD-131301 Massive MIMO See the corresponding

Introduction sections of the subfeatures.
LEOFD-13130101 Flexible Active-Unit 4 Basic Massive MIMO

Management Functions
LEOFD-13130102 Adaptive Transmission 4 Basic Massive MIMO

Mode Functions
LEOFD-13130104 Power Beamforming 4 Basic Massive MIMO

Functions
LEOFD-13130105 Antenna Fault Detection 4 Basic Massive MIMO

Functions
LEOFD-131302 32T32R Massive MIMO See the corresponding

Package sections of the subfeatures.
LEOFD-13130201 UL 32-Antenna Receive 6 DDB

Diversity
LEOFD-13130202 DL 32-Antenna Spatial 6 DDB

Multiplexing
LEOFD-13130203 Massive MIMO Static 5 SSB

Shared Beam on 32T32R
LEOFD-131303 DL 8-Layer MU-MIMO 6 DDB
LEOFD-131304 DL 16-Layer MU-MIMO 6 DDB
LNOFD-151301 Intelligent Beam Shaping 7 Intelligent Beam

Shaping

eRAN
Feature ID Feature Name Section
LEOFD-151316 32T32R Massive MIMO See the corresponding

Enhancement Package sections of the subfeatures.
LEOFD-15131601 Massive MIMO for SCells 8 Massive MIMO for

SCells

eRAN
Massive MIMO (FDD) Feature Parameter Description 3 Overview
3 Overview
Massive MIMO is widely regarded as a key update of multiple-antenna technology in the

4.5G era. It uses a large number of antenna arrays to perform 3D beamforming and multi-
layer multi-user multiplexing, improving the cell capacity in heavy-load scenarios.
Figure 3-1 shows hardware evolution from traditional MIMO sites to massive MIMO sites.
Figure 3-1 Hardware evolution from traditional MIMO sites to massive MIMO sites
NOTE
l AAU: active antenna unit

l BBU: baseband unit
l CPRI: Common Public Radio Interface
l RRU: remote radio unit

eRAN
Massive MIMO (FDD) Feature Parameter Description 4 Basic Massive MIMO Functions
4 Basic Massive MIMO Functions
Basic massive MIMO functions include sector beamforming and LEOFD-131301 Massive
MIMO Introduction.
4.1 Principles
4.1.1 Sector Beamforming

Sector beamforming enables an eNodeB to apply beam weight for cells in a sector so that the
beam patterns are adapted to UE distributions. In this way, massive MIMO achieves spatial
multiplexing gains and beamforming gains and improves cell capacity.
Huawei provides cell beam deployment modes and weights for typical UE distribution
scenarios in the beam weight file. This file is integrated into the eNodeB software package.
After the beam weight file is activated, you can configure the parameters in the
SectorSplitGroup and SectorSplitCell MOs to enable one sector beam to be split into one or
more beams. One beam corresponds to a sector split cell.
Sector Split Group

The SectorSplitGroup MO specifies a beam group consisting of AAU sector equipment for a
carrier. Table 4-1 describes the parameters in this MO.

eRAN
Table 4-1 Parameters in the SectorSplitGroup MO
Parameter Name Parameter ID Description
Beam Template ID SectorSplitGroup. The value of this parameter is the same as

BeamTemplateId the number of sector split cells, that is, one
beam corresponds to one sector split cell.
Static shared beam (SSB) is enabled when
the SectorSplitGroup.BeamTemplateId
parameter is set to a value greater than 1.
For details, see 5 SSB.
Dynamic dedicated beam (DDB) is enabled
when the
SectorSplitGroup.BeamTemplateId
parameter is set to 1. For details, see 6
DDB.
Beam Deployment SectorSplitGroup. When the combinations of different values

Mode BeamDeploymentM of the BeamDeploymentMode and
ode BeamTemplateId parameters are used, the
eNodeB supports different beam patterns
described in Table 4-2 and Table 4-3.
TM4 Weight SectorSplitGroup.T This parameter specifies the weight scheme

Scheme M4WeightScheme related to TM4.
Table 4-2 Beam patterns for sector beamforming (AAU5711)
Value of BeamDeployment BeamDeployment BeamDeployment

BeamTemplateId Mode Set to Mode Set to Mode Set to
MODE_0 MODE_1 MODE_2
1 Inner circle: 0 Not supported Not supported

Outer circle: 1
2 Not supported Inner circle: 0 Not supported

Outer circle: 2
Beam pattern: (1) in
Figure 4-1

Outer circle: 2
Figure 4-1

Outer circle: 2
Figure 4-1

eRAN
Figure 4-1 Beam patterns of the AAU5711 (BeamTemplateId > 1)
Table 4-3 Beam patterns for sector beamforming (AAU5711a)


Outer circle: 1

Outer circle: 2
Figure 4-2

Outer circle: 3
Figure 4-2
4 Not supported Not supported Inner circle: 0

Outer circle: 4
Figure 4-2
Figure 4-2 Beam patterns of the AAU5711a (BeamTemplateId > 1)
Sector Split Cell

The SectorSplitCell MO is used to set the information about sector split cells in a sector split
group. Table 4-4 describes the parameters in this MO.

eRAN
Table 4-4 Parameters in the SectorSplitCell MO
Parameter Name Parameter ID Description
Cell Beam Index SectorSplitCell.Cell This parameter specifies the beam index of
BeamIndex each sector split cell.
Cell Beam Tilt SectorSplitCell.Cell This parameter specifies the beam tilt of
BeamTilt each sector split cell. The inner and outer
cells are formed on the vertical plane (the
AAU5711a has no inner cells).
Cell Beam Azimuth SectorSplitCell.Cell This parameter specifies the horizontal

Offset BeamAzimuthOffset beam azimuth offset of each sector 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):
l Uplink and downlink bandwidths (Cell.DlBandWidth and Cell.UlBandWidth)
l Uplink and downlink EARFCNs (Cell.DlEarfcn, Cell.UlEarfcn, and
Cell.UlEarfcnCfgInd)
l TX/RX mode (Cell.TxRxMode)
l Number of CRS ports (Cell.CrsPortNum)
l CPRI compression mode (Cell.CPRICompression)
l Customized bandwidth configuration (Cell.CustomizedBandWidthCfgInd,
Cell.CustomizedULBandWidth, and Cell.CustomizedDLBandWidth)
4.1.2 Massive MIMO Introduction
LEOFD-13130101 Flexible Active-Unit Management

To enhance system reliability, the following flexible active-unit management policy is
supported in massive MIMO scenarios:
l If more than 28 antennas are functional, the cell works properly. However, network
performance, such as the cell throughput, may deteriorate. The impact is directly
proportionate to the number of faulty antennas.
l If 16 to 28 antennas are functional, the cell cannot provide services but is still activated.
l The massive MIMO cell is deactivated if fewer than 16 antennas are functional.
This function is enabled by default and not controlled by parameters.
LEOFD-13130102 Adaptive Transmission Mode

l After SSB is enabled, sector split cells support downlink 2x2 MIMO, 4x2 MIMO, or 4x4
MIMO. In this case, adaptive switching between transmission modes is the same as that
of common cells. For details, see MIMO.
l After DDB is enabled, sector split cells support adaptive switching between TM4 and
TM9.

eRAN
LEOFD-13130104 Power Beamforming

Power beamforming enables the eNodeB to adjust the phases and amplitudes based on beam
weights in massive MIMO scenarios. With this function, the eNodeB calculates the weight for
each RF channel of the AAU. It then allocates transmit power to each RF channel based on
the amplitude corresponding to the weight, improving the channel power efficiency and the
downlink UE-perceived rate.
LEOFD-13130105 Antenna Fault Detection

This feature enables the eNodeB to periodically check for antenna faults. The eNodeB reports
ALM-29243 Cell Capability Degraded upon detecting an antenna fault.
In this situation, the value of the alarm parameter Specific Problem is Antenna channel
exceptions. The number of functional antennas can be determined based on the values of the
TX Channel Numbers In The Cell and RX Channel Numbers In The Cell parameters.
4.2 Network Analysis
4.2.1 Benefits
Unlike traditional multiple-antenna technologies, massive MIMO supports both horizontal
and vertical beam adjustment, improving cell capacity in heavy-load scenarios.
4.2.2 Impacts
NOTE
Basic functions have no impact on the network and other functions. For details about the impact of the
SSB function on other functions, see 5.2.2 Impacts. For details about the impact of the DDB function
on other functions, see 6.2.2 Impacts.
Network Impacts
None
Function Impacts
None
4.3 Requirements

eRAN
4.3.1 Licenses
Feature ID Feature Name Model Sales Unit
LEOFD-131301 Massive MIMO LT1SMAMIMO01 Per Cell

Introduction
LEOFD-131302 32T32R Massive LT1S32MAMIMO Per Cell

MIMO Package
NOTE
For details about the capacity license usage of a massive MIMO cell, see License Management.
4.3.2 Software
Prerequisite Functions
Function Name Function Switch Reference Description
Cell beam mode eUCellSectorEqm. None This parameter must

CellBeamMode be set to
MASSIVE_MIMO
_Ph2 for the sector
equipment bound
with the sector split
cell.
Mutually Exclusive Functions

None
NOTE
Basic functions have no mutually exclusive functions. For details about the mutually exclusive functions
of the SSB function, see 5.3.2 Software. For details about the mutually exclusive functions of the DDB
function, see 6.3.2 Software.
4.3.3 Hardware
Base Station Models

3900 and 5900 series base stations
Boards
l BBU: BBU3910 or BBU5900
l BBP: UBBPex2
l Main control board: UMPT

eRAN
RF Modules
The AAU5711 or AAU5711a is required.
l The AAU5711 supports only the 1.8 GHz band and the cell bandwidths of 5 MHz, 10
MHz, 15 MHz, and 20 MHz.
l The AAU5711a supports the 1.8 GHz and 2.6 GHz bands, and supports the cell
bandwidths of 5 MHz, 10 MHz, 15 MHz, and 20 MHz at both the bands.
NOTE
For SSB, each site is typically configured with three AAUs, with two to four cells configured on each
carrier of the AAUs. For DDB, each site is typically configured with three AAUs, with one cell
configured on each carrier of the AAUs.
Cells
l When one or two sector split cells are set up in a sector split group, the cells must be
bound to BBPs. When more than two sector split cells are set up in a sector split group,
the cells can be bound to BBPs or not bound. If binding is required, the cells associated
with all sector split cells in a given sector split group must be bound to the same BBP.
l Each UBBPex2 can be bound to cells associated with all sector split cells in a maximum
of two sector split groups.
l The BBP and AAU are connected using two optical fibers. The optical fibers 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.
l Each AAU supports the sector group with the total bandwidth of up to 30 MHz
according to the CPRI capability of the UBBPex2.
4.4 Operation and Maintenance

Massive MIMO cell setup requires LEOFD-131301 Massive MIMO Introduction and
LEOFD-131302 32T32R Massive MIMO Package to be deployed.
l For details about the operation and maintenance of the SSB function, see 5.4 Operation
and Maintenance.
l For details about the operation and maintenance of the DDB function, see 6.4 Operation
and Maintenance.

eRAN
Massive MIMO (FDD) Feature Parameter Description 5 SSB
5 SSB
SSB is enabled when the number of sector split cells generated after sector beamforming is
greater than 1 (SectorSplitGroup.BeamTemplateId is set to a value greater than 1).
5.1 Principles
SSB provides the following three functions: massive MIMO static shared beam on 32T32R,
PDCCH power resource improvement, and intra-AAU inter-cell load balancing.
Massive MIMO Static Shared Beam on 32T32R

In the uplink, 32 receive channels receive the same signal of a given UE from different
directions to improve reception quality. The eNodeB determines the number of receive beams
formed through uplink 32-antenna beamforming based on the setting of the Cell.CrsPortNum
parameter.
Cell.CrsPortNum Function
CRS_PORT_2 Two receive beams are formed in the uplink for each sector
split cell, which is similar to uplink 2-antenna receive diversity.
CRS_PORT_4 Four receive beams are formed in the uplink for each sector
split cell, which is similar to uplink 4-antenna receive diversity.
In the downlink, the eNodeB performs sector beamforming for 32 antennas, forming multiple
fixed beams on the vertical and horizontal planes. Each beam corresponds to a sector split
cell. Each beam is shared by multiple UEs and independently schedules UEs. In this way,
time-frequency resources are reused between beams, enhancing cell capacity. The eNodeB
determines the number of logical ports for downlink transmission in each sector split cell
based on the Cell.CrsPortNum parameter. All antenna ports of a cell have the same beam
shape.

eRAN
Cell.CrsPortNum Function
CRS_PORT_2 Two logical ports are used for downlink beamforming in each
sector split cell, which is similar to downlink 2x2 MIMO.
CRS_PORT_4 Four logical ports are used for downlink beamforming in each
sector split cell, which is similar to downlink 4x2 MIMO or
4x4 MIMO.
To enable a sector beam to be split into multiple beams, the

SectorSplitGroup.BeamTemplateId parameter must be set to a value greater than 1. For
details about the requirements for this parameter, see Table 4-2 and Table 4-3.
NOTE
l For details about uplink 2-antenna receive diversity, uplink 4-antenna receive diversity, downlink
2x2 MIMO, 4x2 MIMO, and 4x4 MIMO, see MIMO.
l In SSB, the beams of multiple sector split cells are all formed through 32-antenna beamforming.
Therefore, signals transmitted from multiple logical ports by multiple sector split cells are carried on
the same physical channel, achieving power gains. To ensure that the power of each physical
channel does not exceed the rated power of a single AAU channel, the maximum cell-specific
reference signal (CRS) power is subject to the maximum power allowed by the carrier, the number
of split cells on the carrier, the number of CRS ports, the scheme for setting the weight of TM4, and
the PA and PB values. For details, contact Huawei technical support.
PDCCH Power Resource Improvement

When PDCCH resources are insufficient, the cell capacity is suppressed. In this case, the
PDCCH power increase offset can be configured using the
CellChPwrCfg.PdcchPowerIncreaseOffset parameter to increase the total available PDCCH
power. Set this parameter based on the following formula:
Value of PdcchPowerIncreaseOffset (dB) = 10 x log10{[Configured power of the local cell

(W) + Value of PowerPDCCHMargin (W)]/Configured power of the local cell (W)}
Where,
l Configured power of the local cell (W): specified by the

PDSCHCfg.ReferenceSignalPwr parameter.
l PowerPDCCHMargin (W): = PowerUsedRRUMax – Sum[PowerCarrier(i)].
PowerUsedRRUMax is the technical specifications of the AAU. For details, see the
corresponding technical description. Sum[PowerCarrier(i)] is the sum of the configured
power of all carriers in W.
For example, if the configured cell power is 40 W and the value of PowerPDCCHMargin is
10 W: PdcchPowerIncreaseOffset (dB) = 10 x log10(50/40) = 0.96 dB
This function takes effect only when all of the following conditions are met:
l Massive MIMO is enabled.

l The parameters CellRfShutdown.RfShutdownSwitch, CellLowPower.LowPwrSwitch,
and CellShutdown.CellShutdownSwitch are set to OFF and the
SymbolShutdownSwitch option of the ENodeBAlgoSwitch.PowerSaveSwitch
parameter is deselected.

eRAN
l The AAU has a power headroom.
Intra-AAU Inter-Cell Load Balancing

This function is based on SSB and is used to balance the load of multiple intra-frequency cells
set up on the same AAU and improve the overall downlink cell capacity.
Multiple sector split cells are generated through SSB. This function can be enabled for only
one or more sector split cells. This function is controlled by the PrbBalanceSw option of the
CellAlgoSwitch.VmsSwitch parameter.
This function enables the eNodeB to initiate intra-frequency handover measurements for UEs
involved in new accesses, incoming handovers, or RRC connection reestablishment of the
serving cell when the serving cell meets the following conditions:
l The downlink PRB usage exceeds the value of the CellVMS.VmsPrbLoadTh parameter.
l The downlink PRB usage difference between the serving cell and an intra-AAU
neighboring cell exceeds the value of the CellVMS.VmsPrbDiffTh parameter.
If both of the following conditions are met, the eNodeB performs an intra-frequency handover
for the UE in the serving cell. The maximum number of UEs that can be handed over out of
the serving cell within 10 seconds is specified by the CellVMS.VmsHoUeNumTh parameter.
l Intra-frequency handover event A3 is triggered. The offset for triggering intra-frequency

handover event A3 is equal to the value of the
IntraFreqHoGroup.IntraFreqHoA3Offset parameter subtracted by the value of the
CellVMS.VmsA3Offset parameter. For details about event A3, see Mobility
Management in Connected Mode.
l The PRB usage is greater than 2%.
5.2.1 Benefits
SSB improves the UE-perceived rate and spectral efficiency in contiguous urban coverage
areas. The increases are closely related to cell loads, whether the cells using SSB provide
contiguous coverage, and UE distribution across each cell. The gains of SSB are higher if the
cell load is higher, cell coverage is more contiguous, and UEs are more evenly distributed in
each cell.
It is recommended that static shared beam be enabled when all the following conditions are
met and dynamic dedicated beam be enabled when any of these conditions is not fulfilled:
l The inter-site distance is small.
l The downlink physical resource block (PRB) usage is high during busy hours.
l The TM9-capable UE penetration rate is low.
Downlink PRB usage = L.ChMeas.PRB.DL.Used.Avg/L.ChMeas.PRB.DL.Avail x 100%
PDCCH power resource improvement increases the total available PDCCH power, downlink
cell throughput, and average downlink UE throughput. When the PDCCH resources of a cell
are limited (namely, the equivalent CCE usage is greater than 60%), the optimal gains can be
achieved.

eRAN
5.2.2 Impacts
Network Impacts
l SSB
– SSB may decrease the UE-perceived throughput in contrast with 2T2R 3-sector
networking when traffic is light (for example, PRB usage < 50%) or load is
imbalanced between cells.
– On a network with non-contiguous coverage from cells generated using SSB, if
SSB causes the equivalent cell-specific reference signal (CRS) power to be lower
than that of neighboring 2T2R cells, the local cell coverage shrinks.
– SSB increases the number of logical cells in contrast with 2T2R 3-sector
networking. This may decrease the handover success rate and increase the number
of radio resource control (RRC) connection reestablishments and the service drop
rate.
– The average downlink PRB usage of a single cell may decrease, while the eNodeB
traffic volume increases.
– The percentage of times rank 1 is reported (indicated by L.ChMeas.RI.Rank1) will
increase, and the probability that any single UE will achieve the peak data rate will
decrease.
l PDCCH power resource improvement
– This function may decrease the average downlink cell throughput and downlink
spectral efficiency when both PDCCH and physical downlink shared channel
(PDSCH) resources are limited.
– This function may increase interference to neighboring cells. Carrier setup may be
affected if an over-large PDCCH power headroom is configured.
l Intra-AAU inter-cell load balancing
– If the load difference between intra-frequency cells is large, intra-AAU inter-cell
load balancing improves the perceived rate of heavy-load cells and the capacity of
light-load cells. This function also increases the number of handovers and slightly
decreases the handover success rate.
– After this function is enabled, the measured value of the
L.HHO.IntraFreq.Load.ExecAttOut counter may increase.
– Intra-AAU inter-cell load balancing is implemented based on downlink traffic. If
this function is enabled and there is traffic imbalance between the uplink and
downlink, the uplink UE-perceived rate may decrease.

eRAN
Function Impacts
Compact bandwidth Cell.CustomizedBa Compact Bandwidth In massive MIMO

ndWidthCfgInd (FDD) scenarios, it is not
recommended that
compact bandwidth
be enabled.
Otherwise, the
performance of
massive MIMO may
be affected.
Random access Cell.PreambleFmt Random Access It is recommended

preamble format Control that this parameter
be set to 0 in
massive MIMO
scenarios.
eMTC introduction EMTC_SWITCH eMTC SSB is not

option under the compatible with
CellEmtcAlgo.Emtc eMTC when two
AlgoSwitch beams are generated
parameter after a split.
Intra-BBP UL UlJointReceptionS- UL CoMP SSB is not

CoMP witch option under compatible with
the intra-BBP UL
CellAlgoSwitch.Upl CoMP when two
inkCompSwitch beams are generated
parameter after a split.
Intra-eNodeB inter- UlJointReception- UL CoMP SSB is not

BBP UL CoMP PhaseIISwitch compatible with
option under the intra-eNodeB inter-
CellAlgoSwitch.Upl BBP UL CoMP
inkCompSwitch when two beams are
parameter generated after a
split.
UL CoMP based on UlJointReceptio- UL CoMP SSB is not

eNodeB nOverBBUsSwitch compatible with UL
coordination option under the CoMP based on
ENodeBAlgoSwitc eNodeB
h.OverBBUsSwitch coordination when
parameter two beams are
generated after a
split.

eRAN
Intra-eNodeB CSPC CellCspcPara.Intra CSPC SSB is not

EnbCspcSw compatible with
intra-eNodeB CSPC
when two beams are
generated after a
split.
5.3 Requirements
5.3.1 Licenses
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.
LEOFD-131301 Massive MIMO LT1SMAMIMO01 Per Cella

Introduction
LEOFD-131302 32T32R Massive LT1S32MAMIMO Per Cella

MIMO Package
LOFD-001001 DL 2x2 MIMO LT1S0D2I2O00 Per Cell
LOFD-001005 UL 4-Antenna LT1S0U4ARD00 Per Cell

Receive Diversity
LOFD-001060 DL 4x4 MIMO LT1S0DMIMO00 Per Cell
a: The licenses for massive MIMO introduction and 32T32R massive MIMO package are
deducted only after a Cell MO is bound with a SectorSplitGroup MO for the sector split
cell 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
SectorSplitCell.
NOTE

eRAN
5.3.2 Software
CPRI compression Cell.CPRICompress CPRI Compression In massive MIMO

ion scenarios, the
Cell.CPRICompress
ion parameter must
be set but cannot be
set to
NO_COMPRESSI
ON.

Downlink cell DlCellCoverEnhan None The AAU5711 or

coverage ceAlgoSw option of AAU5711a does not
enhancement the support downlink
CellAlgoSwitch.Cel cell coverage
lDlCoverEnhanceS- enhancement.
witch parameter
Power derating CellAlgoSwitch.Pw None The AAU5711 or

rDeratSwitch AAU5711a does not
support power
derating.
Single carrier power SINGLE_CA_PW None None

sharing for 4T R_SHARE_SW_F
OR_4T option of
the
PDSCHCFG.TxCh
nPowerCfgSw
parameter
Intra- and inter- PUSCHCfg.Hoppin None None

subframe frequency gMode being set to
hopping INTRA_AND_INT
ER_SUB_FRAME
Dynamic voltage CellAlgoSwitch.Dy Energy The AAU5711 or

adjustment nAdjVoltSwitch Conservation and AAU5711a does not
Emission Reduction support dynamic
voltage adjustment.
RF channel CellRfShutdown.Rf Energy None

intelligent shutdown ShutdownSwitch Conservation and
Emission Reduction

eRAN
Low power CellLowPower.Low Energy None

consumption mode PwrSwitch Conservation and
Emission Reduction
Intelligent power-off CellShutdown.Cell Energy None

of carriers in the ShutdownSwitch Conservation and
same coverage Emission Reduction
Synchronization EDlMaxTXPwrSwi Power Control The AAU5711 or

signal power tch option of the AAU5711a does not
allocation CellAlgoSwitch.Dl support
PcAlgoSwitch synchronization
parameter signal power
allocation.
eMBMS MBMSSwitch eMBMS All the functions

option of the that require the
CellMBMSCfg.MB eCoordinator are not
MSSwitch compatible with
parameter massive MIMO.
GSM and LTE FDD GLDynSpectrumS GSM and LTE FDD All the functions
dynamic spectrum hareSwitch option Dynamic Spectrum that require the
sharing of the Sharing eCoordinator are not
CellAlgoSwitch.Dy compatible with
nSpectrumShareS- massive MIMO.
witch parameter
GSM and LTE zero GLZeroBufferZon GSM and LTE Zero All the functions
bufferzone eSwitch option of Bufferzone that require the
the eCoordinator are not
witch parameter
GSM and LTE SpectrumCloud.Sp GSM and LTE None

spectrum ectrumCloudSwitch Spectrum
concurrency (LTE Concurrency
FDD)
GSM and LTE AvoidGeranInterfS GSM and LTE None

buffer zone witch option of the Buffer Zone
optimization CellAlgoSwitch.Avo Optimization
idInterfSwitch
parameter
GSM and LTE CellAlgoSwitch.GL GSM and LTE None

dynamic power PwrShare Dynamic Power
sharing (LTE) Sharing

eRAN
CDMA and LTE AvoidCDMAInterf CDMA and LTE None

zero bufferzone Switch option of the Zero Bufferzone
(LTE FDD) CellAlgoSwitch.Avo
idInterfSwitch
parameter
UL refarming zero AvoidUtranInterfS UL Refarming Zero None

bufferzone witch option of the Bufferzone
CellAlgoSwitch.Avo
idInterfSwitch
parameter
UMTS and LTE UL_SPECTRUM_ UMTS and LTE None

Spectrum Sharing SHR_PH2_SW Spectrum Sharing
Phase 2 option of the
SpectrumCloud.Sp
ectrumCloudEnhS-
witch parameter
UMTS and LTE DC_HSDPA_BASE UMTS and LTE None

Spectrum Sharing D_UL_SPECTRU Spectrum Sharing
Based on DC- M_SHR option of Based on DC-
HSDPA the HSDPA
SpectrumCloud.Sp
ectrumCloudSwitch
parameter
Extended cell range Cell.CellRadius Extended Cell Massive MIMO

Range does not support a
cell radius greater
than 15 km.
DL CoMP with FDDHomNetDlCo DL CoMP (FDD) None

TM10 mpSwitch option of
the
CellAlgoSwitch.Dl
CompSwitch
parameter or
FDDHetNetDlCom
pSwitch option of
the
CellAlgoSwitch.Dl
CompSwitch
parameter
DL CoMP with Tm9JtSwitch DL CoMP (FDD) None

TM9 option of the
CellAlgoSwitch.Dl
CompSwitch
parameter

eRAN
Uplink 2x2 MU- UlVmimoSwitch MIMO None

MIMO option of the
CellAlgoSwitch.UlS
chSwitch parameter

MIMO option of the
CellAlgoSwitch.UlS
chSwitch parameter
Uplink SU-MIMO ULSUMIMO2Laye MIMO None

rsSwitch option of
the
CellAlgoSwitch.UlS
uMimoAlgoSwitch
parameter
Extended CP Cell.ULCyclicPrefix Extended CP None

and
Cell.DlCyclicPrefix
High speed mobility Cell.HighSpeedFla High Speed Mobility None

g being set to
HIGH_SPEED
Ultra high speed Cell.HighSpeedFla High Speed Mobility None

mobility g being set to
ULTRA_HIGH_SP
EED
SFN cell Cell.MultiRruCellF SFN None

lag being set to
BOOLEAN_TRUE
Dynamic TDM CellAlgoSwitch.Eic TDM eICIC (FDD) None

eICIC icSwitch
CSPC CellCspcPara.Cell CSPC None

CspcSwitch
eCSPC CellCspcPara.Celle CSPC None

CspcSwitch
Uplink timing TimeAlignmentTi Uplink Timing None

control mer.TimingMeasM Control (FDD)
ode
Inter-eNodeB UL UlCompForVideoS Video Experience None

CoMP for video witch option of the Optimization
services CellAlgoSwitch.Upl
inkCompSwitch
parameter

eRAN
Inter-eNodeB UlVoiceJROverRe- VoLTE None

VoLTE CoMP laxedBHSw option
of the
ENodeBAlgoSwitc
h.OverBBUsSwitch
parameter or
UlJROverRelaxed
BHSw option of the
ENodeBAlgoSwitc
h.OverBBUsSwitch
parameter
Inter-eNodeB UL UlNonVoiceJROve UL CoMP None

CoMP based on rRelaxedBHSw
relaxed backhaul option of the
ENodeBAlgoSwitc
h.OverBBUsSwitch
parameter
Turbo receiver CellAlgoSwitch.Tur Turbo Receiver None

boReceiverSwitch
Virtual 4T4R Virtual4T4RSwitch Virtual 4T4R (FDD) None

option of the
CellAlgoSwitch.Em
imoSwitch
parameter
ePDCCH EpdcchFunctionS- Physical Channel None

witch option of the Resource
CellPdcchAlgo.Epd Management
cchAlgoSwitch
parameter
UL multi-cluster UlMultiClusterS- Scheduling None

witch option of the
CellAlgoSwitch.UlS
chExtSwitch
parameter
Adaptive power AdptCellEdgePwr Scheduling None

allocation for cell- AllocSw option of
edge UEs the
CellAlgoSwitch.Cel
lDlCoverEnhanceS-
witch parameter
Uplink CA CaUl2CCSwitch Carrier Aggregation None

option of the
CaMgtCfg.CellCaA
lgoSwitch parameter

eRAN
Intra-eNodeB and CellAlgoSwitch.Upl Uplink Interference None

inter-eNodeB uplink inkIcSwitch Cancellation (FDD)
interference
cancellation
Intra-RAT MRO IntraFreqMroSwit MRO Intra-AAU inter-cell

ch option of the load balancing is not
CellAlgoSwitch.Mr compatible with this
oSwitch parameter function.
Downlink massive l CaDl5CCSwitch Carrier Aggregation None

CA and
DlMassiveCaSw
itch options of
the
CaMgtCfg.Cell
CaAlgoSwitch
parameter
l UeBandCombR
educedR13Sw
option of the
ENodeBAlgoSw
itch.CaAlgoExtS
witch parameter
5.3.3 Hardware
For details, see 4.3.3 Hardware.
5.3.4 Others
After SSB is enabled, a sector serving three cells will split into multiple cells served by beams
on both horizontal and vertical planes, with each sector covering a horizontal 120° azimuth, as
illustrated in Figure 5-1.
Figure 5-1 Example of SSB networking changes
After the cell networking changes, you need to replan the network configurations, such as
neighboring cells, beamwidths, physical random access channel (PRACH) configurations, and
physical cell identifiers (PCIs).

eRAN
l Neighboring cells
The increase in the number of sectors results in more neighbor relationships. The total
number of neighbor relationships for each cell may reach the maximum value, requiring
adjustments to the existing neighbor relationships.
l Angles between beams
To enlarge the inner-cell coverage area, reduce the tilt of the inner-cell beam so that the
angle between the inner- and outer-cell beams decreases.
l PRACHs and PCIs
More sectors will increase the number of PCI reuses, and cause changes to PRACH root
sequence indexes and a shorter distance between cells involved in the reuse. As a result,
PRACH root sequence indexes and PCIs are more likely to conflict and need to be
replanned.
In addition, the equivalent RS power of each port before and after SSB is enabled should be
considered.
l If the RS power remains stable, the downtilt of each outer-cell beam can be the same as
that of each original cell by default.
l If the RS power decreases, network planning and optimization should consider downtilt
angles, angles between beams, RS power, and the settings of PA and PB.
5.4.1 Data Configuration
5.4.1.1 Data Preparation
Sector Split Cell

For details about the data required for establishing a normal cell, see Cell Management. The
following describes only the data that is different from that for establishing a normal cell. For
details about the requirements for sector split cells, see Cells.
Table 5-1 Sector split cell data

Parameter Name Parameter ID Setting Notes
Topo Type RRUCHAIN.TT Set this parameter to

CHAIN or
LOADBALANCE.
Access Type RRUCHAIN.AT Set this parameter to

LOCALPORT.
Topo Position RRU.TP Set this parameter to

TRUNK.
RRU type RRU.RT Set this parameter to AIRU.
RF Unit Working Mode RRU.RS Set this parameter to LO.

eRAN
Number of RX channels RRU.RXNUM Set this parameter to 32.
Number of TX channels RRU.TXNUM Set this parameter to 32.
Maintenance Mode RRU.MNTMODE Set this parameter to

NORMAL.
RF DC Power Off Alarm RRU.RFDCPWROFFALM Set this parameter to OFF.

Detect Switch DETECTSW
Antenna Number SECTOR.ANTNUM Set this parameter to 0.
Create Default Sector SECTOR.CREATESECTO Set this parameter to

Equipment REQM FALSE.
Antenna Config Mode SECTOREQM.ANTCFG Set this parameter to

MODE BEAM.
Beam Shape SECTOREQM.BEAMSH This parameter must be set

APE to SEC_120DEG for the
sector equipment associated
with sector split cells.
Beam Layer Split SECTOREQM.BEAMLAY This parameter must be set

ERSPLIT to None for the sector
equipment associated with
Beam Azimuth Offset SECTOREQM.BEAMAZI sector split cells.
MUTHOFFSET
Uplink bandwidth Cell.UlBandWidth In massive MIMO

scenarios, this parameter
Downlink bandwidth Cell.DlBandWidth cannot be set to
CELL_BW_N6 or
CELL_BW_N15.
This parameter must be set
to the same value for all
sector split cells in the same
sector split group.
Uplink EARFCN Cell.UlEarfcn This parameter must be set

Uplink EARFCN indication Cell.UlEarfcnCfgInd sector split cells in the same
Downlink EARFCN Cell.DlEarfcn sector split group.
Customized uplink Cell.CustomizedULBand-

bandwidth Width
Customized downlink Cell.CustomizedDLBand-

bandwidth Width

eRAN
Customized bandwidth Cell.CustomizedBandWidth In massive MIMO

configure indicator CfgInd scenarios, it is not
recommended that compact
bandwidth be enabled.
Therefore, it is
recommended that this
parameter be set to
NOT_CFG to avoid impact
on the massive MIMO
performance.
sector split group.
CPRI Compression Cell.CPRICompression In massive MIMO

scenarios, this parameter
must be set, but cannot be
set to
NO_COMPRESSION. For
detailed settings, see CPRI
Compression.
sector split group.
CRS Port Number Cell.CrsPortNum Set this parameter to

CRS_PORT_2 or
CRS_PORT_4.
sector split group.
Cell transmission and Cell.TxRxMode Set this parameter to

reception mode 32T32R.
Work mode Cell.WorkMode For a downlink-only cell,

this parameter must be set to
UL_DL for channel
calibration.
Preamble format Cell.PreambleFmt It is recommended that this

parameter be set to 0 in
massive MIMO scenarios.
PA for even power CellDlpcPdschPa.PaPcOff This parameter specifies the

distribution PA value. Set this parameter
based on site requirements.

eRAN
PB PDSCHCfg.Pb This parameter specifies the

PB value. Set this parameter
based on site requirements.
Baseband Equipment ID BASEBANDEQM.BASEB None

ANDEQMID
Baseband Equipment Type BASEBANDEQM.BASEB Set this parameter to ULDL.

ANDEQMTYPE
UMTS UL Demodulation BASEBANDEQM.UMTS Set this parameter to NULL.

Mode DEMMODE
Cell Beam Mode eUCellSectorEqm.CellBea This parameter must be set

mMode to MASSIVE_MIMO_Ph2
for the sector equipment
associated with sector split
cells.
Local cell ID eUCellSectorEqm.LocalCe None

llId
Sector equipment ID eUCellSectorEqm.SectorE Set this parameter according

qmId to the sector equipment ID
configured in the
SECTOREQM MO.
Baseband equipment ID eUCellSectorEqm.BaseBa Set this parameter according

ndEqmId to the baseband equipment
ID configured in the
BASEBANDEQM MO.
CQI Adjust Algorithm CellAlgoSwitch.CqiAdjAlg Select the

Switch oSwitch DlCqiAdjDeltaOptSwitch
option.
Cell System Information CellSiMap.SiSwitch For a downlink-only cell,

Switch select the
ForbidCellSiSwitch option.
For details about a
downlink-only cell, see Cell
Management.

eRAN
Sector Beamforming
Table 5-2 Parameters related to sector beamforming

Beam Template ID SectorSplitGroup.BeamTe Set this parameter based on

mplateId the actual network load and
UE distributions.
l SSB: Set this parameter
to 2, 3, or 4.
l DDB: Set this parameter
to 1.
Beam Deployment Mode SectorSplitGroup.BeamDe Set this parameter by

ploymentMode referring to Table 4-2 and
Table 4-3.

eRAN
TM4 Weight Scheme SectorSplitGroup.TM4Wei The default value is

ghtScheme DEFAULT_MODE.
When the AAU5711a is
deployed:
l If the
SectorSplitGroup.Beam
TemplateId parameter is
set to 2 or 3 and the
DeploymentMode
parameter is set to
MODE_1, you can set
the
SectorSplitGroup.TM4
WeightScheme
parameter to
COVERAGE_MODE_
2 to improve coverage.
In this case, the
SectorSplitCell.CellBea
mTilt parameter is valid.
l If the
TemplateId parameter is
set to 4 and the
DeploymentMode
parameter is set to
MODE_2, you can set
the
WeightScheme
parameter to
COVERAGE_MODE_
1 to improve coverage.
In this case, the optimal
gain is obtained as
expected, but the
mTilt parameter is
invalid. You can also set
the
WeightScheme
parameter to
COVERAGE_MODE_
2. In this case, the
mTilt parameter is valid.

eRAN
Local cell ID SectorSplitCell.LocalCellI None

d
Sector Split Group ID SectorSplitCell.SectorSplit Set this parameter according

GroupId to the sector split group ID
configured in the
SectorSplitGroup MO.
Cell Beam Index SectorSplitCell.CellBeamI Cell beams are indexed from

ndex 0, from the inner circle to
the outer circle, and from
left to right. The definitions
of left and right depend on
the signal transmission
direction of the AAU.

eRAN
Cell Beam Tilta SectorSplitCell.CellBeamT l The recommended value

ilt range is [-2, 8] for the
AAU5711.
– If the
Cell.CrsPortNum
parameter is set to
CRS_PORT_2 and
there are inner and
outer cells, it is
recommended that
this parameter be set
to 6 and 0 for inter
and outer cells,
respectively. If there
are only outer cells, it
is recommended that
to 3.
– If the
Cell.CrsPortNum
parameter is set to
CRS_PORT_4, split
into inner and outer
cells is not
recommended. If
there are only outer
cells, it is
recommended that
to 3.
l For the 1.8 GHz
AAU5711a, the
recommended value is 8
and the recommended
value range is [4, 10].
There is no inner-cell
beam.
l For the 2.6 GHz
AAU5711a, the
recommended value is 8
and the recommended
value range is [5, 10].
There is no inner-cell
beam.

eRAN
Cell Beam Azimuth Offset SectorSplitCell.CellBeamA It is recommended that this

zimuthOffset parameter be set to the same
value for all cells in a given
sector split group. The
default value is 0. When
deploying the AAU5711 or
AAU5711a, you are advised
to set this parameter to [–
10, 10].
This parameter is invalid
when the
MM_INTELLIGENT_BE
AM_SHAPING_SW
option of the
SectorSplitGroup.SectorSp
litSwitch parameter is
selected.
a: For details about the value range of the cell beam tilt, see the technical description of the
corresponding AAU model. If the configured value exceeds the vertical tilt range described
in the AAU technical description, sidelobe suppression will deteriorate, affecting signal
weighting and demodulation. For example, access preambles, the number of UEs in a cell,
CQI, rank, BER, interference, RSRP, RSSI, SINR, TA, cell capacity, and user experience
may be affected.
Table 5-3 Parameters to be set when SectorSplitGroup.BeamTemplateId is set to 2

SRS Configuration Indicator SRSCfg.SrsCfgInd Set this parameter to

BOOLEAN_TRUE.
FDD SRS Configuration SRSCfg.FddSrsCfgMode Set this parameter to

Mode DEFAULTMODE.
SRS Algorithm SRSCfg.SrsAlgoOptSwitch Deselect the

Optimization Switch SrsSubframeRecfgOptS-
witch option.
SRS subframe configuration SRSCfg.SrsSubframeCfg Set this parameter to SC7 or

SC8.
SRS Period Adaptive CellSrsAdaptiveCfg.SrsPe Set this parameter to OFF.

Switch riodAdaptive
User SRS Period CellSrsAdaptiveCfg.UserS Set this parameter to ms320.

rsPeriod

eRAN
Table 5-4 Parameter related to PDCCH power resource improvement

PDCCH Power Increase CellChPwrCfg.PdcchPowe Set this parameter by

Offset rIncreaseOffset referring to PDCCH Power
Resource Improvement
when PDCCH power
resource improvement is
required.
Intra-AAU Inter-Cell Load Balancing
Table 5-5 Parameters related to intra-AAU inter-cell load balancing

Vertical Multiple Sectors CellAlgoSwitch.VmsSwitch Select the PrbBalanceSw

Algorithm Switch option.
VMS A3 Offset CellVMS.VmsA3Offset Set this parameter to 3.
Max UE Number for CellVMS.VmsHoUeNumT Set this parameter to 1.

Handover Out h
Load Difference Threshold CellVMS.VmsPrbDiffTh The value of this parameter

must be less than the value
of the
CellVMS.VmsPrbLoadTh
parameter. The value 40 is
recommended.
Load Balancing Threshold CellVMS.VmsPrbLoadTh Set this parameter to 80.
5.4.1.2 Using MML Commands
Activation Command Examples

//Removing original cell configurations
RMV EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0;
RMV CELL: LocalCellId=0;
RMV SECTOREQM: SECTOREQMID=0;
RMV SECTOR: SECTORID=0;
//Reconfiguring the following information as the RMV CELL command has been
executed
//Configuring CPRI connections (in RRU chain or load sharing mode)
//Configuring an RRU chain
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=0, HSN=3, HPN=0,
CR=AUTO, USERDEFRATENEGOSW=OFF;
//Configuring load sharing
ADD RRUCHAIN: RCN=0, TT=LOADBALANCE, HSRN=0, HSN=3, HPN=0, TSRN=0, TSN=3, TPN=1,

eRAN
//Adding an AAU (MOD RRUCHAIN is not required in RRU chain 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;
//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 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,
EmergencyAreaIdCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG,
MultiRruCellFlag=BOOLEAN_FALSE, CPRICompression=ENHANCED_COMPRESSION,
CrsPortNum=CRS_PORT_2, TxRxMode=32T32R, WorkMode=UL_DL;
//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;
//(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;

eRAN
ADD CELLOP: LocalCellId=103, TrackingAreaId=0, MMECFGNUM=CELL_MME_CFG_NUM_0;
//Configuring the PA, PB, and RS power

MOD CELLDLPCPDSCHPA: LocalCellId=100, PaPcOff=DB_3_P_A;
MOD PDSCHCFG: LocalCellId=100, Pb=1;
MOD PDSCHCFG: LocalCellId=100, ReferenceSignalPwr=182;
//(Optional, applicable to AAU5711a) Configuring a sector split group

ADD SECTORSPLITGROUP: SectorSplitGroupId=0, BeamTemplateId=4,
BeamDeploymentMode=MODE_2, TM4WeightScheme=DEFAULT_MODE;
//(Optional, applicable to AAU5711) Configuring a sector split group
//(Optional, applicable to AAU5711a) Configuring sector split cells. The cell

beam tilt and cell beam azimuth offset can be set based on network conditions.
ADD SECTORSPLITCELL: LocalCellId=100, SectorSplitGroupId=0, CellBeamIndex=0,
CellBeamTilt=8, CellBeamAzimuthOffset=0;
//(Optional, applicable to AAU5711) Configuring sector split cells. The cell beam
tilt and cell beam azimuth offset can be set based on network conditions.
//Activating the beam weight database

ACT BEAMDB: AldActPowerType=SWFILE;
//Activating the cells

ACT CELL: LocalCellId=100;
//(Optional) Enabling PDCCH power resource improvement

MOD CELLCHPWRCFG: LocalCellId=100, PdcchPowerIncreaseOffset=1;
//(Optional) Selecting the DlCqiAdjDeltaOptSwitch option of the CQI Adjust

Algorithm Switch parameter if possible when enabling intra-AAU inter-cell load
balancing
MOD CELLALGOSWITCH: LocalCellId=100, VmsSwitch=PrbBalanceSw-1,
CqiAdjAlgoSwitch=DlCqiAdjDeltaOptSwitch-1;

eRAN
//(Optional) Configuring parameters related to intra-AAU inter-cell load balancing

MOD CELLVMS: LocalCellId=100, VmsHoUeNumTh=1, VmsPrbDiffTh=40, VmsPrbLoadTh=80,
VmsA3Offset=3;
VmsA3Offset=3;
VmsA3Offset=3;
VmsA3Offset=3;
//Setting 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;
Deactivation Command Examples

//Deactivating PDCCH power resource improvement
//Deactivating intra-AAU inter-cell load balancing

MOD CELLALGOSWITCH: LocalCellId=100, VmsSwitch=PrbBalanceSw-0;
//Other functions cannot be deactivated.
5.4.1.3 Using the CME

For detailed operations, see CME-based Feature Configuration.
NOTE
If this function requires the ACT BEAMDB command for activation after cells are activated, this
function can be activated by running this command, but not by using the CME.
5.4.2 Activation Verification

Step 1 Run the DSP CELL command to query the value of Work Status of a cell in which SSB is
enabled. If the value is Normal, SSB has taken effect.
Step 2 Run the LST CELLCHPWRCFG to query the value of the PDCCH Power Increase
Offset(0.1dB) parameter. PDCCH power resource improvement has been enabled if the
parameter value is consistent with the planned value.
Step 3 Run the LST CELLALGOSWITCH command to query the setting of the Vertical Multiple
Sectors Algorithm Switch parameter. If PrbBalanceSw:On is displayed under the
parameter, intra-AAU inter-cell load balancing has been enabled. Monitor the
L.HHO.IntraFreq.Load.ExecAttOut and L.HHO.IntraFreq.Load.ExecSuccOut counters.

eRAN
If neither of the values of the two counters is 0, intra-AAU inter-cell load balancing has taken
effect.
----End
5.4.3 Network Monitoring

Monitoring the UE-perceived Rate
Analyze the ratio 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
5-2.
l Traffic in the original cell = L.Thrp.bits.DL
l Traffic after the reconstruction = Sum of the values of the L.Thrp.bits.DL counter for
all cells in a sector split group
l UE throughput in the original cell = (L.Thrp.bits.DL – L.Thrp.bits.DL.LastTTI)/
L.Thrp.Time.DL.RmvLastTTI
l UE throughput after the reconstruction = (Sum of the values of the L.Thrp.bits.DL
counter of all cells in a sector split group – Sum of the values of the
L.Thrp.bits.DL.LastTTI counter of all cells in a sector split group)/Sum of the values
of the L.Thrp.Time.DL.RmvLastTTI counter of all cells in a sector split group
Figure 5-2 Scatter chart of UE throughput and traffic
Monitoring Spectral Efficiency

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

eRAN
Figure 5-3 Scatter chart of traffic and PRB usage
5.4.4 Possible Issues

For details, see LEOFD-13130105 Antenna Fault Detection and LEOFD-13130101
Flexible Active-Unit Management.

eRAN
Massive MIMO (FDD) Feature Parameter Description 6 DDB
6 DDB
DDB is enabled when the number of sector split cells generated after sector beamforming is 1
(SectorSplitGroup.BeamTemplateId is set to 1).
6.1 Principles
DDB uses sector beamforming to form a sector split cell. In the cell:
l TM9 UEs use UE-level dedicated beams, and MU-MIMO between beams is supported.
In this case, SRS-related parameters need to be set. For details, see 6.4.1.1 Data
Preparation.
l TM4 UEs use cell-level fixed beams and are scheduled independently in the cell.
To enable sector beamforming to form a sector split cell, the

SectorSplitGroup.BeamTemplateId parameter must be set to 1, and the
SectorSplitGroup.BeamDeploymentMode parameter must be set to MODE_0.
Uplink 32-Antenna Receive Diversity

The 32 RX channels receive the same signal of a UE from different directions to improve
reception quality. The eNodeB receives eight optimal beams formed through beamforming on
32 antennas in the uplink. The subsequent processing is similar to that of uplink 8-antenna
receive diversity.
Downlink 32-Antenna Spatial Multiplexing

Beamforming on 32 antennas in the uplink form a sector split cell. The Cell.CrsPortNum
parameter can be set to CRS_PORT_2 or CRS_PORT_4 for the cell. The beam shape of
each port of the cell is the same, which can be 2T or 4T.
NOTE
In DDB, the beams of the cell can be formed through beamforming on 32 antennas. Therefore, signals
transmitted from multiple logical ports are carried on the same physical channel, achieving power gains.
To ensure that the power of each physical channel does not exceed the rated power of a single AAU
channel, the maximum cell-specific reference signal (CRS) power is subject to the maximum power
allowed by the carrier, the number of CRS ports on the carrier, and the PA and PB values. For details,
contact Huawei technical support.

eRAN
DDB provides different functions based on cell configurations and UE capabilities. When the
TM9Switch option of the CellAlgoSwitch.EnhMIMOSwitch parameter is selected:
l When the conditions listed in Table 6-1 are not met, DDB provides the following
functions:
– If the Cell.CrsPortNum parameter is set to CRS_PORT_2, 2x2 MIMO takes
effect.
– If the Cell.CrsPortNum parameter is set to CRS_PORT_4, 4x2 MIMO or 4x4
MIMO takes effect.
l If any of the conditions listed in Table 6-1 is met, the eNodeB uses four antenna ports to
transmit CSI-RSs to TM9-capable UEs that are compliant with 3GPP Release 10 and
support 4-port CSI-RS transmission, allowing such UEs to work in TM9 mode. The cell
provides dedicated traffic beams for TM9-capable UEs to multiplex time-frequency
resources between beams and improve capacity.
– 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.
– 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.
– 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 to improve network performance. 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 is inaccurate. In this case, set the
CellMimoParaCfg.MuMimoWeightAdjStrategy parameter to
NON_ZERO_FORCING to improve network performance. When data is
transmitted in MU-MIMO mode, the eNodeB does not modify the transmit weight
of each data flow, improving the downlink throughput.
Table 6-1 Conditions

Condition 1 The CellCsiRsParaCfg.CsiRsSwitch parameter is set to FIXED_CFG.
Condition 2 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.
Downlink 8-Layer MU-MIMO

This feature enables an eNodeB to pair up to eight UEs working in TM9 for MU-MIMO,
improving downlink spectral efficiency. Up to eight data streams can be transmitted using the
same orthogonal frequency division multiplexing (OFDM) time-frequency resource. The
eNodeB performs pairing as follows:

eRAN
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 demodulation reference signal (DMRS) symbols on
each data stream based on the generated weight values.
4. Combines these symbols and then transmits data over antenna ports.
This feature is controlled by the CellMimoParaCfg.MuMimoMaxPairLayer parameter. To

enable this feature, set this parameter to EIGHT_LAYERS.
Downlink 16-Layer MU-MIMO

This feature enables an eNodeB to pair up to 16 UEs working in TM9 for MU-MIMO,
improving downlink spectral efficiency. Up to 16 data streams can be transmitted using the
same OFDM time-frequency resource. The pairing process is the same as that for downlink 8-
layer MU-MIMO.
This feature is controlled by the CellMimoParaCfg.MuMimoMaxPairLayer parameter. To

enable this feature, set this parameter to SIXTEEN_LAYERS.

PDCCH power resource improvement is the same for DDB and SSB. For details, see
PDCCH Power Resource Improvement.
6.2.1 Benefits
DDB improves the UE-perceived rate and spectral efficiency in contiguous urban coverage
areas. The gain evaluation method is the same as that for SSB. For details, see 5.4.3 Network
Monitoring.
DDB also improves the average uplink cell throughput and average uplink UE throughput in
contiguous urban coverage areas.
l Average uplink cell throughput = L.Thrp.bits.UL/

L.Thrp.Time.Cell.UL.HighPrecision
l Average uplink UE throughput = (L.Thrp.bits.UL – L.Thrp.bits.UE.UL.SmallPkt)/
L.Thrp.Time.UE.UL.RmvSmallPkt
The gains offered by DDB depend on the following factors:
l Penetration rate of TM9-capable UEs compliant with 3GPP Release 10 and supporting 4-
port CSI-RS transmission
l Cell load
l Whether DDB-enabled cells provide contiguous coverage
l UE distribution in the cells
The gains are most noticeable when the following conditions are met:

eRAN
l DDB is enabled for cells that provide contiguous coverage.

l The cell load is high.
l The TM9-capable UE penetration rate is high (measured by the
L.Traffic.User.TM9.Avg counter).
l UEs are distributed evenly within the cells.
l There is a high percentage of large-packet services in the cells.
l Cell channel quality is stable.
l The inter-site distance is small.
DDB 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 SSB is not
suitable.
PDCCH power resource improvement increases the total available PDCCH power, downlink
cell throughput, and average downlink UE throughput. When the PDCCH resources of a cell
are limited (namely, the equivalent CCE usage is greater than 60%), the optimal gains can be
achieved.
6.2.2 Impacts
Network Impacts
l DDB
– 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.
– After this function is enabled, the number of times smaller MCS indexes are
selected during scheduling will decrease, and the number of times larger MCS
indexes are selected during scheduling will increase (detected by observing the
counters L.ChMeas.PUSCH.MCS.0 to L.ChMeas.PUSCH.MCS.28; sampling
period ≥ 24 hours).
l PDCCH power resource improvement
– This function may decrease the average downlink cell throughput and downlink
spectral efficiency when both PDCCH and PDSCH resources are limited.
– This function may increase interference to neighboring cells. Carrier setup may be
affected if an over-large PDCCH power headroom is configured.

eRAN
Function Impacts

recommended that
compact bandwidth
be enabled.
Otherwise, the
performance of
massive MIMO may
be affected.

be set to 0 in
massive MIMO
scenarios.
6.3 Requirements
6.3.1 Licenses
To use this function, you need to purchase licenses for massive MIMO introduction and
32T32R massive MIMO package.
LOFD-001060. Downlink 16-layer MU-MIMO requires that you purchase the license for
LEOFD-131302 DL 8-Layer MU-MIMO.
LEOFD-131301 Massive MIMO LT1SMAMIMO01 Per Cella

Introduction
LEOFD-131302 32T32R Massive LT1S32MAMIMO Per Cella

MIMO Package

Receive Diversity
LEOFD-131303 DL 8-Layer MU- LT1S0D8MMIMO Per Cell

MIMO

eRAN
LEOFD-131304 DL 16-Layer MU- LT1SD16MMIMO Per Cell

MIMO
a: The licenses for massive MIMO introduction and 32T32R massive MIMO package are
deducted only after a Cell MO is bound with a SectorSplitGroup MO for the sector split
cell 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
SectorSplitCell.
NOTE
6.3.2 Software
CPRI compression Cell.CPRICompress CPRI Compression In massive MIMO

ion scenarios, the
Cell.CPRICompress
ion parameter must
be set but cannot be
set to
NO_COMPRESSI
ON.


witch parameter

support power
derating.

eRAN

OR_4T option of
the
PDSCHCFG.TxCh
nPowerCfgSw
parameter

ER_SUB_FRAME

voltage adjustment.

Emission Reduction

Emission Reduction


allocation.

witch parameter

eRAN
witch parameter

FDD)

idInterfSwitch
parameter


idInterfSwitch
parameter

CellAlgoSwitch.Avo
idInterfSwitch
parameter

SpectrumCloud.Sp
ectrumCloudEnhS-
witch parameter

HSDPA the HSDPA
SpectrumCloud.Sp
ectrumCloudSwitch
parameter

cell radius greater
than 15 km.

eRAN

the
CellAlgoSwitch.Dl
CompSwitch
parameter or
FDDHetNetDlCom
pSwitch option of
the
CellAlgoSwitch.Dl
CompSwitch
parameter

TM9 option of the
CellAlgoSwitch.Dl
CompSwitch
parameter

MIMO option of the
CellAlgoSwitch.UlS
chSwitch parameter

MIMO option of the
CellAlgoSwitch.UlS
chSwitch parameter

rsSwitch option of
the
CellAlgoSwitch.UlS
uMimoAlgoSwitch
parameter

and
Cell.DlCyclicPrefix

g being set to
HIGH_SPEED

ULTRA_HIGH_SP
EED

lag being set to
BOOLEAN_TRUE

eRAN

eICIC icSwitch

CspcSwitch

CspcSwitch
Intra-eNodeB CSPC CellCspcPara.Intra CSPC DDB is not

EnbCspcSw compatible with
intra-eNodeB CSPC.
Uplink timing TimeAlignmentTi Uplink Timing Uplink timing based

control mer.TimingMeasM Control (FDD) on PUCCH is not
ode compatible with
massive MIMO.
The
TimeAlignmentTi
mer.TimingMeasM
ode parameter must
be set to INVALID
in massive MIMO
scenarios.

inkCompSwitch
parameter

of the
ENodeBAlgoSwitc
h.OverBBUsSwitch
parameter or
UlJROverRelaxed
BHSw option of the
ENodeBAlgoSwitc
h.OverBBUsSwitch
parameter
Intra-BBP UL UlJointReceptionS- UL CoMP DDB is not

CoMP witch option of the compatible with
CellAlgoSwitch.Upl intra-BBP UL
inkCompSwitch CoMP.
parameter

eRAN
Intra-eNodeB inter- UlJointReception- UL CoMP DDB is not

BBP UL CoMP PhaseIISwitch compatible with
option of the intra-eNodeB inter-
CellAlgoSwitch.Upl BBP UL CoMP.
inkCompSwitch
parameter
UL CoMP based on UlJointReceptio- UL CoMP DDB is not

eNodeB nOverBBUsSwitch compatible with UL
coordination option of the CoMP based on
ENodeBAlgoSwitc eNodeB
h.OverBBUsSwitch coordination.
parameter

ENodeBAlgoSwitc
h.OverBBUsSwitch
parameter

boReceiverSwitch

option of the
CellAlgoSwitch.Em
imoSwitch
parameter

cchAlgoSwitch
parameter
UL Multi-Cluster UlMultiClusterS- Scheduling None

witch option of the
CellAlgoSwitch.UlS
chExtSwitch
parameter

edge UEs the
CellAlgoSwitch.Cel
lDlCoverEnhanceS-
witch parameter

option of the
CaMgtCfg.CellCaA
lgoSwitch parameter

eRAN

interference
cancellation
eMTC introduction EMTC_SWITCH eMTC DDB is not

option of the compatible with
CellEmtcAlgo.Emtc eMTC.
AlgoSwitch
parameter

CA and
DlMassiveCaSw
itch options of
the
CaMgtCfg.Cell
CaAlgoSwitch
parameter
l UeBandCombR
educedR13Sw
option of the
ENodeBAlgoSw
itch.CaAlgoExtS
witch parameter
6.3.3 Hardware
6.3.4 Others
The equivalent RS power of each port before and after DDB is enabled should be considered.
l If the RS power remains stable, the downtilt can be the same as that of each original cell
by default.
l If the RS power decreases, network planning and optimization should consider downtilt,
RS power, and the settings of PA and PB.

DDB requires the sector split cell data, sector beamforming data, and PDCCH power resource
improvement data for SSB. The difference lies in configuration requirements for the

eRAN
BeamTemplateId and BeamDeploymentMode parameters. For details, see 5.4.1.1 Data

Preparation. In addition, the following MOs and data need to be configured for DDB.
Table 6-2 Data that needs to be configured for DDB


BOOLEAN_TRUE.

Mode DEFAULTMODE.
SRS Algorithm SRSCfg.SrsAlgoOptSwitch Deselect the

Optimization Switch SrsSubframeRecfgOptS-
witch option.
SRS subframe configuration SRSCfg.SrsSubframeCfg Set this parameter to SC1 or

SC2.

Switch riodAdaptive
User SRS Period CellSrsAdaptiveCfg.UserS Set this parameter to ms320.

rsPeriod
MU-MIMO Max Pair Layer CellMimoParaCfg.MuMim Set this parameter to its

oMaxPairLayer recommended value. The
corresponding license needs
to be purchased.
MU-MIMO Weight CellMimoParaCfg.MuMim l If LOS transmission

Adjustment Strategy oWeightAdjStrategy prevails between the
eNodeB and UEs, set
this parameter to
FULL_ZERO_FORCI
NG.
l If NLOS transmission
prevails between the
eNodeB and UEs, set
this parameter to
NON_ZERO_FORCIN
G.

//Removing original cell configurations
RMV EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0;
RMV CELL: LocalCellId=0;
RMV SECTOREQM: SECTOREQMID=0;
RMV SECTOR: SECTORID=0;
//Reconfiguring the following information as the RMV CELL command has been

eRAN
executed
//Configuring CPRI connections (in RRU chain or load sharing mode)
//Configuring an RRU chain
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=0, HSN=3, HPN=0,
//Configuring load sharing
ADD RRUCHAIN: RCN=0, TT=LOADBALANCE, HSRN=0, HSN=3, HPN=0, TSRN=0, TSN=3, TPN=1,
//Adding an AAU (MOD RRUCHAIN is not required in RRU chain 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;
//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 a cell
//Binding the cell to the sector equipment and setting the CELLBEAMMODE
parameter. Determine whether to bind the baseband equipment based on site
conditions.
//(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;
//Configuring the PA, PB, and RS power

//Configuring a sector split group

//Configuring sector split cells. The settings of the AAU5711a are used as an
example. The cell beam tilt and cell beam azimuth offset can be set based on
network conditions.
ADD SECTORSPLITCELL: LocalCellId=100, SECTORSPLITGROUPID=0, CELLBEAMINDEX=0,
//Activating the beam weight database

ACT BEAMDB: AldActPowerType=SWFILE;
//Activating the cells


eRAN
//Setting cell-level SRS parameters

MOD SRSCFG: LocalCellId=100, SrsCfgInd=BOOLEAN_TRUE, FddSrsCfgMode=DEFAULTMODE,
SrsAlgoOptSwitch=SrsSubframeRecfgOptSwitch-0, SrsSubframeCfg=SC1;
//Setting cell-level MIMO parameters

MOD CELLMIMOPARACFG: LocalCellId=100, MuMimoMaxPairLayer=SIXTEEN_LAYERS,
MuMimoWeightAdjStrategy=FULL_ZERO_FORCING;
//Enabling TM9
MOD CELLALGOSWITCH: LocalCellId=0, EnhMIMOSwitch=TM9Switch-1;
//Setting CSI-RS adaptation

MOD CELLCSIRSPARACFG: LocalCellId=0, CsiRsSwitch=ADAPTIVE_CFG;
//(Optional) Enabling PDCCH power resource improvement


//Deactivating PDCCH power resource improvement
//Other functions cannot be deactivated.

NOTE

Using MML Commands
Step 1 Run the DSP CELL command to display the status of the cell in DDB mode. If the cell is
available, DDB has been enabled.
Step 2 Run the LST CELLCHPWRCFG to query the value of the PDCCH Power Increase
Offset(0.1dB) parameter. PDCCH power resource improvement has been enabled if the
parameter value is consistent with the planned value.
----End
Using Counters
DDB has been enabled if any of the following counters has a non-zero value.
Counter ID Counter Name Counter Description
1526739778 L.ChMeas.MUBF. Average number of PRBs

2ndLayer.PairPRB.Succ successfully paired for layer-2 UEs
during MU beamforming

3rdLayer.PairPRB.Succ successfully paired for layer-3 UEs

eRAN

4thLayer.PairPRB.Succ successfully paired for layer-4 UEs






10thLayer.PairPRB.Succ successfully paired for layer-10
UEs during MU beamforming







eRAN

For details, see 5.4.3 Network Monitoring.
6.4.4 Possible Issues

For details, see LEOFD-13130105 Antenna Fault Detection and LEOFD-13130101
Flexible Active-Unit Management.

eRAN
Massive MIMO (FDD) Feature Parameter Description 7 Intelligent Beam Shaping
7 Intelligent Beam Shaping
This chapter describes LNOFD-151301 Intelligent Beam Shaping.
7.1 Principles
In the weight file of SSB, the beam direction and beamwidth are fixed. When UE
distributions vary greatly, using these fixed beam parameters may fail to obtain the optimal
gain. Therefore, intelligent beam shaping is introduced.
Intelligent beam shaping generates the beam direction and beamwidth online based on UE
distributions on the basis of SSB, and adjusts the beam power based on the changed beam
direction or beamwidth. This feature improves the UE-perceived rate in sectors.
Intelligent beam shaping obtains UE distribution information through SRS measurement.
Therefore, SRS-related parameters need to be configured. For details, see 7.4.1.1 Data
Preparation.
Intelligent beam shaping takes effect in the following beam configuration scenarios:
Table 7-1 Beam configuration scenarios of intelligent beam shaping (AAU5711)

1 Not supported Not supported Not supported

Outer circle: 2

Outer circle: 2

eRAN
Table 7-2 Beam configuration scenarios of intelligent beam shaping (AAU5711a)


Outer circle: 3
4 Not supported Not supported Inner circle: 0

Outer circle: 4
The MM_INTELLIGENT_BEAM_SHAPING_SW option of the

SectorSplitGroup.SectorSplitSwitch parameter specifies whether to enable intelligent beam
shaping.
l When the MM_INTELLIGENT_BEAM_SHAPING_SW option is deselected, all the
sub-functions of intelligent beam shaping are disabled, and SSB uses the weight file of
the beam weight database in the eNodeB software package.
l When the MM_INTELLIGENT_BEAM_SHAPING_SW option is selected, the sub-
functions of intelligent beam shaping, including pattern adjustment and power
adjustment, can be enabled by selecting other options of the
SectorSplitGroup.SectorSplitSwitch parameter.
If... Then...
The The pattern adjustment function is enabled. The weight file of

PATTERN_ADJ_ the beam weight database in the eNodeB software package
SWITCH option is automatically becomes invalid. The eNodeB generates the
selected weight file and power configuration of SSB online based on the
real-time UE distribution in a cell. The shortest period for beam
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

PATTERN_ADJ_ generates a weight file of SSB based on the beam direction and
SWITCH option is beamwidth set for the split sector.
deselected l 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.
l 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.

eRAN
If... Then...
The The power adjustment function is enabled. The eNodeB

POWER_ADJ_S adaptively adjusts the values of the CellDlpcPdschPa.PaPcOff
WITCH option is and PDSCHCfg.Pb parameters of the beam based on the
selected principle that the downlink transmit power of the cell reaches
the maximum. 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

POWER_ADJ_S not adjust the power allocated to traffic channels.
WITCH option is
deselected
NOTE
l When the PATTERN_ADJ_SWITCH option of the SectorSplitGroup.SectorSplitSwitch

parameter is selected and the value of the PDSCHCfg.ReferenceSignalPwr,
CellDlpcPdschPa.PaPcOff, or PDSCHCfg.Pb parameter changes, performance may deteriorate
within one hour after the change and will become normal after one hour.
l If the beam width 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.
7.2.1 Benefits
Enabling this feature improves the UE-perceived rate in the cell. If UE distributions in sector
split cells are more uneven and the distance between UEs and the antenna normal line is
longer, the gain is greater. Otherwise, the gain is smaller.
7.2.2 Impacts
Network Impacts
When UEs in sector split cells generated through SSB are evenly distributed, the downlink
UE-perceived rate does not increase, and the uplink UE-perceived rate decreases slightly if
the number of UEs is less than 150.

eRAN
Function Impacts

recommended that
compact bandwidth
be enabled.
Otherwise, the
performance of
massive MIMO may
be affected.

be set to 0 in
massive MIMO
scenarios.
Smart carrier SMART_CARRIE Multi-carrier In cells with

selection based on R_SELECTION_S Unified Scheduling intelligent beam
virtual grids W option of the shaping enabled, the
MultiCarrUnifiedS accuracy of
ch.MultiCarrierUni prediction using
fiedSchSw virtual grid models
parameter decreases.
7.3 Requirements
7.3.1 Licenses
To use this function, you need to purchase licenses for massive MIMO introduction, 32T32R
massive MIMO package, and intelligent beam shaping. One license unit of intelligent beam
shaping is required for each sector split group.
LOFD-001060.

Introduction

MIMO Package
LNOFD-151301 Intelligent Beam LT1S00SSBF00 Per

Shaping SectorSplitGroup

eRAN

Receive Diversity
NOTE
7.3.2 Software
Static shared beam None 5 SSB None
Traffic-based eNodeBResModeAl Traffic-based You must select the

automatic analysis go.ServiceMode Automatic Analysis AI_ENHANCEME
and prediction and Prediction NT_SWITCH
option of the
eNodeBResModeAl
go.ServiceMode
parameter before
selecting the
MM_INTELLIGE
NT_BEAM_SHAP
ING_SW option of
the
SectorSplitCell.Cell
Beamwidth
parameter.
After the
AI_ENHANCEME
NT_SWITCH
option setting is
changed, you need
to run the RST APP
command (a high-
risk command) to
reset the app.

eRAN

SRS subframe SrsSubframeRecfS None None

reconfiguration witch option of the
CellAlgoSwitch.Srs
AlgoSwitch
parameter

witch parameter

support power
derating.

OR_4T option of
the
PDSCHCFG.TxCh
nPowerCfgSw
parameter

ER_SUB_FRAME

voltage adjustment.

Emission Reduction

Emission Reduction


eRAN

allocation.

witch parameter
witch parameter

FDD)

idInterfSwitch
parameter


idInterfSwitch
parameter

CellAlgoSwitch.Avo
idInterfSwitch
parameter

eRAN

SpectrumCloud.Sp
ectrumCloudEnhS-
witch parameter

HSDPA the HSDPA
SpectrumCloud.Sp
ectrumCloudSwitch
parameter

cell radius greater
than 15 km.

the
CellAlgoSwitch.Dl
CompSwitch
parameter or
FDDHetNetDlCom
pSwitch option of
the
CellAlgoSwitch.Dl
CompSwitch
parameter

TM9 option of the
CellAlgoSwitch.Dl
CompSwitch
parameter

MIMO option of the
CellAlgoSwitch.UlS
chSwitch parameter

MIMO option of the
CellAlgoSwitch.UlS
chSwitch parameter

eRAN

rsSwitch option of
the
CellAlgoSwitch.UlS
uMimoAlgoSwitch
parameter

and
Cell.DlCyclicPrefix

g being set to
HIGH_SPEED

ULTRA_HIGH_SP
EED

lag being set to
BOOLEAN_TRUE

eICIC icSwitch

CspcSwitch

CspcSwitch
Uplink timing TimeAlignmentTi Uplink Timing Uplink timing based

control mer.TimingMeasM Control (FDD) on PUCCH is not
ode compatible with
massive MIMO.
The
TimeAlignmentTi
mer.TimingMeasM
ode parameter must
be set to INVALID
in massive MIMO
scenarios.

inkCompSwitch
parameter

eRAN

of the
ENodeBAlgoSwitc
h.OverBBUsSwitch
parameter or
UlJROverRelaxed
BHSw option of the
ENodeBAlgoSwitc
h.OverBBUsSwitch
parameter

ENodeBAlgoSwitc
h.OverBBUsSwitch
parameter

boReceiverSwitch

option of the
CellAlgoSwitch.Em
imoSwitch
parameter

cchAlgoSwitch
parameter
UL Multi-Cluster UlMultiClusterS- Scheduling None

witch option of the
CellAlgoSwitch.UlS
chExtSwitch
parameter

edge UEs the
CellAlgoSwitch.Cel
lDlCoverEnhanceS-
witch parameter

option of the
CaMgtCfg.CellCaA
lgoSwitch parameter

eRAN

interference
cancellation
Intra-RAT MRO IntraFreqMroSwit MRO Intra-AAU inter-cell

ch option of the load balancing is not
CellAlgoSwitch.Mr compatible with this
oSwitch parameter function.

CA and
DlMassiveCaSw
itch options of
the
CaMgtCfg.Cell
CaAlgoSwitch
parameter
l UeBandCombR
educedR13Sw
option of the
ENodeBAlgoSw
itch.CaAlgoExtS
witch parameter
7.3.3 Hardware
For details, see 4.3.3 Hardware. This function requires the UMPTe or later.
7.3.4 Others
If intelligent beam shaping has been enabled and a new beam weight has been generated in
the current version, the beam weight will be inherited after an upgrade and will roll back to
the baseline value of the corresponding version during version rollback.

Table 7-3 describes the parameters that must be set for enabling intelligent beam shaping
based on SSB.

eRAN
Table 7-3 Parameters required for activation of intelligent beam shaping


BOOLEAN_TRUE.

Mode DEFAULTMODE.
SoundingRS algorithm CellAlgoSwitch.SrsAlgoSw Deselect the

switch itch SrsSubframeRecfSwitch
option.
SRS subframe configuration SRSCfg.SrsSubframeCfg SC7

Switch riodAdaptive
User SRS Period CellSrsAdaptiveCfg.UserS Set this parameter to ms80

rsPeriod or ms160.
Sector Split Switch SectorSplitGroup.SectorSp Select the

litSwitch MM_INTELLIGENT_BE
AM_SHAPING_SW,
PATTERN_ADJ_SWITC
H, and
POWER_ADJ_SWITCH
options.
Massive MIMO Beam SectorSplitGroup.MmBea When this parameter is set

Azimuth Adjustment Step mAzimuthAdjStep to 0, intelligent beam
shaping adjusts only the
beamwidth, not the beam
azimuth.
When this parameter is set
to 60, intelligent beam
shaping adjusts the
beamwidth and beam
azimuth based on the
clustering result, and the
adjustment step is not
restricted.
The value 5 is
recommended.
Multi-Carrier Unified Sch MultiCarrUnifiedSch.Mult It is recommended that the

Switch iCarrierUnifiedSchSw SMART_CARRIER_SEL
ECTION_SW option be
deselected to avoid affecting
cell performance.

eRAN
Cell Beam Azimuth SectorSplitCell.CellBeamA This parameter is valid only

zimuth when the
MM_INTELLIGENT_BE
AM_SHAPING_SW
option is selected and the
PATTERN_ADJ_SWITC
H option is deselected.
It is recommended that this
parameter be set to 255,
indicating that the beam
direction configured in the
sector beam weight database
is used.
Cell Beamwidth SectorSplitCell.CellBeamw This parameter is valid only

idth when the
MM_INTELLIGENT_BE
AM_SHAPING_SW
option is selected and the
PATTERN_ADJ_SWITC
H option is deselected.
It is recommended that this
parameter be set to
INVALID, indicating that
the beamwidth configured in
the sector beam weight
database is used.
Cell Beam Power Offset SectorSplitCell.CellBeamP This parameter is valid only

owerOffset when both the
MM_INTELLIGENT_BE
AM_SHAPING_SW and
POWER_ADJ_SWITCH
options are selected. The
value 0 is recommended.

eRAN
Service Mode eNodeBResModeAl- You must select the

go.ServiceMode AI_ENHANCEMENT_S
WITCH option of the
eNodeBResModeAl-
go.ServiceMode parameter
before selecting the
MM_INTELLIGENT_BE
AM_SHAPING_SW
option of the
SectorSplitCell.CellBeamw
idth parameter.
After the
AI_ENHANCEMENT_S
WITCH option setting is
changed, you need to run the
RST APP command (a
high-risk command) to reset
the app.

Configure a sector split group and sector split cells for SSB. For details about how to activate
a sector split cell, see 5.4.1.2 Using MML Commands.
//Setting SRS-related parameters
SrsSubframeCfg=SC7;
SrsSubframeCfg=SC7;
SrsSubframeCfg=SC7;
SrsSubframeCfg=SC7;
MOD CELLALGOSWITCH: LocalCellId=100, SrsAlgoSwitch=SrsSubframeRecfSwitch-0;
//Setting the service mode

MOD ENODEBRESMODEALGO: ServiceMode=AI_ENHANCEMENT_SWITCH-1;
//(High-risk command) Resetting the app (The AID parameter can be queried by
running the DSP APP command. The following uses x as an example.)
RST APP: AID=x, FOCRST=NO;
//Turning on the intelligent beam shaping switch for the sector split group

eRAN
MOD SECTORSPLITGROUP: SectorSplitGroupId=0,

SectorSplitSwitch=MM_INTELLIGENT_BEAM_SHAPING_SW-1&PATTERN_ADJ_SWITCH-1&POWER_ADJ_
SWITCH-1;

//Turning off the feature switch
MOD SECTORSPLITGROUP: SectorSplitGroupId=0,
SectorSplitSwitch=MM_INTELLIGENT_BEAM_SHAPING_SW-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;
SrsSubframeCfg=SC3;
SrsSubframeCfg=SC3;
SrsSubframeCfg=SC3;
MOD CELLSRSADAPTIVECFG: LocalCellId=100, SrsPeriodAdaptive=ON;
//Restoring the service mode

MOD ENODEBRESMODEALGO: ServiceMode=AI_ENHANCEMENT_SWITCH-0;

For details, see 5.4.1.3 Using the CME.

Step 1 Run the DSP CELL command to query the value of Work Status of a cell in which SSB is
enabled. If the value is Normal, SSB has taken effect.
Step 2 Run the LST SECTORSPLITGROUP command to query the values of
MM_INTELLIGENT_BEAM_SHAPING_SW, PATTERN_ADJ_SWITCH, and
POWER_ADJ_SWITCH under the Sector Split Switch parameter to check whether the
corresponding functions have taken effect.
Step 3 Observe the value of L.ChMeas.MassiveMIMO.SmartBF.Dur. If the value of this counter
is not 0, beam direction or beamwidth adjustment has taken effect.
----End

Monitoring the UE-perceived Rate
Analyze the ratio by which the UE-perceived rate improves for given traffic. It is
recommended that the scatter chart regarding UE throughput and traffic be used to compare
the curves before and after feature activation, as shown in Figure 7-1.
l Traffic volume = Sum of the values of the L.Thrp.bits.DL counter for all cells in a
sector split group

eRAN
l UE throughput = (Sum of the values of the L.Thrp.bits.DL counter of all cells in a

sector split group – Sum of the values of the L.Thrp.bits.DL.LastTTI counter of all
cells in a sector split group)/Sum of the values of the L.Thrp.Time.DL.RmvLastTTI
counter of all cells in a sector split group
Figure 7-1 Scatter chart of UE throughput and traffic
Monitoring Spectral Efficiency

Analyze the ratio by which traffic increases for a given PRB usage. It is recommended that
the scatter chart regarding PRB usage and traffic be used to compare the curves before and
after feature activation, as shown in Figure 7-2.
l Traffic volume = Sum of the values of the L.Thrp.bits.DL counter for all cells in a
sector split group
l PRB usage = Average value of PRB usage (L.ChMeas.PRB.DL.Used.Avg/
L.ChMeas.PRB.DL.Avail x 100%) of all cells in a sector split group
Figure 7-2 Scatter chart of traffic and PRB usage

eRAN
Massive MIMO (FDD) Feature Parameter Description 8 Massive MIMO for SCells
8 Massive MIMO for SCells
This chapter describes LEOFD-15131601 Massive MIMO for SCells.
8.1 Principles
DDB uses MU-MIMO pairing to schedule multiple UEs with the same time-frequency
resource in the same cell. In CA scenarios, CA UEs in an SCell do not transmit SRSs and
therefore cannot be paired for MU-MIMO. To address this demand, massive MIMO for
SCells is introduced. This feature is controlled by the MM_SCC_TM9_MU_MIMO_SW
option of the CellMimoParaCfg.MimoSwitch parameter.
When this feature is enabled, the PCell determines the beam coverage of a UE based on the
uplink SRS and performs downlink beam selection and CSI-RS resource allocation in CA
scenarios. For UEs in the SCell served by the same AAU and having the same coverage as the
PCell, beams are selected based on the uplink SRS measurement results reported by UEs in
the PCell. In this way, UEs in the SCell can also be paired for MU-MIMO. This improves
spectral efficiency and downlink throughput.
Figure 8-1 Massive MIMO for SCells
The secondary component carrier (SCC) shares the optimal beam selection results with the
primary component carrier (PCC). Therefore, this feature can be enabled only when the
massive MIMO cells involved in carrier aggregation are set up on the same AAU and have
the same coverage.
When massive MIMO for SCells is enabled, the configurations of the following parameters
are the same for the sector split cells on the PCC and SCC:
l SectorSplitGroup.BeamDeploymentMode

eRAN
l SectorSplitGroup.BeamTemplateId
l SectorSplitCell.CellBeamIndex
l SectorSplitCell.CellBeamTilt
8.2.1 Benefits
After this feature is enabled, UEs on the SCC can also be paired for MU-MIMO, improving
spectral efficiency and downlink throughput. In heavy-load scenarios, this feature helps
relieve the network load and increases the UE-perceived rate.
The larger the spacing between the center frequencies of the PCC and SCC, the lower the UE-
perceived rate. It is recommended that this feature be enabled when the spacing is less than or
equal to 100 MHz.
8.2.2 Impacts
Network Impacts
After this feature takes effect, more UEs in SCells enter TM9, which may increase the number
of scheduled UEs and occupy more PDCCH symbols in the downlink. As a result, the failure
rate of uplink grant assignments over the PDCCH increases, and the average uplink UE
throughput may decrease.
Function Impacts
None
8.3 Requirements
8.3.1 Licenses
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.

Introduction

MIMO Package

eRAN
LEOFD-151316 32T32R Massive LT1SMMIMOS00 Per Cell

MIMO
Enhancement
Package
NOTE
8.3.2 Software
CA cell None Carrier Aggregation None

None
8.3.3 Hardware

The following parameter must be set for enabling massive MIMO for SCells based on DDB.
MIMO Switch CellMimoParaCfg.MimoS Select the

witch MM_SCC_TM9_MU_MI
MO_SW option.

eRAN

//Turning on the SCC TM9 MU-MIMO scheduling switch. This switch must be turned on
for all of the massive MIMO cells that are configured as CA cells.
MOD CELLMIMOPARACFG: LocalCellId=100, MimoSwitch=MM_SCC_TM9_MU_MIMO_SW-1;

//Turning off the SCC TM9 MU-MIMO scheduling switch. This switch must be turned
off for all of the massive MIMO cells that are configured as CA cells.
MOD CELLMIMOPARACFG: LocalCellId=100, MimoSwitch=MM_SCC_TM9_MU_MIMO_SW-0;

NOTE

Step 1 Run the LST CELLMIMOPARACFG command to query the value of
MM_SCC_TM9_MU_MIMO_SW under the MIMO Switch parameter. If the value is On,
this feature has been activated.
Step 2 If the values of the following counters of massive MIMO cells are not 0, this feature has taken
effect.
1526747680 L.Traffic.User.SCell.Active.DL.T Average number of CA UEs in

M9.Avg TM9 that treat the local cell as
their SCell and have SCells
activated
----End

1526728564 L.Thrp.bits.DL.CAUser Total traffic volume for PDCP

SDUs sent to activated CA UEs in
a cell
1526728565 L.Thrp.Time.DL.CAUser Total duration for activated CA

UEs transmitting downlink data at
the PDCP layer in a cell

eRAN
1526729259 L.CA.Traffic.bits.DL.SCell Downlink MAC-layer traffic

volume for CA UEs that treat the
local cell as their SCell
1526729004 L.CA.DL.SCell.Act.Dur Total downlink activation duration

of CA UEs that treat the local cell
as their SCell

eRAN
Massive MIMO (FDD) Feature Parameter Description 9 Parameters
9 Parameters
The following hyperlinked EXCEL files of parameter reference match the software version
with which this document is released.
l Node Parameter Reference: contains device and transport parameters.
l eNodeBFunction Parameter Reference: contains all parameters related to radio access
functions, including air interface management, access control, mobility control, and radio
resource management.
NOTE
You can find the EXCEL files of parameter reference for the software version used on the live network
from the product documentation delivered with that version.
FAQ: How do I find the parameters related to a certain feature from parameter
reference?
Step 1 Open the EXCEL file of parameter reference.
Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and choose
Contains. Enter the feature ID, for example, LOFD-001016 or TDLOFD-001016.
Step 3 Click OK. All parameters related to the feature are displayed.
----End

eRAN
Massive MIMO (FDD) Feature Parameter Description 10 Counters
10 Counters
The following hyperlinked EXCEL files of performance counter reference match the software
version with which this document is released.
l Node Performance Counter Summary: contains device and transport counters.
l eNodeBFunction Performance Counter Summary: contains all counters related to radio
access functions, including air interface management, access control, mobility control,
and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used on the live
network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from performance counter
reference?
Step 1 Open the EXCEL file of performance counter reference.
Step 2 On the Counter Summary(En) sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, LOFD-001016 or TDLOFD-001016.
Step 3 Click OK. All counters related to the feature are displayed.
----End

eRAN
Massive MIMO (FDD) Feature Parameter Description 11 Glossary
11 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
Massive MIMO (FDD) Feature Parameter Description 12 Reference Documents
12 Reference Documents
1. CDMA and LTE Zero Bufferzone

2. CPRI Compression
3. CSPC
4. DL CoMP (FDD)
5. eMBMS
6. eMTC
7. GSM and LTE Buffer Zone Optimization
8. GSM and LTE Dynamic Power Sharing
9. GSM and LTE Zero Bufferzone
10. GSM and LTE Spectrum Concurrency
11. GSM and LTE FDD Dynamic Spectrum Sharing
12. MIMO
13. MRO
14. SFN
15. Turbo Receiver
16. UL CoMP
17. UL Refarming Zero Bufferzone
18. UMTS and LTE Spectrum Sharing
19. VoLTE
20. Extended Cell Range
21. Scheduling
22. Multi-carrier Unified Scheduling
23. High Speed Mobility
24. Power Control
25. UMTS and LTE Spectrum Sharing Based on DC-HSDPA
26. Energy Conservation and Emission Reduction
27. Extended CP
28. Mobility Management in Connected Mode

eRAN
Massive MIMO (FDD) Feature Parameter Description 12 Reference Documents
29. Uplink Timing Control (FDD)

30. Uplink Interference Cancellation (FDD)
31. TDM eICIC (FDD)
32. Video Experience Optimization
33. Random Access Control
34. Physical Channel Resource Management
35. Cell Management
36. Virtual 4T4R (FDD)
37. Compact Bandwidth (FDD)
38. Carrier Aggregation

Massive MIMO (FDD) (eRAN15.1 - 01a)

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Massive MIMO (FDD) (eRAN15.1 - 01a)

Загружено:

Авторское право:

Доступные форматы

eRAN

Massive MIMO (FDD) Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01a (2019-04-05) Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.................................................................................................................. 5

Issue 01a (2019-04-05) Copyright © Huawei Technologies Co., Ltd. ii

5.4 Operation and Maintenance..........................................................................................................................................28

7 Intelligent Beam Shaping.......................................................................................................... 60

Issue 01a (2019-04-05) Copyright © Huawei Technologies Co., Ltd. iii

7.4.3 Network Monitoring.................................................................................................................................................. 74

8 Massive MIMO for SCells......................................................................................................... 76

Issue 01a (2019-04-05) Copyright © Huawei Technologies Co., Ltd. iv

1.1 eRAN15.1 01a (2019-04-05)

1.2 eRAN15.1 Draft C (2019-02-15)

Issue 01a (2019-04-05) Copyright © Huawei Technologies Co., Ltd. 1

Combined LNOFD-151301 None 3900 and 5900 series base

1.3 eRAN15.1 Draft B (2019-01-05)

1.4 eRAN15.1 Draft A (2018-12-30)

Issue 01a (2019-04-05) Copyright © Huawei Technologies Co., Ltd. 2

Added support for None 3900 and 5900 series base

Removed the mutually None 3900 and 5900 series base

Added the mutually None 3900 and 5900 series base

Issue 01a (2019-04-05) Copyright © Huawei Technologies Co., Ltd. 3

Change Description Parameter Change Base Station Model

Added intra-AAU inter-cell None 3900 and 5900 series base

Issue 01a (2019-04-05) Copyright © Huawei Technologies Co., Ltd. 4

2 About This Document

2.1 General Statements

Issue 01a (2019-04-05) Copyright © Huawei Technologies Co., Ltd. 5

2.2 Applicable RAT

2.3 Features in This Document

Feature ID Feature Name Section

LEOFD-131301 Massive MIMO See the corresponding

LEOFD-13130101 Flexible Active-Unit 4 Basic Massive MIMO

LEOFD-13130102 Adaptive Transmission 4 Basic Massive MIMO

LEOFD-13130104 Power Beamforming 4 Basic Massive MIMO

LEOFD-13130105 Antenna Fault Detection 4 Basic Massive MIMO

LEOFD-131302 32T32R Massive MIMO See the corresponding

LEOFD-13130201 UL 32-Antenna Receive 6 DDB

LEOFD-13130202 DL 32-Antenna Spatial 6 DDB

LEOFD-13130203 Massive MIMO Static 5 SSB

LEOFD-131303 DL 8-Layer MU-MIMO 6 DDB

LEOFD-131304 DL 16-Layer MU-MIMO 6 DDB

LNOFD-151301 Intelligent Beam Shaping 7 Intelligent Beam

Issue 01a (2019-04-05) Copyright © Huawei Technologies Co., Ltd. 6

Feature ID Feature Name Section

LEOFD-151316 32T32R Massive MIMO See the corresponding

LEOFD-15131601 Massive MIMO for SCells 8 Massive MIMO for

Issue 01a (2019-04-05) Copyright © Huawei Technologies Co., Ltd. 7

Massive MIMO is widely regarded as a key update of multiple-antenna technology in the

l AAU: active antenna unit

Issue 01a (2019-04-05) Copyright © Huawei Technologies Co., Ltd. 8

4 Basic Massive MIMO Functions

4.1.1 Sector Beamforming

Sector Split Group

Issue 01a (2019-04-05) Copyright © Huawei Technologies Co., Ltd. 9

Table 4-1 Parameters in the SectorSplitGroup MO

Parameter Name Parameter ID Description

Beam Template ID SectorSplitGroup. The value of this parameter is the same as

Beam Deployment SectorSplitGroup. When the combinations of different values

TM4 Weight SectorSplitGroup.T This parameter specifies the weight scheme