Uplink ACK Codebook Prioritization for Acknowledgement Collisions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communications networks face challenges in efficiently handling acknowledgement collisions for different service types with varying quality of service requirements, such as eMBB and URLLC, leading to conflicts in uplink communications resources.
Innovation Solution
A method for a communications device to prioritize and transmit acknowledgement information using higher-priority uplink resources in case of collisions, based on predetermined prioritization rules and codebooks, ensuring timely and appropriate transmission of acknowledgement status for different service types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple service types (eMBB, URLLC) share uplink communications resources for acknowledgement transmission, then resource utilization improves, but acknowledgement collision and transmission reliability deteriorate
Solution Approach 1:
The patent segments uplink communications resources into multiple codebooks (first codebook for eMBB, second codebook for URLLC) with different priorities. This segmentation allows separate handling of different service types, preventing acknowledgement collisions while maintaining high resource utilization through priority-based transmission rules.
2Loss of time
If acknowledgement information is transmitted using higher-priority uplink resources, then transmission timeliness improves, but resource allocation complexity increases
Solution Approach 1:
The patent establishes predetermined prioritization rules and codebook assignments before acknowledgements need to be transmitted. The first codebook is assigned higher priority for time-sensitive services, while the second codebook handles other services. This preliminary configuration eliminates the need for complex real-time decisions, reducing device complexity while ensuring timely transmission.
3Adaptability or versatility
If different codebooks are used for different service types, then service differentiation improves, but device complexity increases
Solution Approach 1:
The patent applies local quality by assigning specific codebooks to specific service types based on their requirements. The first codebook is optimized for eMBB services with higher priority, while the second codebook serves URLLC and other services. This localized optimization provides service differentiation while keeping device complexity manageable through clear, service-specific mappings.
Data Source
AI summary
A method includes receiving one or more first downlink data blocks and one or more second downlink data blocks, for each of the one or more first downlink data blocks and one or more second downlink data blocks determining an acknowledgement status, the acknowledgement status indicating whether the downlink data block was correctly received or not received correctly (ACK/NACK), receiving an indication of first uplink communications resources allocated for transmitting first acknowledgement information including the acknowledgement status for the one or more first downlink data blocks, determining that the first uplink communications resources are allocated for the transmission of acknowledgement information generated in accordance with a first codebook, the first codebook for generating acknowledgement information associated with the one or more first downlink data blocks, and receiving an indication of second uplink communications resources allocated for transmitting second acknowledgement information including the acknowledgement status for the second downlink data blocks.