Your browser is not supported. Please update it.

11 September 2014

Headless gateway advance highlighted at IBC

Product launches from French TV access product maker Neotion among others ensure that the headless gateway will feature at IBC in Amsterdam for the second year running as a migration milestone on the road to all-IP broadcast services. The headless gateway is actually more than two years old, having emerged initially on the back of Comcast’s RDK (Reference Design Kit) as a hybrid box for MSOs to embark on their IP migration strategy.

Since then the headless gateway has ridden on the back of RDK to take the whole pay TV CPE market by storm, even if there is still strong demand for more traditional headed equivalents as well as stripped down alternatives such as OTT only HDMI dongles. RDK firstly gained support from other US cable companies, then spread overseas as the likes of Liberty Global jumped on board and finally gained traction amongst satellite and some IPTV operators as well. Most of the leading pay TV CPE makers such as Pace, Arris, ADB and Kaon Media of South Korea have both headed and headless gateways in their portfolios and will be parading these at IBC.

The media gateway itself evolved before RDK as a high end set top combining integrated storage and home networking capabilities to enable multi-room DVR and with IP video access for access to OTT content. But these devices still did the video rendering and connected directly to a household’s main TV set, with well-known examples including various Tivo boxes, Liberty Global’s Horizon and the Hopper from Dish in the US.

Such boxes were seen as ideal hybrid vehicles for migration by some operators, but not by Comcast, which as the leading US MSO with over 20 million subs, was coming under pressure from IPTV operators such as AT&T, as well as DTH competitors, notably DirecTV. Comcast wanted to cut CPE costs and also shorten the typical two year set top box renewal cycle in response to the accelerating pace of pay TV innovation and came up with RDK. The aim was to standardize the commodity aspects of a hybrid gateway while allowing room for innovation at the application and service level.

RDK achieves this by presenting a common platform based on DLNA standards for interoperability and content distribution in the home, along with HTML5 for achieving a consistent UI on multiple devices. Comcast argues that this is already reducing costs and at the same time bringing the development cycles down to one year for several reasons. Firstly the onus is now on CPE makers to establish conformance and interoperability with set tops and gateways rather than the other way round as there is a common target platform. Another reason is that operators such as Comcast can now work with SoC makers to incorporate the RDK framework before adding the higher level functions for a specific box implementation.

RDK will work equally well with headed and headless gateways, but the latter is more in tune with the underlying philosophy. After all RDK was designed to escape the costs and development effort associated with full blown media gateways. Headless gateways eschew the video rendering and instead distribute signals as IP via a home network, either a fixed infrastructure such as MoCA or over Wi-Fi. This means that video rendering has to be performed in the viewing devices, but then tablets, PCs and smartphones as well as smart TVs can all manage that.

For standard TVs a rendering device is required, such as an IP set top or an HDMI dongle. The headless gateway is also stripped of storage, which makes it well suited as an adjunct for a cloud distribution model with nPVR. The headless gateway is therefore a simpler device that can be located anywhere in the home, such as the basement, garage or even outside.

In fact Comcast has also been setting the pace in headless gateways with its XG5 specification, which is designed to make a home network carrier class and capable of delivering HD video as reliably as a traditional broadcast infrastructure. For this reason Comcast specified MoCA 2.0 as a backbone delivery platform in conjunction with Wi-Fi for the final hop, at any rate to serve wireless devices.

Another key component that is specific to cable, although applicable to all gateways and not just the headless variety, is the Tru2way middleware, which emerged as the successor to the original Open Cable Application Platform (OCAP) technology for TVs to connect to cable services without requiring a set-top box. This software presents a common platform for deployment of interactive TV applications on top, insulating the latter from the underlying device. RDK then sits as an abstract layer between that middleware and the SoC so that functions like tuning, decryption and de-multiplexing are handled via generic, rather than proprietary commands. This is what saves development time – when headless gateway makers enable middleware functions specific to a given operator’s requirements, the coding time required to build the software stack is reduced significantly.

So unlike tru2way, RDK does not specify how the middleware layer is executed. Instead, it provides APIs for a variety of functions, including tru2way itself and IP-oriented open-source processes like HTML5, WebKit, Gstreamer and QT, giving operators maximum wriggle room for their middleware environment. Most headless gateways, for example from Cisco, Arris and Pace, therefore are based on tru2way on top of RDK.

In fact Arris and Pace were first off the blocks at CES 2013 with quite similar boxes differing principally in choice of chip set. Arris brought out its MG2402 gateway based on the Comcast XG5 using the Intel Puma 6 DOCSIS 3.0 chipset, able to bond 24 downstream channels and supporting 8 QAM channels and CableCARD-enabled for QAM-based conditional access. Other key chipset suppliers for the MG2402 included Celeno Communications for the 802.11ac chip, Zenverge for the ZN200 video transcoding chip, with Entropic supplying the MoCA 2.0 chip. Pace on the other hand used all Broadcom chipsets, including the BCM3128 receiver, the BCM3335 quad transcoding hybrid IP gateway SoC, and the BCM4360 5 GHz Wi-Fi chip.

Some middleware vendors have incorporated tru2way into their software for headless gateways. SeaChange’s Nucleus for example is built on the company’s own implementation of tru2way to enable set top functionality such as channel change, VOD/DVR playback and trick mode, along with media sharing throughout the home via DLNA. Nucleus is the middleware behind Netgear’s HMG7000 gateway, which was unveiled at last year’s IBC and underwent some operator trials early this year.

Now Neotion has taken a different route this year with its DVBeacon headless gateway at IBC, having chosen Media-OS from Em-Sys as its middleware. Rather than take the RDK route, Em-Sys has built a complete turnkey solution including many of the higher functions needed for a pay TV service, such as simultaneous play, record and transfer for recorded or live TV. It is in effect a complete stack supporting the standards that have become universal for home distribution, including DLNA coupled with DTCP-IP for secure media playing, JavaScript for development and HTML5 for browser based UIs. Neotion has taken a modular approach, with the UI for example separated out so that operators can cherry pick there. At IBC the DVBeacon demonstration is being staged jointly with Em-Sys, featuring an HDMI dongle as the client device for standard TVs.

This dongle incorporates browser and DLNA components from Tokyo based multiscreen software vendor Access Co, chosen because these also have added features suitable for a turnkey package. Neotion has integrated Access’ NetFront Living Connect DLNA Technology Component and NetFront Browser NX in its secure HDMI Dongle. Among added features are support for home media sharing over Wi-Fi with access to content such as photos on mobile devices, which can also control printers without requiring any drivers.

Although headless gateways have been focused principally on MSOs they are starting to be deployed by satellite and IPTV operators as well. The satellite front was opened by Broadcom at IBC 2013 with the announcement of chipsets integrating DVB-S2 for headless gateways, enabling delivery of satellite TV to any IP-enabled client device. These chips were sampling early this year and we await launch of DTH headless gateways based on it.