RLC Entity Segmentation for Buffer Status Reporting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In radio networks with a one-to-many correspondence between sending and receiving nodes, existing buffer status reporting methods lead to resource wastage as all receiving nodes allocate resources when there is data in the PDCP entity's buffer, regardless of data presence in individual RLC entity buffers.
Innovation Solution
Classifying RLC entities as first and second entities, generating and sending buffer status reports only based on data in the PDCP entity and the second RLC entity's buffers, ensuring only the corresponding receiving node allocates resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If buffer status reports are triggered for all receiving nodes when there is to-be-sent data in the PDCP entity buffer, then all receiving nodes can allocate sending resources, but this causes waste of sending resources
Solution Approach 1:
The patent segments the RLC entities into two distinct groups: first RLC entities that only report their own buffer status, and second RLC entities that report combined PDCP and RLC buffer status. This segmentation allows the system to selectively trigger BSRs for specific receiving nodes based on actual data presence, preventing unnecessary resource allocation while maintaining complete buffer status visibility.
Solution Approach 2:
The patent applies local quality by configuring different BSR triggering behaviors for different receiving nodes based on their specific needs. Receiving nodes corresponding to first RLC entities receive BSRs only when those specific entities have data, while receiving nodes corresponding to second RLC entities receive BSRs when PDCP or RLC data is present. This localized approach optimizes resource allocation for each receiving node individually.
2Productivity
If all receiving nodes allocate sending resources when a BSR is triggered, then data transmission can proceed, but resources are wasted when not all nodes need the data
Solution Approach 1:
The patent segments the receiving nodes into two groups based on their correspondence to first or second RLC entities. This segmentation enables the sending node to allocate sending resources selectively - only to receiving nodes that actually need data transmission - rather than allocating to all receiving nodes uniformly, thus maintaining productivity while reducing resource quantity waste.
Solution Approach 2:
The patent changes the triggering parameter for BSR generation based on the type of RLC entity. For first RLC entities, BSRs are triggered only when those specific entities have data. For second RLC entities, BSRs are triggered when PDCP or RLC data is present. This parameter change in triggering conditions ensures that sending resources are allocated based on actual transmission needs rather than uniform triggering.
3Loss of information
If the sending node triggers BSRs for all receiving nodes when PDCP buffer has data, then all nodes are notified, but this leads to redundant resource allocation
Solution Approach 1:
The patent segments buffer status information reporting into two distinct mechanisms: one for first RLC entities that report only their own buffer status, and another for second RLC entities that report combined PDCP and RLC buffer status. This segmentation ensures that receiving nodes receive complete buffer status information relevant to their specific data transmission needs without receiving redundant information from other RLC entities, thus reducing allocation overhead while maintaining information completeness.
Solution Approach 2:
The patent applies local quality by providing customized buffer status information to each receiving node based on their correspondence to specific RLC entities. Each receiving node receives BSR information tailored to its specific transmission requirements, avoiding the overhead of receiving and processing unnecessary buffer status information from unrelated RLC entities.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A sending node and a buffer status reporting method are disclosed. The method includes: classifying at least two RLC entities included in a sending node as at least one first RLC entity and one second RLC entity, where all the RLC entities are associated with a PDCP entity included in the sending node; and in a case in which a buffer of the first RLC entity includes to-be-sent data, generating a first buffer status report BSR based on a size of the to-be-sent data in the buffer of the first RLC entity, and sending the generated first BSR to a receiving node corresponding to the first RLC entity. By classification of the first RLC entity and the second RLC entity, the second RLC entity is exclusively associated with buffer status reporting of the PDCP entity. In the sending node and the buffer status reporting method according to the present invention, it can be achieved that, when there is to-be-sent data in a buffer of a PDCP entity, only one receiving node is triggered to allocate a corresponding sending resource to the to-be-sent data; thereby effectively avoiding a waste of sending resources on a radio network in which a sending node and receiving nodes are in a one-to-many correspondence.