HARQ Process Management for URLLC and eMBB
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile communication networks face challenges in efficiently managing and scheduling data traffic, particularly in scenarios with varying wireless device capabilities and network configurations, leading to suboptimal performance and resource utilization in 5G and LTE environments.
Innovation Solution
The implementation of advanced protocol stacks and scheduling processes within the New Radio (NR) framework, including bandwidth adaptation, carrier aggregation, and dynamic resource allocation, to optimize data transmission and reception across diverse wireless devices and network conditions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple HARQ processes are configured for URLLC retransmissions, then retransmission capability is improved, but process collision with eMBB transmissions occurs
Solution Approach 1:
The patent segments HARQ process management by introducing separate HARQ process spaces for URLLC and eMBB transmissions. URLLC transmissions use dedicated HARQ process IDs (e.g., 0-3) while eMBB uses other process IDs, preventing collision between the two service types while maintaining independent retransmission capabilities for each.
Solution Approach 2:
The patent implements dynamic HARQ process allocation where the network can flexibly assign and release HARQ processes based on current traffic conditions. When URLLC traffic arrives, dedicated HARQ processes are allocated; when eMBB traffic dominates, those processes are released for eMBB use, optimizing resource utilization dynamically.
2Reliability
If dedicated HARQ processes are allocated for URLLC, then URLLC reliability is improved, but resource utilization efficiency deteriorates
Solution Approach 1:
The patent implements dynamic HARQ process allocation where dedicated URLLC HARQ processes are allocated only when URLLC traffic is detected. The network monitors for URLLC data arrivals and activates dedicated HARQ processes at that moment, releasing them when not needed, thus maintaining high reliability when required while optimizing resource utilization during normal operation.
Solution Approach 2:
The patent changes the operational state of HARQ processes based on traffic conditions. HARQ processes can be in an active state dedicated to URLLC or a released state available for eMBB, with the network dynamically transitioning between these states based on real-time traffic demands, optimizing both reliability and efficiency.
3Productivity
If HARQ process space is shared between URLLC and eMBB, then resource efficiency is improved, but service quality differentiation deteriorates
Solution Approach 1:
The patent segments the HARQ process space into distinct domains: dedicated HARQ processes for URLLC (with specific ID ranges) and shared HARQ processes for eMBB. This segmentation ensures that URLLC transmissions have guaranteed resources with predictable performance while eMBB can utilize remaining resources, maintaining service quality differentiation.
Solution Approach 2:
The patent applies different quality characteristics to different parts of the HARQ resource space. URLLC-dedicated HARQ processes are configured with parameters optimized for low latency and high reliability (e.g., shorter time windows, specific process counts), while eMBB-shared processes use parameters optimized for throughput, ensuring each service type receives appropriate quality of service.
Data Source
AI summary
A wireless device receives downlink control information (DCI) comprising a first HARQ process identifier and a resource assignment. The first HARQ process identifier indicates a first HARQ process of HARQ processes. The wireless device transmits, using the resource assignment and based on a second HARQ process identifier, a transport block associated with a second HARQ process, of the HARQ processes. The second HARQ process identifier indicates the second HARQ process and is based on the first HARQ process identifier and a HARQ process identifier offset.