PDCP-RLC Sequence Number Binding to Reduce Unnecessary RLC Retransmissions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In wireless communication systems, particularly in scenarios involving dual connectivity, gaps in Packet Data Convergence Protocol (PDCP) sequence numbers (SNs) occur due to data loss or transmission rate variations, leading to unnecessary Radio Link Control (RLC) retransmissions, which negatively impact latency and efficiency, especially for latency-sensitive applications like extended reality (XR).

Innovation Solution

A method and apparatus are provided to bind PDCP SNs with RLC SNs through a mapping relationship, enabling efficient handling of packet losses and reducing unnecessary RLC retransmissions by informing the receiver of SN gaps, optimizing the binding based on transmission conditions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If PDCP and RLC sequence numbers are independently managed without binding, then each protocol layer can operate autonomously, but gaps in PDCP sequence numbers trigger unnecessary RLC retransmissions, increasing latency and reducing efficiency

Engineering Contradiction:
Improvepacket delivery reliabilityVSAvoidlatency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent merges the independent sequence number management of PDCP and RLC layers by establishing a binding relationship between PDCP SNs and RLC SNs. This allows the receiver to correlate packets across layers, preventing unnecessary retransmissions when PDCP gaps occur, thus improving reliability while reducing latency caused by spurious retransmission requests

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements feedback mechanisms where the receiver informs the transmitter about PDCP sequence number gaps through binding information. This feedback allows the transmitter to understand that PDCP gaps do not necessarily indicate RLC packet loss, preventing unnecessary retransmissions and reducing latency while maintaining reliable packet delivery

Inventive Principle:
Principle #23Feedback

2Reliability

If RLC retransmissions are performed for every PDCP sequence number gap, then packet delivery completeness is ensured, but unnecessary retransmissions increase network traffic and reduce communication efficiency

Engineering Contradiction:
Improvepacket delivery completenessVSAvoidcommunication efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies preliminary action by establishing PDCP-RLC sequence number binding relationships before data transmission occurs. This pre-configured mapping allows the receiver to immediately distinguish between actual packet loss and PDCP layer gaps, preventing unnecessary RLC retransmissions and improving communication efficiency while maintaining delivery completeness

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The binding relationship acts as an intermediary mechanism between PDCP and RLC layers. It mediates the interaction by providing correlation information that prevents the RLC layer from unnecessarily retransmitting packets when PDCP sequence number gaps occur, thus improving productivity without sacrificing reliability

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20250274245A1PDCP-RLC sequence number binding
Publication Date: 2025.08.28 QUALCOMM INC
  • US20250274245A1 patent drawing
  • US20250274245A1 patent drawing
  • US20250274245A1 patent drawing

AI summary

A method for wireless communication at a user equipment (UE) and related apparatus are provided. In the method, the UE receives a configuration from a network entity. The configuration includes a mapping relationship binding a first set of packet data convergence protocol (PDCP) sequence numbers (SNs) respectively to a second set of radio link control (RLC) SNs. The UE further communicates a data packet with the network entity based on the mapping relationship.