LIPA Handover via Direct HeNB Gateway Connections
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In mobile communication systems with Home Node B (HNB)/Home eNode B (HeNB) deployments, mobility procedures often require traffic to traverse the core network, leading to inefficiencies and potential service interruptions due to the need for traffic to go through a Security Gateway (SeGW), which can cause delays and security concerns.
Innovation Solution
A method that enables seamless handover of Local IP Access (LIPA) and Selected IP Traffic Offloading (SIPTO) connections without using the operator's core network, allowing direct communication between HeNBs and LIPA/SIPTO gateways, thereby optimizing traffic paths and reducing reliance on the core network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traffic is routed through the core network via Security Gateway during handover, then security requirements are met, but latency increases and service interruptions occur
Solution Approach 1:
The patent segments the traffic routing into two distinct paths: a secure path through the core network for signaling and authentication, and a direct local path for user data traffic. This allows security functions to be performed through the core network while data traffic takes a shorter, lower-latency route directly between the target HeNB and the local IP network, resolving the contradiction between security requirements and latency reduction.
Solution Approach 2:
The patent introduces a gateway as an intermediary entity that bridges the core network and local IP network. This gateway handles security functions and traffic forwarding, allowing the system to maintain security through core network involvement while enabling direct local access that reduces latency. The gateway acts as a mediator that reconciles the conflicting requirements of security and speed.
2Reliability
If traffic is routed through the core network via Security Gateway, then security control is maintained, but network efficiency decreases
Solution Approach 1:
The patent divides network traffic handling into separate functions: security control remains centralized in the core network, while data traffic forwarding is distributed to local gateways and HeNBs. This segmentation allows security control to be maintained at the core network level while data traffic is handled efficiently at the local level, improving overall network productivity without sacrificing security control.
Solution Approach 2:
The patent adds a spatial dimension to traffic routing by creating a parallel path that bypasses the core network for data traffic. Instead of all traffic moving through a single hierarchical path, the system creates a multi-dimensional routing structure where security functions remain centralized but data traffic can take a direct local route, thereby improving network efficiency while maintaining security control.
3Loss of time
If direct connection between HeNB and LIPA gateway is established, then latency is reduced, but security concerns arise due to external location
Solution Approach 1:
The patent introduces security gateways and authentication mechanisms as intermediaries between the HeNB and the local IP network. These intermediaries verify security credentials and establish secure tunnels before allowing direct connections, thus enabling low-latency direct paths while mitigating security threats through layered security validation.
Solution Approach 2:
The patent implements preliminary security authentication and tunnel establishment before direct data traffic flows between HeNB and local IP network. By performing security verification in advance, the system can establish trusted direct connections that reduce latency while ensuring security requirements are met before the harmful factors can exploit the direct path.
4Reliability
If core network is used for handover traffic, then service continuity is maintained, but service interruptions occur due to traversal time
Solution Approach 1:
The patent performs preliminary setup of direct local paths and gateway connections before handover is needed. By pre-establishing routing paths and authentication credentials, the system can switch to low-latency local paths quickly during handover, maintaining service continuity while minimizing the duration of any interruption compared to establishing paths on-demand through the core network.
Solution Approach 2:
The patent maintains continuous data flow by establishing parallel paths: the core network path remains available for control signaling while a direct local path is prepared and activated for data traffic. This continuity of useful action ensures that data transmission can switch paths seamlessly during handover, maintaining service continuity while reducing the time data traffic is interrupted.
Data Source
AI summary
With the deployment of home NodeB or home eNodeB, a user can access both operator's core network and Local Internet (IP) Access (LIPA), e.g. to home based network or general Internet, on the same device at the same time. However, existing mechanisms do not allow an efficient way of LIPA mobility support, especially when there are multiple home NodeBs or home eNodeBs serving the same LIPA domain. The present invention provides a solution that can achieve seamless mobility among different home NodeBs or home eNodeBs without interruption to LIPA service. The LIPA traffic for the terminal can be contained within the local domain during the handover process. It also provides support of the relocation of the gateway that provides the LIPA access to the mobile terminal.