Description
Contention Free Random Access (CFRA) is a specialized random access procedure defined in 3GPP 5G New Radio (NR) standards. Unlike the Contention Based Random Access (CBRA) procedure, where multiple User Equipments (UEs) may attempt to access the network using the same pool of preambles, leading to potential collisions, CFRA assigns a dedicated, contention-free preamble to a specific UE. This dedicated preamble is allocated by the gNodeB (gNB) via Radio Resource Control (RRC) signaling, typically in messages like the RRCReconfiguration, or via a PDCCH order in the downlink. The procedure is initiated for specific, scheduled events where low latency and high reliability are paramount, such as during a handover command execution or in response to a beam failure recovery request.
The CFRA procedure architecture is integrated within the overall NR Layer 2 and Layer 3 protocols. The key components involved are the UE's Medium Access Control (MAC) entity and the gNB's MAC scheduler. When the gNB decides a UE needs to perform CFRA—for instance, during a handover to a target cell—it provides the UE with a set of dedicated random access resources. These resources include a specific preamble index (from the set of 64 preambles available in a cell) and a specific Physical Random Access Channel (PRACH) occasion (time/frequency resource). The UE then transmits this dedicated preamble on the assigned PRACH occasion. Since this preamble is uniquely assigned for that event, no other UE is using it, guaranteeing that the gNB will receive it without collision.
Upon detecting the dedicated preamble, the gNB sends a Random Access Response (RAR) message on the Physical Downlink Shared Channel (PDSCH), addressed to the Random Access Radio Network Temporary Identifier (RA-RNTI) calculated from the PRACH occasion. The RAR contains a timing advance command and an uplink grant for the UE's subsequent message (Msg3), which in CFRA is typically an RRCReconfigurationComplete or a C-RNTI MAC Control Element. The absence of contention eliminates the need for a contention resolution step (Msg4), which is mandatory in CBRA. This reduction in steps directly translates to lower access latency, often critical for maintaining seamless connectivity during high-speed mobility or for resuming communication after a beam failure.
CFRA plays a critical role in the 5G NR radio access network by enabling fast and deterministic initial uplink synchronization. Its primary operational roles are in handover execution, where a UE must quickly access a target cell; in beam failure recovery, where a UE needs to rapidly report a new candidate beam to the gNB; and in the establishment of uplink synchronization for scheduling request (SR) resources when none are available. By providing a collision-free path, CFRA enhances the reliability and reduces the latency of these control-plane procedures, which is foundational for supporting 5G's stringent requirements for enhanced Mobile Broadband (eMBB), massive Machine-Type Communications (mMTC), and particularly Ultra-Reliable Low-Latency Communications (URLLC).
Purpose & Motivation
CFRA was introduced to address the inherent limitations of the traditional Contention Based Random Access (CBRA) procedure in scenarios where access delay and reliability are critical. In LTE and early mobile systems, CBRA was sufficient for initial network access. However, it involves a four-message handshake with a probabilistic collision resolution step, introducing variable and potentially high latency. For advanced 5G use cases like factory automation, autonomous vehicles, and seamless high-mobility handovers, this unpredictable delay is unacceptable. CFRA was created to provide a deterministic, low-latency access mechanism for scheduled, time-critical events.
The historical context stems from the evolution of mobility and reliability requirements. In LTE, a form of contention-free random access was already defined for handovers, but 5G NR formalized and enhanced the mechanism to be more integral and flexible, particularly to support beam-centric operations. The limitation of CBRA is its statistical nature: as network load increases, the probability of preamble collision rises, leading to access failures, retransmissions, and increased latency. For procedures like handover, where a UE is transitioning between cells, any delay or failure can lead to radio link failure (RLF) and dropped calls. CFRA solves this by pre-allocating resources, guaranteeing successful preamble transmission on the first attempt.
Furthermore, the creation of CFRA was motivated by the need to support 5G's advanced antenna systems and beamforming. In a beamformed network, a UE's connection is maintained via specific directional beams. If a beam fails, the UE must quickly report this to the gNB to switch to a new beam—a process known as beam failure recovery (BFR). Using CBRA for BFR would be too slow and unreliable. CFRA provides a fast-track channel for the UE to send a BFR request using a dedicated preamble, enabling rapid beam recovery and maintaining the high-quality link required for millimeter-wave (mmWave) frequencies and URLLC services. Thus, CFRA is a foundational enabler for 5G's performance targets.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (7 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the CFRA function was enhanced to support PDCCH order-triggered random access for LTM cell switch procedures from the source cell. It also introduced the capability for CFRA to be initiated towards one or multiple candidate cells based on such an order. Furthermore, the dedicated RACH configuration for CFRA was defined to include a quality threshold, with these resources being prioritized by the UE as long as the threshold is met.
In Release 16, enhancements to CFRA (Contention Free Random Access) introduced a specific correction for the prioritization between DCP and RAR to C-RNTI during a CFRA procedure used for Beam Failure Recovery (BFR). This refinement ensures clear procedural ordering when the UE receives specific messages for beam failure recovery.
- Correction on prioritization between DCP and RAR to C-RNTI for CFRA BFR TS 38.300CR0295
In Release 17, the enhancements for CFRA primarily involved its application in new procedures and clearer operational guidelines. Specifically, CFRA was integrated into the LTM (Layer Triggered Mobility) cell switch procedure, where it can be triggered by a PDCCH order from the source cell for access to a candidate cell. Additionally, refinements were made to the pathloss calculation for a PDCCH order triggered PRACH by allowing the pathloss offset to be indicated by that order.
In Release 18, a key clarification was introduced for Contention Free Random Access (CFRA) specifically regarding the procedure triggered by a PDCCH order for Dual Active Protocol Stack (DAPS) Handover. The enhancement provides explicit operational details for the scenario where the UE performs a CFRA procedure towards a target cell while maintaining its connection to the source gNB, as defined within the DAPS Handover framework.
- Clarification of PDCCH ordered CFRA for 2TA TS 38.300CR0868
In Release 19, the key update for CFRA was the introduction of corrections for RACH Occasion (RO) type selection, ensuring proper configuration and prioritization between CFRA and Contention-Based Random Access (CBRA). This refinement directly impacts procedures where dedicated RACH resources are provided, such as during a DAPS Handover or when triggered by a PDCCH order, to maintain the priority of these contention-free resources as long as their configured quality threshold is met.
- Corrections on RO type selection for both CFRA and CBRA TS 38.300CR1056
Explore further
Broader topics and technologies where CFRA plays a role.
Defining Specifications
3GPP specifications that define or reference CFRA, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 38.300 vj00 | NG-RAN Overall Description | Rel-19 |
| TS 38.523 vj20 | 5G NR UE Conformance Testing: Idle/Inactive | Rel-19 |