MIMO(eRAN8.1_04)

eRAN

MIMO Feature Parameter Description Issue

04

Date

2015-08-31

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address:

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

Website:

http://www.huawei.com

Email:

[email protected]

Issue 04 (2015-08-31)

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

i

eRAN MIMO Feature Parameter Description

Contents

Contents 1 About This Document.................................................................................................................. 1 1.1 Scope.............................................................................................................................................................................. 1 1.2 Intended Audience.......................................................................................................................................................... 2 1.3 Change History............................................................................................................................................................... 2 1.4 Differences Between eNodeB Types.............................................................................................................................. 5

2 Overview......................................................................................................................................... 6 2.1 Introduction.................................................................................................................................................................... 6 2.2 Benefits........................................................................................................................................................................... 6 2.3 Classifications of MIMO Techniques.............................................................................................................................7 2.4 Relationships Between MIMO Techniques and Features...............................................................................................8

3 Multiple-Antenna Reception.................................................................................................... 10 3.1 Introduction...................................................................................................................................................................11 3.2 Receive Diversity..........................................................................................................................................................11 3.3 MU-MIMO................................................................................................................................................................... 12 3.3.1 Principles of MU-MIMO...........................................................................................................................................13 3.3.2 Signal Combining in MU-MIMO..............................................................................................................................14 3.3.3 UE Pairing in MU-MIMO......................................................................................................................................... 14 3.4 Adaptive MIMO Technique Switching........................................................................................................................ 14

4 Multiple-Antenna Transmission.............................................................................................. 16 4.1 Introduction.................................................................................................................................................................. 17 4.1.1 Basic Concepts.......................................................................................................................................................... 17 4.1.2 Transmission Modes.................................................................................................................................................. 19 4.2 Transmit Diversity........................................................................................................................................................ 21 4.2.1 Open-Loop Transmit Diversity..................................................................................................................................21 4.2.2 Closed-Loop Transmit Diversity............................................................................................................................... 23 4.3 Spatial Multiplexing..................................................................................................................................................... 23 4.3.1 Principles of Spatial Multiplexing............................................................................................................................. 23 4.3.2 Open-Loop Spatial Multiplexing...............................................................................................................................26 4.3.3 Closed-Loop Spatial Multiplexing............................................................................................................................ 26 4.4 TM9 Transmission Mode..............................................................................................................................................27 4.4.1 Technical Principles...................................................................................................................................................27 4.4.2 Technical Value..........................................................................................................................................................32 Issue 04 (2015-08-31)


ii


Contents

4.5 Working Mode.............................................................................................................................................................. 35 4.5.1 Fixed Configuration of Transmission Modes............................................................................................................ 35 4.5.2 Adaptive Configuration of Transmission Modes.......................................................................................................36 4.5.3 TM9 Configuration....................................................................................................................................................38 4.6 Optimization of Combined RRUs................................................................................................................................ 38 4.6.1 CRS Port Mapping.....................................................................................................................................................39 4.7 Configuration for CSI Reporting.................................................................................................................................. 40 4.7.1 Introduction to CSI Reporting Modes....................................................................................................................... 41 4.7.2 Comparison Between Periodic and Aperiodic CSI Reporting.................................................................................. 42 4.7.3 Configuration of CSI Reporting Mode and Period....................................................................................................43 4.7.4 Optimized Periodic CQI Reporting on the PUCCH.................................................................................................. 44 4.7.5 Enhanced Aperiodic CQI Reporting..........................................................................................................................45 4.7.6 Aperiodic CQI Reporting Optimization.................................................................................................................... 46 4.7.7 Workaround for UE Incompatibility in Aperiodic CQI Reporting Mode................................................................. 46 4.7.8 Downlink Rank Optimization....................................................................................................................................47 4.7.9 Downlink Rank Detection......................................................................................................................................... 47

5 Related Features...........................................................................................................................49 5.1 Features Related to LBFD-00202001 UL 2-Antenna Receive Diversity.....................................................................49 5.2 Features Related to LOFD-001005 UL 4-Antenna Receive Diversity.........................................................................49 5.3 Features Related to LOFD-001002 UL 2x2 MU-MIMO............................................................................................. 50 5.4 Features Related to LOFD-001058 UL 2x4 MU-MIMO............................................................................................. 51 5.5 Features Related to LOFD-001001 DL 2x2 MIMO..................................................................................................... 53 5.6 Features Related to LOFD-001003 DL 4x2 MIMO..................................................................................................... 55 5.7 Features Related to LOFD-001060 DL 4x4 MIMO..................................................................................................... 57 5.8 Features Related to LBFD-002031 Support of aperiodic CQI reports......................................................................... 59 5.9 Features Related to LBFD-060101 Optimization of Periodic and Aperiodic CQI Reporting..................................... 59

6 Network Impact........................................................................................................................... 60 6.1 LBFD-00202001 UL 2-Antenna Receive Diversity.....................................................................................................60 6.2 LOFD-001005 UL 4-Antenna Receive Diversity........................................................................................................ 60 6.3 LOFD-001002 UL 2x2 MU-MIMO............................................................................................................................. 61 6.4 LOFD-001058 UL 2x4 MU-MIMO............................................................................................................................. 62 6.5 LOFD-001001 DL 2x2 MIMO.....................................................................................................................................62 6.6 LOFD-001003 DL 4x2 MIMO.....................................................................................................................................63 6.7 LOFD-001060 DL 4x4 MIMO.....................................................................................................................................68 6.8 LBFD-002031 Support of aperiodic CQI reports.........................................................................................................69 6.9 LBFD-060101 Optimization of Periodic and Aperiodic CQI Reporting..................................................................... 69

7 Engineering Guidelines for Multiple-Antenna Receive Diversity................................... 71 7.1 When to Use Multiple-Antenna Receive Diversity...................................................................................................... 71 7.2 Required Information................................................................................................................................................... 71 7.3 Planning........................................................................................................................................................................ 72 7.4 Deployment of Multiple-Antenna Receive Diversity...................................................................................................73 Issue 04 (2015-08-31)


iii


Contents

7.4.1 Requirements............................................................................................................................................................. 73 7.4.2 Data Preparation........................................................................................................................................................ 74 7.4.3 Precautions.................................................................................................................................................................76 7.4.4 Hardware Adjustment................................................................................................................................................77 7.4.5 Initial Configuration.................................................................................................................................................. 77 7.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs..................................................77 7.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs............................................................... 78 7.4.5.3 Using the CME to Perform Single Configuration.................................................................................................. 79 7.4.5.4 Using MML Commands......................................................................................................................................... 80 7.4.6 Activation Observation..............................................................................................................................................85 7.4.7 Reconfiguration......................................................................................................................................................... 86 7.4.8 Deactivation...............................................................................................................................................................86 7.4.8.1 Using the CME to Perform Batch Configuration................................................................................................... 86 7.4.8.2 Using the CME to Perform Single Configuration.................................................................................................. 87 7.4.8.3 Using MML Commands......................................................................................................................................... 87 7.5 Maintenance..................................................................................................................................................................88 7.5.1 Performance Monitoring............................................................................................................................................88 7.5.2 Parameter Optimization............................................................................................................................................. 88 7.5.3 Troubleshooting......................................................................................................................................................... 88

8 Engineering Guidelines for MU-MIMO.................................................................................90 8.1 When to Use MU-MIMO............................................................................................................................................. 90 8.2 Required Information................................................................................................................................................... 90 8.3 Planning........................................................................................................................................................................ 90 8.4 Deployment of MU-MIMO.......................................................................................................................................... 91 8.4.1 Requirements............................................................................................................................................................. 91 8.4.2 Data Preparation........................................................................................................................................................ 92 8.4.3 Precautions.................................................................................................................................................................93 8.4.4 Hardware Adjustment................................................................................................................................................94 8.4.5 Initial Configuration.................................................................................................................................................. 94 8.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs..................................................94 8.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs............................................................... 95 8.4.5.3 Using the CME to Perform Single Configuration.................................................................................................. 96 8.4.5.4 Using MML Commands......................................................................................................................................... 96 8.4.6 Activation Observation..............................................................................................................................................97 8.4.7 Reconfiguration......................................................................................................................................................... 97 8.4.8 Deactivation...............................................................................................................................................................97 8.4.8.1 Using the CME to Perform Batch Configuration................................................................................................... 97 8.4.8.2 Using the CME to Perform Single Configuration.................................................................................................. 98 8.4.8.3 Using MML Commands......................................................................................................................................... 98 8.5 Maintenance..................................................................................................................................................................98 8.5.1 Performance Monitoring............................................................................................................................................98 8.5.2 Parameter Optimization............................................................................................................................................. 98 Issue 04 (2015-08-31)


iv


Contents

8.5.3 Troubleshooting......................................................................................................................................................... 98

9 Engineering Guidelines for Multiple-Antenna Transmission.........................................100 9.1 When to Use Multiple-Antenna Transmission........................................................................................................... 100 9.2 Required Information................................................................................................................................................. 101 9.3 Planning...................................................................................................................................................................... 103 9.4 Deploying Multiple-Antenna Transmission............................................................................................................... 104 9.4.1 Requirements........................................................................................................................................................... 104 9.4.2 Data Preparation...................................................................................................................................................... 105 9.4.3 Precautions...............................................................................................................................................................115 9.4.4 Hardware Adjustment.............................................................................................................................................. 116 9.4.5 Initial Configuration................................................................................................................................................ 129 9.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs................................................130 9.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs............................................................. 131 9.4.5.3 Using the CME to Perform Single Configuration................................................................................................ 131 9.4.5.4 Using MML Commands....................................................................................................................................... 132 9.4.6 Activation Observation............................................................................................................................................144 9.4.6.1 Observing Adaptive Configuration of Transmission Modes................................................................................144 9.4.6.2 Observing Fixed Configuration of Transmission Modes..................................................................................... 145 9.4.6.3 Observing Periodic and Aperiodic CQI Reporting Optimization........................................................................ 152 9.4.7 Reconfiguration....................................................................................................................................................... 155 9.4.8 Deactivation.............................................................................................................................................................155 9.4.8.1 Using the CME to Perform Batch Configuration................................................................................................. 155 9.4.8.2 Using the CME to Perform Single Configuration................................................................................................ 156 9.4.8.3 Using MML Commands....................................................................................................................................... 156 9.5 Maintenance................................................................................................................................................................160 9.5.1 Performance Monitoring..........................................................................................................................................160 9.5.2 Parameter Optimization........................................................................................................................................... 162 9.5.3 Troubleshooting....................................................................................................................................................... 162

10 Parameters................................................................................................................................. 164 11 Counters.................................................................................................................................... 199 12 Glossary..................................................................................................................................... 253 13 Reference Documents............................................................................................................. 254

Issue 04 (2015-08-31)


v


1 About This Document

1

About This Document

1.1 Scope This document describes the multiple-input multiple-output (MIMO) feature, including its technical principles, related features, network impact, and engineering guidelines. This document covers the following features: l

LBFD-00202001 UL 2-Antenna Receive Diversity

l

LOFD-001005 UL 4-Antenna Receive Diversity

l

LOFD-001002 UL 2x2 MU-MIMO

l


l

LOFD-001001 DL 2x2 MIMO

l


l


l

LBFD-002031 Support of aperiodic CQI reports

l

LBFD-060101 Optimization of Periodic and Aperiodic CQI Reporting

This document applies to the following types of eNodeBs. eNodeB Type

Model

Macro

3900 series eNodeB

Micro

BTS3202E

LampSite

DBS3900 LampSite

Any managed objects (MOs), parameters, alarms, or counters described herein correspond to the software release delivered with this document. Any future updates will be described in the product documentation delivered with future software releases. This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD, and "eNodeB" refers to LTE FDD eNodeB. Issue 04 (2015-08-31)


1



1.2 Intended Audience This document is intended for personnel who: l

Need to understand the features described herein

l

Work with Huawei products

1.3 Change History This section provides information about the changes in different document versions. There are two types of changes, which are defined as follows: l

Feature change Changes in features and parameters of a specified version as well as the affected entities

l

Editorial change Changes in wording or addition of information and any related parameters affected by editorial changes. Editorial change does not specify the affected entities.

eRAN8.1 04 (2015-08-31) This issue includes the following changes. Change Type

Change Description

Parameter Change

Affected Entity

Feature change

None

None

N/A

Editorial change

Revised descriptions in this document.

None

N/A

eRAN8.1 03 (2015-06-30) This issue includes the following changes. Change Type

Change Description

Parameter Change

Affected Entity

Feature change

None

None

N/A

Editorial change

Revised descriptions in this document.

None

N/A

eRAN8.1 02 (2015-04-30) This issue includes the following changes. Issue 04 (2015-08-31)


2



Change Type

Change Description

Parameter Change

Affected Entity

Feature change

Added the downlink rank detection function. For details, see the following sections:

Added the parameter CellDlschAlgo.DlRankDe tectSwitch.

N/A

None

N/A

l 4.7.9 Downlink Rank Detection l 9.4.2 Data Preparation l 9.4.5.4 Using MML Commands Editorial change

None

eRAN8.1 01 (2015-03-23) This issue does not include any changes.

eRAN8.1 Draft A (2015-01-15) Compared with Issue 04 (2014-12-30) of eRAN7.0, Draft A (2015-01-15) of eRAN8.1 includes the following changes.

Issue 04 (2015-08-31)


3



Change Type

Change Description

Parameter Change

Affected Entity

Feature change

Added the following functions:

Added the following parameters:

N/A

l Downlink 4x4 MIMO in TM9 [Trial] l Downlink 4x2 MIMO in TM9 [Trial] l Downlink 2x2 MIMO in TM9 Added a workaround for UE incompatibility in aperiodic CQI reporting mode. For details, see 4.7.7 Workaround for UE Incompatibility in Aperiodic CQI Reporting Mode. Added thresholds for transitions between configuration of CSI-RS and non-configuration of CSI-RS in adaptive CSI-RS configuration mode. For details, see 9.4.2 Data Preparation. Modified some differences between eNodeB types. For details, see 1.4 Differences Between eNodeB Types. Added mutually exclusive features of LOFD-001003 DL 4x2 MIMO and LOFD-001060 DL 4x4 MIMO. For details, see 5.6 Features Related to LOFD-001003 DL 4x2 MIMO and 5.7 Features Related to LOFD-001060 DL 4x4 MIMO.

l ENodeBAlgoSwitch.C OMPATIBILITYCTRL SWITCH l CellCsiRsParaCfg.Csi RsConfigUserNumTh l CellCsiRsParaCfg.Csi RsUnconfigUserNumT h l CellCsiRsParaCfg.Csi RsConfigUserRatioTh l CellCsiRsParaCfg.Csi RsUnconfigUserRatioTh l CellAlgoSwitch.EnhM IMOSwitch l Cell.CrsPortNum l CellCsiRsParaCfg.Lo calCellId l CellCsiRsParaCfg.Csi RsSwitch l CellCsiRsParaCfg.Csi RsPeriod l CellDlschAlgo.MbsfnS fCfg

Modified the impact of LOFD-001001 DL 2x2 MIMO on system capacity. For details, see 6.5 LOFD-001001 DL 2x2 MIMO. Editorial change

Issue 04 (2015-08-31)

None

None


N/A

4



1.4 Differences Between eNodeB Types Feature Support by Macro, Micro, and LampSite eNodeBs Feature ID

Feature Name

Supporte d by Macro eNodeBs

Supported by Micro eNodeBs

Supported by LampSite eNodeBs

LBFD-00202001

UL 2-Antenna Receive Diversity

Yes

Yes

Yes

LOFD-001005

UL 4-Antenna Receive Diversity

Yes

Yes

No

LOFD-001002

UL 2x2 MU-MIMO

Yes

No

Yes

LOFD-001058

UL 2x4 MU-MIMO

Yes

Yes

No

LOFD-001001

DL 2x2 MIMO

Yes

Yes

Yes

LOFD-001003

DL 4x2 MIMO

Yes

No

No

LOFD-001060

DL 4x4 MIMO

Yes

No

No

LBFD-002031

Support of aperiodic CQI reports

Yes

Yes

Yes

LBFD-060101

Optimization of Periodic and Aperiodic CQI Reporting

Yes

No

Yes

Function Implementation in Macro, Micro, and LampSite eNodeBs

Issue 04 (2015-08-31)

Function

Difference

Optimization of Combined RRUs

The optimization of combined RRUs differs among eNodeB types. Macro and LampSite eNodeBs support the optimization of combined RRUs while micro eNodeBs do not. For details, see 4.6 Optimization of Combined RRUs and 9.4.4 Hardware Adjustment.


5


2 Overview

2

Overview

2.1 Introduction Due to the rapid development of wireless communications, customers have ever increasing requirements for system capacity and spectral efficiency. Various solutions, such as expanding the system bandwidth and increasing the modulation order, have emerged. However, expanding the system bandwidth only increases system capacity without effectively increasing the spectral efficiency, and increasing the modulation order increases the spectral efficiency only to a limited extent because the modulation order can hardly be doubled. Multiple-input multiple-output (MIMO) is developed to provide doubled and more spectral efficiency. As an extension of single-input single-output (SISO), MIMO uses multiple antennas at the transmitter and/or receiver in combination with several signal processing techniques. Generally speaking, single-input multiple-output (SIMO), multiple-input singleoutput (MISO), and beamforming are all categorized under MIMO. Figure 2-1 shows an example of MxN MIMO, which uses M transmit (TX) antennas and N receive (RX) antennas. Figure 2-1 Example of MIMO

2.2 Benefits Theoretically, channel capacity scales linearly with the smaller one between the number of transmit antennas and the number of receive antennas. By adopting specific signal processing techniques, MIMO improves radio link reliability and signal quality, which further helps increase system capacity, coverage, and user rate, and ultimately improves user experience. MIMO also brings power gains, multiplexing gains, diversity gains, and array gains. Issue 04 (2015-08-31)


6


2 Overview

Power Gains Assuming that each transmit antenna has the same transmit power, M transmit antennas bring a power gain of 10 lg(M) dB compared with the scenario in which only one transmit antenna is used. In noise-limited scenarios, power gains indicate larger signal to interference plus noise ratios (SINRs) at the receiver and improved receive signal quality.

Multiplexing Gains Multiplexing gains are subject to the multiplexing orders of spatial channels. If channels between transmit and receive antennas are mutually orthogonal and signals from transmit antennas are also mutually independent and transmitted at the same data rate in an MxN MIMO system, this system brings a theoretical spatial multiplexing gain of Min(M,N) compared with the scenario in which one transmit antenna is used. Min(M,N) indicates the smaller number of M and N. The multiplexing order theoretically represents the spatial channel capacity. Theoretically, the channel capacity of an MxN system is Min(M,N) times that of an SISO system. Multiplexing gains indicate the increase in transmission rates. For example, when the downlink bandwidth is 20 MHz, the theoretical peak rate of a single UE is 75 Mbit/s in 1x2 SIMO, 150 Mbit/s in 2x2 MIMO, and approximately 300 Mbit/s in 4x4 MIMO.

Diversity Gains Diversity gains are subject to the diversity orders of spatial channels. If channels between transmit and receive antennas are mutually orthogonal and signals from all transmit antennas are the same, the MxN MIMO system brings a theoretical diversity gain of MxN compared with the SISO system. The diversity order theoretically represents the fault tolerance capability of a spatial channel. Theoretically, the fault tolerance capability of an MxN system is MxN times that of a SISO system. Diversity gains indicate the stability of SINRs sensed at the receiver and the reliability of radio signal reception.

Array Gains Compared with a SISO system, a 1xN MIMO system and an Mx1 MIMO system bring array gains of 10 lg(N) dB and 10 lg(M) dB, respectively. Array gains indicate the improved SINR sensed at the receiver and signal quality.

2.3 Classifications of MIMO Techniques LTE systems use various MIMO techniques in both the uplink (UL) and downlink (DL) to increase spectral efficiency. In addition to the MIMO techniques that will be described in this section, 3GPP specifications provide higher-level MIMO techniques. For example: l

Issue 04 (2015-08-31)

In Release 10, transmission mode 9 (TM9) and TM2 are added to the downlink and uplink, respectively. In TM9, a maximum of eight layers are supported. In TM2, a maximum of four layers are supported. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

7


l

In Release 11, the coordinated multi-point (CoMP) technique is added.

l

In Release 12, 3D-MIMO may be added.

2 Overview

Downlink MIMO Techniques Downlink MIMO techniques can be classified as follows: Open-Loop MIMO and Closed-Loop MIMO Downlink MIMO techniques are classified into open-loop MIMO and closed-loop MIMO based on whether UEs are required to report precoding matrix indicators (PMIs) for eNodeB downlink data transmission. Open-loop MIMO does not require UEs to report PMIs while closed-loop MIMO requires UEs to report PMIs. Transmit Diversity and Spatial Multiplexing Downlink MIMO techniques are classified into transmit diversity and spatial multiplexing based on the number of independent data block transmitted over multiple antennas using the same time-frequency resource. When transmit diversity is adopted, only one data block can be transmitted at each time. When spatial multiplexing is adopted, one or more data blocks can be transmitted at each time. When open-loop MIMO, closed-loop MIMO, transmit diversity, and spatial multiplexing are combined, downlink MIMO techniques are further classified into four categories: open-loop transmit diversity, closed-loop transmit diversity, open-loop spatial multiplexing, and closedloop spatial multiplexing. SU-MIMO and MU-MIMO MIMO techniques are classified into single-user MIMO (SU-MIMO) and multi-user MIMO (MU-MIMO) based on the number of UEs related to the data block transmitted using the same time-frequency resource. When SU-MIMO is adopted, data blocks are transmitted to or received from only one UE. When MU-MIMO is adopted, data blocks are transmitted to or received from multiple UEs.

Uplink MIMO Techniques In the uplink, the UE compliant with 3GPP Release 8 or 9 uses only one transmit antenna and the eNodeB uses multiple receive antennas. Therefore, only receive diversity is used. Similar to downlink MIMO techniques, uplink MIMO techniques can also be classified into SUMIMO and MU-MIMO.

2.4 Relationships Between MIMO Techniques and Features The following table lists the relationships between 3GPP-defined MIMO techniques, Huawei MIMO techniques, and Huawei MIMO features.

Issue 04 (2015-08-31)


8


2 Overview

Table 2-1 Relationships between MIMO techniques and features 3GPP-defined MIMO Technique

Huawei MIMO Technique

Huawei MIMO Feature

Uplink SU-MIMO

Receive diversity

LBFD-00202001 UL 2-Antenna Receive Diversity LOFD-001005 UL 4-Antenna Receive Diversity (not applicable to LampSite eNodeBs)

Uplink MU-MIMO

MU-MIMO

LOFD-001002 UL 2x2 MU-MIMO LOFD-001058 UL 2x4 MU-MIMO (not applicable to LampSite eNodeBs)

Transmit diversity

Open-loop transmit diversity

Closed-loop spatial multiplexing using a single transmission layer

Closed-loop transmit diversity

Large-delay cyclic delay diversity (CDD) spatial multiplexing

Open-loop spatial multiplexing

Closed-loop spatial multiplexing


LOFD-001001 DL 2x2 MIMO LOFD-001003 DL 4x2 MIMO (not applicable to LampSite eNodeBs) LOFD-001060 DL 4x4 MIMO (not applicable to LampSite eNodeBs)

NOTE

l DL MxN MIMO indicates that the eNodeB transmits data using M antenna ports and that the UE receives data using N antennas. For detailed information about antenna ports, see 4.1 Introduction. l UL MxN MU-MIMO indicates that M UEs transmit data using the same time-frequency resource and that the eNodeB receives data using N antennas. Each UE transmits data using one antenna.

Issue 04 (2015-08-31)


9


3

3 Multiple-Antenna Reception

Multiple-Antenna Reception

This chapter describes the principles of multiple-antenna reception. For details about engineering guidelines, see 7 Engineering Guidelines for Multiple-Antenna Receive Diversity and 8 Engineering Guidelines for MU-MIMO.

Issue 04 (2015-08-31)


10



3.1 Introduction Multiple-antenna reception is a MIMO technique in which multiple antennas are used to receive signals and certain algorithms are used to combine the received signals. Multipleantenna reception on the eNodeB side is similar to that on the UE side. This document describes only multiple-antenna reception on the eNodeB side. eNodeBs support two multiple-antenna reception techniques: receive diversity and MUMIMO. This chapter describes the principles and application scenarios for both techniques and for adaptive switching between them. Multiple-antenna reception involves the following features: l


l


l


l


3.2 Receive Diversity Receive diversity involves the following features: l


l


In receive diversity mode, each UE transmits data using one transmit antenna and dedicated time-frequency resource while the eNodeB receives the data using multiple antennas and then combines the received data. This process maximizes the SINR, brings diversity and array gains, and improves cell capacity and coverage. The radio channel from the transmitter to the receiver may experience time-varying deep fading of 10 dB to 20 dB due to its fading characteristics, which will lead to SINR fluctuations at the receiver. If the receiver uses multiple antennas for data reception, the combined signals experience a lower probability of deep fading than the signals received by a single antenna, because there is a relatively low probability that deep fading occurs simultaneously on different antennas. White noises on different antennas are uncorrelated, and therefore the power of the combined noise remains unchanged. However, the energy of the combined signal increases several-fold, which brings array gains. Figure 3-1 shows the principles of receive diversity.

Issue 04 (2015-08-31)


11



Figure 3-1 Principles of receive diversity

As shown in the previous figure, the UE sends signal x to antennas r1 to rM of the eNodeB on different channels. The eNodeB applies a weight wi to each received signal, and then combines the weighted signals into signal y. The combined signal can be expressed as follows: y = W (Hx + N) The variables in the previous formula and figure are described as follows: l

W = (w1 ... wM): 1xM vector composed of the receive antenna weights.

l

H = (h1 ... hM)T: Mx1 channel matrix. hi indicates the channel coefficient, and T indicates the transposition of the matrix. A signal changes in amplitude and phase after passing a channel. Multiplying the signal by the channel coefficient can obtain the changed signal.

l

N = (n1 ... nM)T: Mx1 vector composed of the noises received by the receive antennas.

l

x: transmit signal.

Receive signal combination, especially the calculation of the weights to be applied to each antenna, is key to receive diversity. For details about signal combining, see Receiver Technologies Feature Parameter Description.

3.3 MU-MIMO This section describes the optional features LOFD-001002 UL 2x2 MU-MIMO and LOFD-001058 UL 2x4 MU-MIMO. MU-MIMO enables multiple UEs to use the same time-frequency resources for uplink data transmission. In addition to bringing diversity and array gains like uplink receive diversity, MU-MIMO also brings multiplexing gains. System gains brought by MU-MIMO are subject to the SINRs of paired UEs and UE channel correlations: l

Issue 04 (2015-08-31)

If the paired UEs have high SINRs and their channels are approximately orthogonal, interference between these UEs is effectively mitigated. In this scenario, MU-MIMO effectively increases cell capacity. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

12


l


If the paired UEs have low SINRs or their channels are highly correlated, interference between the UEs cannot be effectively mitigated. In this scenario, MU-MIMO may even decrease cell capacity. Therefore, pairing of such UEs is not recommended.

If a certain number of UEs with high SINRs are moving at low speed, LOFD-001002 UL 2x2 MU-MIMO and LOFD-001058 UL 2x4 MU-MIMO are recommended to increase spectral efficiency. If UEs are moving at high speed or ultra high speed, their channel quality changes fast and radio link conditions are unreliable. MU-MIMO is not recommended for such UEs because it may lead to system performance deterioration. MU-MIMO is controlled by the UlVmimoSwitch option of the CellAlgoSwitch.UlSchSwitch parameter.

3.3.1 Principles of MU-MIMO In MU-MIMO mode, the number of UEs that use the same time-frequency resource cannot exceed the number of receive antennas employed on the eNodeB. In the current version, the eNodeB allows two UEs to use the same time-frequency resources in UL 2x2 MU-MIMO and UL 2x4 MU-MIMO. Figure 3-2 shows UL 2x2 MU-MIMO. Figure 3-2 Principles of 2x2 MU-MIMO

As shown in the previous figure, UE1 and UE2 use the same time-frequency resource to transmit signals x1 and x2, respectively, on their channels to the eNodeB. After applying weights to the signals received from antennas, the MIMO decoder in the eNodeB combines two groups of receive signals into y1 and y2, which are the estimated values of x1 and x2, respectively. The eNodeB calculates the weight w and detects the UEs that use the same timefrequency resource for pairing. The process of calculating the estimated values of signals x1 and x2 can be regarded as two independent processes of receive diversity. Signals x1 and x2 can be regarded as interference Issue 04 (2015-08-31)


13



with each other. Therefore, MU-MIMO, similar to receive diversity, also brings diversity and array gains. The principle of UL 2x4 MU-MIMO is the same as that of UL 2x2 MU-MIMO. Compared with 2x2 MU-MIMO, 2x4 MU-MIMO brings larger diversity and array gains and reduces more interference between paired UEs, because it uses more receive antennas. Therefore, 2x4 MU-MIMO more effectively increases cell throughput and spectral efficiency, reduces the average service delay per cell, and ultimately improves user experience. The key techniques of MU-MIMO are signal combining and UE pairing.

3.3.2 Signal Combining in MU-MIMO In 2x2 MU-MIMO, the eNodeB uses only two antennas for reception and it is difficult for the eNodeB to mitigate inter-cell interference during signal combining even when using interference rejection combining (IRC). Therefore, 2x2 MU-MIMO cannot provide high capacity gains for multiple cells. For details about signal combining, see Receiver Technologies Feature Parameter Description.

3.3.3 UE Pairing in MU-MIMO UE pairing in MU-MIMO is a process in which an eNodeB attempts to select a pair of the best UEs for transmission when MU-MIMO is enabled. The selected pair of UEs has approximately orthogonal channels or provides gains to the system. Generally, UEs with high SINRs can contribute to better UE pairing performance than those with low SINRs. UE pairing in MU-MIMO increases the system capacity and spectral efficiency. The eNodeB attempts to pair UEs for MU-MIMO in each transmission time interval (TTI). The procedure is as follows: 1.

Selects candidate UEs for pairing. If a UE has been scheduled, the eNodeB attempts to pair it with another UE.

2.

Estimates the resulting SINR and spectral efficiency. Based on the SINRs and channel correlation of the two UEs, the eNodeB estimates the SINR and spectral efficiency that will be achieved after the UEs are paired. NOTE

The SINR of UEs before pairing is measured by the serving cell based on the current channel conditions. The paired UEs begin to transmit data after four subframes, which unavoidably results in estimation inaccuracy and affects the final spectral efficiency after UE pairing.

3.

Paires the selected UEs. If the estimated spectral efficiency is higher than the separate spectral efficiencies of the two UEs, the eNodeB pairs them. Otherwise, the eNodeB does not pair them.

4.

Schedules the paired UEs. The eNodeB allocates the same time-frequency resource to the paired UEs for data transmission.

3.4 Adaptive MIMO Technique Switching eNodeBs support adaptive switching between receive diversity and MU-MIMO. Issue 04 (2015-08-31)


14



When the UlVmimoSwitch option of the CellAlgoSwitch.UlSchSwitch parameter is selected, the eNodeB adaptively switches between receive diversity and MU-MIMO based on UE channel conditions. When equipped with two receive antennas, the eNodeB supports adaptive switching between uplink 2-antenna receive diversity and uplink 2x2 MU-MIMO. When equipped with four receive antennas, the eNodeB supports adaptive switching between uplink 4-antenna receive diversity and uplink 2x4 MU-MIMO. When adaptive switching between receive diversity and MU-MIMO is enabled, the eNodeB attempts to pair UEs in each TTI. If the pairing succeeds, MU-MIMO is used. Otherwise, receive diversity is used.

Issue 04 (2015-08-31)


15


4

4 Multiple-Antenna Transmission

Multiple-Antenna Transmission

This chapter describes the principles of multiple-antenna transmission. For engineering guidelines, see 9 Engineering Guidelines for Multiple-Antenna Transmission.

Issue 04 (2015-08-31)


16



4.1 Introduction Multiple-antenna transmission is a MIMO technique in which multiple antennas are used to transmit signals and certain algorithms are used for signal processing. eNodeBs support multiple-antenna transmission while UEs do not. This chapter describes multiple-antenna transmission on the eNodeB side. Multiple-antenna transmission involves the following features: l


l


l


l

LBFD-002031 Support of aperiodic CQI reports

l

LBFD-060101 Optimization of Periodic and Aperiodic CQI Reporting

4.1.1 Basic Concepts To better understand multiple-antenna transmission, we need to understand the basic concepts involved in the LTE downlink physical channel processing procedure, as shown in Figure 4-1. Figure 4-1 LTE downlink physical channel processing procedure

Table 4-1 lists information about codewords, layers, ranks, and antenna ports in different downlink MIMO techniques. Note that: l

Space frequency block coding (SFBC) is a transmit diversity technique with two antenna ports.

l

SFBC+FSTD is a transmit diversity technique with four antenna ports, where FSTD stands for frequency switched transmit diversity.

l

Precoding for large delay CDD is an open-loop spatial multiplexing technique.

l

Precoding without CDD is a closed-loop spatial multiplexing technique.

Table 4-1 Information about codewords, layers, ranks, and antenna ports in different downlink MIMO techniques Downlink MIMO Technique Issue 04 (2015-08-31)

Number of Codewords

Number of Layers


Rank

Antenna Port

17



SIMO

1

1

1

0

SFBC

1

2

1

0, 1

SFBC+FSTD

1

4

1

0, 1, 2, 3

Precoding for large delay CDD

2

2

2

0, 1

2

2

2

0, 1, 2, 3

2

3

3

0, 1, 2, 3

2

4

4

0, 1, 2, 3

1

1

1

0, 1

1

1

1

0, 1, 2, 3

2

2

2

0, 1

2

2

2

0, 1, 2, 3

2

3

3

0, 1, 2, 3

2

4

4

0, 1, 2, 3

Precoding without CDD

Codewords Codewords are data formed after channel coding. Different codewords represent different data. By transmitting different data, MIMO implements spatial multiplexing. To reduce the overhead on channel quality indicator (CQI) and ACK/NACK reporting, LTE supports a maximum of two codewords. In transmit diversity, the number of codewords is 1. In addition, when there is only one antenna at the transmit or receive end, the number of codeword can only be 1. When there are two or more antennas at both transmit and receive ends, the number of codewords depends on the radio channel conditions and UE category. Dual-codeword transmission is mainly used in scenarios with high SINR, low channel correlation, and UE category of 2 or above.

Layers The number of codewords may be different from the number of transmit antenna ports. Therefore, codewords need to be mapped to antenna ports. This is implemented through layer mapping and precoding. In layer mapping, the codewords are mapped to multiple layers according to certain rules. In precoding, the layered data is precoded and mapped to different antenna ports. In transmit diversity, the number of layers is equal to the number of antenna ports for transmitting cell-specific reference signals (CRSs). In spatial multiplexing, the number of layers is equal to the number of scheduled data blocks (that is, the rank value). Multi-layer transmission requires that the UE be of category 2 or above. Downlink 2x2 MIMO and 4x2 MIMO support a maximum of two layers. Downlink 4x4 MIMO supports a maximum of four layers. Issue 04 (2015-08-31)


18



Ranks The rank of transmit diversity is 1, and the rank of spatial multiplexing is equal to the number of layers. Downlink 2x2 MIMO and 4x2 MIMO supports rank 1 or 2, and downlink 4x4 MIMO support rank 1, 2, 3, or 4. Note that rank x indicates that the rank is equal to x.

Precoding Precoding performs mapping from layers to antenna ports. For details about precoding, see section 6.3.4 "Precoding" in 3GPP TS 36.211 V10.5.0.

Antenna Port Antenna ports mentioned in this document are logical ports used for transmission. They do not have one-to-one relationship with physical antennas. Signals on one antenna port can be transmitted over one or more physical antennas. Different antennas ports are used to transmit different reference signals. The following table provides an example: Antenna Port

Reference Signal

p=0

CRS

p = {0, 1} p = {0, 1, 2, 3} p=4

Multimedia Broadcast multicast service Single Frequency Network (MBSFN) reference signal

p = {5, 7, 8, 9, 10}

UE-specific reference signal

For the mapping from reference signals to resource elements (REs), see section 6.10 "Reference signals" in 3GPP TS 36.211 V10.5.0.

4.1.2 Transmission Modes 3GPP defines nine transmission modes, which are described in section 7.1 "UE procedure for receiving the physical downlink shared channel" in 3GPP TS 36.213 V10.6.0. The following table describes the transmission modes supported by FDD eNodeBs.

Issue 04 (2015-08-31)


19



Table 4-2 Transmission modes supported by FDD eNodeBs Transmission Mode

MIMO Technique Defined in 3GPP Specifications

Description

TM1

Single antenna port (port 0)

The reference signal (RS) pattern corresponding to antenna port 0 is used for transmission.

TM2

Transmit diversity

Open-loop transmit diversity is used.

TM3

Transmit diversity

If only one data block is transmitted, open-loop transmit diversity is used.

Large-delay CDD spatial multiplexing

If multiple data blocks are transmitted, open-loop spatial multiplexing is used.

Transmit diversity

If only one data block is transmitted without using the PMIs reported by UEs, open-loop transmit diversity is used.


If one or more data blocks are transmitted using the PMIs reported by UEs, closed-loop spatial multiplexing is used.

Transmit diversity

If only one data block is transmitted without using the PMIs reported by UEs, open-loop transmit diversity is used.

Closed-loop spatial multiplexing using a single transmission layer

If only one data block is transmitted using the PMIs reported by UEs, closed-loop transmit diversity is used.

Transmit diversity

If the PMIs reported by UEs are not used for signal processing at the transmitter and only one antenna port is used for the physical broadcast channel (PBCH) in non-MBSFN subframes, antenna port 0 is used for transmission. Otherwise, transmit diversity is used and only one data block is transmitted.

Spatial multiplexing

If the PMIs reported by UEs are used for signal processing at the transmitter, spatial multiplexing is used and one or more data blocks are transmitted.

TM4

TM6

TM9

Issue 04 (2015-08-31)


20



NOTE

In this document, open-loop transmit diversity and open-loop spatial multiplexing are collectively called open-loop MIMO; closed-loop transmit diversity and closed-loop spatial multiplexing are collectively called closed-loop MIMO. Similarly, TM2 and TM3 are collectively called open-loop MIMO; TM4 and TM6 are collectively called closed-loop MIMO.

Except for TM1, the preceding transmission modes are also known as MIMO transmission modes. You can select TM2, TM3, TM4, TM6 as a fixed MIMO transmission mode for all UEs served by an eNodeB by setting the CellMimoParaCfg.FixedMimoMode parameter. For details, see 4.5.1 Fixed Configuration of Transmission Modes. You can also allow the eNodeB to adaptively select MIMO transmission modes for UEs based on channel conditions by setting the CellMimoParaCfg.MimoAdaptiveSwitch parameter. For details, see 4.5.2 Adaptive Configuration of Transmission Modes. You can configure TM9 for TM9 UEs (that is, UEs supporting TM9) by selecting the TM9Switch option of the CellAlgoSwitch.EnhMIMOSwitch parameter. You can configure TM2, TM3, or TM4 for non-TM9 UEs by setting the CellMimoParaCfg.FixedMimoMode parameter.

4.2 Transmit Diversity Transmit diversity uses multiple antennas to transmit signals and their copies after encoding based on the low correlation between spatial channels and the characteristics of radio waves in time and frequency domains. These signals and their copies with different fading degrees are then combined at the receiver. This process brings diversity gains and improves transmission reliability. Transmit diversity is classified into open- and closed-loop transmit diversity based on whether the PMIs reported by UEs are used to process transmit signals. In open-loop transmit diversity mode, a predefined PMI is used and the PMIs reported by UEs are not used. In closed-loop transmit diversity mode, the PMIs reported by UEs are used.

4.2.1 Open-Loop Transmit Diversity When CRSs are transmitted over two antenna ports (ports 0 and 1), space frequency block coding (SFBC) is used for encoding in both spatial and time domains. When CRSs are transmitted over four antenna ports (ports 0, 1, 2, and 3), SFBC together with frequency switched transmit diversity (FSTD) is used.

SFBC SFBC applies when CRSs are transmitted over two antenna ports. When SFBC is enabled, coding is performed in both space and time domains. The following figure shows signal processing at the transmitter when SFBC is enabled. Figure 4-2 Signal processing at the transmitter when SFBC is enabled

Issue 04 (2015-08-31)


21



In the previous figure, x1 and x2 indicate the signals to be transmitted before SFBC is used. An asterisk (*) indicates the conjugation of a matrix. f1 and f2 indicate subcarriers. Ports 0 and 1 indicate transmit antenna ports. The eNodeB encodes signals x1 and x2 over different antenna ports and subcarriers, and then: l

Transmits signals x1 and x2 over subcarriers f1 and f2 of port 0, respectively.

l

Transmits signals -x2* and x1* over subcarriers f1 and f2 of port 1, respectively.

By transmitting the copies of signals x1 and x2 over different antenna ports and subcarriers, SFBC brings diversity gains.

SFBC+FSTD SFBC+FSTD applies when CRSs are transmitted over four antenna ports. FSTD is a technique in which some of the antenna ports on the transmitter are selected in a specific frequency order for transmission. The following figure shows the signals to be transmitted when SFBC+FSTD is used. Figure 4-3 Signal processing at the transmitter when SFBC+FSTD is enabled

The variables in the previous figure are described as follows: l

x1 to x4: data transmitted before encoding

l

f1 to f4: subcarriers

l

Port 0 to port 3: antenna ports for transmission

l

Asterisk (*): conjugation of a matrix

l

0: no transmission

In SFBC+FSTD mode, the eNodeB encodes signals x1 to x4 on different antennas and subcarriers, and then: l


l


l


l


By transmitting the copies of signals x1 to x4 over different antenna ports and subcarriers, SFBC+FSTD brings diversity gains. Issue 04 (2015-08-31)


22



4.2.2 Closed-Loop Transmit Diversity As a special closed-loop spatial multiplexing, closed-loop transmit diversity processes only one data block. It maps one codeword to one layer and uses zero-delay CDD for precoding. For details, see 4.3.3 Closed-Loop Spatial Multiplexing.

4.3 Spatial Multiplexing Spatial multiplexing is a technique in which multiple data blocks are transmitted using the same time-frequency resource. In spatial multiplexing mode, the number of spatial channels is greater than that in single-antenna mode, thereby increasing system capacity and bringing multiplexing gains. Spatial multiplexing is classified into open-loop spatial multiplexing and closed-loop spatial multiplexing based on whether the PMIs reported by UEs are used. In open-loop spatial multiplexing mode, a predefined PMI is used and the PMIs reported by UEs are not used. In closed-loop spatial multiplexing mode, the PMIs reported by UEs are used.

4.3.1 Principles of Spatial Multiplexing Figure 4-4 illustrates the principles of spatial multiplexing. Figure 4-4 Principles of spatial multiplexing

The variables in the previous figure are described as follows: l

s: transmit data mapped onto different layers

l

x: precoded transmit data

l

y: receive data

l

H: channel matrix

For details about layer mapping and precoding, see Layer Mapping and Precoding. For 3GPP specifications, see sections 6.3.3 "Layer mapping" and 6.3.4 "Precoding" in 3GPP TS 36.211 V10.5.0.

Layer Mapping Layer mapping is a process in which the eNodeB maps codewords onto multiple layers. In this process, the mapping between codewords and data blocks is established. Issue 04 (2015-08-31)


23



Based on the number of transmit and receive antennas, spatial multiplexing allows one or two codewords to be simultaneously transmitted on one to four layers for macro eNodeBs, one or two layers for micro eNodeBs. The following table lists the mapping between codewords and layers in spatial multiplexing. Table 4-3 Mapping between codewords and layers Number of Codewords

Number of Layers

Codeword-to-Layer Mapping

eNodeB Type

1

1

Codeword 1 to Layer 1

Macro or micro eNodeBs

1

2

Codeword 1 to Layers 1 and 2

Macro eNodeBs

2

2

Codeword 1 to Layer 1


Codeword 2 to Layer 2 2

3

Codeword 1 to Layer 1 Codeword 2 to Layers 2 and 3

2

4

Codeword 1 to Layers 1 and 2 Codeword 2 to Layers 3 and 4

Macro or micro eNodeBs Macro or micro eNodeBs

NOTE

For macro eNodeBs, codeword 1 is mapped onto layer 2 only when four antenna ports are used to transmit CRSs.

If two antenna ports for transmitting CRSs and two UE receive antennas are used, one or two layers can be adopted for open-loop spatial multiplexing and CRS-based closed-loop spatial multiplexing. In most cases: l

If two antenna ports for transmitting CRSs and two UE receive antennas are used, one or two layers can be adopted for open-loop spatial multiplexing and CRS-based closed-loop spatial multiplexing.

l

If four antenna ports for transmitting CRSs and four UE receive antennas are used, one to four layers can be adopted for open-loop spatial multiplexing and CRS-based closedloop spatial multiplexing.

l

If four antenna ports for transmitting CRSs and two UE receive antennas are used, one or two layers can be adopted for open-loop spatial multiplexing and CRS-based closed-loop spatial multiplexing.

The number of layers indicates the gain of spatial multiplexing. In case of low SINR, few layers, even only one layer, can be selected by the eNodeB. In case of high SINR or scattering propagation, a large number of layers can be selected by the eNodeB. To determine the number of layers to be scheduled in the downlink in spatial multiplexing mode, the eNodeB requests the UE to report its rank capability.

Issue 04 (2015-08-31)


24



Precoding Precoding is a process in which an eNodeB precodes layered data block and maps the precoded data block to different antenna ports. Figure 4-5 shows the layer mapping and precoding when two antenna ports are used. Figure 4-6 shows the layer mapping and precoding when four antenna ports are used. Figure 4-5 Layer mapping and precoding when two antenna ports are used

Figure 4-6 Layer mapping and precoding when four antenna ports are used

Issue 04 (2015-08-31)


25



Precoding matrices are determined as follows: l

In open-loop spatial multiplexing mode, the eNodeB selects precoding matrices according to section 6.3.4.2.2 in 3GPP TS 36.211 V10.5.0.

l

In closed-loop spatial multiplexing mode, the eNodeB uses the precoding matrices based on the PMIs reported by the UE.

4.3.2 Open-Loop Spatial Multiplexing Open-loop spatial multiplexing brings spatial multiplexing gains. It also brings diversity gains due to its use of large-delay CDD precoding. Diversity gains are brought when the copies of the same signal are transmitted using different antennas with different delays. Open-loop spatial multiplexing precoding is implemented based on the following formula: x = WDUs The variables in the previous formula are described as follows: l


l


l

W: precoding matrix. Its value is derived from the codebook subset, and encoding is performed based on the predefined codebook and encoding rule.

l

D: diagonal matrix. The diagonal element indicates the delay.

l

U: matrix used to mix data block at different layers and then send them to different transmit antennas. Together with matrix D, matrix U brings diversity gains and reduces the channel quality difference between two layers at the receiver.

The eNodeB currently supports a maximum of four layers in open-loop spatial multiplexing. For details about codebook subsets, see section 6.3.4.2.3 "Codebook for precoding and CSI reporting" in 3GPP TS 36.211 V10.5.0.

4.3.3 Closed-Loop Spatial Multiplexing In closed-loop spatial multiplexing mode, the eNodeB adopts zero-delay CDD precoding using the following formula: x = Ws The variables in the previous formula are described as follows: l


l


l

W: precoding matrix obtained by the eNodeB from the codebook set based on the PMI reported by the UE

Each receive antenna of the UE receives signals from different transmit antennas of the eNodeB, leading to cross-channel interference and deterioration in receive signal quality. To minimize cross-channel interference, a signal processing technique can be adopted at the transmitter with known channel conditions. Assuming that channel H is known, singular value decomposition (SVD) is applied to channel H based on the following formula: H=UDVH Issue 04 (2015-08-31)


26



where l

D: diagonal matrix. The diagonal element is the singular value of matrix H.

l

U and VH: unitary matrices.

If matrix V is used for precoding, the following formula applies: y = UDVHWs+n = UDVHVs+n = UDs+n The variables in the previous formula are described as follows: l

n: noise.

l

y: receive data

At the receiver, signal y is multiplied by UH and the following formula applies: r = UHy = UHUDs + UHn = Ds + UHn Then, signals are transmitted in parallel without interfering with each other. Therefore, precoding matrix W equals matrix V. In LTE systems, the eNodeB selects the precoding matrix for closed-loop spatial multiplexing based on the PMI reported by the UE. In actual application, the precoding matrix adopted by the eNodeB cannot equal matrix V due to quantizing errors. In addition, UE feedback delays and errors deteriorate the precoding performance, especially for high-speed UEs. Therefore, closed-loop spatial multiplexing is more suitable for stationary and low-speed UEs. For details about codebook subsets, see section 6.3.4.2.3 in 3GPP TS 36.211 V10.5.0.

4.4 TM9 Transmission Mode 3GPP Release 10 introduces TM9 into LTE. TM9 supports SU-MIMO with a maximum of eight layers and MU-MIMO with a maximum of four data blocks (at most two layers for each UE). In addition, 3GPP Release 10 introduces UE-specific downlink demodulation reference signals (DMRSs) and channel state information reference signals (CSI-RSs) for CSI measurement. 3GPP Release 9 supports a maximum of four layers and uses CRSs for CSI measurement. By contrast, 3GPP Release 10 adds layers and uses CSI-RSs to reduce the overhead of CSI measurement in high-order MIMO scenarios.

4.4.1 Technical Principles In TM4, demodulation is based on common reference signals CRSs, which requires that the physical downlink shared channel (PDSCH) and common channels use the same number of antenna ports. In TM9, by contrast, dedicated reference signals CSI-RSs and DMRSs are added. In TM9, PMI feedback is based on CSI-RSs, demodulation is based on UE-specific DMRSs, and the PDSCH and common channels can use different numbers of antenna ports.

Issue 04 (2015-08-31)

Item

TM4

TM9

Precoding

Based on PMIs

Based on PMIs

Rank indication (RI), PMI, and CQI feedback

Based on CRSs

Based on CSI-RSs


27



Item

TM4

TM9

Demodulation

Based on CRSs

Based on DMRSs

In TM4, l

UEs supporting 4-port CRSs (that is, CRSs transmitted using four antenna ports) support spatial multiplexing with a maximum of four layers.

l

UEs supporting only 2-port CRSs support spatial multiplexing with a maximum of two layers.

l

UEs supporting only 2-port CRSs cannot access a 4-port-CRS network.

l

If some UEs support 4-port CRSs but some UEs support only 2-port CRSs, the eNodeB cannot be configured with 4-port CRSs. In this case, the eNodeB can be configured with only 2-port CRSs and the performance deteriorates because of the limitation of the codebook size.

In TM9, l

The eNodeB selects the most appropriate precoding matrix from the predefined codebook, which is saved on both the eNodeB and the UE.

l

The UE estimates the channel quality based on CSI-RSs, selects the most appropriate precoding matrix on this occasion, and sends the PMI to the eNodeB.

l

The eNodeB performs data precoding and sends the result to the UE.

3GPP Release 9 supports a maximum of four layers and uses CSI-RSs for CSI measurement. By contrast, 3GPP Release 10 reduces the overhead of CSI measurements in high-order MIMO scenarios by adding layers and designing CSI-RSs. In 3GPP Release 10, CSI measurement in TM9 is based on CSI-RSs, and data demodulation is based on DMRSs. CSI-RSs consume a very small number of time and frequency resources (1 RE per port per PRB) because CSI-RSs are multiplexed by using orthogonal series on different antenna ports and the precision requirement on CSI measurement is lower than that on data demodulation. TM9 is commonly used in low-speed movement scenarios, and therefore the CSI-RS reporting period can be set within the range of [5 ms, 10 ms, 20 ms, 40 ms, 80 ms].

DMRS PDSCH demodulation is based on DMRSs, and DMRSs themselves have been precoded. This way, the flexibility in downlink precoding greatly increases, and the physical downlink control channel (PDCCH) signaling overhead decreases because no PMIs are required for transmission. For UE-specific DMRS configuration, the antenna ports for DMRSs at layers 1 to 8 are numbered 7 to 14 respectively and the number of antenna ports can be 1, 2, 4, or 8. For the REs used for DMRSs, see section 6.10.3.2 "Mapping to resource elements" in 3GPP TS 36.211 V10.5.0. Specifically, l

Issue 04 (2015-08-31)

The mapping of DMRSs to REs is the same for antenna ports 7 and 8; it is also the case for antenna ports 9 and 10. In such cases, DMRSs are multiplexed by using 2dimensional orthogonal series on different antenna ports to implement code-division multiplexing (CDM). Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

28



l

Ranks 1 and 2 occupy 12 resource elements (REs) in a resource block (RB) because the mapping of DMRSs to REs is the same for the 2 ranks. Ranks 3 and 4 occupy 24 REs in an RB.

l

If eight antenna ports are used, the mapping of DMRSs to REs is the same for antenna ports 7, 8, 11, and 12; it is also the case for antenna ports 9, 10, 13, and 14. In such cases, DMRSs are multiplexed by using 4-dimensional orthogonal series on different antenna ports to implement CDM.

In TM9, downlink precoding is relatively flexible; it can use codebooks not defined by 3GPP. To ensure the reliability of channel estimation based on DMRSs reported by UEs, the downlink precoding granularity must be limited. 3GPP defines physical resource groups (PRGs) with different granularity for different bandwidths, as listed in Table 4-4. The PMI reporting granularity is always integral multiples of a PRG, regardless of wideband or subband PMIs. Therefore, if PMIs reported by UEs are used for downlink precoding, the requirement on PRGs is fulfilled. Table 4-4 PRG granularity in different bandwidths System Bandwidth (

) (Unit: RB)

PRG Size (

≤ 10

1

11–26

2

27–63

3

64–100

2

) (Unit: PRB)

Power allocation for DMRSs is also defined by 3GPP. For details, see section 5.2 "Downlink power allocation" in 3GPP TS 36.213 V10.5.0. When the rank is equal to 1 or 2, the mapping of DMRSs to REs is the same for the 2 ranks and the ratio of PDSCH RE power to DMRS RE power is equal to 1 (that is, 0 dB). For rank > 2, some DMRS RE resources need to be reserved for other antenna ports and the ratio of PDSCH RE power to DMRS RE power is equal to 1:2 (that is, -3 dB). Figure 4-7 shows the mapping of layers to antenna ports for DMRSs. The downlink control information (DCI) 2C format used by TM9 does not contain a Transport Block to Codeword Swap Flag. Therefore, TB1 can be mapped only to codeword 0 and TB2 can be mapped only to codeword 1.

Issue 04 (2015-08-31)


29



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

CSI-RS CSI-RSs are introduced only for CSI measurement in TM9. 3GPP Release 9 supports a maximum of four layers and uses CRSs for CSI measurement. By contrast, 3GPP Release 10 reduces the overhead of CSI measurement in high-order MIMO scenarios by adding layers and designing CSI-RSs. The eNodeB configures UE-specific CSI-RSs by using the same or different CSI-RS templates for different UEs. A Release 10 UE can have 0 or 1 CSI-RS with non-zero transmit power, or the UE can have 0 to 16 CSI-RSs with zero transmit power. The UE does not consider the subcarriers occupied by CSI-RSs during decoding for MIMO, regardless of whether CSI-RSs are configured with zero or non-zero transmit power. For a Release 8 or 9 UE not supporting CSI-RSs, the UE cannot perceive the transmission of CSI-RSs and therefore the scheduling performance deteriorates if the UE is scheduled in subframes configured with CSI-RSs. If PMI/RI reporting is configured, TM9 UEs report CQIs based on CSI-RSs. If PMI/RI reporting is not configured, TM9 UEs report CQIs based on CRSs. In certain subframes, the UE considers the eNodeB to have not transmitted CSI RSs. These subframes are: l

Subframes where CSI-RSs conflict with the primary or secondary synchronization channel, broadcast channel, or SIB1

l

Subframes configured with paging messages

For the REs used for CSI-RSs, see section 6.10.5.2 "Mapping to resource elements" in 3GPP TS 36.211 V10.5.0. Specifically, l

Issue 04 (2015-08-31)

The mapping of CSI-RSs to REs is the same for antenna ports 15 and 16; this is also the case for antenna ports 17 and 18, 19 and 20, as well as 21 and 22. In such cases, CSI-RSs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

30



are multiplexed by using 2-dimensional orthogonal series on different antenna ports to implement CDM. l

8 antenna ports occupy only 8 REs. This greatly reduces resource overhead.

The following CSI-RS information needs to be configured by using higher-layer signaling: l

Number of CSI-RS ports (that is, CSI-RS ports): 1, 2, 4, or 8.

l

CSI-RS configuration: For details, see Table 6.10.5.2 in 3GPP TS 36.211 V10.5.0.

l

: CSI-RS subframe configuration. For details, see Table 4-5.

l

: CSI-RS reporting period. For details, see Table 4-5.

l

ΔCSI-RS: CSI-RS subframe offset. For details, see Table 4-5.

l

: CSI-RS power configuration, indicating the ratio of PDSCH RE power to CSI-RS RE power. The unit is dB, the value range is from -8 to +15, and the step is 1 dB

Table 4-5 CSI-RS configuration information (Unit: Subframe) 0–4

5

5–14

10

15–34

20

35–74

40

75–154

80

ΔCSI-RS (Unit: Subframe)

CSI Reporting In TM9, the higher layer uses the pmi-RI-Report parameter to indicate whether the UE needs to report PMIs or RIs. If the UE is configured to report PMIs or RIs and if more than one CSIRS antenna port is configured with none-zero transmit power, the UE uses CSI-RSs for serving cell measurements; otherwise, the UE uses CRSs for serving cell measurement measurements. The eNodeB can configure 1, 2, or 4 CRS ports, which occupy port 0, ports 0 and 1, or ports 0 to 3, respectively. The eNodeB can configure 1, 2, 4, or 8 CSI-RS antenna ports, which occupy port 15, ports 15 and 16, ports 15 to 18, or ports 15 to 22. Obviously, the number of CRS ports may be different from the number of CSI-RS antenna ports. Aperiodic CSI reporting modes on the physical uplink shared channel (PUSCH) in TM9 are defined in section 7.2.1 "Aperiodic CQI/PMI/RI Reporting using PUSCH" in 3GPP TS 36.213 V10.5.0. The following briefly describes these modes: Issue 04 (2015-08-31)


31



l

Mode 1-2, 2-2, or 3-1 is used if the UE is configured to report PMIs or RIs and if more than one CSI-RS antenna port is configured.

l

Mode 2-0 or 3-0 is used if the UE is not configured to report PMIs or RIs, or if the UE is configured to report PMIs or RIs but only one CSI-RS antenna port is configured.

Periodic CSI reporting modes on the PUCCH and PUSCH in TM9 are defined in section 7.2.2 "Periodic CQI/PMI/RI Reporting using PUCCH" in 3GPP TS 36.213 V10.5.0. The following briefly describes these modes: l

Mode 1-1 or 2-1 is used if the UE is configured to report PMIs or RIs and if more than one CSI-RS antenna port is configured. If eight CSI-RS antenna ports are configured, two PMIs are required to indicate two precoding matrixes.

l

Mode 1-0 or 2-0 is used if the UE is not configured to report PMIs or RIs, or if the UE is configured to report PMIs or RIs but only one CSI-RS antenna port is configured.

4.4.2 Technical Value The technical value of TM9 is as follows: l

Improving UE Compatibility

l

Improving Performance

Improving UE Compatibility According to 3GPP specifications for LTE, all UEs should be able to work with the eNodeB that uses two or four antenna ports for transmission. UEs detect the number of transmit antenna ports of the eNodeB based on blind detection on the PBCH. However, interoperability testing (IOT) is not performed on most UEs for downlink 4x2 MIMO during the initial commercial use of LTE. As a result, some UEs cannot well support a 4T network (where eNodeBs use four antenna ports for transmission), as illustrated below: l

A very few UEs cannot access the network.

l

The peak-hour performance of some UEs deteriorates greatly, by more than 30%.

l

The far-end performance of some UEs is not satisfactory, and the service drop rate is high.

Figure 4-8 Improving some inventory UEs' compatibility with 4T in TM9

Issue 04 (2015-08-31)


32



For compatibility in a 4T network, one solution is to replace inventory UEs and the other solution is to use TM9. If TM9 is used, all Release 8 or 9 UEs can work in 2x2 MIMO, where two antenna ports are configured for cell-specific CRSs; Release 10 TM9 UEs can work in 4x2 MIMO, where four antenna ports are configured for UE-specific CSI-RSs. In this case, virtual antenna mapping (VAM) can be used to map CRSs from two antenna ports to four physical antennas. There are two VAM solutions for a 4T network, namely 4T2P (four physical antennas and two CRS ports) and 4T1P (four physical antennas and one CRS port), as shown in the following table, Figure 4-9, and Figure 4-10. CRS Port Transmit Sequence on Physical Antennas +45º, -45º, +45º, and -45º

Parameter Setting of Cell.CrsPortMap

(0, 0, 1, 1)

4T2P_0011

(0, 0, 0, 0)

4T1P_0000

Figure 4-9 4T2P VAM solution


For a 2T network, there is only one VAM solution, namely 2T1P, as shown in the following table and Figure 4-11.

Issue 04 (2015-08-31)

CRS Port Transmit Sequence on Physical Antennas +45º, -45º, +45º, and -45º

Parameter Setting of Cell.CrsPortMap

(0, 0)

2T1P_00


33




Compared with the VAM solution for 2T2P, the VAM solution for 4T2P is recommended, with the CRS port transmit sequence of (0, 0, 1, 1). The following table lists the gains provided by this solution. 4T2P (0, 0, 1, 1) vs 2T2P

Average Cell Throughput Gain

Cell-Edge Throughput Gain

TM3

-4% to -6%

6% to 8%

TM4

4% to 6%

14% to 16%

According to section 6.4 "Physical downlink shared channel" in 3GPP TS36.211 V11.5.0, if UEs comply with Release 8 or 9 or if UEs comply with Release 10 but the UEs are not configured with CSI-RSs, the PDSCH is not mapped to REs used for UE-specific CSI-RSs. As a result, the SINR of these UEs decreases and the performance in CSI-RS subframes deteriorates greatly. If no processing is performed, the performance and fairness of these UEs cannot be ensured. The current solution is that such UEs are not scheduled in CSI-RS subframes. However, the peak rate, average cell throughput, and cell-edge throughput decrease in this solution. The decrease degree is related to the CSI-RS reporting period. For example, if the period is 5 ms, the maximum decrease degree is about 20%. However, if the penetration rate of TM9 UEs is high (for example, higher than 20%) and the ratio of these UEs' traffic volume is also high (for example, higher than the penetration rate of these UEs), the average cell throughput and cell-edge throughput hardly decrease. Downlink 4x2 MIMO in TM9 can improve the compatibility of Release 8 or 9 UEs in a 4port CRS network. Being configured with 2-port (even 1-port) CRSs, Release 8 or 9 UEs can work in 2x2 MIMO (even SIMO) mode, which prevents some of these UEs from being unable to access the network or prevents the throughput from decreasing obviously after access to the 4-port CRS network. Being configured with 4-port CSI-RSs, Release 10 TM9 UEs can work in downlink 4x2 MIMO in TM9 and achieve higher gains than in 2x2 MIMO in TM3 or TM4.

Improving Performance In TM9, channel estimation for user data is based on UE-specific DMRSs, and DMRS and PDSCH are precoded simultaneously. Therefore, data demodulation and channel estimation are always matched. If cells each are served by multiple radio frequency (RF) modules, CRSs are transmitted by multiple RF modules or cells while the PDSCH is transmitted by only one RF module or cell. Issue 04 (2015-08-31)


34



In this scenario, the single frequency network (SFN) feature can be deployed to match channel estimation and data demodulation and to increase the average cell throughput and cell-edge throughput in the downlink.

4.5 Working Mode Fixed Configuration of Transmission Modes If fixed configuration of transmission modes is enabled for a cell, the eNodeB configures one transmission mode for all UEs in the cell. Generally, fixed configuration of transmission modes is used for performance testing before multiple-antenna transmission is put into commercial use.

Adaptive Configuration of Transmission Modes If adaptive configuration of transmission modes is enabled for a cell, the eNodeB configures different transmission modes for different UEs in the cell. To adapt to complex and diverse radio channel conditions, it is recommended that adaptive configuration of transmission modes be enabled for multiple-antenna transmission. For example: l

For a UE with a high SINR and low channel correlation, spatial multiplexing brings higher throughput gains than transmit diversity.

l

For a UE with a low SINR, spatial multiplexing brings lower throughput gains than transmit diversity.

l

For a stationary UE or a UE moving at low speed, closed-loop transmit diversity or spatial multiplexing brings higher performance gains than open-loop transmit diversity or spatial multiplexing.

l

For a UE moving at high speed, closed-loop transmission mode may bring no or even negative performance gains and increase system feedback overheads compared with open-loop transmission mode.

4.5.1 Fixed Configuration of Transmission Modes The eNodeB can select one of the following modes for UEs as a fixed MIMO transmission mode: l

TM2

l

TM3

l

TM4 (not recommended)

l

TM6 (not recommended)

The CellMimoParaCfg.FixedMimoMode parameter can be used to configure one of the preceding transmission modes only when the CellMimoParaCfg.MimoAdaptiveSwitch parameter has been set to NO_ADAPTIVE(NO_ADAPTIVE).

Issue 04 (2015-08-31)


35



NOTE

If fixed configuration of transmission modes is enabled: l When the CellMimoParaCfg.InitialMimoType parameter is set to TM2(TM2), the eNodeB selects TM2 for a UE when the UE accesses a cell. l When the CellMimoParaCfg.InitialMimoType parameter is set to ADAPTIVE(ADAPTIVE), the eNodeB selects the transmission mode specified by the CellMimoParaCfg.FixedMimoMode for a UE when the UE accesses a cell.

In downlink 4x4 MIMO, two or more data blocks can be transmitted only when the CellDlschAlgo.MaxMimoRankPara parameter is set to SW_MAX_SM_RANK_4(Rank4). The application scenarios of the transmission modes are as follows: l

TM2 UEs are moving at high speed and their SINRs are low.

l

TM3 UEs are moving at high speed and their SINRs are high.

l

TM4 UEs are stationary or moving at low speed and their SINRs are high.

l

TM6 UEs are stationary or moving at low speed and their SINRs are low.

For TM4 and TM6, the following factors need to be considered: the timeliness and reliability of PMIs provided by UEs and the impact of demodulation performance brought by UEs in closed-loop transmission mode. If the PMI is unreliable or the demodulation performance is unstable, TM4 and TM6 do not improve system performance compared with TM2 and TM3. They may even cause it to deteriorate. If some UEs are discovered as incompatible UEs in TM4 or TM6 and the eNodeB is configured to provide a workaround, the eNodeB applies the adaptive open-loop transmission mode to these UEs. For details, see Terminal Awareness Differentiation Feature Parameter Description.

4.5.2 Adaptive Configuration of Transmission Modes The following table lists the typical application scenarios of MIMO techniques. Table 4-6 Typical application scenarios of MIMO techniques

Issue 04 (2015-08-31)

MIMO Technique

Description

Open-Loop Transmit Diversity

UEs with low SINRs are moving at high speed.

Open-Loop Spatial Multiplexing

UEs with high SINRs are moving at high speed.

Closed-Loop Transmit Diversity

UEs with low SINRs are moving at low speed.

Closed-Loop Spatial Multiplexing

UEs with high SINRs are moving at low speed.


36



NOTE

l The performance of closed-loop transmit diversity and spatial multiplexing is subject to both the timeliness and reliability of PMIs reported by UEs. Either mode may bring no satisfactory gains if the PMIs are not reported timely or are not reliable. l The performance of closed-loop MIMO is subject to both movement speed and channel correlation. Generally, the higher the channel correlation, the more robust the closed-loop transmit diversity and spatial multiplexing techniques are to mobility.

To adapt to complex and diverse radio channel conditions, the eNodeB can adaptively configure different transmission modes for different UEs in a cell. The eNodeB supports the following types of adaptive configuration: l

Adaptive configuration of open-loop transmission modes

l

Adaptive configuration of closed-loop transmission modes

l

Adaptive configuration of open- and closed-loop transmission modes

The CellMimoParaCfg.MimoAdaptiveSwitch parameter specifies whether to enable the preceding types of adaptive configuration. NOTE

If adaptive configuration of transmission modes is enabled, the eNodeB selects a transmission mode for a UE based on the CellMimoParaCfg.InitialMimoType parameter when the UE accesses a cell: l If this parameter is set to TM2(TM2), the eNodeB selects TM2. l If it is set to ADAPTIVE(ADAPTIVE), the eNodeB selects a transmission mode based on the CellMimoParaCfg.MimoAdaptiveSwitch parameter. If this parameter is set to OL_ADAPTIVE(OL_ADAPTIVE), the eNodeB selects TM3. If this parameter is set to CL_ADAPTIVE(CL_ADAPTIVE), the eNodeB selects TM4.

All the preceding types of adaptive configuration can be selected for downlink 2x2 or 4x2 MIMO. NOTE

If the transmission mode of a cell rolls back to 4T2R and the value of the CellMimoParaCfg.MimoAdaptiveSwitch parameter is OC_ADAPTIVE(OC_ADAPTIVE), the value of this parameter must be manually changed to OL_ADAPTIVE(OL_ADAPTIVE) or CL_ADAPTIVE(CL_ADAPTIVE). For details about rollback to 4T2R, see Cell Management Feature Parameter Description.

In downlink 4x4 MIMO, two or more data blocks can be transmitted only when the CellDlschAlgo.MaxMimoRankPara parameter is set to SW_MAX_SM_RANK_4(Rank4). The application scenarios of adaptive configuration of transmission modes are as follows: l

Adaptive configuration of open-loop transmission modes This adaptive configuration does not require UEs to report PMIs and therefore it applies when most UEs in a cell are moving at high speed. The eNodeB adaptively configures open-loop transmit diversity or open-loop spatial multiplexing for data transmission based on radio channel conditions.

l

Adaptive configuration of closed-loop transmission modes This adaptive configuration requires UEs to report PMIs and therefore it applies when most UEs in a cell are moving at low speed, PMIs reported by UEs are reliable, and demodulation performance in closed-loop modes is satisfactory. The eNodeB adaptively configures closed-loop transmit diversity or spatial multiplexing for data transmission based on radio channel conditions. If most PMIs reported by UEs are unreliable or demodulation performance is unsatisfactory, closed-loop transmission modes bring no or

Issue 04 (2015-08-31)


37



even negative performance gains when compared with open-loop transmission modes. In this situation, the eNodeB needs to switch back to adaptive configuration of open-loop transmission modes. l

Adaptive configuration of open- and closed-loop transmission modes This adaptive configuration applies when most UEs in a cell are moving at different speeds, the PMIs reported by UEs in closed-loop mode are highly reliable, and demodulation performance is satisfactory. The eNodeB first configures a transmission mode as the initial transmission mode when the UE accesses the cell, and then adaptively configures an open- or closed-loop transmission mode based on radio channel conditions.

Some UE models may not support closed-loop MIMO techniques. Therefore, adaptive configuration of open-loop transmission modes is recommended for commercial use. Adaptive configuration of closed-loop transmission modes can be used to increase performance if most UEs are moving at low speed, PMIs reported by UEs are reliable, and demodulation performance is satisfactory in closed-loop transmission mode. There is little difference between open-loop and closed-loop 2x2 MIMO. Adaptive configuration of open- and closed-loop transmission modes is not suitable to all application scenarios. For example, if a closed-loop transmission mode brings little gains compared with an open-loop transmission mode and the open-loop transmission mode is selected, adaptive configuration of open- and closed-loop transmission modes may bring losses compared with adaptive configuration of open-loop transmission modes. Therefore, adaptive configuration of open- and closed-loop transmission modes is not recommended. When adaptive configuration of closed-loop transmission modes is enabled and some UEs are discovered as incompatible UEs, the eNodeB can adaptively configure an open-loop transmission mode for these UEs. For details, see Terminal Awareness Differentiation Feature Parameter Description.

4.5.3 TM9 Configuration TM9 UEs can be configured to work in TM9 and non-TM9 UEs can be configured to work in TM2, TM3, TM4, or TM6 only when the CellAlgoSwitch.EnhMIMOSwitch parameter is set to TM9Switch-1. Downlink 2x2 MIMO, downlink 4x2 MIMO, and downlink 4x4 MIMO support the configuration of TM9. TM9 is recommended when the following conditions are met: l

The penetration rate of TM9 UEs is high (for example, higher than 20%).

l

UEs are moving at low speed (lower than 30 km/h) or are stationary.

DMRSs and CSI-RSs are added to 2x2 MIMO in TM9. As a result, the performance in TM9 is worse than the performance in TM3 and TM4. If UEs are moving faster than 30 km/h, the loss in network key performance indicators (KPIs) is especially obvious. It is recommended that downlink 2x2 MIMO in TM9 be deployed together with LOFD-070205 Adaptive SFN/ SDMA.

4.6 Optimization of Combined RRUs If remote radio units (RRUs) are combined to serve a cell, CRS port mapping can increase the cell throughput. Issue 04 (2015-08-31)


38



NOTE

l This document uses RRUs as an example to describe MIMO. If only two ports are required in MIMO, radio frequency units (RFUs) can also be used. l An integrated RRU refers to an RRU that provides multiple transmit and receive channels. Combined RRUs refer to two RRUs that together provide multiple transmit and receive channels. l This document assumes that combined RRUs are connected through common public radio interfaces (CPRIs) in star topology. In addition, combined RRU can be connected in chain topology. For details, see RF Unit and Topology Management Feature Parameter Description.

4.6.1 CRS Port Mapping To avoid the adjustment of feeder connections after RRU channels are connected to physical antennas, CRS port mapping is introduced to map CRS ports to RRU channels and further to physical antennas. Here, RRU channels refer to transmit channels in RRUs, and CRS ports refer to antenna ports (logical ports) for transmitting CRSs. The polarization directions and spacing of physical antennas have impact on the performance of downlink 4x2 MIMO and downlink 4x4 MIMO. As shown in Figure 4-12, physical antennas with the same polarization direction have high channel correlation, and a smaller spacing leads to even higher correlation. Physical antennas with different polarization directions have low channel correlation, but a larger spacing leads to even lower correlation. Figure 4-12 Correlation between antennas with four ports

In the SFBC+FSTD matrix shown in Figure 4-3, antenna ports 0 and 2 are used to transmit an SFBC group, and antenna ports 1 and 3 are used to transmit another SFBC group. To achieve higher diversity gains using dual-polarized antennas, connect antenna ports 0 and 2 to physical antennas installed in different polarization directions and connect antennas 1 and 3 to physical antennas installed in different polarization directions. Open-loop spatial multiplexing and closed-loop spatial multiplexing each have their own requirements for CRS port mapping. It is recommended that CRS ports 0, 2, 1, and 3 or CRS ports 0, 2, 3, and 1 be mapped to physical antennas +45º, -45º, +45º, and -45º. The mapping of CRS ports to physical antennas is determined by the RRU channel sequence and the feeder connection mode. For example, the RRU channel sequence of an integrated RRU of Huawei is (A, C, D, B), and the RRU channel sequence of combined RRUs are (A, B, A, B), as shown in Figure 9-13 and Figure 9-15, respectively. Issue 04 (2015-08-31)


39



To facilitate engineering, it is recommended that RRU channels and physical antennas be connected in non-cross-connection mode, as shown in the topologies for 4T4R cells in 9.4.4 Hardware Adjustment. In this case, CRS ports 0, 2, 3, and 1 of the integrated RRU are respectively mapped to physical antennas +45º, -45º, +45º, and -45º by default. CRS ports 0, 1, 2, and 3 of the combined RRUs are respectively mapped to physical antennas +45º, -45º, +45º, and -45º by default. The mapping of CRS ports to RRU channels is specified by the Cell.CrsPortMap parameter. CRS port mapping applies to the following scenario: l

The cell is a 4T4R cell.

l

The baseband processing unit (BBP) is LBBPd or UBBPd.

l

The Cell.MultiRruCellFlag parameter is set to BOOLEAN_FALSE.

l

The 4T4R cell uses 4T2P to implement 2x2 MIMO. In this scenario, 4T2P_0011 is recommended.

The integrated RRU and combined RRUs have different RRU channel layouts. To ensure a consistent CRS port transmit sequence, the Cell.CrsPortMap parameter values are also different, as listed in the following table. CRS Port Transmit Sequence on Physical Antennas +45º, -45º, +45º, and -45º

Value of Cell.CrsPortMap for Combined RRUs

Value of Cell.CrsPortMap for an Integrated RRU

0, 2, 1, 3

4T4P_0213

4T4P_0321

0, 2, 3, 1

4T4P_0231

4T4P_0123

0, 1, 2, 3

4T4P_0123

4T4P_0312

0, 1, 3, 2

4T4P_0132

4T4P_0213

0, 1, 1, 0

4T2P_0110

4T2P_0110

0, 1, 0, 1

4T2P_0101

4T2P_0101

0, 0, 1, 1

4T2P_0011

4T2P_0011

NOTE

l mTnP in the preceding table indicates that the cell has m transmit channels and n CRS ports. 4TnP_abcd indicates that CRS ports a, b, c, and d are mapped to RRU channels 1, 2, 3, and 4. If the Cell.CrsPortMap parameter is set to NOT_CFG, CRS porting mapping is disabled, indicating 4T4P_0123 in 4T4P scenarios. l If m is equal to n, the number of CRS ports is the same as the number of transmit channels. a, b, c, and d must be different. l Typically, RRU channels 1, 2, 3, and 4 of an integrated RRU correspond to R0A, R0B, R0C, and R0D. RRU channels 1,2, 3, and 4 of combined RRUs correspond to one RRU's R0A and R0B and the other RRU's R0A and R0B.

4.7 Configuration for CSI Reporting Issue 04 (2015-08-31)


40



4.7.1 Introduction to CSI Reporting Modes The channel state information (CSI) that a UE reports to the eNodeB includes a channel quality indicator (CQI), a precoding matrix indicator (PMI), and a rank indication (RI). The information is used to support downlink user plane scheduling and downlink MIMO. Table 4-7 lists five aperiodic CSI reporting modes and Table 4-8 lists four periodic CSI reporting modes. These reporting modes are defined in section 7.2 "UE procedure for reporting Channel State Information (CSI)" in 3GPP TS 36.213 V10.5.0. Table 4-7 Aperiodic CSI reporting modes PUSCH CQI Feedback Type

PMI Feedback Type (No PMI)

PMI Feedback Type (Single PMI)

PMI Feedback Type (Multiple PMIs)

Wideband CQI

-

-

Mode 1-2

UE-selected sub-band CQI

Mode 2-0

-

Mode 2-2

Upper-layer-configured sub-band CQI

Mode 3-0

Mode 3-1

-

Table 4-8 Periodic CSI reporting modes PUCCH CQI Feedback Type

PMI Feedback Type (No PMI)

PMI Feedback Type (Single PMI)

Wideband CQI

Mode 1-0

Mode 1-1

UE-selected sub-band CQI

Mode 2-0

Mode 2-1

Table 4-9 lists the configurable CSI reporting modes in different transmission modes. Table 4-9 Configurable CSI reporting modes in different transmission modes

Issue 04 (2015-08-31)

Transmission Mode

Aperiodic CSI Reporting Mode

Periodic CSI Reporting Mode

TM1

2-0 and 3-0

1-0 and 2-0

TM2

2-0 and 3-0

1-0 and 2-0

TM3

2-0 and 3-0

1-0 and 2-0

TM4

1-2, 2-2, and 3-1

1-1 and 2-1

TM6

1-2, 2-2, and 3-1

1-1 and 2-1

TM9

1-2, 2-2, 3-1, 2-0, and 3-0

1-1, 2-1, 1-0, and 2-0


41



All UEs support the following CSI reporting modes: l

Periodic CSI reporting modes 1-0 and 1-1

l

Aperiodic CSI reporting modes 1-2, 3-0, and 3-1

Only UEs with the corresponding capabilities support the following CSI reporting modes: l

Periodic CSI reporting modes 2-0 and 2-1

l

Aperiodic CSI reporting modes 2-0 and 2-2

CSI reporting is used for link adaptation in the downlink but consumes uplink resources. Therefore, the eNodeB considers both uplink and downlink performance (such as the throughput and number of UEs) before selecting an appropriate reporting mode.

4.7.2 Comparison Between Periodic and Aperiodic CSI Reporting Aperiodic CSI is reported on the PUSCH and scheduled in DCI format 0. The reporting mode is configured in an RRC IE "CQI-ReportConfig". Periodic CSI reporting does not consume PDCCH resource. The reporting period, reporting mode, and required time-frequency resource are configured in the RRC IE "CQIReportConfig". Note that: l

If the UE has no data to transmit at the periodic CSI reporting moment, the CSI is reported on the PUCCH.

l

If the UE has data to transmit at the periodic CSI reporting moment, the CSI is reported on the PUSCH.

Aperiodic CSI reporting provides more comprehensive and real-time channel information than periodic CSI reporting. With more detailed and real-time sub-band information, the downlink scheduler can perform frequency-selective scheduling and obtain diversity gains. However, aperiodic CSI reports contain more bits and therefore consume more uplink resources. Table 4-10 Comparison between periodic CSI reporting and aperiodic CSI reporting

Issue 04 (2015-08-31)

Item

Periodic CSI Reporting

Aperiodic CSI Reporting

Reporting channel

PUCCH or PUSCH, depending on whether the UE has data to transmit at the reporting moment

PUSCH

Trigger

None

Uplink scheduling indicator

PMI feedback type

Single PMI

Single or multiple PMIs

CQI feedback type

l Wideband

l Wideband

l UE-selected best sub-band (coarse sub-band sizes, sent one by one in separate reporting periods)

l UE-selected sub-band (granular sub-band sizes)


l Higher-layer configured subband (one CQI per sub-band, sent in a single subframe) 42



Item

Periodic CSI Reporting

Aperiodic CSI Reporting

RI feedback

Sent in separate subframes from CQI and PMI

Sent together with CQI and PMI

4.7.3 Configuration of CSI Reporting Mode and Period CSI Reporting Mode Configuration The eNodeB adaptively selects a CSI reporting mode based on the MIMO modes in use, as shown in Figure 4-13. Figure 4-13 CSI reporting mode selection during scheduling

l

l

If periodic CSI reporting is selected: –

For open-loop MIMO, mode 1-0 is used.

–

For closed-loop MIMO, mode 1-1 is used.

If aperiodic CSI reporting is selected: –

For open-loop MIMO, mode 3-0 is used.

–

For closed-loop MIMO, mode 3-1 is used.

CSI Reporting Period Configuration Aperiodic CSI reporting is scheduled according to DCI format 0. The shortest trigger period is 1 ms. The periodic CSI reporting period depends on the CellCqiAdaptiveCfg.CqiPeriodAdaptive parameter setting: Issue 04 (2015-08-31)


43


l


If the CellCqiAdaptiveCfg.CqiPeriodAdaptive parameter is set to ON(On): The periodic CSI reporting period is adjusted by the eNodeB based on PUCCH load. If there are only a small number of UEs, the eNodeB selects a short period but not shorter than 5 ms. If the number of UEs increases, the eNodeB gradually increases the period; the longest period is 160 ms.

l

If the CellCqiAdaptiveCfg.CqiPeriodAdaptive parameter is set to OFF(Off): The periodic CSI reporting period is specified by the user-level parameter CellCqiAdaptiveCfg.UserCqiPeriod. The value range is 2 ms, 5 ms, 10 ms, 20 ms, 32 ms, 40 ms, 64 ms, 80 ms, 128 ms, and 160 ms. NOTE

l If the CellCqiAdaptiveCfg.UserCqiPeriod parameter is set to 32 ms, the eNodeB automatically changes the value to 20 ms. l If the CellCqiAdaptiveCfg.UserCqiPeriod parameter is set to 64 ms, the eNodeB automatically changes the value to 40 ms. l If the CellCqiAdaptiveCfg.UserCqiPeriod parameter is set to 128 ms, the eNodeB automatically changes the value to 80 ms.

Aperiodic CSI Reporting Configuration for Handover UEs The overhead of handover signaling affects the handover success rate and handover delay. Aperiodic CSI reporting configuration for handover is controlled by the CellCqiAdaptiveCfg.HoAperiodicCqiCfgSwitch parameter: l

If the CellCqiAdaptiveCfg.HoAperiodicCqiCfgSwitch parameter is set to OFF(Off): The aperiodic CSI reporting mode is not configured in the handover command. It is configured only after the handover. Under this parameter setting, the overhead of handover signaling is low and therefore the handover success rate is high and the handover delay is short. After the handover, the UE cannot obtain the highest downlink throughput without periodic CSI reports.

l

If the CellCqiAdaptiveCfg.HoAperiodicCqiCfgSwitch parameter is set to ON(On): The aperiodic CSI reporting mode is configured in the handover command. If periodic CSI reporting is not configured, the eNodeB triggers an aperiodic CSI reporting procedure for a downlink service after the handover. As the eNodeB proactively triggers an aperiodic CSI reporting procedure after the handover, the eNodeB can obtain the highest downlink throughput. However, the overhead of handover signaling is high, which may decrease the handover success rate and increase the handover delay.

4.7.4 Optimized Periodic CQI Reporting on the PUCCH When the CqiAdaptiveCfg.CqiPeriodAdaptive parameter is set to ON(On), optimized periodic CQI reporting on the PUCCH appropriately extends the interval of periodic CQI reporting to save RBs on the PUCCH. This function enables more RBs to be used for PUSCH data transmission, improving uplink throughput. Optimized periodic CQI reporting on the PUCCH is controlled by the CqiAdaptiveCfg.PucchPeriodicCqiOptSwitch parameter. In addition, optimized periodic CQI reporting on the PUCCH takes effect only when the CqiAdaptiveCfg.CqiPeriodAdaptive parameter is set to ON(On). l Issue 04 (2015-08-31)

If the CellCqiAdaptiveCfg.CqiPeriodAdaptive parameter is set to ON(On): Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

44



The interval between periodic CQI reporting is adaptively adjusted by the eNodeB based on the PUCCH load. When the cell serves a small number of UEs, the interval is set to a small value (minimum value: 5 ms); when the number of online UEs increases, the interval is gradually increased (maximum value: 160 ms). The optimized periodic CQI reporting on the PUCCH function extends the CQI reporting interval and therefore saves PUCCH resources. This function enables more RBs to be used for PUSCH data transmission, improving uplink throughput. l

If the CellCqiAdaptiveCfg.CqiPeriodAdaptive parameter is set to OFF(Off): The interval between periodic CQI reporting is specified by the user-level parameter CellCqiAdaptiveCfg.UserCqiPeriod. NOTE

During a periodic or an aperiodic CSI reporting procedure, all of CQI, RI, and PMI (for closed-loop MIMO) are reported. "Cqi" in the EnAperiodicCqiRptSwitch option of the CellAlgoSwitch.dlschswitch parameter does not indicate that only CQI is reported during an optimized periodic CQI reporting on the PUCCH or an enhanced aperiodic CQI reporting procedure; actually, all of CQI, RI, and PMI are reported.

4.7.5 Enhanced Aperiodic CQI Reporting If UEs are scheduled in frequency selective scheduling (FSS) mode, the eNodeB selects aperiodic CQI reporting for these UEs. If UEs are scheduled in non-FSS mode, the eNodeB selects periodic or aperiodic CQI reporting for these UEs, depending on the EnAperiodicCqiRptSwitch option of the CellAlgoSwitch.DlSchSwitch parameter: l

If the EnAperiodicCqiRptSwitch option is cleared: If UEs are scheduled in non-FSS mode, the eNodeB selects periodic CQI reporting for these UEs and does not trigger aperiodic CQI reporting based on downlink services. If there is not valid periodic CQI reporting during eight periods, the eNodeB triggers an aperiodic CQI reporting procedure. If the UE is not allocated resources for periodic CQI reporting, the eNodeB triggers an aperiodic CQI reporting procedure every 160 ms.

l

If the EnAperiodicCqiRptSwitch option is selected: If UEs are scheduled in non-FSS mode, the eNodeB selects periodic or aperiodic CQI reporting for these UEs. The eNodeB triggers aperiodic CQI reporting based on the period of periodic CQI reporting, period of enhanced aperiodic CQI reporting for UEs in frequency diversity scheduling (FDS) mode (that is, in non-FSS mode), and downlink services. By increasing the periodic CQI reporting period, the eNodeB reduces the consumption of PUCCH resources and increases uplink throughput. By using aperiodic CQI reporting, the eNodeB obtains real-time downlink channel quality information and increases downlink transmission rates. However, aperiodic CQI reporting consumes more PDCCH resources. Therefore, it is recommended that the CellPdcchAlgo.PdcchSymNumSwitch parameter be set to ECFIADAPTIONON(Enhanced CFI Adaption On) to reduce the number of symbols used by the PDCCH and increase downlink transmission rates. If UEs are scheduled in FDS mode, the enhanced aperiodic CQI reporting trigger period is specified by the CellDlschAlgo.FDUEEnhAperCQITrigPeriod parameter. When this parameter is set to a larger value, enhanced aperiodic CQI reporting is less frequently triggered, which reduces uplink overhead. When this parameter is set to a smaller value, enhanced aperiodic CQI reporting is more frequently triggered, which brings downlink gains in some scenarios (for example, in downlink closed-loop MIMO) but increases uplink overhead.

Issue 04 (2015-08-31)


45



If both DRX.DrxAlgSwitch and CellPreAllocGroup.PreAllocationSwitch are turned on, the number of periodic CQI reports will increase. The optimized periodic CQI reporting on the PUCCH and enhanced aperiodic CQI reporting functions can work together to improve the DL transmission rate. Specifically, optimized periodic CQI reporting on the PUCCH extends the interval of periodic CQI reporting while enhanced aperiodic CQI reporting shortens the interval to some extent. In this way, the consumed RBs on the PUCCH are reduced without decreasing the number of CQI reports.

4.7.6 Aperiodic CQI Reporting Optimization Aperiodic CQI reporting optimization aims to avoid unnecessary aperiodic CQI reporting triggered by access failure or discontinuous reception (DRX) start, save PUSCH and PDCCH resources, and increase downlink throughput. Aperiodic CQI reporting optimization is controlled by the AperiodicCqiTrigOptSwitch option of the CellAlgoSwitch.DlSchSwitch parameter: l

If the AperiodicCqiTrigOptSwitch option is cleared: For a UE that initially accesses the network, aperiodic CQI reporting is triggered based on the trigger conditions 200 ms after a downlink Media Access Control (MAC) entity is set up for this UE. If aperiodic CQI reporting is triggered by ineffectiveness of periodic CQI reporting and the CQI report fails a cyclic redundancy check (CRC), aperiodic CQI reporting is triggered again after eight TTIs regardless of the Drx.DrxAlgSwitch parameter setting.

l

If the AperiodicCqiTrigOptSwitch option is selected: For a UE that initially accesses the network, aperiodic CQI reporting is triggered based on the trigger conditions 200 ms after a downlink MAC entity is set up for this UE and the eNodeB detects that the UE has successfully accessed the network. If aperiodic CQI reporting is triggered by the ineffectiveness of periodic CQI reporting and the CQI report fails a CRC: –

If the Drx.DrxAlgSwitch parameter is set to ON(On), aperiodic CQI reporting is not triggered again.

–

If the Drx.DrxAlgSwitch parameter is set to OFF(Off), aperiodic CQI reporting is triggered after eight TTIs.

The selection of the AperiodicCqiTrigOptSwitch option can reduce uplink CQI reports on the PUSCH, save PDCCH resources, lower UE power consumption, and increase downlink throughput. In scenarios where uplink channel conditions are very poor, however, the throughput slightly decreases.

4.7.7 Workaround for UE Incompatibility in Aperiodic CQI Reporting Mode When a type of UE in aperiodic CQI reporting mode 3-1 simultaneously transmits a CQI on the PUSCH and an ACK/NACK, it does not calculate the number of subcarriers for the CQI and ACK/NACK according to 3GPP specifications. As a result, the eNodeB fails to demodulate the ACK/NACK, which leads to a loss in downlink throughput. The eNodeB uses the ApCqiAndAckAbnCtrlSwitch option of the eNodeBAlgoSwitch.CompatibilityCtrlSwitch parameter to address this situation. When a UE in aperiodic CQI reporting mode 3-1 needs to simultaneously transmit a CQI and an ACK/ NACK: Issue 04 (2015-08-31)


46



l

If the ApCqiAndAckAbnCtrlSwitch option is selected, the UE does not transmit the CQI on the PUSCH; instead, it transmits the CQI according to the preallocation instruction of the eNodeB.

l

If the ApCqiAndAckAbnCtrlSwitch option is deselected, the UE transmits the CQI on the PUSCH.

4.7.8 Downlink Rank Optimization In TM2 or TM6 mode, the UE does not report RIs and the eNodeB can use only rank 1 for downlink scheduling. In TM3 or TM4 mode, the UE reports RIs and the eNodeB can use rank 1 or higher for downlink scheduling. The UE selects a rank with the highest spectral efficiency to report based on the downlink channel measurement results and the receiver capability. There is a possibility that the UE reports inappropriate RIs due to fluctuating channel conditions, especially when there is little difference in the spectral efficiency between different ranks. Typically, the UE reports rank 2 when the performance of rank 1 is better. Downlink rank optimization can avoid performance deterioration caused by inaccurate RIs reported by the UE: l

If the CellDlschAlgo.DlRankOptimizeSwitch parameter is set to OFF(Off): The eNodeB performs dynamic downlink scheduling based on reported RIs. If the rank is 1, the eNodeB selects open-loop or closed-loop transmit diversity. If the rank is higher than 1, the eNodeB uses open-loop or closed-loop spatial multiplexing. If the BBP of the eNodeB detects that a reported RI is unreliable, the eNodeB uses rank 1 for downlink scheduling.

l

If the CellDlschAlgo.DlRankOptimizeSwitch parameter is set to ON(On): For non-frequency-selective scheduling, the eNodeB performs rank filtering based on reported RIs. If the probability of reporting rank 1 is higher than a threshold, the eNodeB selects rank 1 for downlink scheduling even when the UE reports rank 2. For frequency selective scheduling, the eNodeB does not perform rank filtering because this type of scheduling is based on aperiodic CSI reporting. If the BBP of the eNodeB detects that a reported RI is unreliable, the eNodeB selects the original rank and CSI for downlink scheduling to avoid a jump in the peak rate.

Downlink rank optimization applies to the scenarios where the UE tends to falsely report rank 2 when it should report rank 1. If the UE correctly reports the rank or tends to falsely report rank 1 when it should report rank 2, the downlink throughput may not improve or even decrease a little after downlink rank optimization is enabled. This function needs to be fully tested before being enabled. In scenarios where this function can improve the downlink performance, this function can be enabled. NOTE

l The number of layers in downlink scheduling must be less than or equal to the rank specified by the CellDlschAlgo.MaxMimoRankPara parameter. l Rank filtering applies only to 2x2 MIMO. For closed-loop MIMO, the eNodeB selects the PMI corresponds to the codeword with an improved modulation and coding mechanism (MCS) for downlink scheduling.

4.7.9 Downlink Rank Detection Rank measurements reported by UEs may be inaccurate because of the following causes: Issue 04 (2015-08-31)


47



l

Different load levels of cells cause different interference to CRS and physical downlink shared channel (PDSCH).

l

The accuracy of rank measurement varies with UEs.

Downlink rank detection helps identify inaccurate rank values and obtain the optimal rank values to achieve better scheduling performance and increase downlink throughput. Rank detection is applicable when the number of CRS antenna ports is two and the transmission mode is TM3. Downlink rank detection is controlled by the CellDlschAlgo.DlRankDetectSwitch parameter. l

When the DetectRank1AdjSwitch option of the CellDlschAlgo.DlRankDetectSwitch parameter is selected, the eNodeB uses the rank values reported by UEs for downlink scheduling.

l

When the DetectRank2AdjSwitch option of the CellDlschAlgo.DlRankDetectSwitch parameter is selected, the eNodeB first uses rank 1 (reported by UEs) for downlink scheduling and attempts rank 2 detection. –

If rank 2 detection attempts succeed continuously, the eNodeB then uses rank 2 for downlink scheduling.

–

If rank 2 detection attempts fail, the eNodeB continues to use rank 1 for downlink scheduling. NOTE

For details about whitelist-based differentiated handling for downlink rank detection, see Terminal Awareness Differentiation Feature Parameter Description.

Issue 04 (2015-08-31)


48


5 Related Features

5

Related Features

5.1 Features Related to LBFD-00202001 UL 2-Antenna Receive Diversity Prerequisite Features None

Mutually Exclusive Features None

Impacted Features None

5.2 Features Related to LOFD-001005 UL 4-Antenna Receive Diversity Prerequisite Features LOFD-001001 DL 2x2 MIMO Uplink 4-antenna receive diversity requires that cells support at least 2T4R.

Mutually Exclusive Features LOFD-001096 Advanced Receiver (PSIC) Parallel soft interference cancellation (PSIC) receivers are not supported in uplink 4-antenna receive diversity mode. Therefore, LOFD-001005 UL 4-Antenna Receive Diversity cannot be used with LOFD-001096 Advanced Receiver (PSIC). LOFD-081206 Intra-eNodeB Coordinated Uplink AMC Issue 04 (2015-08-31)


49


5 Related Features

Coordinated adaptive modulation and coding (CAMC) can be enabled only in 1T2R and 2T2R scenarios.


5.3 Features Related to LOFD-001002 UL 2x2 MU-MIMO Prerequisite Features LOFD-00101502 Dynamic Scheduling When LOFD-001002 UL 2x2 MU-MIMO is enabled, the eNodeB schedules two UEs using the same uplink time-frequency resources. The enabling and disabling of this feature are under control of LOFD-00101502 Dynamic Scheduling. LBFD-00202001 UL 2-Antenna Receive Diversity LOFD-001002 UL 2x2 MU-MIMO requires LBFD-00202001 UL 2-Antenna Receive Diversity to receive and process uplink signals.


Impacted Features LOFD-001016 VoIP Semi-persistent Scheduling LOFD-001002 UL 2x2 MU-MIMO and LOFD-001016 VoIP Semi-persistent Scheduling can be enabled at the same time but VoIP UE performance may not reach the optimum level, for example, the mean opinion score (MOS) may decrease. When both features are enabled, UEs are paired for MU-MIMO in each TTI and different paired UEs cause different levels of interference to the target VoIP UEs. The interference cannot be immediately mitigated because the RBs and MCSs of target VoIP UEs are comparatively stable in semi-persistent scheduling. LOFD-00101402 Uplink Dynamic Inter-Cell Interference Coordination Uplink MU-MIMO is used to increase uplink capacity whereas uplink dynamic inter-cell interference coordination (ICIC) is used to coordinate interference between cells to achieve a tradeoff between capacity and coverage. Therefore, if LOFD-001002 UL 2x2 MU-MIMO is used with LOFD-00101402 Uplink Dynamic Inter-Cell Interference Coordination, MUMIMO performance may not reach the optimum. LBFD-00202202 Uplink Static Inter-Cell Interference Coordination The impact between LOFD-001002 UL 2x2 MU-MIMO and LBFD-00202202 Uplink Static Inter-Cell Interference Coordination is the same as that between LOFD-001002 UL 2x2 MUMIMO and LOFD-00101402 Uplink Dynamic Inter-Cell Interference Coordination. LOFD-001066 Intra-eNodeB UL CoMP LOFD-001002 UL 2x2 MU-MIMO and LOFD-001066 Intra-eNodeB UL CoMP can be enabled for a cell at the same time but cannot be performed for a UE at the same time. Uplink Issue 04 (2015-08-31)


50


5 Related Features

CoMP for type-1 UEs has the highest priority, MU-MIMO the second, and uplink CoMP for type-2 UEs the third. LOFD-070222 Intra-eNodeB UL CoMP Phase II LOFD-001002 UL 2x2 MU-MIMO and LOFD-070222 Intra-eNodeB UL CoMP Phase II can be enabled for a cell at the same time but cannot be performed for a UE at the same time. Uplink CoMP for type-1 UEs has the highest priority, MU-MIMO the second, and uplink CoMP for type-2 UEs the third. LOFD-070223 UL CoMP based on Coordinated BBU LOFD-001002 UL 2x2 MU-MIMO and LOFD-070223 UL CoMP based on Coordinated BBU can be enabled for a cell at the same time but cannot be performed for a UE at the same time. Uplink CoMP for type-1 UEs has the highest priority, MU-MIMO the second, and uplink CoMP for type-2 UEs the third. LOFD-001007 High Speed Mobility LOFD-001002 UL 2x2 MU-MIMO and LOFD-001007 High Speed Mobility can be enabled for a cell at the same time but UEs in this cell cannot be paired for MU-MIMO. LOFD-001008 Ultra High Speed Mobility LOFD-001002 UL 2x2 MU-MIMO and LOFD-001008 Ultra High Speed Mobility can be enabled for a cell at the same time but UEs in this cell cannot be paired for MU-MIMO. LOFD-001096 Advanced Receiver (PSIC) LOFD-001096 Advanced Receiver (PSIC) helps improve the performance of uplink 2x2 MUMIMO. Therefore, it is recommended that LOFD-001002 UL 2x2 MU-MIMO be used with LOFD-001096 Advanced Receiver (PSIC). LOFD-003029 SFN and LOFD-070205 Adaptive SFN/SDMA LOFD-003029 SFN and LOFD-070205 Adaptive SFN/SDMA are compatible with LOFD-001002 UL 2x2 MU-MIMO at the cell level. However, uplink joint reception and MUMIMO cannot be performed for a UE at the same time. UEs that require uplink joint reception take precedence over UEs that require MU-MIMO.

5.4 Features Related to LOFD-001058 UL 2x4 MU-MIMO Prerequisite Features LOFD-00101502 Dynamic Scheduling When LOFD-001058 UL 2x4 MU-MIMO is enabled, the eNodeB schedules two UEs using the same uplink time-frequency resources. The enabling and disabling of this feature are under control of LOFD-00101502 Dynamic Scheduling. LOFD-001001 DL 2x2 MIMO Uplink 2x4 MU-MIMO requires that cells support at least 2T4R. LOFD-001005 UL 4-Antenna Receive Diversity LOFD-001058 UL 2x4 MU-MIMO requires LOFD-001005 UL 4-Antenna Receive Diversity to receive and process uplink signals. Issue 04 (2015-08-31)


51


5 Related Features

Mutually Exclusive Features LOFD-001096 Advanced Receiver (PSIC) PSIC receivers are not supported in uplink 4-antenna receive diversity mode. Therefore, LOFD-001058 UL 2x4 MU-MIMO cannot be used with LOFD-001096 Advanced Receiver (PSIC).

Impacted Features LOFD-001016 VoIP Semi-persistent Scheduling LOFD-001058 UL 2x4 MU-MIMO and LOFD-001016 VoIP Semi-persistent Scheduling can be enabled simultaneously but the VoIP UE performance may not reach the optimum level, for example, the mean opinion score (MOS) may decrease. When both features are enabled, MU-MIMO UEs are paired in each TTI and different paired UEs cause different levels of interference to the target VoIP UEs. However, the interference cannot be immediately adjusted because the RBs and MCSs of target VoIP UEs are comparatively stable in semipersistent scheduling. LOFD-00101402 Uplink Dynamic Inter-Cell Interference Coordination Uplink MU-MIMO is used to increase uplink capacity whereas uplink dynamic inter-cell interference coordination (ICIC) is used to coordinate interference between cells to achieve a tradeoff between capacity and coverage. Therefore, if LOFD-001058 UL 2x4 MU-MIMO is used with LOFD-00101402 Uplink Dynamic Inter-Cell Interference Coordination, MUMIMO performance may not reach the optimum. LBFD-00202202 Uplink Static Inter-Cell Interference Coordination The impact between LOFD-001058 UL 2x4 MU-MIMO and LBFD-00202202 Uplink Static Inter-Cell Interference Coordination is the same as that between LOFD-001058 UL 2x4 MUMIMO and LOFD-00101402 Uplink Dynamic Inter-Cell Interference Coordination. LOFD-001066 Intra-eNodeB UL CoMP LOFD-001058 UL 2x4 MU-MIMO and LOFD-001066 Intra-eNodeB UL CoMP can be enabled simultaneously but they cannot take effect simultaneously for the same UE. Uplink CoMP for type-1 CoMP UEs has the highest priority, MU-MIMO the second, and uplink CoMP for type-2 CoMP UEs the third. LOFD-070222 Intra-eNodeB UL CoMP Phase II LOFD-001058 UL 2x4 MU-MIMO can be used with LOFD-070222 Intra-eNodeB UL CoMP Phase II but they cannot take effect simultaneously for the same UE. Uplink CoMP for type-1 CoMP UEs has the highest priority, MU-MIMO the second, and uplink CoMP for type-2 CoMP UEs the third. LOFD-070223 UL CoMP based on Coordinated BBU LOFD-001058 UL 2x4 MU-MIMO and LOFD-070223 UL CoMP based on Coordinated BBU can be enabled simultaneously but they cannot take effect simultaneously for the same UE. Uplink CoMP for type-1 CoMP UEs has the highest priority, MU-MIMO the second, and uplink CoMP for type-2 CoMP UEs the third. LOFD-001007 High Speed Mobility LOFD-001058 UL 2x4 MU-MIMO and LOFD-001007 High Speed Mobility can be enabled simultaneously for a cell. However, UEs in this cell cannot be selected for pairing. Issue 04 (2015-08-31)


52


5 Related Features

LOFD-001008 Ultra High Speed Mobility LOFD-001058 UL 2x4 MU-MIMO and LOFD-001008 Ultra High Speed Mobility can be enabled simultaneously for a cell. However, UEs in this cell cannot be selected for pairing. LOFD-003029 SFN and LOFD-070205 Adaptive SFN/SDMA LOFD-003029 SFN and LOFD-070205 Adaptive SFN/SDMA are compatible with LOFD-001002 UL 2x4 MU-MIMO at the cell level. However, uplink joint reception and MUMIMO cannot be performed for a UE at the same time. UEs that require uplink joint reception take precedence over UEs that require MU-MIMO.

5.5 Features Related to LOFD-001001 DL 2x2 MIMO Prerequisite Features LBFD-00202001 UL 2-Antenna Receive Diversity LOFD-001001 DL 2x2 MIMO requires LBFD-00202001 UL 2-Antenna Receive Diversity to receive and process uplink signals.


Impacted Features LOFD-00101401 Downlink Dynamic Inter-Cell Interference Coordination When the fixed transmission mode TM6 is used and LOFD-00101401 Downlink Dynamic Inter-Cell Interference Coordination is enabled, system performance deteriorates because using ICIC to expand and shrink the lower frequency band edge affects resource allocation in TM6. LAOFD-002001 Static TDM eICIC When LAOFD-002001 Static TDM eICIC is enabled, the eNodeB does not support adaptive configuration of open- and closed-loop transmission modes. LOFD-00101502 Dynamic Scheduling When the fixed transmission mode TM6 is selected and the frequency selective scheduling function of LOFD-00101502 Dynamic Scheduling is enabled, frequency selective scheduling does not provide gains because it cannot work with resource allocation in TM6. LOFD-001007 High Speed Mobility Closed-loop MIMO is suitable in low-speed scenarios. If TM4, TM6, or adaptive configuration of closed-loop transmission modes is used in high-speed scenarios, system performance deteriorates. In this case, adaptive configuration of open-loop transmission modes is recommended. When UEs are moving at high speed, their demodulation performance based on DMRSs in TM9 is not satisfactory. In addition, TM9 is commonly used in closed-loop mode, which requires that UEs report PMIs or RIs. Therefore, TM9 is always used in low-speed scenarios, not in high-speed scenarios. Issue 04 (2015-08-31)


53


5 Related Features

LOFD-001008 Ultra High Speed Mobility Closed-loop MIMO is suitable in low-speed scenarios. If TM4, TM6, or adaptive configuration of closed-loop transmission modes is used in high-speed scenarios, system performance deteriorates. In this case, adaptive configuration of open-loop transmission modes is recommended. When UEs are moving at ultra high speed, their demodulation performance based on DMRSs in TM9 is not satisfactory. In addition, TM9 is commonly used in closed-loop mode, which requires that UEs report PMIs or RIs. Therefore, TM9 is always used in low-speed scenarios, not in ultra-high-speed scenarios. NOTE

Fixed MIMO transmission mode applies to performance tests before the commercial use of multipleantenna transmission feature. Adaptive MIMO transmission mode is recommended for commercial scenarios.

LBFD-002034 RRU Channel Cross Connection Under MIMO When LBFD-002034 RRU Channel Cross Connection Under MIMO is used, the transmission delays of two RF modules may not be aligned. In this case, downlink open-loop 2x2 MIMO in TM9 can be deployed, but downlink closed-loop 2x2 MIMO in TM9 is not recommended. LOFD-001016 VoIP Semi-persistent Scheduling This feature and LOFD-001016 VoIP Semi-persistent Scheduling can work together. During semi-persistent scheduling for TM9 UEs, the PDSCH is transmitted on port 7 instead of in transmit diversity mode. For details, see section 7.1 "UE procedure for receiving the physical downlink shared channel" in 3GPP TS 36.213 V10.5.0. LOFD-070205 Adaptive SFN/SDMA In TM3 or TM4, CRSs are transmitted in multiple RRUs or cells while the PDSCH are transmitted in one RRU or cell. This mismatch affects the adaptive SFN performance. TM9 can avoid this mismatch, obviously increase the average cell throughput and cell-edge throughput of a cell, and improve user experience. LOFD-0070220 eMBMS Phase 1 based on Centralized MCE Architecture Currently, services carried on the PDSCH in TM9 cannot be scheduled in the MBSFNs subframes occupied by the PMCH. LOFD-001047 LoCation Services (LCS) When LCS is used, LCS reference signals may conflict with CSI-RSs and DMRSs. In this case, if only LCS reference signals are transmitted but neither CSRI-RSs nor DMRSs are transmitted, TM9 performance is affected. Services in TM9 are not scheduled in subframes where LCS reference signals are transmitted. LOFD-001070 Symbol Power Saving In normal subframes, scheduling of services in TM9 can work with basic symbol power saving. In subframes where power saving is applied, no PDSCH services (including services in TM9) are scheduled but CRSs and CSI-RSs can be transmitted. However, the enhanced symbol power saving mode uses MBSFN subframes to avoid scheduling and to achieve power saving. By contrast, TM9 uses MBSFN subframes to improve performance. In enhanced symbol power saving mode, services in TM9 cannot be scheduled in MBSFN subframes configured for this mode. Issue 04 (2015-08-31)


54


5 Related Features

Therefore, TM9 needs to be considered in the entry and exit of the symbol power saving mode. LOFD-001009 Extended Cell Access Radius Generally, TM9 is not used in extended coverage. LOFD-001031 Extended CP TM9 is not compatible with LOFD-001031 Extended CP.

5.6 Features Related to LOFD-001003 DL 4x2 MIMO Prerequisite Features LOFD-001005 UL 4-Antenna Receive Diversity Downlink 4x2 MIMO can be used in a cell only when the cell is a 4T4R cell. LOFD-001001 DL 2x2 MIMO Downlink 4x2 MIMO can be used only after the license for downlink 2x2 MIMO is purchased.

Mutually Exclusive Features LOFD-081223 Extended Cell Access Radius Beyond 100km When the cell coverage exceeds 100 km, channel calibration is not supported and therefore downlink 4x2 or 4x4 MIMO in closed-loop mode is also not supported.

Impacted Features LAOFD-002001 Static TDM eICIC When LAOFD-002001 Static TDM eICIC is enabled, the eNodeB does not support adaptive configuration of open- and closed-loop transmission modes. LOFD-00101401 Downlink Dynamic Inter-Cell Interference Coordination System performance deteriorates when TM6 is used and LOFD-00101401 Downlink Dynamic Inter-Cell Interference Coordination is enabled because using ICIC to expand and shrink the lower frequency band edge affects the resource allocation of TM6. LOFD-00101502 Dynamic Scheduling The gains of frequency selective scheduling are negligible when TM6 is used and the frequency selective scheduling feature of LOFD-00101502 Dynamic Scheduling is enabled because the resource allocation of TM6 affects the coordination between dynamic scheduling and frequency selective scheduling. LOFD-001007 High Speed Mobility Closed-loop MIMO is suitable in low-speed scenarios. If TM4, TM6, or adaptive configuration of closed-loop transmission modes is used in high-speed scenarios, system performance deteriorates. In this case, adaptive configuration of open-loop transmission modes is recommended. Issue 04 (2015-08-31)


55


5 Related Features

When UEs are moving at high speed, their demodulation performance based on DMRSs in TM9 is not satisfactory. In addition, TM9 is commonly used in closed-loop mode, which requires that UEs report PMIs or RIs. Therefore, TM9 is always used in low-speed scenarios, not in high-speed scenarios. LOFD-001008 Ultra High Speed Mobility Closed-loop MIMO is suitable in low-speed scenarios. If TM4, TM6, or adaptive configuration of closed-loop transmission modes is used when UEs are moving at ultra high speed, the system performance deteriorates greatly. In this case, adaptive configuration of open-loop transmission modes is recommended. When UEs are moving at ultra high speed, their demodulation performance based on DMRSs in TM9 is not satisfactory. In addition, TM9 is commonly used in closed-loop mode, which requires that UEs report PMIs or RIs. Therefore, TM9 is always used in low-speed scenarios, not in ultra-high-speed scenarios. LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial] Most UEs cannot support carrier aggregation (CA) and 4T simultaneously. If CA is used in a 4T network, the UE performance deteriorates greatly. If all UEs support both CA and 4T, CA and 4T can be used simultaneously. NOTE


LOFD-001016 VoIP Semi-persistent Scheduling This feature and LOFD-001016 VoIP Semi-persistent Scheduling can work together. During semi-persistent scheduling for TM9 UEs, the PDSCH is transmitted on port 7 instead of in transmit diversity mode. For details, see section 7.1 "UE procedure for receiving the physical downlink shared channel" in 3GPP TS 36.213 V10.5.0. LOFD-0070220 eMBMS Phase 1 based on Centralized MCE Architecture Currently, services carried on the PDSCH in TM9 cannot be scheduled in the MBSFNs subframes occupied by the PMCH. LOFD-001047 LoCation Services (LCS) When LCS is used, LCS reference signals may conflict with CSI-RSs and DMRSs. In this case, if only LCS reference signals are transmitted but neither CSRI-RSs nor DMRSs are transmitted, TM9 performance is affected. Services in TM9 are not scheduled in subframes where LCS reference signals are transmitted. LOFD-001070 Symbol Power Saving In normal subframes, scheduling of services in TM9 can work with basic symbol power saving. In subframes where power saving is applied, no PDSCH services (including services in TM9) are scheduled but CRSs and CSI-RSs can be transmitted. However, the enhanced symbol power saving mode uses MBSFN subframes to avoid scheduling and to achieve power saving. By contrast, TM9 uses MBSFN subframes to improve performance. In enhanced symbol power saving mode, services in TM9 cannot be scheduled in MBSFN subframes configured for this mode. Therefore, TM9 needs to be considered in the entry and exit of the symbol power saving mode. Issue 04 (2015-08-31)


56


5 Related Features

LOFD-001009 Extended Cell Access Radius Generally, TM9 is not used in extended coverage. LOFD-001031 Extended CP TM9 is not compatible with LOFD-001031 Extended CP.

5.7 Features Related to LOFD-001060 DL 4x4 MIMO Prerequisite Features LOFD-001005 UL 4-Antenna Receive Diversity Downlink 4x4 MIMO can be used in a cell only when the cell is a 4T4R cell. LOFD-001001 DL 2x2 MIMO Downlink 4x4 MIMO can be used only after the license for downlink 2x2 MIMO is purchased. LOFD-001003 DL 4x2 MIMO Downlink 4x4 MIMO can be used only after the license for downlink 4x2 MIMO is purchased.

Mutually Exclusive Features LOFD-081223 Extended Cell Access Radius Beyond 100km When the cell coverage exceeds 100 km, channel calibration is not supported and therefore downlink 4x2 or 4x4 MIMO in closed-loop mode is also not supported.

Impacted Features LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial] Most UEs cannot support CA and 4T simultaneously. If CA is used in a 4T network, the UE performance deteriorates greatly. If all UEs support both CA and 4T, CA and 4T can be used simultaneously. LOFD-001007 High Speed Mobility Closed-loop MIMO is suitable in low-speed scenarios. If TM4, TM6, or adaptive configuration of closed-loop transmission modes is used in high-speed scenarios, system performance deteriorates. In this case, adaptive configuration of open-loop transmission modes is recommended. When UEs are moving at high speed, their demodulation performance based on DMRSs in TM9 is not satisfactory. In addition, TM9 is commonly used in closed-loop mode, which requires that UEs report PMIs or RIs. Therefore, TM9 is always used in low-speed scenarios, not in high-speed scenarios. LOFD-001008 Ultra High Speed Mobility Closed-loop MIMO is suitable in low-speed scenarios. If TM4, TM6, or adaptive configuration of closed-loop transmission modes is used when UEs are moving at ultra high Issue 04 (2015-08-31)


57


5 Related Features

speed, the system performance deteriorates greatly. In this case, adaptive configuration of open-loop transmission modes is recommended. When UEs are moving at ultra high speed, their demodulation performance based on DMRSs in TM9 is not satisfactory. In addition, TM9 is commonly used in closed-loop mode, which requires that UEs report PMIs or RIs. Therefore, TM9 is always used in low-speed scenarios, not in ultra-high-speed scenarios. LOFD-001016 VoIP Semi-persistent Scheduling This feature and LOFD-001016 VoIP Semi-persistent Scheduling can work together. During semi-persistent scheduling for TM9 UEs, the PDSCH is transmitted on port 7 instead of in transmit diversity mode. For details, see section 7.1 "UE procedure for receiving the physical downlink shared channel" in 3GPP TS 36.213 V10.5.0. LOFD-0070220 eMBMS Phase 1 based on Centralized MCE Architecture Currently, services carried on the PDSCH in TM9 cannot be scheduled in the MBSFNs subframes occupied by the PMCH. LOFD-001047 LoCation Services (LCS) When LCS is used, LCS reference signals may conflict with CSI-RSs and DMRSs. In this case, if only LCS reference signals are transmitted but neither CSRI-RSs nor DMRSs are transmitted, TM9 performance is affected. Services in TM9 are not scheduled in subframes where LCS reference signals are transmitted. LOFD-001070 Symbol Power Saving In normal subframes, scheduling of services in TM9 can work with basic symbol power saving. In subframes where power saving is applied, no PDSCH services (including services in TM9) are scheduled but CRSs and CSI-RSs can be transmitted. However, the enhanced symbol power saving mode uses MBSFN subframes to avoid scheduling and to achieve power saving. By contrast, TM9 uses MBSFN subframes to improve performance. In enhanced symbol power saving mode, services in TM9 cannot be scheduled in MBSFN subframes configured for this mode. Therefore, TM9 needs to be considered in the entry and exit of the symbol power saving mode. LOFD-001009 Extended Cell Access Radius Generally, TM9 is not used in extended coverage. LOFD-001031 Extended CP TM9 is not compatible with LOFD-001031 Extended CP. LAOFD-002001 Static TDM eICIC When LAOFD-002001 Static TDM eICIC is enabled, the eNodeB does not support adaptive configuration of open- and closed-loop transmission modes. LOFD-00101401 Downlink Dynamic Inter-Cell Interference Coordination When the fixed transmission mode TM6 is used and LOFD-00101401 Downlink Dynamic Inter-Cell Interference Coordination is enabled, system performance deteriorates because using ICIC to expand and shrink the lower frequency band edge affects resource allocation in TM6. Issue 04 (2015-08-31)


58


5 Related Features

LOFD-00101502 Dynamic Scheduling When the fixed transmission mode TM6 is selected and the frequency selective scheduling function of LOFD-00101502 Dynamic Scheduling is enabled, frequency selective scheduling does not provide gains because it cannot work with resource allocation in TM6. NOTE


5.8 Features Related to LBFD-002031 Support of aperiodic CQI reports Prerequisite Features None



5.9 Features Related to LBFD-060101 Optimization of Periodic and Aperiodic CQI Reporting Prerequisite Features None



Issue 04 (2015-08-31)


59


6 Network Impact

6

Network Impact

6.1 LBFD-00202001 UL 2-Antenna Receive Diversity System Capacity LBFD-00202001 UL 2-Antenna Receive Diversity achieves higher diversity gains and array gains than single-antenna reception mode and therefore increases the average uplink cell throughput.

Network Performance LBFD-00202001 UL 2-Antenna Receive Diversity achieves higher diversity gains and array gains than single-antenna reception mode and therefore expands the uplink cell coverage and increases the cell-edge throughput.

6.2 LOFD-001005 UL 4-Antenna Receive Diversity System Capacity Compared with LBFD-00202001 UL 2-Antenna Receive Diversity, this feature brings about 3 dB diversity gains and array gains, decreases the transmit power of cell center users (CCUs), and increases the MCS indexes and throughput of cell edge users (CEUs). In cases 1 to 3 for macro cells defined in 3GPP TR 36.814, uplink 4-antenna receive diversity increases the average uplink throughput by about 30% to 65% compared with uplink 2-antenna receive diversity. If 4-antenna receive diversity provides the same coverage as 2-antenna receive diversity, then: l

For the downlink: Downlink performance is not affected by uplink 4-antenna receive diversity.

l

For the uplink: For UEs far from the eNodeB, uplink 4-antenna receive diversity increases the average uplink MCS index and throughput. A larger number of such UEs leads to a more obvious increase. Particularly, for users very far from the eNodeB, the increase percentage

Issue 04 (2015-08-31)


60


6 Network Impact

exceeds 100%. For UEs closed to the eNodeB, their MCS indexes and throughput do not increase or increases slightly. However, their transmit power decreases by up to 8 dB. If 4-antenna receive diversity provides wider coverage than 2-antenna receive diversity, then: l

For the downlink: Uplink 4-antenna receive diversity may degrade the average downlink MCS index and throughput. One reason is that less time-frequency resources are available to UEs in areas originally covered by uplink 2-antenna receive diversity and therefore the average downlink MCS index and throughput decrease. The other reason is that channel conditions are poor for UEs in areas newly covered by uplink 4-antenna receive diversity and therefore the average downlink MCS index and throughput decrease in the entire cell.

l

For the uplink: Uplink 4-antenna receive diversity may decrease the average uplink MCS index and throughput. One reason is that less time-frequency resources are available to UEs in areas originally covered by uplink 2-antenna receive diversity and therefore the average uplink throughput decreases. The other reason is that channel conditions are poor for UEs in areas newly covered by uplink 4-antenna receive diversity and therefore the average uplink MCS index and throughput decrease in the entire cell.

Network Performance l

Compared with LBFD-00202001 UL 2-Antenna Receive Diversity, this feature brings about 3 dB diversity gains and array gains, improves uplink cell coverage, and increases the MCS indexes and throughput of CEUs. In cases 1 to 3 for macro cells defined in 3GPP TR 36.814, uplink 4-antenna receive diversity increases the uplink cell-edge throughput by about 50% to 158% compared with uplink 2-antenna receive diversity.

l

If 4-antenna receive diversity provides the same coverage as 2-antenna receive diversity, 4-antenna receive diversity improves the network performance. The more the number of UEs far from the eNodeB, the higher the improvement.

l

The area where call drops occur is enlarged to the border where the power falls by about 3 dB in 4-antenna reception, compared with 2-antenna reception. Therefore, in areas newly covered by 4-antenna receive diversity, the number of online UEs increases but these UEs experience poorer channel quality. As a result, the network performance of the entire cell improves slightly or even deteriorates.

6.3 LOFD-001002 UL 2x2 MU-MIMO System Capacity Compared with SU-MIMO, MU-MIMO achieves multiplexing gains because multiple UEs use the same time-frequency resource and more UEs have scheduling opportunities at the same time. This helps increase the average uplink cell throughput. However, UE pairing will negate part of the inter-cell interference suppression capability because the eNodeBs enabled with LOFD-001002 UL 2x2 MU-MIMO are configured with two reception antennas which can distinguish only two signal inputs. Therefore, strong inter-cell interference will affect the capacity improvement performance of LOFD-001002 UL 2x2 MU-MIMO. Issue 04 (2015-08-31)


61


6 Network Impact

Network Performance When interference is severe, the uplink coverage and the throughput of CEUs may decrease because more UEs being scheduled increase uplink interference and IOT.

6.4 LOFD-001058 UL 2x4 MU-MIMO System Capacity Compared with SU-MIMO, MU-MIMO achieves multiplexing gains because multiple UEs use the same time-frequency resource and more UEs have scheduling opportunities at the same time. This helps increase the average uplink cell throughput. In cases 1 to 3 for macro cells defined in 3GPP TR 36.814, this feature increases the average uplink cell throughput by 10% to 30% compared with uplink 4-antenna receive diversity.

Network Performance When interference is severe, the uplink coverage and the CEU throughput may decrease because scheduling more UEs increases uplink interference and IOT.

6.5 LOFD-001001 DL 2x2 MIMO System Capacity LOFD-001001 DL 2x2 MIMO allows an eNodeB to transmit multiple data blocks to UEs with satisfactory channel conditions by using the same time-frequency resource over multiple transmit antennas in open-loop or closed-loop spatial multiplexing mode. In this way, it brings multiplexing gains. Compared with SISO, downlink 2x2 MIMO doubles the downlink peak rate. Downlink 2x2 MIMO in closed-loop mode requires the configuration of integrated RF modules. Its performance cannot be ensured if combined RRUs are used or MIMO mutual aid is enabled. Compared with downlink 2x2 MIMO in TM3 or TM4, downlink 2x2 MIMO in TM9 increases the overhead of dedicated reference signals and the system capacity decreases if downlink 2x2 MIMO in TM9 does not work with other features. However, downlink 2x2 MIMO in TM9 can help the SFN feature to increase the average downlink cell throughput and cell-edge throughput in a multi-RRU cell. The reason is that DMRS and PDSCH are precoded simultaneously, and therefore data demodulation and channel estimation are always matched. When 4T2P is used in a 4T4R cell to implement 2x2 MIMO and the transmit power doubles in cases 1 to 3 for macro cells defined in 3GPP TR 36.814, the average downlink throughput changes by about -5% to +15% compared with 2T2P. If many UEs are not at the cell edge, the throughput loss is high. When the only UE is in the cell center in line of sight (LOS) scenarios, the throughput decreases by about 30% to 40%. For micro eNodeBs, downlink 2x2 MIMO in closed-loop mode depends on UEs. If most PMIs reported by UEs are unreliable or demodulation performance is unsatisfactory, adaptive configuration of closed-loop transmission modes or adaptive configuration of open- and closed-loop transmission modes may reduce system capacity compared with adaptive configuration of open-loop transmission modes. Issue 04 (2015-08-31)


62


6 Network Impact

Network Performance LOFD-001001 DL 2x2 MIMO allows an eNodeB to transmit data using multiple antennas in open-loop or closed-loop transmit diversity mode. In this way, it brings diversity and array gains. Compared with SISO, downlink 2x2 MIMO increases cell coverage in the downlink. Downlink 2x2 MIMO in closed-loop mode requires the configuration of integrated RF modules. Its performance cannot be ensured if combined RRUs are used or MIMO mutual aid is enabled. The CellMimoParaCfg.InitialMimoType parameter has the following impact on the network performance: l

When this parameter is set to TM2(TM2), the service drop rate increases if the number of MIMO mode reconfiguration procedures increases during initial access. If the network side selects a low PDCCH aggregation level, the access success rate increases. However, the downlink throughput decreases because only one data block can be transmitted.

l

When this parameter is set to ADAPTIVE(ADAPTIVE), the service drop rate decreases if the number of MIMO mode reconfiguration procedures decreases during initial access. After the initial access, the UE can transmit one or more data blocks each time, thereby increasing the downlink throughput. If the network side selects a high PDCCH aggregation level, the access success rate decreases.

For the impact of the CellMimoParaCfg.FixedMimoMode and CellMimoParaCfg.MimoAdaptiveSwitch parameters on network performance, see 6.6 LOFD-001003 DL 4x2 MIMO. Downlink 2x2 MIMO in closed-loop mode depends on UEs. If most UEs cannot report reliable PMIs or do not have the required demodulation capability, adaptive configuration of closed-loop transmission modes or adaptive configuration of open- and closed-loop transmission modes provides worse network performance than adaptive configuration of open-loop transmission modes. Downlink 2x2 MIMO in TM9 must work with other features for commercial use. For the impact on network performance, see SFN Feature Parameter Description. If LOFD-070205 Adaptive SFN/SDMA is not deployed, the TM9 performance is worse than the TM3 and TM4 performance because of the overhead of DMRSs. If the UE is moving faster than 30 km/h, the loss in the average cell throughput and cell-edge throughput is especially obvious. In addition, the average throughput and cell-edge throughput may decrease. The throughput loss is high if the CSI-RS reporting period is short, the ratio of inventory UEs is high, and the number of antenna ports for CRSs is large. When 4T2P is used in a 4T4R cell to implement 2x2 MIMO and the transmit power doubles, the downlink coverage increases by about 3 dB compared with 2T2P. In cases 1 to 3 for macro cells defined in 3GPP TR 36.814, the cell-edge throughput increases by about 0% to 30% compared with 2T2P.

6.6 LOFD-001003 DL 4x2 MIMO System Capacity For UEs under favorable channel conditions, LOFD-001003 DL 4x2 MIMO uses open- or closed-loop spatial multiplexing to transmit data. It uses multiple antennas to transmit multiple data blocks using the same time-frequency resource so as to achieve multiplexing Issue 04 (2015-08-31)


63


6 Network Impact

gains and increase the average downlink cell throughput. Downlink 4x2 MIMO approximately doubles the peak rate of downlink SISO. Downlink 4x2 MIMO provides slightly lower peak rates than downlink 2x2 MIMO because of additional overhead of reference signals. The theoretical decrease range is 0% to 2.3%, depending on the bandwidth and control format indicator (CFI). In cases 1 to 3 for macro cells defined in 3GPP TR 36.814, downlink 4x2 MIMO in open-loop mode reduces the average downlink cell throughput by 0% to 10%, compared with downlink 2x2 MIMO in open-loop mode. However, downlink 4x2 MIMO in closed-loop mode provides higher array gains at the transmitter and therefore increases the average downlink cell throughput, compared with downlink 2x2 MIMO in closed-loop mode. In cases 1 to 3 for macro cells defined in 3GPP TR 36.814, downlink 4x2 MIMO in closed-loop mode increases the downlink cell throughput by 10% to 15%, compared with downlink 2x2 MIMO in closed-loop mode. Compared with downlink 4x2 MIMO in TM4, downlink 4x2 MIMO in TM9 increases the overhead of dedicated reference signals and therefore the peak rate decreases. The decrease degree is low if the ratio of MBSFN subframes is high and the number of PDCCH symbols is small. For micro eNodeBs, downlink 4x2 MIMO in open-loop mode provides slightly smaller system capacity and lower peak rate than downlink 2x2 OL MIMO because of additional overhead of reference signals and higher correlation between spatial channels. However, downlink 4x2 MIMO in closed-loop mode provides high array gains at the transmitter and therefore increases the average cell throughput in the downlink. Downlink 4x2 MIMO requires the support of UEs. Downlink 4x2 MIMO (even in closed-loop mode) provides smaller system capacity than downlink 2x2 MIMO if some UEs cannot well support 4-port reference signals.

Network Performance For UEs under unfavorable channel conditions, LOFD-001003 DL 4x2 MIMO uses open- or closed-loop transmit diversity to transmit data. It uses multiple antennas to achieve diversity gains and array gains. Downlink 4x2 MIMO in closed-loop mode achieves higher transmit array gains and provides larger cell coverage than downlink 2x2 MIMO. In cases 1 to 3 for macro cells defined in 3GPP TR 36.814, the downlink cell-edge throughput increases by 10% to 40%, compared with that in downlink 2x2 MIMO in closed-loop mode. Downlink 4x2 MIMO provides slightly lower or higher network performance than downlink 2X2 MIMO because of additional overhead of reference signals and high correlation between spatial channels. In cases 1 to 3 for macro cells defined in 3GPP TR 36.814, the downlink cell-edge throughput changes in the range of -10% to +5%, compared with that in downlink 2x2 MIMO. For the impact of the CellMimoParaCfg.InitialMimoType parameter, see 6.5 LOFD-001001 DL 2x2 MIMO. The CellMimoParaCfg.FixedMimoMode parameter has the following impact on network performance: l

Issue 04 (2015-08-31)

If this parameter is set to TM2(TM2): All UEs work in TM2. UEs report only CQIs (not RIs or PMIs) and can transmit only one data block each time. If the network side is configured with two antenna ports, the downlink peak rate is half of that in TM3 or TM4. If the network side is configured with four antenna ports, the downlink peak rate is less than half of that in TM3 or TM4. The downlink peak throughput is significantly less than that in TM3 or TM4. If the network side selects a low PDCCH aggregation level, the access success rate increases. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

64


6 Network Impact

l

If this parameter is set to TM3(TM3): All UEs work in TM3. UEs report RIs and CQIs (not PMIs) and can transmit one or more data blocks each time. Both the downlink peak rate and downlink throughput are higher than in TM2. If the network side is configured with two antenna ports, the downlink peak rate is doubled. If the network side is configured with four antenna ports, the downlink peak rate is even high. If the network side selects a high PDCCH aggregation level, the access success rate decreases.

l

If this parameter is set to TM4(TM4): All UEs work in TM4. UEs report RIs and PMIs (not CQIs) and can transmit one or more data blocks each time. Both the downlink peak rate and downlink throughput are higher than in TM2. If the network side is configured with two antenna ports, the downlink peak rate is doubled. If the network side is configured with four antenna ports, the downlink peak rate is even high. If the network side selects a high PDCCH aggregation level, the access success rate decreases.

l

–

If the network side is configured with two antenna ports, in non-high-speed scenarios, the downlink throughput is about 5% to 10% greater than that in TM3. If the uplink coding rate increases because of additional PMI reporting, the uplink throughput decreases. If the PMIs reported by UEs are unreliable or the demodulation capability in closed-loop mode cannot be ensured, for example, in high-speed scenarios, the downlink throughput is less than that in TM3.

–

If the network side is configured with four antenna ports, in non-high-speed scenarios, the downlink throughput is about 20% to 30% greater than that in TM3, even 45% for UEs far from the eNodeB. If the uplink coding rate increases because of additional PMI reporting, the uplink throughput decreases. If UEs do not support 4-antenna transmission from the network side, the throughput, service drop rate, or access success rate is about 30% less than that when the network side is configured with two antenna ports.

If this parameter is set to TM6(TM6): All UEs work in TM6. UEs report CQIs and PMIs (not RIs) and can transmit only one data block each time. If the network side is configured with two antenna ports, the downlink peak rate is half of that in TM3 or TM4. If the network side is configured with four antenna ports, the downlink peak rate is less than half of that in TM3 or TM4. The downlink throughput is significantly less than that in TM4. –

If the network side is configured with two antenna ports, in non-high-speed scenarios, the downlink throughput is greater than that in TM2. If the uplink coding rate increases because of additional PMI reporting, the uplink throughput decreases. If the PMIs reported by UEs are unreliable or the demodulation capability in closedloop mode cannot be ensured, for example, in high-speed scenarios, the downlink throughput is less than that in TM2.

–

If the network side is configured with four antenna ports, in non-high-speed scenarios, the downlink throughput is significantly greater than that in TM2. If the uplink coding rate increases because of additional PMI reporting, the uplink throughput decreases. If UEs do not support 4-antenna transmission from the network side, the throughput, service drop rate, or access success rate significantly decreases. The downlink throughput decreases when downlink frequency-selective scheduling or ICIC is enabled, mainly because of the resource allocation mode in TM6.

The CellMimoParaCfg.MimoAdaptiveSwitch parameter has the following impact on the network performance: l

Issue 04 (2015-08-31)

When this parameter is set to NO_ADAPTIVE(NO_ADAPTIVE), a fixed transmission mode is configured based on the CellMimoParaCfg.FixedMimoMode parameter. This Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

65


6 Network Impact

parameter setting is mainly used for performance testing and verification in noncommercial scenarios. l

l

l

When this parameter is set to OL_ADAPTIVE(OL_ADAPTIVE), adaptive configuration of open-loop transmission modes is used. UEs report only RIs and CQIs (not PMIs). This parameter setting allows UEs to best adapt to movement speeds. –

If the network side is configured with two antenna ports, there is no dependency on UEs.

–

If the network side is configured with four antenna ports, there is dependency on UEs. If UEs do not support 4-antenna transmission from the network side, the throughput, service drop rate, or access success rate significantly decreases.

When this parameter is set to CL_ADAPTIVE(CL_ADAPTIVE), adaptive configuration of closed-loop transmission modes is used. UEs report RIs, PMIs, and CQIs. –

If the network side is configured with two antenna ports, in non-high-speed scenarios, the downlink throughput is about 5% to 10% greater than that in when this parameter is set to OL_ADAPTIVE(OL_ADAPTIVE). If the uplink coding rate increases because of additional PMI reporting, the uplink throughput decreases. If the PMIs reported by UEs are unreliable or the demodulation capability in closedloop mode cannot be ensured, for example, in high-speed scenarios, the downlink throughput is less than that when this parameter is set to OL_ADAPTIVE(OL_ADAPTIVE).

–

If the network side is configured with four antenna ports, in non-high-speed scenarios, the downlink throughput is about 20% to 30% greater than that when this parameter is set to OL_ADAPTIVE(OL_ADAPTIVE), even 45% for UEs far from the eNodeB. If the uplink coding rate increases because of additional PMI reporting, the uplink throughput decreases. If UEs do not support 4-antenna transmission from the network side, the throughput, service drop rate, or access success rate is about 30% less than that when the network side is configured with two antenna ports.

When this parameter is set to OC_ADAPTIVE(OC_ADAPTIVE), adaptive configuration of open-loop and closed-loop transmission modes is used. The eNodeB can adaptively configure open- or closed-loop transmission modes for UEs that support this adaptive configuration. –

If the network side is configured with two antenna ports, adaptive configuration of open- and closed-loop transmission modes is difficult to adapt to all scenarios because of little difference in the performance of 2x2 MIMO between open-loop mode and closed-loop mode. Adaptive configuration of open- and closed-loop transmission modes is not recommended because it has even worse performance than adaptive configuration of open-loop transmission modes and adaptive configuration of closed-loop transmission modes.

–

If the network side is configured with four antenna ports but UEs do not support this configuration, the throughput, service drop rate, or access success rate significantly decreases.

CRS port mapping has the following impact on network performance: l

Issue 04 (2015-08-31)

For specific connections between RRU channels and physical channels, the Cell.CrsPortMap parameter determines the mapping between CRS ports and physical antennas. Different polarization directions and spacing of physical antennas lead to different downlink MIMO performance. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

66


l

6 Network Impact

If RRU channels and physical antennas are connected in non-cross-connection mode: –

If this parameter is set to NOT_CFG(Not configure), CRS port mapping is disabled and the network performance is not affected.

–

If this parameter is set to the recommended value, the downlink throughput increases, especially when combined RRUs are used.

–

If this parameter is set to another value, there is a risk that the network performance deteriorates.

The recommended values for an integrated RRU and combined RRUs are different. For micro eNodeBs: l

For UEs under unfavorable channel conditions, LOFD-001003 DL 4x2 MIMO uses open- or closed-loop transmit diversity to transmit data. It uses multiple antennas to achieve diversity gains and array gains. Downlink 4x2 MIMO in closed-loop mode achieves higher transmit array gains and provides larger cell coverage than downlink 2x2 MIMO.

l

Downlink 4x2 MIMO in open-loop mode provides slightly lower network performance than downlink 2x2 MIMO in open-loop mode because of additional overhead of reference signals and higher correlation between spatial channels.

l

Downlink 4x2 MIMO requires the support of UEs. Downlink 4x2 MIMO (even in closed-loop mode) provides lower network performance than downlink 2x2 MIMO if some UEs cannot well support 4-port reference signals.

Compared with downlink 4x2 MIMO in TM4, downlink 4x2 MIMO in TM9 has the following impact on network performance. Baseline Configuration

Issue 04 (2015-08-31)

Gain from Downlink 4x2 MIMO in TM9 Movement Speed < 15 km/h

Movement Speed > 30 km/h

Average Cell Throughput

Cell-Edge Throughput

2T2R RRU, 2x2 MIMO in TM4

5% to 10%

10% to 20%

TM9 may bring a high loss when UEs are moving at high speed.


-15% to -5%

-30% to -10%

TM9 may bring a high loss when UEs are moving at high speed. However, downlink 4x2 IMO in TM9 may improve performance when some inventory UEs work with the eNodeB that uses four antenna ports for transmission. The improvement degree is related to UE categories and movement speeds.


0% to 3%

0% to 5%

TM9 may bring a high loss when UEs are moving at high speed.


67


6 Network Impact

6.7 LOFD-001060 DL 4x4 MIMO System Capacity LOFD-001060 DL 4x4 MIMO uses open- or closed-loop spatial multiplexing to transmit data for UEs under favorable channel conditions. It uses multiple antennas to transmit multiple spatial data blocks on the time-frequency resources so as to achieve higher multiplexing gains. Downlink 4x4 MIMO provides approximately double the peak downlink rate of downlink 2x2 MIMO and provides higher average downlink cell throughput than downlink 2x2 MIMO. In cases 1 to 3 for macro cells defined in 3GPP TR 36.814, downlink 4x4 MIMO in open-loop mode increases the average downlink cell throughput by about 20% to 60%, compared with downlink 2x2 MIMO in open-loop mode. Downlink 4x4 MIMO in TM4 and closed-loop mode increases the average downlink throughput by about 50% to 90%, compared with downlink 2x2 MIMO in TM4 and closed-loop mode. Compared with downlink 4x4 MIMO in TM4, downlink 4x4 MIMO in TM9 increases the overhead of dedicated reference signals and therefore the peak rate decreases. The decrease degree is low if the ratio of MBSFN subframes is high and the number of PDCCH symbols is small. In cases 1 to 3 for macro cells defined in 3GPP TR 36.814, downlink 4x4 MIMO in TM9 in closed-loop mode increases the average downlink throughput by about 40% to 70%, compared with downlink 2x2 MIMO in TM9 and closed-loop mode.

Network Performance LOFD-001060 DL 4x4 MIMO uses open- or closed-loop spatial multiplexing to transmit data for UEs under unfavorable channel conditions. Downlink 4x4 MIMO achieves higher diversity gains at the transmitter and receiver, and provides larger downlink cell coverage than downlink 2x2 MIMO. In cases 1 to 3 for macro cells defined in 3GPP TR 36.814: l

Downlink 4x4 MIMO in open-loop mode increases the downlink cell-edge throughput by about 30% to 70%, compared with downlink 2x2 MIMO in open-loop mode.

l

Downlink 4x4 MIMO in closed-loop mode increases the downlink cell-edge throughput by about 50% to 120%, compared with downlink 2x2 MIMO in closed-loop mode.

l

Downlink 4x4 MIMO in TM9 [Trial] increases the downlink cell-edge throughput by about 50% to 100%, compared with downlink 2x2 MIMO in closed-loop mode.

For the impact of the CellMimoParaCfg.InitialMimoType parameter, see 6.5 LOFD-001001 DL 2x2 MIMO. For the impact of the CellMimoParaCfg.FixedMimoMode and CellMimoParaCfg.MimoAdaptiveSwitch parameters on network performance, see 6.6 LOFD-001003 DL 4x2 MIMO. For the impact of CRS port mapping on network performance, see 6.6 LOFD-001003 DL 4x2 MIMO.

Issue 04 (2015-08-31)


68


6 Network Impact

6.8 LBFD-002031 Support of aperiodic CQI reports System Capacity This feature, together with periodic CQI reporting, allows the eNodeB to periodically or aperiodically obtain CQIs from UEs. With these CQIs, the eNodeB can increase the downlink cell throughput.

Network Performance When the CellCqiAdaptiveCfg.CqiPeriodAdaptive parameter is set to OFF(Off): l

A smaller value of the CellCqiAdaptiveCfg.UserCqiPeriod parameter results in more frequent periodic CQI reporting and higher downlink throughput. However, it also results in a smaller number of UEs supported, fewer RBs for uplink data transmission, and lower uplink throughput.

l

A larger value of CellCqiAdaptiveCfg.UserCqiPeriod results in less frequent CQI reporting and lower downlink throughput, but more supported UEs, more RBs for uplink data transmission, and higher uplink throughput.

If the CellAlgoSwitch.DlSchSwitch parameter is set to EnAperiodicCqiRptSwitch-1, the eNodeB reduces PUCCH resource consumption and increases uplink throughput by increasing the CQI reporting period. The eNodeB also obtains downlink channel quality information more promptly and increases downlink transmission rates through aperiodic CQI reporting. As aperiodic CQI reporting consumes more PDCCH resource, it is also recommended that the CellPdcchAlgo.PdcchSymNumSwitch parameter be set to ECFIADAPTIONON(Enhanced CFI Adaption On) to reduce the number of symbols used by the PDCCH and increase downlink transmission rates. When the CellCqiAdaptiveCfg.HoAperiodicCqiCfgSwitch parameter is set to ON(On), the downlink throughput of handed-over UEs increases. However, an increase in handover signaling overhead may lead to a decrease in the handover success rate and an increase in handover delay.

6.9 LBFD-060101 Optimization of Periodic and Aperiodic CQI Reporting System Capacity Together with PUCCH resource adjustment, optimized periodic CQI reporting on the PUCCH reduces RB consumption on the PUCCH caused by period CQI feedback, increases available RBs on the PUSCH, and improves uplink throughput. Enhanced aperiodic CQI reporting helps increase the CQI reporting frequency and improve the downlink throughput. However, the DL gains provided by this feature depend on CQI measurements of UEs. If both AperiodicCqiTrigOptSwitch and PdcchSymNumSwitch are turned on, this feature reduces aperiodic CQI reporting on the PUSCH when the UE fails to access the cell or when DRX is enabled. The purpose is to save PDCCH resource, consume less UE power, and increase downlink throughput. Issue 04 (2015-08-31)


69


6 Network Impact

Network Performance No impact.

Issue 04 (2015-08-31)


70

7 Engineering Guidelines for Multiple-Antenna Receive Diversity


7

Engineering Guidelines for MultipleAntenna Receive Diversity

7.1 When to Use Multiple-Antenna Receive Diversity l

LBFD-00202001 UL 2-Antenna Receive Diversity This feature is a basic feature and is not under license control. It is automatically enabled if an eNodeB is equipped with two receive antennas. For details, see 7.4.1 Requirements.

l


l

This feature is recommended if the eNodeB is equipped with four receive antennas and the uplink coverage needs to be increased. For details, see 7.4.1 Requirements.

7.2 Required Information Network information needs to be collected before deploying multiple-antenna receive diversity.

Coverage Area l

Coverage area type: dense urban areas, urban areas, suburban districts, rural areas, or highways

l

Service types and their coverage requirements

l

User quantity and user distribution

l

KPI requirements, especially for the cell-edge throughput and average cell throughput in the uplink.

Frequency Band Frequency band information includes the LTE frequency band owned by the operator, adjacent frequency bands, and frequency band distribution of other wireless communications systems in the area which are used to analyze interference from other frequencies. Issue 04 (2015-08-31)


71



Map Whether a digital map of the coverage area is available for system performance simulation needs to be verified.

GSM/UMTS Network Information RF parameters of the existing GSM/UMTS networks are necessary because reusing the existing GSM/UMTS sites helps operators who have deployed GSM/UMTS networks to reduce the cost of deploying LTE networks.

Antenna The following information needs to be collected: l

Antenna model

l

Number of ports

l

Manufacturer

l

Electrical specifications, including the operating frequency band, polarization, gains, horizontal and vertical beamwidths, tilt, sidelobe suppression, front-to-back ratio, and isolation between ports

l

Mechanical specifications, including the antenna size, weight, wind load, and connector

l

Antenna radiation pattern

If a new antenna is to be added, check whether space is sufficient and whether the space meets the requirements for installing the antenna. If an old antenna is to be replaced with a new one, check whether the installation conditions are fulfilled for the new antenna.

Feeder Information about the feeder type and loss

Coupler Information about the coupler type and specifications such as delay and insertion loss

7.3 Planning RF Planning Estimate the uplink budget and capacity based on the information collected by referring to 7.2 Required Information and then complete RF planning.

Network Planning N/A

Hardware Planning It is recommended that an LBBPd or UBBPd be used when the cell bandwidth is 15 or 20 MHz and LOFD-001005 UL 4-Antenna Receive Diversity is enabled. Issue 04 (2015-08-31)


72



NOTE

Neither LBBPd1 nor UBBPd3 supports LOFD-001005 UL 4-Antenna Receive Diversity.

MIMO includes multiple-antenna reception and transmission. Therefore, hardware for multiple-antenna transmission must be considered when you plan hardware for receive diversity. For details about the hardware planning for multiple-antenna transmission, see 9.4.4 Hardware Adjustment.

7.4 Deployment of Multiple-Antenna Receive Diversity 7.4.1 Requirements Operating Environment LBFD-00202001 UL 2-Antenna Receive Diversity requires that the eNodeB have a minimum of two receive channels and two antennas. LOFD-001005 UL 4-Antenna Receive Diversity requires that the eNodeB have a minimum of four receive channels and four antennas.

License If more than two receive channels are used, the operator has purchased the license for the items listed in the following table in addition to a feature license. Without the license, cells cannot be activated. For details about the license control items, see License Management Feature Parameter Description. License Control Item Name

License Control Item ID

BB Receive Channel(FDD)

LT1S00BBRC00

RF Receive Channel(FDD)

LT1S00RFRC00

LBFD-00202001 UL 2-Antenna Receive Diversity This feature is a basic feature and is not under license control. LOFD-001005 UL 4-Antenna Receive Diversity The operator has purchased the feature license and hardware license. l

Issue 04 (2015-08-31)

Feature license


73



l

Feature ID

Feature Name

Model

License Control Item

NE

Sales Unit

LOFD-00100 5

UL 4Antenna Receive Diversity

LT1S0U4 ARD00

UL 4Antenna Receive Diversity (per Cell)(FDD)

eNode B

per Cell

Hardware license

Each BBP and RF unit are equipped with two baseband receive channels and two RF receive channels for a cell, respectively. Therefore, the operator needs to purchase only the license for another two baseband receive channels and two RF receive channels for each cell.

7.4.2 Data Preparation This section describes the data that you need to collect for setting parameters. Required data is data that you must collect for all scenarios. Collect scenario-specific data when necessary for a specific feature deployment scenario. There are three types of data sources: l

Network plan (negotiation required): parameter values planned by the operator and negotiated with the evolved packet core (EPC) or peer transmission equipment

l

Network plan (negotiation not required): parameter values planned and set by the operator

l

User-defined: parameter values set by users

Required Data The following table describes the parameters that must be set in a SECTOR MO to configure a sector. For details, see Cell Management Feature Parameter Description.

Issue 04 (2015-08-31)

Parameter Name

Parameter ID

Data Source

Setting Notes

Sector ID

SECTOR.SEC TORID

Network plan (negotiation not required)

Set this parameter based on the network plan.

Antenna Number

SECTOR.AN TNUM



Cabinet No. of Antenna 1

SECTOR.AN T1CN



Subrack No. of Antenna 1

SECTOR.AN T1SRN




74



Parameter Name

Parameter ID

Data Source

Setting Notes

Slot No. of Antenna 1

SECTOR.AN T1SN



Channel No. of Antenna 1

SECTOR.AN T1N



Create Default Sector Equipment

SECTOR.CR EATESECTO REQM



Default Sector Equipment ID

SECTOR.SEC TOREQMID



The following table describes the parameters that must be set in a SECTOREQM MO to configure a set of sector equipment.

Issue 04 (2015-08-31)

Parameter Name

Parameter ID

Data Source

Setting Notes

Sector Equipment ID

SECTOREQM.S ECTOREQMID



Sector ID

SECTOREQM.S ECTORID



Antenna Number

SECTOREQM.A NTNUM




SECTOREQM.A NT1CN




SECTOREQM.A NT1SRN




SECTOREQM.A NT1SN




SECTOREQM.A NT1N




75



Parameter Name

Parameter ID

Data Source

Setting Notes

Antenna 1 RX/TX Mode

SECTOREQM.A NTTYPE1



The following table describes the parameters that must be set in an eUCellSectorEqm MO to bind a set of sector equipment to a cell. Parameter Name

Parameter ID

Data Source

Setting Notes

Local cell ID

eUCellSectorEqm. LocalCellId



Sector equipment ID

eUCellSectorEqm. SectorEqmId



Scenario-specific Data The following table describes the parameters that must be set in a Cell MO to configure a cell for LBFD-00202001 UL 2-Antenna Receive Diversity and LOFD-001005 UL 4-Antenna Receive Diversity. Parameter Name

Paramete r ID

Data Source

Setting Notes

Local cell ID

Cell.Loca lCellId



Cell transmission and reception mode

Cell.TxR xMode


Set this parameter based on site requirements. For LBFD-00202001 UL 2Antenna Receive Diversity, set this parameter to 1T2R or 2T2R depending on the number of transmit antennas. For LOFD-001005 UL 4-Antenna Receive Diversity, set this parameter to 2T4R or 4T4R depending on the number of transmit antennas.

7.4.3 Precautions To prevent uplink performance deterioration, LBFD-00202001 UL 2-Antenna Receive Diversity requires that the antennas to which the receive channels are connected have Issue 04 (2015-08-31)


76



different polarization directions, regardless of whether an integrated antenna system with multiple ports is used or two antennas each with two ports are combined to serve a cell. If two antennas each with two ports are combined to serve a cell, LOFD-001005 UL 4Antenna Receive Diversity requires that all of the conditions be met: l

The antennas have the same azimuth and downtilt angle.

l

The feeders between the antennas and RRUs have the same type and loss. In addition, the feeders have the same length or have a difference in length less than 1 meter.

If these conditions are not met, uplink performance deteriorates. NOTE

If the difference in downtilt angle is less than 2 degrees, the average performance of uplink 4-antenna receive diversity deteriorates by less than 3% and the cell edge performance by less than 10%. If the difference in downtilt angle is between 3 and 4 degrees, the average performance deteriorates by 5% and the cell edge performance by 20%.

7.4.4 Hardware Adjustment For details about hardware installation for LBFD-00202001 UL 2-Antenna Receive Diversity, see 1T2R Cell, 2T2R Cell (Integrated RRU) or 2T2R Cell (Combined RRUs) in 9.4.4 Hardware Adjustment. For details about hardware installation of LOFD-001005 UL 4-Antenna Receive Diversity, see the following sections in 9.4.4 Hardware Adjustment: l

2T4R Cell (Integrated RRU)

l

2T4R Cell (1T2R+1T2R; 1T2R RRUs)

l


l


l


l


l


7.4.5 Initial Configuration 7.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs Enter the values of the parameters listed in the following table in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the summary data file into the Configuration Management Express (CME) for batch configuration. For detailed instructions, see "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB, which is available in the eNodeB product documentation. The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions: l

Issue 04 (2015-08-31)

The managed objects (MOs) in the following table are contained in a scenario-specific summary data file. In this situation, set the parameters in the MOs, and then verify and save the file. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

77



l

Some MOs in the following table are not contained in a scenario-specific summary data file. In this situation, customize a summary data file to include the MOs before you can set the parameters.

Table 7-1 Parameters related to multiple-antenna receive diversity (for macro eNodeBs) MO

Sheet in the Summary Data File

Parameter Group

Remarks

SECTOR

eNodeB Radio Data

SECTORID, ANTNUM, ANT1CN, ANT1SRN, ANT1SN, ANT1N, CREATESECTOREQM, SECTOREQMID

User-defined sheet

SECTOREQM

eNodeB Radio Data

SECTOREQMID, SECTORID, ANTNUM, ANT1CN, ANT1SRN, ANT1SN, ANT1N, ANTTYPE1

User-defined sheet

Cell

eNodeB Radio Data

LocalCellId, TxRxMode

User-defined sheet

eUCellSectorEqm

eNodeB Radio Data

LocalCellId, SectorEqmId

User-defined sheet

Table 7-2 Parameters related to multiple-antenna receive diversity (for micro eNodeBs) MO


Parameter Group

Remarks

SECTOREQM

eNodeB Radio Data

SECTOREQMID, OPMODE, ANTTYPE

User-defined sheet

Cell

eNodeB Radio Data


User-defined sheet

7.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure is as follows: Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs." For online help, press F1 when a CME window is active, and select Managing the CME > CME Guidelines > LTE Application Management > eNodeB Related Operations > Customizing a Summary Data File for Batch eNodeB Configuration. Issue 04 (2015-08-31)


78



Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME into the customized summary data file. Step 3 In the summary data file, set the parameters in the MOs according to the setting notes provided in section "Data Preparation" and close the file. Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME, and then start the data verification. Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. For detailed operations, see Managing the CME > CME Guidelines > Script File Management > Exporting Incremental Scripts from a Planned Data Area in the CME online help. ----End

7.4.5.3 Using the CME to Perform Single Configuration On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The procedure is as follows: Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window. Step 2 In area 1 shown in Figure 7-1, select the eNodeB to which the MOs belong. Figure 7-1 MO search and configuration window

Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL. Issue 04 (2015-08-31)


79



Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are displayed in area 4. Step 5 Set the parameters in area 4 or 5. Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. ----End

7.4.5.4 Using MML Commands Perform the following steps to configure multiple-antenna receive diversity: Step 1 Add a sector, a set of sector equipment (including antennas), and a cell (including its TX/RX mode). For LBFD-00202001 UL 2-Antenna Receive Diversity, set the TX/RX mode of the cell to 1T2R or 2T2R by referring to the following sections: l

1T2R Cell

l


For LOFD-001005 UL 4-Antenna Receive Diversity, set the TX/RX mode of the cell to 2T4R or 4T4R by referring to the following sections: l


l


l


l


l


l


l


Step 2 Activate the cell. ----End

1T2R Cell For the topology for a 1T2R cell, see Figure 9-1 in 9.4.4 Hardware Adjustment. Example: ADD SECTOR:SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=2,ANT1CN=0,ANT1SRN =60,ANT1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,CREATESECTOREQM=FALS E; ADD SECTOREQM:SECTOREQMID=0,SECTORID=0,ANTNUM=2,ANT1CN=0,ANT1SRN=60,ANT1SN=0,ANT1N=R0A ,ANTTYPE1=RXTX_MODE,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANTTYPE2=RX_MODE; ADD CELL:LOCALCELLID=0,CELLNAME="LTE",FREQBAND=7,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=2850, ULBANDWIDTH=CELL_BW_N50,DLBANDWIDTH=CELL_BW_N50,CELLID=0,PHYCELLID=0,FDDTDDIND=CEL L_FDD,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NO T_CFG,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_FALSE,TXRXMODE=1T2R; ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;

Issue 04 (2015-08-31)


80



2T2R Cell (Integrated RRU) For the topology for a 2T2R cell served by an integrated 2T2R RRU, see Figure 9-2 in 9.4.4 Hardware Adjustment. Example: ADD SECTOR: SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=2,ANT1CN=0,ANT1SRN=60,ANT 1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,CREATESECTOREQM=TRUE,SECTOR EQMID=0; ADD CELL: LOCALCELLID=0,CELLNAME="LTE",FREQBAND=7,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=2850,ULBAN DWIDTH=CELL_BW_N50,DLBANDWIDTH=CELL_BW_N50,CELLID=0,PHYCELLID=0,FDDTDDIND=CELL_FDD ,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG ,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_FALSE,TXRXMODE=2T2R; ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;

2T2R Cell (Combined RRUs) For the topology for a 2T2R cell served by combined 1T2R RRUs, see Figure 9-3 in 9.4.4 Hardware Adjustment. Example: ADD SECTOR: SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=2,ANT1CN=0,ANT1SRN=60,ANT 1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=61,ANT2SN=0,ANT3N=R0A,CREATESECTOREQM=FALSE; ADD SECTOREQM: SECTOREQMID=0,SECTORID=0,ANTNUM=2,ANT1CN=0,ANT1SRN=60,ANT1SN=0,ANT1N=R0A,ANTTYPE1= RXTX_MODE,ANT2CN=0,ANT2SRN=61,ANT2SN=0,ANT2N=R0A,ANTTYPE2=RXTX_MODE; ADD CELL: LOCALCELLID=0,CELLNAME="LTE",FREQBAND=7,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=2850,ULBAN DWIDTH=CELL_BW_N50,DLBANDWIDTH=CELL_BW_N50,CELLID=0,PHYCELLID=0,FDDTDDIND=CELL_FDD ,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG ,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_FALSE,TXRXMODE=2T2R; ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;

2T4R Cell (Integrated RRU) For the topology for a 2T4R cell served by an integrated 2T4R RRU, see Figure 9-4 and Figure 9-5 in 9.4.4 Hardware Adjustment. Example: ADD SECTOR: SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT 1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANT3CN=0,ANT3SRN=60,ANT3SN= 0,ANT3N=R0C,ANT4CN=0,ANT4SRN=60,ANT4SN=0,ANT4N=R0D,CREATESECTOREQM=FALSE; ADD SECTOREQM: SECTOREQMID=0,SECTORID=0,ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT1SN=0,ANT1N=R0A,ANTTYPE1= RXTX_MODE,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANTTYPE2=RXTX_MODE,ANT3CN=0,ANT3S RN=60,ANT3SN=0,ANT3N=R0C,ANTTYPE3=RX_MODE,ANT4CN=0,ANT4SRN=60,ANT4SN=0,ANT4N=R0D,A NTTYPE4=RX_MODE; ADD CELL: LOCALCELLID=0,CELLNAME="LTE",FREQBAND=7,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=2850,ULBAN DWIDTH=CELL_BW_N50,DLBANDWIDTH=CELL_BW_N50,CELLID=0,PHYCELLID=0,FDDTDDIND=CELL_FDD ,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG ,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_FALSE,TXRXMODE=2T4R; ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;

2T4R Cell (1T2R+1T2R; 1T2R RRUs) For the topology for a 2T4R cell served by combined 1T2R RRUs, see Figure 9-6 and Figure 9-7 in 9.4.4 Hardware Adjustment. Issue 04 (2015-08-31)


81



Example: ADD SECTOR: SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT 1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANT3CN=0,ANT3SRN=61,ANT3SN= 0,ANT3N=R0A,ANT4CN=0,ANT4SRN=61,ANT4SN=0,ANT4N=R0B,CREATESECTOREQM=FALSE; ADD SECTOREQM: SECTOREQMID=0,SECTORID=0,ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT1SN=0,ANT1N=R0A,ANTTYPE1= RXTX_MODE,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANTTYPE2=RX_MODE,ANT3CN=0,ANT3SRN =61,ANT3SN=0,ANT3N=R0A,ANTTYPE3=RXTX_MODE,ANT4CN=0,ANT4SRN=61,ANT4SN=0,ANT4N=R0B,A NTTYPE4=RX_MODE; ADD CELL: LOCALCELLID=0,CELLNAME="LTE",FREQBAND=7,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=2850,ULBAN DWIDTH=CELL_BW_N50,DLBANDWIDTH=CELL_BW_N50,CELLID=0,PHYCELLID=0,FDDTDDIND=CELL_FDD ,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG ,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_FALSE,TXRXMODE=2T4R; ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;

2T4R Cell (1T2R+1T2R; 2T2R RRUs) For the topology for a 2T4R cell served by combined 2T2R RRUs, see Figure 9-8, Figure 9-9, and Figure 9-10 in 9.4.4 Hardware Adjustment. To facilitate the upgrade to a 2T2R +0T2R or 4T4R cell, it is recommended that channel A of RRU 1 and channel B of RRU 2 work in TX/RX mode while channel B of RRU 1 and channel A of RRU 2 working in RX mode. Example: ADD SECTOR: SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT 1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANT3CN=0,ANT3SRN=61,ANT3SN= 0,ANT3N=R0A,ANT4CN=0,ANT4SRN=61,ANT4SN=0,ANT4N=R0B,CREATESECTOREQM=FALSE; ADD SECTOREQM: SECTOREQMID=0,SECTORID=0,ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT1SN=0,ANT1N=R0A,ANTTYPE1= RXTX_MODE,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANTTYPE2=RX_MODE,ANT3CN=0,ANT3SRN =61,ANT3SN=0,ANT3N=R0A,ANTTYPE3=RX_MODE,ANT4CN=0,ANT4SRN=61,ANT4SN=0,ANT4N=R0B,ANT TYPE4=RXTX_MODE; ADD CELL: LOCALCELLID=0,CELLNAME="LTE",FREQBAND=7,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=2850,ULBAN DWIDTH=CELL_BW_N50,DLBANDWIDTH=CELL_BW_N50,CELLID=0,PHYCELLID=0,FDDTDDIND=CELL_FDD ,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG ,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_FALSE,TXRXMODE=2T4R; ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;

2T4R Cell (2T2R+0T2R; 2T2R RRUs) For the topology of a 2T4R cell served by combined 2T2R mRFUd modules with one working in 2T2R mode and the other 0T2R mode, see Figure 9-11 and Figure 9-12 in 9.4.4 Hardware Adjustment. Example: ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, HSN=3, HPN=0; ADD RRUCHAIN: RCN=1, TT=CHAIN, BM=COLD, HSN=3, HPN=1; ADD SUBRACK: CN=0, SRN=4, TYPE=RFU; ADD RRU: CN=0, SRN=4, SN=0, TP=TRUNK, RCN=0, PS=0, RT=MRFU, RS=LO, RXNUM=2, TXNUM=2; ADD RRU: CN=0, SRN=4, SN=1, TP=TRUNK, RCN=1, PS=0, RT=MRFU, RS=LO, RXNUM=2, TXNUM=2; ADD SECTOR: SECTORID=0, SECNAME="huawei",LOCATIONNAME="huawei", ANTNUM=4, ANT1CN=0, ANT1SRN=4, ANT1SN=0, ANT1N=R0A, ANT2CN=0, ANT2SRN=4, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=4, ANT3SN=1, ANT3N=R0A, ANT4CN=0, ANT4SRN=4, ANT4SN=1, ANT4N=R0B, CREATESECTOREQM=FALSE; ADD SECTOREQM: SECTOREQMID=0, SECTORID=0, ANTNUM=4, ANT1CN=0, ANT1SRN=4, ANT1SN=0, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=4, ANT2SN=0,

Issue 04 (2015-08-31)


82



ANT2N=R0B, ANTTYPE2=RXTX_MODE, ANT3CN=0, ANT3SRN=4, ANT3SN=1, ANT3N=R0A, ANTTYPE3=RX_MODE, ANT4CN=0, ANT4SRN=4, ANT4SN=1, ANT4N=R0B, ANTTYPE4=RX_MODE; ADD CELL: LocalCellId=0, CellName="LTE", FreqBand=3, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=1925, UlBandWidth=CELL_BW_N25, DlBandWidth=CELL_BW_N25, CellId=25, PhyCellId=25, FddTddInd=CELL_FDD, RootSequenceIdx=33, CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, TxRxMode=2T4R; ADD EUCELLSECTOREQM: LOCALCELLID=0,SECTOREQMID=0;

4T4R Cell (Integrated RRU) For the topology for a 4T4R cell served by an integrated 4T4R RRU, see Figure 9-13 and Figure 9-14 in 9.4.4 Hardware Adjustment. Example: ADD SECTOR: SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT 1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANT3CN=0,ANT3SRN=60,ANT3SN= 0,ANT3N=R0C,ANT4CN=0,ANT4SRN=60,ANT4SN=0,ANT4N=R0D,REATESECTOREQM=TRUE,SECTOREQMID =0; ADD CELL: LOCALCELLID=0,CELLNAME="LTE",FREQBAND=7,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=2850,ULBAN DWIDTH=CELL_BW_N50,DLBANDWIDTH=CELL_BW_N50,CELLID=0,PHYCELLID=0,FDDTDDIND=CELL_FDD ,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG ,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_FALSE,CRSPORTNUM=CRS_PORT_4,TXR XMODE=4T4R; ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;

4T4R Cell (2T2R+2T2R; 2T2R RRUs) For the topology for a 4T4R cell served by combined 2T2R RRUs, see Figure 9-15 and Figure 9-16 in 9.4.4 Hardware Adjustment. Example: ADD SECTOR: SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT 1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANT3CN=0,ANT3SRN=61,ANT3SN= 0,ANT3N=R0A,ANT4CN=0,ANT4SRN=61,ANT4SN=0,ANT4N=R0B,REATESECTOREQM=TRUE,SECTOREQMID =0; ADD CELL: LOCALCELLID=0,CELLNAME="LTE",FREQBAND=7,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=2850,ULBAN DWIDTH=CELL_BW_N50,DLBANDWIDTH=CELL_BW_N50,CELLID=0,PHYCELLID=0,FDDTDDIND=CELL_FDD ,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG ,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_FALSE,CRSPORTNUM=CRS_PORT_4,TXR XMODE=4T4R; ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;

4T4R Cell (2T2R+2T2R; 2T4R RRUs) For the topology for a 4T4R cell served by combined 2T4R RRUs, see Figure 9-17 and Figure 9-18 in 9.4.4 Hardware Adjustment. Example: ADD SECTOR: SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT 1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANT3CN=0,ANT3SRN=61,ANT3SN= 0,ANT3N=R0A,ANT4CN=0,ANT4SRN=61,ANT4SN=0,ANT4N=R0B,CREATESECTOREQM=FALSE; ADD SECTOREQM: SECTOREQMID=0,SECTORID=0,ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT1SN=0,ANT1N=R0A,ANTTYPE1= RXTX_MODE,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANTTYPE2=RXTX_MODE,ANT3CN=0,ANT3S RN=61,ANT3SN=0,ANT3N=R0A,ANTTYPE3=RXTX_MODE,ANT4CN=0,ANT4SRN=61,ANT4SN=0,ANT4N=R0B ,ANTTYPE4=RXTX_MODE;

Issue 04 (2015-08-31)


83



ADD CELL: LOCALCELLID=0,CELLNAME="LTE",FREQBAND=7,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=2850,ULBAN DWIDTH=CELL_BW_N50,DLBANDWIDTH=CELL_BW_N50,CELLID=0,PHYCELLID=0,FDDTDDIND=CELL_FDD ,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG ,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_FALSE,CRSPORTNUM=CRS_PORT_4,TXR XMODE=4T4R; ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;

LBFD-00202001 UL 2-Antenna Receive Diversity The following provides an example for configuring LBFD-00202001 UL 2-Antenna Receive Diversity for micro eNodeBs. Example: If two antennas are used in the downlink (2T2R), the MML command example is as follows: ADD SECTOR:SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=2,ANT1N=R0A,ANT2N= R0B,CREATESECTOREQM=TRUE,SECTOREQMID=0; ADD CELL:LOCALCELLID=0,CELLNAME="LTE",FREQBAND=7,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=2850, ULBANDWIDTH=CELL_BW_N50,DLBANDWIDTH=CELL_BW_N50,CELLID=0,PHYCELLID=0,FDDTDDIND=CEL L_FDD,ROOTSEQUENCEIDX=0,EMERGENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,TXR XMODE=2T2R; ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0; ACT CELL:LOCALCELLID=0;

If one antenna is used in the downlink (1T2R), the MML command example is as follows: ADD SECTOR:SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=2,ANT1N=R0A,ANT2N= R0B,CREATESECTOREQM=FALSE; ADD SECTOREQM:SECTOREQMID=0,SECTORID=0,ANTNUM=2,ANT1N=R0A,ANTTYPE1=RXTX_MODE,ANT2N=R0B ,ANTTYPE2=RX_MODE; ADD CELL:LOCALCELLID=0,CELLNAME="LTE",FREQBAND=7,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=2850, ULBANDWIDTH=CELL_BW_N50,DLBANDWIDTH=CELL_BW_N50,CELLID=0,PHYCELLID=0,FDDTDDIND=CEL L_FDD,ROOTSEQUENCEIDX=0,EMERGENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,TXR XMODE=1T2R; ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0; ACT CELL:LOCALCELLID=0;

LOFD-001005 UL 4-Antenna Receive Diversity The following provides an example for configuring LOFD-001005 4-Antenna Receive Diversity for micro eNodeBs. Example: If four antennas are used in the downlink (4T4R), the MML command example is as follows: ADD SECTOR:SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=4,ANT1N=R0A,ANT2N= R0B,ANT2N=R0C, ANT2N=R0D,CREATESECTOREQM=TRUE,SECTOREQMID=0; ADD CELL:LOCALCELLID=0,CELLNAME="LTE",FREQBAND=7,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=2850, ULBANDWIDTH=CELL_BW_N50,DLBANDWIDTH=CELL_BW_N50,CELLID=0,PHYCELLID=0,FDDTDDIND=CEL L_FDD,ROOTSEQUENCEIDX=0,EMERGENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,TXR XMODE=4T4R; ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0; ACT CELL:LOCALCELLID=0;

If two antennas are used in the downlink (2T4R), the MML command example is as follows: Issue 04 (2015-08-31)


84



ADD SECTOR:SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=4,ANT1N=R0A,ANT2N= R0B,ANT2N=R0C, ANT2N=R0D,CREATESECTOREQM=FALSE; ADD SECTOREQM:SECTOREQMID=0,SECTORID=0,ANTNUM=4,ANT1N=R0A,ANTTYPE1=RXTX_MODE,ANT2N=R0B ,ANTTYPE2=RXTX_MODE,ANT3N=R0C,ANTTYPE3=RX_MODE,ANT4N=R0D,ANTTYPE4=RX_MODE; ADD CELL:LOCALCELLID=0,CELLNAME="LTE",FREQBAND=7,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=2850, ULBANDWIDTH=CELL_BW_N50,DLBANDWIDTH=CELL_BW_N50,CELLID=0,PHYCELLID=0,FDDTDDIND=CEL L_FDD,ROOTSEQUENCEIDX=0,EMERGENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,TXR XMODE=2T4R; ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0; ACT CELL:LOCALCELLID=0; NOTE

The preceding parameter values serve as examples only. Unless otherwise stated, default values are recommended.

7.4.6 Activation Observation LBFD-00202001 UL 2-Antenna Receive Diversity The observation procedure is as follows: Step 1 On the U2000 client, choose Monitor > Signaling Trace > Signaling Trace Management. Step 2 In the navigation tree of the Signaling Trace Management window, choose Trace Type > LTE > Cell Performance Monitoring and then double-click RSSI Statistic Monitoring. Step 3 In the displayed dialog box, select an eNodeB and set the local cell ID of the cell to be traced. Then, click Finish to start a tracing task. Step 4 Observe the real-time values of antenna 0 RSSI(dBm) and antenna 1 RSSI(dBm). If neither of the values is N/A, two receive antennas have been configured and this feature has been activated. ----End

LOFD-001005 UL 4-Antenna Receive Diversity The observation procedure is as follows: Step 1 On the U2000 client, choose Monitor > Signaling Trace > Signaling Trace Management. Step 2 In the navigation tree of the Signaling Trace Management window, choose Trace Type > LTE > Cell Performance Monitoring and then double-click RSSI Statistic Monitoring. Step 3 In the displayed dialog box, select an eNodeB and set the local cell ID of the cell to be traced. Then, click Finish to start a tracing task. Step 4 Observe the real-time values of antenna 0 RSSI(dBm), antenna 1 RSSI(dBm), antenna 2 RSSI(dBm), and antenna 3 RSSI(dBm). If none of the values is N/A, four receive antennas have been configured and this feature has been activated. ----End

Issue 04 (2015-08-31)


85



7.4.7 Reconfiguration An integrated 4T4R RRU can work in 4T2R mode to temporarily mitigate intermodulation interference. However, this mode is not recommended because uplink coverage and downlink throughput in this mode are not as high as those in 4T4R mode. For details about how to adjust the working mode of an integrated 4T4R RRU to 4T2R, see Cell Management Feature Parameter Description.

7.4.8 Deactivation 7.4.8.1 Using the CME to Perform Batch Configuration Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in 7.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to the following table. Table 7-3 Parameters related to multiple-antenna receive diversity MO


Parameter Group

Setting Notes

SECTOR EQM

eNodeB Radio Data

SECTOREQMID, OPMODE, ANTNUM, ANT1CN, ANT1SRN, ANT1SN, ANT1N

User-defined sheet The following parameter settings are only for reference. For details about parameter settings, see 7.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs. SECTOREQMID: 0 OPMODE: DELETE ANTNUM: 1 ANT1CN: 0 ANT1SRN: 60 ANT1SN: 0 ANT1N: R0B

Cell

eNodeB Radio Data


User-defined sheet The following parameter settings are only for reference. For details about parameter settings, see 7.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs. LocalCellId: 0 TxRxMode: 1T1R

Issue 04 (2015-08-31)


86



7.4.8.2 Using the CME to Perform Single Configuration On the CME, set parameters according to 7.4.8.1 Using the CME to Perform Batch Configuration. For detailed instructions, see 7.4.5.3 Using the CME to Perform Single Configuration described for feature activation.

7.4.8.3 Using MML Commands LBFD-00202001 UL 2-Antenna Receive Diversity If this feature is activated according to the instructions in 7.4.5.4 Using MML Commands, you can run the following commands to deactivate it: Example: DEA CELL: LocalCellId=0; MOD SECTOREQM: SECTOREQMID=0, OPMODE=DELETE, ANTNUM=1, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0B; MOD CELL: LocalCellId=0, TxRxMode=1T1R; ACT CELL: LocalCellId=0;

LOFD-001005 UL 4-Antenna Receive Diversity If this feature is activated according to the instructions in 7.4.5.4 Using MML Commands, you can run the following commands to deactivate it: Example: If the baseband unit (BBU) and integrated RRUs are connected as described in 7.4.4 Hardware Adjustment, run the following commands: DEA CELL: LocalCellId=0; MOD SECTOREQM: SECTOREQMID=0, OPMODE=DELETE, ANTNUM=3, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0B, ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0C, ANT3CN=0, ANT3SRN=60, ANT3SN=0, ANT3N=R0D; MOD CELL: LocalCellId=0, TxRxMode=1T1R; ACT CELL: LocalCellId=0;

If the BBU and combined RRUs are connected as described in 7.4.4 Hardware Adjustment, run the following commands: DEA CELL: LocalCellId=0; MOD SECTOREQM: SECTOREQMID=0, OPMODE=DELETE, ANTNUM=3, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0B, ANT2CN=0, ANT2SRN=61, ANT2SN=0, ANT2N=R0A, ANT3CN=0, ANT3SRN=61, ANT3SN=0, ANT3N=R0B; MOD CELL: LocalCellId=0, TxRxMode=1T1R; ACT CELL: LocalCellId=0;

LOFD-001005 UL 4-Antenna Receive Diversity For micro eNodeBs, if this feature is activated according to the instructions in 7.4.5.4 Using MML Commands, you can run the following commands to deactivate it: Example: DEA CELL: LocalCellId=0; MOD SECTOREQM:SECTOREQMID=0, OPMODE=DELETE, ANTNUM=3, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0B, ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0C, ANT3CN=0,

Issue 04 (2015-08-31)


87



ANT3SRN=60, ANT3SN=0, ANT3N=R0D; MOD CELL:LocalCellId=0; TxRxMode=1T1R; ACT CELL: LocalCellId=0;

7.5 Maintenance 7.5.1 Performance Monitoring LBFD-00202001 UL 2-Antenna Receive Diversity Check the received signal strength indicator (RSSI) values of the two antennas in the cell performance tracing result by referring to 7.4.6 Activation Observation. If neither of the values is N/A, uplink 2-antenna receive diversity has been activated.

LOFD-001005 UL 4-Antenna Receive Diversity Check the RSSI values of the four antennas in the cell performance tracing result by referring to 7.4.6 Activation Observation. If none of the values is N/A, uplink 4-antenna receive diversity has been activated. Check the distribution of uplink MCS indexes by using counters L.ChMeas.PUSCH.MCS.N. (where N = 0 to 31). Compare the distribution when LOFD-001005 UL 4-Antenna Receive Diversity is enabled and the distribution when LBFD-00202001 UL 2-Antenna Receive Diversity is enabled. Note that measurements must be performed under the same conditions (for example, the same cell bandwidth and UE transmit power). You can observe that the uplink MCS improves after LOFD-001005 UL 4Antenna Receive Diversity is enabled. In addition, check the uplink throughput by performing drive tests; you can observe that the uplink throughput increases. NOTE

l In uplink 4-antenna receive diversity, if the receive power of two pairs of antennas is imbalanced due to interference or feeder length difference, the gains of four-antenna receive diversity (compared with two-antenna receive diversity) are affected. l If the difference in downtilt angle is less than 2 degrees, the average performance of uplink 4antenna receive diversity deteriorates by less than 3% and the cell edge performance by less than 10%. If the difference in downtilt angle is between 3 and 4 degrees, the average performance deteriorates by 5% and the cell edge performance by 20%. l If the L.Traffic.User.Avg counter value increases, 4-antenna receive diversity provides a wider coverage area than 2-antenna receive diversity and therefore serves more users. In this situation, the average uplink MCS and throughput performance may slightly improve or even deteriorate. For details, see 6.2 LOFD-001005 UL 4-Antenna Receive Diversity.

7.5.2 Parameter Optimization N/A

7.5.3 Troubleshooting Fault Description LBFD-00202001 UL 2-Antenna Receive Diversity fails to be activated when two receive antennas are configured. Issue 04 (2015-08-31)


88



Fault Handling Step 1 On the U2000 client, choose Monitor > Signaling Trace > Signaling Trace Management. Step 2 In the navigation tree of the Signaling Trace Management window, choose Trace Type > LTE > Cell Performance Monitoring > Interference Detect Monitoring. Step 3 Check the value of antenna 0 RSSI(dBm) and antenna 1 RSSI(dBm). If either of the values is N/A, run the LST CELL command to check the Cell transmission and reception mode parameter to see whether the RX mode is 2R. If not, reconfigure the RX mode. Step 4 If the fault persists, contact Huawei technical support. ----End

Fault Description LBFD-00202001 UL 4-Antenna Receive Diversity fails to be activated when four receive antennas are configured.

Fault Handling Step 1 On the U2000 client, run the DSP LICINFO command to check whether the license control item LLT1U4ARD01 is valid. If it is invalid, load a valid license file for this item. Step 2 On the U2000 client, choose Monitor > Signaling Trace > Signaling Trace Management. Step 3 In the navigation tree of the Signaling Trace Management window, choose Trace Type > LTE > Cell Performance Monitoring > Interference Detect Monitoring. Step 4 Check the values of antenna 0 RSSI(dBm), antenna 1 RSSI(dBm), antenna 2 RSSI(dBm), and antenna 3 RSSI(dBm). If one of the values is N/A, run the LST CELL command to check the Cell transmission and reception mode parameter to see whether the RX mode is 4R. If not, reconfigure the RX mode. Step 5 If the fault persists, contact Huawei technical support. ----End

Issue 04 (2015-08-31)


89


8

8 Engineering Guidelines for MU-MIMO

Engineering Guidelines for MU-MIMO

8.1 When to Use MU-MIMO MU-MIMO is used to improve uplink capacity. The features LOFD-001002 UL 2x2 MUMIMO and LOFD-001058 UL 2x4 MU-MIMO are not recommended in high speed mobility or ultra high-speed movement scenarios to ensure the system stability. If there is strong interference between neighboring cells, LOFD-001002 UL 2x2 MU-MIMO is not recommended because it is difficult for the eNodeB to use only two receive antennas to mitigate inter-cell interference. It is recommended that LOFD-001002 UL 2x2 MU-MIMO and LOFD-001096 Advanced Receiver (PSIC) be used together to improve network performance. For micro eNodeBs, MU-MIMO is used to improve uplink capacity. The LOFD-001058 UL 2x4 MU-MIMO feature is not recommended in high-speed or ultra-high-speed movement scenarios to ensure the system stability.

8.2 Required Information N/A

8.3 Planning RF Planning N/A

Network Planning N/A

Hardware Planning MU-MIMO has the same hardware planning requirements as multiple-antenna receive diversity. For details, see 7.3 Planning. Issue 04 (2015-08-31)


90



8.4 Deployment of MU-MIMO 8.4.1 Requirements Required Features LOFD-001002 UL 2x2 MU-MIMO requires that LOFD-00101502 Dynamic Scheduling be enabled. LOFD-001058 UL 2x4 MU-MIMO requires that LOFD-00101502 Dynamic Scheduling and LOFD-001005 UL 4-Antenna Receive Diversity be enabled.

Operating Environment LOFD-001002 UL 2x2 MU-MIMO requires that the eNodeB have a minimum of two receive channels and two antennas. LOFD-001058 UL 2x4 MU-MIMO requires that the eNodeB have a minimum of four receive channels and four antennas.

License If more than two receive channels are used, the operator has purchased the license for the items listed in the following table in addition to a feature license. Without the license, cells cannot be activated. For details about the license control items, see License Management Feature Parameter Description. License Control Item Name


BB Receive Channel(FDD)

LT1S00BBRC00

RF Receive Channel(FDD)

LT1S00RFRC00

LOFD-001002 UL 2x2 MU-MIMO The operator has purchased the feature license. No hardware license is required. l

l

Feature license Feature ID

Feature Name

Model


NE

Sales Unit

LOFD-0 01002

UL 2x2 MUMIMO

LT1S0U2I2 O00

UL 2x2 MUMIMO (FDD)

eNodeB

per Cell

Hardware license

No additional hardware license is required because each BBP and RF unit in a cell are equipped with two baseband receive channels and two RF receive channels, respectively. LOFD-001058 UL 2x4 MU-MIMO Issue 04 (2015-08-31)


91



The operator has purchased the feature license and hardware license. l

l


Feature Name

Model


NE

Sales Unit

LOFD-00105 8

UL 2x4 MUMIMO

LT1S0U MIMO00

UL 2x4 MUMIMO (FDD)

eNode B

per Cell

Hardware license The operator has purchased the licenses for two baseband receive channels and two RF receive channels.

8.4.2 Data Preparation This section describes the data that you need to collect for setting parameters. Required data is data that you must collect for all scenarios. Collect scenario-specific data when necessary for a specific feature deployment scenario. There are three types of data sources: l

Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment

l


l


Required Data N/A

Scenario-specific Data The following table describes the parameters that must be set in the CellAlgoSwitch MO to configure uplink MU-MIMO for a cell.

Issue 04 (2015-08-31)

Parameter Name

Parameter ID

Data Source

Setting Notes

Local cell ID

CellAlgoSwit ch.LocalCellI d


This parameter specifies a local cell ID. Set this parameter in the Cell MO.

Uplink schedule switch

CellAlgoSwit ch.UlSchSwit ch


The UlVmimoSwitch(UlVmimoSwitch) option of this parameter specifies whether to enable or disable uplink MU-MIMO.


92



The following table describes the parameters that must be set in the SRSCfg MO to configure SRS-related parameters. Parameter Name

Parameter ID

Data Source

Setting Notes

Local cell ID

SRSCfg.Loca lCellId



SRS Configuration Indicator

SRSCfg.SrsC fgInd


This parameter specifies an SRS configuration indicator. If this parameter is set to BOOLEAN_FALSE(False), the cell does not configure SRS resources for its UEs. If this parameter is set to BOOLEAN_TRUE(True), the cell configures SRS resources for its UEs. For MU-MIMO, set the SRSCfg.SrsCfgInd parameter to BOOLEAN_TRUE(True).

FDD SRS Configuration Mode

SRSCfg.FddS rsCfgMode


This parameter specifies an FDD SRS resource configuration mode. Set this parameter when the SRSCfg.SrsCfgInd parameter is set to BOOLEAN_TRUE(True). l If the SRSCfg.FddSrsCfgMode parameter is set to DEFAULTMODE(Default Mode), the cell configures SRS resources for its UEs by default after the cell is set up l If the SRSCfg.FddSrsCfgMode parameter is set to ADAPTIVEMODE(Adaptive Mode), the cell adaptively configures SRS resources for its UEs based on its load. For MU-MIMO, set the SRSCfg.FddSrsCfgMode parameter to DEFAULTMODE(Default Mode).

8.4.3 Precautions Before enabling MU-MIMO, ensure that the SRSCfg.SrsCfgInd parameter has been set to BOOLEAN_TRUE(True) and the SRSCfg.FddSrsCfgMode parameter has been set to DEFAULTMODE(Default Mode). Issue 04 (2015-08-31)


93



To prevent uplink performance deterioration, LOFD-001002 UL 2x2 MU-MIMO requires that the antennas to which the receive channels are connected have different polarization directions, regardless of whether an integrated antenna system with multiple ports is used or two antennas each with two ports are combined to serve a cell. If two antennas each with two ports are combined to serve a cell, LOFD-001058 UL 2x4 MUMIMO requires that all of the conditions be met: l

The antennas have the same azimuth and downtilt angle.

l

The feeders between the antennas and RRUs have the same type and loss. The feeders have the same length or have a difference in length less than 1 meter.

If these conditions are not met, uplink performance deteriorates. NOTE

If the difference in downtilt angle is less than 2 degrees, the average performance of uplink 4-antenna receive diversity deteriorates by less than 3% and the cell edge performance by less than 10%. If the difference in downtilt angle is between 3 and 4 degrees, the average performance deteriorates by 5% and the cell edge performance by 20%.

8.4.4 Hardware Adjustment Uplink multiple-antenna receive diversity, uplink MU-MIMO, and downlink MIMO share the same RRU and antenna system and use the same networking mode. For details about hardware adjustment for LOFD-001002 UL 2x2 MU-MIMO, see the following sections in 9.4.4 Hardware Adjustment: l

1T2R Cell

l


l

2T2R Cell (Combined RRUs)

For details about hardware adjustment for LOFD-001058 UL 2x4 MU-MIMO, see the following sections in 9.4.4 Hardware Adjustment: l


l


l


l


l


l


l


8.4.5 Initial Configuration 8.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs Enter the values of the parameters listed in the following table in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the summary data file into the CME for batch configuration. For detailed instructions, see "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB, which is available in the eNodeB product documentation. Issue 04 (2015-08-31)


94



The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions: l

The MOs in the following table are contained in a scenario-specific summary data file. In this situation, set the parameters in the MOs, and then verify and save the file.

l


Table 8-1 Parameters related to MU-MIMO MO


Parameter Group

Remarks

CellAlgoSwitch

User-defined sheet

LocalCellId, UlSchSwitch

User-defined sheet

SRSCfg

User-defined sheet

LocalCellId, SrsCfgInd

User-defined sheet

8.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure is as follows: Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs." For online help, press F1 when a CME window is active, and select Managing the CME > CME Guidelines > LTE Application Management > eNodeB Related Operations > Customizing a Summary Data File for Batch eNodeB Configuration. Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME into the customized summary data file. Step 3 In the summary data file, set the parameters in the MOs according to the setting notes provided in section "Data Preparation" and close the file. Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME, and then start the data verification. Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. For detailed operations, see Managing the CME > CME Guidelines > Script File Management > Exporting Incremental Scripts from a Planned Data Area in the CME online help. ----End Issue 04 (2015-08-31)


95



8.4.5.3 Using the CME to Perform Single Configuration On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The procedure is as follows: Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window. Step 2 In area 1 shown in Figure 8-1, select the eNodeB to which the MOs belong. Figure 8-1 MO search and configuration window

Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL. Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are displayed in area 4. Step 5 Set the parameters in area 4 or 5. Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. ----End

8.4.5.4 Using MML Commands Step 1 (Optional) Run the MOD SRSCFG command to enable SRS resource configuration and set the FDD SRS resource configuration mode. Example: MOD SRSCFG: LocalCellId=0, SrsCfgInd=BOOLEAN_TRUE, FddSrsCfgMode=DEFAULTMODE;

Step 2 Run the MOD CELLALGOSWITCH command to enable uplink MU-MIMO. Example: Issue 04 (2015-08-31)


96



MOD CELLALGOSWITCH:LOCALCELLID=0,ULSCHSWITCH=UlVmimoSwitch-1;

----End

8.4.6 Activation Observation Step 1 On the U2000 client, choose Monitor > Signaling Trace > Signaling Trace Management. Step 2 In the navigation tree of the Signaling Trace Management window, choose Trace Type > LTE > Cell Performance Monitoring > Multi User-MIMO Monitoring. Step 3 Enable multiple UEs to access the network. Ensure that the reference signal received power (RSRP) values of the UEs range from -100 dBm to -75 dBm. Then, perform uplink FTP services on the UEs. Step 4 On the U2000 client, check the value in the Mimo UE Pair Num column. If the value is greater than 0, uplink MU-MIMO is activated on the eNodeB. NOTE

l For macro eNodeBs, you are advised to set the cell bandwidth to 5 MHz, set the TX/RX mode to 2T2R or 2T4R, and ensure that the number of UEs is greater than 5 so that UE pairing can be easily observed. l For micro eNodeBs, you are advised to set the cell bandwidth to 5 MHz, set the TX/RX mode to 4T4R or 2T4R, and ensure that the number of UEs is greater than 5 so that UE pairing can be easily observed.

----End

8.4.7 Reconfiguration N/A

8.4.8 Deactivation 8.4.8.1 Using the CME to Perform Batch Configuration Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in 8.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to Table 8-2. Table 8-2 Parameters related to MU-MIMO MO


Parameter Group

Setting Notes

CellAlgoSwitch

User-defined sheet

LocalCellId, UlSchSwitch

User-defined sheet The following is an example: LocalCellId: 0 UlSchSwitch: UlVmimoSwitch:Off

Issue 04 (2015-08-31)


97




8.4.8.3 Using MML Commands Run the MOD CELLALGOSWITCH command to deactivate MU-MIMO. Example: MOD CELLALGOSWITCH:LOCALCELLID=0,ULSCHSWITCH=UlVmimoSwitch-0;

8.5 Maintenance 8.5.1 Performance Monitoring After MU-MIMO is enabled, perform the following operations to monitor its performance: 1.

On the U2000 client, choose Monitor > Signaling Trace > Signaling Trace Management.

2.

In the navigation tree of the Signaling Trace Management window, choose Trace Type > LTE > Cell Performance Monitoring > Multi User-MIMO Monitoring.

3.

Check the value of Mimo UE Pair Num. –

If the value does not always equal 0, MU-MIMO has taken effect.

–

If the value always equals 0, rectify the fault by following the instructions described in 8.5.3 Troubleshooting.

You can also monitor the performance of MU-MIMO by checking the values of the following counters: l

1526728349 L.ChMeas.VMIMO.PairPRB.Succ

l

1526728350 L.ChMeas.VMIMO.PairPRB.Tot

If the values of both the counters always equal 0, rectify the fault by following the instructions described in 8.5.3 Troubleshooting. Otherwise, MU-MIMO has taken effect.

8.5.2 Parameter Optimization N/A

8.5.3 Troubleshooting Fault Description The MU-MIMO feature fails to be activated.

Issue 04 (2015-08-31)


98



Fault Handling Step 1 Run the DSP LICINFO command on the U2000 client and check whether the license control item LLT1UMIMO01 or LLT1UMIMO02 is valid. If it is invalid, load a valid license file for this item. Step 2 On the U2000 client, choose Monitor > Signaling Trace > Signaling Trace Management. Step 3 In the navigation tree of the Signaling Trace Management window, choose Trace Type > LTE > Cell Performance Monitoring > Users Statistic Monitoring. Then, check the value of General Users Number. l

If less than five UEs access the network, there is a low probability that UEs can be paired, and accordingly MU-MIMO fails to be activated. Therefore, it is recommended that the number of UEs be greater than 5.

l

If there are enough UEs for pairing, go to Step 4. The specific number of UEs depends on other conditions such as bandwidth.

Step 4 In the navigation tree of the Signaling Trace Management window, choose User Performance Monitoring > Quality of Channel Monitoring and check the SINR. There is a low probability that UEs can be paired if the SINR is less than 1 dB, and accordingly MU-MIMO fails to be activated. Therefore, use this feature in scenarios where the SINR is high. Step 5 If the fault persists, contact Huawei technical support. ----End

Issue 04 (2015-08-31)


99


9

9 Engineering Guidelines for Multiple-Antenna Transmission

Engineering Guidelines for MultipleAntenna Transmission

9.1 When to Use Multiple-Antenna Transmission Before deploying multiple-antenna transmission, the operator must consider the compatibility of different UEs with multiple-antenna transmission of the eNodeB and the impact of these UEs on network performance after the deployment.

LOFD-001001 DL 2x2 MIMO LOFD-001001 DL 2x2 MIMO can be used when the following conditions are met: l

On the network side The eNodeB meets 2-antenna transmission requirements described in 9.4.1 Requirements, and the operator has obtained the license. When the eNodeB has four antennas, it can use 4T2P to implement downlink 2x2 MIMO.

l

On the UE side UEs have two receive antennas and can work with the eNodeB that uses two antenna ports for transmission. When the penetration rate of TM9 UEs is high (for example, 20%) in a multi-RRU cell (now a cell can be served by at most two RRUs), it is recommended that downlink 2x2 MIMO in TM9 be deployed together with LOFD-070205 Adaptive SFN/SDMA. The penetration rate is equal to L.Traffic.User.TM9.Avg/L.Traffic.User.Avg.

LOFD-001003 DL 4x2 MIMO LOFD-001003 DL 4x2 MIMO, which improves downlink capacity and coverage, can be used when the following conditions are met: l

On the network side The eNodeB meets 4-antenna transmission requirements described in 9.4.1 Requirements, and the operator has obtained the license.

Issue 04 (2015-08-31)


100


l


On the UE side UEs have two receive antennas and can work with the eNodeB that uses four antenna ports for transmission. To support downlink 4x2 MIMO in TM9, UEs must support TM9, have two receive antennas, and be able to work with the eNodeB that uses four antenna ports for transmission. When the penetration rate of TM9 UEs in a cell is high (for example, 20%), it is recommended that downlink 4x2 MIMO in TM9 be deployed. Downlink 4x2 MIMO in TM9 is a trial function. The penetration rate is equal to L.Traffic.User.TM9.Avg/L.Traffic.User.Avg. NOTE

If some UEs cannot work with the eNodeB that uses four antenna ports for transmission, it is not recommended that downlink 4x2 MIMO be activated. The reason is that the performance of these UEs will deteriorate sharply and some of them even cannot access the network. If all UEs can work with the eNodeB that uses four antenna ports for transmission and some UEs can use four antennas for reception, it is recommended that downlink 4x2 MIMO be activated together with downlink 4x4 MIMO. It is not recommended that downlink 4x2 MIMO be activated individually. The reason is that downlink 4x2 MIMO in open-loop mode has negative impacts in most cases and downlink 4x2 MIMO in closedloop mode has limited gains because the reference signal overhead increases, compared with downlink 2x2 MIMO and provided that the total transmit power remains unchanged.

LOFD-001060 DL 4x4 MIMO LOFD-001060 DL 4x4 MIMO, which improves downlink capacity and coverage, can be used when the following conditions are met: l

On the network side The eNodeB meets 4-antenna transmission requirements described in 9.4.1 Requirements, and the operator has obtained the license.

l

On the UE side UEs have four receive antennas and can work with the eNodeB that uses four antenna ports for transmission. TM9 UEs have four receive antennas and can work with the eNodeB that uses four antenna ports for transmission. When the penetration rate of TM9 UEs is high (for example, 20%), it is recommended that downlink 4x4 MIMO in TM9 be deployed. Downlink 4x4 MIMO in TM9 is a trial function. The penetration rate is equal to L.Traffic.User.TM9.Avg/L.Traffic.User.Avg. NOTE

If all UEs can work with the eNodeB that uses four antenna ports for transmission and some UEs can use four antennas for reception, it is recommended that downlink 4x2 MIMO be activated together with downlink 4x4 MIMO. It is not recommended that downlink 4x2 MIMO be activated individually. The reason is that downlink 4x2 MIMO in open-loop mode has negative impacts in most cases and downlink 4x2 MIMO in closedloop mode has limited gains because the reference signal overhead increases, compared with downlink 2x2 MIMO and provided that the total transmit power remains unchanged.

9.2 Required Information Network information needs to be collected before deploying multiple-antenna transmission. Issue 04 (2015-08-31)


101



Coverage Area l

Coverage area type: dense urban areas, urban areas, suburban districts, rural areas, or highways

l

Service types and their coverage requirements

l

User quantity and user distribution

l

KPI requirements, especially for the average cell throughput and cell-edge throughput in the downlink

Frequency Band l

LTE frequency band owned by the operator

l

Adjacent frequency bands and frequency band distribution of other wireless communications systems in the area, which are used to analyze interference from other frequencies

Map Whether a digital map of the coverage area is available for system performance simulation needs to be verified.

GSM/UMTS Network Information RF parameters of the existing GSM/UMTS networks are necessary because reusing the existing GSM/UMTS sites helps operators who have deployed GSM/UMTS networks to reduce the cost of deploying LTE networks.

Antenna The following information needs to be collected: l

Antenna model

l

Number of ports

l

Manufacturer

l

Electrical specifications, including the operating frequency band, polarization, gains, horizontal and vertical beamwidths, tilt, sidelobe suppression, front-to-back ratio, and isolation between ports

l

Mechanical specifications, including the antenna size, weight, wind load, and connector

l

Antenna radiation pattern

If a new antenna is to be added, check whether space is sufficient and whether the space meets the requirements for installing the antenna. If an old antenna is to be replaced with a new one, check whether the installation conditions are fulfilled for the new antenna.

Feeder Information about the feeder type and loss

Coupler Information about the coupler type and specifications such as delay and insertion loss Issue 04 (2015-08-31)


102



UE l

UE capabilities related to multiple-antenna transmission of the eNodeB

l

Penetration rate of TM9 UEs if TM9 is to be used

9.3 Planning RF Planning Estimate the downlink budget and capacity based on the information collected by referring to 9.2 Required Information and then complete RF planning.

Network Planning For macro eNodeBs, see 9.4.4 Hardware Adjustment for details about networking for multiple-antenna transmission.

Hardware Planning l

l

l

LOFD-001001 DL 2x2 MIMO –

An integrated 2T2R or 2T4R RRU

–

An LBBPd or UBBPd for downlink 2x2 MIMO in TM9

–

An integrated 4T4R RRU that uses 4T2P to support downlink 2x2 MIMO in openloop mode and closed-loop mode.

–

RRUs that are combined to support 4T4R and use 4T2P to support downlink 2x2 MIMO in open-loop mode.

LOFD-001003 DL 4x2 MIMO and LOFD-001060 DL 4x4 MIMO –

An integrated 4T4R RRU

–

An LBBPd or UBBPd

–

A 4-port antenna

LampSite eNodeBs support the deployment of downlink 2x2 MIMO in TM9. NOTE

l The LBBPd1, LBBPd3, and UBBPd3 do not support LOFD-001003 DL 4x2 MIMO or LOFD-001060 DL 4x4 MIMO. l In addition to an integrated 2T2R RRU, two RRUs can be combined to support LOFD-001001 DL 2x2 MIMO. l In addition to an integrated antenna system with four or more ports, two antennas each with two ports can be combined to support LOFD-001003 DL 4x2 MIMO and LOFD-001060 DL 4x4 MIMO.

Table 9-1 describes the mapping between CPRI rates and the maximum numbers of cells supported by different bandwidths and antenna configurations.

Issue 04 (2015-08-31)


103



Table 9-1 CPRI rates and the maximum numbers of cells supported by different bandwidths and antenna configurations CPRI Rate

Maximum Number of Cells Supported in 2-Antenna Transmission

Maximum Number of Cells Supported in 4-Antenna Transmission

1.25 Gbit/s

One cell when the bandwidth is equal to or less than 10 MHz

Not supported.

2.5 Gbit/s

l Two cells when the bandwidth is equal to or less than 10 MHz

One cell when the bandwidth is equal to or less than 10 MHz

l One cell when the bandwidth is 15 or 20 MHz 4.9 Gbit/s

l Four cells when the bandwidth is equal to or less than 10 MHz l Two cells when the bandwidth is 15 or 20 MHz

l Two cells when the bandwidth is equal to or less than 10 MHz l One cell when the bandwidth is 15 or 20 MHz

9.4 Deploying Multiple-Antenna Transmission 9.4.1 Requirements Operating Environment l

LOFD-001001 DL 2x2 MIMO The eNodeB provides at least two transmit channels and two antennas.

l

LOFD-001003 DL 4x2 MIMO and LOFD-001060 DL 4x4 MIMO The eNodeB provides at least four transmit channels and four antennas.

License If more than two transmit channels are used, the operator has purchased the license for the items listed in the following table in addition to a feature license. Without the license, cells cannot be activated. For details about how to activate a license, see License Management Feature Parameter Description. License Control Item Name


BB Transmit Channel(FDD)

LT1S00BBTC00

RF Transmit Channel(FDD)

LT1S00RFTC00

LOFD-001001 DL 2x2 MIMO The operator has purchased the feature license. No hardware license is required. Issue 04 (2015-08-31)


104



l

l


Feature Name

Model


NE

Sales Unit

LOFD-001 001

DL 2x2 MIMO

LT1S0D2I2 O00

DL 2x2 MIMO(FDD)

eNode B

per Cell

Hardware license

For 2T2R cells, no additional hardware license is required because each BBP and RF are equipped with two baseband transmit channels and two RF transmit channels for each cell, respectively. For 4T4R cells, the operator has purchased the license for another two baseband transmit channels and two RF transmit channels for each cell. LOFD-001003 DL 4x2 MIMO The operator has purchased the feature license and hardware license. l

l


Feature Name

Model


NE

Sales Unit

LOFD-00100 3

DL 4x2 MIMO

LT1S0D4 I2O00

DL 4x2 MIMO(FDD)

eNode B

per Cell

Hardware license The operator has purchased the licenses for two baseband transmit channels and two RF transmit channels for each cell.

LOFD-001060 DL 4x4 MIMO The operator has purchased the feature license and hardware license. l

l


Feature Name

Model


NE

Sales Unit

LOFD-001 060

DL 4x4 MIMO

LT1S0D MIMO00

DL 4x4 MIMO(FDD)

eNodeB

per Cell

Hardware license The operator has purchased the licenses for two baseband transmit channels and two RF transmit channels for each cell.

9.4.2 Data Preparation This section describes the data that you need to collect for setting parameters. Required data is data that you must collect for all scenarios. Collect scenario-specific data when necessary for a specific feature deployment scenario. Issue 04 (2015-08-31)


105



There are three types of data sources: l

Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment

l


l


Required Data The following table describes the parameters that must be set in a SECTOR MO to configure a sector. For details, see Cell Management Feature Parameter Description. Parameter Name

Parameter ID

Data Source

Setting Notes

Sector ID

SECTOR.SE CTORID



Antenna Number

SECTOR.AN TNUM




SECTOR.AN T1CN




SECTOR.AN T1SRN




SECTOR.AN T1SN




SECTOR.AN T1N



Create Default Sector Equipment

SECTOR.CR EATESECTO REQM



Default Sector Equipment ID

SECTOR.SE CTOREQMI D



The following table describes the parameters that must be set in a SECTOREQM MO to configure a set of sector equipment.

Issue 04 (2015-08-31)


106



Issue 04 (2015-08-31)

Parameter Name

Parameter ID

Data Source

Setting Notes

Sector Equipment ID

SECTOREQM.SECT OREQMID



Sector ID

SECTOREQM.SECT ORID



Antenna Number

SECTOREQM.ANTN UM




SECTOREQM.ANT1 CN




SECTOREQM.ANT1 SRN




SECTOREQM.ANT1 SN




SECTOREQM.ANT1 N



Antenna 1 RX/TX Mode

SECTOREQM.ANTT YPE1




107


eRAN MIMO Feature Parameter Description NOTE

The preceding tables use one antenna (antenna 1) as an example. Actually, you can configure n antennas: l When the SECTOR.ANTNUM or SECTOREQM. ANTNUM parameter is set to 2, n can be 1 or 2. l When the SECTOR.ANTNUM or SECTOREQM. ANTNUM parameter is set to 4, n can be 1, 2, 3, or 4.

The following table describes the parameters that must be set in an eUCellSectorEqm MO to bind a set of sector equipment to a cell. Parameter Name

Parameter ID

Data Source

Setting Notes

Local cell ID

eUCellSectorEqm. LocalCellId



Sector Equipment ID

eUCellSectorEqm. SectorEqmId



Scenario-specific Data For LOFD-001001 DL 2x2 MIMO, LOFD-001003 DL 4x2 MIMO, and LOFD-001060 DL 4x4 MIMO, the scenario-specific data is prepared as follows. The following table describes the parameters that must be set in a Cell MO to configure a cell and CRS port mapping. Parameter Name

Parameter ID

Data Source

Setting Notes

Local cell ID

Cell.Local CellId



Cell transmission and reception mode

Cell.TxRx Mode


Set this parameter based on the network plan. For LOFD-001001 DL 2x2 MIMO, set this parameter to 2T2R or 2T4R based on the number of receive antennas. For LOFD-001003 DL 4x2 MIMO and LOFD-001060 DL 4x4 MIMO, set this parameter to 4T4R.

CRS Port Number

Issue 04 (2015-08-31)

Cell.CrsPor tNum


If the TM9 switch is turned on in FDD mode, it is recommended that two CRS ports be used. If the TM9 switch is turned off in FDD mode, it is recommended that the number of CRS ports be equal to the number of physical antennas for transmission.


108



Parameter Name

Parameter ID

Data Source

Setting Notes

CRS Antenna Port Mapping

Cell.CrsPor tMap


This parameter can be set for a 4T4R cell, but cannot be set for a 2T2R or 2T4R cell. If an integrated 4T4R RRU is used for LOFD-001003 DL 4x2 MIMO and LOFD-001060 DL 4x4 MIMO, it is recommended that this parameter be set to 4T4P_0321(4T4P_0321). If 2T2R or 2T4R RRUs are combined and feeders are installed in non-crossconnection mode for LOFD-001003 DL 4x2 MIMO and LOFD-001060 DL 4x4 MIMO, it is recommended that this parameter be set to 4T4P_0213(4T4P_0213). l If an integrated RRU or two combined RRUs are used for downlink 4x2 MIMO in TM9, it is recommended that this parameter be set to 4T2P_0011.

The following table describes the parameters that must be set in the CellCsiRsParaCfg MO to configure CSI-RS reporting. Parameter Name

Parameter ID

Data Source

Setting Notes

Local cell ID

CellCsiRs ParaCfg.L ocalCellId



CSI-RS Switch

CellCsiRs ParaCfg.C siRsSwitch


If downlink 2x2 MIMO in TM9 or downlink 4x2 MIMO in TM9 [Trial] are used, then: l If the TM9 switch is turned on, you are advised to set this parameter to FIXED_CFG( Fixed configure). If adaptive configuration is required, set this parameter to ADAPTIVE_CFG(ADAPTIVE_CF G). l If the TM9 switch is turned off, set this parameter to NOT_CFG(Not configure).

Issue 04 (2015-08-31)


109



Parameter Name

Parameter ID

Data Source

Setting Notes

CSI-RS Period

CellCsiRs ParaCfg.C siRsPeriod


If downlink 2x2 MIMO in TM9 or downlink 4x2 MIMO in TM9 are used, it is recommended that this parameter be set to ms5(ms5).

CSI-RS Config User Number Threshold

CellCsiRs ParaCfg.C siRsConfig UserNumT h


This parameter specifies the threshold number of online CSI-RS-supporting UEs for transition from nonconfiguration of CSI-RS to configuration of CSI-RS in adaptive CSI-RS configuration mode. It is recommended that this parameter be set to 10.

CSI-RS Unconfig User Number Threshold

CELLCSI RSPARAC FG.CsiRsU nconfigUse rNumTh


This parameter specifies the threshold number of online CSI-RS-supporting UEs for transition from configuration of CSI-RS to non-configuration of CSI-RS in adaptive CSI-RS configuration mode. It is recommended that this parameter be set to 200.

CSI-RS Config User Ratio Threshold

CellCsiRs ParaCfg.C siRsConfig UserRatio Th


This parameter specifies the threshold proportion of online CSI-RS-supporting UEs for transition from nonconfiguration of CSI-RS to configuration of CSI-RS in adaptive CSI-RS configuration mode. It is recommended that this parameter be set to 30.

CSI-RS Unconfig User Ratio Threshold

CellCsiRs ParaCfg.C siRsUncon figUserRat ioTh


This parameter specifies the threshold proportion of online CSI-RS-supporting UEs for transition from configuration of CSI-RS to non-configuration of CSI-RS in adaptive CSI-RS configuration mode. It is recommended that this parameter be set to 20.

The following table describes the parameter that must be set in the CqiAdaptiveCfg MO to optimize periodic CQI reporting on the PUCCH.

Issue 04 (2015-08-31)


110



Parameter Name

Parameter ID

Data Source

Setting Notes

PUCCH Periodic CQI Optimize Switch

CqiAdaptiveC fg.PucchPerio dicCqiOptSwit ch


This parameter specifies whether to enable optimized periodic CQI reporting on the PUCCH. It is recommended that this parameter be set to ON(On) when CQI reporting period adaptation is enabled.

The following table describes the parameters that must be set in the CellCqiAdaptiveCfg MO to configure aperiodic CQI reporting for handover and adaptive CQI reporting. Parameter Name

Parameter ID

Data Source

Setting Notes

CQI Period Adaptive Switch

CellCqiAdapt iveCfg.CqiPer iodAdaptive


This parameter specifies whether to enable CQI reporting period adaptation. It is recommended that this parameter be set to ON(On).

User CQI period

CellCqiAdapt iveCfg.UserCq iPeriod


This parameter specifies a fixed CQI reporting period. When CQI reporting period adaptation is disabled, the fixed CQI reporting period is required.

Handover Aperiodic CQI Config Switch

CellCqiAdapt iveCfg.HoApe riodicCqiCfgS witch


It is recommended that this parameter be set to OFF(Off).

The following table describes the parameters that must be set in the CellMimoParaCfg MO to configure the MIMO mode of a cell.

Issue 04 (2015-08-31)

Paramet er Name

Parameter ID

Data Source

Setting Notes

eNodeB Type

Local cell ID

CellMimoPar aCfg.LocalCe llId



Macro eNodeBs


111



Paramet er Name

Parameter ID

Data Source

Setting Notes

eNodeB Type

MIMO adaptive switch

CellMimoPar aCfg.MimoA daptiveSwitch


The default value is OL_ADAPTIVE(OL_ADA PTIVE). If test results show that closed-loop MIMO has gains, set this parameter to CL_ADAPTIVE(CL_ADA PTIVE). It is not recommended that this parameter be set to OC_ADAPTIVE(OC_ADA PTIVE). For details, see 4.5.2 Adaptive Configuration of Transmission Modes.


If fixed configuration of transmission modes is required, set this parameter to NO_ADAPTIVE(NO_ADA PTIVE). Fixed MIMO mode

CellMimoPar aCfg.FixedMi moMode


This parameter takes effect only when CellMimoParaCfg.MimoAd aptiveSwitch is set to NO_ADAPTIVE(NO_ADA PTIVE).


Set this parameter by referring to 4.5.1 Fixed Configuration of Transmission Modes. Initial Mimo Type

CellMimoPar aCfg.InitialM imoType


This parameter specifies a MIMO transmission mode used during initial network access. It is recommended that this parameter be set to ADAPTIVE(ADAPTIVE).

Macro eNodeBs

The following table describes the parameters that must be set in the SRSCfg MO to configure SRS resources.

Issue 04 (2015-08-31)


112



Parameter Name

Parameter ID

Data Source

Setting Notes

Local cell ID

SRSCfg.LocalC ellId



SRS Configurati on Indicator

SRSCfg.SrsCfg Ind


Set this parameter to BOOLEAN_TRUE when the CellMimoParaCfg.MimoAdaptiveSwitch parameter is set to OC_ADAPTIVE(OC_ADAPTIVE).

FDD SRS Configurati on Mode

SRSCfg.FddSrs CfgMode


Set this parameter to DEFAULTMODE(Default Mode) when the CellMimoParaCfg.MimoAdaptiveSwitch parameter is set to OC_ADAPTIVE(OC_ADAPTIVE).

(Optional) The following table describes the parameters that must be set in the CellDlschAlgo MO to configure the maximum number of MIMO layers and downlink rank optimization. Parameter Name

Parameter ID

Data Source

Setting Notes

Local cell ID

CellDlschAlgo. LocalCellId



maximum number of MIMO layers

CellDlschAlgo. MaxMimoRan kPara


For 4x4 MIMO, set this parameter to SW_MAX_SM_RANK_4(Rank4). For 4x2 MIMO and 2x2 MIMO, set this parameter to SW_MAX_SM_RANK_2(Rank2). For details, see 4.5.1 Fixed Configuration of Transmission Modes or 4.5.2 Adaptive Configuration of Transmission Modes.

MBSFN Subframe Configurati on

Issue 04 (2015-08-31)

CellDlschAlgo. MbsfnSfCfg


This parameter controls MBSFN subframe configuration. 10 bits correspond to 10 subframes. The value 0 indicates that the subframe is not configured. The value 1 indicates that the subframe is configured. In MBSFN subframes, PDSCH services in MIMO in TM9 can be scheduled.


113



Parameter Name

Parameter ID

Data Source

Setting Notes

Downlink Rank Optimize Switch

CellDlschAlgo. DlRankOptimiz eSwitch


This parameter specifies whether to perform downlink rank optimization.

FD UE Enhanced Aperiodic CQI Trigger Period

CellDlschAlgo. FDUEEnhApe rCQITrigPerio d


This parameter specifies the period for triggering enhanced aperiodic CQI reporting. This parameter is valid when the EnAperiodicCqiRptSwitch option of the CellAlgoSwitch.DlSchSwitch parameter is selected.

It is recommended that this parameter be set to OFF(Off). For details, see 4.7.8 Downlink Rank Optimization.

Value range: 5ms, 10ms, 20ms, 40ms, 80ms, 160ms, inf (indicating enhanced aperiodic CQI reporting is not triggered.) For details, see 4.7.5 Enhanced Aperiodic CQI Reporting.

The following table describes the parameters that must be set in the CellAlgoSwitch MO to configure enhanced aperiodic CSI reporting, aperiodic CQI reporting optimization, and enhanced MIMO. Parameter Name

Parameter ID

Data Source

Setting Notes

DL schedule switch

CellAlgoSwitc h.DlSchSwitch


This parameter specifies the switches related to downlink scheduling in the cell. The switches are used to enable or disable specific downlink scheduling functions. l It is recommended that the EnAperiodicCqiRptSwitch option be deselected. For details, see 4.7.5 Enhanced Aperiodic CQI Reporting. l It is recommended that the AperiodicCqiTrigOptSwitch option be deselected. For details, see 4.7.6 Aperiodic CQI Reporting Optimization.

Enhanced MIMO Switch

Issue 04 (2015-08-31)

CellAlgoSwitc h.EnhMIMOS witch


This parameter specifies whether to turn on the TM9 switch. It is recommended that the TM9Switch option be deselected. For details, see 4.4 TM9 Transmission Mode.


114



The following table describes the parameter that must be set in the eNodeBAlgoSwitch MO to provide a workaround for UE incompatibility in aperiodic CQI reporting mode. Parameter Name

Parameter ID

Data Source

Setting Notes

Compatibility Control Switch

eNodeBAlg oSwitch.Co mpatibilityC trlSwitch


An option of this parameter is used to provide a workaround for UE incompatibility in aperiodic CQI reporting mode 3-1. When a UE in aperiodic CQI reporting mode 3-1 needs to simultaneously transmits a CQI and an ACK/NACK: l If the ApCqiAndAckAbnCtrlSwitch option is selected, the UE does not transmit the CQI on the PUSCH; instead, it transmits the CQI according to the preallocation instruction of the eNodeB. l If the ApCqiAndAckAbnCtrlSwitch option is deselected, the UE transmits the CQI on the PUSCH.

(Optional) The following table describes the parameter that must be set in the CELLDLSCHALGO MO to configure downlink rank detection. Parameter Name

Parameter ID

Data Source

Setting Notes

Downlink Rank Detect Switch

CELLDLSCH ALGO.DlRan kDetectSwitch


This parameter specifies whether to enable downlink rank detection. For details, see 4.7.9 Downlink Rank Detection. It is recommended that the DetectRank2AdjSwitch option be selected.

9.4.3 Precautions LOFD-001001 DL 2x2 MIMO requires that the antennas to which the transmit channels are connected have different polarization directions to prevent downlink performance deterioration, regardless of whether an integrated antenna system with multiple ports is used or two antennas each with two ports are combined to serve a cell. If the azimuths and downtilt angles of combined antennas may be inconsistent, it is recommended that downlink transmit channels be connected to the same physical antenna. If two antennas each with two ports are combined to serve a cell, LOFD-001003 DL 4x2 MIMO and LOFD 001060 DL 4x4 MIMO require that all of the conditions be met: Issue 04 (2015-08-31)


115



l

The antennas have the same azimuth and downtilt.

l

The spacing between the antennas meets the isolation requirement.

l

The feeders between the antennas and RRUs have the same type and loss. The feeders have the same length or have a difference in length less than 1 meter.

9.4.4 Hardware Adjustment N/A Uplink multiple-antenna receive diversity, uplink MU-MIMO, and downlink MIMO share the same RRU and antenna system and use the same networking mode. l

For details about hardware installation for downlink single-antenna transmission (TM1), see 1T2R Cell.

l

For details about hardware installation for downlink 2x2 MIMO in TM9, see the following sections:

l

l

–


–


–


–


–


–


For details about hardware installation for downlink 2x2 MIMO in TM9, see the following sections: –


–


–


For details about hardware installation for downlink 4x2 MIMO, downlink 4x4 MIMO, and downlink 4x2 MIMO in TM9, see 4T4R Cell (Integrated RRU), 4T4R Cell (2T2R +2T2R; 2T2R RRUs), and 4T4R Cell (2T2R+2T2R; 2T4R RRUs). NOTE

l For 2T4R and 4T4R cells, it is recommended that integrated antennas be used, with a spacing of less than 1 wavelength between antenna arrays. The purpose is to increase the downlink throughput of UEs with low SINR, support MIMO technique evolution, reduce the number of modules on each site, and facilitate network optimization. Also, two antennas can be combined to serve a cell. The purpose is to reuse existing antennas, increase uplink throughput, and increase the transmission rates for UEs with high SINR. l LRRU (RRU3201, RRU3203, and RRU3808) and LRFU do not support being combined to serve 2T4R cells, they can be combined to serve 4T4R cells.

1T2R Cell Figure 9-1 shows the topology for a 1T2R cell served by a 1T2R RRU. The BBU and RRU are connected through fibers, and the RRU and physical antenna are connected through feeders. In addition, a 2T2R, 2T4R, or 4T4R RRU can be used to serve a 1T2R cell. The redundant transmit or receive channels can be used for GSM, UMTS, or other LTE cells. Issue 04 (2015-08-31)


116



If an integrated 2T4R or 4T4R RRU is used, a 1T2R cell can be set up only on channels A and C or channels B and D. The cell cannot be set up on channels A and B due to hardware restrictions. Figure 9-1 Topology for a 1T2R cell

2T2R Cell (Integrated RRU) Figure 9-2 shows the topology for a 2T2R cell served by a 2T2R RRU. In addition, a 2T4R or 4T4R RRU can be used to serve a 2T2R cell. The redundant transmit or receive channels can be used for GSM, UMTS, or other LTE cells. If an integrated 2T4R RRU is used, a 2T2R cell can be set up only on channels A and B due to hardware restrictions. If an integrated 4T4R RRU is used, then due to hardware restrictions: l

It is recommended that a 2T2R cell be set up on channels A and C, channels B and D, or channels A and B, where channels A and B have the highest transmit power.

l

It is not recommended that the cell be set up on channels A and D, channels B and C, or channels C and D.

l

All channels must work in TX/RX mode.

Issue 04 (2015-08-31)


117



Figure 9-2 Topology for a 2T2R cell (integrated RRU)

2T2R Cell (Combined RRUs) Figure 9-3 shows the topology for a 2T2R cell served by combined 1T2R RRUs. Figure 9-3 Topology for a 2T2R cell (combined RRUs)

Issue 04 (2015-08-31)


118



NOTE

If combined RRUs are used or MIMO mutual aid is used to set up a 2T2R cell, it is recommended that 2x2 MIMO in open-loop (not closed-loop) mode be used. For details about MIMO mutual aid, see Cell Management Feature Parameter Description.

2T4R Cell (Integrated RRU) Figure 9-4 and Figure 9-5 show the topologies for a 2T4R cell served by a 2T4R RRU. An integrated antenna is recommended for a 4T4R cell. Two combined antennas each with two ports can also be used. If combined antennas are used, the installation must meet the requirements described in 9.4.3 Precautions. In addition to a 2T4R RRU, a 4T4R RRU can be used to serve a 2T4R cell. This requires that channels A and B work in TX/RX mode while channels C and D work in RX mode, which can be set using the ADD SECTOREQM and MOD SECTOREQM command. Figure 9-4 Topology for a 2T4R cell with an integrated antenna (integrated RRU)

Issue 04 (2015-08-31)


119



Figure 9-5 Topology for a 2T4R cell with combined antennas (integrated RRU)

NOTE

l If a 2T4R RRU and an integrated antenna are used, the feeder connection mode shown in Figure 9-5 can also be used. As the antenna arrays of an integrated antenna are spaced about one wavelength apart, the difference in performance between the two modes shown in Figure 9-4 and Figure 9-5 can be ignored. However, the non-cross-connection mode shown in Figure 9-4 is recommended to facilitate the installation. l If a 4T4R RRU is used to serve a 2T4R cell, the topologies shown in Figure 9-13 and Figure 9-14 are recommended. The reason is to facilitate upgrade from a 2T4R cell to a 4T4R cell, avoiding a second installation.

2T4R Cell (1T2R+1T2R; 1T2R RRUs) Two combined 1T2R RRUs can be used to serve a 2T4R cell. Figure 9-6 and Figure 9-7 show the topologies for a 2T4R cell served by two 1T2R RRUs. An integrated antenna is recommended for a 4T4R cell. Two combined antennas each with two ports can also be used. If combined antennas are used, the installation must meet the requirements described in 9.4.3 Precautions.

Issue 04 (2015-08-31)


120



Figure 9-6 Topology for a 2T4R cell with an integrated antenna (1T2R+1T2R; 1T2R RRUs)

Figure 9-7 Topology for a 2T4R cell with combined antennas (1T2R+1T2R; 1T2R RRUs)

2T4R Cell (1T2R+1T2R; 2T2R RRUs) Two 2T2R RRUs are combined to serve a 2T4R cell. Each RRU works in 1T2R mode. To facilitate upgrade from a 2T4R cell to a 2T2R+0T2R or 4T4R cell, it is recommended that feeders be installed in non-cross-connection mode (as shown in Figure 9-8 and Figure 9-9) to Issue 04 (2015-08-31)


121



avoid a second installation, regardless of whether an integrated antenna or combined antennas are used.

Issue 04 (2015-08-31)


122



NOTE

l If the feeder connection mode shown in Figure 9-8 is used, channel A of RRU 1 and channel B of RRU2 must work in TX/RX mode while channel B of RRU 1 and channel A of RRU 2 must work in RX mode, which can be set using the ADD SECTOREQM or MOD SECTOREQM command. If channels A of both RRUs work in TX/RX mode, see Figure 9-6 and Figure 9-7 for feeder installation. However, this mode does not facilitate upgrade to a 2T2R+0T2R or 4T4R cell. l If the horizontal distance between combined antennas is long (for example, longer than 2 m) and if the azimuths and downtilt angles of the antennas are also different, the cross-connection mode shown in Figure 9-10 can be used. This mode assumes that a second installation is permitted for upgrade to a 2T2R+0T2R or 4T4R cell. This mode results in a higher downlink throughput than that shown in Figure 9-9. The specific increase depends on the horizontal distance between the antennas, the difference between the azimuths and downtilt angles of the antennas, as well as the channel conditions. l As the antenna arrays of an integrated antenna are spaced about one wavelength apart, the difference in performance between the two modes shown in Figure 9-8 and Figure 9-10 can be ignored. However, the non-cross-connection mode shown in Figure 9-8 is recommended to facilitate the installation and future upgrade. Figure 9-8 Topology for a 2T4R cell with an integrated antenna (1T2R+1T2R; 2T2R RRUs)

Issue 04 (2015-08-31)


123



Figure 9-9 Topology for a 2T4R cell with combined antennas (1T2R+1T2R; 2T2R RRUs, supporting upgrade)

Figure 9-10 Topology for a 2T4R cell with combined antennas (1T2R+1T2R; 2T2R RRUs, not supporting upgrade)

Issue 04 (2015-08-31)


124



2T4R Cell (2T2R+0T2R; 2T2R RRUs) Two 2T2R mRFUd modules can be combined to serve a 2T4R cell, with one RF module working in 2T2R mode and the other in 0T2R mode. If an integrated antenna is used, the feeder connection mode shown in Figure 9-11 is recommended to facilitate upgrade from a 2T4R cell to a 4T4R cell, avoiding a second installation. If combined antennas are used, the feeder connection mode shown in Figure 9-12 is recommended and the installation must meet the requirements described in 9.4.3 Precautions. NOTE

2T2R+0T2R is recommended while 1T2R+1T2R is not recommended. l If combined antennas are used and the two transmit antenna ports for the 1T2R+1T2R cell are provided by two RF modules, then the downlink throughput decreases if the feeder lengths and feeder losses of the antennas are different or the azimuths or downtilt angles of the two antennas are different. l If multiple RATs share the same antenna system, enable the 0T2R RF module for LTE and the RRU for GSM/UMTS to share the same antenna system, so that the 2T2R RF module with a separate antenna system can be used only for LTE network planning and optimization.


Issue 04 (2015-08-31)


125




4T4R Cell (Integrated RRU) An integrated antenna is recommended for a 4T4R cell. Two combined antennas each with two ports can also be used. If combined antennas are used, the feeder connection mode shown in Figure 9-14 is recommended and the installation must meet the requirements described in 9.4.3 Precautions. Figure 9-13 Topology for a 4T4R cell with an integrated antenna (integrated RRU)

Issue 04 (2015-08-31)


126



Figure 9-14 Topology for a 4T4R cell with combined antennas (integrated RRU)

4T4R Cell (2T2R+2T2R; 2T2R RRUs) The transmit channels of RRUs and the antennas must be connected in non-cross-connection mode, as shown in Figure 9-15 and Figure 9-16, regardless of whether an integrated antenna or combined antennas are used. Figure 9-15 Topology for a 4T4R cell with an integrated antenna (2T2R+2T2R; 2T2R RRUs)

Issue 04 (2015-08-31)


127




4T4R Cell (2T2R+2T2R; 2T4R RRUs) The transmit channels of RRUs and the antennas must be connected in non-cross-connection mode, as shown in Figure 9-17 and Figure 9-18, regardless of whether an integrated antenna or combined antennas are used. NOTE

l If any transmit channel is faulty, roll back the TX/RX mode of the cell from 4T4R to 2T2R and then to 1T1R. That is, the TX/RX mode cannot be rolled back to 2T4R or 1T2R if the antennas are not installed again.

Issue 04 (2015-08-31)


128





9.4.5 Initial Configuration Issue 04 (2015-08-31)


129



9.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs Enter the values of the parameters listed in the following table in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the summary data file into the CME for batch configuration. For detailed instructions, see "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB, which is available in the eNodeB product documentation. The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions: l

The MOs in the following table are contained in a scenario-specific summary data file. In this situation, set the parameters in the MOs, and then verify and save the file.

l


Table 9-2 Parameters related to multiple-antenna transmission

Issue 04 (2015-08-31)

MO


Parameter Group

Remarks

SECTOR

eNodeB Radio Data

SECTORID, ANTNUM, ANT1CN, ANT1SRN, ANT1SN, ANT1N, CREATESECTOREQM, SECTOREQMID

User-defined sheet

SECTOREQM

eNodeB Radio Data

SECTOREQMID, SECTORID, ANTNUM, ANT1CN, ANT1SRN, ANT1SN, ANT1N, ANTTYPE1

User-defined sheet

Cell

eNodeB Radio Data

LocalCellId, TxRxMode, CrsPortNum, CrsPortMap

User-defined sheet

eUCellSectorEqm

eNodeB Radio Data

LocalCellId, SectorEqmId

User-defined sheet

CellMimoParaCf g

eNodeB Radio Data

LocalCellId, MimoAdaptiveSwitch, FixedMimoMode, InitialMimoType

User-defined sheet

SRSCfg

eNodeB Radio Data

LocalCellId, SrsCfgInd

User-defined sheet

CellDlschAlgo

eNodeB Radio Data

LocalCellId, MaxMimoRankPara, MbsfnSfCfg, DlRankOptimizeSwitc, FDUEEnhAperCQITrigPeriod

User-defined sheet


130



MO


Parameter Group

Remarks

CqiAdaptiveCfg

eNodeB Radio Data

PucchPeriodicCqiOptSwitch

User-defined sheet

CellCqiAdaptive Cfg

eNodeB Radio Data

CqiPeriodAdaptive, UserCqiPeriod, HoAperiodicCqiCfgSwitch

User-defined sheet

CellAlgoSwitch

eNodeB Radio Data

DlSchSwitch, EnhMIMOSwitch

User-defined sheet

CellDlschAlgo

eNodeB Radio Data

DlRankDetectSwitch

User-defined sheet

9.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure is as follows: Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs." For online help, press F1 when a CME window is active, and select Managing the CME > CME Guidelines > LTE Application Management > eNodeB Related Operations > Customizing a Summary Data File for Batch eNodeB Configuration. Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME into the customized summary data file. Step 3 In the summary data file, set the parameters in the MOs according to the setting notes provided in section "Data Preparation" and close the file. Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME, and then start the data verification. Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. For detailed operations, see Managing the CME > CME Guidelines > Script File Management > Exporting Incremental Scripts from a Planned Data Area in the CME online help. ----End

9.4.5.3 Using the CME to Perform Single Configuration On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The procedure is as follows: Issue 04 (2015-08-31)


131



Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window. Step 2 In area 1 shown in Figure 9-19, select the eNodeB to which the MOs belong. Figure 9-19 MO search and configuration window

Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL. Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are displayed in area 4. Step 5 Set the parameters in area 4 or 5. Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. ----End

9.4.5.4 Using MML Commands LOFD-001001 DL 2x2 MIMO Configure downlink 2x2 MIMO by referring to the following examples. Step 1 Add a sector, a set of sector equipment (including antennas), and a cell (including its TX/RX mode). For details, see the MML command examples in 7.4.5.4 Using MML Commands: l


l


l


Issue 04 (2015-08-31)


132



l


l


l


If 4T2P is used to implement 2x2 MIMO, see the following sections in 7.4.5.4 Using MML Commands: l


l


l


Step 2 (Optional) If adaptive configuration of open- and closed-loop transmission modes is enabled, run the MOD SRSCFG command to enable the configuration of SRS resources for UEs by setting the SRS Configuration Indicator parameter to BOOLEAN_TRUE(True) and the FDD SRS Configuration Mode parameter set to DEFAULTMODE(Default Mode). Example: MOD SRSCFG: LocalCellId=0, SrsCfgInd=BOOLEAN_TRUE, FddSrsCfgMode=DEFAULTMODE;

Step 3 Run the MOD CELL command to set the CRS Port Number parameter. If a 4T4R cell is expected to implement 2x2 MIMO, set the CRS Antenna Port Mapping parameter to specify a CRS port transmit sequence of 4T2P. Example: To allow a 2T2R cell served by an integrated RRU to support 2x2 MIMO, run the following command to set the CRS Port Number parameter: MOD CELL: LocalCellId=0, CrsPortNum=CRS_PORT_2, TxRxMode=2T2R;

To allow a 4T4R cell served by an integrated RRU or combined RRUs to support 2x2 MIMO, run the following command to set the CRS Antenna Port Mapping parameter to 4T2P_0011: MOD CELL: LocalCellId=0, CrsPortNum=CRS_PORT_2, TxRxMode=4T4R, CrsPortMap=4T2P_0011;

Step 4 Run the MOD CELLMIMOPARACFG command to configure a MIMO transmission mode as described in the following table. Transmission Mode

MML Command

Adaptively configured open-loop transmission mode

Set the MimoAdaptiveSwitch parameter to OL_ADAPTIVE(OL_ADAPTIVE). Example: MOD CELLMIMOPARACFG: LocalCellId=0, MimoAdaptiveSwitch=OL_ADAPTIVE;

Adaptively configured closedloop transmission mode

Issue 04 (2015-08-31)

Set the MimoAdaptiveSwitch parameter to CL_ADAPTIVE(CL_ADAPTIVE). Example: MOD CELLMIMOPARACFG: LocalCellId=0, MimoAdaptiveSwitch=CL_ADAPTIVE;


133



Transmission Mode

MML Command

Adaptively configured open- or closed-loop transmission mode

Set the MimoAdaptiveSwitch parameter to OC_ADAPTIVE(OC_ADAPTIVE).

TM2

Example: MOD CELLMIMOPARACFG: LocalCellId=0, MimoAdaptiveSwitch=OC_ADAPTIVE;

Set the MimoAdaptiveSwitch parameter to NO_ADAPTIVE(NO_ADAPTIVE) and the FixedMimoMode parameter to TM2(TM2). Example: MOD CELLMIMOPARACFG: LocalCellId=0, MimoAdaptiveSwitch=NO_ADAPTIVE, FixedMimoMode=TM2;

TM3


TM4


TM6


Initial transmission mode TM2

Set the InitialMimoType parameter to TM2(TM2). Example: MOD CELLMIMOPARACFG: LocalCellId=0, InitialMimoType=TM2;

Adaptively configured initial transmission mode

Set the InitialMimoType parameter to ADAPTIVE(ADAPTIVE). Example: MOD CELLMIMOPARACFG: LocalCellId=0, InitialMimoType=ADAPTIVE;

Step 5 (Optional) Run the MOD CELLDLSCHALGO command to set the maximum number of MIMO layers and enable or disable downlink rank optimization. Example: Set the maximum number of MIMO layers in downlink scheduling to 2 and enable downlink rank optimization.

Issue 04 (2015-08-31)


134



MOD CELLDLSCHALGO: LocalCellId=0, MaxMimoRankPara=SW_MAX_SM_RANK_2, DlRankOptimizeSwitch = ON;

Step 6 (Optional) Run the MOD CELLCQIADAPTIVECFG command to set the CQI reporting period adaptation switch, UE-level CQI reporting period, and aperiodic CQI configuration switch for handover. Example: Turn off the CQI reporting period adaptation switch and set the UE-level CQI reporting period to 10 ms. MOD CELLCQIADAPTIVECFG:LOCALCELLID=0,CQIPERIODADAPTIVE=OFF,USERCQIPERIOD=ms10;

Example: Turn on the CQI reporting period adaptation switch and the aperiodic CQI configuration switch for handover. MOD CELLCQIADAPTIVECFG:LOCALCELLID=0,CQIPERIODADAPTIVE=ON,HOAPERIODICCQICFGSWITCH=ON;

Step 7 (Optional) When the CQI period adaptive switch parameter is set to ON(On), run the MOD CQIADAPTIVECFG command to enable or disable optimized periodic CQI reporting on the PUCCH. Examples: When the CQI period adaptive switch parameter is set to ON(On), enable optimized periodic CQI reporting on the PUCCH. MOD CQIADAPTIVECFG: PucchPeriodicCqiOptSwitch=ON;

Step 8 (Optional) Run the MOD CELLALGOSWITCH command to enable or disable enhanced aperiodic CQI reporting. Example: Enable enhanced aperiodic CQI reporting. MOD CELLALGOSWITCH: LocalCellId=0, DlSchSwitch=EnAperiodicCqiRptSwitch-1;

Step 9 (Optional) Run the MOD CELLALGOSWITCH command to enable or disable aperiodic CQI reporting optimization. Example: Enable aperiodic CQI reporting optimization. MOD CELLALGOSWITCH: LocalCellId=0, DlSchSwitch=AperiodicCqiTrigOptSwitch-1;

Step 10 (Optional) Run the MOD ENODEBALGOSWITCH command to enable or disable the workaround for UE incompatibility in aperiodic CQI reporting mode. Example: Enable the workaround for UE incompatibility in aperiodic CQI reporting mode. MOD ENODEBALGOSWITCH: COMPATIBILITYCTRLSWITCH=ApCqiAndAckAbnCtrlSwitch-1;

Step 11 (Optional) Run the MOD CELLDLSCHALGO command to enable downlink rank detection. Example: Issue 04 (2015-08-31)


135



MOD CELLDLSCHALGO: LocalCellId=0, DlRankDetectSwitch=DETECTRANK2ADJSWITCH-1&DETECTRANK1ADJSWITCH-0;

Step 12 Activate the cell. Example: ACT CELL: LocalCellId=0;

----End

Downlink 2x2 MIMO in TM9 Based on the preceding configuration for downlink 2x2 MIMO not in TM9, configure downlink 2x2 MIMO in TM9 by referring to the following examples: Step 1 Run the MOD CELLALGOSWITCH command to configure TM9 as described in the following table. Transmission Mode

MML Command

TM9

Set the TM9Switch option of the EnhMIMOSwitch parameter. Example: MOD CELLALGOSWITCH: LocalCellId=0, EnhMIMOSwitch=TM9Switch-1;

Step 2 Run the MOD CELLCSIRSPARACFG command to set the CSI-RS switch and CSI-RS reporting period. Example: MOD CELLCSIRSPARACFG: LocalCellId=0, CsiRsSwitch =FIXED_CFG, CsiRsPeriod=ms5;

Step 3 (Optional) Run the MOD CELLDLSCHALGO command to set MBSFN subframes. Example: MOD CELLDLSCHALGO: LocalCellId=0, MBSFNSFCFG=SubFrame0-0&SubFrame1-0&SubFrame2-0&SubFrame3-0&SubFrame4-0&SubFrame5-0 &SubFrame6-0&SubFrame7-0&SubFrame8-0&SubFrame9-0;

----End

LOFD-001003 DL 4x2 MIMO Configure LOFD-001003 DL 4x2 MIMO by referring to the following examples: Step 1 Add a sector, a set of sector equipment (including antennas), and a cell (including its TX/RX mode). For details, see the MML command examples in 7.4.5.4 Using MML Commands: l


l


l


Step 2 (Optional) If adaptive configuration of open- and closed-loop transmission modes is enabled, run the MOD SRSCFG command to enable the configuration of SRS resources for UEs by Issue 04 (2015-08-31)


136



setting the SRS Configuration Indicator parameter to BOOLEAN_TRUE(True) and the FDD SRS Configuration Mode parameter set to DEFAULTMODE(Default Mode). Example: MOD SRSCFG: LocalCellId=0, SrsCfgInd=BOOLEAN_TRUE, FddSrsCfgMode=DEFAULTMODE;

Step 3 Run the MOD CELL command to set the CRS Port Number parameter and change the CRS Antenna Port Mapping parameter value so as to improve the performance of downlink 4x2 MIMO. Example: For a cell served by an integrated RRU, set the CRS Port Number parameter and change the CRS Antenna Port Mapping parameter value to 4T4P_0321: MOD CELL: LocalCellId=0, CrsPortNum=CRS_PORT_4, TxRxMode=4T4R, CrsPortMap=4T4P_0321;

Example: For a cell served by combined RRUs, set the CRS Port Number parameter and change the CRS Antenna Port Mapping parameter value to 4T4P_0213: MOD CELL: LocalCellId=0, CrsPortNum=CRS_PORT_4, TxRxMode=4T4R, CrsPortMap=4T4P_0213;

Example: Disable CRS port mapping. MOD CELL: LocalCellId=0, TxRxMode=4T4R, CrsPortMap=NOT_CFG;


MML Command



Adaptively configured closedloop transmission mode Adaptively configured open- or closed-loop transmission mode

Issue 04 (2015-08-31)


Set the MimoAdaptiveSwitch parameter to OC_ADAPTIVE(OC_ADAPTIVE). Example: MOD CELLMIMOPARACFG: LocalCellId=0, MimoAdaptiveSwitch=OC_ADAPTIVE;


137



Transmission Mode

MML Command

TM2


TM3


TM4


TM6






Step 5 (Optional) Run the MOD CELLDLSCHALGO command to set the maximum number of MIMO layers and enable or disable downlink rank optimization. Example: Set the maximum number of MIMO layers in downlink scheduling to 2 and enable downlink rank optimization. MOD CELLDLSCHALGO: LocalCellId=0, MaxMimoRankPara=SW_MAX_SM_RANK_2, DlRankOptimizeSwitch = ON;

Step 6 (Optional) Run the MOD CELLCQIADAPTIVECFG command to set the CQI reporting period adaptation switch, UE-level CQI reporting period, and aperiodic CQI configuration switch for handover. Example: Issue 04 (2015-08-31)


138



Turn off the CQI reporting period adaptation switch and set the UE-level CQI reporting period to 10 ms. MOD CELLCQIADAPTIVECFG: CqiPeriodAdaptive=OFF, UserCqiPeriod=ms10;

Example: Turn on the CQI reporting period adaptation switch and the aperiodic CQI configuration switch for handover. MOD CELLCQIADAPTIVECFG:CqiPeriodAdaptive=ON,HoAperiodicCqiCfgSwitch=ON;

Step 7 (Optional) When the CQI period adaptive switch parameter is set to ON(On), run the MOD CQIADAPTIVECFG command to enable or disable optimized periodic CQI reporting on the PUCCH. Example: Enable enhanced aperiodic CQI reporting on the PUCCH. MOD CQIADAPTIVECFG: PucchPeriodicCqiOptSwitch=ON;



Step 10 (Optional) Enable or disable the workaround for UE incompatibility in aperiodic CQI reporting mode. Run the MOD ENODEBALGOSWITCH command to turn on or off ApCqiRptAbnormalCtrlSwitch. Example: Turn on ApCqiRptAbnormalCtrlSwitch. MOD ENODEBALGOSWITCH: COMPATIBILITYCTRLSWITCH=ApCqiAndAckAbnCtrlSwitch-1;


----End

Downlink 4x2 MIMO in TM9 Based on the preceding configuration for downlink 4x2 MIMO not in TM9, configure downlink 4x2 MIMO in TM9 by referring to the following examples: Issue 04 (2015-08-31)


139



Step 1 Run the MOD CELL command to set the CRS Port Number parameter and change the CRS Antenna Port Mapping parameter value. Example: For a cell served by an integrated RRU or combined RRUs, set the CRS Port Number parameter to 2 and change the CRS Antenna Port Mapping parameter value to 4T2P_0011: MOD CELL: LocalCellId=0, CrsPortNum=CRS_PORT_2, TxRxMode=4T4R, CrsPortMap=4T2P_0011;

Step 2 Run the MOD CELLALGOSWITCH command to set the EnhMIMOSwitch parameter to TM9Switch-1. Transmission Mode

MML Command

TM9




----End

LOFD-001060 DL 4x4 MIMO Configure LOFD-001060 DL 4x4 MIMO by referring to the following examples: Step 1 Add a sector, a set of sector equipment (including antennas), and a cell (including its TX/RX mode). For details, see the MML command examples in 7.4.5.4 Using MML Commands: l


l


l


Step 2 (Optional) If adaptive configuration of open- and closed-loop transmission modes is enabled, run the MOD SRSCFG command to enable the configuration of SRS resources for UEs by setting the SRS Configuration Indicator parameter to BOOLEAN_TRUE(True) and the FDD SRS Configuration Mode parameter set to DEFAULTMODE(Default Mode). Example: MOD SRSCFG: LocalCellId=0, SrsCfgInd=BOOLEAN_TRUE, FddSrsCfgMode=DEFAULTMODE;

Issue 04 (2015-08-31)


140



Step 3 (Optional) Run the MOD CELL command to change the CRS Antenna Port Mapping parameter value so as to improve the performance of downlink 4x4 MIMO. Example: For a cell served by an integrated RRU, change the CRS Antenna Port Mapping parameter value to 4T4P_0321: MOD CELL: LocalCellId=0, TxRxMode=4T4R, CrsPortMap=4T4P_0321;

Example: For a cell served by combined RRUs, change the CRS Antenna Port Mapping parameter value to 4T4P_0213. MOD CELL: LocalCellId=0, TxRxMode=4T4R, CrsPortMap=4T4P_0213;

Example: Disable CRS port mapping. MOD CELL: LocalCellId=0, TxRxMode=4T4R, CrsPortMap=NOT_CFG;


MML Command



Adaptively configured closedloop transmission mode Adaptively configured open- or closed-loop transmission mode TM2


Set the MimoAdaptiveSwitch parameter to OC_ADAPTIVE(OC_ADAPTIVE). Example: MOD CELLMIMOPARACFG: LocalCellId=0, MimoAdaptiveSwitch=OC_ADAPTIVE;


Issue 04 (2015-08-31)


141



Transmission Mode

MML Command

TM3


TM4


TM6






Step 5 (Optional) Run the MOD CELLDLSCHALGO command to set the maximum number of MIMO layers and enable or disable downlink rank optimization. Example: Set the maximum number of MIMO layers in downlink scheduling to 4 and enable downlink rank optimization. MOD CELLDLSCHALGO: LocalCellId=0, MaxMimoRankPara=SW_MAX_SM_RANK_4, DlRankOptimizeSwitch = ON;

Step 6 (Optional) Run the MOD CELLCQIADAPTIVECFG command to set the CQI reporting period adaptation switch, UE-level CQI reporting period, and aperiodic CQI configuration switch for handover. Example: Turn off the CQI reporting period adaptation switch and set the UE-level CQI reporting period to 10 ms. MOD CELLCQIADAPTIVECFG: CqiPeriodAdaptive=OFF, UserCqiPeriod=ms10;

Example: Issue 04 (2015-08-31)


142



Turn on the CQI reporting period adaptation switch and the aperiodic CQI configuration switch for handover. MOD CELLCQIADAPTIVECFG:CqiPeriodAdaptive=ON,HoAperiodicCqiCfgSwitch=ON;

Step 7 (Optional) When the CQI period adaptive switch parameter is set to ON(On), run the MOD CQIADAPTIVECFG command to enable or disable optimized periodic CQI reporting on the PUCCH. Example: Enable enhanced aperiodic CQI reporting on the PUCCH. MOD CQIADAPTIVECFG: PucchPeriodicCqiOptSwitch=ON;



Step 10 (Optional) Enable or disable the workaround for UE incompatibility in aperiodic CQI reporting mode. Run the MOD ENODEBALGOSWITCH command to turn on or off ApCqiRptAbnormalCtrlSwitch. Example: Turn on ApCqiRptAbnormalCtrlSwitch. MOD ENODEBALGOSWITCH: COMPATIBILITYCTRLSWITCH=ApCqiAndAckAbnCtrlSwitch-1;


----End

Downlink 4x4 MIMO in TM9 Based on the preceding configuration for downlink 4x4 MIMO not in TM9, configure downlink 4x4 MIMO in TM9 by referring to the following examples: Step 1 Run the MOD CELL command to set the CRS Port Number parameter and change the CRS Antenna Port Mapping parameter value. Example: Issue 04 (2015-08-31)


143



For a cell served by an integrated RRU or combined RRUs, set the CRS Port Number parameter to 2 and change the CRS Antenna Port Mapping parameter value to 4T2P_0011: MOD CELL: LocalCellId=0, CrsPortNum=CRS_PORT_2, TxRxMode=4T4R, CrsPortMap=4T2P_0011;

Step 2 Run the MOD CELLALGOSWITCH command to set the EnhMIMOSwitch parameter to TM9Switch-1. Transmission Mode

MML Command

TM9




----End

9.4.6 Activation Observation Transmission mode configurations can be modified by running an MML command. To avoid signaling storms, the modifications take effect only after the UE accesses the network again.

9.4.6.1 Observing Adaptive Configuration of Transmission Modes On the U2000, run the LST CELLMIMOPARACFG command to check the configuration. l

If the value of the MIMO adaptive switch parameter is OL_ADAPTIVE, adaptive configuration of open-loop transmission modes has been activated. The eNodeB configures transmission modes based on channel conditions. For example, the eNodeB configures open-loop transmit diversity when the SINR is low and configures open-loop spatial multiplexing when the SINR is high with rich scattering.

l

If the value of the MIMO adaptive switch parameter is CL_ADAPTIVE, adaptive configuration of closed-loop transmission modes has been activated. The eNodeB configures transmission modes based on channel conditions. For example, the eNodeB configures closed-loop transmit diversity when the SINR is low and configures closedloop spatial multiplexing when the SINR is high with rich scattering.

l

If the value of the MIMO adaptive switch parameter is OC_ADAPTIVE, adaptive configuration of open- and closed-loop transmission modes has been activated. The eNodeB configures transmission modes based on channel conditions. For example, the

Issue 04 (2015-08-31)


144



eNodeB configures closed-loop transmission mode for low-speed UEs and configures open-loop transmission mode for high-speed UEs. NOTE

Adaptive configuration of open- and closed-loop transmission modes requires that the SRSCfg.SrsCfgInd parameter be set to BOOLEAN_TRUE(True) and the SRSCfg.FddSrsCfgMode parameter be set to DEFAULTMODE(Default Mode).

9.4.6.2 Observing Fixed Configuration of Transmission Modes TM2 Step 1 Enable a UE to access the cell. Start Uu interface tracing on the U2000 client and check the transmissionMode information element (IE) in the RRC_CONN_SETUP message. If the value of this IE is "tm2", the eNodeB has delivered the MIMO configuration successfully, as shown in the following figure. Figure 9-20 RRC_CONN_SETUP_TM2

Step 2 If a Huawei UE is used, perform downlink UDP packet injection at a high speed and use the GENEX Probe tool to check radio parameters. If the transmission mode is TM2, TM2 has been activated. Step 3 If the eNodeB selects single-codeword scheduling under low channel correlation and high downlink SINR, TM2 has been activated, as shown in the following figures (MS1 refers to the UE).

Issue 04 (2015-08-31)


145



Figure 9-21 LTE radio parameters: MS1

Issue 04 (2015-08-31)


146



Figure 9-22 MIMO: MS1

----End

TM3 Enable a UE to access the cell. Start Uu interface tracing on the U2000 client and check the transmissionMode IE in the RRC_CONN_SETUP message. If the value of this IE is "tm3", the eNodeB has delivered the MIMO configuration successfully, as shown in the following figure.

Issue 04 (2015-08-31)


147



Figure 9-23 RRC_CONN_SETUP_TM3

TM4 Enable a UE to access the cell. Start Uu interface tracing on the U2000 client and check the transmissionMode IE in the RRC_CONN_SETUP message. If the value of this IE is "tm4", the eNodeB has delivered the MIMO configuration successfully, as shown in the following figure.

Issue 04 (2015-08-31)


148



Figure 9-24 RRC_CONN_SETUP_TM4

TM6 Step 1 Enable a UE to access the cell. Start Uu interface tracing on the U2000 client and check the transmissionMode IE in the RRC_CONN_SETUP message. If the value of this IE is "tm6", the eNodeB has delivered the MIMO configuration successfully, as shown in the following figure. Figure 9-25 RRC_CONN_SETUP_TM6

Issue 04 (2015-08-31)


149



Step 2 If a Huawei UE is used, perform downlink UDP packet injection at a high speed and use the GENEX Probe tool to check radio parameters. If the transmission mode is TM6, TM6 has been activated. Step 3 If the eNodeB selects single-codeword scheduling under low channel correlation and high downlink SINR, TM6 has been activated, as shown in the following figures. Figure 9-26 LTE radio parameters: MS1

Issue 04 (2015-08-31)


150



Figure 9-27 MIMO: MS1

----End

Downlink 4x4 MIMO Step 1 Use UEs of category 5 that support 4-antenna reception and rank 4 to access a properly running cell with a bandwidth of 20 MHz. Ensure parallel networking of RF channels between the UEs and the eNodeB. Step 2 Move the UEs to the cell center, and perform downlink UDP packet injection to enable the total downlink rate to reach the maximum rate in the cell. Step 3 Check whether the maximum (peak) rate is higher than 160 Mbit/s. If the rate is higher than 160 Mbit/s, downlink 4x4 MIMO is activated. If a Huawei UE is used, use the GENEX Probe tool to check whether MIMO scheduling is performed on the 4T4R RRU. If so, downlink 4x4 MIMO has been activated. ----End

TM9 To verify the activation of TM9, perform the following steps: Step 1 Activate MIMO in TM9. Issue 04 (2015-08-31)


151



Step 2 Ensure that UEs support TM9. Step 3 Start a trace task for DCI Statistic Monitoring on the U2000 client. If there is PDCCH DCI format 2C, TM9 has been activated. ----End

9.4.6.3 Observing Periodic and Aperiodic CQI Reporting Optimization This section uses a cell with a bandwidth of 20 MHz and commercial UEs as an example to describe how to verify the activation of periodic and aperiodic CQI reporting optimization.

Optimized Periodic CQI Reporting on the PUCCH To observe whether optimized periodic CQI reporting on the PUCCH has been activated, perform the following steps: Step 1 Enable 10 UEs to access the cell and then perform ping services. Step 2 Disable optimized periodic CQI reporting on the PUCCH. Then, use one UE to access the cell. Query the cqi-pmi-ConfigIndex value in the RRC_CONN_RECFG message traced over the Uu interface, as shown in Figure 9-28. The value indicates that the corresponding CQI reporting period is 5 ms. For details about the mapping between the CQI reporting period and the cqi-pmi-ConfigIndex value, see section 7.2.2 "Periodic CSI Reporting using PUCCH" in 3GPP TS 36.213 V10.5.0. Figure 9-28 CQI reporting period of 5 ms

Step 3 Release the UE that accessed the cell in Step 2. Enable optimized periodic CQI reporting on the PUCCH. Then, use another UE to access the cell. Query the cqi-pmi-ConfigIndex value in the RRC_CONN_RECFG message traced over the Uu interface, as shown in Figure 9-29. The value indicates that the CQI reporting period is 40 ms.

Issue 04 (2015-08-31)


152



Figure 9-29 CQI reporting period of 40 ms

----End

Enhanced Aperiodic CQI Reporting Step 1 Enable 11 UEs to access a cell, with one UE performing uplink TCP services and the other 10 UEs performing ping services. Step 2 Check the following counters on the U2000 client. l

L.ChMeas.CQI.DL.DualCW.Code0.Aperiodic.0 through L.ChMeas.CQI.DL.DualCW.Code0.Aperiodic.15

l

L.ChMeas.CQI.DL.DualCW.Code1.Aperiodic.0 through L.ChMeas.CQI.DL.DualCW.Code1.Aperiodic.15

l

L.ChMeas.CQI.DL.SingleCW.Aperiodic.5 through L.ChMeas.CQI.DL.SingleCW.Aperiodic.15

Step 3 Disable enhanced aperiodic CQI reporting. The number of aperiodic CQI reports decreases, as shown in Figure 9-30. Figure 9-30 Decreased number of CQI reports

Step 4 The number of aperiodic CQI reports increases significantly, as shown in Figure 9-31.

Issue 04 (2015-08-31)


153



Figure 9-31 Increased number of CQI reports

----End

Aperiodic CQI Reporting Optimization Method 1: Step 1 Simulate a heavy traffic scenario for testing. Step 2 Run the MOD CELLALGOSWITCH command with the AperiodicCqiTrigOptSwitch option of the Enhanced Aperiodic CQI Report Switch parameter deselected, and collect the L.ChMeas.PUSCH.MCS.29 counter value. Step 3 Run the MOD CELLALGOSWITCH command with the AperiodicCqiTrigOptSwitch option of the Enhanced Aperiodic CQI Report Switch parameter selected, and collect the L.ChMeas.PUSCH.MCS.29 counter value. L.ChMeas.PUSCH.MCS.29 indicates the number of aperiodic CQI reports (for details, see section 8.6.2 in 3GPP TS 36.213 V10.5.0). If aperiodic CQI reporting optimization is enabled, the number of times only CQIs are scheduled in the uplink and the number of times MCS 29 is selected decrease. ----End Method 2: Step 1 Simulate a light traffic scenario for testing by enabling a single UE to access a cell. Step 2 Run the MOD DRX command with the DRX switch parameter set to ON(On). Step 3 Run the MOD CELLALGOSWITCH command with the AperiodicCqiTrigOptSwitch option of the Enhanced Aperiodic CQI Report Switch parameter deselected, and collect the L.ChMeas.PUSCH.MCS.29 counter value. Step 4 Run the MOD CELLALGOSWITCH command with the AperiodicCqiTrigOptSwitch option of the Enhanced Aperiodic CQI Report Switch parameter selected, and collect the L.ChMeas.PUSCH.MCS.29 counter value. Expected result: The counter value decreases, indicating that aperiodic CQI reporting optimization takes effect. ----End Issue 04 (2015-08-31)


154



9.4.7 Reconfiguration Micro eNodeBs do not support reconfiguration of multiple-antenna transmission. For macro eNodeBs, to configure or reconfigure a MIMO mode, manually set the CRS Port Number and CRS Antenna Port Mapping parameters. For details about how to configure antennas and TX/RX modes in sectors and sector equipment, see 7.4.5.4 Using MML Commands.

Upgrading Downlink TM1 to Downlink 2x2 MIMO To upgrade downlink TM1 to downlink 2x2 MIMO, change the CRS Port Number parameter value from 1 to 2. If the cell works in 4T4R mode, set the CRS Antenna Port Mapping parameter to enable 4T2P; otherwise, there is no need to set this parameter. Example: To allow a 2T2R cell served by an integrated RRU to support 2x2 MIMO, run the following command to set the CRS Port Number parameter: MOD CELL: LocalCellId=0, CrsPortNum=CRS_PORT_2, TxRxMode=2T2R;

To allow a 4T4R cell served by an integrated RRU or combined RRUs to support 2x2 MIMO, run the following command to set the CRS Antenna Port Mapping parameter to 4T2P_0011: MOD CELL: LocalCellId=0, CrsPortNum=CRS_PORT_2, TxRxMode=4T4R, CrsPortMap=4T2P_0011;

Upgrading Downlink 2x2 MIMO to Downlink 4x2 or 4x4 MIMO To upgrade downlink 2x2 MIMO to downlink 4x2 or 4x4 MIMO, change the CRS Port Number parameter value from 2 to 4. If an integrated RRU is used, it is recommended that the CRS Antenna Port Mapping parameter be set to 4T4P_0321. If combined RRUs are used, it is recommended that this parameter be set to 4T4P_0213. Example: For a cell served by an integrated RRU, set the CRS Port Number parameter and change the CRS Antenna Port Mapping parameter value to 4T4P_0321: MOD CELL: LocalCellId=0, CrsPortNum=CRS_PORT_4, TxRxMode=4T4R, CrsPortMap=4T4P_0321;

Example: For a cell served by combined RRUs, set the CRS Port Number parameter and change the CRS Antenna Port Mapping parameter value to 4T4P_0213: MOD CELL: LocalCellId=0, CrsPortNum=CRS_PORT_4, TxRxMode=4T4R, CrsPortMap=4T4P_0213;

9.4.8 Deactivation 9.4.8.1 Using the CME to Perform Batch Configuration Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple Issue 04 (2015-08-31)


155



eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in 9.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to Table 9-3. Table 9-3 Parameters related to multiple-antenna transmission MO


Parameter Group

Setting Notes

SECTORE QM

eNodeB Radio Data

SECTOREQMID, OPMODE, ANTNUM, ANT1CN, ANT1SRN, ANT1SN, ANT1N

User-defined sheet The following parameter settings are only for reference. For details about parameter settings, see 9.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs. SECTOREQMID: 0 OPMODE: DELETE ANTNUM: 1 ANT1CN: 0 ANT1SRN: 60 ANT1SN: 0 ANT1N: R0B

Cell

eNodeB Radio Data


User-defined sheet The following parameter settings are only for reference. For details about parameter settings, see 9.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs. LocalCellId: 0 TxRxMode: 1T1R


9.4.8.3 Using MML Commands LOFD-001001 DL 2x2 MIMO If this feature is activated according to the instructions in Using MML Commands, you can run the following commands to deactivate it. Example: Issue 04 (2015-08-31)


156



DEA CELL: LocalCellId=0; MOD SECTOREQM: SECTOREQMID=0, OPMODE=DELETE, ANTNUM=1, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0B; MOD CELL: LocalCellId=0, TxRxMode=1T1R; ACT CELL: LocalCellId=0;

Downlink 2x2 MIMO in TM9 If this function is activated according to the instructions in Using MML Commands, you can run the following command to deactivate it by removing CSI-RS and MBSFN subframe configurations and then turning off the TM9 switch. Example: DEA CELL: LocalCellId=0; MOD CELLDLSCHALGO: LocalCellId=0, MBSFNSFCFG=SubFrame0-0&SubFrame1-0&SubFrame2-0&SubFrame3-0&SubFrame4-0&SubFrame5-0 &SubFrame6-0&SubFrame7-0&SubFrame8-0&SubFrame9-0; MOD CELLCSIRSPARACFG: LocalCellId=0, CsiRsSwitch = NOT_CFG; MOD CELLALGOSWITCH: LocalCellId=0, EnhMIMOSwitch=TM9Switch-0; MOD SECTOREQM: SECTOREQMID=0, OPMODE=DELETE, ANTNUM=1, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0B; MOD CELL: LocalCellId=0, TxRxMode=1T1R; ACT CELL: LocalCellId=0;

LOFD-001003 DL 4x2 MIMO If this feature is activated according to the instructions in Using MML Commands, you can run the following commands to deactivate it: Example: If the BBU and RRUs are connected as described in 4T4R Cell (Integrated RRU) in 9.4.4 Hardware Adjustment, you can run the following commands to deactivate this function. DEA CELL: LocalCellId=0; MOD SECTOREQM: SECTOREQMID=0, OPMODE=DELETE, ANTNUM=3, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0B, ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0C, ANT3CN=0, ANT3SRN=60, ANT3SN=0, ANT3N=R0D; MOD CELL: LocalCellId=0, TxRxMode=1T1R; ACT CELL: LocalCellId=0;

If the BBU and RRUs are connected as described in 4T4R Cell (2T2R+2T2R; 2T2R RRUs) and 4T4R Cell (2T2R+2T2R; 2T4R RRUs) in 9.4.4 Hardware Adjustment, you can run the following commands to deactivate this function. DEA CELL: LocalCellId=0; MOD SECTOREQM: SECTOREQMID=0, OPMODE=DELETE, ANTNUM=3, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0B, ANT2CN=0, ANT2SRN=61, ANT2SN=0, ANT2N=R0A, ANT3CN=0, ANT3SRN=61, ANT3SN=0, ANT3N=R0B; MOD CELL: LocalCellId=0, TxRxMode=1T1R; ACT CELL: LocalCellId=0;

Downlink 4x2 MIMO in TM9 If this function is activated according to the instructions in Using MML Commands, you can run the following command to deactivate it by removing CSI-RS and MBSFN subframe configurations and then turning off the TM9 switch. If the BBU and RRUs are connected as described in 4T4R Cell (Integrated RRU) in 9.4.4 Hardware Adjustment, you can run the following commands to deactivate this function. Example: Issue 04 (2015-08-31)


157



DEA CELL: LocalCellId=0; MOD CELLDLSCHALGO: LocalCellId=0, MBSFNSFCFG=SubFrame0-0&SubFrame1-0&SubFrame2-0&SubFrame3-0&SubFrame4-0&SubFrame5-0 &SubFrame6-0&SubFrame7-0&SubFrame8-0&SubFrame9-0; MOD CELLCSIRSPARACFG: LocalCellId=0, CsiRsSwitch = NOT_CFG; MOD CELLALGOSWITCH: LocalCellId=0, EnhMIMOSwitch=TM9Switch-0; MOD SECTOREQM: SECTOREQMID=0, OPMODE=DELETE, ANTNUM=3, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0B, ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0C, ANT3CN=0, ANT3SRN=60, ANT3SN=0, ANT3N=R0D; MOD CELL: LocalCellId=0, TxRxMode=1T1R; ACT CELL: LocalCellId=0;

If the BBU and RRUs are connected as described in 4T4R Cell (2T2R+2T2R; 2T2R RRUs) and 4T4R Cell (2T2R+2T2R; 2T4R RRUs) in 9.4.4 Hardware Adjustment, you can run the following commands to deactivate this function. Example: DEA CELL: LocalCellId=0; MOD CELLDLSCHALGO: LocalCellId=0, MBSFNSFCFG=SubFrame0-0&SubFrame1-0&SubFrame2-0&SubFrame3-0&SubFrame4-0&SubFrame5-0 &SubFrame6-0&SubFrame7-0&SubFrame8-0&SubFrame9-0; MOD CELLCSIRSPARACFG: LocalCellId=0, CsiRsSwitch = NOT_CFG; MOD CELLALGOSWITCH: LocalCellId=0, EnhMIMOSwitch=TM9Switch-0; MOD SECTOREQM: SECTOREQMID=0, OPMODE=DELETE, ANTNUM=3, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0B, ANT2CN=0, ANT2SRN=61, ANT2SN=0, ANT2N=R0A, ANT3CN=0, ANT3SRN=61, ANT3SN=0, ANT3N=R0B; MOD CELL: LocalCellId=0, TxRxMode=1T1R; ACT CELL: LocalCellId=0;

LOFD-001060 DL 4x4 MIMO If this feature is activated according to the instructions in Using MML Commands, you can run the following commands to deactivate it. Example: If the BBU and RRUs are connected as described in 4T4R Cell (Integrated RRU) in 9.4.4 Hardware Adjustment, you can run the following commands to deactivate this function. DEA CELL: LocalCellId=0; MOD SECTOREQM: SECTOREQMID=0, OPMODE=DELETE, ANTNUM=3, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0B, ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0C, ANT3CN=0, ANT3SRN=60, ANT3SN=0, ANT3N=R0D; MOD CELL: LocalCellId=0, TxRxMode=1T1R; ACT CELL: LocalCellId=0;

If the BBU and RRUs are connected as described in 4T4R Cell (2T2R+2T2R; 2T2R RRUs) and 4T4R Cell (2T2R+2T2R; 2T4R RRUs) in 9.4.4 Hardware Adjustment, you can run the following commands to deactivate this function. DEA CELL: LocalCellId=0; MOD SECTOREQM: SECTOREQMID=0, OPMODE=DELETE, ANTNUM=3, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0B, ANT2CN=0, ANT2SRN=61, ANT2SN=0, ANT2N=R0A, ANT3CN=0, ANT3SRN=61, ANT3SN=0, ANT3N=R0B; MOD CELL: LocalCellId=0, TxRxMode=1T1R; ACT CELL: LocalCellId=0;

Downlink 4x4 MIMO in TM9 If this function is activated according to the instructions in 9.4.5.4 Using MML Commands, you can run the following command to deactivate it by removing CSI-RS and MBSFN subframe configurations and then turning off the TM9 switch. Issue 04 (2015-08-31)


158



If the BBU and RRUs are connected as described in 4T4R Cell (Integrated RRU) in 9.4.4 Hardware Adjustment, you can run the following commands to deactivate this function. Example: DEA CELL: LocalCellId=0; MOD CELLDLSCHALGO: LocalCellId=0, MBSFNSFCFG=SubFrame0-0&SubFrame1-0&SubFrame2-0&SubFrame3-0&SubFrame4-0&SubFrame5-0 &SubFrame6-0&SubFrame7-0&SubFrame8-0&SubFrame9-0; MOD CELLCSIRSPARACFG: LocalCellId=0, CsiRsSwitch = NOT_CFG; MOD CELLALGOSWITCH: LocalCellId=0, EnhMIMOSwitch=TM9Switch-0; MOD SECTOREQM: SECTOREQMID=0, OPMODE=DELETE, ANTNUM=3, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0B, ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0C, ANT3CN=0, ANT3SRN=60, ANT3SN=0, ANT3N=R0D; MOD CELL: LocalCellId=0, TxRxMode=1T1R; ACT CELL: LocalCellId=0;

If the BBU and RRUs are connected as described in 4T4R Cell (2T2R+2T2R; 2T2R RRUs) and 4T4R Cell (2T2R+2T2R; 2T4R RRUs) in 9.4.4 Hardware Adjustment, you can run the following commands to deactivate this function. Example: DEA CELL: LocalCellId=0; MOD CELLDLSCHALGO: LocalCellId=0, MBSFNSFCFG=SubFrame0-0&SubFrame1-0&SubFrame2-0&SubFrame3-0&SubFrame4-0&SubFrame5-0 &SubFrame6-0&SubFrame7-0&SubFrame8-0&SubFrame9-0; MOD CELLCSIRSPARACFG: LocalCellId=0, CsiRsSwitch = NOT_CFG; MOD CELLALGOSWITCH: LocalCellId=0, EnhMIMOSwitch=TM9Switch-0; MOD SECTOREQM: SECTOREQMID=0, OPMODE=DELETE, ANTNUM=3, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0B, ANT2CN=0, ANT2SRN=61, ANT2SN=0, ANT2N=R0A, ANT3CN=0, ANT3SRN=61, ANT3SN=0, ANT3N=R0B; MOD CELL:LocalCellId=0, TxRxMode=1T1R; ACT CELL: LocalCellId=0;

LOFD-001003 DL 4x2 MIMO For micro eNodeBs, if this feature is activated according to the instructions in Using MML Commands, you can run the following commands to deactivate it: Example: DEA CELL: LocalCellId=0; MOD SECTOREQM: SECTOREQMID=0, OPMODE=DELETE, ANTNUM=3, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0B, ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0C, ANT3CN=0, ANT3SRN=60, ANT3SN=0, ANT3N=R0D; MOD CELL: LocalCellId=0, TxRxMode=1T1R; ACT CELL: LocalCellId=0;

LOFD-001060 DL 4x4 MIMO For micro eNodeBs, if this feature is activated according to the instructions in Using MML Commands, you can run the following commands to deactivate it: Example: DEA CELL: LocalCellId=0; MOD SECTOREQM: SECTOREQMID=0, OPMODE=DELETE, ANTNUM=3, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0B, ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0C, ANT3CN=0, ANT3SRN=60, ANT3SN=0, ANT3N=R0D; MOD CELL: LocalCellId=0, TxRxMode=1T1R; ACT CELL: LocalCellId=0;

Issue 04 (2015-08-31)


159



NOTE

The preceding commands also deactivate multiple-antenna reception. After the deactivation, only TM1 is available.

9.5 Maintenance 9.5.1 Performance Monitoring LOFD-001001 DL 2x2 MIMO and LOFD-001003 DL 4x2 MIMO After LOFD-001001 DL 2x2 MIMO/LOFD-001003 DL 4x2 MIMO is activated, you can use the following counters to monitor the performance of adaptive configuration of transmission modes: l

1526727393 L.ChMeas.MIMO.PRB.OL.Rank1 (Total number of used downlink PRBs in open-loop rank 1 mode)

l


l

1526727391 L.ChMeas.MIMO.PRB.CL.Rank1 (Total number of used downlink PRBs in closed-loop rank 1 mode)

l


After downlink 2x2 or 4x2 MIMO in TM9 is enabled, you can use the following counters for monitoring: l

1526732723 L.Traffic.User.TM9.Avg (Average number of TM9 UEs in a cell)

l

1526727378 L.Traffic.User.Avg (Average number of UEs in a cell)

The network is running in the following situations: l

When adaptive configuration of open-loop transmission modes is used, the values of 1526727393 L.ChMeas.MIMO.PRB.OL.Rank1 and/or 1526727394 L.ChMeas.MIMO.PRB.OL.Rank2 are not 0 while the counter 1526727391 L.ChMeas.MIMO.PRB.CL.Rank1 and the value of 1526727392 L.ChMeas.MIMO.PRB.CL.Rank2 is 0.

l

When adaptive configuration of closed-loop transmission modes is used, the values of 1526727391 L.ChMeas.MIMO.PRB.CL.Rank1 and/or 1526727392 L.ChMeas.MIMO.PRB.CL.Rank2 are not 0 while the value of 1526727394 L.ChMeas.MIMO.PRB.OL.Rank2 is 0.

l

When adaptive configuration of open- or closed-loop transmission modes is used, the values of 1526727391 L.ChMeas.MIMO.PRB.CL.Rank1, 1526727392 L.ChMeas.MIMO.PRB.CL.Rank2, 1526727393 L.ChMeas.MIMO.PRB.OL.Rank1, and/or 1526727394 L.ChMeas.MIMO.PRB.OL.Rank2 are not 0.

Issue 04 (2015-08-31)


160



NOTE

When radio channels are highly correlated or all the UEs are located at the cell edge with poor channel quality, few or even no PRBs may be cumulatively used in rank 2. When adaptive configuration of open- and closed-loop transmission modes is used, the values of the counters related to closed-loop transmission modes are low or even equal to 0 if the radio channel conditions are more suitable for adaptive configuration of open-loop transmission modes, and the values of the counters related to open-loop modes are low or even equal to 0 if the radio channel conditions are more suitable for adaptive configuration of closed-loop transmission modes.

LOFD-001060 DL 4x4 MIMO After LOFD-001060 DL 4x4 MIMO is activated, you can use the following counters to monitor the performance of adaptive configuration of transmission modes: l


l


l


l


l


l


l


l


After downlink 4x4 MIMO in TM9 is enabled, you can use the following counters for monitoring: l

1526732723 L.Traffic.User.TM9.Avg (Average number of TM9 UEs in a cell)

l

1526727378 L.Traffic.User.Avg (Average number of UEs in a cell)

The network is running in the following situations: When adaptive configuration of open-loop transmission modes is used, the values of 1526727393 L.ChMeas.MIMO.PRB.OL.Rank1, 1526727394 L.ChMeas.MIMO.PRB.OL.Rank2, 1526728176 L.ChMeas.MIMO.PRB.OL.Rank3, and/or 1526728177 L.ChMeas.MIMO.PRB.OL.Rank4 are not 0. NOTE

When radio channels are highly correlated or all the UEs are located at the cell edge with poor channel quality, few or even no PRBs may be cumulatively used in rank 2 or higher.

In addition, you can compare the throughput in downlink 4x4 MIMO and downlink 2x2 MIMO. The throughput in downlink 4x4 MIMO should be the higher. The downlink throughput is calculated as follows: Issue 04 (2015-08-31)


161



Downlink throughput = Total downlink traffic volume at the PDCP layer (indicated by the counter 1526728261 L.Thrp.bits.DL) / Total duration of downlink data transmission (indicated by the counter 1526728232 L.Thrp.Time.Cell.DL) Note that the measurements must be performed under the same conditions (for example, the same cell bandwidth and UE transmit power). NOTE

When the channel correlation is high, channel quality is poor or the correlation between four receive antennas of the UE is high, the volume of data transmitted in rank 3 and rank 4 modes is small or even 0.

9.5.2 Parameter Optimization As described in 4.5.2 Adaptive Configuration of Transmission Modes, adaptive configuration of open-loop transmission modes is recommended for commercial use. Adaptive configuration of closed-loop transmission modes can also be used if it can bring gains in the simulation test performed according to the network plan and the beta test performed in the live network. If combined RRUs are used to serve a 4T4R cell, you are advised to set the Cell.CrsPortMap parameter to 4T4P_0213to improve the performance of 4x2 or 4x4 MIMO in mode. For details, see 4.6.1 CRS Port Mapping. If the TM9 switch is turned on in a 4T4R cell, it is recommended that Cell.CrsPortNum be set to CRS_PORT_2 and Cell.CrsPortMap be set to 4T2P_0011.

9.5.3 Troubleshooting Fault Description In 2T2R, 2T4R, or 4T4R mode, dual-codeword transmission fails under low channel correlation and high SINR.

Fault Handling Step 1 On the U2000 client, run the LST CELLMIMOPARACFG command. If TM2 or TM6 is configured as a fixed transmission mode, change it to another fixed transmission mode that supports two codewords based on the network plan. Step 2 (For macro eNodeBs) On the U2000 client, run the DSP LICINFO command to check whether the license control item LLT1DMIMO01 or LLT1DMIMO02 is valid. If it is invalid, load a valid license file for this item. (For micro eNodeBs) On the U2000 client, run the DSP LICINFO command to check whether the license control item LLT1DMIMO01 is valid. If it is invalid, load a valid license file for this item. Step 3 Check the UE category. If the UE category is 1, the UE does not support spatial multiplexing. Replace the UE with the one of a higher category. If the maximum rank is 1, run the LST CELLDLSCHALGO command to check whether the value of the maximum number of MIMO layers parameter is SW_MAX_SM_RANK_1(Rank1). If yes, change it to SW_MAX_SM_RANK_2(Rank2) or SW_MAX_SM_RANK_4(Rank4). Issue 04 (2015-08-31)


162



Step 4 If the fault persists, contact Huawei technical support. ----End

Fault Description If an antenna system fails, it falls back to 2T2R or 1T1R mode, depending on the number of available antennas.

Fault Handling The eNodeB automatically adjusts the Cell.CrsPortMap parameter to the default value to ensure normal running. After the antennas for 4T4R become available, the eNodeB automatically restores this parameter to the original value.

Fault Description If an antenna system fails, 4T4R cells (served by two combined 2T4R RRUs) fall back to 2T2R or 1T1R mode, depending on the number of available antennas.

Fault Handling For 4T4R cells served by 4T4R RRUs or two combined 2T2R RRUs, if an antenna system fails, they fall back in the sequence of 4T4R->2T4R->2T2R->1T2R->1T1R. For 4T4R cells served by two combined 2T4R RRUs, if an antenna system fails, they fall back in the sequence of 4T4R->2T2R->1T1R.

Fault Description After the TM9 switch is turned on, the DCI Statistic Monitoring result on the U2000 shows that there is not PDCCH DCI format 2C.

Fault Handling Step 1 Check that the eNodeB supports TM9. Note that: l

Macro eNodeBs that use the LBBPc for baseband processing do not support TM9.

l

LampSite eNodeBs support only downlink 2x2 MIMO in TM9.

Step 2 Check that the cell TX/RX mode supports TM9. If the mode is 1T, the transmission mode can only be TM1; in this case, TM9 does not take effect. Step 3 If the fault persists, contact Huawei technical support. ----End

Issue 04 (2015-08-31)


163


10 Parameters

10

Parameters

Table 10-1 Parameters MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

CellDlsc hAlgo

DlRank DetectS witch

MOD CELLD LSCHA LGO

TDLOF D-00100 1

DL 2X2 MIMO

Meaning: Indicates whether to perform rank detection. If the DetectRank2AdjSwitch option is deselected, UEs do not perform rank 2 detection when reporting rank 1. In this case, UEs perform single-codeword scheduling. If the DetectRank2AdjSwitch option is selected: (1) All UEs perform rank 2 detection when reporting rank 1 if whitelisted UEs have not been configured. (2) Only whitelisted UEs perform rank 2 detection when reporting rank 1 if whitelisted UEs have been configured.If the DetectRank1AdjSwitch check box is cleared, the UE does not perform rank 1 detection when reporting rank 2. In this case, the UE performs dual-codeword scheduling. If the DetectRank1AdjSwitch check box is selected, the UE performs rank 1 detection when reporting rank 2.This version does not support the function controlled by the DetectRank1AdjSwitch option, and the option setting does not take effect.

LST CELLD LSCHA LGO

GUI Value Range: DetectRank2AdjSwitch(DetectRank2AdjSwitch), DetectRank1AdjSwitch(DetectRank1AdjSwitch) Unit: None Actual Value Range: DetectRank2AdjSwitch, DetectRank1AdjSwitch Default Value: DetectRank2AdjSwitch:Off, DetectRank1AdjSwitch:Off

Issue 04 (2015-08-31)


164


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

ENodeB AlgoSwi tch

Compati bilityCtr lSwitch

MOD ENODE BALGO SWITC H

LBFD-0 0201802 / TDLBF D-00201 802

Coverag e Based Interfrequenc y Handov er

Meaning:

LST ENODE BALGO SWITC H

LBFD-0 0201805 / TDLBF D-00201 805 LBFD-0 02031 / TDLBF D-00203 1 LOFD-0 01019 / TDLOF D-00101 9 LOFD-0 01020 / TDLOF D-00102 0 TDLOF D-00102 2 TDLOF D-00102 3 LAOFD -001002 01 / TDLAO FD-001 002

Issue 04 (2015-08-31)

Service Based Interfrequenc y Handov er Support of aperiodi c CQI reports PS InterRAT Mobility between EUTRAN and UTRAN

Indicates the options used to enable or disable compatibility solutions when exceptions occur, based on which the eNodeB determines whether to handle compatibility problems. UECapRprtAbnormalCtrlSwitch: If this option is selected, the eNodeB handles compatibility problems of a UE when the UE cannot report its capability information. ApCqiRptAbnormalCtrlSwitch: Indicates whether to apply a compatibility solution to abnormal aperiodic CQI reporting. If this option is selected, the compatibility solution takes effect. The configuration IEs related to aperiodic CQI reporting are always included in RRC Connection Reconfiguration messages used to reconfigure CQIs regardless of whether the IEs changed or not. If this option is deselected, the compatibility solution does not take effect. The configuration IEs related to aperiodic CQI reporting are not included in RRC Connection Reconfiguration messages used to reconfigure CQIs if the IEs remain unchanged.

SRVCC to GERAN

UeInterRatMeasCtrlSwitch: Indicates whether an eNodeB checks the QCI-specific inter-RAT handover policies when evaluating an inter-RAT handover. This function does not allow the eNodeB to deliver interRAT measurement configurations to some special UEs anymore and applies to the following types of interRAT handovers: coverage-based handover, distancebased handover, uplink-quality-based handover, service-based handover, and SPID-specific handover back to the HPLMN. If this option is selected, the eNodeB determines whether to deliver A1/A2, B1, or B2 measurement configurations to the UE for a measurement-based or blind inter-RAT handover based on the setting of the values of the No handover flag parameters in the InterRatPolicyCfgGroup MO for QCIs of services running on the UE. If this option is deselected, the eNodeB does not perform the determination based on the No handover flag parameter values.

Carrier Aggrega tion for Downlin k 2CC

VoipExProtSwitch: Indicates whether to enable service request-based inter-frequency handover protection when a VoLTE exception occurs. If this option is selected and the eNodeB does not support VoLTE, the eNodeB can set up bearers for QCI-1

PS InterRAT Mobility between EUTRAN and GERAN SRVCC to UTRAN


165


MO

Parame ter ID

MML Comma nd

Feature ID

10 Parameters

Feature Name

Description

in 40MHz

services and other services when both of the following conditions are met: (1) The EPC delivers information about bearers with QCI 1 and other QCIs. (2) The UE exits the idle state. After the QCI-1 service bearers are set up, the UE is handed over to an inter-frequency network. This option is dedicated to LTE TDD networks. UeSRSAntSelectCtrlSwitch: Indicates whether to disable antenna selection during SRS transmission. If this option is selected, antenna selection is disabled. This option is dedicated to LTE TDD networks. CaCqiAndAckAbnCtrlSwitch: Indicates whether to enable a workaround of problems that may occur when periodic CQI reports and ACKs/NACKs are transmitted simultaneously in CA scenarios. If this option is selected, the simultaneousAckNackAndCQI IE value is set to False for CA UEs. If this option is deselected, the simultaneousAckNackAndCQI IE is set based on the original algorithms. GUI Value Range: UECapRprtAbnormalCtrlSwitch(UECapRprtAbnormalCtrlSwitch), ApCqiRptAbnormalCtrlSwitch(ApCqiRptAbnormalCtrlSwitch), UeInterRatMeasCtrlSwitch(UeInterRatMeasCtrlSwitch), VoipExProtSwitch(VoipExProtSwitch), UeSRSAntSelectCtrlSwitch(UeSRSAntSelectCtrlSwitch), ApCqiAndAckAbnCtrlSwitch(ApCqiAndAckAbnCtrlSwitch), CaCqiAndAckAbnCtrlSwitch(CaCqiAndAckAbnCtrlSwitch) Unit: None Actual Value Range: UECapRprtAbnormalCtrlSwitch, ApCqiRptAbnormalCtrlSwitch, UeInterRatMeasCtrlSwitch, VoipExProtSwitch, UeSRSAntSelectCtrlSwitch, ApCqiAndAckAbnCtrlSwitch, CaCqiAndAckAbnCtrlSwitch Default Value: UECapRprtAbnormalCtrlSwitch:Off, ApCqiRptAbnormalCtrlSwitch:Off, UeInterRatMeasCtrlSwitch:Off, VoipExProtSwitch:Off, UeSRSAntSelectCtrlSwitch:Off, ApCqiAndAckAbnCtrlSwitch:Off, CaCqiAndAckAbnCtrlSwitch:Off

Issue 04 (2015-08-31)


166


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

CellCsi RsParaC fg

CsiRsCo nfigUser NumTh

MOD CELLC SIRSPA RACFG

LOFD-0 01001

DL 2*2 MIMO

LOFD-0 01003

DL 4*2 MIMO

LST CELLC SIRSPA RACFG

LOFD-0 01060

DL 4x4 MIMO

Meaning: Indicates the threshold for the number of RRC_CONNECTED UEs supporting CSI_RS that is used to evaluate a change from the CSI-RS unconfigured state to the CSI-RS configured state when adaptive CSI-RS configuration is adopted.

TDLAO FD-001 00114

DL 2Layer MIMO Based on TM9

TDLAO FD-081 409

CellCsi RsParaC fg

CsiRsU nconfig UserNu mTh

Issue 04 (2015-08-31)

Unit: None Actual Value Range: 1~1200 Default Value: 10



LOFD-0 01001

DL 2*2 MIMO

LOFD-0 01003

DL 4*2 MIMO


LOFD-0 01060

DL 4x4 MIMO

TDLAO FD-001 00114


TDLAO FD-081 409

GUI Value Range: 1~1200

Meaning: Indicates the threshold for the number of RRC_CONNECTED UEs supporting CSI_RS that is used to evaluate a change from the CSI-RS configured state to the CSI-RS unconfigured state when adaptive CSI-RS configuration is adopted. GUI Value Range: 1~1200 Unit: None Actual Value Range: 1~1200 Default Value: 200



167


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

CellCsi RsParaC fg

CsiRsCo nfigUser RatioTh


LOFD-0 01001

DL 2*2 MIMO

LOFD-0 01003

DL 4*2 MIMO


LOFD-0 01060

DL 4x4 MIMO

Meaning: Indicates the threshold for the ratio of RRC_CONNECTED UEs supporting CSI_RS that is used to evaluate a change from the CSI-RS unconfigured state to the CSI-RS configured state when adaptive CSI-RS configuration is adopted.

TDLAO FD-001 00114


TDLAO FD-081 409

CellCsi RsParaC fg

CsiRsU nconfig UserRati oTh

Issue 04 (2015-08-31)

Unit: % Actual Value Range: 0~100 Default Value: 50



LOFD-0 01001

DL 2*2 MIMO

LOFD-0 01003

DL 4*2 MIMO


LOFD-0 01060

DL 4x4 MIMO

TDLAO FD-001 00114


TDLAO FD-081 409


Meaning: Indicates the threshold for the ratio of RRC_CONNECTED UEs supporting CSI_RS that is used to evaluate a change from the CSI-RS configured state to the CSI-RS unconfigured state when adaptive CSI-RS configuration is adopted. GUI Value Range: 0~100 Unit: % Actual Value Range: 0~100 Default Value: 40



168


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

CellAlg oSwitch

EnhMI MOSwit ch

MOD CELLA LGOSW ITCH

LAOFD -080210

DL 2*2 MIMO based on TM9

Meaning: Indicates whether to enable enhanced MIMO. This parameter now includes one switch. TM9Switch: Indicates whether accessing UEs are allowed to enter TM9 mode. Accessing UEs are allowed to enter the TM9 mode only when this switch is on. This parameter does not apply to cells established on the LBBPc.

LST CELLA LGOSW ITCH

LAOFD -080205 / TDLAO FD-001 00113 TDLAO FD-001 00114 TDLAO FD-080 406 TDLAO FD-080 407

Cell

CrsPort Num

ADD CELL MOD CELL LST CELL

LOFD-0 01001 / TDLOF D-00100 1 LOFD-0 01003 / TDLOF D-00100 3 LOFD-0 01060 / TDLOF D-00106 0

DL 4*2 MIMO based on TM9 DL 8x2 MIMO based on TM9

GUI Value Range: TM9Switch(TM9Switch) Unit: None Actual Value Range: TM9Switch Default Value: TM9Switch:Off

DL 4x4 MIMO based on TM9 DL 8x4 MIMO based on TM9 DL 2x2 MIMO DL 4x2 MIMO DL 4x4 MIMO

Meaning: Indicates the number of ports for transmitting cell-specific reference signal (CRS). As defined in 3GPP specifications, this parameter can be set to CRS_PORT_1, CRS_PORT_2, or CRS_PORT_4. The value CRS_PORT_1 indicates that one CRS port (port 0) is configured. The value CRS_PORT_2 indicates that two CRS ports (ports 0 and 1) are configured. The value CRS_PORT_4 indicates that four CRS ports (ports 0, 1, 2, and 3) are configured. GUI Value Range: CRS_PORT_1(1 port), CRS_PORT_2(2 ports), CRS_PORT_4(4 ports) Unit: None Actual Value Range: CRS_PORT_1, CRS_PORT_2, CRS_PORT_4 Default Value: CRS_PORT_2(2 ports)

Issue 04 (2015-08-31)


169


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

CellCsi RsParaC fg

LocalCe llId

DSP CELLC SIRSPA RACFG

None

None

Meaning: Indicates the local ID of the cell. It uniquely identifies a cell within an eNodeB. GUI Value Range: 0~255 Unit: None


Actual Value Range: 0~255 Default Value: None

MOD CELLC SIRSPA RACFG CellCsi RsParaC fg

CsiRsS witch


LOFD-0 01001

DL 2*2 MIMO

LOFD-0 01003

DL 4*2 MIMO


LOFD-0 01060

DL 4x4 MIMO

TDLAO FD-001 00114


TDLAO FD-081 409 LAOFD -080210 LAOFD -080205

DL 4Layer MIMO Based on TM9 DL 2*2 MIMO based on TM9

Meaning: Indicates whether to configure the CSI-RS. If this parameter is set to NOT_CFG, UEs are not configured with CSI-RSs. If this parameter is set to FIXD_CFG, UEs supporting CSI-RSs are configured with a fixed CSI-RS. If this parameter is set to ADAPTIVE_CFG, UEs supporting CSI-RSs are adaptively configured or not configured with the CSIRS based on the proportion of TM9-capable UEs. If the SfnLoadBasedAdptSwitch parameter is set to OFF(Off) for an ASFN cell on an LTE TDD network, this parameter is invalid when it is set to FIXED_CFG(Fixed configure) or ADAPTIVE_CFG(ADAPTIVE_CFG). GUI Value Range: NOT_CFG(Not configure), FIXED_CFG(Fixed configure), ADAPTIVE_CFG(ADAPTIVE_CFG) Unit: None Actual Value Range: NOT_CFG, FIXED_CFG, ADAPTIVE_CFG Default Value: NOT_CFG(Not configure)


Issue 04 (2015-08-31)


170


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

CellCsi RsParaC fg

CsiRsPe riod


LAOFD -080210


Meaning: Indicates the channel state information (CSI) reference signal (RS) measurement period.


Unit: None


LAOFD -080205 / TDLAO FD-001 00113 TDLAO FD-001 00114 TDLAO FD-080 406 TDLAO FD-080 407

CellDlsc hAlgo

MbsfnSf Cfg

MOD CELLD LSCHA LGO LST CELLD LSCHA LGO

LAOFD -080210 LAOFD -080205

GUI Value Range: ms5(ms5), ms10(ms10), ms20(ms20), ms40(ms40), ms80(ms80) Actual Value Range: ms5, ms10, ms20, ms40, ms80 Default Value: ms5(ms5)

DL 8x2 MIMO based on TM9 DL 4x4 MIMO based on TM9 DL 8x4 MIMO based on TM9 DL 2*2 MIMO based on TM9 DL 4*2 MIMO based on TM9

Meaning: Indicates whether to configure Multimedia Broadcast multicast service Single Frequency Network (MBSFN) subframes. The ten options of this parameter map to the ten MBSFN subframes. If an option is selected, the corresponding subframe is configured. If an option is not selected, the corresponding subframe is not configured. PDSCH services with enhanced MIMO applied can be scheduled on configured MBSFN subframes. GUI Value Range: SubFrame0(SubFrame0), SubFrame1(SubFrame1), SubFrame2(SubFrame2), SubFrame3(SubFrame3), SubFrame4(SubFrame4), SubFrame5(SubFrame5), SubFrame6(SubFrame6), SubFrame7(SubFrame7), SubFrame8(SubFrame8), SubFrame9(SubFrame9) Unit: None Actual Value Range: SubFrame0, SubFrame1, SubFrame2, SubFrame3, SubFrame4, SubFrame5, SubFrame6, SubFrame7, SubFrame8, SubFrame9 Default Value: SubFrame0:Off, SubFrame1:Off, SubFrame2:Off, SubFrame3:Off, SubFrame4:Off, SubFrame5:Off, SubFrame6:Off, SubFrame7:Off, SubFrame8:Off, SubFrame9:Off

Issue 04 (2015-08-31)


171


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

CellAlg oSwitch

UlSchS witch


LOFD-0 01016 / TDLOF D-00101 6

VoIP Semipersisten t Scheduli ng

Meaning:


LOFD-0 01048 / TDLOF D-00104 8 LOFD-0 0101502 / TDLOF D-00101 502 TDLBF D-00202 5 LBFD-0 70102 / TDLBF D-07010 2 LOFD-0 01002 LOFD-0 01058 LBFD-0 01006

TTI Bundlin g Dynami c Scheduli ng Basic Scheduli ngTDL OFD-07 0224:Sc heduling Based on Max Bit Rate MBR>G BR Configu ration UL 2x2 MUMIMO UL 2x4 MUMIMO AMC

This parameter indicates the switches related to uplink (UL) scheduling in the cell. The switches are used to enable or disable specific UL scheduling functions. SpsSchSwitch: Indicates the switch used to enable or disable semi-persistent scheduling during talk spurts of VoIP services. If this switch is on, semi-persistent scheduling is applied during talk spurts of VoIP services. If this switch is off, dynamic scheduling is applied during talk spurts of VoIP services. SinrAdjustSwitch: Indicates whether to adjust the measured signal to interference plus noise ratio (SINR) based on ACK/NACK in UL hybrid automatic repeat request (HARQ) processes. PreAllocationSwitch: Indicates whether to enable preallocation in the uplink. When this switch is on: (1) If SmartPreAllocationSwitch is off and a UE is in the discontinuous reception (DRX) state, preallocation is disabled for the UE in the uplink; (2) If SmartPreAllocationSwitch is off and the UE is not in the DRX state, preallocation is enabled for the UE in the uplink; (3) If SmartPreAllocationSwitch is on and the SmartPreAllocationDuration parameter value is greater than 0, smart preallocation is enabled for the UE in the uplink; (4) If SmartPreAllocationSwitch is on and the SmartPreAllocationDuration parameter value is 0, preallocation is disabled for the UE in the uplink. If this switch is off, preallocation is disabled for the UE in the uplink. If bearer-level preallocation or bearer-level smart preallocation is enabled for a UE with a QCI class, cell-level preallocation and celllevel smart preallocation do not apply to UEs with the QCI. UlVmimoSwitch: Indicates whether to enable multiuser MIMO (MU-MIMO) in the UL. If this switch is on, the eNodeB performs MU-MIMO pairing among UEs based on related principles. UEs forming a pair transmit data using the same time-frequency resources, which improves system throughput and spectral efficiency. TtiBundlingSwitch: Indicates whether to enable transmission time interval (TTI) bundling. If TTI bundling is enabled, more transmission opportunities are available to UEs within the delay budget for VoIP

Issue 04 (2015-08-31)


172


MO

Parame ter ID

MML Comma nd

Feature ID

10 Parameters

Feature Name

Description

services on the Uu interface, thereby improving uplink coverage. ImIcSwitch: Indicates whether to enable the intermodulation interference (IM) cancellation for UEs. When data is transmitted in both uplink and downlink, two IM components are generated symmetrically beside the Direct Current (DC) subcarrier on the downlink receive channel due to interference from uplink radio signals. If this switch is on, IM component elimination is performed on UEs. If this switch is off, IM component elimination is not performed on UEs. This switch applies only to FDD cells working in frequency band 20. SmartPreAllocationSwitch: Indicates whether to enable uplink smart preallocation when preallocation is enabled (by turning on PreAllocationSwitch). If both PreAllocationSwitch and SmartPreAllocationSwitch are on and SmartPreAllocationDuration is set to a value greater than 0, uplink smart preallocation is enabled; otherwise, uplink smart preallocation is disabled. PuschDtxSwitch: Indicates whether the eNodeB uses the physical uplink shared channel (PUSCH) discontinuous transmission (DTX) detection result during UL scheduling. In an LTE FDD cell, if this switch is on, based on the PUSCH DTX detection result, the eNodeB determines whether to perform adaptive retransmission during UL scheduling and also adjusts the control channel element (CCE) aggregation level of the physical downlink control channel (PDCCH) carrying downlink control information (DCI) format 0. If an FDD cell is established on an LBBPc, this switch takes effect only when the cell uses less than four RX antennas and normal cyclic prefix (CP) in the uplink and the SrsCfgInd parameter in the SRSCfg MO is set to BOOLEAN_TRUE. Note that the LBBPc does not support PUSCH DTX detection for UEs with MUMIMO applied. In an LTE TDD cell, this switch takes effect only when the cell is configured with subframe configuration 2 or 5. After this switch takes effect, the eNodeB adjusts the CCE aggregation level based on the PUSCH DTX detection results. Note that LTE TDD cells established on LBBPc boards do not support PUSCH DTX detection. UlIblerAdjustSwitch: Indicates whether to enable the uplink initial block error rate (IBLER) adjustment Issue 04 (2015-08-31)


173


MO

Parame ter ID

MML Comma nd

Feature ID

10 Parameters

Feature Name

Description

algorithm. If this switch is on, IBLER convergence target is adjusted to increase the cell edge throughput. When this switch is on, the recommended configuration of parameter DopMeasLevel in MO CellUlschAlgo is CLASS_1. UlEnhancedFssSwitch: Indicates whether to enable uplink load-based enhanced frequency selection. This switch applies only to FDD cells. UlIicsAlgoSwitch: Indicates whether to enable the UL IICS algorithm. If this switch is on, interference can be reduced based on accurate detection of user attributes and resource scheduling coordination, thereby increasing the cell edge throughput. This switch applies only to LTE TDD networks. UlEnhancedSrSchSwitch: Indicates whether uplink rescheduling is performed only when the On Duration timer for the DRX long cycle starts. Uplink rescheduling is required if the number of HARQ retransmissions for a scheduling request (SR) reaches the maximum value but the scheduling still fails. If this switch is on, uplink re-scheduling is performed only when the On Duration timer for the DRX long cycle starts. If this switch is off, uplink re-scheduling is performed immediately when the number of HARQ retransmissions for SR reaches the maximum value but the scheduling still fails. It is recommended that the switch be turned on in live networks. SchedulerCtrlPowerSwitch: Indicates whether the uplink scheduler performs scheduling without considering power control restrictions. If this switch is on, the uplink scheduler performs scheduling without considering power control restrictions, which ensures full utilization of the transmit power for all UEs. If this switch is off, the uplink scheduler considers power control restrictions while performing scheduling, which prevents full utilization of the transmit power for UEs at far or medium distances from the cell center. UlMinGbrSwitch: Indicates whether to enable uplink minimum guaranteed bit rate (GBR). If this switch is on, the minimum GBR of non-GBR services is ensured by increasing the scheduling priority of UEs whose non-GBR service rates are lower than the minimum GBR of GBR services. UlMbrCtrlSwitch: Indicates whether to enable uplink scheduling based on the maximum bit rate (MBR) and Issue 04 (2015-08-31)


174


MO

Parame ter ID

MML Comma nd

Feature ID

10 Parameters

Feature Name

Description

guaranteed bit rate (GBR) on the GBR bearer. If this switch is on, the eNodeB performs uplink scheduling on GBR bearers based on the MBR and GBR. If this switch is off, the eNodeB performs uplink scheduling on GBR bearers based only on the GBR. MbrUlSchSwitch: Indicates whether the eNodeB performs uplink scheduling based on MBR. If this switch is on, the eNodeB prioritizes UEs based on the MBRs during uplink scheduling. This parameter applies only to LTE TDD cells. UeAmbrUlSchSwitch: Indicates whether the eNodeB performs uplink scheduling based on the aggregate maximum bit rate (AMBR) of UEs. If this switch is on, the eNodeB prioritizes UEs based on the AMBRs during uplink scheduling. This parameter applies only to LTE TDD cells. UlEnhancedDopplerSwitch: Indicates whether to enable enhanced uplink scheduling based on mobility speed. If this switch is on, enhanced uplink scheduling based on mobility speed is enabled. If this switch is on, the eNodeB determines whether a UE is a lowmobility UE based on the Doppler measurement in the physical layer, and then improves uplink frequency selective scheduling performance for low-mobility UEs. If this switch is off, enhanced uplink scheduling based on mobility speed is disabled. This switch takes effect only when the UlEnhancedDopplerSwitch parameter is set to CLASS_1. This switch does not take effect on cells established on an LBBPc. UlRaUserSchOptSw: Indicates whether the eNodeB raises the scheduling priority of UEs sending uplink access signaling, including MSG5 and the RRC Connection Reconfiguration Complete message. If this switch is on, the eNodeB raises the scheduling priority of UEs sending uplink access signaling. If this switch is off, the eNodeB does not raise the scheduling priority of UEs sending uplink access signaling. UlLast2RetransSchOptSwitch: Indicates whether to enable optimization on the scheduling policy for the last two retransmissions. If this switch is on, optimization on the scheduling policy for the last two retransmissions is enabled. If the UE transmit power is not limited, adaptive retransmission is used and the number of RBs increases in the last two retransmissions to increase the receive success rate of Issue 04 (2015-08-31)


175


MO

Parame ter ID

MML Comma nd

Feature ID

10 Parameters

Feature Name

Description

the last two retransmissions and decrease uplink RBLER. If this switch is off, optimization on the scheduling policy for the last two retransmissions is disabled. This switch does not apply to LTE TDD cells. UlInterfFssSwitch: Indicates whether to enable interference-based uplink frequency-selective scheduling. This switch applies only to LTE FDD networks. UlSmallRBSpectralEffOptSw: Indicates whether to enable spectral efficiency optimization on uplink small RBs. If this switch is on, the optimization is enabled, thereby ensuring that the transmission block size calculated based on optimized spectral efficiency is not less than the traffic volume needs to be scheduled. If this switch is off, the optimization is disabled. PuschUsePucchRbSwitch: Indicates whether PUCCH RBs can be occupied by the PUSCH. In scenarios with a single user, if this switch is on, PUCCH RBs can be occupied by the PUSCH. If this switch is off, PUCCH RBs cannot be occupied by the PUSCH. In scenarios with multiple users, PUCCH RBs cannot be occupied by the PUSCH no matter whether this switch is on or off. PuschDtxSchOptSwitch: If this switch is on, the eNodeB determines whether to perform adaptive retransmission during UL scheduling based on the PUSCH DTX detection result. This switch takes effect only when subframe configuration 2 or 5 is used. If a TDD cell is established on an LBBPc, PUSCH DTX detection is not supported. This switch applies only to LTE TDD cells. PrachRbReuseSwitch:If this switch is on, the PUSCH and PRACH transmissions can use the same resource. If this switch is off, the PUSCH and PRACH transmissions cannot use the same resource. This switch applies only to LTE TDD cells. ULFSSAlgoswitch:If this switch is off, uplink frequency-selective scheduling is disabled. If this switch is on, uplink frequency-selective scheduling is enabled. This switch is invalid if the HighSpeedFlag parameter in the Cell MO is set to HIGH_SPEED(High speed cell flag) or

Issue 04 (2015-08-31)


176


MO

Parame ter ID

MML Comma nd

Feature ID

10 Parameters

Feature Name

Description

ULTRA_HIGH_SPEED(Ultra high speed cell flag), that is, uplink frequency-selective scheduling is disabled in high speed and ultra high speed mobility conditions. This switch applies only to LTE TDD cells. SrSchDataAdptSw: Indicates whether to enable data volume adaption in SR scheduling. Data volume adaption in SR scheduling is enabled only when this option is selected. UlFssUserThdStSwitch: UlFssUserThdStSwitch: Indicates whether to enable the optimization policy on the UE number threshold for frequency selective scheduling. The optimization policy is enabled only when this option is selected. GUI Value Range: SpsSchSwitch(SpsSchSwitch), SinrAdjustSwitch(SinrAdjustSwitch), PreAllocationSwitch(PreAllocationSwitch), UlVmimoSwitch(UlVmimoSwitch), TtiBundlingSwitch(TtiBundlingSwitch), ImIcSwitch(ImIcSwitch), SmartPreAllocationSwitch(SmartPreAllocationSwitch), PuschDtxSwitch(PuschDtxSwitch), UlIblerAdjustSwitch(UlIblerAdjustSwitch), UlEnhancedFssSwitch(UlEnhancedFssSwitch), UlEnhancedSrSchSwitch(UlEnhancedSrSchSwitch), SchedulerCtrlPowerSwitch(SchedulerCtrlPowerSwitch), UlIicsAlgoSwitch(UlIicsAlgoSwitch), UlMinGbrSwitch(UlMinGbrSwitch), UlMbrCtrlSwitch(UlMbrCtrlSwitch), MbrUlSchSwitch(MbrUlSchSwitch), UeAmbrUlSchSwitch(UeAmbrUlSchSwitch), UlEnhancedDopplerSwitch(UlEnhancedDopplerSwitch), UlRaUserSchOptSw(UlRaUserSchOptSw), UlLast2RetransSchOptSwitch(UlLast2RetransSchOpt Switch), UlInterfFssSwitch(UlInterfFssSwitch), UlSmallRBSpectralEffOptSw(UlSmallRBSpectralEfficiencyOptSw), PuschUsePucchRbSwitch(PuschUsePucchRbSwitch), PuschDtxSchOptSwitch(PuschDtxSchOptSwitch), ULFSSAlgoSwitch(ULFSSAlgoSwitch), PrachRbReuseSwitch(PrachRbReuseSwitch), SrSchDataAdptSw(SrSchDataAdptSw), UlFssUserThdStSwitch(UlFssUserThdStSwitch) Unit: None Actual Value Range: SpsSchSwitch, SinrAdjustSwitch, PreAllocationSwitch, UlVmimoSwitch, TtiBundlingSwitch, ImIcSwitch, Issue 04 (2015-08-31)


177


MO

Parame ter ID

MML Comma nd

Feature ID

10 Parameters

Feature Name

Description

SmartPreAllocationSwitch, PuschDtxSwitch, UlIblerAdjustSwitch, UlEnhancedFssSwitch, UlEnhancedSrSchSwitch, SchedulerCtrlPowerSwitch, UlIicsAlgoSwitch, UlMinGbrSwitch, UlMbrCtrlSwitch, MbrUlSchSwitch, UeAmbrUlSchSwitch, UlEnhancedDopplerSwitch, UlRaUserSchOptSw, UlLast2RetransSchOptSwitch, UlInterfFssSwitch, UlSmallRBSpectralEffOptSw, PuschUsePucchRbSwitch, PuschDtxSchOptSwitch, ULFSSAlgoSwitch, PrachRbReuseSwitch, SrSchDataAdptSw, UlFssUserThdStSwitch Default Value: SpsSchSwitch:Off, SinrAdjustSwitch:On, PreAllocationSwitch:On, UlVmimoSwitch:Off, TtiBundlingSwitch:Off, ImIcSwitch:Off, SmartPreAllocationSwitch:Off, PuschDtxSwitch:On, UlIblerAdjustSwitch:Off, UlEnhancedFssSwitch:On, UlEnhancedSrSchSwitch:Off, SchedulerCtrlPowerSwitch:Off, UlIicsAlgoSwitch:Off, UlMinGbrSwitch:Off, UlMbrCtrlSwitch:Off, MbrUlSchSwitch:Off, UeAmbrUlSchSwitch:Off, UlEnhancedDopplerSwitch:Off, UlRaUserSchOptSw:Off, UlLast2RetransSchOptSwitch:Off, UlInterfFssSwitch:Off, UlSmallRBSpectralEffOptSw:Off, PuschUsePucchRbSwitch:Off, PuschDtxSchOptSwitch:Off, ULFSSAlgoSwitch:On, PrachRbReuseSwitch:Off, SrSchDataAdptSw:On, UlFssUserThdStSwitch:Off

Issue 04 (2015-08-31)


178


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

CellMi moPara Cfg

MimoA daptiveS witch

MOD CELLM IMOPA RACFG

LOFD-0 01001

DL 2x2 MIMO

Meaning:

LOFD-0 01003

DL 4x2 MIMO

LST CELLM IMOPA RACFG

LOFD-0 01060 / TDLOF D-00106 0

DL 4X4 MIMO

TDLOF D-00100 1

DL 2x2 MIMO

Indicates the type of adaptive MIMO for a multiantenna eNodeB. The values are described as follows: NO_ADAPTIVE: A fixed MIMO transmission mode is used. That is, transition between MIMO transmission modes is not supported. OL_ADAPTIVE: The open-loop adaptive MIMO transmission mode is used. In this mode, UEs report RANK and CQI values but do not report PMI values to the eNodeB. CL_ADAPTIVE: The closed-loop adaptive MIMO transmission mode is used. In this mode, UEs report RANK, CQI, and PMI values to the eNodeB. OC_ADAPTIVE: UEs switch between the open-loop and closed-loop adaptive MIMO transmission modes automatically. GUI Value Range: NO_ADAPTIVE(NO_ADAPTIVE), OL_ADAPTIVE(OL_ADAPTIVE), CL_ADAPTIVE(CL_ADAPTIVE), OC_ADAPTIVE(OC_ADAPTIVE) Unit: None Actual Value Range: NO_ADAPTIVE, OL_ADAPTIVE, CL_ADAPTIVE, OC_ADAPTIVE Default Value: OL_ADAPTIVE(OL_ADAPTIVE)

Issue 04 (2015-08-31)


179


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

Cell

CrsPort Map

ADD CELL

LOFD-0 01001 / TDLOF D-00100 1

DL 2x2 MIMO

Meaning: Indicates the mapping between a cellspecific reference signal (CRS) port and a transmit (TX) channel in an RRU. In cells with one or two TX channels, this parameter cannot be set. In cells with four or eight TX channels, this parameter can be set. As defined in 3GPP specifications, the CrsPortNum parameter can be set to CRS_PORT_1, CRS_PORT_2, or CRS_PORT_4. The value CRS_PORT_1 indicates that one CRS port (port 0) is configured. The value CRS_PORT_2 indicates that two CRS ports (ports 0 and 1) are configured. The value CRS_PORT_4 indicates that four CRS ports (ports 0, 1, 2 and 3). In values of this parameter, mTnP indicates that the number of TX channels configured for a cell is "m" and the number of CRS 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 indicates that virtual antenna mapping (VAM) is applied, that is, the reference signals transmitted over the CRS port are mapped to corresponding TX channels. For example, the parameter value 4T2P_0101 indicates reference signals transmitted over CRS port 0 are mapped to TX channels 1 and 3 in an RRU, and reference signals transmitted over CRS port 1 are mapped to TX channels 2 and 4 in an RRU. 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.

MOD CELL LST CELL

LOFD-0 01003 / TDLOF D-00100 3 LOFD-0 01060 / TDLOF D-00106 0

DL 4x2 MIMO DL 4x4 MIMO

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),

Issue 04 (2015-08-31)


180


MO

Parame ter ID

MML Comma nd

Feature ID

10 Parameters

Feature Name

Description

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) CellMi moPara Cfg

FixedMi moMod e


LOFD-0 01001

DL 2x2 MIMO

LOFD-0 01003

DL 4x2 MIMO


LOFD-0 01060 / TDLOF D-00106 0

DL 4X4 MIMO

TDLOF D-00100 1

DL 2x2 MIMO

Meaning: Indicates the fixed MIMO transmission mode configured by a multi-antenna eNodeB for UEs. This parameter is valid only when MimoAdaptiveSwitch is set to NO_ADAPTIVE. There are four values. TM2: Transmission mode 2 is permanently applied to UEs. TM3: Transmission mode 3 is permanently applied to UEs. TM4: Transmission mode 4 is permanently applied to UEs. TM6: Transmission mode 6 is permanently applied to UEs. GUI Value Range: TM2(TM2), TM3(TM3), TM4(TM4), TM6(TM6) Unit: None Actual Value Range: TM2, TM3, TM4, TM6 Default Value: TM3(TM3)

Issue 04 (2015-08-31)


181


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

CellMi moPara Cfg

InitialMi moType


LOFD-0 01001 / TDLOF D-00100 1

DL 2x2 MIMO

Meaning:


LOFD-0 01003

DL 4x2 MIMO DL 4X4 MIMO

Indicates the MIMO transmission mode used during initial network access. If this parameter is set to TM2(TM2), the MIMO transmission mode used during initial network access is TM2. If this parameter is set to ADAPTIVE(ADAPTIVE), the MIMO transmission mode used during initial network access is determined by the settings of the MimoAdaptiveSwitch and FixedMimoMode parameters. If the MimoAdaptiveSwitch parameter is set to NO_ADAPTIVE, the initial MIMO transmission mode is determined by the setting of the FixedMimoMode parameter. If the MimoAdaptiveSwitch parameter is set to OL_ADAPTIVE or OC_ADAPTIVE, the initial MIMO transmission mode is TM3. If the MimoAdaptiveSwitch parameter is set to CL_ADAPTIVE, the initial MIMO transmission mode is TM4.

LOFD-0 01060 / TDLOF D-00106 0

GUI Value Range: TM2(TM2), ADAPTIVE(ADAPTIVE) Unit: None Actual Value Range: TM2, ADAPTIVE Default Value: ADAPTIVE(ADAPTIVE) CellDlsc hAlgo

MaxMi moRank Para


LOFD-0 01001 / TDLOF D-00100 1 LOFD-0 01003 / TDLOF D-00100 3 LOFD-0 01060 / TDLOF D-00106 0

Issue 04 (2015-08-31)

DL 2x2 MIMO DL 4x2 MIMO DL 4X4 MIMO

Meaning: Indicates the maximum number of layers (the rank) in the implementation of multiple-input multiple-output (MIMO) in DL scheduling. GUI Value Range: SW_MAX_SM_RANK_1(Rank1), SW_MAX_SM_RANK_2(Rank2), SW_MAX_SM_RANK_4(Rank4) Unit: None Actual Value Range: SW_MAX_SM_RANK_1, SW_MAX_SM_RANK_2, SW_MAX_SM_RANK_4 Default Value: SW_MAX_SM_RANK_2(Rank2)


182


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

Cell

MultiRr uCellFla g

ADD CELL

LOFD-0 03029 / TDLOF D-00107 5

SFN

Meaning: Indicates whether to enable or disable the multi-RRU cell feature.

MOD CELL LST CELL

TDLOF D-00200 8 TDLOF D-00109 8 TDLOF D-00108 0 TDLOF D-00108 1

RruJoint CalPara Cfg

TxChnC alSwitch

MOD RRUJOI NTCAL PARAC FG

Adaptiv e SFN/ SDMA InterBBP SFN

Unit: None

InterBBU SFN

Default Value: BOOLEAN_FALSE(False)

TxChnC alTime

MOD RRUJOI NTCAL PARAC FG LST RRUJOI NTCAL PARAC FG

Actual Value Range: BOOLEAN_FALSE, BOOLEAN_TRUE

InterBBP Adaptiv e SFN/ SDMA

TDLOF D-00108 2

InterBBU Adaptiv e SFN/ SDMA

LOFD-0 01003

DL 4x2 MIMO

LOFD-0 01060

DL 4x4 MIMO

Meaning: Indicates whether TX channel calibration is enabled in a cell with combined RRUs and four TX antennas. GUI Value Range: OFF(Off), ON(On) Unit: None

LST RRUJOI NTCAL PARAC FG RruJoint CalPara Cfg

GUI Value Range: BOOLEAN_FALSE(False), BOOLEAN_TRUE(True)

Actual Value Range: OFF, ON Default Value: OFF(Off)

LOFD-0 01003

DL 4x2 MIMO

LOFD-0 01060

DL 4x4 MIMO

Meaning: Indicates the local time to perform periodic TX channel calibration in a cell with combined RRUs and four TX antennas. This parameter works together with the TxChnCalPeriod parameter to determine the time to perform periodic TX channel calibration. For details, see descriptions of the TxChnCalPeriod parameter. GUI Value Range: 00:00:00~23:59:59 Unit: None Actual Value Range: 00:00:00~23:59:59 Default Value: 03:00:00

Issue 04 (2015-08-31)


183


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description


TxChnC alPeriod

MOD RRUJOI NTCAL PARAC FG

LOFD-0 01003

DL 4x2 MIMO

Meaning:

LOFD-0 01060

DL 4x4 MIMO

LST RRUJOI NTCAL PARAC FG

Indicates the interval at which periodic TX channel calibration is performed in a cell with combined RRUs and four TX antennas. This parameter works together with the TxChnCalTime parameter to determine the time to perform periodic TX channel calibration. The following examples clarify the criteria: (1) If the TxChnCalTime parameter is set to 03:00:00 and the TxChnCalPeriod parameter is set to 48 (indicating that the TX channel calibration period is 24 hours), periodic TX channel calibration is performed at 03:00:00 every day. (2) If the TxChnCalTime parameter is set to 03:00:00 and the TxChnCalPeriod parameter is set to 24 (indicating that the TX channel calibration period is 12 hours), periodic TX channel calibration is performed at 03:00:00 and 15:00:00 every day. (3) If the TxChnCalTime parameter is set to 03:00:00 and the TxChnCalPeriod parameter is set to 96 (indicating that the TX channel calibration period is 48 hours), periodic TX channel calibration is performed at 03:00:00 every other day. GUI Value Range: 1~1440 Unit: 0.5h Actual Value Range: 0.5~720 Default Value: 48


TxChnA ntSpacin g

MOD RRUJOI NTCAL PARAC FG LST RRUJOI NTCAL PARAC FG

Issue 04 (2015-08-31)

LOFD-0 01003

DL 4x2 MIMO

LOFD-0 01060

DL 4x4 MIMO

Meaning: Indicates the horizontal distance between two combined physical antennas. The horizontal distance is used for TX channel calibration in a cell with combined RRUs. GUI Value Range: 0~100 Unit: 0.1m Actual Value Range: 0~10 Default Value: 0


184


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

CellCqi Adaptiv eCfg

CqiPerio dAdapti ve

MOD CELLC QIADA PTIVEC FG

LBFD-0 02025

Basic Scheduli ng

Meaning: Indicates whether to enable CQI reporting period adaptation. If this parameter is set to ON(On), the CQI reporting period adaptively changes based on the air interface load of the cell. If this parameter is set to OFF(Off), the CQI reporting period is specified by the UserCqiPeriod parameter.

LST CELLC QIADA PTIVEC FG

LOFD-0 0101502 TDLOF D-00104 9 TDLOF D-00106 1

Dynami c Scheduli ng Single Streami ng Beamfor ming

GUI Value Range: OFF(Off), ON(On) Unit: None Actual Value Range: OFF, ON Default Value: ON(On)

Dual Streami ng Beamfor ming CellCqi Adaptiv eCfg

UserCqi Period


LBFD-0 02025 / TDLBF D-00202 5


LOFD-0 0101502 / TDLOF D-00101 502

Basic Scheduli ng Dynami c Scheduli ng

Meaning: Indicates the fixed CQI reporting period. This parameter takes effect only if the CqiPeriodAdaptive parameter is set to OFF(Off). If the UserCqiPeriod parameter is set to ms2(2ms), the period is automatically changed to 5ms for the TDD cell. GUI Value Range: ms2(2ms), ms5(5ms), ms10(10ms), ms20(20ms), ms40(40ms), ms80(80ms), ms160(160ms) Unit: ms Actual Value Range: ms2, ms5, ms10, ms20, ms40, ms80, ms160 Default Value: ms40(40ms)

Issue 04 (2015-08-31)


185


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

CellCqi Adaptiv eCfg

HoAperi odicCqi CfgSwit ch


LBFD-0 02025 / TDLBF D-00202 5

Basic Scheduli ng


LOFD-0 0101502 / TDLOF D-00101 502

Meaning: Indicates the aperiodic CQI resource configurations and the triggering condition of aperiodic CQI reporting during handovers. If this parameter is set to ON(On), aperiodic CQI resource configurations are included in handover commands. When no periodic CQI resources are configured for a UE, an aperiodic CQI reporting is triggered when the handed-over UE receives data. If this parameter is set to OFF(Off), aperiodic CQI resource configurations are not included in handover commands. The aperiodic CQI resource is configured after the UE is handed over.

Dynami c Scheduli ng

GUI Value Range: OFF(Off), ON(On) Unit: None Actual Value Range: OFF, ON Default Value: OFF(Off) CqiAda ptiveCfg

PucchPe riodicCq iOptSwi tch

MOD CQIAD APTIVE CFG LST CQIAD APTIVE CFG

LBFD-0 02003

Physical Channel Manage ment

Meaning: Indicates whether to enable the optimization on CQI reporting periods and PUCCH resources for CQI reporting. If this switch is turned on, the eNodeB configures less UEs with a short CQI reporting period, decreasing PUCCH resources to be used and increasing available PUSCH resources. If this switch is turned off, the eNodeB configures more UEs with a short CQI reporting period, increasing PUCCH resources to be used and decreasing available PUSCH resources.This parameter applies only to LTE FDD cells. GUI Value Range: OFF(Off), ON(On) Unit: None Actual Value Range: OFF, ON Default Value: ON(On)

Issue 04 (2015-08-31)


186


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

CellAlg oSwitch

DlSchS witch


LOFD-0 01016 / TDLOF D-00101 6

VoIP Semipersisten t Scheduli ng

Meaning:


LOFD-0 0101502 / TDLOF D-00101 502 LOFD-0 01109 / TDLOF D-00110 9 LOFD-0 01070 / TDLOF D-00107 0 TDLOF D-07022 4 LBFD-0 02025 / TDLBF D-00202 5 LBFD-0 02031 / TDLBF D-00203 1 LBFD-0 70102 / TDLBF D-07010 2 LBFD-0 60202

Issue 04 (2015-08-31)

Dynami c Scheduli ng DL NonGBR Packet Bundlin g Symbol Power Saving Scheduli ng Based on Max Bit Rate Basic Scheduli ng Support of aperiodi c CQI reports MBR>G BR Configu ration Enhance d DL Frequen cy Selectiv e

Indicates the switches related to downlink scheduling in the cell. FreqSelSwitch: Indicates whether to enable frequency selective scheduling. If this switch is on, data is transmitted on the frequency band in good signal quality. ServiceDiffSwitch: Indicates whether to enable service differentiation. If this switch is on, service differentiation is applied. If this switch is off, service differentiation is not applied. SpsSchSwitch: Indicates whether to enable semipersistent scheduling during talk spurts of VoIP services. If this switch is on, semi-persistent scheduling is applied during talk spurts of VoIP services. If this switch is off, dynamic scheduling is applied during talk spurts of VoIP services. MBSFNShutDownSwitch: Indicates whether to enable Multimedia Broadcast multicast service Single Frequency Network (MBSFN) subframe shutdown. If this switch is on, MBSFN subframe shutdown is applied. If this switch is off, MBSFN subframe shutdown is not applied. This switch is valid only when SymbolShutdownSwitch is on. If the MBSFN shutdown switch is on, the setting of the switch for mapping SIBs to SI messages becomes invalid. The latter can be specified by the SiMapSwitch parameter in the CellSiMap MO. If the MBSFN subframe shutdown switch is off, the setting of the switch for mapping SIBs to SI messages becomes valid. MBSFN subframe shutdown applies only to LTE-only base stations. NonGbrBundlingSwitch: Indicates whether to enable downlink non-GBR packet bundling. If this switch is on, delay of non-GBR services can be controlled in non-congestion scenarios. If this switch is off, delay of non-GBR services cannot be controlled. EnAperiodicCqiRptSwitch: Indicates whether to enable enhanced aperiodic channel quality indicator (CQI) reporting. If this switch is on, the eNodeB triggers aperiodic CQI reporting for a UE based on downlink services of the UE and the interval at which the UE sends periodic CQI reports. If this switch is off, UEs under non-frequency selective scheduling do not trigger aperiodic CQI reporting based on downlink


187


MO

Parame ter ID

MML Comma nd

Feature ID

10 Parameters

Feature Name

Description

services and triggers an aperiodic CQI reporting if no valid periodic CQI reports are sent in eight consecutive periodic CQI reporting periods. DlMbrCtrlSwitch: Indicates whether to enable downlink scheduling based on the maximum bit rate (MBR) and guaranteed bit rate (GBR) on the GBR bearer. If this switch is on, the eNodeB performs downlink scheduling on GBR bearers based on the MBR and GBR. If this switch is off, the eNodeB performs downlink scheduling on GBR bearers based on the GBR only. MbrDlSchSwitch: Indicates whether the eNodeB performs downlink scheduling based on MBR. If this switch is on, the eNodeB determines priorities of UEs based on the MBR in downlink scheduling. This parameter applies only to LTE TDD cells. UeAmbrDlSchSwitch: Indicates whether the eNodeB performs downlink scheduling based on the aggregate maximum bit rate (AMBR) of UEs. If this switch is on, the eNodeB determines priorities of UEs based on the AMBR of UEs in downlink scheduling. This parameter applies only to LTE TDD cells. EpfEnhancedSwitch: Indicates whether to enable enhanced proportional fair (EPF) for downlink scheduling. EPF for downlink scheduling is enabled only when this switch is on. AperiodicCqiTrigOptSwitch: Indicates whether to trigger aperiodic CQI optimization. If this switch is on, a UE performing initial access triggers aperiodic CQI reporting based on related triggering conditions after the DLMAC instance has been established for 200 ms and the eNodeB receives MSG5. Consider that aperiodic CQI reporting is triggered by invalid CQI reports in eight consecutive CQI reporting periods. If cyclic redundancy check (CRC) on aperiodic CQI reports fails, aperiodic CQI reporting is not repeatedly triggered when DRX is enabled; or aperiodic CQI reporting is triggered after eight TTIs when DRX is disabled. If this switch is off, a UE performing initial access triggers aperiodic CQI reporting based on related triggering conditions after the DLMAC instance has been established for 200 ms. Consider that aperiodic CQI reporting is triggered by invalid CQI reports in eight consecutive CQI reporting periods. If CRC on aperiodic CQI reports fails,

Issue 04 (2015-08-31)


188


MO

Parame ter ID

MML Comma nd

Feature ID

10 Parameters

Feature Name

Description

aperiodic CQI reporting is triggered after eight TTIs regardless of the DRX status. VoipTbsBasedMcsSelSwitch: Indicates whether the modulation and coding scheme (MCS) index is selected based on the transport block size (TBS) in downlink scheduling for VoIP services. If this switch is on, the MCS index is selected based on the TBS in downlink scheduling for VoIP services. If this switch is off, the MCS index is not selected based on the TBS in downlink scheduling for VoIP services. UeSigMcsEnhanceSwitch: Indicates whether to enable or disable the optimized MCS algorithm for UE signaling. The optimized MCS algorithm for UE signaling takes effect after this switch is on. This parameter applies only to LTE TDD cells. PagingInterfRandSwitch: Indicates whether to enable or disable interference randomizing for paging messages. If this switch is on, interference randomizing is enabled for paging messages. This switch is valid only in TDD mode. DlSingleUsrMcsOptSwitch: Indicates conditions for lowering the modulation and coding scheme (MCS) for a single UE. When this switch is on, the MCS can be lowered for a UE if the UE is the only UE to be scheduled in a transmission time interval (TTI). When this switch is off, the MCS can be lowered for a UE if there are only 10 percent of TTIs having UEs to schedule in each sparse packet determination period and the UE is the only UE to be scheduled in each TTI. SubframeSchDiffSwitch: Indicates whether subframes 3 and 8 perform scheduling based on increased number of uplink scheduling UEs when subframe configuration type 2 is used. If this switch is on, subframes 3 and 8 perform scheduling based on increased number of uplink scheduling UEs when subframe configuration type 2 is used. If this switch is off, subframes 3 and 8 perform scheduling based on the policy that other downlink subframes adopt when subframe configuration type 2 is used. This switch is dedicated to LTE TDD cells. TailPackagePriSchSwitch: Indicates the switch that controls the scheduling of downlink connected tail packages in the bearer. If this switch is on, the connected tail package is scheduled preferentially in Issue 04 (2015-08-31)


189


MO

Parame ter ID

MML Comma nd

Feature ID

10 Parameters

Feature Name

Description

the next TTI, which reduces the delay and increases the transmission rate. If this switch is off, the scheduling strategy of the connected tail package is the same as other downlink subframes. This switch is dedicated to LTE TDD cells. FreqSelJudgeIgnorDopplerSwitch: Indicates whether Doppler determination conditions are considered during channel frequency selective scheduling determination. Doppler determination conditions are considered only when this option is deselected. This option applies only to LTE FDD. SIB1InterfRandSwitch: Indicates whether to enable SIB1 interference randomizing. If this switch is on, interference randomizing is enabled for SIB1. This switch applies only to LTE TDD cells. GUI Value Range: FreqSelSwitch(FreqSelSwitch), ServiceDiffSwitch(ServiceDiffSwitch), SpsSchSwitch(SpsSchSwitch), MBSFNShutDownSwitch(MBSFNShutDownSwitch), NonGbrBundlingSwitch(NonGbrBundlingSwitch), EnAperiodicCqiRptSwitch(EnAperiodicCqiRptSwitch), DlMbrCtrlSwitch(DlMbrCtrlSwitch), MbrDlSchSwitch(MbrDlSchSwitch), UeAmbrDlSchSwitch(UeAmbrDlSchSwitch), EpfEnhancedSwitch(EpfEnhancedSwitch), AperiodicCqiTrigOptSwitch(AperiodicCqiTrigOptSwitch), VoipTbsBasedMcsSelSwitch(VoipTbsBasedMcsSelSwitch), PagingInterfRandSwitch(PagingInterfRandSwitch), DlSingleUsrMcsOptSwitch(DlSingleUsrMcsOptSwitch), SubframeSchDiffSwitch(SubframeSchDiffSwitch), TailPackagePriSchSwitch(TailPackagePriSchSwitch), UeSigMcsEnhanceSwitch(UeSigMcsEnhanceSwitch), FreqSelJudgeIgnorDopplerSwitch(FreqSelJudgeIgnorDopplerSwitch), SIB1InterfRandSwitch(SIB1InterfRandSwitch) Unit: None Actual Value Range: FreqSelSwitch, ServiceDiffSwitch, SpsSchSwitch, MBSFNShutDownSwitch, NonGbrBundlingSwitch, EnAperiodicCqiRptSwitch, DlMbrCtrlSwitch, MbrDlSchSwitch, UeAmbrDlSchSwitch, EpfEnhancedSwitch, AperiodicCqiTrigOptSwitch, VoipTbsBasedMcsSelSwitch, PagingInterfRandSwitch, DlSingleUsrMcsOptSwitch, SubframeSchDiffSwitch, TailPackagePriSchSwitch, Issue 04 (2015-08-31)


190


MO

Parame ter ID

MML Comma nd

Feature ID

10 Parameters

Feature Name

Description

UeSigMcsEnhanceSwitch, FreqSelJudgeIgnorDopplerSwitch, SIB1InterfRandSwitch Default Value: FreqSelSwitch:Off, ServiceDiffSwitch:Off, SpsSchSwitch:Off, MBSFNShutDownSwitch:Off, NonGbrBundlingSwitch:Off, EnAperiodicCqiRptSwitch:Off, DlMbrCtrlSwitch:Off, MbrDlSchSwitch:Off, UeAmbrDlSchSwitch:Off, EpfEnhancedSwitch:Off, AperiodicCqiTrigOptSwitch:Off, VoipTbsBasedMcsSelSwitch:Off, PagingInterfRandSwitch:Off, DlSingleUsrMcsOptSwitch:Off, SubframeSchDiffSwitch:Off, TailPackagePriSchSwitch:Off, UeSigMcsEnhanceSwitch:Off, FreqSelJudgeIgnorDopplerSwitch:Off, SIB1InterfRandSwitch:On CellPdc chAlgo

PdcchSy mNumS witch

MOD CELLP DCCHA LGO LST CELLP DCCHA LGO

LBFD-0 02003 / TDLBF D-00200 3


Meaning: Indicates the switch used to enable or disable dynamic adjustment on the number of orthogonal frequency division multiplexing (OFDM) symbols occupied by the physical downlink control channel (PDCCH). If this parameter is set to OFF, the number of OFDM symbols occupied by the PDCCH is fixed and cannot be dynamically adjusted. If this parameter is set to ON, the number of OFDM symbols occupied by the PDCCH is dynamically adjusted based on the required number of PDCCH control channel elements (CCEs). If this parameter is set to ECFIADAPTIONON, the number of OFDM symbols occupied by the PDCCH is dynamically adjusted based on the cell downlink throughput, and the adjustment performance is the best among the three methods. GUI Value Range: OFF(Off), ON(On), ECFIADAPTIONON(Enhanced CFI Adaption On) Unit: None Actual Value Range: OFF, ON, ECFIADAPTIONON Default Value: ON(On)

Issue 04 (2015-08-31)


191


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

CellDlsc hAlgo

FDUEE nhAper CQITrig Period

MOD CELLD LSCHA LGO

LBFD-0 60202

Enhance d DL Frequen cy Selectiv e

Meaning: Indicates the aperiodic channel quality indicator (CQI) reporting period of a UE adopting frequency diversity (FD) scheduling. This parameter can be set to 5ms, 10ms, 20ms, 40ms, 80ms, 160ms, and inf. The parameter value inf indicates that the aperiodic CQI reporting is not triggered. This parameter applies only to LTE FDD.

LST CELLD LSCHA LGO

TDLOF D-00101 502 LOFD-0 0101502

Dynami c Scheduli ng Dynami c Scheduli ng

Drx

DrxAlg Switch

MOD DRX LST DRX

LBFD-0 02017 / TDLBF D-00201 7

DRX

GUI Value Range: 5ms, 10ms, 20ms, 40ms, 80ms, 160ms, inf Unit: None Actual Value Range: 5ms, 10ms, 20ms, 40ms, 80ms, 160ms, inf Default Value: 5ms Meaning: Indicates the DRX switch. The setting of this parameter has no effect on dynamic DRX. DRX applies to a CA UE only when this parameter is set to ON(On) on both eNodeBs to which the PCell and SCell of the CA UE belong. GUI Value Range: OFF(Off), ON(On) Unit: None Actual Value Range: OFF, ON Default Value: OFF(Off)

CellDlsc hAlgo

DlRank Optimiz eSwitch


LBFD-0 02025 / TDLBF D-00202 5 LOFD-0 0101502 / TDLOF D-00101 502 LOFD-0 01060 / TDLOF D-00106 0 LOFD-0 01001 / TDLOF D-00100 1

Issue 04 (2015-08-31)

Basic Scheduli ng Dynami c Scheduli ng DL 4X4 MIMO DL 2X2 MIMO

Meaning: Indicates whether to perform downlink rank optimization. If this parameter is set to OFF, the eNodeB uses the rank received from a UE to schedule the UE. If the baseband processing unit determines that the received rank is unsuitable for UE scheduling, the eNodeB schedules the UE based on rank 1. If this parameter is set to ON, the eNodeB optimizes the received rank and schedules the UE based on the optimized rank. If the baseband processing unit determines that the received rank is unsuitable for UE scheduling, the eNodeB does not optimize the received rank and schedules the UE based on the rank used last time. GUI Value Range: OFF(Off), ON(On) Unit: None Actual Value Range: OFF, ON Default Value: OFF(Off)


192


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

SRSCfg

SrsCfgI nd

MOD SRSCF G

LBFD-0 02003 / TDLBF D-00200 3


Meaning: Indicates whether to configure sounding reference signal (SRS) resources for UEs in a cell. The value BOOLEAN_TRUE indicates that SRS resources are available in the cell and can be configured for UEs in the cell. The value BOOLEAN_FALSE indicates that no SRS resource is available in the cell, and therefore no UE in the cell is configured with SRS resources. This parameter does not take effect on: (1) FDD cell that is established on an LBBPc and uses four or more RX antennas. (2) FDD cell that is established on an LBBPc and uses extended cyclic prefix (CP) in the uplink. (3) TDD cell established on an LBBPc. If this parameter does not take effect on a cell but SRS resources are available in the cell, SRS resources can be configured for UEs in the cell.

LST SRSCF G

GUI Value Range: BOOLEAN_FALSE(False), BOOLEAN_TRUE(True) Unit: None Actual Value Range: BOOLEAN_FALSE, BOOLEAN_TRUE Default Value: BOOLEAN_TRUE(True)

Issue 04 (2015-08-31)


193


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

SRSCfg

FddSrsC fgMode

MOD SRSCF G

None

None

Meaning: Indicates the allocation mode of sounding reference signal (SRS) resources in LTE FDD. This parameter must be set when the SrsCfgInd parameter is set to BOOLEAN_TRUE(True). If the FddSrsCfgMode parameter is set to 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.

LST SRSCF G

GUI Value Range: DEFAULTMODE(Default Mode), ADAPTIVEMODE(Adaptive Mode) Unit: None Actual Value Range: DEFAULTMODE, ADAPTIVEMODE Default Value: ADAPTIVEMODE(Adaptive Mode) SECTO R

SECTO RID

ADD SECTO R DSP SECTO R

None

None

Meaning: Indicates the number of the sector. GUI Value Range: 0~65535 Unit: None Actual Value Range: 0~65535 Default Value: None

LST SECTO R MOD SECTO R RMV SECTO R

Issue 04 (2015-08-31)


194


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

SECTO REQM

SECTO REQMI D

ADD SECTO REQM

None

None

Meaning: Indicates the number of the sector equipment. GUI Value Range: 0~65535

LST SECTO REQM

Unit: None

MOD SECTO REQM

Default Value: None

Actual Value Range: 0~65535

RMV SECTO REQM LST SECTO R

Issue 04 (2015-08-31)


195


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

Cell

LocalCe llId

ACT CELL

None

None

Meaning: Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

ADD CELL


ADD CELLB AND


Unit: None Default Value: None

BLK CELL DEA CELL DSP CELL DSP CELLP HYTOP O DSP CELLU LCOMP CLUST ER DSP LIOPTR ULE DSP PRIBBP ADJUS T LST CELL LST CELLB AND MOD CELL RMV CELL RMV CELLB AND RMV CELLN RT Issue 04 (2015-08-31)


196


MO

Parame ter ID

MML Comma nd

10 Parameters

Feature ID

Feature Name

Description

None

None

Meaning: Indicates the transmission and reception mode of the cell.

STR CELLR FLOOP BACK STR CELLS ELFTES T STR LRTWP RTTST STR PRIBBP ADJUS T UBL CELL DSP LRTWP RTTST DSP PRIBBP RESINF O Cell

TxRxM ode

ADD CELL MOD CELL

GUI Value Range: 1T1R, 1T2R, 2T2R, 2T4R, 4T4R, 8T8R, 2T8R, 4T8R

LST CELL

Unit: None Actual Value Range: 1T1R, 1T2R, 2T2R, 2T4R, 4T4R, 8T8R, 2T8R, 4T8R Default Value: None

Issue 04 (2015-08-31)


197


10 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

CellAlg oSwitch

LocalCe llId

DSP CELLU LCAMC CLUST ER

None

None

Meaning: Indicates the local ID of the cell. It uniquely identifies a cell within a BS. GUI Value Range: 0~255 Unit: None Actual Value Range: 0~255


Default Value: None

MOD CELLA LGOSW ITCH SRSCfg

CellMi moPara Cfg

LocalCe llId

LocalCe llId

DSP SRSCF G

None

None


LST SRSCF G

Unit: None

MOD SRSCF G

Default Value: None



None

None

LocalCe llId

Issue 04 (2015-08-31)

DSP LBT

Meaning: Indicates the local cell ID. It uniquely identifies a cell within an eNodeB. GUI Value Range: 0~255 Unit: None

MOD CELLM IMOPA RACFG CellDlsc hAlgo


Actual Value Range: 0~255 Default Value: None None

None


LST CELLD LSCHA LGO


MOD CELLD LSCHA LGO

Default Value: None

Unit: None Actual Value Range: 0~255


198


11 Counters

11

Counters

Table 11-1 Counters Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526727378

L.Traffic.User.Avg

Average number of users in a cell

Multi-mode: None

RRC Connection Management

GSM: None UMTS: None LTE: LBFD-002007

RRC Connection Management

TDLBFD-002007 1526727391

L.ChMeas.MIMO.P RB.CL.Rank1

Total number of used downlink PRBs in closedloop rank 1 mode

Multi-mode: None

Basic Scheduling

GSM: None

Basic Scheduling

UMTS: None

DL 2x2 MIMO

LTE: LBFD-002025

DL 4x2 MIMO

TDLBFD-002025

Adaptive SFN/ SDMA

LOFD-001001

DL 4X4 MIMO

LOFD-001003 LOFD-001060 LOFD-070205

Issue 04 (2015-08-31)


199


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526727392



Multi-mode: None

Basic Scheduling

GSM: None

Basic Scheduling

UMTS: None

DL 2x2 MIMO

LTE: LBFD-002025

DL 4x2 MIMO

TDLBFD-002025

Adaptive SFN/ SDMA

LOFD-001001

DL 4X4 MIMO

LOFD-001003 LOFD-001060 LOFD-070205 1526727393

L.ChMeas.MIMO.P RB.OL.Rank1

Total number of used downlink PRBs in open-loop rank 1 mode

Multi-mode: None

Basic Scheduling

GSM: None

Basic Scheduling

UMTS: None

DL 2x2 MIMO

LTE: LBFD-002025

DL 4x2 MIMO

TDLBFD-002025 LOFD-001001

Adaptive SFN/ SDMA

LOFD-001003

DL 2x2 MIMO

DL 4X4 MIMO

LOFD-001060 LOFD-070205 TDLOFD-001001 1526727394



Multi-mode: None

Basic Scheduling

GSM: None

Basic Scheduling

UMTS: None

DL 2x2 MIMO

LTE: LBFD-002025

DL 4x2 MIMO

TDLBFD-002025 LOFD-001001

Adaptive SFN/ SDMA

LOFD-001003

DL 2x2 MIMO

DL 4X4 MIMO

LOFD-001060 LOFD-070205 TDLOFD-001001

Issue 04 (2015-08-31)


200


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526727441

L.ChMeas.PUSCH. MCS.29

Number of times MCS index 29 is scheduled on the PUSCH

Multi-mode: None

Basic Scheduling

GSM: None

Basic Scheduling

UMTS: None

Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM

LTE: LBFD-002025 TDLBFD-002025 LBFD-001005 TDLBFD-001005 LOFD-001006 TDLOFD-001006 1526728174



Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM UL 64QAM UL 64QAM

Multi-mode: None

Basic Scheduling

GSM: None

Basic Scheduling

UMTS: None

DL 4X4 MIMO

LTE: LBFD-002025

Adaptive SFN/ SDMA

TDLBFD-002025 LOFD-001060 LOFD-070205 1526728175



Multi-mode: None

Basic Scheduling

GSM: None

Basic Scheduling

UMTS: None

DL 4X4 MIMO

LTE: LBFD-002025

Adaptive SFN/ SDMA

TDLBFD-002025 LOFD-001060 LOFD-070205 1526728176



Multi-mode: None

Basic Scheduling

GSM: None

Basic Scheduling

UMTS: None

DL 4X4 MIMO

LTE: LBFD-002025

Adaptive SFN/ SDMA

TDLBFD-002025 LOFD-001060 LOFD-070205

Issue 04 (2015-08-31)


201


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728177



Multi-mode: None

Basic Scheduling

GSM: None

Basic Scheduling

UMTS: None

DL 4X4 MIMO

LTE: LBFD-002025

Adaptive SFN/ SDMA

TDLBFD-002025 LOFD-001060 LOFD-070205 1526728232

L.Thrp.Time.Cell.D L

Total duration of downlink data transmission in a cell

Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008

Radio Bearer Management Radio Bearer Management Basic Scheduling Basic Scheduling

LBFD-002025 TDLBFD-002025 1526728261

L.Thrp.bits.DL

Total downlink traffic volume for PDCP SDUs in a cell


Radio Bearer Management Radio Bearer Management Basic Scheduling Basic Scheduling

LBFD-002025 TDLBFD-002025 1526728349

L.ChMeas.VMIMO .PairPRB.Succ

Number of RBs that are successfully paired for VMIMO UEs in a cell

Multi-mode: None

UL 2x4 MU-MIMO

GSM: None

2*8 MU-MIMO

UMTS: None

UL 2x2 MU-MIMO

LTE: TDLOFD-001058

UL 2x4 MU-MIMO

TDSLBFD-0307 LOFD-001002 LOFD-001058

Issue 04 (2015-08-31)


202


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728350

L.ChMeas.VMIMO .PairPRB.Tot

Number of RBs that can be paired for VMIMO UEs in a cell

Multi-mode: None

UL 2x4 MU-MIMO

GSM: None

2*8 MU-MIMO

UMTS: None

UL 2x2 MU-MIMO

LTE: TDLOFD-001058

UL 2x4 MU-MIMO

TDSLBFD-0307 LOFD-001002 LOFD-001058 1526728351

L.ChMeas.MUBF.P airPRB.Succ

Number of RBs that are successfully paired for MUBF UEs in a cell

Multi-mode: None

MU-Beamforming

GSM: None UMTS: None LTE: TDLOFD-001077

1526728599

L.ChMeas.PRB.DL .RANK1.MCS.0

Number of PRBs on the PDSCH in rank 1 mode using MCS index 0 for scheduling in a cell

Multi-mode: None GSM: None UMTS: None LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003


LOFD-001060 TDLBFD-001005 TDLOFD-001001 1526728600



Multi-mode: None GSM: None UMTS: None

DL 4x2 MIMO

DL 2x2 MIMO Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM

LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003


LOFD-001060 TDLBFD-001005 TDLOFD-001001

Issue 04 (2015-08-31)



DL 4x2 MIMO

DL 2x2 MIMO

203


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728601



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003


TDLOFD-001001 Number of PRBs on the PDSCH in rank 1 mode using MCS index 4 for scheduling in a cell


DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)

Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM DL 2x2 MIMO

TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728603

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

204


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728604



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728606

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

205


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728607



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728609

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

206


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728610



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728612

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

207


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728613



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728615

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

208


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728616



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728618

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

209


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728619



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728621

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

210


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728622



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728624

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

211


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728625



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728627

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

212


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728628



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728630

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

213


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728631



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728633

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

214


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728634



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728636

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

215


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728637



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728639

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

216


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728640



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728642

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

217


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728643



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728645

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

218


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728646



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728648

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

219


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728649



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728651

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

220


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728652



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728654

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

221


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728655



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728657

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

222


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728658



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526728660

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

223


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526728661



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003


TDLOFD-001001 Number of TBs transmitted in downlink closedloop rank 1 mode


TDLBFD-001005

L.Traffic.DL.SCH. TB.CL.Rank1

DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526729281

DL 4x2 MIMO

DL 4x2 MIMO

DL 2x2 MIMO

Multi-mode: None

DL 2x2 MIMO

GSM: None

DL 4x2 MIMO

UMTS: None

DL 4X4 MIMO

LTE: LOFD-001001

Transport Channel Management

LOFD-001003

DL 2x2 MIMO

LOFD-001060


LBFD-002002 TDLOFD-001001 TDLBFD-002002

Issue 04 (2015-08-31)


224


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526729282


Number of TBs transmitted in downlink closedloop rank 2 mode

Multi-mode: None

DL 2x2 MIMO

GSM: None

DL 4x2 MIMO

UMTS: None

DL 4X4 MIMO

LTE: LOFD-001001


LOFD-001003

DL 2x2 MIMO

LOFD-001060


LBFD-002002 TDLOFD-001001 TDLBFD-002002 1526729283

L.Traffic.DL.SCH. TB.OL.Rank1

Number of TBs transmitted in downlink open-loop rank 1 mode

Multi-mode: None

DL 2x2 MIMO

GSM: None

DL 4x2 MIMO

UMTS: None

DL 4X4 MIMO

LTE: LOFD-001001


LOFD-001003

DL 2x2 MIMO

LOFD-001060





Multi-mode: None

DL 2x2 MIMO

GSM: None

DL 4x2 MIMO

UMTS: None

DL 4X4 MIMO

LTE: LOFD-001001


LOFD-001003

DL 2x2 MIMO

LOFD-001060



Issue 04 (2015-08-31)


225


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526729285



Multi-mode: None

DL 2x2 MIMO

GSM: None

DL 4x2 MIMO

UMTS: None

DL 4X4 MIMO

LTE: LOFD-001001


LOFD-001003

DL 2x2 MIMO

LOFD-001060





Multi-mode: None

DL 2x2 MIMO

GSM: None

DL 4x2 MIMO

UMTS: None

DL 4X4 MIMO

LTE: LOFD-001001


LOFD-001003

DL 2x2 MIMO

LOFD-001060





Multi-mode: None

DL 2x2 MIMO

GSM: None

DL 4x2 MIMO

UMTS: None

DL 4X4 MIMO

LTE: LOFD-001001


LOFD-001003

DL 2x2 MIMO

LOFD-001060



Issue 04 (2015-08-31)


226


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526729288



Multi-mode: None

DL 2x2 MIMO

GSM: None

DL 4x2 MIMO

UMTS: None

DL 4X4 MIMO

LTE: LOFD-001001


LOFD-001003

DL 2x2 MIMO

LOFD-001060



L.ChMeas.CQI.DL. SingleCW.Aperiodi c.5

Number of aperiodic wideband CQI reports with the value of 5 in single-codeword transmission

Multi-mode: None GSM: None

Dynamic Downlink Power Allocation

UMTS: None

Basic Scheduling

LTE: LBFD-002016


LBFD-002025

Basic Scheduling

TDLBFD-002016 TDLBFD-002025 1526729350

L.ChMeas.CQI.DL. SingleCW.Aperiodi c.15

Number of aperiodic wideband CQI reports with the value of 15 in single-codeword transmission



UMTS: None

Basic Scheduling

LTE: LBFD-002016


LBFD-002025

Basic Scheduling

TDLBFD-002016 TDLBFD-002025 1526729367

L.ChMeas.CQI.DL. DualCW.Code0.Ap eriodic.0

Number of aperiodic wideband CQI reports with the value of 0 for codeword 0 in dualcodeword transmission



UMTS: None

Basic Scheduling

LTE: LBFD-002016


LBFD-002025

Basic Scheduling

TDLBFD-002016 TDLBFD-002025

Issue 04 (2015-08-31)


227


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526729382





UMTS: None

Basic Scheduling

LTE: LBFD-002016


LBFD-002025

Basic Scheduling

TDLBFD-002016 TDLBFD-002025 1526729399





UMTS: None

Basic Scheduling

LTE: LBFD-002016


LBFD-002025

Basic Scheduling

TDLBFD-002016 TDLBFD-002025 1526729414





UMTS: None

Basic Scheduling

LTE: LBFD-002016


LBFD-002025

Basic Scheduling

TDLBFD-002016 TDLBFD-002025 1526729455

L.Traffic.DL.SCH. TB.TM1

Number of TBs transmitted in downlink TM1 mode

Multi-mode: None

DL 2x2 MIMO

GSM: None

DL 4x2 MIMO

UMTS: None

DL 4X4 MIMO

LTE: LOFD-001001


LOFD-001003

DL 2x2 MIMO

LOFD-001060



Issue 04 (2015-08-31)


228


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526729456



Multi-mode: None

DL 2x2 MIMO

GSM: None

DL 4x2 MIMO

UMTS: None

DL 4X4 MIMO

LTE: LOFD-001001


LOFD-001003

DL 2x2 MIMO

LOFD-001060





Multi-mode: None

DL 2x2 MIMO

GSM: None

DL 4x2 MIMO

UMTS: None

DL 4X4 MIMO

LTE: LOFD-001001


LOFD-001003

DL 2x2 MIMO

LOFD-001060





Multi-mode: None

DL 2x2 MIMO

GSM: None

DL 4x2 MIMO

UMTS: None

DL 4X4 MIMO

LTE: LOFD-001001


LOFD-001003

DL 2x2 MIMO

LOFD-001060



Issue 04 (2015-08-31)


229


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526729459


Number of TBs transmitted in downlink TM5 mode. TDD Only.

Multi-mode: None

DL 2x2 MIMO

GSM: None

DL 4x2 MIMO

UMTS: None

DL 4X4 MIMO

LTE: LOFD-001001


LOFD-001003

DL 2x2 MIMO

LOFD-001060





Multi-mode: None

DL 2x2 MIMO

GSM: None

DL 4x2 MIMO

UMTS: None

DL 4X4 MIMO

LTE: LOFD-001001


LOFD-001003

DL 2x2 MIMO

LOFD-001060



L.ChMeas.RI.Rank 1

Number of times rank 1 is reported

Multi-mode: None

Basic Scheduling

GSM: None

DL 2x2 MIMO

UMTS: None

DL 4x2 MIMO

LTE: LBFD-002025

Basic Scheduling DL 2x2 MIMO

LOFD-001001 LOFD-001003 TDLBFD-002025 TDLOFD-001001 1526730142

L.ChMeas.RI.Rank 2

Number of times a UE reports rank 2

Multi-mode: None

Basic Scheduling

GSM: None

DL 2x2 MIMO

UMTS: None

DL 4x2 MIMO

LTE: LBFD-002025

Basic Scheduling DL 2x2 MIMO

LOFD-001001 LOFD-001003 TDLBFD-002025 TDLOFD-001001

Issue 04 (2015-08-31)


230


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730172



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730174

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

231


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730175



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730177

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

232


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730178



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730180

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

233


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730181



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730183

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

234


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730184



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730186

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

235


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730187



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730189

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

236


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730190



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730192

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

237


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730193



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730195

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

238


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730196



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730198

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

239


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730199



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730201

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

240


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730202



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730204

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

241


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730205



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730207

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

242


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730208



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730210

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

243


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730211



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730213

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

244


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730214



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730216

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

245


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730217



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730219

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

246


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730220



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730222

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

247


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730223



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730225

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

248


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730226



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730228

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

249


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730229



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730231

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

250


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730232



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003






LOFD-001001

DL 4X4 MIMO

LOFD-001003




DL 4x2 MIMO


LTE: LBFD-001005

DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



Issue 04 (2015-08-31)


TDLBFD-001005


DL 2x2 MIMO

LTE: LBFD-001005

LOFD-001060

1526730234

DL 4x2 MIMO


DL 4x2 MIMO

DL 2x2 MIMO

251


11 Counters

Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1526730235



Multi-mode: None



DL 2x2 MIMO

LOFD-001001

DL 4X4 MIMO

LOFD-001003



L.Traffic.User.TM9 .Avg

Average number of UEs that apply TM9 in a cell


DL 4x2 MIMO

DL 2x2 MIMO RRC Connection Management RRC Connection Management DL 4x2 MIMO DL 2x2 MIMO

LOFD-001003 LOFD-001001 1526732737

L.ChMeas.RI.Rank 3


Multi-mode: None

Basic Scheduling

GSM: None

DL 4X4 MIMO

UMTS: None

Basic Scheduling

LTE: LBFD-002025 LOFD-001060 TDLBFD-002025 1526732738

L.ChMeas.RI.Rank 4


Multi-mode: None

Basic Scheduling

GSM: None

DL 4X4 MIMO

UMTS: None

Basic Scheduling

LTE: LBFD-002025 LOFD-001060 TDLBFD-002025

Issue 04 (2015-08-31)


252


12 Glossary

12

Glossary

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

Issue 04 (2015-08-31)


253


13 Reference Documents

13

Reference Documents

1.

3GPP TS 36.211, "Physical Channels and Modulation"

2.

3GPP TS 36.213, "Physical layer procedures"

3.

3GPP TS 36.306, "User Equipment (UE) radio access capabilities"

4.

3GPP TR 36.814, "Physical Layer Aspects"

5.

Receiver Technologies Feature Parameter Description

6.

Cell Management Feature Parameter Description

7.

License Management Feature Parameter Description

8.

RF Unit and Topology Management Feature Parameter Description

9.

Terminal Awareness Differentiation Feature Parameter Description

Issue 04 (2015-08-31)


254

MIMO(eRAN8.1_04)

Recommend Documents