Adaptive DRX Cycle Timing for Power and Latency Balance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems face inefficiencies in power consumption and data latency due to suboptimal Discontinuous Reception (DRX) cycle management, particularly in scenarios with varying traffic loads and device capabilities.
Innovation Solution
Implementing adaptive DRX cycle management mechanisms that adjust based on traffic characteristics, device capabilities, and network conditions to optimize power usage and reduce latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by moving object
If traditional fixed DRX cycles are used, then device complexity is reduced and ease of operation is improved, but power consumption efficiency deteriorates and data latency increases under varying traffic loads
Solution Approach 1:
The patent implements dynamic DRX cycle adjustment where the DRX cycle length is not fixed but adapts based on traffic characteristics, device capabilities, and network conditions. The network determines and configures appropriate DRX cycle values for different UEs, transforming the static DRX mechanism into a dynamic one that optimizes power efficiency while managing complexity through network-side control
Solution Approach 2:
The patent changes the parameter values of DRX cycles based on traffic load, device capability, and network conditions. Different DRX cycle configurations are applied according to service types (e.g., eMBB, uRLLC, mMTC), allowing the system to optimize power consumption by adjusting the DRX parameter rather than maintaining a fixed configuration
2Loss of time
If traditional fixed DRX cycles are used, then device complexity is reduced and ease of operation is improved, but data latency worsens under varying traffic loads
Solution Approach 1:
The patent implements dynamic DRX cycle adjustment where the DRX cycle length is not fixed but adapts based on traffic characteristics, device capabilities, and network conditions. The network determines and configures appropriate DRX cycle values for different UEs, transforming the static DRX mechanism into a dynamic one that optimizes power efficiency while managing complexity through network-side control
Solution Approach 2:
The patent changes the parameter values of DRX cycles based on traffic load, device capability, and network conditions. Different DRX cycle configurations are applied according to service types (e.g., eMBB, uRLLC, mMTC), allowing the system to optimize power consumption by adjusting the DRX parameter rather than maintaining a fixed configuration
3Productivity
If adaptive DRX cycle management is implemented, then power consumption efficiency is improved and data latency is reduced, but device complexity increases
Solution Approach 1:
The patent introduces the network as an intermediary that determines and configures DRX cycle parameters for UEs. Instead of requiring complex UE-side decision-making, the network acts as a mediator that receives information about device capabilities and traffic characteristics, then provides appropriate DRX configurations, thereby improving performance while managing complexity centrally
Solution Approach 2:
The patent implements feedback mechanisms where UEs report their capabilities and traffic characteristics to the network, which then determines appropriate DRX cycle configurations. This feedback loop allows the system to optimize network performance by continuously adapting DRX parameters based on actual operating conditions while keeping device complexity manageable through standardized reporting procedures
Data Source
AI summary
A method can include receiving, by a wireless device, one or more discontinuous reception (DRX) configuration parameters indicating: a first DRX cycle; a DRX slot offset; and a DRX on-duration timer. The method can also include determining, for starting the DRX on-duration timer, a DRX cycle. The DRX cycle can be the first DRX cycle, based on the one or more DRX configuration parameters not indicating the second DRX cycle with the non-integer value. Alternatively, the DRX cycle can be the second DRX cycle, based on the one or more DRX configuration parameters indicating the second DRX cycle with the non-integer value. A parameter of the one or more DRX configuration parameters can indicate the non-integer value of the second DRX cycle. The method can further include starting, after the DRX slot offset from a subframe determined based on the DRX cycle, the DRX on-duration timer.


