Anchor Relocation Inhibiting Data Transmission During 5G Handover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile network technologies experience service interruptions during anchor relocation in multi-connectivity scenarios, particularly in 5G networks, due to the need for time-critical parameter transfers and data forwarding between old and new anchor locations, leading to latency and potential data reordering issues.
Innovation Solution
Implementing a system that temporarily maintains dual anchor points during relocation, allowing seamless data path switching without interruptions by inhibiting data transmission on the old connection until a predefined event occurs, and ensuring packet sequence continuity through independent operation of both anchors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If anchor relocation is performed in multi-connectivity scenarios, then mobility management is improved, but service interruptions and latency occur due to time-critical parameter transfers and data forwarding between old and new anchor locations
Solution Approach 1:
The patent establishes data forwarding tunnels and transfers anchor parameters (such as PDCP sequence numbers, encryption keys, and routing information) from the old anchor to the new anchor before the actual anchor relocation is triggered. This preliminary preparation ensures that when the anchor relocation occurs, the new anchor is already configured and ready to immediately take over data transmission without causing service interruptions or latency.
2Reliability
If data forwarding is performed between old and new anchor locations during relocation, then continuity is maintained, but data reordering issues and increased complexity occur
Solution Approach 1:
The patent segments the data forwarding process into distinct phases: (1) parameter transfer phase where anchor configuration data is moved from old to new anchor, (2) tunnel establishment phase where data forwarding paths are created, (3) active forwarding phase where user data is routed through the new anchor, and (4) cleanup phase where old anchor resources are released. This segmentation reduces complexity by clearly defining each step and its requirements.
Solution Approach 2:
The patent introduces a control entity (such as a mobility management entity or anchor relocation controller) that acts as an intermediary to coordinate the anchor relocation process. This intermediary manages the timing and sequencing of parameter transfers, tunnel establishment, and data forwarding, ensuring that all operations are synchronized and preventing data reordering issues by controlling the flow of data through the relocation process.
3Ease of operation
If time-critical parameter transfers are performed during anchor relocation, then seamless handover is achieved, but service breaks and latency are introduced
Solution Approach 1:
The patent performs all time-critical parameter transfers (including PDCP sequence numbers, encryption keys, IP addresses, and routing tables) from the old anchor to the new anchor before the anchor relocation is actually triggered. By completing these parameter transfers in advance, the patent ensures that when the relocation occurs, the new anchor is already fully configured and can immediately begin handling user data without any service breaks or latency caused by time-critical parameter transfers.
Data Source
AI summary
It is provided a method, comprising supervising if a request to provide user plane connectivity for a user equipment via a second connection through a second anchor entity is received and if the user plane connectivity for the user equipment is provided via a first connection through a first anchor entity, wherein the first anchor entity and the second anchor entity are differently identified; creating the second connection if the request is received; inhibiting transmitting of user plane data on the second connection from creating the second connection until a predefined event happens if the user plane connectivity for the user equipment is provided via the first connection.