Random Access Channel

Description

The Random Access Channel (RACH) is a fundamental uplink transport channel in 3GPP radio access networks (UTRAN, E-UTRAN, and NG-RAN). It is a contention-based channel, meaning multiple User Equipments (UEs) may attempt to access it simultaneously, potentially leading to collisions that require resolution procedures. The primary purpose of the RACH is to allow a UE, which is not yet time-synchronized with the network's uplink timing, to request an initial connection, perform handover, re-establish a connection after radio link failure, or request uplink resources for scheduling requests (SR) when no dedicated SR resources are configured.

The RACH procedure, often called Random Access (RA), is a multi-step process. In LTE and NR, it exists in two primary forms: Contention-Based Random Access (CBRA) and Contention-Free Random Access (CFRA). In CBRA, the UE randomly selects a preamble (a specific signal sequence) from a set broadcast by the gNB/eNB and transmits it on the physical random access channel (PRACH). The network, upon detecting the preamble, responds with a Random Access Response (RAR) message containing a temporary identifier (TC-RNTI), timing advance command for synchronization, and an initial uplink grant for the UE to send a scheduled message (like an RRC Connection Request). If multiple UEs select the same preamble simultaneously, a collision occurs, which is resolved in subsequent message exchanges. CFRA is used in scenarios like handover, where the network pre-assigns a dedicated preamble to the UE to avoid contention.

Architecturally, the RACH is mapped to the Physical Random Access Channel (PRACH). The PRACH configuration, including available preamble formats, time/frequency resources (RACH occasions), and root sequences, is broadcast in system information (SIB1/SIB2 in LTE, SIB1 in NR). The UE's physical layer handles the preamble transmission, while higher layers (MAC and RRC) manage the procedure's logic, backoff, and failure handling. The design of preamble formats (e.g., with different lengths) supports various cell sizes and deployment scenarios, from small cells to large rural cells, by accommodating different round-trip time delays.

In the overall network operation, RACH is the critical first step for a UE transitioning from idle (RRC_IDLE) or inactive (RRC_INACTIVE) state to connected (RRC_CONNECTED) state. It is also vital for uplink synchronization maintenance, as the timing advance provided in the RAR ensures orthogonal uplink transmissions from multiple UEs, preventing interference. In 5G NR, enhancements like 2-step RACH were introduced, where the UE combines the preamble (MsgA) and the scheduled message (like Msg3) into a single transmission, reducing latency for access, which is crucial for ultra-reliable low-latency communication (URLLC) use cases.

Purpose & Motivation

The RACH was created to solve the fundamental problem of how an unsynchronized UE can initially contact a cellular network without prior coordination. In early mobile systems, without a mechanism for uplink synchronization, simultaneous transmissions from multiple UEs would cause severe interference, making network access unreliable. The RACH provides a structured, contention-managed method for this initial contact, enabling efficient sharing of the radio medium.

Its design addresses the challenge of random access in a shared medium (the air interface). By using short, detectable preamble sequences, the network can efficiently detect access attempts even with poor timing alignment. The contention resolution mechanism allows the network to handle collisions gracefully, which is inevitable in a system with many potential users. This is far more efficient than dedicated signaling channels for each potential UE, which would waste precious radio resources.

Over generations, the purpose has expanded beyond mere initial access. It now supports critical mobility functions like handover, where a UE needs to quickly synchronize to a new cell. It also serves uplink scheduling requests when a UE has data to send but no dedicated control channel. The evolution towards lower latency, especially in 5G, has driven enhancements like the 2-step RACH, directly addressing the need for faster connection setup in mission-critical and industrial IoT applications.