ue state handling gc

8/10/2019 Ue State Handling Gc

http://slidepdf.com/reader/full/ue-state-handling-gc 1/39

© Nokia Solutions and Networks 2014RA41214EN60GLA0

LTE Radio Parameters RL60UE State Handling



4 © Nokia Solutions and Networks 2014RA41214EN60GLA0

Module Objectives

• After completing this learning element, the participant should be able to

describe discuss and analyze:

The different connection and activity states of an LTE UE in comparison toUMTS

Paging configuration parameters

State the possible configuration choices for DRX/DTX in idle mode as wellas in connected mode

Benefits of the operation of smart DRX

Operation of Multimedia priority service




Index

UE States

Purpose of DRX

DRX in Idle ModeMultimedia priority services

DRX in Connected Mode

Smart DRX




States in UTRAN, GERAN, E-UTRA

The following transitions are supported:Supported from RL30 1)

E-UTRARRC_CONNECTEDCELL_DCH

CELL_FACH

CELL_PCHURA_PCH

UTRA_IDLE E-UTRARRC_IDLE

GSM_Connected

GSM_IdleGPRS_Packet_Idle

GPRS_Packet_Transfer

Handover

Reselection

Reselection

Connection Establishment/Connection Release

Supported from RL10/RU20 2)


Handover

CCO

with optional NACC

Supported from RL30 3)

ReselectionSupported from RL10/RG20 4)

CCO

CCO, Reselection


Supported from RL10

LTE




Attach accept

Detach

Attach rejectTAU Reject All Bearer Deactivated

EMM-DEREGISTERED EMM-REGISTERED

EMM states in UE

Attach acceptTAU Accept

Detach

Attach rejectTAU Reject All Bearer Deactivated

EMM-DEREGISTERED EMM-REGISTERED

EMM states in MME

Mobility Management StatesDefinition of main EPS Mobility Management states

• EMM-DEREGISTERED

o

The UE is not reachable by a MME.o UE context can still be stored in the UE and MME

• EMM-REGISTERED

– UE enters to EMM-Registered with Attach or Tracking Area Update procedure

– The UE location is known with accuracy of the tracking area list

– UE has at least one active PDN connection

– After detach procedure the state is changed to EMM-DEREGISTERED




RRC Established

RRC Released

ECM-IDLE ECM-CONNECTED

ECM states in UE

S1 Established

S1 Released

ECM-IDLE ECM-CONNECTED

ECM states in MME

Connection Management States

Definition of EPS Connection Management states

• ECM-IDLE

o No NAS signaling connection between UE and network exists.

o In the EMM-REGISTERED and ECM-IDLE state, the UE shall perform TAU, PeriodicTAU, Service Request, Answer to paging form MME with Service UE and MME enterthe ECM-CONNECTED state when signaling connection is established.

• ECM-CONNECTED

o UE location is known in the MME with an accuracy of a serving eNodeB.o There exists a signaling connection between the UE and the MME.

o The S1 release procedure changes the state at both UE and MME from ECM-CONNECTED to ECM-IDLE.




Index

UE States

Purpose of DRXDRX in Idle Mode

Multimedia priority services


Smart DRX




Normal eNB Initiated Transition to ECM-IDLE (e.g. due to user inactivity)

eNBUE MME S-GW

S1AP: UE Context Release Command

S1AP: UE Context Release CompleteRRC: RRC Connection Release

Release all UE relatedresources,

remove UE context

Set UE to

RRC-IDLE

Set UE to

ECM-IDLE

Detect user inactivityor other eNB trigger

S1AP: UE Context Release Request

S11 interaction to inform S-GWabout connection release

UE inRRC-CONNECTED

L2 ACK

Main impact – > UE- consumes less battery power in idle mode and there are less active UEs whichnetwork have to handle.

Fast going to inactivity has drawback of longer connection setup time (transition idle<->connected)

inactivityTimerInactivity for UL & DLLNCEL; 10..65535s; 1s ; 30s




DTX/DRX Discontinuous Transmission/ Reception

• DRX/DTX means UE transceiver is switched off for some predefined timeperiods. This save power consumption on one side but might consequences inlonger call setup time and/or lower user throughput achievable.

• What are DRX/DTX options ?

• In Idle mode for Paging – this option means UE is listening paging messagesin predefined time opportunities only and sleeping all other time. Supportedfrom RL10 .

• DRX/DTX in connected mode – UE is switched off for predefined timeinterval. Supported from RL30 .




Index

UE States




Smart DRX




Discontinuous Reception for Paging (TS 36.304)

The UE may use DRX in idle mode in order to reduce power consumption

One Paging Occasion (PO) is a subframe where there may be P-RNTI transmitted onPDCCH addressing the paging message One Paging Frame (PF) is one Radio Frame, which may contain one or multiple PagingOccasion(s)

When DRX is used the UE needs only to monitor one PO per DRX cycle

defPagCyccell specific paging DRX cycle duration . Italso determines the maximum pagingDRX duration applicable in the cell.Referred as “T” in 36.304 LNCEL; 32rf(0), 64rf(1), 128rf(2), 256rf(3);128rf(2)1rf = 1 radio frame = 10ms

pagingNbdefines the number of possible Paging Occasions perradio frame , i.e. the density of paging occasions. Thisparameter is used to calculate the number of pagingoccasions within one paging DRX duration, which inturn is used to calculate the paging occasion LNCEL; oneT(2), halfT(3), quarterT(4), oneEighthT(5),oneSixteenthT(6), oneThirtySecondT(7); quarterT(4 )

Example: quarterT = 1/4*T =1 Paging Occasion PO in every 4th radio frame ( 40 ms )

32 PO’s / DRX cycle duration ( 128 rf )




Occasion of Paging Messages

• The cell specific DRX cycle length Tsib is broadcasted by System Information ( PCCH-

Config parameterdefaul tPagingCycle

(in number of radio frames)• The UE specific DRX cycle length Tue might be received from core network from

S1AP Paging Message as Optional IE .

• The used paging DRX Cycle T (in number of radio frames) is set to : T=MIN(Tue,Tsib) .(Referred to as ' T ' in 3GPP TS 36.304)

• The relationship “paging occasions - radio frame” is given by the parameter pagingNbprovided in System Information ( PCCH-Config parameter pagingNb). nB shall beinterpreted as a calculation formula (how to derive paging occasions from T). For betterunderstanding, the result of the calculation formula nB will be written as nB(T) in thissection.Example: quarterT denotes nB(T)= 1/4*T (there is 1 paging occasion in every 4th radioframe).




Example (as per UE Behavior, simplified, note the Tue is smaller than allowedby 3GPP):

Assumptions:Cell paging DRX Tsib = 32(frames),nB(T)=halfT,UE paging DRX Tue = 8 (frames)

Calculation:T = MIN(Tue,Tsib) = MIN(8,32) = 8 frames -> DRX cycle lengthnB(T) = half(8) = 4 -> paging occasions per DRX cycleN = MIN(T,nB(T)) = MIN(8,4) = 4 paging groupsNs = MAX(1, nB(T)/T) = MAX(1, 4 / 8) = MAX(1,0)= 1 subframe used for pagingUE_ID = 3, assumption for this example (it could be any number)T div N = 8 div 4 = 2 -> distance between 2 radio frames with paging occasionsUE_ID mod N = 3 mod 4 = 3 -> relative index of a frame with PO inside DRX(T div N)*(UE_ID mod 4) = 2*3 = 6 -> relative position of the PO inside DRXLet next reachable be SFN = 501; therefore (SFN mod T) = 5; therefore SFN for paging is 501+(6-5)=502.

Simplified case (*to be shown in the picture) as the Tue is smaller than allowed by 3GPP.

SFN

T div N

T (Paging DRX)PagingOccasionPO

[SFN=x*T] [SFN=(x+1)*T]

(T div N)*(UE_ID mod N)




Index

UE States




Smart DRX




Multimedia Priority Services

LTE1074 supports MPS by :

– Paging prioritization

paging resources are assigned according to the IE: Paging Prio ri ty provided within S1-AP: PAGING

as a result higher reachability of paging resources is assured for highpriority users in case of paging congestion

– Recognition and handling of high-priority RRC connections and E-RABs setup

RRC connection requests and E-RABs with a high-priority arerecognized and prioritized in a way similar to IMS Emergency Sessions

• Admission Control thresholds , which are used for IMSEmergency Sessions, are applied to high priority sessions

– Emergency callback

for normal priority UEs -called by High Priority UE

• if a RRC Connection Request is caused by a S1AP: PAGINGmessage which contains a IE: Paging Priority , it is handled like arequest with establishmentCause set to “Emergency”

Multimedia Priority Services ( MPS) allows authorized users to obtain and maintain radio and networkresources with priority, even during congestion.





To use Multimedia Priority Services, the UE must have a MPS subscription *

– MPS subscription is defined by a USIM with special Access Class or Classes – each UE is a member of a one out of ten randomly allocated mobile populations, defined as Access Classes (AC) 0

to 9, which are stored on the USIM

• Apart from AC 0 to 9, the UE may also be a member of one or more out of 5 special categories (AC 11 to 15)

– Access Classes from 11 to 15 are allocated to a specific High Priority Users as follows

MPS from UE perspective

Access Class Use

Standard class

0-9 assigned randomly for every UE

Special classes

11 For PLMN use

12 Security Services

13 Public Utilities (e.g. water/gassuppliers)

14 Emergency Services

15 PLMN Staff

Access Classes for High Priority UsersNote that AC number is not a priority.





Handling of high priority paging with LTE1074:

– upon activation of MPS feature(actHighPrioServices = true ), eNB takesinto account IE: Paging Priority providedwithin S1AP: Paging

– if more than 16 Paging Records (maxcapacity of one RRC Paging Message ) areaddressed to one Paging Occasion,excess Paging is discarded according tothe Paging Priority

note that if no Paging Priority isprovided to a Paging Record then itis treated with the lowest priority

– as a result of prioritization, paging relatedto High Priority UEs is sent when thereis Paging congestion

Paging prioritization:

High priority paging

High priority paging is sent at the cost of lower priority Paging Records.





Support of Multimedia Priority Services is also introducedin the Admission Control (AC) mechanism

– special treatment of high priority users, starting from RRCConnection establishment up to DRB setup, is introduced

• Request for Multimedia Priority Service is indicated byestablishmentCause set to highPriorityAccess within RRCConnection Request message

– upon reception of a request with this establishment cause, eNBmaps the cause highPriorityAccess temporarily to emergency

– then RRC Connection Request is admitted based onEmergency thresholds → maxNumRrcEmergency

dedicated thresholds for Emergency sessions wereintroduced with LTE572 IMS Emergency Session featurewhich is prerequisite for LTE1074

– as maxNumRrcEmergency must be configured to value higherthan maxNumRrc + max( addAUeRrHo , addAUeTcHo ), highpriority sessions have more chances to be established thannormal traffic

High Priority Access (1/3): RRC Connection

Initial Context Setup Request

RRC Connection Request

NAS: Service Request

RRC Connection Setup

RRC Connection Setup Complete Initial UE MessageNAS: Service Request

Random Access Procedure

Radio Admission Control – #RRC Connected UEs

Initial Context Setup Response

Radio Admission Control – #Active UEs + #DRBs

NAS Security Establishment

NAS: Activate default EPS bearercontext request

NAS: Activate default EPSbearer success

eNB MME

establishmentCause = highPriorityAccess


RRC Connection Reconfiguration

RRC Connection ReconfigurationComplete

NAS: Activate default EPSbearer context request





Once the RRC Connection is established, eNB initiates S1connection for the UE with cause highPriorityAccess

– the information is provided by IE: RRC EstablishmentCause within S1-AP Initial UE Message

• Upon reception of Initial Context Setup Request, eNBperforms AC for the number of Active UEs* and theirDRBs

– both Admission Control criteria need to be fulfilled inparallel , therefore similar to RRC Connection, eNBcan handle (depending on ARP) highPriorityAccess connection as emergency

– in case of congestion when threshold for connectedUEs is reached, UE with High Priority Services isadmitted thanks to the emergency threshold i.e.addEmergencySessions

this threshold is added to the maxNumActUE which is defined for „normal‟ UEs in parallel also Default Bearer of the UE must beadmitted → see next slide for more details

High Priority Access (2/3): Initial Context setup

Initial Context Setup Request

NAS: Service Request


RRC Connection Setup Complete Initial UE MessageNAS: Service Request

Random Access Procedure

Initial Context Setup Response

Radio Admission Control – #Active UEs + #DRBs

NAS Security Establishment

NAS: Activate default EPS bearercontext request


eNB MME


RRC Connection Reconfiguration

RRC Connection ReconfigurationComplete

NAS: Activate default EPSbearer context request


Radio Admission Control – #RRC Connected UEs

establishmentCause = highPriorityAccess





To assure that Default Bearers of high pr ior i ty users are admitted, ARP priority ramp-up may be performed

– the bearer can be admitted even during the congestion, i.e. Pre-emption

• Decision to increase the ARP priority depends on the actual ARP value of the bearer in question and an ARP rangedefined for high priority sessions

– hpsSessionConfig structure defines the ARP range which is considered as a high priority in the following way:

if ARP of a bearer is within the high priority ARP range then it is kept and used for Admission Controlotherwise the ARP is temporarily set to Emergency ARP ( emerSessArpPrioLev , default = 1) and used for AC

• note that priority increase is done only internally (within the eNB) and E-RAB Modification procedure is notperformed

High Priority Access (3/3): DRB setup

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

ARP priority

hpsSessArpMax ≥ high priority ARP ≥ hpsSessArpMin

Example:• emerSessArpPrioLev = 1• hpsSessArpMax = 2

• hpsSessArpMin = 5

If bearer ARP is within range from 2 to 5 then itis kept and used for Admission Control

If bearer ARP is not within the range of high priority ARP, then it ismapped to Emergency ARP → in this scenario to ARP =1





Correlation of high priority paging with corresponding RRCConnection Request

– introduced to handle the scenario in which a „normal‟ user iscalled by a „high priority‟ user

special treatment of the „normal‟ user is needed to ensure thatthe connection with the „high priority‟ user will be established

• Operation

– paging for the „normal‟ UE must be sent with high priority toeNB and it must carry S-TMSI in IE: UE Paging Identi ty

– upon reception of S1-AP Paging, eNB stores S-TMSI of UE fortPageCorrInt time (default 3000ms)

– user is treated as high priority (no MPS subscription) if :

RRC Connection Setup Request arrives at eNB beforetPageCorrInt expirationIE: ue-Identity carries a S-TMSI which matches the onestored at the eNB

– else, UE is treated as normal priority

Emergency callback support

eNB MME

S1-AP: Paging

RRC: Paging

RA Procedure



RRC Connection SetupComplete

tPageCorrInt

Paging Priority, S-TMSI

ue-Identity: S-TMSI

S1-AP: Initial UE Message




LTE1074 – Multimedia Priority Services

MO Name Description

LNBTS actHighPrioServices Activate high priority services 0 (false), 1 (true)gui => internalfalse => 0true => 1Default - False

LNBTS hpsSessConfig High-priority session configurations Priority level range to be regardedas high-prioritySFS value range: {1,2, ..., 15)

LNBTS hpsSessArpMax High-priority session ARP prioritylevel maximum

High-priority session ARP prioritylevel maximumSFS value range: {1,2, ..., 15}Default 1

LNBTS hpsSessArpMin High-priority session ARP prioritylevel minimum

High-priority session ARP prioritylevel minimumSFS value range: {1,2, ..., 15}Default 1

LNCEL tPageCorrInt Timer paging correlation interval The timer determines themaximum time between the S1paging and its correlated RRCconnection setup request.SFS value range: 0...10000, step100 Default 3000

Configuration Management




Index

UE StatesPurpose of DRXDRX in Idle ModeMultimedia priority services

DRX in Connected ModeSmart DRX




DRX in RRC Connected ModeOverview

Target: maximize UE battery lifetime by discontinuous monitoring of DL control channel(PDCCH)

UE will be kept time aligned* DRX cycle is limited to 80msSupport of 3GPP defined long DRX cycle (short DRX cycle not supported)

3 different profiles supported:

1. DRX off

2. Voice optimized &

3. Non-GBRThe DRX profiles can be mapped flexibly to different QCI profiles

DRX profile of bearer with highest priority is applied in case of multiple bearers per UE

DRX settings are signaled to UE via RRC messages

DRX settings are applied only to UEs indicating related DRX capabilities

Device type indication ( non power limited devices do not benefit from DRX) provided by UEaccording to 3GPP Rel. 9 can be configured

actDrxactivates the DRX in the cell.LNCEL; true(1),false(0);false(0)

drxApplyDeviceTypeDetermines whether the device type“noBenFromBatConsumpOpt” shall beconsidered for DRX configurationLNCEL; true(1),false(0); true(1)

*Time alignment of the UL transmission isachieved by applying a timing advance at theUE transmitter relative to the received DL timing




DRX in RRC Connected ModeDRX Status

• DRX status could be:

– DRX disabled : – UE always monitors PDCCH for UL and DL grants

– DRX enabled : – Timeline is divided in DRX cycles of equal number of sub-frames – Start of DRX cycle is linked to SFN + offset (see backup slides)

– Within a DRX cycle there are periods the UE is „ DRX Active ‟ and periods the UE is„DRX Sleep ‟ – DRX Sleep

– CQI / SRS / PMI / RI shall not be reported – DRX Active

– UE monitors PDCCH for UL and DL grants

– UE is DRX active according to 3GPP TS36.321: – The On Duration Timer or the DRX Inactivity Timer or a DRX Retransmission Timer or the Contention

Resolution Timer is running ( see next slides ) – A Scheduling Request sent on PUCCH is pending – An UL grant for a pending HARQ retransmission can occur – A PDCCH (allocation) indicating a new transmission addressed to the C-RNTI of the UE has not been

received after successful reception of a Random Access Response for the signaled preamble

drxLongCycleDRX cycle (note that only long

DRX cycle supported)LNCEL; 20ms, 40ms, 80ms;depends on DRX profile

SFN = System Frame NumberSRS = Sounding Reference SignalPMI = Precoding Matrix IndicatorRI = Rank Indicator




DRX in RRC Connected ModeDRX Timers (1/3)

• On duration timer :

• Specifies the number of consecutive TTIs during which the UE shall monitor the PDCCHfor possible allocations

• One per UE according to DRX profile

• Will always be started with the first subframe of a DRX cycle

• If running UE is DRX active

- Shall be set to a value that allows eNB to schedule a UE within the On Duration periodwith high probability if there are data to be transmitted

drxOnDuratTDRX on duration timerLNCEL;1, 2, 3, 4, 5, 6, 8,10ms ;depends on DRX profile




DRX in RRC Connected ModeDRX Timers (2/3)DRX Inactivity timer:

• Specifies the number of consecutive TTIs during which the UE shall monitor PDCCH

after successfully decoding a PDCCH indicating an initial UL or DL user datatransmission for this UE

• Will be started or restarted if the PDCCH indicated a new UL or DL transmission and ifthe UE is DRX Active at that time

• If running UE is DRX active

- For bursty traffic the scheduler can keep the UE awake by scheduling it in a specifictime window (with continuously grants to UE, DRX Inactivity Timer Window will bemoved beyond the end of the DRX cycle)

drxInactivityTDRX inactivity timerLNCEL;1, 2, 3, 4, 5, 6, 8,10, 20,30, 40, 50, 60, 80ms ; dependson DRX profile

DRX On Duration

DRX Inactivity Timer


(1) DL grant on PDCCH+ DL data on PDSCH


Started at (1)

Re -Started at (2) Note: If no further grants to UE during DRX Activetime frame then the DRX Inactivity Timer willexceed and UE stops being DRX Active (notlistening to PDCCH any more)




DRX in RRC Connected ModeDRX Timers (3/3)DRX Retransmission Timer:

• Specifies the maximum number of consecutive PDCCH sub-frames for possible allocations

as soon as a DL retransmission is expected by the UE- Started after HARQ Timer* expires and DL data were not decoded successfully

- Purpose: Span a window within which the UE listens on PDCCH for a retransmission inDL

- If running, UE is DRX active

- Stopped when PDCCH indicates a DL transmission and UE is DRX active at that time

- As UE is DRX Active when DRX Retransmission timer is running, eNB could schedule UEin DL or UL for new transmissions

DRX Retrans. Timer


Will be stopped at (3)

(2) NACK(3) Retransmission of(1)

drxRetransTDRX retransmission timer

LNCEL;2, 4, 6, 8ms ; dependson DRX profile

*HARQ timer is one per HARQ process. Define the sub-frame when nextpossible retransmission could be started earliest




DRX in RRC Connected ModeExample of UL Transmission


DRX On Duration

(1) UL grant on PDCCH

(2) UL

transmission onPUSCH

(3) NACK on PHICH +

UL grant for adaptiveretransmission onPDCCH

In case that thetransmission in (4)also failed, this sub-frame would be thenext slot for giving anUL grant for aretransmission.Hence, this sub-framebelongs to the DRX

Active time too . (4) ULretransmissionon PUSCH

Transmission in UL ispossible while UE is

DRX Sleep

• UE has to monitor PDCCH in this sub-frame as an UL grantfor a retransmission can occur, even if DRX OnDurationand DRX Inactivity timer expired

• DRX Inactivity timer will not be started in this sub-frame asthis UL grant doesn‟t indicate a new transmission




DRX in RRC Connected ModeDRX Profile Modeling

The DRX profiles can be mapped flexibly to different QCI profiles

• qciTab is enhanced by an index to DRX profiles• For each DRX profile index a DRX profile is provided

drxProfileIndex drxProfilePriority Further DRX parameters1 45 None (DRX is off)

2 40 <voice profile>3 30 <non-GBR [80ms] profile>

QCI Table DRX Profiles

drxProfileIndexPointer to the correspondingDRX profileLNBTS: 1, 2, 3;depends on QCI (see table)

drxProfileIndexDRX profile index. Uniquelyidentify a DRX profileLNCEL: 1,2,3;depends on drxProfileIndex

(see table)

drxProfilePriorityDRX profile priority. Applied toidentify the DRX profile to be used ifUE has multiple bearers establishedLNCEL: 0..50; 1;depends on QCI (see table)

QCI drxProfileIndex 1 {1,2}, default 2

2 {1,2,3}, default 2 3 {1,2,3}, default 2 4 {1,2,3}, default 2 5 {1,2,3,4,5}, default 3 6 {1,3,4,5}, default 3 7 {1,3,4,5}, default 3 8 {1,3,4,5}, default 3 9 {1,3,4,5}, default 3

d d S i




Extended DRX SettingsOverview

Extended setting for DRX in connected mode

2 additional DRX profiles with longer setting for the DRX cycle:

drxProfile4

Non-GBR: intermediate DRX

Useful for e.g. QCI 5 IMS related traffic

drxProfile5

Non-GBR: Long DRX

Useful for UE with bursty traffic, e.g. web browsing

UL out-of-sync handling:

By using a very long setting for DRX cycle the UE is going out-of-sync (the time alignment is stopped sometime after the UE has finished the data transmission)

In out-of-sync UE releases dedicated resources on PUCCH

The transition back to UL in-sync is done via Random Access procedure

The choice to which UEs to apply the extended DRX setting could be set with applyOutOfSyncStateparameter

UEs with established GBR bearers are always kept UL in-Sync

applyOutOfSyncStateDefine which UEs should be sent in out ofsync stateLNCEL : extendedDrxOnly(0), allDrx(1),allUEs(2); extendedDrxOnly(0) (i.e. OnlyUEs configured with extended settings forthe long DRX cycle )




DRX in Connected Mode: Parameters overview

DRX Profiles – Summary

drxInactivityT[ms]

drxLongCycle[ms]

drxOnDuratT[ms]

drxProfilePriority drxRetransT[ms]

drxProfile1 DRX disabled 0..50, step 1; 45 DRX disabled

drxProfile2 1,2,3, 4,5,6,8 20, 40 1,2,3,4,5, 6,8,10

0..50, step 1; 40 2, 4,6,8

drxProfile3 10 ,20,30,40,50,60,80

40, 80 1,2,3,4,5, 6,8,10

0..50, step 1; 30 2, 4,6,8

drxProfile4 200,300, 500 ,750,1280,1920, 2560

160, 320 10, 20 ,30,40,50,60,80,100

0..50, step 1; 20 4,6,8, 16 ,24,33

drxProfile5 750,1280,1920,2560

640,1280, 2560 10, 20 ,30,40,50,60,80,100,200

0..50, step 1; 10 4,6,8, 16 ,24,33

drxProfile2 drxProfile3non-GBR bearersthat allow for shortsettings of thelong DRX cycle

drxProfile4non-GBR bearersthat allow formedium settingsof the long DRXcycle (e.g. IMSsignaling)

Optimized forvoice calls

drxProfile5non-GBR bearersw/o specificlatencyrequirements (e.g.web browsing)

drxProfile1DRX OFF

drxInactivityT[ms]

drxLongCycle[ms]

drxOnDuratT[ms]



drxInactivityT[ms]

drxLongCycle[ms]

drxOnDuratT[ms]



drxProfile2 1,2,3, 4,5,6,8 20, 40 1,2,3,4,5, 6,8,10

0..50, step 1; 40 2, 4,6,8

drxInactivityT[ms]

drxLongCycle[ms]

drxOnDuratT[ms]



drxProfile2 1,2,3, 4,5,6,8 20, 40 1,2,3,4,5, 6,8,10

0..50, step 1; 40 2, 4,6,8

drxProfile3 10 ,20,30,40,50,60,80

40, 80 1,2,3,4,5, 6,8,10

0..50, step 1; 30 2, 4,6,8

drxInactivityT[ms]

drxLongCycle[ms]

drxOnDuratT[ms]



drxProfile2 1,2,3, 4,5,6,8 20, 40 1,2,3,4,5, 6,8,10

0..50, step 1; 40 2, 4,6,8

drxProfile3 10 ,20,30,40,50,60,80

40, 80 1,2,3,4,5, 6,8,10

0..50, step 1; 30 2, 4,6,8

drxProfile4 200,300, 500 ,750,1280,1920, 2560

160, 320 10, 20 ,30,40,50,60,80,100

0..50, step 1; 20 4,6,8, 16 ,24,33




Index

UE States

Purpose of DRX

DRX in Idle Mode



Smart DRX

S t DRX




Smart DRX

T ime A lignment T imer

UL-in-sync UL-out-of-sync

STIT = [1 up to 124] * Short DRX Cycle

Transmiss ion phase

UE monitorsPDCCH

RRC inactivity timer

Long DRX cycleDRX inactivity timer4

RRC Idle state

5

3…

RRC Connected state

Paging DRXcycle

3 3

DRX Act ive

DRX Sleep

PO Moni tor ing

RRC_IDLE

1 …

…

2

…

3

1

2

STIT – Short Term Inactivity Timer

1

… Short DRX cycle

3

2 2 2 2

DRX Short Cycle timer = [1 up to 16] * Short DRX cycle

Addi t ional DRX Sleep t ime w hen STIT is runn ing = h igh er ba t tery ga ins

UL

G

RANT

DL

G

RANT

DL

G

RANT

DL

G

RANT

UL

G

RANT

UL

G

RANT

Long DRX cycle: 160ms up to 2560msDRX Inactivity timer >= DRX Long cycle is no longer valid!

LTE585 - RL50




Smart DRX

time

DRX Inactivity TimerShort DRX Cycle = 20ms

Long DRX Cycle = 80ms

DRX Short Cycle timer

DRX Inactivity timer starts

DRX Short Cycle timer

DL grant + DL data sent

DRX On Duration from Short DRX Cycle

DRX On Duration from Long DRX Cycle

• When drxInactivityT expires start drxshortcyleT for the duration STIT• Timing is maintained (enough periodic CQIs sent).• Battery savings made during STIT time as UE now has sleep periods and no longer has to stay

drxactive to remain Time aligned.




drxInactivityT

[ms]

drxLongCycle

[ms]

drxShortCycl

e[ms]

drxShortC

ycleT

drxOnDuratT

[ms]

drxProfilePriority drxRetr

ansT[ms]

smartStInactFact

or

drxSmartProfile2

1,2,3, 4,5,6,8 20, 40 10, 20 ,40 1…16,step 1; 1

1,2,3,4,5, 6,8, 10

0..50, step 1;40

1,2, 4,6 2…124, step2; 124

drxSmartProfile3

10 ,20,30,40,50,60,80

40, 80 20, 40 1…16,step 1; 5

1,2,3,4,5, 6,8, 10

0..50, step 1;30

1,2, 4,6 2…124, step2; 6

drxSmartProfile4

1,2,3,4,5,6,8,10,20,30,40, 50,60,80,100,200,300,500,750,1280,1920,2560

160, 320 10,20,40, 80,160

1…16,step 1; 4

10 ,20,30,40,50,60,80,100

0..50, step 1;20

4,6,8, 16,24,33

2…124, step2; 4

drxSmartP

rofile5

1,2,3,4,5,6,8,

10,20,30,40, 50,60,80,100,200,300,500,750,1280,1920,2560

640,1280, 2

560

10,20,40, 8

0,160,320,640

1…16,

step 1;16

10 ,20,30,4

0,50,60,80,100,200

0..50, step 1;

10

4,6,8, 1

6,24,33

2…124, step

2; 32

DRX Smart Profiles – Summary

Smart DRX




LTE585 Smart DRXConfiguration Management

LNCEL

actSmartDrx Activate smart DRXdrxSmartProfile2,3,4,5 DRX Smart Profile 2,3,4,5

drxProfileIndex DRX Profile indexdrxProfilePriority DRX profile prioritydrxOnDuratT DRX on duration timerdrxInactivityT DRX inactivity timerdrxLongCycle DRX long cycledrxShortCycle DRX short cycledrxShortCycleT DRX short cycle timerdrxRetransT DRX retransmission timersmartStInactFactor Short term inactivity factor for smart DRX

ue state handling gc

Documents