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. An apparatus, comprising:
a hardware processor;
computer memory holding computer program code executed by the hardware processor, the computer program code configured for delivery of video content as a set of Hypertext Transfer Protocol (HTTP) byte range requests, the computer program code comprising:
first program code configured as an HTTP proxy; and
second program code;
wherein the second program code is configured to accept a request from the HTTP proxy, the request associated with an end user player, and in response, to dynamically generate a manifest, the manifest identifying a set of content fragments represented by the HTTP byte range requests; and
wherein the HTTP proxy performs partial object caching (POC) of the set of content fragments and interacts with a translation process to selectively fetch and deliver the manifest, and to selectively deliver the content fragments upon subsequent receipt from the end user player of individual HTTP byte range requests for the content fragments.
2. The apparatus as described in claim 1 wherein the HTTP proxy and the second program code communicate with one another over a localhost connection and a shared memory.
3. The apparatus as described in claim 1 wherein the manifest comprises a multi-bit rate (MBR) manifest that includes bit rate information for a set of distinct bit rates.
4. The apparatus as described in claim 1 wherein the HTTP proxy obtains the set of content fragments from a network-accessible location.
5. The apparatus as described in claim 1 wherein the HTTP proxy is configured to obtain at least one content fragment upon a POC cache miss.
6. The apparatus as described in claim 1 wherein the HTTP proxy dynamically re-assembles the set of content fragments and serves the video content via HTTP.
7. The apparatus as described in claim 1 wherein the manifest is associated with at least one index identifying the content fragments.
8. The apparatus as described in claim 1 wherein the HTTP proxy translates at least one content fragment from a first format to a second format.
9. The apparatus as described in claim 8 wherein the second format is mp4/f4v.