US20100042725A1 - Contents provider participation type contents delivery system and method, and contents delivery network domain name system server thereof - Google Patents
Contents provider participation type contents delivery system and method, and contents delivery network domain name system server thereof Download PDFInfo
- Publication number
- US20100042725A1 US20100042725A1 US12/540,270 US54027009A US2010042725A1 US 20100042725 A1 US20100042725 A1 US 20100042725A1 US 54027009 A US54027009 A US 54027009A US 2010042725 A1 US2010042725 A1 US 2010042725A1
- Authority
- US
- United States
- Prior art keywords
- server
- client
- address
- dns server
- page
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1021—Server selection for load balancing based on client or server locations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1034—Reaction to server failures by a load balancer
Definitions
- the present invention relates to a contents delivery network (CDN) including globally deployed replica servers, and more particularly, to a contents provider (CP) participated contents delivery system and method for allowing a web server of a CP to function as a replica server of a CDN for a client located in proximity to the web server to directly provide contents to the client, and a CDN domain name system (DNS) server of the system.
- CDN contents delivery network
- CP contents provider
- DNS CDN domain name system
- a web server of a contents provider 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.
- ISPs Internet service providers
- 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.
- 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.
- 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.
- 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.
- 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. Although general DNS-based request routing has a problem that network latency according to DNS look-up time is aggravated, the '703 patent decreases network latency by constructing hierarchical DNS servers.
- the DNS-based request routing is performed, which is inefficient.
- An object of the present invention is to allow a DNS server of a CDN provider to perform routing such that a web server operated by a contents provider to directly provide contents such as page embodied objects to a client who requests the contents through a network of the CDN provider when the client is located in proximity to the web server so as to provide improved quality of service (QoS) to the client and decrease useless network load.
- QoS quality of service
- a contents provider (CP) participated contents delivery system including: at least one host server receiving and storing an object embedded in a page and transmitting the object to a client at the request of the client; a web server storing the page and the object, transmitting the object to the at least one host server such that the at least one host server stores the object, and transmitting the page or the object to the client at the request of the client; and a CDN DNS server selecting a server located in proximity to the client from the at least one host server and the web server and transmitting the IP address of the selected server to the client through a local DNS server at the client when inquiry about the IP address of a server storing the object is received from the local DNS server.
- CP contents provider
- the CDN DNS server may select the server located in proximity to the client with reference to the IP address of the client.
- the CDN DNS server may select another server located in proximity to the client when the data traffic of the selected server exceeds a critical value.
- a CDN DNS server including: a transmitting/receiving unit for transmitting/receiving data; a database storing IP addresses of at least one host server storing an object embedded in a page and a web server providing the page and the object; a determination module determining proximity of an arbitrary client to at least one of the at least one host server and the web server; and a controller selecting a specific server which will transmit the object to the client receiving the page through the transmitting/receiving unit from the at least one host server and the web server with reference to the determination result of the determination module and transmitting the IP address of the specific server to the client through the transmitting/receiving unit via a local DNS server at the client with reference to the IP addresses stored in the database when inquiry of the local DNS server about the IP address of a server storing the object is received.
- the determination module may determine the proximity of the client to at least one of the at least one host server and the web server with reference to the IP address of the client.
- the controller may select another server located in proximity to the client when data traffic of the selected server exceeds a critical value.
- a CP participated contents delivery method including: a storing step in which at least one host server receives an object embedded in a page from a web server and stores the object embedded in the page; a page transmitting step in which the web server requested by a client to provide the page transmits the page to the client; and an address transmitting step in which a CDN DNS server selects a server located in proximity to the client from the at least one host server and the web server and transmits the IP address of the selected server to the client through the local DNS server when receiving inquiry about the IP address of a server storing the object is received from a local DNS server at the client receiving the page.
- the CDN DNS server may select the server with reference to the IP address of the client.
- the address transmitting step in which the CDN DNS server receives the inquiry about the IP address of the server storing the object may include a step in which the client inquires of the local DNS server about the IP address of the server storing the object by using a URL representing the position of the object detected while receiving and parsing the page.
- the address transmitting step in which the CDN DNS server receives the inquiry about the IP address of the server storing the object may include a step in which the local DNS server, which receives the inquiry of the client about the IP address, inquires of a contents provider DNS server about the IP address of the server storing the object, receives domain name information of a CDN provider from the contents provider DNS server and inquires of the CDN DNS server about the IP address of the server storing the object.
- the domain name information received by the local DNS server may be included in a canonical name (CNAME) record and received.
- CNAME canonical name
- FIG. 1 is a configuration of a CP participated contents delivery system according to an embodiment of the present invention
- FIG. 2 is a block diagram of a CDN DNS server illustrated in FIG. 1 ;
- FIG. 3 is a flowchart showing a CP participated contents delivery method according to an embodiment of the present invention.
- FIG. 4 is a flowchart showing a CP participated contents delivery method according to another embodiment of the present invention.
- FIG. 1 illustrates a configuration of a CP participated contents delivery system according to an embodiment of the present invention.
- the contents delivery system includes a client 110 , a local domain name system (DNS) server 120 , a host server 130 , a CDN DNS server 140 , a contents provider DNS server 150 , a web server 160 and a network 170 .
- DNS local domain name system
- the client 110 corresponds to equipment such as a computer receiving information from the servers connected through the network 170 .
- 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.
- a uniform resource locator URL
- 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.
- IP Internet Protocol
- the client 110 when the client 110 receives a page from the web server 160 by using the IP address of the web server 160 , the client 110 parses the page and inquires of the local DNS server 120 about the IP address of a server which will provide an embedded object detected while the page is parsed by using the URL of the embedded object. Then, when the client 110 receives the IP address of the web server 160 or the host server 130 , which will transmit the embedded object, from the local DNS server 120 , the client 110 accesses the corresponding server by using the IP address and receives the embedded object.
- 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 .
- the local DNS server 120 When the client 110 requests the local DNS server 120 to provide the IP address of the server storing the embedded object included in the page, the local DNS server 120 transmits/receives messages to/from the contents provider DNS server 150 or the CDN DNS server 140 to transmit the IP address of the web server 160 or the host server 130 which will transmit the embedded object to the client 110 .
- the host server 130 stores replicas of page embedded objects stored in and administrated by the web server 160 and rapidly provides the replicas when the client 110 requests the host server 130 to provide contents.
- the CDN DNS server 140 is a DNS server of a CDN provider and provides the IP address of the host server 130 storing the embedded object at the request of the local DNS server 120 .
- the CDN DNS server 140 of the present invention not only performs a general DNS server function but also selects the host server 130 efficient to provide the embedded object to the client 110 in consideration of at least one of data traffic information of at least one host information 130 , information on proximity of the client 110 to the at least one host server 130 and object information stored in the at least one host server 130 and transmits the IP address of the selected host server 130 to the client 110 through the local DNS server 120 .
- the data traffic information of the at least one host information 130 may be collected in consideration of data traffic and load of the CDN DNS server 140 or the host server 130 when the object stored in the host server 130 is updated and at predetermined time such as a specific period.
- the CDN DNS server 140 When the CDN DNS server 140 receives inquiry of the local DNS server 120 at the client 110 about the IP address of a server storing the page embedded object, the CDN DNS server 140 selects a server located in proximity to the client 110 from the at least one host server 130 and the web server 160 which store the object and transmits the IP address of the selected server to the client 110 through the local DNS server 120 such that the client 110 can receive the object from the selected server. That is, if the web server 160 is located in proximity to the client 110 , and thus it is more efficient to provide the page embedded object by the web server 160 in terms of network route, the web server 160 provides the object to the client 110 . If not, one of the at least one host server 130 , which is located in proximity to the client 110 to be suitable to provide the object, is selected and provides the object to the client 110 .
- the server located in proximity to the client 110 may be selected with reference to the IP address of the client 110 .
- another server located in proximity to the client 110 may be selected and the IP address of the selected server may be transmitted to the client 110 through the local DNS server 120 .
- the client 110 can receive the page embedded object through a network route providing a more rapid response and the CDN provider can dynamically determine the subject of object transmission in consideration of loads of the host server 130 and the web server 160 and network route.
- the web server 160 provides a web page and an embedded object included in the web page, provided by the contents provider.
- the contents provider transmits the embedded object from the web server 160 to the host server 130 such that the host server 130 stores the embedded object. Accordingly, when the client 110 requests the embedded object included in the page, the client 110 can rapidly receive a response through the host server 130 .
- the contents DNS server 150 is a DNS server of the contents provider.
- the contents provider DNS server 150 receives inquiry of the local DNS server 120 about the IP address of the web server 160 storing the page, the contents provider DNS server 150 returns the IP address.
- the contents provider DNS server 150 receives inquiry of the local DNS server 120 about the IP address of a server storing the object included in the page, the contents provider DNS server 150 transmits domain name information of the CDN provider to the local DNS server 120 such that the local DNS server 120 can inquire of the CDN DNS server 140 about the IP address of the server storing the object.
- the domain name information can be transmitted to the local DNS server 120 through a canonical name (CANAME) method, for example.
- CNAME means DNS database record representing a host name.
- the local DNS server 120 can inquire of the CDN DNS server 140 about the IP address of the server storing object by using the domain name information of the CND provider, which is included in the DNS database record.
- 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 CDN DNS server 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.
- CDN DNS server 140 The configuration and operation of the CDN DNS server 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 CDN DNS server 140 illustrated in FIG. 1 .
- the CDN DNS server 140 includes a transmitting/receiving unit 141 , a controller 143 , a database 145 and a determination module 147 .
- the transmitting/receiving unit 141 has an interface for transmitting/receiving data and messages through the network 170 .
- the database 145 stores the IP addresses of the at least one host server 130 and the web server 160 which store page embedded objects provided by the web server.
- the determination module 147 determines proximity of the client 110 to the at least one host server 130 and the web server 160 .
- the proximity of the client 110 to at least one host server 130 and the web server 160 can be determined by using the IP address of the client 110 .
- the controller 143 controls the operation of the CDN DNS server 140 . Specifically, the controller 143 transmits the IP address of the web server 160 to the client 110 through the transmitting/receiving unit 141 via the local DNS server 120 if the determination module 147 determines that the client is located in proximity to the web server 160 when the local DNS server 120 inquires of the CDN DNS server 140 about the IP address of a server storing a page embedded object.
- the controller transmits the IP address of the host server 130 to the client 110 through the transmitting/receiving unit 141 through the local DNS server 120 .
- the client 110 can receive the page embedded object from the server located in proximity thereto. If the selected server is not suitable to provide the object to the client 110 because the data traffic of the server exceeds a critical value although the determination module 147 determines that the server is located in proximity to the client 110 , the controller 143 can transmit the IP address of another sever located in proximity to the client 110 to the client 110 through the transmitting/receiving unit 141 via the local DNS server 120 to attempt to distribute load of the server.
- data traffic information of each server may be information collected by the controller 143 through the transmitting/receiving unit 141 at a specific period or information collected by the determination module 147 through transmitting/receiving unit 141 at a specific period and referred to by the controller 143 .
- FIG. 3 is a flowchart showing a CP participated contents delivery method according to an embodiment of the present invention.
- the at least one host server 130 receives an object embedded in a page of the contents provider from the web server 160 and stores the embedded object in step S 400 .
- Contents, that is, the embedded object may be transmitted in step S 400 when the host server 130 requests the web server 160 to provide the embedded object, at specific periods, and when the object embedded in the page stored in the web server 160 is updated.
- 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 embedded object in step S 405 .
- the local DNS server 120 receives the inquiry about the IP address of the web server 160 in step S 405 and inquires of the contents provider DNS server 150 about the IP address of the web server 160 storing the page and the embedded object in step S 410 .
- the contents provider DNS server 150 receives the inquiry of the local DNS server 120 in step S 410 and transmits the IP address of the web server 160 to the local DNS server 120 in step S 415 .
- the local DNS server 120 receives the IP address of the web server 160 and transmits the IP address of the web server 160 to the client 110 in step S 420 .
- the client 110 receives the IP address of the web server 160 in step S 420 and requests the web server 160 to provide the page embedded object by using the IP address of the web server 160 in step S 425 .
- the web server 160 receives the request of the client 110 in step S 425 and transmits the page to the client 110 in step S 430 .
- the URL representing the position of the embedded object stored in the page is rewritten into a URL representing the position of the embedded object stored in the host server 130 operated and administrated by the CDN provider.
- the client 110 receives the page in step S 430 and parses the page in step S 435 .
- the client 110 detects the URL representing the position of the embedded object stored in the page while parsing the page, the client 110 inquires of the local DNS server 120 about the IP address of a server storing the page embedded object by using the URL in step S 440 .
- the local DNS server 120 receives the inquiry of the client 110 in step S 440 and inquires of the CDN DNS server 140 about the IP address of the server storing the object in step S 445 .
- the CDN DNS server 140 receives the inquiry of the local DNS server 120 in step S 445 and determines proximity of the client 110 to the at least one host server 130 and the web server 160 in step S 450 .
- the CDN DNS server 140 can determine the proximity of the client 110 to the at least one host server 130 and the web server 160 with reference to the IP address of the client 110 , for example.
- the CDN DNS server 140 determines that the client 110 is located in proximity to the web server 160 in step S 450 , the CDN DNS server 140 transmits the IP address of the web server 160 to the local DNS server 120 in step S 455 .
- the local DNS server 120 transmits the IP address of the web server 160 , received in step S 455 , to the client 110 in step S 460 .
- the client 110 requests the web server 160 to provide the object by using the IP address of the web server 160 , received in step S 460 , and receives the object from the web server 160 in step S 470 .
- the IP address of another web server or host server located in proximity to the client 110 can be transmitted to the local DNS server 120 to prevent the load of the web server 160 from increasing.
- the CDN DNS server 140 determines that a specific host server 130 is closer to the client 110 than the web server 160 in step S 450 , the CDN DNS server 140 transmits the IP address of the specific host server 130 to the local DNS server 120 in step S 475 .
- the local DNS server 120 transmits the IP address of the host server 130 , received in step S 475 , to the client 110 in step S 480 .
- the client 110 requests the host server 130 to provide the object by using the IP address of the host server 130 , received in step S 480 , in step S 485 and receives the object from the host server 130 in step S 490 .
- the CDN DNS server 140 can transmit the IP address of the web server 160 or another host server located in proximity to the client 110 to the local DNS server 120 to attempt load distribution.
- FIG. 4 is a flowchart showing a CP participated contents delivery method according to another embodiment of the present invention.
- steps S 400 through S 425 are identical to those of the contents delivery method illustrated in FIG. 3 so that detailed explanations thereof are omitted.
- the web server 160 receives the request of the client 110 for the page embedded object in step S 425 and transmits the corresponding page to the client 110 in step S 500 .
- the page transmitted in step S 500 may be the original page in which the URL representing the position of the embedded object is not rewritten, which is distinguished from the embodiment described with reference to FIG. 3 .
- the client 110 parses the page, received in step S 500 , in step S 505 .
- the client 110 detects the URL of the object embedded in the page while parsing the page in step S 505
- the client 110 inquires of the local DNS server 120 about the IP address of a server storing the page embedded object by using the URL in step S 510 .
- the local DNS server 120 receives the inquiry of the client 110 in step S 510 and inquires of the contents provider DNS server 150 about the IP address of the server storing the object in step S 515 .
- the contents provider DNS server 150 receives the inquiry of the local DNS server 120 in step S 515 and transmits domain name information of the CDN provider to the local DNS server 120 in step S 520 .
- the domain name information of the CDN provider may be included in CNAME resource record and transmitted, for example.
- the local DNS server 120 receives the domain name information in step S 520 and inquires of the CDN DNS server 140 about the IP address of the server storing the page embedded object by using the domain name information in step S 525 .
- the CDN DNS server 140 receives the inquiry of the local DNS server 120 in step S 525 and determines proximity of the client 110 to the at least one host server 130 and the web server 160 in step S 530 .
- the CDN DNS server 140 can determine the proximity of the client 110 to the at least one host server 130 and the web server 160 with reference to the IP address of the client 110 , for example.
- the CDN DNS server 140 determines that the client 110 is located in proximity to the web server 160 in step S 530 , the CDN DNS server 140 transmits the IP address of the web server 160 to the local DNS server 120 in step S 535 .
- the local DNS server 120 transmits the IP address of the web server 160 , received in step S 535 , to the client 110 in step S 540 .
- the client 110 requests the web server 160 to provide the page em bedded object by using the IP address of the web server 160 , received in step S 540 , in step S 545 and receives the object from the web server 160 in step S 550 .
- the IP address of another web server or host server located in proximity to the client 110 can be transmitted to the local DNS server 120 to prevent the load of the web server 160 from increasing.
- the CDN DNS server 140 determines that a specific host server 130 is closer to the client 110 than the web server 160 in step S 530 , the CDN DNS server 140 transmits the IP address of the specific host server 130 to the local DNS server 120 in step S 555 .
- the local DNS server 120 transmits the IP address of the host server 130 , received in step S 555 , to the client 110 in step S 560 .
- the client 110 requests the host server 130 to provide the object by using the IP address of the host server 130 , received in step S 560 , in step S 565 and receives the object from the host server 130 in step S 570 .
- the CDN DNS server 140 can transmit the IP address of the web server 160 or another host server located in proximity to the client 110 to the local DNS server 120 to attempt load distribution.
- a client can receive a page embedded object from a server selected from a web server and at least one host server and located in proximity to the client. Accordingly, the client can rapidly receive the object and a contents provider can promote qualitative contents providing service improvement.
Abstract
A CP participated contents delivery system and method, and a CDN DNS server of the system are provided. When a client detects an embedded object while parsing a page received from a web server, the client inquires of a local DNS server about the IP address of a server storing the object. The local DNS server receives the inquiry of the client and inquires of a CDN DNS server about the IP address of the server storing the object. The CDN DNS server selects a server located in proximity to the client from a host server of a CDN provider, which stores the object, and the web server. The selected server transmits the object to the client. Accordingly, the client can rapidly receive the object and a contents provider can promote qualitative contents providing service improvement.
Description
- 1. Field of the Invention
- The present invention relates to a contents delivery network (CDN) including globally deployed replica servers, and more particularly, to a contents provider (CP) participated contents delivery system and method for allowing a web server of a CP to function as a replica server of a CDN for a client located in proximity to the web server to directly provide contents to the client, and a CDN domain name system (DNS) server of the 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. Although general DNS-based request routing has a problem that network latency according to DNS look-up time is aggravated, the '703 patent decreases network latency by constructing hierarchical DNS servers.
- However, even when the client is located in proximity to the web server of the contents provider, that is, when the client and the web server of the contents provider are close to each other geographically or on a network route, the DNS-based request routing is performed, which is inefficient.
- Accordingly, a method for solving the aforementioned problems is required.
- An object of the present invention is to allow a DNS server of a CDN provider to perform routing such that a web server operated by a contents provider to directly provide contents such as page embodied objects to a client who requests the contents through a network of the CDN provider when the client is located in proximity to the web server so as to provide improved quality of service (QoS) to the client and decrease useless network load.
- To accomplish the object of the present invention, according to an aspect of the present invention, there is provided a contents provider (CP) participated contents delivery system including: at least one host server receiving and storing an object embedded in a page and transmitting the object to a client at the request of the client; a web server storing the page and the object, transmitting the object to the at least one host server such that the at least one host server stores the object, and transmitting the page or the object to the client at the request of the client; and a CDN DNS server selecting a server located in proximity to the client from the at least one host server and the web server and transmitting the IP address of the selected server to the client through a local DNS server at the client when inquiry about the IP address of a server storing the object is received from the local DNS server.
- The CDN DNS server may select the server located in proximity to the client with reference to the IP address of the client.
- The CDN DNS server may select another server located in proximity to the client when the data traffic of the selected server exceeds a critical value.
- According to another aspect of the present invention, there is provided a CDN DNS server including: a transmitting/receiving unit for transmitting/receiving data; a database storing IP addresses of at least one host server storing an object embedded in a page and a web server providing the page and the object; a determination module determining proximity of an arbitrary client to at least one of the at least one host server and the web server; and a controller selecting a specific server which will transmit the object to the client receiving the page through the transmitting/receiving unit from the at least one host server and the web server with reference to the determination result of the determination module and transmitting the IP address of the specific server to the client through the transmitting/receiving unit via a local DNS server at the client with reference to the IP addresses stored in the database when inquiry of the local DNS server about the IP address of a server storing the object is received.
- The determination module may determine the proximity of the client to at least one of the at least one host server and the web server with reference to the IP address of the client.
- The controller may select another server located in proximity to the client when data traffic of the selected server exceeds a critical value.
- According to another aspect of the present invention, there is provided a CP participated contents delivery method including: a storing step in which at least one host server receives an object embedded in a page from a web server and stores the object embedded in the page; a page transmitting step in which the web server requested by a client to provide the page transmits the page to the client; and an address transmitting step in which a CDN DNS server selects a server located in proximity to the client from the at least one host server and the web server and transmits the IP address of the selected server to the client through the local DNS server when receiving inquiry about the IP address of a server storing the object is received from a local DNS server at the client receiving the page.
- In the address transmitting step, the CDN DNS server may select the server with reference to the IP address of the client.
- The address transmitting step in which the CDN DNS server receives the inquiry about the IP address of the server storing the object may include a step in which the client inquires of the local DNS server about the IP address of the server storing the object by using a URL representing the position of the object detected while receiving and parsing the page.
- The address transmitting step in which the CDN DNS server receives the inquiry about the IP address of the server storing the object may include a step in which the local DNS server, which receives the inquiry of the client about the IP address, inquires of a contents provider DNS server about the IP address of the server storing the object, receives domain name information of a CDN provider from the contents provider DNS server and inquires of the CDN DNS server about the IP address of the server storing the object.
- The domain name information received by the local DNS server may be included in a canonical name (CNAME) record and received.
- 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 CP participated contents delivery system according to an embodiment of the present invention; -
FIG. 2 is a block diagram of a CDN DNS server illustrated inFIG. 1 ; -
FIG. 3 is a flowchart showing a CP participated contents delivery method according to an embodiment of the present invention; and -
FIG. 4 is a flowchart showing a CP participated contents delivery method according to another embodiment of the present 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 CP participated contents delivery system according to an embodiment of the present invention. Referring toFIG. 1 , the contents delivery system includes aclient 110, a local domain name system (DNS)server 120, ahost server 130, aCDN DNS server 140, a contentsprovider DNS server 150, aweb server 160 and anetwork 170. - The
client 110 corresponds to equipment such as a computer receiving information from the servers connected through thenetwork 170. For example, theclient 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 theclient 110, the resolver connected to the browser accesses the previously registeredlocal DNS server 120 and resolves a domain name corresponding to the URL into the IP (Internet Protocol) address of theweb server 160 providing the contents. - In the current embodiment of the invention, when the
client 110 receives a page from theweb server 160 by using the IP address of theweb server 160, theclient 110 parses the page and inquires of thelocal DNS server 120 about the IP address of a server which will provide an embedded object detected while the page is parsed by using the URL of the embedded object. Then, when theclient 110 receives the IP address of theweb server 160 or thehost server 130, which will transmit the embedded object, from thelocal DNS server 120, theclient 110 accesses the corresponding server by using the IP address and receives the embedded object. - 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. Thelocal DNS server 120 that receives the domain name of theweb server 160 from the resolver accesses the contentsprovider DNS server 150, receives the IP address of theweb server 160, which corresponds to the domain name, and transmits the IP address to theclient 110. - When the
client 110 requests thelocal DNS server 120 to provide the IP address of the server storing the embedded object included in the page, thelocal DNS server 120 transmits/receives messages to/from the contentsprovider DNS server 150 or theCDN DNS server 140 to transmit the IP address of theweb server 160 or thehost server 130 which will transmit the embedded object to theclient 110. - The
host server 130 stores replicas of page embedded objects stored in and administrated by theweb server 160 and rapidly provides the replicas when theclient 110 requests thehost server 130 to provide contents. - The
CDN DNS server 140 is a DNS server of a CDN provider and provides the IP address of thehost server 130 storing the embedded object at the request of thelocal DNS server 120. The CDNDNS server 140 of the present invention not only performs a general DNS server function but also selects thehost server 130 efficient to provide the embedded object to theclient 110 in consideration of at least one of data traffic information of at least onehost information 130, information on proximity of theclient 110 to the at least onehost server 130 and object information stored in the at least onehost server 130 and transmits the IP address of the selectedhost server 130 to theclient 110 through thelocal DNS server 120. - Here, the data traffic information of the at least one
host information 130, the information on proximity of theclient 110 to the at least onehost server 130 and the object information stored in the at least onehost server 130, considered by theCDN DNS server 140, may be collected in consideration of data traffic and load of theCDN DNS server 140 or thehost server 130 when the object stored in thehost server 130 is updated and at predetermined time such as a specific period. - When the
CDN DNS server 140 receives inquiry of thelocal DNS server 120 at theclient 110 about the IP address of a server storing the page embedded object, theCDN DNS server 140 selects a server located in proximity to theclient 110 from the at least onehost server 130 and theweb server 160 which store the object and transmits the IP address of the selected server to theclient 110 through thelocal DNS server 120 such that theclient 110 can receive the object from the selected server. That is, if theweb server 160 is located in proximity to theclient 110, and thus it is more efficient to provide the page embedded object by theweb server 160 in terms of network route, theweb server 160 provides the object to theclient 110. If not, one of the at least onehost server 130, which is located in proximity to theclient 110 to be suitable to provide the object, is selected and provides the object to theclient 110. - Here, the server located in proximity to the
client 110 may be selected with reference to the IP address of theclient 110. However, when the data traffic of the server selected to provide the object to theclient 110 exceeds a critical value, another server located in proximity to theclient 110 may be selected and the IP address of the selected server may be transmitted to theclient 110 through thelocal DNS server 120. - In this manner, the
client 110 can receive the page embedded object through a network route providing a more rapid response and the CDN provider can dynamically determine the subject of object transmission in consideration of loads of thehost server 130 and theweb server 160 and network route. - The
web server 160 provides a web page and an embedded object included in the web page, provided by the contents provider. In the current embodiment of the present invention, the contents provider transmits the embedded object from theweb server 160 to thehost server 130 such that thehost server 130 stores the embedded object. Accordingly, when theclient 110 requests the embedded object included in the page, theclient 110 can rapidly receive a response through thehost server 130. - The
contents DNS server 150 is a DNS server of the contents provider. When the contentsprovider DNS server 150 receives inquiry of thelocal DNS server 120 about the IP address of theweb server 160 storing the page, the contentsprovider DNS server 150 returns the IP address. - Furthermore, when the contents
provider DNS server 150 receives inquiry of thelocal DNS server 120 about the IP address of a server storing the object included in the page, the contentsprovider DNS server 150 transmits domain name information of the CDN provider to thelocal DNS server 120 such that thelocal DNS server 120 can inquire of theCDN DNS server 140 about the IP address of the server storing the object. - Here, the domain name information can be transmitted to the
local DNS server 120 through a canonical name (CANAME) method, for example. CNAME means DNS database record representing a host name. Thelocal DNS server 120 can inquire of theCDN DNS server 140 about the IP address of the server storing object by using the domain name information of the CND provider, which is included in the DNS database record. - The
network 170 corresponds to a data communication network for data transmission and information exchange among theclient 110, thelocal DNS server 120, thehost server 130, theCDN DNS server 140, the contentsprovider DNS server 150 and theweb server 160. Thenetwork 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
CDN DNS server 140 according to an embodiment of the present invention will now be explained in more detail with reference toFIG. 2 . -
FIG. 2 is a block diagram of theCDN DNS server 140 illustrated inFIG. 1 . Referring toFIGS. 1 and 2 , theCDN DNS server 140 includes a transmitting/receivingunit 141, acontroller 143, adatabase 145 and adetermination module 147. - The transmitting/receiving
unit 141 has an interface for transmitting/receiving data and messages through thenetwork 170. - The
database 145 stores the IP addresses of the at least onehost server 130 and theweb server 160 which store page embedded objects provided by the web server. - The
determination module 147 determines proximity of theclient 110 to the at least onehost server 130 and theweb server 160. Here, the proximity of theclient 110 to at least onehost server 130 and theweb server 160 can be determined by using the IP address of theclient 110. - The
controller 143 controls the operation of theCDN DNS server 140. Specifically, thecontroller 143 transmits the IP address of theweb server 160 to theclient 110 through the transmitting/receivingunit 141 via thelocal DNS server 120 if thedetermination module 147 determines that the client is located in proximity to theweb server 160 when thelocal DNS server 120 inquires of theCDN DNS server 140 about the IP address of a server storing a page embedded object. - If the
determination module 147 determines that theclient 110 is closer to thehost server 130 than theweb server 160, the controller transmits the IP address of thehost server 130 to theclient 110 through the transmitting/receivingunit 141 through thelocal DNS server 120. - In this manner, the
client 110 can receive the page embedded object from the server located in proximity thereto. If the selected server is not suitable to provide the object to theclient 110 because the data traffic of the server exceeds a critical value although thedetermination module 147 determines that the server is located in proximity to theclient 110, thecontroller 143 can transmit the IP address of another sever located in proximity to theclient 110 to theclient 110 through the transmitting/receivingunit 141 via thelocal DNS server 120 to attempt to distribute load of the server. - Here, data traffic information of each server may be information collected by the
controller 143 through the transmitting/receivingunit 141 at a specific period or information collected by thedetermination module 147 through transmitting/receivingunit 141 at a specific period and referred to by thecontroller 143. - A contents delivery method according to the present invention will be explained with reference to
FIGS. 3 and 4 . -
FIG. 3 is a flowchart showing a CP participated contents delivery method according to an embodiment of the present invention. Referring toFIG. 3 , the at least onehost server 130 receives an object embedded in a page of the contents provider from theweb server 160 and stores the embedded object in step S400. Contents, that is, the embedded object, may be transmitted in step S400 when thehost server 130 requests theweb server 160 to provide the embedded object, at specific periods, and when the object embedded in the page stored in theweb server 160 is updated. - When the browser of the
client 110 receives a URL for requesting theweb server 160 to provide the embedded object, the resolver of theclient 110 inquires of thelocal DNS server 120 about the IP address of theweb server 160 storing the page and the embedded object in step S405. - The
local DNS server 120 receives the inquiry about the IP address of theweb server 160 in step S405 and inquires of the contentsprovider DNS server 150 about the IP address of theweb server 160 storing the page and the embedded object in step S410. - The contents
provider DNS server 150 receives the inquiry of thelocal DNS server 120 in step S410 and transmits the IP address of theweb server 160 to thelocal DNS server 120 in step S415. Thelocal DNS server 120 receives the IP address of theweb server 160 and transmits the IP address of theweb server 160 to theclient 110 in step S420. - The
client 110 receives the IP address of theweb server 160 in step S420 and requests theweb server 160 to provide the page embedded object by using the IP address of theweb server 160 in step S425. - The
web server 160 receives the request of theclient 110 in step S425 and transmits the page to theclient 110 in step S430. Here, the URL representing the position of the embedded object stored in the page is rewritten into a URL representing the position of the embedded object stored in thehost server 130 operated and administrated by the CDN provider. - The
client 110 receives the page in step S430 and parses the page in step S435. When theclient 110 detects the URL representing the position of the embedded object stored in the page while parsing the page, theclient 110 inquires of thelocal DNS server 120 about the IP address of a server storing the page embedded object by using the URL in step S440. - The
local DNS server 120 receives the inquiry of theclient 110 in step S440 and inquires of theCDN DNS server 140 about the IP address of the server storing the object in step S445. - The
CDN DNS server 140 receives the inquiry of thelocal DNS server 120 in step S445 and determines proximity of theclient 110 to the at least onehost server 130 and theweb server 160 in step S450. Here, theCDN DNS server 140 can determine the proximity of theclient 110 to the at least onehost server 130 and theweb server 160 with reference to the IP address of theclient 110, for example. - When the
CDN DNS server 140 determines that theclient 110 is located in proximity to theweb server 160 in step S450, theCDN DNS server 140 transmits the IP address of theweb server 160 to thelocal DNS server 120 in step S455. Thelocal DNS server 120 transmits the IP address of theweb server 160, received in step S455, to theclient 110 in step S460. - The
client 110 requests theweb server 160 to provide the object by using the IP address of theweb server 160, received in step S460, and receives the object from theweb server 160 in step S470. - In the current embodiment of the present invention, if the data traffic of the
web server 160 exceeds a critical value although it is determined that theclient 110 is located in proximity to theweb server 160 in step S450, the IP address of another web server or host server located in proximity to theclient 110 can be transmitted to thelocal DNS server 120 to prevent the load of theweb server 160 from increasing. - If the
CDN DNS server 140 determines that aspecific host server 130 is closer to theclient 110 than theweb server 160 in step S450, theCDN DNS server 140 transmits the IP address of thespecific host server 130 to thelocal DNS server 120 in step S475. Thelocal DNS server 120 transmits the IP address of thehost server 130, received in step S475, to theclient 110 in step S480. - Then, the
client 110 requests thehost server 130 to provide the object by using the IP address of thehost server 130, received in step S480, in step S485 and receives the object from thehost server 130 in step S490. - In the current embodiment of the present invention, if the data traffic of the
host server 130 exceeds a critical value although theCDN DNS server 140 determines that theclient 110 is located in proximity to thehost server 130 in step S450, theCDN DNS server 140 can transmit the IP address of theweb server 160 or another host server located in proximity to theclient 110 to thelocal DNS server 120 to attempt load distribution. -
FIG. 4 is a flowchart showing a CP participated contents delivery method according to another embodiment of the present invention. InFIG. 4 , steps S400 through S425 are identical to those of the contents delivery method illustrated inFIG. 3 so that detailed explanations thereof are omitted. - The
web server 160 receives the request of theclient 110 for the page embedded object in step S425 and transmits the corresponding page to theclient 110 in step S500. The page transmitted in step S500 may be the original page in which the URL representing the position of the embedded object is not rewritten, which is distinguished from the embodiment described with reference toFIG. 3 . - The
client 110 parses the page, received in step S500, in step S505. When theclient 110 detects the URL of the object embedded in the page while parsing the page in step S505, theclient 110 inquires of thelocal DNS server 120 about the IP address of a server storing the page embedded object by using the URL in step S510. - The
local DNS server 120 receives the inquiry of theclient 110 in step S510 and inquires of the contentsprovider DNS server 150 about the IP address of the server storing the object in step S515. - The contents
provider DNS server 150 receives the inquiry of thelocal DNS server 120 in step S515 and transmits domain name information of the CDN provider to thelocal DNS server 120 in step S520. Here, the domain name information of the CDN provider may be included in CNAME resource record and transmitted, for example. - The
local DNS server 120 receives the domain name information in step S520 and inquires of theCDN DNS server 140 about the IP address of the server storing the page embedded object by using the domain name information in step S525. - The
CDN DNS server 140 receives the inquiry of thelocal DNS server 120 in step S525 and determines proximity of theclient 110 to the at least onehost server 130 and theweb server 160 in step S530. Here, theCDN DNS server 140 can determine the proximity of theclient 110 to the at least onehost server 130 and theweb server 160 with reference to the IP address of theclient 110, for example. - When the
CDN DNS server 140 determines that theclient 110 is located in proximity to theweb server 160 in step S530, theCDN DNS server 140 transmits the IP address of theweb server 160 to thelocal DNS server 120 in step S535. Thelocal DNS server 120 transmits the IP address of theweb server 160, received in step S535, to theclient 110 in step S540. - The
client 110 requests theweb server 160 to provide the page em bedded object by using the IP address of theweb server 160, received in step S540, in step S545 and receives the object from theweb server 160 in step S550. - In the current embodiment of the present invention, if the data traffic of the
web server 160 exceeds a critical value although it is determined that theclient 110 is located in proximity to theweb server 160 in step S530, the IP address of another web server or host server located in proximity to theclient 110 can be transmitted to thelocal DNS server 120 to prevent the load of theweb server 160 from increasing. - If the
CDN DNS server 140 determines that aspecific host server 130 is closer to theclient 110 than theweb server 160 in step S530, theCDN DNS server 140 transmits the IP address of thespecific host server 130 to thelocal DNS server 120 in step S555. Thelocal DNS server 120 transmits the IP address of thehost server 130, received in step S555, to theclient 110 in step S560. - Then, the
client 110 requests thehost server 130 to provide the object by using the IP address of thehost server 130, received in step S560, in step S565 and receives the object from thehost server 130 in step S570. - In the current embodiment of the present invention, if the data traffic of the
host server 130 exceeds a critical value although theCDN DNS server 140 determines that theclient 110 is located in proximity to thehost server 130 in step S530, theCDN DNS server 140 can transmit the IP address of theweb server 160 or another host server located in proximity to theclient 110 to thelocal DNS server 120 to attempt load distribution. - According to the present invention, a client can receive a page embedded object from a server selected from a web server and at least one host server and located in proximity to the client. Accordingly, the client can rapidly receive the object and a contents provider can promote qualitative contents providing service improvement.
- 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 (11)
1. A contents provider (CP) participated contents delivery system comprising: at least one host server receiving and storing an object embedded in a page and transmitting the object to a client at the request of the client;
a web server storing the page and the object, transmitting the object to the at least one host server such that the at least one host server stores the object, and transmitting the page or the object to the client at the request of the client; and
a CDN DNS server selecting a server located in proximity to the client from the at least one host server and the web server and transmitting the IP address of the selected server to the client through a local DNS server at the client when inquiry about the IP address of a server storing the object is received from the local DNS server.
2. The CP participated contents delivery system of claim 1 , wherein the CDN DNS server selects the server located in proximity to the client with reference to the IP address of the client.
3. The CP participated contents delivery system of claim 1 , wherein the CDN DNS server selects another server located in proximity to the client when the data traffic of the selected server exceeds a critical value.
4. A CDN DNS server comprising:
a transmitting/receiving unit for transmitting/receiving data;
a database storing IP addresses of at least one host server storing an object embedded in a page and a web server providing the page and the object;
a determination module determining proximity of an arbitrary client to at least one of the at least one host server and the web server; and
a controller selecting a specific server which will transmit the object to the client receiving the page through the transmitting/receiving unit from the at least one host server and the web server with reference to the determination result of the determination module and transmitting the IP address of the specific server to the client through the transmitting/receiving unit via a local DNS server at the client with reference to the IP addresses stored in the database when inquiry of the local DNS server about the IP address of a server storing the object is received.
5. The CDN DNS server of claim 4 , wherein the determination module determines the proximity of the client to at least one of the at least one host server and the web server with reference to the IP address of the client.
6. The CDN DNS server of claim 4 , wherein the controller selects another server located in proximity to the client when data traffic of the selected server exceeds a critical value.
7. A CP participated contents delivery method comprising:
a storing step in which at least one host server receives an object embedded in a page from a web server and stores the object embedded in the page;
a page transmitting step in which the web server requested by a client to provide the page transmits the page to the client; and
an address transmitting step in which a CDN DNS server selects a server located in proximity to the client from the at least one host server and the web server and transmits the IP address of the selected server to the client through the local DNS server when receiving inquiry about the IP address of a server storing the object is received from a local DNS server at the client receiving the page.
8. The CP participated contents delivery method of claim 7 , wherein, in the address transmitting step, the CDN DNS server selects the server with reference to the IP address of the client.
9. The CP participated contents delivery method of claim 7 , wherein the address transmitting step in which the CDN DNS server receives the inquiry about the IP address of the server storing the object comprises a step in which the client inquires of the local DNS server about the IP address of the server storing the object by using a URL representing the position of the object detected while receiving and parsing the page.
10. The CP participated contents delivery method of claim 8 , wherein the address transmitting step in which the CDN DNS server receives the inquiry about the IP address of the server storing the object comprises a step in which the local DNS server, which receives the inquiry of the client about the IP address, inquires of a contents provider DNS server about the IP address of the server storing the object, receives domain name information of a CDN provider from the contents provider DNS server and inquires of the CDN DNS server about the IP address of the server storing the object.
11. The CP participated contents delivery method of claim 8 , wherein the domain name information received by the local DNS server is included in a canonical name (CNAME) record and received.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/540,270 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 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US8854108P | 2008-08-13 | 2008-08-13 | |
US12/540,270 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 |
Publications (1)
Publication Number | Publication Date |
---|---|
US20100042725A1 true US20100042725A1 (en) | 2010-02-18 |
Family
ID=41682024
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/540,127 Abandoned US20100042743A1 (en) | 2008-08-13 | 2009-08-12 | Contents delivery system and method using page redirection, and gslb switch thereof |
US12/540,270 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 |
US12/540,212 Expired - Fee Related US8316085B2 (en) | 2008-08-13 | 2009-08-12 | Contents delivery system and method using object redirection, and GSLB switch thereof |
US12/540,234 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 |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/540,127 Abandoned US20100042743A1 (en) | 2008-08-13 | 2009-08-12 | Contents delivery system and method using page redirection, and gslb switch thereof |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/540,212 Expired - Fee Related US8316085B2 (en) | 2008-08-13 | 2009-08-12 | Contents delivery system and method using object redirection, and GSLB switch thereof |
US12/540,234 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 |
Country Status (1)
Country | Link |
---|---|
US (4) | US20100042743A1 (en) |
Cited By (89)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110179174A1 (en) * | 2010-01-19 | 2011-07-21 | Nokia Corporation | Apparatus identification in coexistence networking |
US20130212300A1 (en) * | 2012-02-15 | 2013-08-15 | Limelight Networks, Inc. | Scaled domain name service |
US20140365666A1 (en) * | 2010-09-28 | 2014-12-11 | Amazon Technologies, Inc. | Request routing in a networked environment |
US8924395B2 (en) | 2010-10-06 | 2014-12-30 | Planet Data Solutions | System and method for indexing electronic discovery data |
US9130756B2 (en) | 2009-09-04 | 2015-09-08 | Amazon Technologies, Inc. | Managing secure content in a content delivery network |
US9154551B1 (en) | 2012-06-11 | 2015-10-06 | Amazon Technologies, Inc. | Processing DNS queries to identify pre-processing information |
US9191458B2 (en) | 2009-03-27 | 2015-11-17 | Amazon Technologies, Inc. | Request routing using a popularity identifier at a DNS nameserver |
US9208097B2 (en) | 2008-03-31 | 2015-12-08 | Amazon Technologies, Inc. | Cache optimization |
US9237114B2 (en) | 2009-03-27 | 2016-01-12 | Amazon Technologies, Inc. | Managing resources in resource cache components |
US9246776B2 (en) | 2009-10-02 | 2016-01-26 | Amazon Technologies, Inc. | Forward-based resource delivery network management techniques |
US9253065B2 (en) | 2010-09-28 | 2016-02-02 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US9294391B1 (en) | 2013-06-04 | 2016-03-22 | Amazon Technologies, Inc. | Managing network computing components utilizing request routing |
US9323577B2 (en) | 2012-09-20 | 2016-04-26 | Amazon Technologies, Inc. | Automated profiling of resource usage |
US9332078B2 (en) | 2008-03-31 | 2016-05-03 | Amazon Technologies, Inc. | Locality based content distribution |
US9391949B1 (en) * | 2010-12-03 | 2016-07-12 | Amazon Technologies, Inc. | Request routing processing |
US9407699B2 (en) | 2008-03-31 | 2016-08-02 | Amazon Technologies, Inc. | Content management |
US9407681B1 (en) | 2010-09-28 | 2016-08-02 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US9444759B2 (en) | 2008-11-17 | 2016-09-13 | Amazon Technologies, Inc. | Service provider registration by a content broker |
US9451046B2 (en) | 2008-11-17 | 2016-09-20 | Amazon Technologies, Inc. | Managing CDN registration by a storage provider |
US9479476B2 (en) | 2008-03-31 | 2016-10-25 | Amazon Technologies, Inc. | Processing of DNS queries |
US9495338B1 (en) | 2010-01-28 | 2016-11-15 | Amazon Technologies, Inc. | Content distribution network |
US9497259B1 (en) | 2010-09-28 | 2016-11-15 | Amazon Technologies, Inc. | Point of presence management in request routing |
US9515949B2 (en) | 2008-11-17 | 2016-12-06 | Amazon Technologies, Inc. | Managing content delivery network service providers |
US9525659B1 (en) | 2012-09-04 | 2016-12-20 | Amazon Technologies, Inc. | Request routing utilizing point of presence load information |
US9544394B2 (en) | 2008-03-31 | 2017-01-10 | Amazon Technologies, Inc. | Network resource identification |
US9571389B2 (en) | 2008-03-31 | 2017-02-14 | Amazon Technologies, Inc. | Request routing based on class |
US9590946B2 (en) | 2008-11-17 | 2017-03-07 | Amazon Technologies, Inc. | Managing content delivery network service providers |
US9608957B2 (en) | 2008-06-30 | 2017-03-28 | Amazon Technologies, Inc. | Request routing using network computing components |
US9628554B2 (en) | 2012-02-10 | 2017-04-18 | Amazon Technologies, Inc. | Dynamic content delivery |
US9712484B1 (en) | 2010-09-28 | 2017-07-18 | Amazon Technologies, Inc. | Managing request routing information utilizing client identifiers |
US9734472B2 (en) | 2008-11-17 | 2017-08-15 | Amazon Technologies, Inc. | Request routing utilizing cost information |
US9742795B1 (en) | 2015-09-24 | 2017-08-22 | Amazon Technologies, Inc. | Mitigating network attacks |
US9760528B1 (en) | 2013-03-14 | 2017-09-12 | Glue Networks, Inc. | Methods and systems for creating a network |
US9774619B1 (en) | 2015-09-24 | 2017-09-26 | Amazon Technologies, Inc. | Mitigating network attacks |
US9780965B2 (en) | 2008-05-27 | 2017-10-03 | Glue Networks | Methods and systems for communicating using a virtual private network |
US9785412B1 (en) | 2015-02-27 | 2017-10-10 | Glue Networks, Inc. | Methods and systems for object-oriented modeling of networks |
US9787775B1 (en) | 2010-09-28 | 2017-10-10 | Amazon Technologies, Inc. | Point of presence management in request routing |
US9794281B1 (en) | 2015-09-24 | 2017-10-17 | Amazon Technologies, Inc. | Identifying sources of network attacks |
US9800539B2 (en) | 2010-09-28 | 2017-10-24 | Amazon Technologies, Inc. | Request routing management based on network components |
US9819567B1 (en) | 2015-03-30 | 2017-11-14 | Amazon Technologies, Inc. | Traffic surge management for points of presence |
US9832141B1 (en) | 2015-05-13 | 2017-11-28 | Amazon Technologies, Inc. | Routing based request correlation |
US9888089B2 (en) | 2008-03-31 | 2018-02-06 | Amazon Technologies, Inc. | Client side cache management |
US9887931B1 (en) | 2015-03-30 | 2018-02-06 | 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 |
US9912740B2 (en) | 2008-06-30 | 2018-03-06 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US9930131B2 (en) | 2010-11-22 | 2018-03-27 | Amazon Technologies, Inc. | Request routing processing |
US9928082B1 (en) | 2013-03-19 | 2018-03-27 | Gluware, Inc. | Methods and systems for remote device configuration |
US9954934B2 (en) | 2008-03-31 | 2018-04-24 | Amazon Technologies, Inc. | Content delivery reconciliation |
US9985927B2 (en) | 2008-11-17 | 2018-05-29 | Amazon Technologies, Inc. | Managing content delivery network service providers by a content broker |
US9992086B1 (en) | 2016-08-23 | 2018-06-05 | Amazon Technologies, Inc. | External health checking of virtual private cloud network environments |
US9992303B2 (en) | 2007-06-29 | 2018-06-05 | Amazon Technologies, Inc. | Request routing utilizing client location information |
US10015237B2 (en) | 2010-09-28 | 2018-07-03 | Amazon Technologies, Inc. | Point of presence management in request routing |
US10021179B1 (en) | 2012-02-21 | 2018-07-10 | Amazon Technologies, Inc. | Local resource delivery network |
US10027582B2 (en) | 2007-06-29 | 2018-07-17 | Amazon Technologies, Inc. | Updating routing information based on client location |
US10033627B1 (en) | 2014-12-18 | 2018-07-24 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US10033691B1 (en) | 2016-08-24 | 2018-07-24 | Amazon Technologies, Inc. | Adaptive resolution of domain name requests in virtual private cloud network environments |
US20180219912A1 (en) * | 2017-01-27 | 2018-08-02 | Level 3 Communications, Llc | System and method for scrubbing dns in a telecommunications network to mitigate attacks |
US10049051B1 (en) | 2015-12-11 | 2018-08-14 | Amazon Technologies, Inc. | Reserved cache space in content delivery networks |
US10075551B1 (en) | 2016-06-06 | 2018-09-11 | Amazon Technologies, Inc. | Request management for hierarchical cache |
US10091096B1 (en) | 2014-12-18 | 2018-10-02 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US10097448B1 (en) | 2014-12-18 | 2018-10-09 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US10097566B1 (en) | 2015-07-31 | 2018-10-09 | Amazon Technologies, Inc. | Identifying targets of network attacks |
US10110694B1 (en) | 2016-06-29 | 2018-10-23 | Amazon Technologies, Inc. | Adaptive transfer rate for retrieving content from a server |
CN109167812A (en) * | 2018-08-02 | 2019-01-08 | 网宿科技股份有限公司 | Evaluation services quality, the method for determining adjustable strategies, server and storage medium |
US10205698B1 (en) | 2012-12-19 | 2019-02-12 | Amazon Technologies, Inc. | Source-dependent address resolution |
US10225326B1 (en) | 2015-03-23 | 2019-03-05 | Amazon Technologies, Inc. | Point of presence based data uploading |
US10230819B2 (en) | 2009-03-27 | 2019-03-12 | Amazon Technologies, Inc. | Translation of resource identifiers using popularity information upon client request |
US10257307B1 (en) | 2015-12-11 | 2019-04-09 | Amazon Technologies, Inc. | Reserved cache space in content delivery networks |
US10270878B1 (en) | 2015-11-10 | 2019-04-23 | Amazon Technologies, Inc. | Routing for origin-facing points of presence |
US10348639B2 (en) | 2015-12-18 | 2019-07-09 | Amazon Technologies, Inc. | Use of virtual endpoints to improve data transmission rates |
US10372499B1 (en) | 2016-12-27 | 2019-08-06 | Amazon Technologies, Inc. | Efficient region selection system for executing request-driven code |
US10447648B2 (en) | 2017-06-19 | 2019-10-15 | Amazon Technologies, Inc. | Assignment of a POP to a DNS resolver based on volume of communications over a link between client devices and the POP |
US10469513B2 (en) | 2016-10-05 | 2019-11-05 | Amazon Technologies, Inc. | Encrypted network addresses |
US10503613B1 (en) | 2017-04-21 | 2019-12-10 | Amazon Technologies, Inc. | Efficient serving of resources during server unavailability |
US10521348B2 (en) | 2009-06-16 | 2019-12-31 | Amazon Technologies, Inc. | Managing resources using resource expiration data |
US10592578B1 (en) | 2018-03-07 | 2020-03-17 | Amazon Technologies, Inc. | Predictive content push-enabled content delivery network |
US10601767B2 (en) | 2009-03-27 | 2020-03-24 | Amazon Technologies, Inc. | DNS query processing based on application information |
US10616179B1 (en) | 2015-06-25 | 2020-04-07 | Amazon Technologies, Inc. | Selective routing of domain name system (DNS) requests |
US10623408B1 (en) | 2012-04-02 | 2020-04-14 | Amazon Technologies, Inc. | Context sensitive object management |
US10831549B1 (en) | 2016-12-27 | 2020-11-10 | Amazon Technologies, Inc. | Multi-region request-driven code execution system |
US10862852B1 (en) | 2018-11-16 | 2020-12-08 | Amazon Technologies, Inc. | Resolution of domain name requests in heterogeneous network environments |
US10938884B1 (en) | 2017-01-30 | 2021-03-02 | Amazon Technologies, Inc. | Origin server cloaking using virtual private cloud network environments |
US10958501B1 (en) | 2010-09-28 | 2021-03-23 | Amazon Technologies, Inc. | Request routing information based on client IP groupings |
US11025747B1 (en) | 2018-12-12 | 2021-06-01 | Amazon Technologies, Inc. | Content request pattern-based routing system |
US11075987B1 (en) | 2017-06-12 | 2021-07-27 | Amazon Technologies, Inc. | Load estimating content delivery network |
US11290418B2 (en) | 2017-09-25 | 2022-03-29 | Amazon Technologies, Inc. | Hybrid content request routing system |
US11394683B2 (en) * | 2018-06-04 | 2022-07-19 | Huawei Cloud Computing Technologies Co., Ltd. | Domain name resolution method and apparatus based on a plurality of availability zones AZ |
US11533275B2 (en) * | 2014-12-31 | 2022-12-20 | Samsung Electronics Co., Ltd. | Method and apparatus for allocating server in wireless communication system |
US11604667B2 (en) | 2011-04-27 | 2023-03-14 | Amazon Technologies, Inc. | Optimized deployment based upon customer locality |
Families Citing this family (102)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8121117B1 (en) | 2007-10-01 | 2012-02-21 | F5 Networks, Inc. | Application layer network traffic prioritization |
US20130103556A1 (en) | 2009-06-25 | 2013-04-25 | 3Crowd Technologies, Inc. | Crowd based content delivery |
US20130103785A1 (en) * | 2009-06-25 | 2013-04-25 | 3Crowd Technologies, Inc. | Redirecting content requests |
US8560604B2 (en) | 2009-10-08 | 2013-10-15 | Hola Networks Ltd. | System and method for providing faster and more efficient data communication |
US10721269B1 (en) | 2009-11-06 | 2020-07-21 | F5 Networks, Inc. | Methods and system for returning requests with javascript for clients before passing a request to a server |
US8412832B2 (en) * | 2009-12-23 | 2013-04-02 | Citrix Systems, Inc. | Systems and methods for GSLB MEP connection management across multiple core appliances |
US9503375B1 (en) | 2010-06-30 | 2016-11-22 | F5 Networks, Inc. | Methods for managing traffic in a multi-service environment and devices thereof |
US9420049B1 (en) | 2010-06-30 | 2016-08-16 | F5 Networks, Inc. | Client side human user indicator |
CN102014173B (en) * | 2010-11-01 | 2012-12-26 | 蓝汛网络科技(北京)有限公司 | Domain name redirecting control method, module and system |
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 |
US8879431B2 (en) | 2011-05-16 | 2014-11-04 | F5 Networks, Inc. | Method for load balancing of requests' processing of diameter servers |
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 |
US20130103853A1 (en) | 2011-07-29 | 2013-04-25 | 3Crowd Technologies, Inc. | Directing clients based on communication format |
US9680791B2 (en) | 2011-07-29 | 2017-06-13 | Fortinet, Inc. | Facilitating content accessibility via different communication formats |
US8392576B1 (en) | 2011-09-26 | 2013-03-05 | Google Inc. | Browser based redirection of broken links |
US8504692B1 (en) * | 2011-09-26 | 2013-08-06 | Google Inc. | Browser based redirection of broken links |
US20130097277A1 (en) * | 2011-10-12 | 2013-04-18 | Electronics And Telecommunications Research Institute | Method and apparatus for load balancing of content-centric network |
CN102387201B (en) * | 2011-10-20 | 2015-08-19 | 华为技术有限公司 | The methods, devices and systems of business data processing |
US9210195B2 (en) | 2011-10-20 | 2015-12-08 | Huawei Technologies Co., Ltd. | Method, apparatus, and system for processing service data |
US9313100B1 (en) | 2011-11-14 | 2016-04-12 | Amazon Technologies, Inc. | Remote browsing session management |
CN102668518B (en) * | 2011-12-02 | 2013-10-02 | 华为技术有限公司 | Content distribution network routing method, system, and user terminal |
US9330188B1 (en) | 2011-12-22 | 2016-05-03 | Amazon Technologies, Inc. | Shared browsing sessions |
US9336321B1 (en) | 2012-01-26 | 2016-05-10 | Amazon Technologies, Inc. | Remote browsing and searching |
US8839087B1 (en) | 2012-01-26 | 2014-09-16 | Amazon Technologies, Inc. | Remote browsing and searching |
US10230566B1 (en) | 2012-02-17 | 2019-03-12 | F5 Networks, Inc. | Methods for dynamically constructing a service principal name and devices thereof |
US9020912B1 (en) | 2012-02-20 | 2015-04-28 | F5 Networks, Inc. | Methods for accessing data in a compressed file system and devices thereof |
US9244843B1 (en) | 2012-02-20 | 2016-01-26 | F5 Networks, Inc. | Methods for improving flow cache bandwidth utilization and devices thereof |
US9722851B1 (en) * | 2012-03-27 | 2017-08-01 | Amazon Technologies, Inc. | Optimized retrieval of network resources |
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 |
WO2013163648A2 (en) | 2012-04-27 | 2013-10-31 | F5 Networks, Inc. | Methods for optimizing service of content requests and devices thereof |
US10033837B1 (en) | 2012-09-29 | 2018-07-24 | F5 Networks, Inc. | System and method for utilizing a data reducing module for dictionary compression of encoded data |
US9578090B1 (en) | 2012-11-07 | 2017-02-21 | F5 Networks, Inc. | Methods for provisioning application delivery service and devices thereof |
US10375155B1 (en) | 2013-02-19 | 2019-08-06 | F5 Networks, Inc. | System and method for achieving hardware acceleration for asymmetric flow connections |
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 |
US9578137B1 (en) | 2013-06-13 | 2017-02-21 | Amazon Technologies, Inc. | System for enhancing script execution performance |
US10152463B1 (en) | 2013-06-13 | 2018-12-11 | Amazon Technologies, Inc. | System for profiling page browsing interactions |
CN104427005B (en) * | 2013-08-20 | 2018-01-02 | 阿里巴巴集团控股有限公司 | The method and system that request is accurately dispatched are realized on CDN |
US9241044B2 (en) | 2013-08-28 | 2016-01-19 | Hola Networks, Ltd. | System and method for improving internet communication by using intermediate nodes |
US9998530B2 (en) * | 2013-10-15 | 2018-06-12 | Nicira, Inc. | Distributed global load-balancing system for software-defined data centers |
US10187317B1 (en) | 2013-11-15 | 2019-01-22 | F5 Networks, Inc. | Methods for traffic rate control and devices thereof |
US10694000B2 (en) | 2013-12-02 | 2020-06-23 | Amazon Technologies, Inc. | Browser-based analysis of content request mode performance |
US10237373B2 (en) | 2013-12-02 | 2019-03-19 | Amazon Technologies, Inc. | Performance-based determination of request modes |
US10242322B2 (en) | 2013-12-02 | 2019-03-26 | Amazon Technologies, Inc. | Browser-based selection of content request modes |
CN103763209A (en) * | 2014-01-03 | 2014-04-30 | 上海聚力传媒技术有限公司 | Scheduling method and device of CDN servers |
WO2015105277A1 (en) * | 2014-01-07 | 2015-07-16 | 에스케이플래닛 주식회사 | Apparatus and method for changing alarm information in accordance with weather |
WO2015153738A1 (en) | 2014-04-01 | 2015-10-08 | Merge Healthcare Incorporated | Systems and methods for managing image studies |
US9654587B2 (en) * | 2014-04-16 | 2017-05-16 | Go Daddy Operating Company, LLC | System for location-based website hosting optimization |
CN105100294B (en) * | 2014-05-20 | 2018-05-08 | 阿里巴巴集团控股有限公司 | Obtain method, system, the webserver, browser and the GSLB of webpage |
US11838851B1 (en) | 2014-07-15 | 2023-12-05 | F5, Inc. | Methods for managing L7 traffic classification and devices thereof |
US10182013B1 (en) | 2014-12-01 | 2019-01-15 | F5 Networks, Inc. | Methods for managing progressive image delivery and devices thereof |
US10452619B1 (en) | 2014-12-05 | 2019-10-22 | EMC IP Holding Company LLC | Decreasing a site cache capacity in a distributed file system |
US10423507B1 (en) | 2014-12-05 | 2019-09-24 | EMC IP Holding Company LLC | Repairing a site cache in a distributed file system |
US10951705B1 (en) | 2014-12-05 | 2021-03-16 | EMC IP Holding Company LLC | Write leases for distributed file systems |
US9898477B1 (en) | 2014-12-05 | 2018-02-20 | EMC IP Holding Company LLC | Writing to a site cache in a distributed file system |
US10445296B1 (en) | 2014-12-05 | 2019-10-15 | EMC IP Holding Company LLC | Reading from a site cache in a distributed file system |
US10021212B1 (en) | 2014-12-05 | 2018-07-10 | EMC IP Holding Company LLC | Distributed file systems on content delivery networks |
US10936494B1 (en) | 2014-12-05 | 2021-03-02 | EMC IP Holding Company LLC | Site cache manager for a distributed file system |
US10430385B1 (en) | 2014-12-05 | 2019-10-01 | EMC IP Holding Company LLC | Limited deduplication scope for distributed file systems |
CN105763585A (en) * | 2014-12-17 | 2016-07-13 | 中兴通讯股份有限公司 | Method of implementing data pushing function and GSLB |
US10148727B2 (en) | 2014-12-31 | 2018-12-04 | Vidscale Services, Inc. | Methods and systems for an end-to-end solution to deliver content in a network |
US10091111B2 (en) | 2014-12-31 | 2018-10-02 | Vidscale Services, Inc. | Methods and systems for an end-to-end solution to deliver content in a network |
US11895138B1 (en) | 2015-02-02 | 2024-02-06 | F5, Inc. | Methods for improving web scanner accuracy and devices thereof |
CN106034124B (en) * | 2015-03-17 | 2019-08-23 | 阿里巴巴集团控股有限公司 | A kind of flow statistical method and device |
US10834065B1 (en) | 2015-03-31 | 2020-11-10 | F5 Networks, Inc. | Methods for SSL protected NTLM re-authentication and devices thereof |
CN104811817B (en) * | 2015-04-30 | 2018-04-13 | 北京奇艺世纪科技有限公司 | The method and device of video is played using videoconference client software |
US11350254B1 (en) | 2015-05-05 | 2022-05-31 | F5, Inc. | Methods for enforcing compliance policies and devices thereof |
US10505818B1 (en) | 2015-05-05 | 2019-12-10 | F5 Networks. Inc. | Methods for analyzing and load balancing based on server health and devices thereof |
US11057446B2 (en) | 2015-05-14 | 2021-07-06 | Bright Data Ltd. | System and method for streaming content from multiple servers |
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 |
US11757946B1 (en) | 2015-12-22 | 2023-09-12 | F5, Inc. | Methods for analyzing network traffic and enforcing network policies and devices thereof |
US10404698B1 (en) | 2016-01-15 | 2019-09-03 | F5 Networks, Inc. | Methods for adaptive organization of web application access points in webtops and devices thereof |
US11178150B1 (en) | 2016-01-20 | 2021-11-16 | F5 Networks, Inc. | Methods for enforcing access control list based on managed application and devices thereof |
US10148729B2 (en) * | 2016-03-22 | 2018-12-04 | Go Daddy Operating Company, LLC | Hosting provider hosting routes from a media repository |
CN105975485A (en) * | 2016-04-25 | 2016-09-28 | 乐视控股(北京)有限公司 | Method for accessing CDN by terminal, CDN and terminal |
US11184318B2 (en) * | 2016-09-19 | 2021-11-23 | Wangsu Science & Technology Co., Ltd. | 302 redirecting method, URL generating method and system, and domain-name resolving method and system |
CN111756815B (en) * | 2016-09-19 | 2023-04-07 | 网宿科技股份有限公司 | 302 skipping method, skipping domain name generation method, domain name resolution method and system |
US10412198B1 (en) | 2016-10-27 | 2019-09-10 | F5 Networks, Inc. | Methods for improved transmission control protocol (TCP) performance visibility and devices thereof |
US11063758B1 (en) | 2016-11-01 | 2021-07-13 | F5 Networks, Inc. | Methods for facilitating cipher selection and devices thereof |
US10505792B1 (en) | 2016-11-02 | 2019-12-10 | F5 Networks, Inc. | Methods for facilitating network traffic analytics and devices thereof |
CN108270835B (en) * | 2017-01-03 | 2019-10-22 | 中国移动通信有限公司研究院 | A kind of dispatching method of business tine, device, strategic server and system |
US10536517B2 (en) * | 2017-03-16 | 2020-01-14 | A10 Networks, Inc. | Distributed global server load balancing controllers sharing service delay time |
US10812266B1 (en) | 2017-03-17 | 2020-10-20 | F5 Networks, Inc. | Methods for managing security tokens based on security violations and devices thereof |
US11343237B1 (en) | 2017-05-12 | 2022-05-24 | F5, Inc. | Methods for managing a federated identity environment using security and access control data and devices thereof |
US11122042B1 (en) | 2017-05-12 | 2021-09-14 | F5 Networks, Inc. | Methods for dynamically managing user access control and devices thereof |
CN107071049A (en) * | 2017-05-15 | 2017-08-18 | 复旦大学无锡研究院 | A kind of food security information method of servicing based on Internet of Things |
US10972515B2 (en) * | 2017-07-31 | 2021-04-06 | Verizon Digital Media Services Inc. | Server assisted live stream failover |
CN108702397B (en) * | 2017-08-08 | 2021-07-06 | 达闼机器人有限公司 | Method and system for acquiring and collecting local DNS (Domain name Server) server of client |
US10834230B2 (en) | 2017-08-25 | 2020-11-10 | International Business Machines Corporation | Server request management |
LT3472717T (en) | 2017-08-28 | 2021-01-11 | Luminati Networks Ltd. | Method for improving content fetching by selecting tunnel devices |
US11190374B2 (en) | 2017-08-28 | 2021-11-30 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
CN107613030A (en) * | 2017-11-06 | 2018-01-19 | 网宿科技股份有限公司 | A kind of method and system of processing business request |
US11223689B1 (en) | 2018-01-05 | 2022-01-11 | F5 Networks, Inc. | Methods for multipath transmission control protocol (MPTCP) based session migration and devices thereof |
CN108347481A (en) * | 2018-01-31 | 2018-07-31 | 温州庄吉服饰有限公司 | A kind of remote service security system |
CN110891077A (en) * | 2018-09-07 | 2020-03-17 | 阿里巴巴集团控股有限公司 | CDN node detection method and device |
EP3780557B1 (en) | 2019-02-25 | 2023-02-15 | Bright Data Ltd. | System and method for url fetching retry mechanism |
EP3715966A1 (en) * | 2019-03-29 | 2020-09-30 | Siemens Aktiengesellschaft | Method and system for embedding a web application into a surrounding web application |
EP4030318A1 (en) | 2019-04-02 | 2022-07-20 | Bright Data Ltd. | System and method for managing non-direct url fetching service |
CN110460652B (en) * | 2019-07-26 | 2021-09-14 | 网宿科技股份有限公司 | Resource acquisition method and edge computing scheduling server |
US11729256B2 (en) * | 2021-10-15 | 2023-08-15 | Netflix, Inc. | Predetermining network route for content steering |
Citations (21)
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 |
US20040049579A1 (en) * | 2002-04-10 | 2004-03-11 | International Business Machines Corporation | Capacity-on-demand in distributed computing environments |
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 |
US20040249939A1 (en) * | 2003-05-23 | 2004-12-09 | International Business Machines Corporation | Methods and apparatus for dynamic and optimal server set selection |
US20040267930A1 (en) * | 2003-06-26 | 2004-12-30 | International Business Machines Corporation | Slow-dynamic load balancing method and system |
US20050198309A1 (en) * | 2000-03-20 | 2005-09-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 |
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 |
US20080263180A1 (en) * | 2007-04-19 | 2008-10-23 | Hurst Mark B | Apparatus, system, and method for resilient content acquisition |
US7454500B1 (en) * | 2000-09-26 | 2008-11-18 | Foundry Networks, Inc. | Global server load balancing |
US20090248893A1 (en) * | 2008-03-31 | 2009-10-01 | Richardson David R | Request routing |
US20090327517A1 (en) * | 2008-06-30 | 2009-12-31 | Swaminathan Sivasubramanian | Request routing using network computing components |
US7912954B1 (en) * | 2003-06-27 | 2011-03-22 | Oesterreicher Richard T | System and method for digital media server load balancing |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020065899A1 (en) * | 2000-11-30 | 2002-05-30 | Smith Erik Richard | 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 |
US20020184334A1 (en) * | 2001-06-04 | 2002-12-05 | Cherry Darrel D. | System and method for providing intelligence to network devices |
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 |
US8447876B2 (en) * | 2005-06-02 | 2013-05-21 | Thomson Licensing | Content timing method and system |
US7730187B2 (en) * | 2006-10-05 | 2010-06-01 | Limelight Networks, Inc. | Remote domain name service |
-
2009
- 2009-08-12 US US12/540,127 patent/US20100042743A1/en not_active Abandoned
- 2009-08-12 US US12/540,270 patent/US20100042725A1/en not_active Abandoned
- 2009-08-12 US US12/540,212 patent/US8316085B2/en not_active Expired - Fee Related
- 2009-08-12 US US12/540,234 patent/US8527635B2/en active Active
Patent Citations (22)
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 |
US20050198309A1 (en) * | 2000-03-20 | 2005-09-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 |
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 |
US20040049579A1 (en) * | 2002-04-10 | 2004-03-11 | 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 |
US20040267930A1 (en) * | 2003-06-26 | 2004-12-30 | International Business Machines Corporation | Slow-dynamic load balancing method and system |
US7912954B1 (en) * | 2003-06-27 | 2011-03-22 | Oesterreicher Richard T | System and method for digital media server load balancing |
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 |
US20080263180A1 (en) * | 2007-04-19 | 2008-10-23 | Hurst Mark B | Apparatus, system, and method for resilient content acquisition |
US20090248893A1 (en) * | 2008-03-31 | 2009-10-01 | Richardson David R | Request routing |
US20090327517A1 (en) * | 2008-06-30 | 2009-12-31 | Swaminathan Sivasubramanian | Request routing using network computing components |
Cited By (164)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10027582B2 (en) | 2007-06-29 | 2018-07-17 | Amazon Technologies, Inc. | Updating routing information based on client location |
US9992303B2 (en) | 2007-06-29 | 2018-06-05 | Amazon Technologies, Inc. | Request routing utilizing client location information |
US10645149B2 (en) | 2008-03-31 | 2020-05-05 | Amazon Technologies, Inc. | Content delivery reconciliation |
US9479476B2 (en) | 2008-03-31 | 2016-10-25 | Amazon Technologies, Inc. | Processing of DNS queries |
US10511567B2 (en) | 2008-03-31 | 2019-12-17 | Amazon Technologies, Inc. | Network resource identification |
US11451472B2 (en) | 2008-03-31 | 2022-09-20 | Amazon Technologies, Inc. | Request routing based on class |
US10530874B2 (en) | 2008-03-31 | 2020-01-07 | Amazon Technologies, Inc. | Locality based content distribution |
US11909639B2 (en) | 2008-03-31 | 2024-02-20 | Amazon Technologies, Inc. | Request routing based on class |
US9621660B2 (en) | 2008-03-31 | 2017-04-11 | Amazon Technologies, Inc. | Locality based content distribution |
US9208097B2 (en) | 2008-03-31 | 2015-12-08 | Amazon Technologies, Inc. | Cache optimization |
US10554748B2 (en) | 2008-03-31 | 2020-02-04 | Amazon Technologies, Inc. | Content management |
US9954934B2 (en) | 2008-03-31 | 2018-04-24 | Amazon Technologies, Inc. | Content delivery reconciliation |
US11194719B2 (en) | 2008-03-31 | 2021-12-07 | Amazon Technologies, Inc. | Cache optimization |
US10305797B2 (en) | 2008-03-31 | 2019-05-28 | Amazon Technologies, Inc. | Request routing based on class |
US10797995B2 (en) | 2008-03-31 | 2020-10-06 | Amazon Technologies, Inc. | Request routing based on class |
US9332078B2 (en) | 2008-03-31 | 2016-05-03 | Amazon Technologies, Inc. | Locality based content distribution |
US10158729B2 (en) | 2008-03-31 | 2018-12-18 | Amazon Technologies, Inc. | Locality based content distribution |
US9407699B2 (en) | 2008-03-31 | 2016-08-02 | Amazon Technologies, Inc. | Content management |
US10157135B2 (en) | 2008-03-31 | 2018-12-18 | Amazon Technologies, Inc. | Cache optimization |
US9888089B2 (en) | 2008-03-31 | 2018-02-06 | Amazon Technologies, Inc. | Client side cache management |
US9887915B2 (en) | 2008-03-31 | 2018-02-06 | Amazon Technologies, Inc. | Request routing based on class |
US11245770B2 (en) | 2008-03-31 | 2022-02-08 | Amazon Technologies, Inc. | Locality based content distribution |
US9894168B2 (en) | 2008-03-31 | 2018-02-13 | Amazon Technologies, Inc. | Locality based content distribution |
US10771552B2 (en) | 2008-03-31 | 2020-09-08 | Amazon Technologies, Inc. | Content management |
US9571389B2 (en) | 2008-03-31 | 2017-02-14 | Amazon Technologies, Inc. | Request routing based on class |
US9544394B2 (en) | 2008-03-31 | 2017-01-10 | Amazon Technologies, Inc. | Network resource identification |
US9780965B2 (en) | 2008-05-27 | 2017-10-03 | Glue Networks | Methods and systems for communicating using a virtual private network |
US9912740B2 (en) | 2008-06-30 | 2018-03-06 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US9608957B2 (en) | 2008-06-30 | 2017-03-28 | Amazon Technologies, Inc. | Request routing using network computing components |
US11115500B2 (en) | 2008-11-17 | 2021-09-07 | Amazon Technologies, Inc. | Request routing utilizing client location information |
US10742550B2 (en) | 2008-11-17 | 2020-08-11 | Amazon Technologies, Inc. | Updating routing information based on client location |
US10523783B2 (en) | 2008-11-17 | 2019-12-31 | Amazon Technologies, Inc. | Request routing utilizing client location information |
US9451046B2 (en) | 2008-11-17 | 2016-09-20 | Amazon Technologies, Inc. | Managing CDN registration by a storage provider |
US9590946B2 (en) | 2008-11-17 | 2017-03-07 | Amazon Technologies, Inc. | Managing content delivery network service providers |
US9734472B2 (en) | 2008-11-17 | 2017-08-15 | Amazon Technologies, Inc. | Request routing utilizing cost information |
US9444759B2 (en) | 2008-11-17 | 2016-09-13 | Amazon Technologies, Inc. | Service provider registration by a content broker |
US9985927B2 (en) | 2008-11-17 | 2018-05-29 | Amazon Technologies, Inc. | Managing content delivery network service providers by a content broker |
US11811657B2 (en) | 2008-11-17 | 2023-11-07 | Amazon Technologies, Inc. | Updating routing information based on client location |
US9515949B2 (en) | 2008-11-17 | 2016-12-06 | Amazon Technologies, Inc. | Managing content delivery network service providers |
US10116584B2 (en) | 2008-11-17 | 2018-10-30 | Amazon Technologies, Inc. | Managing content delivery network service providers |
US11283715B2 (en) | 2008-11-17 | 2022-03-22 | Amazon Technologies, Inc. | Updating routing information based on client location |
US9787599B2 (en) | 2008-11-17 | 2017-10-10 | Amazon Technologies, Inc. | Managing content delivery network service providers |
US10491534B2 (en) | 2009-03-27 | 2019-11-26 | Amazon Technologies, Inc. | Managing resources and entries in tracking information in resource cache components |
US9191458B2 (en) | 2009-03-27 | 2015-11-17 | Amazon Technologies, Inc. | Request routing using a popularity identifier at a DNS nameserver |
US10574787B2 (en) | 2009-03-27 | 2020-02-25 | Amazon Technologies, Inc. | Translation of resource identifiers using popularity information upon client request |
US9237114B2 (en) | 2009-03-27 | 2016-01-12 | Amazon Technologies, Inc. | Managing resources in resource cache components |
US10264062B2 (en) | 2009-03-27 | 2019-04-16 | Amazon Technologies, Inc. | Request routing using a popularity identifier to identify a cache component |
US10601767B2 (en) | 2009-03-27 | 2020-03-24 | Amazon Technologies, Inc. | DNS query processing based on application information |
US10230819B2 (en) | 2009-03-27 | 2019-03-12 | Amazon Technologies, Inc. | Translation of resource identifiers using popularity information upon client request |
US10783077B2 (en) | 2009-06-16 | 2020-09-22 | Amazon Technologies, Inc. | Managing resources using resource expiration data |
US10521348B2 (en) | 2009-06-16 | 2019-12-31 | Amazon Technologies, Inc. | Managing resources using resource expiration data |
US10135620B2 (en) | 2009-09-04 | 2018-11-20 | Amazon Technologis, Inc. | Managing secure content in a content delivery network |
US10785037B2 (en) | 2009-09-04 | 2020-09-22 | Amazon Technologies, Inc. | Managing secure content in a content delivery network |
US9712325B2 (en) | 2009-09-04 | 2017-07-18 | Amazon Technologies, Inc. | Managing secure content in a content delivery network |
US9130756B2 (en) | 2009-09-04 | 2015-09-08 | Amazon Technologies, Inc. | Managing secure content in a content delivery network |
US9893957B2 (en) | 2009-10-02 | 2018-02-13 | Amazon Technologies, Inc. | Forward-based resource delivery network management techniques |
US10218584B2 (en) | 2009-10-02 | 2019-02-26 | Amazon Technologies, Inc. | Forward-based resource delivery network management techniques |
US9246776B2 (en) | 2009-10-02 | 2016-01-26 | Amazon Technologies, Inc. | Forward-based resource delivery network management techniques |
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 |
US10506029B2 (en) | 2010-01-28 | 2019-12-10 | Amazon Technologies, Inc. | Content distribution network |
US11205037B2 (en) | 2010-01-28 | 2021-12-21 | Amazon Technologies, Inc. | Content distribution network |
US9787775B1 (en) | 2010-09-28 | 2017-10-10 | Amazon Technologies, Inc. | Point of presence management in request routing |
US10097398B1 (en) | 2010-09-28 | 2018-10-09 | Amazon Technologies, Inc. | Point of presence management in request routing |
US9712484B1 (en) | 2010-09-28 | 2017-07-18 | Amazon Technologies, Inc. | Managing request routing information utilizing client identifiers |
US9497259B1 (en) | 2010-09-28 | 2016-11-15 | Amazon Technologies, Inc. | Point of presence management in request routing |
US10778554B2 (en) | 2010-09-28 | 2020-09-15 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US9407681B1 (en) | 2010-09-28 | 2016-08-02 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US9794216B2 (en) | 2010-09-28 | 2017-10-17 | Amazon Technologies, Inc. | Request routing in a networked environment |
US9191338B2 (en) * | 2010-09-28 | 2015-11-17 | Amazon Technologies, Inc. | Request routing in a networked environment |
US10079742B1 (en) | 2010-09-28 | 2018-09-18 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US9800539B2 (en) | 2010-09-28 | 2017-10-24 | Amazon Technologies, Inc. | Request routing management based on network components |
US10931738B2 (en) | 2010-09-28 | 2021-02-23 | Amazon Technologies, Inc. | Point of presence management in request routing |
US10225322B2 (en) | 2010-09-28 | 2019-03-05 | Amazon Technologies, Inc. | Point of presence management in request routing |
US11632420B2 (en) | 2010-09-28 | 2023-04-18 | Amazon Technologies, Inc. | Point of presence management in request routing |
US11336712B2 (en) | 2010-09-28 | 2022-05-17 | Amazon Technologies, Inc. | Point of presence management in request routing |
US10015237B2 (en) | 2010-09-28 | 2018-07-03 | Amazon Technologies, Inc. | Point of presence management in request routing |
US10958501B1 (en) | 2010-09-28 | 2021-03-23 | Amazon Technologies, Inc. | Request routing information based on client IP groupings |
US11108729B2 (en) | 2010-09-28 | 2021-08-31 | Amazon Technologies, Inc. | Managing request routing information utilizing client identifiers |
US9253065B2 (en) | 2010-09-28 | 2016-02-02 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US20140365666A1 (en) * | 2010-09-28 | 2014-12-11 | Amazon Technologies, Inc. | Request routing in a networked environment |
US8924395B2 (en) | 2010-10-06 | 2014-12-30 | Planet Data Solutions | System and method for indexing electronic discovery data |
US9930131B2 (en) | 2010-11-22 | 2018-03-27 | Amazon Technologies, Inc. | Request routing processing |
US10951725B2 (en) | 2010-11-22 | 2021-03-16 | Amazon Technologies, Inc. | Request routing processing |
US9391949B1 (en) * | 2010-12-03 | 2016-07-12 | Amazon Technologies, Inc. | Request routing processing |
US11604667B2 (en) | 2011-04-27 | 2023-03-14 | Amazon Technologies, Inc. | Optimized deployment based upon customer locality |
US9628554B2 (en) | 2012-02-10 | 2017-04-18 | Amazon Technologies, Inc. | Dynamic content delivery |
US8782279B2 (en) * | 2012-02-15 | 2014-07-15 | Limelight Networks, Inc. | Scaled domain name service |
US20130212300A1 (en) * | 2012-02-15 | 2013-08-15 | Limelight Networks, Inc. | Scaled domain name service |
US10021179B1 (en) | 2012-02-21 | 2018-07-10 | Amazon Technologies, Inc. | Local resource delivery network |
US10623408B1 (en) | 2012-04-02 | 2020-04-14 | Amazon Technologies, Inc. | Context sensitive object management |
US10225362B2 (en) | 2012-06-11 | 2019-03-05 | Amazon Technologies, Inc. | Processing DNS queries to identify pre-processing information |
US11303717B2 (en) | 2012-06-11 | 2022-04-12 | Amazon Technologies, Inc. | Processing DNS queries to identify pre-processing information |
US9154551B1 (en) | 2012-06-11 | 2015-10-06 | Amazon Technologies, Inc. | Processing DNS queries to identify pre-processing information |
US11729294B2 (en) | 2012-06-11 | 2023-08-15 | 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 |
US10015241B2 (en) | 2012-09-20 | 2018-07-03 | Amazon Technologies, Inc. | Automated profiling of resource usage |
US10542079B2 (en) | 2012-09-20 | 2020-01-21 | Amazon Technologies, Inc. | Automated profiling of resource usage |
US9323577B2 (en) | 2012-09-20 | 2016-04-26 | Amazon Technologies, Inc. | Automated profiling of resource usage |
US10645056B2 (en) | 2012-12-19 | 2020-05-05 | Amazon Technologies, Inc. | Source-dependent address resolution |
US10205698B1 (en) | 2012-12-19 | 2019-02-12 | Amazon Technologies, Inc. | Source-dependent address resolution |
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 |
US9929959B2 (en) | 2013-06-04 | 2018-03-27 | Amazon Technologies, Inc. | Managing network computing components utilizing request routing |
US9294391B1 (en) | 2013-06-04 | 2016-03-22 | Amazon Technologies, Inc. | Managing network computing components utilizing request routing |
US10374955B2 (en) | 2013-06-04 | 2019-08-06 | Amazon Technologies, Inc. | Managing network computing components utilizing request routing |
US10097448B1 (en) | 2014-12-18 | 2018-10-09 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US10033627B1 (en) | 2014-12-18 | 2018-07-24 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US11863417B2 (en) | 2014-12-18 | 2024-01-02 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US10091096B1 (en) | 2014-12-18 | 2018-10-02 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US10728133B2 (en) | 2014-12-18 | 2020-07-28 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US11381487B2 (en) | 2014-12-18 | 2022-07-05 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US11533275B2 (en) * | 2014-12-31 | 2022-12-20 | Samsung Electronics Co., Ltd. | Method and apparatus for allocating server in wireless communication system |
US9785412B1 (en) | 2015-02-27 | 2017-10-10 | Glue Networks, Inc. | Methods and systems for object-oriented modeling of networks |
US10225326B1 (en) | 2015-03-23 | 2019-03-05 | Amazon Technologies, Inc. | Point of presence based data uploading |
US11297140B2 (en) | 2015-03-23 | 2022-04-05 | Amazon Technologies, Inc. | Point of presence based data uploading |
US9887932B1 (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 |
US10469355B2 (en) | 2015-03-30 | 2019-11-05 | Amazon Technologies, Inc. | Traffic surge management for points of presence |
US9887931B1 (en) | 2015-03-30 | 2018-02-06 | Amazon Technologies, Inc. | Traffic surge management for points of presence |
US10691752B2 (en) | 2015-05-13 | 2020-06-23 | Amazon Technologies, Inc. | Routing based request correlation |
US10180993B2 (en) | 2015-05-13 | 2019-01-15 | Amazon Technologies, Inc. | Routing based request correlation |
US11461402B2 (en) | 2015-05-13 | 2022-10-04 | Amazon Technologies, Inc. | Routing based request correlation |
US9832141B1 (en) | 2015-05-13 | 2017-11-28 | Amazon Technologies, Inc. | Routing based request correlation |
US10616179B1 (en) | 2015-06-25 | 2020-04-07 | Amazon Technologies, Inc. | Selective routing of domain name system (DNS) requests |
US10097566B1 (en) | 2015-07-31 | 2018-10-09 | Amazon Technologies, Inc. | Identifying targets 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 |
US9794281B1 (en) | 2015-09-24 | 2017-10-17 | Amazon Technologies, Inc. | Identifying sources of network attacks |
US10200402B2 (en) | 2015-09-24 | 2019-02-05 | Amazon Technologies, Inc. | Mitigating network attacks |
US11134134B2 (en) | 2015-11-10 | 2021-09-28 | Amazon Technologies, Inc. | Routing for origin-facing points of presence |
US10270878B1 (en) | 2015-11-10 | 2019-04-23 | Amazon Technologies, Inc. | Routing for origin-facing points of presence |
US10049051B1 (en) | 2015-12-11 | 2018-08-14 | Amazon Technologies, Inc. | Reserved cache space in content delivery networks |
US10257307B1 (en) | 2015-12-11 | 2019-04-09 | Amazon Technologies, Inc. | Reserved cache space in content delivery networks |
US10348639B2 (en) | 2015-12-18 | 2019-07-09 | Amazon Technologies, Inc. | Use of virtual endpoints to improve data transmission rates |
US11463550B2 (en) | 2016-06-06 | 2022-10-04 | Amazon Technologies, Inc. | Request management for hierarchical cache |
US10075551B1 (en) | 2016-06-06 | 2018-09-11 | Amazon Technologies, Inc. | Request management for hierarchical cache |
US10666756B2 (en) | 2016-06-06 | 2020-05-26 | Amazon Technologies, Inc. | Request management for hierarchical cache |
US11457088B2 (en) | 2016-06-29 | 2022-09-27 | Amazon Technologies, Inc. | Adaptive transfer rate for retrieving content from a server |
US10110694B1 (en) | 2016-06-29 | 2018-10-23 | Amazon Technologies, Inc. | Adaptive transfer rate for retrieving content from a server |
US9992086B1 (en) | 2016-08-23 | 2018-06-05 | Amazon Technologies, Inc. | External health checking of virtual private cloud network environments |
US10516590B2 (en) | 2016-08-23 | 2019-12-24 | Amazon Technologies, Inc. | External health checking of virtual private cloud network environments |
US10469442B2 (en) | 2016-08-24 | 2019-11-05 | Amazon Technologies, Inc. | Adaptive resolution of domain name requests in virtual private cloud network environments |
US10033691B1 (en) | 2016-08-24 | 2018-07-24 | Amazon Technologies, Inc. | Adaptive resolution of domain name requests in virtual private cloud network environments |
US11330008B2 (en) | 2016-10-05 | 2022-05-10 | Amazon Technologies, Inc. | Network addresses with encoded DNS-level information |
US10469513B2 (en) | 2016-10-05 | 2019-11-05 | Amazon Technologies, Inc. | Encrypted network addresses |
US10505961B2 (en) | 2016-10-05 | 2019-12-10 | Amazon Technologies, Inc. | Digitally signed network address |
US10616250B2 (en) | 2016-10-05 | 2020-04-07 | Amazon Technologies, Inc. | Network addresses with encoded DNS-level information |
US11762703B2 (en) | 2016-12-27 | 2023-09-19 | Amazon Technologies, Inc. | Multi-region request-driven code execution system |
US10372499B1 (en) | 2016-12-27 | 2019-08-06 | Amazon Technologies, Inc. | Efficient region selection system for executing request-driven code |
US10831549B1 (en) | 2016-12-27 | 2020-11-10 | Amazon Technologies, Inc. | Multi-region request-driven code execution system |
US20180219912A1 (en) * | 2017-01-27 | 2018-08-02 | Level 3 Communications, Llc | System and method for scrubbing dns in a telecommunications network to mitigate attacks |
US11012467B2 (en) * | 2017-01-27 | 2021-05-18 | Level 3 Communications, Llc | System and method for scrubbing DNS in a telecommunications network to mitigate attacks |
US10938884B1 (en) | 2017-01-30 | 2021-03-02 | Amazon Technologies, Inc. | Origin server cloaking using virtual private cloud network environments |
US10503613B1 (en) | 2017-04-21 | 2019-12-10 | Amazon Technologies, Inc. | Efficient serving of resources during server unavailability |
US11075987B1 (en) | 2017-06-12 | 2021-07-27 | Amazon Technologies, Inc. | Load estimating content delivery network |
US10447648B2 (en) | 2017-06-19 | 2019-10-15 | Amazon Technologies, Inc. | Assignment of a POP to a DNS resolver based on volume of communications over a link between client devices and the POP |
US11290418B2 (en) | 2017-09-25 | 2022-03-29 | Amazon Technologies, Inc. | Hybrid content request routing system |
US10592578B1 (en) | 2018-03-07 | 2020-03-17 | Amazon Technologies, Inc. | Predictive content push-enabled content delivery network |
US11394683B2 (en) * | 2018-06-04 | 2022-07-19 | Huawei Cloud Computing Technologies Co., Ltd. | Domain name resolution method and apparatus based on a plurality of availability zones AZ |
CN109167812A (en) * | 2018-08-02 | 2019-01-08 | 网宿科技股份有限公司 | Evaluation services quality, the method for determining adjustable strategies, server and storage medium |
US10862852B1 (en) | 2018-11-16 | 2020-12-08 | Amazon Technologies, Inc. | Resolution of domain name requests in heterogeneous network environments |
US11362986B2 (en) | 2018-11-16 | 2022-06-14 | Amazon Technologies, Inc. | Resolution of domain name requests in heterogeneous network environments |
US11025747B1 (en) | 2018-12-12 | 2021-06-01 | Amazon Technologies, Inc. | Content request pattern-based routing system |
Also Published As
Publication number | Publication date |
---|---|
US20100042724A1 (en) | 2010-02-18 |
US8527635B2 (en) | 2013-09-03 |
US8316085B2 (en) | 2012-11-20 |
US20100042681A1 (en) | 2010-02-18 |
US20100042743A1 (en) | 2010-02-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8527635B2 (en) | Contents delivery system and method, web server and contents provider DNS server thereof | |
US11805184B2 (en) | Content delivery systems and methods | |
US20210021692A1 (en) | Translation of resource identifiers using popularity information upon client request | |
US9800539B2 (en) | Request routing management based on network components | |
US10264062B2 (en) | Request routing using a popularity identifier to identify a cache component | |
US9160703B2 (en) | Request routing management based on network components | |
EP2266064B1 (en) | Request routing | |
US8732309B1 (en) | Request routing utilizing cost information | |
US20100121914A1 (en) | Contents delivery system and method based on content delivery network provider and replication server thereof | |
KR101082362B1 (en) | System and Method for contents delivery, and web server and contents provider DNS server thereof |
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/0984 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 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |