QoS Flow Information Delivery for Low-Latency gNB Scheduling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication technologies face challenges in efficiently delivering quality of service (QoS) flow information, leading to long latency, increased signaling overhead, and prolonged interruption times, particularly in high-data-rate and low-latency applications like Extended Reality (XR) and video streaming.
Innovation Solution
The method involves delivering QoS flow information through various interfaces (NG, F1, E1, and Xn) to optimize gNB radio resource scheduling, using parameters such as uplink and downlink traffic periodicity, jitter information, and PDU set QoS parameters to enhance scheduling efficiency and reduce latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If traditional QoS flow information delivery methods are used, then QoS information can be delivered between network nodes, but latency increases and interruption time is prolonged
Solution Approach 1:
The patent applies preliminary action by pre-configuring QoS flow information delivery mechanisms before data transmission begins. The system establishes QoS parameter configurations, traffic descriptor information, and resource allocation rules in advance through signaling protocols, enabling immediate QoS enforcement when data flows start without requiring real-time negotiation, thus reducing latency while maintaining delivery reliability
Solution Approach 2:
The patent introduces intermediary elements such as QoS flow identifiers, traffic descriptors, and intermediate network nodes that facilitate efficient QoS information delivery. These intermediaries enable indirect but optimized information exchange between source and destination, reducing direct signaling overhead and interruption time while ensuring reliable QoS parameter transmission through multiple standardized interfaces
2Productivity
If detailed QoS flow information is delivered to optimize scheduling, then scheduling efficiency improves, but signaling overhead increases
Solution Approach 1:
The patent segments QoS flow information into distinct components including QoS flow identifiers, traffic descriptors, parameter configurations, and scheduling rules. This segmentation allows the system to transmit only essential QoS parameters through standardized signaling interfaces while delivering detailed flow information through more efficient data plane mechanisms, thereby improving scheduling efficiency without proportionally increasing signaling overhead
Solution Approach 2:
The patent applies partial action by delivering QoS information at different levels of detail to different network nodes based on their specific needs. Critical QoS parameters are delivered to all nodes for basic scheduling, while detailed flow information is selectively delivered only to nodes requiring granular control, reducing overall signaling overhead while maintaining sufficient scheduling efficiency for each node's function
3Measurement precision
If QoS flow information delivery is performed frequently to maintain accuracy, then QoS parameter accuracy improves, but resource utilization efficiency decreases
Solution Approach 1:
The patent implements periodic action by establishing scheduled QoS information delivery intervals and trigger-based updates. QoS parameters are delivered at regular intervals or when specific change thresholds are met, rather than continuously or overly frequently. This periodic mechanism maintains adequate QoS parameter accuracy for scheduling decisions while significantly reducing resource consumption compared to continuous delivery approaches
Data Source
AI summary
The present disclosure describes methods, system, and devices for delivering quality of service (QoS) flow information. The method includes sending, by a first network node, a first message via a communication interface to a second network node, the first message comprising a list of parameters corresponding to a data burst comprising at least one protocol data unit (PDU) set; and receiving, by the first network node, a second message via the communication interface from the second network node, the second message being responsive to the first message.