US2008222243A1PendingUtilityA1

Client-side method for identifying an optimal server

Assignee: AKAMAI TECH INCPriority: May 18, 2000Filed: Nov 15, 2007Published: Sep 11, 2008
Est. expiryMay 18, 2020(expired)· nominal 20-yr term from priority
Inventors:David M. Shaw
H04L 67/1001H04L 65/61H04L 67/1038H04L 65/80H04L 67/1008H04L 67/101H04L 67/1021
52
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A client player performs a query to a nameserver against a network map of Internet traffic conditions. The query is made asking for a particular service (e.g., RTSP) via a particular protocol (TCP) in a particular domain. In response, the nameserver returns a set of one or more tokens, with each token defining a machine or, in the preferred embodiment, a group of machines, from which the player should seek to obtain the stream. The player may then optionally perform one or more tests to determine which of a set of servers provides a best quality of service for the stream. That server is then used to retrieve the stream. Periodically, the client player code repeats the query during stream playback to determine whether there is a better source for the stream. If a better source exists, the player performs a switch to the better stream source “on the fly” if appropriate to maintain and/or enhance the quality of service. Preferably, the client player publishes data identifying why it selected a particular server, and such data may be used to augment the network map used for subsequent request routing determinations.

Claims

exact text as granted — not AI-modified
1 . A method, operating in a content delivery network (CDN) having a set of CDN content servers, wherein content requests generated by end user client machines are associated to the set of CDN content servers using a content delivery network (CDN) map, and wherein an end user client machine has an associated media player, comprising:
 providing an end user client machine with a list of a set of CDN servers, wherein the set of CDN servers is identified by the CDN map;   serving a media stream to the end user client machine from a first CDN content server identified in the list;   as the media stream is being served to the end user client machine from the first CDN server, receiving, at each of a subset of the CDN servers, a given request issued from the end user client machine, and returning to the end user client machine a response to the given request;   receiving, for each of the subset of the CDN servers, a data structure that identifies a value indicating a time for the response to be returned to the end user client machine after issuing the given request; and   using the values to generate a modified CDN map.   
   
   
       2 . The method as described in  claim 1  wherein the given request is an RTSP OPTIONS command. 
   
   
       3 . The method as described in  claim 1  wherein the given request is association with a DNS SRV protocol. 
   
   
       4 . The method as described in  claim 1  wherein the data structures are received as the media stream is being served to the end user client machine from the first CDN content server. 
   
   
       5 . The method as described in  claim 4  further including shifting the serving of the media stream from the first CDN content server to a second CDN content server. 
   
   
       6 . The method as described in  claim 5  wherein the second content server is identified using the modified CDN map. 
   
   
       7 . The method as described in  claim 5  wherein the serving of the media stream is shifted upon receipt at the second CDN content server of a request from the end user client machine media player. 
   
   
       8 . The method as described in  claim 5  wherein the serving of the media stream is shifted as a result of the first CDN content server issuing a redirection. 
   
   
       9 . The method as described in  claim 8  wherein the redirection is associated with an RTSP REDIRECT command.

Join the waitlist — get patent alerts

Track US2008222243A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.