WO2011126481A1 - Partial object distribution in content delivery network - Google Patents
Partial object distribution in content delivery network Download PDFInfo
- Publication number
- WO2011126481A1 WO2011126481A1 PCT/US2010/030282 US2010030282W WO2011126481A1 WO 2011126481 A1 WO2011126481 A1 WO 2011126481A1 US 2010030282 W US2010030282 W US 2010030282W WO 2011126481 A1 WO2011126481 A1 WO 2011126481A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- content
- content object
- distribution server
- cdn
- server
- Prior art date
Links
Classifications
-
- 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/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/21—Server components or server architectures
- H04N21/222—Secondary servers, e.g. proxy server, cable television Head-end
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/64—Addressing
- H04N21/6405—Multicasting
Definitions
- CDNs Content delivery networks
- a content provider offloads delivery of its content objects to the CDN.
- the CDN in turn, enables distribution of large volumes of content to end user with a greater reliability and efficiency than would be possible from a centralized distribution system.
- a CDN distribution server detects the availability of a content object and determines whether the content object is a candidate for distribution.
- the distribution server may detect the availability of the content object in response to a provider making new or updated content available at a content site or a location within the CDN.
- the distribution server obtains identifying information for a candidate content object and determines a select portion of the content object to be distributed within the CDN.
- the select portion can be a predetermined number of bytes located at a predetermined position in the content object, the size and location of which may be determined according to content- specific mapping data.
- the distribution server may push the select portion of the content object to one or more CDN edge servers absent an end-user request.
- a method of distributing content in a CDN is disclosed.
- An indication that a content object is available at a first location of the CDN is received at a distribution server.
- the indication may be an event triggered when a new content object or an updated content object is uploaded to a CDN origin server.
- the distribution server can obtain information relating to the content object from the origin server and can determine whether the content object is a candidate for distribution.
- the distribution server can also compare the information relating to the content object with a set of mapping data. If it is determined that the content object is a candidate for distribution, a select portion of the content object can be identified for distribution based on the mapping data.
- the distribution server can retrieve the select portion of the content object from the origin server and can determine a plurality of edge servers to receive the select portion of the content object.
- the select portion of the content object can be sent to the plurality of edge servers in a multicast communication.
- a content distribution server includes a messaging subsystem coupled to a content delivery network (CDN).
- the messaging subsystem may exchange event messages with a plurality of CDN edge servers.
- the content distribution server also includes a memory which may store mapping data or a reference to mapping data available elsewhere in the CDN.
- the mapping data can include content identifiers and byte values corresponding to the content identifiers.
- the content distribution server can include one or more processors that receive event messages from the messaging subsystem indicating that a content object is available at a first location of the CDN.
- the one or more processors can determine whether the content object is a candidate for positioning at edge servers of the CDN and can obtain an identifier associated with the content object.
- the content distribution server can obtain a portion of the content object from the first location.
- the content distribution server can identify a plurality of recipient edge servers and can send the partial content object over the CDN.
- a content delivery system includes a distribution server and a plurality of edge servers that are arranged into one or more multicast groups.
- the distribution server includes a messaging interface which detects the availability of a content object at a first location of the content delivery system. Detecting the availability of the content object may be done without first receiving a request for delivery of the content object.
- the distribution server also includes an object analyzer which determines whether the content object is a candidate for positioning and obtains mapping information associated with the content object. The object analyzer can retrieve a portion of the content object from the first location based on the mapping information when it is determined that the content object is a candidate for positioning.
- the distribution server also includes a multicast group manager for determining a target multicast group to receive the portion of the content object in accordance with content provider information.
- the multicast group manager can send the portion of the content object to the multicast group of edge servers asynchronously with other CDN operations.
- Each edge server in the multicast group may include a request interface for receiving a content request from an end user computer and for sending a requested content object to the end user computer.
- the edge servers may also include a CDN interface for receiving a multicast message that contains the portion of the content object.
- a byte store at each edge server may be configured to store partial content objects.
- the partial content objects may include a number and selection of bytes that varies according to a type of a corresponding full content object.
- a storage controller can add the portion of the content object received from the distribution server to the byte store and can retrieve data from the byte store in response to receiving the content request.
- the storage controller can generate a CDN event if it is determined that the byte store does not contain a partial content object associated with the content request.
- FIG. 1 shows an embodiment of a content distribution system.
- FIG. 2 shows an embodiment of a CDN point of presence.
- FIG. 3 shows an embodiment of a content distribution server.
- FIG. 4 shows exemplary positioning data.
- FIG. 5 shows exemplary mapping data.
- FIG. 6 shows an exemplary multicast message.
- FIG. 7 shows an exemplary process for distributing partial content objects.
- FIG. 8 shows one embodiment of an edge server.
- FIG. 9 shows an exemplary process for maintaining a partial object content store.
- FIG. 10 shows an exemplary process for responding to a content request.
- FIG. 11 shows an exemplary process for reconciling partial object content stores in a multicast edge server group.
- FIG. 1 a block diagram of an embodiment of a content distribution system 100 is shown in which a content originator 106 offloads delivery of content objects to a content delivery network (CDN).
- the content originator 106 produces and/or distributes the content objects and may include content providers 108 as well as content sites 110.
- the CDN delivers the content objects over the internet 104 to end users 128 via end user systems 102.
- the CDN may include an origin server 112, a distribution server (also "control server") 116, and various points of presence (POPs) 120.
- POPs 120 can be deployed throughout content distribution system 100 and may serve content objects to end user systems 102 in a particular geographic area and/or through a particular service provider.
- a POP 120 may be designated to serve content objects to end users 128 in a particular city, on a particular access network, or both, to facilitate efficient delivery and promote a good user experience.
- a content object is any content file or content stream and could include, for example, video, pictures, data, audio, software, and/or text.
- the terms content object, content, content stream, and/or content file may be used
- Origin server 112 includes storage 114 which maintains a copy of the content objects for one or more content providers 108 and may serve as a source of content objects within the CDN.
- elements of the CDN may monitor content sites 110 and may copy new and/or updated content objects to origin server 112 as they become available.
- an end user 128 requests delivery of content through its respective end user system 102
- the request may be passed either directly or indirectly via the internet 104 to a content site 110.
- the end user system 102 could be a personal computer, media player, handheld computer, Internet appliance, phone, IPTV set-top box, streaming radio or any other device that receives and processes content objects.
- the content site 110 could be a web site at which content is viewable with a web browser. Some or all of the content site 110 could also be accessible with application software other than a web browser.
- a content request When a content request is received, it may be redirected from content site 110 to a CDN location. This may involve formulating a delivery path and embedding the delivery path into URLs associated with a web page or some other mechanism.
- a POP 120 Once the request for content is passed to the CDN, it can be assigned to a POP 120 which, in turn, manages delivery of the requested content object to the end user system 102.
- a request for the content object can be propagated toward the core of the CDN and may ultimately be fulfilled from storage 114 at origin server 112.
- the content object is pulled through the CDN to a POP 120 from which it can be distributed to requesting end user systems 102.
- the full content object may be cached at one or more locations between the core CDN and the network edge. Subsequent requests for the content object can be fulfilled from the cached locations.
- Distribution server 116 balances the need to provide rapid delivery of content objects to end users 128 with the need to make efficient use of network resources.
- Distribution server 116 can monitor the state of content objects at origin server 112 and detect when a content provider 108 uploads new or modified content objects to storage 114.
- distribution server 116 may be coupled to a messaging system 118 of the CDN and may receive notifications over WAN 122 when content-related events occur at origin server 112.
- Messaging system 118 for example, can be middleware based on the Advanced Message Queuing Protocol (AMQP).
- CDN messaging can be a publish-and- subscribe, request-response, or some other linkage by which distribution server 116 monitors, detects, and/or is alerted to content related events at origin server 112.
- distribution server 116 performs an analysis to determine whether the change should be reflected in the CDN.
- the determination of whether to act upon events at origin server 112 can be based on requirements of the content provider, the type of content object, geographic considerations, network considerations, end user considerations, or a combination of many factors.
- a content provider 108 may wish to target its content objects to users in a particular geographic area who will access the content in a particular data format using a particular type of software application such as a music player, a video player, a document viewer, etc.
- distribution server 116 may obtain metadata relating to the content object or portions of the content object itself from origin server 112. Using this information, distribution server 116 can determine a partial content object for distribution to POP locations in the CDN.
- the partial content object can include a small number of bytes or other data units determined based on the type of content. For example, if the content object is a Window Media Video (WMV) file, distribution server 116 may select bytes indicative of the codec, frame size, and other attributes relevant to content playback. In some embodiments, distribution server 116 maintains a content-specific mapping by which the position(s) of relevant data units is determined.
- WMV Window Media Video
- distribution server 116 determines where in the CDN it should be distributed. This operation can be performed separately or it can be combined with the determination of whether an event at origin server 112 is actionable. For example, the determination of whether an event is actionable may lead to a further determination of which parts of the CDN are affected. Thus, if Company X wishes to target the Los Angeles market for distribution of content for mobile devices, distribution server 116 may determine both that a new file event relating to Company X content is actionable and that the portion (or portions) of the new content object determined by analysis should be distributed to POPs 120 serving the appropriate geographic area, hardware platform, software platform, etc. [0033] In some embodiments, server 116 sends partial content to POPs 120 in one or more multicast data packets. Note that, unlike request-driven operations, server 116 may push partial content to the POPs 120 in response to events occurring at origin server 112.
- this process can be performed asynchronously to other CDN operations and may avoid the need to pull data (or to simulate a pull) in order to move the partial content to edge locations.
- Edge servers at POPs 120 receive the multicast packets and may add the partial content object(s) to a local data store. Because the multicast packets often include only a few bytes of a content object, partial content objects for an entire content library can be readily maintained in the local data store. Also, scalability in the CDN is preserved as edge servers can be efficiently added, updated, or removed with a minimal impact to CDN operations. Moreover, when a content request is received, the partial content object can be distributed quickly to the requesting end user system 102 and used by client software to prepare for receiving the full content object.
- relevant bytes of a WMV content object can be passed immediately to the end user system for starting the client software, selecting the appropriate codec, resizing the viewer window, updating the file properties, etc. In this way, the perceived responsiveness of the CDN is improved even when the full content object must be retrieved from a remote location.
- POP 120 includes a content request interface 220, an edge server selection function 224, and a plurality of edge servers 230 each with a corresponding content store 232.
- the designated POP 120 receives the content request through a content request interface 220.
- the edge server selection function 224 assigns the request to an edge server 230 which is responsible for sending the content object to the requesting end user system 102.
- the edge server selection function 224 may select an edge server (e.g., 230-2) from a group of edge servers 230 at a POP through domain name service (DNS) resolution, by redirecting the request, or other known mechanisms.
- DNS domain name service
- Various parameters may be taken into account by the edge server selection function 224 in selecting the edge server 230.
- parameters influencing selection of a particular edge server may include content object characteristics, servers assigned to a particular content provider, adequate quality of service (QoS), performance metrics, capabilities of the CDN edge server 230, and/or routing efficiency between the edge server 230 and the end user system 102.
- QoS quality of service
- performance metrics capabilities of the CDN edge server 230
- routing efficiency between the edge server 230 and the end user system 102 may be included in each POP location.
- the selected edge server 230 determines if a partial content object corresponding to the requested content is available in its associated content store 232. If the partial content object is available, it can be sent rapidly to the requestor so that preparations for receiving the full content object can begin and the end user 128 experience is enhanced. As the partial content object is sent, the full content object can be retrieved from one or more caching locations within the POP 120 or otherwise accessible to the selected edge server 230. In this way, the requested content object is distributed to the end user 128 in an efficient, localized manner.
- the requested content object may be retrieved from a remote location.
- the remote location may be the origin server 112 or another CDN server in the same or a different POP 120.
- the requested content object may then be stored in a cache accessible to the selected edge server 230 and distributed to the requesting end user 128.
- the edge server 230 can act as a caching proxy and can pass requests for content objects not available in its multi-layer cache through to the core network.
- the selected edge server 230 may generate an event or otherwise signal to distribution server 116 that its partial object content store 232 needs to be updated.
- its content store 232 may need to be reconciled with the current state of distribution server 116.
- Distribution server 300 can be used in content distribution system 100 and includes a messaging subsystem 310, a content object analyzer 320, and a multicast group manager 350.
- Messaging subsystem 310 can send messages to and receive messages from other elements of the CDN, including origin server 112, POPs 120, and edge servers 230.
- the messages can be generated by middleware using a proprietary or a standardized protocol such as AMQP and may follow a publish-and-subscribe, request- response, or other communications paradigm.
- distribution server 300 subscribes to events at origin server 112 and publishes its events to edge servers 230 through a broker, although many variations are possible within the scope of the present invention.
- Messaging subsystem 310 conveys CDN events of interest to content object analyzer 320.
- CDN events may include a file creation event, a file update event, a policy change event, or other occurrence relating to the positioning and/or distribution of content objects.
- CDN events may include a file creation event, a file update event, a policy change event, or other occurrence relating to the positioning and/or distribution of content objects.
- the origin server file system may generate a file creation event.
- the file creation event can be propagated to distribution server 300 and received by messaging subsystem 310 as a subscriber to content-related file system events.
- distribution server 300 may periodically request updates in accordance with a content provider's distribution policies and receive responses with updated information.
- messaging subsystem 310 notifies content object analyzer 320.
- Content object analyzer 320 may request information about the content object from origin server 112. For example, content object analyzer 320 may request metadata for a new or changed object. In some cases, the metadata is created by the content provider 108 and may include information about the type of file and the policies or business rules applicable to its distribution within the CDN. Alternatively or additionally, content object analyzer 320 may obtain relevant information about the content object by executing a process on a server where the content object is located. For example, the content object analyzer 320 may gather output from a file analysis process that is performed at origin server 112. [0044] Content object analyzer 320 utilizes the content object information to determine whether the content object is a candidate for partial object positioning within the CDN.
- Positioning data 330 may reflect business rules, customer service agreements, and other decisioning data relevant to whether a particular class of objects from a content provider should be distributed and at what CDN location or locations partial object distribution should occur.
- FIG. 4 shows exemplary positioning data 400 such as can be utilized with distribution server 300.
- positioning data 400 is shown as having a tabular format but can be any suitable data structure.
- Provider ID and content location columns can be used to identify content objects for a particular content provider 108 available at a particular content site or CDN location.
- a content type column can be used for associating an entry in positioning data 400 with a particular type of content such as videos, music, e- books, documents, etc.
- Content positioning and multicast group columns may indicate whether the specified content should be positioned in the CDN and, if so, where it should go.
- Content object analyzer 320 matches the information about the new/updated content object to the positioning data 400 and determines whether to take further action. For example, based on the exemplary positioning data, if it is determined that the new/updated content object is a video object uploaded by provider Alpha to location 01, then content object analyzer 320 may determine that a portion of the object should be distributed to multicast groups Ml, M2, M3, and M4. On the other hand, if the new/updated content object was uploaded by provider Beta to location 02, then partial object positioning is not required. As previously noted, decisions regarding partial object positioning in the CDN can be made on the basis of customer agreements, target markets, demand levels, content categories, target computing platforms, or any combination of factors.
- content object analyzer 320 determines which portion (or portions) of the content object should be distributed. This determination can be made on the basis of mapping data 340 maintained at distribution server 300.
- the mapping data 340 can be used to identify relevant portions of the content for extraction by distribution server 300.
- the portions or partial content objects can then be distributed to the multicast groups identified from positioning data 330.
- FIG. 5 shows exemplary mapping data 500 such as can be utilized with distribution server 300.
- mapping data 500 is shown in tabular format but can be any suitable data structure.
- a content ID column includes data corresponding to the type of content object.
- content ID represents file magic information which uniquely identifies a type of the content object (e.g., Doc.L, Video.X, Audio.Q, etc) and may optionally reflect additional information such as container type, audio codec, and/or video codec information.
- the presently described embodiment is not limited to a particular form of content identification.
- Content object analyzer 320 uses the information obtained about the new/updated content object to retrieve an entry from mapping data 340.
- mapping data 340 can specify a number of relevant bytes and a location of the relevant bytes in the content object according to the type of content. Using results from the mapping data, content object analyzer 320 can obtain a partial content object from origin server 112.
- Multicast group manager 350 receives partial content objects and multicast group information from content object analyzer 320 and assembles one or more data packets for transmission to edge servers 230. For insance, using the multicast group information, multicast group manager 350 may transmit data packets containing partial content objects to edge servers 230 at one or more POP 120 locations.
- FIG. 6 shows an exemplary multicast packet 600 such as can be generated by multicast group manager 350.
- multicast packet 600 includes a multicast group address, a sequence ID, a request name, and a partial content object payload.
- the multicast group address may correspond to the multicast group entry in positioning data 330 and can identify edge servers 230 to receive the partial content object payload.
- the sequence ID can represent a current state of distribution server 300 with respect to partial content objects for a particular content collection, a particular origin server, etc. As described below, the sequence ID can be used in a reconciliation or update process with edge servers.
- the content name corresponds to the identifier used by end user systems 102 to request the content object in the CDN and may, for example, be based on the object's URI or some other identifier.
- FIG. 7 is a flowchart illustrating an exemplary process 700 for distributing partial content objects in a CDN.
- Process 700 can be performed by a distribution server 116 operating within a CDN such as shown in FIG. 1.
- process 700 is performed by one or more processors executing program instructions to control the operation of distribution server 300 as such operations are described in connection with FIG. 3.
- the program instructions and data elements may be stored on computer-readable storage medium such as random-access memory (RAM), read-only memory (ROM), flash memory, magnetic storage devices, optical storage devices, and the like.
- a message is received at the distribution server indicating a content object is available at a first location in the CDN.
- the message can be an event or notification triggered in the CDN when a content provider adds new content to an origin server or modifies an existing content object.
- the message can be a response to a content check initiated by the CDN to a location within a customer network.
- the new or updated content can be transferred from the customer network to a location in the CDN.
- the distribution server obtains information about the new or updated content objects.
- the information may include file metadata, identifiers, fingerprints, hashes, and the like.
- the distribution server determines if the content is a candidate for partial object positioning in the CDN. The determination of whether the content is a candidate for positioning can be made by content object analyzer 320 based on criteria from positioning data 330 such as the content provider, the type of content, the location of the content, business rules, or any other combination of factors and placement logic. If it is determined that the content is not a candidate for partial object positioning, the process ends.
- the distribution server determines one or more portions of the content object for distribution.
- the portion (or portions) of the content object are selected by content object analyzer 320 using mapping data 340 such that a number of bytes and a location of the bytes are based on the type of content. Other considerations relevant to end user systems 102, such as the behavior of application software, may also influence selection of the partial content object.
- the distribution server selects one or more multicast groups to receive the partial content object.
- the multicast groups can be selected based on positioning data 330 and may reflect the application of business rules relating to the content provider.
- the distribution server sends the partial content objects to edge servers of the selected multicast groups.
- partial content objects are pushed to edge locations rather than being pulled in response to content requests. Pushing the partial content objects does not require receipt of a content request or a simulated data pull and may be accomplished in a manner that is asynchronous to other CDN operations. By positioning the partial content objects at edge locations, overall user experience can be improved even when the full content object is obtained from other CDN locations.
- FIG. 8 is a functional block diagram of one embodiment of an edge server 800 such as can be located in a POP 120 of content distribution system 100.
- edge server 800 includes a CDN interface 810, a data store controller 820, an optimized partial-object content store 830, and a content request interface 840.
- CDN interface 810 receives multicast packets (such as shown in FIG. 6) from a distribution server and can extract the sequence ID, request name, and partial object payload, or other data elements.
- Data store controller 820 stores the partial object in an optimized content store 830 and updates a local sequence ID with information from the multicast packet.
- the object may be retrieved from content store 830 using a hash based on its URJ or some other identifier.
- data store controller 820 For example, if the multicast packet contains a partial content object consisting of two bytes from VIDEO.FLV, data store controller 820 writes the two byte portion to content store 830 in an entry corresponding to VIDEO.FLV. Data store controller 820 also records the sequence ID of the multicast packets as an indication of the state of the content store 830. Note that the process by which partial objects are added to content store 830 can be asynchronous to other operations of edge server 800 and does not depend upon end user requests. Also, from the CDN standpoint, partial content objects are pushed (not pulled) from the core network to the edge locations.
- Content request interface 840 receives and processes content requests from end user systems. When a request is received, content request interface 840 passes an identifier of the requested object to data store controller 820. Data store controller 820 determines whether a partial content object corresponding to the requested content is available in content store 830. For example, data store controller 820 may attempt to match the requested content to an index of the bytes available in content store 830. If there is a match, controller 820 retrieves the partial object corresponding to the requested content and quickly sends it to the requestor.
- the partial content object can be selected so as to enable the end user system to begin preparations for receiving the full content object by, for example, starting appropriate software, determining the appropriate codecs to use with the content object, adjusting the size and position of a viewer, etc.
- edge server 800 can check whether the requested object is found in one or more caching layers of the CDN. Caching layers can be arranged in relation to the various POPs 120 so as to hold content objects near the CDN edge thereby maximizing their availability. If the requested object is not found in the caching layers, it can be retrieved from the appropriate origin server and retained in one or more intermediate caching levels for responding to subsequent requests. In this situation, edge server 800 acts as a pass-through device in the delivery content from locations within the CDN to the end user system.
- Edge server 800 can also signal, either directly or indirectly, to a distribution server 116 that a partial content object for requested content was not available in its content store 830.
- edge server 800 includes a messaging system 118 by which it is linked to distribution server 116 and other elements of the CDN. Using the messaging system, data store controller 820 can trigger an event when a partial object is not available in content store 830, and distribution server 116 can respond to the event by performing a reconciliation process as described herein. Alternatively, distribution server 116 may monitor events at the CDN caching levels to determine when reconciliation of the particular edge server 800 or multicast group is appropriate.
- FIG. 9 is a flowchart showing an exemplary process 900 for maintaining a partial object content store.
- Process 900 can be performed by an edge server 230 operating within a CDN such as content delivery system 100 shown in FIG. 1.
- process 900 is performed by one or more processors executing program instructions to direct the operations of edge server 800 as described in FIG. 8.
- the program instructions and data elements may be stored on a computer-readable storage medium such as random-access memory (RAM), read-only memory (ROM), flash memory, one or more magnetic storage devices, optical storage devices, and the like.
- the edge server receives a multicast data packet that contains a partial content object.
- the data packet can be similar to multicast packet 600 and may include various identifiers with partial content bytes.
- the edge server extracts the identifiers and relevant bytes of the content object and records them in its content store. This may include associating the name of the content object with the relevant bytes and updating a sequence identifier for the partial object content store.
- the partial content object is available for distribution from the edge server to end user systems.
- FIG. 10 is a flowchart showing an exemplary process 1000 for responding to a content request.
- Process 1000 can be performed by an edge server operating within a CDN such as content delivery system 100 shown in FIG. 1.
- process 1000 is performed by one or more processors executing program instructions to direct the operations of edge server 800 as described in FIG. 8.
- the program instructions and data elements may be stored on a computer-readable storage medium such as random-access memory (RAM), read-only memory (ROM), flash memory, magnetic storage devices, optical storage devices, and the like.
- a request for a content object is received at the edge server.
- the request may be directed to the edge server as part of an edge server selection function 224 at a POP location 120 as shown in FIG. 2.
- the edge server determines whether a partial object is available for the requested content. This may include searching a content store for an entry corresponding to the requested content. If an entry is found, block 1050, the edge server sends the content-specific bytes from its content store to the end user system from which the content request was received.
- the edge server may send a message on the CDN messaging system to indicate that it was not able to provide a partial content object. As indicated by block 1040, the message may accompany a search for the requested content at different caching levels and/or parts of the CDN. Once a determination is made regarding the partial content object, a check is made for the availability of the full content object at the edge location at block 1060. If the content object is not available at the edge, it is requested from other CDN storage and, at block 1070, the edge server sends the requested object to the end user system.
- FIG. 11 is a flowchart of an exemplary process 1 100 for reconciling partial object content stores for a multicast edge server group.
- Process 1100 can be carried out by a distribution server 300, such as shown in FIG. 3, and can involve one or more processors executing program instructions.
- the program instructions can be stored with appropriate data elements on a computer-readable storage medium as previously described.
- an edge server event is detected.
- the event may be received from the CDN messaging system when a partial content object is not available at an edge location or it may be triggered when an edge server requests content from a CDN location such as a deeper caching level or another POP location.
- the distribution server requests content store identifiers from edge servers belonging to a same multicast group as the edge server to which the event relates. For example, the distribution server may perform a lookup on the edge server address to obtain a multicast group address and then send a status request to the group address.
- the distribution server can determine which partial content objects to distribute.
- the distribution server matches a sequence ID in each response to a current sequence ID and sends a partial content update, block 1140, to individual edge servers via the edge server selection process according to the status of the respective content stores. For example, if a single edge server is taken offline and requires an update after being returned to service, the distribution server can send update packets to the edge server selection process at its point of presence.
- the distribution server determines a lowest sequence ID from the edge server responses and sends update packets to the entire multicast group based on the lowest common denominator.
- an edge server When an edge server receives the multicast update packets, it retrieves the partial content payload and updates entries in its local content store accordingly. In this way, by operation of the distribution server, the local content store at one or more edge locations is reconciled with the most recent collection of partial content distributed within the CDN.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Information Transfer Between Computers (AREA)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/US2010/030282 WO2011126481A1 (en) | 2010-04-07 | 2010-04-07 | Partial object distribution in content delivery network |
CN2010800670094A CN103109511A (en) | 2010-04-07 | 2010-04-07 | Partial object distribution in content delivery network |
BR112012025582A BR112012025582A2 (en) | 2010-04-07 | 2010-04-07 | partial object distribution in content delivery network |
EP10849586.2A EP2556481A4 (en) | 2010-04-07 | 2010-04-07 | Partial object distribution in content delivery network |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/US2010/030282 WO2011126481A1 (en) | 2010-04-07 | 2010-04-07 | Partial object distribution in content delivery network |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011126481A1 true WO2011126481A1 (en) | 2011-10-13 |
Family
ID=44763190
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2010/030282 WO2011126481A1 (en) | 2010-04-07 | 2010-04-07 | Partial object distribution in content delivery network |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP2556481A4 (en) |
CN (1) | CN103109511A (en) |
BR (1) | BR112012025582A2 (en) |
WO (1) | WO2011126481A1 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8892686B1 (en) | 2013-12-19 | 2014-11-18 | Limelight Networks, Inc. | Dynamic content transformation for multiple devices |
US9948550B2 (en) | 2013-06-08 | 2018-04-17 | Huawei Technologies Co., Ltd. | Method, apparatus, and system for routing and forwarding |
US10693858B2 (en) | 2015-07-31 | 2020-06-23 | Huawei Technologies Co., Ltd. | CDN-based access control method and related device |
WO2021138051A1 (en) * | 2019-12-31 | 2021-07-08 | Paypal, Inc. | Geographic location consensus determination |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2874372A1 (en) * | 2013-11-14 | 2015-05-20 | Alcatel Lucent | Delivering managed and unmanaged content across a network |
CN106063200B (en) * | 2013-12-09 | 2019-11-01 | 华为技术有限公司 | A kind of device for content caching, method |
CN104717231B (en) * | 2014-12-18 | 2019-01-25 | 北京蓝汛通信技术有限责任公司 | The pre- distribution processing method and device of content distributing network |
US10735515B2 (en) * | 2017-05-22 | 2020-08-04 | Massachusetts Institute Of Technology | Layered distributed storage system and techniques for edge computing systems |
CN107450974A (en) * | 2017-08-15 | 2017-12-08 | 北京云端智度科技有限公司 | A kind of method of tasks carrying management in CDN system |
CN107483614B (en) * | 2017-08-31 | 2021-01-22 | 京东方科技集团股份有限公司 | Content scheduling method and communication network based on CDN (content delivery network) and P2P network |
CN109669679B (en) * | 2018-12-28 | 2022-04-29 | 北京微播视界科技有限公司 | Service detection and processing method and device and electronic equipment |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20010088742A (en) * | 2001-08-28 | 2001-09-28 | 문의선 | Parallel Information Delievery Method Based on Peer-to-Peer Enabled Distributed Computing Technology |
JP2002032280A (en) | 2000-07-13 | 2002-01-31 | Ism Consulting Firm Kk | Service system and method for distributing contents and software via distributed server and information storage medium |
US20030004947A1 (en) * | 2001-06-28 | 2003-01-02 | Sun Microsystems, Inc. | Method, system, and program for managing files in a file system |
KR20030068475A (en) * | 2002-02-14 | 2003-08-21 | 마츠시타 덴끼 산교 가부시키가이샤 | Content distribution system |
US20080001791A1 (en) | 2006-06-30 | 2008-01-03 | Omneon Video Networks | Transcoding for a distributed file system |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010051980A1 (en) * | 2000-06-01 | 2001-12-13 | Raciborski Nathan F. | Preloading content objects on content exchanges |
JP2004533738A (en) * | 2001-03-02 | 2004-11-04 | カセンナ インコーポレイテッド | A metadata-enabled push-pull model for efficiently distributing video content over networks with low latency |
US8763062B2 (en) * | 2006-10-30 | 2014-06-24 | Alcatel Lucent | Method and apparatus for controlling information available from content distribution points |
-
2010
- 2010-04-07 CN CN2010800670094A patent/CN103109511A/en active Pending
- 2010-04-07 EP EP10849586.2A patent/EP2556481A4/en not_active Withdrawn
- 2010-04-07 BR BR112012025582A patent/BR112012025582A2/en not_active IP Right Cessation
- 2010-04-07 WO PCT/US2010/030282 patent/WO2011126481A1/en active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002032280A (en) | 2000-07-13 | 2002-01-31 | Ism Consulting Firm Kk | Service system and method for distributing contents and software via distributed server and information storage medium |
US20030004947A1 (en) * | 2001-06-28 | 2003-01-02 | Sun Microsystems, Inc. | Method, system, and program for managing files in a file system |
KR20010088742A (en) * | 2001-08-28 | 2001-09-28 | 문의선 | Parallel Information Delievery Method Based on Peer-to-Peer Enabled Distributed Computing Technology |
KR20030068475A (en) * | 2002-02-14 | 2003-08-21 | 마츠시타 덴끼 산교 가부시키가이샤 | Content distribution system |
US20080001791A1 (en) | 2006-06-30 | 2008-01-03 | Omneon Video Networks | Transcoding for a distributed file system |
Non-Patent Citations (1)
Title |
---|
See also references of EP2556481A4 |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9948550B2 (en) | 2013-06-08 | 2018-04-17 | Huawei Technologies Co., Ltd. | Method, apparatus, and system for routing and forwarding |
US8892686B1 (en) | 2013-12-19 | 2014-11-18 | Limelight Networks, Inc. | Dynamic content transformation for multiple devices |
US10693858B2 (en) | 2015-07-31 | 2020-06-23 | Huawei Technologies Co., Ltd. | CDN-based access control method and related device |
WO2021138051A1 (en) * | 2019-12-31 | 2021-07-08 | Paypal, Inc. | Geographic location consensus determination |
US11699140B2 (en) | 2019-12-31 | 2023-07-11 | Paypal, Inc. | Geographic location consensus determination |
Also Published As
Publication number | Publication date |
---|---|
EP2556481A1 (en) | 2013-02-13 |
EP2556481A4 (en) | 2013-12-04 |
CN103109511A (en) | 2013-05-15 |
BR112012025582A2 (en) | 2019-09-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8090863B2 (en) | Partial object distribution in content delivery network | |
WO2011126481A1 (en) | Partial object distribution in content delivery network | |
US10616301B2 (en) | Request-based encoding for streaming content portions | |
US11089129B2 (en) | Accelerated network delivery of channelized content | |
US9185158B2 (en) | Content delivery in a network | |
US11729249B2 (en) | Network address resolution | |
CN105049466B (en) | Method of processing content objects | |
CN109791557B (en) | Computer-implemented method for managing asset storage and storage system | |
US10200490B2 (en) | Content-based redirection | |
JP2017536606A (en) | Long tail content processing in content distribution networks | |
JP2008529157A (en) | System architecture and method for scheduled download service | |
Antunes et al. | NDNrel: A mechanism based on relations among objects to improve the performance of NDN |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201080067009.4 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10849586 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010849586 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112012025582 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 112012025582 Country of ref document: BR Kind code of ref document: A2 Effective date: 20121005 |