Non-3GPP to 3GPP Handover Optimization via Pre-registration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing handover procedures from non-3GPP networks to 3GPP networks experience delays and interruptions due to MME relocation and S-GW relocation, especially when simultaneous connectivity with multiple radio interfaces is not possible, leading to additional signaling and potential session interruptions.
Innovation Solution
The method involves pre-registering the mobile node with a new Mobility Management Entity (MME) and pre-selecting a new Serving-Gateway (S-GW) before the actual handover, ensuring that the necessary contexts are relocated and data paths are switched in advance, thereby eliminating delays and interruptions during the handover process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If MME relocation is performed during handover from non-3GPP to 3GPP network, then the mobile node can be registered with the appropriate mobility management entity, but handover delays and signaling overhead increase
Solution Approach 1:
The patent applies preliminary action by pre-determining the target MME based on the mobile node's current location and pre-registering the mobile node with the target MME before the actual handover occurs. This allows the mobility management entity to be prepared in advance, eliminating the need for time-consuming MME relocation signaling during the handover process itself.
Solution Approach 2:
The patent segments the handover process into distinct phases: a preparation phase where the target MME is determined and the mobile node is pre-registered, and an execution phase where the handover is performed. This segmentation allows the complex MME relocation process to be decoupled from the critical handover timing, improving overall handover performance.
2Productivity
If S-GW relocation is performed during handover from non-3GPP to 3GPP network, then the data path can be optimized, but session interruptions and handover delays occur
Solution Approach 1:
The patent applies preliminary action by pre-selecting the target Serving Gateway based on the mobile node's location and pre-establishing the data path through the target S-GW before the handover occurs. This ensures that the data path is ready in advance, preventing session interruptions during the actual handover execution.
Solution Approach 2:
The patent maintains continuity of useful action by ensuring that the data path through the Serving Gateway is established and active before the handover completes. The mobile node can continue data transmission without interruption because the S-GW relocation has already been performed in the preparation phase.
3Adaptability or versatility
If MME and S-GW relocations are performed during handover, then network mobility management is achieved, but additional signaling and handover interruptions occur
Solution Approach 1:
The patent applies preliminary action by performing both MME determination and S-GW selection in advance, before the handover is triggered. This allows the network to prepare all necessary mobility management functions beforehand, reducing the signaling overhead during the actual handover process and simplifying the handover execution.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
The invention relates to a method for a handover of a mobile node from a non-3GPP to a 3GPP network, and of a mobile node, which is located in a non-3GPP/ 3GPP network. The handover is improved by discovering an appropriate MME and registering the mobile node at the discovered MME, in advance. This includes to first determine the location of the mobile node in the non-3GPP network, so as to be able to detect an MME in the vicinity of the mobile node's location. The 3GPP contexts are then transmitted to the new MME before the handover is performed. Moreover, the invention teaches to change the Serving-Gateway in the 3GPP network before performing a handover, thereby accelerating the handover. When a handover gets likely, the mobile node's location is determined and a new Serving-Gateway is selected. The data path is changed to go via the new Serving-Gateway.