Request routing management based on network components

• US 9,800,539 B2
• Filed: 07/23/2015
• Issued: 10/24/2017
• Est. Priority Date: 09/28/2010
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Richardson, David R., Cormie, John, MacCarthaigh, Colm, Redman, Benjamin W. S.
• Primary Examiner(s): Baturay, Alicia
• Application Number:
  US14/807,726
• Publication Number:
  US 20150334082A1
• Time in Patent Office: 824 Days
• Field of Search: 709217
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/00 Network arrangements or protocols for supporting network services or applications user-to-user messaging H04L51/00; network arrangements, protocols or services for supporting real-time applications in data packet communications networks H04L65/00
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network

Abstract

Systems and methods for managing requesting routing functionality associated with resource requests for one or more resources associated with a content provider are provided. A content delivery network (“CDN”) service provider, on behalf of a content provider, can process domain name service (“DNS”) requests for resources by computing devices and resolve the DNS requests by the identification of a network address of a computing device that will provide the requested resources. Based on the processing of DNS queries initiated by a client computing device, the CDN service provider can measure CDN service provider latencies associated with the generation of DNS requests by network components associated with the client computing devices. Examples of the network components can include DNS resolvers associated with the client computing device.

Claims

1. A computer-implemented system comprising:

a data store for storing performance monitoring information associated with network components associated with client computing device requests for content; and

a computing system in communication with said data store and associated with a service provider, the computing system including a hardware component and operative to;

obtain a first domain name service (DNS) query, the first DNS query corresponding to a resource associated with a resource identifier, and the first DNS query being provided in accordance with a first network scheme;

determine an alternative identifier responsive to the first DNS query, the alternative identifier to cause a second DNS query associated with the resource to be transmitted to a component associated with the service provider utilizing a second network scheme; and

determine an ordered priority of network schemes to use to access particular components associated with the service provider, the determination of the ordered priority being based on performance information associated with the first and second DNS queries.

2. The system as recited in claim 1, wherein the computing system including the hardware component is further operative to:

verify an existing prioritization of components associated with the service provider for servicing requests, the verification of the existing prioritization being based on performance information associated with the first and second DNS queries.

3. The system as recited in claim 1, wherein the resource identifier corresponds to a uniform resource locator of the service provider.

4. The system as recited in claim 1, wherein the alternative identifier references a domain different from a domain associated with the resource identifier.

5. The system as recited in claim 1, wherein the first DNS query is transmitted in accordance with an anycast network scheme.

6. The system as recited in claim 1, wherein the second DNS query is transmitted in accordance with a unicast network scheme.

7. The system as recited in claim 1, wherein the hardware component corresponds to a DNS resolver component.

8. The system as recited in claim 1, wherein the first network scheme corresponds to a first network path and the second network scheme corresponds to a second network path.

9. The system as recited in claim 1, wherein the first and second DNS queries are obtained by different network components.

10. A computer-implemented method comprising:

obtaining, by a service provider, a first domain name service (DNS) query, the first DNS query corresponding to a resource associated with a resource identifier, and the first DNS query being provided in accordance with a first network scheme;

determining, by the service provider, an alternative identifier responsive to the first DNS query, the alternative identifier to cause a second DNS query associated with the resource to be transmitted to a component associated with the service provider utilizing a second network scheme; and

determining a priority of network schemes for accessing components associated with the service provider, the determination of the priority being based at least in part on performance information associated with the first and second DNS queries.

11. The method as recited in claim 10 further comprising verifying an existing prioritization of components associated with the service provider for servicing requests, the verification of the existing prioritization being based on performance information associated with the first and second DNS queries.

12. The method as recited in claim 10, wherein the resource identifier corresponds to a uniform resource locator of the service provider.

13. The method as recited in claim 10, wherein the alternative identifier references a domain different from a domain associated with the resource identifier.

14. The method as recited in claim 10, wherein the alternative identifier includes a label representative of request routing information identifying the component associated with the service provider.

15. The method as recited in claim 10, wherein the alternative identifier further includes a label representative of additional information associated with the client computing device.

16. The method as recited in claim 10, wherein the first DNS query is transmitted in accordance with an anycast network scheme.

17. The method as recited in claim 10, wherein the second DNS query is transmitted in accordance with a unicast network scheme.

18. The method as recited in claim 10, wherein the first DNS query is obtained by a DNS resolver component of the service provider.

19. The method as recited in claim 10, wherein the first network routing scheme corresponds to a first network path and the second network routing scheme corresponds to a second network path.

20. The method as recited in claim 10, wherein the first and second DNS queries are obtained by different network components.