PUCCH Scheduling Request Handling in Dynamic TDD Uplinks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems face challenges in allocating scheduling request (SR) resources efficiently without interfering with other UEs, particularly in dynamic TDD configurations where semi-static SR opportunities may conflict with dynamically changing UL/DL assignments, leading to potential interference and latency issues.
Innovation Solution
The proposed method involves configuring SR resources to be exclusively within semi-static UL slots or symbols, allowing for flexible SR transmission without overlapping with dynamic TDD configurations, and includes techniques for handling conflicts through methods such as skipping SR transmissions or piggybacking on available PUCCH/PUSCH resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If semi-static SR opportunities are configured in dynamic TDD environments, then SR transmission can be supported, but interference with other UEs and slot boundary violations may occur
Solution Approach 1:
The patent applies dynamics by making the SR resource allocation adaptive to dynamic TDD configurations. The gNB dynamically determines whether to allocate SR resources based on current UL/DL assignments, and the UE adapts its SR transmission behavior accordingly - either transmitting on allocated resources or skipping transmission when conflicts are detected. This dynamic adjustment resolves the contradiction by enabling SR support while preventing interference through real-time configuration changes.
Solution Approach 2:
The patent changes the parameter of SR resource allocation from fixed semi-static configuration to dynamic allocation based on TDD configuration. By modifying the allocation parameters according to current system conditions (UL/DL assignments), the system can support SR transmission when resources are available while avoiding interference when they are not, thus resolving the technical contradiction.
2Object-affected harmful factors
If SR resources are allocated dynamically, then interference is avoided, but latency increases due to additional conflict detection and resolution steps
Solution Approach 1:
The patent applies preliminary action by having the gNB pre-determine and allocate SR resources based on anticipated TDD configurations before actual SR transmission occurs. The UE is provided with advance knowledge of SR resource allocations, allowing it to prepare for transmission without requiring real-time conflict detection. This reduces latency while maintaining interference avoidance through the preliminary planning of resource allocations.
Solution Approach 2:
The UE performs self-service by autonomously determining whether to transmit SR based on pre-allocated resources and current configuration, without requiring additional signaling or conflict detection procedures. The UE can independently assess whether allocated resources are valid and proceed with transmission or skipping accordingly, reducing latency while avoiding interference.
3Loss of time
If mini-slot or symbol-level SR reception is implemented, then latency is reduced, but slot boundary violations may occur
Solution Approach 1:
The patent applies local quality by allowing mini-slot or symbol-level SR reception only in specific local regions where it does not violate slot boundaries. The gNB carefully selects allocation positions within the TDD configuration that enable shortened SR transmission while maintaining proper slot structure. This localized approach reduces latency for SR transmission while preserving slot boundary integrity in the overall frame structure.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method performed by a user equipment, UE, in a wireless communication system, the method comprising: receiving, by the UE, from a base station, configuration information related to configured grant; and performing, by the UE, physical uplink shared channel, PUSCH, transmissions based on the configuration information, wherein the configuration information includes a slot-level repetition number and a non-slot-level repetition number, wherein the slot-level repetition number indicates a first number of consecutive slots allocated within the configured grant period, and wherein the non-slot-level repetition number indicates a second number of consecutive PUSCH allocations within a slot.