Radio Node Domain Name Construction for O&M Discovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for pre-configuring O&M node addresses in radio network nodes are cumbersome, requiring extensive configuration of DHCP servers and not easily adaptable to different vendors or tracking areas, leading to inefficiencies in radio network node configuration and maintenance.
Innovation Solution
Radio network nodes determine their O&M node addresses by constructing domain names using identifiers such as vendor IDs, IMEIs, and tracking area codes, which are then resolved through a DNS server to obtain the necessary IP addresses for connection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If pre-configuration of O&M node addresses is performed in radio network nodes or DHCP servers, then the configuration process becomes cumbersome and requires extensive manual setup, but the system can establish reliable connections to O&M nodes
Solution Approach 1:
The radio network node automatically constructs its own domain name using its identifier (e.g., IMEI) and queries the DNS server to obtain the O&M node address, eliminating the need for manual pre-configuration in the node itself
Solution Approach 2:
A DNS server is introduced as an intermediary between the radio network node and the O&M node, translating node identifiers into O&M node addresses dynamically, thereby simplifying the configuration process while maintaining connection reliability
2Adaptability or versatility
If DHCP servers are configured with multiple O&M node addresses for different vendors and tracking areas, then the system can support multi-vendor and multi-area operations, but the DHCP server configuration becomes increasingly complex and difficult to maintain
Solution Approach 1:
The DNS server acts as a mediator that handles the complexity of mapping multiple node identifiers (from different vendors and tracking areas) to appropriate O&M node addresses, freeing the DHCP server from this complex configuration task
Solution Approach 2:
The system changes from using DHCP-based address allocation to DNS-based resolution, where the domain name construction parameters (node identifier, vendor ID, tracking area code) are dynamically combined and resolved, enabling flexible multi-vendor and multi-area support without complex DHCP configurations
3Manufacturing precision
If manual configuration of O&M node addresses is performed for each radio network node, then precise control over node-O&M node mapping is achieved, but the configuration process becomes time-consuming and labor-intensive
Solution Approach 1:
Each radio network node autonomously constructs its domain name using its unique identifier and queries the DNS server to obtain the correct O&M node address, eliminating manual configuration while maintaining precise node-O&M node mapping
Solution Approach 2:
The system uses a standardized domain name construction template that is copied and applied to each node based on its identifier, automatically generating the correct domain name without manual intervention while preserving precise mapping relationships
Data Source
AI summary
A domain name associated with a radio network node's operator or maintenance (OM) node is determined based on at least part of a radio node identifier and a radio network operator identifier. The radio network node sends the domain name to a domain name server. In response to sending the constructed domain name, the radio network node receives from the domain server an IP address for the OM node. The radio network node then initiates a connection with the OM node using the IP address. In one non-limiting example embodiment, the part of the radio node identifier is a radio network node vendor identifier.