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.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (5 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 16, a correction was introduced for the Radio Link Failure (RLF) report specifically concerning Inter-RAT MRO for NR. This update addressed the procedure for reporting failures during mobility between different radio access technologies. The change ensured accurate handling of the RLF report in scenarios involving inter-RAT cell re-selection or redirection.
- Correction on RLF Report for Inter-RAT MRO NR TS 36.306CR1778
In Release 17, the enhancements to the RLF function included updates to the RLF report and the introduction of the CEF report, as detailed in a Change Request. Additionally, corrections were made to the RLF indication procedure specifically for the BAP (BAP RLF Indication).
In Release 18, a new UE capability for reporting UE location information was introduced specifically for the RLF report in NB-IoT. This enhancement allows the network to receive more detailed geographical context when a radio link failure occurs on these narrowband devices. The change focuses on enriching the data available from the RLF reporting procedure for NB-IoT deployments.
- UE Capability on UE location information in NB-IoT RLF report TS 36.306CR1881
In Release 19, the main enhancement for RLF was a correction to ensure the proper handling of failure reports. Specifically, the update addressed scenarios where a failure report could be generated without an accompanying RLF report. This refinement improved the reliability of failure reporting procedures within the network.
- Correction of Failure report without RLF report TS 38.401CR0512
Explore further
Broader topics and technologies where RLF plays a role.
Defining Specifications
3GPP specifications that define or reference RLF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 25.704 vc00 | Study on Enhanced Broadcast of System Information | Rel-12 |
| TS 28.622 vk20 | Telecommunication Management; Generic NRM Information Service | Rel-20 |
| TS 28.627 vj00 | SON Policy NRM IRP: Requirements | Rel-19 |
| TS 28.628 vj00 | SON Policy NRM IRP Information Service | Rel-19 |
| TR 28.837 vi00 | Technical Report on Trace/MDT Management | Rel-18 |
| TS 28.861 vg00 | SON for 5G Networks Management | Rel-16 |
| TS 32.421 vj30 | Subscriber & Equipment Trace Concepts & Requirements | Rel-19 |
| TS 32.422 vk00 | Telecom Management: Trace Control & Configuration | Rel-20 |
| TS 32.442 vj00 | Trace Management IRP: Information Service | Rel-19 |
| TS 32.446 vj00 | Trace Management IRP Solution Set Definitions | Rel-19 |
| TS 32.836 vc00 | NM Centralized Coverage and Capacity Optimization Study | Rel-12 |
| TR 33.877 vi00 | Technical Report on Security Aspects of AI/ML in RAN | Rel-18 |
| TS 36.306 vj00 | E-UTRA UE Radio Access Capability Parameters | Rel-19 |
| TS 36.839 vb10 | HetNet Mobility Improvements for LTE | Rel-11 |
| TS 36.842 vc00 | Small Cell Enhancements for LTE Higher Layers | Rel-12 |
| TS 37.320 vj00 | Minimization of Drive Tests (MDT) Overview | Rel-19 |
| TS 37.816 vg00 | RAN-centric Data Collection & Utilization Study | Rel-16 |
| TS 37.822 vc10 | SON Enhancements for UE Types and Active Antennas | Rel-12 |
| TS 38.340 vj00 | Backhaul Adaptation Protocol (BAP) Specification | Rel-19 |
| TS 38.401 vj10 | NG-RAN Architecture Specification | Rel-19 |
| TS 38.744 vj01 | AI/ML for NR Mobility Study | Rel-19 |