0% found this document useful (0 votes)
984 views56 pages

Beamforming (TDD) Feature Parameter Description

Huawei TDD Beamforming Feature

Uploaded by

Mohammed Shakil
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
984 views56 pages

Beamforming (TDD) Feature Parameter Description

Huawei TDD Beamforming Feature

Uploaded by

Mohammed Shakil
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

12/15/2020 HedEx Startpage

eRAN Feature Documentation


Product Version: eRAN15.1
Library Version: 04
Date: 2019-09-05

For any question, please contact us.


Copyright © Huawei Technologies Co., Ltd. 2019. All rights reserved.

Beamforming (TDD)
Contents
[Link] Beamforming (TDD)

eRAN
Beamforming (TDD) Feature Parameter
Description
Issue 03
Date 2019-07-20

HUAWEI TECHNOLOGIES CO., LTD.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 1/56


12/15/2020 HedEx Startpage

Copyright © Huawei Technologies Co., Ltd. 2019. All rights reserved.


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

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website: [Link]

Email: support@[Link]

1.2.2 Contents
1 Change History
1.1 eRAN15.1 03 (2019-07-20)
1.2 eRAN15.1 02 (2019-06-29)
1.3 eRAN15.1 01 (2019-06-06)
1.4 eRAN15.1 Draft C (2019-03-25)
1.5 eRAN15.1 Draft B (2019-02-22)
1.6 eRAN15.1 Draft A (2019-01-05)

2 About This Document


2.1 General Statements
2.2 Applicable RAT
2.3 Features in This Document

3 Overview
3.1 Definition
3.2 Feature Overview
3.3 Application Scenarios

4 General Principles
4.1 Overall Procedure
4.2 RRU Channel Calibration
4.3 Weight Calculation
4.4 Weighting
4.5 Beamforming Implementation
4.6 Demodulation
4.7 Related Concepts
4.7.1 Antenna Patterns
4.7.2 CSI-RSs

5 SU Beamforming
5.1 Single-Stream Beamforming and Dual-Stream Beamforming
5.1.1 General Principles
5.1.2 Network Analysis
[Link] Benefits
[Link] Impacts
5.1.3 Requirements

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 2/56


12/15/2020 HedEx Startpage
[Link] Licenses
[Link] Software
[Link] Hardware
[Link] Others
5.1.4 Operation and Maintenance
[Link] Data Configuration
[Link].1 Data Preparation
[Link].2 Using MML Commands
[Link].3 Using the CME
[Link] Activation Verification
[Link] Network Monitoring
[Link] Possible Issues
5.2 TM9
5.2.1 General Principles
5.2.2 Network Analysis
[Link] Benefits
[Link] Impacts
5.2.3 Requirements
[Link] Licenses
[Link] Software
[Link] Hardware
[Link] Others
5.2.4 Operation and Maintenance
[Link] Data Configuration
[Link].1 Data Preparation
[Link].2 Using MML Commands
[Link].3 Using the CME
[Link] Activation Verification
[Link] Network Monitoring
[Link] Possible Issues

6 MU Beamforming
6.1 Principles
6.1.1 Overview
6.1.2 MU Beamforming Pairing Procedure
[Link] 2-Layer MU Beamforming and 4-Layer MU Beamforming
[Link] Adaptive MU Beamforming
6.2 Network Analysis
6.2.1 Benefits
6.2.2 Impacts
6.3 Requirements
6.3.1 Licenses
6.3.2 Software
6.3.3 Hardware
6.3.4 Others
6.4 Operation and Maintenance
6.4.1 Data Configuration
[Link] Data Preparation
[Link] Using MML Commands
[Link] Using the CME
6.4.2 Activation Verification
6.4.3 Network Monitoring

7 UE-level TMA
7.1 Adaptive Switching Between Single- and Dual-Stream Beamforming
7.2 Adaptive Switching Between Single-Stream, Dual-Stream, and MU Beamforming
7.3 Adaptive Switching Between Beamforming and MIMO
7.3.1 Principles
7.3.2 Optimization Functions
7.4 Network Analysis
7.4.1 Benefits
7.4.2 Impacts
7.5 Requirements
7.5.1 Licenses
7.5.2 Software
7.5.3 Hardware
7.5.4 Others
7.6 Operation and Maintenance
7.6.1 Data Configuration
[Link] Data Preparation

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 3/56


12/15/2020 HedEx Startpage
[Link].1 Scenario A: Adaptive Switching Between Single- or Dual-Stream Beamforming and MIMO
[Link].2 Scenario B: Adaptive Switching Between Single- or Dual-Stream Beamforming, TM9, and MIMO
[Link].3 Scenario C: MU Beamforming Enabled on the Basis of Scenario A or B
[Link].4 Scenario D: Network Reconstruction Scenario
[Link] Using MML Commands
[Link].1 Scenario A: Adaptive Switching Between Single- or Dual-Stream Beamforming and MIMO
[Link].2 Scenario B: Adaptive Switching Between Single- or Dual-Stream Beamforming, TM9, and MIMO
[Link].3 Scenario C: MU Beamforming Enabled on the Basis of Scenario A or B
[Link].4 Scenario D: Network Reconstruction Scenario
[Link] Using the CME
7.6.2 Activation Verification
7.6.3 Network Monitoring

8 Cell-level TMA
8.1 Heavy-Load TMA Boost
8.2 Network Analysis
8.2.1 Benefits
8.2.2 Impacts
8.3 Requirements
8.3.1 Licenses
8.3.2 Software
8.3.3 Hardware
8.3.4 Others
8.4 Operation and Maintenance
8.4.1 Data Configuration
[Link] Data Preparation
[Link] Using MML Commands
[Link] Using the CME
8.4.2 Activation Verification
8.4.3 Network Monitoring

9 Parameters

10 Counters

11 Glossary

12 Reference Documents

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

eRAN15.1 03 (2019-07-20)
This issue includes the following changes.

chnical Changes

None

itorial Changes

Revised descriptions of optimized switching to beamforming in heavy-load scenarios. For details, see 8.1 Heavy-Load TMA Boost.

eRAN15.1 02 (2019-06-29)
This issue includes the following changes.

chnical Changes

None

itorial Changes

Optimized the hardware requirements for adaptive MU beamforming. For details, see 6.3.3 Hardware.

eRAN15.1 01 (2019-06-06)
This issue includes the following changes.

chnical Changes

Change Description Parameter Change Base Station Model

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 4/56


12/15/2020 HedEx Startpage

Change Description Parameter Change Base Station Model

Added the number of cells supported by adaptive MU None 3900 and 5900 series base stations
beamforming on BBPs. For details, see 6.3.3 Hardware.

itorial Changes

None

eRAN15.1 Draft C (2019-03-25)


This issue includes the following changes.

chnical Changes

Change Description Parameter Change Base Station Model

Added the compatibility of UBBPg boards with None 3900 and 5900 series base stations
beamforming. For details, see the following sections:
[Link] Hardware
[Link] Hardware
6.3.3 Hardware

itorial Changes

Revised descriptions in the following sections:

[Link] Network Monitoring


[Link] Software
[Link] Activation Verification

eRAN15.1 Draft B (2019-02-22)


This issue includes the following changes.

chnical Changes

None

itorial Changes

Revised the descriptions in the following sections:

[Link] Benefits
6 MU Beamforming

eRAN15.1 Draft A (2019-01-05)


This issue introduces the following changes to LTE eRAN TDD 13.1 07 (2018-11-07).

chnical Changes

Change Description Parameter Change Base Station Model

Added optimized TMA for 4R and 8R UEs. For details, see Added the following parameter: 3900 and 5900 series base stations
the following sections: CellBfMimoParaCfg.Ue4ROr8RBfMimoAdaptOptSw
7.3.2 Optimization Functions
7.4.2 Impacts
7.6.1 Data Configuration

Added support for optimized switching to beamforming in Added the following parameter: 3900 and 5900 series base stations
heavy-load scenarios. For details, see the following [Link] DBS3900 LampSite and DBS5900
sections: LampSite
8.1 Heavy-Load TMA Boost
8.2.2 Impacts
8.4.1 Data Configuration

Added adaptive MU beamforming. For details, see the Added the following parameter: 3900 and 5900 series base stations
following sections: [Link]
[Link] Adaptive MU Beamforming
6.2 Network Analysis
6.4 Operation and Maintenance

Added support for heavy-load transmission mode None 3900 and 5900 series base stations
adaptation (TMA) boost. For details, see 8.1 Heavy-Load TMA DBS3900 LampSite and DBS5900
Boost.
LampSite

Added fake antenna selection UE identification. For details, Modified parameters: 3900 and 5900 series base stations
see 5.1 Single-Stream Beamforming and Dual-Stream Beamforming. Added the FakeAntSelIdentificationSwitch option to
the [Link] parameter.

itorial Changes

None

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 5/56


12/15/2020 HedEx Startpage

2 About This Document

General Statements

rpose

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.

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

ature Differences Between RATs

The feature difference section only describes differences in switches or principles.


Unless otherwise stated, descriptions in this document apply to all RATs. If a description does not apply to all RATs, the specific RAT that it does apply to will be stated.
For example, in the statement "TDD cells are compatible with enhanced MU-MIMO", "TDD cells" indicates that this function cannot be used in non-TDD cells.

Applicable RAT
This document applies to TDD.

Features in This Document


This document describes the following TDD features.

Feature ID Feature Name Section

TDLOFD-001049 Single Streaming Beamforming 5.1 Single-Stream Beamforming and Dual-Stream Beamforming

TDLOFD-001061 Dual Streaming Beamforming 5.1 Single-Stream Beamforming and Dual-Stream Beamforming

TDLAOFD-001001 LTE-A Introduction See the corresponding sections of the subfeatures.

TDLAOFD-00100114 DL 2-Layer MIMO Based on TM9 5.2 TM9

TDLAOFD-081409 Downlink 4-Layer MIMO Based on TM9 5.2 TM9

TDLOFD-001077 MU-Beamforming 6 MU Beamforming

TDLOFD-110221 DL 4-Layer MU-Beamforming 6 MU Beamforming

TDLOFD-130204 Advanced Multi-User Coordination 6 MU Beamforming

3 Overview

Definition
Beamforming is a downlink multiple-antenna feature introduced since 3GPP Release 8.
When beamforming is enabled, an eNodeB weights physical downlink shared channel (PDSCH) data to form a narrow beam towards target UEs, increasing the signal-to-noise ratio
(SNR) for demodulation and improving user experience at the cell edge.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 6/56


12/15/2020 HedEx Startpage
Figure 3-1 Beamforming

Feature Overview

Table 3-1 Beamforming feature overview (SU beamforming)

Beamforming Feature Transmission Mode Antenna Port Number of Supported Data Transmit/Receive Mode of the
Streams RRU

TDLOFD-001049 Single TM7 Antenna port 5 1 4T4R or 8T8R


Streaming Beamforming
(known as single-stream
beamforming)

TDLOFD-001049 Single TM8 Antenna port 7 or 8 1 4T4R or 8T8R


Streaming Beamforming
(known as single-stream
beamforming)

TDLOFD-001061 Dual TM8 Antenna ports 7 and 8 2 4T4R or 8T8R


Streaming Beamforming
(known as dual-stream
beamforming)

TDLAOFD-00100114 DL 2- TM9 Antenna ports 7 and 8 1 or 2 4T4R or 8T8R


Layer MIMO Based on TM9

TDLAOFD-081409 DL 4-Layer TM9 Antenna ports 7 to 10 1 to 4 4T4R or 8T8R


MIMO Based on TM9

Table 3-2 Beamforming feature overview (MU beamforming)

Beamforming Feature Transmission Mode Antenna Port Number of Supported Data Transmit/Receive Mode of the
Streams RRU

TDLOFD-001077 MU- TM7, TM8, or TM9 Antenna port 5, 7, or 8 2, corresponding to two UEs 4T4R or 8T8R
Beamforming (known as 2-
layer MU beamforming)

TDLOFD-110221 DL 4-Layer TM7, TM8, or TM9 Antenna port 5, 7, or 8 2 to 4, corresponding to two to 8T8R
MU-Beamforming (including 4- four UEs
layer MU beamforming and
adaptive MU beamforming)

TDLOFD-130204 Advanced TM7, TM8, or TM9 Antenna port 5, 7, or 8 2 to 4, corresponding to two to At least one RRU
Multi-User Coordination four UEs equipped with four or
more antennas are
configured in D-MIMO
or SFN scenarios.
In other scenarios,
4T4R or 8T8R RRUs
are required.

In this document, downlink 2-layer MIMO based on TM9 and downlink 4-layer MIMO based on TM9 are referred to as TM9 for short.

Application Scenarios
In most cases, beamforming is used with MIMO. The following table lists the typical scenarios.

Table 3-3 Typical application scenarios

Application Scenario MIMO Mode Available Transmission Mode Reference

Scenario A: adaptive switching between single- Downlink 2x2 MIMO TM2, TM3, TM7, and TM8 5.1 Single-Stream Beamforming and Dual-
or dual-stream beamforming and MIMO Stream Beamforming
7 UE-level TMA

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 7/56


12/15/2020 HedEx Startpage

Application Scenario MIMO Mode Available Transmission Mode Reference

Downlink 4x4 MIMO TM2, TM3, TM4, TM7, and TM8 5.1 Single-Stream Beamforming and Dual-
Stream Beamforming

7 UE-level TMA

Scenario B: adaptive switching between single- Downlink 2x2 MIMO TM2, TM3, TM7, TM8, and TM9 5.1 Single-Stream Beamforming and Dual-
or dual-stream beamforming, TM9, and MIMO Stream Beamforming
5.2 TM9
7 UE-level TMA

Scenario C: MU beamforming enabled on the Same as scenario A or B Same as scenario A or B 5.1 Single-Stream Beamforming and Dual-
basis of scenario A or B Stream Beamforming
5.2 TM9
6 MU Beamforming
7 UE-level TMA

Scenario D: network reconstruction scenario Same as scenario A, B, or Same as scenario A, B, or C 5.1 Single-Stream Beamforming and Dual-
C Stream Beamforming
5.2 TM9
6 MU Beamforming
7 UE-level TMA

NOTE:
This document describes the following reconstruction scenarios:

Replacement of 2T2R or 4T4R RRUs on the live network with 4T4R or 8T8R RRUs, respectively
Change of the transmit/receive mode of an RRU (which is originally split into two 2T2R or 4T4R RRUs) to 4T4R or 8T8R, respectively

4 General Principles

Overall Procedure
The overall beamforming procedure is as follows:

1. RRU channel calibration


2. Weight calculation
3. Weighting
4. Beamforming implementation
5. Demodulation

Figure 4-1 shows the overall beamforming procedure.

Figure 4-1 Overall beamforming procedure

Transmission mode 9 (TM9) has been introduced in 3GPP Release 10. There are two types of TM9: precoding matrix indication (PMI) feedback-dependent TM9 and PMI feedback-
independent TM9. Compared with TM7 and TM8, TM9 uses a different weighting mechanism and different reference signals for channel state information (CSI) measurement. Table
4-1 compares the transmission modes.

Table 4-1 Comparison between different transmission modes

Transmission Mode Weighting Mechanism Reference Signal Used for CSI Demodulation Mechanism Antenna Port Used for
Measurement Demodulation

TM7 SRS-based weighting Cell-specific reference signals Based on DMRSs Antenna port 5
(CRSs)

TM8 SRS-based weighting CRSs Based on DMRSs Antenna port 7 or 8

PMI feedback-independent SRS-based weighting CRSs Based on DMRSs Antenna ports 7 to 14


TM9

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 8/56


12/15/2020 HedEx Startpage

Transmission Mode Weighting Mechanism Reference Signal Used for CSI Demodulation Mechanism Antenna Port Used for
Measurement Demodulation

PMI feedback-dependent TM9 PMI-based weighting Channel state information- Based on DMRSs Antenna ports 7 to 14
reference signals (CSI-RSs)

RRU Channel Calibration

ckground

Unlike LTE FDD, LTE TDD uses the same frequency in the uplink and downlink. This enables LTE TDD eNodeBs to estimate downlink channel characteristics based on uplink
channel characteristics. Accurate channel estimation requires that the amplitude and phase be consistent between uplink and downlink LTE TDD channels.
Complete reciprocity between the uplink and downlink channel characteristics is impossible due to the amplitude and phase differences between RRU transmit and receive channels.
Such differences vary with transmit and receive channels. To improve the reciprocity between RRU transmit and receive channels, channel calibration is required.

ocedure

1. The eNodeB uses a channel calibration algorithm to calculate the variations of the phase and amplitude of known signals transmitted on different transmit and receive
channels.
2. The eNodeB compensates the phase and amplitude based on the calculations, improving the reciprocity between transmit and receive channels.

pplication

The eNodeB initiates channel calibration based on the following principles:

The eNodeB automatically starts channel calibration within 10 minutes after a cell is set up.
If the initial channel calibration fails, the eNodeB initiates another channel calibration, and keeps trying until channel calibration is successful or three consecutive attempts
have failed.
The eNodeB initiates channel calibration for an 8T8R cell configured with two CRS antenna ports and working in a frequency ranging from 1880 MHz to 1920 MHz or from
2010 MHz to 2025 MHz, immediately after the cell exits the RF channel intelligent shutdown mode. For details about the RF channel intelligent shutdown feature, see Energy
Conservation and Emission Reduction.

For details about how to check whether channel calibration is successful, see [Link] Activation Verification.

Weight Calculation
During weight calculation, the eNodeB obtains a vector to adjust the shape and directionality of beams based on downlink channel characteristics. Downlink channel characteristics
are key to improving the weight calculation accuracy. The methods for obtaining downlink channel characteristics vary with transmission modes.

M7, TM8, and PMI Feedback-independent TM9

Figure 4-2 Weight calculation for TM7, TM8, and PMI feedback-independent TM9

1. The eNodeB obtains the SRSs sent by the UE and then estimates the downlink channel characteristics.
2. The eNodeB uses a beamforming weight calculation algorithm to calculate the weighting based on the downlink channel characteristics.

MI Feedback-dependent TM9

Figure 4-3 Weight calculation for PMI feedback-dependent TM9

1. The UE estimates the downlink channel characteristics based on the received CSI-RSs.
The CSI-RS has been introduced for CSI measurement in 3GPP Release 10. For details about CSI-RSs, see 4.7.2 CSI-RSs.
2. The UE selects the most appropriate weight from the predefined codebook at the very moment based on the downlink channel characteristics, and then provides CSI
feedback to the eNodeB on the PUCCH.
CSI data includes the PMI, rank indication (RI), and channel quality indicator (CQI).
For details about CSI feedback modes, see sections 7.2.1 "Aperiodic CQI/PMI/RI Reporting using PUSCH" and 7.2.2 "Periodic CSI Reporting using PUCCH" in
3GPP TS 36.213 V10.5.0.

3. The eNodeB uses a beamforming weight calculation algorithm to calculate the weighting value based on CSI data.

Weighting
During weighting, the eNodeB uses the vector addition function to add the calculated weighting and the data to be transmitted, including data streams and DMRSs. The width and
directionality of the beam are adjusted based on the calculations. Weighting is applied as follows:
Assume that the noise, N, is generated when an input signal, x(i), passes through channel H. The output signal, y(i), is calculated using the following formula:
y(i) = Hx(i) + N

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 9/56


12/15/2020 HedEx Startpage
When weighting is applied, input signal x(i) is multiplied by complex vector w(i) to change the amplitude and phase of output signal y(i). Output signal y(i) is calculated using the
following formula:
y(i) = Hw(i)x(i) + N
If each input signal x(i) in input signal group X is weighted using a different complex vector w(i) when passing through channel H, output signal group Y is directional, as shown in
Figure 4-4.

Figure 4-4 Weighting in 4T4R networking scenarios

Beamforming Implementation
After weighting, the data is transmitted in a narrow beam directed towards target UEs.
Beamforming uses the interference principle, as shown in Figure 4-5. The crests indicate carrier signal peaks. The signal strength increases when two crests intersect each other and
decreases when a crest intersects with a trough.
If beamforming is not used, the beam shape and lobe positions are fixed. When a UE resides between two beams at the cell edge, signals are weak.
When beamforming is enabled, the eNodeB imposes weighting on and adjusts the transmit power and phase of signals to be transmitted through each antenna array to change the
beam shape and direct the main lobe at target UEs, improving the signal strength.
Figure 4-5 Beamforming principles

NOTE:
For details about the main and side lobes, see 4.7.1 Antenna Patterns.

Demodulation
During demodulation, the UE demodulates physical downlink shared channel (PDSCH) data based on demodulation reference signals (DMRSs).
According to 3GPP Release 10, up to eight layers of data can be demodulated based on the DMRSs and up to eight antenna ports can be used for DMRS demodulation. Table 4-2
lists which antenna ports are available for DMRS demodulation and transmission modes defined in different 3GPP releases.

Table 4-2 Antenna ports available for DMRS demodulation and transmission modes defined in different 3GPP releases

3GPP Specifications Transmission Mode Antenna Port Used for DMRS Demodulation

3GPP Release 8 TM7: single-stream beamforming Antenna port 5

3GPP Release 9 TM7: single-stream beamforming Antenna port 5

TM8: adaptive switching between single-stream beamforming and Antenna port 7 or 8


dual-stream beamforming

3GPP Release 10 TM7: single-stream beamforming Antenna port 5

TM8: adaptive switching between single-stream beamforming and Antenna port 7 or 8


dual-stream beamforming

TM9: up to eight layers Antenna ports 7 to 14

Figure 4-6 shows the mapping from the layers for transmitting DMRSs to antenna ports.

Figure 4-6 Mapping of layers to antenna ports for DMRSs

For details about the DMRS pattern, see section [Link] "Mapping to resource elements" in 3GPP TS 36.211 V10.5.0. For details about DMRS power allocation, see section 5.2
"Downlink power allocation" in 3GPP TS 36.213 V10.5.0.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 10/56


12/15/2020 HedEx Startpage
Related Concepts

4.7.1 Antenna Patterns


Figure 4-7, Figure 4-8, and Figure 4-9 show antenna patterns.
Antenna patterns usually have two or more lobes on the same main plane. The one with the largest radiation strength is the main lobe and the other lobes are side lobes. The
beamwidth (also known as lobewidth) is the angle between the half-power (-3 dB) points of the main lobe. A wide beam indicates a large azimuth and scattered energy. A narrow
beam indicates good directionality and centralized energy.
Figure 4-7 Three-dimensional antenna pattern

Figure 4-8 Vertical antenna pattern

Figure 4-9 Horizontal antenna pattern

4.7.2 CSI-RSs
CSI-RS has been introduced in 3GPP Release 10 to replace cell-specific reference signals (CRSs) for CSI measurements, thereby decreasing the amount of time-frequency
resources required by CRS transmissions in 8T8R networking scenarios.
Table 4-3 Comparison between CSI-RSs and CRSs

CSI Measurement Signal CRS CSI-RS

Number of Supported Antenna Ports 1, 2, or 4 1, 2, 4, or 8

Number of Available Antennas 1, 2, or 4 1, 2, 4, or 8

Antenna Port Antenna ports 0 to 3 Antenna ports 15 to 22

Applicable Transmission Mode TM1 to TM8, and PMI feedback-independent PMI feedback-dependent TM9
TM9

Number of REs in a Single RB Used for Reference 8 when one antenna port is used 2 when one or two antennas are used
Signal Transmission 16 when two antenna ports are used 4 when four antenna ports are used
24 when four antenna ports are used 8 when eight antenna ports are used

CSI-RS-related parameters belong to the CellCsiRsParaCfg MO. For details about resource mappings related to CSI-RSs, see section [Link] "Mapping to resource elements" in
3GPP TS 36.211 V10.5.0.

5 SU Beamforming

Single-Stream Beamforming and Dual-Stream Beamforming

Table 5-1 Single-stream beamforming and dual-stream beamforming features

Feature Transmission Mode Antenna Port Number of Supported Data Transmit/Receive Mode of the
Streams RRU

TDLOFD-001049 Single TM7 Antenna port 5 1 4T4R or 8T8R


Streaming Beamforming
(known as single-stream
beamforming)

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 11/56


12/15/2020 HedEx Startpage

Feature Transmission Mode Antenna Port Number of Supported Data Transmit/Receive Mode of the
Streams RRU

TDLOFD-001049 Single TM8 Antenna port 7 or 8 1 4T4R or 8T8R


Streaming Beamforming
(known as single-stream
beamforming)

TDLOFD-001061 Dual TM8 Antenna ports 7 and 8 2 4T4R or 8T8R


Streaming Beamforming
(known as dual-stream
beamforming)

5.1.1 General Principles

ngle-Stream Beamforming

Single-stream beamforming enables an eNodeB to transmit one data stream to each UE using the same OFDM time-frequency resource, as shown in Figure 5-1. This feature applies
when the channel quality is poor.
Figure 5-1 Single-stream beamforming

The BfSwitch option under the [Link] parameter specifies whether single-stream beamforming is enabled.

al-Stream Beamforming

Dual-stream beamforming enables an eNodeB to transmit two data streams using the same OFDM time-frequency resource for spatial multiplexing, as shown in Figure 5-2. This
feature applies when the channel quality is satisfactory and antenna channels are lowly correlated.
Figure 5-2 Dual-stream beamforming

Dual-stream beamforming requires single-stream beamforming to be enabled and the [Link] parameter to be set to DUAL_LAYER_BF.
To reduce the impact of fake antenna selection UEs on the network, it is recommended that the fake antenna selection UE identification function be enabled to:

Identify and disable the transmit antenna selection capability of fake antenna selection UEs.
Optimize the MCS index selection for antenna selection UEs to achieve the gains of transmit antenna selection.

The FakeAntSelIdentificationSwitch option under the [Link] parameter is used to control the fake antenna selection UE identification function.
Fake antenna selection UE identification requires that the UeSRSAntSelectCtrlSwitch option be deselected under the [Link] parameter to
enable transmit antenna selection.

NOTE:
If the chip of a UE supports transmit antenna selection and its RF module does not support this function, the UE does not support transmit antenna selection as a whole. However,
the UE still claims its support for transmit antenna selection using the RRC_UE_CAP_INFO message. This type of UE is called a fake antenna selection UE. Figure 5-3 shows the
differences between antenna selection UEs and fake antenna selection UEs.

Figure 5-3 Antenna selection UEs and fake antenna selection UEs

5.1.2 Network Analysis

[Link] Benefits

ature Activation Suggestion

Table 5-2 Feature activation suggestions

RRU Specifications Recommended Single-Stream or Dual-Stream Beamforming Feature

4T4R Single-stream beamforming


Dual-stream beamforming if there are antenna selection UEs on the live network. For details about how to
enable fake antenna selection UE identification, see Figure 5-4 and Figure 5-5.

8T8R Dual-stream beamforming

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 12/56


12/15/2020 HedEx Startpage
Figure 5-4 Scenario 1 for enabling fake antenna selection UE identification

Figure 5-5 Scenario 2 for enabling fake antenna selection UE identification

hievable Gains

Beamforming can achieve all of the following gains:

Power gain
The total transmit power achieved when N transmit channels are used is N times that achieved when a single transmit channel is used. When N transmit channels are used,
the power gain of 10log(N) dB is received.
Array gain
White noise cancels out each other due to its good orthogonality after overlapping with each other. For carrier signals, their overlapping increases the energy. When multiple
antennas are used on an eNodeB, the receive signal to interference plus noise ratio (SINR) increases, thereby improving user experience.
A MISO system can bring an array gain of 10log(N) dB based on a SISO system, where the variable N indicates the number of antennas.

Diversity gain
Due to the independence of signal attenuations on spatial channels, beamforming enables multiple antennas to simultaneously transmit the same data. In this way, the impact
of SINR fluctuations is compromised when channel quality deteriorates.

Multiplexing gain
When signal quality is satisfactory, beamforming enables an eNodeB to transmit multiple data streams using the same time-frequency resource, thereby increasing the cell
throughput and peak capacity.

Beamforming gain
Beamforming enables beams to be directed at target UEs, thereby increasing the signal strength of UEs, especially that of cell edge users (CEUs).

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 13/56


12/15/2020 HedEx Startpage

[Link] Impacts

twork Impacts

Single-stream beamforming
This function improves the downlink cell throughput and spectral efficiency.
Dual-stream beamforming
This function enables an eNodeB to transmit two data streams using the same time-frequency resource, increasing the downlink cell throughput and spectral efficiency.
Fake antenna selection UE identification improves the downlink cell throughput and spectral efficiency.

The downlink throughput and spectral efficiency of a cell are calculated as follows:

The average downlink cell throughput is indicated by Cell Downlink Average Throughput.
The downlink spectral efficiency is calculated using the following formula:
Average downlink throughput per PRB (bit/PRB) = [Link]/(60 x 60 x 800 x [Link])

nction Impacts

The following table describes the function impact of single-stream beamforming.

Function Name Function Switch Reference Description

Uplink 2CC CA CaUl2CCSwitch option under Carrier Aggregation The PCC supports beamforming. The support of SCCs for
the [Link] beamforming is as follows:
parameter If uplink CA is enabled, the uplink SCC supports
beamforming.
If uplink CA is not enabled and beamforming in SCells
has been enabled, the SCC supports single- and dual-
stream beamforming. In this case, however, the SCC
does not support long-SRS-period beamforming or MU
beamforming.
If neither uplink CA nor beamforming in SCells is
enabled, the SCC does not support beamforming.

SFN [Link] SFN If this function is enabled and there are joint-scheduling UEs in
an SFN cell, the phases of the received signals at the UEs are
random. This compromises the gains brought by single-stream
beamforming, but system gains are still increased.

Intra-frequency split None Soft Split Resource Duplex (TDD) If soft split scheduling optimization is disabled, beamforming
UEs concentrate in areas where coverage of two cells from a
split overlaps. Beamforming takes effect in a smaller area and
Inter-frequency split None Soft Split Resource Duplex (TDD) produces smaller gains after the split. UE correlation is high,
and the pairing rate is low. This is because UE transmission
mode is affected by UE distributions.

The following table describes the function impact of dual-stream beamforming.

Function Name Function Switch Reference Description

Uplink 2CC CA CaUl2CCSwitch option under the Carrier Aggregation The PCC supports beamforming. The support of SCCs for beamforming is as
[Link] follows:
parameter If uplink CA is enabled, the uplink SCC supports beamforming.
If uplink CA is not enabled and beamforming in SCells has been
enabled, the SCC supports single- and dual-stream beamforming. In
this case, however, the SCC does not support long-SRS-period
beamforming or MU beamforming.
If neither uplink CA nor beamforming in SCells is enabled, the SCC
does not support beamforming.

Uplink SU-MIMO ULSUMIMO2LayersSwitch option MIMO After uplink SU-MIMO is enabled, two antennas send SRSs. The weights for
under the dual-stream beamforming are more accurate and the performance of this
[Link] function may improve.
parameter

5.1.3 Requirements

[Link] Licenses
The following licenses must be purchased for TDLOFD-001049 Single Streaming Beamforming.

Feature ID Feature Name Model Sales Unit

TDLOFD-001049 Single Streaming Beamforming LT1SSGSTRB00 per Cell

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 14/56


12/15/2020 HedEx Startpage
The following licenses must be purchased for TDLOFD-001061 Dual Streaming Beamforming.

Feature ID Feature Name Model Sales Unit

TDLOFD-001049 Single Streaming Beamforming LT1SSGSTRB00 per Cell

TDLOFD-001061 Dual Streaming Beamforming LT1SDUALSB01 per Cell

[Link] 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.

erequisite Functions

Single-stream beamforming requires the following functions.

Function Name Function Switch Reference Description

3GPP R8 specifications None None Single-stream beamforming (TM7) requires 3GPP R8


specifications.

3GPP R9 specifications None None Single-stream beamforming (TM8) requires 3GPP R9


specifications.

Dual-stream beamforming requires the following functions.

Function Name Function Switch Reference

3GPP R9 specifications None None

Single-stream beamforming [Link] Beamforming (TDD)

utually Exclusive Functions

The following table describes the mutually exclusive functions of single- and dual-stream beamforming.

Function Name Function Switch Reference

High speed mobility [Link] High Speed Mobility

Extended cyclic prefix (CP) [Link] Extended CP


[Link]

[Link] Hardware

se Station Models

3900 and 5900 series base stations

oards

Single-stream beamforming and dual-stream beamforming: UBBPei, UBBPe, UBBPg2, UBBPg2a, UBBPg3, UBBPd, UMDU, LBBPd, or LBBPc
Fake antenna selection UE identification requires BBPs other than the LBBP.

NOTE:
For the LBBPc and LBBPd, the [Link] parameter must be set to TDD_ENHANCE in 4T4R scenarios or TDD_8T8R in 8T8R scenarios.
LBBPc+LBBPc convergence is not supported when the [Link] parameter is set to TDD_ENHANCE for an LBBPc.
In LBBPc+LBBPd, LBBPc+UBBPd, LBBPc+UBBPe, or LBBPc+UBBPei convergence scenarios, the converged board must be the LBBPc, instead of the LBBPd, UBBPd,
UBBPe, or UBBPei.

F Modules

Single-stream beamforming and dual-stream beamforming require 4T4R or 8T8R RRUs and antennas.

NOTE:
Beamforming is not supported when the RRU3278 is split into two 4T4R RRUs.
The maximum transmit power of an RRU and the number of CRS ports also need to be collected in network reconstruction scenarios before feature deployment.

lls

The UE speed is less than 120 km/h.


The cell bandwidth is not 5 MHz.
The normal CP is used.

[Link] Others

Es

Table 5-3 lists the requirements for UEs.

Table 5-3 UE requirements

Function UE Requirement

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 15/56


12/15/2020 HedEx Startpage

Function UE Requirement

Single-stream beamforming The following conditions must be met:


The UE complies with 3GPP Release 8 or later.

The UE has at least two receive antennas.

Dual-stream beamforming The following conditions must be met:


The UE complies with 3GPP Release 9 or later.
The UE has at least two receive antennas.
The UE category is greater than or equal to 2.
Either of the following conditions must be met in 4T4R scenarios:
The UE supports transmit antenna selection.
The UE has two transmit antennas and SRS resources are allocated over two antenna ports.
This requirement does not apply to 8T8R scenarios.
If a 4T4R RRU functions as the target RRU in SFN scenarios, the UEs located in the overlapping coverage area of two RRUs
must support transmit antenna selection. Alternatively, the UE has two transmit antennas and SRS resources are allocated
over two antenna ports. This requirement does not apply when an 8T8R RRU functions as the target RRU.

Perform the following operations to verify that the UE has been allocated SRS resources over two antenna ports:

1. Select the ULSUMIMO2LayersSwitch option under the [Link] parameter.


2. Perform Uu interface signaling tracing on the OSS. Figure 5-6 shows the tracing result.
Figure 5-6 Uu interface signaling tracing result

rdware Installation Requirements in Generic Scenarios

Antennas and RRUs must be connected according to the diagrams shown in Figure 5-7 to Figure 5-10. Otherwise, multiple-antenna performance may be affected. All beamforming
features described in this document must meet the hardware installation requirements described in this chapter.
Figure 5-7 4-antenna cross-polarization mapping

Figure 5-8 4-antenna linear-polarization mapping

Figure 5-9 4-antenna circular-polarization mapping

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 16/56


12/15/2020 HedEx Startpage
Figure 5-10 8-antenna cross-polarization mapping

rdware Installation Requirements in Network Reconstruction Scenarios

A 4T4R sector can also be served by part of an 8T8R RRU. Four RRU ports and four antenna ports can be selected to set up a 4T4R sector, as shown in Figure 5-11 and Figure 5-12.
All beamforming features described in this document must meet the hardware installation requirements described in this chapter.
The requirements for splitting an 8T8R RRU are as follows:

Preferentially select two pairs of cross-polarized antennas that are functional and closest to each other.
Randomly select four functional RRU ports, and connect these ports in ascending order of sequence number to the antennas.
Connect the RRU's CAL calibration port and the antenna system's CAL calibration port.

Figure 5-11 Port connection for configuring a 4T4R sector served by part of an 8T8R RRU (1)

Figure 5-12 Port connection for configuring a 4T4R sector served by part of an 8T8R RRU (2)

5.1.4 Operation and Maintenance

[Link] Data Configuration

[Link].1 Data Preparation


The following tables describe the MOs and parameters that must be set to activate single- and dual-stream beamforming.

Table 5-4 Parameters in the BBP MO

Parameter Name Parameter ID Setting Notes

Work Mode [Link] This parameter specifies the working mode of the BBP. For an LBBP, set this parameter to
TDD_ENHANCE when beamforming is used in 4T4R scenarios and to TDD_8T8R when
beamforming is used in 8T8R scenarios.
This parameter is not required for the UBBPd, UBBPe, UBBPei, or UMDU.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 17/56


12/15/2020 HedEx Startpage
Table 5-5 Parameters in the SRSCfg MO

Parameter Name Parameter ID Setting Notes

SRS Configuration Indicator [Link] To improve beamforming performance, set this parameter to BOOLEAN_TRUE. In this situation,
however, the uplink peak throughput may decrease.

TDD SRS Configuration Mode [Link] The value ACCESS_ENHANCED is recommended.

Table 5-6 Parameters in the CellAlgoSwitch MO

Parameter Name Parameter ID Option Setting Notes

BF algorithm switch [Link] BfSwitch Select this option.

[Link] LongSrsPeriodBfSwitch You are advised to select this option.

[Link] FakeAntSelIdentificationSwitch You are advised to select this option.

Table 5-7 Parameters in the CellBf MO

Parameter Name Parameter ID Setting Notes

Beamforming maximum [Link] Set this parameter to SINGLE_LAYER_BF if single-stream beamforming is required.
number of layers Set this parameter to DUAL_LAYER_BF if dual-stream beamforming is required.

Dual Layer Beamforming [Link] Set this parameter to CIRCULAR_ANTENNA_ARRAY_BFALG when 8T8R
Algorithm Type omnidirectional antennas are used.
Set this parameter to AUTO_CONFIG for other types of antennas.

Table 5-8 Parameter in the ENodeBAlgoSwitch MO

Parameter Name Parameter ID Option Setting Notes

Compatibility Control Switch [Link] UeSRSAntSelectCtrlSwitch Fake antenna selection UE identification requires that
this option be deselected to enable transmit antenna
selection.

[Link].2 Using MML Commands

tivation Command Examples

The cell will reset after SRS configurations are modified by running the MOD SRSCFG command.

//(Optional) Querying the working mode of the BBP when a UBBP is not used. If the value of the Work Mode parameter is not TDD_ENHANCE(Support TDD BF
LST BBP:;
MOD BBP: CN=0, SRN=0, SN=3, WM=TDD_ENHANCE;
//Configuring SRS resources
MOD SRSCFG: LocalCellId=0, SrsCfgInd=BOOLEAN_TRUE;
//Turning on the beamforming switch and, preferably, the long-SRS-period beamforming switch
MOD CELLALGOSWITCH: LOCALCELLID=0, BFALGOSWITCH=BfSwitch-1&LongSrsPeriodBfSwitch-1;
//Configuring the maximum number of beamforming layers
MOD CELLBF: LOCALCELLID=0, MAXBFRANKPARA=DUAL_LAYER_BF;
//Enabling fake antenna selection UE identification and disabling antenna selection for SRS transmission
MOD ENODEBALGOSWITCH: CompatibilityCtrlSwitch=UeSRSAntSelectCtrlSwitch-0;
MOD CELLALGOSWITCH: LOCALCELLID=0, BFALGOSWITCH=FakeAntSelIdentificationSwitch-1;

activation Command Examples

//Disabling beamforming
MOD CELLALGOSWITCH: LocalCellId=0, BfAlgoSwitch=BfSwitch-0;
//Disabling fake antenna selection UE identification
MOD CELLALGOSWITCH: LOCALCELLID=0, BFALGOSWITCH=FakeAntSelIdentificationSwitch-0;

[Link].3 Using the CME


For detailed operations, see CME-based Feature Configuration.

[Link] Activation Verification


UEs must reaccess the network to make beamforming take effect after the beamforming algorithm is enabled. Perform the following steps for activation verification:

1. Run the ACT CELL command to activate the cell in which beamforming is used, and run the DSP CELL command to check the cell status.
The cell has been activated if the value of the Cell instance state parameter is Normal.
2. Run the DSP CELLCALIBRATION command to check the channel calibration results. Channel calibration is successful if the value of the Calibration Result parameter is
Success in the latest calibration.

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.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 18/56


12/15/2020 HedEx Startpage
Figure 5-13 Channel calibration results

After fake antenna selection UE identification is enabled, perform the following steps to verify it:

1. View the RRC_UE_CAP_INFO message on the Uu interface. A fake antenna selection UE claims its support for transmit antenna selection using an RRC_UE_CAP_INFO
message, as shown in Figure 5-14.
Figure 5-14 RRC_UE_CAP_INFO message

2. After the UE is identified, view the RRC_CONN_RECFG message. If the eNodeB instructs the UE to disable transmit antenna selection using an RRC_CONN_RECFG
message, as shown in Figure 5-15, fake antenna selection UE identification has taken effect.
Figure 5-15 RRC_CONN_RECFG message

[Link] Network Monitoring


The monitoring methods described in this section are suitable for all beamforming features in this document.

ounter-based Monitoring

Monitor resource usages in different transmission modes based on the following counters.

Counter ID Counter Name

1526728881 [Link].Rank1

1526728882 [Link].Rank2

bservation by Comparing Performance Counters

Compare the traffic statistics obtained in the same period of time before and after the feature deployment. The counters and expected results are as follows:
The uplink and downlink UE throughput increase after the network reconstruction.
Downlink user-perceived rate = ([Link] – [Link])/[Link]/1000
Uplink user-perceived rate = ([Link] – [Link])/[Link]/1000

Proportion of downlink dual-stream beamforming: increase after feature activation


Proportion of downlink dual-stream beamforming: [Link].Rank2/([Link].Rank1 + [Link].Rank2 +
[Link].Rank1 + [Link].Rank2 + [Link].Rank3 + [Link].Rank4 + [Link].Rank1 +
[Link].Rank2 + [Link].Rank3 + [Link].Rank4 + [Link].Rank5 + [Link].Rank6 +
[Link].Rank7 + [Link].Rank8)
Proportion of downlink single-stream beamforming: increase after feature activation
Proportion of downlink single-stream beamforming: [Link].Rank1/([Link].Rank1 + [Link].Rank2 +
[Link].Rank1 + [Link].Rank2 + [Link].Rank3 + [Link].Rank4 + [Link].Rank1 +
[Link].Rank2 + [Link].Rank3 + [Link].Rank4 + [Link].Rank5 + [Link].Rank6 +
[Link].Rank7 + [Link].Rank8)
Average downlink CQI: This KPI must not decrease after feature activation.
Average downlink CQI = Sum([Link].0 x 0 through [Link].15 x 15)/Sum([Link].0 through [Link].15)
Basic air interface counters: These counters must not deteriorate after the network reconstruction.
RRC connection setup success rate = 100 x [Link]/[Link]
Downlink IBLER = ([Link] + [Link] + [Link])/([Link] +
[Link] + [Link]) x 100
Service drop rate = 100 x [Link]/([Link] + [Link])

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 19/56


12/15/2020 HedEx Startpage
Basic air-interface counter values must not obviously deteriorate. If the counter values deteriorate, perform the following operations:

1. Check whether the network structure is changed during the network reconstruction or upgrade. Some operations, such as antenna tilt adjustment, affect network coverage.
2. Check whether the RRU is connected to antennas properly during the network reconstruction. For details, see [Link] Others.
3. Check whether configurations, especially the maximum transmit power of RRUs, are modified after the upgrade.
4. Check whether the number of UEs served by a cell changes obviously after the upgrade. If the number of UEs changes obviously due to objective reasons, continue the
observation. Compare the data when the difference of UE quantities before and after the upgrade is small.

bservation by Conducting a Fixed-Point or Mobile Test on a Single UE

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

Fixed-point test

1. Perform uplink and downlink multi-thread FTP services at five to ten points separately selected near the center, middle, and edge of a cell.
2. Record the uplink and downlink transmission rates measured at the points before and after the upgrade.

Expected result: The transmission rates increase in both the uplink and downlink.

Mobile test

1. Perform FTP packet injection in both the uplink and downlink along the same route in the network reconstruction area.
2. Compare the uplink and downlink transmission rates measured before the network reconstruction with those measured after the network reconstruction.

Expected result: The transmission rates increase in both the uplink and downlink.

[Link] Possible Issues


If the transmission mode cannot switch to beamforming, rectify the fault by performing the following steps:

1. Verify that the operating environment, hardware, UE, and license meet the requirements provided in 5.1.3 Requirements.
2. Verify that activation operations are performed as described in [Link].1 Data Preparation.
3. Run the DSP CELLCALIBRATION command to check the channel calibration results. If channel calibration fails, check for uplink interference.
4. If a UE cannot switch to TM7 or TM8, check the RSRP of the UE. If the RSRP is low, move the UE 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 Normal, rectify the fault based on the cause value.

TM9
This document describes TM9 suitable only for non-massive MIMO scenarios. For details about how to deploy TM9 in massive MIMO scenarios, see Massive MIMO (TDD).

Table 5-9 TM9 feature overview

Feature Transmission Mode Antenna Port Number of Supported Data Transmit/Receive Mode of the
Streams RRU

TDLAOFD-00100114 DL 2- TM9 Antenna ports 7 and 8 1 or 2 4T4R or 8T8R


Layer MIMO Based on TM9

TDLAOFD-081409 DL 4-Layer TM9 Antenna ports 7 to 10 1 to 4 4T4R or 8T8R


MIMO Based on TM9

5.2.1 General Principles

ownlink 2-Layer MIMO Based on TM9

This feature enables the eNodeB to transmit up to two data streams using the same OFDM time-frequency resource in TM9, as shown in Figure 5-16. Adaptive switching between
rank 1 and rank 2 is supported based on UE conditions and channel environments.
Figure 5-16 Downlink 2-Layer MIMO Based on TM9

PMI feedback-dependent TM9 offers beamforming gains and increases the average cell throughput in carrier aggregation (CA) scenarios when SRSs are not configured.
TM9 requires single-stream beamforming to be enabled and the TM9Switch option to be selected under the [Link] parameter.

ownlink 4-Layer MIMO Based on TM9

This feature enables the eNodeB to transmit up to four data streams using the same OFDM time-frequency resource in TM9, as shown in Figure 5-17. Adaptive switching between
ranks (ranks 1 to 4) is supported based on UE conditions and channel environments.
Figure 5-17 Downlink 4-Layer MIMO Based on TM9

This feature offers the following benefits:

TM9 increases the peak cell throughput and average cell throughput when three or four data streams are transmitted using the same OFDM time-frequency resource.
PMI feedback-dependent TM9 offers beamforming gains in CA scenarios when SRSs are not configured.

Downlink 4-layer MIMO based on TM9 is recommended when both of the following conditions are met:

Single-stream beamforming is enabled and the TM9Switch option is selected under the [Link] parameter.
The [Link] parameter is set to SW_MAX_SM_RANK_4.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 20/56


12/15/2020 HedEx Startpage
5.2.2 Network Analysis

[Link] Benefits

ature Activation Suggestion

It is recommended that downlink 4-layer MIMO based on TM9 be enabled when all of the following conditions are met:

RRUs/antennas work in 4T4R or 8T8R mode.


The proportion of good signal quality (for example, SINR > 23 dB) is high.
The 4R or 8R TM9 UE penetration rate is high.

A higher proportion of 4R or 8R TM9 UEs in an area with good signal quality leads to larger increases in the average cell throughput and user-perceived rate.

NOTE:
TM9 is not compatible with downlink 4x4 MIMO.

hievable Gains

The gains of TM9 are the same as those of single- and dual-stream beamforming. For details, see Achievable Gains.

[Link] Impacts

twork Impacts

Downlink 2-layer MIMO based on TM9: This function enables the eNodeB to simultaneously transmit two data streams and improves the downlink cell throughput and spectral
efficiency.
Downlink 4-layer MIMO based on TM9: This function enables the eNodeB to simultaneously transmit two to four data streams and improves the downlink cell throughput and
spectral efficiency.

The downlink throughput and spectral efficiency of a cell are calculated as follows:

The average downlink cell throughput is indicated by Cell Downlink Average Throughput.
The downlink spectral efficiency is calculated using the following formula:
Average downlink throughput per PRB (bit/PRB) = [Link]/(60 x 60 x 800 x [Link])

nction Impacts

The following table describes the function impacts of downlink 2-layer MIMO based on TM9 and downlink 4-layer MIMO based on TM9.

Function Name Function Switch Reference Description

SFN cell [Link] SFN When the [Link] parameter is set


to CSI_RS_PORT_4 or CSI_RS_PORT_8 in SFN scenarios,
independent-scheduling and joint-scheduling TM9 UEs
perform CSI measurement for CQI, PMI, and RI feedback
based on the CSI-RS sent by the SFN cell, increasing the
average cell throughput and improving user experience.

CA for downlink 2CC None Carrier Aggregation When CSI-RSs are configured on the SCC, the UE performs
CSI measurements based on the received CSI-RSs. In this
CA for downlink 2CC in 40 None Carrier Aggregation situation, PMI feedback-dependent TM9 is used on the SCC,
MHz increasing the average cell throughput and improving user
experience.

Symbol power saving TddSymbolShutdownSwitch option Energy Conservation and Emission In the subframes where symbol power saving is implemented,
under the Reduction no PDSCH data is transmitted regardless of whether the UE
[Link] works in TM9 or not, but CSI-RSs can be transmitted for CSI
parameter measurements in PMI feedback-dependent TM9.

DL CoMP IntraDlCompSwitch, DL CoMP (TDD) TM9 UEs can be treated as DL CoMP UEs, and UEs working
InterDlCompDcsSwitch, and in PMI feedback-independent TM9 mode can be treated as
InterDlCompCbfSwitch options DL CoMP coordinating UEs.
under the
[Link]
parameter

eMBMS MBMSSwitch option under the eMBMS When eMBMS services are provided and PMCH data is
[Link] transmitted in the same subframes as CSI-RSs, 3GPP
parameter specifications-compliant CSI-RSs are not transmitted and no
UEs are scheduled for TM9. In this case, TM9 services are
affected.

Out-of-band relay OutOfBandRelaySwitch option Relay In the out-of-band relay network, when a downlink relay
under the subframe conflicts with a subframe used for CSI-RS
[Link] transmission, no CSI-RS is transmitted, ensuring that the
parameter impact on ReBTS transmissions is minimized. In this case,
TM9 services are affected.

Inter-cell downlink D-MIMO InterCellDmimoJTSwitch option D-MIMO (TDD) JT requires that all cells within an inter-cell D-MIMO cluster
under the have the same CSI-RS time-frequency position when TM9 is
[Link] enabled and CSI-RSs are configured.
parameter

5.2.3 Requirements

[Link] Licenses
The following license must be purchased for TDLAOFD-00100114 DL 2-Layer MIMO Based on TM9.

Feature ID Feature Name Model Sales Unit

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 21/56


12/15/2020 HedEx Startpage

Feature ID Feature Name Model Sales Unit

TDLAOFD-00100114 DL 2-Layer MIMO Based on LT1SLTEAID01 per Cell


TM9

The following licenses must be purchased for TDLAOFD-081409 DL 4-Layer MIMO Based on TM9.

Feature ID Feature Name Model Sales Unit

TDLAOFD-081409 DL 4-Layer MIMO Based on LT1S44TTM900 per Cell


TM9

[Link] 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.

erequisite Functions

Downlink 2-layer MIMO based on TM9 requires the following functions.

Function Name Function Switch Reference Description

Single-stream beamforming [Link] Beamforming (TDD) None

3GPP R10 specifications None None This function requires 3GPP Release 10 or later.

3GPP R11 specifications None None This function requires 3GPP Release 10 or later.

Support for UE categories None None This function requires support for a maximum of two, four, or
eight downlink spatial multiplexing layers.

Downlink 4-layer MIMO based on TM9 requires the following functions.

Function Name Function Switch Reference Description

Single-stream beamforming [Link] Beamforming (TDD) None

Downlink 2-layer MIMO TM9Switch option of the Beamforming (TDD) None


based on TM9 [Link]
parameter

3GPP R10 specifications None None None

Support for UE categories None None This function requires support for a maximum of four
downlink spatial multiplexing layers.

utually Exclusive Functions

Downlink 2-layer MIMO based on TM9 and downlink 4-layer MIMO based on TM9

Function Name Function Switch Reference Description

High speed mobility [Link] High Speed Mobility None

Extended CP [Link] Extended CP None


[Link]

LCS [Link] LCS None

Downlink 4x4 MIMO None MIMO None

OTDOA-based positioning OtdoaSwitch option of the LCS OTDOA cannot be enabled when the TM9Switch option of
[Link] the [Link] parameter is selected.
parameter

[Link] Hardware
The hardware requirements described in this section apply only to non-massive MIMO scenarios. In massive MIMO scenarios, the hardware requirements of massive MIMO cells
must be met.

se Station Models

3900 and 5900 series base stations

oards

Function Name BBP Model

Downlink 2-layer MIMO based on TM9 and UBBPg2, UBBPg2a, UBBPg3, UBBPei, UBBPe, UBBPd, UMDU, or LBBPd
downlink 4-layer MIMO based on TM9 For the LBBPd, the [Link] parameter must be set to TDD_ENHANCE in 4T4R scenarios and to TDD_8T8R in
8T8R scenarios.

F Modules

Function Name RRU or Antenna Type

Downlink 2-layer MIMO based on TM9 and 4T4R or 8T8R RRUs


downlink 4-layer MIMO based on TM9

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 22/56


12/15/2020 HedEx Startpage
In RRU split scenarios, beamforming is not supported when the RRU3278 is split into two 4T4R RRUs.
The maximum transmit power of an RRU and the number of CRS ports also need to be collected in network reconstruction scenarios before feature deployment.

lls

The requirements are the same as those of single- and dual-stream beamforming. For details, see Cells.

[Link] Others

Es

Table 5-10 UE requirements

Function Name UE Requirement

Downlink 2-layer MIMO based on All of the following conditions are met:
TM9 The UE complies with 3GPP Release 10 or later.
Bit 103 or 104 of the FGIs is set to 1.
The UE has at least two receive antennas.
The UE category is greater than or equal to 2.

Downlink 4-layer MIMO based on All of the following conditions are met:
TM9
The UE complies with 3GPP Release 10 or later.
Bit 103 or 104 of the FGIs is set to 1.
There are at least four receive antennas.
The UE category is equal to 5, or is greater than 5 and the value of the MIMO-CapabilityDL-r10 field is fourLayers or
eightLayers.
TBS optimization for MIMO UEs requires UE support
If the value of the alternativeTBS-Indices-r12 field is "true" in the UE capability information, the UE supports the TBS
optimization function.

rdware Installation Requirements in Generic Scenarios

The requirements are the same as those of single- and dual-stream beamforming. For details, see Hardware Installation Requirements in Generic Scenarios.

rdware Installation Requirements in Network Reconstruction Scenarios

The requirements are the same as those of single- and dual-stream beamforming. For details, see Hardware Installation Requirements in Network Reconstruction Scenarios.

5.2.4 Operation and Maintenance

[Link] Data Configuration

[Link].1 Data Preparation

rameters Used for Activation

TM9 cannot work with 4x4 MIMO. TM9 requires the following MOs and parameters.

Table 5-11 Parameters in the Cell MO

Parameter Name Parameter ID Setting Notes

CRS Port Number [Link] Retain the default value.

Table 5-12 Parameters in the CellBfMimoParaCfg MO

Parameter Name Parameter ID Setting Notes

Scc Bf Mimo Adaptive [Link] Set this parameter to ON when PMI feedback-dependent TM9 is enabled in downlink CA
Switch scenarios or when uplink CA is enabled.

Table 5-13 Parameters in the CellAlgoSwitch MO

Parameter Name Parameter ID Option Setting Notes

Enhanced MIMO [Link] TM9Switch Select this option if TM9 is required.


Switch

SFN DL Scheduling [Link] None Set this parameter to ADAPTIVE when TM9 is required in SFN
Switch scenarios.

SFN Load-based [Link] None Set this parameter to ON when TM9 is required in SFN
Adaptive Switch scenarios.

DL Scheduling [Link] MIMO_TBSIZE_OPT_SWITCH It is recommended that this option be selected if you want to
Extension Switch improve the peak rate of closed-loop TM9 UEs at the cell
center.

Table 5-14 Parameters in the CellDlschAlgo MO

Parameter Name Parameter ID Option Setting Notes

maximum number of [Link] None Set this parameter to SW_MAX_SM_RANK_2 if 2-layer


MIMO layers TM9 is required.
Set this parameter to SW_MAX_SM_RANK_4 if 4-layer
TM9 is required.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 23/56


12/15/2020 HedEx Startpage

Parameter Name Parameter ID Option Setting Notes

CSI-RS Subframe [Link] UnCfgCsiRsUESchSwitch When TM9 is enabled, it is recommended that this option be
Scheduling Strategy deselected to prohibit scheduling of CSI-RS-unconfigured UEs in
Switch CSI-RS subframes.

CSI-RS Subframe [Link] UnCfgCsiRsUEDeOrderSchSwitch It is recommended that this option be selected when the
Scheduling Strategy penetration rate of TM9 UEs is low.
Switch

Table 5-15 Parameters in the CellCsiRsParaCfg MO

Parameter Name Parameter ID Setting Notes

CSI-RS Switch [Link] Set this parameter to FIXED_CFG when TM9 is enabled.
Set this parameter to NOT_CFG when TM9 is disabled.

CsiRs Port Number [Link] For normal cells:


It is recommended that this parameter be set to CSI-RS_PORT_8 when the
transmit/receive mode is 8T8R.
This parameter must be set to CSI-RS_PORT_4 when the transmit/receive mode is
4T4R.
For SFN cells:
It is recommended that this parameter be set to CSI-RS_PORT_8 when the
transmit/receive mode is 2T2R+8T8R or 8T8R+8T8R.
This parameter must be set to CSI-RS_PORT_4 when the transmit/receive mode is
2T2R+4T4R, 4T4R+4T4R, or 4T4R+8T8R.

CSI-RS Period [Link] Set this parameter to ms80. The cell will reset if the value is changed.

Table 5-16 Parameters in the eNodeBAlgoSwitch MO

Parameter Name Parameter ID Option Setting Notes

Compatibility Control [Link] UeCsiRsCfigCtrlSwitch To configure the CSI-RS policy for TM9-incapable UEs compliant
Switch with 3GPP Release 10 or later, select this option. In this case, if the
UEs have compatibility issues, the UE performance deteriorates.
Check with the operator whether UEs on the live network are
compliant with 3GPP Release 10 or later. If not, deselect this
option.

[Link].2 Using MML Commands

tivation Command Examples

The cell will reset after the CSI-RS period is changed by running the MOD CELLCSIRSPARACFG command.

To enable TM9, perform the following steps:


//Turning on the TM9 algorithm switch
MOD CELLALGOSWITCH: LocalCellId=0, ENHMIMOSWITCH=TM9Switch-1;
//Turning on the CSI-RS configuration switch and configuring the CSI-RS period and the number of CSI-RS ports
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;
//Deselecting the UnCfgCsiRsUESchSwitch option and selecting the UnCfgCsiRsUEDeOrderSchSwitch option
MOD CELLDLSCHALGO: LOCALCELLID=0, CSIRSSFSCHSTRSWITCH=UNCFGCSIRSUESCHSWITCH-0&UnCfgCsiRsUEDeOrderSchSwitch-1;
//(Optional) Selecting the UeCsiRsCfigCtrlSwitch option to configure the CSI-RS policy for TM9-incapable UEs compliant with 3GPP Release 10 or later
MOD ENODEBALGOSWITCH: CompatibilityCtrlSwitch=UeCsiRsCfigCtrlSwitch-0;
//(Optional) Enabling SCC-specific adaptive switching between MIMO and beamforming if PMI feedback-dependent TM9 is required in downlink CA scenario
MOD CELLBFMIMOPARACFG: LOCALCELLID=0, SccBfMimoAdaptiveSwitch=ON;
//(Optional) Setting the SfnDlSchSwitch parameter to ADAPTIVE and the SfnLoadBasedAdptSwitch parameter to ON if TM9 is required in SFN scenarios
MOD CELLALGOSWITCH: LOCALCELLID=0, SfnDlSchSwitch=ADAPTIVE, SfnLoadBasedAdptSwitch=ON;
//(Optional) Enabling MIMO TBS optimization if the peak rate of TM9 UEs at the cell center needs to be improved.
MOD CELLALGOSWITCH: LOCALCELLID=0, DlSchExtSwitch=MIMO_TBSIZE_OPT_SWITCH-1;

activation Command Examples

//Setting the [Link] parameter set to NOT_CFG before TM9 is disabled


MOD CELLCSIRSPARACFG: LocalCellId=0, CSIRSSWITCH= NOT_CFG;
MOD CELLALGOSWITCH: LocalCellId=0, ENHMIMOSWITCH=TM9Switch-0;

[Link].3 Using the CME


For detailed operations, see CME-based Feature Configuration.

[Link] Activation Verification

Method of verifying the TM9 mode


UEs must reaccess the network to make TM9 take effect after the TM9 algorithm is enabled.
Enable a UE to access the network. Start Uu interface tracing on the OSS and check the transmissionMode information element (IE) in the RRC_CONN_SETUP message. If
the value of the transmissionMode IE is "TM9", TM9 has taken effect.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 24/56


12/15/2020 HedEx Startpage
Figure 5-18 transmissionMode tracing result

Method of verifying TBS optimization for MIMO UEs


Verify whether peak rate improvement is enabled for closed-loop TM9 UEs at the cell center.
On the OSS, perform a Uu interface signaling trace task to check the RRC Connection Reconfiguration message. As shown in Figure 5-19, if the value of the tbsIndexAlt IE in
the message is a26 or a33, this function has taken effect.
Figure 5-19 Signaling tracing result

[Link] Network Monitoring

ounter-based Monitoring

Monitor resource usages in TM9 based on the following counters.

Counter ID Counter Name

1526732723 [Link]

1526732888 [Link]

1526747680 [Link]

1526747667 [Link].TM9

1526747668 [Link].TM9

1526747669 [Link]

1526747670 [Link]

bservation by Comparing Traffic Statistics

For details, see Observation by Comparing Performance Counters.

bservation by Conducting a Fixed-Point or Mobile Test on a Single UE

For details, see Observation by Conducting a Fixed-Point or Mobile Test on a Single UE.

[Link] Possible Issues


The handling procedure is the same as that of single- and dual-stream beamforming. For details, see [Link] Possible Issues.

6 MU Beamforming

Table 6-1 MU beamforming feature overview

Feature Transmission Mode Antenna Port Number of Supported Data Transmit/Receive Mode of the
Streams RRU

TDLOFD-001077 MU- TM7, TM8, or TM9 Antenna port 5, 7, or 8 2, corresponding to two UEs 4T4R or 8T8R
Beamforming (known as 2-
layer MU beamforming)

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 25/56


12/15/2020 HedEx Startpage

Feature Transmission Mode Antenna Port Number of Supported Data Transmit/Receive Mode of the
Streams RRU

TDLOFD-110221 DL 4-Layer TM7, TM8, or TM9 Antenna port 5, 7, or 8 2 to 4, corresponding to two to 8T8R
MU Beamforming (including 4- four UEs
layer MU beamforming and
adaptive MU beamforming)

TDLOFD-130204 Advanced TM7, TM8, or TM9 Antenna port 5, 7, or 8 2 to 4, corresponding to two to At least one RRU
Multi-User Coordination four UEs equipped with four or
more antennas are
configured in D-MIMO
or SFN scenarios.
In other scenarios,
4T4R or 8T8R RRUs
are required.

Principles

6.1.1 Overview
MU beamforming enables an eNodeB to pair two to four UEs using the same OFDM time-frequency resource and to transmit one data stream to each UE. This improves the average
cell throughput. Figure 6-1 shows the principles of MU beamforming.
Figure 6-1 MU beamforming

If single- or dual-stream beamforming is enabled, the MuBfSwitch option of the [Link] parameter is selected, and the [Link]
parameter is set to TWO_LAYERS or FOUR_LAYERS, 2-layer or 4-layer MU beamforming can be enabled.
After MU beamforming is enabled, the eNodeB attempts to pair UEs in each transmission time interval (TTI). The eNodeB generates beamforming weights for data streams after
starting the UE pairing procedure. Then, the eNodeB imposes weight on data symbols and DMRS symbols for each data stream using the generated orthogonal weight values. The
eNodeB combines the weighted symbols and transmits them over the antenna ports. In this way, multiple data streams are transmitted in the downlink using the same time-frequency
resource, enhancing the downlink spectral efficiency.
When 2-layer MU beamforming is enabled, the eNodeB selects the UEs with high antenna channel correlations of the same UE and low radio channel correlations between UEs for
pairing due to the following reasons:

If antenna channels are highly correlated and dual-stream beamforming is used, data streams interfere with each other. In 2-layer MU beamforming mode, the UEs with low
UE channel correlations are paired. In this situation, spatial multiplexing gains are offered.
If antenna channels are lowly correlated, multiple data streams can be transmitted to a single UE and 2-layer MU beamforming offers lower gains than dual-stream
beamforming.

To improve the performance of MU beamforming, it is recommended that this function be used on a macro eNodeB equipped with eight antennas. 4-layer MU beamforming is
available only in 8T8R scenarios.

6.1.2 MU Beamforming Pairing Procedure


This section describes the MU beamforming pairing procedure, as shown in Figure 6-2.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 26/56


12/15/2020 HedEx Startpage
Figure 6-2 MU beamforming pairing procedure

[Link] 2-Layer MU Beamforming and 4-Layer MU Beamforming

iring Procedure

Within each TTI, the eNodeB selects UEs, pairs them, and schedules resources for them as follows.
Figure 6-3 UE pairing procedure

1. The eNodeB selects candidates UEs for MU beamforming pairing.


A UE can be selected as a candidate for MU beamforming pairing when both of the following conditions are met:
The UE works in TM7, TM8, or TM9 mode and has a CQI value greater than the internal threshold specified for MU beamforming pairing.
If the UE works in PMI feedback-dependent TM9 mode, the TM9MuBfSwitch option of the [Link] parameter is selected so that UEs can
be paired.

2. The eNodeB selects two candidate UEs for a pairing attempt.


The eNodeB selects the candidate UE with the highest spectral efficiency for layer-1 scheduling. Then, the eNodeB selects another UE whose pairing-related
counters (such as spectral efficiency improvement and UE channel correlation after UE pairing) reach the specified thresholds for layer-2 scheduling.
If the pairing-related counters do not meet the specified thresholds, the pairing fails. The eNodeB does not pair the two UEs.
The eNodeB pairs layer-3 and layer-4 UEs using the same method. The number of pairing layers must be less than or equal to the value of the
[Link] parameter.
UE pairing thresholds for MU beamforming can be adjusted using parameters. For details, see [Link] Data Preparation.

3. The eNodeB uses the same time-frequency resources to transmit data to both of the paired UEs.
Figure 6-4 uses 4-layer MU beamforming pairing as an example to illustrate the RBG allocation for paired UEs.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 27/56


12/15/2020 HedEx Startpage
Figure 6-4 UE pairing principles for 4-layer MU beamforming

heduling Optimization

Advanced multi-user coordination


Advanced multi-user coordination can be enabled based on TDLOFD-110221 DL 4-Layer MU-Beamforming to further improve the 4-layer pairing rate and downlink capacity
in heavy-load scenarios. Advanced multi-user coordination is controlled by the license for TDLOFD-130204 Advanced Multi-User Coordination.
To enable this function, select the MULTI_UE_COORDINATION_OPT_SW option of the [Link] parameter. If this function is enabled, the
eNodeB preferentially selects UEs with a large data volume at layers 2 to 4 for pairing, as shown in Figure 6-5 and Figure 6-6.
Figure 6-5 Data to be scheduled

Figure 6-6 UE pairing before and after advanced multi-user coordination is enabled

MU beamforming resource adjustment


When the downlink PRB usage is less than 100% and MU beamforming is enabled, the local cell adjusts its resources to mitigate its interference to neighboring cells or to
minimize the number of residual small packets generated during UE scheduling when two UEs are paired for MU beamforming.
MU beamforming resource adjustment can be enabled based on 2-layer or 4-layer MU beamforming. To enable this function, select the MubfResAdjSwitch option of the
[Link] parameter.
With the MU beamforming resource adjustment function, the local cell arranges free resource blocks (RBs) using MU beamforming pairing to minimize the number of resource
block groups (RBGs) when layer-1 or layer-2 RBGs are not fully used within a TTI. In this way, the PRB usage of the local cell decreases and interference to neighboring cells
is mitigated.

[Link] Adaptive MU Beamforming


Adaptive MU beamforming further improves capacity based on TDLOFD-110221 DL 4-Layer MU-Beamforming. The eNodeB triggers downlink spatial-domain-preferred MU
beamforming when the cell load reaches a preset threshold, improving the downlink user-perceived rate in 8T8R cells and downlink cell spectral efficiency.
If the [Link] parameter is set to a value other than 255, adaptive MU beamforming is enabled. It is recommended that heavy-load TMA boost be enabled when
adaptive MU beamforming is enabled. For details about heavy-load TMA boost, see 8.1 Heavy-Load TMA Boost.
Figure 6-7 UE pairing procedure

1. The eNodeB determines the cell load.


If the downlink PRB usage of the cell is greater than the value of the [Link] parameter, the eNodeB starts the spatial-domain-preferred MU
beamforming pairing procedure.
If the difference between the value of the [Link] parameter and the downlink PRB usage of the cell is within a certain range, the eNodeB exits the
spatial-domain-preferred MU beamforming pairing procedure.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 28/56


12/15/2020 HedEx Startpage
2. The eNodeB selects candidates UEs for MU beamforming pairing.
The eNodeB selects TM7, TM8, and TM9 UEs that meet both of the following conditions as candidate UEs:
The CQI value is greater than the value of the CellMimoParaCfg.MuPairingMcsThldForTm9 parameter.
The SRS SINR is greater than a preset threshold (specified by the [Link] parameter).

For PMI feedback-dependent TM9 UE or VoLTE UE pairing, the following requirements also must be met:
If the UEs work in PMI feedback-dependent TM9 mode, the TM9MuBfSwitch option of the [Link] parameter is selected.
For VoLTE UEs, the MU_PAIRING_VOLTE_SWITCH option of the [Link] parameter is selected.

3. The eNodeB selects two candidate UEs for a pairing attempt.


The eNodeB selects UEs whose correlation meets the threshold specified by the [Link] parameter among candidate UEs for pairing.
The maximum number of pairing layers is specified by the [Link] parameter.
4. The eNodeB uses the same time-frequency resources to transmit data to both of the paired UEs.
Figure 6-8 show how RBGs are allocated to paired UEs.

Figure 6-8 Adaptive MU beamforming pairing

Network Analysis

6.2.1 Benefits

ature Activation Suggestions

Table 6-2 Feature activation suggestions

Recommended MU Beamforming Function Prerequisites

2-layer MU beamforming The downlink PRB usage is greater than 50% in busy hours.
There are many active UEs in the downlink. At least two UEs are recommended.
The preceding conditions can be met more easily in WTTx scenarios.

4-layer MU beamforming/adaptive MU The downlink PRB usage is greater than 50% in busy hours.
beamforming Four or more UEs are active in the downlink.
The preceding conditions can be met more easily in WTTx scenarios.

The eNodeB enjoys better performance gains of MU beamforming if the following conditions are met:

Coverage area angle (directional antennas): The angle of the sector of the cell ranges from 100° to 140°.
Inter-site distance: The average inter-site distance is greater than 500 m and less than 2000 m.
UE distribution: UEs are evenly distributed.
Load: The downlink PRB usage reaches 80% or higher during busy hours in the deployment area.
Proportion of high-speed UEs: The proportion of high-speed UEs is less than 30%. High-speed UEs refer to those moving at a speed greater than 30 km/h.

NOTE:
The gains of MU beamforming are affected by interference, networking, UE distribution, and UE services and depend on live network conditions. For example:

If the proportion of dual-stream beamforming UEs in a cell is high (greater than 50%) before MU beamforming is enabled, MU beamforming produces fewer performance
gains.
MU beamforming produces more performance gains in a cell where UEs are evenly distributed than in a cell where UEs are centrally distributed. If UEs are not evenly
distributed, adjust the value of the [Link] parameter to optimize performance gains of MU beamforming.
MU beamforming produces more performance gains in a heavy-load cell than in a light-load cell.
MU beamforming produces more performance gains in a cell with less interference.

hievable Gains

For details, see Achievable Gains.

6.2.2 Impacts

twork Impacts

2-layer MU beamforming
This function enables an eNodeB to transmit two data streams using the same time-frequency resource, increasing the downlink cell throughput and spectral efficiency.
If beamforming is enabled and there are joint-scheduling UEs in an SFN cell, the phases of the signals received by UEs are random. This may compromise the gains
offered by beamforming, but system gains are still increased.
This function allows UEs making VoLTE video calls to participate in pairing, improving the capacity of cells serving such UEs. However, the bit error rate and
retransmission rate for downlink QCI 2 bearers increase slightly, and the packet loss rate of QCI 2 bearers may increase.

4-layer MU beamforming
This function increases the number of data streams and the downlink cell throughput and spectral efficiency.
MU beamforming resource adjustment mitigates interference of the local cell to neighboring cells and minimizes the number of residual small packets generated during
UE scheduling.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 29/56


12/15/2020 HedEx Startpage
If beamforming is enabled and there are joint-scheduling UEs in an SFN cell, the phases of the signals received by UEs are random. This may compromise the gains
offered by beamforming, but system gains are still increased.
This function allows UEs making VoLTE video calls to participate in pairing, improving the capacity of cells serving such UEs. However, the bit error rate and
retransmission rate for downlink QCI 2 bearers increase slightly, and the packet loss rate of QCI 2 bearers may increase.
Advanced multi-user coordination
This feature improves the spatial multiplexing gains. It also enhances the downlink cell throughput and spectral efficiency when the network load is heavy.

Adaptive MU beamforming
The eNodeB performs adaptive MU beamforming when the cell load reaches a preset threshold (the downlink PRB usage is greater than 50%) and UEs are evenly
distributed to improve the downlink user-perceived rate and spectral efficiency.
Adaptive MU beamforming increases the downlink MU beamforming pairing rate in a cell. Therefore, after this function is enabled, the average downlink MCS index
decreases. However, the increase in the MU beamforming pairing rate also leads to an increase in the RB reuse efficiency, which improves downlink cell performance.
The decrease in the average MCS index in a cell varies based on the MU beamforming pairing rate, interference, and UE distribution.
Adaptive MU beamforming increases the downlink MU beamforming pairing rate in a cell. Therefore, after this function is enabled, the downlink IBLER and downlink
RBLER may increase, and the PDCCH aggregation level increases.
If the network is heavily loaded, more uplink packets are sent due to an increase in the MU beamforming pairing rate and more frequent downlink scheduling. As a
result, the uplink PRB usage may increase, which may cause uplink resource insufficiency in the TTI and a decrease in the uplink user-perceived rate.
If the MU_PAIRING_VOLTE_SWITCH option of the [Link] parameter is selected, VoLTE UEs can be paired for MU beamforming and the
downlink user-perceived rate in the cell increases. However, the bit error proportion and retransmission proportion for downlink QCI 1 services in the cell slightly
increase, and the voice packet loss rate may increase.
This function allows UEs making VoLTE video calls to participate in pairing, improving the capacity of cells serving such UEs. However, the bit error rate and
retransmission rate for downlink QCI 2 bearers increase slightly, and the packet loss rate of QCI 2 bearers may increase.

NOTE:
The average downlink cell throughput is measured by Cell Downlink Average Throughput.
The downlink spectral efficiency is calculated using the following formula:
Average downlink throughput per PRB (bit/PRB) = [Link]/(60 x 60 x 800 x [Link])
The downlink user-perceived rate is calculated using the following formula:
Downlink user-perceived rate = ([Link] – [Link])/[Link]/1000

nction Impacts

The following table describes the function impacts of 2-layer MU beamforming.

Function Name Function Switch Reference Description

Uplink 2CC CA CaUl2CCSwitch option of the Carrier Aggregation The number of PRBs paired on each layer for
[Link] parameter MU beamforming may fluctuate by 5% or less
when uplink CA is enabled and the
Dl2CCAckResShareSw option of the
[Link] parameter is
selected.
The PCC supports beamforming. The support
of SCCs for beamforming is as follows:
If uplink CA is enabled, the uplink SCC
supports beamforming.
If uplink CA is not enabled and
beamforming in SCells has been
enabled, the SCC supports single- and
dual-stream beamforming. In this case,
however, the SCC does not support
long-SRS-period beamforming or MU
beamforming.
If neither uplink CA nor beamforming in
SCells is enabled, the SCC does not
support beamforming.

Dynamic power sharing LTE_DYN_POWER_SHARING_SW option of the Dynamic Power Sharing When multiple UEs are paired, the power used to
between LTE carriers [Link] Between LTE Carriers transmit each piece of data is reduced because
(LTE TDD) parameter multiple pieces of data share the same resource.
When power sharing is enabled, the power of each
piece of data increases and positive gains can be
obtained.

Preferential use of [Link] Scheduling If 2-layer MU beamforming is enabled and the


resource allocation type [Link] parameter is set to
1 ADAPTIVE or TYPE1_FIRST, the eNodeB
preferentially uses resource allocation type 1 based on
the conditions for the ADAPTIVE or TYPE1_FIRST
policy to take effect.
UEs that have been allocated resources using
resource allocation type 1 cannot be scheduled for MU
beamforming pairing.

DL CoMP IntraDlCompSwitch, InterDlCompDcsSwitch, DL CoMP (TDD) If DL CoMP is enabled, DL CoMP UEs cannot be
and InterDlCompCbfSwitch options of the paired and as a result the proportion of paired MU
[Link] parameter beamforming UEs may decrease.

Downlink D-MIMO DmimoJTSwitch option of the D-MIMO (TDD) When D-MIMO is enabled, multi-user spatial
[Link] parameter multiplexing is implemented in a D-MIMO way, and the
performance counters and performance monitoring
items related to MU beamforming are no longer
measured.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 30/56


12/15/2020 HedEx Startpage

Function Name Function Switch Reference Description

Inter-frequency split None Soft Split Resource Duplex MU beamforming cannot take effect if soft split is
(TDD) enabled.

Intra-frequency split None Soft Split Resource Duplex MU beamforming cannot take effect if soft split is
(TDD) enabled.

The following table describes the function impacts of 4-layer MU beamforming.

Function Name Function Switch Reference Description

Uplink 2CC CA CaUl2CCSwitch option of the Carrier Aggregation The number of PRBs paired on each layer for MU
[Link] beamforming may fluctuate by 5% or less when uplink
parameter CA is enabled and the Dl2CCAckResShareSw option
of the [Link] parameter is
selected.
The PCC supports beamforming. The support of
SCCs for beamforming is as follows:
If uplink CA is enabled, the uplink SCC
supports beamforming.
If uplink CA is not enabled and beamforming in
SCells has been enabled, the SCC supports
single- and dual-stream beamforming. In this
case, however, the SCC does not support
long-SRS-period beamforming or MU
beamforming.
If neither uplink CA nor beamforming in SCells
is enabled, the SCC does not support
beamforming.

Function impacts of advanced multi-user coordination:


None
The following table describes the function impacts of adaptive MU beamforming.

Function Name Function Switch Reference Description

Inter-frequency split None Soft Split Resource Duplex (TDD) MU beamforming cannot take effect if soft split is enabled.

Intra-frequency split None Soft Split Resource Duplex (TDD) MU beamforming cannot take effect if soft split is enabled.

Uplink 2CC CA CaUl2CCSwitch option of the Carrier Aggregation The number of PRBs paired on each layer for MU
[Link] beamforming may fluctuate by 5% or less when uplink
parameter CA is enabled and the Dl2CCAckResShareSw option
of the [Link] parameter is
selected.
The PCC supports beamforming. The support of
SCCs for beamforming is as follows:
If uplink CA is enabled, the uplink SCC
supports beamforming.
If uplink CA is not enabled and beamforming in
SCells has been enabled, the SCC supports
single- and dual-stream beamforming. In this
case, however, the SCC does not support
long-SRS-period beamforming or MU
beamforming.
If neither uplink CA nor beamforming in SCells
is enabled, the SCC does not support
beamforming.

Requirements

6.3.1 Licenses
The following licenses must be purchased for 2-layer MU beamforming (TDLOFD-001077 MU Beamforming).

Feature ID Feature Name Model Sales Unit

TDLOFD-001077 MU-Beamforming LT1STMUBMF00 per Cell

The following licenses must be purchased for 4-layer MU beamforming or adaptive MU beamforming (TDLOFD-110221 DL 4-Layer MU-Beamforming).

Feature ID Feature Name Model Sales Unit

TDLOFD-001077 MU-Beamforming LT1STMUBMF00 per Cell

TDLOFD-110221 DL 4-Layer MU-Beamforming LT1SDL4LMB00 per Cell

The following licenses must be purchased for advanced multi-user coordination (TDLOFD-130204 Advanced Multi-User Coordination).

Feature ID Feature Name Model Sales Unit

TDLOFD-001077 MU-Beamforming LT1STMUBMF00 per Cell

TDLOFD-110221 DL 4-Layer MU-Beamforming LT1SDL4LMB00 per Cell

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 31/56


12/15/2020 HedEx Startpage

Feature ID Feature Name Model Sales Unit

TDLOFD-130204 Advanced Multi-User LT1SAVMUCD00 per Cell


Coordination

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

erequisite Functions

The following table describes the prerequisite functions of 2-layer MU beamforming.

Function Name Function Switch Reference Description

Single-stream beamforming BfSwitch option under the Beamforming (TDD) Single-stream beamforming is required if single-stream
[Link] beamforming UEs are to be paired.
parameter

Dual-stream beamforming BfSwitch option under the Beamforming (TDD) Dual-stream beamforming is required if dual-stream
[Link] beamforming UEs are to be paired.
parameter
[Link] set to
DUAL_LAYER_BF

Downlink 2-layer MIMO TM9Switch option under the Beamforming (TDD) Downlink 2-layer MIMO based on TM9 is required if
based on TM9 [Link] TM9 UEs are to be paired.
parameter

The following table describes the prerequisite functions of 4-layer MU beamforming.

Function Name Function Switch Reference

2-layer MU beamforming MuBfSwitch option under the Beamforming (TDD)


[Link] parameter

The following table describes the prerequisite functions of advanced multi-user coordination.

Function Name Function Switch Reference

Single-stream beamforming BfSwitch option under the Beamforming (TDD)


[Link] parameter

Dual-stream beamforming BfSwitch option under the Beamforming (TDD)


[Link]
parameter
[Link] set to
DUAL_LAYER_BF

4-layer MU beamforming MuBfSwitch option under the Beamforming (TDD)


[Link] parameter
FOUR_LAYERS option under the
[Link] parameter

Downlink D-MIMO DmimoJTSwitch option under the D-MIMO (TDD)


[Link] parameter

The following table describes the prerequisite function of adaptive MU beamforming.

Function Name Function Switch Reference

2-layer MU beamforming MuBfSwitch option under the Beamforming (TDD)


[Link] parameter

utually Exclusive Functions

The following table describes the mutually exclusive functions of 2-layer MU beamforming.

Function Name Function Switch Reference

High speed mobility [Link] High Speed Mobility

Extended cyclic prefix [Link] Extended CP

[Link]

The following table describes the mutually exclusive functions of 4-layer MU beamforming.

Function Name Function Switch Reference

Downlink frequency selective scheduling FreqSelSwitch option under the Scheduling


[Link] parameter

Mutually exclusive functions of advanced multi-user coordination: None


The following table describes the mutually exclusive functions of adaptive MU beamforming.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 32/56


12/15/2020 HedEx Startpage

Function Name Function Switch Reference

SFN [Link] SFN

Downlink D-MIMO DmimoJTSwitch option under the D-MIMO (TDD)


[Link] parameter

Inter-cell downlink D-MIMO InterCellDmimoJTSwitch option under the D-MIMO (TDD)


[Link] parameter

6.3.3 Hardware

se Station Models

The following base stations are compatible with this function:

3900 and 5900 series base stations


DBS3900 LampSite and DBS5900 LampSite: TDLOFD-130204 Advanced Multi-User Coordination is suitable for LampSite eNodeBs on which downlink D-MIMO is enabled.

oards

Function Name BBP Model

2-layer MU beamforming UBBPg2, UBBPg2a, UBBPg3, UBBPei, UBBPe, UBBPd, UMDU, or LBBPd

4-layer MU beamforming UBBPg2, UBBPg2a, UBBPg3, UBBPei, UBBPe, UBBPd, or UMDU

Advanced multi-user coordination UBBPg2, UBBPg2a, UBBPg3, UBBPei, UBBPe, UBBPd, or UMDU

Adaptive MU beamforming UBBPg2, UBBPg2a, UBBPg3, UBBPd6, UBBPd9, UBBPe4, UBBPe6, or UBBPei

Table 6-3 lists the requirements for the number of cells in adaptive MU beamforming. If the number of cells set up on a UBBPg2, UBBPg2a, or UBBPg3 exceeds the maximum
number of cells supported by adaptive MU beamforming, the eNodeB rolls back adaptive MU beamforming to 4-layer MU beamforming.

Table 6-3 Requirements for the number of cells in adaptive MU beamforming

BBP Maximum Number of Cells Supported by Adaptive MU Beamforming

UBBPd6/UBBPd9 3 cells

UBBPe4 3 cells

UBBPe6/UBBPei 6 cells

UBBPg2/UBBPg2a 6 cells

UBBPg3 12 cells

When the BBU is configured with the UBBPg2, UBBPg2a, or UBBPg3 and the following requirements are met, the number of cells established on the UBBPg2, UBBPg2a, or
UBBPg3 will not exceed the maximum number of cells supported by adaptive MU beamforming.

Total number of TDD cells established on the BBU ≤ Sum of the maximum number of cells supported by each baseband processing unit (supporting adaptive MU
beamforming) + Number of cells supported by each baseband processing unit (not supporting adaptive MU beamforming)
For the UBBPg2, UBBPg2a, or UBBPg3, the ADD EUCELLSECTOREQM command is used to bind the sector equipment and baseband equipment.
To bind the sector equipment and baseband equipment is to specify the sector equipment and baseband equipment used by a cell. For details, see Cell Management.
[Link] is set to ON.

NOTE:
For the LBBPd, the [Link] parameter must be set to TDD_ENHANCE in 4T4R scenarios and to TDD_8T8R in 8T8R scenarios.

After 4-layer MU beamforming is enabled and the corresponding license is purchased, if the LBBPd is used, 4-layer MU beamforming cannot take effect and 2-layer MU
beamforming takes effect instead.
Adaptive MU beamforming applies to BBPs working only in LTE TDD mode. (The [Link] parameter is set to LTE_TDD.)
Adaptive MU beamforming only applies to scenarios where the primary BBP and serving BBP are the same BBP. (You can run the DSP CELL command to query the
information about the primary BBP and serving BBP.)

F Modules

Function Name RRU or Antenna Type

2-layer MU beamforming 4T4R or 8T8R RRUs

4-layer MU beamforming 8T8R RRUs

Advanced multi-user coordination At least one RRU equipped with four or more antennas are configured in
D-MIMO or SFN scenarios.
In other scenarios, 4T4R or 8T8R RRUs are required.

Adaptive MU beamforming 8T8R

NOTE:
Beamforming is not supported when the RRU3278 is split into two 4T4R RRUs.
The maximum transmit power of an RRU and the number of CRS ports also need to be collected in network reconstruction scenarios before feature deployment.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 33/56


12/15/2020 HedEx Startpage
lls

The requirements are the same as those of single- and dual-stream beamforming. For details, see Cells.

6.3.4 Others

Es

Both of the following UE conditions are met:

The UE complies with 3GPP Release 8 or later.


The UE has at least two receive antennas.

Operation and Maintenance

6.4.1 Data Configuration

[Link] Data Preparation

rameters Used for Activation

2-layer MU beamforming requires the following MOs and parameters.

Table 6-4 Parameters that must be set in the CellAlgoSwitch MO

Parameter Name Parameter ID Option Setting Notes

MUBF Algorithm Switch [Link] MuBfSwitch Select this option.

[Link] MubfResAdjSwitch Select this option.

[Link] TM9MuBfSwitch This option is deselected by default. Select this option if UEs
working in PMI feedback-dependent TM9 are to be paired.

BF algorithm switch [Link] BfSwitch Select this option.

[Link] LongSrsPeriodBfSwitch You are advised to select this option.

Table 6-5 Parameters in the CellBf MO

Parameter Name Parameter ID Setting Notes

Max Number of MUBF Layers [Link] Set this parameter to TWO_LAYERS.

MUBF Pairing Rule [Link] It is recommended that this parameter be set to POST_MU_PF_PRI_PAIR_RULE.
Set this parameter to POST_MU_EFF_PRI_PAIR_RULE only in testing scenarios.

Port Allocation Avoid for [Link] In eRAN TDD 12.0 or later, set this parameter to USERIDENTIFY to prevent the
Continuous NACK UEs service drop rate of abnormal UEs from increasing when both dual-stream
beamforming and MU beamforming are enabled.
Set this parameter to USERIDENTIFYRANK2PAIRING when abnormal UEs in dual-
stream beamforming mode are to be paired for MU beamforming or D-MIMO.

4-layer MU beamforming requires the following MOs and parameters.

Table 6-6 Parameters that must be set in the CellAlgoSwitch MO

Parameter Name Parameter ID Option Setting Notes

MUBF Algorithm Switch [Link] MuBfSwitch Select this option.

[Link] MubfResAdjSwitch Select this option.

[Link] TM9MuBfSwitch This option is deselected by default. Select this option if UEs
working in PMI feedback-dependent TM9 are to be paired.

Harq Algorithm Switch [Link] TddAckFbModeCfgOptSwitch If 4-layer MU beamforming is required at uplink-downlink


subframe configuration 2, it is recommended that this option
be selected to enable downlink HARQ feedback mode
adaptation. The setting shortens the time within which the
throughput peaks after more than two UEs are paired for 4-
layer MU beamforming.
For details about the impact of selecting this option on
network performance, see Scheduling.

BF algorithm switch [Link] BfSwitch Select this option.

[Link] LongSrsPeriodBfSwitch You are advised to select this option.

Table 6-7 Parameters in the CellBf MO

Parameter Name Parameter ID Setting Notes

Max Number of MUBF Layers [Link] Set this parameter to FOUR_LAYERS.

MUBF Pairing Rule [Link] It is recommended that this parameter be set to POST_MU_PF_PRI_PAIR_RULE.
Set this parameter to POST_MU_EFF_PRI_PAIR_RULE only in testing scenarios.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 34/56


12/15/2020 HedEx Startpage

Parameter Name Parameter ID Setting Notes

Port Allocation Avoid for [Link] In eRAN TDD 12.0 or later, set this parameter to USERIDENTIFY to prevent the
Continuous NACK UEs service drop rate of abnormal UEs from increasing when both dual-stream
beamforming and MU beamforming are enabled.
Set this parameter to USERIDENTIFYRANK2PAIRING when abnormal UEs in dual-
stream beamforming are to be paired for MU beamforming or D-MIMO.

Adaptive MU beamforming requires the following MOs and parameters.

Table 6-8 Parameters that must be set in the CellAlgoSwitch MO

Parameter Name Parameter ID Option Setting Notes

MUBF Algorithm Switch [Link] MuBfSwitch Select this option.

[Link] TM9MuBfSwitch This option is deselected by default. Select this option if UEs
working in PMI feedback-dependent TM9 are to be paired.

Harq Algorithm Switch [Link] TddAckFbModeCfgOptSwitch If adaptive MU beamforming is required at uplink-downlink


subframe configuration 2, it is recommended that this option
be selected to enable downlink HARQ feedback mode
adaptation. The setting shortens the time within which the
throughput peaks after more than two UEs are paired for
adaptive MU beamforming.
For details about the impact of selecting this option on
network performance, see Scheduling.

BF algorithm switch [Link] BfSwitch Select this option.

[Link] LongSrsPeriodBfSwitch You are advised to select this option.

Table 6-9 Parameters in the CellBf MO

Parameter Name Parameter ID Setting Notes

Max Number of MUBF Layers [Link] Set this parameter to FOUR_LAYERS.

MUBF Pairing Rule [Link] It is recommended that this parameter be set to POST_MU_PF_PRI_PAIR_RULE.
Set this parameter to POST_MU_EFF_PRI_PAIR_RULE only in testing scenarios.

Port Allocation Avoid for [Link] In eRAN TDD 12.0 or later, set this parameter to USERIDENTIFY to prevent the
Continuous NACK UEs service drop rate of abnormal UEs from increasing when both dual-stream
beamforming and MU beamforming are enabled.
Set this parameter to USERIDENTIFYRANK2PAIRING when abnormal UEs in dual-
stream beamforming are to be paired for MU beamforming or D-MIMO.

Adaptive MUBF Start [Link] Set this parameter to its recommended value.
Threshold

Table 6-10 Parameter in the CellMLB MO

Parameter Name Parameter ID Setting Notes

MU-MIMO PRB Statistic [Link] Set this parameter to ON.


Optimization Switch

Table 6-11 Parameter in the CellMMAlgo MO

Parameter Name Parameter ID Option Setting Notes

Massive MIMO Algorithm [Link] MU_PAIRING_VOLTE_SWITCH If VoLTE UEs need to be paired, select this option.
Optimization Switch Recommended configurations are as follows:
If there are a large number of VoLTE UEs, it is
recommended that this option be selected to allow
VoLTE UEs to be paired for MU beamforming.
If there are few VoLTE UEs, deselect this option so
that VoLTE UEs cannot be paired for MU
beamforming.
If VoLTE UEs do not participate in MU beamforming pairing:
The impact of interference between paired UEs on
the PDSCH BLER decreases.
The downlink voice packet loss rate in the cell
decreases.
In heavy-load scenarios, the downlink traffic volume
(value of the [Link] counter) decreases.

rameters Used for Optimization

UE pairing for MU beamforming is successful when the spectral efficiency after the UE pairing exceeds a preset threshold. This threshold can be adjusted using the following
parameters to control the number of successfully paired UEs.
Table 6-12 Parameter optimization for 2-layer MU beamforming pairing

Parameter Name Parameter ID Option Setting Notes

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 35/56


12/15/2020 HedEx Startpage

Parameter Name Parameter ID Option Setting Notes

BF to Two Layer MUBF CellBfMimoParaCfg.BfTo2LayerMubfThdOffset None A small value increases the possibility of UE pairing.
Threshold Offset Use the recommended value.

Multi-Layer Pairing Isolation [Link] None The value 444 is recommended.


Threshold

Uplink schedule switch [Link] PuschDtxSwitch Deselect this option.


If this option is selected, the PDCCH module is affected,
and MU beamforming performance deteriorates.

[Link] UlRaUserSchOptSw If this option is selected, cell access performance can be


improved when the proportion of UEs paired for MU
beamforming is high.

Table 6-13 Parameter optimization for 4-layer MU beamforming pairing

Parameter Name Parameter ID Option Setting Notes

BF to Four Layer MUBF CellBfMimoParaCfg.BfTo4LayerMubfThdOffset None A small value increases the possibility of UE
Threshold Offset pairing.
Use the recommended value.

Multi-Layer Pairing [Link] None A smaller value of this parameter leads to a


Isolation Threshold higher probability that UEs meet the pairing
conditions and allows UEs with low isolation to
be paired. However, the throughput may
decrease after pairing.
A larger value of this parameter leads to a lower
probability that UEs meet the pairing conditions
and allows only UEs with high isolation to be
paired. This avoids the risk of throughput
decrease after pairing. However, the multi-layer
pairing rate of the network decreases and
optimal performance cannot be achieved.
The recommended initial value of this parameter
is 466.
It is recommended that this parameter be
optimized as follows based on UE distributions in
a cell:
If UEs are sparsely distributed in a cell, a
small value is recommended, for
example, 444 or 344.
If UEs are centrally distributed in a cell, a
large value is recommended, for
example, 466 or 477.
If UEs are highly centrally distributed in a
cell, a large value is recommended, for
example, 488 or 499.
For a cell covering scenarios such as
traffic intersections and high-rack bridges,
where there are many moving UEs, it is
recommended that this parameter be set
to a large value, for example, 477, 577,
499, or 599.

Coordination Algorithm [Link] MULTI_UE_COORDINATION_OPT_SW It is recommended that this option be selected to


Switch improve the 4-layer MU beamforming pairing
rate and downlink throughput.

CQI Adjust Algorithm [Link] StepVarySwitch Deselect this option.


Switch If this option is selected, MU beamforming
performance deteriorates.

[Link] DlVarIBLERtargetSwitch Deselect this option.


If this option is selected, MU beamforming
performance deteriorates.

[Link] AdaptiveStepVarySwitch Deselect this option.


If this option is selected, MU beamforming
performance deteriorates.

[Link] DlEnVarIblerTargetSwitch Deselect this option.


If this option is selected, MU beamforming
performance deteriorates.

Uplink schedule switch [Link] PuschDtxSwitch Deselect this option.


If this option is selected, the PDCCH module is
affected, and MU beamforming performance
deteriorates.

[Link] UlRaUserSchOptSw If this option is selected, cell access


performance can be improved when the
proportion of UEs paired for MU beamforming is
high.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 36/56


12/15/2020 HedEx Startpage
Table 6-14 Pairing parameter optimization for adaptive MU beamforming

Parameter Name Parameter ID Option Setting Notes

MU Pairing TBS CellMimoParaCfg.MuPairingMcsThldForTm9 None A smaller value of this parameter leads to


Index Threshold a higher probability of meeting the
candidate UE pairing conditions for MU
beamforming. However, if the MCS index
is small, the throughput gain is not
obvious after pairing.
The value 8 is recommended.

MUBF SINR Thld [Link] None A smaller value of this parameter leads to
Ofs Before SRS a higher probability of meeting the
Balance candidate UE pairing conditions for MU
beamforming. However, if the SRS SINR
is small, the throughput gain is not
obvious after pairing.
Use the recommended value.

BF to Two Layer CellBfMimoParaCfg.BfTo2LayerMubfThdOffset None A small value increases the possibility of


MUBF Threshold UE pairing.
Offset Use the recommended value.

BF to Four Layer CellBfMimoParaCfg.BfTo4LayerMubfThdOffset None A small value increases the possibility of


MUBF Threshold UE pairing.
Offset The value –500 is recommended.

Multi-Layer Pairing [Link] None A smaller value of this parameter leads to


Isolation Threshold a higher probability that UEs meet the
pairing conditions and allows UEs with
low isolation to be paired. However, the
throughput may decrease after pairing.
A larger value of this parameter leads to a
lower probability that UEs meet the
pairing conditions and allows only UEs
with high isolation to be paired. This
avoids the risk of throughput decrease
after pairing. However, the multi-layer
pairing rate of the network decreases and
optimal performance cannot be achieved.
The recommended initial value of this
parameter is 466.
It is recommended that this parameter be
optimized as follows based on UE
distributions in a cell:
If UEs are sparsely distributed in a
cell, a small value is
recommended, for example, 444
or 344.
If UEs are centrally distributed in a
cell, a large value is
recommended, for example, 466
or 477.
If UEs are highly centrally
distributed in a cell, a large value
is recommended, for example, 488
or 499.
For a cell covering scenarios such
as traffic intersections and high-
rack bridges, where there are
many moving UEs, it is
recommended that this parameter
be set to a large value, for
example, 477, 577, 499, or 599.

BfMimo Algorithm [Link] BFMIMOADAPTATIONOPTSW Select this option.


Optimization Switch
[Link] HEAVYLOADTRANSMODEADAPTBOOSTSW Deselect this option.

Heavy Load Average [Link] None It is recommended that this parameter be


UE Count Threshold set to 20.

Heavy Load [Link] None Set this parameter to its recommended


Downlink PRB value.
Usage Threshold

Heavy Load Target [Link] None Set this parameter to its recommended
Trans Mode value.

Heavy Load Trans [Link] None It is recommended that this parameter be


Mode Evaluation set to 6.
Period

CQI Adjust Algorithm [Link] StepVarySwitch Deselect this option.


Switch If this option is selected, MU beamforming
performance deteriorates.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 37/56


12/15/2020 HedEx Startpage

Parameter Name Parameter ID Option Setting Notes

[Link] DlVarIBLERtargetSwitch Deselect this option.


If this option is selected, MU beamforming
performance deteriorates.

[Link] AdaptiveStepVarySwitch Deselect this option.


If this option is selected, MU beamforming
performance deteriorates.

[Link] DlEnVarIblerTargetSwitch Deselect this option.


If this option is selected, MU beamforming
performance deteriorates.

[Link] CfiConvertWiDrsSwitch Select this option.


If this option is selected, MU beamforming
performance can be further improved.

[Link] TddBundlingCqiAdjOptSwitch Select this option.


If this option is selected, MU beamforming
performance can be further improved.

[Link] CqiAdjTimeEffSwitch Select this option.


If this option is selected, MU beamforming
performance can be further improved.

[Link] RptCqiFltInitSwitch Select this option.


If this option is selected, MU beamforming
performance can be further improved.

[Link] UeSigInitCqiModSwitch Select this option.


If this option is selected, MU beamforming
performance can be further improved.

[Link] CqiFastCompstSwitch Select this option.


If this option is selected, MU beamforming
performance can be further improved.

Uplink schedule [Link] PuschDtxSwitch Deselect this option.


switch If this option is selected, the PDCCH
module is affected, and MU beamforming
performance deteriorates.

[Link] UlRaUserSchOptSw If this option is selected, cell access


performance can be improved when the
proportion of UEs paired for MU
beamforming is high.

Initial Downlink [Link] None It is recommended that this parameter be


IBLER Target set to 15.

CQI Adjust Step [Link] None It is recommended that this parameter be


set to 50.

Cell CQI Adjustment [Link] None It is recommended that this parameter be


Sample Selection set to 50 to further improve MU
Thld beamforming performance.

[Link] Using MML Commands

tivation Command Examples

Perform the following operations to enable 2-layer MU beamforming.


//Enabling 2-layer MU beamforming
MOD CELLALGOSWITCH: LOCALCELLID=0, BFALGOSWITCH=BfSwitch-1&LongSrsPeriodBfSwitch-1, MUBFALGOSWITCH=MUBFSWITCH-1& MUBFRESADJSWITCH-1, UlSchSwit
MOD CELLBF: LOCALCELLID=0, HighOrderMubfMaxLayer=TWO_LAYERS, QualUEPortAvoidMode=USERIDENTIFY;
//Configuring the isolation threshold for triggering multi-layer pairing
MOD CELLBFMIMOPARACFG: LOCALCELLID=0, MultiLayerPairIsoThd=444;
Perform the following operations to enable 4-layer MU beamforming.
//Enabling 4-layer MU beamforming
MOD CELLALGOSWITCH: LOCALCELLID=0, BFALGOSWITCH=BfSwitch-1&LongSrsPeriodBfSwitch-1, MUBFALGOSWITCH=MUBFSWITCH-1&MUBFRESADJSWITCH-1, HarqAlgoSw
MOD CELLBF: LOCALCELLID=0, HighOrderMubfMaxLayer=FOUR_LAYERS, QualUEPortAvoidMode=USERIDENTIFY;
MOD CELLBFMIMOPARACFG: LOCALCELLID=0, MultiLayerPairIsoThd=466;
//Disabling the StepVarySwitch, DlVarIBLERtargetSwitch, AdaptiveStepVarySwitch, and DlEnVarIblerTargetSwitch options of the CQIADJALGOSWITCH p
MOD CELLALGOSWITCH: LocalCellId=0,CQIADJALGOSWITCH=StepVarySwitch-0&DlVarIBLERtargetSwitch-0&AdaptiveStepVarySwitch-0&DlEnVarIblerTargetSwitch
Perform the following operations to enable adaptive MU beamforming:
//Enabling adaptive MU beamforming
MOD CELLALGOSWITCH: LOCALCELLID=0, BFALGOSWITCH=BfSwitch-1&LongSrsPeriodBfSwitch-1, MUBFALGOSWITCH=MUBFSWITCH-1&HarqRetranPairSwitch-1, HarqAl
MOD CELLBF: LOCALCELLID=0, HighOrderMubfMaxLayer=FOUR_LAYERS, AdaptMubfStartThld=50, QualUEPortAvoidMode=USERIDENTIFY;
MOD CELLMIMOPARACFG: LOCALCELLID=0, MuPairingMcsThldForTm9=8;
MOD CELLBFMIMOPARACFG: LOCALCELLID=0, MultiLayerPairIsoThd=466, BfTo4LayerMubfThdOffset=-500;
MOD CELLMMALGO: LOCALCELLID=0, MubfSinrThldOfsBefSrsBal=0;
MOD CELLCQIADJALGO: LocalCellId=0, CellDeltaCqiSampSelThd=50;
MOD CELLMLB: LOCALCELLID=0, MuMimoPrbStatOptSwitch=ON;
//Enabling heavy-load TMA boost when adaptive MU beamforming is enabled to improve MU beamforming performance
MOD CELLBFMIMOPARACFG: LOCALCELLID=0, BfMimoAlgoOptSwitch= HEAVYLOADTRANSMODEADAPTBOOSTSW-1&HISTORICALSPECTRALEFFOPTSW-0&BFMIMOADAPWITHOUTTM8-
//Disabling the StepVarySwitch, DlVarIBLERtargetSwitch, AdaptiveStepVarySwitch, and DlEnVarIblerTargetSwitch options of the CQIADJALGOSWITCH p
MOD CELLALGOSWITCH: LocalCellId=0,CQIADJALGOSWITCH=StepVarySwitch-0&DlVarIBLERtargetSwitch-0&AdaptiveStepVarySwitch-0&DlEnVarIblerTargetSwitch
//(Optional) Selecting optimization options of the CQIADJALGOSWITCH parameter to further improve MU beamforming performance
MOD CELLALGOSWITCH: LocalCellId=0,CQIADJALGOSWITCH=TddBundlingCqiAdjOptSwitch-1&CqiAdjTimeEffSwitch-1&RptCqiFltInitSwitch-1&UeSigInitCqiModSwi

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 38/56


12/15/2020 HedEx Startpage
//(Optional) Set the CQI adjustment baseline step and the initial downlink IBLER target to further improve MU beamforming performance
MOD CellCqiAdjAlgo: LocalCellId=0, InitDlIblerTarget=15, CqiAdjStep=50;

activation Command Examples

Perform the following operations to disable 2-layer MU beamforming or 4-layer MU beamforming:


//Disabling MU beamforming when the MULTI_UE_COORDINATION_OPT_SW option is selected
MOD CELLALGOSWITCH: LOCALCELLID=0, MUBFALGOSWITCH=MUBFSWITCH-0&MUBFRESADJSWITCH-0, CoordinationAlgoSwitch=MULTI_UE_COORDINATION_OPT_SW-0;
//Disabling MU beamforming when the MULTI_UE_COORDINATION_OPT_SW option is deselected
MOD CELLALGOSWITCH: LOCALCELLID=0, MUBFALGOSWITCH=MUBFSWITCH-0&MUBFRESADJSWITCH-0;
Perform the following operations to disable adaptive MU beamforming.
//Disabling adaptive MU beamforming
MOD CELLBFMIMOPARACFG: LOCALCELLID=0, BfMimoAlgoOptSwitch= HEAVYLOADTRANSMODEADAPTBOOSTSW-0;
MOD CELLBF: LOCALCELLID=0, AdaptMubfStartThld=255;
MOD CELLALGOSWITCH: LOCALCELLID=0, MUBFALGOSWITCH=MUBFSWITCH-0;

[Link] Using the CME


For detailed operations, see CME-based Feature Configuration.

6.4.2 Activation Verification


To verify MU beamforming, perform the following operations:

1. Perform downlink services on four or more UEs compliant with 3GPP Release 8 or later. It is recommended that the UEs reside at different positions.
2. Perform signaling tracing on the OSS. For details, see Signaling Tracing for MU Beamforming. If the tracing result shows that UEs or RBs are successfully paired, MU
beamforming has taken effect.

6.4.3 Network Monitoring

ounter-based Monitoring

Monitor resource usages in different transmission modes based on the following counters.

Counter ID Counter Name

1526739777 [Link]

1526739778 [Link]

1526739779 [Link]

1526739780 [Link]

1526745707 [Link]

bservation by Comparing Traffic Statistics

For details, see Observation by Comparing Performance Counters.

gnaling Tracing for MU Beamforming

Monitor UE pairing results of a cell in MU beamforming mode as follows:

1. On the OSS client, choose Monitor > Signaling Trace > Signaling Trace Management. The Signaling Trace Management page is displayed.
2. From the navigation tree of the Signaling Trace Management page, choose Trace Type > LTE > Cell Performance Monitoring, and double-click Multi-User BF (Cell)
Monitoring. The Multi-User BF (Cell) Monitoring dialog box is displayed.
If adaptive MU beamforming is enabled for the cell (the [Link] parameter is not set to 255), select Non-Massive MIMO Adaptive MUBF Pair.
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.
4. In the displayed dialog box, enter the local cell ID in the Local Cell ID text box, and click Finish. The OSS starts the tracing task.
5. On the Signaling Trace Management page, double-click the tracing 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.

Monitor the number of RBs that are successfully paired for MU beamforming as follows:

1. On the OSS client, choose Monitor > Signaling Trace > Signaling Trace Management. The Signaling Trace Management page is displayed.
2. From the navigation tree of the Signaling Trace Management page, choose Trace Type > LTE > User Performance Monitoring, and double-click Multi-User BF (User)
Monitoring. The Multi-User BF (User) Monitoring dialog box is displayed.
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.
4. In the displayed dialog box, enter the values in the MMEc and mTMSI text boxes, and click Finish. The OSS starts the tracing task.
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.

bservation by Conducting a Fixed-Point or Mobile Test on a Single UE

For details, see Observation by Conducting a Fixed-Point or Mobile Test on a Single UE.

7 UE-level TMA

This function enables the eNodeB to select an appropriate transmission mode for each UE based on channel quality so that the optimal UE-level performance can be delivered.

Adaptive Switching Between Single- and Dual-Stream Beamforming

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 39/56


12/15/2020 HedEx Startpage
If dual-stream beamforming is enabled for the UEs compliant with 3GPP Release 9 or later, the eNodeB adaptively performs single- or dual-stream beamforming based on radio
channel conditions. Figure 7-1 shows the switching between single- and dual-stream beamforming.

Single-stream beamforming applies when the SINR is lower than the switching threshold.
Dual-stream beamforming applies when the SINR is greater than the switching threshold.

The threshold for triggering the switching between single- and dual-stream beamforming is specified by the [Link] parameter. For details, see
[Link].1 Scenario A: Adaptive Switching Between Single- or Dual-Stream Beamforming and MIMO.

Figure 7-1 Switching between single- and dual-stream beamforming

Adaptive Switching Between Single-Stream, Dual-Stream, and MU Beamforming

aptive Switching Between Single-Stream Beamforming and MU Beamforming

If single-stream beamforming and MU beamforming are enabled, the eNodeB can perform adaptive switching between the two transmission modes based on radio conditions.
During the adaptive switching, the eNodeB selects two appropriate single-stream beamforming UEs for pairing based on radio channel conditions.
Compared with single-stream beamforming, adaptive switching between single-stream beamforming and MU beamforming obviously increases the average cell throughput.

aptive Switching Between Single-Stream, Dual-Stream, and MU Beamforming

If single-stream, dual-stream, and MU beamforming are enabled, the eNodeB can perform adaptive switching between them based on radio channel conditions.
During the adaptive switching, the eNodeB adaptively performs single- or dual-stream beamforming based on radio channel conditions, and then selects single-stream beamforming
UEs or dual-stream beamforming UEs for MU beamforming pairing. For details, see Figure 7-2.
Adaptive switching between single-stream, dual-stream, and MU beamforming increases the average cell throughput.

Figure 7-2 Adaptive switching between single-stream, dual-stream, and MU beamforming

Adaptive Switching Between Beamforming and MIMO


Adaptive switching between beamforming and MIMO enables UEs to always select a transmission mode with the highest spectral efficiency under the same channel conditions.
Compared with beamforming and MIMO, the adaptive switching obviously increases the average cell throughput.

7.3.1 Principles
When TMA is enabled, the initial transmission mode used during network access is subject to the setting of the [Link] parameter. For details about
the setting notes of this parameter, see [Link].1 Scenario A: Adaptive Switching Between Single- or Dual-Stream Beamforming and MIMO.
A UE can adaptively enter TM2, TM3, TM4, TM7, TM8, or TM9 based on the parameter settings, UE type, and SINR.
Figure 7-3 TMA affecting factors

If the [Link] parameter is set to NO_ADAPTIVE, the transmission mode is determined by the [Link]
parameter. The setting is recommended only in test scenarios.
Table 7-1 describes the transmission mode selected by a UE when the [Link] parameter is set to TxD_BF_ADAPTIVE.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 40/56


12/15/2020 HedEx Startpage
Table 7-1 TMA selection

UE SINR Transmission Mode

High-speed UEs N/A Transmit diversity (TM2 rank 1)

Low-speed UEs compliant with 3GPP Release 8 N/A Single-stream beamforming (TM7 rank 1)

Low-speed UEs compliant with 3GPP Release 9 or Low Single-stream beamforming (TM7 or TM8
later rank 1)
PMI feedback-independent TM9 rank 1

Low-speed UEs compliant with 3GPP Release 9 or High Dual-stream beamforming (TM8 rank 2)
later PMI feedback-independent TM9 rank 2

Table 7-2 and Table 7-3 describe the transmission mode selected by a UE when the [Link] parameter is set to MIMO_BF_ADAPTIVE.

Table 7-2 TMA selection when the [Link] parameter is set to CRS_PORT_2

UE Type SINR Transmission Mode

High-speed UEs Low Transmit diversity (TM2 rank 1)

High Spatial multiplexing (TM3 rank 2)

Low-speed UEs compliant with 3GPP Release 8 Low Single-stream beamforming (TM7 rank 1)

High Spatial multiplexing (TM3 rank 2)

Low-speed UEs compliant with 3GPP Release 9 Low Single-stream beamforming (TM7 or TM8 rank 1)

High Dual-stream beamforming (TM8 rank 2)


Spatial multiplexing (TM3 rank 2)

Low-speed UEs compliant with 3GPP Release 10 Low Single-stream beamforming (TM7 or TM8 rank 1)
or later
High Dual-stream beamforming (TM8 rank 2)
Spatial multiplexing (TM3 rank 2)
PMI feedback-dependent TM9 rank 3 or 4

Table 7-3 TMA selection when the [Link] parameter is set to CRS_PORT_4

UE Type SINR Transmission Mode

High-speed UEs Low Transmit diversity (TM2 rank 1)

High Spatial multiplexing (TM3 rank 2 to rank 4)

Low-speed UEs compliant with 3GPP Release 8 Low Single-stream beamforming (TM7 rank 1)

High Spatial multiplexing (TM3 or TM4 rank 2 to rank 4)

Low-speed UEs compliant with 3GPP Release 9 or Low Single-stream beamforming (TM7 or TM8 rank 1)
later
High Dual-stream beamforming (TM8 rank 2)
Spatial multiplexing (TM3 or TM4 rank 2 to
rank 4)

TM9 is not compatible with TM4. When the [Link] parameter is set to CRS_PORT_2 in adaptive transmission mode switching scenarios, the transmission mode can
adaptively switch between TM3, TM8, and TM9, but not between TM3, TM4, and TM8. When this parameter is set to CRS_PORT_4 in adaptive transmission mode switching
scenarios, the transmission mode can adaptively switch between TM3, TM4, and TM8, but not between TM3, TM8, and TM9.
The thresholds for switching between different transmission modes can be adjusted. For details, see Parameter Optimization of the Threshold for Triggering Adaptive Switching Between
Beamforming and MIMO.

Figure 7-4 Adaptive switching between beamforming and MIMO when the CrsPortNum parameter is set to CRS_PORT_2(2 ports) and low-speed UEs compliant with 3GPP
Release 8 or 9 exist

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 41/56


12/15/2020 HedEx Startpage

NOTE:
The multiple-antenna solutions and switching points shown in Figure 7-4 are explained as follows:

Multiple-antenna solution for 3GPP Release 8-compliant UEs: Only single-stream beamforming is supported.
Multiple-antenna solution for 3GPP Release 9-compliant UEs: Dual-stream beamforming is supported.
Transmission mode switching point for 3GPP Release 8-compliant UEs: refers to the switching point between single-stream beamforming and TM3 rank 2.
Transmission mode switching point for 3GPP Release 9-compliant UEs: refers to the switching point between single-stream beamforming and dual-stream beamforming or
between dual-stream beamforming and TM3 rank 2.

7.3.2 Optimization Functions


Switching between transmission modes has been optimized as follows:

MA Without TM2

The eNodeB determines whether to consider TM2 during TMA based on the setting of the CellBfMimoParaCfg.BfMimoAdapWithoutTm2 parameter. This function increases the cell
throughput.

ansmission Mode Switching Acceleration

When the [Link] parameter is set to ON, the eNodeB adapts the period for determining transmission modes to UE signal quality, which
facilitates switching to an appropriate transmission mode and increases the UEs' spectral efficiency.
This function accelerates transmission mode switching when the UE initially accesses the network or is online, and may affect the stability of the switching. Therefore, this function
needs to be fully verified on the live network before being enabled.

uick Entry into Beamforming After Initial Network Access

When the [Link] parameter is set to INITIAL_ACCESS_TO_BF, the eNodeB instructs the UEs with good beamforming performance to quickly
switch from MIMO to beamforming after initial network access. This function increases the proportion of beamforming UEs and beamforming-related gains in burst scenarios. Quick
switching to TM7 is not supported in non-massive MIMO cells. In SFN scenarios, the first RRU attribute determination period after each network access shortens, decreasing the
proportion of joint-scheduling UEs. This function is recommended in scenarios with good beamforming performance, such as D-MIMO.

ngle- and Dual-Stream Beamforming Detection

When the BfDetectRank1AdjSwitch option is selected under the [Link] parameter, the eNodeB detects single-stream beamforming performance
in dual-stream beamforming so that an optimal transmission mode can be selected promptly to increase the UEs' spectral efficiency.

MA Without TM8

The eNodeB adaptively switches the transmission mode without considering TM8 when all of the following conditions are met:

4T4R RRUs are configured.


One or more UEs compliant with 3GPP Release 9 or later do not support transmit antenna selection, or the [Link] parameter is set to SINGLE_LAYER_BF.
The BFMIMOADAPWITHOUTTM8 option is selected under the [Link] parameter.

In this situation, the transmission mode can be between TM2 and TM7 or between TM2, TM3, and TM7, as shown in 7.3.1 Principles. This increases the number of RBs available for
scheduling in a cell and improves the throughput.

rect Switching from Dual-Stream Beamforming (TM8) to TM3 Rank 2

Optimized switching from beamforming to MIMO and optimized MIMO rank detection are enabled to improve the rank 2 success rate when the BFTOMIMOALGOOPTSWITCH
option is selected under the [Link] parameter. This function improves throughput.

try into Beamforming for UEs Configured with the SRS Period of 160 ms or Less

UEs configured with the SRS period of 160 ms or less can enter beamforming when the LongSrsPeriodBfSwitch option is selected under the [Link]
parameter. This function further improves the proportion of beamforming UEs.
Fixed beamforming mode is not recommended when TDLEOFD-111505 DL D-MIMO and TDLEOFD-121501 Inter-eNodeB DL D-MIMO (Trial) are enabled, the
LongSrsPeriodBfSwitch option is selected under the [Link] parameter, and more than 400 UEs have accessed the network from the current cell.

ptimized TMA

If the BFMIMOADAPTATIONOPTSW option of the [Link] is selected, optimized TMA takes effect.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 42/56


12/15/2020 HedEx Startpage
This function produces the following benefits:

Beamforming UEs that enjoy beamforming gains can stay in beamforming mode. The proportion of beamforming UEs increases.
The proportion of dual-stream beamforming UEs may increase or decrease, depending on the radio channel quality of the UEs. If the UEs are near the cell center and the
MCS indexes of the two codewords are high, the proportion of dual-stream beamforming UEs may increase. If the MCS index of a codeword is low, the proportion of dual-
stream beamforming UEs may decrease. In both cases, this function selects an optimal transmission mode for UEs based on channel conditions, improving the downlink
spectral efficiency of UEs.

ptimized TMA for 4R and 8R UEs

UEs with more receive antennas demonstrate improved demodulation performance. The SINR ranges in which different transmission modes take effect are different from those for
2R UEs. This function optimizes the SINR ranges in which different transmission modes take effect, improving the downlink spectral efficiency and user-perceived rate.
This function is controlled by the CellBfMimoParaCfg.Ue4ROr8RBfMimoAdaptOptSw parameter. If the CellBfMimoParaCfg.Ue4ROr8RBfMimoAdaptOptSw parameter is set to ON,
this function produces the following benefits:

The threshold for switching between TM3 rank 2 and TM9 rank 4 (PMI feedback-dependent TM9 rank 3 to rank 8) is optimized for 4R 256QAM UEs.
The CellBfMimoParaCfg.Tm3ToTm9SwtgSEffOfs256qam and CellBfMimoParaCfg.Tm9ToTm3SwtgSEffOfs256qam parameters need to be set.
The threshold for switching between TM3 rank 2 and dual-stream beamforming (TM8), and between TM3 rank 2 and PMI feedback-independent TM9 rank 2 is optimized for
4R and 8R UEs.
The CellBfMimoParaCfg.AsUeDualBfToTM3Rank2Offset and CellBfMimoParaCfg.AsUeTM3Rank2ToDualBfOffset parameters need to be set.
To ensure that fake antenna selection UEs do not use the threshold for switching between TM3 rank 2 and dual-stream beamforming for antenna selection UEs, it is
recommended that the FakeAntSelIdentificationSwitch option of the [Link] parameter be selected to identify fake antenna selection UEs.

Network Analysis

7.4.1 Benefits
SU beamforming and MU beamforming: For details, see Achievable Gains.

7.4.2 Impacts

twork Impacts

Single- or dual-stream beamforming: For details, see Network Impacts.


TM9: For details, see Network Impacts.
MU beamforming: For details, see Network Impacts.
Adaptive switching between beamforming and MIMO
Transmission mode switching acceleration and single- and dual-stream beamforming detection: The functions improve the spectral efficiency of the network.
Quick entry into beamforming after initial network access: In scenarios where beamforming performance is good, such as D-MIMO scenarios, this function enables
UEs to quickly switch to beamforming after their initial network access, improving both UE and cell throughput.
TMA without TM8: The eNodeB adaptively switches the transmission mode without considering TM8 when all of the following conditions are met:
4T4R RRUs are used.
One or more UEs compliant with 3GPP Release 9 or later do not support transmit antenna selection, or the [Link] parameter is set to
SINGLE_LAYER_BF.
The BFMIMOADAPWITHOUTTM8 option is selected under the [Link] parameter.

This increases the number of RBs available for scheduling in a cell and improves the throughput.
Direct switching from beamforming to TM3 rank 2: Throughput increases when the BFTOMIMOALGOOPTSWITCH option is selected under the
[Link] parameter.
Entry into beamforming for UEs configured with the SRS period of 160 ms or less: This function improves the proportion of beamforming UEs.
Optimized TMA for 4R and 8R UEs:
If there are 4R or 8R UEs, this function increases the proportion of beamforming UEs.
If there are 4R 256QAM UEs, this function lowers the proportion of PMI feedback-dependent TM9 UEs.
If there are 4R or 8R UEs, this function improves the downlink spectral efficiency and the downlink user-perceived rate.

nction Impacts

Single- or dual-stream beamforming: For details, see Function Impacts.


TM9: For details, see Function Impacts.
MU beamforming: For details, see Function Impacts.
Adaptive switching between beamforming and MIMO: None

Requirements

7.5.1 Licenses
For details about the license requirements of single- or dual-stream beamforming, TM9, and MU beamforming, see [Link] Licenses, [Link] Licenses, and 6.3.1 Licenses, respectively.
The following table lists the additional licenses required by adaptive switching between beamforming and MIMO. The license for downlink 4x4 MIMO needs to be prepared only when
TM4 is available during TMA.

Feature ID Feature Name Model Sales Unit

TDLOFD-001001 DL 2x2 MIMO LT1STD2I2O00 per Cell

TDLOFD-001060 DL 4x4 MIMO LT1STD4I4O00 per Cell

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

erequisite Functions

Single- or dual-stream beamforming: For details, see Prerequisite Functions.


TM9: For details, see Prerequisite Functions.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 43/56


12/15/2020 HedEx Startpage
MU beamforming: For details, see Prerequisite Functions.
Adaptive switching between beamforming and MIMO
The following table describes the prerequisite functions of optimized TMA for 4R and 8R UEs.

Function Name Function Switch Reference Description

Adaptive switching [Link] Beamforming (TDD) This function takes effect only when the
between beamforming set to MIMO_BF_ADAPTIVE [Link] parameter is
and MIMO set to MIMO_BF_ADAPTIVE.

Fake antenna selection FakeAntSelIdentificationSwitch option Beamforming (TDD) Optimization of the threshold for switching between TM3
UE identification under the [Link] and TM7 for 4R and 8R antenna selection UEs takes
parameter effect only if this option is selected.

utually Exclusive Functions

Single- or dual-stream beamforming: For details, see Mutually Exclusive Functions.


TM9: For details, see Mutually Exclusive Functions.
MU beamforming: For details, see Mutually Exclusive Functions.
Adaptive switching between beamforming and MIMO: Only the following functions have mutually exclusive functions.
The following table describes the mutually exclusive functions of optimized TMA.

Function Name Function Switch Reference

Massive MIMO cell [Link] set to 32T32R or 64T64R Massive MIMO (TDD)

SFN cell [Link] SFN

D-MIMO cell [Link] D-MIMO (TDD)

The following table describes the mutually exclusive functions of single- and dual-stream beamforming detection.

Function Name Function Switch Reference Description

Carrier Aggregation None Carrier Aggregation Single- and dual-stream beamforming detection does not
take effect on CA UEs.

7.5.3 Hardware
For details about the hardware requirements of single- or dual-stream beamforming, TM9, and MU beamforming, see [Link] Hardware and 6.3.3 Hardware, respectively.

7.5.4 Others
For details about the UE requirements of single- or dual-stream beamforming, TM9, and MU beamforming, see UEs and UEs, respectively. Adaptive switching between beamforming
and MIMO has no additional UE requirement.

Operation and Maintenance

7.6.1 Data Configuration

[Link] Data Preparation

[Link].1 Scenario A: Adaptive Switching Between Single- or Dual-Stream Beamforming and MIMO

rameters Used for Activation

The following parameters need to be additionally configured on the basis of the configuration of single- or dual-stream beamforming. For details about data preparation for single- or
dual-stream beamforming, see [Link].1 Data Preparation.

Table 7-4 Parameters in the Cell MO

Parameter Name Parameter ID Setting Notes

CRS Port Number [Link] Set this parameter to CRS_PORT_2 in 2x2 MIMO scenarios.
Set this parameter to CRS_PORT_4 in 4x4 MIMO scenarios.
For details about the transmission mode selection result, see 7.3.1 Principles.
If the [Link] parameter is set to CRS_PORT_4, the
[Link] parameter is set to TM2 by default.

Table 7-5 Parameters in the CellDlschAlgo MO

Parameter Name Parameter ID Option Setting Notes

maximum number of MIMO [Link] None It is recommended that this parameter be set to
layers SW_MAX_SM_RANK_2 in downlink 2x2 MIMO
scenarios.
It is recommended that this parameter be set to
SW_MAX_SM_RANK_4 in downlink 4x4 MIMO
scenarios.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 44/56


12/15/2020 HedEx Startpage

Parameter Name Parameter ID Option Setting Notes

Downlink Rank Detect Switch [Link] BfDetectRank1AdjSwitch It is recommended that this option be selected to enable single-
and dual-stream beamforming detection when there are UEs
working in dual-stream beamforming.
When the BfDetectRank1AdjSwitch option is selected under
this parameter, the eNodeB detects the performance of single-
stream beamforming when dual-stream beamforming takes
effect. The detection improves the accuracy of switching
between single- and dual-stream beamforming and increases
the spectral efficiency.

Table 7-6 Parameter in the CellBfMimoParaCfg MO

Parameter Name Parameter ID Option Setting Notes

BfMIMO adaptive [Link] None It is recommended that this parameter be set to


switch MIMO_BF_ADAPTIVE.

Fixed BfMIMO [Link] None This parameter applies only when a transmission mode is
mode tested and the [Link]
parameter is set to NO_ADAPTIVE.

Bf Mimo Adaptive CellBfMimoParaCfg.BfMimoAdapWithoutTm2 None It is recommended that this parameter be set to ON.
Without Tm2 When this parameter is set to ON, TM2 is not considered
during transmission mode adaptation, and TM2 is no
longer used after the UE switches from TM2 to another
transmission mode.

Transmission Mode [Link] None It is recommended that this parameter be set to


Acceleration Switch INITIAL_ACCESS_TO_BF to enable quick entry into
beamforming during initial network access when eight or
more antennas are configured and single-stream
beamforming is enabled. Set this parameter to OFF in
other situations.
In different scenarios, antennas are counted in different
ways.
In SFN scenarios, the antennas mentioned above
refer to those connected to the target RRUs of the
UE.
In D-MIMO scenarios, the antennas mentioned
above refer to those connected to the coordinating
RRUs of the UE.

BfMIMO Adaptive CellBfMimoParaCfg.BfMimoAdapWithTm4Switch None This parameter specifies whether TM4 is available during
with TM4 adaptive switching between beamforming and MIMO.
Set this parameter to ON if downlink 4x4 MIMO is
required.
Set this parameter to OFF if the
[Link]
parameter is set to NO_ADAPTIVE.

Initial BFMIMO [Link] None This parameter specifies the transmission mode used
Mode during initial network access.
TM3 does not take effect and this parameter is set
to TM2 by default when the [Link]
parameter is set to CRS_PORT_4 and the
CellBfMimoParaCfg.BfMimoAdapWithTm4Switch
parameter is set to ON.
When the [Link] parameter is set to
CRS_PORT_4 and the
CellBfMimoParaCfg.BfMimoAdapWithTm4Switch
parameter is set to OFF:
1. Set this parameter to TM2 in non-CA scenarios
or for the PCC in CA scenarios.
2. Set this parameter to TM3 when beamforming is
not supported on the SCC.
3. Set this parameter to TM2 when beamforming is
supported on the SCC.

Antenna Type- [Link] None Set this parameter to 0 when 8T8R cross-
based BF and polarization antennas are used.
MIMO Algo Set this parameter to 1 when 8T8R omnidirectional
Selection antennas are used.
Set this parameter to 2 for other types of
antennas.

BfMimo Algorithm [Link] BFTOMIMOALGOOPTSWITCH It is recommended that this option be selected to enable
Optimization Switch direct switching from dual-stream beamforming (TM8) to
TM3 rank 2 when full adaptive switching between
beamforming and MIMO is enabled.

[Link] BFMIMOADAPWITHOUTTM8 It is recommended that this option be selected to enable


TMA without TM8 when full adaptive switching between
beamforming and MIMO or adaptive switching between
open-loop beamforming modes is enabled.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 45/56


12/15/2020 HedEx Startpage

Parameter Name Parameter ID Option Setting Notes

[Link] BFMIMOADAPTATIONOPTSW It is recommended that this option be selected to enable


optimized adaptive switching between beamforming and
MIMO when full adaptive switching between beamforming
and MIMO is enabled.

Handover BF [Link] None It is recommended that this parameter be set to ON when


Threshold Adjust there are many PCI mod3 conflicts and beamforming is
Switch enabled.

4R or 8R UE BF CellBfMimoParaCfg.Ue4ROr8RBfMimoAdaptOptSw None If there are 4R or 8R UEs, it is recommended that this


MIMO Adaptation option be selected.
Opt Sw

Table 7-7 Parameters in the eNodeBAlgoSwitch MO

Parameter Name Parameter ID Option Setting Notes

Compatibility Control Switch [Link] Tm3Tm4Max4LayerCtrlSwitch Select this option when 4x4 MIMO is enabled.

rameter Optimization of the Threshold for Triggering Adaptive Switching Between Beamforming and MIMO

When adaptive switching between beamforming and MIMO is enabled, the threshold for triggering the adaptive switching may need to be optimized. Perform the following steps to
optimize the threshold for triggering the adaptive switching:

1. Conduct a network test to obtain the relationship between the SINR and throughput, as shown in Figure 7-5.
Figure 7-5 Adaptive switching between beamforming and MIMO (using adaptive switching between dual-stream beamforming and TM3 rank 2 as an example)

2. Obtain the downlink MCS indexes corresponding to the ideal and actual switching points for TMA, calculate the spectral efficiency difference between the two MCS indexes
based on the mapping between MCS indexes and spectral efficiencies, and then adjust parameters listed in Table 7-8 and Table 7-9 based on the spectral efficiency
difference to optimize the thresholds.

The settings of the parameters have a great impact on system performance. Therefore, exercise caution when setting these parameters. You are advised to set these
parameters according to the suggestions provided in the following table.

Table 7-8 Suggestions on setting the thresholds for triggering switching between dual-stream beamforming and TM3 rank 2

UE Description Parameter Name Parameter ID Setting Notes

The low-speed UE Dual Streaming CellBfMimoParaCfg.DualBfToTM3Rank2Offset A large value increases the possibility that switching
moves fast and does Beamforming To TM3 from dual-stream beamforming to TM3 or TM4 rank 2 is
not support transmit Rank2 Offset triggered.
antenna selection. The value of this parameter must be less than or equal
to the value of the
CellBfMimoParaCfg.TM3Rank2ToDualBfThdOffset
parameter plus 4. In most cases, the value of this
parameter should be the same as that of the
CellBfMimoParaCfg.TM3Rank2ToDualBfThdOffset
parameter.

TM3 Rank2 To Dual CellBfMimoParaCfg.TM3Rank2ToDualBfThdOffset A large value decreases the possibility that switching
Streaming from TM3 rank 2 to dual-stream beamforming is
Beamforming triggered.
Threshold Offset

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 46/56


12/15/2020 HedEx Startpage

UE Description Parameter Name Parameter ID Setting Notes

The low-speed UE AS UE Dual BF To CellBfMimoParaCfg.AsUeDualBfToTM3Rank2Offset A large value increases the possibility that switching
moves fast and TM3 Rank2 Offset from dual-stream beamforming to TM3 or TM4 rank 2 is
supports transmit triggered.
antenna selection. The value of this parameter must be less than or equal
to the value of the
CellBfMimoParaCfg.AsUeTM3Rank2ToDualBfOffset
parameter plus 4. In most cases, set this parameter to
the value of the
CellBfMimoParaCfg.AsUeTM3Rank2ToDualBfOffset
parameter.
If optimized TMA for 4R and 8R UEs is enabled, it is
recommended that this parameter be set to –20.

AS UE TM3 Rank2 To CellBfMimoParaCfg.AsUeTM3Rank2ToDualBfOffset A large value decreases the possibility that switching
Dual BF Offset from TM3 or TM4 rank 2 to dual-stream beamforming is
triggered.
If optimized TMA for 4R and 8R UEs is enabled, it is
recommended that this parameter be set to –14.

The UE moves at High and Low Speed [Link] When the UE is moving at walking speed or is
walking speed or is UE TM Switch Thld stationary, beamforming provides better performance.
stationary. Offset Besides the preceding four parameters, it is
recommended that the value of this parameter be
adjusted to increase the possibility that the transmission
mode switches to dual-stream beamforming.
This parameter applies only when 8T8R cross-
polarization antennas are used in LTE TDD networks.
When this parameter is set to 0, the same
threshold is used for low-speed and high-speed
UEs.
A large value decreases the possibility that low-
speed UEs switch from dual-stream
beamforming to TM3 or TM4 rank 2.
Optimal performance can be measured only when the
value of this parameter matches the actual UE
conditions. Otherwise, the throughput and coverage
performance may deteriorate.

Table 7-9 Suggestions on setting the thresholds for triggering switching between single-stream beamforming and dual-stream beamforming.

UE Type Parameter Name Parameter ID Setting Notes

The UE does not support Single to Dual Streaming [Link] In beamforming scenarios, setting this parameter to
transmit antenna Beamforming Threshold a large value increases the probability that the UE
selection. Offset enters single-stream beamforming, and setting this
parameter to a small value increases the probability
that the UE enters dual-stream beamforming. You
are advised to retain the default value of this
parameter.

The UE supports transmit AS UE Single to Dual BF [Link] In beamforming scenarios, setting this parameter to
antenna selection. Offset a large value increases the probability that the UE
enters single-stream beamforming, and setting this
parameter to a small value increases the probability
that the UE enters dual-stream beamforming. You
are advised to retain the default value of this
parameter.

[Link].2 Scenario B: Adaptive Switching Between Single- or Dual-Stream Beamforming, TM9, and MIMO

rameters Used for Activation

TM9 cannot work with 4x4 MIMO. In addition to the MOs and parameters required in scenario A, scenario B requires the following MOs and parameters. For details about data
preparation for single- or dual-stream beamforming, see [Link].1 Data Preparation. For details about data preparation for TM9, see [Link].1 Data Preparation.

Table 7-10 Parameters in the CellBfMimoParaCfg MO

Parameter Name Parameter ID Setting Notes

BfMIMO Adaptive with CellBfMimoParaCfg.BfMimoAdapWithTm4Switch Retain the default value.


TM4

TM3 and TM9 Switching CellBfMimoParaCfg.Tm3AndTm9ThdOffset A smaller value of this parameter leads to a lower probability that a UE switches
Threshold Offset from TM3 to PMI feedback-dependent TM9. The value -30 is recommended.

TM3 Rank2 To TM9 Rank4 CellBfMimoParaCfg.Tm3Rank2ToTm9Rank4Offset This parameter affects the switching of the UE transmission mode from TM3 rank 2
Offset to 4-layer TM9. The value 9 is recommended.
When this parameter is set to a large value, the possibility that the UE
switches from TM3 rank 2 to 4-layer TM9 decreases.
When this parameter is set to a small value, the possibility that the UE
switches from TM3 rank 2 to 4-layer TM9 increases. The optimal
performance can be obtained only when the value of this parameter
matches application scenarios. Otherwise, the throughput and coverage
decrease.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 47/56


12/15/2020 HedEx Startpage

Parameter Name Parameter ID Setting Notes

TM9 Rank4 To TM3 Rank2 CellBfMimoParaCfg.Tm9Rank4ToTm3Rank2Offset This parameter affects the switching of the UE transmission mode from 4-layer
Offset TM9 to TM3 rank 2. The value 40 is recommended.

When this parameter is set to a large value, the possibility that the UE
switches from 4-layer TM9 to TM3 rank 2 increases.
When this parameter is set to a small value, the possibility that the UE
switches from 4-layer TM9 to TM3 rank 2 decreases. The optimal
performance can be obtained only when the value of this parameter
matches application scenarios. Otherwise, the throughput and coverage
decrease.

256QAM TM3 to TM9 CellBfMimoParaCfg.Tm3ToTm9SwtgSEffOfs256qam This parameter affects the switching of the transmission mode from TM3 rank 2 to
Switching Spectral Eff 4-layer TM9 at 256QAM. The value 60 is recommended.
Offset When this parameter is set to a large value, the possibility that the UE
switches from TM3 rank 2 to 4-layer TM9 decreases.
When this parameter is set to a small value, the possibility that the UE
switches from TM3 rank 2 to 4-layer TM9 increases. The optimal
performance can be obtained only when the value of this parameter
matches application scenarios. Otherwise, the throughput and coverage
decrease.

256QAM TM9 to TM3 CellBfMimoParaCfg.Tm9ToTm3SwtgSEffOfs256qam This parameter affects the switching of the transmission mode from 4-layer TM9 to
Switching Spectral Eff TM3 rank 2 at 256QAM. The value 75 is recommended.
Offset When this parameter is set to a large value, the possibility that the UE
switches from 4-layer TM9 to TM3 rank 2 increases.
When this parameter is set to a small value, the possibility that the UE
switches from 4-layer TM9 to TM3 rank 2 decreases. The optimal
performance can be obtained only when the value of this parameter
matches application scenarios. Otherwise, the throughput and coverage
decrease.

[Link].3 Scenario C: MU Beamforming Enabled on the Basis of Scenario A or B


For details about data preparation for MU beamforming, see [Link] Data Preparation.

[Link].4 Scenario D: Network Reconstruction Scenario

NOTE:
This document describes the following reconstruction scenarios:

Replacement of 2T2R or 4T4R RRUs on the live network with 4T4R or 8T8R RRUs, respectively
Change of the transmit/receive mode of an RRU (which is originally split into two 2T2R or 4T4R RRUs) to 4T4R or 8T8R, respectively

The following tables describe the MOs and parameters that must be set to activate beamforming and MIMO in network reconstruction scenarios.

Table 7-11 Parameters in the Cell MO

Parameter Name Parameter ID Setting Notes

CRS Antenna Port Mapping [Link] You are advised to retain the default value to maximize MIMO performance.

Table 7-12 Parameters in the CELLALGOSWITCH MO

Parameter Name Parameter ID Option Setting Notes

Antenna calibration [Link] CrossPolaCalibrationSwitch Select this option under this parameter to improve the
algorithm switch virtual antenna mapping performance of antennas when
two sets of 4T4R cross-polarization antennas are used.
Otherwise, the accumulative number of used PRBs in rank
2 may decrease.

Table 7-13 Parameter in the PDSCHCFG MO

Parameter Name Parameter ID Setting Notes

Reference signal power [Link] If the value of this parameter remains unchanged during network reconstruction, the total
power of the cell may exceed the maximum transmit power of RRUs and network coverage
may overlap after network reconstruction. Therefore, check whether to change the value of
this parameter based on the network plan.

Table 7-14 Parameters in the CELLDLSCHALGO MO

Parameter Name Parameter ID Option Setting Notes

Downlink Rank Detect [Link] DetectRank2AdjSwitch Select this option in network reconstruction scenarios.
Switch

[Link] Using MML Commands


In most cases, beamforming is used with MIMO. The following table lists the typical scenarios.

Table 7-15 Typical scenarios

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 48/56


12/15/2020 HedEx Startpage

Scenario MIMO Mode Available Transmission Mode

Scenario A: adaptive switching between single- or dual-stream Downlink 2x2 MIMO TM2, TM3, TM7, and TM8
beamforming and MIMO
Downlink 4x4 MIMO TM2, TM3, TM4, TM7, and TM8

Scenario B: adaptive switching between single- or dual-stream Downlink 2x2 MIMO TM2, TM3, TM7, TM8, and TM9
beamforming, TM9, and MIMO

Scenario C: MU beamforming enabled on the basis of scenario A or B Same as scenario A or B Same as scenario A or B

Scenario D: network reconstruction on the basis of scenario A, B, or C Same as scenario A, B, or C Same as scenario A, B, or C

[Link].1 Scenario A: Adaptive Switching Between Single- or Dual-Stream Beamforming and MIMO
The following parameters need to be additionally configured on the basis of the configuration of single- or dual-stream beamforming. For details about data configuration of single-
and dual-stream beamforming, see [Link].2 Using MML Commands.

The cell will reset after SRS configurations are modified by running the MOD SRSCFG command.

//(Optional) Configuring the number of CRS antenna ports. This step is required only in downlink 4x4 MIMO scenarios.
MOD CELL: LOCALCELLID=0, CRSPORTNUM=CRS_PORT_4;
//(Optional) Configuring the maximum number of MIMO layers. This step is required only in downlink 4x4 MIMO scenarios.
MOD CELLDLSCHALGO: LOCALCELLID=0, MAXMIMORANKPARA=SW_MAX_SM_RANK_4;
//(Optional) Enabling MIMO at up to four layers based on TM3 and TM4
MOD ENODEBALGOSWITCH: CompatibilityCtrlSwitch=Tm3Tm4Max4LayerCtrlSwitch-1;
//Enabling TMA
//In downlink 2x2 MIMO scenarios:
MOD CELLBFMIMOPARACFG: LOCALCELLID=0,BFMIMOADAPTIVESWITCH=MIMO_BF_ADAPTIVE, BFMIMOADAPWITHOUTTM2=ON, TmAccelerationSwitch=INITIAL_ACCESS_TO_BF;
//In downlink 4x4 MIMO scenarios (TM4 availability needs to be configured):
MOD CELLBFMIMOPARACFG: LOCALCELLID=0, BFMIMOADAPTIVESWITCH=MIMO_BF_ADAPTIVE, BFMIMOADAPWITHOUTTM2=ON, BFMIMOADAPWITHTM4SWITCH=ON, TmAccelerationSwit
//(Optional) Setting the corresponding parameters when 8T8R omnidirectional antennas are used
MOD CELLBFMIMOPARACFG: LOCALCELLID=0, ANTBASEDBFMIMOALGOSELECT=1;
MOD CELLBF: LocalCellId=0, DUALLAYERBFALGTYPE=CIRCULAR_ANTENNA_ARRAY_BFALG;
//(Optional) Enabling beamforming detection for rank 1 if dual-stream beamforming UEs exist
MOD CELLDLSCHALGO: LOCALCELLID=0, DlRankDetectSwitch= BfDetectRank1AdjSwitch-1;
//(Optional) Enabling optimized switching between beamforming and MIMO if dual-stream beamforming UEs exist
MOD CELLBFMIMOPARACFG:LOCALCELLID=0, BfMimoAlgoOptSwitch= BFTOMIMOALGOOPTSWITCH-1;
//(Optional) Enabling TM8-ignored full adaptive switching between transmission mode if 4T4R RRUs are configured and some UEs compliant with 3GPP Rel
MOD CELLBFMIMOPARACFG:LOCALCELLID=0, BfMimoAlgoOptSwitch= BFMIMOADAPWITHOUTTM8-1;
//(Optional) Selecting the BFTOMIMOALGOOPTSWITCH option when adaptive switching between beamforming and MIMO is enabled
MOD CELLBFMIMOPARACFG:LOCALCELLID=0, BfMimoAlgoOptSwitch= BFMIMOADAPTATIONOPTSW-1;
//(Optional) Turning on the fake antenna selection UE identification switch and the 4R and 8R UE transmission mode adaptation optimization switch, a
MOD CELLALGOSWITCH: LOCALCELLID=0, BfAlgoSwitch= FakeAntSelIdentificationSwitch-1;
MOD CELLBFMIMOPARACFG:LOCALCELLID=0, Ue4ROr8RBfMimoAdaptOptSw=1, AsUeDualBfToTM3Rank2Offset=-20, AsUeTM3Rank2ToDualBfOffset=-14;

[Link].2 Scenario B: Adaptive Switching Between Single- or Dual-Stream Beamforming, TM9, and MIMO
The following operations need to be performed if configuration for scenario A is complete.
//Configuring the threshold offsets for triggering switching between TM3 and TM9, from TM3 rank 2 to 4-layer TM9, and from 4-layer TM9 to TM3 rank 2
MOD CELLBFMIMOPARACFG: LOCALCELLID=0, Tm3AndTm9ThdOffset=-30, Tm3Rank2ToTm9Rank4Offset=9, Tm9Rank4ToTm3Rank2Offset=40, Tm3ToTm9SwtgSEffOfs256qam=60,
//(Optional) Turning on the 4R and 8R UE transmission mode adaptation optimization switch when there are 4R 256QAM UEs
MOD CELLBFMIMOPARACFG:LOCALCELLID=0, Ue4ROr8RBfMimoAdaptOptSw=1;

[Link].3 Scenario C: MU Beamforming Enabled on the Basis of Scenario A or B


For details about the data configuration of MU beamforming, see [Link] Using MML Commands.

[Link].4 Scenario D: Network Reconstruction Scenario


Perform the following operations in addition to the operations required in scenario A, B, or C:
//(Optional) Adding the sector and sector equipment when a 4T4R RRU originally split into two 2T2R RRUs is used as a whole to serve a cell or when a
RMV EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;
RMV SECTOR:SECTORID=0;
ADD SECTOR:SECTORID=0,ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANT3CN=0,ANT3SRN=60,ANT3SN=0,ANT3N=R0C,
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;
MOD CELL:LOCALCELLID=0,TXRXMODE=4T4R;
//(Optional) Changing the reference signal power based on the network plan
MOD PDSCHCFG:LOCALCELLID=0,REFERENCESIGNALPWR=92;
//Enabling downlink rank detection
MOD CELLDLSCHALGO: LocalCellId=0,DlRankDetectSwitch=DETECTRANK2ADJSWITCH-1;
//(Optional) Enabling antenna calibration when two sets of 4T4R cross-polarization antennas are used
MOD CELLALGOSWITCH: LOCALCELLID=0,AntCalibrationAlgoSwitch=CrossPolaCalibrationSwitch-1;

[Link] Using the CME


For detailed operations, see CME-based Feature Configuration.

7.6.2 Activation Verification


UEs must reaccess the network to make beamforming or TM9 take effect after the beamforming or TM9 algorithm is enabled. After adaptive switching between beamforming and
MIMO is initially configured, perform the following steps to verify it:

1. To verify the transmission mode, perform the following operations:

a. Start downlink services on a UE compliant with 3GPP Release 8 or later, and move the UE away from the cell center.
b. On the OSS, perform a Uu interface tracing task and check the UE transmission mode. Figure 7-6 shows the Uu interface tracing result.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 49/56


12/15/2020 HedEx Startpage
Figure 7-6 UE transmission mode

c. Check whether the changes of transmission modes during the UE movement match what is listed in Table 7-16. If yes, beamforming and the related TMA have
taken effect.

Table 7-16 Changes in transmission modes during the UE movement

3GPP Release Version Channel Condition Transmission Modes

3GPP Release 8 High SINR TM3 or TM4

Low SINR TM7, TM2, or TM3

3GPP Release 9 High SINR and low spatial correlation TM8, TM4, or TM3

Low SINR and high spatial correlation TM8

Low SINR and spatial correlation TM2 or TM3

3GPP Release 10 High SINR and low spatial correlation TM8, TM3, TM4, or TM9

Low SINR and high spatial correlation TM8 or TM9

Low SINR and spatial correlation TM2 or TM3

7.6.3 Network Monitoring


For details about network monitoring of single-stream beamforming and MU beamforming, see [Link] Network Monitoring, [Link] Network Monitoring, and 6.4.3 Network Monitoring. For
MIMO and TMA, monitor resource usages based on the following counters.

Function Counter ID Counter Name

MIMO 1526727391 to 1526746777 [Link].Rank1~[Link].Rank8

MIMO 1526727393 to 1526728177 [Link].Rank1~[Link].Rank4

MIMO 1526730141 to 1526746773 [Link].Rank1~[Link].Rank8

TMA 1526737831 to 1526737833 [Link]~[Link]

TMA 1526737837 to 1526737838 [Link]~[Link]

TMA 1526737839 to 1526737841 [Link].TM1~[Link].TM3

TMA 1526737845 to 1526737846 [Link].TM7~[Link].TM8

8 Cell-level TMA

This chapter applies only to 4T4R and 8T8R networking scenarios.


Cell-level TMA enables the eNodeB to improve the overall cell performance by selecting appropriate transmission modes for UEs. This function covers heavy-load TMA boost.

Heavy-Load TMA Boost


In most heavy-load 8T8R cells, MU beamforming pairing of UEs working fixedly in beamforming increases the cell spectral efficiency and relieves the network load in contrast with
UE-level TMA. For the heavy-load cells with a high proportion of CCUs or moving UEs, TMA achieves better spectral efficiency than the fixed beamforming mode.
To prevent significant negative gains of the fixed beamforming mode in certain heavy-load cells, heavy-load TMA boost is introduced. This function enables the eNodeB to identify
and use the transmission mode that offers the best spectral efficiency in heavy-load scenarios.
This function takes effect for all newly accessed MBB and WBB UEs and the already online WBB UEs. Figure 8-1 shows the implementation process of this function.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 50/56


12/15/2020 HedEx Startpage
Figure 8-1 Implementation process of heavy-load TMA boost

The following parameter settings are used to configure heavy-load TMA boost.

Purpose Parameter Setting

To enable heavy-load TMA boost The HEAVYLOADTRANSMODEADAPTBOOSTSW and HISTORICALSPECTRALEFFOPTSW


options of the [Link] parameter are selected.

To determine heavy-load scenarios Both of the following conditions are met:


Average downlink PRB usage of the cell > Value of the
[Link] parameter
Average number of UEs in a cell > Value of the
[Link] parameter

To measure the overall historical spectral efficiency of a cell The [Link] parameter specifies the period for measuring
in heavy-load scenarios where cell-level TMA and target the cell load and spectral efficiency when this function takes effect.
beamforming mode are used The [Link] parameter specifies the target beamforming
mode (TM7 or TM8) used by a cell when the cell is heavily loaded.

After this function is enabled, the eNodeB periodically checks the service load of a cell, compares the overall historical spectral efficiency achieved by cell-level TMA with that
achieved by the target beamforming mode in heavy-load scenarios. Based on the comparison result, the eNodeB automatically selects a transmission mode that offers the optimal
spectral efficiency of the cell.
Figure 8-2 shows the processing mechanism for UEs that support TM9 rank 4 after this function is enabled. Optimized switching to beamforming in heavy-load scenarios is controlled
by the [Link] parameter. This function takes effect only if this parameter is not set to 255.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 51/56


12/15/2020 HedEx Startpage
Figure 8-2 Mechanism for switching the transmission mode of UEs that can enter TM9 rank 4 mode

During beamforming in a heavy-load cell, the eNodeB can forcibly switch the transmission mode of a maximum of 10 online UEs to the target beamforming mode (TM7 or TM8) per
logical cell per second.
If the cell changes from the heavy-load beamforming state to the light-load state, the transmission mode of online WBB UEs can switch from the target beamforming mode to TM2,
TM3, TM8, or TM9.

Network Analysis

8.2.1 Benefits
In heavy-load scenarios, this function enables the eNodeB to automatically identify when the gain of the cell-level target beamforming mode is greater than that of TMA and
accordingly enable cell-level target beamforming mode. In this way, the downlink spectral efficiency improves.

NOTE:
A certain period of time is required to reduce the fluctuations in the historical spectral efficiency. Therefore, it is recommended that you obtain stable evaluation results several days
after the eNodeB starts running.

ains

In most beneficial scenarios, the spectral efficiency of the cell is expected to increase by 1% to 3% in contrast with that achieved by UE-level TMA when the average downlink
PRB usage of a cell ranges from 50% to 80% and there are more than 50 UEs on average in a cell.
In most beneficial scenarios, the spectral efficiency of the cell is expected to increase by 3% to 5% in contrast with that achieved by UE-level TMA when the average downlink
PRB usage of a cell is greater than 80% and there are more than 50 UEs on average in a cell.

ost Beneficial Scenarios

This function is recommended when all of the following conditions are met:

The average downlink PRB usage in busy hours is high (recommended value: > 50%).
The average number of UEs in busy hours is large (recommended value: > 50).

The total PRB usage of UEs working in rank 2 and greater in busy hours is less than 30%.
The proportion of moving UEs is low and the cell does not cover railways, high-speed roads, or crossroads.

The gain of this function is more significant if the spectral efficiency of TMA in busy hours is low.

8.2.2 Impacts

twork Impacts

This function increases the proportion of beamforming in busy hours, the average CQI value, the number of paired PRBs, and the downlink spectral efficiency. However, in
WTTx scenarios, additional RRC signaling messages are used for switching between transmission modes of WTTx UEs. After this function is enabled, the service drop rate
may slightly increase.
Gains are positive only when the cell load is heavy. If the heavy-load threshold parameter is set to a small value for this function, the gains brought by this function are not
significant or even negative, and the average CQI value and proportion of DTXs may be slightly affected.
If the cell does not meet the gain requirements, the performance of TMA in the cell may be significantly better than that of the target beamforming mode. Cell-level TMA is
tried after being enabled. Therefore, if this feature is enabled in this scenario, slight negative gains may occur.
When optimized switching to beamforming in heavy-load scenarios takes effect and there are WBB UEs working in PMI feedback-dependent TM9 rank 3 to rank 8 mode, the
eNodeB switches the transmission mode of these UEs to the target beamforming mode. This increases the proportion of beamforming UEs, the number of downlink pairing
layers, and the downlink spectral efficiency.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 52/56


12/15/2020 HedEx Startpage
nction Impacts

Function Name Function Switch Reference Description

4x4 MIMO in the overlapping SfnJtSwitch option under the SFN After 4x4 MIMO in the overlapping areas of an SFN cell is
area of an SFN cell [Link] enabled, a UE that newly accesses the network in an
parameter overlapping area of the SFN cell will enter closed-loop TM9
mode if the SINR and channel condition for the UE meet the
requirements for using TM9 rank 4. However, the UE enters
TM7, TM8, or open-loop TM9 and no longer enters closed-
loop TM9 mode when the following conditions are met:
D-MIMO is enabled in the cell.
Heavy-load TMA boost is enabled in the cell.
The cell meets the heavy load conditions, and the
performance of the target beamforming mode in
heavy-load scenarios is better than that of UE-level
TMA.

WBB UE identification [Link] WBB If WBB UE identification is used with cell-level TMA:
The new transmission mode takes effect for
all newly accessed WBB and MBB UEs.
When an online WBB UE is working in TM7,
TM8, or TM9 and its transmission mode
needs to be switched to a different target
beamforming mode, the new transmission
mode does not take effect on the UE. When
the transmission mode is switched to TMA,
the new transmission mode takes effect on
the UE.
The new transmission mode does not take
effect on the MBB UEs that are already
online.
If the WBB UE identification function is not enabled,
the new transmission mode takes effect only on
newly accessed UEs, not on already online UEs.

Requirements

8.3.1 Licenses
There are no license requirements.

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

erequisite Functions

Function Name Function Switch Reference Description

Single-stream beamforming BfSwitch option of the Beamforming (TDD) This function is required when the
[Link] parameter [Link] parameter is
set to TM7.

Dual-stream beamforming BfSwitch option of the Beamforming (TDD) This function is required when the
[Link] [Link] parameter is
parameter set to TM8.
[Link] set to
DUAL_LAYER_BF

2-layer MU beamforming MuBfSwitch option under the Beamforming (TDD) None


[Link]
parameter
[Link]

Adaptive switching between [Link] Beamforming (TDD) None


beamforming and MIMO set to MIMO_BF_ADAPTIVE

utually Exclusive Functions

Function Name Function Switch Reference Description

Turbo beamforming TurboBfSwitch option under the WTTx Turbo Beamforming (TDD) None
[Link]
parameter

Forcible switching to CellBf.MultiLayerThdSwitchToTM7 D-MIMO (TDD) None


beamforming in heavy-load
D-MIMO scenarios

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 53/56


12/15/2020 HedEx Startpage

Function Name Function Switch Reference Description

Automatic congestion [Link] Automatic Congestion Handling Heavy-load TMA boost is not compatible with rules 31 and 32
handling (ACH) corresponding to the intelligent optimization functions of ACH.
Disable the ACH feature or deactivate rules 31 and 32 before
enabling heavy-load TMA boost.
To disable the ACH feature, run the following command:
MOD ENODEBALGOSWITCH: IOptAlgoSwitch= ACHSwitch-0;
To deactivate rules 31 and 32, run the following
commands:
DEA LIOPTRULE: RULEID=31;
DEA LIOPTRULE: RULEID=32;

Switching to TM7 in multi- None Massive MIMO (TDD) This function is not compatible with switching to TM7 in multi-
layer pairing scenarios layer pairing scenarios. Preferentially enable switching to TM7 in
multi-layer pairing scenarios. If switching to TM7 in multi-layer
pairing scenarios cannot offer positive gains, enable this function.

8.3.3 Hardware

se Station Models

The following base stations are compatible with this function:

3900 and 5900 series base stations


DBS3900 LampSite and DBS5900 LampSite

oards

No requirements

F Modules

No requirements

8.3.4 Others
None

Operation and Maintenance

8.4.1 Data Configuration


This chapter describes the operations required in scenario E where heavy-load TMA boost is enabled on the basis of the configuration of scenario A, B, or C.

[Link] Data Preparation


Table 8-1 and Table 8-2 describe the parameters used for function activation and optimization, respectively. The parameters related to cell setup are not described in the tables.

Table 8-1 Parameters used for activation

Parameter Name Parameter ID Option Setting Notes

BfMimo Algorithm [Link] HEAVYLOADTRANSMODEADAPTBOOSTSW Select this option.


Optimization Switch
HISTORICALSPECTRALEFFOPTSW Select this option.

Table 8-2 Parameters used for optimization

Parameter Name Parameter ID Setting Notes

Heavy Load Target Trans [Link] Set this parameter to its recommended value.
Mode

Heavy Load Trans Mode [Link] Set this parameter to its recommended value.
Evaluation Period

Heavy Load Downlink PRB [Link] Set this parameter to its recommended value.
Usage Threshold

Heavy Load Average UE [Link] Set this parameter to its recommended value.
Count Threshold

Heavy-Load Switch to BF [Link] Set this parameter to its recommended value.


Optimization

[Link] Using MML Commands

tivation Command Examples

//Enabling heavy-load TMA boost and historical spectral efficiency optimization


MOD CELLBFMIMOPARACFG: LocalCellId=0, BfMimoAlgoOptSwitch=HEAVYLOADTRANSMODEADAPTBOOSTSW-1&HISTORICALSPECTRALEFFOPTSW-1;
//(Optional) Enabling optimized switching to beamforming in heavy-load scenarios
MOD CELLBF: LocalCellId=0, HeavyLoadSwitchToBfOpt=15;

activation Command Examples

//Disabling heavy-load TMA boost and historical spectral efficiency optimization


MOD CELLBFMIMOPARACFG: LocalCellId=0, BfMimoAlgoOptSwitch=HEAVYLOADTRANSMODEADAPTBOOSTSW-0&HISTORICALSPECTRALEFFOPTSW-0;
//Disabling optimized switching to beamforming in heavy-load scenarios
MOD CELLBF: LocalCellId=0, HeavyLoadSwitchToBfOpt=255;

[Link] Using the CME

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 54/56


12/15/2020 HedEx Startpage
For detailed operations, see CME-based Feature Configuration.

8.4.2 Activation Verification


Assume that all parameters related to this function are set to their default values.

The [Link] parameter is set to TM7.


The [Link] parameter is set to 10.
The [Link] parameter is set to 50.
The [Link] parameter is set to 50.

1. Run the LST CELLBFMIMOPARACFG command to query the switch status of heavy-load TMA boost and historical spectral efficiency optimization. If both of them have
been turned on, heavy-load TMA boost and historical spectral efficiency optimization are both enabled.
2. Start a Uu interface signaling tracing task on the OSS when the heavy-load thresholds specified by the preceding parameters have been reached.
View the RRC_CONN_RECFG message to check the transmission mode. This function takes effect if the transmissionMode field contains multiple transmission modes
about 5 minutes after this function is enabled and contains only TM7 (except for certain UEs capable of 4x4 MIMO) 5 to 10 minutes after this function is enabled.
3. Run the LST CELLBF command to check whether the Heavy-Load Switch to BF Optimization parameter is not set to 255. If the Heavy-Load Switch to BF
Optimization parameter is not set to 255, optimized switching to beamforming in heavy-load scenarios has been enabled.

8.4.3 Network Monitoring


This function improves the downlink UE pairing rate and spectral efficiency in heavy-load scenarios. The following counters used to observe the performance of this function.

Counter ID Counter Name Description

1526747711 [Link] The counters are related


to heavy-load TMA boost.
1526747712 [Link]

1526747713 [Link]

1526747714 [Link]

1526747715 [Link]

1526739777 through 1526739780 [Link] through [Link] The counters measure the
average number of PRBs
successfully paired for MU
beamforming at each
layer.

1526737840 through 1526737846 [Link].TM2 through [Link].TM8 The counters measure the
proportion of used PRBs
1526747667 [Link].TM9 in a downlink transmission
mode.

1526728261 [Link] The counters measure the


average downlink spectral
1526728763 [Link] efficiency of the cell.

1526730558 [Link]

The following formula is used to evaluate the average downlink spectral efficiency of a cell:
Average downlink spectral efficiency = [Link]/([Link] x [Link])

9 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?

1. Open the EXCEL file of parameter reference.


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.
3. Click OK. All parameters related to the feature are displayed.

FAQ 2: How do I find the information about a certain reserved parameter from the used reserved parameter list?

1. Open the EXCEL file of the used reserved parameter list.


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.

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 55/56


12/15/2020 HedEx Startpage

10 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?

1. Open the EXCEL file of performance counter reference.


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.
3. Click OK. All counters related to the feature are displayed.

11 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

12 Reference Documents

1. 3GPP TS 36.213, "Physical layer procedures"


2. 3GPP TS 36.306, "User Equipment (UE) radio access capabilities"
3. 3GPP TS 36.306, "ue-Category"
4. 3GPP TS 36.331, "Radio Resource Control (RRC); Protocol specification"
5. DL CoMP (TDD)
6. D-MIMO (TDD)
7. eMBMS
8. LCS
9. Dynamic Power Sharing Between LTE Carriers
10. MIMO
11. Massive MIMO (TDD)
12. Relay
13. SFN
14. WBB
15. WTTx Turbo Beamforming (TDD)
16. Scheduling
17. High Speed Mobility
18. Extended CP
19. Energy Conservation and Emission Reduction
20. Soft Split Resource Duplex (TDD)
21. Carrier Aggregation
22. Automatic Congestion Handling

localhost:7890/[Link]?time=Tue Dec 15 2020 [Link] GMT+0300 (Arabian Standard Time) 56/56

You might also like