Inactive RNTI

Description

The Inactive Radio Network Temporary Identifier (I-RNTI) is a crucial identifier in the 5G New Radio (NR) Radio Resource Control (RRC) protocol, introduced as part of the RRC_INACTIVE state in 3GPP Release 15. It serves as a unique, context-specific identifier for a User Equipment (UE) while it is in the RRC_INACTIVE state, a low-power state designed for infrequent data transmission. The I-RNTI is allocated by the serving gNB (Next Generation NodeB) when it transitions the UE from RRC_CONNECTED to RRC_INACTIVE. This identifier is stored as part of the UE's Access Stratum (AS) context, which is also retained in the gNB and, in the case of a CU-DU split architecture, may be managed by the Central Unit (CU). The primary technical operation involving the I-RNTI is the RRC Resume procedure. When downlink data arrives for an inactive UE, the RAN initiates a RAN-based paging message within the configured RAN Notification Area (RNA). This paging message includes the UE's I-RNTI. The UE, monitoring paging occasions, recognizes its I-RNTI and initiates a connection resume request to the gNB, providing the I-RNTI. The gNB uses this I-RNTI to retrieve the stored UE context, allowing for a rapid resumption of the connection without the need for a full RRC setup and Service Request procedure involving the core network. The I-RNTI structure can be of two types: the full I-RNTI, which includes the gNB identity and a UE-specific suffix, or the short I-RNTI, a more compact form. Its specification and usage are detailed in 3GPP TS 38.300 (NR overall description) and the RRC protocol specifications (TS 38.331).

Purpose & Motivation

The I-RNTI was created to address the key requirements of 5G NR for massive Machine-Type Communications (mMTC) and enhanced Mobile Broadband (eMBB): ultra-low power consumption and reduced signaling latency for sporadic data transfers. Previous LTE states, RRC_IDLE and RRC_CONNECTED, presented a trade-off. IDLE mode saved power but required a lengthy core-network-involved procedure to resume data transfer. CONNECTED mode kept resources ready but consumed significant UE battery power. The RRC_INACTIVE state, enabled by the I-RNTI, introduces a third state that combines benefits of both. The I-RNTI solves the problem of efficiently and uniquely identifying a specific UE's stored context within the RAN during inactivity. Without it, the network would have to use a core-network identifier (like the S-TMSI) for paging, which would not directly point to the RAN context, forcing a slower resume process or a full reconnect. By providing a RAN-local handle, the I-RNTI enables RAN-based paging and context retrieval, drastically cutting the control-plane delay and signaling load for state transitions. This is essential for IoT devices sending small, infrequent data packets and for smartphones maintaining always-on applications with minimal battery impact.