DRX Feature Parameter Description (ERAN2.0 - 01)

eRAN
DRX
Feature Parameter Description
Issue
01
Date
2010-07-30
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd
Copyright Huawei Technologies Co., Ltd. 2010. 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 the property 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 the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com

eRAN
DRX
Contents
Contents
1 Introduction.................................................................................................................................1-1
1.1 Scope.............................................................................................................................................................1-1
1.2 Intended Audience.........................................................................................................................................1-1
1.3 Change History..............................................................................................................................................1-1
2 Overview of DRX .......................................................................................................................2-1

2.1 Definition ......................................................................................................................................................2-1
2.2 Advantage......................................................................................................................................................2-1
2.3 Dependencies on Other Features...................................................................................................................2-2
2.4 Typical Application .......................................................................................................................................2-2
3 DRX Technology ........................................................................................................................3-1

3.1 Principle ........................................................................................................................................................3-1
3.2 Key Technologies..........................................................................................................................................3-2
3.2.1 Entering/Quitting the DRX Mode........................................................................................................3-2
3.2.2 Starting the DRX Cycle .......................................................................................................................3-4
3.2.3 Switchover Between the Active Time and the Sleep Time ..................................................................3-5
3.2.4 Switchover Between Long DRX Cycle and Short DRX Cycle .........................................................3-10
3.2.5 RFSP ..................................................................................................................................................3-11
3.3 Feature Interactions.....................................................................................................................................3-11
3.3.1 Dependency on Scheduling................................................................................................................3-11
3.3.2 Dependency on HARQ ......................................................................................................................3-12
3.3.3 Dependency on Random Access ........................................................................................................3-12
3.3.4 Dependency on Measurement ............................................................................................................3-12
3.3.5 Dependency on CQI/SRS Measurement and Report .........................................................................3-13
3.3.6 Dependency on UL Synchronization .................................................................................................3-13
3.3.7 Dependency on Handover ..................................................................................................................3-13
4 Engineering Guidelines............................................................................................................4-1
4.1 Setting the DRX Switch ................................................................................................................................4-1
4.2 Setting the Cell Duplex Mode and TDD Uplink-Downlink Subframe Configuration ..................................4-1
4.3 Setting the DRX Cycle Duration...................................................................................................................4-2
4.4 Setting the Timers .........................................................................................................................................4-3
4.5 Setting the DRX Parameters Related to RFSP ..............................................................................................4-4
4.6 Typical Configuration....................................................................................................................................4-6
Issue 01 (2010-07-30)

iii
eRAN
DRX
Contents
5 Parameters ...................................................................................................................................5-1
6 Counters .......................................................................................................................................6-1
7 Glossary .......................................................................................................................................7-1
7.1 Terms.............................................................................................................................................................7-1
7.2 Acronyms and Abbreviations ........................................................................................................................7-1
8 Reference Documents ...............................................................................................................8-1
iv

Issue 01 (2010-07-30)
eRAN
DRX
1 Introduction
Introduction
1.1 Scope
Discontinuous Reception (DRX) refers to the method in which the UE intermittently enables
or disables the receiver to reduce the power consumption.
This document describes the basic feature LBFD-002017 DRX or TDLBFD-002017 DRX. It
focuses on the principle of DRX and the working mode of the UE with DRX enabled. It also
provides the engineering guidelines for deployment of this feature.
1.2 Intended Audience

This document is intended for:
z
Personnel who need to understand DRX
Personnel who work with Huawei products
1.3 Change History

This section provides information on the changes in different document versions.
There are two types of changes, which are defined as follows:
z
Feature change: refers to the change in the DRX feature of a specific product version.
Editorial change: refers to the change in wording or the addition of the information that
was not described in the earlier version.
Document Issues
The document issue is as follows:
z
01 (2010-07-30)
Draft (2010-05-20)
Issue 01 (2010-07-30)

1-1
eRAN
1 Introduction
01 (2010-07-30)
Compared with draft (2010-05-20) of eRAN2.0, issue 01 (2010-07-30) of eRAN2.0
incorporates the changes described in the following table.
Change Type
Change Description
Parameter Change
Feature change
Section 4.2 "Setting the Cell Duplex

Mode and TDD Uplink-Downlink
Subframe Configuration" is added.
The FddTddType
parameter is added. For
details, see section 4.2
"Setting the Cell Duplex
Mode and TDD
Uplink-Downlink
Subframe Configuration."
Descriptions in section 3.2.1

"Entering/Quitting the DRX Mode" are
modified.
The default value of ShortDRXCycle is
changed.
Editorial change
Feature IDs are added.
None.
Draft (2010-05-20)
Compared with 02 (2010-03-31) of eRAN1.1, draft (2010-05-20) of eRAN2.0 incorporates
the changes described in the following table.
Change Type
Change Description
Parameter Change
Feature change
The description about the RFSP is

added. For details, see section 3.2.5
"RFSP."
The following parameters are

added:
z
LongDRXCycleSpecial
OnDurationTimerSpecial
DRXInactivityTimerSpecial
For details, see chapter 4

"Engineering Guidelines."
Editorial change
1-2
None.

None.
Issue 01 (2010-07-30)
eRAN
DRX
2 Overview of DRX
Overview of DRX
This document focuses on the DRX feature in the RRC_CONNECTED state. For the DRX
feature in the RRC_IDLE state, see the Idle Mode Management Feature Parameter
Description.
For clarity, this document describes DRX from the point of view of FDD. In the case that DRX operates
differently on FDD and TDD, explanations will be provided for TDD.
This chapter provides the definition of DRX, and describes the principles, advantages and
typical cases for applications regarding DRX. If you are already familiar with them, you can
skip this chapter.
For more technical details about DRX, see Chapter 3 "DRX Technology." For engineering
guidelines, see Chapter 4 "Engineering Guidelines."
2.1 Definition
DRX is a working mode (hereinafter referred to as DRX mode) of the UE. The UE enters the
Active Time by turning on its receiver to receive the DL data and signaling only when
necessary and enters the Sleep Time by turning off its receiver to reduce power consumption
by no longer receiving any data in the rest of the time.
In DRX mode, there are two working states for the UE, which are the active state and the
sleep state corresponding to Active Time and Sleep Time, respectively. In non-DRX mode, the
UE always turns on its receiver and keeps working in active state.
z
DRX is a mandatory feature for all UEs of the LTE standard.
The UE cannot enter the DRX mode unless it receives the related RRC signaling from the eNodeB.
In DRX mode, the UE turns on/off the receiver alternatively. The DRX mode, however, has no
impact on the transmitter.
2.2 Advantage
Compared with continuous reception, DRX has the following advantages:
Issue 01 (2010-07-30)

2-1
eRAN
2 Overview of DRX
z
In DRX mode, the UE does not need to continuously monitor the Physical Downlink
Control Channel (PDCCH). Therefore, the reduction of power consumption helps to
prolong the serving time of the UE.
In DRX mode, the eNodeB sends the control information to a UE only in the Active
Time. This helps to save the resources and to increase the utilization of resources for the
control channel on the air interface.
2.3 Dependencies on Other Features

The DRX feature is closely related to other features.
The intermittent disabling of the UE receiver may restrict some operations of the eNodeB,
such as the delivery of the measurement configuration, report of the Channel Quality
Indication (CQI), report of the Sounding Reference Signal (SRS) measurement, and resource
scheduling. In this case, the eNodeB has to perform all these operations only in the DRX
Active Time. At the same time, in DRX mode, the eNodeB is allowed to give up the UL
synchronization with a UE when there is no data transmission for a long time.
In addition, the DRX feature and its parameter settings need to consider the QoS of services,
service type, and measurement configuration. For details, see section 3.3 "Feature
Interactions."
2.4 Typical Application

The DRX feature is mainly applied in the following scenarios:
z
Periodical and consecutive packet services, such as Voice over IP (VoIP).
Services insensitive to the delay, such as the webpage browsing, email, and FTP.
Services that generate small packets, such as the Presence service.

The Presence service refers to the communication method that is used to acquire the Presence
information about some users in real time by following a certain admission principle. Then, the acquired
information is presented to other users. The Presence information can be the user state, communication
capability, and personal preference. For example, the online alert function of MSN acts as a Presence
service.
2-2

Issue 01 (2010-07-30)
eRAN
DRX
3 DRX Technology
DRX Technology
3.1 Principle
To enable DRX, you must configure the DRX parameters for the eNodeB through the M2000
or Web Local Maintenance Terminal (Web LMT). Then, the eNodeB can deliver the DRX
parameters to the UE according to the algorithm at a proper time. After receiving the DRX
parameters, the UE enters the DRX mode and switches between the active state and the sleep
state.
The DRX parameters configured for an eNodeB are applicable to all the cells within the eNodeB.
Generally (see section 3.2.1 "Entering/Quitting the DRX Mode"), the eNodeB delivers the
DRX configuration information to instruct the UE to enter or quit the DRX mode through the
RRC Connection Reconfiguration message. The parameter configuration varies with the QoS
Class Identifier (QCI) of the service. For details, see section 4.6 "Typical Configuration."
In the following scenarios, the UE can automatically quit the DRX mode:
z
The UE leaves the RRC_CONNECTED state and enters the RRC_IDLE state due to poor RF
conditions.
Random access.
In DRX mode, the UE enables the receiver periodically to monitor the PDCCH for possible
signaling. This period of time is referred to as On Duration, and the related timer is On
Duration Timer.
An On Duration Timer is started at the beginning of each DRX cycle. Each DRX cycle
contains an On Duration and possibly one Sleep Time, as shown in Figure 3-1.
Figure 3-1 DRX cycle
Issue 01 (2010-07-30)

3-1
eRAN
DRX
3 DRX Technology
Difference between Active Time and On Duration:

z
The UE enters the DRX Active Time after the UE enables the receiver.
On Duration is one part of the DRX cycle, during which the UE receiver is enabled. The duration of
On Duration is determined by the On Duration Timer.
The DRX Active Time consists of the On Duration period and other periods during which the
receiver is enabled because some of the DRX related timers are working or some services of high
priority appear. For details about the UE in the DRX Active Time, see section 3.2.3 "Switchover
Between the Active Time and the Sleep Time."
The DRX cycle is classified into long DRX cycle and short DRX cycle. You can set the
duration of the long DRX cycle and short DRX cycle through the LongDRXCycle and
ShortDRXCycle parameters respectively, according to the QoS attributes of the service. After
the UE enters the DRX mode, the long DRX cycle is always the firstly applied cycle when the
DRX cycle starts. The long DRX cycle is mandatory and the short DRX cycle is optional. For
the detailed configuration principles, see section 4.3 "Setting the DRX Cycle Duration."
During the period of On Duration, if the UE decodes a PDCCH indicating an initial UL or DL
user data transmission for itself, a DRX Inactivity Timer will be started. Before DRX
Inactivity Timer expires, the UE keeps monitoring the PDCCH for another new initial
transmission. The timer will be restarted as soon as a new initial transmission is detected.
Thus, with the continual data transmission, a DRX Inactivity Timer is started or restarted
repeatedly to extend the Active Time.
When a DRX Inactivity Timer expires, the transmission of one stage is complete. However, it
is possible that another stage of transmission occurs shortly after the moment. In this case, the
UE can enter the short DRX cycle, if configured, to monitor the upcoming signaling messages
in On Duration more frequently than the UE does in the long DRX cycle. Thus, the
transmission delay is reduced. If the short DRX cycle is not configured, the UE continues to
apply the long DRX cycle. If the UE receives nothing after working in the short DRX cycle
for a certain period of time, the UE switches back to the long DRX cycle to save power
consumption. The period is called the life time of the short DRX cycle. The corresponding
timer is the DRX Short Cycle Timer which is counted on the basis of the repetition times of
the short DRX cycle.
After the duration of the DRX cycle is determined,
z
A longer Active Time helps to process the data with less delay, however, leads to more power
consumption on the receiver.
A shorter Active Time helps to make the UE more power-efficient, however, leads to more delay on
data processing.
In DRX mode, the eNodeB enables or disables the UL and DL resource scheduling based on
the DRX state of the UE.
The UE enables the receiver only in the DRX Active Time, which determines that the working
mode of the UE receiver and the other features are interdependent.
3.2 Key Technologies

3.2.1 Entering/Quitting the DRX Mode
The UE enters the DRX mode only after receiving the instruction from the eNodeB.
3-2

Issue 01 (2010-07-30)
eRAN
DRX
3 DRX Technology
The setting of the DRXAlgSwitch parameter determines whether the DRX feature of the
eNodeB is enabled or not. When the DRXAlgSwitch parameter is set to ON, the eNodeB can
deliver the signaling containing the DRX parameters to all UEs connected to this eNodeB.
When the DRXAlgSwitch parameter is set to OFF, the UE cannot enter or keep the DRX
mode.
If a UE is already in DRX mode and the DRXAlgSwitch parameter is set to OFF, the
eNodeB orders the UE to quit the DRX mode when the UE triggers the DRX reconfiguration.
Entering the DRX Mode

When all the following conditions are satisfied, the eNodeB delivers the RRC Connection
Reconfiguration message, where the DRX-Configuration information element (IE) is set to
setup, to the UE. Upon reception of this message, the UE saves all the DRX parameters to the
local register and enters the DRX mode.
z
The DRXAlgSwitch parameter is set to ON.
All services of the UE support DRX.
The QoS attributes of a service type are indicated by QCI. The EnterDRXSwitch
parameter of each QCI decides whether the service corresponding to a QCI supports
DRX or not. If the EnterDRXSwitch parameter is set to ON, the corresponding
service supports DRX. If the EnterDRXSwitch parameter is set to OFF, the
corresponding service does not support DRX.
A Qci indicates the QoS class of a service type. Table 3-1 lists the standardized QCI
characteristics. It is recommended that the services whose QCIs are 1, 4, 6, 8, and 9
be set to support DRX. For details, see section 4.6 "Typical Configuration."
Table 3-1 Standardized QCI characteristics

QCI
Service
Priority
PDB(ms)
PELR
Example Service
GBR
100
10-2
Conversational voice
150
10-3
Conversational video
(Live streaming)
50
10-3
Real-time gaming
300
10-6
Non-conversational video
(Buffered streaming)
100
10-6
IMS signaling
300
10-6
Video (Buffered streaming)

TCP-based
(eg.www,e-mail,chat,ftp,p2p,etc)
100
10-3
Voice
video(Live streaming)
Interactive games
300
10-6
Video (Buffered streaming)

TCP-based(eg.www,e-mail,chat,ftp,
p2p,etc)
Issue 01 (2010-07-30)
Non-GBR

3-3
eRAN
DRX
3 DRX Technology
PDB: Packet Delay Budget
GBR: Guaranteed Bit Rate
PELR: Packet Error Loss Rate
The data volume of the UE is extremely low.
The DRX cycle of the UE is equal to or shorter than the CQI cycle.
The moving speed of the UE is medium or low.
Quitting the DRX Mode

When any of the following conditions is satisfied, the eNodeB delivers the RRC Connection
Reconfiguration message, where the DRX-Configuration IE is set to release, to the UE. Upon
reception of this message, the UE clears all the DRX parameters on the local register and quits
the DRX mode.
z
A service on the UE does not support DRX.
The data volume of the UE is relatively high.
The DRX cycle of the UE is longer than the CQI cycle.
The moving speed of the UE is high.
In addition, if the DRXAlgSwitch parameter is set to OFF, the eNodeB orders the UE to quit
the DRX mode when the UE triggers the DRX reconfiguration.
In semi-persistent scheduling, the UE does not quit the DRX mode when the DRX cycle of the UE is
longer than the CQI cycle. That is, the eNodeB does not decide whether to order the UE to quit the DRX
mode based on the comparison result between the DRX cycle of the UE and the CQI cycle.
3.2.2 Starting the DRX Cycle

Entering the DRX mode does not mean that a DRX cycle will start at the moment. Actually, a
DRX cycle begins at the subframe that meets the following conditions. Then, the UE can
periodically enable or disable the receiver to reduce power consumption.
z
When the long DRX cycle is configured

[(SFN x 10) + SSFN] modulo (LongDRXCycle) = DRX Start Offset;
When the short DRX cycle is configured

[(SFN x 10) + SSFN] modulo (ShortDRXCycle) = (DRX Start Offset) modulo
(ShortDRXCycle);
In the formula, DRX Start Offset represents the time from which the long DRX cycle of the
UE is started. (DRX Start Offset) modulo (ShortDRXCycle) represents the time from which
the short DRX cycle of the same UE is started. In the formula, modulo represents
complementation. The eNodeB delivers LongDRXCycle, ShortDRXCycle, and DRX Start
Offset to the UE through the RRC Connection Reconfiguration message.
z
SFN: System Frame Number
SSFN: System Subframe Number
Figure 3-2 shows how the UE enters the DRX mode. The eNodeB delivers the same long
DRX cycle to UE 1 and UE 2 within the cell coverage, and instructs UE 1 and UE 2 to enter
3-4

Issue 01 (2010-07-30)
eRAN
DRX
3 DRX Technology
the DRX mode at TTI# 1 and TTI# 0 respectively. But, UE 1 and UE 2 enter the DRX cycle at
TTI# 3 and TTI# 4 respectively based on the configured DRX Start Offset.
Figure 3-2 Entering the DRX mode and starting of the DRX cycle
3.2.3 Switchover Between the Active Time and the Sleep Time
The switchover between the Active Time and Sleep Time may be influenced by the
DRX-related timers and services.
When a DRX cycle is configured, the Active Time includes the following periods of time:
z
The time when On Duration Timer, DRX Inactivity Timer, DRX Retransmission Timer,
or Contention Resolution Timer is working. For more information on the timers, see
Table 3-2.
The time when a Scheduling Request is pending.
The time when an uplink grant for a pending Hybrid Automatic Retransmission Request
(HARQ) retransmission can occur.
The time when a PDCCH indicating a new transmission addressed to the UE has not
been received after successful reception of a Random Access Response in the
non-contention-based random access scenario.
Table 3-2 Definition of DRX timers

DRX Timer
Parameter
Definitio
n
Description
On Duration
Timer
OnDurationTimer
Function
The periodical starting of this timer

instructs the UE to enable the
receiver periodically. The UE
monitors the PDCCH before the
timer expires.
Start
This timer is started at the starting

subframe of the DRX cycle. For
details, see section 3.2.2 "Starting
the DRX Cycle."
Issue 01 (2010-07-30)

3-5
eRAN
DRX
3 DRX Technology
DRX Timer
DRX
Inactivity
Timer
DRX Short
Cycle Timer
3-6
Parameter
DRXInactivityTimer
DRXShortCycleTimer
Definitio
n
Description
Timing
The timing is based on the number

of consecutive PDCCH subframe(s).
Stop
This timer is stopped after the UE

receives the DRX command MAC
Control Element (MCE).
This timer is stopped after it

expires.
Expire
This timer is stopped. The UE does

not perform further operations.
Function
This timer is used to determine

whether the DRX Active Time of
the UE is extended because of the
arrival of new data.
This timer provides a reference for

the UE to apply the short DRX
cycle.
Start
This timer is started or restarted

when the UE successfully decodes a
PDCCH indicating an initial UL
grant or DL user data for this UE.
Timing

Stop
This timer is stopped after

receiving the DRX command
MCE.
This timer is stopped after it

expires.
Expire
After this timer expires, the UE

applies the short DRX cycle if
configured, and the DRX Short
Cycle Timer is started or restarted,
or the UE applies the long DRX
cycle if no short DRX cycle is
configured.
Function
This timer identifies the life time of

the short DRX cycle, which is the
repetition times of the short DRX
cycle.

Issue 01 (2010-07-30)
eRAN
DRX
3 DRX Technology
DRX Timer
DRX
Retransmissi
on Timer
HARQ RTT
Timer
Issue 01 (2010-07-30)
Parameter
DRXReTxTimer
Definitio
n
Description
Start
After DRX Inactivity Timer

expires, this timer is started or
restarted if the short DRX cycle is
configured.
After the UE receives the DRX

command MCE, this timer is
started or restarted if the short
DRX cycle is configured.
The UE applies the short DRX

cycle after DRX Short Cycle
Timer is started.
Timing
The timing is based on repetition

times of the short DRX cycle.
Stop
This timer is stopped after it expires.
Expire
This timer is stopped, and the UE

applies the long DRX cycle.
Function
This timer indicates the period of

time for the UE to wait for HARQ.
If no DL data retransmission is
received within this period of time,
the UE may disable the receiver and
enter Sleep Time.
Start
When the HARQ RTT Timer

expires, the DRX Retransmission
Timer is started or restarted if the
UE does not receive the ACK
feedback of the corresponding
downlink data.
Timing

Stop
This timer is stopped if the UE

receives the retransmitted data
before the timer expires.
Expire
This timer is stopped, and the UE

takes no further actions.
Function
This timer specifies the minimum

number of subframe(s) before a DL
HARQ retransmission arrives in the
case of a packet error occurs. This
timer is used to determine when to
start the DRX Retransmission
Timer.

3-7
eRAN
DRX
3 DRX Technology
DRX Timer
Contention
Resolution
Timer
Parameter
Definitio
n
Description
Start
This timer is stopped at the subframe

when there may be a possible
semi-persistent DL data
transmission, or it is stopped at the
subframe when the UE learns by
detecting the PDCCH that one of its
HARQ processes has new subframes
for DL data transmission, it stops the
DRX Retransmission Timer related
to this HARQ process. Meanwhile,
HARQ RTT Timer is started.
Timing

subframe(s).
Stop
This timer is stopped after it expires.
Expire
This timer is stopped, and DRX

Retransmission Timer is started.
Function
This timer indicates the period of

time for the UE to wait for the
resolution of contention. If no Msg4
is received within this period of
time, the UE may disable the
receiver and enter Sleep Time.
Start
This timer is started when the UE

sends the Msg3 message in
contention-based random access
procedure.
Timing

Stop
This timer is stopped after the UE

receives Msg4 or the resource
contention is successfully resolved.
Expire
This timer is stopped and the UE

begins to handle the problems in
random access procedure.
Figure 3-3 takes the UE in FDD mode as an example to illustrate how the UE receiver
performs the switchover between Active Time and Sleep Time based on different timers and
other service processes.
3-8

Issue 01 (2010-07-30)
eRAN
DRX
3 DRX Technology
Figure 3-3 Switchover between the Active Time and Sleep Time
Figure 3-3 shows the effects of the timers and services on Active Time. The descriptions in
the figure describe the conditions under which the state transition starts. For example, "OD"
DRX cycle start is the starting conditions for On Duration Timer at TTI-2 and TTI-15. "OD"
is the abbreviation of this condition or event.
The UE DRX status shown in the green (bottom) plot of Figure 3-3 is the combination of all
Active Time described in the other plots (excluding the plot of HARQ RTT Timer) of the
figure.
For details, see Table 3-3.
Table 3-3 Conditions description for state transition starts
Condition
Meaning
OD
DRX cycle start
Issue 01 (2010-07-30)

3-9
eRAN
DRX
3 DRX Technology
Condition
Meaning
IA
PDCCH (UL grant or DL) received for initial transmission
HARQ RTT Timer Expired
SR
Schedule request sending for initial UL transmission
UR
UL NACK and retransmission required
RAR
Random access response received for the dedicated preamble
CR
Random access MSG3 sending
In the plot of HARQ RTT Timer in Figure 3-3, the "HARQ DL raising" refers to one of the two
HARQ DL transmission scenarios, which is the subframe where the semi-persistent DL data
transmission is scheduled to start, or the subframe where the DL data transmission is to start (the UE
learns this by monitoring the PDCCH).
The HARQ RTT Timer does not directly affect the DRX Active Time. It influences the DRX mode
by influencing the DRX Retransmission Timer.
The frame formats in TDD mode are different from that in FDD mode. Therefore, the definition of
PDCCH subframe in TDD mode is also different from that in FDD mode. In FDD mode, each radio
subframe can carry the PDCCH, while in TDD mode, PDCCH subframe refers to the DL subframe
and the subframe containing DwPTS. Figure 3-3 is also applicable to the TDD mode. However, the
scales of the TTI axis of several related plots should be considered as the PDCCH subframes.
3.2.4 Switchover Between Long DRX Cycle and Short DRX Cycle
Even though the eNodeB delivers both long DRX cycle and short DRX cycle for the UE, the
UE can only apply a single type of cycle at a time, i.e., either the long DRX cycle or the short
DRX cycle.
If the eNodeB delivers both the long DRX cycle and short DRX cycle to the UE, the UE can
switch over between the long DRX cycle and short DRX cycle based on the following
principles.
Long DRX Cycle to Short DRX Cycle

After the DRX Inactivity Timer expires, or the UE receives the DRX Command MCE from
the eNodeB, the UE quits the long DRX cycle and applies the short DRX cycle.
z
Cycle switchover triggered by DRX Inactivity Timer

In the following two scenarios, data transmission is most likely to happen. Thus, the UE
should monitor the PDCCH frequently to reduce the service delay.
The last packet of a consecutive data transmission is received. However, the next data
transmission is not started after some time.
The initial transmission of one packet of a consecutive data transmission is faulty,

and the retransmission lasts for a long period of time, then the next initial
transmission may occur after a certain period of time.
In the preceding two scenarios, the UE may fail to receive the PDCCH indicating an
initial transmission before DRX Inactivity Timer expires. After this timer expires, the UE
applies the short DRX cycle if the eNodeB has configured the short DRX cycle for the
UE. If the short DRX cycle is not configured, the UE applies the long DRX cycle.
3-10

Issue 01 (2010-07-30)
eRAN
DRX
3 DRX Technology
z
Cycle switchover triggered by DRX Command MCE

After the UE receives DRX Command MCE, the UE applies the short DRX cycle if the
eNodeB has configured the short DRX cycle for the UE. If the short DRX cycle is not
configured, the UE applies the long DRX cycle.
Short DRX Cycle to Long DRX Cycle

After DRX Short Cycle Timer expires, the UE applies long DRX cycle.
3.2.5 RFSP
Not all UEs need to use DRX to reduce power consumption. For example, data cards or UEs
with sufficient power supply do not need DRX. The Subscriber Profile ID for RAT/Frequency
Priority (RFSP) function enables the telecom operator to designate a UE as a data card or a
UE with sufficient power supply through simple configuration. Through this function, a UE
can be prevented from operating in DRX mode. Alternatively, the parameters that are
specially designed can be used in DRX mode to reduce the service delay.
On the Evolved Packet Core (EPC) side, the RFSP of a UE is an integer ranging from 1 to 256.
The telecom operator defines the RFSP and binds the RFSP to the Mobile Station
International ISDN Number (MSISDN) of the UE. When the UE accesses the EPC through
the eNodeB, the RFSP of the UE is sent to the eNodeB through the INITIAL CONTEXT
SETUP REQUEST message over the S1 interface.
On the eNodeB side, the telecom operator can specify a collection of integer(s), known as
NotEnterDRXRfspSet, ranging from 1 to 256 through the M2000/Web LMT. If the RFSP of
a UE is equal to an integer in the collection, the eNodeB decides that the UE is of a special
type (a data card or a UE with sufficient power supply).
When the DRX switch is enabled, the eNodeB allows the UEs of the special type to work in
DRX mode by specifying the specially designed parameters. In this case, the UEs of the
special type adhere to the principles described in section 3.2.1 "Entering/Quitting the DRX
Mode." The specially designed parameters are LongDRXCycleSpecial,
OnDurationTimerSpecial, and DRXInactivityTimerSpecial, which are described in section
4.5 "Setting the DRX Parameters Related to RFSP."
3.3 Feature Interactions

This section describes the relationship between DRX and scheduling, HARQ, random access,
measurement, CQI/SRS measurement and report, UL synchronization, and handover.
Compared with other LTE features, DRX has a low priority. Therefore, the UE could enter
Active Time whenever the services or procedures with higher priority occurred. After they
were completed, the UE could return to Sleep Time. Note that CQI/SRS measurement and
report are not subject to this rule.
3.3.1 Dependency on Scheduling

The eNodeB enables the resource scheduling for the UE only in the DRX Active Time. Note
that in this case the system information and paging are not considered.
For the UE working in DRX mode, it performs the Schedule Request (SR) operation once
data appears in the UE buffer whether it is in Active Time or not. If the UE is in Sleep Time, it
switches back to Active Time immediately and begins to monitor the PDCCH. After receiving
Issue 01 (2010-07-30)

3-11
eRAN
DRX
3 DRX Technology
a PDCCH indicating an initial data transmission, DRX Inactivity Timer is started immediately.
Thus, Active Time continues and the UE receives the required scheduling resources.
3.3.2 Dependency on HARQ

The priority of HARQ is higher than that of DRX. In other words, the UE can send or receive
the HARQ feedback after the HARQ process is started whether the UE is in Active Time or
not. Even if the UE is in Sleep Time, it immediately switches to the Active Time.
3.3.3 Dependency on Random Access

In the case of random access, the UE always responds to the random access request, whether
it is in Active Time or not. In this case, the UE enables the receiver and enters Active Time
upon reception of a random access request.
3.3.4 Dependency on Measurement

The priority of measurement is higher than that of DRX. Therefore, the priority is given to
measurement if the configuration of measurement and DRX conflicts.
For details on the measurement procedure in DRX mode, see the Mobility Management in
Connected Mode Feature Parameter Description.
The measurement procedure of the UE in LTE standard can be divided into common
measurement and Gap-based measurement. Common measurement is used for intra-frequency
measurement. Gap-based measurement is used for inter-frequency measurement and
inter-RAT measurement.
Common Measurement
In random access scenario, the UE enters Active Time and uses the first available Random
Access Channel (RACH) to report the UL measurement report, whether the UE is in DRX
Active Time or not.
In other scenarios, the UE reports the measurement report in Active Time. If the UE is in
Sleep Time, then it reports the measurement report in the Active Time of the next DRX cycle.
Gap-Based Measurement
In Gap-based measurement, Gap appears every 40 or 80 ms with the duration of 6 ms. To
minimize the impact on data transmission, the eNodeB should make Gaps appear in the DRX
Sleep Time or makes the configuration of DRX cycle meet the distribution of Gaps.
As shown in Figure 3-4, Gap appears every 40 ms, and is six TTIs earlier than the DRX cycle.
In Figure 3-4, the working status of On Duration Timer is used to represent the DRX cycle.
3-12

Issue 01 (2010-07-30)
eRAN
DRX
3 DRX Technology
Figure 3-4 DRX cycle and Gap-based measurement
3.3.5 Dependency on CQI/SRS Measurement and Report

In DRX mode, the periodical measurement and reporting of Channel Quality Indication (CQI)
can be performed only in Active Time of the UE, and the CQI cycle affects the UE in entering
or quitting the DRX mode (except in the case of semi-persistent scheduling).
In DRX mode, the periodical measurement and reporting of Sounding Reference Signal (SRS)
can be performed only in Active Time of the UE.
If the UE is in Sleep Time, then the report of the CQI/SRS measurement has to wait till the
DRX Active Time.
3.3.6 Dependency on UL Synchronization

The eNodeB should maintain the UL synchronization with the UE at the beginning of the UE
DRX cycle.
After the UE works in the DRX mode for a certain period of time and there is no data
transmission, the eNodeB can give up the UL synchronization of the UE.
If the UE needs to restore the UL synchronization later, it can obtain the UL synchronization
through the random access procedure.
3.3.7 Dependency on Handover

In different stages of a handover, DRX is used in the following manners:
z
When the handover procedure starts:

The source eNodeB sends the RRC Connection Reconfiguration message to order the
UE to quit the DRX mode.
If the UE is in Sleep Time, it can receive the handover command only in the next Active
Time.
If the handover succeeds:

The UE cannot use the DRX feature if the DRX feature is disabled on the target eNodeB.
If the handover fails:

The UE remains in the source cell and the eNodeB judges whether the UE can enter the
DRX mode based on the selected scheme.
Issue 01 (2010-07-30)

3-13
eRAN
DRX
3 DRX Technology
For details on the handover procedure in DRX mode, see the Mobility Management in
Connected Mode Feature Parameter Description.
3-14

Issue 01 (2010-07-30)
eRAN
DRX
4 Engineering Guidelines
Engineering Guidelines
Chapter 3 describes that different services may have different requirements on the DRX
feature. Thus, the configuration of the DRX parameters should consider the specific service
type.
This chapter describes the parameter configuration for the UE to enter/quit the DRX mode under the
signaling instruction sent by the eNodeB. For the scenarios that the UE automatically quits the DRX
mode without receiving the signaling from the eNodeB, see section 3.1 "Principle."
There is no specific requirement for the sequence of setting the DRX switch, setting the DRX cycle
duration, setting the timers, and setting the DRX parameters related to RFSP.
This chapter works as the reference for network planning and feature design. It consists of the
basic configuration principles of the parameters and the recommended configuration for some
parameters.
The Web LMT or M2000 should be used to ensure that the DRX parameters are correctly
configured on the eNodeB.
4.1 Setting the DRX Switch

The setting of the DRXAlgSwitch parameter determines whether the DRX feature of the UEs
within the coverage area of this eNodeB is enabled or not.
When the DRXAlgSwitch parameter is set to ON, the eNodeB can deliver the RRC
Connection Reconfiguration message containing the DRX parameters to a UE connected to
this eNodeB. The UEs can enter the DRX mode only after receiving the DRX parameters. The
following sections give a detailed explanation on the DRX parameters.
If a UE is already in DRX mode, the eNodeB orders the UE to quit the DRX mode when the
DRXAlgSwitch parameter is set to OFF.
4.2 Setting the Cell Duplex Mode and TDD

Uplink-Downlink Subframe Configuration
For FDD, set the FddTddType parameter (indicating the cell duplex mode and TDD
uplink/downlink subframe assignment) to FDD Mode. For TDD, set the FddTddType
Issue 01 (2010-07-30)

4-1
eRAN
DRX
parameter to TDD Configuration 0, TDD Configuration 1, TDD Configuration 2, TDD

Configuration 3, TDD Configuration 4, TDD Configuration 5, or TDD Configuration 6.
Reference document [3] defines the TDD uplink-downlink subframe configurations, which
are listed in Table 4-1.
Table 4-1 TDD uplink-downlink subframe configurations
TDD Uplink-Downlink
Subframe
Configuration
Downlink-to-Uplink
Switch-Point Periodicity
Subframe Number
TDD configuration 0
5 ms
DSUUUDSUUU
TDD configuration 1
5 ms
DSUUDDSUUD
TDD configuration 2
5 ms
DSUDDDSUDD
TDD configuration 3
10 ms
DSUUUDDDDD
TDD configuration 4
10 ms
DSUUDDDDDD
TDD configuration 5
10 ms
DSUDDDDDDD
TDD configuration 6
5 ms
DSUUUDSUUD
For each subframe in a TDD radio frame, "D" denotes the subframe reserved for downlink transmission,
"U" denotes the subframe reserved for uplink transmission, and "S" denotes a special subframe with the
three fields DwPTS, GP and UpPTS.
4.3 Setting the DRX Cycle Duration

The configuration of long DRX cycle and short DRX cycle should consider the power
consumption, service delay, and traffic volume.
z
If you want to increase the DRX Active Time of the UE receiver, you can configure a
long DRX cycle with a short duration. Thus, the services can be handled on time when
the traffic is heavy and the service delay is reduced.
If you want the UE to be more power efficient while retaining the short delay, you can
configured both the long DRX cycle and short DRX cycle on the eNodeB.
LongDRXCycle
This parameter defines the number of subframes occupied by a long DRX cycle of the service
corresponding to a QCI. It is used with the QCI parameter.
You can determine the DRX cycle based on the Packet Delay Budget (PDB) of the service.
Generally, the maximum duration of DRX can be calculated by the following formula:
Maximum DRX Cycle duration = PDB 20 ms (transmission delay from GateWay to
eNodeB).
The setting of LongDRXCycle is based on the service QCI. If a UE has the services of
multiple QCIs simultaneously in DRX mode, the UE chooses the LongDRXCycle parameter
with minimum value as the actual duration of a long DRX cycle.
4-2

Issue 01 (2010-07-30)
eRAN
DRX
For the recommended configuration, see section 4.6 "Typical Configuration."

In the case that a short DRX cycle is configured, you are advised to set the value of LongDRXCycle to
a multiple of the value of ShortDRXCycle.
ShortDRXSwitch
This parameter determines whether a short DRX cycle is supported.
You can set this parameter to ON to reduce service delay. In this case, the UE automatically
enters the short DRX cycle when data transmission is most likely to occur.
If this parameter is set to OFF, only long DRX cycles can be configured for the eNodeB.
ShortDRXCycle
This parameter must be configured when the ShortDrxSwitch parameter is set to ON.
This parameter defines the life span of a short DRX cycle in unit of subframe.
4.4 Setting the Timers

On Duration Timer and DRX Inactivity Timer are shared by the long DRX cycle and short
DRX cycle. The mapping between the timer and parameter is listed in Table 4-2.
Table 4-2 Mapping between the timer and parameter
Timer
Parameter
On Duration Timer
OnDurationTimer
DRX Inactivity Timer
DRXInactivityTimer
DRX Short Cycle Timer
DRXShortCycleTimer
DRX Retransmission Timer
DRXReTxTimer
Contention Resolution Timer can be configured in the random access function, while HARQ RTT Timer
adopts a fixed value. For details, see reference document [1].
OnDurationTimer
This parameter defines the number of PDCCH subframes occupied by the On Duration Timer
of the DRX mode corresponding to a QCI service.
If the value of the OnDurationTimer parameter is equal to the duration of the DRX cycle, no
Sleep Time is configured. In this case, the service delay is the minimum, but the power
consumption of the UE cannot be reduced. Therefore, the duration of OnDurationTimer
must be less than the duration of the DRX cycle.
The value of this parameter varies with the settings of the QCI and FddTddType parameters.
For details about how to set this parameter, see the eNodeB MO Reference.
Issue 01 (2010-07-30)

4-3
eRAN
DRX
DRXInactivityTimer
This parameter defines the number of PDCCH subframes occupied by the DRX Inactivity
Timer of the DRX mode corresponding to a QCI service.
The duration of this parameter cannot be shorter than that of the OnDurationTimer
parameter, and cannot be longer than the duration of the long DRX cycle. If short DRX cycle
is configured, the duration of the OnDurationTimer parameter cannot be larger than the
duration of the short DRX cycle.
The value of this parameter varies with the settings of the QCI and FddTddType parameters.
For details about how to set this parameter, see the eNodeB MO Reference.
DRXShortCycleTimer
This parameter must be configured when the ShortDrxSwitch parameter is set to ON.
This parameter defines the life span of a short DRX cycle, indicating the minimum number of
short DRX cycles the UE has to experience before the UE switches back to a long DRX cycle.
In DRX mode, the UE may enter the short DRX cycle when data transmission is most likely
to happen. A large value of this parameter indicates that the short DRX cycle becomes long,
the delay becomes small, but the UE power consumption is high.
DRXReTxTimer
This parameter defines the number of PDCCH subframes occupied by the DRX
Retransmission Timer. DRX Retransmission Timer specifies the maximum waiting time of the
UE to receive the DL retransmission data.
The maximum delay for the DL scheduling during retransmission is 6 ms. In practical
applications, some margin can be reserved. For example, 8 ms can be adopted. In this case,
DRXReTxTimer is 8 ms long.
For the recommended configuration, see section 4.6 "Typical Configuration."
4.5 Setting the DRX Parameters Related to RFSP

NotEnterDRXRfspSet
This parameter defines the RFSP set that is mapped to special DRX configuration for
non-power-saving UEs. This parameter can be customized by the operator. If the RFSP of a
UE is in the set, special DRX configuration is applied to the UE.
LongDRXCycleSpecial
This parameter defines the long DRX cycle that is mapped to RFSP for non-power-saving
UEs.
Generally, RFSP-capable UEs have sufficient power supply. The major concern for
RFSP-capable UEs is to minimize the delay, and power saving is a secondary factor. In this
case, the DRX cycle is relatively short.
z
4-4
If the expected power to be saved for the UE is low, the maximum delay caused by the
DRX is relatively short. In this case, this parameter can be set to a relatively small value.
Issue 01 (2010-07-30)
eRAN
DRX
z
If the expected power to be saved for the UE is high, the maximum delay caused by the
DRX is relatively long. In this case, this parameter can be set to a relatively large value.
Generally, you are advised to set this parameter to SF10 (10 subframes).
This parameter defines the duration that is mapped to RFSP for non-power-saving UEs.
case, the length of On Duration Timer is relatively long.
In FDD mode, you are advised to set this parameter to PSF4 (4 subframes). In TDD mode,
set this parameter according to Table 4-3.
Table 4-3 Configuration of OnDurationTimer Special in TDD mode
Uplink/Downlink
Subframe Configuration
OnDurationTimer Special
PSF2
PSF2
PSF3
PSF2
PSF3
PSF3
PSF2
DRXInactivityTimerSpecial
This parameter defines the duration of DRX Inactivity Timer that is mapped to RFSP for
non-power-saving UEs.
case, the length of DRX Inactivity Timer is relatively long.
In FDD mode, you are advised to set this parameter to PSF5 (5 subframes). In TDD mode,
set this parameter according to Table 4-4.
Table 4-4 Configuration of DRXInactivityTimerSpecial in TDD mode
Uplink/Downlink
PSF3
PSF3
Issue 01 (2010-07-30)

4-5
eRAN
DRX
Uplink/Downlink
PSF4
PSF3
PSF4
PSF4
PSF3
ShortDrxCycleSpecial
This parameter defines the short DRX cycle that is mapped to RFSP for non-power-saving
UEs.
z
DRX is relatively short. In this case, this parameter does not need to be configured.
DRX is relatively long. In this case, this parameter is configured.
Generally, this parameter is not required. If required, set this parameter to SF5(5 subframes).
DrxShortCycleTimerSpecial
This parameter defines the duration of the short DRX cycle timer that is mapped to RFSP for
non-power-saving UEs.
z
DRX is relatively short. In this case, this parameter does not need to be configured.
DRX is relatively long. In this case, this parameter is configured.
Generally, this parameter is not required. If required, set this parameter to 2.
4.6 Typical Configuration

Table 4-5 describes the recommended values for the DRX parameters based on the
configuration principles and simulation results. The unit for the timing is SubFrame (SF), and
PSF refers to the PDCCH subframe.
For the parameters which are not included in the table, you can set the parameter based on the
descriptions in the preceding part. Table 4-5 is applicable to FDD.
Table 4-5 Typical configuration of DRX (recommended value)
QCI
1
4-6
EnterDRX
LongDRX
ShortDRX
OnDuration
DRXInactivity
DRXRetransmission
Switch
Cycle (SF)
Cycle (SF)
Timer (PSF)
Timer (PSF)
Timer (PSF)
ON
20
10

Issue 01 (2010-07-30)
eRAN
DRX
QCI
EnterDRX
LongDRX
ShortDRX
OnDuration
DRXInactivity
DRXRetransmission
Switch
Cycle (SF)
Cycle (SF)
Timer (PSF)
Timer (PSF)
Timer (PSF)
OFF
OFF
ON
20
OFF
ON
40
OFF
ON
40
ON
40
Issue 01 (2010-07-30)

4-7
eRAN
DRX
5 Parameters
Parameters
This chapter describes the parameters related to DRX.

For the meaning of each parameter, see Table 5-1. For the default value, value ranges, and
MML commands of each parameter, see 0.
Table 5-1 Parameter description (1)
MO
Parameter ID
Description
DRX
DrxAlgSwitch
Indicates the DRX switch. When the

switch is ON, the DRX feature is
supported. When the switch is OFF, the
DRX feature is not enabled.
DRX
ShortDrxSwitch
Indicates whether the short-cycle DRX

is supported. When a short-cycle DRX is
supported, the service delay is reduced.
DRX
NotEnterDrxRfspSet
Indicates the RAT/Frequency Selection

Priority (RFSP) set that is mapped to
special DRX configuration for
non-power-saving UEs. The RFSP set is
defined by the operator. If the RFSP of a
UE is contained in the set, the special
DRX configuration is applied to the UE.
The format of the set is as follows: A1
A2~A3 ... A20 A21~A22 ..., where A1,
A2, ..., A22 are all integers within the
value range of [1,256]. The RFSP set is
null by default.
DRX
LongDrxCycleSpecial
Indicates the long DRX cycle that is

applied only to the non-power-saving
UEs whose RFSPs are contained in the
RFSP set.
DRX
Indicates the length of the On Duration

Timer that is only applied to the
non-power-saving UEs whose RFSP is
contained in the RFSP set.
Issue 01 (2010-07-30)

5-1
eRAN
DRX
5 Parameters
5-2
MO
Parameter ID
Description
DRX
DrxInactivityTimerSpecial
Indicates the length of the DRX

Inactivity Timer that is
applied to only the non-power-saving
UEs whose RFSP is contained in
the RFSP set.
DRX
ShortDrxCycleSpecial
Indicates the short DRX cycle that is

UEs whose RFSP is contained in the
RFSP set.
DRX
DrxShortCycleTimerSpecial
Indicates the short DRX cycle that is

UEs whose RFSP indexes are contained
in the RFSP index set.
DRXTimer
FddTddType
Indicates the cell duplex mode and TDD

UL/DL subframe assignment.
DRXTimer
Qci
Indicates the QoS Class Indication (QCI)

of the EPS bearer. Different QCIs
indicate different QoS specifications
such as packet delay, packet loss/error
rate, and whether the service is a GBR
service or not. For details, see table 6.1.7
in 3GPP TS 23.203.
DRXTimer
OnDurationTimer
Indicates the length of the On Duration

timer.
DRXTimer
DrxInactivityTimer
Indicates the length of the DRX

Inactivity Timer.
DRXParaPerQ
CI
DrxReTxTimer
Indicates the length of DRX

retransmission timer.
DRXParaPerQ
CI
DrxShortCycleTimer
Indicates the length of the DRX short

cycle timer. If this parameter is set to a
large value, the UE follows the short
DRX cycle, if configured, for a long
time.
DRXParaPerQ
CI
EnterDrxSwitch
Indicates whether the bearer with a QCI

support the DRX feature. The value ON
indicates that the bearer supports DRX.
The value OFF indicates that the bearer
does not support DRX. A UE can enter
the DRX mode only when any bearer is
running on it support DRX.
DRXParaPerQ
CI
LongDrxCycle
Indicates the length of the long DRX

cycle.
DRXParaPerQ
CI
ShortDrxCycle
Indicates the length of the short DRX

cycle.

Issue 01 (2010-07-30)
eRAN
DRX
5 Parameters
Table 5-2 Parameter description (2)

MO
Parameter
ID
Default
Value
GUI Value
Range
Actual
Value
Range
Unit
MML
Command
DRX
DrxAlgSwitc
h
OFF(Off)
OFF(Off),
ON(On)
OFF, ON
None
MOD DRX
LST DRX
DRX
ShortDrxSwi
tch
ON(On)
OFF(Off),
ON(On)
OFF, ON
None
MOD DRX
LST DRX
DRX
NotEnterDrx
RfspSet
null
0~250
characters
0~250
None
MOD DRX
LST DRX
DRX
LongDrxCyc
leSpecial
SF10(10
subframes)
SF10(10
subframes),
SF20(20
subframes),
SF32(32
subframes),
SF40(40
subframes),
SF64(64
subframes),
SF80(80
subframes),
SF128(128
subframes),
SF160(160
subframes),
SF256(256
subframes),
SF320(320
subframes),
SF512(512
subframes),
SF640(640
subframes),
SF1024(1024
subframes),
SF1280(1280
subframes),
SF2048(2048
subframes),
SF2560(2560
subframes)
SF10, SF20,
SF32, SF40,
SF64, SF80,
SF128,
SF160,
SF256,
SF320,
SF512,
SF640,
SF1024,
SF1280,
SF2048,
SF2560
subframe
MOD DRX
LST DRX
DRX
OnDurationT
imerSpecial
PSF4(4
subframes)
PSF1(1
subframes),
PSF2(2
subframes),
PSF3(3
subframes),
PSF1, PSF2,
PSF3, PSF4,
PSF5, PSF6,
PSF8,
PSF10,
PSF20,
subframe
MOD DRX
LST DRX
Issue 01 (2010-07-30)

5-3
eRAN
DRX
5 Parameters
MO
DRX
5-4
Parameter
ID
DrxInactivity
TimerSpecial
Default
Value
PSF5(5
subframes)
GUI Value
Range
Actual
Value
Range
PSF4(4
subframes),
PSF5(5
subframes),
PSF6(6
subframes),
PSF8(8
subframes),
PSF10(10
subframes),
PSF20(20
subframes),
PSF30(30
subframes),
PSF40(40
subframes),
PSF50(50
subframes),
PSF60(60
subframes),
PSF80(80
subframes),
PSF100(100
subframes),
PSF200(200
subframes)
PSF30,
PSF40,
PSF50,
PSF60,
PSF80,
PSF100,
PSF200
PSF1(1
subframes),
PSF2(2
subframes),
PSF3(3
subframes),
PSF4(4
subframes),
PSF5(5
subframes),
PSF6(6
subframes),
PSF8(8
subframes),
PSF10(10
subframes),
PSF20(20
subframes),
PSF30(30
subframes),
PSF40(40
subframes),
PSF50(50
subframes),
PSF60(60
PSF1, PSF2,
PSF3, PSF4,
PSF5, PSF6,
PSF8,
PSF10,
PSF20,
PSF30,
PSF40,
PSF50,
PSF60,
PSF80,
PSF100,
PSF200,
PSF300,
PSF500,
PSF750,
PSF1280,
PSF1920,
PSF2560

Unit
MML
Command
subframe
MOD DRX
LST DRX
Issue 01 (2010-07-30)
eRAN
DRX
MO
5 Parameters
Parameter
ID
Default
Value
GUI Value
Range
Actual
Value
Range
Unit
MML
Command
SF2, SF5,
SF8, SF10,
SF16, SF20,
SF32, SF40,
SF64, SF80,
SF128,
SF160,
SF256,
SF320,
SF512,
SF640,
UU_SF_NA
subframe
MOD DRX
LST DRX
subframes),
PSF80(80
subframes),
PSF100(100
subframes),
PSF200(200
subframes),
PSF300(300
subframes),
PSF500(500
subframes),
PSF750(750
subframes),
PSF1280(128
0 subframes),
PSF1920(192
0 subframes),
PSF2560(256
0 subframes)
DRX
ShortDrxCyc
leSpecial
Issue 01 (2010-07-30)
UU_SF_NA(
N/A)
SF2(2
subframes),
SF5(5
subframes),
SF8(8
subframes),
SF10(10
subframes),
SF16(16
subframes),
SF20(20
subframes),
SF32(32
subframes),
SF40(40
subframes),
SF64(64
subframes),
SF80(80
subframes),
SF128(128
subframes),
SF160(160
subframes),
SF256(256
subframes),
SF320(320
subframes),
SF512(512
subframes),
SF640(640
subframes),

5-5
eRAN
DRX
5 Parameters
MO
Parameter
ID
Default
Value
GUI Value
Range
Actual
Value
Range
Unit
MML
Command
UU_SF_NA(
N/A)
DRX
DrxShortCyc
leTimerSpeci
al
1~16
1~16
None
MOD DRX
LST DRX
DRXTimer
FddTddType
None
FDD(FDD
Mode),
TDD_Config
uration_0(TD
D
Congfigurati
on 0),
TDD_Config
uration_1(TD
D
Congfigurati
on 1),
TDD_Config
uration_2(TD
D
Congfigurati
on 2),
TDD_Config
uration_3(TD
D
Congfigurati
on 3),
TDD_Config
uration_4(TD
D
Congfigurati
on 4),
TDD_Config
uration_5(TD
D
Congfigurati
on 5),
TDD_Config
uration_6(TD
D
Congfigurati
on 6)
FDD,
TDD_Config
uration_0,
TDD_Config
uration_1,
TDD_Config
uration_2,
TDD_Config
uration_3,
TDD_Config
uration_4,
TDD_Config
uration_5,
TDD_Config
uration_6
None
MOD
DRXTIMER
LST
DRXTIMER
DRXTimer
Qci
None
QCI1(QCI
1),
QCI2(QCI
2),
QCI3(QCI
3),
QCI4(QCI
QCI1, QCI2,
QCI3, QCI4,
QCI5, QCI6,
QCI7, QCI8,
QCI9
None
MOD
DRXTIMER
LST
DRXTIMER
5-6

Issue 01 (2010-07-30)
eRAN
DRX
MO
5 Parameters
Parameter
ID
Default
Value
GUI Value
Range
Actual
Value
Range
Unit
MML
Command
4),
QCI5(QCI
5),
QCI6(QCI
6),
QCI7(QCI
7),
QCI8(QCI
8),
QCI9(QCI 9)
DRXTimer
OnDurationT
imer
None
PSF1(1
subframes),
PSF2(2
subframes),
PSF3(3
subframes),
PSF4(4
subframes),
PSF5(5
subframes),
PSF6(6
subframes),
PSF8(8
subframes),
PSF10(10
subframes),
PSF20(20
subframes),
PSF30(30
subframes),
PSF40(40
subframes),
PSF50(50
subframes),
PSF60(60
subframes),
PSF80(80
subframes),
PSF100(100
subframes),
PSF200(200
subframes)
PSF1, PSF2,
PSF3, PSF4,
PSF5, PSF6,
PSF8,
PSF10,
PSF20,
PSF30,
PSF40,
PSF50,
PSF60,
PSF80,
PSF100,
PSF200
subframe
MOD
DRXTIMER
LST
DRXTIMER
DRXTimer
DrxInactivity
Timer
None
PSF1(1
subframes),
PSF2(2
subframes),
PSF3(3
subframes),
PSF4(4
subframes),
PSF1, PSF2,
PSF3, PSF4,
PSF5, PSF6,
PSF8,
PSF10,
PSF20,
PSF30,
PSF40,
subframe
MOD
DRXTIMER
LST
DRXTIMER
Issue 01 (2010-07-30)

5-7
eRAN
DRX
5 Parameters
MO
DRXParaPer
QCI
5-8
Parameter
ID
DrxReTxTim
er
Default
Value
None
GUI Value
Range
Actual
Value
Range
PSF5(5
subframes),
PSF6(6
subframes),
PSF8(8
subframes),
PSF10(10
subframes),
PSF20(20
subframes),
PSF30(30
subframes),
PSF40(40
subframes),
PSF50(50
subframes),
PSF60(60
subframes),
PSF80(80
subframes),
PSF100(100
subframes),
PSF200(200
subframes),
PSF300(300
subframes),
PSF500(500
subframes),
PSF750(750
subframes),
PSF1280(128
0 subframes),
PSF1920(192
0 subframes),
PSF2560(256
0 subframes)
PSF50,
PSF60,
PSF80,
PSF100,
PSF200,
PSF300,
PSF500,
PSF750,
PSF1280,
PSF1920,
PSF2560
sf1(1
subframe),
sf2(2
subframes),
sf4(4
subframes),
sf6(6
subframes),
sf8(8
subframes),
sf16(16
subframes),
sf24(24
subframes),
sf33(33
sf1, sf2, sf4,

sf6, sf8, sf16,
sf24, sf33

Unit
MML
Command
subframe
MOD
DRXPARAP
ERQCI
LST
DRXPARAP
ERQCI
Issue 01 (2010-07-30)
eRAN
DRX
MO
5 Parameters
Parameter
ID
Default
Value
GUI Value
Range
Actual
Value
Range
Unit
MML
Command
subframes)
DRXParaPer
QCI
DrxShortCyc
leTimer
None
1~16
1~16
None
MOD
DRXPARAP
ERQCI
LST
DRXPARAP
ERQCI
DRXParaPer
QCI
EnterDrxSwi
tch
None
OFF(Off),
ON(On)
OFF, ON
None
MOD
DRXPARAP
ERQCI
LST
DRXPARAP
ERQCI
DRXParaPer
QCI
LongDrxCyc
le
None
SF10(10
subframes),
SF20(20
subframes),
SF32(32
subframes),
SF40(40
subframes),
SF64(64
subframes),
SF80(80
subframes),
SF128(128
subframes),
SF160(160
subframes),
SF256(256
subframes),
SF320(320
subframes),
SF512(512
subframes),
SF640(640
subframes),
SF1024(1024
subframes),
SF1280(1280
subframes),
SF2048(2048
subframes),
SF2560(2560
subframes)
SF10, SF20,
SF32, SF40,
SF64, SF80,
SF128,
SF160,
SF256,
SF320,
SF512,
SF640,
SF1024,
SF1280,
SF2048,
SF2560
subframe
MOD
DRXPARAP
ERQCI
LST
DRXPARAP
ERQCI
DRXParaPer
QCI
ShortDrxCyc
le
None
SF2(2
subframes),
SF2, SF5,
SF8, SF10,
subframe
MOD
DRXPARAP
Issue 01 (2010-07-30)

5-9
eRAN
DRX
5 Parameters
MO
5-10
Parameter
ID
Default
Value
GUI Value
Range
Actual
Value
Range
SF5(5
subframes),
SF8(8
subframes),
SF10(10
subframes),
SF16(16
subframes),
SF20(20
subframes),
SF32(32
subframes),
SF40(40
subframes),
SF64(64
subframes),
SF80(80
subframes),
SF128(128
subframes),
SF160(160
subframes),
SF256(256
subframes),
SF320(320
subframes),
SF512(512
subframes),
SF640(640
subframes),
UU_SF_NA(
N/A)
SF16, SF20,
SF32, SF40,
SF64, SF80,
SF128,
SF160,
SF256,
SF320,
SF512,
SF640,
UU_SF_NA

Unit
MML
Command
ERQCI
LST
DRXPARAP
ERQCI
Issue 01 (2010-07-30)
eRAN
DRX
6 Counters
Counters
For details about the counters related to DRX, see the eNodeB Performance Counter
Reference.
Issue 01 (2010-07-30)

6-1
eRAN
DRX
7 Glossary
Glossary
7.1 Terms
M2000
iManager M2000 (M2000 for short). The M2000 is a unified

platform that manages Huawei mobile network elements in a
centralized way,
7.2 Acronyms and Abbreviations

CQI
Channel Quality Indicator
DRX
Discontinuous Reception
GBR
Guaranteed Bit Rate
LMT
Local Maintenance Terminal
MCE
MAC Control Element
M2000
iManager M2000
PDB
Packet Delay Budget
PDCCH
Physical Downlink Control Channel
PELR
Packet Error Loss Rate
PSF
PDCCH Sub Frame
QCI
QoS Class Identifier
RACH
Random Access Channel
RFSP
Subscriber Profile ID for RAT/Frequency Priority
SR
Schedule Request
SRS
Sounding Reference Signal
Issue 01 (2010-07-30)

7-1
eRAN
DRX
8 Reference Documents
Reference Documents
This chapter lists the reference documents related to DRX in connected mode:
[1] 3GPP TS 36.321, "Medium Access Control (MAC) protocol specification"
[2] 3GPP TS 36.300, "Overall description"
[3] 3GPP TS 36.211, "Physical channels and modulation"
[4] Idle Mode Management Feature Parameter Description
[5] Mobility Management in Connected Mode Feature Parameter Description
[6] eNodeB MO Reference
[7] eNodeB Performance Counter Reference
Issue 01 (2010-07-30)

8-1

DRX Feature Parameter Description (ERAN2.0 - 01)

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

DRX Feature Parameter Description (ERAN2.0 - 01)

Caricato da

Copyright:

Formati disponibili

eRAN

Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd. 2010. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

2 Overview of DRX .......................................................................................................................2-1

3 DRX Technology ........................................................................................................................3-1

Huawei Proprietary and Confidential

8 Reference Documents ...............................................................................................................8-1

Huawei Proprietary and Confidential

1.2 Intended Audience

Personnel who need to understand DRX

Personnel who work with Huawei products

1.3 Change History

Huawei Proprietary and Confidential

Section 4.2 "Setting the Cell Duplex

Descriptions in section 3.2.1

Feature IDs are added.

The description about the RFSP is

The following parameters are

For details, see chapter 4

Huawei Proprietary and Confidential

DRX is a mandatory feature for all UEs of the LTE standard.

Huawei Proprietary and Confidential

2.3 Dependencies on Other Features

2.4 Typical Application

Periodical and consecutive packet services, such as Voice over IP (VoIP).

Services that generate small packets, such as the Presence service.

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Difference between Active Time and On Duration:

3.2 Key Technologies

Huawei Proprietary and Confidential

Entering the DRX Mode

The DRXAlgSwitch parameter is set to ON.

All services of the UE support DRX.

Table 3-1 Standardized QCI characteristics

Video (Buffered streaming)

Video (Buffered streaming)

Huawei Proprietary and Confidential

PDB: Packet Delay Budget

GBR: Guaranteed Bit Rate

PELR: Packet Error Loss Rate

The data volume of the UE is extremely low.

The moving speed of the UE is medium or low.

Quitting the DRX Mode

A service on the UE does not support DRX.

The data volume of the UE is relatively high.

The DRX cycle of the UE is longer than the CQI cycle.

The moving speed of the UE is high.

3.2.2 Starting the DRX Cycle

When the long DRX cycle is configured

When the short DRX cycle is configured

SFN: System Frame Number

SSFN: System Subframe Number

Huawei Proprietary and Confidential

The time when a Scheduling Request is pending.

Table 3-2 Definition of DRX timers

The periodical starting of this timer

This timer is started at the starting

Huawei Proprietary and Confidential