Huawei 434789548 Massive MIMO TDD ERAN15 1 Draft A PDF

eRAN
Massive MIMO (TDD) Feature

Parameter Description
Issue Draft A
Date 2018-12-30
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: [email protected]
Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. i

eRAN
Massive MIMO (TDD) Feature Parameter Description Contents
Contents
1 Change History.............................................................................................................................. 1
1.1 eRAN15.1 Draft A (2018-12-30)................................................................................................................................... 1
2 About This Document.................................................................................................................. 8

2.1 General Statements......................................................................................................................................................... 8
2.2 Applicable RAT.............................................................................................................................................................. 9
2.3 Features in This Document.............................................................................................................................................9
3 Overview....................................................................................................................................... 11
3.1 Introduction...................................................................................................................................................................11
3.2 Application Scenarios...................................................................................................................................................13
4 Basic Massive MIMO Functions...............................................................................................14

4.1 Principles...................................................................................................................................................................... 14
4.2 Network Analysis......................................................................................................................................................... 16
4.2.1 Benefits...................................................................................................................................................................... 16
4.2.2 Impacts.......................................................................................................................................................................16
4.3 Requirements................................................................................................................................................................ 17
4.3.1 Licenses..................................................................................................................................................................... 17
4.3.2 Software.....................................................................................................................................................................18
4.3.3 Hardware................................................................................................................................................................... 21
4.3.4 Others.........................................................................................................................................................................22
4.4 Operation and Maintenance..........................................................................................................................................23
4.4.1 Data Configuration.................................................................................................................................................... 23
4.4.1.1 Data Preparation..................................................................................................................................................... 23
4.4.1.2 Using MML Commands......................................................................................................................................... 30
4.4.1.3 Using the CME....................................................................................................................................................... 32
4.4.2 Activation Verification.............................................................................................................................................. 32
4.4.3 Network Monitoring.................................................................................................................................................. 32
4.4.4 Possible Issues........................................................................................................................................................... 33
5 Uplink Multiple-Antenna Reception...................................................................................... 37

5.1 Receive Diversity......................................................................................................................................................... 37
5.1.1 Principles................................................................................................................................................................... 37
5.1.2 Network Analysis...................................................................................................................................................... 37
5.1.2.1 Benefits................................................................................................................................................................... 37
Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. ii

eRAN
5.1.2.2 Impacts....................................................................................................................................................................38
5.1.3 Requirements............................................................................................................................................................. 39
5.1.3.1 Licenses.................................................................................................................................................................. 39
5.1.3.2 Software..................................................................................................................................................................39
5.1.3.3 Hardware................................................................................................................................................................ 39
5.1.3.4 Others......................................................................................................................................................................39
5.1.4 Operation and Maintenance.......................................................................................................................................39
5.2 MU-MIMO................................................................................................................................................................... 39
5.2.1 Principles................................................................................................................................................................... 40
5.2.2.1 Benefits................................................................................................................................................................... 43
5.2.2.2 Impacts....................................................................................................................................................................43
5.2.3 Requirements............................................................................................................................................................. 43
5.2.3.1 Licenses.................................................................................................................................................................. 43
5.2.3.2 Software..................................................................................................................................................................45
5.2.3.3 Hardware................................................................................................................................................................ 46
5.2.4.1 Data Configuration................................................................................................................................................. 47
5.2.4.1.1 Data Preparation.................................................................................................................................................. 47
5.2.4.1.2 Using MML Commands...................................................................................................................................... 49
5.2.4.1.3 Using the CME.................................................................................................................................................... 49
5.2.4.2 Activation Verification........................................................................................................................................... 49
5.2.4.3 Network Monitoring............................................................................................................................................... 50
5.2.4.4 Possible Issues........................................................................................................................................................ 52
6 Downlink Multiple-Antenna Transmission.......................................................................... 53

6.1 3D Beamforming.......................................................................................................................................................... 54
6.1.1 Principles................................................................................................................................................................... 54
6.1.2.1 Benefits................................................................................................................................................................... 55
6.1.2.2 Impacts....................................................................................................................................................................56
6.1.3 Requirements............................................................................................................................................................. 57
6.1.3.1 Licenses.................................................................................................................................................................. 57
6.1.3.2 Software..................................................................................................................................................................58
6.1.3.3 Hardware................................................................................................................................................................ 58
6.1.4.1.3 Using the CME.................................................................................................................................................... 60
6.1.4.4 Possible Issues........................................................................................................................................................ 61
Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. iii

eRAN
6.2 MU Beamforming.........................................................................................................................................................61
6.2.1 Principles................................................................................................................................................................... 62
6.2.2.1 Benefits................................................................................................................................................................... 66
6.2.2.2 Impacts....................................................................................................................................................................66
6.2.3 Requirements............................................................................................................................................................. 68
6.2.3.1 Licenses.................................................................................................................................................................. 68
6.2.3.2 Software..................................................................................................................................................................70
6.2.3.3 Hardware................................................................................................................................................................ 71
6.2.4.1.3 Using the CME.................................................................................................................................................... 76
6.3 TM9.............................................................................................................................................................................. 81
6.3.1 Principles................................................................................................................................................................... 81
6.3.2.1.3 Using the CME.................................................................................................................................................... 84
6.4 TM9 Hybrid Precoding.................................................................................................................................................84
6.4.1 Principles................................................................................................................................................................... 84
6.4.2.1 Benefits................................................................................................................................................................... 85
6.4.2.2 Impacts....................................................................................................................................................................85
6.4.3 Requirements............................................................................................................................................................. 86
6.4.3.1 Licenses.................................................................................................................................................................. 86
6.4.3.2 Software..................................................................................................................................................................87
6.4.3.3 Hardware................................................................................................................................................................ 88
6.4.3.4 Others......................................................................................................................................................................88
6.4.4.1.3 Using the CME.................................................................................................................................................... 89
Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. iv

eRAN
6.5 Multi-User Split SDMA............................................................................................................................................... 90

6.5.1 Principles................................................................................................................................................................... 91
6.5.2.1 Benefits................................................................................................................................................................... 94
6.5.2.2 Impacts....................................................................................................................................................................95
6.5.3 Requirements............................................................................................................................................................. 95
6.5.3.1 Licenses.................................................................................................................................................................. 95
6.5.3.2 Software..................................................................................................................................................................96
6.5.3.3 Hardware................................................................................................................................................................ 97
6.5.3.4 Others......................................................................................................................................................................97
6.5.4.1.2 Using MML Commands.................................................................................................................................... 100
6.5.4.1.3 Using the CME.................................................................................................................................................. 100
6.5.4.2 Activation Verification......................................................................................................................................... 100
6.5.4.3 Network Monitoring............................................................................................................................................. 101
6.5.4.4 Possible Issues...................................................................................................................................................... 102
6.6 PDCCH SDMA.......................................................................................................................................................... 102
6.6.1 Principles................................................................................................................................................................. 102
6.6.2 Network Analysis.................................................................................................................................................... 104
6.6.2.1 Benefits................................................................................................................................................................. 104
6.6.2.2 Impacts..................................................................................................................................................................105
6.6.3 Requirements........................................................................................................................................................... 105
6.6.3.1 Licenses................................................................................................................................................................ 105
6.6.3.2 Software................................................................................................................................................................105
6.6.3.3 Hardware.............................................................................................................................................................. 106
6.6.3.4 Others....................................................................................................................................................................106
6.6.4 Operation and Maintenance.....................................................................................................................................106
6.6.4.1 Data Configuration............................................................................................................................................... 106
6.6.4.1.1 Data Preparation................................................................................................................................................ 106
6.6.4.1.3 Using the CME.................................................................................................................................................. 108
6.6.4.4 Possible Issues...................................................................................................................................................... 109
6.7 TMA............................................................................................................................................................................110
6.7.1 Principles................................................................................................................................................................. 110
6.7.1.1 Introduction to Transmission Modes.................................................................................................................... 110
6.7.1.2 TMA Principles.....................................................................................................................................................111
6.7.1.3 Optimized TMA....................................................................................................................................................115
Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. v

eRAN
6.7.2.1 Benefits................................................................................................................................................................. 120

6.7.2.2 Impacts..................................................................................................................................................................120
6.7.3 Requirements........................................................................................................................................................... 120
6.7.3.1 Licenses................................................................................................................................................................ 120
6.7.3.2 Software................................................................................................................................................................121
6.7.3.3 Hardware.............................................................................................................................................................. 122
6.7.4.1.3 Using the CME.................................................................................................................................................. 125
6.8 Enhanced Coordinated Scheduling Based Power Control......................................................................................... 127
6.8.1 Principles................................................................................................................................................................. 127
6.8.2.1 Benefits................................................................................................................................................................. 129
6.8.2.2 Impacts..................................................................................................................................................................130
6.8.3 Requirements........................................................................................................................................................... 130
6.8.3.1 Licenses................................................................................................................................................................ 130
6.8.3.2 Software................................................................................................................................................................130
6.8.3.3 Hardware.............................................................................................................................................................. 132
6.8.3.4 Others....................................................................................................................................................................133
6.8.4.1.3 Using the CME.................................................................................................................................................. 133
6.8.4.4 Possible Issues...................................................................................................................................................... 135
7 Performance Optimization in Massive MIMO....................................................................136

7.1 Massive MIMO Load Steering................................................................................................................................... 136
7.2 PDCCH Capacity Improvement................................................................................................................................. 136
7.2.1 Principles................................................................................................................................................................. 137
7.2.2.1 Benefits................................................................................................................................................................. 138
7.2.2.2 Impacts..................................................................................................................................................................138
7.2.3 Requirements........................................................................................................................................................... 139
7.2.3.1 Licenses................................................................................................................................................................ 139
7.2.3.2 Software................................................................................................................................................................139
7.2.3.3 Hardware.............................................................................................................................................................. 140
Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. vi

eRAN

7.2.4.1.3 Using the CME.................................................................................................................................................. 141
7.3 Uplink Overload Optimization................................................................................................................................... 142
7.3.1 Principles................................................................................................................................................................. 142
7.3.2.1 Benefits................................................................................................................................................................. 143
7.3.2.2 Impacts..................................................................................................................................................................144
7.3.3 Requirements........................................................................................................................................................... 144
7.3.3.1 Licenses................................................................................................................................................................ 144
7.3.3.2 Software................................................................................................................................................................145
7.3.3.3 Hardware.............................................................................................................................................................. 145
7.3.4.1.3 Using the CME.................................................................................................................................................. 146
7.4 SRS NI Joint Suppression...........................................................................................................................................147
7.4.1 Principles................................................................................................................................................................. 147
7.4.2.1 Benefits................................................................................................................................................................. 151
7.4.2.2 Impacts..................................................................................................................................................................151
7.4.3 Requirements........................................................................................................................................................... 151
7.4.3.1 Licenses................................................................................................................................................................ 151
7.4.3.2 Software................................................................................................................................................................152
7.4.3.3 Hardware.............................................................................................................................................................. 153
7.4.4.1.3 Using the CME.................................................................................................................................................. 155
7.5 SRS Time-Domain Measurement and SDNR............................................................................................................ 156
7.5.1 Principles................................................................................................................................................................. 156
Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. vii

eRAN
7.5.2.1 Benefits................................................................................................................................................................. 157

7.5.2.2 Impacts..................................................................................................................................................................158
7.5.3 Requirements........................................................................................................................................................... 158
7.5.3.1 Licenses................................................................................................................................................................ 158
7.5.3.2 Software................................................................................................................................................................158
7.5.3.3 Hardware.............................................................................................................................................................. 159
7.5.4.1.3 Using the CME.................................................................................................................................................. 159
7.6 Beamforming Weight Optimization........................................................................................................................... 161
7.6.1 Principles................................................................................................................................................................. 161
7.6.2.1 Benefits................................................................................................................................................................. 161
7.6.2.2 Impacts..................................................................................................................................................................161
7.6.3 Requirements........................................................................................................................................................... 162
7.6.3.1 Licenses................................................................................................................................................................ 162
7.6.3.2 Software................................................................................................................................................................162
7.6.3.3 Hardware.............................................................................................................................................................. 163
7.6.4.1.3 Using the CME.................................................................................................................................................. 164
7.7 IRC..............................................................................................................................................................................165
7.7.1 Principles................................................................................................................................................................. 165
7.7.2.1 Benefits................................................................................................................................................................. 165
7.7.2.2 Impacts..................................................................................................................................................................166
7.7.3 Requirements........................................................................................................................................................... 166
7.7.3.1 Licenses................................................................................................................................................................ 166
7.7.3.2 Software................................................................................................................................................................166
7.7.3.3 Hardware.............................................................................................................................................................. 167
Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. viii

eRAN
7.7.4.1.3 Using the CME.................................................................................................................................................. 168

7.8 Scheduling Optimization............................................................................................................................................ 169
7.8.1 Principles................................................................................................................................................................. 169
7.8.2.1 Benefits................................................................................................................................................................. 171
7.8.2.2 Impacts..................................................................................................................................................................172
7.8.3 Requirements........................................................................................................................................................... 172
7.8.3.1 Licenses................................................................................................................................................................ 172
7.8.3.2 Software................................................................................................................................................................173
7.8.3.3 Hardware.............................................................................................................................................................. 173
7.8.4.1.3 Using the CME.................................................................................................................................................. 175
7.9 MU Beamforming Pairing of Antenna Selection UEs in Dual-Stream Beamforming...............................................177
7.9.1 Principles................................................................................................................................................................. 177
7.9.2.1 Benefits................................................................................................................................................................. 178
7.9.2.2 Impacts..................................................................................................................................................................179
7.9.3 Requirements........................................................................................................................................................... 179
7.9.3.1 Licenses................................................................................................................................................................ 179
7.9.3.2 Software................................................................................................................................................................180
7.9.3.3 Hardware.............................................................................................................................................................. 180
7.9.3.4 Others....................................................................................................................................................................180
7.9.4.1.3 Using the CME.................................................................................................................................................. 182
7.10 Access Control Optimization Based on Uplink and Downlink UE-Perceived Rates...............................................185
7.10.1 Principles............................................................................................................................................................... 185
7.10.2 Network Analysis.................................................................................................................................................. 185
7.10.2.1 Benefits............................................................................................................................................................... 185
7.10.2.2 Impacts................................................................................................................................................................185
7.10.3 Requirements......................................................................................................................................................... 185
Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. ix

eRAN
7.10.3.1 Licenses.............................................................................................................................................................. 185

7.10.3.2 Software..............................................................................................................................................................186
7.10.3.3 Hardware............................................................................................................................................................ 186
7.10.4 Operation and Maintenance...................................................................................................................................186
7.10.4.1 Data Configuration............................................................................................................................................. 186
7.10.4.1.1 Data Preparation.............................................................................................................................................. 186
7.10.4.1.2 Using MML Commands.................................................................................................................................. 188
7.10.4.1.3 Using the CME................................................................................................................................................ 188
7.10.4.2 Activation Verification....................................................................................................................................... 188
7.10.4.3 Network Monitoring........................................................................................................................................... 188
7.11 PDCCH Resource Reservation for Big-Packet Services in Heavy-Load Scenarios................................................ 189
7.11.1 Principles............................................................................................................................................................... 189
7.11.2.1 Benefits............................................................................................................................................................... 189
7.11.2.2 Impacts................................................................................................................................................................189
7.11.3 Requirements......................................................................................................................................................... 189
7.11.3.1 Licenses.............................................................................................................................................................. 190
7.11.3.2 Software.............................................................................................................................................................. 190
7.11.3.3 Hardware.............................................................................................................................................................190
7.11.4 Operation and Maintenance................................................................................................................................... 190
7.11.4.1.3 Using the CME................................................................................................................................................ 191
7.11.4.2 Activation Verification........................................................................................................................................191
7.12 Optimized PDCCH Aggregation Level Selection Near the Cell Center.................................................................. 191
7.12.1 Principles............................................................................................................................................................... 192
7.12.2.1 Benefits............................................................................................................................................................... 192
7.12.2.2 Impacts................................................................................................................................................................192
7.12.3 Requirements......................................................................................................................................................... 192
7.12.3.1 Licenses.............................................................................................................................................................. 192
7.12.3.2 Software..............................................................................................................................................................193
7.12.3.3 Hardware............................................................................................................................................................ 193
7.12.4.1.3 Using the CME................................................................................................................................................ 193
Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. x

eRAN
7.13 Intelligent Parameter Selection.................................................................................................................................194

7.13.1 Principles............................................................................................................................................................... 194
7.13.2.1 Benefits............................................................................................................................................................... 195
7.13.2.2 Impacts................................................................................................................................................................195
7.13.3 Requirements......................................................................................................................................................... 196
7.13.3.1 Licenses.............................................................................................................................................................. 196
7.13.3.2 Software..............................................................................................................................................................196
7.13.3.3 Hardware............................................................................................................................................................ 196
7.13.4.1.3 Using the CME................................................................................................................................................ 197
8 Parameters................................................................................................................................... 199
9 Counters...................................................................................................................................... 200
10 Glossary..................................................................................................................................... 201
11 Reference Documents............................................................................................................. 202
Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. xi

eRAN
Massive MIMO (TDD) 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 Draft A (2018-12-30)

This issue introduces the following changes to eRAN13.1 06 (2018-10-10).
Technical Changes
Change Description Parameter Change Base Station Model
Added advanced massive Added the 3900 and 5900 series base
MIMO IRC. For details, see PUSCH_RECEIVE_ENH stations
7.7 IRC. _SWITCH option to the
CellMMAlgo.MMAlgoOpt
Switch parameter.
Optimized TM9 hybrid None 3900 and 5900 series base

precoding and multi-user stations
split SDMA. For details, see
6.4 TM9 Hybrid Precoding
and 6.5 Multi-User Split
SDMA.
Added optimized switching Added the 3900 and 5900 series base
to beamforming in heavy- CellBf.HeavyLoadSwitch- stations
load scenarios. For details, ToBfOpt parameter.
see 6.7.1.3 Optimized
TMA.
Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 1

eRAN
Added optimized TMA for Added the 3900 and 5900 series base
4R and 8R UEs. For details, CellBfMimoParaCfg.Ue4R stations
see 6.7.1.3 Optimized Or8RBfMimoAdaptOptSw
TMA. parameter.
Added intelligent selection Added the 3900 and 5900 series base
of massive MIMO CellMMAlgo.MmParamInt stations
parameters (trial). For elSelectSw parameter and its
details, see 7.13 Intelligent options
Parameter Selection. BIG_EVENT_THLD_LE
ARN_SW and
BIG_EVENT_PDCCH_C
APC_ADAPT_SW.
Added moving UE Added the 3900 and 5900 series base

optimization. For details, HIGH_SPEED_OPTI_SC stations
see: HEME option to the
l 6.2.1 Principles CellBf.
MovingUeMuBfScheme
l 6.2.3.2 Software parameter.
l 6.2.4.1.1 Data
Preparation
l 6.5.3.2 Software
Added the SRS IC function. Added the 3900 and 5900 series base
For details, see 7.4 SRS NI CellUlIcAlgo.SrsIcSwitch stations
Joint Suppression. parameter.
Added support for TM9 None 5900 series base stations

hybrid precoding, multi-user
split SDMA, PDCCH
SDMA, and SRS power
control optimization in
eCPRI scenarios.

eRAN
Added the description that Added the 3900 and 5900 series base
the maximum number of NON_AS_UE_MAX_BF_ stations
beamforming layers for both RANK_CTRL_SW option
fake antenna selection UEs to the
and non-antenna selection CellBfMimoParaCfg.BfMi
UEs is fixed to 1 to prevent moAlgoOptSwitch
their entry into dual-stream parameter.
beamforming (TM8) when
MU beamforming pairing of
antenna selection UEs in
dual-stream beamforming is
enabled in massive MIMO
cells and the
NON_AS_UE_MAX_BF_
RANK_CTRL_SW option
is selected under the
CellBfMimoParaCfg.BfMi
moAlgoOptSwitch
parameter. For details, see:
l 7.9.1 Principles
l 7.9.4.1.1 Data
Preparation
l 7.9.4.1.2 Using MML
Commands
Added scheduling Added the 3900 and 5900 series base

optimization for antenna CellAlgoExtSwitch. stations
selection UEs. For details, AntennaSelectionAlgoS-
see 7.9.1 Principles. witch parameter and its
option
ANT_SEL_SCHEDULIN
G_OPT_SWITCH.
Added tilt fine-tuning Added the 3900 and 5900 series base
corresponding to the BfAnt.TiltFractionalPart stations
beamforming weight. For parameter.
details, see 4.4.1.1 Data
Preparation.
Added remote AAU Added the 3900 and 5900 series base
azimuth adjustment. For BfAnt.BfantBearing stations
details, see 4.4.1.1 Data parameter.
Preparation.
Added beamforming weight Added the 3900 and 5900 series base
granularity optimization. BF_WEIGHT_GRAN_OP stations
For details, see 6.1.4.1.1 T_SWITCH option to the
Data Preparation and CellBfMimoParaCfg.BfMi
6.1.4.1.2 Using MML moAlgoOptSwitch
Commands. parameter.

eRAN
Added MU beamforming Added the 3900 and 5900 series base

adaptive power CellBf.MubfPowerNormAd stations
normalization. For details, ptFactor parameter.
see 6.2.4.1.1 Data
Preparation and 6.2.4.1.2
Using MML Commands.
Added access control Added the 3900 and 5900 series base
optimization based on MM_ACCESS_CONTRO stations
uplink and downlink UE- L_OPT_SWITCH option
perceived rates. For details, to the
see 7.10 Access Control CellMMAlgo.MMAlgoOpt
Optimization Based on Switch parameter.
Uplink and Downlink UE-
Perceived Rates.
Added PDCCH resource Added the 3900 and 5900 series base
reservation for big-packet HEAVY_LOAD_BIG_PK stations
services in heavy-load T_SCH_OPT_SW option
scenarios. For details, see to the
section 7.11 PDCCH CellPdcchAlgo.PdcchOpti
Resource Reservation for mizationSwitch parameter.
Big-Packet Services in
Heavy-Load Scenarios.
Added optimized PDCCH Added the 3900 and 5900 series base
aggregation level selection HEAVY_LOAD_BIG_PK stations
near the cell center. For T_SCH_OPT_SW option
details, see 7.12 Optimized to the
PDCCH Aggregation CellPdcchAlgo.PdcchOpti
Level Selection Near the mizationSwitch parameter.
Cell Center.
Added mutually exclusive None 3900 and 5900 series base

relationships between stations
massive MIMO and low-
efficiency UE transfer. For
details, see 4.3.2 Software.
Added the TM8 pairing Added the 3900 and 5900 series base
optimization function. For CellBf.Tm8PairingOptSwit stations
details, see 7.9 MU ch parameter.
Beamforming Pairing of
Antenna Selection UEs in
Dual-Stream
Beamforming.

eRAN
Modified the configuration None 3900 and 5900 series base

suggestions for the stations
CellMMAlgo.SplitSdmaUe
IdenSrsSinrThld parameter
in multi-user SDMA
scenarios. For details, see
6.5.4.1.1 Data Preparation
and 6.5.4.1.2 Using MML
Commands.
Added support of the None 3900 and 5900 series base

UBBPf3 for massive stations
MIMO. For details, see
4.3.3 Hardware.
Added support of UEs in Added the 3900 and 5900 series base
dual-stream beamforming CellBf.DualStreamBfAlgoS stations
(TM8) for multiplexing w parameter and its option
feedback mode. For details, ACK_FEEDBACK_IN_M
see 7.9.1 Principles. UX_MODE_SW.
Modified the configuration None 3900 and 5900 series base

suggestions for the stations
CellCsiRsParaCfg.CsiRsS
witch,
CellDlschAlgo.CsiRsSfSch
StrSwitch, and
CellCsiRsParaCfg.CsiRsPe
riod parameters. For details,
see 6.3.2.1.1 Data
Preparation.
Added MCS index selection None 5900 series base stations

optimization for the
UBBPfw1. For details, see
5.2.3.3 Hardware.
Added support of the None 5900 series base stations

AAU5613 and UBBPfw1
for massive MIMO. For
details, see 4.3.3 Hardware.
Added the restriction that None 5900 series base stations

the UBBPfw1 does not
support SRS power control
optimization. For details,
see 7.4.3.3 Hardware.

eRAN
Added the restriction that None 5900 series base stations

CPRI compression is not
supported in eCPRI
networking scenarios. For
details, see 4.4.1.1 Data
Preparation.
Added the mutually None 3900 and 5900 series base

exclusive relationship stations
between massive MIMO
and interference
coordination for cells with
uplink-downlink subframe
configuration 1 or 2. For
details, see 4.3.2 Software.
Added enhanced None 3900 and 5900 series base

coordinated scheduling stations
based power control (trial).
For details, see 6.8
Enhanced Coordinated
Scheduling Based Power
Control.
Changed the name of None 3900 and 5900 series base

Huawei mobile element stations
management system from
U2000 to U2020.
Added massive MIMO Added the 3900 and 5900 series base
uplink overload MmUlHeavyLoadOptS- stations
optimization. For details, witch option to the
see 7.3 Uplink Overload CellUlschAlgo.VmimoOptA
Optimization. lgoSwitch parameter.
Added MCS index selection Added the 3900 and 5900 series base
optimization for downlink MM_DL_SCH_AND_MC stations
paired UEs with small- S_OPT_SWITCH option to
amount data transmission the
and cell-level outer-loop CellMMAlgo.MMAlgoOpt
adjustment optimization in Switch parameter.
beamforming. For details,
see 7.8 Scheduling
Optimization.

eRAN
Replaced the l Added the 3900 and 5900 series base

eNBCellRsvdPara.RsvdU8 TM9SplitSdmaSwitch stations
Para26 parameter with the option to the
TM9SplitSdmaSwitch and CellAlgoSwitch.MuBfA
CellMMAlgo.SplitSdmaBe lgoSwitch parameter.
amRsrpIsltnThld options l Added the
under the CellMMAlgo.SplitSdma
CellAlgoSwitch.MuBfAlgo BeamRsrpIsltnThld
Switch parameter. For parameter.
details, see:
l 6.5.1 Principles
l 6.5.4.1.1 Data
Preparation
l 6.5.4.1.2 Using MML
Commands
Added MU beamforming Added the 3900 and 5900 series base

pairing of antenna selection FakeAntSelIdentifica- stations
UEs in dual-stream tionSwitch option to the
beamforming. For details, CellAlgoSwitch.BfAlgoSwi
see the following sections: tch parameter.
l 6 Downlink Multiple-
Antenna Transmission
l 6.7.1.1 Introduction to
Transmission Modes
l 6.7.1.2 TMA Principles
l 6.7.1.3 Optimized TMA
l 7.9 MU Beamforming
Pairing of Antenna
Selection UEs in Dual-
Stream Beamforming
Editorial Changes
Revised descriptions in this document.

eRAN
Massive MIMO (TDD) 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.
Feature Differences Between RATs

The feature difference section only describes differences in switches or principles.
Unless otherwise stated, descriptions in this document apply to all RATs. If a description does
not apply to all RATs, the specific RAT that it does apply to will be stated.
For example, in the statement "TDD cells are compatible with enhanced MU-MIMO", "TDD
cells" indicates that this function cannot be used in non-TDD cells.
2.2 Applicable RAT

This document applies to TDD.
2.3 Features in This Document

This document describes the following TDD features.
Feature ID Feature/Function Name Section
TDLEOFD-121601 Massive MIMO See the corresponding

Introduction sections of the subfeatures.
TDLEOFD-12160101 Flexible Active-Unit 4 Basic Massive MIMO

Management Functions
TDLEOFD-12160102 Adaptive Transmission 4 Basic Massive MIMO

Mode Functions
TDLEOFD-12160103 Dynamic SRS Allocation 4 Basic Massive MIMO

Functions
TDLEOFD-12160104 Power Beamforming 4 Basic Massive MIMO

Functions
TDLEOFD-12160105 Antenna Fault Detection 4 Basic Massive MIMO

Functions
TDLEOFD-13160107 BF Weight Optimization 7.6 Beamforming Weight

Optimization
TDLEOFD-15060109 Massive MIMO Uplink 7.3 Uplink Overload

Overload Optimization Optimization

eRAN
Feature ID Feature/Function Name Section
TDLEOFD-121603 64T64R Massive MIMO See the corresponding

Basic Package sections of the subfeatures.
TDLEOFD-12160301 UL 64-Antenna Receive 5.1 Receive Diversity

Diversity
TDLEOFD-12160302 UL 2x64 MU-MIMO 5.2 MU-MIMO
TDLEOFD-121609 UL 4-Layer MU-MIMO 5.2 MU-MIMO
TDLEOFD-121610 UL 8-Layer MU-MIMO 5.2 MU-MIMO
TDLEOFD-121615 DL Flexible 3D- 6.1 3D Beamforming

Beamforming
TDLEOFD-121604 DL 8-Layer MU- 6.2 MU Beamforming

Beamforming

Beamforming

Beamforming (Trial)
TDLEOFD-131615 Massive MIMO TM9 6.4 TM9 Hybrid Precoding

Hybrid Precoding
TDLEOFD-131612 Multi-User Split SDMA in 6.5 Multi-User Split

Massive MIMO SDMA
TDLEOFD-121613 PDCCH SDMA in Massive 6.6 PDCCH SDMA

MIMO
TDLEOFD-150604 Enhanced Coordinated 6.8 Enhanced Coordinated

Scheduling Based Power Scheduling Based Power
Control (Trial) Control
TDLEOFD-131614 SRS NI Joint Suppression 7.4 SRS NI Joint

Suppression
TDLEOFD-150613 Advanced Massive MIMO 7.7 IRC

IRC
TDLEOFD-151616 Intelligent Selection of 7.13 Intelligent Parameter

Massive MIMO Parameters Selection
(Trial)
NOTE
The features described in 4 Basic Massive MIMO Functions and 5.1 Receive Diversity are
prerequisites for setting up massive MIMO cells. The operation and maintenance (O&M) of the features
are described in 4.4 Operation and Maintenance.

eRAN
Massive MIMO (TDD) Feature Parameter Description 3 Overview
3 Overview
3.1 Introduction
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, significantly improving system capacity and 3D coverage.
The following figure shows hardware evolution from traditional MIMO sites to massive
MIMO sites.
Figure 3-1 Hardware evolution of massive MIMO

eRAN
Table 3-1 Function evolution from traditional MIMO to massive MIMO
Category Traditional MIMO Massive MIMO
Broadcast Beamforming Beamwidth can be adjusted Beamwidth can be adjusted

only on the horizontal plane. on both the horizontal and
vertical planes, improving
vertical-plane network
coverage.
Uplink multiple-antenna Up to eight antennas can be Up to 64 antennas can be

receive diversity (receive used for uplink receive used for uplink receive
diversity for short) diversity. diversity.
Uplink multi-user MIMO Up to four layers can share Up to eight layers can share
(MU-MIMO for short) the same time-frequency the same time-frequency
resource. resource.
Downlink single-user Traffic beamwidth can only Traffic beamwidth can be

beamforming (SU be adjusted horizontally. adjusted both horizontally
beamforming for short) and vertically, enhancing the
beamforming accuracy.
Downlink multi-user Up to four layers can share A maximum of 16 layers

beamforming (MU the same time-frequency (24 layers are available only
beamforming for short) resource. for trial)
Multi-user split SDMA in None Physical Downlink Shared

Massive MIMO (multi-user Channel (PDSCH) beams
split SDMA for short) are split, enabling
independent-scheduling UEs
served by different PDSCH
beams to reuse the same
PDSCH resource for data
transmission.
Massive MIMO TM9 hybrid Wide beam weighting, l Horizontal-plane

precoding (TM9 hybrid which performs weighting: The beam is
precoding for short) beamforming based on the divided into multiple
precoding matrix indication orthogonal beams. Each
(PMI) feedback of the UE beam is configured with
independent, measurable
channel state
information-reference
signals (CSI-RSs). The
eNodeB selects the
weighting value with the
best beamforming
capability based on the
channel state.
l Vertical-plane weighting,
which performs
beamforming based on
the PMI feedback of the
UE

eRAN
Category Traditional MIMO Massive MIMO
PDCCH SDMA in massive None Physical downlink control

MIMO (PDCCH SDMA for channel (PDCCH) beams
short) are split, enabling
independent-scheduling UEs
served by different PDCCH
beams to reuse the same
PDCCH resource for data
transmission.
NOTE
For details about traditional MIMO, see MIMO and Beamforming (TDD).
3.2 Application Scenarios

The main benefit of massive MIMO lies in improved cell coverage and capacity. A massive
MIMO site can be deployed on a new site or by reconstructing existing sites. Massive MIMO
is typically deployed in hotspot areas and for covering tall buildings.
l Hotspot coverage
In typical hotspot areas, user density is high and many online UEs create extremely
strong demand for capacity in both the uplink and the downlink. Typical hotspots include
dense urban areas, central business districts (CBDs), public squares, and stadiums.
Massive MIMO can improve system capacity through spatial multiplexing. Up to 8
layers in the uplink for MU-MIMO pairing and up to 16 layers in the downlink for MU
beamforming pairing significantly improve the cell throughput and meet capacity
demands in hotspot areas.
l Tall-building coverage
In tall buildings, users are distributed across many floors, and a normal site cannot
extend coverage vertically very far. The vertical beamwidth (approximately 6.5°) makes
it impossible for a traditional site to cover multiple floors.
Massive MIMO enables the eNodeB to adjust the vertical broadcast beamwidth to up to
35°, enhancing vertical coverage of broadcast beams. In this way, more floors can be
covered by a single site. Massive MIMO strengthens power, array, and diversity gains,
and enables energy to be more concentrated by implementing 3D beamforming on traffic
beams. The gains offset the propagation and penetration losses and improve the link
quality for indoor UEs in tall buildings.
Figure 3-2 Massive MIMO and multi-floor coverage

eRAN
Massive MIMO (TDD) Feature Parameter Description 4 Basic Massive MIMO Functions
4 Basic Massive MIMO Functions
4.1 Principles
Basic massive MIMO functions include broadcast beamforming and TDLEOFD-121601
Massive MIMO Introduction. TDLEOFD-121601 Massive MIMO Introduction is a
prerequisite for activating a massive MIMO cell.
Broadcast Beamforming
Broadcast beamforming enables the eNodeB to apply weighting on broadcast beams to adjust
their coverage scope.
The weighting designed for typical coverage scenarios has been written into the beam weight
file, which is included in the eNodeB software package. After the beam weight file is
activated, the eNodeB configures broadcast beamwidth on both the horizontal and vertical
planes based on the setting of the BfAnt.CoverageScenario parameter, satisfying broadcast
coverage demands in various application scenarios. A vertical beamwidth of up to 35°
significantly improves the vertical coverage scope in tall buildings.
TDLEOFD-12160105 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 identified based on the values of the
TX Channel Numbers In The Cell and RX Channel Numbers In The Cell parameters.
This feature is free from parameter control. It is enabled by default for massive MIMO cells.
TDLEOFD-12160101 Flexible Active-Unit Management

To enhance system reliability, the following flexible active-unit management policy is
supported in massive MIMO scenarios:
l The cell can still work properly as long as 32 or more antennas are operational. However,
faulty antennas may cause network performance, such as the cell throughput, to
deteriorate. The impact is directly proportionate to the number of faulty antennas.

eRAN
l If fewer than 32 antennas remain operational, the massive MIMO cell is deactivated.
l If more than eight antennas are faulty, neither PDCCH SDMA in massive MIMO nor
multi-user split SDMA takes effect.
TDLEOFD-12160102 Adaptive Transmission Mode

This feature enables UEs to work in a transmission mode that delivers the highest spectral
efficiency for any given set of channel conditions. This feature provides significantly better
average cell throughput than fixed transmission modes.
The CellBfMimoParaCfg.BfMimoAdaptiveSwitch parameter controls the TMA policy.
For details about TMA, see 6.7 TMA.
TDLEOFD-12160103 Dynamic SRS Allocation

UE services are classified as either heartbeat, heavy-traffic, or normal services. Online UEs
always use sounding reference signal (SRS) resources, regardless of whether services are
running or not. Beamforming requires short-period SRS resources. If the UEs running only
heartbeat services consume short-period SRS resources, the beamforming performance for
heavy-traffic UEs is affected.
When service-based dynamic SRS allocation is enabled, massive MIMO cells allocate long-
period SRS resources to UEs performing heartbeat services in order to save short-period SRS
resources and allocate more short-period SRS resources to the UEs performing heavy-traffic
services while retaining the SRS policy for UEs performing normal services. In this way, SRS
resource allocation is optimized, improving beamforming performance.
This function is controlled by the SrvBasedSRSAdjAlgo option under the
SRSCfg.SrsCfgPolicySwitch parameter. When this option is selected, the massive MIMO cell
identifies UE service types and then reserves SRS resources for the UEs that are performing
heavy-traffic services within a fixed period. The reserved SRS resources are not available for
the UEs that initially access the network or perform heartbeat services.
Heartbeat, heavy-traffic, and normal services are identified as follows:
l Heartbeat
Heartbeat services include periodical messaging and only a small number of packets are
exchanged each time. The cell identifies a service as the heartbeat service by comparing
the length and volume of the packet transmission to corresponding parameters. Heartbeat
services meet the following two conditions:
– The length of any IP packet transmitted within 2s of a Radio Resource Control
(RRC) connection setup does not exceed the threshold specified by the
ServiceIdentifyPara.HeartbeatPacketLengthThld parameter.
– The cumulative number of IP packets transmitted within 2s of an RRC connection
setup does not exceed the threshold specified by the
ServiceIdentifyPara.HeartbeatPacketNumberThld parameter.
l Heavy-traffic
Heavy-traffic services are those with a high proportion of large packets, services such as
video or file download. The cell identifies a service as the heavy-traffic service when the
following conditions are met within the measurement period specified by the
ServiceIdentifyPara.MassFlowDuration parameter:

eRAN
– The proportion of downlink large IP packets is greater than the threshold specified
by the ServiceIdentifyPara.MassFlowBigPacketRateThld parameter.
– The cumulative number of downlink IP packets is greater than the threshold
specified by the ServiceIdentifyPara.MassFlowPacketNumberThld parameter.
l Normal
All other services are considered normal services.
TDLEOFD-12160104 Power Beamforming

Power beamforming enables the eNodeB to adjust the phases and amplitudes based on beam
weights in massive MIMO scenarios. The eNodeB calculates the weighting for each RF
channel of the AAU using a beamforming algorithm. It then allocates transmit power to each
RF channel based on the amplitude corresponding to the weighting, improving the channel
power efficiency and the downlink user experience rate.
4.2 Network Analysis
4.2.1 Benefits
This feature increases power and array gains. Massive MIMO enables the eNodeB to adjust
broadcast beams and downlink traffic beams both horizontally and vertically. It achieves
better uplink and downlink coverage performance than 8T8R multiple-antenna technologies.
The gains are more significant on the vertical plane.
NOTE
l For details about the power and array gains, see Beamforming (TDD).
l For 3.5 GHz massive MIMO cells, it is recommended that inter-frequency split be enabled so that a
single site can provide six sectors using two frequencies, improving cell coverage. For details about
inter-frequency split, see Soft Split Resource Duplex (TDD).
4.2.2 Impacts
Network Impacts
l System capacity
This feature improves the average cell capacity, peak cell throughput, average single-UE
throughput, and CEU throughput in both the uplink and downlink.
l Network performance
– This feature improves network coverage in both the uplink and downlink.
– Massive MIMO cells have a larger target SRS power for SRS power control than
normal cells. This increases the downlink spectral efficiency and cell throughput as
well as SRS interference.

eRAN
Function Impacts
Function Function Switch Reference Description
Name
DL CoMP cell IntraDlCompSwitch DL CoMP Massive MIMO cells

option under the (TDD) cannot be added to intra-
CellAlgoSwitch.DlComp eNodeB Downlink
Switch parameter Coordinated Multipoint
Transmission (DL
CoMP) clusters.
Inter-eNodeB InterDlCompDcsSwitch DL CoMP Only the dynamic cell

DL CoMP and InterDlCompCbfS- (TDD) selection (DCS) mode is
witch options under the available for inter-
CellAlgoSwitch.DlComp eNodeB DL CoMP in
Switch parameter massive MIMO
scenarios.
MCS selection SmallPktMcsSelectAl- Scheduling Modulation and Coding

for transmission goSw option under the Scheme (MCS) index
of small CellAlgoSwitch.DlSchS selection for transmission
amounts of data witch parameter of small amounts of data
does not take effect for
UEs that have been
paired for massive
MIMO.
4.3 Requirements
4.3.1 Licenses
Feature ID Feature Name Model Sales Unit
TDLEOFD-121601 Massive MIMO LT1SMSMMID00 Per Cell

Introduction
NOTE
For details about the capacity license usage of a massive MIMO cell, see License Management.

eRAN
4.3.2 Software
Prerequisite Functions
Name
Subframe Cell.SpecialSubframe- Subframe Massive MIMO cells

configurations Patterns Configuration support only the
Cell.SubframeAssignme (TDD) following subframe
nt configuration
combinations: uplink-
downlink subframe
configurations 2+special
subframe configurations
5, uplink-downlink
1+special subframe
configurations 7, and
uplink-downlink
2+special subframe
configurations 7.
Mutually Exclusive Functions

Function Name Function Switch Reference Description
Extended CP Cell.UlCyclicPrefix Extended CP None

Cell.DlCyclicPrefix
TTI bundling TtiBundlingSwitch VoLTE According to 3GPP

option under the specifications, TTI
CellAlgoSwitch.UlS bundling is not
chSwitch parameter compatible with
uplink-downlink
subframe
configuration 2.
Massive MIMO
cells do not support
TTI bundling when
uplink-downlink
subframe
configuration 2 is
used.
Adaptive ICIC None Adaptive ICIC None
SFN cell Cell.MultiRruCellM SFN None

ode

eRAN
High speed mobility Cell.HighSpeedFla High Speed Mobility None

g
eMBMS CellMBMSCfg.MB eMBMS None

MSSwitch
Interference UlInterfSuppres- Interference When a UBBPf1 is

detection and sionSwitch option Detection and used, massive
suppression under the Suppression MIMO is not
CellAlgoSwitch.Avo compatible with this
idInterfSwitch function.
parameter
Remote interference CellRicAlgo.Remot Interference Massive MIMO is

adaptive avoidance eInfAdpAvoidSwitc Detection and suitable for dense
h Suppression urban areas, while
CellRicAlgo.DuctD remote interference
LSubfrmShutoffS- adaptive avoidance
witch is applicable in wide
coverage scenarios.
CellRicAlgo.DuctD
LSubfrmShutoffOpt
Sw
Intra-eNodeB UL UlCamcSw option Uplink Coordinated None

CAMC under the Scheduling
CellAlgoSwitch.Ca
mcSwitch parameter
Intra-frequency split N/A Soft Split Resource None

Duplex (TDD)
Uplink SU-MIMO ULSUMIMO2Laye MIMO None

rsSwitch option
under the
CellAlgoSwitch.UlS
uMimoAlgoSwitch
parameter
Downlink D-MIMO DmimoJTSwitch D-MIMO (TDD) None

and
DmimoSchAttriOp
tSwitch options
under the
CellAlgoSwitch.D
MIMOAlgoSwitch
parameter

eRAN
Inter-cell downlink InterCellDmimoJT D-MIMO (TDD) None

D-MIMO Switch option under
the
CellAlgoSwitch.D
MIMOAlgoSwitch
parameter
Cell radius greater None Extended Cell Massive MIMO

than 15 km Range cells are suitable in
densely populated
urban areas, where
network coverage
extension is not
suitable.
Downlink 4x4 None MIMO None

MIMO
Turbo receiver CellAlgoSwitch.Tur Turbo Receiver None

boReceiverSwitch
UL CoMP cell UlJointReceptionS- UL CoMP None

witch option under
the
CellAlgoSwitch.Upl
inkCompSwitch
parameter
ePDCCH CellPdcchAlgo.Epd Physical Channel None

cchAlgoSwitch Resource
Management
eMTC introduction EMTC_SWITCH eMTC None

option under the
CellEmtcAlgo.Emtc
AlgoSwitch
parameter
Turbo beamforming TurboBfSwitch WTTx Turbo None

option under the Beamforming (TDD)
CellAlgoSwitch.Mu
BfAlgoSwitch
parameter
In-band relay InBandRelayDeNb Relay None

Switch and
InBandRelayReNb
Switch options of
the
CellAlgoSwitch.Rel
aySwitch parameter

eRAN
Interference Sa1Sa2InterfCoord Subframe None

coordination for Switch option under Configuration
cells with uplink- the (TDD)
downlink subframe CellAlgoSwitch.Avo
configuration 1 or 2 idInterfSwitch
parameter
4.3.3 Hardware
Base Station Models

3900 and 5900 series base stations
Boards
l BBU: BBU3910 or BBU5900
l BBPs
– UBBPem
– UBBPf1
– UBBPf3
– UBBPfw1 (only available in the BBU5900)
l Main control board: UMPTe
NOTE
For details about the maximum number of BBPs supported by each BBU and the maximum number of
massive MIMO cells supported by each BBP, see the hardware description of the corresponding BBU.
RF Modules
l AAU5271
l AAU5281
l AAU5613 (compatible only with the UBBPfw1 and UBBPf3)
Cells
The following table describes the frequency, cell bandwidth, and subframe configurations
supported by each RF module.
NOTE
l The UBBPf1, UBBPf3, or UBBPfw1 does not support uplink-downlink subframe configuration 1.
l Special subframe configuration 5 can be used only with uplink-downlink subframe configuration 2,
not with uplink-downlink subframe configuration 1.

eRAN
RF Module Frequency Cell Uplink- Special

Bandwidth Downlink Subframe
Subframe Configuration
Configuration
AAU5271 2.3 GHz (2300 10 MHz, 15 1 or 2 5 or 7

MHz to 2400 MHz, and 20
MHz) MHz
AAU5271 2.3 GHz (2350 10 MHz, 15 1 or 2 5 or 7

MHz) MHz
AAU5271 2.6 GHz (2496 10 MHz, 15 1 or 2 5 or 7

MHz) MHz
AAU5271 2.6 GHz (2560 10 MHz, 15 1 or 2 5 or 7

MHz) MHz
AAU5281 3.5 GHz (3445 10 MHz, 15 1 or 2 5 or 7

MHz) MHz
AAU5613 3400 MHz to 10 MHz, 15 2 5 or 7

(compatible 3600 MHz MHz, and 20
only with the 3600 MHz to MHz
UBBPfw1 and 3800 MHz
UBBPf3)
4.3.4 Others
Due to new functions or features, new beam weight files may be introduced in the new
software version after an upgrade. When upgrading or rolling back the software version,
perform operations on the beam weight file according to the following table.
Table 4-1 Precautions for software upgrade and rollback

Scenario Upgrade Precautions Rollback Precautions
The new beam weight file is The beam weight file does The original beam weight
not used in the target not need to be activated. file does not need to be
software version. activated.
The new beam weight file is Run the ACT BFANTDB Run the ACT BFANTDB
used in the target software command to reactivate the command to activate the
version. beam weight file. original beam weight file.

eRAN
NOTE
If a new beam weight file is installed after a software upgrade and then a software rollback is performed:
l Before the original beam weight file is activated, the new beam weight file is still stored in the
eNodeB.
l After the old beam weight file is activated, the new beam weight file is deleted.
4.4 Operation and Maintenance

Massive MIMO cell setup requires that TDLEOFD-121601 Massive MIMO Introduction and
TDLEOFD-12160301 UL 64-Antenna Receive Diversity be activated. This section describes
O&M details for the two features.
4.4.1 Data Configuration
4.4.1.1 Data Preparation
Configuring Massive MIMO Cell Data

This part lists only parameter settings of massive MIMO cell setup that are different from
those of normal cell setup. Configure the following parameters based on the setting notes.
Table 4-2 Configuring massive MIMO cell data
Parameter Name Parameter ID Setting Notes
Protocol Type EQUIPMENT.PROTO Set this parameter to CPRI.

COL
Board Type BT If a UBBPfw1 is used, set this

parameter to UBBP-W.
CPRI Interface Type BBP.CPRIITFTYPE If a UBBPfw1 is used and the BT

parameter is set to UBBP-W by
running the ADD BRD command,
leave this parameter unspecified. If
the BBP of another type is used,
set this parameter to CPRI_QSFP.
Board Specification BRDSPEC This parameter must be set to

UBBPf1 for a UBBPf1.
Otherwise, two CPRI ports,
instead of three, are displayed for
the UBBPem on the CME device
panel.
Topo Type RRUCHAIN.TT Set this parameter to

TRUNK_CHAIN.
Access Type RRUCHAIN.AT Set this parameter to

LOCALPORT.

eRAN
Connect Port Num RRUCHAIN.CONNPO Set this parameter to 1 or 2.

RTNUM
Port 1 Slot No. RRUCHAIN.CONNSN Set this parameter to the slot

1 number of the board of which port
1 connects to the trunk chain.
Port 1 Port No. RRUCHAIN.CONNPN Set this parameter to the CPRI port
1 number 1 of the trunk chain.
Port 2 Slot No. RRUCHAIN.CONNSN Set this parameter to the slot

2 number of the board of which port
2 connects to the trunk chain.
Port 2 Port No. RRUCHAIN.CONNPN Set this parameter to the CPRI port
2 number 2 of the trunk chain.
Protocol Type RRUCHAIN.PROTOC l CPRI networking: Set this

OL parameter to CPRI.
l eCPRI networking: Set this
parameter to eCPRI.
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 TDL.
Number of RX channels RRU.RXNUM Set this parameter to 0.
Number of TX channels RRU.TXNUM Set this parameter to 0.
Maintenance Mode RRU.MNTMODE Set this parameter to NORMAL.
RF DC Power Off Alarm RRU.RFDCPWROFFA Set this parameter to OFF.

Detect Switch LMDETECTSW
Antenna Number SECTOR.ANTNUM Set this parameter to 0.
Create Default Sector SECTOR.CREATESEC Set this parameter to FALSE.

Equipment TOREQM
Antenna Config Mode SECTOREQM.ANTCF Set this parameter to BEAM.

GMODE
Beam Shape SECTOREQM.BEAMS Set this parameter to

HAPE SEC_120DEG.
Beam Layer Split SECTOREQM.BEAML Set this parameter to None.

AYERSPLIT
Beam Azimuth Offset SECTOREQM.BEAMA Set this parameter to None.

ZIMUTHOFFSET
Uplink bandwidth Cell.UlBandWidth Set this parameter to

CELL_BW_N50,

eRAN
Downlink bandwidth Cell.DlBandWidth CELL_BW_N75, or

CELL_BW_N100.
Subframe assignment Cell.SubframeAssignme Set this parameter to SA1 or SA2.

nt NOTE
The UBBPf1, UBBPf3, or UBBPfw1
does not support uplink-downlink
subframe configuration 1.
Special subframe Cell.SpecialSubframe- Set this parameter to SSP5 or

patterns Patterns SSP7.
NOTE
Special subframe configuration 5 can
be used only with uplink-downlink
subframe configuration 2, not with
uplink-downlink subframe
configuration 1.
CPRI Compression Cell.CPRICompression l If an AAU is connected to a

UBBPf3 or UBBPfw1, set this
parameter to
NO_COMPRESSION.
l If the AAU is connected to a
UBBPf1, set this parameter to
NORMAL_COMPRESSION
or
ENHANCED_COMPRESSI
ON.
l If an AAU is connected to a
UBBPem:
– Set this parameter to
NORMAL_COMPRESSI
ON in 10 MHz cells.
ENHANCED_COMPRES
SION in 15 MHz cells.
ENHANCED_COMPRES
SION in 20 MHz cells.
CRS Port Number Cell.CrsPortNum Set this parameter to

CRS_PORT_1 or CRS_PORT_2.
Cell transmission and Cell.TxRxMode Set this parameter to 64T64R.

reception mode
Baseband equipment ID BASEBANDEQM.BAS None

EBANDEQMID
Baseband Equipment BASEBANDEQM.BAS Set this parameter to ULDL.

Type EBANDEQMTYPE

eRAN
UMTS UL BASEBANDEQM.UMT Set this parameter to NULL.

Demodulation Mode SDEMMODE
Local cell ID EUCELLSECTOREQ None

M.LocalCellId
Sector equipment ID EUCELLSECTOREQ Set this parameter according to the

M.SectorEqmId sector equipment ID configured in
the SECTOREQM MO.
Baseband equipment ID EUCELLSECTOREQ Set this parameter according to the

M.BaseBandEqmId baseband equipment ID configured
in the BASEBANDEQM MO.
Configuring Weights for Broadcast Beams

Massive MIMO requires the weighting of broadcast beams to be configured. The MOs and
parameters in the following tables must be configured based on site conditions.
Before configuring a beamforming antenna, run the ACT BFANTDB command with the
OPMODE parameter set to SWFILE to activate the beam weight file.
Table 4-3 Weight parameters for broadcast beams
Device No. BfAnt.DeviceNo Set this parameter based on the

network plan.
Connect RRU subrack BfAnt.ConnSRN Set this parameter to the number

No. of the subrack where the RF
module to be added resides.
Antenna model number BfAnt.MODELNO Set this parameter based on actual

antenna information, which can be
queried by running the DSP
BFANTDB command.
Tilt BfAnt.Tilt Downtilt = BfAnt.Tilt + 0.1 x

BfAnt.TiltFractionalPart
For example:
l If the BfAnt.Tilt parameter is
set to 1 and the
parameter is set to 9, the
downtilt is 1.9°.

eRAN
Tilt Fractional Part BfAnt.TiltFractionalPar l If the BfAnt.Tilt parameter is

t set to 1 and the
parameter is set to -9, the
downtilt is 0.1°.
set to -1 and the
parameter is set to 9, the
downtilt is -0.1°.
set to -1 and the
parameter is set to -9, the
downtilt is -1.9°.
Band BfAnt.Band Set this parameter according to the

value of the Cell.FreqBand
parameter.
Coverage Scenario BfAnt.CoverageScenari Set this parameter based on site

o conditions.
NOTICE
When this parameter is set to
SCENARIO_10, SCENARIO_11,
SCENARIO_12, or SCENARIO_13,
the vertical beamwidth of the massive
MIMO cell equals that of a single
channel. In this situation, changing
the value of the BfAnt.Tilt parameter
almost has no impact on the network.
Weight Number eUCellSectorEqm.Weig Set this parameter based on the

htNO value of the BfAnt.DeviceNo
parameter. This parameter must
not be set to 255.

eRAN
BFANTBEARING BfAnt.BfantBearing In massive MIMO cells, the value

range of this parameter is from -30
to 30.
l If the
BfAnt.CoverageScenario
parameter is set to
SCENARIO_1 or
SCENARIO_5, it is
recommended that this
parameter be set to 0.
l If the
parameter is set to
SCENARIO_2,
SCENARIO_6, or
SCENARIO_10, it is
parameter be set to a value
ranging from -10 to 10.
l If the
parameter is set to
SCENARIO_3,
SCENARIO_7, or
SCENARIO_11, it is
l If the
parameter is set to
SCENARIO_4,
SCENARIO_8,
SCENARIO_9,
SCENARIO_12, or
SCENARIO_13, it is

eRAN
Dynamic SRS Allocation
Table 4-4 Parameters related to service-based dynamic SRS allocation

SRS Configure Policy SRSCfg.SrsCfgPolicySw Select the SrvBasedSRSAdjAlgo

Switch itch option when there are 200 to 500
UEs in a massive MIMO cell.
Heartbeat Packet Length ServiceIdentify- If this parameter is set to a small

Threshold Para.HeartbeatPacket- value, a small number of services
LengthThld are identified as heartbeat services.
Set this parameter to 180.
Heartbeat Packet ServiceIdentify- If this parameter is set to a small

Number Threshold Para.HeartbeatPacket- value, a small number of services
NumberThld are identified as heartbeat services.
The value 4 is recommended.
Mass Flow Monitor ServiceIdentify- If this parameter is set to a small

Duration Para.MassFlowDuratio value, the eNodeB identifies
n heavy-traffic services quickly but
less accurately. The value 2 is
recommended.
Mass Flow Big Packet ServiceIdentify- If this parameter is set to a small

Rate Threshold Para.MassFlowBigPack value, a large number of services
etRateThld are identified as heavy-traffic
services. The value 80 is
recommended.
Mass Flow Packet ServiceIdentify- If this parameter is set to a small

Number Threshold Para.MassFlowPacketN value, a large number of services
umberThld are identified as heavy-traffic
services. The value 200 is
recommended.
Cell Algorithm Switches
Table 4-5 Parameters in the CELLALGOSWITCH MO

IRC Switch CellAlgoSwitch.IrcSwitc l Clear the PrachIrcSwitch

h option under this parameter in
massive MIMO scenarios.
l Select the PucchIrcSwitch
option under this parameter in
interference scenarios.

eRAN
Uplink schedule switch CellAlgoSwitch.UlSchS Clear the PrachRbReuseSwitch

witch option under this parameter in
massive MIMO scenarios.
4.4.1.2 Using MML Commands
Activation Command Examples

This section provides MML command examples for setting up a massive MIMO cell. The
MML commands for configuring transmission data for a massive MIMO cell are the same as
those for a normal cell, and therefore are not provided here.
The following operations are not required when a massive MIMO cell is to be set up at an
existing site:
l Activating the minimum configuration
l Configuring operator information
l Configuring clock information
l Configuring the local time zone and DST information
//Downloading and activating the eNodeB software

DLD SOFTWARE: MODE=IPV4, IP="192.168.0.50", USR="admin", PWD="*****",
SWT=SOFTWARE, DL=NO;
ACT SOFTWARE: OT=NE, SWT=SOFTWARE, SV="xxxx V100RxxxCxxSPCxxx";
//Activating the minimum configuration

ACT CFGFILE: MOD=LEAST, EFT=IMMEDIATELY, PRODUCTTYPE=DBS3900_LTE;
//Configuring cabinet, BBU, and board data

ADD CABINET: CN=0, TYPE=BTS3900;
ADD SUBRACK: CN=0, SRN=0, TYPE=BBU3910;
ADD BRD: SN=16, BT=FAN;
ADD BRD: SN=19, BT=UPEU;
ADD BRD: SN=6, BT=UMPT;
//When a UBBPem or UBBPf3 is used:
ADD BRD: SN=3, BT=UBBP, BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-1&NBIOT-0,
CPRIITFTYPE=CPRI_QSFP;
//Adding a UBBPf1
ADD BRD: SN=3, BT=UBBP, BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-1&NBIOT-0,
BRDSPEC="UBBPf1", CPRIITFTYPE=CPRI_QSFP;
//When a UBBPfw1 is used,
ADD BRD: SN=0, BT=UBBP-W, BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-1&NBIOT-0;
//Configuring the BBU-RU protocol type
SET EQUIPMENT: PROTOCOL=CPRI;
//Configuring operator information

ADD APP: AID=1, AT=eNodeB, AN="LTE",APPMNTMODE=NORMAL;
ADD ENODEBFUNCTION: eNodeBFunctionName="712451", ApplicationRef=1,
eNodeBId=712451;
ADD CNOPERATOR: CnOperatorId=0, CnOperatorName="huawei",
CnOperatorType=CNOPERATOR_PRIMARY, Mcc="460", Mnc="10";
ADD CNOPERATORTA: TrackingAreaId=0, CnOperatorId=0, Tac=10;

eRAN
//(Optional: single CPRI link configuration scenarios) Adding an AAU

ADD RRUCHAIN: RCN=0, TT=TRUNK_CHAIN, AT=LOCALPORT, CONNPORTNUM=1, CONNSN1=3,
CONNPN1=0, PROTOCOL=CPRI;
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=0, PS=0, RT=AIRU, RS=TDL, RXNUM=0,
TXNUM=0, MNTMODE=NORMAL, RFDCPWROFFALMDETECTSW=OFF;
//(Optional: eCPRI scenarios) Adding an AAU
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=0, HSN=2, HPN=0,
PROTOCOL=eCPRI, CR=AUTO, USERDEFRATENEGOSW=OFF;
//(Optional) Adding an AAU. Two optical fibers can be routed between the BBP and
AAU when two CPRI ports are configured. In this case, the two optical fibers must
have the same length.
ADD RRUCHAIN: RCN=0, TT=TRUNK_CHAIN, AT=LOCALPORT, CONNPORTNUM=2, CONNSN1=3,
CONNPN1=0, CONNSN2=3, CONNPN2=1, PROTOCOL=CPRI;
//Configuring clock information

SET CLKSYNCMODE: CLKSYNCMODE=TIME;
SET CLKMODE: MODE=MANUAL, CLKSRC=GPS, SRCNO=0;
ADD GPS: SRN=0, SN=6;
//Configuring the local time zone and DST information

SET TZ: ZONET=GMT+0800, DST=NO;
/*Configuring radio data*/

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

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

//Binding the massive MIMO cell to a BBP. Each massive MIMO cell can be bound
with only one BBP.
ADD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, SN1=3;
//Adding a cell (The following uses CPRI networking as an example. In eCPRI

networking, CPRICompression is set to NO_COMPRESSION.)
ADD CELL: LocalCellId=0, CellName="64TSite", NbCellFlag=FALSE, FreqBand=38,
UlEarfcnCfgInd=NOT_CFG, DlEarfcn=37900, UlBandWidth=CELL_BW_N100,
DlBandWidth=CELL_BW_N100, CellId=0, PhyCellId=0, FddTddInd=CELL_TDD,
SubframeAssignment=SA2, SpecialSubframePatterns=SSP7, EuCellStandbyMode=ACTIVE,
RootSequenceIdx=274, CustomizedBandWidthCfgInd=NOT_CFG,
EmergencyAreaIdCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG,
MultiRruCellFlag=BOOLEAN_FALSE, CrsPortNum=CRS_PORT_2,
CPRICompression=ENHANCED_COMPRESSION, TxRxMode=64T64R;
//Binding the cell to the sector equipment
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0, BASEBANDEQMID=0;
//Adding an operator for the cell

ADD CELLOP: LocalCellId=0, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
//Configuring the RS power

MOD PDSCHCFG: LocalCellId=0, ReferenceSignalPwr=1;
//Activating the beam weight file contained in the software package

ACT BFANTDB: OPMODE=SWFILE;
//Querying the beam weight file

DSP BFANTDB:;
//Configuring the beamforming antenna based on site conditions. The following

parameter settings are only for reference. Set the MODELNO parameter based on the
DSP BFANTDB command output
ADD BFANT: DEVICENO=0, CONNSRN=60, MODELNO="MassiveAntenna", TILT=6,
TiltFractionalPart=0, BFANTBEARING=0, Band=38, CoverageScenario=SCENARIO_2;

eRAN
//Configuring the WeightNO parameter to the same value as the DEVICENO parameter
MOD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0, WeightNO=0;
//Activating the cell

ACT CELL: LocalCellId=0;
//(Optional) Enabling service-based dynamic SRS allocation when there are 200 to
500 UEs in the cell
MOD SRSCFG: LocalCellId=0, SrsCfgPolicySwitch=SrvBasedSRSAdjAlgo-1;
MOD SERVICEIDENTIFYPARA: HeartbeatPacketLengthThld=180,
HeartbeatPacketNumberThld=4, MassFlowBigPacketRateThld=80, MassFlowDuration=2,
MassFlowPacketNumberThld=200;
Deactivation Command Examples

N/A
4.4.1.3 Using the CME

l Fast batch activation
This function can be batch activated using the Feature Operation and Maintenance
function of the CME. For detailed operations, see the following section in the CME
product documentation or online help: CME Management > CME Guidelines >
Enhanced Feature Management > Feature Operation and Maintenance.
l Single/batch configuration
This function can be activated for a single eNodeB or a batch of eNodeBs on the CME.
For detailed operations, see CME-based Feature Configuration.
NOTE
If a function requires the execution of the ACT BFANTDB command for activation after cells are
activated, this function can be activated by running this command, but not by using the CME.
4.4.2 Activation Verification

Step 1 Run the ACT CELL command to activate the massive MIMO cell, and run the DSP CELL
command to check the cell status.
If the value of Cell instance state is Normal, the cell has been activated.
Step 2 Run the DSP BFANT command to check whether the beam weights of the cell have taken
effect. If the amplitudes and phases of physical ports 1 through 64 are not empty in the
command output, the beam weights have taken effect.
Step 3 Run the DSP CELLCALIBRATION command to check the channel calibration results. If
the value of the Calibration Result parameter in the most recent calibration is Success,
channel calibration is successful.
NOTE
l The query results include historical calibration results. Identify the calibration record based on the
activation time of the corresponding cell and the calibration time to determine the calibration result.
l Beamforming and PDCCH SDMA can be activated only when channel calibration is successful.
----End
4.4.3 Network Monitoring

N/A

eRAN
4.4.4 Possible Issues

Channel Calibration Failures
A user-defined performance threshold alarm can be configured on the U2020. The alarm is
reported when the duration of the channel calibration failure exceeds the configured threshold.
The alarm helps O&M personnel more quickly identify channel calibration failures.
NOTE
The L.CellSectorEqpt.UNA.Dur.Cali counter measures the channel calibration failure duration.
To define a channel calibration failure alarm, perform the following operations on the U2020:
Step 1 Choose Performance > Threshold Management > Threshold Settings. The Threshold
Settings tab page is displayed.
Step 2 Choose eNodeB > Measurement of CellSectorEQUIP Performance from the navigation
tree, and then click Add at the bottom right part of the tab page. The Add Threshold dialog
box is displayed.

eRAN
Step 3 Select one or more NEs in the Object tab of the Add Threshold dialog box.
Step 4 On the Basic tab page, set Name, Period, and Activation time.

eRAN
Step 5 On the Advanced tab page, perform the following operations and then click OK.
An alarm is reported if the duration of the channel calibration failure is greater than or equal
to the threshold plus the offset. It is cleared if the duration falls below the threshold minus the
offset.
l Set Direction to Ascending.
l Set Function subset to Network/Measurements Related to Algorithm(LTE)/Cell
Sector Algorithm Measurement.
l Set Counter name to L.CellSectorEqpt.UNA.Dur.Cali.
l Set Threshold based on the calculation result of Period set on the Basic tab page
multiplied by 80% minus the offset. In the example, set Threshold to 9, namely 15 x
80% – 3.
l Set Offset based on the calculation result of Period set on the Basic tab page multiplied
by 20%. In the example, set Offset to 3, namely 15 x 20%.

eRAN
----End
Antenna Fault
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 identified based on the values of the
TX Channel Numbers In The Cell and RX Channel Numbers In The Cell parameters.
l The cell can still work properly as long as 32 or more antennas are operational. However,
faulty antennas may cause network performance, such as the cell throughput, to
deteriorate. The impact is directly proportionate to the number of faulty antennas.
l If fewer than 32 antennas remain operational, the massive MIMO cell is deactivated.
l If more than eight antennas are faulty, neither PDCCH SDMA in massive MIMO nor
multi-user split SDMA takes effect.

eRAN
Massive MIMO (TDD) Feature Parameter Description 5 Uplink Multiple-Antenna Reception
5 Uplink Multiple-Antenna Reception
Uplink multiple-antenna reception technologies are classified as either receive diversity or

MU-MIMO.
5.1 Receive Diversity
5.1.1 Principles
This section describes TDLEOFD-12160301 UL 64-Antenna Receive Diversity.
Receive diversity enables an eNodeB to receive signals through multiple antennas and then
combine the received signals using a specified signal combining algorithm. In this way, the
SINR is maximized and diversity and array gains are achieved. The gains are proportionate to
the number of receive antennas. For details about uplink receive diversity, see MIMO.
Figure 5-1 Receive diversity
Receive diversity is free from parameter control. It is deployed when a massive MIMO cell is
configured and the license has been purchased and activated.
Maximum ratio combining (MRC) and interference rejection combining (IRC) are typically
used for signal combining during receive diversity. For details, see MRC and IRC Receivers.
5.1.2 Network Analysis
5.1.2.1 Benefits
This feature increases array gains. Massive MIMO enables the eNodeB to adjust broadcast
beams and downlink traffic beams both horizontally and vertically. It achieves better uplink

eRAN
and downlink coverage performance than 8T8R multiple-antenna technologies. The gains are
more significant on the vertical plane.
NOTE
For details about diversity gains, see Beamforming (TDD).
5.1.2.2 Impacts
Network Impacts
l System capacity
This feature offers greater diversity gains and array gains than traditional uplink 2, 4, or
8-antenna receive diversity, improving uplink cell coverage, uplink average cell
throughput, and CEU throughput.
l Network performance
This feature provides a larger vertical coverage scope and stronger vertical coverage than
traditional 2, 4, or 8-antenna receive diversity. Accordingly, interference may increase in
contrast with that of a normal cell, leading to increasing measured interference counter
values.
Function Impacts
Name
Control channel PrachIrcSwitch and MRC and IRC Physical Random Access
receivers PucchIrcSwitch options Receivers CHannel (PRACH) IRC,
under the if being enabled, may
CellAlgoSwitch.IrcSwitc affect network access
h parameter performance in massive
MIMO scenarios. It is
recommended that the
PRACH IRC function be
disabled. You are advised
to enable the Physical
Uplink Control CHannel
(PUCCH) IRC function
in interference scenarios.
PRACH RB PrachRbReuseSwitch Scheduling The PRACH RB

occupation by option under the occupation by Physical
PUSCH CellAlgoSwitch.UlSchS Uplink Shared CHannel
witch parameter (PUSCH) function may
decrease the RRC
connection setup success
rate in massive MIMO
scenarios.
It is recommended that
PRACH RB occupation
by PUSCH be disabled.

eRAN
5.1.3 Requirements
5.1.3.1 Licenses
TDLEOFD-121 64T64R Massive MIMO LT1SUL64RD0 Per Cell

603 Basic Package 0
5.1.3.2 Software
Name
Massive MIMO N/A 4 Basic None

introduction Massive
MIMO
Functions

None
5.1.3.3 Hardware
See 4.3.3 Hardware.
5.1.3.4 Others
For details, see 4.3.4 Others.
5.1.4 Operation and Maintenance

For details, see 4.4 Operation and Maintenance.
5.2 MU-MIMO
The following table lists MU-MIMO features and the maximum number of pairing layers that
can be paired for each feature.

eRAN
Feature ID Feature Name Maximum Number of

Layers That Can Be
Paired
TDLEOFD-12160302 UL 2x64 MU-MIMO 2
TDLEOFD-121609 UL 4-Layer MU-MIMO 4
TDLEOFD-121610 UL 8-Layer MU-MIMO 8
NOTE
l MU-MIMO only applies to PUSCH data.

l For MU-MIMO, the number of layers refers to the maximum number of multiplexing layers. Only
rank 1 UEs can be paired in the uplink. Therefore, the maximum number of multiplexing layers for
the same RB equals the maximum number of paired UEs.
5.2.1 Principles
Overview
MU-MIMO is enabled in massive MIMO scenarios when the UlVmimoSwitch option is
selected under the CellAlgoSwitch.UlSchSwitch parameter. When this function is enabled,
the eNodeB attempts to pair UEs in each transmission time interval (TTI). Paired UEs use the
same time-frequency resource for uplink transmission. This technology improves the average
uplink cell throughput. If pairing fails for a given UE, the UE uses independent uplink time-
frequency resources for uplink transmission.
Figure 5-2 MU-MIMO

eRAN
UE Pairing
Figure 5-3 UE pairing procedure for MU-MIMO
The maximum number of MU-MIMO pairing layers in a massive MIMO cell is specified by
the CellUlschAlgo.MaxLayerMMVMIMO parameter.
The principles for selecting UEs to be paired are as follows:
l High-speed UEs are not selected for MU-MIMO pairing due to their constantly changing
channel environment and the poor stability of their radio quality. Pairing such UEs may
cause system performance to deteriorate.
l If the paired UEs have high SINRs and their channels are approximately orthogonal,
interference between the UEs can be effectively mitigated. Such UEs are suitable for
MU-MIMO. If UE channels are strongly correlated or the SINRs are low, interference
between the UEs cannot be effectively mitigated and MU-MIMO may decrease system
performance. Pairing of such UEs is not recommended.

eRAN
NOTE
The correlation between UE channels is calculated based on uplink feedback. This similarity
between uplink channels is highly correlated to the distance between UEs. The correlation is high
if two UEs are close to each other, and is low if they are not.
l The following parameters are used to control the types of UEs to be paired or UE pairing
policy:
Parameter ID Description
CellUlschAlgo.VmimoPairingStrategy Specifies the pairing policy.
HarqVmimoSwitch option under the Specifies whether UEs subjected to

CellUlschAlgo.VmimoOptAlgoSwitch uplink HARQ transmissions can be
parameter paired.
PreSchVmimoSwitch option under the Specifies whether UEs subjected to

CellUlschAlgo.VmimoOptAlgoSwitch uplink preallocation can be paired.
parameter
VoLTEUeVmimoSwitch option under Specifies whether voice over Long Term

the CellAlgoSwitch.UlSchSwitch Evolution (VoLTE) UEs can be paired.
parameter
SrPairingSwitch option under the Specifies whether a UE can be paired

CellAlgoSwitch.UlSchExtSwitch when sending an uplink scheduling
parameter request (SR).
MU-MIMO Enhancement
l Resource randomization
After MU-MIMO is enabled, interference on the PUSCH may increase. You are advised
to enable resource randomization to ensure that the UE-perceived data rate in
neighboring cells does not decrease after MU-MIMO takes effect. This function is
controlled by the VMIMOResRandomSwitch option under the
CellUlschAlgo.VmimoOptAlgoSwitch parameter.
l MCS index selection optimization
The uplink MU-MIMO pairing algorithm has been optimized so that optimal MCS
indexes are selected after pairing. This function is recommended in big-event heavy-load
massive MIMO scenarios. This function takes effect only for cells set up on the UBBPf1,
UBBPf3, or UBBPfw1. It can be used with uplink 2x64 MU-MIMO, uplink 4-layer MU-
MIMO, or uplink 8-layer MU-MIMO. This function is controlled by the
VmimoOptResSwitch option under the CellUlschAlgo.VmimoOptAlgoSwitch
parameter. Selecting this option reduces the initial block error rate (IBLER) after MU-
MIMO pairing, and in big-event heavy-load scenarios, improves the uplink spectral
efficiency.
l Pairing optimization
The mechanism for determining the number of uplink MU-MIMO pairing layers has
been optimized so that five to eight layers can be paired when the number of uplink RBs
is small. This function is recommended in massive MIMO scenarios. This function takes
effect only on cells set up on the UBBPf1 and requires uplink 8-layer MU-MIMO to be
enabled. This function is controlled by the CellUlschAlgo.EnhancedVmimoSwitch

eRAN
parameter. Setting this parameter to ON increases the average number of MU-MIMO

pairing layers and the average uplink cell throughput.
5.2.2.1 Benefits
This feature increases multiplexing gains. Massive MIMO supports up to eight layers for
uplink MU-MIMO, with theoretical uplink peak throughput approximately eight times that
provided by uplink receive diversity in 8T8R networking scenarios.
NOTE
For details about multiplexing gains, see Beamforming (TDD).
5.2.2.2 Impacts
Network Impacts
l A maximum of two, four, or eight UEs can use the same time and frequency resources to
increase the uplink spectral efficiency and uplink cell throughput. After this feature is
enabled, the probability of uplink control channel element (CCE) allocation failures may
increase because the number of uplink scheduled UEs increases.
l If uplink 4-layer MU-MIMO or uplink 8-layer MU-MIMO is enabled:
– The number of UEs paired within each TTI may change, leading to fluctuating
interference between paired UEs. As a result, the BLER of the uplink PUSCH may
increase.
– After a 4T/8T cell is reconstructed into a massive MIMO cell, the uplink and
downlink IBLERs may increase.
l If pairing optimization for uplink 8-layer MU-MIMO is enabled:
– If interference from neighboring cells changes significantly with time, this function
may decrease the average UE throughput, spectral efficiency, and average cell
throughput in the uplink.
– When the uplink physical resource block (PRB) load is not heavy, the single-UE-
perceived rate may decrease. When the uplink PRB load is heavy, the pairing
performance of uplink fifth to eighth layers improves significantly and the uplink
and downlink BLERs may increase.
Function Impacts
None
5.2.3 Requirements
5.2.3.1 Licenses
l The operator has purchased and activated the following license for TDLEOFD-12160302
UL 2x64 MU-MIMO. Only one unit of the license control item Massive MIMO UL 2-
Layers Extended Processing Unit License(TDD) is required.

eRAN
Feature ID Feature Model License Sales Unit

Name Control Item
TDLEOFD-12 64T64R LT1SUL64RD 64T64R Per Cell

1603 Massive 00 Massive
MIMO Basic MIMO Basic
Package Package(TDD)
N/A N/A LT4SMMUL Massive Per 2 Layer

ML01 MIMO UL 2-
Layers
Extended
Processing
Unit
License(TDD)
l The operator has purchased and activated the license for TDLEOFD-121609 UL 4-Layer
MU-MIMO. Two units of the license control item Massive MIMO UL 2-Layers
Extended Processing Unit License(TDD) are required.
Name Control Item

TDLEOFD-12 UL 4-Layer LT1SUL464M UL 4-Layer Per Cell

1609 MU-MIMO 00 MU-MIMO
(TDD)
N/A N/A LT4SMMUL Massive Per 2 Layers

ML01 MIMO UL 2-
Layers
Extended
Processing
Unit
License(TDD)
l The operator has purchased and activated the license for TDLEOFD-121610 UL 8-Layer
MU-MIMO. Four units of the license control item Massive MIMO UL 2-Layers
Name Control Item


eRAN

Name Control Item

(TDD)

(TDD)
N/A N/A LT4SMMUL Massive Per 2 Layers

ML01 MIMO UL 2-
Layers
Extended
Processing
Unit
License(TDD)
5.2.3.2 Software
l TDLEOFD-12160302 UL 2x64 MU-MIMO requires the following functions.
Name
Massive N/A 4 Basic None

MIMO Massive
introduction MIMO
Functions
Single- CellAlgoSwitch.BfAlg Beamforming The MU-MIMO pairing

streaming oSwitch (TDD) algorithm requires that
beamforming UEs in single-stream
beamforming report
measurement results.
Scheduler- SchedulerCtrlPowerS- Scheduling MCS index selection

controlled witch option of the optimization requires
power CellAlgoSwitch.UlSch scheduler-controlled
Switch parameter power to be enabled.
l TDLEOFD-121609 UL 4-Layer MU-MIMO requires the following functions.

eRAN

Name
UL 2x64 MU- UlVmimoSwitch 5.1 Receive None

MIMO option under the Diversity
CellAlgoSwitch.UlSch
Switch parameter

l TDLEOFD-121610 UL 8-Layer MU-MIMO requires the following functions.

Name
UL 2x64 MU- UlVmimoSwitch 5.1 Receive None

MIMO option under the Diversity
Switch parameter
Uplink 4-layer UlVmimoSwitch None None

MU-MIMO option under the
Switch parameter
IRC PUSCH_RECEIVE_E 5.2 MU- The pairing

NH_SWITCH option MIMO optimization function
under the depends on IRC.
CellMMAlgo.MMAlgo
OptSwitch parameter


None
5.2.3.3 Hardware
See 4.3.3 Hardware. The UBBPf1 must be deployed for pairing optimization, and the
UBBPf1, UBBPf3, or UBBPfw1 must be deployed for MCS index selection optimization.

eRAN
5.2.4.1 Data Configuration

If MU-MIMO is to be enabled in massive MIMO cells, the following parameters need to be
set.
Table 5-1 Parameters used for activation

Parameter Parameter ID Setting Notes
Name
Vmimo CellUlschAlgo.VmimoOpt Select the HarqVmimoSwitch,

Optimization AlgoSwitch PreSchVmimoSwitch, and
Algorithm VmimoResRandomSwitch options
Switch under this parameter.
VMIMO Pairing CellUlschAlgo.VmimoPai Set this parameter to ADAPTIVE.

Strategy ringStrategy
Max Number of CellUlschAlgo.MaxLayer l Set this parameter to 2LAYER for

Layers for MMVmimo TDLEOFD-12160302 UL 2x64 MU-
Massive MIMO MIMO.
VMIMO l Set this parameter to 4LAYER for
TDLEOFD-121609 UL 4-Layer MU-
MIMO.
l Set this parameter to 8LAYER for
TDLEOFD-121610 UL 8-Layer MU-
MIMO.
Enhanced CellUlschAlgo.Enhanced Set this parameter to ON when pairing

VMIMO Switch VmimoSwitch optimization is enabled.
Massive MIMO CellMMAlgo.MMAlgoOp Select the

Algorithm tSwitch PUSCH_RECEIVE_ENH_SWITCH
Optimization option when pairing optimization is
Switch enabled.
Vmimo CellUlschAlgo.VmimoOpt Select the VmimoOptResSwitch option

Optimization AlgoSwitch when MCS index selection optimization
Algorithm is enabled.
Switch

eRAN

Name
Uplink schedule CellAlgoSwitch.UlSchSwi l If there are many VoLTE UEs, it is

switch tch recommended that the
UlVmimoSwitch and
VoLTEUeVmimoSwitch options be
selected. The
VoLTEUeVmimoSwitch option takes
effect only when the
UlVmimoSwitch option is selected
under the same parameter.
l If there are a small number of VoLTE
UEs, it is recommended that the
VoLTEUeVmimoSwitch option be
deselected.a
l Select the SchedulerCtrlPowerS-
witch option when MCS index
selection optimization is enabled.
Uplink Schedule CellAlgoSwitch.UlSchExt l UE pairing for SR transmission may

Extended Switch Switch increase the BLER when the network
load is light or there are almost no
uplink services. In such scenarios, it
is not recommended that the
SrPairingSwitch option be selected.b
l UE pairing increases the uplink
system capacity and SR scheduling
success rate when the network load is
heavy or the uplink service load is
heavy, though the BLER also
increases. It is recommended that the
SrPairingSwitch option be selected.
The SrPairingSwitch option takes
effect only when the
UlVmimoSwitch option is selected
under the
CellAlgoSwitch.UlSchSwitch
parameter.
a: After the VoLTEUeVmimoSwitch option is deselected, the impact of interference

between paired UEs on the PUSCH BLER decreases. In massive MIMO cells, the uplink
voice packet loss rate decreases. In heavy load scenarios, the uplink traffic volume
(measured by the L.Thrp.bits.UL counter) decreases.
b: After the SrPairingSwitch option is deselected, the impact of interference between
paired UEs on the PUSCH BLER decreases and the uplink traffic volume (measured by the
L.Thrp.bits.UL counter) decreases in heavy-load scenarios.

eRAN
5.2.4.1.2 Using MML Commands

//Configuring the SRS configuration mode
MOD SRSCFG: LocalCellId=0, SrsCfgInd=BOOLEAN_TRUE, TddSrsCfgMode=ACCESS_ENHANCED;
//Turning on the MU-MIMO switch and the VoLTE-specific MU-MIMO switch
MOD CELLALGOSWITCH: LocalCellId=0,
ULSchSwitch=UlVmimoSwitch-1&VoLTEUeVmimoSwitch-1;
//Enabling SR pairing
MOD CELLALGOSWITCH: LocalCellId=0, ULSchExtSwitch=SrPairingSwitch-1;
//Configuring the maximum number of layers that can be paired for MU-MIMO in
massive MIMO scenarios, enabling pairing for UEs subjected to retransmission and
preallocation, and MU-MIMO resource randomization, and specifying the MU-MIMO
pairing policy
MOD CELLULSCHALGO: LocalCellId=0, MaxLayerMMVmimo =8LAYER,
VmimoOptAlgoSwitch=HarqVmimoSwitch-1&PreSchVmimoSwitch-1&VmimoResRandomSwitch-1,
VmimoPairingStrategy=ADAPTIVE;
//Enable pairing optimization and MCS index selection optimization
MOD CELLMMALGO: LocalCellId=0, MMAlgoOptSwitch=PUSCH_RECEIVE_ENH_SWITCH-1;
MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=SchedulerCtrlPowerSwitch-1;
MOD CELLULSCHALGO: LocalCellId=0, EnhancedVmimoSwitch=ON,
VmimoOptAlgoSwitch=VmimoOptResSwitch-1;

l Deactivating some MU-MIMO functions
//(Optional) Deactivating MU-MIMO pairing for VoLTE UEs
MOD CELLALGOSWITCH: LocalCellId=0, ULSchSwitch=VoLTEUeVmimoSwitch-0;
//(Optional) Deactivating MU-MIMO optimization functions by selecting the
HarqVmimoSwitch, PreSchVmimoSwitch, and VmimoResRandomSwitch options
MOD CellUlschAlgo: LocalCellId=0, VmimoOptAlgoSwitch=HarqVmimoSwitch-0;
//(Optional) Deactivating pairing optimization and MCS index selection
optimization
MOD CELLULSCHALGO: LocalCellId=0, EnhancedVmimoSwitch=OFF,
VmimoOptAlgoSwitch=VmimoOptResSwitch-0;
l Deactivating all MU-MIMO functions

//Disabling uplink MU-MIMO
MOD CELLALGOSWITCH: LocalCellId=0, ULSchSwitch=UlVmimoSwitch-0;
//Disabling MU-MIMO resource randomization
MOD CellUlschAlgo: LocalCellId=0, VmimoOptAlgoSwitch=VmimoResRandomSwitch-0;
5.2.4.1.3 Using the CME

For details, see 4.4.1.3 Using the CME.
5.2.4.2 Activation Verification
MU-MIMO Pairing
Step 1 On the U2020 client, choose Monitor > Signaling Trace > Signaling Trace Management.
Step 2 From the navigation tree of the Signaling Trace Management tab page, choose LTE > Cell
Performance Monitoring, and then double-click Multi User-MIMO Monitoring.
Step 3 In the displayed dialog box, select an eNodeB and set Local Cell ID for the cell to be traced.
Then, click Finish to start a trace task.
Step 4 Use multiple UEs to access the network, adjust the RSRP of the UEs to be greater than –75
dBm, and then perform uplink FTP services on the UEs.
Step 5 Double-click the trace task to verify the value of UL MIMO UE Pair Num.

eRAN
l If the value of UL MIMO UE Pair Num is not N/A, uplink MU-MIMO has taken
effect. UL MIMO UE Pair Num indicates the total number of UEs paired for uplink
MIMO.
l If the value of UL MIMO UE Pair Num 2 Layers is not N/A, uplink 2x64 MU-MIMO
has taken effect.
l If the value of UL MIMO UE Pair Num 3 Layers or UL MIMO UE Pair Num 4
Layers is not N/A, uplink 4-layer MU-MIMO has taken effect.
l If any of the values of UL MIMO UE Pair Num 5 Layers, UL MIMO UE Pair Num
6 Layers, UL MIMO UE Pair Num 7 Layers, or UL MIMO UE Pair Num 8 Layers
is not N/A, uplink 8-layer MU-MIMO has taken effect.
Step 6 Use multiple UEs to access the network, adjust the RSRP of the UEs to be greater than –75
dBm, and then perform uplink VoLTE services on the UEs.
Step 7 Double-click the trace task to verify the value of VoLTE UE VMIMO Pair Num.
If the value of VoLTE UE Mimo Pair Num is not N/A, VoLTE UEs have been paired for
MU-MIMO.
----End
MU-MIMO Enhancement
Step 1 Run the LST CELLULSCHALGO command. If VMIMOResRandomSwitch:On is
displayed under the Vmimo Optimization Algorithm Switch parameter, resource
randomization has been enabled.
Step 2 Run the LST CELLULSCHALGO command. If VmimoOptResSwitch:On is displayed
under the Vmimo Optimization Algorithm Switch parameter, MCS index selection
optimization has been enabled.
Step 3 Run the LST CELLULSCHALGO command to query the value of the Enhanced VMIMO
Switch parameter. If the value is ON, pairing optimization has been enabled.
----End
5.2.4.3 Network Monitoring
Signaling Tracing
Step 2 In the navigation tree of the Signaling Trace Management tab page, choose LTE > Cell
Performance Monitoring > Throughput Monitoring. Check the throughput of the eNodeB
and the cells under it.
Step 3 In the navigation tree of the Signaling Trace Management tab page, choose Trace Type >
LTE > Cell Performance Monitoring > Multi User-MIMO Monitoring. Check the values
of the following monitoring items.
l UL MIMO UE Pair Num
l UL MIMO UE Pair Num 2 Layers through UL MIMO UE Pair Num 8 Layers
l UL MIMO 2Layers PairRB through UL MIMO 8Layers PairRB
UL MIMO UE Pair Num 3 Layers through UL MIMO UE Pair Num 8 Layers and UL MIMO
3Layers PairRB through UL MIMO 8Layers PairRB are not suitable for uplink 2x64 MU-

eRAN
MIMO. UL MIMO UE Pair Num 5 Layers through UL MIMO UE Pair Num 8 Layers and
UL MIMO 5Layers PairRB through UL MIMO 8Layers PairRB are not suitable for uplink
4x64 MU-MIMO.
If the monitoring item corresponding to an MU-MIMO feature has a non-zero value, the
feature has been activated. If the value of Mimo UE Pair Num or the number of paired RBs
is always 0, see 5.2.4.4 Possible Issues.
NOTE
MU-MIMO pairing performance is subjected to channel quality, user distributions, service status, and
other factors. Therefore, it is acceptable if the number of paired layers does not reach the maximum
within a given measurement period.
Step 4 In the navigation tree of the Signaling Trace Management tab page, choose LTE > Cell
Performance Monitoring > Multi User-MIMO Monitoring. Check the value of VoLTE
UE Mimo Pair Num.
l If the value of VoLTE UE Mimo Pair Num is not 0, VoLTE UEs have been paired for
MU-MIMO.
l If the value of VoLTE UE Mimo Pair Num is always 0, see 5.2.4.4 Possible Issues.
----End
Counter-based Monitoring
Step 1 Monitor counters in the following function subsets:
l Total Number of TBs Transmitted in the Uplink in Massive MIMO
l Total Number of TBs That Fail to Be Transmitted in the Uplink in Massive MIMO
l Number of Bits Successfully Transmitted in the Uplink in Massive MIMO
l Total Number of RBs Transmitted in the Uplink in Massive MIMO Scenarios
l Number of RBs That Are Successfully Paired for VMIMO UEs in a Cell
l Number of RBs That Can Be Paired for VMIMO UEs in a Cell
l Number of RBs That Are Successfully Paired for VMIMO layer2 UEs in a Cell
Step 2 Monitor the counters related to the number of PRBs actually scheduled for UEs in a cell. The
number of PRBs is measured by UE, and therefore the total number of PRBs scheduled in a
20 MHz cell may exceed 100, except for the counters L.ChMeas.PRB.UL.Used.Avg and
L.ChMeas.PRB.UL.PUSCH.Avail.
Counter ID Counter Name Description
1526726737 L.ChMeas.PRB.UL.Used.Avg Average number of used uplink

PRBs
1526728545 L.ChMeas.PRB.UL.PreSch.Used Average number of PRBs allocated

.Avg for uplink preallocation
1526730557 L.ChMeas.PRB.UL.PUSCH.Ava Number of available PUSCH

il PRBs
1526746010 L.ChMeas.PRB.UL.DrbUsed.Av Average number of uplink PUSCH

g.ExtQci.Index0 PRBs used by DRBs for services
with an extended QCI of counter
index 0

eRAN
1526741727 L.ChMeas.PRB.UL.Avg.EdgeAc Average number of uplink PRBs

tiveSchVoIPUser used by edge-active-scheduling
UEs performing VoLTE services
1526733015 L.ChMeas.PRB.UL.PCell.Used. Average number of uplink PRBs

Avg occupied by CA UEs that treat the
local cell as their PCell
1526739681 L.ChMeas.PRB.UL.PttUsed.Avg Average number of uplink PRBs

.PLMN used by PTT services for a specific
operator
1526728294 L.RBUsedOwn.UL.PLMN Average number of own PUSCH

PRBs used by a specific operator
1526741667 L.RBUsedOtherGroup.UL.PLM Average number of other operator

N resource group uplink PRBs used
by a specific operator in an
operator resource group in a cell
----End
5.2.4.4 Possible Issues

Fault description: MU-MIMO fails to be activated.
Fault handling:
Step 1 Run the DSP LICINFO command to check whether the feature license is available in the
command output.
l If no, apply for and load a new license.
l If yes, go to the next step.
LTE > Cell Performance Monitoring > Users Statistic Monitoring. Create and start a
tracing task, and check the value of General Users Number.
l If there are five or fewer UEs, the possibility of UE pairing is low and the MU-MIMO
feature does not take effect. It is recommended that there be more than five UEs.
l If there are enough UEs, go to the next step.
LTE > User Performance Monitoring > Quality of Channel Monitoring. Create and start a
tracing task, and check SINRs.
l If the SINRs of the monitored UEs are less than 1 dB, there is a high probability that the
UEs cannot be paired and MU-MIMO does not take effect.
l If the SINRs of the monitored UEs are greater than or equal to 1 dB but MU-MIMO does
not take effect, contact Huawei technical support.
----End

eRAN
Massive MIMO (TDD) Feature Parameter Description 6 Downlink Multiple-Antenna Transmission
6 Downlink Multiple-Antenna Transmission
Category Applicable Channel Recommended

Transmission Mode
3D beamforming PDSCH l UEs incapable of

transmit antenna
selection: TM7
l UEs capable of transmit
antenna selection: TM8
MU beamforming PDSCH l UEs incapable of

transmit antenna
selection: TM7
antenna selection: TM8
Multi-user split SDMA PDSCH TM7, TM8, or PMI

feedback-independent or -
dependent TM9
TM9 PDSCH N/A
TM9 hybrid precoding PDSCH PMI feedback-independent

TM9 or PMI feedback-
dependent TM9
PDCCH SDMA PDCCH N/A
Enhanced coordinated PDSCH N/A

scheduling based power
control
NOTE
Unless otherwise specified, UEs incapable of transmit antenna selection include fake antenna selection
UEs. For details about fake antenna selection UEs, see 7.9.1 Principles.

eRAN
6.1 3D Beamforming
6.1.1 Principles
The overall procedure of beamforming in massive MIMO scenarios is the same as that of
traditional beamforming. For details, see Beamforming (TDD). Figure 6-1 shows the overall
beamforming process.
Figure 6-1 Overall beamforming process
NOTE
l In massive MIMO scenarios, the eNodeB automatically starts the initial channel calibration 2
minutes after a cell is set up. The subsequent channel calibrations are performed on each carrier at a
fixed period of 10 seconds.
l The channel calibration result can be queried by running the DSP CELLCALIBRATION
command. Beamforming and PDCCH SDMA can be activated only when channel calibration is
successful.
TDLEOFD-121615 DL Flexible 3D-Beamforming is also referred to as 3D beamforming. Its

adoption of array antennas increases the number of logical antennas on the vertical plane,
which makes it possible to implement vertical-plane beamforming.
Figure 6-2 Vertical-plane beamforming

eRAN
3D beamforming enables an eNodeB to impose UE-level beam weighting on PDSCH data

both horizontally and vertically. This technique increases the receive SINR of UEs at different
locations.
1. Channel calibration: The eNodeB adjusts the changes in phase, amplitude, and delay
(Delta 1 through Delta 64) of calibration signals to be consistent with each other after
they pass through different AAU channels. This ensures the reciprocity between uplink
and downlink channels.
Figure 6-3 Channel calibration
2. Weight calculation: The eNodeB estimates the PDSCH characteristics based on UE-
reported SRSs and calculates the beamforming weight.
3. Weighting and beamforming: The eNodeB weights the transmitted signals to form a
narrow beam targeted towards the UE. In this way, the eNodeB differentiates UEs
horizontally and vertically.
Figure 6-4 Beamforming
4. Demodulation: The UE demodulates PDSCH data based on demodulation reference

signals (DMRSs).
3D beamforming is controlled by the BfSwitch option under the

CellAlgoSwitch.BfAlgoSwitch parameter. If the BfSwitch option is selected, single-stream
beamforming is supported by default.
6.1.2.1 Benefits
This feature increases beamforming gains. Massive MIMO enables the eNodeB to adjust
broadcast beams and downlink traffic beams both horizontally and vertically. It achieves
better uplink and downlink coverage performance than 8T8R multiple-antenna technologies.
The gains are more significant on the vertical plane.
NOTE
For details about beamforming gains, see Beamforming (TDD).

eRAN
6.1.2.2 Impacts
Network Impacts
l Impact on system capacity: This feature improves the downlink cell throughput and
spectral efficiency.
l Impact on network performance: This feature improves the downlink coverage
capability.
Function Impacts
Name
Coverage-based IntraFreqCoverHoS- Mobility When certain UEs work

intra-frequency witch option under the Management in in beamforming mode in
handover ENodeBAlgoSwitch.Ho Connected massive MIMO cells, the
AlgoSwitch parameter Mode reference signal received
power (RSRP) of intra-
frequency neighboring
cells measured by the
UEs may be greater than
the actual value. In this
case, premature
handovers possibly
occur, increasing the
number of intra-
frequency handovers. In
addition, handovers to
the neighboring cells will
decrease the intra-
frequency handover
success rate due to actual
low RSRP values.

eRAN

Name
Beamforming NoSrsSccBfSwitch Carrier l Beamforming is

in SCell option under the Aggregation available on the
CellAlgoSwitch.NoSrsS primary component
ccBfAlgoSwitch carrier (PCC) but not
parameter on secondary
component carriers
(SCCs) of each CA
UE when uplink
carrier aggregation
(CA) is not supported
and beamforming in
SCells is disabled.
l Beamforming is
available on both the
PCC and SCCs when
either of the
following conditions
is met:
– Uplink CA is not
supported and
beamforming in
SCells is enabled.
– Uplink CA is
supported.
6.1.3 Requirements
6.1.3.1 Licenses
TDLEOFD-121 DL Flexible 3D- LT1SDL643D0 Per Cell

615 Beamforming 0

eRAN
6.1.3.2 Software
Name

MIMO
Functions

None
6.1.3.3 Hardware
See 4.3.3 Hardware.

If 3D beamforming and adaptive switching between beamforming and MIMO are required in
massive MIMO cells, the following parameters need to be configured.
NOTE
The cell will reset after SRS configurations are modified by running the MOD SRSCFG command.

Name
CRS Port Cell.CrsPortNum Set this parameter to CRS_PORT_2.

Number
SRS SRSCfg.SrsCfgInd To improve beamforming performance,

Configuration set this parameter to
Indicator BOOLEAN_TRUE. In this situation,
however, the uplink peak throughput may
decrease.
TDD SRS SRSCfg.TddSrsCfgMode Set this parameter to

Configuration ACCESS_ENHANCED for massive
Mode MIMO cells.

eRAN

Name
BF algorithm CellAlgoSwitch.BfAlgoS Select the BfSwitch option.

switch witch
Beamforming CellBf.MaxBfRankPara Set this parameter to

maximum SINGLE_LAYER_BF.
number of layers
BfMIMO CellBfMimoParaCfg.Bf Set this parameter to

adaptive switch MimoAdaptiveSwitch MIMO_BF_ADAPTIVE.
Fixed BfMIMO CellBfMimoParaCfg.Fix This parameter applies only when a

mode edBfMimoMode transmission mode is tested and the
CellBfMimoParaCfg.BfMimoAdaptive
Switch parameter is set to
NO_ADAPTIVE.
Bf Mimo CellBfMimoParaCfg.Bf Set this parameter to ON.

Adaptive MimoAdapWithoutTm2 When this parameter is set to ON, TM2
Without Tm2 is no longer used after the UE switches
from TM2 to other transmission modes.
BfMIMO CellBfMimoParaCfg.Bf Set this parameter to OFF in massive

Adaptive with MimoAdapWithTm4Switc MIMO scenarios, since massive MIMO
TM4 h is not compatible with downlink 4x4
MIMO.
BfMimo CellBfMimoParaCfg.Bf l Select the

Algorithm MimoAlgoOptSwitch BFTOMIMOALGOOPTSWITCH
Optimization option under this parameter when
Switch adaptive switching between
beamforming and MIMO is enabled.
l Select the
BFMIMOADAPWITHOUTTM8
option under this parameter when
adaptive switching between
beamforming and MIMO or adaptive
switching between open-loop
beamforming modes is enabled.
l It is recommended that the
BF_WEIGHT_GRAN_OPT_SWIT
CH option be selected to enable
beamforming weight granularity
optimization so that the eNodeB
selects the weight granularity based
on the SRS SINR.
UE Access CellBfMimoParaCfg.Ue Set this parameter to TM7 when TMA is

Transmission AccessTMMode enabled in massive MIMO scenarios. For
Mode details about the reasons, see 6.7.1.3
Optimized TMA.

eRAN

Name
PHICH duration PHICHCfg.PhichDuratio Set this parameter to NORMAL.

n
Uplink and CellPdcchAlgo.ULDLPdc Set this parameter to 1.

Downlink chSymNum
PDCCH
Symbols
Configuration
PDCCH Initial CellPdcchAlgo.InitPdcch Set this parameter to 1.

Symbol Number SymNum

//Configuring sounding reference signal (SRS) resources
MOD SRSCFG: LocalCellId=0, SrsCfgInd=BOOLEAN_TRUE, TddSrsCfgMode=ACCESS_ENHANCED;
//Enabling beamforming
MOD CELLALGOSWITCH: LocalCellId=0, BfAlgoSwitch=BfSwitch-1;
//Configuring the maximum number of beamforming layers
MOD CELLBF: LocalCellId=0, MaxBfRankPara=SINGLE_LAYER_BF;
//Configuring TMA and enabling beamforming weight granularity optimization
MOD CELLBFMIMOPARACFG: LocalCellId=0,BfMimoAdaptiveSwitch=MIMO_BF_ADAPTIVE,
BfMimoAdapWithoutTm2=ON, BfMimoAlgoOptSwitch=BFTOMIMOALGOOPTSWITCH-1,
UeAccessTMMode=TM7;
MOD CELLBFMIMOPARACFG:
LocalCellId=0,BfMimoAlgoOptSwitch=BFMIMOADAPWITHOUTTM8-1&BF_WEIGHT_GRAN_OPT_SWITCH
-1;
//Configuring one initial PDCCH OFDM symbol and one uplink/downlink PDCCH symbol
MOD CELLPDCCHALGO: LocalCellId=0, InitPdcchSymNum=1, ULDLPdcchSymNum=1;
//Configuring the PHICH duration mode to normal
MOD PHICHCFG: LocalCellId=0, PhichDuration=NORMAL;

//Disabling beamforming
MOD CELLALGOSWITCH: LocalCellId=0, BfAlgoSwitch=BfSwitch-0;


Run the LST CELLALGOSWITCH command to check whether BfSwitch:On is displayed
under the BF algorithm switch parameter. If yes, 3D beamforming has been enabled.

Step 1 Start downlink services on a UE compliant with 3GPP Release 8 or later, and move the UE
away from the cell center.

eRAN
NOTE
The 3GPP release version of the UE can be queried in the RRC_UE_CAP_INFO message.
Step 2 On the U2020, perform a Uu interface trace task and check the UE transmission mode based
on the value of the transmissionMode field in the explicitValue IE.
Figure 6-5 Signaling tracing result
Step 3 Check whether the changes of transmission modes during the UE movement match what is
listed in 6.7.1.2 TMA Principles. If yes, beamforming and the related TMA have taken
effect.
----End

Fault description: The transmission mode cannot be switched to 3D beamforming.
Fault handling:
Step 1 Verify that the feature, hardware, and license meet the deployment requirements.
Step 2 Verify that switches are configured as required.
Step 3 Run the DSP CELLCALIBRATION command to check the channel calibration results. If
channel calibration has failed, check for uplink interference.
Step 4 If a UE cannot switch to TM7, check the RSRP of the UE. If the RSRP is low, move the UE
to another location and then retry the network access. If the UE cannot switch to TM9, run the
DSP CELLCSIRSPARACFG command to check the value of the CsiRs State parameter. If
the value is not Normal, rectify the fault based on the cause value.
----End
6.2 MU Beamforming
The following table lists 64-antenna MU beamforming features and the maximum number of
layers that can be paired.
Feature ID Feature Name Maximum Number of Layers

That Can Be Paired
TDLEOFD-121604 DL 8-Layer MU- 8

Beamforming

eRAN
Feature ID Feature Name Maximum Number of Layers

That Can Be Paired

Beamforming

Beamforming (Trial)
NOTE
"Layer" in the feature names refers to the maximum number of multiplexing layers.
6.2.1 Principles
Overview
MU beamforming is enabled in massive MIMO scenarios when the MuBfSwitch option is
selected under the CellAlgoSwitch.MuBfAlgoSwitch parameter. When this function is
enabled, the eNodeB attempts to pair UEs in each TTI.
The eNodeB performs MU beamforming as follows:
l Determines the UEs to be paired and the number of downlink data streams to be
transmitted to each UE based on UE pairing conditions.
l Generates orthogonal weight values for downlink data streams based on the zero forcing
principle.
l Imposes weight on data symbols and DMRS symbols for each data stream using the
generated weight values.
l Combines the weighted symbols and transmits them over the antenna ports.
In this way, multiple data streams are transmitted in the downlink using the same time-
frequency resource, enhancing the downlink spectral efficiency.
Figure 6-6 MU beamforming

eRAN
UE Pairing
Figure 6-7 UE pairing
1. The eNodeB selects candidate UEs for MU beamforming pairing.

A UE can be selected as a candidate for MU beamforming pairing when both of the
following conditions are met:
– The UE is working in TM7, and the channel quality indicator (CQI) value is greater
than a given threshold.
– For HARQ retransmission UEs, the HarqRetranPairSwitch option is selected
under the CellAlgoSwitch.MuBfAlgoSwitch parameter.
– VoLTE UEs can be paired only when the MU_PAIRING_VOLTE_SWITCH
option is selected under the CellMMAlgo.MMAlgoOptSwitch parameter.
2. The eNodeB selects for pairing the candidate UEs that meet the following requirements:
– The number of layers is not greater than the value of the
CellBf.HighOrderMubfMaxLayer parameter.
– In massive MIMO scenarios, the UE pairing rule for MU beamforming is specified
by the CELLBF.MassiveMIMOMubfPairRule parameter.
n When this parameter is set to MU_CORR_PAIR_RULE, the eNodeB selects
only the UEs with low channel correlations for MU beamforming pairing. The
pairing increases the system capacity.
n When this parameter is set to
MU_WITHOUT_CORR_PAIR_RULE(MU_WITHOUT_CORR_PAIR_
RULE), the eNodeB selects UEs for pairing without considering UE channel

eRAN
correlations. The pairing rule increases the number of paired layers, but may
reduce the system capacity.
3. The eNodeB uses the same time-frequency resources to transmit data to both of the
paired UEs.
Figure 6-8 uses 4-layer MU beamforming pairing as an example to illustrate the RBG
allocation for paired UEs. UEs with low spatial channel correlations, such as UEs 1, 2, 3,
and 4, can be paired for MU beamforming and are scheduled at different layers. MU
beamforming allows UEs to be paired to occupy different amounts of RB resources.
Therefore, unused layer 3 resources can be allocated to UEs 5 and 6 that are highly
correlated with UE 3 if UEs 5 and 6 are low correlated with other UEs that use the same
resource for data transmission.
Figure 6-8 4-layer pairing for MU beamforming
NOTE
UE pairing uses spatial resources and the scheduling priority of UEs changes after MU
beamforming is enabled. Therefore, MU beamforming has an impact on the features or functions
related to scheduling priorities, such as QoS management.
Scheduling Optimizations for MU Beamforming

l Downlink time-domain extended scheduling
Light-traffic services (such as instant messaging and heartbeat services) may preempt
resources of heavy-traffic services (such as video or web browsing services) when such
services are both running simultaneously. If this occurs, the user perceived rate of heavy-
traffic services decreases.
With the downlink time-domain extended scheduling function, the massive MIMO cell
differentiates light-traffic services from heavy-traffic services and staggers pairing and
scheduling for light- and heavy-traffic services. In this way, light-traffic services are
prevented from preempting resources of heavy-traffic services, improving the UE
perceived rate of heavy-traffic services.
This function is controlled by the DL_TIME_DIM_EXT_SCH_SWITCH option under
the CellAlgoSwitch.DlSchExtSwitch parameter.
The downlink time-domain adaptive extended scheduling function requires the service
identification mechanism. When this function is enabled, set the
ServiceIdentifyPara.MassFlowBigPacketRateThld and
ServiceIdentifyPara.MassFlowPacketNumberThld parameters based on traffic and
service distributions for maximal network optimization.
l MU beamforming-specific MCS index selection optimization

eRAN
MCS index selection is subject to CQIs and the CQI adjustment reliability depends on
the number of downlink data packets. If there are a small number of downlink data
packets, the CQI adjustment reliability is poor. When there are many downlink data
packets, the CQI adjustment reliability is high.
In massive MIMO scenarios, the eNodeB selects MCS indexes for dual-stream
beamforming based on the MCS indexes of single-stream beamforming. When there are
a small number of downlink packets in single-stream beamforming, the MCS indexes of
single-stream beamforming are unreliable, which makes it impossible for the eNodeB to
select optimal MCS indexes for MU beamforming.
MU beamforming-specific MCS index selection optimization is introduced to resolve
this issue. With this function, if the number of MU beamforming data packets is greater
than the threshold specified by the CellCqiAdjAlgo.MuBfPacketThld parameter, the
eNodeB determines MCS indexes for MU beamforming based on 4-bit CQI information
reported by UEs, measured BFGain value of the eNodeB, and HARQ feedback on MU
beamforming data packets. This function enhances the accuracy of MCS index selection
in MU beamforming scenarios.
Beamforming weights calculated based on SRS measurements may not match ever-
changing UE channel conditions, affecting the MCS index selection accuracy for pairing.
If many UEs move at a speed of 5 km/h or less, selecting the
MU_PAIRING_MCS_EXACT_SWITCH option under the
CellMMAlgo.MMAlgoOptSwitch parameter improves the MCS index selection
accuracy for pairing. This optimization has no gain in scenarios where UEs are
stationary. If many UEs move at a speed of greater than 5 km/h, this optimization has
limited gains or even no gains due to exceedingly violent channel condition changes. The
MCS index fluctuates with signal quality when there are many low-speed UEs,
improving the MCS index selection accuracy and the downlink spectral efficiency. The
UEs that are not suitable for pairing are not paired, which may reduce the number of
paired layers.
l Moving UE optimization
This function is controlled by the HIGH_SPEED_OPTI_SCHEME option under the
CellBf.MovingUeMuBfScheme parameter. When this option is selected, the eNodeB
adjusts the MU beamforming grouping mechanism for moving UEs. The adjustment
ensures that the MU beamforming weights of moving UEs are orthogonal. This function
is suitable when downlink 8- or 16-layer MU beamforming is enabled.
This function increases the downlink cell throughput and spectral efficiency in mobility
scenarios, but the average number of pairing layers may decrease.
l Big-event moving UE protection
This function is controlled by the BIG_EVENT_PROTECT_SCHEME option under
the CellBf.MovingUeMuBfScheme parameter. When this option is selected, the eNodeB
adjusts the UE grouping mechanism for MU beamforming pairing of moving UEs. The
adjustment ensures that the MU beamforming weights of moving UEs are orthogonal.
This function is suitable when downlink 8- or 16-layer MU beamforming is enabled.
This function improves MU beamforming pairing performance of moving UEs in big-
event scenarios. In heavy-load scenarios, however, this function may increase the
average PDCP service data unit (SDU) transmission delay.
NOTE
Average PDCP SDU transmission delay = (L.Traffic.DL.PktDelay.Time.QCI.1 +

L.Traffic.DL.PktDelay.Time.QCI.2 + ... + L.Traffic.DL.PktDelay.Time.QCI.8 +
L.Traffic.DL.PktDelay.Time.QCI.9)/(L.Traffic.DL.PktDelay.Num.QCI.1 +
L.Traffic.DL.PktDelay.Num.QCI.2 + ... + L.Traffic.DL.PktDelay.Num.QCI.8 +
L.Traffic.DL.PktDelay.Num.QCI.9)

eRAN
MU Beamforming Outer-Loop Initial Value Control

This function enables users to flexibly configure the initial CQI outer-loop adjustment value
in MU beamforming scenarios by setting the CellMMAlgo.MassiveMimoInitDeltaCqi
parameter. The value of this parameter has the following impacts:
l When the outer-loop CQI adjustment value for UEs paired for massive MIMO is small, a
smaller value of this parameter improves downlink spectral efficiency, and a larger value
of this parameter lowers downlink spectral efficiency.
l When the outer-loop CQI adjustment value for UEs paired for massive MIMO is large, a
larger value of this parameter improves downlink spectral efficiency, and a smaller value
of this parameter lowers downlink spectral efficiency.
NOTE
l Before this function was introduced, the initial CQI outer-loop adjustment value is 0 dB and cannot
be changed in MU beamforming scenarios.
l It is recommended that the CellMMAlgo.MassiveMimoInitDeltaCqi parameter be set to 0. Confirm
the value of the parameter with Huawei engineers during network optimization.
6.2.2.1 Benefits
This feature increases multiplexing gains. Massive MIMO supports up to 16 layers (or 24
layers as a trial version only) for downlink MU beamforming, which delivers 7 times or 9.9
times as much as theoretical downlink peak throughput as downlink 2x2 MIMO in 8T8R
networking scenarios does.
NOTE
For details about multiplexing gains, see Beamforming (TDD).
6.2.2.2 Impacts
Network Impacts
l This function enables an eNodeB to simultaneously transmit up to 8, 16, or even 24 (for
trial) data streams, increasing the downlink cell throughput and spectral efficiency.
l The number of UEs paired within each TTI may change, leading to fluctuating
interference between paired UEs. As a result, the block error rate (BLER) of the
downlink PDSCH may increase.
l The downlink time-domain adaptive extended scheduling function improves the user
perceived rate of downlink heavy-traffic services.
l The MU beamforming-specific MCS index selection optimization function reduces the
IBLER.
l After a 4T/8T cell is reconstructed into a massive MIMO cell, the uplink and downlink
IBLERs may increase.
l When downlink 24-layer MU beamforming take effect, the
CellBf.MassiveMIMOMubfPairRule parameter must be set to
MU_WITHOUT_CORR_PAIR_RULE. As a result, the number of pairing layers and
BLER increase and the MCS index decreases.

eRAN
Function Impacts
Function Function Reference Description
Name Switch
Preferentia CellDlschAlgo. Scheduling Preferential use of resource allocation type

l use of RbgAllocStrate 1 does not take effect when MU
resource gy beamforming is enabled. When the
allocation CellDlschAlgo.RbgAllocStrategy parameter
type 1 is set to ADAPTIVE or TYPE1_FIRST,
the eNodeB preferentially uses resource
allocation type 0 to perform scheduling for
MU beamforming based on MU
beamforming pairing conditions.
Beamformi NoSrsSccBfSw Carrier l Beamforming is available only on the

ng in SCell itch option Aggregatio PCC, not on SCCs when uplink CA is
under the n not supported and beamforming in
CellAlgoSwitc SCells is not enabled.
h.NoSrsSccBfA l Beamforming is available on both the
lgoSwitch PCC and SCCs when either of the
parameter following conditions is met:
– Uplink CA is not supported and
beamforming in SCells is enabled.
– Uplink CA is supported.
Uplink CA CaUl2CCSwitc Carrier l The number of PRBs successfully paired

h option under Aggregatio for MU beamforming on each layer may
the n decrease by 5% when uplink CA is
CaMgtCfg.Cell enabled and the Dl2CCAckResShareSw
CaAlgoSwitch option is selected under the
parameter CellAlgoSwitch.PucchAlgoSwitch
parameter.
l Up to eight layers can be paired for MU
beamforming between UEs served by the
SCCs when uplink CA is enabled. This
restriction does not apply to pairing
between a UE served by an SCC and a
UE served by the PCC or a non-CA UE.

eRAN
Function Function Reference Description

Name Switch
Uplink InterFddTddC Carrier l The number of PRBs successfully paired

FDD+TDD aSwitch option Aggregatio for MU beamforming on each layer may
CA under the n decrease by 5% when FDD+TDD uplink
CaMgtCfg.Cell CA is enabled and the
CaAlgoSwitch Dl2CCAckResShareSw option is
parameter selected under the
CellAlgoSwitch.PucchAlgoSwitch
parameter.
l Up to eight layers can be paired for MU
beamforming between UEs served by the
SCCs when uplink CA is enabled. This
restriction does not apply to pairing
between a UE served by an SCC and a
UE served by the PCC or a non-CA UE.
6.2.3 Requirements
6.2.3.1 Licenses
l The operator has purchased and activated the license for TDLEOFD-121604 DL 8-Layer
MU-Beamforming. Four units of the license control item Massive MIMO DL 2-Layers
Name Control Item
TDLEOFD-12 DL 8-Layer LT1SDL8LM DL 8-Layer Per Cell

1604 MU- B00 MU-
Beamforming Beamforming(
TDD)
N/A N/A LT4SMMDL Massive Per 2 Layers

ML01 MIMO DL 2-
Layers
Extended
Processing
Unit
License(TDD)
l The operator has purchased and activated the license for TDLEOFD-121605 DL 16-
Layer MU-Beamforming. Eight units of the license control item Massive MIMO DL 2-
Layers Extended Processing Unit License(TDD) are required.

eRAN

Name Control Item

1604 MU- B00 MU-
TDD)
TDLEOFD-12 DL 16-Layer LT1SDL16MB DL 16-Layer Per Cell

1605 MU- 00 MU-
TDD)

ML01 MIMO DL 2-
Layers
Extended
Processing
Unit
License(TDD)
l The operator has purchased and activated the license for TDLEOFD-131603 DL 24-
Layer MU-Beamforming (Trial). 12 units of the license control item Massive MIMO
DL 2-Layers Extended Processing Unit License(TDD) are required.
Name Control Item

1604 MU- B00 MU-
TDD)
TDLEOFD-12 DL 16-Layer LT1SDL16MB DL 16-Layer Per Cell

1605 MU- 00 MU-
TDD)
TDLEOFD-13 DL 24-Layer LT4SDLMUB DL 24-Layer Per Cell

1603 MU- F00 MU-
(Trial) TDD)

ML01 MIMO DL 2-
Layers
Extended
Processing
Unit
License(TDD)

eRAN
6.2.3.2 Software
l TDLEOFD-121604 DL 8-Layer MU-Beamforming requires the following functions.
Function Name Function Switch Reference
Massive MIMO introduction N/A 4 Basic

Massive
MIMO
Functions
2-layer MU beamforming and 4- MuBfSwitch option under the Beamforming

layer MU beamforming CellAlgoSwitch.MuBfAlgoSwit (TDD)
ch parameter
Downlink flexible 3D BfSwitch option under the 6.1 3D

beamforming CellAlgoSwitch.BfAlgoSwitch Beamforming
parameter
l TDLEOFD-121605 DL 16-Layer MU-Beamforming requires the following functions.


ch parameter
Downlink 8-layer MU MuBfSwitch option under the 6.2.1

beamforming CellAlgoSwitch.MuBfAlgoSwit Principles
ch parameter
l TDLEOFD-131603 DL 24-Layer MU-Beamforming (Trial) requires the following

functions.

ch parameter
Downlink 8-layer MU MuBfSwitch option under the 6.2.1

beamforming and downlink 16- CellAlgoSwitch.MuBfAlgoSwit Principles
layer MU beamforming. ch parameter

eRAN

Multi-user split SplitSDMASwitch 6.5 Multi-User l Moving UE

SDMA option under the Split SDMA pairing
CellAlgoSwitch.Mu optimization or
BfAlgoSwitch big-event
parameter moving UE
protection is not
compatible with
the multi-user
split SDMA
function.
l Downlink 24-
layer MU
beamforming is
not compatible
with multi-user
split SDMA.
6.2.3.3 Hardware
See 4.3.3 Hardware. Downlink 24-layer MU beamforming (trial) requires a UBBPf1,
UBBPf3, or UBBPfw1 to be configured.

If 3D beamforming is enabled in a massive MIMO cell, the following parameters need to be
configured.

eRAN

Name
MUBF CellAlgoSwitch.MuBfAlg l Select the MuBfSwitch option under

Algorithm Switch oSwitch this parameter if MU beamforming is
required.
l Select the HarqRetranPairSwitch
option under this parameter if MU
beamforming is required during
HARQ retransmission.
l Clear the MubfResAdjSwitch option
under this parameter if the
TxRxMode parameter is set to
64T64R.
DL Scheduling CellAlgoSwitch.DlSchExt Select the

Extension Switch Switch DL_TIME_DIM_EXT_SCH_SWITC
H option under this parameter if the
downlink time-domain adaptive
extended scheduling function is required.
Max Number of CellBf.HighOrderMubfM l Downlink 8-layer MU beamforming:

MUBF Layers axLayer Set this parameter to
EIGHT_LAYERS.
l Downlink 16-layer MU
beamforming: Set this parameter to
SIXTEEN_LAYERS.
l Downlink 24-layer MU beamforming
(Trial): Set this parameter to
TWENTYFOUR_LAYERS.
Port Allocation CellBf.QualUEPortAvoid- Protection processing is recommended

Avoid for Mode for abnormal UEs subjected to
Continuous consecutive block errors when both MU
NACK UEs beamforming and dual-stream
beamforming are enabled. Otherwise, the
abnormal UEs may cause the service
drop rate to increase.
Massive MIMO CellBf.MassiveMIMOMu l Downlink 8- or 16-layer MU

MUBF Pairing bfPairRule beamforming: Set this parameter to
Rule MU_CORR_PAIR_RULE.
l Downlink 24-layer MU beamforming
(Trial): Set this parameter to
MU_WITHOUT_CORR_PAIR_R
ULE.
Cell Highload CellBf.MultiLayerThdSwi Set this parameter to 20.

Thd for Switch to tchToTM7
BF

eRAN

Name
Moving Ue CellBf.MovingUeMuBfSc l If big-event moving UE protection is

MUBF Scheme heme required, select the
BIG_EVENT_PROTECT_SCHE
ME option.
l If moving UE pairing optimization is
required, select the
HIGH_SPEED_OPTI_SCHEME
option.
MU CellCqiAdjAlgo.MuBfPa l Set this parameter to 20 when three

Beamforming cketThld or more layers are to be paired.
Packet Count l Set this parameter to 65535 when two
Threshold or fewer layers are to be paired. In
this situation, the MU beamforming-
specific MCS index selection
optimization function is disabled.
NOTE
The measurement period for counting MU
beamforming packets is 500 ms. Within a
measurement period, scheduling can be
performed for a maximum of 300 times for
uplink-downlink subframe configuration 1
and for a maximum of 400 times for uplink-
downlink subframe configuration 2.
Therefore, MU beamforming-specific MCS
index selection optimization does not take
effect at uplink-downlink subframe
configuration 1 when the CellCqiAdjAlgo.
MuBfPacketThld parameter is set to a value
greater than 300. This function additionally
does not take effect at uplink-downlink
subframe configuration 1 or 2 when the
CellCqiAdjAlgo.MuBfPacketThld
parameter is set to a value greater than 400.

eRAN

Name
Massive MIMO CellMMAlgo.MMAlgoOp l In low-speed mobility scenarios, it is

Algorithm tSwitch recommended that the
Optimization MU_PAIRING_MCS_EXACT_SW
Switch ITCH option be selected to improve
the MU beamforming-specific MCS
index selection accuracy.
l It is recommended that the
MU_PAIRING_VOLTE_SWITCH
option be selected to enable pairing
of VoLTE UEs for MU beamforming
when the network load is heavy in
terms of VoLTE UEs. It is
MU_PAIRING_VOLTE_SWITCH
option be deselected to disable
pairing of VoLTE UEs for MU
beamforming when the network load
is light in terms of VoLTE UEs.
NOTE
If VoLTE UEs do not participate in MU
beamforming pairing:
l The impact of inter-UE interference
on the PDSCH BLER decreases.
l The downlink voice packet loss rate
of massive MIMO cells decreases.
l In heavy-load scenarios, the
downlink traffic volume
(L.Thrp.bits.DL) decreases.
Massive MIMO CellMMAlgo.MassiveMi It is recommended that this parameter be

Initial Delta CQI moInitDeltaCqi set to 0. Confirm the value of the
parameter with Huawei engineers during
network optimization.

eRAN

Name
Beamforming CellMMAlgo.BfWeightTy If this parameter is set to ADAPT, MU

Weight Type pe beamforming adaptive power
normalization is enabled. In this case, the
eNodeB calculates the SNR threshold for
triggering switching between normalized
eigenvector beamforming (NEBF) and
power-limited eigenvector beamforming
(PEBF) in MU beamforming scenarios
based on the SINR, channel estimation
results, and adaptive factors of traffic
channels used before pairing, and
adaptively selects the optimal power
normalization algorithm. In this way,
MU beamforming performance
improves.
The UBBPem does not support MU
beamforming adaptive power
normalization.
MUBF Power CellBf.MubfPowerNormA l If this parameter is set to 0, PEBF

Normalization dptFactor power normalization is used for MU
Adaptive Factor beamforming.
l If this parameter is set to 10, NEBF
power normalization is used for MU
beamforming.
l If this parameter is set to a value
ranging from 0 to 10, the eNodeB
adjusts the threshold for triggering
switching between NEBF and PEBF
in MU beamforming scenarios. A
smaller value of this parameter leads
to a lower SNR threshold for
switching between NEBF and PEBF
and a higher probability of
implementing PEBF for MU
beamforming. This preferentially
guarantees the orthogonality of
paired layers. A larger value of this
parameter leads to a higher SNR
threshold for switching between
NEBF and PEBF and a higher
probability of implementing NEBF
for MU beamforming. This
preferentially makes full use of
antenna transmit power.

eRAN
Table 6-3 Optimization parameters for downlink time-domain adaptive extended scheduling
Name
Mass Flow Big ServiceIdentify- Set this parameter to a large value when
Packet Rate Para.MassFlowBigPacke- most heavy-traffic services are video or
Threshold tRateThld download services and to a small value
when most heavy-traffic services are
web browsing services.
Mass Flow ServiceIdentify- Set this parameter to a large value when

Packet Number Para.MassFlowPacketNu most heavy-traffic services are video or
Threshold mberThld download services and to a small value
when most heavy-traffic services are
web browsing services.

//Enabling MU beamforming as well as MU beamforming pairing for HARQ
retransmission UEs and disabling MU beamforming resource adjustment
MOD CELLALGOSWITCH: LocalCellId=0, BfAlgoSwitch=BfSwitch-1,
MuBfAlgoSwitch=MUBFSWITCH-1&MubfResAdjSwitch-0&HarqRetranPairSwitch-1;
//(Optional) Enabling time-domain adaptive extended scheduling
MOD CELLALGOSWITCH: LocalCellId=0, DlSchExtSwitch=DL_TIME_DIM_EXT_SCH_SWITCH-1;
//Configuring the maximum number of multiplexing layers
MOD CELLBF: LocalCellId=0, HighOrderMubfMaxLayer=EIGHT_LAYERS;
//Configuring the MU beamforming pairing rule
MOD CELLBF: LocalCellId=0, MassiveMIMOMubfPairRule=MU_CORR_PAIR_RULE;
//(Optional) Enabling identification and special handling of abnormal UEs
subjected to consecutive block errors and resulting network drops
MOD CELLBF: LocalCellId=0, QualUEPortAvoidMode=USERIDENTIFYRANK2PAIRING;
//Configuring the threshold for triggering the MU beamforming-specific MCS index
selection optimization function
MOD CELLCQIADJALGO: LocalCellId=0, MuBfPacketThld=20;
//(Optional) Configuring the layer quantity threshold for triggering switching to
TM7 when there are many layers to be paired
MOD CELLBF: LocalCellId=0, MultiLayerThdSwitchToTM7=20;
//(Optional) Enabling the MU beamforming-specific MCS index selection
optimization switch and MU beamforming pairing of VoLTE UEs, and configuring the
initial CQI adjustment value in massive MIMO scenarios
MOD CELLMMALGO: LocalCellId=0,
MMAlgoOptSwitch=MU_PAIRING_MCS_EXACT_SWITCH-1&MU_PAIRING_VOLTE_SWITCH-1,
MassiveMimoInitDeltaCqi=-1;
//Configuring the MU beamforming power normalization adaptive factor
MOD CELLMMALGO: LocalCellId=0, BfWeightType=ADAPT;
MOD CELLBF: LocalCellId=0, MubfPowerNormAdptFactor=6;

//Disabling MU beamforming
MOD CELLALGOSWITCH: LocalCellId=0,
MUBFALGOSWITCH=MuBfSwitch-0&TM9MuBfSwitch-0&MubfResAdjSwitch-0&HarqRetranPairSwitc
h-0;


eRAN

Step 1 Perform downlink services on 16 or more UEs compliant with 3GPP Release 8 or later. These
UEs should have different physical locations.
Step 2 Use the U2020 to perform signaling tracing. For details, see 6.2.4.3 Network Monitoring. If
the measured value of any of the monitoring objects listed in Table 6-4 does not equal 0, MU
beamforming has been activated
Table 6-4 MU beamforming monitoring objects

Monitoring Object Meaning
Number of Massive Number of RBs paired with massive MIMO MU

MIMO MUBF Pairing beamforming TM7 UEs. It is the average of the cumulative
TM7 RB (Num) total number of RBs paired with TM7 UEs at each TTI at the
end of the monitoring period.
Number of Available Number of RBs that can be paired for massive MIMO MU
Massive MIMO MUBF beamforming. It is the average of the cumulative total
Pairing RB (Num) number of RBs paired with the massive MIMO MU
beamforming at each TTI at the end of the monitoring period.
Number of Massive Number of RBs paired with the massive MIMO MU

MIMO MUBF Success beamforming at layer N. It is the cumulative total number of
Pairing RB (Num) in RBs paired with the massive MIMO MU beamforming at
xLayer layer X of each TTI and calculating the average number at the
----End
Step 1 Monitor counters in the following function subsets:
l Number of PRBs for MUBF UEs at Each Layer
l Number of TTIs During Which UEs Are Successfully Paired in the Downlink
l Number of Layers Paired for Massive MIMO MU Beamforming
l Total Number of RBs Transmitted in the Downlink in Massive MIMO Scenarios
l Total Number of TBs Transmitted in the Downlink in Massive MIMO
l Number of Bits Successfully Transmitted in the Downlink in Massive MIMO
l Total Number of TBs Incorrectly Transmitted in the Downlink in Massive MIMO
Step 2 Monitor the SRS SINR using the following counters.

1526748696 L.UL.SINR.SRS.Index0 Number of SRS SINR samples in

range 0

eRAN

range 1

range 2

range 3

range 4
----End
When massive MIMO MU beamforming is enabled, the number of pairing layers and PRBs
increases and the measured values of the following counter may reach 64 bits.
1526728881 L.ChMeas.BF.PRB.OL.Rank1 Total number of used downlink

PRBs in beamforming rank 1
mode.
1526743729 L.ChMeas.BF.TM7.PRB.OL.Ra Total number of PRBs used for

nk1 downlink beamforming in TM7
rank 1 mode.
1526737845 L.ChMeas.PRB.TM7 Total number of used downlink

PRBs in TM7.
1526727391 L.ChMeas.MIMO.PRB.CL.Ran Total number of physical resource

k1 blocks (PRBs) used for rank 1
transmission in downlink closed-
loop MIMO
1526727392 L.ChMeas.MIMO.PRB.CL.Ran Total number of PRBs used for

k2 rank 2 transmission in downlink
closed-loop MIMO

closed-loop MIMO

closed-loop MIMO
When MU beamforming is enabled in massive MIMO scenarios, the following counters

measure the number of PRBs actually scheduled for UEs in a cell. The number of PRBs is
measured by UE, and therefore the total number of PRBs scheduled in a 20 MHz cell may
exceed 100, except for the counters L.ChMeas.PRB.DL.Used.Avg and
L.ChMeas.PRB.DL.DrbUsed.Avg.Equivalent.

eRAN
1526726740 L.ChMeas.PRB.DL.Used.Avg Average number of used downlink

PRBs
1526737871 L.ChMeas.PRB.DL.DrbUsed.Av Average number of standardized

g.Equivalent PRBs used for downlink services
1526746016 L.ChMeas.PRB.DL.DrbUsed.Av Average number of downlink

g.ExtQci.Index0 PDSCH PRBs used by DRBs for
services with an extended QCI of
counter index 0

g.VoIP.Equivalent PRBs used for downlink VoIP
services

g.QCI2.Equivalent PRBs used for downlink QCI 2
services
1526728424 L.ChMeas.PRB.DL.PCell.Used. Average number of downlink

Avg PRBs occupied by CA UEs that
use the local cell as their primary
serving cell
1526732911 L.ChMeas.PRB.DL.PCell.Relaxe Number of downlink PRBs

dBackhaulCAUsed.Avg occupied by CA UEs that treat the
local cell as their PCell in the
relaxed-backhaul-based inter-
eNodeB CA state
1526732912 L.ChMeas.PRB.DL.SCell.Relaxe Number of downlink PRBs

dBackhaulCAUsed.Avg occupied by CA UEs that treat the
local cell as their SCell in the
relaxed-backhaul-based inter-
eNodeB CA state
1526739796 L.RB.DL.PCell.CAUsed.PLMN Number of PDSCH PRBs

occupied by CA UEs of a specific
operator that treat the local cell as
their PCell
1526739797 L.RB.DL.SCell.CAUsed.PLMN Number of PDSCH PRBs used by

operator-specific CA UEs that
treat the local cell as their SCell
1526739718 L.ChMeas.PRB.DL.PttUsed.Avg Average number of downlink

.PLMN PRBs used by PTT services for a
specific operator
1526728293 L.RBUsedOwn.DL.PLMN Average number of own PDSCH

PRBs used by a specific operator

eRAN
1526741668 L.RBUsedOtherGroup.DL.PLM Average number of other operator

N resource group downlink PRBs
used by a specific operator in an
operator resource group in a cell
Signaling Tracing
l Cell-level MU beamforming monitoring
Step 2 From the navigation tree on the left of the Signaling Trace Management tab page, choose
LTE > Cell Performance Monitoring > Multi-User BF (Cell) Monitoring. The Multi-User
BF (Cell) Monitoring dialog box is displayed.
Step 3 In the displayed dialog box, enter the tracing task name in the Trace Name text box, select
the eNodeB to be monitored, and click Next.
Step 4 Enter the local cell ID, and select Massive MIMO MUBF Pair in the Test Items area.
Step 5 On the Signaling Trace Management tab page, double-click the trace task that you have
created to view the monitoring result. For the detailed description of the monitoring result,
press F1 to obtain the online help.
----End
l UE-level MU beamforming monitoring
LTE > User Performance Monitoring > Multi-User BF (User) Monitoring. The Multi-
User BF (User) Monitoring dialog box is displayed.
Step 3 In the displayed dialog box, enter the tracing task name in the Trace Name text box, select
the eNodeB to be monitored, and click Next.
Step 4 In the displayed dialog box, enter the values in the MMEc and mTMSI text boxes, and click
Finish.
Step 5 On the Signaling Trace Management page, double-click the tracing task that you have
created to view the values of the measurement items Indep-Indep Number of successful
MUBF pairing RB and Indep-Joint Number of successful MUBF pairing RB in the
monitoring result. For the detailed description of the monitoring result, press F1 to obtain the
online help.
----End
Observation by Conducting a Fixed-Point or Mobile Test on a Single UE

A fixed-point test or mobile test can be conducted using a single UE to check the effect on the
network.
l Fixed-point test

eRAN
a. Run uplink and downlink multi-thread FTP services at 5 to 10 different locations on

the network. Select areas near the center, middle, and edge of a cell.
b. Compare the uplink and downlink transmission rates measured at different locations
before and after massive MIMO is deployed.
Expected result: The transmission rates increase in both the uplink and downlink.
l Mobile test
a. Perform FTP packet injection in both the uplink and downlink along the same route
in the network reconstruction area.
b. Compare the uplink and downlink transmission rates measured before the network
reconstruction with those measured after the network reconstruction.
Expected result: The transmission rates increase in both the uplink and downlink.
6.3 TM9
For details about the network analysis and running environment of the TM9 feature, see
Beamforming (TDD).
6.3.1 Principles
The following TM9 features are available in massive MIMO scenarios:
l TDLAOFD-00100114 DL 2-Layer MIMO Based on TM9

For details about TM9, see Beamforming (TDD). The availability of the TM9 features
increases the UE transmission modes in massive MIMO scenarios. TM9 hybrid precoding
requires downlink 2-layer MIMO based on TM9 or downlink 4-layer MIMO based on TM9 to
be enabled.

For details about how to enable TM9 in non-massive MIMO scenarios, see Beamforming
(TDD). The procedure for enabling TM9 in massive MIMO scenarios is different from that
used in non-massive MIMO scenarios. This section describes how to enable TM9 in massive
MIMO scenarios.

If TM9 is to be enabled in massive MIMO cells, the following parameters need to be set.

Name
Enhanced MIMO CellAlgoSwitch.EnhMIM When TM9 is enabled, select the

Switch OSwitch TM9Switch option.

eRAN

Name
maximum CellDlschAlgo.MaxMimo l Set this parameter to

number of RankPara SW_MAX_SM_RANK_2 when 2-
MIMO layers layer TM9 is required.
l Set this parameter to
SW_MAX_SM_RANK_4 when 4-
layer TM9 is required.
CSI-RS CellDlschAlgo.CsiRsSfSc It is recommended that the

Subframe hStrSwitch UnCfgCsiRsUESchSwitch option be
Scheduling deselected when TM9 is enabled so that
Strategy Switch UEs not configured with CSI-RSs are not
scheduled in CSI-RS subframes.
If TM9 hybrid precoding is disabled and
the TM9-capable UE penetration rate is
low, it is recommended that the
UnCfgCsiRsUEDeOrderSchSwitch
option be selected.
If TM9 hybrid precoding is enabled,
deselect the UnCfgCsiRsUEDeOr-
derSchSwitch option.
CSI-RS Switch CellCsiRsParaCfg.CsiRs l If TM9 is enabled, set this parameter

Switch to FIXED_CFG.
l If TM9 is disabled, set this parameter
to NOT_CFG.
CsiRs Port CellCsiRsParaCfg.CsiRs Set this parameter to CSI-RS_PORT_4

Number PortNum if TM9 hybrid precoding is enabled.
CSI-RS Period CellCsiRsParaCfg.CsiRs Set this parameter to ms80. The cell will
Period reset if the value is changed.
Compatibility ENodeBAlgoSwitch.Com To configure the CSI-RS policy for TM9-

Control Switch patibilityCtrlSwitch incapable UEs compliant with 3GPP
Release 10 or later, select the
UeCsiRsCfigCtrlSwitch option. In this
case, if the UEs have compatibility
issues, the UE performance deteriorates.
Check with the operator whether UEs on
the live network are compliant with
3GPP Release 10 or later. If not, deselect
the UeCsiRsCfigCtrlSwitch option.
Operator ENodeBAlgoSwitch.Oper This parameter is valid only when the

Specific atorSpecificAlgoSwitch UeCsiRsCfigCtrlSwitch option is
Algorithm selected under the CompatibilityCtrlS-
Switch witch parameter.

eRAN

Name
Scc Bf Mimo CellBfMimoParaCfg.Scc Set this parameter to ON(On) when PMI

Adaptive Switch BfMimoAdaptiveSwitch feedback-dependent TM9 is enabled in
downlink CA scenarios or when uplink
CA is enabled.
LCS switch ENodeBAlgoSwitch.LcsS Clear the OtdoaSwitch option.

witch
TM3 Rank2 To CellBfMimoParaCfg.Tm Set this parameter to 9.

TM9 Rank4 3Rank2ToTm9Rank4Offs
Offset et
TM9 Rank4 To CellBfMimoParaCfg.Tm Set this parameter to 40.

TM3 Rank2 9Rank4ToTm3Rank2Offs
Offset et
256QAM TM3 CellBfMimoParaCfg.Tm Set this parameter to 60.

to TM9 3ToTm9SwtgSEffOfs256q
Switching am
Spectral Eff
Offset
256QAM TM9 CellBfMimoParaCfg.Tm Set this parameter to 75.

to TM3 9ToTm3SwtgSEffOfs256q
Switching am
Spectral Eff
Offset

//Enabling the TM9 algorithm
MOD CELLALGOSWITCH: LocalCellId=0, ENHMIMOSWITCH=TM9Switch-1;
//Turning on the CSI-RS configuration switch and setting the CSI-RS period, the
number of CSI-RS ports, and adaptive CSI-RS configuration
MOD CELLCSIRSPARACFG: LocalCellId=0, CSIRSSWITCH=FIXED_CFG, CSIRSPERIOD=ms80,
CsiRsPortNum=CSI_RS_PORT_4;
//Configuring the maximum number of MIMO layers
MOD CELLDLSCHALGO: LocalCellId=0, MAXMIMORANKPARA=SW_MAX_SM_RANK_4;
//Setting the threshold offset for switching between TM3 and TM9
MOD CELLBFMIMOPARACFG: LocalCellId=0, Tm3Rank2ToTm9Rank4Offset=9,
Tm9Rank4ToTm3Rank2Offset=40, Tm3ToTm9SwtgSEffOfs256qam=60,
Tm9ToTm3SwtgSEffOfs256qam=75;
//Configuring the CSI-RS subframe scheduling strategy switch
MOD CELLDLSCHALGO: LocalCellId=0,
CsiRsSfSchStrSwitch=UnCfgCsiRsUESchSwitch-0&UnCfgCsiRsUEDeOrderSchSwitch-0;
//(Optional) Selecting the UeCsiRsCfigCtrlSwitch option to configure the CSI-RS
policy for TM9-incapable UEs compliant with 3GPP Release 10 or later. In this
case, if the UEs have compatibility issues, the UE performance deteriorates.
Check with the operator whether UEs on the live network comply with 3GPP Release
10 or later. If not, deselect this option.
MOD ENODEBALGOSWITCH: CompatibilityCtrlSwitch=UeCsiRsCfigCtrlSwitch-0,
OperatorSpecificAlgoSwitch=CsiRsCfgSpecificAlgoSwitch-0;
//(Optional) Enabling SCC-specific adaptive switching between MIMO and
beamforming if PMI feedback-dependent TM9 is required in downlink CA scenarios or

eRAN
uplink CA is enabled
MOD CELLBFMIMOPARACFG: LocalCellId=0, SccBfMimoAdaptiveSwitch=ON;
//Disabling OTDOA
MOD ENODEBALGOSWITCH: LcsSwitch=OtdoaSwitch-0;

See Beamforming (TDD).


The observation method of TM9 is the same as that of 3D beamforming. For details, see
6.1.4.2 Activation Verification.

See Beamforming (TDD).
6.4 TM9 Hybrid Precoding

This section describes TDLEOFD-131615 Massive MIMO TM9 Hybrid Precoding.
6.4.1 Principles
TM9 hybrid precoding exploits the array antenna form of massive MIMO networking to
further improve the performance of the following TM9 features:

NOTE
For details about the preceding TM9 features, see Beamforming (TDD).
When TM9 hybrid precoding is enabled, the eNodeB:
l Applies double weighting on closed-loop TM9 UEs.

This function is controlled by the TM9HybridPrecodingSwitch option under the
CellAlgoSwitch.EnhMIMOSwitch parameter.
– Horizontal-plane weighting: The beam is divided into multiple orthogonal beams in
the horizontal plane based on designed orthogonal weighting values, and each beam
is configured with independent measurable CSI-RSs. The eNodeB selects the
weighting value with the best beamforming capability based on the channel state.
– Vertical-plane weighting: The eNodeB performs beamforming based on UEs' PMI
feedback.
l Performs split SDMA on closed-loop TM9 UEs served by the SCC (trial).
Closed-loop TM9 rank 1 and rank 2 UEs served by the SCC can participate in split
SDMA pairing if all of the following conditions are met:
– Multi-user split SDMA is enabled.

eRAN
– Double weighting on closed-loop TM9 UEs is enabled.

– The TM9SplitSdmaSwitch option is selected under the
CellAlgoSwitch.MuBfAlgoSwitch parameter.
For details, see 6.5 Multi-User Split SDMA.
Other closed-loop TM9 UEs support single-UE scheduling for split SDMA but do not
participate in split SDMA pairing.
In CA+massive MIMO scenarios, after TM9 hybrid precoding is enabled on an LTE TDD
carrier:
l It is recommended that beamforming in SCells be enabled so that the UEs with no SRS
reported can enter PMI feedback-dependent TM9 in the LTE TDD SCell when related
trigger conditions are met. In this way, the UE receives the gains of beamforming based
on TM9 hybrid precoding in this TDD SCell, and the average cell throughput rises. For
details about this function, see Carrier Aggregation.
l If beamforming in SCells is not enabled or the conditions for triggering beamforming in
SCells are not met, CA UEs with no SRS reported in the LTE TDD SCell work only in
TM3 and cannot enter PMI feedback-dependent TM9. For details about the trigger
conditions, see Carrier Aggregation.
6.4.2.1 Benefits
l Improved downlink cell throughput and spectral efficiency
l Improved throughput of TM9 UEs
l Total increased proportion of 4R UEs working in TM9 rank 3 or 4
It is recommended that basic massive MIMO functions be used with TM9 hybrid precoding,
especially when there are many TM9-capable 4R UEs. TM9 hybrid precoding must be
enabled if split SDMA is required for closed-loop TM9 UEs.
6.4.2.2 Impacts
Network Impacts
l The gain may be negative when the TM9 UE penetration rate is low.
l After this feature is enabled, the gains for 8R UEs not located at the cell center or edge
are greater than the gains for 4R UEs at the same position.

eRAN
Function Impacts
Name
Beamforming NoSrsSccBfSwitch Carrier In CA+massive MIMO

in SCell option under the Aggregation scenarios, the PCC
CellAlgoSwitch.NoSrsS supports TM9 hybrid
ccBfAlgoSwitch precoding. The support
parameter of SCCs for TM9 hybrid
precoding is as follows:
l If uplink CA is
enabled, uplink SCCs
also support TM9
hybrid precoding.
l If uplink CA is not
enabled and
beamforming in
SCells is enabled,
SCCs without SRS
feedback support
TM9 hybrid
precoding.
l If neither uplink CA
nor beamforming in
SCells is enabled,
SCells do not support
TM9 hybrid
precoding.
6.4.3 Requirements
6.4.3.1 Licenses
TDLEOFD-131 Massive MIMO TM9 LT4SMMTM9 Per Cell

615 Hybrid Precoding HP0

eRAN
6.4.3.2 Software
Name
CSI-RS port CellCsiRsParaCfg.CsiR None Set the

number sPortNum CellCsiRsParaCfg.CsiR
sPortNum parameter to
CSI_RS_PORT_4 if
TM9 hybrid precoding is
required.

MIMO
Functions
Downlink 2- TM9Switch option Beamforming None

layer MIMO under the (TDD)
based on TM9 CellAlgoSwitch.EnhMI
MOSwitch parameter
Downlink 4- TM9Switch option Beamforming None

layer MIMO under the (TDD)
based on TM9 CellAlgoSwitch.EnhMI
MOSwitch parameter

Name
Scheduling of UnCfgCsiRsUESchS- None TM9 hybrid precoding

CSI-RS- witch option under the must not be enabled
unconfigured CellDlschAlgo.CsiRsSfS when the
UEs chStrSwitch parameter UnCfgCsiRsUESchS-
witch option is selected.
Scheduling of UnCfgCsiRsUEDeOr- None TM9 hybrid precoding

CSI-RS- derSchSwitch option must not be enabled
unconfigured under the when the
UEs through CellDlschAlgo.CsiRsSfS UnCfgCsiRsUESchS-
MCS index chStrSwitch parameter witch option is selected.
reduction

eRAN

Name
CSI-RS period CellCsiRsParaCfg.CsiR None If the

sPeriod CellCsiRsParaCfg.CsiR
sPeriod parameter is set
to ms5, the
TM9HybridPrecodingS
witch option must not be
selected under the
CellAlgoSwitch.EnhMI
MOSwitch parameter.
OTDOA OtdoaSwitch option LCS OTDOA cannot be

under the enabled when the
ENodeBAlgoSwitch.Lcs TM9Switch option is
Switch parameter selected under the
MOSwitch parameter.
The TM9Switch option
must be selected under
the
MOSwitch parameter for
TM9 hybrid precoding.
6.4.3.3 Hardware
See 4.3.3 Hardware.
6.4.3.4 Others

If TM9 hybrid precoding is required on the basis of TM9 in massive MIMO cells, the
following parameters need to be configured.

eRAN

PDSCH Split Beam Config CellBf.PdschSplitBeamCon The value

Index figIndex CONFIG_DEFAULT
indicates the largest number
of beams and the widest
PDSCH coverage scope, and
the value
CONFIG_INDEX3
indicates the smallest
number of beams and the
narrowest PDSCH coverage
scope. The value
CONFIG_DEFAULT is
recommended.
NOTE
Cell reactivation will be
triggered to make the
modification take effect if the
parameter is modified.
Enhanced MIMO Switch CellAlgoSwitch.EnhMIMO Select the

Switch TM9HybridPrecodingS-
witch option.
l Beam split weight values are available only when the beam weight file inside the eNodeB
software package is activated. If no beam split weight value is available, enabling TM9
hybrid precoding will lead to cell faults.
l Run the ACT BFANTDB command with the OPMODE parameter set to SWFILE to
activate the beam weight file.

//Activating the beam weight file in the software package
//Setting the PDSCH split beam configuration index
MOD CELLBF: LocalCellId=0,PdschSplitBeamConfigIndex=CONFIG_DEFAULT;
//Enabling TM9 hybrid precoding
MOD CELLALGOSWITCH: LocalCellId=0, EnhMIMOSwitch=TM9HybridPrecodingSwitch-1;

MOD CELLALGOSWITCH: LocalCellId=0, EnhMIMOSwitch=TM9HybridPrecodingSwitch-0;


eRAN

The observation method of TM9 is the same as that of 3D beamforming. For details, see
6.1.4.2 Activation Verification.

1526728261 L.Thrp.bits.DL Total volume of downlink

data transmitted at the
PDCP layer in a cell
1526729005 L.Thrp.bits.DL.LastTTI Downlink PDCP-layer

traffic volume sent in the
last TTI before the buffer is
empty
1526729015 L.Thrp.Time.DL.RmvLast Data transmission duration

TTI except the last TTI before
the downlink buffer is
empty
1526732737 L.ChMeas.RI.Rank3 Number of times a UE

reports rank 3
1526732738 L.ChMeas.RI.Rank4 Number of times a UE

reports rank 4
1526728174 L.ChMeas.MIMO.PRB.C Total number of PRBs used

L.Rank3 for rank 3 transmission in
downlink closed-loop
MIMO
1526728175 L.ChMeas.MIMO.PRB.C Total number of PRBs used

L.Rank4 for rank 4 transmission in
downlink closed-loop
MIMO
1526732723 L.Traffic.User.TM9.Avg Average number of UEs that

apply TM9 in a cell
Average downlink UE throughput = (L.Thrp.bits.DL – L.Thrp.bits.DL.LastTTI)/

L.Thrp.Time.DL.RmvLastTTI
6.5 Multi-User Split SDMA

This section describes TDLEOFD-131612 Multi-User Split SDMA in Massive MIMO.

eRAN
6.5.1 Principles
Multi-user split SDMA enhances the capacity of massive MIMO cells in which MU
beamforming is enabled. It improves downlink service performance of massive MIMO cells
through SDMA on PDSCH split beams in the following scenarios:
l Moving UEs need to be served.
l SRS interference needs to be suppressed.
It is recommended that this function be used with TM9 hybrid precoding so that multi-user
split SDMA takes effect on closed-loop TM9 rank 1 and rank 2 UEs served by the SCC. In
this way, downlink service performance improves in densely populated urban areas with
strong coverage. For details about TM9 hybrid precoding, see 6.4 TM9 Hybrid Precoding.
This feature is controlled by the SplitSDMASwitch option under the
CellAlgoSwitch.MuBfAlgoSwitch parameter. Multi-user split SDMA is disabled if this
option is deselected. The following table describes the principles applicable when this option
is selected.
If... Then...
The CellBf.SplitSdmaAdaptionPeriod Adaptive switching between MU

parameter is set to a value other than beamforming and multi-user split SDMA is
FORCE_SPLIT_SDMA supported. The eNodeB enters or exits
multi-user split SDMA based on the
principles described in Table 6-7 in a period
specified by the
CellBf.SplitSdmaAdaptionPeriod
parameter. MU beamforming applies after
the eNodeB exits multi-user split SDMA.
The CellBf.SplitSdmaAdaptionPeriod The eNodeB directly initiates multi-user

parameter is set to split SDMA without identifying application
FORCE_SPLIT_SDMA scenarios.
Table 6-7 Mechanism for entering and exiting multi-user split SDMA
Whether TM9 Entering or Condition
Hybrid Precoding Exiting Multi-
Is Enabled User Split SDMA
Yes Entered Proportion of UEs with limited SRS

resources in a cell ≥
CellMMAlgo.ASplitSdmaSrsLmtUe-
PropThld or proportion of UEs working in
close-loop TM9 ≥
CellMMAlgo.ASplitSdmaTm9UePropThld

eRAN
Whether TM9 Entering or Condition

Hybrid Precoding Exiting Multi-
Is Enabled User Split SDMA
Exited Proportion of UEs with limited SRS

resources in a cell <
PropThld and proportion of UEs working in
close-loop TM9 <
CellMMAlgo.ASplitSdmaTm9UePropThld
No Entered Proportion of UEs with limited SRS

resources in a cell ≥
PropThld
Exited Proportion of UEs with limited SRS

resources in a cell <
PropThld
NOTE
l UEs with limited SRS resources include moving UEs and UEs subjected to SRS interference.
l A UE is identified as the UE subjected to SRS interference when the SRS SINR of the UE less than
the value of the CellMMAlgo.SplitSdmaUeIdenSrsSinrThld parameter for a specified number of
consecutive times.
The procedure for multi-user split SDMA is as follows:

1. The eNodeB identifies UEs working in closed-loop TM9 and UEs subjected to limited
SRS resources. Other UEs belong to normal UEs.
2. The eNodeB periodically determines the target beam.
a. The eNodeB measures the RSRP of the downlink split beam based on uplink SRS
quality and regards the beam with the largest RSRP value as the target beam of the
UE.
b. The eNodeB obtains the complete beam weight coefficients of the horizontal and
vertical planes based on the attributes of the target beam.
The weight coefficient is obtained based on the setting of the
CellBf.PdschSplitBeamConfigIndex parameter for UEs working in closed-loop
TM9 and UEs subject to limited SRS resources. The weight coefficient is obtained
through MU beamforming for normal UEs.
3. During resource allocation, the eNodeB pairs UEs subjected to SRS resources, and
closed-loop TM9 rank 1 and rank 2 UEs served by an SCC, and normal UEs in hybrid
mode. All UEs participate in SDMA. Figure 6-9 shows hybrid pairing. In the figure, the
beam pointing to UE 1 is split into two beams, forming rank 2.
– For closed-loop TM9 UEs

eRAN
If... Then...
The TM9HybridPrecodingSwitch Close-loop TM9 UEs support only

option is selected under the single-UE scheduling and do not
CellAlgoSwitch.EnhMIMOSwitch participate in split SDMA pairing.
parameter and the
TM9SplitSdmaSwitch option is not
selected under the
CellAlgoSwitch.MuBfAlgoSwitch
parameter
If both the TM9HybridPrecodingS- l Close-loop TM9 rank 1 and rank 2

witch option under the UEs served by the SCC support
CellAlgoSwitch.EnhMIMOSwitch only split SDMA and do not
parameter and the participate in split SDMA pairing.
TM9SplitSdmaSwitch option under l Other close-loop TM9 UEs support
the CellAlgoSwitch.MuBfAlgoSwitch only single-UE scheduling and do
parameter are selected not participate in split SDMA
pairing.
The maximum number of pairing
layers allowed for close-loop TM9
rank 1 and rank 2 UEs served by the
SCC cannot exceed the value of the
CellBf.HighOrderMubfMaxLayer
parameter or 4.
– UEs subjected to limited SRS resources support only split SDMA and can
participate in split SDMA pairing.
– For normal UEs, MU beamforming applies. Normal UEs can be paired with UEs
subjected to limited SRS resources or closed-loop TM9 rank 1 and rank 2 UEs
served by the SCC for SDMA pairing.
Figure 6-9 Hybrid pairing for multi-user split SDMA

eRAN
6.5.2.1 Benefits
This function improves the average downlink spectral efficiency and average downlink user-
perceived rate in target application scenarios.
The following table describes the application scenarios of massive MIMO split SDMA.
Application Scenario Description
Strong coverage scenarios, Characteristics: strong capacity demand, high user density,
such as central business scattered user distribution, and high proportion of UEs
districts (CBDs) and In such scenarios, multi-user split SDMA improves the
campuses number of paired layers for closed-loop TM9 rank 1 and rank
2 UEs served by the SCC.
Mobility scenarios, such Characteristics: heavy traffic, strong capacity demand in the
as traffic hubs and rally uplink and downlink, high user density, scattered user
scenarios distribution, and most UEs having mobility characteristics
suitable for beam-domain pairing
In such scenarios, multi-user split SDMA increases the
beamforming beamwidth and reduces interference between
beams and the mobility sensitiveness of SDMA.
Scenarios with limited Characteristics: many users, huge capacity demand, and
SRS resources, such as clearly insufficient SRS resources or severe uplink
stadiums, concerts, and interference, leading to low SRS SINR
contiguous networking In such scenarios, multi-user split SDMA improves pairing
areas performance regardless of SRS weight estimation.
The following counters can be used to evaluate the SRS
interference in the local cell:
l L.UL.SINR.SRS.Index0
Determine whether to enable multi-user split SDMA based on
the SRS interference. For example, if the proportion of
samples whose SRS SINR is within range 0 is greater than
40%, there is SRS interference in the local cell and multi-user
split SDMA is recommended. The proportion of samples
whose SRS SINR is within range 0 is calculated using the
following formula:
Proportion of samples whose SRS SINR is within range 0 =
L.UL.SINR.SRS.Index0/(L.UL.SINR.SRS.Index0 +
L.UL.SINR.SRS.Index1 + L.UL.SINR.SRS.Index2 +
L.UL.SINR.SRS.Index3 + L.UL.SINR.SRS.Index4)

eRAN
6.5.2.2 Impacts
Network Impacts
l This function improves the average downlink spectral efficiency of the cell.
l This function improves the average downlink UE-perceived rate.
l If the number of downlink scheduled UEs increases in the subframes where both uplink
and downlink CCE resources are allocated, more CCEs are used in the downlink and
fewer CCEs are available in the uplink. As a result, the number of UEs scheduled in the
uplink decreases, affecting uplink capacity.
Function Impacts
Name
Beamforming CellBf.BfWeightOptDeg 7.6 After beamforming

weight reeFactor Beamforming weight optimization is
optimization Weight enabled, UEs with low
Optimization SRS SINRs will not enter
multi-user split SDMA.
UEs with low SRS
SINRs already working
in multi-user split SDMA
will exit the transmission
mode.
Split SDMA for SPLIT_SDMA_SCHE None If multi-user split SDMA

moving UEs ME option under the for moving UEs is
CellBf.MovingUeMuBfS enabled, it is
cheme parameter recommended that the
SPLIT_SDMA_SCHE
ME option be selected
under the
CellBf.MovingUeMuBfS
cheme parameter to
improve the throughput
of moving UEs.
6.5.3 Requirements
6.5.3.1 Licenses
TDLEOFD-131 Multi-User Split SDMA LT4SMUSSM Per Cell

612 in Massive MIMO M00

eRAN
6.5.3.2 Software
Name
TM9 hybrid TM9HybridPrecodingS 6.4 TM9 If multi-user split SDMA

precoding witch option under the Hybrid is required for closed-
CellAlgoSwitch.EnhMI Precoding loop TM9 UEs, TM9
MOSwitch parameter hybrid precoding must be
and enabled.
TM9SplitSdmaSwitch
option under the
CellAlgoSwitch.MuBfAl
goSwitch parameter
Downlink 8- MuBfSwitch option 6.2 MU Multi-user split SDMA

layer MU under the Beamforming requires either of the
beamforming or CellAlgoSwitch.MuBfAl functions.
downlink 16- goSwitch parameter
layer MU
beamforming

Name
Moving UE CellBf.MovingUeMuBfS None The

MU cheme CellBf.MovingUeMuBfS
beamforming cheme parameter can be
scheme set to
BIG_EVENT_PROTE
CT_SCHEME,
HEAVY_LOAD_SCHE
ME,
LIGHT_LOAD_SCHE
ME, or
HIGH_SPEED_OPTI_
SCHEME only when the
SplitSDMASwitch
option is deselected
under the
CellAlgoSwitch.MuBfAl
goSwitch parameter.

eRAN

Name
Downlink 24- MuBfSwitch option 6.2 MU Multi-user split SDMA is

layer MU under the Beamforming not supported when the
beamforming CellAlgoSwitch.MuBfAl CellBf.HighOrderMubf
goSwitch parameter MaxLayer parameter is
set to a value greater than
SIXTEEN_LAYERS.
UE pairing for CellBf.MassiveMIMOM 6.2 MU If both of the following

MU ubfPairRule Beamforming conditions are met, the
beamforming CellBf.MassiveMIMOM
without ubfPairRule parameter
considering can be set to
correlation MU_WITHOUT_COR
R_PAIR_RULE, but UE
pairing for MU
beamforming without
considering correlation
does not take effect:
l The
SplitSDMASwitch or
TM9SplitSDMASwit
ch option is selected
under the
CellAlgoSwitch.Mu
BfAlgoSwitch
parameter.
l Multi-user split
SDMA is triggered.
6.5.3.3 Hardware
See 4.3.3 Hardware.
6.5.3.4 Others

If multi-user split SDMA is required on the basis of MU beamforming, the following
parameters need to be configured.

eRAN

Name
MUBF CellAlgoSwitch.MuBfAl Select the SplitSDMASwitch option.

Algorithm goSwitch
Switch
PDSCH Split CellBf.PdschSplitBeam The value CONFIG_DEFAULT indicates

Beam Config ConfigIndex the largest number of beams and the widest
Index PDSCH coverage scope, and the value
CONFIG_INDEX3 indicates the smallest
number of beams and the narrowest PDSCH
coverage scope. The value
CONFIG_DEFAULT is recommended.
NOTE
Cell reactivation will be triggered to make the
modification take effect if the parameter is
modified.
Split SDMA CellBf.SplitSdmaAdapti l Split SDMA is triggered directly when

Adaption onPeriod this parameter is set to
Period FORCE_SPLIT_SDMA.
l The eNodeB determines whether to
trigger multi-user split SDMA based on
the scenario status identified within the
period when this parameter is set to
PERIOD_15MIN through
PERIOD_120MIN. A short period
results in a high probability of triggering
multi-user split SDMA and high pairing
efficiency, but frequent entries to or exits
from split SDMA and more signaling
overheads for transmission mode
reconfigurations. A long period leads to
a low probability of triggering split
SDMA and low pairing efficiency, but
infrequent entries to or exits from split
SDMA and less signaling overheads for
transmission mode reconfigurations.
Moving Ue CellBf.MovingUeMuBfS It is recommended that the

MUBF Scheme cheme SPLIT_SDMA_SCHEME option be
selected to improve the throughput of
moving UEs, if any.
Adaptive Split CellMMAlgo.ASplitSdm Set this parameter to 10.

SDMA SRS aSrsLmtUePropThld
Limit UE Prop
Thld

eRAN

Name
Adaptive Split CellMMAlgo.ASplitSdm Set this parameter to 10.

SDMA TM9 aTm9UePropThld
UE Proportion
Thld
Split SDMA CellMMAlgo.SplitSdma -12

UE UeIdenSrsSinrThld
Identification
SRS SINR Thld
Enhanced CellAlgoSwitch.EnhMI To enable single-user split SDMA

MIMO Switch MOSwitch scheduling for closed-loop TM9 UEs
without participating in split SDMA pairing
for such UEs, select the
TM9HybridPrecodingSwitch option and
do not select the TM9SplitSdmaSwitch
option under the
CellAlgoSwitch.MuBfAlgoSwitch
parameter.
MUBF CellAlgoSwitch.MuBfAl If split SDMA scheduling is required for

Algorithm goSwitch closed-loop TM9 rank 1 and rank 2 UEs
Switch served by the SCC, and such UEs are
allowed to participate in split SDMA
pairing, select the TM9SplitSdmaSwitch
option.
Split SDMA CellMMAlgo.SplitSdma Set this parameter based on the network

Beam RSRP BeamRsrpIsltnThld plan.
Isolation l A larger value of this parameter leads to
Threshold a higher threshold of the RSRP isolation
of the target beams for two UEs to
participate in split SDMA and better UE
pairing performance but may lead to
fewer pairing layers in the cell.
l A smaller value of this parameter leads
to a lower threshold of the RSRP
isolation of the target beams for two UEs
to participate in split SDMA and poorer
UE pairing performance but may lead to
more pairing layers in the cell.

eRAN
l Beam split weighting values are available only when the beam weight file inside the
eNodeB software package is activated. If no beam split weighting value is available,
enabling multi-user split SDMA will lead to cell faults.
NOTE
The parameter settings in the following examples are used for reference only. Set the parameters based
on network requirements.
//Turning on the split SDMA switch
MOD CELLALGOSWITCH: LocalCellId=0, MuBfAlgoSwitch=SplitSDMASwitch-1;
//(Optional) Configuring the PDSCH split beam configuration index to the default
beam configuration template and the split SDMA adaptation period to 15 minutes,
and enabling split SDMA for moving UEs
MOD CELLBF: LocalCellId=0, PdschSplitBeamConfigIndex=CONFIG_DEFAULT,
SplitSdmaAdaptionPeriod=PERIOD_15MIN, MovingUeMuBfScheme=SPLIT_SDMA_SCHEME;
//(Optional) Configuring the threshold of the proportion of UEs with insufficient
SRSs, the threshold of the proportion of TM9 for triggering split SDMA, the SRS
SINR threshold for identifying UEs available for split SDMA, and split SDMA beam
RSRP isolation threshold based on the network plan
MOD CELLMMALGO: LocalCellId=0, ASplitSdmaSrsLmtUePropThld=10,
ASplitSdmaTm9UePropThld=10, SplitSdmaUeIdenSrsSinrThld=-12,
SplitSdmaBeamRsrpIsltnThld=5;
//(Optional) Enabling multi-user split SDMA for closed-loop TM9 UEs
MOD CELLALGOSWITCH: LocalCellId=0, EnhMIMOSwitch=TM9HybridPrecodingSwitch-1,
MuBfAlgoSwitch=TM9SplitSdmaSwitch-1;

//Turning off the split SDMA switch
MOD CELLALGOSWITCH: LocalCellId=0,MuBfAlgoSwitch=SplitSDMASwitch-0;


You can monitor the following counters to check whether multi-user split SDMA takes effect.
1526746985 L.ChMeas.MassiveMIMO.SplitS Average number of layers for split

dma.Avg.PairLayer SDMA in massive MIMO
scenarios

eRAN
You can perform signaling tracing on the U2020 to check whether multi-user split SDMA
takes effect. For details, see "user-level beam-domain monitoring items" in Monitoring
Through Signaling Tracing.
The following counters can be used to monitor resource usages in different transmission
modes.
1526739777 L.ChMeas.MUBF. Average number of PRBs to be

1stLayer.PairPRB.Tot paired for layer-1 UEs during MU
beamforming
1526739778~1 L.ChMeas.MUBF. Average number of PRBs for UEs

526739780 2ndLayer.PairPRB.Succ~L.ChM of MUBF layers 2 to 4 that can be
eas.MUBF. paired
4thLayer.PairPRB.Succ
1526745726~1 L.ChMeas.MUBF. Average number of PRBs for UEs

526745737 5thLayer.PairPRB.Succ~L.ChM of MUBF layers 5 to 16 that can
eas.MUBF. be paired
16thLayer.PairPRB.Succ
1526745707 L.ChMeas.DL.Succ.Pair.TTI Number of TTIs during which UEs

are successfully paired in the
downlink
1526745708 L.ChMeas.MassiveMIMO.MUB Average number of layers paired

F.Avg.PairLayer for MU beamforming in massive
MIMO scenarios
1526746985 L.ChMeas.MassiveMIMO.SplitS Average number of layers for split

dma.Avg.PairLayer SDMA in massive MIMO
scenarios
Monitoring Through Signaling Tracing

l Cell-level MU beamforming monitoring: to monitoring MU beamforming pairing in a
cell
a. On the U2020 client, choose Monitor > Signaling Trace > Signaling Trace
Management.
b. From the navigation tree on the left of the Signaling Trace Management tab page,
choose LTE > Cell Performance Monitoring > Multi-User BF (Cell)
Monitoring. The Multi-User BF (Cell) Monitoring dialog box is displayed.
c. In the displayed dialog box, enter the tracing task name in the Trace Name text
box, select the eNodeB to be monitored, and click Next.
d. Enter the local cell ID, and select Massive MIMO MUBF Pair in the Test Items
area, and click Finish to start the trace task.

eRAN
e. On the Signaling Trace Management tab page, double-click the trace task that you
have created to view the monitoring result. For the detailed description of the
monitoring result, press F1 to obtain the online help.
l User-level beam-domain monitoring items: to monitor the PDSCH target beam and
working beam information of a UE working in multi-user split SDMA
a. On the U2020 client, choose Monitor > Signaling Trace > Signaling Trace
Management.
b. In the navigation tree on the left of the Signaling Trace Management tab page,
choose Trace Type > LTE > User Performance Monitoring > Beam Space
(User) Monitoring. In the displayed dialog box, select PDSCH Beam Defect.
c. In the displayed dialog box, enter the tracing task name in the Trace Name text
box, select the eNodeB to be monitored, and click Next.
d. Enter the mobility management entity code (MMEC) and MME temporary mobile
subscriber identity (mTMSI) of the UE to be traced, and click Finish. The trace task
is started on the U2020.
e. In the Signaling Trace Management window, double-click the created trace task to
view the monitoring results of PDSCH Beam Flag, PDSCH Beam Identifier,
PDSCH Beam SRS RSRP. For the detailed description of the monitoring result,
press F1 to obtain the online help.

Fault description: The feature does not take effect after the eNodeB software is upgraded,
though the feature switch has been turned on.
Fault handling:
Step 1 Check whether the feature, hardware and license control meet the requirements described in
6.5.3 Requirements.
Step 2 Check whether parameters are properly set by referring to 6.5.4.1.1 Data Preparation.
Step 3 Run the DSP BFANTDB command and check whether the beam weight file is activated by
referring to 6.5.4.1.2 Using MML Commands.
----End
6.6 PDCCH SDMA

This section describes TDLEOFD-121613 PDCCH SDMA in Massive MIMO .
6.6.1 Principles
This feature increases the PDCCH capacity. After the beam weight file is loaded, the PDCCH
wide beam is split into multiple PDCCH narrow beams, as shown in Figure 6-10. The half-
power beamwidth (HPBW) of the narrow beams is similar to that of the wide beam. The
eNodeB determines whether the UE is an independent-scheduling UE or a joint-scheduling
UE based on beam associations and isolations of the UE. Each PDCCH narrow beam is
independently transmitted to an independent-scheduling UE, enabling PDCCH resources to
be shared by multiple UEs served by different beams and enhancing PDCCH capacity. The
beams in the working beam list of joint-scheduling UEs perform joint transmission in a way
of scheduling same as that used before the split.

eRAN
Figure 6-10 PDCCH SDMA
This feature is controlled by the MASSIVE_MIMO_PDCCH_SDMA_SW option under the

CellPdcchAlgo.SplitBeamPdcchSdmaSw parameter.
When this feature is enabled, the eNodeB determines the working beam list, independent-
scheduling UEs, and joint-scheduling UEs as follows:
1. Arranges the beams sent by a UE in descending order by RSRP.
2. Selects the beam with the largest RSRP value as the target PDCCH beam of the UE.
3. Determines the working PDCCH beam list based on the isolation.
a. Arranges the RRUs with the largest RSRP value into beam group A and the other
beams into beam group B, and then calculates the isolation between beam groups A
and B. The isolation equals the ratio of the total RSRP of beam group A to the total
RSRP of beam group B.
b. Compares the isolation with the isolation threshold. For details about the isolation
threshold, see Table 6-9. The eNodeB moves the beam with the second largest
RSRP from beam group B to beam group A and calculates the isolation again if the
isolation is less than a specified threshold. In this way, the eNodeB calculates the
isolation until it exceeds the isolation threshold. When the isolation exceeds the
isolation threshold, the beams contained in beam group A form the working beam
list of the UE.
Table 6-9 Isolation thresholds

CCE Aggregation Isolation Threshold
Level
1 or 2 Determined by the CellPdcchAlgo.SplitBeamPdcchSd-

maThd parameter
4 or 8 Determined by the CellPdcchAlgo.SplitBeamPdcchSd-

maThd and CellPdcchAlgo.SplitBeamPdcchSdmaThl-
dOfs parameters

eRAN
NOTE
l The eNodeB automatically identifies the CCE aggregation level of a UE, free from any
parameter control.
l The SINR is low for UEs with high CCE aggregation levels. For such UEs, adjust the
setting of the CellPdcchAlgo.SplitBeamPdcchSdmaThldOfs parameter to slightly
decrease the isolation threshold so that the UEs are more probably scheduled as
independent-scheduling UEs and more probably enter PDCCH SDMA.
4. Determines UE attributes based on the number of narrow PDCCH beams in the working
beam list of the UE.
– If the working beam list of the UE contains only one narrow PDCCH beam, the UE
is an independent-scheduling UE.
– If the working beam list of the UE contains multiple narrow PDCCH beams, the UE
is a joint-scheduling UE.
6.6.2.1 Benefits
This feature increases the PDCCH capacity and the average UE throughput in the uplink and
downlink.
l Average uplink UE throughput = (L.Thrp.bits.UL – L.Thrp.bits.UE.UL.SmallPkt)/

L.Thrp.Time.UE.UL.RmvSmallPkt
l Average downlink UE throughput = (L.Thrp.bits.DL – L.Thrp.bits.DL.LastTTI)/
This feature is recommended when all of the following conditions are met in massive MIMO
scenarios:
l There are big events.

l Uplink PDCCH resources are severely limited.
Namely, all of the following conditions are met:
– Percentage of uplink CCE allocation failures > 80%
– Uplink equivalent CCE usage > 80%
– Number of uplink activated UEs/Number of uplink scheduled UEs > 5
l Uplink resources are more limited than downlink resources.
Number of uplink activated UEs/Number of uplink scheduled UEs > Number of
downlink activated UEs/Number of downlink scheduled UEs
l UEs are evenly distributed on the horizontal plane.
The call history record (CHR) monitoring item
PERIOD_PRIVATE_BEAM_TRAFFIC can be used to verify whether UEs are evenly
distributed on the horizontal plane. This monitoring item measures the proportions of
downlink traffic on eight beams on the horizontal plane. UEs are evenly distributed on
the horizontal plane if the proportions of downlink traffic in the three directions of beams
2&3, beams 0&1&7, and beams 5&6 are all greater than 25%.
The gains brought by PDCCH SDMA are limited if UEs are not evenly distributed on
the horizontal plane (for example, most UEs are served by one split beam) and there are
only a small number of independent-scheduling UEs.

eRAN
6.6.2.2 Impacts
Network Impacts
l This feature increases the PDCCH capacity, allows more UEs to be scheduled, and
improves the average UE throughput in the uplink and downlink when all of the
following conditions are met. This feature may decrease the spectral efficiency, cell
throughput, and UE-perceived rate if any of the following conditions is not met:
– There are big events.
– Uplink PDCCH resources are severely limited.
– Uplink resources are more limited than downlink resources.
– UEs are evenly distributed on the horizontal plane.
l PDCCH beam split and coverage changes induced by this feature may lead to
fluctuations in the number of UEs, reduce CQIs, and affect TM3 UE performance.
Consequently, this feature has an impact on the PRB usage, pairing performance,
spectral efficiency, cell throughput, and UE-perceived rate.
Function Impacts
None
6.6.3 Requirements
6.6.3.1 Licenses
TDLEOFD-121 PDCCH SDMA in LT4SPSMSMI0 Per Cell

613 Massive MIMO 0
6.6.3.2 Software
Name

MIMO
Functions
PDCCH STRATEGYBASEDON Physical PDCCH SDMA in

aggregation CAPACITY option Channel massive MIMO requires
level adaptation under the Resource capacity-based PDCCH
CellPdcchAlgo.PDCCH Management aggregation level
AggLvlAdaptStrage adaptation.
parameter

eRAN

Name
Inter-frequency None Soft Split None

split Resource
Duplex (TDD)
6.6.3.3 Hardware
See 4.3.3 Hardware.
6.6.3.4 Others

If PDCCH SDMA is to be enabled in massive MIMO cells, the following parameters need to
be set.

PDCCH Split Beam CellPdcchAlgo.Spli Select the

SDMA Switch tBeamPdcchSdmaS MASSIVE_MIMO_PDCCH_SDMA_SW
w option.
PDCCH Split Beam CellPdcchAlgo.Spli Set this parameter to 24.

SDMA Threshold tBeamPdcchSdmaT
hd
Split Beam PDCCH CellPdcchAlgo.Spli Set this parameter to

SDMA Threshold tBeamPdcchSdmaT THRESHOLD_OFFSET_1.
Offset hldOfs
The Strategy Of CellPdcchAlgo.PD Set this parameter to

PDCCH CCHAggLvlAdaptSt STRATEGYBASEDONCAPACITY.
Aggregation Level rage
Adaptation

eRAN
PDCCH SDMA CellPdcchAlgo.Pdc l Set this parameter to

Weight Type chSdmaWeightType PREFERENTIAL_COV_GUARANT
EE if coverage is to be preferentially
guaranteed.
l Set this parameter to
PREFERENTIAL_ENHANCED_SD
MA if the gain is to be preferentially
guaranteed. The
CellPdcchAlgo.PdcchSdmaWeightType
parameter can be set to
PREFERENTIAL_ENHANCED_SD
MA only when the
BfAnt.CoverageScenario parameter is
set to SCENARIO_2 or
SCENARIO_6.
Coverage Scenario BfAnt.CoverageSce PDCCH SDMA requires that this parameter

nario be set to one of the following values:
l SCENARIO_2
l SCENARIO_3
l SCENARIO_4
l SCENARIO_6
l SCENARIO_7
l SCENARIO_8
l SCENARIO_10
l SCENARIO_11
l SCENARIO_12
l Beam split weighting values are available only when the beam weight file is activated. If
no beam split weighting value is available, enabling PDCCH SDMA will lead to cell
faults.
NOTE
The parameter settings in the following examples are used for reference only. Set the parameters based
on network requirements.

eRAN

//Changing the coverage scenario
MOD BFANT:DEVICENO=0, CoverageScenario=SCENARIO_2;
//Enabling PDCCH SDMA
MOD CELLPDCCHALGO: LocalCellId=0, PDCCHAggLvlAdaptStrage=STRATEGYBASEDONCAPACITY,
SplitBeamPdcchSdmaSw=MASSIVE_MIMO_PDCCH_SDMA_SW-1,
PdcchSdmaWeightType=PREFERENTIAL_ENHANCED_SDMA, SplitBeamPdcchSdmaThd=24,
SplitBeamPdcchSdmaThldOfs=THRESHOLD_OFFSET_1;

//Disabling PDCCH SDMA and setting the PDCCH split SDMA weight type to its
default value
MOD CELLPDCCHALGO: LocalCellId=0,
SplitBeamPdcchSdmaSw=MASSIVE_MIMO_PDCCH_SDMA_SW-0,
PdcchSdmaWeightType=PREFERENTIAL_COV_GUARANTEE;


On the U2020 client, start a DCI status monitoring task to monitor the CCE resource pairing
performance when this feature is enabled.
LTE > Cell Performance Monitoring > DCI Statistic Monitoring. On the displayed DCI
Statistic Monitoring dialog box, select PDCCH SDMA in Split Beam DCI STATISTIC.
Figure 6-11 Configuration GUI for DCI statistic monitoring

eRAN
Step 3 Set Local cell ID, Monitor Period (ms), and UE type, and click Finish. The monitoring task
is initiated.
Step 4 On the Signaling Trace Management tab page, double-click the trace task that you have
created to view the monitoring result. PDCCH SDMA in massive MIMO has taken effect if
the number of CCEs successfully paired within the monitoring period is not 0.
----End

1526730838 L.Traffic.SUNPT.UL.Avg Average number of scheduled UEs

per TTI in the uplink in a cell
1526728259 L.Thrp.bits.UL Total uplink traffic volume for

PDCP PDUs in a cell
1526729415 L.Thrp.bits.UE.UL.SmallPkt Uplink PDCP data volume

scheduled for small packets
1526729416 L.Thrp.Time.UE.UL.RmvSmall Uplink PDCP data transmission

Pkt duration except that for small
packets
1526730832 L.Traffic.SUNPT.DL.Avg Average number of scheduled UEs

per TTI in the downlink in a cell
1526728261 L.Thrp.bits.DL Total volume of downlink data

transmitted at the PDCP layer in a
cell
1526729005 L.Thrp.bits.DL.LastTTI Downlink PDCP-layer traffic

volume sent in the last TTI before
the buffer is empty
1526729015 L.Thrp.Time.DL.RmvLastTTI Data transmission duration except

the last TTI before the downlink
buffer is empty
l Average uplink UE throughput = (L.Thrp.bits.UL – L.Thrp.bits.UE.UL.SmallPkt)/

L.Thrp.Time.UE.UL.RmvSmallPkt

Fault description: No CCE resources are paired.
Fault handling:
Step 1 Check whether feature, hardware and license control meet the requirements described in 6.6.3
Requirements.

eRAN
Step 3 Check UE distributions. If the UEs are located near each other, the UEs may receive the same
beam, increasing the probability that no CCE resources are paired. In this situation, adjust the
UE locations or add UEs in dispersed locations and then monitor the pairing performance
again.
----End
Fault description: The feature does not take effect after the eNodeB software is upgraded,
though the feature switch has been turned on.
Fault handling:
Step 1 Check whether feature, hardware and license control meet the requirements described in 6.6.3
Requirements.
Step 3 Run the DSP BFANTDB command and check whether the beam weight file is activated by
referring to 6.6.4.1.2 Using MML Commands.
----End
6.7 TMA
6.7.1 Principles
6.7.1.1 Introduction to Transmission Modes

The transmission mode refers to the transmission solution of the PDSCH between eNodeBs
and UEs. The transmission mode information is delivered to UEs by using RRC connection
messages, and UEs determine a transmission solution of the PDSCH based on the
transmission mode information. Table 6-11 shows the transmission mode used in massive
MIMO scenarios.
Table 6-11 Transmission modes used in massive MIMO scenarios

Transmission Transmission Solution Whether to Use in Massive
Mode MIMO Scenarios
TM1 Single-antenna transmission No

(rarely used)
TM2 Open-loop transmit diversity Yes
TM3 Open-loop spatial multiplexing Yes

eRAN
Transmission Transmission Solution Whether to Use in Massive

Mode MIMO Scenarios
TM4 Closed-loop spatial multiplexing No

Massive MIMO is not compatible
with downlink 4x4 MIMO and the
CellBfMimoParaCfg.BfMimoAd
apWithTm4Switch parameter must
be set to OFF. Therefore, TM4 is
not used in massive MIMO
scenarios.
TM7 Single-stream beamforming Yes
TM8 Dual-stream beamforming When 3D beamforming and MU

beamforming are enabled:
antenna selection: TM8 is
recommended. For details, see
7.9 MU Beamforming Pairing
of Antenna Selection UEs in
Dual-Stream Beamforming.
l UEs incapable of transmit
antenna selection: TM8 is not
recommended.
NOTE
Network performance may be
affected when 3D beamforming
and MU beamforming are enabled
and UEs incapable of transmit
antenna selection work in TM8.
Therefore, it is recommended that
the
BFMIMOADAPWITHOUTTM
8 option be selected under the
CellBfMimoParaCfg.BfMimoAl
goOptSwitch parameter.
TM9 Closed-loop spatial multiplexing Yes

(PMI feedback-dependent TM9)
Open-loop spatial multiplexing Yes

(PMI feedback-independent TM9) UEs incapable of transmit antenna
selection do not support PMI
feedback-independent TM9 during
TMA.
6.7.1.2 TMA Principles

The initial transmission mode for UE access is specified by the
CellBfMimoParaCfg.InitialBfMimoType parameter. The value can be TM2 or TM3.
Transmission mode adaptation (TMA) enables the eNodeB to adaptively select a proper

eRAN
transmission mode for a UE based on the radio channel quality of the UE after it accesses the
network. In this way, the spectral efficiency is improved.
According to Table 6-11, TMA can be performed among TM2, TM3, TM7, TM8, and PMI
feedback-dependent TM9 in massive MIMO scenarios. Table 6-12 illustrates the TMA
principles.
Table 6-12 TMA principles
CellBfMi Cell.Crs UE Type SINR Available Transmission Mode

moParaCfg PortNum
.BfMimoA
daptiveSwi
tch
NO_ADAP N/A N/A N/A The transmission mode is not

TIVE adaptive and is specified by the
CellBfMimoParaCfg.FixedBfMim
oMode parameter.
This value is recommended only in
test scenarios.
TxD_BF_A N/A High- N/A TM2

DAPTIVE speed
UEs
Low- N/A l TM7

speed l TM8 (only suitable for antenna
UEs selection UEs compliant with
compliant 3GPP Release 9 or later)
with
3GPP
Release 8
or later
MIMO_BF CRS_PO High- Low TM2

_ADAPTIV RT_2 speed
E UEs High TM3 rank 2
Low- Low TM7 (as shown in Figure 6-12) or

speed TM8 (for antenna selection UEs
UEs compliant with 3GPP Release 9 or
compliant later, as shown in Figure 6-13)
with
3GPP High TM3 rank 2, as shown in Figure
Release 8 6-12
or 9
Low- Low TM7 (as shown in Figure 6-14) or

speed TM8 (for antenna selection UEs
UEs compliant with 3GPP Release 9 or
compliant later, as shown in Figure 6-15)
with
3GPP

eRAN
CellBfMi Cell.Crs UE Type SINR Available Transmission Mode

moParaCfg PortNum
.BfMimoA
daptiveSwi
tch
Release High TM3 rank 2 or PMI feedback-

10 or dependent TM9 rank 3 or 4, as
later shown in Figure 6-14
NOTE
PMI feedback-dependent TM9 is
available in massive MIMO scenarios
only when TM9 is enabled.
Figure 6-12 TMA for low-speed UEs compliant with 3GPP Release 8 or 9 and incapable of
transmit antenna selection

eRAN
Figure 6-13 TMA for low-speed UEs compliant with 3GPP Release 9 and capable of transmit
antenna selection
Figure 6-14 TMA for low-speed UEs compliant with 3GPP Release 10 and incapable of

eRAN
Figure 6-15 TMA for low-speed UEs compliant with 3GPP Release 10 and capable of
6.7.1.3 Optimized TMA
Transmission Mode Control for UE Access

When TMA is enabled, the proportion of TM2 UEs may be high due to the time required for
switching from TM2 to TM7. As a result, the number of downlink pairing layers is less than
expected. To solve this problem, the CellBfMimoParaCfg.UeAccessTMMode parameter is
introduced to control the initial transmission mode in massive MIMO scenarios.
Value of Initial Transmission Mode

CellBfMimoParaCfg.
UeAccessTMMode
TM7 TM7
This setting improves the proportion of beamforming,
downlink spectral efficiency, and average downlink cell
throughput. When the network is lightly loaded and the
proportion of small packets is high, the UE-perceived rate may
decrease.
AUTOMATIC The initial transmission mode is specified by the

CellBfMimoParaCfg.InitialBfMimoType parameter.
Switching to TM7 in Multi-Layer Pairing Scenarios

When the number of layers to be paired reaches the threshold specified by the
CellBf.MultiLayerThdSwitchToTM7 parameter, the eNodeB switches the UEs working in
TM2, TM3, or PMI feedback-dependent TM9 to TM7, achieving higher pairing gains and
increasing the cell throughput.

eRAN
l In multi-layer pairing scenarios, a small value of the

CellBf.MultiLayerThdSwitchToTM7 parameter increases the possibility that UEs
working in TM7 are paired for MU beamforming.
l In non-multi-layer pairing scenarios, UEs cannot be paired even after switching to TM7.
In this situation, the CellBf.MultiLayerThdSwitchToTM7 parameter must be set to 0 or
a larger value.
When the number of layers to be paired for a cell reaches the threshold specified by the
CellBf.MultiLayerThdSwitchToTM7 parameter and MU beamforming pairing of antenna
selection UEs in TM8 (see 7.9 MU Beamforming Pairing of Antenna Selection UEs in
Dual-Stream Beamforming) is enabled, the eNodeB switches the transmission mode of
antenna selection UEs from TM2, TM3, or PMI feedback-dependent TM9 to TM8. In this
way, the gain of pairing dual-stream beamforming UEs is received, increasing the cell
throughput.
l When multiple layers can be paired, a small value of the
CellBf.MultiLayerThdSwitchToTM7 parameter increases the possibility of MU
beamforming pairing of UEs incapable of transmit antenna selection in TM7 or UEs
capable of transmit antenna selection in TM8.
l In non-multi-layer pairing scenarios, UEs cannot be paired even after switching to TM7.
In this situation, the CellBf.MultiLayerThdSwitchToTM7 parameter must be set to 0 or
a larger value.
Heavy-Load TMA Boost

Significant negative gains in certain cells may be achieved when beamforming is used as a
fixed transmission mode in heavy-load scenarios. Heavy-load TMA boost is introduced to
prevent such a possibility.
This function takes effect for all newly accessed mobile broadband (MBB) and wireless
broadband (WBB) UEs and the already online WBB UEs. Figure 6-16 shows the
implementation process of this function.

eRAN
Figure 6-16 Implementation process of heavy-load TMA boost
After this function is enabled, the eNodeB periodically checks the service load of a cell. In
heavy-load scenarios, the eNodeB calculates the overall spectral efficiency of a cell separately
for cell-level TMA and the target beamforming mode. Then, the eNodeB automatically
selects the transmission mode that maximizes the spectral efficiency of the cell. This function
may cause the cell spectral efficiency to fluctuate due to cell-level TMA attempts.
Step Description
Enable heavy-load TMA boost. This function is controlled by the

HEAVYLOADTRANSMODEADAPTBOOSTSW
and HISTORICALSPECTRALEFFOPTSW options
under the
CellBfMimoParaCfg.BfMimoAlgoOptSwitch
parameter.

eRAN
Step Description
Determine whether the cell load A cell is heavily loaded if both of the following
is heavy. conditions are met:
l Average downlink PRB usage of the cell > Value of
the CellBfMimoParaCfg.HeavyLoadDlPrbUsa-
geThld parameter
l Average number of UEs in a cell > Value of the
CellBfMimoParaCfg.HeavyLoadAvgUeCountThl
d parameter
Measure the overall historical l The CellBfMimoParaCfg.HeavyLoadTransMo-

spectral efficiency of a cell in deEvalPrd parameter specifies the period for
heavy-load scenarios where cell- measuring the cell load and spectral efficiency when
level TMA and target this function takes effect.
beamforming mode are used. l The CellBfMimoParaCfg.HeavyLoadTargetTrans-
Mode parameter specifies the target beamforming
mode (TM7 or TM8) used by a cell when the cell is
heavily loaded.
When the HEAVYLOADTRANSMODEADAPTBOOSTSW option is selected under the

CellBfMimoParaCfg.BfMimoAlgoOptSwitch parameter, the
CellBfMimoParaCfg.HeavyLoadTargetTransMode parameter is set to TM7, and MU
beamforming pairing of antenna selection UEs in dual-stream beamforming is enabled, the
eNodeB switches the transmission mode from TM2, TM3, or PMI feedback-dependent TM9
to TM8. In this way, the dual-stream beamforming gain is obtained, increasing the cell
throughput. For details about MU beamforming pairing of antenna selection UEs in dual-
stream beamforming, see 7.9 MU Beamforming Pairing of Antenna Selection UEs in
Dual-Stream Beamforming.
This function is not compatible with switching to TM7 in multi-layer pairing scenarios. This
function is recommended only when beamforming performance is unstable (including
unstable performance of multi-layer pairing due to radio environment and high proportion of
UEs not suitable for beamforming). In other situations, switching to TM7 in multi-layer
pairing scenarios is recommended.
Handover-specific Beamforming Threshold Adjustment

If the source and target cells of an intra-frequency handover have the same PCI mod 3 value
and beamforming is enabled, it is recommended that the
CellBfMimoParaCfg.HoBFThdAdjSwitch parameter be set to ON to increase the
probability of UEs entering the beamforming mode and increase the downlink throughput.
TMA for 4R and 8R UEs

This function is controlled by the CellBfMimoParaCfg.Ue4ROr8RBfMimoAdaptOptSw
parameter. When the CellBfMimoParaCfg.Ue4ROr8RBfMimoAdaptOptSw parameter is set
to ON, the eNodeB optimizes the TMA mechanism for 4R and 8R UEs as follows:
l Optimizes the threshold for triggering switching between TM3 rank 2 and TM9 rank 4
for 4R UEs when 256QAM is enabled.

eRAN
This optimization requires the CellBfMimoParaCfg.Tm3ToTm9SwtgSEffOfs256qam

and CellBfMimoParaCfg.Tm9ToTm3SwtgSEffOfs256qam parameters to be set.
l Optimizes the threshold for triggering switching between TM3 rank 2 and dual-stream
beamforming (TM8) for 4R and 8R UEs.
This optimization requires the CellBfMimoParaCfg.AsUeDualBfToTM3Rank2Offset
and CellBfMimoParaCfg.AsUeTM3Rank2ToDualBfOffset parameters to be set. To
prevent the threshold of transmit antenna selection UE for triggering switching between
TM3 rank 2 and dual-stream beamforming from taking effect on fake antenna selection
UEs, it is recommended that the FakeAntSelIdentificationSwitch option be selected
under the CellAlgoSwitch.BfAlgoSwitch parameter to identify transmit antenna
selection UEs.
l For massive MIMO cells, if the FakeAntSelIdentificationSwitch option is selected
under the CellAlgoSwitch.BfAlgoSwitch parameter, the threshold for triggering
switching between TM3 and TM7 for 4R and 8R UEs is optimized.
NOTE
Dual-stream beamforming includes dual-stream beamforming (TM8) and PMI feedback-independent

TM9 rank 2. TM9 rank 2 refers to PMI feedback-dependent TM9 rank 3 to rank 8.
Optimized Switching to Beamforming in Heavy-Load Scenarios

This function is controlled by the CellBf.HeavyLoadSwitchToBfOpt parameter. When the
CellBf.HeavyLoadSwitchToBfOpt parameter is set to a value other than 255, optimized
switching to beamforming in heavy-load scenarios is enabled. The optimization principles are
as follows:
l Switching of online WBB UEs to TM7 when the cell is in the heavy-load beamforming
state
If the CellBf.MultiLayerThdSwitchToTM7 parameter is set to a value other than 0 and
the cell enters the heavy-load beamforming state, the eNodeB switches the transmission
mode of WBB UEs from TM2, TM3, or PMI feedback-dependent TM9 (excluding PMI
feedback-dependent TM9 rank 3 to rank 8 in non-hybrid precoding scenarios) to TM7. A
maximum of 10 online WBB UEs can be switched to TM7 per logical cell per second.
After the cell exits the heavy-load beamforming state, the eNodeB selects the
transmission mode for online WBB UEs based on the optimal single-UE link selection
principles.
l Optimized heavy-load TMA boost
When heavy-load TMA boost is enabled by selecting the
HEAVYLOADTRANSMODEADAPTBOOSTSW and
HISTORICALSPECTRALEFFOPTSW options under the
CellBfMimoParaCfg.BfMimoAlgoOptSwitch parameter, the eNodeB increases the
filter factor of the cell-level historical spectral efficiency for heavy-load massive MIMO
cells. This enables the cell-level historical spectral efficiency accurately adapt to the
changes in the number of UEs and load status. After multiple consecutive heavy-load
beamforming states are detected, heavy-load TMA boost is triggered only when the
number of downlink pairing layers is less than the value of the
CellBf.HeavyLoadSwitchToBfOpt parameter.
Number of downlink pairing layers = (L.ChMeas.MUBF.2ndLayer.PairPRB.Succ + ...
+ L.ChMeas.MUBF.16thLayer.PairPRB.Succ)/L.ChMeas.PRB.DL.Used.Avg + 1

eRAN
6.7.2.1 Benefits
The eNodeB adaptively selects a proper transmission mode for a UE based on the radio
channel quality of the UE, maximizing the spectral efficiency.
6.7.2.2 Impacts
Network Impacts
l TMA enabled but transmission mode control for UE access disabled: The proportion of
TM2 UEs may be high due to the time required for switching from TM2 to TM7. As a
result, the number of downlink paired layers is less than expected.
l TMA and transmission mode control for UE access both enabled: When the network is
lightly loaded and the proportion of small packets is high, the UE-perceived rate may
decrease.
l Heavy-load TMA boost: The cell spectral efficiency may fluctuate due to cell-level
TMA tries.
l Optimized TMA for 4R and 8R UEs increases the proportion of beamforming, downlink
UE-level spectral efficiency, and downlink UE-perceived data rate. The proportion of
PMI feedback-dependent TM9 may decrease.
l If WBB UEs have been online for a long time, switching of a WBB UE to TM7 when
the cell is in the heavy-load beamforming state under optimized switching to
beamforming in heavy-load scenarios increases the number of pairing layers, spectral
efficiency, and UE-perceived data rate in the downlink.
l In heavy-load scenarios, optimized heavy-load TMA boost under optimized switching to
beamforming in heavy-load scenarios enables the cell-level historical spectral efficiency
to more accurately adapt to changes in the number of UEs and load status. It reduces the
overhead of heavy-load TMA detections when the cell is in heavy-load beamforming
state.
Function Impacts
None
6.7.3 Requirements
6.7.3.1 Licenses
None

eRAN
6.7.3.2 Software
Name

MIMO
Functions
WBB UE CellWttxParaCfg.Wbb WBB Switching of online

identification OrMbbUserDefMode WBB UEs to TM7 when
the cell is in the heavy-
load beamforming state
under optimized
switching to
beamforming in heavy-
load scenarios depends
on WBB UE
identification.
Switching to CellBf.MultiLayerThdS 6.7.1.3 Switching of online

TM7 in multi- witchToTM7 Optimized WBB UEs to TM7 in the
layer pairing TMA heavy-load beamforming
scenarios state requires switching
to TM7 in multi-layer
pairing scenarios to be
enabled.
Heavy-load HEAVYLOADTRANS 6.7.1.3 Optimized heavy-load

TMA boost MODEADAPTBOOST Optimized TMA boost under
SW and TMA optimized switching to
HISTORICALSPECT beamforming in heavy-
RALEFFOPTSW load scenarios requires
options under the heavy-load TMA boost
CellBfMimoParaCfg.Bf to be enabled.
MimoAlgoOptSwitch
parameter

eRAN

Name
Heavy-load HEAVYLOADTRANS Heavy-Load Heavy-load TMA boost

TMA boost MODEADAPTBOOST TMA Boost is not compatible with
SW and switching to TM7 in
HISTORICALSPECT multi-layer pairing
RALEFFOPTSW scenarios. Preferentially
options under the enable switching to TM7
CellBfMimoParaCfg.Bf in multi-layer pairing
MimoAlgoOptSwitch scenarios. If switching to
parameter TM7 in multi-layer
pairing scenarios cannot
Switching to CellBf.MultiLayerThdS Switching to offer positive gains,
TM7 in multi- witchToTM7 TM7 in Multi- enable heavy-load TMA
layer pairing Layer Pairing boost.
scenarios Scenarios
6.7.3.3 Hardware
See 4.3.3 Hardware.

If TMA and related optimizations are to be enabled in massive MIMO scenarios, the
following parameters need to be set.
Initial BFMIMO CellBfMimoParaCf Set this parameter based on the network

Mode g.InitialBfMimoTyp plan.
e
BfMIMO adaptive CellBfMimoParaCf Set this parameter to

switch g.BfMimoAdaptiveS MIMO_BF_ADAPTIVE.
witch
UE Access CellBfMimoParaCf If transmission mode control for UE access

Transmission Mode g.UeAccessTMMod is required, set this parameter to TM7.
e

eRAN
Cell Highload Thd CellBf.MultiLayerT l In multi-layer pairing scenarios, a small

for Switch to BF hdSwitchToTM7 value of the
CellBf.MultiLayerThdSwitchToTM7
parameter increases the possibility that
UEs working in TM7 are paired for MU
beamforming.
l In non-multi-layer pairing scenarios,
UEs cannot be paired even after
switching to TM7. In this situation, the
CellBf.MultiLayerThdSwitchToTM7
parameter must be set to 0 or a larger
value.
BfMimo Algorithm CellBfMimoParaCf If heavy-load TMA boost is required, select

Optimization Switch g.BfMimoAlgoOptS the HEAVYLOADTRANSMODEA-
witch DAPTBOOSTSW and
HISTORICALSPECTRALEFFOPTSW
options.
Heavy Load Target CellBfMimoParaCf Set this parameter to its recommended

Trans Mode g.HeavyLoadTarget value.
TransMode
Heavy Load Trans CellBfMimoParaCf Set this parameter to its recommended

Mode Evaluation g.HeavyLoadTrans value.
Period ModeEvalPrd
Heavy Load CellBfMimoParaCf Set this parameter to its recommended

Downlink PRB g.HeavyLoadDlPrb value.
Usage Threshold UsageThld
Heavy Load CellBfMimoParaCf Set this parameter to its recommended

Average UE Count g.HeavyLoadAvgUe value.
Threshold CountThld
Handover BF CellBfMimoParaCf If handover-specific beamforming threshold

Threshold Adjust g.HoBFThdAdjSwit adjustment is required, set this parameter to
Switch ch ON.
Optimized switching CellBf.HeavyLoadS Set this parameter to its recommended

to beamforming in witchToBfOpt value.
heavy-load scenarios
4R or 8R UE BF CellBfMimoParaCf If there are 4R or 8R UEs on the network, it

MIMO Adaptation g.Ue4ROr8RBfMim is recommended that this parameter be set to
Opt Sw oAdaptOptSw ON.
AS UE Dual BF To CellBfMimoParaCf Set this parameter based on site conditions.

TM3 Rank2 Offset g.AsUeDualBfToT
M3Rank2Offset

eRAN
AS UE TM3 Rank2 CellBfMimoParaCf Set this parameter based on site conditions.

To Dual BF Offset g.AsUeTM3Rank2T
oDualBfOffset
256QAM TM3 to CellBfMimoParaCf Set this parameter to its recommended

TM9 Switching g.Tm3ToTm9SwtgS value.
Spectral Eff Offset EffOfs256qam
256QAM TM9 to CellBfMimoParaCf Set this parameter to its recommended

TM3 Switching g.Tm9ToTm3SwtgS value.
Spectral Eff Offset EffOfs256qam
BF algorithm switch CellAlgoSwitch.Bf If optimized TMA for 4R and 8R UEs is

AlgoSwitch enabled, it is recommended that the
FakeAntSelIdentificationSwitch option be
selected to prevent the threshold of transmit
antenna selection UE for triggering
switching between TM3 rank 2 and dual-
stream beamforming (TM8) from taking
effect on fake antenna selection UEs.

//Configuring the initial transmission mode for UE access and setting the
BfMimoAdaptiveSwitch parameter (The value MIMO_BF_ADAPTIVE is used as an example)
MOD CELLBFMIMOPARACFG: LocalCellId=0, InitialBfMimoType=TM2,
BfMimoAdaptiveSwitch=MIMO_BF_ADAPTIVE;
//(Optional) Enabling transmission mode control for UE access
MOD CELLBFMIMOPARACFG: LocalCellId=0, UeAccessTMMode=TM7;
//(Optional) Enabling switching to TM7 in multi-layer pairing scenarios
(MultiLayerThdSwitchToTM7 set to 20 is used as an example.)
//(Optional) Enabling heavy-load TMA boost (Heavy-load TMA boost is not
compatible with switching to TM7 in multi-layer pairing scenarios.)
MOD CELLBFMIMOPARACFG: LocalCellId=0,
BfMimoAlgoOptSwitch=HEAVYLOADTRANSMODEADAPTBOOSTSW-1&HISTORICALSPECTRALEFFOPTSW-1;
//(Optional) Enabling handover-specific beamforming threshold adjustment
MOD CELLBFMIMOPARACFG: LocalCellId=0, HoBfThdAdjSwitch=ON;
//(Optional) Enabling optimized TMA for 4R and 8R UEs
MOD CELLBFMIMOPARACFG: LocalCellId=0, Ue4ROr8RBfMimoAdaptOptSw=ON,
AsUeDualBfToTM3Rank2Offset=-20, AsUeTM3Rank2ToDualBfOffset=-14,
Tm3ToTm9SwtgSEffOfs256qam=60, Tm9ToTm3SwtgSEffOfs256qam=75;
//(Optional) Enabling optimized switching to beamforming in heavy-load scenarios
MOD CELLBF: LocalCellId=0, HeavyLoadSwitchToBfOpt=15;

//Disabling TMA
MOD CELLBFMIMOPARACFG: LocalCellId=0, BfMimoAdaptiveSwitch=NO_ADAPTIVE,
FixedBfMimoMode=TM2;
//(Optional) Disabling transmission mode control for UE access
MOD CELLBFMIMOPARACFG: LocalCellId=0, UeAccessTMMode=AUTOMATIC;
//(Optional) Disabling switching to TM7 in multi-layer pairing scenarios
//(Optional) Disabling heavy-load TMA boost and restoring the value of

eRAN
MultiLayerThdSwitchToTM7 (The value 20 is used as an example.)

BfMimoAlgoOptSwitch=HEAVYLOADTRANSMODEADAPTBOOSTSW-0&HISTORICALSPECTRALEFFOPTSW-0;
//(Optional) Disabling handover-specific beamforming threshold adjustment
MOD CELLBFMIMOPARACFG: LocalCellId=0, HoBfThdAdjSwitch=OFF;
//(Optional) Disabling TMA for 4R and 8R UEs
MOD CELLBFMIMOPARACFG: LocalCellId=0, Ue4ROr8RBfMimoAdaptOptSw=OFF;
//(Optional) Disabling optimized switching to beamforming in heavy-load scenarios
MOD CELLBF: LocalCellId=0, HeavyLoadSwitchToBfOpt=255;


Step 1 Run the LST CELLBFMIMOPARACFG command to check whether the value of
BfMIMO adaptive switch is NO_ADAPTIVE. If no, TMA has been enabled.
Step 2 Run the LST CELLBFMIMOPARACFG command to check whether the value of UE
Access Transmission Mode is TM7. If yes, transmission mode control for UE access has
been enabled.
Step 3 Run the LST CELLBF command to check whether the value of Cell Highload Thd for
Switch to BF is 0. If no, switching to TM7 in multi-layer pairing scenarios has been enabled.
Step 4 Run the LST CELLBFMIMOPARACFG command to check whether

HEAVYLOADTRANSMODEADAPTBOOSTSW:On and
HISTORICALSPECTRALEFFOPTSW:Off are displayed under the BfMimo Algorithm
Optimization Switch parameter. If yes, heavy-load TMA boost has been enabled.
Step 5 Run the LST CELLBFMIMOPARACFG command to check whether the value of
Handover BF Threshold Adjust Switch is On. If yes, handover-specific beamforming
threshold adjustment has been enabled.
Step 6 Run the LST CELLBF command. If the value of Heavy-Load Switch to BF Optimization
is not 255, optimized switching to beamforming in heavy-load scenarios has been enabled.
Step 7 Run the LST CELLBFMIMOPARACFG command. If the value of 4R or 8R UE BF

MIMO Adaptation Opt Sw is On, optimized TMA for 4R and 8R UEs has been enabled.
----End

For details, see 6.1.4.3 Network Monitoring.
The following table lists the counters related to the number of WBB UEs after optimized
switching to beamforming in heavy-load scenarios is enabled.
1526745885 L.Traffic.ActiveUser.DL.WBB.Avg Average

number of
WBB UEs
activated in
the downlink

eRAN
1526745955 L.Traffic.User.WBB.Avg Average

number of
WBB UEs in
a cell
After heavy-load TMA boost and optimized heavy-load TMA boost are enabled, the downlink
UE pairing rate and spectral efficiency improve in heavy-load scenarios. The following
counters used to observe the performance of the functions.
1526747711 L.HeavyLoad.TransModeAdapt.Dur.DL.Cell The counters

are related to
1526747712 L.HeavyLoad.TransModeTarget.Dur.DL.Cell heavy-load
1526747713 L.LightToHeavyLoad.Num.DL.Cell TMA boost.
1526747714 L.HeavyLoad.TmaToTmTarget.Num.DL.Cell
1526747715 L.HeavyLoad.TmTargetToTma.Num.DL.Cell
1526739777 to L.ChMeas.MUBF.1stLayer.PairPRB.Tot to The counters

1526739780 L.ChMeas.MUBF.4thLayer.PairPRB.Succ measure the
average
1526745726 to L.ChMeas.MUBF.5thLayer.PairPRB.Succ to number of
1526745737 L.ChMeas.MUBF.16thLayer.PairPRB.Succ PRBs
successfully
paired for
MU
beamforming
at each layer.
1526726740 L.ChMeas.PRB.DL.Used.Avg Number of

downlink
paired layers
1526737840 to L.ChMeas.PRB.TM2 to L.ChMeas.PRB.TM8 The counters

1526737846 measure the
proportion of
1526747667 L.ChMeas.PRB.TM9 used PRBs in
a downlink
transmission
mode.
1526728261 L.Thrp.bits.DL The counters

measure the
1526728763 L.ChMeas.PRB.DL.DrbUsed.Avg average
1526730558 L.Cell.DL.PDSCH.Tti.Num downlink
spectral
efficiency of
the cell.

eRAN
6.8 Enhanced Coordinated Scheduling Based Power

Control
This section describes TDLEOFD-150604 Enhanced Coordinated Scheduling Based Power
Control (Trial).
6.8.1 Principles
This feature enables power coordination between the serving massive MIMO cell and the
neighboring non-massive MIMO cells that cause strong interference to the serving cell. In this
way, this feature improves the downlink spectral efficiency of massive MIMO cells. Figure
6-17 shows the principles of enhanced coordinated scheduling-based power control.
Figure 6-17 Enhanced coordinated scheduling based power control

eRAN
Turning On the Feature Control Switch

This feature is controlled by the CellCspcPara.CelleCspcSwitch parameter. The
CellCspcPara.CelleCspcSwitch parameter can be set to ON only when the
CellCspcPara.eCspcPCAdjRange parameter is set based on the value of the
CellDlpcPdschPa.PaPcOff parameter.
Selecting Cells to Form a Cell Set for Interference Coordination

By collecting information on neighboring cells that meet event A3/A6 reporting conditions
within a certain period, the serving cell selects 10 neighboring cells with the highest
interference as the coordinating cell set for interference coordination.
In non-CA scenarios, neighboring cell information is determined only based on event A3. In
CA scenarios, neighboring cell information of the PCC is determined based on event A3, and
neighboring cell information of the SCC is determined based on event A6. The offset values
of both events A3 and A6 are specified by the CellCspcPara.eCspcA3Offset parameter.
Calculating the Power Adjustment Requirement for Each Neighboring Cell

The calculation is based on the SINR values of UEs in the local cell, downlink transmit power
of the local cell, and RSRP for each neighboring cell. The calculation also aims to maximize
the cell throughput of the entire network. The requirements for reducing the transmit power of
neighboring cells are directly proportionate to the interference intensity of neighboring cells.
Exchanging power adjustment requirements

The serving cell exchanges PRB usage and cell PA information with its neighboring cells with
strong interference to calculate the required transmit power adjustment value.
NOTE
In inter-eNodeB networking scenarios, the serving cell interacts with the neighboring cells causing
strong interference through the eX2 interface when the USU3910 is configured or through the ODI
interface when the USU3900 is configured.
Updating the downlink transmit power of a cell

When the neighboring cell causing strong interference meets the following conditions, the
neighboring cell adjusts the downlink transmit power according to the power adjustment
requirement sent by the serving cell.
l The neighboring cell is a non-massive MIMO cell.
l The cell is not set up on a micro RRU.
l The PRB usage is greater than or equal to 40%.
l The average number of downlink activated UEs in a cell is greater than or equal to the
value of the CellCspcPara.eCspcPCAdjUeNumTh parameter.
The CellCspcPara.eCspcPCAdjRange parameter is used to set the range for adjusting the
downlink transmit power of a cell. Its value must be less than the value of the
CellDlpcPdschPa.PaPcOff parameter. A maximum of two values can be selected for this
parameter:
l If only one value is selected, the eNodeB adjusts the downlink transmit power of the cell
between the value of the CellDlpcPdschPa.PaPcOff parameter and the value of this
parameter.

eRAN
l If two values are selected, the eNodeB adjusts the downlink transmit power of the cell
between the value of the CellDlpcPdschPa.PaPcOff parameter and the two values of
this parameter.
For example:
l If the CellDlpcPdschPa.PaPcOff parameter is set to DB_3_P_A and the options

DB_6_P_A and DB_4DOT77_P_A are selected under the
CellCspcPara.eCspcPCAdjRange parameter, the eNodeB sets the downlink transmit
power to -6 dB, -4.77 dB, or -3 dB.
l If the CellDlpcPdschPa.PaPcOff parameter is set to DB_3_P_A and the DB_6_P_A
option is selected under the CellCspcPara.eCspcPCAdjRange parameter, the eNodeB
sets the downlink transmit power to -6 dB or -3 dB.
Updating the UE Transmit Power

If the UE whose transmit power is to be updated does not use Quadrature Phase Shift Keying
(QPSK) or beamforming, the eNodeB obtains the size of the last scheduled RB, sorts the RBs
in descending order by size, and limits the number of UEs whose transmit power is
reconfigured to 2.
If the UE whose transmit power is to be updated uses QPSK or beamforming, the eNodeB
changes the transmit power of all UEs of this type. In this scenario, the transmit power change
is transmitted only to the physical layer and is not notified to the UE through RRC signaling.
NOTE
This step does not take effect for voice UEs, push to talk (PTT) UEs, enhanced Machine Type
Communication (eMTC) UEs, and Coordinated MultiPoint transmission/reception (CoMP) UEs.
6.8.2.1 Benefits
This function is recommended only when all of the following conditions are met:
l Networking: The serving cell is a massive MIMO cell and multiple non-massive MIMO
macro neighboring cells cause strong interference to the serving cell.
l Load requirements: The PRB usage of any cell is greater than 80%.
l Overlapping coverage rate: More than 40% of UEs in the massive MIMO cell are subject
to interference from two neighboring cells. More than 40% of UEs in non-massive
MIMO cells are subject to interference from another non-massive MIMO cell.
NOTE
If the UE-reported RSRP difference between a neighboring cell and the serving cell is less than 6
dB, the UE is an interfering UE.
l CQI value: The average CQI value of the massive MIMO cell is low due to interference
from neighboring cells.
When all of the preceding conditions are met, enabling this function improves the downlink
spectral efficiency of the massive MIMO cell and that of the entire network. The downlink
spectral efficiency of non-massive MIMO neighboring cells coordinating with the serving
cell, however, may decrease.

eRAN
6.8.2.2 Impacts
Network Impacts
l Inter-cell power coordination improves the downlink spectral efficiency of heavy-load
massive MIMO cells in densely populated urban areas.
l If the inter-cell inter-RRU distance is small and the overlapping coverage area between
cells is large, the inter-cell power coordination gain increases.
l If the distribution of downlink PRB usages between cells is imbalanced, the gain of
inter-cell power coordination increases.
l Coordinated scheduling based power control requires downlink RSRP measurements.
This feature is recommended for networks where most UEs move at speeds less than 10
km/h. If most UEs move at higher speeds, eNodeBs cannot track fast interference
changes.
l When the cell attribute changes from a macro cell to a micro cell due to the configuration
modification, the PA of the cell may fail to be updated. As a result, the cell performance
deteriorates.
Function Impacts
None
6.8.3 Requirements
6.8.3.1 Licenses
TDLEOFD-150604 Enhanced LT4SECSBPC00 Per Cell

Coordinated
Scheduling Based
Power Control
(Trial)
6.8.3.2 Software
Massive MIMO N/A 4 Basic Massive The serving cell

introduction MIMO Functions must be a massive
MIMO cell.

eRAN
Cloud BB None USU3910-based In inter-eNodeB

Multi-BBU networking
Interconnection scenarios, the
USU3900-based serving cell interacts
Multi-BBU with the neighboring
Interconnection cells causing strong
interference through
the eX2 interface
when the USU3910
is configured or
through the ODI
interface when the
USU3900 is
configured.

Interference l CellAlgoSwitch. Interference None

randomizing InterfRandSwitc Randomizing (TDD)
h set to
ECO_BASED
on the eNodeB
side
l McirAlgoSwitch
on the
eCoordinator
side
Adaptive ICIC N/A Adaptive ICIC None
CSPC CellCspcPara.Cell CSPC None

CspcSwitch
High speed mobility Cell.HighSpeedFla High Speed Mobility In high-speed

g mobility scenarios,
cell load changes so
rapidly that
downlink power
adjustment cannot
promptly follow the
load changes.

eRAN
Inter-eNodeB DL InterDlCompDcsS- DL CoMP (TDD) None

CoMP witch and
InterDlCompCbfS-
witch options under
the
CellAlgoSwitch.Dl
CompSwitch
parameter
Intra-frequency split N/A Soft Split Resource None

Duplex (TDD)
Inter-frequency split N/A Soft Split Resource None

Duplex (TDD)
Extended cell range Cell.CellRadius Extended Cell Enhanced

Range Coordinated
Scheduling Based
Power Control
requires that the
radius of each cell
involved should not
exceed 15 km. If the
radius exceeds 15
km, Enhanced
Coordinated
Scheduling Based
Power Control does
not take effect.
Inter-cell downlink InterCellDmimoJT D-MIMO (TDD) None

D-MIMO Switch option under
the
CellAlgoSwitch.D
MIMOAlgoSwitch
parameter
Dynamic power CellDynPowerShar Dynamic Power None

sharing between ing.DynamicPower Sharing Between
LTE carriers SharingSwitch LTE Carriers
6.8.3.3 Hardware
The serving cell is a massive MIMO cell. For details about hardware requirements, see 4.3.3
Hardware.
The neighboring cells are non-massive MIMO cells. The hardware requirements are as
follows:
l Site type: 3900 and 5900 series base stations
l Boards: BBPs other than the LBBPc or LBBPd

eRAN
l RF modules: no requirements
6.8.3.4 Others
PLMN information must be configured for the eNodeBs that serve the cells in the coverage
area of this feature. If the PLMN information is not configured, routes cannot be set up.
Cell eCSPC Switch CellCspcPara.CelleCspcSw Set this parameter to ON.

itch
eCSPC A3 Offset CellCspcPara.eCspcA3Offs Set this parameter as

et required.
PA for even power CellDlpcPdschPa.PaPcOff Set this parameter as

distribution required.
eCSPC Power Control CellCspcPara.eCspcPCAdj See 6.8.1 Principles.

Adjustment Range Range
eCSPC PC Adjustment UE CellCspcPara.eCspcPCAdj It is recommended that this

Number Threshold UeNumTh parameter be set to a non-
zero value.

NOTE
l The parameter settings in the following examples are used for reference only. Set the parameters
based on network requirements.
l After this feature is enabled, it takes about 5 minutes to set up a coordinating neighboring cell for the
first time.
MOD CELLCSPCPARA: LocalCellId=0, eCspcPCAdjUeNumTh=1, eCspcA3Offset=-12,
CelleCspcSwitch=ON, eCspcPCAdjRange=DB_6_P_A-1&DB_4DOT77_P_A-1;

MOD CELLCSPCPARA: LocalCellId=0, CelleCspcSwitch=OFF;

See 4.4.1.3 Using the CME.

eRAN

Step 1 Run the DSP CELLECSPCSTATUS command on the eNodeB. If the command output
contains information about eCSPC coordinating neighboring cells, this function has been
activated. Otherwise, this function has not been activated or has not taken effect.
Step 2 On the U2020, choose Monitor > Signaling Trace > Signaling Trace Management. In the
displayed Signaling Trace Management window, choose LTE > Cell Performance
Monitoring > CSPC (Cell) Monitoring. Double-click CSPC (Cell) Monitoring. If the
measured value of User Num of UE PDSCH PA Consistent with Cell PDSCH PA is not 0,
the feature has taken effect on some UEs. You can also view the cell-level PA. If the PA value
is not the baseline one, the feature has taken effect.
Step 3 On the U2020, choose Monitor > Signaling Trace > Signaling Trace Management. In the
displayed Signaling Trace Management window, choose LTE > Application Layer > Uu
Interface Trace to start an air interface signaling tracing task. Check whether a PA change
takes effect by viewing RRC signaling messages.
----End

1526741772 L.Traffic.PdschPA.Samp.I Number of samples with the

ndex0 downlink PDSCH PA equal
to index 0

to index 1

to index 2

to index 3

to index 4

to index 5

to index 6

to index 7

eRAN

Run the DSP CELLECSPCSTATUS command on the eNodeB to query information about
the coordinating neighboring cells. If any of the following situations occurs, the eX2 interface
is faulty:
l The value of the eCspc Data Link Status parameter is UNAVAILABLE.
l The value of the eCspc Coordinate Cell Link Delay Status parameter is Yes.
Rectify the fault by referring to eX2 Self-Management.

eRAN
Massive MIMO (TDD) Feature Parameter Description 7 Performance Optimization in Massive MIMO
7 Performance Optimization in Massive

MIMO
7.1 Massive MIMO Load Steering

The inter-frequency load steering function of TDLOFD-070215 Intra-LTE User Number Load
Balancing is recommended when the coverage area of a massive MIMO cell overlaps that of
an inter-frequency non-massive MIMO cell on the LTE TDD network.
Inter-frequency load steering in massive MIMO scenarios enables the eNodeB to transfer the
uplink synchronized UEs suitable for massive MIMO between inter-frequency non-massive
MIMO cells and massive MIMO cells, improving traffic volume and spectral efficiency of
massive MIMO cells. For details, see Intra-RAT Mobility Load Balancing.
Figure 7-1 Massive MIMO load steering
7.2 PDCCH Capacity Improvement

eRAN
7.2.1 Principles
Preferential Scheduling for UEs with Low Aggregation Levels
Figure 7-2 Background for introducing preferential scheduling of UEs with low aggregation
levels
When uplink-downlink subframe configuration 2 is used, subframes 2 and 7 cannot be used

for downlink data transmission, and subframes 3 and 8 are used to transmit more downlink
data. This leads to limited uplink and downlink DCIs and downlink CCEs. Therefore,
preferential scheduling of UEs with low aggregation levels has been introduced to resolve this
issue.
This function is controlled by the LOW_AGG_PREFERENTIAL_SCH_SW option under

the CellPdcchAlgo.PdcchOptimizationSwitch parameter. When this function is enabled, the
eNodeB sorts the MU beamforming UEs in ascending order of priority based on their initial
PDCCH CCE aggregation levels in subframe 3 or 8 in each TTI and selects the most suitable
UEs for pairing. This function increases the number of MU beamforming UEs scheduled on
the PDCCH per TTI in subframe 3 or 8 as well as the number of paired layers and average
downlink UE throughput.
Figure 7-3 Principle of preferential scheduling of UEs with low aggregation levels
This function takes effect only when all of the following conditions are met:
l Uplink-downlink subframe configuration 2 is used.
l A massive MIMO cell is set up.
l The MuBfSwitch option is selected under the CellAlgoSwitch.MuBfAlgoSwitch
parameter.

eRAN
l The CellPdcchAlgo.CceMaxInitialRatio parameter is set to 10_1.

l Both the equivalent CCE usage and the uplink equivalent CCE usage are greater than
60%.
l The downlink PRB usage is greater than 60%.
Enhanced Symbol Adaptation

This function is controlled by the ECFIADAPTIONON option under the
CellPdcchAlgo.PdcchSymNumSwitch parameter. It requires preferential scheduling of UEs
with low aggregation levels to be enabled. When this function is enabled, the eNodeB
optimizes the conditions for triggering symbol adaptation for UEs with low aggregation
levels. This increases the number of MU beamforming UEs scheduled on the PDCCH per TTI
as well as the number of paired layers and average downlink UE throughput.
7.2.2.1 Benefits
PDCCH resource allocation has been optimized in massive MIMO scenarios, preventing cell
capacity from being suppressed when PDCCH resources are insufficient. This function
improves the average cell throughput and average UE throughput in the downlink. This
function can achieve the largest gain if the ratio of aggregation level 8 is greater than or equal
to 10% and the ratio of aggregation level 1 is greater than or equal to 30%.
NOTE
l Average downlink cell throughput = L.Thrp.bits.DL/L.Thrp.Time.Cell.DL.HighPrecision

l Ratio of aggregation level 8 = L.ChMeas.PDCCH.AggLvl8Num/
(L.ChMeas.PDCCH.AggLvl1Num + L.ChMeas.PDCCH.AggLvl2Num +
L.ChMeas.PDCCH.AggLvl4Num + L.ChMeas.PDCCH.AggLvl8Num)
7.2.2.2 Impacts
Network Impacts
l If both PDCCH and PDSCH resources are limited, PDCCH capacity enhancement may
decrease the average downlink cell throughput and downlink spectral efficiency.
l Preferential scheduling of UEs with low aggregation levels may slightly decrease the
CEU perceived rate.
l Enhanced PDCCH symbol adaptation may decrease the average cell and UE throughput
in the downlink in moderate- or light-load scenarios.
NOTE
Downlink spectral efficiency = L.Thrp.bits.DL/(L.Cell.DL.PDSCH.Tti.Num x

L.ChMeas.PRB.DL.DrbUsed.Avg)

eRAN
Function Impacts
None
7.2.3 Requirements
7.2.3.1 Licenses
None
7.2.3.2 Software
Massive MIMO N/A 4 Basic Massive Both of the

introduction MIMO Functions subfunctions under
PDCCH capacity
improvement require
massive MIMO
introduction.
Subframe Cell.SubframeAssig Subframe Preferential

configuration nment Configuration scheduling of UEs
(TDD) with low
aggregation levels
requires uplink-
downlink subframe
configuration 2.
Maximum initial CellPdcchAlgo.Cce None Set this parameter to

CCE ratio MaxInitialRatio 10_1 for preferential
scheduling of UEs
with low
aggregation levels.
Downlink 8-layer MuBfSwitch option 6.2 MU Preferential

MU beamforming under the Beamforming scheduling of UEs
Downlink 16-layer CellAlgoSwitch.Mu with low
MU beamforming BfAlgoSwitch aggregation levels
parameter requires downlink 8-
layer MU
beamforming or
downlink 16-layer
MU beamforming.

eRAN
Downlink 4-layer MuBfSwitch option Beamforming (TDD) Preferential

MU beamforming under the scheduling of UEs
CellAlgoSwitch.Mu with low
BfAlgoSwitch aggregation levels
parameter requires downlink 4-
CellBf.HighOrderM layer MU
ubfMaxLayer beamforming.
Preferential LOW_AGG_PREF 7.2.1 Principles Enhanced PDCCH

scheduling of UEs ERENTIAL_SCH_ symbol adaptation
with low SW option under the requires preferential
aggregation levels CellPdcchAlgo.Pdc scheduling of UEs
chOptimizationS- with low
witch parameter aggregation levels.

None
7.2.3.3 Hardware
See 4.3.3 Hardware.

If PDCCH capacity enhancement is required on the basis of MU beamforming in a massive
MIMO cell, the following parameters need to be set.
PDCCH Optimization CellPdcchAlgo.PdcchOpti Select the

Switch mizationSwitch LOW_AGG_PREFEREN
TIAL_SCH_SW option
under this parameter when
preferential scheduling of
UEs with low aggregation
levels or enhanced symbol
adaptation is enabled.

eRAN
PDCCH Symbol Number CellPdcchAlgo.PdcchSym Select the

Adjust Switch NumSwitch ECFIADAPTIONON
option under this parameter
when enhanced symbol
adaptation is enabled.

//Enabling preferential scheduling of UEs with low aggregation levels
PdcchOptimizationSwitch=LOW_AGG_PREFERENTIAL_SCH_SW-1;
//Enabling enhanced symbol adaptation
MOD CELLPDCCHALGO: LocalCellId=0, PdcchSymNumSwitch=ECFIADAPTIONON;

//Deactivating preferential scheduling of UEs with low aggregation levels
PdcchOptimizationSwitch=LOW_AGG_PREFERENTIAL_SCH_SW-0;
//Deactivating enhanced symbol adaptation
MOD CELLPDCCHALGO: LOCALCELLID=0, PdcchSymNumSwitch=OFF;


Step 1 Run the LST CELLPDCCHALGO command to query the status of the
LOW_AGG_PREFERENTIAL_SCH_SW option under the PDCCH Optimization
Switch parameter. Preferentially scheduling of UEs with low aggregation levels is enabled if
LOW_AGG_PREFERENTIAL_SCH_SW:On is displayed.
Step 2 Run the LST CELLPDCCHALGO command to query the value of the PDCCH Symbol
Number Adjust Switch parameter. Enhanced symbol adaptation has been enabled if the
value is Enhanced CFI Adaption On.
----End


cell

the buffer is empty

eRAN

buffer is empty
1526728763 L.ChMeas.PRB.DL.DrbUsed.Av Average number of PRBs used by

g PDSCH DRBs
1526728997 L.Thrp.Time.Cell.DL.HighPreci Total duration of downlink data

sion transmission in a cell (with the
precision of 1 ms)
1526728668 L.ChMeas.PDCCH.AggLvl1Nu Number of times of PDCCH

m resource allocations with
aggregation level 1

aggregation level 2

aggregation level 4

aggregation level 8
1526730558 L.Cell.DL.PDSCH.Tti.Num Number of TTIs on the PDSCH
NOTE
l Average downlink cell throughput = L.Thrp.bits.DL/L.Thrp.Time.Cell.DL.HighPrecision

l Downlink spectral efficiency = L.Thrp.bits.DL/(L.Cell.DL.PDSCH.Tti.Num x
7.3 Uplink Overload Optimization

This section describes TDLEOFD-15060109 Massive MIMO Uplink Overload Optimization.
7.3.1 Principles
Uplink overload optimization is categorized into uplink retransmission scheduling
optimization and uplink power control optimization.

eRAN
Uplink Retransmission Scheduling Optimization

In uplink heavy-load scenarios, there are many uplink retransmission UEs. The retransmission
UEs preferentially use non-adaptive retransmission, and the RBs occupied by these UEs
truncate the uplink frequency band, leading to discrete uplink RB allocation. As a result, RBs
are truncated for UEs performing uplink large-packet transmissions. Figure 7-4 shows non-
adaptive retransmission.
Figure 7-4 Non-adaptive retransmission
To resolve this issue, uplink retransmission scheduling optimization is introduced. This

function is controlled by the MmUlHeavyLoadOptSwitch option under the
CellUlschAlgo.VmimoOptAlgoSwitch parameter. When this option is selected, the eNodeB
performs adaptive scheduling for uplink retransmissions in heavy-load scenarios. In this way,
the frequency-domain resource locations occupied by retransmission UEs can be adjusted,
reducing the number of RB truncations caused by retransmission-oriented scheduling and
improving the uplink spectral efficiency.
Uplink Power Control Optimization

In uplink heavy-load scenarios, the uplink power control SINR threshold for pairing CCUs is
determined only based on the DeModulation Reference Signal (DMRS) SINR measurement
value and pairing MCS index reduction is not considered. This may result in a significant
decrease in the MCS index after the pairing. As a result, the uplink power of paired UEs
cannot increase. Therefore, uplink power control optimization is introduced. This function is
controlled by the CellPcAlgo.MmCellCentSinrThldAdjValue parameter. If this parameter is
set to a value other than 0, this function is enabled. In heavy-load scenarios, the impact of
pairing MCS index reduction on the uplink power control SINR threshold is considered
during uplink power control. In this case, the uplink power of paired CCUs can be increased,
improving the uplink spectral efficiency.
7.3.2.1 Benefits
l Uplink retransmission scheduling optimization
This feature improves the uplink spectral efficiency in uplink heavy-load scenarios. This
function achieves the maximum gain when the uplink CCE allocation failure rate is less
than 10% and the uplink PRB usage is greater than 80%.
l Uplink power control optimization
This function improves the uplink spectral efficiency in uplink heavy-load scenarios.
This function achieves the maximum gain when the uplink PRB usage is greater than
60%.

eRAN
7.3.2.2 Impacts
Network Impacts
l Uplink retransmission scheduling optimization
– This function reduces the impact of RB truncations caused by retransmission
scheduling and improves the uplink PRB usage and uplink spectral efficiency.
– The CCE usage increases, the probability of CCE allocation failures increases, the
number of PDCCH symbols increases, and the proportion of PDCCH DTXs slightly
increases.
NOTE
Proportion of PDCCH DTXs = (L.ChMeas.PDCCH.DL.DTXNum.AggLvl1 +

L.ChMeas.PDCCH.DL.DTXNum.AggLvl2 +
L.ChMeas.PDCCH.DL.DTXNum.AggLvl8)/(L.ChMeas.PDCCH.AggLvl1Num +
L.ChMeas.PDCCH.AggLvl2Num + L.ChMeas.PDCCH.AggLvl4Num +
L.ChMeas.PDCCH.AggLvl8Num)
l Uplink power control optimization
– This function improves the uplink spectral efficiency.
– The growth in the uplink power of UEs near the cell center may increase uplink
interference to neighboring cells.
Function Impacts
None
7.3.3 Requirements
7.3.3.1 Licenses
Uplink overload optimization is controlled by the license of massive MIMO introduction.

Introduction

eRAN
7.3.3.2 Software
Massive MIMO N/A 4 Basic Massive Both uplink

introduction MIMO Functions retransmission
optimization and
uplink power control
optimization require
massive MIMO
introduction to be
purchased.

None
7.3.3.3 Hardware
For details, see 4.3.3 Hardware.

After a massive MIMO cell is set up, the following parameters need to be configured to
activate uplink overload optimization.

Vmimo Optimization CellUlschAlgo.VmimoOptA If uplink retransmission

Algorithm Switch lgoSwitch scheduling optimization is
MmUlHeavyLoadOptS-
witch option.
Massive MIMO Cell Center CellPcAlgo.MmCellCentSi Set this parameter when

SINR Thld Adj Value nrThldAdjValue uplink power control
optimization is required.
If the uplink load exceeds
60%, the value 20 is
recommended.

eRAN

//Enabling uplink retransmission scheduling optimization
MOD CELLULSCHALGO: LocalCellId=0, VmimoOptAlgoSwitch=MmUlHeavyLoadOptSwitch-1;
//Enabling uplink power control optimization
MOD CELLPCALGO: LocalCellId=0, MmCellCentSinrThldAdjValue=20;

//Disabling uplink retransmission scheduling optimization
MOD CellUlschAlgo: LocalCellId=0, VmimoOptAlgoSwitch=MmUlHeavyLoadOptSwitch-0;
//Disabling uplink power control optimization
MOD CELLPCALGO: LocalCellId=0, MmCellCentSinrThldAdjValue=0;


Run the LST CELLULSCHALGO command to query the status of the
MmUlHeavyLoadOptSwitch option under the Vmimo Optimization Algorithm Switch
parameter. If MmUlHeavyLoadOptSwitch:On is displayed, uplink retransmission
scheduling optimization has been enabled.
Uplink Power Control Optimization

Run the LST CELLPCALGO command to query the value of the Massive MIMO Cell
Center SINR Thld Adj Value(0.1dB) parameter. If the value is not 0, uplink power control

1526728664 L.ChMeas.PDCCH.DL.DT Number of times of DTX

XNum.AggLvl1 for PDCCH resource
allocation with aggregation
level 1 in a cell

level 2 in a cell

level 4 in a cell

eRAN

level 8 in a cell
1526728668 L.ChMeas.PDCCH.AggLv Number of times of PDCCH

l1Num resource allocations with
aggregation level 1

aggregation level 2

aggregation level 4

aggregation level 8
Proportion of PDCCH DTXs = (L.ChMeas.PDCCH.DL.DTXNum.AggLvl1 +

L.ChMeas.PDCCH.DL.DTXNum.AggLvl2 + L.ChMeas.PDCCH.DL.DTXNum.AggLvl4
+ L.ChMeas.PDCCH.DL.DTXNum.AggLvl8)/(L.ChMeas.PDCCH.AggLvl1Num +
Enhanced Uplink Power Control

N/A
7.4 SRS NI Joint Suppression

This section describes TDLEOFD-131614 SRS NI Joint Suppression.
7.4.1 Principles
In a single massive MIMO cell, the target value of SRS power control can be increased to
increase the SRS SINR, improving MU beamforming performance. When multiple massive
MIMO cells are configured for contiguous coverage and cell overlapping is severe, increasing
the target value of SRS power control may increase interference between neighboring cells.
As a result, the SRS SINR may decrease and MU beamforming performance may be affected.
To solve the preceding problem, TDLEOFD-131614 SRS NI Joint Suppression is introduced.
This feature covers three functions: SRS resource allocation optimization for interference
avoidance, SRS power control optimization, and SRS interference cancellation (IC).
SRS Resource Allocation Optimization for Interference Avoidance

The SRS resource allocation mechanism has been optimized to reduce inter-cell interference
and improve the SRS SINR. This function is recommended when multiple massive MIMO

eRAN
cells are deployed on the same eNodeB and coverage overlap is severe in big-event scenarios.
This function is controlled by the SRSCfg.SrsInterfAvoidOptSwitch parameter and requires
massive MIMO introduction to be enabled.
Value of the Meaning Description

SRSCfg.SrsInterfAvoidO
ptSwitch Parameter
OFF SRS resource allocation None

optimization for interference
avoidance is disabled.
CLOCKWISE_COMB1 Comb 1 SRS resources are The massive MIMO cell is

preferentially allocated to divided into the left and
UEs in the clockwise right parts so that the SRS
direction to the boundary transmission priority of the
beam, and comb 0 SRS time-frequency position
resources are preferentially (also known as comb) is
allocated to UEs in the staggered between cells.
counterclockwise direction This function mitigates
to the boundary beam, as inter-cell interference and
shown in Figure 7-5. improves the SRS SINR
when being used with the
SRS time-domain
measurement function.
Figure 7-5 Interference avoidance principles

eRAN
NOTE
The ANTICLOCKWISE_COMB1 value is used for performance guarantee only in certain special
networking scenarios. For example, the coverage directions of two inter-eNodeB cells are the opposite
of each other. It is not recommended that the SRSCfg.SrsInterfAvoidOptSwitch parameter be set to
ANTICLOCKWISE_COMB1. Consider the networking conditions if you want to use the value.
Otherwise, the setting may lead to the identical comb preferentially allocated for SRS transmission of
the UEs that interfere with each other in the overlapping coverage areas, increasing interference.
SRS Power Control Optimization

This function enables the eNodeB to adaptively adjust the target SRS SINR value for power
control.
l A large target SRS SINR value for power control is recommended if there is only one
massive MIMO cell.
l An appropriate target SRS SINR value for power control is required to minimize inter-
cell interference when massive MIMO cells are deployed for contiguous coverage.
This function is recommended only when massive MIMO cells are involved to provide
contiguous coverage.
This function is enabled when the SrsPcSwitch option is selected under the
CellAlgoSwitch.UlPcAlgoSwitch parameter and the CellPcAlgo.SrsPcStrategy parameter is
set to SRSPC_SINR_ADAPTIVE. Each massive MIMO cell periodically calculates the
average SRS NP of the cell and determines whether to send SRS NP indicator to cells in the
interference neighboring cell list based on the following principles.
If... Then...
The average SRS noise power (NP) value is Sends the SRS-NP-HIGH IE to neighboring
greater than the upper threshold of –112 cells in the interference neighboring cell list.
dBm, and there are more than 100 UEs in
the cells
The average SRS NP value is less than the Sends SRS-NP-LOW signals to neighboring
lower threshold of –115 dBm cells in the interference neighboring cell list.
The average SRS NP value ranges from the Sends SRS-NP-HOLD signals to
upper threshold to the lower threshold neighboring cells in the interference
neighboring cell list.
After receiving the SRS-NP-Indicator message, the massive MIMO or non-massive MIMO
cell determines whether to adjust the UE-level target SRS SINR value for power control
based on the following principles.
If... Then...
The SRS-NP-HIGH signal sent by the Decreases the UE-level target SRS SINR
neighboring cell is received value for power control.
The SRS-NP-LOW signal sent by the Increases the UE-level target SRS SINR
neighboring cell is received value for power control.

eRAN
If... Then...
The SRS-NP-HOLD signal sent by the Does not adjust the UE-level target SRS
neighboring cell is received SINR value for power control.
NOTE
l The UE-level target SRS SINR value for power control is an internal system parameter and does not
need to be manually configured. Its initial value is controlled by the CellPcAlgo.SrsPcSinrTarget
parameter.
l The SRS NP value refers to the interference noise intensity measured on the SRS symbol, which is
obtained through SRS measurement.
SRS IC
As shown in Figure 7-6, SRS IC reduces or eliminates the SRS interference of neighboring
cells by means of interference cancellation, improving the SRS SINR.
This function is recommended only when massive MIMO cells are involved to provide
contiguous coverage. It is recommended that SRS SDNR be also enabled to further improve
performance.
This function is controlled by the MASSIVE_MIMO_SRS_IC_SW option under the

CellUlIcAlgo.SrsIcSwitch parameter.
Figure 7-6 Example of SRS IC

eRAN
7.4.2.1 Benefits
l SRS resource allocation optimization for interference avoidance: Improves MU
beamforming performance when multiple massive MIMO cells are deployed on a single
eNodeB.
l SRS power control optimization: Improves MU beamforming performance by adaptively
adjusting the target SRS SINR value for power control.
l SRS IC: Reduces or eliminates SRS interference of neighboring cells and improves MU
beamforming performance.
7.4.2.2 Impacts
Network Impacts
l MU beamforming performance improves.
l SRS resource allocation optimization for interference avoidance may prolong the SRS
period of certain UEs when UEs are unevenly distributed in the cell. A prolonged SRS
period affects the beamforming performance of moving UEs and may decrease the
downlink cell throughput.
l SRS power control optimization is designed to increase the average SRS SINR in
contiguous coverage areas. If the uplink SRS SINR of a single light-load cell is high, this
function may decrease its SRS SINR in a contiguous coverage area. However, the
average SRS SINR improves for the coverage area in which SRS power control is
enabled.
l SRS power control optimization increases the number of RRC connection
reconfiguration messages, leading to an increased service drop rate.
l After SRS IC is enabled:
– Uplink performance improves, which may increase the number of uplink Transfer
Control Protocol (TCP) packets. As a result, the uplink spectral efficiency may
decrease.
– Uplink pilot timeslot (UpPTS) interference decreases, improving the SRS SINR
distributions and affecting the number of downlink pairing layers.
Function Impacts
None
7.4.3 Requirements
7.4.3.1 Licenses
TDLEOFD-131614 SRS NI Joint LT4SSRSNJS00 Per Cell

Suppression

eRAN
7.4.3.2 Software
Massive MIMO N/A 4 Basic Massive SRS resource

introduction MIMO Functions allocation
optimization for
interference
avoidance and SRS
IC require massive
MIMO introduction.
Cloud BB None Cloud BB Overview SRS resource

USU3900-based allocation
Multi-BBU optimization for
Interconnection interference
avoidance and SRS
USU3910-based IC require that inter-
Multi-BBU eNodeB routes be
Interconnection
reachablea.
SRS measurement l NCellSrsMeasP None SRS power control

ara.SrsAutoNCe optimization and
llMeasSwitch SRS IC require SRS
l NCellSrsTimeM measurement.
easSwitch option NOTE
under the In non-massive
MIMO scenarios,
NCellSrsMeasP
SRS power control
ara.NCellMeasS optimization does not
witch parameter require the setting of
the
NCellSrsTimeMeas
Switch option under
the
NCellSrsMeasPara.
NCellMeasSwitch
parameter.
SRS time-domain SrsTimeMeasSwitc 7.5 SRS Time- SRS IC requires

measurement h option under the Domain SRS time-domain
CellAlgoSwitch.Srs Measurement and measurement.
AlgoSwitch SDNR
parameter

eRAN
SRS power control SrsPcSwitch option Power Control The

policy under the CellPcAlgo.SrsPcSt
CellAlgoSwitch.Ul rategy parameter
PcAlgoSwitch can be used to
parameter control the SRS
power control policy
only when the
SrsPcSwitch option
is selected under the
CellAlgoSwitch.Ul
PcAlgoSwitch
parameter.
a: The Cloud BB networking supports the following two modes:

l Coordination over relaxed backhaul: In this mode, no USU needs to be deployed. X2 or
eX2 interfaces are used between eNodeBs.
l Coordination over ideal backhaul: LTE TDD supports only the centralized networking
mode. The USU3900 or USU3910 must be deployed. If the USU3900 is deployed, ODI
interfaces are used between eNodeBs. If the USU3910 is deployed, eX2 interfaces are
used between eNodeBs.

Group hopping PUSCHCfg.Group None SRS IC is not

HoppingEnabled compatible with
group hopping.
Sequence hopping
must be disabled for
both the local cell
and its neighboring
cells.
Sequence hopping PUSCHCfg.SeqHo None SRS IC is not

ppingEnabled compatible with
sequence hopping.
Sequence hopping
must be disabled for
both the local cell
and its neighboring
cells.
7.4.3.3 Hardware
See 4.3.3 Hardware. There are no hardware requirements, except that the UBBPem does not
support SRS IC.

eRAN
SRS Interference Avoid SRSCfg.SrsInterfAvoidOpt Set this parameter to

Optimization Switch Switch CLOCKWISE_COMB1
when SRS resource
allocation optimization for
interference avoidance is
enabled.
Srs Power Control Strategy CellPcAlgo.SrsPcStrategy Set this parameter to

SRSPC_SINR_ADAPTIV
E when SRS power control
optimization is enabled.
SRS Auto Neighbour Cell NCellSrsMeasPara.SrsAut Set this parameter to ON

Measurement Switch oNCellMeasSwitch when SRS power control
Neighbouring Cell NCellSrsMeasPara.NCell Select the

Measurement Switch MeasSwitch NCellSrsTimeMeasSwitch
option under this parameter
when SRS power control
Uplink power control CellAlgoSwitch.UlPcAlgoS Select the SrsPcSwitch

algorithm switch witch option under this parameter
when SRS power control
optimization is required.
SRS IC Switch CellUlIcAlgo.SrsIcSwitch When SRS IC is enabled,

select the
MASSIVE_MIMO_SRS_I
C_SW option.
SoundingRS algorithm CellAlgoSwitch.SrsAlgoSw If SRS IC is enabled, select

switch itch the SrsTimeMeasSwitch
option.
Massive MIMO Algorithm CellMMAlgo.MMAlgoOpt When SRS IC is enabled,

Optimization Switch Switch select the
SRS_SDNR_SWITCH
option to enable SRS SDNR
to further improve the
performance.

eRAN
Group hopping enabled PUSCHCfg.GroupHopping Set this parameter to

Enabled BOOLEAN_FALSE for
both the local cell and its
neighboring cells.
Sequence hopping enabled PUSCHCfg.SeqHoppingEn Set this parameter to

abled BOOLEAN_FALSE for
both the local cell and its
neighboring cells.

//Enabling SRS resource allocation optimization for interference avoidance
MOD SRSCFG: LocalCellId=0, SrsInterfAvoidOptSwitch=CLOCKWISE_COMB1;
//(Non-massive MIMO scenarios) enabling SRS power control optimization

MOD NCELLSRSMEASPARA: LocalCellId=1, SrsAutoNCellMeasSwitch=ON;
//(Massive MIMO scenarios) enabling SRS power control optimization
MOD CELLALGOSWITCH: LocalCellId=0, UlPcAlgoSwitch=SrsPcSwitch-1;
MOD NCELLSRSMEASPARA: LocalCellId=0, SrsAutoNCellMeasSwitch=ON,
NCellMeasSwitch=NCellDmrsMeasSwitch-0&NCellSrsTimeMeasSwitch-1;
MOD CELLPCALGO: LocalCellId=0, SrsPcStrategy=SRSPC_SINR_ADAPTIVE;
//Enabling SRS IC
//Configuration of the local cell
MOD PUSCHCFG: LocalCellId=0, GroupHoppingEnabled=BOOLEAN_FALSE,
SeqHoppingEnabled=BOOLEAN_FALSE;
MOD CELLALGOSWITCH: LocalCellId=0, SrsAlgoSwitch=SrsTimeMeasSwitch-1;
MOD CELLULICALGO: LocalCellId=0, SrsIcSwitch=MASSIVE_MIMO_SRS_IC_SW-1;
MOD CELLMMALGO: LocalCellId=0, MMAlgoOptSwitch=SRS_SDNR_SWITCH-1;
//Configurations of the neighboring cell
MOD PUSCHCFG: LocalCellId=1, GroupHoppingEnabled=BOOLEAN_FALSE,
SeqHoppingEnabled=BOOLEAN_FALSE;

//Deactivating SRS resource allocation optimization for interference avoidance
MOD SRSCFG: LocalCellId=0, SrsInterfAvoidOptSwitch=OFF;
//Deactivating SRS power control optimization by restoring the SrsPcStrategy
parameter to the value used before this function is enabled (The following uses
SRSPC_SINR_BASED as an example.)
MOD CELLPCALGO: LocalCellId=0, SrsPcStrategy=SRSPC_SINR_BASED;
//Deactivating SRS IC
MOD CELLULICALGO: LocalCellId=0, SrsIcSwitch=MASSIVE_MIMO_SRS_IC_SW-0;


eRAN

Step 1 Run the LST SRSCFG command to query the value of the SRS Interference Avoid
Optimization Switch parameter. SRS resource allocation optimization for interference
avoidance has been enabled if the value is CLOCKWISE_COMB1.
Step 2 Run the LST CELLPCALGO command to query the value of the Srs Power Control
Strategy parameter. If the value is SRSPC_SINR_ADAPTIVE, SRS power control
Step 3 Run the LST CELLULICALGO command. If MASSIVE_MIMO_SRS_IC_SW:On is
displayed under the SRS IC Switch parameter, SRS IC has been enabled.
----End


cell

g PDSCH DRBs
1526728769 L.UpPTS.Interference.Avg Average UpPTS interference value

SRS resource allocation optimization for interference avoidance, SRS power control
optimization, or SRS IC may not increase the downlink spectral efficiency when the measured
value of the L.UpPTS.Interference.Avg counter is less than –125 dBm.
7.5 SRS Time-Domain Measurement and SDNR
7.5.1 Principles
SRS Time-Domain Measurement
This function enables SRS measurement in the time domain. Beam weight values are
calculated based on SRS measurement results. In massive MIMO scenarios, SRS time-
domain measurement is recommended to improve SRS measurement accuracy and SRS
SINR, enhancing the performance of SU beamforming and MU beamforming.
This function is controlled by the SrsTimeMeasSwitch option under the
CellAlgoSwitch.SrsAlgoSwitch parameter. When this option is selected, SRS time-domain
measurement is enabled. When this option is deselected, SRS time-domain measurement is
disabled. In this case, frequency-domain measurement is used.

eRAN
SRS SDNR
This function uses massive antennas to identify SRS spatial-domain characteristics and takes
SRS interference of UEs in neighboring cells into account during channel estimation. In this
way, this function improves the channel estimation accuracy, the average downlink UE
throughput, and average number of MU beamforming pairing layers. It is recommended that
this function be enabled in massive MIMO scenarios. In addition, it is recommended that SRS
time-domain measurement be used with SRS SDNR to achieve optimal performance.
This function is controlled by the SRS_SDNR_SWITCH option under the

CellMMAlgo.MMAlgoOptSwitch parameter. The SRS SDNR function is enabled when this
option is selected. Assume that cell 0 is a massive MIMO cell and that cell 1 is also a massive
MIMO cell or is a non-massive MIMO cell, as shown in Figure 7-7. After the SRS SDNR
function is enabled in cell 0, cell 0 uses the antenna of the local cell to identify the
interference strength in each direction of UE 0. During channel estimation, the interference
from neighboring cells is mitigated, improving the channel estimation accuracy and
beamforming weighting accuracy.
Figure 7-7 Principles of SRS SDNR
7.5.2.1 Benefits
l SRS time-domain measurement
This function improves the SRS measurement accuracy and SRS SINR, enhancing the
performance of SU beamforming and MU beamforming.
l SRS SDNR
This function improves the channel estimation accuracy, the average downlink UE
throughput, and average number of MU beamforming pairing layers. The gain of this
function decreases if the target cell is opposite the interfering cell. However, the overall
gain is not negative.
NOTE

l Average number of MU beamforming pairing layers =
L.ChMeas.MassiveMIMO.MUBF.Avg.PairLayer

eRAN
7.5.2.2 Impacts
Network Impacts
l SRS time-domain measurement
This function improves the SRS measurement accuracy and SRS SINR, enhancing the
performance of SU beamforming and MU beamforming.
l SRS SDNR
– This function improves the channel estimation accuracy, the average downlink UE
throughput, and average number of MU beamforming pairing layers. The gain of
this function decreases if the target cell is opposite the interfering cell. However, the
overall gain is not negative.
– SRS SDNR has impact on the following counters:
n L.UL.SINR.SRS.Index0
Function Impacts
None
7.5.3 Requirements
7.5.3.1 Licenses
None
7.5.3.2 Software
Massive MIMO N/A 4 Basic Massive Both SRS time-

introduction MIMO Functions domain
measurement and
SRS SDNR require
massive MIMO
introduction.
SRS resource SRSCfg.SrsCfgInd Physical Channel Both SRS time-

management Resource domain
Management measurement and
SRS SDNR require
SRS resource
management.

eRAN

None
7.5.3.3 Hardware
See 4.3.3 Hardware.

If SRS time-domain measurement and SRS SDNR are required in massive MIMO cells, the
following parameters must be set.
SoundingRS algorithm CellAlgoSwitch.SrsAlgoSw Select the

switch itch SrsTimeMeasSwitch option
when SRS time-domain
measurement is required.
Massive MIMO Algorithm CellMMAlgo.MMAlgoOpt Select the

Optimization Switch Switch SRS_SDNR_SWITCH
option when SRS SDNR is
required.

//Enabling SRS time-domain measurement
//Enabling SRS SDNR

//Disabling SRS time-domain measurement
//Disabling SRS SDNR


eRAN

Run the LST CELLALGOSWITCH command to query the status of the
SrsTimeMeasSwitch option under the SoundingRS algorithm switch parameter. If
SrsTimeMeasSwitch:On is displayed, SRS time-domain measurement has been enabled.
SRS SDNR
Run the LST CELLMMALGO command to query the status of the SRS_SDNR_SWITCH
option under the MMAlgoOptSwitch parameter. If SRS_SDNR_SWITCH:On is displayed,
SRS SDNR is enabled.

N/A
SRS SDNR

cell

the buffer is empty

buffer is empty
1526745708 L.ChMeas.MassiveMIMO.MUB Average number of layers paired

F.Avg.PairLayer for MU beamforming in massive
MIMO scenarios

range 0

range 1

range 2

range 3

range 4

eRAN
NOTE

l Average number of MU beamforming pairing layers =
L.ChMeas.MassiveMIMO.MUBF.Avg.PairLayer
7.6 Beamforming Weight Optimization

This section describes TDLEOFD-13160107 BF Weight Optimization.
7.6.1 Principles
The weight filtering function has been introduced. WTTx UEs generally remain stationary
and channel quality changes are typically caused by external noises. Weight filtering can resist
noise and improve channel quality. This function takes effect only in massive MIMO cells and
is recommended in WTTx or WTTx+MBB hybrid scenarios.
With this function, the eNodeB identifies WTTx UEs based on SPIDs or QCIs, or using
device-pipe identification and performs weight filtering on such UEs when the
CellBf.BfWeightOptDegreeFactor parameter is set to a non-zero value and the radio channel
quality is less than the value of the CellBf.BfWeightOptChnQltyThldOfs parameter plus the
channel quality threshold. The channel quality threshold is fixed to 0 dB in the current
version.
7.6.2.1 Benefits
This function improves the downlink spectral efficiency of CEUs with low SINRs in WTTx
or WTTx+MBB scenarios where massive MIMO cells are configured.
7.6.2.2 Impacts
Network Impacts
In WTTx scenarios or WTTx+MBB hybrid scenarios, this feature:
l Increases the downlink spectral efficiency and MCS indexes and may reduce the number
of RBs paired for MU beamforming at each layer for UEs with low SINRs. The gain is
inversely proportionate to the SINR. The gain is not significant for UEs with high SINRs
and even is negative in mobile scenarios.
l Slightly improves the downlink spectral efficiency of the entire network if most UEs are
allocated with short SRS periods and are not located near the cell center.

eRAN
Function Impacts
Name
Multi-user split SplitSDMASwitch 6.5 Multi-User After beamforming

SDMA option under the Split SDMA weight optimization is
CellAlgoSwitch.MuBfAl enabled, UEs with low
goSwitch parameter SRS SINRs will not enter
multi-user split SDMA.
UEs with low SRS
SINRs already working
in multi-user split SDMA
will exit the transmission
mode.
7.6.3 Requirements
7.6.3.1 Licenses
Beamforming weight optimization uses the license of Massive MIMO introduction.

Introduction
7.6.3.2 Software
Name

MIMO
Functions
Single-stream CellAlgoSwitch.BfAlgo Beamforming None

beamforming Switch (TDD)
Device-pipe SpecUeIdentifySwitch Specified User Beamforming weight

identification option under the Coordinated optimization requires
UeCooperationPara.Spe Scheduling either of the functions to
cUserCooperationSwitch be enabled.
parameter

eRAN

Name
WBB UE SpidCfg.SpecifiedUserF WBB

identification lag or
CellQciPara.ServiceFla
g

None
7.6.3.3 Hardware
See 4.3.3 Hardware.

If beamforming weight optimization is required in a massive MIMO cell, the following
parameters need to be set.

BF Weight Optimization CellBf.BfWeightOptDegree This parameter must not be

Degree Factor Factor set to 0 and the
recommended value is 200
when beamforming weight
optimization is enabled. Set
this parameter based on the
time-variant channel
characteristics of the current
network.
BF Weight Opt Chn Quality CellBf.BfWeightOptChnQl- The value 0 is

Thld Offset tyThldOfs recommended.

MOD CELLBF: LocalCellId=0, BfWeightOptDegreeFactor=200,
BfWeightOptChnQltyThldOfs=0;

eRAN

MOD CELLBF: LocalCellId=0, BfWeightOptDegreeFactor=0;


Run the LST CELLBF command to query the values of the BF Weight Optimization
Degree Factor and BF Weight Opt Chn Quality Thld Offset parameters. Beamforming
weight optimization has been enabled if they are the same as the planned ones.

1526727444 to 1526727475 L.ChMeas.PUSCH.MCS.0 Number of times MCS

to index n (n = 0 to 31) is
L.ChMeas.PUSCH.MCS. selected for scheduling on
31 the PDSCH
1526739777 L.ChMeas.MUBF. Average number of PRBs to

1stLayer.PairPRB.Tot be paired for layer-1 UEs
during MU beamforming
1526739778 to 1526745737 L.ChMeas.MUBF. Average number of PRBs

2ndLayer.PairPRB.Succ to successfully paired for UEs
L.ChMeas.MUBF. at layers 2 to 16 during MU
16thLayer.PairPRB.Succ beamforming
1526730558 L.Cell.DL.PDSCH.Tti.Nu Number of TTIs on the

m PDSCH
1526728261 L.Thrp.bits.DL Total volume of downlink

data transmitted at the
PDCP layer in a cell
1526728763 L.ChMeas.PRB.DL.DrbUs Average number of PRBs

ed.Avg used by PDSCH DRBs
1526745879 L.Thrp.bits.DL.WBB Total traffic volume of

downlink PDCP SDUs sent
for WBB UEs in a cell
1526745954 L.ChMeas.PRB.DL.PDSC Average number of PRBs

H.WBBUsed.Avg used for PDSCH
transmission for WBB UEs
in the downlink
1526746696 L.Thrp.bits.DL.UECooper Total traffic volume of

ation downlink PDCP PDUs
transmitted by device-pipe
synergy UEs in a cell

eRAN
1526746697 L.ChMeas.PRB.DL.DrbUs Average number of

ed.Avg.UECooperation downlink PRBs used by
DRBs on the PDSCH for
device-pipe synergy UEs

7.7 IRC
This section describes TDLEOFD-150613 Advanced Massive MIMO IRC.
7.7.1 Principles
On the basis of uplink 2x64 MU-MIMO, IRC improves physical-layer reception performance
as follows:
l Uses high-level IRC to better mitigate interference from neighboring cells.
l Optimizes the interference estimation mechanism in multi-user pairing scenarios,
enhances the antenna equalization robustness, and improves demodulation performance
and post-pairing throughput.
This feature is controlled by the PUSCH_RECEIVE_ENH_SWITCH option under the

CellMMAlgo.MMAlgoOptSwitch parameter.
7.7.2.1 Benefits
Advanced massive MIMO IRC achieves higher average uplink cell throughput and uplink
spectral efficiency than 64T64R multiple-antenna reception or IRC in heavy-load scenarios.
The gains are significant when the uplink PRB load is heavy and the number of uplink paired
layers, interference from neighboring cells, and the number of interference sources increase.
The gains can be maximized when the uplink PUSCH PRB usage of a cell is greater than
60%, the average number of uplink pairing layers is greater than 3, and the measured value of
the L.UL.Interference.Avg counter is greater than -108 dBm.
If there are many uplink small-packet services, it is recommended that the

CellUlschAlgo.EnhancedVmimoSwitch parameter be set to ON to increase the average
number of MU-MIMO pairing layers and the uplink average cell throughput.
If the equivalent uplink CCE usage relative to Control Format Indicator (CFI) adaptation is
greater than 90%, uplink CCE resources are limited. As a result, the number of uplink paired
UEs is limited, and the gains of advanced massive MIMO IRC are affected. Therefore, it is
recommended that the CellPdcchAlgo.CceMaxInitialRatio parameter be set to 10_1 when
advanced massive MIMO IRC is enabled in uplink heavy-load scenarios.

eRAN
NOTE
l Uplink spectral efficiency = (L.Traffic.UL.SCH.QPSK.TB.bits + L.Traffic.UL.SCH.

16QAM.TB.bits + L.Traffic.UL.SCH.64QAM.TB.bits)/(Total number of uplink TTIs x
L.ChMeas.PRB.PUSCH.Avg)
l Uplink PUSCH PRB usage of the cell = L.ChMeas.PRB.PUSCH.Avg/L.ChMeas.PRB.UL.Avail
l Average number of uplink pairing layers = (L.ChMeas.VMIMO.PairPRB2Layer.Succ +
L.ChMeas.VMIMO.PairPRB3Layer.Succ + L.ChMeas.VMIMO.PairPRB4Layer.Succ +
L.ChMeas.VMIMO.PairPRB5Layer.Succ + L.ChMeas.VMIMO.PairPRB6Layer.Succ +
L.ChMeas.VMIMO.PairPRB7Layer.Succ + L.ChMeas.VMIMO.PairPRB8Layer.Succ)/
L.ChMeas.VMIMO.PairPRB2Layer.Succ + 1
l Equivalent uplink CCE usage relative to CFI adaptation = 100 x
L.ChMeas.CCE.ULUsed.Equivalent/L.ChMeas.CCE.ULAvailPower.Equivalent
7.7.2.2 Impacts
Network Impacts
l Advanced massive MIMO IRC may increase the interference noise strength due to the
changes in the interference noise measurement mechanism, but demodulation
performance is not affected.
l After advanced massive MIMO IRC takes effect, uplink performance improves. When
uplink scheduling is complete and no service is available in the downlink for a period of
time, UEs may enter the RRC idle mode more quickly. As a result, the number of paging
messages increases, resulting in negative gains in the downlink.
Function Impacts
None
7.7.3 Requirements
7.7.3.1 Licenses
TDLEOFD-150613 Advanced Massive LT4SMMULRE00 Per Cell

MIMO IRC
7.7.3.2 Software
Uplink 2x64 MU-MIMO UlVmimoSwitch option 5.2 MU-MIMO

under the
CellAlgoSwitch.UlSchSwit
ch parameter

eRAN

None
7.7.3.3 Hardware
This feature requires the UBBPf1. For details about other hardware requirements, see 4.3.3
Hardware.

If IRC is required in a massive MIMO cell on the basis of MU-MIMO, the following
parameters need to be set.

Massive MIMO Algorithm CellMMAlgo.MMAlgoOpt Select the

Optimization Switch Switch PUSCH_RECEIVE_ENH
_SWITCH option.
CCE Max Initial Ratio CellPdcchAlgo.CceMaxInit Set this parameter to 10_1.

ialRatio
Enhanced VMIMO Switch CellUlschAlgo.EnhancedV It is recommended that this

mimoSwitch parameter be set to ON
when there are many uplink
small-packet services. This
increases the average
number of MU-MIMO
pairing layers and the
average uplink cell
throughput.

MOD CELLPDCCHALGO: LocalCellId=0, CceMaxInitialRatio=10_1;
//(Optional) Enabling enhanced MU-MIMO if there are many small-packet services in
the uplink
MOD CELLULSCHALGO: LocalCellId=0, EnhancedVmimoSwitch=ON;


eRAN


Run the LST CELLMMALGO command to query the setting of the Massive MIMO
Algorithm Optimization Switch parameter. Advanced massive MIMO IRC has been
enabled if PUSCH_RECEIVE_ENH_SWITCH:On is displayed in the command output.

1526728298 L.UL.Interference.Avg Average interference and

noise detected on each
uplink PRB
1526727369 L.Traffic.UL.SCH.QPSK. Number of bits of QPSK-

TB.bits encoded TBs transmitted
over the uplink SCH
1526727370 L.Traffic.UL.SCH. Number of bits of 16QAM-

16QAM.TB.bits encoded TBs transmitted
over the uplink SCH
1526727371 L.Traffic.UL.SCH. Number of bits of 64QAM-

64QAM.TB.bits encoded TBs transmitted
over the uplink SCH
1526728764 L.ChMeas.PRB.PUSCH.A Average number of used

vg PUSCH PRBs
1526728434 L.ChMeas.PRB.UL.Avail Number of available uplink

PRBs
1526739782 L.ChMeas.VMIMO.PairP Number of RBs that are

RB2Layer.Succ successfully paired for MU-
MIMO layer 2 UEs in a cell





eRAN


1526729295 L.ChMeas.CCE.ULUsed.E Number of PDCCH CCEs

quivalent used for carrying uplink
DCI, with the CCE power
equivalent to the reference
power
1526743711 L.ChMeas.CCE.ULAvailP Number of PDCCH CCEs

ower.Equivalent with the available uplink
CCE power equivalent to
the reference power
l Uplink spectral efficiency = (L.Traffic.UL.SCH.QPSK.TB.bits + L.Traffic.UL.SCH.

16QAM.TB.bits + L.Traffic.UL.SCH.64QAM.TB.bits)/(Total number of uplink TTIs
x L.ChMeas.PRB.PUSCH.Avg)
l Uplink PUSCH PRB usage of the cell = L.ChMeas.PRB.PUSCH.Avg/
L.ChMeas.PRB.UL.Avail
l Average number of uplink pairing layers = (L.ChMeas.VMIMO.PairPRB2Layer.Succ
+ L.ChMeas.VMIMO.PairPRB3Layer.Succ +
L.ChMeas.VMIMO.PairPRB4Layer.Succ +
L.ChMeas.VMIMO.PairPRB8Layer.Succ)/
L.ChMeas.VMIMO.PairPRB2Layer.Succ + 1
l Equivalent uplink CCE usage relative to CFI adaptation = 100 x
L.ChMeas.CCE.ULUsed.Equivalent/L.ChMeas.CCE.ULAvailPower.Equivalent
7.8 Scheduling Optimization
7.8.1 Principles
Scheduling optimization involves the following functions: selective HARQ scheduling in
subframe 3 or 8, downlink RB allocation optimization, MCS index selection optimization for
downlink paired UEs with small-amount data transmission, and cell-level outer-loop
adjustment optimization in beamforming.
Selective HARQ Scheduling in Subframe 3 or 8

In heavy-load scenarios, available CCE resources are limited in the downlink, curbing the
number of UEs scheduled in downlink subframe 3 or 8. As a result, not all the downlink

eRAN
PRBs of the subframe are used or the number of paired layers is low. To solve this issue,
selective HARQ scheduling in subframe 3 or 8 is introduced. This function is controlled by
the SF_3_8_HARQ_SELECTIVE_SCH_SW option under the
CellPdcchAlgo.PdcchOptimizationSwitch parameter. When this option is selected, the
eNodeB selects the UEs requiring a small number of CCEs and many RBs, for downlink
HARQ retransmission scheduling in subframe 3 or 8 if all of the following conditions are
met:
l A massive MIMO cell is set up.
l Uplink-downlink subframe configuration 2 is used.
l The CellPdcchAlgo.PDCCHAggLvlAdaptStrage parameter is set to
STRATEGYBASEDONCAPACITY.
l The downlink PRB usage is greater than 60%.
l The downlink equivalent CCE usage is less than 60%, the control format indicator (CFI)
value of subframe 3 or 8 is 3, and 12 or fewer downlink CCEs are available.
It is recommended that this function be used with preferential scheduling for UEs with low
aggregation levels (for initial transmission optimization) to increase the number of PRBs
scheduled in subframe 3 or 8, increasing the average cell throughput and average UE
throughput in the downlink.
Downlink RB Allocation Optimization

SRS frequency hopping cannot cover the entire bandwidth. There is no specific beamforming
weight for the first or last resource block group (RBG) and only the beamforming weighting
value of the nearby RBG is available. As a result, the beamforming weight is inaccurate in the
first or last RBG. The downlink RB allocation optimization function is introduced to improve
the accuracy of beamforming weights for the first or last RBG. This function takes effect only
in massive MIMO cells and is controlled by the DL_RB_ASSIGN_OPT_SWITCH option
under the CellMMAlgo.MMAlgoOptSwitch parameter. When this option is selected, the
eNodeB adjusts the allocation sequence of RBG resources and allocates the first and last
RBGs in the end. In addition, the eNodeB optimizes the CQI adjustment mechanism for UEs
allocated with a small number of RBs in the first or last RBG, reducing the impact of
inaccurate beamforming weights.
MCS Index Selection Optimization for Downlink Paired UEs with Small-
Amount Data Transmission
If the amount of downlink data to be initially transmitted is small for paired UEs, the transport
block size (TBS) selected for the initial transmission may be greater than the amount of data
to be transmitted. To resolve this issue, MCS index selection optimization for downlink paired
UEs with small-amount data transmission is introduced. This function is controlled by the
MM_DL_SCH_AND_MCS_OPT_SWITCH option under the
CellMMAlgo.MMAlgoOptSwitch parameter. When this option is selected, the eNodeB
selects a small MCS index while maintaining the number of allocated RBs. This reduces
transmissions of invalid data and the number of retransmissions and increases the average
downlink throughput of paired UEs.
Cell-level Outer-Loop Adjustment Optimization in Beamforming

Without this function, the initial CQI outer-loop value is fixed and the CQI value is difficult to
converge in burst service scenarios. This affects the reliability of traffic channels and the cell
spectral efficiency. To solve this problem, cell-level outer-loop adjustment optimization in

eRAN
beamforming is introduced. This function optimizes the mechanism for adjusting the initial
CQI outer-loop value. It is controlled by the MM_DL_SCH_AND_MCS_OPT_SWITCH
option under the CellMMAlgo.MMAlgoOptSwitch parameter. After the option is selected:
1. The eNodeB determines UE locations based on the 5-bit full-band CQI reported by UEs.
If the reported 5-bit full-band CQI value is less than or equal to 9, the UE is located at
the cell edge. If the CQI value is greater than 9 but is less than or equal to 15, the UE is
located between the cell center and cell edge. In other situations, the UE is near the cell
center. The eNodeB measures the cell-level outer-loop CQI adjustment value for various
locations in the cell based on each codeword.
NOTE
The reported 5-bit full-band CQI value is calculated based on the 4-bit CQI value reported by the
UE. The conversion formula is as follows: 5-bit full-band CQI value = 2 x 4-bit CQI value – 4
2. When a new UE accesses the network, the eNodeB determines the cell-level outer-loop
CQI adjustment value based on the UE type and uses it as the initial outer-loop CQI
value of the UE.
7.8.2.1 Benefits
l Selective HARQ scheduling in subframe 3 or 8 prevents limited cell capacity caused by
insufficient PDCCH resources in massive MIMO cells, increasing the average downlink
UE and cell throughput.
l Downlink RB allocation optimization increases the average downlink throughput and
downlink spectral efficiency in common scenarios. In light- or medium-load scenarios,
the average downlink UE throughput and downlink spectral efficiency may decrease, and
the PDCCH-related counter values, such as the proportion of DTXs, may slightly
deteriorate, and the service drop rate may slightly increase.
l MCS index selection optimization for downlink paired UEs with small-amount data
transmission reduces the number of retransmissions, shortens the scheduling delay of
small-traffic services, and improves the average downlink throughput of paired UEs and
downlink spectral efficiency.
l Cell-level outer-loop adjustment optimization in beamforming facilitates CQI
convergence in burst service scenarios, improving service channel reliability and cell
spectral efficiency.
NOTE
l The gains of downlink RB allocation optimization depend on the proportion of UEs allocated with a
small number of RBs and proportion of the first and last RBGs scheduled.
l Downlink cell throughput = L.Thrp.bits.DL/L.Traffic.Sch.DL.Num
l Proportion of PDCCH DTXs = (L.ChMeas.PDCCH.DL.DTXNum.AggLvl1 +
L.ChMeas.PDCCH.DL.DTXNum.AggLvl2 + L.ChMeas.PDCCH.DL.DTXNum.AggLvl4 +

eRAN
7.8.2.2 Impacts
Network Impacts
l Selective HARQ scheduling in subframe 3 or 8
– This function prevents the limited cell capacity caused by insufficient PDCCH
resources and improves the cell throughput and average UE throughput in the
downlink.
– The average downlink cell throughput may decrease.
NOTE
Average downlink cell throughput = L.Thrp.bits.DL/L.Thrp.Time.Cell.DL.HighPrecision

– The downlink spectral efficiency may slightly decrease because an increasing
number of downlink PRBs are scheduled in subframe 3 or 8.
l Downlink RB allocation optimization
– In heavy-load scenarios, the average downlink UE throughput and downlink
spectral efficiency improve. In light- or medium-load scenarios, the average
downlink UE throughput and downlink spectral efficiency may decrease, and the
PDCCH-related counter values, such as the proportion of DTXs, may slightly
deteriorate, and the service drop rate may slightly increase.
– The downlink initial block error rate (IBLER) and residual block error rate
(RBLER) slightly increase.
l MCS index selection optimization for downlink paired UEs with small-amount data
transmission
– The downlink MCS index and IBLER of paired UEs decrease slightly.
– The number of downlink retransmission UEs decreases and the average number of
scheduled UEs per TTI in the downlink may slightly decrease.
l Cell-level outer-loop adjustment optimization in beamforming
– If there are burst services and traffic channels are heavily loaded, this function
improves the cell spectral efficiency. However, if there are only a few cell-level
outer-loop samples, the downlink BLER may increase. As a result, the cell
throughput deteriorates and the user-perceived rate may be affected.
– If the proportion of MU beamforming UEs is high, the accumulative number of
cell-level outer-loop samples may be inaccurate. As a result, the downlink BLER
increases, the cell throughput deteriorates, and the UE-perceived rate may be
affected.
Function Impacts
None
7.8.3 Requirements
7.8.3.1 Licenses
None

eRAN
7.8.3.2 Software
Massive MIMO N/A 4 Basic Massive The four functions

introduction MIMO Functions of scheduling
optimization take
effect in massive
MIMO cells.
PDCCH aggregation STRATEGYBASE Physical Channel Selective HARQ

level adaptation DONCAPACITY Resource scheduling in
option under the Management subframe 3 or 8
CellPdcchAlgo.PD requires capacity-
CCHAggLvlAdaptSt based PDCCH
rage parameter aggregation level
adaptation.
Uplink-downlink Cell.SubframeAssig Subframe Selective HARQ

subframe nment Configuration scheduling in
configuration 1&2 (TDD) subframe 3 or 8
requires uplink-
downlink subframe
configuration 2.
Adaptive setting of CellCqiAdjAlgo.Ce Channel State Cell-level outer-loop

the initial cell-level llCqiAdjSchCntThl Management adjustment
CQI adjustment d optimization in
value beamforming
requires that
adaptive setting of
the initial cell-level
CQI adjustment
value be enabled.
That is, the
CellCqiAdjAlgo.Ce
llCqiAdjSchCntThl
d parameter must
not be set to 0.

None
7.8.3.3 Hardware
See 4.3.3 Hardware.

eRAN

If scheduling optimization is to be enabled in massive MIMO cells, the following parameters
need to be set.

PDCCH Optimization CellPdcchAlgo.PdcchOpti Select the

Switch mizationSwitch SF_3_8_HARQ_SELECTI
VE_SCH_SW option under
this parameter if selective
HARQ scheduling in
subframe 3 or 8 is required.
Massive MIMO Algorithm CellMMAlgo.MMAlgoOpt l Select the

Optimization Switch Switch DL_RB_ASSIGN_OPT
_SWITCH option under
this parameter if
downlink RB allocation
l If MCS index selection
optimization for
downlink paired UEs
with small-amount data
transmission or cell-level
outer-loop adjustment
optimization in
beamforming is required,
select the
MM_DL_SCH_AND_
MCS_OPT_SWITCH
option.
Cell CQI Adjustment CellCqiAdjAlgo.CellCqiAd This parameter must not be

Schedule Count Thld jSchCntThld set to 0. Set this parameter
based on the network plan.

//Enabling selective HARQ scheduling in subframe 3 or 8
PdcchOptimizationSwitch=SF_3_8_HARQ_SELECTIVE_SCH_SW-1;
//Enabling downlink RB allocation optimization
MOD CELLMMALGO: LocalCellId=0, MMAlgoOptSwitch=DL_RB_ASSIGN_OPT_SWITCH-1;
//Enabling adaptive setting of the initial cell-level CQI adjustment value if
cell-level outer-loop adjustment optimization in beamforming is required. For
details about the value of the CellCqiAdjSchCntThld parameter, see the network
plan.

eRAN
MOD CELLCQIADJALGO: LocalCellId=0, CellCqiAdjSchCntThld=20;

//Enabling MCS index selection optimization for downlink paired UEs with small-
amount data transmission or cell-level outer-loop adjustment optimization in
beamforming
MOD CELLMMALGO: LocalCellId=0, MMAlgoOptSwitch=MM_DL_SCH_AND_MCS_OPT_SWITCH-1;

//Deactivating selective HARQ scheduling in subframe 3 or 8
PdcchOptimizationSwitch=SF_3_8_HARQ_SELECTIVE_SCH_SW-0;
//Deactivating downlink RB allocation optimization
MOD CELLMMALGO: LocalCellId=0, MMAlgoOptSwitch=DL_RB_ASSIGN_OPT_SWITCH-0;
//Deactivating MCS index selection optimization for downlink paired UEs with
small-amount data transmission or cell-level outer-loop adjustment optimization
in beamforming
MOD CELLMMALGO: LocalCellId=0, MMAlgoOptSwitch=MM_DL_SCH_AND_MCS_OPT_SWITCH-0;


Step 1 Run the LST CELLPDCCHALGO command to query the status of the
SF_3_8_HARQ_SELECTIVE_SCH_SW option under the PDCCH Optimization Switch
parameter. Selective HARQ scheduling in subframe 3 or 8 has been enabled if
SF_3_8_HARQ_SELECTIVE_SCH_SW:On is displayed.
Step 2 Run the LST CELLMMALGO command to query the status of the
DL_RB_ASSIGN_OPT_SWITCH option under the Massive MIMO Algorithm
Optimization Switch parameter. Downlink RB allocation optimization has been enabled if
DL_RB_ASSIGN_OPT_SWITCH:On is displayed.
Step 3 Run the LST CELLMMALGO command to query the setting of the
MM_DL_SCH_AND_MCS_OPT_SWITCH option under the Massive MIMO Algorithm
Optimization Switch parameter. If MM_DL_SCH_AND_MCS_OPT_SWITCH:On is
displayed, MCS index selection optimization for downlink paired UEs with small-amount
data transmission or cell-level outer-loop adjustment optimization in beamforming has been
enabled.
----End


cell

the buffer is empty

eRAN

buffer is empty
1526730873 L.Traffic.Sch.DL.Num Number of times that UEs are

scheduled in a cell in the downlink

g PDSCH DRBs

precision of 1 ms)
1526730558 L.Cell.DL.PDSCH.Tti.Num Total number of uplink and

downlink TTIs
1526728664 L.ChMeas.PDCCH.DL.DTXNu Number of times of DTX for

m.AggLvl1 PDCCH resource allocation with
aggregation level 1 in a cell




aggregation level 1

aggregation level 2

aggregation level 4

aggregation level 8

l Downlink cell throughput = L.Thrp.bits.DL/L.Traffic.Sch.DL.Num

eRAN
l Average downlink cell throughput = L.Thrp.bits.DL/

L.Thrp.Time.Cell.DL.HighPrecision
l Proportion of PDCCH DTXs = (L.ChMeas.PDCCH.DL.DTXNum.AggLvl1 +
7.9 MU Beamforming Pairing of Antenna Selection UEs in

Dual-Stream Beamforming
7.9.1 Principles
In massive MIMO cells, antenna selection UEs can deliver better network performance when
working in dual-stream beamforming and being paired for MU beamforming. MU
beamforming pairing of antenna selection UEs in dual-stream beamforming is enabled when
the CellBf.AntSelUEMubfPairMode parameter is set to DUAL_STREAM_PAIR, the
FakeAntSelIdentificationSwitch option is selected under the CellAlgoSwitch.BfAlgoSwitch
parameter, and the CellBf.Tm8PairingOptSwitch parameter is set to ON.
MU beamforming requires the following parameters to be set for UEs in dual-stream

beamforming capable of transmit antenna selection. For details about the parameter settings,
see 7.9.4.1.1 Data Preparation.
l Offset to the threshold for switching the transmission mode of UEs capable of transmit
antenna selection from TM3 rank 2 to dual-stream beamforming:
CellBfMimoParaCfg.AsUeTM3Rank2ToDualBfOffset
antenna selection from dual-stream beamforming to TM3 rank 2:
CellBfMimoParaCfg.AsUeDualBfToTM3Rank2Offset
antenna selection from single-stream beamforming to dual-stream beamforming:
CellBfMimoParaCfg.AsUeBfSingleToDualOffset
If the TddAckFbModeCfgOptSwitch option is selected under the

CellAlgoSwitch.HarqAlgoSwitch parameter, it is recommended that the
ACK_FEEDBACK_IN_MUX_MODE_SW option be selected under the
CellBf.DualStreamBfAlgoSw parameter so that UEs working in dual-stream beamforming
(TM8) can enter the multiplexing feedback mode, increasing the downlink UE-perceived data
rate.
After MU beamforming pairing of antenna selection UEs in dual-stream beamforming is

enabled, the eNodeB preferentially identifies fake antenna selection UEs. For fake antenna
selection UEs, the eNodeB handles the pairing in a way specified for UEs incapable of
transmit antenna selection. For antenna selection UEs, the eNodeB allows the UEs to enter
dual-stream beamforming (TM8) and participate in MU beamforming pairing when TMA is
enabled. It takes long for the eNodeB to identify fake antenna selection UEs. During the

eRAN
identification period, unidentified fake antenna selection UEs may mistakenly enter TM8. As
a result, the performance is affected.
A fake antenna selection UE refers to the UE of which the chip supports transmit antenna
selection but the RF module does not support transmit antenna selection. As a whole, fake
antenna selection UEs do not support transmit antenna selection. However, these UEs claim
their support for transmit antenna selection in the reported RRC_UE_CAP_INFO message.
Figure 7-8 shows the differences between antenna selection UEs and fake antenna selection
UEs.
Figure 7-8 Differences between antenna selection UEs and fake antenna selection UEs
NOTE
Unless otherwise specified, UEs incapable of transmit antenna selection include fake antenna selection
UEs.
If scheduling optimization for antenna selection UEs is enabled by selecting the

ANT_SEL_SCHEDULING_OPT_SWITCH option under the CellAlgoExtSwitch.
AntennaSelectionAlgoSwitch parameter, downlink scheduling performance of antenna
selection UEs working in dual-stream beamforming improves.
If MU beamforming of antenna selection UEs in dual-stream beamforming is enabled in a
massive MIMO cell, the maximum number of beamforming layers is 2 and is controlled by
the CellBf.MaxBfRankPara parameter. This parameter takes effect on both antenna selection
UEs and non-antenna selection UEs. To prevent non-antenna selection UEs from entering
dual-stream beamforming (TM8) after MU beamforming pairing of antenna selection UEs in
dual-stream beamforming is enabled, it is recommended that the
NON_AS_UE_MAX_BF_RANK_CTRL_SW option be selected under the
CellBfMimoParaCfg.BfMimoAlgoOptSwitch parameter. In this case, the maximum number
of beamforming multiplexing layers is fixed to 1 for non-antenna selection UEs.
7.9.2.1 Benefits
This function improves the downlink UE-perceived data rate and downlink cell spectral
efficiency.

eRAN
7.9.2.2 Impacts
Network Impacts
This function improves the downlink UE-perceived data rate and downlink cell spectral
efficiency.
Function Impacts
Switching to TM7 in CellBf.MultiLayerT Switching to TM7 MU beamforming

multi-layer pairing hdSwitchToTM7 in Multi-Layer pairing of antenna
scenarios Pairing Scenarios selection UEs in
dual-stream
beamforming may
affect UE
transmission modes.
Heavy-load TMA HEAVYLOADTR Heavy-Load TMA MU beamforming

boost ANSMODEADAP Boost pairing of antenna
TBOOSTSW and selection UEs in
HISTORICALSPE dual-stream
CTRALEFFOPTS beamforming may
W options under the affect UE
CellBfMimoParaCf transmission modes.
g.BfMimoAlgoOptS
witch parameter
Dual-stream CellBf.MaxBfRank Beamforming (TDD) UEs working in

beamforming Para set to dual-stream
DUAL_LAYER_B beamforming (TM8)
F can enter the
multiplexing
feedback mode,
increasing the
downlink perceived
data rate of such
UEs.
7.9.3 Requirements
7.9.3.1 Licenses
None

eRAN
7.9.3.2 Software
Antenna selection UeSRSAntSelectCt None MU beamforming

for SRS rlSwitch option pairing of antenna
transmission under the selection UEs in
ENodeBAlgoSwitc dual-stream
h.CompatibilityCtrl beamforming
Switch parameter requires that the
eNodeB support
SRS transmit
antenna selection by
deselecting the
UeSRSAntSelectCt
rlSwitch option.

None
7.9.3.3 Hardware
See 4.3.3 Hardware.
7.9.3.4 Others
l UEs support TM8.
l UEs support transmit antenna selection.
l UEs comply with 3GPP Release 9 or later.
Compatibility Control ENodeBAlgoSwitch.Comp Clear the

Switch atibilityCtrlSwitch UeSRSAntSelectCtrlS-
witch option.
BF algorithm switch CellAlgoSwitch.BfAlgoSwi Select the

tch FakeAntSelIdentifica-
tionSwitch option.

eRAN
Beamforming maximum CellBf.MaxBfRankPara The value

number of layers DUAL_LAYER_BF is
recommended.
Antenna Selection UE CellBf.AntSelUEMubfPair- Set this parameter to

MUBF Pair Mode Mode DUAL_STREAM_PAIR
so that antenna selection
UEs can be paired for MU
beamforming when working
in TM8.
TM8 Pairing Optimization CellBf.Tm8PairingOptSwit Set this parameter to ON.

Switch ch
Dual-Stream BF Algorithm CellBf.DualStreamBfAlgoS If the

Switch w TddAckFbModeCfgOptS-
witch option is selected
under the
CellAlgoSwitch.HarqAlgoS
witch parameter, it is
ACK_FEEDBACK_IN_M
UX_MODE_SW option be
selected under the
CellBf.DualStreamBfAlgoS
w parameter.
AS UE TM3 Rank2 To Dual CellBfMimoParaCfg.AsUe Set this parameter to -14.

BF Offset TM3Rank2ToDualBfOffset
AS UE Dual BF To TM3 CellBfMimoParaCfg.AsUe Set this parameter to -20.

Rank2 Offset DualBfToTM3Rank2Offset
AS UE Single to Dual BF CellBfMimoParaCfg.AsUe Set this parameter to 6.

Offset BfSingleToDualOffset
Antenna Selection CellAlgoExtSwitch. Select the

Algorithm Switch AntennaSelectionAlgoS- ANT_SEL_SCHEDULIN
witch G_OPT_SWITCH option.
BfMimo Algorithm CellBfMimoParaCfg.BfMi It is recommended that the

Optimization Switch moAlgoOptSwitch NON_AS_UE_MAX_BF_
RANK_CTRL_SW option
be selected to prevent the
entry of non-antenna
selection UEs into dual-
stream beamforming (TM8).

eRAN

//Turn off the compatibility control switch
MOD ENODEBALGOSWITCH: CompatibilityCtrlSwitch=UeSRSAntSelectCtrlSwitch-0;
//Disabling fake antenna selection UE identification
MOD CELLALGOSWITCH: LocalCellId=0, BfAlgoSwitch=FakeAntSelIdentificationSwitch-1;
//Allowing antenna selection UEs to be paired for MU beamforming when working in
TM8
MOD CELLBF: LocalCellId=0, AntSelUEMubfPairMode=DUAL_STREAM_PAIR,
MaxBfRankPara=DUAL_LAYER_BF, Tm8PairingOptSwitch=ON;
//(Optional) Allowing UEs in dual-stream beamforming (TM8) to enter the
multiplexing feedback mode
MOD CELLBF: LocalCellId=0, DualStreamBfAlgoSw=ACK_FEEDBACK_IN_MUX_MODE_SW-1;
//Setting the thresholds related to UEs capable of transmit antenna selection
MOD CELLBFMIMOPARACFG: LocalCellId=0, AsUeTM3Rank2ToDualBfOffset=-14,
AsUeDualBfToTM3Rank2Offset=-20, AsUeBfSingleToDualOffset=6;
//(Optional) Enabling scheduling optimization for antenna selection UEs
MOD CELLALGOEXTSWITCH: LocalCellId=0,
AntennaSelectionAlgoSwitch=ANT_SEL_SCHEDULING_OPT_SWITCH-1;
//Disabling the entry of non-antenna selection UEs into dual-stream beamforming
(TM8)
BfMimoAlgoOptSwitch=NON_AS_UE_MAX_BF_RANK_CTRL_SW-1;

//Disabling fake antenna selection UE identification
MOD CELLALGOSWITCH: LocalCellId=0, BfAlgoSwitch=FakeAntSelIdentificationSwitch-0;
//Allowing antenna selection UEs not to be paired for MU beamforming when working
in TM8
MOD CELLBF: LocalCellId=0, AntSelUEMubfPairMode=SINGLE_STREAM_PAIR,
MaxBfRankPara=SINGLE_LAYER_BF, Tm8PairingOptSwitch=OFF;
//(Optional) Allowing UEs in dual-stream beamforming (TM8) not to enter the
multiplexing feedback mode
MOD CELLBF: LocalCellId=0, DualStreamBfAlgoSw=ACK_FEEDBACK_IN_MUX_MODE_SW-0;
//(Optional) Deactivating scheduling optimization for antenna selection UEs
MOD CELLALGOEXTSWITCH: LocalCellId=0,
AntennaSelectionAlgoSwitch=ANT_SEL_SCHEDULING_OPT_SWITCH-0;
//Enabling the entry of non-antenna selection UEs into dual-stream beamforming
(TM8)
BfMimoAlgoOptSwitch=NON_AS_UE_MAX_BF_RANK_CTRL_SW-0;


Step 1 Run the LST CELLALGOSWITCH and LST CELLBF commands. If
FakeAntSelIdentificationSwitch:On is displayed under the BF algorithm switch parameter,
Antenna Selection UE MUBF Pair Mode is set to DUAL_STREAM_PAIR, and TM8
Pairing Optimization Switch is set to On, this function has taken effect.
Step 2 (Optional) Run the LST CELLBF command. If

ACK_FEEDBACK_IN_MUX_MODE_SW:Off is displayed under the Dual-Stream BF
Algorithm Switch parameter, UEs in dual-stream beamforming (TM8) can enter the
multiplexing feedback mode.
Step 3 (Optional) Run the LST CELLALGOEXTSWITCH command. If

ANT_SEL_SCHEDULING_OPT_SWITCH:On is displayed under the Antenna Selection

eRAN
Algorithm Switch parameter, scheduling optimization for antenna selection UEs has been
enabled.
Step 4 Run the LST CELLBFMIMOPARACFG command. If
NON_AS_UE_MAX_BF_RANK_CTRL_SW:Off is displayed under the BfMimo
Algorithm Optimization Switch parameter, non-antenna selection UEs cannot enter dual-
stream beamforming (TM8).
----End
Fake Antenna Selection UE Identification

Step 1 View the RRC_UE_CAP_INFO message on the Uu interface. A fake UE claims its support
for transmit antenna selection using the RRC_UE_CAP_INFO message, as shown in Figure
7-9.
Figure 7-9 RRC_UE_CAP_INFO message
Step 2 After identifying the UE, the eNodeB sends an RRC_CONN_RECFG message to instruct the
UE to disable transmit antenna selection, as shown in Figure 7-10. This indicates that fake
antenna selection UE identification has taken effect.

eRAN
Figure 7-10 RRC_CONN_RECFG message
----End
MU Beamforming Pairing of Antenna Selection UEs in Dual-Stream

Beamforming
Use the U2020 to perform signaling tracing. For details, see 6.2.4.3 Network Monitoring.
Observe the measurement results of the monitoring object listed in Table 7-8 to determine
whether MU beamforming pairing of antenna selection UEs in dual-stream beamforming has
taken effect.
Table 7-8 Monitoring object for MU beamforming pairing of antenna selection UEs in dual-
stream beamforming
Monitoring Object Meaning
Number of Massive Number of RBs paired with massive MIMO MU

MIMO MUBF Pairing beamforming TM8 UEs. It is the average of the cumulative
TM8 RB (Num) total number of RBs paired with TM8 UEs at each TTI at the
When MU beamforming pairing of antenna selection UEs in dual-stream beamforming is

enabled, the number of pairing layers and PRBs increases and the measured values of the
following counters may reach 64 bits.
1526728882 L.ChMeas.BF.PRB.OL.Rank2 Total number of used downlink

PRBs in beamforming rank 2
mode

rank 1 mode

eRAN

rank 2 mode
1526737846 L.ChMeas.PRB.TM8 Total number of used downlink

PRBs in TM8
7.10 Access Control Optimization Based on Uplink and

Downlink UE-Perceived Rates
7.10.1 Principles
In a massive MIMO cell, if the uplink or downlink UE-perceived rate is less than a specified
target value and congestions occur in the uplink or downlink, the eNodeB uses the access
control (AC barring) mechanism to reduce the UE access opportunity, improving user
experience.
This function is controlled by the MM_ACCESS_CONTROL_OPT_SWITCH option

under the CellMMAlgo.MMAlgoOptSwitch parameter.
7.10.2.1 Benefits
After this function is enabled in heavy-load scenarios, you can set a proper target uplink or
downlink UE-perceived rate to improve user experience based on the optimal cell capacity
and performance gains.
7.10.2.2 Impacts
Network Impacts
This function prevents the uplink and downlink UE-perceived rates from dropping to 0 Mbit/s
and ensures that the target rate is reached.
Function Impacts
None
7.10.3 Requirements
7.10.3.1 Licenses
None

eRAN
7.10.3.2 Software
Massive MIMO introduction N/A 4 Basic Massive MIMO

Functions

None
7.10.3.3 Hardware
See 4.3.3 Hardware.
Massive MIMO Algorithm CellMMAlgo.MMAlgoOpt In heavy-load scenarios, it is

Optimization Switch Switch recommended that the
MM_ACCESS_CONTRO
L_OPT_SWITCH option
be selected to enable access
control optimization based
on uplink and downlink UE-
perceived rates.
AcBar algorithms switch CellAlgoSwitch.AcBarAlgo It is recommended that this

Switch parameter be set to
ACBAR_SWITCH_DYNA
MIC in heavy-load
scenarios.
Ac Bar Algorithm Switch CellAlgoSwitch.AcBarAlgo It is recommended that this

for Dynamic forDynSwitch parameter be set to
DYNAMIC_FOR_MO in
heavy-load scenarios.
RB Congestion High CellRacThd.RbCongHighT It is recommended that this

Threshold hd parameter be set to 90 in

eRAN
CCE Allocation Failure CellRacThd.CceAlFailHig It is recommended that this

High Threshold hThd parameter be set to 40 in
UL Experience Rate CellRacThd.UlExperience It is recommended that this

Threshold Thd parameter be set to 50 in
DL Experience Rate CellRacThd.DlExperience It is recommended that this

Threshold Thd parameter be set to 1000 in
AC barring for mobile data CellAcBar.AcBarringFor It is recommended that this

configure indicator MoDataCfgInd parameter be set to CFG in
AC barring for mobile CellAcBar.AcBarringFor It is recommended that this

signal configure indicator MoSigCfgInd parameter be set to CFG in
Access probability factor for CellAcBar.AcBarringFacto It is recommended that this

signaling rForSig parameter be set to P85 in
Access probability factor for CellAcBar.AcBarringFacto It is recommended that this

originating call rForCall parameter be set to P85 in
Mean access barring time CellAcBar.AcBarTimeFor ACCESS_BARRING_TIM

for originating call Call E_S4
Mean access barring time CellAcBar.AcBarTimeFor ACCESS_BARRING_TIM

for signaling Sig E_S4
Dynamic AC Barring CellDynAcBarAlgo- It is recommended that this

Control Trigger Threshold Para.DynAcBarTriggerThd parameter be set to 95 in
MO Factor Initial Value CellDynAcBarAlgo- Set this parameter to P95.

Para.MoFactorInitialValue
MO Factor Adjusting Step CellDynAcBarAlgo- Set this parameter to 1.

Para.MoFactorAdjStep
MO Cancel Condition CellDynAcBarAlgo- Set this parameter to 1.

Satisfied Periods Para.MoCancelCondSati-
Periods
MO Factor Retreating Step CellDynAcBarAlgo- Set this parameter to 2.

Para.MoFactorRetreatStep

eRAN

MOD CELLMMALGO: LocalCellId=0, MMAlgoOptSwitch=MM_ACCESS_CONTROL_OPT_SWITCH-1;
MOD CELLALGOSWITCH: LocalCellId=0, AcBarAlgoSwitch=ACBAR_SWITCH_DYNAMIC,
AcBarAlgoforDynSwitch=DYNAMIC_FOR_MO-1;
MOD CELLRACTHD: LocalCellId=0,
RbCongHighThd=90,CceAlFailHighThd=40,UlExperienceThd=50, DlExperience=1000;
MOD CELLACBAR: LocalCellId=0, AcBarringForMoDataCfgInd=CFG,
AcBarringForMoSigCfgInd=CFG, AcBarringFactorForSig=P85,
AcBarringFactorForCall=85, AcBarTimeForCall=ACCESS_BARRING_TIME_S4,
AcBarTimeForSig=ACCESS_BARRING_TIME_S4;
MOD CELLDYNACBARALGOPARA: LocalCellId=0, DynAcBarTriggerThd=95,
MoFactorInitialValue=P95, MoFactorAdjStep=1, MoCancelCondSatiPeriods=1,
MoFactorRetreatStep=2;

MOD CELLMMALGO: LocalCellId=0, MMAlgoOptSwitch=MM_ACCESS_CONTROL_OPT_SWITCH-0;


Run the LST CELLMMALGO command. If
MM_ACCESS_CONTROL_OPT_SWITCH:On is displayed under the Massive MIMO
Algorithm Optimization Switch parameter, this function has been enabled.


cell

the buffer is empty

buffer is empty

g PDSCH DRBs

precision of 1 ms)

eRAN
Average downlink UE throughput = (L.Thrp.bits.DL-L.Thrp.bits.DL.LastTTI)/


7.11 PDCCH Resource Reservation for Big-Packet Services

in Heavy-Load Scenarios
7.11.1 Principles
In massive MIMO cells, if PDCCH resources are insufficient in heavy-load scenarios, UEs
performing large-packet services may not be scheduled. As a result, not all the PRBs in the
cell are used or there are still free RB resources in the spatial domain. To solve this issue,
PDCCH resource reservation for big-packet services in heavy-load scenarios is introduced
This function is controlled by the HEAVY_LOAD_BIG_PKT_SCH_OPT_SW option

under the CellPdcchAlgo.PdcchOptimizationSwitch parameter. After this function is
enabled, the eNodeB preferentially reserves PDCCH resources for UEs performing large-
packet services. This ensures that UEs performing large-packet services can be scheduled and
that RB resources can be fully used in heavy-load scenarios.
NOTE
PDCCH resource reservation for big-packet services in heavy-load scenarios and optimized PDCCH
aggregation level selection near the cell center are controlled by the same switch.
7.11.2.1 Benefits
This feature improves the downlink cell throughput and spectral efficiency in heavy-load
scenarios.
7.11.2.2 Impacts
Network Impacts
This feature improves the downlink cell throughput and spectral efficiency in heavy-load
scenarios.
Function Impacts
None
7.11.3 Requirements

eRAN
7.11.3.1 Licenses
None
7.11.3.2 Software
MU beamforming MuBfSwitch option under 6.2 MU Beamforming

the
CellAlgoSwitch.MuBfAlgo
Switch parameter

None
7.11.3.3 Hardware
See 4.3.3 Hardware.
PDCCH Optimization CellPdcchAlgo.PdcchOpti If PDCCH resource

Switch mizationSwitch reservation for big-packet
services in heavy-load
scenarios is required, select
the
HEAVY_LOAD_BIG_PK
T_SCH_OPT_SW option.

PdcchOptimizationSwitch=HEAVY_LOAD_BIG_PKT_SCH_OPT_SW-1;
MOD CELLALGOSWITCH: LocalCellId=0, MuBfAlgoSwitch=MuBfSwitch-1;

eRAN



Run the LST CELLPDCCHALGO and LST CELLALGOSWITCH commands. If
HEAVY_LOAD_BIG_PKT_SCH_OPT_SW:On under the PDCCH Optimization Switch
parameter and MuBfSwitch:On under the MUBF Algorithm Switch parameter are
displayed, this function has been enabled.


cell

the buffer is empty

buffer is empty

g PDSCH DRBs

precision of 1 ms)
Average downlink UE throughput = (L.Thrp.bits.DL - L.Thrp.bits.DL.LastTTI)/


7.12 Optimized PDCCH Aggregation Level Selection Near

the Cell Center

eRAN
7.12.1 Principles
PDCCH aggregation levels are selected based on the CQI values adjusted based on the
PDSCH BLER. However, in massive MIMO cells, the PDSCH BLER is high due to mobility
and abnormal UEs. This affects the PDCCH aggregation level selection accuracy and severely
limits the PDCCH capacity. To solve this issue, PDCCH resource reservation for big-packet
services in heavy-load scenarios is introduced.
This function is controlled by the HEAVY_LOAD_BIG_PKT_SCH_OPT_SW option

under the CellPdcchAlgo.PdcchOptimizationSwitch parameter. After this function is
enabled, the eNodeB selects the PDCCH aggregation level based on the PDCCH BLER and
the CQI values reported by the UE. This ensures the PDCCH reliability and capacity, and
improves the cell spectral efficiency.
NOTE
PDCCH resource reservation for big-packet services in heavy-load scenarios and optimized PDCCH
aggregation level selection near the cell center are controlled by the same switch.
7.12.2.1 Benefits
This function reduces the CCE usage, increases the cell-level PDCCH capacity, and improves
the cell spectral efficiency if all of the following conditions are met:
l PDCCH resources are insufficient (ratio of uplink or downlink CCE allocation failures >
40% and equivalent CCE efficiency > 60%).
l There are abnormal UEs.
l MU beamforming pairing performance is poor or the downlink MCS index is low.
7.12.2.2 Impacts
Network Impacts
If there are UEs with reported CQI values greater than expected, such as IRC-powered UEs,
this function may affect the PDCCH reliability and decrease the UE-perceived data rate due to
lack of outer-loop CQI control.
Function Impacts
None
7.12.3 Requirements
7.12.3.1 Licenses
None

eRAN
7.12.3.2 Software
Massive MIMO introduction N/A 4 Basic Massive MIMO

Functions

None
7.12.3.3 Hardware
See 4.3.3 Hardware.
PDCCH Optimization CellPdcchAlgo.PdcchOpti If optimized PDCCH

Switch mizationSwitch aggregation level selection
near the cell center is
HEAVY_LOAD_BIG_PK
T_SCH_OPT_SW option.




eRAN

Run the LST CELLPDCCHALGO command. If
HEAVY_LOAD_BIG_PKT_SCH_OPT_SW:On is displayed under the PDCCH
Optimization Switch parameter, this function has been enabled.


cell

g PDSCH DRBs

precision of 1 ms)

7.13 Intelligent Parameter Selection

This section describes TDLEOFD-151616 Intelligent Selection of Massive MIMO Parameters
(trial).
7.13.1 Principles
This feature enables the eNodeB to automatically optimize parameters related to massive
MIMO cells in big-event scenarios.
This feature is controlled by the BIG_EVENT_THLD_LEARN_SW and

BIG_EVENT_PDCCH_CAPC_ADAPT_SW options under the
CellMMAlgo.MmParamIntelSelectSw parameter. If both of the options are selected, the
eNodeB periodically detects the CCE failure rate and the number of uplink synchronized UEs.
If the CCE failure rate and the number of uplink synchronized UEs are greater than their
thresholds self-learned by the system, the eNodeB adjusts PDCCH capacity-related
parameters listed in the following table. Otherwise, the eNodeB restores the parameter values
to those used before the adjustment.
Parameter Adjusted Value
CellPdcchAlgo.PdcchCapacityImproveSwitch ON
CellDlschAlgo.RbgAllocStrategy ADAPTIVE

eRAN
Parameter Adjusted Value
CellPdcchAlgo.CceMaxInitialRatio 10:1
CellPdcchAlgo.PdcchOptimizationSwitch ON
CellPdcchAlgo.PdcchBlerTarget 15
CellPdcchAlgo.PdcchOutLoopAdjBaseStep 1
CellPdcchAlgo.PdcchPowerEnhancedSwitch ON
CellPdcchAlgo.PdcchPwrCtrlUserNumThd 280
NonGbrBundlingSwitch option under the ON

CellAlgoSwitch.DlSchSwitch parameter
AbnUeSchSwitch option under the ON

CellAlgoSwitch.CellSchStrategySwitch parameter
CellUlschAlgo.UlSchAbnUeThd 11
CellPdcchAlgo.NackDtxRatioThd 50
InterFreqHoGroup.A3InterFreqHoA1ThdRsrp N+6, where N is the value before

the adjustment.
InterFreqHoGroup.InterFreqHoA1ThdRsrp N+6, where N is the value before

the adjustment.
CellPdcchAlgo.PdcchAggLvlCLAdjustSwitch OFF
7.13.2.1 Benefits
In heavy-load scenarios, this feature improves the average downlink UE throughput, average
downlink cell throughput, and downlink cell spectral efficiency.
l Average downlink UE throughput = (L.Thrp.bits.DL - L.Thrp.bits.DL.LastTTI)/

7.13.2.2 Impacts
NOTE
Intelligent parameter selection has no impact on the network or functions. However, some function
control switches are turned on after parameter adjustment. For details about the network and function
impacts of these functions, see the corresponding feature parameter descriptions.

eRAN
Network Impacts
None
Function Impacts
None
7.13.3 Requirements
7.13.3.1 Licenses
TDLEOFD-151616 Intelligent Selection LT4SMMPISTDD Per Cell

of Massive MIMO
Parameters (Trial)
7.13.3.2 Software
Massive MIMO N/A 4 Basic Massive Intelligent parameter

introduction MIMO Functions selection takes effect
only in massive
MIMO cells.
Downlink non-GBR NonGbrBundlingS- Scheduling None

packet bundling witch option under
the
CellAlgoSwitch.DlS
chSwitch parameter

None
7.13.3.3 Hardware
See 4.3.3 Hardware.

eRAN
Massive MIMO Param CellMMAlgo.MmParamInt Select the

Intelligent Selection Sw elSelectSw BIG_EVENT_THLD_LE
ARN_SW and
BIG_EVENT_PDCCH_C
APC_ADAPT_SW options.

MmParamIntelSelectSw=BIG_EVENT_THLD_LEARN_SW-1&BIG_EVENT_PDCCH_CAPC_ADAPT_SW-1;

MmParamIntelSelectSw=BIG_EVENT_THLD_LEARN_SW-0&BIG_EVENT_PDCCH_CAPC_ADAPT_SW-0;


Run the LST CELLMMALGO command. If both BIG_EVENT_THLD_LEARN_SW:On
and BIG_EVENT_PDCCH_CAPC_ADAPT_SW:On are displayed under the Massive
MIMO Param Intelligent Selection Sw parameter, intelligent parameter selection has been
enabled.


cell

the buffer is empty

buffer is empty

g PDSCH DRBs

eRAN

precision of 1 ms)
l Average downlink UE throughput = (L.Thrp.bits.DL - L.Thrp.bits.DL.LastTTI)/


eRAN
Massive MIMO (TDD) Feature Parameter Description 8 Parameters
8 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 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 (TDD) Feature Parameter Description 9 Counters
9 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 (TDD) Feature Parameter Description 10 Glossary
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
Massive MIMO (TDD) Feature Parameter Description 11 Reference Documents
11 Reference Documents
1. Beamforming (TDD)
2. Cloud BB Overview
3. CSPC
4. D-MIMO (TDD)
5. DL CoMP (TDD)
6. eMBMS
7. eMTC
8. eX2 Self-Management
9. LCS
10. Dynamic Power Sharing Between LTE Carriers
11. MIMO
12. MRC and IRC Receivers
13. License Management
14. Relay
15. SFN
16. Turbo Receiver
17. UL CoMP
18. VoLTE
19. WBB
20. WTTx Turbo Beamforming (TDD)
21. Specified User Coordinated Scheduling
22. Extended Cell Range
23. Scheduling
24. Interference Detection and Suppression
25. Interference Randomizing (TDD)
26. High Speed Mobility
27. Power Control
28. USU3900-based Multi-BBU Interconnection

eRAN
Massive MIMO (TDD) Feature Parameter Description 11 Reference Documents
29. USU3910-based Multi-BBU Interconnection

30. Extended CP
31. Mobility Management in Connected Mode
32. Soft Split Resource Duplex (TDD)
33. Physical Channel Resource Management
34. Intra-RAT Mobility Load Balancing
35. Uplink Coordinated Scheduling
36. Channel State Management
37. Carrier Aggregation
38. Adaptive ICIC
39. Subframe Configuration (TDD)

Huawei 434789548 Massive MIMO TDD ERAN15 1 Draft A PDF

Uploaded by

Copyright:

Available Formats

Huawei 434789548 Massive MIMO TDD ERAN15 1 Draft A PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Huawei 434789548 Massive MIMO TDD ERAN15 1 Draft A PDF

Uploaded by

Copyright:

Available Formats

eRAN

Massive MIMO (TDD) Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.................................................................................................................. 8

4 Basic Massive MIMO Functions...............................................................................................14

5 Uplink Multiple-Antenna Reception...................................................................................... 37

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. ii

6 Downlink Multiple-Antenna Transmission.......................................................................... 53

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. iii

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. iv

6.5 Multi-User Split SDMA............................................................................................................................................... 90

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. v

6.7.2.1 Benefits................................................................................................................................................................. 120

7 Performance Optimization in Massive MIMO....................................................................136

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. vi

7.2.4 Operation and Maintenance.....................................................................................................................................140

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. vii

7.5.2.1 Benefits................................................................................................................................................................. 157

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. viii

7.7.4.1.3 Using the CME.................................................................................................................................................. 168

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. ix

7.10.3.1 Licenses.............................................................................................................................................................. 185

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. x

7.13 Intelligent Parameter Selection.................................................................................................................................194

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. xi

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

Optimized TM9 hybrid None 3900 and 5900 series base

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 1

Change Description Parameter Change Base Station Model

Added moving UE Added the 3900 and 5900 series base

Added support for TM9 None 5900 series base stations

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 2

Change Description Parameter Change Base Station Model

Added scheduling Added the 3900 and 5900 series base

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 3

Change Description Parameter Change Base Station Model

Added MU beamforming Added the 3900 and 5900 series base

Added mutually exclusive None 3900 and 5900 series base

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 4

Change Description Parameter Change Base Station Model

Modified the configuration None 3900 and 5900 series base

Added support of the None 3900 and 5900 series base

Modified the configuration None 3900 and 5900 series base

Added MCS index selection None 5900 series base stations

Added support of the None 5900 series base stations

Added the restriction that None 5900 series base stations

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 5

Change Description Parameter Change Base Station Model

Added the restriction that None 5900 series base stations

Added the mutually None 3900 and 5900 series base

Added enhanced None 3900 and 5900 series base

Changed the name of None 3900 and 5900 series base

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 6

Change Description Parameter Change Base Station Model

Replaced the l Added the 3900 and 5900 series base

Added MU beamforming Added the 3900 and 5900 series base