RNTI

Radio Network Temporary Identifier

Identifier →
Introduced in R99

RNTI is a temporary identifier assigned by the Radio Access Network to a User Equipment to address and distinguish it in the cell for scheduling and secure data transmission in LTE and 5G NR.

Category
Identifier
Introduced
R99
Where
Radio Access Network › NG-RAN (5G)
Specifications
26 specs
RNTI Description Purpose Related Classification Detected Changes Specifications

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.

Classification

Related approachesPDCCHDCI

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 25 changes

In Release 15, the RNTI function saw clarifications and alignments for new procedures, particularly for paging and inactive state operations. This included aligning the terminology and use of the fullI-RNTI and I-RNTI between paging and configurations like InactiveConfig and SuspendConfig. Additionally, corrections were made to the handling of specific RNTIs such as the V-RNTI and the SI-RNTI for MPDCCH.

  • 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
  • Clarification of PDCCH monitoring when not fully aligned with PDCCH periods TS 36.321CR1459
  • CR to 36.331 on alignment of use of fullI-RNTI and I-RNTI in paging and InactiveConfig (Alt.2) TS 36.331CR3810
  • CR on inclusion of TC-RNTI for monitored RNTI for UL-SCH and inclusion of monitoring PDCCH ordering PRACH on SCell TS 38.202CR0007

+ 19 more changes

Rel-16 11 changes

In Release 16, a key addition for the RNTI function was the introduction of the **PUR RNTI** for E-UTRA, as indicated in the Change Request for "Addition of PUR RNTI in E-UTRA related UE identities." Furthermore, this release included specific corrections and enhancements to existing RNTI procedures, such as a "Correction on prioritization between DCP and RAR to C-RNTI for CFRA BFR" and a "Correction on C-RNTI replacement and conditions for 2-step RA," refining the handling of the **Cell Radio Network Temporary Identifier (C-RNTI)**.

  • Addition of PUR RNTI in E-UTRA related UE identities TS 36.300CR1297
  • 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
  • Incorrect restriction for RLC UM radio bearers TS 36.331CR4385
  • 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

+ 5 more changes

Rel-17 4 changes

In Release 17, specific clarifications were introduced regarding the use of RNTIs in procedures like the PDCCH Ordered RACH for an SCell. The release also defined a new UE capability related to limiting PDCCH monitoring, which directly impacts how RNTIs are used for scheduling and control channel decoding. Furthermore, corrections and clarifications were made for PDCCH blind detection in carrier aggregation and for PDCCH skipping behavior.

  • Clarification on the PDCCH Ordered RACH for SCell in 38.300 TS 38.300CR0639
  • New UE capability to limit PDCCH monitoring TS 38.331CR3176
  • Correction on PDCCH blind detection capability in CA TS 38.331CR3430
  • Clarification on PDCCH skipping TS 38.300CR0599
Rel-18 7 changes

In Release 18, specific clarifications were introduced for RNTI-related procedures, including the use of PDCCH ordered contention-free random access (CFRA) for two timing advance groups (2TA) and for system information (SI) request. The release also provided corrections to the applied Transmission Configuration Indicator (TCI) state for multi-TRP PDCCH reception and to the PDCCH configuration for reduced capability (RedCap) UEs' initial bandwidth part.

  • Clarification of satellite identifiers TS 36.300CR1430
  • Clarification of satellite identifiers TS 36.331CR5152
  • Clarification of PDCCH ordered CFRA for 2TA TS 38.300CR0868
  • Clarification on RACH-ConfigCommon for PDCCH order based CFRA and SI request TS 38.331CR4808
  • Correction to applied TCI state for mTRP PDCCH reception TS 38.331CR5200
  • Handling of radio and RLC bearers at LTM cell switch execution in NR-DC TS 38.331CR5383

+ 1 more changes

Rel-19 2 changes

In Release 19, the RNTI function was updated to support common PDCCH repetition for terrestrial networks (TN), enhancing scheduling reliability. Additionally, a correction was applied to the configuration of the NCR-RNTI. These changes were introduced alongside specific enhancements for Non-Terrestrial Networks (NTN) as indicated in the related CR titles.

  • Introduction of common PDCCH repetition (Rel-19 NTN) for TN [Common_PDCCH_rep_TN] TS 38.300CR1058
  • Correction on NCR-RNTI configuration TS 38.331CR5623

Explore further

Broader topics and technologies where RNTI plays a role.

Defining Specifications

3GPP specifications that define or reference RNTI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 23.060 vj00 GPRS Service Description Stage 2 Rel-19
TS 23.221 vj00 3GPP System Architectural Requirements Rel-19
TR 23.923 v1300 Mobile IP+ Feasibility Study for UMTS/GPRS Rel-4
TS 25.301 vj00 UE-UTRAN Radio Interface Protocol Architecture Rel-19
TS 25.302 vj00 UTRA Physical Layer Services Rel-19
TS 25.303 vj00 Radio Resource Control Procedures Rel-19
TS 25.321 vj00 MAC Protocol Specification for UTRAN Rel-19
TS 25.322 vj00 RLC Protocol Specification Rel-19
TS 25.331 vj00 UTRAN RRC Protocol Specification Rel-19
TS 25.401 vj00 UTRAN Overall Architecture Rel-19
TS 25.423 vj00 UTRAN RNSAP Specification Rel-19
TS 25.425 vj00 UTRAN Iur Interface User Plane Protocols Rel-19
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19
TS 36.133 vj20 E-UTRA RRM Requirements 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.331 vj00 LTE RRC Protocol Specification Rel-19
TS 36.401 vj00 E-UTRAN Overall Architecture Description Rel-19
TS 36.766 vf00 LTE BS Interference Cancellation Receiver Study Rel-15
TR 37.901 vf10 UE Application Layer Data Throughput Performance Rel-15
TS 38.202 vj00 5G NR Physical Layer Services Rel-19
TS 38.300 vj00 NG-RAN Overall Description Rel-19
TS 38.331 vj00 NR Radio Resource Control (RRC) Protocol Specification Rel-19
TS 38.521 vj20 NR Physical Layer UE Conformance Testing Rel-19
TS 43.130 vj00 Iur-g Interface Overview Rel-19