Base Station RLC Header Optimization for 5G URLLC Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 5G communication systems face challenges in achieving ultra-reliable and low-latency communication (URLLC) due to high overhead from header components, especially when transmitting small-sized data, which hinders the attainment of low latency requirements.
Innovation Solution
A base station device that omits portions of the segmentation offset or reserve bits in the RLC header when multiplexing URLLC and eMBB data together, reducing the data amount in the RLC header and overhead during transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a complete RLC header including segmentation offset and reserve bits is transmitted for URLLC data, then the header provides complete information for data reassembly, but the overhead increases and latency increases
Solution Approach 1:
The patent extracts and removes unnecessary portions of the RLC header (segmentation offset and reserve bits) from URLLC data packets. Since URLLC data is typically small and transmitted as a single segment, the segmentation offset field is redundant, and reserve bits can be omitted. This extraction reduces header overhead while maintaining sufficient information for correct data reassembly at the receiver.
Solution Approach 2:
The patent applies partial action by including only the necessary portions of the RLC header for URLLC data rather than the complete header structure used for other data types. The header includes essential fields for identification and reassembly but omits optional or redundant fields, achieving the minimum required information for reliable transmission.
2Loss of time
If the RLC header is optimized for URLLC by omitting segmentation offset and reserve bits, then the overhead is reduced and latency is lowered, but the header may lack complete information for certain data types
Solution Approach 1:
The patent applies local quality by creating different header structures for different data types. URLLC data uses a simplified header optimized for low latency, while other data types (eMBB, voice, video) use the complete RLC header structure. The base station identifies the data type and applies the appropriate header format, ensuring each data type receives the optimal header treatment for its specific requirements.
Solution Approach 2:
The patent changes the header parameters (structure and content) based on the data type being transmitted. For URLLC data, the header parameters are modified to exclude segmentation offset and reserve bits, while for other data types, the complete header structure is maintained. This dynamic parameter adjustment allows the system to optimize for latency when needed while maintaining compatibility for other use cases.
3Loss of time
If different header patterns are used for different data types, then the overhead is optimized for each specific use case, but the system complexity increases
Solution Approach 1:
The patent applies preliminary action by pre-defining and storing multiple header patterns in both the base station and terminal devices. These header patterns are prepared in advance for different data types (URLLC, eMBB, voice, video). When data needs to be transmitted, the appropriate pre-defined header pattern is selected and applied without requiring complex real-time header construction, thereby reducing processing complexity while maintaining optimization benefits.
Data Source
AI summary
A base station device includes, a transmitter that transmits first data of a first type and second data of a second type, and a controller that is able to omit, when the transmitter multiplexes the first data and the second data together and transmits the first data and the second data multiplexed together, at least a portion of a segmentation offset or at least a portion of a reserve bit included in an RLC header of the second data.