Description
The Configured Scheduling RNTI (CS-RNTI) is a critical identifier in the 5G New Radio (NR) physical layer and MAC layer operations, specifically designed to support configured grant (CG) Type 1 and Type 2 transmissions. As defined in 3GPP specifications 38.213 (Physical layer procedures for control) and 38.321 (Medium Access Control protocol specification), CS-RNTI serves as a UE-specific 16-bit value that identifies a user equipment (UE) for the purpose of configured uplink grants. Unlike dynamically scheduled transmissions that require continuous Downlink Control Information (DCI) signaling for each transmission opportunity, CS-RNTI enables semi-persistent scheduling where transmission parameters are pre-configured via RRC signaling and activated/deactivated via specific DCI formats.
Architecturally, CS-RNTI operates within the gNB's MAC scheduler and the UE's MAC entity. When a UE is configured for configured grant operation, the gNB assigns a unique CS-RNTI value through RRC signaling (SystemInformationBlockType1 or dedicated RRC signaling). This identifier is then used to scramble the CRC of specific DCI formats (Format 0_0 or 0_1 with specific fields) that activate, deactivate, or retransmit configured grants. The CS-RNTI allows the UE to recognize that a received DCI pertains to its configured grant resources rather than dynamic scheduling, triggering the appropriate MAC procedures without requiring explicit resource allocation for each transmission.
In configured grant Type 1, all transmission parameters (time-domain resources, frequency-domain resources, MCS, etc.) are fully configured via RRC signaling, and the CS-RNTI is used primarily for activation/deactivation and retransmission commands. For configured grant Type 2, basic parameters are configured via RRC, but the actual activation uses DCI format 0_1 scrambled with CS-RNTI, providing more dynamic control. The CS-RNTI enables hybrid automatic repeat request (HARQ) processes specifically for configured grants, with the HARQ process ID derived from the configured grant configuration index and system frame number, allowing predictable retransmission behavior.
The CS-RNTI's role extends beyond mere identification—it enables efficient resource utilization for periodic traffic patterns characteristic of industrial automation, voice over NR, and other low-latency applications. By eliminating the need for scheduling requests and grant reception for each transmission, CS-RNTI reduces control channel overhead, decreases latency (as UEs can transmit immediately when data arrives), and conserves UE power by minimizing monitoring of PDCCH for dynamic grants. The identifier is cell-specific and reconfigured during handover procedures, ensuring continuity of configured grant services during mobility events.
Purpose & Motivation
CS-RNTI was created to address the limitations of purely dynamic scheduling in 4G LTE for applications requiring deterministic, low-latency communication with periodic traffic patterns. In traditional dynamic scheduling, each uplink transmission requires a scheduling request from the UE, a downlink grant from the gNB, and subsequent data transmission—introducing significant latency (typically 8-14 ms in LTE) and control channel overhead. For industrial IoT, factory automation, and ultra-reliable low-latency communications (URLLC) use cases in 5G, this approach was inadequate for meeting stringent latency requirements (often sub-1ms) and efficient resource utilization for predictable traffic.
The motivation for CS-RNTI emerged from the need to support semi-persistent scheduling (SPS) in 5G NR with enhanced flexibility compared to LTE SPS. While LTE introduced SPS for voice over LTE (VoLTE), it had limitations in configuration flexibility and was primarily designed for periodic traffic with fixed intervals. 5G NR's configured grant mechanism, enabled by CS-RNTI, provides two types of configuration (Type 1 fully RRC-configured and Type 2 RRC+DCI activated) to accommodate diverse service requirements. CS-RNTI specifically solves the problem of how to efficiently signal activation, deactivation, and retransmission commands for pre-configured resources without requiring separate UE identifiers or complex signaling procedures.
Historically, the concept builds upon LTE's SPS-C-RNTI but extends it with 5G-specific enhancements. The creation of CS-RNTI was driven by 3GPP's work on NR URLLC in Release 15, where reducing control plane latency and overhead was paramount. By enabling UEs to transmit immediately on pre-configured resources identified by their CS-RNTI, the system eliminates the scheduling request-grant cycle, directly addressing the latency and reliability requirements of critical communications while maintaining efficient spectrum utilization through statistical multiplexing of configured grant resources among multiple UEs.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (45 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the CS-RNTI function was refined through corrections and clarifications for configured grant operations, including adjustments to Power Headroom Report (PHR) timing, Scheduling Request (SR) triggering, and formula corrections. Specific handling was defined for scenarios such as overlapped configured grants and uplink grants received in a Random Access Response (RAR), and a missing case for Downlink Control Information (DCI) format 1_1 with CS-RNTI was addressed. Additionally, the release introduced the MCS-C-RNTI as a new identifier alongside these enhancements to the configured scheduling framework.
- Correction on PHR timing for configured grant TS 38.213CR0029
- CR on missing case for DCI format 1_1 with CS-RNTI TS 38.213CR0035
- Correction to SR triggering to accommodate the configured grant TS 38.321CR0115
- Correction of Configured Grant formula TS 38.321CR0094
- Corrections on Configured Grants and SPS TS 38.321CR0262
- Introduction of MCS-C-RNTI TS 38.321CR0290
+ 3 more changes
In Release 16, the CS-RNTI function was enhanced with specific corrections and clarifications for industrial IoT (IIoT) and unlicensed spectrum operation. These included miscellaneous corrections for NR unlicensed configured grant and a dedicated MAC Change Request for configured grant related to IIoT. Furthermore, the release introduced clarifications on configured grant (re-)initialization and corrections for handling DRX with bundle transmission of configured uplink grant.
- Introduction of NR-DC in same Frequency Range and of Cross-carrier Scheduling with Different Numerologies TS 38.213CR0077
- Corrections on NR-DC and on Cross-carrier Scheduling with Different Numerologies TS 38.213CR0086
- Corrections on NR-DC and on Cross-carrier Scheduling with Different Numerologies TS 38.213CR0111
- CR to 38.213 on HARQ-ACK processing timeline for DCI format 1_1 with Scell dormancy indication without scheduling PDSCH TS 38.213CR0135
- Miscellaneous corrections on NR unlicensed configured grant TS 38.213CR0159
- Correction on PDCCH monitoring on cell(s) configured with Rel-15 PDCCH monitoring capability TS 38.213CR0170
+ 11 more changes
In Release 17, the CS-RNTI function was enhanced with clarifications and corrections for HARQ-ACK codebook generation when both spatial and time bundling are configured for configured grants. Additionally, specific corrections were introduced regarding the PUCCH resource allocation for UEs operating in NACK-only feedback mode for Semi-Persistent Scheduling (SPS).
- Correction on Type-2 HARQ CB generation when both of spatial bundling and time bundling are configured TS 38.213CR0349
- Correction on Type-2 HARQ CB generation when time bundling is configured but spatial bundling is not configured TS 38.213CR0350
- Correction for BD/CCE budget of scheduling cell(s) in FR2-2 TS 38.213CR0373
- CR on SS0 availability for scheduling MBS to TS 38.213 TS 38.213CR0399
- Correction of number of configured DL-CCs for BD/CCE budget for FR2-2 TS 38.213CR0425
- CR on PUCCH resource for UE configured with NACK-only mode2 for SPS TS 38.213CR0452
+ 2 more changes
In Release 18, the CS-RNTI function was enhanced with corrections and clarifications for multi-PUSCH configured grant operations and for the validity of configured uplink grants used in Small Data Transmission (SDT). Additionally, specific corrections were made to procedures involving HARQ-ACK codebooks and skipping for multi-cell and multi-slot scheduling scenarios managed by the CS-RNTI.
- Correction on HARQ-ACK skipping for Rel-18 multi-cell scheduling TS 38.213CR0673
- Correction on transition time of UL BWP change triggered by DCI format 0_1 scheduling multiple PUSCHs TS 38.213CR0693
- SDT BFR timer being not configured [RA-SDT_BeamFailure] TS 38.321CR1814
- Correction to multi-PUSCH configured grant TS 38.321CR2002
- Correction on Type-2 HARQ-ACK codebook for multi-slot scheduling TS 38.213CR0522
- Path Loss reference RS for SCell UL PC when PL RS is not configured TS 38.213CR0535
+ 5 more changes
Explore further
Broader topics and technologies where CS-RNTI plays a role.
Defining Specifications
3GPP specifications that define or reference CS-RNTI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 38.213 vj10 | NR Physical Layer Control Procedures | Rel-19 |
| TS 38.321 vj00 | NR MAC Protocol Specification | Rel-19 |