Professional Documents
Culture Documents
Issue Draft A
Date 2021-12-30
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.
Website: https://www.huawei.com
Email: support@huawei.com
Contents
1 Change History.........................................................................................................................1
1.1 5G RAN6.1 Draft A (2021-12-30)...................................................................................................................................... 1
3 Overview....................................................................................................................................8
4 Basic Functions of MIMO.....................................................................................................10
4.1 Principles.................................................................................................................................................................................. 10
4.1.1 Uplink Receive Diversity.................................................................................................................................................. 10
4.1.2 Downlink Beamforming.................................................................................................................................................. 11
4.1.3 Antenna Port Mapping.................................................................................................................................................... 14
4.1.3.1 Low-Frequency TDD 4T4R Cell Antenna Port Mapping................................................................................... 14
4.1.3.2 Low-Frequency TDD 8T8R Cell Antenna Port Mapping................................................................................... 16
4.1.4 Other Coverage Enhancement Functions................................................................................................................. 17
4.2 Network Analysis.................................................................................................................................................................. 18
4.2.1 Benefits................................................................................................................................................................................. 18
4.2.2 Impacts.................................................................................................................................................................................. 19
4.3 Requirements......................................................................................................................................................................... 20
4.3.1 Licenses................................................................................................................................................................................. 20
4.3.2 Software................................................................................................................................................................................20
4.3.3 Hardware.............................................................................................................................................................................. 20
4.3.4 Others.................................................................................................................................................................................... 21
4.4 Operation and Maintenance............................................................................................................................................. 21
4.4.1 Data Configuration........................................................................................................................................................... 21
4.4.1.1 Data Preparation............................................................................................................................................................ 21
4.4.1.2 Using MML Commands............................................................................................................................................... 23
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 23
4.4.2 Activation Verification..................................................................................................................................................... 24
4.4.3 Network Monitoring......................................................................................................................................................... 24
5 SU-MIMO................................................................................................................................. 25
5.1 Principles.................................................................................................................................................................................. 25
5.1.1 SU-MIMO Basics................................................................................................................................................................ 25
5.1.2 Downlink SU-MIMO Enhancements........................................................................................................................... 27
5.2 Network Analysis.................................................................................................................................................................. 29
5.2.1 Benefits................................................................................................................................................................................. 29
5.2.2 Impacts.................................................................................................................................................................................. 29
5.3 Requirements......................................................................................................................................................................... 30
5.3.1 Licenses................................................................................................................................................................................. 30
5.3.2 Software................................................................................................................................................................................31
5.3.3 Hardware.............................................................................................................................................................................. 31
5.3.4 Others.................................................................................................................................................................................... 31
5.4 Operation and Maintenance............................................................................................................................................. 31
5.4.1 Data Configuration........................................................................................................................................................... 31
5.4.1.1 Data Preparation............................................................................................................................................................ 32
5.4.1.2 Using MML Commands............................................................................................................................................... 34
5.4.1.3 Using the MAE-Deployment...................................................................................................................................... 35
5.4.2 Activation Verification..................................................................................................................................................... 35
5.4.3 Network Monitoring......................................................................................................................................................... 36
6 MU-MIMO............................................................................................................................... 37
6.1 Principles.................................................................................................................................................................................. 37
6.1.1 MU-MIMO Basics.............................................................................................................................................................. 37
6.1.2 MU-MIMO Spatial Multiplexing Procedures (Low-Frequency TDD)............................................................... 39
6.1.3 PDSCH MU-MIMO Enhancements (Low-Frequency TDD)................................................................................. 40
6.1.4 PUSCH MU-MIMO Enhancements (Low-Frequency TDD)................................................................................. 42
6.2 Network Analysis.................................................................................................................................................................. 44
6.2.1 Benefits................................................................................................................................................................................. 44
6.2.2 Impacts.................................................................................................................................................................................. 44
6.3 Requirements......................................................................................................................................................................... 53
6.3.1 Licenses................................................................................................................................................................................. 53
6.3.2 Software................................................................................................................................................................................53
6.3.3 Hardware.............................................................................................................................................................................. 54
6.3.4 Others.................................................................................................................................................................................... 55
6.4 Operation and Maintenance............................................................................................................................................. 55
6.4.1 Data Configuration........................................................................................................................................................... 55
6.4.1.1 Data Preparation............................................................................................................................................................ 55
6.4.1.2 Using MML Commands............................................................................................................................................... 60
6.4.1.3 Using the MAE-Deployment...................................................................................................................................... 61
6.4.2 Activation Verification..................................................................................................................................................... 61
6.4.3 Network Monitoring......................................................................................................................................................... 63
10 Parameters............................................................................................................................86
11 Counters................................................................................................................................ 87
12 Glossary................................................................................................................................. 88
13 Reference Documents........................................................................................................ 89
1 Change History
Technical Changes
Change Description Parameter Change RAT Base Station Model
Added SRS SINR Added high-frequency TDD High- 3900 and 5900 series
measurement optimization. to the applicable mode of frequency base stations
For details, see 4.1.4 Other the TDD DBS3900 LampSite
Coverage Enhancement SRS_SINR_MEAS_OPT_SW and DBS5900
Functions. option of the LampSite
NRDUCellSrs.SrsAlgoSwitc
h parameter.
Added the SRS-based Added the Low- 3900 and 5900 series
weight validity period NRDUCellPdschPre- frequency base stations
function. For details, see code.SrsWeightValidity- TDD DBS3900 LampSite
4.1.2 Downlink Period parameter. and DBS5900
Beamforming. LampSite
Added SINR optimization Added the Low- 3900 and 5900 series
for downlink MU-MIMO. NRDUCellDlAmc.DlMuMi frequency base stations
For details, see 6.1.3 moSirScaleFactor TDD
PDSCH MU-MIMO parameter.
Enhancements (Low-
Frequency TDD).
Disused the downlink MU- Added the Low- 3900 and 5900 series
MIMO frequency-domain NRDUCellDmrs.DlMuDmrs frequency base stations
correlation-based UE RsvdPortNum and TDD
pairing procedure. NRDUCellRsvdExt.RsvdPar
am7 parameters to the
disuse list.
Added the inter-cell cable Added the Low- 3900 and 5900 series
sequence detection AntPortOptDetPolicy frequency base stations
function. For details, see 9 parameter to the STR TDD
Inter-Cell Cable Sequence ANTENNAPORTOPTDET,
Detection. DSP
ANTENNAPORTOPTDET,
and STP
ANTENNAPORTOPTDET
commands.
Supported weights based Added the R16_TYPE2_SW Low- 3900 and 5900 series
on R16 Type II codebooks. option to the frequency base stations
For details, see 5.1.2 NRDUCellPdschPre- TDD DBS3900 LampSite
Downlink SU-MIMO code.DlCodebookTypeS- and DBS5900
Enhancements. witch parameter. LampSite
Added the uplink MU- Added the Low- 3900 and 5900 series
MIMO cross-slot pairing MU_MULTI_SLOT_PAIR_S frequency base stations
function. For details, see W option to the TDD
6.1.4 PUSCH MU-MIMO NRDUCellUlMimo.UlMuMi
Enhancements (Low- moAlgoSwitch parameter.
Frequency TDD).
Added uplink MU-MIMO Added options to the Low- 3900 and 5900 series
pairing based on space NRDUCellPusch.UlPuschAl frequency base stations
domain optimization. For goSwitch parameter: TDD
details, see 6.1.4 PUSCH ● UL_SCHEDULE_ENH_SW
MU-MIMO Enhancements
(Low-Frequency TDD). ● UL_INTRF_RANDOMIZE
D_SCH_ENH_SW
Editorial Changes
Revised descriptions in this document.
Added descriptions of packet length-based scheduling optimization. For details,
see 4.1.4 Other Coverage Enhancement Functions.
Added descriptions of delay-based scheduling optimization. For details, see 6.1.3
PDSCH MU-MIMO Enhancements (Low-Frequency TDD).
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 optimal gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in Feature
Parameter Description documents apply only to the corresponding software
release. For future software releases, refer to the corresponding updated product
documentation.
Basic functions of Only PMI-based weights but not SRS- 4 Basic Functions
MIMO based weights are supported in NR of MIMO
FDD. Both SRS-based weights and
PMI-based weights are supported in
NR TDD.
3 Overview
For NR TDD, MIMO greatly increases the number of antennas, evolving from the
LTE mainstream 2T2R/4T4R MIMO to the 5G mainstream 32T32R/64T64R massive
MIMO.
LampSite base stations can use distributed antennas to form distributed massive
MIMO cells. For details, see 7 Distributed Massive MIMO (Low-Frequency TDD).
For high-frequency TDD, the gNodeB can also use multi-beam frequency division
multiplexing (FDM) to improve spectral efficiency. For details, see 8 Multi-Beam
FDM (High-Frequency TDD).
Cable sequence detection can be used to find and solve antenna connection
problems during engineering deployment. For details, see 9 Inter-Cell Cable
Sequence Detection.
4.1 Principles
4.1.1 Uplink Receive Diversity
Figure 4-1 shows the principles of uplink receive diversity.
The UE sends signal x, which passes through different channels to the gNodeB's M
antennas r1 to rM. The gNodeB applies a weight wi to each received signal, and
then combines the weighted signals into signal y. The combined signal can be
expressed as follows:
y = W (Hx + N)
where
● W = (w1, ..., wM): 1xM vector composed of RX antenna weights.
● H = (h1, ..., hM)T: Mx1 vector composed of spatial channel coefficients. hi
indicates the coefficient of channel i, and T is a transpose operator. The
channel coefficients are used to obtain the signals that change in amplitude
and phase after passing through channels.
● N = (n1, ..., nM)T: Mx1 vector composed of received noises.
● x: TX signal.
The weights (w1, ..., wM) are used to change the beamwidth and direction. They
are calculated based on downlink channel status.
There are two methods of weight calculation:
● Weight calculation based on sounding reference signal (SRS): The calculation
procedure is illustrated in Figure 4-3.
● Weight calculation based on precoding matrix indication (PMI): The
calculation procedure is illustrated in Figure 4-4.
For low-frequency TDD cells with at least 4T4R antennas, the gNodeB can
adaptively select SRS- or PMI-based weights for the downlink so that the weights
can more accurately reflect the quality of traffic channels, increasing the downlink
throughput of cell edge users (CEUs). If the numbers of TX and RX antennas are
less than four, PMI-based weights are always used and SRS-based weights are not
supported.
SRS-based weights are used to evaluate the quality of downlink channels based
on the reciprocity between uplink and downlink channels. In a TDD system, air
interface channels naturally have reciprocity, but RF channels require calibration to
ensure the reciprocity between TX and RX channels. 3900 and 5900 series base
stations always perform channel calibration. DBS3900 LampSite and DBS5900
LampSite support channel calibration only in distributed massive MIMO cells for
which the INTER_RRU_CHN_CALIB_SW option of the
NRDUCellAlgoSwitch.ChnCalibSwitch parameter is selected.
NOTE
PMI-based weights are always used if channel calibration is not supported. If channel
calibration is not supported in a cell, a corresponding notification will be displayed after the
STR NRDUCELLCHNCALIB command is executed. Channel calibration is not supported in
the following scenarios:
● RF modules do not have the required capability.
● Channel shutdown takes effect.
● There is only one GP symbol in the self-contained slot of a LampSite cell.
● The number of pRRUs that meet calibration conditions in a LampSite cell is less than 2.
The possible causes are as follows.
● The number of available pRRUs is less than 2.
● pRRUs are far away from each other.
● The number of pRRUs whose transmit power is the same as the configured TRP
power is less than 2 in a cell. In a distributed massive MIMO cell, the TRP refers to
the master TRP.
For TDD 4T4R cells, antenna port mapping is performed as described in 4.1.3.1
Low-Frequency TDD 4T4R Cell Antenna Port Mapping. The gNodeB applies one
polarization weight to logical antenna ports 0 and 2 and another polarization
weight to logical antenna ports 1 and 3. Therefore, antenna port mapping has the
following requirements:
● Port 0 is always mapped to RRU channel A. The RRU channels corresponding
to ports 0 and 2 must be connected to a pair of physical antenna ports with
the same polarization.
● The RRU channels corresponding to ports 1 and 3 must be connected to
another pair of physical antenna ports with the same polarization.
When the logical antenna ports and the corresponding physical antenna ports
have the same polarization mode, the downlink multi-antenna performance
improves. For UEs accessing the network, the access success rate increases. For
UEs performing data transmission, the downlink throughput increases.
For TDD 8T8R cells, the mapping between logical antenna ports and RRU channels
needs to be determined based on the polarized antenna sequence. If the
connections are fixed, the mapping can be adjusted using the
NRDUCellCoverage.AntennaPortMapping parameter. For details, see 4.1.3.2
Low-Frequency TDD 8T8R Cell Antenna Port Mapping.
Table 4-1 Recommended antenna port mapping configurations for different TDD
4T4R RRU connections
Note: Physical antenna ports (+45°, –45°, +45°, –45°) indicate that the
polarization directions of physical antenna ports are +45°, –45°, +45°, and –45°,
respectively.
Figure 4-5 shows the mapping. The optimal mapping is that channels A, B, C, and
D are mapped to ports 0, 1, 2, and 3, respectively. In this case, channel A (port 0)
and channel C (port 2) are connected to a pair of +45° physical antenna ports,
and channel B (port 1) and channel D (port 3) are connected to another pair of –
45° physical antenna ports. Therefore, the optimal setting of the
NRDUCellCoverage.AntennaPortMapping parameter is 4T_0123.
Figure 4-6 Antenna port mapping for a low-frequency TDD 8T8R RRU and
Huawei TDD 8T8R passive antennas
● If a low-frequency TDD 8T8R RRU and a Huawei AAU with passive antennas
are connected through feeders as shown in Figure 4-7, it is recommended
that the NRDUCellCoverage.AntennaPortMapping parameter be set to
8T_01234567.
Figure 4-7 Antenna port mapping for a low-frequency TDD 8T8R RRU and a
Huawei AAU with passive antennas
● Enhanced PUSCH SNR level for channel estimation: This function is controlled
by the PUSCH_CE_SINR_LEVEL_ENH_SW option of the
NRDUCellPusch.PuschPerformanceSwitch parameter. For low-frequency
TDD 32T32R and 64T64R cells, this function improves the PUSCH
demodulation performance in interference scenarios and increases the uplink
cell throughput and uplink UE throughput.
● On live networks, the traffic models of different UEs differ greatly. Based on
the traffic models and signal quality, the packet length-based scheduling
optimization function preferentially schedules small-packet UEs with smaller
buffered data volume and better signal quality to improve the user-perceived
rate. This function can take effect for specific UEs, depending on the
NRDUCellPdsch.DlSchOptTimeThld parameter. If the downlink data
transmission scheduling duration estimated for a UE is less than the value of
NRDUCellPdsch.DlSchOptTimeThld, the downlink data transmission
scheduling priority of this UE is increased. Otherwise, the priority remains
unchanged. If NRDUCellPdsch.DlSchOptTimeThld is set to 0, the packet
length-based scheduling optimization function does not take effect. This
function applies only to low-frequency TDD cells with at most 8T8R.
4.2.1 Benefits
Array, diversity, and beamforming gains are offered by multiple TX and RX
antennas, as shown in Figure 4-8, Figure 4-9, and Figure 4-10. Cell coverage
improves; specifically, coverage direction is more flexible, coverage scope is wider,
and three-dimensional coverage can be provided in 32T32R and 64T64R mode. As
a result, the average UE throughput increases in both uplink and downlink.
4.2.2 Impacts
Network Impacts
In heavy-load scenarios, the BBP CPU usage is high. To reduce the BBP CPU usage
and improve gNodeB MIMO performance by optimizing the MIMO measurement
algorithm, the CHN_MEASURE_CPU_DEC_SW option of the
gNodeBParam.NrBoardPerformanceSw parameter can be selected to enable the
function of CPU usage reduction for channel measurement. CPU usage reduction
for channel measurement is not supported in high-frequency TDD.
Function Impacts
RAT Function Function Switch Reference Description
Name
4.3 Requirements
4.3.1 Licenses
None
4.3.2 Software
Prerequisite Functions
None
4.3.3 Hardware
Base Station Models
3900 and 5900 series base stations. 3900 series base stations must be configured
with the BBU3910.
DBS3900 LampSite and DBS5900 LampSite. DBS3900 LampSite must be
configured with the BBU3910.
Boards
All NR-capable main control boards and baseband processing units support this
function. For details, see the BBU technical specifications in 3900 & 5900 Series
Base Station Product Documentation.
Among BBPs, only UBBPg series boards support SRS-based weights for LampSite
4T4R cells.
RF Modules
All NR-capable RF modules support this function. For details, see the technical
specifications of RF modules in 3900 & 5900 Series Base Station Product
Documentation.
For distributed massive MIMO cells served by LampSite base stations, PMI-based
weights are always used when the pRRU596x is used and the
NRDUCell.SlotStructure parameter is set to SS1, SS21, SS51, SS81, SS101, or
SS71; SRS-based weights are supported in other situations.
4.3.4 Others
For details about connections between antennas and RRUs, see the RF cable
connection description in the RRU hardware description in 3900 & 5900 Series
Base Station Product Documentation.
//(Optional, only for 4T4R and 8T8R cells) Configuring antenna port mapping
MOD NRDUCELLCOVERAGE: NrDuCellTrpId=0, NrDuCellCoverageId=0, AntennaPortMapping=DEFAULT;
5 SU-MIMO
5.1 Principles
Uplink SU-MIMO
This function is controlled by the UL_SU_MULTI_LAYER_SW option of the
NRDUCellAlgoSwitch.SuMimoMultipleLayerSw parameter.
For low-frequency TDD cells with 32 or more RX antennas on the gNodeB side
and high-frequency TDD cells, the maximum number of PUSCH multiplexing
layers for a single UE is equal to the minimum among the number of gNodeB RX
antennas, the number of UE TX antennas, and the value of
NRDUCellPusch.MaxMimoLayerCnt.
For cells with eight or fewer RX antennas on the gNodeB side, the maximum
number of PUSCH multiplexing layers for a single UE is equal to the smaller one
between the number of gNodeB RX antennas and the number of UE TX antennas,
as listed in Table 5-1.
8R 2T 2
4R 2T 2
2R 2T 2
Downlink SU-MIMO
This function is controlled by the DL_SU_MULTI_LAYER_SW option of the
NRDUCellAlgoSwitch.SuMimoMultipleLayerSw parameter.
For low-frequency TDD cells with 32 or more TX antennas on the gNodeB side and
high-frequency TDD cells, the maximum number of PDSCH multiplexing layers for
a single UE is equal to the minimum among the gNodeB TX antennas, the number
of UE RX antennas, and the value of NRDUCellPdsch.MaxMimoLayerNum.
For cells with eight or fewer TX antennas on the gNodeB side, the maximum
number of PDSCH multiplexing layers for a single UE is equal to the smaller one
between the number of gNodeB TX antennas and the number of UE RX antennas,
as listed in Table 5-2.
8T 4R 4
4T 4R 4
2T 4R 2
5.2.1 Benefits
SU-MIMO provides the following benefits:
● Uplink SU-MIMO
If a UE supports uplink data transmission over N layers, its uplink peak rate is
theoretically N times that of data transmission over a single layer.
● Downlink SU-MIMO
If a UE supports downlink data transmission over N layers, its downlink peak
rate is theoretically N times that of data transmission over a single layer.
5.2.2 Impacts
Network Impacts
None
Function Impacts
RAT Function Function Switch Reference Description
Name
5.3 Requirements
5.3.1 Licenses
The license for SU-MIMO Multiple Layers has been purchased.
For low-frequency gNodeBs with at least 32T32R, the license for the number of
spatial multiplexing layers is also required. The maximum number cannot exceed
the licensed number. One license unit corresponds to two layers. For details about
licensing rules, see License Management.
RAT Model Description Sales Unit
For high-frequency TDD, the license for the number of spatial multiplexing layers
is also required. The maximum number cannot exceed the licensed number. One
license unit corresponds to two layers. For details about licensing rules, see License
Management.
RAT Model Description Sales Unit
5.3.2 Software
Prerequisite Functions
None
5.3.3 Hardware
Boards
All NR-capable main control boards and baseband processing units support this
function. For details, see the BBU technical specifications in 3900 & 5900 Series
Base Station Product Documentation.
RF Modules
All NR-capable RF modules support this function. For details, see the technical
specifications of RF modules in 3900 & 5900 Series Base Station Product
Documentation.
5.3.4 Others
The NRDUCell.DuplexMode parameter is not set to CELL_SUL.
NOTE
In the User Common Monitoring dialog box, you are advised to set UEID Type to Random
Value or STMSI in NSA networking and set UEID Type to 5G-Random Value or 5G-STMSI
in SA networking.
To further observe function effects, you can use the following indicators. These
indicators apply to both SU-MIMO and MU-MIMO. They can be used to observe
whether SU-MIMO has taken effect only when MU-MIMO is not enabled.
6 MU-MIMO
6.1 Principles
Spatial multiplexing on the PDSCH, PDCCH, and PUSCH for multiple UEs is
supported.
● PDSCH MU-MIMO
This function is controlled by the DL_MU_MIMO_SW option of the
NRDUCellAlgoSwitch.MuMimoSwitch parameter.
● PDCCH MU-MIMO
This function is controlled by the PDCCH_MU_SW option of the
NRDUCellAlgoSwitch.MuMimoSwitch parameter.
● PUSCH MU-MIMO
This function is controlled by the UL_MU_MIMO_SW option of the
NRDUCellAlgoSwitch.MuMimoSwitch parameter.
Table 6-1 lists the maximum number of spatial multiplexing layers for multiple
UEs.
Table 6-1 Maximum number of spatial multiplexing layers for multiple UEs
Low- 64T64R 16 4 8
frequency
TDD
Low- 32T32R 16 4 8
frequency
TDD
For PDSCH MU-MIMO, if the gNodeB has 8T8R antennas, the maximum number
of layers is not determined by the NRDUCellPdsch.MaxMimoLayerNum
parameter. If the gNodeB has more than 8T8R antennas, the maximum number of
layers is equal to the minimum between the value in the preceding table and the
value of NRDUCellPdsch.MaxMimoLayerNum.
For PDCCH MU-MIMO, the maximum number of layers is equal to the minimum
between the value in the preceding table and the value of
NRDUCellPdcch.MaxPairLayerNum.
For PUSCH MU-MIMO, if the gNodeB has 8T8R antennas, the maximum number
of layers is not determined by the NRDUCellPusch.MaxMimoLayerCnt parameter.
If the gNodeB has more than 8T8R antennas, the maximum number of layers is
equal to the minimum between the value in the preceding table and the value of
NRDUCellPusch.MaxMimoLayerCnt.
● If UEs have good SRS signal quality (for example, high SINRs and small signal
fluctuations) and low correlation, inter-UE interference can be effectively
reduced and the UEs can be paired for MU-MIMO. In this situation, MU-
MIMO can fully utilize good channel conditions to increase the system
capacity.
● If UEs have poor SRS signal quality (for example, low SINRs or large signal
fluctuations) or high correlation, inter-UE interference cannot be effectively
● For low-frequency TDD cells with at least 32T32R, the number of downlink
paired layers can be optimized based on channel information for non-
antenna-selection UEs for which PMI-based weights are used. This function is
controlled by the DL_MU_OPTIMAL_LAYER_SW option of the
NRDUCellAlgoSwitch.MuMimoSwitch parameter. LampSite base stations do
not support this function.
● For low-frequency TDD cells with 64T64R, the MCSs of paired UEs in
movement can be adjusted based on CQIs. If the SRS signal quality is high,
the MCSs can better match the actual channel quality, which increases the
throughput of these UEs. If the SRS signal quality is low, however, the cell
throughput may decrease when channel estimation is inaccurate and channel
quality fluctuates sharply. This downlink mobile MU-MIMO enhancement
function is controlled by the DL_MOBILE_MU_ENH_SW option of the
NRDUCellAlgoSwitch.UeFeatureBasedPairEnhSw parameter. LampSite base
stations do not support this function.
● For low-frequency TDD cells with at least 8T8R, the required DMRS resources
are accurately determined during RB resource allocation, thereby saving RB
resources. This function is controlled by the NRDUCellDmrs.DlMuEstRbPolicy
parameter.
● For low-frequency TDD cells with at least 32T32R, small-packet UE groups
can be merged in scenarios where small-packet UEs and large-packet UEs
need to be paired. This reduces the interference between paired UEs but may
decrease the average number of downlink paired layers. This function is
controlled by the DL_SMALL_PACKET_MERGE_SW option of the
NRDUCellDlMimo.DLMuMimoSchSupplementSw parameter.
● For low-frequency TDD cells with at least 32T32R, the
NRDUCellPdsch.DlLowTimeCorrMuSw parameter can be used to specify
whether to allow UEs with drastic channel quality fluctuation to be paired.
● For low-frequency TDD cells with at least 32T32R, the MCS optimization
policy can be selected based on the inter-stream interference estimated using
PMI-based weights. This function is controlled by the
NRDUCellPdsch.DlMimoMcsOptPolicy parameter.
● For low-frequency TDD cells with at least 32T32R, the power of each layer
can be adjusted for two rank-3 or rank-4 UEs based on the signal quality of
the respective layer. While ensuring the performance of the first two layers,
this function improves the performance of the other layers and further
increases the downlink cell throughput. This function is controlled by the
NRDUCellPdsch.MuMimoPwrAllocSwitch parameter.
● For low-frequency TDD cells with at least 8T8R, the rank for an SRS-based
weight UE to take part in pairing can be calculated using multiple methods. If
the NRDUCellDlRank.DlSrsMuMimoRankMode parameter is set to
RI_BASED_MU_RANK, the effective rank is the smaller value between the RI
reported by the UE and the value of NRDUCellDlRank.DlSrsMuMimoRank. If
the NRDUCellDlRank.DlSrsMuMimoRankMode parameter is set to
FIX_MU_RANK, the effective rank is equal to the value of
NRDUCellDlRank.DlSrsMuMimoRank.
● For low-frequency TDD cells with at least 8T8R, the rank for a PMI-based
weight UE to take part in pairing is controlled by the
NRDUCellDlRank.DlPmiMuMimoRank parameter. The effective rank is the
smaller value between the RI reported by the UE and the value of
NRDUCellDlRank.DlPmiMuMimoRank.
● For low-frequency TDD cells with at least 8T8R, MU-MIMO can be triggered
based on the measured downlink cell PRB usage. This function is controlled by
the NRDUCellDlMimo.DlMuPrbUsageThld parameter.
● For low-frequency TDD cells with at least 8T8R, SU-MIMO instead of MU-
MIMO is used when the following conditions are met: (1) the spectral
efficiency prediction function is enabled by selecting the
DL_SE_SU_MU_MIMO_ADAPT_SW option of the
NRDUCellDlMimo.DLMuMimoSchSupplementSw parameter; (2) the
spectral efficiency gain of MU-MIMO relative to SU-MIMO is less than the
value of NRDUCellDlMimo.DlMuBackToSuSeThld.
● For low-frequency TDD cells with at least 8T8R, a UE using PMI-based
weights is prohibited from pairing if the number of beams maintained for it
exceeds the value of NRDUCellDlMimo.DlMuPmiBeamNumThld. This
function increases the downlink cell throughput.
● For low-frequency TDD cells with at least 8T8R, the UE pairing policy is
optimized so that more large-packet UEs can be paired for MU-MIMO to
increase the downlink cell throughput. This function is controlled by the
NRDUCellPdsch.DlMuGatherOptSw parameter.
● For low-frequency TDD cells with at least 32T32R, the post-pairing SINRs of
antenna-selection UEs with large delay spread or large change with time can
be optimized based on information such as the channel conditions of UEs and
the correlation between UEs so that MCS indexes can be selected more
accurately for transmission. SINR optimization for downlink MU-MIMO is
controlled by the NRDUCellDlAmc.DlMuMimoSirScaleFactor parameter.
LampSite base stations do not support this function.
● For low-frequency TDD cells with at most 8T8R, delay-based scheduling
optimization can be used to increase the average downlink UE throughput.
This function is controlled by the DL_DELAY_SCH_OPT_SW option of the
NRDUCellPdsch.DlPdschAlgoSwitch parameter. It takes effect for a UE only
when the buffer size of the UE exceeds the value of
NRDUCellPdsch.DlDelaySchBufferThld parameter.
● For low-frequency TDD cells with at least 8T8R, the conditions for switching
between MCS index tables are optimized to increase the downlink user-
perceived rate. This downlink MCS index table adaptation enhancement
function is controlled by the DL_MCS_TABLE_ADAPT_ENH_SW option of the
NRDUCellDlMimo.DLMuMimoSchSupplementSw parameter.
● For low-frequency TDD cells with at least 8T8R, the scheduler accurately
allocates RB resources based on the data to be scheduled, RBs available in the
cell bandwidth, and REs available on the RBs. This reduces the downlink data
transmission time and increases the downlink user-perceived rate. This
function can be enabled by selecting the TBS_CALC_OPT_SW option of the
NRDUCellPdsch.DlPdschAlgoSwitch parameter and the
RB_ESTIMATE_OPT_SW option of the NRDUCellPdsch.DlPdschAlgoSwitch
parameter.
6.2.2 Impacts
Network Impacts
● After an increase in the proportion of UEs paired in downlink MU-MIMO,
there may be a decrease in the downlink UE throughput in the following
Function Impacts
RAT Function Function Switch Reference Description
Name
6.3 Requirements
6.3.1 Licenses
The license for MU-MIMO Basic Pairing has been purchased.
For TDD, if a gNodeB has 32T32R or more antennas, the license for the number of
spatial multiplexing layers is also required. The maximum number cannot exceed
the licensed number. One license unit corresponds to two layers. For details about
licensing rules, see License Management.
Model Description Sales Unit
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.
Prerequisite Functions
None
6.3.3 Hardware
Boards
All NR-capable main control boards and baseband processing units support this
function. For details, see the BBU technical specifications in 3900 & 5900 Series
Base Station Product Documentation.
RF Modules
All NR TDD-capable RF modules support this function. However, 2T2R and 4T4R
RF modules support MU-MIMO only in virtual MIMO (VMIMO) scenarios. To learn
which RF modules support NR TDD, see the technical specifications in 3900 &
5900 Series Base Station Product Documentation.
NOTE
6.3.4 Others
NR TDD: According to protocols, type-1 single-symbol DMRSs can be transmitted
on a maximum of four ports and therefore PUSCH MU-MIMO can provide a
maximum of four layers for UEs that support such DMRSs; type-1 double-symbol
DMRSs can be transmitted on a maximum of eight ports and therefore PUSCH
MU-MIMO can provide a maximum of eight layers for UEs that support such
DMRSs. For details, see section 6.4.1.1.3 "Precoding and mapping to physical
resources" in 3GPP TS 38.211.
//Activating MU-MIMO
MOD NRDUCELLALGOSWITCH: NrDuCellId=0,
MuMimoSwitch=UL_MU_MIMO_SW-1&PDCCH_MU_SW-0&DL_MU_MIMO_SW-1;
//Setting pairing thresholds for PDSCH MU-MIMO
MOD NRDUCELLPDSCH: NrDuCellId=0, DlPmiMuMimoSpaceIsoThld=140, DlSrsMuMimoSpaceIsoThld=50,
DlSrsMuMimoChanIsoThld=30;
MOD NRDUCELLDLMIMO: NrDuCellId=0, DlMuMimoSrsPreSinrThld=-50;
//Setting the maximum number of spatial multiplexing layers of PDSCH MU-MIMO
MOD NRDUCELLPDSCH: NrDuCellId=0, MaxMimoLayerNum=LAYER_DEFAULT;
//Setting the maximum number of spatial multiplexing layers of PDCCH MU-MIMO
MOD NRDUCELLPDCCH: NrDuCellId=0, MaxPairLayerNum=LAYER_2;
//Setting the maximum number of spatial multiplexing layers of PUSCH MU-MIMO
MOD NRDUCELLPUSCH: NrDuCellId=0, MaxMimoLayerCnt=LAYER_4;
//Configuring PDSCH MU-MIMO enhancements
MOD NRDUCELLALGOSWITCH: NrDuCellId=0, MuMimoSwitch=DL_MU_OPTIMAL_LAYER_SW-1;
MOD NRDUCELLPDSCH: NrDuCellId=0, DlPmiMuMimoSpaceIsoThld=140, DlSrsMuMimoChanIsoThld=30,
DlSrsMuMimoSpaceIsoThld=50, SrsPresinrThld=2, DlMuMimoGroupMode=ISOLATION_CORRELATION,
DlMuGatherOptSw=OFF, DlMimoMcsOptPolicy=OFF, DlLowTimeCorrMuSw=ON,
DlPdschAlgoSwitch=DL_DELAY_SCH_OPT_SW-1, DlDelaySchBufferThld=1;
MOD NRDUCELLDLMIMO: NrDuCellId=0,
DLMuMimoSchSupplementSw=DL_SMALL_PACKET_MERGE_SW-1&DL_SE_SU_MU_MIMO_ADAPT_SW-1,
DlMuPrbUsageThld=0, DlMuBackToSuSeThld=5, DlMuPmiBeamNumThld=3;
MOD NRDUCELLDMRS: NrDuCellId=0, DlMuEstRbPolicy=PSEUDOORTHOG_DMRS_ADAPT_DEDUCT;
MOD NRDUCELLDLRANK: NrDuCellId=0, DlSrsMuMimoRank=RANK_2, DlPmiMuMimoRank=RANK_2;
//(Recommended) Setting the downlink mobile MU-MIMO enhancement switch according to the default
value
MOD NRDUCELLALGOSWITCH: NrDuCellId=0,UeFeatureBasedPairEnhSw=DL_MOBILE_MU_ENH_SW-0;
//Turning on the downlink MCS index table adaptation enhancement switch
MOD NRDUCellDlMimo: NrDuCellId=0, DLMuMimoSchSupplementSw=DL_MCS_TABLE_ADAPT_ENH_SW-1;
//Turning on the downlink TBS calculation optimization switch
MOD NRDUCELLPDSCH: NrDuCellId=0, DlPdschAlgoSwitch=TBS_CALC_OPT_SW-1;
//Turning on the downlink RB estimation optimization switch
MOD NRDUCELLPDSCH: NrDuCellId=0, DlPdschAlgoSwitch=RB_ESTIMATE_OPT_SW-1;
//Configuring PUSCH MU-MIMO enhancements
MOD NRDUCELLULMIMO: NrDuCellId=0, AlignPairBigSmlPktRbThld=20, AlignPairSmlPktRbExtRatio=200,
AlignPairBigPktRbRedRatio=50, MuFreqSelSchRbRatioThld=40, MuRbRatioThld=40,
UlMuMimoAlgoSwitch=MU_BEAM_PAIR_OPT_SW-1&SML_PKT_ALIGN_PAIR_OPT_SW-1&BIG_PKT_ALIGN_PAI
R_OPT_SW-1&BIG_PKT_UE_FREQ_SEL_SCH_OPT_SW-1&MU_MULTI_SLOT_PAIR_SW-1&DIFF_FLDMRS_MAX_L
ENGTH_PAIR_SW-1;
MOD NRDUCELLULAMC: NrDuCellId=0, UlAmcAlgoSw=MU_AMC_OPT_SW-1;
MOD NRDUCELLPUSCH: NrDuCellId=0, UlPuschAlgoSwitch=UL_SCHEDULE_ENH_SW-1;
//(Optional) Configuring the PUSCH MU-MIMO pairing threshold
MOD NRDUCELLULMIMO: NrDuCellId=0, UlMuMimoCorrThld=9, UlMuMimoSinrThld=-20;
//Configuring SINR optimization for downlink MU-MIMO
MOD NRDUCELLDLAMC: NrDuCellId=0, DlMuMimoSirScaleFactor=10;
MOD NRDUCELLPDSCH: NrDuCellId=0, DlMuInitialMcsAdjValue=-2;
Monitoring. Select the corresponding base station and cell to start a monitoring
task. If the value of a monitoring item listed in Table 6-4 is greater than 1, the
corresponding function has taken effect.
Uplink MU- Max Number If the value is greater than 1, PUSCH MU-
MIMO of UL MIMO has taken effect.
monitoring Transmission
Pair Layers
In addition, you can use the following indicators to estimate the effects of PDSCH
MU-MIMO and PUSCH MU-MIMO.
● Average number of downlink MU-MIMO layers on each PRB in a cell =
N.ChMeas.MIMO.DL.Pair.Layer / N.ChMeas.MIMO.DL.Pair.PRB
● Average number of uplink MU-MIMO layers on each PRB in a cell =
N.ChMeas.MIMO.UL.Pair.Layer / N.ChMeas.MIMO.UL.Pair.PRB
● Indicators applicable to both SU-MIMO and MU-MIMO:
– Average number of downlink layers on each PRB in a cell =
N.ChMeas.MIMO.DL.Transmission.Layer / ((N.PRB.DL.DrbUsed.Avg +
N.PRB.DL.SrbUsed.Avg) x N.DL.PDSCH.Tti.Num). The scheduling results
before Msg4 during the access procedure are not considered.
– Maximum number of downlink layers on a PRB in a cell =
N.ChMeas.MIMO.DL.Transmission.Layer.Max
– Average number of uplink layers on each PRB in a cell =
N.ChMeas.MIMO.UL.Trans.Layer / (N.PRB.PUSCH.Used.Avg x
N.UL.PUSCH.Tti.Num)
– Maximum number of uplink layers on a PRB in a cell =
N.ChMeas.MIMO.UL.Trans.Layer.Max
NOTE
7.1 Principles
Cell split can be used for capacity expansion in high-capacity scenarios. After the
split, however, the capacity may not increase or even decrease due to severe intra-
NR-frequency inter-cell interference. In addition, deep fading is likely to occur in
indoor coverage scenarios, affecting user performance. Distributed massive MIMO
is introduced to address these issues. This function reduces cell edges and
mitigates inter-cell interference by combining the original n 4T4R cells into one
4nT4nR cell. This requires that the original cells provide continuous coverage and
be served by RF modules working in the same frequency band. In the massive
MIMO cell generated after the combination, MU-MIMO can be used to improve
the uplink and downlink capacity and spectral efficiency.
A common cell is served by only one transmission reception point (TRP), whereas
a distributed massive MIMO cell is served by multiple TRPs, which can be added
by running the ADD NRDUCELLTRP command.
A distributed massive MIMO cell can be served by multiple TRPs. One TRP is the
master TRP, and the others are slave TRPs. Only the master TRP needs to be
assigned baseband equipment while the slave TRPs are configured with only RF
information. The master and slave TRPs share the same baseband equipment. The
master TRP is specified by setting the NRDUCellTrp.TrpType parameter to
MASTER_DM_MIMO. A slave TRP is specified by setting the
NRDUCellTrp.TrpType parameter to SLAVE and associated with the master TRP
using the NRDUCellTrp.MasterTrpId parameter. In addition, the
DM_MIMO_SERVICE_SWITCH option of the
NRDUCellAlgoSwitch.DmMimoSwitch parameter needs to be set for the
distributed massive MIMO cell to take effect.
The gNodeB determines whether UEs are in overlapping areas based on the SRS
RSRP differences between TRPs. For UEs in overlapping areas, multiple TRPs jointly
process traffic channel data to increase the UE throughput. For UEs not in
overlapping areas, the beams of multiple TRPs can use the same time-frequency
resources of PUSCH, PDSCH, or PDCCH for spatial multiplexing if the
UL_MU_MIMO_SW, DL_MU_MIMO_SW, or PDCCH_MU_SW option of the
Table 7-1 Maximum number of spatial multiplexing layers for multiple UEs
Number of Maximum Maximum Maximum Number of
Antennas Number of Number of PUSCH MU-MIMO
After the PDSCH MU- PDCCH MU- Layers
Combination MIMO Layers MIMO Layers
16T16R or 16 4 8
more
NOTE
Distributed massive MIMO uses multiple antennas for joint transmission and reception to
reduce inter-UE interference. Theoretically, the maximum number of paired layers is equal
to the number of antennas. However, it is recommended that the number of paired layers
be less than the number of antennas to obtain more spatial freedom and achieve better
interference suppression capability. For example, if 4 TRPs with 16 antennas are configured,
the maximum number of layers is 16 in theory. However, the recommended number of
layers in a cell is less than 16 (for example, 12) to achieve better inter-UE interference
suppression capability. If 6 to 8 TRPs with 24 to 32 antennas are configured, the maximum
number of layers in a cell does not need to be limited because it is less than the number of
antennas for joint transmission and reception.
7.2.2 Impacts
Network Impacts
If more than four 4T4R cells are combined into one distributed massive MIMO cell,
the capacity of the combined cell is less than the total capacity of the original
cells.
The transmit power of pRRUs in a distributed massive MIMO cell must be the
same as the NRDUCellTrp.MaxTransmitPower parameter value set for the
master TRP. Otherwise, the throughput may decrease. For details about pRRU
power configuration, see Power Control.
Function Impacts
Function Function Switch Reference Description
Name
7.3 Requirements
7.3.1 Licenses
The following are feature and capacity license requirements.
NR0S0DLEPU00 Massive MIMO DL 2-Layers Extended Processing Unit per 2 Layers per
License (NR) Cell
NR0S0ULEPU00 Massive MIMO UL 2-Layers Extended Processing Unit per 2 Layers per
License (NR) Cell
NR0SDMMIMO03 Distributed Massive MIMO for 5000 Series LampSite per Carrier per
pRRU (NR) pRRU
The maximum number of spatial multiplexing layers cannot exceed the licensed
number. One license unit corresponds to two layers. For details about licensing
rules, see License Management.
7.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.
Prerequisite Functions
None
7.3.3 Hardware
Base Station Models
DBS3900 LampSite and DBS5900 LampSite. DBS3900 LampSite must be
configured with the BBU3910.
Boards
All NR-capable main control boards and NR TDD-capable UBBPg2a/UBBPg3/
UBBPg3a/UBBPg3b boards support this function. For details, see LampSite BBU
Hardware Description in 3900 & 5900 Series Base Station Product Documentation.
NOTE
One BBP supports only one distributed massive MIMO cell. It does not support mixed
configuration of distributed and non-distributed massive MIMO cells.
RF Modules
All NR-capable LampSite Pro pRRUs, except the pRRU592x, pRRU593x, and
pRRU595x, support this function. For details, see the technical specifications of RF
modules in 3900 & 5900 Series Base Station Product Documentation.
7.3.4 Others
Cells must work in TDD mode. That is, the NRDUCell.DuplexMode parameter
must be set to CELL_TDD.
Distributed massive MIMO cells can be served only by 4T4R TRPs, not by TRPs in
other TX/RX modes or pRRUs in different TX/RX modes.
In single-carrier networking, each distributed massive MIMO cell can be served by
a maximum of 16 TRPs. In multi-carrier networking (with multiple carriers on the
same pRRU), each distributed massive MIMO cell can be served by a maximum of
8 TRPs; in addition, these TRPs must be configured on BBPs in the same BBU.
Each distributed massive MIMO cell can be served by a maximum of 96 pRRUs.
8.1 Principles
Hybrid beamforming, including analog beamforming, is used in high frequency
bands. Generally, all TX/RX channels form one analog beam to enhance coverage.
Therefore, only one analog beam is used in a high-frequency cell at a time.
("beam" hereinafter refers to "analog beam" unless otherwise stated.) In addition,
only one optimal beam can be selected for a UE in the cell. For details about how
to select an optimal beam, see mmWave Beam Management (High-Frequency
TDD). As multiple beams cannot be scheduled at the same time, only UEs in one
beam can be scheduled in one slot and spectrum resources cannot be fully
utilized. To improve spectral efficiency, multi-beam frequency division multiplexing
(FDM) is introduced.
Multi-beam FDM is enabled when the VOL_BASED_BEAM_MULTIPLEX_SW option
of the NRDUCellAlgoSwitch.BeamMultiplexSwitch parameter is selected.
Different TX/RX channels form different beams. An RF module with four TX/RX
channels can form a maximum of two beams while an RF module with eight
TX/RX channels can form a maximum of four beams. If a UE served by a beam
does not occupy all RB resources and its coverage is not limited, this UE can be
scheduled together with another UE in another beam in the same slot, as shown
in Figure 8-1.
For burst services, multi-beam FDM may not take effect when there are
restrictions on PDCCH beams. To avoid this, it is recommended that the
PUSCH_DTX_AGG_LVL_ADAPT_SW option of the
NRDUCellPdcch.PdcchAlgoEnhSwitch parameter be selected.
8.2.1 Benefits
When network load is heavy, it is recommended that this function be enabled to
increase the downlink PRB utilization, average downlink UE throughput, and
downlink cell traffic volume.
8.2.2 Impacts
Network Impacts
The average transmit power of RF modules changes after multi-beam FDM takes
effect.
The single-beam gains of UEs in the cell center will decrease and the downlink
IBLER and RBLER of the cell will increase after multi-beam FDM takes effect.
As an antenna array is divided into multiple sub-arrays, the MCS indexes of non-
cell-edge UEs decrease but the number of scheduling times for large-packet UEs
may increase. As the MCS indexes of large-packet UEs are higher than those of
other UEs, the average MCS index of the cell will decrease or increase, depending
on the proportion of non-cell-edge large-packet UEs.
After UEs in multiple beams are scheduled at the same time, there may be
changes in the values of downlink scheduling counters, including the average CCE
aggregation level of UEs and the transmission delay of the first packet at the RLC
layer.
After multi-beam FDM takes effect, the downlink cell throughput may fluctuate. If
there are a large number of small-packet UEs or a large number of large-packet
UEs with only some CCs activated, the numbers of scheduled UEs and PRBs
increase and the downlink cell throughput may increase. However, as an antenna
array is divided into multiple sub-arrays, the average MCS index decreases; as a
result, the number of slots scheduled in each cell may increase and the downlink
cell throughput may decrease.
Function Impacts
Function Function Switch Reference Description
Name
8.3 Requirements
8.3.1 Licenses
There are no license requirements for basic functions.
8.3.2 Software
Prerequisite Functions
None
8.3.3 Hardware
Base Station Models
3900 and 5900 series base stations. 3900 series base stations must be configured
with the BBU3910.
Boards
All NR-capable main control boards and NR TDD mmWave baseband processing
units support this function. For details, see the BBU technical specifications in 3900
& 5900 Series Base Station Product Documentation.
RF Modules
RF modules must be HAAU5213, HAAU5222, or HAAU5323.
8.3.4 Others
None
9.1 Principles
Generally, the four channels of a 4R RRU are connected to those of a four-channel
antenna, as shown in Figure 9-1.
The inter-cell cable sequence detection function can be used only when at least
two cells are properly activated on the same logical site. The detection results are
reliable only when there are UEs performing uplink services properly in the cells to
be checked within the detection time. The maximum detection time is 30 minutes.
To improve the effective rate of detection results in the initial phase of site
deployment, it is recommended that the detection be performed three times, 15
minutes after cell activation, for each site. The inter-cell cable sequence detection
function is enabled when the AntPortOptDetPolicy parameter in the STR
ANTENNAPORTOPTDET command is set to INTER_CELL_DETECT.
The gNodeB searches intra-base-station cells for properly-activated cells that meet
detection requirements. It starts a detection only after finding out qualified cells.
During the detection, it determines whether the RRU of a cell is connected to the
antenna channels of another cell based on the signal correlation between RRU
channels. If so, there is an inter-cell cross-connection.
9.2.1 Benefits
The inter-cell cable sequence detection function enables customers to learn the
connections between RRUs and antennas without visiting sites. Customers need to
visit sites for troubleshooting only if inter-cell cross-connections are detected.
The signal correlation between RX channels is affected by many factors, such as
UE distribution, external interference, and cell service status.
In commercial scenarios, the average number of UEs in each cell must be greater
than 6 during the detection period and not all UEs are distributed in the
overlapping area of intra-base-station cells. The expected effective rate of physical
connection check results is 90%.
If no UEs are in a cell to be checked or UEs are at the edge of the cell, drive-test
UEs can be used for detection in the cell center. Specifically, move drive-test UEs
within an area that is of a line of sight (LOS) distance of 50 m to 100 m in front
of the antenna. During the test, ensure that the UEs are in RRC_CONNECTED
mode and each cell to be checked has certain uplink services during the cable
sequence detection.
Inter-cell cross-connections can be corrected onsite to improve downlink multi-
antenna performance. For UEs accessing the network, the access success rate
increases. For UEs performing data transmission, the downlink throughput
increases.
9.2.2 Impacts
Network Impacts
None
Function Impacts
Function Name Function Switch Reference Description
9.3 Requirements
9.3.1 Licenses
None
9.3.2 Software
Prerequisite Functions
None
9.3.3 Hardware
Base Station Models
3900 and 5900 series base stations. 3900 series base stations must be configured
with the BBU3910.
Boards
All NR TDD-capable main control boards and baseband processing units support
this function. For details, see the BBU technical specifications in 3900 & 5900
Series Base Station Product Documentation.
RF Modules
NR TDD-capable RRUs that have 4T4R or have 2T2R but can be combined for
4T4R support this function. For details, see the technical specifications of RF
modules in 3900 & 5900 Series Base Station Product Documentation.
Cells
Combined RRUs are supported but combined antennas are not supported.
Cells must be 4R cells, not any of the following cells:
● Combined cells
● Hyper cells
If an 8T8R cell is split into two 4T4R cells, the two 4T4R cells must have different
sector coverage directions.
9.3.4 Others
None
Table 9-2 Parameter values and descriptions of the inter-cell cable sequence
detection results
If a local cell has a cross-connection with another cell, the detection result of the
local cell is CROSSED and the Crossed NR DU Cell ID indicates the ID of the other
cell. If a cell has no cross-connection, the detection result of this cell is CORRECT.
If the detection fails due to another reason, a corresponding detection result listed
in Table 9-2 is displayed.
If an inter-cell cable sequence detection succeeds, the detection results of the
checked cells are displayed. If the next inter-cell cable sequence detection fails in
some cells, the Inter-Cell Line Sequence Detection Result field shows the
corresponding errors while the Crossed NR DU Cell ID and Latest Detection
Complete Time fields show the previous successful detection results.
After a cell is reset, deactivated, or reestablished, the previous detection result is
retained. After the RST APP command is executed in a cell, the previous detection
result is no longer retained.
complete, click Export to download the detection result file. If the Inter-Cell Line
Sequence Detection Result field shows the detection results, see Table 9-2 for
the meaning and explanation.
10 Parameters
The following hyperlinked EXCEL files of parameter reference match the software
version with which this document is released.
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.
Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, FBFD-010011.
Step 3 Click OK. All parameters related to the feature are displayed.
----End
Step 1 Open the EXCEL file of the used reserved parameter list.
Step 2 On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT
columns to locate the reserved parameter. View its information, including the
meaning, values, and impacts.
----End
11 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.
● gNodeBFunction 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.
----End
12 Glossary
13 Reference Documents
● 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception"
● Technical Specifications in 3900 & 5900 Series Base Station Product
Documentation
● Energy Conservation and Emission Reduction
● UE Power Saving
● License Management
● Scheduling
● CoMP
● High Speed Mobility
● Multi-Operator Sharing
● Hyper Cell
● Cell Combination
● Cell Management
● Carrier Aggregation
● Super Uplink
● Power Control
● Coordinated Interference Management (Low-Frequency TDD)