UPDATING ROUTING INFORMATION BASED ON CLIENT LOCATION

• US 20110252142A1
• Filed: 06/21/2011
• Published: 10/13/2011
• Est. Priority Date: 11/17/2008
• Status: Active Grant

• Current Assignee: Bradley E. Marshall, David R. Richardson, Swaminathan Sivasubramanian
• Original Assignee: Bradley E. Marshall, David R. Richardson, Swaminathan Sivasubramanian
• Inventors: Richardson, David R., Marshall, Bradley E., Sivasubramanian, Swaminathan
• Granted Patent: US 8,234,403 B2
• Time in Patent Office: Days
• US Class Current: 709/226
• 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-58. -58. (canceled)

59. 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, wherein the query IP address is associated with the client computing device;

responsive to obtaining the query IP address, obtaining, at the first DNS server from a routing data store, a location-based identifier at least based on a portion of the obtained query IP address, wherein the routing data store includes at least one partial IP address to location-based identifier mapping;

resolving the first DNS query based at least in part 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 at least in part on the updated location-based identifier.

60. The method as recited in claim 59, wherein the query IP address being associated with the client computing device comprises the query IP address corresponding to a local DNS resolver of the client computing device.

61. The method as recited in claim 59, wherein the location based identifier is different from the obtained query IP address associated with the first DNS query.

62. The method as recited in claim 59, wherein obtaining the location-based identifier comprises matching a portion of the query IP address with a partial IP address identified in the at least one partial IP address to location-based identifier mapping in the routing data store.

63. The method as recited in claim 59, wherein the routing data store includes a full IP address to location-based identifier mapping, and wherein obtaining the location-based identifier comprises matching a portion of the query IP address with a portion of the full IP address identified in the full IP address to location-based identifier mapping in the routing data store.

64. The method as recited in claim 59, wherein the routing data store includes a full IP address to location-based identifier mapping, and wherein obtaining the location-based identifier comprises partially matching the query IP address with a full IP address identified in the full IP address to location-based identifier mapping in the routing data store.

65. The method as recited in claim 59, wherein the updated location-based identifier is determined based at least in part on user profile information associated with the client computing device.

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

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

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

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

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

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

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

73. The method as recited in claim 72, wherein the relative location is inferred based at least in part on an association of the relative location to a known location.

74. The method as recited in claim 72, wherein the relative location is inferred based at least in part on latency information

75. 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, wherein the query IP address is associated with the client computing device;

responsive to obtaining the query IP address, obtaining, at the first DNS server from a routing data store, a location-based identifier at least based on a portion of the obtained query IP address, wherein the location-based identifier corresponds to location information associated with the client computing device and wherein the location-based identifier is different from the obtained query IP address;

resolving the first DNS query based at least in part 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 based at least in part 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 at least in part on the updated routing information associated with the query IP address associated with the client computing device.

76. The method as recited in claim 75, wherein the routing data store includes at least one partial IP address to location-based identifier mapping.

77. The method as recited in claim 75, wherein the query IP address being associated with the client computing device comprises the query IP address corresponding to a local DNS resolver of the client computing device.

78. The method as recited in claim 75, 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.

79. The method as recited in claim 78, 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.

80. The method as recited in claim 78, 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.

81. The method as recited in claim 75, 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 at least in part on the performance data.

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

83. The method as recited in claim 82, wherein updating the routing information comprises modifying the routing data store based at least in part 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.

84. The method as recited in claim 76, wherein the routing data store further includes location-based identifier to destination identifier mappings, wherein a destination identifier corresponds to a geographic region associated with the content delivery network service from which the first requested resource can be resolved.

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

86. The method as recited in claim 84, 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.

87. The method as recited in claim 86, wherein modifying the routing information comprises modifying the routing data store based at least in part on the performance data with an updated network point of presence mapping.

88. A computer system comprising:

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

a first network point of presence associated with a content delivery network service provider, wherein the first network point of presence comprises at least one computing device and 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, wherein the query IP address is associated with the client computing device;

obtain, at the first DNS server from the routing data store, a location-based identifier at least based on a portion of the obtained query IP address, wherein the location-based identifier corresponds to location information associated with the client computing device and wherein the location-based identifier is different from the obtained query IP address;

resolve the first DNS query based at least in part 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 based at least in part 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 at least in part on the updated routing information associated with the query IP address associated with the client computing device.

89. The system as recited in claim 88, wherein the query IP address being associated with the client computing device comprises the query IP address corresponding to a local DNS resolver of the client computing device.

90. The system as recited in claim 88, wherein obtaining the location-based identifier comprises matching a portion of the query IP address with a partial IP address identified in the at least one partial IP address to location-based identifier mapping in the routing data store.

91. The system as recited in claim 88, wherein the routing data store includes a full IP address to location-based identifier mapping, and wherein obtaining the location-based identifier comprises matching a portion of the query IP address with a portion of the full IP address identified in the full IP address to location-based identifier mapping in the routing data store.

92. The system as recited in claim 88, wherein the routing data store includes a full IP address to location-based identifier mapping, and wherein obtaining the location-based identifier comprises partially matching the query IP address with a full IP address identified in the full IP address to location-based identifier mapping in the routing data store.