LTE RF Optimization

BBU to FSM Swap Project

PM Counters and Parameters Based :Retainability

Verizon
Mohammed Sabahat Ali

Global Delivery Readiness, DE

09/22/2017

1 © Nokia 2016 Nokia Internal Only

 Retainability

2 © Nokia 2016 Nokia Internal Only

FSM Counter based Formula
Context Drop Rate
(EPC_INIT_TO_IDLE_RNL+ EPC_INIT_TO_IDLE_OTHER +
ENB_INIT_TO_IDLE_RNL + ENB_INIT_TO_IDLE_OTHER +
PRE_EMPT_UE_CONTEXT_NON_GBR+((UE_CTX_REL_MME_PART_S
1_RESET+UE_CTX_REL_MME_GLOB_S1_RESET) +
(UE_CTX_REL_ENB_PART_S1_RESET+UE_CTX_REL_ENB_GLOB_S1
_RESET)) )
/ SUM_RRC_CONNECTED_UE
(EPC_INIT_TO_IDLE_UE_NORM_REL + EPC_INIT_TO_IDLE_DETACH
+ ENB_INIT_TO_IDLE_NORM_REL+EPC_INIT_TO_IDLE_RNL+
EPC_INIT_TO_IDLE_OTHER + ENB_INIT_TO_IDLE_RNL +
ENB_INIT_TO_IDLE_OTHER + PRE_EMPT_UE_CONTEXT_NON_GBR
+ ERAB_REL_ENB_RNL_INA_QCI2 - ERAB_REL_ENB_RNL_RED_QCI2
((UE_CTX_REL_MME_PART_S1_RESET+UE_CTX_REL_MME_GLOB_
S1_RESET) +
(UE_CTX_REL_ENB_PART_S1_RESET+UE_CTX_REL_ENB_GLOB_S1
_RESET)) + INTER_ENB_S1_HO_SUCC + (SUCC_INTRA_ENB_HO +
SUCC_INTER_ENB_HO + HO_RLF_SUCC) )
3 © Nokia 2016 Nokia Internal Use
Retainability
Context Drop Rate per Erlang
3600*(EPC_INIT_TO_IDLE_RNL+ EPC_INIT_TO_IDLE_OTHER +
ENB_INIT_TO_IDLE_RNL + ENB_INIT_TO_IDLE_OTHER +
PRE_EMPT_UE_CONTEXT_NON_GBR+((UE_CTX_REL_MME_PART_S
1_RESET+UE_CTX_REL_MME_GLOB_S1_RESET) +
(UE_CTX_REL_ENB_PART_S1_RESET+UE_CTX_REL_ENB_GLOB_S1
_RESET)) )
/ ERAB_REL_ENB_QCI1 - ERAB_REL_ENB_RNL_INA_QCI1 -
Data ERAB Drop Rate
((ERAB_REL_HO_PART + ERAB_REL_ENB -
ERAB_REL_ENB_RNL_INA - ERAB_REL_ENB_RNL_RED +
EPC_EPS_BEARER_REL_REQ_RNL +
EPC_EPS_BEARER_REL_REQ_OTH +
ERAB_REL_EPC_PATH_SWITCH) – (ERAB_REL_HO_PART_QCI1 +
ERAB_REL_ENB_RNL_RED_QCI1 +
EPC_EPS_BEAR_REL_REQ_R_QCI1 +
EPC_EPS_BEAR_REL_REQ_O_QCI1 +
ERAB_REL_EPC_PATH_SWITCH_QCI1) -
(ERAB_REL_HO_PART_QCI2 + ERAB_REL_ENB_QCI2 -
+ EPC_EPS_BEAR_REL_REQ_R_QCI2 +
EPC_EPS_BEAR_REL_REQ_O_QCI2 +
ERAB_REL_EPC_PATH_SWITCH_QCI2))
/
(ERAB_INI_SETUP_SUCC_QCI3+ ERAB_INI_SETUP_SUCC_QCI4+
ERAB_INI_SETUP_SUCC_QCI5+ ERAB_INI_SETUP_SUCC_QCI6 +
ERAB_INI_SETUP_SUCC_QCI7 + ERAB_INI_SETUP_SUCC_QCI8 +
ERAB_INI_SETUP_SUCC_QCI9 +ERAB_ADD_SETUP_SUCC_QCI3
+ERAB_ADD_SETUP_SUCC_QCI4 +ERAB_ADD_SETUP_SUCC_QCI5
+ ERAB_ADD_SETUP_SUCC_QCI6 +
ERAB_ADD_SETUP_SUCC_QCI7 + ERAB_ADD_SETUP_SUCC_QCI8
+ ERAB_ADD_SETUP_SUCC_QCI9)
Call Drop Types Types

• RRC Connection Drop Rate

- The RRC connection drop rate is not so widely used. It is mainly an indication of the radio quality and its effect on synchronization and RLC
acknowledged mode procedures.

• UE Context Drop Rate

- The most important and widely used is the UE context drop rate. It has a direct relation with the signaling flows

• E-RAB Drop Rate

• The E-RAB drop rate is important when analyzing the call drop rate per type of service (per QCI). Note that for a multi-service call, the abnormal
release of one E-RAB does not trigger a UE context release

4 © Nokia 2016 Nokia Internal Use

LTE Bearers

5 © Nokia 2016 Nokia Internal Use

Attach Procedure & Bearer setup with Counters 1/4

6 © Nokia 2016 Nokia Internal Use

Attach Procedure & Bearer setup with Counters 2/4

7 © Nokia 2016 Nokia Internal Use

Attach Procedure & Bearer setup with Counters 3/4

8 © Nokia 2016 Nokia Internal Use

Attach Procedure & Bearer setup with Counters 4/4

9 © Nokia 2016 Nokia Internal Use

Introduction-Call Drops

• Call drop ratio is one of the most important metrics to assess the performance of the mobile networks.
• The call drops are also referred as Radio Link Failures (RLF).
• The mechanisms dealing with RLF are implemented at both UE and eNB side.
• If UE detects radio link problems it tries to recover from RLF during specified interval of time by RRC connection
re-establishment procedure.
• If eNB detects a radio link problem it will wait until the recovery (cancellation of RLF state), or release the UE.
• The call drops can also be initiated by the eNB (or MME) in other scenarios such as timing alignment timer expiry, S1
reset etc.

10 © Nokia 2016 Nokia Internal Use

Call Release Scenarios
Normal call release following UE context release initiated by MME

UE eNB MME S-GW

In a normal call release scenario the MME
initiates the S1 release by sending the UE
Trigger for S1
release occurs
CONTEXT RELEASE COMMAND message to
release of the UE associated S1 logical
RELEASE ACCESS BEARERS REQUEST connection over the S1 interface.

RELEASE ACCESS BEARERS RESPONSE

.

UE CONTEXT RELEASE COMMAND

(Cause: “Normal Release”)

RRC CONNECTION RELEASE

(Cause: “Normal Release”)

UE CONTEXT RELEASE COMPLETE

11 © Nokia 2016 Nokia Internal Use

Call Release Scenarios
UE context release by eNodeB

UE eNB MME S-GW As a general observation, the dropped

call events may be identified by an eNB
UE CONTEXT RELEASE REQUEST initiated UE context release, thus using
(Cause: “Failure Due To E-UTRAN Generated Reason”)
message UE CONTEXT RELEASE
RELEASE ACCESS BEARERS REQUEST
REQUEST with the appropriate error
cause (e.g. “Release due to E-UTRAN
RELEASE ACCESS BEARERS RESPONSE
Generated Reason”). When this
UE CONTEXT RELEASE RESPONSE
message is sent, the radio connection
(Cause: “Normal Release”) with the UE is also terminated on the
RRC CONNECTION RELEASE RRC layer, so the UE goes back to idle
(Cause: “Unspecified”) mode
UE CONTEXT RELEASE COMPLETE

12 © Nokia 2016 Nokia Internal Use

Retainability Issues

Below are the possible reasons for RF resulting in call drops ,but not limited to

1.UE 2.eNodeB

• T310 expiry • PUSCH RLF

• Maximum number of RLC • CQI RLF
retransmissions • HARQ RLF
• Handover failure (T304 expiry) • PDCCH Order failure
• Non-HO related random access problem • Maximum RLC Retransmissions
Exceeded at eNB
• GTP-U failure at eNB
• S1 reset

13 © Nokia 2016 Nokia Internal Use

UE Detected Radio Link Failure initiates RRC Connection Re-establishment

For non-real time services such as web browsing or e-mail, user perception is described as rather a
temporary interruption of data transport, a delay in accessing the next web site or a significant
downturn of the data transmission rate of an ongoing download. If the network can re-establish the lost
radio connection fast enough, the drop of the radio connection won’t really be recognized by the
subscriber.
So, it is important to trigger RRC re-establishment before considering the call as dropped and going back
to idle mode. RRC re-establishment can help recovering from connection problems in areas of quickly
changing radio conditions

14 © Nokia 2016 Nokia Internal Use

UE Detected Radio Link Failure initiates RRC Connection Re-establishment

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 upon:
• T310 expiry
• reaching the maximum number of UL RLC retransmissions
• handover failure (T304 expiry)
• non-HO related random access problem (while neither T300, T301, T304 nor T311 is running)
In case of RRC connection is successfully re-established SRB1 is reconfigured to resume data transfer of RRC messages
and RRC security (without changing algorithms) is reactivated.

15 © Nokia 2016 Nokia Internal Use

UE Detected Radio Link Failure initiates RRC Connection Re-establishment

• Only UE can initiate re-establishment procedure.

• Procedure can succeed only if the concerned cell is
prepared, i.e. has a valid UE context.
• UE context search is limited to the re-establishment
target cell (serving cell / source cell / prepared target
cell).
• AS (access stratum) security must be activated.
• If security is not active UE moves to
RRC-Idle mode instead.
• UE context must be identified by the UE-Identity IE
(included in RRC CONNECTION RE-ESTABLISHMENT
REQUEST).

16 © Nokia 2016 Nokia Internal Use

UE Detected Radio Link Failure initiates RRC Connection Re-establishment
Possible Failure Reasons resulting in Drop
When the signaling shown is not completed, the RRC re-
establishment procedure fails
The reasons for unsuccessful RRC re-establishment can be
associated to, the transmission of RRC REESTABLISHMENT
REJECT message from the eNB .
• Feature not activated
• Reception of another RRC CONNECTION
REESTABLISHMENT REQUEST
while the procedure is already ongoing,
• Unknown Reestab UE-Identity,
• Loss of S1 or cell service,
• CAC failure

17 © Nokia 2016 Nokia Internal Use

UE Detected Radio Link Failures (RLF)
T310 Expiry
• During the UE operation various timers/counters are checked:
- Counter N310 specifies maximum number of out-of-sync indications
- Timer T310 supervises the recovery from physical layer problems. Started after N310 successive out-of-sync
indications from physical layer
- Timer T311 supervises the RRC connection re-establishment

• Radio link failure is triggered by UE after T310 expiry

• UE “normal operation” means that other operations supervised by timers are not running:
- 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

• Depending on the BLER variation, in-sync and out-of-sync indication are reported
• It can lead to start of UE timer T310 after n310 successive out-of-sync indications

18 © Nokia 2016 Nokia Internal Use

UE Detected Radio Link Failures (RLF)
T310 Expiry T310 Stop/T311Start
T310 Start

First Phase Second Phase

DROP

radio
normal operation problem no recovery during T310 no recovery during T311 goes back to idle
detection

RRC_CONNECTED RRC_IDLE

N310 consecutive out- N311 consecutive in-sync RRC connection re-

radio link failure Cell reselection and
of-sync indications indications during t310 establishment attempted after Tracking Area Update if
T310 expiry during T311 RRC Re-Establishment
fails
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 .
After T310 expiry radio link failure is triggered by UE and RRC re-establishment is attempted.
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 and RRC connection resumes.

19 © Nokia 2016 Nokia Internal Use

UE Detected Radio Link Failures (RLF
T310 Expiry- Possible Optimization
• To optimize the call drops following parameter recommendations are given
- n310: maximum number of consecutive "out-of-sync" indications received from lower layers
• The recommended value for cells with high call drop rate is n310=n20 (internal value 7)

- n311: maximum number of consecutive "in-sync" indications received from lower layers

t310: Timer T310 supervises the recovery from physical layer problems. Higher the value of the parameter, longer the time in which UE can
stay in RLF state waiting for recovery. Lowering the value causes faster release  higher drop ratio

t311: Timer T311 supervises the RRC connection re-establishment. Together with T310, the timer increases the time in which UE can try to
recover from RLF state. The timer shall be aligned to typical re-establishment procedure time. The longer the value of this parameter, the
longer eNB will wait for successful re-establishment. Lowering the value of this parameter can lead to increased drop ratio

20 © Nokia 2016 Nokia Internal Use

UE Detected Radio Link Failures (RLF)
Maximum UL RLC Retransmissions Exceeded T311 Stop
T311 Start

First Phase Second Phase DROP

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

RRC_CONNECTED RRC_IDLE

RLC retransmissions until max RLC radio link failure Cell reselection and
retransmission threshold (16) is reached Tracking Area Update if
RRC connection re-establishment RRC Re-Establishment
attempted during T311 fails

• Radio link failure can be triggered by UE if maximum number of retransmissions is reached

• The number of retransmission is defined during call set-up in RRCConnectionReconfiguration message
- Hardcoded to max 16 retransmissions (drbAmMxRtxTh)
- AM RLC maximum retransmission threshold DRB: This parameter is used by the transmitting side of each AM
RLC entity to count the number of transmissions of an AMD PDU.

21 © Nokia 2016 Nokia Internal Use

UE Detected Radio Link Failures (RLF)
Handover Failure (T304 Expiry)
T304 Start T304 Stop & T311 Start
T311 Stop
First Phase Second Phase DROP

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

RRC_CONNECTED RRC_IDLE

RRC Conn ReConf with MobilityInfo (”HO RRC connection re-establishment

command”)
T304 running while UE radio link failure Cell reselection and Tracking Area
attempting access to target cell. attempted to source or target cell
Update if RRC Re-Establishment fails
during T311
T304 expires

• When UE receives RRC Connection Reconfiguration with mobilityControlInfo IE (i.e, ”handover command”), it starts
timer T304.
• If PRACH procedure to the target cell does not succeed by the timer T304 expires then handover failure occurs:
- UE tries RRC Connection Re-establishment with re-establishment cause ”handover Failure”

22 © Nokia 2016 Nokia Internal Use

UE Detected Radio Link Failures (RLF)
Handover Failure (T304 Expiry)
• To improve the call drop ratio, T304 parameter optimization shall be considered
• Higher the timer value, longer supervises the HO procedure
• However in case of failure, UE will longer wait for Re-establishment (critical for voice services)
• Lower the value of the parameter can decrease the HO success ratio
• Lower the timer value, faster the RLF will be triggered (and UE would need to perform RRC Re-establishment).
• Please note that various mobility procedures need different amount of time to succeed (due to e.g. RACH procedure
duration and other RAT specifics)
• Usually procedures should not last more than 50-150 ms

23 © Nokia 2016 Nokia Internal Use

UE Detected Radio Link Failures (RLF)
Non-HO Related Random Access Problem
T311 Start
T311 Stop

First Phase Second Phase

DROP

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

RRC_CONNECTED RRC_IDLE

Random Access triggered due to

missing PUCCH SR resources or radio link failure Cell reselection and
RRC connection re-establishment
PDCCH order UE attempting random RACH failure attempted to serving cell during Tracking Area Update if
access to serving cell. T311 RRC Re-Establishment fails

• Random Access procedure is triggered due no response to the Scheduling Request on PUCCH (i.e. UE sends the SRI(
Scheduling request indicator) on PRACH) or eNB sends PDCCH order to initiate PRACH procedure (e.g. re-acquiring
UL sync).

24 © Nokia 2016 Nokia Internal Use

All RLF Related Timers
Value Value assigned in ALU Harmonized setting (setting to be Source GPL for
Nokia Parameter Default Value from fALU GPL translated into
Range and step assigned in GPL(formatted for fALU assigned in FOA site). Blank entries use harmonized
Short Name Value Nokia parameter format.
Nokia GPL. BBU) the Nokia GPL value. value
400ms
t301 0: 100ms, 1: 200ms ,2: 300ms ,,3: 400ms 400ms ms1500 1500ms 1500ms BCEM
(3)
,4: 600ms ,5: 1000ms ,6: 1500ms 7:
2000ms
0: 1000ms ,1: 3000ms ,2: 5000ms ,3: 3000ms
t311 3000ms ms5000 5000ms 5000ms BCEM
10000ms ,4: 15000ms ,5: 20000ms (1)
,6: 30000ms
2000ms
t310 0: 0ms ,,1: 50ms ,2: 100ms ,3: 200ms 2000ms ms1000 for microcells 1000ms for microcells 1000ms for microcells BCEM
(6)
,4: 500ms ,5: 1000ms ,6: 2000ms ms2000 for macrocells 2000ms for macorcells 2000ms for macrocells
4000ms
t304eNaccGsm 0: 100ms 4000ms Timer2000ms 2000ms 2000ms BCEM
(5)
1: 200ms
2: 500ms
3: 1000ms
4: 2000ms
5: 4000ms
6: 8000ms
500ms
t304InterRATGsm 1: 100ms 500ms 500ms
(3)
2: 200ms
3: 500ms
4: 1000ms
5: 2000ms
6: 4000ms
7: 8000ms

25 © Nokia 2016 Confidential

All RLF Related Timers
)
Nokia Parameter
Short Name
Range and step
Default
Value
Value
assigned in
Value assigned in ALU
GPL(formatted for fALU BBU)
Value from fALU GPL translated into
Nokia parameter format.
Harmonized setting (setting to be assigned
in FOA site). Blank entries use the Nokia
Source GPL for
harmonized value
Nokia GPL. GPL value.
1000ms
t304IntraLte 0: 50ms 1000ms Timer2000ms 2000ms 2000ms BCEM
(5)
1: 100ms
2: 150ms
3: 200ms
4: 500ms
5: 1000ms
6: 2000ms
t304InterRAT 0: 100ms 500ms (2) 500ms
1: 200ms 500ms
2: 500ms
3: 1000ms
4: 2000ms
5: 4000ms
6: 8000ms
0: n1
1: n2
2: n3
3: n4 n10 for microcells n10 for microcells n10 for microcells
n310 n10 (6) n10 BCEM
4: n6 n20 for macrocells n20 for macrocells n20 for macrocells
5: n8
6: n10
7: n20
1: n1
2: n2
3: n3
4: n4
n311 n1 (1) n1 n1 n1 n1 Both
5: n5
6: n6
8: n8
10: n10
26 © Nokia 2016 Confidential
UE Detected Radio Link Failures (RLF) – Counters

27 © Nokia 2016 Nokia Internal Use

 eNB Detected radio link problems

28 © Nokia 2016 Nokia Internal Only

eNB Detected radio link problems
Introduction
• eNB radio link problem detection mechanisms are internally specified
• Multiple methods (called “link monitors”) are defined to detect a radio link problem in the eNB
• If any of the link monitors detects the problem, the eNB will wait for recovery, until T_RLF timer expires
T_RLF = t310 + t311

Each link monitor has its internal criteria to decide when radio link problem is flagged and de-flagged (radio link recovers)
• If the RLF persists longer than T_RLF, RRC+S1 release is triggered
• Counter ENB_INIT_TO_IDLE_RNL is incremented

29 © Nokia 2016 Nokia Internal Use

eNB Detected radio link problems
Introduction
ENB_INIT_TO_IDLE_RNL: eNB initiated transitions to ECM-IDLE due to Radio Network Layer cause
The number of eNB-initiated transitions from the ECM-CONNECTED to ECM-IDLE state for all RNL causes indicating an
abnormal release. The UE-associated logical S1-connection is released.
UPDATED: The counter is updated upon the transmission of an S1AP: UE CONTEXT RELEASE REQUEST message sent by
the eNB to the MME with one of the following release causes:
- RNL Radio Connection with UE Lost
- RNL Failure in the Radio Interface procedure
- RNL TX2RELOCoverall Expiry
- RNL TS1RELOCoverall Expiry
- RNL E-UTRAN Generated Reason
- RNL Radio resources not available
- RNL Invalid QOS combination
- RNL UE not available for PS service
- RNL Unspecified</Description>

30 © Nokia 2016 Nokia Internal Use

eNB Detected Radio Link Failures (RLF)
RRC + S1 Release
When the timer T_RLF expires, the UE
is released from the eNB using eNB
initiated S1 release + RRC connection
release resulting in call drop
RRC Connection Release message is
sent using acknowledged RLC mode
on the DCCH (SRB1) mapped to DL-
SCH
After S1AP: UE Context Release
Complete, the connection is released

31 © Nokia 2016 Nokia Internal Use

eNB Detected radio link problems
PUSCH RLF
• PUSCH RLF is declared when eNB cannot detect the signal from the UE (DTX) for a given period
• When UE is scheduled for PUSCH transmission, eNB expects to receive UL transmission on the scheduled PRBs
• If signal from UE cannot be detected, PUSCH DTX is declared.
• The detection of the radio link problem by the uplink scheduler is based on the comparison of UL grant assignment and the DTX
detection on PUSCH for the assigned PRBs. The detection is based on the DTX PUSCH indication provided by the UL physical layer.
• The result is received by LTE MAC in reliableULtransmissionFlag parameter.

• If the eNB receives “DTX” for multiple resource allocations on UL PUSCH to the same UE during a period of time
(rlpDetMaxTUl) or if “DTX“ is received for a consecutive number of times (rlpDetMaxNUl), the UL scheduler sets the
PuschRlf_ON.
• The recovery of the radio link is indicated when for a consecutive number of UL resource assignments data
(rlpDetEndNUl ) is detected on PUSCH (ACK or NACK received) and UL scheduler sets the PuschRlf_OFF.

32 © Nokia 2016 Nokia Internal Use

eNB Detected radio link problems
PUSCH RLF
Example Parameter Values:
rlpDetMaxNUl=4
rlpDetEndNUl=3

T_RLF = t310 + t311

rlpDetMaxNUl Number of PUSCH DTX detections for radio link problem

rlpDetEndNUl Number of PUSCH detections to end radio link problem

33 © Nokia 2016 Nokia Internal Use

eNB Detected radio link problems
PUSCH RLF
The following parameters are related to Uplink PUSCH DTX detection and recovery
Harmonized setting
(setting to be assigned
Nokia Parameter Range and
Full Name Description Default Value in FOA site). Blank
Short Name step
entries use the Nokia
GPL value.
Defines the number of consecutive
uplink data receptions on PUSCH
without DTX detection before the
Number of PUSCH detections to end
rlpDetEndNUl radio link problems are assumed to 1...20, step 1 3(Mint)
radio link problem
be over and an indication about radio
link recovery is sent to higher layers.
This parameter is vendor-specific.
Defines the number of uplink DTX
detections on PUSCH before an
Number of PUSCH DTX detections for 1...1000,
rlpDetMaxNUl indication about radio link problems 1000(Mint)
radio link problem step 1
is sent to higher layers. This
parameter is vendor-specific.

34 © Nokia 2016 Nokia Internal Use

eNB Detected radio link problems
CQI RLF: detection and recovery
• The eNB supports CQI DTX detection for
periodic CQI reports on PUCCH and PUSCH T_RLF = t310 + t311
• CQI RLF detection counts consecutive missed
CQI transmissions
• If MAC layer receives nCqiDtx consecutive
reports from UL PHY, the MAC declares
CqiRlf_ON.
• 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.

In this example default

nCqiDtx 6
nCqiRec 2

nCqiDtx Radio problem indication based on CQI DTX

nCqiRec Radio problem recovery based on CQI DTX

35 © Nokia 2016 Nokia Internal Use
eNB Detected radio link problems
CQI RLF: detection and recovery
The following parameters are related to CQI DTX detection and recovery
Harmonized setting (setting to be
Nokia Parameter
Full Name Description Range and step Default Value assigned in FOA site). Blank entries use
Short Name
the Nokia GPL value.
Number of concecutive CQI DTX detections required for RL
failure.
The parameter defines the number of consecutive CQI DTX
nCqiDtx Radio problem indication based on CQI DTX 0...250, step 1 100 0
detections causing radio link
failure indication. Special value 0 means that the feature is
disabled.
Number of concecutive CQIs required for RL recovery.
The parameter defines number of consecutive CQI non-DTX
nCqiRec Radio problem recovery based on CQI DTX 1...8, step 1 2 2
detections causing radio link
failure recovery indication.

• Note that significant improvement in dropped call rate can be achieved when increasing the value of cqiPerNp (reporting interval
for periodic CQI).
• PUCCH Power control plays also significant role in CQI based RL failure detection

36 © Nokia 2016 Nokia Internal Use

eNB Detected Radio Link Failures (RLF)
Uplink Ack/Nack DTX Detection
After DL scheduled data, eNB expects
HARQ ACK/NACK on PUCCH or PUSCH.
If for consecutive DL resource T_RLF = t310 + t311
allocations to the same UE the HARQ
feedback from the UE is always "DTX“,
either for a configurable period of time
(rlpDetMaxTimeDl, hard coded to 0 i.e.
not in use) or for a configurable number
of consecutive DL resource allocation
attempts (rlpDetMaxNoDL), DL
scheduler sets AckNackRlf_ON.
HARQ RLF
If for a configurable number detection
(rlpDetEndNoDl) of consecutive DL
resource allocations to the same UE the In this example default
HARQ feedback from the UE is not
rlpDetMaxNoDl 4
"DTX", DL scheduler sets
rlpDetEndNoDl 3
AckNackRlf_OFF.
rlpDetEndNoDl Number of successful PDSCH transmissions
rlpDetMaxNoDl Number of failed PDSCH transmissions

37 © Nokia 2016 Nokia Internal Use

eNB Detected Radio Link Failures (RLF)
Uplink Ack/Nack DTX Detection

Harmonized setting (setting to be

Nokia Parameter assigned in FOA site). Blank entries
Short Name Full Name Description Range and step Default Value use the Nokia GPL value.
This parameter determines the number DL
PDSCH transmission with correct HARQ
feedback until detected radio link problems
Number of successful PDSCH are assumed to be over. This parameter is
rlpDetEndNoDl transmissions vendor-specific. 1...20, step 1 3
This parameter determines the maximum
number of failed DL PDSCH transmission
attempts until radio link problems are
Number of failed PDSCH detected. This parameter is vendor-
rlpDetMaxNoDl transmissions specific. 1...1000, step 1 1000
Determines the timeframe for failed DL
PDSCH transmission attempts until radio
Timeframe for failed PDSCH link problems are detected. This parameter 20...5000 ms, step
rlpDetMaxTimeDl transmissions is vendor-specific. 1 ms 0

38 © Nokia 2016 Nokia Internal Use

eNB Detected Radio Link Failures (RLF)
PDCCH Order RLF
If there is DL data in eNB buffer and UE is out-of-sync, UE must be brought back to in-sync (time aligned) with a RA
procedure.
The procedure includes signaling of dedicated RA preamble (PDCCH order) message 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 is repeated (noRepPdcchOrder, hard coded to 1) again using the selected preamble
and considering DRX status of the UE accordingly.
Final failure of the PDCCH order process is indicated as radio link problem to higher layers with cause “PDCCH order failure

Refer Slide 24 after RLF:

39 © Nokia 2016 Nokia Internal Use

eNB Initiated Releases
Maximum DL RLC Retransmissions Exceeded
If eNB RLC layer notifies that the RLC AM entity of a DRB has reached the event “Maximum number of RLC retransmissions” for an RLC PDU:
eNB 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 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

40 © Nokia 2016 Nokia Internal Use

eNB Initiated Releases
GTP-User Plane Failure at eNB
eNodeB may receive a “GTP-U Error Indication” on an active S1 bearer(s) (S-GW has rejected the reception of uplink data packets)
When single (or all) GBR S1 bearers have failed:
• eNodeB sends the S1AP message UE CONTEXT RELEASE REQUEST with cause “TNL Cause Transport Resource Unavailable” to MME
If one active non-GBR S1 bearer remains:
• eNB starts an internal triggered E-RAB Release
• When the E-RAB Release has finished (reception of RRConnectionReconfigurationComplete), eNB sends the S1AP message E-RAB
RELEASE INDICATION to MME
Finally the RAC and TAC resources of the released E-RAB become free.
Note: TAC allocates only GBR resources

Note
eNB stops sending UL data to S-GW for the affected S1 bearer(s)
and waits for a timer (configured by R&D parameter
tWaitForPosDetach, default 100ms) before starting the
described procedure.
This is caused by non-3GPP-compliant UEs that continue sending
UL data though they have initiated the NAS Detach procedure

41 © Nokia 2016 Nokia Internal Use

eNB Initiated Releases
S1 Reset
• S1 Reset (S1AP: RESET) procedure may be
used by eNB or MME to recover from
erroneous situations

• When the S1 interface is reset either by

the eNB or the MME, the eNB releases all
affected RRC connections

The S1 resets are reflected in the following

counters:
• S1AP_GLOBAL_RESET_INIT_ENB,
• S1AP_GLOBAL_RESET_INIT_MME,
• S1AP_PARTIAL_RESET_INIT_ENB,
S1AP_PARTIAL_RESET_INIT_MME
Additionally, after the S1 reset the S1 setup
attempt follows

42 © Nokia 2016 Nokia Internal Use

 Drops due to Mobility

43 © Nokia 2016 Nokia Internal Only

Mobility related drops
Overview
Handover procedure is usually the main place in which call drops can be observed, due to:
• Mobility parameter errors
• UE movement
• Discontinuous cell coverage

44 © Nokia 2016 Nokia Internal Use

Mobility related drops
Intra eNodeB handover procedure

45 © Nokia 2016 Nokia Internal Use

Mobility related drops
Inter eNodeB handover procedure (X2 example): preparation phase

46 © Nokia 2016 Nokia Internal Use

Mobility related drops
Inter eNodeB handover procedure (X2 example): execution phase

47 © Nokia 2016 Nokia Internal Use

 Interdependencies

48 © Nokia 2016 Nokia Internal Only

 Related features overview impact on call drops
Interdependencies
Related features overview impact on call drops

• These functionalities provide basic
Link monitors mechanism to trigger RLF in case of
for RLF DTX or desynchronization in UL or
triggering DL
• If any of the link monitors detects
the problem, the eNB will wait of
recovery until T_RLF timer expires
C-Plane exception
handling
(t310 + t311)
• However that features are
configurable only by hidden vendor
parameters, which default set to the
Radio Link Failure from
HARQ values which practically switches
• Sleeping cells are special kind of cell
outage in which no alarm is triggered
Cell outage and cell is assumed to be available
• Due to variety of malfunctions leading
to sleeping cell state different
situations are expected
• If UE would try the handover towards
Cell Outage Detection sleeping cell it may end with a call
drop
Cell Outage triggered
reset

them off

Radio Link Failure from

CQI

49 © Nokia 2016 Nokia Internal Use

 Related features overview impact on call drops
Interdependencies
Related features overview impact on call drops

• All mobility features provide the • Automatic Neighbor Relationship

means to move the UEs between
Mobility different network layers
• Availability of that features ensures
continuity of the service while
moving across the network
Mobility Robustness • In case of poor mobility
configuration or lack of proper
InterRAT PS handover to feature activation, the mobility may
WCDMA
be spoiled by
Automatic features support the successful
Neighbor mobility procedures by provision of
Relationships the relations between the cells
• In case of lack or wrong neighbor
relationships, the handover attempt
ANR may lead to call drop
ANR Intra-LTE, Intra-
frequency Fully UE based

SRVCC to WCDMA &

non-continuous coverage resulting
GSM in call drops ANR InterRAT with O&M

ANR Optimization of
RSRQ based cell
Intra-LTE neighbor
reselection & redirect
relations

ANR Intra-LTE, Inter-

Intra cell HO
frequency - UE based

ANR Inter-RAT UTRAN -

RLF triggered handover
Fully UE based

50 © Nokia 2016 Nokia Internal Use

 Related features overview impact on call drops
Interdependencies
Related features overview impact on call drops

• Admission control features protect • The UE may initiate the RRC

the limited cell resources against connection re-establishment
Admission overload Other procedure to continue the RRC
control • Then UEs connection attempts may features connection without going to RRC Idle
be rejected mode when:
• In case UE has no other layer it could • detecting radio link failure
connect to and come back to • handover failure
Admission Control
previous cell is impossible, the call RRC Connection Re-
Establishment
• mobility from E-UTRA failure
drop will be triggered • integrity check failure indication from
lower layers
Transport Admission
Control
• an RRC CONNECTION
RECONFIGURATION failure

• Interference Rejection Combining

Smart Admission Control
features improve the SINR, thus
decrease the probability of the call
drop in interference limited scenarios

51 © Nokia 2016 Nokia Internal Use

References

• Nokia Edu
• Sharenet

52 © Nokia 2016 <Change information classification in footer>

Copyright and confidentiality
The contents of this document are proprietary
and confidential property of Nokia. This document
is provided subject to confidentiality obligations
of the applicable agreement(s).
This document is intended for use of Nokia’s
customers and collaborators only for the purpose
for which this document is submitted by Nokia. No
part of this document may be reproduced or
made available to the public or to any third party
in any form or means without the prior written
permission of Nokia. This document is to be used
by properly trained professional personnel. Any
use of the contents in this document is limited
strictly to the use(s) specifically created in the
applicable agreement(s) under which the
document is submitted. The user of this
document may voluntarily provide suggestions,
comments or other feedback to Nokia in respect
of the contents of this document ("Feedback").
54 © Nokia 2016
Such Feedback may be used in Nokia products
and related specifications or other
documentation. Accordingly, if the user of this
document gives Nokia Feedback on the contents
of this document, Nokia may freely use, disclose,
reproduce, license, distribute and otherwise
commercialize the feedback in any Nokia product,
technology, service, specification or other
documentation.
Nokia operates a policy of ongoing development.
Nokia reserves the right to make changes and
improvements to any of the products and/or
services described in this document or withdraw
this document at any time without prior notice.
The contents of this document are provided "as
is". Except as required by applicable law, no
warranties of any kind, either express or implied,
including, but not limited to, the implied
Nokia Internal Only
warranties of merchantability and fitness for a
particular purpose, are made in relation to the
accuracy, reliability or contents of this document.
NOKIA SHALL NOT BE RESPONSIBLE IN ANY EVENT
FOR ERRORS IN THIS DOCUMENT or for
any loss of data or income or any special,
incidental, consequential, indirect or direct
damages howsoever caused, that might arise
from the use of this document or any contents of
this document.
This document and the product(s) it describes
are protected by copyright according to the
applicable laws.
Nokia is a registered trademark of Nokia
Corporation. Other product and company names
mentioned herein may be trademarks or trade
names of their respective owners.