CBRA

Contention Based Random Access

Radio Access Network →
Introduced in Rel-15

CBRA is a random access procedure in 5G NR where multiple UEs can attempt access by transmitting on the same preamble resource, enabling efficient initial access and uplink resynchronization despite potential contention.

Category
Radio Access Network
Introduced
Rel-15
Where
Radio Access Network › NG-RAN (5G)
Specifications
3 specs
CBRA Description Purpose Related Classification Detected Changes Specifications

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

Part ofPRACH
Related approachesCFRA

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (19 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 3 changes

In Release 15, the CBRA function was enhanced with the introduction of the 2-step random access type, defined by new message sequences MSGA (preamble and payload) and MSGB (the network's response). The release also brought clarifications for SSB-based procedures and specifications for carrier selection during the random access process.

  • Clarification on SSB-based BM, RLM and BFD TS 38.300CR0102
  • Random Access Triggers TS 38.300CR0106
  • CR on the carrier selection for random access TS 38.300CR0134
Rel-16 3 changes

In Release 16, the CBRA function was enhanced for specific scenarios, including the introduction of a new A-IoT CBRA procedure with defined A-IoT MSG1 and A-IoT MSG2 messages. Furthermore, the release introduced mechanisms for prioritization between DCP and RAR to C-RNTI specifically for the CFRA BFR procedure, refining the interaction between different random access types.

  • Introduction of Inter-gNB CSI-RS Based Mobility TS 38.300CR0249
  • Correction on CSI-RS Based Intra-frequency and Inter-frequency Measurement Definition TS 38.300CR0265
  • Correction on prioritization between DCP and RAR to C-RNTI for CFRA BFR TS 38.300CR0295
Rel-17 4 changes

In Release 17, the CBRA function was enhanced with specific support for A-IoT (Aerial Internet of Things) procedures, defining new message types like A-IoT MSG1 and A-IoT MSG2 for direct device-to-network random access. The release also introduced clarifications on applying slice-based RACH configuration and provided updates for Non-Terrestrial Networks (NTN) with specific considerations for cell reselection and random access. Furthermore, an editor's note regarding the PRACH sequence length of 1151 was formally removed from the specification.

  • Clarification on BFD-RS set based BFR TS 38.300CR0596
  • NSAG for cell reselection and random access TS 38.300CR0604
  • Removal of editor's note on sequence length 1151 for PRACH usage TS 38.300CR0621
  • Clarification on the application of slice-based RACH configuration TS 38.300CR0666
Rel-18 6 changes

In Release 18, specific corrections and clarifications were made to the CBRA function, including a clarification for PDCCH ordered CFRA procedures for 2TA. Furthermore, the release introduced the new "A-IoT CBRA" procedure, defining the initial "A-IoT MSG1" and response "A-IoT MSG2" messages for device-to-network random access.

  • Correction of timer-based conditional handover for NR NTN TS 38.300CR0822
  • Clarification of PDCCH ordered CFRA for 2TA TS 38.300CR0868
  • Correction on DL PSI based discard TS 38.300CR0874
  • Correction on priority-based QoE measurements in TS 38.300 TS 38.300CR0919
  • Gap requirement for CSI-RS based measurements and inter-RAT measurements TS 38.300CR0908
  • Correction on location based measurements in NR NTN TS 38.300CR0910
Rel-19 3 changes

In Release 19, the primary update for the Contention Based Random Access (CBRA) function was a correction to the RO (RACH Occasion) type selection procedure, which applies to both CFRA and CBRA. This correction ensures the proper selection mechanism functions as intended across these random access types. The release also introduced specific support for the A-IoT CBRA procedure, defining the related A-IoT MSG1 and A-IoT MSG2 message exchanges for device-to-repeater communication.

  • Corrections on RO type selection for both CFRA and CBRA TS 38.300CR1056
  • Support for Continuous Management-based MDT TS 38.300CR1068
  • Correction of time-based handover for NR NTN TS 38.300CR1109

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.

SpecificationTitleRelease
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