UE Delay Status Reporting with Dynamic Latency Budget Criteria
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems face challenges in dynamically managing latency budgets for varying network loads and resource demands, particularly in environments with diverse QoS classes like URLLC and eMBB, leading to inefficient power consumption and performance variability.
Innovation Solution
A user equipment (UE) adjusts delay status report reporting criteria based on latency budget violations and traffic volume changes, using remaining latency budget criteria and step values to optimize reporting configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by moving object
If a RAN node activates a network energy saving mode to reduce power consumption, then energy efficiency is improved, but latency performance may deteriorate due to reduced network resources
Solution Approach 1:
The patent implements dynamic adjustment of delay status report reporting criteria based on network conditions and QoS requirements. The UE adapts reporting behavior in real-time, modifying reporting intervals and thresholds according to current latency budgets and traffic characteristics, allowing the system to optimize between power consumption and latency performance under varying network states
Solution Approach 2:
The system changes reporting parameters (delay status report criteria, reporting intervals, threshold values) based on network conditions and QoS class requirements. By dynamically adjusting these parameters, the system can reduce power consumption during low-activity periods while maintaining acceptable latency performance when needed, effectively resolving the contradiction between energy saving and latency
2Measurement precision
If delay status report reporting criteria are made stringent to improve latency monitoring precision, then measurement precision is improved, but device complexity increases
Solution Approach 1:
The patent applies different delay status report reporting criteria to different QoS classes and traffic types. Each QoS class (e.g., URLLC, eMBB, mMTC) receives customized reporting thresholds and intervals tailored to its specific latency requirements and traffic characteristics, rather than using a uniform complex criterion for all traffic, thus achieving precise monitoring where needed while simplifying overall system complexity
Data Source
AI summary
A radio access network node configures a user equipment with a delay status report reporting configuration, which may comprise a remaining latency budget criterion. The user equipment may analyze a traffic packet stored in a buffer to determine whether the remaining latency budget criterion is violated. If a violation of a remaining latency budget criterion has occurred, the user equipment may transmit a delay status report to the node. If the violation of the remaining latency budget criterion corresponds to an occurrence count that violates a remaining latency budget violation count criterion, the user equipment may adjust a remaining latency budget criterion to result in an adjusted remaining latency budget criterion, which may be used for generation and transmission of future delay status reports corresponding to packets stored in the buffer in the future. A remaining latency budget criterion may be adjusted based on a change in buffered traffic volume.