PDCP Re-establishment EHC Context Reset

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current specifications for PDCP re-establishment in 5G NR do not clearly define the operations involved in resetting the Ethernet header compression (EHC) protocol, leading to potential synchronization issues and data loss due to unnecessary EHC feedback transmission.

Innovation Solution

The proposed solution involves resetting the EHC protocol by discarding associated contexts and refraining from transmitting EHC feedback during PDCP re-establishment, ensuring that both the compressor and decompressor are synchronized to the initial state, thereby avoiding context mismatches and data loss.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If EHC feedback is transmitted during PDCP re-establishment, then protocol state synchronization is maintained, but data loss occurs due to context mismatch

Engineering Contradiction:

Improvedata integrityVSAvoidEHC feedback transmission

Core Design Contradiction:

ReliabilityVSLoss of information

Solution Approach 1:

The patent extracts the EHC feedback transmission from the PDCP re-establishment procedure by introducing a separate flag mechanism. The receiving entity sets a flag to indicate that EHC feedback should not be transmitted during re-establishment, effectively separating this function from the main re-establishment flow and preventing context mismatch issues.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies preliminary anti-action by proactively preventing the transmission of EHC feedback during PDCP re-establishment through the flag mechanism. This anticipatory measure avoids the potential harm of context mismatch and data loss before it can occur, rather than reacting to problems after they arise.

Inventive Principle:

Principle #9Preliminary anti-action

2Reliability

If EHC protocol is reset during PDCP re-establishment, then synchronization between compressor and decompressor is achieved, but protocol state is lost

Engineering Contradiction:

Improveprotocol synchronizationVSAvoidEHC context

Core Design Contradiction:

ReliabilityVSLoss of information

Solution Approach 1:

The patent applies preliminary action by preparing the receiving entity to handle EHC feedback differently during re-establishment. The flag is set in advance to indicate that EHC feedback should be ignored or not transmitted, allowing the protocol to smoothly transition through the re-establishment process without unexpected context mismatches.

Inventive Principle:

Principle #10Preliminary action

3Productivity

If EHC feedback transmission is enabled during PDCP re-establishment, then normal operation continues, but synchronization issues arise

Engineering Contradiction:

Improvedata transmission continuityVSAvoidsynchronization

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent introduces dynamic behavior by using a flag that can be set or cleared based on the operational state. During PDCP re-establishment, the flag is set to prevent EHC feedback transmission, ensuring synchronization. After re-establishment completes successfully, the flag is cleared to restore normal feedback transmission, allowing the system to adapt its behavior dynamically to current conditions.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS12120185B2Methods and apparatuses for providing header compression protocol reset

Publication Date: 2024.10.15 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

According to an aspect, there is provided a method performed by a wireless device for performing Packet Data Convergence Protocol, PDCP, entity re-establishment. The wireless device is acting as a Packet Data Convergence Protocol, PDCP, receiving entity. The method comprises receiving (101) a request to perform PDCP entity re-establishment; responsive to the request, resetting (103) a header compression protocol by discarding any contexts associated with the header compression protocol, and refraining (105) from transmitting feedback associated with the header compression protocol to a PDCP transmitting entity.