eRAN

DRX and Signaling Control Feature

Parameter Description

Issue 01
Date 2023-09-10

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2023. 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: https://www.huawei.com
Email: [email protected]

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. i

Security Declaration
Vulnerability
Huawei's regulations on product vulnerability management are subject to the Vul. Response Process. For
details about this process, visit the following web page:
https://www.huawei.com/en/psirt/vul-response-process
For vulnerability information, enterprise customers can visit the following web page:
https://securitybulletin.huawei.com/enterprise/en/security-advisory

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. ii

eRAN
DRX and Signaling Control Feature Parameter
Description Contents

Contents

1 Change History.........................................................................................................................1
1.1 eRAN20.0 01 (2023-09-10)..................................................................................................................................................1
1.2 eRAN20.0 Draft A (2023-06-30)........................................................................................................................................ 1

2 About This Document.............................................................................................................2

2.1 General Statements................................................................................................................................................................ 2
2.2 Applicable RAT......................................................................................................................................................................... 2
2.3 Features in This Document.................................................................................................................................................. 3

3 Overview....................................................................................................................................4
4 DRX............................................................................................................................................. 6
4.1 Principles.................................................................................................................................................................................... 6
4.1.1 DRX Process........................................................................................................................................................................... 6
4.1.2 Working Mechanism........................................................................................................................................................... 8
4.1.2.1 Related Concepts.............................................................................................................................................................. 8
4.1.2.2 Startup of a DRX Cycle................................................................................................................................................. 10
4.1.2.3 Operation in a DRX Cycle............................................................................................................................................ 11
4.1.2.3.1 Operation in Active Time......................................................................................................................................... 11
4.1.2.3.2 Switching Between Active Time and Sleep Time.............................................................................................15
4.1.2.4 Switching Between Long and Short Cycles........................................................................................................... 16
4.1.3 Entry and Exit Conditions............................................................................................................................................... 17
4.1.3.1 Entry Conditions (FDD)................................................................................................................................................ 17
4.1.3.2 Exit Conditions (FDD)................................................................................................................................................... 18
4.1.4 DRX for Various Scenarios.............................................................................................................................................. 19
4.1.4.1 DRX for VoLTE................................................................................................................................................................. 21
4.1.4.2 DRX for Special UEs.......................................................................................................................................................23
4.1.4.3 DRX for ANR Measurement........................................................................................................................................ 23
4.1.4.4 DRX for GERAN Measurement.................................................................................................................................. 24
4.1.4.5 SRI Offset Reconfiguration for DRX (FDD)........................................................................................................... 24
4.1.4.6 DRX Under CA................................................................................................................................................................. 24
4.1.4.7 DRX for Uplink Timing Control..................................................................................................................................25
4.1.5 DRX Parameter Configuration at Different Levels................................................................................................. 26
4.1.5.1 QCI-Level DRX Parameter Configuration............................................................................................................... 26
4.1.5.2 QCI-Level DRX Parameter Configuration for Different UE Models.............................................................. 27

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. iii

eRAN
DRX and Signaling Control Feature Parameter
Description Contents

4.2 Network Analysis.................................................................................................................................................................. 27

4.2.1 Benefits................................................................................................................................................................................. 27
4.2.2 Impacts.................................................................................................................................................................................. 28
4.3 Requirements......................................................................................................................................................................... 34
4.3.1 Licenses................................................................................................................................................................................. 34
4.3.2 Software................................................................................................................................................................................34
4.3.3 Hardware.............................................................................................................................................................................. 34
4.3.4 Others.................................................................................................................................................................................... 35
4.4 Operation and Maintenance............................................................................................................................................. 35
4.4.1 Data Configuration (FDD).............................................................................................................................................. 35
4.4.1.1 Data Preparation............................................................................................................................................................ 35
4.4.1.2 Using MML Commands............................................................................................................................................... 40
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 41
4.4.2 Activation Verification......................................................................................................................................................41
4.4.3 Network Monitoring......................................................................................................................................................... 45

5 Dynamic DRX..........................................................................................................................47
5.1 Principles.................................................................................................................................................................................. 47
5.1.1 Dynamic DRX Process...................................................................................................................................................... 47
5.1.2 Entry and Exit Conditions............................................................................................................................................... 49
5.1.2.1 Entry Conditions............................................................................................................................................................. 49
5.1.2.2 Exit Conditions................................................................................................................................................................ 49
5.1.3 Principles.............................................................................................................................................................................. 50
5.2 Network Analysis.................................................................................................................................................................. 52
5.2.1 Benefits................................................................................................................................................................................. 52
5.2.2 Impacts.................................................................................................................................................................................. 54
5.3 Requirements......................................................................................................................................................................... 60
5.3.1 Licenses................................................................................................................................................................................. 60
5.3.2 Software................................................................................................................................................................................60
5.3.3 Hardware.............................................................................................................................................................................. 60
5.3.4 Others.................................................................................................................................................................................... 61
5.4 Operation and Maintenance............................................................................................................................................. 61
5.4.1 Data Configuration........................................................................................................................................................... 61
5.4.1.1 Data Preparation............................................................................................................................................................ 61
5.4.1.2 Using MML Commands............................................................................................................................................... 62
5.4.1.3 Using the MAE-Deployment...................................................................................................................................... 63
5.4.2 Activation Observation.................................................................................................................................................... 63
5.4.3 Network Monitoring......................................................................................................................................................... 63

6 High-Mobility-Triggered Idle Mode.................................................................................. 65

6.1 Principles.................................................................................................................................................................................. 65
6.2 Network Analysis.................................................................................................................................................................. 69
6.2.1 Benefits................................................................................................................................................................................. 69
6.2.2 Impacts.................................................................................................................................................................................. 69

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. iv

eRAN
DRX and Signaling Control Feature Parameter
Description Contents

6.3 Requirements......................................................................................................................................................................... 69
6.3.1 Licenses................................................................................................................................................................................. 69
6.3.2 Software................................................................................................................................................................................70
6.3.3 Hardware.............................................................................................................................................................................. 70
6.3.4 Others.................................................................................................................................................................................... 71
6.4 Operation and Maintenance............................................................................................................................................. 71
6.4.1 Data Configuration........................................................................................................................................................... 71
6.4.1.1 Data Preparation............................................................................................................................................................ 71
6.4.1.2 Using MML Commands............................................................................................................................................... 71
6.4.1.3 Using the MAE-Deployment...................................................................................................................................... 72
6.4.2 Activation Observation.................................................................................................................................................... 72
6.4.3 Network Monitoring......................................................................................................................................................... 72

7 Parameters.............................................................................................................................. 73
8 Counters.................................................................................................................................. 74
9 Glossary................................................................................................................................... 75
10 Reference Documents........................................................................................................ 76

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. v

eRAN
DRX and Signaling Control Feature Parameter
Description 1 Change History

1 Change History

This chapter describes changes not included in the "Parameters", "Counters",

"Glossary", and "Reference Documents" chapters. These changes include:
● Technical changes
Changes in functions and their corresponding parameters
● Editorial changes
Improvements or revisions to the documentation

1.1 eRAN20.0 01 (2023-09-10)

This issue does not include any changes.

1.2 eRAN20.0 Draft A (2023-06-30)

This issue introduces the following changes to eRAN19.1 02 (2023-04-28).

Technical Changes
None

Editorial Changes
Revised descriptions in this document.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 1

eRAN
DRX and Signaling Control Feature Parameter
Description 2 About This Document

2 About This Document

2.1 General Statements

Purpose
This document is intended to acquaint readers with:

● The technical principles of features and their related parameters

● The scenarios where these features are used, the benefits they provide, and
the impact they have on networks and functions
● Requirements of the operating environment that must be met before feature
activation
● Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance
NOTE

This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve optimal gains, contact Huawei professional service engineers.
Functions mentioned in this document work properly only when enabled in the
specified applicable scenarios (such as RAT and networking). If a function not
mentioned in this document is enabled or a function is enabled in a scenario not
specified as applicable, exceptions or other impacts may occur.

Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this
document apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.

2.2 Applicable RAT

This document applies to FDD.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 2

eRAN
DRX and Signaling Control Feature Parameter
Description 2 About This Document

2.3 Features in This Document

This document describes the following FDD features.

Feature ID Feature Name Chapter/Section

LBFD-002017 DRX 4 DRX

LOFD-001105 Dynamic DRX See the corresponding sections

of the subfeatures.

LOFD-00110501 Dynamic DRX 5 Dynamic DRX

LOFD-00110502 High-Mobility- 6 High-Mobility-Triggered

Triggered Idle Mode Idle Mode

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 3

eRAN
DRX and Signaling Control Feature Parameter
Description 3 Overview

3 Overview

This document covers the following DRX and signaling control features:
● DRX
With the ever increasing diversity of LTE applications, the standby time of user
equipment (UE) has become a major concern for end users. To reduce UE
power consumption, 3GPP has introduced discontinuous reception (DRX) for
LTE and Huawei eNodeBs provide the DRX feature accordingly.
● Dynamic DRX
Many smart-terminal applications use small, sparse packets or heartbeat
packets. These applications cause networks to frequently release and
reestablish connections, increasing signaling. In addition, staying in connected
mode for an extended period consumes UE power. The Huawei feature
Dynamic DRX allows UEs to enter power saving or signaling reduction mode
based on UE power consumption and network load.
● 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 High-Mobility-
Triggered Idle Mode feature.
Table 3-1 describes the application scenarios and benefits of these features.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 4

eRAN
DRX and Signaling Control Feature Parameter
Description 3 Overview

Table 3-1 Application scenarios and benefits of DRX and signaling control features
Feature Recommende Applicable Scenario Benefit
d UE Type

DRX Smart and ● Periodic transmission Reduces UE power

non-smart of continuous small consumption.
terminals packets, such as voice
over IP (VoIP)
services
● Delay-insensitive
services, such as
HTML web page
browsing and email
● Services that use
small, sparse packets,
such as Presence
services
● Automatic neighbor
relation (ANR)
measurement

Dynamic DRX Smart ● Services that use ● Reduces the risk

terminals small, sparse packets of signaling
● Services that use storms caused
heartbeat packets by frequent RRC
connection
releases and
reestablishment
s for these
services.
● Reduces UE
power
consumption.

High- Smart Terminals remain in Reduces the risk of

Mobility- terminals connected mode for signaling storms
Triggered Idle long periods with caused by
Mode frequent handovers handovers of UEs
moving at high
speeds.

NOTE

● Presence services, such as instant messaging, 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.
● "UE" and "terminal" in this document have the same meaning.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 5

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

4 DRX

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. This feature is
controlled by the CellDrxPara.DrxAlgSwitch parameter.

4.1 Principles

4.1.1 DRX Process

Figure 4-1 shows the DRX process.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 6

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

Figure 4-1 DRX process

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 the DRX-Configuration IE. For the DRX
entry conditions, see 4.1.3.1 Entry Conditions (FDD).
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 4.1.2.3.2
Switching Between Active Time and Sleep Time and 4.1.2.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

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 7

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

release. After the UE receives the message, it immediately clears all the DRX
parameters stored locally and exits DRX mode. For the DRX exit conditions,
see 4.1.3.2 Exit Conditions (FDD).

NOTE

To address the compatibility issue caused by nonstandard channel quality indicator (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
simultaneousAckNackAndCQI to False when delivering an RRC Connection
Reconfiguration message to a UE that complies with 3GPP Release 8 or earlier;
however, the eNodeB does not do so for a UE that complies with a release later than
3GPP Release 8.
● If the CellDrxPara.CqiMask parameter is set to OFF, the eNodeB does not distinguish
between UEs complying with different 3GPP Releases.
In FDD eMIMO scenarios, the DrxSimulAckNackAndCqiSwitch option of the
CellAlgoSwitch.EmimoSwitch parameter specifies whether to allow UEs in DRX mode to
send CQIs and ACKs/NACKs simultaneously on the physical uplink control channel
(PUCCH).
● If the DrxSimulAckNackAndCqiSwitch option of the CellAlgoSwitch.EmimoSwitch
parameter is selected and the cell is configured with more than two transmit channels,
the eNodeB sets the simultaneousAckNackAndCQI IE to True in the delivered RRC
Connection Reconfiguration message for non-carrier aggregation (non-CA) UEs. For
CA UEs, the simultaneousAckNackAndCQI IE value is determined by the
CaCqiAndAckAbnCtrlSwitch option of the
ENodeBAlgoSwitch.CompatibilityCtrlSwitch parameter.
● If the DrxSimulAckNackAndCqiSwitch option of the CellAlgoSwitch.EmimoSwitch
parameter is deselected, the eNodeB sets the simultaneousAckNackAndCQI IE to False
in the delivered RRC Connection Reconfiguration message.

4.1.2 Working Mechanism

When DRX is used, the UE does not constantly monitor the physical downlink
control channel (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.

4.1.2.1 Related Concepts

On Duration
In DRX mode, a UE does not always keep its receiver off. It periodically turns on its
receiver and monitors possible signaling for a consecutive period. This consecutive
period is called On Duration, which is controlled by the On Duration Timer. The
DrxParaGroup.OnDurationTimer parameter specifies the On Duration Timer.
When DRX is enabled, SRSs and CQIs can only be reported during the active time.
If the TimeAlignmentTimer.TimingMeasMode parameter is set to INVALID, the
eNodeB will ensure that SRS and CQI reporting is coordinated with DRX. If needed,
the length of the On Duration Timer can be increased to ensure that the UE has a
chance to report their CQIs and SRSs.
● If the timer length is greater than the total length of PDCCH subframes
(PSFs) occupied by a long DRX cycle, DRX may fail. That is, the UE always
stays in active time and will not enter sleep time.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 8

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

● If the DrxParaGroup.SupportShortDrx parameter is set to UU_ENABLE and

the timer length is greater than the total length of PSFs occupied by a short
DRX cycle, DRX may fail for short DRX cycles. That is, the UE using a short
DRX cycle always stays in active time and will not enter sleep time.

In FDD, CQI reporting must be ensured. If the

TimeAlignmentTimer.TimingMeasMode parameter is set to ALLMEASMODE,
the eNodeB only ensures that CQI reporting is coordinated with DRX for DRX to
work effectively.
It is recommended that the length of the On Duration Timer be less than the total
length of PSFs occupied by a long or short DRX cycle, depending on which one is
used. When the length of the On Duration Timer is equal to the total length of
PSFs occupied by a DRX cycle, the UE power consumption cannot be reduced, and
the eNodeB does not deliver DRX parameters.
The number of PSFs in a long or short DRX cycle is calculated using the following
formula:
Number of PSFs in a long or short DRX cycle = temp(10 ms) x floor(Long or short
DRX cycle/10) + temp(Long or short DRX cycle modulo 10)
In this formula, temp(x) indicates how many PSFs there are within time x, floor is
the greatest integer function, and modulo is the operation that finds the
remainder after division of one number by another.
In FDD, the value of temp(x) is always x.

DRX Cycle
A DRX cycle is the interval between the beginnings of two occurrences of an On
Duration. A DRX cycle consists of an On Duration and a possible period of sleep
time, as shown in Figure 4-2.

Figure 4-2 DRX cycle

NOTE

The period following an On Duration may be active or sleep time. For details, see 4.1.2.3.1
Operation in Active Time.

A DRX cycle consists of active time and sleep time. There are two types of DRX
cycles: a long cycle and a short cycle.

Active Time
In active time, the UE monitors the PDCCH and UE turns on its receiver. The
length of the active time is equal to the On Duration plus other possible periods

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 9

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

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 4.1.2.3.1 Operation in Active
Time.
If the duration of a DRX cycle is specified:
● A longer active time results in a shorter service delay but increased UE power
consumption.
● A shorter active time results in reduced UE power consumption but a longer
service delay.

Sleep Time
During a DRX cycle, the non-active time is sleep time. During sleep time, the UE
turns off its receiver.

Long DRX Cycle

A long cycle (also called a long DRX cycle) saves more power. The mandatory
parameter DrxParaGroup.LongDrxCycle can be used to configure a long cycle.

NOTE

If a short cycle is not configured before DRX is enabled, then after entering DRX mode, the
UE will use a long cycle. 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 DRX Cycle

A short cycle (also called a short DRX cycle) is jointly controlled by the
CellDrxPara.ShortDrxCycleSwitch and DrxParaGroup.SupportShortDrx
parameters.
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:
(1) CellDrxPara.ShortDrxCycleSwitch: specifies whether to use a short cycle. (2)
DrxParaGroup.SupportShortDrx: specifies whether services of a specific QCI
support a short cycle. (3) DrxParaGroup.ShortDrxCycle: specifies the length of a
short cycle. These parameters are optional.
If a short cycle is configured for the UE, the UE will determine when to use the
long or short cycle as described in 4.1.2.4 Switching Between Long and Short
Cycles.

4.1.2.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:
● For a long DRX cycle:
[(SFN x 10) + SSFN] modulo DrxParaGroup.LongDrxCycle = DRX start offset

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 10

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

The long DRX cycle starts at the time specified by the system frame number
(SFN) and system subframe number (SSFN).
● 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

● 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 4-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).

Figure 4-3 Entering DRX mode and starting the DRX cycle

4.1.2.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.

4.1.2.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:

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 11

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

● The On Duration Timer, DRX Inactivity Timer, DRX Retransmission Timer, or

Contention Resolution Timer is running.
● A scheduling request (SR) sent by the UE on the physical uplink control
channel (PUCCH) is pending.
● An uplink (UL) grant for a pending hybrid automatic repeat request (HARQ)
retransmission occurs.
● 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.

The following tables describe the related DRX timers.

Table 4-1 On Duration Timer (controlled by the DrxParaGroup.OnDurationTimer

parameter)

Definition Description

Function This timer specifies the time during which the UE monitors the
PDCCH.

Start This timer starts at the first subframe of a DRX cycle. For
details, see 4.1.2.2 Startup of a DRX Cycle.

Timing Timing is based on the number of consecutive PDCCH

subframes.

Stop ● This timer stops after the UE receives a DRX command MAC
control element (MCE).
● This timer stops after it expires.

Expiry After this timer expires, the UE enters the sleep state, no longer
monitoring the PDCCH.

Table 4-2 DRX Inactivity Timer (controlled by the

DrxParaGroup.DrxInactivityTimer parameter)

Definition Description

Function This timer specifies the time during which the UE determines
whether to 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.

Timing Timing is based on the number of consecutive PDCCH

subframes.

Stop ● This timer stops after the UE receives a DRX command MCE.
● This timer stops after it expires.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 12

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

Definition Description

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.

Table 4-3 DRX Short Cycle Timer (controlled by the

DrxParaGroup.DrxShortCycleTimer parameter)
Definition Description

Function This timer specifies the lifetime of a short cycle, that is, the
number of consecutive repetition times of a short cycle.

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

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.

Table 4-4 DRX Retransmission Timer (controlled by the

DrxParaGroup.DrxReTxTimer parameter)
Definition Description

Function This timer specifies the length of time the UE will wait for
HARQ 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.

Timing Timing is based on the number of consecutive PDCCH

subframes.

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.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 13

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

Table 4-5 HARQ RTT Timer (No parameters are involved.)

Definition Description

Function This timer specifies the interval 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:
● At the beginning of the subframe when semi-persistent DL
data transmission may take place.
● The UE decodes a PDCCH and knows that a HARQ process
will have a DL transmission in a new subframe.

Timing Timing is based on the number of subframes.

Stop This timer stops after it expires.

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.

Table 4-6 Contention Resolution Timer (No parameters are involved.)

Definition Description

Function This timer specifies the time during which the UE waits for a
Contention 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.

Timing Timing is based on the number of consecutive PDCCH

subframes.

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.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 14

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

4.1.2.3.2 Switching Between Active Time and Sleep Time

Switching between active time and sleep time depends on DRX timers and service
processes.

Figure 4-4 illustrates the switching between active time and sleep time.

Figure 4-4 Switching between active time and sleep time

Table 4-7 describes the conditions for starting active time. For example, OD is the
condition for starting the On Duration Timer.

Table 4-7 Conditions for starting active time

Condition Meaning

OD A DRX cycle starts.

IA A PDCCH message indicating an initial DL

transmission is received.

R The HARQ RTT Timer expires.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 15

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

Condition Meaning

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.

The active time shown in the UE DRX status plot in Figure 4-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 illustrated in Figure 4-4, "DL transmission
required" refers to one of the two DL HARQ transmission scenarios:

● A DL data transmission will start at the subframe with semi-persistent

scheduling applied.
● A DL data transmission will start at the subframe, which the UE learns by
monitoring the PDCCH.

In active time, when the eNodeB interprets no responses from the UE as DTX
(indicating discontinuous transmission) for two consecutive times, it immediately
instructs the UE to enter sleep time and stops downlink scheduling because the
DRX state it maintains is inconsistent with that of the UE. However, this
mechanism will decrease downlink throughput if two consecutive HARQ reports
over the PUCCH are erroneously decoded as DTX or if the eNodeB does not
distinguish between DTX and NACK in carrier aggregation (CA) scenarios. To
prevent this, set the CellDrxPara.DrxRcvDtxProSwitch parameter to ON so that
the eNodeB will not immediately instruct the UE to enter sleep time when it
detects two consecutive DTX states with DRX enabled. Instead, it will determine
whether to instruct the UE to enter sleep time only when the timer defined by the
DrxParaGroup.DrxInactivityTimer parameter expires.

This lowers the probability that the eNodeB erroneously instructs the UE to enter
sleep time, and increases downlink throughput. In common 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 scheduling 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 in the cell.

4.1.2.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.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 16

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

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:
● 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.
● 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.

4.1.3 Entry and Exit Conditions

When certain network and UE conditions are met, the eNodeB instructs UEs to
enter or exit DRX mode. This section describes the conditions for entering and
exiting DRX mode.

4.1.3.1 Entry Conditions (FDD)

DRX is jointly controlled by the general DRX switch CellDrxPara.DrxAlgSwitch
and the QCI-specific DRX switch DrxParaGroup.EnterDrxSwitch.
A UE enters DRX mode when all the following conditions are met:
● The CellDrxPara.DrxAlgSwitch parameter is set to ON.
● All the bearers established for the UE support DRX. That is, the
DrxParaGroup.EnterDrxSwitch parameter of each bearer is set to ON.
● The traffic volume of the UE is at most equal to the threshold specified by the
CellDrxPara.FddEnterDrxThd parameter during the period specified by the
CellDrxPara.DataAmountStatTimer parameter.
There are exceptions. When one of the following conditions is met, the UE does
not enter DRX mode:
● If the UE constantly performs gap-assisted measurement, the eNodeB does
not instruct the UE to enter DRX mode.
● When the UE is in the transmission time interval (TTI) bundling state, the
eNodeB does not instruct the UE to enter DRX mode.
● Newly admitted UEs are prohibited from entering DRX mode when the
number of UEs in DRX mode reaches the maximum in the following scenarios:

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 17

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

– The serving cell is established on an LBBPc.

– The serving cell is not established on an LBBPc, and the
Drx.DrxFlexCtrlSwitch parameter is set to OFF.

4.1.3.2 Exit Conditions (FDD)

The UE exits DRX mode in any of the following situations:

● Any of the following conditions is met:

– Newly established bearers do not support DRX.

▪ When the CellDrxPara.DrxPolicyMode parameter is set to DEFAULT

or 3GPPDEFINEDQCIPRIORITY, the DrxParaGroup.EnterDrxSwitch
parameter is set to OFF for the new bearers.

▪ When the CellDrxPara.DrxPolicyMode parameter is set to

QCIPRIORITY, the DrxParaGroup.EnterDrxSwitch parameter is set
to OFF for the new bearer with the highest priority.
– The traffic volume of the UE is high. That is, the traffic volume in the
period specified by the CellDrxPara.DataAmountStatTimer parameter is
higher than the threshold specified by the CellDrxPara.FddExitDrxThd
parameter.
● The CellDrxPara.DrxAlgSwitch parameter is set to OFF, and the eNodeB
instructs the UE to exit DRX mode in the RRC connection reconfiguration
procedure.
● The UE is in connected mode and experiences a radio link failure (RLF) due to
poor radio conditions.
● The source eNodeB instructs the UE to exit DRX mode only during an inter-
cell handover. After the handover is complete, the target eNodeB determines
whether the UE can enter DRX mode based on the configurations of the
target eNodeB and entry conditions.
● The UE enters the TTI bundling state.
● The eNodeB instructs the UE to exit DRX mode when the UE starts gap-
assisted measurement and 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.
NOTE

If both of these parameters are turned on, only CellDrxPara.GapDrxExclusiveSwitch

is considered.
● The CellDrxPara.SinrThldForVolteDrxCtrl parameter is set to a value other
than -100, and the uplink SINR of the VoLTE UE is less than this parameter
value.
NOTE

When the CellDrxPara.SinrThldForVolteDrxCtrl parameter is set to -100, SINR-based

DRX control is disabled.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 18

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

4.1.4 DRX 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 4.1.4.1 DRX for VoLTE.

For special UEs or ANR measurements, you can configure special DRX parameters.
For details, see 4.1.4.2 DRX for Special UEs and 4.1.4.3 DRX for ANR
Measurement.

The following tables list the DRX parameters for various scenarios.

Table 4-8 DRX parameters for common UEs

Configuratio Parameter ID for VoLTE Parameter ID for Non-VoLTE

n Item Services Services

Long cycle DrxParaGroup.LongDrxCycle DrxParaGroup.LongDrxCycle

length

Short cycle DrxParaGroup.SupportShort DrxParaGroup.SupportShort

switch Drx Drx
Short cycle Short cycles are not used for DrxParaGroup.ShortDrxCycle
length VoLTE UEs by default.

Short Cycle Short cycles are not used for DrxParaGroup.DrxShortCycle

Timer length VoLTE UEs by default. Timer
On Duration DrxParaGroup.OnDurationTi DrxParaGroup.OnDurationTi
Timer length mer mer
DRX Inactivity DrxParaGroup.DrxInactivityTi DrxParaGroup.DrxInactivityTi
Timer length mer mer
DRX DrxParaGroup.DrxReTxTimer DrxParaGroup.DrxReTxTimer
Retransmissio
n Timer
length

Table 4-9 DRX parameters for special UEs

Configuratio Parameter ID
n Item

Long cycle CellDrxSpecialPara.LongDrxCycleSpecial

length

Short cycle CellDrxSpecialPara.ShortDrxCycleSwitchSpecial

switch

Short cycle CellDrxSpecialPara.ShortDrxCycleSpecial

length

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 19

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

Configuratio Parameter ID
n Item

Short Cycle CellDrxSpecialPara.DrxShortCycleTimerSpecial

Timer length

On Duration CellDrxSpecialPara.OnDurationTimerSpecial
Timer length

DRX Inactivity CellDrxSpecialPara.DrxInactivityTimerSpecial

Timer length

DRX DrxParaGroup.DrxReTxTimer
Retransmissio
n Timer
length

Table 4-10 DRX parameters for ANR measurement

Configuratio Parameter ID for Intra-RAT Parameter ID for Inter-RAT
n Item Scenarios Scenarios

Long cycle CellDrxSpecialPara.LongDrxC CellDrxSpecialPara.LongDrxC

length ycleForIntraRatAnr ycleForInterRatAnr
Short cycle Short cycles are not used in Short cycles are not used in
switch ANR measurement. ANR measurement.

Short cycle Short cycles are not used in Short cycles are not used in
length ANR measurement. ANR measurement.

Short Cycle Short cycles are not used in Short cycles are not used in
Timer length ANR measurement. ANR measurement.

On Duration For FDD cells: For FDD cells:

Timer length ● For ● For
CellDrxSpecialPara.LongD CellDrxSpecialPara.LongD
rxCycleForIntraRatAnr ≥ rxCycleForInterRatAnr ≥
SF256, the On Duration SF256, the On Duration
Timer length is set to Timer length is set to
PSF100 by the system. PSF100 by the system.
● For ● For
CellDrxSpecialPara.LongD CellDrxSpecialPara.LongD
rxCycleForIntraRatAnr < rxCycleForInterRatAnr <
SF256, the On Duration SF256, the On Duration
Timer length is set to Timer length is set to
PSF50 by the system. PSF50 by the system.

DRX Inactivity For FDD: For FDD:

Timer length CellDrxSpecialPara.FddAnrDr CellDrxSpecialPara.FddAnrDr
xInactivityTimer xInactivityTimer

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 20

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

Configuratio Parameter ID for Intra-RAT Parameter ID for Inter-RAT

n Item Scenarios Scenarios

DRX Fixed to 8 ms Fixed to 8 ms

Retransmissio
n Timer
length

4.1.4.1 DRX for VoLTE

For VoLTE, a set of special DRX parameter settings is available to minimize 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 a VoLTE UE
has multiple bearers with different QCIs (for example, QCIs 1, 5, and 9), the
eNodeB determines the DRX parameters based on the
CellDrxPara.DrxPolicyMode parameter setting.

DRX Parameter Settings Recommended for VoLTE

The following table lists the common DRX parameters for VoLTE. Recommended
values for DRX parameters vary according to the bearers with different QCIs,
preference for performance or power saving, and FDD or TDD mode. For details,
see related parameter references.

Table 4-11 Settings of common DRX parameters for VoLTE

Parameter ID Description

DrxParaGroup.LongDrxCycle Indicates the length of the long DRX cycle. If

the settings of other DRX parameters remain
unchanged:
● A smaller parameter value results in a
higher probability that the UE stays in
active state and consumes more power.
● A larger parameter value results in a higher
probability that VoLTE scheduling chances
occur during sleep time. This delays packet
transmission and affects user experience.

DrxParaGroup.OnDurationTi Indicates the length of the On Duration Timer.

mer If there are a large number of UEs running
VoLTE services, set a large value for this
parameter to ensure the scheduling of VoLTE
services.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 21

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

Parameter ID Description

DrxParaGroup.DrxInactivityTi Indicates the length of the DRX inactivity

mer timer. If the settings of other DRX parameters
remain unchanged:
● A smaller parameter value results in lower
UE power consumption but longer service
delay.
● A larger parameter value results in higher
UE power consumption but shorter service
delay.

DrxParaGroup.DrxReTxTimer Indicates the length of the DRX

Retransmission Timer. If the settings of other
DRX parameters remain unchanged:
● A smaller parameter value results in a
higher probability that the UE enters sleep
time before receiving the retransmitted
data. In this case, the retransmitted data
cannot be correctly received.
● A larger parameter value results in a higher
probability that the UE keeps waiting for
the retransmitted data even when the data
is lost. In this case, the UE stays in active
time and consumes more power.

DrxParaGroup.SupportShortD Indicates whether short DRX cycles are

rx enabled.
As the short DRX cycle is not recommended
for VoLTE, you are advised to set this
parameter to UU_DISABLE.

Special Processing for VoLTE

When the CellDrxPara.DrxStateDuringUlHarqRetx parameter is set to
DRX_ACTIVE_FOR_VOICE, if the eNodeB has correctly received the data initially
transmitted by a VoLTE UE in DRX mode over the physical uplink shared channel
(PUSCH), the 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 higher resource overhead and lower data
throughput.
When the SpsSchSwitch option of the CellAlgoSwitch.DlSchSwitch parameter is
selected, the following special processing is performed:
● The DlSpsDrxDecouplingSwitch option of
CellDlschAlgo.DlEnhancedVoipSchSw specifies whether the long DRX cycle
configuration is considered during the configuration and activation of
downlink semi-persistent scheduling:

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 22

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

– 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 physical downlink shared channel
(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.
– 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.
● For UEs in downlink semi-persistent scheduling, QCI-specific DRX parameters
do not take effect based on the CellDrxPara.DrxPolicyMode parameter
setting. Instead, the DRX parameters for the QCI corresponding to the
dedicated voice bearer take effect.

4.1.4.2 DRX 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. A UE is called a special UE if any of the following conditions is met:

● The SpidCfg.DrxStatus parameter is set to FALSE for the UE with the

corresponding subscriber profile ID (SPID). For details about SPID, see Flexible
User Steering.
● The UE-EUTRA-Capability IE in the UECapabilityInformation message sent by
the UE contains noBenFromBatConsumpOpt.

The working mode of special UEs is the same as that of common UEs except for
DRX parameter settings.

4.1.4.3 DRX 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 or
DrxParaGroup.EnterDrxSwitch is turned on.

● 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.
● 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.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 23

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

4.1.4.4 DRX for GERAN Measurement

DRX parameters for GERAN measurement need to be configured in the following
scenarios:
● CellDrxPara.CovGsmMeasDrxCfgSwitch is turned on and the eNodeB
triggers GERAN measurement after receiving a coverage-based inter-RAT
event A2 report from the UE.
● 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:
● 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.
● 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.

4.1.4.5 SRI Offset Reconfiguration for DRX (FDD)

Normally, 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 less power can be saved. To save more
UE power, SRI offset reconfiguration for DRX has been introduced to reduce the
number of SR-pending TTIs in sleep time.
The SriOffsetReConfigForDrxSW option of the CellPucchAlgo.SriAlgoSwitch
parameter specifies whether to enable SRI offset reconfiguration for DRX.
● When this option is selected, the SRI offset is reconfigured for DRX to save
more power.
● When this option is deselected, the SRI offset is not reconfigured for DRX. If
the UE sends an SRI during sleep time, the sleep time will be shortened and
less power is saved.
During SRI offset reconfiguration for DRX, the CQI and SRS parameters configured
for the UE's primary carrier cell (PCC) cannot be reconfigured. Otherwise, the
calculated SRI offset is meaningless because the DRX start offset has been
changed with the CQI and SRS parameters.

4.1.4.6 DRX Under CA

In accordance with section 5.7 "Discontinuous Reception (DRX)" in 3GPP TS
36.321 V11.2.0, the DRX active time is the same for all activated serving cells of a

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 24

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

CA UE. All activated serving cells of a CA UE use the DRX parameters for the
primary cell (PCell). DRX parameters under CA are configured as follows:

● If DRX is enabled in both the PCell and the secondary cell (SCell) for a CA UE
and the serving eNodeB of the PCell sends a MAC control element (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 as well, with the DRX parameters for
the PCell applied to the SCell.
– If the UE has not entered DRX mode in the PCell, the eNodeB determines
whether the UE should enter DRX mode in both the PCell and SCell based
on the traffic volume of the UE.
● 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.
● 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.
● The PCell and SCell maintain the DRX status of UEs on their respective
carriers.
– If the PCC_SCC_DRX_STATE_SYNC_SW option of the
CellDrxPara.CaDrxOptSwitch parameter is selected, the PCell and SCells
notify each other of the DRX status change. However, in this case, the
PCell notifies only one SCell of the DRX status change.
– If the PCC_SCC_DRX_STATE_SYNC_OPT_SW option of the
CellDrxPara.CaDrxOptSwitch parameter is selected, the PCell and SCells
notify each other of the DRX status change.
● Both the DrxParaGroup.OnDurationTimer and
DrxParaGroup.DrxInactivityTimer parameters must be set to a value greater
than four subframes for the PCell. Otherwise, the average downlink user
throughput will decrease.

4.1.4.7 DRX for Uplink Timing Control

When SRSs are used for uplink timing control, SRS configurations affect how the
eNodeB sets the DRX parameters. The time alignment (TA) measurement precision
for uplink synchronization depends on the number of times the UE reports SRSs.
To acquire sufficient SRSs for TA measurements, the eNodeB adaptively adjusts the
long DRX cycle based on the UE's SRS configurations and TA delivery interval.
Therefore, the long DRX cycle delivered to the UE on the live network may differ
from that set by MML commands. The long DRX cycle 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.

● 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. A cycle longer than 320 ms may affect uplink
timing performance.
● When TimeAlignmentTimer.TimingMeasMode is set to ALLMEASMODE,
the eNodeB does not restrict DRX parameter settings.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 25

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

When demodulation reference signals (DMRSs) are used for uplink timing control
and DRX is enabled, active time must exist during the TA delivery interval so that
the eNodeB can deliver scheduling information to trigger TA scheduling.

The eNodeB adjusts DRX parameters for UEs based on parameter validity. The DRX
parameter settings may be changed after the validity check. Validity check is
performed to see whether:

● The long cycle is a multiple of the short cycle. If not, the short cycle is
automatically adjusted to an appropriate value.
● The long cycle is a multiple of 10. If not, it is automatically adjusted to an
appropriate value.
● The On Duration Timer length is less than the short cycle. If not, the short
cycle is not configured.
● The On Duration Timer length is less than the long cycle. If not, the DRX
parameters are not configured.

4.1.5 DRX Parameter Configuration at Different Levels

4.1.5.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:
● QCI-level DRX switch
The DrxParaGroup.EnterDrxSwitch parameter specifies the QCI-level DRX
switch. For details about how to use this parameter, see 4.1.3 Entry and Exit
Conditions.

● QCI-level parameters related to DRX timers

QCI-level parameters related to DRX timers include
DrxParaGroup.OnDurationTimer, DrxParaGroup.DrxInactivityTimer,
DrxParaGroup.DrxReTxTimer, DrxParaGroup.LongDrxCycle,
DrxParaGroup.ShortDrxCycle, DrxParaGroup.DrxShortCycleTimer, and
DrxParaGroup.SupportShortDrx. For details about how to use these
parameters, see 4.1.2 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.

For details about standardized QCIs and the corresponding services types, see
"Table 6.1.7: Standardized QCI characteristics" in 3GPP TS 23.203 V12.11.0.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 26

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

4.1.5.2 QCI-Level DRX Parameter Configuration for Different UE Models

DRX parameters can be set differently for UEs with different TACs or UEs with
different TAC+SVN combinations. TAC and SVN stand for the type allocation code
and software version number in the international mobile station equipment
identity and software version (IMEISV), respectively.

This function is an enhancement to Terminal Awareness Differentiation. For

details, see Terminal Awareness Differentiation.

4.2 Network Analysis

4.2.1 Benefits

Gains
DRX provides the following advantages over continuous reception:

● The UE does not need to constantly monitor the PDCCH. The UE can turn off
its radio frequency (RF) receiver and other communication modules to reduce
power consumption and have longer standby time.
● ANR measurement is allowed for UEs during the sleep time in DRX.
● SRI offset reconfiguration for DRX can be used to save more UE power in FDD.
For a given UE, it can reduce UE power consumption by up to 12.3%. For
details, see 4.1.4.5 SRI Offset Reconfiguration for DRX (FDD).
NOTE

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 support DRX and do not
constantly monitor the PDCCH, but they cannot turn off their RF modules. Therefore, the
power saving effect on such UEs is limited.

Most Beneficial Scenarios

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 (CellDrxPara.CovGsmMeasDrxCfgSwitch be set
to 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 (CellDrxPara.MeasDrxSpecSchSwitch be set to
ON) when the call drop rate is very high and there are not high requirements
for ping delay, access delay, and handover interruption delay.

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.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 27

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

Gain Measurement
After activating this feature, the following counters are used for monitoring:
● L.Cdrx.Active.TtiNum and L.Cdrx.Sleep.TtiNum are used to indirectly
measure the power saving effect of UEs on the network.
● L.Voip.Cdrx.Active.TtiNum and L.Voip.Cdrx.Sleep.TtiNum are used to
monitor the power saving effect of UEs performing VoIP services.

4.2.2 Impacts
Network Impacts
DRX sleep time helps reduce UE power consumption but may prolong UE service
delays and decrease the UE traffic volume or throughput.
DRX has the following impact on network performance:
● If the value of the DrxParaGroup.OnDurationTimer parameter is too small,
the VoIP capacity will decrease, or the Downlink Packet Loss Rate (VoIP)
and Uplink Packet Loss Rate (VoIP) in heavy-load scenarios will increase. A
large value of this parameter results in reduced UE power saving.
● If the value of the DrxParaGroup.LongDrxCycle parameter is too large, the
CQI reporting interval will increase, and the traffic volume or throughput
under functions such as scheduling and multiple-input-multiple-output
(MIMO) will decrease. In addition, the Intra-Frequency Handover Out
Success Rate will decrease, and the Service Drop Rate will increase. These
impacts are more obvious in high-speed mobility or weak-coverage scenarios.
If the value of the parameter is too small, the UE power saving effect will
deteriorate.
● If the sleep time is too short, ANR measurements will fail.
● If there are UEs that are incompatible with DRX on the network, service drops
will occur on these UEs and the Service Drop Rate will increase.
NOTE

After DRX is enabled, preallocation is disabled and the benefits or impacts brought by
preallocation no longer exist. The ping delay will increase and the performance of small
window TCP services will deteriorate. For details, see Uplink Scheduling.

Turning on Coverage based GSM Measurement DRX Configure Switch shortens

the delay in measurement reporting, avoids service drops due to delayed
handovers, and decreases the Service Drop Rate. However, in this case, VoIP users
are not scheduled in sleep time, the scheduling interval is prolonged, and voice
quality may deteriorate.
When Measurement DRX Special Schedule Switch is on, the eNodeB schedules
UEs in a special way that provides more chances for UEs to send scheduling
requests (SRs) but increases PDCCH overhead. When the control channel element
(CCE) resource is limited, delays (such as ping delay, access delay, and handover
delay) for online UEs may be prolonged. It is recommended that this switch be on
when the call drop rate is very high and there are not high requirements for ping
delay, access delay, or handover delay.
In FDD, SRI offset reconfiguration for DRX may have the following negative
impacts:

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 28

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

● PUCCH resources may be wasted or adjusted too early. This may further affect
Layer-2-related KPIs, for example, increase two or fewer uplink resource
blocks (RBs) used, reduce two or fewer available PUSCH RBs, and reduce
uplink throughput by up to 14%.
● The E-UTRAN radio access bearer (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 reestablishment success rate may decrease.
● The average CPU usage of main control boards and baseband processing units
(BBPs) increases by no more than 3%.

Function Impacts
RAT Function Function Reference Description
Name Switch

FDD Carrier CA works in Carrier For details about the

aggregation multiple Aggregatio impact of CA on DRX, see
scenarios. Its n Carrier Aggregation.
function
switch varies
depending on
scenarios. For
details, see
Carrier
Aggregation.
FDD Gap-assisted None Mobility When gap-assisted
measurement Managem measurement conflicts
ent in with DRX, gap-assisted
Connected measurement takes
Mode priority.

FDD TTI bundling TtiBundlingS VoLTE When TTI bundling is

witch option used for a UE, the
of the eNodeB does not instruct
CellAlgoSwit the UE to enter DRX
ch.UlSchSwit mode unless required
ch parameter during ANR
measurement. When TTI
bundling is initiated for a
UE in DRX mode, the
eNodeB instructs the UE
to exit DRX mode unless
required during ANR
measurement.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 29

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

RAT Function Function Reference Description

Name Switch

FDD VoIP semi- SpsSchSwitch VoLTE The eNodeB activates

persistent option of the VoIP semi-persistent
scheduling CellAlgoSwit scheduling based on the
ch.UlSchSwit DlSpsDrxDecouplingS-
ch parameter witch option of the
SpsSchSwitch CellDlschAlgo.DlEnhanc
option of the edVoipSchSw parameter:
CellAlgoSwit ● If this option is
ch.DlSchSwit deselected, the
ch parameter eNodeB can activate
downlink semi-
persistent scheduling
only when the value
of
DrxParaGroup.LongD
rxCycle is less than or
equal to the value of
CellDlschAlgo.DlSpsIn
terval.
● If this option is
selected, the eNodeB
can activate downlink
semi-persistent
scheduling regardless
of the settings of
DrxParaGroup.LongD
rxCycle and
CellDlschAlgo.DlSpsIn
terval. In this
situation, semi-
persistently scheduled
initial transmissions on
the PDSCH can be
performed in the DRX
sleep time. If a UE
cannot receive semi-
persistently scheduled
PDSCH data in the
sleep time, the
downlink voice packet
loss rate increases.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 30

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

RAT Function Function Reference Description

Name Switch

FDD Downlink VOLTE_DL_PK VoLTE ● If a UE is in DRX

voice packet T_DUPLICATE mode, the eNodeB
duplication _SW option instructs the UE to exit
for VoLTE UEs of the DRX mode after
VolteAlgoCo downlink voice packet
nfig.VolteOpt duplication for VoLTE
Switch UEs takes effect.
parameter ● A UE cannot enter
DRX mode after
downlink voice packet
duplication for VoLTE
UEs takes effect.

FDD Uplink short- CellUlschAlg Uplink UEs that have entered

interval SPS o.IntvlOfUlSp Scheduling uplink short-interval SPS
sWithSkippin do not support DRX.
g
FDD Superior CellAlgoExtS Superior UEs under enhanced
uplink witch.UlCove Uplink coverage do not support
coverage rageEnhance Coverage DRX.
mentSw (FDD)
FDD Short TTI SHORT_TTI_S Short TTI UEs scheduled in short
W option of (FDD) TTI mode do not support
the DRX.
CellShortTtiA
lgo.SttiAlgoS
witch
parameter

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 31

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

RAT Function Function Reference Description

Name Switch

FDD High speed Cell.HighSpe High When a UE is moving at

mobility edFlag Speed high speed and the long
Mobility DRX cycle is set to 40 ms
or less, the power saving
effect for the UE is not
significant. If this cycle is
set to be longer than 40
ms, the SRS-based timing
and reference signal
received power (RSRP)
measurement are
affected. Both
configurations may result
in a decreased handover
success rate, an increased
service drop rate, a larger
number of RRC
connection
reestablishments, and a
decreased
reestablishment success
rate.

FDD Energy saving SymbolPwrS Energy To ensure the bundled

based on aving.TrigBn Conservati scheduling effect, the
proactive dlSchDlAvgPr on and eNodeB aligns the DRX
scheduling bThld Emission On Duration periods of
Reduction different UEs to increase
the proportion of UEs
that simultaneously enter
the DRX sleep state.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 32

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

RAT Function Function Reference Description

Name Switch

FDD CRS dynamic CRS_DYNAMI Energy ● DRX helps increase the

muting C_MUTING_S Conservati CRS muting
W option of on and probability. However,
the Emission CRS muting does not
SymbolPwrS Reduction take effect if DRX
aving.Symbol parameters are set for
ShutdownEn semi-persistent
hancedSw scheduling.
parameter ● To ensure that all UEs
in a cell can complete
data transmission in
the On Duration
period after
alignment, the On
Duration period must
be set to a value
greater than or equal
to 1/64 of the long
DRX cycle.

FDD Hybrid DSS SpectrumClo LTE FDD The number of RBs

Based on ud.Spectrum and NR available for LTE
Asymmetric CloudSwitch Hybrid decreases, leading to a
Bandwidth set to Dynamic decrease in the average
LTE_NR_SPEC Spectrum number of scheduling
TRUM_SHR Sharing times. As a result, the
and average number of UEs
LNR_SPECTR that enter DRX mode, as
UM_SHR_ASY well as the frequency of
M_SW option UEs entering and exiting
of the DRX mode increase.
SpectrumClo
ud.Spectrum
CloudEnhSwi
tch
parameter

FDD LTE FDD and SpectrumClo LTE FDD The number of RBs
NR Flash ud.Spectrum and NR available for LTE
Dynamic CloudSwitch Dynamic decreases, leading to a
Spectrum set to Spectrum decrease in the average
Sharing LTE_NR_SPEC Sharing number of scheduling
TRUM_SHR times. As a result, the
average number of UEs
that enter DRX mode, as
well as the frequency of
UEs entering and exiting
DRX mode increase.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 33

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

RAT Function Function Reference Description

Name Switch

FDD Automatic FDD_ACH_S Automatic DRX is disabled for a cell

congestion WITCH (FDD) Congestio if smart control for DRX
handling option of the n in ACH is activated and
ParaAutoOpt Handling the trigger condition is
Cfg.AchEffect met. In this case, UEs in
iveType the cell do not enter DRX
parameter mode any more.

4.3 Requirements

4.3.1 Licenses
There are no license requirements for basic functions.

4.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated, if there are any.
For detailed operations, see the relevant feature documents.

Prerequisite Functions
None

Mutually Exclusive Functions

RAT Function Function Reference Description
Name Switch

FDD Ultra high Cell.HighSpe High DRX does not take effect
speed edFlag Speed in ultra-high-speed
mobility Mobility mobility scenarios. If the
DTX rate is high in a cell,
the RRC connection setup
success rate and RRC
connection
reestablishment success
rate may decrease, and
the RRC connection setup
duration may increase.

4.3.3 Hardware
The hardware described in this section may require compatibility between each
other. For details, see the technical specifications and hardware description of the

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 34

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

corresponding hardware in 3900 & 5900 Series Base Station Product

Documentation.

Base Station Models

No requirements

Boards
No requirements

RF Modules
No requirements

4.3.4 Others
None

4.4 Operation and Maintenance

4.4.1 Data Configuration (FDD)

4.4.1.1 Data Preparation

The following tables describe the parameters used for function activation.

Table 4-12 Parameters in the CellDrxPara MO

Parameter Name Parameter ID Setting Notes

DRX Algorithm Switch CellDrxPara.DrxAlgS You are advised to turn on this

witch switch to enable DRX for a
cell.

Short DRX Cycle CellDrxPara.ShortDrx The value ON is

Switch CycleSwitch recommended in scenarios
with tight delay constraints.

DRX State During UL CellDrxPara.DrxState Set this parameter to its

HARQ Retrans DuringUlHarqRetx recommended value.

Data amount Statistic CellDrxPara.DataAm Set this parameter to its

timer ountStatTimer recommended value.

FDD enter DRX CellDrxPara.FddEnter Set this parameter to its

threshold DrxThd recommended value.

FDD exit DRX CellDrxPara.FddExitD Set this parameter to its

threshold rxThd recommended value.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 35

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

Parameter Name Parameter ID Setting Notes

DRX Policy Mode CellDrxPara.DrxPolic If the bearers for a UE have

yMode multiple QCIs, you are advised
to set this parameter to
QCIPRIORITY.

DRX Start Offset CellDrxPara.DrxStart Turn on this switch when SRS

Optimization Switch OffsetOptSwitch resources are not configured
for UEs or there is a large
number of UEs in the cell.

Table 4-13 Parameters in the CellQciPara MO

Parameter Name Parameter ID Setting Notes

Local Cell ID CellQciPara.LocalCell Set this parameter based on

Id the network plan.

QoS Class Indication CellQciPara.Qci Set this parameter based on

the network plan.

DRX Parameter Group CellQciPara.DrxPara Set this parameter based on

ID GroupId the network plan.

QCI Priority For DRX CellQciPara.QciPriori If the bearers for a UE have

tyForDrx multiple QCIs and the
CellDrxPara.DrxPolicyMode
parameter is set to
QCIPRIORITY, the eNodeB
selects the DRX parameter
group for the UE based on the
QCI-specific priorities.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 36

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

Table 4-14 Parameters in the QciPara MO

Parameter Name Parameter ID Setting Notes

Service Type QciPara.ServiceType 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 4-15 Parameters in the DrxParaGroup MO

Parameter Name Parameter ID Setting Notes

Local cell ID DrxParaGroup.LocalC Set this parameter based on

ellId the network plan.

DRX parameter group DrxParaGroup.DrxPar Set this parameter based on

ID aGroupId the network plan.

Enter DRX Switch DrxParaGroup.EnterD If the bearers to which the

rxSwitch DRX parameter group ID
applies are required to support
DRX, set this parameter to
ON.

Category Type DrxParaGroup.CatTyp Set this parameter based on

e the network plan.

On Duration Timer DrxParaGroup.OnDur Set this parameter to its

ationTimer recommended value.

DRX Inactivity Timer DrxParaGroup.DrxIna Set this parameter to its

ctivityTimer recommended value.

DRX Retransmission DrxParaGroup.DrxRe Set this parameter to its

Timer TxTimer recommended value.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 37

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

Parameter Name Parameter ID Setting Notes

Long DRX Cycle DrxParaGroup.LongD Set this parameter to its

rxCycle recommended value.
For voice services with QCI 1,
if the SpsSchSwitch option of
the
CellAlgoSwitch.DlSchSwitch
parameter is selected, you are
advised to set this parameter
to a value less than or equal
to the semi-persistent
scheduling period. Otherwise,
downlink semi-persistent
scheduling cannot be
activated.

Short-Cycle DRX DrxParaGroup.Suppo If the bearers to which the

Supported Indication rtShortDrx DRX parameter group ID
applies are required to support
short DRX cycles, set this
parameter to ON.

Short DRX Cycle DrxParaGroup.ShortD Set this parameter to its

rxCycle recommended value.

DRX Short Cycle Timer DrxParaGroup.DrxSh Set this parameter to its

ortCycleTimer recommended value.

Table 4-16 Parameters in the DRX MO

Parameter Name Parameter ID Setting Notes

DRX Flexibility Control Drx.DrxFlexCtrlSwitc Set this parameter to its

Switch h recommended value.

The following tables describe the parameters used for function optimization.

Table 4-17 Parameters in the SpidCfg MO

Parameter Name Parameter ID Setting Notes

Spid SpidCfg.Spid The parameters are used to

set DRX parameters for special
Drx status SpidCfg.DrxStatus UEs.
Operators can use the Spid
parameter to designate a UE
as a special UE and use
customized parameters for the
UE in DRX mode. This helps
reduce the service delay for
this UE.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 38

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

Table 4-18 Parameters in the CellDrxSpecialPara MO

Parameter Name Parameter ID Setting Notes

Long DRX Cycle for CellDrxSpecialPara.L Set this parameter to its

Intra-RAT ANR ongDrxCycleForIn- recommended value.
traRatAnr
Long DRX Cycle for CellDrxSpecialPara.L Set this parameter to its
Inter-RAT ANR ongDrxCycleForInter- recommended value.
RatAnr
DRX Inactivity Timer CellDrxSpecialPara.D Set this parameter to its
for Special UE rxInactivityTimer- recommended value.
Special
Short DRX Cycle CellDrxSpecialPara.S Set this parameter to its
Switch for Special UE hortDrxCycleSwitch- recommended value.
Special
DRX onDurationTimer CellDrxSpecialPara.O Set this parameter to its
for Special UE nDurationTimerSpe- recommended value.
cial

Table 4-19 Parameters in the CellDrxPara MO

Parameter Name Parameter ID Setting Notes

Coverage based GSM CellDrxPara.CovGsm Set this parameter based on

Measurement DRX MeasDrxCfgSwitch the network plan.
Configure Switch

Measurement DRX CellDrxPara.MeasDrx Set this parameter based on

Special Schedule SpecSchSwitch the network plan.
Switch

Long DRX Cycle for CellDrxPara.LongDrx The value SF320 is

Measurement CycleForMeas recommended in DRX mode.

On Duration Timer for CellDrxPara.OnDurTi The value PSF40 is

Measurement merForMeas recommended in DRX mode.

DRX Inactivity Timer CellDrxPara.DrxInact The value PSF20 is

for Measurement TimerForMeas recommended in DRX mode.

DRX Retransmission CellDrxPara.DrxReTx The value PSF6 is

Timer for TimerForMeas recommended in DRX mode.
Measurement

Short DRX Switch for CellDrxPara.ShortDrx Set this parameter based on

Measurement SwForMeas the network plan.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 39

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

Parameter Name Parameter ID Setting Notes

Short DRX Cycle for CellDrxPara.ShortDrx Set this parameter to its

Measurement CycleForMeas recommended value.

Short Cycle Timer for CellDrxPara.ShortCyc The value 10 is recommended

Measurement leTimerForMeas in DRX mode.

GAP and DRX CellDrxPara.GapDrxE Set this parameter based on

Exclusive Switch xclusiveSwitch the network plan.

VoLTE Gap and DRX CellDrxPara.VolteGap Set this parameter based on

Exclusive Switch DrxExclusiveSwitch the network plan.

SINR Threshold for CellDrxPara.SinrThld Set this parameter to its

VoLTE DRX Control ForVolteDrxCtrl recommended value.

CA DRX Optimization CellDrxPara.CaDrxOp It is recommended that the

Switch tSwitch PCC_SCC_DRX_STATE_SYNC_
OPT_SW option be selected
for CA UEs.

Table 4-20 Parameters in the CellPucchAlgo MO

Parameter Name Parameter ID Setting Notes

SRI Algorithm Switch CellPucchAlgo.SriAlg Select the SriOffsetReConfig-

oSwitch ForDrxSW option of this
parameter to enable SRI offset
reconfiguration for DRX.

4.4.1.2 Using MML Commands

Before using MML commands, refer to 4.2.2 Impacts and 4.3.2 Software and
complete the parameter configurations for related functions based on the impact
and mutually exclusive relationships between the functions, as well as the actual
network scenario.
Before using MML commands, confirm the related parameter modification
precautions by referring to the fields including "Service Interrupted After
Modification" and "Caution" for the corresponding parameters in the parameter
reference.

Activation Command Examples

//Enabling the DRX function
MOD CELLDRXPARA: LocalCellId=0, DrxAlgSwitch=ON, ShortDrxCycleSwitch=ON,
FddEnterDrxThd=1000,FddExitDrxThd=1000;
//Setting a DRX parameter group for a standardized QCI
MOD CELLQCIPARA: LocalCellId=0, Qci=9, DrxParaGroupId=3;
//(Optional) Setting the service type for mapping an extended QCI to a standardized QCI
MOD QCIPARA: Qci=10, ServiceType=TCPorBuffStreaming;
//(Optional) Setting the QCI priority for selecting DRX parameters for a UE with multiple QCIs
MOD CELLDRXPARA: LocalCellId=0, DrxPolicyMode=QCIPRIORITY;

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 40

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

MOD CELLQCIPARA: LocalCellId=0, Qci=9, QciPriorityForDrx=9;

//Configuring a DRX parameter group
MOD DRXPARAGROUP: LocalCellId=0, DrxParaGroupId=3, EnterDrxSwitch=ON, CatType=LTE,
OnDurationTimer=PSF10, DrxInactivityTimer=PSF100,DrxReTxTimer=PSF8, LongDrxCycle=SF320,
SupportShortDrx=UU_ENABLE, ShortDrxCycle=SF80, DrxShortCycleTimer=1;

Optimization Command Examples

//Scenario 1: setting DRX parameters for VoLTE services
MOD DRXPARAGROUP: LocalCellId=0, DrxParaGroupId=3, EnterDrxSwitch=ON, CatType=LTE,
OnDurationTimer=PSF2, DrxInactivityTimer=PSF80, DrxReTxTimer=PSF8, LongDrxCycle=SF40,
SupportShortDrx=UU_DISABLE;
//Scenario 2: setting DRX parameters for special UEs
ADD SPIDCFG: Spid=99, DrxStatus=FALSE, RatFreqPriorityInd=NOT_CFG;
MOD CELLDRXPARA: LocalCellId=0, DrxAlgSwitch=ON, ShortDrxCycleSwitch=ON;
MOD CELLDRXSPECIALPARA: LocalCellId=0,LongDrxCycleSpecial=SF10, OnDurationTimerSpecial=PSF5,
DrxInactivityTimerSpecial=PSF10, ShortDrxCycleSwitchSpecial=UU_DISABLE;
//Scenario 3: setting DRX parameters for ANR measurement
MOD CELLDRXSPECIALPARA: LocalCellId=0, LongDrxCycleForIntraRatAnr=SF320;
//Scenario 4: setting SRI offset reconfiguration for DRX
MOD CELLPUCCHALGO: LocalCellId=0, SriAlgoSwitch=SriOffsetReConfigForDrxSW-1;
//Scenario 5: setting connected-mode DRX parameters for E-UTRAN-to-GERAN measurement
MOD CELLDRXPARA: LocalCellId=0, CovGsmMeasDrxCfgSwitch=ON, MeasDrxSpecSchSwitch=ON,
LongDrxCycleForMeas=SF320, OnDurTimerForMeas=PSF40, DrxInactTimerForMeas=PSF20,
DrxReTxTimerForMeas=PSF6, ShortDrxSwForMeas=ON, ShortDrxCycleForMeas=SF20,
ShortCycleTimerForMeas=10;
//Scenario 6: setting 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;
//Removing DRX parameters when configuring gap-assisted measurement parameters for UEs regardless of
their QCIs
MOD CELLDRXPARA: LocalCellId=0, GapDrxExclusiveSwitch=ON;
//Scenario 7: setting parameters for SINR-based VoLTE DRX exit
MOD CELLDRXPARA: LocalCellId=0, SinrThldForVolteDrxCtrl=5;
//Scenario 8: setting DRX parameters for CA
MOD CELLDRXPARA: LocalCellId=0, CaDrxOptSwitch=PCC_SCC_DRX_STATE_SYNC_OPT_SW-1;

Deactivation Command Examples

The following provides only deactivation command examples. You can determine
whether to restore the settings of other parameters based on actual network
conditions.
//Disabling the DRX function
MOD CELLDRXPARA: LocalCellId=0, DrxAlgSwitch=OFF;

4.4.1.3 Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.

4.4.2 Activation Verification

Scenario 1: Setting DRX Parameters for Common UEs

The activation verification procedure is as follows:

Step 1 Run the MOD CELLDRXPARA command to turn on the DRX switch.

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.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 41

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

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.
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 4-5, the eNodeB has instructed the UE to enter
DRX mode.

Figure 4-5 RRC Connection Reconfiguration (1)

NOTE

Due to the restrictions on CQI and SRS reporting, the configured values for the
DrxParaGroup.OnDurationTimer and DrxParaGroup.LongDrxCycle parameters may be
inconsistent with the values delivered by the eNodeB.

----End

Scenario 2: Setting DRX Parameters for Special UEs

Ensure that an SPID has been set on the EPC for the international mobile
subscriber identity (IMSI) of a UE.
The activation verification procedure is as follows:

Step 1 Run the ADD SPIDCFG command to add the SPID configuration for the IMSI.
Step 2 Run the MOD CELLDRXPARA command to turn on the DRX switch.
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
SPID-specific DRX parameters as shown in Figure 4-6, the eNodeB has instructed
the UE to enter DRX mode.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 42

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

Figure 4-6 RRC Connection Reconfiguration (2)

----End

Scenario 3: Setting DRX Parameters for ANR Measurement

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.
The activation verification procedure is as follows:
Step 1 Run the MOD CELLDRXPARA command to turn on the DRX switch and the MOD
CELLDRXSPECIALPARA command to set the Long DRX Cycle for Intra-RAT ANR
and Long DRX Cycle for Inter-RAT ANR parameters.
● 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.
● 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. (This
message is delivered when ANR measurement is required.) If the message
contains DRX parameters as shown in Figure 4-7, the eNodeB has configured DRX
parameters for ANR measurement.

Figure 4-7 RRC Connection Reconfiguration (3)

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 43

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

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. (This
message is delivered when ANR measurement is required.) If the message still
contains DRX parameters, the eNodeB has configured DRX parameters for ANR
measurement.

----End

Scenario 4: Setting SRI Offset Reconfiguration for DRX

Ensure that DRX has taken effect and the SRI reporting period is not less than 40
ms.
The activation verification procedure is as follows:

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.
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 resource 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 4-8, SRI offset reconfiguration for DRX is
successful.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 44

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

Figure 4-8 RRC Connection Reconfiguration (4)

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

4.4.3 Network Monitoring

After activating this feature, the following counters are used for monitoring:
● L.Cdrx.Enter.Num and L.Cdrx.Exit.Num are used to monitor how often a UE
enters and exits DRX mode.
● L.Traffic.User.Cdrx.Avg is used to monitor the average number of UEs that
enter DRX mode on the network.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 45

eRAN
DRX and Signaling Control Feature Parameter
Description 4 DRX

● L.Cdrx.Active.TtiNum and L.Cdrx.Sleep.TtiNum are used to indirectly

measure the power saving effect of UEs on the network.
● L.Voip.Cdrx.Active.TtiNum and L.Voip.Cdrx.Sleep.TtiNum are used to
monitor the power saving effect of UEs performing VoIP services.
● Handover-related counters: used to monitor the handover performance of UEs
in DRX mode and the proportion of UEs in DRX mode during handovers.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 46

eRAN
DRX and Signaling Control Feature Parameter
Description 5 Dynamic DRX

5 Dynamic DRX

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 consumption increases rapidly or signaling overhead is high
because of UE access to the network. This feature is controlled by the
CellAlgoSwitch.DynDrxSwitch parameter.

5.1 Principles

5.1.1 Dynamic DRX Process

Figure 5-1 shows the dynamic DRX process.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 47

eRAN
DRX and Signaling Control Feature Parameter
Description 5 Dynamic DRX

Figure 5-1 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 5.1.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 signaling reduction mode based on the UE inactivity timer
setting.
When the UE does not have a bearer with a QCI of 69 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

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 48

eRAN
DRX and Signaling Control Feature Parameter
Description 5 Dynamic DRX

defined by the QciPara.UeInactivityTimerDynDrxQci parameter of QCI 69.

For details, see 5.1.3 Principles.
NOTE

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 a called UE if all of the following conditions are met:
● The UE inactivity timer of the UE has expired before the call is answered.
● The UE switches to idle mode.
● 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.
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
5.1.2.2 Exit Conditions.

5.1.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 dynamic
DRX are the same as the parameter configuration principles in DRX. However, the two
features are independent of each other.
● When dynamic DRX is enabled, the DRX switch cannot control whether the DRX
parameters for UEs in the synchronization state take effect. The DRX parameters are
determined based on the DrxParaGroup.EnterDrxSwitch parameter.

5.1.2.1 Entry Conditions

Dynamic DRX mode is enabled when the DynDrxSwitch option of the
CellAlgoSwitch.DynDrxSwitch parameter is selected.
Before dynamic DRX is enabled, the following parameters need to be set for UEs in
the out-of-synchronization state:
● CellDrxPara.LongDrxCycleUnsync
● CellDrxPara.OndurationTimerUnsync
● CellDrxPara.DrxInactivityTimerUnsync
UE power saving preference or network-wide signaling reduction preference in
dynamic DRX mode is determined by the QciPara.UeInactivityTimerDynDrxQci
parameter.

5.1.2.2 Exit Conditions

The UE exits dynamic DRX mode when any of the following conditions is met:

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 49

eRAN
DRX and Signaling Control Feature Parameter
Description 5 Dynamic DRX

● The DynDrxSwitch option of the CellAlgoSwitch.DynDrxSwitch parameter

is deselected, and the eNodeB instructs the UE to exit dynamic DRX mode in
the RRC connection reconfiguration procedure.
● For details about other conditions in FDD, see 4.1.3.2 Exit Conditions (FDD).

5.1.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:
● QciPara.UeInactivityTimerDynDrxQci
● TimeAlignmentTimer.TimeAlignmentTimer
● RrcConnStateTimer.UlSynTimerDynDrx
Figure 5-2 shows how a UE switches between different states.

Figure 5-2 UE state switching

In addition, a protection mechanism is introduced for dynamic DRX, as shown in

Figure 5-3.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 50

eRAN
DRX and Signaling Control Feature Parameter
Description 5 Dynamic DRX

Figure 5-3 Protection mechanism

Dynamic DRX is controlled by the CellAlgoSwitch.DynDrxSwitch parameter. The

principles of dynamic DRX are as follows:

1. If the value of 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 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.
NOTE

If the DynDrxSwitch option of the CellAlgoSwitch.DynDrxSwitch parameter is

selected, the settings of the QciPara.UeInactiveTimerForQci and
QciPara.UlSynTimerForQci parameters take effect only for UEs not supporting
DRX.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 51

eRAN
DRX and Signaling Control Feature Parameter
Description 5 Dynamic 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 the DRX parameters for the out-of-
synchronization state, including 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.

5.2 Network Analysis

5.2.1 Benefits

Gains
Dynamic DRX can provide either of the following benefits:
● Reduced 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.
● Reduced signaling overhead
Dynamic DRX reduces the amount of signaling used for RRC connection
establishment and release 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.

Most Beneficial Scenarios

Dynamic DRX is recommended in the following scenarios:

● Operators attach great importance to UE power saving.

To save more power, you are advised to set a large difference between the
value of the 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 and saves more power.
● Operators attach great importance to signaling reduction.
To reduce signaling, compare the total number of handovers on the network
and the number of E-RAB setups. If the number of handovers is 50% more
than 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 50% less than 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.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 52

eRAN
DRX and Signaling Control Feature Parameter
Description 5 Dynamic DRX

NOTE

If the QciPara.UeInactivityTimerDynDrxQci parameter is set to an inappropriate value,

some UEs may experience incompatibility problems. 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. 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 Terminal Awareness Differentiation feature and
add these UEs to a dynamic DRX blacklist. For details about the operation, see
Terminal Awareness Differentiation.
For QCI 1, it is recommended that the QciPara.UeInactivityTimerDynDrxQci
parameter be set to a value greater than the core-network-configured duration
after which the link is released if the called UE does not answer the call. The
purpose is to solve the problem that the core network releases a VoLTE connection
when the called UE does not answer the call and the inactivity timer of the calling
UE expires.

Gain Measurement
● Power saving
– Use special tools to monitor the power saving effect directly.
– Use counters to monitor the power saving effect indirectly.
If the difference between the QciPara.UeInactivityTimerDynDrxQci
parameter value and the RrcConnStateTimer.UlSynTimerDynDrx
parameter value is large, use the L.Cdrx.Active.TtiNum and
L.Cdrx.Sleep.TtiNum counters and consider the power saving
performance of the UE 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. 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.
● Signaling reduction
– To indirectly monitor changes in signaling overhead, use the following
counters to monitor changes in the numbers of RRC connection setup
attempts in different scenarios:
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
– To indirectly monitor changes in signaling overhead, use the
L.Paging.UU.Att counter to monitor changes in the number of UEs paged
on the Uu interface.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 53

eRAN
DRX and Signaling Control Feature Parameter
Description 5 Dynamic DRX

– To directly monitor changes in signaling overhead on the Uu interface,

use the L.Signal.Num.Uu counter.
– To monitor the total change in signaling overhead on the S1 and Uu
interfaces, use the following counters:
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
NOTE

● If the value of RrcConnStateTimer.UlSynTimerDynDrx after dynamic DRX is

enabled is less than the value of QciPara.UlSynTimerForQci before dynamic DRX
is enabled, the signaling reduction effect decreases.
● Signaling overhead for 10 RRC connection reconfigurations is equivalent to that
for one E-RAB establishment.

5.2.2 Impacts
Network Impacts
Dynamic DRX has the same impact on network performance as DRX. For details,
see 4.2.2 Impacts.
In accordance with section 8.1.2.2 "E-UTRAN intra frequency measurements" in
3GPP TS 36.133 V10.0.0, the RSRP measurement period is a multiple of the long
DRX cycle. After DRX parameters for the out-of-synchronization state are set, the
RSRP measurement period increases. As a result, the number of delayed
handovers, service drops, or RRC connection reestablishments increases.
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 uses
ensures that the DRX parameters for the out-of-synchronization state can still be
sent to the UE. During the period when the base station is ensuring DRX
parameter delivery, if the UE has uplink or downlink data to send or receive or if
the base station delivers a TA command to the UE, the values of the following
counters may fluctuate in the manner shown in Figure 5-4:
● L.RRC.StateTrans.Unsyn2Syn
● L.RRC.StateTrans.Syn2Unsyn
● L.RRC.StateTrans.Unsyn2Syn.Succ
● L.E-RAB.Num.Syn2Unsyn
● L.E-RAB.StateTrans.Unsyn2Syn.Succ

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 54

eRAN
DRX and Signaling Control Feature Parameter
Description 5 Dynamic DRX

● L.E-RAB.StateTrans.Unsyn2Syn.Att
● L.E-RAB.Release.Unsyn

Figure 5-4 Counter fluctuation principle

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 55

eRAN
DRX and Signaling Control Feature Parameter
Description 5 Dynamic DRX

Function Impacts
RAT Function Function Reference Description
Name Switch

FDD Carrier CA works in Carrier For details about the

aggregation multiple Aggregatio impact of CA on DRX, see
scenarios. Its n Carrier Aggregation.
function
switch varies
depending on
scenarios. For
details, see
Carrier
Aggregation.
FDD Gap-assisted None Mobility When gap-assisted
measurement Managem measurement conflicts
ent in with DRX, gap-assisted
Connected measurement takes
Mode priority.

FDD TTI bundling TtiBundlingS VoLTE When TTI bundling is

witch option used for a UE, the
of the eNodeB does not instruct
CellAlgoSwit the UE to enter DRX
ch.UlSchSwit mode unless required
ch parameter during ANR
measurement. When TTI
bundling is initiated for a
UE in DRX mode, the
eNodeB instructs the UE
to exit DRX mode unless
required during ANR
measurement.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 56

eRAN
DRX and Signaling Control Feature Parameter
Description 5 Dynamic DRX

RAT Function Function Reference Description

Name Switch

FDD VoIP semi- SpsSchSwitch VoLTE The eNodeB activates

persistent option of the VoIP semi-persistent
scheduling CellAlgoSwit scheduling based on the
ch.UlSchSwit DlSpsDrxDecouplingS-
ch parameter witch option of the
SpsSchSwitch CellDlschAlgo.DlEnhanc
option of the edVoipSchSw parameter:
CellAlgoSwit ● If this option is
ch.DlSchSwit deselected, the
ch parameter eNodeB can activate
downlink semi-
persistent scheduling
only when the value
of
DrxParaGroup.LongD
rxCycle is less than or
equal to the value of
CellDlschAlgo.DlSpsIn
terval.
● If this option is
selected, the eNodeB
can activate downlink
semi-persistent
scheduling regardless
of the settings of
DrxParaGroup.LongD
rxCycle and
CellDlschAlgo.DlSpsIn
terval. In this
situation, semi-
persistently scheduled
initial transmissions on
the PDSCH can be
performed in the DRX
sleep time. If a UE
cannot receive semi-
persistently scheduled
PDSCH data in the
sleep time, the
downlink voice packet
loss rate increases.

FDD Uplink short- CellUlschAlg Uplink UEs that have entered

interval SPS o.IntvlOfUlSp Scheduling uplink short-interval SPS
sWithSkippin do not support DRX.
g

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 57

eRAN
DRX and Signaling Control Feature Parameter
Description 5 Dynamic DRX

RAT Function Function Reference Description

Name Switch

FDD Superior CellAlgoExtS Superior UEs under enhanced

uplink witch.UlCove Uplink coverage do not support
coverage rageEnhance Coverage DRX.
mentSw (FDD)
FDD Short TTI SHORT_TTI_S Short TTI UEs scheduled in short
W option of (FDD) TTI mode do not support
the DRX.
CellShortTtiA
lgo.SttiAlgoS
witch
parameter

FDD High speed Cell.HighSpe High When a UE is moving at

mobility edFlag Speed high speed and the long
Mobility DRX cycle is set to 40 ms
or less, the power saving
effect for the UE is not
significant. If this cycle is
set to be longer than 40
ms, the SRS-based timing
and RSRP measurement
are affected. Both
configurations may result
in a decreased handover
success rate, an increased
service drop rate, a larger
number of RRC
connection
reestablishments, and a
decreased
reestablishment success
rate.

FDD Energy saving SymbolPwrS Energy To ensure the bundled

based on aving.TrigBn Conservati scheduling effect, the
proactive dlSchDlAvgPr on and eNodeB aligns the DRX
scheduling bThld Emission On Duration periods of
Reduction different UEs to increase
the proportion of UEs
that simultaneously enter
the DRX sleep state.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 58

eRAN
DRX and Signaling Control Feature Parameter
Description 5 Dynamic DRX

RAT Function Function Reference Description

Name Switch

FDD CRS dynamic CRS_DYNAMI Energy ● DRX helps increase the

muting C_MUTING_S Conservati CRS muting
W option of on and probability. However,
the Emission CRS muting does not
SymbolPwrS Reduction take effect if DRX
aving.Symbol parameters are set for
ShutdownEn semi-persistent
hancedSw scheduling.
parameter ● To ensure that all UEs
in a cell can complete
data transmission in
the On Duration
period after
alignment, the On
Duration period must
be set to a value
greater than or equal
to 1/64 of the long
DRX cycle.

FDD Hybrid DSS SpectrumClo LTE FDD The number of RBs

Based on ud.Spectrum and NR available for LTE
Asymmetric CloudSwitch Hybrid decreases, leading to a
Bandwidth set to Dynamic decrease in the average
LTE_NR_SPEC Spectrum number of scheduling
TRUM_SHR Sharing times. As a result, the
and average number of UEs
LNR_SPECTR that enter DRX mode, as
UM_SHR_ASY well as the frequency of
M_SW option UEs entering and exiting
of the DRX mode increase.
SpectrumClo
ud.Spectrum
CloudEnhSwi
tch
parameter

FDD LTE FDD and SpectrumClo LTE FDD The number of RBs
NR Flash ud.Spectrum and NR available for LTE
Dynamic CloudSwitch Dynamic decreases, leading to a
Spectrum set to Spectrum decrease in the average
Sharing LTE_NR_SPEC Sharing number of scheduling
TRUM_SHR times. As a result, the
average number of UEs
that enter DRX mode, as
well as the frequency of
UEs entering and exiting
DRX mode increase.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 59

eRAN
DRX and Signaling Control Feature Parameter
Description 5 Dynamic DRX

5.3 Requirements

5.3.1 Licenses
The following are FDD license requirements.
Feature ID Feature Name Model Sales Unit

LOFD-001105 Dynamic DRX LT1S00DDRX00 per Cell

5.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated, if there are any.
For detailed operations, see the relevant feature documents.

Prerequisite Functions
None

Mutually Exclusive Functions

RAT Function Function Reference Description
Name Switch

FDD Ultra high Cell.HighSpe High Dynamic DRX does not

speed edFlag Speed take effect in ultra-high-
mobility Mobility speed mobility scenarios.

5.3.3 Hardware
The hardware described in this section may require compatibility between each
other. For details, see the technical specifications and hardware description of the
corresponding hardware in 3900 & 5900 Series Base Station Product
Documentation.

Base Station Models

No requirements

Boards
No requirements

RF Modules
No requirements

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 60

eRAN
DRX and Signaling Control Feature Parameter
Description 5 Dynamic DRX

5.3.4 Others
None

5.4 Operation and Maintenance

5.4.1 Data Configuration

5.4.1.1 Data Preparation

Table 5-1 and Table 5-2 describe the parameters used for function activation and
optimization, respectively.

Table 5-1 Parameters used for activation

Parameter Parameter ID Option Setting Notes

Name

Dynamic DRX CellAlgoSwitc DynDrxSwitch It is recommended that

switch h.DynDrxSwit this option be selected to
ch enable dynamic DRX.

Table 5-2 Parameters used for optimization

Parameter Parameter ID Setting Notes

Name

Uplink Sync RrcConnStateT Set this parameter based on the network

Timer Dynamic imer.UlSynTim plan.
DRX erDynDrx

QCI-specific UE QciPara.UeIna Set this parameter based on the network

Inactive Timer ctiveTimerPri plan.
Priority

UE Inactivity QciPara.UeIna Set this parameter based on the network

Timer Dynamic ctivityTimerDy plan.
DRX for QCI nDrxQci

UE Inactive QciPara.UeIna Set this parameter based on the network

Timer for QCI ctiveTimerFor plan.
Qci

UnSync Long CellDrxPara.Lo Set this parameter based on the network

DRX Cycle ngDrxCycleUn plan.
sync

Onduration CellDrxPara.O Set this parameter based on the network

Timer Unsync ndurationTime plan.
rUnsync

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 61

eRAN
DRX and Signaling Control Feature Parameter
Description 5 Dynamic DRX

Parameter Parameter ID Setting Notes

Name

DRX Inactivity CellDrxPara.Dr Set this parameter based on the network

Timer Unsync xInactivityTim plan.
erUnsync

Repeat CellAccess.Rep Set this parameter based on the network

Synchronizatio tSyncAvoidInd plan.
n Avoid
Indication

Repeat CellAccess.Rep Set this parameter based on the network

Synchronizatio tSyncAvoidTim plan.
n Avoid Time e

5.4.1.2 Using MML Commands

Before using MML commands, refer to 5.2.2 Impacts and 5.3.2 Software and
complete the parameter configurations for related functions based on the impact
and mutually exclusive relationships between the functions, as well as the actual
network scenario.

Before using MML commands, confirm the related parameter modification

precautions by referring to the fields including "Service Interrupted After
Modification" and "Caution" for the corresponding parameters in the parameter
reference.

Activation Command Examples

//Enabling the dynamic DRX function
MOD CELLALGOSWITCH:LocalCellId=0, DynDrxSwitch=DynDrxSwitch-1;

Optimization Command Examples

Scenario 1: Setting Parameters for Power Saving (QCI-based)
//(Optional) If operators do not use dynamic DRX to reduce signaling, execute the following commands to
avoid KPI fluctuations
MOD RRCCONNSTATETIMER: UlSynTimerDynDrx=10;
MOD QCIPARA: Qci=9, UeInactivityTimerDynDrxQci=35;
//Configuring DRX parameters for UEs in the out-of-synchronization state
MOD CELLDRXPARA: LocalCellId=0, LongDrxCycleUnsync=SF1280, OndurationTimerUnsync=PSF5,
DrxInactivityTimerUnsync=PSF200;
//Configuring parameters to ensure power saving for UEs that do not support DRX
MOD QCIPARA: Qci=9, UeInactiveTimerForQci=20, UlSynTimerForQci=180;

Scenario 2: Setting Parameters for Signaling Reduction (QCI-based)

//(Optional) If operators use dynamic DRX to reduce signaling, execute the following commands to ensure
the calculation accuracy of KPIs
MOD RRCCONNSTATETIMER: UlSynTimerDynDrx=20;
MOD QCIPARA: Qci=9, UeInactiveTimerForQci=200, UlSynTimerForQci=20,
UeInactivityTimerDynDrxQci=200;
//Configuring DRX parameters for UEs in the out-of-synchronization state and restoring the DRX
parameters to those configured before this function is enabled
MOD CELLDRXPARA: LocalCellId=0, LongDrxCycleUnsync=SF1280, OndurationTimerUnsync=PSF5,
DrxInactivityTimerUnsync=PSF200;
MOD QCIPARA: Qci=9, UeInactiveTimerForQci=20,UlSynTimerForQci=180;

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 62

eRAN
DRX and Signaling Control Feature Parameter
Description 5 Dynamic DRX

Scenario 3: Setting Parameters for Power Saving for UEs that Do Not Support
DRX
MOD QCIPARA: Qci=9, UeInactiveTimerForQci=20, UlSynTimerForQci=180;

Deactivation Command Examples

The following provides only deactivation command examples. You can determine
whether to restore the settings of other parameters based on actual network
conditions.
//Disabling the dynamic DRX function
MOD CELLALGOSWITCH: LocalCellId=0, DynDrxSwitch=DynDrxSwitch-0;

5.4.1.3 Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.

5.4.2 Activation Observation

To check whether dynamic DRX has been activated, use one of the following
methods.

● 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.
● If the value of L.Traffic.User.Unsyn.Drx.Avg is greater than 0, dynamic DRX
has been activated.

5.4.3 Network Monitoring

After dynamic DRX is enabled, monitor the power saving or signaling reduction
effect.

● Power saving
– Use special tools to monitor the power saving effect directly.
– Use counters to monitor the power saving effect indirectly. If the
difference between the QciPara.UeInactivityTimerDynDrxQci parameter
value and the RrcConnStateTimer.UlSynTimerDynDrx parameter value
is large, use the L.Cdrx.Active.TtiNum and L.Cdrx.Sleep.TtiNum
counters and consider the power saving performance of the UE 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. 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.
● Signaling reduction
NOTE

If the value of RrcConnStateTimer.UlSynTimerDynDrx after dynamic DRX is enabled

is less than the value of QciPara.UlSynTimerForQci before dynamic DRX is enabled,
the signaling reduction effect decreases.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 63

eRAN
DRX and Signaling Control Feature Parameter
Description 5 Dynamic DRX

– To indirectly monitor changes in signaling overhead, use the following

counters to monitor changes in the numbers of RRC connection setup
attempts in different scenarios:
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
– To indirectly monitor changes in signaling overhead, use the
L.Paging.UU.Att counter to monitor changes in the number of UEs paged
on the Uu interface.
– To directly monitor changes in signaling overhead on the Uu interface,
use the L.Signal.Num.Uu counter.
– To monitor the total change in signaling overhead on the S1 and Uu
interfaces, use the following counters:
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
NOTE

Signaling overhead for 10 RRC connection reconfigurations is equivalent to that for

one E-RAB establishment.

In signaling reduction mode, some UEs are considered to have compatibility issues
if one of the following conditions is met:

● The L.Signal.Num.DRX.Reconfig counter value increases sharply.

● 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.

Multiple RRC connection reconfigurations are performed each time the UEs with
compatibility issues switch from the out-of-synchronization state to the
synchronization state. To avoid an increase in abnormal signaling overhead caused
by such UEs, you are advised to perform the following operations:

1. Set the CellAccess.ReptSyncAvoidInd parameter to CFG to prohibit such UEs

from triggering multiple RRC connection reconfigurations.
2. Set the CellAccess.ReptSyncAvoidTime parameter to specify the period
during which such UEs are prohibited from triggering multiple RRC connection
reconfigurations.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 64

eRAN
DRX and Signaling Control Feature Parameter
Description 6 High-Mobility-Triggered Idle Mode

6 High-Mobility-Triggered Idle Mode

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. This feature is controlled by
the CellAlgoSwitch.HighMobiTrigIdleModeSwitch parameter.

6.1 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:

● Densely populated areas where people are often on the move

● Small spacing between eNodeBs

In these hot spots, handovers are easily triggered for fast-moving UEs.

Figure 6-1 shows that a UE moves between cells in a hot spot.

Figure 6-1 UE movement

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 65

eRAN
DRX and Signaling Control Feature Parameter
Description 6 High-Mobility-Triggered Idle Mode

Table 6-1 and Table 6-2 list the moving speeds and camping durations of UEs
passing through the center coverage areas of cells with radii of 300 m and 500 m.

Table 6-1 Moving speed and camping duration of a UE in a cell with a radius of
300 m
Moving Speed (km/h) Camping Duration (s)

[30–60] [18–36]

[60–120] [18–9]

> 120 <9

Table 6-2 Moving speed and camping duration of a UE in a cell with a radius of
500 m
Moving Speed (km/h) Camping Duration (s)

[30–60] [30–60]

[60–120] [15–30]

> 120 < 15

In reality, most UEs do not pass through the cell center and the camping duration
of these UEs is even shorter.
Figure 6-2 shows the numbers of access requests triggered by heartbeats.

Figure 6-2 Numbers of access requests triggered by heartbeats

NOTE

In Figure 6-2, 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.

Based on the data shown in Figure 6-2, UEs moving at high speeds have the
following common characteristics:
● The heartbeat periods for most services are 180s or longer.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 66

eRAN
DRX and Signaling Control Feature Parameter
Description 6 High-Mobility-Triggered Idle Mode

● 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.
● 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
High-mobility-triggered idle mode is controlled by the
CellAlgoSwitch.HighMobiTrigIdleModeSwitch parameter.
As shown in Figure 6-3, to avoid a handover, after receiving the measurement
report from a UE, the eNodeB triggers the S1 release procedure and instructs the
UE to enter idle mode when all of the following conditions are met:
● The moving speed of the UE is greater than or equal to 30 km/h during the
camping.
● The UE does not send packets when it is camping on a cell.
NOTE

In NSA Option 3x networking, when a UE camps on a cell, the eNodeB considers by

default that the UE does not send packets.
● The camping duration is greater than or equal to 10s.
As the UE has data to transmit only when a heartbeat period elapses, instructing
the UE to enter idle mode has no impact on the UE's services.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 67

eRAN
DRX and Signaling Control Feature Parameter
Description 6 High-Mobility-Triggered Idle Mode

Figure 6-3 Working mechanism of high-mobility-triggered idle mode

If a high-speed UE is in the EN-DC state (with an SCG added or in the SN

terminated MCG bearer state) and the high-mobility-triggered idle mode function
is enabled by setting the CellAlgoSwitch.HighMobiTrigIdleModeSwitch
parameter to ENABLE, the UE enters the idle mode because it has no packet to
transmit on the LTE side. In this case, the LTE side releases the secondary cell
group (SCG), causing data service interruption or service drops on the NR side.
The function of high-mobility-triggered idle mode control for NSA UEs specifies
whether fast-moving UEs in the EN-DC state switch to idle mode. This function is
controlled by the NSA_HIGH_MOBI_TRIG_IDLE_SW option of the
NsaDcMgmtConfig.NsaDcAlgoExtSwitch parameter. For details about the SN
terminated MCG bearer state, see EPC-based NSA Performance Enhancement.
● If the high-mobility-triggered idle mode function is enabled and the
NSA_HIGH_MOBI_TRIG_IDLE_SW option of the
NsaDcMgmtConfig.NsaDcAlgoExtSwitch parameter is deselected, the base
station does not release fast-moving UEs in the EN-DC state so that they do
not switch to idle mode.
● If the high-mobility-triggered idle mode function is enabled and the
NSA_HIGH_MOBI_TRIG_IDLE_SW option of the
NsaDcMgmtConfig.NsaDcAlgoExtSwitch parameter is selected, the base
station releases fast-moving UEs in the EN-DC state so that they will switch to
idle mode.
NOTE

The NSA_HIGH_MOBI_TRIG_IDLE_SW option of the

NsaDcMgmtConfig.NsaDcAlgoExtSwitch parameter takes effect only when the
CellAlgoSwitch.HighMobiTrigIdleModeSwitch parameter is set to ENABLE.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 68

eRAN
DRX and Signaling Control Feature Parameter
Description 6 High-Mobility-Triggered Idle Mode

6.2 Network Analysis

6.2.1 Benefits

Gains
This 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.

Most Beneficial Scenarios

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 this feature
be enabled.

Gain Measurement
If the number of handovers after this feature is enabled is much smaller than that
before this feature is enabled, this feature has taken effect and the signaling
overhead caused by handovers is reduced.

6.2.2 Impacts

Network Impacts
This function 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.

If high-mobility-triggered idle mode control for NSA UEs is enabled and there are
fast moving UEs in the EN-DC state (with an SCG added or in the SN terminated
MCG bearer state), the signaling impact caused by frequent handovers can be
avoided. However, the number of SCG releases increases and the value of
L.UECNTX.Release.HighSpeed increases.

Function Impacts
None

6.3 Requirements

6.3.1 Licenses
The following are FDD license requirements.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 69

eRAN
DRX and Signaling Control Feature Parameter
Description 6 High-Mobility-Triggered Idle Mode

Feature ID Feature Name Model Sales Unit

LOFD-001105 Dynamic DRX LT1S00DDRX00 per Cell

6.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated, if there are any.
For detailed operations, see the relevant feature documents.

Prerequisite Functions
RAT Function Name Function Switch Reference Description

FDD Dynamic DRX CellAlgoSwitch.Dy DRX and Dynamic DRX

nDrxSwitch Signaling must be enabled
Control before high-
mobility-triggered
idle mode is
enabled.

FDD High-mobility- CellAlgoSwitch.Hig DRX and The high-

triggered idle hMobiTrigIdleMo- Signaling mobility-triggered
mode deSwitch Control idle mode
function must be
enabled before
high-mobility-
triggered idle
mode control for
NSA UEs is
enabled.

Mutually Exclusive Functions

None

6.3.3 Hardware
The hardware described in this section may require compatibility between each
other. For details, see the technical specifications and hardware description of the
corresponding hardware in 3900 & 5900 Series Base Station Product
Documentation.

Base Station Models

3900 and 5900 series base stations (macro base stations)

Boards
No requirements

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 70

eRAN
DRX and Signaling Control Feature Parameter
Description 6 High-Mobility-Triggered Idle Mode

RF Modules
No requirements

6.3.4 Others
None

6.4 Operation and Maintenance

6.4.1 Data Configuration

6.4.1.1 Data Preparation

Table 6-3 and Table 6-4 describe the parameters used for function activation and
optimization, respectively.

Table 6-3 Parameters used for activation

Parameter Name Parameter ID Option Setting Notes

Local cell ID CellAlgoSwitch.LocalC None Set this parameter

ellId based on the
network plan.

High Mobility CellAlgoSwitch.HighM None Set this parameter

Triggered Idle obiTrigIdleModeS- to ENABLE if the
Mode Switch witch high-mobility-
triggered idle
mode function is
required.

Table 6-4 Parameters used for optimization

Parameter Name Parameter ID Option Setting Notes

NSA DC Algorithm NsaDcMgmtConfig.Ns NSA_HIGH It is recommended

Extension Switch aDcAlgoExtSwitch _MOBI_TRI that this option be
G_IDLE_SW deselected.

6.4.1.2 Using MML Commands

Before using MML commands, refer to 6.3.2 Software and complete the
parameter configurations for related functions based on the dependency
relationships between the functions, as well as the actual network scenario.
Before using MML commands, confirm the related parameter modification
precautions by referring to the fields including "Service Interrupted After

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 71

eRAN
DRX and Signaling Control Feature Parameter
Description 6 High-Mobility-Triggered Idle Mode

Modification" and "Caution" for the corresponding parameters in the parameter

reference.

Activation Command Examples

//Enabling the high-mobility-triggered idle mode function
MOD CELLALGOSWITCH: LocalCellId=0, HighMobiTrigIdleModeSwitch=ENABLE;

Optimization Command Examples

//Setting the high-mobility-triggered idle mode control function
MOD NSADCMGMTCONFIG: LocalCellId=0, NsaDcAlgoExtSwitch=NSA_HIGH_MOBI_TRIG_IDLE_SW-0;

Deactivation Command Examples

//Disabling the high-mobility-triggered idle mode function
MOD CELLALGOSWITCH: LocalCellId=0, HighMobiTrigIdleModeSwitch=DISABLE;

6.4.1.3 Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.

6.4.2 Activation Observation

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.

6.4.3 Network Monitoring

After this feature is enabled, use counters to monitor performance:
● If the L.UECNTX.Release.HighSpeed counter value is greater than 0, this
feature has taken effect.
● 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.

Table 6-5 Counters for performance monitoring

Counter ID Counter Name

1526726996 L.HHO.IntraeNB.IntraFreq.ExecAttOut

1526726999 L.HHO.IntraeNB.InterFreq.ExecAttOut

1526727002 L.HHO.IntereNB.IntraFreq.ExecAttOut

1526727005 L.HHO.IntereNB.InterFreq.ExecAttOut

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 72

eRAN
DRX and Signaling Control Feature Parameter
Description 7 Parameters

7 Parameters

The following hyperlinked EXCEL files of parameter documents match the

software version with which this document is released.

● Node Parameter Reference: contains device and transport parameters.

● eNodeBFunction Parameter Reference: contains all parameters related to
radio access functions, including air interface management, access control,
mobility control, and radio resource management.
● eNodeBFunction Used Reserved Parameter List: contains the reserved
parameters that are in use and those that have been disused.
NOTE

You can find the EXCEL files of parameter reference and used reserved parameter list for
the software version used on the live network from the product documentation delivered
with that version.

FAQ 1: How do I find the parameters related to a certain feature from

parameter reference?

Step 1 Open the EXCEL file of parameter reference.

Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, LOFD-001016 or
TDLOFD-001016.

Step 3 Click OK. All parameters related to the feature are displayed.

----End

FAQ 2: How do I find the information about a certain reserved parameter

from the used reserved parameter list?

Step 1 Open the EXCEL file of the used reserved parameter list.

Step 2 On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT
columns to locate the reserved parameter, which may be only a bit of a parameter.
View its information, including the meaning, values, impacts, and product version
in which it is activated for use.

----End

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 73

eRAN
DRX and Signaling Control Feature Parameter
Description 8 Counters

8 Counters

The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● eNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.

NOTE

You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.

FAQ: How do I find the counters related to a certain feature from

performance counter reference?

Step 1 Open the EXCEL file of performance counter reference.

Step 2 On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID, for example, LOFD-001016 or
TDLOFD-001016.
Step 3 Click OK. All counters related to the feature are displayed.

----End

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 74

eRAN
DRX and Signaling Control Feature Parameter
Description 9 Glossary

9 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 75

eRAN
DRX and Signaling Control Feature Parameter
Description 10 Reference Documents

10 Reference Documents

1. 3GPP TS 36.321: "Medium Access Control (MAC) protocol specification"

2. 3GPP TS 23.203: "Policy and charging control architecture"
3. 3GPP TS 36.133: "Requirements for support of radio resource management"
4. Mobility Management in Connected Mode
5. Uplink Scheduling
6. Terminal Awareness Differentiation
7. Flexible User Steering
8. Carrier Aggregation
9. VoLTE
10. High Speed Mobility
11. Physical Channel Resource Management
12. Superior Uplink Coverage (FDD)
13. Short TTI (FDD)
14. Energy Conservation and Emission Reduction
15. LTE FDD and NR Dynamic Spectrum Sharing
16. LTE FDD and NR Hybrid Dynamic Spectrum Sharing
17. Automatic Congestion Handling
18. EPC-based NSA Performance Enhancement

Issue 01 (2023-09-10) Copyright © Huawei Technologies Co., Ltd. 76