Call Re-establishment

Description

Call Re-establishment (CRE) is a critical Radio Resource Control (RRC) procedure defined in 3GPP specifications, primarily for LTE and evolved in 5G NR, designed to recover from a Radio Link Failure (RLF). The procedure is initiated by the User Equipment (UE) when it detects that the radio link with its serving cell has failed but believes the connection context at the network side (specifically at the eNodeB in LTE or gNB in NR) may still be valid. This detection is based on physical layer measurements, such as the downlink radio quality falling below a threshold, leading to out-of-sync indications. Upon detecting RLF, the UE starts a timer (T311 in LTE) and attempts to select a suitable cell for re-establishment, which can be the original cell or a different cell, provided it belongs to the same eNodeB or a prepared neighboring cell. The UE then sends an RRC Connection Re-establishment Request message to the selected cell, containing its UE Identity (C-RNTI) and a shortMAC-I for security verification.

The receiving eNodeB checks if it holds the UE's context. If the context is available and the security check passes, the eNodeB responds with an RRC Connection Re-establishment message, which re-activates security and reconfigures the radio bearers. This allows the UE to resume its data session without needing a full RRC connection setup from idle mode, significantly reducing interruption time. If the context is not found (e.g., because it was cleared after RLF detection) or the security check fails, the network rejects the request with an RRC Connection Re-establishment Reject, forcing the UE to transition to RRC_IDLE and initiate a new connection setup, which is slower and may lead to a perceived call drop.

Architecturally, CRE operates within the RRC protocol layer in the control plane, involving coordination between the UE and the eNodeB (or gNB in NR). Key components include the RLF detection mechanisms in the UE's physical layer, the RRC state management, and the context retention in the network's base station. The procedure relies on the network maintaining the UE context for a short period after RLF, which is managed by timers like the eNodeB's UE context retention timer. CRE is tightly integrated with other mobility procedures, such as handover, as it can be triggered during handover failure scenarios, providing a fallback mechanism to recover the connection.

In the broader network, CRE enhances mobility robustness, especially in challenging radio conditions like cell edges or high-interference environments. It reduces the rate of call drops and improves Key Performance Indicators (KPIs) such as call drop rate and service continuity. The procedure is a foundational aspect of radio link failure recovery, complementing other mechanisms like reconnection without context or connection reconfiguration. Its effectiveness depends on factors like cell preparation, neighbor cell relations, and timer configurations, which are optimized in network planning and operation.

Purpose & Motivation

CRE was introduced to address the critical issue of service interruption due to radio link failures, which were common in mobile networks, especially as data services became more prevalent with 3G and LTE. Prior to CRE, a radio link failure typically forced the UE to drop the call or data session entirely, requiring a full reconnection from scratch. This led to poor user experience, increased signaling load on the network, and higher call drop rates. The motivation was to create a fast recovery mechanism that could salvage an ongoing session by leveraging retained context at the network side, thereby minimizing disruption and improving perceived reliability.

Historically, earlier cellular systems had limited recovery options, often relying on simple reconnection procedures that were slow and inefficient. With the evolution to packet-switched networks in 3GPP Release 5 and beyond, the need for robust mobility management grew, as data sessions (e.g., VoIP, streaming) required low latency and continuity. CRE solved this by providing a standardized procedure that allows quick re-establishment within seconds, reducing the time the UE spends in outage. It specifically targets scenarios where the radio link fails temporarily, such as due to fading, interference, or handover failures, but the core network connection remains intact.

The creation of CRE was driven by the limitations of previous approaches, which lacked context-aware recovery. Without CRE, networks faced increased signaling overhead from frequent full reconnections and degraded QoS for real-time services. By enabling context retention and verification, CRE allows the network to resume sessions efficiently, addressing challenges in mobility and radio resource management. It has become a key feature in LTE and NR for ensuring service continuity, aligning with 3GPP's goals of high reliability and seamless mobility in evolving cellular standards.

Key Features

• Recovers from Radio Link Failure (RLF) by re-establishing the RRC connection
• Uses UE context retention at the eNodeB/gNB for fast session resumption
• Involves security verification via shortMAC-I to prevent unauthorized access
• Reduces service interruption time compared to full reconnection from idle
• Integrates with mobility procedures like handover failure recovery
• Operates on a cell level, allowing re-establishment to same or different prepared cells

Evolution Across Releases

Defining Specifications