DRX (5g Ran6.1 - Draft A)

5G RAN
DRX Feature Parameter Description
Issue Draft A
Date 2021-12-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2022. 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 Draft A Copyright © Huawei Technologies Co., Ltd. i

(2021-12-30)
5G RAN
DRX Feature Parameter Description Contents
Contents
1 Change History.........................................................................................................................1
1.1 5G RAN6.1 Draft A (2021-12-30)...................................................................................................................................... 1
2 About This Document.............................................................................................................3

2.1 General Statements................................................................................................................................................................ 3
2.2 Features in This Document.................................................................................................................................................. 3
2.3 Differences Between NR FDD and NR TDD................................................................................................................... 4
2.4 Differences Between NSA and SA..................................................................................................................................... 4
2.5 Differences Between High Frequency Bands and Low Frequency Bands............................................................ 4
3 Overview....................................................................................................................................5
4 DRX............................................................................................................................................. 6
4.1 Principles.................................................................................................................................................................................... 6
4.1.1 Basic Concepts...................................................................................................................................................................... 6
4.1.2 QCI- and RFSP-based DRX Parameter Configuration........................................................................................... 12
4.1.3 Entering and Exiting DRX Mode................................................................................................................................... 13
4.1.4 Running DRX Mode.......................................................................................................................................................... 15
4.1.4.1 Starting a DRX Cycle..................................................................................................................................................... 16
4.1.4.2 Switching Between Active Time and Sleep Time................................................................................................ 16
4.1.4.3 Switching Between Long and Short DRX Cycles................................................................................................. 19
4.2 Network Analysis.................................................................................................................................................................. 19
4.2.1 Benefits................................................................................................................................................................................. 19
4.2.2 Impacts.................................................................................................................................................................................. 20
4.3 Requirements......................................................................................................................................................................... 35
4.3.1 Licenses................................................................................................................................................................................. 35
4.3.2 Software................................................................................................................................................................................35
4.3.3 Hardware.............................................................................................................................................................................. 36
4.3.4 Others.................................................................................................................................................................................... 36
4.4 Operation and Maintenance............................................................................................................................................. 36
4.4.1 Data Configuration........................................................................................................................................................... 36
4.4.1.1 Data Preparation............................................................................................................................................................ 36
4.4.1.2 Using MML Commands............................................................................................................................................... 41
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 42
4.4.2 Activation Verification..................................................................................................................................................... 42
Issue Draft A Copyright © Huawei Technologies Co., Ltd. ii

(2021-12-30)
5G RAN
DRX Feature Parameter Description Contents
4.4.3 Network Monitoring......................................................................................................................................................... 42
5 Parameters.............................................................................................................................. 44
6 Counters.................................................................................................................................. 45
7 Glossary................................................................................................................................... 46
8 Reference Documents...........................................................................................................47
Issue Draft A Copyright © Huawei Technologies Co., Ltd. iii

(2021-12-30)
5G RAN
DRX 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 5G RAN6.1 Draft A (2021-12-30)

This issue introduces the following changes to 5G RAN5.1 01 (2021-03-05).
Technical Changes
Change Description Parameter RAT Base Station Model
Change
Removed the mutually exclusive None Low- ● 3900 and 5900 series
relationship between DRX and High- frequency base stations
speed Railway Superior Experience in TDD ● DBS3900 LampSite
low-frequency TDD scenarios. For and DBS5900
details, see 4.3.2 Software. LampSite
Added the impact relationship None FDD ● 3900 and 5900 series
between DRX and High-speed Low- base stations
Railway Superior Experience in low- frequency ● DBS3900 LampSite
frequency scenarios. For details, see TDD and DBS5900
4.2.2 Impacts. LampSite
Added the impact relationship of DRX None Low- ● 3900 and 5900 series
with exit from DRX and BWP2 of frequency base stations
weak-coverage UEs in low-frequency TDD ● DBS3900 LampSite
TDD scenarios. For details, see 4.2.2 and DBS5900
Impacts. LampSite
Issue Draft A Copyright © Huawei Technologies Co., Ltd. 1

(2021-12-30)
5G RAN
DRX Feature Parameter Description 1 Change History
Editorial Changes
Revised descriptions in this document.

(2021-12-30)
5G RAN
DRX Feature Parameter Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
Feature Parameter Description documents are 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.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in Feature
Parameter Description documents apply only to the corresponding software
release. For future software releases, refer to the corresponding updated product
documentation.
2.2 Features in This Document

This document describes the following features.
Feature ID Feature Name Chapter/Section
FBFD-021103 DRX 4 DRX

(2021-12-30)
5G RAN
DRX Feature Parameter Description 2 About This Document
2.3 Differences Between NR FDD and NR TDD

Function Difference Chapter/Section
Name
DRX None 4 DRX
2.4 Differences Between NSA and SA

Name
DRX Supported in both NSA 4 DRX

and SA networking, with
the following
differences:
In NSA networking, the
gNodeB does not
instruct a UE in DRX
mode to exit DRX mode
when gap-assisted
measurement is started.
In SA networking, the
gNodeB instructs a UE in
DRX mode to exit DRX
mode when gap-assisted
measurement is started.
2.5 Differences Between High Frequency Bands and

Low Frequency Bands
This document refers to frequency bands belonging to FR1 (410–7125 MHz) as
low frequency bands, and those belonging to FR2 (24250–52600 MHz) as high
frequency bands. For details about FR1 and FR2, see section 5.1 "General" in 3GPP
TS 38.104 V15.5.0.

Name
DRX Supported only in low 4 DRX

frequency bands

(2021-12-30)
5G RAN
DRX Feature Parameter Description 3 Overview
3 Overview
With the ever increasing diversity of applications, terminal standby time has
become a major concern for end users. Many smart-terminal applications use
small sparse packets or heartbeat packets. These applications cause frequent
communications between UEs and base stations. However, if UEs remain in
RRC_CONNECTED mode and always monitor the physical downlink control
channel (PDCCH), a lot of power will be consumed.
To reduce UE power consumption, 3GPP has introduced Discontinuous Reception
(DRX) for NR and Huawei provides the 3GPP-compliant DRX feature accordingly.
DRX enables UEs in connected mode to periodically suspend monitoring the
PDCCH, thereby reducing the power consumption of UEs, especially when UEs are
performing the following services:
● Periodic transmission of continuous small packets
● Delay-insensitive services
● Services characterized by small sparse packets

(2021-12-30)
5G RAN
DRX Feature Parameter Description 4 DRX
4 DRX
DRX is short for discontinuous reception. When the UE needs to receive downlink
(DL) data or signaling, the UE turns on its receiver. In other situations, the UE
turns off its receiver to reduce power consumption. This feature is controlled by
the BASIC_DRX_SW option of the
NRDUCellUePwrSaving.NrDuCellDrxAlgoSwitch parameter.
4.1 Principles
4.1.1 Basic Concepts

This section describes the basic concepts related to DRX.
On Duration
When DRX is used, a UE does not always keep its receiver off but periodically
turns on its receiver. Within a period of time after the DRX cycle starts, the UE
monitors the PDCCH for incoming signaling. This period is called an On Duration
and its length is defined by the On Duration Timer, which is specified by the
gNBDUDrxParamGroup.OnDurationTimer parameter.
DRX Cycle
A DRX cycle is the interval between two occurrences of On Duration, as shown in
Figure 4-1.
A DRX cycle can be a long DRX cycle or short DRX cycle. Each DRX cycle is
divided into active time and sleep time depending on whether the UE monitors
the PDCCH.

(2021-12-30)
5G RAN
Figure 4-1 DRX cycle
In a DRX cycle, after the On Duration period ends, the UE may switch between the
active time and sleep time (for details, see 4.1.4.2 Switching Between Active
Time and Sleep Time).
NOTE
An On Duration period is within the active time.
Active Time
In active time, the UE turns on its receiver and monitors the PDCCH.
According to section 5.7 "Discontinuous Reception (DRX)" in 3GPP TS 38.321

V15.6.0, a UE is in active time if one of the following conditions is met:
● The On Duration Timer, DRX Inactivity Timer, DL Retransmission Timer, UL

Retransmission Timer, or Contention Resolution Timer is running. For details
about the timers, see DRX Timers.
● During the non-contention-based random access (RA), the UE has received a
random access response but has not received the downlink control
information (DCI) that indicates a new transmission.
● The UE has sent a scheduling request (SR) on the physical uplink control
channel (PUCCH) and the SR is pending.
Sleep Time
Inactive time in a DRX cycle is called sleep time. During sleep time, the UE turns
off its receiver.
Long DRX Cycle

Using a long DRX cycle can save more UE power. The long DRX cycle is specified
by the gNBDrxParamGroup.LongCycle parameter.
Short DRX Cycle

A short DRX cycle delivers better service experience than a long DRX cycle but
saves less power. The short DRX cycle is specified by the
gNBDrxParamGroup.ShortCycle parameter.
By default, a long DRX cycle is configured for the UE. If a short DRX cycle is
configured for the UE, the UE will determine when to use the long or short DRX

(2021-12-30)
5G RAN
cycle based on the process described in 4.1.4.3 Switching Between Long and
Short DRX Cycles.
DRX Timers
The following tables describe DRX timers.
NOTE
The parameter in the table of a timer specifies the value of this timer.
Table 4-1 On Duration Timer

Item Description
Parameter gNBDUDrxParamGroup.OnDurationTimer
ID
Function This timer starts at the beginning of a DRX cycle. The UE

monitors the PDCCH before the timer expires.
Start This timer starts at the first subframe of a DRX cycle. For details,
see 4.1.4.1 Starting a DRX Cycle.
Timing Timing is based on milliseconds.
Stop This timer stops upon expiry.
Expiry Upon expiry, this timer stops timing.
Table 4-2 DRX Inactivity Timer

Item Description
Parameter gNBDUDrxParamGroup.DrxInactivityTimer
ID
Function This timer is used for a UE to determine whether to extend the

active time because of the arrival of new data. It also provides a
reference for the UE to determine when to use a short DRX cycle.
Start This timer starts or restarts when the UE successfully decodes a

PDCCH that indicates a new UL or DL transmission (UL grant or
DL data indication) for this UE.
Timing Timing is based on milliseconds.

(2021-12-30)
5G RAN
Item Description
Expiry Upon expiry, this timer stops timing and one of the following
operations is performed:
● If the UE is in a long DRX cycle:
– If a short DRX cycle has been configured, the Short Cycle
Timer starts and the short DRX cycle starts.
– If no short DRX cycle is configured, the long DRX cycle
continues.
● If the UE is in a short DRX cycle, the Short Cycle Timer
restarts.
Table 4-3 Short Cycle Timer

Item Description
Parameter gNBDrxParamGroup.ShortCycleTimer
ID
Function This timer specifies the lifetime of a short DRX cycle, that is, the
number of consecutive repetitions of a short DRX cycle. If
gNBDrxParamGroup.ShortCycleTimer is set to 0, the
gNBDrxParamGroup.ShortCycle parameter does not take effect.
Start After the DRX Inactivity Timer expires, the Short Cycle Timer
starts or restarts depending on the following:
● If the UE is in a long DRX cycle:
– If a short DRX cycle has been configured, the short DRX
cycle starts and the Short Cycle Timer starts.
– If no short DRX cycle is configured, the long DRX cycle
continues and the Short Cycle Timer does not start.
● If the UE is in a short DRX cycle, the Short Cycle Timer
restarts.
Timing Timing is based on the number of repetitions of a short DRX

cycle.
Expiry Upon expiry, this timer stops timing and the UE starts to use a
long DRX cycle.
Table 4-4 DL Retransmission Timer

Item Description
Parameter gNBDUDrxParamGroup.DrxRetransTimer
ID

(2021-12-30)
5G RAN
Item Description
Function This timer specifies the maximum period of time the UE waits for
downlink retransmission in active time.
NOTE
If the UE has not received the downlink retransmitted data before this
timer expires, the UE will no longer accept it.
Start This timer starts or restarts when the DL HARQ-RTT Timer

expires and the UE does not decode the corresponding downlink
data correctly.
Timing Timing is based on the number of slots.
Stop ● This timer stops when the DL HARQ-RTT Timer starts.

● This timer stops upon expiry.
Table 4-5 UL Retransmission Timer

Item Description
Parameter gNBDUDrxParamGroup.DrxRetransTimer
ID
Function This timer specifies the maximum period of time the UE waits for
uplink retransmission in active time.
NOTE
If the UE has not received the uplink grant before this timer expires, the
UE considers that retransmission is no longer needed.
Start This timer starts or restarts when the UL HARQ-RTT Timer

expires.
Timing Timing is based on the number of slots.
Stop ● This timer stops when the UL HARQ-RTT Timer starts.

● This timer stops upon expiry.
Table 4-6 DL HARQ-RTT Timer

Item Description
Parameter N/A (The timer length is fixed to 56 OFDM symbols.)

ID

(2021-12-30)
5G RAN
Item Description
Function This timer specifies the minimum interval between the time
when the gNodeB receives the HARQ feedback of a downlink
data transmission and the time when the downlink data
retransmission starts. This timer is used to determine when to
start the DL Retransmission Timer.
Start This timer starts when the UE returns the ACK/NACK for a
downlink data transmission on the PUCCH.
Timing Timing is based on the number of OFDM symbols.
Expiry Upon expiry, this timer stops timing. If the UE does not decode
the corresponding downlink data correctly, the DL Retransmission
Timer starts.
Table 4-7 UL HARQ-RTT Timer

Item Description
Parameter N/A (The timer length is fixed to 56 OFDM symbols.)

ID
Function This timer specifies the minimum interval between the time
when the UE completes data transmission on the PUSCH and the
time when the UE receives the next UL Grant on the PDCCH. This
timer is used to determine when to start the UL Retransmission
Timer.
Start This timer starts or restarts each time data transmission on the
PUSCH completes.
Timing Timing is based on the number of OFDM symbols.
Expiry Upon expiry, this timer stops timing and the UL Retransmission
Timer starts.
Table 4-8 Contention Resolution Timer

Item Description
Parameter N/A (The timer length is fixed to 64 subframes.)

ID
Function This timer specifies the time during which the UE waits for a
contention resolution in a contention-based random access
procedure.

(2021-12-30)
5G RAN
Item Description
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 subframes.
Stop This timer stops when the UE receives a contention resolution

message.
Expiry Upon expiry, this timer stops timing and the UE retransmits a
preamble.
4.1.2 QCI- and RFSP-based DRX Parameter Configuration
QCI-based DRX Parameter Configuration

Quality of service (QoS) is a measure that helps define the level of service and
provides an indication of customer satisfaction. The QoS class identifier (QCI) is
used to identify the QoS class of a data radio bearer (DRB). QCI-based DRX
parameter configuration allows different DRX parameter groups to be configured
for different QCIs. The NRCellQciBearer and NRDUCellQciBearer MOs are used
to bind a QCI to a DRX parameter group (configured using the
gNBDrxParamGroup and gNBDUDrxParamGroup MOs).
DRX takes effect on a UE only when all of the following conditions are met:
● The QCIs added to the NRCellQciBearer and NRDUCellQciBearer MOs must

exist in the gNBQciBearer MO.
● All QCIs used by the UE are bound to valid DRX parameter groups. That is,
neither NRCellQciBearer.DrxParamGroupId nor
NRDUCellQciBearer.DuDrxParamGroupId is set to 255.
A UE may have multiple radio bearers, each corresponding to a QCI. Different

QCIs have different priorities (specified by the gNBQciBearer.PriorityLevel
parameter). After DRX takes effect on the UE, the UE uses the DRX parameter
group bound with the QCI of the highest priority.
NOTE
In SA networking, the core network, that is 5GC, notifies the gNodeB of the 5G QoS
Identifier (5QI) corresponding to each QoS flow. For detailed description about QCI and
5QI, see QoS Management.
Each QCI is bound to a set of DRX parameter groups. Different QCIs can be bound to the
same set of DRX parameter groups.
DRX is not recommended for QCI 1, QCI 65, QCI 66, and QCI 69. Therefore, DRX parameter
groups are not added or bound for such QCIs by default. If there are DRX parameter groups
for QCI 1, QCI 65, or QCI 66, the DRX parameter group is selected for a UE by QCI priority
in the following sequence: QCI 1 > QCI 65 > QCI 66 > other QCIs.
For QCI 2, QCI 3, QCI 5, QCI 7, QCI 75, QCI 79, QCI 4, QCI 6, QCI 8, QCI 9, and QCI 70, the
system adds and binds DRX parameter groups by default. DRX parameter groups must be
manually added and bound for QCIs other than the preceding ones.

(2021-12-30)
5G RAN
RFSP-based DRX Parameter Configuration

An operator registers RAT/frequency selection priorities (RFSPs) (ranging from 1 to
256) for UEs with the user data management (UDM) database. In this way,
gNodeBs can perform RFSP-based special processing for services performed by
certain UEs and provide UE-specific services based on UEs' service characteristics
and loading status. RFSP-based DRX parameter configuration is to configure
different DRX parameter groups for different RFSPs. Specifically, RFSPs are bound
to DRX parameter groups (specified in the gNBDrxParamGroup and
gNBDUDrxParamGroup MOs) using the gNBRfspConfig and gNBDuRfspConfig
MOs. For details, see Flexible User Steering.
If both QCI bearers and RFSPs are configured for UEs, the gNodeB preferentially
configures DRX parameter groups based on RFSPs.
4.1.3 Entering and Exiting DRX Mode

As shown in Figure 4-2, in a cell where the DRX feature is enabled (by selecting
the BASIC_DRX_SW option of the
NRDUCellUePwrSaving.NrDuCellDrxAlgoSwitch parameter), the base station
performs the following operations for a UE each time DRX is triggered (see
Triggering Scenarios).
● For a UE not in DRX mode, the base station checks whether the UE meets
conditions for entering DRX mode (see Entering Conditions):
– If the conditions are met, the base station sends the UE the DRX
configuration. That is, the base station configures the DRX-Config field in
an RRCConnectionReconfiguration message (NSA networking) or an
RRCReconfiguration message (SA networking) and then sends this
message to the UE. The UE then enters DRX mode based on parameter
settings in this field.
– If the conditions are not met, the UE stays in non-DRX mode.
● For a UE in DRX mode, the base station checks whether the UE meets the
DRX exiting conditions (see Exiting Conditions):
– If the DRX exiting conditions are met, the base station sends the UE an
RRCConnectionReconfiguration message (in NSA networking) or an
RRCReconfiguration message (in SA networking) with the DRX-Config
field unspecified. After receiving the message, the UE immediately clears
all the DRX parameters stored locally and exits DRX mode.
– If the DRX exiting conditions are not met, the UE stays in DRX mode.
NOTE
If the UE has multiple radio bearers with different QCIs, the DRX parameter
group bound with the QCI of the highest priority is used. The radio bearer with
the highest QCI priority may change. Therefore, DRX parameter settings may be
updated when the UE stays in DRX mode.

(2021-12-30)
5G RAN
Figure 4-2 Entering and exiting DRX mode
Triggering Scenarios
● The UE initially accesses the network.
● The UE performs handovers.
● The base station creates or deletes a radio bearer for the UE.
● The base station configures measurement gaps for the UE.
● In carrier aggregation (CA) scenarios, the base station adds or removes a
secondary component carrier (SCC) for the UE.
● The base station delivers the periodic sounding reference signal (SRS)
configuration of the UE.
Entering Conditions
A UE enters DRX mode when all the following conditions are met:
● The DRX feature is enabled for cells in common scenarios. In CA scenarios, the
DRX feature is enabled for both the PCell and SCell of the UE.
● The UE reports that DRX is supported, that is, the MAC-ParametersXDD-Diff
IE contains the longDRX-Cycle field. For details, see section 6.3.3 "UE
capability information elements" in 3GPP TS 38.331 V15.6.0.
● All radio bearers set up for the UE support the DRX feature, that is, DRX
parameter groups have been configured for QCIs of these radio bearers and
the DRX parameter group IDs are valid (neither
NRCellQciBearer.DrxParamGroupId nor
NRDUCellQciBearer.DuDrxParamGroupId is set to 255).
● Long DRX cycle (specified by gNBDrxParamGroup.LongCycle) ≤ {TATimer
length (NRDUCellUlTaConfig.UlTimeAlignmentTimer) x 1/6}

(2021-12-30)
5G RAN
Even if all the preceding conditions are met, the UE does not immediately enter
DRX mode in the following situations:
● The UE constantly performs gap-assisted measurement.
● If DRX exit of UEs performing full-buffer services is enabled in a cell (with the
FULL_BUFFER_UE_EXIT_DRX_SW option of the
NRDUCellUePwrSaving.NrDuCellDrxAlgoSwitch parameter selected) and
the UE is identified as a UE performing full-buffer services, the UE does not
enter the DRX mode. When the UE is no longer identified as a UE performing
full-buffer services, the gNodeB instructs the UE to enter DRX mode through
an RRC connection reconfiguration message.
NOTE
● The UE can perform reportCGI measurements only after entering the DRX sleep time.
Therefore, when the gNodeB instructs the UE to report the NCGI or ECGI, the UE enters
the DRX mode.
● For UEs in RRC_CONNECTED mode, DRX-related parameter modifications take effect
only upon the next RRC connection reconfiguration.
Exiting Conditions
The gNodeB instructs the UE to exit DRX mode when any of the following
conditions is met:
● If DRX is disabled in a cell in common scenarios, the gNodeB instructs the UE
to exit DRX mode during the next RRC connection reconfiguration procedure.
In CA scenarios, if DRX is disabled in either the PCell or SCell of a UE, the
gNodeB instructs the UE to exit DRX mode during the next RRC connection
reconfiguration procedure. (If an SCC that does not support DRX is added for
the UE, the RRC connection reconfiguration is triggered immediately.)
● The UE has set up a radio bearer (for example, a delay-sensitive radio bearer)
for which DRX does not take effect. That is, the QCI of such a radio bearer is
not bound to any DRX parameter group or is bound to a parameter group
whose ID is 255 (NRCellQciBearer.DrxParamGroupId or
NRDUCellQciBearer.DuDrxParamGroupId is set to 255).
● Long DRX cycle (specified by gNBDrxParamGroup.LongCycle) > {TATimer
length (NRDUCellUlTaConfig.UlTimeAlignmentTimer) x 1/6}
In SA networking, the gNodeB instructs the UE to exit DRX mode when gap-
assisted measurement is started. In NSA networking, the gNodeB does not instruct
the UE to exit DRX mode when gap-assisted measurement is started.
4.1.4 Running DRX Mode

After a UE enters DRX mode, a DRX cycle will start (see 4.1.4.1 Starting a DRX
Cycle) if certain conditions are met, and the base station will switch the UE
between active time and sleep time (see 4.1.4.2 Switching Between Active Time
and Sleep Time) and between a long DRX cycle and a short DRX cycle (see
4.1.4.3 Switching Between Long and Short DRX Cycles) based on network
environments and parameter configurations.

(2021-12-30)
5G RAN
4.1.4.1 Starting a DRX Cycle

Upon entering DRX mode, a UE does not immediately start the On Duration Timer
for a DRX cycle. The On Duration Timer starts, which means, the UE starts a DRX
cycle, in the following scenarios:
● A long DRX cycle is started when the following conditions are met:
[(SFN x 10) + SSFN] modulo (gNBDrxParamGroup.LongCycle) = DRX Start
Offset
● A short DRX cycle is started when the following conditions are met:
– The value of gNBDrxParamGroup.ShortCycleTimer is not 0.
– [(SFN * 10) + SSFN] modulo (gNBDrxParamGroup.ShortCycle) = (DRX
Start Offset) modulo (gNBDrxParamGroup.ShortCycle)
In the preceding formulas:
● SFN: system frame number
● SSFN: system subframe number
● modulo (x): The modulo operation is performed on x.
● gNBDrxParamGroup.LongCycle and gNBDrxParamGroup.ShortCycle specify
the durations of the long and short DRX cycles, respectively. The length of the
long DRX cycle is K times of that of the short DRX cycle. K is an integer
greater than or equal to 2.
● DRX Start Offset is the start offset of the long DRX cycle, and (DRX Start
Offset) modulo (gNBDrxParamGroup.ShortCycle) is the start offset of the
short DRX cycle.
● The base station notifies the UE of the cycle duration and DRX Start Offset
using the RRCConnectionReconfiguration message (in NSA networking) or the
RRCReconfiguration message (in SA networking).
NOTE
If a UE reports that it supports long DRX cycles, that is, the MAC-ParametersXDD-Diff IE
contains the longDRX-Cycle field, the UE can use a long DRX cycle. If a UE reports that it
supports short DRX cycles, that is, the MAC-ParametersXDD-Diff IE contains the shortDRX-
Cycle field, the UE can use a short DRX cycle. For details, see section 6.3.3 "UE capability
information elements" in 3GPP TS 38.331 V15.6.0.
4.1.4.2 Switching Between Active Time and Sleep Time

Switching between active time and sleep time depends on DRX timers and other
service processes.
The following describes how the UE receiver switches between the active time and
sleep time based on different timers and other service processes. For details about
the timer running mechanisms, see DRX Timers.
● When the On Duration Timer or DRX Inactivity Timer is running, the UE is in
the active time, as shown in Figure 4-3.

(2021-12-30)
5G RAN
Figure 4-3 Active time determined by the On Duration Timer and DRX
Inactivity Timer
● When the DL HARQ-RTT Timer expires and the UE does not correctly decode
the corresponding downlink data, the DL Retransmission Timer is triggered.
During the running of the DL Retransmission Timer, the UE is in the active
time, as shown in Figure 4-4.
Figure 4-4 Active time determined by the DL HARQ-RTT Timer and DL

Retransmission Timer
● When the UL HARQ-RTT Timer expires, the UL Retransmission Timer starts.

During the running of the UL Retransmission Timer, the UE is in active time,
as shown in Figure 4-5. For details about the periods when the UE is in DRX
active time, see Active Time.

(2021-12-30)
5G RAN
Figure 4-5 Active time determined by the UL HARQ-RTT Timer and UL

Retransmission Timer
The gNodeB and UE use their own DRX timers. That is, the gNodeB determines
whether a UE is in the active or sleep time based on the timers on the gNodeB.
When the gNodeB mistakenly detects SRs from a UE in the DRX sleep time or the
UE in the DRX active time fail to detect DCI from the gNodeB, the DRX Inactivity
Timer and Short Cycle Timer are inconsistent on the gNodeB and UE sides. As a
result, the gNodeB may determine that the UE is in the DRX active time while it is
actually in the DRX sleep time, which causes the following impacts:
● The UE does not respond to the scheduling command from the gNodeB, and
the scheduling result is discontinuous transmission (DTX). This increases the
block error rate (BLER) over the air interface and the number of used PDCCH
control channel elements (CCEs).
● UE's measurement results (such as the SRS and CSI-RS feedback) are
inaccurate.
To address this issue, the gNodeB checks the DRX state of UEs based on the
scheduling feedback.
● In the uplink, if the UL_BASED_DRX_STATUS_DETECT_SW option of the
NRDUCellUePwrSaving.NrDuCellDrxAlgoSwitch parameter is selected, the
gNodeB starts DRX state evaluation based on uplink scheduling feedback.
● In the downlink, the gNodeB starts DRX state evaluation based on downlink
scheduling feedback by default.
After DRX state evaluation based on scheduling feedback is started, the gNodeB
determines that a UE is in the DRX sleep time and therefore stops the DRX
Inactivity Timer and Short Cycle Timer if any of the following conditions is met in
the uplink or downlink:
● When the gNodeB detects an SR from the UE in the DRX sleep time, the
number of consecutive DTXs in the uplink or downlink scheduling feedback is
greater than or equal to the DRX sleep time detection threshold. The DRX
sleep time detection threshold is specified by the
NRDUCellUePwrSaving.DrxSleepStateDetectThld parameter.
● In other scenarios, the number of consecutive DTXs in the uplink or downlink
scheduling feedback is twice the DRX sleep time detection threshold or
greater.

(2021-12-30)
5G RAN
4.1.4.3 Switching Between Long and Short DRX Cycles

The gNodeB delivers parameters of both long and short DRX cycles to the UE, but
the UE uses only a long or short DRX cycle at a time. The UE can switch between
the long and short DRX cycles according to certain rules. The duration of the long
DRX cycle is specified by the gNBDrxParamGroup.LongCycle parameter, and the
duration of the short DRX cycle is specified by the
gNBDrxParamGroup.ShortCycle parameter.
● Switching from a long DRX cycle to a short DRX cycle
By default, a UE uses a long DRX cycle. If the base station has configured a
short DRX cycle for the UE, the UE switches from the long DRX cycle to the
short DRX cycle when the DRX Inactivity Timer expires. In this way, service
delay is shortened.
● Switching from a short DRX cycle to a long DRX cycle
When the Short Cycle Timer expires, the UE exits the short DRX cycle and
enters a long DRX cycle, reducing UE power consumption.
NOTE
The Short Cycle Timer specifies the number of consecutive repetitions of a short DRX
cycle. When the UE enters a short DRX cycle, the Short Cycle Timer immediately starts.
When the Short Cycle Timer expires, the UE exits the short DRX cycle and enters a
long DRX cycle.
4.2 Network Analysis
4.2.1 Benefits
DRX offers the following advantages over continuous reception:
● A UE does not need to constantly monitor the PDCCH. Instead, the UE turns
on its receiver only when necessary. This reduces UE power consumption and
ensures a longer standby time.
● Cell global identifier (CGI) measurement for ANR is allowed for the UE in the
DRX sleep time.
After DRX is enabled, the power saving effect of UEs can be monitored by using
N.Cdrx.Sleep.Dur.Total (total duration for RRC_CONNECTED DRX UEs in the sleep
time) and N.Cdrx.Active.Dur.Total (total duration for RRC_CONNECTED DRX UEs
in the active time).
NOTE
When a UE is in DRX mode, its power consumption can be reduced. The power saving effect
is related to UE chips. Therefore, using the same DRX parameters may not bring the same
power saving effect for different UEs.

(2021-12-30)
5G RAN
4.2.2 Impacts
Network Impacts
DRX sleep times reduce UE power consumption at the expense of prolonged
service delay, which may cause throughput decrease.
DRX has the following impacts on the network:
● The measurement and reporting periods of the channel state information
(CSI) and the synchronization signal and PBCH block (SSB) increase and the
rank adjustment slows, which affects the delay and throughput. In addition,
the handover success rate and SCG addition success rate decrease, and the
service drop rate and HARQ retransmission rate increase. If
gNBDrxParamGroup.LongCycle is set to an excessively large value, or UEs
are moving at high speeds or under weak coverage, the preceding impacts
will be more evident. Longer SSB measurement and reporting periods may
result in fewer RRM measurements.
● The CQI measurement and reporting periods are prolonged. Therefore, the
measured CQI value may increase or decrease depending on the channel
environment.
● If the sleep time is too short, cell global identifier (CGI) measurements for
ANR will fail.
● The number of times UEs are scheduled may decrease.
● The number of UEs with data in the buffer may increase, and the number of
activated UEs increases.
● The consumption of PDCCH CCEs, PDSCH PRBs, and PUSCH PRBs increases.
There is a false detection probability when the gNodeB detects whether a UE
sends SRs. Specifically, although a UE does not send an SR, the gNodeB
detects the SR. When such false detection occurs in the DRX sleep time, the
gNodeB mistakenly considers that the UE is in the DRX active time and
performs scheduling on the UE. However, the UE is actually in the sleep time
and does not respond to the scheduling. This increases the BLER and
retransmissions from the gNodeB, raising up the consumption of CCEs and
PRBs.
● After DRX state evaluation based on scheduling feedback is enabled, the
number of scheduled UEs and the cell throughput increase in heavily loaded
cells. However, false SR detection may be incorrectly identified, causing the UE
throughput to decrease.
In heavy-traffic scenarios, the preceding impact of DRX increases.
In light-load scenarios with small packets transmitted in the uplink, the basic K2
values of UEs decrease. This shortens the uplink retransmission delay and enables
UEs to enter the DRX sleep time more quickly. The value of
N.Cdrx.Sleep.Dur.Total (total duration for RRC_CONNECTED DRX UEs in sleep
time) increases and that of N.Cdrx.Active.Dur.Total (total duration for
RRC_CONNECTED DRX UEs in active time) decreases. An increase in the value of
N.Cdrx.Sleep.Dur.Total may increase the probability of false SR detection in DRX
sleep times, thereby increasing the uplink RBLER. Uplink RBLER =
(N.UL.SCH.HalfPiBPSK.ErrTB.Rbler + N.UL.SCH.QPSK.ErrTB.Rbler + N.UL.SCH.
16QAM.ErrTB.Rbler + N.UL.SCH.64QAM.ErrTB.Rbler + N.UL.SCH.

(2021-12-30)
5G RAN
256QAM.ErrTB.Rbler)/(N.UL.SCH.HalfPiBPSK.TB + N.UL.SCH.QPSK.TB +
N.UL.SCH.16QAM.TB + N.UL.SCH.64QAM.TB + N.UL.SCH.256QAM.TB) x 100%
If the gNodeB configures SRs and CSI to be reported in the same timeslot and
some UEs simultaneously report SRs and CSI in DRX sleep times, the gNodeB
cannot correctly detect the SRs reported by these UEs. As a result, uplink data
cannot be scheduled in a timely manner, increasing the uplink data transmission
delay. To solve this problem, the following functions are introduced:
● Simultaneous reporting of SRs and CSI in DRX sleep times, which is controlled
by the DRX_SR_CSI_REPORT_SW option of the
NRDUCellUePwrSaving.NrDuCellDrxAlgoSwitch parameter. After this
function is enabled, the gNodeB will correctly detect SRs reported by a UE
when the UE simultaneously reports SRs and CSI in the DRX sleep time. For
UEs that support simultaneous reporting of SRs and CSI in DRX sleep times,
the uplink data transmission delay decreases. For UEs that do not support
simultaneous reporting of SRs and CSI in DRX sleep times, the uplink data
transmission delay increases.
● Non-overlapping between CSI and SR reporting slots, which is controlled by
the DRX_CSI_SLOT_SHIFT_FOR_SR_SW option of the
NRDUCellUePwrSaving.NrDuCellDrxAlgoSwitch parameter. After this
function is enabled, the gNodeB will not configure a UE's CSI reporting slot in
which the UE reports an SR. This prevents the increase of uplink data
transmission delay caused by overlapping CSI and SR reporting slots.
When configuring or reconfiguring DRX parameters (DRX-Config) for a UE using
RRC signaling messages, the gNodeB cannot accurately determine the time when
the DRX parameters take effect for the UE. There is a possibility that the DRX
parameters have taken effect on the gNodeB side but still not on the UE side. In
this scenario, the gNodeB incorrectly considers that the UE is in the DRX sleep
time and stops scheduling for the UE. As a result, the UE access delay increases
and the user-perceived throughput decreases. To address this issue, DRX
configuration procedure optimization is introduced. This function is controlled by
the DRX_CONFIG_OPT_SW option of the
NRDUCellUePwrSaving.NrDuCellDrxAlgoSwitch parameter. After the DRX
configuration procedure optimization function is enabled, the gNodeB optimizes
the DRX parameter configuration and reconfiguration procedures. Specifically, new
DRX configurations take effect on the gNodeB side only after the gNodeB receives
a configuration response message from the UE, and the gNodeB does not stop
scheduling the UE during the DRX configuration procedure, thereby increasing the
user-perceived throughput.

(2021-12-30)
5G RAN
Function Impacts
RAT Function Function Reference Description
Name Switch
FDD Intra-RAT NR_NR_ANR ANR ● The UE can

Low- ANR _SW option perform
frequency of the reportCGI
TDD NRCellAlgoS measurements
witch.AnrSw only after
itch entering the DRX
parameter sleep time.
● When the
gNodeB triggers a
UE to read the
NCGIs, the UE
automatically
uses a long DRX
cycle.
The setting of the
BASIC_DRX_SW
option of the
NRDUCellUePwr
Saving.NrDuCell
DrxAlgoSwitch
parameter does
not affect the
configuration of
the long DRX
cycle initiated by
intra-RAT ANR.

(2021-12-30)
5G RAN

Name Switch
FDD Inter-RAT NR_EUTRAN ANR ● The UE can

Low- ANR _ANR_SW perform
frequency option of the reportCGI
TDD NRCellAlgoS measurements
witch.AnrSw only after
itch entering the DRX
parameter sleep time.
● When the
gNodeB triggers a
UE to read the
ECGIs, the UE
automatically
uses a long DRX
cycle.
The setting of the
BASIC_DRX_SW
option of the
NRDUCellUePwr
Saving.NrDuCell
DrxAlgoSwitch
parameter does
not affect the
configuration of
the long DRX
cycle initiated by
inter-RAT ANR.

(2021-12-30)
5G RAN

Name Switch
FDD SRS resource None Channel ● Periodic SRS: The

Low- management Management gNodeB does not
frequency receive or
TDD measure SRS
from UEs in DRX
sleep time.
Therefore, the
quantity of valid
SRSs received by
the gNodeB
decreases.
● Aperiodic SRS:
The gNodeB does
not schedule SRSs
from UEs in DRX
sleep time.
Therefore, the
quantity of valid
SRSs received by
the gNodeB
decreases.
For details about
periodic and
aperiodic SRSs, see
Channel
Management.

(2021-12-30)
5G RAN

Name Switch
FDD CSI-RS None Channel ● Periodic CSI-RS

Low- resource Management for CM: The
frequency management gNodeB does not
TDD check CSI-RS
measurement
reports from UEs
in DRX sleep
times. As a result,
the number of
valid CSI-RS
measurement
reports received
by the gNodeB
decreases.
● Aperiodic CSI-RS
for CM: UEs send
CSI-RS
measurement
reports on the
PUSCH, which
may cause
continuous
scheduling of
uplink data for
UEs. As a result,
the UEs cannot
enter DRX sleep
times.
For details about
periodic and
aperiodic CSI-RS for
CM, see Channel
Management.

(2021-12-30)
5G RAN

Name Switch
FDD Uplink NRDUCellPu Scheduling ● After the uplink

Low- Preallocation sch.UlPreall basic
frequency ocationSwit preallocation
TDD ch function
(controlled by the
UL_BASIC_PREAL
LOCATION_SWIT
CH option of the
NRDUCellPusch.
UlPreallocationS
witch parameter)
is enabled, UEs
cannot enter the
sleep time.
● After uplink smart
preallocation
function
(corresponding to
the
UL_SMART_PREA
LLOCATION_SWI
TCH option of the
NRDUCellPusch.
UlPreallocationS
witch parameter)
is enabled, UEs
cannot enter the
sleep time within
the duration for
uplink smart
preallocation.
● After uplink
preallocation for
sparse-packet
services is
enabled (by
selecting the
SPARSE_DIFF_PR
OC_SW option of
the
gNodeBParam.Se
rviceDiffProcSwit
ch parameter and
the
SPARSE_DIFF_SC
H_SW option of
the
NRDUCellAlgoS

(2021-12-30)
5G RAN

Name Switch
witch.ServiceDiff
Switch
parameter), UEs
performing
sparse-packet
services cannot
enter the sleep
time.
FDD Basic VoNR VONR_SW VoNR When the gNodeB

Low- Functions option of the RLC parameter
frequency NRCellAlgoS group is associated
TDD witch.VonrS with 5QI 1 bearers:
witch ● If
parameter NRDUCellQciBea
rer.DuDrxParam
GroupId or
NRCellQciBearer.
DrxParamGroupI
d is set to the
default value 255,
DRX does not
take effect and
VoNR services are
not affected.
● If neither
NRDUCellQciBea
rer.DuDrxParam
GroupId nor
NRCellQciBearer.
DrxParamGroupI
d is set to the
default value,
DRX is not
affected.
However, the
transmission
delay of voice
packets increases,
affecting the
voice quality of
downlink VoNR
services.

(2021-12-30)
5G RAN

Name Switch
FDD Intra-base- INTRA_GNB_ CoMP ● After the DRX

Low- station DL DL_JT_SW function is
frequency CoMP option of the enabled, UEs are
TDD NRDUCellAl less likely to be
goSwitch.Co identified as
mpSwitch intra-base-station
parameter joint transmission
UEs.
● After DRX is
enabled: if the
function of DRX
exit of UEs
performing full-
buffer services
(controlled by the
FULL_BUFFER_UE
_EXIT_DRX_SW
option of the
NRDUCellUePwr
Saving.NrDuCell
DrxAlgoSwitch
parameter) is
enabled, DRX
does not take
effect for a UE
identified as an
intra-base-station
joint transmission
UE; if the function
of DRX exit of
UEs performing
full-buffer
services is
disabled, the UE
identified as an
intra-base-station
joint transmission
UE cannot enter
the DRX sleep
time because the
aperiodic CSI-RS
for CM is used.

(2021-12-30)
5G RAN

Name Switch
Low- Power saving BWP2_SWIT UE Power ● All UEs working

frequency BWP (low- CH option of Saving in BWP2
TDD frequency the aperiodically
TDD) NRDUCellUe report CSI-RS for
PwrSaving.B CM measurement
wpPwrSavin results if both
gSw power saving
parameter BWP and DRX are
enabled,
NRDUCellPucch.
CsiDedicatedRbN
um is set to RB2,
and the
PUCCH_RBRES_A
DAPTIVE_SWITC
H option of the
NRDUCellPucch.
PucchAlgoSwitch
parameter is
deselected.
Because such UEs
aperiodically
report CSI-RS for
CM measurement
results on the
PUSCH, uplink
data of these UEs
may be scheduled
continuously. As a
result, these UEs
cannot enter the
DRX sleep time.
● If both power
saving BWP and
DRX are enabled
and the
gNBDUDrxParam
Group.DrxInactiv
ityTimer
parameter is set
to a value less
than 20 ms, UEs
may stay in BWP2
and cannot switch
to BWP1.
● If both power
saving BWP and
DRX are enabled

(2021-12-30)
5G RAN

Name Switch
and the
BWP2_APER_CSI_
UE_DRX_ENH_S
W option of the
NRDUCellUePwr
Saving.NrDuCell
DrxAlgoSwitch
parameter is
selected, UEs in
BWP2 do not
aperiodically
report CSI-RS for
CM measurement
results even
though
configured to do
so when there is
no uplink data
transmission in
non-On Duration
periods. This way,
these UEs can
enter the DRX
sleep time, the
number of CSI-RS
for CM
measurement
reports decreases,
and the network
performance is
affected. For
details about the
impact analysis,
see Network
Impacts.
● If both power
saving BWP and
DRX are enabled
and the gNodeB
triggers a
switchover from
BWP2 to BWP1
during the DRX
sleep time, the
DCI for switching
from BWP2 to
BWP1 may fail to
be delivered. As a
result, the

(2021-12-30)
5G RAN

Name Switch
gNodeB stops
scheduling
downlink data
transmission for
the UE during the
BWP switchover,
leading to
downlink
scheduling
failures. To
address this issue,
the
DRX_BWP2_OPT_
SW option of the
NRDUCellUePwr
Saving.BwpPwrS
avingSw
parameter can be
selected so that
the gNodeB
triggers UE
switching from
BWP2 to BWP1
only when the
DRX inactivity
timer is running.
● Periodic PUCCH
CSI reporting
resources can be
allocated to UEs
working in BWP2
by setting
NRDUCellRsvdEx
t02.RsvdParam0
to 1 if the
following
conditions are
met: Both power
saving BWP and
DRX are enabled;
the SSB beam
enhancement
function
(controlled by the
SSB_BEAM_ENH_
SW option of the
NRDUCellAlgoS
witch.FullChanne
lCovEnhSwitch

(2021-12-30)
5G RAN

Name Switch
parameter) is not
in effect; PUCCH
RB adaptation is
enabled (by
selecting the
PUCCH_RBRES_A
DAPTIVE_SWITC
H option of the
NRDUCellPucch.
PucchAlgoSwitch
parameter). This
helps increase the
proportion of DRX
sleep times and
bring more power
saving gains for
UEs, but causes
decreased
average uplink
and downlink UE
throughput,
prolonged delay,
and value
increase or
decrease of the
CQI measurement
items.
FDD Intra-band INTRA_BAN Carrier Data split for a UE is

Low- CA D_CA_SW Aggregation affected if the UE's
frequency option of the DRX state is
TDD NRDUCellAl inconsistent between
goSwitch.Ca its PCell and SCells.
AlgoSwitch When intra-band CA
parameter and DRX are both
INTRA_BAN enabled, it is
D_UL_CA_S recommended that
W option of collaboration
the between CA and
NRDUCellAl DRX (controlled by
goSwitch.Ca the
AlgoSwitch CA_AND_DRX_STAT
parameter US_COLLAB_SW
option of the
NRDUCellCarrMgm
t.CaEnhancedAlgoE
xtSwitch parameter)
be enabled.

(2021-12-30)
5G RAN

Name Switch
FDD Intra-FR INTRA_FR_I Carrier Data split for a UE is

Low- inter-band NTER_BAND Aggregation affected if the UE is
frequency CA _CA_SW in different DRX
TDD option of the states in its PCell
NRDUCellAl and SCells. When
goSwitch.Ca intra-FR inter-band
AlgoSwitch CA and DRX are both
parameter enabled, it is
INTRA_FR_I recommended that
NTER_BAND collaboration
_UL_CA_SW between CA and
option of the DRX be enabled. The
NRDUCellAl collaboration is
goSwitch.Ca controlled by the
AlgoSwitch CA_AND_DRX_STAT
parameter US_COLLAB_SW
option of the
NRDUCellCarrMgm
t.CaEnhancedAlgoE
xtSwitch parameter.
FDD Downlink INTER_BBU_ Carrier When downlink
Low- inter-gNodeB CA_SW Aggregation inter-gNodeB CA is
frequency CA option of the enabled, the length
TDD NRDUCellAl of the DRX inactivity
goSwitch.Ca timer must be
AlgoSwitch greater than 4 ms.
parameter That is, the
gNBDUDrxParamGr
oup.DrxInactivityTi
mer parameter must
be set to a value
greater than MS4.

(2021-12-30)
5G RAN

Name Switch
FDD Uplink data LTE: NSA After DRX is enabled,

Low- transmission NSA_DC_UL_ Networking if DRX exit of UEs
frequency path PATH_SELEC based on performing full-
TDD selection TION_SW EPC buffer services is
option of the enabled (by
NsaDcMgmt selecting the
Config.NsaD FULL_BUFFER_UE_E
cAlgoSwitch XIT_DRX_SW option
parameter of the
NR: NRDUCellUePwrSav
NSA_DC_UL_ ing.NrDuCellDrxAlg
PATH_SELEC oSwitch parameter)
TION_SW and the uplink data
option of the transmission path
NRCellNsaD selection function
cConfig.Nsa takes effect for a UE,
DcAlgoSwitc the UE is a full
h parameter buffer UE. In this
case, DRX does not
take effect.
Low- Low latency HIGH_RELIA URLLC It is not

frequency and high BILITY_BASI recommended that
TDD reliability C_SW option DRX be enabled for
(low- of the bearers carrying low-
frequency NRDUCellAl latency and high-
TDD) goSwitch.Hi reliability services.
ghReliability
Switch
parameter
FDD QCI-specific DL_IBLER_Q URLLC It is not

Low- scheduling CI_SW of the recommended that
frequency based on the gNBDUSchP DRX be enabled for
TDD downlink aramGroup. bearers carrying
target IBLER ScheduleOp differentiated low-
tSwitch latency services.
parameter
FDD Low latency HIGH_RELIA URLLC It is not

Low- and high BILITY_BASI recommended that
frequency reliability C_SW option DRX be enabled for
TDD of the bearers of low-
NRDUCellAl latency and high-
goSwitch.Hi reliability services.
ghReliability
Switch
parameter

(2021-12-30)
5G RAN

Name Switch
FDD High-speed NRDUCell.Hi High Speed To enable DRX in

Low- Railway ghSpeedFla Mobility high-speed cells, the
frequency Superior g differentiated DRX
TDD Experience function must be
enabled (by
selecting the
LOW_SPEED_UE_DR
X_SW option of the
NRCellAlgoSwitch.
HighSpeedDedPoli-
cySw parameter). In
high-speed cells,
DRX takes effect
only for low-speed
UEs.
Low- Exit from BWP2_SWIT UE Power When exit from DRX

frequency DRX and CH option of Saving and BWP2 of weak-
TDD BWP2 of the coverage UEs is
Weak- NRDUCellUe enabled, the gNodeB
Coverage PwrSaving.B does not configure
UEs wpPwrSavin DRX parameters for
gSw weak-coverage UEs
parameter or force them to exit
the DRX mode.
4.3 Requirements
4.3.1 Licenses
None
4.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
Prerequisite Functions
None
Mutually Exclusive Functions

None

(2021-12-30)
5G RAN
4.3.3 Hardware
Base Station Models
3900 and 5900 series base stations. 3900 series base stations must be configured
with the BBU3910.
DBS3900 LampSite and DBS5900 LampSite. DBS3900 LampSite must be
configured with the BBU3910.
Boards
All NR-capable main control boards and baseband processing units support this
function. For details, see the BBU technical specifications in 3900 & 5900 Series
Base Station Product Documentation.
RF Modules
All NR-capable RF modules that work in low frequency bands support this
function. For details, see the technical specifications of RF modules in 3900 & 5900
Series Base Station Product Documentation.
4.3.4 Others
To support DRX basic functions, UEs must support the "longDRX-Cycle" field in the
MAC-ParametersXDD-Diff message. To support the short DRX cycle function, UEs
must also support the "shortDRX-Cycle" field. For details about the fields, see
section 6.3.3 UE capability information elements in 3GPP TS 38.331 V16.4.1.
4.4 Operation and Maintenance
4.4.1 Data Configuration
4.4.1.1 Data Preparation

Table 4-9 and Table 4-10 describe the parameters used for function activation
and optimization.
QCI-specific DRX parameter settings require that bearers with specified QCIs have
been set up for UEs. Therefore, before using this function, ensure that bears of
relevant QCIs have been set up. For details, see QoS Management.

(2021-12-30)
5G RAN
Table 4-9 Parameters used for activation

Parameter Parameter ID Option Setting Notes
Name
NR DU Cell NRDUCellUe BASIC_DRX_S Set this parameter based on

DRX PwrSaving.Nr W the network plan.
Algorithm DuCellDrxAlg
Switch oSwitch
DRX NRCellQciBe None For standardized QCIs, this
Parameter arer.DrxPara parameter is set by default
Group ID mGroupId and does not need to be
manually configured. For
extended QCIs, this parameter
needs to be configured based
on the network plan. Before
enabling DRX, ensure that all
QCIs used by UEs are bound
to valid DRX parameter
groups. The QCIs added to the
NRCellQciBearer MO must
exist in the gNBQciBearer
MO.
DU DRX NRDUCellQci None This parameter is set for

Parameter Bearer.DuDrx standardized QCIs by default
Group ID ParamGroupI and does not need to be
d manually configured. For
extended QCIs, this parameter
needs to be configured based
on the network plan. Before
enabling DRX, ensure that all
QCIs used by UEs are bound
to valid DRX parameter
groups. The QCIs added to the
NRDUCellQciBearer MO must
exist in the gNBQciBearer
MO.
Table 4-10 Parameters used for optimization

Parameter Name Parameter ID Option Setting Notes
DRX Parameter gNBDrxParamGr None Set this parameter

Group ID oup.DrxParamGr based on the
oupId network plan.

(2021-12-30)
5G RAN
Long Cycle gNBDrxParamGr None A larger

oup.LongCycle parameter value
results in a longer
sleep time and
longer delay. A
smaller value
results in shorter
delay. Set this
parameter based
on the network
plan.
Short Cycle gNBDrxParamGr None A larger

oup.ShortCycle parameter value
results in a longer
sleep time and
longer delay. Set
this parameter
based on the
network plan.
Short Cycle Timer gNBDrxParamGr None A larger

oup.ShortCycleTi parameter value
mer results in a longer
short DRX cycle
and shorter delay.
Set this parameter
based on the
network plan.
DU DRX gNBDUDrxParam None Set this parameter

Parameter Group Group.DuDrxPara based on the
ID mGroupId network plan.
On Duration gNBDUDrxParam None A larger

Timer Group.OnDuratio parameter value
nTimer results in a longer
active time and
shorter delay. Set
this parameter
based on the
network plan.

(2021-12-30)
5G RAN
DRX Inactivity gNBDUDrxParam None A larger

Timer Group.DrxInactivi parameter value
tyTimer results in a longer
active time
extension after a
UE receives new
data during the
On Duration
Timer. The length
of this timer must
be longer than or
equal to the time
difference
between SR
sending and
scheduling.
Otherwise, user
experience is
affected and
service drops may
occur. Therefore, it
is recommended
that this timer be
set to 20 ms or
longer.
DRX gNBDUDrxParam None This parameter

Retransmission Group.DrxRetran specifies the
Timer sTimer length of the DL
Retransmission
Timer and UL
Retransmission
Timer. Set this
parameter based
on the network
plan.
NR DU Cell DRX NRDUCellUePwr BWP2_APER_CSI_ Select this option

Algorithm Switch Saving.NrDuCell UE_DRX_ENH_SW based on the
DrxAlgoSwitch network plan.
NR DU Cell DRX NRDUCellUePwr FULL_BUFFER_UE Select this option.

Algorithm Switch Saving.NrDuCell _EXIT_DRX_SW
DrxAlgoSwitch
NR DU Cell DRX NRDUCellUePwr UL_BASED_DRX_S Select this option.
Algorithm Switch Saving.NrDuCell TATUS_DETECT_S
DrxAlgoSwitch W

(2021-12-30)
5G RAN
DRX Sleep State NRDUCellUePwr None Set this parameter

Detect Threshold Saving.DrxSleepS based on the
tateDetectThld network plan.
A smaller value of
this parameter
results in more
timely
identification of
false SR
detections,
increasing the
number of
scheduled UEs
and cell
throughput in
heavy-load cells.
However, false SR
detections may be
incorrectly
identified,
decreasing the UE
throughput. A
larger value of
this parameter
results in a longer
time for
identifying false
SR detections.
This decreases the
number of
scheduled UEs
and cell
throughput on a
heavily loaded
network and
increases the UE
throughput on a
lightly loaded
network.
NR DU Cell DRX NRDUCellUePwr DRX_SR_CSI_REPO Select this option

Algorithm Switch Saving.NrDuCell RT_SW based on the
NR DU Cell DRX NRDUCellUePwr DRX_CONFIG_OP Select this option.

Algorithm Switch Saving.NrDuCell T_SW
DrxAlgoSwitch
BWP Power NRDUCellUePwr DRX_BWP2_OPT_ Select this option.
Saving Switch Saving.BwpPwrS SW
avingSw

(2021-12-30)
5G RAN
NR DU Cell DRX NRDUCellUePwr DRX_CSI_SLOT_SH Select this option

Algorithm Switch Saving.NrDuCell IFT_FOR_SR_SW based on the
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 and the actual
network scenario.
Activation Command Examples

//Enabling the DRX function for a cell
MOD NRDUCELLUEPWRSAVING: NrDuCellId=0, NrDuCellDrxAlgoSwitch=BASIC_DRX_SW-1;
//Adding or binding DRX parameter groups is not required for QCI 1, QCI 65, QCI 66, and QCI 69 because
DRX is not recommended for them. The system adds and binds DRX parameter groups by default for QCI 2,
QCI 3, QCI 5, QCI 7, QCI 75, QCI 79, QCI 4, QCI 6, QCI 8, QCI 9, and QCI 70. You must add and bind the
DRX parameter groups for QCIs other than the preceding ones.
//Adding a DRX parameter group for only a long DRX cycle
ADD GNBDRXPARAMGROUP: DrxParamGroupId=2, LongCycle=MS320;
ADD GNBDUDRXPARAMGROUP: DuDrxParamGroupId=2, OnDurationTimer=MS10,
DrxInactivityTimer=MS100, DrxRetransTimer=SL16;
//Adding DRX parameter groups for long and short DRX cycles
ADD GNBDRXPARAMGROUP: DrxParamGroupId=2, LongCycle=MS320, ShortCycle=MS80,
ShortCycleTimer=1;
ADD GNBDUDRXPARAMGROUP: DuDrxParamGroupId=2, OnDurationTimer=MS10,
//Binding the DRX parameter group to the QCI
MOD NRCELLQCIBEARER: NrCellId=0, Qci=100, DrxParamGroupId=2;
MOD NRDUCELLQCIBEARER: NrDuCellId=0, Qci=100, DuDrxParamGroupId=2;
Optimization Command Examples

//Modifying the DRX parameter settings for a long DRX cycle
MOD GNBDRXPARAMGROUP: DrxParamGroupId=2, LongCycle=MS40;
MOD GNBDUDRXPARAMGROUP: DuDrxParamGroupId=2, OnDurationTimer=MS10,
//Modifying the DRX parameter settings for long and short DRX cycles
MOD GNBDRXPARAMGROUP: DrxParamGroupId=2, LongCycle=MS40, ShortCycle=MS20, ShortCycleTimer=1;
MOD GNBDUDRXPARAMGROUP: DuDrxParamGroupId=2, OnDurationTimer=MS10,
//Modifying the binding relationship between a DRX parameter group and a QCI
//Enabling coordination between the DRX feature and UEs adopting aperiodic CSI-RS for CM reporting on
BWP2
MOD NRDUCELLUEPWRSAVING: NrDuCellId=0,
NrDuCellDrxAlgoSwitch=BWP2_APER_CSI_UE_DRX_ENH_SW-1;
//Enabling DRX exit of UEs performing full-buffer services
MOD NRDUCELLUEPWRSAVING: NrDuCellId=0, NrDuCellDrxAlgoSwitch=FULL_BUFFER_UE_EXIT_DRX_SW-1;
//Enabling DRX state evaluation based on scheduling feedback over the PUSCH
NrDuCellDrxAlgoSwitch=UL_BASED_DRX_STATUS_DETECT_SW-1;
//Configuring the DRX sleep time detection threshold
MOD NRDUCELLUEPWRSAVING: NrDuCellId=0, DrxSleepStateDetectThld=2;
//Enabling simultaneous reporting of SRs and CSI in DRX sleep times
MOD NRDUCELLUEPWRSAVING: NrDuCellId=0, NrDuCellDrxAlgoSwitch=DRX_SR_CSI_REPORT_SW-1;
//Enabling DRX configuration procedure optimization
MOD NRDUCELLUEPWRSAVING: NrDuCellId=0, NrDuCellDrxAlgoSwitch=DRX_CONFIG_OPT_SW-1;

(2021-12-30)
5G RAN
//Enabling optimized collaboration between DRX and BWP2

MOD NRDUCELLUEPWRSAVING: NrDuCellId=0, BwpPwrSavingSw=DRX_BWP2_OPT_SW-1;
//Enabling non-overlapping between CSI and SR reporting slots
NrDuCellDrxAlgoSwitch=DRX_CSI_SLOT_SHIFT_FOR_SR_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 for a specific QCI
//Disabling the DRX function for a cell
MOD NRDUCELLUEPWRSAVING: NrDuCellId=0, NrDuCellDrxAlgoSwitch=BASIC_DRX_SW-0;
4.4.1.3 Using the MAE-Deployment

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

Prerequisites: The UE supports DRX.
The activation verification procedure is as follows:
1. Run the MOD NRDUCELLUEPWRSAVING command with the
BASIC_DRX_SW option of the
NRDUCellUePwrSaving.NrDuCellDrxAlgoSwitch parameter selected to
activate DRX.
2. Enable a UE to access the network. Check the RRCConnectionReconfiguration
message (in NSA networking) or the RRCReconfiguration message (in SA
networking) over the Uu interface. If the message contains DRX parameters,
DRX has taken effect.
NOTE
To ensure that a UE has the opportunity to send periodic SRS and periodic CSI feedback
within the On Duration Timer length, the gNodeB may extend the length. As a result, the
On Duration Timer length in effect may be inconsistent with the value of the
gNBDUDrxParamGroup.OnDurationTimer parameter configured for the gNodeB. If the
extended On Duration Timer length exceeds the long DRX cycle, the gNodeB does not
deliver the DRX configuration to the UE. That is, the DRX-Config field is not filled in the
RRCConnectionReconfiguration message (in NSA networking) or the RRCReconfiguration
message (in SA networking) delivered by the gNodeB to the UE.
4.4.3 Network Monitoring

After DRX is enabled, monitor the following counters to evaluate the impact of
DRX on delay and downlink throughput. For details about the impact, see 4.2.2
Impacts.
● Compare the results of (N.QoS.DL.PktDelaygNBDU.Time/
N.QoS.DL.PktDelaygNBDU.Num) + (N.QoS.DL.PktDelayAirInterface.Time/
N.QoS.DL.PktDelayAirInterface.Num) before and after DRX activation and
evaluate the impact of DRX on service delay.

(2021-12-30)
5G RAN
● Check the result of N.ThpVol.DL.Cell/N.ThpTime.DL.Cell to evaluate the

impact of DRX on throughput.
● Check the result of N.Cdrx.Sleep.Dur.Total (total duration of UEs in the sleep
time in a cell) and N.Cdrx.Active.Dur.Total (total duration of UEs in the
active time in a cell) to evaluate the power saving effect of UEs.
Table 4-11 describes the mapping between the IDs and names of the preceding
counters.
Table 4-11 Mapping between counter IDs and counter names

Counter ID Counter Name
1911816924 N.QoS.DL.PktDelaygNBDU.Time
1911816925 N.QoS.DL.PktDelayAirInterface.Num
1911816926 N.QoS.DL.PktDelayAirInterface.Time
1911816927 N.QoS.DL.PktDelaygNBDU.Num
1911816694 N.ThpVol.DL.Cell
1911816695 N.ThpTime.DL.Cell
1911820769 N.Cdrx.Sleep.Dur.Total
1911820770 N.Cdrx.Active.Dur.Total

(2021-12-30)
5G RAN
DRX Feature Parameter Description 5 Parameters
5 Parameters
The following hyperlinked EXCEL files of parameter reference match the software
version with which this document is released.
● Node Parameter Reference: contains device and transport parameters.
● gNodeBFunction Parameter Reference: contains all parameters 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 parameter reference for the software version used on the
live network from the product documentation delivered with that version.
FAQ: 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, FBFD-010011.
Step 3 Click OK. All parameters related to the feature are displayed.
----End

(2021-12-30)
5G RAN
DRX Feature Parameter Description 6 Counters
6 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.
● gNodeBFunction 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, FBFD-010011.
Step 3 Click OK. All counters related to the feature are displayed.
----End

(2021-12-30)
5G RAN
DRX Feature Parameter Description 7 Glossary
7 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

(2021-12-30)
5G RAN
DRX Feature Parameter Description 8 Reference Documents
8 Reference Documents
● 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception"
● 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification"
● 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification"
● ANR
● Channel Management
● Scheduling
● QoS Management
● Flexible User Steering
● NSA Networking based on EPC
● UE Power Saving
● VoNR
● High Speed Mobility
● CoMP
● Carrier Aggregation
● URLLC
● Technical Specifications in 3900 & 5900 Series Base Station Product
Documentation

(2021-12-30)

DRX (5g Ran6.1 - Draft A)

Uploaded by

Copyright:

Available Formats

DRX (5g Ran6.1 - Draft A)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DRX (5g Ran6.1 - Draft A)

Uploaded by

Copyright:

Available Formats

5G RAN

DRX Feature Parameter Description

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. i

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

Issue Draft A Copyright © Huawei Technologies Co., Ltd. ii

4.4.3 Network Monitoring......................................................................................................................................................... 42

Issue Draft A Copyright © Huawei Technologies Co., Ltd. iii

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

1.1 5G RAN6.1 Draft A (2021-12-30)

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 1

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 2

2 About This Document

2.1 General Statements

2.2 Features in This Document

Feature ID Feature Name Chapter/Section

FBFD-021103 DRX 4 DRX

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 3

2.3 Differences Between NR FDD and NR TDD

DRX None 4 DRX

2.4 Differences Between NSA and SA

DRX Supported in both NSA 4 DRX

2.5 Differences Between High Frequency Bands and

Function Difference Chapter/Section

DRX Supported only in low 4 DRX

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 4

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 5

4.1.1 Basic Concepts

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 6

Figure 4-1 DRX cycle

An On Duration period is within the active time.

According to section 5.7 "Discontinuous Reception (DRX)" in 3GPP TS 38.321

● The On Duration Timer, DRX Inactivity Timer, DL Retransmission Timer, UL

Long DRX Cycle

Short DRX Cycle

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 7

Table 4-1 On Duration Timer

Function This timer starts at the beginning of a DRX cycle. The UE

Timing Timing is based on milliseconds.

Stop This timer stops upon expiry.

Expiry Upon expiry, this timer stops timing.

Table 4-2 DRX Inactivity Timer

Function This timer is used for a UE to determine whether to extend the

Start This timer starts or restarts when the UE successfully decodes a

Timing Timing is based on milliseconds.

Stop This timer stops upon expiry.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 8

Table 4-3 Short Cycle Timer

Timing Timing is based on the number of repetitions of a short DRX

Stop This timer stops upon expiry.

Table 4-4 DL Retransmission Timer

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 9

Start This timer starts or restarts when the DL HARQ-RTT Timer

Timing Timing is based on the number of slots.

Stop ● This timer stops when the DL HARQ-RTT Timer starts.

Expiry Upon expiry, this timer stops timing.

Table 4-5 UL Retransmission Timer