Description
The Radio Network Temporary Identifier (RNTI) is a fundamental addressing mechanism in 3GPP LTE (E-UTRA) and 5G NR (New Radio) networks. It is a 16-bit or 24-bit value assigned by the gNB (in NR) or eNB (in LTE) to a specific User Equipment (UE) or a group of UEs for the duration of a connection or a specific procedure. The RNTI is not a permanent subscriber identity like the IMSI; it is a temporary, context-specific identifier used exclusively over the Uu radio interface between the UE and the base station. Its primary role is to scramble the Cyclic Redundancy Check (CRC) attached to Downlink Control Information (DCI) messages carried on the Physical Downlink Control Channel (PDCCH). When a UE successfully descrambles a DCI CRC using its assigned RNTI, it knows the subsequent scheduling information on the PDSCH or PUSCH is intended for it.
Architecturally, RNTIs operate within the Medium Access Control (MAC) and Physical (PHY) layers. The base station's scheduler uses different types of RNTIs to manage various channels and procedures. For example, the Cell-RNTI (C-RNTI) is uniquely assigned to a UE in RRC_CONNECTED state for user-plane data scheduling. The Temporary C-RNTI is used during random access. Other RNTIs, like the Paging RNTI (P-RNTI) and System Information RNTI (SI-RNTI), are common to all UEs in a cell for broadcasting paging messages and system information blocks (SIBs), respectively. The process is dynamic: a UE monitors the PDCCH for DCI formats scrambled with RNTIs relevant to its state. Upon detection, it decodes the associated data channel (PDSCH for downlink, PUSCH for uplink) as instructed by the DCI.
The RNTI mechanism is key to network efficiency and security. It enables precise scheduling and multiplexing of multiple UEs on shared time-frequency resources. By using different RNTI types, the network can efficiently manage common procedures (broadcast, paging, random access) and dedicated connections without permanent identity exposure over the air, enhancing user privacy. In 5G NR, the concept was extended with additional RNTI types, such as the Configured Scheduling RNTI (CS-RNTI) for grant-free uplink transmission and the Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI) for specific MCS table indications, supporting more advanced features and use cases.
Purpose & Motivation
The RNTI was introduced to solve critical problems of efficient radio resource management and user privacy in packet-switched cellular systems, evolving from the Temporary Logical Link Identifier (TLLI) in GPRS. In earlier circuit-switched systems, a channel was dedicated for the call duration, requiring less dynamic addressing. With the advent of LTE's all-IP, shared-channel architecture, a mechanism was needed to quickly and uniquely address a specific UE among hundreds in a cell for each transmission time interval (TTI), without using permanent identifiers that would compromise security.
Its creation was motivated by the need for a low-overhead, fast scheduling identifier. The RNTI allows the base station scheduler to direct control information to the correct UE with minimal bits. By scrambling the DCI CRC, it provides both addressing and a light integrity check. This design is far more efficient than embedding a full address inside every control message. It also solves the problem of contention in common channels; for instance, the Random Access RNTI (RA-RNTI) identifies which time-frequency resource a random access preamble was sent on, allowing the network to respond to the correct UE even before a dedicated C-RNTI is assigned.
Furthermore, RNTIs address the limitation of static addressing in a highly mobile environment. As a UE moves, its serving cell changes, and so can its C-RNTI. This temporary, cell-specific nature simplifies handover procedures and cell reselection. The evolution into 5G NR required new RNTI types to support features like bandwidth parts, ultra-reliable low-latency communication (URLLC), and network slicing, demonstrating the RNTI's flexibility as a core building block for dynamic radio resource allocation in modern cellular networks.
Key Features
- 16-bit (LTE) or 24-bit (5G NR) temporary identifier assigned by the RAN
- Scrambles the CRC of Downlink Control Information (DCI) on PDCCH
- Multiple types for different purposes (C-RNTI, P-RNTI, SI-RNTI, RA-RNTI)
- Enables efficient scheduling and multiplexing of UEs on shared channels
- Enhances air interface security by avoiding transmission of permanent IDs
- Dynamic assignment and change during handover and connection states
Evolution Across Releases
The RNTI concept was introduced in the UMTS Terrestrial Radio Access Network (UTRAN) specifications, primarily for HSDPA operation. It served as a temporary identifier for user equipment in the CELL_DCH state, used by the Node B for scheduling and addressing on the High-Speed Downlink Shared Channel (HS-DSCH).
Fundamentally redesigned and expanded for LTE (E-UTRAN). The RNTI became a central element of the OFDMA/SC-FDMA scheduling framework, with a standardized set of types (C-RNTI, P-RNTI, SI-RNTI, RA-RNTI) and a defined role in scrambling PDCCH DCI, forming the core of dynamic resource allocation.
Extended for 5G New Radio (NR). Introduced a flexible RNTI size (16-bit or 24-bit) to support larger cell capacities. Added new RNTI types like CS-RNTI for configured grant uplink, MCS-C-RNTI for MCS table indication, and INT-RNTI for pre-emption indication, supporting advanced NR features like URLLC and enhanced mobile broadband.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 23.060 | 3GPP TS 23.060 |
| TS 23.221 | 3GPP TS 23.221 |
| TS 23.923 | 3GPP TS 23.923 |
| TS 25.301 | 3GPP TS 25.301 |
| TS 25.302 | 3GPP TS 25.302 |
| TS 25.303 | 3GPP TS 25.303 |
| TS 25.321 | 3GPP TS 25.321 |
| TS 25.322 | 3GPP TS 25.322 |
| TS 25.331 | 3GPP TS 25.331 |
| TS 25.401 | 3GPP TS 25.401 |
| TS 25.423 | 3GPP TS 25.423 |
| TS 25.425 | 3GPP TS 25.425 |
| TS 25.931 | 3GPP TS 25.931 |
| TS 36.133 | 3GPP TR 36.133 |
| TS 36.300 | 3GPP TR 36.300 |
| TS 36.321 | 3GPP TR 36.321 |
| TS 36.331 | 3GPP TR 36.331 |
| TS 36.401 | 3GPP TR 36.401 |
| TS 36.766 | 3GPP TR 36.766 |
| TS 37.901 | 3GPP TR 37.901 |
| TS 38.202 | 3GPP TR 38.202 |
| TS 38.300 | 3GPP TR 38.300 |
| TS 38.331 | 3GPP TR 38.331 |
| TS 38.521 | 3GPP TR 38.521 |
| TS 43.130 | 3GPP TR 43.130 |