HTTP-based stream delivery
Stream delivery within a content delivery network (CDN) includes recording the stream using a recording tier, and playing the stream using a player tier. Recording begins when the stream is received in a source format. The stream is then converted into an intermediate format (IF), which comprises a stream manifest, one or more fragment indexes (FI), and a set of IF fragments. A player process begins when a requesting client is associated with a CDN HTTP proxy. In response to receipt at the proxy of a request for the stream, the HTTP proxy retrieves (either from the archive or the data store) the stream manifest and at least one fragment index. Using the fragment index, the IF fragments are retrieved to the HTTP proxy, converted to a target format, and then served in response to the client request. Preferably, fragments are accessed, cached and served by the proxy via HTTP.
1. A content delivery system associated with an origin that supports delivery of a content object as a set of Hypertext Transfer Protocol (HTTP) byte range requests, comprising:
a player tier; and
a translation tier positioned downstream from the origin and upstream from the player tier, the translation tier comprising a network-accessible machine configured for on-demand delivery of video content;
the network-accessible machine comprising an HTTP proxy, and a translator process coupled to the HTTP proxy over a localhost connection within the network accessible machine, the translator process configured to accept requests from the HTTP proxy over the localhost connection, the requests associated with a request for the video content received at the player tier and, in response, to on-the-fly generate a manifest, an index and a set of content fragments that collectively comprise a delivery format uniquely associated with the content delivery system, wherein the HTTP proxy performs partial object caching (POC) of fragments of the content object obtained from the origin and interacts with the translator process via a shared memory and using a stream cache process to selectively fetch and deliver to the player tier the manifest, the index and the set of content fragments.
2. The system as described in claim 1 wherein the delivery format uniquely associated with the content delivery system is a fragmented MP4 format.
3. The system as described in claim 2 wherein the delivery format comprises the manifest, a set of one or more fragment indexes comprising the index, and the set of fragments, fragment in the set identified by a fragment number and comprising a header and a payload.
4. The system as described in claim 3 wherein the manifest comprises metadata, and information about the one or more fragment indexes.
5. The system as described in claim 4 wherein a index comprises information identifying a key frame associated with a given time slice, a key frame-to-fragment number mapping, a key frame-to-time mapping, and a key frame-to-byte offset in a key frame-to-fragment number mapping.