Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Issue 02
Date 2019-01-21
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: http://www.huawei.com
Email: support@huawei.com
Contents
1 Change History.............................................................................................................................. 1
1.1 eRAN13.1 02 (2019-01-21)............................................................................................................................................1
1.2 eRAN13.1 01 (2018-04-10)............................................................................................................................................1
1.3 eRAN13.1 Draft C (2018-03-30)....................................................................................................................................1
1.4 eRAN13.1 Draft B (2018-02-05) (FDD)........................................................................................................................ 2
1.5 eRAN13.1 Draft B (2018-02-05) (TDD)........................................................................................................................2
1.6 eRAN13.1 Draft A (2017-12-29) (FDD)........................................................................................................................2
1.7 eRAN13.1 Draft A (2017-12-29) (TDD)....................................................................................................................... 3
3 Overview......................................................................................................................................... 7
3.1 Definition........................................................................................................................................................................7
3.2 Benefits........................................................................................................................................................................... 7
4 Downlink MIMO........................................................................................................................ 11
4.1 Downlink Transmission................................................................................................................................................ 11
4.1.1 Transmission Solutions and Modes........................................................................................................................... 13
4.1.2 Transmission Mode Configuration............................................................................................................................ 14
4.1.2.1 Initial Transmission Modes.................................................................................................................................... 14
4.1.2.2 Transmission Modes in Scheduling........................................................................................................................15
4.1.3 Network Analysis...................................................................................................................................................... 16
4.1.3.1 Benefits................................................................................................................................................................... 16
4.1.3.2 Impacts....................................................................................................................................................................16
4.1.4 Requirements............................................................................................................................................................. 17
4.1.4.1 Licenses.................................................................................................................................................................. 17
4.1.4.2 Software..................................................................................................................................................................17
4.1.4.3 Hardware................................................................................................................................................................ 17
4.1.4.4 Others......................................................................................................................................................................18
4.1.5 Operation and Maintenance.......................................................................................................................................18
4.1.5.1 Data Configuration................................................................................................................................................. 18
4.1.5.1.1 Data Preparation.................................................................................................................................................. 18
4.6.2.1 Benefits................................................................................................................................................................... 37
4.6.2.2 Impacts....................................................................................................................................................................37
4.6.3 Requirements............................................................................................................................................................. 38
4.6.3.1 Licenses.................................................................................................................................................................. 38
4.6.3.2 Software..................................................................................................................................................................38
4.6.3.3 Hardware................................................................................................................................................................ 38
4.6.3.4 Networking............................................................................................................................................................. 38
4.6.3.5 Others......................................................................................................................................................................39
4.6.4 Operation and Maintenance.......................................................................................................................................40
4.6.4.1 Data Configuration................................................................................................................................................. 40
4.6.4.1.1 Data Preparation.................................................................................................................................................. 40
4.6.4.1.2 Using MML Commands...................................................................................................................................... 41
4.6.4.1.3 Using the CME.................................................................................................................................................... 42
4.6.4.2 Verification and Monitoring................................................................................................................................... 42
4.7 DL 4x4 MIMO..............................................................................................................................................................42
4.7.1 Principles................................................................................................................................................................... 42
4.7.2 Network Analysis...................................................................................................................................................... 43
4.7.2.1 Benefits................................................................................................................................................................... 43
4.7.2.2 Impacts....................................................................................................................................................................44
4.7.3 Requirements............................................................................................................................................................. 44
4.7.3.1 Licenses.................................................................................................................................................................. 45
4.7.3.2 Software..................................................................................................................................................................45
4.7.3.3 Hardware................................................................................................................................................................ 45
4.7.3.4 Networking (FDD)................................................................................................................................................. 46
4.7.3.5 Networking (TDD)................................................................................................................................................. 47
4.7.3.6 Others......................................................................................................................................................................48
4.7.4 Operation and Maintenance.......................................................................................................................................49
4.7.4.1 Data Configuration................................................................................................................................................. 49
4.7.4.1.1 Data Preparation.................................................................................................................................................. 49
4.7.4.1.2 Using MML Commands (FDD).......................................................................................................................... 50
4.7.4.1.3 Using MML Commands (TDD).......................................................................................................................... 51
4.7.4.1.4 Using the CME.................................................................................................................................................... 52
4.7.4.2 Verification and Monitoring................................................................................................................................... 52
4.8 TX Channel Calibration................................................................................................................................................53
5 Uplink MIMO.............................................................................................................................. 55
5.1 UL 2-Antenna Receive Diversity................................................................................................................................. 55
5.1.1 Principles................................................................................................................................................................... 55
5.1.1.1 1T2R Cell............................................................................................................................................................... 56
5.1.1.2 2T2R Cell............................................................................................................................................................... 56
5.1.2 Network Analysis...................................................................................................................................................... 58
5.1.2.1 Benefits................................................................................................................................................................... 58
5.1.2.2 Impacts....................................................................................................................................................................58
5.1.3 Requirements............................................................................................................................................................. 58
5.1.3.1 Licenses.................................................................................................................................................................. 58
5.1.3.2 Software..................................................................................................................................................................59
5.1.3.3 Hardware................................................................................................................................................................ 59
5.1.3.4 Others......................................................................................................................................................................59
5.1.4 Operation and Maintenance.......................................................................................................................................59
5.1.4.1 Data Configuration................................................................................................................................................. 59
5.1.4.1.1 Data Preparation.................................................................................................................................................. 59
5.1.4.1.2 Using MML Commands (FDD).......................................................................................................................... 60
5.1.4.1.3 Using MML Commands (TDD).......................................................................................................................... 60
5.1.4.1.4 Using the CME.................................................................................................................................................... 61
5.1.4.2 Verification and Monitoring................................................................................................................................... 61
5.2 UL 4-Antenna Receive Diversity................................................................................................................................. 62
5.2.1 Principles................................................................................................................................................................... 62
5.2.1.1 2T4R Cell (FDD)....................................................................................................................................................62
5.2.1.2 4T4R Cell............................................................................................................................................................... 64
5.2.2 Network Analysis...................................................................................................................................................... 67
5.2.2.1 Benefits................................................................................................................................................................... 67
5.2.2.2 Impacts....................................................................................................................................................................68
5.2.3 Requirements............................................................................................................................................................. 68
5.2.3.1 Licenses.................................................................................................................................................................. 68
5.2.3.2 Software..................................................................................................................................................................69
5.2.3.3 Hardware................................................................................................................................................................ 69
5.2.3.4 Others......................................................................................................................................................................69
5.2.4 Operation and Maintenance.......................................................................................................................................69
5.2.4.1 Data Configuration................................................................................................................................................. 69
5.2.4.1.1 Data Preparation.................................................................................................................................................. 69
5.2.4.1.2 Using MML Commands (FDD).......................................................................................................................... 70
5.2.4.1.3 Using MML Commands (TDD).......................................................................................................................... 71
5.2.4.1.4 Using the CME.................................................................................................................................................... 72
5.2.4.2 Verification and Monitoring................................................................................................................................... 72
5.3 UL 8-Antenna Receive Diversity (TDD)..................................................................................................................... 73
5.3.1 Principles................................................................................................................................................................... 73
5.3.2 Network Analysis...................................................................................................................................................... 74
5.3.2.1 Benefits................................................................................................................................................................... 74
5.3.2.2 Impacts....................................................................................................................................................................75
5.3.3 Requirements............................................................................................................................................................. 75
5.3.3.1 Licenses.................................................................................................................................................................. 75
5.3.3.2 Software..................................................................................................................................................................75
5.3.3.3 Hardware................................................................................................................................................................ 75
5.3.3.4 Others......................................................................................................................................................................76
5.3.4 Operation and Maintenance.......................................................................................................................................76
5.6.1 Principles................................................................................................................................................................... 92
5.6.2 Network Analysis...................................................................................................................................................... 92
5.6.2.1 Benefits................................................................................................................................................................... 92
5.6.2.2 Impacts....................................................................................................................................................................92
5.6.3 Requirements............................................................................................................................................................. 93
5.6.3.1 Licenses.................................................................................................................................................................. 94
5.6.3.2 Software..................................................................................................................................................................94
5.6.3.3 Hardware................................................................................................................................................................ 94
5.6.3.4 Others......................................................................................................................................................................94
5.6.4 Operation and Maintenance.......................................................................................................................................94
5.6.4.1 Data Configuration................................................................................................................................................. 94
5.6.4.1.1 Data Preparation.................................................................................................................................................. 94
5.6.4.1.2 Using MML Commands...................................................................................................................................... 95
5.6.4.1.3 Using the CME.................................................................................................................................................... 95
5.6.4.2 Verification and Monitoring................................................................................................................................... 96
5.7 UL 4x8 MU-MIMO (TDD).......................................................................................................................................... 97
5.7.1 Principles................................................................................................................................................................... 97
5.7.2 Network Analysis...................................................................................................................................................... 98
5.7.2.1 Benefits................................................................................................................................................................... 98
5.7.2.2 Impacts....................................................................................................................................................................98
5.7.3 Requirements............................................................................................................................................................. 99
5.7.3.1 Licenses.................................................................................................................................................................. 99
5.7.3.2 Software................................................................................................................................................................100
5.7.3.3 Hardware.............................................................................................................................................................. 100
5.7.3.4 Others....................................................................................................................................................................100
5.7.4 Operation and Maintenance.....................................................................................................................................100
5.7.4.1 Data Configuration............................................................................................................................................... 101
5.7.4.1.1 Data Preparation................................................................................................................................................ 101
5.7.4.1.2 Using MML Commands.................................................................................................................................... 101
5.7.4.1.3 Using the CME.................................................................................................................................................. 101
5.7.4.2 Verification and Monitoring................................................................................................................................. 102
5.8 UL SU-MIMO............................................................................................................................................................ 103
5.8.1 Principles................................................................................................................................................................. 103
5.8.1.1 Uplink Transmission Modes.................................................................................................................................103
5.8.1.2 Rank Selection...................................................................................................................................................... 103
5.8.1.3 SRS Configuration Policy (TDD).........................................................................................................................104
5.8.2 Network Analysis.................................................................................................................................................... 104
5.8.2.1 Benefits................................................................................................................................................................. 104
5.8.2.2 Impacts..................................................................................................................................................................104
5.8.3 Requirements........................................................................................................................................................... 106
5.8.3.1 Licenses................................................................................................................................................................ 106
5.8.3.2 Software................................................................................................................................................................106
6 Parameters................................................................................................................................... 114
7 Counters...................................................................................................................................... 194
8 Glossary....................................................................................................................................... 264
9 Reference Documents............................................................................................................... 265
1 Change History
This chapter describes changes not included in the "Parameters", "Counters", "Glossary", and
"Reference Documents" chapters. These changes include:
l Technical changes
Changes in functions and their corresponding parameters
l Editorial changes
Improvements or revisions to the documentation
Technical Changes
None
Editorial Changes
Revised descriptions in the document.
Technical Changes
None
Editorial Changes
Optimized descriptions in this document.
Technical Changes
None
Editorial Changes
l Added deactivation command examples. For details, see the respective "Using MML
Commands" sections.
l Described TX channel calibration. For details, see 4.8 TX Channel Calibration.
l Optimized descriptions in this document.
Technical Changes
None
Editorial Changes
Revised descriptions in this document.
Technical Changes
None
Editorial Changes
Revised descriptions in this document.
Technical Changes
Change Description Parameter Change Base Station
Model
Editorial Changes
Incorporated both FDD and TDD descriptions into this document.
Reorganized this document using a new template.
Technical Changes
None
Editorial Changes
Incorporated both FDD and TDD descriptions into this document.
Reorganized this document using a new template.
3 Overview
3.1 Definition
Multiple-input multiple-output (MIMO) refers to the use of multiple antennas for
transmission and reception in a cell. Multiple antenna configurations are expressed in the
form mxn MIMO, where m represents the number of transmit (TX) antennas and n represents
the number of receive (RX) antennas. For example, downlink 2x2 MIMO means that the
eNodeB uses two antennas for transmission and the UE uses two antennas for reception;
downlink 4x4 MIMO means that the eNodeB uses four antennas for transmission and the UE
uses four antennas for reception.
NOTE
In this document, multiple antennas refer to multiple TX/RX ports, not multiple physical antennas.
3.2 Benefits
Table 3-1 lists the benefits provided by multiple-antenna reception and transmission.
Array Gains
Array gains are achieved by utilizing the correlation between signals and non-correlation
between noises on different antennas. The signals are combined to increase the average signal
to interference plus noise ratio (SINR) and improve reception quality, as shown in Figure 3-1.
Multiplexing Gains
Multiplexing gains are provided by multiple spatial channels. This increases cell throughput
by using multiple antennas, without the need for additional bandwidth or transmit power, as
shown in Figure 3-2.
Diversity Gains
Diversity gains are achieved by taking advantage of the non-correlation between deep fading
on different antennas. The signals are combined to reduce fading and improve reception
quality, as shown in Figure 3-3.
Power Gains
Power gains are offered by multiple TX antennas in noise-limited scenarios to increase the
SINR at the RX end and improve reception quality.
4 Downlink MIMO
The number of CRS ports cannot exceed the number of configured TX channels.
transmission is mainly used in scenarios with high SINRs, low channel correlations, and
UE categories of 2 or above.
l Rank
If the codeword rank is 1, the eNodeB typically uses transmit diversity. Alternatively, the
eNodeB can use transmission mode 6 (TM6), which is a special form of closed-loop
spatial multiplexing in rank 1.
If the codeword rank is greater than 1, the eNodeB uses spatial multiplexing.
l Layer mapping and precoding
Layer mapping and precoding are used to map codewords onto CRS ports.
– In layer mapping, codewords are mapped onto layers. The number of layers (also
called MIMO layers) is determined by the rank. The maximum number of layers is
determined by the number of CRS ports, as shown in Table 4-1.
– In precoding, layered data streams are mapped onto CRS ports.
l CRS port
CRS ports are logical antenna ports. According to protocols, a cell can be configured
with one, two, or four CRS ports. The number of CRS ports is specified by the
Cell.CrsPortNum parameter. Table 4-1 describes the logical antenna ports used as CRS
ports.
Example
Figure 4-2 illustrates layer mapping and precoding when the number of CRS ports is four.
Table 4-3 describes the available transmission solutions with four CRS ports in different
transmission modes.
2 4 4
2 4 4
TM3 TM3
TM4 TM4
TM6 TM6
CL_ADAPTIVE TM4
l TM9 is suitable for 2T cells with adaptive single frequency network (SFN) enabled and
4T cells with multi-user MIMO (MU-MIMO) enabled.
l TM10 is suitable for 4T cells with adaptive SFN enabled.
For the applications of TM9 and TM10 in adaptive SFN cells, see SFN. For details about MU-
MIMO in TM9 in 4T cells, see eMIMO (FDD).
4.1.3.1 Benefits
Transmission modes need to be configured based on network situations. Open-loop adaptation
is recommended for the following types of cells:
l Cells served by combined RRUs
l Cells with the "RRU Channel Cross Connection Under MIMO" function enabled
l Cells with the high speed mobility function enabled
l Cells with a radius of over 100 km (FDD)
4.1.3.2 Impacts
Network Impacts
None
Function Impacts
RAT Function Function Switch Reference Description
Name
4.1.4 Requirements
4.1.4.1 Licenses
None
4.1.4.2 Software
Prerequisite Functions
None
4.1.4.3 Hardware
Transmission modes in different MIMO cells have different hardware requirements. For
details, see the descriptions of specific downlink MIMO features.
4.1.4.4 Others
None
Activation Verification
Enable a UE to access the network. Start Uu interface tracing on the U2000 client and check
the transmissionMode information element (IE) in the RRC_CONN_SETUP message. Table
4-7 lists the results indicating that the eNodeB has successfully delivered transmission mode
information. Figure 4-3 shows an example IE value contained in the message.
Table 4-7 IE values indicating that transmission modes have taken effect
tm2 TM2
tm3 TM3
tm4 TM4
tm6 TM6
Network Monitoring
N/A
NOTE
CRS port mapping can be understood as mapping CRS ports onto the TX ports of RF modules. The
sequence of TX/RX ports of an RF module is fixed. For details, see the hardware description of the
corresponding RF module.
Using the same setting for the Cell.CrsPortMap parameter results in different CRS port
sequences on a 4T RRU and two combined 2T RRUs.
l For a 4T RRU, the digital sequence (ports 0, 1, 2, and 3) indicates the CRS port sequence
on channels A, B, C, and D. However, the default channel sequence on RRU hardware is
ACDB.
l For two combined 2T RRUs, the digital sequence (ports 0, 1, 2, and 3) indicates the CRS
port sequence on channels A, B, A, and B.
For example, if the Cell.CrsPortMap parameter is set to 4T4P_0213, then:
l For a 4T RRU, the theoretical channel sequence and CRS port sequence are .
are . The actual sequences are the same as the theoretical sequences.
NOTE
The CRS port mapping principle for 4T2P cells is similar to that for 4T4P cells. The principle is not
described here but the actual sequences indicated by the parameter settings are provided in this table.
4T1P cells do not require CRS port mapping. The Cell.CrsPortMap parameter needs to be set to
NOT_CFG.
If a cell is set up on an LBBPc, the number of CRS ports is equal to the number of physical antennas and
the Cell.CrsPortNum parameter does not take effect. For example, if the LBBPc is configured to
support 2T mode, the number of CRS ports is always 2, regardless of the Cell.CrsPortNum parameter
value.
The mapping of CRS ports onto physical antennas is determined by the TX channel sequence
and the antenna connection mode. For example, the channel sequence of an integrated RRU is
(A, B, C, D). CRS ports 0, 2, 3, and 1 of the integrated RRU are mapped onto physical
antennas +45°, -45°, +45°, and -45° respectively by default.
The mapping of CRS ports onto TX channels is specified by the Cell.CrsPortMap parameter.
NOTE
The LBBPc does not support CRS port mapping. The parameter value NOT_CFG takes effect
regardless of the actual setting of Cell.CrsPortMap.
4TnR Cell
For the LBBPc, the Cell.CrsPortMap parameter can only be set to NOT_CFG because the
LBBPc does not support CRS port transmit sequence changes. For the LBBPd/UBBP/
UBBPe/UBBPei, the Cell.CrsPortMap parameter can be set to one of the CRS port transmit
sequences listed in the following table. Note that the Cell.CrsPortNum parameter must be set
to the number of CRS ports.
0, 2, 1, 3 4T4P_0213
0, 2, 3, 1 4T4P_0231
0, 1, 2, 3 4T4P_0123
0, 1, 3, 2 4T4P_0132
0, 1, 1, 0 4T2P_0110
0, 1, 0, 1 4T2P_0101
0, 0, 1, 1 4T2P_0011
8TnR Cell
For the LBBPd/UBBP/UBBPe/UBBPei, the Cell.CrsPortMap parameter can be set to one of
the CRS port transmit sequences listed in the following table. Note that the Cell.CrsPortNum
parameter must be set to the number of CRS ports.
0, 0, 0, 0, 1, 1, 1, 1 8T2P_00001111
0, 0, 1, 1, 0, 0, 1, 1 8T2P_00110011
0, 1, 0, 1, 0, 1, 0, 1 8T2P_01010101
0, 0, 1, 1, 2, 2, 3, 3 8T4P_00112233
0, 1, 2, 3, 0, 1, 2, 3 8T4P_01230123
When the Cell.CrsPortMap parameter is set to 8TnP_abcdefgh, CRS ports a to h are mapped
onto TX channels 1 to 8. If abcdefgh contains duplicate digits, the corresponding CRS port
signal is sent from multiple TX channels. The default value of this parameter is NOT_CFG.
For 8T4P and 8T2P cells, it is recommended that the Cell.CrsPortMap parameter be set to its
default value NOT_CFG for both wide-beam and non-wide-beam antennas.
4.4.1 Principles
The Cell.CrsPortMap parameter setting may not be the optimum. The optimal mapping
principles are:
l The antennas for CRS ports 0 and 2 form a no-spacing antenna combination. The
antennas for CRS ports 1 and 3 form another.
l The antennas for CRS ports 0 and 1 form a co-polarization antenna combination. The
antennas for CRS ports 2 and 3 form another.
Huawei eNodeBs support CRS port mapping detection and reconfiguration. This function is
controlled by the GlobalProcSwitch.AutoRecfgSwitch parameter.
l If this switch is on, the eNodeB operates based on whether CRS port mapping detection
is successful. The detection result can be queried using the DSP CRSPORTOPTDET
command.
– If successful (that is, CRS Antenna Port Opt Mapping Detection Result is
COMPLETE) and the current Cell.CrsPortMap parameter setting is not the
optimum, the eNodeB automatically reconfigures this parameter.
– If unsuccessful (that is, CRS Antenna Port Opt Mapping Detection Result is not
COMPLETE), the eNodeB does not perform any processing.
l If this switch is off, the eNodeB checks the Cell.CrsPortMap parameter setting and
detects the optimal mapping but does not reconfigure this parameter.
– The method of detecting no-spacing antenna combinations is controlled by the
GlobalProcSwitch.ColumnDetectMethod parameter.
n If this parameter is set to CORRELATION, the eNodeB detects no-spacing
antenna combinations based on the differences in RX signal correlation
between antennas. This process requires the adjustment of antenna downtilt
angles.
n If this parameter is set to ISOLATION, the eNodeB detects no-spacing
antenna combinations based on the differences in isolation between antennas.
This process does not require the adjustment of antenna downtilt angles.
– During the detection, the eNodeB identifies co-polarization antenna combinations
by selecting UEs in a cell for channel estimation and calculating the correlation
between channels. The number of UEs selected per cell per hour is specified by the
GlobalProcSwitch.CrsAntPortOptDetUserNum parameter.
n Selecting a larger number of UEs will result in more accurate detection results
because there are more samples for channel estimation. However, it may affect
resource allocation in the cell.
4.4.1.2 Example
The connections between antennas and RRUs are shown in Figure 4-7. The initial
configuration is presented in the left part of the figure. The Cell.CrsPortMap parameter is set
to 4T4P_0321 and the mapping between CRS ports and TX channels is . The
antennas for CRS ports 0 and 2 form a co-polarization antenna combination, and the antennas
for CRS ports 1 and 3 form another. However, the two combinations should be no-spacing
antenna combinations to ensure transmit diversity gains.
The optimal setting obtained after CRS port mapping detection is 4T4P_0213 and the
mapping between CRS ports and TX channels is , as shown in the right part of the
figure.
4.4.2.1 Benefits
The CRS port mapping detection and reconfiguration function allows operators to adjust
related parameters to adapt to different physical connections without conducting onsite
operations.
The expected detection completion rate is 90%. There may be no detection results after
multiple detections. It is recommended that the electrical downtilt angles of antennas be
configured for cells. Physical connections between antennas and RF modules are detected
based on RX signal strength changes on each antenna at different downtilt angles and
correlation between uplink channels of the UE. RX signal strength and uplink channel
correlation are affected by many factors, for example, antenna downtilt angles, propagation
paths, and external interference.
Therefore, there may be no results after a detection. In this case, multiple detections are
required. If there are still no results after multiple detections, onsite operations are required
because the ambient environments are too complex. When 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. Direct these UEs to
the antennas and move them within the range of 50 m to 100 m. During this process, ensure
that the UEs are in RRC_CONNECTED mode.
The detection result error rate does not exceed 1% if detections are successfully completed.
The User Downlink Average Throughput increases by 1% to 5% in cells where the actual
CRS port mapping is changed to the optimal mapping.
4.4.2.2 Impacts
Network Impacts
If the GlobalProcSwitch.ColumnDetectMethod parameter is set to CORRELATION, the
downtilt angles of antennas require adjustment during detection and the basic network KPIs
of LTE will deteriorate by 30%.
If the antenna system is shared by GSM, UMTS, and LTE, adjusting the downtilt angles of
antennas will affect the network KPIs of GSM and UMTS.
Function Impacts
None
4.4.3 Requirements
4.4.3.1 Licenses
None
4.4.3.2 Software
Prerequisite Functions
None
4.4.3.3 Hardware
Boards
4T4R BBPs can be used, for example, LBBPd2, UBBPd3, UBBPd4, or UBBPd5.
RF Modules
4T4R RF modules or 2T4R RF modules combined for 4T4R can be used.
2T2R RF modules can be used only when certain conditions are met. To find out whether a
2T2R RF module can be used, perform the following steps:
1. Run the DSP CELLPHYTOPO command to obtain the cabinet, subrack, and slot
numbers of an RF module.
2. Run the DSP BRDMFRINFO command and check the Description field.
If the field value is V3, V6, or KUNLUN, the RF module supports this function.
The active antenna unit (AAU) does not support this function.
Cells
Cells must be served by integrated 4T4R RF modules or RF modules combined for 4T4R.
The following cells are not supported:
l 2T2R cells
l 8T8R cells
l SFN cells
l Cells generated by dividing signals of an RRU and directing them to multiple antennas
This function is not suitable for scenarios with software-defined antennas, vertically stacked
antennas, or 4T6S.
If the GlobalProcSwitch.ColumnDetectMethod parameter is set to CORRELATION, CRS
port detection and reconfiguration can be performed in cells that meet the following
conditions:
l The cell bandwidth is 5 MHz or higher, and integrated 4T4R antennas are used.
l The antennas support remote electrical tilt (RET) control, and the RRU ports that support
RET control are correctly connected to the antenna ports.
l In separate-MPT scenarios, the RET antennas are configured on the LTE side so that
downtilt angles can be automatically adjusted and CRS ports can be reconfigured.
If the GlobalProcSwitch.ColumnDetectMethod parameter is set to ISOLATION, CRS port
detection and reconfiguration can be performed in cells with a bandwidth of 5 MHz or higher
and with integrated 4T4R antennas.
4.4.3.4 Others
None
CRS Ant Port Opt GlobalProcSwitch.CrsAnt For drive tests in new cells, you
Mapping Detection User PortOptDetUserNum are advised to set this parameter
Number to the maximum value.
On commercial networks, set
this parameter to its
recommended value.
//Querying the cabinet, subrack, and slot numbers of the RRU of the LTE cell
LST RRU;
//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;
Activation Verification
Step 1 Run the DSP CRSPORTOPTDET command to query the status of CRS port mapping
detection and reconfiguration.
----End
CRS Antenna Port Opt Mapping Indicates the result of CRS port mapping
Detection Result detection for optimization.
Current CRS Antenna Port Mapping Indicates the current mapping between CRS
ports and RRU channels.
Optimal CRS Antenna Port Mapping Indicates the optimal mapping between CRS
ports and RRU channels.
CRS Opt Det Completion Status Indicates the CRS detection completion status
of the entire base station.
CRS Optimization Detection Progress(%) Indicates the CRS detection progress of the
entire base station.
Table 4-11 explains the values of CRS Antenna Port Opt Mapping Detection Result.
Network Monitoring
l Detection completion rate = Number of COMPLETE cells / (Number of COMPLETE
cells + Number of FAILURE cells + Number of FAILURE_TIMEOUT cells)
In this formula, the numbers of COMPLETE, FAILURE, and FAILURE_TIMEOUT
cells are obtained from the CRS Antenna Port Opt Mapping Detection Result.
l Detection result error rate = Number of cells where the detected connections are
inconsistent with the actual connections / Total number of monitored cells
Spot checks on site can be performed to determine whether the detected connections are
consistent with the actual connections.
l User Downlink Average Throughput
4.5.1 Principles
Downlink 2x2 MIMO can be used only in cells configured with at least two CRS ports, and
only for 2R UEs (UEs with two RX channels).
4.5.2.1 Benefits
Table 4-13 describes the improvements provided by downlink 2x2 MIMO over downlink
single-input single-output (SISO).
Increases downlink peak throughput by A single UE far away from the cell center
approximately 100%. will experience high gains.
The performance of this feature cannot be ensured in closed-loop transmission mode if RRUs
are combined for use or the "RRU Channel Cross Connection Under MIMO" feature is used.
Downlink 2x2 MIMO requires that TX channels be connected to physical antennas in
different polarization directions. Otherwise, the gains may be reduced.
4.5.2.2 Impacts
Network Impacts
None
Function Impacts
None
4.5.3 Requirements
4.5.3.1 Licenses
RAT Feature ID Feature Name Model Sales Unit
In addition to feature licenses, capacity licenses are required for MIMO. Each BBP is licensed
by default to provide two baseband TX channels and two baseband RX channels for each cell.
Each RF module is licensed by default to provide two RF TX channels and two RF RX
channels. For details, see License Control Item Lists (FDD) or License Control Item Lists
(TDD).
4.5.3.2 Software
Prerequisite Functions
None
4.5.3.3 Hardware
Boards
No requirements
RF Modules
No requirements
4.5.3.4 Others
UEs must support 2R.
//Activating cell 0
ACT CELL: LocalCellId=0;
//Activating cell 0
ACT CELL: LocalCellId=0;
Activation Verification
Use the counters listed in Table 4-15 to monitor downlink MIMO with transmission modes
adaptively configured. If any counter has a non-zero value, downlink 2x2 MIMO has taken
effect.
Table 4-15 Counters used to monitor downlink MIMO with transmission modes adaptively
configured
Counter ID Counter Name Counter Description Corresponding
Feature
Network Monitoring
None
4.6.1 Principles
Downlink 4x2 MIMO can be used only in a cell configured with at least four CRS ports and
only for 2R UEs.
4.6.2.1 Benefits
Table 4-17 describes the benefits offered by downlink 4x2 MIMO.
Increases the Cell Downlink Average For a single UE, the farther away it is
Throughput by up to 15%. from the cell center, the higher the gains
are.
Increases the downlink edge throughput by
10% to 40%. For a cell, the more cell-edge users
(CEUs) it accommodates, the higher the
gains are.
Downlink 4x2 MIMO requires that the feeders between physical antennas and RRUs be of the
same type, the feeders be shorter than 75 m, and the difference in length between the feeders
be less than 1 m.
4.6.2.2 Impacts
Network Impacts
None
Feature Impacts
None
4.6.3 Requirements
4.6.3.1 Licenses
Feature ID Feature Name Model Sales Unit
In addition to feature licenses, capacity licenses are required for MIMO. Each BBP is licensed
by default to provide two baseband TX channels and two baseband RX channels for each cell.
Each RF module is licensed by default to provide two RF TX channels and two RF RX
channels. For details, see License Control Item Lists (FDD).
4.6.3.2 Software
Prerequisite Functions
None
4.6.3.3 Hardware
Boards
This function requires 4T4R BBPs.
RF Modules
No requirements
4.6.3.4 Networking
The networking requirements for downlink 4x2 MIMO are the same as those for downlink
4x4 MIMO. For details, see 4.7.3.4 Networking (FDD).
4.6.3.5 Others
UEs must support 2R.
To achieve stable benefits from closed-loop MIMO, it is recommended that RRU ports and
antenna ports be connected using jumpers (and feeders) with the same length, regardless of
whether integrated or combined RRUs are used. If one or more jumpers (and feeders) are
connected to a combiner, it is required that the difference in delay between channels induced
by the combiner and jumpers (and feeders) meet the requirements in Table 4-18.
If the inter-channel delay difference does not meet the preceding requirements, there will be a
significant deterioration in the performance of downlink 4x2 MIMO in closed-loop mode.
The larger the delay difference, the higher the degree of deterioration. Assume that the
bandwidth is 10 MHz and inter-channel delay difference is introduced at ports D and B. Then,
the delay difference affects performance, as listed in Table 4-19.
The preceding test results are reference only for estimating the impact of inter-channel delay
difference on 4T performance. The results will change with test conditions.
If combiners are required in engineering, note the following:
l It is recommended that other channels be connected to the same types of combiners to
ensure that the inter-channel delay difference meets the requirements in the preceding
table. However, this solution increases component costs and engineering costs.
l If other channels are not connected to combiners, you need to measure the delay induced
by the existing combiner, estimate the delay difference caused by the difference between
jumpers (and feeders), and use MML commands to provide delay compensation for other
channels. This solution requires a vector network analyzer (VNA) for combiner delay
measurement.
//Changing the number of CRS ports and CRS port mapping. This is a high-risk
operation and you are advised to use the following parameter settings when
setting up the cell.
MOD CELL: LocalCellId=0, CrsPortNum=CRS_PORT_4, TxRxMode=4T4R,
CrsPortMap=4T4P_0321;
//Activating cell 0
ACT CELL: LocalCellId=0;
//Changing the number of CRS ports and CRS port mapping. This is a high-risk
operation and you are advised to use the following parameter settings when
setting up the cell.
MOD CELL: LocalCellId=0, CrsPortNum=CRS_PORT_4, TxRxMode=4T4R,
CrsPortMap=4T4P_0321;
//Activating cell 0
ACT CELL: LocalCellId=0;
Activation Verification
Use the counters listed in Table 4-21 to monitor downlink MIMO with transmission modes
adaptively configured. If any counter has a non-zero value, downlink 4x2 MIMO has taken
effect.
Table 4-21 Counters used to monitor downlink MIMO with transmission modes adaptively
configured
Counter ID Counter Name Counter Description Corresponding
Feature
Network Monitoring
None
4.7.1 Principles
Downlink 4x4 MIMO can be used only in cells configured with at least four CRS ports, and
only for 4R UEs.
Table 4-22 lists the parameters used for this feature.
Downlink 4x4 MIMO supports scheduling of a maximum of four layers. If the UE category is
6 or higher (excluding 8 and 14), the maximum number of layers in TM3 or TM4 is
controlled by the Tm3Tm4Max4LayerCtrlSwitch option of the
ENodeBAlgoSwitch.CompatibilityCtrlSwitch parameter:
l If this option is selected, a maximum of four layers can be scheduled (that is, ranks 1 to 4
are supported).
l If this option is deselected, a maximum of two layers can be scheduled (that is, ranks 1
and 2 are supported).
4.7.2.1 Benefits
Downlink 4x4 MIMO increases the downlink peak throughput by approximately 100%
compared with downlink 2x2 MIMO. Table 4-23 describes the other improvements over
downlink 2x2 MIMO.
NOTE
Downlink closed-loop 4x4 MIMO depends on UE-reported ranks and precoding matrix indications
(PMIs) for scheduling and precoding. The benefits offered by this function are affected if the reported
information is inaccurate or the PMIs reported by UEs in movement cannot match channel changes
promptly.
Downlink 4x4 MIMO requires that the feeders between physical antennas and RRUs be of the
same type, the feeders be shorter than 75 m, and the difference in length between the feeders
be less than 1 m.
4.7.2.2 Impacts
Network Impacts
For TDD, the proportion of UEs in closed-loop mode and the cell throughput will increase
and the service drop rate will decrease after eRAN TDD 11.1 is upgraded to a later version.
For FDD, there is no impact.
Function Impacts
RAT Function Function Reference Description
Name Switch
4.7.3 Requirements
4.7.3.1 Licenses
RAT Feature Feature Name Model Sales Unit
ID
In addition to feature licenses, capacity licenses are required for MIMO. Each BBP is licensed
by default to provide two baseband TX channels and two baseband RX channels for each cell.
Each RF module is licensed by default to provide two RF TX channels and two RF RX
channels. For details, see License Control Item Lists (FDD) or License Control Item Lists
(TDD).
4.7.3.2 Software
Prerequisite Functions
None
4.7.3.3 Hardware
Boards
This function requires 4T BBPs. In TDD, the LBBPc does not support this function.
RF Modules
No requirements
The differences in gains when moving between the different states in Figure 4-8 and Figure
4-9 are as follows:
l From state 1 to state 2, there may be no gains or even performance loss during the
adjustment of downtilt angles and azimuths.
To achieve an overall improvement on 2T2R, ensure that the basic performance does not
deteriorate during the adjustment.
l From state 2 to state 3, there will be gains after 4T4R is deployed.
To avoid such deterioration after the reconstruction, the following networking solutions can
be used:
RRU transmit power is restricted in some countries and regions. For example, the RRU transmit power
specification is 80 w, but only 40 w is allowed by local rules and regulations. If the remaining transmit
power is allocated to the 4P cell, the total transmit power of the RRU will exceed 40 w though the
coverage will not shrink after the reconstruction. In such a case, you are advised to use the solution to
the case when an RRU has no remaining power.
l If an RRU has no remaining power, it is not recommended that downlink 4x4 MIMO be
enabled. If it is enabled, there will be negative impacts.
4.7.3.6 Others
UEs must support 4R.
To achieve stable benefits from closed-loop MIMO, it is recommended that RRU ports and
antenna ports be connected using jumpers (and feeders) with the same length, regardless of
whether integrated or combined RRUs are used. If one or more jumpers (and feeders) are
connected to a combiner, it is required that the difference in delay between channels induced
by the combiner and jumpers (and feeders) meet the requirements in Table 4-24.
If the inter-channel delay difference does not meet the preceding requirements, there will be a
significant deterioration in the performance of downlink 4x4 MIMO in closed-loop mode.
The larger the delay difference, the higher the degree of deterioration. Assume that the
bandwidth is 10 MHz and inter-channel delay difference is introduced at ports D and B. Then,
the delay difference affects performance as listed in Table 4-25.
The preceding test results are reference only for estimating the impact of inter-channel delay
difference on 4T performance. The results will change with test conditions.
If combiners are required in engineering, note the following:
l It is recommended that other channels be connected to the same types of combiners to
ensure that the inter-channel delay difference meets the requirements in the preceding
table. However, this solution increases component costs and engineering costs.
l If other channels are not connected to combiners, you need to measure the delay induced
by the existing combiner, estimate the delay difference caused by the difference between
jumpers (and feeders), and use MML commands to provide delay compensation for other
channels. This solution requires a VNA for combiner delay measurement.
//Changing the number of CRS ports and CRS port mapping. This is a high-risk
operation and you are advised to use the following parameter settings when
setting up the cell.
MOD CELL: LocalCellId=0, CrsPortNum=CRS_PORT_4, TxRxMode=4T4R,
CrsPortMap=4T4P_0321;
//Activating cell 0
ACT CELL: LocalCellId=0;
//Changing the number of CRS ports and CRS port mapping. This is a high-risk
operation and you are advised to use the following parameter settings when
setting up the cell.
MOD CELL: LocalCellId=0, CrsPortNum=CRS_PORT_4, TxRxMode=4T4R,
CrsPortMap=4T4P_0321;
//Activating cell 0
ACT CELL: LocalCellId=0;
//Activating cell 0
ACT CELL: LocalCellId=0;
Activation Verification
Use the counters listed in Table 4-27 to monitor downlink MIMO with transmission modes
adaptively configured. If any counter related to rank 3 or 4 has a non-zero value, downlink
4x4 MIMO has taken effect.
Table 4-27 Counters used to monitor downlink MIMO with transmission modes adaptively
configured
Network Monitoring
None
TX channel calibration cannot be used on combined 1T2R RRUs. Therefore, open-loop 2x2 MIMO is
recommended but closed-loop 2x2 MIMO is not recommended on commercial networks.
5 Uplink MIMO
Figure 5-1 illustrates these solutions using uplink 2-antenna reception as an example.
5.1.1 Principles
Uplink 2-antenna receive diversity requires a cell to have at least two RX channels. The two
RX channels receive the same signal of a UE from different directions to improve reception
quality.
Uplink 2-antenna receive diversity can be deployed in 1T2R or 2T2R cells. The numbers of
TX and RX channels provided by the hardware must be greater than or equal to the numbers
of TX and RX channels in the cell. The TX/RX mode of a cell is specified by the
Cell.TxRxMode parameter.
Integrated RRU
A 2T2R cell is set up on a 2T2R sector. A 2T2R sector can be served by a 2T2R RRU. Figure
5-3 illustrates the deployment.
Combined RRUs
A 2T2R sector can be served by two 1T2R RRUs. Figure 5-4 illustrates the deployment.
5.1.2.1 Benefits
Uplink 2-antenna receive diversity is a basic feature. Its benefits are not detailed here.
5.1.2.2 Impacts
Network Impacts
None
Function Impacts
None
5.1.3 Requirements
5.1.3.1 Licenses
The TX/RX capabilities of cells depend on the TX/RX capabilities of baseband processing
units (BBPs). For the TX/RX capabilities of BBPs, see Hardware Description in product
documentation.
Each BBP is licensed by default to provide two baseband TX channels and two baseband RX
channels for each cell. Each RF module is licensed by default to provide two RF TX channels
and two RF RX channels. Therefore, 2T2R cell setup does not require additional licenses.
5.1.3.2 Software
Prerequisite Functions
None
5.1.3.3 Hardware
Boards
No requirements
RF Modules
No requirements
5.1.3.4 Others
None
//Activating cell 0
ACT CELL: LocalCellId=0;
//Activating cell 0
ACT CELL: LocalCellId=0;
Activation Verification
Step 1 Start a received signal strength indicator (RSSI) monitoring task on the U2000 client to
monitor the RSSIs of antennas.
Item for Unit Value Range Description
Monitoring
UL 2-Antenna Receive Diversity The RSSIs of antennas 0 and 1 are not N/A.
----End
Network Monitoring
Monitor the counters listed in Table 5-2 and calculate the uplink cell throughput. The more
the antennas for a cell, the higher the cell throughput, under the same conditions such as the
same cell, bandwidth, and total transmit power.
1526728259 L.Thrp.bits.UL
1526728998 L.Thrp.Time.Cell.UL.HighPrecision
Monitor the counters listed in Table 5-3 to check the status of connections between antennas
and RRU ports. If the average RSSI value of antenna x is much less than those of the other
antennas, antenna x is not connected to an RRU port. In Figure 5-5, antennas 2 and 3 are not
connected to RRU ports.
5.2.1 Principles
Uplink 4-antenna receive diversity requires that a cell have at least four RX channels. The
four RX channels receive the same signal of a UE from different directions to improve
reception quality.
Uplink 4-antenna receive diversity can be deployed in 2T4R or 4T4R cells. The numbers of
TX and RX channels provided by the hardware must be greater than or equal to the numbers
of TX and RX channels in the cell. The TX/RX mode of a cell is specified by the
Cell.TxRxMode parameter.
Integrated RRU
A 2T4R cell is set up on a 2T4R sector. A 2T4R sector can be served by a 2T4R RRU. Figure
5-6 illustrates the deployment.
A 2T4R sector can also be served by a 4T4R RRU. It is recommended that channels A and B
work in TX/RX mode while channels C and D work in RX mode.
Combined RRUs
A 2T4R sector can be served by two 1T2R RRUs. Figure 5-7 illustrates the deployment.
A 2T4R sector can be served by two 2T2R RRUs. Figure 5-8 illustrates the deployment. In
this case, RRU 1 works in 2T2R mode and RRU 2 works in 0T2R mode. Compared with
1T2R+1T2R, this work mode can prevent downlink throughput from decreasing due to
inconsistent feeder lengths, losses, or other factors.
Integrated RRU
A 4T4R cell is set up on a 4T4R sector. A 4T4R sector can be served by a 4T4R RRU. Figure
5-9 illustrates the deployment.
Combined RRUs
A 4T4R sector can be served by two 2T2R RRUs. Figure 5-10 illustrates the deployment.
A 4T4R sector can be served by two 2T4R RRUs. Figure 5-11 illustrates the deployment.
For special requirements, the ports of an 8T8R RRU can be split into two groups of 4T4R
ports. Each group of 4T4R ports are connected to an 8T8R antenna to set up a 4T4R cell, as
shown in Figure 5-13.
l Preferentially select two pairs of cross-polarized antennas that are functional and not
adjacent to each other.
l Randomly select four functional RRU ports, and connect these ports (in ascending order
of sequence number) to the antennas.
l Connect the RRU's CAL calibration port and the antenna system's CAL calibration port.
5.2.2.1 Benefits
Table 5-4 describes the benefits offered by uplink 4-antenna receive diversity compared with
uplink 2-antenna receive diversity.
Weak Increases the Cell Uplink Average For a single UE, the farther
coverage, Throughput by 30% to 65%. away it is from the cell center,
medium the higher the gains are.
interference,
or high Increases the uplink edge throughput by For a cell, the more CEUs it
interference 50% to 170%. accommodates, the higher the
gains are.
Small inter- Increases the Cell Uplink Average
site distance Throughput by up to 30%.
and low
interference Increases the uplink edge throughput by
up to 60%.
Uplink 4-antenna receive diversity requires that the feeders between physical antennas and
RRUs be of the same type and the difference in length between the feeders be less than 1 m.
Otherwise, the gains may be reduced.
5.2.2.2 Impacts
Network Impacts
None
Function Impacts
None
5.2.3 Requirements
5.2.3.1 Licenses
RAT Feature ID Feature Name Model Sales Unit
In addition to feature licenses, capacity licenses are required for MIMO. Each BBP is licensed
by default to provide two baseband TX channels and two baseband RX channels for each cell.
Each RF module is licensed by default to provide two RF TX channels and two RF RX
channels. For details, see License Control Item Lists (FDD) or License Control Item Lists
(TDD).
5.2.3.2 Software
Prerequisite Functions
None
5.2.3.3 Hardware
Boards
This function requires 4R BBPs.
RF Modules
Some RF modules cannot be combined to serve a 2T4R cell. These modules are RRU3201,
RRU3203, RRU3808, and LRFU.
If two MRFUd modules are combined, the recommended mode is 2T2R+0T2R.
Cells
If two antennas are combined for use, both uplink MIMO and downlink MIMO require that
the antennas have the same azimuth and downtilt angle.
In TDD, the cell bandwidth must be greater than 5 MHz.
5.2.3.4 Others
None
Table 5-5 describes the parameters used for activation using the setup of a 4T4R cell as an
example.
//Changing the number of CRS ports and CRS port mapping. This is a high-risk
operation and you are advised to use the following parameter settings when
setting up the cell.
MOD CELL: LocalCellId=0, CrsPortNum=CRS_PORT_4, TxRxMode=4T4R,
CrsPortMap=4T4P_0321;
//Activating cell 0
ACT CELL: LocalCellId=0;
//Changing the number of CRS ports and CRS port mapping. This is a high-risk
operation and you are advised to use the following parameter settings when
setting up the cell.
MOD CELL: LocalCellId=0, CrsPortNum=CRS_PORT_4, TxRxMode=4T4R,
CrsPortMap=4T4P_0321;
//Activating cell 0
ACT CELL: LocalCellId=0;
//Activating cell 0
ACT CELL: LocalCellId=0;
Activation Verification
Step 1 Start a received signal strength indicator (RSSI) monitoring task on the U2000 client to
monitor the RSSIs of antennas.
UL 2-Antenna Receive Diversity The RSSIs of antennas 0 and 1 are not N/A.
----End
Network Monitoring
Monitor the counters listed in Table 5-6 and calculate the uplink cell throughput. The more
the antennas for a cell, the higher the cell throughput, under the same conditions such as the
same cell, bandwidth, and total transmit power.
1526728259 L.Thrp.bits.UL
1526728998 L.Thrp.Time.Cell.UL.HighPrecision
Monitor the counters listed in Table 5-7 to check the status of connections between antennas
and RRU ports. If the average RSSI value of antenna x is much less than those of the other
antennas, antenna x is not connected to an RRU port. In Figure 5-14, antennas 2 and 3 are not
connected to RRU ports.
5.3.1 Principles
Uplink 8-antenna receive diversity requires that a cell have at least eight RX channels. The
eight RX channels receive the same signal of a UE from different directions to improve
reception quality.
Uplink 8-antenna receive diversity can be deployed in 8T8R cells. The numbers of TX and
RX channels provided by the hardware must be greater than or equal to the numbers of TX
and RX channels in the cell. The TX/RX mode of a cell is specified by the Cell.TxRxMode
parameter.
An 8T8R cell is set up on an 8T8R sector. An 8T8R sector can be served by an 8T8R RRU.
Figure 5-15 illustrates the deployment. Connect the RRU's CAL calibration port and the
antenna system's CAL calibration port.
5.3.2.1 Benefits
Table 5-8 describes the benefits offered by uplink 8-antenna receive diversity compared with
uplink 4-antenna receive diversity.
Increases the Cell Uplink Average For a single UE, the farther away it is from the cell
Throughput by 10% to 30%. center, the higher the gains are.
Increases the uplink edge For a cell, the more CEUs it accommodates, the
throughput. higher the gains are.
5.3.2.2 Impacts
Network Impacts
None
Function Impacts
None
5.3.3 Requirements
5.3.3.1 Licenses
Feature ID Feature Name Model Sales Unit
In addition to feature licenses, capacity licenses are required for MIMO. Each BBP is licensed
by default to provide two baseband TX channels and two baseband RX channels for each cell.
Each RF module is licensed by default to provide two RF TX channels and two RF RX
channels. For details, see License Control Item Lists (TDD).
5.3.3.2 Software
Prerequisite Functions
None
5.3.3.3 Hardware
Boards
This function requires 8R BBPs.
RF Modules
No requirements
Cells
The cell bandwidth must be greater than 5 MHz.
5.3.3.4 Others
None
//Activating cell 0
ACT CELL: LocalCellId=0;
Activation Verification
Step 1 Start a received signal strength indicator (RSSI) monitoring task on the U2000 client to
monitor the RSSIs of antennas.
UL 2-Antenna Receive Diversity The RSSIs of antennas 0 and 1 are not N/A.
----End
Network Monitoring
Monitor the counters listed in Table 5-10 and calculate the uplink cell throughput. The more
the antennas for a cell, the higher the cell throughput, under the same conditions such as the
same cell, bandwidth, and total transmit power.
1526728259 L.Thrp.bits.UL
1526728998 L.Thrp.Time.Cell.UL.HighPrecision
Monitor the counters listed in Table 5-11 to check the status of connections between antennas
and RRU ports. If the average RSSI value of antenna x is much less than those of the other
antennas, antenna x is not connected to an RRU port. In Figure 5-16, antennas 2 and 3 are not
connected to RRU ports.
5.4.1 Principles
Uplink MU-MIMO is controlled by the UlVmimoSwitch option of the
CellAlgoSwitch.UlSchSwitch parameter. To enable 2x2 MU-MIMO in a cell, select this
option and ensure that the cell works in at least 2R mode. This feature can be used for UEs
when channel conditions are favorable.
The eNodeB attempts to pair UEs in each transmission time interval (TTI). If the pairing
succeeds, the eNodeB performs 2x2 MU-MIMO.
UE Selection
In each TTI, the eNodeB schedules UEs in sequence. If all resources are used up but some
UEs are still not scheduled, the eNodeB attempts to pair unscheduled UEs with scheduled
UEs.
Pairing Judgment
Based on the pre-pairing SINR and inter-UE channel correlation, the eNodeB calculates the
post-pairing SINR and then calculates the post-pairing spectral efficiency.
The eNodeB pairs two UEs only if the total post-pairing spectral efficiency is higher than the
total pre-pairing spectral efficiency.
5.4.2.1 Benefits
Uplink MU-MIMO provides a higher Cell Uplink Average Throughput than uplink receive
diversity. Uplink MU-MIMO can offer significant gains when the following conditions are
met:
l The PUSCH load is high. That is, the uplink physical resource block (PRB) usage
exceeds 90%.
l There are adequate PDCCH resources for UE pairing. That is, the control channel
element (CCE) usage is less than 80%.
5.4.2.2 Impacts
Network Impacts
Uplink coverage may deteriorate and CEU throughput may decrease in high interference
scenarios because more UEs are scheduled in uplink MU-MIMO.
Function Impacts
RAT Function Function Reference Description
Name Switch
FDD PSIC receiver MumimoPusch PSIC Receiver The PSIC receiver can be
TDD PsicSwitch used in uplink MU-
option of the MIMO to improve signal
CellAlgoSwitc reception quality for
h.PsicSwitch paired UEs.
parameter
5.4.3 Requirements
5.4.3.1 Licenses
Feature ID Feature Name Model Sales Unit
In addition to feature licenses, capacity licenses are required for MIMO. Each BBP is licensed
by default to provide two baseband TX channels and two baseband RX channels for each cell.
Each RF module is licensed by default to provide two RF TX channels and two RF RX
channels. For details, see License Control Item Lists (FDD).
5.4.3.2 Software
Prerequisite Functions
None
5.4.3.3 Hardware
Boards
This function requires 2R BBPs.
RF Modules
No requirements
5.4.3.4 Others
None
Activation Verification
Step 1 Start an MU-MIMO monitoring task on the U2000 client to monitor the number of UE pairs
in uplink MU-MIMO.
Item for Unit Value Range Description
Monitoring
Mimo UE Pair Pair 0 to 32000 This item indicates the total number of
Num UE pairs in all TTIs of a monitoring
period. This number increases by one
when two UEs are paired for MU-
MIMO in a TTI.
----End
Network Monitoring
Use the counters listed in Table 5-13 to monitor uplink MU-MIMO. If any counter has a non-
zero value, uplink MU-MIMO is functioning properly. If the counter values are always zero,
uplink MU-MIMO is not functioning properly.
1526728349 L.ChMeas.VMIMO.PairPRB.Succ
1526728350 L.ChMeas.VMIMO.PairPRB.Tot
5.5.1 Principles
Uplink MU-MIMO is controlled by the UlVmimoSwitch option of the
CellAlgoSwitch.UlSchSwitch parameter. To enable 2x4 MU-MIMO in a cell, select this
option and ensure that the cell works in at least 4R mode. This function can be used for UEs
when channel conditions are favorable.
The eNodeB attempts to pair UEs in each TTI. If the pairing succeeds, the eNodeB performs
2x4 MU-MIMO. Figure 5-17 shows uplink 2x4 MU-MIMO.
UE Selection
In each TTI, the eNodeB schedules UEs in sequence. If all resources are used up but some
UEs are still not scheduled, the eNodeB attempts to pair unscheduled UEs with scheduled
UEs.
Pairing Judgment
Based on the pre-pairing SINR and inter-UE channel correlation, the eNodeB calculates the
post-pairing SINR and then calculates the post-pairing spectral efficiency.
The eNodeB pairs two UEs only if the total post-pairing spectral efficiency is higher than the
total pre-pairing spectral efficiency.
Enhanced MU- CellUlschAlgo Pairs UEs that will Optimizes pairing results
MIMO .EnhancedVm achieve the highest and increases post-pairing
imoSwitch benefits after pairing. throughput.
MU-MIMO for VoLTEUeVmi Allows UEs with VoLTE Expands the VoLTE UE
VoLTE UEs moSwitch services to be involved in capacity of a cell.
option of the pairing for MU-MIMO.
CellAlgoSwitc
h.UlSchSwitch
parameter
5.5.2.1 Benefits
Uplink MU-MIMO provides a higher Cell Uplink Average Throughput than uplink receive
diversity. Uplink MU-MIMO can offer significant gains when the following conditions are
met:
l In FDD, PUSCH load is high. That is, the uplink PRB usage exceeds 90%.
l In TDD, PUSCH load is high. That is, the uplink PRB usage exceeds 65%.
l There are adequate PDCCH resources for UE pairing. That is, the CCE usage is less than
80%.
5.5.2.2 Impacts
Network Impacts
Uplink coverage may deteriorate and CEU throughput may decrease in high interference
scenarios because more UEs are scheduled in uplink MU-MIMO.
l The CCE usage and CCE allocation failure rate may increase in high load scenarios
because more UEs are scheduled in uplink MU-MIMO.
l The E-RAB setup delay may decrease in high load scenarios because UEs have more
chances to be scheduled in uplink MU-MIMO.
l The number of uplink preallocation times may increase and the number of RBs used in
uplink preallocation may also increase. This is because UEs have more chances to be
scheduled and their uplink data transmission can be completed in a shorter time when
both uplink preallocation and uplink MU-MIMO are enabled.
l The number of uplink error bits in uplink MU-MIMO may increase when the number of
pairing times is low. This is because the modulation and coding scheme (MCS) selection
mechanism for paired UEs is independent of that for unpaired UEs.
Function Impacts
RAT Function Function Switch Reference Description
Name
5.5.3 Requirements
5.5.3.1 Licenses
RAT Feature ID Feature Name Model Sales Unit
In addition to feature licenses, capacity licenses are required for MIMO. Each BBP is licensed
by default to provide two baseband TX channels and two baseband RX channels for each cell.
Each RF module is licensed by default to provide two RF TX channels and two RF RX
channels. For details, see License Control Item Lists (FDD) or License Control Item Lists
(TDD).
5.5.3.2 Software
Prerequisite Functions
None
5.5.3.3 Hardware
Boards
This function requires 4R BBPs.
In TDD, the LBBPc does not support enhanced MU-MIMO.
RF Modules
No requirements
5.5.3.4 Others
None
Activation Verification
Step 1 Start an MU-MIMO monitoring task on the U2000 client to monitor the number of UE pairs
in uplink MU-MIMO.
Mimo UE Pair Num Pair 0 to 32000 This item indicates the total number of
UE pairs in all TTIs of a monitoring
period. This number increases by one
when two UEs are paired for MU-
MIMO in a TTI.
Mimo UE Pair Num Not N/A Uplink MU-MIMO has been enabled.
----End
Network Monitoring
Use the counters listed in Table 5-17 to monitor uplink MU-MIMO. If any counter has a non-
zero value, uplink MU-MIMO is functioning properly. If the counter values are always zero,
uplink MU-MIMO is not functioning properly.
1526728349 L.ChMeas.VMIMO.PairPRB.Succ
1526728350 L.ChMeas.VMIMO.PairPRB.Tot
1526739789 L.ChMeas.VMIMO.PairPRB.Succ.VoLTE
1526739782 L.ChMeas.VMIMO.PairPRB2Layer.Succ
1526739783 L.ChMeas.VMIMO.PairPRB3Layer.Succ
1526739784 L.ChMeas.VMIMO.PairPRB4Layer.Succ
1526740469 L.ChMeas.VMIMO.Succ.SubFrameNum
5.6.1 Principles
The principles of uplink 2x8 MU-MIMO are similar to those of uplink 2x4 MU-MIMO. For
details, see 5.5.1 Principles. Uplink 2x8 MU-MIMO can work in at least 8R cells.
In 8R cells, UL CoMP UEs can be involved in pairing for MU-MIMO, depending on the
SimplePairedCompSw option of the CellAlgoSwitch.UplinkCompSwitch parameter:
l If the option is selected, UL CoMP UEs can be selected for pairing in non-SFN cells but
cannot in SFN cells.
l If this option is deselected, UL CoMP UEs are not selected for pairing and uplink MU-
MIMO takes precedence over type-1 CoMP.
5.6.2.1 Benefits
Uplink MU-MIMO provides a higher Cell Uplink Average Throughput than uplink receive
diversity. Uplink MU-MIMO can offer significant gains when the following conditions are
met:
l The PUSCH load is high. That is, the uplink physical resource block (PRB) usage
exceeds 90%.
l There are adequate PDCCH resources for UE pairing. That is, the CCE usage is less than
80%.
5.6.2.2 Impacts
Network Impacts
MU-MIMO has the following network impacts:
l Uplink coverage may deteriorate and CEU throughput may decrease in high interference
scenarios because more UEs are scheduled in uplink MU-MIMO.
l The CCE usage and CCE allocation failure rate may increase in high load scenarios
because more UEs are scheduled in uplink MU-MIMO.
l The E-RAB setup delay may decrease in high load scenarios because UEs have more
chances to be scheduled in uplink MU-MIMO.
l The number of uplink preallocation times may increase and the number of RBs used in
uplink preallocation may also increase. This is because UEs have more chances to be
scheduled and their uplink data transmission can be completed in a shorter time when
both uplink preallocation and uplink MU-MIMO are enabled.
l The number of uplink error bits in uplink MU-MIMO may increase when the number of
pairing times is low. This is because the MCS selection mechanism for paired UEs is
independent of that for unpaired UEs.
Function Impacts
Function Function Switch Reference Description
Name
5.6.3 Requirements
5.6.3.1 Licenses
Feature ID Feature Name Model Sales Unit
In addition to feature licenses, capacity licenses are required for MIMO. Each BBP is licensed
by default to provide two baseband TX channels and two baseband RX channels for each cell.
Each RF module is licensed by default to provide two RF TX channels and two RF RX
channels. For details, see License Control Item Lists (TDD).
5.6.3.2 Software
Prerequisite Functions
None
5.6.3.3 Hardware
Boards
This function requires 8R BBPs.
RF Modules
No requirements
5.6.3.4 Others
None
Activation Verification
Step 1 Start an MU-MIMO monitoring task on the U2000 client to monitor the number of UE pairs
in uplink MU-MIMO.
Item for Unit Value Range Description
Monitoring
Mimo UE Pair Num Pair 0 to 32000 This item indicates the total number of
UE pairs in all TTIs of a monitoring
period. This number increases by one
when two UEs are paired for MU-
MIMO in a TTI.
Mimo UE Pair Num Not N/A Uplink MU-MIMO has been enabled.
----End
Network Monitoring
Use the counters listed in Table 5-19 to monitor uplink MU-MIMO. If any counter has a non-
zero value, uplink MU-MIMO is functioning properly. If the counter values are always zero,
uplink MU-MIMO is not functioning properly.
1526728349 L.ChMeas.VMIMO.PairPRB.Succ
1526728350 L.ChMeas.VMIMO.PairPRB.Tot
1526739789 L.ChMeas.VMIMO.PairPRB.Succ.VoLTE
1526739782 L.ChMeas.VMIMO.PairPRB2Layer.Succ
1526739783 L.ChMeas.VMIMO.PairPRB3Layer.Succ
1526739784 L.ChMeas.VMIMO.PairPRB4Layer.Succ
1526740469 L.ChMeas.VMIMO.Succ.SubFrameNum
5.7.1 Principles
Uplink 4x8 MU-MIMO is controlled by the HighOrderVMIMOSwitch option of the
CellAlgoSwitch.UlSchSwitch parameter. To enable uplink 4x8 MU-MIMO in a cell, select
this option and ensure that the cell works in at least 8R mode. This function can be used for
UEs when channel conditions are favorable.
The eNodeB attempts to group UEs in each TTI. Specifically, it attempts UE pairing first for
uplink 2x8 MU-MIMO. If successful, it continues to attempt pairing with other UEs. If
successful, uplink 4x8 MIMO is performed.
Table 5-20 describes the functions that enhance uplink 4x8 MU-MIMO. These functions can
take effect only when MU-MIMO has been enabled.
MU-MIMO for VoLTEUeVmi Allows UEs with VoLTE Expands the VoLTE UE
VoLTE UEs moSwitch services to be involved in capacity of a cell.
option of the UE pairing.
CellAlgoSwitc
h.UlSchSwitch
parameter
The maximum number of UEs that can be involved in UE pairing for uplink 4x8 MU-MIMO
is specified by the CellUlSchAlgo.MaxLayerHOVMIMO parameter.
In 8R cells, UL CoMP UEs can be involved in UE pairing, depending on the
SimplePairedCompSw option of the CellAlgoSwitch.UplinkCompSwitch parameter:
l If this option is selected, UL CoMP UEs can be involved in UE pairing but only a
maximum of two layers can be involved. UL CoMP UEs in SFN cells cannot be
involved in UE pairing.
l If this option is deselected, UL CoMP UEs cannot be involved in UE pairing and uplink
MU-MIMO takes precedence over type-1 CoMP.
5.7.2.1 Benefits
Uplink 4x8 MU-MIMO provides a higher average uplink throughput than uplink receive
diversity. Uplink 4x8 MU-MIMO can offer significant gains when the following conditions
are met:
l The PUSCH load is high. That is, the uplink PRB usage exceeds 90%.
l There are adequate PDCCH resources for UE pairing. That is, the CCE usage is less than
80%.
5.7.2.2 Impacts
Network Impacts
MU-MIMO has the following network impacts:
l Uplink coverage may deteriorate and CEU throughput may decrease in high interference
scenarios because more UEs are scheduled in uplink MU-MIMO.
l The CCE usage and CCE allocation failure rate may increase in high load scenarios
because more UEs are scheduled in uplink MU-MIMO.
l The E-RAB setup delay may decrease in high load scenarios because UEs have more
chances to be scheduled in uplink MU-MIMO.
l The number of uplink preallocation times may increase and the number of RBs used in
uplink preallocation may also increase. This is because UEs have more chances to be
scheduled and their uplink data transmission can be completed in a shorter time when
both uplink preallocation and uplink MU-MIMO are enabled.
l The number of uplink error bits in uplink MU-MIMO may increase when the number of
pairing times is low. This is because the MCS selection mechanism for paired UEs is
independent of that for unpaired UEs.
Function Impacts
Function Function Switch Reference Description
Name
5.7.3 Requirements
5.7.3.1 Licenses
Feature ID Feature Name Model Sales Unit
In addition to feature licenses, capacity licenses are required for MIMO. Each BBP is licensed
by default to provide two baseband TX channels and two baseband RX channels for each cell.
NOTE
Uplink 4x8 MU-MIMO can be used without a license in 60 days after an upgrade to eRAN TDD 13.0. It
needs to be licensed for use after this period.
5.7.3.2 Software
Prerequisite Functions
Function Name Function Switch Reference
5.7.3.3 Hardware
Boards
This function requires 8R BBPs.
RF Modules
No requirements
5.7.3.4 Others
None
VMIMOReduceMCSRi-
seRBSwitch
VoLTEUeVmimoSwitch
Activation Verification
Step 1 Start an MU-MIMO monitoring task on the U2000 client to monitor the number of UE pairs
in uplink MU-MIMO.
Item for Unit Value Range Description
Monitoring
Mimo UE Pair Num Pair 0 to 32000 This item indicates the total number of
UE pairs in all TTIs of a monitoring
period. This number increases by one
when two UEs are paired for MU-
MIMO in a TTI.
Mimo UE Pair Num Not N/A Uplink MU-MIMO has been enabled.
----End
Network Monitoring
Use the counters listed in Table 5-22 to monitor uplink MU-MIMO. If any counter has a non-
zero value, uplink MU-MIMO is functioning properly. If the counter values are always zero,
uplink MU-MIMO is not functioning properly.
1526728349 L.ChMeas.VMIMO.PairPRB.Succ
1526728350 L.ChMeas.VMIMO.PairPRB.Tot
1526739789 L.ChMeas.VMIMO.PairPRB.Succ.VoLTE
1526739782 L.ChMeas.VMIMO.PairPRB2Layer.Succ
1526739783 L.ChMeas.VMIMO.PairPRB3Layer.Succ
1526739784 L.ChMeas.VMIMO.PairPRB4Layer.Succ
1526740469 L.ChMeas.VMIMO.Succ.SubFrameNum
5.8 UL SU-MIMO
5.8.1 Principles
Uplink SU-MIMO allows 2T UEs to work in transmission mode 2 (TM2).
l When this option is deselected, all UEs in the cell can work only in TM1.
l When this option is selected, 2T UEs in the cell can work in TM2.
TM1 1 1 1
TM2 1 1 1
2 2 2
l When this parameter is set to FixRank1, all UEs use rank 1 transmission.
l When this parameter is set to FixRank2, all UEs use rank 2 transmission.
l When this parameter is set to RankAdaptive, UE 1 in poor channel conditions uses rank
1 transmission and UE 2 in good channel conditions uses rank 2 transmission, as shown
in Figure 5-18.
5.8.2.1 Benefits
Uplink SU-MIMO provides the following benefits when there are 2T UEs in a cell:
l Nearly doubles the uplink peak throughput.
l Increases the User Uplink Average Throughput of non-cell-edge UEs by 5% to 20%.
l Increases the Cell Uplink Average Throughput.
SU-MIMO offers higher gains in the following conditions:
l The eNodeB has more RX antennas.
l The average uplink SINR is higher.
l A larger proportion of UEs support SU-MIMO.
5.8.2.2 Impacts
Network Impacts
None
Function Impacts
RAT Function Function Reference Description
Name Switch
FDD Uplink 2x4 UlVmimoSwitc 5.5 UL 2x4 UEs selected for uplink
TDD MU-MIMO h option of the MU-MIMO SU-MIMO are not
CellAlgoSwitch. selected for MU-MIMO.
UlSchSwitch
parameter
5.8.3 Requirements
5.8.3.1 Licenses
RAT Feature Feature Name Model Sales Unit
ID
In addition to feature licenses, capacity licenses are required for MIMO. Each BBP is licensed
by default to provide two baseband TX channels and two baseband RX channels for each cell.
Each RF module is licensed by default to provide two RF TX channels and two RF RX
channels. For details, see License Control Item Lists (FDD) or License Control Item Lists
(TDD).
5.8.3.2 Software
Prerequisite Functions
RAT Function Name Function Switch Reference
5.8.3.3 Hardware
For TDD, 3900 and 5900 series base stations are compatible with this function.
Boards
This function requires the UBBPd or UBBPe.
RF Modules
No requirements
Cells
This function requires that cells have a bandwidth of 10 MHz or higher and have two or more
RX channels.
5.8.3.4 Others
UEs must have two transmit channels.
Activation Verification
l Uu DCI status monitoring
Uplink SU-MIMO is active if PDCCH downlink control information (DCI) format 4 is
used in TM2 at least once. The number of times this format can be obtained via Uu DCI
status monitoring.
l Counter observation
Uplink SU-MIMO is active if any of the counters listed in Table 5-27 has a value greater
than 0.
1526746681 L.Traffic.User.ULSUMIMO.Avg
1526743750 L.ChMeas.ULMIMO.PRB.CL.Rank1
1526743751 L.ChMeas.ULMIMO.PRB.CL.Rank2
Benefit Monitoring
Uplink SU-MIMO increases the User Uplink Average Throughput and Cell Uplink
Average Throughput. Table 5-28 lists the related counters.
A higher proportion of RBs used for rank 2 transmission indicates a higher increase in
throughput.
Table 5-28 Counters for calculating the average uplink cell throughput
Counter ID Counter Name
1526728259 L.Thrp.bits.UL
1526728998 L.Thrp.Time.Cell.UL.HighPrecision
1526729049 L.Thrp.bits.UE.UL.LastTTI
1526729050 L.Thrp.Time.UE.UL.RmvLastTTI
CCE Monitoring
When uplink SU-MIMO is active, DCI format 4 is used in scheduling. When uplink SU-
MIMO is inactive, DCI format 0 is used in scheduling. Compared with DCI format 0, DCI
format 4 results in a higher payload. It may also result in higher CCE usage and greater values
of the counters listed in Table 5-29. The increase depends on UE quantity and cell load.
1526728304 L.ChMeas.CCE.ULUsed
1526729295 L.ChMeas.CCE.ULUsed.Equivalent
526730844 L.ChMeas.CCE.UL.AllocFail
The increase in CCE usage may result in changes in the values of the counters listed in Table
5-30.
1526728774 L.RRC.ConnSetup.TimeAvg
1526728775 L.RRC.ConnSetup.TimeMax
1526728776 L.E-RAB.Est.TimeAvg
1526728777 L.E-RAB.Est.TimeMax
l If the pre-test PRB usage is less than 50%, you are advised to enable power control by
the uplink scheduler to maintain the benefits provided by uplink SU-MIMO during the
full buffer service test. This power control function is controlled by the
SchedulerCtrlPowerSwitch option of the CellAlgoSwitch.UlSchSwitch parameter.
l If the pre-test PRB usage is not less than 50% or the full buffer service test is not
performed, you are advised to disable power control by the uplink scheduler. If this
function is enabled, the values of counters listed in Table 5-31 may increase.
NOTE
PRB usage = L.ChMeas.PRB.UL.Used.Avg / Total number of uplink PRBs of the system bandwidth
1526728297 L.UL.Interference.Max
1526728298 L.UL.Interference.Avg
1526743751 L.UL.Interference.Min
1526743709 L.UL.Interference.LinearAvg
6 Parameters
Cell CrsPort ADD LOFD-0 DL 2x2 Meaning: Indicates the number of ports for
Num CELL 01001/ MIMO transmitting cell-specific reference signal (CRS). As
MOD TDLOF DL 4x2 defined in 3GPP specifications, this parameter can be
CELL D-00100 MIMO set to CRS_PORT_1, CRS_PORT_2, or
1 CRS_PORT_4. The value CRS_PORT_1 indicates
LST DL 4x4 that one CRS port (port 0) is configured. The value
CELL LOFD-0 MIMO
01003 CRS_PORT_2 indicates that two CRS ports (ports 0
DL 4x4 and 1) are configured. The value CRS_PORT_4
LOFD-0 MIMO indicates that four CRS ports (ports 0, 1, 2, and 3) are
01060 configured.
DL
TDLOF Flexible GUI Value Range: CRS_PORT_1(1 port),
D-00106 3D- CRS_PORT_2(2 ports), CRS_PORT_4(4 ports)
0 Beamfor Unit: None
TDLEO ming
FD-121 Actual Value Range: CRS_PORT_1, CRS_PORT_2,
615 CRS_PORT_4
Default Value: CRS_PORT_2(2 ports)
CellAlg EnhMI MOD LOFD-0 DL 2x2 Meaning: Indicates the switch used to enable or
oSwitch MOSwit CELLA 01001 MIMO disable enhanced MIMO. Admitted UEs are allowed
ch LGOSW LOFD-0 DL 4x2 to enter TM9 or TM10 mode only if the TM9Switch
ITCH 01003 MIMO or TM10Switch option is selected. The
LST TM4TM9AdaptiveSwitch option can be selected only
LOFD-0 DL 4x4 after the TM9Switch option is selected. If the
CELLA 01060 MIMO
LGOSW TM4TM9AdaptiveSwitch option is selected, UEs
ITCH TDLAO DL 2- meeting certain conditions are allowed to adaptively
FD-001 Layer enter TM4 and TM9 mode. Otherwise, UEs are
00114 MIMO prohibited from adaptively entering TM4 and TM9
TDLAO Based mode. Enhanced MIMO does not apply to the LBBPc.
FD-081 on TM9 The TM4TM9AdaptiveSwitch and TM10Switch
409 DL 4- options apply only to LTE FDD. This parameter
Layer applies only to LTE FDD. ChannelRecSwitch:
LAOFD Indicates whether to enable channel reconstruction
-111204 MIMO
Based optimization. Channel reconstruction optimization is
LEOFD- on TM9 enabled only if this option is selected. This option
111307 applies only to LTE FDD. TM9HybridPrecodingS-
Adaptiv witch: Indicates whether to enable the TM9 hybrid
e SFN/ precoding algorithm in massive MIMO scenarios. If
SDMA this option is selected, the TM9 hybrid precoding
with function is enabled to improve the beamforming
TM10 capability of closed-loop TM9 UEs. If this option is
eMIMO deselected, the TM9 hybrid precoding function is
disabled, and the beamforming capability of closed-
loop TM9 UEs remains unchanged. This option
applies only to LTE TDD.
GUI Value Range: TM9Switch(TM9Switch),
TM4TM9AdaptiveSwitch(TM4TM9AdaptiveSwitch),
TM10Switch(TM10Switch),
ChannelRecSwitch(ChannelRecSwitch),
TM9HybridPrecodingSwitch(TM9HybridPrecodingS-
witch)
Unit: None
Actual Value Range: TM9Switch,
TM4TM9AdaptiveSwitch, TM10Switch,
ChannelRecSwitch, TM9HybridPrecodingSwitch
Default Value: TM9Switch:Off,
TM4TM9AdaptiveSwitch:Off, TM10Switch:Off,
ChannelRecSwitch:Off, TM9HybridPrecodingS-
witch:Off
EpfEnhancedSwitch(EpfEnhancedSwitch),
AperiodicCqiTrigOptSwitch(AperiodicCqiTrigOptS-
witch), VoipTbsBasedMcsSelS-
witch(VoipTbsBasedMcsSelSwitch),
PagingInterfRandSwitch(PagingInterfRandSwitch),
DlSingleUsrMcsOptSwitch(DlSingleUsrMcsOptS-
witch), SubframeSchDiffSwitch(SubframeSchDiffS-
witch), TailPackagePriSchS-
witch(TailPackagePriSchSwitch),
UeSigMcsEnhanceSwitch(UeSigMcsEnhanceSwitch),
FreqSelJudgeIgnorDopplerSwitch(FreqSelJudgeIgnor-
DopplerSwitch),
SIB1InterfRandSwitch(SIB1InterfRandSwitch),
EnhExtQCISpsSchSwitch(EnhExtQCISpsSchSwitch),
DlVoipBundlingSwitch(DlVoipBundlingSwitch),
DlPacketLenAwareSchSw(DlPacketLenAwar-
eSchSw), RLCArqFeedbackEnhanced-
Switch(RLCArqFeedbackEnhancedSwitch),
PaReconfigOptSwitch(PaReconfigOptSwitch),
RankRapidRptSwitch(RankRapidRptSwitch),
DlRLCStateReportSchDe-
laySw(DlRLCStateReportSchDelaySw),
SmallPktMcsSelectAlgoSw(SmallPktMcsSelectAl-
goSw), SRB0SplitSchSw(SRB0SplitSchSw),
BfUserPairPriorSwitch(BfUserPairPriorSwitch),
HarqAllocOptSwitch(HarqAllocOptSwitch),
Pusch32Switch(Pusch32Switch),
DlPreciseAmbrCtrlSwitch(DlPreciseAmbrCtrlSwitch)
Unit: None
Actual Value Range: FreqSelSwitch, SpsSchSwitch,
MBSFNShutDownSwitch, NonGbrBundlingSwitch,
EnAperiodicCqiRptSwitch, DlMbrCtrlSwitch,
MbrDlSchSwitch, UeAmbrDlSchSwitch,
EpfEnhancedSwitch, AperiodicCqiTrigOptSwitch,
VoipTbsBasedMcsSelSwitch, PagingInterfRand-
Switch, DlSingleUsrMcsOptSwitch,
SubframeSchDiffSwitch, TailPackagePriSchSwitch,
UeSigMcsEnhanceSwitch, FreqSelJudgeIgnorDop-
plerSwitch, SIB1InterfRandSwitch,
EnhExtQCISpsSchSwitch, DlVoipBundlingSwitch,
DlPacketLenAwareSchSw, RLCArqFeedbackEnhan-
cedSwitch, PaReconfigOptSwitch,
RankRapidRptSwitch, DlRLCStateReportSchDe-
laySw, SmallPktMcsSelectAlgoSw, SRB0SplitSchSw,
BfUserPairPriorSwitch, HarqAllocOptSwitch,
Pusch32Switch, DlPreciseAmbrCtrlSwitch
Default Value: FreqSelSwitch:Off, SpsSchSwitch:Off,
MBSFNShutDownSwitch:Off, NonGbrBundlingS-
OTDOAInterFreqRSTDMeasSwitch:Off,
EmtcEcidSwitch:Off, EcidOptSwitch:Off
Cell CrsPort ADD LOFD-0 DL 2x2 Meaning: Indicates the mapping between a cell-
Map CELL 01001/ MIMO specific reference signal (CRS) port and a transmit
MOD TDLOF DL 4x2 (TX) channel in an RRU. In cells with one or two TX
CELL D-00100 MIMO channels, this parameter cannot be set. In cells with
1 four or eight TX channels, this parameter can be set.
LST DL 4x4 As defined in 3GPP specifications, the CrsPortNum
CELL LOFD-0 MIMO
01003 parameter can be set to CRS_PORT_1,
DL 4x4 CRS_PORT_2, or CRS_PORT_4. The value
LOFD-0 MIMO CRS_PORT_1 indicates that one CRS port (port 0) is
01060 configured. The value CRS_PORT_2 indicates that
DL 4-
TDLOF Antenna two CRS ports (ports 0 and 1) are configured. The
D-00106 Transmi value CRS_PORT_4 indicates that four CRS ports
0 t (ports 0, 1, 2 and 3). In values of this parameter,
MLBFD Diversit mTnP indicates that the number of TX channels
-121002 y configured for a cell is "m" and the number of CRS
40 ports is "n". The parameter value 4TnP_abcd indicates
that reference signals transmitted over CRS ports a, b,
c, and d are mapped to TX channels 1, 2, 3, and 4 in
an RRU, respectively (The TX channel number here is
for reference only, and is determined based on the
R0A to R0D, or others). The parameter value
8TnP_abcdefgh indicates that reference signals
transmitted over CRS ports a to h are mapped to TX
channels 1 to 8 in an RRU, respectively. Duplicate
numbers of abcd or abcdefgh indicate that virtual
antenna mapping (VAM) is applied, that is, the
reference signals transmitted over the CRS port are
mapped to corresponding TX channels. The parameter
value NOT_CFG indicates that the mapping between
a CRS port and a TX channel in an RRU is not
configured, and CRS ports are mapped to TX channels
in an RRU in a default manner. In TDD cells, "n" in
mTnP must be equal to the CrsPortNum parameter
value. For cells established on LBBPc boards, the
parameter value NOT_CFG takes effect regardless of
the actual parameter setting. This parameter applies
only to LTE FDD and LTE TDD.
GUI Value Range: NOT_CFG(Not configure),
4T4P_0213(4T4P_0213), 4T4P_0231(4T4P_0231),
4T4P_0123(4T4P_0123), 4T4P_0132(4T4P_0132),
4T4P_0312(4T4P_0312), 4T4P_0321(4T4P_0321),
4T2P_0011(4T2P_0011), 4T2P_0101(4T2P_0101),
4T2P_0110(4T2P_0110),
8T2P_00001111(8T2P_00001111),
8T2P_00110011(8T2P_00110011),
8T2P_01010101(8T2P_01010101),
8T4P_00112233(8T4P_00112233),
8T4P_01230123(8T4P_01230123)
Unit: None
Actual Value Range: NOT_CFG, 4T4P_0213,
4T4P_0231, 4T4P_0123, 4T4P_0132, 4T4P_0312,
4T4P_0321, 4T2P_0011, 4T2P_0101, 4T2P_0110,
8T2P_00001111, 8T2P_00110011, 8T2P_01010101,
8T4P_00112233, 8T4P_01230123
Default Value: NOT_CFG(Not configure)
EmimoFbaSwitch:Off, New4TCodebookSwitch:Off,
4TxTM9MuMimoSwitch:Off, DrxSimulAckNack-
AndCqiSwitch:Off, PreciseAmcSwitch:Off,
EmimoCsiEnhanceSwitch:Off, PUSCH12Switch:Off
Cell DlCycli ADD LBFD-0 Normal Meaning: Indicates the length of the DL cyclic prefix
cPrefix CELL 0100401 CP of a cell. A DL cyclic prefix can be a common or
MOD / Extende extended cyclic prefix. An extended cyclic prefix is
CELL TDLBF d CP generally used in a complex environment with a
D-00100 strong multi-path effect and long delay. In a cell, the
LST 401 eMTC UL cyclic prefix length can be different from the DL
CELL Introduc one. In addition, the UL or DL cyclic prefix length of
LOFD-0 tion
01031/ a cell must be the same as that of the cell using the
TDLOF same BBP. For details, see 3GPP TS 36.211.
D-00103 GUI Value Range: NORMAL_CP(Normal),
1 EXTENDED_CP(Extended)
TDLEO Unit: None
FD-121 Actual Value Range: NORMAL_CP,
611 EXTENDED_CP
Default Value: NORMAL_CP(Normal)
Cell UlCycli ADD LBFD-0 Normal Meaning: Indicates the UL cyclic prefix length of a
cPrefix CELL 0100401 CP cell. A cyclic prefix can be a common or extended
MOD / Extende cyclic prefix. An extended cyclic prefix is generally
CELL TDLBF d CP used in a complex environment with a strong multi-
D-00100 path effect and long delay. In a cell, the UL cyclic
LST 401 Broadca prefix length can be different from the DL one. In
CELL st of addition, the UL or DL cyclic prefix length of a cell
LOFD-0 system
01031/ must be the same as that of the cell using the same
informat BBP. For details, see 3GPP TS 36.211.
TDLOF ion
D-00103 GUI Value Range: NORMAL_CP(Normal),
1 EXTENDED_CP(Extended)
LBFD-0 Unit: None
02009/ Actual Value Range: NORMAL_CP,
TDLBF EXTENDED_CP
D-00200
9/ Default Value: NORMAL_CP(Normal)
MLBFD
-120002
29
Cell MultiRr ADD LOFD-0 SFN Meaning: Indicates whether to enable or disable the
uCellFla CELL 03029/ Adaptiv multi-RRU cell feature.
g MOD TDLOF e SFN/ GUI Value Range: BOOLEAN_FALSE(False),
CELL D-00107 SDMA BOOLEAN_TRUE(True)
5
LST Inter- Unit: None
CELL TDLOF BBP
D-00200 Actual Value Range: BOOLEAN_FALSE,
SFN BOOLEAN_TRUE
8
Inter- Default Value: BOOLEAN_FALSE(False)
TDLOF eNodeB
D-00109 SFN
8 Based
TDLOF on
D-00108 Coordin
0 ated
TDLOF eNodeB
D-00108 Inter-
1 BBP
TDLOF Adaptiv
D-00108 e SFN/
2 SDMA
Inter-
eNodeB
Adaptiv
e SFN/
SDMA
Based
on
Coordin
ated
eNodeB
GlobalP CrsAntP DSP None None Meaning: Indicates the CRS antenna port mapping
rocSwitc ortOptD CRSPO optimization detection result of the cell. This
h etResult RTOPT parameter applies only to LTE FDD.
DET GUI Value Range: NA(NA), RUNNING(RUNNING),
FAILURE(FAILURE), COMPLETE(COMPLETE),
SCENARIO_NOT_SUPPORTED(SCENARIO_NOT
_SUPPORTED),
FAILURE_HIGHER_PRIORITY_TASK_DISRUPTI
ON(FAILURE_HIGHER_PRIORITY_TASK_DISRU
PTION),
FAILURE_TIMEOUT(FAILURE_TIMEOUT)
Unit: None
Actual Value Range: NA, RUNNING, FAILURE,
COMPLETE, SCENARIO_NOT_SUPPORTED,
FAILURE_HIGHER_PRIORITY_TASK_DISRUPTI
ON, FAILURE_TIMEOUT
Default Value: None
CellDlsc MaxMi MOD LOFD-0 DL 2x2 Meaning: Indicates the maximum number of layers
hAlgo moRank CELLD 01001/ MIMO (the rank) in the implementation of multiple-input
Para LSCHA TDLOF DL 4x2 multiple-output (MIMO) in DL scheduling. This
LGO D-00100 MIMO parameter applies only to LTE FDD and LTE TDD.
LST 1 GUI Value Range: SW_MAX_SM_RANK_1(Rank1),
DL 4x4
CELLD LOFD-0 MIMO SW_MAX_SM_RANK_2(Rank2),
LSCHA 01003 SW_MAX_SM_RANK_4(Rank4),
LGO DL 4x4 SW_MAX_SM_RANK_8(Rank8)
LOFD-0 MIMO
01060 Unit: None
DL 8x8
TDLOF MIMO Actual Value Range: SW_MAX_SM_RANK_1,
D-00106 (Trial) SW_MAX_SM_RANK_2,
0 SW_MAX_SM_RANK_4, SW_MAX_SM_RANK_8
TDLAO Default Value: SW_MAX_SM_RANK_2(Rank2)
FD-130
490
Cell TxRxM ADD None None Meaning: Indicates the transmission and reception
ode CELL mode of the cell.
MOD GUI Value Range: 1T1R, 1T2R, 2T2R, 2T4R, 4T4R,
CELL 8T8R, 2T8R, 4T8R, 64T64R, 32T32R
LST Unit: None
CELL Actual Value Range: 1T1R, 1T2R, 2T2R, 2T4R,
4T4R, 8T8R, 2T8R, 4T8R, 64T64R, 32T32R
Default Value: None
D-00100 DL 4x4 services and other services when both of the following
1 MIMO conditions are met: (1) The EPC delivers information
LOFD-0 DL 2x2 about bearers with QCI 1 and other QCIs; (2) The UE
01003 MIMO exits the idle mode. After the QCI-1 service bearers
are set up, the UE is handed over to an inter-frequency
TDLAO DL 4x2 cell. This option applies only to LTE FDD and LTE
FD-001 MIMO TDD.
00114 DL 2-
TDLAO Layer ApCqiAndAckAbnCtrlSwitch: Indicates whether to
FD-081 MIMO enable a workaround of problems that may occur
409 Based when aperiodic CQI reports in 3-1 reporting mode and
on TM9 ACKs/NACKs are transmitted simultaneously in a
LAOFD cell. If this option is selected, the eNodeB performs
-001001 DL 4- preallocation for aperiodic CQI reports. If this option
/ Layer is deselected, the eNodeB performs CQI_ONLY
TDLAO MIMO scheduling on aperiodic CQI reports. This option
FD-001 Based applies only to LTE FDD and LTE TDD.
001 on TM9
TDLAO LTE-A UeSRSAntSelectCtrlSwitch: Indicates whether to
FD-110 Introduc disable antenna selection for SRS transmission. If this
401 tion option is selected, antenna selection is disabled. This
option applies only to LTE TDD.
TDLAO Inter-
FD-081 eNodeB CaCqiAndAckAbnCtrlSwitch: Indicates whether to
402 CA enable a workaround of problems that may occur
LBFD-0 based on when periodic CQI reports and ACKs/NACKs are
60101 Coordin transmitted simultaneously in a cell in CA scenarios.
ated If this option is selected, the eNodeB sets the
MRFD- eNodeB SimulAckNackAndCqiSwitch parameter to OFF(Off)
101222 for CA UEs. If this option is deselected, the eNodeB
Inter-
MRFD- sets the SimulAckNackAndCqiSwitch parameter
eNodeB
111222 based on the original algorithm for CA UEs.
CA
Based HoRlcSnSizeSwitch: Controls the configuration of
on RLC sn-FieldLength during handovers. If this option
Relaxed is selected, the configuration of RLC sn-FieldLength
Backhau for the target cell is the same as that for the source
l cell. If this option is deselected, RLC sn-FieldLength
for the target cell is set to the value configured at the
Optimiz target side.
ation of
CQI FddTddCaPcellDuplexFdd: Indicates whether the
Reportin eNodeB regards that a UE supports FDD+TDD CA
g with an LTE FDD cell serving as its PCell when the
FDD UE reports the FDD+TDD CA band combination but
+TDD does not report IE tdd-FDD-CA-PCellDuplex-r12. If
Downlin this option is selected, the eNodeB regards that the UE
k supports this type of CA. If this option is deselected,
Carrier the eNodeB regards that the UE does not support this
Aggrega type of CA. This option applies only to LTE FDD and
tion LTE TDD.
Unit: None
Actual Value Range: SpsSchSwitch,
SinrAdjustSwitch, PreAllocationSwitch,
UlVmimoSwitch, TtiBundlingSwitch,
SmartPreAllocationSwitch, PuschDtxSwitch,
UlIblerAdjustSwitch, UlEnhancedFssSwitch,
UlEnhancedSrSchSwitch, SchedulerCtrlPowerSwitch,
UlIicsAlgoSwitch, UlMinGbrSwitch,
UlMbrCtrlSwitch, MbrUlSchSwitch,
UeAmbrUlSchSwitch, UlEnhancedDopplerSwitch,
UlRaUserSchOptSw, UlLast2RetransSchOptSwitch,
UlInterfFssSwitch, UlSmallRBSpectralEffOptSw,
PuschUsePucchRbSwitch, PuschDtxSchOptSwitch,
ULFSSAlgoSwitch, PrachRbReuseSwitch,
SrSchDataAdptSw, UlFssUserThdStSwitch,
HighOrderVMIMOSwitch, VMIMOReduceMCSRi-
seRBSwitch, VoLTEUeVmimoSwitch,
TtiBundlingForVideoSwitch
Default Value: SpsSchSwitch:Off,
SinrAdjustSwitch:On, PreAllocationSwitch:On,
UlVmimoSwitch:Off, TtiBundlingSwitch:Off,
SmartPreAllocationSwitch:On, PuschDtxSwitch:On,
UlIblerAdjustSwitch:Off, UlEnhancedFssSwitch:On,
UlEnhancedSrSchSwitch:On, SchedulerCtrlPowerS-
witch:Off, UlIicsAlgoSwitch:Off,
UlMinGbrSwitch:Off, UlMbrCtrlSwitch:Off,
MbrUlSchSwitch:Off, UeAmbrUlSchSwitch:Off,
UlEnhancedDopplerSwitch:On,
UlRaUserSchOptSw:Off,
UlLast2RetransSchOptSwitch:On,
UlInterfFssSwitch:Off, UlSmallRBSpectralEf-
fOptSw:Off, PuschUsePucchRbSwitch:Off,
PuschDtxSchOptSwitch:Off, ULFSSAlgoSwitch:On,
PrachRbReuseSwitch:Off, SrSchDataAdptSw:On,
UlFssUserThdStSwitch:Off, HighOrderVMIMOS-
witch:Off, VMIMOReduceMCSRiseRBSwitch:Off,
VoLTEUeVmimoSwitch:Off, TtiBundlingForVideoS-
witch:Off
UlHetnetJointReceptionSwitch,
UlHetnetCompManualNcellCfgSw,
UlHetnetCompOnUlRsrpSw, SimplePairedCompSw,
VoipPrioSw, UlCompInterBoardType2Sw,
UlCompForVideoSwitch, WideRangeCompSwitch,
EnhancedUlCompSwitch
Default Value: UlJointReceptionSwitch:Off,
UlJointReceptionPhaseIISwitch:Off,
UlCompRollbackSwitch:On,
UlJointReception3CellSwitch:Off, UlHetnetJointRe-
ceptionSwitch:Off, UlHetnetCompManualN-
cellCfgSw:Off, UlHetnetCompOnUlRsrpSw:Off,
SimplePairedCompSw:Off, VoipPrioSw:Off,
UlCompInterBoardType2Sw:Off, UlCompForVideoS-
witch:Off, WideRangeCompSwitch:Off,
EnhancedUlCompSwitch:Off
CellAlg PsicSwit MOD LOFD-0 Advance Meaning: Indicates whether to enable parallel soft
oSwitch ch CELLA 01096 d interference cancellation (PSIC). In the case of LTE
LGOSW Receiver FDD, PSIC can be used in cells established on UBBP
ITCH (PSIC) or LBBPd boards in uplink 2x2 MU-MIMO scenarios.
LST In the case of LTE TDD, PSIC can be used in cells
CELLA established on UBBP boards in uplink 2x4 MU-
LGOSW MIMO scenarios. This parameter applies only to LTE
ITCH FDD and LTE TDD.
GUI Value Range: MumimoPuschPsicS-
witch(MumimoPuschPsicSwitch)
Unit: None
Actual Value Range: MumimoPuschPsicSwitch
Default Value: MumimoPuschPsicSwitch:Off
Cell HighSpe ADD LOFD-0 High Meaning: Indicates the speed flag of the cell. Set this
edFlag CELL 01007/ Speed parameter to HIGH_SPEED if the cell is used to
MOD TDLOF Mobility provide coverage for a high-speed railway. Set this
CELL D-00100 Ultra parameter to LOW_SPEED in other scenarios. TDD
7 High cells with a bandwidth of 5 MHz or in 8T8R mode can
LST only be configured as low-speed cells. TDD cells
CELL LOFD-0 Speed
01008 Mobility cannot be configured as ultra-high-speed cells. This
parameter applies only to LTE FDD and LTE TDD.
GUI Value Range: LOW_SPEED(Low speed cell
flag), HIGH_SPEED(High speed cell flag),
ULTRA_HIGH_SPEED(Ultra high speed cell flag),
EXTRA_HIGH_SPEED(Extra high speed cell flag)
Unit: None
Actual Value Range: LOW_SPEED, HIGH_SPEED,
ULTRA_HIGH_SPEED, EXTRA_HIGH_SPEED
Default Value: LOW_SPEED(Low speed cell flag)
CellAlg UlIcSwi MOD TDLOF Uplink Meaning: Indicates whether to enable the uplink
oSwitch tch CELLA D-11120 Interfere interference coordination algorithm. If the
LGOSW 8 nce UL_ICS_SWITCH(UlIcSwitch) option is deselected,
ITCH Coordin the uplink interference coordination algorithm does
LST ation not take effect. If the UL_ICS_SWITCH(UlIcSwitch)
CELLA option is selected, the uplink interference coordination
LGOSW algorithm is enabled. This parameter applies only to
ITCH LTE TDD.
GUI Value Range: UL_ICS_SWITCH(UlIcSwitch)
Unit: None
Actual Value Range: UL_ICS_SWITCH
Default Value: UL_ICS_SWITCH:Off
CellUlsc Enhance MOD LOFD-0 UL 2x4 Meaning: Indicates whether to enhance uplink MU
hAlgo dVmimo CELLU 01058/ MU- MIMO for non-massive MIMO cells or whether to
Switch LSCHA TDLOF MIMO optimize pairing for uplink MU MIMO to pair more
LGO D-00105 UL 2x8 layers of UEs in massive MIMO cells. This parameter
LST 8 MU- applies only to LTE TDD.
CELLU TDLOF MIMO GUI Value Range: OFF(OFF), ON(ON)
LSCHA D-08120 UL Unit: None
LGO 5 2x64 Actual Value Range: OFF, ON
TDLEO MU-
FD-121 MIMO Default Value: OFF(OFF)
60302 UL 4-
TDLEO Layer
FD-121 MU-
609 MIMO
TDLEO UL 8-
FD-121 Layer
610 MU-
MIMO
CellUlsc VMIMO MOD TDLOF UL 2x4 Meaning: Indicates the ratio of RBs preferentially
hAlgo EgdeRes CELLU D-00105 MU- allocated to CEUs after VMIMO interference
Ratio LSCHA 8 MIMO coordination is enabled. This parameter applies only
LGO TDLOF UL 2x8 to LTE TDD.
LST D-08120 MU- GUI Value Range: 0~50
CELLU 5 MIMO Unit: %
LSCHA TDLEO UL
LGO Actual Value Range: 0~50
FD-121 2x64
60302 MU- Default Value: 30
TDLEO MIMO
FD-121 UL 4-
609 Layer
TDLEO MU-
FD-121 MIMO
610 UL 8-
Layer
MU-
MIMO
ENodeB UlIcicFr MOD TDLBF Uplink Meaning: Indicates whether to enable uplink ICIC in
AlgoSwi eqSwitc ENODE D-00202 Static the frequency domain. If this parameter is set to
tch h BALGO 202 Inter- OFF(Off), uplink ICIC in the frequency domain is
SWITC Cell disabled for cells served by the eNodeB. If this
H Interfere parameter is set to STATIC(Static), uplink static CIC
LST nce in the frequency domain is enabled for cells served by
ENODE Coordin the eNodeB. If this parameter is set to
BALGO ation DYNAMIC(Dynamic), uplink dynamic ICIC in the
SWITC frequency domain is enabled for cells served by the
H eNodeB. If uplink adaptive ICIC is enabled, neither
static nor dynamic ICIC is enabled. This parameter
applies only to LTE TDD.
GUI Value Range: OFF(Off), STATIC(Static),
DYNAMIC(Dynamic)
Unit: None
Actual Value Range: OFF, STATIC, DYNAMIC
Default Value: OFF(Off)
CellUlsc MaxLay MOD TDLOF UL 4x8 Meaning: Indicates the maximum number of layers of
hAlgo erHOV CELLU D-13020 MU- UEs that can be paired for high-order VMIMO. This
MIMO LSCHA 3 MIMO parameter applies only to LTE TDD cells.
LGO GUI Value Range: 2LAYER(2LAYER),
LST 3LAYER(3LAYER), 4LAYER(4LAYER)
CELLU Unit: None
LSCHA
LGO Actual Value Range: 2LAYER, 3LAYER, 4LAYER
Default Value: 4LAYER(4LAYER)
CellUlM UlSuMi MOD LOFD-1 UL SU- Meaning: Indicates the rank selection method when
imoPara moRank CELLU 30201/ MIMO the uplink transmission mode is TM2. If this
Cfg Para LMIMO TDLOF parameter is set to FixRank1(FixRank1), only rank 1
PARAC D-12020 transmission can be performed for all UEs in the
FG 1 network. If this parameter is set to
LST FixRank2(FixRank2), only rank 2 transmission can be
CELLU performed for all UEs in the network. If this
LMIMO parameter is set to RankAdaptive(RankAdaptive), the
PARAC eNodeB adaptively selects a rank based on the UE
FG channel quality. This parameter applies only to LTE
FDD and LTE TDD.
GUI Value Range: RankAdaptive(RankAdaptive),
FixRank1(FixRank1), FixRank2(FixRank2)
Unit: None
Actual Value Range: RankAdaptive, FixRank1,
FixRank2
Default Value: RankAdaptive(RankAdaptive)
SRSCfg SrsCfgP MOD TDLOF Single Meaning: Indicates the SRS configuration policy. This
olicySwi SRSCF D-00104 Streami parameter applies only to LTE TDD.
tch G 9 ng SRSPolicyforUL2LayersMIMO: Indicates the two-
LST TDLOF Beamfor antenna-port SRS configuration policy if two antenna
SRSCF D-00106 ming ports are configured for a UE in the uplink. If this
G 1 Dual option is deselected, the eNodeB preferentially
Streami allocates short-term SRSs (including single-antenna-
TDLOF port SRSs). If this option is selected, the eNodeB
D-12020 ng
Beamfor preferentially allocates two-antenna-port SRSs
1 (including long-term SRSs). SrvBasedSRSAdjAlgo:
ming
TDLEO Indicates whether to enable service-based SRS
FD-121 UL SU- adjustment. If this option is selected, the eNodeB can
601 MIMO adjust SRSs for UEs based on the identified UE
Massive services for SRS adjustment. If this option is
MIMO deselected, the eNodeB does not identify UE services
Introduc for SRS adjustment. This option applies only to LTE
tion TDD.
GUI Value Range:
SRSPolicyforUL2LayersMIMO(SRSPolicyforUL2La
yersMIMO), SrvBasedSRSAdjAl-
go(SrvBasedSRSAdjAlgo)
Unit: None
Actual Value Range: SRSPolicyforUL2LayersMIMO,
SrvBasedSRSAdjAlgo
Default Value: SRSPolicyforUL2LayersMIMO:Off,
SrvBasedSRSAdjAlgo:Off
UlSchRbAllocOptSw(UlSchRbAllocOptSw),
UlMultiClusterSwitch(UlMultiClusterSwitch),
SrPairingSwitch(SrPairingSwitch),
UlDrbProactiveSchSwitch(UlDrbProactiveSchSwitch)
Unit: None
Actual Value Range: UlPacketLenAwareSchSw,
EnhExtQCITtiBundlingSwitch, EnhExtQCISpsSchS-
witch, UlVoipRbRsvSwitch, UlThpEnhSwitch,
UlDataFitterRbCalcSwitch, UlFssOptForAttach,
SrbProbeSchSwitch, UlSchCtrlPwrUserSetOptSw,
UlPttSchOptSwitch, UlPttDataSizeEstSwitch,
EnhancedSchForSparseSwitch, UlSigSrSchDateLe-
nAdapt, UlFssWindSearchDirRandSw,
UlCellCenterMCSOptSwitch, PuschSchEscPucchS-
witch, HarqMcsOptSwitch, PreambleSchEnhSwitch,
UlPAMCSwitch, UlSchRbAllocOptSw,
UlMultiClusterSwitch, SrPairingSwitch,
UlDrbProactiveSchSwitch
Default Value: UlPacketLenAwareSchSw:Off,
EnhExtQCITtiBundlingSwitch:Off,
EnhExtQCISpsSchSwitch:Off,
UlVoipRbRsvSwitch:Off, UlThpEnhSwitch:Off,
UlDataFitterRbCalcSwitch:On,
UlFssOptForAttach:Off, SrbProbeSchSwitch:Off,
UlSchCtrlPwrUserSetOptSw:Off,
UlPttSchOptSwitch:Off, UlPttDataSizeEstSwitch:Off,
EnhancedSchForSparseSwitch:Off,
UlSigSrSchDateLenAdapt:Off, UlFssWindSearchDir-
RandSw:Off, UlCellCenterMCSOptSwitch:Off,
PuschSchEscPucchSwitch:Off,
HarqMcsOptSwitch:Off, PreambleSchEnhSwitch:Off,
UlPAMCSwitch:Off, UlSchRbAllocOptSw:Off,
UlMultiClusterSwitch:Off, SrPairingSwitch:On,
UlDrbProactiveSchSwitch:Off
witch), FDDHetNetDlCompS-
witch(FDDHetNetDlCompSwitch),
IntraDlCompJtSwitch(IntraDlCompJtSwitch)
Unit: None
Actual Value Range: IntraDlCompSwitch,
InterDlCompDcsSwitch, InterDlCompCbfSwitch,
FDDHomNetDlCompSwitch, FDDHetNetDlCompS-
witch, IntraDlCompJtSwitch
Default Value: IntraDlCompSwitch:Off,
InterDlCompDcsSwitch:Off, InterDlCompCbfS-
witch:Off, FDDHomNetDlCompSwitch:Off,
FDDHetNetDlCompSwitch:Off,
IntraDlCompJtSwitch:Off
based on NackDtxIdentifySwitch(NackDtxIdentifySwitch):
EPC(LT indicates whether the eNodeB regards NACK/DTX
E TDD) confusions as DTXs or NACKs during PUSCH
demodulation. When this option is selected, the
eNodeB regards NACK/DTX confusions as DTXs.
When this option is deselected, the eNodeB regards
NACK/DTX confusions as NACKs. This option
applies only to LTE FDD and LTE TDD.
CaDl2CCExtSwitch(CaDl2CCExtSwitch): indicates
whether to enable downlink 2CC CA on extended
bandwidth. Downlink FDD 2CC CA can reach an
aggregated bandwidth between 20 MHz and 40 MHz
(inclusive) and downlink TDD 2CC CA can reach an
aggregated bandwidth between 30 MHz and 40 MHz
(inclusive) only if this option is selected. To use this
CA feature, operators must select this option
regardless of whether the local cell acts as a PCell or
an SCell for a UE. This option takes effect only in
adaptive (frequency-based) configuration mode. This
option applies only to LTE FDD and LTE TDD.
CaDl3CCExtSwitch(CaDl3CCExtSwitch): indicates
whether to enable downlink 3CC CA on extended
bandwidth. Downlink FDD 3CC CA can reach an
aggregated bandwidth between 40 MHz and 60 MHz
(inclusive) only if this option is selected. To use this
CA feature, operators must select this option
regardless of whether the local cell acts as a PCell or
an SCell for a UE. This option takes effect only in
adaptive (frequency-based) configuration mode. This
option applies only to LTE FDD.
VolteSupportCaInterFreqMeasSw(VolteSupportCaIn-
terFreqMeasSw): indicates whether VoLTE UEs can
perform inter-frequency measurements for SCell
configuration or PCC anchoring for connected-mode
UEs. The eNodeB delivers inter-frequency
measurement configurations to CA UEs running
VoLTE services for SCell configuration or PCC
anchoring only if this option is selected. To enable the
eNodeB to configure NR SCGs based on gap-assisted
inter-frequency measurements for UEs with
concurrent VoLTE and data services, select this
option. This option applies only to LTE FDD and LTE
TDD.
CaEnhAperiodicCqiRptSwitch: indicates the aperiodic
CQI reporting mechanism in CA. If this option is
selected, then:
Dc3cSwitch(Dc3cSwitch), MultiCarrierFlexCaS-
witch(MultiCarrierFlexCaSwitch), NackDtxIdentify-
Switch(NackDtxIdentifySwitch),
CaDl2CCExtSwitch(CaDl2CCExtSwitch),
CaDl3CCExtSwitch(CaDl3CCExtSwitch),
VolteSupportCaInterFreqMeasSw(VolteSupportCaIn-
terFreqMeasSw), CaEnhAperiodicCqiRptS-
witch(CaEnhAperiodicCqiRptSwitch),
SpectrumCoordinationSwitch(SpectrumCoordina-
tionSwitch), VolteUlCaControlS-
witch(VolteUlCaControlSwitch)
Unit: None
Actual Value Range: CaDl3CCSwitch,
CaUl2CCSwitch, CaDl4CCSwitch,
InterFddTddCaSwitch, 2CCDlCaEnhanceSwitch,
CaDl5CCSwitch, CaInstantlyJudgeSwitch,
LaaCaDlSwitch, FddTddCaUlServiceFirstSwitch,
RcvA2CfgSccSwitch, Dc3cSwitch, MultiCarrierFlex-
CaSwitch, NackDtxIdentifySwitch,
CaDl2CCExtSwitch, CaDl3CCExtSwitch,
VolteSupportCaInterFreqMeasSw, CaEnhAperiodicC-
qiRptSwitch, SpectrumCoordinationSwitch,
VolteUlCaControlSwitch
Default Value: CaDl3CCSwitch:Off,
CaUl2CCSwitch:Off, CaDl4CCSwitch:Off,
InterFddTddCaSwitch:Off,
2CCDlCaEnhanceSwitch:Off, CaDl5CCSwitch:Off,
CaInstantlyJudgeSwitch:Off, LaaCaDlSwitch:Off,
FddTddCaUlServiceFirstSwitch:Off,
RcvA2CfgSccSwitch:Off, Dc3cSwitch:Off,
MultiCarrierFlexCaSwitch:Off, NackDtxIdentify-
Switch:Off, CaDl2CCExtSwitch:Off,
CaDl3CCExtSwitch:Off, VolteSupportCaInterFreq-
MeasSw:Off, CaEnhAperiodicCqiRptSwitch:Off,
SpectrumCoordinationSwitch:Off,
VolteUlCaControlSwitch:Off
torSwitch, AvoidSpurEmissInterfSwitch,
UlInterfSuppressionSwitch, AvoidCDMAInterfS-
witch, AvoidCrsConflictInterfSw
Default Value: AvoidGeranInterfSwitch:Off,
TddAvoidUpPTSInterfSwitch:Off,
AvoidPrachInterfSwitch:Off, AvoidUtranInterfS-
witch:Off, IntraBandInterfMonitorSwitch:Off,
AvoidSpurEmissInterfSwitch:Off, UlInterfSuppres-
sionSwitch:Off, AvoidCDMAInterfSwitch:Off,
AvoidCrsConflictInterfSw:Off
Cell Subfram ADD LBFD-0 Broadca Meaning: Indicates the ratio of UL subframes to DL
eAssign CELL 02009/ st of subframes in a TDD cell. For details, see 3GPP TS
ment MOD TDLBF system 36.211. This parameter applies only to LTE TDD.
CELL D-00200 informat GUI Value Range: SA0(SA0), SA1(SA1), SA2(SA2),
9 ion SA3(SA3), SA4(SA4), SA5(SA5), SA6(SA6),
LST
CELL TDLBF Basic NULL(NULL)
D-00100 uplink- Unit: None
7 downlin
k Actual Value Range: SA0, SA1, SA2, SA3, SA4,
TDLBF SA5, SA6, NULL
D-00100 subfram
701 e Default Value: SA0(SA0)
configur
TDLBF ation
D-00100
702 uplink-
downlin
TDLOF k
D-00102 subfram
6 e
TDLOF configur
D-00102 ation
601 type1&2
TDLOF uplink-
D-00102 downlin
602 k special
TDLOF subfram
D-00102 e
603 configur
ation
type 7
Optional
uplink-
downlin
k
subfram
e
configur
ation
uplink-
downlin
k
subfram
e
configur
ation
type 0
uplink-
downlin
k special
subfram
e
configur
ation
type 4
uplink-
downlin
k special
subfram
e
configur
ation
type 5
Cell MultiRr ADD LOFD-0 SFN Meaning: Indicates the type of the multi-RRU cell.
uCellMo CELL 03029/ Adaptiv GUI Value Range: SFN(SFN),
de MOD TDLOF e SFN/ CELL_COMBINATION(Cell Combination),
CELL D-00107 SDMA TWO_RRU_COMBINATION(TWO RRU
5 Combination), DIGITAL_COMBINATION(Cell
LST Inter-
CELL LOFD-0 BBP Digital Combination),
70205/ SFN MPRU_AGGREGATION(MPRU_AGGREGATION)
TDLOF Unit: None
D-00200 Inter-
8 eNodeB Actual Value Range: SFN, CELL_COMBINATION,
SFN TWO_RRU_COMBINATION,
TDLOF Based DIGITAL_COMBINATION,
D-00109 on MPRU_AGGREGATION
8 Coordin Default Value: SFN(SFN)
TDLOF ated
D-00108 eNodeB
0 Inter-
TDLOF BBP
D-00108 Adaptiv
1 e SFN/
TDLOF SDMA
D-00108 Inter-
2 eNodeB
Adaptiv
e SFN/
SDMA
Based
on
Coordin
ated
eNodeB
CellPdc Epdcch MOD LBFD-0 Physical Meaning: Indicates whether to enable algorithms
chAlgo AlgoSwi CELLP 02003/ Channel related to the EPDCCH. EpdcchFunctionSwitch:
tch DCCHA TDLBF Manage Indicates whether to support EPDCCH. If this option
LGO D-00200 ment is selected, EPDCCH is supported. This option applies
LST 3 only to LTE FDD and LTE TDD.
CELLP GUI Value Range: EpdcchFunctionS-
DCCHA witch(EpdcchFunctionSwitch)
LGO Unit: None
Actual Value Range: EpdcchFunctionSwitch
Default Value: EpdcchFunctionSwitch:Off
SRSCfg SrsCfgI MOD LBFD-0 Physical Meaning: Indicates whether to configure sounding
nd SRSCF 02003/ Channel reference signal (SRS) resources for UEs in a cell.
G TDLBF Manage The value BOOLEAN_TRUE indicates that SRS
LST D-00200 ment resources are available in the cell and can be
SRSCF 3 Virtual configured for UEs in the cell. The value
G LEOFD- 4T4R BOOLEAN_FALSE indicates that no SRS resource is
111305 available in the cell, and therefore no UE in the cell is
DL 4- configured with SRS resources. This parameter does
TDLAO Layer not take effect on: (1) FDD cell that is established on
FD-081 MIMO an LBBPc and uses four or more RX antennas. (2)
409 Based FDD cell that is established on an LBBPc and uses
TDLEO on TM9 extended cyclic prefix (CP) in the uplink. (3) TDD
FD-121 DL cell established on an LBBPc. If this parameter does
615 Flexible not take effect on a cell but SRS resources are
TDLOF 3D- available in the cell, SRS resources can be configured
D-00104 Beamfor for UEs in the cell. This parameter applies only to
9 ming LTE FDD and LTE TDD.
Single GUI Value Range: BOOLEAN_FALSE(False),
Streami BOOLEAN_TRUE(True)
ng Unit: None
Beamfor
ming Actual Value Range: BOOLEAN_FALSE,
BOOLEAN_TRUE
Default Value: BOOLEAN_TRUE(True)
SRSCfg FddSrsC MOD LBFD-0 Physical Meaning: Indicates the allocation mode of sounding
fgMode SRSCF 02003 Channel reference signal (SRS) resources in LTE FDD. This
G LEOFD- Manage parameter must be set when the SrsCfgInd parameter
LST 111305 ment is set to BOOLEAN_TRUE(True). If the
SRSCF Virtual FddSrsCfgMode parameter is set to
G 4T4R DEFAULTMODE(Default Mode), SRS resource
allocation is activated by default after a cell is
established, and SRS resources are allocated to UEs
that access the cell. If this parameter is set to
ADAPTIVEMODE(Adaptive Mode), SRS resource
allocation can be adaptively activated or deactivated
based on the cell load. After this parameter is set to
ADAPTIVEMODE(Adaptive Mode), settings of
parameters SrsAlgoSwitch, SrsSubframeCfg, and
UserSrsPeriod do not take effect. The parameter value
ADAPTIVEMODE(Adaptive Mode) is recommended
in heavy-traffic scenarios where there is a large
number of UEs in the cell. The parameter value
ADAPTIVEMODE(Adaptive Mode) does not apply
to cells established on an LBBPc. This parameter
applies only to LTE FDD.
GUI Value Range: DEFAULTMODE(Default Mode),
ADAPTIVEMODE(Adaptive Mode)
Unit: None
Actual Value Range: DEFAULTMODE,
ADAPTIVEMODE
Default Value: ADAPTIVEMODE(Adaptive Mode)
Default Value: 0
RlcPdcp CaUeRe ADD LBFD-0 Radio Meaning: Indicates the length of the reordering timer
ParaGro ordering RLCPD 02008/ Bearer that applies to non-GBR bearers in RLC AM for CA
up Timer CPPAR TDLBF Manage UEs in the 2CC CA, 3CC CA, and relaxed-backhaul-
AGROU D-00200 ment based CA states in their PCell when the number of
P 8 LTE-A UEs in RRC_CONNECTED mode does not exceed
MOD LAOFD Introduc the value of CaUeRlcParaAdptiveThd. This option
RLCPD -001001 tion applies only to LTE FDD and LTE TDD.
CPPAR GUI Value Range: Treordering_m0(0),
AGROU Treordering_m5(5), Treordering_m10(10),
P Treordering_m15(15), Treordering_m20(20),
LST Treordering_m25(25), Treordering_m30(30),
RLCPD Treordering_m35(35), Treordering_m40(40),
CPPAR Treordering_m45(45), Treordering_m50(50),
AGROU Treordering_m55(55), Treordering_m60(60),
P Treordering_m65(65), Treordering_m70(70),
Treordering_m75(75), Treordering_m80(80),
Treordering_m85(85), Treordering_m90(90),
Treordering_m95(95), Treordering_m100(100),
Treordering_m110(110), Treordering_m120(120),
Treordering_m130(130), Treordering_m140(140),
Treordering_m150(150), Treordering_m160(160),
Treordering_m170(170), Treordering_m180(180),
Treordering_m190(190), Treordering_m200(200)
Unit: None
Actual Value Range: Treordering_m0,
Treordering_m5, Treordering_m10, Treordering_m15,
Treordering_m20, Treordering_m25,
Treordering_m30, Treordering_m35,
Treordering_m40, Treordering_m45,
Treordering_m50, Treordering_m55,
Treordering_m60, Treordering_m65,
Treordering_m70, Treordering_m75,
Treordering_m80, Treordering_m85,
Treordering_m90, Treordering_m95,
Treordering_m100, Treordering_m110,
Treordering_m120, Treordering_m130,
Treordering_m140, Treordering_m150,
Treordering_m160, Treordering_m170,
Treordering_m180, Treordering_m190,
Treordering_m200
Default Value: Treordering_m20(20)
RlcPdcp CaUeSta ADD LBFD-0 Radio Meaning: Indicates the length of the status reporting
ParaGro tProhTi RLCPD 02008/ Bearer prohibition timer that applies to non-GBR bearers in
up mer CPPAR TDLBF Manage RLC AM for CA UEs in the 2CC CA, 3CC CA, and
AGROU D-00200 ment relaxed-backhaul-based CA states in their PCell when
P 8 LTE-A the number of UEs in RRC_CONNECTED mode
MOD LAOFD Introduc does not exceed the value of CaUeRlcParaAdpti-
RLCPD -001001 tion veThd. This option applies only to LTE FDD and LTE
CPPAR TDD.
AGROU GUI Value Range: m0(0), m5(5), m10(10), m15(15),
P m20(20), m25(25), m30(30), m35(35), m40(40),
LST m45(45), m50(50), m55(55), m60(60), m65(65),
RLCPD m70(70), m75(75), m80(80), m85(85), m90(90),
CPPAR m95(95), m100(100), m105(105), m110(110),
AGROU m115(115), m120(120), m125(125), m130(130),
P m135(135), m140(140), m145(145), m150(150),
m155(155), m160(160), m165(165), m170(170),
m175(175), m180(180), m185(185), m190(190),
m195(195), m200(200), m205(205), m210(210),
m215(215), m220(220), m225(225), m230(230),
m235(235), m240(240), m245(245), m250(250),
m300(300), m350(350), m400(400), m450(450),
m500(500)
Unit: None
Actual Value Range: m0, m5, m10, m15, m20, m25,
m30, m35, m40, m45, m50, m55, m60, m65, m70,
m75, m80, m85, m90, m95, m100, m105, m110,
m115, m120, m125, m130, m135, m140, m145,
m150, m155, m160, m165, m170, m175, m180,
m185, m190, m195, m200, m205, m210, m215,
m220, m225, m230, m235, m240, m245, m250,
m300, m350, m400, m450, m500
Default Value: m20(20)
SRSCfg TddSrsC MOD TDLBF Physical Meaning: Indicates the SRS configuration for LTE
fgMode SRSCF D-00200 Channel TDD. If this parameter is set to ACCESS_FIRST, the
G 3 Manage SRS configuration designed to preferentially
LST TDLAO ment guarantee the number of accessed UEs and BHCA is
SRSCF FD-081 DL 4- used. If this parameter is set to
G 409 Layer EXPERIENCE_FIRST, the SRS configuration
MIMO designed to preferentially guarantee user experience
TDLEO (for example, beamforming performance) is used. If
FD-121 Based
on TM9 this parameter is set to EXPERIENCE_ENHANCED,
615 downlink experience improves compared with that
TDLOF DL obtained when this parameter is set to
D-00104 Flexible ACCESS_FIRST. If this parameter is set to
9 3D- ACCESS_ENHANCED, more UEs can access the
Beamfor network compared with that obtained when this
ming parameter is set to EXPERIENCE_ENHANCED. The
Single values EXPERIENCE_ENHANCED and
Streami ACCESS_ENHANCED are not supported by the
ng LBBPc. If this parameter is set to
Beamfor EXPERIENCE_ENHANCED or
ming ACCESS_ENHANCED for a cell established on an
LBBPc board, the value is automatically changed to
ACCESS_FIRST when this parameter takes effect.
This parameter applies only to LTE TDD.
GUI Value Range: ACCESS_FIRST(Access First),
EXPERIENCE_FIRST(Experience First),
EXPERIENCE_ENHANCED(Experience Enhanced),
ACCESS_ENHANCED(Access Enhanced)
Unit: None
Actual Value Range: ACCESS_FIRST,
EXPERIENCE_FIRST,
EXPERIENCE_ENHANCED,
ACCESS_ENHANCED
Default Value: ACCESS_ENHANCED(Access
Enhanced)
7 Counters
8 Glossary
9 Reference Documents