Network Node Configuration Lookup via Distributed Name Server
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for network nodes to look up configuration information, such as DHCP, are limited in that they only allow a single attempt during system boot, may result in outdated information due to changing configurations, and can cause application malfunctions when querying during normal operation, with a hard limit of 255 types of information and lack of support from all servers.
Innovation Solution
A system where a network node creates a query message with an IP prefix and a string specifying the type of configuration information, sent to a name server within a distributed global naming service, allowing for location-specific configuration lookups during system operation, enabling periodic updates and supporting an arbitrary number of configuration types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If DHCP is used to lookup configuration information during system boot, then automatic configuration assignment is achieved, but the network node can only lookup configuration information once and cannot update it during normal operation
Solution Approach 1:
The patent transforms the static, one-time DHCP configuration lookup into a dynamic, ongoing process by introducing a persistent identifier that the network node can use to periodically query configuration information during normal operation, making the configuration system adaptable to changes over time
Solution Approach 2:
The patent introduces a new intermediary component (persistent identifier and query mechanism) between the network node and the configuration information source, allowing the node to actively retrieve updated configuration data without causing IP address reassignment, thus resolving the limitation of single-time lookup
2Ease of operation
If DHCP is used to store configuration information, then automatic assignment is provided, but configuration information can become outdated when changes occur
Solution Approach 1:
The patent implements a feedback mechanism where the network node periodically queries configuration information using its persistent identifier, allowing the system to detect and retrieve updated configuration data, thus maintaining information accuracy while preserving automatic management
Solution Approach 2:
The patent introduces periodic configuration information retrieval operations where the network node actively queries for updated configuration data at scheduled intervals, ensuring that outdated information is replaced while maintaining automatic configuration management
3Loss of information
If DHCP lookup is performed during normal system operation, then configuration information can be retrieved, but the DHCP server may assign a new IP address causing application malfunctions
Solution Approach 1:
The patent extracts the configuration information retrieval function from the DHCP protocol itself, creating a separate query mechanism that uses a persistent identifier to fetch configuration data without triggering the DHCP lease renewal process that would cause IP address changes and application disruptions
4Extent of automation
If DHCP is used for configuration information lookup, then automatic assignment is achieved, but only up to 255 types of configuration information can be supported
Solution Approach 1:
The patent creates a universal configuration information storage and retrieval system that is not constrained by DHCP's 255-type limitation, allowing the network node to query and store an arbitrary number of configuration information types using the persistent identifier mechanism, thus enhancing system versatility while maintaining automatic assignment
Data Source
AI summary
One embodiment of the present invention provides a system for looking up location-specific configuration information for a network node or a subnet. During system operation, a network node creates a query message containing a key that comprises an Internet Protocol (IP) prefix and a string, wherein the IP prefix identifies the network node or the subnet, and the string specifies the type of configuration information. The network node then sends the query message to a name server, which is part of a distributed system that provides a global naming service, wherein the name server additionally stores configuration information. Finally, the network node receives a response message from the name server, wherein the response message contains the requested configuration information.