scope:

The present document is an updated release of TS 102 034 "Transport of MPEG-2 TS Based Services over IP Based Networks"; it is referred to as DVB-IP phase 1.3 and provides extensions to the first set of standardized specifications published by DVB for deployments of DVB services over bi-directional IP networks.

Specifically, it adds support for the following new features:

• signalling of Logical Channel Numbers; the logical channel number is a number associated with a DVB-IP service indicating the ordering preferred by the Service Provider for presentation in a service list;

• signalling of availability of DVB-IP services based on the region in which the Home Network End Device is located;

• UDP only transport of DVB-IP services;

• optional Application Layer Forward Error Correction for DVB-IP services carried over RTP transport.

As in previous releases of TS 102 034, the DVB-IP phase 1.3 work is limited to DVB services [1] encapsulated in MPEG-2 TS [61] and covers both Live Media Broadcast services (i.e. TV or radio styles) Media Broadcast with Trick Modes and Content on Demand services (CoD) (see also clause 6.2). These specifications define the mechanisms required in order for a consumer to be able to buy a standard DVB Home Network End Device, take it home, plug it into an IP network, choose and consume DVB services available over the IP network. Clause 4 describes the architectural framework defined for this set of specifications and introduces a Home Network reference model. The contents of the remaining clauses are described below.

Scope of the present document

What is within the scope

The present document provides specifications to be supported on the interface to the HNED defined as IPI-1 in clause 4 and is based on IP version 4.

It provides a set of technical specifications which covers the following areas:

• The delivery of DVB MPEG-2 TS based services over bi-directional IP networks, both for Live Media Broadcast services (i.e. TV or radio styles) and Content on Demand services. Clause 7 on transport covers the encapsulation of MPEG-2 TS services for delivery over IP and the protocols to be used to access such services. Quality of Service is covered, based on Differentiated Services (DiffServ).

• The Service Discovery and Selection (SD&S) mechanism for DVB based A/V services over bi-directional IP networks. Clause 5 on SD&S defines the service discovery information, its data format and the protocols to use for carriage of this information. Both push and pull models of delivery are supported. Binarisation encoding of SD&S information is specified and can optionally be used if required. Support for advanced codecs, logical channel numbering and signalling regional DVB-IP services is provided.

• The use of command and control application-level protocol RTSP to control CoD services and optionally to join multicast services. This is covered in clause 6.

• Clause 8 deals with the assignment of an IP Address to a Home Network End Device (HNED) to get onto the network. The specification is based on DHCP and is restricted to the scenarios where an HNED has a single interface onto the home network and there is a single Delivery Network Gateway (DNG) per home network segment.

• Clause 9 covers an identification agent for the HNED. This agent provides a simple identification of the HNED to signal its existence to the Network Service Provider if requested.

• Network provisioning. Clause 10 covers an optional network management and provisioning agent. This agent allows a Network Service Provider to automatically provision the end device with additional functionalities. This clause will be deprecated in a future version of the present document when the DVB-IP Remote Management System specification becomes available.

• Discovery of Broadband Content Guides (inc. third party). The Broadband Content Guide itself is provided as a separate specification [71].

• Annex E defines an optional protocol for Application Layer FEC (AL-FEC) protection of streaming media for DVB-IP services carried over RTP transport. This AL-FEC protocol is a layered protocol with a base layer and an enhancement layer. The base layer is a simple packet-based interleaved parity code based on a subset of [76]. The base layer shall be used wherever AL-FEC is used. The enhancement layer is a Raptor code, as defined in [74] and [75] and may optionally be used to provide further packet loss protection.