Air Interface Slice Resource Allocation for Ultra-Low Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing air interface communication systems fail to meet ultra-low-latency requirements due to resource allocation delays, inefficient frame structures, and scheduling delays, which hinder the transmission of ultra-low-latency service flows.
Innovation Solution
The method involves virtualizing air interface resources into ultra-low-latency and non-ultra-low-latency slices, dynamically adjusting reserved resources based on collision situations, reallocating resources during data transmission, and borrowing idle resources from non-ultra-low-latency slices to meet the latency demands of ultra-low-latency services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If dynamic scheduling methods are used for resource allocation, then resource utilization is improved, but scheduling delay increases
Solution Approach 1:
The patent pre-allocates specific time-frequency resources for ultra-low latency services before data arrives. The base station configures dedicated uplink resources in advance for ULL terminals, eliminating the need for scheduling requests and grants at transmission time. This preliminary resource assignment ensures immediate transmission capability while maintaining overall system efficiency through targeted pre-allocation only for ULL traffic.
2Adaptability or versatility
If resource allocation is done according to buffer status report, then resource allocation flexibility is improved, but transmission latency increases
Solution Approach 1:
The patent segments the uplink resource allocation process into two distinct parts: (1) pre-configuration of resource pools for ULL services with immediate access capability, and (2) dynamic BSR-based allocation for non-ULL services. ULL terminals are assigned specific resource blocks in advance without needing to wait for BSR processing, while other terminals continue to use the traditional BSR mechanism. This segmentation resolves the contradiction by providing fast paths for time-critical traffic while maintaining flexibility for other traffic types.
3Adaptability or versatility
If 10ms frame structure is used, then system compatibility is improved, but ultra-low latency requirement cannot be met
Solution Approach 1:
The patent introduces dynamic resource allocation within the existing 10ms frame structure by allowing flexible assignment of specific time-frequency blocks to ULL services on demand. While the overall frame structure remains compatible with existing systems, the resource allocation within each frame becomes dynamic and adaptive, enabling sub-10ms latency for ULL traffic by utilizing any available resource block immediately when data arrives, rather than waiting for frame boundaries.
4Speed
If reserved resources are allocated for ultra-low-latency services, then transmission speed is improved, but resource collision probability increases
Solution Approach 1:
The patent implements a feedback mechanism where the base station monitors the usage and collision status of pre-allocated ULL resources in real-time. Based on this feedback, the system dynamically adjusts the resource allocation strategy - increasing reserved resources when collision rates are high, and optimizing resource distribution when utilization patterns change. This closed-loop control maintains high transmission speed while adapting to actual collision probabilities and traffic conditions.
Data Source
AI summary
A method for reserving and allocating resources for an ultra-low-latency uplink service flow based on an air interface slice includes: virtualizing an air interface resource of a base station side into an ultra-low-latency slice resource and a non-ultra-low-latency slice resource; recording a collision situation on reserved resources in each retry window, and dynamically adjusting a size of the reserved ultra-low-latency slice resource; after detecting that a terminal transmits ultra-low-latency data on the ultra-low-latency slice resource, performing a resource reallocation and determining whether an idle resource is presented; if presented, allocating the idle resource to the terminal transmitting the ultra-low-latency data and returning the borrowed non-ultra-low-latency slice resource after transmitting the ultra-low-latency data; and if not presented, borrowing the non-ultra-low-latency slice resource allocated to a non-ultra-low-latency terminal and returning the borrowed non-ultra-low-latency slice resource after transmitting the ultra-low-latency data.


