RLF IN LTE

Radio Link Failure

RRC Re-establish
 RLF DETECT

UE may assume that Radio Link is broken in the following situation.

 The measured RSRP is too low (under a certain limit)
 It failed to decode PDCCH due to power signal quality (e.g, low RSRP, RSRQ)
 It failed to decode PDSCH due to power signal quality (e.g, low RSRP, RSRQ)

eNodeB may assume that that Radio Link is broken in the following situation.
 SRS Power (SINR) from UE is much lower than what eNB configured for the UE
 eNodeB couldn't detect (see) any NACK nor ACK from UE for PDSCH.
 • Then the next question would be "What UE does when it detects Radio Link Failure ?" or "What
eNodeB does when it detects Radio Link Failure ?".
• The most typical procedure is to go through RRC Connection Reestablishment procedure.

Attempt to recover Radio Link while Out of SYNC (Radio Link Failure) When UL Data arrives from higher layer while Out of SYNC (Radio Link Failure)
 RLF FAILURE

Triggering points of RLF

 upon indication from RLC that the maximum number of re transmissions has been reached
 upon expiry of Timer T310 (this timer is started when physical layer problems are detected i.e. upon receiving N310
consecutive out-of-sync indications from lower layers)
 upon random access problem indication from MAC while neither T300, T301, T304 nor T311 is running

Actions when RLF is detected

 UE shall initiate RRC Connection Re-establishment procedure.

 if AS security has not been activated then inform upper layers about the release of RRC connection with release cause 'other'
 UE AND RLF TIMERS
RlfTimerConstGroup . RlfTimerConstGroupId
RlfTimerConstGroup . T301 Common
RlfTimerConstGroup . T310
RlfTimerConstGroup . T311
RlfTimerConstGroup . N310
RlfTimerConstGroup . N311

UeTimerConst
UeTimerConst .T300
UeTimerConst .T301 Common
UeTimerConst .T310
UeTimerConst .T311
UeTimerConst .N310
UeTimerConst .N311
CALL REESTABLISHMENT TRIGGER

• There are several cases where this process get triggered. According to 36.331 5.3.7.2, there are
several cases as described below.

• Case 1 : When radio link failure happened

• Case 2 : when Handover failure happened
• Case 3 : when mobility from E-UTRA failure happened
• Case 4 : when integrity check failure indication was received from lower layers
• Case 5 : when RRC connection reconfiguration failure happened
CALL REESTABLISH
CALL ESTABLISH
 UE TIMERS

UeTimerConst. N310 Indicates the maximum number of successive "out of sync" indications received from L1

UeTimerConst.T310 Started :when the UE detects any fault at the physical layer
Stopped: if the UE detects one of the following before the timer expires:
(1) The physical-layer fault is rectified;
(2) A handover is triggered;
(3) The UE initiates an RRC connection reestablishment procedure.
After the timer expires, the UE enters the RRC_IDLE mode if the security mode is not activated. If the security
mode is activated, the UE initiates an RRC connection reestablishment procedure.

UeTimerConst. N311 Indicates the maximum number of successive "in sync" indications received from L1

UeTimerConst.T311 Started: when the UE starts the RRC connection reestablishment procedure.
Stopped:if, before the timer expires, the UE selects an E-UTRAN or inter-RAT cell to camp on
After the timer expires, the UE enters the RRC_IDLE mode.
 RLF DETECTION

UeTimerConst. N310 = n10(10), UeTimerConst. N311= n1(1),

UeTimerConst. T310 =MS1000_T310(1000ms), UeTimerConst. T311 =MS10000_T311(10000ms),
 T300 & T301

UeTimerConst .T300= MS300_T300(300ms), UeTimerConst .T301= MS200_T301(200ms),

After the timer expires in both Cases, the UE enters the RRC_IDLE state
RLF DETECT BY UE & ENODEB
 RLF DETECTED BY ENODEB - DOWNLINK

the actions carried out by UE are shown when an DL

Physical Layer failure is detected -- > RRC Connection
Reestablishment Request

• The parameter MaxRetxThreshold determines the number of times a packet is retransmitted at the RLC layer in the downlink. If
this number is reached, the eNodeB declares a DL RLC failure and “kills” the context as shown in the picture below.
MO RlcPdcpParaGroup
Parameter ID UeMaxRetxThreshold
Parameter Name MaxRetxThreshold for UE
MML Command ADD RLCPDCPPARAGROUP
MOD RLCPDCPPARAGROUP
LST RLCPDCPPARAGROUP
Meaning Indicates the UE-specific maximum number of RLC ARQ retransmissions, namely the maximum number of AM PDU
retransmissions. When the number of retransmissions reaches the value of this parameter, RRC connection re-establishment is
initiated.
Feature Name Radio Bearer Management
Value Type Enumeration Type
GUI Value Range Maxretx_Threshold_t1(1), Maxretx_Threshold_t2(2), Maxretx_Threshold_t3(3), Maxretx_Threshold_t4(4), Maxretx_Threshold_t6(6),
Maxretx_Threshold_t8(8), Maxretx_Threshold_t16(16), Maxretx_Threshold_t32(32)
Enumeration Number/Bit Maxretx_Threshold_t1~0, Maxretx_Threshold_t2~1, Maxretx_Threshold_t3~2, Maxretx_Threshold_t4~3, Maxretx_Threshold_t6~4,
Maxretx_Threshold_t8~5, Maxretx_Threshold_t16~6, Maxretx_Threshold_t32~7
Unit None
Actual Value Range Maxretx_Threshold_t1, Maxretx_Threshold_t2, Maxretx_Threshold_t3, Maxretx_Threshold_t4, Maxretx_Threshold_t6,
Maxretx_Threshold_t8, Maxretx_Threshold_t16, Maxretx_Threshold_t32
Default Value Maxretx_Threshold_t32(32)
Recommended Value Maxretx_Threshold_t32(32)
Initial Value Setting Source Default/Recommended Value
Impact RlcPdcpParaGroup
Parameter Relationship This parameter is valid when RlcMode is set to RlcMode_AM.
Impact on Radio Network A larger value of this parameter leads to a higher interference resistance capability, but a larger number of retransmissions results in a
Performance longer delay and lower throughput. Set this parameter to a small value for services with a high requirement for the delay and to a large
value for services with a low requirement for the delay. RRC connection re-establishment has a great impact on Acknowledged Mode
(AM) services, such as packet-loss-sensitive and delay-insensitive TCP services, because packets in the buffer are discarded upon the re-
establishment. Therefore, a large value of this parameter is recommended, reducing the probability of RRC connection re-establishment.
RLF DETECTED BY ENODEB - UPLINK

• Not all vendor implementation support

this type of failure detection. It essentially
consists in measuring the power of the
sounding reference signals (SRS) sent by
the UE in the UL. If the power is below a
given SINR threshold, a timer gets
started. If the SINR remains under the
stated SINR threshold for the entire
duration of the timer, then the eNodeB
declares the UL as out of synch and
proceeds to “kill” the context. If the
SINR of the SRS goes above a second
specified threshold during the timer
duration, the UL is said to be in-synch
and no actions are carried out

the actions carried out by eNodeB are shown when an UL

Physical Layer failure is detected ---- > Context Release
MO RlcPdcpParaGroup
Parameter ID ENodeBMaxRetxThreshold
Parameter Name MaxRetxThreshold for eNodeB
MML Command ADD RLCPDCPPARAGROUP
MOD RLCPDCPPARAGROUP
LST RLCPDCPPARAGROUP
Meaning Indicates the eNodeB-specific maximum number of RLC ARQ retransmissions, which limits the maximum number of acknowledged mode
(AM) PDU retransmissions. When the number of RLC ARQ retransmissions reaches the value of this parameter, eNodeB releases the UE.
Feature Name Radio Bearer Management
Value Type Enumeration Type
GUI Value Range Maxretx_Threshold_t1(1), Maxretx_Threshold_t2(2), Maxretx_Threshold_t3(3), Maxretx_Threshold_t4(4), Maxretx_Threshold_t6(6),
Maxretx_Threshold_t8(8), Maxretx_Threshold_t16(16), Maxretx_Threshold_t32(32)
Enumeration Number/Bit Maxretx_Threshold_t1~0, Maxretx_Threshold_t2~1, Maxretx_Threshold_t3~2, Maxretx_Threshold_t4~3, Maxretx_Threshold_t6~4,
Maxretx_Threshold_t8~5, Maxretx_Threshold_t16~6, Maxretx_Threshold_t32~7
Unit None
Actual Value Range Maxretx_Threshold_t1, Maxretx_Threshold_t2, Maxretx_Threshold_t3, Maxretx_Threshold_t4, Maxretx_Threshold_t6,
Maxretx_Threshold_t8, Maxretx_Threshold_t16, Maxretx_Threshold_t32
Default Value Maxretx_Threshold_t32(32)
Recommended Value Maxretx_Threshold_t32(32)
Initial Value Setting Source Default/Recommended Value
Impact RlcPdcpParaGroup
Parameter Relationship This parameter is valid when RlcMode is set to RlcMode_AM.
Access Read & Write
Service Interrupted After Modification No (And no impact on the UE in idle mode)
Validation of Modification The parameter modification has no impact on the equipment.
Impact on Radio Network Performance A larger value of this parameter leads to a higher interference resistance capability, but a larger number of retransmissions results in a longer
delay and lower throughput. Set this parameter to a small value for services with a high requirement for the delay and to a large value for
services with a low requirement for the delay. RRC connection re-establishment has a great impact on Acknowledged Mode (AM) services,
such as packet-loss-sensitive and delay-insensitive TCP services, because packets in the buffer are discarded upon the re-establishment.
Therefore, a large value of this parameter is recommended, reducing the probability of RRC connection re-establishment.
RRC CONNECTION RELEASE CASES
CASE:1

• Going to idle mode: In

this case, the UE will
receive an RRC connection
release from the eNodeB
due to the expiration of
the inactivity timer (in
most networks configured
to approximately 10
seconds).
CASE:2

• Drop Call - > RLC Failure: When

the number of retransmissions at
the RLC layer in the Downlink
direction reaches its maximum
value given by the parameter
MaxRetxThreshold, the eNodeB
releases the context and sends
an RRC connection release to
the UE.
CASE:3

• Drop Call - > RRC

Connection Reestablishment
Reject: Either because the
feature is not adopted or
because a race condition
occurred in which the case
just presented happened first,
the eNodeB responds with a
RRC connection
reestablishment reject to the
UE
CASE:4

• Tracking Area Update: During a

successful tracking area update, the
eNodeB will send an RRC
connection release to the UE after
sending a tracking area update
message (from the MME) when no
new GUTI is allocated or after the
tracking area update complete
message is received from the UE, if
it received a new GUTI.
CASE:5

• During Detach: Either during normal detach or abnormal detach, both by an UE initiated
detach or network initiated detach, the UE receives an RRC connection Release from the
network. Elements in the Network that may cause a detach message sent from the MME to
the UE are:
• Expiration of timers at the P-GW for the last bearer the UE had, capacity issues or errors.
• Errors or Capacity issues at the S-GW
• Expiration of timers at the MME (t3412) without TAU, errors at the MME, configuration
problems, etc.
THANK YOU