WO2014025972A2 - Architecture scindée entre points de présence - Google Patents

Architecture scindée entre points de présence Download PDF

Info

Publication number
WO2014025972A2
WO2014025972A2 PCT/US2013/054086 US2013054086W WO2014025972A2 WO 2014025972 A2 WO2014025972 A2 WO 2014025972A2 US 2013054086 W US2013054086 W US 2013054086W WO 2014025972 A2 WO2014025972 A2 WO 2014025972A2
Authority
WO
WIPO (PCT)
Prior art keywords
content
pop
pops
cdn
recited
Prior art date
Application number
PCT/US2013/054086
Other languages
English (en)
Other versions
WO2014025972A3 (fr
Inventor
Ofir Ehrlich
Dima Potekhin
Tomer Altman
Leonid Fainberg
Gil Shai
Ofer Gadish
Jason Hoffman
Jason Wolfe
Amitay Dobo
Original Assignee
Limelight Networks, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US13/571,320 external-priority patent/US8356074B1/en
Priority claimed from US13/571,318 external-priority patent/US8612588B1/en
Application filed by Limelight Networks, Inc. filed Critical Limelight Networks, Inc.
Publication of WO2014025972A2 publication Critical patent/WO2014025972A2/fr
Publication of WO2014025972A3 publication Critical patent/WO2014025972A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/957—Browsing optimisation, e.g. caching or content distillation
    • G06F16/9574—Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching

Definitions

  • This disclosure relates in general to content delivery networks and, but not by way of limitation, to accelerating web page delivery.
  • CDNs Content Delivery Networks
  • POPs points of presence
  • DNS domain name service
  • Anycast Anycast
  • An edge server in the POP will serve up the content from its cache, a host within the CDN or an origin server depending on where the content is located. For content that is missing from the CDN, the request to the origin server can be costly in terms of QoS.
  • a system and method for accelerating web page delivery is disclosed in one embodiment.
  • Web content requests are made to an edge server of a first point of presence (POP) of a content delivery network (CDN).
  • the web content has embedded resource links.
  • the first POP can rewrite the embedded resource links to route requests for the embedded resource links to any POP in the CDN or even the origin server.
  • the first POP can decide if the first POP and/or another POP referenced in a rewritten embedded resource link should cache and/or accelerate the resource referenced in the embedded resource link.
  • a CDN having a plurality of POPs includes one or more processor for executing instructions and one or more storage media for retaining instructions.
  • the instructions perform several things such as: receiving a request for web content at a first POP from an end user for content stored on an origin server, wherein: the web content includes a plurality of resource links, the first POP is part of the plurality of POPs, and the first POP comprises: an front- end optimization engine, and a front-end cache; identifying a second POP that is located closer to the origin server than the first POP, wherein: the second POP is part of the plurality of POPs, and the second POP comprises: a back-end optimization engine, and a back-end cache; and rewriting a resource link of the plurality of resource links of the web content, wherein the rewritten resource link is changed to reference the second POP, another POP from the plurality of POPs or the origin server.
  • a CDN having a plurality of POPs for delivering third party content to end users and including a first POP and a second POP.
  • the first POP receives a request for web content from an end user for content stored on an origin server.
  • the web content includes a plurality of resource links.
  • the first POP is part of the plurality of POPs.
  • the first POP includes a front- end optimization engine, and a front-end cache.
  • the second POP is located closer to the origin server than the first POP.
  • the second POP is part of the plurality of POPs.
  • the second POP includes a back-end optimization engine, a back-end cache and a decision engine.
  • the decision engine rewrites a resource link of the plurality of resource links of the web content.
  • the rewritten resource link is changed to reference the second POP, another POP from the plurality of POPs or the origin server.
  • a method for accelerating delivery of third party content using a CDN having a plurality of POPs is disclosed.
  • a request for web content is received at a first POP from an end user for content stored on an origin server.
  • the web content includes a plurality of resource links.
  • the first POP is part of the plurality of POPs.
  • the first POP includes an front-end optimization engine, and a front-end cache.
  • a second POP is identified that is located closer to the origin server than the first POP.
  • the second POP is part of the plurality of POPs.
  • the second POP includes a back-end optimization engine, and a back-end cache.
  • a resource link of the plurality of resource links of the web content is rewritten. The rewritten resource link is changed to reference the second POP, another POP from the plurality of POPs or the origin server.
  • the present disclosure provides a system and method for accelerating web page delivery.
  • Web requests are made to an edge server of a first point of presence (POP) of a content delivery network (CDN).
  • the web content can be cached at the edge server in the first POP. Where the cache is missing the web content, it is queried from a second POP determined to be closer to the origin server for the web content.
  • the second POP can have its own cache or request the web content from the origin server. Only missing components from the web content are passed to the first POP. Additionally, the missing components can be compressed.
  • a method for accelerating content delivery using a CDN comprised of a plurality of POPs is disclosed.
  • a content request for content is received at a first POP of the plurality of POPs.
  • the content request includes a universal resource indicator (URI). It is determined if the content is cached in the first POP. Based upon an outcome of the determination: determining a second POP is closer to an origin of the content than the first POP and requesting the content from the second POP. It is determined if the content is stored in the second POP.
  • URI universal resource indicator
  • the abbreviated content is passed from the second POP to the first POP.
  • the content is reconstituted at the first POP using the abbreviated content and the similar content.
  • the content is returned according to the content request.
  • a CDN for accelerating content movement internally within the CDN.
  • the CDN includes one or more processors, and one or memories coupled with the one or more processors.
  • the one or more processors and one or more memories are configured to: receive a content request for content at a first point of presence (POPs), which is part of a plurality of POPs, wherein the content request includes a universal resource indicator (URI); determine if the content is cached in the first POP; based upon the outcome of the preceding determining limitation: determine a second POP, which is part of the plurality of POPs, is closer to an origin of the content than the first POP, and request the content from the second POP; determine if the content is stored in the second POP;
  • POPs point of presence
  • URI universal resource indicator
  • a CDN for accelerating content movement internally within the CDN which is comprised of a plurality of POPs.
  • the CDN includes a first, second, and third POPs.
  • the third POP is in a third geographic location, wherein the third POP is part of the plurality of POPs.
  • the first POP in a first geographic location, wherein the first POP is part of the plurality of POPs.
  • the first POP receives a content request for content, which include a universal resource indicator (URI). A determination is made if the content is cached in the first POP.
  • the second POP is located in a second geographic location, wherein the second POP is part of the plurality of POPs.
  • the first, second and third geographic locations are all different. A determination is made to decide that the second POP is closer to an origin of the content than either the first or third POP.
  • the content is requested by the first POP from the second POP. It is determined if the content is stored in the second POP. Differential coding is performed the content to produce abbreviated content based upon similar content stored at the first POP.
  • the abbreviated content is passed from the second POP to the first POP.
  • the content is reconstituted at the first POP using the abbreviated content and the similar content.
  • the content is returned by the first POP according to the content request.
  • FIG. 1 depicts a block diagram of an embodiment of a content distribution system
  • FIGs. 2A and 2B depict block diagrams of embodiments of web delivery system
  • FIG. 3 depicts a block diagram of an embodiment of a point of presence (POP);
  • FIG. 4 depicts a block diagram of an embodiment of an edge server
  • FIG. 5 illustrates a swim diagram of an embodiment of a process for accelerated delivery of web content
  • FIG. 6 illustrates a flowchart of an embodiment of a process for updating the mapping of origin server domains to POPs of the content delivery network (CDN).
  • FIG. 7 illustrates a swim diagram of another embodiment of a process for delivery of web content with optional caching and acceleration.
  • FIG. 1 a block diagram of an embodiment of a content distribution system 100 is shown where a content originator 106 offloads delivery of the content objects to a content delivery network (CDN) 110.
  • CDN content delivery network
  • the content distribution system 100 can dynamically and efficiently serve content objects (e.g., Javascript applets, images, Hypertext Markup Language (HTML), videos, Flash animations, etc.) over the Internet 104 to end user systems 102 by an efficient use of caches and acceleration within the CDN 110.
  • content objects e.g., Javascript applets, images, Hypertext Markup Language (HTML), videos, Flash animations, etc.
  • content objects used frequently on a webpage may be provided to user quickly even if the content object is dynamic.
  • Caching by domain, sub-domain, origin server, IP address at a point of presence (POP) 120 near the content originator allows accumulation of different variations of dynamic content is a way that caching at an edge server is unlikely to achieve.
  • POP point of presence
  • An end user 128 may request a set of content object, e.g., by requesting a webpage associated with one or more of content objects.
  • a user may request a file, such as a HTML file.
  • the HTML file may include dynamic content that is customized for some or groups of end users 128.
  • a source of each of the content objects and/or the file may be on an edge server, a host server within the CDN, the origin server 112, the content site 116, or on a cache in another POP 120.
  • differential (“diff ') coding, delta coding and/or compression can be used to reduce the transportation cost and delay associated with transferring the content object or portion of a content object missing from the POP 120.
  • a content originator 106 produces and/or distributes content objects as the originator of content in a digital form for distribution with the Internet 104. Included in the content originator 106 are a content provider 108, a content site 116 and an origin server 112. The figure shows a single origin server 112, but it is to be understood embodiments could have multiple origin servers 112 that each can serve streams of the content object redundantly. For example, the content originator 106 could have multiple origin servers 112 and assign any number of them to serve the content object. The origin servers 112 for a given content site 116 could be widely distributed with some even being hosted by the CDN 110.
  • the content object is any content file or content stream and could include, for example, video, pictures, advertisements, applet, data, audio, software, HTTP content, and/or text.
  • the content object could be live, delayed or stored.
  • references may be made to a content object, content, and/or content file, but it is to be understood that those terms could be generally used interchangeably wherever they may appear.
  • Some content is dynamic in that different end users 128 get different variations of the content, such that the dynamic content is not easily cached at the edge with the variations being pushed out of the cache before they might be requested again.
  • CDN 110 uses the CDN 110 to deliver the content objects over the Internet 104 to end users 128.
  • the CDN 110 may retrieve the content object from the content provider 108 for loading in a cache or hosting for a period of time.
  • the content provider 108 may directly provide the content object to the CDN 110 for hosting, i.e., in advance of the first request or in servicing the first request.
  • the content objects are provided to the CDN 110 through caching and/or pre-population algorithms and stored in one or more servers such that requests may be served from the CDN 110.
  • the origin server 112 holds a copy of each content object for the content originator 106.
  • the contents of the origin server 112 may be reconciled with the CDNs 110 through a cache and/or pre-population algorithm. Some embodiments could populate the CDN 110 with content objects without having an accessible origin server such that the CDN serves as the origin server, a host or a mirror.
  • the CDN 110 can store entire content objects or portions of content objects.
  • the CDN 110 includes a number of points of presence (POPs) 120, which are geographically distributed through the content distribution system 100. Various embodiments may have any number of POPs 120 within the CDN 110 that are generally distributed in various locations around the Internet 104 to be proximate, in a network quality of service (QoS) sense, to end user systems 102.
  • POPs points of presence
  • QoS network quality of service
  • a wide area network (WAN), the Internet 104 and/or other backbone may couple the POPs 120 with each other and also couple the POPs 120 with other parts of the CDN 110.
  • Other embodiments could couple POPs 120 together with the Internet 104 optionally using encrypted tunneling.
  • the request for the content is passed either directly or indirectly via the Internet 104 to the content originator 106.
  • the request for content could be an HTTP Get command sent to an IP address of the content originator 106 after a look-up that finds the IP address.
  • the content originator 106 is the source or re- distributor of content objects.
  • the content site 116 is accessed through a content web site 116 in this embodiment by the end user system 102.
  • the content site 116 could be a web site where the content is viewable by a web browser.
  • the content site 116 could be accessible with application software other than a web browser.
  • the content provider 108 can redirect content requests to any CDN 110 after they are made or can formulate the delivery path beforehand when the web page is formulated to point to the CDN 110. In any event, the request for content is handed over to the CDN 110 for fulfillment in this embodiment.
  • the request is associated with a particular POP 120 within the CDN 110.
  • a routing algorithm used to choose between different POPs 120 could be based upon efficiency, randomness, and/or proximity in Internet-terms, defined by the fabric of the Internet and/or some other mechanism. Other embodiments could find a POP 120 close to the end user system 124 using domain name service (DNS) diversion, redirection, Anycast and/or other techniques.
  • DNS domain name service
  • the particular POP 120 then assigns or routes the request to an edge server.
  • the particular POP 120 may retrieve the portion of the content object from the content provider 108.
  • the content provider 108 may directly provide the content object to the CDN 110 and its associated POPs 120, i.e., in advance of the first request.
  • the content objects are provided to the CDN 110 and stored in one or more CDN servers such that the portion of the requested content may be served from the CDN 110.
  • the origin server 112 holds one copy of each content object for the content originator 106. Periodically, the content of the origin server 112 may be reconciled with the CDN 110 through a cache, hosting and/or pre-population algorithm.
  • An edge server serving the request to the end user system 124 may access the requested content - either by locally retrieving part or all of the content or requesting it from another server.
  • the edge server determines a source for part or all of the requested content within the CDN 110 by querying other peer servers within or remote from the particular POP 120.
  • This embodiment dynamically discovers peer servers, which have already cached or stored the requested content.
  • the peer server that already holds the requested content could be an edge server or a server that doesn't service end user requests, for example, a relay server or ingest server. If part or all of the content cannot be found in the POP 120 originally receiving the request, neighboring POPs 120 could serve as the source in some cases, or the content could be sourced from the content originator 106.
  • a request from an end user system 102 for content may result in requests for content from one or more servers in the CDN 110.
  • a CDN server e.g., an edge server, peer servers, an origin server, etc.
  • requested content objects e.g., requested HTML files
  • the end user system 102 processes the content for the end user 128 upon receipt of the content object.
  • the end user system 102 could be a personal computer, media player, handheld computer Internet appliance, phone, IPTV set top, streaming radio or any other device that can receive and play content objects.
  • a number of end user systems 102 can be networked together sharing a single connection to the Internet 104. Changes could be made by the CDN 110 that does not affect the end user realization of the content except to speed delivery.
  • FIG. 2A a block diagram of an embodiment of web delivery system 200-1 is shown.
  • POPs 120 all interconnected by a network 204 that may include both private WAN or Internet 104 elements to allow communication between the POPs 120.
  • This embodiment uses the CDN 110 to accelerate delivery of content objects by caching content sites and origin servers at a first POP 120-1 nearby for all the other POPs that might request content objects associated with the content site 116 and/or origin server.
  • the end user system 124 requests a content object and has the request assigned to an eighth POP 120-8.
  • the eighth POP 120-8 would determine a POP assigned to each domain, sub-domain, IP address, or other portion of the HTTP request to divide the requests between the various POPs 120.
  • Other embodiments could use a variable or field in the HTTP request to assign HTTP requests to a particular POP 120 nearby the origin server 112 or content site 116.
  • the content site could be at a domain of ACME.gov that is assigned to the first POP 120-1.
  • a server in the first POP 120 would provide the requested content from its cache and retrieve the content object from the content site 116 upon a cache miss.
  • the first POP 120-1 will receive request from all POPs 120 in the CDN 110 for a given assigned domain.
  • the cache in the first POP 120-1 will populate with the full spectrum of requests for the assigned domain.
  • Compression algorithms, diff coding and/or delta coding is used between the frontend POP 120-8 and backend POP 120-1 to more efficiently use the network 204.
  • FIG. 2B a block diagram of an embodiment of web delivery system 200-2 is shown.
  • an end user system 124 is assigned to the sixth POP 120-6 of the CDN 110.
  • a given HTTP request is for a content site 116 that is assigned a third POP 120-3 for fulfillment of those requests.
  • Certain portions of the HTTP file may call for content objects stored on the origin server 112 that is assigned to a first POP 120-1. In this way, the fulfillment duties can be spread out among the POPs 120.
  • This embodiment assigns origin servers 112 and content sites 116 according to an algorithm that chooses from among the POPs according to the one with the lowest latency, but other embodiments could make that choice based upon a function of latency, bandwidth, bandwidth cost, POP resources,
  • POP loading server resources, server loading, cache size, cache speed, and/or any other factor that affects quality of service (QoS).
  • a block diagram of an embodiment of a POP 120 is shown.
  • a number of edge servers 330 are used to perform various functions in the POP 120.
  • the edge servers 330 are hardware computers that can have one or more different functions instantiated for performing the various functions of the POP 120.
  • the instantiations can be scaled up and down as different services are requested from the POP 120.
  • the services offered include content hosting, content caching, web acceleration, compression, video and/or audio streaming, domain name service, cloud computing, gaming hosting, flash engines, encoding, etc.
  • a particular edge server 330 can have several instantiations of the same or different services running simultaneously.
  • the edge servers 330 support web acceleration between POPs 120.
  • the edge server 330 rewrites the URLs or links in web pages to refer to another POP closer to the source of the content requested in the URL.
  • the origin POP mapping store 350 is queried to find the POP that will intermediate requesting the HTTP. Should the origin POP mapping store 350 not have an entry for the domain, the POPs 120 can probe for quick accessibility to the origin server for the domain.
  • algorithms or databases could be used to estimate the location of the domain to select a nearby POP. In this way, one POP is near the end user 128 and the other is near the origin server or content site for the HTTP universal resource locator (URL).
  • the switching fabric 340 routes information within the POP 120.
  • assignment of requests is performed by the switching fabric 340 using load balancing, round robin, random or another scheme to divide the processing between the edge servers 330 configured to perform a particular task.
  • the switching fabric 340 can redirect or reroute the request to another POP.
  • the assigned edge server 330 can rewrite the links in the web page to reference the POP closer to the end user system 124.
  • Some URLs are not rewritable, such as those generated by JavascriptTM, that have unique variables or coding specific to an end user or that are required to be in a certain format for whatever reason.
  • the edge server 330 can recognize those circumstances such that the edge server 330 would not rewrite the URL and would instead directly contact the content site or origin site without a hop through another POP. Additionally, the edge server 330 recognizes when the current POP is both the closest to the end user 128 and the source of the content. The edge server 330 could directly contact the content source or the edge server 330 in the same POP that handles web caching for that domain. It could be the same edge server 330.
  • FIG. 4 a block diagram of an embodiment of an edge server 330 running both ends of the interPOP acceleration in a split architecture is shown. It is to be understood that the functions of the frontend edge server 330 and the backend edge server 330 could be instantiated on the same or different physical hardware servers.
  • a requesting function 480 is performed in a frontend POP 120 and a fulfillment function 490 is performed in a backend POP 120.
  • the requesting function 480 includes an HTTP decompression engine 450, an HTTP edge cache 430, a HTTP request server 440, frontend acceleration engine 405, and a hash function 470.
  • the fulfillment function 490 includes a HTTP compression engine 460, an origin request engine 420, a back-end acceleration engine 415, and an origin cache 410.
  • the HTTP request server 440 receives the connection from the end user system 124.
  • the content specified in the URL could be stored in the frontend edge server 330.
  • the HTTP request server 440 analyzes the request to characterize the web page and embedded links for various conditions. Table II shows examples of the different conditions that are screened for. Once a condition is recognized, split processing is specified. For example, if the HTTP request server finds that the HTML being requested is dynamic and possibly unique to the end user 128, the split processing condition specified by the HTTP request server 440 is non-cacheable
  • Table III shows what functions are involved with a given split processing condition.
  • the split processing defines whether a backend POP 120 will be involved and where caching and acceleration is performed.
  • the HTTP request server 440 can also define if two-level caching is performed with frontend cache using backend caching as a parent cache and whether compression is used between the frontend and backend POPs 120. In this manner, caching, acceleration and/or interPOP compression can be specified on an individual web page or link basis.
  • the edge cache 430 is queried for content corresponding to the URL or similar URLs.
  • Content items in the edge cache 430 are indexed by a hash of the content item itself.
  • the content cached can be HTTP, an entire file, a portion of 5 a file, a function, a piece of run-time code, etc.
  • a hash function 470 performs a hash of the content items stored in the edge cache 430 and the edge cache 430 is indexed by hash.
  • Acceleration techniques speed the user experience. Many acceleration techniques rewrite web sites on the fly, that is to say after their request. To achieve0 the acceleration, links can be rewritten, HTML can be abbreviated or rewritten to run more efficiently, scripts and HTML can be rewritten or reordered.
  • the frontend POP can turn on or off acceleration in either the frontend and/or the backend POP 120. In some embodiments, individual acceleration techniques can be selectively turned on and off for each web page request or link. 5 [0042] For content not found in the edge cache 430, the URL is optionally passed to the fulfillment function 490 in the backend POP determined by reference to the origin POP mapping store 350.
  • Hashes for the content items found in the edge cache 430 are added to the URL so that the origin request engine 420 knows what content items are stored in the edge cache 430.
  • the origin request engine 420 checks the origin0 cache to see if the content item is stored in the POP 120. Where the content item is not found locally, the origin server 112 or content site 116 can be queried for the content item.
  • the origin request engine 420 can do a diff or delta function to determine only the unique components using the HTTP compression engine 460.
  • the compressed item is passed to the HTTP decompression engine 450 with information on how to reconstitute the content item.
  • the changed information found through diff or delta coding can be further compressed using algorithms that find patterns and redundancies to further reduce the size.
  • link layer and/or persistent compression at higher layers can be performed on all content passing interPOP.
  • the HTTP request server 440 stores the reconstituted content item after using the hash function to find a hash used to create an index for the edge cache.
  • the reconstituted content item is passed to the end user system 124 that made the initial request.
  • two-level caching is used to accelerate content delivery in one embodiment.
  • the connection between the frontend POP 120 and the backend POP 120 could be over the Internet 104, a private or leased-line WAN 320 or an encrypted tunnel over the Internet 104 in various embodiments.
  • Both the frontend and backend POPs can perform web page acceleration.
  • This acceleration is an accumulation of processing techniques to optimize the end user experience when viewing web pages.
  • the most interesting content in the web page is sped up using a number of techniques. These techniques can optimize different portions of the delivery chain, for example, the back-end acceleration engine
  • the HTTP request server specifies various processing by adding information and rearranging links.
  • the backend POP 120 could be specified as a subdomain in the UR1 and whether caching is performed specified in a variable in the rewritten link. Links are passed between functions in a given POP 120 or between POPs 120. Other embodiments could use a signaling channel separate from the link to specify the processing. Some embodiments could specify specific caching parameters, acceleration techniques and compression parameters in the rewritten links.
  • FIG. 5 a swim diagram of an embodiment of a process 500 for accelerated delivery of web content is shown.
  • the depicted portion of the process begins in block 504 where the requesting function 480 in a frontend POP 120 receives a HTTP request in the form of a URL or link.
  • the URL has been rewritten to point to a domain of the CDN 110.
  • the frontend POP 120 is chosen because it is nearby, in an Internet sense, to the end user system 124.
  • the HTTP request server 440 checks for the content item in the edge cache 430. Where the content item is found, it is returned to the end user system 124 in block 516.
  • the hashes for the similar content items are retrieved from the cache are retrieved from the edge cache in block 512.
  • the backend POP 120 is determined in block 520.
  • the HTTP request is sent with embedded hashes in block 524.
  • the fulfillment function 490 receives the HTTP request and checks the origin cache 410 for the content item in block 528. Where the content item is found, processing continues to block 544 where diff or delta coding is used to only return the unique portions of the content item. Optional compression of those differences is performed in block 548.
  • the processed content item is passed to HTTP request server 440 for reconstitution in block 552.
  • the content item is hashed with the hash function 470.
  • the content item is stored in the edge cache 430 in block 560.
  • the content item is returned to the end user system. Blocks 556 and 560 can be performed after returning the content item in block 516.
  • processing continues to block 532 where the content is requested from the origin server 112 or content site 116.
  • the content is located and returned to the backend POP 120 in block 540.
  • the fulfillment function 490 hashes the content item and updates the origin cache 410 in block 542.
  • Diff or delta coding is performed in block 544 and processing continues as outlined above to update the edge cache 430 and deliver the content item to the end user system.
  • FIG. 6 a flowchart of an embodiment of a sub-process 520 for updating the mapping of origin server domains to POPs of the CDN 110 is shown.
  • the domain or other source indicator is searched for in the origin POP mapping store 350. If found in block 608, the resulting POP is returned in block 612. Where there is no backend POP 120 in the origin POP mapping store 350, processing goes from block 608 to block 616 to cause all the POPs to test their connection to the domain.
  • the results are collected in block 620 to determine the backend POP in block 624.
  • the result is returned to the HTTP request server 440 in block 612.
  • the origin POP mapping store 350 is updated in block 628.
  • FIG. 7 a swim diagram of another embodiment of a process 700 for delivery of web content with optional caching and acceleration is shown.
  • This embodiment details the different types of caching and acceleration that can be specified for a web page or link.
  • the depicted portion of the process 700 begins in block 504 where a frontend POP 120 receives a HTTP request.
  • the location of the DNS or DNS cache used by the end user system 124 often defines which frontend POP 120 will be initially chosen as an approximation of the location of the end user system 124, but that premise can often be wrong such that a POP 120 is used that is not close.
  • the IP address of the end user system 124 can be used to determine if the wrong POP was initially chosen and where that is the case the request can be routed, redirected or just have the links rewritten to the correct POP 120 in block 716.
  • conditions in the web page are analyzed to determine the split architecture processing.
  • the link(s) are rewritten to specify the caching and acceleration to be performed in specified POPs.
  • a frontend POP 120 might be specified for caching the content without using acceleration after a determination that acceleration is unlikely to aid the end user experience.
  • processing continues to block 520 to retrieve the content and optionally acceleration in block 720 before returning the content in block 516.
  • a backend POP 120 should be used. Where the backend POP 120 is not used, the content can be directly gathered from the origin server in blocks 536 and 540 before it is returned in block 516. Where the frontend POP 120 decides to use a backend POP 120, processing can go to block 728 for retrieval of the content from the origin cache 410 and on a cache miss, requesting the content from the origin in blocks 532, 536, 540. The content found at the origin is updated into the cache in block 732. Optional acceleration is performed in block 736 before returning the content to the frontend POP 120.
  • Implementation of the techniques, blocks, steps and means described above may be done in various ways. For example, these techniques, blocks, steps and means may be implemented in hardware, software, or a combination thereof.
  • the processing units may be implemented within one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described above, and/or a combination thereof.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • processors controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described above, and/or a combination thereof.
  • the embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a swim diagram, a data flow diagram, a structure diagram, or a block diagram. Although a depiction may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged.
  • a process is terminated when its operations are completed, but could have additional steps not included in the figure.
  • a process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination corresponds to a return of the function to the calling function or the main function.
  • embodiments may be implemented by hardware, software, scripting languages, firmware, middleware, microcode, hardware description languages, and/or any combination thereof.
  • the program code or code segments to perform the necessary tasks may be stored in a machine readable medium such as a storage medium.
  • a code segment or machine-executable instruction may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a script, a class, or any combination of instructions, data structures, and/or program statements.
  • a code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, and/or memory contents.
  • Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.
  • the methodologies may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. Any machine-readable medium tangibly embodying instructions may be used in implementing the methodologies described herein.
  • software codes may be stored in a memory.
  • Memory may be implemented within the processor or external to the processor.
  • the term "memory" refers to any type of long term, short term, volatile, nonvolatile, or other storage medium and is not to be limited to any particular type of memory or number of memories, or type of media upon which memory is stored.
  • the term “storage medium” may represent one or more memories for storing data, including read only memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage mediums, optical storage mediums, flash memory devices and/or other machine readable mediums for storing information.
  • ROM read only memory
  • RAM random access memory
  • magnetic RAM magnetic RAM
  • core memory magnetic disk storage mediums
  • optical storage mediums flash memory devices and/or other machine readable mediums for storing information.
  • machine -readable medium includes, but is not limited to portable or fixed storage devices, optical storage devices, and/or various other storage mediums capable of storing that contain or carry instruction(s) and/or data.

Abstract

Un mode de réalisation de l'invention porte sur un système et un procédé pour accélérer une distribution de page web. Des requêtes de contenu web sont faites à un serveur de bordure d'un premier point de présence (POP) d'un réseau de distribution de contenu (CDN). Le contenu web comporte des liens vers des ressources incorporées. Le premier POP peut réécrire les liens vers des ressources incorporées pour router des requêtes pour les liens vers des ressources incorporées vers n'importe quel POP dans le CND ou même le serveur d'origine. Selon certains modes de réalisation, le premier POP peut décider si le premier POP et/ou un autre POP référencé dans un lien vers une ressource incorporée réécrit devrait mettre en cache et/ou accélérer la ressource référencée dans le lien vers la ressource incorporée.
PCT/US2013/054086 2012-08-09 2013-08-08 Architecture scindée entre points de présence WO2014025972A2 (fr)

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US13/571,320 US8356074B1 (en) 2012-08-09 2012-08-09 Inter point of presence split architecture
US13/571,318 US8612588B1 (en) 2012-08-09 2012-08-09 Point of presence to point of presence web page compression
US13/571,320 2012-08-09
US13/571,318 2012-08-09
US13/741,051 2013-01-14
US13/741,051 US8984056B2 (en) 2012-08-09 2013-01-14 Inter point of presence split architecture

Publications (2)

Publication Number Publication Date
WO2014025972A2 true WO2014025972A2 (fr) 2014-02-13
WO2014025972A3 WO2014025972A3 (fr) 2014-04-17

Family

ID=50068706

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2013/054086 WO2014025972A2 (fr) 2012-08-09 2013-08-08 Architecture scindée entre points de présence

Country Status (1)

Country Link
WO (1) WO2014025972A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017205782A1 (fr) * 2016-05-27 2017-11-30 Home Box Office, Inc. Structure de mémoire cache à plusieurs niveaux

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5884098A (en) * 1996-04-18 1999-03-16 Emc Corporation RAID controller system utilizing front end and back end caching systems including communication path connecting two caching systems and synchronizing allocation of blocks in caching systems
US7337248B1 (en) * 2004-03-19 2008-02-26 Sun Microsystems, Inc. Adaptive synchronization method for communication in storage systems
US20110082982A1 (en) * 2009-10-02 2011-04-07 Limelight Networks, Inc. Content delivery network cache grouping
US20110276446A1 (en) * 2010-05-04 2011-11-10 Aryaka Networks, Inc., Heterogeneous service provider model through pay-for-performance based transit settlements
US20110302321A1 (en) * 2000-04-17 2011-12-08 Mark Vange Data redirection system and method therefor

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5884098A (en) * 1996-04-18 1999-03-16 Emc Corporation RAID controller system utilizing front end and back end caching systems including communication path connecting two caching systems and synchronizing allocation of blocks in caching systems
US20110302321A1 (en) * 2000-04-17 2011-12-08 Mark Vange Data redirection system and method therefor
US7337248B1 (en) * 2004-03-19 2008-02-26 Sun Microsystems, Inc. Adaptive synchronization method for communication in storage systems
US20110082982A1 (en) * 2009-10-02 2011-04-07 Limelight Networks, Inc. Content delivery network cache grouping
US20110276446A1 (en) * 2010-05-04 2011-11-10 Aryaka Networks, Inc., Heterogeneous service provider model through pay-for-performance based transit settlements

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017205782A1 (fr) * 2016-05-27 2017-11-30 Home Box Office, Inc. Structure de mémoire cache à plusieurs niveaux
US10404823B2 (en) 2016-05-27 2019-09-03 Home Box Office, Inc. Multitier cache framework
US11146654B2 (en) 2016-05-27 2021-10-12 Home Box Office, Inc. Multitier cache framework

Also Published As

Publication number Publication date
WO2014025972A3 (fr) 2014-04-17

Similar Documents

Publication Publication Date Title
US8984056B2 (en) Inter point of presence split architecture
US8612588B1 (en) Point of presence to point of presence web page compression
US11805184B2 (en) Content delivery systems and methods
US10567287B2 (en) System and methods for efficient media delivery using cache
US8621042B2 (en) Anycast redirect to unicast content download
US8112471B2 (en) System and method for website performance optimization and internet traffic processing
EP2897340B1 (fr) Proxy de routage pour diffusion en flux adaptative
US10904205B2 (en) Content delivery network optimization system
US9350821B2 (en) End-to end acceleration of dynamic content
US8224986B1 (en) Methods and apparatus for redirecting requests for content
US8645494B1 (en) Two-file preloading for browser-based web acceleration
KR20120083903A (ko) 더 빠르고 더 효율적인 데이터 통신을 제공하는 시스템 및 방법
US20140280677A1 (en) Two-file preloading for browser-based web acceleration
US11159642B2 (en) Site and page specific resource prioritization
US20170041422A1 (en) Method and system for retrieving a content manifest in a network
US10075553B1 (en) Systems and methods for automatically rewriting network page code
US20200314208A1 (en) Server-side resource prioritization
US20160285961A1 (en) Delivering managed and unmanaged content across a network
US20180302489A1 (en) Architecture for proactively providing bundled content items to client devices
WO2014025972A2 (fr) Architecture scindée entre points de présence
WO2012091694A1 (fr) Redirection d'envoi à la cantonade vers un téléchargement de contenu à diffusion unique
TW201528806A (zh) 提供多媒體內容之內容部分至用戶端之方法及對應之快取
CN112491963A (zh) 数据传输方法、装置、设备及可读存储介质
CN110036607B (zh) 用于在内容分发网络中动态汇集资源的方法和请求路由器
KR20070003920A (ko) 캐시 서버 네트워크 및 콘텐츠 파일의 분배를 스케쥴링하는방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13827450

Country of ref document: EP

Kind code of ref document: A2

122 Ep: pct application non-entry in european phase

Ref document number: 13827450

Country of ref document: EP

Kind code of ref document: A2