1、 ETSI TS 103 286-3 V1.1.1 (2015-05) Digital Video Broadcasting (DVB); Companion Screens and Streams; Part 3: Discovery TECHNICAL SPECIFICATION ETSI ETSI TS 103 286-3 V1.1.1 (2015-05)2 Reference DTS/JTC-DVB-343-3 Keywords broadcast, companion screen, synchronization, TV ETSI 650 Route des Lucioles F-
2、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-sea
3、rch 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 betwee
4、n 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. Informati
5、on on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp 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 Notification N
6、o 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 copyright and the f
7、oregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2015. European Broadcasting Union 2015. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Tr
8、ade 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 103 286-3 V1.1.1 (2015-05)3 Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs terminolo
9、gy 4g3Introduction 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 7g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 Overview 9g34.1 Introduction 9g34.2 UPnP Device Architecture 9g34.3 UPnP Application Management . 10g34.4 CSS-
10、CII interface mapping on Application Management 11g34.5 CSA behaviour . 12g35 UPnP Device requirements for the TV Device 14g3History 15g3ETSI ETSI TS 103 286-3 V1.1.1 (2015-05)4 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETS
11、I. 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 potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is availab
12、le from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/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 referenced in ETSI SR 000 3
13、14 (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 Europen de Normalisation ELECtr
14、otechnique (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 became a tripartite body by in
15、cluding 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 the technical, legal, progra
16、mme-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 Founded in September 1993,
17、 the DVB Project is a market-led consortium of public and private sector organizations in the television industry. Its aim is to establish the framework for the introduction of MPEG-2 based digital television services. Now comprising over 200 organizations from more than 25 countries around the worl
18、d, DVB fosters market-led systems, which meet the real needs, and economic circumstances, of the consumer electronics and the broadcast industry. The present document is part 3 of a multi-part deliverable covering the DVB Companion Screens and Streams Specification, as identified below: Part 1: “Con
19、cepts, roles and overall architecture“; Part 2: “Content Identification and Media Synchronization“; Part 3: “Discovery“. 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 de
20、scribed 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 103 286-3 V1.1.1 (2015-05)5 Introduction It is assumed that the reader is familiar with parts
21、 1 and 2 of this multi-part deliverable that provide background information on the concepts covered in the present document. Personal, smart devices like tablet computers and smart phones enable new user experiences for broadcast service consumption. Many of these new experiences require communicati
22、on via an IP network between applications or services on a TV Device and Companion Screen Applications (CSAs) on a personal device. An application or service typically needs to know the network location to direct communications to if it is to reach the intended application or service on the intended
23、 device. A location is, at minimum, described by the assigned network IP address and may also include other details such as an IP port number or a resource identifying path. On a home IP network, the devices are typically assigned network addresses by means of static addressing or dynamic allocation
24、 via the Dynamic Host Configuration Protocol (DHCP). Hence, it is not known in advance which addresses should be used for communication. It is also not desirable to expect the user to have knowledge of network addresses and to input these into the device. The present document describes the technolog
25、y used to establish communication between the TV Device and CSA on a companion device without prior knowledge of the assignment of network addresses. This enables a CSA to establish communication with the TV Device via interfaces defined in other parts of this specifications series and therefore to
26、provide the experiences that those interfaces enable. The technology used to achieve this is Universal Plug and Play (UPnP) and it is assumed that the reader is familiar with architecture and technologies used in UPnP (1 and 2). ETSI ETSI TS 103 286-3 V1.1.1 (2015-05)6 1 Scope The present document s
27、pecifies the architecture and protocols for discovering TV Devices in the home that implement, interfaces defined in the other parts of this multi-part deliverable. The discovery protocol is used by the Companion Screen Application to detect TV Devices. The discovery protocol supplies the informatio
28、n so that the following interfaces can be used over the established link: the interfaces between the TV Device and the Companion Screen Application: - interface for metadata exchange, including content identification (CSS-CII); - interface for Wall Clock synchronization (CSS-WC); - interface for Tim
29、eline Synchronization (CSS-TS); - interface for notification of Trigger Events (CSS_TE). The interfaces themselves are described in clauses 6, 8, 9 and 10 of ETSI TS 103 286-2 4. Note that Wall Clock synchronization and Timeline Synchronization interfaces are (currently) discovered indirectly. The p
30、resent document defines the means to discover the CSS-CII interface. The other interfaces are then discovered by means of the established connection for the CSS-CII interface and this is defined in ETSI TS 103 286-2 4. The present document does not describe: The UPnP Device Architecture 1. The UPnP
31、Application Management service 2. How to establish communication through a web socket 3. 2 References 2.1 Normative 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 a
32、pplies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents 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 t
33、his clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. 1 ISO/IEC 29341-1:2011: “Information technology - UPnP Device Architecture - Part 1: UPnP Device Architectur
34、e Version 1.0“. NOTE: This specification was first published by UPnP in 2008, and an equivalent version is available from http:/upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0.pdf. 2 UPnP Forum (September 2014): “ApplicationManagement:1 Service“. NOTE: Available at: http:/upnp.org/specs/ms/UPn
35、P-ms-ApplicationManagement-v1-Service.pdf. This specification is expected to be published by ISO/IEC, though this has not happened at the time of publication of the present document. 3 IETF RFC 6455 (December 2011): “The WebSocket Protocol“. NOTE: Available at http:/tools.ietf.org/html/rfc6455. ETSI
36、 ETSI TS 103 286-3 V1.1.1 (2015-05)7 4 ETSI TS 103 286-2: “Digital Video Broadcasting (DVB); Companion Screens and Streams; Part 2: Content Identification and Media Synchronization“. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or
37、 version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cann
38、ot 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 a particular subject area. i.1 ETSI TS 103 286-1: “Digital Video Broadcasting (DVB); Companion Screens and Streams; Part 1:
39、Concepts, roles and overall architecture“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: action: named subroutine NOTE: This is UPnP terminology. The action is based on the RPC mechanism defined in the UDA. AppInf
40、oList: XML document which describes an application NOTE: This is UPnP terminology specific to the Application Management DCP. application: software program designed to perform an activity NOTE: This is UPnP terminology. Application Management DCP: UPnP DCP that allows applications to be installed, s
41、tarted and stopped by UPnP Actions NOTE: This is UPnP terminology. app-to-app communication: communication between two applications not using the UPnP Device Architecture NOTE: This is terminology from the specification of the UPnP Application Management service definition for a protocol that is out
42、 of band with respect to the UPnP Device Architecture. connectionAddress: connection end point of the protocol NOTE: This is UPnP terminology. It is the name of an XML property in the AppInfoList. Control Point: UPnP client NOTE: This is UPnP terminology. A Control Point represents the client side o
43、f the client server solution defined by the UPnP Device Architecture. ControlURL: HTTP end point for SOAP actions for the UPnP Service NOTE: This is UPnP terminology. The controlURL is conveyed in a DDD. event: notification of a state change from a UPnP Device to a Control Point NOTE: This is UPnP t
44、erminology. ETSI ETSI TS 103 286-3 V1.1.1 (2015-05)8 M-Search: mechanism to search for a UPnP Device or UPnP Service NOTE: This is UPnP terminology. M-Search is part of SSDP discovery protocol. matchingProtocolName: identification of the supported protocol over the connection NOTE: This is UPnP term
45、inology. It is the name of an XML property in the AppInfoList. runningStatus: identification of the status of the application NOTE: This is UPnP terminology. It is the name of an XML property in the AppInfoList. response: UPnP Device created result including output parameters as result of an action
46、invocation request: invocation of an action by Control Point describing which action is being called on the UPnP Device including the input parameters UPnP Device: logical UPnP entity on the network that exposes functionality through UPnP Services. NOTE: This is UPnP terminology. A UPnP Device can u
47、niquely be identified on the network by means of an UDN. UPnP Device Type: definition of the type of a UPnP Device NOTE: This is UPnP terminology. UPnP Device Types can mandate implementation of specific UPnP Services. UPnP Service: logical collection of UPnP Actions and State variables that makes u
48、p functionality in a domain NOTE: This is UPnP terminology. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CSA Companion Screen Application CSS Companion Screens and Streams CSS-CII Interface for Content Identification and other Information DCP Device
49、Control Protocol DHCP Dynamic Host Configuration Protocol DDD Device Description Document GENA General Event Notification Architecture HTTP Hypertext Transfer Protocol IP Internet Protocol MPEG Multimedia Pictures Expert Group RPC Remote Procedure Call NOTE: UPnP uses SOAP as RPC mechanism. SCPD Service Control Protocol Description SOAP Simple Object Access Protocol. NOTE: SOAP is the definition of how to model an RPC subroutine in XML. SSDP Simple Service Discovery Protocol TCP Transmiss
