ETSI TS 102 542-1-2016 Digital Video Broadcasting (DVB) Guidelines for the implementation of DVB-IPTV Phase 1 specifications Part 1 Core IPTV Functions (V2 1 1)《数字视频广播(DVB) 数字视频广播-_1.pdf

《ETSI TS 102 542-1-2016 Digital Video Broadcasting (DVB) Guidelines for the implementation of DVB-IPTV Phase 1 specifications Part 1 Core IPTV Functions (V2 1 1)《数字视频广播(DVB) 数字视频广播-_1.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 102 542-1-2016 Digital Video Broadcasting (DVB) Guidelines for the implementation of DVB-IPTV Phase 1 specifications Part 1 Core IPTV Functions (V2 1 1)《数字视频广播(DVB) 数字视频广播-_1.pdf（49页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 102 542-1 V2.1.1 (2016-04) Digital Video Broadcasting (DVB); Guidelines for the implementation of DVB-IPTV Phase 1 specifications; Part 1: Core IPTV Functions TECHNICAL SPECIFICATION ETSI ETSI TS 102 542-1 V2.1.1 (2016-04)2 Reference RTS/JTC-DVB-360-1 Keywords broadcasting, digital, DVB, IP

2、, TV, video ETSI 650 Route des Lucioles 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 downloa

3、ded from: http:/www.etsi.org/standards-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

4、or perceived difference in contents between 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

5、to revision or change of status. Information 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/Peopl

6、e/CommiteeSupportStaff.aspx Copyright 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 wr

7、itten authorization of ETSI. The copyright 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 f

8、or the benefit of its Members. 3GPPTM 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 542-1 V2.1.1 (2016-04)3 Contents Intellectual Pr

9、operty Rights 5g3Foreword . 5g3Modal verbs terminology 6g31 Scope 7g32 References 7g32.1 Normative references . 7g32.2 Informative references 7g33 Abbreviations . 8g34 Introduction 9g35 Turning on and Booting an HNED . 9g35.0 Workflow description . 9g35.1 Physical/MAC Layer Connection . 10g35.2 IP L

10、ayer connectivity via obtaining an IP Address 10g35.2.0 General remarks 10g35.2.1 Location of the DHCP Server - Bridged and Routed modes 10g35.2.1.0 Overview . 10g35.2.1.1 Bridged Mode . 11g35.2.1.2 Routed Mode . 12g35.2.2 Adding a New DHCP Class Option 12g35.3 FUS and RMS Discovery . 13g35.3.0 Work

11、flow steps . 13g35.3.1 HNED managed using Broadband Forum TR-069 methods 14g35.3.2 Unmanaged HNEDs . 15g35.4 Content Discovery 16g35.4.0 Processing steps 16g35.4.1 Content Discovery in Routed Mode with Local DHCP Server 16g35.4.2 Content Discovery in Routed Mode without DHCP Server . 17g35.5 Content

12、 Selection . 18g35.5.0 Ways of Accessing Content 18g35.5.1 Content Selection in Routed Mode with Local DHCP Server 18g35.5.2 Content Selection in Routed Mode without DHCP Server . 19g35.6 CellId Configuration. 19g36 SD Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI sta

13、ndards“, 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 guarantee can be given as to the existence of other IPRs not

14、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) Broadcast of the European Broadcasting Union (EBU), Comit Euro

15、pen 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 broadcasting and related fields. Since 1995 the JTC Broadcast bec

16、ame 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 includes the co-ordination of its members activities in t

17、he 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 (Geneva) Switzerland Tel: +41 22 717 21 11 Fax: +41 22 717 24 81

18、 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 delivery of digital television and data services. DVB foste

19、rs 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 interactivity for digital video, audio and data. The consort

20、ium came together in 1993 to provide global standardization, interoperability and future proof specifications. The present document is part 1 of a multi-part deliverable covering the Guidelines for the implementation of DVB-IPTV Phase 1 specifications, as identified below: Part 1: “Core IPTV Functio

21、ns“; Part 2: “Broadband Content Guide (BCG) and Content on Demand“; Part 3: “Error Recovery“; Sub-part 1: “Overview of DVB-IPTV Error Recovery“; Sub-part 2: “Application Layer - Forward Error Correction (AL-FEC)“; Sub-part 3: “Retransmission (RET)“; Part 4: “Remote Management and Firmware Update“; P

22、art 5: “Content Download Service (CDS)“. ETSI ETSI TS 102 542-1 V2.1.1 (2016-04)6 Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Draft

23、ing 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 542-1 V2.1.1 (2016-04)7 1 Scope The present document is designed as a companion document to help implement the DVB-IPTV Phase 1

24、version 6: ETSI TS 102 034 1, which is referred to as the DVB-IPTV handbook. The present document is the part 1 of the Guidelines and is focusing on the core IPTV functions. Other parts present other aspects of the DVB-IPTV technologies. The present document is organized in separate sections in the

25、order of the boot-up sequence of the HNED rather than in the same section structure as the DVB-IPTV handbook. Each clause deals with a specific aspect of the DVB-IPTV technology, and offers explanations and examples not found in the DVB-IPTV handbook. 2 References 2.1 Normative references References

26、 are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documen

27、ts which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are

28、 necessary for the application of the present document. 1 ETSI TS 102 034 (V2.1.1): “Digital Video Broadcasting (DVB); Transport of MPEG-2 TS Based DVB Services over IP Based Networks“. 2 ETSI TS 101 154: “Digital Video Broadcasting (DVB); Specification for the use of Video and Audio Coding in Broad

29、casting Applications based on the MPEG-2 Transport Stream“. NOTE: The support of Scalable Video Codec (SVC) is not defined in the present document. 3 ETSI TS 102 824 (V1.1.1): “Digital Video Broadcasting (DVB); Remote Management and Firmware Update System for DVB IPTV Services (Phase 2)“. 4 SMPTE Sp

30、ecification 2022-1: “Forward Error Correction for Real-time Video/Audio Transport Over IP Networks“. 5 ETSI TS 102 905: “Digital Video Broadcasting (DVB); Technical Specification for DVB Services in the Home Network Phase 1“. 6 Broadband Forum TR-069 Amendment 4: “CPE WAN Management Protocol“, July

31、2011. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including

32、any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to

33、a particular subject area. i.1 IETF RFC 3927: “Dynamic Configuration of IPv4 Link-Local Addresses“. i.2 IETF RFC 3203: “DHCP reconfigure extension“. ETSI ETSI TS 102 542-1 V2.1.1 (2016-04)8 i.3 IEEE P802.11- 2012: “Standard for Information Technology - Telecommunications and information exchange bet

34、ween systems- Local and metropolitan area network- Specific requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications“. i.4 IEEE 802.1d (2004): “IEEE Standard for Local and metropolitan area networks: Media Access Control (MAC) Bridges“. i.5 IETF RFC 337

35、6: “Internet Group Management Protocol, Version 3“. i.6 IETF RFC 1112: “Host extensions for IP multicasting“. i.7 Void. i.8 ETSI TS 102 542-4: “Digital Video Broadcasting (DVB); Guidelines for the implementation of DVB-IPTV Phase 1 specifications; Part 4: Remote Management and Firmware Update“. i.9

36、IETF RFC 3810: “Multicast Listener Discovery Version 2 (MLDv2) for IPv6“. 3 Abbreviations For the purposes of the present document, the following abbreviations apply: ALG Application Level Gateway BCG Broadband Content Guide BiM Binary MPEG format for XML CPE Customer Premises Equipment CRLF Carriag

37、e Return Line Feed DHCP Dynamic Host Configuration Protocol DNG Delivery Network Gateway DSCP Differentiated Services CodePoint DSL Digital Subscriber Line DVB Digital Video Broadcasting DVBSTP DVB SD the remote management authority to be changed for a managed HNED where the ProductClass and Hardwar

38、eVersion are compatible; to allow a managed HNED to be made unmanaged; to allow an unmanaged HNED to be made to be managed. 5.3.1 HNED managed using Broadband Forum TR-069 methods Following the FUSS acquisition process for a managed HNED the RMS will be used to manage firmware updates possibly throu

39、gh the FUS and HNED configuration changes so the requirement is for the HNED to contact the RMS. This process will be described fully in the documentation specific to the RMS methods used, where the RMS is compliant with the Broadband Forum methods. This description is carried in section 3.1 of TR-0

40、69 6. The RMS can configure the entry into the FUS announcement service using the DVB extensions described in ETSI TS 102 824 3. ETSI ETSI TS 102 542-1 V2.1.1 (2016-04)15 5.3.2 Unmanaged HNEDs In the case of an unmanaged HNED one of the options for locating the FUSS should give a result in the form

41、of either a unicast or multicast URL. Figure 5.6: Options for locating the FUSS The URI provided in the FUS Stub file may be either unicast or multicast with the options below: The unicast URL may: - point directly to a file image for downloading from the FUS directly (e.g. http:/ The Multicast URL

42、will be based on the “dvb-mcast“ URI scheme as described in clause G.3 of ETSI TS 102 034 1, and may: - point directly to a file image for downloading from the FUS directly (e.g. dvb-mcast:/ - If SDP/SAP is used as the protocol may provide: square4 location of the announcement message specific to th

43、e update image available; square4 location of the entry point of the announcement message hierarchy, may be useful to point to wider populations (not completely populated ID info in FUSS); square4 location of an intermediate pointer message based on wider targeting, may be useful to point to wider p

44、opulations (not completely populated ID info in FUSS). - If DVBSTP is used the protocol may provide: square4 location of the XML description announcement message specific to the update image available. The HNED should be able to locate the firmware update using announcement description on the addres

45、ses provided. The detailed description of those operations is provided in ETSI TS 102 824 3 and the associated guidelines in ETSI TS 102 542-4 i.8. Acquire FUS StubPayloadId = 0x08SegmentId = 0Transport protocol = multicast (DVBSTP)Transport protocol = multicast (DVBSTP) or unicast (HTTP(S)Transport

46、 protocol = multicast (DVBSTP) or unicast (HTTP(S)Transport protocol = unicast (HTTP(S)Unicast URL of update file, transport = HTTP(S)Multicast address of:- Specific description announcement message (dvb-mcast URI)- Pointer message to multicast announcement (dvb-mcast URI)- Entry point to multicast

47、announcement hierarchy (dvb-mcast URI)Link mechanisms into RMS-FUS areaUsage described in TS 102 824 Multicast address of update file (dvb-mcast URI)ETSI ETSI TS 102 542-1 V2.1.1 (2016-04)16 Where the address leads to the entry point of the announcement hierarchy or an intermediate pointer further n

48、avigation will be needed. The capability to associate a firmware update with a specific group of HNEDs can be supported at all these levels with different levels of flexibility. 5.4 Content Discovery 5.4.0 Processing steps Now that the HNEDs have their IP address and that they have performed the FUS

49、 process (including firmware update if necessary), they start looking for the SD it is perfectly possible for the HNED to just join the corresponding multicast group. 5.5.1 Content Selection in Routed Mode with Local DHCP Server The multicast join message is sent on the HN, and the gateway forwards it to the access network. Thus the Live TV stream can be received by the HNED. DNG HNED 2 HNED 1 Home Network Segment Access