Distributing requests across multiple content delivery networks based on subscriber policy

• US 9,203,636 B2
• Filed: 10/31/2007
• Issued: 12/01/2015
• Est. Priority Date: 09/28/2001
• Status: Expired due to Term

• Current Assignee: Level 3 Communications LLC (Lumen Technologies, Inc.)
• Original Assignee: Level 3 Communications LLC (Lumen Technologies, Inc.)
• Inventors: Stolorz, Paul E., Salmon, John K., Warren, Michael S., Koller, Jeffrey G., Hagberg, Aric, Brady, Mark, Pfitzner, David, Middleton, Ted, Yevmenkin, Maksim
• Primary Examiner(s): Walsh, John B
• Application Number:
  US11/932,162
• Publication Number:
  US 20080147866A1
• Time in Patent Office: 2,953 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04L 41/0631 using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
• CPC Class Codes: H04L 41/069 using logs of notifications; Post-processing of notifications
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/04 Processing captured monitoring data, e.g. for logfile generation
• CPC Class Codes: H04L 43/045 for graphical visualisation of monitoring data
• CPC Class Codes: H04L 43/06 Generation of reports
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/0852 Delays
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 43/12 Network monitoring probes
• CPC Class Codes: H04L 61/35 involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
• 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/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• 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/1029 : using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/1031 : Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
• CPC Class Codes: H04L 67/1034 : Reaction to server failures by a load balancer
• 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/52 : specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/55 : Push-based network services
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 : Network security protocols
• CPC Class Codes: H04W 4/02 : Services making use of location information
• CPC Class Codes: H04W 4/021 : Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
• CPC Class Codes: H04W 4/20 : Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel

Abstract

A method, operable in a framework wherein resources of a content provider may be delivered to clients from at least two distinct content delivery networks (CDNs). Responsive to a client request, one of the CDNs is selected, the selection being based at least in part on one or more policies set by the content provider. The client is provided with information associated with the selected CDN. The information may be a domain name such as a CNAME for the selected CDN. The policies may include a load share policy that specifies a relative load share for each CDN, and the selecting may attempt to satisfy the load share policy. Updated content provider policies may be obtained, at regular intervals.

Claims

1. A method, operable in a framework wherein resources of a content provider may be delivered to clients from at least one content delivery network (CDN) formed of a plurality of cache servers or from a subscriber server network associated with the content provider, wherein the subscriber server network is distinct from the at least one CDN, the method comprising:

responsive to receipt of a client request at a name server to resolve a domain name,

retrieving policies from a policy database of the name server, the domain name being associated with a request for at least one resource of the content provider, and

selecting either the at least one CDN or the subscriber server network, the selecting being based at least in part on one or more of the retrieved policies set by the content provider and at least one other retrieved policy, wherein the one or more retrieved policies set by the content provider relate, at least in part, to delivery of resources on behalf of the content provider; and

by hardware in combination with software, providing the client with information associated with the selected network.

2. A method as in claim 1 wherein the information associated with the selected network includes a domain name associated with the selected network.

3. A method as in claim 2 wherein the domain name comprises a CNAME associated with the selected network.

4. A method as in claim 1 wherein the one or more policies set by the content provider include a load share policy that specifies a relative load share for the at least one CDN, and wherein the step of selecting attempts to satisfy the load share policy.

5. The method of claim 1 wherein the selecting is done by a domain name server.

6. A method as in claim 1 further comprising:

obtaining at least one updated content provider policy, and

wherein the one or more of the retrieved policies set by the content provider and used by the step of selecting include the at least one updated content provider policy.

7. A method as in claim 6 wherein the step of obtaining is repeated at regular intervals.

8. A method as in claim 6 wherein the at least one updated content provider policy includes a load share policy for the at least one CDN.

9. A method as in claim 6 wherein the at least one updated content provider policy is obtained from a location specified by the content provider.

10. A method as in claim 1 further comprising:

if the selecting act selects the at least one CDN, then identifying a particular content server in the selected CDN; and

providing the client with an address of the particular content server.

11. The method of claim 1 further comprising:

providing an interface for content providers to update the one or more policies set by the content provider.

12. A method, operable in a framework wherein resources of a content provider may be delivered to users from at least two distinct domains, wherein a first domain comprises a subscriber server network associated with the content provider and a second domain comprises a content delivery network (CDN) distinct from the subscriber server network, the method comprising:

receiving a request from a client resolver to resolve a first domain name, the request being associated with a client request for one of the resources of the content provider;

in response to receipt of the request,

retrieving from a policy database of a name server one or more content provider policies relating to delivery of the one of the resources, at least one of the retrieved policies relating to a relative load share for each of the at least two domains, and

selecting, based at least in part on the one or more retrieved content provider policies set by the content provider and at least one other retrieved policy, one of the at least two domains; and

by hardware in combination with software, providing the client with information associated with the selected domain.

13. A method as in claim 12 wherein the information associated with the selected domain is either (a) a domain name associated with the selected domain or (b) at least one Internet Protocol (IP) address of at least one server in the selected domain.

14. A method as in claim 12 wherein at least one other of the at least two domains corresponds to a second content delivery network domain distinct from the first content delivery network domain and the subscriber server network.

15. A method as in claim 12 wherein the one or more content provider policies include a load share policy that specifies a relative load share for each of the at least two domains, and wherein the step of selecting attempts to satisfy the load share policy.

16. A method as in claim 12 wherein the step of obtaining is repeated at regular intervals.

17. A method as in claim 12 further comprising:

identifying a particular content server in the selected domain; and

providing the client with an address of the particular content server.

18. The method of claim 12 further comprising:

providing an interface for content providers to update the one or more policies set by the content provider.

19. The method of claim 12 wherein the selecting is done by a domain name server.

20. A method, operable in a framework wherein resources of a content provider may be delivered from at least two distinct domains, wherein a first domain comprises a subscriber server network associated with the content provider and a second domain comprises a content delivery network (CDN) distinct from the subscriber server network, the method comprising:

distributing requests to at least one name server to resolve a domain name among the at least two distinct domains based at least in part on one or more load share policies set by the content provider and at least one other policy, the one or more load share policies relating to delivery of content on behalf of the content provider, the one or more load share policies and the at least one other policy being retrieved from a policy database of the at least one name server in response to receipt of at least one of the requests to the at least one name server; and

by hardware in combination with software, providing an interface for the content provider to update the one or more load share policies set by the content provider.

21. A method as in claim 20 wherein at least one of the two distinct domains corresponds to a content delivery network domain.

22. The method of claim 20 wherein the distributing is done by a domain name server.

23. A method, operable in a framework consisting of at least one content delivery network (CDN) comprising a plurality of content servers and capable of delivering resources on behalf of at least one subscriber, wherein the subscriber is associated with a subscriber server network distinct from the at least one CDN, the method comprising:

in response to receipt of a request at a name server to resolve a domain name associated with a particular client request for subscriber content of a particular subscriber of the at least one subscriber,

retrieving from a policy database of a name server one or more policies, the one or more of the retrieved policies including one or more subscriber polices, and

selecting either the at least one CDN or the subscriber server network to handle the particular client request for subscriber content, the selecting being based, at least in part, on one or more retrieved subscriber policies of the particular subscriber, the one or more retrieved subscriber policies relating, at least in part, to delivery of resources on behalf of the particular subscriber and at least one other retrieved policy; and

by hardware in combination with software, causing the client to be directed to the selected network.

24. A method as in claim 23 wherein the one or more subscriber policies include a subscriber-defined load share policy.

25. A method as in claim 23 wherein the step of causing the client to be directed to the selected network comprises:

providing the client with a domain name associated with the selected network.

26. A method as in claim 23 further comprising:

if the selecting act selects the CDN, then identifying a particular content server in the selected CDN; and

providing the client with an address of the particular content server.

27. The method of claim 23 further comprising:

providing an interface for said at least one subscriber to update the one or more subscriber policies.

28. The method of claim 23 wherein the selecting is done by a domain name server.