Professional Documents
Culture Documents
FAJ1213011
•The DRX cycle begins with an On Duration time during which the UE
is awake, followed by a period with Opportunity for DRX. The UE is
asleep during Opportunity for DRX if no timer is forcing it to be awake,
see the figure below. There are two DRX states possible for a specific UE.
Either it is active (awake) or inactive (asleep). The active time is defined
as the time during which the UE monitors the PDCCH for a PDCCH-
subframe.
DRX Cycle
Long and short cycles
•Switching off the transceiver for some time has a negative impact
on latency so a two stage approach has been implemented
•When no data is received during the short cycle mode the device
implicitly enters the long DRX cycle which is much more power
efficient but further increases latency time (and an increase in
bearer drops)
At expiry of inactivityTimer:
At expiry of shortDRXCycleTimer
InactivityTimer
- enter shortDRXCycle
- enter longDRXCycle
- start shortDRXCycleTimer
Active
Sleep
shortDRXCycleTime shortDRXCycleTime
At data send/receive start inactivityTimer
Data
onDuration (marked by )
Start sfn for the onDuration is defined by drxStartOffset:
Short DRX Cycle: [(SFN * 10) + subframe number] modulo (shortDRX-Cycle) = (drxStartOffset) modulo (shortDRX-Cycle)
Long DRX Cycle: [(SFN * 10) + subframe number] modulo (longDRX-Cycle) = drxStartOffset
Long and short cycles
inactivity shortCycleTimer
onDuration
LongCycle (P2)
ShortCycle (P1)
LTE RADIO STATE MACHINE
RRC_CONNECTED
UE monitors PDCCH T1
DRX Inactivity Continuous/
Active
Short DRX
T2
Power consumption
shortCycleTimer
Activity
DRX cycle P1
RRC Inactivity Long DRX
T3
RRC_IDLE
RRC_IDLE DRX cycle P2
(ECM – IDLE)
DRX cycle P3 UE monitors paging channel
• Partial DRX support (FGI 5=1 and FGI 4=0, the UE supports
only long cycles)
Feature
Group
Indicator
Contents :-
1. Introduction- benefits
2. dependencies
3. Feature Operation
3.1 configurations
3.2 License Handling
4. parameters
5. miscellaneous
1.0 Introduction- benefits
Introduction- benefits
• This feature introduces QoS Class Identifier (QCI) dependent DRX settings
which are defined by the operator.
• Instead of a one for all setting, a set of DRX settings can be configured by the
operator, providing the best fit DRX settings depending on the services.
• Service Specific DRX feature includes an extended DRX profile table with 19
DRX profiles (drxProfileId 0 - drxProfileId 18) that can be configured by the
operator.
• When the table is updated through MOM (Managed Object Model), it takes
effect for e-NodeB after the first cell is unlocked.
• The number of sub frames SF32, SF64, SF128, SF256, SF512, SF1024 and SF2048
are not recommended values for longDrxCycle and longDrxCycleOnly
Sl-19 Sl-20
3.2 License Handling
• Efficient DRX/DTX for Connected UE and Service Specific DRX features are
optional features.
• Operator is able to configure extended DRX profiles table, map a DRX profile to
QCI and set DRX priority when both licenses are activated.
• Operator is able to configure only default DRX profile which is used for all QCI
when only Efficient DRX/DTX for Connected UE feature is activated.
The relative priority among the DRX profiles, i.e. if the bearer that is setup with this
QCI has a higher DRX priority than any of the existing bearers
Back
parameters
Affected Parameters:
Network Impact:
The Service Specific DRX feature has no network impact with respect to
coverage, capacity and mobility.
Affected Features:
Related Features:
KPIs:
Counters:
Events: