Huawei 4G Eran 11.1

HedEx Startpage Page 1 of 510
eRAN Feature Documentation

Product Version: eRAN11.1
Library Version: 07
Date: 2017-01-15
For any question, please contact us.

Copyright © Huawei Technologies Co., Ltd. 2017. All rights reserved.
Basic Services
Contents
1 Basic Services
1.1 Cell Management
1.2 Connection Management
1.3 Idle Mode Management
1.4 Multiple Frequency Band Indicator
1.5 Physical Channel Resource Management
1.6 Power Control
1.7 SCTP Congestion Control
1.8 Terminal Awareness Differentiation
1.9 Uplink Timing Control
Basic Services
Parent topic: Radio & Performance
eRAN
Cell Management Feature Parameter Description
Issue 05
Date 2017-01-15
HUAWEI TECHNOLOGIES CO., LTD.

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
http://localhost:7890/printtopics.html?time=Mon May 28 16:10:20 UTC+0530 2018 5/28/2018

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: support@huawei.com
1 Contents
1 About This Document
1.1 Scope
1.2 Intended Audience
1.3 Change History
1.4 Differences Between eNodeB Types
2 Overview
2.1 Introduction
2.2 Benefits
3 Technical Description
3.1 Related Concepts
3.1.1 Cell
3.1.2 Sector
3.1.3 Sector Equipment
3.1.4 RF Equipment
3.1.5 Baseband Equipment
3.1.6 Cell-specific Sector Equipment
3.2 Typical Scenarios
3.2.1 Establishing a Cell in a Common Sector
3.2.2 Establishing Cells in Multiple Sectors with RRU/RFU Splitting
3.2.3 Establishing a Cell in a Single Sector with RRU/RFU Combination
3.2.4 Establishing a Cell in Multiple Sectors Served by Different RRUs
3.3 Cell-related Parameters
3.3.1 Frequency Band
3.3.2 Cell Bandwidth
3.3.3 Maximum Transmit Power of a Cell
4 Related Features
5 Network Impact
6 Engineering Guidelines
6.1 When to Use
6.2 Required Information
6.3 Planning
6.4 Deployment
6.4.1 Process
6.4.2 Requirements
6.4.3 Precautions
6.4.4 Hardware Adjustment
6.4.5 Data Preparation and Activation
6.4.5.1 Data Preparation
6.4.5.2 Using the CME
6.4.5.3 Using MML Commands
6.4.5.4 MML Command Examples
6.4.6 Activation Observation
6.4.7 Reconfiguration
6.4.8 Deactivation
6.5 Performance Monitoring
6.6 Parameter Optimization
6.7 Possible Issues
7 Parameters
8 Counters
9 Glossary
10 Reference Documents

Scope
This document describes cell management, including its technical principles, related features, network impact, and engineering guidelines.
This document covers LBFD-001003 Scalable Bandwidth.
Any parameters, alarms, counters, or managed objects (MOs) described herein apply only to the corresponding software release. For future software releases, refer to the
corresponding updated product documentation.
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD, and "eNodeB" refers to LTE FDD eNodeB.
This document applies to the following types of eNodeBs.
eNodeB Type Model
Macro 3900 series eNodeB
Micro BTS3202E
BTS3203E
BTS3911E
BTS3912E
LampSite DBS3900
Intended Audience
This document is intended for personnel who:
• Need to understand the features described herein

• Work with Huawei products
Change History
This section provides information about the changes in different document versions. There are two types of changes:
• Feature change
Changes in features and parameters of a specified version as well as the affected entities
• 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.
AN11.1 05 (2017-01-15)
This issue includes the following changes.
Change Type Change Description Parameter Change
Feature change None None
Editorial change Revised the descriptions in 1.1 Scope. None
AN11.1 04 (2016-11-01)
Feature change None None
Editorial change Revised descriptions in the document. None
AN11.1 03 (2016-07-30)
Feature change Added band 27. For details, see 3.3.1 Frequency Band. None
Editorial change Revised the descriptions in 6.4.2 Requirements. None
AN11.1 02 (2016-06-30)
Feature change Added descriptions of the newly added pRRU3916. For details, see 6.4.5.1 Data Preparation. None
Editorial change None None
AN11.1 01 (2016-03-07)
This issue does not include any changes.
AN11.1 Draft A (2015-11-30)
Compared with Issue 01 (2015-07-30) of eRAN8.1, Draft A (2015-11-30) of eRAN11.1 includes the following changes.
Change Type Change Description Parameter Change Affected Entity
Feature change Added pRRU3911 configuration descriptions. None LampSite eNodeBs
Added band 66. For details, see 3.3.1 Frequency Band. None Macro, micro, and
LampSite eNodeBs

Editorial change None None N/A
Differences Between eNodeB Types
ature Support by Macro, Micro, and LampSite eNodeBs
Feature ID Feature Name Supported by Macro eNodeBs Supported by Micro eNodeBs Supported by LampSite eNodeBs
LBFD-001003 Scalable Bandwidth Yes Yes Yes
nction Implementation in Macro, Micro, and LampSite eNodeBs
Function Difference
Establishing cells in Implementation of this function varies depending on the eNodeB type.
multiple sectors • Macro and micro eNodeBs support this function.
with RRU/RFU
• LampSite eNodeBs do not support this function.
splitting
For details about establishing cells in multiple sectors with RRU/RFU splitting, see 3.2.2 Establishing Cells in Multiple Sectors with RRU/RFU
Splitting.
Establishing a cell Implementation of this function varies depending on the eNodeB type.
in a single sector • Macro and LampSite eNodeBs support this function.
with RRU/RFU
• Among all micro eNodeB models, only the BTS3911E and BTS3912E support this function.
combination
For details about establishing a cell in a single sector with RRU combination, see 3.2.3 Establishing a Cell in a Single Sector with RRU/RFU
Combination.
Establishing a cell Implementation of this function varies depending on the eNodeB type.
in a sector with • Macro eNodeBs support this function.
RRU/RFU channel
• LampSite eNodeBs do not support this function.
cross-connection
under MIMO • Among all micro eNodeB models, only the BTS3911E and BTS3912E support this function.
For details about establishing a cell in a sector with RRU/RFU channel cross-connection under MIMO, see Base Station Equipment Reliability
Feature Parameter Description.
Establishing a cell Multi-sector cells include digital combination cells, single-frequency-network (SFN) cells, multi-MRRU aggregation cells, and 2-RRU
in multiple sectors combination cells. Implementation of this function varies depending on the eNodeB type.
served by different • Macro eNodeBs support digital combination cells, SFN cells, multi-MRRU aggregation cells, and 2-RRU combination cells.
RRUs
• LampSite eNodeBs support multi-MRRU aggregation cells.
• Among all micro eNodeB models, only the BTS3911E and BTS3912E support this function.
For details about multi-sector cells, see 3.2.4 Establishing a Cell in Multiple Sectors Served by Different RRUs.
Cell bandwidth Bandwidths supported by eNodeBs vary depending on the eNodeB type.
• Macro eNodeBs support the cell bandwidths of 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, and 20 MHz.
• Micro and LampSite eNodeBs support the cell bandwidths of 5 MHz, 10 MHz, 15 MHz, and 20 MHz.
For details about cell bandwidths, see 3.3.2 Cell Bandwidth.
Cell transmission Transmission and reception modes supported by eNodeBs vary depending on the eNodeB type.
and reception • Macro eNodeBs support 1T1R, 1T2R, 2T2R, 2T4R, 4T4R, 2T8R, and 4T8R cells.
mode
• LampSite eNodeBs support 2T2R, 2T4R, and 4T4R cells.
• Micro eNodeBs:
◾ The BTS3202E supports 1T1R, 1T2R, and 2T2R cells.
◾ The BTS3203E supports 1T1R, 1T2R, 2T2R, 2T4R, and 4T4R cells.
◾ The BTS3911E and BTS3912E support 1T1R, 1T2R, and 2T2R cells.
2 Overview
Introduction
Cell management refers to management of wireless communications resources by cell establishment and parameter configuration for cells.
Benefits
Cell management is a basic function for eNodeBs to provide radio coverage.
Related Concepts
Figure 3-1 shows the concepts related to cell management.

Figure 3-1 Cell-related concepts
3.1.1 Cell
A cell is an area where wireless communications services are provided. It is the fundamental unit of a radio network. A cell is added by running the ADD CELL command. All the
cells joinly achieve coverage of the entire radio network.
3.1.2 Sector
A sector is a radio coverage area of an antenna. It is added by running the ADD SECTOR command. Each sector uses one or more radio carriers to provide coverage.
NOTE:
• For a co-MPT base station, if services of different modes are carried on the same transmit channel, configure the same SECTOR MO for these modes.
• It is recommended that each pRRU be planned as a sector for LampSite eNodeBs.
A sector can be omnidirectional or directional, depending on the antenna type. The following table describes the sector types.
Sector Type Definition Benefits
Omnidirectional sector An omnidirectional sector uses an omnidirectional antenna to In light-traffic areas, the deployment of omnidirectional
provide a 360° circular coverage area with the antenna as the sectors reduces the cost of antenna equipment.
coverage center.
Directional sector Directional sectors use directional antennas for coverage. Each In heavy-traffic areas, the deployment of directional
directional antenna covers a 60° or 120° sector area when six or sectors supports large traffic volume. In addition,
three sectors, respectively, are configured on an eNodeB. The directional sectors support more flexible area and sector
azimuth of each sector is slightly greater than 60 or 120 degrees. planning.
The overlapping ensures seamless coverage.
3.1.3 Sector Equipment

Sector equipment is a set of antennas used for the same sector. A sector is linked to a set of antennas comprising a specific piece of sector equipment by running the ADD
SECTOR or ADD SECTOREQM command.
NOTE:
For a co-MPT base station, if services of different modes are carried on the same transmit channel, configure the SECTOREQM MO by mode.
3.1.4 RF Equipment
For a macro or LampSite eNodeB, radio frequency (RF) equipment is a set of RF processing units, including RRUs, RFUs, pRRUs, and AAUs. A piece of RF equipment is
added by running the ADD RRU command. After execution of this command, ADD RRUCHAIN must be run to specify the connected CPRI ports on baseband processing units
(BBPs) for the added RF equipment.
For a micro eNodeB, RF equipment refers to its RF processing units. RRUs need to be added only to the BTS3911E and BTS3912E among all micro eNodeB models.
3.1.5 Baseband Equipment

A piece of baseband equipment consists of one or more BBPs.
For a macro or LampSite eNodeB, a BBP is added by running the ADD BRD command. It can be added to a piece of baseband equipment by running the ADD
BASEBANDEQM command.
For a micro eNodeB, there is no need to add BBPs or baseband equipment.
In LTE eNodeBs, the baseband equipment is used for both uplink and downlink transmissions. It is recommended that each piece of baseband equipment includes only one
BBP. Each BBP can belong to only one piece of baseband equipment.

3.1.6 Cell-specific Sector Equipment

When binding sector equipment to a cell, you can specify the sector equipment and the baseband equipment for the cell at the same time.
For a macro eNodeB, the sector equipment and serving BBP boards specific to a cell are added by running the ADD EUCELLSECTOREQM command. If baseband equipment
is not configured for a cell, the BBP directly connected to the RRU serving the cell is used by default.
For a LampSite eNodeB, the sector equipment group of a cell is added by running the ADD EUSECTOREQMGROUP command. Then, sector equipment is added to the sector
equipment group by running the ADD EUSECTOREQMID2GROUP command.
Typical Scenarios
The following are typical scenarios of cell establishment:
• Establishing a cell in a common sector

• Establishing cells in multiple sectors with RRU/RFU splitting
• Establishing a cell in a single sector with RRU/RFU combination
• Establishing a cell in multiple sectors served by different RRUs/RFUs
• Establishing a cell in a sector with RRU/RFU channel cross-connection under MIMO
For details about cell setup in a sector with RRU/RFU channel cross-connection under MIMO, see Base Station Equipment Reliability Feature Parameter Description.
In the preceding scenarios, only cells in common sectors can be established for micro eNodeBs.
3.2.1 Establishing a Cell in a Common Sector

A cell can be established in a common sector that is served by a single RRU or RFU, as shown in the following figure.
The antenna mode of a cell in a common sector can be 1T1R, 1T2R, 2T2R, 2T4R, 2T8R, 4T4R or 4T8R. xTyR means x transmit channels and y receive channels.
NOTE:
If a cell works in 4T4R mode, you can run the MOD RXBRANCH command to disable two receive channels. Then, the antenna mode of the cell changes to 4T2R. (The 4T2R
mode is used to temporarily prevent intermodulation interference. The 4T2R mode is not recommended for normal use because in this mode uplink coverage of the sector may
reduce compared with the coverage in 4T4R mode.)
Macro and LampSite eNodeBs support 2T4R and 4T4R cells. As micro eNodeBs, the BTS3202E does not support 2T4R or 4T4R cells while the BTS3203E supports 2T4R and
4T4R cells.
Figure 3-2 A cell established in a common sector
3.2.2 Establishing Cells in Multiple Sectors with RRU/RFU Splitting

An RRU/RFU can be logically split to establish multiple sectors when the RRU/RFU processing capability does not match the antenna transmission and reception capability. The
following figure provides an example of this scenario.
The RF unit of a micro eNodeB works in 2T2R mode and can be split to provide two 1T1R sectors.
Figure 3-3 RRU/RFU splitting for multiple sectors (using a 4T4R RRU as an example)
3.2.3 Establishing a Cell in a Single Sector with RRU/RFU Combination

In RRU/RFU combination scenarios, RRUs/RFUs working on the same frequency band jointly provide a sector to achieve greater RF capacity if the RRU/RFU processing
capability does not match the antenna transmission and reception capability.
Macro eNodeBs support combination of 0T2R, 0T4R, 1T2R, 2T2R, 2T4R, or 4T4R RRUs or RFUs.
Figure 3-4 RRU/RFU combination for a single sector (using 2T2R RRUs as an example)
3.2.4 Establishing a Cell in Multiple Sectors Served by Different RRUs

The sectors served by multiple RRUs can be combined to set up a single cell. The RF channels, antenna mode, and transmit power can be configured separately for each
sector to implement precise control of services. The Cell.MultiRruCellFlag parameter specifies whether a cell is established in multiple sectors served by different RRUs, and the
Cell.MultiRruCellMode parameter specifies the types of such cells.

Among all micro eNodeB models, only the BTS3911E and BTS3912E support a cell established in multiple sectors served by different RRUs.
A cell established in multiple sectors served by different RRUs can be an SFN cell, a digital combination cell, or a multi-MRRU aggregation cell. Table 3-1 describes different
types of cell established in multiple sectors served by different RRUs.
Figure 3-5 A cell established in multiple sectors served by different RRUs
Table 3-1 Types of cell established in multiple sectors served by different RRUs
Cell Type Description Applicable eNodeBs
SFN cell Multiple RRUs are combined to serve an SFN cell, where the same physical cell identifier (PCI) and Macro eNodeBs
cell ID are used in all the RRU coverage areas. This expands the cell center area and reduces
interference at the cell edge.
SFN cells apply in densely populated outdoor scenarios and in indoor scenarios where the
distributed antenna system (DAS) is used. For details about SFN cells, see SFN Feature Parameter
Description.
Multi-MRRU aggregation cell A multi-pRRU aggregation cell is the basic service area for providing indoor coverage in the LampSite eNodeBs
LampSite solution.
For details about multi-MRRU aggregation cells, see SFN Feature Parameter Description.
2-RRU-combination cell A 2-RRU-combination cell is set up using sectors provided by two RRUs (each RRU serves one Macro eNodeBs
sector). In the downlink, the two RRUs transmit the same data. In the uplink, the BBP combines the
signals received by the two RRUs.
2-RRU-combination cells mainly cover high-speed railways and highways. They are not
recommended because of unstable performance.
Digital combination cell A digital combination cell is served by multiple RRUs. The RRUs serve different sectors but use the Macro eNodeBs
same PCI. In the downlink, the RRUs transmit the same data. In the uplink, the BBP combines the
signals received by the RRUs.
Digital combination cells mainly cover subways and underground business areas.
For engineering guidelines for digital combination cells, see 6.4 Deployment.
Cell-related Parameters
This section describes three parameters: frequency band, cell bandwidth, and reference signal power.
For other parameters of a cell, such as CPRI compression, cycling prefix, preamble format, and cell radius, see CPRI Compression Feature Parameter Description, Extended CP
Feature Parameter Description, and Extended Cell Range Feature Parameter Description.
For the steps of reconfiguring these parameters, see the reconfiguration guide.
3.3.1 Frequency Band

The frequency band of a cell is specified by the FreqBand parameter. For details about allowed frequency bands, see section 5.5 in 3GPP TS 36.104 V11.0 (2013-07).
If the operating frequencies of a cell belong to multiple frequency bands, the frequency band specified by the CELL.FreqBand parameter has the highest priority. For details
about multi-band technologies, see Multiple Frequency Band Indicator Feature Parameter Description.
Table 3-2 Mapping between the frequency band and frequency range
Frequency Band (FreqBand) Uplink Frequency Range (Lowest and Highest Frequencies) Downlink Frequency Range (Lowest and Highest Frequencies)
1 1920 MHz 1980 MHz 2110 MHz 2170 MHz
2 1850 MHz 1910 MHz 1930 MHz 1990 MHz
3 1710 MHz 1785 MHz 1805 MHz 1880 MHz
4 1710 MHz 1755 MHz 2110 MHz 2155 MHz
5 824 MHz 849 MHz 869 MHz 894 MHz
61 830 MHz 840 MHz 875 MHz 885 MHz
7 2500 MHz 2570 MHz 2620 MHz 2690 MHz
8 880 MHz 915 MHz 925 MHz 960 MHz
9 1749.9 MHz 1784.9 MHz 1844.9 MHz 1879.9 MHz
10 1710 MHz 1770 MHz 2110 MHz 2170 MHz
11 1427.9 MHz 1447.9 MHz 1475.9 MHz 1495.9 MHz
12 699 MHz 716 MHz 729 MHz 746 MHz
13 777 MHz 787 MHz 746 MHz 756 MHz
14 788 MHz 798 MHz 758 MHz 768 MHz

Frequency Band (FreqBand) Uplink Frequency Range (Lowest and Highest Frequencies) Downlink Frequency Range (Lowest and Highest Frequencies)
15 Reserved Reserved Reserved Reserved
16 Reserved Reserved Reserved Reserved
17 704 MHz 716 MHz 734 MHz 746 MHz
18 815 MHz 830 MHz 860 MHz 875 MHz
19 830 MHz 845 MHz 875 MHz 890 MHz
20 832 MHz 862 MHz 791 MHz 821 MHz
21 1447.9 MHz 1462.9 MHz 1495.9 MHz 1510.9 MHz
22 3410 MHz 3490 MHz 3510 MHz 3590 MHz
23 2000 MHz 2020 MHz 2180 MHz 2200 MHz
24 1626.5 MHz 1660.5 MHz 1525 MHz 1559 MHz
25 1850 MHz 1915 MHz 1930 MHz 1995 MHz
26 814 MHz 849 MHz 859 MHz 894 MHz
27 807 MHz 824 MHz 852 MHz 869 MHz
28 703 MHz 748 MHz 758 MHz 803 MHz
29 N/A N/A 717 MHz 728 MHz
66 1710 MHz 1780 MHz 2110 MHz 2200 MHz
NOTE:
• Band 6 is unavailable.
• Band 29 applies only to carrier aggregation scenarios. For details, see Carrier Aggregation Feature Parameter Description.
3.3.2 Cell Bandwidth

This section describes the basic feature LBFD-001003 Scalable Bandwidth.
A cell can be configured with different standardized bandwidths: 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, or 20 MHz. Macro eNodeBs support the cell bandwidths of 1.4 MHz
and 3 MHz, while micro and LampSite eNodeBs do not support these two bandwidths. Cells also support non-standardized bandwidths. For details about non-standardized
bandwidths, see Compact Bandwidth Feature Parameter Description.
Cell bandwidths are specified by the CELL.UlBandWidth and CELL.DlBandWidth parameters.
3.3.3 Maximum Transmit Power of a Cell

This section describes the method of configuring the maximum transmit power of a cell (Pmax_out).
ax_out Configuration Principle
The value of Pmax_out must be less than or equal to the maximum transmit power of the RRU or RFU that provides the cell coverage.
NOTE:
• If multiple cells are served by the same RRU or RFU, the sum of Pmax_out values of these cells must be less than or equal to the maximum transmit power of the RRU
or RFU.
• For details about the maximum transmit power of RRUs or RFUs in different carrier configuration scenarios, see section "Typical Power Configuration Reference for
RF Modules" in 3900 Series Base Station Technical Description.
ax_out Configuration Parameters
Pmax_out is not specified by any parameter and is affected by the bandwidth, transmit/receive mode, CellDlpcPdschPa.PaPcOff, PDSCHCfg.PB, and Referencesignalpwr. The
following table lists parameters that affect Pmax_out for a cell with a fixed bandwidth and transmit/receive mode.
Table 3-3 Pmax_out configuration parameters
Parameter Setting Notes
ReferenceSignalPwr Its value must be calculated. For details, see Pmax_out Calculation Example.
CellDlpcPdschPa.PaPcOff Dual-antenna or four-antenna scenarios: DB_3_P_A(-3 dB)

Single-antenna scenarios: DB0_P_A(0 dB)
PDSCHCfg.PB Single-antenna scenarios: 0

Dual-antenna scenarios: 1
NOTE:
The value of the ReferenceSignalPwr parameter is determined by either of the following parameters:
• EuCellSectorEqm.ReferenceSignalPwr (or EuSectorEqmGroup.ReferenceSignalPwr for LampSite eNodeBs)

• PDSCHCfg.ReferenceSignalPwr
The value of the first parameter prevails if both the parameters are configured.
ax_out Query Method
To query Pmax_out of a cell, perform the following steps:
1. Run the DSP CELL command to query the value of Maximum transmit power(0.1dBm). This parameter indicates the maximum transmit power of a single antenna
channel of a cell.
2. Multiply Maximum transmit power(0.1dBm) by the number of transmit channels of a cell to obtain the value of Pmax_out.
ax_out Calculation Formula
• If the TxBranch.TXMAXPWR parameter is configured, Pmax_out equals the value of TxBranch.TXMAXPWR.

• If the TxBranch.TXMAXPWR parameter is not configured, Pmax_out is calculated using the following formula: Pmax_out = MAX {TypeA (Pmax_out), TypeB (Pmax_out)},
where
◾ Type A (Pmax_out) is the maximum transmit power configured for one type A symbol. The calculation formula is as follows:
◾ Type B (Pmax_out) is the maximum transmit power configured for one type B symbol. The calculation formula is as follows:
Table 3-4 describes the variables in the preceding formulas. For details about the preceding formulas, see section 5.2 in 3GPP TS 36.213 V10.5.0 (2012-03).
Table 3-4 Variables in the formulas
Variable Description
ReferenceSignalPwr Reference signal (RS) power of the physical downlink shared channel (PDSCH).
For details, see Pmax_out Configuration Parameters.
PowerFactorRatio Power factor ratio of the energy per resource element (EPRE) on the PDSCH.
• For Type A (Pmax_out), PowerFactorRatio is , where PaPcOff is determined by the CellDlpcPdschPa.PaPcOff

parameter. For example, when the CellDlpcPdschPa.PaPcOff parameter is set to -3 dB, the value of PowerFactorRatio
-3/10
is 10 , that is, about 0.5.
• For Type B (Pmax_out), PowerFactorRatio is .

◾ PaPcOff is determined by the CellDlpcPdschPa.PaPcOff parameter.
◾ ρB/ρA is related to the PDSCHCfg.PB parameter. Table 3-5 lists the mappings between ρB/ρA and the
PDSCHCfg.PB parameter.
For example, when the CellDlpcPdschPa.PaPcOff parameter is set to -3 dB and the PDSCHCfg.PB
parameter is set to 1, ρB/ρA is 1. In this case, the value of PowerFactorRatio is 0.5.
Type A (NRE) Number of non-RS resource elements (REs) in one type A symbol period. The calculation formula is as follows:
Type A (NRE) = Number of REs per RB in the frequency domain x Number of RBs x Number of antennas
Table 3-6 lists the mappings between the cell bandwidth and number of RBs.
Type B (NRS) Number of RSs in one type B symbol period. The calculation formula is as follows:
Type B (NRS) = Number of RSs per RB in the frequency domain x Number of RBs x Number of antennas
Type B (NRE) Number of non-RS REs in one type B symbol period. The calculation formula is as follows:
Type B (NRE) = Number of REs per RB in the frequency domain x Number of RBs x Number of antennas
Table 3-5 Mapping between PDSCHCfg.PB and the cell-specific ratio (ρB/ρA)
PDSCHCfg.PB ρB/ρA (One Antenna Port) ρB/ρA (Two or Four Antenna Ports)
0 1 5/4
1 4/5 1
2 3/5 3/4
3 2/5 1/2
Table 3-6 Mapping between cell bandwidths and the maximum number of available RBs
Cell Bandwidth (MHz) 1.4 3 5 10 15 20
Maximum Number of Available 6 15 25 50 75 100

RBs
ax_out Calculation Example
Among the three parameters for configuring Pmax_out, PaPcOff and PB can be configured according to Table 3-3. You only need to calculate the value of ReferenceSignalPwr.
The following is an example of calculating the value of ReferenceSignalPwr. In this example, the RRU provides the maximum transmit power of 80 W and serves a 20 MHz cell
with two antennas.
Pmax_out = MAX {Type A (Pmax_out), Type B (Pmax_out)} ≤ 80 W
where
• Type A (Pmax_out)
= ReferenceSignalPwr x PowerFactorRatio x TypeA(NRE)
= ReferenceSignalPwr x 0.5 x 2400
= 1200 x ReferenceSignalPwr
• Type B (Pmax_out)
= ReferenceSignalPwr x TypeB(NRS) + ReferenceSignalPwr x PowerFactorRatio x TypeB(NRE)
= ReferenceSignalPwr x 400 + ReferenceSignalPwr x 0.5 x 1600
= 1200 x ReferenceSignalPwr
NOTE:
• Type A (NRE) = Number of REs per RB in the frequency domain x Number of RBs x Number of antennas = 12 x 100 x 2 = 2400
• Type B (NRS) = Number of RSs per RB in the frequency domain x Number of RBs x Number of antennas = 2 x 100 x 2 = 400
• According to Table 3-3, the PaPcOff parameter for a cell with two antennas is set to –3 dB. Therefore, for type A symbols, PowerFactorRatio = = 0.5.
• According to Table 3-3, the typical value of the PB parameter for a cell with two antennas is 1. According to Table 3-5, for a cell with two antennas, ρB/ρA = 1.
Therefore, for type B symbols, PowerFactorRatio = = 0.5.

• Type B (NRE) = Number of REs per RB in the frequency domain x Number of RBs x Number of antennas = 8 x 100 x 2 = 1600

Based on the preceding calculation results, you can infer that:

Pmax_out = 1200 x ReferenceSignalPwr ≤ 80 W
ReferenceSignalPwr ≤ 66.67 mW = 18.24 dBm
The value of the ReferenceSignalPwr parameter cannot be greater than 18.24 dBm.
4 Related Features
erequisite Features
None
utually Exclusive Features
None
pacted Features
None
5 Network Impact
stem Capacity
System capacities vary with bandwidths. A higher bandwidth allows more UEs to access the network and to be scheduled and therefore supports higher cell throughput.
twork Performance
With the same CPU, digital signal processor (DSP), and memory configurations, a higher cell bandwidth uses more hardware resources. However, a higher system bandwidth
helps produce better service key performance indicators (KPIs).
When to Use
The major function of eNodeBs is to provide radio cell coverage for UEs. Cell management must be enabled.
Required Information
Before you deploy the cell management feature, determine the cell establishment scenario and collect operator information about the frequency band, bandwidth, cell radius,
and power.
Planning
None
Deployment
6.4.1 Process
Figure 6-1 Configuring a cell (for a macro eNodeB)
For details about "Configure device data", see 3900 Series Base Station Initial Configuration Guide.
6.4.2 Requirements
cense
The following table lists the license control items related to cell establishment. Operators must purchase and activate the following licenses.
Model License Control Item Sales Unit NE
LT1S0000PA00 RF Output Power (FDD) per 20W Macro eNodeB

Model License Control Item Sales Unit NE

LT1S005MHZ00 Carrier Bandwidth - 0~5MHz (FDD) per cell Macro eNodeB/LampSite eNodeB/Micro
eNodeB
LT1S010MHZ00 Carrier Bandwidth - 5~10MHz per cell Macro eNodeB/LampSite eNodeB/Micro

(FDD) eNodeB

(FDD) eNodeB

(FDD) eNodeB
LT1S00RFTC00 RF Transmit Channel (FDD) per Channel Macro eNodeB
LT1S00RFRC00 RF Receive Channel (FDD) per Channel Macro eNodeB
LT1S000MCA00 RF Multi Carrier (FDD) per Carrier Macro eNodeB/Micro eNodeB (only
BTS3911E)
LT1S0000PA01 RF Output Power for Blade and per 20W Macro eNodeB
AAU (FDD)
LT1S005MHZ01 Carrier Bandwidth - 0~5MHz for per cell Macro eNodeB

Blade and AAU (FDD)

Blade and AAU (FDD)

Blade and AAU (FDD)

Blade and AAU (FDD)
LT1S00RFTC01 RF Transmit Channel for Blade and per Channel Macro eNodeB
AAU (FDD)
LT1S00RFRC01 RF Receive Channel for Blade and per Channel Macro eNodeB
AAU (FDD)
LT1S000MCA01 RF Multi Carrier for Blade and AAU per Carrier Macro eNodeB
(FDD)
LT1S0ACTUS00 RRC Connected User (FDD) per RRC Connected User Macro eNodeB/LampSite eNodeB/Micro
eNodeB
LT1S0THROU00 Throughput Capacity (FDD) per Mbps Macro eNodeB/LampSite eNodeB/Micro

eNodeB
LT1S0000RB00 Resource Block (FDD) per RB Macro eNodeB/BTS3202E/BTS3203E

LTE
LT1S00BBTC00 BB Transmit Channel (FDD) per Channel Macro eNodeB
LT1S00BBRC00 BB Receive Channel (FDD) per Channel Macro eNodeB
LT1S0BASIC19 eNodeB FDD Basic Software, per cell Macro eNodeB/LampSite eNodeB/Micro
V100R011 (FDD) eNodeB
rdware
• When selecting optical modules for BBPs, ensure that common public radio interface (CPRI) data rates match the cell bandwidths and transmit/receive modes. For
the constraints between the CPRI data rates and the cell bandwidths and transmit/receive modes, see the BBU technical specifications in section "Product
Specifications" in 3900 Series Base Station Technical Description.
• A cell works normally only when the transmit/receive mode of the cell matches the number of transmit and receive channels of the RF module. For details about the
number of transmit and receive channels supported by the RF module, see RRU/RFU technical specifications in section "Product Specifications" in 3900 Series Base
Station Technical Description.
• Bandwidths of the cells provided by the RRUs/RFUs must fall within the frequency bands supported by the RRUs/RFUs.
• If different uplink and downlink bandwidths are configured for a cell served by a macro eNodeB, the following requirements must be met:
◾ The transmit/receive mode of the cell must be 1T1R, 1T2R, or 2T2R.
◾ The uplink and downlink bandwidths must be set to one of the following combinations: 5 MHz/10 MHz, 10 MHz/5 MHz, 10 MHz/15 MHz, 15 MHz/10 MHz,
20 MHz/15 MHz, and 15 MHz/20 MHz.
◾ RF modules must work in the 1800 MHz frequency band (band 3). pRRUs are not allowed.
◾ The LBBPc cannot be used.
NOTE:
When different uplink and downlink bandwidths are configured for a cell, the cell does not support the 141 test and RF loopback.
• A LampSite cell (multi-MRRU aggregation cell) and macro cell (RRU/RFU-serving cell) cannot be established on the same BBP. When both a LampSite cell and a
macro cell are to be established on the same eNodeB, configure different baseband resources for the cells if you want to manually configure baseband resources for
the cells. Relevant MML commands are as follows:
◾ ADD BASEBANDEQM: This command is used to configure a piece of baseband equipment.
◾ ADD EUCELLSECTOREQM: This command is used to bind a macro cell to a piece of baseband equipment.
◾ ADD EUSECTOREQMGROUP: This command is used to bind a LampSite cell to a piece of baseband equipment.
enario-specific Requirements
Establishing a Cell in a Common Sector Without RRU/RFU Combination
• To establish a 4T4R cell in a common sector without RRU/RFU combination, the following conditions must be met:
◾ The RRUs/RFUs must work in 2T4R or 4T4R mode. For details about 2T4R or 4T4R RRU/RFU models, see the following section in 3900 Series Base
Station Technical Description: Product Specifications > Technical Specifications of RRUs or Product Specifications > Technical Specifications of
RFUs.

NOTE:
In the load-sharing topology where RRUs/RFUs are connected to the same BBP, optical modules that support the 2.5 Gbit/s rate can be used. The load-sharing topology is not
recommended.
• To establish two cells in a common sector without RRU/RFU combination, the following conditions must be met:
◾ The RRUs/RFUs must support multiple carriers. For details about RRU/RFU models that support multiple carriers, see the following section in 3900
Series Base Station Technical Description: Product Specifications > Technical Specifications of RRUs or Product Specifications > Technical
Specifications of RFUs.
◾ A standardized bandwidth and a non-standardized bandwidth can be used for the two cells.
◾ The frequency range of the two cells must be within the frequency bands supported by the RRUs/RFUs.
◾ The frequency range of the two cells cannot overlap.
◾ The networking topology for CPRI ports must be star, chain, ring, or load sharing. For details, see RF Unit and Topology Management Feature Parameter
Description.
• Cell frequencies and bandwidths must meet the constraints described in 3.3 Cell-related Parameters.
Establishing a Cell in a Common Sector with RRU/RFU Combination
• The two RRUs/RFUs must support the same frequency range and have the same number of transmit and receive antennas.
• The length difference between CPRI optical fibers used to connect the two RRUs/RFUs to the BBU cannot exceed 100 m.
• RRUs/RFUs must be capable of being combined in the following manners:
◾ A 2T0R RRU/RFU and a 0T2R RRU/RFU are combined to serve a 2T2R cell.
◾ Two 1T2R RRUs/RFUs are combined to serve a 2T2R cell.
• The RRU/RFU topology must be a star topology. For details, see RF Unit and Topology Management Feature Parameter Description.
Establishing a Digital Combination Cell in Multiple Sectors
• The cell can be established on the LBBPd, UBBPd, UBBPe, or UMDU.

• The sectors must be provided by RRU3821Es.
• The RRUs support two to eight levels of cascading connections. CPRI compression can be enabled to save CPRI resources. A maximum of four levels of cascading
connections is recommended. If the cascading level is greater than four, cell performance is not guaranteed. In this case, you are advised to configure more cells.
• The RRUs must be cascaded to a CPRI port on a BBP in a chain topology.
• The cell does not support extended cyclic prefixes (CPs) or the uplink coordinated multipoint reception (UL CoMP) algorithm.
• The cell must work on a bandwidth of 5 MHz, 10 MHz, 15 MHz, or 20 MHz, and the transmission and reception mode of the cell must be 2T2R or 1T1R.
6.4.3 Precautions
None

When a digital combination cell is established in multiple sectors, the RRUs serving this cell must be installed as follows:
• If the RRUs are not installed in a straight line, the distance between any two RRUs cannot be greater than 1000 m. As shown in Figure 6-2, four RRUs are installed to
serve a cell. The distance between RRU1 and RRU4 is the largest and cannot exceed 1000 m.
Figure 6-2 Example of RRUs not installed in a straight line
• If RRUs are installed in a straight line, the distance between each pair of neighboring RRUs cannot be greater than 1000 m. As shown in Figure 6-3, four RRUs are
installed to serve a cell. The distance between two neighboring RRUs (for example, RRU1 and RRU2) cannot exceed 1000 m.
Figure 6-3 Example of RRUs installed in a straight line
• RRUs must be cascaded in a chain topology as shown in Figure 6-4. The requirement of the length of optical fibers is as follows:

NOTE:
Ln represents the length of the optical fiber between two neighboring RRUs or between a BBP and a neighboring RRU.
• The total length of optical fibers connected between the RRUs serving a cell cannot exceed 5 km. That is, the sum of L2, L3, and L4 cannot be greater than 5 km.
• The total length of optical fibers connecting all the RRUs and the BBP cannot exceed 20 km. That is, the sum of L1, L2, L3, and L4 cannot be greater than 20 km.
Figure 6-4 Optical fiber length requirement
6.4.5 Data Preparation and Activation

The following table describes the parameters that must be set in a SECTOR MO to configure a sector.
Parameter Name Parameter ID Setting Notes Data Source
Sector ID SECTOR.SECTORID Ensure that each sector number is unique. Network plan
(negotiation not
required)
Sector Name SECTOR.SECNAME N/A Network plan

(negotiation not
required)
Location Name SECTOR.LOCATIONNAME N/A Network plan

(negotiation not
required)
User Label SECTOR.USERLABEL N/A Network plan

(negotiation not
required)
Antenna Number SECTOR.ANTNUM N/A Network plan

(negotiation not
required)
Cabinet No. of Antenna 1 to SECTOR.ANT1CN to N/A Network plan

Cabinet No. of Antenna 8 SECTOR.ANT8CN (negotiation not
required)
Subrack No. of Antenna 1 to SECTOR.ANT1SRN to N/A Network plan

Subrack No. of Antenna 8 SECTOR.ANT8SRN (negotiation not
required)
Slot No. of Antenna 1 to Slot SECTOR.ANT1SN to For a LampSite eNodeB, Network plan
No. of Antenna 8 SECTOR.ANT8SN • If the pRRU3901 is used, set this parameter to 255 to (negotiation not
enable automatic allocation of the slot number to an required)
antenna. If the slot number is to be assigned
manually, set this parameter to a value ranging from 1
to 3, depending on the slot number of the RF daughter
board.
However, manual and automatic configurations cannot
be both used for the same pRRU.
• If the pRRU3902, pRRU3907, pRRU3911, or
pRRU3916 is used, set this parameter to 0.
Channel No. of Antenna 1 to SECTOR.ANT1N to N/A Network plan

Channel No. of Antenna 8 SECTOR.ANT8N (negotiation not
required)
Create Default Sector SECTOR.CREATESECTOREQM N/A Network plan

Equipment (negotiation not
required)
Default Sector Equipment ID SECTOR.SECTOREQMID N/A Network plan

(negotiation not
required)
The following table describes the parameters that must be set in a SECTOREQM MO to configure a piece of sector equipment.
Sector Equipment ID SECTOREQM.sectorEqmId N/A Network plan

(negotiation not
required)
Sector ID SECTOREQM.sectorId N/A Network plan

(negotiation not
required)
Antenna Number SECTOREQM.ANTNUM N/A Network plan

(negotiation not
required)
Cabinet No. of Antenna 1 to SECTOREQM.ANT1CN to N/A Network plan

Cabinet No. of Antenna 8 SECTOREQM.ANT8CN (negotiation not
required)
Subrack No. of Antenna 1 to SECTOREQM.ANT1SRN to N/A

Subrack No. of Antenna 8 SECTOREQM.ANT8SRN


Network plan
(negotiation not
required)
Slot No. of Antenna 1 to Slot SECTOREQM.ANT1SN to For a LampSite eNodeB, Network plan
No. of Antenna 8 SECTOREQM.ANT8SN • If the pRRU3901 is used, set this parameter to 255 (negotiation not
to enable automatic allocation of the slot number to required)
an antenna. If the slot number is to be assigned
manually, set this parameter to a value ranging from
1 to 3, depending on the slot number of the RF
daughter board.
However, manual and automatic configurations
cannot be both used for the same pRRU.
• If the pRRU3902, pRRU3902, pRRU3911, or
pRRU3916 is used, set this parameter to 0.
Channel No. of Antenna 1 to SECTOREQM.ANT1N to N/A Network plan

Channel No. of Antenna 8 SECTOREQM.ANT8N (negotiation not
required)
Antenna 1 RX/TX Mode to SECTOREQM.ANTTYPE1 to N/A Network plan

Antenna 8 RX/TX Mode SECTOREQM.ANTTYPE8 (negotiation not
required)
TX Antenna 1 Master/Slave SECTOREQM.TXBKPMODE1 to Set the parameter value to MASTER(Master). Network plan
Mode to TX Antenna 8 SECTOREQM.TXBKPMODE8 This parameter cannot be set to SLAVE(Slave) because the (negotiation not
Master/Slave Mode eNodeBs do not support antennas working in active/standby required)
mode.
The following table describes the parameters that must be set in a CnOperator MO to configure an operator.
CN Operator ID CnOperator.CnOperatorId N/A Network plan (negotiation not

required)
CN Operator name CnOperator.CnOperatorName N/A Network plan (negotiation not

required)
CN Operator type CnOperator.CnOperatorType This parameter specifies the operator type: primary or Network plan (negotiation not
secondary. Each eNodeB can be configured with only one required)
primary operator but multiple secondary operators.
Mobile country code CnOperator.Mcc N/A Network plan (negotiation not

required)
Mobile network code CnOperator.Mnc N/A Network plan (negotiation not

required)
The following table describes the parameters that must be set in a CnOperatorTa MO to configure a tracking area for an operator.
Local tracking area ID CnOperatorTa.TrackingAreaId This parameter uniquely identifies a tracking area. This parameter is Network plan
used only in the eNodeB and is different from the tracking area (negotiation not
identity (TAI) configured in the tracking area list (TAL) on the MME. required)
CN Operator ID CnOperatorTa.CnOperatorId N/A Network plan

(negotiation not
required)
Tracking area code CnOperatorTa.Tac N/A Network plan

(negotiation not
required)
The following table describes the parameters that must be set in a Cell MO to configure a cell.
Local Cell ID Cell.LocalCellId N/A Network plan (negotiation

not required)
Cell Name Cell.CellName N/A Network plan (negotiation

not required)
Csg indicator Cell.CsgInd Retain the default value BOOLEAN_FALSE(FALSE). Network plan (negotiation
not required)
Uplink cyclic prefix length Cell.UlCyclicPrefix Retain the default value NORMAL_CP(Normal). Network plan (negotiation
not required)
Downlink cyclic prefix Cell.DlCyclicPrefix Retain the default value NORMAL_CP(Normal). Network plan (negotiation
length not required)
Frequency band Cell.FreqBand N/A Network plan (negotiation

not required)
Uplink EARFCN indication Cell.UlEarfcnCfgInd N/A Network plan (negotiation

not required)
Uplink EARFCN Cell.UlEarfcn This parameter is optional, depending on the value of the Network plan (negotiation
Cell.UlEarfcnCfgInd parameter. not required)
• If Cell.UlEarfcnCfgInd is set to CFG(Configure), set
Cell.UlEarfcn.


• If Cell.UlEarfcnCfgInd is set to NOT_CFG(Not
configure), do not set Cell.UlEarfcn.
Downlink EARFCN Cell.DlEarfcn The downlink frequency identified by the EARFCN must be located Network plan (negotiation
in the band specified by the Cell.FreqBand parameter. not required)
When establishing two cells in multi-carrier scenarios, the EARFCN
range of the two cells cannot overlap.
Uplink bandwidth Cell.UlBandWidth N/A Network plan (negotiation

not required)
Downlink bandwidth Cell.DlBandWidth N/A Network plan (negotiation

not required)
Cell ID Cell.CellId N/A Network plan (negotiation

not required)
Physical cell ID Cell.PhyCellId N/A Network plan (negotiation

not required)
Additional spectrum Cell.AdditionalSpectrumEmission N/A Network plan (negotiation

emission not required)
Cell FDD TDD indication Cell.FddTddInd Set this parameter to CELL_FDD(FDD). Network plan (negotiation
not required)
Cell specific offset Cell.CellSpecificOffset Set this parameter to 0. Network plan (negotiation
not required)
Frequency offset Cell.QoffsetFreq Set this parameter to 0. Network plan (negotiation

not required)
Root sequence index Cell.RootSequenceIdx For details about setting constraints, see the MO reference for the Network plan (negotiation
eNodeB. not required)
Preamble format Cell.PreambleFmt N/A Network plan (negotiation

not required)
Cell radius Cell.CellRadius The value of this parameter must be equal to or greater than the Network plan (negotiation
actual cell radius. Otherwise, UEs at the cell edge may fail to not required)
access the network.
If more than three physical cells are established on a UBBPd8 or
more than six physical cells are established on a UBBPd9, set this
parameter to a value equal to or smaller than 9895.
Customized bandwidth Cell.CustomizedBandWidthCfgInd N/A Network plan (negotiation

configure indicator not required)
Customized uplink Cell.CustomizedULBandWidth This parameter is required only when the Network plan (negotiation
bandwidth Cell.CustomizedBandWidthCfgInd parameter is set to CFG not required)
(Configure).
Customized downlink Cell.CustomizedDLBandWidth This parameter is required only when the Network plan (negotiation
bandwidth Cell.CustomizedBandWidthCfgInd parameter is set to CFG not required)
(Configure).
Ue max power allowed Cell.UePowerMaxCfgInd N/A Network plan (negotiation

configure indicator not required)
Max transmit power Cell.UePowerMax This parameter is required only when the Cell.UePowerMaxCfgInd Network plan (negotiation
allowed parameter is set to CFG(Configure). not required)
Flag of Multi-RRU Cell Cell.MultiRruCellFlag Set this parameter to BOOLEAN_TRUE(True) for multi-sector cells. Network plan (negotiation
not required)
Mode of Multi-RRU Cell Cell.MultiRruCellMode This parameter is required only when the Cell.MultiRruCellFlag Network plan (negotiation
parameter is set to BOOLEAN_TRUE(True). not required)
Air Cell Flag Cell.AirCellFlag N/A Network plan (negotiation

not required)
CRS Port Number Cell.CrsPortNum Set this parameter based on the number of downlink channels. For Network plan (negotiation
example, set this parameter to 2 if a cell works in 2T mode and to 1 not required)
if the cell works in 1T1R mode.
Cell transmission and Cell.TxRxMode This parameter should be the same as the SECTOREQM.antNum Network plan (negotiation
reception mode parameter in the Sector MO. not required)
User Label Cell.UserLabel N/A Network plan (negotiation

not required)
Work mode Cell.WorkMode N/A Network plan (negotiation

not required)
Cell Slave Band Cell.CellSlaveBand Set this parameter by running the ADD CELLBAND command. Network plan (negotiation
not required)
Cell Standby Mode Cell.EuCellStandbyMode N/A Radio planning (Internal

planning)
The following table describes the parameters that must be set in an EUCELLSECTOREQM MO to configure a piece of sector equipment for the cell.
Local Cell ID EUCELLSECTOREQM.LocalCellId N/A Network plan

(negotiation not
required)


Sector equipment ID EUCELLSECTOREQM.sectorEqmId N/A Network plan
(negotiation not
required)
Reference signal power EUCELLSECTOREQM.ReferenceSignalPwr If this parameter is set to 32767, the reference signal Network plan
power of the cell is specified in the PDSCHCfg MO. (negotiation not
For the value calculation, see 3.3.3 Maximum Transmit Power of required)
a Cell.
Baseband equipment ID EUCELLSECTOREQM.BaseBandEqmId If this parameter is set to 255, no baseband equipment is Network plan
specified for the cell. In this case, the cell can use any (negotiation not
baseband equipment of the eNodeB. required)
Sector CPRI Compression EUCELLSECTOREQM.SectorCpriCompression This parameter specifies the CPRI compression mode of Default/recommended
each piece of sector equipment. It is used only when the value:
Mode of Multi-RRU Cell parameter is set to SFN(SFN).
When this parameter is set to NULL(Invalid), the CPRI
compression mode of carriers is specified by the CPRI
Compression parameter in the CELL MO. When this
parameter is set to another value, the CPRI compression
mode of carriers is specified by this parameter.
Auto Config Flag EUCELLSECTOREQM.AutoCfgFlag N/A Radio planning

(Internal planning)
The following table describes the parameters that must be set in a CellOp MO to configure a cell operator.
Local Cell ID CellOp.LocalCellId N/A Network plan (negotiation not required)
Local tracking area ID CellOp.TrackingAreaId N/A Network plan (negotiation not required)
Cell reserved for operator CellOp.CellReservedForOp N/A Network plan (negotiation not required)
Operator uplink RB used ratio CellOp.OpUlRbUsedRatio N/A Network plan (negotiation not required)
Operator downlink RB used CellOp.OpDlRbUsedRatio N/A Network plan (negotiation not required)
ratio
The following table describes the parameters that must be set in a BaseBandEqm MO to configure baseband equipment information.
Parameter Parameter ID Setting Notes

Name
Baseband BaseBandEqm.BASEBANDEQMID Each BaseBandEqmId parameter value identifies a piece of baseband equipment.
Equipment One piece of baseband equipment can include multiple BBPs. For example, the following command specifies
ID that the baseband equipment numbered 0 includes the BBPs installed in slots 1 and 2:
ADD
BASEBANDEQM:BASEBANDEQMID=0,BASEBANDEQMTYPE=ULDL,UMTSDEMMODE=NULL,SN1=2,SN2=1;
However, it is recommended that one piece of baseband equipment include only one BBP.
A BBP cannot belong to multiple pieces of baseband equipment.
Baseband BaseBandEqm.BASEBANDEQMTYPE N/A

Equipment
Type

For detailed operations, see CME-based Feature Configuration.

This section describes how to activate the cell management feature using MML commands in the following scenarios:
Scenario 1: Establishing a Cell in a Common Sector
Scenario 2: Establishing Cells in Multiple Sectors with RRU/RFU Splitting
Scenario 3: Establishing a Cell in a Single Sector with RRU/RFU Combination
Scenario 4: Establishing a Cell in Multiple Sectors Served by Different RRUs
enario 1: Establishing a Cell in a Common Sector
1. (Optional) If an RRU is added, add a sector and sector equipment.
a. Run the ADD SECTOR command to add a sector.
NOTE:
A cell can work in 1T2R, 2T2R, 2T4R, or 4T4R mode, based on which the ANTNUM parameter is configured. For example, if a cell works in 2T4R
mode, the ANTNUM parameter must be set to 4.
b. Run the ADD SECTOREQM command to add sector equipment.
NOTE:
If the SECTOR.CREATESECTOREQM parameter is set to TRUE(TRUE) by running the ADD SECTOR command, ADD SECTOREQM is not required.
The default value of this parameter is FALSE(FALSE).
2. (Optional) If the baseband equipment needs to be bound to a cell, run the ADD BASEBANDEQM command to add baseband equipment.
3. (Optional) If the operator and tracking area information is not configured, perform the following steps:
a. Run the ADD CNOPERATOR command to add an operator.

b. Run the ADD CNOPERATORTA command to add a tracking area.
4. Run the ADD CELL command to add a cell.

5. Run the ADD EUCELLSECTOREQM command to bind sector equipment and optionally baseband equipment for the cell.
6. Run the ADD CELLOP command to specify the operator for the cell.
7. Run the ACT CELL command to activate the cell.
enario 2: Establishing Cells in Multiple Sectors with RRU/RFU Splitting
Establishing two 2T2R cells by splitting a 4T4R RRU is used as an example in this section. Perform steps described in Scenario 1: Establishing a Cell in a Common Sector. In
addition, pay attention to the following details:
• When running the ADD SECTOR and ADD SECTOREQM commands, configure two sectors with the antNum parameter set to 2, and then allocate two antenna
channels of the RRU to one sector and the other two antenna channels to the other sector.
• When running the ADD EUCELLSECTOREQM command, bind the two cells with two pieces of sector equipment.
enario 3: Establishing a Cell in a Single Sector with RRU/RFU Combination
Establishing a 4T4R cell by combining two 2T2R RRUs is used as an example in this section. Perform steps described in Scenario 1: Establishing a Cell in a Common Sector. In
addition, pay attention to the following details:
When running the ADD SECTOR and ADD SECTOREQM commands, set the antNum parameter to 4. Then, divide the four antenna ports into two groups and allocate the
groups to the two 2T2R RRUs respectively.
enario 4: Establishing a Cell in Multiple Sectors Served by Different RRUs
Establishing a digital combination 3-sector cell is used as an example in this section. Perform steps described in Scenario 1: Establishing a Cell in a Common Sector. In addition, pay
attention to the following details:
• Run the ADD SECTOR and ADD SECTOREQM commands each for three times to establish a sector on each RRU.
• When running the ADD CELL command, establish only one cell with the MultiRruCellFlag parameter set to BOOLEAN_TRUE(True) and the MultiRruCellMode
parameter set to DIGITAL_COMBINATION(Cell Digital Combination).
• When running the ADD EUCELLSECTOREQM command, bind the three pieces of sector equipment that have been established to one cell.

This section provides the MML command examples in different scenarios.
• Scenario 1: Establishing a Cell in a Common Sector

• Scenario 2: Establishing Cells in Multiple Sectors with RRU/RFU Splitting
• Scenario 3: Establishing a Cell in a Single Sector with RRU/RFU Combination
• Scenario 4: Establishing a Cell in Multiple Sectors Served by Different RRUs/RFUs
NOTE:
The parameter settings in the following commands are used for reference only. Set the parameters based on network requirements.
enario 1: Establishing a Cell in a Common Sector
//(Optional) Adding a sector and sector equipment if a new RRU is configured

ADD SECTOR: SECTORID=0, ANTNUM=2, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0A, ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0B, CREATESE
CTOREQM=TRUE, SECTOREQMID=0;
//(Optional) Performing the following steps if no operator or tracking area information is added
1. Add an operator.
ADD CNOPERATOR: CnOperatorId=0, CnOperatorName="mobile", CnOperatorType=CNOPERATOR_PRIMARY, Mcc="460", Mnc="01";
2. Add a tracking area.
ADD CNOPERATORTA: TrackingAreaId=0, CnOperatorId=0, Tac=33;
//Adding a cell
ADD CELL: LocalCellId=0, CellName="cell0", FreqBand=12, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=5020, UlBandWidth=CELL_BW_N50, DlBandWi
dth=CELL_BW_N50, CellId=0, PhyCellId=0, FddTddInd=CELL_FDD, RootSequenceIdx=0, CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaI
dCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, TxRxMode=2T2R;
//Adding sector equipment for a cell
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0;
//Adding an operator for a cell
ADD CELLOP: LocalCellId=0, TrackingAreaId=0;
//Activating a cell
ACT CELL: LocalCellId=0;
enario 2: Establishing Cells in Multiple Sectors with RRU/RFU Splitting
Establishing two 2T2R cells by splitting a 4T4R RRU is used as an example.

//Adding two 2T2R sectors with the sector number as 0 and 1 (sector 0 uses antenna ports A and B, and sector 1 uses antenna ports C and D)
ADD SECTOR: SECTORID=0, SECNAME="0", LOCATIONNAME="0", USERLABEL="0", ANTNUM=2, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0A, ANT2C
N=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0B, CREATESECTOREQM=TRUE, SECTOREQMID=0;
ADD SECTOR: SECTORID=1, SECNAME="0", LOCATIONNAME="0", USERLABEL="0", ANTNUM=2, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0C, ANT2C
N=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0D, CREATESECTOREQM=TRUE, SECTOREQMID=1;
1. Add an operator.
//Adding two cells

//Adding two 2T2R sector equipment groups
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;
//Adding the operator information about two cells


Activating two cells
enario 3: Establishing a Cell in a Single Sector with RRU/RFU Combination
//Adding a sector and sector equipment (separating four antennas to two groups and configuring them to the two 2T2R RRUs)
ADD SECTOR: SECTORID=0, SECNAME="Sector0", LOCATIONNAME="River", USERLABEL="0", ANTNUM=4, ANT1CN=0, ANT1SRN=60, ANT1SN=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=TRUE, SECTOREQMID=0;
1. Add an operator.
//Adding a cell
//Adding the mapping relationship between a cell and sector equipment
//Activating a cell
ACT CELL:LocalCellId=0;
enario 4: Establishing a Cell in Multiple Sectors Served by Different RRUs/RFUs
Establishing a digital combination cell in two sectors is used as an example.

//(Optional) Adding a sector and sector equipment if a new RRU is configured
ADD SECTOR:SECTORID=0,ANTNUM=2,ANT1CN=0,ANT1SRN=60,ANT1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,CREATESECTOREQM=TRU
E,SECTOREQMID=0;
ADD SECTOR:SECTORID=1,ANTNUM=2,ANT1CN=0,ANT1SRN=61,ANT1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=61,ANT2SN=0,ANT2N=R0B,CREATESECTOREQM=TRU
E,SECTOREQMID=1;
1. Add an operator.
//Adding a digital combination cell

ADD CELL: LocalCellId=0, CellName="Cell0", FreqBand=7, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=2900, UlBandWidth=CELL_BW_N50, DlBandWid
th=CELL_BW_N50, CellId=0, PhyCellId=0, FddTddInd=CELL_FDD, RootSequenceIdx=0, CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaId
CfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_TRUE, MultiRruCellMode=DIGITAL_COMBINATION, TxRxMode=2T2R;
//Adding the mapping relationship between a cell and sector equipment
//Activating a cell
1. Run the DSP CELL command to check the cell status.

If the Cell instance state parameter is Normal, the cell has been activated.
2. Use a UE to access this cell. If the UE successfully accesses the cell, the cell is working properly.
For cell-related reconfiguration, see eRAN Reconfiguration Guide.
6.4.8 Deactivation
ing the CME
ing MML Commands
Run the DEA CELL command to deactivate the cell.
ML Command Examples
DEA CELL: LocalCellId=0;
Performance Monitoring
None
Parameter Optimization
None
Possible Issues
ult Description
Cell status is abnormal.
ult Handling
1. Start cell status monitoring on the U2000 client to check the cell status. If a cell outage occurs, perform operations according to Cell Outage Detection and Recovery
Feature Parameter Description.

2. View the alarms on the U2000 client. If any alarm has been reported, clear the alarm according to the alarm reference of the eNodeB.
The following table lists the common alarms related to a cell.
Alarm ID Alarm Name
ALM-26816 Licensed Feature Unusable
ALM-26818 No License Running in System
ALM-29240 Cell Unavailable
ALM-29243 Cell Capability Degraded
ALM-29245 Cell Blocked
ALM-29248 RF Out of Service
7 Parameters
Table 7-1 Parameters
MO Parameter ID MML Command Feature ID Feature Name Description
Cell MultiRruCellFlag ADD CELL LOFD- SFN Meaning: Indicates whether to enable or disable the
MOD CELL 003029 / Adaptive multi-RRU cell feature.
LST CELL TDLOFD- SFN/SDMA GUI Value Range: BOOLEAN_FALSE(False),
001075 Inter-BBP BOOLEAN_TRUE(True)
TDLOFD- SFN Unit: None
002008 Inter-BBU Actual Value Range: BOOLEAN_FALSE,
TDLOFD- SFN BOOLEAN_TRUE
001098 Inter-BBP Default Value: BOOLEAN_FALSE(False)
TDLOFD- Adaptive
001080 SFN/SDMA
TDLOFD- Inter-BBU
001081 Adaptive
TDLOFD- SFN/SDMA
001082
Cell MultiRruCellMode ADD CELL LOFD- SFN Meaning: Indicates the type of the multi-RRU cell.
MOD CELL 003029 / Adaptive GUI Value Range: SFN(SFN), CELL_COMBINATION
LST CELL TDLOFD- SFN/SDMA (Cell Combination), TWO_RRU_COMBINATION(TWO
001075 Inter-BBP RRU Combination), DIGITAL_COMBINATION(Cell
LOFD- SFN Digital Combination), MPRU_AGGREGATION
070205 / Inter-BBU (MPRU_AGGREGATION)
TDLOFD- SFN Unit: None
002008 Actual Value Range: SFN, CELL_COMBINATION,
Inter-BBP
TDLOFD- Adaptive TWO_RRU_COMBINATION, DIGITAL_COMBINATION,
001098 SFN/SDMA MPRU_AGGREGATION
TDLOFD- Inter-BBU Default Value: SFN(SFN)
001080 Adaptive
TDLOFD- SFN/SDMA
001081
TDLOFD-
001082
CellDlpcPdschPa PaPcOff MOD CELLDLPCPDSCHPA LBFD- Dynamic Meaning: Indicates the PA to be used when PA
LST CELLDLPCPDSCHPA 002016 / Downlink adjustment for PDSCH power control is disabled, DL
TDLBFD- Power ICIC is disabled, and the even power distribution is used
002016 Allocation for the PDSCH.
GUI Value Range: DB_6_P_A(-6 dB), DB_4DOT77_P_A
(-4.77 dB), DB_3_P_A(-3 dB), DB_1DOT77_P_A(-1.77
dB), DB0_P_A(0 dB), DB1_P_A(1 dB), DB2_P_A(2 dB),
DB3_P_A(3 dB)
Unit: dB
Actual Value Range: DB_6_P_A, DB_4DOT77_P_A,
DB_3_P_A, DB_1DOT77_P_A, DB0_P_A, DB1_P_A,
DB2_P_A, DB3_P_A
Default Value: DB_3_P_A(-3 dB)
PDSCHCfg Pb MOD PDSCHCFG LBFD- Dynamic Meaning: Indicates the scaling factor index of the Energy
LST PDSCHCFG 002016 / Downlink Per Resource Element (EPRE) on the PDSCH. This
TDLBFD- Power scaling factor is determined by the value of this
002016 Allocation parameter and the antenna port. For details, see 3GPP
LBFD- Broadcast of TS 36.213.
002009 / system GUI Value Range: 0~3
TDLBFD- information Unit: None
002009 Actual Value Range: 0~3
Default Value: 1
eUCellSectorEqm ReferenceSignalPwr ADD EUCELLSECTOREQM None None Meaning: Indicates the reference signal power of the cell
MOD EUCELLSECTOREQM sector device. The value 32767 indicates that this
LST EUCELLSECTOREQM reference signal power parameter is invalid. In this case,
the reference signal power of the cell equals the value of
the PDSCHCFG parameter. For details, see 3GPP TS
36.213.This parameter is valid only when a multi-RRU
cell works in SFN,MPRU_AGGREGATION or cell
combination mode.
GUI Value Range: -600~500,32767


Unit: 0.1dBm
Actual Value Range: -60~50,32767
Default Value: 32767
EuSectorEqmGroup ReferenceSignalPwr ADD EUSECTOREQMGROUP None None Meaning: Indicates the reference signal power of a sector
MOD EUSECTOREQMGROUP equipment group for a cell (all sets of sector equipment in
LST EUSECTOREQMGROUP the sector equipment group have the same reference
signal power). If this parameter is set to 32767, the
parameter value is invalid, and the cell uses the
reference signal power specified by the
ReferenceSignalPwr parameter in the PDSCHCFG MO.
For details, see 3GPP TS 36.213. This parameter takes
effect only when parameter MultiRruCellFlag is set to
BOOLEAN_TRUE and MultiRruCellMode is set to
MPRU_AGGREGATION or FDD SFN, respectively.
Unit: 0.1dBm
PDSCHCfg ReferenceSignalPwr MOD PDSCHCFG LBFD- Dynamic Meaning: Indicates the cell reference signal power of
LST PDSCHCFG 002016 / Downlink each physical antenna. However, the cell reference
TDLBFD- Power signal power delivered in SIB2 is that of each logical
002016 Allocation antenna.
LBFD- Broadcast of GUI Value Range: -600~500
002009 / system Unit: 0.1dBm
TDLBFD- information Actual Value Range: -60~50
002009
Default Value: 182
SECTOR SECTORID ADD SECTOR None None Meaning: Indicates the number of the sector.
DSP SECTOR GUI Value Range: 0~65535
LST SECTOR
Unit: None
MOD SECTOR
RMV SECTOR Actual Value Range: 0~65535
Default Value: None
SECTOR SECNAME ADD SECTOR None None Meaning: Indicates the name of the sector.
MOD SECTOR GUI Value Range: 0~99 characters
LST SECTOR
Unit: None
Actual Value Range: 0~99 characters
Default Value: NULL(empty string)
SECTOR LOCATIONNAME ADD SECTOR None None Meaning: Indicates the location name of the base station.
MOD SECTOR GUI Value Range: 0~64 characters
LST SECTOR
Unit: None
SECTOR USERLABEL ADD SECTOR None None Meaning: Indicates the user-defined information of a
MOD SECTOR sector. The value of this parameter consists of xx::yy and
LST SECTOR common character strings, which are separated by
percentage signs (%), for example, %tel::88888888%
owner::huawei%20130101. xx::yy indicates that the value
of xx is yy.
GUI Value Range: 0~255 characters
Unit: None
SECTOREQM SECTOREQMID ADD SECTOREQM None None Meaning: Indicates the number of the sector equipment.
LST SECTOREQM GUI Value Range: 0~65535
MOD SECTOREQM
Unit: None
RMV SECTOREQM
LST SECTOR Actual Value Range: 0~65535
Default Value: None
SECTOREQM SECTORID ADD SECTOREQM None None Meaning: Indicates the number of the sector in which the
LST SECTOREQM sector equipment is located.
GUI Value Range: 0~65535
Unit: None
Actual Value Range: 0~65535
Default Value: None
CnOperator CnOperatorId ADD CNOPERATOR LOFD- RAN Sharing Meaning: Indicates the index of the operator.
LST CNOPERATOR 001036 with Common GUI Value Range: 0~5
MOD CNOPERATOR LOFD- Carrier Unit: None
RMV CNOPERATOR 001037 RAN Sharing Actual Value Range: 0~5
LOFD- with
Default Value: None
001086 Dedicated
TDLOFD- Carrier
001112 RAN Sharing
LOFD- by More
070206 Operators
MOCN
Flexible
Priority
Based
Camping
Hybrid RAN
Sharing


CnOperator CnOperatorName ADD CNOPERATOR LOFD- RAN Sharing Meaning: Indicates the name of the operator.
MOD CNOPERATOR 001036 / with Common GUI Value Range: 1~32 characters
LST CNOPERATOR TDLOFD- Carrier Unit: None
001036 RAN Sharing Actual Value Range: 1~32 characters
LOFD- with
Default Value: None
001037 / Dedicated
TDLOFD- Carrier
001037 RAN Sharing
LOFD- by More
001086 / Operators
TDLOFD- MOCN
001086 Flexible
TDLOFD- Priority
001112 Based
LOFD- Camping
070206 Hybrid RAN
Sharing
CnOperator CnOperatorType ADD CNOPERATOR LOFD- RAN Sharing Meaning: Indicates the type of the operator. The operator
MOD CNOPERATOR 001036 / with Common can be the primary operator or a secondary operator. For
LST CNOPERATOR TDLOFD- Carrier each eNodeB, only one primary operator but more than
001036 RAN Sharing one secondary operator can be configured.
LOFD- with GUI Value Range: CNOPERATOR_PRIMARY(Primary
001037 / Dedicated Operator), CNOPERATOR_SECONDARY(Secondary
TDLOFD- Carrier Operator)
001037 RAN Sharing Unit: None
LOFD- by More Actual Value Range: CNOPERATOR_PRIMARY,
001086 / Operators CNOPERATOR_SECONDARY
TDLOFD- MOCN Default Value: None
001086 Flexible
TDLOFD- Priority
001112 Based
LOFD- Camping
070206 Hybrid RAN
Sharing
CnOperator Mcc ADD CNOPERATOR LOFD- RAN Sharing Meaning: Indicates the mobile country code (MCC) of the
MOD CNOPERATOR 001036 / with Common operator.
LST CNOPERATOR TDLOFD- Carrier GUI Value Range: 3 characters
001036 RAN Sharing Unit: None
LOFD- with Actual Value Range: 000~999
001037 / Dedicated
Default Value: None
TDLOFD- Carrier
001037 RAN Sharing
LOFD- by More
001086 / Operators
TDLOFD- MOCN
001086 Flexible
TDLOFD- Priority
001112 Based
LOFD- Camping
070206 Hybrid RAN
Sharing
CnOperator Mnc ADD CNOPERATOR LOFD- RAN Sharing Meaning: Indicates the mobile network code (MNC) of
MOD CNOPERATOR 001036 / with Common the operator. The value of this parameter is a string of
LST CNOPERATOR TDLOFD- Carrier two or three characters, each of which must be a digit in
001036 RAN Sharing the range from 0 to 9.
LOFD- with GUI Value Range: 2~3 characters
001037 / Dedicated Unit: None
TDLOFD- Carrier Actual Value Range: 00~99,000~999
001037 RAN Sharing Default Value: None
LOFD- by More
001086 / Operators
TDLOFD- MOCN
001086 Flexible
TDLOFD- Priority
001112 Based
LOFD- Camping
070206 Hybrid RAN
Sharing
CnOperatorTa TrackingAreaId ADD CNOPERATORTA LOFD- RAN Sharing Meaning: Indicates the tracking area ID, which uniquely
LST CNOPERATORTA 001036 / with Common identifies an entry of tracking area information. This
MOD CNOPERATORTA TDLOFD- Carrier parameter is used only within the eNodeB and is not
RMV CNOPERATORTA 001036 RAN Sharing used during the information exchange with the EPC. This
LOFD- with is different from the TAI configured in the EPC TAL.
001037 / Dedicated GUI Value Range: 0~65535
TDLOFD- Carrier Unit: None
001037 Hybrid RAN Actual Value Range: 0~65535
LOFD- Sharing Default Value: None
070206
CnOperatorTa CnOperatorId ADD CNOPERATORTA LOFD- RAN Sharing Meaning: Indicates the index of the operator.
MOD CNOPERATORTA 001036 / with Common GUI Value Range: 0~5
LST CNOPERATORTA TDLOFD- Carrier Unit: None
001036 RAN Sharing Actual Value Range: 0~5
LOFD- with
Default Value: None
001037 / Dedicated
TDLOFD- Carrier
001037 Hybrid RAN
Sharing


LOFD-
070206
CnOperatorTa Tac ADD CNOPERATORTA LOFD- RAN Sharing Meaning: Indicates the tracking area code (TAC), which
MOD CNOPERATORTA 001036 / with Common is used by the EPC to determine the area within which
LST CNOPERATORTA TDLOFD- Carrier paging messages are sent. One tracking area is
001036 RAN Sharing comprised of one or more cells.
LOFD- with GUI Value Range: 1~65533,65535
001037 / Dedicated Unit: None
TDLOFD- Carrier Actual Value Range: 1~65533,65535
001037 Hybrid RAN Default Value: None
LOFD- Sharing
070206
Cell LocalCellId ACT CELL None None Meaning: Indicates the local ID of the cell. It uniquely
ADD CELL identifies a cell within a BS.
ADD CELLBAND GUI Value Range: 0~255
BLK CELL
Unit: None
DEA CELL
DSP CELL Actual Value Range: 0~255
DSP CELLCALIBRATION Default Value: None
DSP CELLCAMCSTATUS
DSP CELLPHYTOPO
DSP CELLULCOMPCLUSTER
DSP DDCELLGROUP
DSP LIOPTRULE
DSP PRIBBPADJUST
LST CELL
LST CELLBAND
MOD CELL
RMV CELL
RMV CELLBAND
RMV CELLNRT
RST EUCELLRES
STR CELLRFLOOPBACK
STR CELLSELFTEST
STR LRTWPRTTST
STR PRIBBPADJUST
UBL CELL
DSP LRTWPRTTST
DSP PRIBBPRESINFO
Cell CellName ADD CELL None None Meaning: Indicates the name of the cell.
MOD CELL GUI Value Range: 1~99 characters
DSP CELL
Unit: None
LST CELL
Default Value: None
Cell CsgInd ADD CELL LBFD- Broadcast of Meaning: Indicates whether the cell is a closed
MOD CELL 002009 / system subscriber group (CSG) cell. A CSG cell has restrictions
LST CELL TDLBFD- information on UE access. It broadcasts a specific CSG ID in the SIB
002009 Cell Selection and only those UEs of the group can access the CSG
LBFD- and Re- cell. BOOLEAN_FALSE indicates that the cell is not a
00201803 / selection CSG cell, and BOOLEAN_TRUE indicates that the cell is
TDLBFD- a CSG cell. Currently, Huawei eNodeBs do not support
00201803 CSG cells.
GUI Value Range: BOOLEAN_FALSE(False),
BOOLEAN_TRUE(True)
Unit: None
Actual Value Range: BOOLEAN_FALSE,
BOOLEAN_TRUE
Default Value: BOOLEAN_FALSE(False)
Cell UlCyclicPrefix ADD CELL LBFD- Normal CP Meaning: Indicates the UL cyclic prefix length of a cell. A
MOD CELL 00100401 / Extended CP cyclic prefix can be a common or extended cyclic prefix.
LST CELL TDLBFD- An extended cyclic prefix is generally used in a complex
Broadcast of
00100401 system environment with a strong multi-path effect and long
LOFD- information delay. In a cell, the UL cyclic prefix length can be
001031 / different from the DL one. In addition, the UL or DL cyclic
TDLOFD- prefix length of a cell must be the same as that of the cell
001031 using the same BBP. For details, see 3GPP TS 36.211.
LBFD- GUI Value Range: NORMAL_CP(Normal),
002009 / EXTENDED_CP(Extended)
TDLBFD- Unit: None
002009 Actual Value Range: NORMAL_CP, EXTENDED_CP
Default Value: NORMAL_CP(Normal)
Cell DlCyclicPrefix ADD CELL LBFD- Normal CP Meaning: Indicates the length of the DL cyclic prefix of a
MOD CELL 00100401 / Extended CP cell. A DL cyclic prefix can be a common or extended
LST CELL TDLBFD- cyclic prefix. An extended cyclic prefix is generally used
00100401 in a complex environment with a strong multi-path effect
LOFD- and long delay. In a cell, the UL cyclic prefix length can
001031 / be different from the DL one. In addition, the UL or DL
TDLOFD- cyclic prefix length of a cell must be the same as that of
001031 the cell using the same BBP. For details, see 3GPP TS
36.211.
GUI Value Range: NORMAL_CP(Normal),
EXTENDED_CP(Extended)
Unit: None
Actual Value Range: NORMAL_CP, EXTENDED_CP
Cell FreqBand ADD CELL


ADD CELLBAND LBFD- Cell Selection Meaning: Indicates the frequency band in which a cell
LST CELLBAND 00201803 / and Re- operates. For details about this parameter, see 3GPP TS
MOD CELL TDLBFD- selection 36.104. For details about the usage of 252 to 255, see
RMV CELLBAND 00201803 Broadcast of the following LTE-U forum document: eNodeB Minimum
LST CELL LBFD- system Requirements for LTE-U SDL V1.0.
002009 / information GUI Value Range: 1~256
TDLBFD- Multi-Band Unit: None
002009 Compatibility Actual Value Range: 1~256
LBFD- Enhancement Default Value: None
070103 / LAA
TDLBFD- (Licensed
00201806 Assisted
LEOFD- Access ) for
110301 DL 2 Carrier
Cell UlEarfcnCfgInd ADD CELL LBFD- Cell Selection Meaning: Indicates whether to configure the uplink
MOD CELL 00201803 / and Re- EARFCN of the cell.
LST CELL TDLBFD- selection GUI Value Range: NOT_CFG(Not configure), CFG
00201803 Broadcast of (Configure)
LBFD- system Unit: None
002009 / information Actual Value Range: NOT_CFG, CFG
TDLBFD-
Default Value: NOT_CFG(Not configure)
002009
Cell UlEarfcn ADD CELL LBFD- Coverage Meaning: Indicates the UL EARFCN of the cell. It is
MOD CELL 00201801 / Based Intra- optional, depending on the setting of the UL EARFCN
LST CELL TDLBFD- frequency configuration indicator (UlEarfcnCfgInd). If the value of
00201801 Handover this parameter is not specified, the default UL EARFCN
LBFD- Cell Selection is used, which is calculated based on the DL EARFCN.
00201803 / and Re- For details, see 3GPP TS 36.104.
TDLBFD- selection GUI Value Range:
00201803 Broadcast of 18000~46589,54436~65535,131972~132671
LBFD- system Unit: None
002009 / information Actual Value Range:
TDLBFD- 18000~46589,54436~65535,131972~132671
002009 Default Value: 18000
Cell DlEarfcn ADD CELL LBFD- Broadcast of Meaning: Indicates the DL EARFCN of the cell. For
MOD CELL 002009 / system details about this parameter, see 3GPP TS 36.104. For
LST CELL TDLBFD- information the detailed usage of 255144 to 262143, see the
002009 Coverage following LTE-U forum document: eNodeB Minimum
LBFD- Based Intra- Requirements for LTE-U SDL V1.0.
00201801 / frequency GUI Value Range:
TDLBFD- Handover 0~65535,66436~67335,255144~256143,260894~262143
00201801 LAA Unit: None
LBFD- (Licensed Actual Value Range:
00201803 / Assisted 0~65535,66436~67335,255144~256143,260894~262143
TDLBFD- Access ) for Default Value: None
00201803 DL 2 Carrier
LEOFD-
110301
Cell UlBandWidth ADD CELL LOFD- Compact Meaning: Indicates the UL bandwidth of the cell, which is
MOD CELL 001051 Bandwidth based on the number of resource blocks (RBs). The
LST CELL LBFD- Broadcast of value CELL_BW_N25 indicates a cell bandwidth of 25
002009 / system RBs. The value CELL_BW_N50 indicates a cell
TDLBFD- information bandwidth of 50 RBs. The mapping between the
002009 Scalable parameter value and the actual cell bandwidth (that is,
TDLBFD- Bandwidth the number of RBs) can be deduced similarly. For
001003 details, see 3GPP TS 36.104.
GUI Value Range: CELL_BW_N6(1.4M), CELL_BW_N15
(3M), CELL_BW_N25(5M), CELL_BW_N50(10M),
CELL_BW_N75(15M), CELL_BW_N100(20M)
Unit: None
Actual Value Range: CELL_BW_N6, CELL_BW_N15,
CELL_BW_N25, CELL_BW_N50, CELL_BW_N75,
CELL_BW_N100
Default Value: None
Cell DlBandWidth ADD CELL LOFD- Compact Meaning: Indicates the DL bandwidth of the cell, which is
MOD CELL 001051 Bandwidth based on the number of resource blocks (RBs). The
DSP DDCELLGROUP LBFD- Broadcast of value CELL_BW_N25 indicates a cell bandwidth of 25
LST CELL 002009 / system RBs. The value CELL_BW_N50 indicates a cell
TDLBFD- information bandwidth of 50 RBs. The mapping between the
002009 Scalable parameter value and the actual cell bandwidth (that is,
TDLBFD- Bandwidth the number of RBs) can be deduced similarly. For
001003 details, see 3GPP TS 36.104.
GUI Value Range: CELL_BW_N6(1.4M), CELL_BW_N15
(3M), CELL_BW_N25(5M), CELL_BW_N50(10M),
CELL_BW_N75(15M), CELL_BW_N100(20M)
Unit: None
Actual Value Range: CELL_BW_N6, CELL_BW_N15,
CELL_BW_N25, CELL_BW_N50, CELL_BW_N75,
CELL_BW_N100
Default Value: None
Cell CellId ADD CELL LBFD- Broadcast of Meaning: Indicates the ID of the E-UTRAN cell. The
MOD CELL 002009 / system combination of this parameter and the eNodeB ID forms
DSP CELLCAMCSTATUS TDLBFD- information the E-UTRAN cell identity. The combination of the
LST CELL 002009 E-UTRAN cell identity and the PLMN identity forms the
ECGI. For details, see 3GPP TS 36.413.


Unit: None
Default Value: None
Cell PhyCellId ADD CELL LOFD- Compact Meaning: Indicates the physical cell ID. For details, see
MOD CELL 001051 Bandwidth 3GPP TS 36.331.
LST CELL LBFD- Broadcast of GUI Value Range: 0~503
002009 / system Unit: None
TDLBFD- information Actual Value Range: 0~503
002009
Default Value: None
Cell AdditionalSpectrumEmission ADD CELL LBFD- Broadcast of Meaning: Indicates the additional spectrum emission,
MOD CELL 002009 / system which restricts the emission power of the UEs in the cell.
LST CELL TDLBFD- information For details, see the 3GPP TS 36.101.
002009 GUI Value Range: 1~32
Unit: None
Default Value: 1
Cell FddTddInd ADD CELL LBFD- Broadcast of Meaning: Indicates the duplex mode of the cell.
MOD CELL 002009 system CELL_FDD indicates the FDD mode, and CELL_TDD
LST CELL TDLBFD- information indicates the TDD mode.
001007 Basic uplink- GUI Value Range: CELL_FDD(FDD), CELL_TDD(TDD)
TDLBFD- downlink Unit: None
00100701 subframe Actual Value Range: CELL_FDD, CELL_TDD
TDLBFD- configuration
Default Value: None
00100702 uplink-
TDLOFD- downlink
001026 subframe
configuration
TDLOFD-
type1&2
00102601
uplink-
TDLOFD-
downlink
00102602
special
TDLOFD- subframe
00102603 configuration
type 7
Optional
uplink-
downlink
subframe
configuration
uplink-
downlink
subframe
configuration
type 0
uplink-
downlink
special
subframe
configuration
type 4
uplink-
downlink
special
subframe
configuration
type 5
Cell CellSpecificOffset ADD CELL LBFD- Coverage Meaning: Indicates the cell specific offset for the serving
MOD CELL 00201801 / Based Intra- cell. It affects the probability of triggering handovers from
LST CELL TDLBFD- frequency the serving cell to its neighboring cells. A smaller value of
00201801 Handover this parameter leads to a higher probability. For details,
TDLBFD- Mobility see 3GPP TS 36.331.
002018 Management GUI Value Range: dB-24(-24dB), dB-22(-22dB), dB-20
TDLBFD- Coverage (-20dB), dB-18(-18dB), dB-16(-16dB), dB-14(-14dB), dB-
00201802 Based Inter- 12(-12dB), dB-10(-10dB), dB-8(-8dB), dB-6(-6dB), dB-5
TDLBFD- frequency (-5dB), dB-4(-4dB), dB-3(-3dB), dB-2(-2dB), dB-1(-1dB),
00201804 Handover dB0(0dB), dB1(1dB), dB2(2dB), dB3(3dB), dB4(4dB),
Distance dB5(5dB), dB6(6dB), dB8(8dB), dB10(10dB), dB12
TDLBFD-
Based Inter- (12dB), dB14(14dB), dB16(16dB), dB18(18dB), dB20
00201805
frequency (20dB), dB22(22dB), dB24(24dB)
TDLOFD-
Handover Unit: dB
001019
Service Actual Value Range: dB-24, dB-22, dB-20, dB-18, dB-16,
TDLOFD-
Based Inter- dB-14, dB-12, dB-10, dB-8, dB-6, dB-5, dB-4, dB-3, dB-2,
001043
frequency dB-1, dB0, dB1, dB2, dB3, dB4, dB5, dB6, dB8, dB10,
TDLOFD- dB12, dB14, dB16, dB18, dB20, dB22, dB24
Handover
001072
PS Inter-RAT Default Value: dB0(0dB)
TDLOFD-
Mobility
001020
between
TDLOFD- E-UTRAN
001046 and UTRAN
TDLOFD- Service
001073 based Inter-
RAT
handover to
UTRAN
Distance
based Inter-
RAT


handover to
UTRAN
PS Inter-RAT
Mobility
between
E-UTRAN
and GERAN
Service
based Inter-
RAT
handover to
GERAN
Distance
based Inter-
RAT
handover to
GERAN
Cell QoffsetFreq ADD CELL LBFD- Coverage Meaning: Indicates the specific frequency offset of the
MOD CELL 00201801 Based Intra- serving cell. This parameter is contained in the
LST CELL LBFD- frequency measurement control information and is related to the
00201803 Handover handover difficulty between the serving cell and the
TDLBFD- Cell Selection neighboring cell. For details, see 3GPP TS 36.331.
002018 and Re- GUI Value Range: dB-24(-24dB), dB-22(-22dB), dB-20
TDLBFD- selection (-20dB), dB-18(-18dB), dB-16(-16dB), dB-14(-14dB), dB-
00201802 Mobility 12(-12dB), dB-10(-10dB), dB-8(-8dB), dB-6(-6dB), dB-5
Management (-5dB), dB-4(-4dB), dB-3(-3dB), dB-2(-2dB), dB-1(-1dB),
TDLBFD-
Coverage dB0(0dB), dB1(1dB), dB2(2dB), dB3(3dB), dB4(4dB),
00201804
Based Inter- dB5(5dB), dB6(6dB), dB8(8dB), dB10(10dB), dB12
TDLBFD- (12dB), dB14(14dB), dB16(16dB), dB18(18dB), dB20
00201805 frequency
Handover (20dB), dB22(22dB), dB24(24dB)
TDLOFD- Unit: dB
001019 Distance
Based Inter- Actual Value Range: dB-24, dB-22, dB-20, dB-18, dB-16,
TDLOFD- dB-14, dB-12, dB-10, dB-8, dB-6, dB-5, dB-4, dB-3, dB-2,
frequency
001043 dB-1, dB0, dB1, dB2, dB3, dB4, dB5, dB6, dB8, dB10,
Handover
TDLOFD- dB12, dB14, dB16, dB18, dB20, dB22, dB24
Service
001072 Default Value: dB0(0dB)
Based Inter-
TDLOFD- frequency
001020 Handover
TDLOFD- PS Inter-RAT
001046 Mobility
TDLOFD- between
001073 E-UTRAN
and UTRAN
Service
based Inter-
RAT
handover to
UTRAN
Distance
based Inter-
RAT
handover to
UTRAN
PS Inter-RAT
Mobility
between
E-UTRAN
and GERAN
Service
based Inter-
RAT
handover to
GERAN
Distance
based Inter-
RAT
handover to
GERAN
Cell RootSequenceIdx ADD CELL LBFD- Random Meaning: Indicates the first logical root sequence, which
MOD CELL 002010 / Access is used to generate the preamble sequence. Each logical
LST CELL TDLBFD- Procedure root sequence corresponds to a physical root sequence.
002010 For the mapping between logical root sequences and
physical root sequences, see 3GPP TS 36.211.
Unit: None
Default Value: None
Cell PreambleFmt ADD CELL LBFD- Random Meaning: Indicates the preamble format used in the cell.
MOD CELL 002010 / Access For details, see 3GPP TS 36.211.
LST CELL TDLBFD- Procedure GUI Value Range: 0~4
002010 Unit: None
Default Value: 0
Cell CellRadius ADD CELL LBFD- Random Meaning: Indicates the radius of the cell, that is, the
MOD CELL 002010 / Access farthest distance that a cell can cover under the condition
LST CELL TDLBFD- Procedure of keeping certain network performance. If this parameter
002010 is set to a value greater than 100 km, the Extended Cell


LBFD- Random Access Radius Beyond 100km feature takes effect. Only
002010 / Access FDD cells can be configured with a radius more than 100
TDLBFD- Procedure / km.
002010 / Extended GUI Value Range: 1~160000
LOFD- Cell Access Unit: m
081223 Radius
beyond
100km Default Value: 10000
Cell CustomizedBandWidthCfgInd ADD CELL LOFD- Compact Meaning: Indicates whether to configure a customized
MOD CELL 001051 Bandwidth bandwidth for a cell. A customized bandwidth can be
LST CELL configured only when a standard bandwidth 1.4 MHz, 5
MHz, 10 MHz, 15 MHz, or 20 MHz has been configured.
GUI Value Range: NOT_CFG(Not configure), CFG
(Configure)
Unit: None
Actual Value Range: NOT_CFG, CFG
Cell CustomizedULBandWidth ADD CELL LOFD- Compact Meaning: Indicates a customized uplink bandwidth
MOD CELL 001051 Bandwidth configured for a cell. A customized bandwidth can be
GUI Value Range:
12~14,44~50,89~100,139~150,183~200
Unit: 0.1MHz
Actual Value Range:
1.2~1.4,4.4~5.0,8.9~10.0,13.9~15.0,18.3~20.0
Default Value: 98
Cell CustomizedDLBandWidth ADD CELL LOFD- Compact Meaning: Indicates a customized downlink bandwidth
MOD CELL 001051 Bandwidth configured for a cell. A customized bandwidth can be
GUI Value Range:
12~14,44~50,89~100,139~150,183~200
Unit: 0.1MHz
Actual Value Range:
1.2~1.4,4.4~5.0,8.9~10.0,13.9~15.0,18.3~20.0
Default Value: 98
Cell UePowerMaxCfgInd ADD CELL LBFD- Uplink Power Meaning: Indicates whether to configure the maximum
MOD CELL 002026 / Control TX power of the UE in the cell. If the value of this
LST CELL TDLBFD- Broadcast of parameter is not specified, the maximum power is
002026 system subject to the UE capability.
LBFD- information GUI Value Range: NOT_CFG(Not configure), CFG
002009 / (Configure)
TDLBFD- Unit: None
002009 Actual Value Range: NOT_CFG, CFG
Cell UePowerMax ADD CELL LBFD- Uplink Power Meaning: Indicates the maximum transmit power that a
MOD CELL 002026 / Control UE can apply to uplink transmission in the cell. It is used
LST CELL TDLBFD- Broadcast of in cell selection criterion S to calculate the compensated
002026 system power. If the value of this parameter is not specified, the
LBFD- information maximum power is subject to the UE capability. For
002009 / details, see 3GPP TS 36.304.
TDLBFD- GUI Value Range: -30~36
002009 Unit: dBm
Actual Value Range: -30~36
Default Value: 23
Cell AirCellFlag ADD CELL None None Meaning: Indicates whether the cell is an air cell.
MOD CELL GUI Value Range: BOOLEAN_FALSE(False),
LST CELL BOOLEAN_TRUE(True)
Unit: None
BOOLEAN_TRUE
Default Value: BOOLEAN_FALSE(False)
Cell CrsPortNum ADD CELL LOFD- DL 2x2 MIMO Meaning: Indicates the number of ports for transmitting
MOD CELL 001001 / DL 4x2 MIMO cell-specific reference signal (CRS). As defined in 3GPP
LST CELL TDLOFD- specifications, this parameter can be set to
DL 4x4 MIMO
001001 CRS_PORT_1, CRS_PORT_2, or CRS_PORT_4. The
DL 4x4 MIMO
LOFD- value CRS_PORT_1 indicates that one CRS port (port 0)
Based on
001003 / is configured. The value CRS_PORT_2 indicates that
TM3 and
TDLOFD- two CRS ports (ports 0 and 1) are configured. The value
TM4
001003 CRS_PORT_4 indicates that four CRS ports (ports 0, 1,
LOFD- 2, and 3) are configured.
001060 GUI Value Range: CRS_PORT_1(1 port), CRS_PORT_2
TDLOFD- (2 ports), CRS_PORT_4(4 ports)
001060 Unit: None
Actual Value Range: CRS_PORT_1, CRS_PORT_2,
CRS_PORT_4
Default Value: CRS_PORT_2(2 ports)
Cell TxRxMode ADD CELL None None Meaning: Indicates the transmission and reception mode
MOD CELL of the cell.
LST CELL GUI Value Range: 1T1R, 1T2R, 2T2R, 2T4R, 4T4R,
8T8R, 2T8R, 4T8R


Unit: None
Actual Value Range: 1T1R, 1T2R, 2T2R, 2T4R, 4T4R,
8T8R, 2T8R, 4T8R
Default Value: None
Cell UserLabel ADD CELL None None Meaning: Indicates the user label of the cell.
MOD CELL GUI Value Range: 0~256 characters
LST CELL
Unit: None
Default Value: None
Cell WorkMode ADD CELL LAOFD- Intra-Band Meaning: If this parameter is set to DL_ONLY for a cell
MOD CELL 00100101 Carrier operating in a 3GPP-defined normal band, preparations
LST CELL LAOFD- Aggregation of handovers from inter-frequency cells to this cell and
00100102 for Downlink admission to this cell fail, causing related performance
LAOFD- 2CC statistics to become abnormal.
00100201 Inter-Band GUI Value Range: UL_DL(Uplink and downlink),
LAOFD- Carrier DL_ONLY(Downlink only), LAA(License Assisted
00100202 Aggregation Access)
for Downlink Unit: None
TDLAOFD-
2CC Actual Value Range: UL_DL, DL_ONLY, LAA
001003
Carrier Default Value: UL_DL(Uplink and downlink)
TDLAOFD-
Aggregation
001002
for Downlink
2CC in
40MHz
Support of
UE Category
6
Aggregation
for Downlink
2CC in
30MHz
Carrier
Aggregation
for Downlink
2CC in
40MHz
Cell CellSlaveBand ADD CELLBAND LBFD- Multi-Band Meaning: Indicates slave frequency bands of a cell. If the
LST CELLBAND 070103 / Compatibility operating frequency of a cell belongs to multiple
RMV CELLBAND TDLBFD- Enhancement frequency bands, the frequency band with the highest
00201806 priority is configured by the FreqBand parameter, and
frequency bands with other priorities are configured by
the CellSlaveBand parameter and added in descending
order based on frequency band priorities. The frequency
band priorities of a cell are determined in network
planning. It is recommended that the frequency bands
supporting UEs that comply with 3GPP TS 36.331
V8.16.0, 3GPP TS 36.331 V9.1.0, 3GPP TS 36.331
V10.5.0, or a later vision be configured as slave
frequency bands.
Unit: None
Default Value: None
Cell EuCellStandbyMode ADD CELL LBFD- Broadcast of Meaning: Indicates the active or standby mode of the
MOD CELL 002009 / system cell. A cell is in active mode by default. If this parameter
LST CELL TDLBFD- information is set to STANDBY, an inter-BBU SFN auxiliary cell can
002009 roll back to the standby mode to provide services if inter-
BBU faults occur. Only common cells, SFN cells or
MPRU_AGGREGATION cells support the standby mode.
GUI Value Range: ACTIVE(Active), STANDBY(Standby)
Unit: None
Actual Value Range: ACTIVE, STANDBY
Default Value: ACTIVE(Active)
eUCellSectorEqm LocalCellId ADD EUCELLSECTOREQM None None Meaning: Indicates the local cell identity. It uniquely
LST EUCELLSECTOREQM identifies a cell within an eNodeB.
MOD EUCELLSECTOREQM GUI Value Range: 0~255
RMV EUCELLSECTOREQM
Unit: None
DSP EURTWP
Default Value: None
eUCellSectorEqm SectorEqmId ADD EUCELLSECTOREQM None None Meaning: Indicates the ID of the sector device that
DSP EURTWP serves the cell,it uniquely identifies a sector device within
LST EUCELLSECTOREQM an eNodeB.
RMV EUCELLSECTOREQM
Unit: None
RST EUCELLRES
DSP INREC Actual Value Range: 0~65535
Default Value: None
eUCellSectorEqm BaseBandEqmId ADD EUCELLSECTOREQM None None Meaning:

MOD EUCELLSECTOREQM Indicates the ID of the baseband equipment serving a
LST EUCELLSECTOREQM cell.
When this parameter is set to 255, the baseband
equipment serving a cell is not specified. In this scenario,
the LTE baseband processing units (LBBPs) serving a
cell are selected among all LBBPs in the eNodeB, and


the LBBPs to which the cell's serving RRU is connected
are preferentially selected.
When this parameter is set to a value other than 255, the
cell is served by LBBPs in the specified baseband
equipment, and the LBBPs to which the cell's serving
RRU is connected are preferentially selected.
GUI Value Range: 0~23,255
Unit: None
Actual Value Range: 0~23,255
Default Value: 255
eUCellSectorEqm SectorCpriCompression ADD EUCELLSECTOREQM LOFD- CPRI Meaning:

MOD EUCELLSECTOREQM 001076 / Compression Indicates the common public radio interface (CPRI)
LST EUCELLSECTOREQM TDLOFD- Enhanced compression type for the sector equipment. CPRI
001076 CPRI compression is used in RRU cascading scenarios to
TDLOFD- Compression enable more RRUs to be cascaded without changing the
081214 CPRI data rate. The parameter value
NO_COMPRESSION indicates that CPRI compression is
not used. The parameter value
NORMAL_COMPRESSION indicates that CPRI
compression is used. The parameter value
ENHANCED_COMPRESSION indicates that enhanced
CPRI compression is used. The parameter value NULL
indicates that this parameter is invalid. The performance
of enhanced CPRI compression is better than the
performance of normal CPRI compression. If the eNodeB
is equipped with LBBPd boards and the CPRI data rate is
9.8 Gbit/s for LTE FDD cells or the CPRI data rate is
greater than 4.9 Gbit/s for LTE TDD cells, the CPRI
compression type of cells served by RRUs in the same
RRU chain or ring must be the same. Before changing
the value of this parameter for a cell served RRUs in the
same RRU chain or ring, ensure that all cells served by
the RRU chain or ring are deactivated. Activate the cells
after you change the parameter value.
This parameter is used only when MultiRruCellMode is
set to SFN or CELL_COMBINATION. This parameter
can be set based on the sector equipment. When this
parameter is set to NULL, the CPRI compression type of
carriers depends on the value of the CPRICompression
parameter in the Cell MO. When this parameter is set to
any other value, the sector CPRI compression type of
carriers depends on the value of the
SectorCpriCompression parameter in the
eUCellSectorEqm MO.
GUI Value Range: NO_COMPRESSION(No
Compression), NORMAL_COMPRESSION(Normal
Compression), ENHANCED_COMPRESSION(Enhanced
Compression), NULL(Invalid)
Unit: None
Actual Value Range: NO_COMPRESSION,
NORMAL_COMPRESSION,
ENHANCED_COMPRESSION, NULL
Default Value: NULL(Invalid)
CellOp LocalCellId ADD CELLOP None None Meaning: Indicates the local ID of the cell. It uniquely
DSP identifies a cell within a base station.
CELLBROADCASTCNOPERATOR
LST CELLOP
MOD CELLOP Unit: None
RMV CELLOP Actual Value Range: 0~255
Default Value: None
CellOp TrackingAreaId ADD CELLOP LBFD- Broadcast of Meaning: Indicates the local tracking area identity of the
LST CELLOP 002009 / system cell, which uniquely identifies an operator's record of
MOD CELLOP TDLBFD- information tracking area information within a cell. This parameter is
RMV CELLOP 002009 Cell Selection used only in the eNodeB and is different from the
LBFD- and Re- tracking area identity configured in the tracking area list
00201803 / selection on the MME.
TDLBFD- GUI Value Range: 0~65535
00201803 Unit: None
Default Value: None
CellOp CellReservedForOp ADD CELLOP LBFD- Broadcast of Meaning:

MOD CELLOP 002009 / system Indicates whether the cell is reserved for operator use.
LST CELLOP TDLBFD- information If this parameter is set to CELL_RESERVED_FOR_OP,
002009 the cell is reserved for operator use. UEs of AC11 or
AC15 in their HPLMN or EHPLMN can consider this cell
as a candidate cell for cell selection or reselection. UEs
of AC11 or AC15 outside their HPLMN/EHPLMN and
UEs of AC0-9/AC12-14 consider this cell as a barred cell
during cell selection or reselection.
If this parameter is set to
CELL_NOT_RESERVED_FOR_OP, the cell is not
reserved for operator use. All UEs can consider this cell
as a candidate cell for cell selection or reselection.
GUI Value Range: CELL_RESERVED_FOR_OP
(Reserved), CELL_NOT_RESERVED_FOR_OP(Not
Reserved)
Unit: None


Actual Value Range: CELL_RESERVED_FOR_OP,
CELL_NOT_RESERVED_FOR_OP
Default Value: CELL_NOT_RESERVED_FOR_OP(Not
Reserved)
CellOp OpUlRbUsedRatio ADD CELLOP LOFD- RAN Sharing Meaning: Indicates the percentage of resource blocks
MOD CELLOP 001036 / with Common (RBs) occupied by the operator on the physical uplink
LST CELLOP TDLOFD- Carrier shared channel (PUSCH) when RAN sharing is enabled
001036 Broadcast of on the eNodeB and the RanShareModeSwitch parameter
LBFD- system of the CellAlgoSwitch MO is set to ON(On). If the data
002009 / information volume is sufficient, the percentage of RBs occupied by
TDLBFD- Hybrid RAN each operator will reach the preset value. Modifications
002009 Sharing on this parameter affect the percentages of RBs
LOFD- occupied by operators on the PUSCH. When the
070206 OpPrbGroupshareSwitch option is selected in RAN
sharing mode, this parameter is used to calculate the
percentage of RBs occupied by the operator resource
group on the PUSCH. The percentage of RBs occupied
by an operator resource group is the sum of percentages
of RBs occupied by operators in the group. This
parameter takes effect only in RAN sharing with common
carriers mode or in hybrid RAN sharing mode with more
than one CellOp MO being configured.
Unit: %
Default Value: 16
CellOp OpDlRbUsedRatio ADD CELLOP LOFD- RAN Sharing Meaning: Indicates the percentage of resource blocks
MOD CELLOP 001036 / with Common (RBs) occupied by the operator on the physical downlink
LST CELLOP TDLOFD- Carrier shared channel (PDSCH) when RAN sharing is enabled
001036 Broadcast of on the eNodeB and the RanShareModeSwitch parameter
LBFD- system of the CellAlgoSwitch MO is set to ON(On). If the data
002009 / information volume is sufficient, the percentage of RBs occupied by
TDLBFD- Hybrid RAN each operator will reach the preset value. Modifications
002009 Sharing on this parameter affect the percentage of RBs occupied
LOFD- by operators on the PDSCH. When the
070206 OpPrbGroupshareSwitch option is selected in RAN
sharing mode, this parameter is used to calculate the
percentage of RBs occupied by the operator resource
group on the PDSCH. The percentage of RBs occupied
by an operator resource group is the sum of percentages
of RBs occupied by operators in the group. This
parameter takes effect only in RAN sharing with common
carriers mode or in hybrid RAN sharing mode with more
than one CellOp MO being configured.
Unit: %
Default Value: 16
BASEBANDEQM BASEBANDEQMID ADD BASEBANDEQM None None Meaning: Indicates the number of the baseband
LST BASEBANDEQM equipment.
MOD BASEBANDEQM GUI Value Range: 0~23
RMV BASEBANDEQM
Unit: None
Default Value: None
BASEBANDEQM BASEBANDEQMTYPE ADD BASEBANDEQM None None Meaning: Indicates the type of baseband equipment.
LST BASEBANDEQM GUI Value Range: UL(UL), DL(DL), ULDL(Combined UL
MOD BASEBANDEQM and DL)
RMV BASEBANDEQM
Unit: None
Actual Value Range: UL, DL, ULDL
Default Value: None
8 Counters
There are no specific counters associated with this feature.
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

1. 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation"
2. 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures"
3. 3GPP TS36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC) protocol specification"
4. Cell Outage Detection and Recovery Feature Parameter Description
5. SFN Feature Parameter Description
eRAN
Connection Management Feature Parameter Description
Issue 04
Date 2017-01-15

Notice


2 Contents
1.1 Scope
1.3 Change History
2 Overview
2.1 Introduction
2.2 Benefits
3 Signaling Connection Management

3.1 RRC Connection Setup
3.2 RRC Connection Reestablishment
3.2.1 Conditions for Triggering RRC Connection Reestablishment
3.2.2 RRC Connection Reestablishment Procedure
3.3 RRC Connection Management
3.3.1 Uplink Out-Of-Synchronization Management
3.3.2 UE Inactivity Timer Management
3.3.3 RLF Detection
3.4 Dedicated S1 Connection Setup
3.5 Signaling Connection Release
4 Radio Bearer Management

4.1 SRB2 Setup
4.2 SRB2 Modification
4.3 SRB2 Release
4.4 DRB Setup
4.5 DRB Modification
4.6 DRB Release
5 Related Features
5.1 LBFD-002007 RRC Connection Management
5.2 LBFD-002008 Radio Bearer Management
6 Network Impact
6.1 LBFD-002007 RRC Connection Management
6.2 LBFD-002008 Radio Bearer Management
7.1 When to Use
7.3 Planning
7.4 Deployment
7.4.1 Precautions
7.4.2 Data Preparation and Feature Activation
7.4.4 Deactivation
7.7 Possible Issues
8 Parameters
9 Counters
10 Glossary
Scope
This document describes connection management, including its technical principles, related features, network impact, and engineering guidelines. This document covers the
following features:
• LBFD-002007 RRC Connection Management

• LBFD-002008 Radio Bearer Management
eNodeB Type Model
Micro BTS3202E
BTS3203E
BTS3911E

eNodeB Type Model

BTS3912E
LampSite DBS3900
Intended Audience

Change History
• Feature change
AN11.1 04 (2017-01-15)
Feature change None None N/A
Editorial change Revised the descriptions in 1.1 Scope. None N/A
AN11.1 03 (2016-11-01)
Editorial change Revised the image and description in 3.2.2 RRC Connection None N/A
Reestablishment Procedure.
AN11.1 02 (2016-06-30)
Feature change Added the enhanced RRC connection reestablishment Added the None
protection function. For details, see 3.2.2 RRC Connection GlobalProcSwitch.EnhancedRRCReestProtectThd
Reestablishment Procedure. parameter.
AN11.1 01 (2016-03-07)
Compared with Draft A (2015-12-07) of eRAN11.1, Issue 01 (2016-03-07) of eRAN11.1 includes the following changes.
Feature change Added the parameter for configuring the timer for delaying Added the GlobalProcSwitch.QciParaEffectFlag Macro, micro, and
releasing services of a specified QCI. For details, see 4.6 parameter. LampSite eNodeBs
DRB Release.
Editorial change Revised the descriptions in 3.3.2 UE Inactivity Timer Management. None N/A
AN11.1 Draft A (2015-12-07)
Feature change Added the 3GPP specifications-compliant RRC connection Added the NO_CONTEXT_REEST_SWITCH Macro, micro, and
reestablishment procedure without UE contexts. For (NO_CONTEXT_REEST_SWITCH) option to the LampSite eNodeBs
details, see 3.2.2 RRC Connection Reestablishment Procedure. GlobalProcSwitch.RrcReestOptSwitch parameter.
Optimized the RRC connection setup mechanism. For Added the GLOBALPROCSWITCH.RrcConnPunishThd Macro, micro, and
details, see 3.1 RRC Connection Setup and 6.1 LBFD-002007 RRC parameter. LampSite eNodeBs
Connection Management.
Added the RRC connection reject-triggered cell reselection Added the following parameters: Macro, micro, and
mechanism. For details, see 3.1 RRC Connection Setup, 6.1 • CELLALGOSWITCH.DeprioritisationDeliverInd LampSite eNodeBs
LBFD-002007 RRC Connection Management, and 7 Engineering
• UETIMERCONST.T325
Guidelines.
Added QCI-based configuration of the uplink Added the QciPara.UlSynTimerForQci parameter. Macro, micro, and
synchronization timer. For details, see 3.3.1 Uplink Out-Of- LampSite eNodeBs
Synchronization Management.
Added QCI-based configuration of the UE inactivity timer. Added the following parameters: Macro, micro, and
For details, see 3.3.2 UE Inactivity Timer Management. • QciPara.UeInactivityTimerDynDrxQci LampSite eNodeBs
• QciPara.UeInactiveTimerForQci
• QciPara.UeInactiveTimerPri

Editorial change Reorganized this document. None N/A
ature Support by Macro, Micro, and LampSite Base Stations
None
nction Implementation in Macro, Micro, and LampSite Base Stations
Function Difference
UE release The UE release process varies with base station types.

• A micro eNodeB detects whether the UE is attached to the network after releasing the UE. A macro eNodeB
does not perform this action.
• A micro eNodeB attempts to restore the UE's uplink synchronization before releasing the UE, and delays
releasing the UE for a preset period of time.
For details, see 3.5 Signaling Connection Release.
2 Overview
Introduction
In a Long Term Evolution (LTE) system, connection management involves setup of dedicated connections between user equipment (UE), eNodeBs, and mobility management
entities (MMEs) and release of these connections after services are complete.
Figure 2-1 shows the random access, signaling connection management, and radio bearer management procedures involved in a connection management process.
Figure 2-1 Connection management process
NOTE:
For details about security mode control shown in Figure 2-1, see Radio Security Feature Parameter Description.
1. A UE performs random access when it attempts to set up a connection with the network for service requests, location updates, paging, or other reasons. For details
about random access, see Random Access Control and RACH Optimization Feature Parameter Description.
2. Signaling connections between the UE and the MME are set up. Signaling connections are set up before the security mode control and consists of the following
connections:
• RRC connections: signaling connection between the eNodeB and UE over the air interface
• Dedicated S1 connection: signaling connection between the eNodeB and MME
3. If the UE requests a service, the MME instructs the eNodeB to set up an E-UTRAN radio access bearer (E-RAB), including a radio bearer.
Benefits
Connection management is a basic network feature and a prerequisite for enabling UEs to access the network and perform services on established bearers.
3 Signaling Connection Management
This chapter describes LBFD-002007 RRC Connection Management.

Signaling connections include an RRC connection and a dedicated S1 connection, as shown in Figure 3-1. Generally, a signaling connection is set up for a service bearer. It can
also be set up only for a signaling procedure, such as a UE location update.

Figure 3-1 Signaling connection protocol stack in LTE
Signaling connection management involves RRC connection setup, RRC connection reestablishment, RRC connection management, dedicated S1 connection setup, and
signaling connection release.
RRC Connection Setup

During RRC connection setup, SRB1 is set up. Before an S1 connection is set up, the eNodeB cannot obtain the UE context from the evolved packet core (EPC). Therefore,
security mode activation and SRB1 encryption and integrity protection are not required during RRC connection setup. Measurement configuration can be performed for a UE
during RRC connection setup, but the UE can be handed over only after the security mode is activated.
Figure 3-2 shows the RRC connection setup procedure.
Figure 3-2 RRC connection setup procedure
1. The UE sends the eNodeB an RRC Connection Request message containing the cause for RRC connection setup.
NOTE:
• The cause for RRC connection setup is related to the NAS process and NAS session types. For details, see 3GPP TS 24.301 V8.1.0.
• The RRC Connection Request message contains the UE_ID field. If the upper layer provides the S-TMSI, the UE signals the S-TMSI to the eNodeB. If
no S-TMSI is available, the UE signals a random value ranging from 0 to 240-1 to the eNodeB. The international mobile subscriber identity (IMSI) of the
UE is unknown to the eNodeB.
2. The eNodeB sets up the context for the UE.

If the eNodeB receives multiple RRC Connection Request messages from a UE within the time specified by the RrcConnStateTimer.FilterReptRrcConnReqTimer
parameter, the eNodeB handles only the latest received one.
Within the window specified by both the UeTimerConst.T300 parameter and the RrcConnStateTimer.FilterReptRrcConnReqTimer parameter, the eNodeB
calculates the number of RRC Connection Request messages sent by a UE, except in high-priority access and emergency call scenarios. If the number of RRC
Connection Request messages sent by a UE is greater than the value of the GlobalProcSwitch.RrcConnPunishThd parameter, the eNodeB responds to the UE
with an RRC Connection Reject message containing the wait time IE, the value of which is determined by the RRCCONNSTATETIMER.T302 parameter. Upon
receiving the message, the UE sends another RRC Connection Request message only after the wait time expires.
3. The eNodeB admits the connection without any judgment and allocates SRB1 resources to the UE.
• If the resource allocation is successful, the subsequent steps proceed. If the resource allocation fails, the eNodeB responds to the UE with an RRC
Connection Reject message. If an RRC connection setup request is rejected, the UE must wait for a period before resending a request. The wait time is
specified by the RrcConnStateTimer.T302 parameter. This timer starts when the UE receives a rejection message and stops when the UE enters the
RRC_CONNECTED state or reselects a cell.
• When the system is overloaded, the eNodeB instructs the UE to lower the cell reselection priority by sending the UE an RRC Connection Reject
message containing the deprioritisationReq IE. Upon receiving the message, the UE attempts to access the network from other cells, thereby relieving
the cell overload. The RRC Connection Reject message contains the deprioritisationReq IE when the CELLALGOSWITCH.DeprioritisationDeliverInd
parameter is not set to UNDELIVER(UNDELIVER). When the RRC Connection Reject message contains the deprioritisationReq IE and the UE supports
the IE, the timer specified by the UETIMERCONST.T325 parameter starts. In this case, the eNodeB proceeds as described in the following table.
If... Then...
The value of the deprioritisationType field in the ◾ Sets the cell reselection priorities of the serving frequency and the
deprioritisationReq IE is FREQUENCY. frequencies on which the RRC Connection Reject message containing
the deprioritisationReq IE has been received to the lowest priority if the
timer specified by the UETIMERCONST.T325 parameter does not expire.
◾ Restores the cell reselection priority to the original priority if the timer
specified by the UETIMERCONST.T325 parameter expires.
The value of the deprioritisationType field in the ◾ Sets the cell reselection priorities of all the E-UTRAN frequencies to the
deprioritisationReq IE is E-UTRA. lowest priority if the timer specified by the UETIMERCONST.T325
parameter does not expire.
◾ Restores the cell reselection priority to the original priority if the timer
specified by the UETIMERCONST.T325 parameter expires.
NOTE:
The deprioritisationReq IE has been introduced since 3GPP Release 11. For details, see 3GPP TS 36.331.
4. The eNodeB sends an RRC Connection Setup message containing SRB1 resource configurations to the UE.
5. The UE configures radio resources based on the SRB1 resource information indicated by the RRC Connection Setup message, and then sends an RRC Connection
Setup Complete message to the eNodeB. After the eNodeB receives the RRC Connection Setup Complete message, the RRC connection is set up.
The timer for the eNodeB to wait for an RRC Connection Setup Complete message is specified by the ENodeBConnStateTimer.WaitRrcConnSetupCmpTimer
parameter.
The eNodeB starts another timer to wait for the UE to send other messages over the Uu interface. The timer is specified by the following parameters:

• ENodeBConnStateTimer.UuMessageWaitingTimer if the UE is not running QCI 1 services

• ENodeBConnStateTimer.UuMessageWaitingTimerQci1 if the UE is running QCI 1 services
RRC Connection Reestablishment

During RRC connection reestablishment, the eNodeB reconfigures SRB1, resumes data transmission on the data radio bearer (DRB), and reactivates the security mode in the
access stratum (AS) without modifying security algorithms. The DRB is resumed only after the RRC connection is reestablished.
3.2.1 Conditions for Triggering RRC Connection Reestablishment

RRC connection reestablishment is triggered to retain the RRC connection for UEs in connected mode for which the security mode has been activated. A UE can initiate RRC
connection reestablishment only when the security mode has been activated in the AS.
A UE initiates RRC connection reestablishment in the following scenarios:
• An RLF occurs.
• A handover fails.
• An inter-RAT handover from E-UTRAN fails.
• The UE receives an integrity check failure indication from the physical layer.
• The RRC connection fails to be reconfigured.
A UE detects an RLF when any of the following conditions is met:
• The timer specified by the UeTimerConst.T310 parameter expires.

• The random access fails and the timer specified by the UeTimerConst.T300, UeTimerConst.T301, RrcConnStateTimer.T304ForEutran,
RrcConnStateTimer.T304ForGeran, or UeTimerConst.T311 parameter is not running.
• The maximum number of RLC retransmissions specified by the RlcPdcpParaGroup.UeMaxRetxThreshold parameter has been reached.
NOTE:
A UE starts the timer specified by the UeTimerConst.T310 parameter when both of the following conditions are met:
• The number of out-of-sync indications consecutively received by the UE from lower layers has reached the upper limit specified by the UeTimerConst.N310
parameter.
• None of the timers specified by the UeTimerConst.T300, UeTimerConst.T301, RrcConnStateTimer.T304ForEutran, RrcConnStateTimer.T304ForGeran, and
UeTimerConst.T311 parameters is running.
When the timer specified by the UeTimerConst.T310 parameter is running and the number of in-sync indications consecutively received from lower layers has reached the
upper limit specified by the UeTimerConst.N311 parameter, the UE stops the timer specified by the UeTimerConst.T310 parameter.
3.2.2 RRC Connection Reestablishment Procedure

Figure 3-3 shows the RRC connection reestablishment procedure.
Figure 3-3 RRC connection reestablishment procedure
1. The UE sends an RRC Connection Reestablishment Request message to the eNodeB.
NOTE:
The cause value contained in the message varies with the triggering cause of the RRC connection reestablishment.
• This message contains the cause value "reconfigurationFailure" if the reestablishment is triggered due to an RRC connection reconfiguration failure.
• This message contains the cause value "handoverFailure" if the reestablishment is triggered due to a handover failure.
• This message contains the cause value "otherFailure" if the reestablishment is triggered due to a radio link failure.
In the cause value, the C-RNTI and physCellId IEs indicate the C-RNTI and physical cell ID of the serving cell, respectively.
2. The eNodeB checks whether the context of the UE exists.

If yes, the eNodeB proceeds to 3.
If no, the target eNodeB sends an RLF Indication message to the source eNodeB based on the cell information contained in the RRC Connection Reestablishment
Request message. If the source eNodeB has the UE context, the source eNodeB initiates the handover process. In the handover, the source eNodeB transfers the
UE context to the target eNodeB. The GlobalProcSwitch.RrcReestOptSwitch parameter specifies whether the target eNodeB can implement RRC connection
reestablishment without UE contexts.
3. The eNodeB authenticates the UE. If the security authentication information in the UE is consistent with that in the eNodeB, the UE passes authentication. After the
authentication, the eNodeB releases original resources and then performs admission and resource allocation again.
When the GlobalProcSwitch.EnhancedRRCReestProtectThd parameter is set to 0 and the number of RRC Connection Reestablishment Request messages
containing the cause value "reconfigurationFailure" sent by a UE within 1 minute exceeds the threshold specified by the GlobalProcSwitch.RrcReestProtectThd
parameter, the eNodeB rejects the subsequent RRC connection reestablishment requests containing the same cause value sent by the UE and the UE enters the
RRC idle mode. The GlobalProcSwitch.RrcReestProtectThd parameter will be disused in later versions.
The GlobalProcSwitch.RrcReestProtectThd parameter is invalid when the GlobalProcSwitch.EnhancedRRCReestProtectThd parameter is set to a non-zero value.
In this situation, RRC connection reestablishment protection is enabled. If the number of RRC connection reestablishment requests sent by a UE to an eNodeB
exceeds the threshold specified by the GlobalProcSwitch.EnhancedRRCReestProtectThd parameter, the eNodeB releases the UE and the UE enters the RRC idle
mode.
If the UE fails the authentication, the eNodeB rejects the RRC connection reestablishment request of the UE.
4. The eNodeB sends the UE an RRC Connection Reestablishment message containing the information about the allocated resources. The UE reconfigures radio
resources based on the message, and then starts encryption and integrity protection again.

5. The UE sends an RRC Connection Reestablishment Complete message to the eNodeB.
RRC Connection Management

RRC connection management applies to UEs in idle and connected modes.
• Connected mode: A UE has set up an RRC connection with the eNodeB. The connected mode is further classified as follows:
◾ Synchronization state: A UE in the connected state maintains uplink synchronization with the eNodeB, and the eNodeB allocates physical uplink control
channel (PUCCH) and sounding reference signal (SRS) resources for the UE.
◾ Out-of-synchronization state: A UE in the connected state does not maintain uplink synchronization with the eNodeB, and the eNodeB releases physical
uplink control channel (PUCCH) and sounding reference signal (SRS) resources for the UE.
• Idle mode: A UE does not set up an RRC connection with the eNodeB, and the UE monitors the paging channel of the eNodeB. For details about UE behaviors in
idle mode, see Idle Mode Management Feature Parameter Description.
The following mechanisms are used for RRC connection management:
• Uplink out-of-synchronization management

• UE inactivity timer management
• Radio link failure detection
3.3.1 Uplink Out-Of-Synchronization Management

Uplink out-of-synchronization management enables an eNodeB to maintain uplink timing for a UE in real time so that the UE remains in the uplink synchronization state.
To maintain uplink timing for a UE, the eNodeB delivers timing advance commands to the UE. Each time after receiving ACK feedback from the UE, the eNodeB starts or
restarts the uplink time alignment timer specified by the TimeAlignmentTimer.TimeAlignmentTimer parameter. If the timer expires, the eNodeB regards that the UE enters the
out-of-synchronization state.
For each UE, the eNodeB also maintains an uplink synchronization timer specified by the RrcConnStateTimer.UlSynTimer parameter to control whether to deliver a Timing
Advance Command message to the UE. The eNodeB starts or restarts the timer for a UE when sending data to or receiving data from the UE. Before the timer expires, the
eNodeB continuously sends Timing Advance Command messages to the UE. After the timer expires, the eNodeB stops sending Timing Advance Command messages to the
UE and the UE stops providing ACK feedback. In this situation, the uplink alignment timer expires, and the eNodeB regards that the UE is in the out-of-synchronization state.
If the UE inactivity timer is shorter than the timer specified by the RrcConnStateTimer.UlSynTimer parameter, the RRC connection is released for the UE and the UE directly
enters the idle mode.
If the UE becomes out of synchronization in the uplink and data arrives on the eNodeB side, the eNodeB instructs the UE to initiate random access. When the UE needs to
transmit data to the eNodeB, the UE initiates random access to restore uplink synchronization.
Since eRAN11.1, the uplink synchronization timer can also be set using the QciPara.UlSynTimerForQci parameter. The RrcConnStateTimer.UlSynTimer parameter will be
removed in a later version and the QciPara.UlSynTimerForQci parameter is recommended.
3.3.2 UE Inactivity Timer Management

With UE inactivity timer management, if a UE does not transmit or receive any data within a period specified by the UE inactivity timer, the eNodeB regards the UE as inactive.
To prevent inactive UEs from using system resources for a long time, the eNodeB releases the RRC connection for the UE and sends a UE Context Release Request message
to the EPC when the UE inactivity timer expires.
The UE Context Release Request message contains the cause value "Radio Connection With UE Lost" if both of the following conditions are met:
• An RLF has been detected or the number of RLC connections for all the DRBs have reached the threshold specified by the
RLCPDCPPARAGROUP.UeMaxRetxThreshold parameter before the UE inactivity timer expires.
• Uplink synchronization does not recover for the UE. In other situations, the UE Context Release Request message contains the cause value "User Inactivity."
E Inactivity Timer When PTT Services Are Ongoing
Table 3-1 lists the parameters specifying the UE inactivity timer used when push to talk (PTT) services are ongoing.
Table 3-1 Parameters specifying the UE inactivity timer when PTT services are ongoing
Value of the CELLALGOSWITCH.DynDrxSwitch Parameter Parameter Specifying the UE Inactivity Timer
DynDrxSwitch(DynDrxSwitch) check box selected QciPara.UeInactivityTimerDynDrxQci
DynDrxSwitch(DynDrxSwitch) check box cleared QciPara.UeInactiveTimerForQci
E Inactivity Timer When Voice Services Are Ongoing
Table 3-2 lists the parameters specifying the UE inactivity timer used when voice services are ongoing.
Table 3-2 Parameters specifying the UE inactivity timer when voice services are ongoing
Value of the Value of the Whether the Parameter Specifying the UE Inactivity Timer
GLOBALPROCSWITCH.QciParaEffectFlag CELLALGOSWITCH.DynDrxSwitch License Listed in
Parameter Parameter Table 3-3 Is
Activated
ON DynDrxSwitch(DynDrxSwitch) Yes or no QciPara.UeInactivityTimerDynDrxQci

check box selected
DynDrxSwitch(DynDrxSwitch) Yes • QciPara.UeInactiveTimerForQci when the

check box cleared CellAlgoSwitch.UEInactiveTimerQCI1Switch
parameter is set to ON(On)
• UE inactivity timer for QCI 5 services when the
CellAlgoSwitch.UEInactiveTimerQCI1Switch
parameter is set to OFF(Off)
No UE inactivity timer for QCI 5 services
OFF DynDrxSwitch(DynDrxSwitch) Yes or no RrcConnStateTimer.UeInactTimerDynDrxQci1

check box selected
DynDrxSwitch(DynDrxSwitch) Yes • RrcConnStateTimer.UeInactiveTimerQci1 when the

check box cleared CellAlgoSwitch.UEInactiveTimerQCI1Switch
parameter is set to ON(On)
• RrcConnStateTimer.UeInactiveTimer when the
CellAlgoSwitch.UEInactiveTimerQCI1Switch
parameter is set to OFF(Off)
No RrcConnStateTimer.UeInactiveTimer
Table 3-3 License of the voice characteristic awareness scheduling feature

Feature ID Feature Name Model License Control Item NE Sales Unit
TDLOFD-081229 Voice Characteristic LT1SVOICAS00 Voice Characteristic Awareness eNodeB per Cell
Awareness Scheduling Scheduling (TDD)
NOTE:
The preceding license has an impact on the configuration of the UE inactivity timer only when the UE is performing voice services and the DynDrxSwitch(DynDrxSwitch)
check box is cleared under the CELLALGOSWITCH.DynDrxSwitch parameter.
E Inactivity Timer in Other Situations
Table 3-4 lists the parameters specifying the UE inactivity timer used in other situations.
Table 3-4 Parameters specifying the UE inactivity timer used in other situations
Value of the Value of the Parameter Specifying the UE Inactivity Timer

GlobalProcSwitch.QciParaEffectFlag Parameter CELLALGOSWITCH.DynDrxSwitch
Parameter
ON DynDrxSwitch(DynDrxSwitch) The eNodeB checks the priorities of the UE inactivity timer

check box selected corresponding to online bearers specified by the
QciPara.UeInactiveTimerPri parameter.
• If the UE inactivity timer corresponding to only one online
bearer has the highest priority, the length of the UE inactivity
timer is equal to the value of the
QciPara.UeInactivityTimerDynDrxQci parameter set for the
bearer.
• If the UE inactivity timer corresponding to multiple online
bearers have the highest priority, the length of the UE
inactivity timer is equal to the maximum value of the
QciPara.UeInactivityTimerDynDrxQci parameter among the
bearers.
DynDrxSwitch(DynDrxSwitch) The eNodeB checks the priorities of the UE inactivity timer

check box cleared corresponding to online bearers specified by the
QciPara.UeInactiveTimerPri parameter.
• If only one online bearer has the highest priority, the length of
the UE inactivity timer is equal to the value of the
QciPara.UeInactiveTimerForQci parameter set for the bearer.
• If multiple online bearers have the highest priority, the length
of the UE inactivity timer is equal to the maximum value of the
QciPara.UeInactiveTimerForQci parameter among the bearers.
OFF DynDrxSwitch(DynDrxSwitch) RrcConnStateTimer.UeInactivityTimerDynDrx

check box selected
DynDrxSwitch(DynDrxSwitch) RrcConnStateTimer.UeInactiveTimer
check box cleared
3.3.3 RLF Detection

The eNodeB determines whether a UE experiences an RLF based on the following principles:
• If the TimeAlignmentTimer.TimeAlignmentTimer parameter is set to a value other than INFINITY(Infinity), the eNodeB checks whether an RLF occurs based on the
status of the time alignment (TA) timer.
If... Then...
The timer does not expire The radio link of the UE is functional.
The timer expires • The eNodeB instructs the UE to initiate random access when the eNodeB needs to transmit data to the
UE.
• The UE initiates random access when the UE needs to transmit data to the eNodeB.
◾ If the synchronization is successful, the radio link of the UE recovers.
◾ If the synchronization fails, an RLF has occurred. In this case, the eNodeB releases the RRC
connection for the UE.
• If the GLOBALPROCSWITCH.UeLinkAbnormalDetectSwitch parameter is set to ON(On), the RLF detection function is enabled. With this function, the eNodeB
checks for an RLF based on the channel quality indicator (CQI) reported by the UE. If the number of CQIs not received by the eNodeB within a specified period
exceeds a specified threshold, an RLF occurs. If the radio link is abnormal, the eNodeB releases the RRC connection for the UE.
When the eNodeB releases the RRC connection for a UE due to an RLF, it sends the EPC a UE CONTEXT RELEASE REQUEST message containing the cause value "Radio
Connection With UE Lost."
Dedicated S1 Connection Setup

Figure 3-4 shows the dedicated S1 connection setup procedure.

Figure 3-4 Dedicated S1 connection setup procedure
1. After receiving an RRC Connection Setup Complete message containing a NAS message, the eNodeB allocates a dedicated S1AP ID to the UE, encapsulates the
NAS message and S1AP ID in an Initial UE Message, and sends the message to the MME.
NOTE:
For details about how to select an MME when an eNodeB connects to multiple MMEs, see S1-Flex Feature Parameter Description.
2. The MME obtains the cause for this connection setup from the NAS message contained in the Initial UE Message, handles the UE service request, and assigns the
dedicated S1AP ID to the UE.
The timer for the eNodeB to wait for S1AP-related messages from the MME is specified by the ENodeBConnStateTimer.S1MessageWaitingTimer parameter if the
UE is not running QCI 1 services. The timer for the eNodeB to wait for S1AP-related messages from the MME is specified by the
ENodeBConnStateTimer.S1MsgWaitingTimerQci1 parameter if the UE is running QCI 1 services.
3. The MME sends an Initial Context Setup Request message to the eNodeB. This message may contain the UE context and EPS bearer context.
4. The eNodeB creates a context for the UE, and generates security keys for the service bearer and signaling connection based on the received security parameters.
NOTE:
The eNodeB selects a security algorithm supported by both the eNodeB and UE and then sends the algorithm to the UE using a Security Mode Command message.
For details about the security mode handling mechanism, see Radio Security Feature Parameter Description.
5. The eNodeB makes an admission decision and performs resource allocation.

6. The eNodeB sends a Security Mode Command message, instructing the UE to start integrity protection and encryption. At this moment, downlink encryption is
started.
7. The eNodeB sends an RRC Connection Reconfiguration message to the UE for the setup of SRB2 and DRB. Encryption and integrity protection have been
performed for this message.
8. After receiving the Security Mode Command message from the eNodeB, the UE uses the encryption algorithm specified by the eNodeB to generate security keys for
both service bearers and signaling connections. Then, the UE sends a Security Mode Complete message, which is not encrypted. After the eNodeB receives this
message, uplink encryption is started.
9. The UE sets up a dedicated S1 connection based on the RRC Connection Reconfiguration message and then sends an RRC Connection Reconfiguration Complete
message to the eNodeB.
10. The eNodeB sends an Initial Context Setup Response message to the MME.
The eNodeB simultaneously sends security parameters and bearer parameters to the UE. The security mode setup starts first. The RRC Connection Reconfiguration message
can be sent before the security mode setup ends. This mechanism reduces the delay from the initial UE access to the bearer setup.
Signaling Connection Release

Signaling connection release consists of dedicated S1 connection release and RRC connection release. After an RRC connection is released, the signaling connection and all
the involved radio bearers are released. Figure 3-5 shows a signaling connection release procedure.

Figure 3-5 Signaling connection release procedure
A signaling connection release procedure is triggered in the following scenarios:
• The MME sends a UE Context Release Command message to the eNodeB when the service process is complete on the NAS set up between the UE and MME or
when the UE aborts the service.
• The eNodeB sends a UE Context Release Request message to the MME upon detecting an exception, such as the expiry of the UE inactivity timer or no data
transmission or reception on the UE side. Then, the eNodeB waits for a UE Context Release Command message from the MME.
Then, the eNodeB performs the following operations:
1. Releases transport resources and initiates RRC connection release over the Uu interface.
2. Sends an RRC Connection Release message to the UE, instructing the UE to release radio resources.
In certain scenarios such as when the UE is powered off or in airplane mode, the UE does not reply the RLC-layer ACK message upon receiving the RRC
Connection Release message. As a result, the eNodeB does not receive any responses from the UE and repeatedly sends unnecessary release messages, which
increases radio resources overheads. When a cell is overloaded due to heavy traffic in the preceding scenarios, the number of retransmitted RRC Connection
Release messages at the RLC layer is decreased if the SPECSIGRETRANSOPTSWITCH(SPECSIGRETRANSOPTSWITCH) check box under the
ENodeBAlgoSwitch.HighLoadNetOptSwitch parameter is selected. This reduces radio resource overheads.
3. Releases radio resources.
4. Sends a UE Context Release Complete message to the MME, indicating that the resources are released.
5. Releases the UE context. Then, the UE switches from the RRC_CONNECTED state to the RRC_IDLE state.
NOTE:
The MME can also release the dedicated S1 connection to simultaneously release all the E-RABs.
For micro eNodeBs:
• When a UE becomes inactive and the signaling link has been released, the UE may have lost connections with the network. When the
GlobalProcSwitch.UeRelChkLostSwitch parameter is set to ON(On), the eNodeB checks the connection between the UE and network.
◾ If the connection is abnormal, the UE Context Release Request message contains the cause value "Radio Connection With UE Lost."
◾ If the connection is proper, the UE Context Release Request message contains the cause value "User inactivity."
• If an UE in the uplink out-of-synchronization state needs to transmit downlink data, the eNodeB instructs the UE to initiate random access to restore uplink
synchronization with the eNodeB. The UE can try the restoration for many times. If the restoration fails for the number of times specified by the
GlobalProcSwitch.UeRelReSynTimes parameter, the eNodeB releases the UE. The release is executed after a delay so that the UE has a chance to reestablish the
RRC connection with the serving cell. The delay is the sum of the value of the UeTimerConst.T310 parameter, the value of the UeTimerConst.T311 parameter, and
time margin. The time margin is specified by the CellStandardQci.TrafficRelDelay parameter and used to compensate for the difference in the time on detecting radio
link faults by the UE and eNodeB.
4 Radio Bearer Management
This chapter describes LBFD-002008 Radio Bearer Management.

Figure 4-1 shows the location of the radio bear in the E2E service in the overall service architecture.
Figure 4-1 Radio bear in the E2E service in the overall service architecture

Radio bearers are classified into signaling radio bearers (SRBs) and data radio bearers (DRBs).
• SRBs carry signaling in the control plane. There are three types of SRBs:
◾ SRB0: carries RRC signaling through a common control channel (CCCH) in transparent mode (TM) at the radio link control (RLC) layer before the RRC
connection is successfully set up.
◾ SRB1: carries RRC signaling messages after the RRC connection is successfully set up, and carries NAS messages before SRB2 is set up. SRB1 is
transmitted through a dedicated control channel (DCCH) in acknowledged mode (AM) at the RLC layer.
◾ SRB2: carries NAS signaling through a DCCH in AM mode at the RLC layer. SRB2 has a lower priority than SRB1, and SRB2 can be set up only after the
security mode is activated.
NOTE:
◾ For details about SRB0, SRB1, and SRB2, see section 6.2.2 in 3GPP TS 36.331 V9.16.0.
◾ For details about NAS, see 3GPP TS 24.301.
• DRBs carry data in the user plane. A maximum of eight DRBs can be set up between the UE and the eNodeB. The actual number depends on different QoS classes.
• In this document, radio bearer management refers to SRB2 and DRB management by the eNodeB after the security mode is set up. It involves the setup,
modification, and release of SRB2 and DRBs.
Duration radio bearer management, the UE communicates with the eNodeB using the RRC Connection Reconfiguration message. The RRC connection is reconfigured when a
radio bearer needs to be set up, modified, or released and when handover measurement information needs to be configured or modified. The application scenarios are
differentiated using different IEs in the RRC Connection Reconfiguration message.
SRB2 Setup
After encryption and integrity protection are complete during dedicated S1 connection setup, the eNodeB instructs the UE to set up SRB2 based on the value of the srb-
ToAddModList IE in the RRC Connection Reconfiguration message. Upon receiving the message, the UE performs the following operations:
• Sets up a Packet Data Convergence Protocol (PDCP) entity, and configures related security parameters.
• Sets up and configures an RLC entity.
• Sets up and configures a DCCH.
SRB2 setup uses the same procedure as dedicated S1 connection setup. For details, see 3.4 Dedicated S1 Connection Setup.
SRB2 Modification
SRB2 is modified only when the related configuration information is changed. The eNodeB sends the UE an RRC Connection Reconfiguration message containing the srb-
ToAddModList IE, instructing the UE to reconfigure the PDCP entity, RLC entity, and DCCH. Figure 4-2 shows the SRB2 modification procedure.
Figure 4-2 SRB2 modification procedure
SRB2 Release
SRB2 is released with SRB1 during signaling connection release, not in radio bearer management. For details about signaling connection release, see 3.5 Signaling Connection
Release.
DRB Setup
A DRB can be set up after encryption and integrity protection are complete and the UE context is created. DRB setup is triggered when the MME sends an E-RAB Setup
Request message to the eNodeB. Upon receiving the E-RAB Setup Request message, the eNodeB sends the UE an RRC Connection Reconfiguration message containing a
drb-ToAddModList field in the Radio Resource Config Dedicated IE. Upon receiving the message, the UE performs the following operations:
• Sets up a PDCP entity and configures related security parameters.

• Sets up and configures an RLC entity.
• Sets up and configures a DTCH.
Figure 4-3 DRB setup procedure
DRB Modification
Figure 4-4 shows the DRB modification procedure. According to the instructions in an RRC Connection Reconfiguration message, the UE reconfigures the PDCP entity, RLC
entity, and DTCH.

Figure 4-4 DRB modification procedure
DRB Release
A DRB can be released by the MME using an E-RAB Release Command message or released in a signaling connection release procedure.
When data transmission is faulty for one or more DRBs over the Uu interface, for example, the maximum number of RLC retransmissions specified by the
RLCPDCPPARAGROUP.UeMaxRetxThreshold parameter is reached, the eNodeB postpones releasing faulty DRBs based on the configured release delay timer.
When the GlobalProcSwitch.QciParaEffectFlag parameter is set to ON(On), the release delay timer for services of a specified QCI is specified by the
CellQciPara.TrafficRelDelay parameter. When the GlobalProcSwitch.QciParaEffectFlag parameter is set to OFF(Off), the lengths of the release delay timers configured for
services of standardized and extended QCIs are specified by the CellStandardQci.TrafficRelDelay and CellExtendedQci.TrafficRelDelay parameters, respectively. When a UE
runs multiple services, the minimum length of the release delay timer among all the services applies.
When an eNodeB initiates a DRB release, the eNodeB sends the EPC an E-RAB RELEASE INDICATION or UE CONTEXT RELEASE REQUEST message containing the
cause value "Radio Connection With UE Lost."
During a DRB release, the RRC Connection Reconfiguration message contains a drb-ToReleaseList field under the Radio Resource Config Dedicated IE. Based on the field
value, the UE releases all the resources related to the DRB.
Figure 4-5 DRB release procedure
5 Related Features
LBFD-002007 RRC Connection Management
erequisite Features
Feature ID Feature Name Description
LBFD-002009 Broadcast of system information None
LBFD-00201803 Cell Selection and Reselection None
None
pacted Features
None
LBFD-002008 Radio Bearer Management
erequisite Features
LBFD-002009 Broadcast of system information None
LBFD-00201803 Cell Selection and Reselection None
None
pacted Features
None

6 Network Impact
LBFD-002007 RRC Connection Management
stem Capacity
None
twork Performance
The setting of the GLOBALPROCSWITCH.RrcConnPunishThd parameter increases the RRC connection setup success rate, prolongs the network reaccess delay, and reduces
resource consumption when abnormal UEs fail to access the network repeatedly.
The RRC connection reject-triggered cell reselection function improves the RRC connection setup success rate and decreases the network access delay in big events when the
number of RRC connections in a multi-band or multi-RAT cell is far below the upper limit. This function increases the number of network access attempts when the number of
RRC connections in a multi-band or multi-RAT cell is close to the upper limit. In this situation, the RRC connection setup success rate and network access delay may decrease.
The impact on network performance increases with the number of UEs that support the deprioritisationReq IE.
stem Capacity
None
twork Performance
None
When to Use
The RRC connection reject-triggered cell reselection function is recommended in heavy-traffic scenarios.
N/A
Planning
N/A
Deployment
7.4.1 Precautions
None

The following tables list the parameters that must be set in the CellAlgoSwitch and UeTimerConst MOs to enable RRC connection reject-triggered cell reselection.
Table 7-1 Parameter in the CellAlgoSwitch MO
Deprioritisation Deliver CellAlgoSwitch.DeprioritisationDeliverInd Set this parameter to FREQUENCY(FREQUENCY). Default/recommended

Indicator value
Table 7-2 Parameter in the UeTimerConst MO
Timer 325 UeTimerConst.T325 Set this parameter to MIN5_T325(MIN5_T325). Default/recommended value


To enable RRC connection reject-triggered cell reselection, perform the following operations:
1. Run the MOD CELLALGOSWITCH command with the DeprioritisationDeliverInd parameter set to a desired value.
MOD CELLALGOSWITCH: LocalCellId=0, DeprioritisationDeliverInd=FREQUENCY;
2. Run the MOD UETIMERCONST command with the T325 parameter set to a desired value.
MOD UETIMERCONST: LocalCellId=0, T325=MIN5_T325;
1. On the U2000 client, start Uu and S1 interface tracing.

2. Power on a UE and use it to access the network.
3. View the Uu interface tracing result. If the result contains the RRC_CONN_REQ and RRC_CONN_SETUP_CMP messages, as shown in Figure 7-1, signaling
connection management has been activated.

Figure 7-1 Uu interface tracing result
4. View the S1 interface tracing result. If the result contains the S1AP_INITIAL_UE_MSG and S1AP_INITIAL_CONTEXT_SETUP_RSP messages as shown in Figure
7-2, radio bearer management has been activated.
Figure 7-2 S1 interface tracing result
7.4.4 Deactivation
Connection management is a basic function and cannot be deactivated.
N/A
RC Connection Setup Success Rate (Service)
Table 7-3 Counters
Counter ID Counter Name
1526728217 L.RRC.ConnReq.Att.Emc
1526728218 L.RRC.ConnReq.Att.HighPri
1526728219 L.RRC.ConnReq.Att.Mt
1526728221 L.RRC.ConnReq.Att.MoData
1526728222 L.RRC.ConnReq.Succ.Emc
1526728223 L.RRC.ConnReq.Succ.HighPri
1526728224 L.RRC.ConnReq.Succ.Mt
1526728226 L.RRC.ConnReq.Succ.MoData
Calculation formula: {100} x ([L.RRC.ConnReq.Succ.Emc] + [L.RRC.ConnReq.Succ.HighPri] + [L.RRC.ConnReq.Succ.Mt] + [L.RRC.ConnReq.Succ.MoData])/

([L.RRC.ConnReq.Att.Emc] + [L.RRC.ConnReq.Att.HighPri] + [L.RRC.ConnReq.Att.Mt] + [L.RRC.ConnReq.Att.MoData])
RC Connection Setup Success Rate (Signaling)
Table 7-4 Counters
1526728220 L.RRC.ConnReq.Att.MoSig
1526728225 L.RRC.ConnReq.Succ.MoSig
Calculation formula: {100} x (L.RRC.ConnReq.Succ.MoSig)/(L.RRC.ConnReq.Att.MoSig)
RAB Setup Success Rate (VoIP)
Table 7-5 Counters
1526726668 L.E-RAB.AttEst.QCI.1
1526726669 L.E-RAB.SuccEst.QCI.1
Calculation formula: {100} x (L.E-RAB.SuccEst.QCI.1)/(L.E-RAB.AttEst.QCI.1)
RAB Setup Success Rate (All Services)
Table 7-6 Counters
1526727545 L.E-RAB.AttEst
1526727544 L.E-RAB.SuccEst
Calculation formula: {100} x (L.E-RAB.SuccEst)/(L.E-RAB.AttEst)
ll Drop Rate (VoIP)
Table 7-7 Counters


1526726686 L.E-RAB.AbnormRel.QCI.1
1526726687 L.E-RAB.NormRel.QCI.1
Calculation formula: {100} x (L.E-RAB.AbnormRel.QCI.1)/(L.E-RAB.AbnormRel.QCI.1 + L.E-RAB.NormRel.QCI.1)
ll Drop Rate (All Services)
Table 7-8 Counters
1526727546 L.E-RAB.AbnormRel
1526727547 L.E-RAB.NormRel
Calculation formula: {100} x (L.E-RAB.AbnormRel)/(L.E-RAB.AbnormRel + L.E-RAB.NormRel)
N/A
Possible Issues
ult Description
The E-RAB setup success rate deteriorates significantly.
NOTE:
If the RRC setup success rate deteriorates significantly, contact Huawei for technical support.
ult Handling
1. On the U2000 client, start S1 interface tracing and obtain the tracing result.
Figure 7-3 S1 interface tracing result
2. View the tracing result to check whether there are a large number of S1AP_INITIAL_CONTEXT_SETUP_FAIL messages. If yes, proceed to the next step. If no,
contact Huawei for technical support.
Figure 7-4 S1AP_INITIAL_CONTEXT_SETUP_FAIL message
3. Double-click an S1AP_INITIAL_CONTEXT_SETUP_FAIL message to view details, and check whether the value of the Cause IE is Transport Resource
Unavailable. If yes, proceed to the next step. If no, contact Huawei for technical support.
Figure 7-5 Value of the Cause IE
4. Run the MOD GTPU command with the STATICCHK parameter set to ENABLE(Enable) to enable the GTP-U tunnel detection function.
Figure 7-6 MOD GTPU
5. Run the ADD ENODEBPATH command to add the application type of the IP path corresponding to the S1 interface. In this step, set the AppType parameter to S1
(S1).

Figure 7-7 ADD ENODEBPATH
6. Run the DSP IPPATH command to check whether the value of the IP Path Check Result parameter is Fault. If yes, adjust the IP path according to the network
plan. If no, contact Huawei for technical support.
Figure 7-8 DSP IPPATH
arm
Alarm ID Alarm Name
ALM-29215 Cell RRC Connection Success Rate Too Low
ALM-29216 Cell ERAB Setup Success Rate Too Low
ALM-29217 Cell Call Drop Rate Too High
8 Parameters
GlobalProcSwitch EnhancedRRCReestProtectThd MOD GLOBALPROCSWITCH LBFD-002007 RRC Meaning: Indicates the protection threshold
LST GLOBALPROCSWITCH Connection of the number of RRC connection
Management reestablishments initiated by the same UE in
an eNodeB above which the eNodeB
releases the UE. UE manufacturers may
have different understanding of protocols,
and therefore UE compliance with protocols
varies and may be different from eNodeB
compliance with the same protocols. Some
UEs may initiate the same RRC connection
reestablishments repeatedly. When this
parameter is set to 0, the RRC connection
reestablishment protection function is
disabled. When this parameter is set to a
non-zero value, the function is enabled. This
function releases a UE when the number of
RRC connection reestablishment procedures
initiated by the UE in an eNodeB exceeds the
threshold. If this parameter is set to a non-
zero value, the RrcReestProtectThd
parameter does not take effect.
Unit: None
Default Value: 0
GlobalProcSwitch QciParaEffectFlag MOD GLOBALPROCSWITCH None None Meaning: Indicates whether parameters in
LST GLOBALPROCSWITCH QciPara, CellQciPara, and
CnOperatorQciPara MOs take effect. The
parameters do not take effect by default. If
this parameter is set to OFF, parameters in
StandardQci, ExtendedQci, CellStandardQci,
CellExtendedQci, CnOperatorStandardQci,
and CnOperatorExtendedQci MOs take
effect and parameters in QciPara,
CellQciPara, and CnOperatorQciPara MOs
do not take effect. If this parameter is set to
ON, parameters in QciPara, CellQciPara,
and CnOperatorQciPara MOs take effect and
parameters in StandardQci, ExtendedQci,
CellStandardQci, CellExtendedQci,
CnOperatorStandardQci, and
CnOperatorExtendedQci MOs do not take
effect.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)

GlobalProcSwitch RrcReestOptSwitch MOD GLOBALPROCSWITCH None None Meaning:

LST GLOBALPROCSWITCH Indicates whether the eNodeB supports RRC
connection reestablishment in enhanced
scenarios. This parameter provides the
following options:
PCI_CONFUSION_REEST_SWITCH: This
option specifies whether the eNodeB
supports RRC connection reestablishment in
PCI confusion scenarios. The eNodeB
supports reestablishment in scenarios where
PCIs of neighboring cells are the same only if
this option is selected.
S1_HANDOVER_REEST_SWITCH: This
option specifies whether the eNodeB
supports RRC connection reestablishment in
S1-based handovers. The eNodeB supports
reestablishment in S1-based handovers only
if this option is selected.
NO_CONTEXT_REEST_SWITCH: This
option specifies whether the eNodeB uses
3GPP-defined RRC connection
reestablishment without UE context. If this
option is selected, the eNodeB uses 3GPP-
defined RRC connection reestablishment
without UE context. If this option is
deselected, the eNodeB uses common RRC
connection reestablishment without UE
context.
SEC_CMD_REEST_SWITCH: This option
specifies whether the eNodeB responds to
RRC connection reestablishment requests
from UEs when security mode is activated.
The eNodeB responds to the requests if this
option is selected and rejects the requests if
this option is deselected.
WITH_X2_NO_NCELL_REEST_SWITCH:
This option specifies whether the eNodeB
supports RRC connection reestablishment
when an X2 interface is configured between
the source and target eNodeBs but the
source and target cells are not configured as
neighboring cells of each other. This type of
RRC connection reestablishment is
supported only if this option is selected.
GUI Value Range:
PCI_CONFUSION_REEST_SWITCH
( PCI_CONFUSION_REEST_SWITCH),
S1_HANDOVER_REEST_SWITCH
(S1_HANDOVER_REEST_SWITCH),
NO_CONTEXT_REEST_SWITCH
(NO_CONTEXT_REEST_SWITCH),
SEC_CMD_REEST_SWITCH
(SEC_CMD_REEST_SWITCH),
WITH_X2_NO_NCELL_REEST_SWITCH
(WITH_X2_NO_NCELL_REEST_SWITCH)
Unit: None
Actual Value Range:
PCI_CONFUSION_REEST_SWITCH,
S1_HANDOVER_REEST_SWITCH,
NO_CONTEXT_REEST_SWITCH,
SEC_CMD_REEST_SWITCH,
WITH_X2_NO_NCELL_REEST_SWITCH
Default Value:
PCI_CONFUSION_REEST_SWITCH:Off,
S1_HANDOVER_REEST_SWITCH:Off,
NO_CONTEXT_REEST_SWITCH:Off,
SEC_CMD_REEST_SWITCH:Off,
WITH_X2_NO_NCELL_REEST_SWITCH:Off
GlobalProcSwitch RrcConnPunishThd MOD GLOBALPROCSWITCH LBFD-002007 / RRC Meaning: Indicates the threshold for an RRC
LST GLOBALPROCSWITCH TDLBFD-002007 Connection connection penalty. Certain UEs may
Management repeatedly fail to access networks because
of compatibility issues. If the number of RRC
connection setup requests that the eNodeB
receives from a UE within the time specified
by T300+FilterReptRrcConnReqTimer
exceeds the threshold (a non-zero value), the
eNodeB imposes a penalty on the UE,
rejecting RRC connection setup requests
from the UE. If this parameter is set to 0, the
penalty does not take effect.
Unit: None
Default Value: 0
CellAlgoSwitch DeprioritisationDeliverInd MOD CELLALGOSWITCH LBFD-002007 / RRC Meaning: Indicates whether the
LST CELLALGOSWITCH TDLBFD-002007 Connection RRCConnectionReject message includes the
Management IE deprioritisationReq and the setting of the
IE deprioritisationType in the message. If this
parameter is set to UNDELIVER
(UNDELIVER), the RRCConnectionReject


message does not include the IE
deprioritisationReq. If this parameter is set to
FREQUENCY(FREQUENCY), the
RRCConnectionReject message includes the
IE deprioritisationReq and the value of the IE
deprioritisationType is FREQUENCY. In this
case, after the UE receives an
RRCConnectionReject message, the lowest
cell reselection priority is configured for the
serving frequency and the frequencies
contained in the RRCConnectionReject
messages that have been received and
include the IE deprioritisationReq. If this
parameter is set to EUTRA(EUTRA), the
RRCConnectionReject message includes the
IE deprioritisationReq and the value of the IE
deprioritisationType is EUTRA. In this case,
after the UE receives an
RRCConnectionReject message, the lowest
cell reselection priority is configured for all
E-UTRAN frequencies. For details about the
IEs, see 3GPP 36.331.
GUI Value Range: UNDELIVER
(UNDELIVER), FREQUENCY
(FREQUENCY), EUTRA(EUTRA)
Unit: None
Actual Value Range: UNDELIVER,
FREQUENCY, EUTRA
Default Value: UNDELIVER(UNDELIVER)
UeTimerConst T325 MOD UETIMERCONST LBFD-002007 / RRC Meaning: Indicates the length of timer 325.
LST UETIMERCONST TDLBFD-002007 Connection For details, see 3GPP TS 36.331. This timer
Management starts when a UE receives an
RRCConnectionReject message containing
the deprioritisationReq IE. When the timer
expires, the cell reselection priorities that
have been reduced using
RRCConnectionReject for E-UTRAN
frequencies are restored.
GUI Value Range: MIN5_T325(MIN5_T325),
MIN10_T325(MIN10_T325), MIN15_T325
(MIN15_T325), MIN30_T325(MIN30_T325)
Unit: min
Actual Value Range: MIN5_T325,
MIN10_T325, MIN15_T325, MIN30_T325
Default Value: MIN5_T325(MIN5_T325)
QciPara UlSynTimerForQci ADD QCIPARA LBFD-002007 RRC Meaning: Indicates the timer used to govern
MOD QCIPARA Connection the period in which the eNodeB maintains
LST QCIPARA Management uplink synchronization for UEs that have
bearers of a QCI. After this timer expires, the
eNodeB does not send Timing Advance
Command to the UE. This parameter does
not take effect if it is set to 0. That is, the
eNodeB will constantly send Timing Advance
Command to the UE to maintain uplink
synchronization for the UE. If a UE has
bearers of several QCIs, the eNodeB selects
the longest uplink synchronization timer of
bearers with the highest QCI-specific priority
specified by the UeInactiveTimerPri
parameter as the uplink synchronization
timer for the UE.
Unit: s
Default Value: 180
QciPara UeInactivityTimerDynDrxQci ADD QCIPARA LBFD-002007 RRC Meaning: Indicates the length of the UE
MOD QCIPARA Connection inactivity timer for UEs that have entered
LST QCIPARA Management DRX mode and have bearers of the QCI
when dynamic DRX is enabled. If the
eNodeB detects that a UE has neither
received nor sent data for a period exceeding
the value of this parameter, the eNodeB
releases the RRC connection for this UE. If
this parameter is set to a large value, the
amount of signaling is reduced but UE power
consumption increases. You are advised to
set this parameter to a value greater than
that of UlSynTimerDynDrx. In power saving
mode, you are advised to set this parameter
significantly different to the value of the
UlSynTimerDynDrx parameter, for example a
gap of 10 seconds, to avoid power
consumption increase due to the increase of
signaling. If a UE has bearers of several
QCIs, the eNodeB selects the longest UE
Inactivity Timer of bearers with the highest
QCI-specific priority specified by the
UeInactiveTimerPri parameter as the UE
inactivity timer for the UE.


Unit: None
Default Value: 200
QciPara UeInactiveTimerForQci ADD QCIPARA LBFD-002007 RRC Meaning: Indicates the length of the UE
MOD QCIPARA Connection inactivity timer for UEs that have bearers of a
LST QCIPARA Management QCI. If the eNodeB detects that a UE has
neither received nor sent data for a period
exceeding the value of this parameter, the
eNodeB releases the RRC connection for
this UE. If this parameter is set to 0, the UE
inactivity timer is not used. This parameter
takes effect only for UEs that will access the
network after the parameter is set. If a UE
has bearers of several QCIs, the eNodeB
selects the longest UE Inactivity Timer of
bearers with the highest QCI-specific priority
specified by the UeInactiveTimerPri
parameter as the UE inactivity timer for the
UE.
Unit: None
Default Value: 20
QciPara UeInactiveTimerPri ADD QCIPARA LBFD-002007 RRC Meaning: Indicates the priority for the QCI-
MOD QCIPARA Connection specific UE Inactivity Timer. A larger value of
LST QCIPARA Management this parameter indicates a higher priority. The
eNodeB selects the longest UE Inactivity
Timer with the highest QCI-specific priority as
the UE Inactivity Timer for UEs running
services with the specific QCI. The UE
Inactivity Timer for QCI 69 is taken as the UE
Inactivity Timer for the MCPTT UEs.
Unit: None
Default Value: 0
RrcConnStateTimer FilterReptRrcConnReqTimer MOD LBFD-002007 / RRC Meaning: Indicates the length of the timer for
RRCCONNSTATETIMER TDLBFD-002007 Connection the eNodeB to filter repeated RRC
LST Management Connection Request messages. The actually
RRCCONNSTATETIMER
used timer length is the sum of T300 length
and the value of this parameter.
Unit: s
Default Value: 2
UeTimerConst T300 MOD UETIMERCONST LBFD-002009 / Broadcast of Meaning:

LST UETIMERCONST TDLBFD-002009 system Indicates the timer value of Timer 300. For
information details, see 3GPP TS 36.331.
This timer is started when the UE sends
RRCConnectionRequest.
Before the timer expires, it is stopped if the
UE receives RRCConnectionSetup or
RRCConnectionReject.
After the timer expires, the UE enters the
RRC_IDLE state.
GUI Value Range: MS100_T300(100ms),
MS200_T300(200ms), MS300_T300
(300ms), MS400_T300(400ms),
MS600_T300(600ms), MS1000_T300
(1000ms), MS1500_T300(1500ms),
MS2000_T300(2000ms)
Unit: ms
Actual Value Range: MS100_T300,
MS200_T300, MS300_T300, MS400_T300,
MS600_T300, MS1000_T300,
MS1500_T300, MS2000_T300
Default Value: MS1000_T300(1000ms)
RrcConnStateTimer T302 MOD LBFD-002007 / RRC Meaning:

RRCCONNSTATETIMER TDLBFD-002007 Connection Indicates the length of timer T302.
LST Management T302 specifies the time during which a UE
RRCCONNSTATETIMER
whose RRC connection request is rejected
has to wait before the UE can initiate a
request again.
This timer is started when the UE receives an
RRCConnectionReject message and
stopped when the UE enters the
RRC_CONNECTED mode or performs cell
reselection.
Unit: s
Default Value: 16
ENodeBConnStateTimer WaitRrcConnSetupCmpTimer MOD None None

ENODEBCONNSTATETIMER


LST Meaning: Indicates the timer for the eNodeB
ENODEBCONNSTATETIMER to wait for a RRC Connection Setup
Complete.
Unit: s
Default Value: 15
ENodeBConnStateTimer UuMessageWaitingTimer MOD None None Meaning: Indicates the timer governing the
ENODEBCONNSTATETIMER period the eNodeB waits for a response
LST message from a UE when the UE is running
non-QCI1 services. If the timer expires, the
eNodeB initiates a UE context release over
the S1 interface.
Unit: s
Default Value: 35
ENodeBConnStateTimer UuMessageWaitingTimerQci1 MOD LBFD-002007 / RRC Meaning: Indicates the timer governing the
ENODEBCONNSTATETIMER TDLBFD-002007 Connection period the eNodeB waits for a response
LST Management message from a UE when the UE is running
services with the QCI of 1. If the timer
expires, the eNodeB initiates a UE context
release over the S1 interface.
Unit: s
Default Value: 35

LST UETIMERCONST TDLBFD-002009 system Indicates the length of timer 310. For details,
information see 3GPP TS 36.331.
This timer is started when the UE detects any
fault at the physical layer.
The timer is stopped if the UE detects one of
the following before the timer expires: (1) The
physical-layer fault is rectified; (2) A
handover is triggered; (3) The UE initiates an
RRC connection reestablishment procedure.
RRC_IDLE mode if the security mode is not
activated. If the security mode is activated,
the UE initiates an RRC connection
reestablishment procedure.
MS50_T310(50ms), MS100_T310(100ms),
MS200_T310(200ms), MS500_T310
(500ms), MS1000_T310(1000ms),
MS2000_T310(2000ms)
Unit: ms
MS50_T310, MS100_T310, MS200_T310,
MS500_T310, MS1000_T310,
MS2000_T310

This timer is started when the UE sends an
RRC Connection Reestablishment Request
message.
The timer is stopped if, before it expires, the
UE receives an RRC Connection
Reestablishment or RRC Connection
Reestablishment Reject message. The timer
is also stopped if the selected cell becomes
an unsuitable cell. For the definition of a
suitable cell, see 3GPP TS 36.331.
RRC_IDLE mode.
MS200_T301(200ms), MS300_T301
(300ms), MS400_T301(400ms),
MS600_T301(600ms), MS1000_T301
(1000ms), MS1500_T301(1500ms),
MS2000_T301(2000ms)
Unit: ms
MS200_T301, MS300_T301, MS400_T301,
MS600_T301, MS1000_T301,
MS1500_T301, MS2000_T301
RrcConnStateTimer T304ForEutran MOD None None Meaning: Indicates the length of timer T304
RRCCONNSTATETIMER for intra-RAT handover. If the UE does not
LST complete the handover before this timer
RRCCONNSTATETIMER
expires, the UE reverts back to the


associated configuration and initiates an
GUI Value Range: ms50(50), ms100(100),
ms150(150), ms200(200), ms500(500),
ms1000(1000), ms2000(2000)
Unit: ms
Actual Value Range: ms50, ms100, ms150,
ms200, ms500, ms1000, ms2000
Default Value: ms500(500)
RrcConnStateTimer T304ForGeran MOD None None Meaning: Indicates the length of timer T304
RRCCONNSTATETIMER for inter-RAT handover to GERAN. If the UE
LST does not complete the handover before this
RRCCONNSTATETIMER
timer expires, the UE reverts back to the
associated configuration and initiates an
RRC connection re-establishment procedure.
GUI Value Range: ms100(100), ms200(200),
ms500(500), ms1000(1000), ms2000(2000),
ms4000(4000), ms8000(8000)
Unit: ms
ms1000, ms2000, ms4000, ms8000
Default Value: ms8000(8000)

This timer is started when the UE starts the
The timer is stopped if, before the timer
expires, the UE selects an E-UTRAN or inter-
RAT cell to camp on.
RRC_IDLE mode.
MS3000_T311(3000ms), MS5000_T311
(5000ms), MS10000_T311(10000ms),
MS15000_T311(15000ms), MS20000_T311
(20000ms), MS30000_T311(30000ms)
Unit: ms
MS3000_T311, MS5000_T311,
MS10000_T311, MS15000_T311,
MS20000_T311, MS30000_T311
RlcPdcpParaGroup UeMaxRetxThreshold ADD LBFD-002008 / Radio Bearer Meaning: Indicates the UE-specific maximum
RLCPDCPPARAGROUP TDLBFD-002008 Management number of RLC ARQ retransmissions,
MOD namely the maximum number of AM PDU
RLCPDCPPARAGROUP
retransmissions. When the number of
LST RLCPDCPPARAGROUP
retransmissions reaches the value of this
parameter, RRC connection re-establishment
is initiated.
GUI Value Range: Maxretx_Threshold_t1(1),
Maxretx_Threshold_t2(2),
Maxretx_Threshold_t32(32)
Unit: None
Actual Value Range: Maxretx_Threshold_t1,
Maxretx_Threshold_t2,
Maxretx_Threshold_t32
Default Value: Maxretx_Threshold_t32(32)
UeTimerConst N310 MOD UETIMERCONST LBFD-002009 / Broadcast of Meaning: Indicates the maximum number of
LST UETIMERCONST TDLBFD-002009 system successive "out of sync" indications received
information from L1. For details, see 3GPP TS 36.331.
GUI Value Range: n1(1), n2(2), n3(3), n4(4),
n6(6), n8(8), n10(10), n20(20)
Unit: None
Actual Value Range: n1, n2, n3, n4, n6, n8,
n10, n20
Default Value: n10(10)
UeTimerConst N311 MOD UETIMERCONST LBFD-002009 / Broadcast of Meaning: Indicates the maximum number of
LST UETIMERCONST TDLBFD-002009 system successive "in sync" indications received
information from L1. For details, see 3GPP TS 36.331.
GUI Value Range: n1(1), n2(2), n3(3), n4(4),
n5(5), n6(6), n8(8), n10(10)
Unit: None
Actual Value Range: n1, n2, n3, n4, n5, n6,
n8, n10


Default Value: n1(1)
GlobalProcSwitch RrcReestProtectThd MOD GLOBALPROCSWITCH None None Meaning: Indicates the RRC connection
LST GLOBALPROCSWITCH reestablishment protection threshold. UE
manufacturers may have different
understanding of protocols, and therefore UE
compliance with protocols varies and may be
different from eNodeB compliance with the
same protocols. After a UE initiates an RRC
connection reestablishment procedure due to
reconfigurationFailure and the
reestablishment is complete, the subsequent
RRC connection reconfiguration may fail
again. As a result, the UE initiates an RRC
connection reestablishment procedure again.
If this repeatedly happens, the UE repeatedly
initiates RRC connection reestablishment. If
this parameter is set to 0, the function of
RRC connection reestablishment protection
is not used. If this parameter is set to a value
other than 0, the eNodeB rejects the RRC
connection reestablishment request due to
reconfigurationFailure from a UE when the
number of RRC connection reestablishment
requests initiated by the UE served by the
eNodeB due to reconfigurationFailure has
exceeded the parameter value within 1
minute.
Unit: None
Default Value: 0
TimeAlignmentTimer TimeAlignmentTimer MOD TATIMER None None Meaning: Indicates the length of the uplink
LST TATIMER time alignment timer for UEs in the cell. A UE
is considered not time-aligned in the uplink if
the timer expires.
GUI Value Range: SF500(500 subframes),
SF750(750 subframes), SF1280(1280
subframes), SF1920(1920 subframes),
SF2560(2560 subframes), SF5120(5120
subframes), SF10240(10240 subframes),
INFINITY(Infinity)
Unit: None
Actual Value Range: SF500, SF750,
SF1280, SF1920, SF2560, SF5120,
SF10240, INFINITY
Default Value: INFINITY(Infinity)
RrcConnStateTimer UlSynTimer MOD LBFD-002007 / RRC Meaning: Indicates the timer used to govern
RRCCONNSTATETIMER TDLBFD-002007 Connection the period in which the eNodeB maintains
LST Management uplink synchronization for UEs. After this
RRCCONNSTATETIMER
timer expires, the eNodeB does not send
Timing Advance Command to the UE. This
parameter does not take effect if it is set to 0.
That is, the eNodeB will constantly send
Timing Advance Command to the UE to
maintain uplink synchronization for the UE. If
the QciParaEffectFlag parameter is set to ON
(ON), this parameter does not take effect but
the UlSynTimerForQci parameter in the
QciPara MO takes effect.
Unit: s
Default Value: 180
CellAlgoSwitch DynDrxSwitch MOD CELLALGOSWITCH LBFD- DRX Meaning: Indicates whether to enable
LST CELLALGOSWITCH 002017/TDLBFD- Dynamic dynamic discontinuous reception (DRX) or
002017 DRX smart DRX. Unlink dynamic DRX and smart
LOFD- Smart DRX DRX apply only to LTE TDD cells and
00110501/TDLOFD- requires the mobility speed of UEs to be
00110501 reported. DynDrxSwitch: If this switch is on,
TDLBFD-070112 dynamic DRX applies to newly admitted UEs
to reduce signaling overheads or decrease
UE power consumption. If this switch is off,
dynamic DRX does not apply to newly
admitted UEs. Dynamic DRX applies to
carrier aggregation (CA) UEs only when this
switch is on in both the primary serving cell
(PCell) and secondary serving cell (SCell).
SmartDrxSwitch: If this switch is on, smart
DRX applies to newly admitted UEs that
support mobility speed reporting. The
eNodeB dynamically sets DRX-related
parameters based on UE mobility speeds. If
this switch is off, smart DRX does not apply
to newly admitted UEs. Smart DRX applies to
CA UEs only when this switch is on in both
the PCell and SCell. If DynDrxSwitch is on,
setting the DrxAlgSwitch parameter to ON
cannot ensure that DRX is enabled on
synchronized UEs.


GUI Value Range: DynDrxSwitch
(DynDrxSwitch), SmartDrxSwitch
(SmartDrxSwitch)
Unit: None
Actual Value Range: DynDrxSwitch,
SmartDrxSwitch
Default Value: DynDrxSwitch:Off,
SmartDrxSwitch:Off
CellAlgoSwitch UEInactiveTimerQCI1Switch MOD CELLALGOSWITCH LOFD-081229 / Voice Meaning: Indicates whether the
LST CELLALGOSWITCH TDLOFD-081229 Characteristic UeInactiveTimerQci1 parameter takes effect.
Awareness If UEInactiveTimerQCI1Switch is on,
Scheduling UeInactiveTimerQci1 takes effect; when
there are QCI 1 services, the UE inactivity
timer length is specified by
UeInactiveTimerQci1. If
UEInactiveTimerQCI1Switch is off,
UeInactiveTimerQci1 does not take effect
and the UE inactivity timer length is specified
by UeInactiveTimer.
Unit: None
RrcConnStateTimer UeInactTimerDynDrxQci1 MOD LBFD- RRC Meaning: Indicates the length of the UE
RRCCONNSTATETIMER 002007/TDLBFD- Connection inactivity timer for UEs that enter the DRX
LST 002007 Management state and perform services with a QCI of 1
RRCCONNSTATETIMER
when dynamic DRX is enabled. If the
eNodeB detects that such a UE has
consecutively neither received or sent data
for a duration longer than the timer, the
eNodeB releases the UE. This parameter
takes effect only for UEs that access the
network after the parameter is set. If the
QciParaEffectFlag parameter is set to ON
the UeInactivityTimerDynDrxQci parameter
for QCI 1 in the QciPara MO takes effect.
Unit: s
Default Value: 200
RrcConnStateTimer UeInactiveTimerQci1 MOD LBFD-002007 / RRC Meaning: Indicates the length of the UE
RRCCONNSTATETIMER TDLBFD-002007 Connection inactivity timer for UEs that have bearers of
LST Management QCI 1. If the eNodeB detects that a UE has
RRCCONNSTATETIMER
neither received nor sent data for a duration
eNodeB releases the RRC connection for the
UE. If this parameter is set to 0, the UE
inactivity timer is not used. This timer takes
effect during the setup of bearers with a QCI
of 1. During a handover or RRC connection
reestablishment to a new cell, the eNodeB
determines whether the timer takes effect
based on whether the UE has bearers with a
QCI of 1. If yes, the timer takes effect;
otherwise, the timer does not take effect. If
the QciParaEffectFlag parameter is set to ON
the UeInactiveTimerForQci parameter for
QCI 1 in the QciPara MO takes effect.
Unit: s
Default Value: 20
RrcConnStateTimer UeInactiveTimer MOD LBFD-002007 / RRC Meaning: Indicates the length of the UE
RRCCONNSTATETIMER TDLBFD-002007 Connection inactivity timer for UEs that have no QCI 1
LST Management bearers. If the eNodeB detects that a UE has
RRCCONNSTATETIMER
neither received nor sent data for a period
eNodeB releases the RRC connection for
this UE. If this parameter is set to 0, the UE
inactivity timer is not used. This parameter
takes effect only for UEs that will access the
network after the parameter is set. If the
QciParaEffectFlag parameter is set to ON
the UeInactiveTimerForQci parameter in the
Unit: s
Default Value: 20
RrcConnStateTimer UeInactivityTimerDynDrx MOD LOFD-00110501 / Dynamic Meaning: Indicates the length of the UE
RRCCONNSTATETIMER TDLOFD-00110501 DRX inactivity timer for UEs that have entered
LST DRX mode and have no QCI 1 bearers when
RRCCONNSTATETIMER LOFD-00110502 / High-Mobility-
TDLOFD-00110502 Triggered dynamic DRX is enabled. If the eNodeB
Idle Mode detects that a UE has neither received nor


sent data for a period exceeding the value of
this parameter, the eNodeB releases the
RRC connection for this UE. If this parameter
is set to a large value, the amount of
signaling is reduced but UE power
consumption increases. You are advised to
set this parameter to a value greater than
that of UlSynTimerDynDrx. In power saving
mode, you are advised to set this parameter
significantly different to the value of the
UlSynTimerDynDrx parameter, for example a
gap of 10 seconds, to avoid power
consumption increase due to the increase of
signaling. If the QciParaEffectFlag parameter
is set to ON(ON), this parameter does not
take effect but the
UeInactivityTimerDynDrxQci parameter in the
Unit: s
Default Value: 200
GlobalProcSwitch UeLinkAbnormalDetectSwitch MOD GLOBALPROCSWITCH LBFD-002007 / RRC Meaning: Indicates the UE link fault detection
LST GLOBALPROCSWITCH TDLBFD-002007 Connection switch. If this switch is turned on, link fault
Management detection is enabled for synchronized UEs. If
this switch is turned off, link fault detection is
not enabled for synchronized UEs.
Unit: None
ENodeBConnStateTimer S1MessageWaitingTimer MOD None None Meaning: Indicates the timer governing the
ENODEBCONNSTATETIMER period that the eNodeB waits for a response
LST message from the MME when the eNodeB
performs an S1-based handover for a UE
running non-QCI1 services. If the timer
expires, the eNodeB initiates a UE context
release over the S1 interface. If the eNodeB
performs an S1-based handover for a UE
running services with a QCI of 1, the
S1MsgWaitingTimerQci1 parameter controls
the period that the eNodeB waits for a
response message from the MME.
Unit: s
Default Value: 20
ENodeBConnStateTimer S1MsgWaitingTimerQci1 MOD LBFD-002007 / RRC Meaning: Indicates the timer governing the
ENODEBCONNSTATETIMER TDLBFD-002007 Connection period that the eNodeB waits for a response
LST Management message from the MME when the UE are
running services with the QCI of 1. If the
timer expires, the eNodeB initiates a UE
context release over the S1 interface.
Unit: s
Default Value: 20
ENodeBAlgoSwitch HighLoadNetOptSwitch MOD LOFD-001019 / PS Inter-RAT Meaning: Indicates whether to enable

ENODEBALGOSWITCH TDLOFD-001019 Mobility network performance optimization when the
LST ENODEBALGOSWITCH between network is heavily loaded. This parameter
LOFD-001020 /
TDLOFD-001020 E-UTRAN consists of the following options:
LOFD-001043 / and UTRAN SPECSIGRETRANSOPTSWITCH: Indicates
TDLOFD-001043 PS Inter-RAT whether to optimize special signaling
Mobility retransmission. If this option is selected, the
LOFD-001046 /
between eNodeB adaptively configures the maximum
TDLOFD-001046
E-UTRAN number of special signaling retransmissions
LOFD-001072 / that can be initiated by the RLC layer based
and GERAN
TDLOFD-001072 on the number of UEs in the cell. If this
Service
LOFD-001073 / option is deselected, the eNodeB does not.
based Inter-
TDLOFD-001073 FlowCtrlTriBackoffSwitch: Indicates whether
RAT
LOFD-001078 handover to to enable flow-control-triggered backoff.
UTRAN Consider that the network is heavily loaded
and Msg3 flow control starts. If this option is
Service
selected, flow-control-triggered backoff is
based Inter-
enabled, and UEs that fail random accesses
RAT
are postponed to reinitiate random access
handover to
requests, thereby relieving RACH
GERAN
congestion. If this option is deselected, flow-
Distance control-triggered backoff is disabled. During
based Inter- random access procedures, if flow-control-
RAT triggered backoff is required and the lengths
handover to of timers T300 and T301 are too short, the
UTRAN number of initiated access requests
Distance decreases and the access success rate
based Inter- decreases. Therefore, if this option is
RAT selected, 2000 ms is recommended for the
handover to timers T300 and T301.
GERAN FlowCtrlForwardSwitch: Indicates whether to


E-UTRAN to perform flow control at the initial stage of a
UTRAN signaling procedure. If this option is selected,
CS/PS when Msg3 flow control starts, the Msg1 flow
Steering control threshold is set to a smaller value to
reduce the number of UEs' random access
requests, reducing system load.
FlowCtrlBaseOnUuRsrSwitch: Indicates
whether to enable the flow control based on
air interface resources. If this option is
selected, cell-level MSG3 flow control is
triggered to reduce the CCE resource
consumption for signaling transmission when
CCE resources for signaling transmission are
insufficient in a cell with subframe
configuration 2.This option applies only to
LTE TDD networks.
GUI Value Range:
SPECSIGRETRANSOPTSWITCH
(SPECSIGRETRANSOPTSWITCH),
FlowCtrlTriBackoffSwitch
(FlowCtrlTriBackoffSwitch),
FlowCtrlForwardSwitch
(FlowCtrlForwardSwitch),
FlowCtrlBaseOnUuRsrSwitch
(FlowCtrlBaseOnUuRsrSwitch)
Unit: None
Actual Value Range:
SPECSIGRETRANSOPTSWITCH,
FlowCtrlTriBackoffSwitch,
FlowCtrlForwardSwitch,
FlowCtrlBaseOnUuRsrSwitch
Default Value:
SPECSIGRETRANSOPTSWITCH:On,
FlowCtrlTriBackoffSwitch:Off,
FlowCtrlForwardSwitch:Off,
FlowCtrlBaseOnUuRsrSwitch:Off
GlobalProcSwitch UeRelChkLostSwitch MOD GLOBALPROCSWITCH LBFD-002007 / RRC Meaning: Indicates whether to perform the
LST GLOBALPROCSWITCH TDLBFD-002007 Connection radio link failure (RLF) detection for a UE
Management when the RRC connection for the UE is
released because of UE inactivity.
Unit: None
GlobalProcSwitch UeRelReSynTimes MOD GLOBALPROCSWITCH LBFD-002007 / RRC Meaning: Indicates after which times of
LST GLOBALPROCSWITCH TDLBFD-002007 Connection resynchronization failures the UE release
Management timer is started in scenarios where the RRC
connection is released for a UE caused by
resynchronization failure.
GUI Value Range: r1(1), r2(2), r3(3), r4(4), r5
(5), Infinity(Infinity)
Unit: None
Actual Value Range: r1, r2, r3, r4, r5, Infinity
Default Value: Infinity(Infinity)
CellStandardQci TrafficRelDelay MOD CELLSTANDARDQCI LBFD-002008 / Radio Bearer Meaning: Indicates the waiting duration for
LST CELLSTANDARDQCI TDLBFD-002008 Management the eNodeB to release services with a
specific QCI after the eNodeB detects that
the radio link is abnormal. When the eNodeB
detects that the radio link is abnormal, the
eNodeB waits for the UE to initiate an RRC
connection reestablishment procedure to
restore services. If the waiting duration times
out, the eNodeB releases the services.
Unit: ms
CellQciPara TrafficRelDelay ADD CELLQCIPARA LBFD-002008 / Radio Bearer Meaning: Indicates the waiting duration for
MOD CELLQCIPARA TDLBFD-002008 Management the eNodeB to release services with a
LST CELLQCIPARA specific QCI after the eNodeB detects that
Unit: ms
CellExtendedQci TrafficRelDelay ADD CELLEXTENDEDQCI LBFD-002008 / Radio Bearer Meaning: Indicates the waiting duration for
MOD CELLEXTENDEDQCI TDLBFD-002008 Management the eNodeB to release services with a
LST CELLEXTENDEDQCI specific QCI after the eNodeB detects that


Unit: ms
9 Counters
Table 9-1 Counters
Counter ID Counter Name Counter Description Feature ID Feature Name
1526726657 L.RRC.ConnReq.Msg Number of RRC Multi-mode: None RRC Connection

connection setup requests GSM: None Management
(retransmission included) UMTS: None RRC Connection
LTE: LBFD-002007 Management
TDLBFD-002007
1526726658 L.RRC.ConnReq.Att Number of RRC Multi-mode: None RRC Connection

(retransmission excluded) UMTS: None RRC Connection
TDLBFD-002007
1526726659 L.RRC.ConnReq.Succ Number of RRC Multi-mode: None RRC Connection

connection setup GSM: None Management
completion times UMTS: None RRC Connection
TDLBFD-002007
1526726668 L.E-RAB.AttEst.QCI.1 Number of E-RAB setup Multi-mode: None Radio Bearer Management
attempts initiated by UEs GSM: None Radio Bearer Management
for services with the QCI of UMTS: None
1 in a cell
LTE: LBFD-002008
TDLBFD-002008
1526726669 L.E-RAB.SuccEst.QCI.1 Number of successful Multi-mode: None Radio Bearer Management

E-RAB setups initiated by GSM: None Radio Bearer Management
UEs for services with the UMTS: None
QCI of 1 in a cell
LTE: LBFD-002008
TDLBFD-002008
2 in a cell
LTE: LBFD-002008
TDLBFD-002008

QCI of 2 in a cell
LTE: LBFD-002008
TDLBFD-002008
3 in a cell
LTE: LBFD-002008
TDLBFD-002008

QCI of 3 in a cell
LTE: LBFD-002008
TDLBFD-002008
4 in a cell
LTE: LBFD-002008
TDLBFD-002008

QCI of 4 in a cell
LTE: LBFD-002008
TDLBFD-002008


5 in a cell LTE: LBFD-002008
TDLBFD-002008

QCI of 5 in a cell
LTE: LBFD-002008
TDLBFD-002008
6 in a cell
LTE: LBFD-002008
TDLBFD-002008

QCI of 6 in a cell
LTE: LBFD-002008
TDLBFD-002008
7 in a cell
LTE: LBFD-002008
TDLBFD-002008

QCI of 7 in a cell
LTE: LBFD-002008
TDLBFD-002008
8 in a cell
LTE: LBFD-002008
TDLBFD-002008

QCI of 8 in a cell
LTE: LBFD-002008
TDLBFD-002008
9 in a cell
LTE: LBFD-002008
TDLBFD-002008

QCI of 9 in a cell
LTE: LBFD-002008
TDLBFD-002008
1526726686 L.E-RAB.AbnormRel.QCI.1 Number of abnormal Multi-mode: None Radio Bearer Management

releases of activated GSM: None Radio Bearer Management
E-RABs for services with UMTS: None
the QCI of 1 in a cell
LTE: LBFD-002008
TDLBFD-002008
1526726687 L.E-RAB.NormRel.QCI.1 Number of normal E-RAB Multi-mode: None Radio Bearer Management
releases for services with GSM: None Radio Bearer Management
the QCI of 1 in a cell UMTS: None
LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008


TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
1526726717 L.E-RAB.FailEst.NoReply Number of E-RAB setup Multi-mode: None Radio Bearer Management
failures due to no GSM: None Radio Bearer Management
responses from the UE in a UMTS: None
cell
LTE: LBFD-002008
TDLBFD-002008
1526726767 L.Traffic.DRB.QCI.1 Multi-mode: None Radio Bearer Management


Number of DRBs for GSM: None Radio Bearer Management
services with the QCI of 1 UMTS: None
in a cell LTE: LBFD-002008
TDLBFD-002008
1526726768 L.Traffic.DRB.QCI.2 Number of DRBs for Multi-mode: None Radio Bearer Management
services with the QCI of 2 GSM: None Radio Bearer Management
in a cell UMTS: None
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
1526726776 L.Thrp.bits.UL.QCI.1 Uplink traffic volume for Multi-mode: None Radio Bearer Management
PDCP PDUs of services GSM: None Radio Bearer Management
with the QCI of 1 in a cell UMTS: None Basic Scheduling
LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526726777 L.Thrp.Time.UL.QCI.1 Receive duration of uplink Multi-mode: None Radio Bearer Management
PDCP PDUs for services GSM: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526726782 L.Thrp.bits.UL.QCI.3 Multi-mode: None Radio Bearer Management


Uplink traffic volume for GSM: None Radio Bearer Management
PDCP PDUs of services UMTS: None Basic Scheduling
with the QCI of 3 in a cell LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025


TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526726803 L.Thrp.bits.DL.QCI.1 Downlink traffic volume for Multi-mode: None Radio Bearer Management
PDCP SDUs of services GSM: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526726804 L.Thrp.Time.DL.QCI.1 Transmit duration of Multi-mode: None Radio Bearer Management

downlink PDCP SDUs for GSM: None Radio Bearer Management
services with the QCI of 1 UMTS: None Basic Scheduling
in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025

in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025

in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025

in a cell


TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025

in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025

in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025

in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025

in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025

in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025


1526726833 L.PDCP.Tx.Disc.Trf.SDU.QCI.1 Number of downlink PDCP Multi-mode: None Radio Bearer Management
SDUs discarded for GSM: None Radio Bearer Management
services carried on DRBs UMTS: None Basic Scheduling
with a QCI of 1 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526727045 L.Thrp.bits.UL.QCI.1.Max Maximum uplink traffic Multi-mode: None Radio Bearer Management
volume for PDCP PDUs of GSM: None Radio Bearer Management
in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
in a cell
TDLBFD-002008


LBFD-002025
TDLBFD-002025
in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526727054 L.Thrp.bits.UL.Max Maximum uplink traffic Multi-mode: None Radio Bearer Management
all services UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526727055 L.Thrp.bits.DL.QCI.1.Max Maximum downlink traffic Multi-mode: None Radio Bearer Management
volume for PDCP SDUs of GSM: None Radio Bearer Management
in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025


in a cell LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526727064 L.Thrp.bits.DL.Max Maximum downlink traffic Multi-mode: None Radio Bearer Management
all services UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526727083 L.RRC.SetupFail.ResFail Number of RRC Multi-mode: None RRC Connection

connection setup failures GSM: None Management
due to resource allocation UMTS: None RRC Connection
failures Management
LTE: LBFD-002007
TDLBFD-002007
1526727084 L.RRC.SetupFail.NoReply Number of RRC Multi-mode: None RRC Connection

due to no responses from UMTS: None RRC Connection
the UE Management
LTE: LBFD-002007
TDLBFD-002007
1526727085 L.RRC.ReEst.Att Number of RRC Multi-mode: None RRC Connection

connection reestablishment GSM: None Management
requests UMTS: None RRC Connection
TDLBFD-002007
1526727086 L.RRC.ReEst.Succ Number of successful RRC Multi-mode: None RRC Connection

connection GSM: None Management
reestablishments UMTS: None RRC Connection
TDLBFD-002007


1526727087 L.RRC.ReEst.ReconfFail.Att Number of RRC Multi-mode: None RRC Connection
requests triggered by UMTS: None RRC Connection
reconfiguration failures Management
LTE: LBFD-002007
TDLBFD-002007
1526727088 L.RRC.ReEst.ReconfFail.Succ Number of successful RRC Multi-mode: None RRC Connection

reestablishments triggered UMTS: None RRC Connection
by reconfiguration failures Management
LTE: LBFD-002007
TDLBFD-002007
1526727089 L.RRC.ReEst.ReconfFail.Rej Number of rejected RRC Multi-mode: None RRC Connection

attempts triggered by UMTS: None RRC Connection
reconfiguration failures Management
LTE: LBFD-002007
TDLBFD-002007
1526727090 L.RRC.ReEst.HoFail.Att Number of RRC Multi-mode: None RRC Connection

requests triggered by failed UMTS: None RRC Connection
handovers Management
LTE: LBFD-002007
TDLBFD-002007
1526727091 L.RRC.ReEst.HoFail.Succ Number of successful RRC Multi-mode: None RRC Connection

reestablishments triggered UMTS: None RRC Connection
by failed handovers Management
LTE: LBFD-002007
TDLBFD-002007
1526727092 L.RRC.ReEst.HoFail.Rej Number of rejected RRC Multi-mode: None RRC Connection

attempts triggered by UMTS: None RRC Connection
handover failures Management
LTE: LBFD-002007
TDLBFD-002007
1526727093 L.RRC.ReEstFail.ResFail Number of RRC Multi-mode: None RRC Connection

failures due to failed UMTS: None RRC Connection
resource allocations Management
LTE: LBFD-002007
TDLBFD-002007
1526727094 L.RRC.ReEstFail.NoReply Number of RRC Multi-mode: None RRC Connection

failures due to no UMTS: None RRC Connection
responses from the UE Management
LTE: LBFD-002007
TDLBFD-002007
1526727188 L.Sig.S1.SendSetup.Att Number of S1 link setup Multi-mode: None Radio Bearer Management
attempts at the eNodeB GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526727189 L.Sig.S1.SendSetup.Succ Number of successful S1 Multi-mode: None Radio Bearer Management

link setups at the eNodeB GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526727378 L.Traffic.User.Avg Average number of users Multi-mode: None RRC Connection

in a cell GSM: None Management
UMTS: None RRC Connection
TDLBFD-002007
1526727379 L.Traffic.User.Max Maximum number of users Multi-mode: None RRC Connection

in a cell GSM: None Management
TDLBFD-002007
1526727380 L.Traffic.CEU.Avg Average number of Multi-mode: None RRC Connection

downlink cell edge users GSM: None Management
(CEUs) in a cell UMTS: None RRC Connection
TDLBFD-002007 Downlink Static Inter-Cell
Interference Coordination
TDLBFD-00202201
Adaptive Inter-Cell
LOFD-060201
TDLOFD-060201
Adaptive Inter-Cell
1526727381 L.Traffic.CEU.Max Maximum number of Multi-mode: None RRC Connection

downlink cell edge users GSM: None Management
(CEUs) in a cell UMTS: None RRC Connection


TDLBFD-002007 Downlink Static Inter-Cell
TDLBFD-00202201 Interference Coordination
LOFD-060201 Adaptive Inter-Cell
TDLOFD-060201 Interference Coordination
Adaptive Inter-Cell
1526727382 L.Traffic.User.ULData.Avg Average number of UEs Multi-mode: None RRC Connection

with data in the uplink GSM: None Management
buffer UMTS: None RRC Connection
TDLBFD-002007
1526727383 L.Traffic.User.ULData.Max Maximum number of UEs Multi-mode: None RRC Connection

with data in the uplink GSM: None Management
TDLBFD-002007
1526727384 L.Traffic.User.DLData.Avg Average number of UEs Multi-mode: None RRC Connection

with data in the downlink GSM: None Management
TDLBFD-002007
1526727385 L.Traffic.User.DLData.Max Maximum number of UEs Multi-mode: None RRC Connection

with data in the downlink GSM: None Management
TDLBFD-002007
1526727513 L.E-RAB.AttModify.QCI.1 Number of E-RAB Multi-mode: None Radio Bearer Management

modification attempts GSM: None Radio Bearer Management
initiated by UEs for UMTS: None
services with the QCI of 1
LTE: LBFD-002008
in a cell
TDLBFD-002008
1526727514 L.E-RAB.SuccModify.QCI.1 Number of successful Multi-mode: None Radio Bearer Management

E-RAB modifications GSM: None Radio Bearer Management
LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008



services with the QCI of 5 LTE: LBFD-002008
in a cell TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008
1526727544 L.E-RAB.SuccEst Total number of successful Multi-mode: None Radio Bearer Management
UEs in a cell UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526727545 L.E-RAB.AttEst Total number of E-RAB Multi-mode: None Radio Bearer Management
setup attempts initiated by GSM: None Radio Bearer Management
UEs in a cell UMTS: None Dynamic DRX
LTE: LBFD-002008
TDLBFD-002008
LOFD-00110501
1526727546 L.E-RAB.AbnormRel Total number of abnormal Multi-mode: None Radio Bearer Management
E-RABs initiated by the UMTS: None
eNodeB
LTE: LBFD-002008
TDLBFD-002008
1526727547 L.E-RAB.NormRel Total number of normal Multi-mode: None Radio Bearer Management
E-RAB releases initiated by GSM: None Radio Bearer Management
the eNodeB in a cell UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526727849 L.Thrp.bits.UL.PLMN.QCI.1 Total uplink traffic volume Multi-mode: None Radio Bearer Management
for PDCP SDUs for a GSM: None RAN Sharing with
specific operator for UMTS: None Common Carrier
services with the QCI of 1 RAN Sharing with
LTE: LBFD-002008
in a cell Dedicated Carrier
LOFD-001036
LOFD-001037 Basic Scheduling
TDLBFD-002008 RAN Sharing with
Common Carrier
TDLOFD-001036


TDLOFD-001037 RAN Sharing with
TDLBFD-002025 Dedicated Carrier
Hybrid RAN Sharing
1526727850 L.Thrp.Time.UL.PLMN.QCI.1 Receive duration of uplink Multi-mode: None Radio Bearer Management
PDCP SDUs for a specific GSM: None RAN Sharing with
operator for services with UMTS: None Common Carrier
the QCI of 1 in a cell RAN Sharing with
LTE: LBFD-002008
LOFD-001036 Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
1526727853 L.E-RAB.AttEst.PLMN.QCI.1 Number of E-RAB setup Multi-mode: None Radio Bearer Management
for services with the QCI of UMTS: None RAN Sharing with
1for a specific operator in a Common Carrier
LTE: LBFD-002008
cell
LOFD-001037 RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526727854 L.E-RAB.SuccEst.PLMN.QCI.1 Number of successful Multi-mode: None Radio Bearer Management

UEs for services with the UMTS: None RAN Sharing with
QCI of 1 for a specific Common Carrier
LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
2 for a specific operator in Common Carrier
LTE: LBFD-002008
a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
a cell


TDLOFD-001036 Common Carrier
Hybrid RAN Sharing

LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier


LOFD-070206 Hybrid RAN Sharing
LTE: LBFD-002008
a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

UEs for services for a UMTS: None RAN Sharing with
specific operator with the Common Carrier
LTE: LBFD-002008
QCI of 9 in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526727871 L.E-RAB.AbnormRel.PLMN.QCI.1 Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs for services with UMTS: None RAN Sharing with
the QCI of 1 for a specific Common Carrier
LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526727872 L.E-RAB.NormRel.PLMN.QCI.1 Number of normal E-RAB Multi-mode: None Radio Bearer Management


the QCI of 1 for a specific UMTS: None RAN Sharing with
operator in a cell LTE: LBFD-002008 Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
operator in a cell Common Carrier
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
operator in a cell


Hybrid RAN Sharing
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier



LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526727889 L.PDCP.Tx.TotRev.Trf.SDU.QCI.1 Number of downlink PDCP Multi-mode: None Radio Bearer Management
SDUs transmitted for GSM: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025


TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526727907 L.Traffic.DL.PktDelay.Time.QCI.1 Total processing delay of Multi-mode: None Radio Bearer Management
DRB services with the QCI UMTS: None Basic Scheduling
of 1 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526727908 L.Traffic.DL.PktDelay.Num.QCI.1 Number of successfully Multi-mode: None Radio Bearer Management

transmitted downlink PDCP GSM: None Radio Bearer Management
SDUs for DRB services UMTS: None Basic Scheduling
with the QCI of 1 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
of 2 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025

TDLBFD-002008
LBFD-002025
TDLBFD-002025
of 3 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025

TDLBFD-002008
LBFD-002025
TDLBFD-002025
of 4 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025

TDLBFD-002008
LBFD-002025
TDLBFD-002025
of 5 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526727920 L.Traffic.DL.PktDelay.Num.QCI.5 Multi-mode: None Radio Bearer Management


Number of successfully GSM: None Radio Bearer Management
transmitted downlink PDCP UMTS: None Basic Scheduling
SDUs for DRB services LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
of 6 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025

TDLBFD-002008
LBFD-002025
TDLBFD-002025
of 7 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025

TDLBFD-002008
LBFD-002025
TDLBFD-002025
of 8 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025

TDLBFD-002008
LBFD-002025
TDLBFD-002025
of 9 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025

TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526727934 L.Traffic.DL.PktUuLoss.Loss.QCI.1 Number of downlink PDCP Multi-mode: None Radio Bearer Management
over the Uu interface
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526727935 L.Traffic.DL.PktUuLoss.Tot.QCI.1 Number of downlink PDCP Multi-mode: None Radio Bearer Management
TDLBFD-002008
LBFD-002025


TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526727941 L.Traffic.DL.PktUuLoss.Tot.QCI.3 Number of downlink Multi-mode: None Radio Bearer Management

transmitted PDCP SDUs GSM: None Radio Bearer Management
for services carried on UMTS: None Basic Scheduling
DRBs with a QCI of 3 in a
cell over the Uu interface
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025


with a QCI of 7 in a cell LTE: LBFD-002008 Basic Scheduling
over the Uu interface TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526727961 L.Traffic.UL.PktLoss.Loss.QCI.1 Number of uplink PDCP Multi-mode: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526727962 L.Traffic.UL.PktLoss.Tot.QCI.1 Number of expected uplink Multi-mode: None Radio Bearer Management
PDCP SDUs for services GSM: None Radio Bearer Management
carried on DRBs with a UMTS: None Basic Scheduling
QCI of 1 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
QCI of 2 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025


QCI of 3 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
QCI of 4 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
QCI of 5 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
QCI of 6 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
QCI of 7 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
QCI of 8 in a cell
TDLBFD-002008


LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
QCI of 9 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526728009 L.E-RAB.NormRel.HOOut.PLMN.QCI.1 Number of normal E-RAB Multi-mode: None Radio Bearer Management
releases for outgoing GSM: None Radio Bearer Management
handovers of services with UMTS: None RAN Sharing with
LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036


Hybrid RAN Sharing
LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526728018 L.E-RAB.AbnormRel.HOOut.PLMN.QCI.1 Number of abnormal Multi-mode: None Radio Bearer Management

E-RAB releases for GSM: None Radio Bearer Management
outgoing handovers of UMTS: None RAN Sharing with
services with the QCI of 1 Common Carrier
LTE: LBFD-002008
for a specific operator in a
cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing


LTE: LBFD-002008
cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing


LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
UMTS: None Common Carrier


operator for services with LTE: LBFD-002008 RAN Sharing with
the QCI of 6 in a cell LOFD-001036 Dedicated Carrier
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
Basic Scheduling


LOFD-001037 Radio Bearer Management
LBFD-002025 RAN Sharing with
TDLBFD-002008 Common Carrier
TDLOFD-001037 Dedicated Carrier
TDLBFD-002025 Basic Scheduling
1526728050 L.Thrp.bits.DL.PLMN.QCI.1 Total downlink traffic Multi-mode: None Radio Bearer Management
volume for PDCP SDUs for GSM: None RAN Sharing with
a specific operator for UMTS: None Common Carrier
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
1526728051 L.Thrp.Time.DL.PLMN.QCI.1 Transmit duration of Multi-mode: None Radio Bearer Management

downlink PDCP SDUs for a GSM: None RAN Sharing with
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
TDLBFD-002008


Basic Scheduling
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

downlink PDCP SDUs in a GSM: None RAN Sharing with
cell for a specific operator UMTS: None Common Carrier
for services with the QCI of RAN Sharing with
LTE: LBFD-002008
4 in a cell Dedicated Carrier
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036


Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling


1526728077 L.Traffic.User.Avg.PLMN Average number of users Multi-mode: None RRC Connection

served by a specific GSM: None Management
operator in a cell UMTS: None RRC Connection
Common Carrier
LOFD-001036
RAN Sharing with
TDLOFD-001036
Common Carrier
LOFD-001037
RAN Sharing with
Dedicated Carrier
Hybrid RAN Sharing
1526728178 L.Thrp.bits.DL.SRB Total Bits of Transmitted Multi-mode: None Radio Bearer Management
Signaling SDUs on SRBs GSM: None Radio Bearer Management
at the PDCP Layer UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728179 L.Thrp.bits.UL.SRB Total Bits of Received Multi-mode: None Radio Bearer Management
Signaling SDUs on SRBs GSM: None Radio Bearer Management
at the PDCP Layer UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728192 L.E-RAB.InitAttEst.QCI.1 Number of initial E-RAB Multi-mode: None Radio Bearer Management
QCI of 1 in a cell
LTE: LBFD-002008
TDLBFD-002008
1526728193 L.E-RAB.InitSuccEst.QCI.1 Number of successful initial Multi-mode: None Radio Bearer Management
QCI of 1 in a cell
LTE: LBFD-002008
TDLBFD-002008
QCI of 2 in a cell
LTE: LBFD-002008
TDLBFD-002008
QCI of 2 in a cell
LTE: LBFD-002008
TDLBFD-002008
QCI of 3 in a cell
LTE: LBFD-002008
TDLBFD-002008
QCI of 3 in a cell
LTE: LBFD-002008
TDLBFD-002008
QCI of 4 in a cell
LTE: LBFD-002008
TDLBFD-002008
QCI of 4 in a cell
LTE: LBFD-002008
TDLBFD-002008
QCI of 5 in a cell
LTE: LBFD-002008
TDLBFD-002008
QCI of 5 in a cell
LTE: LBFD-002008
TDLBFD-002008

QCI of 6 in a cell
LTE: LBFD-002008
TDLBFD-002008
QCI of 6 in a cell
LTE: LBFD-002008
TDLBFD-002008
QCI of 7 in a cell
LTE: LBFD-002008
TDLBFD-002008
QCI of 7 in a cell
LTE: LBFD-002008
TDLBFD-002008
QCI of 8 in a cell
LTE: LBFD-002008
TDLBFD-002008
QCI of 8 in a cell
LTE: LBFD-002008
TDLBFD-002008
QCI of 9 in a cell
LTE: LBFD-002008
TDLBFD-002008
QCI of 9 in a cell
LTE: LBFD-002008
TDLBFD-002008
1526728216 L.RRC.ConnSetup Number of RRC Multi-mode: None RRC Connection

connection setup times GSM: None Management
TDLBFD-002007
1526728217 L.RRC.ConnReq.Att.Emc Number of RRC Multi-mode: None RRC Connection

connection setup attempts GSM: None Management
with a cause value of UMTS: None RRC Connection
emergency Management
LTE: LBFD-002007
TDLBFD-002007 Dynamic DRX
LOFD-00110501
1526728218 L.RRC.ConnReq.Att.HighPri Number of RRC Multi-mode: None RRC Connection

highPriorityAccess Management
LTE: LBFD-002007
LOFD-00110501
1526728219 L.RRC.ConnReq.Att.Mt Number of RRC Multi-mode: None RRC Connection

with a cause value of mt- UMTS: None RRC Connection
Access Management
LTE: LBFD-002007
LOFD-00110501
1526728220 L.RRC.ConnReq.Att.MoSig Number of RRC Multi-mode: None RRC Connection

with a cause value of mo- UMTS: None RRC Connection
Signalling Management
LTE: LBFD-002007
LOFD-00110501
1526728221 L.RRC.ConnReq.Att.MoData Number of RRC Multi-mode: None RRC Connection

Data Management
LTE: LBFD-002007


LOFD-00110501
1526728222 L.RRC.ConnReq.Succ.Emc Number of RRC Multi-mode: None RRC Connection

Connection Setup GSM: None Management
Complete messages with a UMTS: None RRC Connection
cause value of emergency Management
LTE: LBFD-002007
received from UEs in a cell
TDLBFD-002007
1526728223 L.RRC.ConnReq.Succ.HighPri Number of RRC Multi-mode: None RRC Connection

cause value of Management
LTE: LBFD-002007
highPriorityAccess
received from UEs in a cell TDLBFD-002007
1526728224 L.RRC.ConnReq.Succ.Mt Number of RRC Multi-mode: None RRC Connection

cause value of mt-Access Management
LTE: LBFD-002007
TDLBFD-002007
1526728225 L.RRC.ConnReq.Succ.MoSig Number of RRC Multi-mode: None RRC Connection

cause value of mo- Management
LTE: LBFD-002007
Signalling received from
UEs in a cell TDLBFD-002007
1526728226 L.RRC.ConnReq.Succ.MoData Number of RRC Multi-mode: None RRC Connection

cause value of mo-Data Management
LTE: LBFD-002007
TDLBFD-002007
1526728227 L.UECNTX.AbnormRel Number of abnormal UE Multi-mode: None Radio Bearer Management

context releases in a cell GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728228 L.UECNTX.NormRel Number of normal UE Multi-mode: None Radio Bearer Management

context releases in a cell GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728232 L.Thrp.Time.Cell.DL Total duration of downlink Multi-mode: None Radio Bearer Management
data transmission in a cell GSM: None Radio Bearer Management
UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526728233 L.Thrp.Time.Cell.UL Total duration of uplink Multi-mode: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526728234 L.E-RAB.SessionTime.QCI1 Duration of data Multi-mode: None Radio Bearer Management

transmission for services GSM: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025

TDLBFD-002008
LBFD-002025
TDLBFD-002025

TDLBFD-002008
LBFD-002025
TDLBFD-002025
L.E-RAB.SessionTime.QCI4


1526728237 Duration of data Multi-mode: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025

TDLBFD-002008
LBFD-002025
TDLBFD-002025

TDLBFD-002008
LBFD-002025
TDLBFD-002025

TDLBFD-002008
LBFD-002025
TDLBFD-002025

TDLBFD-002008
LBFD-002025
TDLBFD-002025

TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526728243 L.E-RAB.SessionTime.UE Total duration of UE data Multi-mode: None Radio Bearer Management
transmission time in a cell GSM: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526728248 L.E-RAB.AttModify Total number of E-RAB Multi-mode: None Radio Bearer Management
initiated by UEs in a cell UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728249 L.E-RAB.SuccModify Total number of successful Multi-mode: None Radio Bearer Management
LTE: LBFD-002008
TDLBFD-002008
1526728250 L.E-RAB.AttEst.PLMN Total number of E-RAB Multi-mode: None Radio Bearer Management
UEs for a specific operator UMTS: None RAN Sharing with
in a cell Common Carrier
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526728251 L.E-RAB.SuccEst.PLMN Total number of successful Multi-mode: None Radio Bearer Management
UEs for a specific operator UMTS: None RAN Sharing with
in a cell Common Carrier
LTE: LBFD-002008
Dedicated Carrier


LOFD-001037 Common Carrier
1526728258 L.Traffic.DRB Number of DRBs in a cell Multi-mode: None Radio Bearer Management
GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728259 L.Thrp.bits.UL Total uplink traffic volume Multi-mode: None Radio Bearer Management
for PDCP PDUs in a cell GSM: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526728260 L.Thrp.Time.UL Total receive duration of Multi-mode: None Radio Bearer Management
uplink PDCP PDUs in a GSM: None Radio Bearer Management
cell UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526728261 L.Thrp.bits.DL Total downlink traffic Multi-mode: None Radio Bearer Management
volume for PDCP SDUs in GSM: None Radio Bearer Management
a cell UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526728262 L.Thrp.Time.DL Total transmit duration of Multi-mode: None Radio Bearer Management
downlink PDCP SDUs in a GSM: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526728263 L.Thrp.bits.UL.PLMN Total uplink traffic volume Multi-mode: None Radio Bearer Management
specific operator in a cell UMTS: None Common Carrier
LTE: LBFD-002008 RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
1526728264 L.Thrp.Time.UL.PLMN Total receive duration of Multi-mode: None Radio Bearer Management
uplink PDCP SDUs for a GSM: None RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
1526728265 L.Thrp.bits.DL.PLMN Total downlink traffic Multi-mode: None Radio Bearer Management
a specific operator in a cell UMTS: None Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing


1526728266 L.Thrp.Time.DL.PLMN Total transmit duration of Multi-mode: None Radio Bearer Management
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
1526728269 L.RRC.SetupFail.Rej Number of RRC Multi-mode: None RRC Connection

Connection Reject GSM: None Management
messages sent to UEs in a UMTS: None RRC Connection
cell Management
LTE: LBFD-002007
TDLBFD-002007
1526728270 L.RRC.ReEstFail.Rej Total number of RRC Multi-mode: None RRC Connection

rejections UMTS: None RRC Connection
TDLBFD-002007
1526728271 L.RRC.ReEstFail.NoCntx Number of RRC Multi-mode: None RRC Connection

failures due to UMTS: None RRC Connection
unavailability of UE Management
LTE: LBFD-002007
contexts
TDLBFD-002007
1526728272 L.S1Sig.ConnEst.Att Number of UE-related Multi-mode: None Radio Bearer Management

signaling connection setup GSM: None Radio Bearer Management
attempts over the S1 UMTS: None
interface
LTE: LBFD-002008
TDLBFD-002008
1526728273 L.S1Sig.ConnEst.Succ Number of successful UE- Multi-mode: None Radio Bearer Management
related signaling GSM: None Radio Bearer Management
connection setups over the UMTS: None
S1 interface
LTE: LBFD-002008
TDLBFD-002008
1526728274 L.E-RAB.InitAttEst Total number of initial Multi-mode: None Radio Bearer Management
E-RAB setup attempts GSM: None Radio Bearer Management
LTE: LBFD-002008
TDLBFD-002008
1526728275 L.E-RAB.InitSuccEst Total number of successful Multi-mode: None Radio Bearer Management
initial E-RAB setups GSM: None Radio Bearer Management
LTE: LBFD-002008
TDLBFD-002008
1526728276 L.E-RAB.FailEst.MME Number of E-RAB setup Multi-mode: None Radio Bearer Management
failures triggered by the GSM: None Radio Bearer Management
MME UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728277 L.E-RAB.FailEst.TNL Number of E-RAB setup Multi-mode: None Radio Bearer Management
failures due to faults at the GSM: None Radio Bearer Management
transport network layer UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728278 L.E-RAB.FailEst.RNL Number of E-RAB setup Multi-mode: None Radio Bearer Management
radio network layer UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023
1526728279 L.E-RAB.FailEst.NoRadioRes Number of E-RAB setup Multi-mode: None Radio Bearer Management
failures due to insufficient GSM: None Radio Bearer Management
radio resources UMTS: None Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023
1526728280 L.E-RAB.FailEst.SecurModeFail Multi-mode: None Radio Bearer Management



Number of E-RAB setup UMTS: None
failures due to security LTE: LBFD-002008
mode configuration failures TDLBFD-002008
1526728282 L.E-RAB.AbnormRel.Radio Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs due to faults at the UMTS: None
radio network layer
LTE: LBFD-002008
TDLBFD-002008
1526728283 L.E-RAB.AbnormRel.TNL Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs due to faults at the UMTS: None
transport network layer
LTE: LBFD-002008
TDLBFD-002008
1526728284 L.E-RAB.AbnormRel.Cong Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs due to network UMTS: None Congestion Control
congestion
LTE: LBFD-002008 Congestion Control
TDLBFD-002008 Radio/transport resource
LBFD-002024 pre-emption
LOFD-00102901 pre-emption
TDLOFD-00102901
1526728291 L.E-RAB.AbnormRel.HOFailure Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs due to handover UMTS: None
failures
LTE: LBFD-002008
TDLBFD-002008
1526728292 L.E-RAB.AbnormRel.MME Number of MME-triggered Multi-mode: None Radio Bearer Management

abnormal releases of GSM: None Radio Bearer Management
activated E-RABs UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728319 L.E-RAB.AbnormRel.eNBTot Total number of abnormal Multi-mode: None Radio Bearer Management
releases of E-RABs GSM: None Radio Bearer Management
initiated by the eNodeB UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728333 L.Traffic.User.Ulsync.Avg Average number of UL Multi-mode: None RRC Connection

synchronized users in a GSM: None Management
cell UMTS: None RRC Connection
TDLBFD-002007
1526728334 L.Traffic.eNodeB.User.Max Maximum number of users Multi-mode: None RRC Connection

under an eNodeB GSM: None Management
TDLBFD-002007
1526728335 L.Traffic.User.Data.Max Maximum number of users Multi-mode: None RRC Connection

with data in the buffer GSM: None Management
TDLBFD-002007
1526728336 L.Traffic.User.Data.Avg Average number of users Multi-mode: None RRC Connection

with data in the buffer GSM: None Management
TDLBFD-002007
1526728357 L.RRC.ConnReq.Att.DelayTol Number of RRC Multi-mode: None RRC Connection

delayTolerantAccess- Management
LTE: LBFD-002007
v1020 Dynamic DRX
TDLBFD-002007
LOFD-00110501
1526728358 L.RRC.ConnReq.Succ.DelayTol Number of successful RRC Multi-mode: None RRC Connection

connection setups with a GSM: None Management
cause value of UMTS: None RRC Connection
LTE: LBFD-002007
v1020
TDLBFD-002007
1526728383 L.E-RAB.AbnormRel.MME.PLMN Number of MME-triggered Multi-mode: None Radio Bearer Management

activated E-RABs for a UMTS: None RAN Sharing with
specific operator Common Carrier
LTE: LBFD-002008
TDLBFD-002008


Dedicated Carrier
Hybrid RAN Sharing
1526728436 L.E-RAB.Release.Unsyn Number of released Multi-mode: None Radio Bearer Management

E-RABs of UEs in the GSM: None Radio Bearer Management
uplink out-of- UMTS: None
synchronization state
LTE: LBFD-002008
TDLBFD-002008
1526728437 L.E-RAB.Num.Syn2Unsyn Total number of E-RABs in Multi-mode: None Radio Bearer Management
UE contexts when the UEs GSM: None Radio Bearer Management
switch from the uplink UMTS: None
synchronized state to the
LTE: LBFD-002008
uplink out-of-
synchronization state in a TDLBFD-002008
cell
1526728438 L.RRC.StateTrans.Syn2Unsyn Number of times a UE Multi-mode: None RRC Connection

switch from the Uplink- GSM: None Management
Synchronized state to the UMTS: None RRC Connection
uplink out-of- Management
LTE: LBFD-002007
synchronization state
TDLBFD-002007
1526728439 L.RRC.StateTrans.Unsyn2Syn Number of times a UE Multi-mode: None RRC Connection

switch from the out-of- GSM: None Management
synchronization state to the UMTS: None RRC Connection
uplink-synchronized state Management
LTE: LBFD-002007
TDLBFD-002007
1526728440 L.UECNTX.Release.HighSpeed Number of UE context Multi-mode: None Radio Bearer Management

releases due to high GSM: None Radio Bearer Management
mobility of UEs UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728445 L.Traffic.ActiveUser.UL.QCI.Total Total number of activated Multi-mode: None RRC Connection

UEs with a QCI (or an GSM: None Management
extended QCI) in the uplink UMTS: None RRC Connection
buffer Management
LTE: LBFD-002007
TDLBFD-002007
1526728446 L.Traffic.ActiveUser.UL.QCI.1 Number of activated UEs Multi-mode: None RRC Connection

with the QCI of 1 in the GSM: None Management
uplink buffer UMTS: None RRC Connection
TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007


TDLBFD-002007

TDLBFD-002007
1526728455 L.Traffic.ActiveUser.DL.QCI.Total Total number of activated Multi-mode: None RRC Connection

UEs with a QCI (or an GSM: None Management
extended QCI) in the UMTS: None RRC Connection
downlink buffer Management
LTE: LBFD-002007
TDLBFD-002007
1526728456 L.Traffic.ActiveUser.DL.QCI.1 Number of activated UEs Multi-mode: None RRC Connection

downlink buffer UMTS: None RRC Connection
TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007
1526728467 L.Traffic.User.Max.PLMN Maximum number of users Multi-mode: None RRC Connection

for a specific operator in a GSM: None Management
Common Carrier
LOFD-001036
RAN Sharing with
TDLOFD-001036
Common Carrier
LOFD-001037
RAN Sharing with
Dedicated Carrier
Hybrid RAN Sharing
1526728473 L.Traffic.ULCEU.Avg Multi-mode: None


Average number of uplink GSM: None RRC Connection
cell edge users (CEUs) in a UMTS: None Management
cell LTE: LBFD-002007 RRC Connection
TDLBFD-002007 Management
TDLBFD-00202202 Uplink Static Inter-Cell
LOFD-060201
Adaptive Inter-Cell
TDLOFD-060201
Adaptive Inter-Cell
1526728474 L.Traffic.ULCEU.Max Maximum number of uplink Multi-mode: None RRC Connection

cell edge users (CEUs) in a GSM: None Management
TDLBFD-002007 Uplink Static Inter-Cell
TDLBFD-00202202
Adaptive Inter-Cell
LOFD-060201
TDLOFD-060201
Adaptive Inter-Cell
1526728481 L.Traffic.User.SRS.Avg Average number of UEs Multi-mode: None RRC Connection

configured with sounding GSM: None Management
reference signal (SRS) UMTS: None RRC Connection
resources in a cell Management
LTE: LBFD-002007
TDLBFD-002007
1526728482 L.Traffic.User.SRS.Max Maximum number of UEs Multi-mode: None RRC Connection

LTE: LBFD-002007
TDLBFD-002007
1526728485 L.RRC.SetupFail.ResFail.SRS Number of RRC Multi-mode: None RRC Connection

due to SRS resource UMTS: None RRC Connection
allocation failure Management
LTE: LBFD-002007
TDLBFD-002007
1526728486 L.RRC.SetupFail.ResFail.PUCCH Number of RRC Multi-mode: None RRC Connection

due to PUCCH resource UMTS: None RRC Connection
LTE: LBFD-002007
TDLBFD-002007
1526728487 L.UECNTX.Modify.Att Number of UE context Multi-mode: None Radio Bearer Management

UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728488 L.UECNTX.Modify.Succ Number of successful UE Multi-mode: None Radio Bearer Management

context modifications GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728489 L.RRC.ConnReq.Msg.disc.FlowCtrl Number of times the RRC Multi-mode: None RRC Connection
Connection Request GSM: None Management
message is discarded due UMTS: None RRC Connection
to flow control Management
LTE: LBFD-002007
TDLBFD-002007
1526728490 L.RRC.SetupFail.Rej.FlowCtrl Number of times the Multi-mode: None RRC Connection

eNodeB sends an RRC GSM: None Management
Connection Reject UMTS: None RRC Connection
message to the UE due to Management
LTE: LBFD-002007
flow control
TDLBFD-002007
1526728564 L.Thrp.bits.DL.CAUser Total traffic volume for Multi-mode: None Radio Bearer Management
PDCP SDUs sent to GSM: None Radio Bearer Management
activated CA UEs in a cell UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526728565 L.Thrp.Time.DL.CAUser Total duration for activated Multi-mode: None Radio Bearer Management
CA UEs transmitting GSM: None Radio Bearer Management
downlink data at the PDCP UMTS: None Basic Scheduling
layer in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526728672 L.Traffic.UL.AM.Retrans.bits Multi-mode: None Radio Bearer Management


Number of bits of uplink GSM: None Radio Bearer Management
PDUs retransmitted in UMTS: None
ARQ mode LTE: LBFD-002008
TDLBFD-002008
1526728673 L.Traffic.DL.AM.Retrans.bits Number of bits of downlink Multi-mode: None Radio Bearer Management
PDUs retransmitted in GSM: None Radio Bearer Management
ARQ mode UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728674 L.Traffic.UL.AM.RxPackets Number of uplink PDUs Multi-mode: None Radio Bearer Management
received in ARQ mode GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728675 L.Traffic.DL.AM.TxPackets Number of downlink PDUs Multi-mode: None Radio Bearer Management
transmitted in ARQ mode GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728676 L.Traffic.UL.AM.Retrans.RxPackets Number of uplink PDUs Multi-mode: None Radio Bearer Management
retransmitted in ARQ mode GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728677 L.Traffic.DL.AM.Retrans.TxPackets Number of downlink PDUs Multi-mode: None Radio Bearer Management
retransmitted in ARQ mode GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728678 L.Traffic.DL.AM.TxDropPackets Number of discarded Multi-mode: None Radio Bearer Management

downlink PDUs in ARQ GSM: None Radio Bearer Management
mode UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728744 L.UECNTX.Release.DurMeasU Number of UE context Multi-mode: None Radio Bearer Management

releases during WCDMA GSM: None PS Inter-RAT Mobility
network measurement UMTS: None between E-UTRAN and
LTE: LBFD-002008 UTRAN
TDLBFD-002008 PS Inter-RAT Mobility
between E-UTRAN and
TDLOFD-001019
UTRAN
1526728745 L.UECNTX.Release.DurMeasG Number of UE context Multi-mode: None Radio Bearer Management

releases during a GERAN GSM: None PS Inter-RAT Mobility
measurement UMTS: None between E-UTRAN and
LTE: LBFD-002008 GERAN
TDLBFD-002008 PS Inter-RAT Mobility
between E-UTRAN and
TDLOFD-001020
GERAN
1526728767 L.S1.Unavail.Dur.Manual Duration of S1 link Multi-mode: None Radio Bearer Management

unavailability due to human GSM: None Radio Bearer Management
factors UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728768 L.S1.Unavail.Dur.Sys Duration of S1 link Multi-mode: None Radio Bearer Management

unavailability due to GSM: None Radio Bearer Management
system faults UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728774 L.RRC.ConnSetup.TimeAvg Average RRC connection Multi-mode: None RRC Connection

setup duration GSM: None Management
TDLBFD-002007
1526728775 L.RRC.ConnSetup.TimeMax Maximum RRC connection Multi-mode: None RRC Connection

setup duration GSM: None Management
TDLBFD-002007
1526728776 L.E-RAB.Est.TimeAvg Average E-RAB setup Multi-mode: None Radio Bearer Management
duration in a cell GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008


TDLBFD-002008
1526728777 L.E-RAB.Est.TimeMax Maximum E-RAB setup Multi-mode: None Radio Bearer Management
duration in a cell GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728787 L.E-RAB.FailModify.NoRadioRes Number of E-RAB Multi-mode: None Radio Bearer Management

modification failures due to GSM: None Radio Bearer Management
insufficient radio resources UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728788 L.E-RAB.Rel.eNodeB.QCI.1 Number of E-RAB releases Multi-mode: None Radio Bearer Management
initiated by the eNodeB for GSM: None Radio Bearer Management
services with QCI of 1 in a UMTS: None
cell
LTE: LBFD-002008
TDLBFD-002008
cell
LTE: LBFD-002008
TDLBFD-002008
cell
LTE: LBFD-002008
TDLBFD-002008
cell
LTE: LBFD-002008
TDLBFD-002008
cell
LTE: LBFD-002008
TDLBFD-002008
cell
LTE: LBFD-002008
TDLBFD-002008
cell
LTE: LBFD-002008
TDLBFD-002008
cell
LTE: LBFD-002008
TDLBFD-002008
cell
LTE: LBFD-002008
TDLBFD-002008
1526728797 L.E-RAB.Rel.eNodeB Total number of E-RAB Multi-mode: None Radio Bearer Management
releases initiated by the GSM: None Radio Bearer Management
eNodeB in a cell UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728798 L.E-RAB.Rel.MME.QCI.1 Number of E-RAB releases Multi-mode: None Radio Bearer Management
initiated by the MME for GSM: None Radio Bearer Management
cell
LTE: LBFD-002008
TDLBFD-002008
cell
LTE: LBFD-002008
TDLBFD-002008
1526728800 L.E-RAB.Rel.MME.QCI.3 Multi-mode: None Radio Bearer Management


Number of E-RAB releases GSM: None Radio Bearer Management
initiated by the MME for UMTS: None
services with QCI of 3 in a LTE: LBFD-002008
cell
TDLBFD-002008
cell
LTE: LBFD-002008
TDLBFD-002008
cell
LTE: LBFD-002008
TDLBFD-002008
cell
LTE: LBFD-002008
TDLBFD-002008
cell
LTE: LBFD-002008
TDLBFD-002008
cell
LTE: LBFD-002008
TDLBFD-002008
cell
LTE: LBFD-002008
TDLBFD-002008
1526728807 L.E-RAB.Rel.MME Total number of E-RAB Multi-mode: None Radio Bearer Management
MME UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728808 L.E-RAB.Left.QCI.1 Number of remaining Multi-mode: None Radio Bearer Management

E-RABs for services with GSM: None Radio Bearer Management
QCI of 1 in a cell UMTS: None
LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008



LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008
1526728817 L.E-RAB.Left Total number of remaining Multi-mode: None Radio Bearer Management
E-RABs in a cell GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728818 L.E-RAB.Rel.S1Reset.eNodeB.QCI.1 Number of abnormal Multi-mode: None Radio Bearer Management

the eNodeB for services UMTS: None
with QCI of 1 because of
LTE: LBFD-002008
the S1 RESET in a cell
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008
1526728827 L.E-RAB.Rel.S1Reset.eNodeB Total number of abnormal Multi-mode: None Radio Bearer Management
the eNodeB because of the UMTS: None
S1 RESET in a cell
LTE: LBFD-002008
TDLBFD-002008
1526728828 L.E-RAB.Rel.S1Reset.MME.QCI.1 Number of abnormal Multi-mode: None Radio Bearer Management

the MME with QCI of 1 UMTS: None
because of the S1 RESET
LTE: LBFD-002008
in a cell
TDLBFD-002008


LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008

LTE: LBFD-002008
in a cell
TDLBFD-002008
1526728837 L.E-RAB.Rel.S1Reset.MME Total number of abnormal Multi-mode: None Radio Bearer Management
the MME because of the UMTS: None
S1 RESET in a cell
LTE: LBFD-002008
TDLBFD-002008
1526728838 L.UECNTX.Rel.S1Reset.eNodeB Number of abnormal UE Multi-mode: None Radio Bearer Management

context releases initiated GSM: None Radio Bearer Management
by the eNodeB due to S1 UMTS: None
RESET
LTE: LBFD-002008
TDLBFD-002008
1526728839 L.UECNTX.Rel.S1Reset.MME Number of abnormal UE Multi-mode: None Radio Bearer Management

by the MME due to S1 UMTS: None
RESET
LTE: LBFD-002008
TDLBFD-002008
1526728840 L.E-RAB.Rel.S1Reset.eNodeB.PLMN.QCI.1 Number of abnormal Multi-mode: None Radio Bearer Management

the eNodeB for services UMTS: None RAN Sharing with
with the QCI of 1 because Common Carrier
LTE: LBFD-002008
of the S1 RESET for a
specific operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036


Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing


1526728849 L.E-RAB.Rel.S1Reset.eNodeB.PLMN Total number of abnormal Multi-mode: None Radio Bearer Management
the eNodeB because of the UMTS: None RAN Sharing with
S1 RESET for a specific Common Carrier
LTE: LBFD-002008
operator in a cell
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526728850 L.UECNTX.AttEst Number of UE context Multi-mode: None Radio Bearer Management

setup attempts GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728851 L.UECNTX.SuccEst Number of successful UE Multi-mode: None Radio Bearer Management

context setups GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728852 L.UECNTX.FailEst.RNL Number of initial context Multi-mode: None Radio Bearer Management
setup failures due to faults GSM: None Radio Bearer Management
at the radio network layer UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728853 L.UECNTX.FailEst.SecurModeFail Number of initial context Multi-mode: None Radio Bearer Management
setup failures due to the GSM: None Radio Bearer Management
security mode UMTS: None
configuration failure
LTE: LBFD-002008
TDLBFD-002008
1526728854 L.UECNTX.FailEst.NoRadioRes Number of initial context Multi-mode: None Radio Bearer Management
setup failures due to GSM: None Radio Bearer Management
insufficient radio resources UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728855 L.UECNTX.FailEst.UeNoReply Number of initial context Multi-mode: None Radio Bearer Management
setup failures due to no GSM: None Radio Bearer Management
response from the UE UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728856 L.UECNTX.Rel.eNodeB Number of UE context Multi-mode: None Radio Bearer Management

eNodeB UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728857 L.UECNTX.Rel.eNodeB.Rnl Number of UE context Multi-mode: None Radio Bearer Management

eNodeB due to faults at the UMTS: None
radio network layer
LTE: LBFD-002008
TDLBFD-002008
1526728858 L.UECNTX.Rel.eNodeB.Userinact Number of UE context Multi-mode: None Radio Bearer Management

eNodeB due to user UMTS: None
inactivity
LTE: LBFD-002008
TDLBFD-002008
1526728859 L.UECNTX.Rel.eNodeB.UeLost Number of UE context Multi-mode: None Radio Bearer Management

eNodeB due to UE lost UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728860 L.UECNTX.Rel.eNodeB.HOFailure Number of UE context Multi-mode: None Radio Bearer Management

eNodeB due to a handover UMTS: None
failure
LTE: LBFD-002008
TDLBFD-002008
1526728861 L.UECNTX.Rel.MME Number of UE context Multi-mode: None Radio Bearer Management

MME UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728862 L.UECNTX.Rel.MME.Normalrel Number of UE context Multi-mode: None Radio Bearer Management

UMTS: None


MME due to a normal LTE: LBFD-002008
cause TDLBFD-002008
1526728879 L.E-RAB.InitEst.TimeAvg Average initial E-RAB Multi-mode: None Radio Bearer Management
setup duration in a cell GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728880 L.E-RAB.InitEst.TimeMax Maximum initial E-RAB Multi-mode: None Radio Bearer Management
setup duration in a cell GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728940 L.E-RAB.AbnormRel.MMETot Total number of MME- Multi-mode: None Radio Bearer Management
triggered abnormal E-RAB GSM: None Radio Bearer Management
releases UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728941 L.E-RAB.AbnormRel.MMETot.PLMN Total number of MME- Multi-mode: None Radio Bearer Management
triggered abnormal E-RAB GSM: None Radio Bearer Management
releases for a specific UMTS: None RAN Sharing with
operator Common Carrier
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526728969 L.Traffic.ActiveUser.DL.Avg Average number of Multi-mode: None RRC Connection

activated UEs in downlink GSM: None Management
TDLBFD-002007
1526728970 L.Traffic.ActiveUser.DL.Max Maximum number of Multi-mode: None RRC Connection

activated UEs in downlink GSM: None Management
TDLBFD-002007
1526728972 L.Traffic.ActiveUser.UL.Avg Average number of Multi-mode: None RRC Connection

activated UEs in uplink GSM: None Management
TDLBFD-002007
1526728973 L.Traffic.ActiveUser.UL.Max Maximum number of Multi-mode: None RRC Connection

activated UEs in uplink GSM: None Management
TDLBFD-002007
1526728975 L.Traffic.ActiveUser.Avg Average number of Multi-mode: None RRC Connection

activated UEs GSM: None Management
TDLBFD-002007
1526728976 L.Traffic.ActiveUser.Max Maximum number of Multi-mode: None RRC Connection

activated UEs GSM: None Management
TDLBFD-002007
1526728997 L.Thrp.Time.Cell.DL.HighPrecision Total duration of downlink Multi-mode: None Radio Bearer Management
(with the precision of 1 ms) UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526728998 L.Thrp.Time.Cell.UL.HighPrecision Total duration of uplink Multi-mode: None Radio Bearer Management
(with the precision of 1 ms) UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526729005 L.Thrp.bits.DL.LastTTI Downlink traffic volume Multi-mode: None Radio Bearer Management
sent in the last TTI for GSM: None Radio Bearer Management


PDCP SDUs before the UMTS: None Basic Scheduling
buffer is empty LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526729006 L.Thrp.bits.DL.LastTTI.QCI.1 Downlink traffic volume Multi-mode: None Radio Bearer Management
PDCP SDUs of services UMTS: None Basic Scheduling
with the QCI 1 before the
buffer is empty
TDLBFD-002008
LBFD-002025
TDLBFD-002025
buffer is empty
TDLBFD-002008
LBFD-002025
TDLBFD-002025
buffer is empty
TDLBFD-002008
LBFD-002025
TDLBFD-002025
buffer is empty
TDLBFD-002008
LBFD-002025
TDLBFD-002025
buffer is empty
TDLBFD-002008
LBFD-002025
TDLBFD-002025
buffer is empty
TDLBFD-002008
LBFD-002025
TDLBFD-002025
buffer is empty
TDLBFD-002008
LBFD-002025
TDLBFD-002025
buffer is empty
TDLBFD-002008
LBFD-002025
TDLBFD-002025
buffer is empty
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526729015 L.Thrp.Time.DL.RmvLastTTI Data transmit duration Multi-mode: None Radio Bearer Management
except the last TTI before GSM: None Radio Bearer Management
the downlink buffer is UMTS: None Basic Scheduling
empty
TDLBFD-002008
LBFD-002025
TDLBFD-002025

1526729016 L.Thrp.Time.DL.RmvLastTTI.QCI.1 Data transmit duration Multi-mode: None Radio Bearer Management
empty for services with the
QCI 1
TDLBFD-002008
LBFD-002025
TDLBFD-002025
QCI 2
TDLBFD-002008
LBFD-002025
TDLBFD-002025
QCI 3
TDLBFD-002008
LBFD-002025
TDLBFD-002025
QCI 4
TDLBFD-002008
LBFD-002025
TDLBFD-002025
QCI 5
TDLBFD-002008
LBFD-002025
TDLBFD-002025
QCI 6
TDLBFD-002008
LBFD-002025
TDLBFD-002025
QCI 7
TDLBFD-002008
LBFD-002025
TDLBFD-002025
QCI 8
TDLBFD-002008
LBFD-002025
TDLBFD-002025
QCI 9
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526729025 L.Thrp.bits.DL.LastTTI.PLMN Downlink traffic volume Multi-mode: None Radio Bearer Management
sent in the last TTI before GSM: None RAN Sharing with
the buffer is empty for a UMTS: None Common Carrier
specific operator RAN Sharing with
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206


Hybrid RAN Sharing
1526729026 L.Thrp.bits.DL.LastTTI.PLMN.QCI.1 Downlink traffic volume Multi-mode: None Radio Bearer Management
the buffer is empty for UMTS: None Common Carrier
services with the QCI 1 for RAN Sharing with
LTE: LBFD-002008
a specific operator Dedicated Carrier
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
1526729032 L.Thrp.bits.DL.LastTTI.PLMN.QCI.7 Multi-mode: None Radio Bearer Management


Downlink traffic volume GSM: None RAN Sharing with
sent in the last TTI before UMTS: None Common Carrier
the buffer is empty for LTE: LBFD-002008 RAN Sharing with
services with the QCI 7 for Dedicated Carrier
LOFD-001036
a specific operator Basic Scheduling
LOFD-001037
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
1526729035 L.Thrp.Time.DL.RmvLastTTI.PLMN Data transmit duration Multi-mode: None Radio Bearer Management
except the last TTI before GSM: None RAN Sharing with
the downlink buffer is UMTS: None Common Carrier
empty for a specific RAN Sharing with
LTE: LBFD-002008
operator Dedicated Carrier
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
1526729036 L.Thrp.Time.DL.RmvLastTTI.PLMN.QCI.1 Data transmit duration Multi-mode: None Radio Bearer Management
empty for services with the RAN Sharing with
LTE: LBFD-002008
QCI 1 for a specific Dedicated Carrier
operator LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008


QCI 3 for a specific LOFD-001036 RAN Sharing with
operator LOFD-001037 Dedicated Carrier
LBFD-002025 Basic Scheduling
TDLBFD-002008 Radio Bearer Management
Dedicated Carrier
LOFD-070206
Basic Scheduling
Hybrid RAN Sharing
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
LTE: LBFD-002008
Basic Scheduling


1526729049 L.Thrp.bits.UE.UL.LastTTI Traffic volume of uplink Multi-mode: None Radio Bearer Management
PDCP PDUs sent in the GSM: None Radio Bearer Management
last TTI before the UE UMTS: None Basic Scheduling
buffer is empty
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526729050 L.Thrp.Time.UE.UL.RmvLastTTI Uplink data transmit Multi-mode: None Radio Bearer Management
duration except the last TTI GSM: None Radio Bearer Management
before the UE buffer is UMTS: None Basic Scheduling
empty
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526729051 L.Thrp.bits.UE.UL.LastTTI.PLMN Traffic volume of uplink Multi-mode: None Radio Bearer Management
PDCP PDUs sent in the GSM: None Radio Bearer Management
last TTI before the UE UMTS: None Basic Scheduling
buffer is empty for a
specific operator
TDLBFD-002008 Hybrid RAN Sharing
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
1526729052 L.Thrp.Time.UE.UL.RmvLastTTI.PLMN Uplink data transmit Multi-mode: None Radio Bearer Management
duration except the last TTI GSM: None Radio Bearer Management
before the UE buffer is UMTS: None Basic Scheduling
empty for a specific
operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
1526729056 L.Thrp.DL.BitRate.Samp.Index0 Number of samples with Multi-mode: None Radio Bearer Management
the downlink throughput GSM: None Radio Bearer Management
ranging within index 0 UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526729060 L.Thrp.DL.BitRate.Samp.Index4 Multi-mode: None Radio Bearer Management


Number of samples with GSM: None Radio Bearer Management
the downlink throughput UMTS: None Basic Scheduling
ranging within index 4 LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526729066 L.Thrp.DL.BitRate.QCI1.Samp.Index0 Number of samples with Multi-mode: None Radio Bearer Management
the downlink QCI-1 service GSM: None Radio Bearer Management
throughput ranging within UMTS: None Basic Scheduling
index 0
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 1
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 2
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 3
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 4
TDLBFD-002008
LBFD-002025


TDLBFD-002025
index 5
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 6
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 7
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 8
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 9
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 0
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 1
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 2
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 3
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 4
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 5


TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 6
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 7
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 8
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 9
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 0
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 1
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 2
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 3
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 4
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 5
TDLBFD-002008
LBFD-002025
TDLBFD-002025


index 6
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 7
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 8
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 9
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 0
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 1
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 2
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 3
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 4
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 5
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 6
TDLBFD-002008


LBFD-002025
TDLBFD-002025
index 7
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 8
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 9
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 0
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 1
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 2
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 3
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 4
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 5
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 6
TDLBFD-002008
LBFD-002025
TDLBFD-002025


index 7 LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 8
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 9
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 0
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 1
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 2
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 3
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 4
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 5
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 6
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 7
TDLBFD-002008
LBFD-002025
TDLBFD-002025

index 8
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 9
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 0
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 1
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 2
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 3
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 4
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 5
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 6
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 7
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 8


TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 9
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 0
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 1
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 2
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 3
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 4
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 5
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 6
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 7
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 8
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526729145 L.Thrp.DL.BitRate.QCI8.Samp.Index9 Multi-mode: None Radio Bearer Management


the downlink QCI-8 service UMTS: None Basic Scheduling
throughput ranging within LTE: LBFD-002008 Basic Scheduling
index 9
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 0
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 1
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 2
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 3
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 4
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 5
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 6
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 7
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 8
TDLBFD-002008
LBFD-002025
TDLBFD-002025
index 9
TDLBFD-002008
LBFD-002025


TDLBFD-002025
1526729156 L.Thrp.DL.BitRate.Samp.Index0.PLMN Number of operator- Multi-mode: None Radio Bearer Management

specific samples with the GSM: None RAN Sharing with
downlink throughput UMTS: None Common Carrier
ranging within index 0 RAN Sharing with
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
1526729162 L.Thrp.DL.BitRate.Samp.Index6.PLMN Multi-mode: None Radio Bearer Management


Number of operator- GSM: None RAN Sharing with
specific samples with the UMTS: None Common Carrier
downlink throughput LTE: LBFD-002008 RAN Sharing with
ranging within index 6 Dedicated Carrier
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
1526729166 L.Thrp.DL.BitRate.QCI1.Samp.Index0.PLMN Number of operator- Multi-mode: None Radio Bearer Management

downlink QCI-1 service UMTS: None Common Carrier
throughput ranging within RAN Sharing with
LTE: LBFD-002008
index 0 Dedicated Carrier
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008


throughput ranging within LOFD-001036 RAN Sharing with
index 2 LOFD-001037 Dedicated Carrier
Dedicated Carrier
LOFD-070206
Basic Scheduling
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Basic Scheduling



LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
TDLBFD-002008


Basic Scheduling
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036


Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling



LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
1526729199 L.Thrp.DL.BitRate.QCI4.Samp.Index3.PLMN Multi-mode: None Radio Bearer Management


downlink QCI-4 service LTE: LBFD-002008 RAN Sharing with
throughput ranging within Dedicated Carrier
LOFD-001036
index 3 Basic Scheduling
LOFD-001037
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008


Dedicated Carrier
LOFD-070206
Basic Scheduling
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Basic Scheduling



LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
TDLBFD-002008


Basic Scheduling
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036


Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling



LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
1526729236 L.Thrp.DL.BitRate.QCI8.Samp.Index0.PLMN Multi-mode: None Radio Bearer Management


downlink QCI-8 service LTE: LBFD-002008 RAN Sharing with
throughput ranging within Dedicated Carrier
LOFD-001036
index 0 Basic Scheduling
LOFD-001037
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008


Dedicated Carrier
LOFD-070206
Basic Scheduling
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Basic Scheduling



LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
TDLBFD-002008


Basic Scheduling
Hybrid RAN Sharing

LTE: LBFD-002008
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
1526729256 L.Thrp.eNodeB.bits.DL.Max Maximum downlink traffic Multi-mode: None Radio Bearer Management
an eNodeB UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526729257 L.Thrp.eNodeB.bits.UL.Max Maximum uplink traffic Multi-mode: None Radio Bearer Management
an eNodeB UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526729258 L.Thrp.eNodeB.bits.Max Maximum sum of the uplink Multi-mode: None Radio Bearer Management
and downlink traffic volume GSM: None Radio Bearer Management
for PDCP SDUs in an UMTS: None Basic Scheduling
eNodeB
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526729261 L.E-RAB.FailEst.NoReply.PLMN Number of E-RAB setup Multi-mode: None Radio Bearer Management
failures due to no GSM: None Radio Bearer Management
responses from the UE in a UMTS: None RAN Sharing with
cell for a specific operator Common Carrier
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729262 L.E-RAB.FailEst.MME.PLMN Number of MME-triggered Multi-mode: None Radio Bearer Management

E-RAB setup failures for a GSM: None Radio Bearer Management
specific operator UMTS: None RAN Sharing with
LTE: LBFD-002008 Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729263 L.E-RAB.FailEst.TNL.PLMN Number of E-RAB setup Multi-mode: None Radio Bearer Management
transport network layer for UMTS: None RAN Sharing with
a specific operator Common Carrier
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729264 L.E-RAB.FailEst.RNL.PLMN Number of E-RAB setup Multi-mode: None Radio Bearer Management
radio network layer for a UMTS: None RAN Sharing with
LTE: LBFD-002008
Dedicated Carrier


1526729265 L.E-RAB.FailEst.NoRadioRes.PLMN Number of E-RAB setup Multi-mode: None Radio Bearer Management
radio resources for a UMTS: None RAN Sharing with
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729266 L.E-RAB.FailEst.SecurModeFail.PLMN Number of E-RAB setup Multi-mode: None Radio Bearer Management
failures due to security GSM: None Radio Bearer Management
mode configuration failures UMTS: None RAN Sharing with
for a specific operator Common Carrier
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729415 L.Thrp.bits.UE.UL.SmallPkt Uplink traffic volume of Multi-mode: None Radio Bearer Management
PDCP PDUs scheduled for GSM: None Radio Bearer Management
small packets UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526729416 L.Thrp.Time.UE.UL.RmvSmallPkt Uplink data transmission Multi-mode: None Radio Bearer Management
duration except that for GSM: None Radio Bearer Management
small packets UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526729417 L.Thrp.bits.UE.UL.SmallPkt.PLMN Uplink traffic volume of Multi-mode: None Radio Bearer Management
PDCP PDUs scheduled for GSM: None RAN Sharing with
small packets for a specific UMTS: None Common Carrier
operator RAN Sharing with
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
1526729418 L.Thrp.Time.UE.UL.RmvSmallPkt.PLMN Uplink data transmission Multi-mode: None Radio Bearer Management
duration except that for GSM: None RAN Sharing with
small packets for a specific UMTS: None Common Carrier
operator RAN Sharing with
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
1526729435 L.Thrp.UL.BitRate.Samp.Index0 Number of samples with Multi-mode: None Radio Bearer Management
the uplink throughput GSM: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025


TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526729445 L.Thrp.UL.BitRate.Samp.Index0.PLMN Number of operator- Multi-mode: None Radio Bearer Management

uplink throughput ranging UMTS: None Common Carrier
within index 0 RAN Sharing with
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

within index 1


Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Basic Scheduling



LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing

LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
1526729493 L.E-RAB.AbnormRel.Radio.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs because of faults UMTS: None RAN Sharing with
at the radio network layer Common Carrier
LTE: LBFD-002008
for a specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729494 L.E-RAB.AbnormRel.TNL.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs because of faults UMTS: None RAN Sharing with
at the transport network Common Carrier
LTE: LBFD-002008
layer for a specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729495 L.E-RAB.AbnormRel.Cong.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs because of UMTS: None Congestion Control
network congestion for a
specific operator
Common Carrier
LOFD-001036
RAN Sharing with
LOFD-001037
Dedicated Carrier
TDLOFD-001036
RAN Sharing with
Dedicated Carrier
Hybrid RAN Sharing
1526729496 L.E-RAB.AbnormRel.HOFailure.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs because of UMTS: None RAN Sharing with
handover failures for a Common Carrier
LTE: LBFD-002008
specific operator
Common Carrier
TDLOFD-001036


Hybrid RAN Sharing
1526729545 L.E-RAB.FailEst.NoRadioRes.SRS Number of E-RAB setup Multi-mode: None Radio Bearer Management
SRS resources UMTS: None Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023
1526729546 L.E-RAB.FailEst.NoRadioRes.PUCCH Number of E-RAB setup Multi-mode: None Radio Bearer Management
PUCCH resources UMTS: None Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023
1526729547 L.E-RAB.FailEst.NoRadioRes.SRS.PLMN Number of E-RAB setup Multi-mode: None Radio Bearer Management
SRS resources for a UMTS: None RAN Sharing with
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729548 L.E-RAB.FailEst.NoRadioRes.PUCCH.PLMN Number of E-RAB setup Multi-mode: None Radio Bearer Management
PUCCH resources for a UMTS: None RAN Sharing with
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729549 L.E-RAB.AbnormRel.Radio.SRBReset Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs because the RLC UMTS: None
PDU for an SRB has been
LTE: LBFD-002008
retransmitted for the
maximum number of times TDLBFD-002008
1526729550 L.E-RAB.AbnormRel.Radio.DRBReset Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs because the RLC UMTS: None
PDU for a DRB has been
LTE: LBFD-002008
1526729551 L.E-RAB.AbnormRel.Radio.ULSyncFail Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs due to uplink UMTS: None
resynchronization failures
LTE: LBFD-002008
TDLBFD-002008
1526729552 L.E-RAB.AbnormRel.Radio.UuNoReply Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs because of no UMTS: None
responses from the UE
LTE: LBFD-002008
TDLBFD-002008
1526729553 L.E-RAB.AbnormRel.Radio.SRBReset.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs because the RLC UMTS: None RAN Sharing with
PDU for an SRB has been Common Carrier
LTE: LBFD-002008
maximum number of times
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729554 L.E-RAB.AbnormRel.Radio.DRBReset.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs because the RLC UMTS: None RAN Sharing with
PDU for a DRB has been Common Carrier
LTE: LBFD-002008


Hybrid RAN Sharing
1526729555 L.E-RAB.AbnormRel.Radio.ULSyncFail.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs due to uplink UMTS: None RAN Sharing with
resynchronization failures Common Carrier
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729556 L.E-RAB.AbnormRel.Radio.UuNoReply.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs because of no UMTS: None RAN Sharing with
responses from the UE for Common Carrier
LTE: LBFD-002008
a specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729666 L.Thrp.Time.Cell.DL.HighPrecision.PLMN Total duration of downlink Multi-mode: None Radio Bearer Management
data transmission for a GSM: None RAN Sharing with
(with the sampling period RAN Sharing with
LTE: LBFD-002008
of 1 millisecond) Dedicated Carrier
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
1526729667 L.Thrp.Time.Cell.UL.HighPrecision.PLMN Total duration of uplink Multi-mode: None Radio Bearer Management
data transmission for a GSM: None RAN Sharing with
(with the sampling period RAN Sharing with
LTE: LBFD-002008
of 1 millisecond) Dedicated Carrier
LOFD-001036
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
TDLBFD-002025
Basic Scheduling
LOFD-070206
Hybrid RAN Sharing
1526729668 L.Traffic.DL.PktSize.Samp.Index0 Number of samples with Multi-mode: None Radio Bearer Management
the downlink PDCP SDU GSM: None Radio Bearer Management
size ranging within index 0 UMTS: None
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008


LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
1526729678 L.Traffic.DL.PktSize.QCI1.Samp.Index0 Number of samples with Multi-mode: None Radio Bearer Management
the downlink QCI-1 PDCP GSM: None Radio Bearer Management
SDU size ranging within UMTS: None
index 0
LTE: LBFD-002008
TDLBFD-002008
index 1
LTE: LBFD-002008
TDLBFD-002008
index 2
LTE: LBFD-002008
TDLBFD-002008
index 3
LTE: LBFD-002008
TDLBFD-002008
index 4
LTE: LBFD-002008
TDLBFD-002008
index 5
LTE: LBFD-002008
TDLBFD-002008
index 6
LTE: LBFD-002008
TDLBFD-002008
index 7
LTE: LBFD-002008
TDLBFD-002008
index 8
LTE: LBFD-002008
TDLBFD-002008


index 9 LTE: LBFD-002008
TDLBFD-002008
index 0
LTE: LBFD-002008
TDLBFD-002008
index 1
LTE: LBFD-002008
TDLBFD-002008
index 2
LTE: LBFD-002008
TDLBFD-002008
index 3
LTE: LBFD-002008
TDLBFD-002008
index 4
LTE: LBFD-002008
TDLBFD-002008
index 5
LTE: LBFD-002008
TDLBFD-002008
index 6
LTE: LBFD-002008
TDLBFD-002008
index 7
LTE: LBFD-002008
TDLBFD-002008
index 8
LTE: LBFD-002008
TDLBFD-002008
index 9
LTE: LBFD-002008
TDLBFD-002008
index 0
LTE: LBFD-002008
TDLBFD-002008
index 1
LTE: LBFD-002008
TDLBFD-002008
index 2
LTE: LBFD-002008
TDLBFD-002008
index 3
LTE: LBFD-002008


TDLBFD-002008
index 4
LTE: LBFD-002008
TDLBFD-002008
index 5
LTE: LBFD-002008
TDLBFD-002008
index 6
LTE: LBFD-002008
TDLBFD-002008
the size of a downlink GSM: None Radio Bearer Management
QCI-3 PDCP SDU ranging UMTS: None
with index 7
LTE: LBFD-002008
TDLBFD-002008
index 8
LTE: LBFD-002008
TDLBFD-002008
index 9
LTE: LBFD-002008
TDLBFD-002008
index 0
LTE: LBFD-002008
TDLBFD-002008
index 1
LTE: LBFD-002008
TDLBFD-002008
index 2
LTE: LBFD-002008
TDLBFD-002008
index 3
LTE: LBFD-002008
TDLBFD-002008
index 4
LTE: LBFD-002008
TDLBFD-002008
index 5
LTE: LBFD-002008
TDLBFD-002008
index 6
LTE: LBFD-002008
TDLBFD-002008
index 7
LTE: LBFD-002008
TDLBFD-002008
1526729716 L.Traffic.DL.PktSize.QCI4.Samp.Index8 Multi-mode: None Radio Bearer Management


the downlink QCI-4 PDCP UMTS: None
SDU size ranging within LTE: LBFD-002008
index 8
TDLBFD-002008
index 9
LTE: LBFD-002008
TDLBFD-002008
index 0
LTE: LBFD-002008
TDLBFD-002008
index 1
LTE: LBFD-002008
TDLBFD-002008
index 2
LTE: LBFD-002008
TDLBFD-002008
index 3
LTE: LBFD-002008
TDLBFD-002008
index 4
LTE: LBFD-002008
TDLBFD-002008
index 5
LTE: LBFD-002008
TDLBFD-002008
index 6
LTE: LBFD-002008
TDLBFD-002008
index 7
LTE: LBFD-002008
TDLBFD-002008
index 8
LTE: LBFD-002008
TDLBFD-002008
index 9
LTE: LBFD-002008
TDLBFD-002008
index 0
LTE: LBFD-002008
TDLBFD-002008
index 1
LTE: LBFD-002008
TDLBFD-002008
index 2


LTE: LBFD-002008
TDLBFD-002008
index 3
LTE: LBFD-002008
TDLBFD-002008
index 4
LTE: LBFD-002008
TDLBFD-002008
index 5
LTE: LBFD-002008
TDLBFD-002008
index 6
LTE: LBFD-002008
TDLBFD-002008
index 7
LTE: LBFD-002008
TDLBFD-002008
index 8
LTE: LBFD-002008
TDLBFD-002008
index 9
LTE: LBFD-002008
TDLBFD-002008
index 0
LTE: LBFD-002008
TDLBFD-002008
index 1
LTE: LBFD-002008
TDLBFD-002008
index 2
LTE: LBFD-002008
TDLBFD-002008
index 3
LTE: LBFD-002008
TDLBFD-002008
index 4
LTE: LBFD-002008
TDLBFD-002008
index 5
LTE: LBFD-002008
TDLBFD-002008
index 6
LTE: LBFD-002008
TDLBFD-002008


index 7
LTE: LBFD-002008
TDLBFD-002008
index 8
LTE: LBFD-002008
TDLBFD-002008
index 9
LTE: LBFD-002008
TDLBFD-002008
index 0
LTE: LBFD-002008
TDLBFD-002008
index 1
LTE: LBFD-002008
TDLBFD-002008
index 2
LTE: LBFD-002008
TDLBFD-002008
index 3
LTE: LBFD-002008
TDLBFD-002008
index 4
LTE: LBFD-002008
TDLBFD-002008
index 5
LTE: LBFD-002008
TDLBFD-002008
index 6
LTE: LBFD-002008
TDLBFD-002008
index 7
LTE: LBFD-002008
TDLBFD-002008
index 8
LTE: LBFD-002008
TDLBFD-002008
index 9
LTE: LBFD-002008
TDLBFD-002008
index 0
LTE: LBFD-002008
TDLBFD-002008


TDLBFD-002008
index 2
LTE: LBFD-002008
TDLBFD-002008
index 3
LTE: LBFD-002008
TDLBFD-002008
index 4
LTE: LBFD-002008
TDLBFD-002008
index 5
LTE: LBFD-002008
TDLBFD-002008
index 6
LTE: LBFD-002008
TDLBFD-002008
index 7
LTE: LBFD-002008
TDLBFD-002008
index 8
LTE: LBFD-002008
TDLBFD-002008
index 9
LTE: LBFD-002008
TDLBFD-002008
1526729768 L.Traffic.UL.PktSize.Samp.Index0 Number of samples with Multi-mode: None Radio Bearer Management
the uplink PDCP SDU size GSM: None Radio Bearer Management
ranging within index 0 UMTS: None
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008


TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
1526729778 L.Traffic.UL.PktSize.QCI1.Samp.Index0 Number of samples with Multi-mode: None Radio Bearer Management
the uplink QCI-1 PDCP GSM: None Radio Bearer Management
index 0
LTE: LBFD-002008
TDLBFD-002008
index 1
LTE: LBFD-002008
TDLBFD-002008
index 2
LTE: LBFD-002008
TDLBFD-002008
index 3
LTE: LBFD-002008
TDLBFD-002008
index 4
LTE: LBFD-002008
TDLBFD-002008
index 5
LTE: LBFD-002008
TDLBFD-002008
index 6
LTE: LBFD-002008
TDLBFD-002008
index 7
LTE: LBFD-002008
TDLBFD-002008
index 8
LTE: LBFD-002008
TDLBFD-002008
index 9
LTE: LBFD-002008
TDLBFD-002008
1526729788 L.Traffic.UL.PktSize.QCI2.Samp.Index0 Multi-mode: None Radio Bearer Management


the uplink QCI-2 PDCP UMTS: None
index 0
TDLBFD-002008
index 1
LTE: LBFD-002008
TDLBFD-002008
index 2
LTE: LBFD-002008
TDLBFD-002008
index 3
LTE: LBFD-002008
TDLBFD-002008
index 4
LTE: LBFD-002008
TDLBFD-002008
index 5
LTE: LBFD-002008
TDLBFD-002008
index 6
LTE: LBFD-002008
TDLBFD-002008
index 7
LTE: LBFD-002008
TDLBFD-002008
index 8
LTE: LBFD-002008
TDLBFD-002008
index 9
LTE: LBFD-002008
TDLBFD-002008
index 0
LTE: LBFD-002008
TDLBFD-002008
index 1
LTE: LBFD-002008
TDLBFD-002008
index 2
LTE: LBFD-002008
TDLBFD-002008
index 3
LTE: LBFD-002008
TDLBFD-002008
index 4


LTE: LBFD-002008
TDLBFD-002008
index 5
LTE: LBFD-002008
TDLBFD-002008
index 6
LTE: LBFD-002008
TDLBFD-002008
index 7
LTE: LBFD-002008
TDLBFD-002008
index 8
LTE: LBFD-002008
TDLBFD-002008
index 9
LTE: LBFD-002008
TDLBFD-002008
index 0
LTE: LBFD-002008
TDLBFD-002008
index 1
LTE: LBFD-002008
TDLBFD-002008
index 2
LTE: LBFD-002008
TDLBFD-002008
index 3
LTE: LBFD-002008
TDLBFD-002008
index 4
LTE: LBFD-002008
TDLBFD-002008
index 5
LTE: LBFD-002008
TDLBFD-002008
index 6
LTE: LBFD-002008
TDLBFD-002008
index 7
LTE: LBFD-002008
TDLBFD-002008
index 8
LTE: LBFD-002008
TDLBFD-002008


index 9
LTE: LBFD-002008
TDLBFD-002008
index 0
LTE: LBFD-002008
TDLBFD-002008
index 1
LTE: LBFD-002008
TDLBFD-002008
index 2
LTE: LBFD-002008
TDLBFD-002008
index 3
LTE: LBFD-002008
TDLBFD-002008
index 4
LTE: LBFD-002008
TDLBFD-002008
index 5
LTE: LBFD-002008
TDLBFD-002008
index 6
LTE: LBFD-002008
TDLBFD-002008
index 7
LTE: LBFD-002008
TDLBFD-002008
index 8
LTE: LBFD-002008
TDLBFD-002008
index 9
LTE: LBFD-002008
TDLBFD-002008
index 0
LTE: LBFD-002008
TDLBFD-002008
index 1
LTE: LBFD-002008
TDLBFD-002008
index 2
LTE: LBFD-002008
TDLBFD-002008


TDLBFD-002008
index 4
LTE: LBFD-002008
TDLBFD-002008
index 5
LTE: LBFD-002008
TDLBFD-002008
index 6
LTE: LBFD-002008
TDLBFD-002008
index 7
LTE: LBFD-002008
TDLBFD-002008
index 8
LTE: LBFD-002008
TDLBFD-002008
index 9
LTE: LBFD-002008
TDLBFD-002008
index 0
LTE: LBFD-002008
TDLBFD-002008
index 1
LTE: LBFD-002008
TDLBFD-002008
index 2
LTE: LBFD-002008
TDLBFD-002008
index 3
LTE: LBFD-002008
TDLBFD-002008
index 4
LTE: LBFD-002008
TDLBFD-002008
index 5
LTE: LBFD-002008
TDLBFD-002008
index 6
LTE: LBFD-002008
TDLBFD-002008
index 7
LTE: LBFD-002008


TDLBFD-002008
index 8
LTE: LBFD-002008
TDLBFD-002008
index 9
LTE: LBFD-002008
TDLBFD-002008
index 0
LTE: LBFD-002008
TDLBFD-002008
index 1
LTE: LBFD-002008
TDLBFD-002008
index 2
LTE: LBFD-002008
TDLBFD-002008
index 3
LTE: LBFD-002008
TDLBFD-002008
index 4
LTE: LBFD-002008
TDLBFD-002008
index 5
LTE: LBFD-002008
TDLBFD-002008
index 6
LTE: LBFD-002008
TDLBFD-002008
index 7
LTE: LBFD-002008
TDLBFD-002008
index 8
LTE: LBFD-002008
TDLBFD-002008
index 9
LTE: LBFD-002008
TDLBFD-002008
index 0
LTE: LBFD-002008
TDLBFD-002008
index 1
LTE: LBFD-002008
TDLBFD-002008
1526729860 L.Traffic.UL.PktSize.QCI9.Samp.Index2 Multi-mode: None Radio Bearer Management


the uplink QCI-9 PDCP UMTS: None
index 2
TDLBFD-002008
index 3
LTE: LBFD-002008
TDLBFD-002008
index 4
LTE: LBFD-002008
TDLBFD-002008
index 5
LTE: LBFD-002008
TDLBFD-002008
index 6
LTE: LBFD-002008
TDLBFD-002008
index 7
LTE: LBFD-002008
TDLBFD-002008
index 8
LTE: LBFD-002008
TDLBFD-002008
index 9
LTE: LBFD-002008
TDLBFD-002008
1526729911 L.E-RAB.AbnormRel.MME.EUtranGen Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs triggered by the UMTS: None
MME with the release
LTE: LBFD-002008
cause of Release due to
E-UTRAN Generated TDLBFD-002008
Reason
1526729912 L.E-RAB.AbnormRel.Cong.PreEmp Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs because of radio UMTS: None Congestion Control
resource preemption
TDLOFD-00102901
1526729913 L.E-RAB.AbnormRel.Cong.Load Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs because of radio UMTS: None Congestion Control
resource overload
TDLBFD-002008
LBFD-002024
TDLBFD-002024
1526729914 L.E-RAB.AbnormRel.TNL.PreEmp Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs because of UMTS: None
transport resource
LTE: LBFD-002008
preemption
TDLBFD-002008
1526729915 L.E-RAB.AbnormRel.TNL.Load Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs because of UMTS: None
transport resource
LTE: LBFD-002008
overload
TDLBFD-002008
1526729916 L.E-RAB.AbnormRel.MMETot.VoIP Multi-mode: None Radio Bearer Management



Number of MME-triggered UMTS: None
abnormal releases of LTE: LBFD-002008
E-RABs for voice services TDLBFD-002008
1526729917 L.E-RAB.AbnormRel.Radio.SRBReset.VoIP Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs for voice services UMTS: None
because the RLC PDU for
LTE: LBFD-002008
an SRB has been
retransmitted for the TDLBFD-002008
1526729918 L.E-RAB.AbnormRel.Radio.NoReply.VoIP Number of abnormal Multi-mode: None Radio Bearer Management

because of no responses
LTE: LBFD-002008
from the UE
TDLBFD-002008
1526729919 L.E-RAB.AbnormRel.Radio.ULSyncFail.VoIP Number of abnormal Multi-mode: None Radio Bearer Management

because of uplink
LTE: LBFD-002008
TDLBFD-002008
1526729920 L.E-RAB.AbnormRel.MME.EUtranGen.VoIP Number of abnormal Multi-mode: None Radio Bearer Management

triggered by the MME with
LTE: LBFD-002008
the release cause of
Release due to E-UTRAN TDLBFD-002008
Generated Reason
1526729921 L.E-RAB.AbnormRel.Radio.VoIP Number of abnormal Multi-mode: None Radio Bearer Management

because of faults at the
LTE: LBFD-002008
radio network layer
TDLBFD-002008
1526729922 L.E-RAB.AbnormRel.HOFailure.VoIP Number of abnormal Multi-mode: None Radio Bearer Management

because of handover
LTE: LBFD-002008
failures
TDLBFD-002008
1526729923 L.E-RAB.AbnormRel.Cong.VoIP Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs for voice services UMTS: None Congestion Control
because of radio network
congestion
TDLOFD-00102901
1526729924 L.E-RAB.AbnormRel.MME.VoIP Number of MME-triggered Multi-mode: None Radio Bearer Management

activated E-RABs for voice UMTS: None
services
LTE: LBFD-002008
TDLBFD-002008
1526729925 L.E-RAB.AbnormRel.TNL.VoIP Number of abnormal Multi-mode: None Radio Bearer Management

because of faults at the
LTE: LBFD-002008
TDLBFD-002008
1526729926 L.E-RAB.AbnormRel.Cong.PreEmp.VoIP Number of abnormal Multi-mode: None Radio Bearer Management

because of radio resource
preemption
TDLOFD-00102901
1526729927 L.E-RAB.AbnormRel.Cong.Load.VoIP Number of abnormal Multi-mode: None Radio Bearer Management

because of radio resource
overload
TDLBFD-002008
LBFD-002024
TDLBFD-002024
1526729928 L.E-RAB.AbnormRel.TNL.PreEmp.VoIP Number of abnormal Multi-mode: None Radio Bearer Management



because of transport LTE: LBFD-002008
resource preemption TDLBFD-002008
1526729929 L.E-RAB.AbnormRel.TNL.Load.VoIP Number of abnormal Multi-mode: None Radio Bearer Management

because of transport
LTE: LBFD-002008
resource overload
TDLBFD-002008
1526729930 L.E-RAB.AbnormRel.MME.EUtranGen.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs triggered by the UMTS: None RAN Sharing with
MME with the release Common Carrier
LTE: LBFD-002008
cause of Release due to
E-UTRAN Generated
Reason for a specific
operator LOFD-001037 RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729931 L.E-RAB.AbnormRel.Cong.PreEmp.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs because of radio UMTS: None RAN Sharing with
resource preemption for a Common Carrier
LTE: LBFD-002008
specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LBFD-002024
Congestion Control
TDLBFD-002024
Congestion Control
LOFD-00102901
Radio/transport resource
TDLOFD-00102901 pre-emption
pre-emption
1526729932 L.E-RAB.AbnormRel.Cong.Load.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs because of radio UMTS: None RAN Sharing with
resource overload for a Common Carrier
LTE: LBFD-002008
specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LBFD-002024
Congestion Control
TDLBFD-002024
Congestion Control
1526729933 L.E-RAB.AbnormRel.TNL.PreEmp.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

transport resource Common Carrier
LTE: LBFD-002008
preemption for a specific
operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729934 L.E-RAB.AbnormRel.TNL.Load.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

transport resource Common Carrier
LTE: LBFD-002008
overload for a specific
operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729935 L.E-RAB.AbnormRel.MMETot.VoIP.PLMN Number of MME-triggered Multi-mode: None Radio Bearer Management

E-RABs for voice services UMTS: None RAN Sharing with
for a specific operator Common Carrier
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206


Hybrid RAN Sharing
1526729936 L.E-RAB.AbnormRel.Radio.SRBReset.VoIP.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

because the RLC PDU for Common Carrier
LTE: LBFD-002008
an SRB has been
for a specific operator LOFD-001037 RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729937 L.E-RAB.AbnormRel.Radio.NoReply.VoIP.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

because of no responses Common Carrier
LTE: LBFD-002008
from the UE for a specific
operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729938 L.E-RAB.AbnormRel.Radio.ULSyncFail.VoIP.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

because of uplink Common Carrier
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729939 L.E-RAB.AbnormRel.MME.EUtranGen.VoIP.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

triggered by the MME with Common Carrier
LTE: LBFD-002008
the release cause of
Release due to E-UTRAN
Generated Reason for a
specific operator LOFD-001037 RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729940 L.E-RAB.AbnormRel.Radio.VoIP.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

because of faults at the Common Carrier
LTE: LBFD-002008
radio network layer for a
specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729941 L.E-RAB.AbnormRel.HOFailure.VoIP.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

because of handover Common Carrier
LTE: LBFD-002008
failures for a specific
operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729942 L.E-RAB.AbnormRel.Cong.VoIP.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

because of radio network Common Carrier
LTE: LBFD-002008
congestion for a specific
operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LBFD-002024
Congestion Control
TDLBFD-002024
Congestion Control
LOFD-00102901


TDLOFD-00102901 Radio/transport resource
pre-emption
pre-emption
1526729943 L.E-RAB.AbnormRel.MME.VoIP.PLMN Number of MME-triggered Multi-mode: None Radio Bearer Management

activated E-RABs for voice UMTS: None RAN Sharing with
services for a specific Common Carrier
LTE: LBFD-002008
operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729944 L.E-RAB.AbnormRel.TNL.VoIP.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

because of faults at the Common Carrier
LTE: LBFD-002008
transport network layer for
a specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729945 L.E-RAB.AbnormRel.TNL.PreEmp.VoIP.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

because of transport Common Carrier
LTE: LBFD-002008
resource preemption for a
specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729946 L.E-RAB.AbnormRel.TNL.Load.VoIP.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

because of transport Common Carrier
LTE: LBFD-002008
resource overload for a
specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729947 L.E-RAB.AbnormRel.Cong.PreEmp.VoIP.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

because of radio resource Common Carrier
LTE: LBFD-002008
preemption for a specific
operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LBFD-002024
Congestion Control
TDLBFD-002024
Congestion Control
LOFD-00102901
TDLOFD-00102901 pre-emption
pre-emption
1526729948 L.E-RAB.AbnormRel.Cong.Load.VoIP.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

because of radio resource Common Carrier
LTE: LBFD-002008
overload for a specific
operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
LBFD-002024
Congestion Control
TDLBFD-002024
Congestion Control
1526729949 L.RRC.SetupFail.ResFail.UserSpec Number of RRC Multi-mode: None RRC Connection

UMTS: None


because of limitation of UE LTE: LBFD-002007 RRC Connection
number specification TDLBFD-002007 Management
1526729950 L.E-RAB.FailEst.SRBReset Number of E-RAB setup Multi-mode: None Radio Bearer Management
failures because the RLC GSM: None Radio Bearer Management
PDU for an SRB has been UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526729951 L.E-RAB.FailEst.TNL.DLRes Number of E-RAB setup Multi-mode: None Radio Bearer Management
failures because of GSM: None Radio Bearer Management
insufficient downlink UMTS: None Admission Control
transport resources
TDLBFD-002008
LBFD-002023
TDLBFD-002023
1526729952 L.E-RAB.FailEst.TNL.ULRes Number of E-RAB setup Multi-mode: None Radio Bearer Management
insufficient uplink transport UMTS: None Admission Control
resources
TDLBFD-002008
LBFD-002023
TDLBFD-002023
1526729953 L.E-RAB.FailEst.NoRadioRes.DLThrpLic Number of E-RAB setup Multi-mode: None Radio Bearer Management
insufficient licensed UMTS: None Admission Control
downlink traffic volume
TDLBFD-002008
LBFD-002023
TDLBFD-002023
1526729954 L.E-RAB.FailEst.NoRadioRes.ULThrpLic Number of E-RAB setup Multi-mode: None Radio Bearer Management
insufficient licensed uplink UMTS: None Admission Control
traffic volume
TDLBFD-002008
LBFD-002023
TDLBFD-002023
1526729955 L.E-RAB.FailEst.NoRadioRes.DLSatis Number of E-RAB setup Multi-mode: None Radio Bearer Management
failures because of a low GSM: None Radio Bearer Management
downlink satisfaction rate UMTS: None Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023
1526729956 L.E-RAB.FailEst.NoRadioRes.ULSatis Number of E-RAB setup Multi-mode: None Radio Bearer Management
uplink satisfaction rate UMTS: None Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023
1526729957 L.E-RAB.FailEst.NoReply.VoIP Number of setup failures of Multi-mode: None Radio Bearer Management
E-RABs for voice services GSM: None Radio Bearer Management
because of no responses UMTS: None
from the UE in a cell
LTE: LBFD-002008
TDLBFD-002008
1526729958 L.E-RAB.FailEst.MME.VoIP Number of MME-triggered Multi-mode: None Radio Bearer Management

setup failures of E-RABs GSM: None Radio Bearer Management
for voice services UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526729959 L.E-RAB.FailEst.TNL.VoIP Number of setup failures of Multi-mode: None Radio Bearer Management
because of faults at the UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526729960 L.E-RAB.FailEst.RNL.VoIP Number of setup failures of Multi-mode: None Radio Bearer Management
because of faults at the UMTS: None
radio network layer
LTE: LBFD-002008
TDLBFD-002008
1526729961 L.E-RAB.FailEst.NoRadioRes.VoIP Number of setup failures of Multi-mode: None Radio Bearer Management
because of insufficient UMTS: None Admission Control
radio resources


TDLBFD-002008
LBFD-002023
TDLBFD-002023
1526729962 L.E-RAB.FailEst.SecurModeFail.VoIP Number of setup failures of Multi-mode: None Radio Bearer Management
because of security mode UMTS: None
configuration failures
LTE: LBFD-002008
TDLBFD-002008
1526729963 L.E-RAB.FailEst.SRBReset.VoIP Number of setup failures of Multi-mode: None Radio Bearer Management
because the RLC PDU for UMTS: None
an SRB has been
LTE: LBFD-002008
1526729964 L.E-RAB.FailEst.NoRadioRes.SRS.VoIP Number of setup failures of Multi-mode: None Radio Bearer Management
SRS resources
TDLBFD-002008
LBFD-002023
TDLBFD-002023
1526729965 L.E-RAB.FailEst.NoRadioRes.PUCCH.VoIP Number of setup failures of Multi-mode: None Radio Bearer Management
PUCCH resources
TDLBFD-002008
LBFD-002023
TDLBFD-002023
1526729966 L.E-RAB.FailEst.NoRadioRes.DLThrpLic.VoIP Number of setup failures of Multi-mode: None Radio Bearer Management
licensed downlink traffic
volume
TDLBFD-002008
LBFD-002023
TDLBFD-002023
1526729967 L.E-RAB.FailEst.NoRadioRes.ULThrpLic.VoIP Number of setup failures of Multi-mode: None Radio Bearer Management
licensed uplink traffic
volume
TDLBFD-002008
LBFD-002023
TDLBFD-002023
1526729968 L.E-RAB.FailEst.NoRadioRes.DLSatis.VoIP Number of setup failures of Multi-mode: None Radio Bearer Management
because of a low downlink UMTS: None Admission Control
satisfaction rate
TDLBFD-002008
LBFD-002023
TDLBFD-002023
1526729969 L.E-RAB.FailEst.NoRadioRes.ULSatis.VoIP Number of setup failures of Multi-mode: None Radio Bearer Management
because of a low uplink UMTS: None Admission Control
satisfaction rate
TDLBFD-002008
LBFD-002023
TDLBFD-002023
1526729970 L.E-RAB.FailEst.TNL.DLRes.VoIP Number of setup failures of Multi-mode: None Radio Bearer Management
downlink transport
resources
TDLBFD-002008
LBFD-002023
TDLBFD-002023
1526729971 L.E-RAB.FailEst.TNL.ULRes.VoIP Number of setup failures of Multi-mode: None Radio Bearer Management
uplink transport resources
TDLBFD-002008
LBFD-002023
TDLBFD-002023
1526729972 L.E-RAB.FailEst.SRBReset.PLMN Number of E-RAB setup Multi-mode: None Radio Bearer Management
failures because the RLC GSM: None Radio Bearer Management
PDU for an SRB has been UMTS: None RAN Sharing with
retransmitted for the Common Carrier
LTE: LBFD-002008
for a specific operator TDLBFD-002008


Dedicated Carrier
Hybrid RAN Sharing
1526729973 L.E-RAB.FailEst.TNL.DLRes.PLMN Number of E-RAB setup Multi-mode: None Radio Bearer Management
transport resources for a
specific operator
LBFD-002023 Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729974 L.E-RAB.FailEst.TNL.ULRes.PLMN Number of E-RAB setup Multi-mode: None Radio Bearer Management
insufficient uplink transport UMTS: None Admission Control
resources for a specific
operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729975 L.E-RAB.FailEst.NoRadioRes.DLThrpLic.PLMN Number of E-RAB setup Multi-mode: None Radio Bearer Management
licensed traffic volume for a
specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729976 L.E-RAB.FailEst.NoRadioRes.ULThrpLic.PLMN Number of E-RAB setup Multi-mode: None Radio Bearer Management
insufficient uplink licensed UMTS: None Admission Control
traffic volume for a specific
operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729977 L.E-RAB.FailEst.NoRadioRes.DLSatis.PLMN Number of E-RAB setup Multi-mode: None Radio Bearer Management
downlink satisfaction rate UMTS: None Admission Control
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729978 L.E-RAB.FailEst.NoRadioRes.ULSatis.PLMN Number of E-RAB setup Multi-mode: None Radio Bearer Management
uplink satisfaction rate for a UMTS: None Admission Control
specific operator


Hybrid RAN Sharing
1526729979 L.E-RAB.FailEst.NoReply.VoIP.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management
because of no responses UMTS: None RAN Sharing with
from the UE in a cell for a Common Carrier
LTE: LBFD-002008
specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729980 L.E-RAB.FailEst.MME.VoIP.PLMN Number of MME-triggered Multi-mode: None Radio Bearer Management

setup failures of E-RABs GSM: None Radio Bearer Management
for voice services for a UMTS: None RAN Sharing with
LTE: LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729981 L.E-RAB.FailEst.TNL.VoIP.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management
because of faults at the UMTS: None RAN Sharing with
transport network layer for Common Carrier
LTE: LBFD-002008
a specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729982 L.E-RAB.FailEst.RNL.VoIP.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management
because of faults at the UMTS: None RAN Sharing with
radio network layer for a Common Carrier
LTE: LBFD-002008
specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729983 L.E-RAB.FailEst.NoRadioRes.VoIP.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management
radio resources for a
specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729984 L.E-RAB.FailEst.SecurModeFail.VoIP.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management
because of security mode UMTS: None RAN Sharing with
configuration failures for a Common Carrier
LTE: LBFD-002008
specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729985 L.E-RAB.FailEst.SRBReset.VoIP.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management
because the RLC PDU for UMTS: None RAN Sharing with
an SRB has been Common Carrier
LTE: LBFD-002008
Common Carrier


1526729986 L.E-RAB.FailEst.NoRadioRes.SRS.VoIP.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management
SRS resources for a
specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729987 L.E-RAB.FailEst.NoRadioRes.PUCCH.VoIP.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management
PUCCH resources for a
specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729988 L.E-RAB.FailEst.NoRadioRes.DLThrpLic.VoIP.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management
licensed downlink traffic
volume for a specific
operator TDLBFD-002008 RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729989 L.E-RAB.FailEst.NoRadioRes.ULThrpLic.VoIP.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management
licensed uplink traffic
volume for a specific
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729990 L.E-RAB.FailEst.NoRadioRes.DLSatis.VoIP.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management
satisfaction rate for a
specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729991 L.E-RAB.FailEst.NoRadioRes.ULSatis.VoIP.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management
specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing

1526729992 L.E-RAB.FailEst.TNL.DLRes.VoIP.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management
downlink transport
resources for a specific
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526729993 L.E-RAB.FailEst.TNL.ULRes.VoIP.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management
uplink transport resources
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526730113 L.E-RAB.SessionTime.UE.HighPrecision.PLMN Total duration of UE data Multi-mode: None Radio Bearer Management
transmission for a specific GSM: None Radio Bearer Management
operator in a cell (with the UMTS: None Basic Scheduling
precision of 100 ms)
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
1526730114 L.E-RAB.SessionTime.HighPrecision.PLMN Total duration of data Multi-mode: None Radio Bearer Management
transmission for a specific GSM: None Radio Bearer Management
operator in a cell (with the UMTS: None Basic Scheduling
precision of 100 ms)
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
1526730115 L.E-RAB.SessionTime.HighPrecision.PLMN.QCI1 Total duration of data Multi-mode: None Radio Bearer Management
with the QCI of 1 for a UMTS: None Basic Scheduling
(with the precision of 100
ms) TDLBFD-002008 Hybrid RAN Sharing
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier


specific operator in a cell LTE: LBFD-002008 Basic Scheduling
(with the precision of 100 TDLBFD-002008 Hybrid RAN Sharing
ms)
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier


(with the precision of 100 LBFD-002025 RAN Sharing with
ms) TDLBFD-002025 Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
1526730124 L.Traffic.PktInterval.Num.Index0 Number of times the Multi-mode: None RRC Connection

packet transmission GSM: None Management
interval for a UE in a cell UMTS: None Dynamic DRX
ranges within index 0 Dynamic DRX
LTE: LBFD-002007
LOFD-001105
TDLOFD-001105

LTE: LBFD-002007
LOFD-001105
TDLOFD-001105

LTE: LBFD-002007
LOFD-001105
TDLOFD-001105

LTE: LBFD-002007
LOFD-001105
TDLOFD-001105

LTE: LBFD-002007
LOFD-001105
TDLOFD-001105

LTE: LBFD-002007
LOFD-001105
TDLOFD-001105

LTE: LBFD-002007
LOFD-001105
TDLOFD-001105

LTE: LBFD-002007
LOFD-001105
TDLOFD-001105

LTE: LBFD-002007
LOFD-001105
TDLOFD-001105
1526730530 L.RRC.ConnReq.Msg.Emc Number of RRC Multi-mode: None RRC Connection

emergency performed by Management
LTE: LBFD-002007
UEs in a cell
(retransmission included) TDLBFD-002007
1526730531 L.RRC.ConnReq.Msg.HighPri Number of RRC Multi-mode: None RRC Connection

highPriorityAccess Management
LTE: LBFD-002007
performed by UEs in a cell
1526730532 L.RRC.ConnReq.Msg.Mt Number of RRC Multi-mode: None RRC Connection



with a cause value of mt- UMTS: None RRC Connection
Access performed by UEs LTE: LBFD-002007 Management
in a cell (retransmission TDLBFD-002007
included)
1526730533 L.RRC.ConnReq.Msg.MoSig Number of RRC Multi-mode: None RRC Connection

Signalling performed by Management
LTE: LBFD-002007
UEs in a cell
1526730534 L.RRC.ConnReq.Msg.MoData Number of RRC Multi-mode: None RRC Connection

Data performed by UEs in Management
LTE: LBFD-002007
a cell (retransmission
included) TDLBFD-002007
1526730535 L.RRC.ConnReq.Msg.DelayTol Number of RRC Multi-mode: None RRC Connection

LTE: LBFD-002007
v1020 performed by UEs in
a cell (retransmission TDLBFD-002007
included)
1526730536 L.RRC.ReEst.NonSrccell.Att Number of RRC Multi-mode: None RRC Connection

requests to another cell UMTS: None RRC Connection
TDLBFD-002007
1526730537 L.RRC.ReEst.NonSrccell.Succ Number of successful RRC Multi-mode: None RRC Connection

times to another cell UMTS: None RRC Connection
TDLBFD-002007
1526730538 L.UECNTX.Left Number of remaining UE Multi-mode: None Radio Bearer Management

context in a cell GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526730539 L.E-RAB.AbnormRel.eNBTot.QCI.1 Number of abnormal Multi-mode: None Radio Bearer Management

releases of E-RABs for GSM: None Radio Bearer Management
in a cell
LTE: LBFD-002008
TDLBFD-002008

in a cell
LTE: LBFD-002008
TDLBFD-002008

in a cell
LTE: LBFD-002008
TDLBFD-002008

in a cell
LTE: LBFD-002008
TDLBFD-002008

in a cell
LTE: LBFD-002008
TDLBFD-002008

in a cell
LTE: LBFD-002008
TDLBFD-002008

in a cell
LTE: LBFD-002008
TDLBFD-002008



in a cell LTE: LBFD-002008
TDLBFD-002008

in a cell
LTE: LBFD-002008
TDLBFD-002008
1526730560 L.Thrp.BitRate.DL.SRB Average rate of Multi-mode: None Radio Bearer Management

transmitting downlink GSM: None Radio Bearer Management
signaling data at the PDCP UMTS: None
layer in a cell
LTE: LBFD-002008
TDLBFD-002008
1526730561 L.Thrp.BitRate.UL.SRB Average rate of receiving Multi-mode: None Radio Bearer Management
uplink signaling data at the GSM: None Radio Bearer Management
PDCP layer in a cell UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526730563 L.Thrp.bits.UL.PDCP.SDU.QCI.1 Uplink traffic volume for Multi-mode: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025


TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526730572 L.Thrp.bits.UL.PDCP.SDU Total uplink traffic volume Multi-mode: None Radio Bearer Management
for PDCP SDUs in a cell GSM: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526730573 L.Thrp.bits.DL.PDCP.PDU.QCI.1 Downlink traffic volume for Multi-mode: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008


LBFD-002025
TDLBFD-002025
1526730582 L.Thrp.bits.DL.PDCP.PDU Total downlink traffic Multi-mode: None Radio Bearer Management
volume of PDCP PDUs in a GSM: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526730589 L.Traffic.User.Ulsync.Avg.PLMN Average number of UL Multi-mode: None RRC Connection

synchronized users for a GSM: None Management
specific operator in a cell UMTS: None RRC Connection
Common Carrier
LOFD-001036
RAN Sharing with
TDLOFD-001036
Common Carrier
LOFD-001037
RAN Sharing with
Hybrid RAN Sharing
Operator Load Based
Intra-LTE MLB
1526730600 L.Traffic.ActiveUser.DL.QCI.Total.Max Maximum number of Multi-mode: None RRC Connection

activated UEs with a QCI GSM: None Management
(or an extended QCI) in the UMTS: None RRC Connection
downlink buffer Management
LTE: LBFD-002007
TDLBFD-002007
1526730601 L.Traffic.ActiveUser.DL.QCI.1.Max Maximum number of Multi-mode: None RRC Connection

activated UEs with the QCI GSM: None Management
of 1 in the downlink buffer UMTS: None RRC Connection
TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007


1526730610 L.Traffic.ActiveUser.UL.QCI.Total.Max Maximum number of Multi-mode: None RRC Connection
activated UEs with a QCI GSM: None Management
(or an extended QCI) in the UMTS: None RRC Connection
uplink buffer Management
LTE: LBFD-002007
TDLBFD-002007
1526730611 L.Traffic.ActiveUser.UL.QCI.1.Max Maximum number of Multi-mode: None RRC Connection

of 1 in the uplink buffer UMTS: None RRC Connection
TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007

TDLBFD-002007
1526730820 L.Traffic.DRB.Max Max number of DRBs in a Multi-mode: None Radio Bearer Management
cell GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526730821 L.Traffic.DRB.Max.QCI.1 Max number of DRBs for Multi-mode: None Radio Bearer Management
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
in a cell


UMTS: None
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
1526730830 L.E-RAB.FailEst.RNL.eNodeB.NormRel Number of E-RAB setup Multi-mode: None Radio Bearer Management
failures due to normal GSM: None Radio Bearer Management
release initiated by UMTS: None
eNodeB
LTE: LBFD-002008
TDLBFD-002008
1526730831 L.E-RAB.FailEst.RNL.eNodeB.AbnormRel Number of E-RAB setup Multi-mode: None Radio Bearer Management
failures due to abnormal GSM: None Radio Bearer Management
release initiated by UMTS: None
eNodeB
LTE: LBFD-002008
TDLBFD-002008
1526730846 L.RRC.ConnReq.Max Maximum number of RRC Multi-mode: None RRC Connection

messages received by a UMTS: None RRC Connection
cell from UEs (including the Management
LTE: LBFD-002007
discarded ones)
TDLBFD-002007
1526730857 L.RRC.ReEstFail.NoCntx.PreProcFail Number of RRC Multi-mode: None RRC Connection

failures due to UE context UMTS: None RRC Connection
unavailability caused by Management
LTE: LBFD-002007
the pre-processing failure
TDLBFD-002007
1526730862 L.E-RAB.AbnormRel.UlWeak.VoIP Number of abnormal Multi-mode: None Radio Bearer Management

because of uplink weak
LTE: LBFD-002008
coverage
TDLBFD-002008
1526730863 L.UECNTX.AbnormRel.UlWeak Number of abnormal UE Multi-mode: None Radio Bearer Management

by the eNodeB due to UMTS: None
uplink weak coverage
LTE: LBFD-002008
TDLBFD-002008
1526730864 L.E-RAB.AbnormRel.MME.QCI.2 Number of MME-triggered Multi-mode: None Radio Bearer Management

activated E-RABs for UMTS: None
LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008


TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008
1526730872 L.Traffic.Sch.UL.Num Number of times that UEs Multi-mode: None Radio Bearer Management
are scheduled in a cell in GSM: None Radio Bearer Management
the uplink UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526730873 L.Traffic.Sch.DL.Num Number of times that UEs Multi-mode: None Radio Bearer Management
are scheduled in a cell in GSM: None Radio Bearer Management
the downlink UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526730876 L.Thrp.Pkts.DL.SRB.SDU Number of downlink Multi-mode: None Radio Bearer Management

PDCP-layer signaling GSM: None Radio Bearer Management
SDUs sent in a cell UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526730877 L.Thrp.Pkts.UL.SRB.SDU Number of uplink PDCP- Multi-mode: None Radio Bearer Management
layer signaling SDUs GSM: None Radio Bearer Management
received in a cell UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526730878 L.Traffic.User.License.Avg Average licensed number Multi-mode: None RRC Connection

of UEs in GSM: None Management
RRC_CONNECTED mode UMTS: None RRC Connection
TDLBFD-002007
1526730879 L.Traffic.SGW.Rx.SDU.Bytes Number of bytes of SDUs Multi-mode: None Radio Bearer Management
that a cell receives from GSM: None Radio Bearer Management
the S-GW UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526730880 L.Traffic.SGW.Tx.SDU.Bytes Number of bytes of SDUs Multi-mode: None Radio Bearer Management
that a cell sends to the GSM: None Radio Bearer Management
S-GW UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526730881 L.Traffic.IntereNB.Transfer.Tx.SDU.Bytes Number of bytes of SDUs Multi-mode: None Radio Bearer Management
sent to target cells during GSM: None Radio Bearer Management
inter-eNodeB handovers UMTS: None Basic Scheduling


TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526730882 L.Traffic.IntereNB.Transfer.Rx.SDU.Bytes Number of bytes of SDUs Multi-mode: None Radio Bearer Management
received from source cells GSM: None Radio Bearer Management
during inter-eNodeB UMTS: None Basic Scheduling
handovers
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526731537 L.Traffic.User.US.Avg Average number of UEs Multi-mode: None RRC Connection

running unlimited services GSM: None Management
TDLBFD-002007
1526731538 L.Traffic.User.US.Max Maximum number of UEs Multi-mode: None RRC Connection

running unlimited services GSM: None Management
TDLBFD-002007
1526732044 L.RRC.SetupFail.Rej.MMEOverload Number of times the Multi-mode: None RRC Connection

eNodeB sends an RRC GSM: None Management
Connection Reject UMTS: None RRC Connection
message to the UE due to Management
LTE: LBFD-002007
MME overload
TDLBFD-002007
1526732676 L.Traffic.User.Index0 Number of times the UE Multi-mode: None RRC Connection

quantity in a cell falls within GSM: None Management
the range indicated by UMTS: None RRC Connection
index 0 Management
LTE: LBFD-002007
TDLBFD-002007

index 1 Management
LTE: LBFD-002007
TDLBFD-002007

index 2 Management
LTE: LBFD-002007
TDLBFD-002007

index 3 Management
LTE: LBFD-002007
TDLBFD-002007

index 4 Management
LTE: LBFD-002007
TDLBFD-002007

index 5 Management
LTE: LBFD-002007
TDLBFD-002007

index 6 Management
LTE: LBFD-002007
TDLBFD-002007

index 7 Management
LTE: LBFD-002007
TDLBFD-002007

index 8 Management
LTE: LBFD-002007
TDLBFD-002007



index 9 LTE: LBFD-002007 Management
TDLBFD-002007

index 10 Management
LTE: LBFD-002007
TDLBFD-002007
1526732721 L.Traffic.User.VoIP.Avg Average number of VoIP Multi-mode: None RRC Connection

UEs in a cell GSM: None Management
TDLBFD-002007
1526732722 L.Traffic.User.VoIP.Max Maximum number of VoIP Multi-mode: None RRC Connection

TDLBFD-002007
1526732723 L.Traffic.User.TM9.Avg Average number of UEs Multi-mode: None RRC Connection

that apply TM9 in a cell GSM: None Management
TDLBFD-002007 DL 4x2 MIMO
LOFD-001003 DL 2x2 MIMO
LOFD-001060
1526732726 L.E-RAB.FailEst.Conflict.Hofail Number of E-RAB setup Multi-mode: None Radio Bearer Management
failures due to conflict with GSM: None Radio Bearer Management
intra-eNodeB handovers UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526732739 L.DLPSServ.EstDelay.Avg.Idle Average access delay for Multi-mode: None Radio Bearer Management
downlink data services GSM: None Radio Bearer Management
successfully initiated by UMTS: None Basic Scheduling
idle-mode UEs in the cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526732740 L.DLPSServ.EstDelay.Good.Num.Idle Number of times that the Multi-mode: None Radio Bearer Management
access delay for a GSM: None Radio Bearer Management
downlink data service UMTS: None Basic Scheduling
successfully initiated by an
idle-mode UE in the cell is
within the Good range TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526732741 L.DLPSServ.EstDelay.Medium.Num.Idle Number of times that the Multi-mode: None Radio Bearer Management
within the Medium range TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526732742 L.DLPSServ.EstDelay.Bad.Num.Idle Number of times that the Multi-mode: None Radio Bearer Management
within the Bad range TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526732743 L.Thrp.bits.DL.PerUser.In.Index0 Number of times that the Multi-mode: None Radio Bearer Management
downlink PS service traffic GSM: None Radio Bearer Management
in the cell is within the UMTS: None Basic Scheduling
range of (0,
DlUserThruputThd0)
TDLBFD-002008
LBFD-002025
TDLBFD-002025
range of
[DlUserThruputThd0,
DlUserThruputThd1) TDLBFD-002008
LBFD-002025
TDLBFD-002025
L.Thrp.bits.DL.PerUser.In.Index2


1526732745 Number of times that the Multi-mode: None Radio Bearer Management
range of
[DlUserThruputThd1,
LBFD-002025
TDLBFD-002025
range of
[DlUserThruputThd2,
LBFD-002025
TDLBFD-002025
range of
[DlUserThruputThd3,
LBFD-002025
TDLBFD-002025
in the cell is greater than UMTS: None Basic Scheduling
DlUserThruputThd4
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526732749 L.Thrp.bits.DL.PerUser.Out.Index0 Number of times that the Multi-mode: None Radio Bearer Management
downlink PS service GSM: None Radio Bearer Management
throughput in the cell is UMTS: None Basic Scheduling
within the range of (0,
DlUserThruputThd0)
TDLBFD-002008
LBFD-002025
TDLBFD-002025
within the range of
[DlUserThruputThd0,
LBFD-002025
TDLBFD-002025
within the range of
[DlUserThruputThd1,
LBFD-002025
TDLBFD-002025
within the range of
[DlUserThruputThd2,
LBFD-002025
TDLBFD-002025
within the range of
[DlUserThruputThd3,
LBFD-002025
TDLBFD-002025
greater than
DlUserThruputThd4
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526732755 L.Traffic.DL.EmptyBuf.PDCPLat.Num Total number of downlink Multi-mode: None Radio Bearer Management
PDCP SDUs that are for GSM: None Radio Bearer Management
DRB services and enter UMTS: None Basic Scheduling
the empty buffer in a cell
TDLBFD-002008


LBFD-002025
TDLBFD-002025
1526732756 L.Traffic.DL.EmptyBuf.PDCPLat.Num.QCI.1 Total number of downlink Multi-mode: None Radio Bearer Management
DRB services of QCI 1 and UMTS: None Basic Scheduling
enter the empty buffer in a
cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526732765 L.Traffic.DL.EmptyBuf.PDCPLat.Time Total transmission delay of Multi-mode: None Radio Bearer Management
the first PDCP SDUs of GSM: None Radio Bearer Management
DRB services in the empty UMTS: None Basic Scheduling
buffer in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526732766 L.Traffic.DL.EmptyBuf.PDCPLat.Time.QCI.1 Total transmission delay of Multi-mode: None Radio Bearer Management


DRB services of QCI 1 in UMTS: None Basic Scheduling
the empty buffer in a cell LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526732775 L.Thrp.bits.UE.UL.PL0 Total uplink throughput of Multi-mode: None Radio Bearer Management
PDCP PDUs for UEs GSM: None Radio Bearer Management
whose path loss ranges UMTS: None Basic Scheduling
within [0, 90) dB
TDLBFD-002008 Uplink Power Control
LBFD-002025 Uplink Power Control
TDLBFD-002025
LBFD-002026
TDLBFD-002026
within [90, 95) dB


TDLBFD-002025
LBFD-002026
TDLBFD-002026
within [95, 100) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
within [100, 105) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026

whose path loss is greater UMTS: None Basic Scheduling
than or equal to 135 dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
1526732786 L.Thrp.Time.UE.UL.RmvSmallPkt.PL0 Data transmission duration Multi-mode: None Radio Bearer Management
of uplink PDCP PDUs GSM: None Radio Bearer Management
(excluding small packets) UMTS: None Basic Scheduling
for UEs whose path loss
ranges within the range of
[0, 90) dB TDLBFD-002008 Uplink Power Control
TDLBFD-002025
LBFD-002026
TDLBFD-002026
ranges within [90, 95) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
within [95, 100) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026


for UEs whose path loss LTE: LBFD-002008 Basic Scheduling
ranges within [120, 125) dB TDLBFD-002008 Uplink Power Control
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
for UEs whose path loss is
greater than or equal to
135 dB TDLBFD-002008 Uplink Power Control
TDLBFD-002025
LBFD-002026
TDLBFD-002026
1526732797 L.Thrp.bits.UE.UL.SmallPkt.PL0 Throughput of small uplink Multi-mode: None Radio Bearer Management
packets at the PDCP layer GSM: None Radio Bearer Management
for UEs whose path loss UMTS: None Basic Scheduling
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025


LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
for UEs whose path loss is UMTS: None Basic Scheduling
135 dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
1526732808 L.Traffic.User.PL0 Number of UEs that Multi-mode: None Radio Bearer Management
perform services and have GSM: None Radio Bearer Management
a path loss ranging within UMTS: None Basic Scheduling
[0, 90) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
[90, 95) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
1526732810 L.Traffic.User.PL2 Multi-mode: None Radio Bearer Management


Number of UEs that GSM: None Radio Bearer Management
perform services and have UMTS: None Basic Scheduling
a path loss ranging within LTE: LBFD-002008 Basic Scheduling
[95, 100) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
[100, 105) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
[105, 110) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
[110, 115) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
[115, 120) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
[120, 125) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
[125, 130) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
[130, 135) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
[135, 138) dB


TDLBFD-002025
LBFD-002026
TDLBFD-002026
1526732920 L.RRC.SetupFail.Rej.Other Number of RRC Multi-mode: None RRC Connection

rejected due to other UMTS: None RRC Connection
causes Management
LTE: LBFD-002007
TDLBFD-002007
1526732921 L.RRC.SetupFail.ResFail.Other Number of RRC Multi-mode: None RRC Connection

due to other resource UMTS: None RRC Connection
LTE: LBFD-002007
TDLBFD-002007
1526732922 L.E-RAB.FailEst.Other Number of E-RAB setup Multi-mode: None Radio Bearer Management
failures due to other GSM: None Radio Bearer Management
reasons UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526732923 L.E-RAB.FailEst.Other.VoIP Number of setup failures of Multi-mode: None Radio Bearer Management
due to other reasons UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526732924 L.E-RAB.FailEst.RNL.Other Number of E-RAB setup Multi-mode: None Radio Bearer Management
reasons at the radio UMTS: None
network layer
LTE: LBFD-002008
TDLBFD-002008
1526732925 L.E-RAB.FailEst.RNL.Other.VoIP Number of setup failures of Multi-mode: None Radio Bearer Management
due to other reasons at the UMTS: None
radio network layer
LTE: LBFD-002008
TDLBFD-002008
1526732926 L.E-RAB.FailEst.TNL.Other Number of E-RAB setup Multi-mode: None Radio Bearer Management
reasons at the transport UMTS: None
network layer
LTE: LBFD-002008
TDLBFD-002008
1526732927 L.E-RAB.FailEst.TNL.Other.VoIP Number of setup failures of Multi-mode: None Radio Bearer Management
LTE: LBFD-002008
TDLBFD-002008
1526732928 L.E-RAB.FailEst.NoRadioRes.Other Number of E-RAB setup Multi-mode: None Radio Bearer Management
failures due to insufficiency GSM: None Radio Bearer Management
of other radio resources UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526732929 L.E-RAB.FailEst.NoRadioRes.Other.VoIP Number of setup failures of Multi-mode: None Radio Bearer Management
due to insufficiency of other UMTS: None
radio resources
LTE: LBFD-002008
TDLBFD-002008
1526732930 L.E-RAB.FailEst.Other.PLMN Number of E-RAB setup Multi-mode: None Radio Bearer Management
reasons for a specific UMTS: None
operator
LTE: LBFD-002008
TDLBFD-002008
1526732931 L.E-RAB.FailEst.Other.VoIP.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management
due to other reasons for a UMTS: None
specific operator
LTE: LBFD-002008
TDLBFD-002008
1526732932 L.E-RAB.FailEst.RNL.Other.PLMN Number of E-RAB setup Multi-mode: None Radio Bearer Management
reasons at the radio UMTS: None
network layer for a specific
LTE: LBFD-002008
operator
TDLBFD-002008
1526732933 L.E-RAB.FailEst.RNL.Other.VoIP.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management


radio network layer for a LTE: LBFD-002008
specific operator TDLBFD-002008
1526732934 L.E-RAB.FailEst.TNL.Other.PLMN Number of E-RAB setup Multi-mode: None Radio Bearer Management
reasons at the transport UMTS: None
LTE: LBFD-002008
ope
TDLBFD-002008
1526732935 L.E-RAB.FailEst.TNL.Other.VoIP.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management
transport network layer for
LTE: LBFD-002008
a specific operator
TDLBFD-002008
1526732936 L.E-RAB.FailEst.NoRadioRes.Other.PLMN Number of E-RAB setup Multi-mode: None Radio Bearer Management
failures due to insufficiency GSM: None Radio Bearer Management
of other radio resources for UMTS: None
a specific operator
LTE: LBFD-002008
TDLBFD-002008
1526732937 L.E-RAB.FailEst.NoRadioRes.Other.VoIP.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management
due to insufficiency of other UMTS: None
radio resources for a
LTE: LBFD-002008
specific operator
TDLBFD-002008
1526732938 L.E-RAB.AbnormRel.Other Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs due to other UMTS: None
reasons
LTE: LBFD-002008
TDLBFD-002008
1526732939 L.E-RAB.AbnormRel.Other.VoIP Number of abnormal Multi-mode: None Radio Bearer Management

due to other reasons
LTE: LBFD-002008
TDLBFD-002008
1526732940 L.E-RAB.AbnormRel.Radio.Other Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs due to other faults UMTS: None
at the radio network layer
LTE: LBFD-002008
TDLBFD-002008
1526732941 L.E-RAB.AbnormRel.Radio.Other.VoIP Number of abnormal Multi-mode: None Radio Bearer Management

due to other faults at the
LTE: LBFD-002008
radio network layer
TDLBFD-002008
1526732942 L.E-RAB.AbnormRel.TNL.Other Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs due to other faults UMTS: None
at the transport network lay
LTE: LBFD-002008
TDLBFD-002008
1526732943 L.E-RAB.AbnormRel.TNL.Other.VoIP Number of abnormal Multi-mode: None Radio Bearer Management

due to other faults at the
LTE: LBFD-002008
TDLBFD-002008
1526732944 L.E-RAB.AbnormRel.Cong.Other Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs due to other radio UMTS: None
resource congestion reaso
LTE: LBFD-002008
TDLBFD-002008
1526732945 L.E-RAB.AbnormRel.Cong.Other.VoIP Number of abnormal Multi-mode: None Radio Bearer Management

due to other radio resource
LTE: LBFD-002008
congestion reasons
TDLBFD-002008
1526732946 L.E-RAB.AbnormRel.Other.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

E-RABs due to other UMTS: None
reasons for a specific
LTE: LBFD-002008
operator
TDLBFD-002008
1526732947 L.E-RAB.AbnormRel.Other.VoIP.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

due to other reasons for a
LTE: LBFD-002008
specific operator
TDLBFD-002008


1526732948 L.E-RAB.AbnormRel.Radio.Other.PLMN Number of abnormal Multi-mode: None Radio Bearer Management
E-RABs because of other UMTS: None
faults at the radio network
LTE: LBFD-002008
layer for a specific operator
TDLBFD-002008
1526732949 L.E-RAB.AbnormRel.Radio.Other.VoIP.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

because of other faults at
LTE: LBFD-002008
the radio network layer for
a specific operator TDLBFD-002008
1526732950 L.E-RAB.AbnormRel.TNL.Other.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

faults at the transport
LTE: LBFD-002008
operator TDLBFD-002008
1526732951 L.E-RAB.AbnormRel.TNL.Other.VoIP.PLNM Number of abnormal Multi-mode: None Radio Bearer Management

because of other faults at
LTE: LBFD-002008
the transport network layer
for a specific operator TDLBFD-002008
1526732952 L.E-RAB.AbnormRel.Cong.Other.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

radio resource congestion
LTE: LBFD-002008
reasons for a specific
operator TDLBFD-002008
1526732953 L.E-RAB.AbnormRel.Cong.Other.VoIP.PLMN Number of abnormal Multi-mode: None Radio Bearer Management

because of other radio
LTE: LBFD-002008
resource congestion
reasons for a specific TDLBFD-002008
operator
1526733014 L.Traffic.User.Relay.Avg Average number of relay Multi-mode: None RRC Connection

TDLBFD-002007 Out of Band Relay
Introduction
TDLAOFD-080405
Out of Band Relay
LAOFD-111202
1526733199 L.Signal.Num.Nas Number of NAS messages Multi-mode: None RRC Connection

GSM: None Management
TDLBFD-002007
1526734141 L.Thrp.bits.DL.Phy Total downlink traffic Multi-mode: None Radio Bearer Management
volume at the physical GSM: None Radio Bearer Management
layer in a cell UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526734142 L.Thrp.bits.UL.Phy Total uplink traffic volume Multi-mode: None Radio Bearer Management
at the physical layer in a GSM: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526734143 L.Thrp.bits.DL.Phy.Max Maximum downlink traffic Multi-mode: None Radio Bearer Management
volume of all services at GSM: None Radio Bearer Management
the physical layer UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526734144 L.Thrp.bits.UL.Phy.Max Maximum uplink traffic Multi-mode: None Radio Bearer Management
volume of all services at GSM: None Radio Bearer Management
the physical layer UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526735160 L.E-RAB.SessionTime.UE.HighPrecision Multi-mode: None Radio Bearer Management


Total duration of UE data GSM: None Radio Bearer Management
transmission time with the UMTS: None Basic Scheduling
precision of 100 LTE: LBFD-002008 Basic Scheduling
milliseconds in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526735161 L.E-RAB.SessionTime.HighPrecision Total duration of Multi-mode: None Radio Bearer Management

transmission time for GSM: None Radio Bearer Management
services with all the QCI UMTS: None Basic Scheduling
with the precision of 100
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526735162 L.E-RAB.SessionTime.HighPrecision.QCI1 Duration of data Multi-mode: None Radio Bearer Management

with the QCI of 1 with the UMTS: None Basic Scheduling
precision of 100
TDLBFD-002008
LBFD-002025
TDLBFD-002025

precision of 100
TDLBFD-002008
LBFD-002025
TDLBFD-002025

precision of 100
TDLBFD-002008
LBFD-002025
TDLBFD-002025

precision of 100
TDLBFD-002008
LBFD-002025
TDLBFD-002025

precision of 100
TDLBFD-002008
LBFD-002025
TDLBFD-002025

precision of 100
TDLBFD-002008
LBFD-002025
TDLBFD-002025

precision of 100
TDLBFD-002008
LBFD-002025
TDLBFD-002025

precision of 100
TDLBFD-002008
LBFD-002025
TDLBFD-002025

precision of 100
TDLBFD-002008
LBFD-002025


TDLBFD-002025
1526735541 L.Traffic.ActiveUser.Relay.Avg Average number of active Multi-mode: None RRC Connection

RUEs GSM: None Management
Introduction
TDLAOFD-080405
1526735542 L.Thrp.Relay.bits.DL Total traffic volume of Multi-mode: None Radio Bearer Management
downlink PDCP SDUs GSM: None Radio Bearer Management
transmitted by active RUEs UMTS: None Basic Scheduling
in a cell
LBFD-002025 Introduction
TDLAOFD-080405
LAOFD-111202
1526735543 L.Thrp.Relay.Time.DL Total transmit duration of Multi-mode: None Radio Bearer Management
transmitted by active RUEs UMTS: None Basic Scheduling
in a cell
TDLAOFD-080405
LAOFD-111202
1526735544 L.Thrp.Relay.bits.UL Total traffic volume of Multi-mode: None Radio Bearer Management
uplink PDCP SDUs GSM: None Radio Bearer Management
received by active RUEs in UMTS: None Basic Scheduling
a cell
TDLAOFD-080405
LAOFD-111202
1526735545 L.Thrp.Relay.Time.UL Total transmit duration of Multi-mode: None Radio Bearer Management
uplink PDCP SDUs GSM: None Radio Bearer Management
received by active RUEs in UMTS: None Basic Scheduling
a cell
TDLAOFD-080405
LAOFD-111202
1526735546 L.Traffic.DL.PktDelay.Relay.Time Total processing delay of Multi-mode: None Radio Bearer Management
transmitted by RUEs in a UMTS: None Basic Scheduling
cell
TDLAOFD-080405
LAOFD-111202
1526735547 L.Traffic.DL.PktDelay.Relay.Num Number of downlink PDCP Multi-mode: None Radio Bearer Management
SDUs successfully GSM: None Radio Bearer Management
transmitted by RUEs in a UMTS: None Basic Scheduling
cell
TDLAOFD-080405
LAOFD-111202
1526735548 L.Traffic.UL.PktLoss.Relay.Loss Number of uplink PDCP Multi-mode: None Radio Bearer Management
SDUs discarded by RUEs GSM: None Radio Bearer Management
in a cell UMTS: None Basic Scheduling
TDLAOFD-080405
LAOFD-111202
1526735549 L.Traffic.UL.PktLoss.Relay.Tot Number of uplink PDCP Multi-mode: None Radio Bearer Management
PDUs expected to be GSM: None Radio Bearer Management
received by RUEs in a cell UMTS: None Basic Scheduling
TDLBFD-002008


LBFD-002025 Out of Band Relay
TDLBFD-002025 Introduction
TDLAOFD-080405 Out of Band Relay
LAOFD-111202
1526735568 L.Thrp.bits.DL.PDCP.Send Total PDCP-layer traffic Multi-mode: None Radio Bearer Management
volume of to-be-transmitted GSM: None Radio Bearer Management
downlink data in a cell UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526735569 L.Thrp.bits.DL.PDCP.Discard Total PDCP-layer traffic Multi-mode: None Radio Bearer Management
volume of discarded to-be- GSM: None Radio Bearer Management
transmitted downlink data UMTS: None Basic Scheduling
in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526735570 L.Thrp.bits.DL.RLC.Send Total RLC-layer traffic Multi-mode: None Radio Bearer Management
volume of downlink data in GSM: None Radio Bearer Management
a cell UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526735571 L.Thrp.bits.UL.RLC.Send Total RLC-layer traffic Multi-mode: None Radio Bearer Management
volume of uplink data in a GSM: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526735572 L.Thrp.bits.UL.PDCP.Discard Total PDCP-layer traffic Multi-mode: None Radio Bearer Management
volume of discarded uplink GSM: None Radio Bearer Management
data in a cell UMTS: None Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526735573 L.Thrp.bits.UL.PDCP.Send Total PDCP-layer traffic Multi-mode: None Radio Bearer Management
volume of uplink data in a GSM: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526736680 L.PDCP.Tx.Disc.Trf.SDU.PLMN.QCI.1 Number of downlink traffic Multi-mode: None Radio Bearer Management
SDUs discarded by the GSM: None Radio Bearer Management
PDCP layer for services UMTS: None Basic Scheduling
with a QCI of 1 for a
Dedicated Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526736681 L.PDCP.Tx.Disc.Trf.SDU.PLMN.QCI.5 Number of downlink traffic Multi-mode: None Radio Bearer Management
SDUs discarded by the GSM: None Radio Bearer Management
PDCP layer for services UMTS: None Basic Scheduling
Dedicated Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526736682 L.PDCP.Tx.TotRev.Trf.SDU.PLMN.QCI.1 Number of transmitted Multi-mode: None Radio Bearer Management

downlink traffic PDCP GSM: None Radio Bearer Management
SDUs for services with a UMTS: None Basic Scheduling
QCI of 1 for a specific
operator in a cell


Dedicated Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526736683 L.PDCP.Tx.TotRev.Trf.SDU.PLMN.QCI.5 Number of transmitted Multi-mode: None Radio Bearer Management

downlink traffic PDCP GSM: None Radio Bearer Management
SDUs for services with a UMTS: None Basic Scheduling
QCI of 5 for a specific
operator in a cell
Dedicated Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526736684 L.Traffic.UL.PktLoss.Loss.PLMN.QCI.1 Total number of discarded Multi-mode: None Radio Bearer Management
uplink PDCP SDUs for GSM: None Radio Bearer Management
traffic services with a QCI UMTS: None Basic Scheduling
of 1 for a specific operator
in a cell
Dedicated Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526736685 L.Traffic.UL.PktLoss.Loss.PLMN.QCI.5 Total number of discarded Multi-mode: None Radio Bearer Management
in a cell
Dedicated Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526736686 L.Traffic.UL.PktLoss.Tot.PLMN.QCI.1 Total number of expected Multi-mode: None Radio Bearer Management
uplink data packets for GSM: None Radio Bearer Management
DRB services with a QCI of UMTS: None Basic Scheduling
1 for a specific operator in
a cell
Dedicated Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526736687 L.Traffic.UL.PktLoss.Tot.PLMN.QCI.5 Total number of expected Multi-mode: None Radio Bearer Management
uplink data packets for GSM: None Radio Bearer Management
a cell
Dedicated Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526736688 L.Traffic.DL.PktDelay.Num.PLMN.QCI.1 Number of successfully Multi-mode: None Radio Bearer Management

TDLBFD-002025


Dedicated Carrier
Hybrid RAN Sharing
1526736689 L.Traffic.DL.PktDelay.Num.PLMN.QCI.5 Number of successfully Multi-mode: None Radio Bearer Management

Dedicated Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526736690 L.Traffic.DL.PktDelay.Time.PLMN.QCI.5 Total processing delay of Multi-mode: None Radio Bearer Management
a cell
Dedicated Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526736691 L.Traffic.DL.PktDelay.Time.PLMN.QCI.1 Total processing delay of Multi-mode: None Radio Bearer Management
a cell
Dedicated Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526736692 L.Traffic.User.VoIP.Avg.PLMN Average number of VoIP Multi-mode: None RRC Connection

UEs of a specific operator GSM: None Management
in a cell UMTS: None RRC Connection
Common Carrier
LOFD-001036
RAN Sharing with
TDLOFD-001036
Common Carrier
LOFD-001037
RAN Sharing with
Dedicated Carrier
Hybrid RAN Sharing
1526736693 L.Traffic.User.VoIP.Max.PLMN Maximum number of VoIP Multi-mode: None RRC Connection

UEs of a specific operator GSM: None Management
in a cell UMTS: None RRC Connection
Common Carrier
LOFD-001036
RAN Sharing with
TDLOFD-001036
Common Carrier
LOFD-001037
RAN Sharing with
Dedicated Carrier
Hybrid RAN Sharing
1526736694 L.E-RAB.FailEst.NoRadioRes.DLSatis.QCI2 Number of setup failures of Multi-mode: None Radio Bearer Management
E-RABs with a QCI of 2 GSM: None Radio Bearer Management
satisfaction rate
TDLBFD-002008
TDLBFD-002023
LBFD-002023
E-RABs with a QCI of 3


because of a low downlink GSM: None Radio Bearer Management
satisfaction rate UMTS: None Admission Control
TDLBFD-002008
TDLBFD-002023
LBFD-002023
satisfaction rate
TDLBFD-002008
TDLBFD-002023
LBFD-002023
1526736697 L.E-RAB.FailEst.NoRadioRes.ULSatis.QCI2 Number of setup failures of Multi-mode: None Radio Bearer Management
satisfaction rate
TDLBFD-002008
TDLBFD-002023
LBFD-002023
satisfaction rate
TDLBFD-002008
TDLBFD-002023
LBFD-002023
satisfaction rate
TDLBFD-002008
TDLBFD-002023
LBFD-002023
1526736700 L.E-RAB.FailEst.NoRadioRes.DLSatis.QCI2.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management
specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526736703 L.E-RAB.FailEst.NoRadioRes.ULSatis.QCI2.PLMN Number of setup failures of Multi-mode: None Radio Bearer Management
specific operator
TDLBFD-002008


Common Carrier
TDLOFD-001037
RAN Sharing with
LOFD-070206
Dedicated Carrier
Hybrid RAN Sharing
specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
specific operator
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526736737 L.Traffic.DL.PktUuLoss.Loss.PLMN.QCI.1 Total number of discarded Multi-mode: None Radio Bearer Management
in a cell
Dedicated Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526736738 L.Traffic.DL.PktUuLoss.Loss.PLMN.QCI.5 Total number of discarded Multi-mode: None Radio Bearer Management
in a cell
Dedicated Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526736739 L.Traffic.DL.PktUuLoss.Tot.PLMN.QCI.1 Total number of expected Multi-mode: None Radio Bearer Management
downlink data packets for GSM: None Radio Bearer Management
a cell
Dedicated Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001037
Dedicated Carrier
LOFD-070206
Hybrid RAN Sharing
1526736740 L.Traffic.DL.PktUuLoss.Tot.PLMN.QCI.5 Total number of expected Multi-mode: None Radio Bearer Management
downlink data packets for GSM: None Radio Bearer Management
a cell
TDLBFD-002025


Dedicated Carrier
Hybrid RAN Sharing
1526736788 L.Traffic.eNodeB.User.Ulsync.Max Maximum number of UL- Multi-mode: None RRC Connection

sync UEs in an eNodeB GSM: None Management
TDLBFD-002007
1526736789 L.Traffic.Board.User.Ulsync.Max Maximum number of UL- Multi-mode: None RRC Connection

sync UEs served by a BBP GSM: None Management
TDLBFD-002007
1526736790 L.Traffic.User.Ulsync.Max Maximum number of UL- Multi-mode: None RRC Connection

sync UEs in a cell GSM: None Management
TDLBFD-002007
1526736791 L.Traffic.DL.PktDelay.Time Total downlink packet Multi-mode: None Radio Bearer Management
processing delay of DRB GSM: None Radio Bearer Management
services with all QCIs UMTS: None Basic Scheduling
(including extended QCIs)
in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526736792 L.Traffic.DL.PktDelay.Num Total number of Multi-mode: None Radio Bearer Management

successfully transmitted GSM: None Radio Bearer Management
downlink PDCP SDUs for UMTS: None Basic Scheduling
DRB services with all QCIs
(including extended QCIs)
in a cell TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526736793 L.Traffic.DL.PktUuLoss.Loss Total number of downlink Multi-mode: None Radio Bearer Management
PDCP SDUs discarded for GSM: None Radio Bearer Management
with all QCIs (including the
QCI for PTT services and
extended QCIs) in a cell TDLBFD-002008
over the Uu interface LBFD-002025
TDLBFD-002025
1526736794 L.Traffic.DL.PktUuLoss.Tot Total number of downlink Multi-mode: None Radio Bearer Management
PDCP SDUs transmitted GSM: None Radio Bearer Management
for services carried on UMTS: None Basic Scheduling
DRBs with all QCIs
(including the QCI for PTT
services and extended TDLBFD-002008
QCIs) in a cell over the Uu LBFD-002025
interface TDLBFD-002025
1526736795 L.Traffic.UL.PktLoss.Loss Total number of uplink Multi-mode: None Radio Bearer Management
LBFD-002025
TDLBFD-002025
1526736796 L.Traffic.UL.PktLoss.Tot Total number of expected Multi-mode: None Radio Bearer Management
LBFD-002025
TDLBFD-002025
1526736797 L.PDCP.Tx.Disc.Trf.SDU Total number of downlink Multi-mode: None Radio Bearer Management
LBFD-002025
TDLBFD-002025
1526736798 L.PDCP.Tx.TotRev.Trf.SDU Number of downlink PDCP Multi-mode: None Radio Bearer Management


QCI for PTT services and TDLBFD-002008
extended QCIs) in a cell LBFD-002025
TDLBFD-002025
1526736799 L.Traffic.DL.Volume.QCI1.Samp.Index0 Number of samples with Multi-mode: None Radio Bearer Management
the downlink traffic volume GSM: None Radio Bearer Management
of E-RABs with a QCI of 1 UMTS: None
within range 0
LTE: LBFD-002008
TDLBFD-002008
within range 1
LTE: LBFD-002008
TDLBFD-002008
within range 2
LTE: LBFD-002008
TDLBFD-002008
within range 3
LTE: LBFD-002008
TDLBFD-002008
within range 4
LTE: LBFD-002008
TDLBFD-002008
within range 5
LTE: LBFD-002008
TDLBFD-002008
within range 6
LTE: LBFD-002008
TDLBFD-002008
within range 7
LTE: LBFD-002008
TDLBFD-002008
1526736807 L.Traffic.DL.Volume.QCI2~4.Samp.Index0 Number of samples with Multi-mode: None Radio Bearer Management
to 4 within range 0
LTE: LBFD-002008
TDLBFD-002008
to 4 within range 1
LTE: LBFD-002008
TDLBFD-002008
to 4 within range 2
LTE: LBFD-002008
TDLBFD-002008
to 4 within range 3
LTE: LBFD-002008
TDLBFD-002008
to 4 within range 4
LTE: LBFD-002008
TDLBFD-002008
to 4 within range 5
LTE: LBFD-002008


TDLBFD-002008
to 4 within range 6
LTE: LBFD-002008
TDLBFD-002008
to 4 within range 7
LTE: LBFD-002008
TDLBFD-002008
to 9 within range 0
LTE: LBFD-002008
TDLBFD-002008
to 9 within range 1
LTE: LBFD-002008
TDLBFD-002008
to 9 within range 2
LTE: LBFD-002008
TDLBFD-002008
to 9 within range 3
LTE: LBFD-002008
TDLBFD-002008
to 9 within range 4
LTE: LBFD-002008
TDLBFD-002008
to 9 within range 5
LTE: LBFD-002008
TDLBFD-002008
to 9 within range 6
LTE: LBFD-002008
TDLBFD-002008
to 9 within range 7
LTE: LBFD-002008
TDLBFD-002008
1526736823 L.Traffic.UL.Volume.QCI1.Samp.Index0 Number of samples with Multi-mode: None Radio Bearer Management
the uplink traffic volume of GSM: None Radio Bearer Management
E-RABs with a QCI of 1 UMTS: None
within range 0
LTE: LBFD-002008
TDLBFD-002008
within range 1
LTE: LBFD-002008
TDLBFD-002008
within range 2
LTE: LBFD-002008
TDLBFD-002008
within range 3
LTE: LBFD-002008
TDLBFD-002008
1526736827 L.Traffic.UL.Volume.QCI1.Samp.Index4 Multi-mode: None Radio Bearer Management


the uplink traffic volume of UMTS: None
E-RABs with a QCI of 1 LTE: LBFD-002008
within range 4
TDLBFD-002008
within range 5
LTE: LBFD-002008
TDLBFD-002008
within range 6
LTE: LBFD-002008
TDLBFD-002008
within range 7
LTE: LBFD-002008
TDLBFD-002008
1526736831 L.Traffic.UL.Volume.QCI2~4.Samp.Index0 Number of samples with Multi-mode: None Radio Bearer Management
E-RABs with a QCI of 2 to UMTS: None
4 within range 0
LTE: LBFD-002008
TDLBFD-002008
4 within range 1
LTE: LBFD-002008
TDLBFD-002008
4 within range 2
LTE: LBFD-002008
TDLBFD-002008
4 within range 3
LTE: LBFD-002008
TDLBFD-002008
4 within range 4
LTE: LBFD-002008
TDLBFD-002008
4 within range 5
LTE: LBFD-002008
TDLBFD-002008
4 within range 6
LTE: LBFD-002008
TDLBFD-002008
4 within range 7
LTE: LBFD-002008
TDLBFD-002008
9 within range 0
LTE: LBFD-002008
TDLBFD-002008
9 within range 1
LTE: LBFD-002008
TDLBFD-002008
9 within range 2


LTE: LBFD-002008
TDLBFD-002008
9 within range 3
LTE: LBFD-002008
TDLBFD-002008
9 within range 4
LTE: LBFD-002008
TDLBFD-002008
9 within range 5
LTE: LBFD-002008
TDLBFD-002008
9 within range 6
LTE: LBFD-002008
TDLBFD-002008
9 within range 7
LTE: LBFD-002008
TDLBFD-002008
1526736847 L.E-RAB.SuccEst.QCI.PTT Number of successful Multi-mode: None Radio Bearer Management

UEs for PTT services UMTS: None Enhanced QoS for MCPTT
LTE: LBFD-002008 Enhanced Extended QCI
TDLBFD-002008 (Trial)
LOFD-081218
TDLOFD-110230
1526736848 L.E-RAB.AttEst.QCI.PTT Number of E-RAB setup Multi-mode: None Radio Bearer Management
for PTT services UMTS: None Enhanced QoS for MCPTT
LOFD-081218
TDLOFD-110230
1526736849 L.E-RAB.InitAttEst.QCI.PTT Number of initial E-RAB Multi-mode: None Radio Bearer Management
LOFD-081218
TDLOFD-110230
1526736850 L.E-RAB.InitSuccEst.QCI.PTT Number of successful initial Multi-mode: None Radio Bearer Management
LOFD-081218
TDLOFD-110230
1526736853 L.E-RAB.AbnormRel.QCI.PTT Number of abnormal Multi-mode: None Radio Bearer Management

PTT services UMTS: None Enhanced QoS for MCPTT
LOFD-081218
TDLOFD-110230
1526736854 L.PDCP.Tx.TotRev.Trf.SDU.QCI.PTT Number of downlink PDCP Multi-mode: None Radio Bearer Management
SDUs transmitted for PTT GSM: None Radio Bearer Management
services in a cell UMTS: None Basic Scheduling
TDLBFD-002008 Enhanced QoS for MCPTT
LBFD-002025 Enhanced Extended QCI
LOFD-081218
TDLOFD-110230
1526736855 L.Traffic.UL.PktLoss.Loss.QCI.PTT Number of uplink PDCP Multi-mode: None Radio Bearer Management
SDUs discarded for PTT GSM: None Radio Bearer Management
services in a cell


TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526736856 L.E-RAB.FailEst.NoRadioRes.DLSatis.PTT Number of E-RAB setup Multi-mode: None Radio Bearer Management
failures for PTT services GSM: None Radio Bearer Management
satisfaction rate
LOFD-081218
TDLOFD-110230
1526736857 L.E-RAB.FailEst.NoRadioRes.ULSatis.PTT Number of setup failures of Multi-mode: None Radio Bearer Management
E-RABs for PTT services GSM: None Radio Bearer Management
satisfaction rate
LOFD-081218
TDLOFD-110230
1526736858 L.E-RAB.NormRel.QCI.PTT Number of normal E-RAB Multi-mode: None Radio Bearer Management
releases for PTT services GSM: None Radio Bearer Management
in a cell UMTS: None Enhanced QoS for MCPTT
LOFD-081218
TDLOFD-110230
1526736861 L.PDCP.Tx.Disc.Trf.SDU.QCI.PTT Number of downlink PDCP Multi-mode: None Radio Bearer Management
SDUs discarded for PTT GSM: None Radio Bearer Management
LOFD-081218
TDLOFD-110230
1526736862 L.Traffic.UL.PktLoss.Tot.QCI.PTT Number of expected uplink Multi-mode: None Radio Bearer Management
PDCP SDUs for PTT GSM: None Radio Bearer Management
LBFD-002025
TDLBFD-002025
LOFD-081218
1526736863 L.UECNTX.Rel.MME.AbnormRel.Act Number of MME-initiated Multi-mode: None Radio Bearer Management

activated UE context UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526736864 L.UECNTX.AbnormRel.Act Number of eNodeB- Multi-mode: None Radio Bearer Management

initiated abnormal releases GSM: None Radio Bearer Management
of activated UE context UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526736879 L.E-RAB.AbnormRel.MME.HOOut.QCI.1 Number of MME-initiated Multi-mode: None Radio Bearer Management

E-RABs for services with a UMTS: None
QCI of 1 during handover
LTE: LBFD-002008
executions
TDLBFD-002008

LTE: LBFD-002008
executions
TDLBFD-002008

LTE: LBFD-002008
executions
TDLBFD-002008



QCI of 4 during handover LTE: LBFD-002008
executions TDLBFD-002008

LTE: LBFD-002008
executions
TDLBFD-002008

LTE: LBFD-002008
executions
TDLBFD-002008

LTE: LBFD-002008
executions
TDLBFD-002008

LTE: LBFD-002008
executions
TDLBFD-002008

LTE: LBFD-002008
executions
TDLBFD-002008
1526736888 L.E-RAB.AbnormRel.MME.HOOut Total number of MME- Multi-mode: None Radio Bearer Management
initiated abnormal releases GSM: None Radio Bearer Management
of E-RABs during handover UMTS: None
executions
LTE: LBFD-002008
TDLBFD-002008
1526737750 L.UECNTXRel.S1SCTPFault.Num Number of UE context Multi-mode: None Radio Bearer Management

releases because of S1 GSM: None Radio Bearer Management
SCTP link disconnection UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526737847 L.UECNTX.Rel.eNodeB.InitAttEst.MMENoReply Number of UE context Multi-mode: None Radio Bearer Management

releases triggered by GSM: None Radio Bearer Management
expiration of initial context UMTS: None
setup requests
LTE: LBFD-002008
TDLBFD-002008
1526737848 L.E-RAB.Rel.eNodeB.Userinact Number of eNodeB- Multi-mode: None Radio Bearer Management

triggered E-RAB releases GSM: None Radio Bearer Management
with the cause value of UMTS: None
User Inactivity
LTE: LBFD-002008
TDLBFD-002008
1526737849 L.Traffic.DL.PktUuLoss.Loss.QCI.PTT Total number of downlink Multi-mode: None Radio Bearer Management
PTT services in a cell over UMTS: None Basic Scheduling
the Uu interface
LOFD-081218
TDLOFD-110230
1526737850 L.Traffic.DL.PktUuLoss.Tot.QCI.PTT Number of downlink PDCP Multi-mode: None Radio Bearer Management
SDUs transmitted for PTT GSM: None Radio Bearer Management
services in a cell over the UMTS: None Basic Scheduling
Uu interface
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526737851 L.Traffic.User.InSession.Avg Average number of UEs Multi-mode: None RRC Connection

with service data to be GSM: None Management
transmitted in a cell UMTS: None RRC Connection
TDLBFD-002007
1526737852 L.Traffic.User.InSession.Max Maximum number of UEs Multi-mode: None RRC Connection

with service data to be GSM: None Management
transmitted in a cell UMTS: None RRC Connection


TDLBFD-002007
1526737854 L.RRC.ReEstFail.Disc.FlowCtrl Number of times the RRC Multi-mode: None RRC Connection
Connection GSM: None Management
Reestablishment Request UMTS: None RRC Connection
messages are discarded Management
LTE: LBFD-002007
due to flow control
TDLBFD-002007
1526739720 L.UECNTX.Rel.MME.AbnormRel Number of MME-initiated Multi-mode: None Radio Bearer Management

abnormal releases of UE GSM: None Radio Bearer Management
context UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526739721 L.UECNTX.Rel.MME.AbnormRel.Init Number of MME-initiated Multi-mode: None Radio Bearer Management

abnormal releases of UE GSM: None Radio Bearer Management
context that is not triggered UMTS: None
to set up
LTE: LBFD-002008
TDLBFD-002008
1526739724 L.Traffic.User.Sample.Num Number of times the Multi-mode: None RRC Connection

number of UEs in GSM: None Management
RRC_CONNECTED mode UMTS: None RRC Connection
is not zero Management
LTE: LBFD-002007
TDLBFD-002007
1526739740 L.E-RAB.FailEst.X2AP Number of E-RAB setup Multi-mode: None Radio Bearer Management
conflicts with X2AP-related UMTS: None
procedures
LTE: LBFD-002008
TDLBFD-002008
1526739741 L.E-RAB.FailEst.X2AP.VoIP Number of voice-service Multi-mode: None Radio Bearer Management

E-RAB setup failures GSM: None Radio Bearer Management
because of conflicts with UMTS: None
X2AP-related procedures
LTE: LBFD-002008
TDLBFD-002008
1526739788 L.Traffic.UL.PktDisorderLoss.Loss.QCI.1 Number of uplink PDCP Multi-mode: None Radio Bearer Management
SDUs of QCI 1 discarded GSM: None Radio Bearer Management
because of SN disorder or UMTS: None Basic Scheduling
changes in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526740440 L.Thrp.bits.DL.LastTTI.CAUser Downlink PDCP-layer Multi-mode: None Radio Bearer Management

traffic volume of CA UEs GSM: None Radio Bearer Management
sent in the last TTI before UMTS: None Basic Scheduling
the buffer is empty
TDLBFD-002008 LTE-A Introduction
LBFD-002025
TDLBFD-002025
LAOFD-001001
1526740441 L.Thrp.Time.DL.RmvLastTTI.CAUser Data transmission duration Multi-mode: None Radio Bearer Management
for CA UEs except the last GSM: None Radio Bearer Management
TTI before the buffer is UMTS: None Basic Scheduling
empty
TDLBFD-002008 LTE-A Introduction
LBFD-002025
TDLBFD-002025
LAOFD-001001
1526740479 L.Traffic.DL.AM.Retrans.SpecificSRB.TxPackets Number of downlink Multi-mode: None Radio Bearer Management

SpecificSRB PDUs GSM: None Radio Bearer Management
retransmitted in ARQ mode UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526741753 L.Traffic.Board.User.Max Maximum number of UEs Multi-mode: None RRC Connection

served by a BBP GSM: None Management
TDLBFD-002007
1526741780 L.E-RAB.AttEst.ExtQCI.Index0 Number of E-RAB setup Multi-mode: None Radio Bearer Management
attempts for services with GSM: None Radio Bearer Management
an extended QCI of UMTS: None Extended-QCI
counter index 0
LTE: LBFD-002008 Extended-QCI
TDLBFD-002008
LBFD-002032
TDLBFD-002032


counter index 1 LTE: LBFD-002008 Extended-QCI
TDLBFD-002008
LBFD-002032
TDLBFD-002032
counter index 2
TDLBFD-002008
LBFD-002032
TDLBFD-002032
an extended QCI of UMTS: None Radio Bearer Management
counter index 3
LTE: LBFD-002008 Radio Bearer Management
TDLBFD-002008
LBFD-002008
TDLBFD-002008
counter index 4
TDLBFD-002008
LBFD-002032
TDLBFD-002032
1526741785 L.E-RAB.SuccEst.ExtQCI.Index0 Number of successful Multi-mode: None Radio Bearer Management

E-RAB setups for services GSM: None Radio Bearer Management
with an extended QCI of UMTS: None Extended-QCI
counter index 0
TDLBFD-002008
LBFD-002032
TDLBFD-002032

counter index 1
TDLBFD-002008
LBFD-002032
TDLBFD-002032

counter index 2
TDLBFD-002008
LBFD-002032
TDLBFD-002032

counter index 3
TDLBFD-002008
LBFD-002032
TDLBFD-002032

counter index 4
TDLBFD-002008
LBFD-002032
TDLBFD-002032
1526741790 L.E-RAB.AbnormRel.ExtQCI.Index0 Number of abnormal Multi-mode: None Radio Bearer Management

services with an extended UMTS: None Extended-QCI
QCI of counter index 0
TDLBFD-002008
LBFD-002032
TDLBFD-002032

TDLBFD-002008
LBFD-002032
TDLBFD-002032


TDLBFD-002008
LBFD-002032
TDLBFD-002032

TDLBFD-002008
LBFD-002032
TDLBFD-002032

TDLBFD-002008
LBFD-002032
TDLBFD-002032
1526741795 L.E-RAB.NormRel.ExtQCI.Index0 Number of normal E-RAB Multi-mode: None Radio Bearer Management
counter index 0
TDLBFD-002008
LBFD-002032
TDLBFD-002032
counter index 1
TDLBFD-002008
LBFD-002032
TDLBFD-002032
counter index 2
TDLBFD-002008
LBFD-002032
TDLBFD-002032
counter index 3
TDLBFD-002008
LBFD-002032
TDLBFD-002032
counter index 4
TDLBFD-002008
LBFD-002032
TDLBFD-002032
1526741802 L.RRC.NoCntxReEst.Att Number of RRC Multi-mode: None RRC Connection

attempts without UE UMTS: None RRC Connection
contexts Management
LTE: LBFD-002007
TDLBFD-002007
1526741803 L.RRC.NoCntxReEst.ReconfFail.Att Number of RRC Multi-mode: None RRC Connection

contexts triggered by Management
LTE: LBFD-002007
reconfiguration failures
TDLBFD-002007
1526741804 L.RRC.NoCntxReEst.HoFail.Att Number of RRC Multi-mode: None RRC Connection

contexts triggered by Management
LTE: LBFD-002007
handover failures
TDLBFD-002007
1526741805 L.RRC.NoCntxReEst.Succ Number of successful RRC Multi-mode: None RRC Connection

UMTS: None


reestablishments without LTE: LBFD-002007 RRC Connection
UE contexts TDLBFD-002007 Management
1526741806 L.RRC.NoCntxReEst.ReconfFail.Succ Number of successful RRC Multi-mode: None RRC Connection

reestablishments without UMTS: None RRC Connection
UE contexts triggered by Management
LTE: LBFD-002007
reconfiguration failures
TDLBFD-002007
1526741807 L.RRC.NoCntxReEst.HoFail.Succ Number of successful RRC Multi-mode: None RRC Connection

reestablishments without UMTS: None RRC Connection
UE contexts triggered by Management
LTE: LBFD-002007
handover failures
TDLBFD-002007
1526741808 L.RRC.NoCntxReEstFail.Rej Number of rejected RRC Multi-mode: None RRC Connection

contexts Management
LTE: LBFD-002007
TDLBFD-002007
1526741809 L.RRC.NoCntxReEstFail.ResFail Number of rejected RRC Multi-mode: None RRC Connection

contexts due to resource Management
LTE: LBFD-002007
allocation failures
TDLBFD-002007
1526741810 L.RRC.NoCntxReEstFail.NoReply Number of rejected RRC Multi-mode: None RRC Connection

contexts due to no Management
LTE: LBFD-002007
responses from Ues
TDLBFD-002007
1526741811 L.Thrp.bits.UL.ExtQCI.Index0 Uplink traffic volume of Multi-mode: None Radio Bearer Management
with an extended QCI of UMTS: None Basic Scheduling
counter index 0
TDLBFD-002008 Extended-QCI
LBFD-002025 Extended-QCI
TDLBFD-002025
LBFD-002032
TDLBFD-002032
counter index 1
TDLBFD-002025
LBFD-002032
TDLBFD-002032
counter index 2
TDLBFD-002025
LBFD-002032
TDLBFD-002032
counter index 3
TDLBFD-002025
LBFD-002032
TDLBFD-002032
counter index 4
TDLBFD-002025
LBFD-002032
TDLBFD-002032
1526741816 L.Thrp.Time.UL.ExtQCI.Index0 Uplink PDCP-layer Multi-mode: None Radio Bearer Management

transmission duration of GSM: None Radio Bearer Management


services with an extended UMTS: None Basic Scheduling
QCI of counter index 0 LTE: LBFD-002008 Basic Scheduling
TDLBFD-002025
LBFD-002032
TDLBFD-002032

TDLBFD-002025
LBFD-002032
TDLBFD-002032

TDLBFD-002025
LBFD-002032
TDLBFD-002032

TDLBFD-002025
LBFD-002032
TDLBFD-002032

TDLBFD-002025
LBFD-002032
TDLBFD-002032
1526741821 L.Thrp.bits.DL.ExtQCI.Index0 Downlink traffic volume of Multi-mode: None Radio Bearer Management
counter index 0
TDLBFD-002025
LBFD-002032
TDLBFD-002032
counter index 1
TDLBFD-002025
LBFD-002032
TDLBFD-002032
counter index 2
TDLBFD-002025
LBFD-002032
TDLBFD-002032
counter index 3


TDLBFD-002025
LBFD-002032
TDLBFD-002032
counter index 4
TDLBFD-002025
LBFD-002032
TDLBFD-002032
1526741826 L.Thrp.Time.DL.ExtQCI.Index0 Downlink PDCP-layer Multi-mode: None Radio Bearer Management

TDLBFD-002025
LBFD-002032
TDLBFD-002032

TDLBFD-002025
LBFD-002032
TDLBFD-002032

TDLBFD-002025
LBFD-002032
TDLBFD-002032

TDLBFD-002025
LBFD-002032
TDLBFD-002032

TDLBFD-002025
LBFD-002032
TDLBFD-002032
1526741831 L.Traffic.ActiveUser.UL.ExtQCI.Index0 Number of activated UEs Multi-mode: None Radio Bearer Management
with an extended QCI of GSM: None Radio Bearer Management
counter index 0 in the UMTS: None Basic Scheduling
uplink
TDLBFD-002025
LBFD-002032
TDLBFD-002032
uplink
TDLBFD-002025
LBFD-002032
TDLBFD-002032


uplink
TDLBFD-002025
LBFD-002032
TDLBFD-002032
uplink
TDLBFD-002025
LBFD-002032
TDLBFD-002032
uplink
TDLBFD-002025
LBFD-002032
TDLBFD-002032
1526741836 L.Traffic.ActiveUser.DL.ExtQCI.Index0 Number of activated UEs Multi-mode: None Radio Bearer Management
downlink
TDLBFD-002025
LBFD-002032
TDLBFD-002032
downlink
TDLBFD-002025
LBFD-002032
TDLBFD-002032
downlink
TDLBFD-002025
LBFD-002032
TDLBFD-002032
downlink
TDLBFD-002025
LBFD-002032
TDLBFD-002032
downlink
TDLBFD-002025
LBFD-002032
TDLBFD-002032
1526741845 L.S1Sig.ConnEst.Att.Emc Number of S1 signaling Multi-mode: None Radio Bearer Management

connection setup attempts GSM: None Radio Bearer Management
for the cause of UMTS: None
"emergency"
LTE: LBFD-002008


TDLBFD-002008
1526741846 L.S1Sig.ConnEst.Att.HighPri Number of S1 signaling Multi-mode: None Radio Bearer Management

"highPriorityAccess"
LTE: LBFD-002008
TDLBFD-002008
1526741847 L.S1Sig.ConnEst.Att.Mt Number of S1 signaling Multi-mode: None Radio Bearer Management

for the cause of "mt- UMTS: None
Access"
LTE: LBFD-002008
TDLBFD-002008
1526741848 L.S1Sig.ConnEst.Att.MoSig Number of S1 signaling Multi-mode: None Radio Bearer Management

for the cause of "mo- UMTS: None
Signalling"
LTE: LBFD-002008
TDLBFD-002008
1526741849 L.S1Sig.ConnEst.Att.MoData Number of S1 signaling Multi-mode: None Radio Bearer Management

for the cause of "mo-Data" UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526741850 L.S1Sig.ConnEst.Att.DelayTol Number of S1 signaling Multi-mode: None Radio Bearer Management

"delayTolerantAccess-
LTE: LBFD-002008
v1020"
TDLBFD-002008
1526741851 L.S1Sig.ConnEst.Succ.Emc Number of successful S1 Multi-mode: None Radio Bearer Management

signaling connection GSM: None Radio Bearer Management
setups for the cause of UMTS: None
"emergency"
LTE: LBFD-002008
TDLBFD-002008
1526741852 L.S1Sig.ConnEst.Succ.HighPri Number of successful S1 Multi-mode: None Radio Bearer Management

"highPriorityAccess"
LTE: LBFD-002008
TDLBFD-002008
1526741853 L.S1Sig.ConnEst.Succ.Mt Number of successful S1 Multi-mode: None Radio Bearer Management

"mt-Access"
LTE: LBFD-002008
TDLBFD-002008
1526741854 L.S1Sig.ConnEst.Succ.MoSig Number of successful S1 Multi-mode: None Radio Bearer Management

"mo-Signalling"
LTE: LBFD-002008
TDLBFD-002008
1526741855 L.S1Sig.ConnEst.Succ.MoData Number of successful S1 Multi-mode: None Radio Bearer Management

"mo-Data"
LTE: LBFD-002008
TDLBFD-002008
1526741856 L.S1Sig.ConnEst.Succ.DelayTol Number of successful S1 Multi-mode: None Radio Bearer Management

"delayTolerantAccess-
LTE: LBFD-002008
v1020"
TDLBFD-002008
1526741885 L.RRC.ConnReq.Msg.disc.Illegal Number of times RRC Multi-mode: None RRC Connection

messages are discarded UMTS: None RRC Connection
because the messages are Management
LTE: LBFD-002007
illegal
TDLBFD-002007
within [138,141) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026


within [141,144) dB LTE: LBFD-002008 Basic Scheduling
LBFD-002025 Support of UE Category 1
TDLBFD-002025
LBFD-002026
TDLBFD-002027
within [144,147) dB
LBFD-002025 Emergency call
TDLBFD-002025
LBFD-002026
TDLBFD-002028
whose path loss is greater UMTS: None Basic Scheduling
than or equal to 147 dB
LBFD-002025 Earthquake and Tsunami
TDLBFD-002025 Warning System(ETWS)
LBFD-002026
TDLBFD-002029
ranges within [138,141) dB
LBFD-002025
TDLBFD-002025
LBFD-002026
LBFD-002025 Support of aperiodic CQI
TDLBFD-002025 reports
LBFD-002026
TDLBFD-002031
TDLBFD-002025
LBFD-002026
TDLBFD-002032
147 dB TDLBFD-002008 Uplink Power Control
LBFD-002025
TDLBFD-002025
LBFD-002026
LBFD-002025
TDLBFD-002025
LBFD-002026
LBFD-002025 Multi Carrier
TDLBFD-002025
LBFD-002026
TDLBFD-002035

LBFD-002025
TDLBFD-002025
LBFD-002026
147 dB
LBFD-002025
TDLBFD-002025
LBFD-002026
a path loss ranging UMTS: None Basic Scheduling
between [138,141) dB
LBFD-002025
TDLBFD-002025
LBFD-002026
LBFD-002025
TDLBFD-002025
LBFD-002026
LBFD-002025
TDLBFD-002025
LBFD-002026
perform services with a GSM: None Radio Bearer Management
path loss greater than or UMTS: None Basic Scheduling
equal to 147 dB
LBFD-002025
TDLBFD-002025
LBFD-002026
attempts for QCI 65 GSM: None Radio Bearer Management
services in a cell UMTS: None
LTE: LBFD-002008
TDLBFD-002008

E-RAB setups for QCI 65 GSM: None Radio Bearer Management
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
1526741978 L.E-RAB.SuccEst.QCI.69 Multi-mode: None Radio Bearer Management


Number of successful GSM: None Radio Bearer Management
E-RAB setups for QCI 69 UMTS: None
services in a cell LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008
setup attempts for QCI 65 GSM: None Radio Bearer Management
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008

QCI 65 services in a cell UMTS: None
LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008

LTE: LBFD-002008
TDLBFD-002008



LTE: LBFD-002008
TDLBFD-002008
1526741993 L.E-RAB.NormRel.QCI.65 Number of normal releases Multi-mode: None Radio Bearer Management
of E-RABs for QCI 65 GSM: None Radio Bearer Management
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
1526741997 L.E-RAB.FailEst.NoRadioRes.DLSatis.QCI65 Number of E-RAB setup Multi-mode: None Radio Bearer Management
failures for QCI 65 services GSM: None Radio Bearer Management
satisfaction rate
TDLBFD-002008
TDLBFD-002023
LBFD-002023
1526741998 L.E-RAB.FailEst.NoRadioRes.DLSatis.QCI66 Number of E-RAB setup Multi-mode: None Radio Bearer Management
satisfaction rate
TDLBFD-002008
TDLBFD-002023
LBFD-002023
1526741999 L.E-RAB.FailEst.NoRadioRes.ULSatis.QCI65 Number of E-RAB setup Multi-mode: None Radio Bearer Management
satisfaction rate
TDLBFD-002008
TDLBFD-002023
LBFD-002023
1526742000 L.E-RAB.FailEst.NoRadioRes.ULSatis.QCI66 Number of E-RAB setup Multi-mode: None Radio Bearer Management
satisfaction rate
TDLBFD-002008
TDLBFD-002023
LBFD-002023
1526742001 L.E-RAB.Est.TimeAvg.QCI.65 Average E-RAB setup Multi-mode: None Radio Bearer Management
duration for QCI 65 GSM: None Radio Bearer Management
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
1526742005 L.E-RAB.Est.TimeMax.QCI.65 Maximum E-RAB setup Multi-mode: None Radio Bearer Management


LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
LTE: LBFD-002008
TDLBFD-002008
1526742009 L.E-RAB.Est.TimeAvg.PLMN Average E-RAB setup Multi-mode: None Radio Bearer Management
duration of a specific GSM: None Radio Bearer Management
operator in a cell UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526742011 L.Traffic.eNodeB.FDD.User.Max Maximum number of LTE Multi-mode: None RRC Connection

FDD UEs served by an GSM: None Management
eNodeB UMTS: None
LTE: LBFD-002007

LTE: LBFD-002007
LOFD-001105
TDLOFD-001105
1526742091 L.E-RAB.AbnormRel.eNBTot.UEAbnormal Number of E-RABs Multi-mode: None Radio Bearer Management

released by defective UEs GSM: None Radio Bearer Management
LTE: LBFD-002008
TDLBFD-002008
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526742097 L.Thrp.Time.UL.QCI.66 Multi-mode: None Radio Bearer Management


Receive duration of uplink GSM: None Radio Bearer Management
PDCP PDUs for services UMTS: None Basic Scheduling
with the QCI of 66 in a cell LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025

in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025

in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025

in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025

in a cell
TDLBFD-002008
LBFD-002025


TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025


with a QCI of 69 in a cell LTE: LBFD-002008 Basic Scheduling
over the Uu interface TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
QCI of 65 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
QCI of 66 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
QCI of 69 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
QCI of 70 in a cell
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025


TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526742143 L.HHO.IntraCell.ExecAttOut Number of intra-cell Multi-mode: None RRC Connection

outgoing handover GSM: None Management
execution attempts in a cell UMTS: None RRC Connection
TDLBFD-002007
1526742145 L.HHO.IntraCell.ExecSuccOut Number of successful intra- Multi-mode: None RRC Connection

cell outgoing handover GSM: None Management
executions in a cell UMTS: None RRC Connection
TDLBFD-002007
1526742148 L.UECNTX.Rel.eNodeB.CallMute Number of UE context Multi-mode: None Radio Bearer Management

eNodeB due to uplink mute UMTS: None
calls
LTE: LBFD-002008
TDLBFD-002008
1526742166 L.E-RAB.FailEst.NoRadioRes.UserSpec Number of E-RAB setup Multi-mode: None Radio Bearer Management
failures because of the GSM: None Radio Bearer Management
limitation of the maximum UMTS: None
number of Ues
LTE: LBFD-002008
TDLBFD-002008
1526742167 L.E-RAB.FailEst.NoRadioRes.RrcUserLic Number of E-RAB setup Multi-mode: None Radio Bearer Management
insufficient licensed UMTS: None
number of UEs in the
LTE: LBFD-002008
RRC_CONNECTED state
TDLBFD-002008
10 Glossary
1. 3GPP TS 36.331: "Radio Resource Control (RRC); Protocol specification"

2. 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access"
3. 3GPP TS 36.211: "Physical channels and modulation"
4. 3GPP TS 36.321: "Medium Access Control (MAC) protocol specification"
5. Idle Mode Management Feature Parameter Description
6. LCS Feature Parameter Description
7. Power Control Feature Parameter Description
8. Radio Security Feature Parameter Description
9. Random Access Control and RACH Optimization Feature Parameter Description
10. S1-Flex Feature Parameter Description

eRAN
Idle Mode Management Feature Parameter Description
Issue 05
Date 2016-11-01

Notice

3 Contents
1.1 Scope
1.3 Change History
2 Overview
2.1 Introduction
2.2 Benefits
3.1 PLMN Selection
3.1.1 PLMN Selection in Automatic Mode
3.1.2 PLMN Selection in Manual Mode
3.1.3 Roaming

3.2 Cell Selection and Reselection

3.2.1 Cell Search
3.2.2 Cell Selection
3.2.3 Neighboring Cell Priority Handling
3.2.4 Blacklisted Cell Identifying
3.2.5 Neighboring Cell Measurement for Cell Reselection
3.2.6 Intra-Frequency or Equal-Priority Inter-Frequency Cell Reselection
3.2.7 Different-Priority Inter-Frequency or Inter-RAT Cell Reselection
3.2.8 Speed-based Cell Reselection
3.3 Tracking Area Registration
3.3.1 Tracking Area Update
3.3.2 Attach/Detach
3.4 Cell Reservation and Access Control
3.4.1 Cell Reservation and Barring
3.4.2 Access Control
3.5 System Information Broadcast
3.5.1 System Information Block Contents
3.5.2 System Information Scheduling Periods
3.5.3 System Information Update
3.6 Paging
3.6.1 Triggering of Paging
3.6.2 Paging Mechanism over the Uu Interface
3.6.3 Paging Handling Procedure
3.6.4 Scheduling of Paging Messages
4 Related Features
4.1 LBFD-002009 Broadcast of system information
4.2 LBFD-002011 Paging
4.3 LBFD-00201803 Cell Selection and Re-selection
5 Network Impact
5.1 LBFD-002009 Broadcast of system information
5.2 LBFD-002011 Paging
5.3 LBFD-00201803 Cell Selection and Re-selection
6.1 When to Use
6.2 Deployment
6.2.1 Requirements
6.2.5 Deactivation
6.5 Possible Issues
7 Parameters
8 Counters
9 Glossary
Scope
This document describes idle mode management, including its technical principles, related features, network impact, and engineering guidelines. This document covers the
following features:
• LBFD-002009 Broadcast of system information

• LBFD-002011 Paging
• LBFD-00201803 Cell Selection and Re-selection
This document applies only to LTE (FDD). Any "LTE" in this document refers to LTE (FDD), and "eNodeB" refers to LTE (FDD) eNodeB.
eNodeB Type Model
Micro BTS3202E
BTS3203E

eNodeB Type Model

BTS3911E
BTS3912E
LampSite DBS3900 LampSite
Intended Audience

Change History
• Feature change
AN11.1 05 (2016-11-01)
Editorial change Optimized descriptions about neighboring cell measurement. For None -
details, see 3.2.5 Neighboring Cell Measurement for Cell Reselection.
Optimized some descriptions. For details, see 3.2.2 Cell Selection and 3.2.7
Different-Priority Inter-Frequency or Inter-RAT Cell Reselection.
AN11.1 04 (2016-08-01)
Editorial change Optimized the description about intra-frequency cell measurement. For None -
details, see 3.2.5 Neighboring Cell Measurement for Cell Reselection.
Optimized the description about the scope where blacklisted cells take
effect. For details, see 3.2.4 Blacklisted Cell Identifying.
AN11.1 03 (2016-06-30)
Editorial change Optimized descriptions about speed-based cell reselection. For details, None -
see 3.2.8 Speed-based Cell Reselection, 6.2.2.1 Data Preparation, 6.2.2.3 Using MML
Commands, 6.2.3 Activation Observation , 6.2.5.2 Using MML Commands, and 6.4
Parameter Optimization.
AN11.1 02 (2016-04-20)
Editorial change Updated the description about the priority of the non-serving E-UTRA None -
frequency under "Common Priority". For details, see 3.2.3 Neighboring Cell
Priority Handling.
AN11.1 01 (2016-03-07)
AN11.1 Draft B (2015-12-30)
Editorial change Updated the descriptions in 4 Related Features and 6.2.1 Requirements. None -
AN11.1 Draft A (2015-12-07)
Feature change Added switches to control whether the eNodeB broadcasts Added the CellSiMap.SiSwitch parameter. Macro/Micro/LampSite
SIB6 and SIB7. For details, see 3.5 System Information
Broadcast.


Supported flexible control over whether the Qqualmin IE is Modified the CellSel.QQualMin parameter Macro/Micro/LampSite
delivered in SIB1. For details, see Cell Selection Criteria in 3.2.2 value range and default value:
Cell Selection. • Added the value 0, indicating
that the Qqualmin IE is not
delivered in SIB1.
• Changed the default value to 0.
Added the function of containing the Paging Priority IE in None Macro/Micro/LampSite

paging messages delivered by the MME. For details, see
3.6.4 Scheduling of Paging Messages.
Added the EutranInterNFreq.MeasPerformanceDemand Added the Macro/Micro/LampSite

parameter to control whether to lower the measurement EutranInterNFreq.MeasPerformanceDemand
performance requirements for non-serving E-UTRA parameter.
frequencies delivered in SIB5. For details, see Inter-
Frequency or Inter-RAT Measurement in 3.2.5 Neighboring Cell
Measurement for Cell Reselection.
Editorial change • Revised the descriptions in the following None -

sections:
◾ 3.2 Cell Selection and Reselection
◾ 6 Engineering Guidelines
• Removed section 2.4 "Related Concepts". For
details about related concepts, see 3GPP
protocols.

The features described in this document are implemented in the same way on macro, micro, and LampSite eNodeBs.
2 Overview
Introduction
In an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), UEs can be either in RRC_CONNECTED or RRC_IDLE mode. RRC is short for radio resource control.
After being powered on, UEs will be in RRC_IDLE mode (also known as idle mode) if no radio resource control (RRC) connection is established between the UEs and the
E-UTRAN.
This document describes the following aspects of idle mode management:
• PLMN selection
UEs select a Public Land Mobile Network (PLMN) and register on the PLMN.
• Cell selection
UEs select cells in the chosen PLMN and camp on the cells so that the UEs can monitor system information and paging messages to obtain services.
• Cell reselection
When camping on a given cell, a UE searches for a better cell based on the cell reselection criteria, to correctly receive system information and successfully initiate
services.
• Tracking area (TA) registration
UEs register their locations with the evolved packet core (EPC) through a TA registration procedure so that the EPC can page them within the TA and request that
they initiate services.
• Cell reservation and access Control
Cell reservation and access control are two mechanisms operators use to control their networks. Cell reservation allows specific cells to be reserved for only UEs of
certain classes (for example, for network management by operators). Access control determines whether UEs can initiate calls in a cell based on UE classes.
• System information broadcast and paging
In a system information broadcast, information such as parameters related to cell selection and reselection, is broadcast to UEs over the broadcast control channel
(BCCH). In paging, paging messages are used to inform all the UEs in a given cell of any changes in the system information, and to carry paging-related information.
The main activities of UEs in idle mode are PLMN selection, cell selection and reselection, and TA registration. Figure 2-1 shows the relationships between them.
Figure 2-1 Relationships between PLMN selection, cell selection and reselection, and TA registration
Benefits
With idle mode management, the eNodeB includes configurations in system information broadcasts, and the UEs select suitable cells to camp on and obtain services based on
these configurations. Idle mode management increases the access success rate, improves the quality of service, and ensures that UEs camp on cells with good signal levels
and qualities.

To guarantee the access success rate and to shorten the time required to access the network , a UE in idle mode selects a cell based on the signal quality of the measured
cells, and based on the parameters in the system information. When camping on the cell, the UE searches for a better cell according to the cell reselection criteria, ensuring that
it receives system information correctly and can initiate services successfully.
PLMN Selection
Figure 3-1 shows the PLMN selection procedure. When a UE is powered on, or returns from an area lacking coverage, the UE first selects the last RPLMN or a PLMN in the
EPLMN list and attempts to register on the selected PLMN. If the registration on that PLMN is successful, the selected PLMN is displayed on the UE, and the UE can now obtain
services from the operator. If the last RPLMN is unavailable or if the registration on the selected PLMN fails, another PLMN can be selected, either automatically or manually,
depending on the priorities of the PLMNs stored in the USIM. For details about PLMN selection, see section 4.4 in 3GPP TS 23.122 R10, which was released in March 2011.
Figure 3-1 PLMN selection procedure
3.1.1 PLMN Selection in Automatic Mode

If a UE fails to register on its most recent RPLMN or EPLMN, the UE attempts to select another PLMN. In automatic network selection mode, the UE selects a PLMN in the
following preferential order:
1. The EHPLMN with the highest priority if the EHPLMN list is present and is not empty, or the HPLMN if the EHPLMN list is not present or is empty.
2. Each PLMN/radio technology combination in the User Controlled PLMN Selector with Access Technology data file in the USIM, in priority order.
3. Each PLMN/radio technology combination in the Operator Controlled PLMN Selector with Access Technology data file in the USIM, in priority order.
4. Other high-quality PLMN/radio technology combinations, in a random order. If the reference signal received power (RSRP) value of a cell in the PLMN/radio
technology combination is greater than or equal to –110 dBm, the combination is considered a high quality PLMN/radio technology combination.
5. Other PLMN/radio technology combinations in order of decreasing signal quality.
When the UE finds a Suitable Cell in a PLMN following this procedure, the UE attempts to register on the PLMN. If the registration is successful, the UE camps on the Suitable
Cell; otherwise, the UE tries the next PLMN.
If the registration on none of the PLMNs is successful, the UE enters the Limited service state. If no PLMN is available, the UE cannot obtain any services.
NOTE:
Limited service, Normal service, and Operator service are three service types that can be provided for UEs in idle mode in Acceptable Cell, Suitable Cell, and Reserved Cell,
respectively. For details about Acceptable Cell, Suitable Cell, and Reserved Cell, see section 4.3 in 3GPP TS 36.304 R10, which was released in March 2011.
3.1.2 PLMN Selection in Manual Mode

If a UE fails to register on its most recent RPLMN or EPLMN, the UE attempts to select a new PLMN. For manual network selection, the UE displays a list of detected PLMNs in
the same order as the PLMNs to be selected for automatic network selection.
In manual mode, the UE can also try forbidden PLMNs, which are determined by the EPC. If the UE successfully registers on the selected PLMN, the UE no longer considers
the PLMN to be forbidden.
3.1.3 Roaming
When roaming, UEs obtain services from a VPLMN other than its HPLMN. For example, the UE may obtain services from a PLMN in another country (an international roaming
area). When the UE with the roaming service moves out of the coverage area of its HPLMN, the UE can obtain services from another PLMN according to the PLMN information
stored on the USIM. The operator determines whether roaming is allowed for a UE.
After the UE registers with a VPLMN by roaming, it periodically searches for its HPLMN and attempts to return to it. The time interval between consecutive searches for the
HPLMN is defined by the operator and stored on the USIM.
Cell Selection and Reselection

This section describes the basic feature LBFD-00201803 Cell Selection and Re-selection.
After selecting a PLMN, a UE selects a cell in the PLMN to camp on. After camping on the cell, the UE monitors system information, performs measurements on the serving cell
and neighboring cells based on measurement rules, and selects a better cell to camp on based on cell reselection criteria.
Before the UE selects a cell to camp on, it performs a cell search procedure. After the UE finds a cell, it performs cell selection or reselection using the selection- or reselection-
related parameters from the system information or from the RRC Connection Release message. Figure 3-2 shows the cell selection and cell reselection procedures. Either Stored
Information Cell Selection (preferred) or Initial Cell Selection can be used to search for a Suitable Cell. For details, see section 5.2.2 in 3GPP TS 36.304 R10, which was
released in March 2011.

Figure 3-2 Cell selection and reselection procedures
NOTE:
For details about the cell reselection triggering conditions, see 3.2.6 Intra-Frequency or Equal-Priority Inter-Frequency Cell Reselection, 3.2.7 Different-Priority Inter-Frequency or Inter-RAT
Cell Reselection, and 3.2.8 Speed-based Cell Reselection.
3.2.1 Cell Search

Cell search is a procedure in which a UE achieves time and frequency synchronization with a cell, obtains the physical cell identifier (PCI), and learns the signal quality and
other information about the cell based on the PCI. A UE performs cell search on all frequencies before selecting or reselecting to a cell.
In an LTE system, two types of synchronization signals are used for cell search: primary synchronization signals (PSSs) and secondary synchronization signals (SSSs). The cell
search procedure is as follows:
1. A UE monitors the PSS to acquire clock synchronization accurate to within 5 ms, and to identify the cell identities in possible cell identity groups the PCI belongs to.
2. The UE monitors the SSSs to acquire frame synchronization, that is, time synchronization, and to identify the cell identity groups based on the one-to-one
relationship with SSSs.
3. The UE identifies the PCI by cross-referencing the identified cell identity and cell identity group.
4. The UE monitors the downlink reference signal to determine the signal quality in the cell.
5. The UE reads information on the broadcast channel (BCH) to acquire related details about the cell.
NOTE:
• In an E-UTRAN, cell identities are grouped to reduce the number of correlation detections, simplifying PCI identification.
• Each cell identity group consists of three cell identities.
3.2.2 Cell Selection

When a UE transitions from connected mode to idle mode or after it has selected a PLMN, the UE must select a cell to camp on.
When the UE transitions from connected mode to idle mode:
1. The UE first attempts to select the most recent cell it has camped on in connected mode, or it selects a Suitable Cell on a frequency that is allocated through the
RRC Connection Release message.
2. If such a cell is not available, the UE attempts to find a Suitable Cell by performing the Stored Information Cell Selection procedure.
3. If the UE fails to find a Suitable Cell, the UE performs the Initial Cell Selection procedure.
ored Information Cell Selection
The Stored Information Cell Selection procedure requires stored information related to carrier frequencies and cell parameters. The information is retrieved from previous
measurement control information elements or from preexisting SI messages. This information can help speed up cell selection.
The Stored Information Cell Selection procedure is as follows:
The UE searches known carrier frequencies for a Suitable Cell.
• If the UE finds a Suitable Cell, it selects that cell to camp on.

• If the UE fails to find a Suitable Cell, it initiates the Initial Cell Selection procedure.
tial Cell Selection
The Initial Cell Selection procedure does not require that the UE know in advance which frequencies are E-UTRA carrier frequencies.
In this procedure, the UE scans all carrier frequencies on the supported E-UTRAN bands to find a Suitable Cell. On each carrier frequency, the UE searches for the strongest
cell only. If the UE finds a Suitable Cell, it selects that cell to camp on. If the UE fails to find a Suitable Cell, it selects an Acceptable Cell to camp on.
ll Selection Criteria
During cell selection, a UE selects an E-UTRAN cell that meets cell selection criteria.
A UE selects an E-UTRAN cell to camp on when both Srxlev and Squal are greater than zero.
where
Srxlev = Qrxlevmeas – (Qrxlevmin + Qrxlevminoffset) - Pcompensation
Squal = Qqualmeas – (Qqualmin + Qqualminoffset)
The variables in the preceding formulas are described as follows:
• Qrxlevmeas is the measured cell RX signal level (RSRP value) of the cell.
• Qrxlevmin is the minimum cell RX signal level. It is broadcast in SIB1 and set by the CellSel.QRxLevMin parameter.

• Qrxlevminoffset is the offset to Qrxlevmin. It is broadcast in SIB1 and set by the CellSel.QRxLevMinOffset parameter. The UE camping on a cell in a VPLMN
considers this offset parameter when it attempts to camp on a cell in a higher-priority PLMN during periodic cell reselection. The cell in the higher-priority PLMN
delivers the value of this parameter to the UE for the Srxlev evaluation.
• Pcompensation is the result of the function: max (PMax - UE Maximum Output Power, 0).
◾ PMax is the maximum transmit power that the UE can apply to uplink transmission. It is broadcast in SIB1 and set by the CELL.UePowerMax parameter.
◾ UE Maximum Output Power is the maximum output power that the UE can physically achieve. It is not configurable on the network side.
• Qqualmeas is the measured cell RX signal quality (RSRQ value) of the cell.
• Qqualmin is the minimum cell RX signal quality required for the cell to become a Suitable Cell. It is broadcast in SIB1 and set by the CellSel.QQualMin parameter.
The CellResel.ThrshServLowQCfgInd and CellSel.QQualMin settings determine whether the Qqualmin IE is delivered in SIB1:
◾ When the value of CellSel.QQualMin is not 0, CellResel.ThrshServLowQCfgInd can be set to CFG(Configure) or NOT_CFG(Not configure). In this case,
the Qqualmin IE is delivered in SIB1.
◾ When the value of CellSel.QQualMin is 0, CellResel.ThrshServLowQCfgInd can only be set to NOT_CFG(Not configure). In this case, the Qqualmin IE is
not delivered in SIB1.
For details, see section 6.2.2 "SystemInformationBlockType1" in 3GPP TS 36.331 R10, which was released in March 2011.
• Qqualminoffset is the offset to Qqualmin. It is broadcast in SIB1 and set by the CellSel.QQualMinOffset parameter. The UE camping on a cell in a VPLMN considers
this offset parameter when it attempts to camp on a cell in a higher-priority PLMN during periodic cell reselection. The cell in the higher-priority PLMN delivers the
value of this parameter to the UE for the Squal evaluation.
3.2.3 Neighboring Cell Priority Handling

After camping on a cell, a UE may attempt to reselect to and then camp on another cell. Before cell reselection, the UE is required to measure the signal quality level of
neighboring cells. The UE then reselects to a neighboring cell by using a specific cell reselection criterion according to the priority of the neighboring cell.
During measurement and implementation of cell reselection, the UE needs to obtain the priorities of neighboring frequencies. Note that frequencies of different RATs must be
configured with different priorities. During the evaluation for reselection to an intra-frequency neighboring cell, the UE ignores the priority of the target frequency because cells
working on the same frequency have the same priority.
The priorities for E-UTRAN frequencies and inter-RAT frequencies include common priorities and dedicated priorities.
ommon Priority
The priority of the serving frequency is specified by CellResel.CellReselPriority and broadcast in system information block type 3 (SIB3).
The priority of the non-serving E-UTRA frequency is specified by EutranInterNFreq.CellReselPriority and broadcast in SIB5. A maximum of 16 non-serving E-UTRA frequencies
can be broadcast.
NOTE:
Each UMPTe board can be configured with a maximum of 16 non-serving E-UTRA frequencies, while other boards can be configured with no more than 8.
The priority of the neighboring UTRAN frequency is specified by UtranNFreq.CellReselPriority and broadcast in SIB6. A maximum of 16 neighboring UTRAN frequencies can be
broadcast.
The priority of the neighboring GERAN frequency is specified by GeranNfreqGroup.CellReselPriority and broadcast in SIB7. A maximum of 16 neighboring GERAN frequency
groups can be broadcast.
The priority of a neighboring CDMA2000 frequency is specified by Cdma2000BandClass.Cdma20001XrttCellReselPri and Cdma2000BandClass.Cdma2000HrpdCellReselPri
and broadcast in SIB8.
dicated Priority
The IdleModeMobilityControlInfo (IMMCI) IE in the RRC Connection Release message delivers the radio resources for each UE during release of radio resources. A maximum
of 16 non-serving E-UTRA frequencies, 16 neighboring UTRAN frequencies, and 16 neighboring GERAN frequency groups can be delivered for each UE.
Cell reselection dedicated priorities include SPID dedicated priorities and operator-specific dedicated priorities.
• SPID dedicated priority

Specifies a dedicated cell reselection priority using the SPID.
An SPID dedicated priority can be either a common SPID priority or an operator-based SPID priority.
◾ Common SPID priority
Specifies an SPID priority configured not based on PLMN.
◾ Operator-based SPID priority
Specifies an SPID priority configured based on the PLMN of the serving cell.
For details about dedicated SPID priorities, see descriptions of LOFD-00105401 Camp & Handover Based on SPID in Flexible User Steering Feature Parameter
Description.
On a shared network, the eNodeB uses LOFD-001133 Multi Operators SPID Policy to implement the operator-specific SPID dedicated priority function for cell
reselection. Specifically, operators sharing the same eNodeB can select their respective SPID value ranges, without negotiating with each other, and the shared
eNodeB allows users of different operators to use the same SPID for different cell reselection dedicated priority policies. For details, see RAN Sharing Feature
Parameter Description.
• Operator-specific dedicated priority
Operator-specific dedicated priorities are either based on the home operator of an adjacent frequency, or of the serving cell.
◾ Home operator of an adjacent frequency
Specifies a dedicated cell reselection priority based on the operator to which an adjacent frequency belongs.
In RAN Sharing scenarios, the dedicated priorities of E-UTRAN, UTRAN, and GERAN frequencies are specified by
EutranNFreqRanShare.CellReselPriority, UtranRanShare.CellReselPriority, and GeranRanShare.CellReselPriority, respectively, for different PLMNs.
◾ Home operator of the serving cell
Specifies a dedicated cell reselection priority based on the PLMN ID of the serving cell. The priorities are specified by
EutranNFreqSCellOp.CellReselDediPri, UtranNFreqSCellOp.CellReselDediPri, GeranNFGroupSCellOp.CellReselDediPri,
Cdma2000BcSCellOp.Cdma1XrttCellReselDediPri, and Cdma2000BcSCellOp.HrpdCellReselDediPri.
Both dedicated priority based on home operator of an adjacent frequency and dedicated priority based on home operator of the serving cell are operator-specific
dedicated priorities. Only one type can be used at a time.
The eNodeB determines the dedicated frequency priorities to carry in the RRC Connection Release message in the following order:
1. The eNodeB preferentially uses SPID dedicated priorities.

2. If no SPID priority is configured for the UE, the eNodeB uses the dedicated frequency priorities of operators configured in the EutranNFreqRanShare,
UtranRanShare, and GeranRanShare MOs, or the frequency priorities of UE-homed operators configured in the EutranNFreqSCellOp, UtranNFreqSCellOp,
GeranNFGroupSCellOp, and Cdma2000BcSCellOp MOs.
3. If no dedicated priority of operators is configured, the eNodeB does not carry dedicated frequency priorities in the RRC Connection Release message.
There are two exceptions:
• For a CA UE, when idle-mode PCC anchoring takes effect, if no SPID dedicated priority or operator-specific dedicated priority is configured, the eNodeB still carries
the dedicated frequency priorities generated by this function in the RRC Connection Release message. For details about the idle-mode PCC anchoring function, see
Carrier Aggregation Feature Parameter Description.

• For a UE release due to system overload, MME overload, or S1-interface faults, even if the eNodeB does not use any of these preceding dedicated priorities, if the
common priority of the neighboring frequency is lower than the common priority of the serving frequency, the eNodeB uses the common priority of the serving
frequency as the dedicated priority of a neighboring frequency and carries the priority in the RRC Connection Release message.
When the eNodeB determines the list of frequency priorities to carry in the RRC Connection Release message, it filters frequencies based on UE capabilities and on the target
PLMN.
1. The eNodeB filters frequencies based on UE capabilities.

• If the eNodeB has obtained UE capabilities, it filters out frequencies that UEs do not support based on systems supported by UEs and UE frequency
capabilities.
NOTE:
If the UE supports enhanced measurement frequency capabilities (UE capability reported in "incMonEUTRA" is TRUE), the eNodeB sends dedicated
priorities for a maximum of 16 frequencies. If it does not, the eNodeB sends dedicated priorities for a maximum of eight frequencies, for which the value
of the EutranInterNFreq.MeasPerformanceDemand parameter is NORMAL(NORMAL).
• If the eNodeB has not obtained UE capabilities, it checks the value of CellAlgoSwitch.ReselecPriAdaptSwitch and determines the cause value of RRC
access request.
◾ If CellAlgoSwitch.ReselecPriAdaptSwitch is set to ON(On) and the cause value of RRC access request is mo-Signalling (such as TAU
accept/reject and attach reject), and the S1 release is initiated by the MME with the cause value NAS, the eNodeB assumes that UEs support
all frequencies in the priority list and does not filter frequencies.
◾ Otherwise, the eNodeB assumes that UEs support only the frequencies of the serving cell. In this case, if frequencies of the serving cell are
included in the frequency list, they are reserved and other frequencies are filtered out. If frequencies of the serving cell are not included in the
frequency list, the eNodeB does not deliver the IMMCI IE.
2. The eNodeB filters frequencies based on the target PLMN.

• If all home PLMNs of external cells under the frequency are not included in the target PLMN list, the eNodeB filters out the frequency.
• If no external cells are configured on the frequency (no PLMN information of external cells), the eNodeB fails to obtain PLMN attributes of the frequency
and filters out the frequency.
The eNodeB includes remaining frequencies in the IMMCI IE and delivers it to UEs.
When a UE camps on a Suitable Cell during cell reselection:
• If dedicated priorities are assigned through dedicated signaling, the UE ignores all the absolute priorities provided in system information.
• If the UE acquires the priorities of other frequencies but no priority of the serving frequency, the UE regards the priority of the serving frequency as the lowest.
During cell reselection, when a UE camps on an Acceptable Cell, the UE uses only the absolute priorities provided in system information. The UE only stores the information
about the dedicated priorities but does not use it for cell reselection even when dedicated priorities are available.
A UE discards priorities provided by dedicated signaling in any of the following situations:
• The NAS signals the AS to perform PLMN selection.

• The UE enters the connected mode.
• The validity time (specified by T320) of the dedicated priority expires.
T320 and the dedicated priority are sent to the UE in the RRC Connection Release message. The eNodeB determines the value of T320 in the following two ways:
• If the dedicated priority is obtained through the UE's SPID mapping or the PCC anchoring function, the value of T320 is always 180 minutes.
• If the dedicated priority is obtained through other means, T320 is specified by the RrcConnStateTimer.T320ForLoadBalance parameter during an RRC connection
release due to load balancing, or by the RrcConnStateTimer.T320ForOther parameter during an RRC connection release due to other reasons.
For details about T320, see section 7.3 in 3GPP TS 36.331 R10, released in March 2011.
3.2.4 Blacklisted Cell Identifying

During cell reselection, UEs are not allowed to measure or reselect to the blacklisted cells of the serving cell. Blacklisted cells are classified into intra-frequency and inter-
frequency blacklisted cells.
• Information about intra-frequency blacklisted cells is delivered in IntraFreqBlackCellList of SIB4 and is excluded from IntraFreqNeighCellList of SIB4.
• Information about inter-frequency blacklisted cells is delivered in InterFreqBlackCellList of SIB5 and is excluded from InterFreqNeighCellList of SIB5.
UEs identify blacklisted cells by their PCIs.

An intra-frequency blacklisted cell can be configured in the IntraFreqBlkCell MO. The first 16 E-UTRAN intra-frequency blacklisted cells are the cells blacklisted in intra-
frequency idle mode. In this MO, IntraFreqBlkCell.PhyCellId specifies the starting PCI of an intra-frequency blacklisted cell list, and IntraFreqBlkCell.PhyCellIdRange specifies
the number of consecutive PCIs from the starting PCI specified by IntraFreqBlkCell.PhyCellId onwards.
An inter-frequency blacklisted cell can be configured in the InterFreqBlkCell MO. The first 16 E-UTRAN inter-frequency blacklisted cells are the cells blacklisted in inter-
frequency idle mode. In this MO, InterFreqBlkCell.DlEarfcn specifies the downlink EARFCN corresponding to the blacklist, InterFreqBlkCell.PhyCellId specifies the starting PCI
in the blacklist, and InterFreqBlkCell.PhyCellIdRange specifies the number of consecutive PCIs from the starting PCI specified by InterFreqBlkCell.PhyCellId onwards.
3.2.5 Neighboring Cell Measurement for Cell Reselection

During cell reselection, UEs perform neighboring cell measurements based on the signal quality of the serving cell and the frequency priorities of the neighboring cells. The UE
measures only the neighboring frequencies broadcast in the system information and the neighboring frequency whose priority information is carried in the RRC Connection
Release message.
ra-Frequency Measurement
To trigger intra-frequency measurements, the following rules apply:

The UE does not perform intra-frequency measurements if the Srxlev and Squal values of the serving cell are greater than SIntraSearchP and SIntraSearchQ, respectively. The UE
performs intra-frequency measurements if the Srxlev or Squal value of the serving cell is not greater than SIntraSearchP or SIntraSearchQ, respectively. For details about how to
calculate the Srxlev and Squal values, see 3.2.2 Cell Selection.
The following table provides reference for determining the values of SIntraSearchP and SIntraSearchQ:
CellResel.SIntraSearchCfgInd CellResel.QQualMinCfgInd IEs Broadcast in SIB3 SIntraSearchP Value SIntraSearchQ Value
NOT_CFG(Not configure) CFG(Configure) s-IntraSearchP and s-IntraSearchP s-IntraSearchQ

s-IntraSearchQ
CFG(Configure) NOT_CFG(Not configure) s-IntraSearch s-IntraSearch 0 dB

(1) (1) (1)
NOT_CFG(Not configure) NOT_CFG(Not configure) N/A Infinity 0 dB(1)
(1)
CFG(Configure) CFG(Configure) s-IntraSearch, s-IntraSearchP s-IntraSearchQ

s-IntraSearchP, and
s-IntraSearchQ
NOTE:

(1)
: In this case, a UE measures the intra-frequency cells, regardless of the signal quality in the serving cell.
Both s-IntraSearch and s-IntraSearchP broadcast in SI are specified by the CellResel.SIntraSearch parameter, and s-IntraSearchQ is specified by the
CellResel.SIntraSearchQ parameter.
When CellResel.QQualMinCfgInd is set to CFG(Configure) and CellResel.SIntraSearchCfgInd is set to NOT_CFG(Not configure), CellResel.SIntraSearch cannot be
configured. In this case, s-IntraSearchP uses the default value or last correctly configured value of CellResel.SIntraSearch
er-Frequency or Inter-RAT Measurement
To trigger inter-frequency or inter-RAT measurements, the following rules apply:
• The UE always performs measurements on inter-frequency or inter-RAT neighboring cells regardless of the signal quality of the serving cell as long as the priorities
of the neighboring frequencies are higher than the priority of the serving frequency.
• If the priorities of non-serving E-UTRA frequencies do not exceed the priority of the serving frequency, or if the priorities of inter-RAT neighboring frequencies are
lower than the priority of the serving frequency, the UE determines whether to start the corresponding measurements according to the following rules:
◾ The UE does not perform inter-frequency or inter-RAT measurements if the Srxlev and Squal values of the serving cell are greater than SnonIntraSearchP and
SnonIntraSearchQ, respectively. SnonIntraSearchP indicates the Srxlev threshold for triggering inter-frequency or inter-RAT measurements. SnonIntraSearchQ indicates
the Squal threshold for triggering inter-frequency or inter-RAT measurements.
◾ The UE performs inter-frequency or inter-RAT measurements if the Srxlev or Squal value of the serving cell is not greater than SnonIntraSearchP or
SnonIntraSearchQ, respectively.
The following table provides reference for determining the values of SnonIntraSearchP and SnonIntraSearchQ:
CellResel.SNonIntraSearchCfgInd CellResel.QQualMinCfgInd IEs Broadcast in SIB3 SnonIntraSearchP Value SnonIntraSearchQ Value
NOT_CFG(Not configure) CFG(Configure) s-NonIntraSearchP and s-NonIntraSearchP s-NonIntraSearchQ

s-NonIntraSearchQ
CFG(Configure) NOT_CFG(Not s-NonIntraSearch s-NonIntraSearch 0 dB

configure)
NOT_CFG(Not configure)(1) NOT_CFG(Not N/A(1) Infinity(1) 0 dB(1)

configure)(1)
CFG(Configure) CFG(Configure) s-NonIntraSearchP, s-NonIntraSearchP s-NonIntraSearchQ

s-NonIntraSearchQ, and
s-NonIntraSearch
NOTE:
(1)
: UEs measure both inter-frequency and inter-RAT cells, regardless of whether the signal quality in the serving cell is good.
Both s-NonIntraSearch and s-NonIntraSearchP broadcast in SI are specified by the CellResel.SNonIntraSearch parameter, and s-NonIntraSearchQ is specified
by the CellResel.SNonIntraSearchQ parameter.
When CellResel.QQualMinCfgInd is set to CFG(Configure) and CellResel.SNonIntraSearchCfgInd is set to NOT_CFG(Not configure), CellResel.SNonIntraSearch
cannot be configured. In this case, s-NonIntraSearchP uses the default value or last correctly configured value of CellResel.SNonIntraSearch.
NOTE:
For inter-frequency frequencies carried in SIB5:
• If the UE does not support enhanced measurement frequency capabilities (UE capability reported in "incMonEUTRA" is not TRUE), the UE can choose a frequency
for which EutranInterNFreq.MeasPerformanceDemand is set to NORMAL(NORMAL) as the target frequency for cell reselection.
• If the UE does support enhanced measurement frequency capabilities, the UE can obtain all the configured inter-frequency frequencies from SI. For frequencies for
which EutranInterNFreq.MeasPerformanceDemand is set to NORMAL(NORMAL), the UE performs measurements based on normal measurement performance. For
frequencies for which EutranInterNFreq.MeasPerformanceDemand is set to REDUCED(REDUCED), the UE performs measurements based on reduced
measurement performance. In this case, the time to reselect to such a frequency may increase.
3.2.6 Intra-Frequency or Equal-Priority Inter-Frequency Cell Reselection

UEs use the cell reselection criteria to reselect to intra-frequency or equal-priority inter-frequency cells. The UE evaluates the neighboring cell using the cell reselection criteria
only when the cell meets the cell selection criteria described in Cell Selection Criteria.
The following parameters broadcast in SIB3 are used for calculating the Srxlev and Squal values of intra-frequency neighboring cells:
• Qrxlevmin is the minimum cell RX signal level. It is set by the CellResel.QRxLevMin parameter and broadcast in SIB3.
• PMax is the maximum transmit power that the UE can apply to uplink transmission in the neighboring cell. It is set by the CellResel.PMax parameter and broadcast in
SIB3.
• Qqualmin is the minimum cell RX signal quality. It is set by the CellResel.QQualMin parameter and broadcast in SIB3.
• For details about Qrxlevminoffset and Qqualminoffset, see 3.2.2 Cell Selection.
The following parameters broadcast in SIB5 are used for calculating the Srxlev and Squal values of inter-frequency neighboring cells:
• Qrxlevmin is the minimum cell RX signal level. It is set by the EutranInterNFreq.QRxLevMin parameter and broadcast in SIB5.
• PMax is the maximum transmit power that the UE can apply to uplink transmission in the neighboring cell. It is set by the EutranInterNFreq.PMax parameter and
broadcast in SIB5.
• Qqualmin is the minimum cell RX signal quality. It is set by the EutranInterNFreq.QQualMin parameter and broadcast in SIB5.
The cell-ranking criteria R_s for the serving cell and R_n for neighboring cells are defined as follows:
R_s = Qmeas,s + Qhyst
R_n = Qmeas,n - Qoffset
where
• Qmeas,s is the measured RSRP value of the serving cell.

• Qhyst is the reselection hysteresis for the serving cell. It is set by the CellResel.Qhyst parameter and broadcast in SIB3.
• Qmeas,n is the measured RSRP value of the neighboring cell.
• Qoffset:
◾ For intra-frequency neighboring cells, it is equal to q-OffsetCell, which is broadcast in SIB4 and set by the EutranIntraFreqNCell.CellQoffset parameter. If
q-OffsetCell is not broadcast in SIB4, the UE sets q-OffsetCell to 0.
◾ For inter-frequency neighboring cells, it is equal to q-OffsetCell plus q-OffsetFreq, which are broadcast in SIB5 and set by the
EutranInterFreqNCell.CellQoffset and EutranInterNFreq.QoffsetFreq parameters, respectively. If q-OffsetCell is not broadcast in SIB5, the UE sets
q-OffsetCell to 0.

NOTE:
SIB4 and SIB5 broadcast a maximum of 16 intra- and inter-frequency neighboring cells of a frequency, respectively. The eNodeB supports a maximum of
256 intra- and inter-frequency neighboring cells in total. The eNodeB selects intra- and inter-frequency neighboring cells by using the following rules in
sequence:
1. Neighboring cells for which EutranIntraFreqNCell.CellQoffset and EutranInterFreqNCell.CellQoffset are set to 0 are not broadcast.
2. Neighboring cells for which EutranIntraFreqNCell.CellMeasPriority and EutranInterFreqNCell.CellMeasPriority are set to HIGH are
preferentially broadcast.
3. If there are more than 16 neighboring cells, the 16 neighboring cells with the largest EutranIntraFreqNCell.CellQoffset and
EutranInterFreqNCell.CellQoffset values are broadcast.
4. If there are less than 16 neighboring cells, neighboring cells for which EutranIntraFreqNCell.CellMeasPriority and
EutranInterFreqNCell.CellMeasPriority are set to LOW and with the largest EutranIntraFreqNCell.CellQoffset and
EutranInterFreqNCell.CellQoffset values are added to reach a total of 16 neighboring cells. All the 16 neighboring cells are broadcast.
The UE follows the cell reselection criteria and selects the neighboring cell with the greatest R_n value, reselecting to that cell if both the following conditions are met:
• The signal quality level of the neighboring cell is always higher than that of the serving cell during the cell reselection time. The cell reselection time for an intra-
frequency neighboring cell is broadcast in SIB3 and set by the CellResel.TreselEutran parameter. The cell reselection time for an inter-frequency neighboring cell is
broadcast in SIB5 and set by the EutranInterNFreq.EutranReselTime parameter.
• The UE has camped on the serving cell for more than 1 second.
During cell reselection, the UE needs to check whether access to a neighboring cell is allowed according to the "cellAccessRelatedInfo" IE in SIB1 sent from the neighboring
cell. If the neighboring cell is barred, it must be excluded from the candidate list. If the neighboring cell cannot function as a Suitable Cell because it is part of the list of forbidden
TAs for roaming or it does not belong to the RPLMN or an EPLMN, the UE does not consider this neighboring cell and other cells on the same frequency as candidates for
reselection within 300 seconds.
3.2.7 Different-Priority Inter-Frequency or Inter-RAT Cell Reselection

Reselection to a different-priority inter-frequency cell or an inter-RAT cell can be classified as either reselection to a higher-priority cell or reselection to a lower-priority cell.
er-Frequency/Inter-RAT Cell Selection Criteria
The Srxlev and Squal values of inter-frequency or inter-RAT neighboring cells need to be calculated when the UE reselects to an inter-frequency or inter-RAT neighboring cell.
The Srxlev and Squal values are calculated as follows:
• Inter-frequency neighboring cell: See 3.2.6 Intra-Frequency or Equal-Priority Inter-Frequency Cell Reselection.
• Neighboring UTRAN cell
Srxlev = Qrxlevmeas - (Qrxlevmin + Qrxlevminoffset) - Pcompensation
Squal = Qqualmeas - (Qqualmin + Qqualminoffset)
Pcompensation = max(UE_TXPWR_MAX_RACH - P_MAX, 0)
Qrxlevmeas is the measured RX signal level of the neighboring UTRAN cell.
Qqualmeas is the measured RX signal quality of the neighboring UTRAN cell.
The values of these parameters are broadcast in SIB6 from the E-UTRAN when the UE implements reselection estimation on a neighboring UTRAN cell.
Qrxlevmin is set by the UtranNFreq.QRxLevMin parameter.
Qqualmin is set by the UtranNFreq.Qqualmin parameter.
UE_TXPWR_MAX_RACH is set by the UtranNFreq.PmaxUtran parameter.
P_MAX is the maximum output power that the UE can physically provide. It is not configurable on the network side.
Values of Qrxlevminoffset and Qqualminoffset are obtained from UTRAN system information. For details, see section 5.2.3.1 in 3GPP TS 25.304 R10, which was
• Neighboring GERAN cell

Srxlev = Qrxlevmeas - Qrxlevmin - Pcompensation
Qrxlevmeas is the measured RX signal level of the neighboring GERAN cell.
Pcompensation = max(MS_TXPWR_MAX_CCH - P, 0)
The values of these parameters are broadcast in SIB7 from the E-UTRAN when the UE implements reselection estimation on a neighboring GERAN cell.
Qrxlevmin is set by the GeranNfreqGroup.QRxLevMin parameter.
MS_TXPWR_MAX_CCH is set by the GeranNfreqGroup.PmaxGeran parameter.
P is the maximum output power that the UE can physically provide.
It is not configurable on the network side. For details, see section 3.6 "Radio constraints" in 3GPP TS 43.022 R10, which was released in March 2011.
• Neighboring CDMA2000 cell
Ec/Io is the measured RX signal quality of the neighboring CDMA2000 cell.

For details, see 3GPP2 C.S0005-A.
iteria for Reselection to a Higher-Priority Cell
If CellResel.ThrshServLowQCfgInd is set to CFG(Configure) and SIB3 contains threshServingLowQ (set by CellResel.ThrshServLowQ), a UE reselects to a higher-priority inter-
frequency or inter-RAT neighboring cell when all the following conditions are met:
• The neighboring cell has one of the following measurement results:
◾ Neighboring E-UTRAN cell: The Squal values of measured neighboring cells are greater than the value of threshX-HighQ (configured in the
EutranInterNFreq.ThreshXHighQ parameter) broadcast in SIB5 within the inter-frequency neighboring cell reselection time (configured in the
EutranInterNFreq.EutranReselTime parameter) broadcast in SIB5. For details about how to calculate the Squal values, see 3.2.6 Intra-Frequency or Equal-
Priority Inter-Frequency Cell Reselection.
◾ Neighboring UTRAN FDD cell: The Squal values of measured neighboring cells are greater than the value of threshX-HighQ (configured in the
UtranNFreq.ThreshXHighQ parameter) broadcast in SIB6 within the neighboring UTRAN cell reselection time (configured in the
CellReselUtran.TreselUtran parameter) broadcast in SIB6.
◾ Neighboring UTRAN TDD cell: The Srxlev values of measured neighboring cells are greater than the value of threshX-High (configured in the
UtranNFreq.ThreshXHigh parameter) broadcast in SIB6 within the neighboring UTRAN cell reselection time (configured in the
◾ Neighboring GERAN cell: The Srxlev values of measured neighboring cells are greater than the value of threshX-High (configured in the
GeranNfreqGroup.ThreshXHigh parameter) broadcast in SIB7 within the neighboring GERAN cell reselection time (configured in the
CellReselGeran.TReselGeran parameter) broadcast in SIB7.
◾ Neighboring CDMA2000 cell: The Srxlev values of measured neighboring cells are greater than the value of threshX-High (configured in the
Cdma2000BandClass.Cdma20001XrttThreshXHigh and Cdma2000BandClass.Cdma2000HrpdThreshXHigh parameters) broadcast in SIB8 within the
neighboring CDMA2000 cell reselection time (configured in the CellReselCdma2000.Cdma1XrttTreselection and CellReselCdma2000.TreselectionHrpd
parameters) broadcast in SIB8.

If CellResel.ThrshServLowQCfgInd is set to NOT_CFG(Not configure) and SIB3 does not contain threshServingLowQ, a UE reselects to a higher-priority inter-frequency or
inter-RAT neighboring cell when all of the following conditions are met:
◾ Neighboring E-UTRAN cell: The Srxlev values of measured neighboring cells are greater than the value of threshX-High (configured in the
EutranInterNFreq.ThreshXhigh parameter) broadcast in SIB5 within the inter-frequency neighboring cell reselection time (configured in the
EutranInterNFreq.EutranReselTime parameter) broadcast in SIB5. For details about how to calculate the Srxlev values, see 3.2.6 Intra-Frequency or Equal-
Priority Inter-Frequency Cell Reselection.
◾ Neighboring UTRAN cell: The Srxlev values of measured neighboring cells are greater than the value of threshX-High (configured in the
UtranNFreq.ThreshXHigh parameter) broadcast in SIB6 within the neighboring UTRAN cell reselection time (configured in the
◾ Neighboring GERAN cell: The Srxlev values of measured neighboring cells are greater than the value of threshX-High (configured in the
GeranNfreqGroup.ThreshXHigh parameter) broadcast in SIB7 within the neighboring GERAN cell reselection time (configured in the
◾ Neighboring CDMA2000 cell: The Srxlev values of measured neighboring cells are greater than the value of threshX-High (configured in the
Cdma2000BandClass.Cdma20001XrttThreshXHigh and Cdma2000BandClass.Cdma2000HrpdThreshXHigh parameters) broadcast in SIB8 within the
If the highest ranked cell is unsuitable for a UE because it is included in a roaming-forbidden TA or because it does not belong to the RPLMN or an EPLMN, the UE does not
consider this cell as a candidate for reselection within 300 seconds.
selection to a Lower-Priority Cell
If CellResel.ThrshServLowQCfgInd is set to CFG(Configure) and SIB3 contains threshServingLowQ (set by CellResel.ThrshServLowQ), a UE reselects to a lower-priority inter-
frequency or inter-RAT neighboring cell when all the following conditions are met:
• No higher-priority inter-frequency or inter-RAT neighboring cell meets the cell reselection criteria.
NOTE:
For details about how to calculate the Squal value of the serving cell, see Cell Selection Criteria.
◾ Neighboring E-UTRAN cell: The Squal value of the serving cell is less than the value of threshServingLowQ broadcast in SIB3 and the Squal values of
measured neighboring cells are greater than the value of threshX-LowQ (configured in the EutranInterNFreq.ThreshXlowQ parameter) broadcast in SIB5
within the inter-frequency neighboring cell reselection time (configured in the EutranInterNFreq.EutranReselTime parameter) broadcast in SIB5. For
details about how to calculate the Squal values of the measured neighboring cells, see 3.2.6 Intra-Frequency or Equal-Priority Inter-Frequency Cell Reselection.
◾ Neighboring UTRAN FDD cell: The Squal value of the serving cell is less than the value of threshServingLowQ broadcast in SIB3 and the Squal values of
measured neighboring cells are greater than the value of threshX-LowQ (configured in the UtranNFreq.ThreshXLowQ parameter) broadcast in SIB6 within
the neighboring UTRAN cell reselection time (configured in the CellReselUtran.TreselUtran parameter) broadcast in SIB6.
◾ Neighboring UTRAN TDD cell: The Squal value of the serving cell is less than the value of threshServingLowQ broadcast in SIB3 and the Squal values of
measured neighboring cells are greater than the value of threshX-Low (configured in the UtranNFreq.ThreshXLow parameter) broadcast in SIB6 within
the neighboring UTRAN cell reselection time (configured in the CellReselUtran.TreselUtran parameter) broadcast in SIB6.
◾ Neighboring GERAN cell: The Squal value of the serving cell is less than the value of threshServingLowQ broadcast in SIB3 and the Srxlev values of
measured neighboring cells are greater than the value of threshX-Low (configured in the GeranNfreqGroup.ThreshXlow parameter) broadcast in SIB7
within the neighboring GERAN cell reselection time (configured in the CellReselGeran.TReselGeran parameter) broadcast in SIB7.
◾ Neighboring CDMA2000 cell: The Squal value of the serving cell is less than the value of threshServingLowQ broadcast in SIB3 and the Srxlev values of
measured neighboring cells are greater than the value of threshX-Low (configured in the Cdma2000BandClass.Cdma20001XrttThreshXLow and
Cdma2000BandClass.Cdma2000HrpdThreshXLow parameters) broadcast in SIB8 within the neighboring CDMA2000 cell reselection time (configured in
the CellReselCdma2000.Cdma1XrttTreselection and CellReselCdma2000.TreselectionHrpd parameters) broadcast in SIB8.
If CellResel.ThrshServLowQCfgInd is set to NOT_CFG(Not configure) and SIB3 does not contain threshServingLowQ, a UE reselects to a lower-priority inter-frequency or inter-
RAT neighboring cell when all the following conditions are met:
• No higher-priority inter-frequency or inter-RAT neighboring cell meets the cell reselection criteria.
NOTE:
For details about how to calculate the Srxlev value of the serving cell, see Cell Selection Criteria.
◾ Neighboring E-UTRAN cell: The Srxlev value of the serving cell is less than the value of threshServingLow (configured in the CellResel.ThrshServLow
parameter) broadcast in SIB3 and the Srxlev values of measured neighboring cells are greater than the value of threshX-Low (configured in the
EutranInterNFreq.ThreshXlow parameter) broadcast in SIB5 within the inter-frequency neighboring cell reselection time (configured in the
EutranInterNFreq.EutranReselTime parameter) broadcast in SIB5. For details about how to calculate the Srxlev values of the measured neighboring cells,
see 3.2.6 Intra-Frequency or Equal-Priority Inter-Frequency Cell Reselection.
◾ Neighboring UTRAN cell: The Srxlev value of the serving cell is less than the value of threshServingLow (configured in the CellResel.ThrshServLow
UtranNFreq.ThreshXLow parameter) broadcast in SIB6 within the neighboring UTRAN cell reselection time (configured in the CellReselUtran.TreselUtran
parameter) broadcast in SIB6.
◾ Neighboring GERAN cell: The Srxlev value of the serving cell is less than the value of threshServingLow (configured in the CellResel.ThrshServLow
GeranNfreqGroup.ThreshXLow parameter) broadcast in SIB7 within the neighboring GERAN cell reselection time (configured in the
◾ Neighboring CDMA2000 cell: The Srxlev value of the serving cell is less than the value of threshServingLow (configured in the CellResel.ThrshServLow
Cdma2000BandClass.Cdma20001XrttThreshXLow and Cdma2000BandClass.Cdma2000HrpdThreshXLow parameters) broadcast in SIB8 within the
3.2.8 Speed-based Cell Reselection

UE movement is classified, by speed, as either normal-, medium-, or high-speed. A UE may start at a normal speed and then accelerate. When the UE is moving at medium or
high speed, it quickly reselects to a cell. In such a case, related cell reselection parameters must be adjusted accordingly. Speed-based cell reselection is supported only when
cell reselection for UEs at normal speed has been enabled.
Speed-based cell reselection is enabled by setting CellResel.SpeedDepReselCfgInd to CFG(Configure) and a specific neighboring cell parameter to CFG(Configure). Table 3-1
lists the parameters for various neighboring cells.
Table 3-1 Neighboring cell parameters
Neighboring Cell Type Parameter

Neighboring Cell Type Parameter

Intra-frequency neighboring E-UTRAN cell CellResel.SpeedStateSfCfgInd
Inter-frequency neighboring E-UTRAN cell EutranInterNFreq.SpeedDependSPCfgInd
Neighboring UTRAN cell CellReselUtran.SpeedStateSfCfgInd
Neighboring GERAN cell CellReselGeran.SpeedStateSfCfgInd
Neighboring CDMA2000 HRPD cell CellReselCdma2000.SpeedStateSfCfgInd
Neighboring CDMA2000 1XRTT cell CellReselCdma2000.Cdma1XrttSpeedStateCfgInd
A UE determines its speed based on the system information broadcast by the eNodeB. The details are as follows:
• If the number of reselection cells does not exceed n-CellChangeMedium (configured in the CellResel.NCellChangeMedium parameter) or n-CellChangeHigh
(configured in the CellResel.NCellChangeHigh parameter) within the t-Evaluation duration (configured in the CellResel.TEvaluation parameter) and the number of
reselection cells does not exceed n-CellChangeMedium or n-CellChangeHigh during the subsequent t-HystNormal duration (configured in the CellResel.THystNormal
parameter), the UE is a normal-speed UE.
• A UE determines that it is moving at a medium speed when the number of reselected cells is greater than n-CellChangeMedium but less than or equal to
n-CellChangeHigh within the t-Evaluation period.
• A UE determines that it is moving at a high speed when the number of reselected cells is greater than n- CellChangeHigh within the t-Evaluation period.
NOTE:
If a UE repeatedly selects a cell, the cell is counted only once into the number of reselected cells.
Cell reselection time and hysteresis vary with the UE speed. The details are as follows:
• Table 3-2 describes cell reselection time required by normal-speed UEs.

• Table 3-3 describes cell reselection time required by medium-speed UEs.
• Table 3-4 describes cell reselection time required by high-speed UEs.
• Table 3-5 describes the reselection hysteresis for the UE at a specific speed.
Table 3-2 Cell reselection time required by normal-speed UEs.
Neighboring Cell System Cell Reselection Time Parameter

Type Information
Involved
Intra-frequency SIB3 t-ReselectionEUTRA t-ReselectionEUTRA is specified by CellResel.TreselEutran.

neighboring
E-UTRAN cell
Inter-frequency SIB5 t-ReselectionEUTRA t-ReselectionEUTRA is specified by EutranInterNFreq.EutranReselTime.

neighboring
E-UTRAN cell
Neighboring UTRAN SIB6 t-ReselectionUTRA t-ReselectionUTRA is specified by CellReselUtran.TReselUtran.

cell
Neighboring SIB7 t-ReselectionGERAN t-ReselectionGERAN is specified by CellReselGeran.TReselGeran.

GERAN cell
Neighboring SIB8 parametersHRPD.t-ReselectionCDMA2000 parametersHRPD.t-ReselectionCDMA2000 is specified by

CDMA2000 HRPD CellReselCdma2000.TreselectionHrpd.
cell
Neighboring SIB8 parameters1XRTT.t-ReselectionCDMA2000 parameters1XRTT.t-ReselectionCDMA2000 is specified by

CDMA2000 1XRTT CellReselCdma2000.Cdma1XrttTreselection.
cell
Table 3-3 Cell reselection time required by medium-speed UEs
Neighboring Cell Type System Cell Reselection Time Parameter

Information
Involved
Intra-frequency SIB3 t-ReselectionEUTRA x t-ReselectionEUTRA- • t-ReselectionEUTRA is specified by CellResel.TreselEutran.

neighboring SF.sf-Medium • t-ReselectionEUTRA-SF.sf-Medium is specified by
E-UTRAN cell CellResel.TReselEutranSfMedium.
Inter-frequency SIB5 t-ReselectionEUTRA x t-ReselectionEUTRA- • t-ReselectionEUTRA is specified by

neighboring SF.sf-Medium EutranInterNFreq.EutranReselTime.
E-UTRAN cell • t-ReselectionEUTRA-SF.sf-Medium is specified by
EutranInterNFreq.TReselEutranSfMedium.
Neighboring UTRAN SIB6 t-ReselectionUTRA x t-ReselectionUTRA- • t-ReselectionUTRA is specified by

cell SF.sf-Medium CellReselUtran.TReselUtran.
• t-ReselectionUTRA-SF.sf-Medium is specified by
CellReselUtran.TReselUtranSfMedium.
Neighboring GERAN SIB7 t-ReselectionGERAN x • t-ReselectionGERAN is specified by

cell t-ReselectionGERAN-SF.sf-Medium CellReselGeran.TReselGeran.
• t-ReselectionGERAN-SF.sf-Medium is specified by
CellReselGeran.TReselGeranSfMedium.
Neighboring SIB8 parametersHRPD.t-ReselectionCDMA2000 • parametersHRPD.t-ReselectionCDMA2000 is specified by

CDMA2000 HRPD x CellReselCdma2000.TreselectionHrpd.
cell parametersHRPD.t-ReselectionCDMA2000- • parametersHRPD.t-ReselectionCDMA2000-SF.sf-Medium is
SF.sf-Medium specified by CellReselCdma2000.TReselCdmaHrpdSfMedium.
SIB8 parameters1XRTT.t-ReselectionCDMA2000 • parameters1XRTT.t-ReselectionCDMA2000 is specified by

x CellReselCdma2000.Cdma1XrttTreselection.


Information
Involved
Neighboring parameters1XRTT.t-ReselectionCDMA2000- • parameters1XRTT.t-ReselectionCDMA2000-SF.sf-Medium
CDMA2000 1XRTT SF.sf-Medium is specified by CellReselCdma2000.Cdma1XrttSfMedium.
cell
Table 3-4 Cell reselection time required by high-speed UEs

Information
Involved
Intra-frequency SIB3 t-ReselectionEUTRA x t-ReselectionEUTRA- • t-ReselectionEUTRA is specified by

neighboring E-UTRAN SF.sf-High CellResel.TreselEutran.
cell • t-ReselectionEUTRA-SF.sf-High is specified by
CellResel.TReselEutranSfHigh.
Inter-frequency SIB5 t-ReselectionEUTRA x t-ReselectionEUTRA- • t-ReselectionEUTRA is specified by

neighboring E-UTRAN SF.sf-High EutranInterNFreq.EutranReselTime.
cell • t-ReselectionEUTRA-SF.sf-High is specified by
EutranInterNFreq.TReselEutranSfHigh.
Neighboring UTRAN SIB6 t-ReselectionUTRA x t-ReselectionUTRA- • t-ReselectionUTRA is specified by

cell SF.sf-High CellReselUtran.TReselUtran.
• t-ReselectionUTRA-SF.sf-High is specified by
CellReselUtran.TReselUtranSfHigh.
Neighboring GERAN SIB7 t-ReselectionGERAN x t-ReselectionGERAN- • t-ReselectionGERAN is specified by

cell SF.sf-High CellReselGeran.TReselGeran.
• t-ReselectionGERAN-SF.sf-High is specified by
CellReselGeran.TReselGeranSfHigh.
Neighboring SIB8 parametersHRPD.t-ReselectionCDMA2000 x • parametersHRPD.t-ReselectionCDMA2000 is specified

CDMA2000 HRPD cell parametersHRPD.t-ReselectionCDMA2000- by CellReselCdma2000.TreselectionHrpd.
SF.sf-High • parametersHRPD.t-ReselectionCDMA2000-SF.sf-High is
specified by CellReselCdma2000.TReselCdmaHrpdSfHigh.
Neighboring SIB8 parameters1XRTT.t-ReselectionCDMA2000 * • parameters1XRTT.t-ReselectionCDMA2000 is specified

CDMA2000 1XRTT parameters1XRTT.t-ReselectionCDMA2000- by CellReselCdma2000.Cdma1XrttTreselection.
cell SF.sf-High • parameters1XRTT.t-ReselectionCDMA2000-SF.sf-High is
specified by CellReselCdma2000.Cdma1XrttSfHigh.
Table 3-5 Cell reselection hysteresis
UE Speed System Cell reselection hysteresis Parameter

Information
Involved
Normal-speed UE SIB3 q-Hyst q-Hyst is specified by CellResel.Qhyst.
Medium-speed UE SIB3 q-Hyst + q-HystSF.sf-Medium • q-Hyst is specified by CellResel.Qhyst.

• q-HystSF.sf-Medium is specified by
CellResel.QHystSfMedium.
High-speed UE SIB3 q-Hyst + q-HystSF.sf-High • q-Hyst is specified by CellResel.Qhyst.

• q-HystSF.sf-High is specified by CellResel.QHystSfHigh.
Tracking Area Registration

A UE informs the EPC of its tracking area (TA) by TA registration. The TA is a concept introduced to the LTE/SAE system for location management of UEs. A TA is identified by
a tracking area identity (TAI), which consists of the MCC, MNC, and tracking area code (TAC).
TA registration can be performed in two ways: tracking area update (TAU) and Attach/Detach.
3.3.1 Tracking Area Update

A UE performs TA updates in the following situations. That is, the UE sends a TA update request when any of the following conditions is met (For details, see section 5.3.3.0
"Provision of UE's TAI to MME in ECM-CONNECTED state" in 3GPP TS 23.401 R10, which was released in March 2011):
• The UE detects that it has entered a new TA when it finds that the TAI in the system information is different from any TAI stored in its USIM.
• The periodic TA update timer expires. This timer length is delivered to the UE through a non-access stratum (NAS) message.
• The UE performs an inter-RAT cell reselection to an E-UTRAN cell.
• The RRC connection is released with the release cause "load re-balancing TAU required".
• The information on UE capabilities stored in the EPC changes.
• The information on Discontinuous Reception (DRX) parameters changes. For details, see 3.6 Paging.
The UE informs the EPC of its TA by TA update. The EPC will send paging messages to all eNodeBs in the TA.
3.3.2 Attach/Detach
When a UE needs to obtain services from a network but is not registered to the network, the UE performs an Attach procedure for TA registration. For the detailed Attach
procedure, see section 5.3.2.1 "E-UTRAN Initial Attach" in 3GPP TS 23.401 R10, which was released in March 2011.
After a successful Attach procedure, the UE is assigned an IP address. The Mobile Equipment Identity (MEI) of the UE will be sent to the Mobility Management Entity (MME) for
authentication.
When the UE fails to access the EPC or the EPC does not allow the access of the UE, a Detach procedure is initiated. After the Detach procedure, the EPC no longer pages the
UE.
Cell Reservation and Access Control

Cell reservation and access control are two mechanisms operators use to control their networks.
• The cell reservation mechanism controls cell selection and reselection procedures. Cells can be reserved only for UEs in idle mode.

• The access control mechanism is implemented for UEs on the basis of access classes. To implement access control, one or more access classes are allocated to a
UE and stored on the USIM, but access class 10 is signaled to the UE through system information.
3.4.1 Cell Reservation and Barring

UEs are notified of cell status by the following information in SIB1:
• cellBarred: specifies whether a cell is barred. The cell barred status is set by CELLACCESS.CellBarred. If a cell belongs to multiple PLMNs, the cell barred status is
shared by all the PLMNs.
• cellReservedForOperatorUse: specifies whether a cell is reserved. The cell reserved status is set by CELLOP.CellReservedForOp. Each PLMN has its own
reserved status.
Table 1 describes cell status, and respective selection and reselection principles.
Table 3-6 Selection and reselection principles for reserved and barred cells
Cell Type Cell Selection and Reselection Principle
Unbarred and unreserved for The UE can consider this cell a candidate during cell selection and reselection procedures.
operator use
Unbarred but reserved for During cell selection and reselection procedures:
operator use • If UEs of access class 11 or 15 camp on their HPLMNs or on EHPLMNs, the UEs treat this cell as a candidate cell.
• Otherwise, UEs treat this cell as a barred cell.
Barred cell During cell selection and reselection procedures:

• The UEs cannot select or reselect to this cell, not even for emergency calls.
• The UEs select another cell as follows:
◾ When intraFreqReselection (set by the CELLACCESS.IntraFreqResel parameter) in SIB1 indicates that
intra-frequency reselection is allowed, the UEs may select another cell on the same frequency if
reselection criteria are fulfilled. When CELLACCESS.IntraFreqResel in SIB1 indicates that intra-frequency
reselection is not allowed, the UEs do not reselect a cell on the same frequency as the barred cell. The
value of intraFreqReselection in SIB1 is specified by the CELLACCESS.IntraFreqResel parameter.
◾ The UEs exclude the barred cell as a candidate for cell selection or reselection for 300 seconds.
3.4.2 Access Control

Access classes are applicable to UE access over the Uu interface. There are 16 access classes, numbered from 0 to 15. The information about access classes 0 to 9 and 11 to
15 is stored in USIMs, and the information about access class 10 is signaled to UEs through system information broadcast to indicate whether cells allow emergency calls. For
details about the list of barred access classes and how UEs determine their access classes, see chapter 4 "Access control" in 3GPP TS 22.011 V10.0.0 and section 3.4 "Access
control" in 3GPP TS 23.122 V10.0.0.
The access class control method is used to control UE network access, as defined in 3GPP TS 36.331. For details about Huawei access control, see Access Class Control Feature
System Information Broadcast

This section describes the basic feature LBFD-002009 Broadcast of system information.
System Information (SI) messages are categorized, based on their contents, into one master information block (MIB) and multiple system information blocks (SIBs). The number
of SIBs is specified in the latest 3GPP protocols. SI messages are transmitted over the BCCH. Figure 3-3 shows the relationships between the MIB and the SIBs.
The MIB is transmitted over the BCH through an independent RRC message. The scheduling period of the MIB is always 40 ms. The BCH is predefined by transport format.
Therefore, the UE receives the MIB on the BCH without obtaining other information on the network.
SIB1 is transmitted over the downlink shared channel (DL-SCH) through an independent RRC message. The scheduling period of SIB1 is always 80 ms. Other SIBs are
transmitted over the DL-SCH through SI messages, and their scheduling periods can be separately set. The SIBs with the same scheduling period can be transmitted through
the same SI message, and one SIB can be contained in only one SI message. SIB1 carries the scheduling period information of all the SIBs and the mapping between SIBs and
SI messages. SIB2 must be mapped to the SI message that corresponds to the first entry in the list of SI messages in the scheduling information. On the physical dedicated
control channel (PDCCH), the UE obtains time and frequency data for the SIB by parsing the SI-Radio Network Temporary Identifier (SI-RNTI).
Only SIB6 and SIB7 delivery is under switch control:
• SIB6 is broadcast only when CellSiMap.SiSwitch(Sib6Switch) is turned on and the CELLRESELUTRAN MO has been configured.
• SIB7 is broadcast only when CellSiMap.SiSwitch(Sib7Switch) is turned on and the CELLRESELGERAN MO has been configured.
• When the contents of the SI are changed, the eNodeB sends paging messages to instruct the UE in idle mode and UE in connected mode to read the new SI
messages.
Figure 3-3 Relationships between SI messages
3.5.1 System Information Block Contents

The MIB and each SIB contain different information. Table 3-7 lists the main contents of the MIB and each SIB. For details, see sections 6.2.2 "Message definitions" and 6.3.1
"System information blocks" in 3GPP TS 36.331 R10, which was released in March 2011.
Table 3-7 Contents of the MIB and SIBs
SI Block Content
MIB Downlink bandwidth of a cell, Physical HARQ Indication Channel (PHICH) parameters, and
System Frame Number (SFN)
SIB1 Parameters related to cell access and cell selection and scheduling information of SI messages

SI Block Content
SIB2 Common radio parameters used by all the UEs in a cell
SIB3 Common cell reselection parameters for all the cells and intra-frequency cell reselection
parameters
SIB4 Intra-frequency neighboring cell list, reselection parameters of each neighboring cell used for cell
reselection, and intra-frequency cell reselection blacklist
SIB5 Non-serving E-UTRA frequency list and reselection parameters of each frequency used for cell
reselection
Inter-frequency neighboring cell list and reselection parameters of each neighboring cell used for
cell reselection
Inter-frequency cell reselection blacklist
SIB6 Universal Terrestrial Radio Access (UTRA) frequency division duplex (FDD) neighboring
frequency list and reselection parameters of each frequency used for cell reselection
UTRA time division duplex (TDD) neighboring frequency list and reselection parameters of each
frequency used for cell reselection
SIB7 GERAN neighboring frequency list and reselection parameters of each frequency used for cell
reselection
SIB8 CDMA2000 pre-registration information

CDMA2000 neighboring frequency band list and reselection parameters of each band used for
cell reselection
CDMA2000 neighboring cell list of neighboring frequency band
SIB9 Name of the home eNodeB
SIB10 Earthquake and Tsunami Warning System (ETWS) primary notification
SIB11 ETWS secondary notification
SIB12 CMAS notification
SIB13 MBMS control information
SIB14 Extended Access Barring (EAB) parameters
SIB15 MBMS Service Area Identities (SAI)
SIB16 GPS time and Coordinated Universal Time (UTC)
3.5.2 System Information Scheduling Periods

The scheduling period for the MIB is fixed at 40 ms. The first transmission of the MIB is scheduled in subframe 0 of radio frames for which the SFN mod 4 = 0, and repetitions
are scheduled in subframe 0 of the last three radio frames in each period.
The scheduling period for the SIB1 is fixed at 80 ms. The first transmission of the SIB1 is scheduled in subframe 5 of radio frames for which the SFN mod 8 = 0, and repetitions
are scheduled in subframe 5 of the later radio frames for which SFN mod 2 = 0 in each period.
The scheduling periods for other SIBs are specified by CellSiMap.SibxPeriod (x indicates 2, 3...). The mapping between an SIB and the SI is affected by the scheduling period
of the SIB, number of SIBs, and bandwidth resources. The SIBs with the same scheduling period map onto the same SI. However, the number of SIBs that can map onto the
same SI is limited. The eNodeB must take into account the minimum UE capability to ensure that all the UEs in a cell can read the system information.
An SI message can be transmitted only within a specific duration in the scheduling period, and the specific duration is called SI window. Only one type of SI message can be
transmitted in an SI window. Within the SI window, the corresponding SI message can be transmitted a number of times in any subframe other than multimedia broadcast
multicast service single frequency network (MBSFN) subframes, uplink subframes in TDD, and the subframes in which the SIB1 is transmitted. The length of the SI window is
determined by the system. For details about the scheduling of the SI, see section 5.2 "System information" in 3GPP TS 36.331 R10, which was released in March 2011.
3.5.3 System Information Update

A UE reads SI messages in the following scenarios:
• The UE has been powered on and is selecting a cell to camp on.

• The UE is performing cell reselection.
• The UE has performed a handover.
• The UE is entering E-UTRAN from another system.
• The UE is returning from an area with no coverage.
After obtaining the SI message, the UE does not repeatedly read the message. It rereads and updates the SI message only when any of the following conditions is met:
• The UE receives the SI message change notification in the paging message transmitted from the eNodeB.
• The UE receives the ETWS or CMAS message broadcast notification in the paging message transmitted from the eNodeB.
• When the UE receives an SI message, it has been 3 hours since it received the previous SI message.
When receiving the SI message change notification in the paging message, the UE does not immediately update the SI message. Instead, it receives the SI message updated
by the eNodeB in the next message modification period. For details about the SI message update, see section 5.2 "System information" in 3GPP TS 36.331 R10, which was
Figure 3-4 shows the SI message update procedure. The modification period of the SI message is N radio frames, starting from a radio frame for which SFN mod n = 0. During
modification period number n, the eNodeB transmits the paging message to inform UEs in RRC_IDLE mode and UEs in RRC_CONNECTED mode about the SI message
change when a paging cycle arrives. When the n+1 modification period arrives, the eNodeB transmits the updated SI message. In this figure, different colors indicate SI
messages with different contents.
Figure 3-4 SI message update procedure
where
• The length of the SI modification period (N radio frames) = modificationPeriodCoeff x defaultPagingCycle, where modificationPeriodCoeff and defaultPagingCycle are
broadcast in SIB2.
◾ modificationPeriodCoeff is the coefficient of the modification period, indicating the minimum number of times the UE monitors paging messages within the
SI message modification period. It is set by the BcchCfg.ModifyPeriodCoeff parameter.

◾ defaultPagingCycle is the default paging cycle in units of radio frames. It is set by the PCCHCfg.DefaultPagingCycle parameter.
• During eNodeB notification update, the length of the paging message delivery is controlled by CellSiMap.SibUpdOptSwitch.
◾ When CellSiMap.SibUpdOptSwitch is set to SibPagingOptCtrlSwitch, that is, the switch is turned on (default setting: turned off), the length is equal to
the length of the SI modification period.
◾ When the switch is turned off (default setting), the length is occasionally shorter than the length of the SI modification period.
When SI messages (except SIB10, SIB11, SIB12, and SIB14) are updated, the eNodeB changes systemInfoValueTag in SIB1. The UE reads the value and compares it with the
one it read last time. If the value has changed, it is an indication that the SI message has changed. If the value has not changed, it is an indication that the SI message has not
changed.
If SIB10, SIB11, SIB12, or SIB14 has changed, the eNodeB does not change systemInfoValueTag in SIB1. Instead, the eNodeB delivers paging messages to the UE, notifying
that the ETWS message and commercial mobile alert system (CMAS) have changed.
For the CDMA2000 system time changes in SIB8 and the UTC time changes in SIB16, the eNodeB does not change systemInfoValueTag in SIB1 or notify the UE of the SI
message change in paging messages.
The UE reads the SI message again 3 hours after receiving an SI message. In this case, the UE reads all the SI messages regardless of whether systemInfoValueTag has
changed.
Paging
This section describes the basic feature LBFD-002011 Paging.
3.6.1 Triggering of Paging

Paging is a procedure of transmitting paging messages to UEs in RRC_IDLE mode or informing all UEs in RRC_CONNECTED mode and RRC_IDLE mode about an SI
message change. A paging procedure can be initiated by either an MME or an eNodeB.
When an MME initiates a paging procedure, the paging message contains a tracking area list (TAL) for the concerned UE. In all the cells within the TAs on the list, the eNodeBs
transmit the paging message over the paging control channel (PCCH) to page the UE. To increase the probability that the UE successfully receives the message, the eNodeBs
send the paging message over the radio interface a number of times specified by the PCCHCfg.PagingSentNum parameter. The paging message contains the domain
information and UE identity. The domain information indicates the origin of paging, and the UE identity may be the S-temporary mobile subscriber identity (S-TMSI) or
international mobile subscriber identity (IMSI) of the UE.
When the SI message changes, the eNodeB transmits a paging message to notify all UEs in RRC_CONNECTED mode and RRC_IDLE mode in the cell and transmits the
updated SI message in the next SI message modification period. To ensure that all of these UEs receive the system information, the eNodeB transmits the paging message on
all possible occasions in discontinuous reception (DRX) cycles.
Though paging is triggered from different Network Elements (NEs), the paging mechanism on the Uu interface is the same.
3.6.2 Paging Mechanism over the Uu Interface

UEs in idle mode receive paging messages using DRX to reduce power consumption. The frames that paging messages are transmitted on over the Uu interface are fixed.
These frames are indicated by the paging frames (PFs) and paging occasion (PO) subframes. One PF is one radio frame, which may contain one or multiple POs, as shown in
Figure 3-5. One PO is a subframe where the paging radio network temporary identifier (P-RNTI) is contained. The PO is transmitted over the PDCCH. In accordance with 3GPP
specifications, the P-RNTI value is fixed. UEs read paging messages over the physical downlink shared channel (PDSCH) according to the P-RNTI.
Figure 3-5 Paging mechanism
The PF number and PO subframe number can be calculated based on the IMSI of the UE, DRX cycle, and number of PO subframes within a DRX cycle. Frame numbers are
stored in the SI that contains the DRX parameters of the UE. The PF number and PO subframe number change with the DRX parameters.
The SFN of a PF is calculated as follows: SFN mod T = (T div N) x (UE_ID mod N)
The subframe number i_s of a PO in FDD is listed in Table 3-8. The subframe number i_s of a PO is derived from the following formula: i_s = floor (UE_ID/N) mod Ns, where
floor represents rounding (UE_ID/N) down to the nearest integer.
Table 3-8 Subframe number i_s of a PO in FDD
Ns PO when i_s=0 PO when i_s=1 PO when i_s=2 PO when i_s=3
1 9 N/A N/A N/A
2 4 9 N/A N/A
4 0 4 5 9
The variables in these formulas are as follows:
• T: DRX cycle. The UE, eNodeB, and MME calculate their own DRX cycles as follows:
◾ Calculation of DRX cycles by the UE
(1) When a UE specific paging cycle is not used, the UE uses the defaultPagingCycle IE value broadcast in SIB2 by the eNodeB as its DRX cycle. The
defaultPagingCycle IE value is specified by the PCCHCfg.DefaultPagingCycle parameter.
(2) When the UE specific paging cycle is used, the UE notifies the MME of the paging cycle length using NAS messages. In addition, the UE compares
the UE specific paging cycle length with the defaultPagingCycle IE value and uses the smaller one as its DRX cycle.
◾ Calculation of DRX cycles by the eNodeB
(1) If the MME has specified a paging DRX cycle in a paging message, the eNodeB compares the paging DRX cycle length with the DefaultPagingCycle
IE value, and uses the smaller one as the paging DRX cycle.
(2) If the MME does not specify a paging DRX cycle in a paging message, the eNodeB uses the defaultPagingCycle IE value as the paging DRX cycle.
◾ Calculation of DRX cycles by the MME
If the UE specific paging cycle is used, the MME specifies the paging DRX cycle (the UE specific paging cycle) in a paging message to the eNodeB. If the
UE specific paging cycle is not used, the MME sends the eNodeB a paging message without containing the paging DRX cycle.

NOTE:
◾ According to section 5.13 in 3GPP TS 23.401 R11 released in December, 2013, the MME is only supposed to specify a paging DRX cycle in a paging
message to the eNodeB when the UE specific paging cycle is being used. In this situation, the paging DRX cycle is equal to the UE specific paging cycle.
Otherwise, the MME does not include a paging DRX cycle in the paging message.
◾ In the S1 setup process, the eNodeB sends the MME the eNodeB-specific default paging DRX cycle (specified by the
GlobalProcSwitch.S1DefaultPagingDrxSelect parameter) for the MME to determine the paging response timeout length. However, not all MMEs comply
with 3GPP specifications. Even when the UE specific paging cycle is not used, these non-compliant MMEs specify a paging DRX cycle, equal to the
default paging DRX cycle reported by the eNodeB over the S1 interface, in a paging message to the eNodeB. In this case, if the default paging DRX cycle
is less than the value of the defaultPagingCycle IE value, the DRX cycle length calculated by the eNodeB differs from that calculated by the UE. To
prevent this problem, it is recommended that the length of the default paging DRX cycle be greater than or equal to the defaultPagingCycle IE value.
• N is min(T, nB). The PCCHCfg.Nb parameter specifies nB. It can be set to 4T, 2T, T, T/2, T/4, T/8, T/16, or T/32.
• Ns is max(1,nB/T).
• UE_ID: equal to IMSI mod1024. If a UE without an IMSI makes an emergency call, the UE uses the default UE_ID value of 0.
◾ If paging is triggered by the MME, the UE_ID value is the UE identity index value contained in the paging message sent over the S1 interface.
◾ If paging is triggered by the eNodeB and no UE_ID is available, the UE uses the default UE_ID value of 0.
3.6.3 Paging Handling Procedure

During system information update, the eNodeB generates a paging message and sets the systemInfoModification IE at each subsequent PO in a single DRX cycle. To page a
single UE, the eNodeB calculates the nearest PO for the UE, generates a paging message, and sets the pagingRecord IE. If the eNodeB is scheduled to send the pagingRecord
or a systemInfoModification IE for another UE in this PO, the eNodeB includes all the information in the paging message.
UEs use DRX in idle mode to reduce power consumption. In each DRX cycle, a UE monitors only its own POs. In one of the POs, the UE interprets the P-RNTI on the PDCCH
and then reads the paging message on the PDSCH based on the P-RNTI. Multiple UEs may have the same PO.
A UE in idle mode starts its receiver to monitor the PDCCH at POs in each DRX cycle. After the UE detects its own paging message, the UE sends a paging response, which is
generated at the NAS, to the MME. The paging response is indicated by mt-Access, the value of the EstablishmentCause IE contained in the RRC Connection Request
message.
If the UE does not interpret the P-RNTI on the PDCCH, or if the UE interprets the P-RNTI but does not detect its pagingRecord, the UE shuts down the receiver and enters the
sleep mode to reduce power consumption.
When a cell starts broadcasting system information, the cell sends paging messages to inform all UEs in its coverage of system information update. To ensure that all UEs can
be paged successfully, the cell broadcasts the paging messages using the maximum values of defaultPagingCycle (256 radio frames) and Ns (4).
3.6.4 Scheduling of Paging Messages

The eNodeB determines the coding rate for paging messages according to the value of CellDlschAlgo.RarAndPagingCR. The PCCHCfg.MaxPagingRecordsNum parameter
specifies the maximum number of UEs that can be included in a paging message.
• If the number of UEs to be paged on each paging occasion is less than or equal to the value of PCCHCfg.MaxPagingRecordsNum, the eNodeB sends the paging
messages for all the UEs on one paging occasion.
• If the number of UEs to be paged on each paging occasion is greater than the value of PCCHCfg.MaxPagingRecordsNum, the eNodeB sends the paging messages
to the UEs according to the strategy specified by PCCHCfg.PagingStrategy.
◾ FIFO
If PCCHCfg.PagingStrategy is set to PAGING_STRATEGY_FIFO(First-in First-out Strategy), the eNodeB preferentially sends the paging messages for
N UEs that arrive earlier in a paging occasion and sends the paging messages for other UEs in the next paging cycle. N is specified by the
PCCHCfg.MaxPagingRecordsNum parameter.
◾ Priority Differentiation
If PCCHCfg.PagingStrategy is set to PAGING_STRATEGY_DIFFPRI(Priority Differentiation Strategy), the eNodeB preferentially selects CS paging
messages and paging messages that have paging priorities and then selects PS paging messages that do not have paging priorities. The eNodeB then
sends the paging messages for N UEs in a paging occasion and sends the paging messages for other UEs in the next paging period. N is specified by the
PCCHCfg.MaxPagingRecordsNum parameter.
The paging message priority information is carried in the paging message sent by the MME to the eNodeB. Value CS of the CN Domain field in a paging
message indicates CS paging. CS paging messages are used in the CSFB service. Value PS of the CN Domain field in a paging message indicates PS
paging. PS paging messages are used in the packet data service or VoLTE service.
Scheduling of paging messages supports interference randomization (referred to as the interference randomization-based paging message scheduling function). Specifically, the
first RB to be allocated to paging messages in a cell varies according to the result of (PCI mod 3) for the cell. Using this RB allocation method ensures that RBs allocated to
paging messages in different cells do not conflict with each other, reducing the inter-message interference.
The interference randomization-based paging message scheduling function is specified by PagingInterfRandSwitch under CellAlgoSwitch.DlSchSwitch. For details about this
function, see Scheduling Feature Parameter Description.
4 Related Features
LBFD-002009 Broadcast of system information
erequisite Features
None
None
pacted Features
None
LBFD-002011 Paging
erequisite Features
None
None
pacted Features
None
LBFD-00201803 Cell Selection and Re-selection

erequisite Features
None
None
pacted Features
LOFD-001032 Intra-LTE Load Balancing LOFD-001032 Intra-LTE Load Balancing uses the dedicated priorities of
neighboring cells.
5 Network Impact
LBFD-002009 Broadcast of system information
stem Capacity
No impact.
twork Performance
Broadcast of system information enables UEs in idle mode to acquire system information so that they can access the network.
Sib6Switch and Sib7Switch of the SiSwitch parameter specify whether the eNodeB broadcasts SIB6 and SIB7, respectively, and whether UEs in RRC_IDLE mode can
reselect to UTRAN and GERAN. If the two switches are turned off, UEs cannot reselect to UTRAN or GERAN. In this case, there may be more bad-quality signals on the
E-UTRAN, which may cause the following impacts:
• Jeopardized performance counters, including the PRACH access success rate, RRC setup success rate, eRAB setup success rate, call drop rate, RRC
reestablishment success rate, cell throughput rate, user throughput rate, IBLER, RBLER, packet loss rate, MOS, IDLE2ACEIVE activation delay, attach delay, and
other delays (such as web browsing or FTP download)
• More online subscribers
• Higher PRB usage efficiency
The specific impacts vary according to user distribution and cannot be quantified. You can determine the impacts based on live network conditions.
LBFD-002011 Paging
stem Capacity
No impact.
twork Performance
Paging ensures that mobile-terminated services can reach the UEs in idle mode.
LBFD-00201803 Cell Selection and Re-selection
stem Capacity
No impact.
twork Performance
Cell selection and reselection ensures sufficient network coverage so that UEs in idle mode will not become out of service when moving between cells.
When to Use
LBFD-002009 Broadcast of system information, LBFD-002011 Paging, and LBFD-00201803 Cell Selection and Re-selection (intra-RAT) are fundamental to coverage continuity
and are enabled by default.
LBFD-00201803 Cell Selection and Re-selection is recommended to ensure coverage continuity when multiple systems coexist. It is not recommended when LTE coverage is
contiguous and LTE load is light.
By default, Sib6Switch and Sib7Switch are turned on. Turn off Sib6Switch and Sib7Switch only when you want to prohibit UEs in E-UTRAN cells from reselecting to UTRAN
and GERAN cells, respectively. For example, turn them off during UTRAN and GERAN network reconstruction.
Deployment
6.2.1 Requirements
her Features
For details, see 4 Related Features.
rdware
None
cense
None
her Requirements
None


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.
quired Data
Configuring frequencies and neighboring cells

For details, see Intra-RAT Mobility Management in Connected Mode Feature Parameter Description and Inter-RAT Mobility Management in Connected Mode Feature Parameter Description.
Configuring cell reselection information
The following table describes the parameters that must be set in the CellResel MO to configure cell reselection.
Parameter Name Parameter ID Data Source Setting Notes
Local cell ID CellResel.LocalCellId Radio network plan Set this parameter to the actual cell ID.
(internal plan)
Threshold for non-intra CellResel.SNonIntraSearchCfgInd Engineering design If this parameter is set to NOT_CFG(Not configure), a UE continuously
freq measurements measures the signal quality of inter-frequency or inter-RAT cells whose
configure indicator priorities are lower than or equal to that of the serving cell, regardless of
the signal quality of the serving cell. As a result, the UE uses more
power. Therefore, you are advised to set this parameter to CFG
(Configure).
Threshold for intra freq CellResel.SIntraSearchCfgInd Engineering design If this parameter is set to NOT_CFG(Not configure), a UE keeps
measurements measuring intra-frequency cells. This process occurs regardless of the
configure indicator signal quality in the serving cell. Therefore, you are advised to set this
parameter to CFG(Configure).
Cell reselection priority CellResel.CellReselPriority Default This parameter specifies the cell reselection priority of the serving
value/Recommended value frequency. The value 0 indicates the lowest priority. In network planning
scenarios, ensure that the value of this parameter is lower than the
priority of reselection to UTRAN cells.
Serving frequency CellResel.ThrshServLowQCfgInd Engineering design This parameter indicates whether to set the RSRQ threshold for
lower priority RSRQ reselection to cells on the serving frequency.
threshold configure
indicator
Minimum required CellResel.QQualMinCfgInd Engineering design This parameter specifies the minimum required quality level configure
quality level configure indicator.
indicator
Ue max power allowed CellResel.PMaxCfgInd Engineering design This parameter indicates whether to configure the maximum TX power
configure indicator of the UE in the intra-frequency neighboring E-UTRAN cell. If this
parameter is set to CFG(Configure), the maximum TX power is
specified by CellResel.PMax. If the value of this parameter is set to
NOT_CFG(Not configure), the maximum TX power is subject to the UE
capability.
Max transmit power CellResel.PMax Default -

allowed value/Recommended value
enario-specific Data
To configure reselection to E-UTRAN inter-frequency, UTRAN, GERAN, or CDMA2000 cells, set the cell reselection priorities and relevant parameters when configuring
neighboring frequencies.
• Reselection to inter-frequency E-UTRAN cells

The following table describes the parameters that must be set in the EutranInterNFreq MO to configure a non-serving E-UTRA frequency.
Local cell ID EutranInterNFreq.LocalCellId Radio network plan -

(internal plan)
Inter frequency EutranInterNFreq.CellReselPriorityCfgInd Default Set this parameter to CFG(Configure).

cell resel priority value/Recommended
configure value
indicator
Inter frequency EutranInterNFreq.CellReselPriority Radio network plan This parameter specifies the cell reselection priority for the
cell resel priority (internal plan) frequency. Set this parameter to a value within the range of
0 to 7. A larger parameter value leads to a higher probability
of measuring neighboring cells and redirecting UEs.
• Reselection to UTRAN cells

The following table describes the parameter that must be set in the CellSiMap MO to configure the SIB6 switch.
Cell System CellSiMap.SiSwitch Radio network plan (internal plan) By default, turn on the Sib6Switch switch to allow UEs to reselect to
Information Switch the UTRAN system. Turn off the Sib6Switch only when you want to
prohibit UEs from reselecting to the UTRAN system.
The following table describes the parameter that must be set in the CellReselUtran MO to configure cell reselection to UTRAN.
Local cell ID CellReselUtran.LocalCellId Radio network plan (internal -

plan)
The following table describes the parameters that must be set in the UtranNFreq MO to configure UTRAN frequencies.
Local cell ID UtranNFreq.LocalCellId Radio network plan (internal plan) -


Reselection UtranNFreq.CellReselPriorityCfgInd Default value/Recommended value Set this parameter to CFG(Configure). If this parameter is
priority set to NOT_CFG(Not configure), the cell reselection
configure priority cannot be set.
indicator
Cell reselection UtranNFreq.CellReselPriority Radio network plan (internal plan) -

priority
• Reselection to GERAN cells

The following table describes the parameter that must be set in the CellSiMap MO to configure the SIB7 switch.
Cell System CellSiMap.SiSwitch Radio network plan (internal plan) By default, turn on the Sib7Switch switch to allow UEs to reselect to
Information Switch the GERAN system. Turn off the Sib7Switch only when you want to
prohibit UEs from reselecting to the GERAN system.
The following table describes the parameter that must be set in the CellReselGeran MO to configure cell reselection to GERAN.
Local cell ID CellReselGeran.LocalCellId Radio network plan (internal plan) -
The following table describes the parameters that must be set in the GeranNfreqGroup MO to configure GERAN frequencies.
Parameter Parameter ID Data Source Setting Notes

Name
Local cell ID GeranNfreqGroup.LocalCellId Radio network plan (internal -

plan)
BCCH group GeranNfreqGroup.BcchGroupId Radio network plan (internal This parameter specifies the ID of the GERAN carrier
ID plan) frequency group. In cell reselection, GERAN frequencies
are grouped. Each GERAN frequency group uses the
same GERAN cell reselection parameters. Set this
parameter to a value ranging from 0 to 31.
Cell GeranNfreqGroup.CellReselPriorityCfgInd Engineering design Set this parameter to CFG(Configure).

reselection
priority
configure
indicator
Cell GeranNfreqGroup.CellReselPriority Engineering design -

reselection
priority
• Reselection to CDMA2000 cells

The following table describes the parameters that must be set in the CellReselCdma2000 MO to configure cell reselection to CDMA2000.

Name
Local cell ID CellReselCdma2000.LocalCellId Radio network plan -

(internal plan)
System time CELLRESELCDMA2000.SysTimeCfgInd Engineering design If the eNodeB supports time synchronization
information (TASM.CLKSYNCMODE set to TIME(TIME)), set this
configure parameter to CFG(Configure).
indicator If the eNodeB supports frequency synchronization
(TASM.CLKSYNCMODE set to FERQ(FERQ)), set this
parameter to NOT_CFG(Not configure).
HRPD CellReselCdma2000.HrpdParaCfgInd Engineering design Set this parameter to CFG(Configure) to allow UEs to
parameters reselect to CDMA2000 HRPD cells.
configure
indicator
HRPD cell CellReselCdma2000.HrpdCellReselectParamCfgInd Engineering design Set this parameter to CFG(Configure) to allow UEs to
reselection reselect to CDMA2000 HRPD cells.
configure
indicator
1XRTT CellReselCdma2000.Cdma1XrttParaCfgInd Engineering design Set this parameter to CFG(Configure) to allow UEs to
parameters reselect to CDMA2000 1xRTT cells.
configure
indicator
1XRTT cell CellReselCdma2000.Cdma1XrttCellReselCfgInd Engineering design Set this parameter to CFG(Configure) to allow UEs to
reselection reselect to CDMA2000 1xRTT cells.
configure
indicator
The following table describes the parameters that must be set in the Cdma2000BandClass MO to configure CDMA2000 frequency bands.
Local cell ID Cdma2000BandClass.LocalCellId Radio network plan -

(internal plan)
Band class Cdma2000BandClass.BandClass Radio network plan -

(internal plan)
Cdma2000BandClass.Cdma20001XrttCellReselInd


CDMA20001XRTT Radio network plan This parameter specifies whether to set the reselection
cell reselection (internal plan) priority of a CDMA2000 1xRTT cell. When this
indicator parameter is set to NOT_CFG(Not configure), the
system information does not contain the reselection
priority of a CDMA2000 1xRTT cell.
CDMA20001XRTT Cdma2000BandClass.Cdma20001XrttCellReselPri Radio network plan This parameter specifies the cell reselection priority for
cell reselection (internal plan) the frequency. Set this parameter to a value within the
priority range of 0 to 7.
CDMA2000HRPD Cdma2000BandClass.Cdma2000HrpdCellReselInd Radio network plan Specifies whether to set the reselection priority of a
cell reselection (internal plan) CDMA2000 HRPD cell. When this parameter is set to
indicator NOT_CFG(Not configure), the system information
does not contain the reselection priority of a
CDMA2000 HRPD cell.
CDMA2000HRPD Cdma2000BandClass.Cdma2000HrpdCellReselPri Radio network plan This parameter specifies the cell reselection priority for
cell reselection (internal plan) the frequency. Set this parameter to a value within the
priority range of 0 to 7.
• Speed-based cell reselection

The following table describes the parameters that must be set in the CellResel MO to configure speed-based cell reselection parameters and intra-frequency
neighboring E-UTRAN cell parameters.
Speed-dependent CellResel.SpeedDepReselCfgInd Engineering design Indicates whether to set speed-based cell reselection
reselection parameters. Speed-based cell reselection is enabled by setting
parameter this parameter to CFG(Configure) and a specific neighboring
configure indicator cell parameter to CFG(Configure).
Speed state scale CellResel.SpeedStateSfCfgInd Engineering design Indicates whether to enable speed-based cell reselection to
factor configure intra-frequency neighboring E-UTRAN cells. Set this parameter
indicator to CFG(Configure) to enable speed-based cell reselection to
intra-frequency neighboring E-UTRAN cells.
The following table describes the parameters that must be set in the EutranInterNFreq MO to configure inter-frequency neighboring E-UTRAN cell parameters.
Speed EutranInterNFreq.SpeedDependSPCfgInd Default This parameter specifies whether to enable speed-based cell
dependent value/Recommended reselection to inter-frequency neighboring E-UTRAN cells. Set
resel value this parameter to CFG(Configure) to enable speed-based cell
parameter reselection to inter-frequency neighboring E-UTRAN cells.
configuring
indicator
Scaling factor EutranInterNFreq.TReselEutranSfMedium Engineering design A smaller value of this parameter leads to a shorter decision
of treseleutran duration of reselection to a cell on a non-serving E-UTRA
in medium frequency for a medium-mobility UE and a higher probability
mobility state of cell reselection. A larger value of this parameter leads to
the opposite effect. If the value of this parameter is too large
or too small, the access success rate is affected.
Scaling factor EutranInterNFreq.TReselEutranSfHigh Engineering design A smaller value of this parameter leads to a shorter decision
of treseleutran duration of reselection to a cell on a non-serving E-UTRA
in high mobility frequency for a high-mobility UE and a higher probability of
state cell reselection. A larger value of this parameter leads to the
opposite effect. If the value of this parameter is too large or
too small, the access success rate is affected.
The following table describes the parameters that must be set in the CellReselUtran MO to configure neighboring UTRAN cell parameters.
Speed state CellReselUtran.SpeedStateSfCfgInd Engineering design This parameter specifies whether to enable speed-based cell
scale factor reselection to neighboring UTRAN cells. Set this parameter to
configure CFG(Configure) to enable speed-based cell reselection to
indicator neighboring UTRAN cells.
The following table describes the parameter that must be set in the CellReselGeran MO to configure neighboring GERAN cell parameters.
Speed state CellReselGeran.SpeedStateSfCfgInd Engineering design This parameter specifies whether to enable speed-based cell
scale factor reselection to neighboring GERAN cells. Set this parameter to
configure CFG(Configure) to enable speed-based cell reselection to
indicator neighboring GERAN cells.
The following table describes the parameters that must be set in the CellReselCdma2000 MO to configure neighboring CDMA2000 cell parameters.

Name
Speed state CellReselCdma2000.SpeedStateSfCfgInd Engineering design This parameter specifies whether to enable speed-based
scale factor cell reselection to neighboring CDMA2000 HRPD cells. Set
configure this parameter to CFG(Configure) to enable speed-based
indicator cell reselection to neighboring CDMA2000 HRPD cells.
1XRTT CellReselCdma2000.Cdma1XrttSpeedStateCfgInd Engineering design This parameter specifies whether to enable speed-based
speed state cell reselection to neighboring CDMA2000 1xRTT cells. Set
scale factors this parameter to CFG(Configure) to enable speed-based
configure cell reselection to neighboring CDMA2000 1xRTT cells.
indicator


ML Commands
For details about how to configure frequencies and neighboring cells, see Intra-RAT Mobility Management in Connected Mode Feature Parameter Description and Inter-RAT Mobility
Management in Connected Mode Feature Parameter Description.
1. Run the MOD EUTRANINTERNFREQ command with Inter frequency cell resel priority configure indicator set to CFG(Configure) and with Local cell ID and
Inter frequency cell resel priority set based on actual conditions.
1. Run the MOD CELLSIMAP command with Sib6Switch(Sib6Switch) under Cell System Information Switch selected.
2. Run the ADD CELLRESELUTRAN command to add the configurations related to reselection to UTRAN cells. In this step, set Local cell ID based on actual
conditions, and retain the default values for other parameters.
3. Run the MOD CELLRESEL command with Cell reselection priority set to an appropriate value.
4. Run the MOD UTRANNFREQ command with Reselection priority configure indicator set to CFG(Configure) and with Local cell ID, Downlink UARFCN, and
Cell reselection priority set based on actual conditions.
5. Run the MOD RRCCONNSTATETIMER command to set Ue inactive timer to a value rather than 0.
1. Run the MOD CELLSIMAP command with Sib7Switch(Sib7Switch) under Cell System Information Switch selected.
2. Run the ADD CELLRESELGERAN command to add the configurations related to reselection to GERAN cells. In this step, set Local cell ID based on actual
conditions, and retain the default values for other parameters.
4. Run the MOD GERANNFREQGROUP command with Cell reselection priority configure indicator set to CFG(Configure) and with Local cell ID, BCCH group
ID, and Cell reselection priority set based on actual conditions.
5. Run the ADD GERANNFREQGROUPARFCN command to add neighboring GERAN BCCH frequencies.
• Reselection to CDMA2000 HRPD cells
1. Run the ADD CELLRESELCDMA2000 command to add the configurations related to reselection to CDMA2000 cells. In this step, set both HRPD parameters
configure indicator and HRPD cell reselection configure indicator to CFG(Configure).
3. Run the MOD CDMA2000BANDCLASS command with CDMA2000HRPD cell reselection indicator set to CFG(Configure). In this step, set Local cell ID, Band
class, and CDMA2000HRPD cell reselection priority based on actual conditions.
• Reselection to CDMA2000 1XRTT cells
1. Run the ADD CELLRESELCDMA2000 command to add the configurations related to reselection to CDMA2000 cells. In this step, set both 1XRTT parameters
configure indicator and 1XRTT cell reselection configure indicator to CFG(Configure).
3. Run the MOD CDMA2000BANDCLASS command with CDMA20001XRTT cell reselection indicator set to CFG(Configure). In this step, set Local cell ID, Band
class, and CDMA20001XRTT cell reselection priority based on actual conditions.
NOTE:
Speed-based cell reselection is supported only when cell reselection for UEs at normal speed has been enabled.
1. Run the MOD CELLRESEL command to configure speed-based cell reselection and intra-frequency neighboring E-UTRAN cell parameters. In this step, set both
Speed-dependent reselection parameter configure indicator and Speed state scale factor configure indicator to CFG(Configure).
2. Configure neighboring cell parameters based on the neighboring cell type.
• Configuring inter-frequency neighboring E-UTRAN cell parameters
Run the MOD EUTRANINTERNFREQ command with Speed dependent resel parameter configuring indicator set to CFG(Configure) and with
Scaling factor of treseleutran in medium mobility state and Scaling factor of treseleutran in high mobility state set based on actual conditions.
• Configuring neighboring UTRAN cell parameters
Run the MOD CELLRESELUTRAN command with Speed state scale factor configure indicator set to CFG(Configure).
• Configuring neighboring GERAN cell parameters
Run the MOD CELLRESELGERAN command with Speed state scale factor configure indicator set to CFG(Configure).
• Configuring neighboring CDMA2000 HRPD cell parameters
Run the MOD CELLRESELCDMA2000 command with HRPD parameters configure indicator, HRPD cell reselection configure indicator, and
Speed state scale factor configure indicator set to CFG(Configure).
• Configuring neighboring CDMA2000 1XRTT cell parameters
Run the MOD CELLRESELCDMA2000 command with 1XRTT parameters configure indicator, 1XRTT cell reselection configure indicator, and
1XRTT speed state scale factors configure indicator set to CFG(Configure).
ML Command Examples

MOD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=3600, CellReselPriorityCfgInd=CFG, CellReselPriority=5;

MOD CELLSIMAP:LOCALCELLID=0,SISWITCH=Sib6Switch-1;
ADD CELLRESELUTRAN: LocalCellId=0, TReselUtran=1, SpeedStateSfCfgInd=NOT_CFG;
MOD CELLRESEL: LocalCellId=0, CellReselPriority=6;
MOD UTRANNFREQ: LocalCellId=0, UtranDlArfcn=10738, CellReselPriorityCfgInd=CFG, CellReselPriority=7;
MOD RRCCONNSTATETIMER: UeInactiveTimer=20;

MOD CELLSIMAP:LOCALCELLID=0,SISWITCH=Sib7Switch-1;
ADD CELLRESELGERAN: LocalCellId=0, TReselGeran=1, SpeedStateSfCfgInd=NOT_CFG;


MOD GERANNFREQGROUP: LocalCellId=0, BcchGroupId=0, GeranVersion=EDGE, StartingArfcn=800, BandIndicator=GSM_dcs1800, Cell
ReselPriorityCfgInd=CFG, CellReselPriority=7;
ADD GERANNFREQGROUPARFCN: LocalCellId=0, BcchGroupId=0, GeranArfcn=1;
• Reselection to CDMA2000 HRPD cells

◾ If the eNodeB supports time synchronization (TASM.CLKSYNCMODE set to TIME(TIME)):
//Setting parameters related to cell reselection to CDMA2000
ADD CELLRESELCDMA2000: LocalCellId=0, SysTimeCfgInd=CFG, SearchWndSizeCfgInd=CFG, HrpdParaCfgInd=CFG, HrpdCellRe
selectParamCfgInd=CFG, Cdma1XrttParaCfgInd=NOT_CFG;
//Setting cell reselection priority
//Configuring CDMA2000 neighboring frequency bands
MOD CDMA2000BANDCLASS: LocalCellId=0, BandClass=bc4, Cdma2000HrpdCellReselInd=CFG, Cdma2000HrpdCellReselPri=3;
//Setting the UE inactivity timer to a value rather than 0
◾ If the eNodeB supports frequency synchronization (TASM.CLKSYNCMODE set to FERQ(FERQ)):
//Setting parameters related to cell reselection to CDMA2000
ADD CELLRESELCDMA2000: LocalCellId=0, SysTimeCfgInd=NOT_CFG, SearchWndSizeCfgInd=CFG, HrpdParaCfgInd=CFG, HrpdCe
llReselectParamCfgInd=CFG, Cdma1XrttParaCfgInd=NOT_CFG;
//Setting cell reselection priority
//Configuring CDMA2000 neighboring frequency bands
MOD CDMA2000BANDCLASS: LocalCellId=0, BandClass=bc4, Cdma2000HrpdCellReselInd=CFG, Cdma2000HrpdCellReselPri=3;
//Setting the UE inactivity timer to a value rather than 0
• Reselection to CDMA2000 1XRTT cells

ADD CELLRESELCDMA2000: LocalCellId=0, SysTimeCfgInd=NOT_CFG, SearchWndSizeCfgInd=NOT_CFG, HrpdParaCfgInd=NOT_CFG, Cdma1X
rttParaCfgInd=CFG, Cdma1XrttCellReselCfgInd=CFG, Cdma1XrttSpeedStateCfgInd=NOT_CFG;
MOD CDMA2000BANDCLASS: LocalCellId=0, BandClass=bc7, Cdma20001XrttCellReselInd=CFG, Cdma20001XrttCellReselPri=4;

MOD CELLRESEL: LocalCellId=0, SpeedDepReselCfgInd=CFG, SpeedStateSfCfgInd=CFG;
MOD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=3600, SpeedDependSPCfgInd=CFG, TReselEutranSfMedium=1DOT0_ENUM, TReselEutr
anSfHigh=0DOT75_ENUM;
MOD CELLRESELUTRAN: LocalCellId=0, SpeedStateSfCfgInd=CFG;
MOD CELLRESELGERAN: LocalCellId=0, SpeedStateSfCfgInd=CFG;
MOD CELLRESELCDMA2000: LocalCellId=0, HrpdParaCfgInd=CFG, HrpdCellReselectParamCfgInd=CFG, SpeedStateSfCfgInd=CFG;
MOD CELLRESELCDMA2000: LocalCellId=0, Cdma1XrttParaCfgInd=CFG, Cdma1XrttCellReselCfgInd=CFG, Cdma1XrttSpeedStateCfgInd=C
FG;
selection to an Inter-Frequency E-UTRAN Cell
1. Enable a UE in idle mode to camp on an E-UTRAN cell. Set the cell reselection priority of an E-UTRAN frequency. Trace the Uu messages of the E-UTRAN cell.
The SIB5 carries the cell reselection priority of the E-UTRAN frequency (cellReselectionPriority), as shown in the following figure.
2. Enable the UE in idle mode to move to the E-UTRAN cell edge. Use the UE to perform services, to trigger the UE to switch from idle mode to connected mode.
Observe the Uu messages of the E-UTRAN cell.
If the RRC_CONNECT_REQ message exists, cell reselection was successful.
selection to an Inter-RAT Cell
The following describes how to verify reselection to a UTRAN cell.
1. Enable a UE in idle mode to camp on an E-UTRAN cell. Set the cell reselection priority of a UTRAN frequency. Trace the Uu messages of the E-UTRAN cell. The
SIB6 carries the cell reselection priority of the UTRAN frequency (cellReselectionPriority), as shown in the following figure.

2. Enable the UE in idle mode to move to the E-UTRAN cell edge. Observe the Uu messages of the UTRAN cell. If the value of the establishmentCause IE in the
RRC_CONNECT_REQ message is interRAT-CellReselection, cell reselection was successful, as shown in the following figure.
eed-based Cell Reselection
Verify cell reselection in the following steps (reselection to an E-UTRAN inter-frequency cell is used as an example):
1. Enable a UE in idle mode to camp on an E-UTRAN cell. Configure parameters related to speed-based cell reselection to inter-frequency neighboring E-UTRAN
cells. Observe the Uu messages of the E-UTRAN cell. Speed-based cell reselection to inter-frequency neighboring E-UTRAN cells, that is, t-ReselectionEUTRA-
SF.sf-Medium and t-ReselectionEUTRA-SF.sf-High, are contained in SIB5, as shown in the following figure.
2. Enable the UE in idle mode to quickly move to the E-UTRAN cell edge. Use the UE to perform services, to trigger the UE to switch from idle mode to connected
mode. Observe the Uu messages of the E-UTRAN cell. If the RRC_CONNECT_REQ message exists, cell reselection was successful.
N/A
6.2.5 Deactivation

ML Commands
• Deactivating reselection to an inter-frequency E-UTRAN cell

Run the MOD EUTRANINTERNFREQ command with Inter frequency cell resel priority configure indicator set to NOT_CFG(Not configure).
• Deactivating reselection to a UTRAN cell

Method 1:
1. Run the MOD UTRANNFREQ command with Reselection priority configure indicator set to NOT_CFG(Not configure).
2. Run the RMV CELLRESELUTRAN command to remove the configuration for reselection to UTRAN cells.
Method 2:
Run the MOD CELLSIMAP command with Sib6Switch(Sib6Switch) under Cell System Information Switch deselected to deactivate cell reselection to UTRAN.

• Deactivating reselection to a GERAN cell

Method 1:
1. Run the MOD GERANNFREQGROUP command with Cell reselection priority configure indicator set to NOT_CFG(Not configure).
2. Run the RMV CELLRESELGERAN command to remove the configuration for reselection to GERAN cells.
Method 2:
Run the MOD CELLSIMAP command with Sib7Switch(Sib7Switch) under Cell System Information Switch deselected to deactivate cell reselection to GERAN.
• Deactivating reselection to a CDMA2000 HRPD cell
1. Run the MOD CDMA2000BANDCLASS command with CDMA2000HRPD cell reselection indicator set to NOT_CFG(Not configure).
2. If the configuration for reselection to a CDMA2000 HRPD cell is available, run the MOD CELLRESELCDMA2000 command with the HRPD parameters
configure indicator parameter set to NOT_CFG(Not configure). If the configuration for reselection to a CDMA2000 HRPD cell is unavailable, run the
RMV CELLRESELCDMA2000 command to remove the configuration for reselection to CDMA2000 HRPD cells.
• Deactivating reselection to a CDMA2000 1xRTT cell
1. Run the MOD CDMA2000BANDCLASS command with CDMA20001XRTT cell reselection indicator set to NOT_CFG(Not configure).
2. If the configuration for reselection to a CDMA2000 1xRRT cell is available, run the MOD CELLRESELCDMA2000 command with the 1XRTT
parameters configure indicator parameter set to NOT_CFG(Not configure). If the configuration for reselection to a CDMA2000 1xRRT cell is
unavailable, run the RMV CELLRESELCDMA2000 command to remove the configuration for reselection to CDMA2000 1xRTT cells.
• Deactivating speed-based cell reselection
NOTE:
If inter-frequency or inter-RAT cell reselection is deactivated, inter-frequency or inter-RAT speed-based cell reselection is deactivated at the same time, without
requiring additional operations.
Method 1: Deactivating speed-based cell reselection to all neighboring cells

Run the MOD CELLRESEL command with Speed-dependent reselection parameter configure indicator set to NOT_CFG(Not configure).
Method 2: Deactivating speed-based cell reselection to some neighboring cells
1. Deactivating speed-based cell reselection to intra-frequency neighboring E-UTRAN cells

Run the MOD CELLRESEL command with Speed state scale factor configure indicator set to NOT_CFG(Not configure).
2. Deactivating speed-based cell reselection to inter-frequency neighboring E-UTRAN cells
Run the MOD EUTRANINTERNFREQ command with Speed dependent resel parameter configuring indicator set to NOT_CFG(Not configure).
3. Deactivating speed-based cell reselection to neighboring UTRAN cells
Run the MOD CELLRESELUTRAN command with Speed state scale factor configure indicator set to NOT_CFG(Not configure).
4. Deactivating speed-based cell reselection to neighboring GERAN cells
Run the MOD CELLRESELGERAN command with Speed state scale factor configure indicator set to NOT_CFG(Not configure).
5. Deactivating speed-based cell reselection to neighboring CDMA2000 HRPD cells
Run the MOD CELLRESELCDMA2000 command with HRPD parameters configure indicator and HRPD cell reselection configure indicator set to
CFG(Configure) and with Speed state scale factor configure indicator set to NOT_CFG(Not configure).
6. Deactivating speed-based cell reselection to neighboring CDMA2000 1xRTT cells
Run the MOD CELLRESELCDMA2000 command with 1XRTT parameters configure indicator and 1XRTT cell reselection configure indicator set to
CFG(Configure) and with 1XRTT speed state scale factors configure indicator set to NOT_CFG(Not configure).
ML Command Examples
• Deactivating reselection to an inter-frequency E-UTRAN cell

MOD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=3600, CellReselPriorityCfgInd=NOT_CFG;
• Deactivating reselection to a UTRAN cell

Method 1:
MOD UTRANNFREQ: LocalCellId=0, UtranDlArfcn=10738, CellReselPriorityCfgInd=NOT_CFG;
RMV CELLRESELUTRAN: LocalCellId=0;
Method 2:
MOD CELLSIMAP: LocalCellId=0, SiSwitch=Sib6Switch-0;
• Deactivating reselection to a GERAN cell

Method 1:
MOD GERANNFREQGROUP: LocalCellId=0, BcchGroupId=0, CellReselPriorityCfgInd=NOT_CFG;
RMV CELLRESELGERAN: LocalCellId=0;
Method 2:
MOD CELLSIMAP: LocalCellId=0, SiSwitch=Sib7Switch-0;
• Deactivating reselection to a CDMA2000 HRPD cell

MOD CDMA2000BANDCLASS: LocalCellId=0, BandClass=bc4, Cdma2000HrpdCellReselInd=NOT_CFG;
MOD CELLRESELCDMA2000: LocalCellId=0, HrpdParaCfgInd=NOT_CFG;
RMV CELLRESELCDMA2000: LocalCellId=0;
• Deactivating reselection to a CDMA2000 1xRTT cell

MOD CDMA2000BANDCLASS: LocalCellId=0, BandClass=bc7, Cdma20001XrttCellReselInd=NOT_CFG;
MOD CELLRESELCDMA2000: LocalCellId=0, Cdma1XrttParaCfgInd=CFG, Cdma1XrttCellReselCfgInd=NOT_CFG;
RMV CELLRESELCDMA2000: LocalCellId=0;
• Deactivating speed-based cell reselection

Method 1: Deactivating speed-based cell reselection to all neighboring cells
MOD CELLRESEL: LocalCellId=0, SpeedDepReselCfgInd=NOT_CFG;
Method 2: Deactivating speed-based cell reselection to some neighboring cells
MOD CELLRESEL: LocalCellId=0, SpeedStateSfCfgInd=NOT_CFG;
MOD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=3600, SpeedDependSPCfgInd=NOT_CFG;
MOD CELLRESELUTRAN: LocalCellId=0, SpeedStateSfCfgInd=NOT_CFG;
MOD CELLRESELGERAN: LocalCellId=0, SpeedStateSfCfgInd=NOT_CFG;
MOD CELLRESELCDMA2000: LocalCellId=0, HrpdParaCfgInd=CFG, HrpdCellReselectParamCfgInd=CFG, SpeedStateSfCfgInd=NOT_CFG;
MOD CELLRESELCDMA2000: LocalCellId=0, Cdma1XrttParaCfgInd=CFG, Cdma1XrttCellReselCfgInd=CFG, Cdma1XrttSpeedStateCfgInd=N
OT_CFG;

LBFD-00201803 Cell Selection and Re-selection does not have the counter statistics result.
The following describes the counters used to monitor LBFD-002009 Broadcast of system information and LBFD-002011 Paging.
Counter ID Counter Name Counter Description
1526726884 L.Paging.S1.Rx Number of paging messages received over the S1 interface in a cell. This counter
reflects the signaling overhead brought by the UE in idle mode.
1526726885 L.Paging.UU.Att Estimated paging success rate. In a paging group, divide L.Paging.UU.Att for a single cell
by the sum of L.Paging.UU.Succ for all cells in the paging group to obtain the paging
success rate.
NOTE:
Generally, the EPC sends paging messages to all cells in a paging group, the value of L.Paging.UU.Att for
each cell is similar. This way, you can use this method to estimate the paging success rate.
1526726886 L.Paging.UU.Succ
If the EPC supports certain enhanced paging features, some UEs in a paging group may receive paging
message from another paging group and the values of L.Paging.UU.Att may greatly differ among the cells
in the same paging group. In this case, you cannot use this method to estimate the paging success rate.
You can obtain the precise paging success rate from the EPC.
1526727212 L.Paging.Dis.Num Number of discarded MME-delivered paging messages in a cell.
1526728521 L.Paging.Dis.PchCong Number of paging messages discarded due to PCH congestion in a cell.
1526728337 L.Paging.UU.SIUpdate Number of paging messages delivered over the Uu interface due to system information
changes in a cell.
ll Selection
The following table describes the parameters that must be set in the CellSel MO to configure cell selection.
Parameter Name Parameter ID Setting Notes
Minimum required RX level CellSel.QRxLevMin Set this parameter properly so that the selected cells can provide signals that
meet quality requirements for basic services.
Minimum required RX level offset CellSel.QRxLevMinOffset A larger value of this parameter increases the probability a cell will meet the
cell selection criterion (criterion S) and become a suitable cell for cell selection.
A smaller value of this parameter decreases the probability.
Minimum required RX quality level CellSel.QQualMin • This parameter is used to calculate the serving sell Squal for cell
selection and reselection. If RSRQ-related parameters are delivered
to control cell selection and reselection, set this parameter to a value
other than 0.
• If only RSRP-related parameters are delivered to control cell
selection and reselection, set this parameter to 0.
Minimum required RX quality level CellSel.QQualMinOffset A larger value of this parameter increases the probability a cell will meet the
offset cell selection criterion (criterion S) and become a suitable cell for cell selection.
A smaller value of this parameter decreases the probability.
The following table describes the parameter that must be set in the CELL MO to configure the maximum allowed transmit power.
Max transmit power allowed CELL.UePowerMax A larger value increases the maximum transmit power for UEs and signal
strength in the local cell but also interference to neighboring cells. A smaller
value leads to the opposite effect.
ighboring Cell Measurement
• Intra-frequency measurement
Threshold for intra frequency CellResel.SIntraSearch Set this parameter to a value greater than the value of the
measurements CellResel.SNonIntraSearch parameter. With other conditions unchanged, a
larger value of this parameter increases the probability intra-frequency cell
measurements will be triggered, and a smaller value decreases the probability.
RSRQ Threshold for intra CELLRESEL.SIntraSearchQ With other conditions unchanged, a larger value of this parameter increases
frequency measurements the probability intra-frequency cell measurements will be triggered, and a
smaller value decreases the probability.
• Inter-frequency or inter-RAT measurement

Threshold for non-intra frequency CellResel.SNonIntraSearch Set this parameter to a value less than that of SIntraSearch.
measurements
RSRQ Threshold for non-intra CellResel.SNonIntraSearchQ With other conditions unchanged, a larger value of this parameter increases
frequency measurements the probability inter-frequency or inter-RAT measurements will be triggered,
and a smaller value decreases the probability.
ll Reselection
• Intra-frequency or equal-priority cell reselection


Minimum required RX level CellResel.QRxLevMin Set this parameter to an appropriate value so that the selected cell can provide
signals that meet the quality requirement of basic services.
Cell reselection timer value for CellResel.TReselEutran A smaller parameter value for a cell increases the probability UEs in this cell
EUTRAN will initiate reselection and also the probability of ping-pong reselection. A
larger parameter value for a cell decreases the probabilities.
Hysteresis value for ranking CellResel.Qhyst This parameter is used to adjust the border of the serving cell, to avoid ping-
criteria pong effect of cell reselection. A larger value of CellResel.Qhyst increases the
coverage of the serving cell and therefore lowers the probability of reselection
to a neighboring cell.
The following table describes the parameter that must be set in the EutranIntraFreqNCell MO to configure neighbor relationships of intra-frequency E-UTRAN cells.
Cell offset EutranIntraFreqNCell.CellQoffset This parameter is used to adjust the border of neighboring cells. A larger
value of EutranIntraFreqNCell.CellQoffset reduces the coverage of the
neighboring cell and therefore lowers the probability of reselection to that
cell.
• Reselection of inter-frequency or inter-RAT cells on different-priority frequencies

Serving frequency lower priority CellResel.ThrshServLow A smaller value of this parameter reduces the probability of reselection to low-
threshold priority inter-frequency or inter-RAT cells.
Serving frequency lower priority CellResel.ThrshServLowQ With other conditions unchanged, a smaller value of this parameter reduces
RSRQ threshold the probability of reselection to an inter-frequency or inter-RAT cell on lower-
priority frequencies, and a larger value of this parameter leads to a higher
probability.
The following table describes the parameters that must be set in the EutranInterNFreq MO to configure a non-serving E-UTRA frequency.
PMAX EutranInterNFreq.PMax A smaller value of this parameter results in a lower signal

quality requirement for reselection to a cell on the non-
serving E-UTRA frequency, decreasing the access success
rate of the cell. A larger value of this parameter results in
the opposite effect.
Minimum RX signal quality EutranInterNFreq.QQualMin A larger value of this parameter reduces the probability a
cell will meet the cell selection criterion (criterion S) and
become a suitable cell for cell selection. A smaller value of
this parameter increases the probability.
Frequency offset EutranInterNFreq.QoffsetFreq A larger value of this parameter reduces the probability of
reselection to cells on the non-serving E-UTRA frequency. A
smaller value of this parameter increases the probability.
Inter frequency high priority RSRQ EutranInterNFreq.ThreshXHighQ A smaller value of this parameter increases the probability
threshold of reselection to a cell on the non-serving E-UTRA
frequency, decreasing the access success rate of the cell. A
larger value of this parameter results in the opposite effect.
Inter frequency low priority RSRQ EutranInterNFreq.ThreshXlowQ A smaller value of this parameter increases the probability
threshold of reselection to a cell on the non-serving E-UTRA
frequency, decreasing the access success rate of the cell. A
larger value of this parameter results in the opposite effect.
Inter frequency high priority threshold EutranInterNFreq.ThreshXhigh With other conditions unchanged, a larger value of this
parameter leads to a lower probability of cell reselection,
and a smaller value leads to a higher probability.
Inter frequency lower priority threshold EutranInterNFreq.ThreshXlow With other conditions unchanged, a larger value of this
parameter leads to a lower probability of cell reselection,
and a smaller value leads to a higher probability.
Minimum required RX level EutranInterNFreq.QRxLevMin Set this parameter to an appropriate value so that the
selected cell can provide signals that meet the quality
requirement of basic services.
EUTRAN reselection time EutranInterNFreq.EutranReselTime A smaller value of this parameter leads to a higher
probability of cell reselection, and a larger value of this
parameter leads to a lower probability. If the value of this
parameter is excessively large or small, the access success
rate is affected.
Measurement Performance Demand EutranInterNFreq.MeasPerformanceDemand You are advised to set this parameter to NORMAL
(NORMAL) for frequencies to meet the following
requirements:
• At least one frequency for intensive coverage is
included.
• Frequencies on the main capacity layer, such as
those with a large bandwidth, high UE
penetration rate, and good coverage, are
included as much as possible.
The following table describes the parameters that must be set in the UtranNFreq MO to configure UTRAN frequencies.

Minimum required quality level UtranNFreq.Qqualmin A larger value of this parameter leads to lower probabilities that a UTRAN
FDD cell meets the cell selection criterion (criterion S) and becomes a
suitable cell selected by a UE. A smaller value of this parameter leads to
higher probabilities.
PMAX UtranNFreq.PmaxUtran Set this parameter based on site requirements.
UTRAN high priority RSRQ UtranNFreq.ThreshXHighQ With other conditions unchanged, a larger value of this parameter leads to
threshold a lower probability of cell reselection, and a smaller value leads to a higher
probability.
UTRAN low priority RSRQ UtranNFreq.ThreshXLowQ With other conditions unchanged, a larger value of this parameter leads to
threshold a lower probability of cell reselection, and a smaller value leads to a higher
probability.
Minimum required RX level UtranNFreq.QRxLevMin Set this parameter to an appropriate value so that the selected cell can
provide signals that meet the quality requirement of basic services.
UTRAN high priority threshold UtranNFreq.ThreshXHigh With other conditions unchanged, a larger value of this parameter leads to
a lower probability of cell reselection, and a smaller value leads to a higher
probability.
UTRAN lower priority threshold UtranNFreq.ThreshXLow With other conditions unchanged, a larger value of this parameter leads to
a lower probability of cell reselection, and a smaller value leads to a higher
probability.
The following table describes the parameters that must be set in the CellReselUtran MO to configure cell reselection to UTRAN.
Cell reselection timer value for CellReselUtran.TReselUtran With other conditions unchanged, a larger value of this parameter leads to a lower
UTRAN probability of cell reselection, and a smaller value leads to a higher probability.
The following table describes the parameters that must be set in the GeranNfreqGroup MO to configure GERAN frequencies.
High priority threshold GeranNfreqGroup.ThreshXHigh With other conditions unchanged, a larger value of this parameter
leads to a lower probability of cell reselection, and a smaller value
leads to a higher probability.
Lower priority threshold GeranNfreqGroup.ThreshXLow With other conditions unchanged, a larger value of this parameter
leads to a lower probability of cell reselection, and a smaller value
leads to a higher probability.
PMAX GeranNfreqGroup.PmaxGeran -
Minimum required RX level GeranNfreqGroup.QRxLevMin Set this parameter to an appropriate value so that the selected
cell can provide signals that meet the quality requirement of basic
services.
The following table describes the parameter that must be set in the CellReselGeran MO to configure cell reselection to GERAN.
Cell reselection timer value CellReselGeran.TReselGeran With other conditions unchanged, a larger value of this parameter leads to a lower
for GERAN probability of cell reselection, and a smaller value leads to a higher probability.
The following table describes the parameters that must be set in the CellReselCdma2000 MO to configure cell reselection to CDMA2000.
Cell reselection timer for CellReselCdma2000.TreselectionHrpd With other conditions unchanged, a larger value of this parameter leads
HRPD to a lower probability of cell reselection, and a smaller value leads to a
higher probability.
Cell reselection timer for CellReselCdma2000.Cdma1XrttTreselection A smaller parameter value for a cell increases the probability UEs in this
1XRTT cell will initiate reselection and also the probability of ping-pong
reselection. A larger parameter value for a cell decreases the
probabilities.
The following table describes the parameters that must be set in the Cdma2000BandClass MO to configure CDMA2000 frequency bands.
CDMA20001XRTT high priority Cdma2000BandClass.Cdma20001XrttThreshXHigh A larger value of this parameter indicates a lower probability of a
threshold UE camping on the cells assigned with the band class, and a
smaller value indicates a higher probability.
CDMA20001XRTT lower priority Cdma2000BandClass.Cdma20001XrttThreshXLow A larger value of this parameter indicates a lower probability of a
CDMA2000HRPD high priority Cdma2000BandClass.Cdma2000HrpdThreshXHigh A larger value of this parameter indicates a lower probability of a
CDMA2000HRPD lower priority Cdma2000BandClass.Cdma2000HrpdThreshXLow A larger value of this parameter indicates a lower probability of a

The following table describes the parameters that must be set in the CellResel MO to configure common speed-based cell reselection parameters and speed-based
cell reselection parameters related to intra-frequency neighboring E-UTRAN cells.

The duration for evaluating CellResel.TEvaluation A smaller value of this parameter leads to a lower probability of the UE entering
criteria to enter mobility states the high mobility or medium mobility state. A larger value of this parameter
leads to the opposite effect.
Additional time hysteresis for CellResel.THystNormal A larger value of this parameter leads to a slower decision on speed change
normal speed and a smaller impact of UE speed variation on cell reselection. A smaller value
of this parameter leads to the opposite effect.
The number of cell changes to CellResel.NCellChangeMedium A larger value of this parameter indicates a lower probability of a UE entering
enter medium mobility state the medium mobility state and cell reselections are more difficult to trigger. A
smaller value of this parameter leads to the opposite effect.
The number of cell changes to CellResel.NCellChangeHigh A larger value of this parameter indicates a lower probability of a UE entering
enter high mobility state the high mobility state and cell reselections are more difficult to trigger. A
smaller value of this parameter leads to the opposite effect.
Additional hysteresis for medium CellResel.QHystSfMedium A smaller value of this parameter results in a higher speed of cell reselection for
speed medium-mobility UEs. A larger value of this parameter leads to the opposite
effect.
Additional hysteresis for high CellResel.QHystSfHigh A smaller value of this parameter results in a higher speed of cell reselection for
speed high-mobility UEs. A larger value of this parameter leads to the opposite effect.
Scaling factor of TReselEutran in CellResel.TReselEutranSfMedium A smaller value of this parameter results in a higher speed of cell reselection for
medium mobility state medium-mobility UEs. A larger value of this parameter leads to the opposite
effect.
Scaling factor of TReselEutran in CellResel.TReselEutranSfHigh A smaller value of this parameter results in a higher speed of cell reselection for
high mobility state high-mobility UEs. A larger value of this parameter leads to the opposite effect.
The following table describes the parameters that must be set in the EutranInterNFreq MO to configure speed-based cell reselection parameters related to inter-
frequency neighboring E-UTRAN cells.
Scaling factor of treseleutran EutranInterNFreq.TReselEutranSfMedium A smaller value of this parameter results in a higher speed of cell
in medium mobility state reselection for medium-mobility UEs. A larger value of this parameter leads
to the opposite effect.
Scaling factor of treseleutran EutranInterNFreq.TReselEutranSfHigh A smaller value of this parameter results in a higher speed of cell
in high mobility state reselection for high-mobility UEs. A larger value of this parameter leads to
the opposite effect.
The following table describes the parameters that must be set in the CellReselUtran MO to configure speed-based cell reselection to neighboring UTRAN cells.
Scaling factor of TReselUtran in CellReselUtran.TReselUtranSfMedium A smaller value of this parameter results in a higher speed of cell reselection
medium mobility state for medium-mobility UEs. A larger value of this parameter leads to the
opposite effect.
Scaling factor of TReselUtran in CellReselUtran.TReselUtranSfHigh A smaller value of this parameter results in a higher speed of cell reselection
high mobility state for high-mobility UEs. A larger value of this parameter leads to the opposite
effect.
The following table describes the parameters that must be set in the CellReselGeran MO to configure speed-based cell reselection to neighboring GERAN cells.
Scaling factor of TReselGeran CellReselGeran.TReselGeranSfMedium A smaller value of this parameter results in a higher speed of cell reselection
in medium mobility state for medium-mobility UEs. A larger value of this parameter leads to the
opposite effect.
Scaling factor of TReselGeran CellReselGeran.TReselGeranSfHigh A smaller value of this parameter results in a higher speed of cell reselection
in high mobility state for high-mobility UEs. A larger value of this parameter leads to the opposite
effect.
The following table describes the parameters that must be set in the CellReselCdma2000 MO to configure speed-based cell reselection to neighboring CDMA2000
cells.
Scaling factor of CellReselCdma2000.TReselCdmaHrpdSfMedium A smaller value of this parameter results in a higher speed of cell
TReselCdmaHrpd in reselection for medium-mobility UEs. A larger value of this parameter
medium mobility state leads to the opposite effect.
Scaling factor of CellReselCdma2000.TReselCdmaHrpdSfHigh A smaller value of this parameter results in a higher speed of cell
TReselCdmaHrpd in high reselection for high-mobility UEs. A larger value of this parameter leads
mobility state to the opposite effect.
1XRTT medium speed CellReselCdma2000.Cdma1XrttSfMedium A smaller value of this parameter results in a higher speed of cell
scale factor reselection for medium-mobility UEs. A larger value of this parameter
1XRTT high speed scale CellReselCdma2000.Cdma1XrttSfHigh A smaller value of this parameter results in a higher speed of cell
factor reselection for high-mobility UEs. A larger value of this parameter leads
to the opposite effect.
ging
• Paging success rate

Decreasing the paging message code rate specified by CellDlschAlgo.RarAndPagingCR helps improve the paging success rate.
However, decreasing the paging message code rate increases the PDSCH resources occupied by paging messages, which causes the downlink throughput to
decrease.

With UE compatibility problems taken into account, set the paging message code rate to 0.035 or higher (setting CellDlschAlgo.RarAndPagingCR to 35). The
number of single-paging message RBs less than or equal to 40% of the total number of single-TTI RBs prevents insufficient downlink power. Therefore, when
adjusting the CellDlschAlgo.RarAndPagingCR setting, you are advised to limit the number of paging records contained in a single paging message (specified by
PCCHCfg.MaxPagingRecordsNum) to limit the maximum number of single-paging message RBs.
The following table lists the recommended values for PCCHCfg.MaxPagingRecordsNum in case of different CellDlschAlgo.RarAndPagingCR values (20 MHz
bandwidth used as an example).
Number of Single-Paging Message RBs CellDlschAlgo.RarAndPagingCR PCCHCfg.MaxPagingRecordsNum
≤ 40 ≥ 78 16
≤ 40 ≥ 73 15
≤ 40 ≥ 69 14
≤ 40 ≥ 64 13
≤ 40 ≥ 60 12
≤ 40 ≥ 55 11
≤ 40 ≥ 50 10
≤ 40 ≥ 45 9
≤ 40 ≥ 41 8
≤ 40 ≥ 36 7
≤ 37 ≥ 35 6
NOTE:
In this table, the recommended number of RBs is calculated based on the paging messages containing UE flags "S-TMSI".
• Uu interface paging capacity

The Uu interface paging capacity is related to nB (specified by PCCHCfg.Nb) and the number of paging message records (specified by
PCCHCfg.MaxPagingRecordsNum). The maximum number of paging message sent over the Uu interface within 1s is equal to the result of (nB/T) multiplied by 100
and PCCHCfg.MaxPagingRecordsNum, where T represents the paging cycle.
NOTE:
The above formula calculates the theoretical maximum paging capacity, but the actual paging capacity is also affected by hardware processing capabilities.
Assume nB equals 1T, and the value of PCCHCfg.MaxPagingRecordsNum is 16, a maximum of 1600 UEs can be paged over the Uu interface within 1s. You can
increase nB and PCCHCfg.MaxPagingRecordsNum to increase the Uu interface paging capacity. However, increasing nB increases the overhead of PDCCHs
occupied by paging messages.
When adjusting the PCCHCfg.MaxPagingRecordsNum setting, query the paging message code rate specified by CellDlschAlgo.RarAndPagingCR, and ensure that
the number of single-paging message RBs does not exceed 40% of the total number of single-TTI RBs, in accordance with the description in the preceding table.
• Paging priority
If paging messages are congested over the Uu interface, you are advised to set PCCHCfg.PagingStrategy to PAGING_STRATEGY_DIFFPRI(Priority
Differentiation Strategy), to ensure that CS paging messages or high-priority paging messages are preferentially sent over the Uu interface.
stem Information Update
If the paging occasion (PO) of a UE supporting Single Radio LTE (SRLTE) falls in the paging monitoring window of a CDMA2000 1X network, the UE will not be able to receive
paging messages from the LTE network, and will not be able to update LTE system information. As a result, RRC establishment may fail.
You are advised to set CellSiMap.SibUpdOptSwitch to SibPagingOptCtrlSwitch in areas with both CDMA and LTE network coverage. The reasons are as follows:
• If this switch is turned on, when the paging cycle of the LTE network is less than that of the CDMA network, RRC establishment failures can be avoided; when the
paging cycle of the LTE network is greater than or equal to that of the CDMA network, the problem persists.
• If this switch is turned off, the problem persists regardless of the paging periods of LTE and CDMA networks.
Possible Issues
None
7 Parameters
CellSiMap SiSwitch MOD CELLSIMAP LBFD-002009 / Broadcast of Meaning:

LST CELLSIMAP TDLBFD-002009 system Indicates the system information
LOFD-070220 information broadcast policy for the cell.
eMBMS Phase OnlyCellSiSwitch(DlOnlyCellSiSwitch):
1 based on Indicates whether to broadcast system
Centralized information in the cell, whose
MCE Cell.WorkMode is set to DL_ONLY.
Architecture System information is broadcast in the cell
only if this option is selected. This option
applies only to LTE FDD cells whose
Cell.WorkMode is set to DL_ONLY.
Sib6Switch(Sib6Switch): Indicates
whether to broadcast SIB6. If this option is
deselected, SIB6 is not broadcast. If this
option is selected and the
CELLRESELUTRAN MO is created, SIB6
is broadcast. For details about the
contents of SIB6, see 3GPP TS 36.331.


Sib7Switch(Sib7Switch): Indicates
whether to broadcast SIB7. If this option is
deselected, SIB7 is not broadcast. If this
CELLRESELGERAN MO is created, SIB7
is broadcast. For details about the
contents of SIB7, see 3GPP TS 36.331.
GUI Value Range: DlOnlyCellSiSwitch
(DlOnlyCellSiSwitch), Sib6Switch
(Sib6Switch), Sib7Switch(Sib7Switch)
Unit: None
Actual Value Range: DlOnlyCellSiSwitch,
Sib6Switch, Sib7Switch
Default Value: DlOnlyCellSiSwitch:Off,
Sib6Switch:On, Sib7Switch:On
CellSel QQualMin MOD CELLSEL LBFD-002009 / Broadcast of Meaning: Indicates the minimum required
LST CELLSEL TDLBFD-002009 system received signal quality, which corresponds
LBFD-00201803 / information to the q-QualMin IE in the system
TDLBFD-00201803 Cell Selection message system information block type 1
and Re- (SIB1) and is used to calculate the Squal
selection value for the serving cell involved in cell
selection and reselection. If this
parameter is set to 0, the SIB1 message
does not contain the q-QualMin IE. If this
parameter is set to a value other than 0,
the SIB1 message contains the q-QualMin
IE with the same value as the parameter
value. For details about this parameter,
see 3GPP TS 36.304.
GUI Value Range: -34~-3,0
Unit: dB
Actual Value Range: -34~-3,0
Default Value: 0
EutranInterNFreq MeasPerformanceDemand ADD EUTRANINTERNFREQ LBFD-002009 / Broadcast of Meaning: Indicates the measurement
MOD TDLBFD-002009 system performance demand for whether to
EUTRANINTERNFREQ information broadcast frequencies in SIB5. If this
LBFD-
LST EUTRANINTERNFREQ parameter is set to NORMAL, a frequency
00201803/TDLBFD- Cell Selection
00201803 and Re- is broadcast in interFreqCarrierFreqList
selection without carrying the IE
reducedMeasPerformance. The
measurement performance of a UE is
normal when the UE measures the
frequency. If this parameter is set to
REDUCED, a frequency is broadcast in
interFreqCarrierFreqListExt carrying the
IE reducedMeasPerformance. The
measurement performance of a UE
supporting extensive frequency
measurement can be reduced to measure
the frequency. For details of the IE
reducedMeasPerformance, see 3GPP TS
36.331.
GUI Value Range: NORMAL(NORMAL),
REDUCED(REDUCED)
Unit: None
Actual Value Range: NORMAL,
REDUCED
Default Value: NORMAL(NORMAL)
CellSel QRxLevMin MOD CELLSEL LBFD-00201803 / Cell Selection Meaning: Indicates the minimum required
LST CELLSEL TDLBFD-00201803 and Re- RX level for the cell to become a
LBFD-002009 / selection candidate for cell selection. This value is
TDLBFD-002009 Broadcast of included in criteria S and used in the
system evaluation of cell selection. For details,
GUI Value Range: -70~-22
Unit: 2dBm
Actual Value Range: -140~-44
Default Value: -64
CellSel QRxLevMinOffset MOD CELLSEL LBFD-00201803 / Cell Selection Meaning: Indicates the offset to the
LST CELLSEL TDLBFD-00201803 and Re- minimum required RX level. This value is
LBFD-002009 / selection included in criteria S and used in the
TDLBFD-002009 Broadcast of evaluation of cell selection. This
system parameter is valid only when the cell
information selection is triggered by periodic searches
for higher-priority PLMNs and the UE is
served by a Visited Public Land Mobile
Network (VPLMN). For details, see 3GPP
TS 36.304.
Unit: 2dB
Default Value: 0
Cell UePowerMax ADD CELL LBFD-002026 / Uplink Power Meaning: Indicates the maximum transmit
MOD CELL TDLBFD-002026 Control power that a UE can apply to uplink
LST CELL LBFD-002009 / transmission in the cell. It is used in cell
TDLBFD-002009 selection criterion S to calculate the
compensated power. If the value of this


Broadcast of parameter is not specified, the maximum
system power is subject to the UE capability. For
GUI Value Range: -30~36
Unit: dBm
Default Value: 23
CellResel ThrshServLowQCfgInd MOD CELLRESEL LBFD-002009 / Broadcast of Meaning: Indicates whether to set the
LST CELLRESEL TDLBFD-002009 system RSRQ threshold for reselection to cells on
LBFD-00201803 / information the serving frequency.
TDLBFD-00201803 Cell Selection GUI Value Range: NOT_CFG(Not
and Re- configure), CFG(Configure)
selection Unit: None
CellSel QQualMinOffset MOD CELLSEL LBFD-002009 / Broadcast of Meaning: Indicates the offset to the
LST CELLSEL TDLBFD-002009 system minimum required RX level for the cell. It
LBFD-00201803 / information is included in criteria S and used in the
TDLBFD-00201803 Cell Selection evaluation of cell selection. This
and Re- parameter is required only when the cell
selection selection is triggered by periodic searches
for higher-priority PLMNs and the UE is
served by a Visited Public Land Mobile
Network (VPLMN). For details, see 3GPP
TS 36.304.
Unit: dB
Default Value: 1
CellResel CellReselPriority MOD CELLRESEL LBFD-00201803 / Cell Selection Meaning: Indicates the cell reselection
LST CELLRESEL TDLBFD-00201803 and Re- priority of the serving frequency. 0
LBFD-002009 / selection indicates the lowest priority. The value of
TDLBFD-002009 Broadcast of this parameter must be determined
system together with the priorities of other
information frequencies during the network planning.
Frequencies used for different RATs must
be assigned different cell reselection
priorities.
Unit: None
Default Value: 7
EutranInterNFreq CellReselPriority ADD EUTRANINTERNFREQ LBFD-00201803 / Cell Selection Meaning: Indicates the cell reselection
MOD TDLBFD-00201803 and priority of the neighboring E-UTRAN
EUTRANINTERNFREQ Reselection frequency. The value 0 indicates the
LST EUTRANINTERNFREQ lowest priority. It is contained in system
information block type 5 (SIB5). The UE
decides whether to reselect a neighboring
cell on the frequency based on the value
of this parameter and the absolute priority
of the serving cell. If the value of this
parameter is larger than the absolute
priority of the serving cell, the UE starts
measurements on neighboring cells on
the frequency; then if the signal quality of
some neighboring cells meets the related
conditions, the UE starts cell reselection.
If the value of this parameter is less than
or equal to the absolute priority of the
serving cell, the UE starts the
measurements only when the signal
quality of the serving cell is poor; then if
the signal quality of some neighboring
cells meets the related conditions, the UE
starts cell reselection. Frequencies used
for different RATs must be assigned
different cell reselection priorities. For
details, see 3GPP TS 36.331.
Unit: None
Default Value: 1
UtranNFreq CellReselPriority ADD UTRANNFREQ LBFD-00201803 / Cell Selection Meaning:

MOD UTRANNFREQ TDLBFD-00201803 and Re- Indicates the cell reselection priority of the
LST UTRANNFREQ LBFD-002009 / selection neighboring UTRAN frequency. The value
TDLBFD-002009 Broadcast of 0 indicates the lowest priority. The UE
TDLOFD-001018 system decides whether to reselect a neighboring
information cell on the UTRAN frequency based on
S1-flex the value of this parameter and the
absolute priority of the serving cell.
If the value of this parameter is larger than
the absolute priority of the serving cell, the
UE starts measurements on neighboring
cells on the UTRAN frequency; then if the
signal quality of some neighboring cells


meets the related conditions, the UE
starts cell reselection.
If the value of this parameter is smaller
than the absolute priority of the serving
cell, the UE starts the measurements only
when the signal quality of the serving cell
is poor; then if the signal quality of some
neighboring cells meets the related
conditions, the UE starts cell reselection.
Frequencies used for different RATs must
be assigned different cell reselection
priorities. For details, see 3GPP TS
36.331.
Unit: None
Default Value: 1
GeranNfreqGroup CellReselPriority ADD GERANNFREQGROUP LBFD-00201803 / Cell Selection Meaning: Indicates the cell reselection
MOD TDLBFD-00201803 and priority of the GERAN carrier frequency
GERANNFREQGROUP Reselection group. The value 0 indicates the lowest
LST GERANNFREQGROUP priority. It is contained in system
information block type 7 (SIB7). The UE
decides whether to reselect a neighboring
cell on a frequency in the GERAN carrier
frequency group based on the value of
this parameter and the absolute priority of
the serving cell. If the value of this
parameter is larger than the absolute
priority of the serving cell, the UE starts
measurements on neighboring cells on
the frequencies in the GERAN carrier
frequency group; then if the signal quality
of some neighboring cells meets the
related conditions, the UE starts cell
reselection. If the value of this parameter
is smaller than the absolute priority of the
serving cell, the UE starts the
measurements only when the signal
quality of the serving cell is poor; then if
the signal quality of some neighboring
cells meets the related conditions, the UE
starts cell reselection. Frequencies used
for different RATs must be assigned
different cell reselection priorities. For
Unit: None
Default Value: 1
Cdma2000BandClass Cdma20001XrttCellReselPri ADD LBFD-00201803 / Cell Selection Meaning: Indicates the absolute priority of
CDMA2000BANDCLASS TDLBFD-00201803 and Re- the CDMA2000 1xRTT band class to be
MOD selection used during cell reselection. The value 0
CDMA2000BANDCLASS LOFD-001035 /
TDLOFD-001035 CS Fallback to indicates the lowest priority. Frequencies
LST
CDMA2000BANDCLASS TDLOFD-001090 CDMA2000 used for different RATs must be assigned
1xRTT different cell reselection priorities. The
Enhanced CS information is contained in SIB8. For
Fallback to details, see 3GPP TS 36.331.
CDMA2000 GUI Value Range: 0~7
1xRTT Unit: None
Default Value: 2
Cdma2000BandClass Cdma2000HrpdCellReselPri ADD LBFD-00201803 / Cell Selection Meaning: Indicates the absolute priority of
CDMA2000BANDCLASS TDLBFD-00201803 and Re- the CDMA2000 HRPD band class to be
MOD selection used during cell reselection. The value 0
TDLOFD-001021 PS Inter-RAT indicates the lowest priority. Frequencies
LST
CDMA2000BANDCLASS Mobility used for different RATs must be assigned
between different cell reselection priorities. The
E-UTRAN and information is contained in SIB8. For
CDMA2000 details, see 3GPP TS 36.331.
Unit: None
Default Value: 2
EutranNFreqRanShare CellReselPriority ADD LOFD-001036 RAN Sharing Meaning: Indicates the cell reselection
EUTRANNFREQRANSHARE with Common priority of the operator that shares the
TDLBFD-00201803
MOD Carrier neighboring E-UTRAN frequency. The
EUTRANNFREQRANSHARE TDLOFD-001112
Cell Selection value 0 indicates the lowest priority. If the
LST LOFD-070206
EUTRANNFREQRANSHARE and Re- related SPID configuration is specified,
selection the cell reselection priority specified in the
MOCN Flexible SPID configuration is used. If no related
Priority Based SPID configuration is specified but this
Camping parameter is set, the eNodeB delivers the
cell reselection priorities of all PLMNs
Hybrid RAN
supported by a UE by using the IE
Sharing
idleModeMobilityControlInfo in an RRC
Connection Release message to the UE.
If no related SPID configuration is
specified and this parameter is not set, a


UE uses the cell reselection priority of the
neighboring E-UTRAN frequency, which is
broadcast in the system information.
Unit: None
Default Value: 0
UtranRanShare CellReselPriority ADD UTRANRANSHARE LOFD-001036 / RAN Sharing Meaning: Indicates the cell reselection
MOD UTRANRANSHARE TDLOFD-001036 with Common priority of the operator that shares the
LST UTRANRANSHARE LBFD-00201803 / Carrier neighboring UTRAN frequency. The value
TDLBFD-00201803 Cell Selection 0 indicates the lowest priority. If the
TDLOFD-001112 and Re- related SPID configuration is specified,
selection set this priority to the one specified in the
LOFD-070206
MOCN Flexible SPID configuration. If no related SPID
Priority Based configuration is specified but this
Camping parameter is set, the eNodeB delivers the
Hybrid RAN
Sharing
neighboring UTRAN frequency, which is
Unit: None
Default Value: 0
GeranRanShare CellReselPriority ADD GERANRANSHARE LOFD-001036 / RAN Sharing Meaning: Indicates the cell reselection
MOD GERANRANSHARE TDLOFD-001036 with Common priority of the operator that shares the
LST GERANRANSHARE LBFD-00201803 / Carrier neighboring GERAN carrier frequency
TDLBFD-00201803 Cell Selection group. The value 0 indicates the lowest
TDLOFD-001112 and Re- priority. If the related SPID configuration is
selection specified, set this priority to the one
LOFD-070206
MOCN Flexible specified in the SPID configuration. If no
Priority Based related SPID configuration is specified but
Camping this parameter is set, the eNodeB delivers
the cell reselection priorities of all PLMNs
Hybrid RAN
Sharing
neighboring GERAN carrier frequency
group, which is broadcast in the system
information.
Unit: None
Default Value: 0
EutranNFreqSCellOp CellReselDediPri ADD LOFD-001112 / MOCN Flexible Meaning: Indicates the cell reselection
EUTRANNFREQSCELLOP TDLOFD-001112 Priority Based dedicated priority for an E-UTRAN
MOD Camping frequency based on the PLMN ID of the
EUTRANNFREQSCELLOP LBFD-00201803 /
TDLBFD-00201803 Cell Selection local cell. The value 0 indicates the lowest
LST
EUTRANNFREQSCELLOP and Re- priority. If the related SPID configuration is
selection specified, the cell reselection priority
specified in the SPID configuration is
used. If no related SPID configuration is
specified but this parameter is set, the
eNodeB delivers the cell reselection
priorities of all PLMNs supported by a UE
by using the IE
neighboring E-UTRAN frequency, which is
Unit: None
Default Value: 0
UtranNFreqSCellOp CellReselDediPri ADD LOFD-001112 / MOCN Flexible Meaning: Indicates the dedicated cell
UTRANNFREQSCELLOP TDLOFD-001112 Priority Based reselection priority for a UTRAN
MOD Camping frequency based on the PLMN ID of the
UTRANNFREQSCELLOP LBFD-00201803 /
TDLBFD-00201803 Cell Selection local cell. The value 0 indicates the lowest
LST
UTRANNFREQSCELLOP and Re- priority. If the related SPID configuration is
specified in the SPID configuration. If no
related SPID configuration is specified but
this parameter is set, the eNodeB delivers


neighboring UTRAN frequency, which is
Unit: None
Default Value: 0
GeranNFGroupSCellOp CellReselDediPri ADD LOFD-001112 / MOCN Flexible Meaning: Indicates the cell reselection
GERANNFGROUPSCELLOP TDLOFD-001112 Priority Based dedicated priority for a GERAN frequency
MOD Camping based on the PLMN ID of the local cell.
GERANNFGROUPSCELLOP LBFD-00201803 /
TDLBFD-00201803 Cell Selection The value 0 indicates the lowest priority. If
LST
GERANNFGROUPSCELLOP and Re- the related SPID configuration is
specified in the SPID configuration. If no
related SPID configuration is specified but
this parameter is set, the eNodeB delivers
neighboring GERAN carrier frequency
group, which is broadcast in the system
information.
Unit: None
Default Value: 0
Cdma2000BcSCellOp Cdma1XrttCellReselDediPri ADD LOFD-001035 / CS Fallback to Meaning: Indicates the dedicated cell
CDMA2000BCSCELLOP TDLOFD-001035 CDMA2000 reselection priority for a CDMA2000
MOD 1xRTT 1xRTT band class based on the PLMN ID
CDMA2000BCSCELLOP TDLOFD-001018
TDLOFD-001112 S1-flex of the local cell. The value 0 indicates the
LST
CDMA2000BCSCELLOP MOCN Flexible lowest priority. If the related SPID
Priority Based configuration is specified, set this priority
Camping to the one specified in the SPID
configuration. If no related SPID
configuration is specified but this
parameter is set, the eNodeB delivers the
CDMA2000 band class, which is
Unit: None
Default Value: 0
Cdma2000BcSCellOp HrpdCellReselDediPri ADD LOFD-001021 / PS Inter-RAT Meaning: Indicates the dedicated cell
CDMA2000BCSCELLOP TDLOFD-001021 Mobility reselection priority for a CDMA2000
MOD between HRPD band class based on the PLMN ID
CDMA2000BCSCELLOP TDLOFD-001112
E-UTRAN and of the local cell. The value 0 indicates the
LST
CDMA2000BCSCELLOP CDMA2000 lowest priority. If the related SPID
MOCN Flexible configuration is specified, set this priority
Priority Based to the one specified in the SPID
Camping configuration. If no related SPID
configuration is specified but this
parameter is set, the eNodeB delivers the
CDMA2000 band class, which is
Unit: None
Default Value: 0
CellAlgoSwitch ReselecPriAdaptSwitch MOD CELLALGOSWITCH LBFD-00201803 / Cell Selection Meaning: Indicates whether to enable or
LST CELLALGOSWITCH TDLBFD-00201803 and Re- disable adaptive dedicated cell reselection
selection priority. If this switch is turned on, the
eNodeB delivers the dedicated cell
reselection priority to a UE when the
following conditions are met: (1) The UE
requests to set up an RRC connection
with the cause value being mo-Signalling.
(2) The MME instructs the eNodeB to
release the S1 bearer. (3) The eNodeB


fails to obtain the UE capability. If this
switch is turned off, the eNodeB does not
deliver dedicated cell reselection priority
to a UE even if the eNodeB fails to obtain
the UE capability information.
Unit: None
RrcConnStateTimer T320ForLoadBalance MOD None None Meaning:

RRCCONNSTATETIMER
Indicates the length of timer T320 for load
LST
RRCCONNSTATETIMER balancing. T320 specifies the time period
during which the dedicated priorities (used
for cell reselection) retain valid. The time
period is contained in the
RRCConnectionRelease message that is
received by the UE. After T320 expires,
the dedicated priorities become invalid.
This timer is started when the UE receives
an RRCConnectionRelease message
containing the t320 IE.
This timer is stopped when the UE enters
the RRC_CONNECTED mode.
GUI Value Range: min5(5), min10(10),
min20(20), min30(30), min60(60), min120
(120), min180(180)
Unit: min
Actual Value Range: min5, min10, min20,
min30, min60, min120, min180
Default Value: min10(10)
RrcConnStateTimer T320ForOther MOD None None Meaning:

RRCCONNSTATETIMER
Indicates the length of timer T320 to be
LST
RRCCONNSTATETIMER contained in RRCConnectionRelease
messages sent for reasons other than
load balancing. T320 specifies the time
period during which the dedicated
priorities (used for cell reselection) are
valid. After T320 expires, the dedicated
priorities become invalid. This parameter
is invalid for UEs to be redirected based
on the subscriber profile ID (SPID).
This timer is started when the UE receives
an RRCConnectionRelease message
containing the t320 IE. It is stopped when
the UE enters the RRC_CONNECTED
mode.
GUI Value Range: min5(5), min10(10),
min20(20), min30(30), min60(60), min120
(120), min180(180)
Unit: min
Actual Value Range: min5, min10, min20,
min30, min60, min120, min180
Default Value: min120(120)
IntraFreqBlkCell PhyCellId ADD INTRAFREQBLKCELL LBFD-002009 / Broadcast of Meaning: Indicates the starting physical
LST INTRAFREQBLKCELL TDLBFD-002009 system cell ID of the intra-frequency blacklisted
MOD INTRAFREQBLKCELL LBFD-00201801 / information cell. For details, see 3GPP TS 36.331.
RMV INTRAFREQBLKCELL TDLBFD-00201801 Coverage GUI Value Range: 0~503
Based Intra- Unit: None
frequency Actual Value Range: 0~503
Handover
Default Value: None
IntraFreqBlkCell PhyCellIdRange ADD INTRAFREQBLKCELL LBFD-002009 / Broadcast of Meaning: Indicates the physical cell ID
MOD INTRAFREQBLKCELL TDLBFD-002009 system range of the intra-frequency blacklisted
LST INTRAFREQBLKCELL LBFD-00201801 / information cell. For details, see 3GPP TS 36.331.
TDLBFD-00201801 Coverage GUI Value Range: n1(n1), n4(n4), n8(n8),
Based Intra- n12(n12), n16(n16), n24(n24), n32(n32),
frequency n48(n48), n64(n64), n84(n84), n96(n96),
Handover n128(n128), n168(n168), n252(n252),
n504(n504)
Unit: None
Actual Value Range: n1, n4, n8, n12, n16,
n24, n32, n48, n64, n84, n96, n128, n168,
n252, n504
Default Value: n1(n1)
InterFreqBlkCell DlEarfcn ADD INTERFREQBLKCELL LBFD-00201803 / Cell Selection Meaning: Indicates the DL EARFCN of
LST INTERFREQBLKCELL TDLBFD-00201803 and the inter-frequency blacklisted cell. For
MOD INTERFREQBLKCELL LBFD-00201802 / Reselection details, see 3GPP TS 36.104.
RMV INTERFREQBLKCELL TDLBFD-00201802 Coverage GUI Value Range:
Based Inter- 0~46589,54436~65535,66436~67335
frequency Unit: None
Handover Actual Value Range:
0~46589,54436~65535,66436~67335
Default Value: None
InterFreqBlkCell PhyCellId ADD INTERFREQBLKCELL LBFD-00201802 / Coverage

LST INTERFREQBLKCELL TDLBFD-00201802 Based Inter-


MOD INTERFREQBLKCELL LBFD-00201804 / frequency Meaning: Indicates the starting physical
RMV INTERFREQBLKCELL TDLBFD-00201804 Handover cell ID of the inter-frequency blacklisted
LBFD-00201805 / Distance Based cell. For details, see 3GPP TS 36.331.
TDLBFD-00201805 Inter-frequency GUI Value Range: 0~503
Handover Unit: None
Service Based Actual Value Range: 0~503
Inter-frequency Default Value: None
Handover
InterFreqBlkCell PhyCellIdRange ADD INTERFREQBLKCELL LBFD-00201802 / Coverage Meaning: Indicates the physical cell ID
MOD INTERFREQBLKCELL TDLBFD-00201802 Based Inter- range of the inter-frequency blacklisted
LST INTERFREQBLKCELL LBFD-00201804 / frequency cell. For details, see 3GPP TS 36.331.
TDLBFD-00201804 Handover GUI Value Range: n1(n1), n4(n4), n8(n8),
LBFD-00201805 / Distance Based n12(n12), n16(n16), n24(n24), n32(n32),
TDLBFD-00201805 Inter-frequency n48(n48), n64(n64), n84(n84), n96(n96),
Handover n128(n128), n168(n168), n252(n252),
Service Based n504(n504)
Inter-frequency Unit: None
Handover Actual Value Range: n1, n4, n8, n12, n16,
n24, n32, n48, n64, n84, n96, n128, n168,
n252, n504
Default Value: n1(n1)
CellResel SIntraSearchCfgInd MOD CELLRESEL LBFD-00201803 / Cell Selection Meaning: Indicates whether to set the
LST CELLRESEL TDLBFD-00201803 and Re- measurement triggering threshold for
LBFD-002009 / selection reselection to intra-frequency cells.
TDLBFD-002009 Broadcast of GUI Value Range: NOT_CFG(Not
system configure), CFG(Configure)
information Unit: None
Default Value: CFG(Configure)
CellResel QQualMinCfgInd MOD CELLRESEL LBFD-002009 / Broadcast of Meaning: Indicates whether to set cell
LST CELLRESEL TDLBFD-002009 system reselection parameters in compliance with
LBFD-00201803 / information 3GPP Release 9 in SIB3.
TDLBFD-00201803 Cell Selection GUI Value Range: NOT_CFG(Not
and Re- configure), CFG(Configure)
selection Unit: None
CellResel SIntraSearch MOD CELLRESEL LBFD-00201803 / Cell Selection Meaning:

LST CELLRESEL TDLBFD-00201803 and Re- Indicates the measurement triggering
LBFD-002009 / selection threshold for reselection to intra-frequency
TDLBFD-002009 Broadcast of cells.
system The UEs start intra-frequency
information measurements only if the value of Cell
selection RX level value (dB) is lower than
or equal to the value of this parameter.
Unit: 2dB
Default Value: 29
CellResel SIntraSearchQ MOD CELLRESEL LBFD-002009 / Broadcast of Meaning: Indicates the RSRQ threshold
LST CELLRESEL TDLBFD-002009 system for starting intra-frequency
LBFD-00201803 / information measurements. It determines the
TDLBFD-00201803 Cell Selection probability of triggering cell reselection to
and Re- an intra-frequency neighboring cell. For
selection details, see 3GPP TS 36.304.
Unit: dB
Default Value: 5
CellResel SNonIntraSearchCfgInd MOD CELLRESEL LBFD-00201803 / Cell Selection Meaning: Indicates whether to configure
LST CELLRESEL TDLBFD-00201803 and Re- the measurement triggering threshold for
LBFD-002009 / selection cell reselection to inter-frequency or inter-
TDLBFD-002009 Broadcast of RAT cells. If this parameter is set to
system NOT_CFG and the QQualMinCfgInd
information parameter is set to NOT_CFG, the UE
continuously measures intra-frequency
and inter-RAT cells, regardless of the
signal quality of the serving cell.
GUI Value Range: NOT_CFG(Not
configure), CFG(Configure)
Unit: None
CellResel SNonIntraSearch MOD CELLRESEL LBFD-00201803 / Cell Selection Meaning: Indicates the measurement
LST CELLRESEL TDLBFD-00201803 and Re- triggering threshold for reselection to
LBFD-002009 / selection inter-frequency or inter-RAT cells. If the
TDLBFD-002009 Broadcast of cell reselection priority of a frequency or
system RAT is higher than that of the serving
information frequency, the UEs always start inter-
frequency or inter-RAT measurements. If
the cell reselection priority of a frequency
is lower than or equal to that of the
serving frequency or if the cell reselection
priority of an RAT is lower than that of the


serving frequency, the UEs start inter-
frequency or inter-RAT measurements
only when the value of Cell selection RX
level value (dB) is lower than or equal to
the value of this parameter.
Unit: 2dB
Default Value: 9
CellResel SNonIntraSearchQ MOD CELLRESEL LBFD-002009 / Broadcast of Meaning: Indicates the RSRQ threshold
LST CELLRESEL TDLBFD-002009 system for starting inter-frequency or inter-RAT
LBFD-00201803 / information measurements. It determines the
and Re- an inter-frequency or inter-RAT
selection neighboring cell. For details, see 3GPP
TS 36.304.
Unit: dB
Default Value: 4
CellResel QRxLevMin MOD CELLRESEL LBFD-00201803 / Cell Selection Meaning: Indicates the minimum required
LST CELLRESEL TDLBFD-00201803 and Re- RX level used in intra-frequency
LBFD-002009 / selection E-UTRAN cell reselection, which
TDLBFD-002009 Broadcast of corresponds to the IE q-RxLevMin in
system SIB3. This value is included in the cell
information reselection criteria and used in the
evaluation of cell reselection. For details,
see 3GPP TS 36.304.
Unit: 2dBm
Default Value: -64
CellResel PMax MOD CELLRESEL LBFD-00201803 / Cell Selection Meaning: Indicates the maximum power
LST CELLRESEL TDLBFD-00201803 and Re- that the UE can apply to transmission in
LBFD-002009 / selection the intra-frequency neighboring cell. It is
TDLBFD-002009 Broadcast of used in cell reselection criteria to calculate
system the compensated power. If the value of
information this parameter is not specified, the
maximum power is subject to the UE
capability. For details, see 3GPP TS
36.304.
Unit: dBm
Default Value: 23
CellResel QQualMin MOD CELLRESEL LBFD-002009 / Broadcast of Meaning: Indicates the minimum required
LST CELLRESEL TDLBFD-002009 system RX signal quality used in intra-frequency
LBFD-00201803 / information E-UTRAN cell reselection, which
TDLBFD-00201803 Cell Selection corresponds to the IE q-QualMin in SIB3.
and Re- This value is included in criteria R and
selection used in the evaluation of cell reselection.
For details, see 3GPP TS 36.304.
Unit: dB
Default Value: -18
EutranInterNFreq QRxLevMin ADD EUTRANINTERNFREQ LBFD-00201803 / Cell Selection Meaning: Indicates the RX level required
MOD TDLBFD-00201803 and for a neighboring cell on the frequency to
EUTRANINTERNFREQ Reselection become a suitable cell for selection. It is
LST EUTRANINTERNFREQ included in criteria S and used in the
evaluation for cell selection. During the
evaluation for cell reselection, the UE
performs the following calculation: Srxlev
= Measured RSRP value of a neighboring
cell on the frequency - Value of this
parameter - Compensated power. If
Srxlev for a cell is better than a threshold
for a time-to-trigger, reselection to the cell
is started. For details, see 3GPP TS
36.304.
Unit: 2dBm
Default Value: -64
EutranInterNFreq Pmax ADD EUTRANINTERNFREQ LBFD-00201803 / Cell Selection Meaning: Indicates the maximum power
MOD TDLBFD-00201803 and that the UE can apply to transmission on
EUTRANINTERNFREQ Reselection the neighboring E-UTRAN frequency. It is
LST EUTRANINTERNFREQ used in cell reselection criteria to calculate
the compensated power. If the value of
this parameter is not specified, the
maximum power is subject to the UE
capability. For details, see 3GPP TS
36.304.
Unit: dBm


Default Value: 23
EutranInterNFreq QqualMin ADD EUTRANINTERNFREQ LBFD-00201803 / Cell Selection Meaning: Indicates the minimum required
MOD TDLBFD-00201803 and Re- received signal quality, which corresponds
EUTRANINTERNFREQ selection to the q-QualMin IE in system information
LST EUTRANINTERNFREQ block type 1 (SIB1) and is used to
calculate the Squal value for the serving
cell involved in cell selection and
reselection. If this parameter is set to 0,
SIB1 does not contain the q-QualMin IE. If
this parameter is set to a value other than
0, SIB1 contains the q-QualMin IE with
the same value as the parameter value.
For details about this parameter, see
3GPP TS 36.304.
Unit: dB
Default Value: -18
CellResel Qhyst MOD CELLRESEL LBFD-00201803 / Cell Selection Meaning: Indicates the hysteresis for cell
LST CELLRESEL TDLBFD-00201803 and Re- reselection when RSRP values are used
LBFD-002009 / selection in the evaluation. This parameter must be
TDLBFD-002009 Broadcast of set based on the slow fading
system characteristic of the area covered by the
information cell. The greater the slow fading variance
is, the larger the value of this parameter
must be set to. A larger value of the
hysteresis results in a larger boundary of
the serving cell and a lower probability of
cell reselection to neighboring cells.
GUI Value Range: DB0_Q_HYST(0dB),
DB1_Q_HYST(1dB), DB2_Q_HYST(2dB),
DB8_Q_HYST(8dB), DB10_Q_HYST
(10dB), DB12_Q_HYST(12dB),
(16dB), DB18_Q_HYST(18dB),
(22dB), DB24_Q_HYST(24dB)
Unit: dB
Actual Value Range: DB0_Q_HYST,
DB1_Q_HYST, DB2_Q_HYST,
DB24_Q_HYST
Default Value: DB4_Q_HYST(4dB)
EutranIntraFreqNCell CellQoffset ADD LBFD-00201801 / Coverage Meaning: Indicates the offset for the intra-
EUTRANINTRAFREQNCELL TDLBFD-00201801 Based Intra- frequency neighboring cell, which is used
MOD frequency in evaluation for cell reselections. A larger
EUTRANINTRAFREQNCELL
Handover value of this parameter results in a lower
LST
EUTRANINTRAFREQNCELL probability of cell reselections. If this
parameter is not set to dB0, it is delivered
in SIB4. For details, see 3GPP TS 36.331.
If this parameter is set to dB0, it is not
delivered in SIB4. In this situation, UEs
use 0 dB as the offset for cell
reselections. For details, see 3GPP TS
36.304.
GUI Value Range: dB-24(-24dB), dB-22
(-22dB), dB-20(-20dB), dB-18(-18dB), dB-
16(-16dB), dB-14(-14dB), dB-12(-12dB),
dB-10(-10dB), dB-8(-8dB), dB-6(-6dB),
dB-5(-5dB), dB-4(-4dB), dB-3(-3dB), dB-2
(-2dB), dB-1(-1dB), dB0(0dB), dB1(1dB),
dB2(2dB), dB3(3dB), dB4(4dB), dB5
(5dB), dB6(6dB), dB8(8dB), dB10(10dB),
dB12(12dB), dB14(14dB), dB16(16dB),
dB18(18dB), dB20(20dB), dB22(22dB),
dB24(24dB)
Unit: dB
Actual Value Range: dB-24, dB-22, dB-
20, dB-18, dB-16, dB-14, dB-12, dB-10,
dB-8, dB-6, dB-5, dB-4, dB-3, dB-2, dB-1,
dB0, dB1, dB2, dB3, dB4, dB5, dB6, dB8,
dB10, dB12, dB14, dB16, dB18, dB20,
dB22, dB24
Default Value: dB0(0dB)
EutranInterFreqNCell CellQoffset ADD LBFD-00201803 / Cell Selection Meaning: Indicates the offset for the inter-
EUTRANINTERFREQNCELL TDLBFD-00201803 and Re- frequency neighboring cell, which is used
MOD selection in evaluation for cell reselections. A larger
EUTRANINTERFREQNCELL
value of this parameter results in a lower
LST
EUTRANINTERFREQNCELL probability of cell reselections. If this
parameter is not set to dB0, it is delivered
in SIB5. For details, see 3GPP TS 36.331.


If this parameter is set to dB0, it is not
delivered in SIB5. In this situation, UEs
use 0 dB as the offset for cell
36.304.
(-22dB), dB-20(-20dB), dB-18(-18dB), dB-
16(-16dB), dB-14(-14dB), dB-12(-12dB),
dB-10(-10dB), dB-8(-8dB), dB-6(-6dB),
dB-5(-5dB), dB-4(-4dB), dB-3(-3dB), dB-2
(-2dB), dB-1(-1dB), dB0(0dB), dB1(1dB),
(5dB), dB6(6dB), dB8(8dB), dB10(10dB),
dB12(12dB), dB14(14dB), dB16(16dB),
dB18(18dB), dB20(20dB), dB22(22dB),
dB24(24dB)
Unit: dB
20, dB-18, dB-16, dB-14, dB-12, dB-10,
dB-8, dB-6, dB-5, dB-4, dB-3, dB-2, dB-1,
dB10, dB12, dB14, dB16, dB18, dB20,
dB22, dB24
EutranInterNFreq QoffsetFreq ADD EUTRANINTERNFREQ LBFD-00201803 / Cell Selection Meaning: Indicates the frequency-specific
MOD TDLBFD-00201803 and Re- offset for the neighboring E-UTRAN
EUTRANINTERNFREQ selection frequency that applies to UEs in idle
LST EUTRANINTERNFREQ mode. It is contained in system
information block type 5 (SIB5) and
delivered to UEs in idle mode for cell
reselection. For details, see 3GPP TS
36.331.
(-22dB), dB-20(-20dB), dB-18(-18dB), dB-
16(-16dB), dB-14(-14dB), dB-12(-12dB),
dB-10(-10dB), dB-8(-8dB), dB-6(-6dB),
dB-5(-5dB), dB-4(-4dB), dB-3(-3dB), dB-2
(-2dB), dB-1(-1dB), dB0(0dB), dB1(1dB),
(5dB), dB6(6dB), dB8(8dB), dB10(10dB),
dB12(12dB), dB14(14dB), dB16(16dB),
dB18(18dB), dB20(20dB), dB22(22dB),
dB24(24dB)
Unit: dB
20, dB-18, dB-16, dB-14, dB-12, dB-10,
dB-8, dB-6, dB-5, dB-4, dB-3, dB-2, dB-1,
dB10, dB12, dB14, dB16, dB18, dB20,
dB22, dB24
EutranIntraFreqNCell CellMeasPriority ADD LBFD-00201801 / Coverage Meaning: Indicates the priority of

EUTRANINTRAFREQNCELL TDLBFD-00201801 Based Intra- measurement on the intra-frequency
MOD frequency neighboring cell. The eNodeB
EUTRANINTRAFREQNCELL LBFD-00201804 /
TDLBFD-00201804 Handover preferentially contains the information
LST
EUTRANINTRAFREQNCELL LBFD-00201805 / Distance Based about a neighboring cell with this priority
TDLBFD-00201805 Inter-frequency set to HIGH_PRIORITY while delivering a
Handover measurement configuration.
Service Based GUI Value Range: LOW_PRIORITY(Low
Inter-frequency Priority), HIGH_PRIORITY(High Priority)
Handover Unit: None
Actual Value Range: LOW_PRIORITY,
HIGH_PRIORITY
Default Value: LOW_PRIORITY(Low
Priority)
EutranInterFreqNCell CellMeasPriority ADD LBFD-00201802 / Coverage Meaning: Indicates the priority of

EUTRANINTERFREQNCELL TDLBFD-00201802 Based Inter- measurement on the inter-frequency
MOD frequency neighboring cell. The eNodeB
EUTRANINTERFREQNCELL LBFD-00201804 /
TDLBFD-00201804 Handover preferentially contains the information
LST
EUTRANINTERFREQNCELL LBFD-00201805 / Distance Based about a neighboring cell with this priority
TDLBFD-00201805 Inter-frequency set to HIGH_PRIORITY while delivering a
Handover measurement configuration.
TDLOFD-001050
Service Based GUI Value Range: LOW_PRIORITY(Low
Inter-frequency Priority), HIGH_PRIORITY(High Priority)
Handover Unit: None
Mobility Actual Value Range: LOW_PRIORITY,
between LTE HIGH_PRIORITY
TDD and LTE Default Value: LOW_PRIORITY(Low
FDD Priority)
CellResel TReselEutran MOD CELLRESEL LBFD-00201803 / Cell Selection Meaning: Indicates the evaluation period
LST CELLRESEL TDLBFD-00201803 and Re- for a UE to determine whether to perform
LBFD-002009 / selection cell reselections to a new E-UTRAN cell.
TDLBFD-002009 Broadcast of If the signal quality of a new E-UTRAN
system cell is better than that of the serving cell
information within the period specified by this
parameter and a UE camps on the
serving cell for more than 1s, the UE


initiates cell reselections to the new
E-UTRAN cell.
Unit: s
Default Value: 1
EutranInterNFreq EutranReselTime ADD EUTRANINTERNFREQ LBFD-00201803 / Cell Selection Meaning: Indicates the evaluation
MOD TDLBFD-00201803 and Re- duration for a UE to determine whether to
EUTRANINTERNFREQ selection reselect the inter-frequency neighboring
LST EUTRANINTERNFREQ cell to camp on. If the signal quality in an
inter-frequency neighboring cell is better
than that in the serving cell for the period
specified by this parameter and a UE
camps on the serving cell for more than
1s, the UE attempts to reselect the inter-
frequency neighboring cell to camp on.
This parameter is contained in SIB5. For
Unit: s
Default Value: 1
UtranNFreq QRxLevMin ADD UTRANNFREQ LBFD-00201803 / Cell Selection Meaning: Indicates the RX level required
MOD UTRANNFREQ TDLBFD-00201803 and for a neighboring cell on the UTRAN
LST UTRANNFREQ Reselection / frequency to become a candidate for
Cell Selection selection. It is included in criteria S and
and Re- used in the evaluation for cell selection.
selection During the evaluation for cell reselection,
the UE performs the following calculation:
Srxlev = Measured RSRP value of a
neighboring cell on the frequency - Value
of this parameter - Compensated power. If
Srxlev for a neighboring cell is better than
a threshold for a time-to-trigger,
reselection to the cell is started. For
Unit: 2dBm
Default Value: -58
UtranNFreq Qqualmin ADD UTRANNFREQ LBFD-00201803 / Cell Selection Meaning: Indicates the minimum quality
MOD UTRANNFREQ TDLBFD-00201803 and level required for a cell on the UTRAN
LST UTRANNFREQ Reselection / frequency to become a candidate for
Cell Selection reselection. This parameter is applied only
and Re- to reselection to UTRAN FDD cells. A
selection neighboring cell on the UTRAN frequency
can become a candidate for reselection
only when the signal quality of the cell is
better than the value of this parameter.
Unit: dB
Default Value: -22
UtranNFreq PmaxUtran ADD UTRANNFREQ LBFD-00201803 / Cell Selection Meaning: Indicates the maximum power
MOD UTRANNFREQ TDLBFD-00201803 and that the UE can apply to transmission on
LST UTRANNFREQ Reselection the UTRAN frequency. It is used in criteria
S to calculate the compensated power.
Unit: dBm
Default Value: 24
GeranNfreqGroup QRxLevMin ADD GERANNFREQGROUP LBFD-00201803 / Cell Selection Meaning: Indicates the minimum GERAN
MOD TDLBFD-00201803 and signal level required for cell reselection
GERANNFREQGROUP Reselection based on criteria S. Assume that: Srxlev =
LST GERANNFREQGROUP Measured RSSI of a neighboring cell on a
frequency in the GERAN carrier frequency
group - Actual value of this parameter -
Compensated power. If Srxlev is
consistently greater than a specific
threshold for cell reselection, the UE
reselects this neighboring cell. For details,
see 3GPP TS 36.104. Note: Actual value
of this parameter = -115 + 2 x GUI value
of this parameter
Unit: 2dBm
Default Value: 0
GeranNfreqGroup PmaxGeran ADD GERANNFREQGROUP LBFD-00201803 / Cell Selection Meaning: Indicates the maximum power
MOD TDLBFD-00201803 and that the UE can apply to transmission on
GERANNFREQGROUP Reselection a frequency in the GERAN carrier
LST GERANNFREQGROUP frequency group. It is used in cell
reselection criteria to calculate the
compensated power. If the value of this


parameter is not specified, the maximum
power is subject to the UE capability. For
Unit: dBm
Default Value: 0
CellResel ThrshServLowQ MOD CELLRESEL LBFD-002009 / Broadcast of Meaning: Indicates the RSRQ threshold
LST CELLRESEL TDLBFD-002009 system for cell reselection to cells on lower-
LBFD-00201803 / information priority frequencies. It determines the
and Re- inter-frequency or inter-RAT neighboring
selection cells on lower-priority frequencies. For
Unit: dB
Default Value: 0
EutranInterNFreq ThreshXhighQ ADD EUTRANINTERNFREQ LBFD-00201803 / Cell Selection Meaning:

MOD TDLBFD-00201803 and Indicates the RSRQ-based minimum RX
EUTRANINTERNFREQ Reselection / level required for a neighboring cell on the
LST EUTRANINTERNFREQ Cell Selection frequency to become a candidate for
and Re- reselection if the RSRQ-based priority of
selection the frequency is higher than that of the
serving frequency.
After measurements are started for
neighboring cells on the neighboring
E-UTRAN frequency, the UE reselects to
a neighboring cell on the frequency only if
the RSRQ-based RX level of the cell is
higher than the value specified by this
parameter for a time-to-trigger. For
Unit: dB
Default Value: 0
UtranNFreq ThreshXHighQ ADD UTRANNFREQ LBFD-00201803 / Cell Selection Meaning:

MOD UTRANNFREQ TDLBFD-00201803 and Indicates the RSRQ-based minimum RX
LST UTRANNFREQ Reselection / level required for a neighboring cell on the
Cell Selection frequency to become a candidate for
selection the frequency is higher than that of the
serving frequency.
neighboring cells on the UTRAN
frequency, the UE reselects to a
neighboring cell on the frequency only if
the RSRQ-based RX level of the cell is
Unit: dB
Default Value: 0
CellReselUtran TReselUtran ADD CELLRESELUTRAN LBFD-002009 / Broadcast of Meaning: Indicates the evaluation period
MOD CELLRESELUTRAN TDLBFD-002009 system for a UE to determine whether to reselect
LST CELLRESELUTRAN LBFD-00201803 / information a neighboring UTRAN cell to camp on.
TDLBFD-00201803 Cell Selection During the evaluation period, if the signal
and Re- quality in a neighboring UTRAN cell is
selection better than that in the serving cell and a
UE camps on the serving cell for more
than 1s, the UE attempts to reselect the
neighboring UTRAN cell to camp on.
Unit: s
Default Value: 1
UtranNFreq ThreshXHigh ADD UTRANNFREQ LBFD-00201803 / Cell Selection Meaning: Indicates the minimum RX level
MOD UTRANNFREQ TDLBFD-00201803 and required for a neighboring cell on the
LST UTRANNFREQ Reselection UTRAN frequency to become a candidate
for reselection if the priority of the
frequency is higher than that of the
serving frequency. After measurements
are started for neighboring cells on the
UTRAN frequency, the UE reselects to a
the RX level of the cell is higher than the
value specified by this parameter for a
time-to-trigger. For details, see 3GPP TS
36.331.
Unit: 2dB


Default Value: 6
GeranNfreqGroup ThreshXHigh ADD GERANNFREQGROUP LBFD-00201803 / Cell Selection Meaning:

MOD TDLBFD-00201803 and Indicates the RX level required for a
GERANNFREQGROUP Reselection neighboring cell on a frequency in the
LST GERANNFREQGROUP
GERAN carrier frequency group to
become a candidate for reselection if the
priority of the frequency is higher than that
of the serving frequency.
neighboring cells on a frequency in the
GERAN carrier frequency group, the UE
reselects to a cell on the frequency only if
the RX level of the cell is better than the
36.104.
Unit: 2dB
Default Value: 7
CellReselGeran TReselGeran ADD CELLRESELGERAN LBFD-00201803 / Cell Selection Meaning: Indicates the evaluation period
MOD CELLRESELGERAN TDLBFD-00201803 and Re- for a UE to determine whether to reselect
LST CELLRESELGERAN LBFD-002009 / selection a neighboring GERAN cell to camp on.
TDLBFD-002009 Broadcast of During the evaluation period, if the signal
system quality in a neighboring GERAN cell is
information better than that in the serving cell and a
UE camps on the serving cell for more
than 1s, the UE attempts to reselect the
neighboring GERAN cell to camp on.
Unit: s
Default Value: 1
Cdma2000BandClass Cdma20001XrttThreshXHigh ADD LBFD-00201803 / Cell Selection Meaning: Indicates the RX signal level
CDMA2000BANDCLASS TDLBFD-00201803 and Re- required for a cell on a frequency in the
MOD selection higher-priority CDMA2000 1xRTT band
TDLOFD-001035 CS Fallback to class to become a candidate for cell
LST
CDMA2000BANDCLASS TDLOFD-001090 CDMA2000 reselection. After measurements are
1xRTT started for cells on a frequency in the
Enhanced CS band class, a cell on the frequency can
Fallback to become a candidate for reselection only if
CDMA2000 the RX signal level of the cell is higher
1xRTT than the value specified by this parameter
for a time-to-trigger. For details, see
3GPP TS 36.304 5.2.4.5.
Unit: 0.5dB
Actual Value Range: -31.5~0
Default Value: -34
Cdma2000BandClass Cdma2000HrpdThreshXHigh ADD LBFD-00201803 / Cell Selection Meaning: Indicates the RX signal level
CDMA2000BANDCLASS TDLBFD-00201803 and Re- required for a cell on a frequency in the
MOD selection higher-priority CDMA2000 HRPD band
TDLOFD-001021 PS Inter-RAT class to become a candidate for cell
LST
CDMA2000BANDCLASS Mobility reselection. After measurements are
between started for cells on a frequency in the
E-UTRAN and band class, a cell on the frequency can
CDMA2000 become a candidate for reselection only if
the RX signal level of the cell is higher
than the value specified by this parameter
3GPP TS 36.304 5.2.4.5.
Unit: 0.5dB
Default Value: -26
CellReselCdma2000 Cdma1XrttTreselection ADD LBFD-00201803 / Cell Selection Meaning: Indicates the evaluation period
CELLRESELCDMA2000 TDLBFD-00201803 and Re- for a UE to determine whether to reselect
MOD selection a neighboring CDMA2000 1xRTT cell to
CELLRESELCDMA2000 LOFD-001035 /
TDLOFD-001035 CS Fallback to camp on. During the evaluation period, if
LST CELLRESELCDMA2000
LBFD-002009 / CDMA2000 the signal quality in a neighboring
TDLBFD-002009 1xRTT CDMA2000 1xRTT cell is better than that
Broadcast of in the serving cell and a UE camps on the
TDLOFD-001090
system serving cell for more than 1s, the UE
information attempts to reselect the neighboring
CDMA2000 1xRTT cell to camp on. For
Enhanced CS
details about this parameter, see 3GPP
Fallback to
TS 36.331.
CDMA2000
1xRTT GUI Value Range: 0~7
Unit: None
Default Value: 1
CellReselCdma2000 TreselectionHrpd ADD LBFD-00201803 / Cell Selection Meaning: Indicates the evaluation period
CELLRESELCDMA2000 TDLBFD-00201803 and Re- for a UE to determine whether to reselect
MOD selection a neighboring CDMA2000 HRPD cell to
TDLOFD-001021 camp on. During the evaluation period, if


LBFD-002009 / PS Inter-RAT the signal quality in a neighboring
TDLBFD-002009 Mobility CDMA2000 HRPD cell is better than that
between in the serving cell and a UE camps on the
E-UTRAN and serving cell for more than 1s, the UE
CDMA2000 attempts to reselect the neighboring
Broadcast of CDMA2000 HRPD cell to camp on. For
system details about this parameter, see 3GPP
information TS 36.331.
Unit: s
Default Value: 1
EutranInterNFreq ThreshXhigh ADD EUTRANINTERNFREQ LBFD-00201803 / Cell Selection Meaning: Indicates the RX level required
MOD TDLBFD-00201803 and for a neighboring cell on the frequency to
EUTRANINTERNFREQ Reselection become a candidate for reselection if the
LST EUTRANINTERNFREQ priority of the frequency is higher than that
of the serving frequency. After
measurements are started for neighboring
cells on the frequency, the UE reselects to
a neighboring cell on the frequency only if
the RX level of the cell is better than the
36.331.
Unit: 2dB
Default Value: 11
EutranInterNFreq ThreshXlowQ ADD EUTRANINTERNFREQ LBFD-00201803 / Cell Selection Meaning:

MOD TDLBFD-00201803 and Indicates the RSRQ-based minimum RX
EUTRANINTERNFREQ Reselection / level required for a neighboring cell on the
LST EUTRANINTERNFREQ Cell Selection frequency to become a candidate for
selection the frequency is lower than that of the
serving frequency.
neighboring cells on a frequency in the
GERAN carrier frequency group, the UE
reselects to a neighboring cell on the
frequency only if the RSRQ-based RX
level of the serving cell is lower than a
specified threshold and that of the cell is
Unit: dB
Default Value: 0
UtranNFreq ThreshXLowQ ADD UTRANNFREQ LBFD-00201803 / Cell Selection Meaning:

MOD UTRANNFREQ TDLBFD-00201803 and Indicates the RSRQ-based minimum RX
LST UTRANNFREQ Reselection / level required for a neighboring cell on the
Cell Selection frequency to become a candidate for
selection the frequency is lower than that of the
serving frequency.
neighboring cells on the frequency, the
UE reselects to a cell on the frequency
only if the RSRQ-based RX level of the
serving cell is lower than a specified
threshold and that of the cell is higher
than the value specified by this parameter
3GPP TS 36.331.
Unit: dB
Default Value: 0
UtranNFreq ThreshXLow ADD UTRANNFREQ LBFD-00201803 / Cell Selection Meaning: Indicates the minimum RX level
MOD UTRANNFREQ TDLBFD-00201803 and required for a neighboring cell on the
LST UTRANNFREQ Reselection UTRAN frequency to become a candidate
for reselection if the priority of the
frequency is lower than that of the serving
frequency. After measurements are
started for neighboring cells on the
UTRAN frequency, the UE reselects to a
the RX level of the serving cell is lower
than a specified threshold and that of the
cell is higher than the value specified by
this parameter for a time-to-trigger. For
Unit: 2dB
Default Value: 6

GeranNfreqGroup ThreshXLow ADD GERANNFREQGROUP LBFD-00201803 / Cell Selection Meaning:

MOD TDLBFD-00201803 and Indicates the minimum RX level required
GERANNFREQGROUP Reselection for a neighboring cell on the GERAN
LST GERANNFREQGROUP
frequency to become a candidate for
reselection if the priority of this target
frequency is lower than that of the serving
frequency.
neighboring cells on the target frequency,
the UE reselects a neighboring cell on this
frequency only when the RX level of the
serving cell is lower than a specified
threshold and that of the neighboring cell
is higher than the value specified by this
Unit: 2dB
Default Value: 7
Cdma2000BandClass Cdma20001XrttThreshXLow ADD LBFD-00201803 / Cell Selection Meaning:

CDMA2000BANDCLASS TDLBFD-00201803 and Re- Indicates the RX signal level required for
MOD selection
CDMA2000BANDCLASS LOFD-001035 / a cell on a frequency in the lower-priority
LST TDLOFD-001035 CS Fallback to CDMA2000 1xRTT band class to become
CDMA2000BANDCLASS TDLOFD-001090 CDMA2000 a candidate for cell reselection.
1xRTT After measurements are started for cells
Enhanced CS on a frequency in the band class, a cell on
Fallback to the frequency can become a candidate for
CDMA2000 reselection only if the RX signal level of
1xRTT the cell is better than the value specified
by this parameter for a time-to-trigger. For
details, see 3GPP TS 36.304 5.2.4.5.
Unit: 0.5dB
Default Value: -34
Cdma2000BandClass Cdma2000HrpdThreshXLow ADD LBFD-00201803 / Cell Selection Meaning:

CDMA2000BANDCLASS TDLBFD-00201803 and Re- Indicates the RX signal level required for
MOD selection
CDMA2000BANDCLASS LOFD-001021 / a cell on a frequency in the lower-priority
LST TDLOFD-001021 PS Inter-RAT CDMA2000 HRPD band class to become
CDMA2000BANDCLASS Mobility a candidate for cell reselection.
between After measurements are started for cells
E-UTRAN and on a frequency in the band class, a cell on
CDMA2000 the frequency can become a candidate for
reselection only if the RX signal level of
the cell is lower than the value specified
by this parameter for a time-to-trigger. For
details, see 3GPP TS 36.304 5.2.4.5.
Unit: 0.5dB
Default Value: -26
CellResel ThrshServLow MOD CELLRESEL LBFD-00201803 / Cell Selection Meaning: Indicates the threshold used in
LST CELLRESEL TDLBFD-00201803 and Re- the evaluation of reselection to a cell on a
LBFD-002009 / selection lower priority E-UTRAN frequency or on
TDLBFD-002009 Broadcast of an inter-RAT frequency. Cell reselection
system to a cell on a lower priority E-UTRAN
information frequency or on an inter-RAT frequency is
performed if no cell on the serving
frequency or on a higher priority
E-UTRAN frequency fulfills criteria 1 for
inter-frequency and inter-RAT
36.304.
Unit: 2dB
Default Value: 7
EutranInterNFreq ThreshXlow ADD EUTRANINTERNFREQ LBFD-00201803 / Cell Selection Meaning:

MOD TDLBFD-00201803 and Indicates the minimum RX level required
EUTRANINTERNFREQ Reselection for a neighboring cell on the frequency to
LST EUTRANINTERNFREQ
become a candidate for reselection if the
priority of the frequency is lower than that
of the serving frequency.
neighboring cells on the frequency, the
UE reselects to a neighboring cell on the
frequency only if the RX level of the
serving cell is lower than a Serving
frequency lower priority threshold and that
of the cell is higher than the value
specified by this parameter for a time-to-
trigger. For details, see 3GPP TS 36.331.
Unit: 2dB


Default Value: 11
CellResel SpeedDepReselCfgInd MOD CELLRESEL LBFD-00201803 / Cell Selection Meaning: Indicates whether to set the
LST CELLRESEL TDLBFD-00201803 and Re- parameters related to speed-dependent
LBFD-002009 / selection cell reselection.
CellResel SpeedStateSfCfgInd MOD CELLRESEL LBFD-00201803 / Cell Selection Meaning: Indicates whether to set the
LST CELLRESEL TDLBFD-00201803 and Re- scaling parameters for speed-dependent
LBFD-002009 / selection cell reselection within E-UTRAN.
EutranInterNFreq SpeedDependSPCfgInd ADD EUTRANINTERNFREQ LBFD-00201803 / Cell Selection Meaning:

MOD TDLBFD-00201803 and Re- Indicates whether to set the speed-
EUTRANINTERNFREQ selection dependent scaling parameters related to
LST EUTRANINTERNFREQ
cell reselection.
If this parameter is set to NOT_CFG,
speed-dependent cell reselections are not
supported by default.
Unit: None
CellReselUtran SpeedStateSfCfgInd ADD CELLRESELUTRAN LBFD-00201803 / Cell Selection Meaning: Indicates whether to set the
MOD CELLRESELUTRAN TDLBFD-00201803 and Re- speed-dependent scaling parameters
LST CELLRESELUTRAN LBFD-002009 / selection related to cell reselection to UTRAN.
CellReselGeran SpeedStateSfCfgInd ADD CELLRESELGERAN LBFD-00201803 / Cell Selection Meaning: Indicates whether to set the
MOD CELLRESELGERAN TDLBFD-00201803 and Re- speed-dependent scaling parameters
LST CELLRESELGERAN LBFD-002009 / selection related to cell reselection to GERAN.
CellReselCdma2000 SpeedStateSfCfgInd ADD LBFD-00201803 / Cell Selection Meaning: Indicates whether to set the
CELLRESELCDMA2000 TDLBFD-00201803 and Re- speed-dependent scaling parameters
MOD selection related to cell reselection to CDMA2000
TDLOFD-001021 PS Inter-RAT HRPD. For details, see 3GPP TS 36.331.
LBFD-002009 / Mobility GUI Value Range: NOT_CFG(Not
TDLBFD-002009 between configure), CFG(Configure)
E-UTRAN and Unit: None
CDMA2000 Actual Value Range: NOT_CFG, CFG
Broadcast of Default Value: NOT_CFG(Not configure)
system
information
CellReselCdma2000 Cdma1XrttSpeedStateCfgInd ADD LBFD-00201803 / Cell Selection Meaning: Indicates whether speed-
CELLRESELCDMA2000 TDLBFD-00201803 and Re- dependent scaling parameters need to be
MOD selection set for cell reselection to CDMA2000
TDLOFD-001035 CS Fallback to 1xRTT.
LBFD-002009 / CDMA2000 GUI Value Range: NOT_CFG(Not
TDLBFD-002009 1xRTT configure), CFG(Configure)
TDLOFD-001090 Broadcast of Unit: None
system Actual Value Range: NOT_CFG, CFG
information Default Value: NOT_CFG(Not configure)
Enhanced CS
Fallback to
CDMA2000
1xRTT
CellResel NCellChangeMedium MOD CELLRESEL LBFD-00201803 / Cell Selection Meaning: Indicates the threshold of the
LST CELLRESEL TDLBFD-00201803 and Re- number of cell reselections, which is used
LBFD-002009 / selection for a UE to enter the medium mobility
TDLBFD-002009 Broadcast of state. This parameter is one of the key
system parameters in determining the mobility
information state of the UE. During the UE mobility
evaluation, if the number of cell
reselections is greater than this parameter
value and is less than or equal to the
NCellChangeHigh parameter value, the
UE enters the medium mobility state.
Unit: None


Default Value: 4
CellResel NCellChangeHigh MOD CELLRESEL LBFD-00201803 / Cell Selection Meaning: Indicates the threshold of the
LST CELLRESEL TDLBFD-00201803 and Re- number of cell reselections, which is used
LBFD-002009 / selection for a UE to enter the high mobility state.
TDLBFD-002009 Broadcast of This parameter is one of the key
system parameters in determining the mobility
information state of the UE. During the UE mobility
evaluation, if the number of cell
reselections is greater than this parameter
value, the UE enters the high mobility
state.
Unit: None
Default Value: 8
CellResel TEvaluation MOD CELLRESEL LBFD-002009 / Broadcast of Meaning: Indicates the duration in which
LST CELLRESEL TDLBFD-002009 system the mobility status of the UE is evaluated.
LBFD-00201803 / information This parameter is one of the key
TDLBFD-00201803 Cell Selection parameters in deciding on the UE
and Re- mobility. A smaller value of this parameter
selection may lead to more frequent switching
among mobility status and lower decision
accuracy. A larger value of this parameter
GUI Value Range:
S30_T_EVALULATION(30s),
S240_T_EVALULATION(240s)
Unit: s
Actual Value Range:
S30_T_EVALULATION,
S60_T_EVALULATION,
S120_T_EVALULATION,
S180_T_EVALULATION,
S240_T_EVALULATION
Default Value: S60_T_EVALULATION
(60s)
CellResel THystNormal MOD CELLRESEL LBFD-002009 / Broadcast of Meaning: Indicates the extra duration
LST CELLRESEL TDLBFD-002009 system required in the evaluation before the UE
LBFD-00201803 / information can enter the normal-mobility state. This
TDLBFD-00201803 Cell Selection parameter can prevent UEs from
and Re- frequently switching from the high- or
selection medium-mobility state to the normal-
mobility state, and is one of the key
parameters in deciding on the UE
mobility. A larger value of this parameter
leads to a lower probability of transition
from the high- or medium-mobility state to
the normal-mobility state but higher
decision accuracy. A smaller value of this
parameter leads to the opposite effect.
GUI Value Range:
S30_T_HYST_NORMAL(30s),
S240_T_HYST_NORMAL(240s)
Unit: s
Actual Value Range:
S30_T_HYST_NORMAL,
S60_T_HYST_NORMAL,
S120_T_HYST_NORMAL,
S180_T_HYST_NORMAL,
S240_T_HYST_NORMAL
Default Value: S30_T_HYST_NORMAL
(30s)
CellResel TReselEutranSfMedium MOD CELLRESEL LBFD-00201803 / Cell Selection Meaning: Indicates the scaling factor
LST CELLRESEL TDLBFD-00201803 and Re- applied to TReselEutran for medium-
LBFD-002009 / selection mobility UEs. The actual duration of cell
TDLBFD-002009 Broadcast of reselection for medium-mobility UEs to
system E-UTRAN is equal to the product of
information TReselEutran and
TReselEutranSfMedium.
GUI Value Range:
T_RESEL_SF_0DOT25(0.25),
T_RESEL_SF_1DOT0(1.0)
Unit: None
Actual Value Range:
T_RESEL_SF_0DOT25,
T_RESEL_SF_0DOT5,
T_RESEL_SF_0DOT75,
T_RESEL_SF_1DOT0
Default Value: T_RESEL_SF_1DOT0(1.0)


EutranInterNFreq TReselEutranSfMedium ADD EUTRANINTERNFREQ LBFD-00201803 / Cell Selection Meaning: Indicates the scaling factor
MOD TDLBFD-00201803 and Re- applied to the cell reselection duration for
EUTRANINTERNFREQ selection medium-mobility UEs. This parameter is
LST EUTRANINTERNFREQ delivered in SIB5. For details, see 3GPP
TS 36.331.
GUI Value Range: 0DOT25_ENUM(0.25),
0DOT5_ENUM(0.5), 0DOT75_ENUM
(0.75), 1DOT0_ENUM(1.0)
Unit: None
Actual Value Range: 0DOT25_ENUM,
0DOT5_ENUM, 0DOT75_ENUM,
1DOT0_ENUM
Default Value: 1DOT0_ENUM(1.0)
CellReselUtran TReselUtranSfMedium ADD CELLRESELUTRAN LBFD-00201803 / Cell Selection Meaning:

MOD CELLRESELUTRAN TDLBFD-00201803 and Re- Indicates the scaling factor applied to
LST CELLRESELUTRAN LBFD-002009 / selection TReselUtran for medium-mobility UEs.
TDLBFD-002009 Broadcast of The actual duration of cell reselection of
system medium-mobility UEs to UTRAN is equal
information to TReselUtran multiplied by
TReselUtranSfMedium.
The value T_RESEL_SF_0DOT25 means
a scaling factor of 0.25,
T_RESEL_SF_0DOT5 means 0.5, and so
on.
GUI Value Range:
Unit: None
Actual Value Range:
T_RESEL_SF_0DOT25,
T_RESEL_SF_0DOT5,
T_RESEL_SF_0DOT75,
T_RESEL_SF_1DOT0
CellReselGeran TReselGeranSfMedium ADD CELLRESELGERAN LBFD-00201803 / Cell Selection Meaning: Indicates the scaling factor
MOD CELLRESELGERAN TDLBFD-00201803 and Re- applied to TReselGeran for medium-
LST CELLRESELGERAN LBFD-002009 / selection mobility UEs. The actual duration of cell
TDLBFD-002009 Broadcast of reselection of medium-mobility UEs to
system GERAN is equal to TReselGeran
information multiplied by TReselGeranSfMedium.
GUI Value Range:
Unit: None
Actual Value Range:
T_RESEL_SF_0DOT25,
T_RESEL_SF_0DOT5,
T_RESEL_SF_0DOT75,
T_RESEL_SF_1DOT0
CellReselCdma2000 TReselCdmaHrpdSfMedium ADD LBFD-00201803 / Cell Selection Meaning: Indicates the scaling factor
CELLRESELCDMA2000 TDLBFD-00201803 and Re- applied to TReselCdmaHrpd for medium-
MOD selection mobility UEs. The actual duration of cell
TDLOFD-001021 PS Inter-RAT reselection of medium-mobility UEs to
LBFD-002009 / Mobility CDMA2000 HRPD is equal to
TDLBFD-002009 between TReselCdmaHrpd multiplied by
E-UTRAN and TReselCdmaHrpdSfMedium. For details,
CDMA2000 see 3GPP TS 36.331.
Broadcast of GUI Value Range:
system T_RESEL_SF_0DOT25(0.25),
information T_RESEL_SF_0DOT5(0.5),
Unit: None
Actual Value Range:
T_RESEL_SF_0DOT25,
T_RESEL_SF_0DOT5,
T_RESEL_SF_0DOT75,
T_RESEL_SF_1DOT0
CellReselCdma2000 Cdma1XrttSfMedium ADD LBFD-00201803 / Cell Selection Meaning: Indicates the scaling factor
CELLRESELCDMA2000 TDLBFD-00201803 and Re- applicable to cell reselection of medium-
MOD selection mobility UEs to CDMA2000 1xRTT. For
TDLOFD-001035 CS Fallback to details, see 3GPP TS 36.331.
LBFD-002009 / CDMA2000 GUI Value Range:
TDLBFD-002009 1xRTT T_RESEL_SF_0DOT25(0.25),
TDLOFD-001090 Broadcast of T_RESEL_SF_0DOT5(0.5),
information T_RESEL_SF_1DOT0(1.0)
Enhanced CS Unit: None
Fallback to Actual Value Range:
CDMA2000 T_RESEL_SF_0DOT25,
1xRTT T_RESEL_SF_0DOT5,


T_RESEL_SF_0DOT75,
T_RESEL_SF_1DOT0
CellResel TReselEutranSfHigh MOD CELLRESEL LBFD-00201803 / Cell Selection Meaning: Indicates the scaling factor
LST CELLRESEL TDLBFD-00201803 and Re- applied to TReselEutran for high-mobility
LBFD-002009 / selection UEs. The actual duration of cell
TDLBFD-002009 Broadcast of reselection of high-mobility UEs to
system E-UTRAN is equal to TReselEutran
information multiplied by TReselEutranSfHigh.
GUI Value Range:
Unit: None
Actual Value Range:
T_RESEL_SF_0DOT25,
T_RESEL_SF_0DOT5,
T_RESEL_SF_0DOT75,
T_RESEL_SF_1DOT0
Default Value: T_RESEL_SF_0DOT75
(0.75)
EutranInterNFreq TReselEutranSfHigh ADD EUTRANINTERNFREQ LBFD-00201803 / Cell Selection Meaning: Indicates the scaling factor
MOD TDLBFD-00201803 and Re- applied to the cell reselection duration for
EUTRANINTERNFREQ selection high-mobility UEs. This parameter is
LST EUTRANINTERNFREQ delivered in SIB5. For details, see 3GPP
TS 36.331.
GUI Value Range: 0DOT25_ENUM(0.25),
0DOT5_ENUM(0.5), 0DOT75_ENUM
(0.75), 1DOT0_ENUM(1.0)
Unit: None
Actual Value Range: 0DOT25_ENUM,
0DOT5_ENUM, 0DOT75_ENUM,
1DOT0_ENUM
Default Value: 0DOT75_ENUM(0.75)
CellReselUtran TReselUtranSfHigh ADD CELLRESELUTRAN LBFD-00201803 / Cell Selection Meaning:

MOD CELLRESELUTRAN TDLBFD-00201803 and Re- Indicates the scaling factor applied to
LST CELLRESELUTRAN LBFD-002009 / selection TReselUtran for high-mobility UEs. The
TDLBFD-002009 Broadcast of actual duration of cell reselection of high-
system mobility UEs to UTRAN is equal to
information TReselUtran multiplied by
TReselUtranSfHigh.
The value T_RESEL_SF_0DOT25 means
a scaling factor of 0.25,
T_RESEL_SF_0DOT5 means 0.5, and so
on.
GUI Value Range:
Unit: None
Actual Value Range:
T_RESEL_SF_0DOT25,
T_RESEL_SF_0DOT5,
T_RESEL_SF_0DOT75,
T_RESEL_SF_1DOT0
(0.75)
CellReselGeran TReselGeranSfHigh ADD CELLRESELGERAN LBFD-00201803 / Cell Selection Meaning: Indicates the scaling factor
MOD CELLRESELGERAN TDLBFD-00201803 and Re- applied to TReselGeran for high-mobility
LST CELLRESELGERAN LBFD-002009 / selection UEs. The actual duration of cell
TDLBFD-002009 Broadcast of reselection of high-mobility UEs to
system GERAN is equal to TReselGeran
information multiplied by TReselGeranSfHigh.
GUI Value Range:
Unit: None
Actual Value Range:
T_RESEL_SF_0DOT25,
T_RESEL_SF_0DOT5,
T_RESEL_SF_0DOT75,
T_RESEL_SF_1DOT0
(0.75)
CellReselCdma2000 TReselCdmaHrpdSfHigh ADD LBFD-00201803 / Cell Selection Meaning: Indicates the scaling factor
CELLRESELCDMA2000 TDLBFD-00201803 and Re- applied to TReselCdmaHrpd for high-
MOD selection mobility UEs. The actual duration of cell
TDLOFD-001021 PS Inter-RAT reselection of high-mobility UEs to
LBFD-002009 / Mobility CDMA2000 HRPD is equal to
TDLBFD-002009 between TReselCdmaHrpd multiplied by
E-UTRAN and TReselCdmaHrpdSfHigh. For details, see
CDMA2000 3GPP TS 36.331.


Broadcast of GUI Value Range:
information T_RESEL_SF_0DOT5(0.5),
Unit: None
Actual Value Range:
T_RESEL_SF_0DOT25,
T_RESEL_SF_0DOT5,
T_RESEL_SF_0DOT75,
T_RESEL_SF_1DOT0
(0.75)
CellReselCdma2000 Cdma1XrttSfHigh ADD LBFD-00201803 / Cell Selection Meaning: Indicates the scaling factor
CELLRESELCDMA2000 TDLBFD-00201803 and Re- applicable to cell reselection of high-
MOD selection mobility UEs to CDMA2000 1xRTT. For
TDLOFD-001035 CS Fallback to details, see 3GPP TS 36.331.
LBFD-002009 / CDMA2000 GUI Value Range:
TDLBFD-002009 1xRTT T_RESEL_SF_0DOT25(0.25),
TDLOFD-001090 Broadcast of T_RESEL_SF_0DOT5(0.5),
information T_RESEL_SF_1DOT0(1.0)
Enhanced CS Unit: None
Fallback to Actual Value Range:
CDMA2000 T_RESEL_SF_0DOT25,
1xRTT T_RESEL_SF_0DOT5,
T_RESEL_SF_0DOT75,
T_RESEL_SF_1DOT0
(0.75)
CellResel QHystSfMedium MOD CELLRESEL LBFD-002009 / Broadcast of Meaning: Indicates the scaling factor (or
LST CELLRESEL TDLBFD-002009 system known as additional hysteresis) applied to
LBFD-00201803 / information Qhyst for medium-mobility UEs. For
TDLBFD-00201803 Cell Selection details, see 3GPP TS 36.304 and 3GPP
and Re- TS 36.331.
selection GUI Value Range:
DB_6_Q_HYST_SF_MEDIUM(-6dB),
DB0_Q_HYST_SF_MEDIUM(0dB)
Unit: dB
Actual Value Range:
DB_6_Q_HYST_SF_MEDIUM,
DB0_Q_HYST_SF_MEDIUM
Default Value:
DB0_Q_HYST_SF_MEDIUM(0dB)
CellResel QHystSfHigh MOD CELLRESEL LBFD-002009 / Broadcast of Meaning: Indicates the scaling factor (or
LST CELLRESEL TDLBFD-002009 system known as additional hysteresis) applied to
LBFD-00201803 / information Qhyst for high-mobility UEs. For details,
TDLBFD-00201803 Cell Selection see 3GPP TS 36.304 and 3GPP TS
and Re- 36.331.
selection GUI Value Range:
DB_6_Q_HYST_SF_HIGH(-6dB),
DB0_Q_HYST_SF_HIGH(0dB)
Unit: dB
Actual Value Range:
DB_6_Q_HYST_SF_HIGH,
DB0_Q_HYST_SF_HIGH
Default Value: DB0_Q_HYST_SF_HIGH
(0dB)
CellAccess CellBarred MOD CELLACCESS LOFD-002012 / Cell Outage Meaning: Indicates whether the cell is
LST CELLACCESS TDLOFD-002012 Detection and barred. If the cell is barred, the UE cannot
LBFD-002009 / Compensation camp on the serving cell. During cell
TDLBFD-002009 Broadcast of reselection, the serving cell is not selected
system as a candidate cell.
information GUI Value Range: CELL_BARRED
(Barred), CELL_NOT_BARRED(Not
Barred)
Unit: None
Actual Value Range: CELL_BARRED,
CELL_NOT_BARRED
Default Value: CELL_NOT_BARRED(Not
Barred)
CellOp CellReservedForOp ADD CELLOP LBFD-002009 / Broadcast of Meaning:

MOD CELLOP TDLBFD-002009 system Indicates whether the cell is reserved for
LST CELLOP information operator use.
CELL_RESERVED_FOR_OP, the cell is
reserved for operator use. UEs of AC11 or
AC15 in their HPLMN or EHPLMN can


consider this cell as a candidate cell for
cell selection or reselection. UEs of AC11
or AC15 outside their HPLMN/EHPLMN
and UEs of AC0-9/AC12-14 consider this
cell as a barred cell during cell selection
or reselection.
CELL_NOT_RESERVED_FOR_OP, the
cell is not reserved for operator use. All
UEs can consider this cell as a candidate
cell for cell selection or reselection.
GUI Value Range:
CELL_RESERVED_FOR_OP(Reserved),
CELL_NOT_RESERVED_FOR_OP(Not
Reserved)
Unit: None
Actual Value Range:
CELL_RESERVED_FOR_OP,
CELL_NOT_RESERVED_FOR_OP
Default Value:
CELL_NOT_RESERVED_FOR_OP(Not
Reserved)
CellAccess IntraFreqResel MOD CELLACCESS LBFD-002009 / Broadcast of Meaning:

LST CELLACCESS TDLBFD-002009 system Indicates whether the cell can initiate the
LBFD- information intra-frequency cell reselection when the
00201803/TDLBFD- Cell Selection cell is barred.
00201803 and Re- NOT_ALLOWED means that the UE
selection cannot initiate the intra-frequency cell
reselection, and ALLOWED means that
the UE can initiate the intra-frequency cell
reselection.
GUI Value Range: ALLOWED,
NOT_ALLOWED
Unit: None
Actual Value Range: ALLOWED,
NOT_ALLOWED
Default Value: ALLOWED
BcchCfg ModifyPeriodCoeff MOD BCCHCFG LBFD-002009 / Broadcast of Meaning: Indicates the modification period
LST BCCHCFG TDLBFD-002009 system coefficient for the BCCH. BCCH
information modification period is equal to
Modification period coefficient multiplies
Default paging cycle, where the BCCH
modification period and default paging
cycle are measured in unit of radio
frames, and the modification period
coefficient is specified by this parameter.
GUI Value Range:
MOD_PERIOD_COEFF_N2(2),
MOD_PERIOD_COEFF_N16(16)
Unit: None
Actual Value Range:
MOD_PERIOD_COEFF_N2,
MOD_PERIOD_COEFF_N16
Default Value:
MOD_PERIOD_COEFF_N2(2)
PCCHCfg DefaultPagingCycle MOD PCCHCFG LBFD-002009 / Broadcast of Meaning: Indicates the default paging
LST PCCHCFG TDLBFD-002009 system period for the cell. It is also called the
LBFD-002011 / information discontinuous reception (DRX) period. If
TDLBFD-002011 Paging the EPC specifies a DRX period for a UE,
the UE compares this period with the
value of this parameter and uses the
smaller one as its DRX period. If the EPC
does not specify a DRX period, the UE
uses the value of this parameter, which is
delivered in the system information, as its
DRX period. For details, see 3GPP TS
36.304.
GUI Value Range: rf32(32 radio frames),
rf64(64 radio frames), rf128(128 radio
frames), rf256(256 radio frames)
Unit: None
Actual Value Range: rf32, rf64, rf128,
rf256
Default Value: rf128(128 radio frames)
CellSiMap SibUpdOptSwitch MOD CELLSIMAP LBFD- Broadcast of Meaning:

LST CELLSIMAP 002009/TDLBFD- system Indicates whether to enable the
002009 information optimization scheme switch that controls
SIB message update.
SibPagingOptCtrlSwitch: Indicates
whether to enable the optimization of
paging triggered by system information
update. If this option is selected, the
optimization scheme takes effect, and the


paging cycle is the same as the BCCH
modification period. If this option is
deselected, the optimization scheme does
not take effect, and the paging cycle is
occasionally less than the BCCH
modification period.
GUI Value Range:
SibPagingOptCtrlSwitch
(SibPagingOptCtrlSwitch)
Unit: None
Actual Value Range:
SibPagingOptCtrlSwitch
Default Value:
SibPagingOptCtrlSwitch:Off
PCCHCfg PagingSentNum MOD PCCHCFG LBFD-002011 / Paging Meaning: Indicates the number of paging
LST PCCHCFG TDLBFD-002011 messages transmitted to UEs over the air
interface.
Unit: None
Default Value: 1
GlobalProcSwitch S1DefaultPagingDrxSelect MOD LBFD-002011 / Paging Meaning: Indicates the value of the IE
GLOBALPROCSWITCH TDLBFD-002011 Default paging DRX contained in the S1
LST GLOBALPROCSWITCH SETUP REQUEST and ENB
CONFIGURATION UPDATE messages
that the eNodeB sends over the S1
interface. For details, see 3GPP TS
36.413.
GUI Value Range: v32(v32), v64(v64),
v128(v128), v256(v256)
Unit: None
Actual Value Range: v32, v64, v128, v256
Default Value: v32(v32)
PCCHCfg Nb MOD PCCHCFG LBFD-002009 / Broadcast of Meaning: Indicates the number of paging
LST PCCHCFG TDLBFD-002009 system occasions (a type of subframe) within a
LBFD-002011 / information paging period. This parameter value also
TDLBFD-002011 Paging indicates the number of paging groups
within a paging period. For details, see
3GPP TS 36.304.
GUI Value Range: FOURT, TWOT,
ONET, HALFT, QUARTERT,
ONE_EIGHTT, ONE_SIXTEENTHT,
ONE_THIRTY_SECONDT
Unit: None
Actual Value Range: FOURT, TWOT,
ONET, HALFT, QUARTERT,
ONE_EIGHTT, ONE_SIXTEENTHT,
ONE_THIRTY_SECONDT
Default Value: ONET
CellDlschAlgo RarAndPagingCR MOD CELLDLSCHALGO LBFD- Paging Meaning: Indicates the code rate for
DSP CELLCOVENHSTUS 002011/TDLBFD- Random Random Access Response messages
LST CELLDLSCHALGO 002011 Access and paging messages.
LBFD- Procedure GUI Value Range: 10~930
002010/TDLBFD- Unit: None
002010 Actual Value Range: 0.010~0.930,
step:0.001
Default Value: 117
PCCHCfg MaxPagingRecordsNum MOD PCCHCFG LBFD-002011 / Paging Meaning: Indicates the maximum number
LST PCCHCFG TDLBFD-002011 of UEs that can be included in a paging
message on each paging occasion.
Unit: None
Default Value: 16
PCCHCfg PagingStrategy MOD PCCHCFG TDLBFD- Paging Meaning: Indicates a paging message
LST PCCHCFG 002011/LBFD- sending policy. There are two policies:
002011 first in first out (FIFO) and priority
differentiation. FIFO means that paging
messages that arrive earlier are
preferentially sent in a paging occasion.
Priority differentiation means higher-
priority paging messages are
preferentially sent in a paging occasion.
GUI Value Range:
PAGING_STRATEGY_FIFO(First-in First-
out Strategy),
PAGING_STRATEGY_DIFFPRI(Priority
Differentiation Strategy)
Unit: None
Actual Value Range:
PAGING_STRATEGY_FIFO,
PAGING_STRATEGY_DIFFPRI


Default Value:
PAGING_STRATEGY_FIFO(First-in First-
out Strategy)
CellAlgoSwitch DlSchSwitch MOD CELLALGOSWITCH LOFD-110205 Traffic Model Meaning:

LST CELLALGOSWITCH LOFD-001016 / Based Indicates whether to enable downlink
TDLOFD-001016 Performance scheduling algorithms in a cell. This
LOFD-00101502 / Optimization parameter includes the following options:
TDLOFD-00101502 VoIP Semi- FreqSelSwitch: Indicates whether to
LOFD-001109 / persistent enable frequency-selective scheduling. If
TDLOFD-001109 Scheduling this option is selected, data is transmitted
LOFD-001070 / Dynamic on the frequency band of high channel
TDLOFD-001070 Scheduling quality.
TDLOFD-070224 DL Non-GBR SpsSchSwitch: Indicates whether to
Packet enable semi-persistent scheduling during
LBFD-002025 /
Bundling talk spurts of VoLTE services. If this
TDLBFD-002025
Symbol Power option is selected, semi-persistent
LBFD-002031 / scheduling is applied during talk spurts of
Saving
TDLBFD-002031 VoLTE services. If this option is
Scheduling
LBFD-070102 / deselected, dynamic scheduling is applied
Based on Max
TDLBFD-070102 during talk spurts of VoLTE services.
Bit Rate
LBFD-060202 MBSFNShutDownSwitch: Indicates
Basic
Scheduling whether to enable Multimedia Broadcast
multicast service Single Frequency
Support of
Network (MBSFN) subframe shutdown. If
aperiodic CQI
this option is selected, MBSFN subframe
reports
shutdown is applied. If this option is
MBR>GBR
deselected, MBSFN subframe shutdown
Configuration
is not applied. This option takes effect
Enhanced DL only if the SymbolShutdownSwitch option
Frequency is selected. If the
Selective MBSFNShutDownSwitch option is
selected, 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 MBSFNShutDownSwitch option
is deselected, the setting of the switch for
mapping SIBs to SI messages becomes
valid. The MBSFNShutDownSwitch option
applies only to LTE-only base stations.
NonGbrBundlingSwitch: Indicates whether
to enable downlink non-GBR packet
bundling. If this option is selected, delay
of non-GBR services can be controlled in
non-congestion scenarios. If this option is
deselected, delay of non-GBR services
cannot be controlled.
EnAperiodicCqiRptSwitch: Indicates
whether to enable enhanced aperiodic
channel quality indicator (CQI) reporting.
If this option is selected, 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 option is
deselected, UEs under non-frequency-
selective scheduling do not trigger
aperiodic CQI reporting based on
downlink services and trigger 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
option is selected, the eNodeB performs
downlink scheduling on GBR bearers
based on the MBR and GBR. If this option
is deselected, 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 option is selected,
the eNodeB prioritizes UEs based on the
MBRs during downlink scheduling. This
option applies only to LTE TDD.
UeAmbrDlSchSwitch: Indicates whether
the eNodeB performs downlink scheduling
based on per UE aggregate maximum bit
rates (UE-AMBRs). If this option is
selected, the eNodeB prioritizes UEs
based on the UE-AMBRs during downlink
scheduling. This option applies only to
LTE TDD.
EpfEnhancedSwitch: Indicates whether to
enable the enhanced proportional fair
(EPF) enhancement algorithm for
downlink scheduling. The EPF
enhancement algorithm for downlink


scheduling is enabled only when this
switch is on.
AperiodicCqiTrigOptSwitch: Indicates
whether to optimize triggering of aperiodic
CQI reporting. If this option is selected, a
UE performing initial access triggers
aperiodic CQI reporting based on related
trigger 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 option is
deselected, a UE performing initial access
triggers aperiodic CQI reporting based on
related trigger 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, 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
dynamic scheduling for VoLTE services.
The MCS index is selected based on the
TBS in downlink dynamic scheduling for
VoLTE services only if this option is
selected.
PagingInterfRandSwitch: Indicates
whether to enable interference
randomization for paging messages. If
this option is selected, interference
randomization is enabled for paging
messages.
DlSingleUsrMcsOptSwitch: Indicates
conditions for lowering the MCS index for
a single UE. If this option is selected, the
MCS index can be lowered for a UE if the
UE is the only UE to be scheduled in a
transmission time interval (TTI). If this
option is deselected, the MCS index can
be lowered for a UE if the threshold for
the function of lowering the MCS index to
increase the number of RBs is reached
and the UE is the only UE to be
scheduled in a TTI.
UeSigMcsEnhanceSwitch: Indicates
whether to enable MCS optimization for
UE signaling. If this option is selected,
MCS optimization for UE signaling is
enabled. For LTE FDD, the MCS index for
UE signaling is the same as the MCS
index for data. For LTE TDD, the MCS
index for UE signaling is lowered based
on the MCS index for data. If this option is
deselected, a fixed low MCS index is used
for UE signaling.
SubframeSchDiffSwitch: Indicates
whether to increase the number of UEs
scheduled in subframes 3 and 8 when
uplink-downlink configuration 2 is used. If
this option is selected, the number of UEs
scheduled in subframes 3 and 8 is
increased when uplinkd-downlink
configuration 2 is used. If this option is
deselected, the scheduling policy used in
subframes 3 and 8 is the same as that
used in other downlink subframes when
uplink-downlink configuration 2 is used.
This option applies only to LTE TDD.
TailPackagePriSchSwitch: Indicates
whether to enable scheduling of downlink
connected tail packages in the bearer. If
this option is selected, the connected tail
package is scheduled preferentially in the
next TTI, which reduces the delay and
increases the transmission rate. If this
option is deselected, the scheduling policy
of the connected tail package is the same
as other downlink subframes. This option
applies only to LTE TDD.
SIB1InterfRandSwitch: Indicates whether
to enable SIB1 interference


randomization. If this option is selected,
interference randomization is enabled for
SIB1. This option applies only to LTE
TDD.
FreqSelJudgeIgnorDopplerSwitch:
Indicates whether to ignore Doppler
conditions. If this option is selected,
Doppler conditions are ignored during
frequency selective channel
determination. If this option is deselected,
Doppler conditions are considered during
frequency selective channel
determination. This option applies only to
LTE FDD.
EnhExtQCISpsSchSwitch: Indicates
whether to enable semi-persistent
scheduling during talk spurts of PTT
services with standardized QCI 65,
standardized QCI 66, or an enhanced
extended QCI. If this option is selected,
semi-persistent scheduling is applied. If
this option is deselected, dynamic
scheduling is applied.
DlVoipBundlingSwitch: Indicates whether
to enable active packet bundling for
downlink VoLTE services. Active packet
bundling is enabled for downlink VoLTE
services only if this option is selected. If
this option is selected, PDCCH resources
can be saved for downlink data services
or uplink services, thereby increasing the
VoLTE capacity in VoLTE-only scenarios
or increasing the throughput of data
services in mixed service scenarios.
However, the delay in downlink VoLTE
voice packet scheduling will increase and
MOSs may decrease. You are advised to
deselect this option if you prefer VoLTE
performance and do not expect MOS
reduction.
DlPacketLenAwareSchSw: Indicates
whether to enable packet length
awareness performance optimization in
the downlink. Packet length awareness
performance optimization is enabled in
the downlink only if this option is selected.
RLCArqFeedbackEnhancedSwitch:
Indicates whether to modify the HARQ
feedback results based on the RLC status
reports when subframe configuration 2 is
used. If this option is selected, the
eNodeB modifies the HARQ feedback
results based on the RLC status reports
after receiving the reports. This prevents
unnecessary HARQ retransmissions. This
PaReconfigOptSwitch: Indicates whether
to enable PA reconfiguration optimization.
The optimization is enabled when this
option is selected.RankRapidRptSwitch:
Indicates whether to enable fast rank
reporting. If this option is selected, an
aperiodic CQI reporting is immediately
triggered after successful network access.
If this option is deselected, an aperiodic
CQI reporting is not immediately triggered
after successful network access.
GUI Value Range: FreqSelSwitch
(FreqSelSwitch), 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),
EnhExtQCISpsSchSwitch
(EnhExtQCISpsSchSwitch),
DlVoipBundlingSwitch
(DlVoipBundlingSwitch),
DlPacketLenAwareSchSw
(DlPacketLenAwareSchSw),
RLCArqFeedbackEnhancedSwitch
(RLCArqFeedbackEnhancedSwitch),
PaReconfigOptSwitch
(PaReconfigOptSwitch),
RankRapidRptSwitch
(RankRapidRptSwitch)
Unit: None
Actual Value Range: FreqSelSwitch,
SpsSchSwitch, MBSFNShutDownSwitch,
NonGbrBundlingSwitch,
EnAperiodicCqiRptSwitch,
DlMbrCtrlSwitch, MbrDlSchSwitch,
UeAmbrDlSchSwitch,
EpfEnhancedSwitch,
AperiodicCqiTrigOptSwitch,
VoipTbsBasedMcsSelSwitch,
PagingInterfRandSwitch,
DlSingleUsrMcsOptSwitch,
SubframeSchDiffSwitch,
TailPackagePriSchSwitch,
UeSigMcsEnhanceSwitch,
FreqSelJudgeIgnorDopplerSwitch,
SIB1InterfRandSwitch,
EnhExtQCISpsSchSwitch,
DlVoipBundlingSwitch,
DlPacketLenAwareSchSw,
RLCArqFeedbackEnhancedSwitch,
PaReconfigOptSwitch,
RankRapidRptSwitch
Default Value: FreqSelSwitch:Off,
SpsSchSwitch:Off,
MBSFNShutDownSwitch:Off,
NonGbrBundlingSwitch:Off,
EnAperiodicCqiRptSwitch:Off,
DlMbrCtrlSwitch:Off, MbrDlSchSwitch:Off,
UeAmbrDlSchSwitch:Off,
EpfEnhancedSwitch:Off,
AperiodicCqiTrigOptSwitch:On,
VoipTbsBasedMcsSelSwitch:On,
PagingInterfRandSwitch:Off,
DlSingleUsrMcsOptSwitch:Off,
SubframeSchDiffSwitch:Off,
TailPackagePriSchSwitch:Off,
UeSigMcsEnhanceSwitch:Off,
FreqSelJudgeIgnorDopplerSwitch:Off,
SIB1InterfRandSwitch:On,
EnhExtQCISpsSchSwitch:Off,
DlVoipBundlingSwitch:Off,
DlPacketLenAwareSchSw:Off,
RLCArqFeedbackEnhancedSwitch:Off,
PaReconfigOptSwitch:Off,
RankRapidRptSwitch:Off
CellResel LocalCellId LST CELLRESEL None None Meaning: Indicates the local ID of the cell.
MOD CELLRESEL It uniquely identifies a cell within a BS.
Unit: None
Default Value: None
CellResel PMaxCfgInd MOD CELLRESEL LBFD-00201803 / Cell Selection Meaning: Indicates whether to configure
LST CELLRESEL TDLBFD-00201803 and Re- the maximum TX power of the UE in the
LBFD-002009 / selection intra-frequency neighboring cell. If the
TDLBFD-002009 Broadcast of value of this parameter is not specified,
system the maximum power is subject to the UE
information capability.
Unit: None
EutranInterNFreq LocalCellId ADD EUTRANINTERNFREQ None None Meaning: Indicates the cell ID of the local
LST EUTRANINTERNFREQ cell. It uniquely identifies a cell within an
MOD eNodeB.
EUTRANINTERNFREQ
RMV EUTRANINTERNFREQ
Unit: None
Default Value: None
CellReselPriorityCfgInd ADD EUTRANINTERNFREQ


EutranInterNFreq MOD LBFD-00201803 / Cell Selection Meaning: Indicates whether to set the
EUTRANINTERNFREQ TDLBFD-00201803 and Re- reselection priority of the neighboring
LST EUTRANINTERNFREQ selection E-UTRAN frequency. For details about
how UEs process frequency priorities
during cell reselection, see section 5.2.4.1
of 3GPP TS 36.304 (V12.4.0).
Unit: None
CellReselUtran LocalCellId ADD CELLRESELUTRAN None None Meaning: Indicates the local ID of the cell.
LST CELLRESELUTRAN It uniquely identifies a cell within a BS.
MOD CELLRESELUTRAN GUI Value Range: 0~255
RMV CELLRESELUTRAN
Unit: None
Default Value: None
UtranNFreq LocalCellId ADD UTRANNFREQ None None Meaning: Indicates the cell ID of the local
LST UTRANNFREQ cell. It uniquely identifies a cell within an
MOD UTRANNFREQ eNodeB.
RMV UTRANNFREQ GUI Value Range: 0~255
Unit: None
Default Value: None
UtranNFreq CellReselPriorityCfgInd ADD UTRANNFREQ LBFD-00201803 / Cell Selection Meaning: Indicates whether to set the
MOD UTRANNFREQ TDLBFD-00201803 and priority of a cell assigned with the
LST UTRANNFREQ Reselection / UARFCN used in cell reselection to
Cell Selection UTRAN. For details about how UEs
and Re- process frequency priorities during cell
selection reselection, see section 5.2.4.1 of 3GPP
TS 36.304 (V12.4.0).
Unit: None
CellReselGeran LocalCellId ADD CELLRESELGERAN None None Meaning: Indicates the local ID of the cell.
LST CELLRESELGERAN It uniquely identifies a cell within a BS.
MOD CELLRESELGERAN GUI Value Range: 0~255
RMV CELLRESELGERAN
Unit: None
Default Value: None
GeranNfreqGroup LocalCellId ADD GERANNFREQGROUP None None Meaning: Indicates the cell ID of the local
LST GERANNFREQGROUP cell. It uniquely identifies a cell within an
MOD eNodeB.
GERANNFREQGROUP
RMV
GERANNFREQGROUP Unit: None
Default Value: None
GeranNfreqGroup BcchGroupId ADD GERANNFREQGROUP LBFD-00201803 / Cell Selection Meaning: Indicates a GERAN carrier
LST GERANNFREQGROUP TDLBFD-00201803 and Re- frequency group. In the cell reselection
MOD LOFD-001020 / selection procedure, the GERAN carrier
GERANNFREQGROUP frequencies are organized in groups and
TDLOFD-001020 PS Inter-RAT
RMV the cell reselection parameters are
GERANNFREQGROUP Mobility
between provided per group of GERAN carrier
E-UTRAN and frequencies.
GERAN GUI Value Range: 0~31
Unit: None
Default Value: None
GeranNfreqGroup CellReselPriorityCfgInd ADD GERANNFREQGROUP LBFD-00201803 / Cell Selection Meaning: Indicates whether to set the
MOD TDLBFD-00201803 and reselection priority of the frequencies in
GERANNFREQGROUP Reselection / the GERAN carrier frequency group. For
LST GERANNFREQGROUP Cell Selection details about how UEs process frequency
and Re- priorities during cell reselection, see
selection section 5.2.4.1 of 3GPP TS 36.304
(V12.4.0).
Unit: None
CellReselCdma2000 LocalCellId ADD None None Meaning: Indicates the local ID of the cell.
CELLRESELCDMA2000 It uniquely identifies a cell within a BS.
MOD
CELLRESELCDMA2000 Unit: None
RMV Actual Value Range: 0~255
CELLRESELCDMA2000
Default Value: None
CellReselCdma2000 SysTimeCfgInd ADD LBFD-00201803 /

CELLRESELCDMA2000 TDLBFD-00201803


MOD LOFD-001035 / Cell Selection Meaning: Indicates whether to configure
CELLRESELCDMA2000 TDLOFD-001035 and Re- the CDMA2000 system time information.
LST CELLRESELCDMA2000 selection For details, see 3GPP TS 36.331.
LBFD-002009 /
TDLBFD-002009 CS Fallback to GUI Value Range: NOT_CFG(Not
TDLOFD-001090 CDMA2000 configure), CFG(Configure)
1xRTT Unit: None
Broadcast of Actual Value Range: NOT_CFG, CFG
system Default Value: NOT_CFG(Not configure)
information
Enhanced CS
Fallback to
CDMA2000
1xRTT
TASM CLKSYNCMODE SET CLKSYNCMODE MRFD-210501 BTS Clock Meaning: Indicates the clock
DSP CLKSTAT MRFD-211601 Multi-mode BS synchronization mode of a BS, which can
LST CLKSYNCMODE Common be frequency synchronization or time
LBFD-003005
Reference synchronization.
LBFD-00300501
Clock(GBTS) GUI Value Range: FREQ(FREQ), TIME
LBFD-00300503
Synchronization (TIME)
LBFD-00300504
Clock Source Unit: None
LBFD-00300505
Switching Actual Value Range: FREQ, TIME
LBFD-00300506 Manually or Default Value: FREQ(FREQ)
LOFD-003013 Automatically
LOFD-00301301 Synchronization
LOFD-00301302 with GPS
LOFD-00301303 Synchronization
LOFD-003023 with BITS
Synchronization
with 1PPS
Synchronization
with E1/T1
Enhanced
Synchronization
Synchronization
with Ethernet
(ITU-T G.8261)
IEEE1588 V2
Clock
Synchronization
Clock over IP
(Huawei
proprietary)
IEEE 1588v2
over IPv6
CellReselCdma2000 HrpdParaCfgInd ADD LBFD-00201803 / Cell Selection Meaning: Indicates whether the eNodeB
CELLRESELCDMA2000 TDLBFD-00201803 and Re- contains the information about
MOD selection CDMA2000 HRPD in SIB8. If this
TDLOFD-001021 PS Inter-RAT parameter is set to CFG, the eNodeB
LBFD-002009 / Mobility contains the parametersHRPD field in
TDLBFD-002009 between SIB8. If this parameter is set to
E-UTRAN and NOT_CFG, the eNodeB does not contain
CDMA2000 the parametersHRPD field in SIB8. For
Broadcast of details, see 3GPP TS 36.331.
system GUI Value Range: NOT_CFG(Not
information configure), CFG(Configure)
Unit: None
CellReselCdma2000 HrpdCellReselectParamCfgInd ADD LBFD-00201803 / Cell Selection Meaning: Indicates whether to set the
CELLRESELCDMA2000 TDLBFD-00201803 and Re- parameters related to cell reselection to
MOD selection CDMA2000 HRPD.
LST CELLRESELCDMA2000 TDLOFD-001021 PS Inter-RAT GUI Value Range: NOT_CFG(Not
LBFD-002009 / Mobility configure), CFG(Configure)
TDLBFD-002009 between Unit: None
E-UTRAN and Actual Value Range: NOT_CFG, CFG
CDMA2000
Broadcast of
system
information
CellReselCdma2000 Cdma1XrttParaCfgInd ADD LBFD-00201803 / Cell Selection Meaning: Indicates whether the eNodeB
CELLRESELCDMA2000 TDLBFD-00201803 and Re- contains the information about
MOD selection CDMA2000 1xRTT in SIB8. If this
LOFD-001035 CS Fallback to parameter is set to CFG, the eNodeB
LBFD-002009 / CDMA2000 contains the parameters1xRTT field in
TDLBFD-002009 1xRTT SIB8. If this parameter is set to
Broadcast of NOT_CFG, the eNodeB does not contain
TDLOFD-001090
system the parameters1xRTT field in SIB8. For
Enhanced CS GUI Value Range: NOT_CFG(Not
Fallback to configure), CFG(Configure)
CDMA2000 Unit: None
1xRTT Actual Value Range: NOT_CFG, CFG
CellReselCdma2000 Cdma1XrttCellReselCfgInd ADD LBFD-00201803 / Cell Selection Meaning: Indicates whether the
CELLRESELCDMA2000 TDLBFD-00201803 and Re- parameters applicable only for cell
selection


MOD LOFD-001035 / CS Fallback to reselection to CDMA2000 1xRTT need to
CELLRESELCDMA2000 TDLOFD-001035 CDMA2000 be set.
LST CELLRESELCDMA2000 1xRTT
LBFD-002009 / GUI Value Range: NOT_CFG(Not
TDLBFD-002009 Broadcast of configure), CFG(Configure)
TDLOFD-001090 system Unit: None
information Actual Value Range: NOT_CFG, CFG
Enhanced CS Default Value: NOT_CFG(Not configure)
Fallback to
CDMA2000
1xRTT
Cdma2000BandClass LocalCellId ADD None None Meaning: Indicates the cell ID of the local
CDMA2000BANDCLASS cell. It uniquely identifies a cell within an
LST eNodeB.
CDMA2000BANDCLASS
MOD GUI Value Range: 0~255
CDMA2000BANDCLASS Unit: None
RMV Actual Value Range: 0~255
CDMA2000BANDCLASS
Default Value: None
Cdma2000BandClass BandClass ADD LBFD-00201803 / Cell Selection Meaning: Indicates the neighboring
CDMA2000BANDCLASS TDLBFD-00201803 and Re- CDMA2000 band class. Signals on a
LST selection frequency within the band class can be
TDLOFD-001035 CS Fallback to obtained by UEs. For details, see the
MOD
CDMA2000BANDCLASS TDLOFD-001090 CDMA2000 BandclassCDMA2000 IE defined in 3GPP
RMV 1xRTT 36.331.
CDMA2000BANDCLASS Enhanced CS GUI Value Range: bc0, bc1, bc2, bc3,
Fallback to bc4, bc5, bc6, bc7, bc8, bc9, bc10, bc11,
CDMA2000 bc12, bc13, bc14, bc15, bc16, bc17,
1xRTT bc18, bc19, bc20, bc21
Unit: None
Actual Value Range: bc0, bc1, bc2, bc3,
bc4, bc5, bc6, bc7, bc8, bc9, bc10, bc11,
bc12, bc13, bc14, bc15, bc16, bc17,
bc18, bc19, bc20, bc21
Default Value: None
Cdma2000BandClass Cdma20001XrttCellReselInd ADD LBFD-00201803 / Cell Selection Meaning: Indicates whether to configure
CDMA2000BANDCLASS TDLBFD-00201803 and Re- cell reselection priorities for CDMA2000
MOD selection 1xRTT band class. If this parameter is set
TDLOFD-001035 CS Fallback to to NOT_CFG, the cell reselection
LST
CDMA2000BANDCLASS TDLOFD-001090 CDMA2000 priorities are not delivered in the system
1xRTT information.
Enhanced CS GUI Value Range: NOT_CFG(Not
Fallback to configure), CFG(Configure)
CDMA2000 Unit: None
1xRTT Actual Value Range: NOT_CFG, CFG
Cdma2000BandClass Cdma2000HrpdCellReselInd ADD LBFD-00201803 / Cell Selection Meaning: Indicates whether to configure
CDMA2000BANDCLASS TDLBFD-00201803 and Re- cell reselection priorities for CDMA2000
MOD selection HRPD band class. If this parameter is set
TDLOFD-001021 PS Inter-RAT to NOT_CFG, the cell reselection
LST
CDMA2000BANDCLASS Mobility priorities are not delivered in the system
between information.
E-UTRAN and GUI Value Range: NOT_CFG(Not
CDMA2000 configure), CFG(Configure)
Unit: None
8 Counters
Table 8-1 Counters
1526726884 L.Paging.S1.Rx Number of received paging Multi-mode: None Paging

messages over the S1 GSM: None Paging
interface in a cell UMTS: None
LTE: LBFD-002011
TDLBFD-002011
1526726885 L.Paging.UU.Att Number of UEs contained in Multi-mode: None Paging

paging messages transmitted GSM: None Paging
over the Uu interface in a cell UMTS: None Dynamic DRX
LTE: LBFD-002011
TDLBFD-002011
LOFD-00110501
1526726886 L.Paging.UU.Succ Number of Successful Paging Multi-mode: None Paging

Responses from the UE in a GSM: None Paging
Cell UMTS: None
LTE: LBFD-002011
TDLBFD-002011

1526727212 L.Paging.Dis.Num Number of discarded paging Multi-mode: None Paging

messages from the MME to GSM: None Paging
UEs UMTS: None
LTE: LBFD-002011
TDLBFD-002011
1526728337 L.Paging.UU.SIUpdate Number of paging messages Multi-mode: None Paging

transmitted due to system GSM: None Paging
information changes UMTS: None
LTE: LBFD-002011
TDLBFD-002011
1526728521 L.Paging.Dis.PchCong Number of paging messages Multi-mode: None Paging

discarded due to paging GSM: None Paging
channel congestion UMTS: None
LTE: LBFD-002011
TDLBFD-002011
1526729280 L.Signal.Num.SIB1.ETWS Times of ETWS-induced SIB1 Multi-mode: None Earthquake and Tsunami
changes GSM: None Warning System (ETWS)
UMTS: None Earthquake and Tsunami
LTE: LBFD-002029 Warning System(ETWS)
TDLBFD-002029 Broadcast of system
information
LBFD-002009
Broadcast of system
TDLBFD-002009
information
1526729665 L.Paging.S1.Rx.PLMN Number of received paging Multi-mode: None Paging

messages over the S1 GSM: None Paging
interface for a specific UMTS: None RAN Sharing with Common
operator in a cell Carrier
LTE: LBFD-002011
TDLBFD-002011 RAN Sharing with Common
TDLOFD-001036 Carrier
LOFD-001036 RAN Sharing with Dedicated
Carrier
LOFD-001037
RAN Sharing with Dedicated
TDLOFD-001037
Carrier
LOFD-070206
Hybrid RAN Sharing
1526730140 L.Paging.UU.Succ.CSFB Number of paging responses Multi-mode: None Paging

for CSFB received from UEs GSM: None Paging
in a cell UMTS: None CS Fallback to UTRAN
LTE: LBFD-002011 CS Fallback to UTRAN
TDLBFD-002011 CS Fallback to GERAN
LOFD-001033 CS Fallback to GERAN
TDLOFD-001033 CS Fallback to CDMA2000
LOFD-001034 1xRTT
LOFD-001035 1xRTT
TDLOFD-001035
1526730145 L.Paging.S1.Rx.CS Number of received paging Multi-mode: None Paging

messages with the IE CN GSM: None Paging
DOMAIN set to CS over the UMTS: None CS Fallback to UTRAN
S1 interface in a cell
LTE: LBFD-002011 CS Fallback to UTRAN
TDLBFD-002011 CS Fallback to GERAN
LOFD-001033 CS Fallback to GERAN
LOFD-001034 1xRTT
LOFD-001035 1xRTT
TDLOFD-001035
1526730562 L.Paging.UU.Num Number of paging messages Multi-mode: None Paging

sent over the Uu interface in a GSM: None Paging
cell UMTS: None
LTE: LBFD-002011
TDLBFD-002011
9 Glossary

This chapter lists the reference documents related to idle mode management:
1. 3GPP TS 36.331, "RRC Protocol Specification"

2. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access"
3. 3GPP TS 36.101, "User Equipment (UE) radio transmission and reception"
4. 3GPP TS 22.011, "Service accessibility"
5. 3GPP TS 23.122, "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode"
6. 3GPP TS 36.304, "User Equipment (UE) procedures in idle mode"
7. 3GPP TS 36.300, "E-UTRAN Overall description"
8. Flexible User Steering Feature Parameter Description
9. Carrier Aggregation Feature Parameter Description
10. Access Class Control Feature Parameter Description
11. Scheduling Feature Parameter Description
eRAN
Multiple Frequency Band Indicator Feature Parameter Description
Issue 03
Date 2017-01-15

Notice


4 Contents
1.1 Scope
1.3 Change History
2 Overview
2.1 Background
2.2 Introduction
2.3 Benefits
3.1 Overview
3.2 Cell Selection
3.3 Cell Reselection
3.4 Handover
3.4.1 Delivery of Frequencies to Measure
3.4.2 Handover Decision
3.5 ANR
3.6 PCI Conflict Detection
3.7 CA
3.8 eMBMS
4 Related Features
5 Network Impact
6.1 When to Use
6.3 Planning
6.3.1 RF Planning
6.3.2 Network Planning
6.3.3 Hardware Planning
6.4 Deployment
6.4.1 Requirements
6.4.2 Precautions
6.7 Possible Issues
7 Parameters
8 Counters
9 Glossary
Scope
This document describes the multiple frequency band indicator (MFBI) feature (that is, LBFD-070103 Multi-Band Compatibility Enhancement), including its technical principles,
related features, network impact, and engineering guidelines.
eNodeB Type Model
Micro BTS3202E
BTS3203E
BTS3911E
BTS3912E
Intended Audience


Change History
• Feature change
AN11.1 03 (2017-01-15)
Feature change None None None
Editorial change Added impacted features. For details, see Impacted Features in None N/A
4 Related Features.
AN11.1 02 (2016-11-01)
Editorial change Revised the descriptions of "Configuring Neighboring None N/A

Frequencies" in 6.4.4.3 Using MML Commands.
AN11.1 01 (2016-03-07)
AN11.1 Draft A (2015-12-30)
Editorial change Revised descriptions in this document. None N/A

The feature described in this document is implemented in the same way on macro, micro, and LampSite eNodeBs.
2 Overview
Background
Table 2-1 lists the E-UTRAN operating bands defined in 3GPP TS 36.101.
Table 2-1 E-UTRAN operating bands
E-UTRAN Operating Band Uplink Operating Band Downlink Operating Band Duplex Mode
(FUL_low–FUL_high MHz) (FDL_low–FDL_high MHz)
2 1850–1910 1930–1990 FDD
3 1710–1785 1805–1880 FDD
4 1710–1755 2110–2155 FDD
5 824–849 869–894 FDD

1 830–840 875–885 FDD
6
7 2500–2570 2620–2690 FDD
8 880–915 925–960 FDD
9 1749.9–1784.9 1844.9–1879.9 FDD
10 1710–1770 2110–2170 FDD
11 1427.9–1447.9 1475.9–1495.9 FDD
12 699–716 729–746 FDD
13 777–787 746–756 FDD
14 788–798 758–768 FDD
15 Reserved Reserved FDD
16 Reserved Reserved FDD
17 704–716 734–746 FDD
18 815–830 860–875 FDD

E-UTRAN Operating Band Uplink Operating Band Downlink Operating Band Duplex Mode
(FUL_low–FUL_high MHz) (FDL_low–FDL_high MHz)
19 830–845 875–890 FDD
20 832–862 791–821 FDD
21 1447.9–1462.9 1495.9–1510.9 FDD
22 3410–3490 3510–3590 FDD
23 2000–2020 2180–2200 FDD
24 1626.5–1660.5 1525–1559 FDD
25 1850–1915 1930–1995 FDD
26 814–849 859–894 FDD
33 1900–1920 1900–1920 TDD
34 2010–2025 2010–2025 TDD
35 1850–1910 1850–1910 TDD
36 1930–1990 1930–1990 TDD
37 1910–1930 1910–1930 TDD
38 2570–2620 2570–2620 TDD
39 1880–1920 1880–1920 TDD
40 2300–2400 2300–2400 TDD
41 2496–2690 2496–2690 TDD
42 3400–3600 3400–3600 TDD
43 3600–3800 3600–3800 TDD
NOTE:
Band 6 is not applicable.
The table shows that particular carrier frequencies may be used by different frequency bands. For example, the carrier frequencies of the uplink range 704–716 MHz and
downlink range 734–746 MHz are used by both bands 12 and 17.
To identify whether a cell supports multiple frequency bands, 3GPP introduces MFBI-related fields to system information blocks (SIBs).
Introduction
An information element (IE) has been added to certain SIBs for MFBI. The IE indicates whether a cell operates in multiple frequency bands and, if so, the primary and secondary
frequency bands. The function of this IE varies depending on the SIB type:
• The IE in SIB1 and SIB2 is used for multi-band cell selection.

• The IE in SIB5 and SIB6 is used for multi-band cell reselection.
Benefits
MFBI allows more UEs to access or be transferred to a multi-band cell. The specific benefits are as follows:
• If a cell operates in multiple frequency bands and SIBs in the cell contain the MFBI-related fields, UEs that support any of these bands can access the cell.
• If a neighboring cell operates in multiple frequency bands, the cell can be the target for cell reselection, handover measurements, and handovers of UEs that support
any of these bands.
For example, if a cell with a 10 MHz bandwidth in band 17 is configured to operate in both bands 12 and 17, both UEs supporting band 12 and UEs supporting band 17 can
access or be transferred to the cell.
This chapter describes MFBI handling in procedures such as cell selection, cell reselection, and handovers.
Overview
Figure 3-1 illustrates an example of a multi-band cell. In this example, cell 1 operates in both bands 12 and 17.
Figure 3-1 Example of a multi-band cell
If the primary frequency band is band 17, both UEs supporting band 17 and MFBI-capable UEs supporting band 12 can receive services from cell 1. When a carrier frequency
(denoted by fc) is included in both bands 12 and 17, it is assigned different E-UTRA absolute radio frequency channel numbers (EARFCNs), that is, EARFCN 1 and EARFCN 2
in the two bands.

NOTE:
If the feature group indicator (FGI) 31 in the RRC_UE_CAP_INFO message of a UE is set to 1, it indicates that the UE supports MFBI.
This chapter describes the following features and functions that are impacted by MFBI:
• Cell selection
• Cell reselection
• Handover
• ANR
• Physical cell identifier (PCI) conflict detection
• Carrier aggregation (CA)
• eMBMS
The impacts of the feature are based on the following assumptions:
• The primary EARFCNs of MFBI cells with the same frequency on the entire network must be consistent. The primary EARFCN of an MFBI cell must be consistent
with the EARFCN of a non-MFBI cell with the same frequency.
• The primary and secondary EARFCNs of an MFBI cell must be consistent with those of its external cells.
• In frequency configuration, the attribute parameters related to the primary and secondary EARFCNs must be set consistently. For details about the involved
parameters, see 6.4 Deployment.
Cell Selection
UEs can camp on multi-band cells.
A multi-band cell can operate in one primary frequency band and a maximum of two secondary frequency bands. The bands are defined as follows:
• Primary frequency band

The primary frequency band has the highest priority. This band is specified by the Cell.FreqBand parameter. The parameter setting is contained in the IE
freqBandIndicator in SIB1.
• Secondary frequency band
The secondary frequency band has a lower priority than the primary frequency band. This band is specified by the Cell.CellSlaveBand parameter. The parameter
settings are contained in the IE multiBandInfoList in SIB1.
• Priority adjustment for the secondary frequency band
After being adjusted, the priority of a secondary frequency band can be higher than that of the primary frequency band. The CellAlgoSwitch.MfbiAlgoSwitch
parameter controls whether priority adjustment is allowed. After priority adjustment is allowed, the IE freqBandIndicatorPriority-r12 is carried in SIB1.
During cell selection, the UE monitors SIB1 and SIB2 in a cell. If the UE supports the frequency band indicated by the IE freqBandIndicator or multiBandInfoList, the UE selects
a frequency band with the highest priority and continues the subsequent cell selection procedure. If the UE does not support any of the indicated frequency bands, the UE does
not select the cell.
If the UE finds that SIB1 carries the IE freqBandIndicatorPriority-r12=TRUE and that the UE capability report message UECapabilityInformation carries the IE
freqBandPriorityAdjustment-r12=Supported, the UE selects a secondary frequency band with the highest priority from MultiBandInfoList to use.
For details about the subsequent cell selection procedure, see Idle Mode Management Feature Parameter Description. For details about SIB1 and SIB2, see sections 6.2.2 "Message
definitions" and 6.3.1 "System information blocks", respectively, in 3GPP TS 36.331 V10.6.0.
Cell Reselection
verview
A UE can perform cell reselection to a multi-band E-UTRAN or UTRAN cell.

During cell reselection, the UE measures the neighboring frequencies indicated in system information in the serving cell. If a neighboring cell is a multi-band cell, the system
information about the neighboring frequencies contains a primary-band-specific EARFCN and a secondary frequency band list.
Information about neighboring E-UTRAN frequencies is contained in SIB5. The IEs InterFreqCarrierFreqInfo and multiBandInfoList in SIB5 indicate the primary-band-specific
EARFCN and the band list, respectively. If the UE supports an indicated frequency band, it continues the subsequent cell reselection procedure.
Information about neighboring UTRAN frequencies is contained in SIB6. The IEs carrierFreqListUTRA-FDD and multiBandInfoList in SIB6 indicate the primary-band-specific
UARFCN and the band list, respectively. If the UE supports an indicated frequency band, it continues the subsequent cell reselection procedure.
For details about the subsequent cell reselection procedure, see Idle Mode Management Feature Parameter Description. For details about SIB5 and SIB6, see section 6.3.1 "System
information blocks" in 3GPP TS 36.331 V10.6.0. This section describes neighboring frequency delivery in cell reselection.
livery of Neighboring E-UTRAN Frequencies
The neighboring E-UTRAN ARFCN is specified by the EutranInterNFreq.DlEarfcn parameter. The primary- and secondary-band-specific EARFCNs of the neighboring
frequency are specified as follows:
• Primary-band-specific EARFCN:
If the EutranInterNFreq.MasterBandFlag parameter of a frequency band is set to TRUE, this band is the primary frequency band. A single neighboring E-UTRAN cell
can have only one primary-band-specific EARFCN. When the parameter of all EARFCNs is set to FALSE, the eNodeB regards the EARFCN with the minimum band
number as the primary-band-specific EARFCN.
• Secondary-band-specific EARFCN:
It is another EARFCN that has the same frequency as the primary-band-specific EARFCN.
The cell reselection parameters carried by SIB5 are the same as those used for configuring the primary-band-specific EARFCN.
livery of Neighboring UTRAN Frequencies
The neighboring UTRAN ARFCN is specified by the UtranNFreq.UtranDlArfcn parameter. The primary- and secondary-band-specific UARFCNs of the neighboring frequency
are specified as follows:
• Primary-band-specific UARFCN:
The primary-band-specific UARFCN is specified by the UtranNFreq.MasterBandFlag parameter. One neighboring UTRAN frequency can have only one primary-
band-specific UARFCN. When the parameter of all UARFCNs is set to FALSE, the eNodeB regards the UARFCN with the minimum band number as the primary-
band-specific UARFCN.
• Secondary-band-specific EARFCN:
It is another UARFCN that has the same frequency as the primary-band-specific UARFCN.
The cell reselection parameters carried by SIB6 are the same as those used for configuring the primary-band-specific UARFCN.
Handover
A UE can be handed over to a neighboring multi-band E-UTRAN or UTRAN cell.
If the neighboring cell operates in multiple frequency bands, the serving eNodeB delivers the frequency information about the neighboring cell to the UE.
eNodeBs perform special treatment on multi-band cells when delivering frequencies to measure and evaluating handovers. For details about handovers, see Intra-RAT Mobility
Management in Connected Mode Feature Parameter Description and Inter-RAT Mobility Management in Connected Mode Feature Parameter Description.

3.4.1 Delivery of Frequencies to Measure

Before delivering measurement configurations to a UE, an eNodeB selects the frequency information that is specific to the bands supported by the UE and the current EARFCN
used for data transmission. For example, if a candidate neighboring cell for handover supports both band 12 and band 17 and takes band 17 as the primary band:
• The eNodeB delivers the frequency information specific to band 12 to a UE that supports only band 12.
• The eNodeB delivers the frequency information specific to band 17 to a UE that supports only band 17.
• For a UE that supports bands 12 and 17:
◾ If some EARFCNs used for data transmission are available in band 12 or 17 or some EARFCNs in band 12 or 17 have been delivered, the eNodeB
selects these EARFCNs for measurement.
◾ Otherwise, the eNodeB selects the primary EARFCN for measurement. For details about how to select the primary EARFCN, see 3.3 Cell Reselection.
NOTE:
The RsvdSwPara3_bit2 option in the eNBRsvdPara.RsvdSwPara3 parameter must be selected to implement the delivery of measurement configurations.
If the SIB1 delivered to UEs in the serving cell carries the IE freqBandIndicatorPriority-r12=TRUE and the capability information UECapabilityInformation of a UE supporting
bands 12 and 17 carries the IE freqBandPriorityAdjustment-r12=Supported, the serving cell selects the EARFCN specific to the secondary frequency band 17 and delivers it to
the UE for intra-frequency measurement.
3.4.2 Handover Decision

In the handover decision phase, the source eNodeB evaluates the candidate cells reported by the UE.
In the case of an inter-eNodeB or inter-RAT handover, the source eNodeB determines that the UE can be handed over to the target cell only if the target cell supports the target
EARFCN or UARFCN according to the external-cell information. The affected parameters vary depending on the RAT:
• For an external E-UTRAN cell

The EutranExternalCell.DlEarfcn parameter specifies the primary-band-specific EARFCN, and the EutranExternalCell.EutranExternalCellSlaveBand parameter
specifies the secondary frequency bands.
If the operating frequency calculated based on the EARFCN of the neighboring cell is the same as that of the serving cell, then the serving and neighboring cells are
considered to be intra-frequency cells. The cells are considered as inter-frequency cells if the operating frequencies are different.
If the capability information UECapabilityInformation of a UE carries the IE freqBandPriorityAdjustment-r12=Supported, the source cell selects the S1-based
handover procedure for the UE.
• For an external UTRAN cell
The UtranExternalCell.UtranDlArfcn parameter specifies the primary-band-specific UARFCN, and the Utranexternalcell.UtranExternalCellSlaveBand parameter
specifies the secondary frequency bands.
In the case of an intra-eNodeB handover, the eNodeB determines that the UE can be handed over to the target cell only if the target cell supports the target EARFCN. The
primary-band-specific EARFCN is specified by the Cell.DlEarfcn parameter and the secondary band is specified by the Cell.CellSlaveBand parameter.
If the SIB1 message in the target cell of an intra-eNodeB handover carries the IE freqBandIndicatorPriority-r12=TRUE and the capability information UECapabilityInformation of
a UE carries the IE freqBandPriorityAdjustment-r12=Supported, the source cell selects the EARFCN specific to the secondary frequency band of the target cell to calculate
KeNB* for the UE.
The target eNodeB in a handover checks whether the target cell supports the target EARFCN. It rejects the handover request if the target cell does not support the EARFCN.
If the SIB1 message in the target cell carries the IE freqBandIndicatorPriority-r12=TRUE and the capability information UECapabilityInformation of a UE that is handed over from
the same eNodeB or based on the S1 interface carries the IE freqBandPriorityAdjustment-r12=Supported, the target cell selects the EARFCN specific to a secondary frequency
band and delivers it to the UE as the target EARFCN.
If the SIB1 in the target cell carries the IE freqBandIndicatorPriority-r12=TRUE and the capability information UECapabilityInformation of a UE that is handed over based on the
X2 interface carries the IE freqBandPriorityAdjustment-r12=Supported, the target cell selects the EARFCN specific to the primary frequency band and delivers it to the UE as the
target EARFCN.
ANR
A new neighboring cell is detected when a cell reported by the UE has a different CGI from those cells in the neighboring cell list (NCL). When the eNodeB detects a missing
neighboring E-UTRAN cell through intra-RAT ANR or detects a neighboring UTRAN cell through inter-RAT ANR, the primary and secondary bands of the cell can be added as
follows:
• If an intra-frequency neighboring cell is added, the eNodeB generates the primary and secondary bands of an external cell by referring to the primary and secondary
bands of the serving cell.
• If an inter-frequency neighboring cell is added, the eNodeB generates the primary and secondary bands of an external cell by referring to the primary and secondary
bands of the inter-frequency EARFCN.
• If the UE reports a cell that has an identical cell global identification (CGI) with but a different EARFCN or UARFCN than a cell in a neighboring cell list (NCL), the
eNodeB adds the secondary band information about the reported cell to the NCL.
The eNodeB does not allow the ENB CONFIGURATION UPDATE message to carry the IE multiBandInfoList. That is, the eNodeB does not allow the "NCL/NRT self-
management based on X2 messages" function to add or update the secondary band information about external cells.
The eNodeB does not allow using the CME's function of associating the serving cell with neighboring cells to modify the primary and secondary bands of a neighboring cell. If
the function is used, the eNodeB will not add or update the secondary band information about the neighboring cell.
For details about ANR, see ANR Management Feature Parameter Description.
PCI Conflict Detection

The PCI conflict evaluation criteria vary depending on the multi-band capabilities of cells:
• Among multi-band cells

The eNodeB determines that a PCI conflict occurs if cells have the same PCI and operating frequency.
• Among single-band cells
The eNodeB determines that a PCI conflict occurs if cells have the same PCI and operating frequency.
For details about how eNodeBs detect PCI conflicts, see PCI Conflict Detection and Self-Optimization Feature Parameter Description.
CA
When evaluating whether to perform CA, the eNodeB considers the CA band capability of the UE and the operating bands of the cells to be carrier-aggregated. The CA
evaluation criteria vary depending on the multi-band capabilities of the cells:
• When a cell operates in multiple frequency bands, CA is applicable if the CA band capability of the UE overlaps any operating band of the cell.
• When a cell operates in only one frequency band, CA is applicable if the CA band capability of the UE overlaps the operating band of the cell.
For details about CA, see Carrier Aggregation Feature Parameter Description.
NOTE:
When measurement conflict occurs, that is, when the eNodeB has delivered the measurement of an EARFCN but other EARFCNs using the same frequency as the EARFCN
are the expected target EARFCNs for CA, CA cannot use the EARFCNs.
eMBMS
The eMBMS feature does not allow SIB15 to carry the IE multiBandInfoList. When the eMBMS feature is activated in a cell supporting multiple bands, UEs that support only
secondary bands in other inter-frequency cells cannot carry the EARFCN in the IE MBMSInterestIndication. For details about eMBMS, see eMBMS Feature Parameter Description.

4 Related Features
erequisite Features
Feature ID Feature Name Dependency
LBFD-002009 Broadcast of System Information None
None
pacted Features
LBFD-00201805 Service Based Inter-frequency Handover The configurations of the primary and secondary
frequencies must be consistent among the following MOs.
LOFD-001112 MOCN Flexible Priority Based Camping This ensures that the listed features apply only to UEs that
support secondary operating bands.
• EUTRANINTERNFREQ
LOFD-001054 Flexible User Steering
• SERVICEIFDLEARFCNGRP
• QCIEUTRANRELATION
LAOFD-001001 LTE-A Introduction
• EUTRANNFREQSCELLOP
• RATFREQPRIORITYGROUP
LBFD-002018 Mobility Management
• EUTRANNFREQRANSHARE
• INTERFREQBLKCELL
LOFD-001032 Intra-LTE Load Balancing
• PCCFREQCFG
• SCCFREQCFG
LOFD-070215 Intra-LTE User Number Load Balancing • EUTRANSPEPCICELL
5 Network Impact
stem Capacity
No impact.
twork Performance
The number of accessed UEs in multi-band cells increases.
When to Use
Use MFBI when the uplink and downlink operating frequencies of a cell are included in multiple frequency bands. For example, if a cell operates at 704–716 MHz in the uplink
and 734–746 MHz in the downlink, then the operating frequencies are included in both bands 12 and 17. For details, see Table 2-1. MFBI can be used in this cell. However, if a
cell operates at 699–716 MHz in the uplink and 729–746 MHz in the downlink, the operating frequencies are included only in band 12. MFBI cannot be used in this cell.
Collect the frequency bands and bandwidths to be used.
Planning
6.3.1 RF Planning
• For existing networks, set the existing frequency band as the primary frequency band and additional frequency bands as secondary frequency bands. For new
networks, it is recommended that the frequency band supported by most UEs be set as the primary frequency band.
• Ensure consistent settings of primary and secondary frequency bands between multi-band cells that operate in the same frequency range throughout the entire
network.
6.3.2 Network Planning

N/A
6.3.3 Hardware Planning

N/A
Deployment
6.4.1 Requirements
rdware
None
cense
None

hers
UEs must be capable of interpreting MFBI-related fields.
6.4.2 Precautions
It is recommended that MFBI be deployed throughout the entire network. Otherwise, the following problem may occur:
On an eNodeB, an external cell is manually configured as a multi-band cell. However, on the serving eNodeB of the cell, the cell is not configured to support multiple bands. If a
UE that supports a secondary frequency band of the external cell initiates a handover to the cell, handover preparation fails.
The primary-band-specific EARFCN specified by the EUTRANEXTERNALCELL.DlEarfcn parameter and the secondary band specified by the
EUTRANEXTERNALCELLBAND.FreqBand parameter must be set based on the actual configurations of the external cell.
If a frequency has more than one EARFCN and one of the EARFCNs is configured in a Cell MO, EutranInterNFreq MOs that contain the other EARFCNs cannot be configured
under the Cell MO.
If the function of adjusting the priority of a secondary frequency band needs to be enabled, the CellAlgoSwitch.MfbiAlgoSwitch parameter must be set to
MFBIBandAdjAlgoSwitch and it is recommended that this function be enabled on the entire network. If this function is not enabled on the entire network, an X2-based
handover may fail because inconsistent EARFCNs may be selected by the source cell and the target cell.

None

There are three types of data sources:
• Network plan (negotiation not required): parameter values planned and set by the operator
• Network plan (negotiation required): parameter values planned by the operator and negotiated with the evolved packet core (EPC) or peer transmission equipment
• User-defined: parameter values set by users
The following table describes the parameters that must be set in Cell MOs to configure the primary and secondary operating bands of each cell.
Frequency band Cell.FreqBand Radio planning This parameter specifies the primary frequency band of a multi-band cell.
(internal planning) Ensure consistent settings of primary and secondary frequency bands
between multi-band cells that operate in the same frequency range
throughout the entire network.
Cell Slave Band Cell.CellSlaveBand Radio planning This parameter specifies a secondary frequency band of the multi-band cell.
(internal planning) Set this parameter by running the ADD CELLBAND command.
If the uplink and downlink carrier frequencies of a cell are not included in
multiple frequency bands, the secondary frequency band can be set
successfully for the cell and UEs supporting this band can access the cell.
However, services on the UEs may be abnormal.
The following table describes the parameter that must be set in the CellAlgoSwitch MO to configure the function of adjusting the priority of a secondary frequency band.
MFBI Algorithm CellAlgoSwitch.MfbiAlgoSwitch Network plan This parameter determines whether to enable the function of adjusting the
Switch (negotiation not priority of a secondary frequency band. This parameter is optional. By default,
required) the function is disabled.
The following table describes the parameters that must be set in EutranInterNFreq MOs to configure each neighboring E-UTRA frequency. If a neighboring E-UTRAN cell
operates in N frequency bands, configure NEutranInterNFreq MOs with identical parameter settings except EARFCNs and primary band indicators.
Master Band EutranInterNFreq.MasterBandFlag Default/Recommended value If this parameter is set to TRUE(True), the EARFCN in the same MO is
Flag contained in SIB5.
If this parameter is set to FALSE(False) in an MO for a frequency:
• If this parameter is set to TRUE(True) in another MO for the
same frequency, the EARFCN in the MO with the parameter
set to FALSE(False) is not contained in SIB5.
• If this parameter is not set to TRUE(True) in any other MO for
the same frequency, only the smallest EARFCN in these MOs
is contained in SIB5.
Downlink EutranInterNFreq.DlEarfcn Radio planning (internal This parameter specifies the downlink EARFCN of the primary frequency
EARFCN planning) band if EutranInterNFreq.MasterBandFlag is set to TRUE.
The following table describes the parameters that must be set in the UtranNFreq MO to configure each neighboring UTRAN frequency. If a neighboring UTRAN cell operates in
N frequency bands, configure N UtranNFreq MOs with identical parameter settings except UARFCNs and primary band indicators.
Master Band Flag UtranNFreq.MasterBandFlag Default/Recommended If this parameter is set to TRUE(True), the UARFCN in the same MO is
value contained in SIB6.
If this parameter is set to FALSE(False):
• If this parameter is set to TRUE(True) in another MO for the
same frequency, the UARFCN in the MO with the parameter set
to FALSE(False) is not contained in SIB6.
• If this parameter is not set to TRUE(True) in any other MO for the
same frequency, only the smallest UARFCN in these MOs is
contained in SIB6.
Downlink UARFCN UtranNFreq.UtranDlArfcn Radio planning (internal This parameter specifies the downlink UARFCN of the primary frequency
planning) band if UtranNFreq.UtranDlArfcn is set to TRUE.
The following table describes the parameters that must be set in EutranExternalCell MOs to specify the secondary operating bands and the EARFCN in the primary operating
band of each external E-UTRAN cell.


Downlink EARFCN EutranExternalCell.DlEarfcn Radio planning This parameter specifies the downlink EARFCN in the
(internal planning) primary operating band of an external E-UTRAN cell.
External E-UTRAN Cell EutranExternalCell.EutranExternalCellSlaveBand Radio planning This parameter specifies the other frequency band in
Slave Band (internal planning) which the cell operates. For details about this parameter,
see 3GPP TS 36.104.
Ensure consistent settings of primary and secondary
frequency bands between multi-band cells that operate in
the same frequency range throughout the entire network.
Set this parameter by running the ADD
EUTRANEXTERNALCELLBAND command.
The following table describes the parameters that must be set in UtranExternalCell MOs to specify the secondary operating bands and the UARFCN in the primary operating
band of each external UTRAN cell.
Downlink UARFCN UtranExternalCell.UtranDlArfcn Radio planning (internal This parameter specifies the downlink UARFCN in the
planning) primary operating band of an external UTRAN cell.
External UTRAN Cell UtranExternalCell.UtranExternalCellSlaveBand Radio planning (internal This parameter specifies the other frequency band in
Slave Band planning) which the cell operates. For details about this parameter,
see 3GPP TS 36.104.
Ensure consistent settings of primary and secondary
frequency bands between multi-band cells that operate in
the same frequency range throughout the entire network.
Set this parameter by running the ADD
UTRANEXTERNALCELLBAND command.
The following table lists the MOs whose parameters related to the primary and secondary frequency bands must be set consistently.
MO Data Source Setting Notes
EUTRANINTERNFREQ Network plan (negotiation not The parameters of the primary and secondary EARFCNs must be set consistently.
required)
SERVICEIFDLEARFCNGRP Network plan (negotiation not The parameters of the primary and secondary EARFCNs must be set consistently.
required)
QCIEUTRANRELATION Network plan (negotiation not The parameters of the primary and secondary EARFCNs must be set consistently.
required)
EUTRANNFREQSCELLOP Network plan (negotiation not The parameters of the primary and secondary EARFCNs must be set consistently.
required)
RATFREQPRIORITYGROUP Network plan (negotiation not The parameters of the primary and secondary EARFCNs must be set consistently.
required)
EUTRANNFREQRANSHARE Network plan (negotiation not The parameters of the primary and secondary EARFCNs must be set consistently.
required)
INTERFREQBLKCELL Network plan (negotiation not The parameters of the primary and secondary EARFCNs must be set consistently.
required)
PCCFREQCFG Network plan (negotiation not The parameters of the primary and secondary EARFCNs must be set consistently.
required)
SCCFREQCFG Network plan (negotiation not The parameters of the primary and secondary EARFCNs must be set consistently.
required)
EUTRANSPEPCICELL Network plan (negotiation not The parameters of the primary and secondary EARFCNs must be set consistently.
required)

tting Primary and Secondary Operating Bands of a Cell
1. Run the ADD CELL command to set the primary frequency band.
2. Run the ADD CELLBAND command to set each secondary frequency band.
onfiguring Neighboring Frequencies
1. Run the ADD EUTRANINTERNFREQ command to configure neighboring E-UTRAN frequencies.

In accordance with the network plan, configure each EARFCN of an E-UTRAN frequency as a neighboring frequency instance. Add an EARFCN that is specific to
the primary frequency band, and set the Master Band Flag parameter of the EARFCN to TRUE(True). Then, add EARFCNs that are specific to secondary
frequency bands, and set the Master Band Flag parameters of the EARFCNs to FALSE(False).
2. Run the ADD UTRANNFREQ command to configure neighboring UTRAN frequencies.
In accordance with the network plan, configure each UARFCN of a UTRAN frequency as a neighboring frequency instance. Add a UARFCN that is specific to the
primary frequency band, and set the Master Band Flag parameter of the UARFCN to TRUE(True). Then, add UARFCNs that are specific to secondary frequency
bands, and set the Master Band Flag parameters of the UARFCNs to FALSE(False).
NOTE:
• If Master Band Flag is set to FALSE(False) for all instances of a neighboring frequency, the eNodeB treats the band with the smallest band indicator as the primary
frequency band.
• The primary and secondary EARFCNs of all cells under an eNodeB must be configured according to the network plan. In addition, the EARFCNs of the primary and
secondary bands must be configured in sequence. If a cell under an eNodeB is not configured according to the preceding rules, ANR incorrectly sets the EARFCN of
a secondary band to the frequency of an external cell. This will occur when ANR is triggered by a UE's MR to add an external cell.
tting Primary and Secondary Operating Bands of External Cells

1. Set the primary and secondary operating bands of an external E-UTRAN cell.
a. Run the ADD EUTRANEXTERNALCELL command to set the primary frequency band.
b. Run the ADD EUTRANEXTERNALCELLBAND command to set each secondary frequency band.
2. Set the primary and secondary operating bands of an external UTRAN cell.
a. Run the ADD UTRANEXTERNALCELL command to set the primary frequency band.
b. Run the ADD UTRANEXTERNALCELLBAND command to set each secondary frequency band.
abling the Function of Adjusting the Priority of a Secondary Frequency Band
1. Run the MOD CELLALGOSWITCH command to enable the function of adjusting the priority of a secondary frequency band.
tting Parameters Related to Primary and Secondary EARFCNs Consistently
1. Run the following commands to query the primary and secondary bands configured with E-UTRAN external cells:
• LST EUTRANINTERNFREQ
• LST SERVICEIFDLEARFCNGRP
• LST QCIEUTRANRELATION
• LST EUTRANNFREQSCELLOP
• LST RATFREQPRIORITYGROUP
• LST EUTRANNFREQRANSHARE
• LST INTERFREQBLKCELL
• LST PCCFREQCFG
• LST SCCFREQCFG
• LST EUTRANSPEPCICELL
2. For the EARFCNs whose primary and secondary bands are configured inconsistently, run the following commands to modify the settings:
• ADD EUTRANINTERNFREQ
• ADD SERVICEIFDLEARFCNGRP
• ADD QCIEUTRANRELATION
• ADD EUTRANNFREQSCELLOP
• ADD RATFREQPRIORITYGROUP
• ADD EUTRANNFREQRANSHARE
• ADD INTERFREQBLKCELL
• ADD PCCFREQCFG
• ADD SCCFREQCFG
• ADD EUTRANSPEPCICELL
Alternatively, run the following commands to modify the parameter settings:

• MOD EUTRANINTERNFREQ
• MOD SERVICEIFDLEARFCNGRP
• MOD QCIEUTRANRELATION
• MOD EUTRANNFREQSCELLOP
• MOD RATFREQPRIORITYGROUP
• MOD EUTRANNFREQRANSHARE
• MOD INTERFREQBLKCELL
• MOD PCCFREQCFG
• MOD SCCFREQCFG
• MOD EUTRANSPEPCICELL

This section assumes that a local multi-band E-UTRAN cell has an inter-frequency neighboring E-UTRAN cell and a neighboring UTRAN cell, which are also multi-band ones.
The following is an example of MML commands for configuring these cells at the local eNodeB.
tting Primary and Secondary Operating Bands of the Local E-UTRAN Cell
//Setting the primary frequency band

ADD CELL: LocalCellId=0, CellName="cell1111", FreqBand=17, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=5800, UlBandWidth=CELL_BW_N50, DlBan
dWidth=CELL_BW_N50, CellId=0, PhyCellId=0, FddTddInd=CELL_FDD, RootSequenceIdx=0, CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAr
eaIdCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, TxRxMode=1T1R;
//Setting a secondary frequency band
ADD CELLBAND: LocalCellId=0, FreqBand=12;
tting the Function of Adjusting the Priority of a Secondary Frequency Band
//Enabling the function of adjusting the priority of a secondary frequency band

MOD CELLALGOSWITCH: LocalCellId=0, MfbiAlgoSwitch=MFBIBandAdjAlgoSwitch-1;
onfiguring Neighboring Frequencies
//Setting the EARFCN of the neighboring E-UTRAN frequency in the primary frequency band
ADD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=5800, UlEarfcnCfgInd=NOT_CFG, CellReselPriorityCfgInd=NOT_CFG, SpeedDependSPCfgInd
=NOT_CFG, MeasBandWidth=MBW50, PmaxCfgInd=NOT_CFG, QqualMinCfgInd=NOT_CFG, MasterBandFlag=True;
//Setting the EARFCN of the neighboring E-UTRAN frequency in a secondary frequency band
ADD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=5140, UlEarfcnCfgInd=NOT_CFG, CellReselPriorityCfgInd=NOT_CFG, SpeedDependSPCfgInd
=NOT_CFG, MeasBandWidth=MBW50, PmaxCfgInd=NOT_CFG, QqualMinCfgInd=NOT_CFG,MasterBandFlag=False;
//Setting the UARFCN of the neighboring UTRAN frequency in the primary frequency band
ADD UTRANNFREQ: LocalCellId=0, UtranDlArfcn=3200, UtranFddTddType=UTRAN_FDD, UtranUlArfcnCfgInd=NOT_CFG, CellReselPriorityCfgInd
=NOT_CFG, MasterBandFlag=True;
//Setting the UARFCN of the neighboring UTRAN frequency in a secondary frequency band
ADD UTRANNFREQ: LocalCellId=0, UtranDlArfcn=1625, UtranFddTddType=UTRAN_FDD, UtranUlArfcnCfgInd=NOT_CFG, CellReselPriorityCfgInd
=NOT_CFG, MasterBandFlag=False;

tting Primary and Secondary Operating Bands of External Cells
//Setting the primary operating band of the external E-UTRAN cell

ADD EUTRANEXTERNALCELL: Mcc="460", Mnc="01", eNodeBId=0, CellId=0, DlEarfcn=5800, UlEarfcnCfgInd=NOT_CFG, PhyCellId=0, Tac=0;
//Setting a secondary operating band of the external E-UTRAN cell
ADD EUTRANEXTERNALCELLBAND: Mcc="460", Mnc="01", eNodeBId=0, CellId=0, FreqBand=12;
//Setting the primary operating band of the external UTRAN cell
ADD UTRANEXTERNALCELL: Mcc="460", Mnc="01", RncId=0, CellId=0, UtranDlArfcn=3200, UtranUlArfcnCfgInd=NOT_CFG, UtranFddTddType=UT
RAN_FDD, RacCfgInd=NOT_CFG, PScrambCode=0, Lac=33;
//Setting a secondary operating band of the external UTRAN cell
ADD UTRANEXTERNALCELLBAND: Mcc="460", Mnc="01", RncId=0, CellId=0, FreqBand=5;
tting Parameters Related to Primary and Secondary EARFCNs Consistently
//If only EARFCN 5800 of the primary band is configured in "Flexible User Steering", run the following command:
ADD RATFREQPRIORITYGROUP: RatFreqPriorityGroupId=0, RatType=EUTRAN, DlEarfcn=5800, Priority=7;
//If the EARFCN of the secondary band that has not been configured is 5140, run the following command to set parameters related to the secondary band:
ADD RATFREQPRIORITYGROUP: RatFreqPriorityGroupId=0, RatType=EUTRAN, DlEarfcn=5140, Priority=7;
mary and Secondary Operating Bands of a Cell
1. Start a Uu interface tracing task on the U2000 client.

2. Check the primary and secondary operating band information in SIB1. If the band information is consistent with that in the cell configuration, the band configuration
is correct.
3. Run the DSP CELL command to check cell status.
If Cell instance state is Normal, the cell has been activated.
4. Use a UE that supports the secondary operating band to access the cell. If the UE successfully accesses the cell, the multi-band cell works properly.
witch for Adjusting the Priority of a Secondary Operating Band

2. Check the switch setting for adjusting the priority of a secondary operating band in SIB1. If the switch setting is consistent with that in the cell configuration, the
switch is set correctly.
3. Run the DSP CELL command to check cell status.
If Cell instance state is Normal, the cell has been activated.
4. Use a UE that supports the secondary operating band to access the cell. If the UE successfully accesses the cell, the multi-band cell works properly.
ighboring Frequency Information

2. Check the information about the primary and secondary operating bands in SIB5. If the secondary operating band information is consistent with that in the
neighboring E-UTRAN frequency configuration, the neighboring E-UTRAN frequency configuration is correct.
3. Check the information about the primary and secondary operating bands in SIB6. If the information about the primary frequency and primary and secondary
operating bands is consistent with that in the neighboring UTRAN frequency configuration, the neighboring UTRAN frequency configuration is correct.
mary and Secondary Operating Bands of External Cells
1. Check whether the primary and secondary operating band configuration of an external E-UTRAN cell is correct.
a. Run the LST EUTRANEXTERNALCELL command to query the primary operating band of the cell.
If the cell was manually configured, check whether Downlink EARFCN in the command output indicates the EARFCN in the primary operating band. If
it does, the primary band configuration of the cell is correct.
b. Run the LST EUTRANEXTERNALCELLBAND command to query the secondary operating bands of the cell.
If the cell was manually configured, check whether Frequency band in the command output indicates the secondary operating bands of the cell. If it
does, the secondary band configuration of the cell is correct.
2. Check whether the primary and secondary band configuration of an external UTRAN cell is correct.
a. Run the LST UTRANEXTERNALCELL command to query the primary operating band of the cell.
If the cell was manually configured, check whether Downlink UARFCN in the command output indicates the UARFCN in the primary operating band. If
it does, the primary band configuration of the cell is correct.
b. Run the LST UTRANEXTERNALCELLBAND command to query the secondary operating bands of the cell.
If the cell was manually configured, check whether Frequency band in the command output indicates the secondary operating bands of the cell. If it
does, the secondary band configuration of the cell is correct.
If external cells are added by ANR, you can also check SON logs to verify whether the MFBI function takes effect:
1. On the U2000 client, choose SON > SON Log.

2. On the Query SON Log tab page, click LTE ANR Log in the Log Category drop-down list in the upper left corner. In the Event Name area, select Update
MultiBandCell Band. Then, click Query to query log information. If log information is available, the MFBI function takes effect.
None
N/A
N/A
Possible Issues
None

7 Parameters
Cell FreqBand ADD CELL LBFD- Cell Selection Meaning: Indicates the frequency band in which a cell
ADD CELLBAND 00201803 / and Re- operates. For details about this parameter, see 3GPP T
LST CELLBAND TDLBFD- selection 36.104. For details about the usage of 252 to 255, see
MOD CELL 00201803 Broadcast of the following LTE-U forum document: eNodeB Minimum
RMV CELLBAND LBFD-002009 / system Requirements for LTE-U SDL V1.0.
LST CELL
TDLBFD-002009 information GUI Value Range: 1~256
LBFD-070103 / Multi-Band Unit: None
TDLBFD- Compatibility Actual Value Range: 1~256
00201806 Enhancement Default Value: None
LEOFD-110301 LAA
(Licensed
Assisted
Access ) for
DL 2 Carrier
Cell CellSlaveBand ADD CELLBAND LBFD-070103 / Multi-Band Meaning: Indicates slave frequency bands of a cell. If t
LST CELLBAND TDLBFD- Compatibility operating frequency of a cell belongs to multiple
RMV CELLBAND 00201806 Enhancement frequency bands, the frequency band with the highest
priority is configured by the FreqBand parameter, and
frequency bands with other priorities are configured by
the CellSlaveBand parameter and added in descending
order based on frequency band priorities. The frequenc
band priorities of a cell are determined in network
V8.16.0, 3GPP TS 36.331 V9.1.0, 3GPP TS 36.331
frequency bands.
Unit: None
Default Value: None
CellAlgoSwitch MFBIAlgoSwitch MOD CELLALGOSWITCH LBFD- Multi-Band Meaning: Indicates whether to enable MFBI-related
LST CELLALGOSWITCH 070103/TDLBFD- Compatibility algorithms. The MFBIBandAdjAlgoSwitch option
00201806 Enhancement indicates whether to enable MFBI band priority
adjustment. If this option is selected, MFBI band priorit
adjustment is enabled. If this option is deselected, MFB
band priority adjustment is disabled.
GUI Value Range: MFBIBandAdjAlgoSwitch
(MFBIBandAdjAlgoSwitch)
Unit: None
Actual Value Range: MFBIBandAdjAlgoSwitch
Default Value: MFBIBandAdjAlgoSwitch:Off
EutranInterNFreq DlEarfcn ADD EUTRANINTERNFREQ LBFD- Coverage Meaning: Indicates the DL EARFCN of the neighboring
LST EUTRANINTERNFREQ 00201802 / Based Inter- cell on the neighboring E-UTRAN frequency. For detai
MOD EUTRANINTERNFREQ TDLBFD- frequency see the 3GPP TS 36.104.
RMV EUTRANINTERNFREQ 00201802 Handover GUI Value Range: 0~46589,54436~65535,66436~673
LBFD- Cell Selection Unit: None
00201803 / and Re- Actual Value Range:
TDLBFD- selection 0~46589,54436~65535,66436~67335
00201803 Distance Default Value: None
LBFD- Based Inter-
00201804 / frequency
TDLBFD- Handover
00201804 Service
LBFD- Based Inter-
00201805 / frequency
TDLBFD- Handover
00201805 Mobility
TDLOFD-001050 between LTE
TDD and LTE
FDD
EutranInterNFreq MasterBandFlag ADD EUTRANINTERNFREQ LBFD-070103 / Multi-Band Meaning: Indicates whether the EARFCN is specific to
MOD EUTRANINTERNFREQ TDLBFD- Compatibility the primary frequency band. Among the EARFCNs of t
LST EUTRANINTERNFREQ 00201806 Enhancement same frequency, if the MasterBandFlag parameter is s
to TRUE for one EARFCN and FALSE for other
EARFCNs, the former EARFCN is specific to the prima
frequency band while the latter EARFCNs are specific
secondary frequency bands. In this case, only the
EARFCN specific to the primary frequency band is
broadcast in system information block type 5 (SIB5). If
the MasterBandFlag parameter is set to FALSE for all
EARFCNs of the same frequency, only the smallest
EARFCN is broadcast in SIB5.
GUI Value Range: FALSE(False), TRUE(True)
Unit: None
Actual Value Range: FALSE, TRUE
Default Value: FALSE(False)


UtranNFreq UtranDlArfcn ADD UTRANNFREQ LBFD- Cell Selection Meaning:
LST UTRANNFREQ 00201803 / and Re- Indicates the DL UARFCN of the neighboring cell on th
MOD UTRANNFREQ TDLBFD- selection UTRAN frequency. The UARFCN range in each FDD
RMV UTRANNFREQ 00201803 PS Inter-RAT frequency band is shown as follows:
LOFD-001019 / Mobility Band 1:
TDLOFD-001019 between Normal UARFCNs: [10562-10838]
LBFD-002009 / E-UTRAN
Special UARFCNs: none
TDLBFD-002009 and UTRAN
Band 2:
TDLOFD-001078 Broadcast of
system Normal UARFCNs: [9662-9938]
information Special UARFCNs:
E-UTRAN to (412,437,462,487,512,537,562,587,612,637,662,687)
UTRAN Band 3:
CS/PS Normal UARFCNs: [1162-1513]
steering Special UARFCNs: none
Band 4:
Normal UARFCNs: [1537-1738]
Special UARFCNs: (1887, 1912, 1937, 1962, 1987,
2012, 2037, 2062, 2087)
Band 5:
Special UARFCNs: (1007, 1012, 1032, 1037, 1062,
1087)
Band 6:
Special UARFCNs: (1037, 1062)
Band 7:
Special UARFCNs: (2587, 2612, 2637, 2662, 2687,
2712, 2737, 2762, 2787, 2812, 2837, 2862, 2887, 2912
Band 8:
Band 9:
The UARFCN range in each TDD frequency band is
shown as follows:
Band 1:
Normal UARFCNs: [9500-9600] and [10050-10125]
Band 2:
Band 3:
Band 4:
Special UARFCNs: (2112, 2137, 2162, 2187, 2212,
2237, 2262, 2287, 2312, 2337)
Band 5:
Band 6:
For details, see 3GPP TS 25.104 and 3GPP TS 25.105
Unit: None
Default Value: None
UtranNFreq MasterBandFlag ADD UTRANNFREQ LBFD-070103 / Multi-Band Meaning: Indicates whether the UARFCN is specific to
MOD UTRANNFREQ TDLBFD- Compatibility the primary frequency band. Among the UARFCNs of t
LST UTRANNFREQ 00201806 Enhancement same frequency, if the MasterBandFlag parameter is s
to TRUE for one UARFCN and FALSE for other
UARFCNs, the former UARFCN is specific to the prima
frequency band while the latter UARFCNs are specific
secondary frequency bands. In this case, only the
UARFCN specific to the primary frequency band is
broadcast in system information block type 6 (SIB6). If
the MasterBandFlag parameter is set to FALSE for all
UARFCNs of the same frequency, only the smallest
UARFCN is broadcast in SIB6.
GUI Value Range: FALSE(False), TRUE(True)
Unit: None
Actual Value Range: FALSE, TRUE
Default Value: FALSE(False)
eNBRsvdPara RsvdSwPara3 MOD ENBRSVDPARA None None Meaning:

LST ENBRSVDPARA Indicates the 32-bit reserved parameter 3 that is reserv
for future requirements.
Note on parameter replacement: Reserved parameters
are temporarily used in patch versions and will be
replaced with new parameters. For example, the ID of


new parameter can signify the parameter function.
Therefore, avoid using this parameter.
GUI Value Range: RsvdSwPara3_bit1
(ReservedSwitchParameter3_bit1), RsvdSwPara3_bit2
(ReservedSwitchParameter3_bit10),
RsvdSwPara3_bit11(ReservedSwitchParameter3_bit1
Unit: None
Actual Value Range: RsvdSwPara3_bit1,
RsvdSwPara3_bit2, RsvdSwPara3_bit3,
RsvdSwPara3_bit32
Default Value: RsvdSwPara3_bit1:Off,
RsvdSwPara3_bit2:Off, RsvdSwPara3_bit3:Off,
RsvdSwPara3_bit32:Off
EutranExternalCell DlEarfcn ADD EUTRANEXTERNALCELL LOFD-001036 / RAN Sharing Meaning: Indicates the DL EARFCN of the external
MOD EUTRANEXTERNALCELL TDLOFD-001036 with Common E-UTRAN cell. For details, see 3GPP TS 36.104.
LST EUTRANEXTERNALCELL LOFD-001037 / Carrier GUI Value Range: 0~46589,54436~65535,66436~673
TDLOFD-001037 RAN Sharing Unit: None
TDLBFD- with Actual Value Range:
00201801 Dedicated 0~46589,54436~65535,66436~67335
TDLBFD- Carrier
Default Value: None
00201802 Coverage
TDLBFD- Based Intra-
00201804 frequency
Handover
TDLBFD-
00201805 Coverage
Based Inter-
TDLOFD-001050
frequency
LOFD-070206 Handover
Distance
Based Inter-
frequency
Handover
Service
Based Inter-


frequency
Handover
Mobility
between LTE
TDD and LTE
FDD
Hybrid RAN
Sharing
EutranExternalCell EutranExternalCellSlaveBand ADD LBFD-070103 / Multi-Band Meaning: Indicates slave frequency bands of an extern
EUTRANEXTERNALCELLBAND TDLBFD- Compatibility E-UTRAN cell. If the operating frequency of an externa
LST 00201806 Enhancement E-UTRAN cell belongs to multiple frequency bands, the
EUTRANEXTERNALCELLBAND
downlink frequency of the frequency band with the
RMV
EUTRANEXTERNALCELLBAND highest priority is configured by the DlEarfcn paramete
and frequency bands with other priorities are configure
by the EutranExternalCellSlaveBand parameter and
added in descending order based on frequency band
priorities. The frequency band priorities of an external
E-UTRAN cell are determined in network planning. It is
recommended that the frequency bands supporting UE
that comply with 3GPP TS 36.331 V8.16.0, 3GPP TS
36.331 V9.1.0, 3GPP TS 36.331 V10.5.0, or a later vis
be configured as slave frequency bands.
Unit: None
Default Value: None
UtranExternalCell UtranDlArfcn ADD UTRANEXTERNALCELL LOFD-001019 / PS Inter-RAT Meaning:

MOD UTRANEXTERNALCELL TDLOFD-001019 Mobility Indicates the DL UARFCN of the external UTRAN cell.
LST UTRANEXTERNALCELL between The UARFCN range in each FDD frequency band is
E-UTRAN shown as follows:
and UTRAN Band 1:
Band 2:
Special UARFCNs:
(412,437,462,487,512,537,562,587,612,637,662,687)
Band 3:
Band 4:
Special UARFCNs: (1887, 1912, 1937, 1962, 1987,
2012, 2037, 2062, 2087)
Band 5:
Special UARFCNs: (1007, 1012, 1032, 1037, 1062,
1087)
Band 6:
Special UARFCNs: (1037, 1062)
Band 7:
Special UARFCNs: (2587, 2612, 2637, 2662, 2687,
2712, 2737, 2762, 2787, 2812, 2837, 2862, 2887, 2912
Band 8:
Band 9:
The UARFCN range in each TDD frequency band is
shown as follows:
Band 1:
Band 2:
Band 3:
Band 4:
Special UARFCNs: (2112, 2137, 2162, 2187, 2212,
2237, 2262, 2287, 2312, 2337)
Band 5:
Band 6:
For details, see 3GPP TS 25.104 and 3GPP TS 25.105


Unit: None
Default Value: None
UtranExternalCell UtranExternalCellSlaveBand ADD LBFD-070103 / Multi-Band Meaning: Indicates slave frequency bands of an extern
UTRANEXTERNALCELLBAND TDLBFD- Compatibility UTRAN cell. If the operating frequency of an external
LST 00201806 Enhancement UTRAN cell belongs to multiple frequency bands, the
UTRANEXTERNALCELLBAND
downlink frequency of the frequency band with the
RMV
UTRANEXTERNALCELLBAND highest priority is configured by the UtranDlArfcn
parameter, and frequency bands with other priorities a
configured by the UtranExternalCellSlaveBand
parameter and added in descending order based on
frequency band priorities. The frequency band priorities
of an external UTRAN cell are determined in network
V8.16.0, 3GPP TS 36.331 V9.1.0, 3GPP TS 36.331
frequency bands.
Unit: None
Default Value: None
Cell DlEarfcn ADD CELL LBFD-002009 / Broadcast of Meaning: Indicates the DL EARFCN of the cell. For
MOD CELL TDLBFD-002009 system details about this parameter, see 3GPP TS 36.104. Fo
LST CELL LBFD- information the detailed usage of 255144 to 262143, see the
00201801 / Coverage following LTE-U forum document: eNodeB Minimum
TDLBFD- Based Intra- Requirements for LTE-U SDL V1.0.
00201801 frequency GUI Value Range:
LBFD- Handover 0~65535,66436~67335,255144~256143,260894~2621
00201803 / LAA Unit: None
TDLBFD- (Licensed Actual Value Range:
00201803 Assisted 0~65535,66436~67335,255144~256143,260894~2621
LEOFD-110301 Access ) for Default Value: None
DL 2 Carrier
8 Counters
There are no specific counters associated with this feature.
9 Glossary
1. 3GPP TS 36.331: "Radio Resource Control (RRC)"

2. Idle Mode Management Feature Parameter Description
3. Overview of Mobility Management in Connected Mode Feature Parameter Description
4. Intra-RAT Mobility Management in Connected Mode Feature Parameter Description
5. Inter-RAT Mobility Management in Connected Mode Feature Parameter Description

eRAN
Physical Channel Resource Management Feature Parameter
Description
Issue 04
Date 2017-01-15

Notice

5 Contents
1.1 Scope
1.2 Exclusion Clauses for Trial Features
1.4 Change History
2 Overview
3 PHICH Resource Management
4 PDCCH/ePDCCH Resource Management

4.1 PDCCH/ePDCCH Information Types
4.2 PDCCH Symbol Adaptation
4.3 PDCCH Aggregation Level Adaptation
4.4 Closed-Loop Adjustment to the PDCCH Aggregation Level
4.5 CCE Ratio Adaptation

4.6 PDCCH Utilization Improvement

4.7 ePDCCH Resource Management
5 PUCCH Resource Management

5.1 PUCCH Information Types
5.1.1 HARQ-ACK
5.1.2 SRI
5.1.3 CQI, PMI, and RI
5.2 Cyclic Shift Interval for the PUCCH
5.3 Dynamic PUCCH Resource Adjustment
5.4 PUCCH Resource Allocation Policy
5.5 PUCCH Flexible Configuration
6 SRS Resource Management

6.1 SRS-related Concepts
6.1.1 SRS Subframe Configuration Index
6.1.2 SRS Subframe Period
6.1.3 SRS Subframe Offset
6.2 Cell-specific SRS
6.2.1 Cell-specific SRS Subframe
6.2.2 Cell-specific SRS Bandwidth
6.3 UE-specific SRS
6.3.1 UE-specific SRS Subframe
6.3.2 UE-specific SRS Period Adaptation
6.3.3 UE-specific SRS Bandwidth
6.4 SRS and HARQ ACK Processing
6.5 SRS Multiplexing
6.5.1 FDM
6.5.2 CDM
6.6 SRS Frequency Hopping
7 Related Features
7.1 LBFD-002003 Physical Channel Management
7.2 LBFD-070107 PDCCH Utilization Improvement
7.3 LOFD-001093 PUCCH Flexible Configuration
7.4 LAOFD-110203 ePDCCH (Trial)
8 Network Impact
8.1 LBFD-002003 Physical Channel Management
8.2 LBFD-070107 PDCCH Utilization Improvement
8.3 LOFD-001093 PUCCH Flexible Configuration
8.4 LAOFD-110203 ePDCCH (Trial)
9 Engineering Guidelines for PHICH Resource Management

9.1 When to Use
9.3 Planning
9.4 Deployment
9.4.1 Requirements
9.4.2 Precautions
9.4.3 Initial Configuration
9.4.6 Deactivation
9.5 PHICH Monitoring
9.7 Possible Issues
10 Engineering Guidelines for PDCCH/ePDCCH Resource Management

10.1 When to Use
10.3 Planning
10.4 Deployment
10.4.1 Requirements
10.4.2 Precautions
10.4.6 Deactivation


10.5 PDCCH/ePDCCH Monitoring
10.7 Possible Issues
11 Engineering Guidelines for PUCCH Resource Management

11.1 When to Use
11.3 Planning
11.4 Deployment
11.4.1 Requirements
11.4.2 Precautions
11.4.6 Deactivation
11.5 PUCCH Monitoring
11.6 Performance Optimization
12 Engineering Guidelines for SRS Resource Management

12.1 When to Use
12.3 Planning
12.4 Deployment
12.4.1 Requirements
12.4.2 Precautions
12.4.6 Deactivation
12.5 SRS Monitoring
13 Parameters
14 Counters
15 Glossary
Scope
This document describes physical channel resource management, including its technical principles, related features, network impact, and engineering guidelines.
This document covers the following features:
• LBFD-002003 Physical Channel Management

• LBFD-070107 PDCCH Utilization Improvement
• LOFD-001093 PUCCH Flexible Configuration
• LAOFD-110203 ePDCCH (Trial)
eNodeB Type Model
Micro BTS3202E
BTS3203E

eNodeB Type Model

BTS3911E
BTS3912E
Exclusion Clauses for Trial Features

Trial features are features that are not yet ready for full commercial release for certain reasons. For example, the industry chain (terminals/CN) may not be sufficiently
compatible. However, these features can still be used for testing purposes or commercial network trials. Anyone who desires to use the trial features shall contact Huawei and
enter into a memorandum of understanding (MoU) with Huawei prior to an official application of such trial features. Trial features are not for sale in the current version but
customers may try them for free.
Customers acknowledge and undertake that trial features may have a certain degree of risk due to absence of commercial testing. Before using them, customers shall fully
understand not only the expected benefits of such trial features but also the possible impact they may exert on the network. In addition, customers acknowledge and undertake
that since trial features are free, Huawei is not liable for any trial feature malfunctions or any losses incurred by using the trial features. Huawei does not promise that problems
with trial features will be resolved in the current version. Huawei reserves the rights to convert trial features into commercial features in later R/C versions. If trial features are
converted into commercial features in a later version, customers shall pay a licensing fee to obtain the relevant licenses prior to using the aforesaid commercial features. If a
customer fails to purchase such a license, the trial feature(s) will be invalidated automatically when the product is upgraded.
Intended Audience

Change History
• Feature change
Changes in features and parameters of a specified version
AN11.1 04 (2017-01-15)
Editorial change Optimized descriptions of the None N/A

CellPdcchAlgo.PdcchCapacityImproveSwitch and
CellPdcchAlgo.PdcchPowerEnhancedSwitch parameters. For
details, see 4.6 PDCCH Utilization Improvement.
AN11.1 03 (2016-11-01)
Editorial change Added the method of calculating the interference degree. For None N/A
details, see PUCCH Flexible Configuration in 11.1 When to Use.
AN11.1 02 (2016-04-20)
Editorial change Modified the following contents: None N/A

• Title (changed to 4.6 PDCCH Utilization Improvement)
• Network Performance in 8.2 LBFD-070107 PDCCH Utilization
Improvement
• PDCCH Utilization Improvement in 10.1 When to Use
• Configuring PDCCH Utilization Improvement in 10.4.3.3 Using
MML Commands
• 10.4.3.4 MML Command Examples
• PDCCH Utilization Improvement in 10.4.4 Activation Observation
• Deactivating PDCCH Utilization Improvement in 10.4.6.2 Using
MML Commands
• Deactivating PDCCH Utilization Improvement in 10.4.6.3 MML
Command Examples
AN11.1 01 (2016-03-07)
Feature change Added the standard QCI 65, QCI 66, QCI 69, and QCI 70. For Added the CellQciPara MO and its Macro, micro, and
details, see the following sections: parameters. LampSite eNodeBs
• 5.1.2 SRI
• 11.4.3.1 Data Preparation
• 11.4.3.3 Using MML Commands
• 11.4.4 Activation Observation


Editorial change Added descriptions of a mutually exclusive feature LEOFD- None N/A
111302 Flexible Bandwidth Based On Overlapped Carriers to
LAOFD-110203 ePDCCH. For details, see Mutually Exclusive
Features in 7.4 LAOFD-110203 ePDCCH (Trial).
Revised descriptions in the following chapters: None N/A

• 2 Overview
• 3 PHICH Resource Management
• 4 PDCCH/ePDCCH Resource Management
AN11.1 Draft B (2015-12-30)
Feature change Added a format 1 code channel allocation mode Added the OPTISELECTMODE Macro, micro, and
RBSAVINGMODE(RBSAVINGMODE). For details, see Format1 (OPTISELECTMODE) option to the LampSite eNodeBs
Code Channel Allocation Mode in 5.1 PUCCH Information Types. PUCCHCfg.Format1ChAllocMode parameter.
Added the function of configuring SCC HARQ-ACK resources. • Added the Macro, micro, and
For details, see 5.1.1 HARQ-ACK. PUCCHCfg.Format3RbNum LampSite eNodeBs
parameter.
• Added the
PUCCHCfg.Max2CCAckChNum
parameter.
• Added the
SCCAckResourceCfgSw option
to the
CellAlgoSwitch.PucchAlgoSwitch
parameter.
AN11.1 Draft A (2015-12-07)
Feature change Added the trial feature LAOFD-110203 ePDCCH. For details, Added the following parameters: Macro, micro, and
see the following sections: • CellPdcchAlgo.EpdcchAlgoSwitch LampSite eNodeBs
• 4.1 PDCCH/ePDCCH Information Types • CellPdcchAlgo.CceThdtoEnableEpdcch
• 4.7 ePDCCH Resource Management • CellPdcchAlgo.RbThdtoEnableEpdcch
• 7.4 LAOFD-110203 ePDCCH (Trial) • CellPdcchAlgo.CceThdtoDisableEpdcch
• 8.4 LAOFD-110203 ePDCCH (Trial) • CellPdcchAlgo.EcceThdtoDisableEpdcch
• 10 Engineering Guidelines for PDCCH/ePDCCH Resource • CellPdcchAlgo.RbThdtoDisableEpdcch
Management
Added the function allowing the adjustment of the PDCCH Added the Macro, micro, and
initial aggregation level. For details, see the following sections: CellPdcchAlgo.PdcchInitialCceAdjustValue LampSite eNodeBs
parameter.
• 4.6 PDCCH Utilization Improvement
• Required Data in 10.4.3.1 Data Preparation
• Configuring PDCCH Utilization Improvement in 10.4.3.3 Using
MML Commands
• PDCCH Utilization Improvement in 10.4.4 Activation
Observation
• Deactivating PDCCH Utilization Improvement in 10.4.6.2 Using
MML Commands
Added format 1 and format 2 code channel allocation modes. • Added the OPTISELECTMODE Macro, micro, and
For details, see the following sections: (OPTISELECTMODE) option to the LampSite eNodeBs
• 5.1 PUCCH Information Types PUCCHCfg.Format1ChAllocMode
parameter.
• 11.4.3.1 Data Preparation
• Added the
• 11.4.3 Initial Configuration
PUCCHCfg.Format2ChAllocMode
• Format1 Code Channel Allocation Mode and Format2 Code parameter.
Channel Allocation Mode in 11.4.4 Activation Observation
Added the PUCCH resource allocation policy function. For Added the PUCCHCfg.PucchAllocPolicy Macro, micro, and
details, see the following sections: parameter. LampSite eNodeBs
• 5.4 PUCCH Resource Allocation Policy
• Network Performance in 8.1 LBFD-002003 Physical Channel
Management
• RB Priority Mode Switch in 11.4.4 Activation Observation
Added the SRS algorithm optimization switch. In FDD+TDD Added the SRSCfg.SrsAlgoOptSwitch parameter. Macro, micro, and
mixed networking scenarios, this switch is used to avoid LampSite eNodeBs
handover failure from TDD cells to FDD cells. Handover failure
may arise due to compatibility problems of certain UEs in the
TDD cells. The SRS algorithm optimization switch can improve
the handover success rate of TDD cells. For details, see the
following sections:
• Configuration in 6.2.1 Cell-specific SRS Subframe


• 12.1 When to Use
• 12.4.2 Precautions
• 12.6 Parameter Optimization
Added performance counters related to the number of times of None Macro, micro, and
PDCCH uplink resource reallocation with aggregation level 1, LampSite eNodeBs
2, 4, or 8. For details, see 10.5 PDCCH/ePDCCH Monitoring.
Editorial change Revised descriptions in 5 PUCCH Resource Management. None N/A
Revised descriptions of CME-based feature configuration in None N/A

engineering guidelines.
Feature ID Feature Name Supported by Macro Supported by Micro Supported by LampSite

eNodeBs eNodeBs eNodeBs
LBFD-002003 Physical Channel Management Yes Yes Yes
LBFD-070107 PDCCH Utilization Improvement Yes Yes Yes
LOFD-001093 PUCCH Flexible Configuration Yes Yes Yes
LAOFD-110203 ePDCCH (Trial) Yes Yes Yes
Function Difference
Channel bandwidths of 1.4 MHz Implementation of this function varies by eNodeB types:
and 3 MHz • Macro eNodeBs support the channel bandwidths of 1.4 MHz and 3 MHz
• Micro and LampSite eNodeBs do not support the channel bandwidths of 1.4 MHz and 3 MHz.
For details, see the following sections:
• 3 PHICH Resource Management
• 4.1 PDCCH/ePDCCH Information Types
• 5.3 Dynamic PUCCH Resource Adjustment
ePDCCH • This function applies only to the macro eNodeB, LampSite eNodeB, BTS3912E, and BTS3911E.
• This function applies only to the 10 MHz, 15 MHz, and 20 MHz bandwidths.
2 Overview
Physical channel resource management properly configures control signaling resources to minimize control signaling resource overhead, ensure control signaling demodulation
performance, and maximize data throughput.
In an LTE network, resource management is performed for each channel, as described in Table 2-1.
Table 2-1 Resource management for physical channels
Physical Channel Resource Management
Downlink Physical broadcast channel (PBCH) PBCH resource allocation does not require manual configurations.
physical
channels Physical control format indicator channel (PCFICH) PCFICH resource allocation does not require manual
configurations.
Physical hybrid ARQ indicator channel (PHICH) See 3 PHICH Resource Management.
Physical Downlink Control Channel (PDCCH) and Enhanced Physical See 4 PDCCH/ePDCCH Resource Management.
Downlink Control Channel (ePDCCH)
Physical downlink shared channel (PDSCH) See Scheduling Feature Parameter Description.
Physical multicast channel (PMCH) See eMBMS Feature Parameter Description.
Uplink physical Physical uplink control channel (PUCCH) See 5 PUCCH Resource Management.
channels
Physical uplink shared channel (PUSCH) See Scheduling Feature Parameter Description.
Physical random access channel (PRACH) See Random Access Control and RACH Optimization Feature Parameter
Description.
This document also describes the sounding reference signal (SRS) resource management algorithm because SRSs are scheduled and managed separately.
For details about power configurations for each channel, see Power Control Feature Parameter Description.
3 PHICH Resource Management
The PHICH carries hybrid automatic repeat request (HARQ) ACK and NACK for uplink data.

The PHICH resource positions for each UE in the uplink are determined by the PUSCH information, PHICH duration, and the number of PHICH groups of this UE. For details,
see section 6.9 "Physical hybrid ARQ indicator channel" in 3GPP TS 36.211 V10.4.0.
• The PHICHCfg.PhichDuration parameter specifies the type of PHICH duration as follows:

Generally, when macro eNodeBs are deployed in urban areas, the coverage of each channel meets basic requirements. Therefore, you are advised to set the
PHICHCfg.PhichDuration parameter to NORMAL in this scenario. In the following scenarios, you are advised to set the PHICHCfg.PhichDuration parameter to
EXTENDED to achieve better demodulation performance: Wide coverage for macro eNodeBs is required, such as in deserts and on ocean surface. Micro eNodeBs
are severely interfered by adjacent macro eNodeBs and coverage needs to be extended.
◾ If this parameter is set to NORMAL, the PHICH is mapped only to the first orthogonal frequency division multiplexing (OFDM) symbol of a subframe, and
the number of OFDM symbols occupied by a PDCCH is adaptively adjusted.
◾ If this parameter is set to EXTENDED, the PHICH is mapped to the first three OFDM symbols and the three resource element groups (REGs) are
allocated on the three symbols to obtain time diversity gains. Therefore, demodulation performance at the physical layer in some scenarios outperforms
that when this parameter is set to NORMAL. When this parameter is set to EXTENDED, PDCCH symbol adaption does not take effect and a PDCCH
occupies a fixed number of OFDM symbols. The number of OFDM symbols occupied by a PDCCH depends on the channel bandwidth:
◾ If the channel bandwidth is 3 MHz (Macro), 5 MHz, 10 MHz, 15 MHz, or 20 MHz, a PDCCH can occupy only three OFDM symbols.
◾ If the channel bandwidth is 1.4 MHz, a PDCCH can occupy three or four OFDM symbols. The channel bandwidth of 1.4 MHz is applicable to
macro eNodeBs.
• The PHICHCfg.PhichResource parameter is used to calculate the number of PHICH groups in a cell. For details about the number of PHICH groups, see section
9.1.2 "PHICH Assignment Procedure" in 3GPP TS 36.213 V10.1.0.
◾ If this parameter is set to ONE_SIXTH, the number of PHICH groups is the minimum, the number of UEs using code division multiplexing (CDM) in each
PHICH group is the maximum, and the PHICH demodulation performance is the worst. In addition, the number of UEs that can be scheduled in each TTI
may decrease due to the limit on the maximum number of UEs using CDM in each PHICH group. If the normal cyclic prefix (CP) is used, each PHICH
group contains a maximum of eight UEs. If the extended CP is used, each PHICH group contains a maximum of four UEs.
◾ If this parameter is set to TWO, the number of PHICH groups is the maximum, the number of UEs using CDM in each PHICH group is the minimum, and
the PHICH demodulation performance is the best. However, the number of resources occupied by the PHICH increases, and the number of scheduling
indications sent on the PDCCH decreases.
4 PDCCH/ePDCCH Resource Management
PDCCH/ePDCCH Information Types

The PDCCH/ePDCCH transmits the following three types of downlink control information (DCI):
• Downlink grant
This DCI includes the PDSCH resource indicator, modulation and coding scheme (MCS), HARQ process number, and PUCCH power control commands. This DCI
has multiple formats, such as formats 1, 1A, 1B, 1C, 1D, 2, and 2A.
• Uplink grant
This DCI includes the PUSCH resource indicator, MCS, and PUSCH or PUCCH power control commands. This DCI has only format 0.
• Power control commands

This DCI is a group of PUSCH power control commands for a UE, which supplement PUSCH/PUCCH power control commands in an uplink grant. This DCI has
formats 3 and 3A.
NOTE:
For details about information bits in each format, see section 5.3.3 "Downlink control information" in 3GPP TS 36.212 V11.4.0.
As shown in Figure 4-1, the PDCCH occupies the first or first several symbols of a subframe. If the channel bandwidth is 1.4 MHz (Macro), it occupies a maximum of four
symbols. In the case of other bandwidths, it occupies a maximum of three symbols.
Figure 4-1 shows an RB. Each grid represents a resource element (RE). REs in yellow are allocated for reference signals of port 0. REs in blue are allocated for reference signals
of port 1. REs in gray are allocated for the PDCCH.
Figure 4-1 Position of the PDCCH
Figure 4-2 shows the multiplexing of ePDCCH, PDCCH, and PDSCH.
Figure 4-2 Multiplexing of ePDCCH, PDCCH, and PDSCH

The ePDCCH and PDSCH use the frequency division multiplexing (FDM) while the ePDCCH and PDCCH use the time division multiplexing (TDM). The ePDCCH can occupy all
OFDM symbols in the time domain except those for the PDCCH. The start symbol of the ePDCCH is determined by RRC signaling or carried by the PCFICH. The ePDCCH
performs resource allocation in PRB units in the frequency domain.
PDCCH Symbol Adaptation

PDCCH symbol adaptation enables the eNodeB to adjust the number of symbols occupied by a PDCCH based on the number of required control channel elements (CCEs).
• When a PDCCH requires fewer CCEs, the eNodeB decreases the number of symbols occupied by the PDCCH and allocates idle time-frequency resources to
PDSCHs.
• When a PDCCH requires more CCEs, the eNodeB increases the number of symbols occupied by the PDCCH until the number reaches the maximum permissible
value.
To rapidly provide CCEs as required and prevent ping-pong adjustments to the number of symbols occupied by a PDCCH, the eNodeB can rapidly increase and slowly
decrease the number of symbols occupied by the PDCCH.
The CellPdcchAlgo.PdcchSymNumSwitch parameter specifies whether to enable PDCCH symbol adaptation.
• When this parameter is set to ON(On), PDCCH symbol adaptation is enabled, and CCE usage must be measured to check whether CCEs are sufficient. The
statistical method of CCE resources is as follows:
◾ If uplink or downlink CCEs fail to be allocated within a transmission time interval (TTI), CCEs are insufficient. In this situation, the number of symbols
occupied by the PDCCH needs to be increased. Uplink CCEs transmit uplink grants, and downlink CCEs transmit downlink grants.
◾ If there are CCEs left after uplink and downlink scheduling is complete within a certain period, the number of required CCEs is less than the number of
available CCEs in the symbols. In this situation, the number of symbols occupied by the PDCCH needs to be decreased.
• When this parameter is set to ECfiAdaptionON(ECfiAdaptionON), enhanced PDCCH symbol adaptation is enabled and the eNodeB decides whether to increase or
decrease the number of PDCCH symbols based on the downlink CCE usage, power usage, and RB usage to maximize downlink throughput. Compared with the
setting ON(On), the setting ECfiAdaptionON(ECfiAdaptionON) enables the eNodeB to more slowly increase and rapidly decrease the number of symbols occupied
by the PDCCH.
◾ If CCEs fail to be allocated to a UE following the first dynamically scheduled UE in the downlink within a TTI, and the downlink RB usage is less than 90%,
CCE resources are insufficient. In this situation, the number of symbols occupied by the PDCCH needs to be increased. If CCEs fail to be allocated to a
UE and the downlink RB usage is greater than 90%, CCEs provided in the symbols meet downlink requirements. In this situation, the number of symbols
occupied by the PDCCH does not need to be increased.
◾ If there are CCEs left after uplink and downlink scheduling is complete within 20 ms, the number of required CCEs is less than the number of available
CCEs in the symbols. In this situation, the number of symbols occupied by the PDCCH needs to be decreased.
◾ If the instantaneous downlink RB usage within a TTI is greater than 90%, the requirements for the downlink CCE quantity and power can be met after the
number of symbols is reduced, and no CCE allocation fails for high-priority scheduling in the uplink, then the CCE resources are sufficient and the
downlink PDSCH is restricted. In this situation, the number of symbols needs to be decreased immediately.
• When this parameter is set to OFF(Off), the eNodeB disables PDCCH symbol adaptation and allocates resources to a PDCCH based on the number of symbols
specified by the CellPdcchAlgo.InitPdcchSymNum parameter.
The CellPdcchAlgo.InitPdcchSymNum parameter specifies the number of OFDM symbols initially occupied by the PDCCH. If this parameter is set to a larger value,
more OFDM symbols are initially occupied by the PDCCH and less downlink resources are occupied by the PDSCH. In this case, downlink throughput decreases. If
this parameter is set to a smaller value, downlink throughput increases.
When the PucchSwitch and PucchFlexCfgSwitch options of the CellAlgoSwitch.PucchAlgoSwitch parameter are deselected, the change of OFDM symbols
occupied by the PDCCH affects the resources occupied by the PUCCH. Adjusting the CellPdcchAlgo.InitPdcchSymNum parameter online is not recommended. The
purpose is to avoid conflicts between PUCCH and other channels and ensure the performance.
PDCCH Aggregation Level Adaptation

A CCE is the smallest resource unit for transmission on a PDCCH. Each CCE contains nine REGs. Each individual REG contains four resource elements (REs) and carries 72
bits of information. Based on coding rates, the eNodeB can aggregate one, two, four, or eight CCEs to constitute a PDCCH which corresponds to aggregation level 1, 2, 4, or 8,
as stipulated in 3GPP specifications. The aggregation level indicates the number of CCEs a PDCCH occupies. For example, if the aggregation level is 1, the PDCCH occupies
one CCE; if the aggregation level is 2, the PDCCH occupies two CCEs.
• PDCCHs with aggregation level 8 have the lowest coding rate and the best demodulation performance.
If PDCCH aggregation levels for all UEs in a cell are set to 8, CCE resources for PDCCHs are wasted for UEs in the cell center and at a medium distance from the
cell center.
• PDCCHs with aggregation level 1 have the highest coding rate and the worst demodulation performance.
If PDCCH aggregation levels for all UEs in a cell are set to 1, PDCCHs may not be correctly demodulated by UEs at a medium distance from the cell center and at
the cell edge.
This function enables the eNodeB to select an appropriate PDCCH aggregation level based on channel quality, thereby maximizing the demodulation performance and the
capacity of the PDCCH.
• Channel quality is derived from the channel quality indicator (CQI).

• An appropriate PDCCH aggregation level is the lowest aggregation level ensuring that BLERs are less than 1.5%.
The eNodeB provides the aggregation level adaptation function for PDCCHs carrying uplink and downlink grant DCIs. Under satisfactory PDCCH demodulation performance
conditions, PDCCH aggregation level adaptation can:
• Minimize resources occupied by the PDCCH

• Reduce PDCCH load
• Reduce interference to neighboring cells
• Improve system performance
This function enables the eNodeB to select an appropriate PDCCH aggregation level. The eNodeB bases this selection on the signal to interference plus noise ratio (SINR). The
SINR is calculated based on the MCS index for the scheduled PDSCH. Figure 4-3 shows the procedure.

Figure 4-3 Procedure for PDCCH aggregation level adaptation
1. The CQI adjustment algorithm calculates the CQI value.

The CQI adjustment algorithm is an optional feature LOFD-00101501 CQI Adjustment. For details, see Scheduling Feature Parameter Description.
2. The eNodeB calculates the SINR of downlink reference signals based on the CQI value.
3. The eNodeB calculates the SINR of the PDCCH based on the SINR of the downlink reference signals.
4. The eNodeB calculates the demodulation thresholds for various coding rates or aggregation levels based on the DCI formats.
5. The eNodeB compares the PDCCH SINR with the demodulation threshold for each aggregation level and selects an appropriate PDCCH aggregation level.
The CellPdcchAlgo.AggLvlSelStrageForDualCW parameter is introduced to ensure the selection of an appropriate PDCCH aggregation level. This parameter specifies the policy
for selecting a PDCCH aggregation level in dual-codeword scenarios.
• If this parameter is set to STRATEGYBASEDONCAPACITY(Capacity-based Selection Strategy), the capacity-based policy is used. This also causes the average
PDCCH aggregation level to decrease and allows the PDCCH to accommodate more UEs. However, this policy causes larger PDCCH BLERs for UEs strongly
affected by interference. In this scenario, PDCCH BLERs cannot converge on the target value even when closed-loop adjustment to the PDCCH aggregation level is
enabled.
• If this parameter is set to STRATEGYBASEDONCOVERAGE(Coverage-based Selection Strategy), the coverage-based policy is used. The average PDCCH
aggregation level increases and the PDCCH demodulation performance improves. In this scenario, the number of UEs the PDCCH can support decreases.
Due to demodulation performance differences between terminals, the CellPdcchAlgo.PdcchMaxCodeRate parameter is introduced to set a maximum PDCCH code rate. When
the PDCCH code rate exceeds the value of the CellPdcchAlgo.PdcchMaxCodeRate parameter, the eNodeB automatically raises the PDCCH aggregation level:
• A smaller value of this parameter indicates a smaller maximum PDCCH code rate. When there is a smaller parameter value, the eNodeB selects a higher PDCCH
aggregation level, which leads to larger coverage but lower PDCCH capacity.
• A larger value of this parameter indicates a larger maximum PDCCH code rate. When there is a higher parameter value, the eNodeB selects a lower PDCCH
aggregation level, which leads to smaller coverage but higher PDCCH capacity.
An appropriate aggregation level must be set for the PDCCH so that all UEs in the cell can successfully interpret the control information. The CellPdcchAlgo.ComSigCongregLv
parameter specifies the appropriate PDCCH aggregation level.
NOTE:
Aggregation level adaptation does not apply to a PDCCH used for carrying a power control command in DCI format 3 or 3A or for indicating the transmission of random access
response, paging, or system information messages on the PDCCH.
Closed-Loop Adjustment to the PDCCH Aggregation Level

The PDCCH aggregation level may be inaccurate on the live network due to the following causes. In severe cases, service drops may occur.
• The interference with the PDSCH differs from the interference with the PDCCH.
• Periodic CQI adjustment used for selecting an MCS is slower than channel condition changes.
Therefore, closed-loop adjustment to the PDCCH aggregation level is used to dynamically adjust the PDCCH aggregation level based on the PDCCH BLER:
• If the PDCCH BLER is greater than the target BLER, the closed-loop adjustment raises the aggregation level to improve the PDCCH coverage performance.
• If the PDCCH BLER is less than the target BLER, the closed-loop adjustment lowers the aggregation level to reduce the PDCCH resource usage.
The CellPdcchAlgo.PdcchAggLvlCLAdjustSwitch parameter specifies whether to enable closed-loop adjustment to the PDCCH aggregation level.
The PDCCH BLER is calculated based on downlink grant DCI or uplink grant DCI 0. Closed-loop adjustment to the PDCCH aggregation level for downlink grants is based on the
downlink grant DCI. The adjustment for uplink grants is controlled by the PuschDtxSwitch option of the CellAlgoSwitch.UlSchSwitch parameter.
• If this option is selected, the adjustment for uplink grants is based on uplink grant DCI 0.
• If this option is cleared, the adjustment for uplink grants is based on all the downlink grant DCI.
The CellPdcchAlgo.PdcchBlerTarget parameter indicates the target BLER of the closed-loop adjustment to the PDCCH aggregation level. A larger or smaller value of this
parameter may result in negative gains of the throughput rate. The default value is recommended.
• A large value of this parameter increases PDCCH capacity but increases the DTX percentage of the PDCCH and reduces the system throughput rate.
• A small value of this parameter decreases the DTX percentage of the PDCCH, results in a high PDCCH aggregation level, reduces the system capacity, and reduces
the system throughput rate when CCE resources are limited.
CCE Ratio Adaptation

Uplink CCEs transmit uplink grants, and downlink CCEs transmit downlink grants. The CCE ratio is the ratio of the number of uplink CCEs to the number of downlink CCEs.

To adapt to changes in uplink and downlink services and improve cell throughput and quality of service (QoS), the eNodeB dynamically adjusts the CCE ratio based on the
usage of uplink and downlink CCEs.
The CellPdcchAlgo.CceRatioAdjSwitch parameter specifies whether to enable CCE ratio adaptation.
• If the CellPdcchAlgo.CceRatioAdjSwitch parameter is set to ON(On), the eNodeB dynamically adjusts the CCE ratio in each TTI based on the usage of uplink and
downlink CCEs.
• If the CellPdcchAlgo.CceRatioAdjSwitch parameter is set to OFF(Off), the eNodeB does not dynamically adjust the CCE ratio.
The ReserveCommonCCESwitch option of the CellPdcchAlgo.UlPdcchAllocImproveSwitch parameter specifies whether to reserve CCE resources in the common search
space for uplink channels.
• When the ReserveCommonCCESwitch option of the CellPdcchAlgo.UlPdcchAllocImproveSwitch parameter is selected, CCE resources in the common search
space will be reserved for uplink channels. When the PDCCH bandwidth is limited, the uplink CCE allocation success rate increases, and therefore the VoLTE
capacity and the access success rate increase. However, when the number of required downlink CCE resources increases, the delay for scheduling certain downlink
UEs increases.
• When the ReserveCommonCCESwitch option of the CellPdcchAlgo.UlPdcchAllocImproveSwitch parameter is cleared, CCE resources in the common search
space will not be reserved for uplink channels. When the PDCCH bandwidth is limited, the uplink CCE allocation success rate decreases and downlink scheduling
delay performance improves. However, this affects the VoLTE capacity and access success rate.
PDCCH Utilization Improvement

This section describes the basic feature LBFD-070107 PDCCH Utilization Improvement.
After CCEs fail to be allocated to a UE, the eNodeB reallocates CCEs to the UE by increasing the PDCCH transmit power and lowering the PDCCH aggregation level for the
UE. This improves the PDCCH allocation success rate and PDCCH capacity.
The CellPdcchAlgo.PdcchCapacityImproveSwitch parameter specifies whether to enable optimization on PDCCH capacity expansion.
• When the CellPdcchAlgo.PdcchCapacityImproveSwitch parameter is set to ON(On), the eNodeB increases the PDCCH power and lowers the PDCCH aggregation
level for a UE to reallocate CCEs to the UE if the CCE allocation for the UE fails.
• When the CellPdcchAlgo.PdcchCapacityImproveSwitch parameter is set to OFF(Off), the eNodeB neither increases the PDCCH power nor lowers the PDCCH
aggregation level for a UE to reallocate CCEs to the UE if the CCE allocation for the UE fails.
The CellPdcchAlgo.PdcchInitialCceAdjustValue parameter specifies the adjustment value of the PDCCH initial aggregation level. A larger value of this parameter indicates a
smaller SRB initial aggregation level, less CCE resources occupied by the PDCCH, and slightly less PDCCH demodulation performance. A smaller value of this parameter
indicates a greater SRB initial aggregation level, better PDCCH demodulation performance, and more occupied CCEs. In heavily loaded networks, you are advised to set this
parameter to 0, thereby decreasing the SRB CCE consumption and increasing the number of UEs that access the cell. The relationships between this parameter and
CellPdcchAlgo.PdcchCapacityImproveSwitch and the setting requirements are as follows:
• When the CellPdcchAlgo.PdcchCapacityImproveSwitch parameter is set to ON(On), the adjustment value of the PDCCH initial aggregation level depends. If the
value of the CellPdcchAlgo.PdcchInitialCceAdjustValue parameter is less than or equal to 0, the SRB adjustment value of the PDCCH initial aggregation level is
equal to the value and DRB adjustment value of the PDCCH initial aggregation level is 0. If the value of the CellPdcchAlgo.PdcchInitialCceAdjustValue parameter is
greater than 0, the SRB and DRB adjustment values of the PDCCH initial aggregation level are equal to the value.
• When the CellPdcchAlgo.PdcchCapacityImproveSwitch parameter is set to OFF(Off), the SRB and DRB adjustment values of the PDCCH initial aggregation level
are equal to the value of the CellPdcchAlgo.PdcchInitialCceAdjustValue parameter.
The eNodeB can select a more accurate aggregation level based on the PDCCH quality and proper PDCCH power, thereby decreasing the failure rate of allocating the PDCCH
aggregation level for PDCCH capacity expansion. The CellPdcchAlgo.PdcchPowerEnhancedSwitch parameter specifies whether to enable power control enhancement for the
PDCCH.
• When the CellPdcchAlgo.PdcchPowerEnhancedSwitch parameter is set to ON(On), the eNodeB selects a lower aggregation level based on the channel quality. A
lower aggregation level indicates a higher coding rate and poorer demodulation performance. To ensure PDCCH demodulation performance of UEs, the eNodeB
increases the PDCCH transmit power, thereby increasing the number of UEs allocated for the PDCCH per TTI. After this switch is on, the number of symbols
occupied by the PDCCH decreases in case of identical numbers of UEs to be scheduled or more UEs can be scheduled in case of identical numbers of symbols
occupied by the PDCCH.
• When the CellPdcchAlgo.PdcchPowerEnhancedSwitch parameter is set to OFF(Off), the eNodeB selects a higher aggregation level based on the channel quality.
The PDCCH transmit power is manually configured, thereby decreasing the number of UEs allocated for the PDCCH per TTI and affecting uplink and downlink
throughput of cells and UEs when the PDCCH resources are limited.
The CellPdcchAlgo.PdcchCapacityImproveSwitch and CellPdcchAlgo.PdcchPowerEnhancedSwitch parameters can be set to ON(On) at the same time. However, it is
recommended that the CellPdcchAlgo.PdcchCapacityImproveSwitch parameter be set to OFF(Off) in heavy-load scenarios.
ePDCCH Resource Management

This section describes the trial feature LAOFD-110203 ePDCCH.
ECCE is the minimum resource unit for ePDCCH transmission. Based on coding rates, the eNodeB can aggregate 1, 2, 4, 8, 16, or 32 ECCEs to constitute an ePDCCH, which
corresponds to aggregation level 1, 2, 4, 8, 16, or 32, as stipulated in 3GPP specifications. The aggregation level indicates the number of ECCEs occupied by an ePDCCH. For
example, if the aggregation level is 1, the ePDCCH occupies one ECCE; if the aggregation level is 2, the ePDCCH occupies two ECCEs.
• ePDCCHs with aggregation level 32 have the lowest coding rate and best demodulation performance.
If ePDCCH aggregation levels for all UEs in a cell are set to 32, ECCE resources for ePDCCHs are wasted for UEs in the cell center.
• ePDCCHs with aggregation level 1 have the highest coding rate and worst demodulation performance.
If ePDCCH aggregation levels for all UEs in a cell are set to 1, ePDCCHs may not be correctly demodulated by UEs not in the cell center.
After ePDCCH is enabled, ePDCCH resource management continues to use the following PDCCH switches: CellPdcchAlgo.PdcchAggLvlCLAdjustSwitch,
CellPdcchAlgo.CceRatioAdjSwitch, CellPdcchAlgo.PdcchCapacityImproveSwitch, CellPdcchAlgo.PdcchPowerEnhancedSwitch, and CellPdcchAlgo.PdcchBlerTarget. For
example, if ePDCCH and closed-loop adjustment to the PDCCH aggregation level are enabled, ePDCCH uses the mechanism of closed-loop adjustment to the ePDCCH
aggregation level. If ePDCCH is enabled and closed-loop adjustment to the PDCCH aggregation level is disabled, ePDCCH does not use the mechanism of closed-loop
adjustment to the ePDCCH aggregation level. If UEs are using ePDCCH resources, these UEs continue using ePDCCH resources until they exit even though ePDCCH is
disabled.
This feature has the following constraints:
• ePDCCH does not support 5 MHz, 3 MHz, or 1.4 MHz narrow bandwidth, non-standard bandwidth, or super combined cell scenarios.
• ePDCCH supports 1-, 2-, and 4-antenna configurations. It does not support the 8-antenna configuration.
• ePDCCH cannot be deployed on the LBBPc board.
• ePDCCH resources can be used only when the PUCCHCfg.DeltaShift parameter is set to DS1_DELTA_SHIFT(ds1).
5 PUCCH Resource Management
PUCCH Information Types

PUCCHs carry the following types of control messages:
• Acknowledgment (ACK) to downlink HARQ

• Scheduling request indicator (SRI)
• Feedback of downlink channel quality indications, including the CQI, precoding matrix indication (PMI), and rank indication (RI)

PUCCHs support seven formats. Table 5-1 describes the message type and modulation scheme for each format.
Table 5-1 PUCCH formats
PUCCH formats Control Message Modulation Scheme Number of Bits per Subframe
1 SRI N/A N/A
1a ACK to downlink HARQ for single-codeword transmission BPSK 1
1b ACK to downlink HARQ for multi-codeword transmission QPSK 2
2 Feedback of downlink channel quality indications QPSK 20
2a A 1-bit ACK to downlink HARQ, when the same UE simultaneously QPSK+BPSK 21

sends an ACK to downlink HARQ, and feedback of downlink
channel quality indications.
2b A 2-bit ACK to downlink HARQ, when the same UE simultaneously QPSK+QPSK 22

sends an ACK to downlink HARQ, and feedback of downlink
channel quality indications.
3 ACK to downlink HARQ for a maximum of 5 carriers in CA QPSK 48

scenarios. A reference signal carries a maximum of 10-bit ACK to
downlink HARQ when a UE simultaneously sends an ACK to
downlink HARQ for a maximum of 5 carriers and SRI in CA
scenarios.
PUCCHs occupy resource blocks (RBs) at two ends of an uplink cell bandwidth and use frequency hopping to achieve frequency diversity gains. Figure 5-1 shows the mapping
to physical RBs for a PUCCH. In this figure, m is specified in section 5.4 "Physical uplink control channel" in 3GPP TS 36.211 V10.4.0 and indicates the index of an RB used by
the PUCCH.
Figure 5-1 Mapping to physical RBs for a PUCCH
rmat1 Code Channel Allocation Mode
The PUCCHCfg.Format1ChAllocMode parameter specifies the mode for allocating code channel resources occupied by the PUCCH in format 1, 1a, or 1b in each RB. This
parameter takes effect only when the PUCCHCfg.DeltaShift parameter is set to DS1_DELTA_SHIFT(ds1).
• When the PUCCHCfg.Format1ChAllocMode parameter is set to FIXEDMODE(Fixed Mode), consecutive PUCCH format1/1a/1b code channel resources are always
allocated.
• When the PUCCHCfg.Format1ChAllocMode parameter is set to RANDOMMODE(Random Mode), PUCCH format1/1a/1b code channel resources are allocated at
random. In multi-UE scenarios, this decreases the code channel adjacency probability and improves detection performance.
• When the PUCCHCfg.Format1ChAllocMode parameter is set to OPTISELECTMODE(OPTISELECTMODE), PUCCH format 1/1a/1b code channel resources are
allocated using an optimized selection mode. Compared with the RANDOMMODE(Random Mode) option, the OPTISELECTMODE(OPTISELECTMODE) option
further reduces the adjacency possibility of code channels, decreases inter-bit interference, and improves the PUCCH demodulation capability, but may increase the
PUCCH RB overhead. When the cell bandwidth is 1.4 MHz, you are advised not to set this parameter to OPTISELECTMODE(OPTISELECTMODE).
• When the PUCCHCfg.Format1ChAllocMode parameter is set to RBSAVINGMODE(RBSAVINGMODE), PUCCH format 1/1a/1b code channel resources are
allocated based on RB saving by increasing UE multiplexing efficiency in RBs. A maximum of 36 n1PUCCH-AN code channels can be multiplexed in each RB.
Interference between code channels increases, and demodulation performance of PUCCH format 1/1a/1b code channel resources deteriorates. When the cell
bandwidth is 1.4 MHz, you are advised not to set this parameter to RBSAVINGMODE(RBSAVINGMODE).
NOTE:
The n1PUCCH-AN code channel is specified by the n1PUCCH-AN IE in the PUCCH-ConfigCommon message delivered over the air interface on the eNodeB side. It
indicates the number of code-division multiplexed SRIs and ACKs to downlink semi-persistent scheduling.
For the LBBPd and UBBP, when the PUCCHCfg.DeltaShift parameter is set to DS1_DELTA_SHIFT(ds1), the following rules apply to the channel resources. If the
PUCCHCfg.Format1ChAllocMode parameter is set to FIXEDMODE(Fixed Mode) or RANDOMMODE(Random Mode), the channel resources whose n1PUCCH-AN
code channel number modulo 36 is less than 18 are available and other channel resources are unavailable. If the PUCCHCfg.Format1ChAllocMode parameter is set
to OPTISELECTMODE(OPTISELECTMODE), 18 almost discontinuous channel resources on each RB are available and other channel resources are unavailable. If
the PUCCHCfg.Format1ChAllocMode parameter is set to RBSAVINGMODE(RBSAVINGMODE), the channel resources whose n1PUCCH-AN code channel number
modulo 36 is less than or equal to 35 are available and no channel resources are unavailable.
When the number of UEs in the cell is small (in newly deployed sites or in off-peak hours), this parameter can be set to either FIXEDMODE(Fixed Mode) or RANDOMMODE
(Random Mode). When the number of UEs in the cell is large or in the high-speed railway scenarios, the parameter value OPTISELECTMODE(OPTISELECTMODE) is
recommended. When uplink PRB resources are possibly limited, the parameter value RBSAVINGMODE(RBSAVINGMODE) is recommended.
After the PUCCHCfg.Format1ChAllocMode parameter is reconfigured, the cell is automatically reset so that the modification takes effect.
The PUCCHCfg.Format2ChAllocMode parameter specifies the mode for allocating code channel resources occupied by the PUCCH in format 2, 2a, or 2b.
• When the PUCCHCfg.Format2ChAllocMode parameter is set to FIXEDMODE(Fixed Mode), consecutive PUCCH format2/2a/2b code channel resources are always
allocated.
• When the PUCCHCfg.Format2ChAllocMode parameter is set to RANDOMMODE(Random Mode), PUCCH format2/2a/2b code channel resources are allocated at
random. This decreases the inter-bit interference and improves detection performance.
5.1.1 HARQ-ACK
A UE uses an ACK to respond to a PDSCH decoding success.
• If the UE successfully receives data from the eNodeB, it sends an ACK.

• If the UE fails to receive data from the eNodeB, it sends a negative acknowledgement (NACK).
A PUCCH needs to allocate code channel resources to UEs for sending HARQ-ACKs and also needs to allocate SCC HARQ-ACK channel resources on the PCC to CA UEs
(referred to as SCC ACK channel resources). According to the current 3GPP specifications, CA UEs can send SCC HARQ-ACKs using the following methods:
• Format1b plus channel selection

• Format3
The SCCAckResourceCfgSw option of the CellAlgoSwitch.PucchAlgoSwitch parameter specifies whether SCC ACK channel resources allocated to CA UEs are configurable.
These resources include Format1b SCC ACK channel resources and the number of Format3 RBs.
• When the SCCAckResourceCfgSw option is cleared, the number of SCC ACK resources allocated by the eNodeB to CA UEs depends on an algorithm and the
PUCCHCfg.Format3RbNum and PUCCHCfg.Max2CCAckChNum parameters do not take effect.
• When the SCCAckResourceCfgSw option is selected:
◾ When the eNodeB allocates Format3 channels to UEs using the Format3 method, the PUCCHCfg.Format3RbNum parameter specifies the number of
Format3 RBs that can be allocated by the eNodeB.
◾ When the eNodeB allocates SCC ACK channels to UEs using the Format1 plus channel selection method and the Dl2CCAckResShareSw option of the
CellAlgoSwitch.PucchAlgoSwitch parameter is selected, the PUCCHCfg.Max2CCAckChNum parameter specifies the number of 2CC SCC ACK channels
that can be allocated by the eNodeB.
5.1.2 SRI
A UE uses an SRI to request an uplink bandwidth to be allocated by the eNodeB. Figure 5-2 shows the scheduling request procedure.
Figure 5-2 Scheduling request procedure
The UE sends an SRI in the same format as an ACK when new uplink data needs to be scheduled. SRIs and ACKs can share the same RBs. Table 5-2 lists SR periodicity and
subframe offset configuration, as stipulated in 3GPP specifications.
Table 5-2 SR period and subframe offset configuration
SR Configuration Index SR Period (ms) SR Subframe Offset
0-4 5 SR Configuration Index
5-14 10 SR Configuration Index-5
155 Set this parameter to OFF(OFF). N/A
A UE sends SRIs to the eNodeB every SRI period. The PUCCHCfg.SriPeriodAdaptive parameter specifies whether a fixed or adaptive SRI period is used.
xed SRI Period
If the PUCCHCfg.SriPeriodAdaptive is set to OFF(Off), users can set the CellQciPara.SriPeriod parameter to specify an SRI period for each standardized QoS class identifier
(QCI).
NOTE:
If the GlobalProcSwitch.QciParaEffectFlag parameter is set to OFF(Off), you can use the CellStandardQci.SriPeriod parameter to configure the fixed SRI period.
• If a UE requests a single-service connection, the SRI period for the UE is the same as that for the QCI of the service.
• If a UE requests a multi-service connection, the SRI period for the UE is the minimum value among the SRI periods for all QCIs of the services on the UE.
If a shorter SRI period is set for services with different QCIs, a UE can send more SRIs in the SRI period, which causes fewer UEs to access the cell under the condition that the
cell resources remain unchanged.
This decreases the average uplink scheduling delay for the UE and improves user experience.
aptive SRI Period
SRIs occupy PUCCH resources, and their occupancy is represented by SRI loads.
The eNodeB adaptively adjusts an SRI period based on SRI loads, which is called SRI period adaptation.
The PUCCHCfg.SriPeriodAdaptive parameter specifies whether the eNodeB adaptively adjusts an SRI period based on SRI loads.
• If the PUCCHCfg.SriPeriodAdaptive parameter is set to QCIADAPTIVE(QCIADAPTIVE), the eNodeB adaptively adjusts the SRI period for newly admitted UEs
based on SRI loads. The SRI period adaptively changes based on the QCI.
Low SRI loads are determined based on the number of admitted UEs. The other SRI loads are determined based on the usage of SRI channel resources.
◾ For low SRI loads:
For low SRI loads, set SRI periods for all admitted UEs to 5 ms. This setting decreases the average uplink scheduling delay for the UEs and improves
user experience. However, the cell SRI capacity decreases.
The CellPucchAlgo.SriLowLoadThd parameter specifies the threshold for the low load state of SRI resources. The value range is 0 to 50, indicating the
number of UEs that can be admitted under the low load state. After the number of admitted UEs reaches the specified threshold, the low load state
changes to the medium load state. The SRI period for the next admitted UE will be configured based on the medium load state.
◾ For medium SRI loads:

If a UE requests a single-service connection, the SRI period for the UE is the same as that for the QCI of the service. If a UE requests a multi-service
connection, the SRI period for the UE is the minimum value among the SRI periods for all QCIs of the services on the UE.
Table 5-3 SRI periods for medium SRI loads
QCI SRI Period (ms)
3 5
1, 2, 5, 7, 65, 66, and 69 10
4, 6, 8, 9, and 70 20
◾ For high SRI loads:

Table 5-4 SRI periods for high SRI loads
QCI SRI Period (ms)
3 20
1, 2, 4, 5, 6, 7, 8, 9, 65, 66, 69, and 70 40
◾ For heavy SRI loads:

Table 5-5 SRI periods for heavy SRI loads
QCI SRI Period (ms)
3 40
1, 2, 4, 5, 6, 7, 8, 9, 65, 66, 69, and 70 80
A higher SRI load results in a larger SRI period set for a newly admitted UE.
The eNodeB does not adjust SRI periods for the admitted UEs that have been allocated SRI resources based on SRI loads.
If the PUCCHCfg.SriPeriodAdaptive parameter is set to QCIADAPTIVE(QCIADAPTIVE), SRI loads increase when more UEs access a cell. The SRI periods for
newly admitted UEs also increase. This increases SRI capacity but results in long average uplink scheduling delays for certain UEs.
• If the PUCCHCfg.SriPeriodAdaptive parameter is set to NOQCIADAPTIVE(NOQCIADAPTIVE), the SRI period is related only to the SRI load in the serving cell. The
eNodeB configures SRI periods for UEs in the serving cell merely based on SRI load status. The same cell load status indicates one SRI period.
RI Period
The CellPucchAlgo.SriAlgoSwitch parameter specifies the working mode for SRI period configuration.
The SriAdaptiveHoldForVoIPSW option of the CellPucchAlgo.SriAlgoSwitch parameter specifies the SRI period adaptation retainability during SRI resource adjustment of
voice UEs.
• If the SriAdaptiveHoldForVoIPSW option is selected, the SRI period of voice UEs during SRI resource adjustment is allocated based on adaptive loads. When the
number of UEs is small, the SRI period based on adaptive loads is less than the SRI long period that is fixedly allocated, increasing the MOS of voice UEs connected
during SRI adjustment.
• If the SriAdaptiveHoldForVoIPSW option is cleared, the SRI period remains fixedly allocated during SRI resource adjustment. This option takes effect only when the
PucchSwitch option of the PucchAlgoSwitch parameter is selected and the SriPeriodAdaptive parameter is set to a value other than OFF(Off).
The SriPeriodCfgOptSW option of the CellPucchAlgo.SriAlgoSwitch parameter specifies whether to optimize SRI period configuration.
• If the SriPeriodCfgOptSW option is selected, SRI periods are configured based only on the SRI resource usage in the cell. When CA and VoLTE are enabled, the
eNodeB is configured with more UEs with short SRI periods, PUCCH resources to be used increase, and available PUSCH resources decrease.
• If the SriPeriodCfgOptSW option is cleared, SRI periods are configured based on the usage for all of SRI, semi-persistent ACK, and dynamic ACK resources. When
CA and VoLTE are enabled, the eNodeB is configured with fewer UEs with short SRI periods, PUCCH resources to be used decrease, and available PUSCH
resources increase.
5.1.3 CQI, PMI, and RI
QI
CQI indicates downlink channel quality.

The eNodeB controls CQI reporting of UEs. A UE reports a CQI to the eNodeB periodically, or in event-triggered mode.
• CQIs reported periodically are sent to the eNodeB over a PUCCH or PUSCH. Use the PUSCH if the PUSCH has idle resources. Otherwise, use the PUCCH.
• CQIs reported in event-triggered mode are sent to the eNodeB over a PUSCH.
Event-triggered reporting takes precedence over periodic reporting if both are configured. The selection of periodic reporting and event-triggered reporting of CQIs is determined
by Huawei eNodeBs. For details, see MIMO Feature Parameter Description.
The CqiAdaptiveCfg.PucchPeriodicCqiOptSwitch parameter indicates whether to enable the optimization on CQI reporting periods and PUCCH resources for CQI reporting.
• If this parameter is set to ON(On), the eNodeB is configured with fewer UEs with short CQI reporting periods, PUCCH resources to be used decrease, and available
PUSCH resources increase.
• If this parameter is set to OFF(Off), the eNodeB is configured with more UEs with short CQI reporting periods, PUCCH resources to be used increase, and available
PUSCH resources decrease.
MI
A PMI indicates a precoding matrix. When closed-loop MIMO is enabled, the PMI is sent with the CQI.
To avoid interference between spatial channels, codewords are mapped onto different layers, and layered data is multiplied by a precoding matrix and mapped onto different
antenna ports for transmission. After transmission over spatial channels, the received signals are equivalent to a group of parallel signals without interference between them. For
details, see MIMO Feature Parameter Description.
RI indicates the rank of a spatial channel matrix. For details, see MIMO Feature Parameter Description.
Cyclic Shift Interval for the PUCCH

All PUCCH formats use cyclic shifts of a sequence in each symbol. Each RB can use multiple cyclic shift sequences. The number of cyclic shift sequences is determined by the
PUCCHCfg.DeltaShift parameter, which indicates a cyclic shift interval. The PUCCHCfg.DeltaShift parameter corresponds to , which is specified in section 5.4
"Physical uplink control channel" in 3GPP TS 36.211 V10.4.0.
• If this parameter is set to DS1_DELTA_SHIFT(ds1), is 1.

Under this setting, the multipath delay is relatively short, the normal CP can be used, and there is a large number of UEs using CDM on a PUCCH RB.

Under this setting, the multipath delay is relatively short, the normal CP can be used, and there is a medium number of UEs using CDM on a PUCCH RB.

Under this setting, the multipath delay is relatively long, the normal or extended CP can be used, and there is a small number of UEs using CDM on a PUCCH RB.

The LBBPd and UBBP boards support the PUCCHCfg.DeltaShift parameter set to any valid value. The LBBPc board does not support the PUCCHCfg.DeltaShift parameter set
to DS1_DELTA_SHIFT(ds1).
Dynamic PUCCH Resource Adjustment

The eNodeB dynamically adjusts PUCCH resources based on PUCCH resource load. By reducing the overhead, more resources can be used for PUSCH transmissions. By
increasing the PUCCH resources, more UEs can be admitted. The CellAlgoSwitch.PucchAlgoSwitch parameter specifies whether to enable dynamic PUCCH resource
adjustment.
• If the PucchSwitch option of the CellAlgoSwitch.PucchAlgoSwitch parameter is selected, the eNodeB adaptively increases or decreases PUCCH resources based
on PUCCH resource loads.
◾ If the PUCCH resource load is greater than a specified threshold, the eNodeB increases PUCCH resources to ensure that UEs successfully access a cell.
◾ If the PUCCH resource load is less than a specified threshold, the eNodeB decreases PUCCH resources to prevent a waste in uplink RBs due to large
PUCCH resource overheads, thereby increasing PUSCH capacity.
NOTE:
When the PucchSwitch option of this parameter is selected, PUCCH resources occupied by cells vary in inter-cell load imbalance scenarios, possibly resulting in
mutual interference between SRI, CQI, or ACK resources of different cells, and further affecting counters, such as the access delay and call drop rate.
• If the PucchSwitch option of the CellAlgoSwitch.PucchAlgoSwitch parameter is cleared, the number of RBs actually occupied by the PUCCH is calculated as
follows:
NPUCCH = PUCCHCfg.CqiRbNum + ceil{[(PUCCHCfg.NaSriChNum + DsNaChNum) * PUCCHCfg.DeltaShift]/(N_RS * N_CS)}
where
◾ The PUCCHCfg.CqiRbNum parameter specifies the number of RBs for CQIs. The PUCCHCfg.NaSriChNum parameter specifies the total number of code-
division multiplexed SRIs and ACKs to downlink semi-persistent scheduling.
◾ If the PUCCHCfg.CqiRbNum parameter is set to a small value, a small number of UEs can use periodic CQI reporting. When the traffic volume
exceeds the configured capacity, the network performance deteriorates.
◾ If the PUCCHCfg.NaSriChNum parameter is set to a small value, a small number of UEs can be scheduled in downlink semi-persistent
scheduling and a small number of UEs can be supported in a cell.
◾ If both PUCCHCfg.NaSriChNum and PUCCHCfg.CqiRbNum are set to large values, a large number of UEs can be supported in a cell.
However, a small number of PUSCH resources can be used, and therefore the uplink throughput is low.
If LOFD-001093 PUCCH Flexible Configuration is activated, the eNodeB adds 2 x PucchExtendedRBNum to the value of the
PUCCHCfg.CqiRbNum parameter when delivering the nRB-CQI IE of PUCCH cell-level parameters over the air interface.
In macro eNodeBs, the relationship of PUCCHCfg.NaSriChNum and PUCCHCfg.CqiRbNum with RACHCfg.PrachFreqOffset and
PUSCHCfg.hoppingoffset must be considered when PUCCHCfg.NaSriChNum and PUCCHCfg.CqiRbNum are set. The value of
RACHCfg.PrachFreqOffset must be greater than ceil(NPUCCH x 1/2), and the value of PUSCHCfg.hoppingoffset must be greater than ceil
(NPUCCH).
In micro eNodeBs, the relationship of PUCCHCfg.NaSriChNum and PUCCHCfg.CqiRbNum with RACHCfg.PrachFreqOffset must be
considered when PUCCHCfg.NaSriChNum and PUCCHCfg.CqiRbNum are set. The value of RACHCfg.PrachFreqOffset must be greater than
ceil(NPUCCH x 1/2).
◾ N_RS indicates the number of symbols used to transmit reference signals in format 1, 1a or 1b within one slot. In macro eNodeBs, if the normal CP is
used, the value of N_RS is 3; if the extended CP is used, the value of N_RS is 2. In micro eNodeBs, the value of N_RS is 3.
◾ N_CS indicates the maximum number of cyclic shifts for PUCCH format 1, 1a, or 1b. According to the protocol, N_CS has a fixed value 12.
◾ PucchExtendedRBNum indicates the number of extended PUCCH RBs. Set PucchExtendedRBNum to 0 if the PucchFlexCfgSwitch option of the
CellAlgoSwitch.PucchAlgoSwitch parameter is cleared.
◾ DsNaChNum indicates the number of code-division multiplexed ACKs to downlink dynamic scheduling.
◾ If the CellPdcchAlgo.PdcchSymNumSwitch parameter is set to OFF(Off), the value of DsNaChNum is set based on the value of
CellPdcchAlgo.InitPdcchSymNum. For details, see Table 5-6.
NOTE:
Adjusting the CellPdcchAlgo.InitPdcchSymNum parameter online is not recommended because this operation leads to conflicts between the
PUCCH and other channels and therefore deteriorates channel performance.
◾ If the CellPdcchAlgo.PdcchSymNumSwitch parameter is set to ON(On), see Table 5-6.

◾ If the cell bandwidth is 1.4 MHz (Macro), the value of DsNaChNum corresponds to the value 4 of
CellPdcchAlgo.InitPdcchSymNum.
◾ If the cell bandwidth is not 1.4 MHz (Macro), the value of DsNaChNum corresponds to the value 3 of
CellPdcchAlgo.InitPdcchSymNum.
Table 5-6 Mapping between the value of DsNaChNum and the number of PDCCH symbols in different channel bandwidths, where the
channel bandwidths of 1.4 MHz and 3 MHz apply to macro eNodeBs
Channel Bandwidth Number of PDCCH Symbols (Specified by DsNaChNum

CellPdcchAlgo.InitPdcchSymNum)
1.4 MHz (Normal CP) 2 2
3 4
4 6
1.4 MHz (Extended CP) 2 2
3 4
4 5
3 MHz 1 2
2 7
3 12
5 MHz 1 3
2 12
3 20
10 MHz 1 8
2 25

Channel Bandwidth Number of PDCCH Symbols (Specified by DsNaChNum

CellPdcchAlgo.InitPdcchSymNum)
3 41
15 MHz 1 12
2 37
3 62
20 MHz 1 17
2 50
3 84
PUCCH Resource Allocation Policy

PUCCHCfg.PucchAllocPolicy specifies the PUCCH resource allocation policy.
The RbPriorityModeSW option of the PUCCHCfg.PucchAllocPolicy parameter specifies whether resources on different RBs are used by preference during code channel
resource allocation.
• When the RbPriorityModeSW option is selected, the eNodeB preferentially uses resources on different RBs and evenly distributes UEs on all RBs during PUCCH
code channel resource allocation, thereby decreasing inter-bit interference on most UEs in a cell and improving PUCCH performance.
• When the RbPriorityModeSW option is cleared, the eNodeB uses each RB resource of the PUCCH wholly in sequence. UEs in the cell are mostly distributed on
RBs of the corresponding PUCCH format at the band edges. Therefore, UEs on the RBs have greater inter-bit interference.
It is recommended that the RbPriorityModeSW option be selected in big events. When the PucchSwitch option of the CellAlgoSwitch.PucchAlgoSwitch parameter is cleared
in big events, GUI settings of the PUCCHCfg.NaSriChNum and PUCCHCfg.CqiRbNum parameters take effect.
When the RbPriorityModeSW option is selected, the values of the PUCCHCfg.NaSriChNum and PUCCHCfg.CqiRbNum parameters apply to the LBBPd or UBBP. For details,
see Table 5-7. For example, when the bandwidth is 10 MHz or higher and the value of the Delta Shift parameter is ds1, the recommended values of PUCCHCfg.NaSriChNum and
PUCCHCfg.CqiRbNum are 121 and 4.
Table 5-7 Values of the PUCCHCfg.NaSriChNum and PUCCHCfg.CqiRbNum parameters
Condition PUCCHCfg.NaSriChNum PUCCHCfg.CqiRbNum
10 MHz, 15 MHz, or 20MHz ds1 121 4
ds2 67
5 MHz ds1 111 4
ds2 57
In addition, when the 3CC feature takes effect, you are advised to add 1 to the corresponding value of PUCCHCfg.CqiRbNum in Table 5-7. For the LBBPc, the recommended
value of PUCCHCfg.CqiRbNum is 3 and the value of PUCCHCfg.NaSriChNum is 5 subtracted from the corresponding value in the preceding table.
A smaller value of PUCCHCfg.NaSriChNum (for example, the default value 6) or PUCCHCfg.CqiRbNum may result in access failure, SCC addition failure, SPS configuration
failure, or DL throughput decrease of cells and UEs. A larger value reduces UL and DL throughput gains of cells and UEs.
PUCCH Flexible Configuration

This section describes the optional feature LOFD-001093 PUCCH Flexible Configuration.
When the PUCCH experiences severe interference caused by inter-RAT signal leakage, the access performance deteriorates and the downlink throughput decreases. PUCCH
flexible configuration reduces or even prevents this interference and therefore improves the access performance and increases the downlink throughput. In addition, the
frequency band originally reserved for the PUCCH can be used to schedule uplink data to reduce the decrease in the PUSCH throughput.
The PucchFlexCfgSwitch option of the CellAlgoSwitch.PucchAlgoSwitch parameter specifies whether to enable PUCCH flexible configuration:
• When the PucchFlexCfgSwitch option is cleared, the PUCCH is allocated RBs from the band edges. Assume that the band consists of 100 RBs (numbered from 0
to 99). Then, the PUCCH is allocated from RB 0 and RB 99.
• When the PucchFlexCfgSwitch option is selected, n RBs (n = PUCCHCfg.PucchExtendedRBNum) are moving from each of the band edges to the middle. The
original RBs are reserved for the PUSCH, and the PUCCH is allocated RBs from the (n + 1)th RB. Assume that the band consists of 100 RBs (numbered from 0 to
99) and the value of PUCCHCfg.PucchExtendedRBNum is 5. Then, the PUCCH is allocated RBs from RB 5 and RB 94. After RBs are reserved for the PUSCH,
maximum RBs required for the PUCCH are allocated from both edges in the remaining RBs. Then, the PRACH is allocated six continuous RBs from the start edge in
the remaining RBs, as shown in Figure 5-3.
Figure 5-3 Flexible channel configuration
In Figure 5-3, RBs from 0 to 4 and from 95 to 99 are reserved for the PUSCH. The PUCCH requires a maximum of four RBs. Therefore, the PUCCH is allocated RBs
from 5 to 6 and from 93 to 94 and the PRACH is allocated RBs from 7 to 12.
The PUCCHCfg.PucchExtendedRBNum parameter specifies the number of extended PUCCH RBs and can be set based on the amount of interference the PUCCH is
experiencing. Consider the following physical resources configurations when setting this parameter:
◾ Uplink channel bandwidth
◾ PRACH bandwidth
◾ Bandwidth for SRSs
◾ Number of PUCCH RBs
◾ Non-standard bandwidth
Table 5-8 lists the maximum number of extended PUCCH RBs for each channel bandwidth under the default physical resource configurations. If this parameter is set
to a value larger than the recommended value, the available channel bandwidth cannot meet the requirements of the preceding physical resource configurations and
the cell cannot be set up or will be deactivated.
If LOFD-001051 Compact Bandwidth is enabled, the number of punctured RBs must be deducted from the maximum number of extended PUCCH RBs. Compared
with values in Table 5-8, the maximum number of extended PUCCH RBs changes based on the number of punctured RBs.
Table 5-8 Maximum number of extended PUCCH RBs for each channel bandwidth under the default physical resource configurations
Channel Bandwidth 5 MHz 10 MHz 15 MHz 20 MHz
Maximum Number of Extended 2 20 14 24

PUCCH RBs
1 10 7 12

Value of
PUCCHCfg.PucchExtendedRBNum
NOTE:
If the default physical resource configurations are not used, the maximum numbers of extended PUCCH RBs are different from the numbers listed previously and can
be calculated based on the changed physical resource configurations.
The step of the PUCCHCfg.PucchExtendedRBNum parameter is 2. Therefore, the maximum number of RBs in Table 5-8 is twice the value of
PUCCHCfg.PucchExtendedRBNum parameter. For example, the maximum configuration of the PUCCHCfg.PucchExtendedRBNum parameter for the 5 MHz
bandwidth is 1.
6 SRS Resource Management
In the LTE system, a UE periodically sends SRSs across the entire PUSCH frequency band as much as possible. After receiving the SRSs, the eNodeB processes them and
measures SINRs and time synchronization values on subcarriers in the PUSCH frequency band for each UE.
• SINRs are used for frequency selective scheduling of uplink channels, link adaptation, and power control.
• Time synchronization values are used for uplink time synchronization of UEs.
The SRSCfg.SrsCfgInd parameter specifies whether SRS resources are configured for UEs:
• If this parameter is set to BOOLEAN_TRUE(True), SRS resources need to be configured for UEs in a cell. Compared with PUSCH demodulation reference signals
(DMRSs), SRSs reduce the PDCCH overhead of PUSCH scheduling and therefore increase the downlink capacity. To use open-loop (OL) and closed-loop (CL)
MIMO adaptation or uplink multi-user MIMO (MU-MIMO), it is recommended that SRS resources be configured.
• If this parameter is set to BOOLEAN_FALSE(False), SRS resources are not configured for UEs in a cell. As there is no SRS overhead, the uplink capacity
increases. However, SRS-dependent features such as frequency selective scheduling and virtual MIMO cannot achieve better performance.
When an LBBPc board supports less than four receive antennas, the SRSCfg.SrsCfgInd parameter can be set to BOOLEAN_TRUE(True) or BOOLEAN_FALSE(False). When
this parameter is set to BOOLEAN_FALSE(False), virtual MIMO is not supported. When the LBBPc board supports four or more receive antennas or LOFD-001031 Extended
CP is activated, the SRSCfg.SrsCfgInd parameter can be set only to BOOLEAN_TRUE(True). If an LBBPd board is used, this parameter can be set to either BOOLEAN_TRUE
(True) or BOOLEAN_FALSE(False).
The SRSCfg.FddSrsCfgMode parameter must be set to specify the SRS resource allocation mode for macro LTE FDD cells when the SRSCfg.SrsCfgInd parameter is set to
BOOLEAN_TRUE(True).
• If the SRSCfg.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 the SRSCfg.FddSrsCfgMode parameter is set to ADAPTIVEMODE(Adaptive Mode), the parameter value applies only to macro cells established on an LBBPd or a
UBBP, and 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 SRSCfg.SrsSubframeCfg, CellAlgoSwitch.SrsAlgoSwitch, CellSrsAdaptiveCfg.SrsPeriodAdaptive, and
CellSrsAdaptiveCfg.UserSrsPeriod do not take effect. The value ADAPTIVEMODE(Adaptive Mode) is recommended in heavy-traffic scenarios where there is a
large number of UEs in the cell. If the bandwidth is 5 MHz or smaller, it is recommended that the TimeAlignmentTimer.TimingResOptSwitch parameter be set to ON
(On).
SRS-related Concepts
6.1.1 SRS Subframe Configuration Index

An SRS subframe configuration index defines a subframe period and a subframe offset, which are contained in one set of subframe configuration data, as listed in the first
column of Table 6-1.
6.1.2 SRS Subframe Period

SRSs are transmitted every T ms, where T indicates the SRS subframe period.
6.1.3 SRS Subframe Offset

The SRS subframe offset indicates the position (subframe number) where SRSs are transmitted in the time domain within a certain time period. SRSs are always transmitted in
the last symbol of the subframe.
For details about these concepts, see section 5.5.3 "Sounding reference signal" in 3GPP TS 36.211 V10.4.0.
Cell-specific SRS
6.2.1 Cell-specific SRS Subframe

A cell-specific SRS subframe indicates time-domain resources that can be configured for all UEs in a cell.
onfiguration
Cell-specific SRS subframe configurations in frequency division duplex (FDD) mode are defined in section 5.3.3 "Sounding reference signal" in 3GPP TS 36.211 V10.4.0, as
listed in Table 6-1.
Table 6-1 Cell-specific SRS subframe configuration in FDD mode
Cell-specific SRS Subframe Configuration Cell-specific SRS Subframe Configuration Index Subframe Period (ms) Subframe Offset
Index (Binary)
0 0000 1 {0}
1 0001 2 {0}
2 0010 2 {1}
3 0011 5 {0}
4 0100 5 {1}
5 0101 5 {2}
6 0110 5 {3}
7 0111 5 {0, 1}
8 1000 5 {2, 3}
9 1001 10 {0}
10 1010 10 {1}

Cell-specific SRS Subframe Configuration Cell-specific SRS Subframe Configuration Index Subframe Period (ms) Subframe Offset
Index (Binary)
11 1011 10 {2}
12 1100 10 {3}
13 1101 10 {0, 1, 2, 3, 4, 6, 8}
14 1110 10 {0, 1, 2, 3, 4, 5, 6, 8}
15 1111 Inf N/A
When the SRSCfg.FddSrsCfgMode parameter is set to DEFAULTMODE(Default Mode), the SRSCfg.SrsSubframeCfg parameter is used to specify the index for a cell-specific
SRS subframe configuration, as listed in the first column of Table 6-1.
NOTE:
• When the SRSCfg.SrsSubframeCfg parameter is not set to the default value, the number of UEs in a cell cannot reach the maximum allowed value due to the
discontinuity of the SRS subframes configured in the cell.
• In FDD+TDD mixed networking scenarios, when the SrsSubframeRecfgOptSwitch option of the eNBCellRsvdPara.RsvdSwPara3 parameter is selected, you are
advised not to set SRSCfg.SrsSubframeCfg to SC14(14).
A cell-specific SRS subframe configuration index corresponds to a specific combination of subframe period and subframe offset. In FDD mode for example, if the
SRSCfg.SrsSubframeCfg parameter is set to SC5(5), the cell-specific SRS subframe period is 5 ms and the subframe offset is 2. That is, cell-specific SRSs are transmitted on
subframe 2 every 5 ms.
namic Adjustment
The eNodeB can dynamically adjust cell-specific SRS subframes based on cell loads.
• If cell loads rise, the eNodeB increases time-domain resources for SRSs.
• If cell loads drop, the eNodeB decreases time-domain resources for SRSs to reduce PUSCH resource consumption. The eNodeB increases resource allocation
success rates by reshuffling bandwidth fragments.
When the SRSCfg.FddSrsCfgMode parameter is set to DEFAULTMODE(Default Mode), the CellAlgoSwitch.SrsAlgoSwitch parameter is used to determine whether to enable
dynamic adjustment to cell-specific SRS subframe configuration:
• If the SrsSubframeRecfSwitch option of the CellAlgoSwitch.SrsAlgoSwitch parameter is selected, the eNodeB adaptively adjusts SRS subframe configuration
based on cell loads.
• If the SrsSubframeRecfSwitch option of the CellAlgoSwitch.SrsAlgoSwitch parameter is cleared, the eNodeB always uses the SRS subframe configuration
specified by the SRSCfg.SrsSubframeCfg parameter to allocate time-frequency resources for SRSs.
• If the SRSCfg.SrsSubframeCfg parameter is not set to a default value and the SRS subframes indicated by this parameter cannot be dynamically adjusted, dynamic
adjustment to cell-specific SRS subframes does not take effect and the actual maximum number of UEs supported by a cell may not reach the specification even
though the SrsSubframeRecfSwitch option of the CellAlgoSwitch.SrsAlgoSwitch parameter is selected.
6.2.2 Cell-specific SRS Bandwidth

A cell-specific SRS bandwidth configuration indicates a set of types of SRS bandwidth that can be allocated to all UEs in a cell. For details, see section 5.3.3 Sounding reference
signal in 3GPP TS 36.211 V10.4.0.
3GPP TS 36.211 V10.4.0 defines a maximum of four levels of SRS bandwidths. Therefore, the system supports a maximum of four types of SRS bandwidths. Figure 6-1 shows a
cell-specific SRS bandwidth configuration tree. An SRS bandwidth can be 32 RBs, 16 RBs, 8 RBs, or 4 RBs.
Figure 6-1 Cell-specific SRS bandwidth configuration tree
Table 6-2 through Table 6-5 list cell-specific SRS bandwidth configurations for different uplink bandwidths.
Table 6-2 Cell-specific SRS bandwidth configuration (6 RBs < Uplink bandwidth ≤ 40 RBs)
SRS Bandwidth b=0 b=1 b=2 b=3

Configuration Index
mSRS,b Nb mSRS,b Nb mSRS,b Nb mSRS,b Nb
0 36 1 12 3 4 3 4 1
1 32 1 16 2 8 2 4 2
2 24 1 4 6 4 1 4 1
3 20 1 4 5 4 1 4 1
4 16 1 4 4 4 1 4 1
5 12 1 4 3 4 1 4 1
6 8 1 4 2 4 1 4 1
7 4 1 4 1 4 1 4 1
SRS Bandwidth Configuration b = 0 b=1 b=2 b=3

Index
0 48 1 24 2 12 2 4 3
1 48 1 16 3 8 2 4 2
2 40 1 20 2 4 5 4 1
3 36 1 12 3 4 3 4 1
4 32 1 16 2 8 2 4 2

5 24 1 4 6 4 1 4 1
6 20 1 4 5 4 1 4 1
7 16 1 4 4 4 1 4 1

Index
0 72 1 24 3 12 2 4 3
1 64 1 32 2 16 2 4 4
2 60 1 20 3 4 5 4 1
3 48 1 24 2 12 2 4 3
4 48 1 16 3 8 2 4 2
5 40 1 20 2 4 5 4 1
6 36 1 12 3 4 3 4 1
7 32 1 16 2 8 2 4 2

Index
0 96 1 48 2 24 2 4 6
1 96 1 32 3 16 2 4 4
2 80 1 40 2 20 2 4 5
3 72 1 24 3 12 2 4 3
4 64 1 32 2 16 2 4 4
5 60 1 20 3 4 5 4 1
6 48 1 24 2 12 2 4 3
7 48 1 16 3 8 2 4 2
NOTE:
In the preceding tables:
• b: indicates the level of the bandwidth tree. b=0 indicates the top layer in Figure 6-1 when the SRS bandwidth is 32 RBs. This rule applies to other values.
• mSRS,b: indicates the SRS bandwidth on level b.
• Nb: indicates the number of leaf nodes on level b. The number is a multiple of the SRS bandwidth on level (b-1) relative to the SRS bandwidth on level b.
The channel bandwidth determines cell-specific SRS bandwidth configuration that a cell uses. The SRSCfg.CellSrsBandwidthCfg parameter specifies the current cell-specific
SRS bandwidth configuration.
Based on the cell bandwidth, the eNodeB selects a cell-specific SRS bandwidth configuration from Table 6-2 through Table 6-5.
UE-specific SRS
6.3.1 UE-specific SRS Subframe

A UE sends SRSs on a subframe. The subframe is called a UE-specific SRS subframe.
UE-specific SRS periods of 2 ms, 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, 160 ms, and 320 ms are defined in section 8.2 "UE sounding procedure" in 3GPP TS 36.213 V10.4.0. UE-
specific SRS subframes are a subset of cell-specific SRS subframes because UEs must transmit SRSs on configured cell-specific SRS subframes. UE-specific SRS periods and
subframe offsets are jointly coded. The 10-bit ISRS parameter indicates UE-specific SRS period and subframe offset configuration. Table 6-6 lists UE-specific SRS subframe
configuration in FDD mode.
Table 6-6 UE-specific SRS subframe configuration in FDD mode
UE-specific SRS Subframe Configuration Index ISRS Subframe Period (ms) Subframe Offset
0–1 2 ISRS
2–6 5 ISRS – 2
7–16 10 ISRS – 7
17–36 20 ISRS – 17
37–76 40 ISRS – 37
77–156 80 ISRS – 77
157–316 160 ISRS – 157
317–636 320 ISRS – 317
637–1023 Reserved Reserved
Configuring the UE-specific SRS subframe period and offset requires 10 bits. One additional bit is required to indicate a single SRS transmission or a periodic SRS transmission.
UE-specific SRS subframe periods and offsets are jointly configured in RRC signaling messages to reduce signaling overheads.
6.3.2 UE-specific SRS Period Adaptation

The eNodeB can adaptively adjust the SRS period for UEs based on SRS loads. This way is called UE-specific SRS period adaptation.

The settings of the parameters CellSrsAdaptiveCfg.SrsPeriodAdaptive and CellSrsAdaptiveCfg.UserSrsPeriod take effect only when the SRSCfg.FddSrsCfgMode parameter is
set to DEFAULTMODE(Default Mode).
The CellSrsAdaptiveCfg.SrsPeriodAdaptive parameter determines whether to enable or disable SRS period adaptation.
• If this parameter is set to ON(On), the eNodeB adaptively adjusts the SRS period for newly admitted UEs based on SRS loads. SRS resources may be normally
loaded, slightly congested, or heavily congested. A high SRS load results in a long SRS period set for newly admitted UEs.
◾ When the SRS resources are normally loaded, the eNodeB sets the SRS period to 10 ms for newly admitted UEs. This reduces the interval for updating
SRS measurements, improving user experience. However, the cell SRS capacity decreases.
◾ When the SRS resources are slightly congested, the eNodeB sets the SRS period to 20 ms for newly admitted UEs. This allows more UEs to access the
cell. However, user experience becomes less satisfactory.
◾ When the SRS resources are heavily loaded, the eNodeB sets the SRS period to 40 ms for newly admitted UEs. This allows more UEs to access the cell
and leads to a compromise between cell capacity and performance.
◾ The eNodeB does not adjust SRS periods for the admitted UEs that have been allocated SRS resources.
• If this parameter is set to OFF(Off), the eNodeB sets a fixed SRS period for newly admitted UEs. The CellSrsAdaptiveCfg.UserSrsPeriod parameter specifies the
fixed SRS period, which can be set to 5, 10, 20, 40, 80, 160, or 320 ms. If a short fixed SRS period is configured, the maximum number of UEs using SRS in a cell
may not reach the maximum allowed value. If a long fixed SRS period is configured, the maximum number of such UEs in a cell increases but the performance of
features depending on SRS measurement deteriorates. If the CellSrsAdaptiveCfg.UserSrsPeriod parameter is set to 80, 160, or 320 ms, uplink timing performance
deteriorates and UE out-of-synchronization occurs. In this situation, you are advised to reconfigure the CellSrsAdaptiveCfg.UserSrsPeriod parameter with
parameters in the TimeAlignmentTimer MO for the Uplink Timing Control feature.
6.3.3 UE-specific SRS Bandwidth

A UE sends SRSs within a bandwidth. The bandwidth is called a UE-specific SRS bandwidth. UE-specific SRS bandwidths are obtained from cell-specific SRS bandwidth
configurations, corresponding to b = 0, 1, 2, and 3.
SRS and HARQ ACK Processing

To prevent conflicts between SRSs and PUCCH HARQ ACKs of a UE, during conflicts, the eNodeB discards the SRSs, which results in the performance deterioration of
features depending on the SRS function, or shortens the HARQ ACKs and SRIs, which results in the deterioration of PUCCH demodulation performance.
• If the SRSCfg.AnSrsSimuTrans parameter is set to BOOLEAN_TRUE(True):

◾ The UE can simultaneously send an SRS and a PUCCH HARQ ACK.
◾ The UE can send PUCCH HARQ ACKs or SRIs in shortened formats.
◾ The UE does not discard SRSs.
• If the SRSCfg.AnSrsSimuTrans parameter is set to BOOLEAN_FALSE(False):

◾ The UE cannot simultaneously send an SRS and a PUCCH HARQ ACK.
◾ The UE can send only PUCCH HARQ ACKs or SRIs.
◾ The UE discards SRSs.
SRS Multiplexing
An SRS multiplexing mode determines how UEs transmit SRSs using time-frequency resources.
6.5.1 FDM
The FDM mode allows UEs to transmit SRSs using different frequencies. FDM is classified into localized frequency division multiplexing (LFDM) and distributed frequency
division multiplexing (DFDM).
• LFDM
Different UEs use different RBs for continuously transmitting SRSs.
• DFDM
Different UEs use discontinuous subcarriers for transmitting SRSs. If the repetition factor (RPF) is 2, SRSs are transmitted only on even-numbered subcarriers or
odd-numbered subcarriers. SRSs have a comb transmission interval, which is specified by the comb parameter. If the comb parameter is set to 0, SRSs are
transmitted on even-numbered subcarriers. If the comb parameter is set to 1, SRSs are transmitted on odd-numbered subcarriers.
6.5.2 CDM
The CDM mode allows SRSs with the same subframe, bandwidth, and comb value to occupy the same time-frequency position. Codewords use cyclic shift sequences
generated from the same Zadoff-Chu sequence. CDM supports a maximum of eight cyclic shift sequences.
SRS Frequency Hopping

SRS frequency hopping enables a UE to transmit SRSs on a small frequency band at one time and to transmit SRSs on another frequency band at the next time. In this way,
the eNodeB achieves sounding on the entire channel bandwidth. SRS frequency hopping implements channel quality measurements in the entire channel bandwidth by using a
small sounding bandwidth.
7 Related Features
This chapter describes the required features, mutually exclusive features, and affected features of physical channel resource management.
LBFD-002003 Physical Channel Management
erequisite Features
None
None
pacted Features
None
LBFD-070107 PDCCH Utilization Improvement
erequisite Features
None
None

pacted Features
None
LOFD-001093 PUCCH Flexible Configuration
erequisite Features
None
Function Name Description
Uplink ICIC and Uplink Frequency Hopping N/A
pacted Features
SRS Bandwidth Configuration PUCCH flexible configuration impacts the SRS bandwidth configuration and accordingly the uplink capability.
LOFD-001051 Compact Bandwidth When the Compact Bandwidth feature is enabled, the maximum number of extended PUCCH RBs changes
based on the number of punctured RBs.
LAOFD-110203 ePDCCH (Trial)
erequisite Features
None
LEOFD-111302 Flexible Bandwidth based on Overlap Carriers • When two Double Deck cells need to support any of non-
standard bandwidths 5.7 MHz, 7.3 MHz, 7.6 MHz, 8.6 MHz,
and 8.9 MHz, ePDCCH cannot be enabled for them.
• When Double Deck cells with a standard bandwidth 3 MHz
need to support any of non-standard bandwidths 4 MHz, 12.2
MHz, and 17.1 MHz, ePDCCH cannot be enabled for them.
• When Double Deck cells with a standard bandwidth 10 MHz
need to support either of non-standard bandwidths 27.6 MHz
and 28.5 MHz, ePDCCH cannot be enabled for them.
pacted Features
CSPC You are advised not to use ePDCCH with these functions because using the
ePDCCH feature may reduce expected gains of the preceding interference
coordination techniques.
ICIC
NOTE:
After ePDCCH is enabled, RBs of ePDCCH are included in RB usage calculation for features
DL CoMP that are related to the calculation and described in Inter-RAT Mobility Load Balancing Feature
Parameter Description, Intra-RAT Mobility Load Balancing Feature Parameter Description,
Admission and Congestion Control Feature Parameter Description, and SFN Feature Parameter
GLDSS Description. However, this has no impact on these features.
8 Network Impact
This chapter describes the network impact of physical channel resource management.
LBFD-002003 Physical Channel Management
stem Capacity
• PHICH
The PHICH duration and the number of PHICH groups impact the downlink capacity. A longer PHICH duration or a larger number of PHICH groups lead to higher
PHICH resource overhead and accordingly lower downlink capacity.
• PDCCH
◾ The number of symbols occupied by the PDCCH impacts the downlink capacity. If the PDCCH occupies a larger number of symbols, the PDCCH
resource overhead is higher. As a result, the downlink capacity is lower.
◾ PDCCH aggregation level adaptation and closed-loop adjustment impact both uplink and downlink capacities. The two functions determine the PDCCH
aggregation level for the eNodeB, and the accuracy of the PDCCH aggregation level impacts the PDCCH demodulation performance. Higher accuracy
leads to higher demodulation performance and accordingly higher uplink and downlink capacities.
◾ CCE ratio adaptation impacts both uplink and downlink capacities. The CCE ratio determines the ratio of the number of uplink CCEs to the number of
downlink CCEs. When the allocated CCEs are less than the required CCEs, the system capacity is reduced.
• PUCCH
The periods for sending CQIs and SRIs on the PUCCH impact downlink user experience and uplink capacity. Shorter periods lead to better user experience but
higher PUCCH resource overhead and accordingly lower uplink capacity.
• SRS
SRS resource configuration impacts the uplink capacity. A shorter SRS period leads to better user experience. If a larger number of UEs are configured with SRSs,
the PUSCH resource overhead is higher. As a result, the uplink capacity becomes lower.
When SRS parameters for an LBBPc or PUCCH parameters are not set to the default values, the actual maximum number of UEs supported by a cell varies and may not reach
the maximum allowed value.

twork Performance
• PHICH
The number of PHICH groups impacts the PHICH demodulation performance. A larger number of multiplexed UEs in each PHICH group leads to lower PHICH
demodulation performance and probably more uplink data transmission failures.
• PDCCH
PDCCH symbol adaptation enables the eNodeB to use PDCCH symbols effectively and therefore achieves optimum uplink and downlink performance. PDCCH
aggregation level adaptation and closed-loop adjustment ensure the PDCCH demodulation performance and therefore increase the cell throughput and enhance the
edge coverage. When the CellPdcchAlgo.PdcchCapacityImproveSwitch parameter is set to ON(On), the PDCCH power is increased for UEs whose CCE allocation
fails and the CCE aggregation level is decreased to reallocate CCEs to the UEs. This decreases the average aggregation level of the cell and improves the PDCCH
capacity and CCE allocation success rate, thereby increasing the cell throughput.
When the CellPdcchAlgo.AggLvlSelStrageForDualCW parameter is set to STRATEGYBASEDONCOVERAGE(Coverage-based Selection Strategy), the average
PDCCH aggregation level increases and the PDCCH demodulation performance improves in dual-codeword scenarios. However, the number of symbols occupied
by the PDCCH may increase. As a result, both the cell throughput and the number of UEs that can be supported by the PDCCH may decrease.
• PUCCH
PUCCH SRI configuration impacts uplink user experience. A shorter SRI period leads to better user experience, for example, shorter delays. CQI and HARQ ACK
configuration impacts downlink performance. A shorter CQI period leads to better user experience brought by the downlink adaptive modulation and coding (AMC).
If the prioritized RB mode is selected for the PUCCH resource allocation policy, the CPU load of the baseband processing unit may increase.
• SRS
SRS resource configuration impacts uplink AMC and timing accuracy. A shorter SRS period leads to better user experience brought by the uplink AMC and more
accurate timing. The introduction of the SRS increases system resource consumption and decreases system capacity.
LBFD-070107 PDCCH Utilization Improvement
stem Capacity
This feature reduces the CCE overhead and improves the uplink and downlink CCE allocation success rates and the number of UEs scheduled in each TTI without affecting
network coverage, thereby improving the system capacity.
twork Performance
Based on different RB and CCE usage, this feature has the following impact on network performance:
• Low average RB usage and unlimited CCE usage

In such a lightly-loaded network, using this feature does not increase cell throughput. Most services on the live network are burst services. This feature probably
decreases the number of PDCCH symbols and improves downlink user-perceived rates, but brings no gains to uplink user-perceived rates.
• Full RB usage (greater than 95%) and unlimited CCE usage
In this scenario, the CCE usage is low (for example, less than 40%). This feature improves downlink user-perceived rates, but brings no gains to the uplink.
• Full RB usage (greater than 95%) and high CCE usage (greater than 60%)
This feature does not bring positive gains in this scenario. Most scheduled UEs added in this scenario are CEUs, which causes low spectral efficiency. As a result,
user-perceived rates and cell rates decrease in the downlink or uplink with full RB usage.
• The uplink or downlink RB usage is not full due to limited CCE resources
In such a heavily-loaded network, CCEs become insufficient, followed by an insufficiency of RBs. This feature increases the number of UEs to be scheduled and
improves the uplink and downlink RB usage.
Assume that the downlink RB usage is full but the uplink RB usage is not. After the feature is activated, the eNodeB schedules more UEs in the uplink and increases
the RB usage in the uplink. The downlink MCS index of added uplink scheduled UEs is low, thereby increasing the number of downlink response packets and
decreasing the average downlink throughput. However, it increases uplink capacity.
NOTE:
Several factors may increase uplink small packets. For example, if most of the increased uplink UE scheduling times caused by PDCCH capacity improvement are
for small packet UEs, the number of small packets increases. The downlink throughput improvement increases the number of uplink TCP response packets, thereby
increasing the number of small packets.
LOFD-001093 PUCCH Flexible Configuration
stem Capacity
PUCCH flexible configuration reduces the interference to the PUCCH when the uplink band edges experience severe interference. With PUCCH flexible configuration, the
downlink CQIs and RIs measured by UEs can be reported to eNodeBs in real time, improving downlink performance.
twork Performance
PUCCH flexible configuration improves the PUCCH coverage and ensures the uplink and downlink performance when the uplink band edges experience severe interference.
However, RB extension due to PUCCH flexible configuration causes the PUSCH resources to be discontinuous and may lower the uplink resource usage.
LAOFD-110203 ePDCCH (Trial)
stem Capacity
This feature increases the control channel capacity when PDCCH resources are insufficient and PRB resources are sufficient.
twork Performance
In a heavily loaded network where CCEs are insufficient but RBs are sufficient, this feature increases control channel resources, decreases CCE congestion, and improves the
PDCCH allocation success rate, thereby increasing the number of scheduled UEs and RB usage. Therefore, this feature improves cell throughput and user-perceived rates. The
cell downlink throughput is expected to increase by 3% and uplink and downlink user-perceived rates are expected to increase by 5%.
9 Engineering Guidelines for PHICH Resource Management
When to Use
The eNodeB performs PHICH resource management by default and allocates PHICH resources according to 3GPP specifications.
N/A
Planning
N/A
Deployment

9.4.1 Requirements
perating Environment
None
ansmission Networking
None
cense
None
9.4.2 Precautions
Do not reconfigure the PHICHCFG.PhichDuration or PHICHCFG.PhichResource parameter while a cell is running. Otherwise, ongoing services in the cell will be interrupted.

• User-defined: parameter values set by users.
quired Data
The following table describes the parameters that must be set in the PHICHCfg MO to configure the PHICH.
PHICH duration PHICHCfg.PhichDuration This parameter specifies the type of the PHICH duration. If this parameter is set to Network plan
NORMAL, the number of OFDM symbols occupied by the PDCCH is automatically (negotiation not
adjusted. The value NORMAL is recommended. required)
PHICH resource PHICHCfg.PhichResource This parameter specifies a coefficient that is used to calculate the resources used by Network plan
the PHICH for the cell. The value ONE is recommended. (negotiation not
required)
None

This feature can be activated for a single eNodeB or a batch of eNodeBs on the CME. For detailed operations, see CME-based Feature Configuration.

On the U2000 client, run the MOD PHICHCFG command to configure the PHICH duration and PHICH resource.

MOD PHICHCFG:LOCALCELLID=0,PHICHDURATION=NORMAL,PHICHRESOURCE=ONE;

To check whether PHICH parameter settings take effect, perform the following steps:
NOTE:
Anonymization has been performed on Uu interface tracing tasks, and therefore no security risk exists.
1. Run the LST PHICHCFG command on the U2000 client to check the values of PHICH duration and PHICH resource for a normally activated cell. Then, record the
values.
2. On the U2000 client, choose Monitor > Signaling Trace > Signaling Trace Management. In the navigation tree on the left of the Signaling Trace Management
window, choose Trace Type > LTE > Application Layer > Uu Interface Trace to start Uu signaling tracing in the cell.
3. Deactivate the cell, and activate the cell again. Check the values of the information elements (IEs) phich-Duration and phich-Resource in the first
RRC_MASTER_INFO_BLOCK message traced on the Uu interface.
If the values of phich-Duration and phich-Resource are the same as the values of PHICH duration and PHICH resource recorded in 1, respectively, the parameter
settings take effect.

Figure 9-1 RRC_MASTER_INFO_BLOCK message
N/A
9.4.6 Deactivation


N/A

N/A
PHICH Monitoring
N/A
The PHICH demodulation performance depends on PHICH resource management and PHICH power control. Dynamic power adjustment for the PHICH is disabled (that is, the
PhichInnerLoopPcSwitch option of the CellAlgoSwitch.DlPcAlgoSwitch parameter is cleared) by default, and static power adjustment is used instead.
If the PHICH demodulation performance is poor, for example, when severe interference occurs in the downlink, you are advised to perform the following steps:
1. Adjust the PHICH power.

For detailed instructions, see Power Control Feature Parameter Description.
• If the PHICH demodulation performance improves, no further operation is required.
• If the PHICH demodulation performance does not improve, go to 2.
2. Adjust the PHICH parameter.

Increase the number of PHICH groups and change the value of the PHICHCFG.PhichDuration parameter to EXTENDED.
NOTICE:
After this adjustment, the downlink capacity of the cell may decrease because PDCCH symbol adaptation cannot work.
Possible Issues
N/A
10 Engineering Guidelines for PDCCH/ePDCCH Resource Management
1 When to Use
DCCH Symbol Adaptation
PDCCH symbol adaptation is enabled by default. It is recommended that this function be disabled in ultra-high-speed mobility scenarios and enabled in other scenarios.
Enhanced PDCCH symbol adaptation is recommended if frequency selective scheduling is enabled. For details about frequency selective scheduling, see Scheduling Feature
DCCH Aggregation Level Adaptation
PDCCH aggregation level adaptation is enabled by default. No manual operation is required for parameter setting.

osed-Loop Adjustment to the PDCCH Aggregation Level
Closed-loop adjustment to the PDCCH aggregation level is enabled by default. It is recommended that this function be used.
CE Ratio Adaptation
CCE ratio adaptation is enabled by default. It is recommended that this function be used.
DCCH Utilization Improvement
It is recommended that this feature be enabled except when the RB usage is excessively high (for example, greater than 95%) and the CCE usage is high (for example, greater
than 60%).
DCCH
The ePDCCH feature is disabled by default. It is recommended that ePDCCH be enabled only when PDCCH resources are limited, PRB resources are sufficient, and UEs
supporting ePDCCH exist in a cell.
You are not advised to use ePDCCH with CSPC, ICIC, DL CoMP, or GSM and LTE dynamic spectrum sharing. Using the ePDCCH feature may reduce expected gains of the
preceding interference coordination techniques.
2 Required Information
In external CHRs, obtain the number of UEs supporting ePDCCH in a cell. If a large number of UEs supporting ePDCCH exist, CCE usage is high, and PRB usage is low, you
can enable the LAOFD-110203 ePDCCH (Trial) feature.
3 Planning
N/A
4 Deployment
10.4.1 Requirements
Before PDCCH symbol adaptation can be enabled, the PHICHCFG.PhichDuration parameter must be set to NORMAL.
None
cense
None
10.4.2 Precautions
None

• Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment
quired Data
The following table describes the parameters that must be set in the CellPdcchAlgo MO to configure the PDCCH aggregation level, CCE ratio adaptation, initial number of
PDCCH symbols, PDCCH symbol adaptation, and closed-loop adjustment to the PDCCH aggregation level.
SignalCongregateLevel CellPdcchAlgo.ComSigCongregLv This parameter specifies the PDCCH aggregation level. The value Network plan
CONGREG_LV4 is recommended for decreasing the usage of CCEs by (negotiation not
common control signaling. required)
Cce Ratio Adjust CellPdcchAlgo.CceRatioAdjSwitch This parameter specifies whether to enable CCE/ECCE ratio adaptation Network plan
Switch for the PDCCH/ePDCCH. The value ON(On) is recommended. (negotiation not
required)
PDCCH Initial Symbol CellPdcchAlgo.InitPdcchSymNum This parameter specifies the number of OFDM symbols initially Network plan
Number occupied by the PDCCH. If the CellPdcchAlgo.PdcchSymNumSwitch (negotiation not
parameter is set to ON(On), the value 1 is recommended for required)
CellPdcchAlgo.InitPdcchSymNum. If the
CellPdcchAlgo.PdcchSymNumSwitch parameter is set to OFF(Off), the
value 4 is recommended for the 1.4 MHz bandwidth. For other
bandwidths, the value 3 is recommended.
PDCCH Symbol CellPdcchAlgo.PdcchSymNumSwitch This parameter specifies whether to enable dynamic adjustment to the Network plan
Number Adjust Switch number of OFDM symbols occupied by the PDCCH. In non-high-speed (negotiation not
scenarios, the value ECFIADAPTIONON(Enhanced CFI Adaption On) required)
is recommended. In other scenarios, the value OFF is recommended.
PDCCH Aggregation CellPdcchAlgo.PdcchAggLvlCLAdjustSwitch This parameter specifies whether to enable closed-loop adjustment to Network plan
Level CL Switch the PDCCH/ePDCCH aggregation level. The value ON(On) is (negotiation not
recommended. required)
Aggregation Level CellPdcchAlgo.AggLvlSelStrageForDualCW This parameter specifies the policy for selecting a PDCCH aggregation Network plan
Strategy for Dual level in dual-codeword scenarios. Set the parameter to (negotiation not
Codewords STRATEGYBASEDONCAPACITY(Capacity-based Selection required)
Strategy) or STRATEGYBASEDONCOVERAGE(Coverage-based
Selection Strategy) as required.
PDCCH Capacity CellPdcchAlgo.PdcchCapacityImproveSwitch This parameter specifies whether to enable optimization on Network plan
Improve Switch PDCCH/ePDCCH capacity expansion. The value OFF(Off) is (negotiation not
recommended. required)
PDCCH Initial Cce CellPdcchAlgo.PdcchInitialCceAdjustValue This parameter specifies the adjustment value of the PDCCH initial
Adjustment Value aggregation level.


Network plan
(negotiation not
required)
PDCCH Max Code CellPdcchAlgo.PdcchMaxCodeRate This parameter specifies the maximum coding rate on the Network plan
Rate PDCCH/ePDCCH. If the coding rate on the PDCCH/ePDCCH exceeds (negotiation not
the value of this parameter, the PDCCH/ePDCCH aggregation level required)
needs to be increased.
UL PDCCH Alloc CellPdcchAlgo.UlPdcchAllocImproveSwitch This parameter specifies the policy for improving the uplink PDCCH Network plan
Improve Switch allocation success rate. (negotiation not
When the ReserveCommonCCESwitch option of this parameter is required)
selected, CCE resources in the common search space will be reserved
for uplink channels.
PDCCH Power CellPdcchAlgo.PdcchPowerEnhancedSwitch This parameter specifies whether to enable enhanced Network plan
Enhanced Switch PDCCH/ePDCCH power control. If this switch is turned on, the eNodeB (negotiation not
selects an appropriate PDCCH/ePDCCH aggregation level based on required)
channel quality and increases PDCCH/ePDCCH transmit power to
increase PDCCH/ePDCCH capacity. The value OFF(Off) is
recommended.
PDCCH BLER Target CellPdcchAlgo.PdcchBlerTarget This parameter specifies the target BLER for PDCCH link adaptation. Network plan
The PDCCH BLER needs to converge to this target value. The value 15 (negotiation not
is recommended. required)
EPDCCH Algorithm CellPdcchAlgo.EpdcchAlgoSwitch This parameter indicates the algorithm switch which enables the Network plan
Switch ePDCCH. The ePDCCH feature takes effect after this switch is turned (negotiation not
on. The value OFF(Off) is recommended. required)
CCE Usage Threshold CellPdcchAlgo.CceThdtoEnableEpdcch This parameter specifies the CCE usage threshold for enabling the Network plan
To Enable EPDCCH ePDCCH. If CCE usage is greater than the value of this parameter, the (negotiation not
eNodeB configures ePDCCH resources for newly accessed UEs. The required)
value 80 is recommended.
RB Usage Threshold CellPdcchAlgo.RbThdtoEnableEpdcch This parameter specifies the downlink RB usage threshold for enabling Network plan
To Enable EPDCCH the ePDCCH. If downlink RB usage is less than the value of this (negotiation not
parameter, the eNodeB configures ePDCCH resources for newly required)
accessed UEs. The value 60 is recommended.
CCE Usage Threshold CellPdcchAlgo.CceThdtoDisableEpdcch This parameter specifies the CCE usage threshold for disabling the Network plan
To Disable EPDCCH ePDCCH. If CCE usage is less than the value of this parameter, the (negotiation not
eNodeB disables the ePDCCH. The value 60 is recommended. required)
ECCE Usage CellPdcchAlgo.EcceThdtoDisableEpdcch This parameter specifies the ECCE usage threshold for disabling the Network plan
Threshold To Disable ePDCCH. If ECCE usage is less than the value of this parameter, the (negotiation not
EPDCCH eNodeB disables the ePDCCH. The value 5 is recommended. required)
RB Usage Threshold CellPdcchAlgo.RbThdtoDisableEpdcch This parameter specifies the downlink RB usage threshold for disabling Network plan
To Disable EPDCCH the ePDCCH. If downlink RB usage is greater than the value of this (negotiation not
parameter, the eNodeB disables the ePDCCH. The value 80 is required)
recommended.
None

onfiguring PDCCH Aggregation Level Adaptation
Run the MOD CELLPDCCHALGO command to set the PDCCHAggLvlAdaptStrage parameter to STRATEGYBASEDONCOVERAGE(Coverage-based Selection Strategy)
or STRATEGYBASEDONCAPACITY(Capacity-based Selection Strategy) based on the network plan.
onfiguring PDCCH Aggregation Level Selection in Dual-codeword Scenarios
Run the MOD CELLPDCCHALGO command to set Aggregation Level Strategy for Dual Codewords to STRATEGYBASEDONCAPACITY(Capacity-based Selection
Strategy) or STRATEGYBASEDONCOVERAGE(Coverage-based Selection Strategy) based on the network plan.
onfiguring PDCCH Symbol Adaptation
Run the MOD CELLPDCCHALGO command to set PDCCH Symbol Number Adjust Switch to ON(On) or ECFIADAPTIONON(Enhanced CFI Adaption On) based on the
network plan.
onfiguring CCE Ratio Adaptation
Run the MOD CELLPDCCHALGO command to set Cce Ratio Adjust Switch to ON(On) and select or clear the ReserveCommonCCESwitch(ReserveCommonCCESwitch)
option of the UlPdcchAllocImproveSwitch parameter based on the network plan.
onfiguring PDCCH Utilization Improvement
Run the MOD CELLPDCCHALGO command to set PdcchCapacityImproveSwitch and PdcchPowerEnhancedSwitch to ON(On), and set PdcchInitialCceAdjustValue.
onfiguring Closed-Loop Adjustment to the PDCCH Aggregation Level
Run the MOD CELLPDCCHALGO command to set PDCCH Aggregation Level CL Switch to ON(On).
onfiguring ePDCCH
Run the MOD CELLPDCCHALGO command to select the EpdcchFunctionSwitch(EpdcchFunctionSwitch) option of the EpdcchAlgoSwitch parameter.
• Configuring PDCCH aggregation level adaptation
MOD CELLPDCCHALGO: LOCALCELLID=0, PDCCHAggLvlAdaptStrage=STRATEGYBASEDONCOVERAGE;

• Configuring PDCCH aggregation level selection in dual-codeword scenarios
MOD CELLPDCCHALGO: LOCALCELLID=0, AggLvlSelStrageForDualCW=STRATEGYBASEDONCAPACITY;
• Configuring PDCCH symbol adaptation
MOD CELLPDCCHALGO: LOCALCELLID=0, PdcchSymNumSwitch=ECFIADAPTIONON;
• Configuring CCE ratio adaptation
MOD CELLPDCCHALGO: LOCALCELLID=0, CceRatioAdjSwitch=ON, UlPdcchAllocImproveSwitch= ReserveCommonCCESwitch-1;
• Configuring PDCCH utilization improvement
MOD CELLPDCCHALGO: LOCALCELLID=0, PdcchCapacityImproveSwitch=ON, PdcchPowerEnhancedSwitch=ON;
• Configuring closed-loop adjustment to the PDCCH aggregation level
MOD CELLPDCCHALGO: LOCALCELLID=0, PdcchAggLvlCLAdjustSwitch=ON;
• Configuring ePDCCH
MOD CELLPDCCHALGO: LOCALCELLID=0, ePDCCHAlgoSwitch=ePDCCHFunctionSwitch-1;
DCCH Aggregation Level Adaptation
1. After a 10 MHz cell is successfully activated, enable a UE to access the cell at the cell center and start User Datagram Protocol (UDP) data upload and download at
60 Mbit/s.
window, choose Trace Type > LTE > Cell Performance Monitoring > DCI Statistic Monitoring to start DCI statistics monitoring. Monitor the real-time values of
the following items: PDCCH Use 1 CCE Num, PDCCH Use 2 CCE Num, PDCCH Use 4 CCE Num, and PDCCH Use 8 CCE Num. Figure 10-1 shows an example.
When the UE is at the cell center, the eNodeB preferentially selects aggregation levels that lead to high coding rates for the UE. Therefore, the expected result is
that PDCCH Use 1 CCE Num, PDCCH Use 2 CCE Num, or both have larger values than PDCCH Use 4 CCE Num and PDCCH Use 8 CCE Num.
Figure 10-1 DCI statistics monitoring (1)
3. Move the UE to the cell edge, and monitor the real-time values of the same items.
When the UE is at the cell edge, the eNodeB preferentially selects aggregation levels that lead to low coding rates for the UE. If the value of PDCCH Use 4 CCE
Num or PDCCH Use 8 CCE Num is greater than the corresponding value observed in Step2, PDCCH aggregation level adaptation takes effect.
NOTE:
An observation method similar to this applies to ePDCCH aggregation level adaptation.
DCCH Aggregation Level Selection in Dual-codeword Scenarios
1. After a 10 MHz cell is successfully activated, enable a UE to access the cell and start UDP data upload and download at 60 Mbit/s. Ensure that dual-codeword
scheduling is enabled for the UE.
2. When the BLER on the PDCCH is larger than the target BLER, run the LST CELLPDCCHALGO command on the U2000 client and verify that Aggregation Level
Strategy for Dual Codewords is set to STRATEGYBASEDONCOVERAGE.
3. Check performance counters on the U2000 client. For details, see Number of Times of DTX for PDCCH Resource Allocations with a Specific Aggregation Level in a Cell and
Number of Successful PDCCH Resource Allocations with a Specific Aggregation Level in a Cell.
If the number of times of discontinuous transmission (DTX) for PDCCH resource allocations decreases and the number of successful PDCCH resource allocations
for high aggregation levels increases in dual-codeword scenarios, the coverage-based aggregation level selection policy takes effect.
1. After a 10 MHz cell is successfully activated, enable a UE to access the cell at the cell center and start UDP data upload and download at 60 Mbit/s.
window, choose Trace Type > LTE > Cell Performance Monitoring > DCI Statistic Monitoring to start DCI statistics monitoring. Monitor the real-time values of
the following items: CFI Engross 1 Symbol Stat.Num, CFI Engross 2 Symbol Stat.Num, CFI Engross 3 Symbol Stat.Num, and CFI Engross 4 Symbol Stat.Num.
Figure 10-2 shows an example.
When the UE is at the cell center, the eNodeB prefers a small number of symbols for the PDCCH. Therefore, the expected result is that CFI Engross 1 Symbol
Stat.Num, CFI Engross 2 Symbol Stat.Num, or both have larger values than CFI Engross 3 Symbol Stat.Num and CFI Engross 4 Symbol Stat.Num.
Figure 10-2 DCI statistics monitoring (2)

3. Enable another three UEs to access the cell and start UDP data upload and download on these UEs at 60 Mbit/s, and move all the UEs to the cell edge.
4. Monitor the real-time values of the same items.
When the number of UEs at the cell edge increases, the eNodeB prefers a larger number of symbols for the PDCCH. If the value of CFI Engross 3 Symbol
Stat.Num is greater than the value observed in 2, PDCCH symbol adaptation takes effect.
CE Ratio Adaptation
On the U2000 client, run the LST CELLPDCCHALGO command to check the values of Cce Ratio Adjust Switch.
If the value of Cce Ratio Adjust Switch is On, CCE/ECCE ratio adaptation takes effect. Otherwise, CCE/ECCE ratio adaptation does not take effect.
DCCH Utilization Improvement
• Method 1: Checking whether the function is enabled by viewing configurations
On the U2000 client, run the LST CELLPDCCHALGO command to check the values of PDCCH Capacity Improve Switch, PDCCH Power Enhanced Switch, and PDCCH
Initial Cce Adjustment Value.
If PDCCH Capacity Improve Switch and PDCCH Power Enhanced Switch are set to On, PDCCH/ePDCCH capacity improvement is enabled.
If the value of the PDCCH Initial Cce Adjustment Value parameter is greater than -10, the eNodeB has selected a lower aggregation level, helping improve PDCCH capacity.
• Method 2: Checking whether the function takes effect by viewing services
On the U2000 client, choose Monitor > Signaling Trace > Signaling Trace Management. In the navigation tree on the left of the Signaling Trace Management window,
choose Trace Type > LTE > Cell Performance Monitoring > DCI Statistic Monitoring to start DCI statistics monitoring. Monitor the real-time values of the following items:
• PDCCH Use 1 CCE Num

If the weighted average of the preceding items decreases, PDCCH capacity improvement takes effect.
DCCH
On the U2000 client, choose Monitor > Signaling Trace > Signaling Trace Management. In the navigation tree on the left of the Signaling Trace Management window,
choose Trace Type > LTE > Cell Performance Monitoring > DCI Statistic Monitoring to start DCI statistics monitoring. Monitor the real-time values of the following items:
ePDCCH Use 1 ECCE Num, ePDCCH Use 2 ECCE Num, ePDCCH Use 4 ECCE Num, ePDCCH Use 8 ECCE Num, ePDCCH Use 16 ECCE Num, and ePDCCH Use 32 ECCE
Num.
If the value of any preceding item is not zero, the ePDCCH feature takes effect and UEs in a cell are using ePDCCH resources.
osed-Loop Adjustment to the PDCCH Aggregation Level
NOTE:
Anonymization has been performed on S1 interface tracing tasks, and therefore no security risk exists.
1. Ensure that the test UE's serving cell and the intra-frequency neighboring cells are activated. On the U2000 client, run the LST CELLPDCCHALGO command to
query and record the value of PDCCH Virtual Loading Proportion.
2. Run the MOD CELLPDCCHALGO command with the PDCCH Virtual Loading Proportion parameter set to 100 to generate weak interference to the PDSCH and
strong interference to the PDCCH in the serving cell.
3. Choose Monitor > Signaling Trace > Signaling Trace Management.
4. In the navigation tree on the left of the Signaling Trace Management window, choose Trace Type > LTE > Application Layer > S1 Interface Trace, and double-
click S1 Interface Trace.
5. In the S1 Interface Trace dialog box, configure the S1 interface tracing task and click Finish.
6. On the task list in the Signaling Trace Management window, double-click the S1 Interface Trace task. A monitoring window for S1 interface tracing is displayed.
7. Enable the UE to access the network from the serving cell. Move the UE close to the cell center, and ensure that the UE can receive strong signals from intra-
frequency neighboring cells. After the UE's inactivity timer times out (which indicates that the UE has entered the RRC_IDLE mode), perform downlink UDP
transmission at a rate of 150 Mbit/s (which causes the UE to enter the RRC_CONNECTED mode). Check the UE's S1AP_INITIAL_UE_MSG message in the
monitoring window, and record the values of mMEC and m-TMSI, as shown in Figure 10-3.
Figure 10-3 S1AP_INITIAL_UE_MSG message
8. In the navigation tree on the left of the Signaling Trace Management window, choose Trace Type > LTE > User Performance Monitoring > BLER Monitoring,
and double-click BLER Monitoring.
9. In the BLER Monitoring dialog box, configure the BLER monitoring task with the MMEc field set to the decimal value of mMEC and the mTMSI field set to the
decimal value of m-TMSI, and click Finish, as shown in Figure 10-4.

Figure 10-4 BLER monitoring (1)
10. On the task list in the Signaling Trace Management window, double-click the BLER Monitoring task. A monitoring window for BLER monitoring is displayed.
11. Check the values of PDCCH/EPDCCH BLER (Permillage). When the PDSCH experiences weak interference while the PDCCH experiences strong interference,
the expected observation results are as follows: When closed-loop adjustment to the PDCCH/ePDCCH aggregation level is enabled, the eNodeB dynamically
adjusts the PDCCH/ePDCCH aggregation level of the UE based on the PDCCH/ePDCCH BLER. The values of PDCCH BLER/EPDCCH (Permillage) converge to
zero. When closed-loop adjustment to the PDCCH/ePDCCH aggregation level is disabled, the eNodeB calculates the PDCCH/ePDCCH aggregation level based on
the MCS indexes for the scheduled PDSCH. The calculated level is inaccurate, and therefore the values of PDCCH/EPDCCH BLER (Permillage) do not converge
at zero.
12. Run the MOD CELLPDCCHALGO command with the PDCCH Virtual Loading Proportion parameter set to the original value.
N/A
10.4.6 Deactivation

activating PDCCH Symbol Adaptation
Run the MOD CELLPDCCHALGO command to deactivate dynamic adjustment on the number of OFDM symbols occupied by the PDCCH and set the initial number of PDCCH
symbols.
activating CCE Ratio Adaptation
Run the MOD CELLPDCCHALGO command to deactivate CCE ratio adjustment.
activating Closed-Loop Adjustment to the PDCCH Aggregation Level
Run the MOD CELLPDCCHALGO command to deactivate closed-loop adjustment to the PDCCH aggregation level.
activating PDCCH Utilization Improvement
Run the MOD CELLPDCCHALGO command to set PDCCH Capacity Improve Switch and PDCCH Power Enhanced Switch to OFF(Off), and set PDCCH Initial Cce
Adjustment Value.
activating ePDCCH
Run the MOD CELLPDCCHALGO command to deselect the ePDCCHFunctionSwitch(ePDCCHFunctionSwitch) option of the EPDCCH Algorithm Switch parameter.
activating PDCCH Symbol Adaptation
MOD CELLPDCCHALGO:LOCALCELLID=0,INITPDCCHSYMNUM=3,PDCCHSYMNUMSWITCH=OFF;
activating CCE Ratio Adaptation
MOD CELLPDCCHALGO:LOCALCELLID=0,CCERATIOADJSWITCH=OFF;
activating Closed-Loop Adjustment to the PDCCH Aggregation Level
MOD CELLPDCCHALGO:LOCALCELLID=0,PDCCHAGGLVLCLADJUSTSWITCH=OFF;
activating PDCCH Utilization Improvement
MOD CELLPDCCHALGO: LOCALCELLID=0, PdcchCapacityImproveSwitch=OFF, PdcchPowerEnhancedSwitch=OFF;
activating ePDCCH
MOD CELLPDCCHALGO: LOCALCELLID=0, ePDCCHAlgoSwitch=ePDCCHFunctionSwitch-0;

5 PDCCH/ePDCCH Monitoring
DCCH Symbol Usage
Use the following counters to monitor the PDCCH symbol usage of a cell:
Counter Name Description
L.ChMeas.PDCCH.SymNum.1 Number of times the PDCCH occupies one symbol in a measurement period
L.ChMeas.PDCCH.SymNum.2 Number of times the PDCCH occupies two symbols in a measurement period
L.ChMeas.PDCCH.SymNum.3 Number of times the PDCCH occupies three symbols in a measurement period
L.ChMeas.PDCCH.SymNum.4 Number of times the PDCCH occupies four symbols in a measurement period
If the values of the first two counters are relatively large and the values of the last two counters are relatively small, the PDCCH symbol usage is low.
DCCH CCE Usage
Use the following counters to monitor the PDCCH CCE usage of a cell:
L.ChMeas.CCE.ULUsed Number of PDCCH CCEs used for uplink DCI in a measurement period
L.ChMeas.CCE.DLUsed Number of PDCCH CCEs used for downlink DCI in a measurement period
L.ChMeas.CCE.CommUsed Number of PDCCH CCEs used for common DCI
L.ChMeas.CCE.Avail Number of available PDCCH CCEs
L.ChMeas.CCE.DLUsed.DRB Number of PDCCH CCEs used for initial transmitted downlink data in a cell
L.ChMeas.CCE.DLUsed.SRB Number of PDCCH CCEs used for initial transmitted downlink signaling in a cell
L.ChMeas.CCE.DLUsed.MCE Number of PDCCH CCEs used for initial transmitted downlink MCEs in a cell
If the value of L.ChMeas.CCE.DLUsed is larger than the value of L.ChMeas.CCE.ULUsed, the PDCCH downlink CCE usage is high.
Compare the weekly total uplink and downlink throughput before and after PDCCH symbol adaptation is enabled and evaluate the gains.
L.Thrp.bits.UL Total uplink traffic volume for PDCP PDUs in a cell

L.Thrp.bits.DL Total downlink traffic volume for PDCP SDUs in a cell
If the total uplink and downlink traffic volumes in a cell increase after PDCCH symbol adaptation is enabled, this feature brings positive gains.
mber of Times of DTX for PDCCH Resource Allocations with a Specific Aggregation Level in a Cell
Based on the numbers of times of DTX for PDCCH resource allocations with a specific PDCCH aggregation level before and after the Aggregation Level Strategy for Dual
Codewords parameter is set to STRATEGYBASEDONCOVERAGE, the gains for the PDCCH aggregation level selection policy in dual-codeword scenarios can be evaluated.
L.ChMeas.PDCCH.DL.DTXNum.AggLvl1 Number of times of DTX for PDCCH resource allocation with aggregation level 1 in a cell
L.ChMeas.PDCCH.DL.DTXNum.AggLvl2 Number of times of DTX for PDCCH resource allocations with aggregation level 2 in a cell
mber of Successful PDCCH Resource Allocations with a Specific Aggregation Level in a Cell
Based on the numbers of successful PDCCH resource allocations with a specific PDCCH aggregation level before and after the Aggregation Level Strategy for Dual
Codewords parameter is set to STRATEGYBASEDONCOVERAGE, the gains for the PDCCH aggregation level selection policy in dual-codeword scenarios can be evaluated.
Based on the numbers of successful PDCCH resource allocations with a specific uplink and downlink PDCCH aggregation level when the PDCCH Capacity Improve Switch
parameter is set to ON(On) and OFF(Off), the gains for PDCCH capacity improvement can be evaluated.
Based on the numbers of successful PDCCH resource allocations with a specific uplink and downlink PDCCH aggregation level when the PDCCH Power Enhanced Switch
parameter is set to ON(On) and OFF(Off), the gains for PDCCH power control improvement can be evaluated.
L.ChMeas.PDCCH.AggLvl1Num Number of times of PDCCH resource allocations with aggregation level 1

L.ChMeas.PDCCH.UL.AggLvl1Num Number of times of PDCCH uplink resource allocations with aggregation level 1
When the Aggregation Level Strategy for Dual Codewords parameter is set to STRATEGYBASEDONCOVERAGE, the PDCCH aggregation level selection policy selected in
dual-codeword scenarios brings gains if the number of times of DTX for uplink and downlink PDCCH resource allocations decreases and the number of successful uplink and
downlink PDCCH resource allocations with high aggregation levels in dual-codeword scenarios increases.
When the PDCCH Capacity Improve Switch parameter is set to ON(On), PDCCH capacity improvement brings gains if the uplink and downlink weighted average PDCCH
aggregation level decreases.

If the PDCCH Power Enhanced Switch parameter is set to ON(On), PDCCH power control improvement brings gains if the uplink and downlink weighted average PDCCH
aggregation level decreases.
DCCH Usage
Use the following counters to monitor the ePDCCH ECCE usage of a cell:
L.ChMeas.eCCE.DLUsed.DRB Number of ePDCCH eCCEs used by initially transmitted downlink data

L.ChMeas.eCCE.DLUsed.MCE Number of ePDCCH eCCEs used by initially transmitted downlink MCEs
L.ChMeas.eCCE.DLUsed.SRB Number of ePDCCH eCCEs used by initially transmitted downlink signaling messages
L.ChMeas.ePDCCH.DL.DTXNum.AggLvl1 Number of times DTX is detected for downlink ePDCCH resource allocations with aggregation
level 1 in a cell
level 2 in a cell
level 4 in a cell
level 8 in a cell
level 16 in a cell
level 32 in a cell
L.ChMeas.Dl.ePDCCH.AggLvl1Num Number of times downlink ePDCCH resource allocations with aggregation level 1
L.ChMeas.Ul.ePDCCH.AggLvl1Num Number of times uplink ePDCCH resource allocations with aggregation level 1
6 Parameter Optimization
To optimize network performance, enable CCE/ECCE ratio adaptation and closed-loop adjustment to the PDCCH/ePDCCH aggregation level in all scenarios.
In non-ultra-high-speed mobility scenarios, enable PDCCH symbol adaptation in addition to the preceding functions.
7 Possible Issues
N/A
11 Engineering Guidelines for PUCCH Resource Management
1 When to Use
This section describes when to use the following functions of PUCCH resource management.
aptive SRI Period
SRI period adaptation is enabled by default. In ultra-high-speed mobility scenarios, disabling this function is recommended. In other scenarios, enabling this function is
recommended.
namic PUCCH Resource Adjustment
Dynamic PUCCH resource adjustment is enabled by default. In ultra-high-speed mobility scenarios, disabling this function is recommended. In other scenarios, enabling this
function is recommended.
UCCH Flexible Configuration
PUCCH flexible configuration is disabled by default. When the uplink bandwidth is experiencing strong interference (for example, 50 dBm) at both ends, enabling PUCCH
flexible configuration is recommended. In other scenarios, allowing PUCCH flexible configuration to retain its default setting of disabled is recommended. In other scenarios, you
are advised to retain PUCCH flexible configuration disabled.
NOTE:
Interference degree = Interference value – Background noise
where
• The interference value is obtained through interference detection on the U2000.

• The background noise changes based on network conditions. It is equal to the power spectrum density of the thermal noise multiplied by the bandwidth.
In a scenario where the power spectrum density of the thermal noise is -174 dBm/Hz and the bandwidth is 180 kHz, the background noise is then approximately -121 dBm.

B Priority Mode for the PUCCH Resource Allocation Policy
Enable the RB priority mode only in the big event scenario.
None
3 Planning
None
4 Deployment
11.4.1 Requirements
The PUCCH Flexible Configuration feature is used for the LBBPd and UBBP. Micro eNodeBs do not have such requirements.
None
cense
The operator has purchased and activated the license for the feature listed in the following table. Micro eNodeBs do not have such requirements.
Feature ID Feature Name Model License Control Item NE Sales Unit
LOFD-001093 PUCCH Flexible LT1S000PFC00 PUCCH Flexible Configuration eNodeB per Cell
Configuration
11.4.2 Precautions
Do not reconfigure the CellAlgoSwitch.PucchAlgoSwitch, PUCCHCfg.DeltaShift, PUCCHCfg.NaSriChNum, PUCCHCfg.CqiRbNum, PUCCHCfg.PucchExtendedRBNum, or
PUCCHCfg.Format1ChAllocMode parameter while a cell is running. Otherwise, ongoing services in the cell will be interrupted.

quired Data
The following table describes the parameter that must be set in the CellPucchAlgo MO to configure the threshold for determining the low load state of SRI resources.
SRI Low Load Threshold CellPucchAlgo.SriLowLoadThd This parameter specifies the threshold for determining the low load Network plan
state of SRI resources. The value 0 is recommended for the 1.4 (negotiation not
MHz and 3 MHz bandwidths, 10 for the 5 MHz and 10 MHz required)
bandwidths, and 20 for the 15 MHz and 20 MHz bandwidths.
SRI Algorithm Switch CellPucchAlgo.SriAlgoSwitch This parameter specifies the working modes for SRI reporting Network plan
period configuration. (negotiation not
SriAdaptiveHoldForVoIPSW: Indicates whether to enable SRI required)
reporting period adaptation for VoLTE UEs during resource
adjustment for SRI reporting. SriAdaptiveHoldForVoIPSW takes
effect only when both PUCCH resource adjustment and SRI
reporting period adaptation are enabled. You are advised to select
this option if required by speech quality of voice UEs.
SriPeriodCfgOptSW: Indicates whether to optimize SRI reporting
period configuration. You are advised to select this option in CA
and SPS scenarios.
SriOffsetReConfigForDrxSW: For details, see DRX and Signaling
Control Feature Parameter Description.
The following table describes the parameter that must be set in the CellQciPara MO to configure the SRI period.
SRI Period CellQciPara.SriPeriod This parameter specifies the interval at which SRIs are sent. This Network plan
parameter is valid when GlobalProcSwitch.SriAdaptiveSwitch is set (negotiation not
to OFF(Off). The value ms10(SRI 10ms) is recommended. required)
NOTE:
The following table describes the parameters that must be set in the PUCCHCfg MO to configure the cyclic shift interval for the PUCCH, the number of resource indexes
allocated to SRIs and semi-persistent ACKs, the number of RBs for CQI reporting, the number of extended PUCCH RBs, format1 code channel allocation mode, format2 code
channel allocation mode, SRI period adaptive switch, PUCCH allocation policy, number of Format3 RBs, and maximum number of code channels that can be used by SCC
ACKs in 2CC CA scenarios in PUCCH flexible configuration.
Delta shift PUCCHCfg.DeltaShift This parameter specifies the cyclic shift interval for the PUCCH. Network plan
• If the cell is configured on an LBBPc and uses normal (negotiation not
CPs, set this parameter to DS2_DELTA_SHIFT(ds2). required)
• If the cell is configured on an LBBPc and uses
extended CPs, set this parameter to
DS3_DELTA_SHIFT(ds3).


• If the cell is configured on an LBBPd or UBBP and uses
normal CPs, set this parameter to DS1_DELTA_SHIFT
(ds1).
• If the cell is configured on an LBBPd or UBBP and uses
extended CPs, set this parameter to
DS3_DELTA_SHIFT(ds3).
Format1 Channel PUCCHCfg.Format1ChAllocMode This parameter specifies the mode for allocating code channel Network plan
Allocation Mode resources occupied by the PUCCH in format 1, 1a, or 1b. This (negotiation not
parameter takes effect only when the PUCCHCfg.DeltaShift required)
parameter is set to DS1_DELTA_SHIFT(ds1).
If a cell is serving multiple UEs, you are advised to set this
parameter to RANDOMMODE(randommode). Then, code
channel resources occupied by the PUCCH in format 1, 1a, or 1b
are allocated randomly. This reduces interference between code
channels and improves PUCCH demodulation capability.
In high-speed railway scenarios, you are advised to set this
parameter to OPTISELECTMODE(OPTISELECTMODE). This
reduces interference between code channels and improves
PUCCH demodulation capability.
When uplink PRBs are insufficient, you are advised to set this
parameter to RBSAVINGMODE(RBSAVINGMODE), saving
PUCCH RB resources.
Format2 Channel PUCCHCfg.Format2ChAllocMode This parameter specifies the mode for allocating code channel Network plan
Allocation Mode resources occupied by the PUCCH in format 2, 2a, or 2b. You are (negotiation not
advised to set this parameter to RANDOMMODE(randommode). required)
This reduces interference between code channels and improves
PUCCH demodulation capability.
ACK/SRI Channel PUCCHCfg.NaSriChNum This parameter specifies the number of resource indexes Network plan
Number allocated to SRIs and semi-persistent ACKs. This parameter takes (negotiation not
effect if the PucchSwitch option of the required)
CellAlgoSwitch.PucchAlgoSwitch parameter is cleared. The value
6 is recommended.
CQI RB number PUCCHCfg.CqiRbNum This parameter specifies the number of RBs for CQI reporting. Network plan
This parameter takes effect if the PucchSwitch option of the (negotiation not
CellAlgoSwitch.PucchAlgoSwitch parameter is cleared. The value required)
1 is recommended.
PUCCH Extended RB PUCCHCfg.PucchExtendedRBNum This parameter specifies the number of extended PUCCH RBs, Network plan
Number which is also the number of RBs reserved on the band edges for (negotiation not
the PUSCH. This parameter is valid when the switch of PUCCH required)
flexible configuration is turned on. The parameter setting must
consider the number of RBs used by the PRACH, SRS, and
PUCCH as well as the number of compressed RBs. If the
parameter value is so large that there are no enough RBs for the
PRACH and SRS, the cell cannot be established successfully. In
addition, the parameter setting should consider the amount of
interference the PUCCH is likely to experience.
This parameter is inapplicable to micro eNodeBs.
SRI Period Adaptive PUCCHCfg.SriPeriodAdaptive This parameter specifies whether to enable SRI period adaptation. Network plan
Switch • If the uplink throughput is required, you are advised to (negotiation not
set this parameter to QCIADAPTIVE(QCIADAPTIVE). required)
• If the SRI short period is required, you are advised to
set this parameter to NOQCIADAPTIVE
(NOQCIADAPTIVE).
• If a fixed SRI period is required, you are advised to set
this parameter to OFF(Off).
PUCCH Allocation Policy PUCCHCfg.PucchAllocPolicy This parameter specifies the PUCCH resource allocation policy. Network plan
RbPriorityModeSW: Indicates whether to enable the RB priority (negotiation not
mode during PUCCH code channel resource allocation. This required)
option takes effect only when PUCCH resource adjustment is
disabled. You are advised to select this option in big events.
Format3 RB Number PUCCHCfg.Format3RbNum Indicates the maximum number of RBs used by PUCCH Network plan
resources in Format 3 that can be allocated by the eNodeB to (negotiation not
UEs that send HARQ-ACKs over the PUCCH Format3. required)
Set this parameter to a larger value if the eNodeB needs to
allocate more Format3 RBs.
Max 2CC ACK Channel PUCCHCfg.Max2CCAckChNum This parameter specifies the maximum number of 2CC SCC ACK Network plan
Number channels that can be allocated by the eNodeB when the eNodeB (negotiation not
allocates SCC ACK channels to UEs using the Format1b plus required)
channel selection method.
Set this parameter to a larger value if the eNodeB needs to
allocate more 2CC SCC ACK channels.
The following table describes the parameter that must be set in the CellAlgoSwitch MO to configure PUCCH algorithms.
PUCCH algorithm switch CellAlgoSwitch.PucchAlgoSwitch This parameter specifies whether to enable PUCCH resource Network plan
adjustment, PUCCH flexible configuration, and SCC ACK (negotiation not
resource configuration. required)
PucchSwitch: In non-ultra-high-speed mobility scenarios, you are
advised to select the PucchSwitch option. In ultra-high-speed
mobility scenarios, you are advised to clear the PucchSwitch
option.


PucchFlexCfgSwitch: If the LBBPd is used, the uplink bandwidth
is 5 MHz or above, and the uplink band edges experience severe
interference, you are advised to select the PucchFlexCfgSwitch
option. With this setting, none of uplink ICIC, frequency hopping,
and scheduling can take effect. In other scenarios, you are
advised to clear the PucchFlexCfgSwitch option.
SCCAckResourceCfgSW: When uplink PRBs are insufficient or
you need to adjust the number of RBs that are used by PUCCH
resources in Format3, you are advised to select the
SCCAckResourceCfgSw option. In other scenarios, you are
advised to clear the SCCAckResourceCfgSw option.
None

1. Run the MOD CELLPUCCHALGO command to set the threshold for determining the low load state of SRI resources and working mode for SRI reporting period
configuration.
2. Run the MOD PUCCHCFG and MOD CELLQCIPARA commands to set the SRI period.
NOTE:
3. Run the MOD PUCCHCFG command to set the cyclic shift interval for the PUCCH, number of resource indexes allocated to SRIs and ACKs to downlink semi-
persistent scheduling, number of RBs for CQI reporting, Format1 code channel allocation mode, Format2 code channel allocation mode, PUCCH resource allocation
policy, number of Format3 RBs, and maximum number of code channels that can be used by SCC ACKs in 2CC CA scenarios, and enable SRI adaptation.
4. Run the MOD CELLALGOSWITCH command to set PucchSwitch, PucchFlexCfgSwitch, and SCCAckResourceCfgSw.
• Configuring the SRI light load threshold

MOD CELLPUCCHALGO:LOCALCELLID=0, SRILOWLOADTHD=10;
• Configuring SRI period adaptation retainability of voice UEs
MOD CELLPUCCHALGO:LOCALCELLID=0,SRIALGOSWITCH=SriAdaptiveHoldForVoIPSW-1;
• Configuring SRI period configuration optimization
MOD CELLPUCCHALGO:LOCALCELLID=0,SRIALGOSWITCH=SriPeriodCfgOptSW-1;
• Configuring the fixed SRI period
MOD PUCCHCFG:LOCALCELLID=0,SRIPERIODADAPTIVE=OFF;
MOD CELLQCIPARA: LOCALCELLID=0,QCI=9,SRIPERIOD=ms20;
• Configuring the SRI period adaptive switch
MOD PUCCHCFG:LOCALCELLID=0,SRIPERIODADAPTIVE=NOQCIADAPTIVE;
• Configuring the delta shift
MOD PUCCHCFG:LOCALCELLID=0,DELTASHIFT=DS1_DELTA_SHIFT;
• Configuring the dynamic PUCCH resource adjustment
MOD CELLALGOSWITCH: LOCALCELLID=0,PUCCHALGOSWITCH=PucchSwitch-1;
• Configuring the PUCCH flexible configuration
MOD PUCCHCFG:LOCALCELLID=0,PUCCHEXTENDEDRBNUM=1;
MOD CELLALGOSWITCH:LOCALCELLID=0,PUCCHALGOSWITCH=PucchFlexCfgSwitch-1;
• Setting the Format1 channel allocation mode to the optimized selection mode
MOD PUCCHCFG:LOCALCELLID=0,FORMAT1CHALLOCMODE=OPTISELECTMODE;
• Setting the Format1 channel allocation mode to the RB saving mode
MOD PUCCHCFG:LOCALCELLID=0,FORMAT1CHALLOCMODE=RBSAVINGMODE;
• Setting the Format2 channel allocation mode to the random mode
MOD PUCCHCFG:LOCALCELLID=0,FORMAT2CHALLOCMODE=RANDOMMODE;
• Enabling the RB priority mode for the PUCCH resource allocation policy
MOD PUCCHCFG:LOCALCELLID=0,PUCCHALLOCPOLICY=RbPriorityModeSW-1,NASRICHNUM=121,CQIRBNUM=5;
MOD CELLALGOSWITCH: LOCALCELLID=0,PUCCHALGOSWITCH=PucchSwitch-0;
NOTE:
For the values of the PUCCHCfg.NaSriChNum and PUCCHCfg.CqiRbNum parameters, see 5.4 PUCCH Resource Allocation Policy.
• Enabling the SCC ACK resource configuration switch

MOD PUCCHCFG:LOCALCELLID=0, Format3RbNum=1, Max2CCAckChNum=MAX_CH_NUM8;
MOD CELLALGOSWITCH: LOCALCELLID=0,PUCCHALGOSWITCH=Dl2CCAckResShareSw-1& SCCAckResourceCfgSw-1;
UCCH SRI Adaptation
NOTE:
1. On the U2000 client, run the LST CELLPUCCHALGO command to check and record the value of SRI Low Load Threshold.
3. On the U2000 client, run the MOD CELLPUCCHALGO command with the SRI Low Load Threshold parameter set to 1.
4. Enable a UE to access the cell at the cell center, and check for the IE sr-ConfigIndex in the RRC_CONN_RECFG message for this UE, as shown in Figure 11-1.
• If the RRC_CONN_RECFG message contains the IE sr-ConfigIndex, use the value of this IE to find the SRI period for this UE in Table 5-2.

• If the RRC_CONN_RECFG message does not contain the IE sr-ConfigIndex, obtain the value of this IE from the RRC_CONN_SETUP message for this
UE. Use that value to find the SRI period for this UE in Table 5-2. Figure 11-2 shows a sample RRC_CONN_SETUP message.
Before the UE accesses the cell, the SRI resource load is light in this cell. Therefore, the eNodeB configures a short SRI period for the UE when the UE accesses
the cell.
Figure 11-1 RRC_CONN_RECFG message (1)
Figure 11-2 RRC_CONN_SETUP message (1)
5. Enable another UE to access the same cell at the cell center, and check for the IE sr-ConfigIndex in the RRC_CONN_RECFG message for this UE, as shown in
Figure 11-3.
• If the RRC_CONN_RECFG message contains the IE sr-ConfigIndex, use the value of this IE to find the SRI period for this UE in Table 5-2.
• If the RRC_CONN_RECFG message does not contain the IE sr-ConfigIndex, obtain the value of this IE from the RRC_CONN_SETUP message for this
UE. Use that value to find the SRI period for this UE in Table 5-2. Figure 11-4 shows a sample RRC_CONN_SETUP message.
When the second UE attempts to access the cell, the SRI resource load is at a medium level in this cell. Therefore, the eNodeB configures a long SRI period for this
UE. If the SRI period for the second UE is longer than that for the first UE, SRI adaptation takes effect.

Figure 11-3 RRC_CONN_RECFG message (2)
6. On the U2000 client, run the MOD CELLPUCCHALGO command with the SRI Low Load Threshold parameter set to the original value.
clic Shift Interval for the PUCCH
NOTE:
1. On the U2000 client, run the LST PUCCHCFG command to check and record the value of Cyclic Shift Interval.
3. Deactivate the cell, and activate the cell again. Then, check the IE deltaPUCCH-Shift in the first RRC_SYS_INFO message traced on the Uu interface. Figure 11-5
shows a sample RRC_SYS_INFO message. Check whether the value of the IE is consistent with the value of Cyclic Shift Interval. If they are consistent, the
configuration takes effect.

Figure 11-5 RRC_SYS_INFO message
namic PUCCH Resource Adjustment
1. After a 10 MHz cell is successfully activated, run the LST CELLPDCCHALGO command on the U2000 client to check and record the values of PDCCH Initial
Symbol Number and PDCCH Symbol Number Adjust Switch.
2. On the U2000 client, run the MOD CELLPDCCHALGO command with the PDCCH Initial Symbol Number and PDCCH Symbol Number Adjust Switch
parameters set to 1 and OFF, respectively.
window, choose Trace Type > LTE > Cell Performance Monitoring > Usage of RB Monitoring. Check the values of Uplink Pucch RB Num, as shown in Figure
11-6. When the number of PDCCH symbols is 1, the eNodeB prefers a small number of RBs for the PUCCH.
Figure 11-6 Uplink Pucch RB Num (1)
4. Run the MOD CELLPDCCHALGO command with the PDCCH Initial Symbol Number parameter set to 3.
window, choose Trace Type > LTE > Cell Performance Monitoring > Usage of RB Monitoring. Check the values of Uplink Pucch RB Num, as shown in Figure
11-7.
When the number of PDCCH symbols is 3, the eNodeB prefers a large number of RBs for the PUCCH. If the value of Uplink Pucch RB Num is greater than that
observed in 3, dynamic PUCCH resource adjustment takes effect.

Figure 11-7 Uplink Pucch RB Num (2)
6. On the U2000 client, run the MOD CELLPDCCHALGO command with the PDCCH Initial Symbol Number and PDCCH Symbol Number Adjust Switch
parameters set to the original values.
UCCH Flexible Configuration
1. On the U2000, run the LST PUCCHCFG command to check and record the value of PUCCH Extended RB Number.
window, choose Trace Type > LTE > Cell Performance Monitoring > Interference Detect Monitoring to start interference monitoring. Check the values of
PUCCH Extended RB Number, as shown in Figure 11-8.
If the observed value of PUCCH Extended RB Number is equal to the configured value of PucchExtendedRBNum, PUCCH flexible configuration takes effect.
Figure 11-8 Interference Detect Monitoring
NOTE:
2. Run the LST CELLPUCCHALGO command to check and record the default value of SRI Low Load Threshold. Then, set it to 20.
3. Run the MOD PUCCHCFG command with the Format1 Code Channel Allocation Mode parameter set to FIXEDMODE(Fixed Mode) and other PUCCH
configuration parameters set to the default values.
4. Enable 17 non-CA and non-SPS UEs to access an activated cell successively and stay in RRC_CONNECTED mode, avoiding the release of PUCCH resources. In
the Uu tracing result, trace and record the sr-PUCCH-ResourceIndex IE in the RRC_CONN_SETUP message of all UEs, as shown in Figure 11-9.
If the modulo-36 operation results of Format1/1a/1b codes indicated by all sr-PUCCH-ResourceIndex IEs are 0, 1, 2, and 3, the configuration takes effect.

5. Run the MOD PUCCHCFG command with the Format1 Code Channel Allocation Mode parameter set to RANDOMMODE(Random Mode) and other PUCCH
configuration parameters set to those in 3.
6. Enable 17 UEs that are neither CA UEs nor SPS UEs to access an activated cell successively and stay in RRC_CONNECTED mode, avoiding the release of
PUCCH resources. In the Uu tracing result, record the sr-PUCCH-ResourceIndex IE in the RRC_CONN_SETUP message of all UEs, as shown in Figure 11-9.
7. Run the MOD PUCCHCFG command with the Format1 Code Channel Allocation Mode parameter set to OPTISELECTMODE(OPTISELECTMODE) and other
PUCCH configuration parameters set to those in 3.
8. Enable 17 UEs that are neither CA UEs nor SPS UEs to access an activated cell successively and stay in RRC_CONNECTED mode, avoiding the release of
PUCCH resources. In the Uu tracing result, record the sr-PUCCH-ResourceIndex IE in the RRC_CONN_SETUP message of all UEs, as shown in Figure 11-9.
9. Run the MOD PUCCHCFG command with the Format1 Channel Allocation Mode parameter set to RBSAVINGMODE(RBSAVINGMODE) and SRI Period
Adaptive Switch parameter set to OFF(OFF).
10. Run the MOD CELLQCIPARA command with the QCIx.SriPeriod parameter set to 5ms and other PUCCH configuration parameters set to the values same to
those in 3.
NOTE:
the Uu tracing result, trace and record the sr-PUCCH-ResourceIndex IE in the RRC_CONN_SETUP message of all UEs, as shown in Figure 11-9.
If the modulo-36 operation results of Format1/1a/1b codes indicated by all sr-PUCCH-ResourceIndex IEs are 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17,
18, 19, and 20, respectively, the configuration takes effect.
12. Run the MOD CELLPUCCHALGO command with the SRI Low Load Threshold parameter set to the original value.
NOTE:
2. Run the LST CQIADAPTIVECFG command to check and record the initial value of the PUCCH Periodic CQI Optimize Switch parameter. Then, run the MOD
CQIADAPTIVECFG command with the PUCCH Periodic CQI Optimize Switch parameter set to OFF(Off).
3. Run the LST CELLCQIADAPTIVECFG command to check and record the initial value of the CQI Period Adaptive Switch parameter. Then, run the MOD
CELLCQIADAPTIVECFG command with the CQI Period Adaptive Switch parameter set to ON(On).
4. Run the MOD PUCCHCFG command with the Format2 Code Channel Allocation Mode parameter set to FIXEDMODE(Fixed Mode) and other PUCCH
configuration parameters set to the default values.
5. Enable 8 non-CA UEs to access an activated cell successively and stay in RRC_CONNECTED mode, avoiding the release of PUCCH resources. In the Uu tracing
result, trace and record the cqi-PUCCH-ResourceIndex IE in the RRC_CONN_SETUP message of all UEs, as shown in Figure 11-10.
If the modulo-12 operation results of Format2/2a/2b codes indicated by all cqi-PUCCH-ResourceIndex IEs are 0 and 2 or 0 and 3, the configuration takes effect.

6. Run the MOD PUCCHCFG command with the Format2 Code Channel Allocation Mode parameter set to RANDOMMODE(Random Mode) and other PUCCH
configuration parameters set to those in 3 and 4.
the Uu tracing result, trace and record the cqi-PUCCH-ResourceIndex IE in the RRC_CONN_SETUP message of all UEs, as shown in Figure 11-10.
If the modulo-12 operation results of Format2/2a/2b codes indicated by all cqi-PUCCH-ResourceIndex IEs are 0 and 4 or 0 and 6, the configuration takes effect.
8. Run the MOD CQIADAPTIVECFG command with the PUCCH Periodic CQI Optimize Switch parameter set to the initial value.
9. Run the MOD CELLCQIADAPTIVECFG command with the CQI Period Adaptation parameter set to the initial value.
B Priority Mode Switch
NOTE:
2. Run the LST CELLPUCCHALGO command to check and record the default value of SRI Low Load Threshold. Then, set it to 10.
3. Run the MOD CELLALGOSWITCH command to set PUCCH Resource Adjustment Switch to Off(Off).
4. Run the MOD PUCCHCFG command to set CQI RB number to a value greater than 1 and ACK/SRI Channel Number to a value greater than 36/deltashift. This
ensures that both the numbers of CQI RBs and SRI RBs exceed 1. For example, the CQI RB number parameter can be set to 5 and ACK/SRI Channel Number
parameter can be set to 121.
5. Run the MOD PUCCHCFG command to set RB Priority Mode Switch to ON(On).
6. Enable seven UEs to access an activated cell successively and stay in RRC_CONNECTED mode, avoiding the release of PUCCH resources. In the Uu tracing
result, trace and record the sr-PUCCH-ResourceIndex and cqi-PUCCH-ResourceIndex IEs in the RRC_CONN_SETUP message of all UEs, as shown in Figure 11-9
and Figure 11-10, respectively.
The setting of RB Priority Mode Switch takes effect when the following requirements are met:
• Any Format1/1a/1b code indicated by all sr-PUCCH-ResourceIndex IEs is a subnet of {0,(36/deltashift)}.
NOTE:
When DeltaShift is set to DS1, DS2, or DS3, the preceding formula uses 1, 2,3, respectively. Therefore, the value of 36/deltashift can be 36, 18, or 12,
depending on the value of DeltaShift.
• Any Format2/2a/2b code indicated by all cqi-PUCCH-ResourceIndex IEs is a subnet of {0,12}.
CC HARQ-ACK Resources
NOTE:
2. Run the MOD PUCCHCFG command with the Format3 RB Number parameter set to 1 and Max 2CC ACK Channel Number parameter set to MAX_CH_NUM8
(Ch8).
3. Run the MOD CELLALGOSWITCH command with the SCCAckResourceCfgSw and Dl2CCAckResShareSw options selected.
4. Enable 10 UEs to access an activated cell successively. Configure them as 2CC UEs and enable them to stay in RRC_CONNECTED mode. In the Uu tracing result,
trace and record the n1PUCCH-AN-CS-List-r10 IE in the RRC_CONN_RECFG message of all UEs.
5. Enable 10 UEs to access the activated cell successively. Configure them as 3CC UEs and enable them to stay in RRC_CONNECTED mode. In the Uu tracing
result, trace and record the n3PUCCH-AN-List-r10 IE in the RRC_CONN_RECFG message of all UEs.
6. Run the MOD PUCCHCFG command with the Format3 RB Number parameter set to 2 and Max 2CC ACK Channel Number parameter set to MAX_CH_NUM16
(Ch16).
7. Repeat 4.
8. Repeat 5.
9. Record the number of 2CC ACK codes in the n1PUCCH-AN-CS-List-r10 IE and number of Format3 codes in the n3PUCCH-AN-List-r10 IE of all UEs in the
preceding steps.
• The setting of SCCAckResourceCfgSw and Max 2CC ACK Channel Number takes effect when the following conditions are met:
◾ The number of 2CC ACK codes in the n1PUCCH-AN-CS-List-r10 IE of all UEs in 4 is less than or equal to 8.
◾ The number of 2CC ACK codes in the n1PUCCH-AN-CS-List-r10 IE of all UEs in 7 is greater than 8 but less than or equal to 16.
• The setting of Format3 RB Number takes effect when the following conditions are met:
◾ The number of 2CC ACK codes in the n3PUCCH-AN-List-r10 IE of all UEs in 5 is less than or equal to 5.
◾ The number of 2CC ACK codes in the n3PUCCH-AN-List-r10 IE of all UEs in 8 is greater than 5 but less than or equal to 10.
N/A
11.4.6 Deactivation


activating SRI Period Adaptation
1. Run the MOD CELLQCIPARA command to set the SRI period.

2. Run the MOD GLOBALPROCSWITCH command to turn off the SRI period adaptation switch.
activating Dynamic PUCCH Resource Adjustment
1. Run the MOD PUCCHCFG command to set the Delta shift, Semi-persistent ACK and SRI Sub Channel, and CQI RB number parameters.
NOTICE:
When you reconfigure the Delta shift, Format1 Channel Allocation Mode, ACK/SRI Channel Number, CQI RB number, Format3 RB Number, and Max 2CC
ACK Channel Number parameters, the cell is automatically reset and PUCCH resources are allocated based on new configuration values immediately.
2. Run the MOD CELLALGOSWITCH command to turn off the PUCCH resource adjustment switch.
NOTICE:
The cell is reset after the execution of this command.
activating PUCCH Flexible Configuration
Run the MOD CELLALGOSWITCH command to turn off the PUCCH flexible configuration switch.
NOTICE:
The cell is reset after the execution of this command and then allocated PUCCH resources on the band edges.
activating SRI Period Adaptation
MOD CELLQCIPARA: LOCALCELLID=0, QCI=9, SRIPERIOD=ms20;

MOD PUCCHCFG:LOCALCELLID=0,SRIPERIODADAPTIVE=OFF;
activating Dynamic PUCCH Resource Adjustment
MOD PUCCHCFG:LOCALCELLID=0,DELTASHIFT=DS1_DELTA_SHIFT,NASRICHNUM=6,CQIRBNUM=1;
MOD CELLALGOSWITCH:LOCALCELLID=0,PUCCHALGOSWITCH=PucchSwitch-0;
activating PUCCH Flexible Configuration
MOD CELLALGOSWITCH: LOCALCELLID=0,PUCCHALGOSWITCH=PucchFlexCfgSwitch-0;
tting the Format1 Channel Allocation Mode to the Fixed Mode
MOD PUCCHCFG: LOCALCELLID=0,FORMAT1CHALLOCMODE=FIXEDMODE;
tting the Format2 Channel Allocation Mode to the Fixed Mode
MOD PUCCHCFG: LOCALCELLID=0,FORMAT2CHALLOCMODE=FIXEDMODE;
sabling the RB Priority Mode for the PUCCH Resource Allocation Policy
MOD PUCCHCFG: LOCALCELLID=0,PUCCHALLOCPOLICY=RbPriorityModeSW-0;
sabling the SCC ACK Resource Configuration Switch
MOD CELLALGOSWITCH: LOCALCELLID=0,PUCCHALGOSWITCH= SCCAckResourceCfgSw-0;
5 PUCCH Monitoring
UCCH Usage
Evaluate the gains based on the following counters one week before and after dynamic PUCCH resource adjustment is enabled.
L.ChMeas.PRB.PUCCH.Avg Average number of used PRBs over the PUCCH

L.Traffic.User.Avg Average number of users in a cell
L.Thrp.bits.UL Total uplink traffic volume for PDCP PDUs in a cell
If any of the following changes occurs after dynamic PUCCH resource adjustment is enabled:
• The number of PUCCH RBs in a cell decreases.

• The number of UEs in a cell increases.
• The total uplink traffic volume in a cell increases.
The dynamic PUCCH resource adjustment brings gains.
UCCH Resource Allocation
Evaluate whether a cell meets PUCCH resource requirements based on the following counter during a period.
L.RRC.SetupFail.ResFail.PUCCH Number of RRC connection setup failures due to PUCCH resource allocation failure
A smaller value indicates better PUCCH resource requirement satisfaction and better user experience.
6 Performance Optimization
To optimize the network performance in non-ultra-high-speed mobility scenarios, enable SRI period adaptation and dynamic PUCCH resource adjustment. When the uplink
band edges experience severe interference, enable PUCCH flexible configuration to mitigate or even cancel the interference with the PUCCH. To optimize RRC setup delay
performance in CA and SPS scenarios, select the SriPeriodCfgOptSW option.

7 Possible Issues
N/A
12 Engineering Guidelines for SRS Resource Management
1 When to Use
It is recommended that SRS-related features be set as follows:
• You are advised to retain the default value BOOLEAN_TRUE(True) of the SRSCfg.SrsCfgInd parameter.
• When the SRSCfg.SrsCfgInd parameter is set to BOOLEAN_TRUE(True), the SRSCfg.FddSrsCfgMode parameter is set to ADAPTIVEMODE(Adaptive Mode) by
default.
◾ For normal cells, it is recommended that the SRSCfg.FddSrsCfgMode parameter be set to ADAPTIVEMODE(Adaptive Mode). If the cell bandwidth is 5
MHz or smaller, it is recommended that the TimeAlignmentTimer.TimingResOptSwitch parameter be set to ON(On).
◾ For SFN, CSPC, high-speed, or ultra-high-speed cells, it is recommended that the SRSCfg.FddSrsCfgMode parameter be set to DEFAULTMODE(Default
Mode).
• Dynamic adjustment to the cell-specific SRS subframe configuration is enabled by default. It is recommended that this feature be used in normal situations.
• UE-specific SRS period adaptation is enabled by default. It is recommended that this feature be used in normal situations.
• The SrsSubframeRecfgOptSwitch option of the SRSCFG.SrsAlgoOptSwitch parameter is cleared by default. In FDD+TDD mixed network scenarios, you are
advised to select the SrsSubframeRecfgOptSwitch option if the following conditions are met:
◾ The SRSCfg.SrsCfgInd parameter is set to BOOLEAN_TRUE.
◾ The SRSCfg.FddSrsCfgMode parameter is set to DEFAULTMODE.
◾ The SrsSubframeRecfSwitch option of the CellAlgoSwitch.SrsAlgoSwitch parameter is selected.
N/A
3 Planning
None
4 Deployment
12.4.1 Requirements
None
None
cense
None
12.4.2 Precautions
Do not reconfigure the SRSCfg.FddSrsCfgMode, SRSCfg.SrsSubframeCfg, SRSCfg.AnSrsSimuTrans, or eNBCellRsvdPara.RsvdSwPara3 parameter while a cell is running.
Otherwise, ongoing services in the cell will be interrupted.

quired Data
The following table describes the parameters that must be set in the SRSCfg MO to configure the SRS subframe configuration index and whether an SRS and an ACK/NACK
can be simultaneously transmitted.
SRS Configuration Indicator SRSCfg.SrsCfgInd This parameter specifies whether to configure SRS resources for UEs in a Network plan
cell. The default value BOOLEAN_TRUE(True) is recommended. (negotiation not
required)
SRS ACK/NACK SRSCfg.AnSrsSimuTrans This parameter specifies whether the SRS and the ACK/NACK or SR on the Network plan
simultaneous transmission PUCCH can be simultaneously transmitted using the same time resources. (negotiation not
The value BOOLEAN_TRUE(True) is recommended. required)
SRS subframe configuration SRSCfg.SrsSubframeCfg This parameter specifies the index of the SRS subframe configuration for the Network plan
cell. This parameter takes effect if the FDD SRS Configuration Mode (negotiation not
parameter is set to DEFAULTMODE(Default Mode) and the required)
SrsSubframeRecfSwitch option of the CellAlgoSwitch.SrsAlgoSwitch
parameter is deselected. The value SC3(3) is recommended.
FDD SRS Configuration SRSCfg.FddSrsCfgMode This parameter specifies the allocation mode of cell-specific SRS resources. Network plan
Mode This parameter must be set when the SRSCfg.SrsCfgInd parameter is set to (negotiation not
BOOLEAN_TRUE(True). For normal cells, it is recommended that this required)
parameter be set to ADAPTIVEMODE(Adaptive Mode) (applicable only to
macro cells that use LBBPd or UBBP). For SFN, CSPC, high-speed, or ultra-
high-speed cells, it is recommended that this parameter be set to
DEFAULTMODE(Default Mode).

The following table describes the parameter that must be set in the CellAlgoSwitch MO to configure the switch for SRS subframe configuration adjustment.
SoundingRS algorithm CellAlgoSwitch.SrsAlgoSwitch This parameter specifies whether to enable dynamic adjustment to the cell- Network plan
switch specific SRS subframe configuration. This parameter takes effect if the FDD (negotiation not
SRS Configuration Mode parameter is set to DEFAULTMODE(Default required)
Mode). It is recommended that the SrsSubframeRecfSwitch option of this
parameter be selected.
The following table describes the parameters that must be set in the CellSrsAdaptiveCfg MO to configure the UE-specific SRS period adaptation switch and SRS period.
SRS Period Adaptive CellSrsAdaptiveCfg.SrsPeriodAdaptive This parameter specifies whether to enable UE-specific SRS period adaptation. Network
Switch This parameter takes effect if the FDD SRS Configuration Mode parameter is plan
set to DEFAULTMODE(Default Mode). The value ON(On) is recommended. (negotiation
not
required)
User SRS Period CellSrsAdaptiveCfg.UserSrsPeriod This parameter specifies the UE-specific SRS period. This parameter takes Network
effect if the FDD SRS Configuration Mode parameter is set to plan
DEFAULTMODE(Default Mode) and the (negotiation
CellSrsAdaptiveCfg.SrsPeriodAdaptive parameter is set to OFF(Off). The not
value ms40(40ms) is recommended. required)
None

1. Run the MOD SRSCFG command to set the allocation mode of SRS resources, the SRS subframe configuration, and whether an SRS and an ACK/NACK can be
simultaneously transmitted.
2. Run the MOD CELLALGOSWITCH command to turn on the SRS algorithm switch.
3. Run the MOD SRSADAPTIVECFG command to turn on the SRS period adaptation switch.

MOD SRSCFG:LOCALCELLID=0,SRSSUBFRAMECFG=SC3,ANSRSSIMUTRANS=BOOLEAN_TRUE;
MOD CELLALGOSWITCH:LOCALCELLID=0,SRSALGOSWITCH=SrsSubframeRecfSwitch-1;
MOD CELLSRSADAPTIVECFG: LOCALCELLID=0, SRSPERIODADAPTIVE=ON;
multaneous Transmission of SRS and ACK/NACK
NOTE:
1. On the U2000 client, run the LST SRSCFG command and record the value of SRS ACK/NACK simultaneous transmission.
3. Deactivate the cell, and activate the cell again. Check the value of the IE ackNackSRS-SimultaneousTransmission in the first RRC_SYS_INFO message traced on
the Uu interface.
If the value of this IE is the same as the value of SRS ACK/NACK simultaneous transmission, the parameter setting takes effect.

Figure 12-1 RRC_SYS_INFO message
namic Adjustment to the Cell-specific SRS Subframe Configuration
On the U2000 client, run the LST CELLALGOSWITCH command to check the value of SoundingRS algorithm switch.
If the value of SoundingRS algorithm switch is SrsSubframeRecfSwitch:On, dynamic adjustment to the cell-specific SRS subframe configuration is enabled.
E-specific SRS Period Adaptation
On the U2000 client, run the LST SRSADAPTIVECFG command to check the value of SRS period adaptive switch.
If the value of SRS period adaptive switch is On, UE-specific SRS period adaptation is enabled.
N/A
12.4.6 Deactivation

activating Dynamic Adjustment to Cell-specific SRS Subframe Configuration
1. Run the MOD SRSCFG command to set the SRS subframe configuration parameter.
2. Run the MOD CELLALGOSWITCH command to deactivate dynamic adjustment to cell-specific SRS subframe configuration.
NOTICE:
Adjusting the SRS subframe configuration parameter will interrupt the communication for a short period. Then, the eNodeB allocates SRS resources based on the
adjusted value.
activating UE-specific SRS Period Adaptation
Run the MOD SRSADAPTIVECFG command to set the User SRS period config parameter and deactivate UE-specific SRS period adaptation.
activating Dynamic Adjustment to Cell-specific SRS Subframe Configuration
MOD SRSCFG:LOCALCELLID=0,SRSSUBFRAMECFG=SC3;
MOD CELLALGOSWITCH:LOCALCELLID=0,SRSALGOSWITCH=SrsSubframeRecfSwitch-0;
activating UE-specific SRS Period Adaptation
MOD CELLSRSADAPTIVECFG: LOCALCELLID=0, SRSPERIODADAPTIVE=OFF, USERSRSPERIOD=ms40;
5 SRS Monitoring
ll-specific SRS Bandwidth
1. Run the LST CELL command to query the cell uplink bandwidth.
2. Run the DSP SRSCFG command to query the current cell-specific SRS bandwidth configuration.
3. Based on the cell uplink bandwidth and cell-specific SRS bandwidth configuration, search Table 6-2 through Table 6-5 for the actual cell-specific SRS bandwidth.
4. Check the ratio of the cell-specific SRS bandwidth to the cell uplink bandwidth.
A higher ratio indicates that this bandwidth provides higher uplink coverage, which benefits uplink frequency-selective scheduling, link adaptation, and power control.
ll-specific SRS Subframe

NOTE:
2. Check the value of the IE srs-SubframeConfig in the RRC_SYS_INFO message, as shown in Figure 12-2.
Figure 12-2 Querying cell-specific SRS Subframe configuration
3. Search Table 6-1 for the cell-specific SRS subframe period and subframe offset corresponding to the value of srs-SubframeConfig.
4. Check the ratio of the number of cell-specific SRS subframes to the total number of subframes in the cell during a period of time.
A higher ratio indicates more resources occupied by SRSs, more resources available in the cell, but less resources allocated for the PUSCH.
5. Check where the number of cell-specific SRS subframes changes during the tracing procedure.
If there is no RRC_SYS_INFO message in the Uu tracing result, the number has not changed. If the number has increased or decreased, the eNodeB adjusts the
SRS resources to adapt to the load changes on SRS resources.
E-specific SRS
Use the following counters to monitor UE-specific SRSs:
L.Traffic.User.SRS.Avg Average number of UEs configured with sounding reference signal (SRS)
resources in a cell
L.Traffic.User.SRS.Max Maximum number of UEs configured with sounding reference signal (SRS)
resources in a cell
L.Traffic.User.Avg Average number of users in a cell
L.Traffic.User.Max Maximum number of users in a cell
L.RRC.SetupFail.ResFail.SRS Number of RRC connection setup failures due to SRS resource allocation
failure
Check the number of UEs configured with SRS resources using L.Traffic.User.SRS.Avg and L.Traffic.User.SRS.Max and the total number of UEs in the cell using
L.Traffic.User.Avg and L.Traffic.User.Max. Check the number of RRC connection setup failures due to SRS resource allocation failures using L.RRC.SetupFail.ResFail.SRS.
Check the ratio of the number of UEs configured with SRS resources to the total number of UEs in the cell or the number of RRC connection setup failures due to SRS resource
allocation failures during a period of time. A higher ratio or fewer failures indicate a higher degree to which UEs' SRS resource requirements are satisfied and accordingly better
user experience.
6 Parameter Optimization
To optimize the network performance, enable dynamic adjustment to the cell-specific SRS subframe configuration and UE-specific SRS period adaptation in all scenarios.
In FDD+TDD mixed networking scenarios, you are advised to select the SrsSubframeRecfgOptSwitch option of the eNBCellRsvdPara.RsvdSwPara3 parameter for FDD cells
if the following conditions are met. This avoids handover failure from TDD cells to FDD cells due to compatibility problems of certain UEs in the TDD cells, thereby improving the
handover success rate of TDD cells but slightly decreasing the uplink throughput of FDD cells.
• The BOOLEAN option of the SRSCfg.SrsCfgInd parameter for FDD cells is selected.
• The SRSCfg.FddSrsCfgMode parameter is set to DEFAULTMODE.
• The SrsSubframeRecfSwitch option of the CellAlgoSwitch.SrsAlgoSwitch parameter is selected.
7 Possible Issues
N/A

13 Parameters
CellPdcchAlgo PdcchCapacityImproveSwitch MOD CELLPDCCHALGO LBFD-002003 Physical Channel Meaning: Indicates whether to enable
LST CELLPDCCHALGO Management optimization on PDCCH capacity expansion.
For LTE FDD networks, if this parameter is
set to ON(On), (1) the initial value for closed-
loop adjustment on PDCCH aggregation level
applies only to SRBs; (2) if a UE fails to be
allocated with CCEs, the eNodeB reallocates
CCEs to the UE by increasing the PDCCH
power and decreasing the PDCCH
aggregation level for the UE. If this parameter
is set to OFF(Off), (1) the initial value for
closed-loop adjustment on PDCCH
aggregation level applies to both SRBs and
DRBs; (2) if a UE fails to be allocated with
CCEs, the eNodeB does not reallocate CCEs
to the UE by increasing the PDCCH power
and decreasing the PDCCH aggregation
level for the UE. For LTE TDD networks, if
this parameter is set to ON(On), the eNodeB
reallocates CCEs to a UE, if the UE fails to
be allocated with CCEs, by increasing the
PDCCH transmit power and decreasing the
PDCCH aggregation level for the UE. If this
parameter is set to OFF(Off), the eNodeB
does not reallocate CCEs to a UE, if the UE
fails to be allocated with CCEs, by increasing
the PDCCH power and decreasing the
PDCCH aggregation level for the UE.
Unit: None
CellPdcchAlgo PdcchPowerEnhancedSwitch MOD CELLPDCCHALGO LBFD-002003 / Physical Channel Meaning: Indicates whether to enable
LST CELLPDCCHALGO TDLBFD-002003 Management enhanced PDCCH power control. If this
switch is turned on, the eNodeB selects
appropriate PDCCH transmit power based on
channel quality to increase PDCCH capacity.
This parameter is valid only for FDD, not for
TDD.
Unit: None
PUCCHCfg Format1ChAllocMode MOD PUCCHCFG LBFD-002003 / Physical Channel Meaning: Indicates the mode for allocating
LST PUCCHCFG TDLBFD-002003 Management PUCCH format 1/1a/1b code channel
resources. The setting of this parameter
takes effect only when the DeltaShift
parameter is set to DS1_DELTA_SHIFT
(ds1). If the Format1ChAllocMode parameter
is set to FIXEDMODE(Fixed Mode),
consecutive PUCCH format 1/1a/1b code
channel resources are always allocated. If
the Format1ChAllocMode parameter is set to
RANDOMMODE(Random Mode), PUCCH
format 1/1a/1b code channel resources are
randomly allocated. If this parameter is set to
OPTISELECTMODE(OPTISELECTMODE),
PUCCH format 1 code channel resources are
allocated based on the optimized selection
mode. If this parameter is set to
RBSAVINGMODE(RB Saving Mode),
PUCCH format 1/1a/1b code channel
resources are allocated in such a way where
an RB is allocated to as many UEs as
possible to save RBs.The RBSAVINGMODE
value takes effect only in LTE FDD. When
this parameter is set to RBSAVINGMODE for
LTE TDD, the effect is the same as that set
to RANDOMMODE.
GUI Value Range: FIXEDMODE(Fixed
Mode), RANDOMMODE(Random Mode),
OPTISELECTMODE(OPTISELECTMODE),
RBSAVINGMODE(RBSAVINGMODE)
Unit: None
Actual Value Range: FIXEDMODE,
RANDOMMODE, OPTISELECTMODE,
RBSAVINGMODE
Default Value: FIXEDMODE(Fixed Mode)
PUCCHCfg Format3RbNum MOD PUCCHCFG LBFD-002003 / Physical Channel Meaning: Indicates the maximum number of
LST PUCCHCFG TDLBFD-002003 Management RBs that can be used by PUCCH resources


in Format 3. This parameter takes effect only
when the SCCAckResourceCfgSw option of
the PucchAlgoSwitch parameter is selected.
Unit: None
Default Value: 2
PUCCHCfg Max2CCAckChNum MOD PUCCHCFG LBFD-002003 / Physical Channel Meaning: Indicates the maximum number of
LST PUCCHCFG TDLBFD-002003 Management code channels that can be used by SCC
ACKs in 2CC CA scenarios. This parameter
takes effect only when options
Dl2CCAckResShareSw and
SCCAckResourceCfgSw of the
PucchAlgoSwitch parameter are selected.
GUI Value Range: MAX_CH_NUM8(Ch8),
MAX_CH_NUM16(Ch16), MAX_CH_NUM24
(Ch24), MAX_CH_NUM32(Ch32)
Unit: None
Actual Value Range: MAX_CH_NUM8,
MAX_CH_NUM16, MAX_CH_NUM24,
MAX_CH_NUM32
Default Value: MAX_CH_NUM32(Ch32)
CellAlgoSwitch PucchAlgoSwitch MOD LBFD-002003 / Physical Channel Meaning:

CELLALGOSWITCH TDLBFD-002003 Management PucchSwitch: Indicates whether to enable the
LST CELLALGOSWITCH
PUCCH resource adjustment algorithm.
If this option is selected, PUCCH resource
adjustment is initiated when the PUCCH
resources are insufficient or excessive. If this
option is deselected, PUCCH resource
adjustment is disabled.
PucchFlexCfgSwitch: Indicates whether to
enable PUCCH flexible configuration. This
function does not take effect if an LBBPc is
used or the cell bandwidth is 1.4 or 3 MHz.
When PUCCH flexible configuration is
enabled, frequency-domain uplink ICIC and
uplink frequency hopping scheduling cannot
be used. If this option is selected, an equal
number of RBs (specified by the
PucchExtendedRBNum parameter) are
separately added to both ends of the uplink
band allocated for the PUCCH. The total
number of extension PUCCH RBs equals the
PucchExtendedRBNum parameter value
multiplied by 2, and the extension RBs can
be used for PUSCH scheduling. This option
applies only to LTE FDD.
Dl2CCAckResShareSw: Indicates whether to
enable PUCCH ACK channel resource
sharing for downlink 2CC CA. The eNodeB
divides the ACK channel resources on a PCC
for downlink 2CC CA into four groups. If this
option is deselected, CA UEs scheduled on
each SCC associated with this PCC are
allowed to use the ACK channel resources in
only one group. If this option is selected, CA
UEs scheduled on each SCC associated with
this PCC can use the ACK channel resources
in any group.
SCCAckResourceCfgSW: Indicates whether
to enable SCC ACK resource configuration. If
this option is selected, the eNodeB controls
the maximum number of RBs that can be
used by PUCCH format 3 and the maximum
number of code channels that can be used
by SCC ACKs in 2CC CA scenarios
according to the settings of the
Format3RBNum and Max2CCAckChNum
parameters in the PUCCHCfg MO,
respectively. If this option is deselected, the
eNodeB controls the maximum number of
RBs that can be used by PUCCH format 3
and the maximum number of code channels
that can be used by SCC ACKs in 2CC CA
scenarios based on related algorithms.
GUI Value Range: PucchSwitch
(PucchSwitch), PucchFlexCfgSwitch
(PucchFlexCfgSwitch),
Dl2CCAckResShareSw
(Dl2CCAckResShareSw),
SCCAckResourceCfgSw
(SCCAckResourceCfgSw)
Unit: None
Actual Value Range: PucchSwitch,
PucchFlexCfgSwitch,
Dl2CCAckResShareSw,
SCCAckResourceCfgSw
Default Value: PucchSwitch:On,
PucchFlexCfgSwitch:Off,


Dl2CCAckResShareSw:On,
SCCAckResourceCfgSw:Off
CellPdcchAlgo EpdcchAlgoSwitch MOD CELLPDCCHALGO LBFD- Physical Channel Meaning: Indicates whether to enable
LST CELLPDCCHALGO 002003/TDLBFD- Management algorithms related to the EPDCCH.
002003 EpdcchFunctionSwitch: Indicates whether to
support EPDCCH. If this option is selected,
EPDCCH is supported.
GUI Value Range: EpdcchFunctionSwitch
(EpdcchFunctionSwitch)
Unit: None
Actual Value Range: EpdcchFunctionSwitch
Default Value: EpdcchFunctionSwitch:Off
CellPdcchAlgo CceThdtoEnableEpdcch MOD CELLPDCCHALGO LBFD-002003 / Physical Channel Meaning: Indicates the CCE usage threshold
LST CELLPDCCHALGO TDLBFD-002003 Management for configuring the EPDCCH. If the CCE
usage is greater than this parameter value,
the eNodeB configures EPDCCH resources
for newly accessed UEs.
Unit: None
Default Value: 80
CellPdcchAlgo RbThdtoEnableEpdcch MOD CELLPDCCHALGO LBFD-002003 / Physical Channel Meaning: Indicates the downlink RB usage
LST CELLPDCCHALGO TDLBFD-002003 Management threshold for configuring EPDCCH. If the
downlink RB usage is less than this
parameter value, the eNodeB configures
EPDCCH resources for newly accessed UEs.
Unit: None
Default Value: 60
CellPdcchAlgo CceThdtoDisableEpdcch MOD CELLPDCCHALGO LBFD-002003 / Physical Channel Meaning: Indicates the CCE usage threshold
LST CELLPDCCHALGO TDLBFD-002003 Management for disabling EPDCCH. If the CCE usage is
lower than this parameter value, the eNodeB
disables the EPDCCH.
Unit: None
Default Value: 60
CellPdcchAlgo EcceThdtoDisableEpdcch MOD CELLPDCCHALGO LBFD-002003 / Physical Channel Meaning: Indicates the ECCE usage
LST CELLPDCCHALGO TDLBFD-002003 Management threshold for disabling EPDCCH. If the ECCE
usage is lower than this parameter value, the
eNodeB disables the EPDCCH.
Unit: None
Default Value: 5
CellPdcchAlgo RbThdtoDisableEpdcch MOD CELLPDCCHALGO LBFD-002003 / Physical Channel Meaning: Indicates the downlink RB usage
LST CELLPDCCHALGO TDLBFD-002003 Management threshold for disabling EPDCCH. If the
downlink RB usage is greater than this
parameter value, the eNodeB disables the
EPDCCH.
Unit: None
Default Value: 80
CellPdcchAlgo PdcchInitialCceAdjustValue MOD CELLPDCCHALGO LBFD-002003 Physical Channel Meaning: Indicates the PDCCH initial
LST CELLPDCCHALGO Management aggregation level adjustment. This parameter
applies only to LTE FDD.
Unit: None
Default Value: -10
PUCCHCfg Format2ChAllocMode MOD PUCCHCFG LBFD-002003 / Physical Channel Meaning: Indicates the channel resource
LST PUCCHCFG TDLBFD-002003 Management allocation mode for PUCCH format 2/2a/2b. If
this parameter is set to FIXEDMODE,
consecutive channel resources are allocated
for PUCCH format 2/2a/2b. If this parameter
is set to RANDOMMODE, channel resource
allocation is optimized for PUCCH format
2/2a/2b.
GUI Value Range: FIXEDMODE(Fixed
Mode), RANDOMMODE(Random Mode)
Unit: None
Actual Value Range: FIXEDMODE,
RANDOMMODE
Default Value: FIXEDMODE(Fixed Mode)
PUCCHCfg PucchAllocPolicy MOD PUCCHCFG LBFD-002003 / Physical Channel Meaning: Indicates the PUCCH resource
LST PUCCHCFG TDLBFD-002003 Management allocation policy. RbPriorityModeSW:
Indicates whether RB priority mode takes
effect when the eNodeB allocates new
PUCCH code channel resources. This option


takes effect only when the PucchSwitch
option of the PucchAlgoSwitch parameter is
deselected. If this option is selected, eNodeB
preferentially uses different RBs when
allocating new PUCCH code channel
resources. In this way, UEs evenly reuse all
RBs, decreasing inter-code-channel
interference on UEs in the cell and improving
PUCCH detection performance. If this option
is deselected, the eNodeB fully uses each
PUCCH RB one by one.
GUI Value Range: RbPriorityModeSW
(RbPriorityModeSW)
Unit: None
Actual Value Range: RbPriorityModeSW
Default Value: RbPriorityModeSW:Off
SRSCfg SrsAlgoOptSwitch MOD SRSCFG LBFD-002003 Physical Channel Meaning: Controls SRS algorithm
LST SRSCFG Management optimization. SrsSubframeRecfgOptSwitch:
Controls SRS subframe reconfiguration
optimization. This option applies only to LTE
FDD. If this option is selected, the SRS
subframe reconfiguration path is optimized to
avoid the configurations that may cause UE
compatibility issues. If this option is
deselected, the SRS subframe
reconfiguration path is not optimized.
GUI Value Range:
SrsSubframeRecfgOptSwitch
(SrsSubframeRecfgOptSwitch)
Unit: None
Actual Value Range:
SrsSubframeRecfgOptSwitch
Default Value:
SrsSubframeRecfgOptSwitch:Off
PHICHCfg PhichDuration MOD PHICHCFG LBFD-002003 / Physical Channel Meaning: Indicates the PHICH duration type.
LST PHICHCFG TDLBFD-002003 Management If this parameter is set to NORMAL, the
LOFD-001051 Compact Bandwidth number of OFDM symbols occupied by the
LBFD-002009 / Broadcast of system PDCCH is automatically adjusted. If this
TDLBFD-002009 information parameter is set to EXTENDED, the number
of OFDM symbols occupied by the PDCCH is
fixed. Specifically, this number is fixed to 3 or
4 for 1.4 MHz cells and 3 for cells with other
bandwidths. For the mapping between the
type and the duration, see 3GPP TS 36.211.
GUI Value Range: NORMAL, EXTENDED
Unit: None
Actual Value Range: NORMAL, EXTENDED
Default Value: NORMAL
PHICHCfg PhichResource MOD PHICHCFG LBFD-002003 / Physical Channel Meaning:

LST PHICHCFG TDLBFD-002003 Management Indicates a coefficient that is used to
LOFD-001051 Compact Bandwidth calculate the resources used by the PHICH
LBFD-002009 / Broadcast of system for the cell. It corresponds to the Ng
TDLBFD-002009 information parameter in the protocol.
For details on the usage of the Ng parameter,
see 3GPP TS 36.211.
GUI Value Range: ONE_SIXTH, HALF, ONE,
TWO
Unit: None
Actual Value Range: ONE_SIXTH, HALF,
ONE, TWO
Default Value: ONE
CellPdcchAlgo PdcchSymNumSwitch MOD CELLPDCCHALGO LBFD-002003 / Physical Channel Meaning: Indicates whether to enable
LST CELLPDCCHALGO TDLBFD-002003 Management 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(Off), the number of
OFDM symbols occupied by the PDCCH is
fixed and cannot be dynamically adjusted. If
this parameter is set to ON(On), the number
dynamically adjusted based on the required
number of PDCCH control channel elements
(CCEs). The OFDM symbol adjustment
range can be determined by referring to the
MML reference of the InitPdcchSymNum
parameter. If this parameter is set to
ECFIADAPTIONON(Enhanced CFI Adaption
On), 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. The OFDM symbol
adjustment range can be determined by
referring to the MML reference of the
InitPdcchSymNum parameter.


GUI Value Range: OFF(Off), ON(On),
ECFIADAPTIONON(Enhanced CFI Adaption
On)
Unit: None
Actual Value Range: OFF, ON,
ECFIADAPTIONON
Default Value: ECFIADAPTIONON
(Enhanced CFI Adaption On)
CellPdcchAlgo InitPdcchSymNum MOD CELLPDCCHALGO LBFD-002003 / Physical Channel Meaning: Indicates the number of OFDM
LST CELLPDCCHALGO TDLBFD-002003 Management symbols initially occupied by the PDCCH. If
the switch for dynamic adjustment of the
number of OFDM symbols occupied by the
PDCCH is turned off, this parameter
indicates the number of OFDM symbols that
are always occupied by the PDCCH. For LTE
TDD cells, this parameter indicates the
number of OFDM symbols initially occupied
by PDCCH where only the downlink
scheduling and controlling information is
transmitted in downlink subframes. If the
switch for dynamic adjustment of the number
turned on and the bandwidth is 1.4 MHz or 3
MHz, the PDCCH occupies 4 or 3 OFDM
symbols, respectively, and this parameter is
invalid. If the switch is turned on and the
bandwidth is 5 MHz, 10 MHz, 15 MHz, or 20
MHz, the eNodeB adjusts the number of
OFDM symbols in the range of 1, 2, and 3
when this parameter is set to the default
value 1, or in the range of 2 and 3 when this
parameter is set to 2 or 3. For LTE TDD cells,
if the switch is turned on and the bandwidth is
5 MHz, the eNodeB adjusts the number of
OFDM symbols in the range of 2 and 3 by
default, and this parameter is invalid.
Unit: None
Default Value: 1
CellPdcchAlgo AggLvlSelStrageForDualCW MOD CELLPDCCHALGO LBFD-002003 Physical Channel Meaning: Indicates the policy for control
LST CELLPDCCHALGO Management channel element (CCE) aggregation level
selection of the physical downlink control
channel (PDCCH) in dual-codeword
scenarios. In capacity-based CCE
aggregation level selection of the PDCCH,
set this parameter to
STRATEGYBASEDONCAPACITY. In this
situation, the average CCE aggregation level
of the PDCCH in dual-codeword scenarios
decreases, and more UEs can be supported
on the PDCCH. In coverage-based CCE
aggregation level selection of the PDCCH,
set this parameter to
STRATEGYBASEDONCOVERAGE. In this
situation, both the average CCE aggregation
level of the PDCCH in dual-codeword
scenarios and cell coverage performance
increase. This parameter is set to
STRATEGYBASEDONCAPACITY by
default.This parameter applies only to LTE
FDD.
GUI Value Range:
STRATEGYBASEDONCAPACITY(Capacity-
based Selection Strategy),
STRATEGYBASEDONCOVERAGE
(Coverage-based Selection Strategy)
Unit: None
Actual Value Range:
STRATEGYBASEDONCAPACITY,
STRATEGYBASEDONCOVERAGE
Default Value:
STRATEGYBASEDONCAPACITY(Capacity-
based Selection Strategy)
CellPdcchAlgo PdcchMaxCodeRate MOD CELLPDCCHALGO LBFD-002003 / Physical Channel Meaning: Indicates the maximum coding rate
LST CELLPDCCHALGO TDLBFD-002003 Management on the PDCCH. The coding rate on the
PDCCH cannot exceed this parameter value.
Otherwise the PDCCH aggregation level
must be increase.
Unit: None
Actual Value Range: 0.75~1.2, step:0.01
Default Value: 75
CellPdcchAlgo ComSigCongregLv MOD CELLPDCCHALGO LBFD-002003 / Physical Channel Meaning: Indicates the CCE aggregation
LST CELLPDCCHALGO TDLBFD-002003 Management level for common control signaling. If the
HOSuccRateBoostOptSwitch option of the
HoSignalingOptSwitch parameter is selected,
the PDCCH CCE aggregation level is


changed to level 8 when an RAR message
for a handover is retransmitted.
GUI Value Range: CONGREG_LV4,
CONGREG_LV8
Unit: None
Actual Value Range: CONGREG_LV4,
CONGREG_LV8
Default Value: CONGREG_LV4
CellPdcchAlgo PdcchAggLvlCLAdjustSwitch MOD CELLPDCCHALGO LBFD-002003 / Physical Channel Meaning: Indicates the switch used to enable
LST CELLPDCCHALGO TDLBFD-002003 Management or disable closed-loop adjustment to the
PDCCH aggregation level. If this switch is
turned on, PDCCH aggregation level is
adjusted based on the block error rate
(BLER) of the PDCCH. If this switch is turned
off, PDCCH aggregation level is not adjusted
based on the BLER of the PDCCH.
Unit: None
Default Value: ON(On)
CellAlgoSwitch UlSchSwitch MOD LOFD-001016 / VoIP Semi-persistent Meaning:

CELLALGOSWITCH TDLOFD-001016 Scheduling This parameter indicates the switches related
LST CELLALGOSWITCH
LOFD-001048 / TTI Bundling to uplink (UL) scheduling in the cell. The
TDLOFD-001048 Dynamic Scheduling switches are used to enable or disable
LOFD- Basic Scheduling specific UL scheduling functions.
00101502 / SpsSchSwitch: Indicates whether to enable
MBR>GBR
TDLOFD- semi-persistent scheduling during talk spurts
Configuration
00101502 of VoLTE services. If this option is selected,
UL 2x2 MU-MIMO semi-persistent scheduling is applied during
TDLBFD-002025
UL 2x4 MU-MIMO talk spurts of VoLTE services. If this option is
LBFD-070102 /
AMC deselected, dynamic scheduling is applied
TDLBFD-070102
during talk spurts of VoLTE services.
LOFD-001002
SinrAdjustSwitch: Indicates whether to adjust
LOFD-001058 / the measured signal to interference plus
TDLOFD-001058 noise ratio (SINR) based on ACK/NACK in
LBFD-001006 UL hybrid automatic repeat request (HARQ)
processes.
PreAllocationSwitch: Indicates whether to
enable preallocation in the uplink. If this
option is selected: (1) If the
SmartPreAllocationSwitch option is
deselected and a UE is in the discontinuous
reception (DRX) state, preallocation is
disabled for the UE in the uplink; (2) If the
SmartPreAllocationSwitch option is
deselected and the UE is not in the DRX
state, preallocation is enabled for the UE in
the uplink; (3) If the
SmartPreAllocationSwitch option is selected
and the SmartPreAllocationDuration
parameter value is greater than 0, smart
preallocation is enabled for the UE in the
uplink; (4) If the SmartPreAllocationSwitch
SmartPreAllocationDuration parameter value
is 0, preallocation is disabled for the UE in
the uplink. If this option is deselected,
preallocation is disabled for the UE in the
uplink. If bearer-level preallocation or bearer-
level smart preallocation is enabled for a
QCI, cell-level preallocation and cell-level
smart preallocation do not apply to UEs with
the QCI.
UlVmimoSwitch: Indicates whether to enable
multi-user MIMO (MU-MIMO) in the UL. If this
option is selected, 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 VoLTE
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 option is selected,
IM component elimination is performed on
UEs. If this option is deselected, IM
component elimination is not performed on


UEs. This option applies only to FDD cells
working in frequency band 20.
SmartPreAllocationSwitch: Indicates whether
to enable uplink smart preallocation when
preallocation is enabled (by selecting
PreAllocationSwitch). If both the
PreAllocationSwitch and
SmartPreAllocationSwitch options are
selected 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
option is selected, 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 option takes
effect only if 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 MU-
MIMO applied. In an LTE TDD cell, this
option takes effect only when the cell is
configured with subframe configuration 2 or
5. After this option 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 IBLER adjustment
algorithm. If this option is selected, the target
IBLER is adjusted for CEUs in TDD cells to
increase the cell edge throughput. If this
option is selected independently for FDD
cells, the algorithm does not take effect.
UlEnhancedFssSwitch: Indicates whether to
enable uplink load-based enhanced
frequency selective scheduling. This option
applies only to FDD cells.
UlIicsAlgoSwitch: Indicates whether to enable
the UL IICS algorithm. If this option is
selected, interference can be reduced based
on accurate detection of user attributes and
resource scheduling coordination, thereby
increasing the cell edge throughput. This
UlEnhancedSrSchSwitch: Indicates whether
uplink re-scheduling is performed only when
the On Duration timer for the DRX long cycle
starts. Uplink re-scheduling is required if the
number of HARQ retransmissions for a
scheduling request (SR) reaches the
maximum value but the scheduling still fails.
If this option is selected, uplink re-scheduling
is performed only when the On Duration timer
for the DRX long cycle starts. If this option is
deselected, 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 this option be
selected in live networks.
SchedulerCtrlPowerSwitch: Indicates
whether the uplink scheduler performs
scheduling without considering power control
restrictions. If this option is selected, the
uplink scheduler performs scheduling without
considering power control restrictions, which
ensures full utilization of the transmit power
for all UEs. If this option is deselected, 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 option is selected, 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 guaranteed bit rate (GBR) on
the GBR bearer. If this option is selected, the
eNodeB performs uplink scheduling on GBR
bearers based on the MBR and GBR. If this
option is deselected, 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 option is selected, the eNodeB
prioritizes UEs based on the MBRs during
uplink scheduling. This option applies only to
LTE TDD.
UeAmbrUlSchSwitch: Indicates whether the
eNodeB performs uplink scheduling based on
the aggregate maximum bit rate (AMBR) of
UEs. If this option is selected, the eNodeB
prioritizes UEs based on the UE-AMBRs
during uplink scheduling. This option applies
only to LTE TDD.
UlEnhancedDopplerSwitch: Indicates
whether to enable enhanced uplink
scheduling based on mobility speed. If this
option is selected, enhanced uplink
scheduling based on mobility speed is
enabled. In enhanced uplink scheduling
based on mobility speed, the eNodeB uses
Doppler measurement results to determine
low-speed UEs to further improve UL
performance of low-speed UEs. If this option
is deselected, enhanced uplink scheduling
based on mobility speed is disabled.
Enhanced uplink scheduling based on
mobility speed takes effect only when the
DopMeasLevel parameter is set to CLASS_1
and the UlEnhancedDopplerSwitch option is
selected. This option 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
option is selected, the eNodeB raises the
scheduling priority of UEs sending uplink
access signaling. If this option is deselected,
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 option is selected,
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 the
last two retransmissions and decrease uplink
RBLER. If this option is deselected,
optimization on the scheduling policy for the
last two retransmissions is disabled.
UlInterfFssSwitch: Indicates whether to
enable interference-based uplink frequency-
selective scheduling. This parameter applies
only to LTE FDD.
UlSmallRBSpectralEffOptSw: Indicates
whether to enable spectral efficiency
optimization on uplink small RBs. If this
option is selected, the optimization is
enabled, thereby ensuring that the
transmission block size calculated based on
optimized spectral efficiency is not less than
the traffic volume to be scheduled. If this
option is deselected, the optimization is
disabled.
PuschUsePucchRbSwitch: Indicates whether
PUCCH RBs can be occupied by the
PUSCH. In scenarios with a single user, if
this option is selected, PUCCH RBs can be
occupied by the PUSCH. If this option is
deselected, PUCCH RBs cannot be occupied
by the PUSCH. In scenarios with multiple
users, PUCCH RBs cannot be occupied by
the PUSCH regardless of whether this option
is selected.
PuschDtxSchOptSwitch: If this option is
selected, the eNodeB determines whether to


perform adaptive retransmission during UL
scheduling based on the PUSCH DTX
detection result. This option 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
option applies only to TDD cells.
PrachRbReuseSwitch: If this option is
selected, the PUSCH and PRACH
transmissions can use the same resource. If
this option is deselected, the PUSCH and
PRACH transmissions cannot use the same
resource. This option applies only to TDD
cells.
ULFSSAlgoswitch: If this option is
deselected, uplink frequency-selective
scheduling is disabled. If this option is
selected, uplink frequency-selective
scheduling is enabled. This option applies
only to LTE TDD.
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. This option applies only to LTE
FDD cells.
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.
HighOrderVMIMOSwitch: Indicates whether
to enable high-order VMIMO. High-order
VMIMO is enabled only when this option is
selected. This option applies only to TDD
cells.
VMIMOReduceMCSRiseRBSwitch: Indicates
whether VMIMO pairing is performed for UEs
whose MCS index is reduced to increase the
number of RBs. VMIMO is performed for UEs
whose MCS index is reduced to increase the
number of RBs only when this option is
selected. This option applies only to TDD
cells.
VoLTEUeVmimoSwitch: Indicates whether
VMIMO pairing is performed for VoLTE UEs.
VMIMO pairing is performed for VoLTE UEs
only when this option is selected. This option
applies only to TDD cells.
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
(UlLast2RetransSchOptSwitch),
UlInterfFssSwitch(UlInterfFssSwitch),
UlSmallRBSpectralEffOptSw
(UlSmallRBSpectralEfficiencyOptSw),
PuschUsePucchRbSwitch
(PuschUsePucchRbSwitch),
PuschDtxSchOptSwitch
(PuschDtxSchOptSwitch), ULFSSAlgoSwitch
(ULFSSAlgoSwitch), PrachRbReuseSwitch
(PrachRbReuseSwitch), SrSchDataAdptSw
(SrSchDataAdptSw), UlFssUserThdStSwitch
(UlFssUserThdStSwitch),
HighOrderVMIMOSwitch
(HighOrderVMIMOSwitch),
VMIMOReduceMCSRiseRBSwitch
(VMIMOReduceMCSRiseRBSwitch),
VoLTEUeVmimoSwitch
(VoLTEUeVmimoSwitch)
Unit: None


Actual Value Range: SpsSchSwitch,
SinrAdjustSwitch, PreAllocationSwitch,
UlVmimoSwitch, TtiBundlingSwitch,
ImIcSwitch, SmartPreAllocationSwitch,
PuschDtxSwitch, UlIblerAdjustSwitch,
UlEnhancedFssSwitch,
UlEnhancedSrSchSwitch,
SchedulerCtrlPowerSwitch, UlIicsAlgoSwitch,
UlMinGbrSwitch, UlMbrCtrlSwitch,
MbrUlSchSwitch, UeAmbrUlSchSwitch,
UlEnhancedDopplerSwitch,
UlRaUserSchOptSw,
UlLast2RetransSchOptSwitch,
UlInterfFssSwitch,
UlSmallRBSpectralEffOptSw,
PuschUsePucchRbSwitch,
PuschDtxSchOptSwitch, ULFSSAlgoSwitch,
PrachRbReuseSwitch, SrSchDataAdptSw,
UlFssUserThdStSwitch,
HighOrderVMIMOSwitch,
VMIMOReduceMCSRiseRBSwitch,
VoLTEUeVmimoSwitch
Default Value: SpsSchSwitch:Off,
SinrAdjustSwitch:On,
PreAllocationSwitch:On, UlVmimoSwitch:Off,
TtiBundlingSwitch:Off, ImIcSwitch:Off,
SmartPreAllocationSwitch:On,
PuschDtxSwitch:On, UlIblerAdjustSwitch:Off,
UlEnhancedFssSwitch:On,
UlEnhancedSrSchSwitch:On,
SchedulerCtrlPowerSwitch:Off,
UlIicsAlgoSwitch:Off, UlMinGbrSwitch:Off,
UlMbrCtrlSwitch:Off, MbrUlSchSwitch:Off,
UeAmbrUlSchSwitch:Off,
UlEnhancedDopplerSwitch:Off,
UlRaUserSchOptSw:Off,
UlLast2RetransSchOptSwitch:On,
UlInterfFssSwitch:Off,
UlSmallRBSpectralEffOptSw:Off,
PuschUsePucchRbSwitch:Off,
PuschDtxSchOptSwitch:Off,
ULFSSAlgoSwitch:On,
PrachRbReuseSwitch:Off,
SrSchDataAdptSw:On,
UlFssUserThdStSwitch:Off,
HighOrderVMIMOSwitch:Off,
VMIMOReduceMCSRiseRBSwitch:Off,
VoLTEUeVmimoSwitch:Off
CellPdcchAlgo PdcchBlerTarget MOD CELLPDCCHALGO LBFD- PDCCH Utilization Meaning: Indicates the target BLER for
LST CELLPDCCHALGO 070107;TDLBFD- Improvement;Physical PDCCH link adaptation performed when the
002003 Channel PdcchAggLvlCLAdjustSwitch parameter in
Management the CellPdcchAlgo MO is set to ON(On).
Unit: None
Actual Value Range: 0~1, step:0.001
Default Value: 15
CellPdcchAlgo CceRatioAdjSwitch MOD CELLPDCCHALGO LBFD-002003 / Physical Channel Meaning: Indicates the CCE ratio adjustment
LST CELLPDCCHALGO TDLBFD-002003 Management switch for the PDCCH. If this switch is turned
on, the resource allocation algorithm of the
PDCCH dynamically adjusts the UL and DL
CCE ratios within each transmission time
interval (TTI) based on CCE usages in UL
and DL. If this switch is turned off, the UL and
DL CCE ratios are not dynamically adjusted.
Unit: None
CellPdcchAlgo UlPdcchAllocImproveSwitch MOD CELLPDCCHALGO LBFD-002003 / Physical Channel Meaning: Indicates whether to enable the
LST CELLPDCCHALGO TDLBFD-002003 Management mechanism of increasing the control channel
element (CCE) resource allocation success
rate in the uplink.
ReserveCommonCCESwitch: Indicates
whether to reserve CCE resources in the
common search space for the uplink. CCE
resources in the common search space are
reserved for the uplink only when this switch
is on.
GUI Value Range:
ReserveCommonCCESwitch
(ReserveCommonCCESwitch)
Unit: None
Actual Value Range:
ReserveCommonCCESwitch
Default Value:
ReserveCommonCCESwitch:Off
PUCCHCfg DeltaShift MOD PUCCHCFG LBFD-002003 / Physical Channel Meaning: Indicates the interval between
LST PUCCHCFG TDLBFD-002003 Management cyclic shifts used for the PUCCH. The
interval between cyclic shifts used for the


PUCCH can be acquired based on the
average delay spread in the cell, where the
average delay spread is acquired based on
the networking environment. The parameter
value DS1_DELTA_SHIFT is not supported
by the LBBPc. If a cell is established on an
LBBPc but this parameter is set to
DS1_DELTA_SHIFT, the value of this
parameter is automatically changed to
DS2_DELTA_SHIFT when this parameter
takes effect. For details, see 3GPP TS
36.211.
GUI Value Range: DS1_DELTA_SHIFT(ds1),
DS2_DELTA_SHIFT(ds2),
DS3_DELTA_SHIFT(ds3)
Unit: None
Actual Value Range: DS1_DELTA_SHIFT,
DS2_DELTA_SHIFT, DS3_DELTA_SHIFT
Default Value: DS1_DELTA_SHIFT(ds1)
PUCCHCfg SriPeriodAdaptive MOD PUCCHCFG LBFD-002003 / Physical Channel Meaning: Indicates whether to enable
LST PUCCHCFG TDLBFD-002003 Management scheduling request indicator (SRI) period
adaptation. If this parameter is set to
QCIADAPTIVE(QCIADAPTIVE), the SRI
period adaptively changes based on the cell
load and bearers with different QCIs. If this
parameter is set to NOQCIADAPTIVE
(NOQCIADAPTIVE), the SRI period
adaptively changes based on only the cell
load. If the parameter is set to OFF(OFF), the
SRI period is set to the value of the SriPeriod
parameter in the CellStandardQci MO.
GUI Value Range: OFF(OFF),
QCIADAPTIVE(QCIADAPTIVE),
NOQCIADAPTIVE(NOQCIADAPTIVE)
Unit: None
Actual Value Range: OFF, QCIADAPTIVE,
NOQCIADAPTIVE
Default Value: QCIADAPTIVE
(QCIADAPTIVE)
CellQciPara SriPeriod ADD CELLQCIPARA LBFD-002003 / Physical Channel Meaning: Indicates the interval at which
MOD CELLQCIPARA TDLBFD-002003 Management scheduling request indicators are sent.
LST CELLQCIPARA GUI Value Range: ms5(SRI 5ms), ms10(SRI
10ms), ms20(SRI 20ms), ms40(SRI 40ms),
ms80(SRI 80ms)
Unit: None
ms40, ms80
Default Value: ms10(SRI 10ms)
GlobalProcSwitch QciParaEffectFlag MOD None None Meaning: Indicates whether parameters in

GLOBALPROCSWITCH QciPara, CellQciPara, and
LST CnOperatorQciPara MOs take effect. The
GLOBALPROCSWITCH
parameters do not take effect by default. If
this parameter is set to OFF, parameters in
StandardQci, ExtendedQci, CellStandardQci,
CellExtendedQci, CnOperatorStandardQci,
and CnOperatorExtendedQci MOs take effect
and parameters in QciPara, CellQciPara, and
CnOperatorQciPara MOs do not take effect.
If this parameter is set to ON, parameters in
QciPara, CellQciPara, and
CnOperatorQciPara MOs take effect and
parameters in StandardQci, ExtendedQci,
CellStandardQci, CellExtendedQci,
CnOperatorStandardQci, and
CnOperatorExtendedQci MOs do not take
effect.
Unit: None
CellStandardQci SriPeriod MOD LBFD-002003 / Physical Channel Meaning: Indicates the interval at which
CELLSTANDARDQCI TDLBFD-002003 Management scheduling request indicators are sent.
LST
CELLSTANDARDQCI GUI Value Range: ms5(SRI 5ms), ms10(SRI
10ms), ms20(SRI 20ms), ms40(SRI 40ms),
ms80(SRI 80ms)
Unit: None
ms40, ms80
Default Value: ms10(SRI 10ms)
CellPucchAlgo SriLowLoadThd MOD CELLPUCCHALGO LBFD-002003 / Physical Channel Meaning: Indicates the threshold for the low
LST CELLPUCCHALGO TDLBFD-002003 Management load state of the SRI resources. The SRI
resources enter the low load state if the
PUCCH resource allocation algorithm detects
that the number of admitted UEs is smaller
than the value of this parameter.


Unit: None
Default Value: 10
CellPucchAlgo SriAlgoSwitch MOD CELLPUCCHALGO LBFD-002003 / Physical Channel Meaning:

LST CELLPUCCHALGO TDLBFD-002003 Management Indicates the working modes for SRI
reporting period configuration.
SriAdaptiveHoldForVoIPSW: Indicates
whether to enable SRI reporting period
adaptation for VoLTE UEs during resource
adjustment for SRI reporting. If this option is
selected, SRI reporting periods are
configured based on the cell load. If the
number of UEs is small, adaptively
configured SRI reporting periods are shorter
than the fixed long SRI reporting period,
improving the MOS of VoLTE users. If this
option is deselected, the fixed long SRI
reporting period is retained.
SriAdaptiveHoldForVoIPSW takes effect only
when both PUCCH resource adjustment and
SRI reporting period adaptation are enabled.
SriPeriodCfgOptSW: Indicates whether to
optimize SRI reporting period configuration. If
this option is selected, SRI reporting periods
are configured based only on the SRI
reporting resource usage in the cell. When
CA and VoLTE are enabled, many UEs can
be assigned short SRI reporting periods, the
amount of PUCCH resource increases, but
the amount of available PUSCH resource
decreases. If this option is deselected, SRI
reporting periods are configured based on
the resource usage for all of SRI reporting,
semi-persistent ACK reporting, and dynamic
ACK reporting. When CA and VoLTE are
enabled, a few UEs can be assigned short
SRI reporting periods, the amount of PUCCH
resource decreases, but the amount of
available PUSCH resource increases.
SriOffsetReConfigForDrxSW: indicates
whether to reconfigure the SRI subframe
offset for DRX. This option takes effect only
when DRX is enabled. This option applies
only to LTE FDD. If this option is selected,
the eNodeB adjusts SRI and DRX subframe
offsets for power saving. If this option is
deselected, the eNodeB does not perform the
adjustment.
GUI Value Range:
SriAdaptiveHoldForVoIPSW
(SriAdaptiveHoldForVoIPSW),
SriPeriodCfgOptSW(SriPeriodCfgOptSW),
SriOffsetReConfigForDrxSW
(SriOffsetReConfigForDrxSW)
Unit: None
Actual Value Range:
SriAdaptiveHoldForVoIPSW,
SriPeriodCfgOptSW,
SriOffsetReConfigForDrxSW
Default Value:
SriAdaptiveHoldForVoIPSW:Off,
SriPeriodCfgOptSW:Off,
SriOffsetReConfigForDrxSW:Off
CqiAdaptiveCfg PucchPeriodicCqiOptSwitch MOD CQIADAPTIVECFG LBFD-002003 Physical Channel Meaning: Indicates whether to enable the
LST CQIADAPTIVECFG Management 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.
Unit: None
PUCCHCfg CqiRbNum MOD PUCCHCFG LBFD-002003 / Physical Channel Meaning: Indicates the number of RBs
LST PUCCHCFG TDLBFD-002003 Management allocated to the CQI at the RRC layer of cell.
Unit: None
Default Value: 1
PUCCHCfg NaSriChNum MOD PUCCHCFG LBFD-002003 / Physical Channel Meaning: Indicates the number of resource
LST PUCCHCFG TDLBFD-002003 Management indexes allocated to SRI and semi-persistent


ACK at the RRC layer for the cell. If this
parameter is set to 0, UEs may fail to access
the cell.
Unit: None
Default Value: 6
RACHCfg PrachFreqOffset MOD RACHCFG LBFD-002009 / Broadcast of system Meaning: Indicates the offset of the starting
LST RACHCFG TDLBFD-002009 information frequency-domain position of the PRACH
LBFD-002010 / Random Access RBs.
TDLBFD-002010 Procedure GUI Value Range: 0~94
Unit: None
Default Value: 6
PUSCHCfg HoppingOffset MOD PUSCHCFG LBFD-002009 / Broadcast of system Meaning:

LST PUSCHCFG TDLBFD-002009 information Indicates the hopping offset of the PUSCH.
Unit: RB
Default Value: 0
PUCCHCfg PucchExtendedRBNum MOD PUCCHCFG LBFD-002003 / Physical Channel Meaning: Indicates the total number of RBs
LST PUCCHCFG TDLBFD-002003 Management at the two ends of the system band that are
LOFD-001093 PUCCH Flexible reserved for the PUSCH. This parameter is
Configuration valid only when the PUCCH flexible
configuration switch (PucchFlexCfgSwitch) is
turned on. The parameter setting must
consider the number of RBs used by the
PRACH, SRS, and PUCCH as well as the
number of RBs compressed. If the parameter
setting exceeds the system bandwidth
capability and accordingly affects the
preceding RB resource allocation, the cell
cannot be established successfully.
Unit: 2RB
Default Value: 1
SRSCfg SrsCfgInd MOD SRSCFG LBFD-002003 / Physical Channel Meaning: Indicates whether to configure
LST SRSCFG TDLBFD-002003 Management 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.
GUI Value Range: BOOLEAN_FALSE
(False), BOOLEAN_TRUE(True)
Unit: None
BOOLEAN_TRUE
Default Value: BOOLEAN_TRUE(True)
SRSCfg FddSrsCfgMode MOD SRSCFG None None Meaning: Indicates the allocation mode of
LST SRSCFG 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.
GUI Value Range: DEFAULTMODE(Default
Mode), ADAPTIVEMODE(Adaptive Mode)
Unit: None
Actual Value Range: DEFAULTMODE,
ADAPTIVEMODE
Default Value: ADAPTIVEMODE(Adaptive
Mode)
SRSCfg SrsSubframeCfg MOD SRSCFG LBFD-002003 / Physical Channel Meaning: Indicates the index of the SRS
LST SRSCFG TDLBFD-002003 Management subframe configuration for the cell. The value
SCn, where n is variable, represents
configuration n. For example, the value SC0
indicates subframe configuration 0, and the
value SC1 indicates subframe configuration
1. If the cell operates in FDD mode, the value
SC15 is reserved. If the cell operates in TDD
mode, the values SC14 and SC15 are
reserved. The reserved values cannot be
used. For the relationship between the
subframe configuration index and the cell-
specific subframe cycle/offset, see 3GPP TS
36.211. In FDD mode, this parameter is
permanently valid. In TDD mode, this
parameter is valid only if TddSrsCfgMode is
set to EXPERIENCE_FIRST.
GUI Value Range: SC0(0), SC1(1), SC2(2),
SC3(3), SC4(4), SC5(5), SC6(6), SC7(7),
SC8(8), SC9(9), SC10(10), SC11(11), SC12
(12), SC13(13), SC14(14)
Unit: None
Actual Value Range: SC0, SC1, SC2, SC3,
SC4, SC5, SC6, SC7, SC8, SC9, SC10,
SC11, SC12, SC13, SC14
Default Value: SC3(3)
CellAlgoSwitch SrsAlgoSwitch MOD LBFD-002003 / Physical Channel Meaning:

CELLALGOSWITCH TDLBFD-002003 Management Indicates the switch used to enable or disable
LST CELLALGOSWITCH
change in the cell-specific SRS subframe
configuration (that is, the adjustment on the
setting of the SrsSubframeCfg parameter).
If the switch is on, the algorithm dynamically
adjusts the SRS subframe configuration
based on the usage of cell resources.
If the switch is off, the algorithm uses the
initial configuration and does not perform
dynamic switching.
GUI Value Range: SrsSubframeRecfSwitch
(SrsSubframeRecfSwitch)
Unit: None
Actual Value Range:
SrsSubframeRecfSwitch
Default Value: SrsSubframeRecfSwitch:On
CellSrsAdaptiveCfg SrsPeriodAdaptive MOD LBFD-002003 / Physical Channel Meaning: Indicates whether to enable SRS
CELLSRSADAPTIVECFG TDLBFD-002003 Management reporting period adaptation. If this parameter
LST is set to ON(On), the SRS reporting period
CELLSRSADAPTIVECFG
adaptively changes based on the SRS
algorithm. If this parameter is set to OFF(Off),
the SRS reporting period is specified by the
UserSrsPeriod parameter.
Unit: None
CellSrsAdaptiveCfg UserSrsPeriod MOD LBFD-002003 / Physical Channel Meaning: Indicates the fixed SRS reporting
CELLSRSADAPTIVECFG TDLBFD-002003 Management period. This parameter takes effect only
LST when the SrsPeriodAdaptive parameter is set
CELLSRSADAPTIVECFG
to OFF(Off).
GUI Value Range: ms5(5ms), ms10(10ms),
ms20(20ms), ms40(40ms), ms80(80ms),
ms160(160ms), ms320(320ms)
Unit: ms
ms40, ms80, ms160, ms320
Default Value: ms40(40ms)
TimeAlignmentTimer TimingResOptSwitch MOD TATIMER None None Meaning: Indicates whether to enable the
LST TATIMER mechanism of optimized resource scheduling
for uplink timing.If this parameter is set to
OFF, the eNodeB adopts the existing
resource scheduling policy for uplink timing,
which consumes a large amount of resources
used for delivering Timing Advance
Commands in large traffic scenarios.If this
parameter is set to ON, the eNodeB adopts
the mechanism of optimized resource
scheduling for uplink timing, which reduces
the number of unnecessary Timing Advance


Commands to be delivered and reduces
resources allocated for uplink timing in large
traffic scenarios.This parameter applies only
to LTE FDD cells. The parameter value ON is
recommended in heavily loaded cells where
there is a large number of UEs.
Unit: None
eNBCellRsvdPara RsvdSwPara3 MOD None None Meaning:

ENBCELLRSVDPARA
Indicates the 32-bit reserved parameter 3
LST
ENBCELLRSVDPARA that is reserved for future requirements.
Note on parameter replacement: Reserved
parameters are temporarily used in patch
versions and will be replaced with new
parameters. For example, the ID of a new
parameter can signify the parameter function.
RsvdSwPara3_bit2
RsvdSwPara3_bit3
RsvdSwPara3_bit4
RsvdSwPara3_bit5
RsvdSwPara3_bit6
RsvdSwPara3_bit7
RsvdSwPara3_bit8
RsvdSwPara3_bit9
RsvdSwPara3_bit10
RsvdSwPara3_bit11
RsvdSwPara3_bit12
RsvdSwPara3_bit13
RsvdSwPara3_bit14
RsvdSwPara3_bit15
RsvdSwPara3_bit16
RsvdSwPara3_bit17
RsvdSwPara3_bit18
RsvdSwPara3_bit19
RsvdSwPara3_bit20
RsvdSwPara3_bit21
RsvdSwPara3_bit22
RsvdSwPara3_bit23
RsvdSwPara3_bit24
RsvdSwPara3_bit25
RsvdSwPara3_bit26
RsvdSwPara3_bit27
RsvdSwPara3_bit28
RsvdSwPara3_bit29
RsvdSwPara3_bit30
RsvdSwPara3_bit31
RsvdSwPara3_bit32
(ReservedSwitchParameter3_bit32)
Unit: None


RsvdSwPara3_bit32
RsvdSwPara3_bit2:Off,
SRSCfg CellSrsBandwidthCfg DSP SRSCFG None None Meaning: Indicates the cell-specific SRS
bandwidth. It corresponds to the srs-
BandwidthConfig parameter in the protocol.
GUI Value Range: BW0(BW0), BW1(BW1),
BW2(BW2), BW3(BW3), BW4(BW4), BW5
(BW5), BW6(BW6), BW7(BW7),
INVALID_BANDWIDTH(Invalid bandwidth)
Unit: None
Actual Value Range: BW0, BW1, BW2, BW3,
BW4, BW5, BW6, BW7,
INVALID_BANDWIDTH
Default Value: None
SRSCfg AnSrsSimuTrans MOD SRSCFG LBFD-002003 / Physical Channel Meaning:

LST SRSCFG TDLBFD-002003 Management Indicates whether the sounding reference
signal (SRS) of a UE and the ACK/NACK or
scheduling request (SR) on the PUCCH are
allowed to use the same time resources for
simultaneous transmission.
If this parameter is set to BOOLEAN_FALSE,
simultaneous transmission is not allowed. In
this situation, the UE discards the SRS and
only transmits the ACK/NACK or SR on the
PUCCH.
If this parameter is set to BOOLEAN_TRUE,
simultaneous transmission is allowed. In this
situation, the UE transmits truncated
ACK/NACK or SR. For details, see 3GPP TS
36.211.
GUI Value Range: BOOLEAN_FALSE
(False), BOOLEAN_TRUE(True)
Unit: None
BOOLEAN_TRUE
CellAlgoSwitch DlPcAlgoSwitch MOD LBFD-002003 / Physical Channel Meaning: Indicates whether to enable power
CELLALGOSWITCH TDLBFD-002003 Management control for the PDSCH, PDCCH, and PHICH.
LST CELLALGOSWITCH PdschSpsPcSwitch: If this option is
LBFD-002009 / Broadcast of system
TDLBFD-002009 information deselected, power is allocated evenly during
LBFD-002016 / Dynamic Downlink semi-persistent scheduling on the PDSCH. If
TDLBFD-002016 Power Allocation this option is selected, power control is
applied during semi-persistent scheduling on
TDLOFD-001049 Single Streaming
the PDSCH, ensuring quality (indicated by
TDLOFD-001061 Beamforming
IBLER) of VoIP services in the QPSK
Dual Streaming modulation scheme.
Beamforming PhichInnerLoopPcSwitch: Indicates whether
to enable PHICH inner-loop power control. If
this option is deselected, only the initial
transmit power for the PHICH is set. If this


option is selected, the eNodeB controls the
physical channel transmit power to enable
the receive SINR to converge to the target
SINR. PdcchPcSwitch: Indicates whether to
enable PDCCH power control. If this option is
deselected, power is allocated evenly on the
PDCCH. If this option is selected, power
allocated to PDCCH is adjusted dynamically.
EDlMaxTXPwrSwitch: If this option is
deselected, the maximum TX power of the
cell is determined by the RS power and the
scaling factor indexes Pa and Pb. If this
option is selected, the maximum TX power of
the cell can be increased to improve the RB
usage in the cell. This option has no impact
on 10 MHz, 15 MHz and 20 MHz LTE TDD
cells. BFModeUserPwrSwitch: Indicates
whether to enable power optimization for
beamforming UEs. If this option is
deselected, the original power allocation
scheme is adopted for beamforming UEs. If
this option is selected, the eNodeB uses the
configured power headroom to increases the
power for beamforming UEs. This option
applies only to LTE TDD networks.
SigPowerIncreaseSwitch: Indicates whether
to enable signaling power improvement. If
this option is selected, the PDSCH transmit
power increases when scheduling is
performed for downlink retransmission of
signaling during network entry. This option
applies only to LTE TDD cells.
BFModeUserAdptPwrSwitch: Indicates
whether to enable power adaptation for
beamforming UEs. If this option is selected,
the cell adaptively increases the power of
beamforming UEs based on the available
power of the RRU and loads at neighboring
cell edges. In this way, the average cell
throughput increases. This option applies
only to LTE TDD networks.
GUI Value Range: PdschSpsPcSwitch,
PhichInnerLoopPcSwitch, PdcchPcSwitch,
EDlMaxTXPwrSwitch,
BFModeUserPwrSwitch,
SigPowerIncreaseSwitch,
BFModeUserAdptPwrSwitch
Unit: None
Actual Value Range: PdschSpsPcSwitch,
EDlMaxTXPwrSwitch,
BFModeUserPwrSwitch,
SigPowerIncreaseSwitch,
BFModeUserAdptPwrSwitch
Default Value: PdschSpsPcSwitch:Off,
PhichInnerLoopPcSwitch:Off,
PdcchPcSwitch:On,
EDlMaxTXPwrSwitch:Off,
BFModeUserPwrSwitch:Off,
SigPowerIncreaseSwitch:Off,
BFModeUserAdptPwrSwitch:Off
GlobalProcSwitch SriAdaptiveSwitch MOD LBFD-002003 / Physical Channel Meaning: Indicates whether to enable
GLOBALPROCSWITCH TDLBFD-002003 Management scheduling request indication (SRI)
LST adaptation. If this switch is turned on, the SRI
GLOBALPROCSWITCH
period adaptively changes based on the SRI
algorithm. If this switch is turned off, the SRI
period is the value of the SriPeriod parameter
in the CellStandardQci MO.
Unit: None
14 Counters
Table 14-1 Counters
1526727378 L.Traffic.User.Avg Average number of users in Multi-mode: None RRC Connection

a cell GSM: None Management
TDLBFD-002007


1526727379 L.Traffic.User.Max Maximum number of users in Multi-mode: None RRC Connection
a cell GSM: None Management
TDLBFD-002007
1526727483 L.ChMeas.PRB.PUCCH.Avg Average number of used Multi-mode: None Basic Scheduling

PRBs over the PUCCH GSM: None Basic Scheduling
UMTS: None
LTE: LBFD-002025
TDLBFD-002025
1526728259 L.Thrp.bits.UL Total uplink traffic volume for Multi-mode: None Radio Bearer Management
PDCP PDUs in a cell GSM: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526728261 L.Thrp.bits.DL Total downlink traffic volume Multi-mode: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526728297 L.UL.Interference.Max Maximum uplink interference Multi-mode: None Physical Channel

and noise received by each GSM: None Management
PRB in a cell UMTS: None Physical Channel
TDLBFD-002003 Adaptive SFN/SDMA
LOFD-070205
1526728298 L.UL.Interference.Avg Average uplink interference Multi-mode: None Physical Channel

and noise received by each GSM: None Management
PRB in a cell UMTS: None Physical Channel
TDLBFD-002003 Adaptive SFN/SDMA
LOFD-070205
1526728299 L.ChMeas.PDCCH.SymNum.1 Number of times the PDCCH Multi-mode: None Physical Channel
occupies one symbol in a GSM: None Management
measurement period UMTS: None Physical Channel
TDLBFD-002003
occupies two symbols in a GSM: None Management
TDLBFD-002003
occupies three symbols in a GSM: None Management
TDLBFD-002003
occupies four symbols in a GSM: None Management
TDLBFD-002003
1526728303 L.ChMeas.CCE.CommUsed Number of PDCCH CCEs Multi-mode: None Physical Channel

used for common DCI GSM: None Management
UMTS: None Physical Channel
TDLBFD-002003
1526728304 L.ChMeas.CCE.ULUsed Number of PDCCH CCEs Multi-mode: None Physical Channel

used for uplink DCI in a GSM: None Management
TDLBFD-002003
1526728305 L.ChMeas.CCE.DLUsed Number of PDCCH CCEs Multi-mode: None Physical Channel

used for downlink DCI in a GSM: None Management
TDLBFD-002003
1526728435 L.UL.Interference.Min Multi-mode: None Physical Channel

GSM: None Management


Minimum uplink interference UMTS: None Physical Channel
and noise received by each LTE: LBFD-002003 Management
PRB in a cell TDLBFD-002003 Adaptive SFN/SDMA
LOFD-070205

LTE: LBFD-002007
TDLBFD-002007
1526728482 L.Traffic.User.SRS.Max Maximum number of UEs Multi-mode: None RRC Connection

LTE: LBFD-002007
TDLBFD-002007
1526728485 L.RRC.SetupFail.ResFail.SRS Number of RRC connection Multi-mode: None RRC Connection

setup failures due to SRS GSM: None Management
resource allocation failure UMTS: None RRC Connection
TDLBFD-002007
1526728486 L.RRC.SetupFail.ResFail.PUCCH Number of RRC connection Multi-mode: None RRC Connection

setup failures due to PUCCH GSM: None Management
resource allocation failure UMTS: None RRC Connection
TDLBFD-002007
1526728664 L.ChMeas.PDCCH.DL.DTXNum.AggLvl1 Number of times of DTX for Multi-mode: None Physical Channel
PDCCH resource allocation GSM: None Management
with aggregation level 1 in a UMTS: None Physical Channel
cell Management
LTE: LBFD-002003
TDLBFD-002003
cell Management
LTE: LBFD-002003
TDLBFD-002003
cell Management
LTE: LBFD-002003
TDLBFD-002003
cell Management
LTE: LBFD-002003
TDLBFD-002003
1526728668 L.ChMeas.PDCCH.AggLvl1Num Number of times of PDCCH Multi-mode: None Physical Channel

resource allocations with GSM: None Management
aggregation level 1 UMTS: None Physical Channel
TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003
1526728765 L.ChMeas.CCE.Avail Number of available PDCCH Multi-mode: None Physical Channel

CCEs GSM: None Management
TDLBFD-002003
1526729292 L.ChMeas.CCE.DLUsed.DRB Number of PDCCH CCEs Multi-mode: None Physical Channel

used for initial transmitted GSM: None Management
downlink data in a cell UMTS: None Dynamic Downlink Power
Allocation


LTE: LBFD-002003 Dynamic Downlink Power
LBFD-002016 Allocation
TDLBFD-002016
1526729293 L.ChMeas.CCE.DLUsed.SRB Number of PDCCH CCEs Multi-mode: None Physical Channel

downlink signaling in a cell UMTS: None Dynamic Downlink Power
LTE: LBFD-002003 Allocation
LBFD-002016 Dynamic Downlink Power
Allocation
TDLBFD-002016
1526729294 L.ChMeas.CCE.DLUsed.MCE Number of PDCCH CCEs Multi-mode: None Physical Channel

downlink MCEs in a cell UMTS: None Dynamic Downlink Power
Allocation
TDLBFD-002016
1526729295 L.ChMeas.CCE.ULUsed.Equivalent Number of PDCCH CCEs Multi-mode: None Physical Channel

with the CCE power GSM: None Management
equivalent to the reference UMTS: None Dynamic Downlink Power
power used for uplink DCI Allocation
LTE: LBFD-002003
Allocation
TDLBFD-002016
1526729296 L.ChMeas.CCE.DLUsed.Equivalent Number of PDCCH CCEs Multi-mode: None Physical Channel

power used for downlink DCI Allocation
LTE: LBFD-002003
Allocation
TDLBFD-002016
1526730620 L.UL.Interference.Avg.PRB0 Average interference and Multi-mode: None Physical Channel

noise received by PRB 0 in a GSM: None Management
cell UMTS: None Physical Channel
TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003


TDLBFD-002003

noise received by PRB 10 in GSM: None Management
a cell UMTS: None Physical Channel
TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

a cell


TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003



TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003
1526730672 L.UL.Interference.Avg.PRB52 Multi-mode: None


Average interference and GSM: None Physical Channel
noise received by PRB 52 in UMTS: None Management
a cell LTE: LBFD-002003 Physical Channel

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

Management


LTE: LBFD-002003
TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003


TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

a cell


TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003
1526730720 L.UL.Interference.Max.PRB0 Maximum interference and Multi-mode: None Physical Channel

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003



TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003
1526730744 L.UL.Interference.Max.PRB24 Multi-mode: None


Maximum interference and GSM: None Physical Channel

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

Management


LTE: LBFD-002003
TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003


TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

a cell


TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003



TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003
1526730816 L.UL.Interference.Max.PRB96 Multi-mode: None


Maximum interference and GSM: None Physical Channel

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003
1526730844 L.ChMeas.CCE.UL.AllocFail Number of uplink CCE Multi-mode: None Physical Channel

allocation failures in a cell GSM: None Management
UMTS: None
LTE: LBFD-002003
1526730845 L.ChMeas.CCE.DL.AllocFail Number of downlink CCE Multi-mode: None Physical Channel

allocation failures in a cell GSM: None Management
UMTS: None
LTE: LBFD-002003
1526732045 L.UL.RSSI.PUCCH.Index0 Number of times the eNodeB Multi-mode: None Physical Channel
detects a PRB-level average GSM: None Management
RSSI ranging within index 0 UMTS: None Physical Channel
on the PUCCH Management
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003


LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
1526732067 L.UL.RSSI.PUSCH.Index0 Number of times the eNodeB Multi-mode: None Physical Channel
on the PUSCH Management
LTE: LBFD-002003
TDLBFD-002003


on the PUSCH LTE: LBFD-002003 Management
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003


TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
1526734045 L.UL.Interference.PUSCH.Index0 Number of times the eNodeB Multi-mode: None Physical Channel
detects a PRB-level IN GSM: None Management
ranging within index 0 on the UMTS: None Physical Channel
PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
1526734053 L.UL.Interference.PUSCH.Index8 Multi-mode: None


Number of times the eNodeB GSM: None Physical Channel
detects a PRB-level IN UMTS: None Management
ranging within index 8 on the LTE: LBFD-002003 Physical Channel
PUSCH Management
TDLBFD-002003
PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
ranging within index 10 on UMTS: None Physical Channel
the PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
1526734061 L.UL.Interference.PUCCH.Index0 Number of times the eNodeB Multi-mode: None Control Channel IRC
detects a PRB-level IN GSM: None Physical Channel
ranging within index 0 on the UMTS: None Management
PUCCH Physical Channel
LTE: LOFD-001094
LBFD-002003 Management
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
PUCCH
LTE: LOFD-001094


LBFD-002003 Physical Channel
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
ranging within index 10 on UMTS: None Management
the PUCCH Physical Channel
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
1526734077 L.UL.Interference.PRACH.Index0 Number of times the eNodeB Multi-mode: None Control Channel IRC
PRACH Physical Channel
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094


TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
the PRACH Physical Channel
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003


LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
1526734093 L.UL.RSRP.PUSCH.Index0 Number of times the eNodeB Multi-mode: None Physical Channel
detects a UE-level RSRP GSM: None Management
PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003


LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
LTE: LBFD-002003
TDLBFD-002003
1526734117 L.UL.RSRP.PUCCH.Index0 Number of times the eNodeB Multi-mode: None Control Channel IRC
detects a UE-level RSRP GSM: None Physical Channel
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003


LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
detects a UE-level RSRP


ranging within index 14 on GSM: None Physical Channel
the PUCCH UMTS: None Management
LTE: LOFD-001094 Physical Channel
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
LTE: LOFD-001094
TDLBFD-002003
1526736735 L.ChMeas.CCE.ULUsed.VoIP Number of PDCCH CCEs Multi-mode: None Physical Channel

used for uplink VoIP services GSM: None Management
TDLBFD-002003 Dynamic Downlink Power
Allocation
LBFD-002016
Dynamic Downlink Power
TDLBFD-002016
Allocation
1526736736 L.ChMeas.CCE.DLUsed.VoIP Number of PDCCH CCEs Multi-mode: None Physical Channel

used for downlink VoIP GSM: None Management
services UMTS: None Physical Channel
Allocation
LBFD-002016
TDLBFD-002016
Allocation


1526737656 L.CellSectorEQUIP.UL.RSSI.Avg.Ant0 Average RSSI of antenna 0 Multi-mode: None Physical Channel
in a set of cell sector GSM: None Management
equipment UMTS: None Physical Channel
TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003
1526737664 L.CellSectorEQUIP.UL.RSSI.Max.Ant0 Maximum RSSI of antenna 0 Multi-mode: None Physical Channel

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

equipment


TDLBFD-002003

TDLBFD-002003
1526737672 L.CellSectorEQUIP.UL.RSSI.Min.Ant0 Minimum RSSI of antenna 0 Multi-mode: None Physical Channel

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003

TDLBFD-002003
1526739747 L.ChMeas.PDCCH.UL.AggLvl1Num Number of times an eNodeB Multi-mode: None Physical Channel

allocates the PDCCHs with GSM: None Management
aggregation level 1 for uplink UMTS: None Physical Channel
scheduling Management
LTE: LBFD-002003
TDLBFD-002003

LTE: LBFD-002003
TDLBFD-002003

LTE: LBFD-002003
TDLBFD-002003

LTE: LBFD-002003
TDLBFD-002003
1526739817 L.ChMeas.Dl.ePDCCH.AggLvl1Num Number of times downlink Multi-mode: None ePDCCH[Trial]

ePDCCH resource GSM: None ePDCCH (Trial)
allocations with aggregation UMTS: None
level 1
LTE: LAOFD-110203


TDLAOFD-111401

level 2
LTE: LAOFD-110203
TDLAOFD-111401

level 4
LTE: LAOFD-110203
TDLAOFD-111401

level 8
LTE: LAOFD-110203
TDLAOFD-111401

level 16
LTE: LAOFD-110203
TDLAOFD-111401

level 32
LTE: LAOFD-110203
TDLAOFD-111401
1526739823 L.ChMeas.Ul.ePDCCH.AggLvl1Num Number of times uplink Multi-mode: None ePDCCH[Trial]

level 1
LTE: LAOFD-110203
TDLAOFD-111401

level 2
LTE: LAOFD-110203
TDLAOFD-111401

level 4
LTE: LAOFD-110203
TDLAOFD-111401

level 8
LTE: LAOFD-110203
TDLAOFD-111401

level 16
LTE: LAOFD-110203
TDLAOFD-111401

level 32
LTE: LAOFD-110203
TDLAOFD-111401
1526739829 L.ChMeas.ePDCCH.DL.DTXNum.AggLvl1 Number of times DTX is Multi-mode: None ePDCCH[Trial]

detected for downlink GSM: None ePDCCH (Trial)
ePDCCH resource UMTS: None
allocations with aggregation
LTE: LAOFD-110203
level 1 in a cell
TDLAOFD-111401

LTE: LAOFD-110203
level 2 in a cell
TDLAOFD-111401

LTE: LAOFD-110203
level 4 in a cell
TDLAOFD-111401
1526740432 L.ChMeas.ePDCCH.DL.DTXNum.AggLvl8 Multi-mode: None ePDCCH[Trial]


Number of times DTX is GSM: None ePDCCH (Trial)
detected for downlink UMTS: None
ePDCCH resource LTE: LAOFD-110203
TDLAOFD-111401
level 8 in a cell

LTE: LAOFD-110203
level 16 in a cell
TDLAOFD-111401

LTE: LAOFD-110203
level 32 in a cell
TDLAOFD-111401
1526740435 L.ChMeas.eCCE.DLUsed.DRB Number of ePDCCH eCCEs Multi-mode: None ePDCCH[Trial]

used by initially transmitted GSM: None ePDCCH (Trial)
downlink data UMTS: None
LTE: LAOFD-110203
TDLAOFD-111401
1526740436 L.ChMeas.eCCE.DLUsed.MCE Number of ePDCCH eCCEs Multi-mode: None ePDCCH[Trial]

downlink MCEs UMTS: None
LTE: LAOFD-110203
TDLAOFD-111401
1526740437 L.ChMeas.eCCE.DLUsed.SRB Number of ePDCCH eCCEs Multi-mode: None ePDCCH[Trial]

downlink signaling messages UMTS: None
LTE: LAOFD-110203
TDLAOFD-111401
15 Glossary
1. 3GPP TS 36.211, "Physical Channels and Modulation"

2. 3GPP TS 36.213, "Physical layer procedures"
3. Power Control Feature Parameter Description
5. Connection Management Feature Parameter Description
7. MIMO Feature Parameter Description

eRAN
Power Control Feature Parameter Description
Issue 05
Date 2017-01-15

Notice

6 Contents
1.1 Scope
1.3 Change History
2 Overview
2.1 Introduction
2.2 Benefits
2.3 Downlink Power Allocation
2.4 Uplink Power Control
3 Downlink Power Allocation

3.1 Overview
3.2 CRS
3.3 Synchronization Signals
3.4 PBCH
3.5 PCFICH
3.6 RAR Messages
3.7 PHICH
3.8 PDCCH Carrying Common Control Information
3.9 PDCCH Carrying Dedicated Control Information
3.10 PDSCH Carrying Common Information
3.11 PDSCH Carrying UE-Specific Information
3.11.1 Power Calculation
3.11.2 Power Control Policy
3.12 PMCH
3.13 Unbalanced Transmit Power Configurations Between Channels
4 Uplink Power Control

4.1 Overview
4.2 PRACH
4.2.2 Power Ramping
4.3 PUSCH


4.3.2 Initial Power Setting by the eNodeB
4.3.3 Power Adjustment by the eNodeB
4.3.4 Msg3 Power Control During Random Access
4.4 PUCCH
4.4.4 Optimized PUCCH Power Control at DTXs
4.5 SRS
4.5.2 Power Setting by the eNodeB
5 Related Features
5.1 LBFD-002016 Dynamic Downlink Power Allocation
5.2 LBFD-002026 Uplink Power Control
5.3 LBFD-070105 IoT-based PUSCH Power Control
5.4 LBFD-081101 PUCCH Outer Loop Power Control
6 Network Impact
6.1 LBFD-002016 Dynamic Downlink Power Allocation
6.2 LBFD-002026 Uplink Power Control
6.3 LBFD-070105 IoT-based PUSCH Power Control
6.4 LBFD-081101 PUCCH Outer Loop Power Control
7.1 When to Use
7.1.1 Downlink Power Control
7.1.2 Uplink Power Control
7.1.3 IoT-based PUSCH Power Control
7.1.4 PUCCH Outer-Loop Power Control
7.3 Planning
7.4 Deployment of Downlink Power Control
7.4.1 Requirements
7.4.2 Precautions
7.4.5 Deactivation
7.5 Deployment of Uplink Power Control
7.5.1 Requirements
7.5.4 Deactivation
7.8 Possible Issues
8 Parameters
9 Counters
10 Glossary
Scope
This document describes power control, including its technical principles, related features, network impact, and engineering guidelines.
This document covers the following features:
• LBFD-002016 Dynamic Downlink Power Allocation

• LBFD-002026 Uplink Power Control

• LBFD-070105 IoT-based PUSCH Power Control

• LBFD-081101 PUCCH Outer Loop Power Control
eNodeB Type Model
Micro BTS3202E
BTS3203E
Intended Audience

Change History
• Feature change
AN11.1 05 (2017-01-15)
Feature None None N/A

change
Editorial Revised Feature Support by Macro, Micro, and LampSite None N/A
change eNodeBs in 1.4 Differences Between eNodeB Types because
BTS3911E and BTS3912E do not support LBFD-
081101 PUCCH Outer Loop Power Control.
AN11.1 04 (2016-08-01)
Feature Added the function of BTS3911E supporting LBFD- None N/A

change 081101 PUCCH Outer Loop Power Control. For details,
see Feature Support by Macro, Micro, and LampSite eNodeBs in
1.4 Differences Between eNodeB Types.
Editorial Revised descriptions in this document. None N/A

change
AN11.1 03 (2016-06-30)
Feature None None N/A

change
Editorial Revised the following sections: N/A N/A

change
• 3.13 Unbalanced Transmit Power Configurations
Between Channels
• Prerequisite Features in 5.1 LBFD-002016 Dynamic
Downlink Power Allocation
• Unbalanced Transmit Power Configurations Between
Channels in 7.1.1 Downlink Power Control
AN11.1 02 (2016-04-20)
Feature Added the function of unbalanced transmit power Added the following parameters: Macro and micro eNodeBs
change configurations between channels. For details, see the • PDSCHCfg.TxPowerOffsetAnt0
following sections:
• PDSCHCfg.TxPowerOffsetAnt1
• 3.13 Unbalanced Transmit Power Configurations • PDSCHCfg.TxPowerOffsetAnt2
Between Channels
• 5.1 LBFD-002016 Dynamic Downlink Power Allocation
• 6.1 LBFD-002016 Dynamic Downlink Power Allocation
• 7.1 When to Use
• 7.4 Deployment of Downlink Power Control
• 7.6 Performance Monitoring


Editorial None None N/A
change
AN11.1 01 (2016-03-07)
AN11.1 Draft A (2015-12-30)
Feature Added the function of initial fast PUCCH power control. Added the PucchInitialPcSwitch Macro, micro, and LampSite eNodeBs
change For details, see the following sections: (PucchInitialPcSwitch) option to the
• Initial Fast PUCCH Power Control CellAlgoSwitch.UlPcAlgoSwitch parameter.
• 7.5 Deployment of Uplink Power Control
Added the function of power allocation for RAR Added the Macro, micro, and LampSite eNodeBs
messages. For details, see the following sections: CellChPwrCfg.HoRarPwrEnhancedSwitch
• 3.6 RAR Messages parameter.
• 7.1 When to Use
• 7.4 Deployment of Downlink Power Control
Modified the function of optimized PUSCH closed-loop Added the CellPcAlgo.NearPointUePuschType Macro, micro, and LampSite eNodeBs
power control for UEs near the cell center. For details, parameter.
see PUSCH Closed-loop Power Control Optimization on UEs Near
the Cell Center.
Added the function of PUSCH transmit power Added the Macro, micro, and LampSite eNodeBs
adjustment for UEs running voice services in dynamic CellPcAlgo.VoLteSinrHighThdOffset
scheduling mode. For details, see the following parameter.
sections:
• 4.3.3 Power Adjustment by the eNodeB
• 6.2 LBFD-002026 Uplink Power Control
• PUSCH Transmit Power Adjustment for UEs Running
Voice Services with Dynamic Scheduling Applied
• 7.5.2 Data Preparation and Feature Activation
Removed dynamic PDSCH power control from LBFD- None Macro, micro, and LampSite eNodeBs
002016 Dynamic Downlink Power Allocation and
deleted the related descriptions.
Editorial Revised the description in the following sections: Added the CellUlPcComm.DeltaMsg2 N/A
change • 4.3.1 Power Calculation parameter.
• 4.4.1 Power Calculation
Revised the description of CME-based feature None N/A

configuration in engineering guidelines.
Feature ID Feature Name Supported by Macro Supported by Micro eNodeBs Supported by LampSite
eNodeBs eNodeBs
LBFD-002016 Dynamic Downlink Power Allocation Yes Yes Yes
LBFD-002026 Uplink Power Control Yes Yes Yes
LBFD-070105 IoT-based PUSCH Power Control Yes Yes Yes
LBFD-081101 PUCCH Outer Loop Power Control Yes No Yes
Function Difference
Inter-cell interference Unlike macro and LampSite eNodeBs, micro eNodeBs do not support ICIC and have a different power control policy for the
coordination (ICIC) PDSCH. For details, see 3.11.2 Power Control Policy and 5.1 LBFD-002016 Dynamic Downlink Power Allocation.
Transmit power restriction on On a network with both macro and micro eNodeBs deployed, the maximum transmit power of UEs in micro cells is restricted.
UEs in micro cells For details, see 4.3.3 Power Adjustment by the eNodeB.
Cell bandwidth restriction Micro cells do not support the bandwidths of 1.4 MHz and 3 MHz, and therefore power control for channels does not apply to
micro cells with those bandwidths.
Reference signal (RS) power In scenarios where a repeater amplifies the output power of a small-power remote radio unit (RRU), the AntRsPwrSwitch
delivered in SIB2 (AntRsPwrSwitch) option can be used to control the RS power delivered in system information block type 2 (SIB2).
RS power adjustment In macro eNodeBs, RS power can be set for different sets of sector equipment. In LampSite eNodeBs, RS power can be set
for different sets of sector equipment and different sector equipment groups. For details, see 3.2 CRS.
Unbalanced transmit power LampSite eNodeBs do not support unbalanced transmit power configurations between channels.
configurations between
channels

2 Overview
Introduction
Power control regulates the transmit power of eNodeBs and UEs to compensate for path loss and shadow fading, counteract interference between intra-frequency E-UTRAN
cells, and help meet coverage and capacity requirements.
Power control in the E-UTRAN is classified by signal direction into downlink power allocation and uplink power control.
Benefits
In the E-UTRAN, power control is performed on eNodeBs and UEs and offers the following benefits:
• Ensuring quality of services

Power control adjusts transmit power to the minimum level that maintains the quality of services in terms of the block error rate (BLER).
• Reducing interference
Power control reduces interference to neighboring cells.
• Lowering power consumption
Uplink power control lowers the power consumption of UEs.
• Expanding coverage and capacity
◾ Downlink power control allocates different power levels to UEs at different locations in a cell to meet coverage requirements and expand cell coverage
areas. In addition, downlink power control allocates the minimum downlink transmit power that meets the requirement for the signal to interference plus
noise ratio (SINR). In this way, network capacity increases.
◾ Uplink power control uses a technique known as fractional power compensation (FPC) to lower the interference to neighboring cells, increasing network
capacity.
Downlink Power Allocation

LBFD-002016 Dynamic Downlink Power Allocation is a basic feature. Downlink power allocation applies to the following physical signals, traffic channels, control channels, and
messages:
• Cell-specific reference signal (CRS)

• Synchronization signal
• Physical broadcast channel (PBCH)
• Physical control format indicator channel (PCFICH)
• Random Access Response (RAR) messages
• Physical HARQ indicator channel (PHICH)
• Physical downlink control channel (PDCCH)
• Physical downlink shared channel (PDSCH)
• Physical multicast channel (PMCH)
Uplink Power Control

LBFD-002026 Uplink Power Control is also a basic feature. Uplink power control applies to the following physical signals, traffic channels, and control channels:
• Physical random access channel (PRACH)

• Physical uplink shared channel (PUSCH)
• Physical uplink control channel (PUCCH)
• Sounding reference signal (SRS)
3 Downlink Power Allocation
Overview
This chapter describes the basic feature LBFD-002016 Dynamic Downlink Power Allocation. Downlink power allocation uses either of the following techniques:
• Fixed power allocation

Operators set fixed power values based on channel quality to meet the requirements for the downlink cell coverage.
eNodeBs allocate fixed power to the following signals and channels:
◾ CRS
◾ Synchronization signal
◾ PBCH
◾ PCFICH
◾ PDCCH that carries common control information
◾ PDSCH that carries common information
◾ PMCH
• Dynamic power control

Dynamic power control lowers interference, expands cell capacity, and increases coverage while meeting users' quality of service (QoS) requirements.
This type of power control applies to the following signals and channels:
◾ RAR messages
◾ PHICH
◾ PDCCH carrying dedicated control information
◾ PDSCH carrying UE-specific information
CRS
An eNodeB transmits CRSs in all downlink subframes. The CRSs serve as a basis for downlink channel estimation and are used for data demodulation.
The CRS power is indicated by the energy per resource element (EPRE) and is specified by the PDSCHCfg.ReferenceSignalPwr parameter.

The PDSCHCfg.ReferenceSignalPwr parameter specifies the RS power transmitted by a remote radio unit (RRU). Generally, the PDSCHCfg.ReferenceSignalPwr parameter
value is delivered in SIB2. However, when a repeater amplifies the transmit power of a small-power RRU, the path loss calculated based on the PDSCHCfg.ReferenceSignalPwr
parameter value in SIB2 is incorrect. To prevent this, the RS power delivered in SIB2 is now controlled by the CellAlgoSwitch.RepeaterSwitch parameter.
• If the AntRsPwrSwitch(AntRsPwrSwitch) option of the parameter is deselected, the PDSCHCfg.ReferenceSignalPwr parameter value is delivered in SIB2.
• If the AntRsPwrSwitch(AntRsPwrSwitch) option of the parameter is selected, the RS power at the antenna is calculated based on the
CellChPwrCfg.AntOutputPwr and PDSCHCfg.ReferenceSignalPwr parameters. The calculation process is as follows:
1. The CellChPwrCfg.AntOutputPwr parameter is set to specify the transmit power for the entire channel bandwidth at the antenna port.
2. The maximum transmit power of the RRU for the cell is calculated based on the CRS power, PA, and PB and is recorded as RruOutputPwr in the unit of
dBm. The gain of the transmit power at the antenna port relative to the transmit power of the RRU is calculated using the following formula: Δ (dB) =
10log10 (CellChPwrCfg.AntOutputPwr parameter value x 1000) – RruOutputPwr. The CellChPwrCfg.AntOutputPwr parameter value is expressed in the
unit of W and therefore is converted into a value in the unit of mW in the formula.
3. The RS power at the antenna is calculated using the following formula: AntReferenceSignalPwr (dBm) = PDSCHCfg.ReferenceSignalPwr parameter
value + Δ. Then, the calculated value is delivered in SIB2.
ulti-RRU Cells
In a multi-RRU cell whose Cell.MultiRruCellFlag is set to BOOLEAN_TRUE(True) and Cell.MultiRruCellMode is set to SFN(SFN), CELL_COMBINATION(Cell Combination), or
MPRU_AGGREGATION(MPRU_AGGREGATION), the RS power of each RRU that serves the cell is specified by the eUCellSectorEqm.ReferenceSignalPwr parameter.
PRU Aggregation Cells
In a multi-RRU cell whose Cell.MultiRruCellMode is set to MPRU_AGGREGATION(MPRU_AGGREGATION), the RS power of each sector equipment group is also user-
configurable. In summary, the RS power of each MPRU for LampSite eNodeBs can now be determined by the following parameters:
• PDSCHCfg.ReferenceSignalPwr (indicating the CRS power of each antenna)

• EuSectorEqmGroup.ReferenceSignalPwr (indicating the RS power of a sector equipment group for the cell)
• eUCellSectorEqm.ReferenceSignalPwr (indicating the RS power of a set of sector equipment for the cell)
The three parameters take effect in descending order of priority:
1. eUCellSectorEqm.ReferenceSignalPwr
2. EuSectorEqmGroup.ReferenceSignalPwr
3. PDSCHCfg.ReferenceSignalPwr
Synchronization Signals
Synchronization signals, used for cell search and system synchronization, can be categorized as primary synchronization signals (PSSs) and secondary synchronization signals
(SSSs). The PSS and SSS are transmitted over the primary synchronization channel (P-SCH) and secondary synchronization channel (S-SCH), respectively.
An eNodeB calculates the transmit power of the P-SCH and S-SCH using the following formula:
PowerSCH = PDSCHCfg.ReferenceSignalPwr + CellChPwrCfg.SchPwr
The CellChPwrCfg.SchPwr parameter specifies the offset of the P-SCH (or S-SCH) power relative to the CRS power.
The maximum cell transmit power is calculated based on CRS power, PA, and PB. If the power offset for synchronization signals is greater than PA, the RBs of synchronization
signal subframes cannot be fully used, which decreases system capacity.
To prevent this, the maximum cell transmit power increase function can be used. This function is controlled by the CellAlgoSwitch.DlPcAlgoSwitch parameter.
• When the EDlMaxTXPwrSwitch(EDlMaxTXPwrSwitch) option of this parameter is selected, the maximum cell transmit power increases properly so long as it is
within the power limit. The RBs of synchronization signal subframes can be fully used to increase downlink transmission rate.
• When the EDlMaxTXPwrSwitch(EDlMaxTXPwrSwitch) option is deselected, the function is disabled and the maximum cell transmit power is calculated based on
RS power, PA, and PB.
This option can be used only in an LTE-only network.
PBCH
An eNodeB transmits the PBCH in each radio frame in a cell. The PBCH carries the system information of the cell, such as the cell bandwidth, antenna configurations, and
frame numbers.
The eNodeB calculates the PBCH transmit power using the following formula:
PowerPBCH = PDSCHCfg.ReferenceSignalPwr + CellChPwrCfg.PbchPwr
The CellChPwrCfg.PbchPwr parameter specifies the offset of the PBCH transmit power relative to the CRS power.
PCFICH
The PCFICH indicates the number of orthogonal frequency division multiplexing (OFDM) symbols used for PDCCH transmission in a subframe. The PCFICH is located at the
first OFDM symbol in each subframe.
An eNodeB calculates the PCFICH transmit power using the following formula:
PowerPCFICH = PDSCHCfg.ReferenceSignalPwr + CellChPwrCfg.PcfichPwr
The CellChPwrCfg.PcfichPwr parameter specifies the offset of the PCFICH transmit power relative to the CRS power.
RAR Messages
eNodeBs send UEs the RAR messages to respond to the Random Access Request messages.
An eNodeB calculates the transmit power for the initial RAR message (referred to as initial RAR power in this document) using the following formula:
PowerRAR = PDSCHCfg.ReferenceSignalPwr + CellChPwrCfg.RaRspPwr
In this formula, the CellChPwrCfg.RaRspPwr parameter specifies the offset of the initial RAR power relative to the CRS power.
The power control policy for the RAR messages sent to UEs involved in handovers is determined by the CellChPwrCfg.HoRarPwrEnhancedSwitch parameter:
• When this parameter is set to ON(On):

◾ If the eNodeB receives a handover-specific preamble that is transmitted for the first time, the RAR power takes the CellChPwrCfg.RaRspPwr parameter
value.
◾ If the eNodeB receives a handover-specific preamble that is retransmitted for the first time, the RAR power is equal to the CellChPwrCfg.RaRspPwr
parameter value plus 3 dB.
◾ If the eNodeB receives a handover-specific preamble that is retransmitted for the nth time, where n ranges from two to the RACHCfg.PreambleTransMax
parameter value minus 1, the RAR power is equal to the CellChPwrCfg.RaRspPwr parameter value plus 6 dB.
◾ If the eNodeB receives a handover-specific preamble that is retransmitted for at least RACHCfg.PreambleTransMax times, the RAR power takes the
CellChPwrCfg.RaRspPwr parameter value.
• When this parameter is set to OFF(Off):

The RAR power takes the CellChPwrCfg.RaRspPwr parameter value.
NOTE:
If the increased RAR power would exceed the maximum transmit power of an RRU, the eNodeB does not increase the RAR power this time during RAR delivery. Instead, the
RAR power takes the CellChPwrCfg.RaRspPwr parameter value.

PHICH
The PHICH carries the acknowledgment/negative acknowledgment (ACK/NACK) to uplink hybrid automatic repeat request (HARQ) transmission.
The power control policy for the PHICH is determined by the PhichInnerLoopPcSwitch(PhichInnerLoopPcSwitch) option of the CellAlgoSwitch.DlPcAlgoSwitch parameter.
• When the PhichInnerLoopPcSwitch(PhichInnerLoopPcSwitch) option is selected, the eNodeB estimates SINRRS based on channel quality indicators (CQIs),
calculates the difference between the estimated SINRRS and SINRTarget, and periodically adjusts the PHICH power based on the difference to adapt to changes in
path loss and shadow fading. To minimize the impact of SINRTarget on cell radius, power efficiency, and cell capacity, SINRTarget permanently takes the value of 0 for
the PHICH. The adjustment works as follows:
◾ If SINRRS is less than SINRTarget, the eNodeB increases the PHICH power.
◾ If SINRRS is greater than SINRTarget, the eNodeB decreases the PHICH power.
◾ If SINRRS is equal to SINRTarget, the eNodeB retains the PHICH power.
• When the PhichInnerLoopPcSwitch(PhichInnerLoopPcSwitch) option is deselected, the fixed allocation of the PHICH power takes effect, and the offset of the
PHICH power relative to the CRS power is specified by the CellDlpcPhich.PwrOffset parameter.
The PHICH occupies so few resources that decreasing its transmit power cannot significantly reduce power consumption. In addition, the PHICH carries ACKs/NACKs to uplink
data and requires high accuracy. Decreasing the PHICH transmit power may reduce the accuracy and decrease the uplink data transmission rate. Therefore, the
PhichInnerLoopPcSwitch(PhichInnerLoopPcSwitch) option is deselected by default in commercial networks.
PDCCH Carrying Common Control Information

The PDCCH carries the following common control information:
• Control information of RACH responses

• Control information of paging messages
• Control information of system information blocks (SIBs) for the dynamic broadcast channel (D-BCH)
• Transmit power control (TPC) commands (using downlink control information [DCI] format 3)
PDCCH power control ensures the coverage performance of the common control information carried on the PDCCH. The offset of the PDCCH transmit power for the common
control information relative to the CRS power is always 0 dB.
PDCCH Carrying Dedicated Control Information

The PDCCH carries the following types of dedicated control information:
• Uplink scheduling information (using DCI format 0)

• Downlink scheduling information (using DCI format 1, 1a, 1b, 2, or 2b)
The power control policy for the PDCCH carrying dedicated control information is determined by the PdcchPcSwitch(PdcchPcSwitch) option of the
CellAlgoSwitch.DlPcAlgoSwitch parameter.
• When the PdcchPcSwitch(PdcchPcSwitch) option is selected, the eNodeB evaluates whether the PDCCH transmit power meets PDCCH reliability requirements,
based on the proportion of received discontinuous transmissions (DTXs). If the requirements are not met, the eNodeB increases the PDCCH transmit power.
• When the PdcchPcSwitch(PdcchPcSwitch) option is deselected, the fixed allocation of the PDCCH transmit power takes effect. In this case, the offset of the
PDCCH transmit power for the dedicated control information relative to the CRS power is specified by the CellDlpcPdcch.DediDciPwrOffset parameter.
0 PDSCH Carrying Common Information

PDSCH power control ensures coverage when the PDSCH carries RACH responses, paging messages, and SIBs on the D-BCH.
Parameters CellChPwrCfg.RaRspPwr, CellChPwrCfg.PchPwr, and CellChPwrCfg.DbchPwr specify the offsets of the transmit power for RACH responses, paging messages,
and SIBs relative to the CRS power, respectively.
1 PDSCH Carrying UE-Specific Information

PDSCH power control effectively increases network throughput and spectral efficiency.
NOTE:
Adaptive modulation and coding (AMC) and HARQ also increase network throughput and spectral efficiency. You can use them together with power control.

In PDSCH power control, OFDM symbols in one timeslot can be classified into type A symbols and type B symbols:
• Type A symbols are the symbols during a symbol period in which there are no RSs.
• Type B symbols are the symbols during a symbol period in which there are RSs.
The ratio of the PDSCH EPRE to the CRS EPRE for type A symbols (or type B symbols) is denoted by ρA (or ρB). Table 3-1 and Table 3-2 list the OFDM symbol indexes within a
timeslot with the ratio being ρA and ρB when the normal CP and extended CP are configured, respectively.
Table 3-1 OFDM symbol indexes (normal CP)
Number of Antenna Ports Symbol Indexes Where the Ratio Is Denoted by ρA Symbol Indexes Where the Ratio Is Denoted by ρB
1 or 2 1, 2, 3, 5, 6 0, 4
4 2, 3, 5, 6 0, 1, 4
Table 3-2 OFDM symbol indexes (extended CP)
Number of Antenna Symbol Indexes Where the Ratio Is Denoted by ρA Symbol Indexes Where the Ratio Is Denoted by ρB
Ports
1 or 2 1, 2, 4, 5 0, 3
4 2, 4, 5 0, 1, 3
PDSCH power control determines the EPREs of different OFDM symbols by using ρA and ρB. ρA is used to determine the EPRE of type A symbols on the PDSCH, and ρB is
used to determine the EPRE of type B symbols on the PDSCH.
The EPRE of type A symbols and that of type B symbols on the PDSCH are denoted by PPDSCH_A and PPDSCH_B, respectively. The calculation formulas are as follows:
PPDSCH_A = ρA + PDSCHCfg.ReferenceSignalPwr
PPDSCH_B = ρB + PDSCHCfg.ReferenceSignalPwr
• ρA is calculated as follows:
◾ If PDSCH data transmission uses transmit diversity with four antenna ports, ρA equals .

◾ In other scenarios, ρA equals in units of dB.
PA is a UE-specific parameter provided by RRC signaling for PDSCH demodulation, and indicates the offset of ρA to PA. equals 0 in all
PDSCH transmission schemes except multi-user multiple-input multiple-output (MU-MIMO).
• ρB depends on the power factor ratio ρB/ρA. Table 3-3 lists the values of the cell-specific ratio ρB/ρA corresponding to different PB values in scenarios with different
quantities of antenna ports. PB is specified by the PDSCHCfg.Pb parameter.
Table 3-3 Values of ρB/ρA for one, two, or four antenna ports
PB ρB/ρA (One Antenna Port) ρB/ρA (Two or Four Antenna Ports)
0 1 5/4
1 4/5 1
2 3/5 3/4
3 2/5 1/2
3.11.2 Power Control Policy

The PDSCH power control policy varies depending on the setting of the ENodeBAlgoSwitch.DlIcicSwitch parameter, which controls downlink ICIC, as described in Table 3-4.
Table 3-4 PDSCH power control policy
ICIC Switch Setting PDSCH Power Control Policy
The ENodeBAlgoSwitch.DlIcicSwitch parameter is set to The eNodeB calculates the PDSCH transmit power based on PA specified by
DlIcicDynamicSwitch_ON_ENUM or DlIcicStaticSwitch_ON_ENUM, the CellDlpcPdsch.CcuPa and CellDlpcPdsch.CeuPa parameters for cell-
indicating that downlink ICIC is enabled. center users and cell-edge users, respectively.
The ENodeBAlgoSwitch.DlIcicSwitch parameter is set to The eNodeB takes a fixed value for the PDSCH transmit power. PA is
DlIcicSwitch_OFF_ENUM, indicating that downlink ICIC is disabled. specified by the CellDlpcPdschPa.PaPcOff parameter.
Micro eNodeBs do not support downlink ICIC, and therefore the PDSCH power control policy in micro eNodeBs is the same as that in macro eNodeBs with downlink ICIC
disabled.
2 PMCH
The PMCH is used for transmitting the control information and user data of evolved multimedia broadcast/multicast service (eMBMS). The PMCH is carried on one or multiple
Multimedia Broadcast multicast service Single Frequency Network (MBSFN) subframes.
PMCH transmit power control uses the CellChPwrCfg.PmchPwrOffset parameter. The PMCH transmit power is calculated using the following formula:
PPMCH = Pmax_out + CellChPwrCfg.PmchPwrOffset
where:
• PPMCH indicates the PMCH transmit power.

• Pmax_out indicates the maximum PDSCH transmit power.
Pmax_out = Max{PPDSCH_A, PPDSCH_B}
For details about the formulas for calculating PPDSCH_A and PPDSCH_B, see 3.11.1 Power Calculation.
• The CellChPwrCfg.PmchPwrOffset parameter indicates the offset of the PMCH transmit power relative to Pmax_out.
If cell power has not exceeded either the licensed power capacity or the transmit power capability of the sector equipment serving the cell, operators can set the
offset to increase the PMCH transmit power. By doing this, the eNodeB will select a high-index modulation and coding scheme (MCS) to increase the MBMS service
capacity.
NOTE:
Currently, the offset is specific to cells, instead of sector equipment or sector equipment group.
In a single frequency network (SFN) cell, the PMCH transmit power must not exceed the licensed power capacity of any physical cell or the transmit power capability of sector
equipment. Otherwise, cell activation or cell reestablishment will fail.
3 Unbalanced Transmit Power Configurations Between Channels

Unbalanced transmit power configuration between channels can be enabled to increase the overall downlink transmit power and improve downlink performance if unbalanced
transmit power can be used by physical channels available for LTE within a multimode RF module and one of the following features is used:
• LOFD-001001 DL 2x2 MIMO

The offsets of physical channel transmit power relative to the baseline transmit power can be set using the following parameters:
The transmit power for physical channels can be calculated by the following formulas:
• Pmax_Ant0 = Pmax_out + PDSCHCfg.TxPowerOffsetAnt0

where:
• Pmax_Ant0 indicates the maximum transmit power for physical channel 0.

• Pmax_out indicates the maximum PDSCH transmit power.
NOTE:

• The baseline transmit power is determined by the system bandwidth, CRS power, PA, and PB.
• The function of unbalanced transmit power configurations between channels does not apply to SFN cells currently.
• AAUs do not support unbalanced transmit power configurations between channels.
4 Uplink Power Control
Overview
This chapter describes the following basic features:

This section outlines the basic principles of power control for the PUSCH and PUCCH.
NOTE:
Power control for the SRS and PRACH differs from power control for the PUSCH or the PUCCH, and the SRS transmit power depends on the effect of PUSCH power control.
This section does not describe power control for the SRS and the PRACH. For related descriptions, see 4.2 PRACH and 4.5 SRS. The demodulation reference signal (DMRS)
transmit power is consistent with the PUSCH transmit power.
PUSCH power control and PUCCH power control allow UEs to adjust their transmit power based on the TPC commands received from the eNodeB.
An eNodeB sends a TPC command over the PDCCH to a UE after generating the command based on the power control parameter settings, interference from neighboring cells,
eNodeB measurement results on uplink data transmission, and feedback from the UE. According to the mapping defined in section 5.1 "Uplink power control" in 3GPP TS
36.213 V9.3.0, the UE converts the TPC command into a power adjustment value. Then, the UE determines its transmit power based on factors including the power adjustment
value, its own maximum transmit power, the nominal power of the cell, the path loss, the MCS, and the amount of radio resources. By adjusting UEs' transmit power, uplink
power control enables the transmission performance of radio links to approach the target value, suppressing inter-cell interference.
NOTE:
SINR and reference signal received power (RSRP) mentioned in this chapter refer to those of uplink channels only.
PRACH
PRACH power control allows UEs to use the minimum transmit power to send random access preambles while ensuring the random access success rate. In this way,
interference to neighboring cells reduces and power consumption of UEs decreases.

The PRACH transmit power is calculated using the following formula:
where:
• is the UE power capability.
• is the target PRACH transmit power expected by the eNodeB when the requirements for the preamble detection performance are met and the PRACH
preamble format is 0. The initial value of is specified by the RACHCfg.PreambInitRcvTargetPwr parameter. If this parameter is set to a smaller value, the
probability of correct preamble demodulation decreases. If this parameter is set to a larger value, interference to neighboring cells increases.
• is the downlink path loss estimated by the UE. This value is obtained based on the RSRP measurement value and the CRS power. Parameters
PDSCHCfg.ReferenceSignalPwr and CellUlpcDedic.FilterRsrp specify the CRS power and the alpha filtering coefficient used for RSRP measurement value filtering.
The UE acquires the two parameter settings from SIB2.
• is the offset of the power for the current preamble format relative to the power for preamble format 0.
• is the number of times the UE sends the preamble. This value cannot exceed the maximum allowed number of preamble transmissions.
• is the preamble power ramping step. This variable is specified by the RACHCfg.PwrRampingStep parameter.
The eNodeB sends and to a UE by broadcasting SIB2, and the UE calculates the transmit power for the random access preamble based on , , , and
the recorded .
4.2.2 Power Ramping

If a random access procedure initiated by a UE fails before the number of preamble transmissions reaches the maximum, the UE retransmits the random access preamble using
increased PRACH transmit power. The overall PRACH transmit power ramping process is as follows:
1. The UE sends a random access preamble.

2. If the eNodeB correctly detects this preamble, it sends a random access response to the UE.
3. If the UE does not receive the random access response, it retransmits the preamble with the PRACH transmit power increased by each time and counts
until it either receives an RAR message or reaches the maximum number of preamble transmissions.
PUSCH
PUSCH power control aims to:
• Lower interference to neighboring cells and increase cell throughput.

• Ensure service rates for cell-edge users.

The PUSCH transmit power is calculated using the following formula:
where:

• represents the ith uplink subframe.
• is the number of resource blocks (RBs) used in the th uplink subframe.
• is the received power spectral density (PSD) expected by the eNodeB. It is calculated as follows:
◾ is the transmit PSD of the PUSCH expected by the eNodeB for correct PUSCH demodulation. is specified by
the CellUlpcComm.P0NominalPUSCH parameter.
◾ is the offset of the UE transmit power relative to . This offset reflects the impacts of UE categories, service types, and
channel qualities on the PUSCH transmit power.
• α is the path-loss compensation factor. It is specified by the CellUlpcComm.PassLossCoeff parameter.
• is the downlink path loss estimated by the UE. For details, see 4.2.1 Power Calculation. If the UE is working in the uplink carrier aggregation (CA) state, the
CellUlpcDedic.PathlossReferenceLink parameter can be used to control downlink path loss estimation in the secondary serving cell (SCell) of the UE.
• is the offset of the power for the current MCS relative to the power for the reference MCS. If the CellUlpcDedic.DeltaMcsEnabled parameter is set to
UU_ENABLE, is a non-zero value. If this parameter is set to UU_DISABLE, is 0.
• is the adjustment to the PUSCH transmit power. UEs obtain the adjustment values from the TPC commands sent over the PDCCH.
The initial value of is calculated using the following formula:
◾ indicates the transmit power increase for the random access preamble.
◾ indicates the offset used for power calculation. It is specified by the CellUlPcComm.DeltaMsg2 parameter.

The measurement values required for power control may not be ready in the early phase for UEs that initially access or are handed over to a cell. The eNodeB sets the transmit
PSD for the PUSCH based on , , and α, enabling cell-edge users to successfully access the cell and perform services.
, , and α affect the transmit PSD. Smaller values of these factors result in a decrease in both the access success rate and service rate. Larger values
cause a decrease in the amount of resources allocated to UEs and an increase in the transmit power in the early phase after UE access, which increases the interference to
neighboring cells.

During service provision, path loss and shadow fading need to be tracked and the transmit PSD needs to be dynamically adjusted on a periodic basis. While meeting service
quality requirements, PUSCH transmit power adjustment reduces UE transmit power to lower interference to neighboring cells and to increase network capacity.
Dynamic scheduling and semi-persistent scheduling apply to different types of services carried on the PUSCH. PUSCH power control uses different policies for these two
scheduling modes.
Inter-cell interference increases with network load, and stronger inter-cell interference leads to lower data rates of cell-edge users. To reduce inter-cell interference and improve
cell-edge user experience, interference control is used in PUSCH power control with dynamic scheduling applied.
USCH Transmit Power Adjustment with Dynamic Scheduling Applied
PUSCH power control with dynamic scheduling applied is controlled by the InnerLoopPuschSwitch(InnerLoopPuschSwitch) option of the CellAlgoSwitch.UlPcAlgoSwitch
parameter. When this option is selected, the eNodeB estimates the transmit PSD of the UE and, based on the difference between the estimated and the target transmit PSDs,
periodically adjusts the PUSCH transmit power. The adjustment adapts to changes in channel conditions and traffic loads.
• If the estimated transmit PSD is greater than the target value, the eNodeB sends the UE a TPC command, ordering a decrease in transmit power.
• If the estimated transmit PSD is less than the target value, the eNodeB sends the UE a TPC command, ordering an increase in transmit power.
• If the estimated transmit PSD is equal to the target value, the eNodeB sends the UE a TPC command, ordering no changes in transmit power.
NOTE:
The transmit PSD in the E-UTRAN refers to the transmit power per RB.
USCH Transmit Power Adjustment for UEs Running Voice Services with Dynamic Scheduling Applied
A high threshold used to determine high PUSCH SINR does not necessarily increase throughput of UEs running voice services. On condition that voice quality does not
degrade, a proper decrease in the transmit power of these UEs lowers uplink interference and increases the voice quality of cell-edge users.
When the InnerLoopPuschSwitch(InnerLoopPuschSwitch) option of the CellAlgoSwitch.UlPcAlgoSwitch parameter is selected, the PUSCH transmit power of UEs running
voice services can be adjusted based on the CellPcAlgo.VoLteSinrHighThdOffset parameter setting. This parameter specifies the offset of the PUSCH high-SINR threshold for
UEs running voice services relative to the PUSCH high-SINR threshold for UEs running data services.
USCH Closed-loop Power Control Optimization on UEs Near the Cell Center
The PUSCH transmit power of UEs near the cell center can be adjusted based on the measured SINR to prevent the transmit power from being excessively high. If the SINR
evaluation value is greater than the high-SINR threshold, the eNodeB sends TPC commands, instructing UEs to decrease transmit power.
On a network with the presence of inter-RAT or intermittent interference, the measured SINR may be falsely high due to the difficulty to detect intermittent interference. In this
case, PUSCH closed-loop power control incorrectly instructs UEs near the cell center to lower the PUSCH transmit power, which decreases uplink throughput of these UEs. To
accurately adjust the PUSCH transmit power of these UEs, PUSCH closed-loop power control optimization must be enabled. The eNodeB selects the SINR evaluation value to
be compared with the high-SINR threshold based on the settings of parameters CellAlgoSwitch.UlPcAlgoSwitch and CellPcAlgo.NearPointUePuschType.
• When the NearPointUeOptPUSCHSwitch(NearPointUeOptPUSCHSwitch) option of the CellAlgoSwitch.UlPcAlgoSwitch parameter is selected:

◾ If the CellPcAlgo.NearPointUePuschType parameter is set to AllUser(AllUser), the eNodeB considers the smaller values between the measured SINR
values and the SINRs after adjustment as the SINR evaluation values for all UEs.
◾ If the CellPcAlgo.NearPointUePuschType parameter is set to UlBigPktUser(UlBigPktUser), the eNodeB considers the smaller values between the
measured SINR values and the SINRs after adjustment as the SINR evaluation values for UEs that are identified as the ones running uplink large-packet
services. The eNodeB considers the measured SINR values as the SINR evaluation values for other UEs.
• If the NearPointUeOptPUSCHSwitch(NearPointUeOptPUSCHSwitch) option of the CellAlgoSwitch.UlPcAlgoSwitch parameter is deselected, the eNodeB

considers the measured SINR values as the SINR evaluation values for all UEs.
SRP Upper Limit in PUSCH Closed-loop Power Control

PUSCH closed-loop power control may apply an upper limit to the RSRP of the PUSCH so as to control UE transmit power. This prevents uplink received power saturation at
repeaters and reduces uplink interference. The PuschRsrpHighThdSwitch(PuschRsrpHighThdSwitch) option of the CellAlgoSwitch.UlPcAlgoSwitch parameter determines
whether to enable this function. The CellPcAlgo.PuschRsrpHighThd parameter determines the upper limit. This function works as follows:
• If the PuschRsrpHighThdSwitch(PuschRsrpHighThdSwitch) option is selected, PUSCH closed-loop power control applies an upper limit to the RSRP of the
PUSCH. Uplink demodulation performance can be ensured.
• If the PuschRsrpHighThdSwitch(PuschRsrpHighThdSwitch) option is deselected, PUSCH closed-loop power control does not limit the RSRP of the PUSCH.
T-based PUSCH Power Control with Dynamic Scheduling Applied
This section describes the basic feature LBFD-070105 IoT-based PUSCH Power Control. IoT stands for interference over thermal.
The CellAlgoSwitch.ULPcAlgoSwitch parameter determines whether to enable IoT-based PUSCH power control with dynamic scheduling applied.
• If the PuschIoTCtrlSwitch(PuschIoTCtrlSwitch) option of the parameter is selected, a heavily loaded cell initiates a load indication procedure by sending Overload
Indication messages to neighboring cells over X2 interfaces, informing the neighboring cells of the interference level experienced per PRB in the local cell. After a
neighboring cell receives the Overload Indication message, UEs near and at middle distances from the cell center decrease their transmit power to reduce the
interference to other cells. When the heavy load in the local cell is relieved, the local cell stops sending the Overload Indication messages.
• If the PuschIoTCtrlSwitch(PuschIoTCtrlSwitch) option of the parameter is deselected, PUSCH power control does not consider inter-cell interference, and cells do
not exchange interference information.
NOTE:
The PuschIoTCtrlSwitch(PuschIoTCtrlSwitch) option takes effect only when both the InnerLoopPuschSwitch(InnerLoopPuschSwitch) option of the
CellAlgoSwitch.ULPcAlgoSwitch parameter and the SchedulerCtrlPowerSwitch(SchedulerCtrlPowerSwitch) option of the CellAlgoSwitch.UlSchSwitch parameter are
selected. For details about the SchedulerCtrlPowerSwitch(SchedulerCtrlPowerSwitch) option, see Scheduling Feature Parameter Description.
IoT-based PUSCH power control with dynamic scheduling enabled works when intra-RAT interference ramps in a heavily-loaded cell. Do not enable this function if inter-RAT
interference is present. Otherwise, the local cell sends Overload Indication messages to inter-RAT neighboring cells and UEs in those cells unnecessarily decrease their
transmit power.
USCH Transmit Power Adjustment with Semi-Persistent Scheduling Applied
The CellAlgoSwitch.UlPcAlgoSwitch parameter determines whether to adjust the PUSCH transmit power when semi-persistent scheduling is enabled.
When the CloseLoopSpsSwitch(CloseLoopSpsSwitch) option of the parameter is selected, a UE periodically adjusts the PUSCH transmit power based on the difference
between the measured IBLER and the target IBLER (IBLERTarget) to adapt to channel condition changes. The value of IBLERTarget depends on the service requirements in semi-
persistent scheduling.
• If the measured IBLER is greater than IBLERTarget, the eNodeB sends a TPC command to the UE, ordering an increase in the transmit power.
• If the measured IBLER is less than IBLERTarget, the eNodeB sends a TPC command to the UE, ordering a decrease in the transmit power.
• If the measured IBLER is equal to IBLERTarget, the eNodeB sends a TPC command to the UE, ordering no changes in the transmit power.
The PUSCH-related TPC commands for multiple semi-persistently scheduled UEs are sent to the UEs over the PDCCH with DCI format 3. This reduces PDCCH signaling
overhead.
4.3.4 Msg3 Power Control During Random Access

Msg3, in the random access procedure, is the RRC Connection Request message. When the PUSCH carries Msg3, the PUSCH transmit power of each UE is calculated using
the following formula:
where:
• is the number of RBs used in the th uplink subframe.
• is the target PRACH transmit power expected by the eNodeB when the requirements for the preamble detection performance are met and the PRACH
preamble format is 0.
• is the offset of the Msg3 power relative to the random access preamble power during random access. This offset is specified by the
CellUlpcComm.DeltaPreambleMsg3 parameter.
• is the downlink path loss estimated by the UE. For details, see 4.2.1 Power Calculation.
• is the offset of the power for the current MCS relative to the power for the reference MCS. For details, see 4.3.1 Power Calculation.
• is the adjustment to the UE transmit power for the PUSCH. UEs obtain the adjustment values from the TPC commands sent over the PDCCH.
The transmit power for sending Msg3 is determined based on and the parameters related to PUSCH power control. For details about , see 4.2 PRACH.
PUCCH
The PUCCH carries the ACKs/NACKs to downlink data, CQIs, and scheduling requests (SRs). User throughput is severely affected if the probability of incorrect PUCCH
demodulation is excessively high. PUCCH power control aims to ensure the PUCCH performance and reduce the interference to neighboring cells.

The PUCCH transmit power is calculated using the following formula:
where:
• is the received PSD expected by the eNodeB. It is calculated as follows:
◾ is the target PSD expected by the eNodeB and is specified by the CellUlpcComm.P0NominalPUCCH parameter.
◾ is the offset of the UE transmit power relative to . This offset reflects the impacts of UE categories, service types, and
channel qualities on the PUCCH transmit power.

• is the downlink path loss estimated by the UE. A UE works out this value based on the measured RSRP and the CRS power contained in SIB2. The alpha
filtering coefficient used to filter the RSRP measurement values is specified by the CellUlpcDedic.FilterRsrp parameter.
• is dependent on the PUCCH format. The variable nCQI indicates the number of information bits for a CQI and reflects the impact of the number of
CQI bits of the PUCCH on the PUCCH transmit power. The variable nHARQ indicates the number of information bits for HARQ and reflects the impact of HARQ-
related signaling over the PUCCH on the PUCCH transmit power.
• reflects the impact of a PUCCH format on the PUCCH transmit power. It is specified by the following parameters:
◾ CellUlpcComm.DeltaFPUCCHFormat1
◾ CellUlpcComm.DeltaFPUCCHFormat1b
◾ CellUlpcComm.DeltaFPUCCHFormat2
◾ CellUlpcComm.DeltaFPUCCHFormat2a
◾ CellUlpcComm.DeltaFPUCCHFormat2b
• is the adjustment to the PUCCH transmit power. UEs obtain the adjustment values from the TPC commands sent over the PDCCH.
The initial value of is calculated using the following formula: .
◾ indicates the transmit power increase for the random access preamble.
◾ indicates the offset used for power calculation during random access.
The eNodeB sets the PUCCH transmit power based on and in early stages after a UE initially accesses or is handed over to a cell. This ensures that
cell-edge UEs can successfully access the cell.

During service provision, PUCCH transmit power adjustment tracks path loss and shadow fading and dynamically adjusts the transmit power to meet the requirements for
channel quality.
UCCH Outer-Loop Power Control
This section describes the basic feature LBFD-081101 PUCCH Outer Loop Power Control.
PUCCH outer-loop power control is controlled by the CellAlgoSwitch.UlPcAlgoSwitch parameter.
When the OuterLoopPucchSwitch(OuterLoopPucchSwitch) option of the parameter is selected, the eNodeB dynamically adjusts the target SINR (SINRTarget) for inner-loop
power control of the PUCCH in format 1a, 1b, or 3 based on the difference between the measured bit error rate (BER) and the target BER (BERTarget) of the PUCCH in format 2,
2a, or 2b. This feature helps implement PUCCH power control based on channel conditions, improve PUCCH demodulation performance, and decrease the false detection rate
of the PUCCH in format 2, 2a, or 2b, increasing downlink throughput. The adjustment rules are as follows:
• If the measured BER is greater than the BERTarget, the eNodeB increases the SINRTarget.
• If the measured BER is equal to the BERTarget, the eNodeB does not change the SINRTarget.
• If the measured BER is less than the BERTarget, the eNodeB decreases the SINRTarget.
NOTE:
After the OuterLoopPucchSwitch(OuterLoopPucchSwitch) option is selected, the RSRP upper limit is no longer effective for the PUCCH, and downlink throughput increases
even when strong interference is present.
When the OuterLoopPucchSwitch(OuterLoopPucchSwitch) option is deselected, a fixed SINRTarget is used for PUCCH inner-loop power control.
UCCH Inner-Loop Power Control
PUCCH inner-loop power control is controlled by the CellAlgoSwitch.UlPcAlgoSwitch parameter.

When the InnerLoopPucchSwitch(InnerLoopPucchSwitch) option of the parameter is selected, the eNodeB periodically adjusts the PUCCH transmit power based on the
difference between the measured SINR and the SINRTarget to adapt to channel condition changes.
The PUCCH power control period is 200 ms by default and can be set using the CellPcAlgo.PucchPcPeriod parameter. If PUCCH outer-loop power control is enabled, the
PUCCH inner-loop power control period is always 20 ms.
SINRTarget is determined by the BLER requirements of different PUCCH formats and the eNodeB demodulation capability. To lift the maximum SINRTarget and increase the
PUCCH transmit power, the CellPcAlgo.PucchPcTargetSinrOffset parameter can be used to set the offset to the SINRTarget (referred to as SINROffset). These variables are used
as follows:
• If the measured SINR is greater than the sum of SINRTarget and SINROffset, the eNodeB sends a TPC command to the UE, ordering a decrease in the transmit power.
• If the measured SINR is less than the sum of SINRTarget and SINROffset, the eNodeB sends a TPC command to the UE, ordering an increase in the transmit power.
• If the measured SINR is equal to the sum of SINRTarget and SINROffset, the eNodeB sends a TPC command to the UE, ordering no changes in the transmit power.
UCCH Power Control Enhancement
The CellPcAlgo.PucchCloseLoopPcType parameter determines whether to enable PUCCH power control enhancement. This function requires changing the PUCCH RSRP
threshold by setting the CellUlpcComm.P0NominalPUCCH parameter.
• When the CellPcAlgo.PucchCloseLoopPcType parameter is set to USE_P0NOMINALPUCCH(Use P0NominalPUCCH):

◾ Increasing the value of CellUlpcComm.P0NominalPUCCH raises the PUCCH RSRP threshold and consequently further increases the PUCCH transmit
power of cell-center users.
◾ Decreasing the value of CellUlpcComm.P0NominalPUCCH lowers the PUCCH RSRP threshold, and consequently the PUCCH power of cell-center users
may decrease.
• When the CellPcAlgo.PucchCloseLoopPcType parameter is set to NOT_USE_P0NOMINALPUCCH(Not Use P0NominalPUCCH), changing the
CellUlpcComm.P0NominalPUCCH parameter value does not change the PUCCH RSRP threshold, and therefore PUCCH power control enhancement does not work.
tial Fast PUCCH Power Control
The CellAlgoSwitch.UlPcAlgoSwitch parameter determines whether to enable initial fast PUCCH power control.
If the PucchInitialPcSwitch(PucchInitialPcSwitch) option of the parameter is selected, the eNodeB determines whether to enable initial fast PUCCH power control based on
the difference (DeltaSinrinitial) between the initially reported SINR and SINRTarget.
If the value of DeltaSinrinitial is too large, initial fast PUCCH power control takes effect. The eNodeB includes TPC commands in each DL grant, and instructs the UE to decrease
the PUCCH transmit power. This function stops and the original PUCCH power control policy takes effect when the measured SINR approaches the SINRTarget. If the value of
DeltaSinrinitial is not too large, the original PUCCH power control policy takes effect.
4.4.4 Optimized PUCCH Power Control at DTXs

A DTX may occur because the UE has not received DL grants, the PUCCH transmit power is too low, or interference is excessively strong. However, it is difficult for an eNodeB
to determine which of these conditions has occurred when it recognizes the DTX. To prevent incorrect adjustments to the PUCCH transmit power, the eNodeB performs the
following operations for PUCCH power control, depending on the setting of the CellAlgoSwitch.UlPcAlgoSwitch parameter:
• If the PucchPcDtxSinrSwitch(PucchPcDtxSinrSwitch) option of the parameter is deselected, the eNodeB discards the measured SINR of the PUCCH signals that
are considered in the DTX state. If the DTX is caused by low PUCCH transmit power or strong interference, PUCCH power control cannot increase the PUCCH
transmit power of the UE and therefore PUCCH demodulation performance deteriorates.
• If the PucchPcDtxSinrSwitch(PucchPcDtxSinrSwitch) option of the parameter is selected, the eNodeB performs amplitude limiting and filtering on the measured
SINR for the PUCCH signals that are considered in the DTX state. The eNodeB then uses the new SINR as an input to PUCCH power control.
SRS
The SRS is used for uplink channel estimation and uplink timing, and therefore SRS power control ensures the accuracy of these activities.

The SRS transmit power is calculated using the following formula:
where:
• is the transmission bandwidth of the SRS.
• is the offset of the SRS transmit power relative to the PUSCH transmit power. This value is specified by the CellUlpcDedic.PSrsOffsetDeltaMcsDisable
or CellUlpcDedic.PSrsOffsetDeltaMcsEnable parameter, depending on the CellUlpcDedic.DeltaMcsEnabled parameter value.
• is the target PSD expected by the eNodeB when dynamic scheduling is used on the PUSCH.
• α is the path-loss compensation factor and can be set using the CellUlpcComm.PassLossCoeff parameter.
• is the downlink path loss estimated by the UE. This value is calculated based on the measured RSRP and the CRS transmit power. The alpha filtering coefficient
used to filter the RSRP measurement values is specified by the CellUlpcDedic.FilterRsrp parameter.
• is the adjustment to the UE transmit power for the PUSCH, and can be obtained from the TPC commands sent over the PDCCH.
4.5.2 Power Setting by the eNodeB
The eNodeB determines the SRS transmit power based on the configured , the amount of resources, and PUSCH power control parameters and .
5 Related Features
LBFD-002016 Dynamic Downlink Power Allocation
erequisite Features
None
LOFD-081208 Inter-eNodeB SFN Based on Coordinated BBU The function of unbalanced transmit power
configurations between channels does not apply to
LOFD-081209 Inter-eNodeB Adaptive SFN/SDMA Based on SFN cells.
Coordinated BBU
pacted Features
LBFD-002025 Basic Scheduling Enabling PDCCH power control causes power

changes and therefore affects these two scheduling
features. The power change helps increase
LOFD-00101502 Dynamic Scheduling downlink throughput and decrease the service drop
rate.
LOFD-00101501 CQI Adjustment CQI adjustment (controlled by the

CellAlgoSwitch.CqiAdjAlgoSwitch parameter)
increases the accuracy of CQIs for PDSCH power
control and therefore improves the performance of
PDSCH power control.
erequisite Features
None
None
pacted Features
LBFD-002025 Basic Scheduling The uplink power control algorithm provides the uplink scheduling algorithm with the
power headroom of a UE. Based on the power headroom, the scheduler determines
LOFD-00101502 Dynamic Scheduling an MCS and the number of RBs for the UE to maximize network throughput while
meeting the QoS requirements of the UE. The uplink scheduling algorithm provides


the uplink power control algorithm with the transport block size (TBS) and the number
of allocated RBs for UE transmit power setting.
In addition, the uplink scheduling algorithm provides the uplink power control
algorithm with information such as the PUCCH format and SRS resource amount for
related power setting.
LOFD-001016 VoIP Semi-persistent Scheduling The uplink semi-persistent scheduling algorithm provides the uplink BLER as an input
to the uplink power control algorithm. The BLER is a prerequisite for enabling PUSCH
transmit power adjustment in semi-persistent scheduling. If uplink semi-persistent
scheduling is enabled, you are advised to enable PUSCH closed-loop power control
with semi-persistent scheduling applied (by setting CloseLoopSpsSwitch on).
LBFD-002010 Random Access The random access control algorithm provides the uplink power control algorithm with
information such as the preamble format and the number of times the UE sends the
preamble, ensuring the UE transmit power during the random access procedure.
LBFD-070105 IoT-based PUSCH Power Control
erequisite Features
None
None
pacted Features
LBFD-002025 Basic Scheduling Uplink scheduling provides IoT-based PUSCH

power control with TBSs and the number of
allocated PRBs for UE power setting. To ensure full
utilization of UE transmit power, the
SchedulerCtrlPowerSwitch
LOFD-00101502 Dynamic Scheduling (SchedulerCtrlPowerSwitch) option of the
CellAlgoSwitch.UlSchSwitch parameter must be
selected when IoT-based PUSCH power control is
enabled.
LBFD-002026 Uplink Power Control IoT-based PUSCH power control is an optimization

of PUSCH inner-loop power control. Therefore, the
InnerLoopPuschSwitch(InnerLoopPuschSwitch)
option must be selected when IoT-based PUSCH
power control is enabled.
LBFD-081101 PUCCH Outer Loop Power Control
erequisite Features
LBFD-002026 Uplink Power Control PUCCH outer-loop power control works only if the
PUCCH inner-loop power control function of uplink
None
pacted Features
None
6 Network Impact
LBFD-002016 Dynamic Downlink Power Allocation
stem Capacity
PDSCH power control has an immediate impact on downlink network capacity. The CRS power, PA, PB, and offset of physical channel transmit power relative to the baseline
transmit power affect cell throughput. These parameters indicate the total transmit power of a cell. Excessively large values of them result in significant interference to
neighboring cells, and unexpectedly small values cause power waste and decreases in coverage and throughput.
Good performance of the PCFICH, PHICH, and PDCCH ensures network functionality. Power control for these channels affects channel reliability, which in turn affects various
performance indicators, including:
• PCFICH power control has an impact on PDCCH demodulation and uplink and downlink throughput.
• PHICH power control has an impact on uplink ACK/NACK demodulation and uplink HARQ processes, affecting indicators such as uplink throughput and latency.
• When the PDCCH carries dedicated control information, PDCCH power control has an impact on indicators such as uplink and downlink throughput and latency
• RAR power control affects the power for RAR message transmission, which in turn affects indicators such as the dedicated-preamble-based access success rate and
the handover success rate.
twork Performance
Downlink power control has an impact on key performance indicators (KPIs) in the following aspects:
• Access success rate

Downlink power control affects message transmission reliability during the access procedure. The power offsets for downlink channels affect the network coverage
for access. To enhance coverage, ensure the same coverage levels between uplink channels and between downlink channels.
• Handover success rate

For example, PDCCH power control affects handover message delivery. This has an impact on the handover success rate.
• Service drop rate
For example, PDCCH power control affects PDCCH reliability and further affects transmission on other uplink and downlink channels. This has an impact on the
service drop rate.
stem Capacity
Uplink power control has the following impacts on network capacity:
• PUSCH power control determines the transmit power of each UE and the number of RBs allocated for uplink transmission. Therefore, it has an immediate impact on
uplink network capacity.
• PUCCH power control affects the transmission reliability of uplink control information and ACKs/NACKs, and affects downlink throughput.
• SRS power control affects the accuracy of uplink timing and SINR measurements and has an impact on the performance of functions such as uplink AMC. Therefore,
SRS power control affects network throughput.
twork Performance
Uplink power control has an impact on KPIs in the following aspects:
• Access success rate

Uplink power control affects message transmission reliability during the access procedure.
In addition, uplink power control determines the coverage of channels and affects the network coverage for access. To enhance coverage, ensure the same
coverage levels between uplink channels and between downlink channels.
• Handover success rate
For example, power control for the PUSCH and PUCCH affects measurement reporting, and power control for the PRACH, PUSCH, and PUCCH affects the random
access procedure. Measurement reporting and random access both affect the handover success rate.
• Service drop rate
For example, power control for the PUSCH and PUCCH affects transmission reliability on uplink channels. This has an impact on the service drop rate.
• Voice quality
Adjustments on the PUSCH high-SINR threshold for UEs running voice services affect the voice quality of these UEs.
LBFD-070105 IoT-based PUSCH Power Control
stem Capacity
IoT-based PUSCH power control helps decrease uplink inter-cell interference on heavily loaded networks, enhancing uplink coverage and increasing the uplink throughput of
cell-edge users.
Lowering the PUSCH transmit power of UEs at places near and of medium distances to the cell center decreases interference on adjacent cells. However, uplink throughput of
these UEs may decrease.
The throughput change and user number change vary according to site conditions such as the number of users in the network, user distribution, service types, and settings of
parameters related to power control.
twork Performance
IoT-based PUSCH power control helps decrease uplink inter-cell interference on heavily loaded networks, increasing the access success rate and handover success rate and
decreasing the service drop rate.
LBFD-081101 PUCCH Outer Loop Power Control
stem Capacity
PUCCH outer-loop power control helps enhance PUCCH transmission reliability and decrease the probability of false detection of channel state information on the PUCCH,
increasing the average UE throughput and cell throughput in the downlink. The information includes CQI, rank indication (RI), and precoding matrix indication (PMI).
twork Performance
PUCCH outer-loop power control decreases the percentage of PUCCH DTXs and increases downlink throughput.
This feature helps decrease the downlink packet loss rate of VoLTE services and enhance voice quality of these services.
This feature may increase the number of uplink small packets, decreasing the ratio of L.Thrp.bits.UL to L.Thrp.Time.UL. The L.Thrp.bits.UL counter measures the total data
amount of uplink protocol data units (PDUs) received at the PDCP layer, and the L.Thrp.Time.UL counter measures the total time during which the uplink PDUs are received at
the PDCP layer.
NOTE:
The number of uplink small packet increases for either of the following reasons:
• The percentage of PDCCH DTXs decreases, which decreases the number of PDCCH CCEs to be consumed and increases PDCCH capacity. In this case, if most
UEs send small packets in the uplink, the number of small packets increases.
• The number of uplink TCP response packets increases along with the increase of downlink throughput.
When to Use
7.1.1 Downlink Power Control
namic PHICH Power Adjustment
The default PHICH power offset meets PHICH demodulation requirements. Dynamic power adjustment for the PHICH does not produce significant gains. Therefore, it is
recommended that the PhichInnerLoopPcSwitch(PhichInnerLoopPcSwitch) option of the CellAlgoSwitch.DlPcAlgoSwitch parameter be deselected so that fixed power
allocation for the PHICH takes effect.
AR Power Increase During Handovers
It is recommended that the CellChPwrCfg.HoRarPwrEnhancedSwitch parameter be set to ON(On) when the dedicated-preamble-based access success rate and handover
success rate are low due to downlink interference or weak downlink coverage.
wer Control for the PDCCH Carrying Dedicated Control Information

It is recommended that the PdcchPcSwitch(PdcchPcSwitch) option of the CellAlgoSwitch.DlPcAlgoSwitch parameter be selected to decrease the PDCCH transmit power in
the cell center and to reduce the service drop rate and increase the throughput for cell-edge users.
RS and Data Power Setting Suggestions
The settings of CRS power, PA, and PB determine the pilot power, data power, and the numeric relationship between the two types of transmit power. These settings affect
downlink throughput and KPIs such as the handover success rate and access success rate.
To improve downlink throughput and KPIs, configuration suggestions are provided as follows, which vary depending on the main source of interference to the data of the local
cell:
• The main source of interference is CRSs transmitted in neighboring cells when the neighboring cells are lightly loaded (cell load is lower than 20%).
In this case, an effective measure is to increase the data power and decrease the CRS power in the local cell, which decreases interference to neighboring cells.
Specifically, the following settings are recommended in a scenario with a total power of 40 W and a bandwidth of 20 MHz: CRS power = 15.2 dBm, PA = 0, and PB =
0.
• The main source of interference is data transmitted in neighboring cells when the neighboring cells are heavily loaded.
In this case, an effective measure is to increase the CRS power to an appropriate value in the local cell to improve the PDSCH demodulation performance.
Specifically, the following settings are recommended in a scenario with a total power of 40 W and a bandwidth of 20 MHz: CRS power = 18.2 dBm, PA = –3, and PB =
1.
crease in the Maximum Cell Transmit Power
• If the maximum cell transmit power does not exceed the maximum transmit power of a single-mode single-carrier RRU, you are advised to select the
EDlMaxTXPwrSwitch(EDlMaxTXPwrSwitch) option of the CellAlgoSwitch.DlPcAlgoSwitch parameter.
NOTE:
When this option is selected, there is a possibility that the transmit power of some subframes exceeds the expected maximum transmit power. This function must be
disabled in countries or regions where the instantaneous power is prohibited from exceeding the power limit.
• The EDlMaxTXPwrSwitch(EDlMaxTXPwrSwitch) option must be deselected for multi-mode or multi-carrier RRUs that may affect network performance.
NOTE:
When you run an MML command to change this option setting, a message will be displayed, indicating that the modification will have severe impact on the system. Cell services
will be interrupted if you change this option setting during network operation.
ttings of the Antenna RS Power (Applicable Only to Macro eNodeBs)
To ensure correct path loss calculation at UEs in scenarios where repeaters are used, it is recommended that the AntRsPwrSwitch(AntRsPwrSwitch) option of the
CellAlgoSwitch.RepeaterSwitch parameter be selected.
balanced Transmit Power Configurations Between Channels
It is recommended that this function be enabled if unbalanced transmit power can be used by channels available for LTE of a multimode RF module and one of the following
features is used:

7.1.2 Uplink Power Control

This section describes when to use uplink power control.
USCH Inner-Loop Power Control with Dynamic Scheduling Applied
It is recommended that the InnerLoopPuschSwitch(InnerLoopPuschSwitch) option of the Uplink power control algorithm switch parameter be selected to achieve higher
throughput of cell-edge users and scheduling fairness between users.
USCH Transmit Power Adjustment for UEs Running Voice Services with Dynamic Scheduling Applied
In a heavily loaded network with multiple cells (each cell serves more than 200 UEs among which more than 20 UEs run voice services), if UEs are distributed near, at medium
distances to, and far away from the cell center, and interference to the PUSCH is greater than –105 dBm, you are advised to set the CellPcAlgo.VoLteSinrHighThdOffset
parameter to its recommended value to decrease the transmit power of UEs running voice services, thereby decreasing uplink interference and improving voice service quality
of cell edge UEs.
USCH Closed-loop Power Control Optimization on UEs Near the Cell Center
To accurately adjust the PUSCH transmit power of UEs near the cell center, PUSCH closed-loop power control determines whether a UE needs to decrease its transmit power
for the PUSCH based on the smaller value between the measured SINR value and adjusted SINR value. UEs near the cell center increase the transmit power for the PUSCH in
networks with the presence of inter-RAT or intermittent interference, which increases uplink throughput of these UEs. However, this also increases uplink interference on
neighboring cells.
When cell-level SRS resources are not configured, it is recommended that this function be enabled and the CellPcAlgo.NearPointUePuschType parameter be set to
UlBigPktUser(UlBigPktUser). This function is not recommended when cell-level SRS resources are configured.
SRP Upper Limit in PUSCH Closed-loop Power Control
This function is recommended when repeaters are deployed. If this option is selected, PUSCH closed-loop power control ensures that the RSRP does not exceed the upper
limit. Therefore, uplink receive power saturation at repeaters (if any) can be prevented and uplink demodulation performance can be guaranteed. In addition, uplink interference
decreases.
USCH Closed-Loop Power Control with Semi-Persistent Scheduling Applied
If the CloseLoopSpsSwitch(CloseLoopSpsSwitch) option of the Uplink power control algorithm switch parameter is deselected, closed-loop power control is disabled for
the PUSCH with semi-persistent scheduling applied. If this option is selected, the eNodeB adjusts TPC commands based on whether the received initial-transmission data
packets are correct, ensuring that the IBLER approaches the target value.
PUSCH closed-loop power control with semi-persistent scheduling applied helps guarantee the VoLTE service quality. It is recommended that this option be selected when
uplink semi-persistent scheduling is enabled to achieve good VoLTE service performance, and be deselected when uplink semi-persistent scheduling is disabled.
If the CloseLoopSpsSwitch(CloseLoopSpsSwitch) option is selected in a cell with dynamic scheduling and semi-persistent scheduling both applied, it is recommended that
the InnerLoopPuschSwitch(InnerLoopPuschSwitch) option of the Uplink power control algorithm switch parameter also be selected to ensure user experience of all UEs
running voice services in the cell.
UCCH Inner-Loop Power Control
It is recommended that the InnerLoopPucchSwitch(InnerLoopPucchSwitch) option of the Uplink power control algorithm switch parameter be selected to ensure PUCCH
signal quality.
UCCH Power Control Enhancement
With PUCCH power control enhancement disabled, the PUCCH transmit power of cell-center users is restricted if the PUCCH experiences strong interference. In this situation,
the detection error rate on the PUCCH increases, which affects downlink throughput.

It is recommended that PUCCH power control enhancement be enabled when the PUCCH experiences high interference. With this function enabled, you can set the
CellUlpcComm.P0NominalPUCCH parameter to a large value to increase the PUCCH transmit power of UEs near the cell center and downlink throughput. The recommended
value for the CellUlpcComm.P0NominalPUCCH parameter is –110 in the unit of dBm.
Increasing the PUCCH transmit power of UEs near the cell center raises interference to neighboring cells and other UEs in the local cell, which further decreases downlink
throughput of cell-edge users.
NR Optimization for PUCCH Signals in DTX
If the PucchPcDtxSinrSwitch(PucchPcDtxSinrSwitch) option of the Uplink power control algorithm switch parameter is deselected, the eNodeB may fail to demodulate
PUCCH signals from UEs due to low PUCCH transmit power in a network with strong interference. If this option is selected, the PUCCH transmit power of UEs can be increased
in a network with strong interference to ensure successful PUCCH demodulation. It is recommended that options PucchPcDtxSinrSwitch(PucchPcDtxSinrSwitch) and
InnerLoopPucchSwitch(InnerLoopPucchSwitch) be both selected.
tial Fast PUCCH Power Control
Deselecting the PucchInitialPcSwitch(PucchInitialPcSwitch) option of the Uplink power control algorithm switch parameter prevents the SINR on the PUCCH from being
timely approaching the target SINR. As a result, inter-cell PUCCH interference and the probability of false PUCCH detections increase, and downlink throughput decreases.
Selecting this option allows the SINR on the PUCCH to rapidly approach the target value. In this way, the probability of false PUCCH detections decreases and downlink
throughput increases. In addition, the probability of missing SR detections and the uplink voice packet loss rate decreases, and the voice quality improves. Therefore, it is
recommended that options PucchInitialPcSwitch(PucchInitialPcSwitch) and InnerLoopPucchSwitch(InnerLoopPucchSwitch) be both selected.
It is recommended that initial fast PUCCH power control is function be enabled when all of the following conditions are met:
• The CellUlpcComm.P0NominalPUCCH parameter value is greater than or equal to –105 in the unit of dBm.
• Discontinuous reception (DRX) and dynamic DRX are disabled.
• The cell is located in a densely populated urban area.
7.1.3 IoT-based PUSCH Power Control

If the PuschIoTCtrlSwitch(PuschIoTCtrlSwitch) option of the Uplink power control algorithm switch parameter is deselected, PUSCH power control does not consider
inter-cell interference, which causes strong interference to cells in a heavily loaded network and low data rates at cell edges.
If this option is selected, PUSCH power control considers inter-cell interference according to the following situations:
• In a heavily-loaded network, neighboring cells that receive Overload Indication messages decrease the transmit power of UEs in or of medium distances to cell
centers to reduce uplink interference on the cell sending Overload Indication messages. This increases the data rate at the edge of the cell sending the messages.
However, uplink throughput of cells that receive the messages may decrease.
• In a lightly-loaded network, the eNodeB does not perform inter-cell interference control.
In a network with heavy traffic, it is recommended that the PuschIoTCtrlSwitch(PuschIoTCtrlSwitch) option be selected to ensure the performance of cell-edge users, and
parameters CellUlpcComm.P0NominalPUSCH and CellUlpcComm.PassLossCoeff be set to –96 in the unit of dBm and AL1(1), respectively.
A cell is heavily loaded if both the following conditions are met:
• The average interference on all PRBs scheduled on the PUSCH exceeds –98 dBm.
• The number of synchronized UEs exceeds the thresholds listed in Table 7-1.
Table 7-1 Synchronized UE number thresholds in a heavily-loaded cell
eNodeB Type Bandwidth UE Number Threshold
Macro and LampSite 10 MHz or more than 10 MHz 200
5 MHz or less than 5 MHz 150
Micro All bandwidths 80
If a cell is heavily loaded, you are advised to:
• Select the PuschIoTCtrlSwitch(PuschIoTCtrlSwitch) option in the local cell and its neighboring cells to ensure the performance of cell-edge users in the local cell.
• Set parameters CellUlpcComm.P0NominalPUSCH and CellUlpcComm.PassLossCoeff to –96 in the unit of dBm and AL1(1), respectively, in the local cell.
• Set parameters CellUlpcComm.P0NominalPUSCH and CellUlpcComm.PassLossCoeff to –106 in the unit of dBm and AL1(1), respectively, in the neighboring cells.
A smaller value of the CellUlpcComm.P0NominalPUSCH parameter results in a lower transmit power and lower uplink throughput of UEs in the cell, and also weaker
interference on neighboring cells. A larger value of this parameter results in the opposite effects.
If an SFN cell is served by RRUs of different models, the PuschIoTCtrlSwitch(PuschIoTCtrlSwitch) option must be deselected.
The PuschIoTCtrlSwitch(PuschIoTCtrlSwitch) option takes effect only when options InnerLoopPuschSwitch (InnerLoopPuschSwitch) and SchedulerCtrlPowerSwitch
(SchedulerCtrlPowerSwitch) are selected.
7.1.4 PUCCH Outer-Loop Power Control

If channel conditions of PUCCH in format 2/2a/2b are poor or the PUCCH is exposed to strong interference, PUCCH outer-loop power control helps increase the PUCCH
transmit power and downlink throughput. You are advised to enable PUCCH outer-loop power control in this situation.
It is recommended that this function be enabled only when all of the following conditions are met:
• The CellUlpcComm.P0NominalPUCCH parameter value is greater than or equal to –105 dBm.

• Both DRX and dynamic DRX are disabled.
• The cell is located in a densely populated urban area.
• The average interference on the PUCCH exceeds–110 dBm.
None.
Planning
None.
Deployment of Downlink Power Control

This section describes the deployment of LBFD-002016 Dynamic Downlink Power Allocation.
7.4.1 Requirements
Downlink power control has no requirements on the operating environment, transmission networking, or licenses.
7.4.2 Precautions
• Network services are interrupted if you change the setting of the EDlMaxTXPwrSwitch(EDlMaxTXPwrSwitch) option of the CellAlgoSwitch.DlPcAlgoSwitch
parameter during network operation.
• The following parameters can be configured only for non-SFN cells that have been deactivated:
◾ PDSCHCfg.TxPowerOffsetAnt0

AAUs do not support unbalanced transmit power configurations between channels. If the preceding parameters are configured for an AAU, the abnormal wave speed
will result in performance deterioration.

CRS Power Allocation
The following table describes the parameters that must be set in the PDSCHCfg MO to specify CRS power.

Name
Local cell ID PDSCHCfg.LocalCellId Network plan This parameter specifies the local identity of a cell. Set this parameter based on the
(negotiation not network plan. Ensure that this parameter has been set in a Cell MO.
required)
Reference PDSCHCfg.ReferenceSignalPwr Network plan This parameter specifies the CRS power for a cell. Set this parameter based on the
signal power (negotiation not network plan during eNodeB deployment.
required)
(Optional) The following table describes the parameters that must be set in the EuSectorEqmGroup MO to specify the RS power of a sector equipment group for a multi-RRU
cell that works in MPRU aggregation mode under a LampSite eNodeB.
Sector EuSectorEqmGroup.SectorEqmGroupId Network plan (negotiation not None

Equipment required)
Group ID
Reference EuSectorEqmGroup.ReferenceSignalPwr Network plan (negotiation not This parameter specifies the RS power of the sector
signal power required) equipment group for a cell. If this parameter is set to
32767, the RS power is invalid, and the cell uses the
RS power specified in the PDSCHCfg MO.
(Optional) The following table describes the parameters that must be set in the eUCellSectorEqm MO to specify the RS power of each RRU that serves a multi-RRU cell
working in SFN, cell combination, or MPRU aggregation mode.

Name
Sector eUCellSectorEqm.SectorEqmId Network plan (negotiation This parameter specifies the ID of the sector equipment that serves the
equipment ID not required) cell. Set this parameter to the sector equipment ID specified when the
sector or sector equipment is added.
Reference eUCellSectorEqm.ReferenceSignalPwr Network plan (negotiation This parameter specifies the RS power for the sector equipment. If this
signal power not required) parameter is set to 32767, the RS power is invalid, and the cell uses the
RS power specified in the PDSCHCfg MO.
Synchronization Signals Power Allocation

The following table describes the parameters that must be set in the CellChPwrCfg MO to specify synchronization signal power.
Local cell ID CellChPwrCfg.LocalCellId Network plan This parameter specifies the local identity of a cell. Set this parameter based on the
required)
SCH power CellChPwrCfg.SchPwr Network plan This parameter specifies the offset of the synchronization channel power relative to the
(negotiation not CRS power. When the bandwidth is 1.4 MHz, 3 MHz, or 5 MHz, set this parameter to the
required) value of the CellDlpcPdschPa.PaPcOff parameter. When the bandwidth is 10 MHz, 15
MHz, or 20 MHz, set this parameter to a value that is 3 dB greater than the
CellDlpcPdschPa.PaPcOff parameter value.
PBCH Transmit Power Allocation

The following table describes the parameters that must be set in the CellChPwrCfg MO to specify PBCH transmit power.
Local cell ID CellChPwrCfg.LocalCellId Network plan This parameter specifies the local identity of a cell. Set this parameter based on the
required)
PBCH power CellChPwrCfg.PbchPwr Network plan This parameter specifies the offset of the PBCH transmit power relative to the CRS
(negotiation not power. Set this parameter to the value of the CellDlpcPdschPa.PaPcOff parameter.
required)
PCFICH Transmit Power Allocation

The following table describes the parameters that must be set in the CellChPwrCfg MO to specify PCFICH transmit power.
Local cell ID CellChPwrCfg.LocalCellId Network plan This parameter specifies the local identity of a cell. Set this parameter based on
(negotiation not the network plan. Ensure that this parameter has been set in a Cell MO.
required)
PCFICH power CellChPwrCfg.PcfichPwr Network plan This parameter specifies the offset of the PCFICH transmit power relative to the
(negotiation not CRS power. Set this parameter to the value of the CellDlpcPdschPa.PaPcOff
required) parameter.
Power Allocation for RAR Messages

The following table describes the parameters that must be set in the CellChPwrCfg MO to specify RAR power.

Local cell ID CellChPwrCfg.LocalCellId Network plan This parameter specifies the local identity of a cell. Set this parameter based on
required)
Rach response power CellChPwrCfg.RaRspPwr Network plan This parameter specifies the offset of the RAR power relative to the CRS power.
(negotiation not Set this parameter to the value of the CellDlpcPdschPa.PaPcOff parameter.
required)
PHICH Power Allocation

The following table describes the parameters that must be set in the CellDlpcPhich MO to specify PHICH transmit power.
Local cell ID CellDlpcPhich.LocalCellId Network plan This parameter specifies the local identity of a cell. Set this parameter based on
required)
Phich Pc Off Power Offset CellDlpcPhich.PwrOffset Network plan This parameter specifies the offset of the PHICH power relative to the CRS
(negotiation not power when PHICH power control is disabled. Set this parameter to a value that
required) is 3 dB greater than the value of the CellDlpcPdschPa.PaPcOff parameter.
The following table describes the parameters that must be set in the CellAlgoSwitch MO to configure PHICH inner-loop power control.
Local cell ID CellAlgoSwitch.LocalCellId Network plan This parameter specifies the local identity of a cell. Set this parameter based
(negotiation not on the network plan. Ensure that this parameter has been set in a Cell MO.
required)
Downlink power control CellAlgoSwitch.DlPcAlgoSwitch Network plan This parameter specifies the options used to enable or disable downlink power
algorithm switch (negotiation not control for the PDSCH, PDCCH, and PHICH. It also specifies the power
required) control policy for the maximum cell transmit power.
PhichInnerLoopPcSwitch: This option specifies whether to enable PHICH
inner-loop power control. If this option is deselected, only the initial PHICH
power needs to be set. If this option is selected, the eNodeB adjusts the
PHICH power to enable the receiver SINR to approach the target SINR. It is
recommended that this option be deselected.
Power Allocation for the PDCCH Carrying Dedicated Control Information

The following table describes the parameters that must be set in the CellDlpcPdcch MO to specify PDCCH transmit power.
Local cell ID CellDlpcPdcch.LocalCellId Network plan This parameter specifies the local identity of a cell. Set this parameter based
required)
DCI power offset for CellDlpcPdcch.DediDciPwrOffset Network plan This parameter specifies the offset of the PDCCH power relative to the CRS
dedicated control (negotiation not power when the PDCCH carries dedicated control information. Set this
required) parameter to the value of the CellDlpcPdschPa.PaPcOff parameter.
The following table describes the parameters that must be set in the CellAlgoSwitch MO to configure PDCCH power control.
required)
Downlink power control CellAlgoSwitch.DlPcAlgoSwitch Network plan This parameter specifies the options used to enable or disable downlink
algorithm switch (negotiation not power control for the PDSCH, PDCCH, and PHICH. It also specifies the
required) power control policy for the maximum cell transmit power.
PdcchPcSwitch: This option specifies whether to enable PDCCH power
control. If this option is deselected, power is evenly allocated on the PDCCH.
If this option is selected, the PDCCH transmit power is dynamically adjusted.
It is recommended that this option be selected.
Power Allocation for the PDSCH Carrying Common Control Information

The following table describes the parameters that must be set in the CellChPwrCfg MO to configure the PDSCH transmit power when the PDSCH carries common control
information.
Local cell ID CellChPwrCfg.LocalCellId Network plan (negotiation not This parameter specifies the local identity of a cell. Set this
required) parameter based on the network plan. Ensure that this parameter
has been set in a Cell MO.
DBCH power CellChPwrCfg.DbchPwr Network plan (negotiation not This parameter specifies the offset of the transmit power for
required) broadcast information on the PDSCH relative to the CRS power.
Set this parameter to the value of the CellDlpcPdschPa.PaPcOff
parameter.
PCH power CellChPwrCfg.PchPwr Network plan (negotiation not This parameter specifies the offset of the transmit power for
required) paging messages on the PDSCH relative to the CRS power.
When the bandwidth is 1.4 MHz, 3 MHz, or 5 MHz, set this
parameter to the value of the CellDlpcPdschPa.PaPcOff
parameter. When the bandwidth is 10 MHz, 15 MHz, or 20 MHz,
set this parameter to a value that is 3 dB greater than the
CellDlpcPdschPa.PaPcOff parameter value.
Rach response CellChPwrCfg.RaRspPwr Network plan (negotiation not This parameter specifies the offset of the transmit power for RAR
power required) messages on the PDSCH relative to the CRS power. When the
bandwidth is 1.4 MHz, 3 MHz, or 5 MHz, set this parameter to the


value of the CellDlpcPdschPa.PaPcOff parameter. When the
bandwidth is 10 MHz, 15 MHz, or 20 MHz, set this parameter to a
value that is 3 dB greater than the CellDlpcPdschPa.PaPcOff
parameter value.
Power Allocation for the PDSCH Carrying UE-Specific Information

The following table describes the parameters that must be set in the CellDlpcPdschPa MO to specify PA.
Local cell ID CellDlpcPdschPa.LocalCellId Network plan (negotiation not This parameter specifies the local
required) identity of a cell. Set this parameter
based on the network plan. Ensure
that this parameter has been set in a
Cell MO.
PA for even power distribution CellDlpcPdschPa.PaPcOff Network plan (negotiation not This parameter specifies the PA value
required) when PA adjustment for PDSCH
transmit power control is disabled, DL
ICIC is disabled, and even power
distribution is used for the PDSCH. It
is recommended that this parameter
be set to DB0_P_A(0 dB) when only
one antenna is used, and be set to
DB_3_P_A(-3 dB) when two or four
antennas are used.
The following table describes the parameters that must be set in the PDSCHCfg MO to specify PB.
Local cell ID PDSCHCfg.LocalCellId Network plan This parameter specifies the local identity of a cell. Set this parameter based on
required)
PB PDSCHCfg.Pb Network plan This parameter is the index of a power factor ratio related to the EPRE on the
(negotiation not PDSCH. This factor index is determined by the value of this parameter and the
required) number of antenna ports. It is recommended that this parameter be set to 0 when
only one antenna is used, and be set to 1 when two or four antennas are used.
Increase in the Maximum Cell Transmit Power

The following table describes the parameters that must be set in the CellAlgoSwitch MO to determine the policy to increase the maximum cell transmit power.
required)
Downlink power control CellAlgoSwitch.DlPcAlgoSwitch Network plan This parameter specifies the options used to enable or disable downlink
algorithm switch (negotiation not power control for the PDSCH, PDCCH, and PHICH. It also specifies the
required) power control policy for the maximum cell transmit power.
EDlMaxTXPwrSwitch: Selecting this option may increase both the maximum
cell transmit power and RB usage. When this option is deselected, the
maximum cell transmit power is calculated based on the CRS power, PA, and
PB. It is recommended that this option be selected for single-mode single-
carrier RRUs, and be deselected for multi-mode or multi-carrier RRUs to avoid
system performance deterioration.
PMCH Transmit Power Allocation

(Optional) The following table describes the parameters that must be set in the CellChPwrCfg MO to specify the PMCH transmit power in a network with eMBMS enabled.
Local cell ID CellChPwrCfg.LocalCellId Network plan (negotiation not This parameter specifies the local identity of a cell. Set this
required) parameter based on the network plan.
Ensure that this parameter has been set in a Cell MO.
PMCH Power CellChPwrCfg.PmchPwrOffset Network plan (negotiation not This parameter specifies the offset of the PMCH transmit power
Offset required) relative to the maximum PDSCH transmit power. For details about
the formula to calculate the maximum PDSCH transmit power, see
3.11.1 Power Calculation.
The following table describes the parameters that must be set in the CellDlpcPdsch MO to specify PA for cell-center users and cell-edge users in macro eNodeBs with downlink
ICIC enabled.
Local cell ID CellDlpcPdsch.LocalCellId Network plan This parameter specifies the local identity of a cell. Set this parameter based on
required)
Center UE PA CellDlpcPdsch.CcuPa Network plan This parameter specifies the PA value of cell center users when DL ICIC is
(negotiation not enabled. When CellDlpcPdschPa.PaPcOff is set to -6 dB, you are advised not
required) to enable ICIC. When CellDlpcPdschPa.PaPcOff is set to -4.77 dB, you are
advised to set this parameter to PA_NEG6(-6dB). When
CellDlpcPdschPa.PaPcOff is set to -3 dB, you are advised to set this parameter
to PA_NEG6(-6dB). When CellDlpcPdschPa.PaPcOff is set to -1.77 dB, you
are advised to set this parameter to PA_NEG4DOT77(-4.77dB). When
CellDlpcPdschPa.PaPcOff is set to 0 dB, you are advised to set this parameter
to PA_NEG3(-3dB). When CellDlpcPdschPa.PaPcOff is set to 1 dB, you are
advised to set this parameter to PA_NEG1DOT77(-1.77dB). When


to PA_0(0dB). When CellDlpcPdschPa.PaPcOff is set to 3 dB, you are advised
not to enable ICIC.
Edge UE PA CellDlpcPdsch.CeuPa Network plan This parameter specifies the PA value of cell edge UEs when DL ICIC is
(negotiation not enabled. When CellDlpcPdschPa.PaPcOff is set to -6 dB, you are advised not to
required) enable ICIC. When CellDlpcPdschPa.PaPcOff is set to -4.77 dB, you are
advised to set this parameter to PA_NEG3(-3dB). When
CellDlpcPdschPa.PaPcOff is set to -3 dB, you are advised to set this parameter
to PA_NEG1DOT77(-1.77dB). When CellDlpcPdschPa.PaPcOff is set to -1.77
dB, you are advised to set this parameter to PA_0(0dB). When
to PA_1(1dB). When CellDlpcPdschPa.PaPcOff is set to 1 dB, you are advised
to set this parameter to PA_2(2dB). When CellDlpcPdschPa.PaPcOff is set to 2
dB, you are advised to set this parameter to PA_3(3dB). When
CellDlpcPdschPa.PaPcOff is set to 3 dB, you are advised not to enable ICIC.
The following table describes parameters that must be set in the PDSCHCfg MO to specify the transmit power offset of each channel relative to the baseline transmit power.
Offset of Ant0 to Tx PDSCHCfg.TxPowerOffsetAnt0 Network plan This parameter specifies the offset of the transmit power of channel 0 relative
Power (negotiation not to the baseline transmit power. The baseline transmit power is determined by
required) the system bandwidth, CRS power, PA, and PB. If the transmit power
configurations should be the same between channels, set this parameter to
255. If the transmit power configurations should be different between channels,
set this parameter to a proper value based on site requirements.


Configuring CRS Power Allocation
Run the MOD PDSCHCFG command to set the CRS power.
(Optional) Configuring RS Power Allocation for a Sector Equipment Group
Run the MOD EUSECTOREQMGROUP command to set the RS power of each RRU that serves a cell.
(Optional) Configuring RS Power Allocation for a Set of Sector Equipment
Run the MOD EUCELLSECTOREQM command to set the RS power of each RRU that serves a cell.
Configuring Power Allocation for Synchronization Signals, PBCH, PCFICH, and PDSCH Carrying Common Information
Run the MOD CELLCHPWRCFG command to set the offsets of the power for synchronization channels, PBCH, PCFICH, and PDSCH carrying common information relative to
the CRS power.
Configuring PHICH Power Allocation
1. Run the MOD CELLDLPCPHICH command to set the offset of the PHICH power relative to the CRS power when the PhichInnerLoopPcSwitch
(PhichInnerLoopPcSwitch) option is deselected.
2. Run the MOD CELLALGOSWITCH command with the PhichInnerLoopPcSwitch(PhichInnerLoopPcSwitch) setting of the Downlink power control algorithm
switch parameter specified.
Configuring Power Allocation for the PDCCH Carrying Dedicated Control Information
1. Run the MOD CELLDLPCPDCCH command to set the offset of the transmit power for dedicated control information on the PDCCH relative to the CRS power when
the PdcchPcSwitch(PdcchPcSwitch) option is deselected.
2. Run the MOD CELLALGOSWITCH command with the PdcchPcSwitch(PdcchPcSwitch) setting of the Downlink power control algorithm switch parameter
specified.
Configuring Power Allocation for the PDSCH Carrying UE-Specific Information
• Scenario 1: in macro eNodeBs with downlink ICIC disabled or in micro eNodeBs
1. Run the MOD PDSCHCFG command to set PB.

2. Run the MOD CELLDLPCPDSCHPA command to set the PDSCH PA when the PDSCH carries UE-specific information.
• Scenario 2: in macro eNodeBs with downlink ICIC enabled
1. Run the MOD PDSCHCFG command to set PB.

2. Run the MOD CELLDLPCPDSCHPA command to set the PDSCH PA when the PDSCH carries UE-specific information.
3. Run the MOD CELLDLPCPDSCH command to set the PDSCH PA for cell-center users and the PDSCH PA for cell-edge users when the PDSCH carries UE-specific
information.
Configuring the Maximum Cell Transmit Power Increase Function

Run the MOD CELLALGOSWITCH command with the EDlMaxTXPwrSwitch(EDlMaxTXPwrSwitch) setting of the Downlink power control algorithm switch parameter
specified.

Setting Antenna RS Power (Applicable Only to Macro eNodeBs)
1. Run the MOD CELLALGOSWITCH command with the AntRsPwrSwitch(AntRsPwrSwitch) setting of the Repeater Switch parameter specified.
2. Run the MOD CELLCHPWRCFG command with the Antenna Output Power parameter set to specify the transmit power for the entire channel bandwidth at the
antenna port.
(Optional) Configuring PMCH Power Allocation

Run the MOD CELLCHPWRCFG command to set the offset of the PMCH transmit power relative to the CRS power.
(Optional) Configuring Power Allocation for RAR Messages
Run the MOD CELLCHPWRCFG command to set the offset of the RAR power relative to the CRS power.
(Optional) Setting Transmit Power for Each Channel
Run the MOD PDSCHCFG command to set the transmit power offsets of channels 0, 1, 2, and 3 relative to the baseline transmit power.

Configuring CRS Power Allocation
MOD PDSCHCFG: LocalCellId=0, ReferenceSignalPwr=182;
(Optional) Configuring RS Power Allocation for a Sector Equipment Group
MOD EUSECTOREQMGROUP: LocalCellId=0, SectorEqmGroupId=0, ReferenceSignalPwr=182;
(Optional) Configuring RS Power Allocation for a Set of Sector Equipment
MOD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0, ReferenceSignalPwr=182;
Configuring Power Allocation for Synchronization Signals, PBCH, PCFICH, and PDSCH Carrying Common Information
MOD CELLCHPWRCFG: LocalCellId=0, PcfichPwr=-600, PbchPwr=-600, SchPwr=0, DbchPwr=-600, PchPwr=0, RaRspPwr=0;
Configuring PHICH Power Allocation
MOD CELLDLPCPHICH: LocalCellId=0, PwrOffset=0;
MOD CELLALGOSWITCH: LocalCellId=0, DlPcAlgoSwitch=PhichInnerLoopPcSwitch-0;
Configuring Power Allocation for the PDCCH Carrying Dedicated Control Information
MOD CELLDLPCPDCCH: LocalCellId=0, DediDciPwrOffset=-30;
MOD CELLALGOSWITCH: LocalCellId=0, DlPcAlgoSwitch=PdcchPcSwitch-1;
Configuring Power Allocation for the PDSCH Carrying UE-Specific Information
• Scenario 1: in macro eNodeBs with downlink ICIC disabled or in micro eNodeBs
MOD PDSCHCFG: LocalCellId=0, Pb=1;

MOD CELLDLPCPDSCHPA: LocalCellId=0, PaPcOff=DB_3_P_A;
• Scenario 2: in macro eNodeBs with downlink ICIC enabled
MOD PDSCHCFG: LocalCellId=0, Pb=1;

MOD CELLDLPCPDSCHPA: LocalCellId=0, PaPcOff=DB_3_P_A;
MOD CELLDLPCPDSCH: LocalCellId=0, CcuPa=PA_NEG6, CeuPa=PA_NEG1DOT77;
Configuring the Maximum Cell Transmit Power Increase Function
MOD CELLALGOSWITCH: LocalCellId=0, DlPcAlgoSwitch=EDlMaxTXPwrSwitch-1;
Setting Antenna RS Power (Applicable Only to Macro eNodeBs)
MOD CELLALGOSWITCH:LocalCellId=0, RepeaterSwitch=AntRsPwrSwitch-1;
MOD CELLCHPWRCFG:LocalCellId=0, AntOutputPwr=20;
(Optional) Configuring PMCH Power Allocation
MOD CELLCHPWRCFG: LocalCellId=0, PmchPwrOffset=255;
(Optional) Configuring Power Allocation for RAR Messages
MOD CellChPwrCfg: LocalCellId=0, HoRarPwrEnhancedSwitch=0, RaRspPwr=0;
(Optional) Setting Transmit Power for Each Channel
MOD PDSCHCFG: LocalCellId=0, TxPowerOffsetAnt0=0, TxPowerOffsetAnt1=0, TxPowerOffsetAnt2=0, TxPowerOffsetAnt3=0;
RS Power Allocation
1. On the U2000 client, choose Monitor > Signaling Trace > Signaling Trace Management.
2. In the navigation tree of the displayed Signaling Trace window, choose Trace Type > LTE > Application Layer > Uu Interface Trace. Double-click Uu Interface
Trace.
3. Set task information in the displayed Uu Interface Trace dialog box and click Finish. The Uu interface signaling tracing task is started.
4. Double-click the new task in the task list on the right of the Signaling Trace Management tab page. The task monitoring tab page is displayed.
5. After parameter settings are changed, find the referenceSignalPower IE in the first RRC_SYS_INFO message traced over the Uu interface. Then, check whether the
value of the referenceSignalPower IE is consistent with the value of PDSCHCfg.ReferenceSignalPwr.
If the values are consistent, the configuration has taken effect; otherwise, the configuration does not take effect.
For example, the value of the referenceSignalPower IE is 18, which means 18 dBm. The value configured for PDSCHCfg.ReferenceSignalPwr is 182, which means
18.2 dBm. The two values are actually the same. The minor margin of error is caused by the precision of IE values defined in 3GPP specifications.
HICH Power Allocation
2. In the navigation tree of the displayed Signaling Trace window, choose Trace Type > LTE > Application Layer > S1 Interface Trace. Double-click S1 Interface
Trace.
3. Set task information in the displayed S1 Interface Trace dialog box and click Finish. The S1 interface signaling tracing task is started.
5. Use a UE to access the cell. Wait until the UE inactivity timer expires and the UE enters RRC_IDLE mode. Then, perform uplink data transmission at 80 Mbit/s using
the UDP mode to enable the UE to enter RRC_CONNECTED mode. Check the values of IEs mMEC and m-TMSI in the S1AP_INITIAL_UE_MSG message traced
over the S1 interface.
6. In the navigation tree of the Signaling Trace window, choose Trace Type > LTE > User Performance Monitoring > DL Power Control Monitoring. Double-click
DL Power Control Monitoring.
7. In the displayed DL Power Control Monitoring dialog box, set MMEc and mTMSI to the decimal values of IEs mMEC and m-TMSI, respectively. Then, click Finish
to start the downlink power control monitoring.
9. Check the real-time value of Power Offset of PHICH (0.01dB).
• When the PhichInnerLoopPcSwitch(PhichInnerLoopPcSwitch) option is deselected, the eNodeB allocates fixed PHICH power. In this situation, the
value of Power Offset of PHICH (0.01dB) is the same as the CellDlpcPhich.PwrOffset parameter value.

• When PhichInnerLoopPcSwitch(PhichInnerLoopPcSwitch) option is selected, the eNodeB dynamically adjusts the PHICH power. In this situation, the
values of Power Offset of PHICH (0.01dB) and CellDlpcPhich.PwrOffset may be different.
wer Allocation for the PDCCH Carrying Dedicated Control Information
Trace.
5. Use a UE to access the cell. Wait until the UE inactivity timer expires and the UE enters RRC_IDLE mode. Then, perform downlink data transmission at 150 Mbit/s
using the UDP mode to enable the UE to enter RRC_CONNECTED mode. Check the values of IEs mMEC and m-TMSI in the S1AP_INITIAL_UE_MSG message
traced over the S1 interface.
to start the downlink power control monitoring.
9. Move the UE to the cell edge and check the real-time value of Power Offset of PDCCH(0.01dB).
• When the PdcchPcSwitch(PdcchPcSwitch) option is selected and the UE is at the cell edge, the eNodeB increases the PDCCH transmit power. If the
value of Power Offset of PDCCH(0.01dB) is different from the CellDlpcPdcch.DediDciPwrOffset parameter value, power allocation for the PDCCH
carrying dedicated control information has taken effect.
• When the PdcchPcSwitch(PdcchPcSwitch) option is deselected, the eNodeB does not adjust the PDCCH transmit power, and Power Offset of
PDCCH(0.01dB) and CellDlpcPdcch.DediDciPwrOffset have the same value.
wer Allocation for the PDSCH Carrying UE-Specific Information
Trace.
5. After parameter settings are changed, find the p-b IE in the first RRC_SYS_INFO message traced over the Uu interface. Then, check whether the value of the p-b IE
is consistent with the value of PDSCHCfg.Pb.
If the values are consistent, the PDSCHCfg.Pb parameter setting has taken effect; otherwise, the parameter setting does not take effect.
Trace.
9. Use a UE to access the cell. Wait until the UE inactivity timer expires and the UE enters RRC_IDLE mode. Then, perform downlink data transmission at 150 Mbit/s
using the UDP mode to enable the UE to enter RRC_CONNECTED mode. Check the values of IEs mMEC and m-TMSI in the S1AP_INITIAL_UE_MSG message
traced over the S1 interface.
to start the UE downlink power control monitoring.
13. Check the real-time value of PDSCH PA (0.01dB).
• When downlink ICIC is disabled, the value of PDSCH PA (0.01dB) is the same as the CellDlpcPdschPa.PaPcOff parameter value.
• When downlink ICIC is enabled, the eNodeB allocates the PDSCH transmit power according to UE attributes. In this situation, the value of PDSCH PA
(0.01dB) is the same as the value of CellDlpcPdsch.CcuPa or CellDlpcPdsch.CeuPa.
Micro eNodeBs do not support downlink ICIC, and therefore the value of PDSCH PA (0.01dB) in micro eNodeBs is the same as that in macro eNodeBs with
downlink ICIC disabled.
aximum Cell Transmit Power Increase
1. On the U2000 client, choose Maintenance > MML Command.

2. In the navigation tree of the displayed MML Command window, select the eNodeB serving the current cell.
3. Run the MML command LST CELLALGOSWITCH and record the value for CellAlgoSwitch.DlPcAlgoSwitch.
4. Run the MML command MOD CELLALGOSWITCH with the EDlMaxTXPwrSwitch(EDlMaxTXPwrSwitch) option deselected to disable the maximum cell transmit
power increase function.
6. In the navigation tree of the Signaling Trace window, choose Trace Type > LTE > Cell Performance Monitoring > Usage of RB Monitoring. Double-click Usage
of RB Monitoring.
7. Set task information in the displayed Usage of RB Monitoring dialog box and click Finish. The cell RB usage trace task is started.
9. Use a UE to access the cell at the position where RSRP equals –100 dBm. Then, perform downlink data transmission at 150 Mbit/s using the UDP mode.
10. Record the real-time value of Downlink Used RB Num. When the EDlMaxTXPwrSwitch(EDlMaxTXPwrSwitch) option is deselected and the offset of the
synchronization signal power relative to the CRS power is greater than PA, the RBs allocated for downlink data transmission in synchronization signal subframes
cannot be fully used.
11. Run the MML command MOD CELLALGOSWITCH with the EDlMaxTXPwrSwitch(EDlMaxTXPwrSwitch) option selected to enable the maximum cell transmit
power increase function.
12. Use the UE to access the cell at the position where RSRP equals -100 dBm. Then, perform downlink data transmission at 150 Mbit/s using the UDP mode.
13. Record the real-time value of Downlink Used RB Num. When the EDlMaxTXPwrSwitch(EDlMaxTXPwrSwitch) option is selected, the eNodeB increases the
maximum cell transmit power if the offset of the synchronization signal power relative to the CRS power is greater than PA and the power limited barred by the
eNodeB is not exceeded. This improves the downlink RB usage in the cell. If the value of Downlink Used RB Num observed in this step is greater than that in 10,
the maximum cell transmit power increase function has taken effect. Otherwise, this function does not take effect.
14. Run the MML command MOD CELLALGOSWITCH to restore settings of CellAlgoSwitch.DlPcAlgoSwitch.
7.4.5 Deactivation


Deactivating Dynamic PHICH Power Adjustment
1. Run the MOD CELLDLPCPHICH command to set the offset of the PHICH power relative to the CRS power when the PhichInnerLoopPcSwitch
(PhichInnerLoopPcSwitch) option is deselected.
2. Run the MOD CELLALGOSWITCH command with the PhichInnerLoopPcSwitch(PhichInnerLoopPcSwitch) option deselected.
Deactivating Power Allocation for the PDCCH Carrying Dedicated Control Information
1. Run the MOD CELLDLPCPDCCH command to set the offset of the transmit power for dedicated control information on the PDCCH relative to the CRS power when
the PdcchPcSwitch(PdcchPcSwitch) option is deselected.
2. Run the MOD CELLALGOSWITCH command with the PdcchPcSwitch(PdcchPcSwitch) option deselected.
Deactivating the Maximum Cell Transmit Power Increase Function

Run the MOD CELLALGOSWITCH command with the EDlMaxTXPwrSwitch(EDlMaxTXPwrSwitch) option deselected.
Network services will be interrupted if the EDlMaxTXPwrSwitch(EDlMaxTXPwrSwitch) option setting is changed during network operation.
Deactivating Antenna RS Power Setting (Applicable only to Macro eNodeBs)
Run the MOD CELLALGOSWITCH command with the AntRsPwrSwitch(AntRsPwrSwitch) option deselected.
Deactivating the Transmit Power for Each Channel
Run the MOD PDSCHCFG command with parameters Offset of Ant0 to Tx Power, Offset of Ant1 to Tx Power, Offset of Ant2 to Tx Power, and Offset of Ant3 to Tx
Power set to 255 to disable the function of unbalanced transmit power configurations between channels.

Deactivating Dynamic PHICH Power Adjustment
MOD CELLDLPCPHICH:LOCALCELLID=0,PWROFFSET=0;
MOD CELLALGOSWITCH:LOCALCELLID=0,DLPCALGOSWITCH=PhichInnerLoopPcSwitch-0;
Deactivating Power Allocation for the PDCCH Carrying Dedicated Control Information
MOD CELLDLPCPDCCH:LOCALCELLID=0,DEDIDCIPWROFFSET=-30;
MOD CELLALGOSWITCH:LOCALCELLID=1,DLPCALGOSWITCH=PdcchPcSwitch-0;
Deactivating the Maximum Cell Transmit Power Increase Function
MOD CELLALGOSWITCH:LOCALCELLID=0,DLPCALGOSWITCH=EDlMaxTXPwrSwitch-0;
Deactivating Antenna RS Power Setting (Applicable only to Macro eNodeBs)
MOD CELLALGOSWITCH:LocalCellId=0, RepeaterSwitch=AntRsPwrSwitch-0;
(Optional) Deactivating Transmit Power Setting for Each Channel
MOD PDSCHCFG: LocalCellId=0, TxPowerOffsetAnt0=255, TxPowerOffsetAnt1=255, TxPowerOffsetAnt2=255, TxPowerOffsetAnt3=255;
Deployment of Uplink Power Control

This section describes the deployment of the following features:

7.5.1 Requirements
Uplink power control has no requirements on the operating environment, transmission networking, or licenses.
The LBBPc does not support LBFD-081101 PUCCH Outer Loop Power Control.
NOTE:
LampSite eNodeBs do not support the LBBPc.

PRACH Transmit Power Settings
The following table describes the parameters that must be set in the RACHCfg MO to configure PRACH power control.

Name
Local cell ID RACHCfg.LocalCellId Network This parameter specifies the local identity of a cell. Set this parameter based on the network plan.
plan Ensure that this parameter has been set in a Cell MO.
(negotiation
not
required)
Power RACHCfg.PwrRampingStep Network This parameter specifies the preamble power ramping step. The value
ramping plan DB2_PWR_RAMPING_STEP(2dB) is recommended.
step (negotiation
not
required)
Preamble RACHCfg.PreambInitRcvTargetPwr Network This parameter specifies the target PRACH transmit power expected by the eNodeB when
initial plan PRACH preamble format 0 is applied on condition that requirements for preamble detection
received (negotiation performance are met. The value DBM_104(-104dBm) is recommended.
target power not
required)
PUSCH Transmit Power Settings

The following table describes the parameters that must be set in the CellUlpcComm MO to configure PUSCH power control.

Name
Local cell ID CellUlpcComm.LocalCellId Network plan This parameter specifies the local identity of a cell. Set this parameter based on the
required)
Path loss CellUlpcComm.PassLossCoeff Network plan This parameter specifies the compensation factor for path loss. The value AL07(0.7) is
coefficient (negotiation not recommended.
required)


Name
P0 nominal CellUlpcComm.P0NominalPUSCH Network plan This parameter specifies the target PUSCH transmit power expected by the eNodeB
PUSCH (negotiation not when requirements on normal PUSCH demodulation are met. The value -67 is
required) recommended.
The following table describes the parameters that must be set in the CellUlpcDedic MO to specify the RRC-dedicated parameters for PUSCH power control.
Local cell ID CellUlpcDedic.LocalCellId Network plan This parameter specifies the local identity of a cell. Set this parameter based on
(negotiation the network plan. Ensure that this parameter has been set in a Cell MO.
not required)
Delta-MCS enable or CellUlpcDedic.DeltaMcsEnabled Network plan This parameter specifies whether a UE needs to adjust the transmit power based
disable indication (negotiation on the difference between MCSs. The value UU_DISABLE(Disable) is
not required) recommended.
RSRP filtering coefficient CellUlpcDedic.FilterRsrp Network plan This parameter specifies the alpha filtering coefficient used by the UE to filter
(negotiation RSRP measurement values during path loss estimation. The value
not required) UU_FC6_FILTER_COEFF(UU_FC6_FILTER_COEFF) is recommended.
The following table describes the parameters that must be set in the CellAlgoSwitch MO to configure power control for the PUSCH and PUCCH.

Name
Local cell CellAlgoSwitch.LocalCellId Network This parameter specifies the local identity of a cell. Set this parameter based on the network plan.
ID plan Ensure that this parameter has been set in a Cell MO.
(negotiation
not
required)
Uplink CellAlgoSwitch.UlPcAlgoSwitch Network This parameter specifies the options used to enable or disable uplink power control, especially
power plan power control policies for the PUSCH and PUCCH.
control (negotiation CloseLoopSpsSwitch: If this option is deselected, closed-loop power control does not apply to the
algorithm not PUSCH with semi-persistent scheduling enabled. If this option is selected, the eNodeB adjusts TPC
switch required) commands based on whether the received initial-transmission data packets are correct, ensuring
that the IBLER approaches the target value. It is recommended that this option be deselected.
InnerLoopPuschSwitch: Inner-loop power control applies to the PUSCH with dynamic scheduling
enabled only when this option is selected. It is recommended that this option be selected.
PuschIoTCtrlSwitch: Interference control is enabled in closed-loop power control for the PUSCH
with dynamic scheduling applied only when this option is selected. It is recommended that this
option be deselected.
NearPointUeOptPUSCHSwitch: If this option is deselected, the measured SINR works as the SINR
evaluation value. If this option is selected, the smaller value between the measured SINR and the
SINR after adjustment works as the SINR evaluation value. It is recommended that this option be
deselected.
PuschRsrpHighThdSwitch: If this option is deselected, PUSCH closed-loop power control does
not limit the RSRP of the PUSCH. If this option is selected, PUSCH closed-loop power control
requires that the RSRP should not exceed an upper limit. It is recommended that this option be
deselected.
PucchInitialPcSwitch: The PUCCH transmit power of initially accessed UEs can rapidly approach
the target value only when this option is selected, thereby decreasing PUCCH interference between
neighboring cells. It is recommended that this option be selected.
PUCCH Transmit Power Settings

The following table describes the parameters that must be set in the CellUlpcComm MO to configure PUCCH power control.
Local cell ID CellUlpcComm.LocalCellId Network plan This parameter specifies the local identity of a cell. Set this parameter based on
required)
P0 nominal CellUlpcComm.P0NominalPUCCH Network plan This parameter specifies the target PUCCH transmit power expected by the
PUCCH (negotiation not eNodeB for normal PUCCH demodulation. The value -115 is recommended.
required)
DeltaF for CellUlpcComm.DeltaFPUCCHFormat1 Network plan This parameter specifies the delta value corresponding to PUCCH format 1. The
PUCCH format 1 (negotiation not value DELTAF0(0dB) is recommended.
required)
DeltaF for CellUlpcComm.DeltaFPUCCHFormat1b Network plan This parameter specifies the delta value corresponding to PUCCH format 1b. The
PUCCH format (negotiation not value DELTAF3(3dB) is recommended.
1b required)
DeltaF for CellUlpcComm.DeltaFPUCCHFormat2 Network plan This parameter specifies the delta value corresponding to PUCCH format 2. The
PUCCH format 2 (negotiation not value DELTAF1(1dB) is recommended.
required)
DeltaF for CellUlpcComm.DeltaFPUCCHFormat2a Network plan This parameter specifies the delta value corresponding to PUCCH format 2a. The
2a required)
DeltaF for CellUlpcComm.DeltaFPUCCHFormat2b Network plan This parameter specifies the delta value corresponding to PUCCH format 2b. The
2b required)
The following table describes the parameters that must be set in the CellAlgoSwitch MO to configure power control for the PUSCH and PUCCH.
Local cell ID CellAlgoSwitch.LocalCellId This parameter specifies the local identity of a cell. Set this parameter based on the
network plan. Ensure that this parameter has been set in a Cell MO.


Network plan
(negotiation not
required)
Uplink power CellAlgoSwitch.UlPcAlgoSwitch Network plan This parameter specifies the options used to enable or disable uplink power control,
control (negotiation not especially power control policies for the PUSCH and PUCCH.
algorithm required) InnerLoopPucchSwitch: Inner-loop power control applies to the PUCCH only when this
switch option is selected. It is recommended that this option be selected.
PucchPcDtxSinrSwitch: If this option is deselected, the eNodeB does not process the
measured SINR of PUCCH signals in DTX. If both this option and
InnerLoopPucchSwitch are selected, the eNodeB processes the measured SINR of
PUCCH signals in DTX, generates TPC commands based on the SINR, and sends the
commands to UEs. It is recommended that this option be selected.
OuterLoopPucchSwitch: Outer-loop power control applies to the PUCCH only when
this option is selected. It is recommended that this option be selected.
PucchInitialPcSwitch: The PUCCH transmit power of initially accessed UEs can rapidly
approach the target value only when this option is selected, thereby decreasing PUCCH
interference between neighboring cells. It is recommended that this option be selected.
The following table describes the parameters must be set in the CellPcAlgo MO to configure PUCCH closed-loop power control.
Local cell ID CellPcAlgo.LocalCellId Network plan This parameter specifies the local identity of a cell. Set this parameter based
required)
PUCCH Close Loop CellPcAlgo.PucchCloseLoopPcType Network plan This parameter specifies whether the P0NominalPUCCH parameter setting
Power Control Type (negotiation not affects PUCCH closed-loop power control.
required) If this parameter is set to NOT_USE_P0NOMINALPUCCH(Not Use
P0NominalPUCCH), the P0NominalPUCCH parameter setting does not affect
PUCCH closed-loop power control. If this parameter is set to
USE_P0NOMINALPUCCH(Use P0NominalPUCCH), the RSRP cannot
exceed the P0NominalPUCCH parameter value in PUCCH closed-loop power
control. The parameter value NOT_USE_P0NOMINALPUCCH(Not Use
P0NominalPUCCH) is recommended.
Pucch Power CellPcAlgo.PucchPcperiod Network plan This parameter specifies the period of PUCCH power control. The parameter
Control Period (negotiation not value 1 (equals the actual value 20 ms) is recommended.
required)
Pucch Power CellPcAlgo.PucchPcTargetSinrOffset Network plan This parameter specifies the offset of the final target SINR to the predefined
Control Target Sinr (negotiation not target SINR in PUCCH power control. The parameter value 0 is
Offset required) recommended.
SRS Transmit Power Settings

The following table describes the parameters that must be set in the CellUlpcDedic MO to specify the offset of the SRS transmit power relative to the PUSCH transmit power.
Local cell ID CellUlpcDedic.LocalCellId Network plan This parameter specifies the local identity of a cell. Set this
(negotiation not parameter based on the network plan. Ensure that this parameter
required) has been set in a Cell MO.
Power Offset of SRS CellUlpcDedic.PSrsOffsetDeltaMcsDisable Network plan This parameter specifies the offset of the SRS transmit power
When DeltaMcsEnabled (negotiation not relative to the PUSCH transmit power when the
Off required) CellUlpcDedic.DeltaMcsEnabled parameter is set to UU_DISABLE
(Disable). The parameter value -30 (corresponding to -3 dB) is
recommended.
Power Offset of SRS CellUlpcDedic.PSrsOffsetDeltaMcsEnable Network plan This parameter specifies the offset of the SRS transmit power
When DeltaMcsEnabled (negotiation not relative to the PUSCH transmit power when the
On required) CellUlpcDedic.DeltaMcsEnabled parameter is set to UU_ENABLE
(Enable). The parameter value -30 (corresponding to -3 dB) is
recommended.


Configuring PRACH Power Control
Run the MOD RACHCFG command to set the expected initial preamble receive target power and power ramping step.
Configuring PUSCH Power Control
1. Run the MOD CELLULPCCOMM command to set the expected PSD on the PUSCH and path loss compensation factor for the eNodeB.
2. Run the MOD CELLULPCDEDIC command to set the DeltaMcsEnabled switch for the PUSCH and the RSRP alpha filtering coefficient.
3. Run the MOD CELLALGOSWITCH command to set InnerLoopPuschSwitch, CloseLoopSpsSwitch, PuschIoTCtrlSwitch, NearPointUeOptPUSCHSwitch, and
PuschRsrpHighThdSwitch for the PUSCH.
4. (Optional) Run the MOD CELLPCALGO command to set the offset of the PUSCH high-SINR threshold of UEs running voice services relative to the PUSCH high-
SINR threshold of UEs running data services.
Configuring PUCCH Power Control
1. Run the MOD CELLULPCCOMM command to set the expected PSD on the PUCCH and the power offset for power of the PUCCH in format 1, 1b, 2, 2a, or 2b
relative to the power of the PUCCH in format 1a.
2. Run the MOD CELLALGOSWITCH command to set InnerLoopPucchSwitch, OuterLoopPucchSwitch, PucchPcDtxSinrSwitch, and PucchInitialPcSwitch.
3. Run the MOD CELLPCALGO command to enable PUCCH power control enhancement.
Configuring SRS Power Control

Run the MOD CELLULPCDEDIC command to set the offset of the SRS power relative to the PUSCH power.

Configuring PRACH Power Control

MOD RACHCFG: LOCALCELLID=0, PWRRAMPINGSTEP=DB2_PWR_RAMPING_STEP, PREAMBINITRCVTARGETPWR=DBM_104;
Configuring PUSCH Power Control
MOD CELLULPCCOMM: LOCALCELLID=0, PASSLOSSCOEFF=AL07, P0NOMINALPUSCH=-67;
MOD CELLULPCDEDIC: LOCALCELLID=0, DELTAMCSENABLED=UU_DISABLE, FILTERRSRP=UU_FC6_FILTER_COEFF;
MOD CELLALGOSWITCH: LOCALCELLID=0, ULPCALGOSWITCH=CloseLoopSpsSwitch-0&InnerLoopPuschSwitch-1&PuschIoTCtrlSwitch-0&NearPointUeOp
tPUSCHSwitch-0&PuschRsrpHighThdSwitch-0;
MOD CELLPCALGO: LocalCellId=0, VOLTESINRHIGHTHDOFFSET=-30, PuschRsrpHighThd=-82;
Configuring PUCCH Power Control
MOD CELLULPCCOMM: LOCALCELLID=0, P0NOMINALPUCCH=-115, DELTAFPUCCHFORMAT1=DELTAF0, DELTAFPUCCHFORMAT1B=DELTAF3, DELTAFPUCCHFORMAT
2=DELTAF1, DELTAFPUCCHFORMAT2A=DELTAF2, DELTAFPUCCHFORMAT2B=DELTAF2;
MOD CELLALGOSWITCH: LOCALCELLID=0, ULPCALGOSWITCH=InnerLoopPucchSwitch-1&PucchPcDtxSinrSwitch-1&OuterLoopPucchSwitch-1&PucchInit
ialPcSwitch-1;
MOD CELLPCALGO: LOCALCELLID=0, PUCCHCLOSELOOPPCTYPE=NOT_USE_P0NOMINALPUCCH, PUCCHPCPERIOD=1, PUCCHPCTARGETSINROFFSET=0;
Configuring SRS Power Control
MOD CELLULPCDEDIC: LOCALCELLID=0, PSRSOFFSETDELTAMCSDISABLE=-30, PSRSOFFSETDELTAMCSENABLE=-30;
RACH Power Control
Trace.
5. After parameter settings are changed, find IEs powerRampingStep and preambleInitialReceivedTargetPower in the first RRC_SYS_INFO message traced over the
Uu interface. Then, check whether the values of the two IEs are consistent with the values of parameters RACHCfg.PwrRampingStep and
RACHCfg.PreambInitRcvTargetPwr, respectively.
If the values are consistent, the PRACH transmit power settings have taken effect; otherwise, PRACH transmit power settings do not take effect.
USCH Power Control
Trace.
5. After parameter settings are changed, find IEs p0-NominalPUSCH and alpha in the first RRC_SYS_INFO message traced over the Uu interface. Then, check
whether the values of the IEs are consistent with the values of parameters CellUlpcComm.P0NominalPUSCH and CellUlpcComm.PassLossCoeff, respectively.
If the values are consistent, the settings have taken effect; otherwise, the settings do not take effect.
6. Use a UE to access the cell, and find IEs deltaMCS-Enabled and filterCoefficient in the first RRC_CONN_SETUP message traced over the Uu interface. Then,
check whether the values of the IEs are consistent with the values of parameters CellUlpcDedic.DeltaMcsEnabled and CellUlpcDedic.FilterRsrp, respectively.
8. In the navigation tree of the displayed MML Command window, select the eNodeB serving the current cell.
9. Run the LST CELLALGOSWITCH command and record option settings of the CellAlgoSwitch.UlPcAlgoSwitch parameter.
10. Run the MOD CELLALGOSWITCH command with the InnerLoopPuschSwitch(InnerLoopPuschSwitch) option deselected.
11. Use the UE to access the cell at a place near the cell center. Then, perform uplink data transmission at 80 Mbit/s using the UDP mode.
12. In the navigation tree of the Signaling Trace window, choose Trace Type > LTE > Cell Performance Monitoring > Usage of RB Monitoring. Double-click Usage
of RB Monitoring.
13. Set task information in the displayed Usage of RB Monitoring dialog box and click Finish. The cell RB usage trace task is started.
15. Check the real-time value of Uplink Equivalent Used RB Num. When the UE is near the position where the RSRP equals –75 dBm, the value of Uplink
Equivalent Used RB Num approximates 1000 times the uplink cell bandwidth. Move the UE from a place near the cell center to a place at middle distance from the
cell center until the value of Uplink Equivalent Used RB Num becomes about 500 times the uplink cell bandwidth. Then, record this value.
16. Run the MOD CELLALGOSWITCH command with the InnerLoopPuschSwitch(InnerLoopPuschSwitch) option be selected to enable PUSCH inner-loop power
control with dynamic scheduling applied.
17. Use the UE to access the cell at the position described in 15. Then, perform uplink data transmission at 80 Mbit/s using the UDP mode.
18. Check the real-time value of Uplink Equivalent Used RB Num.
When the InnerLoopPuschSwitch(InnerLoopPuschSwitch) option is selected, the number of uplink PUSCH RBs decreases slowly as the UE moves away from
the cell center. If the value of Uplink Equivalent Used RB Num is greater than the value recorded in 15, PUSCH inner-loop power control with dynamic scheduling
applied has taken effect.
19. Run the MOD CELLALGOSWITCH command with option settings of the CellAlgoSwitch.UlPcAlgoSwitch parameter restored.
T-based PUSCH Power Control
2. In the navigation tree of the displayed Signaling Trace window, choose Trace Type > LTE > Application Layer > X2 Interface Trace. Double-click X2 Interface
Trace.
3. Set task information in the displayed X2 Interface Trace dialog box and click Finish. The S1 interface signaling tracing task is started.
4. Double-click the new task in the task list on the right of the Signaling Trace Management tab page.
5. Check whether the LOAD_INFORMATION message is displayed in X2 interface tracing results.
6. Consider that the cell is heavily loaded. If the PuschIoTCtrlSwitch(PuschIoTCtrlSwitch) option is selected, the LOAD_INFORMATION message exists in the X2
interface tracing result. If this option is deselected, the LOAD_INFORMATION message does not exist in the X2 interface tracing result.
UCCH Power Control
Trace.
5. After parameter settings are changed, find the values of the following IEs in the first RRC_SYS_INFO message traced over the Uu interface:

• p0-NominalPUCCH
• deltaF-PUCCH-Format1
• deltaF-PUCCH-Format1b
• deltaF-PUCCH-Format2
• deltaF-PUCCH-Format2a
• deltaF-PUCCH-Format2b
Check whether the values of these IEs are consistent with the values of the following parameters, respectively:
• CellUlpcComm.P0NominalPUCCH
• CellUlpcComm.DeltaFPUCCHFormat1
• CellUlpcComm.DeltaFPUCCHFormat1b
• CellUlpcComm.DeltaFPUCCHFormat2
• CellUlpcComm.DeltaFPUCCHFormat2a
• CellUlpcComm.DeltaFPUCCHFormat2b
Trace.
9. Use a UE to access the cell near the cell center. Wait until the UE inactivity timer expires and the UE enters RRC_IDLE mode. Then, perform downlink data
transmission at 150 Mbit/s using the UDP mode to enable the UE to enter RRC_CONNECTED mode. Check the values of IEs mMEC and m-TMSI in the
S1AP_INITIAL_UE_MSG message traced over the S1 interface.
10. In the navigation tree of the Signaling Trace window, choose Trace Type > LTE > User Performance Monitoring > UL Power Control Monitoring. Double-click
UL Power Control Monitoring.
11. In the displayed UL Power Control Monitoring dialog box, set MMEc and mTMSI to the decimal values of IEs mMEC and m-TMSI, respectively. Then, click Finish
to start the uplink power control monitoring.
13. Check the real-time value of PUCCH SINR (0.01dB).
When the InnerLoopPucchSwitch(InnerLoopPucchSwitch) option is selected, the eNodeB periodically adjusts the PUCCH transmit power. When the UE is near
the cell center, the value of PUCCH SINR (0.01dB) fluctuates around the pre-configured target value (about 16 dB). When this option is deselected and the UE is
near the cell center, the value of PUCCH SINR (0.01dB) fluctuates around a relatively larger value than the pre-configured target value.
uter-Loop PUCCH Power Control
Trace.
5. Use a UE to access the cell near the cell center. Wait until the UE inactivity timer expires and the UE enters RRC_IDLE mode. Then, perform downlink data
transmission at 150 Mbit/s using the UDP mode to enable the UE to enter RRC_CONNECTED mode. Check the values of IEs mMEC and m-TMSI in the
S1AP_INITIAL_UE_MSG message traced over the S1 interface.
6. In the navigation tree of the Signaling Trace window, choose Trace Type > LTE > User Performance Monitoring > UL Power Control Monitoring. Double-click
UL Power Control Monitoring.
7. In the displayed UL Power Control Monitoring dialog box, set MMEc and mTMSI to the decimal values of IEs mMEC and m-TMSI, respectively. Then, click Finish
to start the uplink power control monitoring.
9. Check the real-time value of PUCCH SINR (0.01dB).
Note that you must select the InnerLoopPucchSwitch(InnerLoopPucchSwitch) option before selecting the OuterLoopPucchSwitch(OuterLoopPucchSwitch)
option.
If the OuterLoopPucchSwitch(OuterLoopPucchSwitch) option is selected in a network with poor channel conditions for PUCCH in format 2, 2a, or 2b, the
eNodeB periodically adjusts the target SINR for PUCCH inner-loop power control, and the value of PUCCH SINR (0.01dB) is greater than the pre-configured target
value (about 16 dB). If this option is deselected in the preceding scenario, the target SINR for PUCCH inner-loop power control retains unchanged, and the value of
PUCCH SINR (0.01dB) fluctuates around the pre-configured target value.
RS Power Control
Trace.
5. Use a UE to access the cell and find IEs deltaMCS-Enabled and pSRS-Offset in the RRC_CONN_SETUP message traced over the Uu interface.
• If the deltaMCS-Enabled IE value is en0, check whether the actual value of the pSRS-Offset IE is the same as the actual value of the
CellUlpcDedic.PSrsOffsetDeltaMcsDisable parameter. If the actual values are the same, SRS power control has taken effect; otherwise, SRS power
control does not take effect.
For example, when the deltaMCS-Enabled IE value is en0:
The pSRS-Offset IE value is 5, equaling the actual value –3 dB, which can be calculated by –10.5 plus the value of 1.5 multiplied by 5 in the unit of dB.
The CellUlpcDedic.PSrsOffsetDeltaMcsDisable parameter value is –30, equaling the actual value –3 dB. The actual values are the same and SRS power
control has taken effect.
• If the deltaMCS-Enabled IE value is en1, check whether the actual value of the pSRS-Offset IE is the same as the actual value of the
CellUlpcDedic.PSrsOffsetDeltaMcsEnable parameter. If the actual values are the same, SRS power control has taken effect; otherwise, SRS power
control does not take effect.
For example, when the deltaMCS-Enabled IE value is en1:
The pSRS-Offset IE value is 0, equaling the actual value –3 dB, which can be calculated by 0 minus 3 in the unit of dB. The
CellUlpcDedic.PSrsOffsetDeltaMcsEnable parameter value is –30, equaling the actual value –3 dB. The actual values are the same and SRS power
control has taken effect.
NOTE:
For details about the conversion from the displayed value to the actual value of the pSRS-Offset IE, see section 6.3.2 "Radio resource control information elements"
in 3GPP TS 36.331 V9.8.0.
7.5.4 Deactivation



Deactivating PUSCH Inner-Loop Power Control with Dynamic Scheduling Applied
Run the MOD CELLALGOSWITCH command with the InnerLoopPuschSwitch(InnerLoopPuschSwitch) option deselected.
Deactivating IoT-based PUSCH Power Control
Run the MOD CELLALGOSWITCH command with the PuschIoTCtrlSwitch(PuschIoTCtrlSwitch) option deselected.
Deactivating PUSCH Closed-loop Power Control with Semi-Persistent Scheduling Applied
Run the MOD CELLALGOSWITCH command with the CloseLoopSpsSwitch(CloseLoopSpsSwitch) option deselected.
Deactivating PUSCH Closed-Loop Power Control Optimization on UEs Near the Cell Center
Run the MOD CELLALGOSWITCH command with the NearPointUeOptPUSCHSwitch(NearPointUeOptPUSCHSwitch) option deselected.
Deactivating the Use of the RSRP Upper Limit in PUSCH Closed-Loop Power Control
Run the MOD CELLALGOSWITCH command with the PuschRsrpHighThdSwitch(PuschRsrpHighThdSwitch) option deselected.
Deactivating PUCCH Inner-Loop Power Control and SINR Optimization for PUCCH Signals in DTX
Run the MOD CELLALGOSWITCH command with options InnerLoopPucchSwitch(InnerLoopPucchSwitch) and PucchPcDtxSinrSwitch(PucchPcDtxSinrSwitch)
deselected.
Deactivating PUCCH Outer-Loop Power Control
Run the MOD CELLALGOSWITCH command with the OuterLoopPucchSwitch(OuterLoopPucchSwitch) option deselected.
Deactivating Initial Fast PUCCH Power Control
Run the MOD CELLALGOSWITCH command with the PucchInitialPcSwitch(PucchInitialPcSwitch) option deselected.

Deactivating PUSCH Inner-Loop Power Control with Dynamic Scheduling Applied
MOD CELLALGOSWITCH:LOCALCELLID=0,ULPCALGOSWITCH=InnerLoopPuschSwitch-0;
Deactivating IoT-based PUSCH Power Control
MOD CELLALGOSWITCH:LOCALCELLID=0,ULPCALGOSWITCH=PuschIoTCtrlSwitch-0;
Deactivating PUSCH Closed-Loop Power Control with Semi-Persistent Scheduling Applied
MOD CELLALGOSWITCH:LOCALCELLID=0,ULPCALGOSWITCH=CloseLoopSpsSwitch-0;
Deactivating PUSCH Closed-Loop Power Control Optimization on UEs Near the Cell Center
MOD CELLALGOSWITCH:LOCALCELLID=0,ULPCALGOSWITCH=NearPointUeOptPUSCHSwitch-0;
Deactivating the Use of the RSRP Upper Limit in PUSCH Closed-Loop Power Control
MOD CELLALGOSWITCH:LOCALCELLID=0,ULPCALGOSWITCH=PuschRsrpHighThdSwitch-0;
Deactivating PUCCH Inner-Loop Power Control and SINR Optimization for PUCCH Signals in DTX
MOD CELLALGOSWITCH:LOCALCELLID=0,ULPCALGOSWITCH=InnerLoopPucchSwitch-0&PucchPcDtxSinrSwitch-0;
Deactivating PUCCH Outer-Loop Power Control
MOD CELLALGOSWITCH: LocalCellId=0, UlPcAlgoSwitch= OuterLoopPucchSwitch-0;
Deactivating Initial Fast PUCCH Power Control
MOD CELLALGOSWITCH: LocalCellId=0, UlPcAlgoSwitch= PucchInitialPcSwitch-0;
onitoring Power Control for the PDCCH Carrying Dedicated Control Information
To check whether power control for the PDCCH carrying dedicated control information takes effect in a cell, perform the following steps on the U2000 client:

3. Set task information in the displayed DL Power Control Monitoring dialog box. Set MMEc and mTMSI to the decimal values of IEs mMEC and m-TMSI,
respectively. Click Finish. The DL power control monitoring task is started.
4. Double-click the new DL power control monitoring task in the task list on the right of the Signaling Trace window. A tab page is displayed for you to monitor DL
power control.
5. Check the values in the Power Offset of PDCCH(0.01dB) column. Check the values in the Power Offset of PDCCH(0.01dB) column. If the value is always –300
for UEs at the cell edge, power control for the PDCCH carrying dedicated control information does not take effect. Otherwise, this power control function takes
effect.
If a cell meets related requirements for this function to take effect, monitor counters and collect network KPIs of the cell, such as the access success rate, service
drop rate, and handover success rate. Compare the weekly KPIs before and after this function is enabled and evaluate the gain that this function has offered. If the
KPIs improve after this function is enabled, the power control gain is obvious.
onitoring PUSCH Inner-Loop Power Control with Dynamic Scheduling Applied
Check the Cell Uplink Average Throughput KPI. Compare the weekly Cell Uplink Average Throughput before and after the function of PUSCH inner-loop power control with
dynamic scheduling applied is enabled and evaluate the gain of this function. If Cell Uplink Average Throughput increases after this function is enabled, the power control gain is
obvious.
The performance of this function is affected by certain factors such as UE distribution and uplink interference. The gain depends on network conditions and cannot be quantized.
Cell Uplink Average Throughput can be calculated by using the following formula:
Cell Uplink Average Throughput = L.Thrp.bits.UL / L.Thrp.Time.Cell.UL.HighPrecision
onitoring IoT-based PUSCH Power Control
After this feature is activated, you can monitor the counters described in this section to evaluate feature performance.
Check the Cell Uplink Average Throughput KPI to collect the statistics of uplink cell throughput. Compare the weekly Cell Uplink Average Throughput before and after the IoT-
based PUSCH Power Control feature is enabled and evaluate the gain of this feature. The feature performance is affected by certain factors such as UE distribution and uplink
interference. The gain depends on network conditions and cannot be quantized.
Cell Uplink Average Throughput can be calculated by using the following formula:
Cell Uplink Average Throughput = L.Thrp.bits.UL / L.Thrp.Time.Cell.UL.HighPrecision
Check the values of counters L.UL.RSRP.PUSCH.Index0 to L.UL.RSRP.PUSCH.Index23 in a neighboring cell to determine whether the RSRP on the PUSCH of the neighboring cell
decreases.
Check the values of counters L.UL.Interference.PUSCH.Index0 to L.UL.Interference.PUSCH.Index15 in the local cell to determine whether the interference on the PUSCH of the
local cell decreases.
onitoring PUCCH Outer-Loop Power Control

Check KPIs User Downlink Average Throughput and Cell Downlink Average Throughput to collect the statistics of downlink throughput. Compare the weekly downlink
throughput before and after PUCCH outer-loop power control is enabled and evaluate the gain of this feature. If User Downlink Average Throughput and Cell Downlink Average
Throughput increase after this feature is enabled, the power control gain is obvious.
User Downlink Average Throughput and Cell Downlink Average Throughput can be calculated by using the following formulas, respectively:
• User Downlink Average Throughput = (L.Thrp.bits.DL – L.Thrp.bits.DL.LastTTI) / L.Thrp.Time.DL.RmvLastTTI

• Cell Downlink Average Throughput = L.Thrp.bits.DL / L.Thrp.Time.Cell.DL.HighPrecision
NOTE:
The gain of PUCCH outer-loop power control is affected by the following factors:
• Value of CellUlpcComm.P0NominalPUCCH
A larger value indicates greater gains.
• DRX and dynamic DRX features
Disabling DRX and dynamic DRX brings greater gains.
• Value of CellPcAlgo.PucchPcTargetSinrOffset
A larger value indicates smaller gains.
• Value of CellCqiAdaptiveCfg.SimulAckNackAndCqiSwitch
Setting this parameter to ON(On) brings great gains.
onitoring Initial Fast PUCCH Power Control
Check KPIs User Downlink Average Throughput and Cell Downlink Average Throughput to collect the statistics of downlink throughput. Compare the weekly downlink
throughput before and after the feature is enabled and evaluate the gain of initial fast PUCCH power control. If User Downlink Average Throughput and Cell Downlink Average
Throughput increase after the PucchInitialPcSwitch(PucchInitialPcSwitch) option is selected, initial fast PUCCH power control brings significant gains.
User Downlink Average Throughput and Cell Downlink Average Throughput can be calculated by using the following formulas, respectively:
• User Downlink Average Throughput = (L.Thrp.bits.DL – L.Thrp.bits.DL.LastTTI) / L.Thrp.Time.DL.RmvLastTTI

• Cell Downlink Average Throughput = L.Thrp.bits.DL / L.Thrp.Time.Cell.DL.HighPrecision
onitoring RAR Transmit Power Increase for UEs Involved in Handovers
Consider that the CellChPwrCfg. HoRarPwrEnhancedSwitch parameter is set to ON(ON). If the values of KPIs Dedicate RACH Successful Rate and Intra-Frequency Handover
Out Success Rate increase, the RAR power increase function for UEs involved in handovers brings obvious gains.
Dedicate RACH Successful Rate and Intra-Frequency Handover Out Success Rate can be calculated by using the following formulas, respectively:
• Dedicate RACH Successful Rate = L.RA.Dedicate.HO.Msg3Rcv / L.RA.Dedicate.HO.Att

• Intra-Frequency Handover Out Success Rate =(L.HHO.IntraeNB.IntraFreq.ExecSuccOut + L.HHO.IntereNB.IntraFreq.ExecSuccOut) /
(L.HHO.IntraeNB.IntraFreq.ExecAttOut + L.HHO.IntereNB.IntraFreq.ExecAttOut) x 100%
onitoring Unbalanced Transmit Power Configurations Between Channels
The function of unbalanced transmit power configurations between channels produces significant gains if cell downlink throughput and downlink user-perceived throughput
increase on the condition that the following parameters are set to values other than 255:
When the uplink band edges experience severe interference, enable PUCCH flexible configuration to reduce or eliminate the impact of the interference source on the PUCCH.
For details about PUCCH flexible configuration, see Physical Channel Resource Management Feature Parameter Description.
Possible Issues
wer Control for the PDCCH Carrying Dedicated Control Information
If network KPIs of a cell deteriorate after this function is enabled, check the number of DTXs in the cell to determine whether the PDCCH demodulation performance degrades.
Perform the following steps on the U2000 client:

2. In the navigation tree of the Signaling Trace window, choose Trace Type > LTE > Cell Performance Monitoring > HARQ Statistic Monitoring. Double-click
HARQ Statistic Monitoring.
3. Set task information in the displayed HARQ Statistic Monitoring dialog box and click Finish. The HARQ statistics monitoring trace task is started.
4. Double-click the new HARQ statistics monitoring trace task in the task list on the right of the Signaling Trace Management tab page. The task monitoring tab page
is displayed.
5. Check the number of DTXs on the PDSCH and PUSCH.
If there are a large number of DTXs, the PDCCH demodulation performance is poor. Disable this function by referring to 7.4.5 Deactivation, and set the offset of the
power for the PDCCH carrying dedicated control information relative to the CRS power. Check whether the PDCCH demodulation performance and KPIs improve.
After this function is disabled, you can increase the preceding offset to improve the PDCCH demodulation performance. However, this may result in excessively high
PDCCH power, which incurs PDCCH resource allocation failures. The failures cause a decrease in the number of scheduling times in the cell, which can be
obtained in the DCI Statistic Monitoring task. For details about DCI Statistic Monitoring, see 7.6 Performance Monitoring.
If other problems occur, contact Huawei engineers.
USCH Inner-Loop Power Control with Dynamic Scheduling Applied
If the gain of uplink cell throughput does not increase obviously after this function is enabled, check whether uplink interference is present in the cell. Perform the following steps
on the U2000 client:

2. In the navigation tree of the Signaling Trace window, choose Trace Type > LTE > Cell Performance Monitoring > Interference Detect Monitoring. Double-click
Interference Detect Monitoring.
3. Set task information in the displayed Interference Detect Monitoring dialog box and click Finish. The interference detection task is started.
5. Check the interference power on each uplink RB.
If intermittent interference on uplink RBs or severe uplink interference is observed, PUSCH inner-loop power control with dynamic scheduling applied will intensify
the interference.
To improve user experience in this situation, you are advised to turn on PuschRsrpHighThdSwitch so that the transmit power of UEs in the cell center is restricted
and the spectral efficiency for other UEs rises. However, the throughput of UEs in the cell center will decrease.

ll Unavailable Due to Excessively High Cell Power
This section takes macro eNodeBs for example. The maximum cell transmit power is calculated according to CRS power, PA, and PB. When the eMBMS feature is deployed, the
PMCH power is also considered in calculating the maximum cell transmit power. Cells become unavailable if the maximum cell transmit power exceeds RRU power capacity. If
ALM-29240 Cell Unavailable is reported, check whether the alarm is caused by excessively high cell transmit power. Perform the following steps:
1. Check the alarm locating information and record the local cell ID in the information.
3. In the navigation tree of the displayed MML Command window, select the eNodeB that serves the local cell.
4. Run the LST EUCELLSECTOREQM command and record the sector equipment ID corresponding to the local cell ID.
5. Run the LST SECTOREQM command and record the sector ID corresponding to the sector equipment ID.
6. Run the LST SECTOR command and record the cabinet number, subrack number, and slot number of the RRU corresponding to the sector ID.
7. Run the DSP RRU command and record the maximum output power of RRU transmit channels.
8. Run the DSP TXBRANCH command and record the maximum output power of each RRU transmit channel.
9. Run the LST PDSCHCFG command and record the CRS power and PB of the cell.
10. Run the LST CELLDLPCPDSCHPA command and record the PA of the cell.
11. (Optional) Run the LST CELLCHPWRCFG command and record the offset of the PMCH power relative to the maximum PDSCH power.
12. Refer to 3.11.1 Power Calculation to calculate the maximum cell transmit power based on the following items: CRS power, PA, PB, PMCH power offset, cell bandwidth,
and the number of antennas of the sector. If the maximum cell transmit power exceeds the RRU power capacity, refer to 7.4.3 Data Preparation and Feature Activation
to decrease the maximum cell transmit power until the power does not exceed the RRU power capacity. Then, check whether the alarm is cleared. If this alarm
persists, the alarm was not caused by excessively high cell transmit power.
8 Parameters
PDSCHCfg TxPowerOffsetAnt0 MOD PDSCHCFG LOFD-001001 DL 2x2 Meaning: Indicates the offset of the TX power of physical
LST PDSCHCFG LOFD-001003 MIMO channel 0 relative to the baseline TX power. The
LOFD-001060 DL 4x2 baseline TX power is determined by the system
MIMO bandwidth, cell reference signal power, Pa, and Pb. If the
DL 4X4 TX power configurations should be the same between
MIMO physical channels, set this parameter to 255. If the TX
power configurations should be different between
physical channels, set this parameter to a proper value
based on the actual situation. This parameter applies
only to FDD.
Unit: 0.1dB
Default Value: 255
only to FDD.
Unit: 0.1dB
Default Value: 255
only to FDD.
Unit: 0.1dB
Default Value: 255
only to FDD.


Unit: 0.1dB
Default Value: 255
CellAlgoSwitch UlPcAlgoSwitch MOD CELLALGOSWITCH LBFD-002009 / Broadcast of Meaning:

LST CELLALGOSWITCH TDLBFD-002009 system Indicates whether to enable power control for the PUSCH
LBFD-002026 / information or PUCCH. This parameter includes the following
TDLBFD-002026 Uplink Power options:
LBFD-081101 / Control CloseLoopSpsSwitch: Indicates whether to enable
TDLBFD-081104 PUCCH closed-loop power control for the PUSCH in semi-
Outer Loop persistent scheduling mode. If this option is selected,
Power TPC commands are adjusted based on correctness of
Control the received initial-transmission packets to decrease the
IBLER.
InnerLoopPuschSwitch: Indicates whether to enable
inner-loop power control for the PUSCH in dynamic
scheduling mode. Inner-loop power control for the
PUSCH in dynamic scheduling mode is enabled only
when this option is selected.
InnerLoopPucchSwitch: Indicates whether to enable
inner-loop power control for the PUCCH. Inner-loop
power control for the PUCCH is enabled only when this
option is selected.
CloseLoopOptPUSCHSwitch: Indicates whether to
enable the optimization on closed-loop power control for
the PUSCH in dynamic scheduling mode. The
optimization is enabled only when this option is selected.
This option applies only to LTE TDD.
PucchPcDtxSinrSwitch: Indicates whether the eNodeB
processes the measured uplink SINR in the DTX state
when the PUCCH DTX is detected. If this option is
deselected, the eNodeB does not process the measured
uplink SINR in the DTX state when the PUCCH DTX is
detected. If this option is selected, the eNodeB
processes the measured uplink SINR even when
PUCCH DTX is detected, generates power control
commands based on the SINR, and delivers the power
control commands to UEs.
PuschIoTCtrlSwitch: Indicates whether to enable
interference control in closed-loop power control for the
PUSCH in dynamic scheduling mode. Interference
control in closed-loop power control for the PUSCH in
dynamic scheduling mode is enabled only when this
option is selected.
SrsPcSwitch: Indicates whether to enable SRS power
control adjustment. SRS power control adjustment is
enabled only when this option is selected. This option
applies only to LTE TDD.
NearPointUeOptPUSCHSwitch: Indicates whether to
apply optimized closed-loop power control for the
PUSCH to UEs near the cell center. The optimization
helps UEs near the cell center to avoid unnecessary
power lowering due to inter-RAT or abrupt interference. If
this option is selected, optimized closed-loop power
control for the PUSCH is applied to UEs near the cell
center. If this option is deselected, optimized closed-loop
power control for the PUSCH is not applied to UEs near
the cell center. This option applies only to LTE FDD.
PuschRsrpHighThdSwitch: Indicates whether closed-loop
power control for the PUSCH limits the maximum value
of RSRP. If this option is deselected, closed-loop power
control for the PUSCH does not limit the maximum value
of RSRP. If this option is selected, the maximum value of
RSRP cannot exceed the RSRP value specified by the
PuschRsrpHighThd parameter in the CellPcAlgo MO.
This option applies only to LTE FDD.
OuterLoopPucchSwitch: Indicates whether to enable
outer-loop PUCCH power control. Outer-loop PUCCH
power control is enabled only when this option is
selected.
PucchInitialPcSwitch: Indicates whether to apply fast
PUCCH power control on newly accessed UEs. Fast
PUCCH power control is applied to newly accessed UEs
only when this option is selected. This option applies only
to LTE FDD.
GroupPCForPucchSwitch: Indicates whether to enable
power control for the PUCCH group in dynamic
scheduling. This option requires that UEs support
PUCCH group power control and applies only to LTE
TDD.
GUI Value Range: CloseLoopSpsSwitch
(CloseLoopSpsSwitch), InnerLoopPuschSwitch
(InnerLoopPuschSwitch), InnerLoopPucchSwitch
(InnerLoopPucchSwitch), CloseLoopOptPUSCHSwitch
(CloseLoopOptPUSCHSwitch), PucchPcDtxSinrSwitch
(PucchPcDtxSinrSwitch), PuschIoTCtrlSwitch
(PuschIoTCtrlSwitch), SrsPcSwitch(SrsPcSwitch),
NearPointUeOptPUSCHSwitch
(NearPointUeOptPUSCHSwitch),
PuschRsrpHighThdSwitch(PuschRsrpHighThdSwitch),
OuterLoopPucchSwitch(OuterLoopPucchSwitch),


PucchInitialPcSwitch(PucchInitialPcSwitch),
GroupPCForPucchSwitch(GroupPCForPucchSwitch)
Unit: None
Actual Value Range: CloseLoopSpsSwitch,
InnerLoopPuschSwitch, InnerLoopPucchSwitch,
CloseLoopOptPUSCHSwitch, PucchPcDtxSinrSwitch,
PuschIoTCtrlSwitch, SrsPcSwitch,
NearPointUeOptPUSCHSwitch,
PuschRsrpHighThdSwitch, OuterLoopPucchSwitch,
PucchInitialPcSwitch, GroupPCForPucchSwitch
Default Value: CloseLoopSpsSwitch:Off,
InnerLoopPuschSwitch:On, InnerLoopPucchSwitch:On,
CloseLoopOptPUSCHSwitch:Off,
PucchPcDtxSinrSwitch:On, PuschIoTCtrlSwitch:Off,
SrsPcSwitch:On, NearPointUeOptPUSCHSwitch:Off,
PuschRsrpHighThdSwitch:Off,
OuterLoopPucchSwitch:Off, PucchInitialPcSwitch:Off,
GroupPCForPucchSwitch:Off
CellChPwrCfg HoRarPwrEnhancedSwitch MOD CELLCHPWRCFG LBFD-002016 / Dynamic Meaning: Indicates whether the eNodeB increases the
LST CELLCHPWRCFG TDLBFD-002016 Downlink transmit power of the Random Access Response (RAR)
Power message when a UE is being handed over to the target
Allocation cell and repeatedly sends dedicated preambles. If this
parameter is set to OFF(OFF), the eNodeB does not
increase the transmit power of the RAR message sent to
the UE that is being handed over to the target cell. If this
parameter is set to ON(ON) and a UE that is being
handed over to the target cell repeatedly sends
dedicated preambles, the eNodeB increases the transmit
power of the RAR message by another 3 dB each time
on the basis of the RaRspPwr parameter value. The
transmit power of the RAR message can be increased by
a maximum of 6 dB.
GUI Value Range: OFF(OFF), ON(ON)
Unit: None
Default Value: OFF(OFF)
CellPcAlgo NearPointUePuschType MOD CELLPCALGO LBFD-002026 Uplink Power Meaning:

LST CELLPCALGO Control Indicates the type of UEs near the cell center to which
the PUSCH power increase applies.
If this parameter is set to AllUser(AllUser), the PUSCH
power increase applies to all UEs near the cell center.
If this parameter is set to UlBigPktUser(UlBigPktUser),
the PUSCH power increase applies to all large-packet
UEs near the cell center.
This option applies only to LTE FDD.
GUI Value Range: AllUser(AllUser), UlBigPktUser
(UlBigPktUser)
Unit: None
Actual Value Range: AllUser, UlBigPktUser
Default Value: AllUser(AllUser)
CellPcAlgo VoLteSinrHighThdOffset MOD CELLPCALGO LBFD-002026 / Uplink Power Meaning:

LST CELLPCALGO TDLBFD-002026 Control Indicates the offset of the PUSCH SINR high threshold of
UEs running voice services against the PUSCH SINR
high threshold of UEs running data services. This
parameter takes effect only when closed-loop PUSCH
In a heavily loaded network with a large number of UEs,
setting this parameter to a proper value decreases
interference in neighboring cells caused by CCUs
running voice services in the local cell, and improves
voice quality for CEUs running voice services in the local
cell. If this parameter is set to 0, the optimization scheme
does not apply to UEs running voice services. If this
parameter is adjusted to a value less than 0, the PUSCH
SINR high threshold of UEs running voice services is
lowered and the SINR evaluation value is changed. For
LTE TDD, this parameter is valid only when the
PuschIoTCtrlSwitch option is deselected under the
UlPcAlgoSwitch parameter; this parameter is not
applicable to UEs using 64QAM in the uplink.
Unit: 0.1dB
Default Value: 0
CellUlpcComm DeltaMsg2 MOD CELLULPCCOMM LBFD- Uplink Power Meaning: Indicates the power offset of Msg3 transmitted
LST CELLULPCCOMM 002026/TDLBFD- Control during uplink random access. This parameter is also
002026 used to set the initial power of the PUSCH or PUCCH for
closed-loop power control.
GUI Value Range: DELTAMsg2_NEG6(-6dB),
DELTAMsg2_NEG4(-4dB), DELTAMsg2_NEG2(-2dB),
DELTAMsg2_0(0dB), DELTAMsg2_2(2dB),
DELTAMsg2_4(4dB), DELTAMsg2_6(6dB),
DELTAMsg2_8(8dB)
Unit: dB
Actual Value Range: DELTAMsg2_NEG6,
DELTAMsg2_NEG4, DELTAMsg2_NEG2,


DELTAMsg2_0, DELTAMsg2_2, DELTAMsg2_4,
DELTAMsg2_6, DELTAMsg2_8
Default Value: DELTAMsg2_6(6dB)
PDSCHCfg ReferenceSignalPwr MOD PDSCHCFG LBFD-002016 / Dynamic Meaning: Indicates the cell reference signal power of
LST PDSCHCFG TDLBFD-002016 Downlink each physical antenna. However, the cell reference
LBFD-002009 / Power signal power delivered in SIB2 is that of each logical
TDLBFD-002009 Allocation antenna.
Broadcast of GUI Value Range: -600~500
system Unit: 0.1dBm
information Actual Value Range: -60~50
Default Value: 182
CellAlgoSwitch RepeaterSwitch MOD CELLALGOSWITCH LBFD-002016 Dynamic Meaning: Indicates the type of reference signal (RS)
LST CELLALGOSWITCH Downlink power to be delivered in system information block type 2
Power (SIB2). If the AntRsPwrSwitch option is selected, the RS
Allocation power calculated based on the AntOutputPwr parameter
value is delivered in SIB2. If the AntRsPwrSwitch option
is not selected, the RS power specified by the
ReferenceSignalPwr parameter is delivered in SIB2. This
parameter applies only to LTE FDD.
GUI Value Range: AntRsPwrSwitch(AntRsPwrSwitch)
Unit: None
Actual Value Range: AntRsPwrSwitch
Default Value: AntRsPwrSwitch:Off
CellChPwrCfg AntOutputPwr MOD CELLCHPWRCFG LBFD-002016 Dynamic Meaning: Indicates the transmit power for the entire
LST CELLCHPWRCFG Downlink channel bandwidth at each antenna connector. If the
Power AntRsPwrSwitch option of the RepeaterSwitch parameter
Allocation is selected, this parameter value is used to calculate the
reference signal (RS) power to be delivered in system
information block type 2 (SIB2).
Unit: W
Default Value: 20
Cell MultiRruCellFlag ADD CELL LOFD-003029 / SFN Meaning: Indicates whether to enable or disable the
MOD CELL TDLOFD-001075 Adaptive multi-RRU cell feature.
LST CELL TDLOFD-002008 SFN/SDMA GUI Value Range: BOOLEAN_FALSE(False),
TDLOFD-001098 Inter-BBP BOOLEAN_TRUE(True)
TDLOFD-001080 SFN Unit: None
TDLOFD-001081 Inter-BBU Actual Value Range: BOOLEAN_FALSE,
TDLOFD-001082 SFN BOOLEAN_TRUE
Inter-BBP Default Value: BOOLEAN_FALSE(False)
Adaptive
SFN/SDMA
Inter-BBU
Adaptive
SFN/SDMA
Cell MultiRruCellMode ADD CELL LOFD-003029 / SFN Meaning: Indicates the type of the multi-RRU cell.
MOD CELL TDLOFD-001075 Adaptive GUI Value Range: SFN(SFN), CELL_COMBINATION
LST CELL LOFD-070205 / SFN/SDMA (Cell Combination), TWO_RRU_COMBINATION(TWO
TDLOFD-002008 Inter-BBP RRU Combination), DIGITAL_COMBINATION(Cell
TDLOFD-001098 SFN Digital Combination), MPRU_AGGREGATION
TDLOFD-001080 Inter-BBU (MPRU_AGGREGATION)
TDLOFD-001081 SFN Unit: None
TDLOFD-001082 Inter-BBP Actual Value Range: SFN, CELL_COMBINATION,
Adaptive TWO_RRU_COMBINATION, DIGITAL_COMBINATION,
SFN/SDMA MPRU_AGGREGATION
Inter-BBU Default Value: SFN(SFN)
Adaptive
SFN/SDMA
eUCellSectorEqm ReferenceSignalPwr ADD EUCELLSECTOREQM None None Meaning: Indicates the reference signal power of the cell
MOD EUCELLSECTOREQM sector device. The value 32767 indicates that this
LST EUCELLSECTOREQM reference signal power parameter is invalid. In this case,
the reference signal power of the cell equals the value of
the PDSCHCFG parameter. For details, see 3GPP TS
36.213.This parameter is valid only when a multi-RRU
cell works in SFN,MPRU_AGGREGATION or cell
combination mode.
Unit: 0.1dBm
EuSectorEqmGroup ReferenceSignalPwr ADD None None Meaning: Indicates the reference signal power of a sector
EUSECTOREQMGROUP equipment group for a cell (all sets of sector equipment in
MOD the sector equipment group have the same reference
EUSECTOREQMGROUP
signal power). If this parameter is set to 32767, the
LST
EUSECTOREQMGROUP parameter value is invalid, and the cell uses the
reference signal power specified by the
ReferenceSignalPwr parameter in the PDSCHCFG MO.
For details, see 3GPP TS 36.213. This parameter takes
effect only when parameter MultiRruCellFlag is set to
BOOLEAN_TRUE and MultiRruCellMode is set to
MPRU_AGGREGATION or FDD SFN, respectively.


Unit: 0.1dBm
CellChPwrCfg SchPwr MOD CELLCHPWRCFG LBFD-002016 / Dynamic Meaning: Indicates the offset of the transmit power for
LST CELLCHPWRCFG TDLBFD-002016 Downlink the cell synchronization signals relative to the reference
LBFD-002009 / Power signal power.
TDLBFD-002009 Allocation GUI Value Range: -3175~3175
Broadcast of Unit: 0.005dB
system Actual Value Range: -15.875~15.875
information
Default Value: 0
CellAlgoSwitch DlPcAlgoSwitch MOD CELLALGOSWITCH LBFD-002003 / Physical Meaning: Indicates whether to enable power control for
LST CELLALGOSWITCH TDLBFD-002003 Channel the PDSCH, PDCCH, and PHICH. PdschSpsPcSwitch: If
LBFD-002009 / Management this option is deselected, power is allocated evenly
TDLBFD-002009 Broadcast of during semi-persistent scheduling on the PDSCH. If this
LBFD-002016 / system option is selected, power control is applied during semi-
TDLBFD-002016 information persistent scheduling on the PDSCH, ensuring quality
Dynamic (indicated by IBLER) of VoIP services in the QPSK
TDLOFD-001049
Downlink modulation scheme. PhichInnerLoopPcSwitch: Indicates
TDLOFD-001061 whether to enable PHICH inner-loop power control. If this
Power
Allocation option is deselected, only the initial transmit power for the
PHICH is set. If this option is selected, the eNodeB
Single
controls the physical channel transmit power to enable
Streaming
the receive SINR to converge to the target SINR.
Beamforming
PdcchPcSwitch: Indicates whether to enable PDCCH
Dual power control. If this option is deselected, power is
Streaming allocated evenly on the PDCCH. If this option is selected,
Beamforming power allocated to PDCCH is adjusted dynamically.
EDlMaxTXPwrSwitch: If this option is deselected, the
maximum TX power of the cell is determined by the RS
power and the scaling factor indexes Pa and Pb. If this
option is selected, the maximum TX power of the cell can
be increased to improve the RB usage in the cell. This
option has no impact on 10 MHz, 15 MHz and 20 MHz
LTE TDD cells. BFModeUserPwrSwitch: Indicates
whether to enable power optimization for beamforming
UEs. If this option is deselected, the original power
allocation scheme is adopted for beamforming UEs. If
this option is selected, the eNodeB uses the configured
power headroom to increases the power for beamforming
UEs. This option applies only to LTE TDD networks.
SigPowerIncreaseSwitch: Indicates whether to enable
signaling power improvement. If this option is selected,
the PDSCH transmit power increases when scheduling is
performed for downlink retransmission of signaling during
network entry. This option applies only to LTE TDD cells.
BFModeUserAdptPwrSwitch: Indicates whether to enable
power adaptation for beamforming UEs. If this option is
selected, the cell adaptively increases the power of
beamforming UEs based on the available power of the
RRU and loads at neighboring cell edges. In this way, the
average cell throughput increases. This option applies
only to LTE TDD networks.
GUI Value Range: PdschSpsPcSwitch,
EDlMaxTXPwrSwitch, BFModeUserPwrSwitch,
SigPowerIncreaseSwitch, BFModeUserAdptPwrSwitch
Unit: None
Actual Value Range: PdschSpsPcSwitch,
EDlMaxTXPwrSwitch, BFModeUserPwrSwitch,
SigPowerIncreaseSwitch, BFModeUserAdptPwrSwitch
Default Value: PdschSpsPcSwitch:Off,
PhichInnerLoopPcSwitch:Off, PdcchPcSwitch:On,
EDlMaxTXPwrSwitch:Off, BFModeUserPwrSwitch:Off,
SigPowerIncreaseSwitch:Off,
BFModeUserAdptPwrSwitch:Off
CellChPwrCfg PbchPwr MOD CELLCHPWRCFG LBFD-002016 / Dynamic Meaning: Indicates the offset of the PBCH transmit
LST CELLCHPWRCFG TDLBFD-002016 Downlink power relative to the reference signal power.
LBFD-002009 / Power GUI Value Range: -3175~3175
TDLBFD-002009 Allocation Unit: 0.005dB
Broadcast of Actual Value Range: -15.875~15.875
system
Default Value: -600
information
CellChPwrCfg PcfichPwr MOD CELLCHPWRCFG LBFD-002016 / Dynamic Meaning: Indicates the offset of the PCFICH transmit
LST CELLCHPWRCFG TDLBFD-002016 Downlink power relative to the reference signal power.
system
Default Value: -600
information
CellChPwrCfg RaRspPwr MOD CELLCHPWRCFG LBFD-002016 / Dynamic Meaning: Indicates the offset of the transmit power for
LST CELLCHPWRCFG TDLBFD-002016 Downlink the random access responses on the PDSCH channel
LBFD-002009 / Power relative to the reference signal power.
information
Default Value: 0


RACHCfg PreambleTransMax MOD RACHCFG LBFD-002009 / Broadcast of Meaning: Indicates the maximum number of preamble
LST RACHCFG TDLBFD-002009 system transmission times. For details about this parameter, see
LBFD-002010 / information 3GPP TS 36.321.
TDLBFD-002010 Random GUI Value Range: N3_PREMB_TRANS_MAX(3times),
Access N4_PREMB_TRANS_MAX(4times),
Procedure N5_PREMB_TRANS_MAX(5times),
N6_PREMB_TRANS_MAX(6times),
N200_PREMB_TRANS_MAX(200times)
Unit: None
Actual Value Range: N3_PREMB_TRANS_MAX,
N4_PREMB_TRANS_MAX, N5_PREMB_TRANS_MAX,
N6_PREMB_TRANS_MAX, N7_PREMB_TRANS_MAX,
N8_PREMB_TRANS_MAX,
N10_PREMB_TRANS_MAX,
N200_PREMB_TRANS_MAX
Default Value: N10_PREMB_TRANS_MAX(10times)
CellDlpcPhich PwrOffset MOD CELLDLPCPHICH LBFD-002016 / Dynamic Meaning: Indicates the power offset between the PHICH
LST CELLDLPCPHICH TDLBFD-002016 Downlink transmit(TX) power and the reference signal(RS) power.
Power This offset is used when PHICH power control is
Allocation disabled.
Unit: 0.1dB
Default Value: 0
CellDlpcPdcch DediDciPwrOffset MOD CELLDLPCPDCCH LBFD-002003 / Physical Meaning: Indicates the offset of the DCI power relative to
LST CELLDLPCPDCCH TDLBFD-002003 Channel the reference signal power when the PDCCH channel
LBFD-002016 / Management carries dedicated control information.
TDLBFD-002016 Dynamic GUI Value Range: -150~150
Downlink Unit: 0.1dB
Power Actual Value Range: -15~15
Allocation
Default Value: -30
CellChPwrCfg PchPwr MOD CELLCHPWRCFG LBFD-002011 Paging Meaning: Indicates the offset of the transmit power for
LST CELLCHPWRCFG LBFD-002016 / Dynamic the paging information on the PDSCH channel relative to
TDLBFD-002016 Downlink the reference signal power.
system Default Value: 0
information
CellChPwrCfg DbchPwr MOD CELLCHPWRCFG LBFD-002016 / Dynamic Meaning: Indicates the offset of the transmit power for
LST CELLCHPWRCFG TDLBFD-002016 Downlink broadcast information on the PDSCH channel relative to
LBFD-002009 / Power the reference signal power.
information
Default Value: -600
PDSCHCfg Pb MOD PDSCHCFG LBFD-002016 / Dynamic Meaning: Indicates the scaling factor index of the Energy
LST PDSCHCFG TDLBFD-002016 Downlink Per Resource Element (EPRE) on the PDSCH. This
LBFD-002009 / Power scaling factor is determined by the value of this
TDLBFD-002009 Allocation parameter and the antenna port. For details, see 3GPP
Broadcast of TS 36.213.
system GUI Value Range: 0~3
Default Value: 1
ENodeBAlgoSwitch DlIcicSwitch MOD TDLBFD- Downlink Meaning:

ENODEBALGOSWITCH 00202201 Static Inter- Provides the DL ICIC algorithm switches. The switch has
LST Cell
ENODEBALGOSWITCH three states:
Interference DlIcicSwitch_OFF_ENUM: Indicates that DL ICIC is
Coordination disabled.
DlIcicDynamicSwitch_ON_ENUM: Indicates that dynamic
DL ICIC is enabled.
DlIcicStaticSwitch_ON_ENUM: Indicates that static DL
ICIC is enabled.
It is recommended that this parameter be used only in
LTE TDD cells.
GUI Value Range: DlIcicSwitch_OFF_ENUM,
DlIcicDynamicSwitch_ON_ENUM,
DlIcicStaticSwitch_ON_ENUM
Unit: None
Actual Value Range: DlIcicSwitch_OFF_ENUM,
DlIcicDynamicSwitch_ON_ENUM,
DlIcicStaticSwitch_ON_ENUM
Default Value: DlIcicSwitch_OFF_ENUM


CellDlpcPdsch CcuPa MOD CELLDLPCPDSCH LBFD-002016 / Dynamic Meaning: Indicates the PA value of cell center UEs when
LST CELLDLPCPDSCH TDLBFD-002016 Downlink DL ICIC is enabled.
TDLBFD- Power GUI Value Range: PA_NEG6(-6dB), PA_NEG4DOT77
00202201 Allocation (-4.77dB), PA_NEG3(-3dB), PA_NEG1DOT77(-1.77dB),
Downlink PA_0(0dB), PA_1(1dB), PA_2(2dB), PA_3(3dB)
Static Inter- Unit: dB
Cell Actual Value Range: PA_NEG6, PA_NEG4DOT77,
Interference PA_NEG3, PA_NEG1DOT77, PA_0, PA_1, PA_2, PA_3
Coordination
Default Value: PA_NEG6(-6dB)
CellDlpcPdsch CeuPa MOD CELLDLPCPDSCH LBFD-002016 / Dynamic Meaning: Indicates the PA value of cell edge UEs when
LST CELLDLPCPDSCH TDLBFD-002016 Downlink DL ICIC is enabled.
TDLBFD- Power GUI Value Range: PA_NEG6(-6dB), PA_NEG4DOT77
00202201 Allocation (-4.77dB), PA_NEG3(-3dB), PA_NEG1DOT77(-1.77dB),
Downlink PA_0(0dB), PA_1(1dB), PA_2(2dB), PA_3(3dB)
Static Inter- Unit: dB
Cell Actual Value Range: PA_NEG6, PA_NEG4DOT77,
Interference PA_NEG3, PA_NEG1DOT77, PA_0, PA_1, PA_2, PA_3
Coordination
Default Value: PA_NEG1DOT77(-1.77dB)
CellDlpcPdschPa PaPcOff MOD CELLDLPCPDSCHPA LBFD-002016 / Dynamic Meaning: Indicates the PA to be used when PA
LST CELLDLPCPDSCHPA TDLBFD-002016 Downlink adjustment for PDSCH power control is disabled, DL
Power ICIC is disabled, and the even power distribution is used
Allocation for the PDSCH.
GUI Value Range: DB_6_P_A(-6 dB), DB_4DOT77_P_A
(-4.77 dB), DB_3_P_A(-3 dB), DB_1DOT77_P_A(-1.77
dB), DB0_P_A(0 dB), DB1_P_A(1 dB), DB2_P_A(2 dB),
DB3_P_A(3 dB)
Unit: dB
Actual Value Range: DB_6_P_A, DB_4DOT77_P_A,
DB_3_P_A, DB_1DOT77_P_A, DB0_P_A, DB1_P_A,
DB2_P_A, DB3_P_A
Default Value: DB_3_P_A(-3 dB)
CellChPwrCfg PmchPwrOffset MOD CELLCHPWRCFG LOFD- eMBMS Meaning:

LST CELLCHPWRCFG 070220/TDLOFD- Phase 1 Indicates the offset of PMCH power to the maximum
070220 based on PDSCH power. The maximum PDSCH power is
Centralized calculated by using the following formula: Max
MCE (P_PDSCH_A, P_PDSCH_B). For details about formulas
Architecture to calculate P_PDSCH_A and P_PDSCH_B, see section
"Basics of PDSCH Power Calculation" in
Power Control Feature Parameter Description
.
GUI Value Range: 0~60,255
Unit: 0.1dB
Actual Value Range: 0~6,255
Default Value: 255
RACHCfg PreambInitRcvTargetPwr MOD RACHCFG LBFD-002009 / Broadcast of Meaning:

LST RACHCFG TDLBFD-002009 system Indicates the target UE transmit power for the PRACH
LBFD-002010 / information expected by the eNodeB when PRACH preamble format
TDLBFD-002010 Random 0 is applied on condition that requirements for preamble
LBFD-002026 / Access detection performance are met.
TDLBFD-002026 Procedure For details, see 3GPP TS 36.321.
Uplink Power GUI Value Range: DBM_120(-120dBm), DBM_118
Control (-118dBm), DBM_116(-116dBm), DBM_114(-114dBm),
DBM_112(-112dBm), DBM_110(-110dBm), DBM_108
(-108dBm), DBM_106(-106dBm), DBM_104(-104dBm),
DBM_102(-102dBm), DBM_100(-100dBm), DBM_98
(-98dBm), DBM_96(-96dBm), DBM_94(-94dBm),
DBM_92(-92dBm), DBM_90(-90dBm)
Unit: dBm
Actual Value Range: DBM_120, DBM_118, DBM_116,
DBM_114, DBM_112, DBM_110, DBM_108, DBM_106,
DBM_104, DBM_102, DBM_100, DBM_98, DBM_96,
DBM_94, DBM_92, DBM_90
Default Value: DBM_104(-104dBm)
CellUlpcDedic FilterRsrp MOD CELLULPCDEDIC LBFD-002026 / Uplink Power Meaning: Indicates the alpha filtering coefficient used by
LST CELLULPCDEDIC TDLBFD-002026 Control the UE during RSRP measurement for path loss
estimation.
GUI Value Range: UU_FC0_FILTER_COEFF
(UU_FC0_FILTER_COEFF), UU_FC1_FILTER_COEFF
(UU_FC9_FILTER_COEFF),
UU_FC11_FILTER_COEFF


(UU_FC19_FILTER_COEFF)
Unit: None
Actual Value Range: UU_FC0_FILTER_COEFF,
UU_FC1_FILTER_COEFF, UU_FC2_FILTER_COEFF,
UU_FC13_FILTER_COEFF,
UU_FC15_FILTER_COEFF,
UU_FC17_FILTER_COEFF, UU_FC19_FILTER_COEFF
Default Value: UU_FC6_FILTER_COEFF
(UU_FC6_FILTER_COEFF)
RACHCfg PwrRampingStep MOD RACHCFG LBFD-002009 / Broadcast of Meaning:

LST RACHCFG TDLBFD-002009 system Indicates the step by which the TX power for random
LBFD-002010 / information access preambles is increased each time after a RACH
TDLBFD-002010 Random access failure. If multiple attempts to access the PRACH
LBFD-002026 / Access fail, the UE increases the TX power for random access
TDLBFD-002026 Procedure preambles by a step specified by this parameter each
Uplink Power time after an access failure to ensure successful access.
Control For details, see 3GPP TS 36.321.
GUI Value Range: DB0_PWR_RAMPING_STEP(0dB),
DB2_PWR_RAMPING_STEP(2dB),
DB4_PWR_RAMPING_STEP(4dB),
DB6_PWR_RAMPING_STEP(6dB)
Unit: dB
Actual Value Range: DB0_PWR_RAMPING_STEP,
DB2_PWR_RAMPING_STEP,
DB4_PWR_RAMPING_STEP,
DB6_PWR_RAMPING_STEP
Default Value: DB2_PWR_RAMPING_STEP(2dB)
CellUlpcComm P0NominalPUSCH MOD CELLULPCCOMM LBFD-002026 / Uplink Power Meaning: Indicates the nominal P0 value of the PUSCH.
LST CELLULPCCOMM TDLBFD-002026 Control It is used in UL power control. For details, see 3GPP TS
LBFD-002009 / Broadcast of 36.213.
TDLBFD-002009 system GUI Value Range: -126~24
information Unit: dBm
Default Value: -67
CellUlpcComm PassLossCoeff MOD CELLULPCCOMM LBFD-002026 / Uplink Power Meaning: Indicates the compensation factor for path loss.
LST CELLULPCCOMM TDLBFD-002026 Control It is used in UL power control. For details, see 3GPP TS
LBFD-002009 / Broadcast of 36.213.
TDLBFD-002009 system GUI Value Range: AL0(0), AL04(0.4), AL05(0.5), AL06
information (0.6), AL07(0.7), AL08(0.8), AL09(0.9), AL1(1)
Unit: None
Actual Value Range: AL0, AL04, AL05, AL06, AL07,
AL08, AL09, AL1
Default Value: AL07(0.7)
CellUlpcDedic PathlossReferenceLink MOD CELLULPCDEDIC LBFD-002026 / Uplink Power Meaning: Indicates the path loss reference link used by a
LST CELLULPCDEDIC TDLBFD-002026 Control serving cell in the downlink. For details about how to use
this parameter, see 3GPP TS 36.213.
GUI Value Range: PCELL(pCell), SCELL(sCell)
Unit: None
Actual Value Range: PCELL, SCELL
Default Value: SCELL(sCell)
CellUlpcDedic DeltaMcsEnabled MOD CELLULPCDEDIC LBFD-002026 / Uplink Power Meaning: Indicates whether a UE needs to adjust the
LST CELLULPCDEDIC TDLBFD-002026 Control transmit power based on the MCS. The indication is sent
to the UE through an RRC message. The indication is
denoted by a bit. Bit 0 indicates that both Ks and ΔTF are
equal to 0. Bit 1 indicates that Ks is equal to 1.25 and
ΔTF is calculated. For details, see 3GPP TS 36.213.
GUI Value Range: UU_DISABLE(Disable), UU_ENABLE
(Enable)
Unit: None
Actual Value Range: UU_DISABLE, UU_ENABLE
Default Value: UU_DISABLE(Disable)
CellPcAlgo PuschRsrpHighThd MOD CELLPCALGO LBFD-002026 Uplink Power Meaning: Indicates the upper limit of RSRP in closed-
LST CELLPCALGO Control loop power control for the PUSCH. This parameter takes
effect only when PuschRsrpHighThdSwitch of the
UlPcAlgoSwitch parameter in the CellAlgoSwitch MO is
on.
Unit: dBm
Default Value: -82
CellAlgoSwitch UlSchSwitch MOD CELLALGOSWITCH LOFD-001016 / VoIP Semi- Meaning:

LST CELLALGOSWITCH TDLOFD-001016 persistent This parameter indicates the switches related to uplink
LOFD-001048 / Scheduling (UL) scheduling in the cell. The switches are used to
TDLOFD-001048 TTI Bundling enable or disable specific UL scheduling functions.
LOFD- Dynamic SpsSchSwitch: Indicates whether to enable semi-
00101502 / Scheduling persistent scheduling during talk spurts of VoLTE
TDLOFD- Basic services. If this option is selected, semi-persistent
00101502 Scheduling scheduling is applied during talk spurts of VoLTE


TDLBFD-002025 MBR>GBR services. If this option is deselected, dynamic scheduling
LBFD-070102 / Configuration is applied during talk spurts of VoLTE services.
TDLBFD-070102 UL 2x2 MU- SinrAdjustSwitch: Indicates whether to adjust the
LOFD-001002 MIMO measured signal to interference plus noise ratio (SINR)
LOFD-001058 / UL 2x4 MU- based on ACK/NACK in UL hybrid automatic repeat
TDLOFD-001058 MIMO request (HARQ) processes.
LBFD-001006 AMC PreAllocationSwitch: Indicates whether to enable
preallocation in the uplink. If this option is selected: (1) If
the SmartPreAllocationSwitch option is deselected and a
UE is in the discontinuous reception (DRX) state,
preallocation is disabled for the UE in the uplink; (2) If the
SmartPreAllocationSwitch option is deselected and the
UE is not in the DRX state, preallocation is enabled for
the UE in the uplink; (3) If the SmartPreAllocationSwitch
option is selected and the SmartPreAllocationDuration
parameter value is greater than 0, smart preallocation is
enabled for the UE in the uplink; (4) If the
SmartPreAllocationSwitch option is selected and the
SmartPreAllocationDuration parameter value is 0,
preallocation is disabled for the UE in the uplink. If this
option is deselected, preallocation is disabled for the UE
in the uplink. If bearer-level preallocation or bearer-level
smart preallocation is enabled for a QCI, cell-level
preallocation and cell-level smart preallocation do not
apply to UEs with the QCI.
UlVmimoSwitch: Indicates whether to enable multi-user
MIMO (MU-MIMO) in the UL. If this option is selected,
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 VoLTE 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 option is selected, IM component
elimination is performed on UEs. If this option is
deselected, IM component elimination is not performed
on UEs. This option applies only to FDD cells working in
frequency band 20.
SmartPreAllocationSwitch: Indicates whether to enable
uplink smart preallocation when preallocation is enabled
(by selecting PreAllocationSwitch). If both the
PreAllocationSwitch and SmartPreAllocationSwitch
options are selected 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 option is selected,
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 option takes effect only if
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 MU-MIMO
applied. In an LTE TDD cell, this option takes effect only
when the cell is configured with subframe configuration 2
or 5. After this option 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 IBLER adjustment algorithm. If this option is
selected, the target IBLER is adjusted for CEUs in TDD
cells to increase the cell edge throughput. If this option is
selected independently for FDD cells, the algorithm does
not take effect.
UlEnhancedFssSwitch: Indicates whether to enable
uplink load-based enhanced frequency selective
scheduling. This option applies only to FDD cells.
UlIicsAlgoSwitch: Indicates whether to enable the UL
IICS algorithm. If this option is selected, interference can
be reduced based on accurate detection of user
attributes and resource scheduling coordination, thereby
increasing the cell edge throughput. This option applies
only to LTE TDD.


UlEnhancedSrSchSwitch: Indicates whether uplink re-
scheduling is performed only when the On Duration timer
for the DRX long cycle starts. Uplink re-scheduling is
required if the number of HARQ retransmissions for a
scheduling request (SR) reaches the maximum value but
the scheduling still fails. If this option is selected, uplink
re-scheduling is performed only when the On Duration
timer for the DRX long cycle starts. If this option is
deselected, 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 this option be selected
in live networks.
SchedulerCtrlPowerSwitch: Indicates whether the uplink
scheduler performs scheduling without considering
power control restrictions. If this option is selected, the
uplink scheduler performs scheduling without considering
power control restrictions, which ensures full utilization of
the transmit power for all UEs. If this option is
deselected, 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 option is
selected, 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
guaranteed bit rate (GBR) on the GBR bearer. If this
option is selected, the eNodeB performs uplink
scheduling on GBR bearers based on the MBR and
GBR. If this option is deselected, 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 option
is selected, the eNodeB prioritizes UEs based on the
MBRs during uplink scheduling. This option applies only
to LTE TDD.
UeAmbrUlSchSwitch: Indicates whether the eNodeB
performs uplink scheduling based on the aggregate
maximum bit rate (AMBR) of UEs. If this option is
selected, the eNodeB prioritizes UEs based on the UE-
AMBRs during uplink scheduling. This option applies only
to LTE TDD.
UlEnhancedDopplerSwitch: Indicates whether to enable
enhanced uplink scheduling based on mobility speed. If
this option is selected, enhanced uplink scheduling
based on mobility speed is enabled. In enhanced uplink
scheduling based on mobility speed, the eNodeB uses
Doppler measurement results to determine low-speed
UEs to further improve UL performance of low-speed
UEs. If this option is deselected, enhanced uplink
scheduling based on mobility speed is disabled.
Enhanced uplink scheduling based on mobility speed
takes effect only when the DopMeasLevel parameter is
set to CLASS_1 and the UlEnhancedDopplerSwitch
option is selected. This option 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
option is selected, the eNodeB raises the scheduling
priority of UEs sending uplink access signaling. If this
option is deselected, 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 option is selected,
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 the last two
retransmissions and decrease uplink RBLER. If this
option is deselected, optimization on the scheduling
policy for the last two retransmissions is disabled.
UlInterfFssSwitch: Indicates whether to enable
interference-based uplink frequency-selective
scheduling. This parameter applies only to LTE FDD.
UlSmallRBSpectralEffOptSw: Indicates whether to
enable spectral efficiency optimization on uplink small
RBs. If this option is selected, the optimization is
enabled, thereby ensuring that the transmission block
size calculated based on optimized spectral efficiency is
not less than the traffic volume to be scheduled. If this
option is deselected, the optimization is disabled.


PuschUsePucchRbSwitch: Indicates whether PUCCH
RBs can be occupied by the PUSCH. In scenarios with a
single user, if this option is selected, PUCCH RBs can be
occupied by the PUSCH. If this option is deselected,
PUCCH RBs cannot be occupied by the PUSCH. In
scenarios with multiple users, PUCCH RBs cannot be
occupied by the PUSCH regardless of whether this
option is selected.
PuschDtxSchOptSwitch: If this option is selected, the
eNodeB determines whether to perform adaptive
retransmission during UL scheduling based on the
PUSCH DTX detection result. This option 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 option applies only to
TDD cells.
PrachRbReuseSwitch: If this option is selected, the
PUSCH and PRACH transmissions can use the same
resource. If this option is deselected, the PUSCH and
PRACH transmissions cannot use the same resource.
This option applies only to TDD cells.
ULFSSAlgoswitch: If this option is deselected, uplink
frequency-selective scheduling is disabled. If this option
is selected, uplink frequency-selective scheduling is
enabled. This option applies only to LTE TDD.
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. This option applies only to LTE FDD cells.
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.
HighOrderVMIMOSwitch: Indicates whether to enable
high-order VMIMO. High-order VMIMO is enabled only
when this option is selected. This option applies only to
TDD cells.
VMIMOReduceMCSRiseRBSwitch: Indicates whether
VMIMO pairing is performed for UEs whose MCS index
is reduced to increase the number of RBs. VMIMO is
performed for UEs whose MCS index is reduced to
increase the number of RBs only when this option is
selected. This option applies only to TDD cells.
VoLTEUeVmimoSwitch: Indicates whether VMIMO
pairing is performed for VoLTE UEs. VMIMO pairing is
performed for VoLTE UEs only when this option is
selected. This option applies only to TDD cells.
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
(UlLast2RetransSchOptSwitch), UlInterfFssSwitch
(UlInterfFssSwitch), UlSmallRBSpectralEffOptSw
(UlSmallRBSpectralEfficiencyOptSw),
PuschUsePucchRbSwitch(PuschUsePucchRbSwitch),
PuschDtxSchOptSwitch(PuschDtxSchOptSwitch),
ULFSSAlgoSwitch(ULFSSAlgoSwitch),
PrachRbReuseSwitch(PrachRbReuseSwitch),
SrSchDataAdptSw(SrSchDataAdptSw),
UlFssUserThdStSwitch(UlFssUserThdStSwitch),
HighOrderVMIMOSwitch(HighOrderVMIMOSwitch),
VMIMOReduceMCSRiseRBSwitch
(VMIMOReduceMCSRiseRBSwitch),
VoLTEUeVmimoSwitch(VoLTEUeVmimoSwitch)
Unit: None
Actual Value Range: SpsSchSwitch, SinrAdjustSwitch,
PreAllocationSwitch, UlVmimoSwitch, TtiBundlingSwitch,
ImIcSwitch, SmartPreAllocationSwitch, PuschDtxSwitch,
UlIblerAdjustSwitch, UlEnhancedFssSwitch,
UlEnhancedSrSchSwitch, SchedulerCtrlPowerSwitch,
UlIicsAlgoSwitch, UlMinGbrSwitch, UlMbrCtrlSwitch,
MbrUlSchSwitch, UeAmbrUlSchSwitch,
UlEnhancedDopplerSwitch, UlRaUserSchOptSw,
UlLast2RetransSchOptSwitch, UlInterfFssSwitch,
UlSmallRBSpectralEffOptSw, PuschUsePucchRbSwitch,
PuschDtxSchOptSwitch, ULFSSAlgoSwitch,
PrachRbReuseSwitch, SrSchDataAdptSw,
UlFssUserThdStSwitch, HighOrderVMIMOSwitch,


VMIMOReduceMCSRiseRBSwitch,
VoLTEUeVmimoSwitch
Default Value: SpsSchSwitch:Off, SinrAdjustSwitch:On,
PreAllocationSwitch:On, UlVmimoSwitch:Off,
TtiBundlingSwitch:Off, ImIcSwitch:Off,
SmartPreAllocationSwitch:On, PuschDtxSwitch:On,
UlIblerAdjustSwitch:Off, UlEnhancedFssSwitch:On,
UlEnhancedSrSchSwitch:On,
SchedulerCtrlPowerSwitch:Off, UlIicsAlgoSwitch:Off,
UlMinGbrSwitch:Off, UlMbrCtrlSwitch:Off,
MbrUlSchSwitch:Off, UeAmbrUlSchSwitch:Off,
UlEnhancedDopplerSwitch:Off, UlRaUserSchOptSw:Off,
UlLast2RetransSchOptSwitch:On, UlInterfFssSwitch:Off,
UlSmallRBSpectralEffOptSw:Off,
PuschUsePucchRbSwitch:Off,
PuschDtxSchOptSwitch:Off, ULFSSAlgoSwitch:On,
PrachRbReuseSwitch:Off, SrSchDataAdptSw:On,
UlFssUserThdStSwitch:Off, HighOrderVMIMOSwitch:Off,
VMIMOReduceMCSRiseRBSwitch:Off,
VoLTEUeVmimoSwitch:Off
CellUlpcComm DeltaPreambleMsg3 MOD CELLULPCCOMM LBFD-002026 / Uplink Power Meaning: Indicates the power offset (delta value) of
LST CELLULPCCOMM TDLBFD-002026 Control message 3 relative to the preamble. This power offset
LBFD-002009 / Broadcast of has a step size of 2. For details, see 3GPP TS 36.213.
TDLBFD-002009 system GUI Value Range: -1~6
information Unit: 2dB
Default Value: 4
CellUlpcComm P0NominalPUCCH MOD CELLULPCCOMM LBFD-002026 / Uplink Power Meaning: Indicates the target UE transmit power for the
LST CELLULPCCOMM TDLBFD-002026 Control PUCCH expected by the eNodeB on condition that
LBFD-002009 / Broadcast of normal demodulation can be performed. For details, see
TDLBFD-002009 system 3GPP TS 36.213.
information GUI Value Range: -127~-96
Unit: dBm
Default Value: -115
CellUlpcComm DeltaFPUCCHFormat1 MOD CELLULPCCOMM LBFD-002026 / Uplink Power Meaning: Indicates the Delta value corresponding to
LST CELLULPCCOMM TDLBFD-002026 Control PUCCH format 1. For details, see 3GPP TS 36.213.
LBFD-002009 / Broadcast of GUI Value Range: DELTAF_2(-2dB), DELTAF0(0dB),
TDLBFD-002009 system DELTAF2(2dB)
information Unit: dB
Actual Value Range: DELTAF_2, DELTAF0, DELTAF2
Default Value: DELTAF0(0dB)
CellUlpcComm DeltaFPUCCHFormat1b MOD CELLULPCCOMM LBFD-002026 / Uplink Power Meaning: Indicates the Delta value corresponding to
LST CELLULPCCOMM TDLBFD-002026 Control PUCCH format 1b. For details, see 3GPP TS 36.213.
LBFD-002009 / Broadcast of GUI Value Range: DELTAF1(1dB), DELTAF3(3dB),
Actual Value Range: DELTAF1, DELTAF3, DELTAF5
CellUlpcComm DeltaFPUCCHFormat2 MOD CELLULPCCOMM LBFD-002026 / Uplink Power Meaning: Indicates the Delta value corresponding to
LST CELLULPCCOMM TDLBFD-002026 Control PUCCH format 2. For details, see 3GPP TS 36.213.
TDLBFD-002009 system DELTAF1(1dB), DELTAF2(2dB)
Actual Value Range: DELTAF_2, DELTAF0, DELTAF1,
DELTAF2
CellUlpcComm DeltaFPUCCHFormat2a MOD CELLULPCCOMM LBFD-002026 / Uplink Power Meaning: Indicates the Delta value corresponding to
LST CELLULPCCOMM TDLBFD-002026 Control PUCCH format 2a. For details, see 3GPP TS 36.213.
CellUlpcComm DeltaFPUCCHFormat2b MOD CELLULPCCOMM LBFD-002026 / Uplink Power Meaning: Indicates the Delta value corresponding to
LST CELLULPCCOMM TDLBFD-002026 Control PUCCH format 2b. For details, see 3GPP TS 36.213.
CellPcAlgo PucchPcPeriod MOD CELLPCALGO LBFD-002026 Uplink Power Meaning: Indicates the period of power control for the
LST CELLPCALGO Control PUCCH.
Unit: 20ms
Default Value: 1
CellPcAlgo PucchPcTargetSinrOffset MOD CELLPCALGO LBFD-002026 Uplink Power Meaning: Indicates the offset to the target signal to
LST CELLPCALGO Control interference plus noise ratio (SINR) in power control for
the PUCCH.


Unit: dB
Default Value: 0
CellPcAlgo PucchCloseLoopPcType MOD CELLPCALGO LBFD-002026 Uplink Power Meaning: Indicates whether the P0NominalPUCCH
LST CELLPCALGO Control parameter affects closed-loop power control (CL PC) for
the PUCCH. If this parameter is set to
NOT_USE_P0NOMINALPUCCH, the P0NominalPUCCH
parameter does not affect CL PC for the PUCCH. If this
parameter is set to USE_P0NOMINALPUCCH, the
reference signal received power (RSRP) cannot exceed
the P0NominalPUCCH parameter value in CL PC for the
PUCCH.
GUI Value Range: NOT_USE_P0NOMINALPUCCH(Not
Use P0NominalPUCCH), USE_P0NOMINALPUCCH
(Use P0NominalPUCCH)
Unit: None
Actual Value Range: NOT_USE_P0NOMINALPUCCH,
USE_P0NOMINALPUCCH
Default Value: NOT_USE_P0NOMINALPUCCH(Not Use
P0NominalPUCCH)
CellUlpcDedic PSrsOffsetDeltaMcsDisable MOD CELLULPCDEDIC LBFD-002026 / Uplink Power Meaning: Indicates the power offset of the sounding
LST CELLULPCDEDIC TDLBFD-002026 Control reference signal to the PUSCH when DeltaMcsEnabled
is set to UU_DISABLE.
GUI Value Range:
-105,-90,-75,-60,-45,-30,-15,0,15,30,45,60,75,90,105,120
Unit: 0.1dB
Actual Value Range:
-10.5,-9,-7.5,-6,-4.5,-3,-1.5,0,1.5,3,4.5,6,7.5,9,10.5,12
Default Value: -30
CellUlpcDedic PSrsOffsetDeltaMcsEnable MOD CELLULPCDEDIC LBFD-002026 / Uplink Power Meaning: Indicates the power offset of the sounding
LST CELLULPCDEDIC TDLBFD-002026 Control reference signal to the PUSCH when DeltaMcsEnabled
is set to UU_ENABLE.
GUI Value Range:
-30,-20,-10,0,10,20,30,40,50,60,70,80,90,100,110,120
Unit: 0.1dB
Actual Value Range: -3,-2,-1,0,1,2,3,4,5,6,7,8,9,10,11,12
Default Value: -30
CellAlgoSwitch CqiAdjAlgoSwitch MOD CELLALGOSWITCH LOFD- CQI Meaning:

LST CELLALGOSWITCH 00101501 / Adjustment CqiAdjAlgoSwitch: Indicates whether to allow the
TDLOFD- Dynamic eNodeB to adjust the UE-reported CQI based on the
00101501 Scheduling initial block error rate (IBLER). If this option is selected,
LOFD- the CQI adjustment algorithm is enabled. In this case, the
00101502 / eNodeB adjusts the UE-reported CQI based on the
TDLOFD- IBLER. If this option is deselected, the CQI adjustment
00101502 algorithm is disabled. In this case, the eNodeB does not
adjust the UE-reported CQI based on the IBLER.
StepVarySwitch: Indicates whether to enable the
variable-step-based adjustment algorithm. If this option is
selected, the variable-step-based adjustment algorithm is
enabled to accelerate the convergence of IBLER. In this
case, rapid adjustment at large steps is applied if there is
a relatively large difference between the measured
IBLER and target IBLER; fine-tuning at small steps is
applied if the measured IBLER approaches the target
IBLER. If this option is deselected, the adjustment is
performed at a fixed step.
DlVarIBLERtargetSwitch: Indicates whether to enable
downlink target IBLER adaptation. If this option is
selected, the downlink target IBLER is adjusted based on
the size of transport blocks (TBs) to improve the spectral
efficiency. If this option is deselected, the target IBLER is
determined based on the setting of
DlEnVarIblerTargetSwitch.
TddBundlingCqiAdjOptSwitch: Indicates whether to
enable optimized CQI adjustment algorithm in ACK
bundling mode. If this option is selected, the optimized
CQI adjustment algorithm is enabled. If this option is
deselected, the optimized CQI adjustment algorithm is
disabled.
TddMultiplexingCqiAdjOptSwitch: Indicates whether to
enable the optimized CQI adjustment algorithm in ACK
multiplexing mode. If this option is selected, the
optimized CQI adjustment algorithm is enabled. If this
option is deselected, the optimized CQI adjustment
algorithm is disabled.
AdaptiveStepVarySwitch: Indicates whether to enable
adaptive step change in CQI adjustment. If this option is
selected, significant changes in the signal quality can be
detected, and the CQI adjustment is performed at a large
step, accelerating the IBLER convergence. If this option
is deselected, the CQI adjustment is performed at a fixed
step.
DlCqiAdjDeltaOptSwitch: Indicates whether to enable
optimization on downlink CQI adjustment calculation. If
this option is deselected, the CQI adjustment is
calculated based on the following formula: CQI
adjustment = (Number of ACKs for initial transmissions x


CQI adjustment per ACK + Number of NACKs for initial
transmissions x CQI adjustment per NACK)/(Number of
NACKs for initial transmissions + Number of ACKs for
initial transmissions). If this option is selected, the CQI
adjustment is calculated based on the following formula:
CQI adjustment = Number of ACKs for initial
transmissions x CQI adjustment per ACK + Number of
NACKs for initial transmissions x CQI adjustment per
NACK).
DlEnVarIblerTargetSwitch: Indicates whether to enable
enhanced downlink target IBLER adaption. If this option
is selected, the downlink target IBLER is adaptively
adjusted based on CQI fluctuation and TB size. If this
option is deselected, the downlink target IBLER policy is
controlled by DlVarIBLERtargetSwitch.
DlRetxTbsIndexAdjOptSwitch: Indicates whether to
enable transport block size (TBS) index adjustment
optimization in retransmissions. If this option is selected,
TBS index adjustment optimization in retransmissions is
enabled. The TBS index is lowered for the scheduling of
the last two retransmissions, and the TBS index is
determined based on the CQI adjustment for the
scheduling of other retransmissions. If this option is
deselected, TBS index adjustment optimization in
retransmissions is disabled. The TBS index is
determined based on the CQI adjustment for the
scheduling of all retransmissions.
CfiConvertOptSwitch: Indicates whether to enable CFI
calculation optimization. If this option is selected, new
CFI calculation tables for normal and special subframes
are used to ensure more accurate MCS selection in
normal and special subframes and facilitate IBLER
convergence to the target value. If this option is
deselected, the original CFI calculation tables for normal
and special subframes are used. This option applies only
to LTE TDD.
BundlingOptThdSwitch: Indicates whether to adjust the
MCS index threshold for enabling the optimized CQI
adjustment algorithm in TDD bundling mode. If this
option is selected, the lower MCS index threshold for
enabling the optimized CQI adjustment algorithm in TDD
bundling mode is changed from MCS index 6 to MCS
index 0. If this option is deselected, the lower MCS index
threshold for enabling the optimized CQI adjustment
algorithm in TDD bundling mode is MCS index 6. This
DlSpsMcsIncreaseSwitch: Indicates whether to enable
MCS index increase for semi-persistent scheduling
(SPS). If this option is selected, MCS index increase is
enabled for SPS. If this option is deselected, MCS index
increase is disabled for SPS. Turning on this switch can
reduce the number of RBs for SPS and improve cell
performance when the RB resource is limited but may
decrease the VoLTE MOS. Turning off this switch may
increase the number of RBs for SPS but increase the
VoLTE MOS.
CqiAdjTimeEffSwitch: Indicates whether to enable
validity evaluation and adjustment for CQI adjustment
values, and also controls whether to trigger large-step-
based CQI adjustment in the scenario where a long time
has elapsed before a UE begins to perform services
together with the AdaptiveStepVarySwitch option setting.
If this option is selected, the eNodeB evaluates the
validity of all CQI adjustment values in a unified manner
and adjusts these adjustment values based on the
evaluation results. If this option and the
AdaptiveStepVarySwitch option are selected, large-step-
based CQI adjustment is triggered in the scenario where
a long time has elapsed before a UE begins to perform
services. If this option is deselected, the eNodeB does
not evaluate the validity of CQI adjustment values or
adjust these values in a unified manner, and large-step-
based CQI adjustment is not triggered in the scenario
where a long time has elapsed before a UE begins to
perform services.
RptCqiFltInitSwitch: Indicates whether to adjust the initial
filtered value of the reported CQI. If this option is
selected, the initial filtered value of the reported CQI is
determined based on the CQI value reported by the UE,
and the filtering coefficient for the reported CQI in the first
several reporting periods is adjusted. If this option is
deselected, the initial filtered value of CQIs reported by
all UEs is fixed to 4.
UeSigInitCqiModSwitch: Indicates the time when the
reported initial CQI takes effect. If this option is selected,
the reported initial CQI takes effect when the ACK to
MSG4 HARQ retransmission is received or when MSG5
is received. If this option is deselected, the reported CQI
immediately takes effect. This option applies only to LTE
TDD.
CqiFastCompstSwitch: Indicates whether the eNodeB
performs fast CQI compensation for the following UEs:
UEs handed over to cells whose values of PCI modulo 3


conflict with source cells' values of PCI modulo 3,
beamforming UEs in 8T8R cells, and UEs reporting
aperiodic CQIs during network access under a high
CAPS condition. If this option is selected, the eNodeB
identifies these UEs and quickly compensates for the
CQIs of these UEs. If this option is deselected, the
eNodeB does not identify these UEs for CQI
compensation. This option applies only to LTE TDD.
GUI Value Range: CqiAdjAlgoSwitch(CqiAdjAlgoSwitch),
StepVarySwitch(StepVarySwitch),
DlVarIBLERtargetSwitch(DlVarIBLERtargetSwitch),
TddBundlingCqiAdjOptSwitch
(TddBundlingCqiAdjOptSwitch),
TddMultiplexingCqiAdjOptSwitch
(TddMultiplexingCqiAdjOptSwitch),
AdaptiveStepVarySwitch(AdaptiveStepVarySwitch),
DlCqiAdjDeltaOptSwitch(DlCqiAdjDeltaOptSwitch),
DlEnVarIblerTargetSwitch(DlEnVarIblerTargetSwitch),
DlRetxTbsIndexAdjOptSwitch
(DlRetxTbsIndexAdjOptSwitch), CfiConvertOptSwitch
(CfiConvertOptSwitch), BundlingOptThdSwitch
(BundlingOptThdSwitch), DlSpsMcsIncreaseSwitch
(DlSpsMcsIncreaseSwitch), CqiAdjTimeEffSwitch
(CqiAdjTimeEffSwitch), RptCqiFltInitSwitch
(RptCqiFltInitSwitch), UeSigInitCqiModSwitch
(UeSigInitCqiModSwitch), CqiFastCompstSwitch
(CqiFastCompstSwitch)
Unit: None
Actual Value Range: CqiAdjAlgoSwitch, StepVarySwitch,
DlVarIBLERtargetSwitch, TddBundlingCqiAdjOptSwitch,
TddMultiplexingCqiAdjOptSwitch,
AdaptiveStepVarySwitch, DlCqiAdjDeltaOptSwitch,
DlEnVarIblerTargetSwitch,
DlRetxTbsIndexAdjOptSwitch, CfiConvertOptSwitch,
BundlingOptThdSwitch, DlSpsMcsIncreaseSwitch,
CqiAdjTimeEffSwitch, RptCqiFltInitSwitch,
UeSigInitCqiModSwitch, CqiFastCompstSwitch
Default Value: CqiAdjAlgoSwitch:On,
StepVarySwitch:Off, DlVarIBLERtargetSwitch:Off,
TddBundlingCqiAdjOptSwitch:Off,
TddMultiplexingCqiAdjOptSwitch:Off,
AdaptiveStepVarySwitch:Off,
DlCqiAdjDeltaOptSwitch:Off,
DlEnVarIblerTargetSwitch:Off,
DlRetxTbsIndexAdjOptSwitch:On,
CfiConvertOptSwitch:Off, BundlingOptThdSwitch:Off,
DlSpsMcsIncreaseSwitch:Off, CqiAdjTimeEffSwitch:Off,
RptCqiFltInitSwitch:Off, UeSigInitCqiModSwitch:Off,
CqiFastCompstSwitch:Off
PDSCHCfg LocalCellId LST PDSCHCFG None None Meaning: Indicates the local ID of the cell. It uniquely
MOD PDSCHCFG identifies a cell within a BS.
Unit: None
Default Value: None
EuSectorEqmGroup SectorEqmGroupId ADD None None Meaning: Indicates the group ID of the sector devices
EUSECTOREQMGROUP that serve the cell,it uniquely identifies a group of sector
ADD devices within a cell.
EUSECTOREQMID2GROUP
LST GUI Value Range: 0~35
EUSECTOREQMGROUP Unit: None
LST Actual Value Range: 0~35
EUSECTOREQMID2GROUP
MOD
Default Value: None
EUSECTOREQMGROUP
RMV
EUSECTOREQMGROUP
RMV
EUSECTOREQMID2GROUP
eUCellSectorEqm SectorEqmId ADD EUCELLSECTOREQM None None Meaning: Indicates the ID of the sector device that
DSP EURTWP serves the cell,it uniquely identifies a sector device within
LST EUCELLSECTOREQM an eNodeB.
RMV EUCELLSECTOREQM
Unit: None
RST EUCELLRES
DSP INREC Actual Value Range: 0~65535
Default Value: None
CellChPwrCfg LocalCellId LST CELLCHPWRCFG None None Meaning: Indicates the local ID of the cell. It uniquely
MOD CELLCHPWRCFG identifies a cell within a BS.
Unit: None
Default Value: None
CellDlpcPhich LocalCellId LST CELLDLPCPHICH None None Meaning: Indicates the local ID of the cell. It uniquely
MOD CELLDLPCPHICH identifies a cell within a BS.
Unit: None
Default Value: None


CellAlgoSwitch LocalCellId DSP None None Meaning: Indicates the local ID of the cell. It uniquely
CELLULCAMCCLUSTER identifies a cell within a BS.
DSP CELLULICSSTATUS
LST CELLALGOSWITCH
MOD CELLALGOSWITCH Unit: None
Default Value: None
CellDlpcPdcch LocalCellId LST CELLDLPCPDCCH None None Meaning: Indicates the local ID of the cell. It uniquely
MOD CELLDLPCPDCCH identifies a cell within a BS.
Unit: None
Default Value: None
CellDlpcPdschPa LocalCellId LST CELLDLPCPDSCHPA None None Meaning: Indicates the local ID of the cell. It uniquely
MOD CELLDLPCPDSCHPA identifies a cell within a BS.
Unit: None
Default Value: None
CellDlpcPdsch LocalCellId LST CELLDLPCPDSCH None None Meaning: Indicates the local ID of the cell. It uniquely
MOD CELLDLPCPDSCH identifies a cell within a BS.
Unit: None
Default Value: None
RACHCfg LocalCellId DSP RACHCFG None None Meaning: Indicates the local ID of the cell. It uniquely
LST RACHCFG identifies a cell within a BS.
MOD RACHCFG GUI Value Range: 0~255
Unit: None
Default Value: None
CellUlpcComm LocalCellId LST CELLULPCCOMM None None Meaning: Indicates the local ID of the cell. It uniquely
MOD CELLULPCCOMM identifies a cell within a BS.
Unit: None
Default Value: None
CellUlpcDedic LocalCellId LST CELLULPCDEDIC None None Meaning: Indicates the local ID of the cell. It uniquely
MOD CELLULPCDEDIC identifies a cell within a BS.
Unit: None
Default Value: None
CellPcAlgo LocalCellId LST CELLPCALGO None None Meaning: Indicates the local cell ID. It uniquely identifies
MOD CELLPCALGO a cell within an eNodeB.
Unit: None
Default Value: None
CellCqiAdaptiveCfg SimulAckNackAndCqiSwitch MOD LBFD-001006 / AMC Meaning: Indicates whether CQI and ACK/NACK can be
CELLCQIADAPTIVECFG TDLBFD-001006 simultaneously sent on the PUCCH. For details, see the
CQI
LST contents related to PUCCH formats in 3GPP TS 36.213.
CELLCQIADAPTIVECFG LOFD- Adjustment
00101501 / Enhanced If this parameter is set to OFF, the value of
TDLOFD- Scheduling simultaneousAckNackAndCQI becomes False. In this
00101501 case, CQI and ACK/NACK cannot be simultaneously
Physical
TDLOFD-001015 sent on the PUCCH. If this parameter is set to ON, the
Channel
UE enters the DRX state, and the cqi-Mask IE value is
LBFD-002003 / Management
setup, the value of simultaneousAckNackAndCQI
TDLBFD-002003
becomes True. In this case, CQI and ACK/NACK can be
simultaneously sent on the PUCCH.
Unit: None
9 Counters
Table 9-1 Counters
1526727396 L.ChMeas.CQI.DL.0 Number of wideband CQI Multi-mode: None Dynamic Downlink Power
reports with the value of 0 GSM: None Allocation
UMTS: None Dynamic Scheduling
Allocation


LOFD-00101502 Dynamic Scheduling
TDLBFD-002016
TDLOFD-00101502
LOFD-00101502 Allocation
TDLBFD-002016 Dynamic Scheduling
TDLOFD-00101502
TDLOFD-00101502
TDLOFD-00101502
TDLOFD-00101502
TDLOFD-00101502
TDLOFD-00101502
TDLOFD-00101502
TDLOFD-00101502
TDLOFD-00101502
TDLOFD-00101502
1526727407 L.ChMeas.CQI.DL.11 Multi-mode: None


Number of wideband CQI GSM: None Dynamic Downlink Power
reports with the value of 11 UMTS: None Allocation
LTE: LBFD-002016 Dynamic Scheduling
LOFD-00101502 Dynamic Downlink Power
TDLBFD-002016 Allocation
TDLOFD-00101502 Dynamic Scheduling
TDLOFD-00101502
TDLOFD-00101502
TDLOFD-00101502
TDLOFD-00101502
1526728259 L.Thrp.bits.UL Total uplink traffic volume Multi-mode: None Radio Bearer Management
for PDCP PDUs in a cell GSM: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
uplink PDCP PDUs in a cell GSM: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526729292 L.ChMeas.CCE.DLUsed.DRB Number of PDCCH CCEs Multi-mode: None Physical Channel

downlink data in a cell UMTS: None Dynamic Downlink Power
Allocation
TDLBFD-002016
1526729293 L.ChMeas.CCE.DLUsed.SRB Number of PDCCH CCEs Multi-mode: None Physical Channel

downlink signaling in a cell UMTS: None Dynamic Downlink Power
Allocation
TDLBFD-002016
1526729294 L.ChMeas.CCE.DLUsed.MCE Number of PDCCH CCEs Multi-mode: None Physical Channel

downlink MCEs in a cell UMTS: None Dynamic Downlink Power
Allocation
TDLBFD-002016
1526729295 L.ChMeas.CCE.ULUsed.Equivalent Number of PDCCH CCEs Multi-mode: None Physical Channel

power used for uplink DCI Allocation
LTE: LBFD-002003
Allocation
TDLBFD-002016
1526729296 L.ChMeas.CCE.DLUsed.Equivalent Number of PDCCH CCEs Multi-mode: None Physical Channel



power used for downlink LTE: LBFD-002003 Allocation
DCI LBFD-002016 Dynamic Downlink Power
1526729319 L.ChMeas.CQI.DL.SingleCW.Periodic.0 Number of periodic Multi-mode: None Dynamic Downlink Power

wideband CQI reports with GSM: None Allocation
the value of 0 in single- UMTS: None Dynamic Scheduling
codeword transmission Dynamic Downlink Power
LTE: LBFD-002016
TDLOFD-00101502

LTE: LBFD-002016
TDLOFD-00101502

LTE: LBFD-002016
TDLOFD-00101502

LTE: LBFD-002016
TDLOFD-00101502

LTE: LBFD-002016
TDLOFD-00101502

LTE: LBFD-002016
TDLOFD-00101502

LTE: LBFD-002016
TDLOFD-00101502

LTE: LBFD-002016
TDLOFD-00101502

LTE: LBFD-002016
TDLOFD-00101502

LTE: LBFD-002016
TDLOFD-00101502


LTE: LBFD-002016
TDLOFD-00101502

LTE: LBFD-002016
TDLOFD-00101502

LTE: LBFD-002016
TDLOFD-00101502

LTE: LBFD-002016
TDLOFD-00101502

LTE: LBFD-002016
TDLOFD-00101502

LTE: LBFD-002016
TDLOFD-00101502
1526729335 L.ChMeas.CQI.DL.SingleCW.Aperiodic.0 Number of aperiodic Multi-mode: None Dynamic Downlink Power

codeword transmission Support of aperiodic CQI
LTE: LBFD-002016
LOFD-00101502 reports
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
Support of aperiodic CQI
TDLBFD-002031
reports

LTE: LBFD-002016
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016


TDLBFD-002031 Support of aperiodic CQI
reports

LTE: LBFD-002016
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016


reports

LTE: LBFD-002016
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports
1526729351 L.ChMeas.CQI.DL.DualCW.Code0.Periodic.0 Number of periodic Multi-mode: None Dynamic Downlink Power

the value of 0 for codeword UMTS: None Dynamic Scheduling
0 in dual-codeword Dynamic Downlink Power
LTE: LBFD-002016
transmission Allocation
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502


TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502



0 in dual-codeword LTE: LBFD-002016 Dynamic Downlink Power
transmission LOFD-00101502 Allocation
TDLOFD-00101502
1526729367 L.ChMeas.CQI.DL.DualCW.Code0.Aperiodic.0 Number of aperiodic Multi-mode: None Dynamic Downlink Power

0 in dual-codeword Support of aperiodic CQI
LTE: LBFD-002016
transmission reports
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502


reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502


reports

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502


LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
TDLOFD-00101502

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502


reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502


reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports

LTE: LBFD-002016
LOFD-00101502
Allocation
TDLBFD-002016
Dynamic Scheduling
TDLOFD-00101502
TDLBFD-002031
reports
PDCP PDUs for UEs whose GSM: None Radio Bearer Management
path loss ranges within [0, UMTS: None Basic Scheduling
90) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
95) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
100) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
path loss ranges within UMTS: None Basic Scheduling
[100, 105) dB


TDLBFD-002025
LBFD-002026
TDLBFD-002026
[105, 110) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
[110, 115) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
[115, 120) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
[120, 125) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
[125, 130) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
[130, 135) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
path loss is greater than or UMTS: None Basic Scheduling
equal to 135 dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
ranges within the range of
[0, 90) dB TDLBFD-002008 Uplink Power Control
TDLBFD-002025
LBFD-002026
TDLBFD-002026


TDLBFD-002025
LBFD-002026
TDLBFD-002026
within [95, 100) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026


for UEs whose path loss TDLBFD-002008 Uplink Power Control
ranges within [130, 135) dB LBFD-002025 Uplink Power Control
TDLBFD-002025
LBFD-002026
TDLBFD-002026
greater than or equal to 135
dB TDLBFD-002008 Uplink Power Control
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026


TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
TDLBFD-002025
LBFD-002026
TDLBFD-002026
dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
1526732808 L.Traffic.User.PL0 Number of UEs that perform Multi-mode: None Radio Bearer Management
services and have a path GSM: None Radio Bearer Management
loss ranging within [0, 90) UMTS: None Basic Scheduling
dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
loss ranging within [100, UMTS: None Basic Scheduling
105) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026


110) dB LTE: LBFD-002008 Basic Scheduling
TDLBFD-002025
LBFD-002026
TDLBFD-002026
115) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
120) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
125) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
130) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
135) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
138) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
1526734045 L.UL.Interference.PUSCH.Index0 Number of times the Multi-mode: None Physical Channel

eNodeB detects a PRB- GSM: None Management
level IN ranging within index UMTS: None Physical Channel
0 on the PUSCH Management
LTE: LBFD-002003
TDLBFD-002003
1526734060 L.UL.Interference.PUSCH.Index15 Number of times the Multi-mode: None Physical Channel

eNodeB detects a PRB- GSM: None Management
level IN ranging within index UMTS: None Physical Channel
LTE: LBFD-002003
TDLBFD-002003
1526734093 L.UL.RSRP.PUSCH.Index0 Number of times the Multi-mode: None Physical Channel

eNodeB detects a UE-level GSM: None Management
RSRP ranging within index UMTS: None Physical Channel
LTE: LBFD-002003


TDLBFD-002003
1526734116 L.UL.RSRP.PUSCH.Index23 Number of times the Multi-mode: None Physical Channel

eNodeB detects a UE-level GSM: None Management
RSRP ranging within index UMTS: None Physical Channel
LTE: LBFD-002003
TDLBFD-002003
1526736735 L.ChMeas.CCE.ULUsed.VoIP Number of PDCCH CCEs Multi-mode: None Physical Channel

used for uplink VoIP GSM: None Management
Allocation
LBFD-002016
TDLBFD-002016
Allocation
1526736736 L.ChMeas.CCE.DLUsed.VoIP Number of PDCCH CCEs Multi-mode: None Physical Channel

used for downlink VoIP GSM: None Management
Allocation
LBFD-002016
TDLBFD-002016
Allocation
1526739662 L.ChMeas.DL.256QAM.CQI.DL.0 Number of wideband CQI Multi-mode: None Dynamic Downlink Power
sent by downlink-256QAM- UMTS: None Basic Scheduling
enabled UEs Dynamic Downlink Power
LTE: LBFD-002016
TDLBFD-002025 DL 256QAM
LEOFD-110301 DL 256QAM
TDLEOFD-110515
LTE: LBFD-002016
TDLEOFD-110515
LTE: LBFD-002016
TDLEOFD-110515
LTE: LBFD-002016
TDLEOFD-110515
LTE: LBFD-002016
TDLEOFD-110515
LTE: LBFD-002016
TDLEOFD-110515


LTE: LBFD-002016
TDLEOFD-110515
LTE: LBFD-002016
TDLEOFD-110515
LTE: LBFD-002016
TDLEOFD-110515
LTE: LBFD-002016
TDLEOFD-110515
LTE: LBFD-002016
TDLEOFD-110515
LTE: LBFD-002016
TDLEOFD-110515
LTE: LBFD-002016
TDLEOFD-110515
LTE: LBFD-002016
TDLEOFD-110515
enabled UEs
LTE: LBFD-002016


TDLEOFD-110515 DL 256QAM
LTE: LBFD-002016
TDLEOFD-110515
[138,141) dB
TDLBFD-002025
LBFD-002026
TDLBFD-002026
[141,144) dB
LBFD-002025 Support of UE Category 1
TDLBFD-002025
LBFD-002026
TDLBFD-002027
[144,147) dB
LBFD-002025 Emergency call
TDLBFD-002025
LBFD-002026
TDLBFD-002028
path loss is greater than or UMTS: None Basic Scheduling
equal to 147 dB
LBFD-002025 Earthquake and Tsunami
TDLBFD-002025 Warning System(ETWS)
LBFD-002026
TDLBFD-002029
LBFD-002025
TDLBFD-002025
LBFD-002026
LBFD-002025 Support of aperiodic CQI
TDLBFD-002025 reports
LBFD-002026
TDLBFD-002031
TDLBFD-002025
LBFD-002026
TDLBFD-002032

dB TDLBFD-002008 Uplink Power Control
LBFD-002025
TDLBFD-002025
LBFD-002026
LBFD-002025
TDLBFD-002025
LBFD-002026
LBFD-002025 Multi Carrier
TDLBFD-002025
LBFD-002026
TDLBFD-002035
LBFD-002025
TDLBFD-002025
LBFD-002026
dB
LBFD-002025
TDLBFD-002025
LBFD-002026
loss ranging between UMTS: None Basic Scheduling
[138,141) dB
LBFD-002025
TDLBFD-002025
LBFD-002026
[141,144) dB
LBFD-002025
TDLBFD-002025
LBFD-002026
[144,147) dB
LBFD-002025
TDLBFD-002025
LBFD-002026
services with a path loss GSM: None Radio Bearer Management
greater than or equal to 147 UMTS: None Basic Scheduling
dB
LBFD-002025
TDLBFD-002025
LBFD-002026

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

2. 3GPP TS 36.331, "Radio Resource Control (RRC); Protocol specification"
3. Physical Channel Resource Management Feature Parameter Description
eRAN
SCTP Congestion Control Feature Parameter Description
Issue 01
Date 2016-03-07

Notice


7 Contents
1.1 Scope
1.3 Change History
2 Overview
3.1 SCTP Congestion Detection
3.2 Back Pressure
3.3 Signaling Congestion Control
4 Related Features
5 Network Impact
6.1 When to Use
6.3 Planning
6.4 Deployment
6.4.1 Requirements
6.4.2 Data Preparation
6.4.3 Precautions
6.4.4 Activation
6.4.7 Deactivation
6.7 Possible Issues
7 Parameters
8 Counters
9 Glossary
Scope
This document describes LBFD-002033 SCTP Congestion Control, including its technical principles, related features, network impact, and engineering guidelines.
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.
eNodeB Type Model
Micro BTS3202E
BTS3203E
BTS3911E
BTS3912E
Intended Audience

Change History
• Feature change
Changes in features and parameters of a specified version
Changes in wording or addition of information and any related parameters affected by editorial changes.
AN11.1 01 (2016-03-07)

AN11.1 Draft A (2015-12-30)
Compared with Issue 01 (2015-03-23) of eRAN8.1, Draft A (2015-12-30) of eRAN11.1 includes no changes.

The BTS3203E does not support any new and enhanced features or functions in eRAN8.1. For details, see 1.3 Change History.
2 Overview
In an LTE system, control plane messages, also referred to as signaling messages, are used to guarantee the proper operation of the evolved universal terrestrial radio access
network (E-UTRAN), including the proper setups, changes, and releases of service connections. Therefore, the reliability of control plane messages is important to the LTE
system. S1 signaling messages between an eNodeB and a mobility management entity (MME) comply with the Stream Control Transmission Protocol (SCTP). An SCTP
association is set up between two SCTP endpoints to achieve connection-based reliable transmission. For details, see the RFC 4960 standard.
If the network load is high, a large number of SCTP messages occupy a large amount of central processing unit (CPU) resources of the main control board such as the universal
main processing and transmission unit (UMPT). If the system becomes congested, it may not be able to process any additional services. To prevent SCTP congestion from
causing exceptions in the SCTP association, eNodeB, and MME, SCTP congestion control is triggered if SCTP resources become insufficient. The congestion control improves
the robustness of signaling processing. SCTP resources include the CPU resources used to process SCTP messages and buffers for SCTP messages waiting to be transmitted.
NOTE:
• An SCTP association is a logical connection set up between two SCTP endpoints. It consists of two SCTP endpoints and protocol status information such as
verification tags and transmission sequence numbers. An SCTP association is identified by the IP addresses and port numbers of the two endpoints. Only one SCTP
association can be set up between two SCTP endpoints.
• In SCTP congestion control performed over the S1 interface, the downlink is from the MME to the eNodeB, and the uplink is from the eNodeB to the MME.
In Huawei's SCTP congestion control solution, SCTP congestion control includes SCTP congestion detection, reverse pressure, and signaling congestion control at the
application layer, and is performed only in the downlink. The eNodeB determines whether SCTP congestion occurs based on the SCTP resource usage. If SCTP congestion
occurs, the eNodeB uses reverse pressure to inform the application layer. The application layer then differentiates signaling processing to reduce the signaling traffic volume,
thereby ensuring reliable transmission. In addition, SCTP congestion control prevents signaling bursts from causing an eNodeB breakdown.
Figure 2-1 illustrates the process of SCTP congestion control. For details, see 3 Technical Description.
Figure 2-1 Process of SCTP congestion control
If the downlink signaling load is heavy, the CPU and SCTP buffer resources become insufficient, thereby affecting services of existing UEs and prohibiting new UEs from
accessing the network. SCTP congestion control uses downlink SCTP congestion detection, back pressure, and signaling congestion control to relieve signaling congestion.
NOTE:
The LMPT and UMPT share the same SCTP congestion control specifications.
SCTP Congestion Detection

SCTP congestion detection determines whether SCTP congestion occurs and whether SCTP congestion is relieved.
If the usage of the main control board CPU processing SCTP messages reaches 85% and the SCTP traffic volume reaches 4550 packets/s, SCTP congestion occurs. If the
CPU usage falls below 85% or the SCTP traffic volume becomes less than 4550 packets/s, SCTP congestion is relieved.
Back Pressure
Back pressure is implemented according to chapter 7 "Congestion Control" in the Network Working Group RFC 4960 Stream Control Transmission Protocol. If the application
layer detects downlink SCTP congestion, the eNodeB uses back pressure to feed back the usage of the buffer for received SCTP messages to the MME.
Signaling Congestion Control
ME
After the eNodeB detects congestion on the SCTP association in the downlink, the eNodeB informs the MME SCTP layer, which then informs the MME S1 application part (S1-
AP). After receiving the congestion information, the MME S1-AP reduces the number of initial S1-AP messages on the SCTP association. The amount of signaling is therefore
reduced at the signaling source.
odeB
If the congestion is still not relieved after the MME performs the signaling congestion control, the eNodeB S1-AP identifies and discards low-priority paging messages.

4 Related Features
erequisite Features
None
None
pacted Features
None
5 Network Impact
stem Capacity
SCTP congestion control prevents signaling bursts from affecting eNodeB operations and helps to maintain the system capacity.
twork Performance
SCTP congestion control prevents system breakdowns when signaling bursts occur.
When to Use
SCTP congestion control is a basic feature and is used by default to improve eNodeB stability.
N/A
Planning
N/A
Deployment
6.4.1 Requirements
None

None
6.4.3 Precautions
None
6.4.4 Activation
None

None
None
6.4.7 Deactivation
None
The counter listed in the following table is used to measure the number of times downlink SCTP congestion control is triggered. The counter increases by 1 each time downlink
SCTP congestion control is triggered. The counter value is cleared when the eNodeB resets.
Counter ID Counter Name Description
1526729664 L.DLSctpCong.Num Number of times downlink SCTP congestion control is triggered
N/A
Possible Issues
N/A
7 Parameters

There are no specific parameters associated with this feature.
8 Counters
Table 8-1 Counters
1526729664 L.DLSctpCong.Num Number of times of downlink Multi-mode: None SCTP Congestion Control
SCTP congestion control GSM: None
UMTS: None
LTE: LBFD-002033
9 Glossary
1. RFC 4960 Stream Control Transmission Protocol
eRAN
Terminal Awareness Differentiation Feature Parameter
Description
Issue 4
Date 2016-11-01


Notice

8 Contents
1.1 Scope
1.3 Change History
2 Overview
2.1 Introduction
2.2 Benefits
2.3 Architecture
3.1 IMEISV-based Terminal Identification
3.1.1 IMEISV
3.1.2 Terminal Awareness Differentiation Procedure
3.1.3 Huawei Equipment Recognition
3.1.4 IMEISV Reception and Transfer at eNodeBs
3.2 UE-Capability-based Terminal Identification
3.2.1 UE Capability Information
3.2.3 Obtaining and Transferring UE Capability Information
3.3 Differentiated Handling on UEs
4 Related Features
5 Network Impact
6.1 When to Use
6.3 Planning
6.4 Deployment
6.4.1 Process
6.4.2 Requirements
6.4.3 Precautions
6.4.7 Deactivation
6.7 Possible Issues
7 Parameters
8 Counters
9 Glossary

Scope
This document describes LBFD-081103 Terminal Awareness Differentiation, including its technical principles, related features, network impact, and engineering guidelines.
eNodeB Type Model
Micro BTS3202E
BTS3203E
BTS3911E
BTS3912E
Intended Audience

Change History
• Feature change
AN11.1 04 (2016-11-01)
Feature change Added the impacts of terminal awareness differentiation on other None N/A
features and functions in 3.3 Differentiated Handling on UEs.
Added differentiated handling for defective UEs in 4T4R cells. For Activated the following parameters: N/A
details, see: • eNBCellRsvdPara.RsvdU16Para7
• 3.3 Differentiated Handling on UEs • RsvdSwPara0_bit1 of the
• 4 Related Features UECOMPATRSVDPARA.RsvdSwPara0
• 6.4.5.1 Data Preparation parameter
Editorial change Revised the descriptions in 6.4.5.2 Using MML Commands. None N/A
AN11.1 03 (2016-06-30)
Editorial change Revised descriptions throughout this document. None N/A
AN11.1 02 (2016-04-30)
Editorial change Revised the descriptions of data preparation, activation, and deactivation in None N/A
AN11.1 01 (2016-03-07)
AN11.1 Draft A (2015-12-30)
Feature change Added the support for UE-capability-based terminal awareness Added the following parameters: Macro, micro,
differentiation. For details, see: • UeCompat.Index and LampSite
• 2.3 Architecture eNodeBs
• UeCompat.UeInfoType
• 3.2 UE-Capability-based Terminal Identification • ABLMSG.UeCapIndex
• 3.3 Differentiated Handling on UEs • UeInfo.Fgi
• 6.2 Required Information • UeInfo.FgiR9
• 6.4.1 Process • UeInfo.FgiR10
• 6.4.2 Requirements • UeInfo.AccessStratumRelease
• 6.4.3 Precautions • UeInfo.UeCategory
• 6.4.5.1 Data Preparation • UeInfo.UeCategoryDlR12
• 6.4.5.2 Using MML Commands • UeInfo.UeCategoryUlR12
• 6.4.5.3 MML Command Examples • UeInfo.FgiR9Add
• 6.4.6 Activation Observation • UeInfo.EutranBandList1
• 6.4.8 Reconfiguration • UeInfo.EutranBandList2


Added the UeCompatOpt.WhiteLstCtrlSwitch parameter to enable the Added the UeCompatOpt.WhiteLstCtrlSwitch Macro, micro,
terminal whitelist function based on masked IMEISV. For details, see: parameter. and LampSite
• 2 Overview eNodeBs
• 3.3 Differentiated Handling on UEs
• 4 Related Features
• 6.1 When to Use
• 6.4 Deployment
Added the function of disabling DRX for UEs in RRC_CONNECTED Added the DRX_SWITCH_OFF option to the Macro, micro,
mode to the terminal blacklist function for defective UEs. For details, UeCompatOpt.BlkLstCtrlSwitch parameter. and LampSite
see: eNodeBs
• 2 Overview
• 6.1 When to Use
• 6.4 Deployment
Added the description of signaling survival based on masked IMEISV. Added the following parameters: Macro, micro,
For details, see: ABLMSG.ImeisvTac and LampSite
• 2 Overview ABLMSG.ImeisvSvn eNodeBs
• 3.3 Differentiated Handling on UEs ABLMSG.ImeisvDesc
• 4 Related Features ABLMSG.RuleIndex
• 6.1 When to Use ABLMSG.RuleCfgType
• 6.4 Deployment
Added IOS trace and IFTS trace based on masked IMEISV. For None Macro, micro,
details, see: and LampSite
• 2 Overview eNodeBs
• 6.1 When to Use
• 6.4 Deployment
Enhanced the terminal blacklist function by adding the function of Added the following switches to the Macro, micro,
disabling inter-frequency and inter-RAT measurements of the UeCompatOpt.BlkLstCtrlSwitch parameter: and LampSite
strongest cell in the measurement period for defective UEs, which are • OSS_INTER_RAT_MR_SWITH_OFF eNodeBs
triggered by OSS subscription. For details, see:
• OSS_INTER_FREQ_MR_SWITH_OFF
• 6.1 When to Use
Editorial change • Revised the descriptions of CME-based feature None N/A

configuration in engineering guidelines.
• Revised other descriptions throughout this document.

2 Overview
Introduction
Terminal compatibility issues arise when the number of terminals (that is, UEs) on LTE networks rapidly increases. The Terminal Awareness Differentiation feature is introduced
to mitigate the impact of such issues. This feature includes the following functions:
• Blacklist control
It is conceivable that certain UEs on live networks may have software or hardware defects. These UEs can have a negative impact on network key performance
indicators (KPIs), when a function is enabled on the networks. If the function is disabled for a cell, no UE (including normal UEs) served by the cell can use this
function. If the function is still enabled, the network KPIs deteriorate. The negative impact of defective UEs on network KPIs cannot be eliminated while ensuring that
the function works properly on normal UEs. To resolve this issue, defective UEs can be blacklisted to prevent the function from being enabled for them.
NOTE:
A defective UE is a UE that supports a function, but due to its own software or hardware defect, does not work properly with the function.
• Whitelist control
To enable a certain function for a specified type of UEs, the UEs can be whitelisted so that differentiated handling takes effect on them.
• Signaling survival
If a type of UE is not compatible with an information element (IE) in Uu messages, an eNodeB can use this function to modify the IE to avoid the incompatibility.
• Signaling tracing
Signaling tracing can be performed to check whether a type of UE is defective.
Benefits
Terminal Awareness Differentiation resolves various UE compatibility issues and eliminates the adverse impact on network KPIs by preventing defective UEs from triggering
abnormal procedures or by taking special measures on specified UEs.
Architecture

Figure 2-1 illustrates the network architecture in which the Terminal Awareness Differentiation feature works.
Figure 2-1 Network architecture
Table 2-1 describes the functions of each element involved in the Terminal Awareness Differentiation feature.
Table 2-1 Functions of each element
Element Function
U2000 Is used to configure feature-related parameters for eNodeBs.
UE Reports its international mobile station equipment identity and software version (IMEISV) or terminal capability information to
a mobility management entity (MME).
MME Interprets the information reported by a UE to identify the IMEISV or UE capability, and sends the IMEISV or UE capability
information to the associated eNodeB.
eNodeB Receives terminal capability information, and then determines whether the UE is the target UE. If it is the target UE, the
eNodeB applies a differentiated handling policy to the UE. Otherwise, the eNodeB does not perform differentiated handling
on the UE.
This chapter describes the principles of LBFD-081103 Terminal Awareness Differentiation. For engineering guidelines, see 6 Engineering Guidelines.
IMEISV-based Terminal Identification
3.1.1 IMEISV
An IMEISV is used to identify a UE on a network. As defined in section 6.2.2 "Composition of IMEISV" of 3GPP TS 23.003 V12.3.0, an IMEISV is composed of the elements
shown in Figure 3-1.
Figure 3-1 Structure of IMEISV
The elements are described as follows:
• Type Allocation Code (TAC): identifies the type of each UE. Its length is eight decimal digits.
• Serial Number (SNR): is an individual serial number uniquely identifying each UE within each TAC. Its length is six decimal digits.
• Software Version Number (SVN): identifies the software version of the UE. Its length is two decimal digits.
The last four digits of the SNR in the IMEISV that an eNodeB receives from an MME are masked by setting the four digits to FFFF, according to section 9.2.3.38 "Masked
IMEISV" in 3GPP TS 36.413 V12.3.0, to protect user privacy.
TAC identifies a type of UEs, and TAC and SVN can specify a type of UEs with the same software version.

Figure 3-2 illustrates the overall procedure of Terminal Awareness Differentiation.

Figure 3-2 Terminal Awareness Differentiation procedure
1. On the U2000 client, operators run man-machine language (MML) commands to set the IMEISV criteria (TAC or TAC+SVN) for UEs that require differentiated
handling and their differentiated handling policies. The differentiated handling policies are as follows:
2. The MME recognizes that the eNodeB is from Huawei.

3. The MME sends the IMEISV of a UE to the Huawei eNodeB, or the source eNodeB in a handover transfers the IMEISV received from the MME to the target Huawei
eNodeB.
• During initial access, the MME sends an INITIAL CONTEXT SETUP REQUEST message containing the IMEISV.
• During an S1-based handover, the MME sends a HANDOVER REQUEST message containing the IMEISV through the S1 interface to the target
eNodeB.
• During an X2-based handover, the source eNodeB sends a HANDOVER REQUEST message containing the IMEISV through the X2 interface to the
target eNodeB.
4. The eNodeB checks whether the received IMEISV meets the configured IMEISV criteria. It performs differentiated handling on the UE if its IMEISV meets the
criteria.
3.1.3 Huawei Equipment Recognition

The Masked IMEISV information element (IE) is introduced as late as in V12.2.0 of 3GPP TS 36.413 and 36.423, which means that equipment on live networks may not be able
to identify this IE. If a third-party eNodeB does not support this IE, procedure errors may occur. Huawei adds two private S1 messages for Huawei MMEs to differentiate
between Huawei and third-party eNodeBs, aimed at preventing the errors.
As shown in Figure 3-3, an MME and an eNodeB may interact in three ways:
• If a Huawei MME is connected to a Huawei eNodeB, the eNodeB sends a private request message to the MME. The MME interprets the message and determines
that the eNodeB is a Huawei eNodeB. The MME then sends a private response message to the eNodeB. In this case, the MME will send the IMEISV of each UE to
the eNodeB.
• If a Huawei MME is connected to a third-party eNodeB, the eNodeB sends a request message to the MME. The MME interprets the message and determines that
the eNodeB is not from Huawei. In this case, the MME does not send a response message. The parameter settings on the MME determine whether to deliver
IMEISVs to the eNodeB.
• If a third-party MME complies with 3GPP TS 36.413 V12.2.0 and is connected to a Huawei eNodeB, the eNodeB sends a private request message to the MME. The
MME does not send a response message to the eNodeB because it cannot interpret the message. In this case, the third-party MME determines whether to deliver
the IMEISV of each UE to the Huawei eNodeB.
Figure 3-3 Huawei equipment recognition
A Huawei eNodeB starts a 2s timer after it sends a private request message. If the eNodeB does not receive a private response message from the MME within 2 seconds, the
timer expires and the eNodeB sends a second private request message. This process continues until the timer expires for three instances, before the eNodeB considers the
MME to be a third-party MME.
3.1.4 IMEISV Reception and Transfer at eNodeBs

An eNodeB receives the IMEISV of a UE from an MME and may transfer the IMEISV to another eNodeB over the X2 interface.
NOTE:
In Figure 3-4, Figure 3-5, and Figure 3-6, text in blue represents the steps and messages involved in the Terminal Awareness Differentiation feature. Text in black represents other
procedures.
tial Access
During initial access, the MME sends an INITIAL CONTEXT SETUP REQUEST message containing the IMEISV to the eNodeB, as shown in Figure 3-4.

Figure 3-4 Reception of an IMEISV during initial access
-based Handover
During an S1-based handover, the MME sends a HANDOVER REQUEST message containing the IMEISV through the S1 interface to the target eNodeB, as shown in Figure
3-5.
Figure 3-5 Reception of an IMEISV during an S1-based handover
-based Handover
During an X2-based handover, the source eNodeB sends a HANDOVER REQUEST message containing the IMEISV through the X2 interface to the target eNodeB, as shown in
Figure 3-6.
Figure 3-6 Reception of an IMEISV during an X2-based handover

UE-Capability-based Terminal Identification
3.2.1 UE Capability Information

The IE UE-EUTRA-Capability, which is defined in section 6.3.6 "Other information elements of 3GPP TS 36.331", contains UE E-UTRA radio access capability parameters.
Radio access capability parameters vary with UEs. Therefore, UEs can be identified using a combination of radio access capability parameters. This method is recommended
when the MME does not support the delivery of the IE Masked IMEISV.
NOTICE:
It is possible that a normal UE is identified as a defective UE because radio access capability parameters cannot uniquely identify a UE. As a result, terminal awareness
differentiation may be incorrectly performed by the eNodeB on some normal UEs.

Figure 3-7 illustrates the overall procedure for Terminal Awareness Differentiation.
Figure 3-7 Terminal awareness differentiation procedure (based on UE capability)
1. On the U2000, operators run MML commands to set UE capability parameters and differentiated handling policies for UEs that require differentiated handling. The
differentiated handling policies are as follows:
2. The eNodeB obtains UE capability information from UEs in different scenarios.

• During initial UE access, the MME delivers an INITIAL CONTEXT SETUP REQUEST message containing UE capability information to the eNodeB. If the
message does not contain any UE capability information, the eNodeB sends a UE CAPABILITY ENQUIRY message to the UE. Then, the UE sends the
UE CAPABILITY INFORMATION message containing UE capability information to the eNodeB.
• During an S1-based handover, the MME sends a HANDOVER REQUEST message containing UE capability information through the S1 interface to the
target eNodeB.
• During an X2-based handover, the source eNodeB sends a HANDOVER REQUEST message containing UE capability information through the X2
interface to the target eNodeB.
3. The eNodeB checks whether the received UE capability information is consistent with UE capability parameters configured using MML commands.
4. If consistent, the eNodeB performs differentiated handling on the UE.
3.2.3 Obtaining and Transferring UE Capability Information

The eNodeB obtains UE capability information from the MME or UE, and transfers it to other eNodeBs over the X2 interface.
NOTE:
In Figure 3-8, Figure 3-9, and Figure 3-10, text in blue represents the steps and messages involved in terminal awareness differentiation. Text in black represents other procedures.
tial Access
During initial UE access, the MME delivers an INITIAL CONTEXT SETUP REQUEST message conveying UE capability information to the eNodeB. If the message does not
contain any UE capability information, the eNodeB sends a UE CAPABILITY ENQUIRY message to the UE. Then, the UE sends the UE CAPABILITY INFORMATION message
containing UE capability information to the eNodeB.
Figure 3-8 shows the procedure for obtaining UE capability information during initial access.

Figure 3-8 Obtaining UE capability information (during initial access)
-based Handover
During an S1-based handover, the MME sends a HANDOVER REQUEST message conveying UE capability information through the S1 interface to the target eNodeB. Figure
3-9 shows the procedure for obtaining UE capability information during an S1-based handover.
Figure 3-9 Obtaining UE capability information during an S1-based handover
-based Handover
During an X2-based handover, the source eNodeB sends a HANDOVER REQUEST message conveying UE capability information through the X2 interface to the target
eNodeB. Figure 3-10 shows the procedure for obtaining UE capability information during an X2-based handover.

Figure 3-10 Obtaining UE capability information during an X2-based handover
Differentiated Handling on UEs

An eNodeB performs differentiated handling on UEs only when all the following switches are on:
• AbnormalUeHandleSwitch
AbnormalUeHandleSwitch in the GlobalProcSwitch.UeCompatSwitch parameter controls whether the eNodeB performs differentiated handling on specified UEs.
• UeTypeRecogSwitch
The UeCompat.UeInfoType parameter specifies a terminal identification type. Table 3-1 lists the terminal identification types.
Table 3-1 Setting terminal identification types
Terminal Identification Type Parameter Setting Scenario
IMEISV-based The UeCompat.UeInfoType parameter The UeTypeRecogSwitch option of the

can be set to IMEISV_TAC or GlobalProcSwitch.S1MmePrivFeatureInd parameter controls whether the
IMEISV_TAC_SVN. eNodeB requests IMEISVs from the MME. If this option is selected, the
eNodeB checks each received IMEISV to determine whether any IMEISV
meets the IMEISV criteria configured on the U2000.
• If an IMEISV meets the criteria, the eNodeB applies the preset
differentiated handling policies to the UE.
• If the IMEISV does not meet the criteria, the eNodeB does not
perform differentiated handling on the UE.
The eNodeB considers that an IMEISV meets the criteria if either of the
following conditions is fulfilled:
• When UeCompatOpt.ImeisvSvn is not specified, the TAC in the
IMEISV is the same as the value of UeCompatOpt.ImeisvTac.
• When UeCompatOpt.ImeisvSvn is specified, the TAC and SVN in
the IMEISV are the same as the values of UeCompatOpt.ImeisvTac
and UeCompatOpt.ImeisvSvn, respectively.
UE-capability-based The UeCompat.UeInfoType parameter After receiving UE capability information, the eNodeB compares the
is set to UE_CAPABILITY. information with the values of UE capability parameters configured on the
U2000.
• If they match, the eNodeB applies the preset differentiated handling
policies to the UE.
• If they do not match, the eNodeB does not perform differentiated
handling on the UE.
The configured UE capability information comes from a group of parameters in
the UeInfo MO. The eNodeB compares the received UE capability information
with the parameter group. The UE capability information matches only when
they are the same.
After the preceding switches are turned on, the eNodeB applies differentiated handling policies, such as blacklist control, whitelist control, signaling survival, or signaling trace,
as required.
NOTE:
When the eNodeB supports both IMEISV-based and UE capability-based terminal awareness differentiation and the IMEISV and UE capability information about a UE match the
preset parameters, IMEISV-based terminal awareness differentiation is preferentially adopted because it is more accurate for terminal identification.
acklist Control
If a type of UEs needs to be blacklisted on the eNodeB, the options of the UeCompat.BlkLstCtrlSwitch parameter can be selected as required to perform differentiated handling
for the type of UEs.
The blacklist control policies are specific to individual features or functions. The features or functions can be disabled for defective UEs. Table 3-2 provides a detailed description
of the UeCompat.BlkLstCtrlSwitch parameter settings and blacklist control policies.
Table 3-2 Blacklist control policies and their parameter settings
Affected Feature Parameter Setting Policy
LOFD-002001 Automatic The LTE_ANR_SWITCH_OFF option of the The following functions do not take effect on defective UEs:
Neighbour Relation (ANR) UeCompat.BlkLstCtrlSwitch parameter is selected. • Event-triggered intra-RAT ANR (where RAT is short for
radio access technology)
• Fast intra-RAT ANR
• Proactive physical cell identifier (PCI) conflict detection
• ANR based on specified PCI groups
In addition, if the MlbBasedEventAnrSwitch
(MlbBasedEventAnrSwitch) option of the


ENodeBAlgoSwitch.AnrSwitch parameter is selected, event-
triggered ANR based on mobility load balancing (MLB) does not
take effect on defective UEs.
For details, see ANR Management Feature Parameter Description.
LOFD-002002 Inter-RAT • For inter-RAT ANR with UTRAN: The following functions do not take effect on defective UEs:
ANR The UTRAN_ANR_SWITCH_OFF option of the • Event-triggered ANR with UTRAN
UeCompat.BlkLstCtrlSwitch parameter is • Fast ANR with UTRAN
selected. • Event-triggered ANR with GERAN
• For inter-RAT ANR with GERAN: • Fast ANR with GERAN
The GERAN_ANR_SWITCH_OFF option of the • Event-triggered ANR with CDMA2000
UeCompat.BlkLstCtrlSwitch parameter is
• Fast ANR with CDMA2000
selected.
• For inter-RAT ANR with CDMA2000: In addition, if the MlbBasedEventAnrSwitch
(MlbBasedEventAnrSwitch) option of the
The CDMA_ANR_SWITCH_OFF option of the
ENodeBAlgoSwitch.AnrSwitch parameter is selected, event-
UeCompat.BlkLstCtrlSwitch parameter is
triggered ANR based on MLB does not take effect on defective
selected.
UEs.
For details, see ANR Management Feature Parameter Description and LTE-
CDMA2000 ANR Management Feature Parameter Description.
LOFD-00110501 Dynamic The DYNAMIC_DRX_SWITCH_OFF option of the Dynamic discontinuous reception (DRX) does not take effect on
DRX UeCompat.BlkLstCtrlSwitch parameter is selected. defective UEs. For details, see DRX and Signaling Control Feature
LBFD-002017 DRX The DRX_SWITCH_OFF option of the DRX does not take effect on defective UEs. For details, see DRX
UeCompat.BlkLstCtrlSwitch parameter is selected. and Signaling Control Feature Parameter Description.
Features related to carrier The CA_SWITCH_OFF option of the The following functions do not take effect on defective UEs:
aggregation (CA), as UeCompat.BlkLstCtrlSwitch parameter is selected. • Secondary serving cell (SCell) configuration
described in Carrier Aggregation
Feature Parameter Description • Primary component carrier (PCC) anchoring
For details, see Carrier Aggregation Feature Parameter Description.
LOFD-001048 TTI Bundling The TTI_BUNDLING_SWITCH_OFF option of the Transmission time interval (TTI) bundling does not take effect on
UeCompat.BlkLstCtrlSwitch parameter is selected. defective UEs. For details, see Scheduling Feature Parameter
Description.
Features related to multiple- The MIMO_TM_MODE_SET option of the The following functions do not take effect on defective UEs:
input multiple-output (MIMO), UeCompat.BlkLstCtrlSwitch parameter is selected. • CellMimoParaCfg.MimoAdaptiveSwitch is automatically
as described in MIMO Feature set to OL_ADAPTIVE.
Parameter Description
• CellMimoParaCfg.InitialMimoType is automatically set to
ADAPTIVE(ADAPTIVE).
NOTE:
This differentiated handling policy takes effect only when the defective UEs
work in fixed or adaptive closed-loop MIMO mode.
For details, see MIMO Feature Parameter Description.
• LBFD-002031 The APERIODIC_CQI_RPT_SWITCH_OFF option of the Aperiodic CQI reporting does not take effect on defective UEs.
Support of UeCompat.BlkLstCtrlSwitch parameter is selected. For details, see MIMO Feature Parameter Description.
aperiodic CQI
reports
• LBFD-060101
Optimization of
Periodic and
Aperiodic CQI
Reporting
LOFD-001017 RObust The ROHC_SWITCH_OFF option of the Robust header compression (ROHC) does not take effect on
Header Compression UeCompat.BlkLstCtrlSwitch parameter is selected. defective UEs. For details, see ROHC Feature Parameter Description.
(ROHC)
Periodic inter-RAT The OSS_INTER_RAT_MR_SWITH_OFF option of the Periodic inter-RAT measurement for the strongest cell triggered
measurement for the UeCompat.BlkLstCtrlSwitch parameter is selected. by OSS subscription does not take effect on defective UEs.
strongest cell triggered by
OSS subscription
Periodic inter-frequency The OSS_INTER_FREQ_MR_SWITH_OFF option of the Periodic inter-frequency measurement for the strongest cell
measurement for the UeCompat.BlkLstCtrlSwitch parameter is selected. triggered by OSS subscription does not take effect on defective
strongest cell triggered by UEs.
OSS subscription
LOFD-111207 VoLTE Rate The OSS_INTER_FREQ_MR_SWITH_OFF option of the Uplink adaptive multirate control (AMRC) is disabled for defective
Control UeCompat.BlkLstCtrlSwitch parameter is selected. UEs.
Forbidding capabilities The OSS_INTER_FREQ_MR_SWITH_OFF option of the The capabilities beyond the UE protocol version are forbidden for
beyond the UE protocol UeCompat.BlkLstCtrlSwitch parameter is selected. defective UEs.
version
LOFD-001003 DL 4x2 MIMO The RsvdSwPara0_bit1 option of the Defective UEs in 4T cells are redirected to inter-frequency 2T
LOFD-001060 DL 4x4 MIMO UECOMPATRSVDPARA.RsvdSwPara0(LTE FDD cells. After the redirection, the defective UEs are served by the 2T
eNodeB) parameter is selected. The cells.
MOUeCompatEffectSw option of the
GLOBALPROCSWITCH.UeCompatSwitch parameter is
selected. The value of the UECOMPATRSVDPARA.Index
parameter is the same as that of the UECOMPAT.Index
parameter.
hitelist Control
If a type of UEs needs to be whitelisted on the eNodeB, the options of the UeCompat.WhiteLstCtrlSwitch parameter can be selected as required to perform differentiated
handling for the type of UEs.

Through parameter configuration, the eNodeB can determine whether the whitelist control function takes effect on a type of UEs. Table 3-3 provides a detailed description of the
UeCompat.WhiteLstCtrlSwitch parameter settings and whitelist control policies.
Table 3-3 Whitelist control policy and its parameter settings
Downlink rank detection The RANK_DETECT_SWITCH_ON option of the These UEs are whitelisted so that downlink rank detection
UeCompat.WhiteLstCtrlSwitch parameter is selected. takes effect on them.
The prerequisite is that the DetectRank2AdjSwitch option of
the CellDlschAlgo.DlRankDetectSwitch parameter has been
selected.
LOFD-111207 VoLTE Rate The UL_AMRC_SWITCH_ON option of the Uplink AMRC is enabled for whitelisted UEs.
Control UeCompat.WhiteLstCtrlSwitch parameter is selected.
gnaling Survival Control
The ADD ABLMSG command is executed on the eNodeB to perform signaling survival for a specified type of UEs.
After receiving the IMEISV from the MME, the eNodeB compares the IMEISV with information about a UE configured in the ABLMSG MO.
• If ABLMSG.RuleCfgType is set to ALL, signaling survival is performed for all UEs served by the eNodeB.
• If ABLMSG.RuleCfgType is set to IMEISV_TAC, the eNodeB checks whether the TAC of a UE is available in the TACs of the masked IMEISVs. If available, the
eNodeB performs signaling survival for the UE. If not, the eNodeB does not perform signaling survival for the UE.
• If ABLMSG.RuleCfgType is set to IMEISV_TAC_SVN, the eNodeB checks whether the TAC and SVN of a UE are available in the TACs and SVNs of the masked
IMEISVs. If available, the eNodeB performs signaling survival for the UE. If not, the eNodeB does not perform signaling survival for the UE.
• If ABLMSG.RuleCfgType is set to UE_CAPABILITY, the eNodeB compares the UE capability parameter group corresponding to UeCompat.UeCapIndex with the
actual UE capability information. If they match, the eNodeB performs signaling survival for the UE. If they do not match, the eNodeB does not perform signaling
survival for the UE.
gnaling Trace
• IMEISV-based standard signaling trace

When starting an intelligent optimization system (IOS) trace on the U2000, operators can configure TAC or both TAC and SVN in the trace window. After receiving a
trace task from the U2000, the eNodeB compares the settings in the trace task with information about camped UEs. If only TAC is set in the trace task, the eNodeB
compares only the TAC in IMEISV. If both TAC and SVN are set, the eNodeB compares the TAC and SVN in IMEISV.
◾ During the initial RRC connection setup, the eNodeB obtains the Masked IMEISV IE from the S1AP_INITIAL CONTEXT SETUP REQUEST messages
sent by the MME and then matches the settings in the trace task.
◾ During the incoming S1 handover, the target eNodeB obtains the Masked IMEISV IE from the S1AP_HANDOVER REQUEST messages sent by the MME
and then matches the settings in the trace task.
◾ During the incoming X2 handover, the target eNodeB obtains the Masked IMEISV IE from the X2AP_HANDOVER REQUEST messages sent by the
source eNodeB and then matches the settings in the trace task.
◾ During the RRC reestablishment or intra-eNodeB incoming handover (such as inter-cell incoming handover), the eNodeB matches the stored IMEISVs of
connected UEs with the settings in the trace task.
If a UE matches the settings in the trace task, the eNodeB reports the standard signaling data generated by the UE to the U2000.
IOS trace can collect the signaling data of a maximum of 50 UEs simultaneously in each cell. If a UE is released or handed over to another cell, the eNodeB will
select a newly connected UE to match data.
• IMEISV-based TTI data trace
When starting an IFTS trace on the U2000 or Web LMT, operators can configure TAC or both TAC and SVN in the trace window.
If a UE matches the IMEISV in the trace task, the eNodeB reports the TTI data generated later by the UE to the U2000. IFTS trace can collect the signaling data of
only one UE in each cell at a time. If a UE is released or handed over to another cell, the eNodeB will select a newly connected UE to match data.
• UE-capability-based standard signaling trace

When starting an IOS trace on the U2000, operators can set a UE capability index in the trace window. After receiving a trace task from the U2000, the eNodeB
compares the settings in the trace task with information about camped UEs.
◾ During the initial RRC connection setup, the eNodeB obtains UE capability information from the INITIAL CONTEXT SETUP REQUEST message
delivered by the MME or from the UE CAPABILITY INFORMATION message sent by the UE. Then, the eNodeB compares the received UE capability
information with the settings in the trace task.
◾ During the incoming S1 handover, the target eNodeB obtains UE capability information from the HANDOVER REQUEST message delivered by the MME
and then matches the settings in the trace task.
◾ During the incoming X2 handover, the target eNodeB obtains UE capability information from the HANDOVER REQUEST message sent by the source
eNodeB and then matches the settings in the trace task.
◾ During the RRC reestablishment or intra-eNodeB incoming handover (such as inter-cell incoming handover), the eNodeB matches the stored UE
capability information about a connected UE with the settings in the trace task.
If a UE matches the settings in the trace task, the eNodeB reports the standard signaling data generated by the UE to the U2000.
IOS trace can collect the signaling data of a maximum of 50 UEs simultaneously in each cell. If a UE is released or handed over to another cell, the eNodeB will
select a newly connected UE to match data.
• UE-capability-based TTI data trace
When starting an IFTS trace on the U2000 or Web LMT, operators can set a UE capability index in the trace window.
If a UE matches the UE capability in the trace task, the eNodeB reports the TTI data generated by the UE to the U2000. IFTS trace can collect the data of only one
UE in each cell at a time. If a UE is released or handed over to another cell, the eNodeB will select a newly connected UE to match UE capability information.
4 Related Features
erequisite Features
None
None
pacted Features
Feature ID Feature/Function Name Impact Description

Feature ID Feature/Function Name Impact Description

LOFD-002001 Automatic Neighbour Relation (ANR) After the terminal blacklist function of LBFD-081103 Terminal
Awareness Differentiation is enabled, measurements for intra-RAT
ANR or proactive PCI conflict detection can be disabled for
specified defective UEs.
LOFD-002002 Inter-RAT ANR After the terminal blacklist function of LBFD-081103 Terminal
Awareness Differentiation is enabled, measurements for intra-RAT
ANR can be disabled for specified defective UEs.
LOFD-001105 Dynamic DRX After the terminal blacklist function of LBFD-081103 Terminal
Awareness Differentiation is enabled, dynamic DRX can be
disabled for specified defective UEs.
LBFD-002017 DRX After the terminal blacklist function of LBFD-081103 Terminal

Awareness Differentiation is enabled, DRX for UEs in connected
mode can be disabled for specified defective UEs.
LOFD-001048 TTI Bundling After the terminal blacklist function of LBFD-081103 Terminal
Awareness Differentiation is enabled, TTI Bundling can be disabled
for specified defective UEs.
LOFD-001017 RObust Header Compression (ROHC) After the terminal blacklist function of LBFD-081103 Terminal
Awareness Differentiation is enabled, ROHC can be disabled for
specified defective UEs.
N/A Carrier Aggregation After the terminal blacklist function of LBFD-081103 Terminal
Awareness Differentiation is enabled, the impact on the CA
features is that the eNodeB does not configure SCells or perform
PCC anchoring for specified defective UEs.
LOFD-001001 DL 2x2 MIMO After the terminal blacklist function of LBFD-081103 Terminal
Awareness Differentiation is enabled, the impact on the MIMO
LOFD-001003 DL 4x2 MIMO features is that specified defective UEs cannot enter closed-loop
MIMO mode.
LBFD-002031 Support of aperiodic CQI reports After the terminal blacklist function of LBFD-081103 Terminal
Awareness Differentiation is enabled, Enhanced Aperiodic CQI
LBFD-060101 Optimization of Periodic and Aperiodic CQI Reporting can be disabled for specified defective UEs.
Reporting
LBFD-002025 Basic Scheduling After the terminal whitelist function of LBFD-081103 Terminal
Awareness Differentiation is enabled, the accuracy of rank
LOFD-00101502 Dynamic Scheduling reporting is affected.
LOFD-001003 DL 4x2 MIMO Specified defective UEs in 4T cells can be redirected to inter-
frequency 2T cells through configuration after blacklist control in
LOFD-001060 DL 4x4 MIMO the LBFD-081103 Terminal Awareness Differentiation feature takes
effect.
NOTE:
• This function applies to the scenario where a 4T4R cell using a high
frequency and a 2T2R cell using a low frequency cover the same
area.
5
• This function does not take effect when frequency-priority-based
inter-frequency handover is enabled.
Network Impact
stem Capacity
After the blacklist control function in the LBFD-081103 Terminal Awareness Differentiation feature takes effect, blacklisted UEs are excluded from the application range of the
feature, increasing cell throughput.
After the whitelist control function in the LBFD-081103 Terminal Awareness Differentiation feature takes effect, the eNodeB performs downlink rank detection for whitelisted
UEs, increasing the downlink UE throughput in the event of inaccurate rank indication (RI) reports. However, when these UEs report RIs accurately, this function may slightly
decrease the downlink throughput. The number of rank detections and the channel quality determine how much the downlink throughput of a single UE is affected.
twork Performance
This feature prevents or reduces network risks caused by UE incompatibility, such as service drops and RRC connection reestablishment.
This chapter provides engineering guidelines for LBFD-081103 Terminal Awareness Differentiation.
When to Use
Use the terminal blacklist function of this feature when certain UEs on your network do not work properly with any of the following functions:
• Intra-RAT ANR
• Inter-RAT ANR
• Dynamic DRX
• DRX in RRC_CONNECTED mode
• CA
• TTI bundling
• Closed-loop MIMO

• Aperiodic CQI reporting

• ROHC
• Periodic inter-frequency measurement for the strongest cell triggered by OSS subscription
• Periodic inter-RAT measurement for the strongest cell triggered by OSS subscription
Use the terminal whitelist function of this feature when UEs on the network report inaccurate rank detection results.
The application scenarios of signaling survival and signaling trace in this feature are not specified.
Before deploying this feature, collect the defective UE lists for specified functions and analyze the percentages of such UEs in the network. In addition, you can collect call
history records (CHRs) and the results of signaling tracing over interfaces to determine whether there are other defective UEs. In CHRs, the Publicinfo event block contains the
ulTac and ucSvn fields, which correspond to the TAC and SVN of IMEISV, respectively. The UeCapInfo event block contains the Fgi, UeCategory, and AccessStratumRelease
fields, which correspond to the fields in UE capability information and help locate UE compatibility problems.
NOTE:
To enable an eNodeB to obtain the IMEISV of a UE, ensure that the EPC is capable of obtaining the IMEISV and delivering it to the eNodeB.
Planning
F Planning
N/A
twork Planning
N/A
rdware Planning
N/A
Deployment
6.4.1 Process
The feature deployment process is as follows:
1. For IMEISV-based terminal awareness differentiation, turn on the IMEISV-related switch on MMEs so that they can interpret the IMEISVs of UEs.
2. On eNodeBs, set feature-related parameters.
a. Select the UeTypeRecogSwitch option of the S1 MME Private Feature Indicator parameter. This step is required only when the MME is provided by
Huawei and the MME delivers IMEISVs only to Huawei eNodeBs.
b. Select the AbnormalUeHandleSwitch option of the Ue Compatibility Switch parameter.
c. Select a differentiated handling policy, which can be blacklist control, whitelist control, signaling survival, or signaling tracing.
d. If blacklist control or whitelist control is selected, specify IMEISV information or UE capability information and the related compatibility handling
measures. If signaling survival is selected, specify a rule configuration type and set IMEISV information or UE capability information. If signaling tracing
is selected, set IMEISV information or UE capability information.
6.4.2 Requirements
N/A
N/A
cense
N/A
hers
• UE
If IMEISV-based terminal awareness differentiation is adopted, UEs must be capable of reporting IMEISV.
• Core network
If IMEISV-based terminal awareness differentiation is adopted, the MME must be capable of delivering IMEISV.
If the MME is provided by Huawei, it must support USN9810 V900R014C10 or later. If the MME is provided by another vendor, it must comply with 3GPP TS 36.413
V12.2.0.
• Transmission equipment
None
• Third-party network equipment

None
6.4.3 Precautions
After blacklist or whitelist control is enabled, any UEs can be configured as defective UEs. A maximum of 128 UE models or eight UE categories with different UE capability
information can be configured on each eNodeB.

N/A

This section describes the data that you need to collect for setting parameters. 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.
• User-defined: parameter values set by users
quired Data

• IMEISV-based terminal identification
The following table describes the parameters that must be set in the GlobalProcSwitch MO.
S1 MME Private GlobalProcSwitch. Radio planning The UeTypeRecogSwitch option of this parameter controls whether to allow the
Feature Indicator S1MmePrivFeatureInd (negotiation with the eNodeB to obtain the IMEISV information of UEs from the MME. Each IMEISV that
peer) an eNodeB receives from an MME has been masked by setting the last 4 digits of
the SNR in the IMEISV to FFFF.
• If this option is selected, the eNodeB requests IMEISVs from MMEs.
• If this option is deselected, the eNodeB does not request IMEISVs from
MMEs.
NOTE:
After this option is selected, only the UEs that newly access or are handed over to the eNodeB
report their IMEISVs. The switch setting does not affect existing UEs on the network.
Ue Compatibility GlobalProcSwitch. Default/recommended The AbnormalUeHandleSwitch option of this parameter specifies whether to
Switch UeCompatSwitch value enable handling of abnormal UEs.
• If this option is selected, the eNodeB performs differentiated handling
on specified UEs.
• If this option is deselected, the eNodeB does not perform differentiated
handling on specified UEs.
The MOUeCompatEffectSw option of the parameter determines whether the
UeCompat MO takes effect.
• If the option is selected, the UeCompat MO takes effect but the
UeCompatOpt MO does not take effect.
• If the option is deselected, the UeCompat MO does not take effect but
the UeCompatOpt MO takes effect.
• UE-capability-based terminal identification
The following table describes the parameters that must be set in the GlobalProcSwitch MO.
Ue Compatibility GlobalProcSwitch. Default/recommended The AbnormalUeHandleSwitch option of this parameter specifies whether to
Switch UeCompatSwitch value enable handling of abnormal UEs.
• If this option is selected, the eNodeB performs differentiated handling
on specified UEs.
• If this option is deselected, the eNodeB does not perform differentiated
handling on specified UEs.
The MOUeCompatEffectSw option of the parameter determines whether the
• If the option is selected, the UeCompat MO takes effect but the
UeCompatOpt MO does not take effect.
• If the option is deselected, the UeCompat MO does not take effect but
the UeCompatOpt MO takes effect.
The UeInfo MO contains parameters related to UE information. The following table describes the key parameters.
Feature Group UeInfo.Fgi Radio planning This parameter indicates the FGIs of Release 8 or earlier, which correspond to
Indicator (internal planning) the bit string in the field featureGroupIndicators in the IE UE-EUTRA-Capability in
3GPP TS 36.331.
• If this parameter is set to 0, it is not used for matching terminal
information.
• If this parameter is not set to 0, its value must be consistent with UE
capability information for matching terminal information.
Feature Group UeInfo.FgiR9 Radio planning This parameter indicates the Release 9 FGIs supported by defective UEs, which
Indicator Release 9 (internal planning) correspond to the bit string in the field featureGroupIndicators-r9 in the IE fdd-
Add-UE-EUTRA-Capabilities-r9 or tdd-Add-UE-EUTRA-Capabilities-r9 defined in
3GPP TS 36.331. A UE matches the UE type when the parameter value matches
the field in any of the IEs.
information.
Feature Group UeInfo.FgiR10 Radio planning This parameter indicates the Release 10 FGIs supported by defective UEs, which
Indicator Release 10 (internal planning) correspond to the bit string in the field featureGroupIndRel10-r10 in the IE UE-
EUTRA-Capability-v1020-IEs, fdd-Add-UE-EUTRA-Capabilities-v1060, or tdd-
Add-UE-EUTRA-Capabilities-v1060 defined in 3GPP TS 36.331. A UE matches
the UE type when the parameter value matches the field in any of the IEs.
information.
Access Stratum UeInfo.AccessStratumRelease Radio planning This parameter indicates the access stratum capability supported by defective
Release (internal planning) UEs, which corresponds to the field AccessStratumRelease in the information
element (IE) UE-EUTRA-Capability defined in 3GPP TS 36.331.
information.


UE Category UeInfo.UeCategory Radio planning This parameter indicates the UE categories supported by defective UEs, which
(internal planning) correspond to the fields ue-Category, ue-Category-v1020, ue-Category-v1170,
and ue-Category-v11a0 in the IE UE-EUTRA-Capability defined in 3GPP TS
36.331.
information.
UE Category DL UeInfo.UeCategoryDlR12 Radio planning This parameter indicates the UE category supported by defective UEs, which
Release12 (internal planning) corresponds to the field ue-CategoryDL-r12 in the IE UE-EUTRA-Capability
defined in 3GPP TS 36.331.
information.
UE Category UL UeInfo.UeCategoryUlR12 Radio planning This parameter indicates the UE category supported by defective UEs, which
Release12 (internal planning) corresponds to the field ue-CategoryUL-r12 in the IE UE-EUTRA-Capability
information.
Feature Group UeInfo.FgiR9Add Radio planning This parameter indicates the Release-9-additional FGIs supported by defective
Indicator Release 9 (internal planning) UEs, which correspond to the bit string in the field featureGroupIndRel9Add-r9 in
Add the IE UE-EUTRA-Capability-v9a0-IEs, fdd-Add-UE-EUTRA-Capabilities-r9, or
tdd-Add-UE-EUTRA-Capabilities-r9 as defined in 3GPP TS 36.331. A UE
matches the UE type when the parameter value matches the field in any of the
IEs.
information.
E-UTRAN Band List UeInfo.EutranBandList1 Radio planning This parameter indicates the E-UTRA band list 1, which corresponds to the fields
1 (internal planning) bandEUTRA in the IE SupportedBandListEUTRA in 3GPP TS 36.331.
information.
E-UTRAN Band List UeInfo.EutranBandList2 Radio planning This parameter indicates the E-UTRA band list 2, which corresponds to the fields
2 (internal planning) bandEUTRA in the information element (IE) SupportedBandListEUTRA in 3GPP
TS 36.331.
information.
• Configuring blacklist control and whitelist control

This table describes the parameters that must be set in the UeCompat MO to configure blacklist control and whitelist control.
Index UeCompat.Index Radio planning This parameter indicates the index of a UE compatibility processing action.
(internal planning)
UE Information UeCompat.UeInfoType Radio planning This parameter specifies the information type of a UE.
Type (internal planning) • If this parameter is set to IMEISV_TAC, UeCompat.ImeisvTac
must be configured.
• If this parameter is set to IMEISV_TAC_SVN, UeCompat.
ImeisvTac and UeCompat.ImeisvSvn must be configured.
• If this parameter is set to UE_CAPABILITY,
UeCompat.UeCapIndex must be configured.
Imeisv Tac UeCompat.ImeisvTac Radio planning This parameter indicates the type allocation code (TAC) in the IMEISVs of
(internal planning) UEs. Each TAC identifies a UE model.
This parameter must be configured when UeCompat.UeInfoType is set to
IMEISV_TAC or IMEISV_TAC_SVN.
Imeisv Svn UeCompat.ImeisvSvn Radio planning This parameter indicates the software version number (SVN) in the
(internal planning) IMEISVs of UEs. Each SVN identifies a software version of UEs.
This parameter must be configured when UeCompat.UeInfoType is set to
IMEISV_TAC_SVN.
UE Capability UeCompat.UeCapIndex Radio planning This parameter specifies the index of a UE capability.
Index (internal planning) This parameter must be configured when UeCompat.UeInfoType is set to
UE_CAPABILITY.
The value of this parameter comes from UeInfo.UeCapIndex. The
ABLMSG.UeCapIndex parameter must be set before this parameter is
configured.
Black List Control UeCompat.BlkLstCtrlSwitch Radio planning This parameter indicates whether to blacklist some features. Set this
Switch (internal planning) parameter based on site conditions.
If the option of this parameter is selected, the specified UEs are blacklisted
to disable the associated feature or function.

Ue Type UeCompat.UeTypeDesc Radio planning This parameter indicates the user-defined description of UEs.
Description (internal planning)
White List Control UeCompat.WhiteLstCtrlSwitch Radio planning This parameter indicates whether to whitelist some features. Set this
Switch (internal planning) parameter based on site conditions.
• Configuring signaling survival

The following table describes the parameters that must be set in the ABLMSG MO to configure signaling survival.
Interface Protocol ABLMSG.MsgItfType Radio planning This parameter indicates the interface protocol type of the debugging
Name (internal planning) message.
Message Type ABLMSG.MsgType Radio planning This parameter specifies the number of the message transmitted over 3GPP-
(internal planning) defined interfaces.
IMEISV TAC ABLMSG.ImeisvTac Radio planning This parameter indicates the type allocation code (TAC) in the IMEISVs of
(internal planning) UEs. Each TAC identifies a UE model.
IMEISV SVN ABLMSG.ImeisvSvn Radio planning This parameter indicates the software version number (SVN) in the IMEISVs
(internal planning) of UEs. Each SVN identifies a software version of UEs.
IMEISV Description ABLMSG.ImeisvDesc Engineering design This parameter indicates the user-defined description of the UE type.
Rule Index ABLMSG.RuleIndex Engineering design This parameter indicates the index of a rule for a debugging message.
Different messages may have the same rule index.
Rule Configuration ABLMSG.RuleCfgType Radio planning This parameter specifies a rule configuration type.
Type (internal planning) • If this parameter is set to ALL, the rule configuration type is applied
to all UEs.
• If this parameter is set to IMEISV_TAC, the rule configuration type
is applied only to UEs of a specified model.
• If this parameter is set to IMEISV_TAC_SVN, the rule configuration
type is applied only to UEs of the specified model and software
version.
• If this parameter is set to UE_CAPABILITY, the rule configuration
type is applied only to UEs of a specified UE capability index.
UE Capability Index ABLMSG.UeCapIndex Radio planning This parameter specifies the index of a UE capability.
(internal planning) This parameter must be configured when ABLMSG.RuleCfgType is set to
UE_CAPABILITY.
• Configuring differentiated handling for defective UEs in 4T4R cells

The following table describes the parameter that must be set in the eNBCellRsvdPara MO.
Reserved U16 eNBCellRsvdPara.RsvdU16Para7 Radio planning This parameter specifies whether the frequency of an inter-frequency
Parameter 7 (internal planning) neighboring cell belongs to a 4T cell or a 2T cell.
The following table describes the parameter that must be set in the UECOMPATRSVDPARA MO.

Name
Reserved UECOMPATRSVDPARA.RsvdSwPara0 Default/recommended The RsvdSwPara0_bit1 option of this parameter determines whether
Switch value differentiated handling takes effect on defective UEs in 4T cells.
Parameter 0
• Configuring IMEISV-based signaling trace

N/A
EISV-based Terminal Awareness Differentiation
NOTE:
• The MOUeCompatEffectSw option of the Ue Compatibility Switch parameter must be selected when running the MOD GLOBALPROCSWITCH command before
using the UeCompat MO. This will make the UeCompat MO take effect.
• When configuring IMEISVs in the ADD UECOMPAT command, ensure that the configuration order is the same as the order in which IMEISVs are displayed after
running the DSP ALLUEBASICINFO command.
• Setting Blacklist Control Policies
1. Run the MOD GLOBALPROCSWITCH command to make the UeCompat MO take effect, enable the eNodeB to obtain IMEISV information of UEs from the MME,
and turn on the terminal awareness differentiation switch.
2. Run the ADD UECOMPAT command to specify a UE information type and IMEISV TAC and select the associated options of the Black List Control Switch
parameter.
3. (Optional) To enable differentiated handling for defective UEs in 4T4R cells, do as follows:
a. Run the MOD ENBCELLRSVDPARA command to set the Reserved U16 Parameter 7 parameter according to the rules in the following table:
Frequency Mapping Between Binary Bits and Frequencies Parameter Value
2800, 2900, 3000, 3100, 3200, and 100010 (The six binary bits correspond to 3300, 3200, 3100, 3000, 34
3300 (in which 2900 and 3300 are 2900, and 2800 in sequence. In the binary value, 1 indicates 4T and 0
frequencies of 4T cells, and the others indicates 2T.)
are frequencies of 2T cells)
20


2800, 2900, 3000, 3100, 3200, and 010100 (The six binary bits correspond to 3300, 3200, 3100, 3000,
b. Run the MOD UECOMPATRSVDPARA command with the RsvdSwPara0_bit1 option of the Reserved Switch Parameter 0 parameter selected.
• Setting Whitelist Control Policies
2. Run the MOD CELLDLSCHALGO command with the DetectRank2AdjSwitch(DetectRank2AdjSwitch) option of the Downlink Rank Detect Switch parameter
selected.
3. Run the ADD UECOMPAT command to specify a UE information type and IMEISV TAC and select the associated options of the White List Control Switch
parameter.
• Configuring Signaling Survival
2. Run the ADD ABLMSG command to specify the IMEISV TAC and SVN, and set the Rule Configuration Type parameter.
• Configuring Signaling Trace
1. Run the MOD GLOBALPROCSWITCH command with the UeTypeRecogSwitch(UeTypeRecogSwitch) option of the S1 MME Private Feature Indicator
parameter and the AbnormalUeHandleSwitch(AbnormalUeHandleSwitch) option of the Ue Compatibility Switch parameter selected.
2. Start a signaling trace task on the U2000 with the TAC and SVN specified.
E-Capability-based Terminal Awareness Differentiation
NOTE:
The MOUeCompatEffectSw option of the Ue Compatibility Switch parameter must be selected when running the MOD GLOBALPROCSWITCH command before using the
UeCompat MO. This will make the UeCompat MO take effect.
• Setting Blacklist Control Policies
1. Run the MOD GLOBALPROCSWITCH command to make the UeCompat MO take effect and turn on the terminal awareness differentiation switch.
2. Run the ADD UEINFO command to set parameters related to UE capability information.
3. Run the ADD UECOMPAT command to specify a UE information type and IMEISV TAC and select the associated options of the Black List Control Switch
parameter.
4. (Optional) To enable differentiated handling for defective UEs in 4T4R cells, do as follows:
a. Run the MOD ENBCELLRSVDPARA command to set the Reserved U16 Parameter 7 parameter according to the rules in the following table:
b. Run the MOD UECOMPATRSVDPARA command with the RsvdSwPara0_bit1 option of the Reserved Switch Parameter 0 parameter selected.
• Setting Whitelist Control Policies
3. Run the ADD UECOMPAT command to specify a UE information type and IMEISV TAC and select the associated options of the White List Control Switch
parameter.
• Configuring Signaling Survival
3. Run the ADD ABLMSG command to specify a UE capability index and a rule configuration type.
• Configuring Signaling Trace
1. Run the MOD GLOBALPROCSWITCH command with the AbnormalUeHandleSwitch option of the Ue Compatibility Switch parameter selected.
2. Start a signaling trace task on the U2000 with the UE capability index specified.
EISV-based Terminal Awareness Differentiation
Setting Blacklist Control Policies

//Selecting the options UeTypeRecogSwitch, AbnormalUeHandleSwitch, and MOUeCompatEffectSw
MOD GLOBALPROCSWITCH: S1MmePrivFeatureInd=UeTypeRecogSwitch-1, UeCompatSwitch=AbnormalUeHandleSwitch-1&MOUeCompatEffectSw-1;
//Specifying a UE information type and IMEISV TAC and selecting the associated options of the Black List Control Switch parameter
ADD UECOMPAT: Index=0, UeInfoType=IMEISV_TAC_SVN, ImeisvTac=12345678, ImeisvSvn=12, BlkLstCtrlSwitch=LTE_ANR_SWITCH_OFF-1&DYNAMI
C_DRX_SWITCH_OFF-1, UeTypeDesc="Phone";
//(Optional) Enabling differentiated handling for defective UEs in 4T4R cells with the Reserved U16 Parameter 7 parameter set to 0 (indicating that no frequencies are used for
4T cells)
MOD ENBCELLRSVDPARA: LocalCellId=0, RsvdU16Para7=0;
MOD UECOMPATRSVDPARA: Index=0, RsvdSwPara0=RsvdSwPara0_bit1-1;
Setting Whitelist Control Policies


//Specifying a UE information type and IMEISV TAC and selecting the associated option of the White List Control Switch parameter
ADD UECOMPAT: Index=0, UeInfoType=IMEISV_TAC_SVN, ImeisvTac=12345678, ImeisvSvn=12, WhiteLstCtrlSwitch=RANK_DETECT_SWITCH_ON-1,
UeTypeDesc="Phone";
Configuring Signaling Survival
//Specifying the IMEISV TAC and SVN and setting the Rule Configuration Type parameter
ADD ABLMSG: RuleIndex=1, MsgItfType=S1AP, MsgType=255, ImeisvTac=12345678, ImeisvSvn=12, RuleCfgType=IMEISV_TAC_SVN, MsgOpType=D
ISCARD, MatchCount=ZERO;
Configuring Signaling Trace
//Starting a signaling trace task on the U2000 with the TAC and SVN specified. This step does not involve the execution of an MML script.
E-Capability-based Terminal Awareness Differentiation
Setting Blacklist Control Policies

//Selecting the options AbnormalUeHandleSwitch and MOUeCompatEffectSw
MOD GLOBALPROCSWITCH: UeCompatSwitch=AbnormalUeHandleSwitch-1&MOUeCompatEffectSw-1;
//Setting UE capability information
ADD UEINFO: UeCapIndex=0, AccessStratumRelease=1, UeCategory=40, Fgi=1247894;
//Specifying a UE information type and IMEISV TAC and selecting the associated options of the Black List Control Switch parameter
ADD UECOMPAT: Index=0, UeInfoType=UE_CAPABILITY, UeCapIndex=0, BlkLstCtrlSwitch=LTE_ANR_SWITCH_OFF-1&DYNAMIC_DRX_SWITCH_OFF-1, U
eTypeDesc="Phone";
//(Optional) Enabling differentiated handling for defective UEs in 4T4R cells with the Reserved U16 Parameter 7 parameter set to 0 (indicating that no frequencies are used for
4T cells)
MOD ENBCELLRSVDPARA: LocalCellId=0, RsvdU16Para7=0;
MOD UECOMPATRSVDPARA: Index=0, RsvdSwPara0=RsvdSwPara0_bit1-1;
Setting Whitelist Control Policies
//Specifying a UE information type and IMEISV TAC and selecting the associated option of the White List Control Switch parameter
ADD UECOMPAT: Index=0, UeInfoType=UE_CAPABILITY, UeCapIndex=0, WhiteLstCtrlSwitch=RANK_DETECT_SWITCH_ON-1, UeTypeDesc="Phone";
Configuring Signaling Survival
//Specifying a UE capability index and a rule configuration type
ADD ABLMSG: RuleIndex=1, MsgItfType=S1AP, MsgType=255, UeCapIndex=0, RuleCfgType=UE_CAPABILITY, MsgOpType=DISCARD, MatchCount=ZE
RO;
Configuring Signaling Trace
//Starting a signaling trace task on the U2000 with the UE information index specified. This step does not involve the execution of an MML script.
bserving IMEISV-based Terminal Awareness Differentiation
1. Run the DSP ALLUEBASICINFO command to query the IMEISV of a UE. The command output is similar to information shown in Figure 6-1.
Figure 6-1 Example of the command output of DSP ALLUEBASICINFO
2. On the U2000, check the INITIAL CONTEXT SETUP REQUEST message of the S1 interface for the Masked IMEISV IE. Figure 6-2 shows an example of the INITIAL
CONTEXT SETUP REQUEST message.
Figure 6-2 Example of the INITIAL CONTEXT SETUP REQUEST message
It is expected that the IMEISV values queried in the preceding two steps are the same but in reverse order, as shown in Table 6-1.
Table 6-1 Queried IMEISV values
IMEISV Source IMEISV Value
Query result of step 1 35 74 56 04 40 FF FF 19
Query result of step 2 53 47 65 40 04 FF FF 91

NOTE:
The IMEISV value in the command output of DSP ALLUEBASICINFO is arranged in the same order as that in a UE, while the Masked IMEISV value in the S1
message is arranged in compliance with 3GPP technical specifications.
When configuring IMEISV in the ADD UECOMPAT command, ensure that the IMEISV value is arranged in the same order as that in the command result of DSP
ALLUEBASICINFO.
In addition, the masked IMEISV is also available in the PublicInfo event of an external CHR. Table 6-2 provides the mapping between external CHRs and masked
IMEISVs.
Table 6-2 Mapping relationship
CHR Field Masked IMEISV IE Field Value (Hexadecimal)
ulTac TAC 86 04 53 02
ulSnr SNR 29 FF FF
ulSvn SVN 00
bserving UE-Capability-based Terminal Awareness Differentiation
1. On the U2000, check the INITIAL CONTEXT SETUP REQUEST message of the S1 interface for the UE Eutran Capability IE. Figure 6-3 shows an example of the
INITIAL CONTEXT SETUP REQUEST message.
Figure 6-3 Example of the INITIAL CONTEXT SETUP REQUEST message
The values of the fields related to UE capability information correspond to the parameter values of the UeInfo MO, as listed in Table 6-3.
Table 6-3 Mappings between UE capability information in the message and the parameter values of the UeInfo MO
Field Value Mapping Parameter in the UeInfo MO
accessStratumRelease 1 UeInfo.AccessStratumRelease
ue-Category 3 UeInfo.UeCategory
featureGroupIndicators 01111111000011111111110010000000 UeInfo.Fgi
In addition, the UeInfo event of CHR also contains fields related to UE capability information. The values of these fields correspond to the parameter values of the
UeInfo MO, as listed in Table 6-4.
Table 6-4 Mappings between UE capability information in CHR and the parameter values of the UeInfo MO
CHR Field Mapping Parameter in UeInfo MO
AccessStratumRelease UeInfo.AccessStratumRelease
UeCategory UeInfo.UeCategory
Fgi UeInfo.Fgi
6.4.7 Deactivation
Table 6-5 provides the parameter used to deactivate this feature.
Table 6-5 Parameters for deactivating the Terminal Awareness Differentiation feature
MO Parameter Group Setting Notes
GlobalProcSwitch UE Compatibility Switch Deselect AbnormalUeHandleSwitch in the Ue Compatibility

Switch parameter.
1. Run the MOD GLOBALPROCSWITCH command with the AbnormalUeHandleSwitch(AbnormalUeHandleSwitch) option of the Ue Compatibility Switch
parameter deselected.
MOD GLOBALPROCSWITCH: UeCompatSwitch=AbnormalUeHandleSwitch-0;
This feature has the following reconfiguration scenarios (using IMEISV-based terminal awareness differentiation as an example):
• After the incompatibility of a certain type of UEs with a feature is resolved, remove the type of UEs from the terminal blacklist or whitelist.
1. Run the MOD UECOMPAT command to modify the differentiated handling policies for that type of UEs.
MOD UECOMPAT: Index=0, UeInfoType=IMEISV_TAC_SVN, ImeisvTac=12345678, ImeisvSvn=12, UeTypeDesc="Phone1", BlkLstCtrlSwit
ch=DYNAMIC_DRX_SWITCH_OFF-0, WhiteLstCtrlSwitch=RANK_DETECT_SWITCH_ON-0;
• If a certain type of UEs experiences new compatibility problems on a feature, blacklist or whitelist this type of UEs.
1. Run the MOD UECOMPAT command to modify the differentiated handling policies for that type of UEs.
MOD UECOMPAT: Index=0, UeInfoType=IMEISV_TAC_SVN, ImeisvTac=87654321, ImeisvSvn=12, UeTypeDesc="Phone2", BlkLstCtrlSwit
ch=DYNAMIC_DRX_SWITCH_OFF-1, WhiteLstCtrlSwitch=RANK_DETECT_SWITCH_ON-1;

Terminal Awareness Differentiation can mitigate the impact of UE incompatibility with networks. This incompatibility with networks can result in problems such as more service
drops, more RRC connection re-establishments, and lower uplink and downlink throughput. You can evaluate feature performance by monitoring the problem changes. When
defective UEs account for a small percentage of all UEs on a network, you may not be able to find feature gains from performance counters. In this case, you can create user
tracing tasks for these UEs to monitor the feature performance.
In specific networks, use user-defined performance indicators to evaluate feature gains. This section provides a reference only.
Table 6-6 lists example KPIs.
Table 6-6 KPIs
KPI Name Formula
User uplink average throughput L.Thrp.bits.UL / L.Thrp.Time.UL
User downlink average throughput L.Thrp.bits.DL / L.Thrp.Time.DL
Success rate of S1-based handover (L.HHO.IntereNB.IntraFreq.ExecAttOut + L.HHO.IntereNB.InterFreq.ExecAttOut - L.HHO.X2.IntraFreq.ExecAttOut -

preparations L.HHO.X2.InterFreq.ExecAttOut) / (L.HHO.IntereNB.IntraFreq.PrepAttOut + L.HHO.IntereNB.InterFreq.PrepAttOut -
L.HHO.X2.IntraFreq.PrepAttOut - L.HHO.X2.InterFreq.PrepAttOut) × 100%
Success rate of X2-based handover (L.HHO.X2.IntraFreq.ExecAttOut + L.HHO.X2.InterFreq.ExecAttOut) / (L.HHO.X2.IntraFreq.PrepAttOut +

preparations L.HHO.X2.InterFreq.PrepAttOut) × 100%
Intra-frequency handover success rate (L.HHO.IntraeNB.IntraFreq.ExecSuccOut+L.HHO.IntereNB.IntraFreq.ExecSuccOut) /

(L.HHO.IntraeNB.IntraFreq.ExecAttOut+L.HHO.IntereNB.IntraFreq.ExecAttOut) × 100%
Inter-frequency handover success rate (L.HHO.IntraeNB.InterFreq.ExecSuccOut+L.HHO.IntereNB.InterFreq.ExecSuccOut) /

(L.HHO.IntraeNB.InterFreq.ExecAttOut+L.HHO.IntereNB.InterFreq.ExecAttOut) × 100%
Intra-eNodeB handover success rate (L.HHO.IntraeNB.InterFreq.ExecSuccOut + L.HHO.IntraeNB.IntraFreq.ExecSuccOut) / (L.HHO.IntraeNB.IntraFreq.ExecAttOut +

L.HHO.IntraeNB.InterFreq.ExecAttOut) × 100%
Inter-eNodeB handover success rate (L.HHO.IntereNB.IntraFreq.ExecSuccOut + L.HHO.IntereNB.InterFreq.ExecSuccOut) / (L.HHO.IntereNB.IntraFreq.ExecAttOut +

L.HHO.IntereNB.InterFreq.ExecAttOut) × 100%
S1-based handover success rate (L.HHO.IntereNB.IntraFreq.ExecSuccOut + L.HHO.IntereNB.InterFreq.ExecSuccOut - L.HHO.X2.IntraFreq.ExecSuccOut -

L.HHO.X2.InterFreq.ExecSuccOut) / (L.HHO.IntereNB.IntraFreq.ExecAttOut + L.HHO.IntereNB.InterFreq.ExecAttOut -
L.HHO.X2.IntraFreq.ExecAttOut - L.HHO.X2.InterFreq.ExecAttOut) × 100%
X2-based handover success rate (L.HHO.X2.IntraFreq.ExecSuccOut + L.HHO.X2.InterFreq.ExecSuccOut) / (L.HHO.X2.IntraFreq.ExecAttOut +

L.HHO.X2.InterFreq.ExecAttOut) × 100%
Service drop rate (including MME- (L.E-RAB.AbnormRel + L.E-RAB.AbnormRel.MME) / (L.E-RAB.AbnormRel + L.E-RAB.NormRel) × 100%
triggered abnormal releases)
Service drop rate (excluding MME- L.E-RAB.AbnormRel / (L.E-RAB.AbnormRel + L.E-RAB.NormRel) × 100%

VoIP call drop rate (including MME- (L.E-RAB.AbnormRel.QCI.1 + L.E-RAB.AbnormRel.MME.VoIP) / (L.E-RAB.AbnormRel.QCI.1 + L.E-RAB.NormRel.QCI.1) × 100%
VoIP call drop rate (excluding MME- L.E-RAB.AbnormRel.QCI.1 / (L.E-RAB.AbnormRel.QCI.1 + L.E-RAB.NormRel.QCI.1) × 100%
NOTE:
The intra-frequency handover success rate, inter-frequency handover success rate, service drop rate (excluding MME-triggered abnormal releases), and VoIP call drop rate
(excluding MME-triggered abnormal releases) in Table 6-6 correspond to the KPIs Intra-Frequency Handover Out Success Rate, Inter-Frequency Handover Out Success
Rate, Service Drop Rate (All), and Call Drop Rate (VoIP), respectively, defined in eRAN KPI Reference. All the other KPIs except these ones must be customized by
operators.
Table 6-7 describes the counters listed in Table 6-6.
Table 6-7 Counters
1526728259 L.Thrp.bits.UL Total uplink traffic volume for PDCP PDUs in a cell
1526728260 L.Thrp.Time.UL Total receive duration of uplink PDCP PDUs in a cell
1526728261 L.Thrp.bits.DL Total downlink traffic volume for PDCP SDUs in a cell
1526728262 L.Thrp.Time.DL Total transmit duration of downlink PDCP SDUs in a cell
1526727002 L.HHO.IntereNB.IntraFreq.ExecAttOut Number of inter-eNodeB intra-frequency outgoing handover executions

in a cell
1526727005 L.HHO.IntereNB.InterFreq.ExecAttOut Number of inter-eNodeB inter-frequency outgoing handover executions

in a cell
1526727265 L.HHO.X2.IntraFreq.ExecAttOut Number of X2-based intra-frequency outgoing handover executions in a

cell
1526727268 L.HHO.X2.InterFreq.ExecAttOut Number of X2-based inter-frequency outgoing handovers in a cell
1526727001 L.HHO.IntereNB.IntraFreq.PrepAttOut Number of inter-eNodeB intra-frequency outgoing handover attempts in

a cell
1526727004 L.HHO.IntereNB.InterFreq.PrepAttOut Number of inter-eNodeB inter-frequency outgoing handover attempts in

a cell
1526727264 L.HHO.X2.IntraFreq.PrepAttOut Number of X2-based intra-frequency outgoing handover attempts in a

cell
1526727267 L.HHO.X2.InterFreq.PrepAttOut Number of X2-based inter-frequency outgoing handover attempts in a

cell
1526726997 L.HHO.IntraeNB.IntraFreq.ExecSuccOut Number of successful intra-eNodeB intra-frequency outgoing handovers

in a cell

1526727003 L.HHO.IntereNB.IntraFreq.ExecSuccOut Number of successful inter-eNodeB intra-frequency outgoing handovers

in a cell
1526726996 L.HHO.IntraeNB.IntraFreq.ExecAttOut Number of intra-eNodeB intra-frequency outgoing handover executions

in a cell
1526727000 L.HHO.IntraeNB.InterFreq.ExecSuccOut Number of successful intra-eNodeB inter-frequency outgoing handovers

in a cell
1526726999 L.HHO.IntraeNB.InterFreq.ExecAttOut Number of intra-eNodeB inter-frequency outgoing handover executions

in a cell
1526727006 L.HHO.IntereNB.InterFreq.ExecSuccOut Number of successful inter-eNodeB inter-frequency outgoing handovers

in a cell
1526727266 L.HHO.X2.IntraFreq.ExecSuccOut Number of successful X2-based intra-frequency outgoing handovers
1526727269 L.HHO.X2.InterFreq.ExecSuccOut Number of successful X2-based inter-frequency outgoing handovers in a

cell
1526727546 L.E-RAB.AbnormRel Total number of abnormal releases of activated E-RABs initiated by the
eNodeB
1526728292 L.E-RAB.AbnormRel.MME Number of MME-triggered abnormal releases of activated E-RABs
1526727547 L.E-RAB.NormRel Total number of normal E-RAB releases initiated by the eNodeB in a cell
1526726686 L.E-RAB.AbnormRel.QCI.1 Number of abnormal releases of activated E-RABs for services with the
QCI of 1 in a cell
1526729924 L.E-RAB.AbnormRel.MME.VoIP Number of MME-triggered abnormal releases of activated E-RABs for

voice services
1526726687 L.E-RAB.NormRel.QCI.1 Number of normal E-RAB releases for services with the QCI of 1 in a
cell
N/A
Possible Issues
N/A
7 Parameters
eNBCellRsvdPara RsvdU16Para7 MOD None None Meaning:

ENBCELLRSVDPARA
Indicates the U16 reserved parameter 7 that is reserved
LST
ENBCELLRSVDPARA for future requirements.
Note on parameter replacement: Reserved parameters
are temporarily used in patch versions and will be
replaced with new parameters. For example, the ID of a
new parameter can signify the parameter function.
Unit: None
Default Value: 0
UeCompatRsvdPara RsvdSwPara0 MOD None None Meaning: Indicates reserved 32-bit switch parameter 0
UECOMPATRSVDPARA that is reserved for future requirements. Note on
LST parameter replacement: Reserved parameters are
UECOMPATRSVDPARA
temporarily used in patch versions and will be replaced
with new parameters. For example, the ID of a new
parameter can signify the parameter function. Therefore,
avoid using this parameter.


(ReservedSwitchParameter0_bit32)
Unit: None
RsvdSwPara0_bit32
UeCompat Index ADD UECOMPAT LBFD-081103 Terminal Meaning: Indicates the index of a UE compatibility
LST UECOMPAT Awareness processing action.
MOD UECOMPAT Differentiation GUI Value Range: 0~127
RMV UECOMPAT
Unit: None
Default Value: None
UeCompat UeInfoType ADD UECOMPAT LBFD-081103 Terminal Meaning: Indicates the information type to identify UEs.
MOD UECOMPAT Awareness The information includes the specified TAC, the specified
LST UECOMPAT Differentiation TAC and SVN, and the specified capability. If this
parameter is set to IMEISV_TAC, the ImeisvTac
parameter must be configured. If this parameter is set to
IMEISV_TAC_SVN, the ImeisvTac and ImeisvSvn
parameters must be configured. If this parameter is set to
UE_CAPABILITY, the UeCapIndex parameter must be
configured.
GUI Value Range: IMEISV_TAC(IMEISV_TAC),
IMEISV_TAC_SVN(IMEISV_TAC_SVN),
UE_CAPABILITY(UE_CAPABILITY)
Unit: None
Actual Value Range: IMEISV_TAC, IMEISV_TAC_SVN,
UE_CAPABILITY
Default Value: None
AblMsg UeCapIndex ADD ABLMSG LBFD-081103 Terminal Meaning:

LST ABLMSG Awareness Indicates the UE capability index. This parameter is
Differentiation mapped to the UeCapIndex parameter in the UeInfo MO.
The index must be set if the UeInfoType parameter is set
to UE_CAPABILITY.
Unit: None
Default Value: 0
UeInfo Fgi ADD UEINFO LBFD-081103 Terminal Meaning: Indicates the FGIs of Release 8 or earlier
MOD UEINFO Awareness supported by defective UEs, which correspond to the bit
LST UEINFO Differentiation string in the field featureGroupIndicators in the
information element (IE) UE-EUTRA-Capability in 3GPP
TS 36.331. If this parameter is set to 0, this parameter is
not used for UE match. If this parameter is set to another
value, a UE matches the UE type when the parameter
value is completely identical to the UE capability
information.


Unit: None
Default Value: 0
UeInfo FgiR9 ADD UEINFO LBFD-081103 Terminal Meaning:

MOD UEINFO Awareness Indicates the Release 9 FGIs supported by defective
LST UEINFO Differentiation UEs, which correspond to the bit string in the field
featureGroupIndicators-r9 in the information element (IE)
fdd-Add-UE-EUTRA-Capabilities-r9 or tdd-Add-UE-
EUTRA-Capabilities-r9 defined in 3GPP TS 36.331. A UE
matches the UE type when the parameter value matches
If this parameter is set to 0, this parameter is not used for
UE match. If this parameter is set to another value, a UE
matches the UE type when the parameter value is
completely identical to the UE capability information.
Unit: None
Default Value: 0
UeInfo FgiR10 ADD UEINFO LBFD-081103 Terminal Meaning:

MOD UEINFO Awareness Indicates the Release 10 FGIs supported by defective
LST UEINFO Differentiation UEs, which correspond to the bit string in the field
featureGroupIndRel10-r10 in the information element (IE)
UE-EUTRA-Capability-v1020-IEs, fdd-Add-UE-EUTRA-
Capabilities-v1060, or tdd-Add-UE-EUTRA-Capabilities-
v1060 defined in 3GPP TS 36.331. A UE matches the UE
type when the parameter value matches the field in any
of the IEs.
Unit: None
Default Value: 0
UeInfo AccessStratumRelease ADD UEINFO LBFD-081103 Terminal Meaning:

MOD UEINFO Awareness Indicates the access stratum capability supported by
LST UEINFO Differentiation defective UEs, which corresponds to the field
AccessStratumRelease in the information element (IE)
UE-EUTRA-Capability defined in 3GPP TS 36.331. The
parameter value 0 denotes the field value rel8, 1 rel9, 2
rel10, 3 rel11, 4 rel12, 5 spare3, 6 spare2, and 7 spare1.
Other parameter values are reserved and have no
corresponding field values.
If this parameter is set to 255, this parameter is not used
for UE match. If this parameter is set to another value, a
UE matches the UE type when the parameter value is
completely identical to the access stratum capability that
is supported by the UE.
Unit: None
Default Value: 255
UeInfo UeCategory ADD UEINFO LBFD-081103 Terminal Meaning:

MOD UEINFO Awareness Indicates the UE categories supported by defective UEs,
LST UEINFO Differentiation which correspond to the fields ue-Category, ue-Category-
v1020, ue-Category-v1170, and ue-Category-v11a0 in
the information element (IE) UE-EUTRA-Capability
When setting this parameter, you need to combine field
values indicating the UE categories in binary format and
then convert the binary number into a decimal number.
The binary digit combination rule is as follows: Each bit
from the right to the left stands for a UE category defined
in 3GPP specifications. Bit 0 stands for category 1, bit 1
category 2, bit 2 category 3, ..., bit 9 category 10, bit 10
category 11, and bit 11 category 12. Other bits are
reserved as no other categories are defined in 3GPP
specifications. If a bit value is 1, the corresponding UE
category is supported by defective UEs. For example, if a
defective UE supports both categories 4 and 6, the binary
number indicating the UE capabilities is 101000. This
binary number can be converted into 40 in decimal
format, which can be taken as the parameter value.
Unit: None
Default Value: 0
UeInfo UeCategoryDlR12 ADD UEINFO LBFD-081103 Meaning:


MOD UEINFO Terminal Indicates the UE category supported by defective UEs,
LST UEINFO Awareness which corresponds to the field ue-CategoryDL-r12 in the
Differentiation information element (IE) UE-EUTRA-Capability defined in
3GPP TS 36.331. The parameter value 0 denotes the
field value Category0, 1 Category1, 2 Category2, ..., 12
Category12, 13 Category13, and 14 Category14. Other
parameter values are reserved and have no
corresponding field values.
completely identical to the UE category that is supported
by the UE.
Unit: None
Default Value: 255
UeInfo UeCategoryUlR12 ADD UEINFO LBFD-081103 Terminal Meaning:

MOD UEINFO Awareness Indicates the UE category supported by defective UEs,
LST UEINFO Differentiation which corresponds to the field ue-CategoryUL-r12 in the
information element (IE) UE-EUTRA-Capability defined in
3GPP TS 36.331. The parameter value 0 denotes the
field value Category0, 1 Category1, 2 Category2, ..., 12
Category12, and 13 Category13. Other parameter values
are reserved and have no corresponding field values.
completely identical to the UE category that is supported
by the UE.
Unit: None
Default Value: 255
UeInfo FgiR9Add ADD UEINFO LBFD-081103 Terminal Meaning:

MOD UEINFO Awareness Indicates the Release-9-additional FGIs supported by
LST UEINFO Differentiation defective UEs, which correspond to the bit string in the
field featureGroupIndRel9Add-r9 in the information
element (IE) UE-EUTRA-Capability-v9a0-IEs, fdd-Add-
UE-EUTRA-Capabilities-r9, or tdd-Add-UE-EUTRA-
Capabilities-r9 as defined in 3GPP TS 36.331. A UE
matches the UE type when the parameter value matches
Unit: None
Default Value: 0
UeInfo EutranBandList1 ADD UEINFO LBFD-081103 Terminal Meaning:

MOD UEINFO Awareness Indicates the E-UTRA band list 1, which corresponds to
LST UEINFO Differentiation the fields bandEUTRA in the information element (IE)
SupportedBandListEUTRA in 3GPP TS 36.331.
values indicating the E-UTRA bands in binary format and
from the right to the left stands for an E-UTRA band. Bit 0
stands for band 1, bit 1 band 2, bit 2 band 3, ..., and bit
31 band 32. If the value of a bit is 1, the corresponding
E-UTRA band is supported by defective UEs. For
example, if a defective UE supports both bands 4 and 7,
the binary number indicating the E-UTRA band list is
1001000. This binary number can be converted into 72 in
decimal format, which can be taken as the parameter
value.
completely identical to the E-UTRA band list that is
supported by the UE.
Unit: None
Default Value: 0
UeInfo EutranBandList2 ADD UEINFO LBFD-081103 Terminal Meaning:

MOD UEINFO Awareness Indicates the E-UTRA band list 2, which corresponds to
LST UEINFO Differentiation the fields bandEUTRA in the information element (IE)
SupportedBandListEUTRA in 3GPP TS 36.331.
values indicating the E-UTRA bands in binary format and
from the right to the left stands for an E-UTRA band. Bit 0


stands for band 33, bit 1 band 34, bit 2 band 35, ..., and
bit 31 band 63. If the value of a bit is 1, the corresponding
E-UTRA band is supported by defective UEs. For
example, if a defective UE supports both bands 35 and
41, the binary number indicating the E-UTRA band list is
100000100. This binary number can be converted into
104 in decimal format, which can be taken as the
parameter value.
completely identical to the E-UTRA band list that is
supported by the UE.
Unit: None
Default Value: 0
UeCompatOpt WhiteLstCtrlSwitch ADD UECOMPATOPT LBFD-081103 / Terminal Meaning:

MOD UECOMPATOPT TDLBFD-081103 Awareness Indicates whether to whitelist some features.
LST UECOMPATOPT LOFD-081219 / Differentiation RANK_DETECT_SWITCH_ON: Indicates whether the
TDLOFD-111201 Voice eNodeB performs rank detection for the UE. This function
LBFD-00201802 / Coverage is enabled only if this option is selected.
TDLBFD-00201802 Enhancement UL_AMRC_SWITCH_ON: Indicates whether uplink
LOFD-001019 / Coverage AMRC is enabled for the UE. This function is enabled
TDLOFD-001019 Based Inter- only if this option is selected.
LOFD-001020 / frequency FLASH_SRVCC_SWITCH_ON: Indicates whether to
TDLOFD-001020 Handover enable flash SRVCC for specified UEs. This option
LOFD-001021 / PS Inter-RAT applies only to LTE TDD cells. If this option is deselected,
TDLOFD-001021 Mobility flash SRVCC is disabled for specified UEs. If this option
between is selected, flash SRVCC is enabled for specified UEs.
TDLBFD-002018
E-UTRAN GUI Value Range: RANK_DETECT_SWITCH_ON(Rank
TDLBFD-00201804 and UTRAN Detect Switch On), UL_AMRC_SWITCH_ON( Ul Amrc
TDLBFD-00201805 PS Inter-RAT Switch On), FLASH_SRVCC_SWITCH_ON( Flash
Mobility SRVCC Switch On)
between Unit: None
E-UTRAN
Actual Value Range: RANK_DETECT_SWITCH_ON,
and GERAN
UL_AMRC_SWITCH_ON,
PS Inter-RAT FLASH_SRVCC_SWITCH_ON
Mobility
Default Value: RANK_DETECT_SWITCH_ON:No,
between
UL_AMRC_SWITCH_ON:No,
E-UTRAN
FLASH_SRVCC_SWITCH_ON:No
and
CDMA2000
Mobility
Management
Distance
Based Inter-
frequency
Handover
Service
Based Inter-
frequency
Handover
UeCompatOpt BlkLstCtrlSwitch ADD UECOMPATOPT LOFD-002001 Automatic Meaning: Indicates whether to blacklist some features.
MOD UECOMPATOPT LOFD-002002 Neighbour LTE_ANR_SWITCH_OFF: If this option is selected, the
LST UECOMPATOPT Relation following functions are disabled for defective UEs: intra-
LOFD-001105
(ANR) RAT event-triggered ANR, intra-RAT fast ANR, active
LAOFD-001001
Inter-RAT PCI conflict detection, ANR based on specified PCI
LAOFD-001002 groups, and E-UTRAN measurement functions controlled
ANR
LAOFD-070201 by MlbBasedEventAnrSwitch.
Dynamic
LAOFD-001003 DRX UTRAN_ANR_SWITCH_OFF: If this option is selected,
LAOFD-080207 the following functions are disabled for defective UEs:
Carrier
LAOFD-080208 event-triggered ANR with UTRAN, fast ANR with
Aggregation
UTRAN, and UTRAN measurements controlled by
LAOFD-080202 for Downlink
MlbBasedEventAnrSwitch.
LOFD-001048 2CC in
GERAN_ANR_SWITCH_OFF: If this option is selected,
LOFD-001001 20MHz
the following functions are disabled for defective UEs:
LOFD-001003 Carrier event-triggered ANR with GERAN, fast ANR with
Aggregation GERAN, and GERAN measurements controlled by
LOFD-001060
for Downlink MlbBasedEventAnrSwitch. CDMA_ANR_SWITCH_OFF:
LBFD-002031 2CC in If this option is selected, the following functions are
LOFD-001017 40MHz disabled for defective UEs: fast ANR with CDMA2000
TDLOFD-002001 Flexible CA and event-triggered ANR with CDMA2000.
TDLOFD-002002 from Multiple DYNAMIC_DRX_SWITCH_OFF: If this option is
TDLOFD-00110501 Carriers selected, dynamic DRX is disabled for defective UEs.
TDLAOFD-001002 Carrier CA_SWITCH_OFF: If this option is selected, the
Aggregation following functions are disabled for defective UEs: SCell
TDLAOFD-070201
for 2CC configuration and PCC anchoring.
TDLOFD-001048 based on TTI_BUNDLING_SWITCH_OFF: If this option is
LBFD-081103 Coordinated selected, TTI bundling is disabled for defective UEs.
TDLBFD-002017 BBU MIMO_TM_MODE_SET(MIMO TM Mode Set): If this
LOFD-081219 / Carrier option is selected, the MimoAdaptiveSwitch and
TDLOFD-111201 Aggregation InitialMimoType parameters are set to OL_ADAPTIVE
for Downlink and ADAPTIVE, respectively, for detective UEs.
3CC in APERIODIC_CQI_RPT_SWITCH_OFF: If this option is
40MHz selected, enhanced aperiodic CQI reporting is disabled
Carrier for defective UEs. ROHC_SWITCH_OFF: If this option is
Aggregation selected, ROHC is disabled for defective UEs.
for Downlink DL_2CC_CA_ENHANCE_SWITCH_OFF: If this option is
selected, the function of enhanced DL ACK demodulation


3CC in with two TDD component carriers aggregated is disabled
60MHz for defective UEs. This option applies only to LTE TDD.
Carrier DRX_SWITCH_OFF: If this option is selected, DRX for
Aggregation UEs in RRC_CONNECTED mode is disabled for
for Uplink defective UEs. OSS_INTER_RAT_MR_SWITH_OFF: If
2CC [Trial] this option is selected, periodic inter-RAT measurement
TTI Bundling of strongest cells triggered by OSS subscription tasks is
disabled for defective UEs.
DL 2x2 MIMO
OSS_INTER_FREQ_MR_SWITH_OFF: If this option is
DL 4x2 MIMO selected, periodic inter-frequency measurement of
DL 4x4 MIMO strongest cells triggered by OSS subscription tasks is
Support of disabled for defective UEs. UL_AMRC_SWITCH_OFF: If
aperiodic CQI this option is selected, uplink AMRC is disabled for
reports defective UEs. FORBID_HIGH_CAPABILITY_OFF:
RObust Indicates whether the eNodeB forbids capabilities beyond
Header the UE protocol version for defective UEs that comply
Compression with 3GPP Release 10 or later. If this option is
(ROHC) deselected, capabilities beyond the UE protocol version
Automatic are allowed to take effect on the eNodeB. If this option is
Neighbour selected, the eNodeB ignores capabilities beyond the UE
Relation protocol version that are reported by the UEs.
(ANR) GUI Value Range: LTE_ANR_SWITCH_OFF
Inter-RAT (LTE_ANR_SWITCH_OFF),
ANR UTRAN_ANR_SWITCH_OFF
(UTRAN_ANR_SWITCH_OFF),
Dynamic
GERAN_ANR_SWITCH_OFF
DRX
(GERAN_ANR_SWITCH_OFF),
Carrier CDMA_ANR_SWITCH_OFF
Aggregation (CDMA_ANR_SWITCH_OFF),
for Downlink DYNAMIC_DRX_SWITCH_OFF
2CC in (DYNAMIC_DRX_SWITCH_OFF), CA_SWITCH_OFF
40MHz (CA_SWITCH_OFF), TTI_BUNDLING_SWITCH_OFF
Flexible CA (TTI_BUNDLING_SWITCH_OFF),
from Multiple MIMO_TM_MODE_SET(MIMO_TM_MODE_SET),
Carriers APERIODIC_CQI_RPT_SWITCH_OFF
TTI Bundling (APERIODIC_CQI_RPT_SWITCH_OFF),
Terminal ROHC_SWITCH_OFF(ROHC_SWITCH_OFF),
Awareness DL_2CC_CA_ENHANCE_SWITCH_OFF
Differentiation (DL_2CC_CA_ENHANCE_SWITCH_OFF),
DRX DRX_SWITCH_OFF(DRX_SWITCH_OFF),
OSS_INTER_RAT_MR_SWITH_OFF
Voice (OSS_INTER_RAT_MR_SWITH_OFF),
Coverage OSS_INTER_FREQ_MR_SWITH_OFF
Enhancement (OSS_INTER_FREQ_MR_SWITH_OFF),
UL_AMRC_SWITCH_OFF(UL_AMRC_SWITCH_OFF),
FORBID_HIGH_CAPABILITY_OFF
(FORBID_HIGH_CAPABILITY_OFF)
Unit: None
Actual Value Range: LTE_ANR_SWITCH_OFF,
UTRAN_ANR_SWITCH_OFF,
GERAN_ANR_SWITCH_OFF,
CDMA_ANR_SWITCH_OFF,
DYNAMIC_DRX_SWITCH_OFF, CA_SWITCH_OFF,
TTI_BUNDLING_SWITCH_OFF,
MIMO_TM_MODE_SET,
APERIODIC_CQI_RPT_SWITCH_OFF,
ROHC_SWITCH_OFF,
DL_2CC_CA_ENHANCE_SWITCH_OFF,
DRX_SWITCH_OFF,
OSS_INTER_RAT_MR_SWITH_OFF,
OSS_INTER_FREQ_MR_SWITH_OFF,
UL_AMRC_SWITCH_OFF,
Default Value: LTE_ANR_SWITCH_OFF:No,
UTRAN_ANR_SWITCH_OFF:No,
GERAN_ANR_SWITCH_OFF:No,
CDMA_ANR_SWITCH_OFF:No,
DYNAMIC_DRX_SWITCH_OFF:No,
CA_SWITCH_OFF:No,
TTI_BUNDLING_SWITCH_OFF:No,
MIMO_TM_MODE_SET:No,
APERIODIC_CQI_RPT_SWITCH_OFF:No,
ROHC_SWITCH_OFF:No,
DL_2CC_CA_ENHANCE_SWITCH_OFF:No,
DRX_SWITCH_OFF:No,
OSS_INTER_RAT_MR_SWITH_OFF:No,
OSS_INTER_FREQ_MR_SWITH_OFF:No,
UL_AMRC_SWITCH_OFF:No,
FORBID_HIGH_CAPABILITY_OFF:No
AblMsg ImeisvTac ADD ABLMSG None None Meaning: Indicates the type allocation code (TAC) in the
LST ABLMSG IMEISVs of UEs. Each TAC identifies a UE model. For
details about IMEISVs, see section 6.2.2 in 3GPP TS
23.003 V10.1.0 or later releases. Do not change the
setting of this parameter without the guidance from
Huawei Customer Service Center.
Unit: None
Default Value: 0
AblMsg ImeisvSvn ADD ABLMSG None None Meaning: Indicates the software version number (SVN) in
LST ABLMSG the IMEISVs of UEs. Each SVN identifies a software


version of UEs. For details about IMEISVs, see section
6.2.2 in 3GPP TS 23.003 V10.1.0 or later releases. Do
not change the setting of this parameter without the
guidance from Huawei Customer Service Center.
Unit: None
Default Value: 0
AblMsg ImeisvDesc ADD ABLMSG None None Meaning: Indicates the user-defined description of the UE
LST ABLMSG type.
GUI Value Range: 0~40 characters
Unit: None
Default Value: None
AblMsg RuleIndex ADD ABLMSG None None Meaning: Indicates the index of a rule for the debugging
LST ABLMSG message.
RMV ABLMSG GUI Value Range: 0~49
Unit: None
Default Value: None
AblMsg RuleCfgType ADD ABLMSG None None Meaning:

LST ABLMSG Indicates whether the rule takes effect on all UEs, UEs
with the specified TAC, UEs with the specified TAC and
SVN, or UEs with the specified capability.
If this parameter is set to ALL, none of ImeisvTac,
ImeisvSvn, and UeCapIndex needs to be configured.
If this parameter is set to IMEISV_TAC, the ImeisvTac
parameter must be configured.
If this parameter is set to IMEISV_TAC_SVN, the
ImeisvTac and ImeisvSvn parameters must be
configured.
If this parameter is set to UE_CAPABILITY, the
UeCapIndex parameter must be configured.
GUI Value Range: ALL(All), IMEISV_TAC(TAC of
IMEISV), IMEISV_TAC_SVN(TAC and SVN of IMEISV),
UE_CAPABILITY(Capability of UE)
Unit: None
Actual Value Range: ALL, IMEISV_TAC,
IMEISV_TAC_SVN, UE_CAPABILITY
Default Value: ALL(All)
GlobalProcSwitch UeCompatSwitch MOD LBFD- Coverage Meaning:

GLOBALPROCSWITCH 00201802/TDLBFD- Based Inter- Indicates whether to enable compatibility optimization
LST 00201802 frequency
GLOBALPROCSWITCH functions for UEs to control the differentiated handling of
LBFD- Handover abnormal UEs.
00201804/TDLBFD- Distance AbnormalUeHandleSwitch: This option specifies whether
00201804 Based Inter- to enable handling of abnormal UEs. This function is
LBFD- Frequency enabled only if this option is selected.
00201805/TDLBFD- Handover UltraFlashCsfbComOptSw(UltraFlashCsfbComOptSw):
00201805 Service Indicates whether to enable the optimization of UE
Based Inter- incompatibility risks in ultra-flash CSFB. If this option is
frequency selected, an eNodeB triggers an ultra-flash CSFB
Handover procedure based on the private IE "SRVCC based
eCSFB operation possible" that the MME sends to the
eNodeB. If this option is deselected, the eNodeB does
not trigger an ultra-flash CSFB procedure based on this
IE.
ForbidR8R9UeAccessB41Sw
(ForbidR8R9UeAccessB41Sw): Indicates whether to
forbid UEs compliant with 3GPP Release 8 and Release
9 to access a cell that works at a frequency ranging from
2575 MHz to 2595 MHz within band 41. If this option is
selected, all the UEs are forbidden to access a cell that
works at a frequency ranging from 2575 MHz to 2595
MHz of band 41. If this option is deselected, the UEs are
not forbidden to access such a cell. It is recommended
that this option be selected only if there are abnormal
UEs that support band 41 according to its capability
report but actually do not support the frequency range
from 2575 MHz to 2595 MHz within band 41.
InterFddTddMeasComOptSw: Indicates whether to
enable compatibility optimization on inter-duplex-mode
measurements for UEs. If a UE can send inter-duplex-
mode measurement reports but actually cannot perform
inter-duplex-mode measurements, this UE incompatibility
issue may cause an increase in the service drop rate. If
this option is selected, the eNodeB is not allowed to
deliver inter-duplex-mode measurement configurations to
such UEs.
PerExtendBitSw: Indicate whether to encode extended
bit indicators for Uu messages if extended IEs specified
by later 3GPP releases are not included in Uu message
code. If this option is selected, extended bit indicators are
not encoded. If this option is deselected, extended bit
indicators are encoded.
MOUeCompatEffectSw: Indicates whether the UeCompat
MO takes effect. If this option is selected, the UeCompat


MO but not the UeCompatOpt MO takes effect. If this
option is deselected, the UeCompatOpt MO but not the
GUI Value Range: AbnormalUeHandleSwitch
(AbnormalUeHandleSwitch), UltraFlashCsfbComOptSw
(UltraFlashCsfbComOptSw),
ForbidR8R9UeAccessB41Sw
(ForbidR8R9UeAccessB41Sw), MOUeCompatEffectSw
( MOUeCompatEffectSw), PerExtendBitSw
(PerExtendBitSw), InterFddTddMeasComOptSw
(InterFddTddMeasComOptSw)
Unit: None
Actual Value Range: AbnormalUeHandleSwitch,
UltraFlashCsfbComOptSw,
ForbidR8R9UeAccessB41Sw, MOUeCompatEffectSw,
PerExtendBitSw, InterFddTddMeasComOptSw
Default Value: AbnormalUeHandleSwitch:Off,
UltraFlashCsfbComOptSw:Off,
ForbidR8R9UeAccessB41Sw:Off,
MOUeCompatEffectSw:Off, PerExtendBitSw:Off,
InterFddTddMeasComOptSw:Off
GlobalProcSwitch S1MmePrivFeatureInd MOD LBFD-081103 Terminal Meaning: Indicates the switch to control the Huawei-
GLOBALPROCSWITCH Awareness proprietary functions related to the S1
LST Differentiation interface.UeTypeRecogSwitch: This option controls
GLOBALPROCSWITCH
whether to allow the eNodeB to obtain the IMEISV
information of UEs from the MME. An eNodeB applies for
the IMEISV information delivered from the MME only if
this option is selected. For details about the definition of
IMEISV, see section 6.2.2 in 3GPP TS 23.003.As defined
in section 9.2.3.38 in 3GPP TS 36.413 V12.2.0, the last 4
digits of the SNR in the IMEISV are masked by setting
the corresponding bits to F.
GUI Value Range: UeTypeRecogSwitch
(UeTypeRecogSwitch)
Unit: None
Actual Value Range: UeTypeRecogSwitch
Default Value: UeTypeRecogSwitch:Off
UeCompatOpt ImeisvSvn ADD UECOMPATOPT LBFD-081103 Terminal Meaning: Indicates the software version number (SVN) in
MOD UECOMPATOPT Awareness the IMEISVs of UEs. Each SVN identifies a software
LST UECOMPATOPT Differentiation version of UEs. For details about IMEISVs, see section
6.2.2 in 3GPP TS 23.003 V8.21.0 or later releases. If the
ImeisvSvnCfgInd parameter is set to NOT_CFG
(NOT_CFG), the GUI value of the ImeisvSvn parameter
is NULL.
Unit: None
Default Value: 99
UeCompatOpt ImeisvTac ADD UECOMPATOPT LBFD-081103 Terminal Meaning: Indicates the type allocation code (TAC) in the
LST UECOMPATOPT Awareness IMEISV of abnormal UEs. The TAC identifies the UE
MOD UECOMPATOPT Differentiation model.For details about the definition of IMEISV, see
RMV UECOMPATOPT section 6.2.2 in 3GPP TS 23.003.
Unit: None
Default Value: None
UeCompat BlkLstCtrlSwitch ADD UECOMPAT LBFD-081103 Terminal Meaning: Indicates whether to blacklist some features.
MOD UECOMPAT LOFD-002001 Awareness LTE_ANR_SWITCH_OFF: If this option is selected, the
LST UECOMPAT Differentiation following functions are disabled for defective UEs: intra-
LOFD-002002
Automatic RAT event-triggered ANR, intra-RAT fast ANR, active
LOFD-001105
Neighbour PCI conflict detection, ANR based on specified PCI
LAOFD-001001 groups, and E-UTRAN measurement functions controlled
Relation
LAOFD-001002 (ANR) by MlbBasedEventAnrSwitch.
LAOFD-070201 Inter-RAT UTRAN_ANR_SWITCH_OFF: If this option is selected,
LAOFD-001003 ANR the following functions are disabled for defective UEs:
LAOFD-080207 event-triggered ANR with UTRAN, fast ANR with
Dynamic
UTRAN, and UTRAN measurements controlled by
LAOFD-080208 DRX
MlbBasedEventAnrSwitch.
LAOFD-080202 Carrier GERAN_ANR_SWITCH_OFF: If this option is selected,
LOFD-001048 Aggregation the following functions are disabled for defective UEs:
LOFD-001001 for Downlink event-triggered ANR with GERAN, fast ANR with
2CC in GERAN, and GERAN measurements controlled by
LOFD-001003
20MHz MlbBasedEventAnrSwitch. CDMA_ANR_SWITCH_OFF:
LOFD-001060
Carrier If this option is selected, the following functions are
LBFD-002031 Aggregation disabled for defective UEs: fast ANR with CDMA2000
LOFD-001017 for Downlink and event-triggered ANR with CDMA2000.
LBFD-002017 2CC in DYNAMIC_DRX_SWITCH_OFF: If this option is
TDLOFD-002001 40MHz selected, dynamic DRX is disabled for defective UEs.
TDLOFD-002002 Flexible CA CA_SWITCH_OFF: If this option is selected, the
from Multiple following functions are disabled for defective UEs: SCell
TDLOFD-00110501
Carriers configuration and PCC anchoring.
TDLAOFD-001002 TTI_BUNDLING_SWITCH_OFF: If this option is
Carrier
TDLAOFD-070201 Aggregation selected, TTI bundling is disabled for defective UEs.
TDLOFD-001048 for 2CC MIMO_TM_MODE_SET: If this option is selected, the
TDLBFD-002017 based on MimoAdaptiveSwitch and InitialMimoType parameters
LOFD-081219 / Coordinated are set to OL_ADAPTIVE and ADAPTIVE, respectively,
TDLOFD-111201 BBU for detective UEs.
APERIODIC_CQI_RPT_SWITCH_OFF: If this option is


Carrier selected, enhanced aperiodic CQI reporting is disabled
Aggregation for defective UEs. ROHC_SWITCH_OFF: If this option is
for Downlink selected, ROHC is disabled for defective UEs.
3CC in DL_2CC_CA_ENHANCE_SWITCH_OFF: If this option is
40MHz selected, the function of enhanced DL ACK demodulation
Carrier with two TDD component carriers aggregated is disabled
Aggregation for defective UEs. This option applies only to LTE TDD.
for Downlink DRX_SWITCH_OFF: If this option is selected, DRX for
3CC in UEs in RRC_CONNECTED mode is disabled for
60MHz defective UEs. OSS_INTER_RAT_MR_SWITH_OFF: If
Carrier this option is selected, periodic inter-RAT measurement
Aggregation of strongest cells triggered by OSS subscription tasks is
for Uplink disabled for defective UEs.
2CC [Trial] OSS_INTER_FREQ_MR_SWITH_OFF: If this option is
selected, periodic inter-frequency measurement of
TTI Bundling
strongest cells triggered by OSS subscription tasks is
DL 2x2 MIMO disabled for defective UEs. UL_AMRC_SWITCH_OFF: If
DL 4x2 MIMO this option is selected, uplink AMRC is disabled for
DL 4x4 MIMO defective UEs. FORBID_HIGH_CAPABILITY_OFF:
Support of Indicates whether the eNodeB forbids capabilities beyond
aperiodic CQI the UE protocol version for defective UEs that comply
reports with 3GPP Release 10 or later. If this option is
RObust deselected, capabilities beyond the UE protocol version
Header are allowed to take effect on the eNodeB. If this option is
Compression selected, the eNodeB ignores capabilities beyond the UE
(ROHC) protocol version that are reported by the UEs.
DRX GUI Value Range: LTE_ANR_SWITCH_OFF
(LTE_ANR_SWITCH_OFF),
Automatic
UTRAN_ANR_SWITCH_OFF
Neighbour
(UTRAN_ANR_SWITCH_OFF),
Relation
GERAN_ANR_SWITCH_OFF
(ANR)
(GERAN_ANR_SWITCH_OFF),
Inter-RAT CDMA_ANR_SWITCH_OFF
ANR (CDMA_ANR_SWITCH_OFF),
Dynamic DYNAMIC_DRX_SWITCH_OFF
DRX (DYNAMIC_DRX_SWITCH_OFF), CA_SWITCH_OFF
Carrier (CA_SWITCH_OFF), TTI_BUNDLING_SWITCH_OFF
Aggregation (TTI_BUNDLING_SWITCH_OFF),
for Downlink MIMO_TM_MODE_SET(MIMO_TM_MODE_SET),
2CC in APERIODIC_CQI_RPT_SWITCH_OFF
40MHz (APERIODIC_CQI_RPT_SWITCH_OFF),
Flexible CA ROHC_SWITCH_OFF(ROHC_SWITCH_OFF),
from Multiple DL_2CC_CA_ENHANCE_SWITCH_OFF
Carriers (DL_2CC_CA_ENHANCE_SWITCH_OFF),
TTI Bundling DRX_SWITCH_OFF(DRX_SWITCH_OFF),
OSS_INTER_RAT_MR_SWITH_OFF
DRX (OSS_INTER_RAT_MR_SWITH_OFF),
Voice OSS_INTER_FREQ_MR_SWITH_OFF
Coverage (OSS_INTER_FREQ_MR_SWITH_OFF),
Enhancement UL_AMRC_SWITCH_OFF(UL_AMRC_SWITCH_OFF),
(FORBID_HIGH_CAPABILITY_OFF)
Unit: None
Actual Value Range: LTE_ANR_SWITCH_OFF,
UTRAN_ANR_SWITCH_OFF,
GERAN_ANR_SWITCH_OFF,
CDMA_ANR_SWITCH_OFF,
DYNAMIC_DRX_SWITCH_OFF, CA_SWITCH_OFF,
TTI_BUNDLING_SWITCH_OFF,
MIMO_TM_MODE_SET,
APERIODIC_CQI_RPT_SWITCH_OFF,
ROHC_SWITCH_OFF,
DL_2CC_CA_ENHANCE_SWITCH_OFF,
DRX_SWITCH_OFF,
OSS_INTER_RAT_MR_SWITH_OFF,
OSS_INTER_FREQ_MR_SWITH_OFF,
UL_AMRC_SWITCH_OFF,
Default Value: LTE_ANR_SWITCH_OFF:No,
UTRAN_ANR_SWITCH_OFF:No,
GERAN_ANR_SWITCH_OFF:No,
CDMA_ANR_SWITCH_OFF:No,
DYNAMIC_DRX_SWITCH_OFF:No,
CA_SWITCH_OFF:No,
TTI_BUNDLING_SWITCH_OFF:No,
MIMO_TM_MODE_SET:No,
APERIODIC_CQI_RPT_SWITCH_OFF:No,
ROHC_SWITCH_OFF:No,
DL_2CC_CA_ENHANCE_SWITCH_OFF:No,
DRX_SWITCH_OFF:No,
OSS_INTER_RAT_MR_SWITH_OFF:No,
OSS_INTER_FREQ_MR_SWITH_OFF:No,
UL_AMRC_SWITCH_OFF:No,
FORBID_HIGH_CAPABILITY_OFF:No
ENodeBAlgoSwitch AnrSwitch MOD LOFD-002001 / Automatic Meaning:

ENODEBALGOSWITCH TDLOFD-002001 Neighbour Indicates whether to enable automatic neighbor relation
LST Relation
ENODEBALGOSWITCH LOFD-002002 / (ANR). This parameter provides the following options:
TDLOFD-002002 (ANR) IntraRatEventAnrSwitch: If this option is selected, intra-
Inter-RAT RAT event-triggered ANR is enabled. This type of ANR
ANR sets up and optimizes intra-RAT neighbor relationships
as triggered by coverage-based intra-RAT handover
events.


IntraRatFastAnrSwitch: If this option is selected, intra-
RAT fast ANR is enabled. This type of ANR sets up and
optimizes intra-RAT neighbor relationships based on
periodic intra-RAT measurements.
IntraRatAnrAutoDelSwitch: If this option is selected,
IntraRatEventAnrSwitch is selected, and NoRmvFlag of
an intra-RAT neighboring cell is set to
PERMIT_RMV_ENUM, automatic removal of intra-RAT
neighbor relationships is allowed. If the
IntraRatAnrAutoDelSwitch option is deselected,
automatic removal of intra-RAT neighbor relationships is
allowed.
UtranEventAnrSwitch: If this option is selected, event-
triggered ANR with UTRAN is enabled. This type of ANR
sets up and optimizes inter-RAT neighbor relationships
with UTRAN cells as triggered by events for coverage-
based handovers to UTRAN.
GeranEventAnrSwitch: If this option is selected, event-
triggered ANR with GERAN is enabled. This type of ANR
sets up and optimizes inter-RAT neighbor relationships
with GERAN cells as triggered by events for coverage-
based handovers to GERAN.
UtranFastAnrSwitch: If this option is selected, fast ANR
with UTRAN is enabled. This type of ANR sets up and
optimizes inter-RAT neighbor relationships with UTRAN
cells based on periodic UE measurements on UTRAN.
UEs measure only neighboring cells contained in
measurement configurations, in which the eNodeB does
not include external UTRAN cells. To enable external
UTRAN cells added by fast ANR to be measured for
handovers, you are advised to set UtranEventAnrSwitch
on as well.
GeranFastAnrSwitch: If this option is selected, fast ANR
with GERAN is enabled. This type of ANR sets up and
optimizes inter-RAT neighbor relationships with GERAN
cells based on periodic UE measurements on GERAN.
CdmaFastAnrSwitch: If this option is selected, fast ANR
with CDMA2000 is enabled. This type of ANR sets up
and optimizes inter-RAT neighbor relationships with
CDMA2000 cells based on periodic UE measurements
on CDMA2000 networks.
UtranAutoNrtDeleteSwitch: If UtranAutoNrtDeleteSwitch
and UtranEventAnrSwitch are both selected, the eNodeB
can automatically remove inter-RAT neighbor
relationships with UTRAN cells whose NoRmvFlag is set
to PERMIT_RMV_ENUM. If UtranAutoNrtDeleteSwitch is
deselected, the eNodeB is not allowed to automatically
remove neighbor relationships with UTRAN cells.
GeranAutoNrtDeleteSwitch: If GeranAutoNrtDeleteSwitch
and GeranEventAnrSwitch are both selected, the
eNodeB can automatically remove inter-RAT neighbor
relationships with GERAN cells whose NoRmvFlag is set
to PERMIT_RMV_ENUM. If GeranAutoNrtDeleteSwitch
is deselected, the eNodeB is not allowed to automatically
remove neighbor relationships with GERAN cells.
CdmaAutoNrtDeleteSwitch: If CdmaAutoNrtDeleteSwitch
and CdmaEventAnrSwitch are both selected, the eNodeB
can automatically remove inter-RAT neighbor
relationships with CDMA2000 cells whose NoRmvFlag is
set to PERMIT_RMV_ENUM. If
CdmaAutoNrtDeleteSwitch is deselected, the eNodeB is
not allowed to automatically remove neighbor
relationships with CDMA2000 cells.
CdmaEventAnrSwitch: If this option is selected, event-
triggered ANR with CDMA2000 is enabled. This type of
ANR sets up and optimizes inter-RAT neighbor
relationships with CDMA2000 cells as triggered by
events for handovers to CDMA2000 networks.
MlbBasedEventAnrSwitch: indicates whether to enable
MLB-based event-triggered ANR. If
MlbBasedEventAnrSwitch is deselected, the eNodeB
does not set up or optimize neighbor relationships based
on MLB measurements. If MlbBasedEventAnrSwitch and
IntraRatEventAnrSwitch are both selected, the eNodeB
can automatically set up and optimize inter-frequency
neighbor relationships based on inter-frequency MLB
measurements. If MlbBasedEventAnrSwitch and an
option for event-triggered inter-RAT ANR
(UtranEventAnrSwitch or GeranEventAnrSwitch) are both
selected, the eNodeB can automatically set up and
optimize neighbor relationships with cells of that RAT
based on measurements for MLB to that RAT.
IntraRatNoHoSetAnrSwitch: If
IntraRatNoHoSetAnrSwitch and IntraRatEventAnrSwitch
are both selected, the eNodeB automatically sets
NoHoFlag for intra-RAT neighbor relationships. If
IntraRatNoHoSetAnrSwitch is deselected, the eNodeB
does not modify this attribute. When
IntraRatNoHoSetAnrSwitch is selected, pay attention to
the neighbor relationships whose NoHoFlag is set to
FORBID_HO_ENUM by ANR so as to prevent any


impact on handover performance. This option takes
effect only when the OptMode parameter is set to FREE.
IntraRatDoubleThdAnrSwitch: If
IntraRatDoubleThdAnrSwitch and
can automatically set up and optimize intra-RAT neighbor
relationships based on intra-RAT ANR measurement
events. With different data configurations, the probability
of triggering intra-RAT ANR measurements can be higher
than or equal to that of triggering measurements for
coverage-based handovers. If
IntraRatDoubleThdAnrSwitch is deselected, the eNodeB
does not set up or optimize intra-RAT neighbor
relationships based on intra-RAT ANR measurement
events. In the current version, this option applies only to
LTE TDD.
ServiceBasedEventAnrSwitch: If
ServiceBasedEventAnrSwitch and
can set up and optimize intra-RAT inter-frequency
neighbor relationships based on service-based inter-
frequency handovers. If ServiceBasedEventAnrSwitch
and UtranEventAnrSwitch are both selected, the eNodeB
can set up and optimize neighbor relationships with
UTRAN cells based on service-based handovers to
UTRAN.
ServiceReqEventAnrSwitch: If this option is selected and
IntraRatEventAnrSwitch is selected, service-based inter-
frequency handovers can trigger ANR to add and
optimize neighbor relationships with inter-frequency
neighboring cells.
IntraRatEnhancedEventAnrSwitch: If this option is
selected, intra-RAT enhanced event-triggered ANR is
enabled. This type of ANR is triggered by events other
than coverage-based handovers, handovers for MLB,
service-based handovers, and service-request-based
handovers. When IntraRatEventAnrSwitch and
IntraRatEnhancedEventAnrSwitch are both selected and
the frequency-specific ANR indicator is set to allow ANR,
the eNodeB can set up and optimize intra- and inter-
frequency neighbor relationships as triggered by these
events. If IntraRatEnhancedEventAnrSwitch is
deselected, the eNodeB does not set up or optimize
neighbor relationships when these events occur.
CaBasedEventAnrSwitch: indicates whether to enable
event-triggered ANR based on CA measurements. If
CaBasedEventAnrSwitch and IntraRatEventAnrSwitch
are both selected, the eNodeB can set up neighbor
relationships with cells detected during CA
measurements. In addition, when PCI confusions occur,
the eNodeB acquires ECGIs to identify target cells.
InterFreqAngcAnrSwitch: indicates whether to enable
ANGC-based event-triggered inter-frequency ANR. If
both InterFreqAngcAnrSwitch and
IntraRatEventAnrSwitch are selected, ANR automatically
adds a neighbor relationship with a neighboring cell
detected based on ANGC.
GUI Value Range: IntraRatEventAnrSwitch
(IntraRatEventAnrSwitch), IntraRatFastAnrSwitch
(IntraRatFastAnrSwitch), IntraRatAnrAutoDelSwitch
(IntraRatAnrAutoDelSwitch), UtranEventAnrSwitch
(UtranEventAnrSwitch), GeranEventAnrSwitch
(GeranEventAnrSwitch), UtranFastAnrSwitch
(UtranFastAnrSwitch), GeranFastAnrSwitch
(GeranFastAnrSwitch), CdmaFastAnrSwitch
(CdmaFastAnrSwitch), UtranAutoNrtDeleteSwitch
(UtranAutoNrtDeleteSwitch), GeranAutoNrtDeleteSwitch
(GeranAutoNrtDeleteSwitch), CdmaAutoNrtDeleteSwitch
(CdmaAutoNrtDeleteSwitch), CdmaEventAnrSwitch
(CdmaEventAnrSwitch), MlbBasedEventAnrSwitch
(MlbBasedEventAnrSwitch), IntraRatNoHoSetAnrSwitch
(IntraRatNoHoSetAnrSwitch),
IntraRatDoubleThdAnrSwitch
(IntraRatDoubleThdAnrSwitch),
ServiceBasedEventAnrSwitch
(ServiceBasedEventAnrSwitch),
ServiceReqEventAnrSwitch(ServiceReqEventAnrSwitch),
IntraRatEnhancedEventAnrSwitch
(IntraRatEnhancedEventAnrSwitch),
InterFreqAngcAnrSwitch(InterFreqAngcAnrSwitch),
CaBasedEventAnrSwitch(CaBasedEventAnrSwitch)
Unit: None
Actual Value Range: IntraRatEventAnrSwitch,
IntraRatFastAnrSwitch, IntraRatAnrAutoDelSwitch,
UtranEventAnrSwitch, GeranEventAnrSwitch,
UtranFastAnrSwitch, GeranFastAnrSwitch,
CdmaFastAnrSwitch, UtranAutoNrtDeleteSwitch,
GeranAutoNrtDeleteSwitch, CdmaAutoNrtDeleteSwitch,
CdmaEventAnrSwitch, MlbBasedEventAnrSwitch,
IntraRatNoHoSetAnrSwitch,
IntraRatDoubleThdAnrSwitch,
ServiceBasedEventAnrSwitch,
ServiceReqEventAnrSwitch,


IntraRatEnhancedEventAnrSwitch,
InterFreqAngcAnrSwitch, CaBasedEventAnrSwitch
Default Value: IntraRatEventAnrSwitch:Off,
IntraRatFastAnrSwitch:Off,
IntraRatAnrAutoDelSwitch:On, UtranEventAnrSwitch:Off,
GeranEventAnrSwitch:Off, UtranFastAnrSwitch:Off,
GeranFastAnrSwitch:Off, CdmaFastAnrSwitch:Off,
UtranAutoNrtDeleteSwitch:On,
GeranAutoNrtDeleteSwitch:On,
CdmaAutoNrtDeleteSwitch:On,
CdmaEventAnrSwitch:Off, MlbBasedEventAnrSwitch:Off,
IntraRatNoHoSetAnrSwitch:Off,
IntraRatDoubleThdAnrSwitch:Off,
ServiceBasedEventAnrSwitch:Off,
ServiceReqEventAnrSwitch:Off,
IntraRatEnhancedEventAnrSwitch:Off,
InterFreqAngcAnrSwitch:Off,
CaBasedEventAnrSwitch:Off
CellMimoParaCfg MimoAdaptiveSwitch MOD LOFD-001001 DL 2x2 MIMO Meaning:

CELLMIMOPARACFG
LOFD-001003 DL 4x2 MIMO Indicates the type of adaptive MIMO for a multi-antenna
LST
CELLMIMOPARACFG LOFD-001060 DL 4X4 eNodeB. The values are described as follows:
TDLOFD-001060 MIMO NO_ADAPTIVE: A fixed MIMO transmission mode is
TDLOFD-001001 DL 4x4 MIMO used. That is, transition between MIMO transmission
Based on modes is not supported.
TM3 and OL_ADAPTIVE: The open-loop adaptive MIMO
TM4 transmission mode is used. In this mode, UEs report
DL 2x2 MIMO 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: NO_ADAPTIVE(NO_ADAPTIVE)
CellMimoParaCfg InitialMimoType MOD LOFD-001001 / DL 2x2 MIMO Meaning:

CELLMIMOPARACFG TDLOFD-001001 DL 4x2 MIMO Indicates the MIMO transmission mode used during initial
LST
CELLMIMOPARACFG LOFD-001003 DL 4X4 network access.
LOFD-001060 MIMO If this parameter is set to TM2(TM2), the MIMO
TDLOFD-001060 DL 4x4 MIMO transmission mode used during initial network access is
Based on TM2.
TM3 and If this parameter is set to ADAPTIVE(ADAPTIVE), the
TM4 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.
GUI Value Range: TM2(TM2), ADAPTIVE(ADAPTIVE)
Unit: None
Actual Value Range: TM2, ADAPTIVE
Default Value: ADAPTIVE(ADAPTIVE)
UeCompatRsvdPara Index LST LBFD-081103 Terminal Meaning: Indicates the index of a UE compatibility
UECOMPATRSVDPARA Awareness processing action.
MOD Differentiation GUI Value Range: 0~127
UECOMPATRSVDPARA
Unit: None
Default Value: None
UeCompat WhiteLstCtrlSwitch ADD UECOMPAT LBFD-081103 / Terminal Meaning: Indicates whether to whitelist some features.
MOD UECOMPAT TDLBFD-081103 Awareness RANK_DETECT_SWITCH_ON: Indicates whether the
LST UECOMPAT LOFD-081219 Differentiation eNodeB performs rank detection for the UE. This function
LBFD-00201802 / Inter-eNodeB is enabled only if this option is selected.
TDLBFD-00201802 VoLTE CoMP UL_AMRC_SWITCH_ON: Indicates whether uplink
Coverage AMRC is enabled for the UE. This function is enabled
LOFD-001019 /
Based Inter- only if this option is selected.
TDLOFD-001019
frequency FLASH_SRVCC_SWITCH_ON: Indicates whether to
LOFD-001020 / enable flash SRVCC for specified UEs. This option
TDLOFD-001020 Handover
applies only to LTE TDD cells. If this option is deselected,
LOFD-001021 PS Inter-RAT
flash SRVCC is disabled for specified UEs. If this option
Mobility
TDLBFD-002018 is selected, flash SRVCC is enabled for specified UEs.
between
TDLBFD-00201804 E-UTRAN GUI Value Range: RANK_DETECT_SWITCH_ON(Rank
TDLBFD-00201805 and UTRAN Detect Switch On), UL_AMRC_SWITCH_ON( Ul Amrc
Switch On), FLASH_SRVCC_SWITCH_ON( Flash
PS Inter-RAT
SRVCC Switch On)
Mobility
between Unit: None


E-UTRAN Actual Value Range: RANK_DETECT_SWITCH_ON,
and GERAN UL_AMRC_SWITCH_ON,
PS Inter-RAT FLASH_SRVCC_SWITCH_ON
Mobility Default Value: RANK_DETECT_SWITCH_ON:No,
between UL_AMRC_SWITCH_ON:No,
E-UTRAN FLASH_SRVCC_SWITCH_ON:No
and
CDMA2000
Mobility
Management
Distance
Based Inter-
frequency
Handover
Service
Based Inter-
frequency
Handover
CellDlschAlgo DlRankDetectSwitch MOD TDLOFD-001001 DL 2X2 Meaning:

CELLDLSCHALGO MIMO
TDLOFD-001060 Indicates whether to perform rank detection.
DSP
CELLCOVENHSTUS TDLOFD-001061 DL 4x4 MIMO DetectRank2AdjSwitch: If this option is deselected, the
LST CELLDLSCHALGO Based on eNodeB does not perform rank 2 detection for UEs
TM3 and reporting rank 1. In this case, the eNodeB performs
TM4 single-codeword scheduling. If this option is selected: (1)
Dual The eNodeB performs rank 2 detection upon reception of
streaming rank 1 report from any UEs if whitelisted UEs have not
Beamforming been configured. (2) The eNodeB performs rank 2
detection only upon reception of rank 1 report from
whitelisted UEs if configured. The StartRankDetectEffThd
parameter in the CellDlschAlgo MO, the
StartRankDetectCntThd parameter in the CellDlschAlgo
MO, the RankDetectSuccessCntThd parameter in the
CellDlschAlgo MO, and the RankReverseDetectCntThd
parameter in the CellDlschAlgo MO take effect only when
the DetectRank2AdjSwitch option is selected.
DetectRank1AdjSwitch: If this option is deselected, the
eNodeB does not perform rank 1 detection for UEs
reporting rank 2. In this case, the eNodeB performs dual-
codeword scheduling. If this option is selected, the
eNodeB performs rank 1 detection for UEs reporting rank
2.The function controlled by DetectRank1AdjSwitch
applies to LTE TDD but not to LTE FDD in the current
version.Therefore, the setting of DetectRank1AdjSwitch
takes effect only for LTE TDD.
BfDetectRank1AdjSwitch: If this option is deselected, the
eNodeB switches between the single-stream
beamforming and dual-stream beamforming modes
based on the spectral efficiency. If this option is selected,
the eNodeB attempts to switch to the single-stream
beamforming mode when it is in dual-stream
beamforming mode. This option applies only to LTE TDD
cells.
GUI Value Range: DetectRank2AdjSwitch
(DetectRank2AdjSwitch), DetectRank1AdjSwitch
(DetectRank1AdjSwitch), BfDetectRank1AdjSwitch
(BfDetectRank1AdjSwitch)
Unit: None
Actual Value Range: DetectRank2AdjSwitch,
DetectRank1AdjSwitch, BfDetectRank1AdjSwitch
Default Value: DetectRank2AdjSwitch:Off,
DetectRank1AdjSwitch:Off, BfDetectRank1AdjSwitch:Off
UeCompat UeCapIndex ADD UECOMPAT LBFD-081103 Terminal Meaning:

MOD UECOMPAT Awareness Indicates the UE capability index. This parameter is
LST UECOMPAT Differentiation mapped to the UeCapIndex parameter in the UeInfo MO.
The index must be set if the UeInfoType parameter is set
to UE_CAPABILITY.
Unit: None
Default Value: 0
UeCompat ImeisvTac ADD UECOMPAT LBFD-081103 Terminal Meaning:

MOD UECOMPAT Awareness Indicates the type allocation code (TAC) in the IMEISVs
LST UECOMPAT Differentiation of UEs. Each TAC identifies a UE model. For details
about IMEISVs, see section 6.2.2 in 3GPP TS 23.003
V10.1.0 or later releases.
If the UeInfoType parameter is set to IMEISV_TAC or
IMEISV_TAC_SVN, this parameter must be set.
Unit: None
Default Value: 0
UeCompat ImeisvSvn ADD UECOMPAT LBFD-081103 Terminal Meaning:

MOD UECOMPAT Awareness Indicates the software version number (SVN) in the
LST UECOMPAT Differentiation IMEISVs of UEs. Each SVN identifies a software version
of UEs. For details about IMEISVs, see section 6.2.2 in
3GPP TS 23.003 V10.1.0 or later releases.


If the UeType parameter is set to IMEISV_TAC_SVN,
this parameter must be set.
Unit: None
Default Value: 0
UeInfo UeCapIndex ADD UEINFO LBFD-081103 Terminal Meaning: Indicates the UE capability index.
LST UEINFO Awareness GUI Value Range: 0~7
MOD UEINFO Differentiation Unit: None
RMV UEINFO
Default Value: None
UeCompat UeTypeDesc ADD UECOMPAT LBFD-081103 Terminal Meaning: Indicates the user-defined description of UEs
MOD UECOMPAT Awareness GUI Value Range: 0~80 characters
LST UECOMPAT Differentiation Unit: None
Default Value: None
AblMsg MsgItfType ADD ABLMSG None None Meaning: Indicates the interface protocol type of the
LST ABLMSG debugging message. Do not change the setting of this
parameter without the guidance from Huawei Customer
Service Center.
GUI Value Range: S1AP(S1AP), X2AP(X2AP), RRC
(RRC)
Unit: None
Actual Value Range: S1AP, X2AP, RRC
Default Value: None
AblMsg MsgType ADD ABLMSG None None Meaning: Indicates the number of the message
LST ABLMSG transmitted over 3GPP-specific interfaces. Do not change
the setting of this parameter without the guidance from
Huawei Customer Service Center.
Unit: None
Default Value: None
8 Counters
Table 8-1 Counters
1526726686 L.E-RAB.AbnormRel.QCI.1 Number of abnormal releases Multi-mode: None Radio Bearer Management
of activated E-RABs for GSM: None Radio Bearer Management
services with the QCI of 1 in a UMTS: None
cell
LTE: LBFD-002008
TDLBFD-002008
releases for services with the GSM: None Radio Bearer Management
LTE: LBFD-002008
TDLBFD-002008
1526726996 L.HHO.IntraeNB.IntraFreq.ExecAttOut Number of intra-eNodeB Multi-mode: None Coverage Based Intra-

intra-frequency outgoing GSM: None frequency Handover
handovers executions in a UMTS: None Coverage Based Intra-
cell frequency Handover
LTE: LBFD-00201801
TDLBFD-00201801
1526726997 L.HHO.IntraeNB.IntraFreq.ExecSuccOut Number of successful intra- Multi-mode: None Coverage Based Intra-
eNodeB intra-frequency GSM: None frequency Handover
outgoing handovers in a cell UMTS: None Coverage Based Intra-
LTE: LBFD-00201801 frequency Handover
TDLBFD-00201801
1526726999 L.HHO.IntraeNB.InterFreq.ExecAttOut Number of intra-eNodeB Multi-mode: None Coverage Based Inter-

inter-frequency outgoing GSM: None frequency Handover
handovers executions in a UMTS: None Coverage Based Inter-
LTE: LBFD-00201802
TDLBFD-00201802 Distance Based Inter-
frequency Handover
LBFD-00201804
Distance Based Inter-
TDLBFD-00201804
frequency Handover
LBFD-00201805
Service Based Inter-
TDLBFD-00201805 frequency Handover
frequency Handover
1526727000 L.HHO.IntraeNB.InterFreq.ExecSuccOut Multi-mode: None


Number of successful intra- GSM: None Coverage Based Inter-
eNodeB inter-frequency UMTS: None frequency Handover
outgoing handovers in a cell LTE: LBFD-00201802 Coverage Based Inter-
LBFD-00201804 Distance Based Inter-
frequency Handover
TDLBFD-00201804
LBFD-00201805
frequency Handover
TDLBFD-00201805
frequency Handover
frequency Handover
1526727001 L.HHO.IntereNB.IntraFreq.PrepAttOut Number of inter-eNodeB Multi-mode: None Coverage Based Intra-

handover attempts in a cell UMTS: None Coverage Based Intra-
TDLBFD-00201801
1526727002 L.HHO.IntereNB.IntraFreq.ExecAttOut Number of inter-eNodeB Multi-mode: None Coverage Based Intra-

handovers executions in a UMTS: None Coverage Based Intra-
LTE: LBFD-00201801
TDLBFD-00201801
1526727003 L.HHO.IntereNB.IntraFreq.ExecSuccOut Number of successful inter- Multi-mode: None Coverage Based Intra-
eNodeB intra-frequency GSM: None frequency Handover
outgoing handovers in a cell UMTS: None Coverage Based Intra-
TDLBFD-00201801
1526727004 L.HHO.IntereNB.InterFreq.PrepAttOut Number of inter-eNodeB Multi-mode: None Coverage Based Inter-

handover attempts in a cell UMTS: None Coverage Based Inter-
frequency Handover
LBFD-00201804
TDLBFD-00201804
frequency Handover
LBFD-00201805
frequency Handover
1526727005 L.HHO.IntereNB.InterFreq.ExecAttOut Number of inter-eNodeB Multi-mode: None Coverage Based Inter-

handovers executions in a UMTS: None Coverage Based Inter-
LTE: LBFD-00201802
frequency Handover
LBFD-00201804
TDLBFD-00201804
frequency Handover
LBFD-00201805
frequency Handover
1526727006 L.HHO.IntereNB.InterFreq.ExecSuccOut Number of successful inter- Multi-mode: None Coverage Based Inter-
eNodeB inter-frequency GSM: None frequency Handover
outgoing handovers in a cell UMTS: None Coverage Based Inter-
frequency Handover
LBFD-00201804
TDLBFD-00201804
frequency Handover
LBFD-00201805
frequency Handover
1526727264 L.HHO.X2.IntraFreq.PrepAttOut Number of X2-based intra- Multi-mode: None Coverage Based Intra-
frequency outgoing handover GSM: None frequency Handover
attempts in a cell UMTS: None Coverage Based Intra-
TDLBFD-00201801
1526727265 L.HHO.X2.IntraFreq.ExecAttOut Number of X2-based intra- Multi-mode: None Coverage Based Intra-
executions in a cell UMTS: None Coverage Based Intra-
TDLBFD-00201801
1526727266 L.HHO.X2.IntraFreq.ExecSuccOut Number of successful X2- Multi-mode: None Coverage Based Intra-
based intra-frequency GSM: None frequency Handover
outgoing handovers UMTS: None Coverage Based Intra-
TDLBFD-00201801


1526727267 L.HHO.X2.InterFreq.PrepAttOut Number of X2-based inter- Multi-mode: None Coverage Based Inter-
attempts in a cell UMTS: None Coverage Based Inter-
frequency Handover
LBFD-00201804
TDLBFD-00201804
frequency Handover
LBFD-00201805
frequency Handover
1526727268 L.HHO.X2.InterFreq.ExecAttOut Number of X2-based inter- Multi-mode: None Coverage Based Inter-
frequency outgoing GSM: None frequency Handover
handovers in a cell UMTS: None Coverage Based Inter-
frequency Handover
LBFD-00201804
TDLBFD-00201804
frequency Handover
LBFD-00201805
frequency Handover
1526727269 L.HHO.X2.InterFreq.ExecSuccOut Number of successful X2- Multi-mode: None Coverage Based Inter-
based inter-frequency GSM: None frequency Handover
outgoing handovers in a cell UMTS: None Coverage Based Inter-
frequency Handover
LBFD-00201804
TDLBFD-00201804
frequency Handover
LBFD-00201805
frequency Handover
1526727546 L.E-RAB.AbnormRel Total number of abnormal Multi-mode: None Radio Bearer Management
releases of activated E-RABs GSM: None Radio Bearer Management
initiated by the eNodeB UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526727547 L.E-RAB.NormRel Total number of normal Multi-mode: None Radio Bearer Management
the eNodeB in a cell UMTS: None
LTE: LBFD-002008
TDLBFD-002008
1526728259 L.Thrp.bits.UL Total uplink traffic volume for Multi-mode: None Radio Bearer Management
PDCP PDUs in a cell GSM: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
uplink PDCP PDUs in a cell GSM: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526728261 L.Thrp.bits.DL Total downlink traffic volume Multi-mode: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526728262 L.Thrp.Time.DL Total transmit duration of Multi-mode: None Radio Bearer Management
downlink PDCP SDUs in a GSM: None Radio Bearer Management
TDLBFD-002008
LBFD-002025
TDLBFD-002025
1526728292 L.E-RAB.AbnormRel.MME Number of MME-triggered Multi-mode: None Radio Bearer Management

activated E-RABs UMTS: None
LTE: LBFD-002008


TDLBFD-002008
1526729924 L.E-RAB.AbnormRel.MME.VoIP Number of MME-triggered Multi-mode: None Radio Bearer Management

activated E-RABs for voice UMTS: None
services
LTE: LBFD-002008
TDLBFD-002008
9 Glossary
1. 3GPP TS 36.413: "S1 Application Protocol (S1AP)"

2. 3GPP TS 23.003: "Numbering, addressing and identification"
3. ANR Management Feature Parameter Description
4. DRX and Signaling Control Feature Parameter Description
5. MIMO Feature Parameter Description
6. Carrier Aggregation Feature Parameter Description
7. ROHC Feature Parameter Description
eRAN
Uplink Timing Control Feature Parameter Description
Issue 03
Date 2017-01-15


Notice

9 Contents
1 About The Document
1.1 Scope
1.3 Change History
2 Overview
2.1 Introduction
2.2 Benefits
3.1 Uplink Timing Control During RA
3.2 Uplink Timing Control After RA
3.3 Timers
3.3.1 Uplink Time Alignment Timer
3.3.2 Uplink Synchronization Timer
3.3.3 UE Inactivity Timer
4 Related Features
5 Network Impact
6.1 When to Use
6.3 Planning
6.4 Deployment
6.4.1 Requirements
6.4.5 Deactivation
6.7 Possible Issues
7 Parameters
8 Counters
9 Glossary
1 About The Document
Scope
This document describes LBFD-070101 Uplink Timing Based on PUCCH and uplink timing control, including their technical principles, related features, network impact, and
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.
eNodeB Type Model
Micro BTS3203E

eNodeB Type Model

BTS3911E
BTS3912E
Intended Audience

Change History
• Feature change
AN11.1 03 (2017-01-15)
Feature change None None Macro, micro, and LampSite

eNodeBs
Editorial change Revised 6.4.3 Initial Configuration. None N/A
AN11.1 02 (2016-04-20)

eNodeBs
Editorial change Revised descriptions in the following chapter and sections: None N/A
• 1.1 Scope
• 6.1 When to Use
• 6.4.2 Data Preparation
• 6.4.3 Initial Configuration
AN11.1 01 (2016-03-07)
AN11.1 Draft A (2015-12-30)

eNodeBs
Editorial change Revised the descriptions of CME-based feature configuration in engineering None N/A
guidelines.

The BTS3203E does not support any new and enhanced features or functions in eRAN8.1. For details, see 1.3 Change History.
2 Overview
Introduction
During uplink timing control, the eNodeB calculates the timing offset after measuring uplink signals received from a UE. The eNodeB then converts the timing offset into a timing
advance command and issues the command to the UE. After receiving the command, the UE adjusts the time to transmit uplink signals. The entire process shown in Figure 2-1
ensures time synchronization between the UE and the eNodeB.
Figure 2-1 Uplink timing control

Benefits
With uplink timing control enabled, the eNodeB adjusts the time of transmitting uplink signals from each UE so that uplink signals from different UEs simultaneously reach the
eNodeB. This ensures orthogonality of uplink signals transmitted by different UEs, mitigates intra-cell interference, and maintains the demodulation performance of the eNodeB.
Uplink timing control can be performed during or after random access (RA), as shown in Figure 3-1.
• Uplink timing control during RA

Non-synchronized UEs (including UEs that are newly powered on or handed over to the cell, UEs in RRC_IDLE mode, and out-of-synchronization UEs) establish or
restore uplink synchronization based on RA. For details, see 3.1 Uplink Timing Control During RA.
• Uplink timing control after RA
A synchronized UE maintains the synchronization state based on periodic uplink timing adjustment. For details, see 3.2 Uplink Timing Control After RA.
When a UE is in the synchronization state, the uplink time alignment timer, uplink synchronization timer, and UE inactivity timer maintain and manage the UE states.
For details about working principles and settings of these timers, see 3.3.1 Uplink Time Alignment Timer, 3.3.2 Uplink Synchronization Timer, and 3.3.3 UE Inactivity Timer.
◾ If the uplink time alignment timer expires, an uplink-synchronized UE enters the out-of-synchronization state.
◾ If the uplink synchronization timer expires, this causes the uplink time alignment timer to expire, which further makes an uplink-synchronized UE enter the
out-of-synchronization state.
◾ If the UE inactivity timer expires, an uplink-synchronized UE enters the RRC_IDLE mode.
Non-synchronized UEs will enter the synchronization state by initiating the RA procedure again.
Figure 3-1 Timers maintaining UE states
Uplink Timing Control During RA

RA is classified into contention-based RA and non-contention-based RA.
A UE achieves uplink synchronization with the eNodeB based on uplink timing control during RA. Figure 3-2 outlines the procedure for uplink timing control during RA.
Figure 3-2 Uplink timing control during RA
1. A UE sends a random access preamble to the eNodeB.

2. The eNodeB calculates the timing offset on the UE side based on the received random access preamble.
3. The eNodeB converts the calculated timing offset into a timing advance command.
4. The eNodeB sends the UE the timing advance command, which is contained in the Random Access Response.
5. After receiving the timing advance command, the UE adjusts the time to transmit uplink signals. For details about timing adjustment, see section 4.2.3 "Transmission
timing adjustments" in 3GPP TS 36.213 V10.10.0.
Uplink Timing Control After RA

After experiencing a successful RA, an uplink-synchronized UE maintains the synchronization state based on periodic uplink timing adjustments. Figure 3-3 outlines the
procedure for periodic uplink timing adjustment.
Figure 3-3 Periodic uplink timing adjustment
1. The eNodeB allocates uplink resources to a UE, and the UE transmits uplink signals.
Resources allocated to the UE include sounding reference signal (SRS), demodulation reference signal (DMRS) for physical uplink shared channel (PUSCH), or
channel quality indicator (CQI) in physical uplink control channel (PUCCH).
2. The eNodeB measures the timing offset of the UE based on the uplink signals received from the UE.
The timing offset can be measured based on the allocated SRS resources, DMRS for PUSCH, or CQI in PUCCH. The TimeAlignmentTimer.TimingMeasMode
parameter specifies the method for measuring uplink timing offsets.
• When this parameter is set to INVALID(Invalid Timing Measurement Mode):
◾ If the eNodeB has allocated SRS resources to a UE, the eNodeB measures the timing offset of the UE based on the SRS resources.
◾ If the eNodeB has not allocated SRS resources to a UE, the eNodeB measures the timing offset of the UE based on the DMRS for PUSCH. If
the UE does not have any PUSCH resources, the eNodeB allocates PUSCH resources to the UE and then measures the timing offset based
on the DMRS for PUSCH.
• When this parameter is set to ALLMEASMODE(All Timing Measurement Mode):

◾ If the eNodeB has allocated SRS resources to a UE, the eNodeB measures the timing offset of the UE based on the SRS resources. If the UE
has PUSCH resources, the eNodeB measures the timing offset of the UE based on the SRS and DMRS for PUSCH, but the timing offset
measured based on the DMRS for PUSCH is preferentially used.
◾ If the eNodeB has not allocated SRS resources to a UE, the eNodeB measures the timing offset of the UE based on the CQI in PUCCH. If the
UE has PUSCH resources, the eNodeB measures the timing offset of the UE based on the CQI in PUCCH and DMRS for PUSCH, but the
timing offset measured based on the DMRS for PUSCH is preferred.
NOTE:
The eNodeB measures the timing offset of the UE based on the CQI in PUCCH only after the eNodeB allocates periodic CQIs to the UE.
Periodic CQI allocation is performed for UEs that are newly powered on, UEs that are newly handed over to the cell, and UEs in RRC_IDLE
mode. The eNodeB reconfigures periodic CQIs for out-of-synchronization UEs to restore synchronization with the eNodeB.
NOTE:
It is recommended that the TimeAlignmentTimer.TimingResOptSwitch parameter be set to ON(On) to reduce the amount of DMRS for PUSCH for timing offset
measurements in heavy traffic scenarios. Setting the TimeAlignmentTimer.TimingResOptSwitch parameter to ON(On) will decrease the UE mobility speed
supported by the uplink timing control based on the DMRS for PUSCH.
If the TimeAlignmentTimer.TimingResOptSwitch parameter is set to ON(On), selecting the TaEnhancePuschDmrs option of the TimeAlignmentTimer.TaEnhance
parameter decreases the amount of DMRS for PUSCH allocated by the eNodeB to UEs for timing offset measurements to a larger extent.
3. The eNodeB converts the measured timing offset into a Timing Advance Command.
4. The eNodeB sends the Timing Advance Command to the UE. The TimeAlignmentTimer.TimingAdvCmdOptSwitch parameter specifies the policy of sending the
Timing Advance Command to UEs.
• If the TimeAlignmentTimer.TimingAdvCmdOptSwitch parameter is set to OFF(Off), the eNodeB periodically sends the Timing Advance Command to
the UE. This is called the periodic policy. The length of Timing Advance Command sending period is calculated by the formula "Floor (the
TimeAlignmentTimer.TimeAlignmentTimer parameter value/2 - 32)" and cannot be manually set.
• If the TimeAlignmentTimer.TimingAdvCmdOptSwitch parameter is set to ON(On), the eNodeB adopts the "periodic evaluation and event-triggering"
policy. The period can be set by the TimeAlignmentTimer.TACmdSendPeriod parameter. A smaller value of this parameter indicates that the eNodeB
sends the Timing Advance Commands to UEs more frequently. As a result, more air interface resources are consumed and a higher mobility speed can
be supported. A larger value of this parameter results in the opposite effects. If this parameter is set to INVALID(NULL), the period that the eNodeB
adopts to send Timing Advance Commands takes a smaller value between 928 and the value calculated by the formula "Value of
TimeAlignmentTimer.TimeAlignmentTimer/2 - 32" (unit: ms).
In the "periodic evaluation and event-triggering" policy, the eNodeB periodically checks whether a UE experiences timing offsets within a timing advance
command sending period.
◾ If so, the eNodeB sends a Timing Advance Command to the UE.
◾ If not, the eNodeB does not send a Timing Advance Command to the UE.
NOTE:
If the UE does not experience a timing offset before the uplink time alignment timer expires, the eNodeB sends the Timing Advance
Command to the UE in case that the uplink time alignment timer expires because the UE does not receive the Timing Advance Command for
a long time.
NOTE:
If the TimeAlignmentTimer.TimingMeasMode parameter is set to ALLMEASMODE(All Timing Measurement Mode) or the
TimeAlignmentTimer.TimingResOptSwitch parameter is set to ON(On), the eNodeB always adopts the "periodic evaluation and event-triggering" policy regardless
of the TimeAlignmentTimer.TimingAdvCmdOptSwitch parameter setting.
5. The UE adjusts the time to transmit uplink signals based on the received Timing Advance Command. For details about timing adjustment, see section 4.2.3
"Transmission timing adjustments" in 3GPP TS 36.213 V10.10.0.

6. Uplink timing offset measurements and uplink timing adjustments are performed periodically by following steps 1 to 5.
Timers
3.3.1 Uplink Time Alignment Timer
orking Principles
Uplink synchronization between a UE and the eNodeB is performed using their respective time alignment timers.
• The UE uses its uplink time alignment timer to determine whether it is in the synchronization state. Before the timer expires, the UE considers itself to be in the
synchronization state. After the timer expires, the UE considers itself to be in the out-of-synchronization state.
• The eNodeB uses its uplink timer alignment timer to determine whether the UE is in the synchronization state. Before the timer expires, the eNodeB determines that
the UE is in the synchronization state. After the timer expires, the eNodeB determines that the UE is in the out-of-synchronization state and stops sending the Timing
Advance Command to the UE, excluding the Timing Advance Command included in the Random Access Response message.
Table 3-1 describes the working principles of the uplink time alignment timers on the UE side and the eNodeB side.
Table 3-1 Working principles of uplink time alignment timers
Timer Action Description
Uplink time alignment timer Start • When the UE receives the Timing Advance Command included in the Random
on the UE side Access Response message during RA:
◾ For a non-contention-based RA, the UE starts or restarts the timer.
◾ For a contention-based RA, if the timer has not started, the UE starts the
timer. If the timer has started, the UE does not restart the timer.
NOTE:
The timer stops if the contention-based RA fails.
• Upon receiving the Timing Advance Command after RA, the UE starts or restarts
the timer.
Expire • If the UE does not receive the Timing Advance Command from the eNodeB, the UE
does not restart the timer. As a result, the timer will expire.
• After the uplink synchronization timer expires, the eNodeB no longer sends the
Timing Advance Command to the UE, and therefore the UE does not restart the
timer. As a result, the timer will expire.
Uplink time alignment timer Start • During RA:

on the eNodeB side
◾ For a non-contention-based RA, the eNodeB starts or restarts the timer
after receiving an ACK from the UE that replies to the delivered Random
Access Response message.
◾ For a contention-based RA, the eNodeB starts or restarts the timer for
the UE that has successfully accessed the network.
• If the UE has successfully accessed the network, the eNodeB starts or restarts the
timer after receiving the ACK from the UE that replies to the delivered Timing
Advance Command.
Expire • If the eNodeB does not receive an ACK from the UE after delivering the Timing
Advance Command, the eNodeB does not restart the timer. As a result, the timer
will expire.
• After the uplink synchronization timer expires, the eNodeB no longer sends the
Timing Advance Command to the UE, and therefore the eNodeB does not restart
the timer. As a result, the timer will expire.
Both the uplink time alignment timer on the UE side and that on the eNodeB side can be restarted before expiration to prolong the duration of uplink synchronization. Upon
receiving the Timing Advance Command from the eNodeB, the UE restarts its uplink time alignment timer and sends an ACK to the eNodeB. Upon receiving the ACK, the
eNodeB restarts its uplink time alignment timer, as shown in Figure 3-4.
Figure 3-4 Time to restart the uplink time alignment timers
mer Settings
The uplink time alignment timers on the UE and eNodeB sides are controlled independently. The TimeAlignmentTimer.TimeAlignmentTimer parameter specifies the uplink time
alignment timer length on the eNodeB side. After being set, the timer length is sent to the UE through air interface signaling.
• If the eNodeB adopts the periodic policy, it is recommended that the TimeAlignmentTimer.TimeAlignmentTimer parameter be set to SF1920(1920 subframes). A
smaller value of the TimeAlignmentTimer.TimeAlignmentTimer parameter indicates that the eNodeB sends the Timing Advance Command to the UE more
frequently, more radio resources are consumed, and a higher mobility speed is supported. A larger value of this parameter indicates the opposite effects.
• If the eNodeB adopts the periodic evaluation and event-triggering policy, it is recommended that the TimeAlignmentTimer.TimeAlignmentTimer parameter be set to
SF10240(10240 subframes). In heavy traffic scenarios where the TimeAlignmentTimer.TimingResOptSwitch parameter is set to ON(On), it is recommended that
the TimeAlignmentTimer.TimeAlignmentTimer parameter be set to INFINITY(Infinity). A smaller value of the TimeAlignmentTimer.TimeAlignmentTimer parameter
(for example, less than SF5120(5120 subframes)) leads to a higher probability of UEs in the discontinuous reception (DRX) state entering the out-of-synchronization
state.
NOTE:
For details about the relationship between the TimeAlignmentTimer.TimeAlignmentTimer parameter value and the DRX state, see DRX and Signaling Control Feature
Setting the TimeAlignmentTimer.TimingResOptSwitch parameter to ON(On) and enabling the DRX feature may affect the average CQI.
3.3.2 Uplink Synchronization Timer

orking Principles
The uplink synchronization timer controls whether the eNodeB continues to maintain uplink synchronization between a UE and the eNodeB. The eNodeB maintains an uplink
synchronization timer for each UE.
Table 3-2 Working principles of the uplink synchronization timer
Action Description
Start The eNodeB starts or restarts the timer for a UE while sending data to or receiving data from the UE. Before the uplink
synchronization timer for a UE expires, the eNodeB continuously sends the Timing Advance Commands to the UE.
Expire After the uplink synchronization timer for a UE expires, the eNodeB no longer sends the Timing Advance Commands to the
UE, and determines that the UE enters the out-of-synchronization state after the uplink time alignment timer on the eNodeB
side expires.
mer Settings
The RrcConnStateTimer.UlSynTimer parameter specifies the uplink synchronization timer length.
• A smaller value for this parameter results in a higher probability of the UE entering the out-of-synchronization state, a shorter time for the UE to occupy PUCCH and
SRS resources, and a larger number of RA requests initiated by the UE.
• A larger value for this parameter results in a lower probability of the UE entering the out-of-synchronization state, a longer time for the UE to occupy PUCCH and
SRS resources, and a smaller number of RA requests initiated by the UE.
NOTE:
The RrcConnStateTimer.UlSynTimer parameter is maintained only on the eNodeB side.
If the RrcConnStateTimer.UlSynTimer parameter is set to 0, the uplink synchronization timer will never expire.
3.3.3 UE Inactivity Timer
orking Principles
The eNodeB determines whether a UE is in RRC_CONNECTED mode based on the state of the UE inactivity timer. Table 3-3 describes the working principles of this timer.
Table 3-3 Working principles of the UE inactivity timer
Action Description
Start The eNodeB starts or restarts the timer for a UE while sending data to or receiving data from the UE. Before the UE
inactivity timer expires, the eNodeB determines that the UE is in RRC_CONNECTED mode.
Expire After the UE inactivity timer expires, the eNodeB sends an RRC Connection Release message to the UE; the UE is then
released and enters the RRC_IDLE mode. This prevents an inactive UE from occupying radio resources for a long time.
NOTE:
If the UE inactivity timer for an out-of-synchronized UE expires, the UE enters the synchronization state first. Then, the eNodeB sends an RRC Connection Release message to
the UE, and the UE enters the RRC_IDLE mode.
mer Settings
The RrcConnStateTimer.UeInactiveTimer parameter specifies the length of the UE inactivity timer. When a UE does not send data to or receive data from the eNodeB:
• If this parameter is set to a smaller value, the UE will be released earlier, and the UE sends the RRC connection setup requests to the eNodeB more frequently.
Because the number of UEs released normally increases, the service drop rate decreases.
• If this parameter is set to a larger value, the UE will be released later, the RRC connection between the UE and the eNodeB maintains for a longer time, and the UE
occupies radio resources for a longer time as well. Because the number of UEs being released normally decreases, the service drop rate increases.
• If the value of RrcConnStateTimer.UlSynTimer is greater than the value of RrcConnStateTimer.UeInactiveTimer, the UE enters the RRC_IDLE mode directly.
NOTE:
The RrcConnStateTimer.UeInactiveTimer parameter is maintained only on the eNodeB side. If the parameter setting is changed, the change applies to UEs that
access the network afterwards.
If the RrcConnStateTimer.UeInactiveTimer parameter is set to 0, the timer does not take effect, which means the UEs are always in RRC_CONNECTED mode.
4 Related Features
erequisite Features
None
LOFD-001008 Ultra High Speed Mobility LOFD-001008 Ultra High Speed Mobility takes priority over LBFD-070101
Uplink Timing Based on PUCCH. If the Cell.HighSpeedFlag parameter is set to
ULTRA_HIGH_SPEED(Ultra high speed cell flag) or EXTRA_HIGH_SPEED
(Extra high speed cell flag), LBFD-070101 Uplink Timing Based on PUCCH
does not take effect.
NOTE:
LOFD-001008 Ultra High Speed Mobility does not apply to micro eNodeBs. Therefore, the
mutually exclusive relationship between LBFD-070101 Uplink Timing Based on PUCCH and
LOFD-001008 Ultra High Speed Mobility does not involve micro eNodeBs.
LOFD-001031 Extended CP LOFD-001031 Extended CP takes priority over LBFD-070101 Uplink Timing
Based on PUCCH. If the Cell.UlCyclicPrefix parameter is set to EXTENDED_CP


(Extended), LBFD-070101 Uplink Timing Based on PUCCH does not take
effect.
NOTE:
LOFD-001031 Extended CP does not apply to micro eNodeBs. Therefore, the mutually
exclusive relationship between LBFD-070101 Uplink Timing Based on PUCCH and LOFD-
001031 Extended CP does not involve micro eNodeBs.
mpacted Features
LBFD-002017 DRX • When LBFD-002017 DRX is enabled, parameters related to DRX are
restrained by uplink timing. For details, see DRX and Signaling Control
Feature Parameter Description. When both LBFD-002017 DRX and
LBFD-070101 Uplink Timing Based on PUCCH are enabled,
parameters related to DRX are no longer restrained by uplink timing,
and therefore the power consumption of UEs in the DRX state can
be further reduced.
• If LBFD-002017 DRX is enabled, the eNodeB receives CQIs in
PUCCH from UEs only when the UEs are in the DRX active time.
The timing offset measurement accuracy depends on the number of
CQIs in PUCCH received by the eNodeB. If the long DRX cycle
duration is greater than or equal to 160 ms, to ensure that the
eNodeB can measure a timing offset accurately before delivering the
Timing Advance Command, the Timing Advance Command sending
period must be extended to enable the eNodeB to obtain sufficient
CQIs in PUCCH. However, extending the Timing Advance
Command sending period decreases the supported mobility speed of
UEs.
• If the eNodeB does not receive a valid periodic CQI report within
eight consecutive periodic CQI reporting periods from a UE in DRX
sleep time, the eNodeB instructs the UE to send an aperiodic CQI
report in the DRX active time. The aperiodic CQI report must be sent
based on CQI_ONLY scheduling if the UE does not have uplink data
to transmit. CQI_ONLY scheduling consumes air interface resources
and reduces gains offered by LBFD-070101 Uplink Timing Based on
PUCCH.
LOFD-00110501 Dynamic DRX The impact of LBFD-070101 Uplink Timing Based on PUCCH on LOFD-
00110501 Dynamic DRX is the same as that on LBFD-002017 DRX.
5 Network Impact
stem Capacity
In LBFD-070101 Uplink Timing Based on PUCCH, when the eNodeB adopts the periodic decision and event triggering policy in the timing advance command, fewer control
channel elements (CCEs) in the PDCCH are consumed for measuring uplink timing offset based on DMRS for PUSCH, and therefore the PDCCH can support more UEs. The
number of reduced CCEs varies according to the number of users in a network, user distribution, and service type, and therefore cannot be quantified.
twork Performance
In LBFD-070101 Uplink Timing Based on PUCCH, when the eNodeB adopts the periodic decision and event triggering policy in the timing advance command, fewer physical
resource blocks (PRBs) in the PUSCH are consumed for measuring uplink timing offset based on DMRS for PUSCH, and the usage of PRB in the PUSCH decreases. However,
if a large number of UEs exist in a cell, the number of service drops and the number of E-RAB setup failures may increase slightly. The changes in the previously mentioned
counters vary according to site requirements and cannot be quantified. This is because the changes depend on the number of users in a network, UE distribution, and service
types.
When to Use
It is recommended that LBFD-070101 Uplink Timing Based on PUCCH be enabled when both the following conditions are met:
• The SRS resources cannot support uplink timing required by all the UEs in a cell. That is, the average number of uplink synchronized UEs is greater than the
average number of UEs allocated with SRS resources (the value of the L.Traffic.User.Ulsync.Avg counter is greater than the value of the L.Traffic.User.SRS.Avg
counter) or no SRS resources are available in the cell (the SRSCFG.SrsCfgInd parameter is set to BOOLEAN_FALSE(False)).
• Pre-scheduling does not take effect. When pre-scheduling or intelligent pre-scheduling is enabled, the eNodeB actively initiates uplink scheduling for UEs that are not
allocated SRS resources. In this situation, the eNodeB measures timing offsets of UEs based on the DMRS for PUSCH. If LBFD-070101 Uplink Timing Based on
PUCCH is enabled in this scenario, the eNodeB measures timing offsets of UEs based on both the DMRS for PUSCH and CQI in PUCCH. However, timing offsets
calculated based on DMRS for PUSCH are prioritized for uplink timing adjustment. In this situation, LBFD-070101 Uplink Timing Based on PUCCH offers lower
gains.
N/A
Planning
N/A
Deployment
6.4.1 Requirements

LBFD-070101 Uplink Timing Based on PUCCH must work with the LBBPd or UBBPd.
None
cense
None

quired Data
The following table describes the parameters that must be set in the TimeAlignmentTimer MO to configure the uplink timing measurement mode and the uplink time alignment
timer length.
Timing Measurement TimeAlignmentTimer.TimingMeasMode Network plan (negotiation not required) This parameter specifies the method of
Mode measuring uplink timing offsets.
• When this parameter is set to
INVALID(Invalid Timing
Measurement Mode), the eNodeB
measures the timing offset of the
UE based on the SRS or the
DMRS for PUSCH.
• When this parameter is set to
ALLMEASMODE(All Timing
Measurement Mode), the eNodeB
measures the timing offset of the
UE based on both the SRS and
DMRS for PUSCH or based on
both the CQIs in PUCCH and
DMRS for PUSCH.
The value ALLMEASMODE(All Timing
Measurement Mode) is recommended.
Uplink time alignment TimeAlignmentTimer.TimeAlignmentTimer Network plan (negotiation not required) This parameter specifies the length of the
timer uplink time alignment timer for UEs in the cell.
When the
TimeAlignmentTimer.TimingAdvCmdOptSwitch
parameter is set to ON, the value SF10240
(10240 subframes) is recommended for this
parameter.
Scenario 1: DRX is disabled, or DRX is enabled and the long DRX cycle is less than 160 ms.
The following table describes the parameters that must be set in the TimeAlignmentTimer MO to configure the uplink timing advance command optimization switch and TA
command sending period.
Uplink timing TimeAlignmentTimer.TimingAdvCmdOptSwitch Network plan (negotiation not If this parameter is set to ON(On), the eNodeB sends
advance command required) fewer Timing Advance Commands to motionless or low-
optimization switch mobility UEs to save air interface resources and reduce
power consumption for UEs in DRX mode. Therefore,
the parameter value ON(On) is recommended.
TA Command TimeAlignmentTimer.TACmdSendPeriod Network plan (negotiation not This parameter takes effect only when the
Sending Period required) TimeAlignmentTimer.TimingAdvCmdOptSwitch parameter
is set to ON(On). The default value SF928(928
subframes) is recommended.
Scenario 2: DRX is enabled and the long DRX cycle is greater than or equal to 160 ms.
In this scenario, the parameters listed in the following table must be configured in the TimeAlignmentTimer MO.
Uplink timing TimeAlignmentTimer.TimingAdvCmdOptSwitch Network plan (negotiation not If this parameter is set to ON(On), the eNodeB sends
advance command required) fewer Timing Advance Commands to motionless or low-
optimization switch mobility UEs to save air interface resources and reduce
power consumption for UEs in DRX mode. Therefore,
the parameter value ON(On) is recommended.
TA Command TimeAlignmentTimer.TACmdSendPeriod Network plan (negotiation not This parameter takes effect only when the
Sending Period required) TimeAlignmentTimer.TimingAdvCmdOptSwitch parameter
is set to ON(On). The parameter value SF5088(5088
subframes) is recommended.
sing the CME

sing MML Commands
1. Run the MOD TATIMER command to configure the timing measurement mode, length of the uplink time alignment timer, uplink Timing Advance Command
optimization switch, and TA command sending period.
1. Run the MOD TATIMER command to configure the timing measurement mode, length of the uplink time alignment timer, uplink Timing Advance Command
optimization switch, and TA command sending period.
ML Command Examples
MOD TATIMER: LocalCellId=0, TimingMeasMode=ALLMEASMODE, TimeAlignmentTimer=SF10240, TimingAdvCmdOptSwitch=ON, TACmdSendPeriod=SF
928;
MOD TATIMER: LocalCellId=0, TimingMeasMode=ALLMEASMODE, TimeAlignmentTimer=SF10240, TimingAdvCmdOptSwitch=ON, TACmdSendPeriod=SF
5088;
ing MML Commands
Run the LST TATIMER command on the eNodeB to verify that the TimingMeasMode parameter value is ALLMEASMODE and LBFD-070101 Uplink Timing based on PUCCH
has been activated.
ing Performance Counters
If the value of neither of the two counters listed in Table 6-1 is zero, LBFD-070101 Uplink Timing based on PUCCH takes effect.
Table 6-1 Counters related to uplink timing control
1526730143 L.Traffic.User.TAMeas.PUCCH.Avg This counter specifies the average number of users whose uplink timing
offsets are measured based on the PUCCH.
1526730144 L.Traffic.User.TAMeas.PUCCH.Max This counter specifies the maximum number of users whose uplink
timing offsets are measured based on the PUCCH.
6.4.5 Deactivation
ing the CME
ing MML Commands
1. Run the MOD TATIMER command to configure the timing measurement mode and the length of the uplink time alignment timer.
1. Run the MOD TATIMER command to configure the timing measurement mode, length of the uplink time alignment timer, and uplink Timing Advance Command
optimization switch.
ML Command Examples
If the Uplink timing advance command optimization switch parameter is set to OFF(Off), SF1920(1920 subframes) is recommended for the Uplink time alignment timer
parameter.
MOD TATIMER: LocalCellId=0, TimingMeasMode=INVALID, TimeAlignmentTimer=SF1920;
If the Uplink timing advance command optimization switch parameter is set to ON(On), SF10240(10240 subframes) is recommended for the Uplink time alignment timer
parameter.
MOD TATIMER: LocalCellId=0, TimingMeasMode=INVALID, TimeAlignmentTimer=SF10240;
MOD TATIMER: LocalCellId=0, TimingMeasMode=INVALID, TimeAlignmentTimer=SF10240, TimingAdvCmdOptSwitch=OFF;
The following table describes the parameters that must be set in the RrcConnStateTimer MO to configure the uplink synchronization timer length and the UE inactivity timer
length.
Parameter Name Parameter ID Source Setting Notes
Uplink Sync Timer RrcConnStateTimer.UlSynTimer Network plan (negotiation not This parameter indicates the timer used to govern the
required) period in which the eNodeB maintains uplink
synchronization for a UE. After this timer expires, the
eNodeB does not send Timing Advance Command to the
UE. The parameter value 180 is recommended.
Ue inactive timer RrcConnStateTimer.UeInactiveTimer Network plan (negotiation not This parameter indicates the length of the UE inactivity
required) timer for UEs that do not have QCI 1 bearers. The
parameter value 20 is recommended.
ML Command Examples
MOD RRCCONNSTATETIMER: UlSynTimer=180, UeInactiveTimer=20;
The operation of LBFD-070101 Uplink Timing Based on PUCCH can be monitored based on the counters in Table 6-2.
Table 6-2 Counters related to uplink timing control
1526730143 L.Traffic.User.TAMeas.PUCCH.Avg This counter specifies the average number of users whose
uplink timing offsets are measured based on the PUCCH.

1526730144 L.Traffic.User.TAMeas.PUCCH.Max This counter specifies the maximum number of users whose
uplink timing offsets are measured based on the PUCCH.
1526728764 L.ChMeas.PRB.PUSCH.Avg This counter specifies the number of used PRBs in the
PUSCH.
1526728304 L.ChMeas.CCE.ULUsed This counter specifies the number of CCEs in the PDCCH used
to carry DCIs for uplink transmission.
1526728566 to 1526728597 L.ChMeas.PUSCH.MCS.0~ L.ChMeas.PUSCH.MCS.31 These counters specify the number of times that MCS index 0
to 31 is scheduled on the PUSCH
After LBFD-070101 Uplink Timing Based on PUCCH is enabled, the uplink timing offsets of some UEs in a cell are measured based on the CQI in PUCCH, which reduces air
interface resources consumed by uplink timing offset measurement based on the DMRS for PUSCH. Therefore, do as follows:
• Observe the L.Traffic.User.TAMeas.PUCCH.Avg counter to obtain the average number of users whose uplink timing offsets are measured based on the PUCCH.
• Observe the L.Traffic.User.TAMeas.PUCCH.Max counter to obtain the maximum number of users whose uplink timing offsets are measured based on the PUCCH.
• Observe the L.ChMeas.PRB.PUSCH.Avg counter to verify that the number of used PRBs in the PUSCH decreases.
• Observe the L.ChMeas.CCE.ULUsed counter to verify that the number of CCEs in the PDCCH used to carry DCIs for uplink transmission decreases.
• Observe counters from L.ChMeas.PUSCH.MCS.0 to L.ChMeas.PUSCH.MCS.31 to verify that the number of scheduling times in the PUSCH decreases. The number of
scheduling times in the PUSCH is the value of the sum of counters from L.ChMeas.PUSCH.MCS.0 to L.ChMeas.PUSCH.MCS.31.
When DRX is enabled, scheduling request (SR) false detections cause unnecessary uplink scheduling, which consumes air interface resources and reduces gains generated by
LBFD-070101 Uplink Timing Based on PUCCH.
PUSCH DTX detection helps avoid unnecessary uplink scheduling caused by SR false detections. Therefore, if both DRX and LBFD-070101 Uplink Timing Based on PUCCH
are enabled, you are also advised to enable PUSCH DTX detection.
Possible Issues
None
7 Parameters
TimeAlignmentTimer TimingMeasMode MOD TATIMER LBFD- Uplink Meaning: Indicates the method of measuring uplink timing
LST TATIMER 070101 Timing offsets. If this parameter is set to INVALID, uplink timing offsets
Based on are measured based on the demodulation reference signal
PUCCH (DMRS) for PUSCH or sounding reference signal (SRS). If this
parameter is set to ALLMEASMODE, uplink timing offsets are
measured based on the DMRS for PUSCH and SRS or based
on the DMRS for PUSCH and channel quality indicator (CQI) in
PUCCH. In addition, the value ON of the
TimingAdvCmdOptSwitch parameter takes effect regardless of
the actual parameter setting. That is, the eNodeB always sends
the Timing Advance Command to UEs. In this case, it is
recommended that the TimeAlignmentTimer parameter be set to
SF10240. The value ALLMEASMODE applies only to LTE FDD
cells. The parameter value INVALID takes effect in a cell
regardless of the actual parameter setting in any of the following
scenarios: (1) The cell is established on an LBBPc. (2) The
UlCyclicPrefix parameter is set to EXTENDED_CP. (3) The
HighSpeedFlag parameter is set to HIGH_SPEED,
ULTRA_HIGH_SPEED, or EXTRA_HIGH_SPEED. (4) The
TX/RX mode of the cell is 2T8R.
GUI Value Range: INVALID(Invalid Timing Measurement Mode),
ALLMEASMODE(All Timing Measurement Mode)
Unit: None
Actual Value Range: INVALID, ALLMEASMODE
Default Value: INVALID(Invalid Timing Measurement Mode)
TimeAlignmentTimer TimingResOptSwitch MOD TATIMER None None Meaning: Indicates whether to enable the mechanism of
LST TATIMER optimized resource scheduling for uplink timing.If this parameter
is set to OFF, the eNodeB adopts the existing resource
scheduling policy for uplink timing, which consumes a large
amount of resources used for delivering Timing Advance
Commands in large traffic scenarios.If this parameter is set to
ON, the eNodeB adopts the mechanism of optimized resource
scheduling for uplink timing, which reduces the number of
unnecessary Timing Advance Commands to be delivered and
reduces resources allocated for uplink timing in large traffic
scenarios.This parameter applies only to LTE FDD cells. The
parameter value ON is recommended in heavily loaded cells
where there is a large number of UEs.
Unit: None
TimeAlignmentTimer TaEnhance MOD TATIMER None None Meaning:

LST TATIMER Indicates whether to enable enhanced TA.
TaEnhancePuschDmrs: If this option is selected, enhanced TA
is enabled, and uplink-synchronization-induced overloads over


the air interface decrease. If this option is deselected, enhanced
TA is disabled.
This parameter does not take effect in the following scenarios: 1.
The FddTddInd parameter in the Cell MO is set to CELL_TDD
(TDD).
2. The baseband processing unit type is the LBBPc.
3. The HoppingMode parameter in the PUSCHCfg MO is set to
INTRA_AND_INTER_SUB_FRAME(Inter And Intra).
4. The HighSpeedFlag parameter in the Cell MO is set to
HIGH_SPEED(High speed cell flag), ULTRA_HIGH_SPEED
(Ultra high speed cell flag), or EXTRA_HIGH_SPEED(Extra high
speed cell flag).
5. The TimingResOptSwitch parameter in the
TimeAlignmentTimer MO is set to OFF.
GUI Value Range: TaEnhancePuschDmrs
(TaEnhancePuschDmrs)
Unit: None
Actual Value Range: TaEnhancePuschDmrs
Default Value: TaEnhancePuschDmrs:Off
TimeAlignmentTimer TimingAdvCmdOptSwitch MOD TATIMER None None Meaning:

LST TATIMER Indicates whether optimization of the mechanism for delivering
the uplink time alignment command takes effect. If the
optimization takes effect, the number of unnecessary uplink time
alignment commands delivered to motionless or low-mobility
UEs can be reduced to save air interface resources and reduce
power consumption of UEs in DRX mode. This ensures the
uplink time alignment performance if the length of the uplink time
alignment timer is set to a large value.
If this parameter is set to ON, it is recommended that the
TimeAlignmentTimer parameter be set to SF10240. A smaller
value of the TimeAlignmentTimer parameter, such as SF5120,
leads to a higher probability of becoming out-of-synchronization
in the uplink for UEs in DRX mode.
If this parameter is set to ON, it is recommended that the
LongDrxCycle parameter be smaller than or equal to SF320.
Otherwise, the uplink time alignment performance of UEs in
DRX mode is affected.
Unit: None
TimeAlignmentTimer TACmdSendPeriod MOD TATIMER None None Meaning: Indicates the interval for sending the Timing Advance
LST TATIMER Command to UEs. This parameter needs to be set only when
the TimingAdvCmdOptSwitch parameter is set to ON. If this
parameter is set to Invalid, none of parameter settings in the
MML Command window takes effect.This parameter applies
only to LTE FDD cells.
GUI Value Range: INVALID(NULL), SF218(218 subframes),
SF343(343 subframes), SF608(608 subframes), SF928(928
subframes), SF1248(1248 subframes), SF2528(2528
subframes), SF5088(5088 subframes)
Unit: None
Actual Value Range: INVALID, SF218, SF343, SF608, SF928,
SF1248, SF2528, SF5088
Default Value: SF928(928 subframes)
TimeAlignmentTimer TimeAlignmentTimer MOD TATIMER None None Meaning: Indicates the length of the uplink time alignment timer
LST TATIMER for UEs in the cell. A UE is considered not time-aligned in the
uplink if the timer expires.
GUI Value Range: SF500(500 subframes), SF750(750
subframes), SF10240(10240 subframes), INFINITY(Infinity)
Unit: None
Actual Value Range: SF500, SF750, SF1280, SF1920, SF2560,
SF5120, SF10240, INFINITY
Default Value: INFINITY(Infinity)
RrcConnStateTimer UlSynTimer MOD LBFD- RRC Meaning: Indicates the timer used to govern the period in which
RRCCONNSTATETIMER 002007 / Connection the eNodeB maintains uplink synchronization for UEs. After this
LST TDLBFD- Management timer expires, the eNodeB does not send Timing Advance
RRCCONNSTATETIMER
002007 Command to the UE. This parameter does not take effect if it is
set to 0. That is, the eNodeB will constantly send Timing
Advance Command to the UE to maintain uplink synchronization
for the UE. If the QciParaEffectFlag parameter is set to ON(ON),
this parameter does not take effect but the UlSynTimerForQci
parameter in the QciPara MO takes effect.
Unit: s
Default Value: 180
RrcConnStateTimer UeInactiveTimer MOD LBFD- RRC Meaning: Indicates the length of the UE inactivity timer for UEs
RRCCONNSTATETIMER 002007 / Connection that have no QCI 1 bearers. If the eNodeB detects that a UE has
LST TDLBFD- Management neither received nor sent data for a period exceeding the value
RRCCONNSTATETIMER
002007 of this parameter, the eNodeB releases the RRC connection for
this UE. If this parameter is set to 0, the UE inactivity timer is not
used. This parameter takes effect only for UEs that will access


the network after the parameter is set. If the QciParaEffectFlag
parameter is set to ON(ON), this parameter does not take effect
but the UeInactiveTimerForQci parameter in the QciPara MO
takes effect.
Unit: s
Default Value: 20
Cell HighSpeedFlag ADD CELL LOFD- High Speed Meaning: Indicates the speed flag of the cell. Set this parameter
MOD CELL 001007 / Mobility to HIGH_SPEED if the cell is used to provide coverage for a
LST CELL TDLOFD- Ultra High high-speed railway. Set this parameter to LOW_SPEED in other
001007 Speed scenarios. TDD cells with a bandwidth of 5 MHz or in 8T8R
LOFD- Mobility mode can only be configured as low-speed cells. TDD cells
001008 cannot be configured as ultra-high-speed cells.
GUI Value Range: LOW_SPEED(Low speed cell flag),
HIGH_SPEED(High speed cell flag), ULTRA_HIGH_SPEED
(Ultra high speed cell flag), EXTRA_HIGH_SPEED(Extra high
speed cell flag)
Unit: None
Actual Value Range: LOW_SPEED, HIGH_SPEED,
ULTRA_HIGH_SPEED, EXTRA_HIGH_SPEED
Default Value: LOW_SPEED(Low speed cell flag)
Cell UlCyclicPrefix ADD CELL LBFD- Normal CP Meaning: Indicates the UL cyclic prefix length of a cell. A cyclic
MOD CELL 00100401 / Extended prefix can be a common or extended cyclic prefix. An extended
LST CELL TDLBFD- CP cyclic prefix is generally used in a complex environment with a
00100401 Broadcast of strong multi-path effect and long delay. In a cell, the UL cyclic
LOFD- system prefix length can be different from the DL one. In addition, the
001031 / information UL or DL cyclic prefix length of a cell must be the same as that
TDLOFD- of the cell using the same BBP. For details, see 3GPP TS
001031 36.211.
LBFD- GUI Value Range: NORMAL_CP(Normal), EXTENDED_CP
002009 / (Extended)
TDLBFD- Unit: None
002009 Actual Value Range: NORMAL_CP, EXTENDED_CP
SRSCfg SrsCfgInd MOD SRSCFG LBFD- Physical Meaning: Indicates whether to configure sounding reference
LST SRSCFG 002003 / Channel signal (SRS) resources for UEs in a cell. The value
TDLBFD- Management BOOLEAN_TRUE indicates that SRS resources are available in
002003 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.
GUI Value Range: BOOLEAN_FALSE(False),
BOOLEAN_TRUE(True)
Unit: None
Actual Value Range: BOOLEAN_FALSE, BOOLEAN_TRUE
8 Counters
Table 8-1 Counters
1526727412 L.ChMeas.PUSCH.MCS.0 Number of times MCS index 0 Multi-mode: None Basic Scheduling
is scheduled on the PUSCH GSM: None Modulation: DL/UL QPSK,
UMTS: None DL/UL 16QAM, DL 64QAM
LBFD-001005 Modulation: DL/UL QPSK,
TDLBFD-002025 DL/UL 16QAM, DL 64QAM
TDLBFD-001005
1526727443 L.ChMeas.PUSCH.MCS.31 Number of times MCS index Multi-mode: None Basic Scheduling
31 is scheduled on the GSM: None Basic Scheduling
PUSCH UMTS: None Modulation: DL/UL QPSK,
LTE: LBFD-002025 DL/UL 16QAM, DL 64QAM
TDLBFD-002025 Modulation: DL/UL QPSK,
LBFD-001005 DL/UL 16QAM, DL 64QAM
TDLBFD-001005 UL 64QAM
LOFD-001006 UL 64QAM
TDLOFD-001006
1526728304 L.ChMeas.CCE.ULUsed Number of PDCCH CCEs Multi-mode: None Physical Channel

used for uplink DCI in a GSM: None Management
measurement period


TDLBFD-002003
1526728333 L.Traffic.User.Ulsync.Avg Average number of UL Multi-mode: None RRC Connection

synchronized users in a cell GSM: None Management
TDLBFD-002007

LTE: LBFD-002007
TDLBFD-002007
1526728764 L.ChMeas.PRB.PUSCH.Avg Average number of used Multi-mode: None Basic Scheduling

PUSCH PRBs GSM: None Basic Scheduling
UMTS: None Adaptive SFN/SDMA
LTE: LBFD-002025
TDLBFD-002025
LOFD-070205
1526730143 L.Traffic.User.TAMeas.PUCCH.Avg Average number of UEs Multi-mode: None Uplink Timing Based on
whose uplink timing offsets GSM: None PUCCH
are measured based on the UMTS: None
PUCCH
LTE: LBFD-070101
1526730144 L.Traffic.User.TAMeas.PUCCH.Max Maximum number of UEs Multi-mode: None Uplink Timing Based on
whose uplink timing offsets GSM: None PUCCH
are measured based on the UMTS: None
PUCCH
LTE: LBFD-070101
9 Glossary
1. 3GPP TS 36.213, "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures"
2. 3GPP TS 36.321, "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control"
3. DRX and Signaling Control Feature Parameter Description
5. Connection Management Feature Parameter Description

Huawei 4G Eran 11.1

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Huawei 4G Eran 11.1

Caricato da

Copyright:

Formati disponibili

HedEx Startpage Page 1 of 510

eRAN Feature Documentation

For any question, please contact us.

HUAWEI TECHNOLOGIES CO., LTD.

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

http://localhost:7890/printtopics.html?time=Mon May 28 16:10:20 UTC+0530 2018 5/28/2018

Huawei Technologies Co., Ltd.

http://localhost:7890/printtopics.html?time=Mon May 28 16:10:20 UTC+0530 2018 5/28/2018

1 About This Document

eNodeB Type Model

Macro 3900 series eNodeB

• Need to understand the features described herein

This issue includes the following changes.

Change Type Change Description Parameter Change

Feature change None None

Editorial change Revised the descriptions in 1.1 Scope. None

This issue includes the following changes.

Change Type Change Description Parameter Change

Feature change None None

Editorial change Revised descriptions in the document. None

This issue includes the following changes.

Change Type Change Description Parameter Change

Editorial change Revised the descriptions in 6.4.2 Requirements. None

This issue includes the following changes.

Change Type Change Description Parameter Change

Editorial change None None

This issue does not include any changes.

AN11.1 Draft A (2015-11-30)

Change Type Change Description Parameter Change Affected Entity

Feature change Added pRRU3911 configuration descriptions. None LampSite eNodeBs

http://localhost:7890/printtopics.html?time=Mon May 28 16:10:20 UTC+0530 2018 5/28/2018

Change Type Change Description Parameter Change Affected Entity

Editorial change None None N/A

Differences Between eNodeB Types

ature Support by Macro, Micro, and LampSite eNodeBs

LBFD-001003 Scalable Bandwidth Yes Yes Yes

nction Implementation in Macro, Micro, and LampSite eNodeBs

http://localhost:7890/printtopics.html?time=Mon May 28 16:10:20 UTC+0530 2018 5/28/2018

Figure 3-1 Cell-related concepts

Sector Type Definition Benefits

3.1.3 Sector Equipment

3.1.5 Baseband Equipment

http://localhost:7890/printtopics.html?time=Mon May 28 16:10:20 UTC+0530 2018 5/28/2018

3.1.6 Cell-specific Sector Equipment

• Establishing a cell in a common sector

3.2.1 Establishing a Cell in a Common Sector

Figure 3-2 A cell established in a common sector

3.2.2 Establishing Cells in Multiple Sectors with RRU/RFU Splitting

3.2.3 Establishing a Cell in a Single Sector with RRU/RFU Combination

3.2.4 Establishing a Cell in Multiple Sectors Served by Different RRUs

http://localhost:7890/printtopics.html?time=Mon May 28 16:10:20 UTC+0530 2018 5/28/2018

Cell Type Description Applicable eNodeBs

3.3.1 Frequency Band

1 1920 MHz 1980 MHz 2110 MHz 2170 MHz

2 1850 MHz 1910 MHz 1930 MHz 1990 MHz

3 1710 MHz 1785 MHz 1805 MHz 1880 MHz

4 1710 MHz 1755 MHz 2110 MHz 2155 MHz

5 824 MHz 849 MHz 869 MHz 894 MHz

61 830 MHz 840 MHz 875 MHz 885 MHz

7 2500 MHz 2570 MHz 2620 MHz 2690 MHz

8 880 MHz 915 MHz 925 MHz 960 MHz

9 1749.9 MHz 1784.9 MHz 1844.9 MHz 1879.9 MHz

10 1710 MHz 1770 MHz 2110 MHz 2170 MHz