Multi-Flow DRX Parameter Configuration for XR Delay Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current DRX configurations in the NR system do not adequately match the features of multiple data flows in extended reality (XR) services, leading to delays and reduced network capacity due to mismatched data flow arrival times, resulting in inefficient energy consumption by terminal devices.
Innovation Solution
Configuring multiple groups of DRX parameters for different data flows based on their specific time features, such as data arrival periodicity and transmission rhythms, to align monitoring states with data arrival times, reducing delays and improving network capacity while minimizing energy consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single DRX configuration is used for multiple data flows, then device complexity is reduced, but data flow delay increases and network capacity decreases
Solution Approach 1:
The patent segments the single DRX configuration into multiple groups of DRX parameters, where each group is specifically configured for different data flows based on their arrival periodicity characteristics. This segmentation allows each data flow to have a tailored DRX configuration, reducing delay while maintaining manageable complexity through systematic organization.
Solution Approach 2:
The patent introduces dynamic selection of DRX parameter groups based on data flow characteristics. The terminal device dynamically selects appropriate DRX parameters from multiple groups according to the actual data flow arrival patterns, enabling adaptive optimization of delay performance without permanently increasing system complexity.
2Loss of time
If DRX monitoring is extended to cover all data flow arrival times, then data flow delay is reduced, but energy consumption increases
Solution Approach 1:
The patent segments monitoring duties by assigning different DRX parameter groups to different data flows. The terminal device only needs to monitor during active periods specified by the selected DRX parameters, rather than continuously monitoring for all possible data arrivals. This segmented approach reduces unnecessary monitoring and lowers energy consumption while still capturing all data flows in their respective active windows.
Solution Approach 2:
The patent changes DRX parameters (cycle length, active duration, offset) based on data flow characteristics to optimize the balance between delay and energy consumption. By adjusting these parameters dynamically, the system ensures monitoring occurs only when necessary for each data flow, minimizing energy waste while maintaining low delay performance.
3Productivity
If DRX parameters are optimized for each data flow individually, then network capacity is improved, but device complexity increases
Solution Approach 1:
The patent creates a universal framework where a single set of DRX parameter groups serves multiple data flows with different characteristics. Each group of DRX parameters is designed to be multi-functional, capable of handling different data flow patterns through dynamic selection. This universality allows the system to achieve optimized network capacity for multiple flows without proportionally increasing device complexity.
Solution Approach 2:
The patent employs dynamic selection mechanisms that allow the terminal device to adaptively choose the most appropriate DRX parameter group for each data flow based on observed arrival patterns. This dynamic approach enables individual optimization for each data flow to improve network capacity, while the selection logic maintains manageable complexity by avoiding the need for manual configuration of each parameter set.
Data Source
AI summary
This application provides a network configuration method, an apparatus, and a device. In the method, a terminal device may receive a plurality of groups of DRX parameters, and related parameters such as DRX cycles in the plurality of groups of DRX parameters are configured differently, so that DRX configurations can better match features, such as data arrival time and data amount, of different data flows. In this way, the terminal device can wake up in time when data arrives, and monitors a PDCCH for a proper period of time, to ensure a service delay and user experience. In addition, monitoring time is not longer than time needed for the data amount, helping