Semi-Persistent Scheduling & Configured Grants

SPS lifecycle, CG Type 1/2, K-repetition, PDCCH overhead savings & 6G AI-driven adaptation

← MAC Overview ← Scheduling Master SR & RA Fallback → DL Assignment → BSR → LCP → PHR → TA → DRX → ☆ Energy-Saving MAC

1. The Problem — PDCCH Overhead for Periodic Traffic

For predictable periodic traffic like Voice over NR (VoNR, 20 ms) or URLLC telemetry, dynamic scheduling wastes enormous PDCCH resources — one DCI per packet. SPS and CG pre-allocate periodic resources with a single activation DCI, saving up to 99.9% PDCCH overhead.

Dynamic Scheduling

Every packet needs a DCI. 50 VoNR UEs = 2,500 CCEs/sec on PDCCH. Limits cell capacity for other users.

SPS (Downlink)

One activation DCI → periodic PDSCH without new DCI. 95%+ PDCCH savings for periodic DL traffic.

CG (Uplink)

One activation DCI (or none for Type 1) → periodic PUSCH. UE transmits without waiting for grants.

2. SPS — Semi-Persistent Scheduling (Downlink)

SPS pre-allocates periodic PDSCH resources. The gNB configures periodicity via RRC, activates with a single DCI (CS-RNTI), and the UE receives PDSCH on every occasion without a new DCI. Retransmissions use dynamic grants (C-RNTI).

🎛️ SPS Lifecycle — Activation → Periodic PDSCH → Deactivation

Watch the complete SPS lifecycle: RRC config → activation DCI → periodic PDSCH (no DCI) → deactivation DCI.

PhaseTriggerWhat Happens
RRC ConfigRRC ReconfigurationCS-RNTI, periodicity, PUCCH resource configured
ActivationDCI with CS-RNTIUE validates DCI → starts periodic PDSCH
Periodic PDSCHEvery period (no DCI)UE receives and decodes → sends HARQ-ACK on PUCCH
RetransmissionDynamic DCI (C-RNTI)If NACK, gNB sends reTX via dynamic grant
DeactivationDCI with CS-RNTIUE stops periodic PDSCH

3. Configured Grants (Uplink)

🔄 CG Type 1 vs Type 2 — Side-by-Side Comparison

Compare the activation flows: Type 1 needs only RRC (immediate), Type 2 needs RRC + activation DCI (flexible MCS).

CG Type 1 (RRC-only)

All parameters in RRC. Active immediately after config. No DCI needed. Best for handover — CG ready before data arrives.

CG Type 2 (RRC + DCI)

Periodicity in RRC. MCS/RBs via activation DCI. Can be deactivated. More flexible — gNB chooses MCS per activation.

Up to 4 CG Configs

Per BWP (Rel-16). Different periodicities for VoNR (20 ms), URLLC (2 ms), IoT (100 ms). UE selects based on LC→LCG→CG mapping.

4. CG K-Repetition — Reliability Without Retransmissions

K-repetition transmits each CG packet K times with cycling RV values (0→2→3→1). gNB combines all K transmissions for higher decoding probability. Essential for URLLC (10⁻⁵ BLER target).

🔁 K-Repetition with RV Cycling

Adjust K and watch the repetition pattern. Higher K = more reliability but more resource usage. gNB can early-terminate if decoded before all K.

5. PDCCH Overhead Savings — Quantified

📊 Dynamic vs SPS/CG — PDCCH Overhead Comparison

Adjust the number of VoNR UEs and see the PDCCH CCE consumption. Dynamic scheduling saturates PDCCH quickly; SPS/CG barely uses it.

20
MetricDynamicSPS / CG
DCIs per UE/sec50~0.05
CCEs per UE/sec150~0.15
Grant latency per packet1–2 ms0 ms
PDCCH utilization (20 UEs)60%< 1%

6. Use Cases — VoNR, URLLC, V2X

VoNR Voice

CG period: 20 ms (matches AMR-WB codec). TB: 40-60 bytes. MCS: 4 (QPSK). 24-32 RBs. During silence: SID every 160 ms or deactivate.

URLLC Control

CG period: 0.5-2 ms. K-rep: 4-8. Priority: 1 (high). MCS: 6. 32-64 bytes. Latency: ~1 ms. Reliability: 10⁻⁵ BLER.

V2X Sidelink

SL CG Type 1. Period: 100 ms (CAM). Works out-of-coverage. No gNB needed. Deterministic timing for safety.

IoT Telemetry

CG Type 2 (on-demand). Period: 100 ms. MCS: 10 (16-QAM). 48 RBs. Activated when data arrives.

7. Practical Field Considerations

ScenarioPeriodTypeK-repMCSPriority
VoNR voice20 msCG-1140 (normal)
VoNR SID160 msCG-1120
URLLC control2 msCG-1461 (high)
IoT telemetry100 msCG-21100
V2X CAM100 msSL-1280
Common pitfall: SPS periodicity must match the actual codec period. Voice codec = 20 ms but SPS set to 40 ms → every other packet needs dynamic grant → defeats the purpose of SPS entirely.

LTE vs 5G NR

AspectLTE (SPS only)5G NR (SPS + CG)
DirectionSPS (DL + UL shared)SPS (DL) + CG (UL) separate
Types1 typeCG Type 1 + Type 2
Max configs18 SPS + 4 CG per BWP
Min period10 ms2 symbols
K-repetitionNoneUp to K=8

8. 6G Evolution — AI-Driven SPS/CG

AI Period Adaptation

AI monitors traffic and adjusts CG period in real-time: 20 ms (talk) → 160 ms (silence) → 5 ms (burst). 40-60% resource savings.

Predictive CG

AI predicts data arrival → activates CG before data arrives → zero activation latency. Deactivates when burst ends.

Multi-Link CG

CG on cell + WiFi + satellite. AI selects best link per packet. 99.9999% reliability via multi-link diversity.

SPS for ISAC

SPS carries both data AND radar sensing signals. Deterministic timing for range/Doppler. Zero extra overhead.

🚀 SPS/CG Evolution — 4G to 6G

Compare SPS/CG capabilities across generations: configs, min period, K-repetition, and AI features.

Dimension4G (LTE)5G NR6G (Target)
DLSPSSPS (8 configs)AI-adaptive SPS
ULSPS (shared)CG Type 1/2 (4 configs)Predictive CG
Min period10 ms2 symbols< 1 symbol
K-repetitionNoneUp to 8Up to 32
Period adaptationManualManualAI-driven
SensingNoneNoneSPS for ISAC
← MAC Overview ← Scheduling Master SR & RA Fallback → DL Assignment → BSR → LCP → PHR → TA → DRX → ☆ Energy-Saving MAC