Dynamic DNS Server Federation Route Cache
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication systems in federated domains face inefficiencies and resource expenses due to the need for repeated secure DNS lookups across different domains, as they lack effective caching mechanisms for routing information and cannot prevent futile requests to a federation broker for unavailable information.
Innovation Solution
Implementing a dynamic DNS server with a data cache that stores both positive and negative caching information, allowing it to service communication link requests without needing to query the federation broker for already cached data, thereby reducing the burden on the federation broker and improving resource efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a secure DNS lookup is performed at the federation broker for each communication link to a destination domain, then routing information can be obtained, but time and resource expenses increase
Solution Approach 1:
The patent implements a cache at the originating domain that stores routing information obtained from the federation broker in advance. When a communication link needs to be established, the system first checks the local cache before querying the federation broker, thereby performing the expensive DNS lookup operation preliminarily and avoiding repeated queries for the same destination domain.
Solution Approach 2:
The patent introduces a local cache component at the originating domain that stores routing information locally. This localizes the storage of routing data, allowing the system to quickly retrieve routing information from the local cache rather than repeatedly querying the remote federation broker, thus improving response time while maintaining routing accuracy.
2Reliability
If repeated DNS lookups are performed at the federation broker, then routing information can be obtained, but resource expenses increase
Solution Approach 1:
The system performs DNS lookups preliminarily by caching routing information at the originating domain after the first successful query to the federation broker. Subsequent communication links to the same destination domain use the cached information, preventing repeated energy-consuming queries to the federation broker while ensuring routing information remains available.
Solution Approach 2:
The patent creates a local copy of routing information from the federation broker and stores it in a cache at the originating domain. This copy allows the system to retrieve routing data locally without repeatedly accessing the federation broker, significantly reducing the energy consumption of the broker while maintaining routing information availability.
3Productivity
If DNS lookups are performed without negative caching, then routing information can be queried, but futile requests to unavailable federation brokers increase
Solution Approach 1:
The system performs a preliminary check of the cache before querying the federation broker. If the cache contains negative information indicating that routing information is unavailable for a particular destination domain, the system avoids making futile requests to the federation broker, thereby preventing wasted energy while maintaining productivity by quickly determining unavailability.
4Productivity
If caching is implemented at the I-CSCF as disclosed in US 2008/0181200 A1, then some routing information can be stored, but the system remains limited to addressing local endpoints
Solution Approach 1:
The patent implements a caching mechanism that is not limited to local endpoints but can store and retrieve routing information for any destination domain. The cache at the originating domain can hold routing information for multiple different destination domains, making the system universally applicable to federated communications across any domain, thereby enhancing both productivity and adaptability.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Methods and systems for providing a cache of federated routing information on a dynamic domain name server are provided. More particularly, information obtained from a federation broker can be stored in a dynamic domain name server associated with an enterprise for use in connection with requests for communication links originating from communication endpoints included in the enterprise. By providing this cache of information, requests for federated routing information made to the federation broker can be reduced.