RLC Entity Segmentation for High-Frequency L2 Buffer Control
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, to manage buffer occupancy and scheduling.
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 buffer 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 of status reporting control parameters for each RLC entity, enabling optimized buffer management for high frequency carriers while maintaining efficient processing for low frequency carriers, thus resolving the contradiction between high data rate capability and L2 buffer requirement.
2Reliability
If separate RLC entities are configured for different carriers, then buffer management is improved, but protocol stack complexity increases
Solution Approach 1:
The patent divides the RLC entity into multiple separate entities, each managing specific carriers independently. This segmentation improves buffer management reliability by allowing tailored status reporting control parameters for different carrier types, while the modular structure actually reduces overall system complexity by enabling localized optimization without affecting other carriers.
Solution Approach 2:
The patent applies local quality by configuring different status reporting control parameters for different RLC entities based on their specific carrier assignments. Each RLC entity receives customized parameters optimized for its designated carriers, improving overall buffer management effectiveness while maintaining clear separation of responsibilities that simplifies protocol implementation.
3Productivity
If status reporting control parameters are configured per carrier, then data handling efficiency is improved, but configuration complexity increases
Solution Approach 1:
The patent segments the configuration process by associating specific status reporting control parameters with each separate RLC entity. This segmentation enables independent optimization of parameters for different carrier types, improving data handling efficiency for high frequency carriers while maintaining straightforward configuration management through the modular RLC entity structure.
Solution Approach 2:
The patent implements local quality by assigning customized status reporting control parameters to each RLC entity based on its specific carrier assignments. This approach optimizes data handling efficiency for each carrier type while actually simplifying the overall configuration process by localizing parameter settings to specific, well-defined entities rather than requiring complex global configuration.
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.