Managing Configured Application-Layer Measurements in Response to a Connection Set-Up Message
US-2024357401-A1 · Oct 24, 2024 · US
US10015243B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10015243-B2 |
| Application number | US-201414291311-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 30, 2014 |
| Priority date | Sep 1, 2010 |
| Publication date | Jul 3, 2018 |
| Grant date | Jul 3, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Some embodiments provide systems and methods for determining a server of a distributed hosting system to optimally distribute content to an end user. The method includes identifying an IP address of the end user. Based on the IP address, a set of servers send packets to the end user to derive performance metrics. The performance metrics are used to determine a server from the set of servers that optimally distributes content to the end user. The method modifies a configuration for resolving end user requests such that the optimal server is identified to the end user when the end user requests content from the hosting system. Some embodiments determine the optimal server by providing downloadable content that is embedded with a monitoring tool. The monitoring tool causes the end user to derive performance metrics for the hosting system when downloading a particular object from a set of servers.
Opening claim text (preview).
We claim: 1. A method for identifying a server from a plurality of distributed servers of a hosting system for responding to a user request, the method comprising: receiving an original Domain Name System (DNS) request at a DNS recursive name server; producing at the DNS recursive name server, a modified DNS request differing from the original DNS request in response to said receiving, wherein said producing comprises propagating from the DNS recursive name server to a different DNS name server, the modified DNS request comprising an Internet Protocol (IP) address of the DNS recursive name server and a particular IP address associated with said user originating said original DNS request, wherein the particular IP address is not an IP address of any DNS server used in resolving the user's DNS request; mapping the particular IP address associated with the user to a particular set of performance metrics from a plurality of performance metrics at a DNS authoritative name server of the hosting system receiving the modified DNS request, wherein the plurality of performance metrics measure content delivery performance of the plurality of distributed servers to a plurality of regions, and wherein the particular set of performance metrics measures content delivery performance of the plurality of distributed servers to a specific region for the particular IP address associated with the user; updating the particular set of performance metrics in response to the DNS authoritative name server receiving the modified DNS request, wherein said updating comprises distributing monitoring packets from at least two of the plurality of distributed servers in different regions to the particular IP address, and revising the particular set of performance metrics based on results from said distributing; and modifying a configuration of the hosting system used in resolving DNS requests comprising IP addresses mapping to the particular set of performance metrics, wherein modifying the configuration comprises changing a DNS response sent from the DNS authoritative name server from providing a first address of a default first server from the plurality of distributed servers to a second address of a different second server from the plurality of distributed servers based on said updating of the particular set of performance metrics, wherein the content delivery performance of the second server to the particular IP address is greater than the content delivery performance of the first server and other servers of the plurality of distributed servers. 2. The method of claim 1 further comprising extracting the particular IP address associated with the user from the modified DNS request. 3. The method of claim 1 , wherein modifying the configuration comprises modifying a DNS resolution table or configuration file of said DNS authoritative name server. 4. The method of claim 1 , wherein the particular set of performance metrics comprise results of the at least two distributed servers either pinging the particular IP address or tracing routes from the at least two distributed servers to the particular IP address. 5. The method of claim 1 further comprising passing in reply to the modified DNS request, a DNS response comprising an IP address of the second server. 6. The method of claim 5 further comprising receiving at the second server, a content request from the particular IP address. 7. The method of claim 6 further comprising passing content in response to the content request from the second server to the particular IP address. 8. The method of claim 1 further comprising aggregating the plurality of performance metrics from the plurality of distributed servers. 9. An authoritative DNS server for an Anycast based hosting system, the hosting system operating a plurality of distributed servers for content distribution to end users, the authoritative DNS server comprising: a network interface receiving a modified DNS request from any of a set of DNS servers in a DNS hierarchy operating to resolve the modified DNS request on behalf a user, wherein the modified DNS request deviates from an original DNS request issued by said user by including a first IP address identifying a DNS server in said DNS hierarchy and adding a second IP address identifying the user of the original DNS request, and wherein the authoritative DNS server receives said modified DNS request instead of the original DNS request from said DNS server in said DNS hierarchy; a memory including program instructions; and a processor operating responsive to the program instructions to: obtain based on the second IP address identifying the user in the modified DNS request, performance metrics identifying content delivery performance from an Anycast address of the hosting system and an IP address of a first server from the plurality of distributed servers to said second IP address; select said Anycast address in response to a different second server from the plurality of distributed servers selected for the second IP address based on Anycast providing faster content delivery performance to the second IP address than the first server as determined from the performance metrics; pass through the network interface in reply to the modified DNS request, a DNS response resolving said modified DNS request to the Anycast address of the hosting system; and update said performance metrics in response to passing the second IP address from the authoritative DNS server to a plurality of monitoring servers of the hosting system in different regions and receiving different performance metrics identifying different content delivery performance from the plurality of monitoring servers. 10. The authoritative DNS server of claim 9 , wherein the processor further operates responsive to the program instructions to obtain the performance metrics by retrieving the performance metrics from each of the plurality of distributed servers. 11. The authoritative DNS server of claim 9 , wherein the processor further operates responsive to the program instructions to initialize a routine on each distributed server causing the distributed server to pass at least one packet to the second IP address and to derive an updated performance metric based on performance associated with passing the at least one packet from the distributed server to the second IP address. 12. The authoritative DNS server of claim 9 , wherein the modified DNS request is modified with an extension mechanism expanding the original DNS request with a field carrying said second IP address in addition to standardized DNS request fields. 13. A method for identifying a server from a plurality of distributed servers of a hosting system for responding to a user request, the method comprising: extracting a first IP address identifying a user issuing an original DNS request from a modified DNS request passing from a DNS server in a DNS hierarchy, wherein said DNS server changes the original DNS request by incorporating said first IP address as part of the modified DNS request; grouping the user with a set of other users in a particular group based on commonality between the first IP address of said user and IP addressing of the set of other users; obtaining in response to said first IP address and said grouping, performance metrics measuring content delivery performance from each of the plurality of distributed servers to a second IP address from the particular group that is different than the first IP address; selecting for the first IP address from the original DNS request, a particular server from the plurality of distributed servers serving content to the second IP address with greater content deliver
Customer-centric QoS measurements · CPC title
Electricity · mapped topic
Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers · CPC title
Delays · CPC title
based on network conditions · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.