Your browser is not supported. Please update it.

27 March 2014

Broadcasters like what they see in HbbTV 2.0

The Hybrid Broadcast Broadband TV (HbbTV) standard has been a European success story that rather like DVB has caught on way beyond the continent’s borders. It is now moving into its proper second generation, with HbbTV 2.0 currently being evaluated by broadcasters, especially in Europe, having evolved beyond being just a standard for interactive TV. HbbTV is now both a standard for converging TV with broadband delivery over IP as defined by the European Telecommunications Standards Institute (ETSI) and also a promotional initiative for the broadcasting industry as it embraces the Internet. This leads to the paradox that the very success of HbbTV will ultimately ensure its extinction as a distinct standard or platform. In essence HbbTV is a box or container for delivering key components of the hybrid and ultimately IP based broadcast world, which like the biodegradable packaging of some nursery plants, it will eventually dissipate.

The result of being a rallying platform is that the sum of HbbTV’s parts is actually greater than its whole. It has associated components covering for example cloud services and personalization that are beyond the immediate brief of the ETSI standard itself. Even the core standard has expanded in scope with the version 2.0, with the principle addition being incorporation of HTML5, which is becoming the standard mark-up language for playing audio and video within web pages. HTML5 is largely taking over from Adobe’s Flash, which about five years ago looked set to dominate the multimedia world and was bet on by a number of hybrid TV initiates, including the UK’s Project Canvas, subsequently rechristened YouView.

At that time HbbTV had yet to hit the world, being at the inception stage then purely as a standard facilitating interactivity within broadcast services, as an alternative to the DVB’s Multimedia Home Platform (MHP). Then HbbTV 1.1 was published as an ETSI standard in June 2010, although it was really the offspring of a marriage between the French H4TV project and the German HTML profil project.

The next version HbbTV 1.5 followed early in 2012, bringing two crucial new ingredients – compatibility with leading DRMs and support for the then nascent MPEG DASH adaptive streaming standard. Apart from HTML5 the most notable addition in HbbTV 2.0 is support for another key emerging standard, the HEVC (High Efficiency Video Coding) codec. HbbTV 2.0 also in effect gives HTML5 a leg up as well, given that unlike Flash it does not enable interactivity with a remote broadcast service on its own. In combination with HbbTV, HTML5 can operate inside an interactive TV service. Having said that, there are moves afoot to incorporate interactivity directly within HTML5, the main challenge being to ensure that different brands of browser handle it consistently. This rather highlights HbbTV’s role stimulating development of relevant standards and technologies.

The arrival of HbbTV 2.0 has stoked debate within the broadcasting community over the likely course of hybrid technology over the next five years. HbbTV does not yet have things all its own way, even in Europe, but hybrid broadcasting technology as a whole has largely converged at the network transport level. All hybrid applications require some sort of mechanism for triggering applications as well as for exchanging metadata and all have a technique for caching.

Both HbbTV and MHP signal services via a DVB-based Application Information Table and Program Map Table, and applications for both environments are carried and pre-cached using the Digital Storage Media Command and Control (DSM-CC) toolkit for developing control channels associated with MPEG-2 transport streams. On the signaling and transport side, just about all the standards originally developed for interactivity, including HbbTV and MHP, as well as MHEG (Multimedia and Hypermedia Experts Group) and OIPF (Open IPTV Forum), are based on the DVB TS 102 809 standard, because that is the main one used for time-sensitive applications requiring frame synchronization.

The main differences between these hybrid and interactive standards resides within the presentation layer. MHP adopted Java, while the UK’s YouView platform uses Adobe Flash and HbbTV originally went with CE-HTML, a standard for designing webpages with remote user interfaces for CE devices on Universal Plug and Play (UPnP) networks.

At the time these decisions were made, HTML5 was only evolving and there was some uncertainty over which standard would prevail for hybrid and interactive services, or even for sure that they would be browser based. In the event these earlier decisions have left all three hybrid initiatives with a headache. All three standards were based on technologies that are rapidly being superseded in the Internet environment by HTML5. The number of HTML5 developers ‘ and therefore of apps ‘ has been exploding as it is seen as the future for all media clients.

HbbTV was the first to see the light and has now completed the work of incorporating HTML5 in version 2.0. But now HbbTV has some legacy itself to confront. Early HbbTV devices only support applications authored in CE-HTML so that will have to continue being supported. Meanwhile YouView and MHEG will have to come into line too.

Apart from the immediate technologies within the standard, HbbTV has succeeded in helping identify the common components needed for hybrid and IP broadcast services and also in stimulated the resulting developments. It directly led to the formation of the European Union funded project called Hybrid Broadband Broadcast (HBB) NEXT, with a remit to augment HbbTV with surrounding personalization and deployment capabilities. So far its contributions have embraced multi-user identification and recommendations, synchronization between media streams and devices, voice and gesture recognition and so called cloud offloading.

HBB-NEXT also contributed directly to HbbTV 2.0 with three features required for second screen interaction with the primary service, whose need was not apparent when the earlier version 1.5 was being developed. These were for accurate synchronization between wireless devices, synchronization between apps and the Audio/Video stream, and user/identity management. The identity management feature enables HbbTV applications to exploit user identity obtained from companion devices in order to provide personalized services, subject to the user’s permission. The two media synchronization features between them enable HbbTV devices to combine media content from multiple sources, such as video from broadcast and audio through broadband. This could either be on a single HbbTV terminal, or via a combination say of TV and second screen.

HBB-NEXT is also developing components outside the immediate HbbTV standard but which will be needed for emerging hybrid services. One of these still under development is a cloud-based media processing platform, referred to as media cloud, to support adaptive live streaming across multiple devices, such as set tops, smart phones, tablets and PCs. This includes interfaces designed for three purposes, to enable devices to interact with the media cloud, for content providers to manipulate their assets during delivery, and thirdly for the platform operator to monitor resource usage across the entire media cloud platform. This media cloud platform has been integrated with other HBB-NEXT applications on both Android tablets and set tops to support various media services, such as sign-language stream synchronization in the cloud, subtitle overlaying, and dynamic ad insertion.

HBB-NEXT has demonstrated a prototype of media cloud for two use cases, one for synchronizing two separate streams and delivering these to various terminals. One example was playing out the video of a sign language interpreter alongside the TV channel on mobile devices and other HbbTV terminals.

The second use case involved scanning the QR (Quick Response) code of the current TV program so that users can resume watching on their mobile devices in the living room by accessing an adaptive stream over the home’s broadband network. In this case, the adaptive streaming is generated by the media cloud after taking account of the client device’s capabilities.

It appears then that all roads are leading to HTML5 around which various enabling standards and technologies are coalescing. HbbTV is proving a useful vehicle to carry standards on that journey, but once they have all arrived at the destination it may end up empty.