Description
The Random Access Radio Network Temporary Identifier (RA-RNTI) is a crucial temporary identifier used during the Random Access Channel (RACH) procedure in 3GPP LTE and NR systems. Its primary function is to address a specific User Equipment (UE) or group of UEs in the initial downlink message (Random Access Response, RAR) from the network before a unique UE-specific identifier like C-RNTI is established or confirmed. The RA-RNTI is not assigned by the network via signaling; instead, it is algorithmically determined by both the UE and the base station (eNodeB/gNB) based on the physical radio resources used for the preamble transmission.
How it works is integral to the contention-based random access process. When a UE needs to initiate communication (e.g., during initial access, handover, or uplink synchronization), it selects and transmits a Random Access Preamble on a specific Physical Random Access Channel (PRACH) occasion. A PRACH occasion is defined by a specific time (system frame and subframe/slot) and frequency resource. The UE then calculates the RA-RNTI using a standardized formula: RA-RNTI = 1 + s_id + 14 * t_id + 14 * 80 * f_id + 14 * 80 * 8 * ul_carrier_id (for LTE, with variations for NR). Here, s_id, t_id, and f_id are indices for the subframe, time, and frequency resource of the preamble, respectively. The UE monitors the downlink control channel (PDCCH) scrambled with this calculated RA-RNTI for the RAR message.
The network (gNB/eNodeB), upon detecting a preamble on that specific PRACH occasion, calculates the identical RA-RNTI. It then transmits the RAR message on the Downlink Shared Channel (PDSCH), and signals its presence by sending a Downlink Control Information (DCI) format on the PDCCH scrambled with that RA-RNTI. This allows all UEs that transmitted a preamble in that resource to detect the message, but the RAR contains a temporary identifier (Temporary C-RNTI) and a timing advance command intended for the successful UE. The RA-RNTI thus serves as a resource-specific address for the initial step of contention resolution, bridging the unidentified uplink transmission to a targeted downlink response.
Purpose & Motivation
The RA-RNTI was introduced with LTE in 3GPP Release 8 to solve a key problem in the contention-based random access procedure: how does the network send a response to a UE whose identity is not yet known? In previous systems, initial access mechanisms were less efficient. The RA-RNTI provides an elegant, resource-based addressing scheme that avoids the need for explicit identity signaling in the first uplink message (the preamble, which carries no UE ID).
This design is motivated by the need for efficiency and scalability. The preamble is a short, simple signal to minimize interference and detection complexity. Embedding a full UE identity would make it longer and more complex. Instead, the RA-RNTI leverages the uniqueness of the time-frequency resource used for the preamble as a temporary, implicit address. This allows the network's response to be efficiently broadcast to all UEs that might have used that resource (addressing potential collisions), while being targeted enough to avoid overwhelming all UEs with all responses.
It addresses the limitation of having no established signaling connection. Before the RACH procedure, the UE may not have a C-RNTI (in case of initial access) or may have an outdated one (in case of radio link failure). The RA-RNTI provides the necessary hook for the first downlink control message, enabling the establishment or resumption of a proper RRC connection and the assignment of a permanent or semi-persistent identifier, which is fundamental for network mobility and resource management.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (28 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-8, normative work from Rel-15.
In Release 15, a correction was made to the RA-RNTI range specifically for use on a non-anchor carrier. This change ensured the RA-RNTI calculation remained unique and functional when the random access procedure was initiated on carriers other than the anchor, as part of broader enhancements for carrier selection and random access triggers.
- Introduction of New Radio Access Technology in TS 36.300 TS 36.300CR0998
- Clarifying PDCCH Period Definition TS 36.321CR1300
- Defining PDCCH-Subframes for NB-IoT UE TS 36.321CR1327
- Corrections to random access power control for TDD in 36.321 TS 36.321CR1362
- Correction on Random Access Preamble groups for EDT TS 36.321CR1446
- Clarification of PDCCH monitoring when not fully aligned with PDCCH periods TS 36.321CR1459
+ 8 more changes
In Release 16, a specific correction was made to the RA-RNTI function regarding prioritization between a DCP (Discontinuous Reception Cycle) indication and a Random Access Response (RAR) addressed to a C-RNTI during a Contention-Free Random Access (CFRA) procedure for Beam Failure Recovery (BFR). This change ensured clear procedural handling to avoid conflicts when these two downlink control messages occurred simultaneously.
- Introducing UE Radio Capability Mapping procedure for EN-DC TS 36.300CR1314
- PDCCH-based HARQ-ACK for a specific HARQ process with multi-TB scheduling TS 36.321CR1517
- Correction on prioritization between DCP and RAR to C-RNTI for CFRA BFR TS 38.300CR0295
- Dynamic UMTS Radio Capability impact on SRVCC and RACS TS 38.300CR0317
- Supporting use of UE Radio Capability for Paging in RRC_INACTIVE TS 38.300CR0380
- Handling of UE Radio Capability for Paging in NB-IoT and eMTC TS 36.300CR1263
+ 1 more changes
In Release 17, the RA-RNTI function was updated with clarifications on PDCCH Ordered RACH procedures for SCell, as detailed in the 38.300 specification. The release also included clarifications on PDCCH skipping and provided a Non-Stand Alone Guidance (NSAG) for cell reselection and random access procedures. Additionally, an editor's note regarding the PRACH sequence length of 1151 was formally removed from the specification text.
In Release 18, the RA-RNTI function was updated to provide clarification for satellite identifiers and for PDCCH ordered contention-free random access (CFRA) procedures involving two timing advance groups (2TA). These changes ensure the RA-RNTI calculation and usage remain unambiguous in non-terrestrial networks and in advanced multi-TA scenarios.
In Release 19, the RA-RNTI function was enhanced to support common PDCCH repetition for Terrestrial Networks (TN), a feature initially developed for Non-Terrestrial Networks (NTN). This introduces a new procedure where the network can transmit repeated Physical Downlink Control Channel (PDCCH) orders, which are addressed using the RA-RNTI, to improve reliability. The change allows the UE to receive and combine these repeated transmissions for more robust random access response reception.
- Introduction of common PDCCH repetition (Rel-19 NTN) for TN [Common_PDCCH_rep_TN] TS 38.300CR1058
Explore further
Broader topics and technologies where RA-RNTI plays a role.
Defining Specifications
3GPP specifications that define or reference RA-RNTI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |
| TS 36.321 vj00 | E-UTRA MAC Protocol Specification | Rel-19 |
| TS 36.401 vj00 | E-UTRAN Overall Architecture Description | Rel-19 |
| TS 38.300 vj00 | NG-RAN Overall Description | Rel-19 |