ILNP Breakout for 5G Session Mobility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The use of anchor points in 5G networks introduces inefficiencies due to the need for traffic tunneling, even when correspondent nodes are geographically close, leading to bandwidth and latency issues, and existing solutions do not effectively address these inefficiencies while maintaining seamless session mobility.
Innovation Solution
The implementation of the Identifier Locator Network Protocol (ILNP) enables a distributed gateway architecture by separating identifier and locator namespaces, allowing traffic to be broken out locally without relying on distant anchor points, and supports incremental deployment by using ILNP breakout capabilities in a 5G network, facilitating seamless session mobility and reducing tunneling overhead.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If anchor points are used in 5G networks for mobility management, then session continuity is maintained during handovers, but traffic tunneling overhead increases and latency increases even for geographically close correspondent nodes
Solution Approach 1:
The patent segments the IP address functionality into two separate namespaces: identifier namespace (for session identification) and locator namespace (for routing). This segmentation allows the identifier to remain stable for session continuity while the locator changes with position, eliminating the need for end-to-end tunneling through anchor points and reducing latency for local traffic.
Solution Approach 2:
The patent extracts the anchoring function from the IP address itself by separating identifier and locator roles. The identifier portion remains fixed for a given session while the locator portion adapts to current position, removing the requirement for traffic to be tunneled through distant anchor points and enabling direct routing when appropriate.
2Ease of operation
If anchor points are used in 5G networks, then mobility management is simplified, but network bandwidth is wasted due to unnecessary tunneling of traffic through distant nodes
Solution Approach 1:
The patent introduces dynamic behavior to the locator namespace, allowing it to change automatically with the user equipment's position while the identifier remains static. This dynamic locator updates enable direct routing to the current location without requiring traffic to traverse through fixed anchor points, optimizing bandwidth usage based on real-time position information.
Solution Approach 2:
The patent enables local quality of routing by allowing traffic to be routed directly to the local access point when the correspondent node is geographically close, rather than forcing all traffic through distant anchor points. This localized routing approach reduces unnecessary bandwidth consumption while maintaining mobility management capabilities.
3Productivity
If ILNP breakout is deployed in 5G networks, then tunneling overhead is reduced and efficiency improves, but compatibility with non-ILNP capable devices and networks is compromised
Solution Approach 1:
The patent implements multi-functionality in the ILNP architecture by enabling it to operate in different modes: full ILNP breakout for ILNP-capable devices to achieve high efficiency, and fallback to traditional anchored routing for non-ILNP capable devices. The identifier-locator separation framework provides a universal foundation that adapts to different capability levels, maintaining compatibility while enabling efficiency improvements where possible.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
A method implemented by a network device functioning as a source gNodeB in a cellular communication network to support incremental deployment of identifier locator network protocol (ILNP) breakout in the cellular communication network. The method includes sending a list of data network names (DNNs) advertised by an access and mobility management function (AMF) to a user equipment (UE), receiving from the UE a first request for a first session with an ILNP session and service continuity (SSC) mode, facilitating the UE establishing a first packet data network (PDN) session associated with a UE selected DNN, where the first PDN session requests the ILNP SSC mode, receiving from the UE a second request for a second session to the selected DNN using a non-ILNP SSC mode, and facilitating the UE establishing a second PDN session to the selected DNN using the non-ILNP SSC mode.