IP Flow Mobility via GTP Protocol Translation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile communication networks face capacity exhaustion issues in the 4G and Beyond 4G era, particularly due to the lack of full support for mobile IP protocols in core network infrastructures, which limits the effectiveness of IP flow mobility solutions, especially for GTP-based interfaces between 3GPP and non-3GPP access networks.
Innovation Solution
A method for realizing IP flow mobility between 3GPP and non-3GPP access networks over GTP-based interfaces is proposed, where a user equipment (UE) connected to a PDN-GW initiates an IFOM triggering message to select and move IP flows based on EPS bearer ID and IP flow descriptions, updating mapping tables and initiating a 3GPP bearer modification procedure to relocate selected IP flows.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If IP flow mobility solutions based on DSMIPv6 or PMIPv6 protocols are implemented, then traffic offload capability is improved, but core network infrastructure compatibility deteriorates due to lack of full support for mobile IP protocols
Solution Approach 1:
The patent introduces a Proxy Mobile IPv6 (PMIPv6) gateway as an intermediary entity that translates between mobile IP protocols and GTP. The gateway acts as a mediator between the UE and the core network, converting PMIPv6 signaling messages into GTP-compatible formats, thereby enabling IP flow mobility without requiring full mobile IP protocol support in the core network infrastructure.
Solution Approach 2:
The patent transforms the protocol parameter space by mapping PMIPv6 protocol parameters to equivalent GTP parameters. The gateway performs parameter translation including mapping Mobile Access Identifier (MAI) to GTP tunnel identifiers, transforming Binding Cache entries into GTP bearer contexts, and converting Protocol Configuration Options into GTP-compatible signaling parameters.
2Reliability
If GTP-based interface is used between 3GPP and non-3GPP access networks, then core network infrastructure compatibility is improved, but IP flow mobility functionality deteriorates due to lack of protocol support
Solution Approach 1:
The PMIPv6 gateway serves as a protocol translation intermediary that enables IP flow mobility over GTP-based interfaces. The gateway receives PMIPv6 signaling from the UE, translates it into GTP-compatible signaling messages, and forwards them to the core network, thereby providing IP flow mobility functionality through the GTP interface without requiring native mobile IP protocol support in the core network.
Solution Approach 2:
The patent makes the GTP interface multi-functional by enabling it to carry both traditional GTP traffic and translated PMIPv6 signaling messages. The gateway extends the GTP interface functionality to support mobile IP protocol operations, allowing a single GTP-based interface to fulfill multiple roles including traffic tunneling and mobility management signaling.
3Adaptability or versatility
If multiple access networks are supported simultaneously, then traffic offload flexibility is improved, but network complexity increases due to multiple protocol stacks
Solution Approach 1:
The PMIPv6 gateway acts as an external protocol translation intermediary, offloading the complexity of mobile IP protocol handling from the UE to the network side. The UE only needs to run a simplified PMIPv6 client, while the gateway handles the complex protocol translation and interaction with the GTP-based core network, thereby reducing device complexity while maintaining multi-access connectivity.
Data Source
Figure 1~2
Figure 3~4
Figure 5~6
AI summary
A method to realize IP flow mobility (IFOM) between 3GPP access and non-3GPP access over GTP based interfaces is proposed. A user equipment is connected to a PDN-GW via a 3GPP access network and a non-3GPP access network. The UE transmits an IFOM triggering message to the PDN-GW, which selects IP flows to be moved based on EPS bearer ID and IP flow description. The PDN-GW sends an Update Bearer Request to a WAG or ePDG, and updates its mapping table if the Update Bearer Request is successful. The UE also updates its mapping table upon receiving an IFOM acknowledgement from the WAG or ePDG. The PDN-GW initiates a 3GPP bearer modification procedure to move the selected IP flows.