HbbTV Symposium 9th October 2014 HbbTV Roadmap Jon Piesing, TP Vision Jon Piesing is the vice-chair of HbbTV. He played a major role facilitating the convergence of the original French and German initiatives which together become HbbTV. Jon has been a leading figure in the development of specifications for integration of TV and interactivity for more than ten years. This has included being the chairman of groups in DVB, the Open IPTV Forum and the UK DTG. Jon is now Director, Standardisation for TP Vision (who manufacture Philips TVs for Europe and a number of other territories). He has previously held senior positions related to standardisation in several different units of Philips. HbbTV Roadmap For HbbTV Symposium Europe 2014 Jon Piesing Chair HbbTV Specification Working Group © HbbTV Confidential page 2 Contents » Where we’ve come from - HbbTV 1 and 1.5 » HbbTV 2 » » » » » New Technology Companion Screen Feature Improvements Testing Status Today » Beyond HbbTV v2 © HbbTV Confidential page 3 Where We’ve Come From - HbbTV 1 and 1.5 » HbbTV 1 » Specification published via ETSI in June 2010 » Test suite v0.9 available in August 2012 » HbbTV 1.5 » Specification published via ETSI in November 2012 » Errata #1 published in October 2013 » Errata #2 published in August 2014 » Test suite v1.0 now in final acceptance and review » Release hoped by end 2014 © HbbTV Confidential page 4 NEW TECHNOLOGY IN HBBTV V2 © HbbTV Confidential page 5 HTML5 and Associated Technologies » For HbbTV v1/1.5, we refer to a selection of web standards defined in CEA-2014 and modified in the Open IPTV Forum » HbbTV v2 we replace this with a selection of W3C & other web standards defined in OIPF shortly before the HbbTV v2 technical work started » HTML4 replaced with HTML5 » Also many features started life in the HTML5 spec and have been spun out into separate specs » WOFF, Canvas 2D, XHR, Web Messaging, Web Socket, Web Workers, Server-Sent Events, Web Storage, Media Fragment URI » CSS 2.1 extended with a selection of CSS3 » Basic UI, Color, Images, Backgrounds and Borders, Selectors, Media Queries, Multi-column Layout, Flexible Box Layout, Fonts, Transforms, Transitions, Animations » DOM2 replaced by DOM 3 as required by HTML5 © HbbTV Confidential page 6 HTML5 Video Element » Included in the spec for IP delivered video » Good for those who want to target TVs, tablets, phones, (etc) all with the same HTML app » Sometimes less functionality than the current API » Old API based on the <object> element is still included both for IP delivered video and broadcast video » Apps can choose which to use » Many integration details with TV needed to be defined » Mapping between HTML5 video element features and A/V file / container formats (MPEG-2 TS, ISOBMFF/MP4, DASH) » Support for TTML subtitles with a native TTML decoder » HTML5 media specs were more influenced by the other subtitle format WebVTT » Support for live TV » HTML5 media specs were designed around content that has a beginning and an end © HbbTV Confidential page 7 DVB CI Plus 1.4 HbbTV TV Terminal Application Control Control CI Plus Host [content]DRM [content]DRM content (IP) [content]CI Plus (LSC) CI Plus CI Plus CAM Descrambling /rescrambling DRM Common Interface DRM Server » “DRM in a CAM” feature references CI+ 1.4 “Host Player Mode” » For content delivered over broadband using MPEG DASH, or downloaded (incl. from broadcast) » 2 other features use the CI+ 1.4 “Auxiliary File System” » Launch apps where whole app comes from the CAM » Access to data from the CAM by conventional broadcast or broadband apps © HbbTV Confidential page 8 Other New Technology » HEVC video via broadband » Covers both UHD and HD use-cases » UHD particularly where it’s not available in the broadcast » HD for the same quality as AVC at a lower bitrate or higher quality than AVC at the same bitrate » HEVC via broadcast is left to national specs » Subtitles via broadband » Uses W3C TTML as profiled by the EBU (“EBU-TT-D”) » Privacy » » » » Uses the W3C ‘do not track’ specification Possibility of blocking third party cookies commonly used in tracking Possibility of blocking tracking web sites Recommendations to app developers on respecting privacy » Multi-stream synchronisation » E.g. sync audio delivered via broadband with broadcast video » Builds extensively on synchronising applications and content across devices (see later slides) © HbbTV Confidential page 9 COMPANION SCREENS © HbbTV Confidential page 10 Launching CS App. From the TV HbbTV Terminal Companion Screen CS Application HbbTV App. HTML App. Web Browser Web Browser Discovery / launch HbbTV CSManager Launch Discover CS Launcher Install / Launch Native App. Install / Launch Launcher • User starts “Launcher” app on companion screen • Launcher app typically comes from TV manufacturer • Protocol between terminal and launcher is proprietary but payload for describing what app to launch (from what app store) is specified • App asks HbbTVCSManager for list of currently running launchers • App asks choses a device with a running launcher • App asks launcher to (install and) launch app © HbbTV Confidential page 11 App2App Communication HbbTV Terminal Companion Screen WS connection CS Application HbbTV App. HTML App. Web Browser Web Browser Service end-points HbbTV CSManager WebSocket Server • • • • • • © HbbTV Native App. WebSocket connection TV runs websocket server App asks HbbTVCSManager for local end point of websocket server App makes websocket connection to local end point Companion screen app obtains remote end point of websocket server Companion screen app makes websocket connection to remote end point Websocket server pairs local and remote connections Confidential page 12 Remotely Launching HbbTV App. HbbTV Terminal Companion Screen CS Application HbbTV App. HTML App. Web Browser Web Browser Native App. Launch HbbTV App HbbTV CSManager Discovery HbbTV Terminal Launch HbbTV App » Based on Netflix/Youtube DIAL protocol » App on companion screen discovers HbbTV terminal & makes HTTP POST request to the end point to launch an app » App launching can be refused for various possible reasons listed in the spec © HbbTV Confidential page 13 Companion Screen Common Pieces » Some things are common to several of the companion screen features » Discovery based on DIAL/ UPnP-SSDP » Companion screen devices can discover HbbTV TVs via DIAL » Discovery also provides URLs for HbbTV CS services supported on the TV » HbbTVCSManager object in the browser in the TV » Apps on the TV can get a list of CS devices » Apps on the TV can obtain URLs for HbbTV CS services on that TV » 3 routes for app on companion screen to get URLs for services on the TV » Via DIAL/UPnP-SSDP discovery » Via app 2 app communication from an app running on the TV » As a launch parameter - if the CS app was launched by the TV © HbbTV Confidential page 14 Synchronising Applications & Content Across Devices » Based on work in DVB “TM-CSS” group © HbbTV Confidential page 15 FEATURE IMPROVEMENTS © HbbTV Confidential page 16 Main Improvements » MPEG DASH » Refers to the new DVB profile of MPEG DASH » Also supports existing HbbTV MPEG DASH » Will be suitable for live TV and not just on-demand » Advert insertion into VoD content » Uses two HTML5 media elements with additional requirements for a clean transition between them » Push VoD » Aka “Non-realtime content delivery via broadcast” » Combines existing API with a file transport protocol optimised for small numbers of (very) large files © HbbTV Confidential page 17 Other Improvements » Support for mouse and keyboard devices » Trivial extension to existing APIs » Application and content synchronisation » Minor enhancements to existing specs » Reconciling key request conflicts » Better sharing of user input between HbbTV environment and other TV set features based on existing web APIs » Caching of object carousels » Based on solution used for MHEG-5 in Australia © HbbTV Confidential page 18 HbbTV v2 Specification Overview HbbTV Specification Vol. 5 DAE Vol. 2 Media Formats Vol. 7 Content & Service Protection Web Standards TV Profile CEA-2014 © HbbTV HTML5 CSS3.. DOM3.. TS 102 zzz EN 300 468 TS 102 zzz TS 102 809 CSS DVB-SI DASH TS 101 154 TS 103 205 ext. to CI Plus CI Plus Tech-3380 “EBU-TT-D” ..... …... TTML Confidential Video and Audio Codecs 23009-1 DASH 23001-7 CENC page 19 Testing » For HbbTV v1/1.5, test suite development was largely based on voluntary effort and was painfully slow » The link between the spec and individual tests is something called “assertions” » Getting volunteers to write and review assertions is really difficult » For v2, the specification will not be published until there are reviewed assertions for everything that needs them » HbbTV will commission tests based on the reviewed assertions » RfI for possible test case suppliers has just been issued » RfP for test cases suppliers to be written based on RfI responses » Reviewed assertions are needed before we can issue the RfP » HbbTV wants to reduce the wait for the v2 test suite compared to the v1 / v1.5 test suite © HbbTV Confidential page 20 Specification Status Today » Stable draft of the specification shared with partner organisations at the end of July » Currently processing and solving comments from review of this draft » Test assertions exist for all features » Currently being reviewed » Some iteration required where solutions to review comments will impact assertions » Publication of the v2 spec depends on HbbTV member contributions to review assertions © HbbTV Confidential page 21 BEYOND HBBTV V2 © HbbTV Confidential page 22 IPTV » Work on HbbTV and IPTV started during the discussions about transferring activities from OIPF to HbbTV » Also inspired by some of the German activities around video via multicast » 3 scenarios for HbbTV and IPTV » IPTV is the “Broadcast” in HbbTV – no conventional DVB-C/S/T » All TV channels / services come via IPTV » IPTV is “Broadcast” alongside conventional DVB-C/S/T » TV channels / services come via either/both IPTV and DVB-C/S/T » Multicast video presented by an HbbTV app » HbbTV is not going to do an “HbbTV IPTV profile” » People have done those before and they haven’t been used (or at least not admitted to) » First step will be to document how various IPTV technologies can be used with HbbTV » E.g. DVB SD&S, DVB OSDT, multicast video, RTSP, … » Basic IPTV technology choices (e.g. FCC, RET/FEC) will be left to those closer to deployments © HbbTV Confidential page 23 Independent Application Signalling » Heard many times yesterday about network operators that don’t carry the HbbTV signalling provided by the broadcasters » Prevents consumers accessing HbbTV services using the HbbTV TV they’ve paid for » HbbTV will be investigating other ways for the information needed to run an app to reach consumer’s TVs » No agreed solutions yet but .. » In the USA, ATSC are working on watermarking for this and other use-cases • • Call for proposals issued in January 2014 http://www.atsc.org/cms/index.php/standards/other-technical-documents/333-call-forproposals-for-atsc-30-automatic-content-recognition-watermarking-solutions » HbbTV 1/1.5 include mechanisms for running HbbTV apps with analogue TV (where there’s no signalling) » Based on sending a channel identifier to a secure web server and getting HbbTV signalling information back as the response © HbbTV Confidential page 24 More? » HbbTV works on requirements proposed by its members and reviewed in the Requirements Working Group » Things only happen because members contribute time and energy to making them happen » If you think something belongs in a future HbbTV spec » If you’re an HbbTV member, come along to the Requirements Group and start a discussion » If you’re not an HbbTV member, how about joining? © HbbTV Confidential page 25
© Copyright 2024 ExpyDoc
