HeNB Gateway Redundancy via Multi-Identity Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current small cell network architectures face challenges in managing ambiguity and signaling traffic during small cell gateway failures, particularly due to limitations in redundant configurations and dependency on intelligent TAI lists, which can lead to reduced active TAI lists and increased tracking area updates.
Innovation Solution
Implementing a method where each Home eNode B (HeNB) is configured with multiple global eNode B identities (eNB IDs), allowing it to switch and broadcast corresponding eNB IDs when re-parenting to a different gateway, thereby supporting HeNB-GW redundancy without requiring changes to the Mobility Management Entity (MME) or wasting secondary TAIs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If redundant small cell gateway configurations are implemented, then gateway reliability is improved, but signaling traffic and management complexity increase
Solution Approach 1:
The HeNB is pre-configured with multiple global eNB IDs associated with different HeNB-GWs before a failure occurs. When a gateway failure is detected, the HeNB can immediately switch to a backup gateway using the pre-configured alternative eNB ID, eliminating the need for complex real-time configuration changes and reducing management overhead during failover events.
2Reliability
If intelligent TAI lists are used for gateway redundancy, then gateway failover capability is improved, but active TAI list size decreases and signaling traffic increases
Solution Approach 1:
Instead of using intelligent TAI lists that dynamically manage tracking area identifiers, the invention changes the approach by using multiple global eNB IDs that are statically configured and associated with different HeNB-GWs. This parameter change eliminates the need for complex TAI list management while maintaining failover capability, as the HeNB simply switches between pre-configured eNB IDs rather than managing dynamic TAI lists.
3Reliability
If multiple global eNB IDs are configured for each HeNB, then gateway redundancy is improved, but configuration complexity increases
Solution Approach 1:
The invention makes the global eNB ID a multi-functional parameter that serves both as the identifier for the serving gateway and as the identifier for backup gateways. By configuring multiple global eNB IDs in the HeNB, the same identifier structure is reused for both active and backup gateways, eliminating the need for separate backup identifier configurations and reducing overall system complexity despite providing redundancy.
Data Source
AI summary
An example method is provided and may include steps of configuring a HeNB with plurality of global eNode B identities (global eNB IDs), where each global eNB ID is associated with one of a plurality of HeNB gateways (HeNB-GWs), and broadcasting a first global eNB ID by the HeNB when the HeNB is served by a first HeNB-GW. When/if the HeNB loses connectivity with the first HeNB-GW, the method provides a step of switching the broadcasting from the first global eNB ID to a second global eNB ID and re-parenting the HeNB, now broadcasting or is configured to start/continue broadcasting the second global eNB ID, from being served by the first HeNB-GW to being served by a second HeNB-GW.