Internet Location Coordinate Enhanced DNS Server Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The Domain Name System (DNS) is underutilized due to its simplicity, which fails to describe how resources exist in a network environment or local conditions, leading to inefficiencies and congestion issues with rising Internet traffic.
Innovation Solution
An Internet Location Coordinate (ILC) enhanced DNS architecture that uses network beacons to provide location information to participants, allowing for the selection of an optimal server based on factors like time, distance, and network traffic, enhancing routing efficiency and network performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If DNS maintains simplicity with only domain names and structured name space, then ease of operation is improved, but ability to describe network conditions and resources is worsened
Solution Approach 1:
The patent segments the DNS functionality by introducing separate record types (ILC records, LOC records, RLOC records) that can be independently queried and processed. This allows the core DNS to remain simple while adding descriptive capabilities through optional extensions, resolving the contradiction between simplicity and adaptability.
Solution Approach 2:
The patent adds new dimensions to the DNS data structure by incorporating location information (physical location, network location, traffic conditions) alongside traditional domain name data. This dimensional expansion enables the DNS to describe network conditions without fundamentally altering the basic resolution mechanism, thus maintaining ease of operation while improving adaptability.
2Device complexity
If DNS uses only basic domain name resolution, then device complexity is reduced, but productivity is worsened due to congestion issues
Solution Approach 1:
The patent implements preliminary actions by pre-resolving location information and pre-establishing optimal routing paths before actual data transmission occurs. Location records are queried and processed in advance, allowing the system to prepare optimal server selections and routing decisions beforehand, thereby improving productivity without significantly increasing operational complexity.
Solution Approach 2:
The patent incorporates feedback mechanisms where location information and network conditions are continuously monitored and fed back into the DNS resolution process. This feedback loop enables dynamic adjustment of server selections based on real-time conditions, improving productivity while maintaining manageable complexity through automated feedback-driven optimization.
3Ease of manufacture
If DNS lacks location information mechanisms, then ease of manufacture is maintained, but loss of information about network conditions occurs
Solution Approach 1:
The patent introduces location records and ILC records as intermediary elements that bridge the gap between basic DNS resolution and detailed network condition information. These intermediary records carry location data, physical location information, and network conditions as optional fields, enabling information preservation without mandating complex changes to the core DNS manufacturing process.
Solution Approach 2:
The patent applies parameter changes by modifying existing DNS record structures to include optional location and condition parameters. Rather than fundamentally changing how DNS is manufactured, the system extends existing record types with new parameters (location, traffic conditions, network state), thereby preserving ease of manufacture while preventing information loss through enhanced data capabilities.
Data Source
AI summary
An exemplary architecture is for an Internet Location Coordinate enhanced Domain Name System (DNS). An exemplary method includes requesting information for a plurality of servers associated with a network domain name of a Domain Name System (DNS) where the information includes information based in part on packets transmitted by each of the plurality of servers to a plurality of network beacons; receiving the requested information from a name server associated with the Domain Name System (DNS); and, based in part on the received information, selecting an optimal server for the network domain name. Other methods, devices and systems are also disclosed.


