UPDATING ROUTING INFORMATION BASED ON CLIENT LOCATION

• US 20100125675A1
• Filed: 11/17/2008
• Published: 05/20/2010
• Est. Priority Date: 11/17/2008
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Richardson, David R., Marshall, Bradley E., Sivasubramanian, Swaminathan
• Granted Patent: US 7,991,910 B2
• Time in Patent Office: Days
• US Class Current: 709/242
• CPC Class Codes: H04L 2101/69 using geographic information, e.g. room number
• CPC Class Codes: H04L 45/74 Address processing for routing
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/029 Location-based management or tracking services

Abstract

A system, method, and computer-readable medium for updating request routing information associated with client location information are provided. A content delivery network service provider receives a DNS query from a client computing device. The DNS query corresponds to a resource identifier for requested content from the client computing device. The content delivery network service provider obtains a query IP address corresponding to the client computing device. Based on routing information associated with the query IP address, the content delivery network service provider routes the DNS query. The process further includes monitoring performance data associated with the transmission of the requested resource and updating routing information associated with the query IP address based on the performance data for use in processing subsequent requests form the client computing device.

Claims

1. A computer-implemented method comprising:

obtaining a first DNS query from a client computing device at a first DNS server, wherein the first DNS query corresponds to a first requested resource and wherein the first DNS server corresponds to a content delivery network service;

obtaining a query IP address associated with the first DNS query at the first DNS server;

obtaining a location-based identifier associated with at least a partial IP address corresponding to the query IP address from a routing data store, wherein the routing data store includes at least partial IP address to location-based identifier mappings;

resolving the first DNS query based on the location-based identifier;

collecting performance data associated with transmission of the first requested resource;

modifying the routing data store based on the performance data with an updated location-based identifier associated with the query IP address;

obtaining a second DNS query from the client computing device at a second DNS server, wherein the second DNS query corresponds to a second requested resource;

resolving the second DNS query based on the updated location-based identifier associated with the query IP address of the client computing device.

2. The method as recited in claim 1, wherein the updated location-based identifier is determined based on user profile information associated with the client computing device.

3. The method as recited in claim 2, wherein the updated location-based identifier corresponds to an alternative billing address associated with the client computing device.

4. The method as recited in claim 2, wherein the updated location-based identifier corresponds to a shipping address associated with the client computing device.

5. The method as recited in claim 1, wherein modifying the routing data store comprises adding a new entry to the routing data store mapping the query IP address to the updated location-based identifier.

6. The method as recited in claim 1, wherein modifying the routing data store comprises modifying an existing location-based identifier to at least partial IP address mapping entry with the updated location-based identifier.

7. The method as recited in claim 1, wherein the query IP address is associated with the client computing device.

8. The method as recited in claim 7, wherein the query IP address is associated with a DNS resolver component associated with the client computing device.

9. The method as recited in claim 1, wherein the location-based identifier corresponds to a physical location associated with the client computing device.

10. The method as recited in claim 1, wherein the location-based identifier corresponds to a logical location associated with the client computing device.

11. The method as recited in claim 1, wherein the location-based identifier corresponds to a relative location.

12. The method as recited in claim 11, wherein the relative location is inferred based on an association of the relative location to a known location.

13. The method as recited in claim 12, wherein the relative location is inferred based on latency information

14. A computer-implemented method comprising:

obtaining a first DNS query from a client computing device at a first DNS server, wherein the first DNS query corresponds to a first requested resource and wherein the first DNS server corresponds to a content delivery network service;

obtaining a query IP address associated with the first DNS query at the first DNS server;

obtaining a location-based identifier associated with at least a partial IP address corresponding to the query IP address from a routing data store;

resolving the first DNS query based on the location-based identifier;

collecting performance data associated with transmission of the first requested resource;

updating routing information in the routing data store associated with the query IP address of the client computing device based on the performance data;

obtaining a second DNS query from the client computing device at a second DNS server, wherein the second DNS query corresponds to a second requested resource;

resolving the second DNS query based on the updated routing information associated with the query IP address of the client computing device.

15. The method as recited in claim 14, wherein the routing data store includes at least partial IP address to location-based identifier mappings.

16. The method as recited in claim 15, wherein updating the routing information comprises modifying the routing data store based on the performance data with an updated location-based identifier associated with the query IP address.

17. The method as recited in claim 16, wherein modifying the routing data store comprises adding a new entry to the routing data store mapping the query IP address to the updated location-based identifier.

18. The method as recited in claim 16, wherein modifying the routing data store comprises modifying an existing location-based identifier to at least partial IP address mapping entry with the updated location-based identifier.

19. The method as recited in claim 14, wherein updating the routing information comprises collapsing two or more location-based identifiers to at least partial IP address mapping entries into a single location-based identifier to at least partial IP address data entry based on the performance data.

20. The method as recited in claim 15, wherein the at least partial IP address to location-based identifier mappings each have a corresponding confidence factor.

21. The method as recited in claim 20, wherein updating the routing information comprises modifying the routing data store based on the performance data by updating the confidence factor corresponding to the at least partial IP address to location-based identifier mapping associated with the query IP address of the client computing device.

22. The method as recited in claim 15, wherein the routing data store further includes location-based identifier to destination identifier mappings.

23. The method as recited in claim 22, wherein modifying the routing information comprises modifying the routing data store based on the performance data with an updated destination identifier corresponding to the location-based identifier associated with the query IP address.

24. The method as recited in claim 22, wherein the routing data store further includes network points of presence mappings to at least one of the location-based identifiers and the destination identifiers.

25. The method as recited in claim 24, wherein modifying the routing information comprises modifying the routing data store based on the performance data with an updated network point of presence mapping.

26. The method as recited in claim 24, wherein the network points of presence mappings include distribution allocations.

27. The method as recited in claim 26, wherein modifying the routing information comprises modifying the routing data store based on the performance data with an updated distribution allocation.

28. The method as recited in claim 24, wherein the routing data store further includes a failover list for each network point of presence mapping, wherein the failover list identifies one or more alternative network points of presence for resolving a DNS query associated with the query IP address should the network points of presence identified in the network points of presence mappings be unavailable.

29. The method as recited in claim 28, wherein modifying the routing information comprises modifying the routing data store based on the performance data with an updated failover list.

30. The method as recited in claim 14, wherein the query IP address is associated with the client computing device.

31. The method as recited in claim 30, wherein the query IP address is associated with a DNS resolver component associated with the client computing device.

32. The method as recited in claim 14, wherein the location-based identifier corresponds to a physical location associated with the client computing device.

33. The method as recited in claim 14, wherein the location-based identifier corresponds to a logical location associated with the client computing device.

34. The method as recited in claim 14, wherein the location-based identifier corresponds to a relative location.

35. The method as recited in claim 34, wherein the relative location is inferred based on an association of the relative location to a known location.

36. The method as recited in claim 35, wherein the relative location is inferred based on latency information

37. A computer system comprising:

a routing data store including at least partial query IP address to location-based identifier mappings; and

a first network point of presence associated with a content delivery network service provider, wherein the first network point of presence is operable to;

obtain a first DNS query from a client computing device at a first DNS server, wherein the first DNS query corresponds to a first requested resource and wherein the first DNS server corresponds to a content delivery network service;

obtain a query IP address associated with the first DNS query at the first DNS server;

obtain a location-based identifier associated with at least a partial IP address corresponding to the query IP address from the routing data store;

resolve the first DNS query based on the location-based identifier;

collect performance data associated with transmission of the first requested resource;

update routing information in the routing data store associated with the query IP address of the client computing device based on the performance data;

obtain a second DNS query from the client computing device at a second DNS server, wherein the second DNS query corresponds to a second requested resource; and

resolve the second DNS query based on the updated routing information associated with the query IP address of the client computing device.

38. The system as recited in claim 37, wherein updating the routing information comprises modifying the routing data store based on the performance data with an updated location-based identifier associated with the query IP address.

39. The system as recited in claim 38, wherein modifying the routing data store comprises adding a new entry to the routing data store mapping the query IP address to the updated location-based identifier.

40. The system as recited in claim 38, wherein modifying the routing data store comprises modifying an existing location-based identifier to at least partial IP address mapping entry with the updated location-based identifier.

41. The system as recited in claim 37, wherein updating the routing information comprises collapsing two or more location-based identifier to at least partial IP address mapping entries into a single location-based identifier to at least partial IP address data entry based on the performance data.

42. The system as recited in claim 38, wherein the at least partial IP address to location-based identifier mappings in the routing data store each have a corresponding confidence factor.

43. The system as recited in claim 42, wherein updating the routing information comprises modifying the routing data store based on the performance data by updating the confidence factor corresponding to the at least partial IP address to location-based identifier mapping associated with the query IP address of the client computing device.

44. The system as recited in claim 38, wherein the routing data store further includes location-based identifier to destination identifier mappings.

45. The system as recited in claim 44, wherein modifying the routing information comprises modifying the routing data store based on the performance data with an updated destination identifier corresponding to the location-based identifier associated with the query IP address.

46. The system as recited in claim 44, wherein the routing data store further includes network points of presence mappings to at least one of the location-based identifiers and the destination identifiers.

47. The system as recited in claim 46, wherein modifying the routing information comprises modifying the routing data store based on the performance data with an updated network point of presence mapping.

48. The system as recited in claim 46, wherein the network points of presence mappings include distribution allocations.

49. The system as recited in claim 48, wherein modifying the routing information comprises modifying the routing data store based on the performance data with an updated distribution allocation.

50. The system as recited in claim 46, wherein the routing data store further includes a failover list for each network point of presence mapping, wherein the failover list identifies one or more alternative network points of presence for resolving a DNS query associated with the query IP address should the network points of presence identified in the network points of presence mappings be unavailable.

51. The system as recited in claim 50, wherein modifying the routing information comprises modifying the routing data store based on the performance data with an updated failover list.

52. The system as recited in claim 37, wherein the query IP address is associated with the client computing device.

53. The system as recited in claim 52, wherein the query IP address is associated with a DNS resolver component associated with the client computing device.

54. The system as recited in claim 37, wherein the location-based identifier corresponds to a physical location associated with the client computing device.

55. The system as recited in claim 37, wherein the location-based identifier corresponds to a logical location associated with the client computing device.

56. The system as recited in claim 37, wherein the location-based identifier corresponds to a relative location.

57. The system as recited in claim 56, wherein the relative location is inferred based on an association of the relative location to a known location.

58. The system as recited in claim 57, wherein the relative location is inferred based on latency information