Description
The G-CS-RNTI (Group Configured Scheduling Radio Network Temporary Identifier) is a specialized RNTI introduced in 3GPP Release 17 for 5G New Radio (NR) to support group-based configured scheduling, a feature critical for massive Machine-Type Communication (mMTC) and Internet of Things (IoT) scenarios. It operates within the Medium Access Control (MAC) and Radio Resource Control (RRC) layers, as detailed in specifications 38.321 and 38.331. Unlike UE-specific RNTIs like the C-RNTI, the G-CS-RNTI is shared by a group of UEs that have been configured with identical semi-persistent scheduling (SPS) parameters for uplink transmissions. This group configuration is established via RRC signaling, where the network assigns the G-CS-RNTI value and associated SPS resources, such as periodicity, time/frequency allocations, and modulation and coding schemes, to multiple devices simultaneously.
When a UE is configured with a G-CS-RNTI, it monitors the Physical Downlink Control Channel (PDCCH) for Downlink Control Information (DCI) scrambled with this identifier. Upon detecting such a DCI, all UEs in the group interpret it as an activation, deactivation, or retransmission command for their pre-configured SPS resources, as per 38.213. This mechanism allows the network to manage resources for numerous UEs with a single control message, drastically reducing the control signaling overhead that would otherwise be required if each UE were addressed individually. The G-CS-RNTI is particularly effective for applications with periodic, predictable traffic patterns, such as sensor data reporting or smart meter readings, where devices transmit small packets at regular intervals.
Architecturally, the G-CS-RNTI integrates with the NR MAC scheduler in the gNB, which handles resource allocation and scheduling decisions. Key components include the RRC protocol for configuration management, the MAC layer for scheduling activation, and the physical layer for PDCCH processing. Its role is to enhance spectral efficiency and device battery life by minimizing the need for frequent scheduling requests and grants, thereby supporting scalable IoT deployments. The G-CS-RNTI also complements other NR features like power saving modes and coverage enhancement techniques, ensuring reliable and efficient operation in diverse mMTC environments.
Purpose & Motivation
The G-CS-RNTI was created to address the escalating demands of massive IoT deployments in 5G networks, where traditional per-UE scheduling mechanisms become inefficient and resource-intensive. Prior to Release 17, configured scheduling in NR relied on UE-specific SPS, which required individual RRC configurations and DCI activations for each device, leading to excessive control channel congestion and signaling overhead. This approach was unsustainable for scenarios involving thousands of low-power, periodic-transmission devices, such as in smart cities or industrial IoT, as it drained network capacity and increased UE power consumption due to frequent monitoring and signaling interactions.
Motivated by the need for scalability and energy efficiency in mMTC, 3GPP introduced group-based configured scheduling with the G-CS-RNTI in Release 17. This innovation solves the problem of inefficient resource management for periodic traffic by enabling a single control message to schedule multiple UEs simultaneously. Historical context includes earlier LTE enhancements like eMTC and NB-IoT, which offered group scheduling but were limited to narrower bandwidths and simpler use cases; the G-CS-RNTI extends these concepts to the more flexible and high-capacity 5G NR framework. It directly addresses limitations of previous approaches by reducing PDCCH blind decoding attempts, lowering latency for group activations, and conserving UE battery life through minimized signaling, thereby supporting the 5G vision of connecting a massive number of devices seamlessly.
Furthermore, the G-CS-RNTI facilitates network slicing for IoT services by allowing efficient resource partitioning for different device groups. It aligns with 3GPP's ongoing efforts to optimize NR for diverse verticals, ensuring that 5G can meet the stringent requirements of ultra-reliable low-latency communication (URLLC) and enhanced mobile broadband (eMBB) alongside mMTC. By solving these core challenges, the G-CS-RNTI plays a pivotal role in enabling cost-effective and scalable IoT solutions within the 5G ecosystem.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (172 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the G-CS-RNTI function was newly introduced to enable group-based configured grant transmissions. This identifier allows the network to schedule or activate uplink resources for multiple UEs simultaneously, supporting efficient small data transmission. The release included corrections and clarifications related to configured grant procedures, such as the timing for Power Headroom Reports (PHR) and the formula for configured grant calculations.
- PDCCH monitoring for overlapped CORESETs TS 38.213CR0018
- CR on QCL assumption for receiving PDCCH for RAR TS 38.213CR0026
- Correction on PHR timing for configured grant TS 38.213CR0029
- Correction on PDCCH monitoring TS 38.213CR0040
- CR on PDCCH Monitoring for NR-DC TS 38.213CR0048
- Clarifications on dynamic scheduling TS 38.300CR0083
+ 37 more changes
In Release 16, the G-CS-RNTI function was enhanced to support new features including secondary DRX groups and operations for NR-DC (NR Dual Connectivity) with cross-carrier scheduling. These enhancements required corrections and clarifications to the UE's PDCCH monitoring procedures and HARQ-ACK codebook determination, particularly for scenarios involving dormancy indication and configured grant transmissions. The updates ensured proper operation of group-based scheduling across the more complex carrier aggregation and dual connectivity frameworks introduced in this release.
- Introduction of NR-DC in same Frequency Range and of Cross-carrier Scheduling with Different Numerologies TS 38.213CR0077
- Implementing confirmation of code block group based transmission TS 38.331CR1717
- Introduction of secondary DRX group CR 38.321 TS 38.321CR0746
- Introduction of secondary DRX group CR 38.331 TS 38.331CR1632
- NR-DC Cell Group capability filtering TS 38.331CR2703
- Corrections on NR-DC and on Cross-carrier Scheduling with Different Numerologies TS 38.213CR0086
+ 41 more changes
In Release 17, the enhancements for the G-CS-RNTI function primarily involved corrections and clarifications to PDCCH monitoring procedures to ensure reliable scheduling. This included specific corrections for multi-slot PDCCH monitoring in NR-DC and CA scenarios with mixed capability types and for operations in the FR2-2 frequency range. Additionally, refinements were made to procedures for PDCCH skipping and to the handling of the BD/CCE budget for scheduling cells in FR2-2.
- Explicit Indication of SI Scheduling window position [SI-SCHEDULING] TS 38.331CR2953
- Adding UE capability of CSI reporting cross PUCCH SCell group TS 38.331CR3144
- CR on PDCCH repetition with SSSG switching TS 38.213CR0332
- Correction on the tables for determining Type0 PDCCH monitoring occasions TS 38.213CR0337
- Correction on multi-slot PDCCH monitoring in NR-DC and CA scenarios with mixed capability types TS 38.213CR0342
- Corrections on PDCCH monitoring enhancement for 52-71GHz spectrum TS 38.213CR0346
+ 34 more changes
In Release 18, the G-CS-RNTI function was enhanced to support multi-cell scheduling, where a single DCI can schedule multiple PUSCHs across non-consecutive slots in FR1. The release also introduced corrections and clarifications for its operation, including handling for the joint TCI state configuration and the applicable BWP during such multi-cell scheduling procedures.
- Correction to 38.300 for multi-cell scheduling TS 38.300CR0832
- Introduction of Multiple PUSCH scheduling by single DCI for non-consecutive slots in FR1 [M-PUSCH in FR1] TS 38.331CR4629
- Corrections and Updates to UE capabilities for RAN1 feature group 55-6 TS 38.331CR4862
- CR on PDCCH monitoring for dedicated spectrum less than 5 MHz TS 38.213CR0596
- 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
+ 30 more changes
In Release 19, the enhancements for G-CS-RNTI primarily focused on improving reliability for common control channels, specifically introducing PDCCH repetitions for the Type0-PDCCH Common Search Space (CSS) set in Terrestrial Networks (TNs). This includes the introduction of common PDCCH repetition for both TNs and Non-Terrestrial Networks (NTN), alongside technical alignments such as corrections for parameters related to intra-slot PDCCH repetition. These updates build upon the existing framework where the UE determines a CORESET for the Type0-PDCCH CSS set from the MIB upon detection of an SS/PBCH block.
- Introduction of PDCCH repetitions for Type0-PDCCH CSS set in TNs [Common_PDCCH_Rep_TN] TS 38.213CR0748
- Introduction of common PDCCH repetition (Rel-19 NTN) for TN [Common_PDCCH_rep_TN] TS 38.300CR1058
- Correction on PDCCH candidates skipping for receiving RAR when overlapping with candidate SSB TS 38.213CR0755
- Alignment on parameter for intra-slot PDCCH repetition TS 38.213CR0761
- CR for Autonomous updates of the UE-specific TA or common TA in an OCC group in NR NTN TS 38.213CR0763
- Correction on dependency of group-based beam reporting TS 38.331CR5544
Explore further
Broader topics and technologies where G-CS-RNTI plays a role.
Defining Specifications
3GPP specifications that define or reference G-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.300 vj00 | NG-RAN Overall Description | Rel-19 |
| TS 38.321 vj00 | NR MAC Protocol Specification | Rel-19 |
| TS 38.331 vj00 | NR Radio Resource Control (RRC) Protocol Specification | Rel-19 |