1、 ETSI TS 102 824 V2.1.1 (2016-04) Digital Video Broadcasting (DVB); Remote Management and Firmware Update System for DVB IPTV Services (Phase 2) TECHNICAL SPECIFICATION ETSI ETSI TS 102 824 V2.1.1 (2016-04)2 Reference RTS/JTC-DVB-358 Keywords broadcasting, digital, DVB, IP ETSI 650 Route des Luciole
2、s F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards
3、-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents be
4、tween such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Infor
5、mation on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright
6、Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyr
7、ight and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. European Broadcasting Union 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM
8、and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 102 824 V2.1.1 (2016-04)3 Contents Intellectual Property Rights 7g3Foreword . 7g3Modal ver
9、bs terminology 7g31 Scope 8g32 References 9g32.1 Normative references 9g32.2 Informative references . 11g33 Definitions, abbreviations and notations 11g33.1 Definitions . 11g33.2 Abbreviations 12g33.3 Notations . 13g33.3.1 Augmented Backus-Naur Form (ABNF) . 13g34 Reference Model 14g34.0 Overview .
10、14g34.1 Modes of operation 15g34.1.0 Characteristics of RMS and FUS entities 15g34.1.1 RMS-only mode . 15g34.1.2 RMS-FUS mode 16g34.1.3 FUS-only mode 16g34.2 Type of firmware update files . 17g34.3 The role of the entities in the RMS-FUS architecture . 17g34.3.0 Overview . 17g34.3.1 CPEs 17g34.3.2 R
11、MS Administrator 17g34.3.3 RMS . 18g34.3.4 CE manufacturer 18g34.3.5 FUS 19g34.4 Control priorities of RMS vs. FUS-only . 19g34.5 CPE Bootstrap process 20g34.5.1 FUSS Process (Managed and unmanaged CPEs) 20g34.5.2 Process after FUSS (Managed CPEs) 20g34.6 Running state behaviour of CPEs 21g34.6.1 Un
12、managed CPEs 21g34.6.2 Managed CPEs. 21g35 The RMS-FUS sub-systems . 21g35.0 Reference architecture . 21g35.1 Interfaces overview . 22g35.2 The Remote Management System (RMS) . 23g35.2.0 General . 23g35.2.1 Communication with RMS administration 23g35.2.2 Management of the inventory 23g35.2.3 CPE man
13、agement interface 23g35.2.4 Processing of metadata and communication with the FUS (interface 4) . 24g35.3 The Firmware Update System (FUS) 24g35.3.0 General . 24g35.3.1 FUS manager and storage modules 24g35.3.2 Signalling and messaging to enable CPEs to locate updates . 26g35.3.2.0 Ways of signallin
14、g and messaging . 26g35.3.2.1 Multicast announcement service 26g35.3.2.2 Unicast query/response channel (QRC) . 26g35.3.3 Firmware update delivery 26g35.3.3.0 Delivery modes 26g35.3.3.1 Delivery failure in a managed environment . 27g35.3.3.2 Delivery failure in an unmanaged environment . 27g3ETSI ET
15、SI TS 102 824 V2.1.1 (2016-04)4 5.4 Secure Message Exchange and Secure Network Time 27g35.4.0 Provisioning requirements . 27g35.4.1 Secure Message Exchange . 27g35.4.2 Secure Network Time 28g36 The interfaces . 28g36.0 Characteristics of interfaces 28g36.1 Interface 1 - Firmware Update file from CE
16、manufacturer to FUS manager 29g36.1.0 General . 29g36.1.1 Payload coding and format 29g36.2 Interface 2 - Associated metadata from CE manufacturer to FUS manager 29g36.3 Interface 3 - CE manufacturer to RMS 29g36.4 Interface 4 - RMS-FUS control interface 30g36.5 Interface 5 - Multicast delivery of f
17、irmware update file to network 30g36.5.0 Supported protocols . 30g36.5.1 Payload coding and format 30g36.5.2 Security 30g36.5.3 Delivery protocol . 30g36.5.3.0 Recommended protocols 30g36.5.3.1 FLUTE . 31g36.5.3.1.0 Introduction 31g36.5.3.1.1 Profiling of FLUTE file download mechanism in DVB IPI Fir
18、mware Update Service . 31g36.5.3.1.2 FLUTE session description in DVB IPI Firmware Update Service . 32g36.5.3.2 DSM-CC 32g36.6 Interface 6 - Unicast delivery of firmware update file to network 32g36.6.0 Introduction 32g36.6.1 Payload coding and format 32g36.6.2 Security 33g36.6.2.0 Recommendations 3
19、3g36.6.2.1 HyperText Transport Protocol (HTTP) 33g36.6.2.2 File Transfer Protocol (FTP) 33g36.6.2.3 Trivial File Transfer Protocol (TFTP) 33g36.6.3 Delivery protocol . 33g36.7 Interface 7 - Firmware Update announcement service 33g36.7.0 Types of announcements . 33g36.7.1 Download discovery navigatio
20、n using the multicast announcement message service . 34g36.7.2 Carriage of multicast announcement over SAP transport 37g36.7.2.0 General . 37g36.7.2.1 Coding of Session Announcement Protocol . 37g36.7.2.1.0 Coding principles 37g36.7.2.1.1 Limitations 37g36.7.2.1.2 Authentication method to be used in
21、 SAP payload 38g36.7.2.2 Payload coding of SDP header . 38g36.7.2.3 Coding of media sections . 40g36.7.2.4 IP address range options . 40g36.7.2.5 Security 40g36.7.3 Carriage over DVBSTP . 40g36.7.3.0 Coding principles . 40g36.7.3.1 Coding of DVBSTP . 40g36.7.3.2 Payload coding for DVBSTP . 41g36.7.3
22、.3 IP address options for DVBSTP . 41g36.7.3.4 Security 41g36.8 Interface 8 - Query/response interface from FUS to home environment (QRC) . 41g36.8.0 General . 41g36.8.1 Download discovery navigation using the unicast query/response channel 42g36.8.2 Payload coding and format 42g36.8.2.0 Introductio
23、n 42g36.8.2.1 FirmwareUpdateCheck/FirmwareUpdateCheckResponse . 42g36.8.3 Security 44g36.8.4 Delivery protocol . 44g36.8.5 Message back-off and retry strategy 45g36.9 Interface 9 - CPE management interface . 45g3ETSI ETSI TS 102 824 V2.1.1 (2016-04)5 6.9.0 Introduction 45g36.9.1 Management interface
24、 requirements 45g36.9.2 Security 45g36.9.3 Delivery protocol . 45g36.10 Interface 10 - RMS management and control 45g36.11 Interface 11 - FUS control interface and file management interface . 45g36.12 Interface 12 - Update file streaming to delivery formatter 45g36.13 Interface 13 - RMS device regis
25、tration 46g37 Data Model . 46g3Annex A (normative): Use of TR-069 / CWMP for DVB RMS-FUS . 47g3A.0 Introduction 47g3A.1 Reference specifications within the TR-069 framework 47g3A.2 CWMP Remote Procedure Calls 47g3A.2.0 Introduction . 47g3A.2.1 RPCs required at the RMS and CPE side by TR-069 Framewor
26、k 48g3A.2.2 RPCs optional at the RMS and CPE side by TR-069 Framework . 48g3A.3 Remote Management functionality using CWMP . 49g3A.3.1 How to exploit CWMP for DVB remote management functions 49g3A.3.2 Examples of firmware update tasks in a managed environment 50g3Annex B (normative): Metadata schema
27、 . 51g3B.0 General . 51g3B.1 Textual representation of XML schema Fipi-rms_phase2_2009-1“ 51g3B.2 Textual representation of XML schema “ipi-rms_phase3_2012-09“ . 61g3Annex C (normative): Uniform Resource Identifier (URI) scheme for the connection to a multicast service . 70g3C.0 General . 70g3C.1 Ba
28、sic DVB-MCAST URI scheme 70g3C.2 RMS-FUS usage of DVB-MCAST URI scheme for DVBSTP . 70g3C.3 RMS-FUS usage of DVB-MCAST URI scheme for SAP . 71g3C.4 RMS-FUS usage of DVB-MCAST URI scheme for DSM-CC . 71g3C.5 RMS-FUS usage of DVB-MCAST URI scheme for FLUTE 71g3Annex D (normative): SDP attributes 73g3D
29、.0 DVB RMS specific attributes . 73g3D.1 FLUTE specific attributes (multicast update announcement) 74g3D.2 DSM-CC specific attributes (multicast update announcement) . 75g3D.3 SAP media type usage (pointer announcement) . 76g3D.4 DVBSTP media type usage (pointer announcement) . 77g3D.5 Query announc
30、ement 77g3D.6 Unicast announcement . 78g3D.7 Target filtering attributes 79g3D.7.0 Media description attributes 79g3D.7.1 CE manufacturer filter . 79g3D.7.2 Device class filter 79g3D.7.3 Device group filter. 80g3ETSI ETSI TS 102 824 V2.1.1 (2016-04)6 Annex E (normative): DVB specific data model exte
31、nsions required for DVB Content Download Service . 81g3E.0 General . 81g3E.1 CDS Push Service storage management. 81g3E.2 CDS Pull Service storage management 81g3Annex F (normative): Extension of TR-069 / CWMP to carry DVB specific Content Download Service data model extensions 83g3F.0 General . 83g
32、3F.1 Rationale for the chosen solution and guidelines for implementation . 84g3F.2 DVB data model extensions . 86g3F.3 Remote Management functionality using CWMP . 87g3Annex G (informative): Bibliography . 88g3History 89g3ETSI ETSI TS 102 824 V2.1.1 (2016-04)7 Intellectual Property Rights IPRs essen
33、tial or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potential
34、ly Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No gua
35、rantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by Joint Technical Committee (JTC) Broa
36、dcast of the European Broadcasting Union (EBU), Comit Europen de Normalisation ELECtrotechnique (CENELEC) and the European Telecommunications Standards Institute (ETSI). NOTE: The EBU/ETSI JTC Broadcast was established in 1990 to co-ordinate the drafting of standards in the specific field of broadca
37、sting and related fields. Since 1995 the JTC Broadcast became a tripartite body by including in the Memorandum of Understanding also CENELEC, which is responsible for the standardization of radio and television receivers. The EBU is a professional association of broadcasting organizations whose work
38、 includes the co-ordination of its members activities in the technical, legal, programme-making and programme-exchange domains. The EBU has active members in about 60 countries in the European broadcasting area; its headquarters is in Geneva. European Broadcasting Union CH-1218 GRAND SACONNEX (Genev
39、a) Switzerland Tel: +41 22 717 21 11 Fax: +41 22 717 24 81 The Digital Video Broadcasting Project (DVB) is an industry-led consortium of broadcasters, manufacturers, network operators, software developers, regulatory bodies, content owners and others committed to designing global standards for the d
40、elivery of digital television and data services. DVB fosters market driven solutions that meet the needs and economic circumstances of broadcast industry stakeholders and consumers. DVB standards cover all aspects of digital television from transmission through interfacing, conditional access and in
41、teractivity for digital video, audio and data. The consortium came together in 1993 to provide global standardization, interoperability and future proof specifications. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“
42、, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 102 824 V2.1.1 (2016-04)8 1 Scope The present
43、 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 documen
44、t, 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 c
45、onjunction 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 manage
46、ment 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
47、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
48、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 a
49、nnouncement 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 fun
