How do other standards initiatives fit with OIPF?
The Forum does not duplicate the work done in other fora but makes use of standards developed elsewhere and uses them to construct its end-to-end interoperable specifications. There are many standards development organizations (SDOs) and industry fora that address IPTV and related areas such as; ATIS IIF, Broadband Forum, CEA, DLNA, DVB, ETSI TISPAN and MCD, HGI, ITU, Marlin Developer Community, OMA, SCTE, UPnP and 3GPP. Some of them have already finalized their work or are working on specifications that are of relevance to the Open IPTV Forum. They often focus on specific parts of the overall solution (e.g. home network, content protection, browser technologies) or specific deployment scenarios (e.g. managed networks).
How does OIPF ensure compatibility with external standards?
The functional blocks of the OIPF solution are derived from existing external standards, and co‑operation agreements and liaison activities are in place with external standard bodies to ensure future system compatibility. The Open IPTV Forum combines appropriate specifications from such bodies for its overall solution. Common members between the OIPF and these bodies have allowed us to ensure that the specifications are aligned. With some of them we have already established liaison relationships and exchanged documents. For the detailed status of work in other standardization bodies, please contact them directly.
Are there not too many forums trying to standardize Connected TV to their own flavor?
At first glance the global industry for Connected TV appears to be awash with standards bodies and organizations, with the OIPF being just another contender. On closer inspection however it becomes clear that the OIPF mission is to work with the ‘best of breed’ of these other organizations to draw together various specifications into one coherent, end-to-end interoperable solution. The OIPF does not seek to ‘reinvent the wheel’ on standards, rather, to extend the acronym, it seeks to build an interoperable transport system from components already created by existing standards bodies, whilst adding in components of its own. The key point is that, by conforming to the Forum’s specifications, which include and build on existing standards offerings, the industry can ensure the maximum possible level of interoperability of entertainment services and retail TVs for end-users.
Contributing standards organisations include; W3C, DVB, 3GPP, ETSI, DLNA, OMA, MPEG, Broadband Forum, CEA, IETF, ITU, Java Community Process, JPEG, MDC and HbbTV.
With which standardization bodies is the Open IPTV Forum already collaborating?
The OIPF has set up close ties with other industry organizations, benefited from various combinations of overlapping member companies (and even individuals within those companies), and initiated formal liaisons and regular dialogue with many bodies. The OIPF specifications contain references to standards published by W3C, DVB, MPEG, 3GPP, ETSI, Broadband Forum, CEA, DLNA, IETF, ITU, Java Community Process, JPEG, MDC, OMA.
HbbTV Consortium Specifications reference the work of the OIPF as a supporting pillar for use with Connected TVs. We have hence built an active relationship in support of the rapid deployment of HbbTV-compatible Connected TVs across Europe.
Do OIPF and HbbTV cooperate with each other?
Yes. OIPF and HbbTV have a formal cooperation agreement, expressing the desire to minimise fragmentation and divergence of their activities. Through 2012 there has been co-operation in the area of technical specifications development and a joint announcement regarding certification, compliance and testing (http://www.oipf.tv/news/oipf-and-hbbtv-collaborate-on-testing-of-common-technologies-crucial-to-global-interactive-tv-deployments).
How are OIPF and HbbTV related?
The OIPF specifications provide important components for creation of HbbTV specifications. In essence, HbbTV adopts a large amount of the technical work from OIPF and applies it to an additional market sector. There is a significant overlap between OIPF and HbbTV participants.
This commonality has significant benefits for product development, especially for CE manufacturers, as two different market segments can be addressed through shared functionality, providing improved investment return for manufacturers, along with a "stepping stone implementation" towards the richer OIPF specification. Feedback from HbbTV deployment should provide technical validation of many OIPF building blocks, which benefits both activities.
Both HbbTV and OIPF use web technologies for the application format. Many HbbTV applications are expected to be trivially portable to OIPF.
The extensive common elements between the two technical solutions should provide a larger market for many application developers and give a better return on investment for manufacturers.
What specifications from the OIPF are referenced by HbbTV?
The main building block for HbbTV is Volume 5 (Declarative Application Environment) from Open IPTV Forum. The HbbTV v.1.2.1 specification also references Vol 2, the Media Formats specification, Volume 4, the Protocols, for unicast streaming over HTTP, and Vol 7, on Content & Service Protection, for CI+ and HTTP Basic and Digest authentication.
Which markets do OIPF and HbbTV target?
HbbTV focuses on European (DVB) broadcast TV whereas OIPF addresses the global market for IPTV service providers covering both managed and open internet environment. OIPF can exploit IMS-based managed network capabilities where present as well. OIPF provides three different profiles to cover different business models and market sectors
OIPF sees HbbTV as supporting its development work and taking elements of its specifications to market segments that are not the primary focus of OIPF, adding overall market weight through overlap and commonality.
HbbTV is primarily targeted at the European retail DVB market, with either an un-managed network, or operating over a managed network provided by the broadcaster.
How does the OIPF fit with the Smart TV Alliance?
The Smart TV Alliance publicly states that they profile relevant industry specifications (including OIPF) to define a common platform based on HTML5 for app developers, so that they can create conformant applications with the assurance that these can run on all end devices (connected TVs, tablets, etc.) which also implement that profile. As the OIPF DAE also provides a common platform for applications implemented in the current generation of TVs, we expect that the new work to enhance it with aspects defined in the HTML5 suite of specifications can only lead to a convergence between these two platforms. Having members in common will certainly drive this convergence.
Further questions on the Smart TV Alliance should be directed to that organization.