HeNB Mobility Support via Version-Based Service Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing wireless communication systems, particularly in 3GPP R-10 networks, fail to support mobility for User Equipment (UE) when it moves out of a Home evolved Node B (HeNB) supporting Local Internet Protocol Access (LIPA), leading to service interruptions and incorrect network operations due to the inability to determine whether the UE is using LIPA or Selected Internet Protocol Traffic Offload (SIPTO) services.
Innovation Solution
A method and apparatus that obtain version information of the Home evolved Node B (HeNB) and subscription information to determine the service type associated with the UE's mobility, establishing UE context information to ensure correct handover operations and prevent service interruptions by distinguishing between LIPA and SIPTO services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the network side uses general APN information for both LIPA and SIPTO services, then both services can be supported, but the network side cannot determine whether the current service is LIPA or SIPTO when the UE moves
Solution Approach 1:
The patent segments the service identification by introducing version information (R-10 or R-11) as a distinct identifier. This allows the network to differentiate between LIPA and SIPTO services by checking the version information in the UE context, thereby resolving the information loss while maintaining support for both service types.
Solution Approach 2:
The patent applies local quality by adding version information specifically to the UE context related to LIPA/SIPTO services. This targeted approach allows the network to identify service types without changing the overall APN information structure, maintaining backward compatibility while enabling precise service differentiation.
2Loss of energy
If the network side cannot determine the service type, then signaling resources and radio resources are wasted due to incorrect network operations, but adding service type determination increases network complexity
Solution Approach 1:
The patent implements preliminary action by determining and storing the service type (LIPA or SIPTO) and version information in the UE context before the UE moves. This allows the network to make correct decisions during handover without requiring complex real-time analysis, thereby reducing resource waste while keeping the added complexity minimal and manageable.
3Ease of operation
If LIPA service is supported in R-10 HeNB, then local IP access is enabled, but mobility is not supported when UE moves out of the HeNB
Solution Approach 1:
The patent applies dynamics by introducing version information that indicates whether the HeNB supports mobility for LIPA services. This allows the network to dynamically adjust its behavior based on the HeNB's capabilities - maintaining LIPA service continuity when moving to R-11 HeNBs that support mobility, while appropriately handling R-10 HeNBs that do not support mobility.
Data Source
Figure 1~2
Figure 3~4
Figure 5
AI summary
Method and apparatus are provided for supporting mobility of a UE in a system without an HeNB GW. An S1 setup request message is sent to an MME by an HeNB. The S1 setup request message includes version information of the HeNB. An RRC connection is established between the UE and the HeNB. An initial UE message is sent from the HeNB to the MME. An NAS message is sent from the UE to the MME. An establish bearer request message is sent from the MME to a corresponding SGW based on an IP address of an LGW. The IP address of the LGW is obtained by the MME through the S1 setup request message. An establish bearer response message is sent from the LGW to the SGW in response to the establish bearer request message. The establish bearer response message is sent from the SGW to the MME.