PDCP Duplication Control via RLC Entity Status

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing wireless communication systems lack detailed methods for implementing Packet Data Convergence Protocol (PDCP) duplication, which is essential for enhancing data transmission reliability in next-generation wireless communication systems.

Innovation Solution

The proposed solution involves a method for submitting PDCP PDUs to lower layers in wireless communication systems, specifically using a flowchart-based procedure that determines whether to operate in duplication mode or split bearer mode based on configuration and data volume considerations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If PDCP duplication is implemented to increase data transmission reliability, then transmission reliability is improved, but device complexity increases due to multiple RLC entities and configuration management

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidPDCP duplication configuration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The UE autonomously determines whether to activate PDCP duplication based on RLC entity status information without requiring explicit network configuration commands. The UE self-evaluates buffer status and RLC entity availability, then self-activates or deactivates duplication mode accordingly, reducing network-side configuration complexity while maintaining reliability improvements

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The PDCP duplication function is designed to be dynamically activated or deactivated based on real-time RLC entity status. The system transitions between duplication mode and non-duplication mode according to buffer status and entity availability, allowing adaptive complexity management that scales with actual transmission needs rather than maintaining fixed high complexity

Inventive Principle:
Principle #15Dynamics

2Reliability

If PDCP duplication is activated to ensure data transmission through multiple paths, then transmission reliability is improved, but data transmission latency increases due to additional processing and routing steps

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoiddata transmission latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

PDCP duplication is activated only partially - specifically when RLC entity status indicates available capacity and when buffer status thresholds are met. Rather than always duplicating data, the system applies duplication selectively to portions of data traffic that benefit most from redundancy, reducing overall processing latency while maintaining reliability for critical transmissions

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system performs preliminary evaluation of RLC entity status and buffer conditions before activating duplication. By pre-assessing whether duplication is necessary based on current system state, the patent avoids unnecessary duplication activation that would increase latency, while ensuring duplication is ready to activate quickly when reliability becomes critical

Inventive Principle:
Principle #10Preliminary action

3Manufacturing precision

If detailed configuration procedures for PDCP duplication are provided, then implementation precision is improved, but ease of operation deteriorates due to complex configuration management

Engineering Contradiction:
ImprovePDCP duplication implementation precisionVSAvoidconfiguration management ease
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The UE performs self-configuration of PDCP duplication by autonomously determining activation conditions based on RLC entity status information. Instead of requiring detailed network-provided configuration parameters, the UE self-configures duplication behavior according to predefined status thresholds and buffer conditions, achieving precise implementation without complex configuration management

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent changes the control parameter from detailed configuration parameters to simple status indicators (buffer status, RLC entity availability). By monitoring these parameters and automatically adjusting duplication activation accordingly, the system achieves precise control with minimal configuration overhead, improving ease of operation while maintaining implementation precision

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP4184834B1Method for packet data convergence protocol (PDCP) data transmission in wireless communication systems
Publication Date: 2025.03.05 SHARP KK
  • EP4184834B1 patent drawingFigure 1A~1B
  • EP4184834B1 patent drawingFigure 2
  • EP4184834B1 patent drawingFigure 3

AI summary

A method, performed by a User Equipment (UE) including a Packet Data Convergence Protocol (PDCP) entity associated with two Radio Link Control (RLC) entities and configured with a duplication function that is not activated, includes: determining, by the PDCP entity, whether the two RLC entities belong to a same cell group, and submitting, by the PDCP entity, a PDCP Data Protocol Data Unit (PDU) to a primary RLC entity of the two RLC entities when the two RLC entities belong to the same cell group.