Out-of-Order RLC Entity for Low-Latency Wireless Traffic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication networks face limitations in flexibility and efficiency due to the current out-of-order delivery (OOD) capability being limited to a per-Data Radio Bearer (DRB) basis, which restricts the ability to handle different types of traffic and traffic flows effectively, especially in scenarios requiring low latency and ultra-reliable low latency communication (URLLC).
Innovation Solution
The solution enables out-of-order delivery at the granularity of a Radio Link Control (RLC) entity, allowing networks and devices to selectively support OOD across multiple PDU Sets or QoS flows mapped to the same DRB, using multiple RLC entities for in-order and out-of-order traffic, and configuring RLC entities with RRC to match upper layer configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If out-of-order delivery is enabled at the DRB level, then latency is reduced for some traffic, but flexibility to handle different traffic types is lost
Solution Approach 1:
The patent segments the out-of-order delivery capability from the DRB level down to the RLC entity level. This allows different RLC entities within the same DRB to have different OOD configurations, enabling fine-grained control where some RLC entities can use OOD for low-latency traffic while others maintain in-order delivery for traffic requiring reliability, thus resolving the contradiction between latency reduction and flexibility.
2Adaptability or versatility
If multiple RLC entities are used for different traffic types, then flexibility and latency performance improve, but device complexity increases
Solution Approach 1:
The patent implements universal configuration mechanisms where a single DRB can universally support multiple RLC entities with different OOD capabilities. The network can configure and manage these multiple RLC entities through standardized procedures, allowing the system to handle diverse traffic types without proportionally increasing complexity, as the management framework remains unified rather than requiring separate handling for each entity.
Data Source
AI summary
The techniques described herein may include a device, comprising: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause the device to: communicate, via a wireless communication network, information as in-order traffic using an in-order radio link control (RLC) entity; and communicate, via the wireless communication network, information as out-of-order traffic using an out-of-order RLC entity. The in-order traffic and the out-of-order traffic may be communicated using the same data radio bearer (DRB). The out-of-order traffic may include selective out-of-order delivery (OOD) or per-packet OOD. Additional examples, features and other techniques are also described herein.


