Joint Downlink-Uplink Scheduling for Low-Latency 5G Traffic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing 5G NR systems face challenges in efficiently managing the varying resource demands and latency requirements of different quality-of-service classes, particularly for applications like virtual reality, which require high-capacity and low-latency communications, while also optimizing power consumption in mobile devices.
Innovation Solution
User equipment transmits an application-type indication message to the radio access network, receiving a joint downlink-uplink scheduling configuration to manage traffic flows based on application-specific search spaces, allowing for dynamic scheduling of downlink and uplink traffic to prioritize critical packets and optimize resource allocation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If conventional separate downlink and uplink scheduling is used, then device complexity is reduced, but latency requirement cannot be satisfied for URLLC applications
Solution Approach 1:
The patent combines separate downlink and uplink scheduling into a unified joint scheduling mechanism. The RAN node transmits a single DCI message that simultaneously schedules both downlink data reception and uplink data transmission, eliminating the need for separate scheduling procedures and reducing overall latency for time-critical applications.
Solution Approach 2:
The joint scheduling configuration is prepared and transmitted in advance as a configurable pattern. The RAN node pre-configures the joint DL-UL scheduling parameters including time offsets and resource allocations, allowing the UE to execute the scheduling without real-time computation delays, thus satisfying stringent latency requirements.
2Loss of time
If joint downlink-uplink scheduling configuration is implemented, then latency requirement is satisfied, but device complexity increases
Solution Approach 1:
The patent transforms the complex joint scheduling problem into manageable parameters by configuring specific time offsets (e.g., timeOffsetDL2UL) and resource allocation patterns. These parameterized configurations allow the UE to compute scheduling decisions through simple arithmetic operations rather than complex optimization algorithms, reducing computational complexity while maintaining low latency.
3Adaptability or versatility
If dynamic scheduling is used for varying application demands, then adaptability is improved, but device complexity increases
Solution Approach 1:
The patent implements dynamic adaptability through configurable joint scheduling patterns that can be adjusted based on application requirements. The RAN node can modify time offsets, resource allocations, and scheduling frequencies dynamically while maintaining a structured framework that limits computational complexity at the UE side through pre-defined configuration options.
4Reliability
If application-specific search space monitoring is implemented, then reliability is improved, but power consumption increases
Solution Approach 1:
The patent applies local quality by creating application-specific search spaces tailored to different QoS requirements. URLLC applications monitor dedicated search spaces with high reliability configurations, while eMBB applications use different search space configurations. This localized optimization ensures high reliability for critical applications without requiring all applications to maintain maximum power consumption levels.
Data Source
AI summary
A user equipment transmits, to a RAN node, application-specific information that may comprise quality of service class identifiers associated with traffic flows corresponding to the application. Responsive to the application-specific information, the user equipment receives, from the node, configuration information corresponding to an application-specific downlink search space, which may be monitored or decoded using the configuration information by the user equipment to determine a joint downlink-uplink configuration. The joint downlink-uplink configuration may indicate downlink resources to use for receiving application-flow-specific downlink traffic and the joint downlink-uplink configuration may indicate uplink resources to be used to transmit application-flow-specific uplink traffic that is linked to, or corresponds to, the application-flow-specific downlink traffic. The user equipment may be configured to transmit an estimated buffer status report indicating estimated uplink traffic to be transmitted corresponding to application-flow-specific downlink traffic.