Logical Channel Grouping for PDB-Aware XR Uplink Scheduling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In extended reality (XR) services, the existing buffer status report (BSR) mechanism for logical channel groups (LCGs) fails to account for varying packet delay budgets (PDBs) within data bursts, leading to inefficient uplink scheduling and reduced capacity.
Innovation Solution
A logical channel grouping method that associates LCGs with specific remaining PDB ranges and priority levels, enabling the network device to allocate resources based on configured rules, ensuring timely and efficient uplink scheduling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the terminal device sends a BSR indicating total buffered data volume for an LCG, then the network device can allocate uplink resources based on the reported volume, but the allocation may exceed the PDB of packets causing scheduling failures
Solution Approach 1:
The patent segments the buffered data into multiple groups based on remaining PDB ranges. Instead of reporting a single total volume for the LCG, the terminal device divides the data into segments (first buffered data with first remaining PDB range, second buffered data with second remaining PDB range, etc.) and reports each segment's volume separately. This segmentation allows the network device to allocate resources appropriately for each PDB category, ensuring packets are not scheduled beyond their PDB while maintaining high scheduling efficiency.
2Ease of operation
If the network device allocates uplink resources without considering varying PDBs, then resource allocation is simplified, but packets may be scheduled beyond their PDB leading to scheduling failures
Solution Approach 1:
The buffered data is segmented by remaining PDB ranges, creating distinct categories (e.g., first remaining PDB range, second remaining PDB range). Each segment is reported separately in the BSR, allowing the network device to apply different allocation strategies to different segments while maintaining a systematic and manageable allocation process.
Solution Approach 2:
The patent introduces remaining PDB range as a new parameter for data classification. By changing the classification parameter from simple LCG membership to PDB-range-based grouping, the system enables the network device to make informed allocation decisions that respect packet delay requirements while maintaining operational simplicity through standardized reporting formats.
3Device complexity
If the terminal device reports buffered data at LCG granularity without PDB information, then the reporting mechanism remains simple, but the network device cannot perform differentiated scheduling for packets with different PDB requirements
Solution Approach 1:
The reporting mechanism is segmented to include multiple data volume indicators corresponding to different PDB ranges. The terminal device divides the buffered data into segments based on remaining PDB ranges and reports each segment's volume separately, enabling differentiated scheduling while maintaining a structured and manageable reporting format.
Solution Approach 2:
The patent adds a new dimension to the BSR reporting by incorporating remaining PDB range information. Instead of reporting a single aggregate volume per LCG, the system reports volumes across multiple PDB range dimensions, enabling the network device to perform multi-dimensional scheduling decisions that accommodate varying packet delay requirements.
Data Source
AI summary
A method includes: determining that to-be-reported buffered data exists on a first logical channel LCH, and sending a buffer status report BSR to a network device according to a preset configuration rule and based on the to-be-reported buffered data on the first LCH. The BSR indicates a first data volume and a first logical channel group LCG, the first data volume corresponds to the first LCG and includes a data volume of first data, the buffered data includes the first data, and the first LCG is one of LCGs configured for the first LCH. A remaining packet delay budget PDB of the first data is within a first remaining PDB range; or a priority level of the first data is within a first priority level range, and the priority level of the first data is determined based on a remaining PDB and a data type of the first data.