4 G

eRAN
DRX and Signaling Control Feature

Parameter Description
Issue 03
Date 2017-12-06
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2017. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 03 (2017-12-06) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
eRAN
DRX and Signaling Control Feature Parameter Description Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 2
1.3 Change History............................................................................................................................................................... 2
1.4 Differences Between eNodeB Types.............................................................................................................................. 4
2 Overview......................................................................................................................................... 5
3 Technical Description...................................................................................................................7
3.1 LBFD-002017 DRX....................................................................................................................................................... 7
3.1.1 Overview..................................................................................................................................................................... 7
3.1.1.1 Definition and Application Scenarios.......................................................................................................................7
3.1.1.2 Benefits..................................................................................................................................................................... 7
3.1.1.3 DRX Process.............................................................................................................................................................8
3.1.2 DRX Parameter Configuration at Different Levels..................................................................................................... 9
3.1.2.1 QCI-Level DRX Parameter Configuration...............................................................................................................9
3.1.2.2 QCI-Level DRX Parameter Configuration for Different UE Models.................................................................... 11
3.1.3 Entry and Exit Conditions..........................................................................................................................................11
3.1.3.1 Entry Conditions..................................................................................................................................................... 11
3.1.3.2 Exit Conditions....................................................................................................................................................... 12
3.1.4 Working Mechanism..................................................................................................................................................12
3.1.4.1 Related Concepts.................................................................................................................................................... 12
3.1.4.2 Startup of a DRX Cycle..........................................................................................................................................14
3.1.4.3 Operation in a DRX Cycle......................................................................................................................................15
3.1.4.3.1 Operation in Active Time.................................................................................................................................... 15
3.1.4.3.2 Switching Between Active Time and Sleep Time............................................................................................... 18
3.1.4.4 Switching Between Long and Short Cycles........................................................................................................... 20
3.1.4.5 DRX for GERAN Measurement.............................................................................................................................20
3.1.5 DRX Parameters for Various Scenarios.....................................................................................................................21
3.1.5.1 DRX Parameters for VoLTE................................................................................................................................... 23
3.1.5.2 DRX Parameters for Special UEs...........................................................................................................................25
3.1.5.3 DRX Parameters for ANR Measurement............................................................................................................... 26
3.1.5.4 SRI Offset Reconfiguration for DRX..................................................................................................................... 26
3.2 LOFD-00110501 Dynamic DRX..................................................................................................................................26
Issue 03 (2017-12-06) Huawei Proprietary and Confidential ii

eRAN
3.2.1 Introduction............................................................................................................................................................... 26
3.2.1.1 Definition and Application Scenarios.....................................................................................................................26
3.2.1.2 Benefits................................................................................................................................................................... 27
3.2.1.3 Dynamic DRX Process........................................................................................................................................... 27
3.2.2 Entry and Exit Conditions......................................................................................................................................... 29
3.2.2.1 Entry Conditions.....................................................................................................................................................29
3.2.2.2 Exit Conditions....................................................................................................................................................... 30
3.2.3 Principles................................................................................................................................................................... 30
3.3 LOFD-00110502 High-Mobility-Triggered Idle Mode................................................................................................32
3.3.1 Introduction............................................................................................................................................................... 32
3.3.1.1 Definition and Application Scenarios.....................................................................................................................32
3.3.1.2 Benefits................................................................................................................................................................... 32
3.3.2 Principles................................................................................................................................................................... 33
4 Related Features...........................................................................................................................36
4.1 LBFD-002017 DRX..................................................................................................................................................... 36
4.2 LOFD-00110501 Dynamic DRX..................................................................................................................................42
5 Network Impact........................................................................................................................... 44
5.1 LBFD-002017 DRX..................................................................................................................................................... 44
5.2 LOFD-00110501 Dynamic DRX..................................................................................................................................47
6 Engineering Guidelines............................................................................................................. 50
6.1 Engineering Guidelines for LBFD-002017 DRX.........................................................................................................50
6.1.1 When to Use.............................................................................................................................................................. 50
6.1.2 Required Information................................................................................................................................................ 50
6.1.3 Planning..................................................................................................................................................................... 50
6.1.4 Deployment............................................................................................................................................................... 51
6.1.4.1 Requirements.......................................................................................................................................................... 51
6.1.4.2 Precautions..............................................................................................................................................................51
6.1.4.3 Hardware Adjustment.............................................................................................................................................51
6.1.4.4 Activation............................................................................................................................................................... 51
6.1.4.4.1 Data Preparation.................................................................................................................................................. 51
6.1.4.4.2 Using the CME.................................................................................................................................................... 64
6.1.4.4.3 Using MML Commands...................................................................................................................................... 64
6.1.4.5 Activation Observation...........................................................................................................................................67
6.1.4.6 Reconfiguration...................................................................................................................................................... 71
6.1.4.7 Deactivation............................................................................................................................................................71
6.1.4.7.1 Using the CME.................................................................................................................................................... 72
6.1.5 Maintenance...............................................................................................................................................................72
6.1.5.1 Performance Monitoring.........................................................................................................................................72
Issue 03 (2017-12-06) Huawei Proprietary and Confidential iii

eRAN
6.1.5.2 Parameter Optimization.......................................................................................................................................... 73

6.1.5.3 Possible Issues........................................................................................................................................................ 74
6.2 Engineering Guidelines for LOFD-00110501 Dynamic DRX..................................................................................... 75
6.2.1 When to Use.............................................................................................................................................................. 75
6.2.3 Planning..................................................................................................................................................................... 77
6.2.4 Deployment............................................................................................................................................................... 77
6.2.4.1 Requirements.......................................................................................................................................................... 77
6.2.4.2 Precautions..............................................................................................................................................................78
6.2.4.4 Activation............................................................................................................................................................... 78
6.2.4.4.2 Using the CME.................................................................................................................................................... 81
6.2.4.7 Deactivation............................................................................................................................................................84
6.2.4.7.1 Using the CME.................................................................................................................................................... 84
6.2.5 Maintenance...............................................................................................................................................................84
6.2.5.3 Possible Issues........................................................................................................................................................ 88
6.3 Engineering Guidelines for LOFD-00110502 High-Mobility-Triggered Idle Mode................................................... 88
6.3.1 When to Use.............................................................................................................................................................. 89
6.3.3 Planning..................................................................................................................................................................... 89
6.3.4 Deployment............................................................................................................................................................... 89
6.3.4.1 Requirements.......................................................................................................................................................... 89
6.3.4.2 Precautions..............................................................................................................................................................90
6.3.4.4 Activation............................................................................................................................................................... 90
6.3.4.4.2 Using the CME.................................................................................................................................................... 90
6.3.4.7 Deactivation............................................................................................................................................................91
6.3.4.7.1 Using the CME.................................................................................................................................................... 91
6.3.5 Maintenance...............................................................................................................................................................91
Issue 03 (2017-12-06) Huawei Proprietary and Confidential iv

eRAN

6.3.5.3 Possible Issues........................................................................................................................................................ 92
7 Parameters..................................................................................................................................... 93
8 Counters...................................................................................................................................... 167
9 Glossary....................................................................................................................................... 182
10 Reference Documents............................................................................................................. 183
Issue 03 (2017-12-06) Huawei Proprietary and Confidential v

eRAN
DRX and Signaling Control Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes discontinuous reception (DRX) and signaling control, including its
technical principles, related features, network impact, and engineering guidelines. This
document covers the following features:
l LBFD-002017 DRX
l LOFD-00110501 Dynamic DRX
l LOFD-00110502 High-Mobility-Triggered Idle Mode
Feature compatibility with specific terminal models is not presented in this document. For
compatibility information, contact Huawei engineers.
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 and 5900 series base stations
Micro BTS3202E
BTS3203E
BTS3911E
BTS3912E
LampSite DBS3900 LampSite and DBS5900 LampSite
Issue 03 (2017-12-06) Huawei Proprietary and Confidential 1

eRAN
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein
l Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes:
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.
eRAN12.1 03 (2017-12-06)
This issue includes the following changes.
Change Change Description Parameter Affected

Type Change Entity
Feature None None Macro, micro,

change and LampSite
eNodeBs
Editorial Revised descriptions in this None N/A

change document.
eRAN12.1 02 (2017-08-30)
This issue includes the following changes.

eRAN

Type Change Entity
Feature Added description of the mapping None Macro, micro,

change between extended QCIs and and LampSite
standardized QCIs as well as eNodeBs
related parameters in DRX mode.
For details, see the following
sections:
l 3.1.2.1 QCI-Level DRX
Parameter Configuration
l 6.1.4.4.1 Data Preparation
l 6.1.4.4.3 Using MML
Commands
Added information: Settings of None Macro, micro,

both the eNodeB-level DRX and LampSite
parameter Drx.DrxAlgSwitch and eNodeBs
the cell-level DRX parameter
CellDrxPara.DrxAlgSwitch are
supported in this version. When
both of the parameters are set, the
setting of the eNodeB-level DRX
parameter takes effect. For
details, see the following
sections:
l 6.1.4.4.1 Data Preparation
l 6.1.4.4.3 Using MML
Commands
Editorial Revised descriptions in this None N/A

change document.
eRAN12.1 01 (2017-03-08)
This issue does not include any changes.
eRAN12.1 Draft A (2016-12-30)

Draft A (2016-12-30) of eRAN12.1 introduces the following changes to Issue 01
(2016-03-07) of eRAN11.1.

Type Change Entity
Feature Added PUCCH CQI detection None Macro, micro,

change reliability optimization in DRX and LampSite
mode. For details, see "Impacted eNodeBs
Features" in 4.1 LBFD-002017
DRX.

eRAN

Type Change Entity
Supported DRX parameter None Macro, micro,

configuration for different UE and LampSite
models. For details, see 3.1.2.2 eNodeBs
QCI-Level DRX Parameter
Configuration for Different UE
Models.
Optimized the processing None Macro, micro,

mechanism in the DRX entry and LampSite
phase. For details, see 3.1.1.3 eNodeBs
DRX Process.
Editorial Revised descriptions in 3.1.2 None N/A

change DRX Parameter Configuration
at Different Levels.
1.4 Differences Between eNodeB Types

Feature Support by Macro, Micro, and LampSite eNodeBs
Feature ID Feature Supported by Supported by Supported by
Name Macro Micro LampSite
eNodeBs eNodeBs eNodeBs
LBFD-002017 DRX Yes Yes Yes
LOFD-001105 Dynamic DRX Yes Yes Yes

01
LOFD-001105 High-Mobility- Yes Yes No

02 Triggered Idle
Mode
Function Implementation in Macro, Micro, and LampSite eNodeBs

The function described in this document is implemented in the same way on macro, micro,
and LampSite eNodeBs.

eRAN
DRX and Signaling Control Feature Parameter Description 2 Overview
2 Overview
This document covers the following features:

l LBFD-002017 DRX
The standby time of user equipment (UE) has become a major concern for end users. To
reduce UE power consumption, 3GPP introduced discontinuous reception (DRX) for
LTE. Accordingly, Huawei eNodeBs provide the LBFD-002017 DRX feature.
l LOFD-00110501 Dynamic DRX
Many smart-terminal applications use small, sparse packets or heartbeat packets. These
applications cause networks to frequently release and reestablish radio resource control
(RRC) connections, increasing signaling. Staying in connected mode for an extended
period consumes UE power. The Huawei feature LOFD-00110501 Dynamic DRX allows
UEs to enter power saving or reduced signaling mode based on UE power consumption
and network load.
l LOFD-00110502 High-Mobility-Triggered Idle Mode
When UEs in connected mode are moving at high speeds, frequent handovers occur.
When there are a large number of such UEs, excessive signaling strains the network. To
reduce the signaling, Huawei eNodeBs use the LOFD-00110502 High-Mobility-
Triggered Idle Mode feature.
Table 2-1 describes the application scenarios and benefits of these features.

eRAN
DRX and Signaling Control Feature Parameter Description 2 Overview
Table 2-1 Application scenarios and benefits

Feature Recommende Application Scenario Benefit
Name d UE Type
LBFD-002017 l Smart l Periodic transmission of Reduces UE power

DRX terminals continuous small packets, consumption.
l Non-smart such as voice over IP
terminals (VoIP) services
l Delay-insensitive services,
such as HTML web page
browsing and email
l Services characterized by
small, sparse packets, such
as Presence services
l Automatic neighbor
relation (ANR)
measurement
LOFD-00110 Smart terminals l Services characterized by l Reduces signaling

501 Dynamic small, sparse packets storms caused by
DRX l Services characterized by frequent RRC
heartbeat packets, such as connection
the Microsoft Service releases and
Network (MSN) reestablishments
for these services.
l Reduces UE power
consumption.
LOFD-00110 Smart terminals Terminals remain in Reduces signaling

502 High- connected mode for long storms caused by
Mobility- periods with frequent handovers of UEs
Triggered Idle handovers moving at high
Mode speeds.
NOTE
l Presence services, such as MSN presence notices, allow end users to obtain real-time presence
information based on a certain communication methods and access policies. Presence information
can be user availability status, personal notes, or other personal information.
l "UE" and "terminal" in this document have the same meaning.

eRAN
DRX and Signaling Control Feature Parameter Description 3 Technical Description
3 Technical Description
3.1 LBFD-002017 DRX

This section describes the principles of LBFD-002017 DRX. For engineering guidelines, see
6.1 Engineering Guidelines for LBFD-002017 DRX.
NOTE
"DRX" in this document refers to DRX for UEs in connected mode. DRX for UEs in idle mode is
different, which is described in Idle Mode Management Feature Parameter Description.
3.1.1 Overview
3.1.1.1 Definition and Application Scenarios
Definition
DRX is a technology in which a UE can switch between active and sleep states. When the UE
needs to receive downlink (DL) data or signaling, the UE turns on its receiver and enters the
active state. In other situations, the UE turns off its receiver and enters the sleep state to
reduce power consumption.
In DRX mode, a DRX cycle consists of active time and sleep time, which correspond
respectively to the active state and sleep state. In non-DRX mode, the UE keeps its receiver
on and stays in the active state. For explanations of the DRX cycle, active time, and sleep
time, see 3.1.4.1 Related Concepts.
Application Scenarios
For application scenarios, see Table 2-1.
3.1.1.2 Benefits
DRX provides the following advantages over continuous reception:

eRAN
l Reduces power consumption and prolongs the standby time of the UE. The UE does not
need to constantly monitor the physical downlink control channel (PDCCH). The UE can
turn off its receiver and other communication modules.
l Allows the UE to perform ANR measurement during the sleep time in DRX.
NOTE
l When a UE is in DRX mode, the extended standby time depends on the UE model, traffic model,
and DRX parameter settings. UEs from certain vendors do not need to constantly monitor the
PDCCH, but they cannot turn off their RF modules. Therefore, the power saving effect on such UEs
is limited.
l Performance preference or power saving preference can be configured using DRX parameters. For
details, see 6.1.4.4.3 Using MML Commands.
l Scheduling request indicator (SRI) offset reconfiguration for DRX can be used to save more UE
power. For a given UE, it can reduce UE power consumption by up to 12.3%. For details, see 3.1.5.4
SRI Offset Reconfiguration for DRX. However, this function also has certain negative impact. For
details, see 5.1 LBFD-002017 DRX.
3.1.1.3 DRX Process

Figure 3-1 shows the DRX process.
Figure 3-1 DRX process

eRAN
1. DRX entry phase

After the UE accesses the network, the eNodeB checks whether the UE meets the
conditions for entering DRX mode. When the conditions are met, the eNodeB sends the
UE an RRC Connection Reconfiguration message with the DRX-Configuration
information element (IE) set to setup. The UE then enters DRX mode based on
parameters in this IE. For the DRX entry conditions, see 3.2.2.1 Entry Conditions.
NOTE
To address the compatibility issue caused by nonstandard CQI reporting occasions in earlier
protocols, the eNodeB performs the following operations regardless of the
CellCqiAdaptiveCfg.SimulAckNackAndCqiSwitch parameter setting:
If the CellDrxPara.CqiMask parameter is set to ON, the eNodeB sets the
simultaneousAckNackAndCQI IE to False when delivering an RRC Connection
Reconfiguration message to a UE in compliance with 3GPP Release 8 or earlier; however, the
eNodeB does not do so for a UE in compliance with a release later than 3GPP Release 8.
If the CellDrxPara.CqiMask parameter is set to OFF, the 3GPP releases that UEs comply with
are not considered.
l If the DrxSimulAckNackAndCqiSwitch option of the CellAlgoSwitch.EmimoSwitch
parameter is selected and the cell is configured with more than two transmit antennas, the
eNodeB sets simultaneousAckNackAndCQI to True in the delivered RRC Connection
Reconfiguration message for non-CA UEs. For CA UEs, the value of
simultaneousAckNackAndCQI is determined by the CaCqiAndAckAbnCtrlSwitch option
of the ENodeBAlgoSwitch.CompatibilityCtrlSwitch parameter.
l If the DrxSimulAckNackAndCqiSwitch option of the CellAlgoSwitch.EmimoSwitch
parameter is deselected, the eNodeB sets simultaneousAckNackAndCQI to False in the
delivered RRC Connection Reconfiguration message.
2. DRX execution phase
After the UE enters DRX mode, the eNodeB instructs the UE to switch between active
and sleep states as well as between long and short DRX cycles based on network
conditions and parameter settings. For details, see 3.1.4.3.2 Switching Between Active
Time and Sleep Time and 3.1.4.4 Switching Between Long and Short Cycles.
3. DRX exit phase
The eNodeB checks whether the UE meets the conditions for exiting DRX mode. When
the conditions are met, the eNodeB sends the UE an RRC Connection Reconfiguration
message with the DRX-Configuration IE set to release. After the UE receives the
message, it immediately clears all the DRX parameters stored locally and exits DRX
mode. For the conditions for exiting DRX mode, see 3.2.2.2 Exit Conditions.
3.1.2 DRX Parameter Configuration at Different Levels
3.1.2.1 QCI-Level DRX Parameter Configuration

Services with different QoS class identifiers (QCIs) have different characteristics. A DRX
parameter group can be set for each QCI. Each group is identified by the
CellQciPara.DrxParaGroupId parameter value and includes the following parameters:
l QCI-level DRX switch: DrxParaGroup.EnterDrxSwitch
For details about how to use this parameter, see 3.1.3 Entry and Exit Conditions.
l QCI-level parameters related to DRX timers:
– DrxParaGroup.OnDurationTimer
– DrxParaGroup.DRXInactivityTimer

eRAN
– DrxParaGroup.DRXReTxTimer
– DrxParaGroup.LongDrxCycle
– DrxParaGroup.ShortDrxCycle
– DrxParaGroup.DrxShortCycleTimer
– DrxParaGroup.SupportShortDrx
For details about how to use these parameters, see 3.1.4 Working Mechanism.
If a UE has multiple bearers with different QCIs, the DRX parameter group is determined by
the CellDrxPara.DrxPolicyMode parameter setting.
For an extended QCI, the DRX parameter group is determined as follows. First, this QCI is
mapped to a standardized QCI based on its QciPara.ServiceType parameter value, which may
be IMSSignalling, LowDelay, or TCPorBuffStreaming, corresponding to standardized QCI
5, 7, or 9, respectively. Then, the standardized QCI is mapped to a DRX parameter group
based on the CellQciPara.DrxParaGroupId parameter value.
Table 3-1 lists the standardized QCIs and the corresponding service types.
Table 3-1 QCIs and the corresponding service types
QC Bearer Priorit Packet Packet Example Service

I Type y Delay Error
Budge Loss
t Rate
(PDB) (PELR
)
1 Guaranteed 2 100 ms 10-2 Conversational voice

bit rate
2 (GBR) 4 150 ms 10-3 Conversational video, such as live
streaming
3 3 50 ms 10-3 Real-time gaming
4 5 300 ms 10-6 Non-conversational video, such as

buffered streaming
65 0.7 75 ms 10-2 Mission-critical user-plane push-to-talk

voice, such as Mission Critical Push To
Talk (MCPTT)
66 2 100 ms 10-2 Non-mission-critical user-plane push-

to-talk voice
5 Non-GBR 1 100 ms 10-6 IP Multimedia Subsystem (IMS)

signaling
6 6 300 ms 10-6 Video (such as buffered streaming) and

TCP-based services (such as web
browsing, email, chat, and point-to-
point services)
7 7 100 ms 10-3 Voice, video (such as live streaming),

and interactive gaming

eRAN
QC Bearer Priorit Packet Packet Example Service

I Type y Delay Error
Budge Loss
t Rate
(PDB) (PELR
)
8 8 300 ms 10-6 Video (such as buffered streaming) and

TCP-based services (such as web
9 9 browsing, email, chat, and point-to-
point services)
69 0.5 60 ms 10-6 Mission-critical delay-sensitive

signaling, such as MCPTT signaling
70 5.5 200 ms 10-6 Mission-critical data (the example

services are the same as those for QCIs
6, 8, and 9)
3.1.2.2 QCI-Level DRX Parameter Configuration for Different UE Models

This function is an enhancement to LBFD-081103 Terminal Awareness Differentiation. For
details, see Terminal Awareness Differentiation Feature Parameter Description.
3.1.3 Entry and Exit Conditions

UEs enter or exit DRX mode after receiving instructions from the eNodeB. This section
describes the conditions for entering and exiting DRX mode.
3.1.3.1 Entry Conditions

The DRX functionality is jointly controlled by the general DRX switch
CellDrxPara.DrxAlgSwitch and the QCI-specific DRX switch
DrxParaGroup.EnterDrxSwitch.
The UE enters DRX mode when all the following conditions are met:
l The CellDrxPara.DrxAlgSwitch parameter is set to ON.
l All the established bearers for the UE support DRX. That is, the
DrxParaGroup.EnterDrxSwitch parameter of each bearer is set to ON.
l One of the following conditions related to the CellDrxPara.FddEnterDrxThd parameter
is met:
– The CellDrxPara.FddEnterDrxThd parameter is set to a value ranging from 0 to
999, and the measured traffic volume is less than or equal to the value of the
CellDrxPara.FddEnterDrxThd parameter in the period specified by the
CellDrxPara.DataAmountStatTimer parameter.
– The CellDrxPara.FddEnterDrxThd parameter is set to 1000. Under this setting,
the eNodeB does not evaluate DRX entry based on the measured traffic volume;
instead, the eNodeB directly instructs the UE to enter DRX mode.
l The UE is neither in the state where it constantly performs gap-assisted measurement nor
in the transmission time interval (TTI) bundling state.

eRAN
3.1.3.2 Exit Conditions

The UE exits DRX mode in any of the following situations:
l The UE exits DRX mode when any of the following conditions is met.
– The QCI of a new service does not support DRX mode. That is, the
DrxParaGroup.EnterDrxSwitch for this QCI is set to OFF.
– The traffic volume of the UE is high. That is, the traffic volume is higher than the
threshold specified by the CellDrxPara.FddExitDrxThd parameter in the period
specified by the CellDrxPara.DataAmountStatTimer parameter.
NOTE
When the CellDrxPara.FddExitDrxThd parameter is set to 1000, the UE does not exit
DRX mode.
l The CellDrxPara.DrxAlgSwitch parameter is set to OFF, and the eNodeB instructs the
UE to exit DRX mode in the RRC connection reconfiguration procedure.
l The UE in connected mode experiences a radio link failure (RLF) when radio conditions
deteriorate.
l The eNodeB instructs the UE to exit DRX mode during a handover.
l The UE is in the TTI bundling state.
l When the UE starts gap-assisted measurement, the eNodeB instructs the UE to exit DRX
mode if one of the following conditions is met:
– CellDrxPara.GapDrxExclusiveSwitch is turned on.
– CellDrxPara.VolteGapDrxExclusiveSwitch is turned on and the UE has a QCI 1
bearer.
If both CellDrxPara.VolteGapDrxExclusiveSwitch and
CellDrxPara.GapDrxExclusiveSwitch are turned on, only
CellDrxPara.GapDrxExclusiveSwitch is considered.
3.1.4 Working Mechanism

In DRX mode, the UE does not constantly monitor the PDCCH. In the active state, the UE
turns on its receiver to monitor the PDCCH. In the sleep state, the UE no longer monitors the
PDCCH and can turn off its receiver to reduce power consumption.
3.1.4.1 Related Concepts
On Duration
In DRX mode, the UE does not constantly keep its receiver off. It periodically turns on its
receiver and monitors the PDCCH for incoming signaling for a consecutive period. This
consecutive period is called On Duration and defined by the
DrxParaGroup.OnDurationTimer parameter.
DRX Cycle
A DRX cycle is the interval between two occurrences of On Duration. A DRX cycle consists
of an On Duration and a possible period of sleep time, as shown in Figure 3-2.

eRAN
Figure 3-2 DRX cycle
NOTE
The period following an On Duration may be active or sleep time. For details, see 3.1.4.3.1 Operation
in Active Time.
A DRX cycle consists of active time and sleep time. It may be a long or short cycle.
Active Time
In active time, the UE turns on its receiver and monitors the PDCCH. Active time is equal to
On Duration plus other possible periods during which the UE needs to turn on its receiver, for
example, a period during which other DRX timers are working or a high-priority service is
being processed. Other DRX timers include the DRX Inactivity Timer, Contention Resolution
Timer, and DRX Retransmission Timer. For details, see 3.1.4.3.1 Operation in Active Time.
For a given DRX cycle:
l A longer active time results in a shorter service delay but increased UE power
consumption.
l A shorter active time results in reduced UE power consumption but a longer service
delay.
Sleep Time
In sleep time, the UE can turn off its receiver.
Long Cycle
A long cycle (also called long DRX cycle) saves more power. You can use the mandatory
parameter DrxParaGroup.LongDrxCycle to configure a long cycle.
NOTE
If a short cycle is not configured before DRX is enabled, the UE will use a long cycle after entering
DRX mode. If a short cycle has been configured before DRX is enabled, the UE will preferentially use
the short cycle and switch to a long cycle after the timer defined by
DrxParaGroup.DrxShortCycleTimer expires.
Short Cycle
The application of a short cycle (also called short DRX cycle) is jointly controlled by
CellDrxPara.ShortDrxCycleSwitch and the QCI-level DRX switch
DrxParaGroup.SupportShortDrx.
A short cycle results in better service experience than a long cycle but saves less power. You
can use the following optional parameters to configure a short cycle:

eRAN
l CellDrxPara.ShortDrxCycleSwitch: specifies whether to use a short cycle.

l DrxParaGroup.SupportShortDrx: specifies whether services of a specific QCI support
a short cycle.
l DrxParaGroup.ShortDRXCycle: specifies the length of a short cycle.
If a short cycle is configured for the UE, the UE will determine when to use the long or short
cycle as described in 3.1.4.4 Switching Between Long and Short Cycles.
3.1.4.2 Startup of a DRX Cycle

After the UE enters DRX mode, the On Duration Timer may not start immediately. The timer
starts up and the UE starts a long or short DRX cycle only when the following conditions are
met:
l For a long DRX cycle:
[(SFN x 10) + SSFN] modulo DrxParaGroup.LongDrxCycle = DRX start offset
The long DRX cycle starts at the time specified by the system frame number (SFN) and
system subframe number (SSFN).
l For a short DRX cycle:
[(SFN x 10) + SSFN] modulo DrxParaGroup.ShortDrxCycle = DRX start offset
modulo DrxParaGroup.ShortDrxCycle
The short DRX cycle starts at the time specified by the SFN and SSFN.
NOTE
l These formulas are defined in section 5.7 "Discontinuous Reception (DRX)" of 3GPP TS 36.321
V10.5.0.
In these formulas, DRX start offset is the start offset of the long DRX cycle, and DRX start
offset modulo DrxParaGroup.ShortDrxCycle is the start offset of the short DRX cycle. The
eNodeB notifies the UE of the long DRX cycle, short DRX cycle, and DRX start offset in the
RRC Connection Reconfiguration message.
If the DrxParaGroup.ShortDrxCycle parameter is set, the value of the
DrxParaGroup.LongDrxCycle parameter must be a multiple of the value of the
DrxParaGroup.ShortDrxCycle parameter.
Figure 3-3 shows how the UE enters DRX mode. The eNodeB assigns the same long DRX
cycle of 10 transmission time intervals (TTIs) to both UE 1 and UE 2 in radio frame 0 (whose
SFN is 0) in a cell and instructs them to enter DRX mode respectively at TTI 1 and TTI 0. UE
1 and UE 2 enter the DRX cycle respectively at TTI 3 and TTI 4, based on the configured
DRX start offset. Therefore, for UE 1, (SFN, SSFN) = (0, 3); for UE 2, (SFN, SSFN) = (0, 4).

eRAN
Figure 3-3 Entering DRX mode and starting the DRX cycle
3.1.4.3 Operation in a DRX Cycle

A DRX cycle consists of active time and sleep time. This section describes the operation in
active time and the switching between active time and sleep time.
3.1.4.3.1 Operation in Active Time

The UE turns on its receiver in active time. According to section 5.7 in 3GPP TS 36.321
V10.5.0, the UE is in active time if any of the following conditions is met:
l The On Duration Timer, DRX Inactivity Timer, DRX Retransmission Timer, or

Contention Resolution Timer is running. For details about the timers, see Table 3-2.
l A scheduling request (SR) sent by the UE on the physical uplink control channel
(PUCCH) is pending.
l An uplink (UL) grant for a pending hybrid automatic repeat request (HARQ)
retransmission occurs.
l The UE has not received a PDCCH indicating an initial data transmission after
successfully receiving a Random Access Response in a non-contention-based random
access procedure.
Table 3-2 describes the related DRX timers.
Table 3-2 DRX timers

DRX Timer Parameter Definition Description
ID
On Duration DrxParaGro Function This timer specifies the time during

Timer up.OnDurati which the UE monitors the PDCCH.
onTimer
Start This timer starts at the first subframe
of a DRX cycle. For details, see
3.1.4.2 Startup of a DRX Cycle.
Timing Timing is based on the number of

consecutive PDCCH subframes.

eRAN

ID
Stop l This timer stops after the UE

receives a DRX command MAC
control element (MCE).
l This timer stops after it expires.
Expiry After this timer expires, the UE enters

the sleep state, no longer monitoring
the PDCCH.
DRX Inactivity DrxParaGro Function This timer specifies the time during
Timer up.DRXInact which the UE determines whether to
ivityTimer extend its active time because of the
arrival of new data. This timer
provides a reference for the UE to use
a short cycle.
Start This timer starts or restarts when the

UE successfully decodes a PDCCH
indicating an initial uplink grant or
downlink user data for this UE.

Stop l This timer stops after the UE

receives a DRX command MCE.
l This timer stops after it expires.
Expiry After this timer expires, the UE uses a

short cycle if the cycle is configured,
and the DRX Short Cycle Timer starts
or restarts. Alternatively, the UE uses
a long cycle if no short cycle is
configured.
DRX Short DrxParaGro Function This timer specifies the lifetime of a

Cycle Timer up.DRXShor short cycle, that is, the number of
tCycleTimer consecutive repetition times of a short
cycle.
Start l After the DRX Inactivity Timer

expires, this timer starts or restarts
if a short cycle is configured.
l After the UE receives the DRX
command MCE, this timer starts
or restarts if a short cycle is
configured.
l The UE uses a short cycle after the
DRX Short Cycle Timer starts.

eRAN

ID
Timing Timing is based on the repetition

times of the short cycle.
Stop This timer stops after it expires.
Expiry After this timer expires, the UE uses

the long cycle.
DRX DrxParaGro Function This timer specifies the length of time

Retransmission up.DRXReT the UE will wait for HARQ
Timer xTimer retransmission in active time. If the
UE has not received the retransmitted
data before this timer expires, the UE
will no longer accept it.
Start The DRX Retransmission Timer starts

or restarts when the HARQ RTT
Timer expires but the UE does not
receive the retransmitted DL data.

Stop This timer stops if the UE receives the

retransmitted data before the timer
expires.
Expiry After this timer expires, the UE takes

no further action.
HARQ RTT - Function This timer specifies the interval

Timer between the initial DL data
transmission and the first DL HARQ
retransmission. This timer is used to
determine when to start the DRX
Retransmission Timer.
Start This timer starts and the DRX

Retransmission Timer stops during
either of the following situations:
l At the beginning of the subframe
when semi-persistent DL data
transmission may take place.
l The UE decodes a PDCCH and
knows that a HARQ process will
have a DL transmission in a new
subframe.

subframes.
Stop This timer stops after it expires.

eRAN

ID
Expiry After this timer expires, if the UE

detects that DL data has been received
correctly, the UE takes no further
action; otherwise, the DRX
Retransmission Timer starts.
Contention - Function This timer specifies the time during

Resolution which the UE waits for a Contention
Timer Resolution message in a contention-
based random access procedure.
Start This timer starts when the UE initially

transmits or retransmits an Msg3 in a
contention-based random access
procedure.

Stop This timer stops after the UE receives

a Contention Resolution message.
Expiry After this timer expires, the UE

retransmits a preamble.
In the On Duration, the DRX Inactivity Timer starts when the UE decodes a PDCCH and
knows that an initial data transmission is about to start. The UE continues to monitor the
PDCCH for new transmissions until the DRX Inactivity Time expires. The timer restarts if a
new transmission occurs. The DRX Inactivity Timer can repeatedly restart for continuous data
transmissions to prolong the active time.
When the DRX Inactivity Timer expires and a short cycle has been configured, the UE enters
a short cycle. For details, see Switching from a Long DRX Cycle to a Short DRX Cycle.
3.1.4.3.2 Switching Between Active Time and Sleep Time

Switching between active time and sleep time depends on DRX timers and service processes.
Figure 3-4 illustrates the switching between active time and sleep time in various frequency
division duplex (FDD) mode scenarios.

eRAN
Figure 3-4 Switching between active time and sleep time
Table 3-3 describes the conditions for starting active time. For example, OD is the condition
for starting the On Duration Timer.
Table 3-3 Conditions for starting active time
Condition Meaning
OD A DRX cycle starts.
IA A PDCCH message indicating an initial DL data transmission is

received.
R The HARQ RTT Timer expires.
SR A UL scheduling request is sent.
UR A UL negative acknowledgment (NACK) is received, and

retransmission is required.
RAR A non-contention-based random access response is received.
CR Msg3 is sent in a random access procedure.

eRAN
The active time shown in the UE DRX status plot in Figure 3-4 combines the active time
described in each of the other plots excluding the plot of HARQ RTT Timer.
In the plot of HARQ RTT Timer, "DL HARQ raises" refers to one of the two DL HARQ
transmission scenarios:
l A semi-persistent DL data transmission is scheduled to start at the subframe.
l A DL data transmission is scheduled to start at the subframe, which the UE learns by
monitoring the PDCCH.
3.1.4.4 Switching Between Long and Short Cycles

The UE applies only a long or short DRX cycle at a time even when the eNodeB assigns both
long and short DRX cycles to the UE. The UE switches between long and short DRX cycles
when the eNodeB assigns both long and short DRX cycles to the UE.
Switching from a Long DRX Cycle to a Short DRX Cycle

If the eNodeB delivers short DRX cycle parameters to the UE, the UE will exit the long DRX
cycle and enter a short DRX cycle if either of the following occurs:
l The DRX Inactivity Timer expires.
If there is data to transmit, the eNodeB starts the DRX Inactivity Timer. When the DRX
Inactivity Timer expires, the short DRX cycle starts.
l The UE receives the DRX command MCE.
After the UE receives the DRX command MCE, the UE enters a short DRX cycle.
Otherwise, the UE still uses the long DRX cycle.
Switching from a Short DRX Cycle to a Long DRX Cycle

If the UE does not receive new data during a specified period after entering a short DRX
cycle, it will switch to a long DRX cycle to save power.
The period before the UE switches to a long DRX cycle is called the lifetime of the short
DRX cycle. The lifetime is measured by the number of times the short DRX cycle repeats.
The DRX Short Cycle Timer determines how long the short DRX cycle runs. The
DrxParaGroup.DrxShortCycleTimer parameter sets the time for the DRX Short Cycle
Timer. After the DRX Short Cycle Timer expires, the UE uses the long DRX cycle.
3.1.4.5 DRX for GERAN Measurement

DRX parameters for GERAN measurement need to be configured in the following scenarios:
l CellDrxPara.CovGsmMeasDrxCfgSwitch is turned on and the eNodeB triggers
GERAN measurement after receiving a coverage-based inter-RAT event A2 report from
the UE.
l CellDrxPara.DrxForMeasSwitch is turned on and ultra-flash CSFB triggers GERAN
measurement.
DRX for GERAN measurement has a lower priority than DRX for ANR measurement but has
a higher priority than other types of DRX. When triggering DRX for GERAN measurement:

eRAN
l The eNodeB uses the DRX parameters for ANR measurement instead of those specific
to GERAN measurement if one of the following conditions is met:
– The DRX parameters for ANR measurement have been configured
– The DRX parameters specific to GERAN measurement have been configured but
DRX for ANR measurement is triggered.
l The eNodeB uses the DRX parameters specific to GERAN measurement even if the
parameters for other types of DRX (except DRX for ANR measurement) have been
configured.
If the DRX parameters specific to GERAN measurement have been configured and
CellDrxPara.MeasDrxSpecSchSwitch is set to ON(On), the eNodeB performs special
uplink and downlink scheduling to make the UE stay in the sleep time for a long period,
prolonging the time for GERAN measurement and shortening the delay in measurement
reporting.
3.1.5 DRX Parameters for Various Scenarios

UEs enter the active or sleep state based on DRX configurations.
For common services on common UEs, you can configure one set of DRX parameters. For
details, see 3.1.5.1 DRX Parameters for VoLTE.
For special UEs or ANR measurements, you can configure special DRX parameters. For
details, see 3.1.5.2 DRX Parameters for Special UEs and 3.1.5.3 DRX Parameters for
ANR Measurement.
Table 3-4 lists the parameters for each scenario.
Table 3-4 DRX parameters for various scenarios

Configurati DRX Parameters for DRX DRX Parameters for ANR
on Item Common UEs Parameters Measurement
for Special
VoIP Non-VoIP UEs Intra-RAT Inter-RAT
Service Services
s
Long cycle DrxParaGroup.Lon CellDrxSp CellDrxSpecia CellDrxSpecialPar

length gDrxCycle ecialPara. lPara.LongDr a.LongDrxCycleFo
LongDrxC xCycleForIntr rInterRatAnr
ycleSpecial aRatAnr
Short cycle DrxParaGroup.Sup CellDrxSp Short cycles are not used in ANR
switch portShortDrx ecialPara. measurement.
ShortDrxC
ycleSwitch
Special

eRAN
Short cycle Short DrxParaG CellDrxSp Short cycles are not used in ANR
length cycles roup.Shor ecialPara. measurement.
are not tDrxCycle ShortDrxC
used for ycleSpecial
VoIP
UEs by
default.
Short cycle Short DrxParaG CellDrxSp Short cycles are not used in ANR
timer cycles roup.DRX ecialPara. measurement.
length are not ShortCycl DrxShortC
used for eTimer ycleTimerS
VoIP pecial
UEs by
default.
On DrxParaGroup.OnD CellDrxSp For For

Duration urationTimer ecialPara. CellDrxSpecialPara. CellDrxSpe
timer OnDuratio LongDrxCycleForIn- cialPara.Lo
length nTimerSpe traRatAnr ≥ SF256, ngDrxCycle
cial the On Duration timer ForInterRat
length is set to Anr ≥
PSF200 by the SF256, the
system. On Duration
For timer length
CellDrxSpecialPara. is set to
LongDrxCycleForIn- PSF200 by
traRatAnr < SF256, the system.
the On Duration timer For
length is set to CellDrxSpe
PSF100 by the cialPara.Lo
system. ngDrxCycle
ForInterRat
Anr <
SF256, the
On Duration
timer length
is set to
PSF100 by
the system.
DRX DrxParaGroup.DrxI CellDrxSp CellDrxSpecialPara.FddAnrDrxIna

inactivity nactivityTimer ecialPara. ctivityTimer
timer DRXInacti
length vityTimerS
pecial
DRX DrxParaGroup.DRX DrxParaG The DRX retransmission timer length

retransmiss ReTxTimer roup.DRX is set to 8 ms by the system.
ion timer ReTxTimer
length

eRAN
NOTE
The CellDrxSpecialPara MO can take effect only when the

CellDrxSpecialPara.CellDrxSpecialParaValid parameter is set to TRUE.
3.1.5.1 DRX Parameters for VoLTE

For VoLTE, a set of special DRX parameter settings is available to reduce UE power
consumption while maintaining VoLTE capacity.
As VoLTE bearers have a QCI of 1, the DRX parameters for QCI 1 can be used for VoLTE.
As bearers with QCI 5 are set up for IMS signaling transmission during VoLTE services, the
DRX parameters for QCI 5 also need to be set. If the VoLTE UE has multiple bearers with
different QCIs (for example, QCI 1, QCI 5, and QCI 9), the eNodeB determines the DRX
parameters based on the CELLDRXPARA.DrxPolicyMode parameter setting.
Long Cycle for VoLTE

A long cycle is specified by the DrxParaGroup.LongDrxCycle parameter.
The VoLTE scheduling period is 20 ms. When semi-persistent scheduling is disabled, it is

recommended that the DrxParaGroup.LongDrxCycle parameter for QCI 1 be set to SF40(40
subframes). When semi-persistent scheduling is enabled, it is recommended that the
DrxParaGroup.LongDrxCycle parameter for QCI 1 be set to SF20(20 subframes).
l If the parameter value is too small, the UE will probably stay in the active state and
consume more power.
l If the parameter value is too large, the VoLTE scheduling may be performed during sleep
time. This delays packet transmission and affects user experience.
Short Cycle for VoLTE

VoLTE requires a suitable DRX cycle, for example, 20 ms or 40 ms. If a shorter cycle is used,
less power will be saved and no obvious decrease will be seen in service delay. Therefore, a
short cycle is not recommended for VoLTE.
On Duration Timer for VoLTE

Based on the number of UEs with VoLTE services, set an appropriate value for the On
Duration Timer, which is specified by the DrxParaGroup.onDurationTimer parameter. If
there are a large number of UEs with VoLTE services, set a large value for this parameter to
ensure the scheduling of VoLTE services.
It is recommended that the DrxParaGroup.onDurationTimer parameter for QCI 1 be set to

PSF10(10 PDCCH subframes).
DRX Inactivity Timer for VoLTE

To save more UE power, it is recommended that the DrxParaGroup.DrxInactivityTimer
parameter for QCI 1 be set to PSF5(5 PDCCH subframes). To ensure voice quality, it is
recommended that this parameter be set to a larger value based on the uplink coverage of the
live network.

eRAN
DRX Retransmission Timer for VoLTE

It is recommended that the DrxParaGroup.DrxReTxTimer parameter for QCI 1 be set to
SF8(8 subframes).
Recommended DRX Parameter Settings for VoLTE

Table 3-5 lists the recommended DRX parameter settings for VoLTE when semi-persistent
scheduling is enabled.
Table 3-5 Recommended DRX parameter settings for VoLTE when semi-persistent
scheduling is enabled
Parameter ID Recommended Value
DrxParaGroup.LongDrxCycle SF20
DrxParaGroup.onDurationTimer PSF10
DrxParaGroup.DrxInactivityTimer PSF5
DrxParaGroup.DrxReTxTimer SF8
DrxParaGroup.SupportShortDrx UU_DISABLE
Table 3-6 lists the recommended DRX parameter settings for VoLTE when semi-persistent
scheduling is disabled.
Table 3-6 Recommended DRX parameter settings for VoLTE when semi-persistent
scheduling is disabled
Parameter ID Recommended Value
DrxParaGroup.LongDrxCycle SF40
DrxParaGroup.onDurationTimer PSF10
DrxParaGroup.DrxInactivityTimer PSF5
DrxParaGroup.DrxReTxTimer SF8
DrxParaGroup.SupportShortDrx UU_DISABLE
NOTE
When the uplink coverage is poor, the DrxParaGroup.DrxInactivityTimer parameter can be set to a
larger value to avoid packet loss caused by the service delay of UEs.
Special Processing for VoLTE

Set the CellDrxPara.DrxStateDuringUlHarqRetx parameter to
DRX_ACTIVE_FOR_VOICE. Under this parameter setting, if the eNodeB has correctly
received the data initially transmitted by a VoLTE UE in DRX mode over the PUSCH, the

eRAN
eNodeB can perform dynamic scheduling for another initial transmission on the next
retransmission occasion of the uplink HARQ process. This mechanism provides more
scheduling chances for VoLTE UEs, shortens scheduling delays induced by DRX, and
improves voice quality. However, more scheduling chances for VoLTE UEs will lead to an
increase in resource overhead and a decrease in data throughput.
When the SpsSchSwitch option of the CellAlgoSwitch.DlSchSwitch parameter is selected,

the DlSpsDrxDecouplingSwitch option of the CellDlschAlgo.DlEnhancedVoipSchSw
parameter determines whether to consider the long cycle setting during the configuration and
activation of downlink semi-persistent scheduling:
l If the DlSpsDrxDecouplingSwitch option is deselected, downlink semi-persistent

scheduling can be performed only when the scheduling period configured for VoLTE is a
multiple of the long cycle. Under these parameter settings, downlink semi-persistent
scheduling always arranges the initial transmission over the PDSCH within the period
indicated by the On Duration Timer in the long cycle, that is, within the period when the
UE stays in the active state.
l If the DlSpsDrxDecouplingSwitch option is selected, downlink semi-persistent
scheduling is not subject to the preceding restrictions. It may arrange the initial
transmission over the PDSCH within the period when the UE stays in the active state or
sleep state.
3.1.5.2 DRX Parameters for Special UEs

Not all UEs are sensitive to power consumption. For example, data cards or UEs with a
sufficient power supply focus on service delay rather than power consumption. These UEs are
called special UEs. The subscriber profile ID for RAT/frequency priority (RFSP) function
allows operators to designate a UE as a special UE and use special DRX parameters for this
UE to shorten service delay.
On the Evolved Packet Core (EPC) side, the UE RFSP is an integer ranging from 1 to 256.
Operators can define the RFSP and bind it to the mobile station international ISDN number
(MSISDN) of the UE. When the UE accesses the EPC, the RFSP of the UE is included in the
INITIAL CONTEXT SETUP REQUEST message and sent to the eNodeB over the S1
interface.
On the eNodeB side, operators can set the SpidCfg.Spid parameter to an integer ranging from
1 to 256 on the U2000 or Web LMT. When the RFSP value of the UE is the same as the
SpidCfg.Spid parameter value and the SpidCfg.DrxStatus parameter is set to FALSE, the
eNodeB considers the UE to be a special UE. Otherwise, the eNodeB considers the UE to be a
common UE.
On the UE side, the UE reports its type to the eNodeB using the UE-EUTRA-Capability IE in
a UECapabilityInformation message. If the UE-EUTRA-Capability IE contains
noBenFromBatConsumpOpt, the UE is a special UE. Otherwise, the UE is a common UE.
The UE type (common or special) is reported on both the eNodeB and UE sides. The eNodeB
compares the results reported on the two sides. When the results are inconsistent, the eNodeB
considers the UE to be a special UE. When the results are consistent, the eNodeB identifies
the UE type based on the results and uses the appropriate DRX feature.
The working mode of special UEs is the same as that of common UEs except that DRX
parameters configured for special UEs are different from those configured for common UEs.

eRAN
3.1.5.3 DRX Parameters for ANR Measurement

ANR measurement requires a relatively long sleep time. If the DRX cycle is too short, ANR
measurement cannot be completed during this period. If the DRX cycle is too long, the
scheduling delay will be so long that it fails to meet quality of service (QoS) requirements.
When the eNodeB receives a special-DRX start indication during ANR measurement, the
eNodeB sets the CellDrxSpecialPara.LongDrxCycleForIntraRatAnr or
CellDrxSpecialPara.LongDrxCycleForInterRatAnr parameter to a large value for ANR
measurement in sleep time.
The eNodeB configures a long cycle for ANR measurement in sleep time regardless of
whether CellDrxPara.DrxAlgSwitch is on.
l If the cells to be measured are E-UTRAN cells, the eNodeB will use the value of the
CellDrxSpecialPara.LongDrxCycleForIntraRatAnr parameter as the long cycle length.
l If the cells to be measured are GERAN or UTRAN cells, the eNodeB will use the value
of the CellDrxSpecialPara.LongDrxCycleForInterRatAnr parameter as the long cycle
length.
3.1.5.4 SRI Offset Reconfiguration for DRX

Generally, if a UE sends an SRI to the eNodeB during sleep time, the UE will switch from the
sleep state to the active state and the UE power saving effect will deteriorate. To save more
UE power, SRI offset reconfiguration for DRX is introduced to reduce the number of SR-
pending TTIs falling in sleep time.
The SriOffsetReConfigForDrxSW option of the CellPucchAlgo.SriAlgoSwitch parameter
specifies whether to enable SRI offset reconfiguration for DRX.
l When the SriOffsetReConfigForDrxSW option is selected, the SRI offset is
reconfigured for DRX to save more power.
l When the SriOffsetReConfigForDrxSW option is deselected, the SRI offset is not
reconfigured for DRX. If the UE sends an SRI in sleep time, the sleep time will be
shortened and less power can be saved.
During SRI offset reconfiguration for DRX, the channel quality indicator (CQI) and sounding
reference signal (SRS) parameters configured for the UE's PCell cannot be reconfigured.
Otherwise, the calculated SRI offset is meaningless because the DRX start offset has been
changed with the CQI and SRS parameters.
3.2 LOFD-00110501 Dynamic DRX

This section describes the implementation principles of dynamic DRX. For engineering
guidelines, see 6.2 Engineering Guidelines for LOFD-00110501 Dynamic DRX.
3.2.1 Introduction
Definition
Dynamic DRX allows the eNodeB to determine whether to reduce UE power consumption or
signaling overhead based on manual configurations when the amount of UE power

eRAN
consumption increases rapidly or signaling overhead is high because of UE access to the

network.
3.2.1.2 Benefits
Dynamic DRX provides the following benefits but cannot provide all these benefits
simultaneously:
l Reduces UE power consumption. When UE power consumption is high, the eNodeB
sends different DRX parameters to UEs in the synchronization state and UEs in the out-
of-synchronization states, instructing them to dynamically switch between two sets of
DRX parameters.
l Reduces signaling overhead by reducing the amount of RRC connection establishment
and release signaling for services that use small, sparse packets or heartbeat packets.
The UE inactivity timer is increased to allow UEs to stay in connected mode longer in
the case of high signaling overhead caused by UEs' access to the network.
3.2.1.3 Dynamic DRX Process

Figure 3-5 shows the dynamic DRX process.

eRAN
Figure 3-5 Dynamic DRX process
1. Dynamic DRX entry phase

After the UE accesses the network, the eNodeB determines whether the UE meets the
conditions for entering dynamic DRX mode. When the conditions are met, the eNodeB
sends the UE an RRC Connection Reconfiguration message with the DRX-
Configuration IE set to setup. The UE then enters dynamic DRX mode based on
parameters in this IE. For details, see 3.2.2.1 Entry Conditions.
2. Dynamic DRX execution phase
After the UE enters dynamic DRX mode, the eNodeB instructs the UE to enter power
saving or reduced signaling mode based on the UE inactivity timer setting.
– When the GLOBALPROCSWITCH.QciParaEffectFlag parameter is set to OFF,
the QCI parameter settings do not take effect.
When the UE does not have a bearer with a QoS class identifier (QCI) of 1, the
bearers with other QCIs use the UE inactivity timer defined by the
RrcConnStateTimer.UeInactivityTimerDynDrx parameter. When the UE has a
QCI 1 bearer, all the bearers of this UE use the UE inactivity timer defined by the
RrcConnStateTimer.UeInactTimerDynDrxQci1 parameter.
– When the GLOBALPROCSWITCH.QciParaEffectFlag parameter is set to ON,
the QCI parameter settings take effect.

eRAN
When the UE does not have a QCI 69 bearer or the UE has such a bearer but the
bearer is not used to carry MCPTT, the maximum
QCIPARA.UeInactivityTimerDynDrxQci parameter value of the bearers with the
highest priority (defined by QCIPARA.UeInactiveTimerPri) is used as the UE
inactivity timer value. When the UE has a QCI 69 bearer and this bearer is used to
carry MCPTT, all the bearers of this UE use the UE inactivity timer defined by the
QCIPARA.UeInactivityTimerDynDrxQci parameter of QCI 69. For details, see
3.2.3 Principles.
NOTE
l When dynamic DRX is enabled and the value of the UE inactivity timer is less than the value
of the connection release timer on the core network side, no voice service can be set up for the
UE if the following conditions are met: (1) The UE inactivity timer of a called UE has expired
before the UE answers a call. (2) The UE switches to idle mode. (3) The UE reselects another
VoLTE-incapable cell with a higher priority.
To avoid the connection from being released on the core network side before the UE answers
the call, the UE inactivity timer can be set to a larger value.
l For details about the QCIPARA.UeInactiveTimerPri parameter, see QoS Management
Feature Parameter Description.
3. Dynamic DRX exit phase
The eNodeB checks whether the UE meets the conditions for exiting dynamic DRX
mode. When the conditions are met, the eNodeB sends the UE an RRC Connection
Reconfiguration message with the DRX-Configuration IE set to release. After the UE
receives the message, it immediately clears all the DRX parameters stored locally and
exits dynamic DRX mode. For details, see 3.2.2.2 Exit Conditions.
3.2.2 Entry and Exit Conditions

When certain network and UE conditions are met, the eNodeB instructs UEs to enter or exit
dynamic DRX mode. This section describes the entry and exit conditions.
NOTE
The configuration principles of DRX parameters for the synchronization state in LOFD-00110501
Dynamic DRX are the same as the configuration principles of DRX parameters in LBFD-002017 DRX.
However, the two features are independent of each other.
3.2.2.1 Entry Conditions

Dynamic DRX mode is enabled when the CellAlgoSwitch.DynDrxSwitch parameter is set to
DynDrxSwitch-1.
Before dynamic DRX is enabled, the following parameters need to be set:
l For UEs in the synchronization state: DrxParaGroup.LongDrxCycle,
DrxParaGroup.OnDurationTimer and DrxParaGroup.DrxInactivityTimer
l For UEs in the out-of-synchronization state: CellDrxPara.LongDrxCycleUnsync,
CellDrxPara.OndurationTimerUnsync and CellDrxPara.DrxInactivityTimerUnsync
UE power saving preference or network-wide signaling reduction preference in dynamic DRX
mode is determined by the following parameters:
l RrcConnStateTimer.UeInactivityTimerDynDrx
l RrcConnStateTimer.UeInactTimerDynDrxQci1
l QciPara.UeInactivityTimerDynDrxQci

eRAN
3.2.2.2 Exit Conditions

The UE exits dynamic DRX mode when any of the following conditions is met:
l The CellAlgoSwitch.DynDrxSwitch parameter is set to DynDrxSwitch-0, and the
eNodeB instructs the UE to exit dynamic DRX mode in the RRC connection
reconfiguration procedure.
l Other conditions are the same as those for LBFD-002017 DRX. For details, see 3.1.3.2
Exit Conditions.
3.2.3 Principles
To allow smart terminals to stay in sleep state longer and consume less power, the eNodeB
selects different DRX parameters for UEs in synchronization and out-of-synchronization
states based on the following parameters:
l RrcConnStateTimer.UeInactivityTimerDynDrx,
RrcConnStateTimer.UeInactTimerDynDrxQci1 or
QciPara.UeInactivityTimerDynDrxQci
l RrcConnStateTimer.UlSynTimerDynDrx
Figure 3-6 shows how a UE switches between different states.
Figure 3-6 UE state switching
The eNodeB delivers dynamic DRX parameters based on UE states:

eRAN
Figure 3-7 Protection mechanism
Dynamic DRX is controlled by the CellAlgoSwitch.DynDrxSwitch parameter. The principles

of dynamic DRX are as follows:
1. If the value of RrcConnStateTimer.UeInactivityTimerDynDrx,
RrcConnStateTimer.UeInactTimerDynDrxQci1, or
QciPara.UeInactivityTimerDynDrxQci is greater than the value of
RrcConnStateTimer.UlSynTimerDynDrx, the eNodeB may not maintain the
synchronization state for the UE and may configure DRX parameters for the out-of-
synchronization state.
– Setting the RrcConnStateTimer.UeInactivityTimerDynDrx,
QciPara.UeInactivityTimerDynDrxQci parameter to a larger value increases the
time the UE is in connected mode, reduces the number of transitions between
connected and idle modes, reduces the signaling overhead in frequent connection
establishments and releases for small, sparse packets or heartbeat packets, but saves
less UE power.
– Setting the RrcConnStateTimer.UlSynTimerDynDrx parameter to a smaller value
decreases the time the eNodeB synchronizes with the UE and saves more UE
power.

eRAN
NOTE
If the DynDrxSwitch(DynDrxSwitch) option of the CellAlgoSwitch.DynDrxSwitch

parameter is selected, the settings of the RrcConnStateTimer.UeInactiveTimer or
QciPara.UeInactiveTimerForQci and RrcConnStateTimer.UlSynTimer parameters take
effect only for UEs not supporting DRX.
2. When UEs are in the synchronization state, the eNodeB assigns the UEs the DRX
parameters DrxParaGroup.LongDrxCycle, DrxParaGroup.OnDurationTimer, and
DrxParaGroup.DrxInactivityTimer. When the timer defined by
RrcConnStateTimer.UlSynTimerDynDrx expires, the eNodeB assigns the UEs a longer
DRX cycle by setting the CellDrxPara.LongDrxCycleUnsync,
CellDrxPara.OndurationTimerUnsync, and CellDrxPara.DrxInactivityTimerUnsync
parameters. The eNodeB dynamically switches between DRX parameters for the
synchronization state and DRX parameters for the out-of-synchronization state based on
UE states.
3.3 LOFD-00110502 High-Mobility-Triggered Idle Mode

This section describes the implementation principles of the high-mobility-triggered idle mode
feature. For engineering guidelines, see 6.3 Engineering Guidelines for LOFD-00110502
High-Mobility-Triggered Idle Mode.
3.3.1 Introduction

If UEs frequently move between cells while staying in connected mode for a long period of
time, a large number of handovers will be triggered, causing excessive handover signaling.
Especially after dynamic DRX is enabled, UEs stay in connected mode for a prolonged period
of time. In this scenario, if UEs move fast, instead of cell reselections, more handovers are
triggered. To prevent handover signaling from affecting eNodeB performance, the eNodeB
uses the high-mobility-triggered idle mode feature.
Definition
High-mobility-triggered idle mode is a state in which the number of handovers and the
amount of related signaling decrease after UEs enter idle mode based on their movement
speeds and the packet sending state.
3.3.1.2 Benefits
The high-mobility-triggered idle mode feature reduces the number of handovers and the
amount of signaling on the entire network, minimizing the impact of handover signaling on
network stability while maintaining user experience.

eRAN
3.3.2 Principles
In high-mobility-triggered idle mode, eNodeBs determine whether to release UEs based on
their movement speeds, packet sending states, and camping duration. For triggering
conditions, see Working Mechanism.
Characteristics of Fast-Moving UEs

LTE networks are often deployed in hot spots that have the following characteristics:
l Densely populated areas where people are often on the move

l Small spacing between eNodeBs
In these hot spots, handovers are easily triggered for fast-moving UEs.
Figure 3-8 shows that a UE moves between cells in a hot spot.
Figure 3-8 UE movement
Table 3-7 and Table 3-8 list the movement speeds and camping duration for a UE passing
through the center coverage areas of cells with radii of 300 m and 500 m.
Table 3-7 Movement speed and camping time of a UE in a cell with a radius of 300 m
Movement Speed (km/h) Camping Time (Seconds)
[30-60] [18-36]
[60-120] [18-9]
> 120 <9
Table 3-8 Movement speed and camping time of a UE in a cell with a radius of 500 m
[30-60] [30-60]

eRAN
[60-120] [15-30]
> 120 < 15
In reality, most UEs do not pass through the cell center and the camping time of these UEs is
even shorter.
Figure 3-9 shows the numbers of access requests triggered by heartbeats.
Figure 3-9 Numbers of access requests triggered by heartbeats
In Figure 3-9, the x-axis specifies the service types and the y-axis specifies the number of
network access requests triggered by heartbeats within an hour. The heartbeat period is equal
to 3600 divided by the number of service requests.
You can extrapolate the following from the data shown in Figure 3-9:
l The heartbeat periods for most services are 180s or longer.

l In each heartbeat period, the UE stays in connected mode for a long time.
During a heartbeat period, if the UE is moving fast, it may pass through several cells and
be handed over many times. For example, during a heartbeat period of 180s, a UE
moving at 30 km/h may pass through at least five 300 m radius cells. If the UE stays in
connected mode in this period, at least five handovers will be performed. During this
process, no service data is transmitted.
l Most UEs have only heartbeat packets to transmit and receive for an extended period, a
period even longer than the time the UEs take to process other services.
Working Mechanism
The high-mobility-triggered idle mode feature is controlled by the
CellAlgoSwitch.HighMobiTrigIdleModeSwitch parameter.
To avoid a handover, the eNodeB triggers the S1 release procedure after receiving the
measurement report from a UE and instructs the UE to enter idle mode when all of the
following conditions are met:
l The movement speed of the UE is greater than or equal to 30 km/h during the camping.
l The UE does not transmit data when it is camping on a cell.

eRAN
l The camping time is greater than or equal to 10s.

As the UE has data to transmit only when a heartbeat period begins, instructing the UE to
enter idle mode has no impact on the UE's services.
Figure 3-10 shows the working mechanism of the high-mobility-triggered idle mode feature.
Figure 3-10 Working mechanism of the high-mobility-triggered idle mode feature

eRAN
DRX and Signaling Control Feature Parameter Description 4 Related Features
4 Related Features
4.1 LBFD-002017 DRX

Prerequisite Features
None
Mutually Exclusive Features

Feature ID Feature Name Description
LOFD-001008 Ultra High Speed DRX does not take effect in high-speed and
Mobility ultra-high-speed mobility scenarios.
LOFD-001007 High Speed

Mobility

eRAN
Impacted Features
Function Description
Name
Scheduling DRX has the following impact on scheduling:

l When no system information is being delivered and no paging is
performed, the eNodeB enables resource scheduling for the UE only
during active time.
l In DRX mode, the UE sends an SR when there is data in the UE buffer,
regardless of whether the UE is in the active state. Even if the UE is in
the sleep state, it immediately switches to the active state and begins to
monitor the PDCCH. When the UE receives the data initially sent on the
PDCCH, the eNodeB starts the DRX Inactivity Timer to increase the
active time until the UE obtains resources.
l For downlink scheduling (provided in LBFD-002025 Basic Scheduling
and LBFD-002005 DL Asynchronous HARQ), HARQ feedback takes
priority over DRX. That is, UEs can provide HARQ feedback regardless
of whether they are in active time.
l For uplink scheduling (provided in LBFD-002025 Basic Scheduling and
LBFD-002006 UL Synchronous HARQ), when the eNodeB needs to
deliver an uplink grant for a pending retransmission in a TTI, the eNodeB
must ensure that the TTI is in active time. In this way, the eNodeB can
send ACK/NACK feedback or schedule a retransmission, and the UE can
receive HARQ feedback in this TTI.
l There is a small chance that false detection of SRs may result in DRX
status information inconsistency between the eNodeB and the UE. When
DRX is enabled, uplink and downlink BLERs may increase. To reduce
false detection of SRs, you are advised to take one or more of the
following actions:
– Set the CELLULSCHALGO.SriFalseDetThdSwitch parameter to
ON when there are no VoIP services.
– Set the CellAlgoSwitch.UlSchSwitch parameter to
PuschDtxSwitch-1. This setting may lead to an increase in the
service drop rate in weak coverage or strong interference scenarios.
– Set the CellAlgoSwitch.UlSchSwitch parameter to
UlEnhancedSrSchSwitch-1.
For details, see Scheduling Feature Parameter Description.
l When the UE is in the uplink pre-scheduling state, the eNodeB instructs
the UE to exit the uplink pre-scheduling state after the UE enters DRX
mode. Upon exiting DRX mode, the UE enters the pre-scheduling state.
l When TTI bundling (provided by LOFD-001048 TTI Bundling) is used
for the UE, the eNodeB does not instruct the UE to enter DRX mode
unless required during ANR measurement. When the UE is in DRX
mode, the eNodeB instructs the UE to exit DRX mode after TTI bundling
is initiated. When the UE is performing ANR measurements in DRX
mode, the eNodeB does not instruct the UE to exit DRX mode.

eRAN
Name
l The eNodeB activates LOFD-001016 VoIP Semi-persistent Scheduling

based on the DlSpsDrxDecouplingSwitch option of the
CellDlschAlgo.DlEnhancedVoipSchSw parameter:
– If this option is deselected, the eNodeB can activate downlink semi-
persistent scheduling only when the value of
DrxParaGroup.LongDrxCycle is less than or equal to the value of
CellDlschAlgo.DlSpsInterval.
– If this option is selected, the eNodeB can activate downlink semi-
persistent scheduling regardless of the settings of
DrxParaGroup.LongDrxCycle and CellDlschAlgo.DlSpsInterval.
In this situation, the initial transmission over the PDSCH can be semi-
persistently scheduled in the sleep time. If the UE does not support
the reception of semi-persistently scheduled PDSCH data in the sleep
time, the downlink voice packet loss rate will increase.
Connection The UE immediately responds to random access requests, regardless of

Manageme whether it is in the active state.
nt
Mobility During different stages of a handover, DRX functions in different ways:

Manageme l When the handover process starts:
nt in After receiving a handover decision indicating that the handover request
Connected has been accepted, the source eNodeB sends an RRC Connection
Mode Reconfiguration message to instruct the UE to exit DRX mode. If this
happens during sleep time, the UE will not receive the message until after
the next active time arrives.
l When the handover succeeds:
The eNodeB determines whether to apply DRX to the UE based on
whether DRX is enabled.
l When the handover fails:
The UE remains in the current cell, and the source eNodeB checks
whether the UE can enter DRX mode.
NOTE
For details about the handover process in DRX mode, see Intra-RAT Mobility
Management in Connected Mode Feature Parameter Description.

eRAN
Name
Measureme When measurement configurations conflict with DRX configurations,

nt measurement takes priority.
NOTE
For details about the measurement process in DRX mode, see Intra-RAT Mobility
Management in Connected Mode Feature Parameter Description.
UE measurement in LTE can be classified into the following types, where
common measurement is suitable for intra-frequency measurement and gap-
assisted measurement is suitable for inter-frequency measurement and inter-
RAT measurement.
l Common measurement
For random access, the UE enters the active state if it is in sleep time and
then uses the first available random access channel (RACH) to send UL
measurement reports.
In other scenarios, the UE sends measurement reports only in active time.
If the UE is in the sleep state, it will send measurement reports in active
time in the next DRX cycle.
l Gap-assisted measurement
In gap-assisted measurement, gaps with 6 ms each are generated every 40
ms or 80 ms. To reduce the impact on data transmission, the eNodeB
needs to generate gaps in sleep time. If gaps have been configured for the
UE, the UE cannot enter DRX mode.
The UE cannot enter DRX mode in either of the following situations:
– Periodic measurement reporting based on the gap-assisted
measurement has been enabled for the modules that have subscribed
to it. Such a module may be the FARS cell tracing module or the
Nastar module.
– Some operations are performed by mistake, which can be checked by
querying the operation logs on the U2000.
l Handover-oriented measurement
When the eNodeB receives a coverage-based inter-RAT event A2 report
from the UE or ultra-flash CSFB triggers GERAN measurement, DRX
parameters for GERAN measurement are configured if the measurement
gap is activated for the first time. If the DRX parameters specific to
GERAN measurement have been configured and the
CellDrxPara.MeasDrxSpecSchSwitch parameter is set to ON(On), the
eNodeB performs special uplink and downlink scheduling to make the
UE stay in sleep time for a long period, prolonging the time for GERAN
measurement and shortening the delay in measurement reporting.

eRAN
Name
CQI 1. In DRX mode, the UE turns off its receiver intermittently. This restricts
Reporting the delivery of channel quality indicator (CQI) and sounding reference
signal (SRS) measurement configurations from the eNodeB and the
report of these CQI and SRS measurement results from the UE.
Therefore, the eNodeB cannot deliver these measurement configurations
in sleep time, and the UE must report the CQI and SRS measurement
results in compliance with protocol requirements.
For UEs complying with 3GPP Release 8, CQIs, precoding matrix
indicators (PMIs), and rank indicators (RIs) can be reported over the
PUCCH only in active time. For UEs complying with 3GPP Release 9,
CQIs, PMIs, and RIs can be reported over the PUCCH only in the On
Duration.
The CellDrxPara.CqiMask parameter controls when CQIs, PMIs, and
RIs can be reported in the On Duration:
l If this parameter is set to ON, CQIs, PMIs, and RIs can be reported
only in the On Duration.
l If this parameter is set to OFF, CQIs, PMIs, and RIs can be reported
in active time.
l SRSs can be sent only in active time.
1. If an SRI is falsely detected during sleep time, the eNodeB and the UE
will be in different DRX states. The eNodeB will be in the active state
and monitor CQIs while the UE will still be in the sleep state and not
send CQIs.
False detection of CQIs has a negative impact. Falsely detected CQIs are
considered as reliable CQIs. These CQIs are measured by counters,
leading to inaccurate CQI measurements. In addition, these CQIs are
involved in layer 2 (L2) CQI filtering, leading to inaccurate CQI filtering
results and affecting the downlink throughput.
In this scenario, you are advised to turn on the PUCCH CQI reliability
optimization switch by selecting the
PUCCH_CQI_FALSE_DETECTION_SW option of the
CellCqiAdjAlgo.CqiOptSwitch parameter. This setting reduces the false
detection probability and increases the detection reliability for the CQIs
of PUCCHs in formats 2, 2a, and 2b. It increases the CQI measurement
accuracy and downlink user-perceived rate.
2. CQI configurations affect the settings of DRX parameters controlled by
the eNodeB. The eNodeB can automatically adjust the value of the
operator-defined DrxParaGroup.OnDurationTimer parameter so that
the number of CQIs reported by the UE during a period meets the
requirements for downlink scheduling performance.
NOTE
Currently, most UEs that comply with 3GPP Release 9 do not support CQI mask. You
are advised to retain the default value OFF of the CellDrxPara.CqiMask parameter
for these UEs.

eRAN
Name
Timing When SRSs are used for timing control, the time alignment (TA)
Control measurement precision for uplink synchronization depends on the number of
times the UE reports SRSs. To acquire sufficient SRSs, the eNodeB
adaptively adjusts the long cycle based on the SRS configurations of the UE
and the period set for delivery of TA measurements to the UE. Therefore, the
value delivered to the UE may differ from that set by MML commands. The
value must be a multiple of 10 ms because the SRS reporting period is a
multiple of 10 ms and the CQI reporting period is a multiple of 5 ms for
Huawei eNodeBs. The specific value depends on other parameters:
l When TimeAlignmentTimer.TimingAdvCmdOptSwitch is set to ON,
the eNodeB does not restrict the setting of
DrxParaGroup.LongDrxCycle for the sake of ensuring timing
performance. However, it is recommended that the cycle should not
exceed 320 ms. Settings greater than 320 ms may affect uplink timing
performance.
l When TimeAlignmentTimer.TimingMeasMode is set to
ALLMEASMODE, the eNodeB does not impose restrictions on DRX
parameter settings.
When demodulation reference signals (DMRSs) are used for timing control
and DRX is enabled, at least one active time must exist during the period set
for delivery of TA measurements so that the eNodeB can deliver scheduling
information to trigger the delivery.
NOTICE
The eNodeB configures DRX parameters for UEs based on parameter validity,
protocol compatibility, and chip compatibility. For example, UEs with Qualcomm
chips consider the settings of certain DRX parameters invalid and the RRC connection
needs to be reestablished. These DRX parameters may be adjusted after the validity
check. Validity check is performed to see whether:
l The long cycle should be a multiple of the short cycle. Otherwise, the short cycle is
automatically adjusted to an appropriate value.
l The long cycle should be a multiple of 10. Otherwise, it is automatically adjusted
to an appropriate value.
l The OnDurationTimer value should be less than the short cycle. Otherwise, the
short cycle is not configured.
l The OnDurationTimer value should be less than the long cycle. Otherwise, the
DRX parameters are not configured.

eRAN
Name
Carrier When carrier aggregation (CA) is enabled, the DRX mechanism works as
Aggregatio follows:
n l If DRX is enabled in both the primary serving cell (PCell) and the
secondary serving cell (SCell) for a CA UE and the serving eNodeB of
the PCell sends an MCE to activate the SCell, the eNodeB will handle
the UE states in the cells as follows:
– If the UE has entered DRX mode in the PCell, the eNodeB will
instruct the UE to enter DRX mode in the SCell, with the DRX
parameters for the PCell applied to the SCell.
– If the UE has not entered DRX mode in the PCell, the eNodeB will
determine whether the UE should enter DRX mode in both the PCell
and SCell based on the traffic volume of the UE.
l If DRX is enabled in the PCell but disabled in the SCell, the UE will exit
DRX mode (if it has entered this mode) after the SCell is configured for
the UE.
l If DRX is disabled in the PCell, the UE will not enter DRX mode in
either the PCell or the SCell, regardless of whether DRX is enabled in the
SCell.
For details about CA features, see Carrier Aggregation Feature Parameter
Description.

None

Feature ID Feature Name Description
LOFD-001008 Ultra High Speed Dynamic DRX does not take effect in high-
Mobility speed and ultra-high-speed mobility scenarios.
LOFD-001007 High Speed

Mobility

eRAN
Impacted Features
Feature ID Feature/ Description
Function
Name
LBFD-002017 DRX l The DRX parameters for UEs in the

synchronization state used in LOFD-00110501
Dynamic DRX are the same as the DRX
parameters used in LBFD-002017 DRX.
However, the two features do not depend on each
other.
l When LOFD-00110501 Dynamic DRX is
enabled, the switch for LBFD-002017 DRX
cannot control whether the DRX parameters for
UEs in the synchronization state take effect.
N/A Others The other impacted features of LOFD-00110501

Dynamic DRX are the same as those of
LBFD-002017 DRX. For details, see 4.1
LBFD-002017 DRX.

None

None
Impacted Features
None

eRAN
DRX and Signaling Control Feature Parameter Description 5 Network Impact
5 Network Impact
5.1 LBFD-002017 DRX

System Capacity
None
Network Performance
The sleep time in DRX helps reduce UE power consumption but may increase delay for
ongoing services, resulting in decreased traffic volume or throughput.
DRX has the following impacts on network performance:
l If the value of the DrxParaGroup.OnDurationTimer parameter is too small, the VoIP

capacity will decrease, or the uplink and downlink packet loss rates for voice services in
heavy-load scenarios will increase. A large value for this parameter results in reduced
UE power saving.
l If the value of the DrxParaGroup.LongDrxCycle parameter is too large, the CQI
reporting period will increase, and the traffic volume or throughput under functions such
as scheduling and multiple-input-multiple-output (MIMO) will decrease. In addition, the
handover success rate decreases, and the service drop rate increases. These impacts are
more obvious in high-speed mobility or weak-coverage scenarios. If the value of the
DrxParaGroup.LongDrxCycle parameter is too small, the UE power saving effect will
deteriorate.
l If the value of the DrxParaGroup.DRXInactivityTimer parameter is too small, the
uplink and downlink cell throughput as well as user-perceived uplink and downlink
throughput may decrease, or the uplink and downlink packet loss rates will increase for
voice services when there are a large number of UEs in connected mode (for example,
when the average number of UEs in connected mode exceeds 100). When there are no
VoIP services, you are advised to set the DrxParaGroup.DRXInactivityTimer
parameter to be greater than or equal to 80 ms.
l If the sleep time is too short, ANR measurement will fail.
l UEs cannot be scheduled in sleep time. In this situation, the resource allocation for TA
measurement is affected. Consequently, the L.RRC.StateTrans.Syn2Unsyn counter

eRAN
value and the number of RRC connection reestablishments are affected. As a result, the
random access success rate is affected.
l After DRX is enabled, throughput may increase:
– Before DRX is enabled, multiple small packets need to be scheduled multiple times.
After DRX is enabled, such packets are accumulated in sleep time and can be
scheduled at one time. The saved PDCCH resources can be used to transmit
downlink data and increase downlink user-perceived throughput.
– In throughput calculation, data in the last TTI is removed and cell center user
(CCU) data is more likely to be removed than cell edge user (CEU) data. Before
DRX is enabled, small packets account for a high proportion and therefore CCU
data is far more likely to be removed than CEU data. After DRX is enabled, small
packets are accumulated before scheduling and the probability of removing CCU
data is lowered. As the small packets of CCUs can be counted, the measured uplink
and downlink user-perceived throughput is higher than before.
l After DRX is enabled, UEs can report CQIs only during active time. If the channel
quality of CEUs fluctuates significantly during sleep time, the UEs cannot report CQIs
for modulation and coding scheme (MCS) adjustment in a timely manner. As a result, the
bit error rate (BER) for CEUs may increase, and the downlink packet loss rate for voice
services or data services may rise.
l When a UE initiates CSFB during a handover, the eNodeB preferentially processes the
handover but fails to process the CSFB. After the handover, the mobility management
entity (MME) initiates the CSFB again. When DRX is enabled, the presence of the sleep
time increases the probability of CSFB during handovers. In this case, the number of
CSFB-triggered handover failures and the number of CSFB-triggered handover attempts
may increase, while the number of successful CSFB executions remains unchanged. As a
result, the CSFB-triggered handover success rate may decrease, but this has a very little
impact on user experience.
l After DRX is enabled, the long cycle specified by the DrxParaGroup.LongDrxCycle
parameter must be shorter than the timer length specified by the
RlcPdcpParaGroup.DiscardTimer parameter. Otherwise, packet loss may occur for
ping services, small packet services, or VoIP services, especially for services of QCIs 1
and 5.
l To reduce the CPU usage, you are advised to:
– Disable DRX for heavy traffic scenarios. Otherwise, multiple timers need to be
maintained for each UE. The CPU consumption of the baseband processing board
increases with the increasing number of UEs.
– Set the CellDrxPara.FddEnterDrxThd and CellDrxPara.FddExitDrxThd
parameters to 1000. Otherwise, a large amount of RRC connection reconfiguration
signaling is generated and the CPU usage of the main control board or BBP is high.
l DRX takes effect once the E-UTRAN radio access bearer (E-RAB) is set up, leading to
failures in UE pre-scheduling. At the same time, some UEs may fail to send SRs due to
compatibility issues. This leads to fluctuations in the E-RAB setup success rate. It is
recommended that the smart preallocation function be enabled to avoid these issues.
l When DRX is enabled and the sleep time specified by the
DrxParaGroup.LongDrxCycle, DrxParaGroup.OnDurationTimer, or
DrxParaGroup.DRXInactivityTimer parameter is lengthened, the probability of false
detection of SRs in sleep time increases. False detection of SRs causes the eNodeB to
periodically detect CQIs (ranging from 0 to 15) when UEs have not reported any. As a
result, the eNodeB detects a large number of random CQI values ranging from 0 to 15.
This leads to fluctuations in both the CQI distribution and the average CQI. For example,

eRAN
when most UEs are close to the eNodeB and the proportion of high-order CQIs (for
example, CQIs 11 to 15) is very high, the average CQI may decrease. As these random
values are detected in sleep time (when the UEs have no data to transmit), these random
values have no impact on scheduling.
l In DRX mode, when the eNodeB interprets no responses from the UE as "DTX"
(indicating discontinuous transmission) for two consecutive times, it immediately stops
downlink scheduling because the DRX state it maintains is inconsistent with that of the
UE. (This inconsistency is caused by false detection of SRs or missing detection of
PDCCHs.) However, this mechanism will decrease downlink throughput if two
consecutive HARQ reports over the PUCCH are erroneously decoded as "DTX" or if a
CA UE reports "DTX/NACK" but the eNodeB regards it as "DTX". To lower the
probability that the eNodeB erroneously stops downlink scheduling and to increase
downlink throughput, the CellDrxPara.DrxRcvDtxProSwitch parameter has been
introduced. If this switch is turned on, the eNodeB will not immediately stop downlink
scheduling; instead, it stops downlink scheduling only when the timer defined by the
DrxParaGroup.DRXInactivityTimer parameter expires. In normal scenarios, turning on
this switch may increase downlink initial block error rate (IBLER). In heavy traffic
scenarios, turning on this switch may prolong the active time of cell edge users (CEUs)
and increase their data retransmission probability when two consecutive DTX states are
detected. As CEUs have a higher retransmission scheduling priority than cell center
users (CCUs), downlink throughput will decrease and downlink IBLER will increase.
l SRI offset reconfiguration for DRX may have the following negative impact:
– PUCCH resources may be wasted or adjusted too early. This impact may further
affect L2-related KPIs, for example, increase two or fewer uplink RBs used, reduce
two or fewer available PUSCH RBs, reduce uplink throughput by 0% to 14%, and
reduce perceived uplink data rates by 0% to 14%.
– The E-RAB setup delay may be prolonged and the E-RAB setup success rate may
decrease.
– In heavy load scenarios, the service drop rate may increase and the RRC connection
success rate may decrease.
– The average CPU usage of main control boards and BBPs increase by 0% to 3%.
The impact on key performance indicators (KPIs) is dependent on the specific service type,
application scenario, and parameter configuration. Specific KPIs are not listed in this section.
NOTE
When DRX is enabled, the eNodeB instructs the UE to exit the preallocation state. The performance of
TCP services with ping delay and a small size deteriorates, the uplink throughput increases, and the
number of RBs for uplink frequency-selective scheduling and that for UL Comp decreases. For details,
see Scheduling Feature Parameter Description.
In DRX mode, you can enable smart preallocation to reduce the impact of UE exiting the preallocation
state. However, the power saving effect will deteriorate as the smart preallocation duration increases.
Turning on CellDrxPara.CovGsmMeasDrxCfgSwitch shortens the delay in measurement

reporting, avoids service drops due to too late handovers, and therefore decreases the service
drop rate. However, VoLTE users are not scheduled in sleep time, the scheduling interval is
prolonged, and voice quality may deteriorate.
When CellDrxPara.MeasDrxSpecSchSwitch is on, the eNodeB schedules UEs in a special

way, which provides more chances for UEs to send SRs but increases PDCCH overhead.
When the CCE resource is limited, delays (such as ping delay, access delay, handover delay)
for online UEs may be prolonged. It is recommended that this switch be on when the call drop

eRAN
rate is very high and there are not high requirements for ping delay, access delay, and
handover delay.

System Capacity
None
Network Performance
LOFD-00110501 Dynamic DRX has the same impact as LBFD-002017 DRX on network
performance. For details, see 5.1 LBFD-002017 DRX.
According to section 8.1.2.2 "E-UTRAN intra frequency measurements" in 3GPP TS 36.133
V10.0.0, the reference signal received power (RSRP) measurement period is a multiple of the
long DRX cycle. After DRX parameters for out-of-synchronization UEs are set, the RSRP
measurement period increases. As a result, the number of delayed handovers, service drops, or
RRC connection reestablishments increases.
If the RrcConnStateTimer.UeInactivityTimerDynDrx,
QCIPARA.UeInactivityTimerDynDrxQci parameter is set to a large value according to
operations in 6.2.2 Required Information, the large value has the following impacts:
l The total number of E-RAB releases decreases, while the number of abnormal E-RAB
releases slightly changes. The decreased number of E-RAB releases is equal to the
number of E-RABs in UE contexts when the UEs switch from the uplink
synchronization state to the uplink out-of-synchronization state.
To ensure the accuracy of the calculated service drop rate, add the value of the L.E-
RAB.Num.Syn2Unsyn counter to the denominator and subtract the value of the L.E-
RAB.Release.Unsyn counter from the denominator. The formula is as follows:
Service drop rate (%) = [L.E-RAB.AbnormRel]/([L.E-RAB.AbnormRel] + [L.E-
RAB.NormRel] + [L.E-RAB.Num.Syn2Unsyn] - [L.E-RAB.Release.Unsyn])
l The number of RRC connection establishments decreases significantly. In some
scenarios (for example, weak coverage scenarios), the number of failed RRC connection
setups does not decrease proportionally. The number of decreased RRC connection
setups converts into the number of times UEs switch from the out-of-synchronization
state to the synchronization state.
To ensure the accuracy of the calculated service RRC connection setup success rate, add
the value of the L.RRC.StateTrans.Unsyn2Syn.Succ counter to the numerator and add
the value of the L.RRC.StateTrans.Unsyn2Syn counter to the denominator. The
formula is as follows:
Service RRC connection setup success rate (%) = (L.RRC.ConnReq.Succ.Mt +
L.RRC.ConnReq.Succ.MoData + L.RRC.ConnReq.Succ.EMC +
L.RRC.ConnReq.Succ.HighPri + L.RRC.ConnReq.Succ.DelayTol +
L.RRC.StateTrans.Unsyn2Syn.Succ) /(L.RRC.ConnReq.Att.Mt +
L.RRC.ConnReq.Att.MoData + L.RRC.ConnReq.Att.EMC +
L.RRC.ConnReq.Att.HighPri + L.RRC.ConnReq.Att.DelayTol +
L.RRC.StateTrans.Unsyn2Syn)
l The number of E-RAB setups decreases significantly. In some scenarios (for example,
weak coverage scenarios), the number of failed E-RAB setups does not decrease

eRAN
proportionately. The number of decreased E-RAB setups converts into the number of
times UEs switch from the out-of-synchronization state to the synchronization state.
To ensure the accuracy of the calculated E-RAB setup success rate, add the value of the
L.E-RAB.StateTrans.Unsyn2Syn.Succ counter to the numerator and add the value of
the L.E-RAB.StateTrans.Unsyn2Syn.Att counter to the denominator. The formula is as
follows:
E-RAB setup success rate (%) = (L.E-RAB.SuccEst + L.E-
RAB.StateTrans.Unsyn2Syn.Succ)/(L.E-RAB.AttEst + L.E-
RAB.StateTrans.Unsyn2Syn.Att)
l The number of UEs in connected mode increases.
l The number of handovers increases in networks with high UE mobility.
l If the RrcConnStateTimer.UeInactTimerDynDrxQci1 parameter is set to a smaller
value, the UE will be released earlier when the QCI 1 bearer does not carry any service
and the UE will initiate RRC connection requests more frequently. As the number of
normal releases increases, some KPIs will improve, for example, the QCI 1 service drop
rate will decrease. A larger parameter value will result in the opposite effects.
When dynamic DRX is enabled, dedicated preambles are used in the switching from the out-
of-synchronization state to the synchronization state caused by downlink data transmission
and the number of contention-based random access attempts decreases. If the number of
contention-based random access failures remains unchanged, the contention-based random
access success rate will decrease.
When dynamic DRX is enabled and the timer specified by the

RrcConnStateTimer.UlSynTimerDynDrx parameter expires, the eNodeB increases the
DrxParaGroup.LongDrxCycle parameter value to, for example, 1280 ms. This long cycle
increases the probability of false detection of SRs in sleep time. False detection of SRs causes
the eNodeB to periodically detect CQIs (ranging from 0 to 15) when UEs have not reported
any. As a result, the eNodeB detects a large number of random CQI values ranging from 0 to
15. This leads to fluctuations in both the CQI distribution and the average CQI. For example,
when most UEs are close to the eNodeB and the proportion of high-order CQIs (for example,
CQIs 11 to 15) is very high, the average CQI may decrease. As these random values are
detected in sleep time (when the UEs have no data to transmit), these random values have no
impact on scheduling.
When dynamic DRX is enabled and the timer specified by the

RrcConnStateTimer.UlSynTimerDynDrx parameter expires, the eNodeB uses a protection
mechanism to ensure that the DRX parameters for the out-of-synchronization state can be sent
to the UE. During the protection period, if the UE has uplink or downlink data to transmit or
the eNodeB delivers a TA command to the UE, the values of the following counters may
fluctuate, as shown in Figure 5-1:
l L.RRC.StateTrans.Unsyn2Syn
l L.RRC.StateTrans.Syn2Unsyn
l L.RRC.StateTrans.Unsyn2Syn.Succ
l L.E-RAB.Num.Syn2Unsyn
l L.E-RAB.StateTrans.Unsyn2Syn.Succ
l L.E-RAB.StateTrans.Unsyn2Syn.Att
l L.E-RAB.Release.Unsyn

eRAN
Figure 5-1 Counter fluctuation principle

System Capacity
No impact.
Network Performance
This feature decreases the number of handovers for fast-moving UEs, reduces the impact of
handover signaling on the network, and lowers the CPU usage of the eNodeB.

eRAN
DRX and Signaling Control Feature Parameter Description 6 Engineering Guidelines
6 Engineering Guidelines
6.1 Engineering Guidelines for LBFD-002017 DRX

This section provides guidelines for configuring LBFD-002017 DRX.
6.1.1 When to Use

DRX is recommended when UE power saving is preferred and DRX-induced service delay is
tolerable.
It is recommended that DRX parameters for coverage-based GERAN measurement be

configured (that is, CellDrxPara.CovGsmMeasDrxCfgSwitch be on) when E-UTRAN
coverage is poor (which leads to a high service drop rate) while GERAN coverage is good.
It is recommended that special scheduling during DRX for GERAN measurement be enabled
(that is, CellDrxPara.MeasDrxSpecSchSwitch be on) when the call drop rate is very high
and there are not high requirements for ping delay, access delay, and handover interruption
delay.
6.1.2 Required Information

Before deploying DRX, collect information about whether mainstream UEs on the live
network support DRX. Consult manufacturers of the UE chips about potential interoperability
testing (IOT) compatibility issues.
6.1.3 Planning
RF Planning
N/A
Network Planning
N/A

eRAN
Hardware Planning
N/A
6.1.4 Deployment
6.1.4.1 Requirements
Operating Environment
N/A
Transmission Networking
N/A
License
DRX is a basic feature and is not under license control.
6.1.4.2 Precautions
None
6.1.4.3 Hardware Adjustment

N/A
6.1.4.4 Activation
6.1.4.4.1 Data Preparation
Required Data
The following table describes the parameters that must be set in the CellDrxPara MO to
configure cell-level DRX parameters.
Parameter Parameter ID Setting Notes

Name
Local cell ID CellDrxPara.Loca None

lCellId

eRAN

Name
FDD enter DRX CellDrxPara.Fdd l A smaller parameter value results in a lower

threshold EnterDrxThd probability of entering DRX mode.
l A larger parameter value results in a higher
probability of entering DRX mode.
l If CellDrxPara.FddEnterDrxThd is set to
1000, the eNodeB does not instruct the UE to
enter DRX mode based on the traffic
measurements. Instead, the UE directly enters
DRX mode.
FDD exit DRX CellDrxPara.Fdd l A smaller parameter value results in a higher

threshold ExitDrxThd probability of exiting DRX mode.
l A larger parameter value results in a lower
probability of exiting DRX mode.
l If CellDrxPara.FddExitDrxThd and
CellDrxPara.FddEnterDrxThd are set to
small values and the difference between them
is small, the UE enters and exits DRX mode
frequently.
l If CellDrxPara.FddExitDrxThd is set to
1000, the eNodeB does not instruct the UE to
exit DRX mode based on the traffic
measurements. The UE no longer exits DRX
mode after entering DRX mode.
Data amount CellDrxPara.Data None

Statistic timer AmountStatTimer

eRAN

Name
DRX Policy CellDrxPara.Drx l If this parameter is set to

Mode PolicyMode DEFAULT(Default), the eNodeB will select
the DRX parameter group with the smallest
DrxParaGroup.LongDrxCycle value for the
UE. If multiple DRX parameter groups have
the smallest DrxParaGroup.LongDrxCycle
value, the eNodeB will select the DRX
parameter group corresponding to the QCI of
the service with the highest allocation/
retention priority (ARP) informed by the EPC.
l If this parameter is set to
QCIPRIORITY(QCI priority), the eNodeB
will select the DRX parameter group
corresponding to the QCI with the highest
priority. If no DRX parameter group is
configured for the QCI with the highest
priority, the eNodeB will not select any DRX
parameter group for this UE.
l If this parameter is set to
3GPPDEFINEDQCIPRIORITY, the
eNodeB will select the DRX parameter group
with the smallest
DrxParaGroup.LongDrxCycle value for the
UE. If multiple DRX parameter groups have
the smallest DrxParaGroup.LongDrxCycle
value, the eNodeB will select the DRX
parameter group corresponding to the QCI
with the highest priority defined by 3GPP
specifications.
DRX Start CellDrxPara.Drx If this switch is turned on, DrxStartOffset values

Offset StartOffsetOptS- can be randomly distributed within the range of 0
Optimization witch to (LongDrxCycle - 1) for UEs that are
Switch configured with only SRS resources, only
periodic CQI reporting, or neither. When the cell
serves a large number of UEs, the probability of
centralized downlink scheduling decreases, and
the downlink scheduling delay decreases, and UE
downlink throughput increases.
It is recommended that this switch be turned on
when SRS resources are not allocated for UEs or
there is a large number of UEs in the cell.
Scenario-specific Data
Scenario 1: Setting DRX Parameters for Common UEs

eRAN

Name
DRX Algorithm CellDrxPara.Drx None

Switch AlgSwitch
Short DRX CellDrxPara.Shor The value ON is recommended in scenarios with

Cycle Switch tDrxCycleSwitch tight delay constraints.
DRX State CellDrxPara.Drx When this parameter is set to

During UL StateDuringUlHa DRX_ACTIVE_FOR_VOICE, the eNodeB
HARQ Retrans rqRetx allows initial transmissions on uplink HARQ
retransmission occasions for voice UEs in DRX
mode.
The following table describes the parameters that must be set in the Drx MO to configure
eNodeB-level DRX parameters.

Name
DRX switch Drx.DrxAlgSwitc This version supports synchronization and

h delivery of the settings of both the eNodeB-level
and cell-level parameters.
l If the eNodeB-level parameter is set to
ON(On), the setting of the eNodeB-level
parameter, rather than the setting of the cell-
level parameter, takes effect in all cells served
by the eNodeB.
l If the eNodeB-level parameter is set to
OFF(Off), the setting of the cell-level
parameter for each cell takes effect
individually in the cells.
You are advised to set the cell-level parameter
and then set the eNodeB-level parameter to
OFF(Off). Otherwise, DRX is enabled in all cells
served by the eNodeB.
The following table describes the parameters that must be set in a DrxParaGroup MO to
configure DRX parameter groups.

Name
Local cell ID DrxParaGroup.L None

ocalCellId

eRAN

Name
DRX parameter DrxParaGroup.D None

group ID rxParaGroupId
Enter DRX DrxParaGroup.E l The value OFF is recommended for bearers

Switch nterDrxSwitch with tight delay constraints.
l The value ON is recommended for bearers
without tight delay constraints.
Category Type DrxParaGroup.C Set this parameter to LTE when applying the
atType other parameters in this MO to LTE UEs.
On Duration DrxParaGroup.O A larger parameter value results in a longer active

Timer nDurationTimer time and a shorter delay.
Set DrxParaGroup.OnDurationTimer to
PSF10(10 PDCCH subframes) if
DrxParaGroup.LongDrxCycle is set to
SF320(320 subframes).
DRX Inactivity DrxParaGroup.D A larger parameter value results in a longer active

Timer rxInactivityTimer time upon the arrival of new data in the On
Duration.
Set the DrxParaGroup.DrxInactivityTimer
parameter to PSF100(100 PDCCH subframes) if
the DrxParaGroup.LongDrxCycle parameter is
set to SF320(320 subframes).
DRX DrxParaGroup.D None

Retransmission rxReTxTimer
Timer

eRAN

Name
Long DRX DrxParaGroup.L A larger parameter value results in a longer sleep

Cycle ongDrxCycle time and a longer delay.
It is not recommended that this parameter be set
to a value greater than 320 ms when the
TimeAlignmentTimer.TimingAdvCmdOptS-
witch parameter is set to ON(On). Otherwise, the
uplink timing performance is affected.
l If power saving is a major concern, the value
SF320(320 subframes) is recommended for
better power saving effects, and the
TimeAlignmentTimer.TimeAlignmentTimer
parameter must be set to SF10240(10240
subframes).
NOTICE
Theoretically, a long cycle of 320 ms prolongs the
interval at which the measured RSRP is reported. This
may reduce the handover success rate, which is closely
related to UE mobility and weak-coverage networking.
Lab tests need to be conducted for specific scenarios. If
the test results match customer expectation, a long
cycle of 320 ms can be used. In cells where UEs move
at high speeds, use the default long cycle of 40 ms.
l For VoIP services with QCI 1, if
SpsSchSwitch(SpsSchSwitch) under the
CellAlgoSwitch.DlSchSwitch parameter is
selected, set this parameter to a value equal to
or less than the semi-persistent scheduling
period, that is, 20 ms. Otherwise, downlink
semi-persistent scheduling cannot take effect.
The length of the long cycle must be less than the
value of RlcPdcpParaGroup.DiscardTimer
(indicating the length of the Packet Data
Convergence Protocol (PDCP) data discard timer
for the corresponding QCI). Otherwise, packet
loss occurs during ping operations or low-traffic
services.
Short-Cycle DrxParaGroup.S None

DRX Supported upportShortDrx
Indication
Short DRX DrxParaGroup.S A larger parameter value results in a longer sleep

Cycle hortDrxCycle time and a longer delay.
Set the DrxParaGroup.ShortDrxCycle
parameter to SF80(80 subframes) if the
DrxParaGroup.LongDrxCycle parameter is set
to SF320(320 subframes).

eRAN

Name
DRX Short DrxParaGroup.D A larger parameter value results in a longer time

Cycle Timer rxShortCycleTim- during which the UE is in short cycles.
er You are advised to set the
DrxParaGroup.DrxShortCycleTimer parameter
to 1 if the DrxParaGroup.LongDrxCycle
parameter is set to SF320(320 subframes).
NOTE
l Performance-preferred and power saving-preferred parameter settings are recommended for

configuring DRX. For details, see "Scenario 1: Setting DRX Parameters for Common UEs" in
6.1.4.4.3 Using MML Commands.
l If the GlobalProcSwitch.QciParaEffectFlag parameter is set to ON(On), the CellQciPara and
Qcipara MOs take effect. If this parameter is set to OFF(Off), the CellStandardQci and
CellExtendedQci MOs take effect. The CellStandardQci and CellExtendedQci MOs are not
recommended as they will be removed in later versions. Therefore, the following uses CellQciPara
and Qcipara MOs as examples.
The following table describes the parameters that must be set in a CellQciPara MO to
configure cell-level QCI parameters.

Name
Local cell ID CellQciPara.Loc None

alCellId
QoS Class CellQciPara.Qci None

Indication
DRX parameter CellQciPara.Drx Modify the DRX parameters mapped to the QCI,
group ID ParaGroupId if required, in the identified parameter group.
QCI Priority For CellQciPara.Qci This parameter specifies the priority used for
DRX PriorityForDrx selecting a DRX parameter group for a
standardized QCI. A larger parameter value
indicates a lower priority.
If the bearers for a UE have multiple QCIs and
the CellDrxPara.DrxPolicyMode parameter is
set to QCIPRIORITY(QCI priority), the
eNodeB selects the DRX parameter group for the
UE based on the QCI-specific priorities.
The following table describes the parameter that must be set in a QciPara MO to map a
parameter group to an extended QCI.

eRAN

Name
Service Type QciPara.ServiceT For an extended QCI, the DRX parameter group
ype is determined as follows. First, this QCI is
mapped to a standardized QCI based on its
QciPara.ServiceType parameter value, which
may be IMSSignalling, LowDelay, or
TCPorBuffStreaming, corresponding to
standardized QCI 5, 7, or 9, respectively. Then,
the standardized QCI is mapped to a DRX
parameter group based on the
CellQciPara.DrxParaGroupId parameter value.
If the GlobalProcSwitch.QciParaEffectFlag parameter is set to OFF(Off), the

CellStandardQci and CellExtendedQci MOs take effect.
l The following table describes the parameters that must be set in a CellStandardQci MO
to map a parameter group to a cell-level standardized QCI.
Name
Local cell ID CellStandardQc None

i.LocalCellId
QoS Class CellStandardQc None

Indication i.Qci
DRX parameter CellStandardQc Modify the DRX parameters mapped to the

group ID i.DrxParaGroup QCI, if required, in the identified parameter
Id group.
QCI Priority CellStandardQc This parameter specifies the priority used for
For DRX i.QciPriorityFor selecting a DRX parameter group for a
Drx standardized QCI. A larger parameter value
indicates a lower priority.
If the bearers for a UE have multiple QCIs and
the CellDrxPara.DrxPolicyMode parameter is
set to QCIPRIORITY(QCI priority), the
eNodeB selects the DRX parameter group for
the UE based on the QCI-specific priorities.
l The following table describes the parameters that must be set in a CellExtendedQci MO
to map a parameter group to a cell-level extended QCI.
Name
Extended QCI CellExtendedQci Set this parameter if DRX parameters are

.ExtendedQci required for an extended QCI.

eRAN

Name
Local cell ID CellExtendedQci None

.LocalCellId
l The following table describes the parameter that must be set in an ExtendedQci MO to
map a parameter group to an extended QCI.

Name
Service type ExtendedQci.Ser For an extended QCI, the DRX parameter

viceType group is determined as follows. First, this QCI
is mapped to a standardized QCI based on its
ExtendedQci.ServiceType parameter value,
which may be IMSSignalling, LowDelay, or
TCPorBuffStreaming, corresponding to
standardized QCI 5, 7, or 9, respectively.
Then, the standardized QCI is mapped to a
DRX parameter group based on the
CellStandardQci.DrxParaGroupId parameter
value.
The following table describes the parameter that must be set in the TimeAlignmentTimer
MO to specify the length of the uplink time alignment timer for UEs in a cell.

Name
Uplink time TimeAlignmentTi When the DrxParaGroup.LongDrxCycle

alignment timer mer.TimeAlignme parameter value is greater than or equal to 80 ms,
ntTimer change the TimeAlignmentTim-
er.TimeAlignmentTimer parameter value from
1920 ms (the default value) to 10240 ms to
ensure that a long cycle does not affect
synchronization.
When the TimeAlignmentTim-
er.TimingAdvCmdOptSwitch parameter is set to
ON(On), it is recommended that the
TimeAlignmentTimer.TimeAlignmentTimer
parameter be set to SF10240(10240 subframes).
If the TimeAlignmentTim-
er.TimeAlignmentTimer parameter is set to a
small value, for example, less than SF5120(5120
subframes), the probability of uplink out-of-
synchronization for UEs in DRX mode increases.
Scenario 2: Setting DRX Parameters for Special UEs

eRAN
The following table describes the parameters that must be set in a SpidCfg MO to set the
DRX status for each subscriber profile ID (SPID).

Name
Spid SpidCfg.Spid Operators can use this parameter to designate a

UE as a special UE and enable it to enter DRX
mode. This helps reduce the service delay for
this UE.
Drx status SpidCfg.DrxStatu None

s

Name
DRX Algorithm CellDrxPara.Drx None

Switch AlgSwitch
Short DRX CellDrxPara.Shor None

Cycle Switch tDrxCycleSwitch
The following table describes the parameters that must be set in the CellDrxSpecialPara MO
to set special DRX parameters of a cell.
NOTE
The parameters described in the following table are applicable only to one of the following types of
UEs: (1) UEs that do not require power saving and their RFSP indexes are contained in the RFSP index
set; (2) UEs that do not support power saving, which is indicated by the reported UE capability
information.

Name
Long DRX Cycle CellDrxSpecialPa None

for Special UE ra.LongDrxCycleS
pecial
DRX CellDrxSpecialPa A larger parameter value results in a longer

onDurationTimer ra.OnDurationTi active time and a shorter delay. A smaller
for Special UE merSpecial parameter value results in a shorter active time
and a longer delay.
DRX Inactivity CellDrxSpecialPa This parameter specifies the length of the DRX
Timer for Special ra.DrxInactivityTi Inactivity Timer for the RFSP function.
UE merSpecial The value PSF10(10 PDCCH subframes) is
recommended.

eRAN

Name
Short DRX Cycle CellDrxSpecialPa None

Switch for ra.ShortDrxCycle
Special UE SwitchSpecial
Short DRX Cycle CellDrxSpecialPa None

for Special UE ra.ShortDrxCycle
Special
DRX Short Cycle CellDrxSpecialPa None

Timer for Special ra.DrxShortCycle
UE TimerSpecial
Scenario 3: Setting DRX Parameters for ANR Measurement

The following table describes the parameters that must be set in the CellDrxSpecialPara MO
to set special DRX parameters of a cell.

Name

for Intra-RAT ra.LongDrxCycle
ANR ForIntraRatAnr

for Inter-RAT ra.LongDrxCycle
ANR ForInterRatAnr
Scenario 4: Setting SRI Offset Reconfiguration for DRX

The following table describes the parameter that must be set in the CellPucchAlgo MO to set
the SRI algorithm switch. The following table describes the key parameters.

Name
SRI Algorithm CellPucchAlgo.Sr When this parameter is set to SriOffsetReConfig-

Switch iAlgoSwitch ForDrxSW-1, the eNodeB reconfigures the SRI
offset based on DRX parameters to save more UE
power. The reconfiguration takes effect when
DRX is enabled and the SRI reporting period is
not less than 40 ms. When this parameter is set to
SriOffsetReConfigForDrxSW-0, the
reconfiguration does not take effect.
Scenario 5: Setting DRX Parameters for GERAN Measurement

eRAN
To enable DRX for GERAN measurement for shortening the delay in measurement reporting,
turn on CellDrxPara.CovGsmMeasDrxCfgSwitch and set DRX parameters for GERAN
measurement. The following table describes the parameters that must be set in the
CellDrxPara MO.

Name
Coverage based CellDrxPara.Cov Turn on this switch when the following

GSM GsmMeasDrxCfg conditions are met:
Measurement Switch l E-UTRAN coverage is weak and the service
DRX Configure drop rate is high.
Switch
l GERAN coverage is strong.
l UEs support DRX for GERAN measurement.
l The negative impact of turning on this switch
is acceptable.
Measurement CellDrxPara.Mea Turn on this switch when the call drop rate is
DRX Special sDrxSpecSchSwit very high and there are not high requirements for
Schedule Switch ch ping delay, access delay, and handover
interruption delay.
Long DRX Cycle CellDrxPara.Lon A larger parameter value results in a shorter delay
for Measurement gDrxCycleForMe in measurement reporting but a larger impact on
as services.
Set this parameter as required. For example, set
this parameter to a large value if the service drop
rate needs to be significantly reduced and service
performance deterioration during measurement is
acceptable.
On Duration CellDrxPara.On A larger parameter value results in a shorter

Timer for DurTimerForMea measurement time and a smaller impact on
Measurement s services.
this parameter to a small value if the service drop
acceptable.
DRX Inactivity CellDrxPara.Drx A larger parameter value results in a shorter

Timer for InactTimerForMe measurement time and a smaller impact on
Measurement as services.
acceptable.

eRAN

Name
DRX CellDrxPara.Drx A smaller parameter value results in a high

Retransmission ReTxTimerForM probability that the UE enters the sleep time, a
Timer for eas shorter delay in measurement reporting, but a
Measurement larger impact on services.
acceptable.
Short DRX CellDrxPara.Sho This parameter specifies whether to configure

Switch for rtDrxSwForMeas short DRX cycle parameters for GERAN
Measurement measurement.
A short DRX cycle results in a smaller impact on
services but a longer delay in measurement
reporting.
Short DRX Cycle CellDrxPara.Sho A larger parameter value results in a shorter delay
for Measurement rtDrxCycleForMe in measurement reporting but a larger impact on
as services.
this parameter to a large value if the service drop
acceptable.
Short Cycle CellDrxPara.Sho A smaller parameter value results in lower UE

Timer for rtCycleTimerFor- power consumption but a longer service delay.
Measurement Meas
Scenario 6: Setting Whether to Remove DRX Parameters When Configuring Gap-

assisted Measurement Parameters
The following table describes the parameters that must be set in the CellDrxPara MO.

Name
GAP and DRX CellDrxPara.Gap None

Exclusive DrxExclusiveSwit
Switch ch
VoLTE Gap and CellDrxPara.Volt None

DRX Exclusive eGapDrxExclusiv
Switch eSwitch

eRAN
Scenario 7: Setting DRX Parameters for Gap Configuration Optimization Based on

SRIs
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO.

Name
Handover ENODEBALGOSWITCH It is recommended that the

Common .HoCommOptSwitch DrxBasedSriGapOptSwitch option be
Optimized selected to reduce the impact of gap-
Switch assisted measurement on SRs in DRX
mode.
NOTE
When this option is selected, SRIs are
considered in gap configuration, which
reduces the risk of service drops.
Deselecting this option has the opposite
effects.
6.1.4.4.2 Using the CME

For detailed operations, see CME-based Feature Configuration.
6.1.4.4.3 Using MML Commands

NOTE
If the GlobalProcSwitch.QciParaEffectFlag parameter is set to ON(On), the CellQciPara and

QciPara MOs take effect. This section provides MML command examples using these two MOs.
MML Command
Step 1 Run the MOD CELLDRXPARA command to turn on the cell-level DRX switch.
MOD CELLDRXPARA: LocalCellId=0, DrxAlgSwitch=ON, ShortDrxCycleSwitch=ON;
Step 2 (Optional) Run the MOD DRX command to turn off the eNodeB-level DRX switch and
enable the cell-level DRX.
MOD DRX: DrxAlgSwitch=OFF;
Step 3 Run the MOD GLOBALPROCSWITCH command with the QCI Parameter Effect Flag
parameter set to ON for the QCI parameters in the CellQciPara MO to take effect.
MOD GLOBALPROCSWITCH: QciParaEffectFlag=ON;
Step 4 Run the MOD CELLQCIPARA command to set a DRX parameter group for a standardized
QCI.
MOD CELLQCIPARA: LocalCellId=0, Qci=9,DrxParaGroupId=3;
Step 5 (Optional) Run the MOD QCIPARA command to set the service type for mapping an
extended QCI to a standardized QCI.
MOD QCIPARA: Qci=10,ServiceType=TCPorBuffStreaming;
Step 6 If the long cycle is equal to or longer than 80 ms, run the MOD TATIMER command to
modify the time alignment timer.

eRAN
MOD TATIMER: LocalCellId=0, TimeAlignmentTimer=SF10240;
Step 7 To reduce RRC reconfiguration signaling generated by UEs frequently entering and exiting
DRX mode, run the MOD CELLDRXPARA command to set the FDD enter DRX
threshold and FDD exit DRX threshold parameters to 1000. Then, UEs will not enter or exit
DRX mode based on traffic statistics.
MOD CELLDRXPARA: LocalCellID=0,FddEnterDrxThd =1000,FddExitDrxThd = 1000;
Step 8 Run the MOD DRXPARAGROUP command to turn on the switch of a specified DRX
parameter group and configure DRX parameters.
l Performance-preferred parameters
MOD DRXPARAGROUP: LocalCellId=0, DrxParaGroupId=3, EnterDrxSwitch=ON,
CatType=LTE, OnDurationTimer=PSF2, DrxInactivityTimer=PSF80, DrxReTxTimer=PSF8,
LongDrxCycle=SF40, SupportShortDrx=UU_ENABLE, ShortDrxCycle=SF20,
DrxShortCycleTimer=1;
l Power saving-preferred parameters

CatType=LTE, OnDurationTimer=PSF10, DrxInactivityTimer=PSF100,DrxReTxTimer=PSF8,
LongDrxCycle=SF320, SupportShortDrx=UU_ENABLE, ShortDrxCycle=SF80,
DrxShortCycleTimer=1;
Step 9 (Optional) To allow the eNodeB to select DRX parameters based on QCI priorities, run the
MOD CELLDRXPARA command to specify a DRX parameter selection policy and run the
MOD CELLQCIPARA command to set DRX priorities used in DRX parameter selection.
MOD CELLDRXPARA: LocalCellId=0, DrxPolicyMode=QCIPRIORITY;
MOD CELLQCIPARA: LocalCellId=0, Qci=9, QciPriorityForDrx=9;
Step 10 (Optional) To provide more scheduling chances for voice UEs, run the MOD
CELLDRXPARA command to set the DRX State During UL HARQ Retrans parameter.
MOD CELLDRXPARA: LocalCellId=0, DrxStateDuringUlHarqRetx=DRX_ACTIVE_FOR_VOICE;
----End
Step 1 Run the ADD SPIDCFG command to configure SPIDs.

ADD SPIDCFG: Spid=99, DrxStatus=FALSE, RatFreqPriorityInd=NOT_CFG;
Step 2 Run the MOD CELLDRXPARA command to turn on the DRX switch.
Step 3 Run the MOD CELLDRXSPECIALPARA command to configure DRX parameters.

MOD CELLDRXSPECIALPARA: LocalCellId=0,
CellDrxSpecialParaValid=TRUE,LongDrxCycleSpecial=SF10,
OnDurationTimerSpecial=PSF5, DrxInactivityTimerSpecial=PSF10,
ShortDrxCycleSwitchSpecial=UU_DISABLE;
----End
Step 1 Run the MOD CELLDRXSPECIALPARA command to set DRX parameters for ANR
measurements.
MOD CELLDRXSPECIALPARA: LocalCellId=0, LongDrxCycleForIntraRatAnr=SF320;
----End
Step 1 Run the MOD CELLPUCCHALGO command with the SriOffsetReConfigForDrxSW

option of the SRI Algorithm Switch parameter selected.

eRAN
MOD CELLPUCCHALGO: LocalCellId=0, SriAlgoSwitch=SriOffsetReConfigForDrxSW-1;
----End
Step 1 Run the MOD CELLDRXPARA command to set Coverage based GSM Measurement
DRX Configure Switch and Measurement DRX Special Schedule Switch to ON and set
the following parameters:
l Long DRX Cycle for Measurement
l On Duration Timer for Measurement
l DRX Inactivity Timer for Measurement
l DRX Retransmission Timer for Measurement
l Short DRX Switch for Measurement
l Short DRX Cycle for Measurement
l Short Cycle Timer for Measurement
----End

Step 1 Run the MOD CELLDRXPARA command to specify whether to remove DRX parameters
when configuring gap-assisted measurement parameters.
//Removing DRX parameters when configuring gap-assisted measurement parameters
for VoLTE UEs
MOD CELLDRXPARA: LocalCellId=0, VolteGapDrxExclusiveSwitch=ON;
for UEs regardless of their QCIs
MOD CELLDRXPARA: LocalCellId=0, GapDrxExclusiveSwitch=ON;
----End

SRIs
Step 1 Run the MOD ENODEBALGOSWITCH command to enable gap configuration

optimization based on SRIs.
MOD ENODEBALGOSWITCH: HoCommOptSwitch=DrxBasedSriGapOptSwitch-1;
----End
MML Command Examples

1. Configure performance-preferred parameters for common UEs.

MOD CELLQCIPARA: LocalCellId=0, Qci=9, DrxParaGroupId=3;
CatType=LTE, OnDurationTimer=PSF2, DrxInactivityTimer=PSF80,
DrxReTxTimer=psf8, LongDrxCycle=SF40, SupportShortDrx=UU_ENABLE,
ShortDrxCycle=SF20, DrxShortCycleTimer=1;
2. Configure power saving-preferred parameters for common UEs.

eRAN

MOD CELLQCIPARA: LocalCellId=0, Qci=9, DrxParaGroupId=3;
CatType=LTE, OnDurationTimer=PSF10,
DrxInactivityTimer=PSF100,DrxReTxTimer=psf8, LongDrxCycle=SF320,
SupportShortDrx=UU_ENABLE, ShortDrxCycle=SF80, DrxShortCycleTimer=1;

ADD SPIDCFG: Spid=99, DrxStatus=FALSE, RatFreqPriorityInd=NOT_CFG;
MOD CELLDRXSPECIALPARA: LocalCellId=0,
CellDrxSpecialParaValid=TRUE,LongDrxCycleSpecial=SF10,
OnDurationTimerSpecial=PSF5, DrxInactivityTimerSpecial=PSF10,
ShortDrxCycleSwitchSpecial=UU_DISABLE;

MOD CELLDRXSPECIALPARA: LocalCellId=0, LongDrxCycleForIntraRatAnr=SF320;

MOD CELLPUCCHALGO: LocalCellId=0, SriAlgoSwitch=SriOffsetReConfigForDrxSW-1;

MOD CELLDRXPARA: LocalCellId=0, CovGsmMeasDrxCfgSwitch=ON,
MeasDrxSpecSchSwitch=ON, LongDrxCycleForMeas=SF320, OnDurTimerForMeas=PSF40,
DrxInactTimerForMeas=PSF20, DrxReTxTimerForMeas=PSF6, ShortDrxSwForMeas=ON,
ShortDrxCycleForMeas=SF20, ShortCycleTimerForMeas=10;

for VoLTE UEs
MOD CELLDRXPARA: LocalCellId=0, VolteGapDrxExclusiveSwitch=ON;
for UEs regardless of their QCIs
MOD CELLDRXPARA: LocalCellId=0, GapDrxExclusiveSwitch=ON;

SRIs
MOD ENODEBALGOSWITCH: HoCommOptSwitch=DrxBasedSriGapOptSwitch-1;
6.1.4.5 Activation Observation

The activation observation procedure is as follows:
Step 2 Run the LST CELLQCIPARA command with the Local Cell ID and QoS Class Indication
parameters specified to query the DRX parameter group ID.
Step 3 Run the LST DRXPARAGROUP command. If the command output shows that the Enter
DRX Switch parameter value for a QCI is On, DRX has been activated for bearers with this
QCI.

eRAN
Step 4 Enable a UE to access the network and check the RRC Connection Reconfiguration message
(displayed as RRC_CONN_RECFG). If the message contains DRX parameters as shown in
Figure 6-1, the eNodeB has instructed the UE to enter DRX mode.
Figure 6-1 RRC Connection Reconfiguration (1)
NOTE
Due to the limitation of the CQI and SRS, the configured values for the DrxParaGroup.OnDurationTimer
and DrxParaGroup.LongDrxCycle parameters are inconsistent with the values delivered by the eNodeB.
----End

Ensure that an SPID has been set on the EPC for the international mobile subscriber identity
(IMSI) of a UE.
Step 1 Run the ADD SPIDCFG command to add the SPID configuration for the IMSI.
Step 3 Enable a UE to access the network and maintain light traffic in the uplink and downlink on
the UE. Then, check the RRC Connection Reconfiguration message (displayed as
RRC_CONN_RECFG) on the Uu interface. If the message contains RFSP-specific DRX
parameters as shown in Figure 6-2, the eNodeB has instructed the UE to enter DRX mode.

eRAN
----End

In FDD mode, the eNodeB configures or reconfigures DRX parameters for UEs during ANR
measurement regardless of whether the CellDrxPara.DrxAlgSwitch parameter is set to ON
or OFF.
Step 1 Run the MOD CELLDRXSPECIALPARA command to turn on the DRX switch and set the
Long DRX Cycle for Intra-RAT ANR and Long DRX Cycle for Inter-RAT ANR
parameters.
l The value of the Long DRX Cycle for Intra-RAT ANR parameter is used as the long
cycle if ANR measurements are performed on E-UTRAN cells.
l The value of the Long DRX Cycle for Inter-RAT ANR parameter is used as the long
cycle if ANR measurements are performed on GERAN or UTRAN cells.
Step 2 Check the RRC Connection Reconfiguration message on the Uu interface. (The RRC
Connection Reconfiguration message is delivered when ANR measurement is required.) If the
message contains DRX parameters as shown in Figure 6-3, the eNodeB has configured DRX
parameters for the UE during ANR measurement.

eRAN
Step 3 Run the MOD CELLDRXPARA command to turn off the DRX switch.
Step 4 Check the RRC Connection Reconfiguration message on the Uu interface. (The RRC
Connection Reconfiguration message is delivered when ANR measurement is required.) If the
message still contains DRX parameters, the eNodeB has configured DRX parameters for the
UE during ANR measurement.
----End

Ensure that DRX has taken effect and the SRI reporting period is not less than 40 ms.
Step 1 Run the MOD CELLPUCCHALGO command with the SriOffsetReConfigForDrxSW

option of the SRI Algorithm Switch parameter selected.
Step 2 Retain the default values of PUCCH-related parameters. For details, see Physical Channel
Resource Management Feature Parameter Description.
Step 3 The eNodeB configures the SRI resource for the UE in Msg4 during access in the RRC layer.
Step 4 The eNodeB reconfigures the SRI offset for the UE in the RRC connection reconfiguration
message delivered for DRX parameter configuration. Observe the
rrcConnectionReconfiguration IE on the Uu interface. If this IE includes DRX parameters, as
shown in Figure 6-4, SRI offset reconfiguration for DRX is successful.

eRAN
NOTE
If the SR is pending in sleep time because the possible TTIs have been occupied, the eNodeB cannot
reconfigure the SRI offset for the UE.
----End
6.1.4.6 Reconfiguration
eNodeBs are reconfigured in batches. For details, see the reconfiguration guide of eNodeBs.
6.1.4.7 Deactivation
Table 6-1 lists the parameter related to deactivation.

eRAN
Table 6-1 Parameter related to deactivation

MO Parameter Group Setting Notes
CellDrxPara DRX Algorithm Set the DRX Algorithm Switch

Switch parameter to OFF.
This feature can be deactivated by using the CME or MML commands.


Step 1 Run the MOD CELLDRXPARA command to set the DRX Algorithm Switch parameter to
OFF.
MOD CELLDRXPARA: LocalCellId=0, DrxAlgSwitch=OFF;
Step 2 Run the MOD TATIMER command to restore the setting of the Uplink time alignment
timer parameter.
----End
NOTE
The deactivation procedures for common UEs and special UEs are the same.
6.1.5 Maintenance
6.1.5.1 Performance Monitoring

After activating this feature, use the following counters for monitoring:
l L.Cdrx.Enter.Num and L.Cdrx.Exit.Num: used to monitor how often a UE enters and
exits DRX mode.
l L.Traffic.User.Cdrx.Avg: used to monitor the average number of UEs that enter DRX
mode on the network.
l L.Cdrx.Active.TtiNum and L.Cdrx.Sleep.TtiNum: used to indirectly monitor the
power saving effect of UEs on the network.
l L.Voip.Cdrx.Active.TtiNum and L.Voip.Cdrx.Sleep.TtiNum: used to monitor the
power saving effect of UEs performing VoIP services.
l Handover-related counters: used to monitor the handover performance of UEs in DRX
mode and the proportion of UEs in the DRX state during handovers.
This feature supports quick configuration of counter collection by feature using the U2000.
The measurement for the counters related to this feature can be set in a single operation.
These counters are determined by the counter-feature relationships listed in the performance
counter reference. For details about the operations, see "Quickly Setting Performance
Measurement by Feature" in iManager U2000 MBB Network Management System Product
Documentation.

eRAN
6.1.5.2 Parameter Optimization

After DRX is enabled, the following parameters may need to be modified:

Name
FDD enter CellDrxPara. This parameter specifies the threshold for UEs to enter
DRX FddEnterDrx DRX mode in an FDD cell. This threshold is used in the
threshold Thd DRX algorithm.
It is expressed as the proportion of the number of TTIs
with data transmission to the total number of TTIs. If
the traffic volume at a UE is equal to or below this
threshold, the eNodeB instructs the UE to stay in or
enter DRX mode. The value of the
CellDrxPara.FddEnterDrxThd parameter must be less
than that of the CellDrxPara.FddExitDrxThd
parameter under the same CellDrxPara MO.
The value 300 is recommended.
To prevent UEs from frequently entering and exiting
DRX mode for traffic volume reasons, it is
recommended that this parameter be set to 1000. With
this setting, the eNodeB does not determine whether
UEs need to enter or exit DRX mode based on traffic
volume; instead, the eNodeB instructs UEs to directly
enter DRX mode during the initial access. For this
purpose, the eNodeB sends DRX parameters to UEs
during the initial access without additional RRC
connection reconfiguration signaling.
FDD exit CellDrxPara. This parameter specifies the threshold for UEs to exit
DRX FddExitDrxT DRX mode in an FDD cell. This threshold is used in the
threshold hd DRX algorithm.
It is expressed as the proportion of the number of TTIs
with data transmission to the total number of TTIs. If
the traffic volume at a UE is equal to or higher than this
threshold, the eNodeB instructs the UE to stay in non-
DRX mode or exit DRX mode. The value of the
CellDrxPara.FddEnterDrxThd parameter must be less
than that of the CellDrxPara.FddExitDrxThd
parameter under the same CellDrxPara MO.
To prevent UEs from frequently entering and exiting
DRX mode for traffic volume reasons, it is
recommended that this parameter be set to 1000. After
the UE enters DRX mode, it does not exit until the
connection is released.

eRAN

Name
Data amount CellDrxPara. This parameter specifies the UE traffic measurement

Statistic timer DataAmountS period. The DRX algorithm determines whether a UE
tatTimer should exit or enter DRX mode based on the UE traffic
volume measured during this period.
Long DRX CellDrxSpeci This parameter specifies a long cycle for intra-RAT
Cycle for alPara.LongD ANR measurement. It is recommended that this
Intra-RAT rxCycleForInt parameter be set to a value greater than 256 ms to
ANR raRatAnr increase the measurement success rate.
6.1.5.3 Possible Issues
Fault Description
After accessing the network, the UE cannot enter DRX mode.
Troubleshooting
Step 1 Run the LST CELLDRXPARA command to check the value of DRX Algorithm Switch.
l If the value is Off, run the MOD CELLDRXPARA command to turn on the DRX
switch.
l If the value is On, go to Step 2.
Step 2 Run the LST CELLDRXPARA command to check the value of FDD enter DRX
threshold(per mill).
l If the value is inappropriate, change the value by referring to 6.2.4.4.1 Data
Preparation.
l If the value is appropriate, go to Step 3.
Step 3 Check whether the UE is performing services with a large traffic volume.
l If the UE is performing services with a large traffic volume, it does not enter DRX mode.
l If the UE is performing services (such as ping and VoIP services) with a very small
traffic volume, go back to Step 2 and then go to Step 4.
Step 4 Run the LST CELLQCIPARA command to query the DRX parameter group IDs
corresponding to the service QCIs of the UE.
Step 5 Run the LST DRXPARAGROUP command to check the Enter DRX Switch settings for the
DRX parameter group IDs.
l If any Enter DRX Switch value is Off, run the MOD DRXPARAGROUP command to
turn on the corresponding DRX switch or stop the ongoing service on the corresponding
bearer.
l If all the Enter DRX Switch values are On, contact Huawei engineers.
----End

eRAN
6.2 Engineering Guidelines for LOFD-00110501 Dynamic

DRX
This section provides guidelines for configuring LOFD-00110501 Dynamic DRX.
6.2.1 When to Use

Dynamic DRX is recommended in the following situations:
l Operators attach great importance to UE power saving.

In this scenario, you are advised to set a large difference between the value of the
RrcConnStateTimer.UeInactivityTimerDynDrx,
QCIPARA.UeInactivityTimerDynDrxQci parameter and that of the
RrcConnStateTimer.UlSynTimerDynDrx parameter. This enables UEs to be in the out-
of-synchronization state for a longer time, thereby improving the power saving effect. In
addition, it is recommended that both the CellDrxPara.FddEnterDrxThd and
CellDrxPara.FddExitDrxThd parameters be set to 1000 and the
CellDrxPara.DrxInactivityTimerUnsync parameter be set to 200 ms so that UEs can
save more power.
l Operators attach great importance to signaling reduction.
In this scenario, compare the total number of handovers with the number of E-RAB
setups. If the number of handovers is greater than 50% of the number of E-RAB setups,
the signaling storm is caused by handover signaling and therefore dynamic DRX is not
recommended. If the number of handovers is less than 50% of the number of E-RAB
setups and the average number of E-RAB setups for a single UE in peak hours is greater
than 200, dynamic DRX is recommended to reduce signaling overhead.
NOTE
If the RrcConnStateTimer.UeInactivityTimerDynDrx,
RrcConnStateTimer.UeInactTimerDynDrxQci1, or QCIPARA.UeInactivityTimerDynDrxQci
parameter is set to an inappropriate value, some UEs may experience incompatibility issues. Therefore,
you are advised to contact Huawei technical support in advance.
If the UE inactivity timer is set to a large value (for example, 200s) on the eNodeB side, some
UEs may experience incompatibility problems, that is, some UEs may be released and enter
idle mode before the inactivity timer expires, which leads to service drops. To prevent such
incompatible UEs from affecting network performance, you can enable the LBFD-081103
Terminal Awareness Differentiation feature and add these UEs to a dynamic DRX blacklist.
For details about the operation, see Terminal Awareness Differentiation Feature Parameter
Description.
It is recommended that the RrcConnStateTimer.UeInactTimerDynDrxQci1 parameter be set

to a value greater than the core-network-configured duration after which the link is released
because the called party does not answer the call. The purpose is to solve the problem that the
core network releases a VoLTE connection when the called party does not answer the call and
the inactivity timer of the calling party expires.

The information about the following timers is required before dynamic DRX deployment:

eRAN
l DRX UE inactivity timer, defined by one of the following:

– RrcConnStateTimer.UeInactivityTimerDynDrx
– RrcConnStateTimer.UeInactTimerDynDrxQci1
– QCIPARA.UeInactivityTimerDynDrxQci
Note that a DRX UE refers to a UE that supports DRX.
l DRX UL sync timer, defined by RrcConnStateTimer.UlSynTimerDynDrx
l Non-DRX UE inactivity timer, defined by one of the following:
– RrcConnStateTimer.UeInactiveTimer
– QCIPARA.UeInactiveTimerForQci
l Non-DRX UL sync timer, defined by RrcConnStateTimer.UlSynTimer
Assume that the non-DRX UE inactivity timer is set to the value a and the non-DRX UL sync
timer is set to the value b. Then, take one of the following actions
l If operators do not use dynamic DRX to reduce signaling, perform the following
operations to avoid KPI fluctuations:
– Set the DRX UE inactivity timer to the value a.
– Set the DRX UL sync timer to the value b.
To further save UE power, set the DRX UL sync timer shorter than the DRX UE
inactivity timer. This setting will not increase the number of UEs in connected mode.
l If operators use dynamic DRX to reduce signaling, perform the following operations to
ensure KPI accuracy:
– Set both DRX and non-DRX UL sync timers to the value a.
– Set both DRX and non-DRX UE inactivity timers to a value greater than the value
a.
After the preceding operations, the number of UEs in connected mode will increase.
For example, if the non-DRX UE inactivity timer is 20s. Then:
- Set both DRX and non-DRX UL sync timers to 20s.
- Set both DRX and non-DRX UE inactivity timers to 200s.
To evaluate the impact of adjustments to DRX and non-DRX UE inactivity timers, set the
non-DRX UE inactivity timer to a large value V (for example, 200s) and query the values of
the following counters. When the timers are adjusted between 0 to V, you can observe the
changes in signaling.
l L.Traffic.PktInterval.Num.Index0

eRAN
To evaluate the impact of DRX and non-DRX UL sync timers, use the following counters to
obtain out-of-synchronization durations. Longer durations indicate better power saving
effects.
l L.User.UL.Unsync.Dur.Index0
6.2.3 Planning
RF Planning
To reduce signaling bursts caused by frequent access and release on live networks without
coverage problems (for example, without ping-pong handovers), dynamic DRX prolongs the
time UEs stay in connected mode. The networks must meet the following coverage
requirements:
l No coverage holes
l No overshoot coverage
l No pilot pollution
l No path loss imbalance between uplink and downlink
Network Planning
N/A
Hardware Planning
N/A
6.2.4 Deployment
N/A
N/A

eRAN
License
The operator has purchased and activated the license for the feature listed in Table 6-2.
Table 6-2 License information

Feature ID Feature Model License NE Sales
Name Control Item Unit
LOFD-001105 Dynamic LT1S00DDR Dynamic eNodeB per cell

DRX X00 DRX(FDD)
To enable dynamic DRX after purchasing and activating this license, you must turn on
CellAlgoSwitch.DynDrxSwitch.
6.2.4.2 Precautions
If dynamic DRX is enabled, set the CellDrxPara.FddEnterDrxThd and
CellDrxPara.FddExitDrxThd parameters to 1000. Under these settings, the eNodeB directly
instructs UEs to enter or exit the synchronization state (without considering the traffic
volume), thereby reducing the number of RRC connection reconfiguration messages for
frequent entry and exit of the synchronization state.
To prevent UE compatibility issues, when dynamic DRX is enabled, you are advised to set
DRX parameters for all bearers on the live network, including bearers with QCIs 2, 3, and 7.
l If bearers with QCI 2 or 3 exist but the DRX parameters are not set for them, set
DrxParaGroup.LongDrxCycle to SF10, set DrxParaGroup.OnDurationTimer to
PSF8, and set DrxParaGroup.DrxInactivityTimer to PSF10.
l If bearers with QCI 7 exist, different DRX parameter groups can be used for the bearers
based on the QCI definitions of operators. For example, bind QCI 7 to DRX parameter
group 2 or 3 by running the MOD CELLSTANDARDQCI command.

N/A
6.2.4.4 Activation
Required Data
N/A
Scenario-specific Data
The following table describes the parameter that must be set in the CellAlgoSwitch MO to
modify the cell-level DRX parameters.

eRAN

Name
Dynamic DRX CellAlgoSwitch. None

switch DynDrxSwitch
The following table describes the parameters that must be set in the RrcConnStateTimer
MO to modify the UE control timer settings.
Name
UE Inactivity RrcConnStateTi l If UE power saving is required, you are

Timer Dynamic mer.UeInactivity advised to keep this parameter unchanged.
DRX TimerDynDrx l If signaling reduction is required, you are
advised to adjust this parameter to a larger
value.
UE Inactive RrcConnStateTi None

Timer for QCI1 mer.UeInactTim
Dynamic DRX erDynDrxQci1
Uplink Sync RrcConnStateTi None

Timer Dynamic mer.UlSynTimer
DRX DynDrx
NOTE
Reduced-signaling-preferred and power-saving-preferred parameter settings are recommended for

configuring dynamic DRX.
The following table describes the parameter that must be set in the CellDrxPara MO to
modify cell-level DRX parameters.

Name
QCI Parameter QciParaEffectFl This parameter determines whether parameters in

Effect Flag ag QciPara, CellQciPara, and CnOperatorQciPara
MOs take effect. The default value is OFF(Off).
The following table describes the parameters that must be set in a QCIPARA MO to
configure QCI-specific UE inactivity timers.

eRAN

Name
QCI-specific UE UeInactiveTimer None

Inactive Timer Pri
Priority
UE Inactivity UeInactivityTime None

Timer Dynamic rDynDrxQci
DRX for QCI
UE Inactive UeInactiveTimer None

Timer for QCI ForQci

Name
UnSync Long CellDrxPara.Lo None

DRX Cycle ngDrxCycleUnsy
nc
Onduration CellDrxPara.On None

Timer Unsync durationTimerU
nsync
DRX Inactivity CellDrxPara.Dr None

Timer Unsync xInactivityTimer-
Unsync
The following table describes the parameters that must be set in the CellAccess MO to avoid
compatibility issues of UEs.

Name
Repeat CellAccess.Rept None

Synchronization SyncAvoidInd
Avoid Indication
Repeat CellAccess.Rept None

Synchronization SyncAvoidTime
Avoid Time
NOTE
For details about compatibility issues of UEs, see 6.2.5.1 Performance Monitoring.

eRAN

MML Commands (Non-QCI-based)

Step 1 Run the LST RRCCONNSTATETIMER command to query the
RrcConnStateTimer.UeInactiveTimer parameter value (denoted by a) and
RrcConnStateTimer.UlSynTimer parameter value (denoted by b).
LST RRCCONNSTATETIMER:;
Step 2 If operators do not use dynamic DRX to reduce signaling, perform the following operations to
avoid KPI fluctuations:
l Set the RrcConnStateTimer.UeInactivityTimerDynDrx or
RrcConnStateTimer.UeInactTimerDynDrxQci1 parameter to the value a.
l Set the RrcConnStateTimer.UlSynTimerDynDrx parameter to the value b.
To save more power, ensure that the value of RrcConnStateTimer.UlSynTimerDynDrx is

less than the value of RrcConnStateTimer.UeInactivityTimerDynDrx or
RrcConnStateTimer.UeInactTimerDynDrxQci1 and the difference between the two values
must be large enough. This configuration does not increase the number of UEs in connected
mode.
MOD RRCCONNSTATETIMER: UeInactivityTimerDynDrx=35,UlSynTimerDynDrx=10;
Step 3 If operators use dynamic DRX to reduce signaling, perform the following operations to ensure
KPI accuracy:
1. Set the RrcConnStateTimer.UlSynTimerDynDrx and
RrcConnStateTimer.UlSynTimer parameters to the value a.
2. Set the RrcConnStateTimer.UeInactivityTimerDynDrx (or
RrcConnStateTimer.UeInactTimerDynDrxQci1) and
RrcConnStateTimer.UeInactiveTimer parameters to the same value greater than the
value a.
After these operations, the values of RrcConnStateTimer.UeInactivityTimerDynDrx (or

RrcConnStateTimer.UeInactTimerDynDrxQci1) and
RrcConnStateTimer.UeInactiveTimer are greater than the value a and the number of UEs in
connected mode increases.
MOD RRCCONNSTATETIMER:
UeInactivityTimerDynDrx=200,UeInactiveTimer=200,UlSynTimerDynDrx=20,UlSynTimer=20;
Step 4 After 6.1.4.4.1 Data Preparation is performed, if KPIs deteriorate, use a new formula to
calculate the service drop rate, as described in 6.1.4.4.1 Data Preparation. If KPIs do not
deteriorate, proceed to the next step.
Step 5 Run the MOD CELLDRXPARA command to configure DRX parameters for UEs in the out-
of-synchronization state. To save more power, it is recommended that the
CellDrxPara.FddEnterDrxThd and CellDrxPara.FddExitDrxThd parameters be set to 1000
and that the CellDrxPara.DrxInactivityTimerUnsync parameter be set to 200 ms. That way,
UEs in the synchronization state do not enter or exit DRX mode based on traffic statistics.
The DRX parameters for UEs in the synchronization state remain the same as those
configured before dynamic DRX is enabled.

eRAN
MOD
CELLDRXPARA:LocalCellID=0,LongDrxCycleUnsync=SF1280,OndurationTimerUnsync=PSF5,Drx
InactivityTimerUnsync=PSF200,FddEnterDrxThd =1000,FddExitDrxThd = 1000;
Step 6 Run the MOD CELLALGOSWITCH command to enable dynamic DRX:

MOD CELLALGOSWITCH:LocalCellId=0,DynDrxSwitch=DynDrxSwitch-1;
Step 7 Run the MOD RRCCONNSTATETIMER command to set

RrcConnStateTimer.UeInactivityTimerDynDrx (or
RrcConnStateTimer.UeInactTimerDynDrxQci1) and RrcConnStateTimer.UlSynTimer to
ensure the power saving effect for UEs that do not support DRX:
MOD RRCCONNSTATETIMER:UeInactiveTimer=20,UlSynTimer=180;
Step 8 (Optional) If UEs with compatibility issues exist in the network, you are advised to run the
MOD CELLACCESS command to set the CellAccess.ReptSyncAvoidInd and
CellAccess.ReptSyncAvoidTime parameters. The purpose is to reduce RRC connection
reconfiguration signaling. For details about how to determine whether UEs have compatibility
issues, see 6.2.5.1 Performance Monitoring.
MOD CELLACCESS:LocalCellId=0, ReptSyncAvoidInd=CFG, ReptSyncAvoidTime=100;
----End
MML Command Examples (Non-QCI-based)

Scenario 1: Setting Parameters for Power Saving Mode
MOD RRCCONNSTATETIMER:UeInactivityTimerDynDrx=35, UlSynTimerDynDrx=10;
MOD CELLDRXPARA:LocalCellID=0, LongDrxCycleUnsync=SF1280,
OndurationTimerUnsync=PSF5, DrxInactivityTimerUnsync=PSF200, FddEnterDrxThd=1000,
FddExitDrxThd=1000;
MOD CELLALGOSWITCH:LocalCellId=0, DynDrxSwitch=DynDrxSwitch-1;
Scenario 2: Setting Parameters for Reduced Signaling Mode

MOD RRCCONNSTATETIMER:UeInactivityTimerDynDrx=200, UeInactiveTimer=200,
UlSynTimerDynDrx=20, UlSynTimer=20;
MOD CELLDRXPARA:LocalCellID=0, LongDrxCycleUnsync=SF1280,
OndurationTimerUnsync=PSF5, DrxInactivityTimerUnsync=PSF200, FddEnterDrxThd=1000,
FddExitDrxThd=1000;
MOD CELLALGOSWITCH:LocalCellId=0, DynDrxSwitch=DynDrxSwitch-1;
MOD RRCCONNSTATETIMER:UeInactiveTimer=20, UlSynTimer=180;
MML Commands (QCI-based)

Step 1 Run the LST QCIPARA command to query the QCIPARA.UeInactiveTimerForQci
parameter value (denoted by a) and QCIPARA.UlSynTimerForQci parameter value (denoted
by b).
LST QCIPARA:;
Step 2 If operators do not use dynamic DRX to reduce signaling, perform the following operations to
avoid KPI fluctuations:
l Set the QCIPARA.UeInactivityTimerDynDrxQci parameter to the value a.
l Set the RrcConnStateTimer.UlSynTimerDynDrx parameter to the value b.
To save more power, ensure that the value of RrcConnStateTimer.UlSynTimerDynDrx is

less than the value of QCIPARA.UeInactivityTimerDynDrxQci and the difference between
the two values must be large enough. This configuration does not increase the number of UEs
in connected mode.

eRAN
MOD RRCCONNSTATETIMER:UlSynTimerDynDrx=10;
MOD QCIPARA:Qci=9,UeInactivityTimerDynDrxQci=35;
Step 3 If operators use dynamic DRX to reduce signaling, perform the following operations to ensure
KPI accuracy:
1. Set the values of RrcConnStateTimer.UlSynTimerDynDrx and
QCIPARA.UlSynTimerForQci to be the same as the value a.
2. Set the values of QCIPARA.UeInactivityTimerDynDrxQci and
QCIPARA.UeInactiveTimerForQci to the same value larger than the value a.
After the preceding operations are complete, the values of the
QCIPARA.UeInactivityTimerDynDrxQci and QCIPARA.UeInactiveTimerForQci
parameters are greater than the value a and the number of UEs in connected mode increases.
MOD
QCIPARA:Qci=9,UeInactiveTimerForQci=200,UlSynTimerForQci=20,UeInactivityTimerDynDr
xQci=200;
Step 4 After Step 3 is performed, if KPIs deteriorate, use a new formula to calculate the service drop
rate, as described in 6.1.4.4.1 Data Preparation. If KPIs do not deteriorate, proceed to the
next step.
Step 5 Run the MOD CELLDRXPARA command to configure DRX parameters for UEs in the out-
of-synchronization state. To save more power, it is recommended that the
CellDrxPara.FddEnterDrxThd and CellDrxPara.FddExitDrxThd parameters be set to 1000
and that the CellDrxPara.DrxInactivityTimerUnsync parameter be set to 200 ms. That way,
UEs in the synchronization state do not enter or exit DRX mode based on traffic statistics.
The DRX parameters for UEs in the synchronization state remain the same as those
configured before dynamic DRX is enabled.
MOD
CELLDRXPARA:LocalCellID=0,LongDrxCycleUnsync=SF1280,OndurationTimerUnsync=PSF5,Drx
InactivityTimerUnsync=PSF200,FddEnterDrxThd =1000,FddExitDrxThd = 1000;
Step 6 Run the MOD CELLALGOSWITCH command to enable dynamic DRX:

Step 7 Run the MOD RRCCONNSTATETIMER command to set

QCIPARA.UeInactiveTimerForQci and QCIPARA.UlSynTimerForQci to ensure the power
saving effect for UEs that do not support DRX:
MOD QCIPARA:Qci=9,UeInactiveTimerForQci=20,UlSynTimerForQci=180;
Step 8 (Optional) If UEs with compatibility issues exist in the network, you are advised to run the
MOD CELLACCESS command to set the CellAccess.ReptSyncAvoidInd and
CellAccess.ReptSyncAvoidTime parameters. The purpose is to reduce RRC connection
reconfiguration signaling. For details about how to determine whether UEs have compatibility
issues, see 6.2.5.1 Performance Monitoring.
----End
MOD CELLACCESS:LocalCellId=0,ReptSyncAvoidInd=CFG, ReptSyncAvoidTime=100;
MML Command Examples (QCI-based)

Scenario 1: Setting Parameters for Power Saving Mode
MOD QCIPARA:Qci=9,UeInactivityTimerDynDrxQci=35;
MOD CELLDRXPARA:LocalCellID=0,LongDrxCycleUnsync=SF1280,

eRAN
OndurationTimerUnsync=PSF5, DrxInactivityTimerUnsync=PSF200,FddEnterDrxThd=1000,
FddExitDrxThd=1000;
Scenario 2: Setting Parameters for Reduced Signaling Mode

MOD
QCIPARA:Qci=9,UeInactiveTimerForQci=200,UlSynTimerForQci=20,UeInactivityTimerDynDr
xQci=200;
MOD CELLDRXPARA:LocalCellID=0,LongDrxCycleUnsync=SF1280,
OndurationTimerUnsync=PSF5,DrxInactivityTimerUnsync=PSF200, FddEnterDrxThd=1000,
FddExitDrxThd=1000;
MOD QCIPARA:Qci=9,UeInactiveTimerForQci=20,UlSynTimerForQci=180;

To check whether dynamic DRX has been activated, use one of the following methods.
l If the number of dynamic DRX reconfiguration messages

(L.Signal.Num.DRX.Reconfig - L.Cdrx.Enter.Num - L.Cdrx.Exit.Num) is greater
than 0, dynamic DRX has been activated.
l If the value of L.Traffic.User.Unsyn.Drx.Avg is greater than 0, dynamic DRX has been
activated.
N/A

CellAlgoSwitch Dynamic DRX Set this parameter to

switch DynDrxSwitch-0.


Run the MOD CELLALGOSWITCH command to deactivate dynamic DRX.
6.2.5 Maintenance

eRAN

After dynamic DRX is enabled, monitor the power saving or signaling reduction effect.
l Monitoring the power saving effect
You can monitor the power saving effect in either of the following ways:
– Use special tools to monitor it directly.
– Use counters to monitor it indirectly.
If the difference between the UE inactivity timer (defined by
RrcConnStateTimer.UeInactivityTimerDynDrx,
QCIPARA.UeInactivityTimerDynDrxQci) and
RrcConnStateTimer.UlSynTimerDynDrx is large, use the L.Cdrx.Active.TtiNum
and L.Cdrx.Sleep.TtiNum counters and consider the power saving effect to
determine the power saving effect..
For example, when the DRX cycle is 40 ms, the UE does not turn off its receiver;
when the DRX cycle is 1280 ms, the UE turns off its receiver in certain conditions.
The L.Cdrx.Sleep.TtiNum counter indicates that less than 7% power is saved but
actually more than 20% power is saved after the DRX cycle increases from 40 ms
to 1280 ms, provided that the traffic model remains unchanged.
l Monitoring the signaling reduction effect
NOTE
If the value of RrcConnStateTimer.UlSynTimerDynDrx after dynamic DRX is enabled is less

than the value of RrcConnStateTimer.UlSynTimer before dynamic DRX is enabled, the
signaling reduction effect decreases.
You can use counters to monitor the signaling reduction effect in various scenarios:
– Use the following counters to monitor changes in the numbers of RRC connection
setup attempts in different scenarios so as to indirectly monitor changes in signaling
overhead:
L.RRC.ConnReq.Att; L.RRC.ConnReq.Att.Emc
L.RRC.ConnReq.Att.HighPri
L.RRC.ConnReq.Att.Mt
L.RRC.ConnReq.Att.MoSig
L.RRC.ConnReq.Att.MoData
L.RRC.ConnReq.Att.DelayTol
– Use the L.Paging.UU.Att counter to monitor changes in the number of UEs paged
on the Uu interface so as to indirectly monitor changes in signaling overhead.
– Use the L.Signal.Num.Uu counter to directly monitor changes in signaling
overhead on the Uu interface.
– Use the following counters to monitor the total change in signaling overhead on the
S1 and Uu interfaces:
L.E-RAB.AttEst;
L.Signal.Num.DRX.Reconfig;
L.RRC.StateTrans.Syn2Unsyn.
Then, use the following formula to calculate the total change:
L.E-RAB.AttEst + (L.Signal.Num.DRX.Reconfig +
L.RRC.StateTrans.Syn2Unsyn) / 10

eRAN
NOTE
Signaling overhead for 10 RRC connection reconfigurations is equivalent to that for one E-RAB
establishment.
In reduced signaling mode, some UEs are considered to have compatibility issues if one of the
following conditions is met:
l The L.Signal.Num.DRX.Reconfig counter value increases sharply.
l The Uu interface trace result shows that two or more consecutive RRC connection
reconfigurations are performed each time a UE switches from the out-of-synchronization
state to the synchronization state. Each RRC connection reconfiguration involves RRC
Connection Reconfiguration and RRC Connection Reconfiguration Complete messages.
Under these conditions, multiple RRC connection reconfigurations are performed each time
the UE switches from the out-of-synchronization state to the synchronization state. To avoid
an increase in abnormal signaling overhead caused by such a UE, you are advised to perform
the following operations:
1. Set the CellAccess.ReptSyncAvoidInd parameter to CFG(Configure) to prohibit
multiple successful synchronization procedures repeatedly initiated by such a UE from
triggering multiple RRC connection reconfigurations.
2. Set the CellAccess.ReptSyncAvoidTime parameter to specify the period during which
multiple successful synchronization procedures repeatedly initiated by such a UE trigger
only one RRC connection reconfiguration.
Documentation.

This section describes the parameters that can be modified to improve dynamic DRX
performance.
The following table describes the UE control timer parameters that can be modified in the
RrcConnStateTimer MO to adjust the balance between power saving and reduced signaling.

eRAN
Paramete Parameter Data Setting Notes

r Name ID Source
UE RrcConnSt Network This parameter specifies the length of the UE

Inactivity ateTimer. plan inactivity timer when dynamic DRX is
Timer UeInactivit (negotiation enabled. During the timer length, the eNodeB
Dynamic yTimerDyn not required) monitors whether the UE receives and
DRX Drx transmits data. If the UE does not receive or
transmit data before the timer expires, the
eNodeB releases the UE. If this parameter is
set too large, the signaling amount decreases
but UEs consume more power.
l If UE power saving is required, you are
advised to keep this parameter unchanged.
l If signaling reduction is required, you are
advised to adjust this parameter to a larger
value.
UE RrcConnSt Network This parameter specifies the length of the UE

Inactive ateTimer.U plan inactivity timer for UEs that have entered DRX
Timer for eInactTime (negotiation mode and have QCI 1 bearers. If the eNodeB
QCI1 rDynDrxQ not required) detects that a UE has entered DRX mode and
Dynamic ci1 has QCI 1 bearers but has neither received nor
DRX sent data for a period exceeding the value of
this parameter, the eNodeB releases the RRC
connection for this UE.
If the parameter setting is changed, the change
applies to UEs that newly access the network.
Uplink RrcConnSt Network This parameter specifies the length of the

Sync ateTimer. plan uplink synchronization timer when the
Timer UlSynTime (negotiation dynamic DRX is enabled. This timer and the
Dynamic rDynDRX not required) protection mechanism determine whether to
DRX maintain uplink synchronization for a UE.
After this timer expires and the protection
period elapses, the eNodeB no longer sends the
TA command to the UE. It is recommended
that the value of this parameter be less than the
value of the RrcConnStateTim-
er.UeInactivityTimerDynDrx parameter.
The following table describes the cell-level DRX parameters that can be modified in the
CellDrxPara MO to improve DRX performance in the out-of-synchronization state.

eRAN
Paramete Parameter Data Setting Notes

r Name ID Source
UnSync CellDrxPar Network This parameter specifies the long DRX cycle
Long a.LongDrx plan for a UE in the out-of-synchronization state
DRX CycleUnsyn (negotiation when the eNodeB does not maintain
Cycle c not required) synchronization for the UE.
Onduratio CellDrxPar Network This parameter specifies the length of the On

n Timer a.Ondurati plan Duration Timer for a UE in the out-of-
Unsync onTimerUn (negotiation synchronization state when the eNodeB does
sync not required) not maintain synchronization for the UE.
DRX CellDrxPar Network This parameter specifies the length of the

Inactivity a.DrxInacti plan DRX Inactivity Timer for a UE in the out-of-
Timer vityTimerU (negotiation synchronization state when the eNodeB does
Unsync nsync not required) not maintain synchronization for the UE.
Fault Description
Dynamic DRX is never triggered after the network is put into use.
Troubleshooting
Step 1 Run the LST CELLALGOSWITCH command to query the Dynamic DRX switch setting
l If the Dynamic DRX switch value is DynDrxSwitch:Off, run the MOD
CELLALGOSWITCH command to set it to DynDrxSwitch:On.
l If the Dynamic DRX switch value is DynDrxSwitch:On, go to Step 2.
Step 2 Run the LST CELLQCIPARA command to query the DRX parameter group IDs
corresponding to the service QCIs of the UE.
Step 3 Run the LST DRXPARAGROUP command to check the Enter DRX Switch settings for the
DRX parameter groups.
l If any Enter DRX Switch value is Off, run the MOD DRXPARAGROUP command to
turn on the corresponding DRX switch or stop the ongoing service on the corresponding
bearer.
l If all the Enter DRX Switch values are On, contact Huawei technical support.
----End
6.3 Engineering Guidelines for LOFD-00110502 High-

Mobility-Triggered Idle Mode
This section provides guidelines for configuring LOFD-00110502 High-Mobility-Triggered
Idle Mode.

eRAN
6.3.1 When to Use

When dynamic DRX is enabled or the UE inactivity timer is set to a large value, the number
of handovers of UEs moving at high speeds increases significantly as does the amount of
signaling. In this situation, it is recommended that LOFD-00110502 High-Mobility-Triggered
Idle Mode be enabled to prevent signaling bursts caused by frequent handovers.

You must obtain the following information:
l EARFCNs, coverage, and configurations of E-UTRAN cells

l eNodeB's capability to support LOFD-00110502 High-Mobility-Triggered Idle Mode
l Handover frequency and online duration of existing UEs, which help determine whether
this feature needs to be deployed
6.3.3 Planning
RF Planning
On live networks with no coverage problems, the high-mobility-triggered idle mode feature
prevents signaling bursts by reducing the handover frequency for high-mobility UEs.
Therefore, the networks must meet the following coverage requirements:
l No coverage holes.
l No overshoot coverage.
l No pilot pollution.
l No path loss imbalance between uplink and downlink.
Network Planning
N/A
Hardware Planning
N/A
6.3.4 Deployment
N/A
N/A

eRAN
License
The operator has purchased and activated the license for the feature listed in Table 6-4.
Table 6-4 License information

Feature Feature Model License Control NE Sales
ID Name Item Unit
LOFD-001 Dynamic LT1S00DDR Dynamic eNodeB per cell

105 DRX X00 DRX(FDD)
To enable LOFD-00110502 High-Mobility-Triggered Idle Mode after purchasing and

activating the license, set the CellAlgoSwitch.HighMobiTrigIdleModeSwitch parameter to
ENABLE(Enable).
Related Features
You are advised to enable LOFD-00110501 Dynamic DRX before enabling LOFD-00110502
High-Mobility-Triggered Idle Mode.
6.3.4.2 Precautions
None

N/A
6.3.4.4 Activation
Required Data
The following table describes the parameters that must be set in the CellAlgoSwitch MO to
configure the high-mobility-triggered idle mode feature.
Parameter Name Parameter ID Setting Notes
Local cell ID CellAlgoSwitch.LocalCellID None
High Mobility Triggered Idle CellAlgoSwitch.HighMobiTrigIdl None

Mode Switch eModeSwitch


eRAN

Run the MOD CELLALGOSWITCH command with the High Mobility Triggered Idle
Mode Switch parameter set to ENABLE(Enable) to enable the high-mobility-triggered idle
mode feature.
MOD CELLALGOSWITCH: LocalCellId=0, HighMobiTrigIdleModeSwitch=ENABLE;

If the L.UECNTX.Release.HighSpeed counter value is greater than 0, the high-mobility-
triggered idle mode feature has been enabled and taken effect.
N/A

CellAlgoSwitch High Mobility Triggered Idle Set this parameter to DISABLE.

Mode Switch


Run the MOD CELLALGOSWITCH command to deactivate the high-mobility-triggered
idle mode feature.
MOD CELLALGOSWITCH: LocalCellId=0, HighMobiTrigIdleModeSwitch=DISABLE;
6.3.5 Maintenance

After this feature is enabled, use counters to monitor performance:
l If the L.UECNTX.Release.HighSpeed counter value is greater than 0, this feature has
taken effect.
l If the number of handovers (measured by the following counters) after this feature is
enabled is much smaller than that before this feature is enabled, this feature has taken
effect.

eRAN
Table 6-6 Counters for performance monitoring

Counter ID Counter Name Description
1526726996 L.HHO.IntraeNB.IntraFreq Number of intra-eNodeB intra-

.ExecAttOut frequency outgoing handover
executions in a cell
1526726999 L.HHO.IntraeNB.InterFreq Number of intra-eNodeB inter-

1526727002 L.HHO.IntereNB.IntraFreq Number of inter-eNodeB intra-

1526727005 L.HHO.IntereNB.InterFreq Number of inter-eNodeB inter-

Documentation.

N/A
Fault Description
The high-mobility-triggered idle mode feature has never been triggered after the network is
put into use.
Fault Handling
Run the LST CELLALGOSWITCH command to query the High Mobility Triggered Idle
Mode Switch parameter value.
l If the High Mobility Triggered Idle Mode Switch parameter value is Disable, run the
MOD CELLALGOSWITCH command to set it to ENABLE(Enable).
l If the High Mobility Triggered Idle Mode Switch parameter value is Enable, contact
Huawei technical support.

eRAN
DRX and Signaling Control Feature Parameter Description 7 Parameters
7 Parameters
Table 7-1 Parameters

MO Parame MML Feature Feature Description
ter ID Comma ID Name
nd
Drx DrxAlg MOD LBFD-0 DRX Meaning: Indicates whether to enable DRX. This
Switch DRX 02017 / RRC parameter does not control dynamic DRX, and
LST TDLBF and dynamic DRX applies only to LTE networks. DRX
DRX D-00201 DRX takes effect on a CA UE only when this parameter is
7 Policy set to ON(On) on both eNodeBs serving the PCell and
TDLOF for SCells of the CA UE. This parameter applies only to
D-12110 Public LTE FDD and LTE TDD.
5 Safety GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
CellDrx DrxAlg MOD LBFD-0 DRX Meaning: Indicates whether to enable DRX. This
Para Switch CELLD 02017 / Breathin parameter does not control dynamic DRX, and
RXPAR TDLBF g Pilot dynamic DRX applies only to LTE networks. DRX is
A D-00201 allowed to use for a CA UE only if this parameter is
LST 7/ set to ON on the eNodeBs serving the PCell and
CELLD MLBFD SCells of the CA UE. For LTE FDD and LTE TDD
RXPAR -120002 cells, the DrxAlgSwitch parameter in the CellDrxPara
A 36 MO takes effect only if the DrxAlgSwitch parameter
LEOFD- in the Drx MO is set to OFF. For NB-IoT cells, DRX
111306 / is allowed to use only when the DrxAlgSwitch
TDLOF parameter in the CellDrxPara MO is set to ON.
D-12020 GUI Value Range: OFF(Off), ON(On)
5 Unit: None

eRAN

nd
CellCqi SimulAc MOD None None Meaning:

Adaptiv kNackA CELLC Indicates whether CQI and ACK/NACK can be
eCfg ndCqiS QIADA simultaneously sent on the PUCCH. For details, see
witch PTIVEC the contents related to PUCCH formats in 3GPP TS
FG 36.213.
LST
CELLC The value of simultaneousAckNackAndCQI is set to
QIADA False if this parameter is set to OFF.
PTIVEC If this parameter is set to ON, the value of
FG simultaneousAckNackAndCQI depends on the DRX
status of a UE, the setting of DrxSimulAckNack-
AndCqiSwitch of the EmimoSwitch parameter, and
the setting of cqi-Mask.
1) The UE is not in the DRX state.
- If the UE is not in the CA state, the value of
simultaneousAckNackAndCQI is set to True.
- If the UE is in the CA state, the value of
simultaneousAckNackAndCQI for the UE depends on
the setting of CaCqiAndAckAbnCtrlSwitch of the
CompatibilityCtrlSwitch parameter for the eNodeB.
2) The UE is in the DRX state.
i) cqi-Mask is set to ON.
ii) cqi-Mask is set to OFF.
1. DrxSimulAckNackAndCqiSwitch is selected and
the number of configured transmit antennas of the cell
is greater than two.

eRAN

nd
2. The value of simultaneousAckNackAndCQI is set

to False if DrxSimulAckNackAndCqiSwitch is
deselected.
If the value of simultaneousAckNackAndCQI is set to
True, CQI and ACK/NACK can be simultaneously
sent on the PUCCH. If the value of simultaneousAck-
NackAndCQI is set to False, CQI and ACK/NACK
cannot be simultaneously sent on the PUCCH.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Default Value: ON(On)
CellDrx CqiMas MOD LBFD-0 DRX Meaning: Indicates whether the cqi-Mask IE can be
Para k CELLD 02017 / set. The cqi-Mask IE is an optional IE introduced in
RXPAR TDLBF 3GPP Release 9. If the cqi-Mask IE is set to Setup, the
A D-00201 UE can send CQI/PMI/RI/PTI reports on PUCCH
LST 7 only in the onDuration period of discontinuous
CELLD reception (DRX). If the cqi-Mask IE is not set, the UE
RXPAR can send CQI/PMI/RI/PTI reports on PUCCH in the
A active period of DRX. This parameter applies only to
LTE FDD and LTE TDD.
Unit: None

eRAN

nd
CellAlg EmimoS MOD LEOFD- Virtual Meaning:

oSwitch witch CELLA 111305 4T4R Indicates whether to enable eMIMO-related
LGOSW LEOFD- eMIMO algorithms.
ITCH 111307
LST Virtual4T4RSwitch: Indicates whether to enable the
CELLA virtual 4T4R function. This option applies only to
LGOSW FDD. The function is enabled only if this option is
ITCH selected.
EmimoMuMimoSwitch: Indicates whether to enable
the eMIMO MU-MIMO function. This option applies
only to FDD. The function is enabled only if this
option is selected.
EmimoCpsSwitch: Indicates whether to enable
coordinated pilot scheduling for eMIMO. This option
applies only to FDD. The function is enabled only if
this option is selected. When this option is selected,
the eNodeB determines the pilot transmission mode
based on inter-cell load status.
EmimoFbaSwitch: Indicates whether to enable the
following functions:
- Fast beam alignment for eMIMO
- Extending UE rank reporting period in non-high-
speed-railway scenarios when the CQI reporting
period is adaptively changed to 40 ms.
The preceding two functions are enabled only if this
option is selected. This parameter applies only to LTE
FDD.
New4TCodebookSwitch: Indicates whether to use the
new 4T codebook. The new 4T codebook can be used
for UEs that support the new 4T codebook only if this
option is selected. This option applies only to LTE
FDD.
4TxTM9MuMimoSwitch: Indicates whether to enable
the 4TX TM9 MU-MIMO function. This option
applies only to FDD. The function is enabled only if
this option is selected.
DrxSimulAckNackAndCqiSwitch: Indicates whether
to allow UEs in DRX mode to send CQI and ACK/
NACK simultaneously on the PUCCH when
SimulAckNackAndCqiSwitch is set to ON and
CqiMask is set to OFF. This option takes effect when
the number of configured downlink transmit antennas
of the cell is greater than two. If this option is

eRAN

nd
selected, UEs in DRX mode can send CQI and ACK/

NACK simultaneously on the PUCCH when
SimulAckNackAndCqiSwitch is set to ON and
CqiMask is set to OFF. If this option is deselected, the
settings of the SimulAckNackAndCqiSwitch and
CqiMask parameters determine whether to allow UEs
in DRX mode to send CQI and ACK/NACK
simultaneously on the PUCCH.
GUI Value Range:
Virtual4T4RSwitch(Virtual4T4RSwitch),
EmimoMuMimoSwitch(EmimoMuMimoSwitch),
EmimoCpsSwitch(EmimoCpsSwitch),
EmimoFbaSwitch(EmimoFbaSwitch),
New4TCodebookSwitch(New4TCodebookSwitch),
4TxTM9MuMimoSwitch(4TxTM9MuMimoSwitch),
DrxSimulAckNackAndCqiS-
witch(DrxSimulAckNackAndCqiSwitch)
Unit: None
Actual Value Range: Virtual4T4RSwitch,
EmimoMuMimoSwitch, EmimoCpsSwitch,
EmimoFbaSwitch, New4TCodebookSwitch,
4TxTM9MuMimoSwitch, DrxSimulAckNackAndC-
qiSwitch
Default Value: Virtual4T4RSwitch:Off,
EmimoMuMimoSwitch:Off, EmimoCpsSwitch:Off,
EmimoFbaSwitch:Off, New4TCodebookSwitch:Off,
4TxTM9MuMimoSwitch:Off, DrxSimulAckNack-
AndCqiSwitch:Off

eRAN

nd
ENodeB Compati MOD LBFD-0 Coverag Meaning:

AlgoSwi bilityCtr ENODE 0201802 e Based Indicates whether to enable compatibility solutions,
tch lSwitch BALGO / Inter- based on which the eNodeB determines whether to
SWITC TDLBF frequenc handle compatibility issues. This parameter includes
H D-00201 y the following options:
LST 802 Handov
ENODE LBFD-0 er UECapRprtAbnormalCtrlSwitch: If this option is
BALGO 0201805 Service selected, the eNodeB handles compatibility issues of
SWITC / Based UEs that cannot report their capabilities. This option
H TDLBF Inter- applies only to LTE FDD and LTE TDD.
D-00201 frequenc ApCqiRptAbnormalCtrlSwitch: Indicates whether to
805 y apply a compatibility solution to abnormal aperiodic
LBFD-0 Handov channel quality indicator (CQI) reporting. If this
02031 / er option is selected, the compatibility solution takes
TDLBF Support effect. The configuration IEs related to aperiodic CQI
D-00203 of reporting are always included in RRC Connection
1 aperiodi Reconfiguration messages used to reconfigure CQIs
LOFD-0 c CQI regardless of whether the IEs are changed or not. If
01019 / reports this option is deselected, the compatibility solution
TDLOF PS Inter- does not take effect. The configuration IEs related to
D-00101 RAT aperiodic CQI reporting are not included in RRC
9 Mobility Connection Reconfiguration messages used to
between reconfigure CQIs if the IEs remain unchanged. This
LOFD-0 option applies only to LTE FDD and LTE TDD.
01020 / E-
TDLOF UTRAN UeInterRatMeasCtrlSwitch: Indicates whether the
D-00102 and eNodeB checks the QCI-specific inter-RAT handover
0 UTRAN policies when evaluating an inter-RAT handover. This
LAOFD PS Inter- function does not allow the eNodeB to deliver inter-
-001002 RAT RAT measurement configurations to some special UEs
01 / Mobility anymore and applies to the following types of inter-
TDLAO between RAT handovers: coverage-based handover, distance-
FD-001 E- based handover, uplink-quality-based handover,
002 UTRAN service-based handover, and SPID-specific handover
and back to the HPLMN. If this option is selected, the
LBFD-0 GERAN eNodeB determines whether to deliver inter-RAT
02008 / A1/A2, blind A1/A2, and inter-RAT B1/B2
TDLBF Carrier
Aggrega measurement configurations to the UE for a
D-00200 measurement-based or blind inter-RAT handover
8 tion for
Downlin based on the setting of the NoHoFlag parameters in
LOFD-0 k 2CC the InterRatPolicyCfgGroup MO for QCIs of services
01060 in running on the UE. If this option is deselected, the
TDLOF 40MHz eNodeB does not perform the evaluation based on the
D-00106 values of the NoHoFlag parameters in the
Radio InterRatPolicyCfgGroup MO.
0 Bearer
LOFD-0 Manage VoipExProtSwitch: Indicates whether to enable
01001 / ment service-request-based inter-frequency handover
TDLOF protection when a VoLTE exception occurs. If this

eRAN

nd
D-00100 DL 4x4 option is selected and the eNodeB does not support
1 MIMO VoLTE, the eNodeB can set up bearers for QCI-1
LOFD-0 DL 4x4 services and other services when both of the following
01003 MIMO conditions are met: (1) The EPC delivers information
Based about bearers with QCI 1 and other QCIs; (2) The UE
TDLAO exits the idle mode. After the QCI-1 service bearers
FD-001 on TM3
and are set up, the UE is handed over to an inter-frequency
00114 cell. This option applies only to LTE FDD and LTE
TM4
TDLAO TDD.
FD-081 DL 2*2
409 MIMO ApCqiAndAckAbnCtrlSwitch: Indicates whether to
DL 4*2 enable a workaround of problems that may occur
LAOFD when aperiodic CQI reports in 3-1 reporting mode and
-001001 MIMO
ACKs/NACKs are transmitted simultaneously in a
/ DL 2- cell. If this option is selected, the eNodeB performs
TDLAO Layer preallocation for aperiodic CQI reports. If this option
FD-001 MIMO is deselected, the eNodeB performs CQI_ONLY
001 Based scheduling on aperiodic CQI reports. This option
TDLAO on TM9 applies only to LTE FDD and LTE TDD.
FD-110 DL 4-
401 UeSRSAntSelectCtrlSwitch: Indicates whether to
Layer
disable antenna selection for SRS transmission. If this
TDLAO MIMO
option is selected, antenna selection is disabled. This
FD-081 Based
option applies only to LTE TDD.
402 on TM9
LTE-A CaCqiAndAckAbnCtrlSwitch: Indicates whether to
LBFD-0
Introduc enable a workaround of problems that may occur
60101
tion when periodic CQI reports and ACKs/NACKs are
MRFD- transmitted simultaneously in a cell in CA scenarios.
101222 Inter-
If this option is selected, the eNodeB sets the
eNodeB
MRFD- SimulAckNackAndCqiSwitch parameter to OFF(Off)
CA
111222 for CA UEs. If this option is deselected, the eNodeB
Based
sets the SimulAckNackAndCqiSwitch parameter
on
based on the original algorithm for CA UEs.
Coordin
ated HoRlcSnSizeSwitch: Controls the configuration of
BBU RLC sn-FieldLength during handovers. If this option
Inter- is selected, the configuration of RLC sn-FieldLength
eNodeB for the target cell is the same as that for the source
CA cell. If this option is deselected, RLC sn-FieldLength
Based for the target cell is set to the value configured at the
on target side.
Relaxed FddTddCaPcellDuplexFdd: Indicates whether the
Backhau eNodeB regards that a UE supports FDD+TDD CA
l with an LTE FDD cell serving as its PCell when the
Optimiz UE reports the FDD+TDD CA band combination but
ation of does not report IE tdd-FDD-CA-PCellDuplex-r12. If
Periodic this option is selected, the eNodeB regards that the UE
and supports this type of CA. If this option is deselected,
Aperiodi the eNodeB regards that the UE does not support this

eRAN

nd
c CQI type of CA. This option applies only to LTE FDD and
Reportin LTE TDD.
g
FddTddCaPcellDuplexTdd: Indicates whether the
FDD
eNodeB regards that a UE supports FDD+TDD CA
+TDD
with an LTE TDD cell serving as its PCell when the
Downlin
UE reports the FDD+TDD CA band combination but
k
does not report IE tdd-FDD-CA-PCellDuplex-r12. If
Carrier
this option is selected, the eNodeB regards that the UE
Aggrega
supports this type of CA. If this option is deselected,
tion(LT
the eNodeB regards that the UE does not support this
E FDD)
type of CA. This option applies only to LTE FDD and
FDD LTE TDD.
+TDD
Uplink Tm3Tm4Max4LayerCtrlSwitch: Indicates whether
Carrier UEs of category 6 and above (excluding category 5)
Aggrega support four-layer MIMO based on TM3/TM4. If this
tion option is selected, UEs of category 6 or above
(LTE (excluding category 5) support MIMO at a maximum
FDD) of four layers based on TM3/TM4. If this option is
deselected, UEs of category 6 or above (excluding
category 5) support MIMO at a maximum of two
layers based on TM3/TM4. This option applies only to
UeCsiRsCfigCtrlSwitch: Indicates whether to

configure CSI-RSs for TM9-incapable and TM10-
incapable UEs complying with 3GPP Release 10 or
later after the cell sends CSI-RSs. If this option is
selected, CSI-RSs are configured for such UEs. If this
option is deselected, CSI-RSs are not configured for
such UEs. This option applies only to LTE FDD and
LTE TDD.
GUI Value Range: UECapRprtAbnormalCtrlS-
witch(UECapRprtAbnormalCtrlSwitch),
ApCqiRptAbnormalCtrlS-
witch(ApCqiRptAbnormalCtrlSwitch),
UeInterRatMeasCtrlSwitch(UeInterRatMeasCtrlS-
witch), VoipExProtSwitch(VoipExProtSwitch),
UeSRSAntSelectCtrlSwitch(UeSRSAntSelectCtrlS-
witch), ApCqiAndAckAbnCtrlS-
witch(ApCqiAndAckAbnCtrlSwitch),
CaCqiAndAckAbnCtrlS-
witch(CaCqiAndAckAbnCtrlSwitch),
HoRlcSnSizeSwitch(HoRlcSnSizeSwitch),
FddTddCaPcellDuplexFdd(FddTddCaPcellDu-
plexFdd), FddTddCaPcellDu-
plexTdd(FddTddCaPcellDuplexTdd),
Tm3Tm4Max4LayerCtrlSwitch(Tm3Tm4Max4Layer

eRAN

nd
CtrlSwitch), UeCsiRsCfigCtrlS-
witch(UeCsiRsCfigCtrlSwitch)
Unit: None
Actual Value Range: UECapRprtAbnormalCtrlSwitch,
ApCqiRptAbnormalCtrlSwitch,
UeInterRatMeasCtrlSwitch, VoipExProtSwitch,
UeSRSAntSelectCtrlSwitch,
ApCqiAndAckAbnCtrlSwitch,
CaCqiAndAckAbnCtrlSwitch, HoRlcSnSizeSwitch,
FddTddCaPcellDuplexFdd, FddTddCaPcellDu-
plexTdd, Tm3Tm4Max4LayerCtrlSwitch,
UeCsiRsCfigCtrlSwitch
Default Value: UECapRprtAbnormalCtrlSwitch:Off,
ApCqiRptAbnormalCtrlSwitch:On,
UeInterRatMeasCtrlSwitch:Off,
VoipExProtSwitch:Off, UeSRSAntSelectCtrlS-
witch:Off, ApCqiAndAckAbnCtrlSwitch:Off,
CaCqiAndAckAbnCtrlSwitch:On,
HoRlcSnSizeSwitch:On, FddTddCaPcellDu-
plexFdd:On, FddTddCaPcellDuplexTdd:Off,
Tm3Tm4Max4LayerCtrlSwitch:Off,
UeCsiRsCfigCtrlSwitch:Off
CellQci DrxPara ADD LBFD-0 DRX Meaning: Indicates the ID of a DRX parameter group.
Para GroupId CELLQ 02017 / RRC This parameter takes effect only on standardized
CIPAR TDLBF and QCIs. This parameter applies only to LTE FDD and
A D-00201 DRX LTE TDD.
MOD 7 Policy GUI Value Range: 0~49
CELLQ TDLOF for Unit: None
CIPAR D-12110 Public
A 5 Safety Actual Value Range: 0~49
LST Default Value: 0

CELLQ
CIPAR
A

eRAN

nd
DrxPara EnterDr ADD LBFD-0 DRX Meaning: Indicates whether bearers to which the
Group xSwitch DRXPA 02017 / Breathin parameter group applies support DRX. The value ON
RAGRO TDLBF g Pilot indicates that the bearers support DRX. The value
UP D-00201 OFF indicates that the bearers do not support DRX.
7 RRC This parameter applies only to LTE FDD and LTE
MOD and
DRXPA LEOFD- TDD.
DRX
RAGRO 111306 / Policy GUI Value Range: OFF(Off), ON(On)
UP TDLOF for Unit: None
LST D-12020 Public
5 Actual Value Range: OFF, ON
DRXPA Safety
RAGRO TDLOF Default Value: OFF(Off)
UP D-12110
5
DrxPara OnDurat ADD LBFD-0 DRX Meaning: Indicates the length of the On Duration
Group ionTime DRXPA 02017 / Breathin Timer. If the configured value does not meet the
r RAGRO TDLBF g Pilot restrictions of CQI reporting intervals and SRS
UP D-00201 transmission intervals, the actual value of this
7 Dynami parameter assigned to a UE may be greater than the
MOD c DRX
DRXPA LEOFD- configured value. This parameter applies only to LTE
RAGRO 111306 RRC FDD and LTE TDD.
UP and GUI Value Range: PSF1(1 PDCCH subframes),
LOFD-0 DRX
LST 0110501 PSF2(2 PDCCH subframes), PSF3(3 PDCCH
Policy subframes), PSF4(4 PDCCH subframes), PSF5(5
DRXPA LTROF for
RAGRO PDCCH subframes), PSF6(6 PDCCH subframes),
D-11120 Public PSF8(8 PDCCH subframes), PSF10(10 PDCCH
UP 3/ Safety subframes), PSF20(20 PDCCH subframes), PSF30(30
TDLOF eMTC PDCCH subframes), PSF40(40 PDCCH subframes),
D-12110 Introduc PSF50(50 PDCCH subframes), PSF60(60 PDCCH
5 tion subframes), PSF80(80 PDCCH subframes),
MLOFD PSF100(100 PDCCH subframes), PSF200(200
-121280 PDCCH subframes), PSF300(300 PDCCH
/ subframes), PSF400(400 PDCCH subframes),
TDLEO PSF500(500 PDCCH subframes), PSF600(600
FD-121 PDCCH subframes), PSF800(800 PDCCH
611 subframes), PSF1000(1000 PDCCH subframes),
PSF1200(1200 PDCCH subframes), PSF1600(1600
PDCCH subframes)
Unit: subframe
Actual Value Range: PSF1, PSF2, PSF3, PSF4, PSF5,
PSF6, PSF8, PSF10, PSF20, PSF30, PSF40, PSF50,
PSF60, PSF80, PSF100, PSF200, PSF300, PSF400,
PSF500, PSF600, PSF800, PSF1000, PSF1200,
PSF1600
Default Value: PSF2(2 PDCCH subframes)

eRAN

nd
DrxPara DrxInact ADD LBFD-0 DRX Meaning: Indicates the length of the DRX inactivity
Group ivityTim DRXPA 02017 / Breathin timer. This parameter applies only to LTE FDD and
er RAGRO TDLBF g Pilot LTE TDD.
UP D-00201 GUI Value Range: PSF1(1 PDCCH subframe),
7 Dynami
MOD c DRX PSF2(2 PDCCH subframes), PSF3(3 PDCCH
DRXPA LEOFD- subframes), PSF4(4 PDCCH subframes), PSF5(5
RAGRO 111306 RRC PDCCH subframes), PSF6(6 PDCCH subframes),
UP and PSF8(8 PDCCH subframes), PSF10(10 PDCCH
LOFD-0 DRX
LST 0110501 subframes), PSF20(20 PDCCH subframes), PSF30(30
Policy PDCCH subframes), PSF40(40 PDCCH subframes),
DRXPA LTROF for
RAGRO PSF50(50 PDCCH subframes), PSF60(60 PDCCH
D-11120 Public subframes), PSF80(80 PDCCH subframes),
UP 3/ Safety PSF100(100 PDCCH subframes), PSF200(200
TDLOF eMTC PDCCH subframes), PSF300(300 PDCCH
D-12110 Introduc subframes), PSF500(500 PDCCH subframes),
5 tion PSF750(750 PDCCH subframes), PSF1280(1280
MLOFD PDCCH subframes), PSF1920(1920 PDCCH
-121280 subframes), PSF2560(2560 PDCCH subframes)
/ Unit: subframe
TDLEO
FD-121 Actual Value Range: PSF1, PSF2, PSF3, PSF4, PSF5,
611 PSF6, PSF8, PSF10, PSF20, PSF30, PSF40, PSF50,
PSF750, PSF1280, PSF1920, PSF2560
DrxPara DrxReT ADD LBFD-0 DRX Meaning: Indicates the length of the DRX
Group xTimer DRXPA 02017 / RRC Retransmission Timer. This parameter applies only to
RAGRO TDLBF and LTE FDD and LTE TDD.
UP D-00201 DRX GUI Value Range: PSF1(1 PDCCH subframes),
MOD 7 Policy PSF2(2 PDCCH subframes), PSF4(4 PDCCH
DRXPA LTROF for subframes), PSF6(6 PDCCH subframes), PSF8(8
RAGRO D-11120 Public PDCCH subframes), PSF16(16 PDCCH subframes),
UP 3/ Safety PSF24(24 PDCCH subframes), PSF33(33 PDCCH
LST TDLOF eMTC subframes), PSF40(40 PDCCH subframes), PSF64(64
DRXPA D-12110 Introduc PDCCH subframes), PSF80(80 PDCCH subframes),
RAGRO 5 tion PSF96(96 PDCCH subframes), PSF112(112 PDCCH
UP MLOFD subframes), PSF128(128 PDCCH subframes),
-121280 PSF160(160 PDCCH subframes), PSF320(320
/ PDCCH subframes)
TDLEO Unit: subframe
FD-121 Actual Value Range: PSF1, PSF2, PSF4, PSF6, PSF8,
611 PSF16, PSF24, PSF33, PSF40, PSF64, PSF80,
PSF96, PSF112, PSF128, PSF160, PSF320

eRAN

nd
DrxPara LongDr ADD LBFD-0 DRX Meaning:

Group xCycle DRXPA 02017 / Breathin Indicates the length of the long DRX cycle. Because
RAGRO TDLBF g Pilot of the impact of the SRS bandwidth and TA period
UP D-00201 specified by the TimeAlignmentTimer parameter, the
7 Dynami
MOD c DRX actual value of this parameter assigned to a UE may
DRXPA LEOFD- be less than the configured value. In addition, the
RAGRO 111306 RRC configured value will be rounded down to an integral
UP and multiple of 10. Therefore, you are advised to set this
LOFD-0 DRX
LST 0110501 parameter to a value that is an integral multiple of 10.
Policy
DRXPA LTROF for If users hope that the value actually assigned to a UE
RAGRO D-11120 Public is greater than or equal to 80 ms, set the
UP 3\ Safety TimeAlignmentTimer parameter to a value greater
TDLOF eMTC than or equal to 10240 ms. If the
D-12110 Introduc TimingAdvCmdOptSwitch parameter is set to ON, it
5 tion is recommended that the LongDrxCycle parameter be
MLOFD set to a value less than or equal to 320 ms. Otherwise,
-121280 the uplink time alignment performance of UEs is
\ affected. If the TimingAdvCmdOptSwitch parameter
TDLEO is set to ON, it is recommended that the
FD-121 TimeAlignmentTimer parameter be set to sf10240. A
611 smaller value of the TimeAlignmentTimer parameter
(for example, less than sf5120) increases the
probability that UEs in DRX mode are out of
synchronization in the uplink. The length of the long
DRX cycle must be shorter than the length of the
PDCP packet discarding timer for the corresponding
QCI. Otherwise, packet loss occurs during a ping
operation or low-traffic service. This parameter
applies only to LTE FDD and LTE TDD.
GUI Value Range: SF10(10 subframes), SF20(20
subframes), SF32(32 subframes), SF40(40
subframes)
Unit: subframe
Actual Value Range: SF10, SF20, SF32, SF40, SF64,
SF80, SF128, SF160, SF256, SF320, SF512, SF640,
SF1024, SF1280, SF2048, SF2560
Default Value: SF40(40 subframes)

eRAN

nd
DrxPara ShortDr ADD LBFD-0 DRX Meaning: Indicates the length of the short DRX cycle.
Group xCycle DRXPA 02017 / RRC According to 3GPP specifications, the length of a long
RAGRO TDLBF and DRX cycle must be an integer multiple of that of a
UP D-00201 DRX short DRX cycle. In addition, the actual value of
MOD 7 Policy LongDrxCycle assigned to a UE may be less than the
DRXPA TDLOF for configured value because of the restrictions of the
RAGRO D-12110 Public SRS bandwidth and TA period specified by the
UP 5 Safety TimeAlignmentTimer parameter. Therefore, the actual
value of ShortDrxCycle assigned to a UE may be less
LST than the configured value. This parameter applies only
DRXPA to LTE FDD and LTE TDD.
RAGRO
UP GUI Value Range: SF2(2 subframes), SF5(5
subframes), SF8(8 subframes), SF10(10 subframes),
SF16(16 subframes), SF20(20 subframes), SF32(32
subframes), SF640(640 subframes)
Unit: subframe
SF20, SF32, SF40, SF64, SF80, SF128, SF160,
SF256, SF320, SF512, SF640
DrxPara DrxShor ADD LBFD-0 DRX Meaning: Indicates the length of the DRX Short Cycle
Group tCycleTi DRXPA 02017 / RRC Timer. If this parameter is set to 1, the length of this
mer RAGRO TDLBF and timer is one short DRX cycle. If this parameter is set
UP D-00201 DRX to 2, the length of this timer is two short DRX cycles.
MOD 7 Policy If this parameter is set to a large value, a UE for which
DRXPA TDLOF for short DRX cycles are enabled stays in short-cycle
RAGRO D-12110 Public DRX for a long time. For details, see section 5.7 in
UP 5 Safety 3GPP TS 36.321. This parameter applies only to LTE
FDD and LTE TDD.
LST
DRXPA GUI Value Range: 1~16
RAGRO Unit: None
UP Actual Value Range: 1~16
Default Value: 1

eRAN

nd
DrxPara Support ADD LBFD-0 DRX Meaning: Indicates whether short DRX cycles are
Group ShortDr DRXPA 02017 / Breathin enabled. This parameter applies only to LTE FDD and
x RAGRO TDLBF g Pilot LTE TDD.
UP D-00201 GUI Value Range: UU_DISABLE(Disable),
7 RRC
MOD and UU_ENABLE(Enable)
DRXPA LEOFD- DRX Unit: None
RAGRO 111306 Policy
UP Actual Value Range: UU_DISABLE, UU_ENABLE
LTROF for
LST D-11120 Public Default Value: UU_ENABLE(Enable)
DRXPA 3/ Safety
RAGRO TDLOF
UP D-12110
5
CellDrx DrxPoli MOD LBFD-0 DRX Meaning:

Para cyMode CELLD 02017 / RRC Indicates the policy for selecting a DRX parameter
RXPAR TDLBF and group for a UE whose bearers have different QCIs.
A D-00201 DRX
LST 7 Policy If this parameter is set to DEFAULT, the eNodeB
CELLD TDLOF for selects the group with the shortest long DRX cycle
RXPAR D-12110 Public and, if an identical long DRX cycle length is mapped
A 5 Safety to multiple QCIs, selects the group mapped to the
highest-ARP QCI. (The ARP settings are delivered
from the EPC.)
If this parameter is set to QCIPRIORITY, the eNodeB
selects the group mapped to the highest-priority QCI
and, if no DRX parameter group is mapped to the
highest-priority QCI, does not configure DRX
parameters for the UE.
If this parameter is set to 3GPPDEFINEDQCIPRIOR-
ITY, the eNodeB selects the group with the shortest
long DRX cycle and, if an identical long DRX cycle
length is mapped to multiple QCIs, selects the group
mapped to the QCI with the highest 3GPP-defined
priority. This parameter applies only to LTE FDD and
LTE TDD.
GUI Value Range: DEFAULT(Default),
QCIPRIORITY(QCI priority),
3GPPDEFINEDQCIPRIORITY(3GPP Defined Qci
priority)
Unit: None
Actual Value Range: DEFAULT, QCIPRIORITY,
3GPPDEFINEDQCIPRIORITY
Default Value: 3GPPDEFINEDQCIPRIORITY(3GPP
Defined Qci priority)

eRAN

nd
QciPara Service ADD LBFD-0 Dynami Meaning: Indicates the service type corresponding to
Type QCIPA 0101502 c the operator-defined QCI. This extended QCI inherits
RA / Scheduli configurations from the corresponding standardized
MOD TDLBF ng QCI. If this parameter is set to IMSSignalling,
QCIPA D-00101 configurations of QCI 5 are inherited. If this
RA 502 parameter is set to LowDelay, configurations of QCI 7
are inherited. If this parameter is set to
LST TCPorBuffStreaming, configurations of QCI 9 are
QCIPA inherited. This parameter applies only to LTE FDD
RA and LTE TDD.
GUI Value Range: IMSSignalling(IMS Signalling),
LowDelay(Low Delay), TCPorBuffStreaming(TCP
Based or Buffered Streaming), CBTC(CBTC)
Unit: None
Actual Value Range: IMSSignalling, LowDelay,
TCPorBuffStreaming, CBTC
Default Value: TCPorBuffStreaming(TCP Based or
Buffered Streaming)
CellDrx FddEnte MOD LBFD-0 DRX Meaning: Indicates the threshold for UEs to enter the
Para rDrxThd CELLD 02017 / discontinuous reception (DRX) mode in a cell that
RXPAR TDLBF operates in FDD mode. This threshold is used in the
A D-00201 DRX algorithm. It is expressed as a proportion of the
LST 7 transmission time intervals (TTIs) with data
CELLD transmission to the total TTIs. If the measurement
RXPAR result of UE traffic is equal to or lower than this
A threshold, the eNodeB determines that the UE should
remain in DRX mode or the UE should be triggered to
enter DRX mode. If both the values of the
FddExitDrxThd and FddEnterDrxThd parameters are
small and close to each other, the UE frequently enters
and exits the DRX mode. When both the
FddEnterDrxThd parameter and the FddExitDrxThd
parameter are set to 1000 and DRX is enabled, the
eNodeB directly determines that the UE should enter
or exit the DRX mode, but not according to the
measurement result of UE traffic. This parameter
applies only to LTE FDD.
GUI Value Range: 0~1000
Unit: per mill
Actual Value Range: 0~1000
Default Value: 1000

eRAN

nd
CellDrx DataAm MOD LBFD-0 DRX Meaning: Indicates the length of the UE traffic
Para ountStat CELLD 02017 / measurement period. The traffic volume of a UE
Timer RXPAR TDLBF during this period is measured. Based on the
A D-00201 measurement result, the DRX algorithm decides
LST 7 whether the UE should enter or exit DRX. This
CELLD parameter applies only to LTE FDD and LTE TDD.
RXPAR GUI Value Range: 2~300
A Unit: 20ms
Default Value: 30
CellDrx FddExit MOD LBFD-0 DRX Meaning: Indicates the threshold for UEs to exit the
Para DrxThd CELLD 02017 / discontinuous reception (DRX) mode in a cell that
RXPAR TDLBF operates in FDD mode. This threshold is used in the
A D-00201 DRX algorithm. It is expressed as a proportion of the
LST 7 transmission time intervals (TTIs) with data
CELLD transmission to the total TTIs. If the measurement
RXPAR result of UE traffic is higher than this threshold, the
A eNodeB determines that the UE should remain in the
non-DRX mode or the UE should be triggered to exit
the DRX mode. If the value of the FddExitDrxThd
parameter is set to 1000 and the value of the
FddEnterDrxThd parameter is set to a value smaller
than 1000, the UE will not exit the DRX mode once
entering the DRX mode. If both the values of the
FddExitDrxThd and FddEnterDrxThd parameters are
small and close to each other, the UE frequently enters
and exits the DRX mode. When both the
FddEnterDrxThd parameter and the FddExitDrxThd
parameter are set to 1000 and DRX is enabled, the
eNodeB directly determines that the UE should enter
or exit the DRX mode, but not according to the
measurement result of UE traffic. This parameter
Unit: per mill
Default Value: 1000

eRAN

nd
CellDrx GapDrx MOD LBFD-0 DRX Meaning: Indicates whether the eNodeB delivers the
Para Exclusiv CELLD 02017 / gap-assisted measurement configuration and DRX
eSwitch RXPAR TDLBF configuration to a UE at the same time. If this
A D-00201 parameter is set to ON(On), the eNodeB instructs the
LST 7 UE to perform gap-assisted measurements and at the
CELLD same time removes the DRX configuration that has
RXPAR been delivered to the UE. If this parameter is set to
A OFF(Off), the eNodeB can deliver both configurations
to the UE. If the DrxForMeasSwitch parameter is set
to ON(On), the GapDrxExclusiveSwitch parameter
does not take effect. If the GapDrxExclusiveSwitch
parameter is set to ON(On), the VolteGapDrxExclusi-
veSwitch parameter does not take effect. This
parameter applies only to LTE FDD and LTE TDD.
Unit: None
CellDrx VolteGa MOD LBFD-0 DRX Meaning: Indicates whether the eNodeB delivers the
Para pDrxEx CELLD 02017 / intra-RAT gap-assisted measurement configuration
clusiveS RXPAR TDLBF and DRX configuration to a UE performing a voice
witch A D-00201 service at the same time. If this parameter is set to
LST 7 ON(On), the eNodeB instructs the UE to perform
CELLD intra-RAT gap-assisted measurements and at the same
RXPAR time removes the DRX configuration that has been
A delivered to the UE . If this parameter is set to
OFF(Off), the eNodeB can deliver both configurations
to the UE. If the DrxForMeasSwitch parameter is set
to ON(On), the VolteGapDrxExclusiveSwitch
parameter does not take effect. This parameter applies
only to LTE FDD and LTE TDD.
Unit: None

eRAN

nd
CellDrx ShortDr MOD LBFD-0 DRX Meaning: Indicates whether to enable or disable short
Para xCycleS CELLD 02017 / DRX cycles. Short DRX cycles reduce the traffic
witch RXPAR TDLBF delay. If the ShortDrxSwitch parameter in the Drx MO
A D-00201 is set to OFF, the ShortDrxCycleSwitch parameter in
LST 7 the CellDrxPara MO does not take effect. If the
CELLD ShortDrxSwitch parameter in the Drx MO is set to
RXPAR ON, the ShortDrxCycleSwitch parameter in the
A CellDrxPara MO takes effect. This parameter applies
Unit: None
CellDrx CovGsm MOD TDLOF SRVCC Meaning: Indicates whether to deliver measurement-
Para MeasDr CELLD D-00102 to dedicated DRX parameters to a UE when GERAN
xCfgSwi RXPAR 3/ GERAN measurements are triggered for a coverage-based
tch A LOFD-0 PS Inter- handover of the UE. If this parameter is set to ON, the
LST 01023 RAT eNodeB delivers both DRX parameters and gap-
CELLD TDLOF Mobility assisted GERAN measurement configurations to the
RXPAR D-00102 between UE. If this parameter is set to OFF, the eNodeB
A 0/ E- delivers only gap-assisted GERAN measurement
LOFD-0 UTRAN configurations to the UE. This parameter applies only
01020 and to LTE FDD and LTE TDD.
LBFD-0 GERAN GUI Value Range: OFF(Off), ON(On)
02017 / DRX Unit: None
TDLBF
D-00201
7 Default Value: OFF(Off)
CellDrx DrxFor MOD LOFD-0 Ultra- Meaning: Indicates whether to deliver measurement-
Para MeasSw CELLD 81283 / Flash dedicated DRX parameters to a UE when GERAN
itch RXPAR TDLOF CS measurements are triggered for CSFB of the UE. If
A D-08120 Fallback this parameter is set to ON, the eNodeB delivers both
LST 3 to DRX parameters and gap-assisted GERAN
CELLD LBFD-0 GERAN measurement configurations to the UE. If this
RXPAR 02017 / DRX parameter is set to OFF, the eNodeB delivers only
A TDLBF gap-assisted GERAN measurement configurations to
D-00201 the UE. This parameter applies only to LTE FDD and
7 LTE TDD.
Unit: None

eRAN

nd
CellDrx MeasDr MOD LOFD-0 SRVCC Meaning: Indicates whether to enable special
Para xSpecSc CELLD 01023 / to scheduling for UEs to which the eNodeB has
hSwitch RXPAR TDLOF GERAN delivered measurement-dedicated DRX parameters. If
A D-00102 CS this parameter is set to ON, special scheduling is
LST 3 Fallback enabled so that the sleep time, during which GERAN
CELLD LOFD-0 to measurements can be performed, is maximized for
RXPAR 01034 / GERAN UEs that are running services. As a result, the
A TDLOF measurement reporting delay is shortened for such
Flash UEs. If this parameter is set to OFF, special
D-00103 CS
4 scheduling is disabled. For UEs with ongoing
Fallback services, the sleep time is so short that measurement
LOFD-0 to reporting is delayed. This parameter applies only to
01053 / GERAN LTE FDD and LTE TDD.
TDLOF Flash
D-00105 GUI Value Range: OFF(Off), ON(On)
CS
3 Fallback Unit: None
LOFD-0 to Actual Value Range: OFF, ON
81283 / GERAN Default Value: OFF(Off)
TDLOF Ultra-
D-08120 Flash
3 CS
LOFD-0 Fallback
01020 / to
TDLOF GERAN
D-00102 PS Inter-
0 RAT
LOFD-0 Mobility
01046 / between
TDLOF E-
D-00104 UTRAN
6 and
LBFD-0 GERAN
02017 / DRX
TDLBF
D-00201
7

eRAN

nd
CellDrx LongDr MOD LBFD-0 DRX Meaning: Indicates the length of a long DRX cycle
SpecialP xCycleS CELLD 02017 / WBB that is applied only to one of the following types of
ara pecial RXSPE TDLBF Specifie UEs: (1) UEs that do not require power saving and
CIALPA D-00201 d Policy their RFSP indexes are contained in the RFSP index
RA 7 Manage set; (2) UEs that do not support power saving, which
LST LOFD-1 ment is indicated by the reported UE capability information.
CELLD 10223 Because of the impact of the SRS bandwidth and TA
RXSPE period specified by the TimeAlignmentTimer
CIALPA parameter, the actual value of LongDrxCycleSpecial
RA assigned to a UE may be less than the configured
value. In addition, the configured value will be
rounded down to an integral multiple of 10. Therefore,
you are advised to configure LongDrxCycleSpecial to
a value that is an integral multiple of 10. If users hope
that the value actually assigned to a UE is greater than
or equal 80 ms, set the TimeAlignmentTimer
parameter to a value greater than or equal to 10240
ms. If the TimingAdvCmdOptSwitch parameter is set
to ON, it is recommended that the LongDrxCycleSpe-
cial parameter be set to less than or equal to 320 ms.
Otherwise, the uplink time alignment performance of
UEs is affected. If the TimingAdvCmdOptSwitch
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, indicates a higher probability that UEs
in DRX mode are out of synchronization in the uplink.
This parameter applies only to LTE FDD and LTE
TDD.
subframes)
Unit: subframe
SF80, SF128, SF160, SF256, SF320, SF512, SF640,
SF1024, SF1280, SF2048, SF2560

eRAN

nd
CellDrx LongDr MOD LBFD-0 DRX Meaning: Indicates the long DRX cycle for intra-RAT
SpecialP xCycleF CELLD 02017 / ANR. If intra-RAT ANR is enabled, this parameter
ara orIntraR RXSPE TDLBF takes effect regardless of whether DRX is enabled. If a
atAnr CIALPA D-00201 long DRX cycle is configured for ANR measurement,
RA 7 it is recommended that this parameter be set to a value
LST greater than or equal to 256 ms to ensure that the UE
CELLD can successfully obtain the CGI of a cell. However, a
RXSPE large value of this parameter results in a longer CGI
CIALPA reading delay and therefore increases system delay.
RA This parameter applies only to LTE FDD and LTE
TDD.
subframes)
Unit: subframe
Actual Value Range: SF128, SF160, SF256, SF320,
SF512, SF640, SF1024, SF1280, SF2048, SF2560
CellDrx LongDr MOD LBFD-0 DRX Meaning: Indicates the long DRX cycle for inter-RAT
SpecialP xCycleF CELLD 02017 / ANR. If inter-RAT ANR is enabled, this parameter is
ara orInterR RXSPE TDLBF valid regardless of whether DRX is enabled. If there
atAnr CIALPA D-00201 are multiple RAT systems and all of them are involved
RA 7 in inter-RAT ANR measurements, it is recommended
LST that this parameter be set to the maximum value of the
CELLD long DRX cycles required by inter-RAT ANR
RXSPE measurements. Otherwise, the success rate for inter-
CIALPA RAT ANR measurements may be affected. This
RA parameter applies only to LTE FDD and LTE TDD.
subframes)
Unit: subframe
SF512, SF640, SF1024, SF1280, SF2048, SF2560

eRAN

nd
CellDrx ShortDr MOD LBFD-0 DRX Meaning: Indicates whether to enable or disable short
SpecialP xCycleS CELLD 02017 / DRX cycles only for one of the following types of
ara witchSp RXSPE TDLBF UEs: (1) UEs that do not require power saving and
ecial CIALPA D-00201 their RFSP indexes are contained in the RFSP index
RA 7 set; (2) UEs that do not support power saving, which
LST is indicated by the reported UE capability information.
CELLD This parameter applies only to LTE FDD and LTE
RXSPE TDD.
CIALPA GUI Value Range: UU_DISABLE(Disable),
RA UU_ENABLE(Enable)
Unit: None
Actual Value Range: UU_DISABLE, UU_ENABLE
Default Value: UU_DISABLE(Disable)
CellDrx ShortDr MOD LBFD-0 DRX Meaning: Indicates the length of a short DRX cycle
SpecialP xCycleS CELLD 02017 / that is applied only to one of the following types of
ara pecial RXSPE TDLBF UEs: (1) UEs that do not require power saving and
CIALPA D-00201 their RFSP indexes are contained in the RFSP index
CELLD According to 3GPP specifications, the length of a long
RXSPE DRX cycle must be an integer multiple of that of a
CIALPA short DRX cycle. In addition, the actual value of
RA LongDrxCycleSpecial assigned to a UE may be less
than the configured value because of the impact of the
SRS bandwidth and TA period specified by the
TimeAlignmentTimer parameter. Therefore, the actual
value of ShortDrxCycleSpecial assigned to a UE may
be less than the configured value. This parameter
subframes), SF8(8 subframes), SF10(10 subframes),
SF16(16 subframes), SF20(20 subframes), SF32(32
Unit: subframe
SF20, SF32, SF40, SF64, SF80, SF128, SF160,
SF256, SF320, SF512, SF640

eRAN

nd
CellDrx DrxShor MOD LBFD-0 DRX Meaning: Indicates the length of the DRX Short Cycle
SpecialP tCycleTi CELLD 02017 / Timer that applies only to one of the following types
ara merSpec RXSPE TDLBF of UEs: (1) UEs that do not require power saving and
ial CIALPA D-00201 their RFSP indexes are contained in the RFSP index
CELLD The length of this timer is expressed in the number of
RXSPE short DRX cycles. If this parameter is set to 1, the
CIALPA length of this timer is one short DRX cycle. If this
RA parameter is set to 2, the length of this timer is two
short DRX cycles. For details, see section 5.7 in 3GPP
TS 36.321. This parameter applies only to LTE FDD
and LTE TDD.
Unit: None
Default Value: 1
CellDrx OnDurat MOD LBFD-0 DRX Meaning: Indicates the length of the On Duration
SpecialP ionTime CELLD 02017 / WBB Timer that applies only to one of the following types
ara rSpecial RXSPE TDLBF Specifie of UEs: (1) UEs that do not require power saving and
CIALPA D-00201 d Policy their RFSP indexes are contained in the RFSP index
RA 7 Manage set; (2) UEs that do not support power saving, which
LST LOFD-1 ment is indicated by the reported UE capability information.
CELLD 10223 For details about this timer, see 3GPP TS 36.321.
RXSPE Because of the impact of CQI reporting intervals and
CIALPA SRS transmission intervals, the actual value of
RA OnDurationTimerSpecial assigned to a UE may be
greater than the configured value. This parameter
GUI Value Range: PSF1(1 PDCCH subframe),
PSF2(2 PDCCH subframes), PSF3(3 PDCCH
subframes), PSF4(4 PDCCH subframes), PSF5(5
PDCCH subframes), PSF6(6 PDCCH subframes),
subframes), PSF80(80 PDCCH subframes),
PDCCH subframes)
Unit: subframe
PSF60, PSF80, PSF100, PSF200

eRAN

nd
CellDrx DrxInact MOD LBFD-0 DRX Meaning: Indicates the length of the DRX Inactivity
SpecialP ivityTim CELLD 02017 / Timer that applies only to one of the following types
ara erSpecia RXSPE TDLBF of UEs: (1) UEs that do not require power saving and
l CIALPA D-00201 their RFSP indexes are contained in the RFSP index
CELLD For details about this timer, see 3GPP TS 36.321. This
RXSPE parameter applies only to LTE FDD and LTE TDD.
CIALPA GUI Value Range: PSF1(1 PDCCH subframe),
RA PSF2(2 PDCCH subframes), PSF3(3 PDCCH
PDCCH subframes), PSF300(300 PDCCH
subframes), PSF2560(2560 PDCCH subframes)
Unit: subframe
PSF750, PSF1280, PSF1920, PSF2560

eRAN

nd
CellDrx FddAnr MOD LBFD-0 DRX Meaning: Indicates the length of the DRX Inactivity
SpecialP DrxInact CELLD 02017 Timer for LTE FDD automatic neighbor relation
ara ivityTim RXSPE (ANR). If ANR is enabled, this parameter takes effect
er CIALPA regardless of whether the DRX feature is enabled.
RA This parameter applies only to LTE FDD.
LST GUI Value Range: PSF1(1 PDCCH subframe),
CELLD PSF2(2 PDCCH subframes), PSF3(3 PDCCH
RXSPE subframes), PSF4(4 PDCCH subframes), PSF5(5
CIALPA PDCCH subframes), PSF6(6 PDCCH subframes),
RA PSF8(8 PDCCH subframes), PSF10(10 PDCCH
Unit: subframe
PSF750, PSF1280, PSF1920, PSF2560
CellDrx CellDrx MOD LBFD-0 DRX Meaning: Indicates whether the parameters in the
SpecialP SpecialP CELLD 02017 / WBB CellDrxSpecialPara MO take effect. If the
ara araValid RXSPE TDLBF Specifie CellDrxSpecialParaValid parameter is set to
CIALPA D-00201 d Policy FALSE(FALSE), the parameters in the
RA 7 Manage CellDrxSpecialPara MO do not take effect but the
LST LOFD-1 ment parameters in the Drx MO take effect. If the parameter
CELLD 10223 is set to TRUE(TRUE), the parameters in the
RXSPE CellDrxSpecialPara MO take effect. This parameter
CIALPA applies only to LTE FDD and LTE TDD.
RA GUI Value Range: FALSE(FALSE), TRUE(TRUE)
Unit: None
Actual Value Range: FALSE, TRUE
Default Value: FALSE(FALSE)

eRAN

nd
CellDrx DrxState MOD LBFD-0 DRX Meaning: Indicates whether to allow only
Para DuringU CELLD 02017 / retransmission during an uplink HARQ retransmission
lHarqRe RXPAR TDLBF period. If this parameter is set to
tx A D-00201 DRX_ACTIVE_FOR_RETX(DRX_ACTIVE_FOR_
LST 7 RETX), for UEs in DRX mode, the eNodeB performs
CELLD only retransmission during an uplink HARQ
RXPAR retransmission period. If this parameter is set to
A DRX_ACTIVE_FOR_VOICE(DRX_ACTIVE_FOR_
VOICE), for VoLTE UEs in DRX mode, the eNodeB
can also perform initial transmission during an uplink
HARQ retransmission period. If drx-InactivityTimer
for a VoLTE UE is less than 8 ms, the probability of
scheduling this VoLTE UE increases, decreasing the
DRX-induced scheduling latency and improving
speech quality. This parameter applies only to LTE
FDD.
GUI Value Range:
DRX_ACTIVE_FOR_RETX(DRX_ACTIVE_FOR_
RETX),
DRX_ACTIVE_FOR_VOICE(DRX_ACTIVE_FOR_
VOICE)
Unit: None
Actual Value Range: DRX_ACTIVE_FOR_RETX,
DRX_ACTIVE_FOR_VOICE
Default Value:
DRX_ACTIVE_FOR_VOICE(DRX_ACTIVE_FOR_
VOICE)

eRAN

nd
CellAlg DlSchS MOD LOFD-1 Traffic Meaning:

oSwitch witch CELLA 10205 / Model Indicates whether to enable downlink scheduling
LGOSW TDLOF Based algorithms in a cell. This parameter includes the
ITCH D-11022 Perform following options:
LST 7 ance
CELLA LOFD-0 Optimiz FreqSelSwitch: Indicates whether to enable
LGOSW 01016 / ation frequency-selective scheduling. If this option is
ITCH TDLOF VoIP selected, data is transmitted on the frequency band of
D-00101 Semi- high channel quality. This option applies only to LTE
6 persisten FDD and LTE TDD.
LBFD-0 t
SpsSchSwitch: Indicates whether to enable semi-
0101502 Scheduli
persistent scheduling during talk spurts of VoLTE
/ ng
services. If this option is selected, semi-persistent
TDLBF Dynami scheduling is applied during talk spurts of VoLTE
D-00101 c services. If this option is deselected, dynamic
502 Scheduli scheduling is applied during talk spurts of VoLTE
LOFD-0 ng services. This option applies only to LTE FDD and
01109 / DL LTE TDD.
TDLOF Non-
MBSFNShutDownSwitch: Indicates whether to
D-00110 GBR
enable Multimedia Broadcast multicast service Single
9 Packet
Frequency Network (MBSFN) subframe shutdown. If
LOFD-0 Bundlin
this option is selected, MBSFN subframe shutdown is
01070 / g
applied. If this option is deselected, MBSFN subframe
TDLOF Symbol shutdown is not applied. This option takes effect only
D-00107 Power if the SymbolShutdownSwitch option of the
0 Saving PowerSaveSwitch parameter is selected. If the
TDLOF Scheduli MBSFNShutDownSwitch option is selected, the
D-07022 ng setting of the switch for mapping SIBs to SI messages
4/ Based becomes invalid. If the MBSFNShutDownSwitch
TDLOF on Max option is deselected, the setting of the switch for
D-07022 Bit Rate mapping SIBs to SI messages becomes valid. The
2 MBSFNShutDownSwitch option applies only to LTE-
Basic
LBFD-0 only base stations. This option applies only to LTE
Scheduli
02025 / FDD and LTE TDD.
ng
TDLBF Support NonGbrBundlingSwitch: Indicates whether to enable
D-00202 of downlink non-GBR packet bundling. If this option is
5 aperiodi selected, delay of non-GBR services can be controlled
LBFD-0 c CQI in non-congestion scenarios. If this option is
02031 / reports deselected, delay of non-GBR services cannot be
TDLBF MBR>G controlled. This option applies only to LTE FDD and
D-00203 BR LTE TDD.
1 Configu EnAperiodicCqiRptSwitch: Indicates whether to
LBFD-0 ration enable enhanced aperiodic channel quality indicator
70102 / Enhance (CQI) reporting. If this option is selected, the eNodeB
TDLBF d DL triggers aperiodic CQI reporting for a UE based on
Frequen downlink services of the UE and the interval at which

eRAN

nd
D-07010 cy the UE sends periodic CQI reports. If this option is

2 Selectiv deselected, UEs under non-frequency-selective
LBFD-0 e scheduling do not trigger aperiodic CQI reporting
60202 Enhance based on downlink services and trigger an aperiodic
d CQI reporting if no valid periodic CQI reports are sent
LOFD-0 in eight consecutive periodic CQI reporting periods.
81218 extende
d QCI This option applies only to LTE FDD and LTE TDD.
LTROF
D-11120 MCPTT DlMbrCtrlSwitch: Indicates whether to enable
4/ Voice downlink scheduling based on the maximum bit rate
TDLOF Manage (MBR) and guaranteed bit rate (GBR) on GBR
D-12110 ment bearers. If this option is selected, the eNodeB
6 DL performs downlink scheduling on GBR bearers based
Asynchr on the MBR and GBR. If this option is deselected, the
TDLBF eNodeB performs downlink scheduling on GBR
D-00200 onous
HARQ bearers based on the GBR only. This option applies
5 only to LTE FDD and LTE TDD.
LBFD-0 Optimiz
60101 ation of MbrDlSchSwitch: Indicates whether the eNodeB
Periodic performs downlink scheduling based on MBR. If this
LBFD-0 and option is selected, the eNodeB prioritizes UEs based
60103 / Aperiodi on the MBRs during downlink scheduling. This
TDLBF c CQI parameter applies only to LTE TDD.
D-08010 Reportin
2 UeAmbrDlSchSwitch: Indicates whether the eNodeB
g
performs downlink scheduling based on per UE
LEOFD- Enhance aggregate maximum bit rates (UE-AMBRs). If this
111305 d DL option is selected, the eNodeB prioritizes UEs based
LEOFD- Frequen on the UE-AMBRs during downlink scheduling. This
111307 cy option applies only to LTE TDD.
TDLOF Selectiv
e EpfEnhancedSwitch: Indicates whether to enable
D-12110
Scheduli enhanced proportional fair (EPF) enhancement for
5
ng scheduling. EPF enhancement for scheduling is
enabled only if this option is selected. This option
Virtual
4T4R
eMIMO AperiodicCqiTrigOptSwitch: Indicates whether to
optimize triggering of aperiodic CQI reporting. If this
PRRC option is selected, a UE performing initial access
and triggers aperiodic CQI reporting based on related
DRX trigger conditions after the DLMAC instance has been
Policy established for 200 ms and the eNodeB receives
for MSG5. Consider that aperiodic CQI reporting is
Public triggered by invalid CQI reports in eight consecutive
Safety 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

eRAN

nd
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. This option applies only to LTE FDD and LTE
TDD.
VoipTbsBasedMcsSelSwitch: Indicates whether the
modulation and coding scheme (MCS) index is
selected based on the transport block size (TBS) in
downlink 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. This option applies only to LTE
FDD and LTE TDD.
PagingInterfRandSwitch: Indicates whether to enable
interference randomization for paging messages. If
this option is selected, interference randomization is
enabled for paging messages. This option applies only
to LTE FDD and LTE TDD.
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. This
option applies only to LTE FDD and LTE TDD.
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. This option applies only to LTE FDD and
LTE TDD.
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

eRAN

nd
in subframes 3 and 8 is increased when uplink-

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
parameter 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. This option applies only to LTE FDD and
LTE TDD.
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 for VoLTE services or
increasing the throughput of data services in mixed
service scenarios. However, the delay in VoLTE voice
packet scheduling will increase in the downlink and
MOSs may decrease. You are advised to deselect this
option if you prefer VoLTE performance and do not

eRAN

nd
expect MOS reduction. This option applies only to

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. This option applies only
RLCArqFeedbackEnhancedSwitch: Indicates whether
to modify HARQ feedback results based on RLC
status reports when uplink-downlink configuration 2
is used. If this option is selected, the eNodeB modifies
HARQ feedback results based on RLC status reports
after receiving the reports. This prevents unnecessary
HARQ retransmissions. This option applies only to
LTE TDD.
PaReconfigOptSwitch: Indicates whether to enable PA
reconfiguration optimization. The optimization is
enabled when this option is selected. This option
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. This option
DlRLCStateReportSchDelaySw: Indicates whether to
enable optimization on the delay-based scheduling of
downlink RLC status reports. The optimization is
enabled when this option is selected. This option
SmallPktMcsSelectAlgoSw: Indicates whether to
enable MCS selection for small packets. If this option
is selected, the scheduler selects an MCS with a lower
index based on the amount of data to be initially
transmitted and the allocated TBS in each TTI on
condition that the allocated TBS can carry the data.
The function is enabled only if this option is selected.
This option applies only to LTE FDD and LTE TDD.
SRB0SplitSchSw: Indicates whether to enable
separate scheduling of SRB0 and contention
resolution MCE. If this option is selected, SRB0 and
contention resolution MCE are separately scheduled.

eRAN

nd
BfUserPairPriorSwitch: Indicates whether to

preferentially allocate resources to paired
beamforming UEs for UE pairing features such as MU
beamforming and DMIMO. If this option is selected,
the eNodeB preferentially allocates resources to
paired beamforming UEs for UE pairing features such
as MU beamforming and DMIMO. This option
HarqAllocOptSwitch: Indicates whether to optimize

the allocation of HARQ processes. If this option is
selected, the downlink UE rate increases. This option
takes effect only when DMIMO or massive MIMO is
enabled. This option applies only to LTE TDD.
Pusch32Switch: Indicates whether to enable the

PUSCH 3-2 feedback mode. If this option is selected,
UEs that support the PUSCH 3-2 feedback mode use
this mode to aperiodically report CQIs. If this option
is deselected, the mode cannot be used. This option
DlPreciseAmbrCtrlSwitch: Indicates whether to

enable precise downlink AMBR control. If this option
is selected, a more accurate optimization algorithm
applies to the AMBR control, which achieves more
accurate AMBR control. If this option is deselected,
the original AMBR control algorithm is used. This
GUI Value Range: FreqSelSwitch(FreqSelSwitch),
SpsSchSwitch(SpsSchSwitch),
MBSFNShutDownSwitch(MBSFNShutDownSwitch),
NonGbrBundlingSwitch(NonGbrBundlingSwitch),
EnAperiodicCqiRptSwitch(EnAperiodicCqiRptS-
witch), DlMbrCtrlSwitch(DlMbrCtrlSwitch),
MbrDlSchSwitch(MbrDlSchSwitch),
UeAmbrDlSchSwitch(UeAmbrDlSchSwitch),
EpfEnhancedSwitch(EpfEnhancedSwitch),
AperiodicCqiTrigOptSwitch(AperiodicCqiTrigOptS-
witch), VoipTbsBasedMcsSelS-
witch(VoipTbsBasedMcsSelSwitch),
PagingInterfRandSwitch(PagingInterfRandSwitch),
DlSingleUsrMcsOptSwitch(DlSingleUsrMcsOptS-
witch), SubframeSchDiffSwitch(SubframeSchDiffS-
witch), TailPackagePriSchS-
witch(TailPackagePriSchSwitch),
UeSigMcsEnhanceSwitch(UeSigMcsEnhanceSwitch),
FreqSelJudgeIgnorDopplerSwitch(FreqSelJudgeIgnor-
DopplerSwitch),

eRAN

nd
SIB1InterfRandSwitch(SIB1InterfRandSwitch),
EnhExtQCISpsSchSwitch(EnhExtQCISpsSchSwitch),
DlVoipBundlingSwitch(DlVoipBundlingSwitch),
DlPacketLenAwareSchSw(DlPacketLenAwar-
eSchSw), RLCArqFeedbackEnhanced-
Switch(RLCArqFeedbackEnhancedSwitch),
PaReconfigOptSwitch(PaReconfigOptSwitch),
RankRapidRptSwitch(RankRapidRptSwitch),
DlRLCStateReportSchDe-
laySw(DlRLCStateReportSchDelaySw),
SmallPktMcsSelectAlgoSw(SmallPktMcsSelectAl-
goSw), SRB0SplitSchSw(SRB0SplitSchSw),
BfUserPairPriorSwitch(BfUserPairPriorSwitch),
HarqAllocOptSwitch(HarqAllocOptSwitch),
Pusch32Switch(Pusch32Switch),
DlPreciseAmbrCtrlSwitch(DlPreciseAmbrCtrlSwitch)
Unit: None
Actual Value Range: FreqSelSwitch, SpsSchSwitch,
MBSFNShutDownSwitch, NonGbrBundlingSwitch,
EnAperiodicCqiRptSwitch, DlMbrCtrlSwitch,
MbrDlSchSwitch, UeAmbrDlSchSwitch,
EpfEnhancedSwitch, AperiodicCqiTrigOptSwitch,
VoipTbsBasedMcsSelSwitch, PagingInterfRand-
Switch, DlSingleUsrMcsOptSwitch,
SubframeSchDiffSwitch, TailPackagePriSchSwitch,
UeSigMcsEnhanceSwitch, FreqSelJudgeIgnorDop-
plerSwitch, SIB1InterfRandSwitch,
EnhExtQCISpsSchSwitch, DlVoipBundlingSwitch,
DlPacketLenAwareSchSw, RLCArqFeedbackEnhan-
cedSwitch, PaReconfigOptSwitch,
RankRapidRptSwitch, DlRLCStateReportSchDe-
laySw, SmallPktMcsSelectAlgoSw, SRB0SplitSchSw,
BfUserPairPriorSwitch, HarqAllocOptSwitch,
Pusch32Switch, DlPreciseAmbrCtrlSwitch
Default Value: FreqSelSwitch:Off, SpsSchSwitch:Off,
MBSFNShutDownSwitch:Off, NonGbrBundlingS-
witch:Off, EnAperiodicCqiRptSwitch:Off,
DlMbrCtrlSwitch:Off, MbrDlSchSwitch:Off,
UeAmbrDlSchSwitch:Off, EpfEnhancedSwitch:Off,
AperiodicCqiTrigOptSwitch:On, VoipTbsBasedMcs-
SelSwitch:On, PagingInterfRandSwitch:Off,
DlSingleUsrMcsOptSwitch:Off, SubframeSchDiffS-
witch:Off, TailPackagePriSchSwitch:Off,
UeSigMcsEnhanceSwitch:Off, FreqSelJudgeIgnor-
DopplerSwitch:Off, SIB1InterfRandSwitch:On,
EnhExtQCISpsSchSwitch:Off, DlVoipBundlingS-
witch:Off, DlPacketLenAwareSchSw:Off,
RLCArqFeedbackEnhancedSwitch:Off,

eRAN

nd
PaReconfigOptSwitch:Off, RankRapidRptSwitch:Off,
DlRLCStateReportSchDelaySw:Off,
SmallPktMcsSelectAlgoSw:Off,
SRB0SplitSchSw:Off, BfUserPairPriorSwitch:Off,
HarqAllocOptSwitch:Off, Pusch32Switch:Off,
DlPreciseAmbrCtrlSwitch:Off

eRAN

nd
CellDlsc DlEnhan MOD LBFD-0 Dynami Meaning:

hAlgo cedVoip CELLD 0101502 c Indicates whether to enable enhanced scheduling on
SchSw LSCHA / Scheduli VoLTE services in the downlink. This parameter
LGO TDLBF ng includes options related to enhanced scheduling
LST D-00101 VoIP algorithms for VoLTE services in the downlink.
CELLD 502 Semi-
LSCHA LOFD-0 persisten DlVoIPLoadBasedSchSwitch: Indicates whether to
LGO 01016 / t enable cell-load-based adaptive selection of dynamic
TDLOF Scheduli scheduling and semi-persistent scheduling for UEs
D-00101 ng running VoLTE services. If this option is deselected,
6 cell-load-based adaptive selection of dynamic and
semi-persistent scheduling cannot be performed for
UEs running VoLTE services. If this option is
selected, dynamic and semi-persistent scheduling can
be adaptively selected for UEs running VoLTE
services based on the cell load. This option applies
DlSpsRevHarqUseSwitch: Indicates whether HARQ
feedback resources reserved for semi-persistent
scheduling can be used by dynamic scheduling.
HARQ feedback resources reserved for semi-
persistent scheduling can be used by dynamic
scheduling only when this option is selected. This
DlSpsDrxDecouplingSwitch: Indicates whether the
long DRX cycle configuration is considered during
the configuration and activation of downlink semi-
persistent scheduling. If this option is deselected, the
long DRX cycle configuration is considered during
the configuration and activation of downlink semi-
persistent scheduling, and downlink semi-persistent
scheduling cannot be configured or activated when the
downlink semi-persistent scheduling period is not an
integral multiple of the long DRX cycle. If this option
is selected, the long DRX cycle configuration is not
considered during the configuration and activation of
downlink semi-persistent scheduling. This option
DlSchVoipDuringHoSwitch: Indicates whether to
enable voice service scheduling in the downlink
during scheduling of handover signaling. If this option
is deselected, the eNodeB does not schedule voice
services in the downlink when scheduling handover
signaling. If this option is selected, the eNodeB can
schedule voice services in the downlink when
scheduling handover signaling, decreasing the
downlink packet delay for voice services and

eRAN

nd
improving the voice service quality in handovers,

especially the voice service quality in DRX scenarios.
GUI Value Range: DlVoIPLoadBasedSchS-
witch(DlVoIPLoadBasedSchSwitch),
DlSpsRevHarqUseSwitch(DlSpsRevHarqUseSwitch),
DlSpsDrxDecouplingSwitch(DlSpsDrxDecouplingS-
witch), DlSchVoipDuringHoS-
witch(DlSchVoipDuringHoSwitch)
Unit: None
Actual Value Range: DlVoIPLoadBasedSchSwitch,
DlSpsRevHarqUseSwitch, DlSpsDrxDecouplingS-
witch, DlSchVoipDuringHoSwitch
Default Value: DlVoIPLoadBasedSchSwitch:Off,
DlSpsRevHarqUseSwitch:Off,
DlSpsDrxDecouplingSwitch:Off, DlSchVoipDuring-
HoSwitch:On
SpidCfg Spid ADD LOFD-0 Camp & Meaning: Indicates the subscriber profile ID (SPID).
SPIDCF 0105401 Handov This parameter applies only to LTE FDD and LTE
G / er Based TDD.
LST TDLOF on SPID GUI Value Range: 1~256
SPIDCF D-00105 UL Pre-
401 Unit: None
G allocatio
LOFD-0 n Based Actual Value Range: 1~256
MOD
SPIDCF 01059 / on SPID Default Value: None
G TDLOF
D-00105
RMV 9
SPIDCF
G
SpidCfg DrxStat ADD LBFD-0 DRX Meaning: Indicates whether to use normal or special
us SPIDCF 02017 / Camp & DRX. If this parameter is set to TRUE, ordinary DRX
G TDLBF Handov parameters are applied to UEs with the SPID. If this
MOD D-00201 er Based parameter is set to FALSE, special DRX parameters
SPIDCF 7 on SPID are applied to UEs with the SPID. This parameter
G LOFD-0 applies only to LTE FDD and LTE TDD.
WBB
LST 0105401 Specifie GUI Value Range: FALSE(FALSE), TRUE(TRUE)
SPIDCF / d Policy Unit: None
G TDLOF Manage
D-00105 Actual Value Range: FALSE, TRUE
ment
401 Default Value: FALSE(FALSE)
LOFD-1
10223

eRAN

nd
CellPuc SriAlgo MOD LBFD-0 Physical Meaning:

chAlgo Switch CELLP 02003 / Channel Indicates the working modes for SRI reporting period
UCCHA TDLBF Manage configuration.
LGO D-00200 ment
LST 3 Voice SriAdaptiveHoldForVoIPSW: Indicates whether to
CELLP LOFD-0 Characte enable SRI reporting period adaptation for VoLTE
UCCHA 81229 ristic UEs during resource adjustment for SRI reporting. If
LGO Awarene this option is selected, SRI reporting periods are
ss configured based on the cell load. If the number of
Scheduli UEs is small, adaptively configured SRI reporting
ng 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. This
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 of SRI reporting, semi-
persistent ACK reporting, and dynamic ACK
reporting. When CA and VoLTE are enabled, few UEs
can be assigned short SRI reporting periods, the
amount of PUCCH resource decreases, but the amount
of available PUSCH resource increases. This option
SriOffsetReConfigForDrxSW: indicates whether to
reconfigure the SRI subframe offset for DRX. 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 this function.
SriPeriodOptForVoipSW: Indicates whether to
perform VoLTE-based adaptive SRI period
optimization. If this option is selected, the eNodeB
preferentially allocates a short SRI period for VoLTE
UEs, thereby improving user experience of VoLTE
UEs. This option takes effect only when
SriPeriodAdaptive is set to QCIADAPTIVE and
SriReCfgInd is set off. This option applies only to

eRAN

nd
FDD. If this option is deselected, the eNodeB does not

perform this function.
SriDetectEnhanceSW: Indicates whether to enable L1
detection enhancement algorithm for PUCCH SRI.
When this option is selected, the PUCCH SRI
detection enhancement algorithm is enabled for a cell.
In this case, an optimized interference noise
estimation algorithm applies to the PUCCH format1
detection. This helps effectively suppress false SRI
detections. When this option is deselected, the
PUCCH SRI detection enhancement algorithm is not
enabled, and the original demodulation algorithm is
used for PUCCH format1 detection. This option
GUI Value Range: SriAdaptiveHoldFor-
VoIPSW(SriAdaptiveHoldForVoIPSW),
SriPeriodCfgOptSW(SriPeriodCfgOptSW),
SriOffsetReConfigForDrxSW(SriOffsetReConfig-
ForDrxSW), SriPeriodOptFor-
VoipSW(SriPeriodOptForVoipSW),
SriDetectEnhanceSW(SriDetectEnhanceSW)
Unit: None
Actual Value Range: SriAdaptiveHoldForVoIPSW,
SriPeriodCfgOptSW, SriOffsetReConfigForDrxSW,
SriPeriodOptForVoipSW, SriDetectEnhanceSW
Default Value: SriAdaptiveHoldForVoIPSW:Off,
SriPeriodCfgOptSW:On, SriOffsetReConfig-
ForDrxSW:Off, SriPeriodOptForVoipSW:Off,
SriDetectEnhanceSW:Off

eRAN

nd
GlobalP QciPara MOD LBFD-0 Radio Meaning: Indicates whether parameters in QciPara,
rocSwitc EffectFl GLOBA 02008 Bearer CellQciPara, and CnOperatorQciPara MOs take
h ag LPROC TDLBF Manage effect. The parameters take effect by default. If this
SWITC D-00201 ment parameter is set to OFF, parameters in StandardQci,
H 7 DRX ExtendedQci, CellStandardQci, CellExtendedQci,
LST CnOperatorStandardQci, and CnOperatorExtendedQci
LBFD-0 Mobility MOs take effect and parameters in QciPara,
GLOBA 02018 / Manage
LPROC CellQciPara, and CnOperatorQciPara MOs do not
TDLBF ment take effect. If this parameter is set to ON, parameters
SWITC D-00201
H Coverag in QciPara, CellQciPara, and CnOperatorQciPara
8 e Based MOs take effect and parameters in StandardQci,
TDLBF Intra- ExtendedQci, CellStandardQci, CellExtendedQci,
D-00201 frequenc CnOperatorStandardQci, and CnOperatorExtendedQci
801 y MOs do not take effect. This parameter applies only to
LBFD-0 Handov LTE FDD and LTE TDD.
0201802 er GUI Value Range: OFF(Off), ON(On)
/ Coverag Unit: None
TDLBF e Based
D-00201 Inter- Actual Value Range: OFF, ON
802 frequenc Default Value: ON(On)
LBFD-0 y
0201805 Handov
/ er
TDLBF Service
D-00201 Based
805 Inter-
LOFD-0 frequenc
0301101 y
/ Handov
TDLOF er
D-00301 Transpo
101 rt
LOFD-0 Overboo
0301102 king
/ Transpo
TDLOF rt
D-00301 Differen
102 tiated
LOFD-0 Flow
0301103 Control
/ Transpo
TDLOF rt
D-00301 Resourc
103 e
Overloa
d
Control

eRAN

nd
RrcCon UeInacti MOD LOFD-0 Dynami Meaning: Indicates the length of the UE Inactivity
nStateTi vityTim RRCCO 0110501 c DRX Timer for UEs that have entered DRX mode and have
mer erDynDr NNSTA / High- no QCI-1 services when dynamic DRX is enabled. If
x TETIM TDLOF Mobility the eNodeB detects that such a UE has neither
ER D-00110 - received nor sent data for a period exceeding the value
LST 501 Triggere of this parameter, the eNodeB releases the RRC
RRCCO LOFD-0 d Idle connection for the UE. If this parameter is set to a
NNSTA 0110502 Mode large value, the amount of signaling is reduced but UE
TETIM / power consumption increases. You are advised to set
RRC this parameter to a value greater than that of
ER TDLOF Connect
D-00110 UlSynTimerDynDrx. In power saving mode, you are
ion advised to set this parameter significantly different
502 Manage from the value of the UlSynTimerDynDrx parameter,
LBFD-0 ment for example a difference of 10 seconds, to avoid
02007 power consumption increase due to the increase of
signaling. If the QciParaEffectFlag parameter in the
GlobalProcSwitch MO is set to ON(On), the
UeInactivityTimerDynDrxQci parameter in the
QciPara MO, rather than this parameter takes effect.
TDD.
Unit: s
Default Value: 200
RrcCon UeInact MOD LBFD-0 RRC Meaning: Indicates the length of the UE Inactivity
nStateTi TimerD RRCCO 02007/ Connect Timer for UEs that have entered DRX mode and have
mer ynDrxQ NNSTA TDLBF ion QCI-1 services when dynamic DRX is enabled. If the
ci1 TETIM D-00200 Manage eNodeB detects that such a UE has neither received
ER 7 ment nor sent data for a period exceeding the value of this
LST LOFD-0 Dynami parameter, the eNodeB releases the RRC connection
RRCCO 0110501 c DRX for the UE. This parameter takes effect only for such
NNSTA UEs that will access the network after the parameter is
TETIM set. If the QciParaEffectFlag parameter in the
ER GlobalProcSwitch MO is set to ON(On), the
UeInactivityTimerDynDrxQci parameter in the
QciPara MO for QCI 1, rather than this parameter
takes effect. This parameter applies only to LTE FDD
and LTE TDD.
Unit: s
Default Value: 200

eRAN

nd
QciPara UeInacti ADD LBFD-0 RRC Meaning: Indicates the length of the UE inactivity
vityTim QCIPA 02007 / Connect timer for UEs that have entered DRX mode and have
erDynDr RA TDLBF ion bearers of the QCI when dynamic DRX is enabled. If
xQci MOD D-00200 Manage the eNodeB detects that a UE has neither received nor
QCIPA 7 ment sent data for a period exceeding the value of this
RA LOFD-0 Dynami parameter, the eNodeB releases the RRC connection
0110501 c DRX for this UE. If this parameter is set to a large value, the
LST amount of signaling is reduced but UE power
QCIPA / Enhance
TDLOF consumption increases. You are advised to set this
RA d parameter to a value greater than that of
D-00110 Extende
501 UlSynTimerDynDrx. In power saving mode, you are
d QCI advised to set this parameter significantly different to
LOFD-0 Enhance the value of the UlSynTimerDynDrx parameter, for
81218 d QoS example a gap of 10 seconds, to avoid power
TDLOF for consumption increase due to the increase of signaling.
D-11023 MCPTT If a UE has bearers of several QCIs, the eNodeB
0 (Trial) selects the longest UE Inactivity Timer of bearers with
LOFD-0 Voice the highest QCI-specific priority specified by the
81229 / Characte UeInactiveTimerPri parameter as the UE inactivity
TDLOF ristic timer for the UE. This parameter applies only to LTE
D-08122 Awarene FDD and LTE TDD.
9 ss GUI Value Range: 10~3600
LTROF Scheduli Unit: s
D-11120 ng
1/ MCPTT
TDLOF QoS Default Value: 200
D-12110 Manage
3 ment
TDLOF Congesti
D-12110 on
4 Control
LTROF for
D-11120 Public
3/ Safety
TDLOF RRC
D-12110 and
5 DRX
Policy
for
Public
Safety

eRAN

nd
QciPara UeInacti ADD LBFD-0 RRC Meaning: Indicates the priority of the QCI-specific
veTimer QCIPA 02007 / Connect UE Inactivity Timer. A larger value of this parameter
Pri RA TDLBF ion indicates a higher priority. The eNodeB selects the
MOD D-00200 Manage longest UE Inactivity Timer with the highest QCI-
QCIPA 7 ment specific priority as the UE Inactivity Timer for UEs
RA LOFD-0 Voice running services with the specific QCI. The UE
81229 / Characte Inactivity Timer for QCI 69 is taken as the UE
LST Inactivity Timer for the MCPTT UEs. This parameter
QCIPA TDLOF ristic
D-08122 Awarene applies only to LTE FDD and LTE TDD.
RA
9 ss GUI Value Range: 0~255
Scheduli Unit: None
ng
Default Value: 0
CellAlg DynDrx MOD LBFD-0 DRX Meaning:

oSwitch Switch CELLA 02017/ Dynami Indicates whether to enable dynamic discontinuous
LGOSW TDLBF c DRX reception (DRX) or smart DRX. Smart DRX applies
ITCH D-00201 only to LTE TDD cells and requires the mobility
7 Smart
LST DRX speed of UEs to be reported.
CELLA LOFD-0
LGOSW 0110501 Enhance DynDrxSwitch: If this switch is on, dynamic DRX
ITCH / d QoS applies to newly admitted UEs to reduce signaling
TDLOF for overheads or decrease UE power consumption. If this
D-00110 MCPTT switch is off, dynamic DRX does not apply to newly
501 (Trial) admitted UEs. Dynamic DRX applies to carrier
RRC aggregation (CA) UEs only when this switch is on in
TDLBF both the primary serving cell (PCell) and secondary
D-07011 and
DRX serving cell (SCell).
2
Policy SmartDrxSwitch: If this switch is on, smart DRX
TDLOF for
D-11023 applies to newly admitted UEs that support mobility
Public speed reporting. The eNodeB dynamically sets DRX-
0 Safety related parameters based on UE mobility speeds. If
TDLOF this switch is off, smart DRX does not apply to newly
D-12110 admitted UEs. Smart DRX applies to CA UEs only
5 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. This option applies only to LTE
FDD and LTE TDD.
GUI Value Range: DynDrxSwitch(DynDrxSwitch),
SmartDrxSwitch(SmartDrxSwitch)
Unit: None
Actual Value Range: DynDrxSwitch, SmartDrxSwitch
Default Value: DynDrxSwitch:Off,
SmartDrxSwitch:Off

eRAN

nd
CellDrx LongDr MOD TDLBF DRX Meaning: Indicates the length of the long DRX cycle
Para xCycleU CELLD D-00201 Dynami for a UE in the uplink out-of-synchronization state.
nsync RXPAR 7/ c DRX Set this parameter to a value greater than the value of
A LBFD-0 LongDrxCycle; otherwise, the power saving gain of
LST 02017 the DRX for UEs in the uplink out-of-synchronization
CELLD LOFD-0 state may decrease. This parameter applies only to
RXPAR 01105 / LTE FDD and LTE TDD.
A LOFD-0 GUI Value Range: SF10(10 subframes), SF20(20
0110501 subframes), SF32(32 subframes), SF40(40
/ subframes), SF64(64 subframes), SF80(80
TDLOF subframes), SF128(128 subframes), SF160(160
D-00110 subframes), SF256(256 subframes), SF320(320
501 subframes), SF512(512 subframes), SF640(640
subframes)
Unit: subframe
SF80, SF128, SF160, SF256, SF320, SF512, SF640,
SF1024, SF1280, SF2048, SF2560
CellDrx Ondurati MOD LOFD-0 Dynami Meaning: Indicates the DRX onduration timer for UEs
Para onTimer CELLD 0110501 c DRX when the eNodeB does not maintain synchronization
Unsync RXPAR / High- for UEs. This parameter applies only to LTE FDD and
A TDLOF Mobility LTE TDD.
LST D-00110 - GUI Value Range: PSF1(1 PDCCH subframe),
CELLD 501 Triggere PSF2(2 PDCCH subframes), PSF3(3 PDCCH
RXPAR LOFD-0 d Idle subframes), PSF4(4 PDCCH subframes), PSF5(5
A 0110502 Mode PDCCH subframes), PSF6(6 PDCCH subframes),
/ DRX PSF8(8 PDCCH subframes), PSF10(10 PDCCH
TDLOF subframes), PSF20(20 PDCCH subframes), PSF30(30
D-00110 PDCCH subframes), PSF40(40 PDCCH subframes),
502 PSF50(50 PDCCH subframes), PSF60(60 PDCCH
LBFD-0 subframes), PSF80(80 PDCCH subframes),
02017 PSF100(100 PDCCH subframes), PSF200(200
PDCCH subframes)
Unit: subframe

eRAN

nd
CellDrx DrxInact MOD LBFD-0 DRX Meaning: Indicates the DRX inactivity timer for UEs
Para ivityTim CELLD 02017 Dynami when the eNodeB does not maintain synchronization
erUnsyn RXPAR LOFD-0 c DRX for UEs. This parameter applies only to LTE FDD and
c A 01105 / LTE TDD.
High-
LST TDLOF Mobility GUI Value Range: PSF200(200 PDCCH subframes),
CELLD D-00110 - PSF300(300 PDCCH subframes), PSF500(500
RXPAR 5/ Triggere PDCCH subframes), PSF750(750 PDCCH
A LOFD-0 d Idle subframes), PSF1280(1280 PDCCH subframes),
0110501 Mode PSF1920(1920 PDCCH subframes), PSF2560(2560
/ PDCCH subframes)
TDLOF Unit: subframe
D-00110
501 Actual Value Range: PSF200, PSF300, PSF500,
PSF750, PSF1280, PSF1920, PSF2560
TDLOF
D-00110 Default Value: PSF200(200 PDCCH subframes)
502
RrcCon UlSynTi MOD LOFD-0 Dynami Meaning: Indicates the timer used to govern the
nStateTi merDyn RRCCO 0110501 c DRX period in which the eNodeB maintains uplink
mer Drx NNSTA / High- synchronization for a DRX UE when dynamic DRX is
TETIM TDLOF Mobility enabled. After this timer expires, the eNodeB does not
ER D-00110 - send Timing Advance Command to the UE. You are
LST 501 Triggere advised to set this parameter to a value smaller than
RRCCO LOFD-0 d Idle the value of UeInactivityTimerDynDrx.In power
NNSTA 0110502 Mode saving mode, you are advised to set this parameter
TETIM / significantly different to the value of the
ER TDLOF UeInactivityTimerDynDrx parameter, for example a
D-00110 gap of 10 seconds, to avoid power consumption
502 increase due to the increase of signaling. This
Unit: s
Default Value: 20

eRAN

nd
RrcCon UeInacti MOD LBFD-0 RRC Meaning: Indicates the length of the UE Inactivity
nStateTi veTimer RRCCO 02007 / Connect Timer for UEs that do not have QCI-1 services. If the
mer NNSTA TDLBF ion eNodeB detects that such a UE has neither received
TETIM D-00200 Manage nor sent data for a period exceeding the value of this
ER 7 ment parameter, the eNodeB releases the RRC connection
LST for the UE. If this parameter is set to 0, the UE
RRCCO Inactivity Timer is not used. This parameter takes
NNSTA effect only for such UEs that will access the network
TETIM after the parameter is set. If the QciParaEffectFlag
ER parameter in the GlobalProcSwitch MO is set to
ON(On), the UeInactiveTimerForQci parameter in the
TDD.
Unit: s
Default Value: 20

eRAN

nd
QciPara UeInacti ADD LBFD-0 RRC Meaning: Indicates the length of the UE inactivity
veTimer QCIPA 02007 / Connect timer for UEs that have bearers of a QCI. If the
ForQci RA TDLBF ion eNodeB detects that a UE has neither received nor
MOD D-00200 Manage sent data for a period exceeding the value of this
QCIPA 7 ment parameter, the eNodeB releases the RRC connection
RA LOFD-0 Enhance for this UE. If this parameter is set to 0, the UE
81218 d inactivity timer is not used. This parameter takes
LST effect only for UEs that will access the network after
QCIPA TDLOF Extende
d QCI this parameter is set. If a UE has bearers of several
RA D-11023 QCIs, the eNodeB selects the longest UE Inactivity
0 Enhance Timer of bearers with the highest QCI-specific
LOFD-0 d QoS priority specified by the UeInactiveTimerPri
81229 / for parameter as the UE inactivity timer for the UE. This
TDLOF MCPTT parameter applies only to LTE FDD and LTE TDD.
D-08122 (Trial)
9 Voice
Characte Unit: s
LTROF
D-11120 ristic Actual Value Range: 0~3600
1/ Awarene Default Value: 20
TDLOF ss
D-12110 Scheduli
3 ng
TDLOF MCPTT
D-12110 QoS
4 Manage
ment
LTROF
D-11120 Congesti
3/ on
TDLOF Control
D-12110 for
5 Public
Safety
RRC
and
DRX
Policy
for
Public
Safety

eRAN

nd
RrcCon UlSynTi MOD LBFD-0 RRC Meaning: Indicates the timer used to govern the
nStateTi mer RRCCO 02007 / Connect period in which the eNodeB maintains uplink
mer NNSTA TDLBF ion synchronization for UEs. After this timer expires, the
TETIM D-00200 Manage eNodeB does not send Timing Advance Command to
ER 7 ment the UE. This parameter does not take effect if it is set
LST to 0. That is, the eNodeB will constantly send Timing
RRCCO Advance Command to the UE to maintain uplink
NNSTA synchronization for the UE. If the QciParaEffectFlag
TETIM parameter in the GlobalProcSwitch MO is set to
ER ON(On), the UlSynTimerForQci parameter in the
TDD.
Unit: s
Default Value: 180
CellAlg HighMo MOD TDLOF High- Meaning: Indicates whether to enable the high-
oSwitch biTrigId CELLA D-00110 Mobility mobility-triggered-idle switch. When this parameter is
leMode LGOSW 502 / - set to ENABLE, UEs in high mobility are released
Switch ITCH LOFD-0 Triggere and enter the idle mode, and therefore the signaling
LST 0110502 d Idle impact on the network caused by frequent handovers
CELLA Mode are reduced. When this parameter is set to
LGOSW DISABLED, UEs in high mobility are not released.
ITCH This parameter applies only to LTE FDD and LTE
TDD.
GUI Value Range: DISABLE(Disable),
ENABLE(Enable)
Unit: None
Actual Value Range: DISABLE, ENABLE
Default Value: DISABLE(Disable)
CellUlsc SriFalse MOD None None Meaning: Indicates whether to increase the scheduling
hAlgo DetThd CELLU request indicator (SRI) false detection threshold for
Switch LSCHA UEs in the discontinuous reception (DRX) state. If
LGO this parameter is set to ON, the threshold increases
LST and the SRI false detection probability decreases. If
CELLU this parameter is set to OFF, both the threshold and the
LSCHA probability remain unchanged. This parameter applies
LGO only to LTE FDD and LTE TDD.
Unit: None

eRAN

nd
CellAlg UlSchS MOD LOFD-0 VoIP Meaning:

oSwitch witch CELLA 01016 / Semi- Indicates whether to enable uplink scheduling
LGOSW TDLOF persisten functions for the cell.
ITCH D-00101 t
LST 6 Scheduli SpsSchSwitch: Indicates whether to enable semi-
CELLA LOFD-0 ng persistent scheduling during talk spurts of VoLTE
LGOSW 01048 / TTI services. If this option is selected, semi-persistent
ITCH TDLOF Bundlin scheduling is applied. If this option is deselected,
D-00104 g dynamic scheduling is applied. This option applies
8 only to LTE FDD and LTE TDD.
Dynami
LBFD-0 c SinrAdjustSwitch: Indicates whether to adjust the
0101502 Scheduli measured SINR based on ACK/NACK messages in
/ ng the UL hybrid automatic repeat request (HARQ)
TDLBF Basic processes. This option applies only to LTE FDD and
D-00101 Scheduli LTE TDD.
502 ng PreAllocationSwitch: Indicates whether to enable
LBFD-0 MBR>G preallocation in the uplink. If this option is selected:
02025 / BR (1) If the SmartPreAllocationSwitch option is
TDLBF Configu deselected and a UE is in the discontinuous reception
D-00202 ration (DRX) state, preallocation is disabled for the UE in
5 the uplink; (2) If the SmartPreAllocationSwitch option
UL 2x2
LBFD-0 is deselected and the UE is not in the DRX state,
MU-
70102 / preallocation is enabled for the UE in the uplink; (3) If
MIMO
TDLBF the SmartPreAllocationSwitch option is selected and
D-07010 UL 2x4 the SmartPreAllocationDuration parameter value is
2 MU- greater than 0, smart preallocation is enabled for the
MIMO UE in the uplink; (4) If the SmartPreAllocationSwitch
LOFD-0
AMC option is selected and the SmartPreAllocationDuration
01002
parameter value is 0, preallocation is disabled for the
LOFD-0 Uplink UE in the uplink. If this option is deselected,
01058 / Coverag preallocation is disabled for the UE in the uplink. If
TDLOF e bearer-level preallocation or bearer-level smart
D-00105 Improve preallocation is enabled for a QCI, cell-level
8 ment for preallocation and cell-level smart preallocation do not
Video apply to UEs with the QCI. This option applies only to
LBFD-0
01006 / Enhance LTE FDD and LTE TDD.
TDLBF d UL
Frequen UlVmimoSwitch: Indicates whether to enable multi-
D-00100
cy user MIMO (MU-MIMO) in the uplink. If this option
6
Selectiv is selected, the eNodeB performs MU-MIMO pairing
LOFD-1 e among UEs based on related principles. UEs forming
20205 Scheduli a pair transmit data using the same time-frequency
LBFD-0 ng resources, which improves the system throughput and
60102 spectral efficiency. This option applies only to LTE
UL FDD and LTE TDD.
TDLEO 2x64
FD-121 MU- TtiBundlingSwitch: Indicates whether to enable
608 MIMO transmission time interval (TTI) bundling. If TTI

eRAN

nd
TDLEO UL bundling is enabled, more transmission opportunities

FD-121 4x64 are available to UEs within the delay budget for
609 MU- VoLTE services on the Uu interface, thereby
TDLEO MIMO improving uplink coverage. This option applies only
FD-121 UL to LTE FDD and LTE TDD.
610 8x64 ImIcSwitch: Indicates whether to enable the
MU- intermodulation (IM) interference cancellation for
MIMO UEs. When data is transmitted in both the uplink and
downlink, uplink signals generate two IM components
symmetrically beside the Direct Current (DC)
subcarrier on the downlink receive channel due to the
nonlinearity of the UE receive channel. If this option
is selected, IM component elimination is performed
for UEs. If this option is deselected, IM component
elimination is not performed for UEs. This option
applies only to LTE FDD cells working on frequency
band 20. This option applies only to LTE FDD.
SmartPreAllocationSwitch: Indicates whether to
enable uplink smart preallocation when the
PreAllocationSwitch option is selected. If both the
PreAllocationSwitch and this option are selected and
the SmartPreAllocationDuration parameter in the
CellPreallocGroup MO is set to a value greater than 0,
uplink smart preallocation is enabled. Otherwise,
uplink smart preallocation is disabled. This option
PuschDtxSwitch: Indicates whether the eNodeB uses
the PUSCH discontinuous transmission (DTX)
detection result during uplink scheduling. If this
option is selected for an LTE FDD cell, the eNodeB
determines whether to perform adaptive
retransmission, and also adjusts the CCE aggregation
level of the PDCCH carrying downlink control
information (DCI) format 0 based on the PUSCH
DTX detection result during uplink scheduling. If an
LTE 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(True). Note that the LBBPc
does not support PUSCH DTX detection for VMIMO
UEs. For an LTE TDD cell, this option takes effect
only when the uplink-downlink subframe
configuration is set to SA2 or SA5. If 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

eRAN

nd
support PUSCH DTX detection. This option applies

UlIblerAdjustSwitch: Indicates whether to enable the

uplink IBLER adjustment algorithm. If this option is
selected, the target IBLER is adjusted for UEs based
on the channel quality and fluctuation to increase the
cell throughput. This option applies only to LTE FDD
and LTE TDD. If this option is selected independently
for FDD cells with the UlTargetIBlerAdaptType
option deselected, the algorithm does not take effect.
UlEnhancedFssSwitch: Indicates whether to enable

uplink load-based enhanced frequency selective
scheduling. This option applies only to LTE FDD.
UlIicsAlgoSwitch: Indicates whether to enable the

uplink interference-intensity-based coordinated
scheduling (UL IICS) algorithm. If this option is
selected, interference can be reduced based on
accurate detection of user attributes and scheduling
resource coordination, 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 for live
networks. This option applies only to LTE FDD and
LTE TDD.
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,
ensuring full utilization of the transmit power for all
UEs. If this option is deselected, the uplink scheduler
considers power control restrictions while performing
scheduling. In this case, the transmit power cannot be
fully used for UEs at the cell edge or between the cell

eRAN

nd
edge and cell center. This option applies only to LTE

FDD and LTE TDD.
UlMinGbrSwitch: Indicates whether to ensure 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. This option applies only to LTE FDD
and LTE TDD.
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. This option applies only to LTE
FDD and LTE TDD.
MbrUlSchSwitch: Indicates whether the eNodeB

performs uplink scheduling based on the MBR. If this
option is selected, the eNodeB prioritizes UEs based
on the MBRs during uplink scheduling. This option
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
AMBRs of UEs during uplink scheduling. This option
UlEnhancedDopplerSwitch: Indicates whether to

enable enhanced uplink scheduling based on mobility
speed estimation. If this option is selected, enhanced
uplink scheduling based on mobility speed estimation
is enabled. In enhanced uplink scheduling based on
mobility speed estimation, the eNodeB uses Doppler
measurement results to identify low-speed UEs to
further improve uplink 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(CLASS_1) and the
UlEnhancedDopplerSwitch option is selected. This
option does not apply to cells established on LBBPc
boards. This option applies only to LTE FDD.

eRAN

nd
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. In NB-IoT scenarios with air
interface resource congestion, this option restricts the
number of preambles to perform flow control on UEs
accessing the cell.
UlLast2RetransSchOptSwitch: Indicates whether to
optimize the scheduling policy for the last two
retransmissions. If this option is selected, the
scheduling policy is optimized for the last two
retransmissions. 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, the scheduling
policy is not optimized for the last two
retransmissions. This option applies only to LTE FDD
and LTE TDD.
UlInterfFssSwitch: Indicates whether to enable
interference-based uplink frequency-selective
scheduling. This option applies only to LTE FDD.
UlSmallRBSpectralEffOptSw: Indicates whether to
improve the spectral efficiency of small RBs in the
uplink. If this option is selected, the spectral efficiency
of small RBs in the uplink is optimized, 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 spectral efficiency of small RBs in the uplink is
not optimized. This option applies only to LTE FDD
and LTE TDD.
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
the setting of this option. This option applies only to

eRAN

nd
PuschDtxSchOptSwitch: If this option is selected, the

eNodeB determines whether to perform adaptive
retransmission based on the PUSCH DTX detection
result during uplink scheduling. This option takes
effect only when the uplink-downlink subframe
configuration SA2 or SA5 is used. If an LTE TDD cell
is established on an LBBPc, PUSCH DTX detection is
not supported. This option applies only to LTE TDD.
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.
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
amount adaptation in SR-based scheduling. Data
amount adaptation in SR-based scheduling is enabled
only when this option is selected. This option applies
only to LTE FDD.
UlFssUserThdStSwitch: If this option is selected, the
UE number threshold is optimized for uplink
frequency selective scheduling. If this option is
deselected, the UE number threshold is not optimized
for uplink frequency selective scheduling. This option
HighOrderVMIMOSwitch: Indicates whether to
enable high order VMIMO. If this option is selected,
high order VMIMO is enabled. If this option is
deselected, high order VMIMO is disabled. This
option applies only to LTE TDD.
VMIMOReduceMCSRiseRBSwitch: Indicates
whether VMIMO pairing is performed for UEs whose
MCS index is reduced to increase the number of RBs.
If this option is selected, VMIMO is performed for
UEs whose MCS index is reduced to increase the
number of RBs. If this option is deselected, VMIMO
is not performed for UEs whose MCS index is
reduced to increase the number of RBs. This option
VoLTEUeVmimoSwitch: Indicates whether VMIMO
pairing is performed for VoLTE UEs. If this option is

eRAN

nd
selected, VMIMO pairing is performed for VoLTE

UEs. If this option is deselected, VMIMO pairing is
not performed for VoLTE UEs. This option applies
only to LTE TDD.
TtiBundlingForVideoSwitch: If this option is selected,
TTI bundling is enabled for UEs running video
services in weak coverage areas, improving video
service coverage at the cell edge. If this option is
deselected, TTI bundling is disabled for UEs running
video services in weak coverage areas. This option
GUI Value Range: SpsSchSwitch(SpsSchSwitch),
SinrAdjustSwitch(SinrAdjustSwitch),
PreAllocationSwitch(PreAllocationSwitch),
UlVmimoSwitch(UlVmimoSwitch),
TtiBundlingSwitch(TtiBundlingSwitch),
ImIcSwitch(ImIcSwitch), SmartPreAllocationS-
witch(SmartPreAllocationSwitch),
PuschDtxSwitch(PuschDtxSwitch),
UlIblerAdjustSwitch(UlIblerAdjustSwitch),
UlEnhancedFssSwitch(UlEnhancedFssSwitch),
UlEnhancedSrSchSwitch(UlEnhancedSrSchSwitch),
SchedulerCtrlPowerSwitch(SchedulerCtrlPowerS-
witch), UlIicsAlgoSwitch(UlIicsAlgoSwitch),
UlMinGbrSwitch(UlMinGbrSwitch),
UlMbrCtrlSwitch(UlMbrCtrlSwitch),
MbrUlSchSwitch(MbrUlSchSwitch),
UeAmbrUlSchSwitch(UeAmbrUlSchSwitch),
UlEnhancedDopplerSwitch(UlEnhancedDopplerS-
witch), UlRaUserSchOptSw(UlRaUserSchOptSw),
UlLast2RetransSchOptSwitch(UlLast2RetransSchOpt
Switch), UlInterfFssSwitch(UlInterfFssSwitch),
UlSmallRBSpectralEffOptSw(UlSmallRBSpectralEf-
ficiencyOptSw), PuschUsePucchRbS-
witch(PuschUsePucchRbSwitch), PuschDtxSchOptS-
witch(PuschDtxSchOptSwitch),
ULFSSAlgoSwitch(ULFSSAlgoSwitch),
PrachRbReuseSwitch(PrachRbReuseSwitch),
SrSchDataAdptSw(SrSchDataAdptSw),
UlFssUserThdStSwitch(UlFssUserThdStSwitch),
HighOrderVMIMOSwitch(HighOrderVMIMOS-
witch), VMIMOReduceMCSRiseRBS-
witch(VMIMOReduceMCSRiseRBSwitch),
VoLTEUeVmimoSwitch(VoLTEUeVmimoSwitch),
TtiBundlingForVideoSwitch(TtiBundlingForVideoS-
witch)
Unit: None

eRAN

nd
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, VMIMOReduceMCSRi-
seRBSwitch, VoLTEUeVmimoSwitch,
TtiBundlingForVideoSwitch
Default Value: SpsSchSwitch:Off,
SinrAdjustSwitch:On, PreAllocationSwitch:On,
UlVmimoSwitch:Off, TtiBundlingSwitch:Off,
ImIcSwitch:Off, SmartPreAllocationSwitch:On,
PuschDtxSwitch:On, UlIblerAdjustSwitch:Off,
UlEnhancedFssSwitch:On, UlEnhancedSrSchS-
witch:On, SchedulerCtrlPowerSwitch:Off,
UlIicsAlgoSwitch:Off, UlMinGbrSwitch:Off,
UlMbrCtrlSwitch:Off, MbrUlSchSwitch:Off,
UeAmbrUlSchSwitch:Off, UlEnhancedDopplerS-
witch:On, UlRaUserSchOptSw:Off,
UlLast2RetransSchOptSwitch:On,
UlInterfFssSwitch:Off, UlSmallRBSpectralEf-
fOptSw:Off, PuschUsePucchRbSwitch:Off,
PuschDtxSchOptSwitch:Off, ULFSSAlgoSwitch:On,
PrachRbReuseSwitch:Off, SrSchDataAdptSw:On,
UlFssUserThdStSwitch:Off, HighOrderVMIMOS-
witch:Off, VMIMOReduceMCSRiseRBSwitch:Off,
VoLTEUeVmimoSwitch:Off, TtiBundlingForVideoS-
witch:Off

eRAN

nd
CellDlsc DlSpsInt MOD LOFD-0 VoIP Meaning:

hAlgo erval CELLD 01016 / Semi- Indicates the downlink semi-persistent scheduling
LSCHA TDLOF persisten interval. This parameter provides three values. If this
LGO D-00101 t parameter is set to ms20(20ms) or ms40(40ms), a
LST 6 Scheduli fixed interval of 20 or 40 ms is used. If this parameter
CELLD ng is set to ADAPTIVE, the eNodeB adaptively uses the
LSCHA interval of 20 or 40 ms. The value ADAPTIVE takes
LGO effect only for TDD eNodeBs.
FDD eNodeBs support a fixed interval of 20 or 40 ms.
If this parameter is set to ADAPTIVE for FDD
eNodeBs, the actually effective value is ms20(20ms).
TDD.
GUI Value Range: ms20(20ms), ms40(40ms),
ADAPTIVE(ADAPTIVE)
Unit: None
Actual Value Range: ms20, ms40, ADAPTIVE
Default Value: ms20(20ms)

eRAN

nd
CellCqi CqiOptS MOD LBFD-0 CQI Meaning:

AdjAlgo witch CELLC 0101501 Adjustm Indicates whether to enable optimization algorithms
QIADJ / ent for CQI transmission on the PUCCH and PUSCH.
ALGO TDLBF
LST D-00101 PUSCH_CQI_FALSE_DETECTION_SW: Indicates
CELLC 501 whether to enable the algorithm of counteracting false
QIADJ detection of CQIs on the PUSCH. The algorithm
ALGO effectively reduces the probability of false CQI
detection. False CQI detection occurs if a UE does not
report a CQI but the eNodeB detects a CQI from the
UE. The algorithm is enabled only if this option is
selected. This option applies only to LTE FDD and
LTE TDD.
PUCCH_CQI_FALSE_DETECTION_SW: Indicates
whether to enable the algorithm of counteracting false
detection of CQIs on the PUCCH. The algorithm is
enabled only if this option is selected. This option
GUI Value Range:
PUSCH_CQI_FALSE_DETECTION_SW(PUSCH_C
QI_FALSE_DETECTION_SW),
PUCCH_CQI_FALSE_DETECTION_SW(PUCCH_
CQI_FALSE_DETECTION_SW)
Unit: None
Actual Value Range:
PUSCH_CQI_FALSE_DETECTION_SW,
PUCCH_CQI_FALSE_DETECTION_SW
Default Value:
PUSCH_CQI_FALSE_DETECTION_SW:Off,
PUCCH_CQI_FALSE_DETECTION_SW:Off

eRAN

nd
TimeAli Timing MOD TDLOF RRC Meaning:

gnment AdvCm TATIM D-12110 and Indicates whether optimization of the mechanism for
Timer dOptSwi ER 5 DRX delivering the uplink time alignment command takes
tch LST Policy effect. If the optimization takes effect, the number of
TATIM for unnecessary uplink time alignment commands
ER Public delivered to motionless or low-mobility UEs can be
Safety 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 TimeAlignmentTim-
er 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. This
Unit: None

eRAN

nd
TimeAli Timing MOD LBFD-0 Uplink Meaning: Indicates the method of measuring uplink
gnment MeasMo TATIM 70101 Timing timing offsets. If this parameter is set to INVALID,
Timer de ER Based uplink timing offsets are measured based on the
LST on demodulation reference signal (DMRS) for PUSCH or
TATIM PUCCH sounding reference signal (SRS). If this parameter is
ER 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. This
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)

eRAN

nd
RlcPdcp Discard ADD LBFD-0 Radio Meaning: Indicates the length of the PDCP discard
ParaGro Timer RLCPD 02008 / Bearer timer. This parameter applies only to LTE FDD and
up CPPAR TDLBF Manage LTE TDD.
AGROU D-00200 ment GUI Value Range: DiscardTimer_50(50),
P 8 VoLTE DiscardTimer_100(100), DiscardTimer_150(150),
MOD LOFD-1 Coverag DiscardTimer_300(300), DiscardTimer_500(500),
RLCPD 20204 e DiscardTimer_750(750), DiscardTimer_1500(1500),
CPPAR TDLOF Enhance DiscardTimer_Infinity(infinity)
AGROU D-12020 ment Unit: ms
P 3 Based
on Actual Value Range: DiscardTimer_50,
LST TDLOF DiscardTimer_100, DiscardTimer_150,
RLCPD Extende
D-12110 d Delay DiscardTimer_300, DiscardTimer_500,
CPPAR 5 DiscardTimer_750, DiscardTimer_1500,
AGROU Budget
MLOFD DiscardTimer_Infinity
P Deep
-121280 Coverag Default Value: DiscardTimer_Infinity(infinity)
/ e
TDLEO Improve
FD-121 ment for
611 VoLTE
RRC
and
DRX
Policy
for
Public
Safety
eMTC
Introduc
tion

eRAN

nd
CellDrx DrxRcv MOD LBFD-0 DRX Meaning:

Para DtxProS CELLD 02017 Indicates whether to enable UEs to enter the DRX
witch RXPAR sleep time after two consecutive discontinuous
A transmissions (DTXs) are detected. Consider that this
LST parameter is set to ON and DRX is enabled for a UE
CELLD in common scenarios. After detecting two consecutive
RXPAR DTXs, the eNodeB determines whether to enable the
A UE to enter the DRX sleep time based on the stop
time of the DRXInactivityTimer timer instead of
promptly enabling the UE to enter the DRX sleep
time. If the eNodeB detects the two consecutive DTXs
after the DRXInactivityTimer timer stops, the UE
enters the DRX sleep time. If the eNodeB detects the
two consecutive DTXs when or before the
DRXInactivityTimer timer stops, the UE does not
enter the DRX sleep time.
If this parameter is set to ON and DRX is enabled for
a UE in carrier aggregation (CA) scenarios, the
eNodeB determines whether two consecutive DTXs
occur on both the primary component carrier (PCC)
and the secondary component carrier (SCC). If two
consecutive DTXs occur, the eNodeB determines
whether the UE enters the DRX sleep time based on
conditions in common scenarios. In CA scenarios, the
setting of this parameter in the PCell and the SCell
must be the same. This parameter applies only to LTE
FDD and LTE TDD.
Unit: None
CellDrx LocalCe LST None None Meaning: Indicates the local ID of the cell. It uniquely
Para llId CELLD identifies a cell within a BS.
RXPAR GUI Value Range: 0~255
A
Unit: None
MOD
CELLD Actual Value Range: 0~255
RXPAR Default Value: None
A

eRAN

nd
CellDrx DrxStart MOD LBFD-0 DRX Meaning: Indicates whether to enable optimized
Para OffsetO CELLD 02017 random distribution of DrxStartOffset values for UEs
ptSwitch RXPAR that are configured with only sounding reference
A signal (SRS) resources, or periodic channel quality
LST indicator (CQI), or neither. If this parameter is set to
CELLD OFF, then DrxStartOffset takes the value of SrsOffset,
RXPAR CqiOffset, or 0 when a UE is configured with only
A SRS resources, or periodic CQI, or neither,
respectively. This prevents DrxStartOffset values from
being randomly distributed within the range of 0 to
(LongDrxCycle - 1). If this parameter is set to ON,
DrxStartOffset values can be randomly distributed
within the range of 0 to (LongDrxCycle - 1) for UEs
that are configured with only SRS resources, or
periodic CQI, or neither. This parameter applies only
to LTE FDD eNodeBs and is recommended to be set
to ON when SRS resources are not allocated for UEs
or there is a large number of UEs in the cell.This
parameter applies only to LTE FDD.
Unit: None
DrxPara DrxPara ADD LBFD-0 DRX Meaning: Indicates the ID of the DRX parameter
Group GroupId DRXPA 02017 / group. This parameter applies only to LTE FDD and
RAGRO TDLBF LTE TDD.
UP D-00201 GUI Value Range: 0~49
LST 7
Unit: None
DRXPA
RAGRO Actual Value Range: 0~49
UP Default Value: None
MOD
DRXPA
RAGRO
UP
RMV
DRXPA
RAGRO
UP

eRAN

nd
DrxPara CatType ADD LBFD-0 DRX Meaning: Indicates the UE category type. Other
Group DRXPA 02017 / eMTC parameters in this MO apply to LTE UEs, eMTC UEs
RAGRO TDLBF Introduc in mode A, and eMTC UEs in mode B if this
UP D-00201 tion parameter is set to LTE, EMTC_MODE_A, and
MOD 7 EMTC_MODE_B, respectively. This parameter
DRXPA MLOFD applies only to LTE FDD and LTE TDD.
RAGRO -121280 GUI Value Range: LTE(LTE),
UP / EMTC_MODE_A(EMTC_MODE_A),
LST TDLEO EMTC_MODE_B(EMTC_MODE_B)
DRXPA FD-121 Unit: None
RAGRO 611
Actual Value Range: LTE, EMTC_MODE_A,
UP EMTC_MODE_B
Default Value: LTE(LTE)
TimeAli TimeAli MOD LBFD-0 RRC Meaning: Indicates the length of the uplink time
gnment gnment TATIM 02007 Connect alignment timer for UEs in the cell. A UE is
Timer Timer ER TDLBF ion considered not time-aligned in the uplink if the timer
LST D-00201 Manage expires. This parameter applies only to LTE FDD and
TATIM 7 ment LTE TDD.
ER LEOFD- DRX GUI Value Range: SF500(500 subframes), SF750(750
111306 / Breathin subframes), SF1280(1280 subframes), SF1920(1920
TDLOF g Pilot subframes), SF2560(2560 subframes), SF5120(5120
D-12020 subframes), SF10240(10240 subframes),
RRC INFINITY(Infinity)
5 and
TDLOF DRX Unit: None
D-12110 Policy Actual Value Range: SF500, SF750, SF1280, SF1920,
5 for SF2560, SF5120, SF10240, INFINITY
Public Default Value: INFINITY(Infinity)
Safety
CellQci LocalCe ADD LBFD-0 Extende Meaning: Indicates the local ID of a cell. It uniquely
Para llId CELLQ 02032 d-QCI identifies a cell within an eNodeB. This parameter
CIPAR LTROF MCPTT applies only to LTE FDD and LTE TDD.
A D-11120 QoS GUI Value Range: 0~255
LST 1 Manage Unit: None
CELLQ ment
CIPAR Actual Value Range: 0~255
A Default Value: None
MOD
CELLQ
CIPAR
A
RMV
CELLQ
CIPAR
A

eRAN

nd
CellQci Qci ADD LBFD-0 Basic Meaning: Indicates the QoS class identifier (QCI),
Para CELLQ 02025 / Scheduli which is an attribute of evolved packet system (EPS)
CIPAR TDLBF ng bearers. Different QCIs indicate different QoS
A D-00202 Dynami requirements, such as the packet delay budget, packet
LST 5 c loss rate (PLR) and packet error rate (PER), and
CELLQ LBFD-0 Scheduli resource type (whether the service is a GBR service or
CIPAR 0101502 ng not). For details, see Table 6.1.7 in 3GPP TS 23.203.
A / This parameter applies only to LTE FDD and LTE
TDLBF TDD.
MOD
CELLQ D-00101 GUI Value Range:
CIPAR 502 1,2,3,4,5,6,7,8,9,10~64,65,66,67~68,69,70,71~254
A Unit: None
RMV Actual Value Range:
CELLQ 1,2,3,4,5,6,7,8,9,10~64,65,66,67~68,69,70,71~254
CIPAR Default Value: None
A
CellQci QciPrior ADD LBFD-0 DRX Meaning: Indicates the QCI-specific priority for
Para ityForDr CELLQ 02017 / RRC selecting a DRX parameter group. A larger value of
x CIPAR TDLBF and this parameter indicates a lower priority. If the bearers
A D-00201 DRX for a UE have multiple QCIs and the DrxPolicyMode
MOD 7 Policy parameter is set to QCIPRIORITY(QCI priority), the
CELLQ TDLOF for eNodeB selects the DRX parameter group for the UE
CIPAR D-12110 Public based on the QCI-specific priorities. This parameter
A 5 Safety applies only to LTE FDD and LTE TDD.
LST GUI Value Range: 1~254
CELLQ Unit: None
CIPAR Actual Value Range: 1~254
A
Default Value: 9
CellStan LocalCe LST None None Meaning: Indicates the local ID of the cell. It uniquely
dardQci llId CELLS identifies a cell within an eNodeB. This parameter
TANDA applies only to LTE FDD and LTE TDD.
RDQCI GUI Value Range: 0~255
MOD Unit: None
CELLS
TANDA Actual Value Range: 0~255
RDQCI Default Value: None

eRAN

nd
CellStan Qci LST LBFD-0 Basic Meaning: Indicates the QoS class identifier (QCI) of
dardQci CELLS 02025 / Scheduli an evolved packet system (EPS) bearer. Different
TANDA TDLBF ng QCIs indicate different QoS requirements, such as the
RDQCI D-00202 Dynami packet delay budget, packet loss rate (PLR) and
MOD 5 c packet error rate (PER), and resource type (whether
CELLS LBFD-0 Scheduli the service is a GBR service or not). For details, see
TANDA 0101502 ng Table 6.1.7 in 3GPP TS 23.203. This parameter
RDQCI / applies only to LTE FDD and LTE TDD.
TDLBF GUI Value Range: QCI1(QCI 1), QCI2(QCI 2),
D-00101 QCI3(QCI 3), QCI4(QCI 4), QCI5(QCI 5), QCI6(QCI
502 6), QCI7(QCI 7), QCI8(QCI 8), QCI9(QCI 9)
Unit: None
Actual Value Range: QCI1, QCI2, QCI3, QCI4, QCI5,
QCI6, QCI7, QCI8, QCI9
Default Value: None
CellStan DrxPara MOD LBFD-0 DRX Meaning: Indicates the ID of a DRX parameter group.
dardQci GroupId CELLS 02017 / This parameter applies only to LTE FDD and LTE
TANDA TDLBF TDD.
RDQCI D-00201 GUI Value Range: 0~9
LST 7
Unit: None
CELLS
TANDA Actual Value Range: 0~9
RDQCI Default Value: 0
CellStan QciPrior MOD LBFD-0 DRX Meaning: Indicates the QCI-specific priority for
dardQci ityForDr CELLS 02017 / selecting a DRX parameter group. A larger value of
x TANDA TDLBF this parameter indicates a lower priority. If the bearers
RDQCI D-00201 for a UE have multiple QCIs and the DrxPolicyMode
LST 7 parameter is set to QCIPRIORITY(QCI priority), the
CELLS eNodeB selects the DRX parameter group for the UE
TANDA based on the QCI-specific priorities. This parameter
RDQCI applies only to LTE FDD and LTE TDD.
Unit: None
Default Value: 9

eRAN

nd
CellExte Extende ADD LBFD-0 Extende Meaning: Indicates the extended QoS class identifier
ndedQci dQci CELLE 02032 / d-QCI (QCI), which is required by the operator for service
XTEND TDLBF differentiation. This parameter applies only to LTE
EDQCI D-00203 FDD and LTE TDD.
LST 2 GUI Value Range: 10~254
CELLE Unit: None
XTEND
EDQCI Actual Value Range: 10~254
MOD Default Value: None

CELLE
XTEND
EDQCI
RMV
CELLE
XTEND
EDQCI
CellExte LocalCe ADD None None Meaning: Indicates the local ID of the cell. It uniquely
ndedQci llId CELLE identifies a cell within an eNodeB. This parameter
XTEND applies only to LTE FDD and LTE TDD.
EDQCI GUI Value Range: 0~255
LST Unit: None
CELLE
XTEND Actual Value Range: 0~255
EDQCI Default Value: None
MOD
CELLE
XTEND
EDQCI
RMV
CELLE
XTEND
EDQCI

eRAN

nd
Extende Service ADD LBFD-0 Dynami Meaning: Indicates the service type corresponding to
dQci Type EXTEN 0101502 c the extended QCI. This extended QCI inherits
DEDQC / Scheduli configurations from the corresponding standardized
I TDLBF ng QCI. If this parameter is set to IMSSignalling,
MOD D-00101 configurations of QCI 5 are inherited. If this
EXTEN 502 parameter is set to LowDelay, configurations of QCI 7
DEDQC are inherited. If this parameter is set to
I TCPorBuffStreaming, configurations of QCI 9 are
inherited. This parameter applies only to LTE FDD
LST and LTE TDD.
EXTEN
DEDQC GUI Value Range: IMSSignalling(IMS Signalling),
I LowDelay(Low Delay), TCPorBuffStreaming(TCP
Based or Buffered Streaming), CBTC(CBTC)
Unit: None
Actual Value Range: IMSSignalling, LowDelay,
TCPorBuffStreaming, CBTC
Default Value: TCPorBuffStreaming(TCP Based or
Buffered Streaming)
CellDrx LongDr MOD LOFD-0 Ultra- Meaning: Indicates the length of the long DRX cycle
Para xCycleF CELLD 81283 / Flash dedicated to GERAN measurement. This parameter
orMeas RXPAR TDLOF CS applies only to LTE FDD and LTE TDD.
A D-08120 Fallback GUI Value Range: SF128(128 subframes), SF160(160
LST 3 to subframes), SF256(256 subframes), SF320(320
CELLD TDLBF GERAN subframes), SF512(512 subframes), SF640(640
RXPAR D-00201 DRX subframes), SF1024(1024 subframes), SF1280(1280
A 7 subframes), SF2048(2048 subframes), SF2560(2560
subframes)
Unit: subframe
SF512, SF640, SF1024, SF1280, SF2048, SF2560

eRAN

nd
CellDrx OnDurT MOD LOFD-0 Ultra- Meaning: Indicates the length of the On Duration
Para imerFor CELLD 81283 / Flash Timer dedicated to GERAN measurement. This
Meas RXPAR TDLOF CS parameter applies only to LTE FDD and LTE TDD.
A D-08120 Fallback GUI Value Range: PSF1(1 PDCCH subframe),
LST 3 to PSF2(2 PDCCH subframes), PSF3(3 PDCCH
CELLD TDLBF GERAN subframes), PSF4(4 PDCCH subframes), PSF5(5
RXPAR D-00201 DRX PDCCH subframes), PSF6(6 PDCCH subframes),
A 7 PSF8(8 PDCCH subframes), PSF10(10 PDCCH
PDCCH subframes)
Unit: subframe
CellDrx DrxInact MOD LOFD-0 Ultra- Meaning: Indicates the length of the DRX Inactivity
Para TimerFo CELLD 81283 / Flash Timer dedicated to GERAN measurement. This
rMeas RXPAR TDLOF CS parameter applies only to LTE FDD and LTE TDD.
A D-08120 Fallback GUI Value Range: PSF1(1 PDCCH subframe),
LST 3 to PSF2(2 PDCCH subframes), PSF3(3 PDCCH
CELLD TDLBF GERAN subframes), PSF4(4 PDCCH subframes), PSF5(5
RXPAR D-00201 DRX PDCCH subframes), PSF6(6 PDCCH subframes),
A 7 PSF8(8 PDCCH subframes), PSF10(10 PDCCH
Unit: subframe
PSF750, PSF1280, PSF1920, PSF2560

eRAN

nd
CellDrx DrxReT MOD LOFD-0 Ultra- Meaning: Indicates the length of the DRX
Para xTimerF CELLD 81283 / Flash Retransmission Timer dedicated to GERAN
orMeas RXPAR TDLOF CS measurement. This parameter applies only to LTE
A D-08120 Fallback FDD and LTE TDD.
LST 3 to GUI Value Range: PSF1(1 PDCCH subframes),
CELLD TDLBF GERAN PSF2(2 PDCCH subframes), PSF4(4 PDCCH
RXPAR D-00201 DRX subframes), PSF6(6 PDCCH subframes), PSF8(8
A 7 PDCCH subframes), PSF16(16 PDCCH subframes),
subframes)
Unit: subframe
PSF16, PSF24, PSF33
CellDrx ShortDr MOD LOFD-0 Ultra- Meaning: Indicates whether to enable the short DRX
Para xSwFor CELLD 81283 / Flash cycle dedicated to GERAN measurement. This
Meas RXPAR TDLOF CS parameter applies only to LTE FDD and LTE TDD.
A D-08120 Fallback GUI Value Range: OFF(Off), ON(On)
LST 3 to
GERAN Unit: None
CELLD TDLBF
RXPAR D-00201 DRX Actual Value Range: OFF, ON
A 7 Default Value: OFF(Off)
CellDrx ShortDr MOD LOFD-0 Ultra- Meaning: Indicates the length of the short DRX cycle
Para xCycleF CELLD 81283 / Flash dedicated to GERAN measurement. This parameter
orMeas RXPAR TDLOF CS applies only to LTE FDD and LTE TDD.
A D-08120 Fallback GUI Value Range: SF2(2 subframes), SF5(5
LST 3 to subframes), SF8(8 subframes), SF10(10 subframes),
CELLD TDLBF GERAN SF16(16 subframes), SF20(20 subframes), SF32(32
RXPAR D-00201 DRX subframes), SF40(40 subframes), SF64(64
A 7 subframes), SF80(80 subframes), SF128(128
Unit: subframe
SF20, SF32, SF40, SF64, SF80, SF128, SF160,
SF256, SF320, SF512, SF640

eRAN

nd
CellDrx ShortCy MOD LOFD-0 Ultra- Meaning: Indicates the length of the DRX Short Cycle
Para cleTime CELLD 81283 / Flash Timer dedicated to GERAN measurement. This
rForMea RXPAR TDLOF CS parameter applies only to LTE FDD and LTE TDD.
s A D-08120 Fallback GUI Value Range: 1~16
LST 3 to
GERAN Unit: None
CELLD TDLBF
RXPAR D-00201 DRX Actual Value Range: 1~16
A 7 Default Value: 1

eRAN

nd
ENodeB HoCom MOD LBFD-0 Coverag Meaning:

AlgoSwi mOptSw ENODE 0201802 e Based Indicates whether to enable optimization on handover-
tch itch BALGO / Inter- related common configurations and algorithms.
SWITC TDLBF frequenc
H D-00201 y BasedSriGapOptSwitch: Indicates whether to consider
LST 802 Handov the transmission of SRIs when configuring
ENODE LOFD-0 er measurement gaps for UEs in non-DRX mode. The
BALGO 01019 / PS Inter- eNodeB considers the collaboration only if this option
SWITC TDLOF RAT is selected. This option applies only to LTE FDD and
H D-00101 Mobility LTE TDD.
9 between L2UBasedHoPolicyPenaltySwitch: Indicates whether
LOFD-0 E- to differentiate between PS HO and SRVCC for
01020 / UTRAN penalty and retry after E-UTRAN-to-UTRAN
TDLOF and operation failures (which may be admission failures
D-00102 UTRAN due to non-resource reasons or handover failures after
0 PS Inter- handover command delivery). The eNodeB
LBFD-0 RAT differentiates between PS HO and SRVCC for penalty
0201804 Mobility and retry only if this option is selected. This option
/ between applies only to LTE FDD and LTE TDD.
TDLBF E-
UTRAN DrxBasedSriGapOptSwitch: Indicates whether to
D-00201 consider the transmission of SRIs when configuring
804 and
GERAN measurement gaps for UEs in DRX mode. The
LBFD-0 eNodeB considers the collaboration only if this option
0201805 Distance is selected. This option applies only to LTE FDD and
/ Based LTE TDD.
TDLBF Inter-
D-00201 frequenc LaiCsfbBlindNCellSelSwitch: Indicates the policy of
805 y determining a target cell for LAI-based CSFB in a
Handov blind manner (not based on measurements). If this
LOFD-0 er option is selected, the eNodeB preferentially selects
01033 / the neighboring cell with the highest blind handover
TDLOF Service
Based priority; if multiple cells have the same priority, the
D-00103 eNodeB selects a cell with the same LAC as the
3 Inter-
frequenc source cell. If this option is deselected, the eNodeB
LOFD-0 y preferentially selects the neighboring cell with the
01034 / Handov same LAC as the source cell; if multiple cells have the
TDLOF er same LAC, the eNodeB selects a cell with the highest
D-00103 blind handover priority. This option applies only to
4 CS LTE FDD and LTE TDD.
Fallback
to TrigQuanBothMeasOptSw: Indicates whether to
UTRAN independently enable RSRP- and RSRQ-based inter-
CS frequency or inter-RAT measurements when both
Fallback inter-frequency and inter-RAT A1/A2 measurements
to are enabled. If this option is selected, the eNodeB
GERAN starts RSRP-based inter-frequency or inter-RAT
measurements after receiving RSRP-triggered event
A2 and starts RSRQ-based inter-frequency or inter-

eRAN

nd
RAT measurements after receiving RSRQ-triggered

event A2. If this option is deselected, the eNodeB
starts only one type of measurement. That is, the
eNodeB starts only RSRP-based inter-frequency or
inter-RAT measurements if it receives RSRP-triggered
event A2 first and the same rules applies to RSRQ.
GapCfgOptSwitch: Indicates whether to adopt the
optimized gap configuration mode. If this option is
selected, optimized gap configuration mode is used,
without affecting by the settings of the
BasedSriGapOptSwitch and DrxBasedSriGapOptS-
witch options. If this option is deselected, optimized
gap configuration mode is not used. The
BasedSriGapOptSwitch and DrxBasedSriGapOptS-
witch options can take effect. This option applies only
GUI Value Range: BasedSriGapOptS-
witch(BasedSriGapOptSwitch),
L2UBasedHoPolicyPenalty-
Switch(L2UBasedHoPolicyPenaltySwitch),
DrxBasedSriGapOptSwitch(DrxBasedSriGapOptS-
witch), LaiCsfbBlindNCellSelS-
witch(LaiCsfbBlindNCellSelSwitch),
TrigQuanBothMeasOptSw(TrigQuanBothMea-
sOptSw), GapCfgOptSwitch(GapCfgOptSwitch)
Unit: None
Actual Value Range: BasedSriGapOptSwitch,
L2UBasedHoPolicyPenaltySwitch,
DrxBasedSriGapOptSwitch, LaiCsfbBlindNCellSelS-
witch, TrigQuanBothMeasOptSw, GapCfgOptSwitch
Default Value: BasedSriGapOptSwitch:On,
L2UBasedHoPolicyPenaltySwitch:Off,
DrxBasedSriGapOptSwitch:On, LaiCsfbBlindNCell-
SelSwitch:Off, TrigQuanBothMeasOptSw:Off,
GapCfgOptSwitch:Off

eRAN

nd
CellAcc ReptSyn MOD LOFD-0 Dynami Meaning: Indicates whether all synchronization
ess cAvoidI CELLA 01105 / c DRX procedures repeatedly initiated by a UE having
nd CCESS TDLOF compatibility problems can trigger the RRC
LST D-00110 connection reconfiguration procedure. If this
CELLA 5 parameter is set to CFG, all synchronization
CCESS procedures repeatedly initiated by a UE having
compatibility problems do not trigger the RRC
connection reconfiguration procedure. If this
parameter is set to NOT_CFG, all synchronization
procedures repeatedly initiated by a UE having
compatibility problems trigger the RRC connection
reconfiguration procedure. This parameter applies
GUI Value Range: NOT_CFG(Not configure),
CFG(Configure)
Unit: None
Actual Value Range: NOT_CFG, CFG
Default Value: NOT_CFG(Not configure)
CellAcc ReptSyn MOD LOFD-0 Dynami Meaning: Indicates the period during which
ess cAvoidT CELLA 01105 / c DRX synchronization procedures repeatedly initiated by a
ime CCESS TDLOF UE having compatibility problems trigger only one
LST D-00110 RRC connection reconfiguration procedure. This
CELLA 5 parameter applies only to LTE FDD and LTE TDD.
CCESS GUI Value Range: 1~1000
Unit: ms
Default Value: 100

eRAN

nd
QciPara UlSynTi ADD LBFD-0 RRC Meaning: Indicates the timer used to govern the
merFor QCIPA 02007 / Connect period in which the eNodeB maintains uplink
Qci RA TDLBF ion synchronization for UEs that have bearers of a QCI.
MOD D-00200 Manage After this timer expires, the eNodeB does not send the
QCIPA 7 ment Timing Advance Command to the UE. This parameter
RA LOFD-0 Enhance does not take effect when set to 0. That is, the eNodeB
81218 d will constantly send the Timing Advance Command to
LST the UE to maintain uplink synchronization for the UE.
QCIPA TDLOF Extende
d QCI If a UE has bearers of several QCIs, the eNodeB
RA D-11023 selects the longest uplink synchronization timer of
0 Enhance bearers with the highest QCI-specific priority
LTROF d QoS specified by the UeInactiveTimerPri parameter as the
D-11120 for uplink synchronization timer for the UE. This
1/ MCPTT parameter applies only to LTE FDD and LTE TDD.
TDLOF (Trial)
D-12110 MCPTT
3 QoS Unit: s
TDLOF Manage Actual Value Range: 0~3600
D-12110 ment Default Value: 180
5 RRC
and
DRX
Policy
for
Public
Safety
CellAlg LocalCe DSP None None Meaning: Indicates the local ID of the cell. It uniquely
oSwitch llId CELLU identifies a cell within an eNodeB.
LCAMC GUI Value Range: 0~255
CLUST
ER Unit: None
DSP Actual Value Range: 0~255

CELLU Default Value: None
LICSST
ATUS
LST
CELLA
LGOSW
ITCH
MOD
CELLA
LGOSW
ITCH

eRAN
DRX and Signaling Control Feature Parameter Description 8 Counters
8 Counters
Table 8-1 Counters

Counter ID Counter Name Counter Feature ID Feature Name
Description
1526726658 L.RRC.ConnReq.At Number of RRC Multi-mode: None RRC Connection

t connection setup GSM: None Management
requests RRC Connection
(retransmission UMTS: None
Management
excluded) LTE:
LBFD-002007
TDLBFD-002007
1526726885 L.Paging.UU.Att Number of UEs Multi-mode: None Paging

contained in paging GSM: None Paging
messages
transmitted over the UMTS: None Dynamic DRX
Uu interface in a LTE: LBFD-002011
cell TDLBFD-002011
LOFD-00110501
1526726996 L.HHO.IntraeNB.In Number of intra- Multi-mode: None Coverage Based

traFreq.ExecAttOut eNodeB intra- GSM: None Intra-frequency
frequency outgoing Handover
handovers UMTS: None
Coverage Based
executions in a cell LTE: Intra-frequency
LBFD-00201801 Handover
TDLBFD-0020180
1

eRAN

Description
1526726999 L.HHO.IntraeNB.In Number of intra- Multi-mode: None Coverage Based

terFreq.ExecAttOut eNodeB inter- GSM: None Inter-frequency
Coverage Based
executions in a cell LTE: Inter-frequency
TDLBFD-0020180 Distance Based
2 Inter-frequency
4 Inter-frequency
TDLBFD-0020180 Service Based Inter-
5 frequency
Handover
Service Based Inter-
frequency
Handover
1526727002 L.HHO.IntereNB.In Number of inter- Multi-mode: None Coverage Based

traFreq.ExecAttOut eNodeB intra- GSM: None Intra-frequency
Coverage Based
executions in a cell LTE: Intra-frequency
TDLBFD-0020180
1
1526727005 L.HHO.IntereNB.In Number of inter- Multi-mode: None Coverage Based

terFreq.ExecAttOut eNodeB inter- GSM: None Inter-frequency
Coverage Based
executions in a cell LTE: Inter-frequency
2 Inter-frequency
4 Inter-frequency
TDLBFD-0020180 Service Based Inter-
5 frequency
Handover
Service Based Inter-
frequency
Handover

eRAN

Description
1526727285 L.HHO.DRX.Intrae Number of intra- Multi-mode: None DRX

NB.IntraFreq.Exec eNodeB intra- GSM: None Coverage Based
AttOut frequency outgoing Intra-frequency
Handover
executions in the LTE:
DRX state LBFD-002017 DRX
LBFD-00201801 Coverage Based
Intra-frequency
TDLBFD-002017 Handover
TDLBFD-0020180
1
1526727286 L.HHO.DRX.Intrae Number of Multi-mode: None DRX

NB.IntraFreq.Exec successful intra- GSM: None Coverage Based
SuccOut eNodeB intra- Intra-frequency
frequency outgoing UMTS: None
Handover
handovers in the LTE:
Intra-frequency
TDLBFD-0020180
1

NB.InterFreq.Exec eNodeB inter- GSM: None Coverage Based
AttOut frequency outgoing Inter-frequency
Handover
Inter-frequency
TDLBFD-0020180
2

NB.InterFreq.Exec successful intra- GSM: None Coverage Based
SuccOut eNodeB inter- Inter-frequency
Handover
Inter-frequency
TDLBFD-0020180
2

eRAN

Description
1526727289 L.HHO.DRX.Intere Number of inter- Multi-mode: None Coverage Based

NB.IntraFreq.Exec eNodeB intra- GSM: None Intra-frequency
AttOut frequency outgoing Handover
DRX
DRX state LBFD-00201801 Coverage Based
Intra-frequency
TDLBFD-0020180
1
1526727290 L.HHO.DRX.Intere Number of Multi-mode: None Coverage Based

NB.IntraFreq.Exec successful inter- GSM: None Intra-frequency
SuccOut eNodeB intra- Handover
DRX
Intra-frequency
TDLBFD-0020180
1
1526727291 L.HHO.DRX.Intere Number of inter- Multi-mode: None Coverage Based

NB.InterFreq.Exec eNodeB inter- GSM: None Inter-frequency
AttOut frequency outgoing Handover
DRX
Inter-frequency
TDLBFD-0020180
2
1526727292 L.HHO.DRX.Intere Number of Multi-mode: None Coverage Based

NB.InterFreq.Exec successful inter- GSM: None Inter-frequency
SuccOut eNodeB inter- Handover
DRX
Inter-frequency
TDLBFD-0020180
2
1526727544 L.E-RAB.SuccEst Total number of Multi-mode: None Radio Bearer

successful E-RAB GSM: None Management
setups initiated by Radio Bearer
UEs in a cell UMTS: None
Management
LTE:
LBFD-002008
TDLBFD-002008

eRAN

Description
1526727545 L.E-RAB.AttEst Total number of E- Multi-mode: None Radio Bearer

RAB setup attempts GSM: None Management
initiated by UEs in Radio Bearer
a cell UMTS: None
Management
LTE:
LBFD-002008 Dynamic DRX
TDLBFD-002008
LOFD-00110501
1526727546 L.E- Total number of Multi-mode: None Radio Bearer

RAB.AbnormRel abnormal releases GSM: None Management
of activated E- Radio Bearer
RABs initiated by UMTS: None
Management
the eNodeB LTE:
LBFD-002008
TDLBFD-002008
1526727547 L.E-RAB.NormRel Total number of Multi-mode: None Radio Bearer

normal E-RAB GSM: None Management
releases initiated by Radio Bearer
the eNodeB in a UMTS: None
Management
cell LTE:
LBFD-002008
TDLBFD-002008

t.Emc connection setup GSM: None Management
attempts with a RRC Connection
cause value of UMTS: None
Management
emergency LTE:
TDLBFD-002007
LOFD-00110501

t.HighPri connection setup GSM: None Management
Management
highPriorityAccess LTE:
TDLBFD-002007
LOFD-00110501

eRAN

Description

t.Mt connection setup GSM: None Management
cause value of mt- UMTS: None
Management
Access LTE:
TDLBFD-002007
LOFD-00110501

t.MoSig connection setup GSM: None Management
cause value of mo- UMTS: None
Management
Signalling LTE:
TDLBFD-002007
LOFD-00110501

t.MoData connection setup GSM: None Management
cause value of mo- UMTS: None
Management
Data LTE:
TDLBFD-002007
LOFD-00110501
1526728222 L.RRC.ConnReq.S Number of RRC Multi-mode: None RRC Connection

ucc.Emc Connection Setup GSM: None Management
Complete messages RRC Connection
with a cause value UMTS: None
Management
of emergency LTE:
received from UEs LBFD-002007
in a cell TDLBFD-002007

ucc.HighPri Connection Setup GSM: None Management
Management
of LTE:
highPriorityAccess LBFD-002007
received from UEs TDLBFD-002007
in a cell

eRAN

Description

ucc.Mt Connection Setup GSM: None Management
Management
of mt-Access LTE:

ucc.MoData Connection Setup GSM: None Management
Management
of mo-Data LTE:

t.DelayTol connection setup GSM: None Management
Management
delayTolerantAc- LTE:
cess-v1020 LBFD-002007 Dynamic DRX
TDLBFD-002007
LOFD-00110501
1526728358 L.RRC.ConnReq.S Number of Multi-mode: None RRC Connection

ucc.DelayTol successful RRC GSM: None Management
connection setups RRC Connection
Management
of delayTolerantAc- LTE:
cess-v1020 LBFD-002007
TDLBFD-002007
1526728436 L.E- Number of released Multi-mode: None Radio Bearer

RAB.Release.Unsy E-RABs of UEs in GSM: None Management
n the uplink out-of- Radio Bearer
synchronization UMTS: None
Management
state LTE:
LBFD-002008
TDLBFD-002008

eRAN

Description
1526728437 L.E- Total number of E- Multi-mode: None Radio Bearer

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

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

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

e.HighSpeed context releases due GSM: None Management
to high mobility of Radio Bearer
UEs UMTS: None
Management
LTE:
LBFD-002008
TDLBFD-002008
1526728465 L.Signal.Num.Uu Number of Multi-mode: None DRX

signaling messages GSM: None DRX
over the Uu
interface UMTS: None
LTE:
LBFD-002017
TDLBFD-002017

eRAN

Description
1526728466 L.Signal.Num.DRX Number of DRX Multi-mode: None DRX

.Reconfig reconfiguration GSM: None DRX
messages
UMTS: None Dynamic DRX
LTE: Dynamic DRX
LBFD-002017
TDLBFD-002017
LOFD-001105
TDLOFD-001105
1526728546 L.Traffic.User.Cdrx Average number of Multi-mode: None Dynamic DRX

.Avg UEs on which DRX GSM: None DRX
takes effect in a cell
UMTS: None Dynamic DRX
LTE:
LOFD-001105
LBFD-002017
TDLOFD-001105
1526728547 L.Cdrx.Enter.Num Number of times a Multi-mode: None DRX

UE in connected GSM: None DRX
mode enters DRX
in UMTS: None Dynamic DRX
RRC_CONECTED LTE: Dynamic DRX
mode LBFD-002017
TDLBFD-002017
LOFD-001105
TDLOFD-001105
1526728548 L.Cdrx.Exit.Num Number of times a Multi-mode: None DRX

UE in connected GSM: None DRX
mode exits DRX in
RRC_CONECTED UMTS: None Dynamic DRX
mode LTE: Dynamic DRX
LBFD-002017
TDLBFD-002017
LOFD-001105
TDLOFD-001105

eRAN

Description
1526728549 L.Cdrx.Active.TtiN Total number of Multi-mode: None Dynamic DRX

um TTIs for DRX UEs GSM: None Dynamic DRX
in active state
UMTS: None DRX
LTE: DRX
LOFD-001105
TDLOFD-001105
LBFD-002017
TDLBFD-002017
1526728550 L.Cdrx.Sleep.TtiNu Total number of Multi-mode: None Dynamic DRX

m TTIs for DRX UEs GSM: None Dynamic DRX
in sleep state
UMTS: None DRX
LTE: DRX
LOFD-001105
TDLOFD-001105
LBFD-002017
TDLBFD-002017
1526728551 L.Voip.Cdrx.Active. Total number of Multi-mode: None Dynamic DRX

TtiNum TTIs for DRX UEs GSM: None Dynamic DRX
in active state and
performing VoIP UMTS: None DRX
services LTE: DRX
LOFD-001105
TDLOFD-001105
LBFD-002017
TDLBFD-002017
1526728552 L.Voip.Cdrx.Sleep. Total number of Multi-mode: None Dynamic DRX

TtiNum TTIs for DRX UEs GSM: None Dynamic DRX
in dormant state and
performing VoIP UMTS: None DRX
services LTE: DRX
LOFD-001105
TDLOFD-001105
LBFD-002017
TDLBFD-002017

eRAN

Description

NB.InterFddTdd.Ex eNodeB inter- GSM: None Coverage Based
ecAttOut duplex-mode Inter-frequency
handover UMTS: None
Handover
executions triggered LTE:
for UEs in the DRX LBFD-002017 DRX
state LBFD-00201802 Coverage Based
Inter-frequency
TDLBFD-0020180
2

NB.InterFddTdd.Ex successful intra- GSM: None Coverage Based
ecSuccOut eNodeB inter- Inter-frequency
duplex-mode UMTS: None
Handover
outgoing handovers LTE:
triggered for UEs in LBFD-002017 DRX
the DRX state LBFD-00201802 Coverage Based
Inter-frequency
TDLBFD-0020180
2
1526729588 L.HHO.DRX.Intere Number of inter- Multi-mode: None DRX

NB.InterFddTdd.Ex eNodeB inter- GSM: None Coverage Based
ecAttOut duplex-mode Inter-frequency
handover UMTS: None
Handover
executions triggered LTE:
for UEs in the DRX LBFD-002017 DRX
state LBFD-00201802 Coverage Based
Inter-frequency
TDLBFD-0020180
2
1526729589 L.HHO.DRX.Intere Number of Multi-mode: None DRX

NB.InterFddTdd.Ex successful inter- GSM: None Coverage Based
ecSuccOut eNodeB inter- Inter-frequency
duplex-mode UMTS: None
Handover
outgoing handovers LTE:
triggered for UEs in LBFD-002017 DRX
the DRX state LBFD-00201802 Coverage Based
Inter-frequency
TDLBFD-0020180
2

eRAN

Description
1526729656 L.RRC.StateTrans. Number of Multi-mode: None Dynamic DRX

Unsyn2Syn.Succ successfully GSM: None Dynamic DRX
recovered RRC
connections when UMTS: None
UEs switch from LTE:
the uplink out-of- LOFD-001105
synchronization TDLOFD-001105
state to the uplink-
synchronized state
1526729657 L.E- Number of E-RAB Multi-mode: None Dynamic DRX

RAB.StateTrans.Un recovery attempts GSM: None Dynamic DRX
syn2Syn.Att when UEs switch
from the uplink out- UMTS: None
of-synchronization LTE:
state to the uplink- LOFD-001105
synchronized state TDLOFD-001105
1526729658 L.E- Number of Multi-mode: None Dynamic DRX

RAB.StateTrans.Un successfully GSM: None Dynamic DRX
syn2Syn.Succ recovered E-RABs
when UEs switch UMTS: None
from the uplink out- LTE:
of-synchronization LOFD-001105
state to the uplink- TDLOFD-001105
synchronized state
1526730104 L.User.UL.Unsync. Number of times Multi-mode: None Dynamic DRX

Dur.Index0 the duration of a GSM: None Dynamic DRX
UE in the out-of-
state in a cell ranges LTE:
within index 0 LOFD-001105
TDLOFD-001105

UE in the out-of-
TDLOFD-001105

UE in the out-of-
TDLOFD-001105

eRAN

Description

UE in the out-of-
TDLOFD-001105

UE in the out-of-
TDLOFD-001105

UE in the out-of-
TDLOFD-001105

UE in the out-of-
TDLOFD-001105

UE in the out-of-
TDLOFD-001105

UE in the out-of-
TDLOFD-001105

eRAN

Description
1526730124 L.Traffic.PktInterva Number of times Multi-mode: None RRC Connection

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

index 1 LBFD-002007
LOFD-001105
TDLOFD-001105

index 2 LBFD-002007
LOFD-001105
TDLOFD-001105

index 3 LBFD-002007
LOFD-001105
TDLOFD-001105

index 4 LBFD-002007
LOFD-001105
TDLOFD-001105

eRAN

Description

index 5 LBFD-002007
LOFD-001105
TDLOFD-001105

index 6 LBFD-002007
LOFD-001105
TDLOFD-001105

index 7 LBFD-002007
LOFD-001105
TDLOFD-001105

index 8 LBFD-002007
LOFD-001105
TDLOFD-001105
1526739742 L.Traffic.User.Unsy Number of UEs Multi-mode: None Dynamic DRX

n.Drx.Avg configured with GSM: None Dynamic DRX
out-of-
DRX parameters in LTE:
a cell LOFD-001105
TDLOFD-001105

eRAN
DRX and Signaling Control Feature Parameter Description 9 Glossary
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
DRX and Signaling Control Feature Parameter Description 10 Reference Documents
10 Reference Documents
1. 3GPP TS 36.211: "Physical channels and modulation"

2. 3GPP TS 36.300: "Overall description"
3. 3GPP TS 36.321: "Medium Access Control (MAC) protocol specification"
4. Idle Mode Management Feature Parameter Description
5. Intra-RAT Mobility Management in Connected Mode Feature Parameter Description
6. Scheduling Feature Parameter Description
7. Terminal Awareness Differentiation Feature Parameter Description


4 G

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

4 G

Încărcat de

Drepturi de autor:

Formate disponibile

eRAN

DRX and Signaling Control Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 03 (2017-12-06) Huawei Proprietary and Confidential i

1 About This Document.................................................................................................................. 1

Issue 03 (2017-12-06) Huawei Proprietary and Confidential ii

Issue 03 (2017-12-06) Huawei Proprietary and Confidential iii

6.1.5.2 Parameter Optimization.......................................................................................................................................... 73

Issue 03 (2017-12-06) Huawei Proprietary and Confidential iv

6.3.5.2 Parameter Optimization.......................................................................................................................................... 92

Issue 03 (2017-12-06) Huawei Proprietary and Confidential v

1 About This Document

eNodeB Type Model

Macro 3900 and 5900 series base stations

LampSite DBS3900 LampSite and DBS5900 LampSite

Issue 03 (2017-12-06) Huawei Proprietary and Confidential 1

1.2 Intended Audience

1.3 Change History

Change Change Description Parameter Affected

Feature None None Macro, micro,

Editorial Revised descriptions in this None N/A

Issue 03 (2017-12-06) Huawei Proprietary and Confidential 2

Change Change Description Parameter Affected

Feature Added description of the mapping None Macro, micro,

Added information: Settings of None Macro, micro,

Editorial Revised descriptions in this None N/A

eRAN12.1 Draft A (2016-12-30)

Change Change Description Parameter Affected

Feature Added PUCCH CQI detection None Macro, micro,

Issue 03 (2017-12-06) Huawei Proprietary and Confidential 3

Change Change Description Parameter Affected

Supported DRX parameter None Macro, micro,

Optimized the processing None Macro, micro,

Editorial Revised descriptions in 3.1.2 None N/A

1.4 Differences Between eNodeB Types

LBFD-002017 DRX Yes Yes Yes

LOFD-001105 Dynamic DRX Yes Yes Yes

LOFD-001105 High-Mobility- Yes Yes No

Function Implementation in Macro, Micro, and LampSite eNodeBs

Issue 03 (2017-12-06) Huawei Proprietary and Confidential 4

This document covers the following features:

Issue 03 (2017-12-06) Huawei Proprietary and Confidential 5

Table 2-1 Application scenarios and benefits

LBFD-002017 l Smart l Periodic transmission of Reduces UE power

LOFD-00110 Smart terminals l Services characterized by l Reduces signaling

LOFD-00110 Smart terminals Terminals remain in Reduces signaling

Issue 03 (2017-12-06) Huawei Proprietary and Confidential 6

3.1 LBFD-002017 DRX

3.1.1.1 Definition and Application Scenarios

Issue 03 (2017-12-06) Huawei Proprietary and Confidential 7

3.1.1.3 DRX Process

Figure 3-1 DRX process

Issue 03 (2017-12-06) Huawei Proprietary and Confidential 8

1. DRX entry phase

3.1.2 DRX Parameter Configuration at Different Levels

3.1.2.1 QCI-Level DRX Parameter Configuration

Issue 03 (2017-12-06) Huawei Proprietary and Confidential 9

Table 3-1 QCIs and the corresponding service types

QC Bearer Priorit Packet Packet Example Service

1 Guaranteed 2 100 ms 10-2 Conversational voice

3 3 50 ms 10-3 Real-time gaming