Delay Status Report Triggering for PDCP Buffer Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Delay Status Report (DSR) procedure in communication technology continuously triggers DSRs for already transmitted data, leading to increased uplink overhead and useless reports, as the report would signal no data volume for transmitted data.
Innovation Solution
A terminal device determines a criterion for buffered data units not submitted to a lower layer in the Packet Data Convergence Protocol (PDCP), and based on this criterion, triggers a DSR comprising the data volume and remaining time of these data units, thereby optimizing the DSR trigger mechanism.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the existing DSR procedure continuously triggers DSRs for already transmitted data, then the DSR reporting mechanism remains active and monitors all buffered data, but the uplink overhead increases and useless reports are generated
Solution Approach 1:
The patent extracts and removes already transmitted data from the DSR reporting scope, focusing only on new buffered data that has not been submitted to the lower layer. This is achieved by modifying the trigger criterion to specifically identify and report only new data units, thereby eliminating useless reports for transmitted data and reducing uplink overhead.
Solution Approach 2:
The patent applies partial action by triggering DSR reports only for a subset of data (new buffered data) rather than all buffered data including already transmitted data. This selective reporting approach reduces the quantity of reports while maintaining the essential monitoring function for relevant data.
2Productivity
If the DSR trigger criterion is relaxed to include all buffered data, then more data is monitored and reported, but the number of useless reports increases
Solution Approach 1:
The patent extracts and removes already transmitted data from the monitoring scope, focusing only on new buffered data units that have not been submitted to the lower layer. This selective extraction ensures that only relevant data triggers reports, eliminating useless reports for transmitted data.
Solution Approach 2:
The patent applies local quality by differentiating the treatment of different data states: new buffered data triggers DSR reports, while already transmitted data does not. This localized differentiation optimizes the reporting mechanism by applying the trigger criterion selectively based on data state.
3Loss of energy
If the DSR trigger criterion is strict to only new data, then useless reports are reduced, but the complexity of determining data state increases
Solution Approach 1:
The patent introduces an intermediary mechanism using the PDCP layer's data submission status as a mediator to determine whether data should trigger a DSR report. The data state determination is simplified by relying on the existing PDCP submission indicator, which clearly distinguishes between new and transmitted data without complex additional logic.
Solution Approach 2:
The patent applies self-service by utilizing the PDCP layer's existing data submission tracking mechanism to automatically determine data state for DSR triggering. The system leverages its own internal state information (whether data has been submitted to the lower layer) to make the determination, eliminating the need for external complex state detection.
Data Source
AI summary
Embodiments of the present disclosure relate to a delay status report (DSR). In an aspect, a terminal device determines a criterion for one or more data units. The one or more data units are buffered and not submitted to a lower layer in a packet data convergence protocol (PDCP). Moreover, the terminal device triggers, based on said criterion, a DSR comprising a data volume of the one or more data units and a remaining time associated with the one or more data units. In this way, it is possible to improve the DSR reporting with enhanced efficiency.