INTERNET LOCATION COORDINATE ENHANCED DOMAIN NAME SYSTEM

• US 20090222581A1
• Filed: 03/03/2008
• Published: 09/03/2009
• Est. Priority Date: 03/03/2008
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Josefsberg, Arne, Wolman, Alastair, Scheibel, Mark D., Dunagan, John D.
• Granted Patent: US 7,991,879 B2
• Time in Patent Office: Days
• US Class Current: 709/245
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4552 Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1021 based on client or server locations
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04W 4/02 Services making use of location information

Abstract

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.

Claims

1. A network architecture comprising:

a network;

name servers associated with a Domain Name System (DNS);

beacons in communication with the network and positioned at a plurality of locations throughout the network;

clients in communication with the network wherein each of the clients comprises instructions to determine an Internet Location Coordinate (ILC) based in part on sending packets to a plurality of the beacons; and

servers in communication with the network wherein each of the servers comprises instructions to determine an Internet Location Coordinate (ILC) based in part on sending packets to a plurality of the beacons and instructions to send an Internet Location Coordinate (ILC) to one of the name servers of the Domain Name System (DNS).

2. The network architecture of claim 1 wherein, in response to a client request for a domain name, a plurality of the servers associated with the domain name communicate, directly or indirectly, their respective Internet Location Coordinate (ILC) to the client.

3. The network architecture of claim 2 wherein the client selects one of the plurality of servers based in part on the Internet Location Coordinate (ILC) for that server.

4. The network architecture of claim 1 wherein the network comprises the Internet.

5. The network architecture of claim 1 wherein the Internet Location Coordinate (ILC) comprises a plurality of tuples.

6. The network architecture of claim 5 wherein a tuple comprises a beacon identifier and a round trip time (RTT).

7. A method, implemented in part by a computing device, the method comprising:

requesting information for a plurality of servers associated with a network domain name wherein the information comprises information based in part on packets transmitted by each of the plurality of servers to a plurality of network beacons;

receiving the requested information, directly or indirectly, from a name server associated with a Domain Name System (DNS); and

based in part on the received information, selecting an optimal server for the network domain name.

8. The method of claim 7 wherein each of the plurality of servers transmits packets to at least two network beacons to ascertain a transmission time between the server and each of the network beacons.

9. The method of claim 7 wherein each of the network beacons reflects a packet received from a server to allow the server to determine a round trip time (RTT) for the network beacon.

10. The method of claim 7 wherein the information comprises a network latency indicator for each of the plurality of servers.

11. The method of claim 7 wherein a client performs the requesting.

12. The method of claim 7 wherein a client performs the selecting.

13. The method of claim 7 wherein a client performs the requesting and the selecting.

14. The method of claim 7 wherein the receiving comprises receiving a User Datagram Protocol (UDP) packet.

15. The method of claim 7 wherein the requesting comprises a request issued by a Domain Name System (DNS) resolver.

16. The method of claim 7 wherein the selecting comprises selecting an optimal server for the network domain name based in part on transmission times from a client to a plurality of network beacons.

17. A method, implemented in part by a computing device, the method comprising:

transmitting packets to a plurality of network beacons;

based in part on the transmitting, determining a transmission time for each of the plurality of network beacons;

calculating an Internet Location Coordinate (ILC) based in part on the transmission times; and

communicating the Internet Location Coordinate (ILC) to a domain name server.

18. The method of claim 17 further comprising periodically repeating the transmitting, determining and calculating.

19. The method of claim 17 wherein the Internet Location Coordinate (ILC) comprises a tuple for each of the network beacons.

20. The method of claim 19 wherein the tuple comprises a beacon identifier and a round trip time (RTT) for a packet sent to the network beacon.