Massive MIMO (TDD) (eRAN16.1 - 13)

eRAN
Massive MIMO (TDD) Feature

Parameter Description
Issue 13
Date 2021-08-13
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2021. 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: https://www.huawei.com
Email: support@huawei.com
Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. i

eRAN
Massive MIMO (TDD) Feature Parameter
Description Contents
Contents
1 Change History.........................................................................................................................1
1.1 eRAN16.1 13 (2021-08-13)..................................................................................................................................................1
1.2 eRAN16.1 12 (2021-05-07)..................................................................................................................................................1
1.3 eRAN16.1 11 (2021-02-28)..................................................................................................................................................2
1.4 eRAN16.1 10 (2021-01-14)..................................................................................................................................................2
1.5 eRAN16.1 09 (2020-12-30)..................................................................................................................................................3
1.6 eRAN16.1 08 (2020-12-08)..................................................................................................................................................3
1.7 eRAN16.1 07 (2020-10-31)..................................................................................................................................................3
1.8 eRAN16.1 06 (2020-09-29)..................................................................................................................................................4
1.9 eRAN16.1 05 (2020-08-31)..................................................................................................................................................4
1.10 eRAN16.1 04 (2020-07-29)............................................................................................................................................... 5
1.11 eRAN16.1 03 (2020-07-03)............................................................................................................................................... 6
1.12 eRAN16.1 02 (2020-05-20)............................................................................................................................................... 6
1.13 eRAN16.1 01 (2020-04-07)............................................................................................................................................... 7
1.14 eRAN16.1 Draft C (2020-03-30)...................................................................................................................................... 8
1.15 eRAN16.1 Draft B (2020-03-10)...................................................................................................................................... 8
1.16 eRAN16.1 Draft A (2020-01-20)...................................................................................................................................... 9
2 About This Document...........................................................................................................16

2.1 General Statements..............................................................................................................................................................16
2.2 Applicable RAT....................................................................................................................................................................... 16
2.3 Features in This Document................................................................................................................................................ 16
3 Overview................................................................................................................................. 19
3.1 Introduction............................................................................................................................................................................ 19
3.2 Application Scenarios.......................................................................................................................................................... 21
4 Basic Massive MIMO Functions..........................................................................................23

4.1 Principles.................................................................................................................................................................................. 23
4.2 Network Analysis.................................................................................................................................................................. 25
4.2.1 Benefits................................................................................................................................................................................. 25
4.2.2 Impacts.................................................................................................................................................................................. 26
4.3 Requirements......................................................................................................................................................................... 29
4.3.1 Licenses................................................................................................................................................................................. 29
4.3.2 Software................................................................................................................................................................................29
Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. ii

eRAN
4.3.3 Hardware.............................................................................................................................................................................. 34
4.4 Operation and Maintenance............................................................................................................................................. 35
4.4.1 Data Configuration........................................................................................................................................................... 35
4.4.1.1 Data Preparation............................................................................................................................................................ 35
4.4.1.2 Using MML Commands............................................................................................................................................... 45
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 47
4.4.2 Activation Verification..................................................................................................................................................... 48
4.4.3 Network Monitoring......................................................................................................................................................... 48
4.4.4 Possible Issues.................................................................................................................................................................... 48
5 Uplink Multiple-Antenna Reception.................................................................................51

5.1 Receive Diversity................................................................................................................................................................... 51
5.1.1 Principles.............................................................................................................................................................................. 51
5.1.2 Network Analysis............................................................................................................................................................... 51
5.1.2.1 Benefits.............................................................................................................................................................................. 51
5.1.2.2 Impacts.............................................................................................................................................................................. 52
5.1.3 Requirements...................................................................................................................................................................... 52
5.1.3.1 Licenses.............................................................................................................................................................................. 53
5.1.3.2 Software............................................................................................................................................................................ 53
5.1.3.3 Hardware.......................................................................................................................................................................... 53
5.1.4 Operation and Maintenance......................................................................................................................................... 53
5.2 MU-MIMO............................................................................................................................................................................... 53
5.2.1 Principles.............................................................................................................................................................................. 54
5.2.2.1 Benefits.............................................................................................................................................................................. 57
5.2.2.2 Impacts.............................................................................................................................................................................. 57
5.2.3 Requirements...................................................................................................................................................................... 58
5.2.3.1 Licenses.............................................................................................................................................................................. 58
5.2.3.2 Software............................................................................................................................................................................ 61
5.2.3.3 Hardware.......................................................................................................................................................................... 63
5.2.4.1 Data Configuration........................................................................................................................................................ 63
5.2.4.1.1 Data Preparation.........................................................................................................................................................63
5.2.4.1.2 Using MML Commands............................................................................................................................................ 65
5.2.4.1.3 Using the MAE-Deployment................................................................................................................................... 66
5.2.4.2 Activation Verification.................................................................................................................................................. 66
5.2.4.3 Network Monitoring..................................................................................................................................................... 67
5.2.4.4 Possible Issues................................................................................................................................................................. 69
6 Downlink Multiple-Antenna Transmission..................................................................... 70

6.1 3D Beamforming................................................................................................................................................................... 71
6.1.1 Principles.............................................................................................................................................................................. 71
6.1.2.1 Benefits.............................................................................................................................................................................. 73
Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. iii

eRAN
6.1.2.2 Impacts.............................................................................................................................................................................. 73
6.1.3 Requirements...................................................................................................................................................................... 74
6.1.3.1 Licenses.............................................................................................................................................................................. 74
6.1.3.2 Software............................................................................................................................................................................ 74
6.1.3.3 Hardware.......................................................................................................................................................................... 75
6.1.4.4 Possible Issues................................................................................................................................................................. 78
6.2 MU Beamforming................................................................................................................................................................. 79
6.2.1 Principles.............................................................................................................................................................................. 79
6.2.1.1 Overview........................................................................................................................................................................... 79
6.2.1.2 UE Pairing......................................................................................................................................................................... 81
6.2.1.3 Scheduling Optimizations for MU Beamforming................................................................................................82
6.2.1.4 Initial CQI Adjustment Value Control for MU Beamforming.......................................................................... 84
6.2.2.1 Benefits.............................................................................................................................................................................. 84
6.2.2.2 Impacts.............................................................................................................................................................................. 85
6.2.3 Requirements...................................................................................................................................................................... 87
6.2.3.1 Licenses.............................................................................................................................................................................. 87
6.2.3.2 Software............................................................................................................................................................................ 89
6.2.3.3 Hardware.......................................................................................................................................................................... 90
6.3 TM9......................................................................................................................................................................................... 100
6.3.1 Principles............................................................................................................................................................................ 101
6.3.2 Network Analysis............................................................................................................................................................ 103
6.3.2.1 Benefits............................................................................................................................................................................103
6.3.2.2 Impacts............................................................................................................................................................................ 104
6.3.3 Requirements.................................................................................................................................................................... 105
6.3.3.1 Licenses........................................................................................................................................................................... 105
6.3.3.2 Software.......................................................................................................................................................................... 106
6.3.3.3 Hardware........................................................................................................................................................................ 109
Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. iv

eRAN
6.3.3.4 Others.............................................................................................................................................................................. 110

6.3.4 Operation and Maintenance....................................................................................................................................... 111
6.3.4.1 Data Configuration..................................................................................................................................................... 111
6.3.4.1.1 Data Preparation...................................................................................................................................................... 111
6.3.4.1.2 Using MML Commands......................................................................................................................................... 114
6.3.4.1.3 Using the MAE-Deployment.................................................................................................................................115
6.3.4.2 Activation Verification................................................................................................................................................115
6.3.4.3 Network Monitoring................................................................................................................................................... 117
6.4 TM9 Hybrid Precoding...................................................................................................................................................... 118
6.4.1 Principles............................................................................................................................................................................ 118
6.4.2.1 Benefits............................................................................................................................................................................119
6.4.2.2 Impacts............................................................................................................................................................................ 120
6.4.3 Requirements.................................................................................................................................................................... 121
6.4.3.1 Licenses........................................................................................................................................................................... 121
6.4.3.2 Software.......................................................................................................................................................................... 122
6.4.3.3 Hardware........................................................................................................................................................................ 124
6.5 Multi-User Split SDMA..................................................................................................................................................... 128
6.5.1 Principles............................................................................................................................................................................ 128
6.5.2.1 Benefits............................................................................................................................................................................131
6.5.2.2 Impacts............................................................................................................................................................................ 132
6.5.3 Requirements.................................................................................................................................................................... 133
6.5.3.1 Licenses........................................................................................................................................................................... 133
6.5.3.2 Software.......................................................................................................................................................................... 133
6.5.3.3 Hardware........................................................................................................................................................................ 135
6.5.4.4 Possible Issues............................................................................................................................................................... 141
6.6 PDCCH SDMA ..................................................................................................................................................................... 141
Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. v

eRAN
6.6.1 Principles............................................................................................................................................................................ 141

6.6.2.1 Benefits............................................................................................................................................................................144
6.6.2.2 Impacts............................................................................................................................................................................ 145
6.6.3 Requirements.................................................................................................................................................................... 145
6.6.3.1 Licenses........................................................................................................................................................................... 145
6.6.3.2 Software.......................................................................................................................................................................... 145
6.6.3.3 Hardware........................................................................................................................................................................ 146
6.6.4.4 Possible Issues............................................................................................................................................................... 150
6.7 TMA......................................................................................................................................................................................... 151
6.7.1 Principles............................................................................................................................................................................ 151
6.7.1.1 Introduction to Transmission Modes.....................................................................................................................151
6.7.1.2 TMA Principles.............................................................................................................................................................. 152
6.7.1.3 Optimized TMA............................................................................................................................................................ 155
6.7.2.1 Benefits............................................................................................................................................................................163
6.7.2.2 Impacts............................................................................................................................................................................ 163
6.7.3 Requirements.................................................................................................................................................................... 165
6.7.3.1 Licenses........................................................................................................................................................................... 165
6.7.3.2 Software.......................................................................................................................................................................... 165
6.7.3.3 Hardware........................................................................................................................................................................ 167
6.8 Enhanced Coordinated Scheduling Based Power Control.................................................................................... 173
6.8.1 Principles............................................................................................................................................................................ 173
6.8.2.1 Benefits............................................................................................................................................................................176
6.8.2.2 Impacts............................................................................................................................................................................ 177
6.8.3 Requirements.................................................................................................................................................................... 177
6.8.3.1 Licenses........................................................................................................................................................................... 177
Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. vi

eRAN
6.8.3.2 Software.......................................................................................................................................................................... 177

6.8.3.3 Hardware........................................................................................................................................................................ 180
6.8.3.4 Others.............................................................................................................................................................................. 180
6.8.4.4 Possible Issues............................................................................................................................................................... 182
7 Performance Optimization in Massive MIMO..............................................................183

7.1 Massive MIMO Load Steering........................................................................................................................................ 183
7.2 PDCCH Capacity Improvement...................................................................................................................................... 183
7.2.1 Principles............................................................................................................................................................................ 184
7.2.2.1 Benefits............................................................................................................................................................................186
7.2.2.2 Impacts............................................................................................................................................................................ 187
7.2.3 Requirements.................................................................................................................................................................... 187
7.2.3.1 Licenses........................................................................................................................................................................... 187
7.2.3.2 Software.......................................................................................................................................................................... 187
7.2.3.3 Hardware........................................................................................................................................................................ 189
7.3 Uplink Overload Optimization....................................................................................................................................... 191
7.3.1 Principles............................................................................................................................................................................ 192
7.3.2.1 Benefits............................................................................................................................................................................193
7.3.2.2 Impacts............................................................................................................................................................................ 193
7.3.3 Requirements.................................................................................................................................................................... 193
7.3.3.1 Licenses........................................................................................................................................................................... 193
7.3.3.2 Software.......................................................................................................................................................................... 194
7.3.3.3 Hardware........................................................................................................................................................................ 194
Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. vii

eRAN

7.4 SRS Interference Joint Suppression...............................................................................................................................196
7.4.1 Principles............................................................................................................................................................................ 196
7.4.2.1 Benefits............................................................................................................................................................................200
7.4.2.2 Impacts............................................................................................................................................................................ 201
7.4.3 Requirements.................................................................................................................................................................... 202
7.4.3.1 Licenses........................................................................................................................................................................... 202
7.4.3.2 Software.......................................................................................................................................................................... 203
7.4.3.3 Hardware........................................................................................................................................................................ 205
7.5 SRS Time-Domain Measurement and SDNR............................................................................................................ 208
7.5.1 Principles............................................................................................................................................................................ 208
7.5.2.1 Benefits............................................................................................................................................................................209
7.5.2.2 Impacts............................................................................................................................................................................ 209
7.5.3 Requirements.................................................................................................................................................................... 210
7.5.3.1 Licenses........................................................................................................................................................................... 210
7.5.3.2 Software.......................................................................................................................................................................... 210
7.5.3.3 Hardware........................................................................................................................................................................ 210
7.6 Beamforming Weight Optimization.............................................................................................................................212
7.6.1 Principles............................................................................................................................................................................ 212
7.6.2.1 Benefits............................................................................................................................................................................213
7.6.2.2 Impacts............................................................................................................................................................................ 213
7.6.3 Requirements.................................................................................................................................................................... 213
7.6.3.1 Licenses........................................................................................................................................................................... 213
Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. viii

eRAN
7.6.3.2 Software.......................................................................................................................................................................... 214

7.6.3.3 Hardware........................................................................................................................................................................ 214
7.7 IRC............................................................................................................................................................................................ 216
7.7.1 Principles............................................................................................................................................................................ 216
7.7.2.1 Benefits............................................................................................................................................................................217
7.7.2.2 Impacts............................................................................................................................................................................ 218
7.7.3 Requirements.................................................................................................................................................................... 218
7.7.3.1 Licenses........................................................................................................................................................................... 219
7.7.3.2 Software.......................................................................................................................................................................... 219
7.7.3.3 Hardware........................................................................................................................................................................ 219
7.8 Scheduling Optimization................................................................................................................................................. 223
7.8.1 Principles............................................................................................................................................................................ 223
7.8.2.1 Benefits............................................................................................................................................................................225
7.8.2.2 Impacts............................................................................................................................................................................ 227
7.8.3 Requirements.................................................................................................................................................................... 229
7.8.3.1 Licenses........................................................................................................................................................................... 229
7.8.3.2 Software.......................................................................................................................................................................... 229
7.8.3.3 Hardware........................................................................................................................................................................ 230
7.9 MU Beamforming Pairing of Antenna Selection UEs in Dual-Stream Beamforming.................................234
Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. ix

eRAN
7.9.1 Principles............................................................................................................................................................................ 234

7.9.2.1 Benefits............................................................................................................................................................................235
7.9.2.2 Impacts............................................................................................................................................................................ 236
7.9.3 Requirements.................................................................................................................................................................... 238
7.9.3.1 Licenses........................................................................................................................................................................... 238
7.9.3.2 Software.......................................................................................................................................................................... 238
7.9.3.3 Hardware........................................................................................................................................................................ 239
7.9.3.4 Others.............................................................................................................................................................................. 239
7.10 Access Control Optimization Based on Uplink and Downlink User-Perceived Rates............................... 244
7.10.1 Principles.......................................................................................................................................................................... 244
7.10.2 Network Analysis.......................................................................................................................................................... 244
7.10.2.1 Benefits......................................................................................................................................................................... 244
7.10.2.2 Impacts......................................................................................................................................................................... 244
7.10.3 Requirements................................................................................................................................................................. 244
7.10.3.1 Licenses......................................................................................................................................................................... 244
7.10.3.2 Software....................................................................................................................................................................... 244
7.10.3.3 Hardware......................................................................................................................................................................246
7.10.4 Operation and Maintenance.....................................................................................................................................246
7.10.4.1 Data Configuration................................................................................................................................................... 246
7.10.4.1.1 Data Preparation.................................................................................................................................................... 246
7.10.4.1.2 Using MML Commands....................................................................................................................................... 247
7.10.4.1.3 Using the MAE-Deployment.............................................................................................................................. 247
7.10.4.2 Activation Verification............................................................................................................................................. 247
7.10.4.3 Network Monitoring................................................................................................................................................ 248
7.11 PDCCH Resource Reservation for Large-Packet Services in Heavy-Load Scenarios..................................248
7.11.1 Principles.......................................................................................................................................................................... 248
7.11.2.1 Benefits......................................................................................................................................................................... 248
7.11.2.2 Impacts......................................................................................................................................................................... 249
7.11.3 Requirements................................................................................................................................................................. 249
7.11.3.1 Licenses......................................................................................................................................................................... 249
7.11.3.2 Software....................................................................................................................................................................... 249
7.11.3.3 Hardware......................................................................................................................................................................250
Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. x

eRAN

7.12 Optimized PDCCH Aggregation Level Selection Near the Cell Center..........................................................251
7.12.1 Principles.......................................................................................................................................................................... 251
7.12.2.1 Benefits......................................................................................................................................................................... 251
7.12.2.2 Impacts......................................................................................................................................................................... 252
7.12.3 Requirements................................................................................................................................................................. 252
7.12.3.1 Licenses......................................................................................................................................................................... 252
7.12.3.2 Software....................................................................................................................................................................... 252
7.12.3.3 Hardware......................................................................................................................................................................252
7.13 Intelligent Selection of Massive MIMO Parameters.............................................................................................253
7.13.1 Principles.......................................................................................................................................................................... 254
7.13.2 Automatic Assurance Scenarios............................................................................................................................... 258
7.13.2.1 PDCCH Capacity Enhancement............................................................................................................................ 258
7.13.2.2 Uplink Interference Optimization........................................................................................................................ 262
7.13.2.3 Adaptive Overload Optimization......................................................................................................................... 266
7.13.2.4 MLB Parameter Optimization............................................................................................................................... 267
7.13.2.5 RS Adaptation.............................................................................................................................................................268
7.13.3.1 Benefits......................................................................................................................................................................... 271
7.13.3.2 Impacts......................................................................................................................................................................... 271
7.13.4 Requirements................................................................................................................................................................. 271
7.13.4.1 Licenses......................................................................................................................................................................... 272
7.13.4.2 Software....................................................................................................................................................................... 272
7.13.4.3 Hardware......................................................................................................................................................................272
Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. xi

eRAN

7.14 Massive MIMO MU Beamforming Power Enhancement (Trial)...................................................................... 276
7.14.1 Principles.......................................................................................................................................................................... 276
7.14.2.1 Benefits......................................................................................................................................................................... 276
7.14.2.2 Impacts......................................................................................................................................................................... 277
7.14.3 Requirements................................................................................................................................................................. 277
7.14.3.1 Licenses......................................................................................................................................................................... 277
7.14.3.2 Software....................................................................................................................................................................... 277
7.14.3.3 Hardware......................................................................................................................................................................278
7.15 SRS-Expansion-based Precise Beamforming...........................................................................................................279
7.15.1 Principles.......................................................................................................................................................................... 279
7.15.2.1 Benefits......................................................................................................................................................................... 280
7.15.2.2 Impacts......................................................................................................................................................................... 280
7.15.3 Requirements................................................................................................................................................................. 283
7.15.3.1 Licenses......................................................................................................................................................................... 283
7.15.3.2 Software....................................................................................................................................................................... 283
7.15.3.3 Hardware......................................................................................................................................................................285
8 Parameters............................................................................................................................288
9 Counters................................................................................................................................ 289
10 Glossary............................................................................................................................... 290
11 Reference Documents...................................................................................................... 291
Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. xii

eRAN
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:
● Technical changes
Changes in functions and their corresponding parameters
● Editorial changes
Improvements or revisions to the documentation
1.1 eRAN16.1 13 (2021-08-13)

This issue includes the following changes.
Technical Changes
None
Editorial Changes
Added descriptions of the hardware requirements of massive MIMO. For details,
see 4.3.3 Hardware.
Added descriptions of the mutually exclusive relationship between massive MIMO

and RF channel intelligent shutdown. For details, see 4.3.2 Software.
Revised the setting notes for the BfAnt.TILT parameter. For details, see 4.4.1.1
Data Preparation.
1.2 eRAN16.1 12 (2021-05-07)

Technical Changes
None
Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. 1

eRAN
Editorial Changes
Added an impact relationship between massive MIMO and cell-level CPRI
compression. For details, see 4.2.2 Impacts.
Recommended that the PCCHCfg.DefaultPagingCycle parameter be set in eCPRI

scenarios. For details, see 4.4.1.1 Data Preparation and 4.4.1.2 Using MML
Commands.
Revised descriptions in 6.1.1 Principles and 6.2.1.1 Overview.
Added a mutually exclusive relationship between correlation-based cluster pairing

optimization and downlink 24-layer MU beamforming (trial). For details, see
6.2.3.2 Software.
Revised descriptions of the network impacts of uplink pairing optimization. For

details, see 7.7.2.2 Impacts.
Revised descriptions of IRC hardware requirements. For details, see 7.7.3.3

Hardware.
1.3 eRAN16.1 11 (2021-02-28)

Technical Changes
Change Description Parameter Change Base Station Model
Enabled the AAU5636 to None 3900 and 5900 series

support massive MIMO, base stations
and added coverage
scenario patterns for the
AAU5636. For details, see
4.4.1.1 Data
Preparation.
Editorial Changes
Revised descriptions in 4.4.1.2 Using MML Commands.
Revised descriptions of the license for 32T32R Massive MIMO Basic Package. For
details, see 5.2.3.1 Licenses.
Revised descriptions of the network impacts of load-based TMA optimization. For

details, see 6.7.2.1 Benefits.
1.4 eRAN16.1 10 (2021-01-14)


eRAN
Technical Changes
None
Editorial Changes
Revised the description of hardware requirements of massive MIMO. For details,
see 4.3.3 Hardware.
1.5 eRAN16.1 09 (2020-12-30)

Technical Changes
None
Editorial Changes
Revised the description of the principles of TM9 hybrid precoding. For details, see
6.4.1 Principles.
Revised the description of network monitoring for TM9 hybrid precoding. For
details, see 6.4.4.3 Network Monitoring.
Deleted the description of 8-port TM9 hybrid precoding.
Deleted the description of differentiated processing for special 4R UEs.
1.6 eRAN16.1 08 (2020-12-08)

Technical Changes
None
Editorial Changes
Added a mutually exclusive relationship between the TM9 hybrid precoding
function and the CSI-RS period parameter. For details, see 6.4.3.2 Software.
Added an impact relationship between SRS interference avoidance and SRS
resource allocation optimization for interference avoidance. For details, see 7.4.2.2
Impacts.
Added the principle description of intelligent selection of massive MIMO
parameters. For details, see 7.13.1 Principles.
1.7 eRAN16.1 07 (2020-10-31)


eRAN
Technical Changes
None
Editorial Changes
Revised the descriptions of benefits, license, and software for TM9. For details, see
6.3.2.1 Benefits, 6.3.3.1 Licenses, and 6.3.3.2 Software.
Added the impact relationship between TM9 hybrid precoding and TM9 port 5. For
Added the description of mutually exclusive functions of multi-user split SDMA.
For details, see 6.5.3.2 Software.
Added the impact relationship between optimized switching to TM7 in multi-layer
pairing scenarios and TM9 port 5. For details, see 6.7.2.2 Impacts.
Added the impact relationship between switching to TM7 in multi-layer pairing
scenarios and TM9 port 5. For details, see 6.7.2.2 Impacts.
Added the impact relationship between heavy-load TMA boost and TM9 port 5.
For details, see 6.7.2.2 Impacts.
Added the benefits of SRS power control optimization. For details, see 7.4.2.1
Benefits.
Added the impact relationship between MU Beamforming Pairing of Antenna
Selection UEs in Dual-Stream Beamforming and TM9 port 5. For details, see
7.9.2.2 Impacts.
1.8 eRAN16.1 06 (2020-09-29)

Technical Changes
None
Editorial Changes
Revised the description of SRS interference joint suppression. For details, see 7.4
SRS Interference Joint Suppression.
1.9 eRAN16.1 05 (2020-08-31)


eRAN
Technical Changes
Enabled the UBBPg3b to None 3900 and 5900 series

support SRS-expansion- base stations
based precise
beamforming. For details,
see 7.15.3.3 Hardware.
Editorial Changes
Modified the vertical beamwidths indicated by weight indexes 14 to 17 for
different AAU coverage scenarios. For details, see 4.4.1.1 Data Preparation.
Revised the description of hardware requirements of massive MIMO. For details,
see 4.3.3 Hardware.
Added the description of the network impacts of resource randomization in MU-
MIMO enhancement. For details, see 5.2.2.2 Impacts.
Added hardware requirements for TM9 hybrid precoding. For details, see 6.4.3.3
Hardware.
Added hardware requirements for multi-user split SDMA. For details, see 6.5.3.3
Hardware.
Added hardware requirements for PDCCH SDMA. For details, see 6.6.3.3
Hardware.
Added hardware requirements for SRS IC. For details, see 7.4.3.3 Hardware.
1.10 eRAN16.1 04 (2020-07-29)

Technical Changes
Enabled the UBBPg3b to None 3900 and 5900 series

support massive MIMO. base stations
For details, see 4.3.3
Hardware.
Editorial Changes
Added the hardware requirements of 4-layer MIMO based on TM9 and SRS
measurement. For details, see 6.3.3.3 Hardware.
Added parameters used for optimization of TM9 hybrid precoding. For details, see
6.4.4.1 Data Configuration.

eRAN
Revised the description of the principles of load-based TMA optimization. For

details, see 6.7.1.3 Optimized TMA.
Added the description of the network impacts of uplink pairing optimization. For
1.11 eRAN16.1 03 (2020-07-03)

Technical Changes
Enabled the AAU5636w None 3900 and 5900 series

to support massive base stations
MIMO and added the
coverage scenarios of the
AAU5636w. For details,
see 4.4.1.1 Data
Preparation.
Editorial Changes
Added the horizontal and vertical beamwidths indicated by weight indexes 14 and
15 for AAU coverage scenarios. For details, see 4.4.1.1 Data Preparation.
Updated the prerequisite functions of downlink 2-layer MIMO based on TM9. For
details, see 6.3.3.2 Software.
Revised the description of the principles of TM8-excluded adaptation. For details,
see 6.7.1.3 Optimized TMA.
Added the prerequisite functions space-domain measurement and SINR-based
adaptive SRS power control for SRS power control optimization. For details, see
7.4.3.2 Software.
Revised the description of beamforming cell-level initial CQI adjustment value
optimization in terms of principles, benefits, and impacts. For details, see 7.8.1
Principles, 7.8.2.1 Benefits, and 7.8.2.2 Impacts.
Added the impact of downlink RB scheduling proportion limitation for SU
beamforming UEs on downlink user-perceived rates. For details, see 7.8.2.2
Impacts.
1.12 eRAN16.1 02 (2020-05-20)

Technical Changes
None

eRAN
Editorial Changes
Added setting notes for the BfAnt.CoverageScenario parameter. For details, see
4.4.1.1 Data Preparation.
Revised the description of data configuration for service-based dynamic SRS

allocation. For details, see 4.4.1.1 Data Preparation and 4.4.1.2 Using MML
Commands.
Revised the description of the mutually exclusive functions of TM9. For details, see
6.3.3.2 Software.
Revised the description of the mutually exclusive functions of TM9 hybrid

precoding. For details, see 6.4.3.2 Software.
Added the description of the network impacts of TM9 hybrid precoding. For
Added the description of the network impacts of PDCCH SDMA. For details, see
6.6.2.2 Impacts.
Revised the description of the principles of optimized TMA for 4R and 8R UEs as
well as TM8-excluded adaptation. For details, see 6.7.1.3 Optimized TMA.
Added the description of the network impacts of PDCCH resource reservation for
large-packet services in heavy-load scenarios. For details, see 7.11.2.2 Impacts.
Revised the description of the function impacts of SRS-expansion-based precise

beamforming on carrier aggregation. For details, see 7.15.2.2 Impacts.
1.13 eRAN16.1 01 (2020-04-07)

Technical Changes
Added hardware None 3900 and 5900 series

requirements of 8-port base stations
TM9 hybrid precoding in
eCPRI scenarios. For
details, see 6.4.3.3
Hardware.
Deleted the UBBPg3a None 3900 and 5900 series

board from 4.3.3 base stations
Hardware.
Enabled the AAU5639 to None 3900 and 5900 series

support downlink 8x8 base stations
MIMO. For details, see
6.3.3.3 Hardware.

eRAN
Editorial Changes
Described the impacts of the "4-layer MIMO based on TM9 and SRS
measurement" function on downlink 2CC aggregation. For details, see 6.3.2.2
Impacts.
Described TM9w/oPMI in TMA mode. For details, see 6.7.1.2 TMA Principles.
Added the description of the prerequisite functions of PDCCH resource reservation

for large-packet services in heavy-load scenarios. For details, see 7.11.3.2
Software.
Added the description of the network impacts of PDCCH resource reservation for
large-packet services in heavy-load scenarios. For details, see 7.11.2.2 Impacts.
Described the network impacts of SRS-extension-based precise beamforming. For

details, see Network Impacts.
1.14 eRAN16.1 Draft C (2020-03-30)

Technical Changes
None
Editorial Changes
Revised the description of the principles of differentiated processing for special 4R
UEs and the corresponding MML command examples.
Revised descriptions in this document.
1.15 eRAN16.1 Draft B (2020-03-10)

Technical Changes
Added TDLAOFD-130490 None 3900 and 5900 series

DL 8x8 MIMO. For base stations
details, see 6.3 TM9.
Added differentiated Modified parameters: 3900 and 5900 series

processing for special 4R Added the base stations
UEs. 8PORT_CSI_RS_SWITCH
_ON option to the
UeCompat.WhiteLstCtrl
Switch parameter.

eRAN
Editorial Changes
Modified the UE requirements of downlink 4-layer MIMO based on TM9 and SRS
measurement. For details, see 6.3.3.4 Others.
Revised the description of 8-port TM9 hybrid precoding configuration using MML
commands. For details, see 6.4.4.1.2 Using MML Commands.
Added the beneficial scenarios of PDCCH resource reservation for large-packet
services in heavy-load scenarios. For details, see 7.11.2.1 Benefits.
1.16 eRAN16.1 Draft A (2020-01-20)

This issue introduces the following changes to eRAN15.1 03 (2019-07-20).
Technical Changes
Added the mutually None 3900 and 5900 series

exclusive relationship base stations
between LTE and NR
power sharing and
PDCCH SDMA
enhancement. For
Software.
Added beam coverage Modified parameters: 3900 and 5900 series

scenarios, that is, added Added enumerated base stations
enumerated values to the values SCENARIO_14,
BfAnt.CoverageScenario SCENARIO_15,
parameter and added the SCENARIO_16, and
setting notes for the SCENARIO_17 to the
BfAnt.BFANTBEARING BfAnt.CoverageScenari
parameter. For details, o parameter.
see 4.4.1.1 Data
Preparation.
Enabled the UBBPg3a to None 3900 and 5900 series

Hardware.
Enabled the UMPTga to None 3900 and 5900 series

Hardware.

eRAN
Added 4-layer MIMO Modified parameters: 3900 and 5900 series

based on TM9 and SRS Added the enumerated base stations
measurement. For value FOUR_LAYER_BF
details, see 6.3 TM9. to the
CellBf.MaxBfRankPara
parameter.
Added optimized Modified parameters: 3900 and 5900 series

switching to TM7 in Added the base stations
multi-layer pairing INCREASE_SM_LAYER_T
scenarios. For details, see MA_OPT_SW option to
6.7.1.3 Optimized TMA. the
CellBfMimoParaCfg.Bf
MimoAlgoOptSwitch
parameter.
Added 8-port TM9 hybrid Modified parameters: 3900 and 5900 series
precoding. For details, ● Added the base stations
see 6.4 TM9 Hybrid enumerated value
Precoding. CONFIG_INDEX4 to
the
CellBf.PdschSplitBea
mConfigIndex
parameter.
● Added the
enumerated value
CSI_RS_PORT_8 to
the
CellCsiRsParaCfg.Csi
RsPortNum
parameter.
Added the support for None 3900 and 5900 series

setting up both massive base stations
MIMO cells and common
cells on the same
UBBPg2a. For details, see
4.3.3 Hardware.
Added downlink RB Added parameters: 3900 and 5900 series

scheduling proportion CellMMAlgo.DlSubfPrb base stations
limitation for SU UsageRestrThld
beamforming UEs. For
details, see 7.8
Scheduling
Optimization.

eRAN
Added SRS-expansion- Added parameters: 3900 and 5900 series

based precise SRSCfg.SrsResExpansio base stations
beamforming. For details, nSwitch
see 7.15 SRS-Expansion-
based Precise
Beamforming.
Added massive MIMO Modified parameters: 3900 and 5900 series

MU beamforming power Added the base stations
enhancement. For MUBF_PWR_ENH_SW
details, see 7.14 Massive option to the
MIMO MU CellMMAlgo.PreciseMu
Beamforming Power bfOptSwitch parameter.
Enhancement (Trial).
Changed the name of None 3900 and 5900 series

U2020 to MAE-Access base stations
and the name of CME to
MAE-Deployment.
Added a switch to specify Added parameters: 3900 and 5900 series

whether to allocate RBs CellMimoParaCfg.RanS base stations
to operators in haringSchOptSwitch
proportion in multi-user
pairing scenarios. For
details about the impacts
of this switch in MU-
MIMO and MU
beamforming scenarios,
see:
● 5.2.2.2 Impacts
● 6.2.2.2 Impacts
Removed the mutually None 3900 and 5900 series

exclusive relationship base stations
between massive MIMO
introduction and the
interference detection
and suppression function.
Software.

eRAN
Stated that the None 3900 and 5900 series

SPLIT_SDMA_SCHEME base stations
value of the
CellBf.MovingUeMuBfSc
heme parameter can
take effect only when the
SRS_LMT_AND_ABN_UE
_IDENT_SW option of
the
CellBf.UeIdentificationS
witch parameter is
selected. For details, see
6.5.4.1.1 Data
Preparation.
Stated that the None 3900 and 5900 series

HIGH_SPEED_OPT_SCHE base stations
ME value of the
heme parameter and the
BIG_EVENT_PROTECT_S
CHEME value of the
heme parameter can
take effect only when the
SRS_LMT_AND_ABN_UE
_IDENT_SW option of
the
CellBf.UeIdentificationS
witch parameter is
selected. For details, see
6.2.1.3 Scheduling
Optimizations for MU
Beamforming.

eRAN
Added PDCCH SDMA Modified parameters: 3900 and 5900 series

enhancement. For ● Added the base stations
details, see 6.6 PDCCH POWER_SHARING_A
SDMA . MONG_5_BEAMS,
POWER_SHARING_A
MONG_4_BEAMS,
and
POWER_SHARING_A
MONG_3_BEAMS
values to the
CellPdcchAlgo.Pdcch
SdmaWeightType
parameter.
● Added the
MASSIVE_MIMO_PD
CCH_MEAS_SW
option to the
CellPdcchAlgo.SplitB
eamPdcchSdmaSw
parameter.
Enabled the BBU5900A None 5900 series base stations

to support massive
MIMO. For details, see
4.3.3 Hardware.
Added counters for MU None 3900 and 5900 series

beamforming to the base stations
"Proportions of Non-
Paired UEs and Paired
UEs in the Downlink"
function subset. For
Network Monitoring.
Changed the beam None 3900 and 5900 series

weight database base stations
activation mode, no
longer using an MML
command. For details,
see 4.4.1 Data
Configuration.
Added uplink MU-MIMO Modified parameters: 3900 and 5900 series

pairing optimization. For Added the base stations
details, see 5.2 MU- MMVmimoUePairin-
MIMO. gOptSw option to the
CellUlschAlgo.VmimoO
ptAlgoSwitch
parameter.

eRAN
Changed Intelligent Modified parameters: 3900 and 5900 series

Selection of Massive Added the base stations
MIMO Parameters from BIG_EVENT_AUTO_ASS
a trial feature to a URANCE_SW option to
commercial feature. the
Added the following CellMMAlgo.MmParam
application scenarios: IntelSelectSw
uplink interference parameter. The
optimization, adaptive BIG_EVENT_PDCCH_CA
overload optimization, PC_ADAPT_SW option
MLB optimization, and will be disused in later
RS adaptation. For versions.
details, see 7.13
Intelligent Selection of Added parameters:
Massive MIMO ● CellMMAlgo.MmPar
Parameters. amIntelSelectDlUxT
hld
● CellMMAlgo.MmPar
amIntelSelectUlUxT
hld
Added optimization of Modified parameters: 3900 and 5900 series
enhanced symbol Added the enumerated base stations
adaptation. For details, value
see 7.2 PDCCH Capacity MM_HEAVY_LOAD_ECFI
Improvement. _ADAPT_ON to the
CellPdcchAlgo.PdcchSy
mNumSwitch
parameter.
Added downlink Modified parameters: 3900 and 5900 series

correlation-based UE Added the base stations
pairing optimization. For DL_CORR_UE_PAIRING_
details, see 7.8 OPT_SWITCH option to
Scheduling the
Optimization. CellMMAlgo.MMAlgoO
ptSwitch parameter.
Added downlink low- Added parameters: 3900 and 5900 series
SRS-SINR UE pairing CellMMAlgo.LowSrsSin base stations
optimization. For details, rUePairLayerThld
see 7.8 Scheduling
Optimization.

eRAN
Added load-based TMA Modified parameters: 3900 and 5900 series

optimization. For details, Added the base stations
see 6.7.1.3 Optimized LOAD_BASED_TMA_OP
TMA. T_SW option to the
CellBfMimoParaCfg.Bf
MimoAlgoOptSwitch
parameter
Enabled the uplink None 3900 and 5900 series

receive enhancement base stations
function to be used in
eCPRI networking with
64 antennas. For details,
see 7.7.3.3 Hardware.
Modified information None 3900 and 5900 series

related to the base stations
L.ChMeas.PRB.UL.PttUse
d.Avg.PLMN and
L.ChMeas.PRB.DL.PttUse
d.Avg.PLMN counters,
which are disused from
eRAN16.0.
Modified information Deleted parameters: 3900 and 5900 series

related to the Cell.EmergencyAreaIdC base stations
Cell.EmergencyAreaIdCf fgInd
gInd parameter, which is
disused from eRAN16.0.
Editorial Changes
● Revised the RF module requirements. For details, see 4.3.3 Hardware.
● Revised the beneficial scenarios of PDCCH SDMA. For details, see 6.6.2.1
Benefits.
● Changed the CellBf.HeavyLoadSwitchToBfOpt parameter value
recommended for optimized switching to beamforming in heavy-load
scenarios. For details, see 6.7.4.1.2 Using MML Commands.
● Updated the hardware requirements for PDCCH SDMA enhancement. For
details, see 6.6.3.3 Hardware.
● Added formulas for calculating the equivalent CCE usage with CFIs fixed to 3.
For details, see the sections related to this indicator.
● Revised the description of the principles of intelligent selection of massive
MIMO parameters. For details, see 7.13.1 Principles.

eRAN
Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
This document is intended to acquaint readers with:
● The technical principles of features and their related parameters

● The scenarios where these features are used, the benefits they provide, and
the impact they have on networks and functions
● Requirements of the operating environment that must be met before feature
activation
● 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.
2.2 Applicable RAT

This document applies to TDD.
2.3 Features in This Document

This document describes the following TDD features.

eRAN
Feature ID Feature Name Chapter/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
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-151611 32T32R Massive MIMO See the corresponding

Basic Package sections of the
subfeatures.
TDLEOFD-15161101 UL 32-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-15161102 UL 2x32 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

eRAN
Feature ID Feature Name Chapter/Section

Beamforming (Trial)
TDLAOFD-00100114 DL 2-Layer MIMO Based 6.3 TM9

on TM9
TDLAOFD-081409 DL 4-Layer MIMO Based 6.3 TM9

on TM9
TDLAOFD-130490 DL 8x8 MIMO 6.3 TM9
TDLEOFD-131615 Massive MIMO TM9 6.4 TM9 Hybrid

Hybrid Precoding 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

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

Joint Suppression
TDLEOFD-150613 Advanced Massive MIMO 7.7 IRC

IRC
TDLEOFD-151616 Intelligent Selection of 7.13 Intelligent

Massive MIMO Selection of Massive
Parameters MIMO Parameters
TDLEOFD-161601 Precise Beamforming 7.15 SRS-Expansion-

with SRS Expansion based Precise
Beamforming
NOTE
The features described in 4 Basic Massive MIMO Functions and 5.1 Receive Diversity are
prerequisites for setting up massive MIMO cells. Operation and maintenance of the features
are described in 4.4 Operation and Maintenance.
Massive MIMO optimization in WTTx scenarios involves the following features. For details,
see Massive MIMO Optimization in WTTx Scenarios (TDD).
● TDLEOFD-150602 WTTx Pairing Enhancement
● TDLEOFD-151608 SRS Antenna Selection in Massive MIMO
● TDLEOFD-151609 SRS Interference Avoidance

eRAN
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 antennas to perform 3D beamforming
and multi-layer multi-user resource 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
Table 3-1 Function evolution from traditional MIMO to massive MIMO
Category Traditional MIMO Massive MIMO
Uplink multiple-antenna Up to eight antennas can Up to 32 or 64 antennas

receive diversity (receive be used for uplink can be used for uplink
diversity for short) receive diversity. receive diversity.
Uplink multi-user MIMO Up to four layers can Up to eight layers can

(MU-MIMO for short) share the same resource. share the same resource.

eRAN
Broadcast beamforming Beamwidths can be Beamwidths can be

adjusted only on the adjusted on both the
horizontal plane. horizontal and vertical
planes, improving
vertical-plane network
coverage.
Downlink single-user Traffic beamwidth can Traffic beamwidth can

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

beamforming (MU share the same resource. share the same resource.
beamforming for short) (24 layers are available
only for trial.)
TM9 hybrid precoding Wide beam weighting, ● Horizontal-plane

which performs weighting: One beam
beamforming based on is divided into
the precoding matrix multiple orthogonal
indication (PMI) beams. Each beam is
feedback of the UE configured with
independent,
measurable channel
state information-
reference signal (CSI-
RS). The eNodeB
selects the weights
with the best
beamforming
capability based on
the channel state.
● Vertical-plane
weighting:
Beamforming is
performed based on
PMI feedback.
Multi-user split SDMA None Physical downlink shared

channel (PDSCH) beams
are split, enabling
independently scheduled
UEs served by different
PDSCH beams to share
the same PDSCH
resource for data
transmission.

eRAN
PDCCH SDMA None Physical downlink

control channel (PDCCH)
beams are split, enabling
independently scheduled
UEs served by different
PDCCH beams to share
the same PDCCH
resource for data
transmission.
NOTE
For details about traditional MIMO, see MIMO and Beamforming (TDD).
3.2 Application Scenarios

Massive MIMO is mainly used to improve cell coverage and capacity. It can be
deployed on a new site or a reconstructed site. It is typically deployed to cover
hotspot areas and tall buildings.
● Hotspot areas
In typical hotspot areas, UE density is high and many online UEs create
extremely strong demands for capacity in both the uplink and the downlink.
Typical hotspot areas include dense urban areas, central business districts
(CBDs), public squares, and stadiums.
Massive MIMO improves capacity through spatial multiplexing. Up to 8 layers
in the uplink for MU-MIMO and up to 16 layers in the downlink for MU
beamforming significantly improve cell throughput and meet capacity
demands in hotspot areas.
● Tall buildings
In tall buildings, UEs 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 horizontally and vertically adjusts broadcast beams, enhancing
vertical coverage. 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 effectively offset propagation loss and penetration loss,
improving link quality for UEs in tall buildings.

eRAN
Figure 3-2 Coverage for tall buildings

eRAN
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. 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 17° (in 32T32R
scenarios) or 35° (in 64T64R scenarios) significantly improves the vertical coverage
scope. The horizontal and vertical beamwidths may vary depending on the AAU
model. For details, see Table 4-2.
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.

eRAN
TDLEOFD-12160101 Flexible Active-Unit Management

To enhance system reliability, the following flexible active-unit management policy
is supported in massive MIMO scenarios:
● The cell can still work properly as long as 16 (in 32T32R scenarios) or 32 (in
64T64R scenarios) 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.
● If fewer than 16 (in 32T32R scenarios) or 32 (in 64T64R scenarios) antennas
are operational, the massive MIMO cell is deactivated.
● If more than 4 (in 32T32R scenarios) or 8 (in 64T64R scenarios) antennas are
faulty, neither PDCCH SDMA nor multi-user split SDMA takes effect in
massive MIMO.
MIMO cells.
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

transmission mode adaptation (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. This
saves short-period SRS resources and enables the eNodeB to 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 of the

SRSCfg.SrsCfgPolicySwitch parameter. When this option is selected, the massive
MIMO cell identifies UE service types and then reserves short-period SRS resources
for UEs that are performing heavy-traffic services. The reserved SRS resources are
not available for UEs that initially access the network or perform heartbeat
services.
Heartbeat, heavy-traffic, and normal services are identified as follows:
● Heartbeat services

eRAN
Heartbeat services include periodic 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 size of any IP packet transmitted within 2s after a Radio Resource
Control (RRC) connection setup does not exceed the threshold specified
by the ServiceIdentifyPara.HeartbeatPacketLengthThld parameter.
– The total number of IP packets transmitted within 2s after an RRC
connection setup does not exceed the threshold specified by the
ServiceIdentifyPara.HeartbeatPacketNumberThld parameter.
● Heavy-traffic services
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:
– The proportion of downlink large IP packets is greater than the threshold
specified by the ServiceIdentifyPara.MassFlowBigPacketRateThld
parameter.
– The total number of downlink IP packets is greater than the threshold
specified by the ServiceIdentifyPara.MassFlowPacketNumberThld
parameter.
● Normal services
All other services are considered normal services.
TDLEOFD-12160104 Power Beamforming

Power beamforming supports amplitude adjustment based on beam weights in
massive MIMO scenarios. The eNodeB calculates the weights 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-perceived rate.
MIMO cells.
4.2 Network Analysis
4.2.1 Benefits
This feature achieves more power gains and array gains, and increases the average
cell capacity, peak cell throughput, average single-UE throughput, and cell edge
UE (CEU) throughput in the uplink and downlink.
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.

eRAN
NOTE
● For details about the power and array gains, see Beamforming (TDD).
● 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
● Massive MIMO cells have a larger target SRS power for SRS power control
than common cells. This increases the downlink spectral efficiency and cell
throughput but also increases SRS interference.
● In massive MIMO scenarios, the values of the counters with IDs ranging from
1526746778 to 1526746789 are invalid.
● In massive MIMO scenarios, the values of all the following items of TDD
interference detection monitoring on the MAE-Access are invalid:
– Average of Receive Power of All UL Symbols(dBm)
– Receive Power of Symbol 1 in First UL Subframe(dBm) to Receive
Power of Symbol 5 in First UL Subframe(dBm)
– Receive Power of Symbol 7 in the Last UL Subframe(dBm) to Receive
Power of Symbol 10 in the Last UL Subframe(dBm)
– Receive Power of Symbol 12 in the Last UL Subframe(dBm) and
Receive Power of Symbol 13 in the Last UL Subframe(dBm)
NOTE
If the ACT BFANTDB command is not executed to activate the weight file in the software
package in eRAN15.1 or earlier, the weight file will be automatically activated and take
effect after an upgrade to eRAN16.0. In this case, if the weight values of cells change,
network KPIs will also change.
Function Impacts
Function Name Function Switch Reference Description
DL CoMP cell IntraDlCompSwit DL CoMP (TDD) Massive MIMO

ch option of the cells cannot be
CellAlgoSwitch.D added to intra-
lCompSwitch eNodeB downlink
parameter coordinated
multipoint
transmission (DL
CoMP) clusters.

eRAN
Inter-eNodeB DL InterDlCompDcsS DL CoMP (TDD) Only the dynamic

CoMP witch and cell selection
InterDlCompCbfS (DCS) mode is
witch options of available for inter-
the eNodeB DL CoMP
CellAlgoSwitch.D in massive MIMO
lCompSwitch scenarios.
parameter
MCS selection for SmallPktMcsSele Scheduling Modulation and

transmission of ctAlgoSw option coding scheme
small amounts of of the (MCS) index
data CellAlgoSwitch.D selection for
lSchSwitch transmission of
parameter small amounts of
data does not
take effect for
UEs that have
been paired for
massive MIMO.

eRAN
Cell-level CPRI Cell.CPRICompres CPRI Compression Based on the BBP

compression sion requirements of
massive MIMO
provided in 4.3.3
Hardware, it is
recommended
that the CPRI
compression
parameters be set
as follows:
● If an AAU is
connected to a
UBBPg2a/
UBBPg3b/
UBBPg3, set
this parameter
to
NO_COMPRES
SION.
● If an AAU is
connected to a
UBBPf3/
UBBPg3b/
UBBPfw1, set
this parameter
to
NO_COMPRES
SION.
● If an AAU is
connected to a
UBBPf1/
UBBPg4, set
this parameter
to
NORMAL_CO
MPRESSION or
ENHANCED_C
OMPRESSION.
● If an AAU is
connected to a
UBBPem:
– Set this
parameter
to
NORMAL_C
OMPRESSI
ON in 10
MHz cells.

eRAN
– Set this
parameter
to
ENHANCED
_COMPRES
SION in 15
MHz cells.
– Set this
parameter
to
ENHANCED
_COMPRES
SION in 20
MHz cells.
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 required by a massive MIMO cell, see License
Management.
4.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.

eRAN
Prerequisite Functions
Subframe Cell.SpecialSubfr Subframe Massive MIMO

configuration amePatterns Configuration cells support only
Cell.SubframeAss (TDD) the following
ignment subframe
configuration
combinations:
uplink-downlink
subframe
configuration 2 +
special subframe
configuration 5,
uplink-downlink
subframe
configuration 2 +
special subframe
configuration 6,
uplink-downlink
subframe
configuration 1 +
special subframe
configuration 7,
and uplink-
downlink
subframe
configuration 2 +
special subframe
configuration 7.
Only the UBBPem
supports uplink-
downlink
subframe
configuration 1.
Only the
AAU5613 and
AAU5614 support
uplink-downlink
subframe
configuration 2 +
special subframe
configuration 6.

eRAN
Mutually Exclusive Functions

Extended CP Cell.UlCyclicPrefi Extended CP None

x
Cell.DlCyclicPrefi
x
TTI bundling TtiBundlingSwitc VoLTE According to
h option of the 3GPP
CellAlgoSwitch.U specifications, TTI
lSchSwitch bundling is not
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.MultiRruCell SFN None

Mode
High speed Cell.HighSpeedFl High Speed None
mobility ag Mobility
eMBMS CellMBMSCfg.MB eMBMS None
MSSwitch
Remote CellRicAlgo.Rem Interference Massive MIMO is
interference oteInfAdpAvoidS Detection and suitable for dense
adaptive witch Suppression urban areas, while
avoidance CellRicAlgo.Duct remote
DLSubfrmShutoff interference
Switch adaptive
avoidance is
CellRicAlgo.Duct applicable in wide
DLSubfrmShutoff coverage
OptSw scenarios.
Intra-eNodeB UL UlCamcSw option Uplink None

CAMC of the Coordinated
CellAlgoSwitch.C Scheduling
amcSwitch
parameter

eRAN
Intra-frequency None Soft Split None

split Resource Duplex
(TDD)
Uplink SU-MIMO ULSUMIMO2Laye MIMO None
rsSwitch option
of the
CellAlgoSwitch.U
lSuMimoAlgoSwi
tch parameter
Downlink D- DmimoJTSwitch D-MIMO (TDD) None
MIMO and
DmimoSchAttriO
ptSwitch options
of the
CellAlgoSwitch.D
MIMOAlgoSwitc
h parameter
Inter-cell InterCellDmimoJ D-MIMO (TDD) None
downlink D- TSwitch option of
MIMO the
CellAlgoSwitch.D
MIMOAlgoSwitc
h 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.T Turbo Receiver None

urboReceiverSwit
ch
UL CoMP cell UlJointReception UL CoMP None
Switch option of
the
CellAlgoSwitch.U
plinkCompSwitch
parameter
ePDCCH CellPdcchAlgo.Ep Physical Channel None

dcchAlgoSwitch Resource
Management

eRAN
eMTC EMTC_SWITCH eMTC None

introduction option of the
CellEmtcAlgo.Em
tcAlgoSwitch
parameter
Turbo TurboBfSwitch WTTx Turbo None

beamforming option of the Beamforming
CellAlgoSwitch. (TDD)
MuBfAlgoSwitch
parameter
In-band relay InBandRelayDeN Relay None

bSwitch and
InBandRelayReN
bSwitch options
of the
CellAlgoSwitch.R
elaySwitch
parameter
Interference Sa1Sa2InterfCoor Subframe None

coordination for dSwitch option of Configuration
cells with uplink- the (TDD)
downlink CellAlgoSwitch.A
subframe voidInterfSwitch
configuration 1 or parameter
2

eRAN
RF channel CellRfShutdown. Energy When RF channel

intelligent RfShutdownSwit Conservation and intelligent
shutdown ch Emission shutdown is
Reduction enabled, the
BfAnt.CoverageS
cenario
parameter cannot
be set to
SCENARIO_13,
EXPANDSCENARI
O_1,
EXPANDSCENARI
O_2, or
EXPANDSCENARI
O_3 in 32T32R
massive MIMO
scenarios.
When RF channel
intelligent
shutdown is
enabled, the
BfAnt.CoverageS
cenario
parameter cannot
be set to
EXPANDSCENARI
O_1,
EXPANDSCENARI
O_2, or
EXPANDSCENARI
O_3 in 64T64R
massive MIMO
scenarios.
4.3.3 Hardware
Base Station Models
3900 and 5900 series base stations
Boards
● BBU: BBU3910/BBU5900/BBU5900A
● BBPs:
– UBBPem (capable of CPRI)
– UBBPf1 (capable of CPRI)
– UBBPf3 (capable of eCPRI)

eRAN
– UBBPfw1 (capable of eCPRI)

– UBBPg2a (capable of eCPRI)
– UBBPg3 (capable of eCPRI)
– UBBPg3b (capable of eCPRI)
– UBBPg4 (capable of CPRI)
● Main control board:
– UMPTe
– UMPTga
– UMPTg
NOTE
● For details about the maximum number of BBPs supported by each BBU, the maximum
number of massive MIMO cells supported by each BBP, and CPRI protocol types, see the
technical description of the corresponding BBU.
● For the CPRI protocol types supported by a BBP, see the hardware description of the
corresponding BBU.
● 32T32R and 64T64R massive MIMO cells cannot be set up on the same UBBPg2a,
UBBPg3b, or UBBPg3.
● Massive MIMO cells and common cells can be set up on the same UBBPg3/UBBPg3b/
UBBPg2a. When 2T2R/4T4R/8T8R and 32T32R/64T64R cells share the same BBP, all
these cells need to be bound to this BBP. If a cell fails to be set up, reset the BBP to
reshuffle resources.
● When a BBU is configured with both eCPRI-capable BBPs and CPRI-capable BBPs or with
both UBBPem/UBBPf1 and UBBPg, it is required that each cell be bound to a BBP and
each BASEBANDEQM MO contain only one board. This prevents cell activation failures
and incorrect license alarms when licensed resources are insufficient.
RF Modules
Only 64T64R AAUs and 32T32R AAUs support massive MIMO cells.
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
Massive MIMO Cell Data

The following lists only the parameter settings that are different from those for
common cell setup. Set the following parameters based on the setting notes.

eRAN
Table 4-1 Massive MIMO cell data

Parameter Name Parameter ID Setting Notes
Protocol Type EQUIPMENT.PROTOC Set this parameter to CPRI.

OL
Board Type BT If a UBBPfw1 is used, set this
parameter to UBBP-W. If
another type of BBP is used,
set this parameter to UBBP.
CPRI Interface Type BBP.CPRIITFTYPE If the BBP supports CPRI, set

this parameter to CPRI_QSFP.
If the BBP supports eCPRI, set
this parameter to CPRI_SFP.
Board Specification BRDSPEC If the BBP is UBBPf1/UBBPg4,

set this parameter to UBBPf1/
UBBPg4. If the parameter is
set to another value, two CPRI
ports are displayed on the
MAE-Deployment device panel
based on the UBBPem but
three CPRI ports should be
displayed.
Topo Type RRUCHAIN.TT Set this parameter to

TRUNK_CHAIN.
Access Type RRUCHAIN.AT Set this parameter to

LOCALPORT.
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

1 port 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

2 port number 2 of the trunk
chain.

eRAN
Protocol Type RRUCHAIN.PROTOCO ● CPRI networking: Set this

L parameter to CPRI.
● 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 RRU.RS Set this parameter to TDL.

Mode
Number of RX RRU.RXNUM Set this parameter to 0.

channels
Number of TX RRU.TXNUM Set this parameter to 0.

channels
Maintenance Mode RRU.MNTMODE Set this parameter to

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

Alarm Detect Switch MDETECTSW
Antenna Number SECTOR.ANTNUM Set this parameter to 0.
Create Default Sector SECTOR.CREATESECT Set this parameter to FALSE.

Equipment OREQM
Antenna Config Mode SECTOREQM.ANTCFG Set this parameter to BEAM.
MODE
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,
Downlink bandwidth Cell.DlBandWidth CELL_BW_N75, or
CELL_BW_N100.
Subframe assignment Cell.SubframeAssign Set this parameter to SA1 or

ment SA2. For details about the
subframe configurations
supported by each BBP, see
4.3.2 Software.

eRAN
Special subframe Cell.SpecialSubframe Set this parameter to SSP5,

patterns Patterns SSP6, or SSP7. For details
about subframe configuration
combinations, see 4.3.2
Software.
CPRI Compression Cell.CPRICompressio Based on the BBP

n requirements of massive
MIMO provided in 4.3.3
Hardware, it is recommended
that the CPRI compression
parameters be set as follows:
● If an AAU is connected to a
UBBPg2a/UBBPg3b/
UBBPg3, set this parameter
to NO_COMPRESSION.
UBBPf3/UBBPg3b/
UBBPfw1, set this
parameter to
NO_COMPRESSION.
UBBPf1/UBBPg4, set this
parameter to
NORMAL_COMPRESSION
or
ENHANCED_COMPRESSIO
N.
UBBPem:
– Set this parameter to
NORMAL_COMPRESSIO
N in 10 MHz cells.
ENHANCED_COMPRESS
ION in 15 MHz cells.
ENHANCED_COMPRESS
ION 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 32T32R

reception mode or 64T64R.
Baseband equipment BASEBANDEQM.BASE None

ID BANDEQMID

eRAN
Baseband Equipment BASEBANDEQM.BASE Set this parameter to ULDL.

Type BANDEQMTYPE
UMTS UL BASEBANDEQM.UMT Set this parameter to NULL.
Demodulation Mode SDEMMODE
Local cell ID eUCellSectorEqm.Loc None
alCellId
Sector equipment ID eUCellSectorEqm.Sec Set this parameter according
torEqmId to the sector equipment ID
configured in the
SECTOREQM MO.
Baseband equipment eUCellSectorEqm.Bas Set this parameter according

ID eBandEqmId to the baseband equipment ID
configured in the
BASEBANDEQM MO.
Default paging cycle PCCHCfg.DefaultPagi The value rf256 is

ngCycle recommended in eCPRI
scenarios.
Broadcast Beam Weight Parameters

Massive MIMO requires the configuration of broadcast beam weights. The MOs
and parameters in the following tables must be configured based on site
conditions.
Table 4-2 Broadcast beam weight parameters

Device No. BfAnt.DEVICENO Set this parameter based on

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

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

number MassiveAntenna.
Tilt BfAnt.TILT Downtilt = BfAnt.TILT + 0.1 x

BfAnt.TiltFractionalPart
For example:
● If the BfAnt.TILT parameter
is set to 1 and the

eRAN
Tilt Fractional Part BfAnt.TiltFractionalP parameter is set to 9, the

art downtilt is 1.9°.
is set to 1 and the
parameter is set to -9, the
downtilt is 0.1°.
is set to -1 and the
parameter is set to 9, the
downtilt is -0.1°.
is set to -1 and the
parameter is set to -9, the
downtilt is -1.9°.
If the
BfAnt.CoverageScenario
parameter is set to
SCENARIO_10 to
SCENARIO_13 (indicating
wide-beam scenarios), the
BfAnt.TILT and
parameters do not need to be
set.
If the BfAnt.TILT parameter is
set to a value within the tilt
range supported by the AAU,
the BfAnt.TILT parameter
value takes effect. If the
parameter is set to a value
greater than the maximum tilt
supported by the AAU, the
maximum tilt takes effect. If
the parameter is set to a value
less than the minimum tilt
supported by the AAU, the
minimum tilt takes effect.
Band BfAnt.Band Set this parameter to the

value of the Cell.FreqBand
parameter.

eRAN
Coverage Scenario BfAnt.CoverageScena The horizontal and vertical

rio beamwidths of each coverage
scenario vary according to
AAU models, and it is
recommended that this
parameter be set based on
coverage. For details, see
Table 4-3 and Table 4-4.
If the range indicated by this
parameter is beyond that
supported by AAU capability,
the actual range is determined
by AAU capability.
The vertical beamwidth of a
massive MIMO antenna is
equivalent to that of a single
channel. The adjustment of
the BfAnt.TILT parameter has
little effect in the following
scenarios:
● In 64T64R scenarios, this
parameter is set to
SCENARIO_10,
SCENARIO_11,
SCENARIO_12, or
SCENARIO_13.
● In 32T32R scenarios, this
parameter is set to
SCENARIO_5,
SCENARIO_6,
SCENARIO_7,
SCENARIO_8, or
SCENARIO_9.
Due to the limited vertical
beamwidth of a single 32T32R
channel, it is not
recommended that this
parameter be set to
SCENARIO_10 to
SCENARIO_13.
Weight Number eUCellSectorEqm.We Set this parameter based on

ightNO the value of the
BfAnt.DEVICENO parameter.
This parameter must not be
set to 255.

eRAN
BFANTBEARING BfAnt.BFANTBEARIN In massive MIMO cells, the

G value range of this parameter
is from -30 to 30.
● The value 0 is
recommended if the
parameter is set to
SCENARIO_1 or
SCENARIO_5.
● A value in the range of -10
to 10 is recommended if
the
parameter is set to
SCENARIO_2,
SCENARIO_6, or
SCENARIO_10.
the
parameter is set to
SCENARIO_3,
SCENARIO_7, or
SCENARIO_11.
the
parameter is set to
SCENARIO_4,
SCENARIO_8,
SCENARIO_9,
SCENARIO_12, or
SCENARIO_13.
● The value 0 is
recommended if the
parameter is set to
SCENARIO_14,
SCENARIO_15,
SCENARIO_16, or
SCENARIO_17.
Table 4-3 lists the horizontal and vertical beamwidths of broadcast beams of the
AAU5271.

eRAN
Table 4-3 Coverage scenario pattern 1
Weight Index Horizontal Vertical Beamwidth

Beamwidth
1 90° 8°
2 65° 8°
3 45° 8°
4 25° 8°
5 90° 17°
6 65° 17°
7 45° 17°
8 25° 17°
9 15° 17°
10 65° 35°
11 45° 35°
12 25° 35°
13 15° 35°
14 100° 8°
15 100° 17°
16 Max 8°
17 Max 17°
Table 4-4 lists the horizontal and vertical beamwidths of broadcast beams of the
AAU5281/AAU5613/AAU5614/AAU5313/AAU5339/AAU5339w/AAU5631/
AAU5639/AAU5639w/AAU5649/AAU5636w/AAU5636.
Table 4-4 Coverage scenario pattern 2

Beamwidth
1 90° 6°
2 65° 6°
3 45° 6°
4 25° 6°
5 90° 12°

eRAN

Beamwidth
6 65° 12°
7 45° 12°
8 25° 12°
9 15° 12°
10 65° 25°
11 45° 25°
12 25° 25°
13 15° 25°
14 100° 6°
15 100° 12°
16 Max 6°
17 Max 12°
Note: "Max" indicates the maximum horizontal beamwidth supported by the

antenna.
Dynamic SRS Allocation Parameters
Table 4-5 Dynamic SRS allocation parameters

SRS Configure Policy SRSCfg.SrsCfgPolicyS To enable service-based

Switch witch dynamic SRS allocation, select
the SrvBasedSRSAdjAlgo
option.
Heartbeat Packet ServiceIdentify- If this parameter is set to a

Length Threshold Para.HeartbeatPacke small value, a small number
tLengthThld of services are identified as
heartbeat services. The value
180 is recommended.
Heartbeat Packet ServiceIdentify- If this parameter is set to a

Number Threshold Para.HeartbeatPacke small value, a small number
tNumberThld of services are identified as
heartbeat services. The value 4
is recommended.

eRAN
Mass Flow Monitor ServiceIdentify- If this parameter is set to a

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

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

Number Threshold Para.MassFlowPacket small value, a large number of
NumberThld services are identified as
heavy-traffic services. The
Cell Algorithm Switch Parameters
Table 4-6 Cell algorithm switch parameters

IRC Switch CellAlgoSwitch.IrcSw ● Deselect the

itch PrachIrcSwitch option.
● Select the PucchIrcSwitch
option of this parameter in
interference scenarios.
Uplink schedule CellAlgoSwitch.UlSch Deselect the

switch Switch PrachRbReuseSwitch option.
4.4.1.2 Using MML Commands
Activation Command Examples

This section provides MML command examples for setting up a massive MIMO
cell. The following operations are not required when a massive MIMO cell is to be
set up at an existing site:
● Activating the minimum configuration
● Configuring operator information
● Configuring clock information
● 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;

eRAN
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 the BBP is UBBPem
ADD BRD: SN=3, BT=UBBP, BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-1&NBIOT-0,
CPRIITFTYPE=CPRI_QSFP;
//When the BBP is UBBPf3/UBBPg2a/UBBPg3b/UBBPg3
ADD BRD: SN=3, BT=UBBP, BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-1&NBIOT-0,
CPRIITFTYPE=CPRI_SFP;
//When the BBP is UBBPf1
ADD BRD: SN=3, BT=UBBP, BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-1&NBIOT-0, BRDSPEC="UBBPf1",
//When the BBP is UBBPg4
ADD BRD: SN=3, BT=UBBP, BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-1&NBIOT-0, BRDSPEC="UBBPg4",
//When the BBP is UBBPfw1
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;
//(Optional: single-CPRI 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: dual-CPRI scenarios where the two optical fibers between BBP and AAU must have the same
length) Adding an AAU
ADD RRUCHAIN: RCN=0, TT=TRUNK_CHAIN, AT=LOCALPORT, CONNPORTNUM=2, CONNSN1=3,
CONNPN1=0, CONNSN2=3, CONNPN2=1, PROTOCOL=CPRI;
//Configuring clock information

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

SET TZ: ZONET=GMT+0800, DST=NO;
//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.

eRAN
ADD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, SN1=3;
//Adding a cell
//The following command uses a 64T64R cell and CPRI networking as an example. In CPRI networking
scenarios, set the Cell.CPRICompression parameter to ENHANCED_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,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, CrsPortNum=CRS_PORT_2,
CPRICompression=ENHANCED_COMPRESSION, TxRxMode=64T64R;
//Adding a cell (The following uses a 32T32R cell and eCPRI networking as an example. In eCPRI
networking, set the Cell.CPRICompression parameter to NO_COMPRESSION.)
ADD CELL: LocalCellId=0, CellName="32TSite", 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,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, CrsPortNum=CRS_PORT_2,
CPRICompression=NO_COMPRESSION, TxRxMode=32T32R;
//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;
//Adding a beamforming antenna based on actual cell conditions

ADD BFANT: DEVICENO=0, CONNSRN=60, MODELNO="MassiveAntenna", TILT=6, TiltFractionalPart=0,
BFANTBEARING=0, Band=38, CoverageScenario=SCENARIO_2;
//Setting 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

MOD SRSCFG: LocalCellId=0, SrsCfgPolicySwitch=SrvBasedSRSAdjAlgo-1;
MOD SERVICEIDENTIFYPARA: HeartbeatPacketLengthThld=180, HeartbeatPacketNumberThld=4,
MassFlowBigPacketRateThld=80, MassFlowDuration=2, MassFlowPacketNumberThld=200;
//(Optional, recommended) Setting the default paging cycle in eCPRI scenarios

MOD PCCHCFG: LocalCellId=0, DefaultPagingCycle=rf256;
Deactivation Command Examples

None
4.4.1.3 Using the MAE-Deployment

● Fast batch activation
This function can be batch activated using the Feature Operation and
Maintenance function of the MAE-Deployment. For detailed operations, see
the following section in the MAE-Deployment product documentation or
online help: MAE-Deployment Management > MAE-Deployment
Guidelines > Enhanced Feature Management > Feature Operation and
Maintenance.
● Single/Batch configuration

eRAN
This function can be activated for a single base station or a batch of base
stations on the MAE-Deployment. For detailed operations, see Feature
Configuration Using the MAE-Deployment.
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 been successfully configured. If the amplitudes and phases of physical ports
1 through 64 are not empty in the command output, the beam weights have been
successfully configured.
Step 3 Run the DSP CELLCALIBRATION command after UEs access the network to check
the channel calibration result. If the Calibration Result of the latest calibration is
SUCCESS, channel calibration is successful.
NOTE
● 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.
● Beamforming and PDCCH SDMA cannot be activated if channel calibration fails.
----End
4.4.3 Network Monitoring

N/A
4.4.4 Possible Issues
Channel Calibration Failures

A user-defined performance threshold alarm can be configured on the MAE-
Access. The alarm is reported when the duration of the channel calibration failure
reaches the configured threshold. The alarm helps more quickly identify channel
calibration failures.
To define a channel calibration failure alarm, perform the following operations on

the MAE-Access:
Step 1 On the MAE-Access, 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.
Step 3 Select one or more NEs in the Object tab of the Add Threshold dialog box.

eRAN
Step 4 On the Basic tab page, set Name, Period, and Activation time.
Step 5 On the Advanced tab page, perform the following operations and then click OK.
● Set Direction to Ascending.
● Set Function subset to Network/Measurements Related to
Algorithm(LTE)/Cell Sector Algorithm Measurement.
● Set Counter name to L.CellSectorEqpt.UNA.Dur.Cali.
● 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.
● 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
If the channel calibration failure duration in the period specified by Period is
greater than or equal to Threshold plus Offset, the customized channel
calibration failure alarm is reported. If the channel calibration failure duration in
the period specified by Period is less than Threshold minus Offset, the alarm is
cleared.
Antenna Fault
For details, see TDLEOFD-12160105 Antenna Fault Detection and
TDLEOFD-12160101 Flexible Active-Unit Management.

eRAN
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

This section describes TDLEOFD-15161101 UL 32-Antenna Receive Diversity and
TDLEOFD-12160301 UL 64-Antenna Receive Diversity.
5.1.1 Principles
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 (64T64R is used as an example.)
Receive diversity is not under parameter control. It can be used after a massive
MIMO cell is configured and the license is loaded.
The typical signal combining algorithms used by receive diversity include
maximum ratio combining (MRC) and interference rejection combining (IRC). 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 horizontally and vertically. It

eRAN
achieves better uplink and downlink coverage performance than 8T8R. 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
This function covers a larger area on the vertical plane than 2-, 4-, or 8-antenna
receive diversity. Accordingly, interference may increase and the measured
interference value may increase, compared with a common cell.
Function Impacts
Function Function Switch Reference Description
Name
Control PrachIrcSwitch and MRC and IRC If PRACH IRC is

channel PucchIrcSwitch Receivers enabled in a massive
receivers options of the MIMO cell, it may
CellAlgoSwitch.IrcSw affect the
itch parameter performance of access
to the cell and
therefore it is
recommended that
PRACH IRC be
disabled. In
interference scenarios,
it is recommended
that PUCCH IRC be
enabled.
PRACH RB PrachRbReuseSwitch Scheduling The function of

occupation by option of the PRACH RB occupation
PUSCH CellAlgoSwitch.UlSch by PUSCH may
Switch parameter decrease the RRC
connection setup
success rate in
massive MIMO
scenarios.
It is recommended
that PRACH RB
occupation by PUSCH
be disabled.
5.1.3 Requirements

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

603 MIMO Basic Package 0
TDLEOFD-151 32T32R Massive LT4S32TBSTD Per Cell

611 MIMO Basic Package D
5.1.3.2 Software
Name
Massive 32T32R or 64T64R 4 Basic None

MIMO value of the Massive
introduction Cell.TxRxMode MIMO
parameter Functions

None
5.1.3.3 Hardware
For details, see 4.3.3 Hardware. Uplink 32-antenna receive diversity requires a
32T32R AAU and a UBBPg2a/UBBPg3b/UBBPg3. Uplink 64-antenna receive
diversity requires a 64T64R AAU.
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 their specifications.

eRAN
Feature ID Feature Name Maximum Maximum

Number of Number of
Layers That Can Antennas
Be Paired
TDLEOFD-121603 UL 2x64 MU- 2 64

02 MIMO
TDLEOFD-121609 UL 4-Layer MU- 4 32 or 64

MIMO
TDLEOFD-121610 UL 8-Layer MU- 8 32 or 64

MIMO
TDLEOFD-151611 UL 2x32 MU- 2 32

02 MIMO
NOTE
● MU-MIMO is used only for PUSCH resource multiplexing.

● 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 allows multiple UEs' data to be transmitted using the same time-
frequency resources. It brings multiplexing gains in addition to diversity and array
gains.
After MU-MIMO is enabled in a massive MIMO cell, the eNodeB attempts to pair
UEs in each TTI. UEs that are paired successfully use the same uplink time-
frequency resources to transmit multiple data streams. This increases the average
uplink cell throughput. Each of UEs that fail to be paired uses independent uplink
time-frequency resources.
MU-MIMO is controlled by the UlVmimoSwitch option of the
CellAlgoSwitch.UlSchSwitch parameter.
Figure 5-2 MU-MIMO

eRAN
UE Pairing
Figure 5-3 UE pairing procedure for MU-MIMO
The maximum number of paired layers for MU-MIMO in a massive MIMO cell is
specified by the CellUlschAlgo.MaxLayerMMVMIMO parameter.
The principles for selecting UEs to be paired are as follows:
● High-speed UEs are not selected for MU-MIMO pairing, as their channels
change rapidly and their radio links are unstable. Pairing such UEs may cause
system performance to deteriorate.
● 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.
NOTE
The correlation between UE channels is calculated based on uplink feedback. This

correlation 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.

eRAN
● The following parameters are used to control the types of UEs to be paired or
UE pairing policy:
Parameter ID Description
CellUlschAlgo.VmimoPairingStrat- Specifies the pairing policy.

egy
HarqVmimoSwitch option of the Specifies whether to pair UEs that
CellUlschAlgo.VmimoOptAlgoSwit require uplink HARQ retransmission.
ch parameter
PreSchVmimoSwitch option of the Specifies whether to pair UEs subject
CellUlschAlgo.VmimoOptAlgoSwit to uplink preallocation.
ch parameter
VoLTEUeVmimoSwitch option of Specifies whether to pair VoLTE UEs.
the CellAlgoSwitch.UlSchSwitch
parameter
SrPairingSwitch option of the Specifies whether to pair UEs

CellAlgoSwitch.UlSchExtSwitch sending an uplink scheduling
parameter request (SR).
MU-MIMO Enhancement
● Resource randomization
After MU-MIMO is enabled, interference on the PUSCH may increase. In this
case, you are advised to enable resource randomization to ensure that the
user-perceived rates in neighboring cells do not decrease after MU-MIMO
takes effect. This function is controlled by the VMIMOResRandomSwitch
option of the CellUlschAlgo.VmimoOptAlgoSwitch parameter.
● 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 is controlled by the
VmimoOptResSwitch option of 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.
● Uplink MU-MIMO pairing optimization
When uplink is heavily loaded and large-packet services are limited,
retransmission may cause large-packet services to be discontinuous and
generate fragments. As a result, the number of paired layers decreases. The
uplink MU-MIMO pairing optimization function reduces fragments and
increases the number of paired layers for large-packet services. In addition,
this function increases large-packet UE scheduling priorities.
This function is controlled by the MmVmimoUePairingOptSw option of the
CellUlschAlgo.VmimoOptAlgoSwitch parameter. After this function is
enabled, the uplink cell throughput increases.
● Resource randomization in MU-MIMO enhancement

eRAN
After this function is enabled, uplink resource allocation positions are

staggered between cells. This may increase the number of uplink resource
fragments and decrease the uplink user-perceived rate.
5.2.2.1 Benefits
This function increases multiplexing gains. Massive MIMO supports up to eight
layers for uplink MU-MIMO, with the theoretical uplink peak throughput
approximately eight times that provided by uplink receive diversity in 8T8R
scenarios.
The uplink MU-MIMO pairing optimization function can increase the User Uplink
Average Throughput and uplink cell throughput by up to 5% in big event
scenarios where more than four UEs have uplink large packets (occupying more
than 60 RBs) within a TTI and the proportion of such TTIs exceeds 50%. If the
preceding conditions are not met, this function does not provide noticeable gains.
NOTE
For details about multiplexing gains, see Beamforming (TDD).
5.2.2.2 Impacts
Network Impacts
● After uplink 2x32 MU-MIMO, uplink 2x64 MU-MIMO, uplink 4-layer MU-
MIMO, or uplink 8-layer MU-MIMO is enabled, the probability of uplink
control channel element (CCE) allocation failures may increase because the
number of uplink scheduled UEs increases.
● Uplink 4-layer MU-MIMO or uplink 8-layer MU-MIMO
– After the function is enabled, paired UEs may change in each TTI, leading
to fluctuating interference between paired UEs. As a result, the PUSCH
BLER may increase.
– The uplink or downlink IBLER may increase after a 4T/8T cell is
reconstructed into a massive MIMO cell.
● Uplink MU-MIMO pairing optimization
After this function is enabled, the user-perceived data rates of large-packet
UEs increase and the user-perceived data rates of small-packet UEs decrease.
The total user-perceived data rate may fluctuate and the average user
scheduling duration may also fluctuate.
● Resource randomization in MU-MIMO enhancement
After this function is enabled, uplink resource allocation positions are
staggered between cells. This may increase the number of uplink resource
fragments and decrease the uplink user-perceived rate.

eRAN
Function Impacts
Function Function Referenc Description
Name Switch e
RAN ENodeBShari RAN To maximize the uplink capacity when

sharing ngMode.ENo Sharing MU-MIMO is enabled, the proportion
with deBSharingM of RBs is not limited during UE pairing.
common ode The actual proportion of uplink RBs
carrier allocated to an operator may be less
than the CellOp.OpUlRbUsedRatio
parameter value if the base station
sharing mode is set to SHARED_FREQ,
the
CellAlgoSwitch.RanShareModeSwitc
h parameter of the shared cells is set
to ON or STATIC_SHARING, and the
CellMimoParaCfg.RanSharingSchOpt
Switch parameter is set to OFF.
Hybrid ENodeBShari RAN To maximize the uplink capacity when
RAN ngMode.ENo Sharing MU-MIMO is enabled, the proportion
sharing deBSharingM of RBs is not limited during UE pairing.
ode The actual proportion of uplink RBs
allocated to an operator may be less
than the CellOp.OpUlRbUsedRatio
parameter value if the base station
sharing mode is set to
HYBRID_SHARED, the
5.2.3 Requirements
5.2.3.1 Licenses
● 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)
None None LT4SMMULM Massive Per 2 Layer

L01 MIMO UL 2-
Layers
Extended
Processing
Unit License
(TDD)
● 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. Either of
64T64R Massive MIMO Basic Package (TDD) and 32T32R Massive MIMO
Basic Package (TDD) is required.

Name Control Item

Package Package
(TDD)
TDLEOFD-15 32T32R LT4S32TBST 32T32R Per Cell

1611 Massive DD Massive
Package Package
(TDD)
TDLEOFD-12 UL 4-Layer LT1SUL464M UL 4-Layer Per Cell

1609 MU-MIMO 00 MU-MIMO
(TDD)
None None LT4SMMULM Massive Per 2 Layers

L01 MIMO UL 2-
Layers
Extended
Processing
Unit License
(TDD)
UL 8-Layer MU-MIMO. Four units of the license control item Massive MIMO
UL 2-Layers Extended Processing Unit License (TDD) are required. Either of

eRAN
64T64R Massive MIMO Basic Package (TDD) and 32T32R Massive MIMO
Basic Package (TDD) is required.
Name Control Item

Package Package
(TDD)

Package Package
(TDD)

(TDD)

(TDD)

L01 MIMO UL 2-
Layers
Extended
Processing
Unit License
(TDD)
● The operator has purchased and activated the following license for
TDLEOFD-15161102 UL 2x32 MU-MIMO. Only one unit of the license control
item Massive MIMO UL 2-Layers Extended Processing Unit License (TDD)
is required.
Name Control Item

Package Package
(TDD)

eRAN

Name Control Item

L01 MIMO UL 2-
Layers
Extended
Processing
Unit License
(TDD)
5.2.3.2 Software
● TDLEOFD-15161102 UL 2x32 MU-MIMO and TDLEOFD-12160302 UL 2x64
MU-MIMO require the following functions.
Name
Massive Cell.TxRxMode set 4 Basic None

MIMO to 32T32R or Massive
introduction 64T64R MIMO
Functions
Downlink BfSwitch option of 6.1 3D The MU-MIMO

flexible 3D the Beamformin pairing algorithm
beamformin CellAlgoSwitch.BfAl g requires that UEs in
g goSwitch parameter single-stream
beamforming report
measurement
results.
Scheduler- SchedulerCtrlPo- Scheduling MCS index selection

controlled werSwitch option of optimization
power the depends on the
CellAlgoSwitch.UlSc scheduler-controlled
hSwitch parameter power function.
Bundled CellUlschAlgo.UlHe Scheduling Uplink MU-MIMO

scheduling of avyloadOptSchSwit pairing optimization
SR UEs ch requires bundled
(TDD) scheduling of SR UEs
in heavy load
scenarios.

eRAN

Name
TCP ACK CellUlschAlgo.Estim Video Uplink MU-MIMO

estimation atedTcpAckPacket- Experience pairing optimization
(TDD) Count Optimization takes effect only
when TCP ACK
estimation is
enabled.
● TDLEOFD-121609 UL 4-Layer MU-MIMO requires the following functions.

Name
Uplink 2x32 UlVmimoSwitch 5.1 Receive Either uplink 2x32

MU-MIMO option of the Diversity MU-MIMO or uplink
or uplink CellAlgoSwitch.UlSc 2x64 MU-MIMO is
2x64 MU- hSwitch parameter required.
MIMO

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

Name
Uplink 2x32 UlVmimoSwitch 5.1 Receive Either uplink 2x32

MU-MIMO option of the Diversity MU-MIMO or uplink
or uplink CellAlgoSwitch.UlSc 2x64 MU-MIMO is
2x64 MU- hSwitch parameter required.
MIMO
Uplink 4- UlVmimoSwitch None None

layer MU- option of the
MIMO CellAlgoSwitch.UlSc
hSwitch parameter

None

eRAN
5.2.3.3 Hardware
For details, see 4.3.3 Hardware. MCS index selection optimization requires the
configuration of UBBPf1/UBBPf3/UBBPfw1/UBBPg2a/UBBPg3b/UBBPg3/UBBPg4.
Uplink 2x32 MU-MIMO requires the configuration of UBBPg2a/UBBPg3b/UBBPg3.
AAU models should be determined based on the number of antennas.
5.2.4.1 Data Configuration
5.2.4.1.1 Data Preparation

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.Vmimo To enable MU-MIMO, select the

Optimization OptAlgoSwitch HarqVmimoSwitch and
Algorithm PreSchVmimoSwitch options.
Switch To enable MU-MIMO enhancement,
perform the following operations:
● To enable resource
randomization, select the
VmimoResRandomSwitch
option.
● To enable MCS index selection
optimization, select the
VmimoOptResSwitch option.
● To enable uplink MU-MIMO
pairing optimization, select the
MmVmimoUePairingOptSw
option.
VMIMO Pairing CellUlschAlgo.VmimoP Set this parameter to ADAPTIVE.

Strategy airingStrategy

eRAN

Name
Max Number CellUlschAlgo.MaxLay ● Set this parameter to 2LAYER for

of Layers for erMMVMIMO TDLEOFD-15161102 UL 2x32
Massive MIMO MU-MIMO.
VMIMO ● Set this parameter to 2LAYER for
TDLEOFD-12160302 UL 2x64
MU-MIMO.
● Set this parameter to 4LAYER for
TDLEOFD-121609 UL 4-Layer
MU-MIMO.
● Set this parameter to 8LAYER for
TDLEOFD-121610 UL 8-Layer
MU-MIMO.
Uplink CellAlgoSwitch.UlSchS ● If there are many VoLTE UEs, it is

schedule witch recommended that the
switch UlVmimoSwitch and
VoLTEUeVmimoSwitch options
be selected. The
VoLTEUeVmimoSwitch option
takes effect only when the
UlVmimoSwitch option is
selected.
● If there are a small number of
VoLTE UEs, it is recommended
that the VoLTEUeVmimoSwitch
option be deselected.a
● Select the SchedulerCtrlPowerS-
witch option when MCS index
selection optimization is enabled.

eRAN

Name
Uplink CellAlgoSwitch.UlSchE ● In light load or sparse uplink

Schedule xtSwitch service scenarios, the BLER may
Extended increase if UEs sending
Switch scheduling requests are paired.
Therefore, it is not recommended
that the SrPairingSwitch option
be selectedb.
● In heavy load or densely
distributed uplink service
scenarios, UE pairing for SR
transmission increases the uplink
capacity and SR scheduling
success rate, though also causes
the BLER to increase. Therefore, it
is recommended that the
SrPairingSwitch option be
selected. The SrPairingSwitch
option takes effect only when the
UlVmimoSwitch option of the
CellAlgoSwitch.UlSchSwitch
parameter is selected.
CCE Max Initial CellPdcchAlgo.CceMax The value 10_1 is recommended for

Ratio InitialRatio uplink MU-MIMO pairing
optimization so that the function is
easier to take effect.
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.
5.2.4.1.2 Using MML Commands

//Setting 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;
//Turning on the SrPairingSwitch

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 subject to retransmission and preallocation, and MU-MIMO resource
randomization, and specifying the MU-MIMO pairing policy

eRAN
MOD CELLULSCHALGO: LocalCellId=0, MaxLayerMMVMIMO=8LAYER,

VmimoOptAlgoSwitch=HarqVmimoSwitch-1&PreSchVmimoSwitch-1&VmimoResRandomSwitch-1,
VmimoPairingStrategy=ADAPTIVE;
//Enabling MCS index selection optimization

MOD CELLULSCHALGO: LocalCellId=0, VmimoOptAlgoSwitch=VmimoOptResSwitch-1;
//Enabling uplink MU-MIMO pairing optimization

MOD CELLULSCHALGO: LocalCellId=0, VmimoOptAlgoSwitch=MmVmimoUePairingOptSw-1;
//Configuring the maximum initial CCE ratio
MOD CELLPDCCHALGO: LocalCellId=0, CceMaxInitialRatio=10_1;

● 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 deselecting the HarqVmimoSwitch,

PreSchVmimoSwitch, or VmimoResRandomSwitch option
MOD CELLULSCHALGO: LocalCellId=0, VmimoOptAlgoSwitch=HarqVmimoSwitch-0;
//(Optional) Deactivating MCS index selection optimization

MOD CELLULSCHALGO: LocalCellId=0, VmimoOptAlgoSwitch=VmimoOptResSwitch-0;
//(Optional) Deactivating uplink MU-MIMO pairing optimization

MOD CELLULSCHALGO: LocalCellId=0, VmimoOptAlgoSwitch=MmVmimoUePairingOptSw-0;
● 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 MAE-Deployment

Maintenance.
5.2.4.2 Activation Verification
MU-MIMO Pairing
Step 1 On the MAE-Access, choose Monitor > Signaling Trace > Signaling Trace
Management.
Step 2 In the navigation tree of the Signaling Trace Management tab page, choose LTE
> Cell Performance Monitoring, and then double-click Multi-User MIMO
Monitoring.

eRAN
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 or equal to –75 dBm, and then perform uplink FTP services on these UEs.
Step 5 Double-click the trace task to verify the value of UL MIMO UE Pair Num.
● 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.
● If the value of UL MIMO UE Pair Num 2 Layers is not N/A, uplink 2x32 MU-
MIMO or uplink 2x64 MU-MIMO has been enabled.
● 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 been enabled.
● 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 been enabled.
Step 6 Use multiple UEs to access the network, adjust the RSRP of the UEs to be greater
than or equal to –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
involved in MU-MIMO pairing.
----End
MU-MIMO Enhancement
Step 1 Run the LST CELLULSCHALGO command. If the value of Vmimo Optimization
Algorithm Switch is VMIMOResRandomSwitch:On, resource randomization has
been enabled.
Algorithm Switch is VmimoOptResSwitch:On, MCS index selection optimization
has been enabled.
Algorithm Switch is MMVmimoUePairingOptSw:On, uplink MU-MIMO pairing
optimization has been enabled.
----End
5.2.4.3 Network Monitoring
Signaling Tracing
Management.
> Cell Performance Monitoring > Throughput Monitoring. Check the
throughput of the corresponding base station and cells.

eRAN
> Cell Performance Monitoring > Multi User-MIMO Monitoring. Check the
values of the following monitoring items on the MAE-Access.
● UL MIMO UE Pair Num
● UL MIMO UE Pair Num 2 Layers through UL MIMO UE Pair Num 8 Layers
● 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-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 4-layer MU-MIMO.
If the monitoring item corresponding to an MU-MIMO feature has a non-zero

value, the feature has been activated. If the number of UEs or RBs paired for
uplink MIMO is always 0, see 5.2.4.4 Possible Issues.
NOTE
MU-MIMO pairing performance is subject 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.
> Cell Performance Monitoring > Multi User-MIMO Monitoring. Check the
value of VoLTE UE Mimo Pair Num on the MAE-Access.
● If the value of VoLTE UE Mimo Pair Num is not 0, VoLTE UEs have been
paired for MU-MIMO.
● 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:
● Total Number of TBs Transmitted in the Uplink in Massive MIMO
● Total Number of TBs That Fail to Be Transmitted in the Uplink in Massive
MIMO
● Number of Bits Successfully Transmitted in the Uplink in Massive MIMO
● Total Number of RBs Transmitted in the Uplink in Massive MIMO Scenarios
● Number of RBs That Are Successfully Paired for VMIMO UEs in a Cell
● Number of RBs That Can Be Paired for VMIMO UEs in a Cell
● 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. If multiple UEs share the same PRB, multiple PRBs are counted. 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.

eRAN
Counter ID Counter Name
1526726737 L.ChMeas.PRB.UL.Used.Avg
1526728545 L.ChMeas.PRB.UL.PreSch.Used.Avg
1526730557 L.ChMeas.PRB.UL.PUSCH.Avail
1526746010 L.ChMeas.PRB.UL.DrbUsed.Avg.ExtQci.Index0
1526741727 L.ChMeas.PRB.UL.Avg.EdgeActiveSchVoIPUser
1526733015 L.ChMeas.PRB.UL.PCell.Used.Avg
1526728294 L.RBUsedOwn.UL.PLMN
1526741667 L.RBUsedOtherGroup.UL.PLMN
----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.
● If no, apply for and load a new license.
● If yes, go to the next step.
Management.
> Cell Performance Monitoring > Users Statistic Monitoring. Create and start a
tracing task, and check the value of General Users Number.
● 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.
● If there are enough UEs, go to the next step.
> User Performance Monitoring > Quality of Channel Monitoring. Create and
start a tracing task, and check SINRs.
● 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.
● 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
Description 6 Downlink Multiple-Antenna Transmission
6 Downlink Multiple-Antenna
Transmission
Category Applicable Channel Recommended

Transmission Mode
3D beamforming PDSCH ● Non-antenna-

selection UEs: TM7
● Antenna selection
UEs: TM8
MU beamforming PDSCH ● Non-antenna-

selection UEs: TM7
● Antenna selection
UEs: TM8
TM9 PDSCH TM9w/oPMI or

TM9wPMI
TM9 hybrid precoding PDSCH TM9wPMI
Multi-user split SDMA PDSCH TM7, TM8, or PMI

feedback-independent
TM9 (TM9w/oPMI), or
PMI feedback-dependent
TM9 (TM9wPMI)
PDCCH SDMA PDCCH N/A
Enhanced coordinated PDSCH N/A

scheduling based power
control
NOTE
Unless otherwise specified, non-antenna-selection UEs 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
● 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.
● The channel calibration result can be queried by running the DSP CELLCALIBRATION
command. Beamforming and PDCCH SDMA cannot be activated if channel calibration
fails.
TDLEOFD-121615 DL Flexible 3D-Beamforming is also referred to as 3D

beamforming. 3D beamforming adopts array antennas and uses more logical
antennas on the vertical plane than traditional beamforming, which makes it
possible to implement vertical-plane beamforming.

eRAN
Figure 6-2 Vertical-plane beamforming
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 PDSCH characteristics based on

UE-reported SRSs and calculates beamforming weights.
3. Weighting and beamforming: The eNodeB applies the weights to the to-be-
transmitted signals to form narrow beams towards the UEs. In this way, the
eNodeB differentiates the UEs horizontally and vertically.
Figure 6-4 Beamforming
4. Demodulation: The UEs demodulate PDSCH data based on demodulation

reference signals (DMRSs).
3D beamforming is controlled by the BfSwitch option of the
CellAlgoSwitch.BfAlgoSwitch parameter. This feature takes effect only when the
BfSwitch option of the CellAlgoSwitch.BfAlgoSwitch parameter is selected and
the license for TDLEOFD-121615 DL Flexible 3D-Beamforming (as described in
6.1.3.1 Licenses) has been obtained.

eRAN
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. Massive MIMO also increases the downlink cell throughput and spectral
efficiency.
NOTE
For details about beamforming gains, see Beamforming (TDD).
6.1.2.2 Impacts
Network Impacts
None
Function Impacts
Name
Coverage- IntraFreqCoverHoS- Mobility When certain UEs

based intra- witch option of the Management work in beamforming
frequency ENodeBAlgoSwitch.H in Connected mode in massive
handover oAlgoSwitch Mode MIMO cells, the
parameter 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 lead to a
decrease in the intra-
frequency handover
success rate due to
actual low RSRP
values.

eRAN

Name
Beamforming NoSrsSccBfSwitch Carrier Beamforming is

in SCells option of the Aggregation supported in the PCell.
CellAlgoSwitch.NoSrs It is supported in
SccBfAlgoSwitch SCells only under
parameter certain conditions:
● When uplink CA is
not supported and
beamforming in
SCells is not
enabled,
beamforming is
not supported in
SCells.
not supported but
beamforming in
SCells is enabled,
beamforming is
supported in SCells.
supported,
beamforming is
supported in SCells.
6.1.3 Requirements
6.1.3.1 Licenses
TDLEOFD-121 DL Flexible 3D- LT1SDL643D0 Per Cell

615 Beamforming 0
6.1.3.2 Software

eRAN
Function Name Function Switch Reference
Massive MIMO 32T32R or 64T64R value 4 Basic Massive MIMO

introduction of the Cell.TxRxMode Functions
parameter

None
6.1.3.3 Hardware
For details, 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

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

Configuration e ACCESS_ENHANCED for massive
Mode MIMO cells.
BF algorithm CellAlgoSwitch.BfAlgo Select the BfSwitch option.

switch Switch

eRAN

Name
Beamforming CellBf.MaxBfRankPara Set this parameter to

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

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

mode xedBfMimoMode transmission mode is tested and the
CellBfMimoParaCfg.BfMimoAdapti
veSwitch parameter is set to
NO_ADAPTIVE.
Bf Mimo CellBfMimoParaCfg.Bf Set this parameter to ON.

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

Adaptive with MimoAdapWithTm4S massive MIMO scenarios, since
TM4 witch massive MIMO is not compatible
with downlink 4x4 MIMO.
BfMimo CellBfMimoParaCfg.Bf ● You are advised to select the

Algorithm MimoAlgoOptSwitch BFTOMIMOALGOOPTSWITCH
Optimization option when enabling adaptive
Switch switching between beamforming
and MIMO.
● Select the
BFMIMOADAPWITHOUTTM8
option when enabling adaptive
switching between beamforming
and MIMO or adaptive switching
between open-loop beamforming
modes.
● You are advised to select the
BF_WEIGHT_GRAN_OPT_SWITC
H option to enable beamforming
weight granularity optimization
so that the eNodeB selects the
weight granularity based on the
SRS SINR.

eRAN

Name
UE Access CellBfMimoParaCfg.Ue Set this parameter to TM7 when

Transmission AccessTMMode TMA is enabled in massive MIMO
Mode scenarios. For details about the
reasons, see 6.7.1.3 Optimized
TMA.
PHICH PHICHCfg.PhichDurati Set this parameter to NORMAL.

duration on
Uplink and CellPdcchAlgo.ULDLPd Set this parameter to 1.
Downlink cchSymNum
PDCCH
Symbols
Configuration
PDCCH Initial CellPdcchAlgo.InitPdcc Set this parameter to 1.

Symbol hSymNum
Number

//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;


eRAN

Maintenance.

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.
NOTE
The 3GPP release version of the UE can be queried in the RRC_UE_CAP_INFO message.
Step 2 On the MAE-Access, 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.

eRAN
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 MU beamforming features and their specifications.
Feature ID Feature Name Maximum Number of

Number of Antennas
Layers That Can
Be Paired
TDLEOFD-121604 DL 8-Layer MU- 8 32 or 64

Beamforming
TDLEOFD-121605 DL 16-Layer MU- 16 32 or 64

Beamforming
TDLEOFD-131603 DL 24-Layer MU- 24 64

Beamforming
(Trial)
NOTE
"Layer" in the feature names refers to the maximum number of multiplexing layers.
6.2.1 Principles
6.2.1.1 Overview
MU beamforming allows multiple UEs to be paired on the same time-frequency
resources. One or two data streams can be transmitted for each UE, and a
maximum of 24 streams can be transmitted simultaneously. In TM8, a maximum
of two streams of each antenna selection UE can be involved in pairing.
After MU beamforming is enabled in a massive MIMO cell, the eNodeB attempts
to pair UEs in each TTI.
The eNodeB performs MU beamforming as follows:
1. Determines the UEs to be paired based on UE pairing conditions, and the
number of downlink data streams to be transmitted to each UE.

eRAN
2. Generates orthogonal weights for downlink data streams based on the zero
forcing principle.
3. Applies the weights to data symbols and DMRS symbols for each data stream.
4. 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 resources, enhancing the downlink spectral efficiency.
MU beamforming is controlled by the MuBfSwitch option of the
CellAlgoSwitch.MuBfAlgoSwitch parameter.
This feature takes effect only when the MuBfSwitch option of the
CellAlgoSwitch.MuBfAlgoSwitch parameter is selected and the license for MU
beamforming (as described in 6.2.3.1 Licenses) has been obtained.
Figure 6-6 MU beamforming

eRAN
6.2.1.2 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 all 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 pairs the UEs that meet the pairing 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.
▪ 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.
▪ When this parameter is set to MU_WITHOUT_CORR_PAIR_RULE, the

eNodeB selects UEs for pairing without considering UE channel
correlations. The pairing rule increases the number of paired layers,
but may reduce the system capacity.

eRAN
3. The eNodeB uses the same time-frequency resources to transmit data to the
paired UEs.
Figure 6-8 uses 4-layer MU beamforming pairing as an example to illustrate
the resource block group (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 resources at layer 3 can be allocated to UEs 5 and 6 that are highly
correlated with UE 3 but lowly correlated with other UEs that use the same
resources for data transmission.
Figure 6-8 MU beamforming pairing
NOTE
UE pairing uses spatial resources and the scheduling priorities of UEs change after MU
beamforming is enabled. Therefore, MU beamforming has an impact on the features
or functions related to scheduling priorities, such as QoS management.
6.2.1.3 Scheduling Optimizations for MU Beamforming
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 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 user-perceived rate of heavy-traffic services.
This function is controlled by the DL_TIME_DIM_EXT_SCH_SWITCH option of the

CellAlgoSwitch.DlSchExtSwitch parameter.
The downlink time-domain extended scheduling function requires the service

identification mechanism. When this function is enabled, set the
ServiceIdentifyPara.MassFlowBigPacketRateThld and

eRAN
ServiceIdentifyPara.MassFlowPacketNumberThld parameters based on traffic

and service distributions for maximal network optimization.
MU Beamforming-specific MCS Index Selection Optimization

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. If there are many downlink
data packets, the CQI adjustment reliability is high.
In massive MIMO scenarios, the eNodeB selects MCS indexes for MU beamforming
based on the MCS indexes of SU beamforming. When there are a small number of
data packets in SU beamforming, the MCS indexes of SU 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 of 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. MCS indexes vary with signal quality when there are many low-speed
UEs, improving the MCS index selection accuracy and downlink spectral efficiency.
The UEs that are not suitable for pairing are not paired, which may reduce the
number of paired layers.
Moving UE Optimization
This function is controlled by the HIGH_SPEED_OPT_SCHEME value of the
CellBf.MovingUeMuBfScheme parameter. It also depends on the
SRS_LMT_AND_ABN_UE_IDENT_SW option of the CellBf.UeIdentificationSwitch
parameter. After the moving UE optimization function is enabled, the eNodeB
adjusts the MU beamforming pairing mechanism for moving UEs to ensure that
the MU beamforming weights of these 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 paired layers in the cell may
decrease.
Big-Event Moving UE Protection

This function is controlled by the BIG_EVENT_PROTECT_SCHEME value of the
CellBf.MovingUeMuBfScheme parameter. It also depends on the

eRAN
SRS_LMT_AND_ABN_UE_IDENT_SW option of the CellBf.UeIdentificationSwitch

parameter. After the big-event moving UE protection function is enabled, the
eNodeB adjusts the MU beamforming pairing mechanism for moving UEs in big-
event scenarios to ensure that the MU beamforming weights of these 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) delay.
NOTE
Average PDCP SDU 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)
6.2.1.4 Initial CQI Adjustment Value Control for MU Beamforming

Without this function, the initial CQI adjustment value for MU beamforming is 0
and cannot be changed. With this function, the initial CQI adjustment value for
MU beamforming can be configured using the
CellMMAlgo.MassiveMimoInitDeltaCqi parameter. The CQI adjustment values
for different UEs will converge to different values based on the
CellCqiAdjAlgo.InitDlIblerTarget parameter setting. For different CQI adjustment
values, the CellMMAlgo.MassiveMimoInitDeltaCqi parameter setting has
different impacts.
● If smaller CQI adjustment values are required for paired UEs, a smaller value
of this parameter improves the downlink spectral efficiency and a larger value
of this parameter lowers the downlink spectral efficiency.
● If larger CQI adjustment values are required for paired UEs, a larger value of
this parameter improves the downlink spectral efficiency and a smaller value
of this parameter lowers the downlink spectral efficiency.
NOTE
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 (trial) for downlink MU beamforming, which delivers 7 times or 9.9
times (trial) as much theoretical downlink peak throughput as downlink 2x2
MIMO in 8T8R networking scenarios does.
NOTE
For details about multiplexing gains, see Beamforming (TDD).

eRAN
6.2.2.2 Impacts
Network Impacts
● After MU beamforming is enabled, UEs paired within each TTI may change.
As a result, the interference between paired UEs may fluctuate and the
PDSCH BLER may increase.
● The downlink time-domain extended scheduling function improves the user
perceived rate of downlink heavy-traffic services.
● The MU beamforming-specific MCS index selection optimization function
reduces the IBLER.
● After a 4T/8T cell is reconstructed into a massive MIMO cell, the uplink and
downlink IBLERs may increase.
● When downlink 24-layer MU beamforming takes effect, the number of paired
layers may increase, the MCS index may decrease, and the BLER may increase.
This is because that the CellBf.MassiveMIMOMubfPairRule parameter must
be set to MU_WITHOUT_CORR_PAIR_RULE for the function to take effect.
Function Impacts
Name Switch e
Preferenti CellDlschAlg Schedulin Preferential use of resource allocation

al use of o.RbgAllocStr g type 1 does not take effect when MU
resource ategy beamforming is enabled. When the
allocation CellDlschAlgo.RbgAllocStrategy
type 1 parameter 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.
Beamfor NoSrsSccBfS Carrier Beamforming is supported in the PCell.

ming in witch option Aggregati It is supported in SCells only under
SCells of the on certain conditions:
CellAlgoSwit ● When uplink CA is not supported
ch.NoSrsSccB and beamforming in SCells is not
fAlgoSwitch enabled, beamforming is not
parameter supported in SCells.
● When uplink CA is not supported
but beamforming in SCells is
enabled, beamforming is supported
in SCells.
● When uplink CA is supported,
beamforming is supported in SCells.

eRAN

Name Switch e
Uplink CA CaUl2CCSwit Carrier ● The number of PRBs successfully

ch option of Aggregati paired for MU beamforming on
the on each layer may decrease by 5%
CaMgtCfg.Ce when uplink CA is enabled and the
llCaAlgoSwit Dl2CCAckResShareSw option of
ch parameter the
CellAlgoSwitch.PucchAlgoSwitch
● If uplink CA is enabled, up to eight
layers can be used for pairing SCC
UEs in MU beamforming. There is
no restriction on the maximum
number of layers for pairing SCC
UEs and PCC UEs or the maximum
UEs and non-CA UEs.
Uplink InterFddTddC Carrier ● The number of PRBs successfully

FDD+TDD aSwitch Aggregati paired for MU beamforming on
CA option of the on each layer may decrease by 5%
CaMgtCfg.Ce when uplink FDD+TDD CA is
llCaAlgoSwit enabled and the
ch parameter Dl2CCAckResShareSw option of
the
CellAlgoSwitch.PucchAlgoSwitch
● If uplink CA is enabled, up to eight
layers can be used for pairing SCC
UEs in MU beamforming. There is
no restriction on the maximum
UEs and PCC UEs or the maximum
UEs and non-CA UEs.
RAN ENodeBShari RAN To maximize the uplink capacity when

sharing ngMode.ENo Sharing MU beamforming is enabled, the
with deBSharingM proportion of RBs is not limited during
common ode UE pairing. The actual proportion of
carrier downlink RBs allocated to an operator
may be less than the
CellOp.OpDlRbUsedRatio parameter
value if the base station sharing mode
is set to SHARED_FREQ, the

eRAN

Name Switch e
Hybrid ENodeBShari RAN To maximize the uplink capacity when

RAN ngMode.ENo Sharing MU beamforming is enabled, the
sharing deBSharingM proportion of RBs is not limited during
ode UE pairing. The actual proportion of
downlink RBs allocated to an operator
may be less than the
CellOp.OpDlRbUsedRatio parameter
value if the base station sharing mode
is set to HYBRID_SHARED, the
6.2.3 Requirements
6.2.3.1 Licenses
DL 8-Layer MU-Beamforming. Four units of the license control item Massive
MIMO DL 2-Layers Extended Processing Unit License(TDD) are required.
Name Control Item
TDLEOFD-12 DL 8-Layer LT1SDL8LMB DL 8-Layer Per Cell

1604 MU- 00 MU-
Beamformin Beamformin
g g(TDD)
None None LT4SMMDLM Massive Per 2 Layers

L01 MIMO DL 2-
Layers
Extended
Processing
Unit
License(TDD)
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- 00 MU-
g g(TDD)
TDLEOFD-12 DL 16-Layer LT1SDL16MB DL 16-Layer Per Cell

1605 MU- 00 MU-
g g(TDD)

L01 MIMO DL 2-
Layers
Extended
Processing
Unit
License(TDD)
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- 00 MU-
g g(TDD)
TDLEOFD-12 DL 16-Layer LT1SDL16MB DL 16-Layer Per Cell

1605 MU- 00 MU-
g g(TDD)
TDLEOFD-13 DL 24-Layer LT4SDLMUBF DL 24-Layer Per Cell

1603 MU- 00 MU-
g (Trial) g(TDD)

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

eRAN
6.2.3.2 Software
● TDLEOFD-121604 DL 8-Layer MU-Beamforming requires the following
functions.
Massive MIMO Cell.TxRxMode set to 4 Basic Massive MIMO

introduction 32T32R or 64T64R Functions
2-layer MU MuBfSwitch option of Beamforming (TDD)

beamforming and 4- the
layer MU beamforming CellAlgoSwitch.MuBfA
lgoSwitch parameter
Downlink flexible 3D BfSwitch option of the 6.1 3D Beamforming
beamforming CellAlgoSwitch.BfAlgo
Switch parameter
● TDLEOFD-121605 DL 16-Layer MU-Beamforming requires the following

functions.

lgoSwitch parameter
Downlink 8-layer MU MuBfSwitch option of 6.2.1 Principles
beamforming the
CellAlgoSwitch.MuBfA
lgoSwitch parameter
● TDLEOFD-131603 DL 24-Layer MU-Beamforming (Trial) requires the

following functions.

lgoSwitch parameter
Downlink 8-layer MU MuBfSwitch option of 6.2.1 Principles
beamforming and the
downlink 16-layer MU CellAlgoSwitch.MuBfA
beamforming lgoSwitch parameter

eRAN

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

SDMA option of the Split SDMA pairing
CellAlgoSwitch. optimization or
MuBfAlgoSwitch big-event
parameter moving UE
protection is
not compatible
with the multi-
user split
SDMA
function.
● Downlink 24-
layer MU
beamforming
is not
compatible
with multi-user
split SDMA.
Energy saving SymbolPwrSavin Energy Downlink time-

based on g.TrigBndlSchDlA Conservation and domain extended
proactive vgPrbThld Emission scheduling is not
scheduling Reduction compatible with
energy saving
based on
proactive
scheduling.
Correlation-based DL_CLUSTER_PAI Massive MIMO Correlation-based

cluster pairing RING_SW option Optimization in cluster pairing
optimization of the WTTx Scenarios optimization is
CellMMAlgo.Prec (TDD) not supported
iseMubfOptSwitc when the number
h parameter of layers specified
by the
CellBf.HighOrder
MubfMaxLayer
parameter is
greater than 16.
6.2.3.3 Hardware
For details, see 4.3.3 Hardware. Downlink 24-layer MU beamforming (trial)
requires the configuration of UBBPf1/UBBPf3/UBBPfw1/UBBPg2a/UBBPg3b/
UBBPg3/UBBPg4.

eRAN

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

Name
MUBF CellAlgoSwitch.MuBfA ● Select the MuBfSwitch option of

Algorithm lgoSwitch this parameter if MU
Switch beamforming is required.
● Select the HarqRetranPairS-
witch option of this parameter if
MU beamforming is required
during HARQ retransmission.
● Deselect the MubfResAdjSwitch
option of this parameter if the
TxRxMode parameter is set to
32T32R or 64T64R.
DL Scheduling CellAlgoSwitch.DlSchE Select the

Extension xtSwitch DL_TIME_DIM_EXT_SCH_SWITCH
Switch option of this parameter if the
downlink time-domain extended
scheduling function is required.
Max Number CellBf.HighOrderMubf ● Downlink 8-layer MU

of MUBF MaxLayer beamforming: Set this parameter
Layers to EIGHT_LAYERS.
● Downlink 16-layer MU
beamforming: Set this parameter
to SIXTEEN_LAYERS.
beamforming (Trial): Set this
parameter to
TWENTYFOUR_LAYERS.
Port Allocation CellBf.QualUEPortAvoi Protection processing is

Avoid for dMode recommended for abnormal UEs
Continuous subject to consecutive block errors
NACK UEs when both MU beamforming and
dual-stream beamforming are
enabled. Otherwise, the abnormal
UEs may cause the service drop rate
to increase.

eRAN

Name
Massive MIMO CellBf.MassiveMIMOM ● Downlink 8- or 16-layer MU

MUBF Pairing ubfPairRule beamforming: Set this parameter
Rule to MU_CORR_PAIR_RULE.
beamforming (Trial): Set this
parameter to
MU_WITHOUT_CORR_PAIR_RU
LE.
Cell Highload CellBf.MultiLayerThdS Set this parameter to 20.

Thd for Switch witchToTM7
to BF
Moving Ue CellBf.MovingUeMuBf ● If big-event moving UE

MUBF Scheme Scheme protection is required, set this
parameter to
BIG_EVENT_PROTECT_SCHEME.
● If moving UE optimization is
required, set this parameter to
HIGH_SPEED_OPT_SCHEME.
MU CellCqiAdjAlgo.MuBfP ● Set this parameter to 20 when

Beamforming acketThld three or more layers are to be
Packet Count paired.
Threshold ● Set this parameter to 65535
when two 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 under uplink-
downlink subframe configuration 1 and
a maximum of 400 times under uplink-
downlink subframe configuration 2.
Therefore, MU beamforming-specific
MCS index selection optimization does
not take effect under 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 under 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.MMAlgo ● In low-speed mobility scenarios,

Algorithm OptSwitch it is recommended that the
Optimization MU_PAIRING_MCS_EXACT_SWI
Switch TCH option be selected to
improve the MU beamforming-
specific MCS index selection
accuracy.
● It is recommended that the
MU_PAIRING_VOLTE_SWITCH
option be selected to enable
pairing of VoLTE UEs for MU
beamforming when there is a
large number of VoLTE UEs. It is
recommended that the
MU_PAIRING_VOLTE_SWITCH
option be deselected to disable
pairing of VoLTE UEs for MU
beamforming when there is a
small number of VoLTE UEs.
NOTE
If VoLTE UEs do not participate in
MU beamforming pairing:
● The impact of inter-UE
interference on the PDSCH BLER
decreases.
● The downlink voice packet loss
rate of massive MIMO cells
decreases.
● In heavy-load scenarios, the
downlink traffic volume
(L.Thrp.bits.DL) decreases.
Massive MIMO CellMMAlgo.MassiveM It is recommended that this

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

eRAN

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

Weight Type Type MU 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.

eRAN

Name
MUBF Power CellBf.MubfPowerNor ● If this parameter is set to 0, PEBF

Normalization mAdptFactor power normalization is used for
Adaptive Factor MU beamforming.
● If this parameter is set to 10,
NEBF power normalization is
used for MU beamforming.
● 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 power
normalization 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 power
normalization for MU
beamforming. This preferentially
makes full use of the transmit
power of each antenna.
Table 6-3 Optimization parameters for downlink time-domain extended

scheduling
Name
Mass Flow Big ServiceIdentify- Set this parameter to a large value

Packet Rate Para.MassFlowBigPack when most heavy-traffic services
Threshold etRateThld are video or download services and
to a small value when most heavy-
traffic services are web browsing
services.

eRAN

Name
Mass Flow ServiceIdentify- Set this parameter to a large value

Packet Number Para.MassFlowPacket when most heavy-traffic services
Threshold NumberThld are video or 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 downlink time-domain 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=SIXTEEN_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 subject 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=8;
//Enabling the big-event moving UE protection function

MOD CELLBF: LocalCellId=0, MovingUeMuBfScheme=BIG_EVENT_PROTECT_SCHEME,
UeIdentificationSwitch=SRS_LMT_AND_ABN_UE_IDENT_SW-1;
//Enabling the moving UE optimization function

MOD CELLBF: LocalCellId=0, MovingUeMuBfScheme=HIGH_SPEED_OPT_SCHEME,

eRAN

//Disabling MU beamforming
MOD CELLALGOSWITCH: LocalCellId=0,
MuBfAlgoSwitch=MuBfSwitch-0&TM9MuBfSwitch-0&MubfResAdjSwitch-0&HarqRetranPairSwitch-0;

Maintenance.

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 MAE-Access to perform signaling tracing. For details, see 6.2.4.3 Network
Monitoring. If the measured value of any of the cell-level monitoring objects
listed in Table 6-4 is not 0, MU beamforming has been activated.
Table 6-4 MU beamforming monitoring objects

Monitoring Object Meaning
Number of Massive Number of downlink RBs paired for TM7 UEs for
MIMO MUBF Pairing massive MIMO MU beamforming. It can be obtained
TM7 RB (Num) by averaging the number of RBs paired for TM7 UEs
in each TTI in a monitoring period.
Number of Available Number of downlink RBs that can be paired for

Massive MIMO MUBF massive MIMO MU beamforming. It can be obtained
Pairing RB (Num) by averaging the number of RBs that can be paired in
each TTI in a monitoring period.
Number of Massive Number of downlink RBs paired at layer x for massive

MIMO MUBF Success MIMO MU beamforming. It can be obtained by
Pairing RB (Num) in averaging the number of RBs paired at layer x in each
xLayer TTI in a monitoring period.
----End

eRAN
Step 1 Monitor counters in the following function subsets:
● Number of PRBs for MUBF UEs at Each Layer
● Number of TTIs During Which UEs Are Successfully Paired in the Downlink
● Number of Layers Paired for Massive MIMO MU Beamforming
● Total Number of RBs Transmitted in the Downlink in Massive MIMO Scenarios
● Total Number of TBs Transmitted in the Downlink in Massive MIMO
● Number of Bits Successfully Transmitted in the Downlink in Massive MIMO
● Total Number of TBs Incorrectly Transmitted in the Downlink in Massive
MIMO
● Proportions of Non-Paired UEs and Paired UEs in the Downlink
Step 2 Monitor the SRS SINR using the following counters.
1526748696 L.UL.SINR.SRS.Index0
----End
When massive MIMO MU beamforming is enabled, the number of paired layers
and PRBs increases and the measured values of the following counter may reach
64 bits.
1526728881 L.ChMeas.BF.PRB.OL.Rank1
1526743729 L.ChMeas.BF.TM7.PRB.OL.Rank1
1526737845 L.ChMeas.PRB.TM7
1526727391 L.ChMeas.MIMO.PRB.CL.Rank1
When massive MIMO MU beamforming is enabled, the following counters

measure the number of PRBs actually scheduled for UEs in a cell. If multiple UEs

eRAN
share the same PRB, multiple PRBs are counted. 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.
1526726740 L.ChMeas.PRB.DL.Used.Avg
1526737871 L.ChMeas.PRB.DL.DrbUsed.Avg.Equivalent
1526746016 L.ChMeas.PRB.DL.DrbUsed.Avg.ExtQci.Index0
1526737870 L.ChMeas.PRB.DL.DrbUsed.Avg.VoIP.Equivalent
1526742157 L.ChMeas.PRB.DL.DrbUsed.Avg.QCI2.Equivalent
1526728424 L.ChMeas.PRB.DL.PCell.Used.Avg
1526732911 L.ChMeas.PRB.DL.PCell.RelaxedBackhaul-
CAUsed.Avg
1526732912 L.ChMeas.PRB.DL.SCell.RelaxedBackhaul-
CAUsed.Avg
1526739796 L.RB.DL.PCell.CAUsed.PLMN
1526739797 L.RB.DL.SCell.CAUsed.PLMN
1526728293 L.RBUsedOwn.DL.PLMN
1526741668 L.RBUsedOtherGroup.DL.PLMN
Signaling Tracing
● Cell-level MU beamforming monitoring
Management.
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
● UE-level MU beamforming monitoring

eRAN
Management.
page, choose 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
6.3 TM9
Massive MIMO supports the following TM9 features:
● TDLAOFD-00100114 DL 2-Layer MIMO Based on TM9
● TDLAOFD-130490 DL 8x8 MIMO
Table 6-5 Overview of TM9 features

Feature Transmission Logical Port Number of Number of
Mode Data Streams RRU
Channels
TDLAOFD-00 TM9w/oPMI Port 7 and 1~2 32T32R or

100114 DL 2- or TM9wPMI port 8 64T64R
Layer MIMO
Based on TM9
TDLAOFD-08 TM9w/oPMI Port 7 to port 1~4 32T32R or

1409 DL 4- or TM9wPMI 10 64T64R
Layer MIMO
Based on TM9
TDLAOFD-13 TM9wPMI Port 7 to port 1~8 32T32R or

0490 DL 8x8 14 64T64R
MIMO

eRAN
6.3.1 Principles
Downlink 2-Layer MIMO Based on TM9
In TM9wPMI or TM9w/oPMI mode, the eNodeB performs downlink weighting
based on PMI feedback or SRS measurement, and transmits a maximum of two
data streams on the same OFDM time-frequency resources. Adaptive switching
between rank 1 and rank 2 is supported based on UE and channel conditions.
Downlink 2-layer MIMO based on TM9 is enabled when the following conditions
are met: 3D beamforming is enabled, the TM9Switch option of the
CellAlgoSwitch.EnhMIMOSwitch parameter is selected, and the
CellDlschAlgo.MaxMimoRankPara parameter is set to SW_MAX_SM_RANK_2.
Downlink 4-Layer MIMO Based on TM9

This function works in either of the following modes:
● 4-layer MIMO based on TM9 and PMI feedback
In TM9wPMI mode, the eNodeB performs downlink weighting based on PMI
feedback and transmits a maximum of four data streams on the same OFDM
time-frequency resources, as shown in Figure 6-9. Adaptive switching among
ranks 1 to 4 is supported based on UE and channel conditions.
Figure 6-9 4-layer MIMO based on TM9 and PMI feedback
Downlink 4-layer MIMO based on TM9 and PMI feedback can be used when
– 3D beamforming is enabled and the TM9Switch option of the
CellAlgoSwitch.EnhMIMOSwitch parameter is selected.
– The CellDlschAlgo.MaxMimoRankPara parameter is set to
SW_MAX_SM_RANK_4.
● 4-layer MIMO based on TM9 and SRS measurement
In TM9w/oPMI mode, the eNodeB performs downlink weighting based on SRS
measurement and transmits a maximum of four data streams on the same

eRAN
OFDM time-frequency resources, as shown in Figure 6-10. Adaptive switching

among ranks 1 to 4 is supported based on UE and channel conditions.
Figure 6-10 4-layer MIMO based on TM9 and SRS measurement
Downlink 4-layer MIMO based on TM9 and SRS measurement can be used
when the following conditions are met:
– 3D beamforming is enabled, the TM9Switch option of the
CellAlgoSwitch.EnhMIMOSwitch parameter is selected, and the
CellBf.MaxBfRankPara parameter is set to FOUR_LAYER_BF.
– The MM_ANT_SEL_ENH_SWITCH option of the
CellMMAlgo.MMAlgoOptSwitch parameter is selected.
– The SRSCfg.SrsResExpansionSwitch parameter is set to OFF.
4-layer MIMO based on TM9 and SRS measurement is preferentially used if it
is enabled together with 4-layer MIMO based on TM9 and PMI feedback.
Downlink 8x8 MIMO

Downlink 8x8 MIMO enables a maximum of eight data streams to be transmitted
using the same OFDM time-frequency resources in TM9, as shown in Figure 6-11.
Adaptive switching among ranks 1 to 8 is supported based on UE and channel
conditions.
Figure 6-11 Downlink 8x8 MIMO
This feature offers the following benefits:

● TM9 increases the peak throughput and average cell throughput when five to
eight data streams are transmitted.
● TM9wPMI offers beamforming gains in CA scenarios with no SRS configured.
Downlink 8x8 MIMO is enabled when all of the following conditions are met:

eRAN
● 3D beamforming is enabled and the TM9Switch option of the

CellAlgoSwitch.EnhMIMOSwitch parameter is selected.
● The CellDlschAlgo.MaxMimoRankPara parameter is set to
SW_MAX_SM_RANK_8.
● The CellCsiRsParaCfg.CsiRsPortNum parameter is set to CSI_RS_PORT_8.
Assume that both downlink 8x8 MIMO and downlink 2CC aggregation are
enabled for cells. Then, each carrier of a CA UE supports a maximum of eight
layers only when the UE reports its support for eight layers on each carrier.
Otherwise, each carrier supports only a maximum of four layers. For details about
the UE-reported capabilities on carriers, see section 4.1 "ue-Category" in 3GPP TS
36.306.
6.3.2.1 Benefits
Deployment Suggestions
If the penetration rate of 4R or 8R TM9 UEs is high, you are advised to enable 4-
layer MIMO based on TM9 and SRS measurement as well as TM9 hybrid
precoding. 4R or 8R UEs that support 4-antenna selection can obtain the gains
provided by 4-layer MIMO based on TM9 and SRS measurement. 4R or 8R UEs
that do not support 4-antenna selection can obtain the gains provided by TM9
hybrid precoding.
Achievable Benefits
The benefits offered by TM9 are described as follows:
● Downlink 2-layer MIMO based on TM9: It increases the average downlink cell
throughput and average downlink cell spectral efficiency by transmitting two
data streams simultaneously.
● Downlink 4-layer MIMO based on TM9:
– It increases the average downlink cell throughput and average downlink
cell spectral efficiency by transmitting two to four data streams
simultaneously.
– In medium- or light-load scenarios, 4-layer MIMO based on TM9 and SRS
measurement increases the user-perceived rate in massive MIMO cells
and the rank of UEs that support 4-antenna selection.
● Downlink 8x8 MIMO: It increases the average downlink cell throughput and
average downlink cell spectral efficiency by transmitting two to eight data
streams simultaneously.
The average downlink cell throughput and average downlink cell spectral
efficiency are calculated as follows:
● Average downlink cell throughput = Cell Downlink Average Throughput
● Average downlink cell spectral efficiency = L.Thrp.bits.DL /
(L.Cell.DL.PDSCH.Tti.Num x L.ChMeas.PRB.DL.DrbUsed.Avg)

eRAN
6.3.2.2 Impacts
Network Impacts
● Downlink 2-layer MIMO based on TM9: none
● Downlink 4-layer MIMO based on TM9:
– Based on TM9 and PMI feedback: When the penetration rate of TM9 UEs
is low, negative impacts may be caused by increased overhead.
– Based on TM9 and SRS measurement: This function increases the amount
of data that can be scheduled in each TTI for UEs, reduces the delay, and
may increase the downlink PDCP traffic volume transmitted in the last
TTI before the buffer is empty. Therefore, this function increases the
average downlink cell throughput and downlink UE throughput
(including tail packets) but may decrease the downlink UE throughput
(excluding tail packets).
Delay: indicated by counters such as L.Thrp.Time.DL.RmvLastTTI,
L.Thrp.Time.DL, and L.Thrp.Time.Cell.DL.HighPrecision
Downlink PDCP traffic volume transmitted in the last TTI before the
buffer is empty = L.Thrp.bits.DL.LastTTI
Average downlink cell throughput = Cell Downlink Average Throughput
Downlink UE throughput (including tail packets) = L.Thrp.bits.DL /
L.Thrp.Time.DL
Downlink UE throughput (excluding tail packets) = (L.Thrp.bits.DL –
L.Thrp.bits.DL.LastTTI) / L.Thrp.Time.DL.RmvLastTTI
● Downlink 8x8 MIMO: As it requires the 8-port CSI-RS configuration, the
performance of UEs incapable of 8-port CSI-RS on the live network may
deteriorate.
Function Impacts
The following describes the function impacts of downlink 8x8 MIMO, downlink 2-
layer MIMO based on TM9 and downlink 4-layer MIMO based on TM9.

eRAN
Function Function Reference Description

Name Switch
Downlink 2CC None Carrier Downlink 8x8 MIMO and 4-

aggregation Aggregation layer MIMO based on TM9
and SRS measurement take
effect only for the following
UEs:
● UEs not in the CA state
● CA UEs in the downlink
2CC aggregation state
TM9 has the following impacts
on CA UEs in the downlink
2CC aggregation state.
If CSI-RS is configured for
SCCs with no SRS configured,
the UEs can obtain the CSI
based on CSI-RS measurement
and enter the TM9wPMI mode
on the SCCs, improving the
average cell throughput and
user experience.
Symbol power TddSymbolSh Energy In the subframes where

saving utdownSwitc Conservation symbol power saving is
h option of and Emission implemented, no PDSCH data
the Reduction is transmitted regardless of
ENodeBAlgoS whether the UE works in TM9
witch.PowerS or not, but CSI-RSs can be
aveSwitch transmitted for CSI
parameter measurements in TM9wPMI
mode.
Out-of-band OutOfBandR Relay In the out-of-band relay

relay elaySwitch network, when a downlink
option of the relay subframe conflicts with a
CellAlgoSwit subframe used for CSI-RS
ch.RelaySwit transmission, no CSI-RS is
ch parameter transmitted, ensuring that the
impact on ReBTS
transmissions is minimized. In
this case, TM9 services are
affected.
6.3.3 Requirements
6.3.3.1 Licenses
The following license must be purchased for TDLAOFD-00100114 DL 2-Layer
MIMO Based on TM9.

eRAN
Feature ID Feature Model Sales Unit

Name
TDLAOFD-00 LTE-A LT1SLTEAID01 per Cell

1001 Introduction
The following license must be purchased for TDLAOFD-081409 DL 4-Layer MIMO

Based on TM9.

Name
TDLAOFD-08 DL 4-Layer LT1S44TTM90 per Cell

1409 MIMO Based 0
on TM9
The following licenses must be purchased for TDLAOFD-130490 DL 8x8 MIMO.

Name
TDLAOFD-13 DL 8x8 MIMO LT1SDLMIMO per Cell

0490 08
6.3.3.2 Software
● Downlink 2-layer MIMO based on TM9 requires the following functions.

Name Switch
3D BfSwitch 6.1 3D This function requires 3D

beamformin option of the Beamformin beamforming.
g CellAlgoSwi g
tch.BfAlgoS
witch
parameter
3GPP R10 None None This function requires 3GPP

Specification Release 10 or later.
s

eRAN

Name Switch
Support of None None UE categories must support

UE a maximum of two, four, or
categories eight downlink spatial
multiplexing layers.
● Downlink 4-layer MIMO based on TM9 and PMI feedback requires the
Name Switch
Downlink 2- TM9Switch 6.3 TM9 This function requires

layer MIMO option of the downlink 2-layer MIMO
based on CellAlgoSwi based on TM9.
TM9 tch.EnhMIM
OSwitch
parameter

UE a maximum of four
categories downlink spatial
● Downlink 4-layer MIMO based on TM9 and SRS measurement requires the
Name Switch

TM9 tch.EnhMIM
OSwitch
parameter
SRS antenna MM_ANT_SE Massive This function requires that

selection L_ENH_SWIT MIMO antenna selection
CH option of Optimization enhancement for massive
the in WTTx MIMO be enabled.
CellMMAlgo Scenarios
.MMAlgoOp (TDD)
tSwitch
parameter
Number of Cell.CrsPort None This function requires that

reference Num set to the Cell.CrsPortNum
signal ports CRS_PORT_2 parameter be set to
CRS_PORT_2.

eRAN

Name Switch

UE a maximum of four
● Downlink 8x8 MIMO requires the following functions.

Name Switch

TM9 tch.EnhMIM
OSwitch
parameter

TM9 tch.EnhMIM
OSwitch
parameter

UE a maximum of eight

● Downlink 2-layer MIMO based on TM9 and downlink 4-layer MIMO based on
TM9 and PMI feedback are incompatible with the following functions.

Name Switch
High speed Cell.HighSpe High Speed None

mobility edFlag Mobility
Extended CP Cell.DlCyclic Extended CP If the TM9Switch option of
Prefix the
CellAlgoSwitch.EnhMIMOS
witch parameter is selected,
the Cell.DlCyclicPrefix
parameter cannot be set to
EXTENDED_CP.
Downlink None MIMO None

4x4 MIMO

eRAN
● Downlink 4-layer MIMO based on TM9 and SRS measurement is incompatible

with the following functions.
Name Switch

Prefix the
EXTENDED_CP.

4x4 MIMO
SRS resource SRSCfg.SrsR None None

extension esExpansion
Switch set to
SRS_RES_EX
PANSION_M
ODE
● Downlink 8x8 MIMO is incompatible with the following functions.

Name Switch

Prefix the
EXTENDED_CP.

4x4 MIMO
SFN cell Cell.MultiRr SFN None

uCellMode
6.3.3.3 Hardware
For details, see 4.3.3 Hardware. The UBBPem does not support 4-layer MIMO
based on TM9 and SRS measurement. If the CellBf.MaxBfRankPara parameter is

eRAN
set to FOUR_LAYER_BF for the UBBPem, the default value SINGLE_LAYER_BF

takes effect.
6.3.3.4 Others
UEs
Table 6-6 UE requirements

Function Name UE Requirement
Downlink 2-layer All of the following conditions are met:

MIMO based on ● The UE complies with 3GPP Release 10 or later.
TM9
● FGI103 or FGI104 is 1.
● At least two receive antennas are available.
● The UE category is greater than or equal to 2.

MIMO based on ● The UE complies with 3GPP Release 10 or later.
TM9 and PMI
feedback ● FGI103 or FGI104 is 1.
● At least four receive antennas are available.
● The UE category is greater than or equal to 5, and the
value of MIMO-CapabilityDL-r10 is fourLayers or
eightLayers.
● The UE supports TBS optimization for MIMO if it requires
this function.
If the capability information reported by the UE shows
that the value of alternativeTBS-Indices-r12 is true, the
UE supports TBS optimization.

MIMO based on ● FGI103 or FGI104 is 1.
TM9 and SRS
measurement ● At least four receive antennas are available.
● The UE supports 4-antenna selection in 1CC or in-band
contiguous 2CC CA scenarios.
● The value of pmi-Disabling-r10 is true.
● The UE category is greater than or equal to 5, and the
value of MIMO-CapabilityDL-r10 is eightLayers.

eRAN
Function Name UE Requirement
Downlink 8x8 All of the following conditions are met:

MIMO ● The UE complies with 3GPP Release 10 or later.
● FGI103 or FGI104 is 1.
● The UE category is 8, 14, 17, 18, or 19, and the value of
MIMO-CapabilityDL-r10 is eightLayers.
● The UE supports the function of TBS optimization
function for MIMO UEs if it requires this function.
If the capability information reported by the UE shows
that the value of alternativeTBS-Indices-r12 is true, the
UE supports TBS optimization.

The following table describes the parameters that must be configured for 2-layer
MIMO based on TM9 and SRS measurement as well as MIMO based on TM9 and
PMI feedback in massive MIMO cells.
Table 6-7 Parameters used for activation of 2-layer MIMO based on TM9 and SRS
measurement as well as 2/4/8-layer MIMO based on TM9 and PMI feedback
Name
Enhanced CellAlgoSwitch.EnhMI To enable TM9, select the

MIMO Switch MOSwitch TM9Switch option.
Maximum CellDlschAlgo.MaxMi ● For 2-layer MIMO based on TM9,

Number of moRankPara set this parameter to
MIMO Layers SW_MAX_SM_RANK_2.
● For 4-layer MIMO based on TM9,
set this parameter to
SW_MAX_SM_RANK_4.
● For 8-layer MIMO based on TM9,
set this parameter to
SW_MAX_SM_RANK_8.

eRAN

Name
CSI-RS CellDlschAlgo.CsiRsSfS It is recommended that the

Subframe chStrSwitch UnCfgCsiRsUESchSwitch option be
Scheduling deselected when TM9 is enabled so
Strategy Switch that 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
UnCfgCsiRsUEDeOrderSchSwitch
option be selected.
If TM9 hybrid precoding is enabled,
deselect the UnCfgCsiRsUEDeOr-
derSchSwitch option.
CSI-RS Switch CellCsiRsParaCfg.CsiRs ● If TM9 is enabled, set this

Switch parameter to FIXED_CFG.
● If TM9 is disabled, set this
parameter to NOT_CFG.
CsiRs Port CellCsiRsParaCfg.CsiRs Set this parameter to

Number PortNum CSI_RS_PORT_4 or CSI_RS_PORT_8.
Set this parameter to
CSI_RS_PORT_8 when downlink 8x8
MIMO is enabled in a massive
MIMO cell.
CSI-RS Period CellCsiRsParaCfg.CsiRs Set this parameter to ms80. The cell

Period will reset if the value is changed.
Compatibility ENodeBAlgoSwitch.Co To configure the CSI-RS policy for

Control Switch mpatibilityCtrlSwitch TM9-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
protocols. If not, deselect the
UeCsiRsCfigCtrlSwitch option.
Operator ENodeBAlgoSwitch.Op This parameter is valid only when

Specific eratorSpecificAlgoS- the UeCsiRsCfigCtrlSwitch option
Algorithm witch of the CompatibilityCtrlSwitch
Switch parameter is selected.

eRAN

Name
Scc Bf Mimo CellBfMimoParaCfg.Sc Set this parameter to ON when

Adaptive cBfMimoAdaptiveS- TM9wPMI is required in downlink
Switch witch CA scenarios or when uplink CA is
enabled.
LCS switch ENodeBAlgoSwitch.Lcs Deselect the OtdoaSwitch option.

Switch
TM3 Rank2 To CellBfMimoParaCfg.T Set this parameter to 9.
TM9 Rank4 m3Rank2ToTm9Rank4
Offset Offset
TM9 Rank4 To CellBfMimoParaCfg.T Set this parameter to 40.
TM3 Rank2 m9Rank4ToTm3Rank2
Offset Offset
256QAM TM3 CellBfMimoParaCfg.T Set this parameter to 60.
to TM9 m3ToTm9SwtgSEffOfs
Switching 256qam
Spectral Eff
Offset
256QAM TM9 CellBfMimoParaCfg.T Set this parameter to 75.

to TM3 m9ToTm3SwtgSEffOfs
Switching 256qam
Spectral Eff
Offset
TM3 and TM9 CellBfMimoParaCfg.T Set this parameter to -30.

Switching m3AndTm9ThdOffset
Threshold
Offset
The following table describes the parameters that must be configured for 4-layer
MIMO based on TM9 and SRS measurement in massive MIMO cells.
Table 6-8 Parameters used for activation of 4-layer MIMO based on TM9 and SRS
measurement
Name
Enhanced CellAlgoSwitch.EnhMI To enable TM9, select the

MIMO Switch MOSwitch TM9Switch option.
Beamforming CellBf.MaxBfRankPara Set this parameter to

maximum FOUR_LAYER_BF.
number of
layers

eRAN

Name
Dual-Stream CellBf.DualStreamBfAl To improve TM9 performance, it is

BF Algorithm goSw recommended that the
Switch ACK_FEEDBACK_IN_MUX_MODE_S
W option be selected.
Harq CellAlgoSwitch.HarqAl To improve TM9 performance, it is

Algorithm goSwitch recommended that the
Switch TddAckFbModeCfgOptSwitch
option be selected.
Activation Command Examples (Using 4-Layer MIMO Based on TM9 and

PMI Feedback as an Example)
//Turning on the TM9 switch
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,
Tm3AndTm9ThdOffset=-30;
//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 TM9wPMI is
required in downlink CA scenarios or uplink CA is enabled
MOD CELLBFMIMOPARACFG: LocalCellId=0, SccBfMimoAdaptiveSwitch=ON;
//Disabling OTDOA
MOD ENODEBALGOSWITCH: LcsSwitch=OtdoaSwitch-0;
Activation Command Examples (Using 4-Layer MIMO Based on TM9 and SRS
Measurement as an Example)
//Turning on the TM9 switch
//Configuring the maximum number of beamforming layers
MOD CELLBF: LocalCellId=0, MaxBfRankPara=FOUR_LAYER_BF;
//Enabling ACK feedback in multiplexing mode
MOD CELLBF: LocalCellId=0, DualStreamBfAlgoSw=ACK_FEEDBACK_IN_MUX_MODE_SW-1;

eRAN
//Enabling HARQ feedback optimization

MOD CELLALGOSWITCH: LocalCellId=0, HarqAlgoSwitch=TddAckFbModeCfgOptSwitch-1;
Deactivation Command Examples (Using 4-Layer MIMO Based on TM9 and

PMI Feedback as an Example)
//Setting the CellCsiRsParaCfg.CsiRsSwitch parameter to NOT_CFG before turning off the TM9 switch
MOD CELLCSIRSPARACFG: LocalCellId=0, CsiRsSwitch= NOT_CFG;
Deactivation Command Examples (Using 4-Layer MIMO Based on TM9 and

SRS Measurement as an Example)
//Deactivating 4-layer MIMO based on TM9 and SRS measurement
MOD CELLBF: LocalCellId=0, MaxBfRankPara=DUAL_LAYER_BF;

For detailed operations, see Feature Configuration Using the MAE-Deployment.
Using Signaling
UEs must access the network again to make TM9 take effect after the TM9 switch
is turned on.
After UEs access the network again, check the RRC_CONN_RECFG message in the
Uu interface tracing result on the MAE-Access, as shown in Figure 6-12 and
Figure 6-13.
● If the transmissionMode IE value is TM9, TM9 has taken effect.
● If the pmi-RI-Report-r9 IE is present, TM9 dependent on PMI feedback has
taken effect. If this IE is absent, TM9 dependent on SRS measurement has
taken effect.
● If the maxLayersMIMO-r10 IE value is twoLayers, a maximum of two layers
are supported. If the IE value is fourLayers, a maximum of four layers are
supported. If the IE value is eightLayers, a maximum of eight layers are
supported.

eRAN
Figure 6-12 Tracing result (1)
Figure 6-13 Tracing result (2)
Using Counters
Observe the following counters to check whether TM9 has taken effect. If the
value of the counter in Table 6-9 is not 0, TM9 has taken effect.
Table 6-9 Number of UEs in a cell

1526732723 L.Traffic.User.TM9.Avg
Observe the following counters. TM9 dependent on SRS measurement has taken
effect if any of the open-loop counters in Table 6-10 has a non-zero value. TM9
dependent on PMI feedback has taken effect if any of the closed-loop counters in
Table 6-11 has a non-zero value.

eRAN
Table 6-10 Counters for TM9 dependent on SRS measurement

Table 6-11 Counters for TM9 dependent on PMI feedback

1526746774 to 1526746777 L.ChMeas.MIMO.PRB.CL.Rank5 to

L.ChMeas.MIMO.PRB.CL.Rank8

Monitor resource usages in TM9 based on the following counters.
1526747680 L.Traffic.User.SCell.Active.DL.TM9.Avg
1526747879 L.Traffic.User.TM9Capability.Avg
1526747668 L.Traffic.DL.SCH.TB.TM9
1526747669 L.Traffic.DL.SCH.TB.TM9.bits
1526747670 L.Traffic.DL.SCH.TB.Retrans.TM9.bits
1526732737 L.ChMeas.RI.Rank3
1526732738 L.ChMeas.RI.Rank4

eRAN
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:
● TDLAOFD-130490 DL 8x8 MIMO
NOTE
For the principles of the preceding features, see Beamforming (TDD).
TM9 hybrid precoding has the following two functions:

● Double weighting for closed-loop TM9 UEs
This function is controlled by the TM9HybridPrecodingSwitch option of the
CellAlgoSwitch.EnhMIMOSwitch parameter.
– Horizontal-plane weighting: A beam is divided into multiple orthogonal
beams in the horizontal plane based on designed orthogonal weight
values, and each beam is configured with independent measurable CSI-
RS. The eNodeB selects the weight values with the best beamforming
capability based on channel conditions.
– Vertical-plane weighting: Beamforming is performed in the vertical plane
based on PMI feedback.
When the CellCsiRsParaCfg.CsiRsPortNum parameter is set to
CSI_RS_PORT_4, 4-port TM9 hybrid precoding is enabled.
● Split SDMA pairing of closed-loop TM9 UEs on SCCs (trial)
Rank 1 and rank 2 closed-loop TM9 UEs on SCCs can participate in split
SDMA pairing if both multi-user split SDMA and double weighting on closed-
loop TM9 UEs are enabled and the TM9SplitSdmaSwitch option of the
CellAlgoSwitch.MuBfAlgoSwitch parameter is selected. For details, see 6.5
Multi-User Split SDMA. Other closed-loop TM9 UEs do not participate in
split SDMA pairing.
If TM9 hybrid precoding is enabled for TDD carriers in CA+massive MIMO
scenarios, then:
● It is recommended that beamforming in SCells be enabled so that CA UEs
with no SRS reported can enter the TM9wPMI mode in their TDD SCells when
required conditions are met. In this way, the UEs obtain the gains provided by

eRAN
TM9 hybrid precoding and the average cell throughput increases. For details
about beamforming in SCells, see Carrier Aggregation.
● If beamforming in SCells is not enabled or does not take effect because
required conditions are not met, CA UEs with no SRS reported cannot enter
the TM9wPMI mode but can work only in TM3 in TDD SCells. For the required
conditions, see Carrier Aggregation.
Multi-user split SDMA also needs to be enabled if 4-port TM9 hybrid precoding
needs to work with multi-user split SDMA.
NOTE
Trial functions are functions 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 functions can still be used for testing purposes or commercial network
trials. Anyone who desires to use the trial functions shall contact Huawei and enter into a
memorandum of understanding (MoU) with Huawei prior to an official application of such
trial functions. Trial functions are not for sale in the current version but customers may try
them for free.
Customers acknowledge and undertake that trial functions may have a certain degree of
risk due to absence of commercial testing. Before using them, customers shall fully
understand not only the expected benefits of such trial functions but also the possible
impact they may exert on the network. In addition, customers acknowledge and undertake
that since trial functions are free, Huawei is not liable for any trial function malfunctions or
any losses incurred by using the trial functions. Huawei does not promise that problems
with trial functions will be resolved in the current version. Huawei reserves the rights to
convert trial functions into commercial functions in later R/C versions. If trial functions are
converted into commercial functions in a later version, customers shall pay a licensing fee
to obtain the relevant licenses prior to using the said commercial functions. If a customer
fails to purchase such a license, the trial function(s) will be invalidated automatically when
the product is upgraded.
6.4.2.1 Benefits
Deployment Suggestions
4-port TM9 hybrid precoding is recommended when UEs meet all of the following
conditions:
● Support 4R or 8R.
● Support 4-port TM9 and have a penetration rate higher than the
CellCsiRsParaCfg.CsiRsConfigUserRatioTh parameter value (recommended
value: 30).
● Camp on the cell center or at a medium distance from the cell center.
Achievable Benefits
TM9 hybrid precoding offers the following benefits:
● Increases the downlink user-perceived rate (User Downlink Average
Throughput) in massive MIMO cells in medium- and light-load scenarios.
● Increases the downlink user-perceived rate (User Downlink Average
Throughput) in massive MIMO cells in CA scenarios.

eRAN
● Increases the proportion of high ranks for 4R or 8R TM9 UEs.
6.4.2.2 Impacts
Network Impacts
4-port TM9 hybrid precoding has the following network impacts:
● There may be negative impacts due to CSI-RS overhead when the proportion
of TM9 UEs is low.
● In areas at a medium distance from the cell center, the gains obtained by 8R
UEs are not as obvious as those obtained by 4R UEs.
● After TM9 hybrid precoding is enabled, the proportion of PDCCH DTXs, IBLER,
and RBLER fluctuate, and the air interface signaling may increase due to CSI-
RS resource configuration messages (in RRC connection reconfiguration
messages).
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) x 100%

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

in SCells option of the Aggregation scenarios, the PCC
CellAlgoSwitch.NoSrs supports TM9 hybrid
SccBfAlgoSwitch precoding. The
parameter support of SCCs for
TM9 hybrid precoding
is as follows:
● If uplink CA is
enabled, uplink
SCCs also support
TM9 hybrid
precoding.
● If uplink CA is not
enabled and
beamforming in
SCells is enabled,
SCCs without SRS
feedback support
TM9 hybrid
precoding.
● If neither uplink CA
nor beamforming
in SCells is enabled,
SCells do not
support TM9
hybrid precoding.
TM9 port 5 Tm9Port5Switch Massive When TM9 hybrid

option of the MIMO precoding is enabled,
UeCooperationPara.S Optimization the TM9 port 5
pecUserCooperationS in WTTx function does not
witch parameter Scenarios forcibly switch UEs to
(TDD) TM7 and allows UEs
to stay in closed-loop
TM9 mode.
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
Massive Cell.TxRxMode set to 4 Basic None

MIMO 32T32R or 64T64R Massive
introduction MIMO
Functions
Downlink 2- TM9Switch option of 6.3 TM9 When the

layer MIMO the CellDlschAlgo.MaxMi
based on TM9 CellAlgoSwitch.EnhM moRankPara
IMOSwitch parameter is set to
parameter SW_MAX_SM_RANK_
2, up to rank 2 in
TM9wPMI mode is
supported.
Downlink 4- TM9Switch option of 6.3 TM9 When the

layer MIMO the CellDlschAlgo.MaxMi
based on TM9 CellAlgoSwitch.EnhM moRankPara
IMOSwitch parameter is set to
parameter SW_MAX_SM_RANK_
4, up to rank 4 in
TM9wPMI mode is
supported.

eRAN

Name
PDSCH Split CellBf.PdschSplitBea None For 4-port TM9 hybrid

Beam Config mConfigIndex precoding, the
Index CellBf.PdschSplitBea
mConfigIndex
parameter can be set
to a value in the
range of
CONFIG_DEFAULT to
CONFIG_INDEX3.
These parameter
values correspond to
the gradually
decreased numbers of
beams and gradually
decreased PDSCH
coverage areas. The
recommended value is
CONFIG_DEFAULT.
Assume that a cell is
activated and the
CellBf.PdschSplitBea
mConfigIndex
parameter is set to
CONFIG_INDEX4.
Then, if the
CellCsiRsParaCfg.CsiR
sPortNum parameter
needs to be set to
CSI_RS_PORT_8, the
TM9HybridPrecoding
Switch option of the
CellAlgoSwitch.EnhM
IMOSwitch
parameter needs to
be deselected first.

Name
Scheduling of UnCfgCsiRsUESchS- None TM9 hybrid precoding

CSI-RS- witch option of the cannot be enabled
unconfigured CellDlschAlgo.CsiRsSf when scheduling of
UEs SchStrSwitch CSI-RS-unconfigured
parameter UEs is enabled.

eRAN

Name
Scheduling of UnCfgCsiRsUEDeOr- None TM9 hybrid precoding

CSI-RS- derSchSwitch option cannot be enabled
unconfigured of the when scheduling of
UEs through CellDlschAlgo.CsiRsSf CSI-RS-unconfigured
MCS index SchStrSwitch UEs through MCS
reduction parameter index reduction is
enabled.
CSI-RS period CellCsiRsParaCfg.CsiR None If the

sPeriod CellCsiRsParaCfg.CsiR
sPeriod parameter is
set to ms5 and the
CellCsiRsParaCfg.CsiR
sPortNum parameter
is set to
CSI_RS_PORT_4, the
TM9HybridPrecoding
Switch option of the
CellAlgoSwitch.EnhM
IMOSwitch
parameter cannot be
selected.
6.4.3.3 Hardware
For details, see 4.3.3 Hardware. If the UBBPg3b is configured to support both LTE
TDD and NR, it does not support the TM9 hybrid precoding function.

If TM9 hybrid precoding is required in massive MIMO cells where TM9 has been
enabled, the following parameters need to be configured.
Table 6-12 Parameters used for activation of 4-port TM9 hybrid precoding
Enhanced MIMO Switch CellAlgoSwitch.EnhMIM Select the

OSwitch TM9HybridPrecodingS-
witch option.

eRAN
CsiRs Port Number CellCsiRsParaCfg.CsiRsP If 4-port TM9 hybrid

ortNum precoding is required, set
the
CellCsiRsParaCfg.CsiRsP
ortNum parameter to
CSI_RS_PORT_4. In this
case, up to rank 4 in
TM9wPMI mode is
supported.
CSI-RS Switch CellCsiRsParaCfg.CsiRsS The value

witch ADAPTIVE_CFG is
recommended.
If this parameter is set to
ADAPTIVE_CFG or
FIXED_CFG, only 4-port
CSI-RSs are transmitted
in the cell.
When the CellCsiRsParaCfg.CsiRsSwitch parameter is set to ADAPTIVE_CFG,

adaptation-related thresholds may not be the optimal and therefore may require
optimization. Conduct network tests, and observe the signaling overhead and the
increase in the average cell throughput after TM9 hybrid precoding is enabled.
Then, adjust the values of the following parameters to reduce the signaling
overhead and increase the average cell throughput.
Table 6-13 Parameter used for optimization
CSI-RS Config User CellCsiRsParaCfg.CsiRsC Set this parameter to 1.

Number Threshold onfigUserNumTh
CSI-RS Unconfig User CellCsiRsParaCfg.CsiRsU Set this parameter to 1.
Number Threshold nconfigUserNumTh
CSI-RS Config User Ratio CellCsiRsParaCfg.CsiRsC Set this parameter to 30
Threshold onfigUserRatioTh when the
ortNum parameter is set
to CSI_RS_PORT_4.
CSI-RS Unconfig User CellCsiRsParaCfg.CsiRsU Set this parameter to 20

Ratio Threshold nconfigUserRatioTh when the
ortNum parameter is set
to CSI_RS_PORT_4.
CSI-RS Set Judge Timer CellCsiRsParaCfg.CsiRsS Set this parameter to

etJudgeTimer 3600.

eRAN
CSI-RS Set Judge CellCsiRsParaCfg.CsiRsS Set this parameter to

Hysteresis Timer etJudgeHysTimer 600.
BfMimo Algorithm CellBfMimoParaCfg.Bf It is recommended that

Optimization Switch MimoAlgoOptSwitch the
LOAD_BASED_TMA_OPT
_SW option be selected
to accelerate the entry of
4R UEs into closed-loop
TM9. Under this setting,
UEs with poor
performance in closed-
loop TM9 can quickly
exit this mode to reduce
the IBLER and service
drop rate.
NOTICE
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.

Enable 4-port TM9 hybrid precoding:
//Setting the CSI-RS switch
MOD CELLCSIRSPARACFG: LocalCellId=0, CsiRsSwitch=FIXED_CFG, CsiRsPeriod=ms80,
CsiRsPortNum=CSI_RS_PORT_4;
//Enabling TM9 hybrid precoding
MOD CELLALGOSWITCH: LocalCellId=0, EnhMIMOSwitch=TM9HybridPrecodingSwitch-1;
Optimization Command Examples

Optimize 4-port TM9 hybrid precoding:
//(Optional) Adjusting CSI-RS-related parameters if the CellCsiRsParaCfg.CsiRsSwitch parameter is set to
ADAPTIVE_CFG
MOD CELLCSIRSPARACFG: LocalCellId=0, CsiRsSwitch=ADAPTIVE_CFG, CsiRsConfigUserNumTh=1,
CsiRsUnconfigUserNumTh=1, CsiRsConfigUserRatioTh=30, CsiRsUnconfigUserRatioTh=20,
CsiRsSetJudgeHysTimer=3600, CsiRsSetJudgeTimer=600;
// (Optional, recommended) Selecting the LOAD_BASED_TMA_OPT_SW option of the
CellBfMimoParaCfg.BfMimoAlgoOptSwitch parameter to accelerate the entry of 4R UEs into closed-loop
TM9. Under this setting, UEs with poor performance in closed-loop TM9 can quickly exit this mode to
reduce the IBLER and service drop rate.
MOD CELLBFMIMOPARACFG: LocalCellId=0, BfMimoAlgoOptSwitch=LOAD_BASED_TMA_OPT_SW-1;

eRAN

//Disabling TM9 hybrid precoding
MOD CELLALGOSWITCH: LocalCellId=0, EnhMIMOSwitch=TM9HybridPrecodingSwitch-0;

Maintenance.

● 4-port TM9 hybrid precoding
Run the DSP CELLCSIRSPARACFG command and query the CsiRs State. If the
result is Normal, hybrid precoding has taken effect. In this case, only 4-port
CSI-RSs are transmitted in the cell.

Monitor the counters listed in Table 6-14 if 4-port TM9 hybrid precoding is
configured for a cell.
Table 6-14 Counters used to monitor 4-port TM9 hybrid precoding

Counter ID Counter Name Observation
Purpose
1526728261 L.Thrp.bits.DL Used to calculate the

User Downlink
1526729005 L.Thrp.bits.DL.LastTTI Average
1526729015 L.Thrp.Time.DL.RmvLastTTI Throughput.
1526732737 L.ChMeas.RI.Rank3 Used to measure the

proportion of times a
1526732738 L.ChMeas.RI.Rank4 rank is reported in
closed-loop TM9.
1526728174 L.ChMeas.MIMO.PRB.CL.Rank3 Used to measure the

proportion of RBs
1526728175 L.ChMeas.MIMO.PRB.CL.Rank4 scheduled in closed-
loop TM9.

eRAN
Counter ID Counter Name Observation

Purpose
1526732723 L.Traffic.User.TM9.Avg Used to measure the

number of UEs that
finally enter the TM9
mode.
1526747879 L.Traffic.User.TM9Capability.Av Used to measure the

g proportion of TM9-
capable UEs.
1526747668 L.Traffic.DL.SCH.TB.TM9 Used to measure the

percentage of TBs in
TM9.
1526747667 L.ChMeas.PRB.TM9 Used to measure the

total number of PRBs
used in TM9.
6.5 Multi-User Split SDMA

This section describes TDLEOFD-131612 Multi-User Split SDMA in Massive MIMO.
6.5.1 Principles
Multi-user split SDMA is a capacity enhancement feature based on MU
beamforming. It implements spatial multiplexing by means of PDSCH beam
splitting. It improves the downlink service performance of massive MIMO cells in
certain scenarios, for example, when moving UEs need to be served and SRS
interference needs to be handled.
It is recommended that the multi-user split SDMA feature be used with 4-port
TM9 hybrid precoding (as described in 6.4 TM9 Hybrid Precoding) so that this
feature can take effect on closed-loop TM9 rank 1 and rank 2 UEs on SCCs. In this
way, downlink service performance improves in densely populated urban areas
with strong coverage.
This feature is controlled by the SplitSdmaSwitch option of 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.

eRAN
If... Then...
The CellBf.SplitSdmaAdaptionPeriod Adaptive switching between MU

parameter is not set to beamforming and multi-user split
FORCE_SPLIT_SDMA SDMA is supported. The eNodeB
enters or exits multi-user split SDMA
based on the principles described in
Table 6-15 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-

parameter is set to user split SDMA without identifying
FORCE_SPLIT_SDMA application scenarios.
Table 6-15 Mechanism for entering and exiting multi-user split SDMA
Whether 4-Port Entering or Condition
TM9 Hybrid Exiting Multi-
Precoding Is User Split SDMA
Enabled
Yes Entered Any of the following conditions is met:

● Proportion of UEs with limited SRS
resources in a cell ≥
CellMMAlgo.ASplitSdmaSrsLm-
tUePropThld
● Proportion of closed-loop TM9 UEs
≥
CellMMAlgo.ASplitSdmaTm9UePr
opThld
Exited All the following conditions are met:
● Proportion of UEs with limited SRS
resources in a cell <
CellMMAlgo.ASplitSdmaSrsLm-
tUePropThld
● Proportion of closed-loop TM9 UEs
<
CellMMAlgo.ASplitSdmaTm9UePr
opThld
No Entered Proportion of UEs with limited SRS
resources in a cell ≥
CellMMAlgo.ASplitSdmaSrsLmtUe-
PropThld

eRAN
Whether 4-Port Entering or Condition

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

resources in a cell <
CellMMAlgo.ASplitSdmaSrsLmtUe-
PropThld
NOTE
● UEs with limited SRS resources include moving UEs and UEs subject to SRS interference.
● A UE is identified as the UE subject 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 subject to
limited SRS resources. Other UEs belong to normal UEs.
2. The eNodeB periodically determines the target beams.
a. The eNodeB measures the RSRP values of downlink split beams based on
uplink SRS quality and regards the beams with the largest RSRP as the
target beams of the UEs.
b. The eNodeB obtains the complete beam weight coefficients of the
horizontal and vertical planes based on the attributes of the target
beams.
The weight coefficients are 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
coefficients are obtained through MU beamforming for normal UEs.
3. During resource allocation, the eNodeB pairs UEs subject to limited SRS
resources, closed-loop TM9 rank 1 and rank 2 UEs on SCCs, and normal UEs in
hybrid mode. All UEs participate in spatial multiplexing. Figure 6-14 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
If... Then...
The TM9HybridPrecodingSwitch Closed-loop TM9 UEs support only

option of the single-UE scheduling and do not
CellAlgoSwitch.EnhMIMOSwitch participate in split SDMA pairing.
parameter is selected but the
TM9SplitSdmaSwitch option of
the
CellAlgoSwitch.MuBfAlgoSwitch
parameter is deselected

eRAN
If... Then...
Both the TM9HybridPrecodingS- ● Closed-loop TM9 rank 1 and

witch option of the rank 2 UEs on SCCs support
CellAlgoSwitch.EnhMIMOSwitch split SDMA and participate in
parameter and the split SDMA pairing.
TM9SplitSdmaSwitch option of ● Other closed-loop TM9 UEs
the support only single-UE
CellAlgoSwitch.MuBfAlgoSwitch scheduling and do not
parameter are selected participate in split SDMA
pairing.
The maximum number of paired
layers allowed for closed-loop
TM9 rank 1 and rank 2 UEs on
SCCs cannot exceed the value of
the CellBf.HighOrderMubfMax-
Layer parameter or 4.
– For UEs subject to limited SRS resources, split SDMA can be used. These
UEs can participate in split SDMA pairing.
– For normal UEs, MU beamforming is used. These UEs can be paired with
UEs subject to limited SRS resources or closed-loop TM9 rank 1 and rank
2 UEs on SCCs for spatial multiplexing
Figure 6-14 Hybrid pairing for multi-user split SDMA
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.

eRAN
Application Scenario Description
Strong coverage Characteristics: strong capacity demand, high user

scenarios, such as density, and scattered user distribution
central business In such scenarios, multi-user split SDMA improves the
districts (CBDs) and number of paired layers for closed-loop TM9 rank 1
campuses and rank 2 UEs on SCCs.
Mobility scenarios, Characteristics: heavy traffic, strong capacity demand

such as traffic hubs in the uplink and downlink, high user density,
and rally scenarios scattered user 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,

SRS resources, such as and 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
areas pairing performance regardless of SRS weight
estimation.
The following counters can be used to evaluate the
SRS interference in the local cell:
● 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)
6.5.2.2 Impacts
Network Impacts
● This function improves the average downlink spectral efficiency of the cell.

eRAN
● This function improves the average downlink user-perceived rate.

● 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.BfWeightOptD 7.6 After beamforming

weight egreeFactor Beamformin weight optimization is
optimization g Weight enabled, UEs with low
Optimization SRS SINRs will not
enter multi-user split
SDMA. UEs with low
SRS SINRs already in
multi-user split SDMA
mode will exit this
mode.
Split SDMA CellBf.MovingUeMuB None If multi-user split

for moving fScheme SDMA for moving UEs
UEs is enabled, set the
CellBf.MovingUeMuB
fScheme parameter
to
SPLIT_SDMA_SCHEM
E to improve the
throughput of moving
UEs.
6.5.3 Requirements
6.5.3.1 Licenses
TDLEOFD-131 Multi-User Split LT4SMUSSM Per Cell

612 SDMA in Massive M00
MIMO
6.5.3.2 Software

eRAN
Name
TM9 hybrid TM9HybridPrecoding 6.4 TM9 If multi-user split

precoding Switch option of the Hybrid SDMA is required for
CellAlgoSwitch.EnhM Precoding closed-loop TM9 UEs,
IMOSwitch 4-port TM9 hybrid
parameter and precoding must be
TM9SplitSdmaSwitch enabled.
option of the
CellAlgoSwitch.MuBf
AlgoSwitch
parameter
Downlink 8- MuBfSwitch option of 6.2 MU Multi-user split SDMA

layer MU the Beamformin requires either of the
beamforming CellAlgoSwitch.MuBf g functions.
and downlink AlgoSwitch
16-layer MU parameter
beamforming

Name
Moving UE CellBf.MovingUeMuB None The

MU fScheme CellBf.MovingUeMuB
beamforming fScheme parameter
scheme can be set to
BIG_EVENT_PROTECT
_SCHEME,
HEAVY_LOAD_SCHE
ME,
LIGHT_LOAD_SCHEM
E, or
HIGH_SPEED_OPT_SC
HEME only when the
SplitSdmaSwitch
option of the
CellAlgoSwitch.MuBf
AlgoSwitch
parameter is
deselected.

eRAN

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

layer MU the Beamformin is not supported when
beamforming CellAlgoSwitch.MuBf g the number of layers
AlgoSwitch specified by the
parameter CellBf.HighOrderMu
bfMaxLayer
parameter is greater
than 16.
UE pairing for CellBf.MassiveMIMO 6.2 MU If both of the

MU MubfPairRule Beamformin following conditions
beamforming g are met, the
without CellBf.MassiveMIMO
considering MubfPairRule
correlation parameter can be set
to
MU_WITHOUT_CORR
_PAIR_RULE, but UE
pairing for MU
beamforming without
considering
correlation does not
take effect:
● The
SplitSdmaSwitch
or
TM9SplitSdmaSwi
tch option of the
CellAlgoSwitch.M
uBfAlgoSwitch
parameter is
selected.
● Multi-user split
SDMA is triggered.
SRS- SRSCfg.SrsResExpansi 7.15 SRS- SRS-expansion-based

expansion- onSwitch set to Expansion- precise beamforming
based precise SRS_RES_EXPANSION based Precise is not compatible with
beamforming _MODE Beamformin split SDMA in
g movement scenarios.
6.5.3.3 Hardware
For details, see 4.3.3 Hardware. If the UBBPg3b is configured to support both LTE
TDD and NR, it does not support multi-user split SDMA.

eRAN

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

Name
MUBF CellAlgoSwitch.MuBf Select the SplitSDMASwitch option.

Algorithm AlgoSwitch
Switch
PDSCH Split CellBf.PdschSplitBea The values CONFIG_DEFAULT to

Beam Config mConfigIndex CONFIG_INDEX3 correspond to the
Index gradually decreased numbers of beams
and gradually decreased PDSCH
coverage areas. The value
CONFIG_DEFAULT is recommended.
NOTE
If the parameter is adjusted, cell
reactivation will be triggered to make the
modification take effect.
Split SDMA CellBf.SplitSdmaAda ● Split SDMA is triggered directly

Adaption ptionPeriod when this parameter is set to
Period FORCE_SPLIT_SDMA.
● 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.

eRAN

Name
Moving Ue CellBf.MovingUeMuB It is recommended that this parameter

MUBF fScheme be set to SPLIT_SDMA_SCHEME to
Scheme improve the throughput of moving
UEs, if any.
The SPLIT_SDMA_SCHEME option
takes effect when the
SRS_LMT_AND_ABN_UE_IDENT_SW
option of the
CellBf.UeIdentificationSwitch
Adaptive Split CellMMAlgo.ASplitSd Set this parameter to 10.

SDMA SRS maSrsLmtUePropThl
Limit UE Prop d
Thld
Adaptive Split CellMMAlgo.ASplitSd Set this parameter to 10.

SDMA TM9 maTm9UePropThld
UE Proportion
Thld
Split SDMA CellMMAlgo.SplitSd Set this parameter to -12.

UE maUeIdenSrsSinrThl
Identification d
SRS SINR Thld
Enhanced CellAlgoSwitch.EnhM To allow closed-loop TM9 UEs to

MIMO Switch IMOSwitch participate in single-UE scheduling for
split SDMA but not UE pairing for split
SDMA, select the
TM9HybridPrecodingSwitch option
and deselect the
TM9SplitSdmaSwitch option of the
CellAlgoSwitch.MuBfAlgoSwitch
parameter.
MUBF CellAlgoSwitch.MuBf To allow closed-loop TM9 rank 1 and

Algorithm AlgoSwitch rank 2 UEs on SCCs to participate in
Switch UE pairing for split SDMA, select the
TM9SplitSdmaSwitch option.

eRAN

Name
Split SDMA CellMMAlgo.SplitSd Set this parameter based on the

Beam RSRP maBeamRsrpIsltnThl network plan.
Isolation d ● A larger value of this parameter
Threshold leads to 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
paired layers in the cell.
● 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
paired layers in the cell.
NOTICE
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 multi-user split SDMA will lead to cell faults.
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;

eRAN

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

Maintenance.

You can monitor the following counters to check whether multi-user split SDMA
takes effect.
1526746985 L.ChMeas.MassiveMIMO.SplitSdma.Avg.PairLayer
You can perform signaling tracing on the MAE-Access to check whether multi-user
split SDMA takes effect. For details, see the 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.1stLayer.PairPRB.Tot
1526739778~152673978 L.ChMeas.MUBF.2ndLayer.PairPRB.Succ to
0 L.ChMeas.MUBF.4thLayer.PairPRB.Succ
1526745726~152674573 L.ChMeas.MUBF.5thLayer.PairPRB.Succ to
7 L.ChMeas.MUBF.16thLayer.PairPRB.Succ
1526745707 L.ChMeas.DL.Succ.Pair.TTI
1526745708 L.ChMeas.MassiveMIMO.MUBF.Avg.PairLayer

eRAN
1526746985 L.ChMeas.MassiveMIMO.SplitSdma.Avg.PairLayer
1526747879 L.Traffic.User.TM9Capability.Avg
Monitoring Through Signaling Tracing

● Cell-level MU beamforming monitoring: to monitor MU beamforming pairing
in a cell
a. On the MAE-Access, choose Monitor > Signaling Trace > Signaling
Trace Management.
b. In 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.
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.
● 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 MAE-Access, choose Monitor > Signaling Trace > Signaling
Trace Management.
b. In the navigation tree on the left of the Signaling Trace Management
tab page, choose 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 MAE-Access.
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 (dBm). For the detailed
description of the monitoring result, press F1 to obtain the online help.

eRAN

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 hardware and license requirements in 6.5.3 Requirements are
met.
Step 2 Check whether parameters are properly set by referring to 6.5.4.1.1 Data
Preparation.
----End
6.6 PDCCH SDMA

This section describes TDLEOFD-121613 PDCCH SDMA in Massive MIMO .
6.6.1 Principles
PDCCH SDMA in massive MIMO is introduced to improve PDCCH resource usage
when PDCCH resources are insufficient.
SDMA
The PDCCH SDMA feature splits a wide beam of PDCCH into multiple beams and
allows PDCCH resources to be shared by multiples UEs in these beams. This
feature is controlled by the MASSIVE_MIMO_PDCCH_SDMA_SW option of the
CellPdcchAlgo.SplitBeamPdcchSdmaSw parameter.
The PDCCH SDMA procedure is as follows:
1. A wide beam of PDCCH is split into multiple narrow beams.
A beam weight file is loaded for splitting the wide beam of PDCCH into
multiple narrow beams, as shown in Figure 6-15. The half-power beamwidth
(HPBW) of the narrow beams is similar to that of the wide beam.
Figure 6-15 PDCCH SDMA

eRAN
2. The eNodeB determines the attributes of UEs.

The eNodeB determines whether a UE requires an independent scheduling or
a joint scheduling based on UE-beam relationship and inter-beam isolation.
For details about UE identification, see UE Identification.
3. SDMA is performed.
For independently scheduled UEs, they are scheduled in each narrow beam. In
this way, PDCCH resources are shared by multiple UEs in different beams and
PDCCH SDMA is implemented, increasing PDCCH capacity. For jointly
scheduled UEs, they are scheduled in the beams in a working beam list for
joint transmission. The scheduling mode is the same as that used before the
split.
When PDCCH resources are insufficient but PDSCH or PUSCH resources are
sufficient, a PDCCH SDMA enhancement function can be used. This function uses
power sharing weights to implement power sharing between beams and improve
PDCCH resource usage. Power sharing between beams (as shown in Figure 6-16)
is controlled by the CellPdcchAlgo.PdcchSdmaWeightType parameter, which can
be set to POWER_SHARING_AMONG_5_BEAMS,
POWER_SHARING_AMONG_4_BEAMS, or
POWER_SHARING_AMONG_3_BEAMS.
Figure 6-16 Example of power sharing among four beams
Before enabling PDCCH SDMA, you can perform UE-beam relationship

measurement on the eNodeB to determine the number of PDCCH beams that
serve a UE. Based on measurement results, you can evaluate whether the feature
is suitable for enabling.
● When the MASSIVE_MIMO_PDCCH_MEAS_SW option of the
CellPdcchAlgo.SplitBeamPdcchSdmaSw parameter is selected, the eNodeB
uses a group of PDCCH split beams for UE-beam relationship measurement.
● When this feature is required, the CellPdcchAlgo.PdcchSdmaWeightType
parameter needs to be set for specifying a weight type, and the
CellPdcchAlgo.SplitBeamPdcchSdmaThd and
CellPdcchAlgo.SplitBeamPdcchSdmaThldOfs parameters need to be set for
determining UE-beam relationships.
● Measurement results are indicated by the monitoring item
PRIVATE_UE_PDCCH_SDMA_BEAM_MEASUREMENT in call history record
(CHR) logs. The monitoring item measures the number of beams that serve a
UE. If the proportion of single-beam UEs and dual-beam UEs is greater than
60%, this feature is suitable for use.

eRAN
– A single-beam UE refers to a UE served by one beam and a dual-beam

UE refers to a UE served by two beams.
– Proportion of single-beam UEs and dual-beam UEs = Number of single-
beam UEs and dual-beam UEs / Total number of UEs
UE Identification
The eNodeB determines the working beam list and UE attribute (independently or
jointly scheduled UE) for PDCCH SDMA as follows:
1. Arranges the beams sent by a UE in descending order by RSRP.
2. Selects the PDCCH beam with the largest RSRP value as a target beam of the
UE.
3. Determines the working beam list based on the isolation.
a. Arranges the beam with the largest RSRP value into group A and the
other beams into group B, and then calculates the isolation, which equals
the ratio of the total RSRP of group A to the total RSRP of group B.
b. Compares the isolation with the isolation threshold provided in Table
6-17. If the isolation is less than the threshold, the eNodeB moves the
beam with the second largest RSRP from group B to group A and
calculates the isolation again. The eNodeB repeats the operations until
the isolation exceeds the threshold, and uses the beams in group A as the
working beam list of the UE.
Table 6-17 Isolation thresholds

CCE Aggregation Isolation Threshold
Level
1 or 2 Determined by the
CellPdcchAlgo.SplitBeamPdcchSdmaThd
parameter
4 or 8 Determined by the
CellPdcchAlgo.SplitBeamPdcchSdmaThd and
CellPdcchAlgo.SplitBeamPdcchSdmaThldOfs
parameters
NOTE
● The eNodeB automatically identifies the CCE aggregation level of a UE, free
from any parameter control.
● The SINR is low for UEs with high CCE aggregation levels. For such UEs,
adjust the CellPdcchAlgo.SplitBeamPdcchSdmaThldOfs parameter value to
slightly decrease the isolation threshold so that the UEs are more probably
treated as independently scheduled UEs and more probably enter the PDCCH
SDMA procedure.
4. Determines the UE attribute 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 independently scheduled UE.

eRAN
– If the working beam list of the UE contains multiple narrow PDCCH

beams, the UE is a jointly scheduled UE.
6.6.2.1 Benefits
This feature increases the PDCCH capacity and the number of scheduled UEs per
TTI (SUNPT) in a cell.
● Average uplink SUNPT in a cell = L.Traffic.SUNPT.UL.Avg

● Average downlink SUNPT in a cell = L.Traffic.SUNPT.DL.Avg
This feature is recommended when all of the following conditions are met in
massive MIMO scenarios:
● PDCCH resources are insufficient.

Either of the following conditions is met:
– The uplink CCE allocation failure rate exceeds 40%, and the uplink
equivalent CCE usage with control format indicators (CFIs) fixed to 3
exceeds 60%.
– The downlink CCE allocation failure rate exceeds 60%, and the downlink
equivalent CCE usage with CFIs fixed to 3 exceeds 80%.
The following provides formulas for calculating the uplink and downlink CCE
allocation failure rates and the uplink and downlink equivalent CCE usages
with CFIs fixed to 3:
– Uplink CCE allocation failure rate = L.ChMeas.CCE.UL.AllocFail /
(L.ChMeas.CCE.UL.AllocFail + L.ChMeas.PDCCH.UL.AggLvl1Num +
L.ChMeas.PDCCH.UL.AggLvl2Num + L.ChMeas.PDCCH.UL.AggLvl4Num
+ L.ChMeas.PDCCH.UL.AggLvl8Num) x 100%
– Downlink CCE allocation failure rate = L.ChMeas.CCE.DL.AllocFail /
(L.ChMeas.CCE.DL.AllocFail + L.ChMeas.PDCCH.AggLvl1Num +
L.ChMeas.PDCCH.AggLvl2Num + L.ChMeas.PDCCH.AggLvl4Num +
– Uplink equivalent CCE usage with CFIs fixed to 3 =
L.ChMeas.CCE.ULUsed.Equivalent / ((60 x 60 x 200) x 84) x 100%
– Downlink equivalent CCE usage with CFIs fixed to 3 =
L.ChMeas.CCE.DLUsed.Equivalent / ((60 x 60 x 200) x (88 + 55 + 84
+ 88)) x 100%
● UEs are distributed evenly.
UE distribution can be determined based on the monitoring item
PRIVATE_UE_PDCCH_SDMA_BEAM_MEASUREMENT in CHR logs. If the
proportion of single-beam UEs and dual-beam UEs is greater than 60%, this
feature is suitable for use.
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
● This feature increases the PDCCH capacity and number of scheduled UEs
when all conditions for enabling this feature are met. It further increases the
average UE throughput, spectral efficiency, and user-perceived data rates in
both uplink and downlink. If any required condition is not met, the spectral
efficiency, cell throughput, and average downlink UE throughput may
decrease after this feature is enabled.
● After this feature is enabled, coverage changes induced by PDCCH beam split
may lead to changes in the number of UEs, performance indicators related to
air interface signaling, proportion of PDCCH DTXs, and PUCCH performance
counters (involving interference, SINR, RSRP, and RSSI). In addition, the CQIs
may decrease and the performance of TM3 UEs may deteriorate. The changes
in the number of UEs and decreases in the CQIs will have impacts on the PRB
usage, pairing performance, spectral efficiency, cell throughput, and average
downlink UE throughput.
PUCCH performance counters (involving interference, SINR, RSRP, and RSSI):
L.UL.Interference.PUCCH.Index0 to L.UL.Interference.PUCCH.Index15,
L.UL.SINR.PUCCH.Index0 to L.UL.SINR.PUCCH.Index12,
L.UL.RSRP.PUCCH.Index0 to L.UL.RSRP.PUCCH.Index23, and
L.UL.RSSI.PUCCH.Index0 to L.UL.RSSI.PUCCH.Index21
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

eRAN
Name

introduction MIMO
Functions
PDCCH CellPdcchAlgo.PDCC Physical PDCCH SDMA in

aggregation HAggLvlAdaptStrage Channel massive MIMO
level set to Resource requires capacity-
adaptation STRATEGYBASEDON- Management based PDCCH
CAPACITY aggregation level
adaptation.

Name
Inter- None Soft Split None

frequency Resource
split Duplex (TDD)
CRS port Cell.CrsPortNum set None When PDCCH SDMA
number to CRS_PORT_1 enhancement is used,
the Cell.CrsPortNum
parameter cannot be
set to CRS_PORT_1.
LTE and NR LTE_NR_DYN_POWER LTE and NR LTE and NR power

Power _SHARING_SW option Power sharing is not
Sharing of the Sharing compatible with
CellDynPowerShar- PDCCH SDMA
ing.DynamicPowerSh enhancement.
aringSwitch
parameter
6.6.3.3 Hardware
For the hardware requirements for PDCCH SDMA, see 4.3.3 Hardware. If the
UBBPg3b is configured to support both LTE TDD and NR, it does not support
PDCCH SDMA.
The BBP cannot be the UBBPem for PDCCH SDMA enhancement.

eRAN

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

PDCCH Split CellPdcchAlgo.Sp When UE-beam relationship

Beam SDMA litBeamPdcchSd measurement is required for
Switch maSw determining whether to enable PDCCH
SDMA, select the
MASSIVE_MIMO_PDCCH_MEAS_SW
option.
When PDCCH SDMA is required, select
the
MASSIVE_MIMO_PDCCH_SDMA_SW
option.
PDCCH Split CellPdcchAlgo.Sp Set this parameter to 24.

Beam SDMA litBeamPdcchSd
Threshold maThd
Split Beam CellPdcchAlgo.Sp Set this parameter to
PDCCH SDMA litBeamPdcchSd THRESHOLD_OFFSET_1.
Threshold Offset maThldOfs
The Strategy Of CellPdcchAlgo.PD Set this parameter to
PDCCH CCHAggLvlAdapt STRATEGYBASEDONCAPACITY.
Aggregation Level Strage
Adaptation
PDCCH SDMA CellPdcchAlgo.Pd ● If coverage is to be preferentially

Weight Type cchSdmaWeightT guaranteed, set this parameter to
ype PREFERENTIAL_COV_GUARANTEE.
● If gain is to be preferentially
guaranteed, set this parameter to
PREFERENTIAL_ENHANCED_SDMA
. This parameter can be set to this
value only when the
BfAnt.CoverageScenario parameter
is set to SCENARIO_2 or
SCENARIO_6.
● If PDCCH SDMA enhancement is
used, the value
POWER_SHARING_AMONG_5_BEA
MS is recommended.

eRAN
Coverage Scenario BfAnt.CoverageS PDCCH SDMA requires that this

cenario parameter be set to one of the
following values:
● SCENARIO_2
● SCENARIO_3
● SCENARIO_4
● SCENARIO_6
● SCENARIO_7
● SCENARIO_8
● SCENARIO_10
● SCENARIO_11
● SCENARIO_12
In 32T32R scenarios, it is not
recommended that this parameter be
set to SCENARIO_10 to SCENARIO_12
due to the limited vertical beamwidth
of a single channel.
If PDCCH SDMA enhancement is used,
the value SCENARIO_2 is
recommended.
NOTICE
Beam split weight values are available only when the beam weight database file is
activated. If no beam split weight value is available, enabling PDCCH SDMA will
lead to cell faults.
The parameter settings in the following examples are used for reference only. Set
the parameters based on network requirements.
//Configuring PDCCH SDMA enhancement
MOD CELLPDCCHALGO: LocalCellId=0, PdcchSdmaWeightType=POWER_SHARING_AMONG_5_BEAMS;
//Enabling massive MIMO PDCCH measurement when UE-beam relationship measurement is required for
determining whether to enable PDCCH SDMA
MOD CELLPDCCHALGO: LocalCellId=0,SplitBeamPdcchSdmaSw=MASSIVE_MIMO_PDCCH_MEAS_SW-1;
//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, SplitBeamPdcchSdmaThd=24,
SplitBeamPdcchSdmaThldOfs=THRESHOLD_OFFSET_1;

eRAN

//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&MASSIVE_MIMO_PDCCH_MEAS_SW-0,
PdcchSdmaWeightType=PREFERENTIAL_COV_GUARANTEE;

Maintenance.

On the MAE-Access, start a DCI status monitoring task to monitor the CCE
resource pairing performance when this feature is enabled.
Management.
page, choose LTE > Cell Performance Monitoring > DCI Statistic Monitoring. On
the displayed DCI Statistic Monitoring dialog box, select PDCCH DCI STATISTIC
and PDCCH SDMA in Split Beam DCI STATISTIC.

eRAN
Figure 6-17 Configuration GUI for DCI statistic monitoring
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

After this function is enabled, monitor the following KPIs:
● User Uplink Average Throughput
● User Downlink Average Throughput (N/A, LTE eNodeB)

Fault description: No CCE resources are paired.
Fault handling:
met.
Preparation.
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

eRAN
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:
met.
Preparation.
----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-19 shows the
transmission mode used in massive MIMO scenarios.
Table 6-19 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 Yes

multiplexing
TM4 Closed-loop spatial No

multiplexing Massive MIMO is not
compatible with downlink 4x4
MIMO and the
CellBfMimoParaCfg.BfMimo
AdapWithTm4Switch
parameter must be set to OFF.
Therefore, TM4 is not used in
massive MIMO scenarios.

eRAN
Transmission Transmission Solution Whether to Use in Massive

Mode MIMO Scenarios
TM7 Single-stream beamforming Yes
TM8 Dual-stream beamforming When 3D beamforming and

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

multiplexing (TM9wPMI)
Open-loop spatial Yes

multiplexing (TM9w/oPMI) Non-antenna-selection UEs do
not support TM9w/oPMI
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 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.
The scope of TMA in massive MIMO scenarios includes TM2, TM3, TM7, TM8,
TM9wPMI, and TM9w/oPMI, as listed in Table 6-19. Table 6-20 describes the TMA
principles.

eRAN
Table 6-20 TMA principles

CellBfMim Cell.CrsP UE Type Channel Available Transmission Mode
oParaCfg. ortNum SINR
BfMimoAd
aptiveSwit
ch
NO_ADAP N/A N/A N/A The transmission mode is
TIVE specified by the
CellBfMimoParaCfg.FixedBfMi
moMode parameter, not
adaptively adjusted.
This value is recommended only
in test scenarios.
TxD_BF_A N/A High- N/A TM2

DAPTIVE speed
UEs
Low- N/A ● TM7

speed ● TM8 (only suitable for
R8 and antenna-selection R9 and
later later UEs)
UEs
MIMO_BF_ CRS_PO High- Low TM2

ADAPTIVE RT_2 speed
UEs High TM3 rank 2
Low- Low TM7 (as shown in Figure 6-18)

speed or TM8 (for antenna-selection
R8/R9 R9 and later UEs, as shown in
UEs Figure 6-19)
High TM3 rank 2, as shown in Figure

6-18
Low- Low TM7 (as shown in Figure 6-20)

speed or TM8 (for antenna-selection
R10 and R9 and later UEs, as shown in
later Figure 6-21)
UEs
High TM3 rank 2 or TM9wPMI rank 3
or 4, as shown in Figure 6-20
Low- N/A TM9w/oPMI

speed 4-
antenna
-
selection
UEs
Note: UEs can be switched to the TM9wPMI or TM9w/oPMI mode only when
TM9 is enabled in massive MIMO cells.

eRAN
Figure 6-18 TMA for low-speed non-antenna-selection R8/R9 UEs
Figure 6-19 TMA for low-speed antenna-selection R9 and later UEs

eRAN
Figure 6-20 TMA for low-speed non-antenna-selection R10 UEs
Figure 6-21 TMA for low-speed antenna-selection R10 UEs
6.7.1.3 Optimized TMA
Transmission Mode Control for UE Access

After TMA is enabled, the proportion of TM2 UEs may be high due to the time
required for switching from TM2 to TM7, and therefore the number of downlink
paired layers may be less than expected. To address this issue, the

eRAN
CellBfMimoParaCfg.UeAccessTMMode parameter is introduced to control the

initial transmission mode in massive MIMO scenarios.
Value of Initial Transmission Mode

CellBfMimoParaCfg.
UeAccessTMMode
TM7 The initial transmission mode is 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 user-
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 TM9wPMI to TM7, achieving higher pairing gains and
increasing the cell throughput.
● In multi-layer pairing scenarios, a smaller value of
CellBf.MultiLayerThdSwitchToTM7 results in a higher probability that TM7
is used and UEs are paired in this mode for MU beamforming.
● In non-multi-layer pairing scenarios, a larger value of
CellBf.MultiLayerThdSwitchToTM7 or the value 0 should be used because
UEs cannot be paired even when TM7 is used and furthermore the cell
throughput will decrease in this situation.
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 Dual-Stream Beamforming is enabled (as
described in 7.9 MU Beamforming Pairing of Antenna Selection UEs in Dual-
Stream Beamforming), the eNodeB can switch the transmission mode from TM2,
TM3, or TM9wPMI to TM8 for antenna selection UEs. In this way, the pairing gain
is received, increasing the cell throughput.
● In multi-layer pairing scenarios, a smaller value of
CellBf.MultiLayerThdSwitchToTM7 results in a higher probability that TM7
(for non-antenna-selection UEs) or TM8 (for antenna selection UEs) is used
and UEs are paired in this mode for MU beamforming.
● In non-multi-layer pairing scenarios, a larger value of
CellBf.MultiLayerThdSwitchToTM7 or the value 0 should be used because
UEs cannot be paired even when TM7 is used and furthermore the cell
throughput will decrease in this situation.
Optimized Switching to TM7 in Multi-Layer Pairing Scenarios

When the proportion of multi-stream UEs in a cell is high, optimized switching to
TM7 in multi-layer pairing scenarios can be enabled to increase the number of

eRAN
spatial multiplexing layers in the cell, improving the downlink spectral efficiency
and downlink user-perceived rate.
The eNodeB switches the transmission mode from TM2, TM3, or TM9wPMI to
TM7 so as to obtain higher pairing gains and increase cell throughput when all of
● The number of layers to be paired in the cell reaches the threshold specified
by the CellBf.MultiLayerThdSwitchToTM7 parameter.
● The number of layers to be paired in the cell reaches the number of spatial
multiplexing layers (measured during a period) plus an offset.
● The INCREASE_SM_LAYER_TMA_OPT_SW option of the
CellBfMimoParaCfg.BfMimoAlgoOptSwitch parameter is selected.
The eNodeB can switch the transmission mode from TM2, TM3, or TM9wPMI to
TM8 for antenna selection UEs so as to obtain dual-stream-UE pairing gains and
increase cell throughput when all of the following conditions are met:
● The number of layers to be paired in the cell reaches the threshold specified
by the CellBf.MultiLayerThdSwitchToTM7 parameter.
● The number of layers to be paired in the cell reaches the number of spatial
multiplexing layers (measured during a period) plus an offset.
● The INCREASE_SM_LAYER_TMA_OPT_SW option of the
● MU Beamforming Pairing of Antenna Selection UEs in Dual-Stream
Beamforming is enabled. For details, see 7.9 MU Beamforming Pairing of
Antenna Selection UEs in Dual-Stream Beamforming.
Heavy-Load TMA Boost

Heavy-load TMA boost is introduced to prevent noticeable negative impacts from
occurring in some heavy-load cells when a fixed beamforming mode is used.
This function takes effect for newly admitted mobile broadband (MBB) UEs as
well as newly admitted and already online wireless broadband (WBB) UEs. Figure
6-22 shows the implementation process of this function.

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

boost HEAVYLOADTRANSMODEADAPTBOOSTSW
and HISTORICALSPECTRALEFFOPTSW options
of the
CellBfMimoParaCfg.BfMimoAlgoOptSwitch
parameter.

eRAN
Step Description
Checking whether the cell is A cell is heavily loaded if both of the following
heavily loaded conditions are met:
● Average downlink PRB usage of the cell >
CellBfMimoParaCfg.HeavyLoadDlPrbUsa-
geThld parameter value
● Average number of UEs in the cell >
CellBfMimoParaCfg.HeavyLoadAvgUeCount
Thld parameter value
Measuring the historical cell ● The
spectral efficiency separately CellBfMimoParaCfg.HeavyLoadTransMo-
for cell-level TMA mode and deEvalPrd parameter specifies the period for
target beamforming mode in measuring the cell load and spectral
heavy-load scenarios efficiency when this function takes effect.
● The CellBfMimoParaCfg.HeavyLoadTarget-
TransMode parameter specifies the target
beamforming mode (TM7 or TM8) used by a
cell when the cell is heavily loaded.
Automatically selecting a When the

mode that maximizes the CellBfMimoParaCfg.HeavyLoadTargetTrans-
cell spectral efficiency Mode parameter is set to TM7 and MU
Beamforming Pairing of Antenna Selection UEs
in Dual-Stream Beamforming (described in 7.9
MU Beamforming Pairing of Antenna
Selection UEs in Dual-Stream Beamforming) is
enabled, the eNodeB can switch the transmission
mode of antenna selection UEs from TM2, TM3,
or TM9wPMI to TM8. In this way, the dual-
stream beamforming gain is obtained, increasing
the cell throughput.
This function is not compatible with switching to TM7 in multi-layer pairing

scenarios. This function is recommended when beamforming performance is
unstable (for example, when the performance of multi-layer pairing is unstable
due to radio environment or the proportion of UEs unsuitable for beamforming is
high). 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.

eRAN
Optimized 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:
● Optimizes the threshold for switching between rank-2 TM3 and 4-layer TM9
for 4R UEs in 256QAM mode.
This optimization requires the configuration of the
CellBfMimoParaCfg.Tm3ToTm9SwtgSEffOfs256qam and
CellBfMimoParaCfg.Tm9ToTm3SwtgSEffOfs256qam parameters. The two
switching offsets apply to both 4R and 8R UEs.
For 4R UEs, this optimization uses an additional offset, making it more
difficult for 4R UEs to switch from rank-2 TM3 to rank-3~rank-8 TM9 in
closed-loop mode than for 8R UEs.
● Optimizes the threshold for switching between rank-2 TM3 and dual-stream
beamforming for 4R and 8R non-antenna-selection UEs when the
FakeAntSelIdentificationSwitch option of the CellAlgoSwitch.BfAlgoSwitch
This optimization requires the configuration of the
CellBfMimoParaCfg.DualBfToTM3Rank2Offset and
CellBfMimoParaCfg.TM3Rank2ToDualBfThdOffset parameters. When the
FakeAntSelIdentificationSwitch option of the CellAlgoSwitch.BfAlgoSwitch
parameter is selected, antenna selection UEs are distinguished from fake
antenna selection UEs.
For 4R and 8R non-antenna-selection (including fake antenna selection) UEs,
this optimization uses an additional offset, making it easier for these UEs to
switch to dual-stream beamforming. The offset is different for 64QAM and
256QAM.
● Optimizes the threshold for switching between TM3 and TM7 for 4R and 8R
antenna-selection UEs in massive MIMO cells, making it easier for these UEs
to switch to TM7, when the FakeAntSelIdentificationSwitch option of the
CellAlgoSwitch.BfAlgoSwitch parameter is selected.
NOTE
Dual-stream beamforming can be performed in TM8 or TM9w/oPMI. 4-layer TM9 refers to

rank-3 to rank-8 TM9wPMI.
Optimized Switching to Beamforming in Heavy-Load Scenarios

This function is controlled by the CellBf.HeavyLoadSwitchToBfOpt parameter.
When this 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:
● Switching of online WBB UEs to TM7 when the cell is in the heavy-load
beamforming state
The transmission modes of online WBB UEs are switched from TM2, TM3, or
TM9wPMI to TM7 when all of the following conditions are met. A maximum
of 10 online WBB UEs can transit to TM7 per logical cell per second.

eRAN
– Optimized switching to TM7 in multi-layer pairing scenarios is enabled,

that is, the CellBf.MultiLayerThdSwitchToTM7 parameter value is not 0.
– The cell is in the heavy-load beamforming state, that is, the number of
layers to be paired reaches the threshold specified by the
CellBf.MultiLayerThdSwitchToTM7 parameter.
After the cell exits the heavy-load beamforming state, the transmission modes
of online WBB UEs are selected based on the optimal single-UE link selection
principles.
● Optimized heavy-load TMA boost
When heavy-load TMA boost is enabled by selecting the
HEAVYLOADTRANSMODEADAPTBOOSTSW and
HISTORICALSPECTRALEFFOPTSW options of the
CellBfMimoParaCfg.BfMimoAlgoOptSwitch parameter, the eNodeB
increases the filter factor of the historical cell spectral efficiency for heavy-
load massive MIMO cells. This enables the historical cell spectral efficiency to
accurately adapt to the changes in the number of UEs and load status. In
heavy load scenarios, cell-level TMA mode or target beamforming mode is
adaptively selected when the average number of downlink paired layers is less
than or equal to the value of CellBf.HeavyLoadSwitchToBfOpt. Target
beamforming mode is fixedly selected when the average number of downlink
paired layers is greater than the value of CellBf.HeavyLoadSwitchToBfOpt.
Number of downlink paired layers = (L.ChMeas.MUBF.2ndLayer.PairPRB.Succ
+ ... + L.ChMeas.MUBF.16thLayer.PairPRB.Succ)/L.ChMeas.PRB.DL.Used.Avg
+1
Load-based TMA Optimization

This function is controlled by the LOAD_BASED_TMA_OPT_SW option of the
CellBfMimoParaCfg.BfMimoAlgoOptSwitch parameter.
Under the following parameter settings, load-based TMA optimization is

performed on a UE after it accesses a cell:
● The CellBfMimoParaCfg.BfMimoAdaptiveSwitch parameter is set to

MIMO_BF_ADAPTIVE.
● The CellBfMimoParaCfg.InitialBfMimoType parameter is set to TM2.
● The LOAD_BASED_TMA_OPT_SW option of the
The processing mechanism is as follows:
● When a cell is lightly loaded:

Assume that an E-RAB has been set up for a UE. If the UE reports a CQI
greater than or equal to a threshold, the eNodeB switches the transmission
mode from TM2 to TM3 for the UE. If the UE reports a CQI less than the
threshold, the eNodeB retains TM2.
When the TM9HybridPrecodingSwitch option of the
CellAlgoSwitch.EnhMIMOSwitch parameter is selected, it will take a shorter
time to switch to closed-loop TM9 for a UE that supports multi-layer closed-
loop TM9. If the performance is poor after the UE enters closed-loop TM9, the
UE quickly exits this mode.

eRAN
● When a cell is heavily loaded:

When delivering an RRC Connection Reconfiguration message during an E-
RAB setup procedure, the eNodeB switches the transmission mode from TM2
to TM7 for a non-antenna-selection UE, or from TM2 to TM8 for an antenna
selection UE.
For a CA UE, after the LOAD_BASED_TMA_OPT_SW option of the

CellBfMimoParaCfg.BfMimoAlgoOptSwitch parameter is selected, the
transmission mode carried in the first SCell RRC Connection Reconfiguration
message is not changed.
NOTE
● If the heavy-load TMA boost function is enabled, the cell is considered to be lightly
loaded when either of the following conditions is met:
● Average downlink PRB usage of the cell ≤
CellBfMimoParaCfg.HeavyLoadDlPrbUsageThld parameter value
● Average number of UEs in the cell ≤
CellBfMimoParaCfg.HeavyLoadAvgUeCountThld parameter value
● If switching to TM7 in multi-layer pairing scenarios is enabled, the cell is considered to
be lightly loaded if the following condition is met:
Number of layers to be paired in the cell < CellBf.MultiLayerThdSwitchToTM7
parameter value
● If both the heavy-load TMA boost function and the "switching to TM7 in multi-layer
pairing scenarios" function are disabled, the cell is treated as a lightly loaded cell.
TM8-Excluded Adaptation
This function excludes TM8 from adaptive switching between beamforming and
MIMO or between open-loop beamforming modes. This function increases the
number of RBs available for scheduling in a cell, thereby increasing the
throughput. This function is enabled when the BFMIMOADAPWITHOUTTM8
option of the CellBfMimoParaCfg.BfMimoAlgoOptSwitch parameter is selected
in one of the following scenarios.
Table 6-21 Configuration scenarios of TM8-excluded adaptation
Scenario CellBf.MaxBfRankP FakeAntSelIdentifi- UEs for Which

ara cationSwitch Option Adaptation Is to Be
of Performed
CellAlgoSwitch.BfAlg
oSwitch
1 SINGLE_LAYER_BF N/A All UEs
2 DUAL_LAYER_BF or Selected Only non-antenna-

FOUR_LAYER_BF selection UEs

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.
If all of the following conditions are met, it is recommended that optimized

switching to TM7 in multi-layer pairing scenarios be enabled. In other situations,
enabling this function brings no gains.
● The proportion of UEs for which rank 2 or higher is used is greater than 70%.
● The number of downlink active UEs in the cell ranges from 2 to 4.
6.7.2.2 Impacts
Network Impacts
● When TMA is enabled but transmission mode control for UE access is
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.
● When both TMA and transmission mode control for UE access are enabled,
the user-perceived rate may decrease if the network is lightly loaded and the
proportion of small packets is high.
● Optimized switching to TM7 in multi-layer pairing scenarios
This function has the following network impacts, compared with switching to
TM7 in multi-layer pairing scenarios:
– If MU Beamforming Pairing of Antenna Selection UEs in Dual-Stream
Beamforming is disabled, the proportion of TM7 may decrease and the
number of downlink paired layers may decrease.
– If MU Beamforming Pairing of Antenna Selection UEs in Dual-Stream
Beamforming is enabled, the proportion of TM7, TM8, and open-loop
TM9 may decrease and the number of downlink paired layers may
decrease.
– When the proportion of multi-stream UEs in a cell is high, the number of
spatial multiplexing layers increases.
Number of spatial multiplexing layers in a cell =
[(L.ChMeas.MIMO.PRB.CL.Rank1 + L.ChMeas.MIMO.PRB.OL.Rank1 +
L.ChMeas.BF.PRB.OL.Rank1) + (L.ChMeas.MIMO.PRB.CL.Rank2 +
L.ChMeas.MIMO.PRB.OL.Rank2 + L.ChMeas.BF.PRB.OL.Rank2) +
(L.ChMeas.MIMO.PRB.CL.Rank3 + L.ChMeas.MIMO.PRB.OL.Rank3 +
L.ChMeas.BF.PRB.OL.Rank3) + (L.ChMeas.MIMO.PRB.CL.Rank4 +
L.ChMeas.MIMO.PRB.OL.Rank4 + L.ChMeas.BF.PRB.OL.Rank4) +
L.ChMeas.MIMO.PRB.CL.Rank5 + L.ChMeas.MIMO.PRB.CL.Rank6 +
L.ChMeas.MIMO.PRB.CL.Rank7 + L.ChMeas.MIMO.PRB.CL.Rank8] /
(L.ChMeas.PRB.DL.Used.Avg x Measurement period)
– The downlink spectral efficiency and downlink user-perceived rate
increase.
● Heavy-load TMA boost may cause the cell spectral efficiency to fluctuate due
to cell-level transmission mode attempts.

eRAN
● Optimized TMA for 4R and 8R UEs increases the proportion of beamforming,

downlink UE spectral efficiency, and downlink user-perceived rate. The
proportion of TM9wPMI may decrease.
● If WBB UEs have been online for a long time, switching of online WBB UEs to
TM7 when the cell is in the heavy-load beamforming state (which is a
function of optimized switching to beamforming in heavy-load scenarios)
increases the number of paired layers, spectral efficiency, and user-perceived
rate in the downlink.
● In heavy-load scenarios, optimized heavy-load TMA boost (which is a function
of optimized switching to beamforming in heavy-load scenarios) enables the
historical cell 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 the heavy-load beamforming state.
● Load-based TMA optimization
– After load-based TMA optimization is enabled in a cell, if the cell is
lightly loaded, then the proportion of TM2 decreases, the proportion of
rank-2 TM3 increases, the proportion of beamforming may decrease, the
proportion of closed-loop TM9 may increase, and the downlink spectral
efficiency increases. As the proportion of rank 2 increases, the reported
CQIs may decrease, the MCS indexes may decrease, and the downlink
spectral efficiency increases. If the cell is heavily loaded, then the
reported CQIs may increase, the proportion of beamforming increases,
and the number of downlink paired layers increases.
– After load-based TMA optimization is enabled in a cell, if the proportion
of downlink tail packets exceeds 50%, then the downlink spectral
efficiency may increase and the downlink user-perceived rate (User
Downlink Average Throughput) may decrease. The main reason is that
more tail packets may be generated after downlink spectral efficiency is
improved and scheduling is accelerated. As a result, the value of
(L.Thrp.bits.DL – L.Thrp.bits.DL.LastTTI) decreases, the value of
L.Thrp.Time.DL.RmvLastTTI also decrease, and the downlink user-
perceived rate may not increase.
Proportion of downlink tail packets = L.Thrp.bits.DL.LastTTI /
L.Thrp.bits.DL x 100%
– As the downlink spectral efficiency increases, there may be changes in
DRX entry/exit (for example, the number of DRX entry/exit times and the
active/sleep time in DRX mode may change). As a result, the values of
related DRX counters fluctuate.

eRAN
Function Impacts
Name
TM9 port 5 Tm9Port5Switch Massive ● When optimized

option of the MIMO switching to TM7
UeCooperationPara.S Optimization in multi-layer
pecUserCooperationS in WTTx pairing scenarios is
witch parameter Scenarios enabled, the TM9
(TDD) port 5 function
does not forcibly
switch UEs to TM7
and allows UEs to
stay in closed-loop
TM9 mode.
● The TM9 port 5
function requires
that switching to
TM7 in multi-layer
pairing scenarios or
heavy-load TMA
boost be enabled.
6.7.3 Requirements
6.7.3.1 Licenses
None
6.7.3.2 Software
Name

introduction MIMO
Functions

eRAN

Name
WBB UE CellWttxParaCfg.Wb WBB Switching of online

identification bOrMbbUserDefMod WBB UEs to TM7
e when the cell is in the
heavy-load
beamforming state
(which is a function of
optimized switching
to beamforming in
heavy-load scenarios)
depends on WBB UE
identification.
Switching to CellBf.MultiLayerThd 6.7.1.3 Switching of online

TM7 in multi- SwitchToTM7 Optimized WBB UEs to TM7
layer pairing TMA when the cell is in the
scenarios heavy-load
beamforming state
(which is a function of
optimized switching
to beamforming in
heavy-load scenarios)
depends on switching
to TM7 in multi-layer
pairing scenarios.
Optimized switching
pairing scenarios
depends on switching
pairing scenarios.
Heavy-load HEAVYLOADTRANSM 6.7.1.3 Optimized heavy-load

TMA boost ODEADAPTBOOSTS Optimized TMA boost (which is a
W and TMA function of optimized
HISTORICALSPECTRA switching to
LEFFOPTSW options beamforming in
of the heavy-load scenarios)
CellBfMimoParaCfg.B depends on heavy-
fMimoAlgoOptSwitc load TMA boost.
h parameter

eRAN

Name
Heavy-load HEAVYLOADTRANSM 6.7.1.3 Heavy-load TMA

TMA boost ODEADAPTBOOSTS Optimized boost is not
W and TMA compatible with
HISTORICALSPECTRA switching to TM7 in
LEFFOPTSW options multi-layer pairing
of the scenarios.
CellBfMimoParaCfg.B Preferentially enable
fMimoAlgoOptSwitc switching to TM7 in
h parameter multi-layer pairing
scenarios. If switching
Switching to CellBf.MultiLayerThd 6.7.1.3 to TM7 in multi-layer
TM7 in multi- SwitchToTM7 Optimized pairing scenarios
layer pairing TMA cannot offer positive
scenarios gains, enable heavy-
load TMA boost.
6.7.3.3 Hardware
For details, see 4.3.3 Hardware. The UBBPem does not support optimized
switching to TM7 in multi-layer pairing scenarios.

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

Mode fg.InitialBfMimo network plan.
Type
BfMIMO adaptive CellBfMimoParaC Set this parameter to
switch fg.BfMimoAdapti MIMO_BF_ADAPTIVE.
veSwitch
UE Access CellBfMimoParaC If transmission mode control for UE
Transmission fg.UeAccessTMM access is required, set this parameter
Mode ode to TM7.

eRAN
Cell Highload Thd CellBf.MultiLayer ● In multi-layer pairing scenarios, set

for Switch to BF ThdSwitchToTM7 the CellBf.MultiLayerThdSwitch-
ToTM7 parameter to a smaller
value to increase the probability
that TM7 is used and UEs are
paired in this mode for MU
beamforming.
● In non-multi-layer pairing scenarios,
set the
CellBf.MultiLayerThdSwitch-
ToTM7 parameter to 0 or a larger
value as UEs cannot be paired even
when TM7 is used.
BfMimo CellBfMimoParaC If heavy-load TMA boost is required,

Algorithm fg.BfMimoAlgoO select the HEAVYLOADTRANSMO-
Optimization ptSwitch DEADAPTBOOSTSW and
Switch HISTORICALSPECTRALEFFOPTSW
options.
BfMimo CellBfMimoParaC To enable load-based TMA

Algorithm fg.BfMimoAlgoO optimization, select the
Optimization ptSwitch LOAD_BASED_TMA_OPT_SW option.
Switch
Heavy Load CellBfMimoParaC Set this parameter to its recommended

Target Trans fg.HeavyLoadTar value.
Mode getTransMode
Heavy Load Trans CellBfMimoParaC The value 1 is recommended in
Mode Evaluation fg.HeavyLoadTra massive MIMO scenarios.
Period nsModeEvalPrd
Heavy Load CellBfMimoParaC The value 40 is recommended in
Downlink PRB fg.HeavyLoadDlP massive MIMO scenarios.
Usage Threshold rbUsageThld
Heavy Load CellBfMimoParaC Set this parameter to its recommended
Average UE Count fg.HeavyLoadAvg value.
Threshold UeCountThld
Handover BF CellBfMimoParaC If handover-specific beamforming
Threshold Adjust fg.HoBfThdAdjS threshold adjustment is required, set
Switch witch this parameter to ON.
Heavy-Load CellBf.HeavyLoad Set this parameter to its recommended

Switch to BF SwitchToBfOpt value.
Optimization
4R or 8R UE BF CellBfMimoParaC To enable optimized TMA for 4R and

MIMO Adaptation fg.Ue4ROr8RBfM 8R UEs, set this parameter to ON
Opt Sw imoAdaptOptSw

eRAN
Dual Streaming CellBfMimoParaC When optimized TMA for 4R and 8R

Beamforming To fg.DualBfToTM3 UEs is enabled, set this parameter.
TM3 Rank2 Offset Rank2Offset Set this parameter based on network
conditions.
TM3 Rank2 To CellBfMimoParaC When optimized TMA for 4R and 8R

Dual Streaming fg.TM3Rank2ToD UEs is enabled, set this parameter.
Beamforming ualBfThdOffset Set this parameter based on network
Threshold Offset conditions.
256QAM TM3 to CellBfMimoParaC Set this parameter to its recommended

TM9 Switching fg.Tm3ToTm9Sw value.
Spectral Eff Offset tgSEffOfs256qam
256QAM TM9 to CellBfMimoParaC Set this parameter to its recommended
TM3 Switching fg.Tm9ToTm3Sw value.
Spectral Eff Offset tgSEffOfs256qam
BF algorithm CellAlgoSwitch.B If optimized TMA for 4R and 8R UEs is
switch fAlgoSwitch enabled, it is recommended that the
FakeAntSelIdentificationSwitch
option be selected to prevent the
threshold for triggering the switching
of antenna selection UEs between
rank-2 TM3 and dual-stream TM8
from taking effect on fake antenna
selection UEs.
BfMimo CellBfMimoParaC If the proportion of multi-stream UEs

Algorithm fg.BfMimoAlgoO is high, it is recommended that the
Optimization ptSwitch INCREASE_SM_LAYER_TMA_OPT_SW
Switch option be selected to enable optimized
switching to TM7 in multi-layer pairing
scenarios, a function of TMA
optimization.
BfMimo CellBfMimoParaC To enable TM8-excluded adaptation,

Algorithm fg.BfMimoAlgoO select the
Optimization ptSwitch BFMIMOADAPWITHOUTTM8 option.
Switch

//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;

eRAN
//(Optional) Enabling switching to TM7 in multi-layer pairing scenarios (assuming that

MultiLayerThdSwitchToTM7 is set to 20)
//(Optional) Enabling optimized switching to TM7 in multi-layer pairing scenarios (assuming that
MultiLayerThdSwitchToTM7 is set to 20)
MOD CELLBFMIMOPARACFG: LocalCellId=0, BfMimoAlgoOptSwitch=INCREASE_SM_LAYER_TMA_OPT_SW-1;
//(Optional) Enabling heavy-load TMA boost (Heavy-load TMA boost is not compatible with switching to
TM7 in multi-layer pairing scenarios. The two functions cannot be enabled at the same time.)
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,
DualBfToTM3Rank2Offset=-25, TM3Rank2ToDualBfThdOffset=-25, Tm3ToTm9SwtgSEffOfs256qam=60,
Tm9ToTm3SwtgSEffOfs256qam=75;
//(Optional) Enabling optimized switching to beamforming in heavy-load scenarios

MOD CELLBF: LocalCellId=0, HeavyLoadSwitchToBfOpt=13;
//(Optional) Enabling load-based TMA optimization

//(Optional) Enabling TM8-excluded adaptation

MOD CELLBFMIMOPARACFG:LOCALCELLID=0, BfMimoAlgoOptSwitch=BFMIMOADAPWITHOUTTM8-1;

//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 optimized switching to TM7 in multi-layer pairing scenarios
MOD CELLBFMIMOPARACFG: LocalCellId=0, BfMimoAlgoOptSwitch=INCREASE_SM_LAYER_TMA_OPT_SW-0;
//(Optional) Disabling heavy-load TMA boost and restoring the value of 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 optimized 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;
//(Optional) Disabling load-based TMA optimization
//(Optional) Disabling TM8-excluded adaptation
MOD CELLBFMIMOPARACFG:LOCALCELLID=0, BfMimoAlgoOptSwitch=BFMIMOADAPWITHOUTTM8-0;


● Run the LST CELLBFMIMOPARACFG command. If the value of BfMIMO
adaptive switch is not NO_ADAPTIVE, TMA has been enabled.

eRAN
● Run the LST CELLBFMIMOPARACFG command. If the following command

output is displayed, transmission mode control for UE access has been
enabled.
UE Access Transmission Mode = TM7
● Run the LST CELLBF command. If the value of Cell Highload Thd for Switch
to BF is not 0, switching to TM7 in multi-layer pairing scenarios has been
enabled.
output is displayed, optimized switching to TM7 in multi-layer pairing
scenarios has been enabled.
BfMimo Algorithm Optimization Switch = INCREASE_SM_LAYER_TMA_OPT_SW:On

output is displayed, heavy-load TMA boost has been enabled.
BfMimo Algorithm Optimization Switch = HEAVYLOADTRANSMODEADAPTBOOSTSW:On
= HISTORICALSPECTRALEFFOPTSW:On

output is displayed, handover-specific beamforming threshold adjustment has
been enabled.
Handover BF Threshold Adjust Switch = On
● 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.
output is displayed, optimized TMA for 4R and 8R UEs has been enabled.
4R or 8R UE BF MIMO Adaptation Opt Sw = On

output is displayed, load-based TMA optimization has been enabled.
BfMimo Algorithm Optimization Switch = LOAD_BASED_TMA_OPT_SW:On

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.
Counter ID Counter Name Observation Purpose
1526745885 L.Traffic.ActiveUser.DL.WBB.Avg Used to measure the

average number of
WBB UEs activated in
the downlink.
1526745955 L.Traffic.User.WBB.Avg Used to measure the

average number of
WBB UEs in a cell.
After optimized switching to TM7 in multi-layer pairing scenarios is enabled,

observe the counters listed in the following table.

eRAN
1526727391 L.ChMeas.MIMO.PRB.CL.Rank1 to Used to estimate the

to L.ChMeas.MIMO.PRB.CL.Rank2 proportion of rank 1
1526727392 to rank 8, and
calculate the number
1526727393 L.ChMeas.MIMO.PRB.OL.Rank1 to of downlink spatial
to L.ChMeas.MIMO.PRB.OL.Rank2 multiplexing layers in
1526727394 a cell.
1526728174 L.ChMeas.MIMO.PRB.CL.Rank3 to
to L.ChMeas.MIMO.PRB.CL.Rank4
1526728175
1526728176 L.ChMeas.MIMO.PRB.OL.Rank3 to
to L.ChMeas.MIMO.PRB.OL.Rank4
1526728177
1526746774 L.ChMeas.MIMO.PRB.CL.Rank5 to
to L.ChMeas.MIMO.PRB.CL.Rank8
1526746777
1526728881 L.ChMeas.BF.PRB.OL.Rank1 to
to L.ChMeas.BF.PRB.OL.Rank2
1526728882
1526758992 L.ChMeas.BF.PRB.OL.Rank3 to
to L.ChMeas.BF.PRB.OL.Rank4
1526758991
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 are used to observe the performance of the
functions.
1526747711 L.HeavyLoad.TransModeAdapt.Dur.D Used to measure the

L.Cell values of indicators
related to heavy-load
1526747712 L.HeavyLoad.TransModeTarget.Dur.D TMA boost.
L.Cell
1526747713 L.LightToHeavyLoad.Num.DL.Cell
1526747714 L.HeavyLoad.TmaToTmTarget.Num.D
L.Cell
1526747715 L.HeavyLoad.TmTargetToTma.Num.D
L.Cell

eRAN
1526739777 L.ChMeas.MUBF.1stLayer.PairPRB.Tot Used to calculate the

to to L.ChMeas.MUBF. number of downlink
1526739780 4thLayer.PairPRB.Succ paired layers.
1526745726 L.ChMeas.MUBF.
to 5thLayer.PairPRB.Succ to
1526745737 L.ChMeas.MUBF.
16thLayer.PairPRB.Succ
1526737840 L.ChMeas.PRB.TM2 to Used to calculate the

to L.ChMeas.PRB.TM8 proportion of PRBs
1526737846 used in each downlink
transmission mode.
1526728261 L.Thrp.bits.DL Used to estimate the

average downlink
1526728763 L.ChMeas.PRB.DL.DrbUsed.Avg spectral efficiency of a
1526730558 L.Cell.DL.PDSCH.Tti.Num cell.
The calculation formulas are as follows:

● Proportion of PRBs in a transmission mode (for example, in TM9) =
L.ChMeas.PRB.TM9 / (L.ChMeas.PRB.TM2 + ... + L.ChMeas.PRB.TM9) x
100%
● Number of downlink paired layers = (L.ChMeas.MUBF.2ndLayer.PairPRB.Succ
+ ... + L.ChMeas.MUBF.16thLayer.PairPRB.Succ) /
L.ChMeas.PRB.DL.Used.Avg + 1
● Average downlink spectral efficiency = L.Thrp.bits.DL /
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-23 shows the principles of enhanced coordinated
scheduling-based power control.

eRAN
Figure 6-23 Enhanced coordinated scheduling based power control
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.
Determining an Interference Coordination Set

By collecting information on neighboring cells that meet event A3/A6 reporting
conditions within a certain period, the serving cell selects a maximum of 10
neighboring cells with the highest interference to form an interference
coordination set.
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 SCCs is determined

eRAN
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 neighboring cell RSRP. The calculation also
aims to maximize the cell throughput of the entire network. The stronger the
interference generated by a neighboring cell, the more the power of the
neighboring cell to be reduced.
Exchanging Power Adjustment Requirements

The serving cell exchanges PRB usage and cell PA information with its neighboring
cells causing 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 Cell Transmit Power

The downlink transmit power of a neighboring cell causing strong interference is
adjusted according to the power adjustment requirement sent by the serving cell
when the neighboring cell meets the following conditions:
● It is not a massive MIMO cell.
● It is not in the coverage of a micro RRU.
● Its PRB usage is greater than or equal to 40%.
● The average number of downlink activated UEs in it is greater than or equal
to the value of the CellCspcPara.eCspcPCAdjUeNumTh parameter.
The CellCspcPara.eCspcPCAdjRange parameter specifies the downlink transmit

power adjustment range for a cell. A maximum of two options of this parameter
can be selected and the values indicated by the selected options must be less than
the value of the CellDlpcPdschPa.PaPcOff parameter.
● If only one option of the CellCspcPara.eCspcPCAdjRange parameter is
selected, the downlink transmit power of the cell can be adjusted to the value
indicated by this option or the value of the CellDlpcPdschPa.PaPcOff
parameter.
● If two options of the CellCspcPara.eCspcPCAdjRange parameter are selected,
the downlink transmit power of the cell can be adjusted to one of the values
indicated by the options or the value of the CellDlpcPdschPa.PaPcOff
parameter.
For example:
● If the DB_6_P_A option of the CellCspcPara.eCspcPCAdjRange parameter is

selected and the CellDlpcPdschPa.PaPcOff parameter is set to DB_3_P_A, the
downlink transmit power of the cell can be adjusted to –6 dB or –3 dB.

eRAN
● If the DB_6_P_A and DB_4DOT77_P_A options of the

CellCspcPara.eCspcPCAdjRange parameter are selected and the
CellDlpcPdschPa.PaPcOff parameter is set to DB_3_P_A, the downlink
transmit power of the cell can be adjusted to –6 dB, –4.77 dB, or –3 dB.
Updating the UE Transmit Power

If QPSK or beamforming is not used for the UEs whose transmit power is to be
adjusted, the eNodeB obtains the sizes of the last scheduled RBs, sorts the RBs in
descending order by size, and adjusts the transmit power of a maximum of two
UEs.
If QPSK or beamforming is used for the UEs whose transmit power is to be
adjusted, the eNodeB adjusts the transmit power of all UEs of this type. In this
scenario, the transmit power change is notified only to the physical layer but not
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, or coordinated multipoint transmission/reception
(CoMP) UEs.
6.8.2.1 Benefits
This function is recommended only when all of the following conditions are met:
● Networking: one massive MIMO cell (acting as the serving cell) + multiple
non-massive-MIMO macro cells (acting as neighboring cells and causing
strong interference)
● Load: The PRB usage of each cell is greater than 80%.
● Overlapping coverage rate: In the massive MIMO cell, more than 40% of UEs
experience interference from two cells. In the non-massive-MIMO cells, more
than 40% of UEs cause interference between these cells.
NOTE
If the difference between the UE-reported serving cell RSRP and neighboring cell RSRP
is less than 6 dB, this UE causes interference.
● CQI: The average CQI 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 cells cooperating
with the serving cell, however, may decrease.

eRAN
6.8.2.2 Impacts
Network Impacts
● Inter-cell power coordination improves the downlink spectral efficiency of
heavy-load massive MIMO cells in densely populated urban areas.
● 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.
● If the distribution of downlink PRB usages between cells is imbalanced, the
gain of inter-cell power coordination increases.
● 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.
● 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 Cell.TxRxMode 4 Basic Massive The serving cell

introduction set to 32T32R or MIMO Functions must be a
64T64R massive MIMO
cell.

eRAN
Cloud BB None USU3910-based In inter-eNodeB

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

Interference ● ECO_BASED Interference None

randomization value of the Randomizing
CellAlgoSwitc (TDD)
h.InterfRandS
witch
parameter on
the eNodeB
side
● McirAlgoSwitc
h parameter
on the
eCoordinator
side
Adaptive inter-cell ACT AICIC Adaptive ICIC None

interference command
coordination executed on the
eCoordinator
CSPC CellCspcPara.Cell CSPC None

CspcSwitch

eRAN
High speed Cell.HighSpeedFl High Speed In high-speed

mobility ag Mobility mobility
scenarios, cell
load changes so
rapidly that
downlink power
adjustment
cannot promptly
follow the load
changes.
Inter-eNodeB DL InterDlCompDcsS DL CoMP (TDD) None

CoMP witch and
InterDlCompCbfS
witch options of
the
CellAlgoSwitch.D
lCompSwitch
parameter
Intra-frequency None Soft Split None

split Resource Duplex
(TDD)
Inter-frequency None Soft Split None
split IFSSFuncSwitch Resource Duplex
option of the (TDD)
ENodeBAlgoSwit
ch.SSRDAlgoSwit
ch parameter
Extended cell Cell.CellRadius Extended Cell Enhanced
range Range coordinated
scheduling based
power control
(eCSPC) requires
that the radius of
each cell involved
should not exceed
15 km. If the
radius exceeds 15
km, eCSPC does
not take effect.
Inter-cell InterCellDmimoJ D-MIMO (TDD) None

downlink D- TSwitch option of
MIMO the
CellAlgoSwitch.D
MIMOAlgoSwitc
h parameter

eRAN
Dynamic Power CellDynPowerSh Dynamic Power None

Sharing Between aring.DynamicPo Sharing Between
LTE Carriers werSharingSwitc LTE Carriers
h
Energy saving SymbolPwrSavin Energy eCSPC and
based on g.TrigBndlSchDlA Conservation and bundled
proactive vgPrbThld Emission scheduling cannot
scheduling Reduction both take effect.
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:
● Base station models: 3900 and 5900 series base stations
● Boards: BBPs except the LBBPc and LBBPd
● RF modules: no requirements
6.8.3.4 Others
PLMN information must be configured for the eNodeBs that serve the cells with
this feature enabled. If the PLMN information is not configured, routes cannot be
set up.

Table 6-23 describes the parameters used for function activation.
Cell eCSPC Switch CellCspcPara.CelleCspcS Set this parameter to

witch ON.
eCSPC A3 Offset CellCspcPara.eCspcA3Of Set this parameter as

fset required.
PA for even power CellDlpcPdschPa.PaPcOf Set this parameter as

distribution f required.

eRAN
eCSPC Power Control CellCspcPara.eCspcPCA For details, see 6.8.1

Adjustment Range djRange Principles.
eCSPC PC Adjustment UE CellCspcPara.eCspcPCA It is recommended that

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

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

//Turning off the cell-level eCSPC switch
MOD CELLCSPCPARA: LocalCellId=0, CelleCspcSwitch=OFF;

Maintenance.

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.
Management. On the Signaling Trace Management window, choose LTE > Cell
Performance Monitoring > CSPC (Cell) Monitoring. Double-click CSPC (Cell)

eRAN
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 For UEs subject to PA changes, choose Monitor > Signaling Trace > Signaling
Trace Management on the MAE-Access. 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.Index0

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:
● The value of the eCspc Data Link Status parameter is UNAVAILABLE.
● The value of the eCspc Coordinate Cell Link Delay Status parameter is Yes.
Rectify the fault by referring to eX2 Self-Management.

eRAN
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 of UEs with Low Aggregation Levels
Figure 7-2 Background for introducing preferential scheduling of UEs with low
aggregation levels
If uplink-downlink subframe configuration 2 is used, downlink data cannot be

transmitted in subframes 2 or 7, and more downlink data is transmitted in
subframes 3 and 8. This will limit uplink and downlink DCI transmission resources
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 of

the CellPdcchAlgo.PdcchOptimizationSwitch parameter. After this function takes
effect, the eNodeB sorts MU beamforming UEs in subframes 3 and 8 in ascending
order of their previous initial PDCCH CCE aggregation levels and selects the most
suitable UEs for pairing. This function increases the number of MU beamforming
UEs scheduled on the PDCCH in subframes 3 and 8, the number of paired layers in
the cell, and the 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:
● Uplink-downlink subframe configuration 2 is used.
● A massive MIMO cell is set up.
● The MuBfSwitch option of the CellAlgoSwitch.MuBfAlgoSwitch parameter
is selected.

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

● The downlink equivalent CCE usage with CFIs fixed to 3 is less than 60%.
● The CFIs of subframes 3 and 8 are 3.
● The number of available downlink CCEs is less than or equal to 12.
● The downlink PRB usage is greater than 60%.
Enhanced Symbol Adaptation

This function is controlled by the CellPdcchAlgo.PdcchSymNumSwitch
parameter. When the CellPdcchAlgo.PdcchSymNumSwitch parameter is set to
ECFIADAPTIONON to enable this function, 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,
number of paired layers in the cell, and average downlink UE throughput.
Optimization of Enhanced Symbol Adaptation

After optimization of enhanced symbol adaptation is enabled in a heavy-load
massive MIMO cell, the eNodeB estimates the number of PDCCH symbols based
on the number of UEs to be scheduled, to better match the required PDCCH
resources. This increases the number of MU beamforming UEs scheduled on the
PDCCH per TTI, number of paired layers in the cell, and average downlink UE
throughput.
This function is controlled by the CellPdcchAlgo.PdcchSymNumSwitch

parameter. When the CellPdcchAlgo.PdcchSymNumSwitch parameter is set to
MM_HEAVY_LOAD_ECFI_ADAPT_ON, this function is enabled.
This function takes effect only when all of the following conditions are met:
● The MuBfSwitch option of the CellAlgoSwitch.MuBfAlgoSwitch parameter
is selected.
● The CellPdcchAlgo.CceMaxInitialRatio parameter is set to 10_1.
● The equivalent CCE usage with CFIs fixed to 3 exceeds or equals 60%, and the
downlink CCE allocation failure rate exceeds or equals 20%.
PDCCH Aggregation Level Prioritization

PDCCH resources are severely limited in big event scenarios. To schedule more
UEs, the eNodeB needs to preferentially schedule UEs with low PDCCH
aggregation levels and then schedule UEs with high PDCCH aggregation levels.
For this purpose, PDCCH aggregation level prioritization is introduced.
The CellUSParaCfg.DlCceSchPriorityPenaltyLvl and

CellUSParaCfg.UlCceSchPriorityPenaltyLvl parameters are used to control
PDCCH aggregation level prioritization for downlink and uplink, respectively. This
function takes effect when both parameters are set to values other than NONE
and PDCCH resources are insufficient (the cell CCE usage or equivalent CCE usage
is greater than 60%).

eRAN
After this function takes effect, the eNodeB lowers the scheduling priorities of UEs
with PDCCH aggregation levels 4 and 8, saving PDCCH resources and increasing
the number of scheduled UEs.
7.2.2.1 Benefits
Preferential scheduling of UEs with low aggregation levels alleviates the problem
that the cell capacity is suppressed when PDCCH resources are insufficient in
massive MIMO cells. This increases the average downlink cell throughput and
average downlink UE throughput. This function can achieve the largest gain if the
proportion of aggregation level 8 is greater than or equal to 10% and the
proportion of aggregation level 1 is greater than or equal to 30%.
Optimization of enhanced symbol adaptation in a heavy-load massive MIMO cell
increases the number of MU beamforming UEs scheduled on the PDCCH per TTI,
number of paired layers in the cell, and average downlink UE throughput. If a
massive MIMO cell does not meet the heavy-load conditions, this function does
not take effect automatically.
PDCCH aggregation level prioritization increases the number of scheduled UEs
when PDCCH resources are insufficient (the cell CCE usage or equivalent CCE
usage is greater than 60%) in big event scenarios. This function does not take
effect if required conditions are not met.
NOTE

● Average downlink UE throughput = User Downlink Average Throughput
● Proportion of aggregation level 8 = L.ChMeas.PDCCH.AggLvl8Num /
(L.ChMeas.PDCCH.AggLvl1Num + L.ChMeas.PDCCH.AggLvl2Num +
L.ChMeas.PDCCH.AggLvl4Num + L.ChMeas.PDCCH.AggLvl8Num) x 100%
● CCE usage = (L.ChMeas.CCE.ULUsed + L.ChMeas.CCE.DLUsed) / ((60 x 60 x 200) x (88
+ 55 + 84 + 88)) x 100%
● A massive MIMO cell is considered to be heavily loaded when the equivalent CCE usage
with CFIs fixed to 3 exceeds or equals 60% and the downlink CCE allocation failure rate
exceeds or equals 20%.
● Equivalent CCE usage with CFIs fixed to 3 = (L.ChMeas.CCE.ULUsed.Equivalent +
L.ChMeas.CCE.DLUsed.Equivalent) / ((60 x 60 x 200) x (88 + 55 + 84 + 88)) x
100%
● Downlink CCE allocation failure rate = L.ChMeas.CCE.DL.AllocFail /

eRAN
7.2.2.2 Impacts
Network Impacts
● If both PDCCH and PDSCH resources are limited, PDCCH capacity
enhancement may decrease the average downlink cell throughput and
downlink spectral efficiency.
● Preferential scheduling of UEs with low aggregation levels may slightly
decrease the CEU perceived rate.
● The downlink spectral efficiency, average downlink cell throughput, and
average downlink UE throughput may decrease if enhanced PDCCH symbol
adaptation is enabled in moderate- or light-load scenarios.
● The downlink cell spectral efficiency may slightly decrease if optimization of
enhanced symbol adaptation is enabled when the CQI is lower than 9.
● PDCCH aggregation level prioritization lowers the scheduling priorities of UEs
with PDCCH aggregation levels 4 and 8. As a result, the priorities of some
CEUs decrease, and the user-perceived rates of these UEs may decrease.
NOTE
● Downlink spectral efficiency = L.Thrp.bits.DL / (L.Cell.DL.PDSCH.Tti.Num x

L.ChMeas.PRB.DL.DrbUsed.Avg)
Function Impacts
None
7.2.3 Requirements
7.2.3.1 Licenses
None
7.2.3.2 Software

eRAN
Massive MIMO 32T32R or 4 Basic Massive All the functions

introduction 64T64R value of MIMO Functions of PDCCH
the capacity
Cell.TxRxMode improvement
parameter require massive
MIMO
introduction.
Subframe Cell.SubframeAss Subframe Preferential

configuration ignment Configuration scheduling of UEs
(TDD) with low
aggregation levels
requires uplink-
downlink
subframe
configuration 2.
CCE Max Initial CellPdcchAlgo.Cc None Set this parameter

Ratio eMaxInitialRatio to 10_1 for
preferential
scheduling of UEs
with low
aggregation
levels.
Downlink 8-layer MuBfSwitch 6.2 MU Preferential

MU beamforming option of the Beamforming scheduling of UEs
Downlink 16-layer CellAlgoSwitch. with low
MU beamforming MuBfAlgoSwitch aggregation levels
parameter requires downlink
8-layer MU
beamforming or
downlink 16-layer
MU beamforming.
Downlink 4-layer MuBfSwitch Beamforming Preferential

MU beamforming option of the (TDD) scheduling of UEs
CellAlgoSwitch. with low
MuBfAlgoSwitch aggregation levels
parameter requires downlink
CellBf.HighOrder 4-layer MU
MubfMaxLayer beamforming.

eRAN
PDCCH STRATEGYBASED Physical Channel Optimization of

aggregation level ONCAPACITY Resource enhanced symbol
adaptation value of the Management adaptation and
CellPdcchAlgo.PD PDCCH
CCHAggLvlAdapt aggregation level
Strage parameter prioritization
depend on
capacity-based
PDCCH
aggregation level
adaptation.

None
7.2.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.

Name
PDCCH CellPdcchAlg To enable enhanced symbol adaptation or

Optimization o.PdcchOpti preferential scheduling of UEs with low
Switch mizationSwit aggregation levels, select the
ch LOW_AGG_PREFERENTIAL_SCH_SW option.
PDCCH CellPdcchAlg To enable enhanced symbol adaptation, set

Symbol o.PdcchSymN this parameter to ECFIADAPTIONON.
Number umSwitch
Adjust Switch
PDCCH CellPdcchAlg To enable optimization of enhanced symbol

Symbol o.PdcchSymN adaptation, set this parameter to
Number umSwitch MM_HEAVY_LOAD_ECFI_ADAPT_ON.
Adjust Switch

eRAN

Name
Downlink CCE CellUSParaCf To enable PDCCH aggregation level

Sch Priority g.DlCceSchPri prioritization, set this parameter. The value
Penalty Level orityPenaltyL LEVEL_THREE is recommended.
vl
Uplink CCE CellUSParaCf To enable PDCCH aggregation level
Sch Priority g.UlCceSchPri prioritization, set this parameter. The value
Penalty Level orityPenaltyL LEVEL_THREE is recommended.
vl

//Enabling preferential scheduling of UEs with low aggregation levels
MOD CELLPDCCHALGO: LocalCellId=0, PdcchOptimizationSwitch=LOW_AGG_PREFERENTIAL_SCH_SW-1;
//Enabling enhanced symbol adaptation
MOD CELLPDCCHALGO: LocalCellId=0, PdcchSymNumSwitch=ECFIADAPTIONON;
//Enabling optimization of enhanced symbol adaptation
MOD CELLPDCCHALGO: LocalCellId=0, PdcchSymNumSwitch=MM_HEAVY_LOAD_ECFI_ADAPT_ON;
//Enabling PDCCH aggregation level prioritization
MOD CellUSParaCfg: LocalCellId=0, DlCceSchPriorityPenaltyLvl=LEVEL_THREE;
MOD CellUSParaCfg: LocalCellId=0, UlCceSchPriorityPenaltyLvl=LEVEL_THREE;

//Deactivating preferential scheduling of UEs with low aggregation levels
MOD CELLPDCCHALGO: LocalCellId=0, PdcchOptimizationSwitch=LOW_AGG_PREFERENTIAL_SCH_SW-0;
//Deactivating enhanced symbol adaptation
MOD CELLPDCCHALGO: LOCALCELLID=0, PdcchSymNumSwitch=OFF;
//Deactivating optimization of enhanced symbol adaptation
MOD CELLPDCCHALGO: LocalCellId=0, PdcchSymNumSwitch=OFF;
//Deactivating PDCCH aggregation level prioritization
MOD CellUSParaCfg: LocalCellId=0, DlCceSchPriorityPenaltyLvl=NONE;
MOD CellUSParaCfg: LocalCellId=0, UlCceSchPriorityPenaltyLvl=NONE;


Step 1 Run the LST CELLPDCCHALGO command. If a value of PDCCH Optimization
Switch is LOW_AGG_PREFERENTIAL_SCH_SW:On, preferential scheduling of UEs
with low aggregation levels has been enabled.
Step 2 Run the LST CELLPDCCHALGO command. If the value of PDCCH Symbol
Number Adjust Switch is Enhanced CFI Adaption On, enhanced symbol
adaptation has been enabled.
Step 3 Run the LST CELLPDCCHALGO command. If the value of PDCCH Symbol
Number Adjust Switch is MM_HEAVY_LOAD_ECFI_ADAPT_ON, optimization of
enhanced symbol adaptation has been enabled.

eRAN
Step 4 Run the LST CELLUSPARACFG command. If the values of Downlink CCE Sch
Priority Penalty Level and Uplink CCE Sch Priority Penalty Level are not NONE,
PDCCH aggregation level prioritization has been enabled.
----End

1526728261 L.Thrp.bits.DL
1526729005 L.Thrp.bits.DL.LastTTI
1526729015 L.Thrp.Time.DL.RmvLastTTI
1526728763 L.ChMeas.PRB.DL.DrbUsed.Avg
1526728997 L.Thrp.Time.Cell.DL.HighPrecision
1526728668 L.ChMeas.PDCCH.AggLvl1Num
1526730558 L.Cell.DL.PDSCH.Tti.Num
NOTE

● CCE usage = (L.ChMeas.CCE.ULUsed + L.ChMeas.CCE.DLUsed) / [(60 x 60 x 200) x (88
+ 55 + 84 + 88)] x 100%
● Equivalent CCE usage = (L.ChMeas.CCE.ULUsed.Equivalent +
L.ChMeas.CCE.DLUsed.Equivalent) / [(60 x 60 x 200) x (88 + 55 + 84 + 88)] x 100%
● Average downlink cell 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.

eRAN
7.3.1 Principles
Uplink overload optimization is categorized into uplink retransmission scheduling
optimization and uplink power control optimization.
Uplink Retransmission Scheduling Optimization

There are a large number of UEs that require uplink retransmission when uplink
load is heavy. Before uplink retransmission scheduling optimization is introduced,
non-adaptive retransmission is preferentially used for UEs that require
retransmission. RBs occupied by such UEs cause uplink frequency resources to be
discontinuous. However, uplink RBs must be continuous for a UE. As a result, UEs
with uplink large packets may not obtain required resources. To address this issue,
uplink retransmission scheduling optimization is introduced, as illustrated in
Figure 7-4.
Figure 7-4 Uplink retransmission scheduling optimization
This function is controlled by the MmUlHeavyLoadOptSwitch option of the

CellUlschAlgo.VmimoOptAlgoSwitch parameter. When this option is selected,
adaptive retransmission is used for UEs that require retransmission in heavy load
scenarios. The eNodeB can adjust the positions of frequency resources occupied by
such UEs, making more RBs continuous and improving 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 DMRS SINR measurement but not based on
post-pairing MCS index reduction. As a result, the MCS indexes may decrease
significantly after the pairing and the uplink power of paired CCUs cannot be
increased. To address this issue, uplink power control optimization is introduced.
This function is controlled by the CellPcAlgo.MmCellCentSinrThldAdjValue

eRAN
parameter. If this parameter is set to a value other than 0, this function is enabled.
In heavy-load scenarios, this function considers the impact of post-pairing MCS
index reduction on the uplink power control SINR threshold during uplink power
control, allowing the uplink power of paired CCUs to be increased and thereby
improving the uplink spectral efficiency.
7.3.2.1 Benefits
● Uplink retransmission scheduling optimization
This function increases the uplink PRB usage of a cell and further 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%.
● 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%.
7.3.2.2 Impacts
Network Impacts
● Uplink retransmission scheduling optimization
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

L.ChMeas.PDCCH.DL.DTXNum.AggLvl2 + L.ChMeas.PDCCH.DL.DTXNum.AggLvl4 +
L.ChMeas.PDCCH.DL.DTXNum.AggLvl8) / (L.ChMeas.PDCCH.AggLvl1Num +
● Uplink power control optimization
The growth in the uplink power of CCUs may lead to an increase in 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.

eRAN

Introduction
7.3.3.2 Software
Massive MIMO 32T32R or 4 Basic Massive Both uplink

introduction 64T64R value of MIMO Functions retransmission
the optimization and
Cell.TxRxMode uplink power
parameter control
optimization
require massive
MIMO
introduction to be
purchased.

None
7.3.3.3 Hardware

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

eRAN
Vmimo Optimization CellUlschAlgo.VmimoO If uplink retransmission

Algorithm Switch ptAlgoSwitch scheduling optimization
is required, select the
MmUlHeavyLoadOptS-
witch option.
Massive MIMO Cell CellPcAlgo.MmCellCent Set this parameter when

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

//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 optimization has been enabled.

eRAN

1526728664 L.ChMeas.PDCCH.DL.DTXNum.AggLvl1

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

N/A
7.4 SRS Interference 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).

eRAN
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 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 The massive MIMO cell

are preferentially is divided into the left
allocated to UEs in the and right parts so that
clockwise direction to the time-frequency
the boundary beam, and resources preferentially
comb 0 SRS resources allocated to UEs for SRS
are preferentially transmission are
allocated to UEs in the staggered between cells.
counterclockwise This function mitigates
direction to the inter-cell interference
boundary beam, as and improves the SRS
shown in Figure 7-5. SINR when being used
with the SRS time-
domain measurement
function (described in
7.5 SRS Time-Domain
Measurement and
SDNR).

eRAN
Figure 7-5 Interference avoidance principles
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.
● A large target SRS SINR value for power control is recommended if there is
only one massive MIMO cell.
● 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 noise power (NP) of the cell and determines whether

eRAN
to send SRS NP indicators to cells in the interference neighboring cell list based on
the following principles.
If... Then...
The average SRS NP value is greater Sends SRS-NP-HIGH signals to

than the upper threshold of –112 dBm, neighboring cells in the interference
and there are more than 100 UEs in neighboring cell list.
the cells
The average SRS NP value is less than Sends SRS-NP-LOW signals to

the lower threshold of –115 dBm neighboring cells in the interference
neighboring cell list.
The average SRS NP value ranges from Sends SRS-NP-HOLD signals to

the upper threshold to the lower neighboring cells in the interference
threshold neighboring cell list.
After receiving an SRS NP indicator, a 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
neighboring cell is received SINR 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.
The SRS-NP-HOLD signal sent by the Does not adjust the UE-level target
neighboring cell is received SRS SINR value for power control.
NOTE
● 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.
● SRS NP values refer to the interference plus noise power values measured on SRS
symbols.
SRS IC
SRS IC reduces or eliminates the SRS interference of inter- or intra-eNodeB intra-
frequency neighboring cells by means of interference cancellation, improving the
SRS SINR, as shown in Figure 7-6.

eRAN
Figure 7-6 Example of SRS IC
A local cell in which SRS IC is enabled must be a massive MIMO cell. A

neighboring cell producing intra-frequency interference can be a massive MIMO or
non-massive-MIMO cell.
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. For details about SRS SDNR, see SRS SDNR.
This function is controlled by the MASSIVE_MIMO_SRS_IC_SW option under the
CellUlIcAlgo.SrsIcSwitch parameter.
7.4.2.1 Benefits
● SRS resource allocation optimization for interference avoidance: It improves
MU beamforming performance when multiple massive MIMO cells are
deployed on a single eNodeB.
● SRS power control optimization: It adaptively adjusts the target SRS SINR for
power control, reduces inter-cell interference in contiguous networking
scenarios, and improves MU beamforming performance. This function is
recommended in low-speed scenarios with more than 100 RRC_CONNECTED
UEs and SRS interference (that is, the value of L.UpPTS.Interference.Avg
exceeds –118 dB and the proportion of pre-equalized SRS SINRs less than –8
dB exceeds 20%).
● SRS IC:
– This function improves MU beamforming performance and User
Downlink Average Throughput by reducing or eliminating SRS
interference between intra- or inter-eNodeB intra-frequency neighboring
cells.
– If the number of UEs in neighboring cells is small, this function has a
small gain.

eRAN
– If the overlapping coverage rate between neighboring cells and the local
cell is small, this function has a small gain.
7.4.2.2 Impacts
Network Impacts
● MU beamforming performance improves.
● SRS resource allocation optimization for interference avoidance may prolong
the SRS period of certain UEs when UEs are unevenly distributed in the left
and right areas of a boundary beam. A prolonged SRS period affects the
beamforming performance of moving UEs and may decrease the downlink
cell throughput.
● SRS power control optimization aims to increase the average SRS SINR in
contiguous cells. After SRS power control optimization is enabled, the SRS
SINR may decrease in cells with light load and high uplink SRS SINR but the
average SRS SINR will increase in contiguous cells.
● SRS power control optimization increases the number of RRC connection
reconfiguration messages, leading to an increased service drop rate.
● After SRS IC is enabled:
– Downlink performance improves, which may increase the number of
uplink Transfer Control Protocol (TCP) packets. As a result, the uplink
spectral efficiency may decrease.
– If SRS interference is low, uplink pilot timeslot (UpPTS) interference may
increase; this decreases SRS SINRs and accordingly the number of
downlink paired layers and the proportion of beamforming. If SRS
interference is high, UpPTS interference will decrease; this increases SRS
SINRs, the number of downlink paired layers, and the proportion of
beamforming.
Function Impacts
SRS-expansion- SRSCfg.SrsResExp 7.15 SRS- If both SRS-

based precise ansionSwitch set Expansion-based expansion-based
beamforming to Precise precise
SRS_RES_EXPANS Beamforming beamforming and
ION_MODE SRS resource
allocation
optimization for
interference
avoidance are
enabled, the
average SRS
perioda may be
prolonged.

eRAN
SRS interference WTTxSRSIntrfAv Massive MIMO While both SRS

avoidance oidanceSw option Optimization in interference
of the WTTx Scenarios avoidance and
SRSCfg.SrsCfgPol (TDD) SRS resource
icySwitch allocation
parameter optimization for
interference
avoidance reduce
SRS interference,
the former
delivers better
performance.
After SRS
interference
avoidance is
enabled, it is not
recommended
that SRS resource
allocation
optimization for
interference
avoidance be
enabled.
Otherwise, the
performance of
SRS interference
avoidance may
deteriorate in
WTTx scenarios.
Note a: Average SRS period = (L.Traffic.User.2msSRS.Avg x 2 + L.Traffic.User.

5msSRS.Avg x 5 + L.Traffic.User.10msSRS.Avg x 10 + L.Traffic.User.
320msSRS.Avg x 320) / (L.Traffic.User.2msSRS.Avg + L.Traffic.User.5msSRS.Avg
+ L.Traffic.User.10msSRS.Avg + L.Traffic.User.20msSRS.Avg + L.Traffic.User.
40msSRS.Avg + L.Traffic.User.80msSRS.Avg + L.Traffic.User.160msSRS.Avg +
L.Traffic.User.320msSRS.Avg)
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 Cell.TxRxMode 4 Basic Massive SRS resource

introduction set to 32T32R or MIMO Functions allocation
64T64R optimization for
interference
avoidance and
SRS IC require
massive MIMO
introduction.
Space-domain SPACE_DOMAIN_ None If a neighboring

measurement MEAS_SW option cell is not a
of the massive MIMO
CellAlgoExtSwitc cell, enable space-
h.MeasOptAlgoE domain
xtSw parameter measurement
before enabling
SRS power control
optimization
enhancement.
SRS power control CellPcAlgo.SrsPcS None If a neighboring

policy trategy set to cell is not a
SRSPC_SINR_ADA massive MIMO
PTIVE cell, select the
SINR-based
adaptive SRS
power control
algorithm before
enabling SRS
power control
optimization
enhancement.
Cloud BB None Cloud BB SRS resource

Overview allocation
USU3900-based optimization for
Multi-BBU interference
Interconnection avoidance and
SRS IC require
USU3910-based that inter-eNodeB
Multi-BBU routes be
Interconnection
reachablea.

eRAN
SRS measurement ● NCellSrsMeas None SRS power control

Para.SrsAutoN optimization and
CellMeasSwitc SRS IC require SRS
h measurement.
● NCellSrsTime NOTE
MeasSwitch In non-massive-
MIMO scenarios,
option of the
SRS power control
NCellSrsMeas optimization does
Para.NCellMea not require the
sSwitch setting of the
parameter NCellSrsTimeMea
sSwitch option of
the
NCellSrsMeasPara
.NCellMeasSwitch
parameter.
SRS time-domain SrsTimeMeasSwi 7.5 SRS Time- SRS IC requires

measurement tch option of the Domain SRS time-domain
CellAlgoSwitch.S Measurement measurement.
rsAlgoSwitch and SDNR
parameter
SRS power control SrsPcSwitch Power Control The

option of the CellPcAlgo.SrsPcS
CellAlgoSwitch.U trategy
lPcAlgoSwitch parameter can be
parameter used to control
the SRS power
control policy only
when the
SrsPcSwitch
option of the
CellAlgoSwitch.U
lPcAlgoSwitch
parameter is
selected.
a: The Cloud BB networking supports the following two modes:

● Coordination over relaxed backhaul: In this mode, no USU needs to be
deployed. The X2 or eX2 interface is used between eNodeBs.
● Coordination over ideal backhaul: In TDD, only centralized networking is
supported. The USU3910 needs to be deployed (with eX2 interfaces used
between eNodeBs) or the USU3900 needs to be deployed (with ODI
interfaces used between eNodeBs).

eRAN

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
For details, see 4.3.3 Hardware. The UBBPem does not support SRS IC. If the
UBBPg3b is configured to support both LTE TDD and NR, it does not support SRS
IC.


SRS Interference Avoid SRSCfg.SrsInterfAvoidO Set this parameter to

Optimization Switch ptSwitch CLOCKWISE_COMB1
when SRS resource
allocation optimization
for interference
avoidance is enabled.

eRAN
Srs Power Control CellPcAlgo.SrsPcStrateg Set this parameter to

Strategy y SRSPC_SINR_ADAPTIVE
when SRS power control
optimization is enabled.
SRS Auto Neighbour Cell NCellSrsMeasPara.SrsA Set this parameter to ON

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

Measurement Switch MeasSwitch NCellSrsTimeMeasS-
witch option under this
parameter when SRS
power control
Uplink power control CellAlgoSwitch.UlPcAlg Select the SrsPcSwitch

algorithm switch oSwitch 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_IC
_SW option.
SoundingRS algorithm CellAlgoSwitch.SrsAlgo If SRS IC is enabled,

switch Switch select the
SrsTimeMeasSwitch
option.
Massive MIMO CellMMAlgo.MMAlgoO When SRS IC is enabled,

Algorithm Optimization ptSwitch select the
Switch SRS_SDNR_SWITCH
option to enable SRS
SDNR to further improve
the performance.
Group hopping enabled PUSCHCfg.GroupHoppi When enabling SRS IC,

ngEnabled set this parameter to
BOOLEAN_FALSE for the
local and neighboring
cells.
Sequence hopping PUSCHCfg.SeqHoppingE When enabling SRS IC,

enabled nabled set this parameter to
BOOLEAN_FALSE for the
local and neighboring
cells.

eRAN

● SRS resource allocation optimization for interference avoidance
//Enabling SRS resource allocation optimization for interference avoidance
MOD SRSCFG: LocalCellId=0, SrsInterfAvoidOptSwitch=CLOCKWISE_COMB1;
● SRS power control optimization

//(Non-massive-MIMO scenarios) Enabling SRS power control optimization
MOD CELLALGOSWITCH: LocalCellId=1, UlPcAlgoSwitch=SrsPcSwitch-1;
MOD NCELLSRSMEASPARA: LocalCellId=1, SrsAutoNCellMeasSwitch=ON;
MOD CELLPCALGO: LocalCellId=1, SrsPcStrategy=SRSPC_SINR_ADAPTIVE;
//(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;
//Setting the interface type when no eX2 link is configured between base stations and X2 is used for
message transmission
MOD GLOBALPROCSWITCH: ItfTypeForNonIdealModeServ=X2;
● SRS IC
//Performing the following operations for the local cell
//Enabling SRS IC
MOD PUSCHCFG: LocalCellId=0, GroupHoppingEnabled=BOOLEAN_FALSE,
SeqHoppingEnabled=BOOLEAN_FALSE;
MOD CELLALGOSWITCH: LocalCellId=0, SrsAlgoSwitch=SrsTimeMeasSwitch-1;
NCellMeasSwitch=NCellSrsTimeMeasSwitch-1;
MOD CELLULICALGO: LocalCellId=0, SrsIcSwitch=MASSIVE_MIMO_SRS_IC_SW-1;
MOD CELLMMALGO: LocalCellId=0, MMAlgoOptSwitch=SRS_SDNR_SWITCH-1;
//Performing the following operations for neighboring cells

NCellMeasSwitch=NCellDmrsMeasSwitch-0&NCellSrsTimeMeasSwitch-1;
//Running the following commands only when a neighboring cell is a massive MIMO cell and it also
requires SRS IC

● SRS resource allocation optimization for interference avoidance
//Deactivating SRS resource allocation optimization for interference avoidance
MOD SRSCFG: LocalCellId=0, SrsInterfAvoidOptSwitch=OFF;
● SRS power control optimization

//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;
● SRS IC
//Deactivating SRS IC


eRAN
Maintenance.

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

After this function is enabled, observe the User Downlink Average Throughput
(N/A, LTE eNodeB) for network monitoring.
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 space-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
paired 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 space-domain noise reduction (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 its
antennas to identify the strength of interference with UE 0 in each direction.
During channel estimation, the interference from neighboring cells is mitigated,
improving the channel estimation accuracy and beamforming weight accuracy.
Figure 7-7 Principles of SRS SDNR
7.5.2.1 Benefits
● SRS time-domain measurement
This function improves the SRS measurement accuracy and SRS SINR,
enhancing the performance of SU beamforming and MU beamforming.
● SRS SDNR
This function improves the channel estimation accuracy, User Downlink
Average Throughput, and average number of paired layers in MU
beamforming (L.ChMeas.MassiveMIMO.MUBF.Avg.PairLayer). If the target
cell is opposite the interfering cell, this function offers lower gains but does
not have negative impacts.
7.5.2.2 Impacts
Network Impacts
● SRS time-domain measurement: none
● SRS SDNR: This function has an impact on the following counters:

eRAN
– 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 32T32R or 4 Basic Massive Both SRS time-

introduction 64T64R value of MIMO Functions domain
the measurement and
Cell.TxRxMode SRS SDNR require
parameter massive MIMO
introduction.
SRS resource SRSCfg.SrsCfgInd Physical Channel Both SRS time-

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

None
7.5.3.3 Hardware

eRAN

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

switch Switch SrsTimeMeasSwitch
option when SRS time-
domain measurement is
required.
Massive MIMO CellMMAlgo.MMAlgoO Select the

Algorithm Optimization ptSwitch SRS_SDNR_SWITCH
Switch option when SRS SDNR
is required.

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


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



Run the LST CELLALGOSWITCH command to query the status of the
SrsTimeMeasSwitch option under the SoundingRS algorithm switch parameter.

eRAN
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
After this function is enabled, observe the following counters and User Downlink
Average Throughput for network monitoring.
1526745708 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.

eRAN
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:
● 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.
● Slightly improves the downlink spectral efficiency of the entire network if
most UEs are allocated with short SRS periods and are not located in the cell
center.
Function Impacts
Name
Multi-user SplitSdmaSwitch 6.5 Multi- After beamforming

split SDMA option of the User Split weight optimization is
CellAlgoSwitch.MuBf SDMA enabled, UEs with low
AlgoSwitch SRS SINRs will not
parameter enter multi-user split
SDMA. UEs with low
SRS SINRs already in
multi-user split SDMA
mode will exit this
mode.
7.6.3 Requirements
7.6.3.1 Licenses
Beamforming weight optimization uses the license for Massive MIMO
Introduction.

Introduction

eRAN
7.6.3.2 Software
Name

introduction MIMO
Functions
Downlink BfSwitch option of 6.1 3D None

flexible 3D the Beamformin
beamforming CellAlgoSwitch.BfAlg g
oSwitch parameter
Device-pipe SpecUeIdentifySwitc Specified User Beamforming weight
identification h option of the Coordinated optimization requires
UeCooperationPara.S Scheduling either of the functions
pecUserCooperationS to be enabled.
witch parameter
WBB UE SpidCfg.SpecifiedUse WBB
identification rFlag or
CellQciPara.ServiceFl
ag

None
7.6.3.3 Hardware

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

eRAN

BF Weight Optimization CellBf.BfWeightOptDeg This parameter must not

Degree Factor reeFactor be 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 CellBf.BfWeightOptChn The value 0 is

Quality Thld Offset QltyThldOfs recommended.

//Configuring the beamforming weight optimization degree factor and the offset to the channel quality
threshold for beamforming weight optimization
MOD CELLBF: LocalCellId=0, BfWeightOptDegreeFactor=200, BfWeightOptChnQltyThldOfs=0;

//Configuring the beamforming weight optimization degree factor
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 to

L.ChMeas.PUSCH.MCS.31
1526739777 L.ChMeas.MUBF.1stLayer.PairPRB.Tot

eRAN
1526739778 to 1526745737 L.ChMeas.MUBF.

2ndLayer.PairPRB.Succ to
L.ChMeas.MUBF.
16thLayer.PairPRB.Succ
1526745879 L.Thrp.bits.DL.WBB
1526745954 L.ChMeas.PRB.DL.PDSCH.WBBUsed.A
vg
1526746696 L.Thrp.bits.DL.UECooperation
1526746697 L.ChMeas.PRB.DL.DrbUsed.Avg.UECo
operation
Average downlink cell spectral efficiency = L.Thrp.bits.DL /

7.7 IRC
This section describes TDLEOFD-150613 Advanced Massive MIMO IRC.
7.7.1 Principles
Interference rejection combining (IRC) improves reception performance at the
physical layer based on MU-MIMO, as shown in Figure 7-8.
Figure 7-8 IRC
IRC provides the following functions:

eRAN
● Uplink receive enhancement

– Multiple antennas are used to perform IRC, improving the capability of
combating spatially colored interference from neighboring cells.
– The interference estimation mechanism has been optimized in multi-user
pairing scenarios, enhancing the antenna equalization robustness and
improving demodulation performance and post-pairing throughput.
– This function is controlled by the PUSCH_RECEIVE_ENH_SWITCH option
of the CellMMAlgo.MMAlgoOptSwitch parameter.
● Uplink pairing optimization
– The mechanism for determining the number of uplink paired layers for
MU-MIMO is optimized. Five to eight layers can be paired when there is a
small number of uplink RBs.
– This function requires uplink 8-layer MU-MIMO to be enabled and is
controlled by the CellUlschAlgo.EnhancedVmimoSwitch parameter.
Setting this parameter to ON increases the average number of paired
layers for MU-MIMO and the average uplink cell throughput.
– When 32 antennas are used, this function requires the
PUSCH_RECEIVE_ENH_SWITCH option of the
CellMMAlgo.MMAlgoOptSwitch parameter to be selected. When 64
antennas are used, there is no such requirement.
7.7.2.1 Benefits
Uplink receive enhancement achieves higher average uplink cell throughput,
average uplink UE 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 PRB usage of a cell exceeds
60%, the average number of uplink paired layers exceeds 3, and the
L.UL.Interference.Avg counter value exceeds –108 dBm.
When there are many uplink small-packet services, it is recommended that the
uplink pairing optimization function be enabled to increase the average number of
paired layers for MU-MIMO and the average uplink cell throughput.
If the uplink equivalent CCE usage in CFI adaptation mode exceeds 90%, uplink
CCE resources are limited. As a result, the number of uplink paired UEs is limited,
and the gains of uplink receive enhancement are affected. Therefore, it is
recommended that the CellPdcchAlgo.CceMaxInitialRatio parameter be set to
10_1 when uplink receive enhancement is enabled in uplink heavy-load scenarios.

eRAN
NOTE
● Average uplink UE throughput = User Uplink Average Throughput (N/A, LTE eNodeB)
● 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)
● Uplink PRB usage of the cell = L.ChMeas.PRB.UL.Used.Avg/L.ChMeas.PRB.UL.Avail
● Average number of uplink paired 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
● Uplink equivalent CCE usage in CFI adaptation mode =
L.ChMeas.CCE.ULUsed.Equivalent/L.ChMeas.CCE.ULAvailPower.Equivalent
7.7.2.2 Impacts
Network Impacts
● Uplink receive enhancement
– After this function takes effect, the measured interference and noise may
increase as the measurement mechanism changes, but demodulation
performance is not affected.
– After this function 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 idle mode more quickly. As a
result, the number of paging messages increases, resulting in negative
gains in the downlink.
● Uplink pairing optimization
– When the uplink PRB load is not heavy, the single-user-perceived rate
may decrease. When the uplink PRB load is heavy, the proportion of 5- to
8-layer pairing improves significantly and the uplink and downlink BLERs
may increase.
– After this function is enabled, the number of uplink paired layers
increases in medium- and heavy-load scenarios. This has the following
impacts:
▪ The uplink interference with neighboring cells may increase.
▪ The uplink cell spectral efficiency and uplink user experience improve
in most scenarios but may deteriorate in rare scenarios where
channels are highly correlated.
▪ The uplink IBLER and RBLER may increase.
Function Impacts
None
7.7.3 Requirements

eRAN
7.7.3.1 Licenses
TDLEOFD-150613 Advanced Massive LT4SMMULRE00 Per Cell

MIMO IRC
7.7.3.2 Software
Uplink 2x32 MU- UlVmimoSwitch 5.2 MU-MIMO IRC requires

MIMO or uplink option of the uplink 2x32 MU-
2x64 MU-MIMO CellAlgoSwitch.U MIMO or uplink
lSchSwitch 2x64 MU-MIMO
parameter, and to be enabled.
CellUlschAlgo.Ma
xLayerMMVMIM
O parameter set
to 2LAYER
UL 8-Layer MU- UlVmimoSwitch 5.2 MU-MIMO Uplink pairing

MIMO option of the optimization
CellAlgoSwitch.U requires uplink 8-
lSchSwitch layer MU-MIMO
parameter to be enabled.
PUSCH receivers MrcIrcAdptSwitc MRC and IRC Uplink pairing

h option of the Receivers optimization
CellAlgoSwitch.P requires the
uschIrcAlgoSwitc PUSCH receiver to
h parameter be enabled.

None
7.7.3.3 Hardware
For details, see 4.3.3 Hardware. BBPs cannot be UBBPem.

eRAN

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

Name
Massive CellMMAlgo.PUSCH_RECEI To enable the uplink receive

MIMO MMAlgoOptS VE_ENH_SWIT enhancement function, select
Algorithm witch CH this option.
Optimization To enable the uplink pairing
Switch optimization function in
scenarios with 32 antennas,
select this option.
CCE Max CellPdcchAlg None Set this parameter to 10_1.

Initial Ratio o.CceMaxIniti
alRatio
Enhanced CellUlschAlg None If there are a large number of
VMIMO o.EnhancedV uplink small-packet services, it
Switch mimoSwitch is recommended that the
uplink pairing optimization
function be enabled by setting
this parameter to ON.
PUSCH IRC CellAlgoSwit MrcIrcAdptSw To enable the uplink pairing

algorithm ch.PuschIrcAl itch optimization function, select
switch goSwitch this option.

//Turning on the MRC/IRC adaptation switch
MOD CELLALGOSWITCH: LocalCellId=0, PuschIrcAlgoSwitch=MrcIrcAdptSwitch-1;
//Enabling enhanced PUSCH reception

MOD CELLMMALGO: LocalCellId=0, MMAlgoOptSwitch=PUSCH_RECEIVE_ENH_SWITCH-1;
//Configuring the maximum initial CCE ratio

MOD CELLPDCCHALGO: LocalCellId=0, CceMaxInitialRatio=10_1;
//Enabling enhanced MU-MIMO

MOD CELLULSCHALGO: LocalCellId=0, EnhancedVmimoSwitch=ON;

//Disabling enhanced MU-MIMO
MOD CELLULSCHALGO: LocalCellId=0, EnhancedVmimoSwitch=OFF;

eRAN
//Disabling enhanced PUSCH reception

MOD CELLMMALGO: LocalCellId=0, MMAlgoOptSwitch=PUSCH_RECEIVE_ENH_SWITCH-0;

Maintenance.

Step 1 Run the LST CELLMMALGO command. If the value of Massive MIMO Algorithm
Optimization Switch is PUSCH_RECEIVE_ENH_SWITCH:On, uplink receive
enhancement has been enabled.
Step 2 For scenarios with 64 antennas, run the LST CELLULSCHALGO command. If the
value of Enhanced VMIMO Switch is ON, uplink pairing optimization has been
enabled.
Step 3 For scenarios with 32 antennas, uplink pairing optimization has been enabled if
● The LST CELLULSCHALGO command output shows that the value of
Enhanced VMIMO Switch is On.
● The LST CELLMMALGO command output shows that a value of Massive
MIMO Algorithm Optimization Switch is
PUSCH_RECEIVE_ENH_SWITCH:On.
----End

1526728298 L.UL.Interference.Avg
1526727369 L.Traffic.UL.SCH.QPSK.TB.bits
1526727370 L.Traffic.UL.SCH.16QAM.TB.bits
1526727371 L.Traffic.UL.SCH.64QAM.TB.bits
1526728764 L.ChMeas.PRB.PUSCH.Avg
1526726737 L.ChMeas.PRB.UL.Used.Avg
1526728434 L.ChMeas.PRB.UL.Avail

eRAN
1526739782 L.ChMeas.VMIMO.PairPRB2Layer.Suc
c
c
c
c
c
c
c
1526729295 L.ChMeas.CCE.ULUsed.Equivalent
1526743711 L.ChMeas.CCE.ULAvailPower.Equivale
nt
1526728259 L.Thrp.bits.UL
1526729415 L.Thrp.bits.UE.UL.SmallPkt
1526729416 L.Thrp.Time.UE.UL.RmvSmallPkt
● Average uplink UE throughput = User Uplink Average Throughput

● 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)
● Uplink PRB usage of the cell = L.ChMeas.PRB.UL.Used.Avg/
L.ChMeas.PRB.UL.Avail
● Average number of uplink paired layers =
(L.ChMeas.VMIMO.PairPRB2Layer.Succ +
L.ChMeas.VMIMO.PairPRB3Layer.Succ +
L.ChMeas.VMIMO.PairPRB8Layer.Succ)/
L.ChMeas.VMIMO.PairPRB2Layer.Succ + 1
● Uplink equivalent CCE usage in CFI adaptation mode =
L.ChMeas.CCE.ULUsed.Equivalent/L.ChMeas.CCE.ULAvailPower.Equivalent

eRAN
7.8 Scheduling Optimization
7.8.1 Principles
The following describes the functions related to scheduling optimization.
Selective HARQ Scheduling in Subframes 3 and 8

In heavy-load scenarios, available CCE resources are limited in the downlink. As a
result, there is a decrease in the number of UEs scheduled, downlink PRBs
allocated, or layers paired in downlink subframes 3 and 8. To solve this issue,
selective HARQ scheduling in subframes 3 and 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 target UEs (which require a small number of CCEs
and large resource blocks) for downlink HARQ retransmission scheduling in
subframes 3 and 8 if all of the following conditions are met:
● The CellPdcchAlgo.PDCCHAggLvlAdaptStrage parameter is set to
STRATEGYBASEDONCAPACITY.
● The downlink PRB usage is greater than 60%.
● The downlink equivalent CCE usage with CFIs fixed to 3 is less than 60%.
● The CFIs of subframes 3 and 8 are 3.
● The number of available downlink CCEs is less than or equal to 12.
NOTE
Downlink equivalent CCE usage with CFIs fixed to 3 = L.ChMeas.CCE.DLUsed.Equivalent /

((60 x 60 x 200) x (88 + 55 + 84 + 88)) x 100%
It is recommended that this function be used with preferential scheduling of UEs

with low aggregation levels (for initial transmission optimization) to increase the
number of PRBs scheduled in subframes 3 and 8, increasing the downlink cell
throughput and average downlink UE throughput.
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
of 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.

eRAN
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 of 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.
Beamforming Cell-Level Initial CQI Adjustment Value Optimization

Before this function is introduced, the initial CQI adjustment value is fixed and
specified by the CellCqiAdjAlgo.InitDeltaCqi parameter. For burst services on the
live network, this initial CQI adjustment value makes it difficult for the IBLER to
converge to the target value specified by the CellCqiAdjAlgo.InitDlIblerTarget
parameter. This affects the traffic channel reliability and cell spectral efficiency. To
address this issue, beamforming cell-level initial CQI adjustment value
optimization is introduced.
This function optimizes the initial CQI adjustment value for newly admitted UEs.
This function is controlled by the MM_DL_SCH_AND_MCS_OPT_SWITCH option
of the CellMMAlgo.MMAlgoOptSwitch parameter. After this function is enabled,
the initial CQI adjustment value is obtained as follows:
1. The eNodeB determines the position of an online UE based on its reported 5-
bit wideband CQI.
If the reported 5-bit wideband CQI is less than or equal to 9, the UE is located
at the cell edge. If the CQI is greater than 9 but less than or equal to 15, the
UE is located at a medium distance from the cell center. In other situations,
the UE is in the cell center. The eNodeB measures the cell-level initial CQI
adjustment values in different positions in the cell for each codeword.
NOTE
The reported 5-bit wideband CQI is calculated based on the 4-bit CQI reported by the
UE. The conversion formula is as follows:
5-bit wideband CQI = 2 x 4-bit CQI – 4
2. When a UE is newly admitted, the eNodeB determines the UE position as
described in 1 and selects the corresponding cell-level initial CQI adjustment
value as the UE's initial CQI adjustment value.
Downlink Correlation-based UE Pairing Optimization

In a UE pairing procedure of MU beamforming, UE correlation judgment is
relatively loose. The downlink correlation-based UE pairing optimization function
is introduced to improve judgment accuracy by performing more judgments on UE
correlation.
This function is controlled by the DL_CORR_UE_PAIRING_OPT_SWITCH option of
the CellMMAlgo.MMAlgoOptSwitch parameter. Selecting this option will

eRAN
improve the downlink pairing performance and increase the average downlink cell
throughput and average downlink UE throughput.
Downlink Low-SRS-SINR UE Pairing Optimization

In a UE pairing procedure of MU beamforming, a UE can be selected as a
candidate for pairing only when its SRS SINR exceeds an internal threshold. In
scenarios with SRS interference or poor coverage, however, if there is a large
proportion of UEs whose SRS SINR is lower than the internal threshold, the overall
downlink cell performance will deteriorate as these UEs occupy a large number of
PRBs. To address this issue, the downlink low-SRS-SINR UE pairing optimization
function is introduced.
This function is controlled by the CellMMAlgo.LowSrsSinrUePairLayerThld
parameter. When this parameter is set to a value other than 0 and 1, the function
is enabled. The eNodeB allows a UE to be involved in downlink pairing when the
following conditions are met:
● The UE SRS SINR is in the range from the internal threshold set by this
optimization function to the internal threshold used in the UE pairing
procedure of MU beamforming.
● The CQI is higher than a threshold.
This function increases the number of downlink paired layers in a cell and
therefore increases the average downlink throughput of the cell.
Downlink RB Scheduling Proportion Limitation for SU Beamforming UEs

When MU beamforming is enabled and the proportion of SU beamforming UEs
(UEs not meeting pairing conditions) is high in heavy-load scenarios, scheduling
SU beamforming UEs occupies a large number of downlink RBs. As a result, the
proportion of downlink RBs available for MU beamforming UEs (UEs meeting
pairing conditions) is low, decreasing the average downlink cell throughput. To
address this issue, downlink RB scheduling proportion limitation for SU
beamforming UEs is introduced.
This function is controlled by the CellMMAlgo.DlSubfPrbUsageRestrThld
parameter. If this parameter is set to a value other than 100 and the proportion of
downlink RBs scheduled for SU beamforming UEs exceeds the parameter value,
the eNodeB lowers the downlink scheduling priority of SU beamforming UEs to
limit this proportion. This increases the proportion of downlink RBs available for
MU beamforming UEs, the average number of layers paired for downlink MU
beamforming, and the average downlink cell throughput.
This function adjusts the scheduling priorities of SU beamforming UEs and MU
beamforming UEs. Therefore, enabling this function may affect functions related
to priority adjustment.
7.8.2.1 Benefits
● Selective HARQ scheduling in subframes 3 and 8 prevents the cell capacity
from being suppressed due to insufficient PDCCH resources in massive MIMO

eRAN
cells, increasing the average downlink UE throughput and downlink cell

throughput.
● Downlink RB allocation optimization increases the average downlink UE
throughput and average downlink cell spectral efficiency in heavy-load
scenarios.
● 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.
● Beamforming cell-level initial CQI adjustment value optimization improves
the reliability of traffic channels and the average downlink cell throughput for
burst services on live networks.
● Downlink correlation-based UE pairing optimization increases the average
downlink cell throughput and average downlink UE throughput when only a
small number of UEs need to be paired in the downlink in a cell. If the
required conditions are not met, this function does not provide noticeable
gains.
● Downlink low-SRS-SINR UE pairing optimization
This function increases the number of downlink paired layers and therefore
increases the average downlink cell throughput and average downlink UE
throughput when all the following conditions are met. If the following
conditions are not met, this function does not provide noticeable gains.
– The proportion of low-SRS-SINR UEs is high.
– The number of downlink paired layers is less than the
CellMMAlgo.LowSrsSinrUePairLayerThld parameter value.
● Downlink RB scheduling proportion limitation for SU beamforming UEs
If all of the following conditions are met, this function increases the
proportion of downlink RBs scheduled for MU beamforming UEs, the average
number of layers paired for downlink MU beamforming, and the average
downlink cell throughput, and may increase the number of scheduled UEs. If
the following conditions are not met, this function does not provide
noticeable gains.
– The proportion of SU beamforming UEs is high.
– The average downlink PRB usage in the cell reaches or exceeds 80%.
– The average number of downlink active UEs in the cell reaches or exceeds
20.
– The average number of layers paired for downlink MU beamforming in
the cell reaches or exceeds 2.
NOTE
● The gains of downlink RB allocation optimization depend on the proportion of UEs

allocated a small number of RBs and proportion of the first and last RBGs scheduled.
● Average number of paired layers in downlink MU beamforming =
L.ChMeas.MassiveMIMO.MUBF.Avg.PairLayer
● Downlink cell throughput = L.Thrp.bits.DL / L.Traffic.Sch.DL.Num
● Downlink spectral efficiency = L.Thrp.bits.DL / (L.Cell.DL.PDSCH.Tti.Num x

eRAN
7.8.2.2 Impacts
Network Impacts
● Selective HARQ scheduling in subframes 3 and 8
– The average downlink cell throughput may decrease.
– The average downlink cell spectral efficiency may slightly decrease
because an increasing number of downlink PRBs are scheduled in
subframes 3 and 8.
NOTE

● Downlink RB allocation optimization
– In light- or medium-load scenarios, the average downlink UE throughput
and average downlink cell spectral efficiency may decrease, 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.
NOTE

● Proportion of PDCCH DTXs = (L.ChMeas.PDCCH.DL.DTXNum.AggLvl1 +
● 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.
● Beamforming cell-level initial CQI adjustment value optimization
– If the volume of burst services is large and traffic channels are heavily
loaded, this function increases the average downlink cell throughput.
However, if there are only a few ACK/NACK reports from online UEs, the
downlink BLER may increase, the average downlink cell throughput may
decrease, and the user-perceived rate may decrease.
– If the proportion of MU beamforming UEs is high but the proportion of
online SU beamforming UEs is low, the cell-level initial CQI adjustment
value may be inaccurate. As a result, the downlink BLER increases, the
average downlink cell throughput decreases, and the user-perceived rate
may decrease.
● Downlink correlation-based UE pairing optimization

eRAN
This function uses a stricter correlation judgment algorithm. The number of

downlink paired layers may slightly decrease, the downlink MCS index may
slightly increase, and the downlink IBLER may slightly decrease.
● Downlink low-SRS-SINR UE pairing optimization
As the number of downlink paired layers increases, the downlink IBLER and
RBLER increase, the downlink MCS index may decrease, the average PDCP
SDU delay may decrease or increase, and the first-packet delay may decrease.
NOTE
Average PDCP SDU 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)
First-packet delay = L.Traffic.DL.EmptyBuf.PDCPLat.Time /
L.Traffic.DL.EmptyBuf.PDCPLat.Num
● Downlink RB scheduling proportion limitation for SU beamforming UEs
– After this function is enabled, the User Downlink Average Throughput
of CEUs may decrease. When traffic is imbalanced, the average downlink
UE throughput in a cell may slightly decrease. In uplink congestion
scenarios, the User Uplink Average Throughput may slightly decrease.
– After this function is enabled, the downlink user-perceived rate (User
Downlink Average Throughput) may decrease. The main reason is that
the proportion of downlink tail packets may increase after the downlink
spectral efficiency is improved and scheduling is accelerated. As a result,
the value of L.Thrp.bits.DL minus the value of L.Thrp.bits.DL.LastTTI
decreases, the value of L.Thrp.Time.DL.RmvLastTTI also decrease, and
the downlink user-perceived rate may not increase.
Proportion of downlink tail packets = L.Thrp.bits.DL.LastTTI /
L.Thrp.bits.DL x 100%
Function Impacts
RAN sharing with SHARED_FREQ RAN Sharing When both

common carrier value of the downlink RB
ENodeBSharingM scheduling
ode.ENodeBShari proportion
ngMode limitation for SU
parameter beamforming UEs
and RAN sharing
with common
carrier are
enabled, the
proportion of
downlink RBs
scheduled for
each operator
may change.

eRAN
7.8.3 Requirements
7.8.3.1 Licenses
None
7.8.3.2 Software
Massive MIMO Cell.TxRxMode 4 Basic Massive All functions of

introduction set to 32T32R or MIMO Functions scheduling
64T64R optimization take
effect in massive
MIMO cells.
PDCCH CellPdcchAlgo.PD Physical Channel Selective HARQ

aggregation level CCHAggLvlAdapt Resource scheduling in
adaptation Strage set to Management subframes 3 and
STRATEGYBASED 8 depends on
ONCAPACITY capacity-based
PDCCH
aggregation level
adaptation.
Uplink-downlink Cell.SubframeAss Subframe Selective HARQ

subframe ignment Configuration scheduling in
configuration 1&2 (TDD) subframes 3 and
8 depends on
uplink-downlink
subframe
configuration 2.

eRAN
Adaptive setting CellCqiAdjAlgo.C Channel State Beamforming cell-

of the initial cell- ellCqiAdjSchCntT Management level initial CQI
level CQI hld adjustment value
adjustment value optimization
requires that cell-
level initial CQI
adjustment value
adaptation be
enabled, that is,
the
CellCqiAdjAlgo.C
ellCqiAdjSchCntT
hld parameter be
set to a non-zero
value.
Downlink 8-layer MuBfSwitch 6.2 MU All functions of

MU beamforming, option of the Beamforming scheduling
downlink 16-layer CellAlgoSwitch. optimization
MU beamforming, MuBfAlgoSwitch require that any
or downlink 24- parameter function of MU
layer MU beamforming be
beamforming enabled.
(trial)

None
7.8.3.3 Hardware

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

eRAN

Parameter Parameter ID Option Setting Notes
Name
PDCCH CellPdcchAlg SF_3_8_HARQ Select this option when

Optimization o.PdcchOpti _SELECTIVE_S enabling selective HARQ
Switch mizationSwit CH_SW scheduling in subframes 3 and
ch 8.
Massive CellMMAlgo.DL_RB_ASSIG Select this option when

MIMO MMAlgoOptS N_OPT_SWIT enabling downlink RB
Algorithm witch CH allocation optimization.
Optimization
Switch CellMMAlgo. MM_DL_SCH_ Select this option when
MMAlgoOptS AND_MCS_OP enabling MCS index selection
witch T_SWITCH optimization for downlink
paired UEs with small-amount
data transmission or when
enabling beamforming cell-
level initial CQI adjustment
value optimization.
CellMMAlgo.DL_CORR_UE_ Select this option when

MMAlgoOptS PAIRING_OPT enabling downlink correlation-
witch _SWITCH based UE pairing optimization.
Cell CQI CellCqiAdjAl None Set this parameter to a value

Adjustment go.CellCqiAdj other than 0 based on the
Schedule SchCntThld network plan.
Count Thld
Low SRS SINR CellMMAlgo. None Set this parameter to a value

UE Pairing LowSrsSinrU other than 0 and 1. The value
Layer Thld ePairLayerTh 4 is recommended when
ld downlink low-SRS-SINR UE
pairing optimization is
required.
DL SUBF PRB CellMMAlgo. None The value 20 is recommended

Usage DlSubfPrbUs when downlink RB scheduling
Restriction ageRestrThld proportion limitation for SU
Thld beamforming UEs is required.

//Enabling selective HARQ scheduling in subframe 3 or 8
MOD CELLPDCCHALGO: LocalCellId=0, 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 cell-level initial CQI adjustment value adaptation before enabling beamforming cell-level initial
CQI adjustment value optimization, with the CellCqiAdjSchCntThld parameter set based on network plans

eRAN
MOD CELLCQIADJALGO: LocalCellId=0, CellCqiAdjSchCntThld=50;
//Enabling MCS index selection optimization for downlink paired UEs with small-amount data transmission
or beamforming cell-level initial CQI adjustment value optimization
MOD CELLMMALGO: LocalCellId=0, MMAlgoOptSwitch=MM_DL_SCH_AND_MCS_OPT_SWITCH-1;
//Enabling downlink correlation-based UE pairing optimization
MOD CELLMMALGO: LocalCellId=0, MMAlgoOptSwitch=DL_CORR_UE_PAIRING_OPT_SWITCH-1;
//Enabling downlink low-SRS-SINR UE pairing optimization

MOD CELLMMALGO: LocalCellId=0, LowSrsSinrUePairLayerThld=4;
//Enabling downlink RB scheduling proportion limitation for SU beamforming UEs

MOD CELLMMALGO: LocalCellId=0, DlSubfPrbUsageRestrThld=20;

//Deactivating selective HARQ scheduling in subframe 3 or 8
MOD CELLPDCCHALGO: LocalCellId=0, 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 beamforming cell-level initial CQI adjustment value optimization
MOD CELLMMALGO: LocalCellId=0, MMAlgoOptSwitch=MM_DL_SCH_AND_MCS_OPT_SWITCH-0;
//Deactivating downlink correlation-based UE pairing optimization
MOD CELLMMALGO: LocalCellId=0, MMAlgoOptSwitch=DL_CORR_UE_PAIRING_OPT_SWITCH-0;
//Deactivating downlink low-SRS-SINR UE pairing optimization

MOD CELLMMALGO: LocalCellId=0, LowSrsSinrUePairLayerThld=0;
//Deactivating downlink RB scheduling proportion limitation for SU beamforming UEs

MOD CELLMMALGO: LocalCellId=0, DlSubfPrbUsageRestrThld=100;


Step 1 Run the LST CELLPDCCHALGO command. If the PDCCH Optimization Switch
parameter has a value of SF_3_8_HARQ_SELECTIVE_SCH_SW:On, selective HARQ
scheduling in subframes 3 and 8 has been enabled.
Step 2 Run the LST CELLMMALGO command. If the Massive MIMO Algorithm
Optimization Switch parameter has a value of
DL_RB_ASSIGN_OPT_SWITCH:On, downlink RB allocation optimization has been
enabled.
MM_DL_SCH_AND_MCS_OPT_SWITCH:On, MCS index selection optimization for
downlink paired UEs with small-amount data transmission or beamforming cell-
level initial CQI adjustment value optimization has been enabled.
DL_CORR_UE_PAIRING_OPT_SWITCH:On, downlink correlation-based UE pairing
Step 5 Run the LST CELLMMALGO command. If the Low SRS SINR UE Pairing Layer
Thld parameter has a value other than 0 and 1, downlink low-SRS-SINR UE
pairing optimization has been enabled.

eRAN
Step 6 Run the LST CELLMMALGO command. If the DL SUBF PRB Usage Restriction
Thld parameter has a value other than 100, downlink RB scheduling proportion
limitation for SU beamforming UEs has been enabled.
----End

1526729005 L.Thrp.bits.DL.LastTTI
1526729015 L.Thrp.Time.DL.RmvLastTTI
1526730873 L.Traffic.Sch.DL.Num
1526728997 L.Thrp.Time.Cell.DL.HighPrecision
● User Downlink Average Throughput

● Cell Downlink Average Throughput
● Proportion of PDCCH DTXs = (L.ChMeas.PDCCH.DL.DTXNum.AggLvl1 +

eRAN
7.9 MU Beamforming Pairing of Antenna Selection UEs

in Dual-Stream Beamforming
7.9.1 Principles
This function allows dual-stream antenna-selection UEs to participate in MU
beamforming in massive MIMO cells, improving network performance. This
function 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 Pairing of Antenna Selection UEs in Dual-Stream Beamforming

requires the following parameters to be set. For details about the parameter
settings, see 7.9.4.1.1 Data Preparation.
● Offset to the threshold for switching the transmission mode of antenna

selection UEs from rank-2 TM3 to dual-stream beamforming:
CellBfMimoParaCfg.AsUeTM3Rank2ToDualBfOffset
selection UEs from dual-stream beamforming to rank-2 TM3:
CellBfMimoParaCfg.AsUeDualBfToTM3Rank2Offset
selection UEs 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 provide feedback in multiplexing mode, increasing the
downlink user-perceived 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 non-antenna-selection UEs. 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 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 a UE with its chip supporting antenna

selection but its RF module not supporting antenna selection. As a whole, fake
antenna selection UEs do not support antenna selection. However, these UEs claim
their support for antenna selection in the reported RRC_UE_CAP_INFO message.
Figure 7-9 shows the differences between antenna selection UEs and fake
antenna selection UEs.

eRAN
Figure 7-9 Differences between antenna selection UEs and fake antenna selection
UEs
NOTE
Unless otherwise specified, non-antenna-selection UEs include fake antenna selection UEs.
When the ACK_FEEDBACK_IN_MUX_MODE_SW option of the

CellBf.DualStreamBfAlgoSw parameter is deselected and the
ANT_SEL_SCHEDULING_OPT_SWITCH option of the
CellAlgoExtSwitch.AntennaSelectionAlgoSwitch parameter is selected, both
scheduling optimization for antenna selection UEs and pairing optimization for
dual-stream UEs (with one stream for initial data transmission and the other
stream for data retransmission) take effect, improving downlink scheduling
performance.
When the ACK_FEEDBACK_IN_MUX_MODE_SW option of the
CellBf.DualStreamBfAlgoSw parameter is selected and the
ANT_SEL_SCHEDULING_OPT_SWITCH option of the
CellAlgoExtSwitch.AntennaSelectionAlgoSwitch parameter is also selected, only
scheduling optimization for antenna selection UEs takes effect.
If MU Beamforming Pairing 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 user-perceived data rate and downlink cell
spectral efficiency.
If either of the following conditions is met, this function can offer the target gains
for antenna selection UEs (including 2T and 4T antenna selection UEs). If the
following conditions are not met, this function may have negative impacts and
therefore you are not advised to enable it.

eRAN
● The CQI value is greater than or equal to 11.

● The traffic distribution of online UEs meets the following requirements: total
traffic proportion of top 3 beams ≤ 80% and traffic proportion of top 1 beam
≤ 50%.
– The traffic proportion of online UEs served by a beam can be calculated
based on the value of the counters DLTrafficBits_Beam_0 to
DLTrafficBits_Beam_63 in the PERIOD_PRIVATE_BEAM_TRAFFIC external
CHR event. After online UEs are sorted in descending order of their traffic
proportions, the traffic proportion of top 3 beams and the traffic
proportion of top 1 beam can be obtained.
– Traffic proportion of online UEs served by beam i = DLTrafficBits_Beam_i/
Sum(DLTrafficBits_Beam_0, ..., DLTrafficBits_Beam_63)
It is recommended that antenna selection UEs (including 2T and 4T antenna
selection UEs) be placed every other beam so that the inter-UE correlation is low
enough and the gains are maximized in commercial use.
7.9.2.2 Impacts
Network Impacts
● If antenna selection UEs are paired, the number of data streams scheduled for
a single UE increases and the number of paired layers changes. In this case,
the downlink IBLER, downlink RBLER, and proportion of PDCCH DTXs may
fluctuate.
Downlink IBLER = (L.Traffic.DL.SCH.QPSK.ErrTB.Ibler + L.Traffic.DL.SCH.
16QAM.ErrTB.Ibler + L.Traffic.DL.SCH.64QAM.ErrTB.Ibler) /
(L.Traffic.DL.SCH.QPSK.TB + L.Traffic.DL.SCH.16QAM.TB +
L.Traffic.DL.SCH.64QAM.TB) x 100%
Downlink RBLER = (L.Traffic.DL.SCH.QPSK.ErrTB.Rbler + L.Traffic.DL.SCH.
16QAM.ErrTB.Rbler + L.Traffic.DL.SCH.64QAM.ErrTB.Rbler) /
(L.Traffic.DL.SCH.QPSK.TB + L.Traffic.DL.SCH.16QAM.TB +
L.Traffic.DL.SCH.64QAM.TB) x 100%
● To maximize the receive energy of two antennas on the UE side, pairing of
antenna selection UEs may change UE weight and UE correlation in contrast
to pairing of non-antenna selection UEs. Therefore, the measured value of the
L.ChMeas.MassiveMIMO.MUBF.Avg.PairLayer counter changes.

eRAN
Function Impacts
Switching to TM7 CellBf.MultiLayer Switching to MU Beamforming

in multi-layer ThdSwitchToTM7 TM7 in Multi- Pairing of
pairing scenarios Layer Pairing Antenna Selection
Scenarios UEs in Dual-
Stream
Beamforming
may affect
transmission
modes.
Heavy-load TMA HEAVYLOADTRA Heavy-Load TMA MU Beamforming

boost NSMODEADAPTB Boost Pairing of
OOSTSW and Antenna Selection
HISTORICALSPEC UEs in Dual-
TRALEFFOPTSW Stream
options under the Beamforming
CellBfMimoParaC may affect
fg.BfMimoAlgoO transmission
ptSwitch modes.
parameter
Dual-stream CellBf.MaxBfRan Beamforming UEs working in

beamforming kPara set to (TDD) dual-stream
DUAL_LAYER_BF beamforming
(TM8) can
provide feedback
in multiplexing
mode, increasing
the downlink
user-perceived
rate of such UEs.
Quick entry into CellBfMimoParaC None If the

beamforming fg.TmAcceleratio CellBf.Tm8Pairin
after initial nSwitch set to gOptSwitch
network access INITIAL_ACCESS_ parameter is set
TO_BF to ON and the
cell is lightly
loaded, quick
entry into
beamforming
after initial
network access
does not take
effect.

eRAN
TM9 port 5 Tm9Port5Switch Massive MIMO When MU

option of the Optimization in Beamforming
UeCooperationPa WTTx Scenarios Pairing of
ra.SpecUserCoop (TDD) Antenna Selection
erationSwitch UEs in Dual-
parameter Stream
Beamforming is
enabled, the TM9
port 5 function
does not forcibly
switch UEs to
TM7 and allows
UEs to stay in
open-loop TM9
mode.
7.9.3 Requirements
7.9.3.1 Licenses
None
7.9.3.2 Software
UE SRS antenna UeSRSAntSelectC None MU Beamforming

selection trlSwitch option Pairing of
exception control under the Antenna Selection
ENodeBAlgoSwit UEs in Dual-
ch.Compatibility Stream
CtrlSwitch Beamforming
parameter requires that the
eNodeB support
antenna selection
for SRS
transmission by
deselecting the
UeSRSAntSelectC
trlSwitch option.

eRAN
MU beamforming MuBfSwitch 6.2 MU MU Beamforming

option under the Beamforming Pairing of
CellAlgoSwitch. Antenna Selection
MuBfAlgoSwitch UEs in Dual-
parameter Stream
Beamforming
requires downlink
8-layer MU
beamforming or
downlink 16-layer
MU beamforming.

None
7.9.3.3 Hardware
7.9.3.4 Others
● UEs support TM8.
● UEs support antenna selection.
● UEs comply with 3GPP Release 9 or later.

Compatibility Control ENodeBAlgoSwitch.Com Clear the

Switch patibilityCtrlSwitch UeSRSAntSelectCtrlS-
witch option.
BF algorithm switch CellAlgoSwitch.BfAlgoS Select the

witch FakeAntSelIdentifica-
tionSwitch option.

eRAN
Beamforming maximum CellBf.MaxBfRankPara The value

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

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

Optimization Switch witch ON.
Dual-Stream BF CellBf.DualStreamBfAlg If the

Algorithm Switch oSw TddAckFbModeCfgOptS
witch option is selected
under the
CellAlgoSwitch.HarqAlg
oSwitch parameter, it is
ACK_FEEDBACK_IN_MU
X_MODE_SW option be
selected under the
CellBf.DualStreamBfAlg
oSw parameter.
AS UE TM3 Rank2 To CellBfMimoParaCfg.AsU Set this parameter to
Dual BF Offset eTM3Rank2ToDualBfOf -14.
fset
AS UE Dual BF To TM3 CellBfMimoParaCfg.AsU Set this parameter to
Rank2 Offset eDualBfToTM3Rank2Of -20.
fset
AS UE Single to Dual BF CellBfMimoParaCfg.AsU Set this parameter to 6.
Offset eBfSingleToDualOffset
Antenna Selection CellAlgoExtSwitch.Ante Select the
Algorithm Switch nnaSelectionAlgoS- ANT_SEL_SCHEDULING_
witch OPT_SWITCH option.
BfMimo Algorithm CellBfMimoParaCfg.Bf It is recommended that

Optimization Switch MimoAlgoOptSwitch the
NON_AS_UE_MAX_BF_R
ANK_CTRL_SW option
be selected to prevent
the entry of non-
antenna selection UEs
into dual-stream
beamforming (TM8).

eRAN

//Turning off the compatibility control switch
MOD ENODEBALGOSWITCH: CompatibilityCtrlSwitch=UeSRSAntSelectCtrlSwitch-0;
//Enabling 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 provide feedback in multiplexing mode
//Setting the thresholds related to UEs capable of 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;
//Prohibiting antenna selection UEs in TM8 from being paired for MU beamforming
MOD CELLBF: LocalCellId=0, AntSelUEMubfPairMode=SINGLE_STREAM_PAIR,
MaxBfRankPara=SINGLE_LAYER_BF, Tm8PairingOptSwitch=OFF;
//(Optional) Prohibiting UEs in dual-stream beamforming (TM8) from providing feedback in multiplexing
mode
//(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:On is displayed under the Dual-Stream BF

eRAN
Algorithm Switch parameter, UEs in dual-stream beamforming (TM8) can

provide feedback in multiplexing mode.
Step 3 (Optional) Run the LST CELLALGOEXTSWITCH command. If
ANT_SEL_SCHEDULING_OPT_SWITCH:On is displayed under the Antenna
Selection 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:On 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 antenna selection using the RRC_UE_CAP_INFO message, as shown in
Figure 7-10.
Figure 7-10 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-11.
This indicates that fake antenna selection UE identification has taken effect.

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

Beamforming
Use the MAE-Access 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-9 to determine whether MU Beamforming Pairing of Antenna Selection
UEs in Dual-Stream Beamforming has taken effect.
Table 7-9 Monitoring object for MU Beamforming Pairing of Antenna Selection

UEs in Dual-Stream Beamforming
Monitoring Object Meaning
Number of Massive Number of downlink RBs paired for TM8 UEs for MU
MIMO MUBF Pairing beamforming. It can be obtained by averaging the
TM8 RB (Num) number of RBs paired for TM8 UEs in each TTI in a
monitoring period.
When MU Beamforming Pairing of Antenna Selection UEs in Dual-Stream

Beamforming is enabled, the number of paired layers and PRBs increases and the
measured values of the following counters may reach 64 bits in length.

eRAN
7.10 Access Control Optimization Based on Uplink and

Downlink User-Perceived Rates
7.10.1 Principles
This function is controlled by the MM_ACCESS_CONTROL_OPT_SWITCH option
under the CellMMAlgo.MMAlgoOptSwitch parameter.
With this function in a massive MIMO cell, if the uplink or downlink user-
perceived rate is less than a specified target value and congestion occurs in the
uplink or downlink, the eNodeB uses access class (AC) barring to reduce UE access
opportunities, improving user experience.
7.10.2.1 Benefits
After this function is enabled in heavy-load scenarios, you can set a proper target
uplink or downlink user-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 user-perceived rates from dropping
to 0 Mbit/s and ensures that the target rate is reached. For details about the
impact on access, see the description of intelligent access class control in Access
Class Control.
Function Impacts
None
7.10.3 Requirements
7.10.3.1 Licenses
None
7.10.3.2 Software

eRAN
Massive MIMO 32T32R or 4 Basic Massive Access control

introduction 64T64R value of MIMO Functions optimization
the based on uplink
Cell.TxRxMode and downlink
parameter user-perceived
rates depends on
massive MIMO
introduction.
Dynamic service- ACBAR_SWITCH_ Access Class Access control

specific access DYNAMIC value Control optimization
control of the based on uplink
CellAlgoSwitch.A and downlink
cBarAlgoSwitch user-perceived
parameter rates requires the
CellAlgoSwitch.A
Extended access EABAlgoSwitch eMTC cBarAlgoSwitch
barring (EAB) option of the parameter to be
CellAlgoSwitch. set to
MTCCongControl ACBAR_SWITCH_
Switch parameter DYNAMIC or the
EABAlgoSwitch
option of the
CellAlgoSwitch.
MTCCongControl
Switch parameter
to be selected.
When the
CellAlgoSwitch.A
cBarAlgoSwitch
parameter is set
to
ACBAR_SWITCH_
DYNAMIC, it is
recommended
that the
CellAlgoSwitch.A
cBarAlgoforDynS
witch parameter
be set to
DYNAMIC_FOR_
MO.

None

eRAN
7.10.3.3 Hardware

Massive MIMO CellMMAlgo.MMAlgoO Select the

Algorithm Optimization ptSwitch MM_ACCESS_CONTROL
Switch _OPT_SWITCH option.
RB Congestion High CellRacThd.RbCongHig The value 90 is

Threshold hThd recommended.
CCE Allocation Failure CellRacThd.CceAlFailHi The value 40 is

High Threshold ghThd recommended.
UL Experience Rate CellRacThd.UlExperienc The value 50 is

Threshold eThd recommended.
DL Experience Rate CellRacThd.DlExperienc The value 1000 is

Threshold eThd recommended.
AC barring for mobile CellAcBar.AcBarringFor The value CFG is

data configure indicator MoDataCfgInd recommended.
AC barring for mobile CellAcBar.AcBarringFor The value CFG is

signal configure indicator MoSigCfgInd recommended.
Access probability factor CellAcBar.AcBarringFact The value P85 is

for signaling orForSig recommended.
Access probability factor CellAcBar.AcBarringFact The value P85 is

for originating call orForCall recommended.
Mean access barring CellAcBar.AcBarTimeFor Set this parameter to

time for originating call Call ACCESS_BARRING_TIME
_S4.
Mean access barring CellAcBar.AcBarTimeFor Set this parameter to

time for signaling Sig ACCESS_BARRING_TIME
_S4.
Dynamic AC Barring CellDynAcBarAlgo- The value 95 is

Control Trigger Para.DynAcBarTriggerT recommended.
Threshold hd

eRAN
MO Factor Initial Value CellDynAcBarAlgo- Set this parameter to

Para.MoFactorInitial- P95.
Value
MO Factor Adjusting CellDynAcBarAlgo- Set this parameter to 1.
Step Para.MoFactorAdjStep
MO Cancel Condition CellDynAcBarAlgo- Set this parameter to 1.

Satisfied Periods Para.MoCancelCondSati
Periods
MO Factor Retreating CellDynAcBarAlgo- Set this parameter to 2.
Step Para.MoFactorRetreat-
Step
AC barring information CellAcBar.AcBarringInfo Set this parameter to
configure indicator CfgInd CFG.

//Enabling massive MIMO access control optimization
MOD CELLMMALGO: LocalCellId=0, MMAlgoOptSwitch=MM_ACCESS_CONTROL_OPT_SWITCH-1;
//Modifying the configuration of admission and load control thresholds

MOD CELLRACTHD: LocalCellId=0, RbCongHighThd=90,CceAlFailHighThd=40,UlExperienceThd=50,
DlExperienceThd=1000;
//Modifying cell access barring information

MOD CELLACBAR: LocalCellId=0, AcBarringInfoCfgInd=CFG, AcBarringForMoDataCfgInd=CFG,
AcBarringFactorForCall=P85, AcBarTimeForCall=ACCESS_BARRING_TIME_S4,
AcBarringForMoSigCfgInd=CFG, AcBarringFactorForSig=P85, AcBarTimeForSig=ACCESS_BARRING_TIME_S4;
//Modifying the configurations of dynamic access barring of a cell

MOD CELLDYNACBARALGOPARA: LocalCellId=0, DynAcBarTriggerThd=95, MoFactorInitialValue=P95,
MoFactorAdjStep=1, MoCancelCondSatiPeriods=1, MoFactorRetreatStep=2;

//Disabling massive MIMO access control optimization
MOD CELLMMALGO: LocalCellId=0, MMAlgoOptSwitch=MM_ACCESS_CONTROL_OPT_SWITCH-0;


Run the LST CELLMMALGO command. If the Massive MIMO Algorithm
MM_ACCESS_CONTROL_OPT_SWITCH:On, this function has been enabled.
For details about how to monitor related counters, see the activation verification
description of intelligent access class control in Access Class Control.

eRAN

After this function is enabled, observe the following KPIs for network monitoring:
7.11 PDCCH Resource Reservation for Large-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 idle RB resources in the spatial
domain. To solve this issue, PDCCH resource reservation for large-packet services
in heavy-load scenarios is introduced.
This function is controlled by the HEAVY_LOAD_BIG_PKT_SCH_OPT_SW option of
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 large-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 function increases the downlink cell throughput and spectral efficiency when
PDCCH resources are insufficient (that is, when the downlink or uplink CCE
allocation failure rate is greater than 40% and the equivalent CCE usage with CFIs
fixed to 3 is greater than 60%). This function does not take effect in other
scenarios.
Formulas for calculating the downlink CCE allocation failure rate, uplink CCE
allocation failure rate, and equivalent CCE usage:
● Uplink CCE allocation failure rate = L.ChMeas.CCE.UL.AllocFail /
L.ChMeas.PDCCH.UL.AggLvl2Num + L.ChMeas.PDCCH.UL.AggLvl4Num +
L.ChMeas.PDCCH.UL.AggLvl8Num) x 100%

eRAN
● Equivalent CCE usage with CFIs fixed to 3 =

(L.ChMeas.CCE.ULUsed.Equivalent + L.ChMeas.CCE.DLUsed.Equivalent) /
((60 x 60 x 200) x (88 + 55 + 84 + 88)) x 100%
7.11.2.2 Impacts
Network Impacts
If PDSCH resources are limited, enabling this function may decrease the User
Downlink Average Throughput.
If large-packet UEs are at the cell edge, enabling this function may decrease the
downlink user-perceived rate as UEs with smaller MCS indexes are preferentially
scheduled.
Function Impacts
None
7.11.3 Requirements
7.11.3.1 Licenses
None
7.11.3.2 Software
MU beamforming MuBfSwitch option 6.2 MU Beamforming

under the
CellAlgoSwitch.MuBfAl
goSwitch parameter
Capacity-based PDCCH STRATEGYBASEDONCA- Physical Channel
CCE aggregation level PACITY option of the Resource Management
adaptation strategy CellPdcchAlgo.PDCCHA
ggLvlAdaptStrage
parameter

None

eRAN
7.11.3.3 Hardware


PDCCH Optimization CellPdcchAlgo.PdcchOp If PDCCH resource

Switch timizationSwitch reservation for large-
packet services in heavy-
load scenarios is
required, select the
HEAVY_LOAD_BIG_PKT_
SCH_OPT_SW option.

//Enabling the MU beamforming algorithm
MOD CELLALGOSWITCH: LocalCellId=0, MuBfAlgoSwitch=MuBfSwitch-1;
//Enabling optimized large-packet scheduling in heavy-load scenarios

MOD CELLPDCCHALGO: LocalCellId=0, PdcchOptimizationSwitch=HEAVY_LOAD_BIG_PKT_SCH_OPT_SW-1;

//Disabling optimized large-packet scheduling in heavy-load scenarios


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.


eRAN

(L.Cell.DL.PDSCH.Tti.NumxL.ChMeas.PRB.DL.DrbUsed.Avg)
7.12 Optimized PDCCH Aggregation Level Selection

Near the Cell Center
7.12.1 Principles
PDCCH aggregation levels are selected based on the CQI values adjusted based on
the PDSCH BLER. However, for cell-center UEs in a massive MIMO cell, 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.
Therefore, optimized PDCCH aggregation level selection near the cell center is
introduced.
This function is controlled by the HEAVY_LOAD_BIG_PKT_SCH_OPT_SW option of

the CellPdcchAlgo.PdcchOptimizationSwitch parameter. After this function is
enabled, PDCCH aggregation levels for cell-center UEs are determined based on
the PDCCH BLER and UE-reported CQI values. This increases the PDCCH capacity
while ensuring the PDCCH reliability, and improves the cell spectral efficiency.
NOTE
PDCCH resource reservation for large-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
When PDCCH resources are insufficient (that is, when the downlink or uplink CCE
allocation failure rate exceeds 40% and the equivalent CCE usage with CFIs fixed
to 3 exceeds 60%), this function reduces the CCE usage, increases the cell-level
PDCCH capacity, and improves the cell spectral efficiency if the downlink MCS
index is low due to either of the following reasons. This function does not take
effect in other scenarios.
● There are abnormal UEs.

● There are many MU beamforming UEs and MU beamforming pairing
performance is poor.
Formulas for calculating the downlink CCE allocation failure rate, uplink CCE
allocation failure rate, and equivalent CCE usage:

eRAN
● Uplink CCE allocation failure rate = L.ChMeas.CCE.UL.AllocFail /

L.ChMeas.PDCCH.UL.AggLvl2Num + L.ChMeas.PDCCH.UL.AggLvl4Num +
● Equivalent CCE usage with CFIs fixed to 3 =
(L.ChMeas.CCE.ULUsed.Equivalent + L.ChMeas.CCE.DLUsed.Equivalent) /
((60 x 60 x 200) x (88 + 55 + 84 + 88)) x 100%
7.12.2.2 Impacts
Network Impacts
If there are UEs (such as IRC-capable UEs) with reported CQI values greater than
expected, this function may affect the PDCCH reliability and decrease the user-
perceived rate due to lack of initial CQI adjustment value control.
Function Impacts
None
7.12.3 Requirements
7.12.3.1 Licenses
None
7.12.3.2 Software
Massive MIMO 32T32R or 64T64R value 4 Basic Massive MIMO

introduction of the Cell.TxRxMode Functions
parameter

None
7.12.3.3 Hardware

eRAN


PDCCH Optimization CellPdcchAlgo.PdcchOp If optimized PDCCH

Switch timizationSwitch aggregation level
selection near the cell
center is required, select
the
HEAVY_LOAD_BIG_PKT_
SCH_OPT_SW option.

//Enabling optimized large-packet scheduling in heavy-load scenarios

//Disabling optimized large-packet scheduling in heavy-load scenarios


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.

7.13 Intelligent Selection of Massive MIMO Parameters

This section describes TDLEOFD-151616 Intelligent Selection of Massive MIMO
Parameters.

eRAN
7.13.1 Principles
Overview
In big event scenarios, manual parameter adjustment cannot ensure network
performance in real time. To address this issue, intelligent selection of massive
MIMO parameters is introduced. This feature automatically adjusts parameters
related to massive MIMO cells in big event scenarios. It increases the average
downlink UE throughput, average downlink cell throughput, and downlink spectral
efficiency in heavy-load scenarios.
This feature is controlled by the BIG_EVENT_AUTO_ASSURANCE_SW option of

the CellMMAlgo.MmParamIntelSelectSw parameter. When this option is
selected, automatic assurance for massive MIMO big events is enabled.
Automatic assurance for massive MIMO big events is provided in the following
scenarios: PDCCH capacity enhancement, uplink interference optimization,
adaptive overload optimization, MLB parameter optimization, and RS adaptation.
For details, see the corresponding sections in 7.13.2 Automatic Assurance
Scenarios.
Procedure
Figure 7-12 illustrates the procedure of intelligent parameter selection after this
feature is enabled.
Figure 7-12 Intelligent parameter selection
The detailed procedure of intelligent parameter selection is as follows:
1. The eNodeB performs periodic data collection.
Measurement Formula
Item
Number of L.Traffic.User.Ulsync.Avg
uplink-
synchronized
UEs
(represented
by CU)

eRAN
Measurement Formula
Item
Number of L.Traffic.User.Ulsync.Avg x 20 MHz / Bandwidth

UEs in an
equivalent
bandwidth
Uplink PRB L.ChMeas.PRB.UL.Used.Avg / L.ChMeas.PRB.UL.Avail

usage
CCE allocation Number of failed CCE allocations / (Number of failed CCE

failure rate allocations + Number of successful CCE allocations)
● Uplink CCE allocation failure rate =
L.ChMeas.CCE.UL.AllocFail /
(L.ChMeas.CCE.UL.AllocFail +
L.ChMeas.PDCCH.UL.AggLvl1Num +
● Downlink CCE allocation failure rate =
L.ChMeas.CCE.DL.AllocFail /
(L.ChMeas.CCE.DL.AllocFail +
L.ChMeas.PDCCH.AggLvl1Num +
PUSCH L.UL.Interference.Avg
interference

eRAN
Measurement Formula
Item
PUCCH (L.UL.Interference.PUCCH.Index0 x Intf (0) +

interference L.UL.Interference.PUCCH.Index1 x Intf (1) + ... +
L.UL.Interference.PUCCH.Index15 x Intf (15)) /
(L.UL.Interference.PUCCH.Index0 +
L.UL.Interference.PUCCH.Index1 + ... +
L.UL.Interference.PUCCH.Index15)
Intf (0) = –121.5
Intf (1) = –120.5
Intf (2) = –119.5
Intf (3) = –118.5
Intf (4) = –117.5
Intf (5) = –116.5
Intf (6) = –115.5
Intf (7) = –114.5
Intf (8) = –113.5
Intf (9) = –112.5
Intf (10) = –110
Intf (11) = –106
Intf (12) = –102
Intf (13) = –98
Intf (14) = –94
Intf (15) = –90
2. The eNodeB checks trigger or rollback conditions.

The eNodeB determines whether trigger or rollback conditions are met in
each application scenario of automatic assurance for massive MIMO big
events based on the data collected in step 1.
Trigger conditions and rollback conditions for each automatic assurance
scenario are the combinations of different atom rules. For details, see the
corresponding sections in 7.13.2 Automatic Assurance Scenarios. You can
modify a trigger or rollback condition by activating or deactivating an atom
rule. Table 7-13 lists the atom rules.
Table 7-13 Atom rules

Atom Rule Description Atom Rule ID
(LIOptRuleMember.AtomRuleID)
CU > 300 101
CU < 250 102

eRAN
Atom Rule Description Atom Rule ID

(LIOptRuleMember.AtomRuleID)
PDCCH CCE allocation failure rate > 103

30%
PDCCH CCE allocation failure rate > 104

50%
Number of UEs in an equivalent 105

bandwidth > 700

bandwidth > 600

bandwidth < 500
PUCCH interference > –105 dBm 108
PUSCH interference > –105 dBm 109
Uplink PRB usage > 80% 110

bandwidth < 400
In atom rule 101 "CU > 300", 300 is the default value of atom rule 101.
In atom rule 102 "CU < 250", 250 is the default value of atom rule 102.
Whether the default values are used depends on the setting of the
BIG_EVENT_THLD_LEARN_SW option of the
CellMMAlgo.MmParamIntelSelectSw parameter, as listed in Table 7-14.
Table 7-14 Atom rules 101 and 102

Atom Rule ID Atom Rule When Atom Rule When
(LIOptRuleMember.At BIG_EVENT_THLD_LEA BIG_EVENT_THLD_LEA
omRuleID) RN_SW Is Selected RN_SW Is Deselected
101 CU > BigEventCU CU > 300
102 CU < BigEventCU – CU < 250

BigEventOffset
The following describes BigEventCU and BigEventOffset mentioned in Table

7-14.
– BigEventCU: It indicates a UE count threshold learned by the system.
The eNodeB determines the value of BigEventCU by learning based on
the CellMMAlgo.MmParamIntelSelectDlUxThld and
CellMMAlgo.MmParamIntelSelectUlUxThld parameter settings, and

eRAN
takes the value of BigEventCU as the UE count threshold in trigger or

rollback conditions.
– BigEventOffset: It indicates a UE count threshold offset, which is set to 50
by default.
3. The eNodeB adjusts parameter values.
When the trigger or rollback condition for the adjustment of a parameter is
met and the corresponding rule is activated, the eNodeB adjusts this
parameter for automatic assurance for massive MIMO big events.
All parameters that can be adjusted in automatic assurance for massive
MIMO big events have corresponding rule IDs (LIOptRule.RuleID). For
specific rule IDs and post-adjustment parameter values, see the corresponding
sections in 7.13.2 Automatic Assurance Scenarios.
7.13.2 Automatic Assurance Scenarios

Automatic assurance for massive MIMO big events is provided in the following
scenarios: PDCCH capacity enhancement, uplink interference optimization,
adaptive overload optimization, MLB parameter optimization, and RS adaptation.
7.13.2.1 PDCCH Capacity Enhancement

In big event scenarios, CCE resources are more likely to be insufficient. Parameters
related to PDCCH capacity can be automatically adjusted to improve the CCE
usage and PDCCH capacity, thereby improving user experience.
The eNodeB periodically checks the CCE allocation failure rate and number of
uplink-synchronized UEs. Based on trigger/rollback conditions and rule activation
status, the eNodeB performs the following operations on PDCCH capacity
parameters:
● If trigger conditions are met and parameter adjustment rules are activated,
the eNodeB adjusts PDCCH capacity parameters. Table 7-15 through Table
7-17 list the parameter values after adjustment. Parameter adjustment can
decrease the CCE allocation failure rate and increase downlink user-perceived
data rates.
● If trigger conditions are met but parameter adjustment rules are deactivated,
the eNodeB does not adjust PDCCH capacity parameters.
● If rollback conditions are met and parameter rollback rules are activated, the
eNodeB restores the parameters to the values before the adjustment.
● If rollback conditions are met but parameter rollback rules are deactivated,
the eNodeB does not restore the parameters.

eRAN
Table 7-15 CCE aggregation level optimization

Parameter Post- Trigger Rollback Parameter Parameter
Adjustmen Condition Condition Adjustmen Rollback
t t Rule ID Rule ID
Parameter (LIOptRul (LIOptRul
Value e.RuleID) e.RuleID)
CellPdcch STRATEGY CCE CU < 201 202

Algo.PDCC BASEDONC allocation BigEventC
HAggLvlA APACITY failure rate U–
daptStrag > 30%, and BigEventOf
e CU > fset
BigEventC
U
CellPdcch ON CCE CU < 201 202

Algo.Pdcch allocation BigEventC
CapacityI failure rate U–
mproveSw > 30%, and BigEventOf
itch CU > fset
BigEventC
U
CellPdcch ON_ALL CCE CU < 201 202

PowerEnh failure rate U–
ancedSwit > 30%, and BigEventOf
ch CU > fset
BigEventC
U
CellPdcch 280 CCE CU < 201 202

PwrCtrlUs failure rate U–
erNumThd > 30%, and BigEventOf
CU > fset
BigEventC
U

eRAN
Table 7-16 CCE resource scheduling optimization

t t Rule ID Rule ID
CellPdcch 10_1 CCE CU < 201 202

Algo.CceM allocation BigEventC
axInitialRa failure rate U–
tio > 30%, and BigEventOf
CU > fset
BigEventC
U
LOW_AGG Selected CCE CU < 201 202

_PREFERE allocation BigEventC
NTIAL_SC failure rate U–
H_SW and > 30%, and BigEventOf
SF_3_8_HA CU > fset
RQ_SELEC BigEventC
TIVE_SCH_ U
SW options
of the
CellPdcch
Algo.Pdcch
Optimizati
onSwitch
parameter

BlerTarget failure rate U–
> 30%, and BigEventOf
CU > fset
BigEventC
U

OutLoopA failure rate U–
djBaseStep > 30%, and BigEventOf
CU > fset
BigEventC
U

Algo.Nack allocation BigEventC
DtxRatioT failure rate U–
hd > 50%, and BigEventOf
CU > fset
BigEventC
U

eRAN

t t Rule ID Rule ID
CellDlschA ADAPTIVE CCE CU < 201 202

lgo.RbgAll allocation BigEventC
ocStrategy failure rate U–
CU > fset
BigEventC
U
AbnUeSch Selected CCE CU < 203 204

Switch allocation BigEventC
option of failure rate U–
the > 50%, and BigEventOf
CellAlgoS CU > fset
witch.Cell BigEventC
SchStrateg U
ySwitch
parameter
CellUlschA 11 CCE CU < 203 204

lgo.UlSchA allocation BigEventC
bnUeThd failure rate U–
CU > fset
BigEventC
U
NonGbrBu Selected CCE CU < 203 204

ndlingSwit allocation BigEventC
ch option failure rate U–
of the > 50%, and BigEventOf
CellAlgoS CU > fset
witch.DlSc BigEventC
hSwitch U
parameter
BIG_EVEN Selected CCE CU < 203 204

T_NON_GB allocation BigEventC
R_BUNDLI failure rate U–
NG_SW > 50%, and BigEventOf
option of CU > fset
the BigEventC
CellMMAl U
go.MmPar
amIntelSel
ectSw
parameter

eRAN
Table 7-17 Signaling overhead reduction

t t Rule ID Rule ID
InterFreqH N + 6, CCE CU < 205 206

oGroup.A3 where N is allocation BigEventC
InterFreqH the value failure rate U–
oA1ThdRsr before the > 50%, and BigEventOf
p adjustment CU > fset
. BigEventC
U
InterFreqH N + 6, CCE CU < 205 206

oGroup.Int where N is allocation BigEventC
erFreqHoA the value failure rate U–
1ThdRsrp before the > 50%, and BigEventOf
adjustment CU > fset
. BigEventC
U
7.13.2.2 Uplink Interference Optimization

The eNodeB periodically checks PUSCH interference, PUCCH interference, uplink
PRB usage, and number of uplink-synchronized UEs. Based on trigger/rollback
conditions and rule activation status, the eNodeB performs the following
operations on uplink interference parameters:
the eNodeB adjusts uplink interference parameters. Table 7-18 through Table
7-20 list the parameter values after adjustment. Parameter adjustment can
decrease uplink interference and increase uplink user-perceived data rates.
the eNodeB does not adjust uplink interference parameters.

eRAN
Table 7-18 Parameter adjustment for uplink interference optimization (related to

PUCCH interference)
ID Adjustmen Condition Condition Adjustmen Rollback
t t Rule ID Rule ID
CellUlpcCo -115 PUCCH CU < 261 262

mm.P0No interferenc BigEventC
minalPUC e > –105 U–
CH dBm, and BigEventOf
CU > fset
BigEventC
U
CellPcAlgo USE_P0NO PUCCH CU < 261 262

.PucchClos MINALPUC interferenc BigEventC
eLoopPcTy CH e > –105 U–
pe dBm, and BigEventOf
CU > fset
BigEventC
U
CellPcAlgo 10 PUCCH CU < 261 262

.PucchPcT interferenc BigEventC
argetSinrOf e > –105 U–
fset dBm, and BigEventOf
CU > fset
BigEventC
U

PUSCH interference)
t t Rule ID Rule ID
CellUlpcCo -100 PUSCH CU < 263 264

mm.P0No interferenc BigEventC
minalPUSC e > –105 U–
H dBm, and BigEventOf
CU > fset
BigEventC
U

eRAN

t t Rule ID Rule ID
CellPcAlgo -96 PUSCH CU < 263 264

.PuschRsrp interferenc BigEventC
HighThd e > –105 U–
dBm, and BigEventOf
CU > fset
BigEventC
U
PuschRsrp Selected PUSCH CU < 263 264

HighThdS interferenc BigEventC
witch e > –105 U–
option of dBm, and BigEventOf
the CU > fset
CellAlgoS BigEventC
witch.UlPc U
AlgoSwitc
h
parameter
SpecUePU Deselected PUSCH CU < 263 264

SCHPcOpt interferenc BigEventC
Switch e > –105 U–
the CU > fset
CellAlgoS BigEventC
witch.UlPc U
AlgoSwitc
h
parameter
NearBigPa Deselected PUSCH CU < 263 264

cketUeFast interferenc BigEventC
PcSwitch e > –105 U–
the CU > fset
CellAlgoS BigEventC
witch.UlPc U
AlgoSwitc
h
parameter
CellUlpcCo AL1 PUSCH CU < 263 264

mm.PassL interferenc BigEventC
ossCoeff e > –105 U–
dBm, and BigEventOf
CU > fset
BigEventC
U

eRAN

t t Rule ID Rule ID
PreAllocati Deselected PUSCH CU < 263 264

onSwitch interferenc BigEventC
option of e > –105 U–
the dBm, and BigEventOf
CellAlgoS CU > fset
witch.UlSc BigEventC
hSwitch U
parameter
SmartPrea Deselected PUSCH CU < 263 264

llocationS interferenc BigEventC
witch e > –105 U–
the CU > fset
CellAlgoS BigEventC
witch.UlSc U
hSwitch
parameter
Scheduler Deselected PUSCH CU < 263 264

CtrlPower interferenc BigEventC
Switch e > –105 U–
the CU > fset
CellAlgoS BigEventC
witch.UlSc U
hSwitch
parameter

uplink PRBs)
t t Rule ID Rule ID
CaMgtCfg. 0 Uplink PRB CU < 265 266

CellMaxPc usage > BigEventC
cNumber 80%, and U–
CU > BigEventOf
BigEventC fset
U

eRAN

t t Rule ID Rule ID
UlSigSrSch Selected Uplink PRB CU < 265 266

DateLenA usage > BigEventC
dapt 80%, and U–
option of CU > BigEventOf
the BigEventC fset
CellAlgoS U
witch.UlSc
hExtSwitc
h
parameter
FreqSelSwi Deselected Uplink PRB CU < 265 266

tch option usage > BigEventC
of the 80%, and U–
CellAlgoS CU > BigEventOf
witch.DlSc BigEventC fset
hSwitch U
parameter
7.13.2.3 Adaptive Overload Optimization

In big event scenarios, the average downlink UE throughput in a cell tends to drop
to 0 when the cell is overloaded. Parameters related to overload protection can be
adjusted to reduce the cell signaling overhead and decrease the access success
rate of cell edge UEs, thereby improving the cell resource usage and average user
experience.
The eNodeB periodically checks the overload threshold represented by the number
of UEs. Based on trigger/rollback conditions and rule activation status, the eNodeB
performs the following operations on overload protection parameters:
the eNodeB adjusts overload protection parameters. Table 7-21 lists the
parameter values after adjustment. Parameter adjustment can reduce the
number of CEUs allowed to access the cell and improve online user
experience in overload scenarios.
the eNodeB does not adjust overload protection parameters.

eRAN
Table 7-21 Parameter adjustment for adaptive overload optimization

t t Rule ID Rule ID
CellBfMim NO_ADAPT CU>BigEve CU<BigEve 321 322

oParaCfg.B IVE ntCU ntCU –
fMimoAda BigEventOf
ptiveSwitc fset
h
CellBfMim TM7 CU>BigEve CU<BigEve 321 322
oParaCfg.F ntCU ntCU –
ixedBfMim BigEventOf
oMode fset
CellDrxPar OFF CU>BigEve CU<BigEve 321 322

a.DrxAlgS ntCU ntCU –
witch BigEventOf
fset
CellSel.QR N + 4 dBm, Number of Number of 383 384

xLevMin where N is UEs in an UEs in an
the value equivalent equivalent
before the bandwidth bandwidth
adjustment > 600 < 600 – 2 x
BigEventOf
fset
CellResel. N + 4 dBm, Number of Number of 383 384

QRxLevMi where N is UEs in an UEs in an
n the value equivalent equivalent
adjustment > 600 < 600 – 2 x
BigEventOf
fset
7.13.2.4 MLB Parameter Optimization

In big event scenarios, MLB-related parameters can be adjusted to improve MLB
performance.
The eNodeB periodically checks the number of uplink-synchronized UEs. Based on

trigger/rollback conditions and rule activation status, the eNodeB performs the
following operations on MLB parameters:
the eNodeB adjusts MLB parameters. Table 7-22 lists the parameter values
after adjustment. Adjusted parameters together with MLB thresholds can
improve MLB performance.

eRAN
the eNodeB does not adjust MLB parameters.
Table 7-22 Parameter adjustment for MLB optimization

t t Rule ID Rule ID
CellMLB.U 10 CU > CU < 381 382

eNumDiff BigEventC BigEventC
Thd U U–
BigEventOf
fset
CellMLB.Id 10 CU > CU < 381 382

leMlbUeN BigEventC BigEventC
umDiffThd U U–
BigEventOf
fset
7.13.2.5 RS Adaptation
In heavy load scenarios, if a cell absorbs too many UEs, user experience will
deteriorate. RS-related parameters can be adjusted to reduce the cell coverage and
limit the number of UEs in the cell to ensure online user experience.
The eNodeB periodically checks the number of UEs in an equivalent bandwidth.
Based on trigger/rollback conditions and rule activation status, the eNodeB
performs the following operations on RS-related parameters:
the eNodeB adjusts RS parameters. Table 7-23 lists the parameter values
after adjustment.
the eNodeB does not adjust RS parameters.

eRAN
Table 7-23 Parameter adjustment for RS adaptation

t t Rule ID Rule ID
PDSCHCfg. N – 3, Number of Number of 441 442

Reference where N is UEs in an UEs in an
SignalPwr the value equivalent equivalent
adjustment > 700 < 700 – 6 x
. BigEventOf
fset
PDSCHCfg. 0 Number of Number of 441 442

Pb UEs in an UEs in an
equivalent equivalent
bandwidth bandwidth
> 700 < 700 – 6 x
BigEventOf
fset
CellDlpcPd DB0_P_A Number of Number of 441 442

schPa.PaPc UEs in an UEs in an
Off equivalent equivalent
bandwidth bandwidth
> 700 < 700 – 6 x
BigEventOf
fset
CellDlpcPh 30 Number of Number of 441 442

ich.PwrOff UEs in an UEs in an
set equivalent equivalent
bandwidth bandwidth
> 700 < 700 – 6 x
BigEventOf
fset
CellDlpcPd 0 Number of Number of 441 442

cch.DediDc UEs in an UEs in an
iPwrOffset equivalent equivalent
bandwidth bandwidth
> 700 < 700 – 6 x
BigEventOf
fset
CellChPwr 0 Number of Number of 441 442

Cfg.PbchP UEs in an UEs in an
wr equivalent equivalent
bandwidth bandwidth
> 700 < 700 – 6 x
BigEventOf
fset

eRAN

t t Rule ID Rule ID

Cfg.DbchP UEs in an UEs in an
wr equivalent equivalent
bandwidth bandwidth
> 700 < 700 – 6 x
BigEventOf
fset

Cfg.Pcfich UEs in an UEs in an
Pwr equivalent equivalent
bandwidth bandwidth
> 700 < 700 – 6 x
BigEventOf
fset

Cfg.RaRsp UEs in an UEs in an
Pwr equivalent equivalent
bandwidth bandwidth
> 700 < 700 – 6 x
BigEventOf
fset

Cfg.PchPw UEs in an UEs in an
r equivalent equivalent
bandwidth bandwidth
> 700 < 700 – 6 x
BigEventOf
fset

Cfg.SchPw UEs in an UEs in an
r equivalent equivalent
bandwidth bandwidth
> 700 < 700 – 6 x
BigEventOf
fset

Cfg.PrsPwr UEs in an UEs in an
equivalent equivalent
bandwidth bandwidth
> 700 < 700 – 6 x
BigEventOf
fset

eRAN
7.13.3.1 Benefits
In heavy-load scenarios, this feature improves the average downlink UE
throughput, average downlink cell throughput, and average downlink cell spectral
efficiency.

7.13.3.2 Impacts
NOTE
Intelligent parameter selection has no network impacts or function impacts. However, some
functions are enabled after parameter adjustment. For details about the impacts of these
functions, see the corresponding feature parameter descriptions. For example, the function
of selective HARQ scheduling in subframes 3 and 8 is enabled after the
CellPdcchAlgo.PdcchOptimizationSwitch parameter is adjusted for PDCCH capacity
enhancement. For details about the network impacts of this function, see Network
Impacts.
Network Impacts
In automatic guarantee scenarios, intelligent parameter selection has the
following network impacts:
● PDCCH capacity enhancement: Some parameters increase PDCCH capacity by

means of scheduling.
● Uplink interference optimization: There are gains in contiguous networking
scenarios. There are only low gains or even no gain in non-contiguous
networking scenarios.
● Adaptive overload optimization: The signal strength of UEs admitted to the
cell increases, but the access of some CEUs may be affected.
● MLB parameter optimization: The difference in the number of UEs between
carriers decreases, but there will be more signaling interactions and
handovers.
● RS adaptation: RS power is reduced, cell coverage is shrunk, and the service
drop rate may increase during power adjustment.
Function Impacts
None
7.13.4 Requirements

eRAN
7.13.4.1 Licenses
TDLEOFD-151616 Intelligent LT4SMMPISTDD Per Cell

Selection of
Massive MIMO
Parameters
7.13.4.2 Software
Massive MIMO Cell.TxRxMode 4 Basic Massive Intelligent

introduction set to 32T32R or MIMO Functions parameter
64T64R selection takes
effect only in
massive MIMO
cells.
Downlink non- NonGbrBundling Scheduling None

GBR packet Switch option of
bundling the
CellAlgoSwitch.D
lSchSwitch
parameter

None
7.13.4.3 Hardware

Table 7-24 and Table 7-25 describe the parameters used for function activation
and optimization, respectively.

eRAN

Massive MIMO Param CellMMAlgo.MmParamI Select the

Intelligent Selection Sw ntelSelectSw BIG_EVENT_THLD_LEAR
N_SW and
BIG_EVENT_AUTO_ASS
URANCE_SW options.
Table 7-25 Parameter used for optimization

Rule ID LIOptRule.RuleID Rule IDs are related to

parameters to be
adjusted. For details
about the mapping
between them, see
parameter adjustment
tables in 7.13.2
Automatic Assurance
Scenarios.
Rule ID LIOptRuleMember.RuleI Set this parameter to the

D same value as the
LIOptRule.RuleID
parameter.
Atom Rule ID LIOptRuleMember.Ato Set this parameter when

mRuleID an atom rule needs to be
deactivated. For the
mapping between atom
rules and atom rule IDs,
see Table 7-13.
Active Status LIOptRuleMember.Activ Set this parameter to

eStatus DEACTIVATED when an
atom rule needs to be
deactivated.
MM Param Intel CellMMAlgo.MmParamI Retain the default value.

Selection DL User Exp ntelSelectDlUxThld
Thld
MM Param Intel CellMMAlgo.MmParamI Retain the default value.

Selection UL User Exp ntelSelectUlUxThld
Thld

eRAN

//Enabling big event threshold learning
MOD CELLMMALGO: LocalCellId=0, MmParamIntelSelectSw=BIG_EVENT_THLD_LEARN_SW-1,
MmParamIntelSelectUlUxThld=1024, MmParamIntelSelectDlUxThld=5120;
//Enabling automatic assurance for big events
MOD CELLMMALGO: LocalCellId=0, MmParamIntelSelectSw=BIG_EVENT_AUTO_ASSURANCE_SW-1;
Optimization Command Examples

Set threshold parameters, for example, to their default values.
//Adjusting the downlink and uplink user experience thresholds for intelligent selection of massive MIMO
parameters
MOD CELLMMALGO: LocalCellId=0, MmParamIntelSelectUlUxThld=1024,
MmParamIntelSelectDlUxThld=5120;
Table 7-26 describes the mapping between rule IDs and default activation status
in each application scenario of automatic assurance for massive MIMO big events.
If a rule is deactivated by default, it can take effect only after being activated. For
example, rules 441 and 442 for RS adaptation are deactivated by default, and
parameters can be adjusted and restored only after the rules are activated.
Table 7-26 Default activation status
Scenario Rule ID Default Activation

(LIOptRule.RuleID) Status
PDCCH capacity 201/202/203/204/205/20 Activated

enhancement 6
Uplink interference 261/262/263/264/265/26 Deactivated

optimization 6
MLB parameter 321/322 Deactivated

optimization
Adaptive overload 381/382/383/384 Deactivated

optimization
RS adaptation 441/442 Deactivated
After this feature is enabled, you can activate, deactivate, and modify optimization
rules for each automatic assurance scenario.
//Activating a rule, for example, rule 201
LST LIOPTRULE: RuleID=201;
ACT LIOPTRULE: RuleID=201;
//Deactivating a rule, for example, rule 201
DEA LIOPTRULE: RuleID=201;
//Deactivating an atom rule, for example, atom rule 101
LST LIOPTRULEMEMBER: AtomRuleID=101, RuleID=201;
MOD LIOPTRULEMEMBER: RuleID=201, AtomRuleID=101, ActiveStatus=DEACTIVATED;

eRAN

//Disabling big event threshold learning and automatic assurance for big events
MOD CELLMMALGO: LocalCellId=0,
MmParamIntelSelectSw=BIG_EVENT_THLD_LEARN_SW-0&BIG_EVENT_AUTO_ASSURANCE_SW-0;

Maintenance.

Step 1 Run the LST CELLMMALGO command to query the Massive MIMO Param
Intelligent Selection Sw parameter.
● If BIG_EVENT_AUTO_ASSURANCE_SW is set to On, automatic assurance for
massive MIMO big events has been enabled. If the switch is Off, this function
is disabled.
● If BIG_EVENT_THLD_LEARN_SW is set to On, big event threshold learning for
intelligent parameter selection has been enabled; the threshold obtained
based on learning will be used in trigger conditions. If the switch is Off, this
function is disabled.
Step 2 Check whether rules for intelligent parameter selection have taken effect.
● Method 1: Run the DSP LIOPTRULE command. If the Executive Status
parameter value of a rule for intelligent parameter selection is EXECUTED,
this rule has taken effect.
● Method 2: On the MAE-Access, query SON logs, with Log Category set to LTE
Automatic Congestion Handler Log. Check whether the function takes effect
based on the log.
Step 3 Check whether UE count threshold learning has been completed for intelligent
parameter selection.
Run the DSP MMBIGEVENTLEARNTHLD command. If the Massive MIMO Big
Event UE Count Learning Thld parameter value is a valid value, UE count
threshold learning has been completed.
----End


eRAN

7.14 Massive MIMO MU Beamforming Power

Enhancement (Trial)
Trial functions are functions 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 functions can still be used for testing
purposes or commercial network trials. Anyone who desires to use the trial
functions shall contact Huawei and enter into a memorandum of understanding
(MoU) with Huawei prior to an official application of such trial functions. Trial
functions are not for sale in the current version but customers may try them for
free.
Customers acknowledge and undertake that trial functions may have a certain
degree of risk due to absence of commercial testing. Before using them, customers
shall fully understand not only the expected benefits of such trial functions but
also the possible impact they may exert on the network. In addition, customers
acknowledge and undertake that since trial functions are free, Huawei is not liable
for any trial function malfunctions or any losses incurred by using the trial
functions. Huawei does not promise that problems with trial functions will be
resolved in the current version. Huawei reserves the rights to convert trial
functions into commercial functions in later R/C versions. If trial functions are
converted into commercial functions in a later version, customers shall pay a
licensing fee to obtain the relevant licenses prior to using the said commercial
functions. If a customer fails to purchase such a license, the trial function(s) will
be invalidated automatically when the product is upgraded.
7.14.1 Principles
During downlink pairing for massive MIMO MU beamforming, power
normalization is used to ensure orthogonality between paired UEs. As a result, the
downlink transmit power of some antennas is limited. To address this issue, the
massive MIMO MU beamforming power enhancement function is introduced to
improve power usage while ensuring orthogonality between paired UEs, thereby
improving the downlink performance of massive MIMO.
This function generates orthogonal weights for downlink data streams based on
the zero forcing principle, calculates the power of antennas for paired UEs, and
adaptively increases the power of some weak antennas, reducing the power
difference between antennas.
This function is controlled by the MUBF_PWR_ENH_SW option of the
CellMMAlgo.PreciseMubfOptSwitch parameter.
7.14.2.1 Benefits
This function increases the average downlink cell spectral efficiency if UEs are
evenly distributed in the cell and the proportion of RBs that can be paired for

eRAN
massive MIMO MU beamforming is greater than 50%. If the preceding conditions

are not met, the gains provided by this function are not obvious.
7.14.2.2 Impacts
Network Impacts
This function increases the average downlink cell spectral efficiency.

Function Impacts
None
7.14.3 Requirements
7.14.3.1 Licenses
There are no license requirements for trial functions.
7.14.3.2 Software
Massive MIMO 64T64R value of 4 Basic Massive Massive MIMO

introduction the MIMO Functions MU beamforming
Cell.TxRxMode power
parameter enhancement
takes effect only
in massive MIMO
cells.
Downlink 8-layer MuBfSwitch 6.2 MU Massive MIMO

MU beamforming, option of the Beamforming MU beamforming
downlink 16-layer CellAlgoSwitch. power
MU beamforming, MuBfAlgoSwitch enhancement
or downlink 24- parameter requires any of
layer MU the three features.
beamforming
(trial)

eRAN

MUBF Power CellBf.MubfPowe 6.2 MU When massive

Normalization rNormAdptFacto Beamforming MIMO MU
Adaptive Factor r beamforming
power
enhancement is
enabled, the
CellBf.MubfPowe
rNormAdptFacto
r parameter is
fixedly set to 0. In
this case, PEBF
power
normalization is
used for MU
beamforming.
Moving UE MU CellBf.MovingUe None When massive

beamforming MuBfScheme MIMO MU
scheme beamforming
power
enhancement is
enabled, the
CellBf.MovingUe
MuBfScheme
parameter cannot
be set to
HEAVY_LOAD_SC
HEME,
LIGHT_LOAD_SC
HEME, or
SPLIT_SDMA_SC
HEME.
7.14.3.3 Hardware
For details, see 4.3.3 Hardware. The UBBPem does not support this function.
RF modules must be 64T64R AAUs.


eRAN

Precise MUBF CellMMAlgo.PreciseMu Select the

Optimization Switch bfOptSwitch MUBF_PWR_ENH_SW
option.

//Enabling massive MIMO MU beamforming power enhancement
MOD CELLMMALGO: LocalCellId=100, PreciseMubfOptSwitch=MUBF_PWR_ENH_SW-1;

//Deactivating massive MIMO MU beamforming power enhancement
MOD CELLMMALGO: LocalCellId=100, PreciseMubfOptSwitch=MUBF_PWR_ENH_SW-0;


Step 1 Run the LST CELLMMALGO command. If the Precise MUBF Optimization Switch
parameter has a value of MUBF_PWR_ENH_SW:On, massive MIMO MU
beamforming power enhancement has been enabled. Otherwise, the function is
disabled.
----End

After this function is enabled, monitor the average downlink cell spectral efficiency
improvement using counters.
7.15 SRS-Expansion-based Precise Beamforming

This section describes the feature TDLEOFD-161601 Precise Beamforming with SRS
Expansion.
7.15.1 Principles
If UEs are moving or channels are changing, beamforming weights estimated
based on SRS may not well match the actual downlink channel information. As a
result, MU beamforming performance deteriorates.
This feature expands SRS resources in a cell, increasing the number of SRS symbols
in a 5 ms half-frame from two to three and the number of code division

eRAN
multiplexing (CDM) UEs from four to six, as shown in Figure 7-13. Assuming that
the number of UEs remains unchanged, this feature shortens the average SRS
period, improves the channel estimation timeliness, and therefore enhances the
performance of MU beamforming on time-varying channels.
Figure 7-13 Cell SRS resource expansion
This feature is controlled by the SRSCfg.SrsResExpansionSwitch parameter. When

this parameter is set to SRS_RES_EXPANSION_MODE, this feature is enabled. It is
recommended that this feature be enabled in cells where the proportion of UEs
moving at low speed (3 km/h to 5 km/h) is high and the uplink load is not heavy.
7.15.2.1 Benefits
This feature increases the User Downlink Average Throughput when the
downlink load is medium or heavy and the proportion of low-speed UEs (moving
at 3 km/h to 5 km/h) is high.
7.15.2.2 Impacts
Network Impacts
● After this feature is enabled, the last symbols in uplink subframes are used for
SRS transmission. As a result, the average uplink cell throughput and average
uplink MCS index decrease, the uplink IBLER may slightly decrease, and the
number of PUSCH PRBs increases.
– Average uplink cell throughput = Cell Uplink Average Throughput
– Average uplink MCS index = (L.ChMeas.PUSCH.MCS.0 x 0 +
L.ChMeas.PUSCH.MCS.1 x 1 + ... + L.ChMeas.PUSCH.MCS.27 x 27 +
L.ChMeas.PUSCH.MCS.28 x 28) / (L.ChMeas.PUSCH.MCS.0 +
L.ChMeas.PUSCH.MCS.1 + ... + L.ChMeas.PUSCH.MCS.27 +
L.ChMeas.PUSCH.MCS.28)
– Uplink IBLER = (L.CA.PCell.Traffic.UL.SCH.QPSK.ErrTB.Ibler +
L.CA.PCell.Traffic.UL.SCH.16QAM.ErrTB.Ibler +
L.CA.PCell.Traffic.UL.SCH.64QAM.ErrTB.Ibler) /
(L.CA.PCell.Traffic.UL.SCH.QPSK.TB + L.CA.PCell.Traffic.UL.SCH.
16QAM.TB + L.CA.PCell.Traffic.UL.SCH.64QAM.TB) x 100%

eRAN
– Number of PUSCH PRBs = L.ChMeas.PRB.PUSCH.Avg

● After this feature is enabled, PUCCH resources in uplink subframes are limited,
which has the following impacts:
– SRI/HARQ feedback is sent in a shortened format, and the performance
of CEUs may deteriorate.
– When there are a large number of UEs, the CQI reporting period is
prolonged, the downlink gain decreases, the uplink UE scheduling delay
increases, and the PUCCH PRB usage and uplink PRB usage of the cell
decrease.
▪ PUCCH PRB usage = L.ChMeas.PRB.PUCCH.Avg /

▪ Uplink PRB usage of the cell = L.ChMeas.PRB.UL.Used.Avg /

● After this feature is enabled, the number of SRS CDM UEs increases, the
UpPTS interference may increase, and the average SRS SINR may decrease.
Therefore, when the proportion of moving UEs is less than 10%, this feature
may change the downlink IBLER, average number of downlink paired layers,
and average downlink MCS index, and may decrease the average downlink UE
throughput and average downlink cell throughput.
– UpPTS interference = L.UpPTS.Interference.Avg
– Average SRS SINR = [L.UL.SINR.SRS.Index0 x (–8) +
L.UL.SINR.SRS.Index1 x (–6) + L.UL.SINR.SRS.Index2 x (–2) +
L.UL.SINR.SRS.Index3 x 2.5 + L.UL.SINR.SRS.Index4 x 5] /
(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)
– Downlink IBLER = (L.Traffic.DL.SCH.QPSK.ErrTB.Ibler +
L.Traffic.DL.SCH.16QAM.ErrTB.Ibler + L.Traffic.DL.SCH.
64QAM.ErrTB.Ibler) / (L.Traffic.DL.SCH.QPSK.TB + L.Traffic.DL.SCH.
16QAM.TB + L.Traffic.DL.SCH.64QAM.TB) x 100%
– Average number of downlink paired layers =
(L.ChMeas.PRB.DL.Used.Avg + L.ChMeas.MUBF.2ndLayer.PairPRB.Succ
+ L.ChMeas.MUBF.3rdLayer.PairPRB.Succ + ... + L.ChMeas.MUBF.
15thLayer.PairPRB.Succ + L.ChMeas.MUBF.16thLayer.PairPRB.Succ) /
L.ChMeas.PRB.DL.Used.Avg
– Average downlink MCS index = (L.ChMeas.PDSCH.MCS.0 x 0 +
L.ChMeas.PDSCH.MCS.1 x 1 + ... + L.ChMeas.PDSCH.MCS.27 x 27 +
L.ChMeas.PDSCH.MCS.28 x 28) / (L.ChMeas.PDSCH.MCS.0 +
L.ChMeas.PDSCH.MCS.1 + L.ChMeas.PDSCH.MCS.2 + ... +
L.ChMeas.PDSCH.MCS.27 + L.ChMeas.PDSCH.MCS.28)
– Average downlink UE throughput = User Downlink Average Throughput
– Average downlink cell throughput = Cell Downlink Average Throughput
● After this feature is enabled, the average SRS period of UEs decreases and the
average number of UEs in DRX mode (indicated by the
L.Traffic.User.Cdrx.Avg counter) may increase.
● When this feature is enabled, it is recommended that the
CellPcAlgo.SrsPcSinrTarget parameter be set to a value not greater than 10
dB for special subframes.

eRAN
The CellPcAlgo.SrsPcSinrTargetForUlSf parameter is set based on uplink

subframe interference.
● When this feature is enabled and antenna selection takes effect, the SRS
period of UEs increases and the Cell Downlink Average Throughput may
decrease if there is a large proportion of antenna selection UEs. Therefore, it
is recommended that fake antenna selection UE identification be enabled in
this scenario.
– To make antenna selection take effect, deselect the
UeSRSAntSelectCtrlSwitch option of the
ENodeBAlgoSwitch.CompatibilityCtrlSwitch parameter.
– To enable fake antenna selection UE identification, select the
FakeAntSelIdentificationSwitch option of the
CellAlgoSwitch.BfAlgoSwitch parameter.
Function Impacts
Dynamic PUCCH PucchSwitch Physical Channel When SRS-

resource option of the Resource expansion-based
adjustment CellAlgoSwitch.P Management precise
ucchAlgoSwitch beamforming is
parameter enabled, it is
recommended
that the
PucchSwitch
option be selected
to ensure SRS
performance.
SRS resource SRSCfg.SrsInterf 7.4 SRS If both SRS-

allocation AvoidOptSwitch Interference expansion-based
optimization for Joint Suppression precise
interference beamforming and
avoidance SRS resource
allocation
optimization for
interference
avoidance are
enabled, the
average SRS
perioda may be
prolonged.

eRAN
Uplink 2CC CaUl2CCSwitch Carrier In CA scenarios, if

aggregation option of the Aggregation this feature is not
CaMgtCfg.CellCa enabled or
AlgoSwitch disabled in all the
parameter PCell and SCells,
the uplink CA
success rate may
decrease and
there may be a
higher probability
that UEs in the
SCells do not have
SRS resources.
Note a: Average SRS period = (L.Traffic.User.2msSRS.Avg x 2 + L.Traffic.User.

7.15.3 Requirements
7.15.3.1 Licenses
TDLEOFD-161601 Precise LT4SMMSRSRE0 Per Cell

Beamforming
with SRS
Expansion
7.15.3.2 Software

eRAN
Massive MIMO Cell.TxRxMode 4 Basic Massive SRS-expansion-

introduction set to 32T32R or MIMO Functions based precise
64T64R. beamforming
takes effect only
in massive MIMO
cells.
SRS resource SRSCfg.SrsCfgInd Physical Channel SRS-expansion-

management Resource based precise
Management beamforming
requires SRS
resource
management.
SRI/HARQ BOOLEAN_TRUE None SRS-expansion-

feedback in a value of the based precise
shortened format SRSCfg.AnSrsSim beamforming
uTrans parameter requires SRI/
HARQ feedback in
a shortened
format.
Long-delay- LARGE_DELAY_SP None SRS-expansion-

spread UE READ_UE_IDENT_ based precise
identification SW option of the beamforming
CellBf.UeIdentific requires long-
ationSwitch delay-spread UE
parameter identification.
Mute UpPTS CellRicAlgo.Mute None SRS-expansion-

Symbol Number UpPTSSymNum based precise
beamforming
requires that this
parameter be set
to 0.

Multi-user split SplitSdmaSwitch 6.5 Multi-User SRS-expansion-

SDMA option of the Split SDMA based precise
CellAlgoSwitch. beamforming is
MuBfAlgoSwitch not compatible
parameter with multi-user
split SDMA.

eRAN
SRS interference WTTxSRSIntrfAv Massive MIMO SRS-expansion-

avoidance oidanceSw option Optimization in based precise
of the WTTx Scenarios beamforming is
SRSCfg.SrsCfgPol (TDD) not compatible
icySwitch with SRS
parameter interference
avoidance.
Flexible PUCCH PucchFlexCfgSwi Physical Channel SRS-expansion-

configuration tch option of the Resource based precise
CellAlgoSwitch.P Management beamforming is
ucchAlgoSwitch not compatible
parameter with flexible
PUCCH
configuration.
Rank 3 or 4 in FOUR_LAYER_BF 6.3 TM9 SRS-expansion-

open-loop TM9 value of the based precise
CellBf.MaxBfRan beamforming is
kPara parameter not compatible
with rank 3 or 4
in open-loop TM9.
7.15.3.3 Hardware
For details, see 4.3.3 Hardware. The UBBPem does not support this feature.


SRS Resource Expansion SRSCfg.SrsResExpansion Set this parameter to

Switch Switch SRS_RES_EXPANSION_M
ODE.

eRAN
NOTICE
Changing the value of the SRSCfg.SrsResExpansionSwitch parameter will cause

the cell to be reset automatically.

//Enabling SRS-expansion-based precise beamforming
MOD SRSCFG: LocalCellId=0, SrsResExpansionSwitch=SRS_RES_EXPANSION_MODE;

//Deactivating SRS-expansion-based precise beamforming
MOD SRSCFG: LocalCellId=0, SrsResExpansionSwitch=OFF;

Maintenance.

Step 1 Run the LST CELL command and query the value of Cell active state. If the value
is Active, go to Step 2.
Step 2 Run the LST SRSCFG command and query the value of SRS Resource Expansion
Switch.
● If the value is SRS_RES_EXPANSION_MODE, SRS-expansion-based precise
beamforming has taken effect.
● If the value is OFF, this feature does not take effect.
----End

This feature increases the User Downlink Average Throughput when the
downlink load is medium or heavy and the proportion of low-speed UEs (moving
at 3 km/h to 5 km/h) is high.
The average SRS period can be shortened after this feature is enabled, on the
assumption that the number of UEs remains unchanged. The monitoring item is
as follows:

eRAN
Average SRS period = (L.Traffic.User.2msSRS.Avg x 2 + L.Traffic.User.


eRAN
Description 8 Parameters
8 Parameters
The following hyperlinked EXCEL files of parameter documents match the

software version with which this document is released.
● Node Parameter Reference: contains device and transport parameters.

● eNodeBFunction Parameter Reference: contains all parameters related to
radio access functions, including air interface management, access control,
mobility control, and radio resource management.
● eNodeBFunction Used Reserved Parameter List: contains the reserved
parameters that are in use and those that have been disused.
NOTE
You can find the EXCEL files of parameter reference and used reserved parameter list for
the software version used on the live network from the product documentation delivered
with that version.
FAQ 1: 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
FAQ 2: How do I find the information about a certain reserved parameter

from the used reserved parameter list?
Step 1 Open the EXCEL file of the used reserved parameter list.
Step 2 On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT
columns to locate the reserved parameter, which may be only a bit of a parameter.
View its information, including the meaning, values, impacts, and product version
in which it is activated for use.
----End

eRAN
Description 9 Counters
9 Counters
The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● eNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.
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
Description 10 Glossary
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
Description 11 Reference Documents
11 Reference Documents
1. Beamforming (TDD)
2. Cloud BB Overview
3. CPRI Compression
4. CSPC
5. D-MIMO (TDD)
6. DL CoMP (TDD)
7. eMBMS
8. eMTC
9. eX2 Self-Management
10. LCS
11. Dynamic Power Sharing Between LTE Carriers
12. MIMO
13. MRC and IRC Receivers
14. License Management
15. Relay
16. SFN
17. Turbo Receiver
18. UL CoMP
19. VoLTE
20. WBB
21. WTTx Turbo Beamforming (TDD)
22. Massive MIMO Optimization in WTTx Scenarios (TDD)
23. Specified User Coordinated Scheduling
24. Extended Cell Range
25. Scheduling
26. Interference Detection and Suppression
27. Interference Randomizing (TDD)
28. High Speed Mobility

eRAN
Description 11 Reference Documents
29. Power Control

30. Cell Switch-off Based on Automatic Co-coverage Identification
31. Energy Conservation and Emission Reduction
32. USU3900-based Multi-BBU Interconnection
33. USU3910-based Multi-BBU Interconnection
34. Extended CP
35. Mobility Management in Connected Mode
36. Soft Split Resource Duplex (TDD)
37. Physical Channel Resource Management
38. Intra-RAT Mobility Load Balancing
39. Uplink Coordinated Scheduling
40. Channel State Management
41. Carrier Aggregation
42. Adaptive ICIC
43. Subframe Configuration (TDD)

Massive MIMO (TDD) (eRAN16.1 - 13)

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

Massive MIMO (TDD) (eRAN16.1 - 13)

Uploaded by

Copyright:

Available Formats

eRAN

Massive MIMO (TDD) Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. i

2 About This Document...........................................................................................................16

4 Basic Massive MIMO Functions..........................................................................................23

Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. ii

5 Uplink Multiple-Antenna Reception.................................................................................51

6 Downlink Multiple-Antenna Transmission..................................................................... 70

Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. iii

Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. iv

6.3.3.4 Others.............................................................................................................................................................................. 110

Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. v

6.6.1 Principles............................................................................................................................................................................ 141

Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. vi

6.8.3.2 Software.......................................................................................................................................................................... 177

7 Performance Optimization in Massive MIMO..............................................................183

Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. vii

7.3.4.1.3 Using the MAE-Deployment.................................................................................................................................195

Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. viii

7.6.3.2 Software.......................................................................................................................................................................... 214

Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. ix

7.9.1 Principles............................................................................................................................................................................ 234

Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. x

7.11.4.1 Data Configuration................................................................................................................................................... 250

Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. xi

7.13.5.2 Activation Verification............................................................................................................................................. 275

Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. xii

This chapter describes changes not included in the "Parameters", "Counters",

1.1 eRAN16.1 13 (2021-08-13)

Added descriptions of the mutually exclusive relationship between massive MIMO

1.2 eRAN16.1 12 (2021-05-07)

Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. 1

Recommended that the PCCHCfg.DefaultPagingCycle parameter be set in eCPRI

Revised descriptions in 6.1.1 Principles and 6.2.1.1 Overview.

Added a mutually exclusive relationship between correlation-based cluster pairing

Revised descriptions of the network impacts of uplink pairing optimization. For

Revised descriptions of IRC hardware requirements. For details, see 7.7.3.3

1.3 eRAN16.1 11 (2021-02-28)

Enabled the AAU5636 to None 3900 and 5900 series

Revised descriptions of the network impacts of load-based TMA optimization. For

1.4 eRAN16.1 10 (2021-01-14)

Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. 2

1.5 eRAN16.1 09 (2020-12-30)

1.6 eRAN16.1 08 (2020-12-08)

1.7 eRAN16.1 07 (2020-10-31)

Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. 3

1.8 eRAN16.1 06 (2020-09-29)

1.9 eRAN16.1 05 (2020-08-31)

Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. 4

Enabled the UBBPg3b to None 3900 and 5900 series

1.10 eRAN16.1 04 (2020-07-29)

Enabled the UBBPg3b to None 3900 and 5900 series

Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. 5

Revised the description of the principles of load-based TMA optimization. For

1.11 eRAN16.1 03 (2020-07-03)

Enabled the AAU5636w None 3900 and 5900 series

1.12 eRAN16.1 02 (2020-05-20)

Issue 13 (2021-08-13) Copyright © Huawei Technologies Co., Ltd. 6

Revised the description of data configuration for service-based dynamic SRS

Revised the description of the mutually exclusive functions of TM9 hybrid