Shared content delivery infrastructure

• US 20070233884A1
• Filed: 05/30/2007
• Published: 10/04/2007
• Est. Priority Date: 02/10/1998
• Status: Active Grant

• Current Assignee: Level 3 Communications LLC (Lumen Technologies, Inc.)
• Original Assignee: Level 3 Communications LLC (Lumen Technologies, Inc.)
• Inventors: Farber, David, Swart, Andrew, Greer, Richard, Balter, James
• Granted Patent: US 8,572,208 B2
• Time in Patent Office: Days
• US Class Current: 709/229
• CPC Class Codes: G06F 16/957 Browsing optimisation, e.g. caching or content distillation
• CPC Class Codes: G06F 2209/509 Offload
• CPC Class Codes: G06F 9/505 considering the load
• CPC Class Codes: H04L 43/065 related to network devices
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 61/301 Name conversion
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• 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/1014 based on the content of a request
• CPC Class Codes: H04L 67/1019 Random or heuristic server selection
• CPC Class Codes: H04L 67/1021 based on client or server locations
• 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/1036 : Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers
• 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/125 : involving control of end-device applications over a network
• 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/56 : Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• 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/568 : Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5682 : Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 67/61 : taking into account QoS or priority requirements
• CPC Class Codes: H04L 9/40 : Network security protocols

Abstract

A method of processing requests for resources in a system in which a plurality of content providers provide multiple resources. Content providers offload the serving of some of their resources to a shared content delivery network (CDN) formed by a plurality of servers. The CDN is shared among the content providers. Some of a content provider'"'"'s content may be served from an origin server associated with that content provider, while requests for other content from that content provider are served from the shared CDN.

Claims

1. A method of processing requests for resources in a system in which a plurality of content providers provide multiple resources, the method comprising:

responsive to a first request from a first client for a first resource, said first resource being associated with a first content provider, said first request including at least a first hostname, causing said first resource to be served to the first client from a shared content delivery network (CDN) formed by a plurality of repeater servers; and

responsive to a second request from a second client for a second resource, said second resource being associated with a second content provider distinct from said first content provider, and said second request including at least a second hostname distinct from said first hostname, causing said second resource to be served to the second client from the shared CDN.

2. A method as in claim 1 wherein the first resource is a first embedded object referenced in a first web page associated with the first content provider, said first web page having been served to the first client from a first origin server associated with the first content provider.

3. A method as in claim 2 wherein the second resource is a second embedded object referenced in a second web page associated with the second content provider, said second web page having been served to the second client from a second origin server associated with the second content provider.

4. A method as in claim 1 wherein

said first resource is served to the first client from the shared CDN instead of from a first origin server associated with the first content provider;

and

said second resource is served to the second client from the shared CDN instead of from a second origin server associated with the second content provider, said second origin server being distinct from said first origin server.

5. A method as in claim 1 further comprising:

providing said shared CDN.

6. A method as in claim 1 wherein the first content provider is associated with a first domain and the second content provider is associated with a second domain, distinct from the first domain.

7. A method as in claim 6 wherein the first hostname resolves to the shared CDN and wherein the second hostname resolves to the shared CDN.

8. A method as in claim 1 wherein the first resource is to be served from a first CDN server, the method further comprising:

when the first CDN server does not have the first resource, said first CDN server obtaining a copy of the first resource.

9. A method as in claim 8 further comprising:

said first CDN server serving the first resource to the first client.

10. A method as in claim 8 wherein the first CDN server obtains a copy of the first resource from a peer server.

11. A method as in claim 8 wherein the first CDN server obtains a copy of the first resource from a first origin server associated with the first content provider.

12. A method as in claim 1 wherein the first resource is to be served to the first client from a first CDN server and wherein the second resource is to be served to the second client from a second CDN server, the method further comprising:

when the first CDN server does not have the first resource, said first CDN server obtaining the first resource; and

said first CDN server serving the first resource to the first client; and

when the second CDN server does not have the second resource, said second CDN server obtaining the second resource; and

said second CDN server serving the second resource to said second client.

13. A method as in claim 12 wherein:

the first CDN server obtains the first resource from a peer server or from a first origin server associated with the first content provider; and

the second CDN server obtains the second resource from a peer server or from a second origin server associated with the second content provider.

14. A method as in any one of claims 1-13 wherein the system comprises the Internet, and wherein the first request is based, at least in part, on a first Uniform Resource Locator (URL) that includes said first hostname, and wherein the second request is based, at least in part, on a second URL that includes said second hostname.

15. A method as in claim 14 wherein

the first resource is a resource selected from the group comprising static and dynamic:

video content, audio content, text, image content, web pages, HTML files, XML files, files in a markup language, documents, hypertext documents, data files, and embedded resources; and

the second resource is a resource selected from the group comprising static and dynamic;

video content, audio content, text, image content, web pages, HTML files, XML files, files in a markup language, documents, hypertext documents, data files, and embedded resources.

16. A method of processing resource requests in a computer network, the method comprising:

(A) providing a shared network of repeater servers;

(B) responsive to a first request for a first resource, said first resource being associated with a first content provider, at a first repeater server in the shared network of repeater servers,

(b1) if said first repeater server does not have said first resource, said first repeater server obtaining a copy of said first resource; and

(b2) said first repeater serving said first resource; and

(C) responsive to a second request, the second request being for a second resource distinct from said first resource, and said second resource being associated with a second content provider distinct from said first content provider, at a second repeater server in the shared network of repeater servers,

(c1) if said second repeater server does not have said second resource, said second repeater server obtaining a copy of said second resource; and

(c2) said second repeater serving said second resource.

17. A method as in claim 16 wherein the first resource is served from said first repeater server instead of from a first origin server associated with the first content provider, and wherein the second resource is served from said second repeater server instead of from a second origin server associated with the second content provider.

18. A method as in claim 17 wherein said first origin server and said second origin server are distinct from said repeater servers.

19. A method as in claim 16 wherein said first repeater server attempts to obtain a copy of said first resource from a peer server or from a first origin server associated with said first content provider, and said second repeater server attempts to obtain a copy of said second resource from a peer server or from a second origin server associated with said second content provider.

20. A method as in any one of claims 16-19 wherein the system comprises the Internet, and wherein the first request is based at least in part on a first Uniform Resource Locator (URL) that includes said first hostname, and wherein the second request is based, at least in part, on a second URL that includes said second hostname.

21. A method as in claim 20 wherein

the first resource is a resource selected from the group comprising static and dynamic:

video content, audio content, text, image content, web pages, HTML files, XML files, files in a markup language, documents, hypertext documents, data files, and embedded resources; and

the second resource is a resource selected from the group comprising static and dynamic;

video content, audio content, text, image content, web pages, HTML files, XML files, files in a markup language, documents, hypertext documents, data files, and embedded resources.

22. A method as in claim 16 wherein:

said first request is an HTTP request.

23. A method as in claim 22 wherein said HTTP request includes a first hostname that resolves to said shared network of repeater servers.

24. A method as in claim 23 wherein said HTTP request is directed to said first repeater server by an HTTP REDIRECT command.

25. A method of processing requests for resources in the Internet, wherein multiple content providers provide multiple resources to multiple clients, the method comprising:

providing a shared content delivery network (CDN), said CDN being formed by a plurality of repeater servers,

wherein at least some of said repeater servers are constructed and adapted to respond to client requests for resources from a plurality of content providers, and

wherein a first resource, requested by a first client, said first resource being associated with a first content provider, is served to said first client from said shared CDN instead of from said first content provider; and

wherein a second resource, requested by a second client, said second resource being associated with a second content provider distinct from said first content provider, is served from said shared CDN instead of from said second content provider.