PDN IP Address Change in Split EPC Architecture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In a split control and user plane Evolved Packet Core (EPC) architecture, managing user equipment (UE) mobility leads to increased signaling and latency due to the need for deactivating and reactivating signaling paths as users move, especially with a large number of users, making it challenging to maintain network connectivity efficiently.
Innovation Solution
A method that determines the need for changing user data plane entities based on UE location, selects new entities, allocates new Packet Data Network (PDN) Internet Protocol (IP) addresses, and communicates these changes to the UE without involving PDN deactivation and reactivation procedures, thereby reducing signaling and latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If user equipment mobility is managed in a traditional EPC architecture, then connectivity is maintained, but signaling overhead and latency increase significantly
Solution Approach 1:
The patent segments the PDN connection management by introducing a PDN connection identifier that remains constant while allowing user plane entity changes. This separation enables mobility management without requiring full PDN deactivation and reactivation, thereby reducing signaling overhead and latency while maintaining connectivity reliability.
Solution Approach 2:
The patent performs preliminary allocation of a PDN connection identifier before user plane entity changes occur. This pre-establishment of the identifier allows seamless transitions during mobility events without requiring subsequent PDN reactivation procedures, reducing signaling latency while maintaining continuous connectivity.
2Reliability
If user equipment mobility is managed by deactivating and reactivating signaling paths, then connectivity is maintained, but the number of signaling operations increases
Solution Approach 1:
The patent separates the control plane PDN connection management from the user plane entity management by introducing a persistent PDN connection identifier. This allows user plane entities to be changed without triggering PDN deactivation and reactivation signaling operations, thereby maintaining connectivity while reducing the number of signaling operations required during mobility events.
Solution Approach 2:
The PDN connection identifier acts as an intermediary that links the control plane to the user plane across entity changes. This identifier enables the network to track and maintain PDN connections through user plane entity transitions without requiring repeated PDN deactivation and reactivation procedures, simplifying the signaling process while ensuring connectivity reliability.
3Productivity
If PDN IP address changes are implemented without connection teardown, then communication continuity is improved, but address management complexity increases
Solution Approach 1:
The patent segments the IP address management by introducing a PDN connection identifier that is separate from the PDN IP address itself. This allows the IP address to change while the connection identifier remains constant, enabling seamless address changes without connection teardown. The identifier acts as a stable reference that simplifies tracking connections despite address changes, offsetting the increased address management complexity.
Solution Approach 2:
The patent implements feedback mechanisms where the network monitors PDN connection identifiers and automatically manages IP address changes while maintaining the association between the identifier and the active connection. This automated feedback-based management reduces the burden of manual address management while ensuring communication continuity during address transitions.
Data Source
AI summary
A method is provided in one example embodiment and may include determining a location for a user equipment (UE); determining whether at least one user data plane entity servicing at least one packet data network (PDN) flow for the UE is to be changed based, at least in part, on the location of the UE; if at least one user data plane entity is to be changed, selecting at least one new user data plane entity to service the at least one PDN flow for the UE; allocating a new PDN Internet Protocol (IP) address for the at least one PDN flow for which the user data plane entity is changed; and communicating the new PDN IP address to the UE.