RLC Buffer Management via Dynamic Data Duplication Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In carrier aggregation scenarios, terminal devices face challenges in efficiently processing data in Radio Link Control (RLC) buffers, particularly in managing data duplication and transmission functions across multiple RLC entities to ensure reliable and efficient data transmission.

Innovation Solution

A method and device for processing data by controlling the state of data duplication and transmission functions based on indication information, using timers to manage the occupancy of RLC buffers, and selectively transmitting or discarding data units depending on the state of data duplication and transmission functions across different RLC entities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data duplication function is enabled to improve transmission reliability, then data transmission reliability is improved, but buffer occupancy time increases and resource utilization decreases

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidbuffer occupancy time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies dynamics by making the data duplication function configurable and switchable based on transmission requirements. The system dynamically adjusts between duplicated transmission (for reliability) and non-duplicated transmission (for efficiency) through indication information from the network device, allowing optimal performance characteristics to be selected according to current network conditions and service requirements.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of transmission mode by introducing indication information that controls whether data duplication is performed. This parameter change allows the system to switch between different transmission strategies (duplicated vs. non-duplicated) to optimize the trade-off between reliability and buffer occupancy time based on specific transmission scenarios.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If data duplication function is enabled to improve transmission reliability, then data transmission reliability is improved, but resource utilization decreases

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidresource utilization
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system dynamically controls the data duplication function through indication information, enabling duplication only when reliability is prioritized. When indication information signals non-duplicated transmission mode, the system switches to more efficient resource utilization, thus dynamically adapting resource consumption to actual transmission needs.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent introduces a controllable parameter (indication information) that changes the transmission mode between duplicated and non-duplicated. This parameter change allows optimization of resource utilization by selecting non-duplicated mode when appropriate, while maintaining the ability to switch to duplicated mode when reliability requirements demand it.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If timer is used to control RLC buffer occupancy time, then buffer management efficiency is improved, but complexity of processing increases

Engineering Contradiction:
Improvebuffer management efficiencyVSAvoidprocessing complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by starting a timer when data is stored in the RLC buffer. This timer is set in advance to control the maximum occupancy time, and the system proactively checks whether the timer expires before transmission occurs, enabling efficient buffer management through pre-configured time control mechanisms.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The timer mechanism provides feedback by continuously monitoring the occupancy time of data in the RLC buffer. When the timer expires, the system receives feedback that the data has exceeded the allowed occupancy time, triggering actions to prioritize transmission or discard the data, thus enabling automated buffer management through feedback-driven control.

Inventive Principle:
Principle #23Feedback

4Reliability

If data is transmitted through multiple RLC entities, then transmission reliability is improved, but device complexity increases

Engineering Contradiction:
Improvetransmission reliabilityVSAvoidentity management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies universality by using a unified indication information mechanism to control the data duplication function across multiple RLC entities. The same control approach (receiving and processing indication information) is used regardless of which RLC entities are involved, allowing the system to manage multiple entities through a universal control interface rather than requiring entity-specific management logic.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11778689B2Method and device for processing data
Publication Date: 2023.10.03 GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
  • US11778689B2 patent drawing
  • US11778689B2 patent drawing
  • US11778689B2 patent drawing

AI summary

A method and device for processing data are provided. The method comprises: a terminal device controlling the current state of a copied data transfer function according to first indication information, wherein the first indication information is used for indicating whether the copied data transfer function is enabled; and the terminal device processing, according to the current state of the copy data transfer function, each RLC service data unit (SDU) in a first radio link control (RLC) cache and a second RLC cache, wherein the first RLC cache corresponds to a first RLC entity, and the second RLC cache corresponds to a second RLC entity.