scope:

The present document contains the specification for the remote management and firmware update system for DVB IPTV services and forms an addendum to the DVB IPTV Handbook ETSI TS 102 034 [1]. All aspects of the RMS and FUS functionality which are standardized by DVB are described within this single common document, but since the RMS and associated FUS service is specified to be directly associated with the DVB IPTV Handbook ETSI TS 102 034 [1] some direct references to parts of that specification are included. The association with [1] does not prevent the present document partially or completely being used in conjunction with other IPTV delivery services.

Remote Management is the ability of a server entity outside the home environment to monitor and configure the devices within the home and covers provisioning and assurance tasks. It optionally includes firmware updates to the equipment.

The remote management entity is referred to as the Remote Management System (RMS) and the firmware update capability as the Firmware Update System (FUS).

This updated version of the document also now includes:

• Addition of specific RMS-FUS payloadID for DVBSTP announcement messages (0xB2).

• The definition of the data model extension objects to support the DVB Content Delivery System specific functionality, intended to be used in conjunction with the data models for IPTV CPEs defined by other organization, e.g. Broadband Forum, Cablelabs.

• An annex defining the way in which the DVB specific data model objects may work within the Broadband Forum data model. Similar modelling could be for data models from other standards organizations but that has not been done in the present document.

• DVB RMS-FUS profiling of the authentication method specified for the SAP multicast protocol for carrying the firmware update announcement messages.

• An extension to the metadata which may support usage of multiple file objects in a single carousel (FLUTE or DSM-CC), and multiple DSM-CC data components within a service for firmware update delivery.

• Profiling of the dvb-mcast URI specific to each delivery protocol, allowing support for usage of multiple file objects in a single delivery carousel (FLUTE or DSM-CC), multiple DSM-CC data components within a service for firmware update delivery and multiple channels for FLUTE.

The present document is intended to provide additional functionality that may be used in conjunction with existing RMS specifications standardized by other bodies and primarily focuses on defining a multicast firmware update capability. A description of the additional functionality for an RMS interface based on the Broadband Forum TR-069 framework is presented in annex A.

The targeting of the firmware updates may include all the devices in the home environment if the CE manufacturer supplies updates. It should be noted that the method presented in the present document does not preclude delivery to home network devices which would potentially be "hidden" behind a gateway device in future phases.

The term "CPE" has been adopted in the present document in preference to the more well-known DVB-IPI terms "HNED" (Home Network End Device) and "DNG" (Delivery Network Gateway) in order to take other DVB devices such as the home network devices currently being specified by DVB-IPI HN task force into account. Both DNG and HNED are included in the scope of CPE in this context.

The logical architecture required to realise the RMS and FUS environments is described in the present document. The RMS and FUS may be provided by the same or different agencies, and may be co-located. The entities identified as building blocks of RMS and FUS are logical entities rather than physical devices, and a single manufacturer could integrate multiple logical entities into a single physical device.

The RMS and the FUS service may be provided by the service provider, network operator or a third party on an agreed contract basis.

Note that there may be several CE manufacturers contributing firmware files, and several FUSs, which may be managed by one or more RMSs (but with only one active management service at a time for any single CPE) delivered through multiple networks to the various populations of CPEs. However, some rules on prioritization in terms of CPE management are defined within the present document.

The options for delivery of the update files over the IPTV delivery network to the CPEs are specified in the present document in the following clauses.

Security is an important aspect of all communications in an IP environment and the requirements for and methods of securely either exchanging messaging or sending firmware update payloads are described in each clause of the present document where it is possible and in a way appropriate to the part of the specification. These are referenced to a central clause describing the principles used within the present document. However, it is not intended for carrying the most secure downloads, such as those where DRM related or contractual conditions apply.

Packaging and authentication of firmware updates delivered over multicast DVBSTP is not specified in the present document, it is assumed that those functions will be defined at a manufacturer-specific level.