HeNB GW DNS Pre-configuration for X2 Signaling Scaling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The large number of femtocells in 3G and LTE networks creates scaling and signaling load issues for control nodes, and the introduction of a Home eNodeB Gateway (HeNB GW) in the X2 signaling path addresses these problems but introduces an addressing challenge due to the need for frequent DNS configuration during normal network operation.
Innovation Solution
Implementing an automatic one-time pre-configuration of DNS servers with FQDN-to-HeNB GW IP address translation data for all potentially connecting HeNBs, and using aggregated FQDN representation to reduce the size of translation tables, allowing eNBs to establish X2 connections without knowing the HeNB GW ID or its size, and enabling dynamic derivation of HeNB GW identities and addresses from E-CGI of served femtocells.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a HeNB GW is introduced in the X2 signaling path to handle scaling and signaling load, then the control nodes can manage huge numbers of HeNBs, but frequent DNS configuration is required during normal network operation which increases operational complexity
Solution Approach 1:
The patent applies preliminary action by pre-configuring the DNS server with FQDN-to-HeNB GW IP address translation data for all potentially connecting HeNBs before they actually connect. This one-time setup eliminates the need for frequent DNS configuration during normal network operation, resolving the contradiction between handling many HeNBs and avoiding operational complexity
Solution Approach 2:
The system uses aggregated FQDN representation where the DNS server automatically resolves FQDNs to HeNB GW IP addresses without requiring manual intervention. The DNS server serves itself by maintaining pre-configured translation tables that handle multiple HeNBs efficiently, reducing operational complexity while maintaining high productivity
2Ease of operation
If DNS translation tables are configured for all HeNBs to enable X2 connections, then eNBs can establish connections without knowing HeNB GW ID, but the translation tables become large
Solution Approach 1:
The patent merges multiple individual FQDN-to-IP address translations into a single aggregated FQDN entry in the DNS server. Instead of maintaining separate translation records for each HeNB, the system uses one aggregated entry that represents all HeNBs, dramatically reducing the quantity of data in DNS translation tables while maintaining ease of operation for X2 connection establishment
Data Source
AI summary
The present invention relates to methods and arrangements for introducing an automatic one-time configuration of the DNS server(s) when a base station gateway, such as an HeNB GW, is deployed, such that the FQDN-to-HeNB GW IP address translation data is proactively configured. This is performed to identify the base station gateway address to which subsequently deployed base stations will be connected. That is, the FQDN-to-HeNB GW IP address translation data for the HeNB IDs of all the HeNBs that may potentially connect to the HeNB GW is proactively configured in the DNS server(s), thereby avoiding frequent and constantly ongoing DNS configuration during normal network operation. This configuration of the DNS allows the eNB to obtain the destination address for an X2 connection without knowing about an eventual HeNB GW, nor the addressing details, such as size/length (or fixed number of bits) of the HeNB GW ID.