Description
Contention Based Random Access (CBRA) is a fundamental procedure within the 5G New Radio (NR) Radio Access Network (RAN) defined by 3GPP. It enables a User Equipment (UE) to initiate communication with the gNodeB (gNB) when it lacks a dedicated uplink resource or precise uplink timing alignment. The procedure is termed 'contention-based' because multiple UEs may simultaneously select and transmit the same random access preamble on a shared Physical Random Access Channel (PRACH) occasion, leading to a contention scenario that must be resolved. CBRA is primarily triggered for events such as initial access from RRC_IDLE or RRC_INACTIVE states, RRC Connection Re-establishment, handover, uplink data arrival when out-of-sync, and scheduling request failure recovery.
The CBRA procedure follows a well-defined four-step message exchange, often referred to as the 4-step RACH. In Step 1 (Msg1), the UE selects a random access preamble from a set of contention-based preambles configured by the gNB via system information and transmits it on a PRACH time-frequency resource. The preamble serves as a signature and allows the gNB to estimate the UE's timing advance. In Step 2 (Msg2), the gNB responds with a Random Access Response (RAR) message on the PDSCH, addressed via a Random Access Radio Network Temporary Identifier (RA-RNTI). The RAR conveys an uplink grant for Msg3, a temporary Cell Radio Network Temporary Identifier (TC-RNTI) for the UE, and a timing advance command.
Upon receiving a valid RAR, the UE proceeds to Step 3 (Msg3). Using the granted uplink resource, the UE transmits an RRC message (e.g., RRCSetupRequest, RRCResumeRequest) that contains a unique UE identifier, such as the Resume ID or a random value. This step is critical for contention resolution. Since multiple UEs may have used the same preamble and received the same TC-RNTI and grant, their Msg3 transmissions will collide. The gNB decodes one Msg3 successfully and forwards it to higher layers. Finally, in Step 4 (Msg4), the gNB sends a Contention Resolution message addressed to the UE using the unique identifier from Msg3 (e.g., via the C-RNTI or by echoing the UE's identity in the MAC CE). Only the UE whose identifier matches will consider the procedure successful, declare the TC-RNTI as its C-RNTI, and proceed. Other contending UEs will detect failure, back off, and retry.
The architecture supporting CBRA involves the UE's MAC and PHY layers, the gNB's MAC and PHY layers, and RRC layer signaling. Key physical layer components include the PRACH configuration (preamble format, time/frequency resources), the PDCCH for RAR scheduling (using the RA-RNTI derived from the PRACH occasion), and the PUSCH/PDSCH for Msg3 and Msg4 transport. The procedure's role is pivotal for network entry, uplink synchronization recovery, and connection management, forming the basis for reliable and efficient initial access in 5G networks. Its design balances resource efficiency for massive connectivity scenarios with the need for robust collision handling.
Purpose & Motivation
CBRA exists to provide a scalable and efficient mechanism for UEs to gain initial uplink synchronization and request resources from the network without prior scheduling coordination. In cellular systems, a UE cannot simply start transmitting data; it must first align its uplink timing with the gNB to prevent interference and be granted radio resources. The random access procedure solves this chicken-and-egg problem. The contention-based approach is motivated by the sporadic and unpredictable nature of access attempts from a potentially large population of UEs, making it impractical to assign dedicated resources for each potential access. CBRA allows the network to serve many UEs with a limited set of preamble resources, accepting occasional collisions as a trade-off for reduced signaling overhead and resource reservation.
Historically, contention-based random access has been a cornerstone of cellular systems since GSM (with its RACH) and through UMTS and LTE. Each generation refined the procedure for lower latency and higher reliability. In 5G NR, CBRA addresses the limitations of previous approaches by supporting a wider range of use cases, including enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). For mMTC, handling massive numbers of devices attempting access simultaneously is a key challenge that CBRA addresses through features like enhanced backoff and flexible PRACH resource configuration. Compared to its Contention-Free Random Access (CFRA) counterpart, which uses dedicated preambles assigned by the gNB for specific UEs (e.g., during handover), CBRA is the workhorse for unscheduled, initial access scenarios. Its creation and standardization in 3GPP Rel-15 were driven by the need for a flexible, robust, and efficient access scheme capable of supporting the diverse requirements of 5G, from high-speed smartphones to low-power IoT sensors.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-15, normative work from Rel-19.
In Release 19, a correction was introduced for the selection of the RACH Occasion (RO) type, which applies to both Contention-Free and Contention-Based Random Access (CFRA and CBRA). This specific update refines the procedure for how a UE selects between the first or second PRACH occasions, particularly in scenarios involving Subband Full Duplex (SBFD) operations.
- Corrections on RO type selection for both CFRA and CBRA TS 38.300CR1056
Explore further
Broader topics and technologies where CBRA plays a role.
Defining Specifications
3GPP specifications that define or reference CBRA, 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.391 vj00 | NR; Ambient IoT MAC Protocol Spec | Rel-19 |
| TS 38.523 vj20 | 5G NR UE Conformance Testing: Idle/Inactive | Rel-19 |