Configured Grant Uplink Scheduling for Latency-Sensitive Traffic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Wireless communication systems face challenges in managing uplink traffic via configured grant (CG) periods with multiple shared channel occasions, particularly in scenarios where spans of PUSCH occasions from different CG periods overlap, leading to scheduling ambiguities and resource use discrepancies.
Innovation Solution
Implementing signaling- or configuration-based mechanisms that include rules for avoiding time domain overlapping between spans of PUSCH occasions within different CG periods, allowing for staggered offsets of multi-PUSCH occasion CGs to align with data generation periodicity, and calculating starting symbols based on CG period durations to ensure efficient resource allocation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple PUSCH occasions are configured within different CG periods, then uplink data transmission capacity is improved, but scheduling ambiguity and resource allocation conflicts occur when spans overlap in time
Solution Approach 1:
The network entity pre-configures multiple CG periods with multiple PUSCH occasions each, and pre-establishes time domain overlapping rules and skipping mechanisms before actual data transmission occurs. This preliminary configuration enables the UE to autonomously resolve scheduling ambiguities without real-time network intervention, maintaining both high transmission capacity and scheduling reliability
Solution Approach 2:
Time domain overlapping rules act as an intermediary mechanism between multiple CG periods. When spans of PUSCH occasions from different CG periods overlap, the overlapping rules determine which occasions to skip or prioritize, resolving conflicts without requiring additional signaling overhead or reducing transmission capacity
2Loss of energy
If CG periods are staggered to align with data generation periodicity, then spectral efficiency is improved, but complexity in calculating starting symbols and managing multiple CG configurations increases
Solution Approach 1:
The network entity configures multiple CG periods with different starting symbols and periodicities to match various data generation patterns. By adjusting these parameters, the system optimizes spectral efficiency for different traffic types while the UE manages the configurations using standardized procedures defined in the specification
Solution Approach 2:
The uplink transmission resource is segmented into multiple independent CG periods, each with its own PUSCH occasions, starting symbols, and periodicities. This segmentation allows the system to handle different data generation periodicities simultaneously while maintaining manageable configuration complexity through modular structure
3Adaptability or versatility
If spans of PUSCH occasions from different CG periods overlap in time, then resource utilization flexibility is improved, but ambiguity in determining which occasions to use increases
Solution Approach 1:
The UE autonomously resolves scheduling ambiguities in overlapping PUSCH occasions by applying time domain overlapping rules and skipping mechanisms defined in the specification. The network entity provides the configuration and rules, but the UE independently makes scheduling decisions without requiring real-time network coordination, maintaining both flexibility and operational simplicity
Data Source
AI summary
Methods, systems, and devices for wireless communications are described. In some systems, a user equipment (UE) and a network entity may support one or more mechanisms according to which the UE and the network entity may avoid glitches in latency-sensitive traffic and reduce ambiguity relating to scheduling and resource use expectations for configured grant (CG) periods including multiple shared channel occasions. Such mechanisms may include a rule according to which the UE and the network entity expect spans of shared channel occasions within different CG periods to avoid overlapping in time. The rule may preclude any time domain overlapping between spans of shared channel occasions within different CG periods or may allow for a time domain overlapping between spans of shared channel occasions within different CG periods and instead indicate how a UE is expected to use shared channel occasions of overlapping spans of shared channel occasions.