Wireless Resource Request Signaling with QoS and Backlog
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems face inefficiencies in requesting radio resources, particularly on the reverse link, as existing methods do not effectively utilize quality of service (QoS) information and backlog levels to optimize resource allocation and scheduling.
Innovation Solution
The system supports multiple types of QoS information and backlog levels in resource requests, allowing terminals to determine and send resource requests with specific configurations that include QoS class, latency deadline, or combinations thereof, using various formats to efficiently convey information for resource allocation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If traditional resource request methods are used without QoS information, then the signaling overhead is reduced, but the resource allocation efficiency and QoS support capability deteriorate
Solution Approach 1:
The resource request message is segmented into multiple fields with different functions: backlog level field for data volume indication, QoS class field for service type identification, and latency deadline field for timing requirements. This segmentation allows efficient transmission of multiple types of QoS information while maintaining clear structure and reducing parsing complexity at the base station side.
Solution Approach 2:
The resource request message structure is designed to be universal by incorporating multiple QoS information types (QoS class, latency deadline, backlog level) that can accommodate different service requirements. The base station can process these unified requests and allocate resources appropriately based on the combined information, making the system versatile for various QoS scenarios without requiring separate signaling mechanisms.
2Measurement precision
If detailed QoS information is included in resource requests, then the resource allocation accuracy is improved, but the signaling overhead increases
Solution Approach 1:
Different fields in the resource request message carry different types of quality information tailored to specific allocation needs: backlog level for quantity assessment, QoS class for service category identification, and latency deadline for timing-critical allocations. This local quality approach ensures that only relevant QoS parameters are transmitted for each specific resource request scenario, optimizing the balance between information completeness and signaling efficiency.
3Adaptability or versatility
If multiple QoS parameters are transmitted, then the scheduling flexibility is improved, but the processing complexity at base station increases
Solution Approach 1:
The base station scheduler dynamically adjusts resource allocation decisions based on the combination of QoS parameters received in resource requests. The scheduler can prioritize requests with strict latency deadlines, allocate resources according to QoS class requirements, and balance overall system load using backlog level information. This dynamic processing approach enables flexible adaptation to varying traffic conditions while using standardized field formats that streamline the decision-making process.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Techniques for sending resource requests in a wireless communication system are described. Multiple types of quality of service (QoS) information may be supported for resource requests and may include QoS class and latency deadline. A terminal may have data to send on the reverse link and may determine QoS information for the data. The QoS information may include at least one QoS type, which may be dependent on a configuration selected for use to send resource requests. The terminal may also determine backlog level information indicative of the amount of data to send. The terminal may generate a resource request with the backlog level and QoS information. The resource request may include the backlog level information and QoS class information, the backlog level information and either QoS class information or latency deadline information, the backlog level information and latency deadline information, or some other combination of information.