Global hosting system

• US 8,577,997 B2
• Filed: 09/15/2012
• Issued: 11/05/2013
• Est. Priority Date: 07/14/1998
• Status: Expired due to Fees

• Current Assignee: Massachusetts Institute of Technology
• Original Assignee: Massachusetts Institute of Technology
• Inventors: Thomson, Leighton F., Lewin, Daniel M.
• Primary Examiner(s): SHINGLES, KRISTIE D
• Application Number:
  US13/620,795
• Publication Number:
  US 20130013748A1
• Time in Patent Office: 416 Days
• Field of Search: 709/219, 709/217, 709/249
• US Class Current: 709/219
• CPC Class Codes: G06F 16/957 Browsing optimisation, e.g. caching or content distillation
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: H04L 61/2514 between local and global IP addresses
• 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/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/5007 Internet protocol [IP] addresses
• 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/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/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/1029 using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• 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/289 Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/567 : Integrating service provisioning from a plurality of service providers
• 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

Network architecture supports hosting and content distribution on a global scale. The architecture allows a Content Provider to replicate and serve its most popular content at an unlimited number of points throughout the world. The inventive framework comprises a set of servers operating in a distributed manner. The actual content to be served is preferably supported on a set of hosting servers (sometimes referred to as ghost servers). This content comprises HTML page objects that, conventionally, are served from a Content Provider site. A base HTML document portion of a Web page is served from the Content Provider'"'"'s site while one or more embedded objects for the page are served from the hosting servers, preferably, those hosting servers near the client machine. By serving the base HTML document from the Content Provider'"'"'s site, the Content Provider maintains control over the content.

Claims

1. Service provider system for delivering text, graphics, images, downloads, audio or video on behalf of multiple content providers, comprising:

a set of content servers distributed across multiple network locations, including at least one third party network location;

a set of name servers distributed across multiple network locations, each name server comprising software executing in a hardware element;

a first name server of the set of name servers that responds to a first domain name service (DNS) query to a hostname to issue a first response that includes a first set of one or more IP addresses, the first DNS query originating from a first local DNS name server and including at least a portion of an IP address of a machine associated with the first local DNS name server;

a second name server of the set of name servers that responds to a second DNS query to the hostname to issue a second response that differs from the first response and that includes a second set of one or more IP addresses, the second DNS query originating from a second local DNS name server and including at least a portion of an IP address of a machine associated with the second local DNS name server;

wherein the first name server is located in proximity to a first subset of content servers corresponding to the first set of one or more IP addresses, the second name server being located in proximity to a second subset of content servers corresponding to the second set of one or more IP addresses.

2. The service provider system as described in claim 1 wherein the first name server is closer to the first local DNS name server than is the second name server.

3. The service provider system as described in claim 2 wherein the first DNS query is associated with first content requested by a first end user, and the second DNS query is associated with second content requested by a second end user.

4. The service provider system as described in claim 3 wherein the first and second content are one of the following:

(a) identical content, (b) different content from a same content provider, and (c) different content from different content providers.

5. The service provider system as described in claim 1 wherein the first response includes an IP address associated with a content server that is nearby the first local DNS server, not overloaded, and that is likely to host a content object associated with the first DNS query.

6. The service provider system as described in claim 1 wherein the first and second name servers are located in a second level of a DNS hierarchy having at least first and second levels.

7. The service provider system as described in claim 6 wherein the first level of the DNS hierarchy includes at least one other name server that receives the first DNS query and, in response, returns an IP address of the first or second name server in the second level.

8. The service provider system as described in claim 1 wherein the hostname is associated with a data string.

9. The service provider system as described in claim 8 wherein the data string is associated with a URL for a content object.

10. Computer program code in non-transitory computer readable media for delivering text, graphics, images, downloads, audio or video on behalf of multiple content providers, comprising:

program code defining a set of content servers distributed across multiple network locations, including at least one third party network location;

program code defining a set of name servers distributed across multiple network locations;

wherein given program code of a first name server of the set of name servers responds to a first domain name service (DNS) query to a hostname to issue a first response that includes a first set of one or more IP addresses, the first DNS query originating from a first local DNS name server and including at least a portion of an IP address of a machine associated with the first local DNS name server; and

wherein given program code of a second name server of the set of name servers responds to a second DNS query to the hostname to issue a second response that differs from the first response and that includes a second set of one or more IP addresses, the second DNS query originating from a second local DNS name server and including at least a portion of an IP address of a machine associated with the second local DNS name server;

wherein the first name server is adapted to be located in proximity to a first subset of content servers corresponding to the first set of one or more IP addresses, and wherein the second name server is adapted to be located in proximity to a second subset of content servers corresponding to the second set of one or more IP addresses.