Abstract: Described herein is an end-to-end solution (i.e., capable of constructing a content delivery network all the way from an origin server to end user devices) which provides a managerial overview to what has been a very disjoint build-out of networks. In the past, networks have evolved to serve particular needs, as opposed to being architected from a strategic view. What this does is to allow someone (e.g., content provider, network operator, etc.) to impose a strategy over those networks. Rather than having to construct solutions that deliver a particular kind of content, a particular security requirement, a particular latency requirement, etc., one can simply provision particular types of nodes as needed when needed.

Abstract: Methods and devices are described for generating a recipe for creating a clip. A clip request may be received at a server, such as a content server. The clip request may be related to a clip including audio and/or video. The server may include one or more processors and a cache, the cache including chunks. Each chunk may store a predetermined positive number of bytes of data. The server may search the cache to determine whether the clip is to be generated from a recipe stored within the cache. The recipe may include one or more tasks. The server may generate the clip in view of the one or more tasks of the recipe. The server may transmit a clip response comprising the clip to the client device.

Abstract: Methods and devices are described for generating a recipe for creating a clip. A recipe request can be received at a server, such as a recipe server. The recipe request may be related to a clip including audio and/or video. The server can generate a recipe for creating the clip using one or more slices of a data source. The recipe can include one or more tasks that can include a data-source task which can include a specification of the data source and slice definitions for the one or more slices. The data source can include a video and/or audio data source. A slice definition can include a slice value and a slice offset for locating a respective slice within the data source. The recipe can then be transmitted from the server.

Abstract: Described herein is an end-to-end solution (i.e., capable of constructing a content delivery network all the way from an origin server to end user devices) which provides a managerial overview to what has been a very disjoint build-out of networks. In the past, networks have evolved to serve particular needs, as opposed to being architected from a strategic view. What this does is to allow someone (e.g., content provider, network operator, etc.) to impose a strategy over those networks. Rather than having to construct solutions that deliver a particular kind of content, a particular security requirement, a particular latency requirement, etc., one can simply provision particular types of nodes as needed when needed.

Abstract: Apparatus and devices are described for generating clips by executing one or more tasks contained in a recipe. The recipe can be received at a server, such as a content server, perhaps as part of a clip request. The server can generate a clip by parsing the recipe. Parsing the recipe can include determining whether a given task of the one or more tasks is a data-source task and, in response to determining that the given task is a data-source task, extracting one or more slices of data from a data source specified in the data-source task and adding the one or more slices to the clip. The data source can include a video data source or a combined video and audio data source. Once generated, the clip can be sent from the server.