RLC Protocol Stack Segmentation for High-Frequency Data Rates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems face challenges in managing high data rates when using high frequency spectrum due to substantial demands on L2 buffering, particularly in user equipment (UE) and network resources.
Innovation Solution
The implementation of a protocol stack configuration that includes separate configurations for first and second RLC entities handling carriers below and above a frequency threshold, along with separate status reporting control parameters for each carrier and subcarrier spacing, and buffer occupancy control mechanisms to prevent L2 buffer overflow.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If high frequency spectrum is used to achieve high data rates, then data rate is improved, but L2 buffering requirement increases substantially
Solution Approach 1:
The patent segments the RLC entity into multiple separate RLC entities, each handling specific carriers or carrier groups. This segmentation allows independent configuration and management of buffering parameters for different carriers, enabling optimized L2 buffering that matches the actual data rate requirements of each carrier group, thereby reducing overall buffering demand while maintaining high data rates.
Solution Approach 2:
The patent applies local quality by configuring separate status reporting control parameters for each carrier or carrier group. This allows tailored buffering and control parameters specific to each carrier's characteristics, optimizing the balance between data rate and buffering requirement for each local carrier segment rather than using uniform settings for all carriers.
2Quantity of substance
If separate RLC entities are configured for different carriers, then L2 buffering is optimized, but protocol stack complexity increases
Solution Approach 1:
The patent segments the RLC entity into multiple separate RLC entities, each handling specific carriers or carrier groups. This segmentation allows independent configuration and management of buffering parameters for different carriers, enabling optimized L2 buffering that matches the actual data rate requirements of each carrier, thereby reducing overall buffering demand while maintaining high data rates.
Solution Approach 2:
The patent implements a universal configuration framework where a single configuration mechanism can manage multiple RLC entities with different parameters. The base station can configure separate status reporting control parameters for each carrier or carrier group using a unified approach, reducing operational complexity while maintaining the benefits of segmented buffering optimization.
Data Source
AI summary
To accommodate a mix of high frequency carriers and lower frequency carriers, a protocol stack may include a radio link control (RLC) entity that allows configuration of status reporting control parameters on per carrier, or per subcarrier spacing. Alternatively, a protocol stack may include two RLC entities, one for handling high frequency carriers, and another for handling lower frequency carriers. (High frequency carriers and lower frequency carriers may be distinguished based on a frequency threshold.) Furthermore, a user equipment may transmit (to the network) an indication of its L2 buffer size. The network may configure the UE and/or control scheduling, to ensure the UE's L2 buffer does not overrun. Alternatively, the UE may indicate that it can support a percentage of a maximum buffer size. The network may configure the UE and/or control scheduling so that the UE's buffer occupancy does not exceed the percentage.