US20100042743A1 - Contents delivery system and method using page redirection, and gslb switch thereof - Google Patents

Contents delivery system and method using page redirection, and gslb switch thereof Download PDF

Info

Publication number
US20100042743A1
US20100042743A1 US12540127 US54012709A US20100042743A1 US 20100042743 A1 US20100042743 A1 US 20100042743A1 US 12540127 US12540127 US 12540127 US 54012709 A US54012709 A US 54012709A US 20100042743 A1 US20100042743 A1 US 20100042743A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
host server
server
page
information
ip address
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US12540127
Inventor
Jae Sic Jeon
Kyong Hwan KIM
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
SK Planet Co Ltd
Original Assignee
SK Telecom Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/15Directories; Name-to-address mapping
    • H04L61/1505Directories; Name-to-address mapping involving standard directories or standard directory access protocols
    • H04L61/1511Directories; Name-to-address mapping involving standard directories or standard directory access protocols using domain name system [DNS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents characterised by the data terminal contains provisionally no documents
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12047Directories; name-to-address mapping
    • H04L29/12056Directories; name-to-address mapping involving standard directories and standard directory access protocols
    • H04L29/12066Directories; name-to-address mapping involving standard directories and standard directory access protocols using Domain Name System [DNS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/10Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network
    • H04L67/1002Network-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
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/10Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network
    • H04L67/1002Network-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/1004Server selection in load balancing
    • H04L67/1008Server selection in load balancing based on parameters of servers, e.g. available memory or workload
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/10Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network
    • H04L67/1002Network-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/1004Server selection in load balancing
    • H04L67/1021Server selection in load balancing based on client or server locations
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/10Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network
    • H04L67/1002Network-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/1034Reaction to server failures by a load balancer

Abstract

A contents delivery system and method, and a GSLB switch thereof are provided. When a client requests a web server to provide a page and embedded objects, the web server embeds the URL representing the position in which the page and embedded objects are stored in an HTTP 302 redirection message and transmits the HTTP 302 redirection message including the URL to the client. A GSLB switch corresponding to the URL transmits the IP address of a specific host server selected from at least one host server storing the page and the embedded objects to the client. Accordingly, load of the web server decreases and flexibility in change of a CDN solution is secured.

Description

    BACKGROUND OF THE INVENTION
  • 1. Field of the Invention
  • The present invention relates to a contents delivery system and method, and more particularly, to a contents delivery system and method using page redirection for allowing a web server, which receives a request for a page and objects included in the page from a client, to redirect the request such that a host server of a contents delivery network (CDN) provider transmits the corresponding contents and a global server load balancing (GSLB) switch of the contents delivery system.
  • 2. Description of the Related Art
  • A web server of a contents provider (CP) generally provides a large number of contents (for example, videos, music, files, etc.) to clients. A large load is generated when the web server provides the whole or some of the contents to a plurality of clients one to one because the plurality of clients exist in a plurality of Internet service providers (ISPs) while the web server is connected to a single ISP.
  • Accordingly, traffic between ISPs exponentially increases as the number of contents providers and clients increase, and thus transmission delay and/or transmission failure rate due to traffic congestion increase. Web server fail-over may occur in the worst case.
  • To solve this problem, a contents delivery network (CDN) is introduced. The CDN is a service which previously stores contents converging on a web server of a contents provider located at a great distance from clients, for example, contents with large capacity, such as pictures, banners, videos or audio, or contents frequently requested by clients, in host servers globally deployed at points of presence (PoP) of a plurality of ISPs and redirects the path of the host server closest to a client when the client requests the contents provider to provide contents such that the client accesses the host server through the redirected path to be provided with the contents. Here, the host server may be referred to as a cache server, a replica server or a ghost server.
  • The CDN is classified into an overlay type and a network type according to system configuration. In the overlay type CDN, a server for a special purpose and a plurality of cache servers manage distribution of contents. The overlay type CDN has an advantage of simple administration because there is no need for a CDN provider to control network lower layer. In the network type CDN, network components such as a router and a switch include codes for confirming a specific application type and forwarding requests of clients according to a predetermined policy.
  • Recently, most of solutions of CDN providers have adopted mixture of the overlay and network types. An example of mixture of the two types is disclosed in U.S. Pat. No. 6,108,703 (Referred to as '703 patent hereinafter) entitled “Global hosting system”, issued to F. Thomson Lieghton et al., and assigned to MIT (Messachusetts Institute of Technology).
  • According to the '703 patent, a web server of a contents provider provides a page including a uniform resource locator (URL) (referred to as ‘modified URL’ hereinafter) of an embedded object, which is modified according to a special routine, in response to a request of a client. The web browser of the client loads the embedded object in order to display the page. The '703 patent identifies the modified URL through hierarchical DNS servers called a first level name server and a second level name server and returns the IP address of the optimum host server capable of providing the actual object to the client.
  • The '703 patent uses so-called DNS-based request routing. General DNS-based request routing has a problem that network latency according to DNS look-up time is aggravated. The '703 patent increases system complexity although it decreases network latency by constructing hierarchical DNS servers.
  • The above-described routine for generating the modified URL operates in the web server of the contents provider. An illustrative routine disclosed in the '703 patent is as follows.
  • 1. Embedded object URL before modified:
  • www.domainname,com/frontpage.jpg
  • 2. Embedded object URL after modified:
  • www.yy.zzz.net/aaaa/www.domainame.com/frontpage.jpg
  • Here, xxx field denotes a serial number, yy field denotes the second level name server, zzz field represents the first level name server and aaaa field represents other information (for example, fingerprint).
  • The modified URL includes a plurality of fields in addition to fields (yy and zzz) for achieving the DNS-based request routing in a complicated form. Furthermore, the routine for generating the modified URL must be executed and maintained by the web server of the contents provider.
  • However, when the contents provider replaces the solution of the CDN provider according to the '703 patent by the solution of another CDN provider, it is required to re-modify or change the modified URL applied to all pages according to the routine or recommendation of the solution of the other CDN provider. That is, flexibility in the change of the CDN solution is deteriorated.
  • Furthermore, URL modification according to the routine of the '703 patent increases the length of an HTML tag and the capacity of a page.
  • Accordingly, a method for solving the aforementioned problems is required.
  • SUMMARY OF THE INVENTION
  • The present invention provides a system and a method for allowing a web server which receives a request for a page and objects included in the page from a client to deliver corresponding contents without having a burden of modifying URLs of embedded objects to decrease system complexity and secure flexibility in changed of a CDN solution.
  • According to an aspect of the present invention, there is provided a contents delivery system using page redirection, which includes at least one host server receiving and storing a page and objects included in the page; a web server storing the page and the objects, transmitting the page and the objects to the at least one host server such that the at least one host server stores the page and the objects, embedding the URL representing the position in which the page and the objects are stored in an HTTP 302 redirection message and transmitting the HTTP 302 redirection message including the URL to a client when the client requests the web server to provide the page and the objects; and a GSLB switch corresponding to the URL and transmitting the IP address of a specific host server which will transmit the page and the objects, selected from the at least one host server, to the client through a local domain name system (DNS) server at the client when the local DNS server inquires of the GSLB switch about the IP address of the host server storing the page and the objects.
  • The GSLB switch may select the specific host server which will transmit the page and the objects with reference to a host network map including position information of the at least one host server and information on pages and objects stored in the at least one host server.
  • The position information of the least one host server may include the IP address of the at least one host server.
  • The GSLB switch may select the specific host server located in proximity to the client with reference to the IP address of the at least one host server and the IP address of the client.
  • The GSLB switch may select the specific host server in consideration of data traffic information of the at least one host server and fail-over information of the at least one host server.
  • According to another aspect of the present invention, there is provided a contents delivery method using page redirection, which includes a storing step in which at least one host server receives a page and objects included in the page from a web server and stores the page and the objects; a message transmitting step in which the web server embeds the URL representing the position in which the page and the objects stored in the host server are stored in an HTTP 302 redirection message and transmits the HTTP 302 redirection message including the URL to a client when the client requests the web server to provide the page and the objects; and an address transmitting step in which a GSLB switch corresponding to the URL transmits the IP address of a specific host server which will transmit the page and the objects, selected from the at least one host server, to the client through a local DNS server at the client when the local DNS server inquires of the GSLB switch about the IP address of the host server storing the page and the objects.
  • In the address transmitting step, the GSLB switch may transmit the IP address of the specific host server to the local DNS server in consideration of data traffic information of the at least one host server, fail-over information of the at least one host server, information on proximity of the client to the at least one host server and information on the page and the objects stored in the at least one host server.
  • In the address transmitting step, the GSLB switch may transmit the IP address of another GSLG switch to the local DNS server and the other GSLB switch may receive inquiry of the local DNS server about the IP address of the specific host server storing the page and the objects from the local DNS server and transmit the IP address of the specific host server to the client.
  • In the address transmitting step, the GSLB switch may transmit the IP address of the other GSLB switch among a plurality of GSLB switches to the local DNS server with reference to fail-over information of the plurality of GSLB switches.
  • According to another aspect of the present invention, there is provided a GSLB switch including a transmitting/receiving unit transmitting/receiving data; a host network map database storing a host network map including position information of at least on host server and information on a page and objects stored in the at least one host server; and a controller receiving the position information of the at least one host server and the information on the page and the objects stored in the at least one host server through the transmitting/receiving unit to update the host network map, selecting a specific host server which will transmit the page and the objects from the at least one host server with reference to the host network map and transmitting the IP address of the specific host server to a client through a local DNS server at the client via the transmitting/receiving unit when receiving inquiry of the local DNS server about the IP address of the host server storing the page and the objects from the local DNS server through the transmitting/receiving unit.
  • The position information of the at least one host server may include the IP address of the at least one host server.
  • The controller may select the specific host server located in proximity to the client with reference to the IP address of the at least one host server and the IP address of the client.
  • The GSLB switch may further include an information collecting module collecting at least one of data traffic information of the at least one host server and fail-over information of the at least one host server through the transmitting/receiving unit.
  • The information collecting module may further collect fail-over information of a plurality of GSLB switches.
  • The information collecting module may collect the information by transmitting/receiving messages to/from the at least one host server or the plurality of GSLB switches.
  • The information collecting module may collect the fail-over information when data traffic is relatively small in consideration of data traffic of the at least one host server or the plurality of GSLB switches.
  • The controller may transmit the IP address of the specific host server with reference to the information collected by the information collecting module when receiving the inquiry of the local DNS server about the IP address.
  • The controller may transmit the IP address of a GSLB switch other than the GSLB switch among the plurality of GSLB switches with reference to the information collected by the information collecting module when receiving the inquiry of the local DNS server about the IP address.
  • The information collecting module may store the collected information in the host network map.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The above and other features and advantages of the present invention will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings in which:
  • FIG. 1 is a configuration of a contents delivery system using page redirection according to an embodiment of the present invention;
  • FIG. 2 is a block diagram of a GSLB switch illustrated in FIG. 1;
  • FIG. 3 is host network map information stored in a host network map database illustrated in FIG. 2; and
  • FIG. 4 is a flowchart showing a contents delivery method according to an embodiment of the present invention.
  • DETAILED DESCRIPTION OF THE INVENTION
  • The present invention will now be described more fully with reference to the accompanying drawings, in which exemplary embodiments of the invention are shown. The invention may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the invention to those skilled in the art. Throughout the drawings, like reference numerals refer to like elements.
  • FIG. 1 illustrates a configuration of a contents delivery system using page redirection according to an embodiment of the present invention. Referring to FIG. 1, the contents delivery system includes a client 110, a local domain name system (DNS) server 120, a host server 130, a GSLB switch 140, a contents provider DNS server 150, a web server 160 and a network 170.
  • The client 110 corresponds to equipment such as a computer receiving information from the servers connected through the network 170. For example, the client 110 includes equipment which is currently commercially used or will be developed such as personal computers (PCs), household appliances, mobile communication devices, etc. in the current embodiment of the invention.
  • The client 110 includes a browser and a resolver. When a uniform resource locator (URL) that requests specific contents is input to the browser of the client 110, the resolver connected to the browser accesses the previously registered local DNS server 120 and resolves a domain name corresponding to the URL into the IP (Internet Protocol) address of the web server 160 providing the contents.
  • In the current embodiment of the invention, the client 110 request the web server 160 to provide a page and objects included in the page by using the IP address of the web server 160, received from the local DNS server 120. When the client 110 receives URL information on positions of the page and the objects included in the page from the web server 160 through a hypertext transfer protocol (HTTP) 302 redirection message, the client 110 inquires of the local DNS server 120 about the IP address of a server that stores the page and the objects included in the page by using the URL information. The HTTP 302 redirection message is one of response messages according to HTTP for redirecting a request of the client 110 to a URL at a different position.
  • When the client 110 receives the IP address of the host server 130 storing the page and the objects included in the page from the local DNS server 120, the client 110 accesses the host server 130 by using the IP address and receives the page and the objects included in the page.
  • The local DNS server 120 means a domain name server that transforms a domain name into an IP address and converts a symbolic name into a numeral address used by machines. The local DNS server 120 that receives the domain name of the web server 160 from the resolver accesses the contents provider DNS server 150, receives the IP address of the web server 160, which corresponds to the domain name and transmits the IP address to the client 110.
  • When the client 110 request the local DNS server 120 to provide the IP address of the server storing the page and the objects included in the page, the local DNS server 120 transmits/receives messages to/from the GSLB switch 140 to receive the IP address of the host server 130 storing the page and the objects included in the page and transmits the IP address to the client 110.
  • The host server 130 stores replicas of pages and embedded objects stored and administrated by the web server 160 and rapidly provides the replicas when the client 110 requests contents.
  • The GLSB switch 140 provides an intelligent DNS function, identifies and administrates at least one globally deployed host server 130. For example, the GSLB switch 140 according to the current embodiment of the invention has position information of the at least one host server 130 and information on pages and embedded objects stored in the at least one host server 130. Here, the position information of the at least one host server 130 may include the IP address of the at least one host server 130 and the GSLB switch 140 may determine proximity of the client 110 to the at least one host server 130 by using the IP address of the at least one host server 130.
  • The GSLB switch 140 may select a specific host server 130 which will transmit the page and the objects included in the page, requested by the client 110, to the client 110 on the basis of the proximity of the client 110 to the at least one host server 130 and the information on the pages and objects stored the at least one host server 130 and transmit the IP address of the selected host server 130 to the client 110 through the local DNS server 120.
  • Furthermore, the GSLB switch 140 may select the specific host server 130 which will respond to the request of the client 110 in consideration of data traffic information and fail-over information of the at least one host server 130 and transmit the IP address of the selected host server 130 to the client 110.
  • Here, the information on the proximity of the client 110 to the host server 130, information on the pages and objects stored in the host server 130, and the data traffic information and fail-over information of the host server 130 may be collected at predetermined time such as a predetermined period in consideration of data traffic and load of the GSLB switch 140 or the host server 130 when the pages and objects stored in the host server 130 are updated.
  • In the current embodiment of the invention, the GSLB switch 140 may collect fail-over information of a plurality of other GSLB switches. For instance, when there is a GSLB switch more suitable to respond to the inquiry of the local DNS server 120 about the IP address of the host server 130 than the GSLB switch 140, the inquiry is re-routed to the more suitable GSLB switch such that the GLSB switch can respond to the inquiry of the local DNS server 120. Here, the routing can be achieved with reference to fail-over information of the GLSB switch 140, other GSLB switches or the host server 130. The fail-over information of the other GSLB switches may be collected at predetermined time such as a predetermined period in consideration of data traffic and load of the GSLB switch 140 and other GSLB switches or the host server 130.
  • The web server 160 provides pages and embedded objects included in the pages provided by a contents provider. In the current embodiment of the invention, the contents provider transmits the pages and embedded objects included in the pages from the web server 160 to the host server 130 and stores the pages and embedded objects in the host server 130. Accordingly, when the client 110 requests the web server 160 to provide a specific page and embedded objects included in the specific page, the client 110 can rapidly receive a response through the host server 130.
  • Furthermore, when the client 110 requests the web server 160 to provide the page and the embedded objects, the web server 160 embeds a URL which represents the position at which a CDN provider stores the page and the embedded objects in an HTTP 302 redirection message and transmits the HTTP 302 redirection message to the client 110. Then, the client 110 receives the URL, requests the local DNS server 120 to provide the IP address of the host server 130 which will transmits the page and the embedded objects by using the URL, accesses the host server 130 through the IP address and receives the contents, that is, the page and the embedded objects.
  • The contents provider DNS server 150 is a DNS server of the contents provider. When the local DNS server 120 inquires of the contents provider DNS server 150 about the IP address of the web server 160 storing the page and the embedded objects, the contents provider DNS server 150 returns the IP address to the local DNS server 120 such that the IP address is delivered to the client 110.
  • The network 170 corresponds to a data communication network for data transmission and information exchange among the client 110, the local DNS server 120, the host server 130, the GSLB switch 140, the contents provider DNS server 150 and the web server 160. The network 170 according to the present invention includes Internet, Intranet, Extranet, and other wired and wireless networks and a combination thereof, which are well-known or will be developed.
  • The configuration and operation of the GLSB switch 140 according to an embodiment of the present invention will now be explained in more detail with reference to FIG. 2.
  • FIG. 2 is a block diagram of the GLSB switch 140 illustrated in FIG. 1. Referring to FIGS. 1 and 2, the GSLB switch 140 includes a transmitting/receiving unit 210, a controller 220, a host network map database 230 and an information collecting module 240.
  • The transmitting/receiving unit 210 includes an interface for transmitting/receiving data and messages through the network 170.
  • The host network map database 230 stores a host network map including the position information of the at least one host server 130 and the information on the pages and embedded objects stored in the at least one host server 130.
  • The information collecting module 240 collects at least one of the fail-over information of the plurality of other GSLB switches, fail-over information of the host server 130 and data traffic information of the host server 130 through the transmitting/receiving unit 210. For instance, the information collecting module 240 may collect the information at specific periods. Furthermore, the information collecting module 240 may collect the information when data traffic is relatively small in consideration of the data traffic of the other GLSB switches or the host server 130. The information collected by the information collecting module 240 is stored in the host network map such that the controller 230 can refer to the information.
  • The controller 220 receives the position information of the at least one host server 130 and the information on the pages and embedded objects stored in the at least one host server 130 through the transmitting/receiving unit 210 and updates the host network map. Furthermore, when the controller 220 receives inquiry of the local DNS server 120 about the IP address of the specific host server 130 storing the page and embedded objects requested by the client 110, the controller 220 selects the specific host server 130 from the at least one host server 130 with reference to the host network map stored in the host network map database 230 and transmits the IP address of the selected host server 130 to the client 110 through the transmitting/receiving unit 210 via the local DNS server 120.
  • In addition, the controller 220 may select the specific host server 130 which will transmit the page and embedded objects to the client 110 with reference to information collected by the information collecting module 240. The information may be collected in real time. Otherwise, the information may be collected by the information collecting module 240 and stored in the host network map or updated and stored in the host network map.
  • The controller 220 may route the inquiry of the local DNS server 120 about the IP address of the host server 130 to a GSLB switch more suitable for the response to the inquiry with reference to the fail-over information of the other GSLB switches, collected by the information collecting module 240. That is, if the GSLB switch 140 fails or data traffic of the GSLB switch 140 exceeds a critical value, the controller 220 allows another GSLB switch having no fail-over to respond to the request of the client 110.
  • The information of the host network map stored in the host network map database 230 will now be described in more detail with reference to FIG. 2.
  • FIG. 3 illustrates information of the host network map 300 stored in the host network map database 230 illustrated in FIG. 2. The host network map 300 is map information referred to by the GSLB switch 140 when the GLSB switch 140 selects the host server 130 which provides the page and embedded objects requested by the client 110.
  • Referring to FIG. 3, the host network map 300 includes host server information 310, stored page and object information 320, IP address 330, data traffic information 340 and fail-over information 550 in column.
  • The host server information 310 corresponds to an identification information field for identifying the host server 130. Although the host server information 310 is represented by numerals in the current embodiment of the invention, it is not limited thereto and any identifier capable of identifying the host server 130 can be included in the technical scope of the present invention.
  • The stored page and object information 320 corresponds to a field representing information on pages and objects received from the web server 160 and stored in each host server 130.
  • The IP address 330 corresponds to a field representing the IP address of each host server 130. The IP address field 330 may include a plurality of IP addresses of a single host server 130.
  • The data traffic information 340 corresponds to a field representing data traffic of each host server 130. Although large data traffic is represented as ‘Red’, slightly large data traffic is represented as ‘Yellow’ and small data traffic is represented as ‘Green’ in the current embodiment of the invention, the technical scope of the present invention is not limited thereto.
  • The fail-over information 350 corresponds to a field representing whether each host server 130 fails over. Specifically, ‘A (Available)’ represents that the host server 130 normally operates and ‘N/A (Non-available)’ represents that the host server 130 fails over.
  • Referring to the host network map 300, the stored page and object information 320 corresponding to host server ‘1’ in the host server information 310 corresponds to ‘AAA’ and ‘BBB’, and thus it can be known that host server ‘1’ stores pages or objects ‘AAA’ and ‘BBB’. Furthermore, the IP address of host server ‘1’ is ‘X.X.X’ and data traffic of host server ‘1’ is ‘Red’, and thus host server ‘1’ has large data traffic. In addition, the fail-over information 350 corresponding to host server ‘1’ is represented as ‘A’, and thus host server ‘1’ does not fail over. Host servers ‘2’, ‘3’, ‘4’ and ‘5’ can be understood in the same manner so that detailed explanations thereof are omitted.
  • If the client 110 requests the GSLB switch 140 to provide the IP address of the host server 130 which will transmit contents ‘AAA’ through the local DNS server 120, the controller 220 of the GSLB switch 140 recognizes that host servers ‘1’, ‘2’, ‘4’ and ‘5’ store contents ‘AAA’ from the host network map 300 stored in the host network map database 230.
  • Here, host server ‘1’ has large data traffic because the data traffic information 340 thereof is represented as ‘Red’ and host server ‘2’ has fail-over because the fail-over information 350 thereof is represented as ‘N/A’, and thus host servers ‘1’ and ‘2’ are not suitable to transmit contents ‘AAA’. Host servers ‘4’ and ‘5’ have small data traffic because data traffic information 340 thereof is represented as ‘Green’ and do not have fail-over because the fail-over information 350 thereof is represented as ‘A’. Accordingly, the controller 220 of the GSLB switch 140 selects one of host servers ‘4’ and ‘5’ as a host server suitable to transmit contents ‘AAA’.
  • Here, the controller 220 of the GSLB switch 140 may allow one of host servers ‘4’ and ‘5’, which is closer to the client 110 than the other, to transmit the corresponding contents in consideration of proximity of the client 110 to the host servers. For instance, the controller 220 may compare the IP addresses of host servers ‘4’ and ‘5’ to the IP address of the client 110 and select a host server closer to the client 110 than the other.
  • A contents delivery method according to an embodiment of the present invention will now be explained with reference to FIG. 4 in detail.
  • FIG. 4 is a flowchart showing a contents delivery method using page redirection according to an embodiment of the present invention. Referring to FIG. 4, the host server 130 receives a page and objects included in the page of a contents provider from the web server 160 and stores the page and the objects in step S400. Here, contents, that is, the page and the objects included in the page, can be transmitted when the host server 130 requests the web server 160 to provide the contents, at specific periods, and when the page and objects included in the page stored in the web server 160 are updated.
  • When a URL for requesting the web server 160 to provide the page and the objects included in the page is input to the browser of the client 110, the resolver of the client 110 inquires of the local DNS server 120 about the IP address of the web server 160 storing the page and the objects included in the page in step S405.
  • The local DNS server 120 receives the inquiry of the client 110 about the IP address of the web server 160 in step S405 and inquires of the contents provider DNS server 150 corresponding to the DNS server of the contents provider about the IP address of the web server 160 storing the page and the objects in step S410.
  • The contents provider DNS server 150 receives the inquiry of the local DNS server 120 in step S410 and transmits the IP address of the web server 160 to the local DNS server 120 in step S415. The local DNS server 120 receives the IP address of the web server 160 and transmits the received IP address to the client 110 in step S420.
  • The client 110 receives the IP address of the web server 160 in step S420 and requests the web server 160 to provide the page and the objects by using the IP address of the web server 160 in step S425. The web server 160 receiving the request of the client 110 in step S425 embeds the URL representing the position in which the page and the objects of CDN provider are stored in an HTTP 302 redirection message and transmits the HTTP 302 redirection message to the client 110 in step S430.
  • The client 110 receives the HTTP 302 redirection message including the URL representing the position in which the page and the objects are stored in step S430 and inquires of the local DNS server 120 about the IP address of the host server 130 storing the page and the objects by using the URL in step S435. The local DNS server 120 receives the inquiry of the client 110 in step S435 and inquires of the GSLB switch 140 corresponding to the URL about the IP address of the host server 130 which will transmit the page and the objects included in the page in step S440.
  • The GSLB switch 140 receives the inquiry of the local DNS server 120 in step S440 and selects the specific host server 130 which will transmit the page and the objects to the client 110 from at least one host server in step S445. Here, the GSLB switch 140 can select the host server 130 on the basis of at least one of data traffic information of the at least one host server, fail-over information of the at least one host server, information on proximity of the client 110 to the at least one host server and information on pages and objects stored in the at least one host server.
  • The GSLB switch 140 transmits the IP address of the host server 130 storing the page and the objects included in the page to the local DNS server 120 in step S450. The local DNS server 120 transmits the IP address of the host server 130 to the client 110 in step S455.
  • The client 110 receives the IP address of the host server 130 in step S455 and requests the host server 130 to provide the page and the objects included in the page in step S460, receives the page transmitted from the host server 130 in step S465, and parses the page in step S470.
  • When the client 110 detects the objects included in the page while parsing the page in step S470, the client 110 requests the host server 130 to transmit the objects included in the page by using the IP address of the host server 130, transmitted to the client 110 in step S455, in step S475 and receives the objects transmitted from the host server 130 in step S480.
  • According to the present invention, the GSLB switch can select a specific host server to provide a page and objects included in the page to the client. Accordingly, load of the web server is reduced and there is no need to modify URLs of embedded objects when a CDN solution is changed. Furthermore, the client can receive the page and the objects included in the page more rapidly.
  • While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present invention as defined by the following claims.

Claims (21)

  1. 1. A contents delivery system using page redirection comprising:
    at least one host server receiving and storing a page and objects included in the page;
    a web server storing the page and the objects, transmitting the page and the objects to the at least one host server such that the at least one host server stores the page and the objects, embedding the URL representing the position in which the page and the objects are stored in an HTTP 302 redirection message and transmitting the HTTP 302 redirection message including the URL to a client when the client requests the web server to provide the page and the objects; and
    a GSLB switch corresponding to the URL and transmitting the IP address of a specific host server which will transmit the page and the objects, selected from the at least one host server, to the client through a local DNS server at the client when the local DNS server inquires of the GSLB switch about the IP address of the host server storing the page and the objects.
  2. 2. The contents delivery system of claim 1, wherein the GSLB switch selects the specific host server which will transmit the page and the objects with reference to a host network map including position information of the at least one host server and information on pages and objects stored in the at least one host server.
  3. 3. The contents delivery system of claim 2, wherein the position information of the least one host server includes the IP address of the at least one host server.
  4. 4. The contents delivery system of claim 3, wherein the GSLB switch selects the specific host server located in proximity to the client with reference to the IP address of the at least one host server and the IP address of the client.
  5. 5. The contents delivery system of claim 2, wherein the GSLB switch selects the specific host server in consideration of data traffic information of the at least one host server and fail-over information of the at least one host server.
  6. 6. A contents delivery method using page redirection, comprising:
    a storing step in which at least one host server receives a page and objects included in the page from a web server and stores the page and the objects;
    a message transmitting step in which the web server embeds the URL representing the position in which the page and the objects stored in the host server are stored in an HTTP 302 redirection message and transmits the HTTP 302 redirection message including the URL to a client when the client requests the web server to provide the page and the objects; and
    an address transmitting step in which a GSLB switch corresponding to the URL transmits the IP address of a specific host server which will transmit the page and the objects, selected from the at least one host server, to the client through a local DNS server at the client when the local DNS server inquires of the GSLB switch about the IP address of the host server storing the page and the objects.
  7. 7. The contents delivery method of claim 6, wherein the GSLB switch transmits the IP address of the specific host server to the local DNS server in consideration of data traffic information of the at least one host server, fail-over information of the at least one host server, information on proximity of the client to the at least one host server and information on pages and objects stored in the at least one host server in the address transmitting step.
  8. 8. The contents delivery method of claim 6, wherein the GSLB switch transmits the IP address of another GSLG switch to the local DNS server and the other GSLB switch receives inquiry of the local DNS server about the IP address of the specific host server storing the page and the objects from the local DNS server and transmits the IP address of the specific host server to the client in the address transmitting step.
  9. 9. The contents delivery method of claim 8, wherein the GSLB switch transmits the IP address of the other GSLB switch among a plurality of GSLB switches to the local DNS server with reference to fail-over information of the plurality of GSLB switches in the address transmitting step.
  10. 10. A GSLB switch comprising:
    a transmitting/receiving unit transmitting/receiving data;
    a host network map database storing a host network map including position information of at least on host server and information on a page and objects stored in the at least one host server; and
    a controller receiving the position information of the at least one host server and the information on the page and the objects stored in the at least one host server through the transmitting/receiving unit to update the host network map, selecting a specific host server which will transmit the page and the objects from the at least one host server with reference to the host network map and transmitting the IP address of the specific host server to a client through a local DNS server at the client via the transmitting/receiving unit when receiving inquiry of the local DNS server about the IP address of the host server storing the page and the objects from the local DNS server through the transmitting/receiving unit.
  11. 11. The GSLB switch of claim 10, wherein the position information of the at least one host server includes the IP address of the at least one host server.
  12. 12. The GSLB switch of claim 11, wherein the controller selects the specific host server located in proximity to the client with reference to the IP address of the at least one host server and the IP address of the client.
  13. 13. The GSLB switch of claim 10, further comprising an information collecting module collecting at least one of data traffic information of the at least one host server and fail-over information of the at least one host server through the transmitting/receiving unit.
  14. 14. The GSLB switch of claim 13, wherein the information collecting module further collects fail-over information of a plurality of GSLB switches.
  15. 15. The GSLB switch of claim 13, wherein the information collecting module collects the information by transmitting/receiving messages to/from the at least one host server or the plurality of GSLB switches.
  16. 16. The GSLB switch of claim 13, wherein the information collecting module collects the fail-over information when data traffic is relatively small in consideration of data traffic of the at least one host server or the plurality of GSLB switches.
  17. 17. The GSLB switch of claim 13, wherein the controller transmits the IP address of the specific host server with reference to the information collected by the information collecting module when receiving the inquiry of the local DNS server about the IP address.
  18. 18. The GSLB switch of claim 14, wherein the controller transmits the IP address of a GSLB switch other than the GSLB switch among the plurality of GSLB switches with reference to the information collected by the information collecting module when receiving the inquiry of the local DNS server about the IP address.
  19. 19. The GSLB switch of claim 13, wherein the information collecting module stores the collected information in the host network map.
  20. 20. The GSLB switch of claim 14, wherein the information collecting module collects the information by transmitting/receiving messages to/from the at least one host server or the plurality of GSLB switches.
  21. 21. The GSLB switch of claim 14, wherein the information collecting module collects the fail-over information when data traffic is relatively small in consideration of data traffic of the at least one host server or the plurality of GSLB switches.
US12540127 2008-08-13 2009-08-12 Contents delivery system and method using page redirection, and gslb switch thereof Abandoned US20100042743A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US8854108 true 2008-08-13 2008-08-13
US12540127 US20100042743A1 (en) 2008-08-13 2009-08-12 Contents delivery system and method using page redirection, and gslb switch thereof

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US12540127 US20100042743A1 (en) 2008-08-13 2009-08-12 Contents delivery system and method using page redirection, and gslb switch thereof

Publications (1)

Publication Number Publication Date
US20100042743A1 true true US20100042743A1 (en) 2010-02-18

Family

ID=41682024

Family Applications (4)

Application Number Title Priority Date Filing Date
US12540234 Active 2030-04-18 US8527635B2 (en) 2008-08-13 2009-08-12 Contents delivery system and method, web server and contents provider DNS server thereof
US12540212 Active 2030-04-13 US8316085B2 (en) 2008-08-13 2009-08-12 Contents delivery system and method using object redirection, and GSLB switch thereof
US12540127 Abandoned US20100042743A1 (en) 2008-08-13 2009-08-12 Contents delivery system and method using page redirection, and gslb switch thereof
US12540270 Abandoned US20100042725A1 (en) 2008-08-13 2009-08-12 Contents provider participation type contents delivery system and method, and contents delivery network domain name system server thereof

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US12540234 Active 2030-04-18 US8527635B2 (en) 2008-08-13 2009-08-12 Contents delivery system and method, web server and contents provider DNS server thereof
US12540212 Active 2030-04-13 US8316085B2 (en) 2008-08-13 2009-08-12 Contents delivery system and method using object redirection, and GSLB switch thereof

Family Applications After (1)

Application Number Title Priority Date Filing Date
US12540270 Abandoned US20100042725A1 (en) 2008-08-13 2009-08-12 Contents provider participation type contents delivery system and method, and contents delivery network domain name system server thereof

Country Status (1)

Country Link
US (4) US8527635B2 (en)

Cited By (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102014173A (en) * 2010-11-01 2011-04-13 蓝汛网络科技(北京)有限公司 Domain name redirecting control method, module and system
US8392576B1 (en) 2011-09-26 2013-03-05 Google Inc. Browser based redirection of broken links
US20130103785A1 (en) * 2009-06-25 2013-04-25 3Crowd Technologies, Inc. Redirecting content requests
US8504692B1 (en) * 2011-09-26 2013-08-06 Google Inc. Browser based redirection of broken links
US20130232260A1 (en) * 2009-12-23 2013-09-05 Citrix Systems, Inc. Systems and methods for gslb mep connection management across multiple core appliances
US20140108672A1 (en) * 2011-12-02 2014-04-17 Huawei Technologies Co., Ltd. Content Delivery Network Routing Method, System and User Terminal
US8879431B2 (en) 2011-05-16 2014-11-04 F5 Networks, Inc. Method for load balancing of requests' processing of diameter servers
US9083652B2 (en) 2009-06-25 2015-07-14 Fortinet, Inc. Crowd based content delivery
US9143451B2 (en) 2007-10-01 2015-09-22 F5 Networks, Inc. Application layer network traffic prioritization
US20150341414A1 (en) * 2014-05-20 2015-11-26 Alibaba Group Holding Limited Method and system for acquiring web pages
US9244843B1 (en) 2012-02-20 2016-01-26 F5 Networks, Inc. Methods for improving flow cache bandwidth utilization and devices thereof
US9307044B2 (en) 2012-03-28 2016-04-05 At&T Intellectual Property I, L.P. System and method for routing content based on real-time feedback
US9331979B2 (en) 2011-07-29 2016-05-03 Fortinet, Inc. Facilitating content accessibility via different communication formats
US9420049B1 (en) 2010-06-30 2016-08-16 F5 Networks, Inc. Client side human user indicator
US9497614B1 (en) 2013-02-28 2016-11-15 F5 Networks, Inc. National traffic steering device for a better control of a specific wireless/LTE network
US9503375B1 (en) 2010-06-30 2016-11-22 F5 Networks, Inc. Methods for managing traffic in a multi-service environment and devices thereof
US9578090B1 (en) 2012-11-07 2017-02-21 F5 Networks, Inc. Methods for provisioning application delivery service and devices thereof
US9699138B2 (en) 2011-07-29 2017-07-04 Fortinet, Inc. Directing clients based on communication format
US20170279888A1 (en) * 2016-03-22 2017-09-28 Go Daddy Operating Company, LLC Hosting provider hosting routes from a media repository
US9832200B2 (en) 2015-12-14 2017-11-28 Bank Of America Corporation Multi-tiered protection platform
US9832229B2 (en) 2015-12-14 2017-11-28 Bank Of America Corporation Multi-tiered protection platform
US9898477B1 (en) 2014-12-05 2018-02-20 EMC IP Holding Company LLC Writing to a site cache in a distributed file system
US9992163B2 (en) 2015-12-14 2018-06-05 Bank Of America Corporation Multi-tiered protection platform
US10021212B1 (en) 2015-03-27 2018-07-10 EMC IP Holding Company LLC Distributed file systems on content delivery networks

Families Citing this family (68)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8533293B1 (en) 2008-03-31 2013-09-10 Amazon Technologies, Inc. Client side cache management
US8321568B2 (en) 2008-03-31 2012-11-27 Amazon Technologies, Inc. Content management
US7970820B1 (en) 2008-03-31 2011-06-28 Amazon Technologies, Inc. Locality based content distribution
US8601090B1 (en) 2008-03-31 2013-12-03 Amazon Technologies, Inc. Network resource identification
US8606996B2 (en) 2008-03-31 2013-12-10 Amazon Technologies, Inc. Cache optimization
US8447831B1 (en) 2008-03-31 2013-05-21 Amazon Technologies, Inc. Incentive driven content delivery
US7962597B2 (en) 2008-03-31 2011-06-14 Amazon Technologies, Inc. Request routing based on class
US8156243B2 (en) 2008-03-31 2012-04-10 Amazon Technologies, Inc. Request routing
US8837491B2 (en) 2008-05-27 2014-09-16 Glue Networks Regional virtual VPN
US7925782B2 (en) 2008-06-30 2011-04-12 Amazon Technologies, Inc. Request routing using network computing components
US9912740B2 (en) 2008-06-30 2018-03-06 Amazon Technologies, Inc. Latency measurement in resource requests
US8028090B2 (en) 2008-11-17 2011-09-27 Amazon Technologies, Inc. Request routing utilizing client location information
US8065417B1 (en) 2008-11-17 2011-11-22 Amazon Technologies, Inc. Service provider registration by a content broker
US8521880B1 (en) 2008-11-17 2013-08-27 Amazon Technologies, Inc. Managing content delivery network service providers
US8122098B1 (en) 2008-11-17 2012-02-21 Amazon Technologies, Inc. Managing content delivery network service providers by a content broker
US8073940B1 (en) 2008-11-17 2011-12-06 Amazon Technologies, Inc. Managing content delivery network service providers
US8732309B1 (en) 2008-11-17 2014-05-20 Amazon Technologies, Inc. Request routing utilizing cost information
US8060616B1 (en) 2008-11-17 2011-11-15 Amazon Technologies, Inc. Managing CDN registration by a storage provider
US8756341B1 (en) 2009-03-27 2014-06-17 Amazon Technologies, Inc. Request routing utilizing popularity information
US8412823B1 (en) 2009-03-27 2013-04-02 Amazon Technologies, Inc. Managing tracking information entries in resource cache components
US8397073B1 (en) 2009-09-04 2013-03-12 Amazon Technologies, Inc. Managing secure content in a content delivery network
US8433771B1 (en) 2009-10-02 2013-04-30 Amazon Technologies, Inc. Distribution network with forward resource propagation
US20110179174A1 (en) * 2010-01-19 2011-07-21 Nokia Corporation Apparatus identification in coexistence networking
US9495338B1 (en) 2010-01-28 2016-11-15 Amazon Technologies, Inc. Content distribution network
US9407681B1 (en) 2010-09-28 2016-08-02 Amazon Technologies, Inc. Latency measurement in resource requests
US8468247B1 (en) 2010-09-28 2013-06-18 Amazon Technologies, Inc. Point of presence management in request routing
US9787775B1 (en) 2010-09-28 2017-10-10 Amazon Technologies, Inc. Point of presence management in request routing
US8819283B2 (en) * 2010-09-28 2014-08-26 Amazon Technologies, Inc. Request routing in a networked environment
US8577992B1 (en) 2010-09-28 2013-11-05 Amazon Technologies, Inc. Request routing management based on network components
US9712484B1 (en) 2010-09-28 2017-07-18 Amazon Technologies, Inc. Managing request routing information utilizing client identifiers
US8930513B1 (en) 2010-09-28 2015-01-06 Amazon Technologies, Inc. Latency measurement in resource requests
CN103229167A (en) 2010-10-06 2013-07-31 星汇数据解决方案公司 System and method for indexing electronic discovery data
US8452874B2 (en) 2010-11-22 2013-05-28 Amazon Technologies, Inc. Request routing processing
US9391949B1 (en) * 2010-12-03 2016-07-12 Amazon Technologies, Inc. Request routing processing
CN102098351A (en) * 2010-12-13 2011-06-15 山东科技大学 Method for analyzing color numerical value domain name
CN102611763A (en) * 2011-01-25 2012-07-25 中国移动通信集团公司 DNS (Domain Name Server) inquiring method and equipment
US20120311076A1 (en) * 2011-05-31 2012-12-06 Cisco Technology, Inc. System and method to support different uniform resource locator formats for content on different network elements
US20130097277A1 (en) * 2011-10-12 2013-04-18 Electronics And Telecommunications Research Institute Method and apparatus for load balancing of content-centric network
US9210195B2 (en) 2011-10-20 2015-12-08 Huawei Technologies Co., Ltd. Method, apparatus, and system for processing service data
CN102387201B (en) * 2011-10-20 2015-08-19 华为技术有限公司 The method of processing traffic data, the apparatus and system
US9313100B1 (en) 2011-11-14 2016-04-12 Amazon Technologies, Inc. Remote browsing session management
US9330188B1 (en) 2011-12-22 2016-05-03 Amazon Technologies, Inc. Shared browsing sessions
US8839087B1 (en) 2012-01-26 2014-09-16 Amazon Technologies, Inc. Remote browsing and searching
US9336321B1 (en) 2012-01-26 2016-05-10 Amazon Technologies, Inc. Remote browsing and searching
US8904009B1 (en) 2012-02-10 2014-12-02 Amazon Technologies, Inc. Dynamic content delivery
US8291117B1 (en) * 2012-02-15 2012-10-16 Limelight Networks, Inc. Scaled domain name service
US9722851B1 (en) * 2012-03-27 2017-08-01 Amazon Technologies, Inc. Optimized retrieval of network resources
US9154551B1 (en) 2012-06-11 2015-10-06 Amazon Technologies, Inc. Processing DNS queries to identify pre-processing information
US9525659B1 (en) 2012-09-04 2016-12-20 Amazon Technologies, Inc. Request routing utilizing point of presence load information
US9323577B2 (en) 2012-09-20 2016-04-26 Amazon Technologies, Inc. Automated profiling of resource usage
US9760528B1 (en) 2013-03-14 2017-09-12 Glue Networks, Inc. Methods and systems for creating a network
US9928082B1 (en) 2013-03-19 2018-03-27 Gluware, Inc. Methods and systems for remote device configuration
US9294391B1 (en) 2013-06-04 2016-03-22 Amazon Technologies, Inc. Managing network computing components utilizing request routing
US9578137B1 (en) 2013-06-13 2017-02-21 Amazon Technologies, Inc. System for enhancing script execution performance
CN104427005B (en) * 2013-08-20 2018-01-02 阿里巴巴集团控股有限公司 Cdn method is implemented in the system and scheduling request precise
US20150278463A1 (en) 2014-04-01 2015-10-01 Merge Healthcare Incorporated Systems and methods for pre-authorizing image studies
CN105763585A (en) * 2014-12-17 2016-07-13 中兴通讯股份有限公司 Method of implementing data pushing function and GSLB
US9785412B1 (en) 2015-02-27 2017-10-10 Glue Networks, Inc. Methods and systems for object-oriented modeling of networks
US9887931B1 (en) 2015-03-30 2018-02-06 Amazon Technologies, Inc. Traffic surge management for points of presence
US9819567B1 (en) 2015-03-30 2017-11-14 Amazon Technologies, Inc. Traffic surge management for points of presence
US9887932B1 (en) 2015-03-30 2018-02-06 Amazon Technologies, Inc. Traffic surge management for points of presence
CN104811817B (en) * 2015-04-30 2018-04-13 北京奇艺世纪科技有限公司 The method of using the video client software and video playback devices
US9832141B1 (en) 2015-05-13 2017-11-28 Amazon Technologies, Inc. Routing based request correlation
US9794281B1 (en) 2015-09-24 2017-10-17 Amazon Technologies, Inc. Identifying sources of network attacks
US9742795B1 (en) 2015-09-24 2017-08-22 Amazon Technologies, Inc. Mitigating network attacks
US9774619B1 (en) 2015-09-24 2017-09-26 Amazon Technologies, Inc. Mitigating network attacks
US9992086B1 (en) 2016-08-23 2018-06-05 Amazon Technologies, Inc. External health checking of virtual private cloud network environments
CN106453675A (en) * 2016-09-19 2017-02-22 网宿科技股份有限公司 302 jump method, method and system for generating URL, and method and system for resolving domain name resolution request

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6108703A (en) * 1998-07-14 2000-08-22 Massachusetts Institute Of Technology Global hosting system
US20010049732A1 (en) * 2000-06-01 2001-12-06 Raciborski Nathan F. Content exchange apparatus
US20020026511A1 (en) * 2000-04-28 2002-02-28 Garcia-Luna-Aceves Jj System and method for controlling access to content carried in a caching architecture
US6357010B1 (en) * 1998-02-17 2002-03-12 Secure Computing Corporation System and method for controlling access to documents stored on an internal network
US6484204B1 (en) * 1997-05-06 2002-11-19 At&T Corp. System and method for allocating requests for objects and managing replicas of objects on a network
US20020184334A1 (en) * 2001-06-04 2002-12-05 Cherry Darrel D. System and method for providing intelligence to network devices
US6799214B1 (en) * 2000-03-03 2004-09-28 Nec Corporation System and method for efficient content delivery using redirection pages received from the content provider original site and the mirror sites
US20060020684A1 (en) * 2004-07-20 2006-01-26 Sarit Mukherjee User specific request redirection in a content delivery network
US7082476B1 (en) * 2000-05-24 2006-07-25 Cisco Technology, Inc. System and method of optimizing retrieval of network resources by identifying and substituting embedded symbolic host name references with network addresses in accordance with substitution policies
US20060288119A1 (en) * 2005-06-15 2006-12-21 Hostway Corporation Multi-level redirection system
US7216154B1 (en) * 2000-11-28 2007-05-08 Intel Corporation Apparatus and method for facilitating access to network resources
US20080163064A1 (en) * 2000-07-19 2008-07-03 Eric Sven-Johan Swildens Load balancing service
US20080208961A1 (en) * 2007-02-23 2008-08-28 Hostway Corporation Parallel retrieval system
US7454500B1 (en) * 2000-09-26 2008-11-18 Foundry Networks, Inc. Global server load balancing

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6854018B1 (en) * 2000-03-20 2005-02-08 Nec Corporation System and method for intelligent web content fetch and delivery of any whole and partial undelivered objects in ascending order of object size
WO2002044915A1 (en) * 2000-11-30 2002-06-06 Appfluent Technology, Inc. System and method for delivering dynamic content
US7103651B2 (en) * 2000-11-30 2006-09-05 Nortel Networks Limited Method and apparatus for discovering client proximity network sites
US7130874B2 (en) * 2002-03-12 2006-10-31 International Business Machines Corporation Method, system, and program for maintaining data in a distributed computing environment for processing transaction requests
US9137324B2 (en) * 2002-04-10 2015-09-15 International Business Machines Corporation Capacity on-demand in distributed computing environments
US20040249939A1 (en) * 2003-05-23 2004-12-09 International Business Machines Corporation Methods and apparatus for dynamic and optimal server set selection
US7475108B2 (en) * 2003-06-26 2009-01-06 International Business Machines Corporation Slow-dynamic load balancing method
US7912954B1 (en) * 2003-06-27 2011-03-22 Oesterreicher Richard T System and method for digital media server load balancing
WO2006132611A1 (en) * 2005-06-02 2006-12-14 Thomson Licensing Content timing method and system
US7730187B2 (en) * 2006-10-05 2010-06-01 Limelight Networks, Inc. Remote domain name service
US20080263180A1 (en) * 2007-04-19 2008-10-23 Hurst Mark B Apparatus, system, and method for resilient content acquisition
US8156243B2 (en) * 2008-03-31 2012-04-10 Amazon Technologies, Inc. Request routing
US7925782B2 (en) * 2008-06-30 2011-04-12 Amazon Technologies, Inc. Request routing using network computing components

Patent Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6484204B1 (en) * 1997-05-06 2002-11-19 At&T Corp. System and method for allocating requests for objects and managing replicas of objects on a network
US6357010B1 (en) * 1998-02-17 2002-03-12 Secure Computing Corporation System and method for controlling access to documents stored on an internal network
US20070005689A1 (en) * 1998-07-14 2007-01-04 Leighton F T Content distribution system using an alternative domain name system (DNS) and content servers
US6108703A (en) * 1998-07-14 2000-08-22 Massachusetts Institute Of Technology Global hosting system
US6799214B1 (en) * 2000-03-03 2004-09-28 Nec Corporation System and method for efficient content delivery using redirection pages received from the content provider original site and the mirror sites
US20020026511A1 (en) * 2000-04-28 2002-02-28 Garcia-Luna-Aceves Jj System and method for controlling access to content carried in a caching architecture
US7082476B1 (en) * 2000-05-24 2006-07-25 Cisco Technology, Inc. System and method of optimizing retrieval of network resources by identifying and substituting embedded symbolic host name references with network addresses in accordance with substitution policies
US20010049732A1 (en) * 2000-06-01 2001-12-06 Raciborski Nathan F. Content exchange apparatus
US20080163064A1 (en) * 2000-07-19 2008-07-03 Eric Sven-Johan Swildens Load balancing service
US7454500B1 (en) * 2000-09-26 2008-11-18 Foundry Networks, Inc. Global server load balancing
US7216154B1 (en) * 2000-11-28 2007-05-08 Intel Corporation Apparatus and method for facilitating access to network resources
US20020184334A1 (en) * 2001-06-04 2002-12-05 Cherry Darrel D. System and method for providing intelligence to network devices
US20060020684A1 (en) * 2004-07-20 2006-01-26 Sarit Mukherjee User specific request redirection in a content delivery network
US20060288119A1 (en) * 2005-06-15 2006-12-21 Hostway Corporation Multi-level redirection system
US20080208961A1 (en) * 2007-02-23 2008-08-28 Hostway Corporation Parallel retrieval system

Cited By (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9143451B2 (en) 2007-10-01 2015-09-22 F5 Networks, Inc. Application layer network traffic prioritization
US20150195354A1 (en) * 2009-06-25 2015-07-09 Fortinet, Inc. Redirection content requests
US20130103785A1 (en) * 2009-06-25 2013-04-25 3Crowd Technologies, Inc. Redirecting content requests
US9083652B2 (en) 2009-06-25 2015-07-14 Fortinet, Inc. Crowd based content delivery
US9712611B2 (en) * 2009-12-23 2017-07-18 Citrix Systems, Inc. Systems and methods for GSLB MEP connection management across multiple core appliances
US20130232260A1 (en) * 2009-12-23 2013-09-05 Citrix Systems, Inc. Systems and methods for gslb mep connection management across multiple core appliances
US9420049B1 (en) 2010-06-30 2016-08-16 F5 Networks, Inc. Client side human user indicator
US9503375B1 (en) 2010-06-30 2016-11-22 F5 Networks, Inc. Methods for managing traffic in a multi-service environment and devices thereof
CN102014173A (en) * 2010-11-01 2011-04-13 蓝汛网络科技(北京)有限公司 Domain name redirecting control method, module and system
US8879431B2 (en) 2011-05-16 2014-11-04 F5 Networks, Inc. Method for load balancing of requests' processing of diameter servers
US9356998B2 (en) 2011-05-16 2016-05-31 F5 Networks, Inc. Method for load balancing of requests' processing of diameter servers
US9584473B2 (en) 2011-07-29 2017-02-28 Fortinet, Inc. Facilitating content accessibility via different communication formats
US9699138B2 (en) 2011-07-29 2017-07-04 Fortinet, Inc. Directing clients based on communication format
US9331979B2 (en) 2011-07-29 2016-05-03 Fortinet, Inc. Facilitating content accessibility via different communication formats
US9917914B2 (en) 2011-07-29 2018-03-13 Fortinet, Inc. Facilitating content accessibility via different communication formats
US9584472B2 (en) 2011-07-29 2017-02-28 Fortinet, Inc. Facilitating content accessibility via different communication formats
US9537820B2 (en) 2011-07-29 2017-01-03 Fortinet, Inc. Facilitating content accessibility via different communication formats
US9680791B2 (en) 2011-07-29 2017-06-13 Fortinet, Inc. Facilitating content accessibility via different communication formats
US8504692B1 (en) * 2011-09-26 2013-08-06 Google Inc. Browser based redirection of broken links
US8392576B1 (en) 2011-09-26 2013-03-05 Google Inc. Browser based redirection of broken links
US9871722B2 (en) * 2011-12-02 2018-01-16 Huawei Technologies Co., Ltd. Content delivery network routing method, system and user terminal
US20140108672A1 (en) * 2011-12-02 2014-04-17 Huawei Technologies Co., Ltd. Content Delivery Network Routing Method, System and User Terminal
US9244843B1 (en) 2012-02-20 2016-01-26 F5 Networks, Inc. Methods for improving flow cache bandwidth utilization and devices thereof
US9307044B2 (en) 2012-03-28 2016-04-05 At&T Intellectual Property I, L.P. System and method for routing content based on real-time feedback
US9578090B1 (en) 2012-11-07 2017-02-21 F5 Networks, Inc. Methods for provisioning application delivery service and devices thereof
US9497614B1 (en) 2013-02-28 2016-11-15 F5 Networks, Inc. National traffic steering device for a better control of a specific wireless/LTE network
US20150341414A1 (en) * 2014-05-20 2015-11-26 Alibaba Group Holding Limited Method and system for acquiring web pages
US9898477B1 (en) 2014-12-05 2018-02-20 EMC IP Holding Company LLC Writing to a site cache in a distributed file system
US10021212B1 (en) 2015-03-27 2018-07-10 EMC IP Holding Company LLC Distributed file systems on content delivery networks
US9832229B2 (en) 2015-12-14 2017-11-28 Bank Of America Corporation Multi-tiered protection platform
US9992163B2 (en) 2015-12-14 2018-06-05 Bank Of America Corporation Multi-tiered protection platform
US9832200B2 (en) 2015-12-14 2017-11-28 Bank Of America Corporation Multi-tiered protection platform
US20170279888A1 (en) * 2016-03-22 2017-09-28 Go Daddy Operating Company, LLC Hosting provider hosting routes from a media repository

Also Published As

Publication number Publication date Type
US8316085B2 (en) 2012-11-20 grant
US8527635B2 (en) 2013-09-03 grant
US20100042725A1 (en) 2010-02-18 application
US20100042681A1 (en) 2010-02-18 application
US20100042724A1 (en) 2010-02-18 application

Similar Documents

Publication Publication Date Title
US7102996B1 (en) Method and system for scaling network traffic managers
US6813635B1 (en) System and method for distributing load among redundant independent stateful world wide web server sites
US6553376B1 (en) Efficient content server using request redirection
US9154551B1 (en) Processing DNS queries to identify pre-processing information
US6954456B2 (en) Method for content-aware redirection and content renaming
US7293093B2 (en) HTML delivery from edge-of-network servers in a content delivery network (CDN)
US7228359B1 (en) Methods and apparatus for providing domain name service based on a client identifier
US6490615B1 (en) Scalable cache
US20130332619A1 (en) Method of Seamless Integration and Independent Evolution of Information-Centric Networking via Software Defined Networking
US8819283B2 (en) Request routing in a networked environment
US20130339429A1 (en) Dns query processing using resource identifiers specifying an application broker
US20020199014A1 (en) Configurable and high-speed content-aware routing method
US20120198043A1 (en) Customized domain names in a content delivery network (cdn)
US20030172163A1 (en) Server load balancing system, server load balancing device, and content management device
US20110161461A1 (en) Content distribution network
US20050097185A1 (en) Localization link system
US7058633B1 (en) System and method for generalized URL-rewriting
US7925782B2 (en) Request routing using network computing components
Fayazbakhsh et al. Less pain, most of the gain: Incrementally deployable icn
US9083743B1 (en) Managing request routing information utilizing performance information
US20040047349A1 (en) Packet transfer equipment, packet transfer method resolution server, DNS server, network system and program
US9444759B2 (en) Service provider registration by a content broker
US20110231475A1 (en) Internet Protocol Version 6 Content Routing
US20080320003A1 (en) Scaling network services using dns
US8930544B2 (en) Network resource identification

Legal Events

Date Code Title Description
AS Assignment

Owner name: SK TELECOM CO., LTD.,KOREA, REPUBLIC OF

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:JEON, JAE SIC;KIM, KYONG HWAN;REEL/FRAME:023092/0358

Effective date: 20090811

AS Assignment

Owner name: SK PLANET CO., LTD., KOREA, REPUBLIC OF

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SK TELECOM. CO., LTD;REEL/FRAME:027829/0213

Effective date: 20120214