PDCP Version Indication in Dual Connectivity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In cellular communication networks, especially in scenarios with high demand for mobile services and data rates, challenges arise in ensuring reliable and efficient exchange of control and performance information between base stations and mobile devices, particularly in dual connectivity arrangements.

Innovation Solution

The implementation of advanced communication protocols and circuitry configurations, such as NR PDCP, to enable efficient communication and data processing in 5G and NR networks, allowing for seamless switching between LTE and NR modes, and optimizing resource allocation and bearer configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If dual connectivity arrangements are implemented to increase network capacity and data rates, then network capacity and throughput are improved, but control information exchange complexity and signaling delays increase

Engineering Contradiction:
Improvenetwork capacityVSAvoidcontrol information exchange complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a version indication mechanism as an intermediary element in the PDCP protocol. This intermediary carries version information that enables both LTE and NR base stations to correctly interpret PDCP packets without requiring complex per-packet negotiation, thus resolving the control information exchange complexity while maintaining dual connectivity benefits

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent applies preliminary action by embedding version information in the PDCP header before packet transmission. This allows the receiving end to pre-configure the appropriate PDCP version interpretation, avoiding real-time decision complexity and reducing signaling delays during dual connectivity operation

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If seamless switching between LTE and NR modes is enabled, then user experience and service continuity are improved, but protocol complexity and processing overhead increase

Engineering Contradiction:
Improvemode switching capabilityVSAvoidprotocol complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent uses parameter changes by modifying the PDCP protocol to include version indication fields that change based on the active connectivity mode. This allows the system to adapt between LTE and NR modes through simple parameter adjustments rather than complex protocol transformations, reducing processing overhead while maintaining seamless switching capability

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If PDCP version compatibility is maintained across LTE and NR networks, then interoperability is improved, but protocol design complexity increases

Engineering Contradiction:
ImprovePDCP version compatibilityVSAvoidprotocol design complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by separating the PDCP protocol into version-specific and version-agnostic components. The version indication field segments the protocol handling, allowing different PDCP versions to coexist with clear demarcation, thereby maintaining compatibility across LTE and NR networks while managing protocol design complexity through structured organization

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11019683B2Methods to indicate a version of packet data convergence protocol (PDCP) in dual connectivity arrangements
Publication Date: 2021.05.25 INTEL CORP
  • US11019683B2 patent drawing
  • US11019683B2 patent drawing
  • US11019683B2 patent drawing

AI summary

Embodiments of a User Equipment (UE), Evolved Node-B (eNB) and methods of communication are generally described herein. The UE may receive a SystemInformationBlockType1 from an eNB. The UE may determine that the eNB supports Fifth Generation Core (5GC) operation if the SysteminformationBlocklType1 message includes a plmn-Identity-5GC-r15 parameter. The UE may transmit a radio resource control (RRC) connection request message to establish an RRC connection. If it is determined that the eNB supports 5GC operation, and if the UE supports 5GC operation, the UE may encode the RRC connection request message in accordance with a default new radio packet data convergence protocol (NR PDCP) configuration; and may use NR PDCP for one or more subsequent messages.