UE State Handling

RA41214EN50GLA0 1
UE State Handling

RA41214EN50GLA0 2
UE State Handling

RA41214EN50GLA0 4
UE State Handling

RA41214EN50GLA0 5
UE State Handling

CCO = Cell Change Order

NACC = Network Assisted Cell Change

1)

(RL30) LTE56: IRAT HO to WCDMA

(RL40) LTE736: CSFB to UTRAN
(RL40) LTE872: SRVCC to WCDMA

2)

(RL10) LTE762: Reselection

(RU20) RAN2067: Reselection

3)

(RL30) LTE442: NACC to GSM

4)

(RL10) LTE762: Reselection

(GR20) BSS21353: Reselection

RA41214EN50GLA0 6
UE State Handling

RA41214EN50GLA0 7
UE State Handling

RA41214EN50GLA0 8
UE State Handling

RA41214EN50GLA0 9
UE State Handling

RA41214EN50GLA0 10
UE State Handling

• When both schedulers indicate “inactivity” on DL as well as on UL (based on DRB

data availability) the UE inactivity detection algorithm indicates UE combined
activity state “inactivity” to UE State Handling (UE-SH). Following this indication
UE combined activity state is reset to “activity” again such that as soon as the
above conditions are met again another indication of UE “inactivity” to UE state
handling is performed.
• Schedulers are also indicating a UE being “active” again to UE inactivity detection
algorithm such that always the correct state of UL and DL activity is reflected in
DRX/DTX-ALG. Once of the transmission directions becoming “active” again is not
explicitly reported to UE state handling.
• The inactivity timer applied by the schedulers is O&M configurable inactivitytimer
• The effect of an UE inactivity indication to UE state handling is not reported back to
DRX-DTX-ALG. If the UE is removed from RRC_CONNECTED state this will be
visible via release of all RBs of a UE from RAC.

RA41214EN50GLA0 11
UE State Handling

RA41214EN50GLA0 12
UE State Handling

RA41214EN50GLA0 13
UE State Handling

RA41214EN50GLA0 14
UE State Handling

RA41214EN50GLA0 15
UE State Handling

RA41214EN50GLA0 16
UE State Handling

RA41214EN50GLA0 17
UE State Handling

RA41214EN50GLA0 18
UE State Handling

actDrx ：Parameter to activate or deactivate the DRX in RRC Connected state

feature in a cell.

DRX is not disabled for Release 9 UEs that do not benefit from battery consumption
optimization. DRX is disabled in this case if:
The parameter drxApplyDeviceType is set to True (This parameter determines
whether the device type noBenFromBatConsumpOpt of the UE is considered for
DRX configuration. Such an UE does not foresee to particularly benefit from NW-
based battery consumption optimization)
The UE capabilities for E-UTRA contain the device type noBenFromBatConsumpOpt

RA41214EN50GLA0 19
UE State Handling

DRX Cycle= DRX Active + DRX Sleep

DRX Active= OnDuration + Inactivity Timer

When a DRX cycle is configured, the Active Time includes the time while:
-onDurationTimer or drx-InactivityTimer or drx-RetransmissionTimer or mac-
ContentionResolutionTimer (as described in subclause 5.1.5) is running;
or
-a Scheduling Request sent on PUCCH is pending (as described in subclause
5.4.4);
or
- an uplink grant for a pending HARQ retransmission can occur and there is data in
the corresponding HARQ buffer; or
- a PDCCH 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
explicitly signaled preamble (as described in subclause 5.1.4).

RA41214EN50GLA0 20
UE State Handling

on-duration: duration in downlink subframes that the UE waits for, after waking up
from DRX, to receive PDCCHs. If the UE successfully decodes a PDCCH, the UE
stays awake and starts the inactivity timer;

Note: If UE hasn’t been scheduled in On Duration and the UE doesn’t get DRX Active
again later in this cycle (e.g. by sending a SR), there is no possibility to start the DRX
Inactivity timer for the rest of the DRX cycle! In this case no transmission will take
place in this DRX cycle.

RA41214EN50GLA0 21
UE State Handling

Starting of the DRX Inactivity Timer

DRX Inactivity Timer will be started if the PDCCH indicated a new UL or DL
transmission and if the UE is DRX Active at that time
Restarting of the DRX Inactivity Timer
DRX Inactivity Timer Window will be moved with every grant indicating a
new transmission in UL or DL. This can only happen when such a grant will
be received when UE is DRX active
Continuously grants to UE, DRX Inactivity Timer Window will be moved
beyond the end of the DRX cycle
–If no further grants to UE during DRX Active time frame
▪ The DRX Inactivity Timer will exceed and UE stops being DRX Active (not
listening to PDCCH any more)
▪ Cannot receive further grants, until it awakes again e.g. at the beginning
of the next DRX cycle when the On Duration Timer will be started.

The parameter provides a means for the network to keep a user “alive” when there is
a sudden need to largely schedule the UE. Hence the mechanism allows for large
power saving while facilitating high QoS for bursty traffic types. Setting is a trade-off
between scheduler freedom and power saving as UE is forced to continuous monitor
for PDCCH whenever scheduled

RA41214EN50GLA0 22
UE State Handling

when the UE fails to decode a transport block of one of HARQ active

processes, it assumes that the next retransmission will take place at
least after
DRX Retransmission timer, so it can go in power saving state without
the needs to listen to PDCCH.

Note that HARQ retransmissions are planned outside of the DRX cycle
to allow for a tighter DRX optimization without having to plan for the
worst case retransmission.
The DRX retransmission timer is defined so that the UE does not have
to wait for a full DRX cycle for an expected retransmission that has
been lost due to either ACK/NACK misinterpretation or PDCCH failed
detection

RA41214EN50GLA0 23
UE State Handling

RA41214EN50GLA0 24
UE State Handling

RA41214EN50GLA0 25
UE State Handling

Extended settings for the long DRX cycle require UL out-of-synch handling
UEs can’t be kept time aligned any more
TA estimation is based on periodic CQI reporting if there is no UL traffic;
For long DRX cycle settings and during phases of data transmission, UE has
to be kept in active time continuously, realized by restricting the DRX
Inactivity timer accordingly
If phase of data transmission ends, TA to UE is stopped, and UE goes UL
out-of-sync
UE releases dedicated resources on PUCCH and for SRS
Re-synchronization via RA procedure due to UL or DL data arrival and re-
configuration of dedicated resources must be supported.
Transition to uplink In-Sync
DL data transmission trigger
The eNodeB initiates a random access procedure for UEs which are in uplink Out-of-
Sync and have data for downlink transmission. The eNodeB provides in this case the
RACH parameters via the PDCCH order to the UE.
UL data transmission trigger
During the UL Out-of-Sync state, UE may start a contention based random access
procedure in order to transmit data on uplink
Following the transition to In-Sync, UEs are reconfigured with any resources
released during UL Out-of-Sync transition (resources on PUCCH and for SRS, if
applicable).

RA41214EN50GLA0 26
UE State Handling

Behavior depending on ‘short term inactivity detection’

As long as no short term inactivity has been detected
(short term inactivity timer has not been expired)
 UE needs to be kept time aligned
Note:
During DRX Active for UEs with extended settings of the long DRX
cycle
(with the extended settings of the long DRX cycle the DRX Inactivity
Timer has to be set accordingly as to ensure UE being DRX Active
until detection of short term inactivity in order to be able to keep UE
UL in-sync.)

Short term inactivity has been detected

eNB stops sending timing alignment command to UE
(although subsequent DRX On-Duration arrives and TAT has not expired ->
UE goes UL out-of-sync when TAT expires)
In case traffic resumes before TAT expires, UE will be DRX active at least
for a time period corresponding to DRX Inactivity Timer
If traffic resumes after TAT expires a RA procedure is required to recover UE
UL synchronization.

RA41214EN50GLA0 27
UE State Handling

RA41214EN50GLA0 28
UE State Handling

RA41214EN50GLA0 29
UE State Handling

RA41214EN50GLA0 30
UE State Handling

RA41214EN50GLA0 31
UE State Handling

Limitation coming from LTE473 (drxInactivityT >= drxLongCycle) is no longer valid

(UE does not need to be in DRX Active all the time when STIT is running), further
battery savings should be visible

Now thanks to higher periodicity of DRX On Duration during DRX Short Cycle Timer
is running it is possible to collect suitable number of pCQI samples to estimate TA
with required accuracy = UL-in-sync can be assured

Short DRX Cycle similarly to long DRX Cycle will be aligned with CQI Periodicity

Minimum amount of 12 periodic CQIs per second is still binding

RA41214EN50GLA0 32
UE State Handling

RA41214EN50GLA0 33
UE State Handling

RA41214EN50GLA0 34
UE State Handling

RA41214EN50GLA0 35