Split Bearer DSR Reporting with Threshold-Based RLC Tracking

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing wireless communication systems face challenges in accurately reporting delay status for split bearers, particularly in scenarios involving extended reality (XR) services, where different importance levels of packet data units are mapped to the same quality of service flow and radio bearer, leading to mismatches in delay-critical PDCP data volume reporting across multiple transmission paths.

Innovation Solution

The proposed solution involves associating a packet data convergence protocol (PDCP) entity with a primary and secondary RLC entity, calculating data volume against a threshold to determine PDCP PDU submission, and introducing a new MAC control element for delay status reporting (DSR) that aligns with PDCP transmission behavior across multiple paths, ensuring accurate reporting of delay-critical data volume to both primary and secondary RLC entities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If DSR reporting is implemented for split bearers, then delay status reporting capability is improved, but reporting accuracy deteriorates due to mismatches across multiple transmission paths

Engineering Contradiction:

ImproveDSR reporting capabilityVSAvoiddelay-critical PDCP data volume reporting accuracy

Core Design Contradiction:

Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The patent segments the reporting mechanism by introducing separate indicators for primary and secondary RLC entities. The UE determines data volume for each RLC entity separately and includes distinct indicators in DSR MAC CE reports, allowing independent tracking of delay-critical data on each transmission path rather than aggregated reporting that causes mismatches

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism where the UE acts as a mediator between the PDCP entity and multiple RLC entities. The UE receives data volume information from the PDCP entity, processes it according to each RLC entity's status, and generates appropriate DSR reports for each path, ensuring consistent and accurate reporting across multiple transmission paths

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If data is transmitted through multiple RLC entities, then transmission reliability is improved, but device complexity increases due to multiple DSR reporting paths

Engineering Contradiction:

Improvetransmission reliabilityVSAvoidDSR reporting complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the DSR reporting function into separate handling for primary and secondary RLC entities. The UE maintains separate data volume tracking and reporting logic for each RLC entity, simplifying the overall complexity by treating each path independently rather than managing complex interactions between multiple reporting paths

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements self-service where each RLC entity path independently determines and reports its own data volume status. The UE autonomously evaluates data volume for each RLC entity based on local buffer status and transmission conditions, eliminating the need for complex coordination and negotiation between network entities for DSR reporting

Inventive Principle:

Principle #25Self-service

3Measurement precision

If all data volumes are reported to maintain accuracy, then measurement precision is improved, but energy consumption increases

Engineering Contradiction:

Improvedata volume reporting accuracyVSAvoidUE power consumption

Core Design Contradiction:

Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The patent applies partial action by reporting data volume information selectively rather than continuously for all paths. The UE determines whether to include DSR indicators in reports based on whether data volume exceeds thresholds or changes significantly, reducing unnecessary reporting transmissions and associated power consumption while maintaining reporting accuracy when needed

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The patent changes the reporting parameter from continuous data volume reporting to threshold-based triggering. The UE monitors data volume changes and only generates DSR reports when parameters such as data volume exceed configured thresholds or change beyond a certain margin, reducing the frequency of power-consuming transmissions while preserving measurement precision through on-demand accurate reporting

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS20250254744A1Techniques for DSR reporting for split bearer operation

Publication Date: 2025.08.07 LENOVO (SINGAPORE) PTE LTD

AI summary

Various aspects of the present disclosure relate to techniques for delay status reported (DSR) for split bearer operation. An apparatus is configured to associate a packet data convergence protocol (PDCP) entity with a primary radio link control (RLC) entity and at least one secondary RLC entity, indicate a data volume associated with the PDCP entity to a medium access control (MAC) entity for DSR, determine an amount of data available for transmission based on the data volume associated with the PDCP entity and an RLC data volume that is pending for initial transmission in the primary RLC entity and the at least one secondary RLC entity, and indicate an amount of the data volume associated with the PDCP entity to the MAC entity associated with the primary RLC entity for DSR in response to the amount of data available for transmission being less than a threshold.