Unified web hosting and content distribution

Abstract

A domain name server request is received from a local domain name server. Operational performance parameters of a web host and a first content distribution network are received. Aggregate operational performance parameters of a second content distribution network are received. A first record is sent to the local domain name server that indicates the domain name server request is to be handled by the web host on a condition that a performance value is below a predetermined operational performance level threshold. A second record is sent to the local domain name server that indicates the domain name server request is to be handled by the first or the second content distribution network on a condition that the performance value is equal to or above the predetermined operational performance level threshold.

Claims

1. An apparatus comprising: circuitry configured to receive a domain name server request from a local domain name server; circuitry configured to receive operational performance parameters of a web host and a first content distribution network; circuitry configured to receive aggregate operational performance parameters of a second content distribution network; circuitry configured to send a first record to the local domain name server for the domain name server request that indicates the domain name server request is to be handled by the web host on a condition that a performance value, based on the received operational performance parameters of the web host and the first content distribution network and the received aggregate operational performance parameters of the second content distribution network, is below a predetermined operational performance level threshold, wherein the first record includes an Internet Protocol (IP) address of the web host; and circuitry configured to send a second record to the local domain name server for the domain name server request that indicates the domain name server request is to be handled by the first or the second content distribution network on a condition that the performance value is equal to or above the predetermined operational performance level threshold.

2. The apparatus of claim 1, wherein the apparatus is under operational control of a primary service provider.

3. The apparatus of claim 1, wherein the web host and at least one of the first content distribution network or the second content distribution network are under operational control of a primary service provider.

4. The apparatus of claim 1, wherein the operational performance level threshold is response time.

5. The apparatus of claim 1, wherein the operational performance level threshold is available bandwidth.

6. The apparatus of claim 1, wherein the operational performance parameters of the web host and first content distribution network are received from a monitoring apparatus that directly monitors the web host and first content distribution network.

7. The apparatus of claim 6, wherein the monitoring apparatus is under operation control of a primary service provider.

8. The apparatus of claim 1, wherein the aggregate operational performance parameters of the second content distribution network are received from a monitoring apparatus that is local to the second content distribution network and not under operational control of a primary service provider.

9. A method implemented by an apparatus, the method comprising: receiving a domain name server request from a local domain name server; receiving operational performance parameters of a web host and a first content distribution network; receiving aggregate operational performance parameters of a second content distribution network; sending a first record to the local domain name server for the domain name server request indicating that the domain name server request is to be handled by the web host on a condition that a performance value, based on the received operational performance parameters of the web host and the first content distribution network and the received aggregate operational performance parameters of the second content distribution network, is below a predetermined operational performance level threshold, wherein the first record includes an Internet Protocol (IP) address of the web host; and sending a second record to the local domain name server for the domain name server request indicating that the domain name server request is to be handled by the first or the second content distribution network on a condition that the performance value is equal to or above the predetermined operational performance level threshold.

10. The method of claim 9, wherein the apparatus is under operational control of a primary service provider.

11. The method of claim 9, wherein the web host and at least one of the first content distribution network or the second content distribution network are under operational control of a primary service provider.

12. The method of claim 9, wherein the operational performance level threshold is response time.

13. The method of claim 9, wherein the operational performance level threshold is available bandwidth.

14. The method of claim 9, wherein the operational performance parameters of the web host and first content distribution network are received from a monitoring apparatus that directly monitors the web host and first content distribution network.

15. The method of claim 14, wherein the monitoring apparatus is under operation control of a primary service provider.

16. The method of claim 9, wherein the aggregate operational performance parameters of the second content distribution network are received from a monitoring apparatus that is local to the second content distribution network and not under operational control of a primary service provider.

17. A computer-readable medium with stored instructions executable by a computing device, comprising: instructions to receive a domain name server request from a local domain name server; instructions to receive operational performance parameters of a web host and a first content distribution network; instructions to receive aggregate operational performance parameters of a second content distribution network; instructions to send a first record to the local domain name server for the domain name server request that indicates the domain name server request is to be handled by the web host on a condition that a performance value, based on the received operational performance parameters of the web host and the first content distribution network and the received aggregate operational performance parameters of the second content distribution network, is below a predetermined operational performance level threshold, wherein the first record includes an Internet Protocol (IP) address of the web host; and instructions to send a second record to the local domain name server for the domain name server request that indicates the domain name server request is to be handled by the first or the second content distribution network on a condition that the performance value is equal to or above the predetermined operational performance level threshold.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) The present invention will become more fully understood from the detailed description given hereinbelow and the accompanying drawings which are given by way of illustration only, and thus are not limitative of the present invention, and wherein:

(2) FIG. 1 illustrates a conventional Web Hosting with a server cluster;

(3) FIG. 2 illustrates a DNS based Content Distribution Network (CDN);

(4) FIG. 3 illustrates Content Internetworking (CDI) with DNS;

(5) FIG. 4 is a schematic overview of the architecture of the present invention;

(6) FIGS. 5.1-5.3 show the message exchanges during operation of the present invention under three different representative load conditions; and

(7) FIG. 6 shows a representative screen of a customer portal allowing direct customer visibility into and management of the operational performance and other aspects of the service of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

(8) FIG. 4 is a schematic diagram of the different components of the integrated web hosting and content delivery system 10 of the present invention, as deployed in a representative environment with a primary CDN (CDN A) and two partner CDNs (CDN B, and CDN C). Shown are a hosting center 11, several content distribution networks (CDN A, CDN B, and CDN C), a monitoring system 12, a redirection system 13, and a service management system 14. Note that the redirection system 13, the monitoring system 12, the service management system 14, and typically at least one CDN (CDN A is this case) are assumed to be under the same operational control as the primary service provider. The content distribution networks of the present invention may be any of a variety of content distribution networks, which provide audio streaming, video streaming, website access, or any other web-based service.

(9) With this arrangement, the monitoring system 12 of the primary service provider can directly monitor the capacity and health of servers in its own CDN A, as shown by the broken lines leading from the monitoring system 12 to CDN A. However, it is typically not possible for the primary service provider's monitoring system to fully monitor the partner CDNs (CDN B and CDN C). Instead, as shown, the monitoring system 12 will interact with a local monitoring system 12b, 12c of the partner CDN B, CDN C. CDN B and CDN C monitor the performance of their own servers and other systems internally, and then relay aggregate capacity and health statistics to the primary service provider monitoring system 12, as shown by the broken lines leading from monitoring system 12 to the monitoring system 12b of CDN B, and to the monitoring system 12c of CDN C. The monitoring system 12 in the primary service provider network uses the health and capacity measurements of its own CDN A and partner CDN B and CDN C to determine which customer requests should be served from the either the hosting center 11, or one or more of the CDN servers of the partner CDNs involved. The monitoring system 12 then updates the redirection system 13 which redirects the actual user requests to the appropriate server(s). The redirection system 13 can perform the client redirection using several well known methods, e.g.: DNS, or application level redirection. (Known Content Network (CN) Request-Routing Mechanisms; A. Barbir, B. Cain, R. Nair and O. Spatscheck, IETF Request for Comments: 3568, July 2003).

(10) Next, examples of the operation of the present invention will be discussed. In particular, FIGS. 5.1, 5.2 and 5.3 show the message exchanges involving an instantiation of the described invention under varying load conditions.

(11) In FIG. 5.1, the available capacity in the hosting center 11 is such that all client requests can be served from there. The interaction with a typical client is shown, including:

(12) 1: The customer's client machine C requests its local DNS server DNS.sub.1 to resolve a fully qualified domain name (FQDN) that is associated with the service, e.g.: customer1.onerateservice.com. (Note that this FQDN might be part of a URL that the user encounters while browsing the web.)

(13) 2: The local DNS server DNS.sub.1 determines that the authoritative DNS server for this domain is the DNS server(s) operated by the primary service provider. (Note that it can determine this in the normal way by querying the root DNS servers. This step is not shown.)

(14) 3: The redirection system can return an A-record containing the IP address of the server in the hosting center 11 which should be serving the request.

(15) 4: The local DNS server DNS.sub.1 returns the A record to the client machine C.

(16) 5/6: The client machine C directly interacts with the server in the hosting center 11 to retrieve the data.

(17) FIG. 5.2 shows the scenario where the load in the hosting center increase to the point where a customer-specific operational performance threshold is triggered in the monitoring system 12, causing some or all of the user requests to be directed to CDN A, in order that the requested content can be served in accordance with a predetermined service level (as set by a service level agreement (SLA) between the primary CDN and the customer enterprise). Note that as shown in FIG. 5.2, the content can be served from both the hosting center 11 and CDN A at the same time. Thus, some client machine requests will still be directed to the hosting center 11 as described before, while others will be directed to CDN A.

(18) 1: The client machine C requests its local DNS server DNS.sub.1 to resolve a full qualified domain name (FQDN) that is associated with the service, e.g.: customer1.onerateservice.com. (Note that this FQDN might be part of a URL that the user encounters while browsing the web.)

(19) 2: The local DNS server DNS.sub.1 determines that the authoritative DNS server (redirection system) for this domain is the DNS server(s) operated by the primary service provider. (Note that it can determine this in the normal way by querying the root DNS servers. This step is not shown.)

(20) 3: The redirection system 13 can return an A-record containing the IP address of the server, either in the hosting center 11 or in CDN A, which should be serving the request.

(21) 4: The local DNS server DNS.sub.1 returns the A record to the client machine C.

(22) 5/6: The client machine C directly interacts with the appropriate server, either in the hosting center 11 or CDN A to retrieve the data.

(23) FIG. 5.3 shows the situation when the load in the hosting center and CDN A is such that the monitoring system decides to also include CDN B in the service of the requested content. Further, the content can be served from each of the hosting center 11, CDN A, and CDN B simultaneously, with the monitoring system 12 determining the amount of requests going to each. In this case it is assumed that CDN B is a partner CDN so that the primary service provider redirection system or DNS cannot directly resolve the DNS request into an A-record. Instead, the local DNS server DNS.sub.1 is directed to a DNS server in the partner CDN B, which will resolve the request to an A-record. (Note that this procedure could also have been required for the previous case if CDN A, had its own DNS system or redirection system, e.g. to realize local load balancing.)

(24) Message exchanges shown in FIG. 5.3 include:

(25) The client machine C requests its local DNS server DNS.sub.1 to resolve a full qualified domain name (FQDN) that is associated with the service, e.g.: customer1.onerateservice.com. (Note that this FQDN might be part of a URL that the user encounters while browsing the web).

(26) 2: The local DNS server DNS.sub.1 determines that the authoritative DNS server for this domain is the DNS server(s) operated by the primary service provider. (Note that it can determine this in the normal way by querying the root DNS servers. This step is not shown.)

(27) 3: The redirection system 13 can return an NS-record or a CNAME-record which points the local DNS server DNS.sub.1 to a DNS server in the partner CDN B.

(28) 4: The local DNS server DNS.sub.1 requests a resolution from partner CDN B's DNS server.

(29) 5: Partner CDN B's DNS server can return an A-record containing the IP address of the server in CDN B which should be serving the request.

(30) 6: The local DNS server DNS.sub.1 returns the A-record to the client machine C.

(31) 7/8: The client machine C directly interacts with a server in the hosting center 11, in CDN A, or in CDN B, to retrieve the data.

(32) Internet access for the client machines C described above and shown in FIGS. 5.1 to 5.3 may be via a dial-up modem, DSL-modem or cable modem, in the case of typical residential users, or via a LAN with connectivity to the service provider through a router, in the case of typical business users. In all cases, a client machine would make use of a local DNS server to resolve host names to IP addresses to enable the client to access servers in the network.

(33) The integrated web hosting and content distribution system of the present invention includes a billing model that permits the hosting/CDN service to track usage both internally and externally (when using CDI). It also includes integrated provisioning, measurement, and management systems. The integrated provisioning system accepts input from/about the customer, and interfaces with the provisioning system of each of the hosting service and the CDN. Similarly an integrated billing/measurement system interfaces to the corresponding systems in both the primary service provider, the hosting service, and any partner CDNs. Offered load to the integrated system is tracked in real-time or near-time time, in order to drive content routing decisions. The functions are part of the service management system 14 shown in FIG. 4. On the other hand, they may be separate systems and functions.

(34) The monitoring system has a technical architecture that permits the system to select dynamically among the hosting service, and multiple CDNs. This is accomplished as shown in FIGS. 5.1-5.3. The DNS server to which the local DNS is referred has information about the load and availability of the web-hosting complex, the integrated CDN, and partner CDNs (as specified by CDI). It also has information about performance/load capacity thresholds that trigger a switch from one mode of operation to another. Such thresholds may be customer specific (in other words, DNS name specific).

(35) The architecture of the present invention extends the architecture of current service offerings, for example the AT&T CDN Brokering Service, by integrating a web-hosting complex into the brokering CDN's distribution options, and by unifying the billing of a web hosting service and one or more CDNs.

(36) Next a summary of some of the effects and advantages of the present invention are described.

(37) A primary benefit is simplified service from the point of view of the enterprise customer. For example, no longer does an enterprise have to decide whether to make use of its own hosting center, or whether their traffic volumes warrant the use of a CDN. The enterprise can simply sign up with a service provider offering the integrated web hosting and content distribution service of the present invention. Then, when their traffic volumes grow to the point where a CDN is needed, the services of the CDN are made available automatically in real-time, without the need for further actions by the enterprise. As a result, operational performance levels will be maintained at levels agreed to between the primary service provider and the enterprise.

(38) Another major simplification from the customer point of view is in terms of billing and interaction with the primary service provider. A single bill with a flat rate billing scheme will be provided to the customer. This flat rate may be a flat rate per transaction, or a flat rate for usage over a period of time, or a combination of these. In other words, there will be no premium charges for maintaining a certain operational performance level, which the enterprise might otherwise be subject to, without the present invention.

(39) In addition, the present invention will enable the primary service provider to provide a single point of contact (SPOC) to each customer for all the customer's web hosting, content distribution, and billing and reporting needs. As shown in FIG. 6, the present invention also offers a web portal or customer management interface 20 allowing customers direct access to functions such as response time, available bandwidth, billing, trouble status, and the like.

(40) Many variations of the service concept described above can be made and are to be considered within the scope of the present invention.

(41) For example, the content distribution networks of the present invention may be any of a variety of content distribution networks, which provide audio streaming, video streaming, website access, or any other web-based service, regardless of whether are under the control of the primary service provider or not.

(42) Further, many variations are possible regarding the mechanisms used to perform redirection. For example, the present invention is described as making use of a DNS-based system to perform the redirection task. However, many other redirection methods can be used to achieve the service unification, including application based redirection.

(43) Further, while the present invention assumes that the redirection system and monitoring system to be under the operational control of the primary service provider, having direct operational control of at least one CDN and the web hosting center are not absolute requirements. All CDNs may be provided by other (partner) service providers. Likewise, the web hosting center, may be customer operated, or operated by another organization, or any combination of these.

(44) In addition, many variations are possible regarding access to and control of the local domain name servers DNS.sub.1 (See FIGS. 5.1-5.3). For example, residential users may gain access to a local DNS.sub.1 controlled by their local cable service provider, or a local DNS.sub.1 operated by their local phone company via a dial-up, or broadband link. Business organizations may operate their own domain name server DNS.sub.1, or alternatively, the domain name server DNS.sub.1 may be provided by the primary service provider, or other internet service provider (ISP).

(45) Other service options are also available and should be considered to be within the scope of the present invention, including but not limited to, collocation services, managed web hosting services, load capacity testing services, customer performance monitoring and reporting, and customer management for requesting changes and reporting troubles. In addition, customer monitoring, reporting, and management may be provided via a web portal, a customer management device of any known type, or other means.

(46) The invention being thus described, it will be obvious that the same may be varied in many ways. Such variations are not to be regarded as a departure from the spirit and scope of the invention, and all such modifications as would be obvious to one skilled in the art are intended to be included within the scope of the following claims.