Call Drop Optimization: Last Updated: November, 2013

Call Drop Optimization
Last Updated: November, 2013

Version 1.1
Latest version of this module can be downloaded from:
https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D506699937
For internal use

Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
Content
• Introduction
- Reasons for Drop Call
This module is for Call drops after
• KPIs: setup phase only. Connection
- Important KPIs/Counters setup is discussed in
Call Setup Optimization Module
- Target values and NSN and Project References
• Optimization actions/analysis
- UE initiated Drop Call analysis: signalling flows and counter triggering
- eNodeB initiated Drop Call analysis: signalling flows and counter triggering
- Drop Call counter triggers
- Handover related Drop Call analysis
• Summary
- Possible Observations and recommendations
- Parameters involved
• Impact of different Features

• Project examples
• Links to further material
For internal use
2 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
Possible reasons for Call Drops
• UE Detected Radio Link Failures (RLF)

• T310 expiry
• Maximum number of RLC retransmissions
• Handover failure (T304 expiry)
• Non-HO related random access problem
• eNodeB Detected Radio Link Failures (RLF)
• PUSCH RLF
• CQI RLF
• Ack/Nack RLF
• PDCCH Order failure
• SRS RLF
• eNodeB Initiated Release:
• TA Timer Expiry
• Maximum RLC Retransmissions Exceeded
• GTP-U failure
• Handover related Drops
For internal use
Content
• Introduction
• KPIs:
- Important KPIs/Counters
• Summary
- parameters involved

For internal use
List of important KPIs
E-RAB Related
LTE_5025a E-RAB Drop Ratio:(abnormal E-RAB release requests / all E-RAB release
commands)*100%
LTE_5570c E-UTRAN E-RAB active drop ratio with data in the buffer due to RNL Radio Connection
with UE Lost
LTE_5581a E-UTRAN E-RAB Retainability Rate, RAN View, RNL Failure with UE Lost
LTE_5571b E-UTRAN E-RAB QCI1 with data in the queue drop ratio, RAN View, RNL Failure with UE
Lost
LTE_5090b E-UTRAN E-RAB Drop Ratio per Cause RNL (E-RAB drop ratio due to Radio Network
Layer
(RNL) cause initiated by eNodeB – visible to NSN user)
Note: For non-GBR data services can be
LTE_5575a E-UTRAN Total E-RAB Active Time high because always-on services may keep
LTE_5576a E-UTRAN E-RAB Active Time QCI1 UE all the time in RRC-Connected mode. A
LTE_5577a E-UTRAN E-RAB Active Time QCI2 very small number of drops can result in
LTE_5578a E-UTRAN E-RAB Active Time QCI3 high drop ratio. For example, when user
LTE_5580a E-UTRAN E-RAB Active Time nonGBR removes UE from laptop this results in a E-
RAB drop
M8008C0 REJ_RRC_CONN_RE_ESTAB
For internal use (Counter)
List of important KPIs
Handover Related
LTE_5043a E-UTRAN Total HO Success Ratio, intra eNodeB

LTE_5035a E-UTRAN HO Success Ratio, intra eNodeB
LTE_5058b E-UTRAN Total HO Success Ratio, inter eNodeB X2 based
LTE_5048b E-UTRAN HO Success Ratio, Inter eNodeB X2 based
LTE_5084a E-UTRAN Total HO Success Ratio, inter eNodeB S1 based
LTE_5082a E-UTRAN HO Success Ratio, inter eNodeB S1 based
LTE_5115a E-UTRAN Inter-Frequency HO Success Ratio Measurement Gap assisted
LTE_5195a E-UTRAN Inter RAT HO Success Ratio
LTE_5564a E-UTRAN Inter RAT HO UTRAN with SRVCC Success Ratio
LTE_5567a E-UTRAN Inter RAT HO GERAN with SRVCC Success Ratio
LTE_5174a E-UTRAN Number of Late HO Events
LTE_5175a E-UTRAN Number of Type 1 Early HO Events
LTE_5176a E-UTRAN Number of Type 2 Early HO Events
For internal use

KPI Targets and reference values Internal Use only!!
LTE_5025: eRAB Drop Ratio %
NSN Recommended values : LTE_5025< 0.3%,

Up to date NSN recommended values can be found in KPI Benchmarker Tool (apply the access rights
through the tool):
https://alpaca.emea.nsn-net.net/Alpaca/Account/Login?ReturnUrl=/Alpaca/
For internal use
EPS Bearer Connection Establishment
EPS Bearer
Success Connection
Ratio, Release Establishment
Ratio & Attempts
Scope:
Scope:
•KPI
•KPI LTE_5017A
LTE_5017A describes
describes thethe setup
setup success
Success Ratio, Release Ratio & Attempts ratio
success
ratio of the elementary E-RAB setup procedure
of the elementary E-RAB setup procedure
used
used to
to setup
setup the
the E-RAB
E-RAB between
between MME
MME and
and UEUE
•Note:
•Note: ItIt indicates
indicates the
the E-UTRAN
E-UTRAN contribution
contribution to
to
network accessibility for the end-user, not
network accessibility for the end-user, not the the
whole
whole end-to-end
end-to-end service
service accessibility.
accessibility.
Observation:
Observation:
•• The
The majority
majority of
of EPS
EPS Bearer
Bearer connection
connection
establishments
establishments problems (if RRC SR
problems (if RRC SR is
is good)
good)
indicate
indicate the transport or the core network issues
the transport or the core network issues
••E-RAB
E-RAB drop
drop ratio
ratio depends
depends on on RRC
RRC inactivity
inactivity
timer
timer
•3GPP
•3GPP recommends
recommends normalizing
normalizing drops
drops by
by time
time
(drops
(drops per
per minute)
minute) for
for non-GBR
non-GBR bearers
bearers
NSN
NSN Recommendation
Recommendation
Core
Core network
network KPIs
KPIs need
need to
to be
be analyzed
analyzed for
for further
further
problem isolation
problem isolation
Example KPI analysis
For internal use
8 ©2013 Nokia Solutions and Networks. All rights reserved.
Success Ratio, Release Ratio & Attempts
E-RAB Drop Ratio, Attempts
Scope:
Scope:
•KPI
•KPI LTE_5025d
LTE_5025d describes
describes E-RAB
E-RAB Drop
Drop ration
ration with
with
out
out pre-emptions
pre-emptions (RAN
(RAN point
point of
of view)
view)
..
Observation:
Observation:
•• The
The majority
majority ofof EPS
EPS Bearer
Bearer connection
connection
establishments
establishments problems (if
problems (if RRC
RRC SRSR is
is good)
good)
indicate
indicate the
the transport
transport or
or the
the core
core network
network issues
issues
•E-RAB
•E-RAB drop
drop ratio
ratio depends
depends on on RRC
RRC inactivity
inactivity
timer
timer
••3GPP
3GPP recommends
recommends normalizing
normalizing drops
drops byby time
time
(drops
(drops per
per minute)
minute) for
for non-GBR
non-GBR bearers
bearers
NSN
NSN Recommendation
Recommendation
Core
Core network
network KPIs
KPIs need
need to
to be
be analyzed
analyzed for
for further
further
problem
problem isolation
isolation
Example KPI analysis

For internal use
Content
• Introduction
• KPIs:
• Summary

For internal use
UE initiated Drop Call analysis
T310 expiry
Maximum number of RLC retransmissions
Handover failure (T304 expiry)
Non-HO related random access problem
For internal use

UE Detected Radio Link Failures (RLF) 1/2
• When UE is in RRC_CONNECTED and RRC security is active, it can trigger Radio Link
Failure (RLF) and initiate RRC connection re-establishment procedure after following
events (3GPP 36.331, 36.300):
1. upon T310 expiry

2. upon reaching the maximum number of RLC retransmissions
3. upon handover failure (T304 expiry)
4. upon non-HO related random access problem
• The UE sends, for the initiation of the procedure, an integrity checked

RRConnectionReestablishmentRequest message to the eNodeB
For internal use

UE Detected Radio Link Failures (RLF) 2/2
• The eNodeB checks whether it still has a valid UE:
- in a source cell which becomes the serving cell or

- in a prepared target cell which becomes the serving cell
• The eNodeB sends RRCConnectionReestablishment response to the UE for resuming

the SRB1 and security. The UE confirms the message with a
RRCConnectionReestablishmentComplete message. The eNodeB subsequently re
-establishes SRB2 and DRBs
• NOTE: if UE is in RRC_CONNECTED while RRC security is not active, UE goes to

RRC_IDLE, performs cell reselection and TAU
For internal use

RRC Re-Establishment procedure
Successful
UE EUTRAN
RRC Re-Est triggered. UE makes cell reselection and sends Re-Est.

RRCConnectionReestablishmentRequest
RRCConnectionReestablishment
RRCConnectionReestablishmentComplete
RRC Conn Re-Est can only succeed in a cell that has:

• Short MAC-I of the target cell
• PCI of the source cell
• C-RNTI in the source cell
For internal use
RRC Connection Re-establishment
Successful Procedure
Message Sequence Chart:
For internal use

RRC Re-establishment Request
Example: RRC Signaling Message
Time: 9:38:13.165
RRConnectionReestablishmentRequest (3GPP TS 36.331 ver 8.7.0 Rel 8)
UL-CCCH-Message
message
c1
rrcConnectionReestablishmentRequest
criticalExtensions
rrcConnectionReestablishmentRequest-r8
ue-Identity This is
This is the
the PCI
PCI ofof the
the cell
cell where
where UE
UE
c-RNTI was last
was last successfully
successfully connected
connected to.
to. In
In
Bin : 4C F0 (= 19696) HO case
HO case it’s
it’s the
the source
source cell.
cell.
physCellId : 30
shortMAC-I
Bin : AB 7D (= 43901)
reestablishmentCause : otherFailure
spare
Bin : 0 (2 bits)
Data (hex):
09 9E
For 01 EAuse
internal B7 D8
Successful
RRC SIGNALING MESSAGE
RRC Re-Establishment message
Time: 16:49:06.085 sets up SRB1 again
RRCConnectionReestablishment (3GPP TS 36.331 ver 8.7.0 Rel 8)
DL-CCCH-Message
message
c1
rrcConnectionReestablishment
rrc-TransactionIdentifier : 2
criticalExtensions
c1
rrcConnectionReestablishment-r8
radioResourceConfigDedicated
srb-ToAddModList
srb-ToAddModList value 1 SRB1 re-establishment
SRB1 re-establishment in
in RRC
RRC Conn
Conn
srb-Identity :1 Re-establishment message.
Re-establishment message.
mac-MainConfig
explicitValue
ul-SCH-Config
maxHARQ-Tx : n5
periodicBSR-Timer : infinity
retxBSR-Timer : sf2560
ttiBundling : false
drx-Config : release
For internal use
17 -----------------KLIP----------------------- ©2013 Nokia Solutions and Networks. All rights reserved.
Unsuccessful
UE EUTRAN
RRC Re-Est triggered. UE makes cell reselection and sends Re-Est.
RRCConnectionReestablishmentReject
Cell reselection + TAU Req

RRC Conn Setup Complete
(NAS: Tracking Area Update Request)
For internal use

RRC Connection Re-establishment
Unsuccessful Procedure
Message Sequence Chart:
For internal use

RRC Re-Establishment signaling Source Target Serving
HO Case
UE MME
eNB eNB GW
Packet data Packet data
Legend
Source C-RNTI, target short

Measurement Reports L3 signalling
HO Decision
Handover Request User Data MAC-I and source PCI sent

Admission Control and
Resource Allocation to target cell in X2AP HO
TX2RELOCOverall Handover Request Acknowledge
TX2RELOCexec Req
.RRC Connection Reconfiguration
Deliver buffered and in

Detach from old cell transit packets to target eNB
SN Status Transfer
Data Forwarding
Failes to access target cell
T304 expires
Cell selection to source cell Buffer Packets from
Source eNB
RRC Connection
Reestablishment
Request(Cause: handover
Failure; c-RNTI of source cell)
UE can try re-
Accept RCR
Stop data forwarding
Handover Cancel
establishment to any cell,
RRC Connection
Reestablishment but only source and target
RRC Connection
Reestablishment Complete cell are prepared
Reestablish SRB2 &
DRB
Optionally configure
Measurement Gaps
RRC Connection
Reconfiguration
RRC Connection
Reconfiguration Complete
Packet data Packet data
For internal use

RRC Re-Establishment –
message sequence flow
Unsuccessful HO execution or complete
For internal use

1. RLF due to T310 expiry at UE
First Phase Second Phase
radio
normal operation problem no recovery during T310 no recovery during T311 goes back to idle
detection
RRC_CONNECTED RRC_IDLE
radio link failure

n310 consecutive n311 consecutive in- Cell reselection and
out-of-sync sync indications Tracking Area Update
indications during t310 RRC connection re- if RRC Re-
establishment Establishment fails
- For UE “normal operation” in the figure above means : attempted during t311
• UE not waiting for RRC Connection Setup/Reject (T300 not running)
• UE not waiting for RRC Re-establishment Establishment/Reject (T301 not running)
• handover not ongoing (T304 not running)
• No RLF recovery ongoing (T311 not running)
- NOTE: the terms in-sync and out-of-sync refer to L1 problems, not to timing alignment
- Detection of physical layer problems in RRC_CONNECTED:
• The UE shall, upon receiving N310 consecutive "out-of-sync" indications from lower layers while neither T300, T301, T304 nor T311 is
running, start timer T310.
- Recovery of physical layer problems
• Upon receiving N311 consecutive "in-sync" indications from lower layers while T310 is running, the UE shall stop timer T310.
For internal use

1. RLF due to T310 expiry, in-sync and out-of-sync definition, without DRX,
3GPP TS 36.133 Sec 7.6
• When the downlink radio link quality estimated over the last [200] ms period becomes worse than the threshold Q out,
Layer 1 of the UE shall send an out-of-sync indication to the higher layers within [200] ms Q out evaluation period.
• When the downlink radio link quality estimated over the last [100] ms period becomes better than the threshold Q in,
Layer 1 of the UE shall send an in-sync indication to the higher layers within [100] ms Q in evaluation period.
• The threshold Qout is defined as the level at which the downlink radio link cannot be reliably received and shall
correspond to [10%] block error rate of a hypothetical PDCCH transmission taking into account the PCFICH errors
with transmission parameters specified in Table 7.6.1-1 of 3GPP TS 36.133.
• The threshold Qin is defined as the level at which the downlink radio link quality can be significantly more reliably
received than at Qout and shall correspond to [2%] block error rate of a hypothetical PDCCH transmission taking into
account the PCFICH errors with transmission parameters specified in Table 7.6.1-2 of 3GPP TS 36.133.
• UE timer T310 is started after n310 successive out-of-sync indications from physical layer. Two successive in-
sync/out-of-sync indications from physical layer shall be separated by at least [10] ms.
• NOTE: 3GPP notation [.] means that the final numerical values have not been agreed in the specification.
For internal use
In-sync and out-of-sync
Definition without DRX
• Window to estimate if BLER > out-sync threshold is [200ms] Hence: out of last 200 TTIs at least 20
PDCCH have been received in error
• Window to estimate if BLER < in-sync threshold is [100ms] Hence: out of last 100 TTIs at most 2
PDCCH have been received in error
BLER of reference
PCFICH + PDCCH
out-sync
out-sync
out-sync
out-sync
out-sync
out-sync
out-sync
out-sync
in-sync
in-sync
in-sync
10%
2%
>10ms time
NOTE: 3GPP notation [.] means that the final numerical values have not been agreed in the specification.
Reference For
PDCCH and PCFICH configuration used in the BLER estimation is defined by 3GPP
internal use
2. RLF due to maximum UL RLC Retransmission reached
normal operation RLC retransmissions until max value no recovery during T311 goes back to idle
radio link failure

RLC retransmissions Cell reselection
until max RLC retx and Tracking Area
threshold is reached RRC connection
Update if RRC
re-establishment
Re-Establishment
attempted during
fails
from RRC Connection Reconfiguration: t311
drb-ToAddModList
drb-ToAddModList value 1
drb-Identity :1
rlc-Config
am After max UL RLC retransmissions has been reached
ul-AM-RLC
t-PollRetransmit : ms40
pollPDU : p32
UE initiates the RRC connection re-establishment procedure
pollByte : kB25
maxRetxThreshold : t8
For internal use

3. RLF due to HO failure
normal operation Attempting PRACH to target cell no recovery during T311 goes back to idle
radio link failure
RRC Conn ReConf T304 running Cell reselection

RRC connection and Tracking Area
with MobilityInfo while UE re-establishment
attempting access Update if RRC
(”HO command”) attempted to Re-Establishment
to target cell. source or target fails
T304 expires cell during t311
from RRC Connection Reconfiguration:

- If PRACH procedure to the target cell does not succeed by the
mobilityControlInfo timer T304 expires:
targetPhysCellId : 33
t304 : ms1000 • UE tries RRC Connection Re-establishment with re-
newUE-Identity
Bin : 14 EB (= 5355) establishment cause ”handoverFailure”
For internal use

4. RLF due to non-HO random access failure
normal operation Attempting PRACH to serving cell no recovery during T311 goes back to idle
radio link failure

Example: Random Cell reselection
Access triggered due to UE attempting RRC connection
and Tracking Area
missing PUCCH SR random access to re-establishment
Update if RRC
resources, or PDCCH serving cell. attempted to
Re-Establishment
order serving cell during
fails
t311
RACH failure
- “Non-HO random access” means
• PDCCH order -triggered RA (RL30/RL25)
• Random Access Scheduling Request
- Random Access Scheduling Request is not a real radio link failure (time alignment status for the UE is ‘in-sync’), but
only as a result of UE PUCCH Scheduling Request is failing multiple times and thus, UE is sending SR on PRACH.
• eNodeB reconfigures PUCCH after detection of RA-SR.
• Otherwise UE tries RRC Connection Re-establishment.
For internal use
Re-establishment cause in RRC Conn Re-Est msg
Source: 3GPP TS 36.331
- UE sets the reestablishmentCause as follows:
- if the re-establishment procedure was initiated due to RRC reconfiguration failure (i.e., the UE is
unable to comply with the reconfiguration), UE sets the reestablishmentCause to the value
'reconfigurationFailure‘
- if the re-establishment procedure was initiated due to intra-LTE handover failure or inter-RAT
mobility from EUTRA failure, UE sets the reestablishmentCause to the value
'handoverFailure‘
- Otherwise UE sets the reestablishmentCause to the value 'otherFailure‘. NOTE: This includes
T310 RLF failure.
For internal use

Parameters 1/2
Following parameters are related to RLF detection and recovery:
Parameters Range Description Setting
This is the maximum number of consecutive "out of

n310 n1 (0), n2 (1), n3 (2), n4 (3), n6 sync" indications received from lower layers. n10
(4), n8 (5), n10 (6),n20 (7) n1 corresponds to 1 and so on.
Maximum number of consecutive "in-sync" indications received from lower

layers. If Layer 1 in UE detects N311 consecutive in-sync-indicators while T310 is
n311 n1 (0), n2 (1), n3 (2), n4 (3), n5 running, UE stops T310. If Layer 1 in UE detects no or less than N311 consecutive n1
(4), n6 (5), n8 (6),n10 (7) in-synch indications until T310 is expired UE starts RRC connection re-
establishment procedure - radio link failure. n1 corresponds to 1 and so on.
Timer T304 supervises the successful completion of a handover or cell change. If

50ms (0), 100ms (1), 150ms (2), T304 expires prior to the UE successfully completing the random access
t304IntraLte 200ms (3), 500ms (4), 1000ms procedure on the target cell, the UE initiates the RRC Connection re- 1000 ms
(5), 2000ms (6) establishment procedure. The UE starts this timer upon receiving the mobility
control information
For internal use

Parameters 2/2
Following parameters are related to RLF detection and recovery:

Upon finding a suitable cell on an LTE frequency, the UE stops the timer T311, starts
the timer T301 and initiates a contention based random access procedure to enable
the RRCConnectionReestablishmentRequest message to be sent. In the
RRCConnectionReestablishmentRequest message, the UE includes the identity used in
100ms (0), 200ms (1), 300ms (2), the cell in which the failure occurred, the identity of that cell, a short Message
400ms (3), Authentication Code and a cause. Timer T301 supervises the RRC connection
t301 200 ms
600ms (4), 1000ms (5), 1500ms reestablishment Procedure.
(6), 2000ms (7) Start: Transmission of RRCConnectionReestabilshmentRequest
Stop: Reception of RRCConnectionReestablishment
or RRCConnectionReestablishmentReject
message as well as when the selected cell becomes unsuitable. At expiry: Go to
RRC_IDLE
0ms (0), 50ms (1), 100ms (2),

t310 200ms (3), 500ms (4), 1000ms (5), Timer T310 supervises the recovery from physical layer problems. If Layer 1 in UE 2000 ms
2000ms (6) detects N310 consecutive out-of-sync indicators, T310 is started
1000ms (0), 3000ms (1), 5000ms Timer T311 supervises the RRC connection reestablishment. To attempt RRC
t311 (2), 10000ms (3), connection re-establishment, the UE starts a timer known as T311 and performs cell 3000 ms
15000ms (4), 20000ms (5), selection
30000ms (6)
For internal use

Content
• Introduction
• KPIs:
• Summary

For internal use
eNodeB initiated Drop Call analysis:
eNodeB Detected RLF
TA timer expiry
Maximum RLC retransmissions exceeded
GTP-U failure
For internal use

eNodeB initiated call drop Call Analysis
Overview
• Multiple methods (“link monitors”) are defined to detect a radio link problem in the eNodeB. eNodeB
can drop the call due to following triggers
• eNodeB-detected radio link problems
- Uplink PUSCH DTX detection for scheduled uplink data.
- CQI DTX detection for periodic CQI reports in PUCCH and PUSCH.
- Uplink Ack/Nack DTX detection for transmitted downlink data.
- PDCCH Order failure
- SRS RLF
• TA timer expiry
• Maximum RLC retransmissions exceeded
• GTP-U failure
For internal use

eNodeB Detected RLF
TA timer expiry
GTP-U failure
For internal use

Radio Link problem detection at eNodeB
Introduction
• eNodeB radio link problem detection mechanisms are NSN-internally specified

• Multiple methods (called “link monitors”) are defined to detect a radio link problem in the eNodeB.
• When one link monitor detects a problem, it is really a radio link problem even if other link monitors have not yet
indicated anything.
• Each link monitor has its internal criteria and filtering with internal counters to decide when there is a radio link
problem occurring and when there is a radio link problem recovery occurring.
• When a radio link problem is detected, an eNodeB-internal timer (T_RLF) is started. The timer T_RLF is stopped
when in case of radio link failure recovery.
• T_RLF = t310 + t311 (eNodeB-internal timer)
• Link monitors :
• Uplink PUSCH DTX detection for scheduled uplink data (RRM SFS ID 2041)
• CQI DTX detection for periodic CQI reports in PUCCH and PUSCH (Radio L1 SFS)
• Uplink Ack/Nack DTX detection for transmitted downlink data (RRM SFS ID 2006)
• PDCCH Order RLF (RL30)
• SRS DTX detection (RL15)
For internal use

1. PUSCH RLF: RlsCause_PuschRlf_ON
• When UE is scheduled for PUSCH transmission, eNodeB expects to receive UL transmission on the scheduled PRBs
• If signal from UE cannot be detected at all, PUSCH DTX is declared
NOTE: The case where UL TBS is received but it fails CRC check is not DTX (it’s a NACK)
• DTX PUSCH indication is provided by the UL physical layer.
• The result is received by LTE MAC in reliableULtransmissionFlag parameter (which can be seen in UL TTI trace).
• Both counter-based and timer-based RLF detection is supported
• Timer-based PUSCH RLF detection:

- If “DTX“ is received on the PUSCH for a configurable period of time (rlpDetMaxTimeUl), PUSCH RLF is set on
• Counter-based PUSCH RLF detection:
- If “DTX“ is received on the PUSCH for a consecutive number of times (rlpDetMaxNoUl), PUSCH RLF is set on
• The recovery of the radio link is indicated when for a configurable number of contiguous UL resource assignments data is
detected on PUSCH (ACK or NACK received).
- Defined byForparameter
internal use rlpDetEndNoUl.
Timer based detection details
RLF timer-based detection in case of rlpDetMaxTUl is not zero:
• LTE MAC shall start timer rrmUlPuschDtxTimer with value for the UE to which indication with
reliableULtransmissionFlag=FALSE is received when the previous indication was
reliableULtransmissionFlag=TRUE.
• The timer rrmUlPuschDtxTimer shall be stopped when indication with

reliableULtransmissionFlag=TRUE is received for the UE.
• If the timer rrmUlPuschDtxTimer reaches rlpDetMaxTUl value, LTE MAC shall indicate RLF of
the UE to LTE UEC (UE Control program block) by using MAC_RadioLinkStatusInd message with
rlsCause value RlsCause_PuschRlf_ON.
• RlsCause_PuschRlf_ON can be read in Emil trace or BTS UDP log

For internal use
• reliableULtransmissionFlag can be read in UL TTI trace

Counter based detection details
RLF counter-based detection in case of rlpDetMaxNUl is not zero:
• LTE MAC shall count consecutive indications with reliableULtransmissionFlag=FALSE in UE basis

and store the counter value to internal parameter rrmUlPuschDtxDetections.
• LTE MAC shall initialize the counter to zero and reset it after every indication with
reliableULtransmissionFlag=TRUE.
• If the counter rrmUlPuschDtxDetections for the UE reaches rlpDetMaxNUl value, LTE eNodeB
MAC layer indicates RLF to higher layers by using MAC_RadioLinkStatusInd message with
rlsCause value RlsCause_PuschRlf_ON.
For internal use

Recovery from RLF
Recovery from PUSCH RLF is counter-based
• LTE MAC shall count consecutive indications with reliableULtransmissionFlag=TRUE for those UEs
for which the indication is sent and store the counter value to internal parameter
rrmUlPuschTxDetections.
• LTE MAC shall initialize the counter to zero and reset it after every indication of
reliableULtransmissionFlag=FALSE.
• If the counter rrmUlPuschTxDetections of a UE reaches rlpDetEndNUl value, eNodeB MAC layer

shall indicate RLF cancellation of the UE to higher layers by using MAC_RadioLinkStatusInd
message with rlsCause value RlsCause_PuschRlf_OFF.
• Message can be seen in Emil or BTS log
For internal use

1. PUSCH RLF: RlsCause_PuschRlf, counter-based RLF detection example
RLF timer running
LSE
LSE
LSE
E
E
T_RLF = T310 + T311
R UE
R UE
RU E
R UE
R UE
R UE
RU E
ALS
ALS
ALS
g=FA
g=FA
g=FA
g=T
g=T
g=T
g=T
g=T
g=T
g=T
g=F
g= F
g=F
nFla
nFla
nFla
nFla
nFla
nFla
nFla
nFla
nFla
nFla
nFla
nFla
nFla
issio
issio
issio
issio
issio
issio
issio
issio
issio
issio
issio
issio
issio
ns m
nsm
nsm
nsm
nsm
nsm
nsm
ns m
ns m
nsm
nsm
nsm
nsm
Ltra
Ltra
Ltra
Ltra
Ltra
Ltra
Ltra
Ltra
Ltra
Ltra
Ltra
Ltra
Ltra
bleU
bleU
bleU
bleU
bleU
bleU
bleU
bleU
bleU
bleU
bleU
bleU
bleU
vendor-file parameters
relia
relia
relia
relia
relia
relia
in this example:
relia
relia
relia
relia
relia
relia
relia
3
2
uplink
PUSCH_RLF time
downlink ON
PUSCH_R
LF OFF
UL UL UL UL UL UL UL UL UL UL UL UL UL
grant grant grant grant grant grant grant grant grant grant grant grant grant
For internal use

2. Periodic CQI RLF: RlsCause_CqiRlf_ON
Source: Radio L1 SFS
• The eNodeB supports CQI DTX detection for periodic CQI reports on PUCCH and PUSCH.
• If MAC layer receives nCqiDtx consecutive reports from UL PHY, the MAC declares CqiRLF_ON
- can be seen in BTS log and Emil
• If the MAC has set CqiRLF_ON for a specific UE and nCqiRec consecutive CQI reports are again
detected successfully for that UE, the MAC sets CqiRLF_OFF
• The parameters nCqiDtx and nCqiRec are in the vendor-specific parameter file
• For both PUSCH and PUCCH the periodic CQI is encoded using a Reed Muller block code and comes
along without any CRC. Hence, the UL PHY indicates a DTX detection for periodic CQI reports on
PUCCH or PUSCH whenever a report is configured but no reliable transmission from the UE could be
detected. So the output of the detector shall be either the detected CQI report or a DTX indication.
• NOTE: CQI_RLF detection

For internal use does not apply to aperiodic CQI report on PUSCH
2. Periodic CQI RLF: RlsCause_CqiRlf
Example
T_RLF = T310 + T311
d te
tecte
etec
dete ic CQI
e
dete odic CQ
RLF timer running
QI d
QI d
cted
cted
od
ic C
dic C
Peri
CQI
CQI
CQI
CQI
CQI
od
CQI
CQI
CQI
CQI
DTX
CQI
DTX
DTX
DTX
DTX
Peri
DTX
DTX
DTX
DTX
DTX
o
Peri
Peri
CQI_RLF time
ON
LNCEL/cqiPerNp=10ms CQI_RLF
OFF
vendor-file parameters in this example:
6
1
For internal use
Emil example
Example of
Example of
UL Problems
UL Problems
For internal use

3. Ack/Nack RLF: RlsCause_AckNackRlf_ON
Source: RRM SFS ID 2006
• After DL scheduled data, eNodeB expects HARQ ACK or NACK on PUCCH or PUSCH at known UL
TTI
• Timer-based ACK/NACK RLF detection:
- If ACK/NACK “DTX“ is received for a configurable period of time (rlpDetMaxTimeDl), ACK/NACK RLF is set on
• Counter-based ACK/NACK RLF detection:

- If ACK/NACK “DTX“ is received for a consecutive number of times (rlpDetMaxNoDl), ACK/NACK RLF is set on
• The recovery of the RLF is indicated when for a configurable number of contiguous ACK/NACK
opportunities ACK or NACK is detected on PUSCH or PUCCH (no DTX):
- Defined by parameter rlpDetEndNoDl.
• Setting rlpDetMaxTimeDl=0 switches off time-based radio problem detection.

For internal use
44 • Setting rlpDetMaxNoDL=0
Presentation / Author / Date switches off counter-based radio
©2013 Nokia problem
Solutions detection.
and Networks. All rights reserved.
4. PDCCH Order RLF
Source: L2 SFS
• If there DL data in eNodeB buffer and UE is out-of-sync, UE must be brought back to in-sync (time
aligned) with a RA procedure before DL data can be sent
• Signaling of dedicated RA preamble via PDCCH (so-called PDCCH order) is done using DCI format
1A
• In case that PDCCH order fails for a UE (i.e., no transmission of assigned dedicated preamble
detected by eNodeB, or no msg3 transmission) the PDCCH order shall be repeated
noRepPdcchOrder times (R&D configurable parameter, range 0-3, default 1), again using the
selected preamble and considering DRX status of the UE accordingly.
• Final failure of the PDCCH order process shall be indicated as radio link problem to higher layers
with cause “PDCCH order failure” (see UESTATE.1496).
• If inactivity timer for the UE has expired then there is no T_RLF timer involved  S1 and RRC
released immediately
For internal use
5. SRS RLF
Source: L1 TD SFS
• The eNodeB supports SRS DTX detection for radio link problem detection
• If MAC layer receives nSrsDtx consecutive reports from UL PHY, the MAC declares SRS RLF
• If the MAC has set SRS RLF for a specific UE and nSrsRec consecutive SRS transmissions are
succesfully detected the UE, the MAC sets SRS RLF OFF
- Hence the SRS RLF has similar mechanism as CQI DTX RLF
• The parameters nSrsDtx and nSrsRec are operator-configurable

• default values from RL50 SCF:
50
1
For internal use

RLF related parameters in vendor file, RL50
50
2
3
3
1000
1000
0
0
For internal use

RLF related Call Drop Triggered by e-NB Source: UE State handling SFS
RRC release + S1 release
• 3GPP does not specify eNodeB radio link failures, but NSN eNodeB mimics the behavior of the UE
RLF specified in 3GPP.
• When a radio link problem is detected, an eNodeB-internal timer (T_RLF) is started. The timer T_RLF
is stopped when in case of radio link failure recovery.
• For a given UE, T_RLF is started when any of the PUSCH RLF, CQI RLF, SRS RLF or AckNack RLF
is set to ON state
• For a given UE, T_RLF is stopped only if all RLFs are OFF
• When the timer T_RLF expires, the UE is released from the eNodeB using eNodeB initiated S1
release + RRC connection release –> call drop
• T_RLF = T310 + T311
For internal use

RLF triggering by eNodeB
Signaling
UE eNB MME S-GW
Detect radio link

UE in
problem, T_RLF
RRC-CONNECTED
expires
S1AP: UE Context Release Request
S1AP: UE Context Release Command
S11 interaction to inform S-GW

RRC: RRC Connection Release S1AP: UE Context Release Complete about connection release
Set UE to Release all UE related Set UE to

RRC-IDLE resources, ECM-IDLE
remove UE context
Only L2 Ack needed for successful RRC Conn Release. If L2 Ack not received after timer tL2AckRrcRel expires
(def=800ms), RRC is released anyway.
NOTE: No RLC Ack needed for RRC Connection Release. No reTx for RRC Connection Release
For internal use

eNodeB Detected RLF
TA timer expiry
GTP-U failure
For internal use

In-sync and out-of-sync states
Overview
• RRC connected sub=states: UL in-sync and UL out-of-sync
E-UTRA
RRC_CONNECTED
Expiry of DRX Short Inactivity Timer (intentional)
Timing maintenance issue (unintentional)
Uplink RA SR or downlink
PDCCH order to bring UE
TA TA back in-sync (RL30)
UL in-sync UL out-of-sync
Contention-based RA success after UL data arrival

PDCCH order success after DL data arrival
PDCCH order success after DRX Inactivity timer expiration
RRC Connection Reestablishment
RRC Connection Setup

RRC Connection Release
PDCCH order failure after DL data arrival
Radio link failure
PDCCH order failure after Inactivity timer expiration
E-UTRA
RRC_IDLE
For internal use

TA timer expiry at UE
• As UE detects Out-of-Sync status using a Timing Alignment Timer, the timer shall be started or
restarted whenever an initial TA or a TA update command is received (see [3GPP-36.321], section 5.2). If
the timer expires, the UE detects out-of-sync status.
• 3GPP TS 36.321: When timeAlignmentTimer expires at UE, UE MAC layer shall:

- flush all HARQ buffers;
- notify RRC layer to release PUCCH/SRS;
- clear any configured downlink assignments and uplink grants
• 3GPP TS 36.331: Upon receiving a PUCCH/ SRS release request from MAC layer, the UE RRC shall:
- release periodic CQI reporting config, i.e. it stops CQI reporting on PUCCH
- release Scheduling Request Config
For internal use

TA timer expiry at eNodeB (1/3)
Maintenance of UL Time Alignment by eNodeB (source: Radio L2 SFS)
• UL TA update is done periodically and in addition on per-need basis. MAC entity provides PHY layer
the information when a TA update is needed together with the TA update value. MAC entity in
eNodeB shall send it to UE via Timing Alignment MAC control element.
• The interval between periodic TA update commands is based on the Timing Alignment Timer
reduced by a configurable offset taTimerMargin.
• Radio L2 SFS: TA command period = TimeAlignTimer – taTimerMargin
• A configurable parameter TimeAlignmentMaxOffset is used to determine the maximum allowed
timing alignment offset before a per-need timing alignment update is required.
For internal use

• If the TA offset measured by the UL PHY layer is greater than the configurable threshold
TimeAlignmentMaxOffset then a TA command is sent to the UE.
• If the reported TA offset also exceeds a threshold calculated as taSchedulingThreshold =
max(taOffsetSchedMgn, TimeAlignmentMaxOffset +0.5µs), the UL scheduler is informed that the UE
is drifting out of alignment
• When HARQ ACK feedback is received for the TA command then:
- For a per-need TA command and when taSchedulingThreshold (see above) was exceeded: the UL scheduler is
informed that the TA is OK again.
- The periodic timing alignment timer is (re)started.
For internal use

• If no HARQ ACK feedback is received for a TA command within the maximum number of DL HARQ
transmissions then:
- The TA update command shall be repeated up to a configurable maximum number of times taCommandMaxRetries
or until the timing alignment timer expires; the latest available timing advance estimation shall be used for every
repetition.
• If the maximum number of retries is exceeded or the timing alignment timer has expired, then
status UE UL out-of-sync is detected  TatExpiry seen in UDP Log and Emil
• Immediate release of RRC and S1 follows (there is no waiting for T_RLF expiry)
For internal use

Time Alignment Mechanism
• Periodic TA command (successful)
taTimer
taTimerMargin
Timer1 Send
Start Timer1: expires TA-cmd Re-Start Timer1
taTimer-taTimerMargin
Harq Ack
• Periodic TA command (unsuccessful)

Up-to
Timer1 Send taCmdMaxRetry
Start Timer1: TA-cmd
RLF TatExpiry
expires
taTimer-taTimerMargin HARQ
Retransm.
[harqMaxTrD-1]
This retry mechanism applies also to Harq Nack taTimer = 10240ms

- On-Need-Base/EmergencyTA-cmd Time window until Call is TaTimerMargin = 2000ms
dropped: harqMaxTrD = 4
~ 10*4*8 = 320 ms taCmdMaxRetry = 10
• On-Need-Base/Emergency TA command taMaxOffset = 0.52us
- if calculated TA > taMaxOffset => send TA-cmd

For internal use
56 / ©2013 Nokia Solutions and Networks. All rights reserved.
In-sync, out-of-sync handling in RL30
• Parameter LNCEL/applyOutOfSyncState defines how eNodeB handles TA expiry

- Determines which UEs shall be actively sent to UL out-of-sync state provided that bearer
combination and applied DRX profile allows for this.
- extendedDrxOnly: only UEs being configured with extended settings for the long DRX cycle
- allDrx: all UEs being configured for DRX provided that applied DRX profile allows
- allUEs: all UEs independently of DRX configuration provided that bearer combination allows.
For internal use

•
In-sync normal case Procedure describes how an UE gets back into UL
synchronization from a state in which the time alignment
has been lost
UE eNB MME
- eNodeB detects that the time alignment of the UE is
UL out-of-sync (e.g. expiration of time alignment
eNB detects timer)
UE detects
TA „out-of-sync“
- UE also detects out-of-sync (same trigger) and
TA „out-of-sync“ and
releases PUCCH/SRS releases resources on PUCCH for CQI reporting and
resources
scheduling request
DL Data Activity
eNB detects DL data
RA triggered by PDCCH order (DCI 1A format)

- If eNodeB detects DL data (either data traffic or RRC
signalling)
eNB detects that RA is • eNodeB sends a PDCCH order for RA procedure to UE
performed and recognizes that
TA „in-sync“
(DCI 1A with specific codepoint; preferably non-
contention based RA depending on preamble availability)
UL Data Activity
• UE starts a random access procedure
• eNodeB recognizes when random access of the UE was
UE detects UL data
successful and UE UL time alignment is back “in-sync”
RA triggered by UL data
eNB detects that RA is

- If UE detects UL data (either data traffic or RRC
TA „in-sync“ signalling):
• UE starts a random access procedure (contention-
based)
• eNodeB recognizes when random access of the UE was
RRC: RRCConnectionReconfiguration
PUCCH/SRS resources
successful and UE UL time alignment is back “in-sync”
UE sets up PUCCH/SRS
resources
UL Grant via SR
- eNodeB triggers the RRC procedure RRC
RRC: RRCConnectionReconfigurationComplete Connection Reconfiguration to configure (again) the
For internal use
PUCCH resources for CQI reporting and scheduling
58 /
request
©2013 Nokia Solutions and Networks. All rights reserved.
• Same resource used for simplification but could be
optimized optionally
In-sync failure case • Procedure describes how eNodeB detects
that an UE has been lost – triggered by
downlink traffic
- eNodeB detects that the time alignment of the UE
is “out-of-sync” (e.g. expiration of time alignment
UE eNB MME timer)
eNB detects
-
TA „out-of-sync“
UE detects UE detects also that the time alignment is out-of-
TA „out-of-sync“ and
releases PUCCH/SRS sync and releases its PUCCH resources for CQI
resources
reporting and scheduling request and/or UE
detects a radio link failure and moves to
UE detects RLF and goes to
RRC IDLE
RRC_IDLE
eNB detects DL data - If eNodeB detects DL data (either data traffic or

RRC signalling)
RA triggered by PDCCH order (DCI 1A format) • eNodeB sends a PDCCH order DCI 1A to UE (may
include several re-tries)
• UE will not recognize this PDCCH order because it has
eNB detects that no RA is
gone to RRC_IDLE
TA has failed • eNodeB recognizes that the random access of the UE
was not successful (UE does not send any random
Normal RLF handling with new trigger „in-sync failure
access preamble) and that the “in-sync” handling has
failed
- This event is handled as a new trigger for the

radio link failure procedure
• eNodeB starts a supervision timer T-RLF and triggers UE
Context Release after timer expiration
For internal use • Note: by using the supervision timer, UE is able to return
59 / to cell
©2013 Nokia Solutions and via the
Networks. RRCreserved.
All rights Connection Reestablishment
procedure
User Inactivity Detection during out-of-sync
• Procedure describes how eNodeB handles an UE whose
time alignment is out-of-sync and whose inactivity timer
UE eNB MME
has expired
TA of UE gets „out-of-sync“ - eNodeB detects that the time alignment of the UE is
“out-of-sync” (e.g. expiration of time alignment timer)
(UE has released PUCCH/SRS resources)
Inactivity
Timer
Alt. UE has gone to RRC IDLE
UE detects RLF and/or

goes to IDLE - The inactivity timer for the UE expires. In the
meantime, UE may still be RRC_CONNECTED or may
RA triggered by PDCCH order have gone to RRC_IDLE silently
eNB detects that no RA is
TA has failed
- eNodeB checks the reachability of the UE by sending

UE Context Release with cause „Radio Connection with UE Lost“
the PDCCH order (DCI 1A)
Alt.
UE remains RRC CONNECTED
RA triggered by PDCCH order

- If UE performs a random access
• eNodeB recognizes that this is a normal “user inactivity” case
eNB detects that RA is
• eNodeB sends the RRC message
performed and recognizes that RRCConnectionReconfiguration to configure PUCCH/SRS
TA „in-sync“
resources
RRC: RRCConnectionReconfiguration • eNodeB sends the message UE CONTEXT RELEASE
PUCCH/SRS resources
REQUEST to MME with cause “User Inactivity”
RRC: RRCConnectionReconfigurationComplete
• If MME starts the UE Context Release procedure
S1AP: UE CONTEXT RELEASE REQUEST
- eNodeB sends the RRC message
Cause: User Inactivity
RRCConnectionRelease to UE and releases the UE
context.
MME initated UE Context Release Procedure • If MME does not start the UE Context Release procedure
- eNodeB keeps the current configuration.
- Note: this may happen if new DL data arrive - either data
For internal use traffic or S1AP signalling
RRC + S1 release after TA timer expiry at eNodeB when RL30 out-of-sync
handling not used for UE
NOTE: TA
NOTE: TA out-of-sync
out-of-sync causes
causes immediate
immediate
release (no
release (no T_RLF
T_RLF involved)
involved)
UE eNB MME S-GW
UE in
TA timer expires
RRC-CONNECTED
S1AP: UE Context Release Request
S1AP: UE Context Release Command
S11 interaction to inform S-GW

RRC: RRC Connection Release S1AP: UE Context Release Complete about connection release
Set UE to Release all UE related Set UE to

RRC-IDLE resources, ECM-IDLE
remove UE context
For internal use

TA timer expiry at eNodeB, Emil example
TaTExpiry followed
TaTExpiry followed by
by
immediate S1
immediate S1 ++ RRC
RRC
release)
release)
For internal use

Presentation / Author / Date
Time Alignment
Parameters
Following parameters are recommended for UL time alignment configuration:
Determines the number of subframes after which a

UE assumes it is out-of-sync in UL if no Time Alignment
500 (0), 750 (1), 1280 (2), 1920 command was received. The increased TA timer saves resources due to
taTimer
(3), 2560 (4), 5120 reduced number of TA command transmissions and also allows UEs more 10240 (6)
(5), 10240 (6) time for answering TA command and thus, probability for dropped calls (RLF)
might be less in case of UE is shadowed for short time only or not responding
for short time.
The parameter defines lead with respect to the

taTimerMargin 0...2560 taTimer expiration time for starting to send the 2000
periodic timing advance command.
Determines the maximum allowed Time Alignment
taMaxOffset 0...5, step 0.01 offset. If the value is exceeded, TA command is sent to the UE to adjust UL 52 (0.52us)
timing.
For internal use

eNodeB Detected RLF
TA timer expiry
GTP-U failure
For internal use

RLC layer STATUS polling mechanism
- RLC layer retransmissions only in RLC acknowledged mode
- RLC AM transmitter requests a STATUS PDU from RLC receiver (sets poll bit on in RLC header)
• After the number of bytes transmitted since previous poll exceeds the value of amRlcPBTab3ulPollByte (uplink, ue
cat3) or amRlcPBTab3dlPollByte (downlink, ue cat3), or
• After pollPdu RLC PDUs have been transmitted since previous poll
• in the last data PDU in the RLC transmit buffer
- The RLC AM receiver responds to polling request by transmitting a STATUS PDU which acknowledges successfully
received PDUs and also selectively nacks unsuccessfully received PDUs.
• RLC receiver also sends STATUS PDU if tReord timer expires.
• RLC receiver will not send STATUS PDU more often than interval defined by parameter tProhib.
• NOTE: default PDDB settings tProhib=50ms and tReord=50ms.
- If RLC transmitter receives no STATUS PDU within tPollretr, a new poll request along with unacknowledged data will be
sent to RLC receiver
For internal use

65 - RLC AM Presentation
window size is/ Date
/ Author fixed to 512 RLC PDUs (segments©2013
of an RLC
Nokia PDU
Solutions andare counted
Networks. asreserved.
All rights one PDU).
RLC layer ARQ mechanism
• RLC transmitter will retransmit all data that is NACKed in the STATUS PDU
• Maximum number of UL and DL RLC retransmissions is defined by vendor parameter drbAmMxRtxTh
(default=16)
Ttransfer-1 Twait<= tProhib Ttransfer-2
Rx
Tx
time
Polling trigger reached ACKed RLC PDUs can
be removed from buffer
AM RLC Round Trip Time
For internal use

66 Presentation / Author / Date
©2013 Nokia Solutions and Networks. All rights reserved.
Reaching Max #RLC Retransmissions
• The 3GPP described reaction after the detection of the event “Maximum number of RLC retransmissions”
for an RLC PDU is to initiate an intra-cell handover but this is not supported until RL50 (?)
- As a work-around, eNodeB waits for an UE initiated RRC Connection Reestablishment
• eNodeB never resumes the SRB/DRB without an intra-cell handover or RRC connection reestablishment
because the affected RLC entity is still blocked
- intra-cell handover cannot be initiated if the event “Maximum number of RLC retransmissions” has
occurred for SRB1 (the RRC message RRCConnectionReconfiguration cannot be sent to UE) i.e. only
applicable for SRB2 and DRBs
SBR ID Usage
0 for RRC messages using the CCCH logical channel e.g. RRC Connection Setup message
1 for RRC messages (which may include a piggybacked NAS message) as well as for NAS
messages prior to the establishment of SRB2 (prior security activation), all using DCCH
logical channel;
2 for NAS messages, using DCCH logical channel. SRB2 has a lower-priority than SRB1 and is
always configured ONLY after security activation.
For internal use

SRB1
• eNodeB RLC layer notifies that the RLC AM entity of a SRB1 (RRC message with piggybacked NAS) has reached the
event “Maximum number of RLC retransmissions” for an RLC PDU
• eNodeB initiates a S1AP release procedure:

- eNodeB sends the S1AP message UE CONTEXT RELEASE REQUEST with cause “RNL Cause Radio
Connection with UE Lost” to MME to initiate the UE release as for the radio link failure procedure
• 17 RLC transmissions with polling interval of 100ms = 1700ms
17 RLC transmissions with

polling interval of 100ms =
1700ms
For internal use

drb-ToAddModList {
{eps-BearerIdentity 5,
drb-Identity 4,

pdcp-Config {
discardTimer ms750,
rlc-AM {
SRB1 statusReportRequired TRUE},

headerCompression notUsed : NULL},
rlc-Config am : {
ul-AM-RLC {
t-PollRetransmit ms120,
• t-PollRetransmit is by default set to 100ms for SRB and 120ms for DRB (tPollRetr) pollPDU p64,
pollByte kB500,
• maxRetxThreshold is set to 16 for SRB and also 16 for DRB (drbAmMxRtxTh) maxRetxThreshold t16},
• Note that the parameters above are hard coded for SRB
dl-AM-RLC {
t-Reordering ms50,
• Above means that the RLC (re)transmissions takes t-StatusProhibit ms50}},
logicalChannelIdentity 3,
- SRB 100ms*17 = 1700ms logicalChannelConfig {
ul-SpecificParameters {
- DRB 120ms*17 = 2040ms priority 9,
prioritisedBitRate kBps16,
message c1 : rrcConnectionSetup : { bucketSizeDuration ms100,
rrc-TransactionIdentifier 2, logicalChannelGroup 2} } },
criticalExtensions c1 : rrcConnectionSetup-r8 : { {eps-BearerIdentity 6,
radioResourceConfigDedicated { drb-Identity 5,
srb-ToAddModList { pdcp-Config {
{ discardTimer ms750,
srb-Identity 1, rlc-AM {
rlc-Config explicitValue : am : { statusReportRequired TRUE},
ul-AM-RLC { headerCompression notUsed : NULL},
t-PollRetransmit ms100, rlc-Config am : {
pollPDU pInfinity, ul-AM-RLC {
pollByte kBinfinity, t-PollRetransmit ms120,
maxRetxThreshold t16 pollPDU p64,
}, pollByte kB500,
dl-AM-RLC { maxRetxThreshold t16},
t-Reordering ms50, dl-AM-RLC {
t-StatusProhibit ms0 t-Reordering ms50,
} t-StatusProhibit ms50} },
}, logicalChannelIdentity 4,
logicalChannelConfig {
ul-SpecificParameters {
priority 9,
For internal use prioritisedBitRate kBps16,
69 ©2013 Nokia Solutions and Networks. All rightsbucketSizeDuration

reserved. ms300,
logicalChannelGroup 3} } } },
DRB
• If eNodeB RLC layer notifies that the RLC AM entity of a DRB has reached the event “Maximum
number of RLC retransmissions” for an RLC PDU
- eNodeB starts the timer T_RLC based on the value of the RRC timer T311
- The timer T_RLC is stopped if the eNodeB accepts an RRC message
RRCConnectionReestablishmentRequest from UE or the RLF timer T_RLF has expired
- When the timer T_RLC expires, eNodeB checks whether the timer T_RLF is running:
• If T_RLF is running, eNodeB ignores all subsequent indications that a problem triggering an
RLF has recovered and wait for the expiration of T_RLF or an accepted RRC message
RRCConnectionReestablishmentRequest from the UE
• Otherwise eNodeB sends the S1AP message UE CONTEXT RELEASE REQUEST with cause
“RNL Cause Radio Connection with UE Lost” to MME to initiate the UE release as for the radio
link failure procedure
For internal use

Reaching Max #RLC Retransmissions (1/2)
DRB
T_RLC
T_RLC == T311
T311 == 5s
5s started
started (T_RLC
(T_RLC == T311
T311 ++ 200ms)
200ms)
T_RLC
T_RLC expiry
expiry
For internal use

Reaching Max #RLC Retransmissions (2/2)
DRB
• Max RLC Retransmissions Exceeded in above case is for DRB as can be seen from the TUP error message below
(DRBid = 4 i.e. EPS Bearer Id = 5)
For internal use

eNodeB Detected RLF
TA timer expiry
GTP-U failure
For internal use

Release due to GTP-U Error Indication from S-GW (eNodeB-triggered)
Source: Bearer Management SFS
• eNodeB may receive a “GTP-U Error Indication” on an active (single) S1 bearer (S-GW has rejected
the reception of uplink data packets) - for more details see [DATAPATH SFS].871. In that case
eNodeB shall send the S1AP message UE CONTEXT RELEASE REQUEST with cause “TNL Cause
Transport Resource Unavailable” to MME - for details see [UESTATE SFS].720).
• Example: This failure cause happens in X2 handover if S-GW relocation is attempted.
For internal use

Release due to GTP-U Error Indication from S-GW
eNodeB Triggered
GTP-U Error
GTP-U Error received
received
from S-GW  release
from S-GW  release
S1 + RRC
S1 + RRC
For internal use

Content
• Introduction
• KPIs:
• Summary

For internal use
Drop call can be initiated by UE, MME or eNodeB
• UE can ”initiate a drop” by starting RRC Connection Re-establishment

• Note: besides RLF also other causes can trigger RRC Conn Re-Establishment
• eNodeB can initiate abnormal S1 + RRC release due to:

• Radio network layer problem (TA timer, RLF, PDCCH Order failure)
• Transport network layer problem (GTP-U error, Treloc expiry, Path Switch problem)
• Other abnormal cause
• MME can initiate abnormal S1 + RRC release due to:

• Radio network layer problem
• Other abnormal cause
For internal use

Successful case
RRC Conn Re-Est can only succeed in a cell that has:

• Short MAC-I of the target cell
• PCI of the source cell
• C-RNTI in the source cell M8008C4 RRC_CON_RE_ESTAB_ATT
M8008C6 RRC_CON_RE_ESTAB_ATT_HO_FAIL
M8008C8 RRC_CON_RE_ESTAB_ATT_OTHER
M8008C5 RRC_CON_RE_ESTAB_SUCC
M8008C7 RRC_CON_RE_ESTAB_SUCC_HO_FAIL
M8008C9 RRC_CON_RE_ESTAB_SUCC_OTHER
For internal use

Unsuccessful Procedure
For internal use

eNodeB initiated abnormal release counters
eNodeB initiated EPS bearer release (abnormal)

ECM_CONNECTED
ECM_CONNECTED M8006C12 eNodeB_EPS_BEARER_REL_REQ_RNL
eNodeB MME
M8006C14 eNodeB_EPS_BEARER_REL_REQ_TNL
Abnormal M8006C13 eNodeB_EPS_BEARER_REL_REQ_OTH
release M8006C134 eNodeB_EPS_BEAR_REL_REQ_R_QCI1
M8006C143 eNodeB_EPS_BEAR_REL_REQ_O_QCI1
S1AP: UEContextReleaseRequest M8006C152 eNodeB_EPS_BEAR_REL_REQ_T_QCI1
With cause
eNodeB initiated UE Context Release (abnormal)
S1AP: UEContextReleaseCommand
M8013C15 eNodeB_INIT_TO_IDLE_RNL
With cause
M8013C16 eNodeB_INIT_TO_IDLE_OTHER
S1AP: UEContextReleaseComplete
Radio bearer release (abnormal)
M8007C5 RB_REL_REQ_RNL
ECM_IDLE
ECM_IDLE M8007C6 RB_REL_REQ_OTHER
M8006 EPS Bearer Measurements: cell level

M8007 Radio Bearer Measurements: cell level
M8013 UE State Measurements: cell level
For internal use
MME initiated abnormal release counters
ECM_CONNECTED
ECM_CONNECTED
eNodeB MME
MME initiated EPS bearer release (abnormal)
Abnormal M8006C8 EPC_EPS_BEARER_REL_REQ_RNL
release
M8006C9 EPC_EPS_BEARER_REL_REQ_OTH
S1AP: UEContextReleaseCommand MME initiated UE Context Release (abnormal)

With cause M8013C11 EPC_INIT_TO_IDLE_RNL
M8013C12 EPC_INIT_TO_IDLE_OTHER
S1AP: UEContextReleaseComplete
Cause value
Cause value mapping
mapping
should be
should be checked
checked
ECM_IDLE
ECM_IDLE from MME
from MME
M8006 EPS Bearer Measurements: cell level

M8007 Radio Bearer Measurements: cell level
M8013 UE State Measurements: cell level
For internal use
MME initiated Transaction to ECM-Idle state
Normal procedure
For internal use

eNodeB initiated Transition to ECM-IDLE
Normal procedure
For internal use

MME initiated Transaction to ECM-Idle state
Abnormal procedure
For internal use

eNodeB initiated Transaction to ECM-IDLE
Abnormal procedure
For internal use

Transaction to ECM-Idle State Due to Reset on S1
Abnormal procedure
For internal use

Content
• Introduction
• KPIs:
• Summary

For internal use
Handover measurements
Counters
• Counters of group M8009 Intra-eNodeB HO measurement give information per source cell only
• Counters of group M8014 Inter-eNodeB HO measurement give information per source cell only
• Counters of group M8015 give information per neighbor
- M8015C0: Failed intra eNodeB HO preparations
- M8015C1: Intra eNodeB HO attempts
- M8015C2: Intra eNodeB HO successes
- M8015C15: Intra eNodeB HO failures (any reason)
For internal use

Intra eNodeB Handover (Positive)
UE Source cell Target cell MME SGW

Measurement configuration
UL/DL Data (source cell)
M8009 Intra eNodeB Handover Measurements, triggered in source

RRC Measurement Report cell
Intra-eNodeB M8009C1 TOT_HO_DECISION

Handover
decision
Succesful RAC and
resources allocation
on target cell M8009C2 INTRA_eNodeB_HO_PREP
RRC Connection Reconfiguration
PRACH Msg1 (ded. preamble) M8009C6 ATT_INTRA_eNodeB_HO

M8007C0 DATA_RB_STP_ATT (triggered in target cell)
Msg2 L2 UL Allocation + TA
RRC Connection Reconfiguration Complete

M8009C7 SUCC_INTRA_eNodeB_HO
Release
source M8007C1 DATA_RB_STP_COMP (triggered in target cell)
For internal use resources
UL/DL Data (target cell)
Intra eNodeB Handover KPI, total success rate
Total Success Rate
• Formula LTE_5043a: (NetAct names)
100*sum(SUCC_INTRA_eNodeB_HO) / sum(INTRA_eNodeB_HO_PREP)
• M8009C7 SUCC_INTRA_eNodeB_HO = The reception of an internal UE Context Release

Request for the handover on the source side. Updated to the source cell.
• M8009C2 INTRA_eNodeB_HO_PREP = An internal eNodeB trigger. The eNodeB MM receives a

list with the target cells from RRM and decides on an Intra-eNodeB Handover. Updated to the
source cell.
For internal use

Intra eNodeB Handover
Negative 1

RRC Measurement Report M8009 Intra eNodeB Handover Measurements, triggered in source
cell
No Intra-eNodeB
Handover decision
M8009C0 TOT_NOT_START_HO_PREP
Measurement report received but handover not started for some

reason
For internal use

Negative 2


Intra-eNodeB
Handover
decision
Admission control and
resources allocation fails
on target cell M8009C3 FAIL_eNodeB_HO_PREP_AC
RAC failure
For internal use

Negative 3


Intra-eNodeB
Handover
decision
HO preparation not
triggered
M8009C5 FAIL_eNodeB_HO_PREP_OTH
Other reason that does not fit
any other cause
For internal use

Negative 4
RRC Conn Reconfiguration

w/ mobilityControlInfo IE
RRC Conn Reconfig Complete

missing in target (timer ??)
M8007C2 DATA_RB_STP_FAIL
Counter triggered in target cell
For internal use

Handover Preparation Failure (Counter Update)
For internal use

Handover Execution Failure (Counter Update)
For internal use

Inter eNodeB Handover
Positive, preparation
UE Source eNodeB Target eNodeB MME SGW

UL/DL Data (source eNodeB)
M8014 Inter eNodeB Handover Measurements, triggered in source

RRC Measurement Report
cell
inter-eNodeB
Handover M8014C0 INTER_eNodeB_HO_PREP
decision
X2AP Handover Request
Admission control
and resources
allocation on target
eNodeB (RAC+TAC) M8014C6 ATT_INTER_eNodeB_HO
RRC Conn Reconfiguration X2AP Handover Request Ack

M8007C0 DATA_RB_STP_ATT (triggered in target cell)
For internal use

Inter eNodeB Handover M8014 Inter eNodeB Handover
Measurements, triggered in source cell
Positive, Execution
Source Target
UE eNodeB eNodeB MME SGW

w/ mobilityControlInfo IE DL Data (target eNodeB)
X2AP Status Transfer

PRACH Msg1 (ded. preamble)
M8007C1 DATA_RB_STP_COMP
L2 UL Allocation + TA (triggered in target cell)

Path Switch Request
UP Update Request
GTP-U end marker
DL Data (target eNodeB)
UP Update Response
Path Switch Request Ack
X2AP UE Context Release UL/DL Data (target eNodeB)
UE Ctx release M8014C7 SUCC_INTER_eNodeB_HO
For internal use

Inter eNodeB Handover KPI
Total Success Rate
Formula LTE_5058b: (NetAct names)
• 100*sum(SUCC_INTER_eNodeB_HO) / sum(INTER_eNodeB_HO_PREP)
• M8014C7 SUCC_INTER_eNodeB_HO = the reception of a X2AP: Release Resource message

sent by the target eNodeB
• M8014C0 INTER_eNodeB_HO_PREP = the transmission of an X2AP: Handover Request to the
target eNodeB.
For internal use

Negative 1, Preparation


M8014 Inter eNodeB Handover Measurements, triggered in source cell
inter-eNodeB
Handover
decision
Admission control and resources allocation

failure in target eNodeB (RAC+TAC)
M8014C3 FAIL_eNodeB_HO_PREP_AC
X2AP Handover Preparation Failure
For internal use


inter-eNodeB M8014 Inter eNodeB Handover Measurements, triggered in

Handover source cell
decision
Timer tX2RelocPrep
M8014C2 FAIL_eNodeB_HO_PREP_TIME
tX2RelocPrep expiry
X2AP Handover Cancel
For internal use


M8014 Inter eNodeB Handover Measurements, triggered in source
cell
inter-eNodeB
Handover
decision
M8014C5 FAIL_eNodeB_HO_PREP_OTHER
All other failure causes
For internal use

Negative 1, Execution
Target
Source
UE eNodeB MME SGW
eNodeB
X2AP Handover Request Ack

E
X2AP Status Transfer HER
E
PRACH Msg1 (ded. preamble)
HER
W
L2 UL Allocation + TA ME
E SO
LUR
I
FA Path Switch Request
UP Update Request
Timer TX2RELOCoverall GTP-U end marker
M8014C8
UP Update Response
INTER_eNodeB_HO_FAIL Path Switch Request Ack
No X2AP UE Context Release received
 TX2RELOCoverall expires UL/DL Data (target eNodeB)
S1AP UE Context Release Request
UE Ctx release
For internal use
Negative 2, Execution


M8007C2 DATA_RB_STP_FAIL
Timer TX2RELOCexec
TX2RELOCexec expiry since no RRC Conn

Reconfiguration Complete received in target cell Counter triggered in target cell
For internal use

Negative 1, Generic
inter-eNodeB
Handover
decision

RRC Conn Re-Establishment Request (received at any time during preparation or execution)
M8021C21 MRO_EARLY_TYPE1_HO
Triggered if re-est cause is ”HO failure”
No counter for X2AP Handover Cancel

For internal use
Negative 2, Generic


UE attempts to S1AP UE Context Release Command or S1AP Reset

access target
cell (received at any time during preparation or execution)
No counter for X2AP Handover Cancel
For internal use

LTE533: Mobility Robustness
Feature
• LTE533 Mobility Robustness includes counters and Optimizer algorithms for fixing HO problems.
• Failure events are detected by RRC Connection Re-Establishment
• Too late HO
• Too Early HO type I
• Too Early HO type II
• Can be visualised in Optimizer or analyze the counters directly
• LTE_5174a E-UTRAN Number of Late HO Events
• LTE_5175a E-UTRAN Number of Type 1 Early HO Events
• LTE_5176a E-UTRAN Number of Type 2 Early HO Events
• Can help optimizing neighbours and basic RF
• MRO related counters
• M8015C16 LTE_Neighb_Cell_HO MRO_LATE_HO_NB
• M8015C17 LTE_Neighb_Cell_HO MRO_EARLY_TYPE1_HO_NB
• M8015C18 LTE_Neighb_Cell_HO MRO_EARLY_TYPE2_HO_NB
• M8021C20 LTE_Handover MRO_LATE_HO
• M8021C21 LTE_Handover MRO_EARLY_TYPE1_HO
• M8021C22 LTE_Handover MRO_EARLY_TYPE2_HO
For internal use

LTE533: Too Late Handover
Feature
• Too late HO : Suitable HO target candidate is reported by UE too late, or not at all.
– UE stays too long in HO source cell – degrading cell quality enforces radio link failure on UE
side
– UE re-establishes connection to another cell
– Could indicate missing neighbours
RLF at UE side
(detected at cell A)
T310 T311
RL problem at UE side RRCConnectionReestablishmentRequest cause UE

(detected at cell A) ”other” sent to cell B
Cell B sends X2AP RLF INDICATION msg to
cell A
Counters:
M8021C20 MRO_LATE_HO
Incremented in cell A
For internal use

LTE533: Too Early Handover Type I
Feature
• Too early HO Type I : HO triggered too early , UE tries to re-establish to source cell
– UE tries to enter too early the HO target cell – insufficient cell quality enforces HO failure or
radio link failure right after HO completion
– UE re-establishes connection to HO source cell again
cause ”HO Failure” sent to cell A
HO procedure start HO failure
from cell A at UE side
T304 T311
UE
Counters:
Incremented in cell A
For internal use
LTE533: Too Early Handover Type II
Case A
• Too early HO Type II case A : Handover is triggered is reported by UE too early

– UE enters too early the HO target cell – insufficient cell quality enforces HO failure or radio link
failure right after HO completion
– UE tries to re-establish connection to a third cell
RRCConnectionReestablishmentRequest sent
to cell C
HO procedure start Successful
from cell A HO to cell B
tStoreUeCntxt timer
UE
Counters: cell C sends X2AP HO REPORT
M8021C22 MRO_EARLY_TYPE2_HO to cell B
Incremented in cell B
For internal use

LTE533: Too Early Handover Type II
Case B
• Too early HO Type II case B example: is reported by UE too early.

– Handover is triggered and target cell receives PRACH preamble, but does not receive RRC
Reconfiguration Complete.
– UE re-establishes connection to a third cell
RRCConnectionReestablishmentRequest sent
Successful to cell C
HO procedure start PRACH phase
from cell A Missing RRC Reconfig
to cell B
Complete in cell B
UE
cell C sends X2AP HO REPORT
to cell B
Counters:
Incremented in cell B
For internal use

Content
• Introduction
• KPIs:
• Summary

For internal use
Parameters related to drop calls
• Wrong parameter configuration can increase the call drop rate significantly
• For handover access related drops, the PRACH phase in target cell should be optimized. See call
setup optimization material in this training.
• Prolonging UE and eNodeB initiated drop timers and constants may improve probability of recovery
• Missing neighbors result in UL interference and user-perceived coverage gaps in the network 
drops
• The best way to improve retainability is to optimize basic physical RF: improve coverage and
cell dominance!!! “Can’t fix bad RF with parameters (except by fixing missing neighbors).”
For internal use

MO parameter full name parameter short name description value range PDDB default
Indicates the maximum number of HARQ
transmissions in UL that is configured for
Maximum number of each UE at initial access to a specific cell.
LNCEL harqMaxTrUl 1...7, step 1 5
HARQ transmission in UL NOTE: this parameter also defines
number of transmissions in PRACH
handover access.
Indicates the maximum number of HARQ
Maximum number of
LNCEL harqMaxTrDl transmissions in DL that is configured for 1...16, step 1 3
HARQ transmission in DL
each UE at initial access to a specific cell.
This is the maximum number of
n1 (0), n2 (1), n3 (2), n4
Maximum number of out- consecutive "out of sync" indications
LNCEL n310 (3), n6 (4), n8 (5), n10 -
of-sync indications received from lower layers.
(6), n20 (7)
n1 corresponds to 1 and so on.
Maximum number of consecutive "in-
n1 (0), n2 (1), n3 (2), n4
Maximum number of in- sync" indications received from lower
LNCEL n311 (3), n5 (4), n6 (5), n8 (6), -
sync indications layers.
n10 (7)
n1 corresponds to 1 and so on.
0ms (0), 50ms (1), 100ms
Timer T310 supervises the recovery from (2), 200ms (3), 500ms
LNCEL Timer T310 t310 -
physical layer problems. (4), 1000ms (5), 2000ms
(6)
1000ms (0), 3000ms (1),
5000ms (2), 10000ms
Timer T311 supervises the RRC
LNCEL Timer T311 t311 (3), 15000ms (4), -
connection re-establishment.
20000ms (5), 30000ms
(6)
For internal use
50ms (0), 100ms (1),
Timer T304 supervises the successful 150ms (2), 200ms (3),
LNCEL Timer T304 intra-LTE t304IntraLte 1000ms (5)
completion of a handover or cell change. 500ms (4), 1000ms (5),
2000ms (6)
Determines the number of subframes after

500 (0), 750 (1), 1280 (2),
which a UE assumes it is out-of-sync in UL
LNCEL Time alignment timer taTimer 1920 (3), 2560 (4), 5120 10240 (6)
if no Time Alignment command was
(5), 10240 (6)
received.
The parameter defines lead with respect to

the taTimer expiration time for starting to 0...2560 subframes, step 1
LNCEL Time alignment timer margin taTimerMargin 2000 subframes
send the periodic timing advance subframes
command.
The number of times the timing advance

Maximum number of time command is retried before the LTE MAC
LNBTS taCmdMaxRetry 1...10, step 1 10
alignment command retries assumes that the UE has gone out-of-
synch. This parameter is vendor-specific.
Determines which UEs shall be actively

sent to UL out-of-sync state provided that
bearer combination and applied DRX
profile allows for this.
extendedDrxOnly: only UEs being
configured with extended settings for the extendedDrxOnly (0),
LNCEL Apply UL out-of-sync state applyOutOfSyncState extendedDrxOnly (0)
long DRX cycle allDrx (1), allUEs (2)
allDrx: all UEs being configured for DRX
provided that applied DRX profile allows
allUEs: all UEs independently of DRX
configuration provided that bearer
combination allows.
For internal use

The parameter defines the number of
Radio problem consecutive CQI DTX detections causing radio
LNBTS indication based on nCqiDtx link failure indication. Special value 0 means 0...100, step 1 50
CQI DTX that the feature is disabled.
The parameter is vendor-specific.
The parameter defines number of consecutive
Radio problem
CQI non-DTX detections causing radio link
LNBTS recovery based on nCqiRec 1...8, step 1 2
failure recovery indication.
CQI DTX
The parameter is vendor-specific.
Defines the number of consecutive uplink data
receptions on PUSCH without DTX detection
Number of PUSCH
before the radio link problems are assumed to
LNBTS detections to end radio rlpDetEndNUl 1...20, step 1 3
be over and an indication about radio link
link problem
recovery is sent to higher layers. This
parameter is vendor-specific.
This parameter determines the number DL
PDSCH transmission with correct HARQ
Number of successful
LNBTS rlpDetEndNoDl feedback until detected radio link problems are 1...20, step 1 3
PDSCH transmissions
assumed to be over. This parameter is vendor-
specific.
Defines the number of uplink DTX detections on
Number of PUSCH
PUSCH before an indication about radio link
LNBTS DTX detections for rlpDetMaxNUl 1...1000, step 1 1000
problems is sent to higher layers. This
radio link problem
parameter is vendor-specific.
This parameter determines the maximum
Number of failed number of failed DL PDSCH transmission
LNBTS rlpDetMaxNoDl 1...1000, step 1 1000
PDSCH transmissions attempts until radio link problems are detected.
This parameter is vendor-specific.
For internal use

This parameter determines the maximum

number of failed DL PDSCH transmission
Number of failed PDSCH
LNBTS rlpDetMaxNoDl attempts until radio link problems are 1...1000, step 1 1000
transmissions
detected. This parameter is vendor-
specific.
Defines the time frame for uplink DTX

detections on PUSCH before an indication
Time of PUSCH DTX about radio link problems is sent to higher
LNBTS detections for radio link rlpDetMaxTUl layers. This parameter is vendor-specific. 20...5000 ms, step 1 ms 0 ms
problem
IMPORTANT: The parameter cannot have
a value other than 0.
Determines the timeframe for failed DL

Timeframe for failed PDSCH PDSCH transmission attempts until radio
LNBTS rlpDetMaxTimeDl 20...5000 ms, step 1 ms 5000 ms
transmissions link problems are detected. This parameter
is vendor-specific.
For internal use

Content
• Introduction
• KPIs:
• Summary

For internal use
Features relevant to drops
RL30/40 & RL25TD/35TD/45TD
• Mobility Robustness LTE533 - RL30/RL35TD
• Inter-RAT PS handover to WCDMA LTE56 - RL30/RL25TD
• ANR Intra-LTE, Intra-frequency Fully UE based LTE782 - RL30/RL25TD
• ANR Inter-RAT with O&M LTE783 & LTE784 & LTE510 - RL30/RL25TD
• ANR Optimization of Intra-LTE neighbor relations LTE 771 - RL30/RL25TD
• RRC Connection Re-Establishment LTE735 - RL30/RL25TD
• SRVCC to WCDMA LTE 872 –RL40/RL45TD
• SRVCC to GSM LTE 873 – RL40/RL45TD
Feature
Feature parameter
parameter details
details in
in the
the Radio
Radio Wiki:
Wiki:
• Smart Admission Control LTE497 –RL 40/RL35TD
NPO features and References
NPO features and References
• ARP based admission Control LTE534 –RL40/RL35TD
• IRC for 2 RX Paths LTE979 RL40/- no TDD
• RSRQ based cell reselection LTE1036 – RL50/RL35TD
• RSRQ based redirect LTE1407 –RL50/RL35TD
• Intra cell HO LTE511- RL 50/RL45TD
• IRC for 4RX paths LTE980 –RL 50/- no TDD
For internal use

Content
• Introduction
• KPIs:
• Summary

For internal use
Case Study 1:
Call Drop due to Handover Failure : Tx2RelocOverall Timer Expiry
For internal use

UE Log: Handover to Target Cell (PCI: 29)
• UE received RrcConnection-
Reconfiguration (handover
command) for target cell: PCI 29.
• UE completed the contention-free
random access to the target cell
(preamble id = 45) by receiving
Random Access Response (RACH
RSP) from eNodeB and sent
RrcConnection
ReconfigurationComplete message
to eNodeB.
For internal use

UE Log: Radio Conditions
For internal use

BTS Log: Source Cell (PCI=71) Mon_0008_13.emil
tx2relocoverall
tx2relocoverall timer=
timer= 5.35s
5.35s
• RLC layer detected issue on DL data acknowledgements and triggered RLC retransmissions until
maximum number of retransmissions (16) were reached.
- The UE context release was initiated by eNodeB on a source cell with cause: tx2relocoverall-expiry
(tx2relocoverall=T304max+T311+T301+ tx2relocoverallDelta = 5350ms).
For internal use

BTS Log: Target Cell (PCI=29)
Mon_000E_95.emil
• The UE receives successfully random access response from a target cell (C-RNTI=22729) but
RrcConnectionReconfigurationComplete message (Msg3) was never received for some reason (e.g.
interference or poor uplink coverage) by a target cell and thus, the handover was not further proceeded.
For internal use

Inter-eNodeB X2 Handover – Message Flow
Handover command for

target cell: PCI 29
No RRC reconfiguration
MaxRlcRetrans Exceeded in a complete message received
source cell in a target cell.
Tx2RelocOverall timer
expires
For internal use

UE Log: Random Access for UL Data Arrival
• The eNodeB had already released RRC

connection and stopped scheduling the
UE.
• However, UE never received

RrcConnectionRelease message and
thus, the random access procedure
was initiated due to UL data arrival.
• The UE keeps sending the requests
until max. preamble retransmissions
(10) reached.
For internal use

UE Log: RRC Connection Re-establishment
• After the failed random access

procedure, RRC connection re-
establishment was initiated by UE to
the target cell.
• However, RRC connection re-

establishment was rejected by the
eNodeB because the UE context was
earlier released due to incomplete
handover.
For internal use

Radio Link Failure
normal operation Attempting PRACH to serving cell no recovery during T311 goes back to idle
radio link failure

Random Access triggered
due to UL data arrival. UE attempting RRC connection re-
random access to establishment attempted to
serving cell. serving cell during t311 but
eventually eNodeB rejected the
RRC re-establishment
RACH failure
For internal use

Case Study 2:
Call Drop due to Handover Cancel – Tx2RelocPrep Timer Expiry
For internal use

UE Log: Multiple Measurement Reports from UE
• UE triggers multiple measurements

reports for handover (event A3) but no
response from eNodeB.
For internal use

BTS Log: Source Cell (PCI = 124) Mon_00F6_29112.e
mil
• The source eNodeB sends multiple X2AP: HANDOVER REQUEST messages but target eNodeB does not
respond with X2AP: HANDOVER ACKNOWLEDGE and thus, after the expiry of tX2RelocPrep timer
(500ms) the X2AP: HANDOVER CANCEL procedure is started.
For internal use
Inter-eNodeB X2 Handover
Message Flow
No
No Handover
Handover Request
Request
Acknowledge
Acknowledge from
from
target
target eNodeB,
eNodeB, i.e.
i.e.
HO cancel handover preparation
handover preparation
fails
fails
For internal use

Case Study3:
Call Drop due to Handover Failure: No Path Switch Request ACK from MME
For internal use

UE log: RRC Connection Release
• The message: rrcConnectionRelease was sent by eNodeB to release the call after UE successfully
handover from PCI:56 (Suhun1A1) to PCI:4 (Suhun1A0).
For internal use

BTS Log: No PathSwitchRequest ACK from MME
tx2reloccomp
tx2reloccomp timer
timer =
= 0.5s
0.5s
• No S1AP:PathSwitchRequestACK message response from MME, so after expiration of timer

tx2relocccomp (= 500ms) the target eNodeB initiated UE context release procedure to release the
resource in both source eNodeB by sending X2AP:UEContextRelease and target eNodeB by sending
RrcConnectionRelease to UE for release the call.
For internal use
BTS Log: No PathSwitchRequestAck from MME
tx2reloccomp
tx2reloccomp timer
timer =
= 2s
2s
• The timer tx2reloccomp setting was changed to 2000ms (max. value) in order to allow more time for MME
for path switch but it failed as well.
For internal use

Inter-eNodeB X2 Handover – Message Flow
After
After the
the target
target eNodeB
eNodeB
sent
sent “Path Switch
“Path Switch Request”
Request”
message
message to to MME,
MME, then
then
eNodeB
eNodeB expects
expects to
to receive
receive
a message “ Path Switch
a message “ Path Switch
Request
Request Acknowledge”
Acknowledge”
back
back from
from MME
MME within
within
timer
timer Tx2RELOCcomp.
Tx2RELOCcomp. If If
this timer expires, the
this timer expires, the
eNodeB-initiated
eNodeB-initiated context
context
release
release procedure
procedure isis
started.
started.
For internal use

Case Study 4:
Missing Neighbor: RRC Release with Redirect to eHRPD
For internal use

UE Log: Low Serving Cell RSRP
For internal use

UE Log: RRC Release with Redirect to eHRPD
- UE is sending consecutive
measurement reports until
RrcConnectionRelease is received
from eNodeB.
- The event A2 is triggered: RSRP 27
(-113 dBm) < threshold4 (-110
dBm)
For internal use

/
BTS Log: RRC Connection Release
• The UE sends measurement reports but the eNodeB doesn’t react to them (i.e. it doesn’t start the HO
preparation) because the PCI=168 in the measurement report is not configured as eNodeB neighbour.
For internal use

Case Study 5:
Call Drop due to Radio Link Failure: PuschRlf & CqiRlf
For internal use

UE Log: Intra-eNodeB Handover
• The intra-eNodeB handover to a target

cell (PCI 356) was successfully
completed.
For internal use

BTS Log: Target Cell (PCI:356)
• The handover was completed in a target cell (C-RNTI= 14248) by receiving RRC connection reconfiguration complete
message from UE.
• However, UE initiates random access for scheduling requests.
For internal use
UE Log: Random Access for Scheduling Request
• The UE stops receiving an UL grants

(e.g. insufficient power for PUCCH-SR)
and thus, after the time dSrTransMax *
cellSrPeriod = 64*10 = 640 ms is
reached, UE releases PUCCH
resources and performs the scheduling
request via random access (RA-SR).
For internal use

UE Log: Random Access for Scheduling Request
• The eNodeB detects RA-SR from UE

and sends the RRC message
RrcConnection-Reconfiguration to
inform the UE regarding SR and CQI
reconfiguration on PUCCH.
For internal use

BTS Log: eNodeB Detected RLF – PuschRlf
• The eNodeB detects uplink DTX on PUSCH and indicates radio link problems to higher layers, i.e.
PuschRlf_ON.
• The detection of the radio link problem by the uplink scheduler is based on the comparison of grant
assignment and the DTX detection on PUSCH for the assigned PRBs. The detection shall take into
account the DTX PUSCH indication provided by the physical layer.
• This could occur due to insufficient UE Tx power for PUSCH. The uplink power control parameter for
PUSCH may need to be adjusted.
For internal use
BTS Log: eNodeB Detected RLF – CqiRlf
• The eNodeB supports CQI DTX detection for periodic CQI reports on PUCCH and PUSCH .
• The CqiRlf_ON indicates the number of consecutive CQI DTX detections causing radio link failure.
• This could occur due to insufficient UE tx power for CQI reports on PUSCH. The parameter puschCqiOffI
may need to be adjusted based on CQI misdetection on eNodeB or dFpucchF2 for carrying CQI reports
on PUCCH.
For internal use

UE Log: RRC Connection Re-establishment Reject
• Eventually, the RRC connection re-establishment is triggered by UE due to radio link failure because UE
never received RrcConnectionRelease from eNodeB.
• The UE context was earlier released by eNodeB with cause: radio-connection-with-ue-lost and thus, the
request was rejected by eNodeB.
For internal use

Project Examples
• Following project related material is available in IMS:
- US Market: LTE Performance Analysis

• Refer to section: LTE OSS Failure Counter Analysis
For internal use

Content
• Introduction
• KPIs:
• Summary

For internal use
Links to relevant material
• MBB PL KPI Bench marking tool (for KPI target values):

- https://alpaca.emea.nsn-net.net/Alpaca/Account/Login?ReturnUrl=/Alpaca/
• LTE Project Uploads:
- https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/383538041
• LTE feature Testing Materials in IMS:
- https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/505235702
• Radio wiki for more details:
- https://workspaces.emea.nsn-net.net/sites/nporadio/Radio%20Wiki/Home.aspx
• JUMP:
- http://nop-i.nokiasiemensnetworks.com/pl_login.php?dst=L2xuYnRzX2ZwLnBocA
• IMS link to this material:
- https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D506699937
For internal use

Call Drop Optimization: Last Updated: November, 2013

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Call Drop Optimization: Last Updated: November, 2013

Uploaded by

Copyright:

Available Formats

Call Drop Optimization

Last Updated: November, 2013

For internal use

• Impact of different Features

• UE Detected Radio Link Failures (RLF)

• Impact of different Features

LTE_5043a E-UTRAN Total HO Success Ratio, intra eNodeB

For internal use

LTE_5025: eRAB Drop Ratio %

NSN Recommended values : LTE_5025< 0.3%,

Example KPI analysis

• Impact of different Features

For internal use

1. upon T310 expiry

• The UE sends, for the initiation of the procedure, an integrity checked

For internal use

• The eNodeB checks whether it still has a valid UE:

- in a source cell which becomes the serving cell or

• The eNodeB sends RRCConnectionReestablishment response to the UE for resuming

• NOTE: if UE is in RRC_CONNECTED while RRC security is not active, UE goes to

For internal use

RRC Re-Est triggered. UE makes cell reselection and sends Re-Est.

RRC Conn Re-Est can only succeed in a cell that has:

Message Sequence Chart:

For internal use

RRC Re-Est triggered. UE makes cell reselection and sends Re-Est.

Cell reselection + TAU Req

For internal use

Message Sequence Chart:

For internal use

Packet data Packet data

Source C-RNTI, target short

Handover Request User Data MAC-I and source PCI sent

Deliver buffered and in

Packet data Packet data

For internal use

For internal use

First Phase Second Phase

radio link failure

For internal use

First Phase Second Phase

radio link failure

For internal use

First Phase Second Phase

radio link failure

RRC Conn ReConf T304 running Cell reselection

from RRC Connection Reconfiguration:

For internal use

First Phase Second Phase

radio link failure

- UE sets the reestablishmentCause as follows:

For internal use

Following parameters are related to RLF detection and recovery:

Parameters Range Description Setting

This is the maximum number of consecutive "out of

Maximum number of consecutive "in-sync" indications received from lower

Timer T304 supervises the successful completion of a handover or cell change. If

For internal use

Following parameters are related to RLF detection and recovery:

0ms (0), 50ms (1), 100ms (2),

For internal use

• Impact of different Features

For internal use