Meta content delivery network system

• US 20030229682A1
• Filed: 11/15/2002
• Published: 12/11/2003
• Est. Priority Date: 05/16/2001
• Status: Active Grant

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Akamai Technologies, Inc.
• Inventors: Day, Richard David
• Granted Patent: US 7,185,052 B2
• Time in Patent Office: Days
• US Class Current: 709/219
• 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/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1014 based on the content of a request
• CPC Class Codes: H04L 67/1021 based on client or server locations
• CPC Class Codes: H04L 67/1025 Dynamic adaptation of the criteria on which the server selection is based
• CPC Class Codes: H04L 67/1029 using data related to the state of servers by a load balancer
• 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/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 9/40 Network security protocols

Abstract

A meta content delivery network system provides a Meta CDN DNS (MCD) server that performs scheduling for multiple content delivery networks (CDN) and is authoritative for all domains given to the CDNs. The MCD contains information about CDNs which participate in each CDN domain names. Each CDN provides to the Meta CDN a domain name that will refer to their CDN'"'"'s portion of the entire Meta CDN for that Meta CDN customer. The MCD receives domain name query requests from local DNSs and selects the proper CDN address based on a predefined capacity reservation of CDNs and statically mapped preferences for certain clients and directs the local DNS requests to the proper CDN address.

Claims

1. A process for scheduling traffic and load balancing between a plurality of Content Delivery Networks (CDN), comprising the step of:

providing a Meta CDN Domain Name Server (DNS) server;

wherein said Meta server is the authoritative for all of the domains of said CDNs;

wherein said Meta server provides a scheduling layer above said CDNs;

wherein said Meta server directs local DNS requests to the proper CDN;

wherein said Meta server records the domain names that each CDN participates in;

wherein said Meta server receives domain name query requests from local DNSs; and

wherein said Meta server returns a CDN domain address based on a predefined capacity reservation of CDNs and statically mapped preferences for certain clients.

2. The process of claim 1, wherein a client'"'"'s local DNS finds which DNS server is authoritative for said CDN domain address and sends a request to that authoritative DNS server.

3. The process of claim 2, wherein said authoritative DNS server performs load balancing for the servers within its CDN and returns an A record to said local DNS.

4. The process of claim 3, wherein said local DNS sends said A record to the requesting client;

and wherein the requesting client uses said A record to make a request to a server within the proper CDN.

5. The process of claim 1, wherein said Meta server defines weights for each CDN;

and wherein said weights are used to control a weighted scheduling algorithm for said CDNs.

6. The process of claim 5, wherein said weights are dynamically adjusted to change CDN priorities.

7. The process of claim 5, wherein each CDN indicates its availability to accept more traffic to said Meta server.

8. The process of claim 1, further comprising the step of:

aggregating billing information for a Meta CDN customer;

wherein each CDN reports to said Meta server, the billing information for said Meta CDN customer; and

wherein said billing information is determined by the amount of traffic redirected to a CDN.

9. The process of claim 8, further comprising the step of:

providing a user interface for an operator to retrieve and report billing information and administrate billing parameters.

10. A process for scheduling traffic and load balancing between a plurality of Content Delivery Networks (CDN), comprising the step of:

providing a Meta CDN Domain Name Server (DNS) server;

wherein said Meta server is the authoritative for all of the domains of said CDNs;

wherein said Meta server provides a scheduling layer above said CDNs;

wherein said Meta server directs local DNS requests to the proper CDN; and

wherein said Meta server records the domain names that each CDN participates in.

11. The process of claim 10, wherein said Meta server receives domain name query requests from local DNSs;

and wherein said Meta server returns a CDN domain address based on a predefined capacity reservation of CDNs and statically mapped preferences for certain clients.

12. The process of claim 11, wherein a client'"'"'s local DNS finds which DNS server is authoritative for said CDN domain address and sends a request to that authoritative DNS server.

13. The process of claim 12, wherein said authoritative DNS server performs load balancing for the servers within its CDN and returns an A record to said local DNS.

14. The process of claim 13, wherein said local DNS sends said A record to the requesting client;

and wherein the requesting client uses said A record to make a request to a server within the proper CDN.

15. The process of claim 10, wherein said Meta server allocates Name Server (NS) records dynamically;

and wherein each CDN keeps said Meta server updated with all of the scheduling devices that each CDN uses.

16. The process of claim 10, wherein said Meta server defines weights for each CDN;

and wherein said weights are used to control a weighted scheduling algorithm for said CDNs.

17. The process of claim 16, wherein said weights are dynamically adjusted to change CDN priorities.

18. The process of claim 16, wherein each CDN indicates its availability to accept more traffic to said Meta server.

19. The process of claim 10, further comprising the step of:

aggregating billing information for a Meta CDN customer;

wherein each CDN reports to said Meta server, the billing information for said Meta CDN customer; and

wherein said billing information is determined by the amount of traffic redirected to a CDN.

20. The process of claim 19, further comprising the step of:

providing a user interface for an operator to retrieve and report billing information and administrate billing parameters.

21. An apparatus for scheduling traffic and load balancing between a plurality of Content Delivery Networks (CDN), comprising:

a Meta CDN Domain Name Server (DNS) server;

wherein said Meta server is the authoritative for all of the domains of said CDNs;

wherein said Meta server provides a scheduling layer above said CDNs;

wherein said Meta server directs local DNS requests to the proper CDN;

wherein said Meta server records the domain names that each CDN participates in;

wherein said Meta server receives domain name query requests from local DNSs; and

wherein said Meta server returns a CDN domain address based on a predefined capacity reservation of CDNs and statically mapped preferences for certain clients.

22. The apparatus of claim 21, wherein a client'"'"'s local DNS finds which DNS server is authoritative for said CDN domain address and sends a request to that authoritative DNS server.

23. The apparatus of claim 22, wherein said authoritative DNS server performs load balancing for the servers within its CDN and returns an A record to said local DNS.

24. The apparatus of claim 23, wherein said local DNS sends said A record to the requesting client;

and wherein the requesting client uses said A record to make a request to a server within the proper CDN.

25. The apparatus of claim 21, wherein said Meta server defines weights for each CDN;

and wherein said weights are used to control a weighted scheduling algorithm for said CDNs.

26. The apparatus of claim 25, wherein said weights are dynamically adjusted to change CDN priorities.

27. The apparatus of claim 25, wherein each CDN indicates its availability to accept more traffic to said Meta server.

28. The apparatus of claim 21, further comprising:

a module for aggregating billing information for a Meta CDN customer;

wherein each CDN reports to said Meta server, the billing information for said Meta CDN customer; and

wherein said billing information is determined by the amount of traffic redirected to a CDN.

29. The apparatus of claim 28, further comprising:

a user interface for an operator to retrieve and report billing information and administrate billing parameters.

30. An apparatus for scheduling traffic and load balancing between a plurality of Content Delivery Networks (CDN), comprising:

a Meta CDN Domain Name Server (DNS) server;

wherein said Meta server is the authoritative for all of the domains of said CDNs;

wherein said Meta server provides a scheduling layer above said CDNs;

wherein said Meta server directs local DNS requests to the proper CDN; and

wherein said Meta server records the domain names that each CDN participates in.

31. The apparatus of claim 30, wherein said Meta server receives domain name query requests from local DNSs;

and wherein said Meta server returns a CDN domain address based on a predefined capacity reservation of CDNs and statically mapped preferences for certain clients.

32. The apparatus of claim 31, wherein a client'"'"'s local DNS finds which DNS server is authoritative for said CDN domain address and sends a request to that authoritative DNS server.

33. The apparatus of claim 32, wherein said authoritative DNS server performs load balancing for the servers within its CDN and returns an A record to said local DNS.

34. The apparatus of claim 33, wherein said local DNS sends said A record to the requesting client;

and wherein the requesting client uses said A record to make a request to a server within the proper CDN.

35. The apparatus of claim 30, wherein said Meta server allocates Name Server (NS) records dynamically;

and wherein each CDN keeps said Meta server updated with all of the scheduling devices that each CDN uses.

36. The apparatus of claim 30, wherein said Meta server defines weights for each CDN;

and wherein said weights are used to control a weighted scheduling algorithm for said CDNs.

37. The apparatus of claim 36, wherein said weights are dynamically adjusted to change CDN priorities.

38. The apparatus of claim 36, wherein each CDN indicates its availability to. accept more traffic to said Meta server.

39. The apparatus of claim 30, further comprising:

a module for aggregating billing information for a Meta CDN customer;

wherein each CDN reports to said Meta server, the billing information for said Meta CDN customer; and

wherein said billing information is determined by the amount of traffic redirected to a CDN.

40. The apparatus of claim 39, further comprising:

a user interface for an operator to retrieve and report billing information and administrate billing parameters.