REQUEST ROUTING BASED ON CLASS

• US 20110208876A1
• Filed: 04/29/2011
• Published: 08/25/2011
• Est. Priority Date: 03/31/2008
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Richardson, David R., Scofield, Christopher L., Marshall, Bradley E., Pope, Elmore Eugene, Sivasubramanian, Swaminathan
• Granted Patent: US 8,135,820 B2
• Time in Patent Office: Days
• US Class Current: 709/238
• CPC Class Codes: H04L 41/04 Network management architectures or arrangements
• CPC Class Codes: H04L 45/70 Routing based on monitoring results
• CPC Class Codes: H04L 45/72 Routing based on the source address
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

A system and method for management and processing of resource requests is provided. A content delivery network service provider receives a DNS query from a client computing device. The DNS query corresponds to a requested resource from the client computing device. The content delivery network service provider associates the client computing device with a cluster of other client computing devices. Based on routing information for the cluster, the content delivery network service provider routes the DNS query. The process can further include monitoring performance data associated with the delivery of the requested resource and updating the routing information for the cluster based on the performance data for use in processing subsequent requests from client computing devices in the cluster.

Claims

1-33. -33. (canceled)

34. A method comprising:

obtaining a Domain Name System (DNS) query from a client computing device at a first DNS server, wherein the DNS query corresponds to a requested resource and wherein the first DNS server corresponds to a content delivery network service, the content delivery network service having one or more cache servers to provide the requested resource;

determining a class of the client computing device associated with the DNS query; and

determining routing information based on the class of the client computing device.

35. The method as recited in claim 34, wherein the routing information for the determined class is associated with the first DNS server.

36. The method as recited in claim 35, wherein the routing information for the determined class for the first DNS server is different from routing information for the determined class for a second DNS server of the content delivery network service provider.

37. The method as recited in claim 34, wherein the class corresponds to an interne service provider.

38. The method as recited in claim 34, wherein the class corresponds to a designated geographic location of the requesting client computing device.

39. The method as recited in claim 34, wherein determining routing information comprises selecting a cache component for providing content associated with the resource request based on routing information for the determined class of the client computing device, wherein the cache component is associated with a cache server of the content delivery network service.

40. The method as recited in claim 34, wherein determining routing information comprises:

determining whether the first DNS server is authoritative based on routing information for the determined class of the client computing device; and

if not, selecting a second DNS server for processing the resource request based on the routing information for the determined class of the client computing device.

41. A system comprising:

a first network point of presence associated with a content delivery network service provider, wherein the first network point of presence includes a first Domain Name System (DNS) server that receives a DNS query from a client computing device, wherein the DNS query corresponds to a requested resource associated with a first resource identifier, wherein the content delivery network service provider includes one or more cache servers to provide the requested resource, and wherein the first DNS server in the first network point of presence is operable to;

determine a class of the client computing device associated with the DNS query; and

determine routing information based on the class of the client computing device.

42. The system as recited in claim 41, wherein the routing information for the determined class is associated with the first DNS server.

43. The system as recited in claim 42, wherein the routing information for the determined class for the first DNS server is different from routing information for the determined class for a second DNS server of the content delivery network service provider.

44. The system as recited in claim 41, wherein the class corresponds to an internet service provider.

45. The system as recited in claim 41, wherein the class corresponds to a designated geographic location of the requesting client computing device.

46. The system as recited in claim 41, wherein determining routing information comprises selecting a cache component for providing content associated with the resource request based on routing information for the determined class of the client computing device, wherein the cache component is associated with a cache server of the content delivery network service.

47. The system as recited in claim 41, wherein determining routing information comprises:

determining whether the first DNS server is authoritative based on routing information for the determined class of the client computing device; and

if not, selecting a second DNS server for processing the resource request based on the routing information for the determined class of the client computing device.

48. A system comprising:

a first network point of presence associated with a content delivery network service provider, wherein the first network point of presence includes a Domain Name System (DNS) server component that receives a DNS query from a client computing device, wherein the DNS query corresponds to a requested resource associated with a first resource identifier, wherein the content delivery network service provider includes one or more cache servers to provide the requested resource, and wherein the DNS server component in the first network point of presence is operable to;

associate the client computing device with a cluster of other client computing devices;

determine an alternative DNS server for use in providing the requested resource based on routing information for the cluster; and

cause transmission of the alternative resource identifier to the client computing device, wherein the alternative resource identifier includes information for causing a DNS query to resolve to a domain corresponding to the content delivery service provider.

49. The system as recited in claim 48, wherein the alternative resource identifier corresponds to a canonical name record identifier.

50. The system as recited in claim 48 further comprising:

a second network point of presence associated with the content delivery network service provider, wherein the second network point of presence includes a DNS server component that receives a subsequent DNS query from the client computing device, wherein the subsequent DNS query corresponds to a requested resource associated with the alternative resource identifier, and wherein the DNS server component in the second network point of presence is operable to;

associate the client computing device with a cluster of other client computing devices; and

route the subsequent DNS query based on routing information for the cluster.

51. The system as recited in claim 48 further comprising:

a second network point of presence associated with the content delivery network service provider, wherein the second network point of presence includes a DNS server component that receives a subsequent DNS query from the client computing device, wherein the subsequent DNS query corresponds to a requested resource associated with the alternative resource identifier, and wherein the DNS server component in the second network point of presence is operable to;

resolve the subsequent DNS query to identify a cache component for providing content associated with the original resource request; and

cause transmission of information identifying the identified cache component to the client computing device.

52. A method comprising:

obtaining a Domain Name System (DNS) query from a client computing device at a first DNS server, wherein the DNS query corresponds to a requested resource and wherein the first DNS server corresponds to a content delivery network service provider, the content delivery network service provider having one or more cache servers to provide the requested resource;

associating the client computing device with a cluster of other client computing devices;

determining an alternative DNS server for use in providing the requested resource based on routing information for the cluster; and

causing transmission of the alternative resource identifier to the client computing device, wherein the alternative resource identifier includes information for causing a DNS query to resolve to a domain corresponding to the content delivery service provider.

53. The method as recited in claim 52, wherein the alternative resource identifier corresponds to a canonical name record identifier.

54. The method as recited in claim 52 further comprising:

obtaining a subsequent DNS query from the client computing device at a second DNS server, wherein the subsequent DNS query corresponds to a requested resource associated with the alternative resource identifier and wherein the second DNS server corresponds to the content delivery network service provider;

associating the client computing device with a cluster of other client computing devices; and

routing the subsequent DNS query based on routing information for the cluster.

55. The method as recited in claim 52 further comprising:

obtaining a subsequent DNS query from the client computing device at a second DNS server, wherein the subsequent DNS query corresponds to a requested resource associated with the alternative resource identifier and wherein the second DNS server corresponds to the content delivery network service provider;

resolving the subsequent DNS query to identify a cache component for providing content associated with the original resource request; and

causing transmission of information identifying the identified cache component to the client computing device.