Configured Grant PUSCH Repetition for Low-Latency Uplink Scheduling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing number of communication devices and data volume in wireless networks necessitates a method to efficiently utilize limited radio resources for uplink and downlink data and control information transmission, particularly in high-density node and user equipment scenarios, while addressing varying service requirements and latency challenges.
Innovation Solution
The implementation involves optimizing the transmission and reception of wireless communication signals using techniques such as carrier aggregation, cognitive radio, and multi-base station cooperation to enhance mobile broadband communication, supporting diverse services with different reliability and latency sensitivities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the number of user equipment and data volume increase to satisfy growing communication demands, then communication capacity and data throughput increase, but radio resource availability per device decreases and resource utilization efficiency deteriorates
Solution Approach 1:
The patent segments the uplink transmission resources by dividing the physical uplink shared channel (PUSCH) transmission into multiple opportunities with different repetition factors. This allows the system to allocate resources more granularly, assigning different numbers of repetitions to different UEs or data packets based on their specific requirements, thereby improving overall resource utilization efficiency while maintaining high data throughput for multiple devices
Solution Approach 2:
The patent implements dynamic resource allocation by allowing the base station to flexibly adjust the number of PUSCH repetitions and transmission opportunities based on real-time channel conditions, buffer status, and UE requirements. This dynamic adaptation enables the system to optimize radio resource usage under varying load conditions, preventing resource waste while ensuring sufficient capacity for high-throughput applications
2Reliability
If transmission resources are increased to improve communication reliability and data throughput, then service quality improves, but resource utilization efficiency and system scalability deteriorate
Solution Approach 1:
The patent changes the parameter of transmission repetition count based on service requirements and channel conditions. By adjusting the number of PUSCH repetitions dynamically, the system can ensure high communication reliability for critical services while using fewer repetitions for less critical traffic, thereby maintaining overall resource utilization efficiency. The base station can select from multiple repetition factors (e.g., 1, 2, 4, 8) to match the required reliability level for each transmission
Solution Approach 2:
The patent creates a universal PUSCH transmission framework that can handle multiple service types (eMBB, mMTC, URLLC) with different reliability requirements using the same resource allocation mechanism. The configured grant Type 2 approach provides a multi-functional solution that adapts to various service scenarios without requiring separate dedicated resource pools, thus improving resource utilization efficiency while maintaining high reliability for all service types
3Loss of time
If latency is reduced to meet URLLC requirements, then response time improves, but resource allocation complexity and system design difficulty increase
Solution Approach 1:
The patent applies preliminary action by pre-configuring grant parameters and transmission opportunities before actual data transmission is needed. The base station configures multiple PUSCH transmission opportunities with predetermined repetition factors in advance, allowing UEs to immediately transmit data when needed without complex real-time scheduling decisions. This pre-configuration approach reduces latency for URLLC while keeping resource allocation management relatively simple through template-based configurations
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
In the present specification, a user equipment may: receive RRC configuration including first configuration information relating to a first DCI format and second configuration information relating to a second DCI format; receive a configured grant configuration including a repetition scheme and resource allocation information; determine resource allocation of a configured grant on the basis of i) configuration information, which includes the same repetition scheme as the repetition scheme in the configured grant configuration, among the first configuration information and the second configuration information, and ii) the resource allocation information; and perform PUSCH transmission on the basis of the resource allocation. Each of the first configuration information and the second configuration information may include a TDRA table.