DVB-I – Frequently Asked Questions

The list below is based on questions received following the first demonstrations of DVB-I at IBC2019.

 


How is the service list discovered? Is there one list that contains all services?

DVB-I will support various options for the provision of service lists, which will enable the support of many different deployment scenarios and business models. Exactly what kinds of lists appear will be up to those who implement the specification.

--

Once DVB-I exists and I have a good broadband connection to my home, why would I connect a broadcast antenna?

There are still many reasons for users to connect their TV set to an antenna. For example, some services may only be available over broadcast for operational reasons, or may be available in better or more appropriate quality via broadcast. DVB-I enables hybrid offerings combining both broadcast and broadband services.

--

Can DVB-I deliver on-demand content?

DVB-I can deliver on-demand content.

Catalogues of on-demand content can be provided using DVB-I metadata that links either to an on-demand stream itself or to an application that would present the selected piece of content. DVB-I service lists can also include services that are themselves apps delivering on-demand content.

--

Who will make DVB-I clients for mobile devices (to be downloaded from app stores)?

The DVB-I client on a mobile device may be provided by the network operator, the device manufacturer, a third party app developer, or even natively by the device OS, depending on commercial considerations around leveraging linear television service delivery to those devices.

--

Can I make a DVB-T/S/C service fork to DVB-I for a period of time, and then return to the broadcast version at some point later? 

Switching between delivery methods would typically be on an "event" basis. The DVB-I service discovery specification permits "availability windows" to be specified per delivery mechanism and priorities to be assigned to each, allowing selection by the DVB-I client.

--

Do I have to provide EPG data to qualify as a DVB-I channel?

The provision of programme guide data for a DVB-I service (channel) is optional but it certainly helps to enrich the user experience.

--

Can I make the URL and/or contents for my channel conditional on user data / location / accessibility needs?

DVB-I enables the use of authentication and supports the delivery of personalized services. The use of location or accessibility information may not necessarily require knowledge of the actual user, as these can be derived from information configured in the terminal.

--

How is content protection and rights management handled in DVB-I?

Content protection for broadband-delivered services is fully supported.

Various DRM systems can be used, with the content itself protected with the MPEG DASH Common Encryption format. For broadcast services the usual DVB Conditional Access mechanisms are supported. Authentication and the collection of other user-specific information can be handled by a service-related application, for example using HbbTV.

--

How does DVB-I relate to HbbTV?

DVB-I and HbbTV are complementary solutions.

A DVB-I service list can include both broadcast and DVB-DASH broadband services that have an associated HbbTV 'red button' application. Furthermore, a DVB-I service list can include services that are themselves an HbbTV app, where the app takes the responsibility for presenting the video and audio.

--

How does DVB-I relate to 5G?

DVB-I uses generic web-based protocols and does not rely on any specific characteristics of 5G. It could serve as a network-agnostic specification for service discovery, installation and delivery of television services, including as a service layer on top of 5G.

--

More information on DVB-I