System and method for hybrid push-based streaming

Number: 10009659
Published: 2018-06-26
Filed: 2016-03-31
Assignee: DISNEY ENTERPRISES, INC.
Inventors: Reisner; Samuel J.
CPC: H04N21/2353; H04L67/141; H04N21/2393; H04L67/02; H04N21/8456; H04N21/812; H04N21/26258; H04L67/55; H04N21/8126; H04N21/8455; H04L67/06; H04N21/6125; H04N21/4351; H04N21/4882; H04N21/2385
Verdict: Set aside hybrid push-based streaming plumbing
Source: Google Patents · FreePatentsOnline

Abstract

Methods and systems for hybrid push-based media streaming of encoded video (or media) content grouped into video segment (or chunk) files to one or more user devices are described, where push notices are provided from a manifest server to subscribing user devices over a persistent low bandwidth connection when the video segment files are ready to be viewed. The video segment files may be downloaded by the user devices from segment servers to the user devices via a separate HTTP high bandwidth streaming connection, or other form of separate connection. In addition, unique, personalized, or additional content may be inserted in the push notices and viewed by the user devices without impacting video playback performance.

Background

BACKGROUND(1) It is common practice for computer-based servers to digitally stream media content (e.g., video, music, text, graphics, and the like), live or on-demand, to electronic devices, such as mobile smartphones, tablets and the like, for viewing by a user. Such media content is often provided to the user devices (or clients) via the internet using a distributed network of computer-based data file servers deployed in one or more data centers, also referred to as a content delivery network or content distribution network (collectively, CDN). A typical CDN structure may be a hierarchical tree format, where if a client requests digital media content or asset from a nearby edge node and that node does not have the asset, it goes to its parent node and the like, until it finds the desired asset. Once a client has requested an asset from a node, the asset remains available for some period of time at that node for future clients, thereby providing an efficient file delivery web architecture.(2) HTTP-based streaming methods, such as HLS (HTTP-based Live Media Streaming communication protocol), supported or implemented by products made by companies such as Apple, Inc., HDS (HTTP Dynamic Streaming), supported or implemented by products made by companies such as Adobe, Inc., and DASH (Dynamic Adaptive bit-rate Streaming over HTTP) or MPEG-DASH, are commonly used for streaming media content and operate using “HTTP-based streaming,” where media content is stored in segments or “chun

Claims

1. A method for a user device to receive streaming encoded video content grouped into segment video files, comprising: establishing a low-bandwidth persistent manifest connection between the user device and a manifest server; receiving at the user device from the manifest server, a push notice that a next video segment file in a segment server is available for viewing, the push notice being received via the persistent manifest connection, wherein the push notice comprises a manifest pointer indicative of the next video segment file in the segment server; updating a user device local manifest file with the manifest pointer from the push notice; downloading to the user device, via a segment delivery connection between the user device and the segment server, separate from the persistent manifest connection, the next video segment file from the segment server, for playing on the user device; playing the next segment file on the user device; and wherein the user device does not receive any manifest file or playlist. 18. A method for streaming encoded video content grouped into segment video files to at least one user device, comprising: establishing a persistent low-bandwidth manifest connection between the at least one user device and a manifest server; sending to the user device from the manifest server, a push notice that a next video segment file in a segment server is available for viewing, the push notice being sent via the persistent manifest connection, wherein the push notice comprises a manifest pointer indicative of the next video segment file in the segment server; building a local manifest file within the user device using the manifest pointer from the push notice; downloading to the user device, via a segment delivery connection between the user device and the segment server, separate from the persistent manifest connection, the next video segment file from the segment server, for playing on the user device; and wherein the user device does not receive any manifest file or playlist.