Browse Prior Art Database

WEBRTC AS A PROTOCOL FOR STREAMING IN-HOME MEDIA FROM SOURCES OTHER THAN FROM CAPTURE DEVICES

IP.com Disclosure Number: IPCOM000246085D
Publication Date: 2016-May-03
Document File: 8 page(s) / 121K

Publishing Venue

The IP.com Prior Art Database

Related People

Raju Solomon: AUTHOR

Abstract

Presented herein is a solution for WebRTC-based in-home streaming solution. WebRTC (Web Real-time Communications) can be leveraged to play content which is either stored or actively buffered in-home through WebRTC supported browser or applications instead of media from capture devices.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 26% of the total text.

Page 01 of 8

WEBRTC AS A PROTOCOL FOR STREAMING IN-HOME MEDIA FROM SOURCES OTHER THAN FROM CAPTURE DEVICES

AUTHOR:

Raju Solomon

CISCO SYSTEMS, INC.

ABSTRACT

    Presented herein is a solution for WebRTC-based in-home streaming solution. WebRTC (Web Real-time Communications) can be leveraged to play content which is either stored or actively buffered in-home through WebRTC supported browser or applications instead of media from capture devices.

DETAILED DESCRIPTION


1. WebRTC as a Protocol for Streaming In-home Media from Sources other than from Capture Devices

    Traditionally, in-home video content has been delivered using either Digital Living Network Alliance (DLNA) or proprietary protocols from or to a set-top box (STB). This approach is acceptable until procedural language based middleware (MW) is being used to abstract applications that are either custom built for the MW or are based on specifications on STBs. The middleware hides the nuances of discovering, playing or delivering the content on the client side and also publishing and serving the content on the server side. Moreover, this approach makes the applications "platform or middleware API dependent" and requires changes in the browser interpreter to perform the required sequences, which is to say that even though the applications are actually scripts which should run across platforms, they become tied to a middleware.

    Presented herein is a solution for WebRTC-based in-home streaming solution. WebRTC (Web Real-time Communications) can be leveraged to play content which is

Copyright 2016 Cisco Systems, Inc.

1


Page 02 of 8

either stored or actively buffered in-home through WebRTC supported browser or applications instead of media from capture devices.

    If WebRTC APIs are supported for streaming, then any standardized browser can be used to play content in-home on the set-top box by porting it only for the machine and graphics, without the need to port custom tags to stream, play content in-home.

    When WebRTC is used for in-home content delivery from sources other than the capture devices then the following challenges need to be dealt with, and which are solved in this submission:

    1. Transcoding: WebRTC streaming is based on VP8/iLBC/iSAC though in-home content would be expected to be in other codec formats.

    2. Transmission source: Streaming content would be stored in files and this would require appropriate hooking to the WebRTC protocol.

    3. Trickplay - WebRTC is a media used for real-time chat, and there is no scenario for trick mode. Hence it defines no methodology for trickmode.

    4. Content Hosting: There is no methodology for listing and hosting content in WebRTC.


2. Basic Concept and Flow of WebRTC

    In the normal sequence of operations of WebRTC, the user of a browser intending to start a stream (or chat) with a recipient, choses the user and then does a "createOffer" , to the host webserver. The host webserver then tunnels through to the webserver on the intended endpoint and then it res...