H04L67/10—Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network

H04L67/1002—Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers, e.g. load balancing

H04L67/10—Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network

H04L67/1002—Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers, e.g. load balancing

H04L67/1004—Server selection in load balancing

H04L67/1008—Server selection in load balancing based on parameters of servers, e.g. available memory or workload

H04L67/10—Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network

H04L67/1002—Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers, e.g. load balancing

H04L67/1004—Server selection in load balancing

H04L67/1014—Server selection in load balancing based on the content of a request

H04L67/10—Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network

H04L67/1002—Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers, e.g. load balancing

H04L67/1004—Server selection in load balancing

H04L67/1021—Server selection in load balancing based on client or server locations

H04L67/10—Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network

H04L67/1002—Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers, e.g. load balancing

H04L67/1025—Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers, e.g. load balancing dynamic adaptation of the criteria on which the server selection is based

H04L67/10—Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network

H04L67/1002—Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers, e.g. load balancing

H04L67/1029—Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers, e.g. load balancing using data related to the state of servers by a load balancer

H04L2029/06054—Access to distributed or replicated servers, e.g. using brokers

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.

Description

BACKGROUND OF THE INVENTION

1. Technical Field [0001]

The invention relates to network traffic management in a computer environment. More particularly, the invention relates to traffic scheduling between multiple independent content delivery networks in a computer environment. [0002]

2. Description of the Prior Art [0003]

A Content Delivery Network (CDN) is collection of caching, streaming, storage, and other servers distributed throughout the Internet in order to deliver content closer to the end user, avoiding the “middle mile” problem. [0004]

CDN's provide two main benefits to their users (in this case the user is the customer or content owner, not the end user). The first is reduction of traffic at the origin site. Every request that arrives at the CDN is a request not arriving at the origin site. This means that the origin site will have less work to do as it utilizes the CDN more and more. In addition, the type of work that is being removed is often very different than what will continue to be directed at the origin site. As an example, all of the requests for images which result in many connections to a server are removed from the origin while connections that need access to the database remain. This allows the origin site to be tuned for the database type requests that it will be receiving. A CDN of at least one POP will provided this benefit to a customer. [0005]

The second benefit is increased performance for the delivery of the content by reducing the network delay between the browser and the content. This is done by placing servers in locations near the end users and using a system to direct end users to the “best” server. Each customer will have a different group of end users. Some will need full global coverage while other may only need certain parts of the world. [0006]

A network provider building their own CDN has a very cost effective solution for solving the first problem of reducing origin site load. Owning their own network, they often see their internal costs for using it as very low, and as a result can price a CDN solution very low. The ability of a given network provider to solve the second issue with only their own connectivity, will not work for all customers. [0007]

Today there are two types of CDNs generally available: facilities-based CDNs (also referred to as an on-net CDN) and multi-network CDNs. A facilities-based CDN has deployment limited to a single service provider's network and points of presence (POPs). A multi-network, CDN has servers distributed on many different service provider networks and POPs. [0008]

In general, multi-network CDNs provide higher performance, availability, redundancy, and scalability than facilities-based CDNs, due to the fact that no one service provider network controls all the content providers (servers) and/or the eyeballs (clients). Also, not many service providers have sufficient coverage and POPs to distribute and deliver content. Thus, a multi-network CDN will outperform a facilities-based CDN in all cases. [0009]

However, some service providers still want to create a facilities-based CDN in order to maintain traffic on their own network as well as to participate in this new and growing market. There is a need to provide the facilities-based CDN providers the advantages of multi-network CDNs. [0010]

It would be advantageous to provide a meta content delivery network system that provides load balancing and traffic scheduling across independent CDNs in a computer network. It would further be advantageous to provide a meta content delivery network system that allows CDN providers to designate the availability of their networks. [0011]

SUMMARY OF THE INVENTION

The invention provides a meta content delivery network system. The system provides load balancing and traffic scheduling across multiple content delivery networks (CDN) in a computer network. In addition, the invention allows CDN providers to designate the availability of their networks and to assign clients to specific CDNs. [0012]

A preferred embodiment of the invention provides a Meta CDN scheduling layer above multiple content delivery networks (CDN). This combined Meta CDN provides customers with the combined scale and reach of all the underlying CDNs. [0013]

Meta CDN scheduling is performed by a Meta CDN DNS (MCD) server. The MCD server is authoritative for all domains given to customers of the Meta CDN service. The MCD contains information about which CDNs participate in which 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. [0014]

The MCD receives domain name query requests from local DNSs. It 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. [0015]

The local DNS finds which DNS server is authoritative for the CDN address and sends a request to that authoritative DNS server. The authoritative DNS server performs load balancing for the servers within its CDN and returns an A record to the local DNS which forwards the A record to the requesting client. The requesting client uses the A record to make a request to a server within the proper CDN. [0016]

The MCD defines weights for each CDN which are used to control a weighted scheduling algorithm for the CDNs. The weights are dynamically adjusted to change CDN priorities. [0017]

Alternatively, the MCD allocates Name Server (NS) records dynamically to the local DNS. Each CDN keeps the MCD updated with all of the scheduling devices that each CDN uses. [0018]

Other aspects and advantages of the invention will become apparent from the following detailed description in combination with the accompanying drawings, illustrating, by way of example, the principles of the invention.[0019]

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block schematic diagram of an on-net architecture according to the invention; [0020]

FIG. 2 is a block schematic diagram of an overlay architecture according to the invention; [0021]

FIG. 3 is a block schematic diagram of a content proxying example according to the invention; [0022]

FIG. 4 is a block schematic diagram of a Meta CDN scheduling layer above multiple CDNs according to the invention; [0023]

FIG. 5 is a block schematic diagram of an authoritative Meta CDN DNS (MCD) server for a group of CDNs according to the invention; and [0024]

FIG. 6 is a block schematic diagram of an exemplary MCD load balancing and redirection packet flow according to the invention. [0025]

DETAILED DESCRIPTION OF THE INVENTION

The invention is embodied in a meta content delivery network system in a computer environment. A system according to the invention provides load balancing and traffic scheduling across multiple content delivery networks (CDN) in a computer network. In addition, the invention allows CDN providers to designate the availability of their networks and to assign clients to specific CDNs. [0026]

The invention provides a Meta Content Delivery Network (CDN) DNS server that enables multiple independent CDN providers to maximize the bandwidth of their network as well as their revenue. [0027]

CDNs are a collection of servers deployed at different points on the Internet. A scheduling layer is provided above them that determines which server a given client should use. This scheduling is based on the load/availability of each server and their relative proximity, or latency, to the clients (users). By directing clients to the least loaded and lowest latency server, download time is greatly reduced as well as the load on the origin servers. [0028]

There are two main architectures in use by CDNs: on-net and overlay. Both methods have the CDN as authoritative for the domain name to be accelerated through DNS. Varying degrees of importance are placed on the role DNS takes in making the actual server selection. [0029]

On-Net Architecture [0030]

Referring to FIG. 1, an on-net deployment is a collection of servers [0031] 102, 103, 104, 105 arranged around the edge of a single network 101. This allows content to be served from the “on network” side of peering points, reducing the traffic across the backbone of the on network. In addition, it places servers 102, 103, 104, 105 close to clients 106, 107, 108, 109, 110 who are on network. Since the servers exist on a single network, routing techniques can be used to direct clients to the server with the least latency to a given client. This can be achieved by broadcasting routes for the IPs of the servers out all interfaces that connect this network to other networks. This causes off net client requests to find the closest entry point to the on network where they immediately find a server with that IP. Because the CDN owns the network, it is able to deploy servers in locations such as peering points to make the service compelling. Network traffic still needs to cross the peering point for clients that originate from off net.

Overlay Architecture [0032]

With respect to FIG. 2, overlay networks deploy their servers across multiple networks [0033] 202, 203, 204, 205. Because these deployments span networks 202, 203, 204, 205, scheduling using routing tricks is difficult or impossible. Instead, overlay architectures are usually designed around a smart DNS server 201 that makes the determination of where to send users at DNS resolution time.

The smart DNS server [0034] 201 uses the source IP address of the client making the request to determine latency from the client to servers in the network. The Smart DNS server 201 also uses server load and availability information to direct the client to the best possible server.

Domain Names [0035]

In both architectures, to have content served from a CDN, the content must be under a domain that the CDN is authoritative for. This is done by the content owner delegating a domain name to the CDN or by the CDN creating a name in their domain for the customer to use. The latter tends to work better as it avoids any possible misconfiguration of the DNS on the part of the content owner. [0036]

The CDN has to understand what type of content the customer needs to support and may have content types mapped into domain names. In other words, when the customer wants to use the CDN for SSL content, they may use the hostname ssl-customer.cdn.com. For HTTP content, they may use the hostname http-customer.cdn.com. This allows the CDN to have specialized servers for different types of content. [0037]

Protocol Support [0038]

Communication on the Internet takes multiple forms, HTTP, SSL, FTP, streaming media, etc. CDNs, since they are not the creators of the content, cache content on behalf of the creator. Not all CDNs support all content types, or if they do, they may go about supporting a protocol using different solutions. [0039]

How Content Gets In [0040]

There are typically two methods for getting content into a CDN; proxying and publishing. The different methods are chosen for different reasons based on the way the content will be used. [0041]

Content Proxying [0042]

Rferring to FIG. 3, using content proxying, origin servers [0043] 301, 302, 303, keep master copies of content and CDN servers 303, 304, 305, 306 cache content. Requests sent to CDN servers include enough information to allow them to fetch the content from the origin servers if the content is not already cached.

The mapping of requested content to origin content is accomplished using multiple methods and is protocol dependent. HTTP and SSL protocol requests normally use one of two methods: embedded URL information and Host directive mapping. As a real example of each, consider a single piece of content we wish to have served from a CDN: [0044]

http://www.customer.com/path/to/object.gif [0045]

If the content is going to be mapped to the origin site by the host directive the CDN URL would look like this: [0046]

http://customer.cdn.com/path/to/object.gif [0047]

CDN servers would notice the HTTP host header customer.cdn.com and would have a table that maps it to www.customer.com. [0048]

Host based directive approaches have a few draw backs. First, a different CDN domain name needs to be given for each customer origin site. Second, all webcaches have to be updated with information in some way to add a new customer to the system. Finally, clients that do not send the host directive in their request will not be able to be supported with this solution. [0049]

If the content is going to be mapped to the origin site using embedded URL information, the CDN URL could look like this: [0050]

http://customer.cdn.com/www.customer.com/path/to/object.gif [0051]

In this solution, the CDN server can find the name of the origin site in the request (in this case in-between the first two slashes). This approach reduces the complexity of having to ensure that the CDN servers have access in some way to the host directive mapping and solves the problem of supporting clients that do not send a host directive in their requests. This approach requires changing the URLs that refer to the content to a URL formatted as above. [0052]

Content Publishing [0053]

Using content publishing, CDN servers are thought of like origin sites. An external mechanism is used to ensure the CDN servers are in sync with the origin site. This could be thought of as a mirroring solution. It tends to work well for large file size content or protocols that do not lend themselves well to proxying. [0054]

Meta Content Delivery Network [0055]

With respect to FIG. 4, the Meta CDN [0056] 401 provides a scheduling layer above multiple content delivery networks 402, 403, 404, 405, 406. This combined Meta CDN 407 provides customers with the combined scale and reach of all the underlying CDNs. The benefits to the customer is greater than that which can be provided by any of the underlying CDNs.

Architecture [0057]

Referring to FIG. 5, Meta CDN scheduling is performed by a Meta CDN DNS (MCD) server [0058] 501. The MCD server 501 is authoritative for all domains given to customers of the Meta CDN service 502.

Scheduling [0059]

The MCD is provided with information about which CDNs participate in which 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. Table I shows an example of the information used by the MCD to correlate Meta CDN domain names to the proper CDN.
[0060]

Meta Domain

CDN-1 Domain

CDN-2 Domain

CDN-3 Domain

Customer1.meta.com

Customer1.cdn-1.com

Customer1.cdn-2.com

Customer1.cdn-3.com

Customer2.meta.com

Customer2.cdn-2.com

Not used

Customer2.cdn-3.com

With respect to FIG. 6, an example of the MCD operation is shown. Redirection, or load-balancing operates as follows: [0061]

1. The browser [0062] 606 sends a request 601 to its local DNS 607 for customer1.meta.com

2. The local DNS [0063] 607 goes through DNS and finds the Meta DNS server (MCD) 608 to be authoritative for this domain and sends a query 602 to the MCD 608. The MCD 608 looks at the request and returns an answer based on predefined capacity reservation and statically mapped preferences for certain clients 602. An example of this is if one of the CDNs is known to be better suited to server requests from a particular ISP, it will be mapped to do so. The answer comes from the Meta DNS in the form of a CNAME. The Meta DNS controls the TTL on the CNAME and thus controls how long a user is scheduled to a particular CDN. In this example, from Table I, the answer is customer1.cdn-1.com.

3. The local DNS [0064] 607 finds who is authoritative for customer1.cdn-1.com and sends a request 603 to the DNS server of CDN-1 609. The DNS for CDN-1 609 performs the load balancing for the servers within CDN-1 and returns an A record 603 to the local DNS 607.

4. The local DNS [0065] 607 returns this A record 604 to the client 606.

5. The client [0066] 606 makes a request 605 to the server within CDN-1 611.

Domain Names [0067]

The Domain Name that the customer uses is controlled by the Meta CDN. Issues such as failed page loads can result if sites use any of the underlying CDN domain names to reference CDN content. [0068]

Protocol Support [0069]

The Meta CDN supports any Protocol of the underlying CDNs. Any of the CDNs that do not support a particular protocol will not be scheduled to for those domain names. [0070]

How Content Gets In [0071]

Content never enters the Meta CDN but instead enters each of the underlying CDNs directly through the method used for a particular protocol. This is very simple for “pull” based protocols like HTTP and HTTPS, but requires a Meta CDN entry point for “push” content. [0072]

Problems Solved [0073]

This invention solves many of the problems that are encountered in an independent CDN situation. [0074]

The Meta CDN schedules to the CDN's scheduling devices, giving the CDN the final decision of which server within to utilize. By returning a CNAME, it is up to the client to find the device authoritative for the name. The Meta CDN can alternatively give out NS records dynamically, requiring that each CDN keep the Meta CDN in sync with all of the scheduling devices that they use. [0075]

The Meta CDN controls how long a user will be handed off to a CDN before the Meta CDN has the chance to change this decision. The name that the client is looking up is the name Meta CDN name. Any TTLs given out by each CDN on their records will not affect the Meta CDN's ability to redirect users. [0076]

On a per customer basis, the Meta CDN decides which CDNs a customer will be able to utilize. The Meta CDN maps Meta Hostnames to any amount of the CDNs. This can be done for different billing issues, as well as for feature support. [0077]

The Meta CDN can pre map customers to a specific CDN. The Meta CDN allows static mapping tables to be updated on a client IP basis. This allows the Meta CDN operator to determine which CDN they want the traffic for the source IP sent. [0078]

The amount of traffic to be scheduled to each CDN by the Meta CDN can be based on percentages. A simple user interface is available to the operator from the CDNs to indicate their availability to accept more traffic. The Meta CDN provides the ability to defines weight for each CDN. These weights act to control a weighted round robin scheduling algorithm in the Meta CDN. In addition, a simple interface is provided to allow each CDN to indicate to the Meta CDN their availability. Weights are also dynamically allocated to allow for adjustments. The Meta CDN has the ability to reserve capacity of CDNs to ensure traffic flow. [0079]

Since the Meta CDN redirects traffic to and from CDNs, it has the ability to get billing information directly from the redirected traffic. This enables the Meta CD N provider to accurately bill for the amount of traffic that is redirected for any customer. Each CDN generates billing information for each Meta CDN customer and provides it to the Meta CDN. The Meta CDN aggregates the billing information for each customer. The Meta CDN provides a simple user interface for the operator to retrieve and report billing information and administrate billing parameters. [0080]

Although the invention is described herein with reference to the preferred embodiment, one skilled in the art will readily appreciate that other applications may be substituted for those set forth herein without departing from the spirit and scope of the present invention. Accordingly, the invention should only be limited by the claims included below. [0081]

Claims (40)

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.