Chunked http video cache routing
AssigneeRamp Holdings, Inc.
InventorRaymond Lau
Life of this patent
Estimating the term…
Abstract
Methods and apparatus, including computer program products, for chunked Hypertext Transfer Protocol (HTTP) video cache routing. A method includes, in a client system linked to at least one arbitrary cache node and a group of interconnected computers that include one or more local cache nodes, the client system including at least a processor and a memory, the memory including a browser, loading a player in the browser, and on the player, playing chunked HTTP video requested from the one arbitrary cache node acting as a master cache node, the master cache node requesting a manifest and modifying the manifest so the requests for the actual video are retrieved by the client system from one of the local cache nodes.
Claims18
A method comprising:
- in a client system linked to at least one arbitrary cache node and a group of interconnected computers that include one or more local cache nodes, the client system including at least a processor and a memory, the memory including a browser, loading a player in the browser;
- and
- on the player, playing chunked HTTP video requested from the one arbitrary cache node acting as a master cache node, the master cache node requesting a manifest and modifying the manifest so the requests for the actual video are retrieved by the client system from one of the local cache nodes.
A method comprising:
- loading a video player into a browser, the browser running in a memory of a user system;
- loading, in the video player, a URI of a chunked HTTP video;
- consulting, in the browser, a PAC file, seeing that the URI matches a domain serving video, and making a request to a master cache node as specified by the PAC file;
- loading, in the browser, a Media Presentation Description (MPD) from the master cache node;
- loading, in the master cache node, a MPD from the Internet;
- modifying, in the master cache node, the manifest to point to the appropriate local cache node depending on the browser's IP address, and returning it to the player in the browser;
- and
- parsing, in the player, the manifest and making subsequent requests for media chunks to the re-written URIs, which now point to a local cache node acting as a reverse proxy.
Dependencies are inferred from the claim text.