Single Cell Radio Network Temporary Identifier

Description

The Single Cell Radio Network Temporary Identifier (SC-RNTI) is a critical identifier within the LTE Radio Access Network (RAN), specifically defined in the context of the MAC (Medium Access Control) layer. It is a 16-bit value, similar to other RNTI types, used by the eNodeB to address a specific User Equipment (UE) on the Physical Downlink Control Channel (PDCCH) for the purpose of scheduling uplink or downlink shared channel resources. Unlike the Cell RNTI (C-RNTI), which is the primary identifier for a UE in RRC_CONNECTED mode and is cell-specific but can be maintained during handovers, the SC-RNTI is explicitly designed for use within the confines of a single cell. Its allocation and usage are tightly coupled to specific MAC procedures.

Operationally, the SC-RNTI is assigned to a UE by the eNodeB during particular events. A primary use case is during the Random Access Channel (RACH) procedure for contention-based random access. When a UE transmits a Random Access Preamble (Msg1), the eNodeB responds with a Random Access Response (RAR, Msg2) on the PDSCH. The scheduling information for this RAR is indicated on the PDCCH addressed to the RA-RNTI, which is common for that time-frequency resource. However, for subsequent messages, if the UE is being granted resources for Msg3 (the first scheduled uplink transmission containing the UE identity) or for an early contention resolution message, the eNodeB may use the Temporary C-RNTI (which becomes the C-RNTI upon successful contention resolution) or, in defined scenarios, an SC-RNTI. The 3GPP specifications (TS 36.321 for MAC) detail the precise conditions under which an SC-RNTI is used for addressing specific MAC control elements or data.

Architecturally, the SC-RNTI resides in the MAC sublayer of the eNodeB and the UE. The eNodeB's scheduler uses the SC-RNTI value to scramble the Cyclic Redundancy Check (CRC) bits of a Downlink Control Information (DCI) format transmitted on the PDCCH. The UE continuously monitors the PDCCH for DCI formats scrambled with RNTIs it has been configured to monitor. When a UE detects a DCI with a CRC scrambled by its assigned SC-RNTI, it knows the associated grant or assignment on the PDSCH or PUSCH is intended for it. This mechanism allows for highly efficient, low-overhead addressing of a specific UE without requiring explicit higher-layer addressing in every transmission. Its role is particularly important for optimizing signaling efficiency for infrequent or small data bursts, helping to reduce control channel overhead and battery consumption for the UE.

Purpose & Motivation

The SC-RNTI was introduced to provide a streamlined, temporary identifier for efficient radio resource management within a single LTE cell, addressing specific scenarios where the full, permanent C-RNTI is unnecessary or inefficient. Prior to its explicit definition, temporary identifiers were used, but the SC-RNTI formalized a clear mechanism for single-cell operations. The primary problem it solves is the need for a low-overhead method to schedule resources for a UE during transient states or for specific procedures without conferring the full privileges and persistence of a C-RNTI.

Historically, as LTE networks evolved to support a massive number of devices, including those for Machine-Type Communication (MTC) and the Internet of Things (IoT), optimizing every bit of control signaling became paramount. Procedures like random access and the transmission of small data packets are critical for network entry and efficient operation. Using a dedicated C-RNTI for every minor interaction could be wasteful. The SC-RNTI provides a middle ground—a UE-specific identifier that the network can use temporarily for a confined purpose within one cell, after which it can be released. This is especially useful in scenarios like early data transmission or for specific MAC control elements where the communication context is limited and handover is not a consideration. It addresses the limitation of using common RNTIs (like RA-RNTI or P-RNTI) for group messages or broadcast, which lack user specificity, and the limitation of always using a C-RNTI, which implies a more stable RRC connection and consumes a longer-term identifier resource in the eNodeB's management tables.