Delivering resources to clients in a distributed computing environment with rendezvous based on load balancing and network conditions

• US 8,296,396 B2
• Filed: 10/31/2007
• Issued: 10/23/2012
• Est. Priority Date: 02/10/1998
• Status: Expired due to Term

• Current Assignee: Level 3 Communications LLC (Lumen Technologies, Inc.)
• Original Assignee: Level 3 Communications LLC (Lumen Technologies, Inc.)
• Inventors: Farber, David A., Greer, Richard E., Swart, Andrew D., Balter, James A.
• Primary Examiner(s): Blair, Douglas
• Application Number:
  US11/980,686
• Publication Number:
  US 20080215755A1
• Time in Patent Office: 1,819 Days
• Field of Search: 709/219, 709/245, 709/226
• US Class Current: 709/219
• CPC Class Codes: G06F 16/957 Browsing optimisation, e.g. caching or content distillation
• CPC Class Codes: G06F 9/505 considering the load
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/10015 Access to distributed or replicated servers, e.g. using brokers
• CPC Class Codes: H04L 67/1006 with static server selection, e.g. the same server being selected for a specific client
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/101 based on network conditions
• CPC Class Codes: H04L 67/1012 based on compliance of requirements or conditions with available server resources
• CPC Class Codes: H04L 67/1019 Random or heuristic server selection
• CPC Class Codes: H04L 67/1023 based on a hash applied to IP addresses or costs
• CPC Class Codes: H04L 67/1025 Dynamic adaptation of the criteria on which the server selection is based
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/2895 Intermediate processing functionally located close to the data provider application, e.g. reverse proxies
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A plurality of repeater servers form a shared content delivery network (CDN) to serve resources to clients on behalf of a plurality of content providers. First and second resources are associated with a first content provider, the first resource referencing the second resource. The second resource is associated with a domain of the shared CDN. Responsive to a request that causes the first resource to be served to a client from a server in a domain associated with the first content provider, a CDN server is identified in the domain associated with the shared CDN to serve the second resource to the client. The CDN server is selected based, at least in part, on load conditions on at least some of the CDN servers, and on the client'"'"'s location. Responsive to the CDN server being requested to serve the second resource: if a copy of the second resource is available on the CDN server, the copy is served to the client from the CDN server; otherwise, the second resource is replicated on the CDN server and then served to the client from the CDN server.

Claims

1. A method for delivering resources to clients in a framework in which a plurality of repeater servers form a shared content delivery network (CDN) operable to serve resources to clients on behalf of a plurality of content providers, wherein a first resource is associated with a first content provider of said plurality of content providers, and wherein said first resource references a second resource via at least a first hostname, the method comprising:

(A) associating the first content provider with the shared CDN such that at least the second resource can be served from the shared CDN to clients on behalf of the first content provider, wherein the associating act (A) comprises;

(a1) configuring each of the plurality of repeater servers with a table listing at least one identifier for each of the plurality of content providers; and

(a2) configuring each of the plurality of repeater servers to record activity related to serving resources therefrom on behalf of the content providers identified in the table; and

(B) after at least a portion of the first resource is served to a client from a content source distinct from said plurality of repeater servers, providing at least a second hostname that is at least partially distinct from the first hostname, and after resolution of the second hostname, serving the second resource to the client from a particular repeater server in the shared CDN selected based, at least in part, on a relative location corresponding to said client and at least some of the plurality of repeater servers, and wherein the serving act (B) comprises;

(b1) if a copy of the second resource is available on the particular repeater server, serving the copy of the second resource to the client from the particular repeater server;

otherwise,

(b2) if a copy of the second resource is not available on the particular repeater server,

(b21) replicating the second resource on the particular repeater server, and

(b22) serving the replicated second resource to the client from the particular repeater server; and

(C) responsive to the serving act (B), recording by the particular repeater server, information related to the serving of the second resource.

2. A method as recited in claim 1, wherein a first uniform resource locator (URL) comprises the first hostname

and a second URL comprises the second hostname, the second hostname comprising at least an identifier associated with the first content provider in the table configured on the particular repeater server.

3. A method as recited in claim 2, wherein the first URL is embedded in the first resource.

4. A method as in claim 2, wherein the particular repeater server is chosen from the plurality of repeater servers based at least in part on the relative location of the client, said relative location determined based at least in part on data corresponding to a cost of transmission between at least some of the repeater servers and the client.

5. A method as in claim 4, wherein the particular repeater server is further chosen, based at least in part on load measurements.

6. A method as recited in claim 1, wherein the particular repeater server is chosen from the plurality of repeater servers using, at least in part, a software component co-located with the content source.

7. A method as recited in claim 1, wherein resolution of the second hostname identifies an IP address corresponding to the particular repeater server.

8. A method as recited in claim 1, wherein the content source comprises an origin server of the first content provider.

9. A method as recited in claim 1, wherein the table configured on each of the plurality of repeater servers further comprises at least one origin server identifier corresponding to each of the content provider identifiers, wherein the replicating act (b1) comprises:

referencing the table using the identifier of the first content provider to determine an origin server associated with the first content provider; and

retrieving the second resource from the origin server associated with the first content provider.

10. A method as recited in claim 1, wherein the recorded information comprises a first timestamp associated with the serving act (B).

11. A method as recited in claim 10, further comprising:

collecting information related to the serving of at least the second resource by at least some repeater servers in the shared CDN that have served the second resource during a first given period in time, the first given period in time including a first time specified in the first timestamp, said collected information being derived at least in part from the recorded information.

12. A method for delivering resources to clients on behalf of a plurality of content providers, wherein at least a first resource maintained on an origin server associated with a first content provider of said plurality of content providers references a second resource via at least a first hostname, the method comprising:

(A) providing a plurality of repeater servers distinct from the origin server;

(B) configuring each of the plurality of repeater servers with a table listing at least one identifier for each of the plurality of content providers; and

(C) configuring each of the plurality of repeater servers to record activity related to serving resources therefrom on behalf of the content providers identified in the table;

(D) after at least a portion of the first resource is served to a client from the origin server, providing at least a second hostname that is at least partially distinct from the first hostname, and after resolution of the second hostname, serving the second resource to the client from a particular repeater server of said plurality of repeater servers, and wherein the serving act (D) comprises;

(d1) if a copy of the second resource is available on the particular repeater server, serving the copy of the second resource to the client from the particular repeater server;

otherwise,

(d2) replicating the second resource on the particular repeater server and then serving the replicated second resource to the client from the particular repeater server,

said particular repeater server having been selected based, at least in part, on a relative location corresponding to said client and at least some of the plurality of repeater servers; and

(E) responsive to the serving act (D), recording, by the particular repeater server, information related to the serving of the second resource.

13. A method as recited in claim 12, further comprising:

determining the relative location of the client based at least in part on data corresponding to a cost of transmission between at least some of the repeater servers and the client.

14. A method as recited in claim 13, further comprising:

using load measurements to select the particular repeater server from the repeater servers considered in the determining step.

15. A method as recited in claim 12, wherein the second resource is originally associated, via a first uniform resource locator (URL), with the origin server, said first URL including the first hostname, the first hostname being resolvable to said origin server, and wherein the method further comprises:

causing the second resource to be associated with at least the particular repeater server via a second URL, wherein said second URL includes the second hostname, the second hostname being resolvable to identify at least the particular repeater server.

16. A method as recited in claim 15, wherein the second hostname is formed by prepending data to the first hostname.

17. A method as in claim 16, wherein the data prepended to the first hostname comprises at least a portion of an identifier associated with the first content provider in the table configured on the particular repeater server.

18. A method as recited in claim 12, wherein the second resource comprises video content.

19. A method as recited in claim 12, wherein the table configured on each of the plurality of repeater servers further comprises at least one origin server identifier corresponding to each of the content provider identifiers, wherein the replicating act (d2) comprises:

referencing the table using the identifier of the first content provider to determine an origin server associated with the first content provider; and

retrieving the second resource from the origin server associated with the first content provider.

20. A method as recited in claim 12, wherein the recorded information comprises a first timestamp associated with the serving act (D).

21. A method as recited in claim 20, further comprising:

collecting information related to the serving of at least the second resource by at least some repeater servers that have served the second resource during a first given period in time, the first given period in time including a first time specified in the first timestamp, said collected information being derived at least in part from the recorded information.

22. A method for delivering resources to clients in a distributed computing framework, said framework including a shared network formed by a plurality of repeater servers operable to serve resources to clients on behalf of the plurality of content providers, wherein at least a first resource associated with a first content provider of said plurality of content providers references a second resource via at least a first hostname, the method comprising:

(A) configuring each of the plurality of repeater servers with a table listing at least one identifier for each of the plurality of content providers, including the first content provider;

(B) configuring each of the plurality of repeater servers to record activity related to serving resources therefrom on behalf of the content providers identified in the table;

(C) after at least a portion of the first resource is served to a client from a content source distinct from said plurality of repeater servers, providing at least a second hostname that is at least partially distinct from the first hostname, and after resolution of the second hostname, serving the second resource to the client from a particular repeater server in the network selected based at least in part on a location corresponding to said client, and wherein the serving step comprises; and

(c1) if a copy of the second resource is available on the particular repeater server, serving the copy of the second resource to the client from the particular repeater server;

otherwise,

(c2) replicating the second resource on the particular repeater server and then serving the replicated second resource to the client from the particular repeater server; and

(D) responsive to the serving act (C), recording, by the particular repeater server, information related to the serving of the second resource.

23. A method as defined in claim 22, wherein the particular repeater server is chosen from the plurality of repeater servers using, at least in part, a software component co-located with the content source.

24. A method as in claim 23, wherein the particular repeater server is chosen by the software component after the software component intercepts a request for the first resource by the client destined for the content source.

25. A method as recited in claim 24, wherein the software component uses at least a Group Reduction Table means and a Link Cost Table means for choosing the particular repeater server from the plurality of repeater servers.

26. A method as recited in claim 22, wherein selection of the particular repeater server is further based at least in part on load conditions on at least some of the plurality of repeater servers.

27. A method as in claim 22, wherein the

second hostname comprises an identifier associated with the first content provider in the table configured on the particular repeater server.

28. A method as recited in claim 22, wherein the table configured on each of the plurality of repeater servers further comprises at least one origin server identifier corresponding to each of the content provider identifiers, wherein the replicating act (b2) comprises:

referencing the table using the identifier of the first content provider to determine an origin server associated with the first content provider; and

retrieving the second resource from the origin server associated with the first content provider.

29. A method as recited in claim 22, wherein the recorded information comprises a first timestamp associated with the serving act (C).

30. A method as recited in claim 29, further comprising:

collecting information related to the serving of at least the second resource by at least some repeater servers in the shared network that have served the second resource during a first given period in time, the first given period in time including a first time specified in the first timestamp, said collected information being derived at least in part from the recorded information.

31. A method for delivering resources to clients on behalf of a plurality of content providers, wherein at least a first resource is maintained on at least a first origin server associated with a first content provider of said plurality of content providers, and wherein at least a second resource is maintained on at least a second origin server associated with a second content provider of said plurality of content providers, said second content provider being distinct from said first content provider, and wherein said first resource references a third resource and wherein said second resource references a fourth resource, the method comprising:

(A) providing a plurality of repeater servers distinct from the first origin server and the second origin server;

(B) configuring each of the plurality of repeater servers with a table listing at least one identifier for each of the plurality of content providers, including the first content provider and the second content provider, wherein the table configured on each of the plurality of repeater servers further comprises at least one origin server identifier corresponding to each of the content provider identifiers;

(C) configuring each of the plurality of repeater servers to record activity related to serving resources therefrom on behalf of the content providers identified in the table; and

(D) after the first resource has been served to a first client from the first origin server, serving the third resource to the first client from a particular repeater server of said plurality of repeater servers, wherein the serving act comprises;

(d1) if a copy of the third resource is available on the particular repeater server, serving the copy of the third resource to the client from the particular repeater server;

otherwise,

(d2) replicating the third resource on the particular repeater server and then serving the third resource to the client from the particular repeater server, the replicating act (d2) further comprising;

referencing the table using at least the identifier of the first content provider to determine an origin server associated with the first content provider; and

retrieving the third resource from the origin server associated with the first content provider,

said particular repeater server having been selected to serve the third resource to the first client based, at least in part, on a relative location corresponding to said first client and at least some of the plurality of repeater servers;

(E) responsive to said serving act (D), recording by the particular repeater server, information related to the serving of the third resource; and

(F) after the second resource has been served to a second client from the second origin server, serving the fourth resource to the second client from the particular repeater server, wherein the serving act comprises;

(f1) if a copy of the fourth resource is available on the particular repeater server, serving the copy of the fourth resource to the second client from the particular repeater server;

otherwise,

(f2) replicating the fourth resource on the particular repeater server and then serving the fourth resource to the second client from the particular repeater server, the replicating act (f2) further comprising;

referencing the table using at least the identifier of the second content provider to determine an origin server associated with the second content provider; and

retrieving the fourth resource from the origin server associated with the second content provider,

said particular repeater server having been selected to serve the fourth resource to the second client based, at least in part, on a relative location corresponding to said second client and at least some of the plurality of repeater servers; and

(G) responsive to said serving act (F), recording by the particular repeater server, information related to the serving of the fourth resource.

32. A method as recited in claim 31, wherein the information recorded in act (E) comprises a first timestamp associated with the serving act (D) and wherein the information recorded in act (G) comprises a second timestamp associated with the serving act (F).

33. A method as recited in claim 32, further comprising:

collecting first information related to the serving of at least the third resource by at least some repeater servers in the shared network that have served the third resource during a first given period in time, the first given period in time including a first time specified in the first timestamp, said first information being derived at least in part from the information recorded in act (E); and

collecting second information related to the serving of at least the fourth resource by at least some repeater servers in the shared network that have served the fourth resource during a second given period in time, the second given period in time including a second time specified in the second timestamp, said second information being derived at least in part from the information recorded in act (G).

34. A method as recited in claim 31, wherein the act of retrieving the third resource from the origin server associated with the first content provider comprises the particular repeater server obtaining the third resource directly from the origin server associated with the first content provider and wherein the act of retrieving the fourth resource from the origin server associated with the second content provider comprises the particular repeater server obtaining the fourth resource directly from the origin server associated with the second content provider.