Radio Link Failure

Description

Radio Link Failure (RLF) is a critical event in 3GPP cellular networks where the radio connection between a User Equipment (UE) and its serving cell becomes unusable and is declared as failed. It is not a single measurement but a procedural outcome triggered by specific, standardized conditions monitored by both the UE and the network (e.g., gNB in NR). The primary mechanism for RLF detection at the UE side is based on the monitoring of radio link quality through physical layer measurements. In LTE and NR, this is typically governed by timers T310 and T311, and counters like N310 and N311. The process involves the UE's physical layer continuously evaluating the downlink radio quality (e.g., based on Cell-specific Reference Signal (CRS) in LTE or Synchronization Signal Block (SSB)/Channel State Information Reference Signal (CSI-RS) in NR). If the quality falls below a threshold (Q_out), the physical layer indicates 'out-of-sync' to higher layers. After receiving a consecutive number (N310) of 'out-of-sync' indications, the UE starts timer T310. If the radio quality does not recover (by receiving N311 'in-sync' indications) before T310 expires, the UE declares an RLF and initiates Radio Resource Control (RRC) connection re-establishment procedures to attempt recovery.

From the network perspective, a gNB may also infer an RLF based on uplink radio problems or failure to receive expected feedback (e.g., lack of HARQ ACKs or CQI reports) over a period. The declaration of RLF is a definitive state that moves the connection out of normal operation. Upon declaring RLF, the UE suspends all radio bearers except SRB0, selects a suitable cell (not necessarily the strongest), and initiates an RRC Re-establishment procedure to that cell. This procedure aims to quickly restore the signaling connection and, if successful, can also re-activate the data bearers with minimal service interruption. If re-establishment fails, the UE transitions to RRC_IDLE and must perform a fresh connection setup. The network uses RLF reports, which the UE can log and later transmit upon reconnection, to analyze failure causes. These reports contain valuable data like the location, measurements of serving and neighboring cells before failure, and the identified failure cause, enabling Self-Organizing Network (SON) functions for mobility optimization.

RLF is intrinsically linked to mobility management. Poor handover parameter settings (e.g., handover thresholds, time-to-trigger) are a major cause of RLFs, leading to too-late or too-early handovers, or handovers to wrong cells. Therefore, RLF detection and reporting are central to Mobility Robustness Optimization (MRO) SON functions. The network analyzes RLF and handover failure statistics to automatically adjust mobility parameters, reducing call drops and improving user experience. In advanced deployments like dual connectivity, RLF may be declared on a specific cell group (Master or Secondary), triggering specific recovery actions without necessarily dropping the entire connection.

Purpose & Motivation

Radio Link Failure exists as a formalized, standardized concept to provide a clear and consistent failure detection and recovery mechanism for radio connections in mobile networks. The radio environment is dynamic; signal strength can degrade rapidly due to user mobility, obstacles, or interference. Without a well-defined RLF procedure, a UE might indefinitely attempt to communicate over a lost link, wasting battery and radio resources, or drop the connection in an uncontrolled manner, leading to poor user experience and difficulty in network diagnosis. The RLF framework solves this by establishing unambiguous criteria (timers, counters, thresholds) for declaring a link failed, ensuring both the UE and network have a common understanding of connection status.

Its creation was motivated by the need for robust mobility and connection management, especially as networks evolved towards higher speeds and more complex scenarios in LTE (Rel-8 onwards) and 5G NR. Earlier systems had less sophisticated link failure handling. The formal RLF procedures, introduced and enhanced from Rel-8/Rel-9 onwards, enable predictable recovery behavior. They address the problem of 'radio link blackout' by triggering a swift and standardized recovery attempt (RRC re-establishment) that is faster than establishing a new connection from scratch. Furthermore, the associated RLF reporting mechanism, significantly enhanced in later releases, addresses the critical network optimization problem of 'troubleshooting mobility failures.' By collecting detailed failure logs from UEs, operators can automatically identify and correct suboptimal network configurations (like handover parameters), which directly improves network reliability and reduces dropped calls. Thus, RLF is not just a failure indicator but a foundational enabler for automated network self-healing and optimization.

Key Features

• Triggered by physical layer 'out-of-sync' indications exceeding configured thresholds (N310, T310)
• Initiates RRC connection re-establishment procedure for recovery
• Supports detailed failure logging and reporting (RLF reports) for network optimization
• Integral part of Mobility Robustness Optimization (MRO) in SON
• Can be detected by both UE and network nodes
• Configurable parameters allow tuning for different deployment scenarios and mobility conditions

Evolution Across Releases

Defining Specifications