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
- Re
Reas
ason
ons
s for
for Dr
Drop
op Cal
alll
This module is for Call drops after
• KPIs: setup phase only. Connection
setup is discussed in Call Setup
- Im
Impo
port
rtan
antt KPIs
KPIs/C
/Cou
ount
nter
ers
s
Optimization Module
- Targ
arget
et valu
valueses and
and NSN
NSN and Proj
Project
ect Refe
Referen
rences
ces

• Optimization actions/analy
actions/analysis sis
- UE initiated
initiated Drop CallCall analysi
analysis:
s: signalli
signalling
ng flows
flows and
and counter
counter triggeri
triggering
ng
- eNode
eNodeB B initiated
initiated Drop
Drop Call
Call analysis:
analysis: signall
signalling
ing flows
flows and counte
counterr triggering
triggering
- Dr
Drop
op Cal
Calll coun
counteterr trig
trigge
gersrs
- Han
Handov
dover
er rel
relate
ated
d Dro
Drop p Cal
Calll anal
analysi
ysis
s
• Summary
- Pos
Possib
sible
le Obse
Observa
rvatio
tions
ns and
and recom
recommen
mendatdation
ions s
- Pa
Para
rame
meteters
rs in
inv
vol
olve
ved d

• 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
3 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 Content
• Introduction
- Reasons for Drop Call

• KPIs:
- Important KPIs/Counters
- 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
4 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 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 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 –
eNodeB – visible to NSN user)
LTE_5575a E-UTRAN Total E-RAB Active Time
Note: For non-GBR data services can be
LTE_5576a E-UTRAN E-RAB Active Time QCI1
high because always-on services may keep
LTE_5577a E-UTRAN E-RAB Active Time QCI2 UE all the time in RRC-Connected mode. A
LTE_5578a E-UTRAN E-RAB Active Time QCI3 very small number of drops can result in high
LTE_5580a E-UTRAN E-RAB Active Time nonGBR drop ratio. For example, when user removes
UE from laptop this results in a E-RAB drop
M8008C0 REJ_RRC_CONN_RE_ESTAB (Counter)
For internal use
5 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 List of important KPIs
Handover Related

LTE_5043a E-UTRAN Total

Total HO Success Ratio, intra eNodeB
LTE_5035a E-UTRAN HO Success Ratio, intra eNodeB
LTE_5058b E-UTRAN Total
Total HO Success Ratio, inter eNodeB X2 based
LTE_5048b E-UTRAN HO Success Ratio, Inter eNodeB X2 based
LTE_5084a E-UTRAN Total
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

6 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 KPI Targets and reference values Internal Use only!!
onl y!!

LTE_50
TE_5025:
25: eRAB Drop Ratio %

NSN Recommended values : LTE_5025

TE_5025<< 0.3%,
Up to date
dat e NSN recommended values can be found in KPI Benchmarker Tool
Tool (apply the access rights
through the tool):
https://alpaca.emea.nsn-net.net/Alpaca/Account/Login?ReturnUrl=/Alpaca/
For internal use
7 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 EPS Bearer Connection Establishment
EPS Bearer
Success Connection
Ratio, Release Establishment
Ratio & Attempts
Scope:

Success Ratio, Release Ratio & Attempts • KPI LTE_5017A describes the setup success ratio
of the elementary E-RAB setup procedure used
to setup the E-RAB between MME and UE
• Note: It indicates the E-UTRAN contribution to
network accessibility for the end-user, not the
whole end-to-end service accessibility.

Observation:
• The majority of EPS Bearer connection
establishments problems (if RRC SR is good)
indicate the transport or the core network issues
• E-RAB drop ratio depends on RRC inactivity timer 
• 3GPP recommends normalizing drops by time
(drops per minute) for non-GBR bearers

NSN Recommendation
Core network KPIs need to be analyzed for further
problem isolation
Example KPI analysis
For internal use
8 ©2013 Nokia Solutions and Networks. All rights reserved.
 EPS Bearer Connection Establishment
EPS Bearer Connection Establishment
Success Ratio, Release Ratio & Attempts
E-RAB Drop Ratio, Attempts
Scope:
• KPI LTE_5025d describes E-RAB Drop ration with
out pre-emptions (RAN point of view)
.

Observation:
• The majority of EPS Bearer connection
establishments problems (if RRC SR is good)
indicate the transport or the core network issues
• E-RAB drop ratio depends on RRC inactivity timer 
• 3GPP recommends normalizing drops by time
(drops per minute) for non-GBR bearers

NSN Recommendation
Core network KPIs need to be analyzed for further
problem isolation

Example KPI analysis

For internal use
9 ©2013 Nokia Solutions and Networks. All rights reserved.
 Content
• Introduction
- Reasons for Drop Call

• KPIs:
- Important KPIs/Counters
- 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
10 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 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

11 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 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

12 ©2013 Nokia Solutions and Networks. All rights reserved.
 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 wi th 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

13 ©2013 Nokia Solutions and Networks. All rights reserved.
 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 Q out 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 f inal numerical values have not been agreed in the specification.

For internal use

23 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 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

        c         c         c         c         c         c         c         c        c        c        c
        n         n         n         n         n         n         n         n
       y        y        y        y        y        y        y        y        n        n        n
        s         s         s         s         s         s         s         s        y        y        y
     -      -      -      -      -      -      -      -        s        s        s
          t           t           t           t           t           t           t           t      -      -      -
       u        u        u        u        u        u        u        u        n        n        n
        o         o         o         o         o         o         o         o          i          i          i

10%

2%

time
>10ms

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
24 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 2. RLF due to maximum UL RLC Retransmission reached

First Phase Second Phase

normal operation RLC retransmissions until max value no recovery during T311 goes back to idle

RRC_CONNECTED RRC_IDLE

radio link failure

RLC retransmissions Cell reselection
until max RLC retx and Tracking Area
threshold is reached RRC connection re-
Update if RRC
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 UE initiates the RRC connection re-establishment procedure
pollPDU : p32
pollByte : kB25
maxRetxThreshold : t8

For internal use

25 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 3. RLF due to HO failure

First Phase Second Phase

normal operation Attempting PRACH to target cell no recovery during T311 goes back to idle

RRC_CONNECTED RRC_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

26 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 4. RLF due to non-HO random access failure

First Phase Second Phase

normal operation Attempting PRACH to serving cell no recovery during T311 goes back to idle

RRC_CONNECTED RRC_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
27 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 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

28 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 1. PUSCH RLF: RlsCause_PuschRlf_ON
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

39 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 1. PUSCH RLF: RlsCause_PuschRlf, counter-based RLF detection example
RLF timer running

T_RLF = T310 + T311

vendor-file parameters
in this example:
<p name="rlpDetMaxNUl">3</p>
<p name="rlpDetEndNUl">2</p>
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

40 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 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 report s 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 does not apply to aperiodic CQI report on PUSCH
For internal use
41 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 2. Periodic CQI RLF: RlsCause_CqiRlf 
Example

T_RLF = T310 + T311

RLF timer running

CQI_RLF time
ON
LNCEL/cqiPerNp=10ms CQI_RLF
OFF
vendor-file parameters in this example:

<p name="nCqiDtx">6</p>
<p name="nCqiRec">1</p>
For internal use
42 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 Emil example

Example of
UL Problems

For internal use

43 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 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.

• Setting rlpDetMaxNoDL=0 switches off counter-based radio problem detection.

• If both counter-based and time-based options are disabled, radio problem detection based on UL
For internal use
44  Ack/Nack is disabled
Presentation completely.
/ Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 MME initiated Transaction to ECM-Idle state
Normal procedure

For internal use

82 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 eNodeB initiated Transition to ECM-IDLE
Normal procedure

For internal use

83 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 MME initiated Transaction to ECM-Idle state
 Abnormal procedure

For internal use

84 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 eNodeB initiated Transaction to ECM-IDLE
 Abnormal procedure

For internal use

85 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 Transaction to ECM-Idle State Due to Reset on S1
 Abnormal procedure

For internal use

86 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 Content
• Introduction
- Reasons for Drop Call

• KPIs:
- Important KPIs/Counters
- 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
87 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 Intra eNodeB Handover 
Negative 4

UE Source cell Target cell MME SGW

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

94 ©2013 Nokia Solutions and Networks. All rights reserved.
 Intra eNodeB Handover
Handover Preparation Failure (Counter Update)

For internal use

95 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 Intra eNodeB Handover
Handover Execution Failure (Counter Update)

For internal use

96 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 Inter eNodeB Handover 
Positive, preparation

UE Source eNodeB Target eNodeB MME SGW

Measurement configuration
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)
w/ mobilityControlInfo IE

For internal use

97 ©2013 Nokia Solutions and Networks. All rights reserved.
 Inter eNodeB Handover  M8014 Inter eNodeB Handover
Measurements, triggered in source cell
Positive, Execution
Source Target
UE eNodeB eNodeB MME SGW

RRC Conn Reconfiguration

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)

RRC Conn Reconfig Complete

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

98 ©2013 Nokia Solutions and Networks. All rights reserved.
 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

99 ©2013 Nokia Solutions and Networks. All rights reserved.
 Inter eNodeB Handover 
Negative 1, Preparation

UE Source eNodeB Target eNodeB MME SGW

Measurement configuration
UL/DL Data (source eNodeB)

RRC Measurement Report

M8014 Inter eNodeB Handover Measurements, triggered
triggered in source
inter-eNodeB cell
Handover
decision

X2AP Handover Request

 Admission control and resources allocation

allocation
failure in target eNodeB (RAC+TAC)
M8014C3 FAIL_eNodeB_HO_PREP_
FAIL_eNodeB_HO_PREP_AC
AC

X2AP Handover Preparation Failure

For internal use

100 ©2013 Nokia Solutions and Networks. All rights reserved.
 Inter eNodeB Handover 
Negative 2, Preparation

UE Source eNodeB Target eNodeB MME SGW

Measurement configuration
UL/DL Data (source eNodeB)

RRC Measurement Report

inter-eNodeB M8014 Inter eNodeB Handover Measurements,

Measurements, triggered in
Handover source cell
decision
X2AP Handover Request

Timer tX2RelocPrep
Timer tX2RelocPrep
M8014C2 FAIL_eNodeB_HO_PREP_TI
FAIL_eNodeB_HO_PREP_TIME
ME

tX2RelocPrep expiry
X2AP Handover Cancel
For internal use
101 ©2013 Nokia Solutions and Networks. All rights reserved.
 Inter eNodeB Handover 
Negative 3, Preparation

UE Source eNodeB Target eNodeB MME SGW

Measurement configuration
UL/DL Data (source eNodeB)

RRC Measurement Report

M8014 Inter eNodeB Handover Measurements,
Measurements, triggered in source
source
cell
inter-eNodeB
Handover
decision
X2AP Handover Request

M8014C5 FAIL_eNodeB_HO_PREP_OT
FAIL_eNodeB_HO_PREP_OTHER
HER
 All other failure causes
causes
X2AP Handover Cancel

For internal use

102 ©2013 Nokia Solutions and Networks. All rights reserved.
 Inter eNodeB Handover 
Negative 1, Execution
Target
Source
UE eNodeB MME SGW
eNodeB
X2AP Handover Request Ack

RRC Conn Reconfiguration

DL Data (target eNodeB)
w/ mobilityControlInfo IE
X2AP Status Transfer 
PRACH Msg1 (ded. preamble)
L2 UL Allocation + TA
RRC Conn Reconfig Complete
Path Switch Request
UP Update Request
Timer TX2RELOCoverall  GTP-U end marker 
DL Data (target eNodeB)
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
103 ©2013 Nokia Solutions and Networks. All rights reserved.
 Inter eNodeB Handover 
Negative 2, Execution

UE Source eNodeB Target eNodeB MME SGW

X2AP Handover Request Ack

RRC Conn Reconfiguration

w/ mobilityControlInfo IE

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

104 ©2013 Nokia Solutions and Networks. All rights reserved.
 Inter eNodeB Handover 
Negative 1, Generic

UE Source eNodeB Target eNodeB MME SGW

inter-eNodeB
Handover
decision
X2AP Handover Request

X2AP Handover Request Ack

RRC Conn Reconfiguration

w/ mobilityControlInfo IE

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”

X2AP Handover Cancel

No counter for X2AP Handover Cancel

For internal use
105 ©2013 Nokia Solutions and Networks. All rights reserved.
 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 E vents
• 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

107 ©2013 Nokia Solutions and Networks. All rights reserved.
 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

108 ©2013 Nokia Solutions and Networks. All rights reserved.
 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

RRCConnectionReestablishmentRequest
cause ”HO Failure” sent to cell A
HO procedure start HO failure
f rom cell A at UE side
T304 T311

UE

Counters:
M8021C21 MRO_EARLY_TYPE1_HO

Incremented in cell A
For internal use
109 ©2013 Nokia Solutions and Networks. All rights reserved.
 Content
• Introduction
- Re
Reas
ason
ons
s for
for Dr
Drop
op Cal
alll

• KPIs:
- Im
Impo
port
rtan
antt KPIs
KPIs/C
/Cou
ount
nter
ers
s
- Targ
arget
et valu
valueses and
and NSN
NSN and Proj
Project
ect Refe
Referen
rences
ces

• Optimization actions/analy
actions/analysis sis
- UE initiated
initiated Drop CallCall analysi
analysis:
s: signalli
signalling
ng flows
flows and
and counter
counter triggeri
triggering
ng
- eNode
eNodeB B initiated
initiated Drop
Drop Call
Call analysis:
analysis: signall
signalling
ing flows
flows and counte
counterr triggering
triggering
- Dr
Drop
op Cal
Calll coun
counteterr trig
trigge
gersrs
- Han
Handov
dover
er rel
relate
ated
d Dro
Drop p Cal
Calll anal
analysi
ysis
s
• Summary
- Pos
Possib
sible
le Obse
Observa
rvatio
tions
ns and
and recom
recommen
mendatdation
ions s
- Pa
Para
rame
meteters
rs in
inv
vol
olve
ved d

• Impact of different Features

• Project examples
• Links to further material
For internal use
118 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 Features relevant to drops
RL30/40 & RL25TD/35TD/45TD

• Mobility Robustness LTE533 - RL30/RL35TD

• Inter-RAT PS handover
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
relations LTE 771 - RL30/RL25TD
• RRC Connection Re-Establishment LTE735 - RL30/RL25TD
• SRVCC to WCDMA LTE 872 –
872 –RL40/RL45TD
RL40/RL45TD
• SRVCC to GSM LTE 873 –
873 – RL40/RL45TD Feature parameter details in the Radio Wiki: NPO
• Smart Admission Control LTE497
LTE497 –
 –RL
RL 40/RL35TD features and References
•  ARP based admission Control LTE534 –
LTE534 –RL40/RL35TD
RL40/RL35TD
• IRC for 2 RX Paths LTE979 RL40/-
RL40/- no TDD
• RSRQ based cell reselection LTE1036 –
LTE1036 – RL50/RL35TD
• RSRQ based redirect LTE1407 –
LTE1407 –RL50/RL35TD
RL50/RL35TD
• Intra cell HO LTE511- RL 50/RL45TD
• IRC for 4RX paths LTE980 –
LTE980 –RL
RL 50/-
50/- no TDD

For internal use

119 ©2013 Nokia Solutions and Networks. All rights reserved.
 Content
• Introduction
- Re
Reas
ason
ons
s for
for Dr
Drop
op Cal
alll

• KPIs:
- Im
Impo
port
rtan
antt KPIs
KPIs/C
/Cou
ount
nter
ers
s
- Targ
arget
et valu
valueses and
and NSN
NSN and Proj
Project
ect Refe
Referen
rences
ces

• Optimization actions/analy
actions/analysis sis
- UE initiated
initiated Drop Call
Call analysi
analysis:
s: signalli
signalling
ng flows
flows and
and counter
counter triggeri
triggering
ng
- eNode
eNodeB B initiated
initiated Drop
Drop Call
Call analysis:
analysis: signall
signalling
ing flows
flows and counte
counterr triggering
triggering
- Dr
Drop
op Cal
Calll coun
counteterr trig
trigge
gersrs
- Han
Handov
dover
er rel
relate
atedd Dro
Drop p Cal
Calll anal
analysi
ysis
s
• Summary
- Pos
Possib
sible
le Obse
Observarvatio
tions
ns and
and recom
recommen
mendatdation
ions s
- pa
para
rame
meteters
rs in
invo
volv
lved
ed

• Impact of different Features

• Project examples
• Links to further material
For internal use
120 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 Case Study 1:
Call Drop due to Handover Failure : Tx2RelocOverall Timer Expiry

For internal use

121 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 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

122 / ©2013 Nokia Solutions and Networks. All rights reserved.
 UE Log: Radio Conditions

For internal use

123 / ©2013 Nokia Solutions and Networks. All rights reserved.
 Inter-eNodeB X2 Handover 
Message Flow

No Handover Request
 Acknowledge from
target eNodeB, i.e.
HO cancel handover preparation
fails

For internal use

133 ©2013 Nokia Solutions and Networks. All rights reserved.
 Case Study3:
Call Drop due to Handover Failure: No Path Switch Request ACK from MME

For internal use

134 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 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

135 / ©2013 Nokia Solutions and Networks. All rights reserved.
 UE Log: Low Serv
Serving
ing Cell RSRP

For internal use

140 / ©2013 Nokia Solutions and Networks. All rights reserved.
 UE Log
Log:: RRC Rel
Releas
ease
e with Redi
Redirec
rectt to eHRPD
eHRPD

- UE is se
send
ndining
g co
cons
nsec
ecut
utiv
ive
e
measurement reports until
RrcConnectionRelease is received
from eNodeB.
- Th
Thee ev
even
entt A2 is tr
trig
igge
gere
red:
d: RS
RSRP
RP 27
(-113
(-113 dBm) < threshold4 (-1 (-110
10
dBm)

For internal use

141 / ©2013 Nokia Solutions and Networks. All rights reserved.
/
 BTS Log:
Log: RRC Connec
Connection
tion Release
Release

• The UE sends measurem

measurement
ent reports but
but the eNode
eNodeB
B doesn’t react to them (i.e. it doesn’t start the HO
preparation) because the PCI=168 in the measurement
measurement report is not configured as eNodeB neighbour.

For internal use

142 / ©2013 Nokia Solutions and Networks. All rights reserved.
 Case Study 5:
Call Drop due to Radio Link Failure: PuschRlf & CqiRlf 

For internal use

143 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.
 UE Log: Intra-eNodeB Handover 

• The intra-eNodeB handover to a target

cell (PCI 356) was successfully
completed.

For internal use

144 / ©2013 Nokia Solutions and Networks. All rights reserved.
 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
145 / ©2013 Nokia Solutions and Networks. All rights reserved.
 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

146 / ©2013 Nokia Solutions and Networks. All rights reserved.
 Links to relevant material

• MBB PL KPI Bench marking tool (for KPI t arget 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

153 Presentation / Author / Date ©2013 Nokia Solutions and Networks. All rights reserved.