The HbbTV 2.0.1 specification updates HbbTV 2.0 to add a few features needed for deployment in the UK and Italian market as well as fixing issues found during implementation of HbbTV 2.0 receivers and tests.
This document contains the currently identified and resolved errata to ETSI TS 102 796 v1.4.1. It is a living document which will be updated based on experience of implementing receivers, services and tests.
This document is a comparison between HbbTV 2.0.1 (2016-07-04) as published and HbbTV 2.0 (TS 102 796 V1.3.1 – 2015-10). The comparison has been done using the automated mechanism in Microsoft Word which may result in false positives and results that are more compex than would come from a manual comparison.
This is the first version of the HbbTV 2.0.1 specification and has been replaced by the 2016-07-04 version. It is preserved here purely for the record and should not be used.
HbbTV 2.0 was published in 2015. It updated the web platform to HTML5 and introduced a number of new features. It has been replaced by HbbTV 2.0.1.
See attached for more information about the development of the HbbTV 2.0 Specification.
Frequently asked questions about HbbTV 2.0.
This is a version of TS 102 796 V1.2.1 with the changes from errata 4 (see below) applied. Changes are marked with the usual underline/strike-through convention to make it easier for users to see the differences. Issue numbers are included for cross-referencing with errata 4.
TS 102 796 V1.2.1 (often called HbbTV 1.5) introduced support for HTTP adaptive streaming (based on MPEG-DASH), improving the perceived quality of video presentation on busy or slow Internet connections. It also enabled content providers to protect DASH delivered content with potentially multiple DRM technologies based on the MPEG CENC specification, improving efficiency in markets where more than one DRM technology will be used.
This version was based on 3 documents;
The present document contains the currently identified and resolved errata to ETSI TS 102 796 v1.2.1 integrated into the text of original specification. It is provided as a convenience for users of the specification so that the changes defined in the errata document can be seen in context. Changes relative to the original TS 102 79 V1.2.1 are marked and labelled with issue numbers which match the issue numbers in the errata document.
This document includes all errata from errata 1, errata 2, errata 3 and errata 4.
This errata document contains a set of identified and resolved errata to the HbbTV specification published as ETSI TS 102 796 v1.2.1. This document contains all agreed errata and replaces errata 2 and errata 1.
This is the second errata to TS 102 796 1.2.1. It is replaced by errata 3 and is preserved here purely for the record. It should not be used.
This is the first errata to TS 102 796 1.2.1. The contents are fully included in errata 2. It is preserved here purely for the record and should not be used.
This is an updated version of the stand-alone HbbTV 1.5 specification. It is preserved here purely as for the record. It is obsolete and should not be used any longer as the content is included in TS 102 796 V1.2.1 with important clarifications.
This is the original version of HbbTV 1.5. It is preserved here purely as for the record. It is obsolete and should not be used any longer as the August 1st 2012 version includes important clarifications.
This is the original HbbTV specification. It should only be used when developing applications and services targeted at already deployed HbbTV TVs and set-top boxes. New TV and set-top box developments should use TS 102 796 V1.2.1 or HbbTV 2.0.
This errata document contains a set of identified and resolved errata to the HbbTV specification. These have been integrated with HbbTV 1.5 and the text of ETSI TS 102 796 V1.1.1 and the results are included in version 1.2.1. This fully replaces the former errata 1.
This is errata 1 for HbbTV 1.0. It is preserved here purely as for the record. It is obsolete and should not be used any longer.
This specification is an extension to the core HbbTV specification to support operator application. Operator applications allow TV operators, in partnership with TV manufacturers, to provide an operator-branded experience as an application on TVs. This application acts as a “Virtual Set Top Box”, providing effectively all functionality of a Set Top Box (STB) without the need to install one. The OpApp specification describes how the HbbTV browser can run both HbbTV broadcaster applications and operator applications at the same time. It specifies how operator applications are discovered, installed and how they can replace the TV’s native UI, including access to the TV’s remote control key. New readers should read “OpApps Explained” first in order to get an overview.
This presentation provides an insight into the HbbTV OpApp specification. It includes a description of what an operator application is, market drivers for operator applications, as well as an overview of technical details within the HbbTV OpApp specification.
The versions of the HbbTV Specification published to date rely on signalling in the broadcast to start broadcast-related applications, through the Application Information Table (AIT). This document defines a method for discovery of broadcast-related HbbTV services via a broadband internet connection for settings where AIT signalling via the broadcast network is not available to the HbbTV terminal.
This specification defines how HbbTV terminals can be used with IPTV services. It is applicable to IP-only devices (no DVB-C/S/T tuner) where the broadcast” is IPTV. It is also applicable to hybrid devices where some TV channels come via IP and some via DVB-C/S/T.
The document contains the list of TLS root certificates that must be supported by HbbTV terminals.
This spreadsheet replaces a list included in HbbTV 1.0/TS 102 796 V1.1.1.
The contents of this spreadsheet were developed by the UK Digital TV Group whose contribution is very much appreciated by HbbTV.
Date updated: 30th April 2015 (by the UK DTG Root Certs ad hoc group)
Date updated: 26th October 2015
In June 2014, the activities of the Open IPTV Forum (OIPF) were transferred to the HbbTV Association. This broadened the HbbTV Association’s mandate to include defining specifications for service providers and technology suppliers that streamline and accelerate deployment of IPTV services.
The HbbTV Test Suite provides a set of test material to enable implementers to test devices against the HbbTV specifications and other associated specifications (such as OIPF). It is suitable for suppliers of complete devices and also suppliers of hardware and software components.
Currently the test suite includes tests for HbbTV v1 and v1.5 (ie ETSI TS 102 796 v1.1.1 and v1.2.1). Tests for HbbTV 2 are expected to be added during Q4 2015 and 2016.
Anyone can access the HbbTV Test Suite through an HbbTV Registered Test Center. A list of these can be found in the following section.
HbbTV members who have the necessary expertise and equipment may also license the test suite for use in their own facility. The test suite license covers a whole company, including associated companies, and a list of those who have signed it can be found here. The test suite is distributed with details on how to obtain a new test harness which provides minimum required functionality to execute approved test materials in a manual way. Commercial test tools which implement the test harness specification are also available.
This file contains an indication of the contents of the test suite. The precise contents at any particular time may differ due to tests being removed and/or reinstated through the Test Material Challenge Process.
HbbTV Members wishing to license the HbbTV Test Suite should leave contact details here:
HbbTV Registered Test Centers offer HbbTV testing services to the market, for those manufacturers, operators or integrators who do not wish to do HbbTV receiver testing in-house. The process for a test center to register with HbbTV is lightweight with relatively few obligations, in return for which the test center can be added to the list below.
Manufacturers do not need to become an HbbTV Registered Test Center if they are only testing their own HbbTV products.
HbbTV Registered Test Centers offer HbbTV testing services to the market, for those manufacturers, operators or integrators who do not wish to do HbbTV receiver testing in-house.
The process for a test center to register with HbbTV is lightweight with relatively few obligations, in return for which the test center can be added to the list below.
Manufacturers do not need to become an HbbTV Registered Test Center if they are only testing their own HbbTV products.
HbbTV cannot recommend a particular test center nor does it audit or accredit test centers for regulatory compliance. The following criteria may be considered when selecting a test center. It does not include other criteria covering any commercial relationship that would required with the test center.
|Reputation||Is the organisation impartial and trusted in the industry? For example you may wish to request references or evidence of previous relevant work.|
|Technical Expertise||Does the test center employ testers with HbbTV knowledge; and appropriate qualifications?|
|Confidentiality||How does the test center ensure confidentiality of test reports and test samples?|
|Efficiency||Does the test center have good procedures for managing bookings and conduct testing efficiently and quickly?|
|Responsiveness||How will the test center provide swift support and answer questions in a timely manner?|
|Facilities||Does the test center have all necessary equipment to perform the range of testing required?|
|Awareness||How does the test center track changes in published specifications and test suite releases? A list of the approved tests is published above; are they using the latest version of the test suite?|
|Deliverability||Ask for an example test report, to determine if this meets the requirements of the client and any 3rd party regulatory body. Can this report be verified for authenticity?|
|Support||Will the test center assist in debugging any test failures? What is their re-test policy? Will they help with challenging any tests that are felt to be in error?|
DTG Testing Limited
DTV Accredited Compliance Lab (part of Samsung Electronics)
Eurofins Digital Testing
Sofia Digital Ltd.
Sony Europe Ltd.
Vestel Elektronik A.S.
The attached schema files have been developed by the HbbTV Association to capture test case requirements, to document the development and approval process for each test case, and to enable implementation of test cases using a HbbTV conformant test harness. These schema are published to enable other groups to use the same schema for development of their own test cases in a way that will maximise interoperability of implementations.
This work is licensed under the Creative Commons Attribution-NoDerivs3.0 Unported License. Creative Commons can be reached at 444 Castro Street, Suite 900, Mountain View, California, 94041, USA
HbbTV welcomes test reviewers to help qualify whether submitted test material is fit to be included in an official Test Suite.
HbbTV and OIPF test material is collected and tracked in a common HbbTV Test Repository powered by SVN. The test material is not for testing or validating devices and such use is prohibited. The HbbTV Test Suite is provided for testing devices against the HbbTV specification and the OIPF test suite is provided for testing devices against the OIPF specification.
During the “Test Review” process, any issues found with submitted test materials are tracked using Redmine. HbbTV and OIPF have anticipated that issues may be encountered even after an official Test Suite is released, and a “Test Material Challenge Process” exists, again tracked by Redmine.
The process for developing and reviewing test materials is shared by two standards bodies, namely HbbTV and the Open IPTV Forum, since test specifications have significant overlap. A test reviewer can be a member of either body (or both), a subcontractor of said member or an approved test material provider.
The details of how test material is reviewed and approved, as well as how test reviewers are selected for particular tests is given in the Test Material Approval Procedure document which is available to companies that become test reviewers.
In order to become a test reviewer, your company will need to conclude the Test Repository Access Agreement (TRAA). To start this process, please send an e-mail to firstname.lastname@example.org, clearly stating your company wishes to get access to the HbbTV Test Repository.
In case your company is a member of HbbTV and/or OIPF, please clearly state this in the e-mail. Please note that such membership will be checked as part of the application procedure.
After the TRAA is signed, individual user accounts will be created to obtain access to the SVN Test Repository and the Redmine issue tracker.
Access to the HbbTV test repository will first be approved per company, before individuals can be added. Each individual requiring access to SVN must send a username and password in a single password file created with the htpasswd command to email@example.com.
htpasswd -c myhtpasswd.txt myusername
Please use as username something which allows others to quickly see who you are e.g. simply use “jdoe” if your name is John Doe. On most Unix systems the htpasswd command is available. Windows users will find multiple places to download it when searching via Google.
The SVN repository is located at https://hbbtv.org/testing-repo so to checkout the repository the following command can be used.
svn co https://hbbtv.org/testing-repo –username=jdoe
If you do not have an account on the Redmine server, you can register for one by going to the following URL: https://hbbtv.fvdev.ca/redmine/account/register
When registering with Redmine, as with the email lists, please only use email addresses clearly linked to your company details given in the TRAA application questionnaire. Yahoo, Google, Hotmail or e-mail addresses that have no company affiliation are not acceptable.
When you have registered with Redmine, your account will be activated manually by the Redmine administrator. In case you have any questions around your account please contact firstname.lastname@example.org.
The HbbTV Full Logo License Agreement allows organisations to use the HbbTV Logo on HbbTV receiver products and packaging that implement either ETSI TS 102 796 v1.1.1 or ETSI TS 102 796 v1.2.1. It describes the obligations required of a Licensee wishing to use the Logo, such as testing the product with the official HbbTV Test Suite and agreeing to modify the receiver if it is found to be non-compliant.
The HbbTV Logo Usage Policy is intended for organisations that wish to use the HbbTV Logo, but do not wish to use it on HbbTV receiver products and packaging. The HbbTV Logo Usage Policy categorises the different types of parties that may use the Logo, along with the obligations of those parties. No license fee is payable for usage of the Logo covered by the HbbTV Logo Usage Policy.
The HbbTV Logo Guidelines is a separate document that describes the rules for how the Logo shall be displayed, including physical characteristics such as colour and aspect ratio. Any use of the HbbTV Logo, under either the HbbTV Full Logo License Agreement or under the Logo Usage Policy, must adhere to the HbbTV Logo Guidelines. The HbbTV Logo Guidelines and the HbbTV Logo artwork are only made available to organisations that have either signed the HbbTV Full Logo License Agreement or have agreed to the HbbTV Logo Usage Policy.
HbbTV takes security very seriously. Security researchers who wish to disclose vulnerability in an HbbTV specification should contact email@example.com in order to enable a constructive engagement. Vulnerabilities associated with a specific manufacturer’s implementation of HbbTV should be reported to the manufacturer concerned but HbbTV can assist in facilitating this.
Tampering with the broadcast transmissions is currently an area of interest for security researchers. Whilst HbbTV does not define the specifications for broadcast transmission, we take this topic very seriously and work actively with the other standards organisations responsible such as the DVB project on such matters, as well as making revisions to our own specifications to protect users. Further relevant Information.
HbbTV Association Policy on Trust and Security
The HbbTV Association is committed to improving the security of services provided using HbbTV technology. The following policy guides HbbTV’s work:
The technical specifications produced by the Open IPTV Forum are provided to the public via the specifications section below.
If you need to contact the Open IPTV Forum about any matter connected with the organization, you may do so at: firstname.lastname@example.org
All technical questions about the OIPF specifications should be referred to the HbbTV Association at: email@example.com
The Smart TV Alliance has merged its activities with HbbTV Association, extending the scope of the HbbTV Specification to address Over-The-Top Services. The combined forces of the two organizations will streamline standards for OTT innovation so consumers can enjoy ever more interactive experiences on their connected TV devices.
The harmonization of activities aims to enable a more efficient approach for developing OTT services across the industry for manufacturers, broadcasters, content producers and developers to create applications for broadcast and broadband delivery via connected TV or set-top-box using a common HbbTV Specification.