Identifying an efficient destination server

• US 9,686,229 B2
• Filed: 11/11/2013
• Issued: 06/20/2017
• Est. Priority Date: 12/16/2010
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Thaler, III, David Garfield
• Primary Examiner(s): Tran, Philip B
• Application Number:
  US14/076,981
• Publication Number:
  US 20140075050A1
• Time in Patent Office: 1,317 Days
• Field of Search: 709238, 709241, 709224, 709203
• CPC Class Codes: H04L 2101/69 using geographic information, e.g. room number
• CPC Class Codes: H04L 43/0864 Round trip delays
• CPC Class Codes: H04L 61/35 involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/457 containing identifiers of data entities on a computer, e.g. file names

Abstract

One or more techniques and/or systems are disclosed for identifying a list of destination servers ordered by round-trip time (RTT) for a requesting machine. When a client interacts with an address, such as an IP address, when accessing a remote service, an RTT is collected for the address, or the RTT may be derived for a range of addresses, and saved in a database. When the client subsequently requests access to a remote service, a list of destination servers are returned, respectively identified by corresponding addresses. The destination servers can be sorted in order of efficiency by determining an expected RTT associated with a matching address, or range, in the database, and sorting the destination servers by their respective expected RTTs.

Claims

1. A method, comprising:

receiving a first address of a first server;

receiving a second address of a second server, the first server and the second server both configured to service a same client request;

matching the first address to a first address range, the first address range having a first associated response time;

matching the second address to a second address range, the second address range having a second associated response time; and

ordering the first server and the second server relative to one another based at least upon;

the first associated response time associated with the first address range that is matched to the first address of the first server, the first associated response time based at least in part on an average of a plurality of response times for addresses in the first address range, wherein a response time of the plurality of response times is associated with a round trip response time between a client device associated with the same client request and the first server; and

the second associated response time associated with the second address range that is matched to the second address of the second server.

2. The method of claim 1, at least one of the first address or the second address comprising at least one of:

an Internet Protocol (IP) address;

an IP address plus port;

or

an IP address plus protocol.

3. The method of claim 1, the first address range different than the second address range.

4. The method of claim 1, the first address and the second address associated with a common site.

5. The method of claim 1, the receiving the first address and the second address based at least upon a query for a list of one or more addresses associated with a domain name.

6. The method of claim 1, comprising receiving the first address and the second address from a domain name system server.

7. The method of claim 1, wherein the average is a first average, the plurality of response times is a first plurality of response times, the response time is a first response time, and the round trip response time is a first round trip response time, the second associated response time based at least in part on a second average of a second plurality of response times for addresses in the second address range, wherein a second response time of the second plurality of response times is associated with a second round trip response time between the client device associated with the same client request and the second server.

8. A system, comprising:

one or more processing units; and

memory comprising instructions that are executable by at least one of the one or more processing units to perform acts comprising;

matching a first address of a first server to a first address range, the first address range having a first associated response time, the first associated response time associated with a slowest response time of a first plurality of response times for addresses in the first address range;

matching a second address of a second server to a second address range, the second address range having a second associated response time, the second associated response time associated with a slowest response time of a second plurality of response times for addresses in the second address range, the first server and the second server both configured to service a same client request; and

ordering the first server and the second server relative to one another based at least upon;

the first associated response time associated with the first address range that is matched to the first address of the first server; and

the second associated response time associated with the second address range that is matched to the second address of the second server.

9. The system of claim 8, at least one of the first address or the second address comprising at least one of:

an Internet Protocol (IP) address;

an IP address plus port;

or

an IP address plus protocol.

10. The system of claim 8, the first address range different than the second address range.

11. The system of claim 8, the first address and the second address associated with a common online service.

12. The system of claim 8, wherein the acts further comprise receiving the first address and the second address in response to a query for a list of one or more addresses associated with a domain name.

13. The system of claim 8, the acts further comprising receiving the first address and the second address from a domain name system server.

14. The system of claim 8, wherein a response time of the first plurality of response times is associated with a round trip response time between a client device associated with the same client request and the first server.

15. A computer-readable device comprising instructions that are executable to cause a computing device to:

transmit a query for a list of servers to service a client request;

receive, responsive to the query, a first address of a first server and a second address of a second server;

match the first address to a first plurality of addresses;

match the second address to a second plurality of addresses; and

order the first address and the second address relative to one another based at least upon;

a first historical delay time associated with the first address range that the first server is matched to, the first historical delay time associated with a slowest response time of a plurality of response times for addresses in the first address range; and

a second historical delay time associated with the second address range that the second server is matched to.

16. The computer-readable device of claim 15, at least one of the first address or the second address comprising at least one of:

an Internet Protocol (IP) address;

an IP address plus port;

or an IP address plus protocol.

17. The computer-readable device of claim 15, the first address range different than the second address range.

18. The computer-readable device of claim 15, the first address and the second address associated with a common site.

19. The computer-readable device of claim 15, the list of servers to service the client request queried based at least upon a site name.

20. The computer-readable device of claim 15, the first range of addresses including a contiguous range of Internet Protocol addresses.