Mimo (FDD) (5g Ran6.1 - Draft A)
Mimo (FDD) (5g Ran6.1 - Draft A)
Mimo (FDD) (5g Ran6.1 - Draft A)
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....................................................................................................................................6
4 Basic Functions of MIMO....................................................................................................... 7
4.1 Principles.................................................................................................................................................................................... 7
4.1.1 Uplink Receive Diversity.................................................................................................................................................... 7
4.1.2 Downlink Beamforming..................................................................................................................................................... 8
4.1.3 Antenna Port Mapping...................................................................................................................................................... 9
4.1.4 Other Coverage Enhancement Functions................................................................................................................. 13
4.2 Network Analysis.................................................................................................................................................................. 14
4.2.1 Benefits................................................................................................................................................................................. 14
4.2.2 Impacts.................................................................................................................................................................................. 15
4.3 Requirements......................................................................................................................................................................... 15
4.3.1 Licenses................................................................................................................................................................................. 15
4.3.2 Software................................................................................................................................................................................15
4.3.3 Hardware.............................................................................................................................................................................. 15
4.3.4 Others.................................................................................................................................................................................... 16
4.4 Operation and Maintenance............................................................................................................................................. 16
4.4.1 Data Configuration........................................................................................................................................................... 16
4.4.1.1 Data Preparation............................................................................................................................................................ 16
4.4.1.2 Using MML Commands............................................................................................................................................... 17
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 17
4.4.2 Activation Verification..................................................................................................................................................... 17
4.4.3 Network Monitoring......................................................................................................................................................... 17
5 SU-MIMO................................................................................................................................. 18
5.1 Principles.................................................................................................................................................................................. 18
7.3.2 Software................................................................................................................................................................................41
7.3.3 Hardware.............................................................................................................................................................................. 42
7.3.4 Others.................................................................................................................................................................................... 42
7.4 Operation and Maintenance............................................................................................................................................. 42
7.4.1 Data Configuration........................................................................................................................................................... 42
7.4.1.1 Data Preparation............................................................................................................................................................ 42
7.4.1.2 Using MML Commands............................................................................................................................................... 43
7.4.2 Activation Verification..................................................................................................................................................... 43
7.4.3 Network Monitoring......................................................................................................................................................... 45
8 Parameters.............................................................................................................................. 46
9 Counters.................................................................................................................................. 47
10 Glossary................................................................................................................................. 48
11 Reference Documents........................................................................................................ 49
1 Change History
Technical Changes
Change Description Parameter Change RAT Base Station Model
Classified antenna port Added the FDD 3900 and 5900 series
detection into column AntPortMapOptDetMode base stations
detection and polarization parameter to the STR
detection. For details, see 6 ANTENNAPORTOPTDET
Antenna Port Detection. command.
Added the inter-cell cable Added the FDD 3900 and 5900 series
sequence detection AntPortOptDetPolicy base stations
function. For details, see 7 parameter to the STR
Inter-Cell Cable Sequence ANTENNAPORTOPTDET,
Detection. DSP
ANTENNAPORTOPTDET,
and STP
ANTENNAPORTOPTDET
commands.
Editorial Changes
Revised descriptions.
Moved descriptions of antenna port mapping and MU-MIMO in 8T8R mode from
this document to Smart 8T8R (FDD).
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
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 FDD cells, PMI-based weights are always used and SRS-based weights are not
supported.
Table 4-1 Recommended antenna port mapping configurations for different FDD
4T4R RRU connections
RRU Channels Recommended Logical Antenna Ports
Connected to Physical NRDUCellCoverage.Ant Mapped to RRU
Antenna Ports (+45°, – ennaPortMapping Channels (A, C, D, B)
45°, +45°, –45°) Parameter Setting
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 provides a mapping example. For an FDD 4T4R RRU, the channel
sequence is A, C, D, and B. When the channels are connected to the physical
antenna ports in sequence, the optimal mapping is that channels A, B, C, and D
are mapped to ports 0, 3, 2, and 1, respectively. In this case, channel A (port 0)
and channel D (port 1) are connected to a pair of +45° physical antenna ports,
and channel B (port 3) and channel C (port 2) are connected to another pair of –
45° physical antenna ports. Therefore, the optimal setting of the
NRDUCellCoverage.AntennaPortMapping parameter is 4T_0321 or 4T_0231.
However, the default 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 B (port 1)
are connected to a pair of +45° and –45° physical antenna ports, respectively;
channel C (port 2) and channel D (port 3) are connected to another pair of –45°
and +45° physical antenna ports, respectively. Therefore, the optimal setting of the
NRDUCellCoverage.AntennaPortMapping parameter is not 4T_0123.
Table 4-2 Recommended antenna port mapping configurations for different FDD
2T2R RRU connections
RRU Channels Recommended Logical Antenna Ports
Connected to Physical NRDUCellCoverage.Ant Mapped to RRU
Antenna Ports (+45°, – ennaPortMapping Channels (RRU1 A,
45°, +45°, –45°) Parameter Setting RRU1 B, RRU2 A, RRU2
B)
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-6 provides a mapping example. The optimal mapping is that RRU1 A,
RRU1 B, RRU2 A, and RRU2 B are mapped to ports 0, 2, 1, and 3, respectively. In
this case, RRU1 A (port 0) and RRU2 A (port 1) are connected to a pair of +45°
physical antenna ports, and RRU1 B (port 2) and RRU2 B (port 3) are connected
to another pair of –45° physical antenna ports. Therefore, the optimal setting of
the NRDUCellCoverage.AntennaPortMapping parameter is 4T_0213 or 4T_0312.
However, the default mapping is that RRU1 A, RRU1 B, RRU2 A, and RRU2 B are
mapped to ports 0, 1, 2, and 3, respectively. In this case, RRU1 A (port 0) and
RRU1 B (port 1) are connected to a pair of +45° and –45° physical antenna ports,
respectively; RRU2 A (port 0) and RRU2 B (port 1) are connected to another pair
of –45° and +45° physical antenna ports, respectively. Therefore, the optimal
setting of the NRDUCellCoverage.AntennaPortMapping parameter is not
4T_0123.
Figure 4-6 Antenna port mapping for combined FDD 2T2R RRUs
4.2.1 Benefits
Significantly increasing the number of TX and RX antennas achieves higher array,
diversity, and beamforming gains, as shown in Figure 4-7, Figure 4-8, and Figure
4-9. These gains mean improved cell coverage and increased average uplink and
downlink UE throughput.
4.2.2 Impacts
Network Impacts
The BBP CPU usage is high in heavy-load scenarios. 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.
Function Impacts
None
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 FDD-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 FDD-capable RF modules support this function. For details, see the
technical specifications of RF modules in 3900 & 5900 Series Base Station Product
Documentation.
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.
In FDD 4T scenarios, tower-mounted amplifiers (TMAs) cannot be deployed in
asymmetric networking mode. This is because channel calibration fails in this
mode, affecting MIMO performance in 4T cells.
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 cells with 32 or more RX antennas on the gNodeB side, the maximum number
of PUSCH multiplexing layers for a single UE is equal to the minimum among the
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.
32R 2T 2
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 cells with 32 or more TX antennas on the gNodeB side, 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.
32T 4R 4
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
Function Name Function Switch Reference Description
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.
Model Description Sales Unit
5.3.2 Software
Prerequisite Functions
None
5.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 FDD-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 FDD-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
None
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. However, they can be used to
observe whether SU-MIMO has taken effect only when MU-MIMO is not enabled.
● 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)
● 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
6.1 Principles
polarization combinations by selecting UEs in the cell for channel estimation and
calculating the correlation between UE channels based on RSRP.
Huawei gNodeBs support antenna port (mapping configuration) detection and
reconfiguration. The total detection time ranges from 18 minutes to 24 hours.
Currently, cell-level detection and base-station-level detection are supported;
antenna port detection and reconfiguration are optional and can be performed
separately; column detection, polarization detection, and column+polarization
detection are available. These functions are controlled by the NrDuCellId,
AntPortAutoReconfigSw, and AntPortMapOptDetMode parameters in the STR
ANTENNAPORTOPTDET command and require that the AntPortOptDetPolicy
parameter in this command be set to INTRA_CELL_DETECT in advance.
● If NrDuCellId is not set to a specific value, antenna port detection or
reconfiguration is performed on the entire base station. If NrDuCellId is set to
a specific value, antenna port detection or reconfiguration is performed only
for the specified cell.
● If AntPortAutoReconfigSw is set to OFF, only antenna port detection is
performed but reconfiguration is not performed. If AntPortAutoReconfigSw
is set to ON after detection is performed, only antenna port reconfiguration is
performed but detection is no longer performed. Reconfiguration will lead to
cell reestablishment.
● AntPortMapOptDetMode is used to specify the cable sequence detection
mode.
– If AntPortMapOptDetMode is set to COLUMN, only column detection is
performed to determine which two antennas belong to the same column
combination. The detection is implemented through reception and
transmission by the antennas themselves, not requiring online UEs. After
the column detection succeeds, the DSP ANTENNAPORTOPTDET
command output shows that the column detection is complete and
displays the completion time. If polarization detection has been
successfully performed before the column detection, the command
output provides the optimal port mapping based on the column detection
result and the previous polarization detection result, shows that the
detection is complete, and displays the completion time.
– Similarly, if AntPortMapOptDetMode is set to POLAR, only polarization
detection is performed to determine which two antennas belong to the
same polarization combination. The detection requires more than one
RRC_CONNECTED UE in the cell. If there are no such UEs, the base
station continuously searches for such UEs and stops the detection after a
maximum of 24 hours. After the polarization detection succeeds, the DSP
ANTENNAPORTOPTDET command output shows that the polarization
detection is complete and displays the completion time.
– If AntPortMapOptDetMode is set to COLUMN_POLAR, the base station
performs column detection first and then polarization detection. After the
detection succeeds, the DSP ANTENNAPORTOPTDET command output
shows that the detection is complete and displays the polarization
detection completion time.
6.1.2 Examples
Figure 6-2 shows an example of antenna port detection, where the antennas
connected to channels A and D form a polarization combination and the antennas
Figure 6-3 shows an example of antenna port detection, where the antennas
connected to channels A and C form a polarization combination and the antennas
connected to channels D and B form another. According to the antenna port
mapping requirements for FDD 4T4R cells described in 4.1.3 Antenna Port
Mapping, the optimal mapping is as follows:
● Ports 0 and 1 are mapped to channels A and C, respectively. That is, ports 0
and 1 correspond to one polarization combination.
● Ports 2 and 3 are mapped to channels B and D, respectively. That is, ports 2
and 3 correspond to the other polarization combination.
● Ports 0 and 2 correspond to one column combination. Ports 1 and 3
correspond to the other column combination.
Figure 6-3 Configuration example for an FDD 4T4R RRU in cross-connection mode
6.2.1 Benefits
The antenna port detection function allows operators to adjust related parameter
values to adapt to different physical connections without conducting onsite
operations.
RX signal strength and uplink channel correlation are affected by many factors, for
example, antenna downtilt angles, propagation paths, and external interference.
Column detection does not require that there are RRC_CONNECTED UEs in a cell,
while polarization detection requires that there is at least one RRC_CONNECTED
UE in a cell. The expected effective rate of physical connection detection results is
90%. The error rate of detection results does not exceed 1% if the detection is
completed.
If no UEs are in a cell or UEs are at the cell edge, drive-test UEs can be used for
detection in the cell center. Drive-test UEs must be moved within the 150 m LOS
range of the antenna and must be in RRC_CONNECTED mode during the
detection. It is recommended that drive-test UEs keep moving. If the UEs are
stationary, the expected detection time increases.
Column detection and polarization detection are optional and can be performed
separately. You are advised to perform column detection in off-peak hours during
site deployment and then perform polarization detection using drive-test UEs to
shorten the polarization detection time. If drive-test UEs are used for polarization
detection, you are not advised to use them for other tests during the detection.
Changing the actual antenna port mapping of a cell to the optimal mapping can
improve the downlink multi-antenna performance. For UEs accessing the network,
it can increase the access success rate. For UEs performing data transmission, it
can increase the downlink throughput.
6.2.2 Impacts
Network Impacts
Adjusting the downtilt angles of antennas during detection will degrade basic
network KPIs by 30%.
If the antenna system is shared with LTE, adjusting the downtilt angles of
antennas will affect the network KPIs of LTE.
LTE and NR have the same requirements for antenna port mapping. The detection
results of LTE and NR can be used by each other. It is not recommended that LTE
and NR detections be performed at the same time. Simultaneous detections will
increase the LTE or NR detection failure rate. That is, the STR CRSPORTOPTDET
command on the LTE side and the STR ANTENNAPORTOPTDET command on the
NR side cannot be executed at the same time. Only after one of the detections is
completed can the other detection be performed.
The uplink peak rate of UEs selected for cable sequence detection decreases
during polarization detection. The polarization detection time is about 5 minutes
to 24 hours while the column detection time is about 15 minutes.
Function Impacts
Function Name Function Switch Reference Description
6.3 Requirements
6.3.1 Licenses
None
6.3.2 Software
Prerequisite Functions
Function Function Switch Reference Description
Name
Note: The antennas support remote electrical tilt (RET) control, and the RRU
ports that support RET control are correctly connected to the antenna ports. The
following provides an example for setting an antenna device number.
//Querying the device number of the RET antenna used by the cell
LST RET:;
//Querying the cabinet, subrack, and slot numbers of the RRUs used by the cell
LST RRU:;
//Binding the RET antenna to the RRUs
//(1) For an RRU (RRU 60) that does not share the antenna system with others
MOD
RETSUBUNIT:DEVICENO=0,SUBUNITNO=1,CONNCN1=0,CONNSRN1=60,CONNSN1=0,CONNPN1=R0A;
//(2) For two 4T4R RRUs (RRUs 60 and 61) that share the same antenna system
MOD
RETSUBUNIT:DEVICENO=0,SUBUNITNO=1,CONNCN1=0,CONNSRN1=60,CONNSN1=0,CONNPN1=R0A,CO
NNCN2=0,CONNSRN2=61,CONNSN2=0,CONNPN2=R0A;
6.3.3 Hardware
Boards
All NR-capable main control boards and NR FDD-capable baseband processing
units support this function. For details, see the BBU technical specifications in 3900
& 5900 Series Base Station Product Documentation.
RF Modules
In addition to the RRU5501/RRU5502/RRU5502w, 4T4R RRUs and 2T2R/2T4R
RRUs that can be combined for 4T4R also support this function. For details, see
the technical specifications of RF modules in 3900 & 5900 Series Base Station
Product Documentation.
Cells
Only 4H1V antennas, not 2H2V antennas, can be used. Combined RRUs are
supported but combined antennas are not supported.
Polarization detection is suspended when the uplink PRB usage exceeds 40% in a
cell with a bandwidth of 5 MHz or when the uplink PRB usage exceeds 30% in a
cell with a bandwidth greater than 5 MHz. Polarization detection continues when
the PRB usage decreases. This avoids the impact of antenna port detection on
heavy-load cells.
6.3.4 Others
None
MOD RETSUBUNIT:DEVICENO=0,SUBUNITNO=1,CONNCN1=0,CONNSRN1=60,CONNSN1=0,CONNPN1=R0A;
//(2) For two 4T4R RRUs (RRUs 60 and 61) that share the same antenna system
MOD
RETSUBUNIT:DEVICENO=0,SUBUNITNO=1,CONNCN1=0,CONNSRN1=60,CONNSN1=0,CONNPN1=R0A,CONN
CN2=0,CONNSRN2=61,CONNSN2=0,CONNPN2=R0A;
7.1 Principles
Generally, the four channels of a 4R RRU are connected to those of a four-channel
antenna, as shown in Figure 7-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.
7.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.
7.2.2 Impacts
Network Impacts
None
Function Impacts
Function Name Function Switch Reference Description
7.3 Requirements
7.3.1 Licenses
None
7.3.2 Software
Prerequisite Functions
None
7.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 FDD-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 FDD-capable RRUs that have 2T4R/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.
7.3.4 Others
None
Table 7-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 7-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 7-2 for
the meaning and explanation.
8 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
9 Counters
The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● 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
10 Glossary
11 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
● Cell Combination
● Cell Management
● Carrier Aggregation