PDCP Version Change for Wireless Handover Data Integrity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current fifth-generation wireless communication systems face challenges in efficiently managing handovers between different Packet Data Convergence Protocol (PDCP) entities, particularly during inter-RAT and intra-RAT handovers, which can result in data loss and require complex bearer type changes, especially when switching between LTE and NR PDCP entities.
Innovation Solution
The method involves performing a PDCP version change by switching from a first PDCP entity to a second PDCP entity, with the network and User Equipment (UE) coordinating this change by releasing the old radio bearer and adding a new one with the updated PDCP entity, and refreshing security keys, while ensuring a lossless transition by determining sequence number lengths and transferring state variables to maintain data integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If PDCP entity switching is performed during handover, then data transmission continuity is improved, but data loss occurs during the transition process
Solution Approach 1:
The source base station performs preliminary actions by determining the PDCP version change requirement before handover, selecting an appropriate PDCP entity for the target base station, and transferring necessary PDCP state variables (such as PDCP sequence numbers and transmission status) to the target base station in advance. This preliminary preparation ensures that the target base station is ready to receive data without interruption, preventing data loss during the handover transition.
2Reliability
If PDCP version change is implemented during handover, then service continuity is maintained, but handover complexity increases
Solution Approach 1:
The patent implements PDCP version change by modifying key parameters during handover, including the PDCP entity identifier, PDCP sequence number length, and security key parameters. The source base station determines whether a PDCP version change is required based on target base station capabilities and service requirements, then transfers updated parameter sets to the target base station. This parameter-based approach maintains service continuity while managing complexity through standardized parameter transitions.
3Manufacturing precision
If sequence number length is changed during PDCP entity switching, then data integrity is improved, but processing complexity increases
Solution Approach 1:
The source base station performs preliminary determination of the appropriate PDCP sequence number length based on the target base station's capabilities and the specific service requirements before handover execution. The determined sequence number length and corresponding PDCP state variables are pre-calculated and packaged for transfer to the target base station. This preliminary action ensures data integrity is maintained while avoiding complex real-time processing during the actual handover transition.
Data Source
AI summary
Embodiments herein disclose a method for performing a handover in a wireless communication network. The method includes performing, by a network, a Packet Data Convergence Protocol (PDCP) version change for one or more radio bearers to switch from a first PDCP entity to a second PDCP entity. Further, the method includes receiving, by a User Equipment (UE), at least one of a PDCP version change indication and security key change indication from the network. Furthermore, the method includes performing, by the UE, a PDCP version change to switch from the first PDCP entity to the second PDCP entity for a configured radio bearer in response to receiving the PDCP version change indication.