HNB Gateway Relocation via Hb Interface
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current user equipment (UE) relocation methods in UMTS networks increase the burden on the core network, require significant storage and reconstruction of context information at the Home Node B Gateway (HNB GW), and fail to efficiently manage downlink user plane data transport and quality of service (QoS) negotiation, especially when UE is in a Cell_FACH state.
Innovation Solution
The method involves the Source Home Node B (S-HNB) sending RANAP Relocation messages to the HNB GW, which then forwards them to the Target Home Node B (T-HNB), reducing the need for HNB GW to store UE context information and allowing T-HNB to allocate resources without alternative RAB parameters, thus optimizing relocation and QoS negotiation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If UE relocation is carried out via SGSN in the core network, then the relocation procedure can be completed, but the burden of the core network is increased and relocation performance is degraded
Solution Approach 1:
The patent extracts the relocation procedure from the core network (SGSN) and implements it at the radio access network level (HNB GW). By taking out the relocation function from the core network, the patent reduces the core network burden while maintaining reliable relocation capability through direct HNB-to-HNB coordination.
2Adaptability or versatility
If HNB GW stores and reconstructs UE context information for relocation, then the relocation can be supported, but the storage requirement and complexity of HNB GW are significantly increased
Solution Approach 1:
The patent introduces a new intermediary interface (Hb interface) between HNB and HNB GW specifically for relocation signaling. This intermediary mechanism allows relocation to be supported without requiring HNB GW to store and reconstruct full UE context information, as the Hb interface handles the relocation coordination directly between HNBs.
3Productivity
If traditional relocation method is used, then UE can be relocated between HNBs, but the downlink user plane data transport and QoS negotiation are not efficiently managed
Solution Approach 1:
The patent applies preliminary action by establishing the Hb interface and defining the relocation signaling procedure in advance. This preliminary setup enables efficient downlink user plane data transport and QoS negotiation during relocation, as the framework is already in place to handle these functions without requiring complex real-time decisions.
Data Source
AI summary
A method for relocating User Equipment (UE). The method includes a Source Home Node B (S-HNB) sending a Radio Access Network Application Part (RANAP) Relocation Required message and a RANAP Relocation Request message encapsulated in a RANAP User Adaptation (RUA) Direct Transfer message to an HNB gateway (HNB GW). The method also includes the HNB GW sending the RANAP Relocation Request message encapsulated in a RUA Direct Transfer message or in a RUA Connection message to a target HNB (T-HNB). The relocation method may have several advantages. For example, the HNB GW is not required to store a large amount of UE Context, thereby reducing the burden of the HNB GW. The interaction with the CN is decreased, thereby reducing the burden of the CN. The HNB GW is not required to construct RANAP relocation messages, thereby reducing the complexity of the HNB GW.