1、Information technology UPnP Device Architecture Part 20-11: Audio video device control protocol Level 4 Connection manager service BS ISO/IEC 29341-20-11:2017 BSI Standards Publication WB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06Information technology UPnP Device Architecture Part 20-11:
2、 Audio video device control protocol Level 4 Connection manager service Technologies de linformation Architecture de dispositif UPnP Partie 20-11: Protocole de contrle de dispositif audio-vido Niveau 4 Service de gestionnaire de connexion INTERNATIONAL STANDARD ISO/IEC 29341-20-11 Reference number I
3、SO/IEC 29341-20-11:2017(E) First edition 2017-09 ISO/IEC 2017 National foreword This British Standard is the UK implementation of ISO/IEC 29341-20-11:2017. The UK participation in its preparation was entrusted to Technical Committee ICT/-/1, Information systems co-ordination. A list of organizations
4、 represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2017 Published by BSI Standards Limited 2017 ISBN
5、978 0 580 90845 3 ICS 35.200 Compliance with a British Standard cannot confer immunity from legal obligations. This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 September 2017. Amendments/corrigenda issued since publication Date Text affecte
6、d BRITISH STANDARD BS ISO/IEC 293412011:2017Information technology UPnP Device Architecture Part 20-11: Audio video device control protocol Level 4 Connection manager service Technologies de linformation Architecture de dispositif UPnP Partie 20-11: Protocole de contrle de dispositif audio-vido Nive
7、au 4 Service de gestionnaire de connexion INTERNATIONAL STANDARD ISO/IEC 29341-20-11 Reference number ISO/IEC 29341-20-11:2017(E) First edition 2017-09 ISO/IEC 2017 BS ISO/IEC 293412011:2017 ii ISO/IEC 2017 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2017, Published in Switzerland All r
8、ights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from
9、 either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Ch. de Blandonnet 8 CP 401 CH-1214 Vernier, Geneva, Switzerland Tel. +41 22 749 01 11 Fax +41 22 749 09 47 copyrightiso.org www.iso.org ISO/IEC 29341-20-11:2017(E) BS ISO/IEC 293412011:2017 ii
10、ISO/IEC 2017 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2017, Published in Switzerland All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or
11、posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Ch. de Blandonnet 8 CP 401 CH-1214 Vernier, Geneva, Switzerland Tel. +41 22 749 01 11 F
12、ax +41 22 749 09 47 copyrightiso.org www.iso.org ISO/IEC 29341-20-11:2017(E) ISO/IEC 29341-20-11:2017(E) ISO/IEC 2017 All rights reserved iii CONTENTS 1 Scope vi 2 Normative references 1 3 Terms, definitions, symbols and abbreviations 4 3.1 Provisioning terms 4 3.2 Symbols . 5 4 Notations and Conven
13、tions . 5 4.1 Notation . 5 4.1.1 Data Types . 5 4.1.2 Strings Embedded in Other Strings 6 4.1.3 Extended Backus-Naur Form . 6 4.2 Derived Data Types 7 4.2.1 Summary 7 4.2.2 CSV Lists 7 4.3 Management of XML Namespaces in Standardized DCPs 8 4.3.1 Namespace Prefix Requirements 12 4.3.2 Namespace Name
14、s, Namespace Versioning and Schema Versioning 13 4.3.3 Namespace Usage Examples . 15 4.4 Vendor-defined Extensions 15 4.4.1 Vendor-defined Action Names 15 4.4.2 Vendor-defined State Variable Names 15 4.4.3 Vendor-defined XML Elements and attributes 16 4.4.4 Vendor-defined Property Names . 16 5 Servi
15、ce Modeling Definitions 16 5.1 ServiceType 16 5.2 State Variables 17 5.2.1 State Variable Overview . 17 5.2.2 SourceProtocolInfo . 17 5.2.3 SinkProtocolInfo . 18 5.2.4 CurrentConnectionIDs 18 5.2.5 FeatureList 18 5.2.6 ClockUpdateID . 18 5.2.7 DeviceClockInfoUpdates 19 5.2.8 A_ARG_TYPE_ConnectionSta
16、tus . 20 5.2.9 A_ARG_TYPE_ConnectionManager . 20 5.2.10 A_ARG_TYPE_Direction 20 5.2.11 A_ARG_TYPE_ProtocolInfo 20 5.2.12 A_ARG_TYPE_ConnectionID . 20 5.2.13 A_ARG_TYPE_AVTransportID . 20 5.2.14 A_ARG_TYPE_RcsID . 21 5.2.15 A_ARG_TYPE_ItemInfoFilter 21 5.2.16 A_ARG_TYPE_Result 22 5.2.17 A_ARG_TYPE_Re
17、nderingInfoList . 22 5.3 Eventing and Moderation . 28 5.4 Actions 28 5.4.1 Action Overview . 28 5.4.2 GetProtocolInfo() . 29 BS ISO/IEC 293412011:2017ISO/IEC 29341-20-11:2017(E) iv ISO/IEC 2017 All rights reserved 5.4.3 PrepareForConnection() . 29 5.4.4 ConnectionComplete() 31 5.4.5 GetCurrentConnec
18、tionIDs() 32 5.4.6 GetCurrentConnectionInfo() . 33 5.4.7 GetRendererItemInfo() . 34 5.4.8 GetFeatureList() . 35 5.4.9 Common Error Codes . 35 6 XML Service Description 36 7 Test . 40 Annex A (normative) Protocol Specifics . 41 A.1 Application to HTTP Streaming 41 A.1.1 ProtocolInfo Definition 41 A.1
19、.2 Implementation of PrepareForConnection() . 41 A.1.3 Implementation of ConnectionComplete() . 41 A.1.4 Automatic Connection Cleanup . 41 A.2 Application to RTSP/RTP/UDP Streaming 42 A.2.1 ProtocolInfo Definition 42 A.2.2 Implementation of PrepareForConnection() . 42 A.2.3 Implementation of Connect
20、ionComplete() . 42 A.2.4 Automatic Connection Cleanup . 42 A.3 Application to Device-Internal Streaming 42 A.4 Application to IEC61883 Streaming 43 A.4.1 ProtocolInfo Definition 43 A.4.2 Implementation of PrepareForConnection() . 44 A.4.3 Implementation of ConnectionComplete() . 45 A.4.4 Automatic C
21、onnection Cleanup . 45 A.5 Application to Vendor-specific Streaming 46 Annex B (normative) CM features 47 B.1 Introduction . 47 B.2 Requirements for the CLOCKSYNC feature, Version 1 47 Annex C (informative) Theory of Operation . 53 C.1 Purpose . 53 C.2 ProtocolInfo Concept . 53 C.2.1 4 thField . 54
22、C.2.2 IEC61883 Exception . 55 C.2.3 Formal EBNF for the 4 thfield 55 C.2.4 ProtocolInfo Conventions for Protected Content 56 C.3 Typical Control Point Operations 57 C.3.1 Introduction 57 C.3.2 Establishing a New Connection 57 C.3.3 Dealing with Ongoing Connections . 58 C.4 Relation to Devices withou
23、t ConnectionManagers . 58 C.5 PrepareForConnection() and ConnectionComplete() . 59 C.5.1 PrepareForConnection() . 59 C.5.2 ConnectionComplete() 59 C.5.3 General Usage Model . 59 C.5.4 Relationship to AVTransport and RenderingControl Services. 60 C.5.5 ConnectionIDs . 60 BS ISO/IEC 293412011:2017ISO/
24、IEC 29341-20-11:2017(E) iv ISO/IEC 2017 All rights reserved 5.4.3 PrepareForConnection() . 29 5.4.4 ConnectionComplete() 31 5.4.5 GetCurrentConnectionIDs() 32 5.4.6 GetCurrentConnectionInfo() . 33 5.4.7 GetRendererItemInfo() . 34 5.4.8 GetFeatureList() . 35 5.4.9 Common Error Codes . 35 6 XML Servic
25、e Description 36 7 Test . 40 Annex A (normative) Protocol Specifics . 41 A.1 Application to HTTP Streaming 41 A.1.1 ProtocolInfo Definition 41 A.1.2 Implementation of PrepareForConnection() . 41 A.1.3 Implementation of ConnectionComplete() . 41 A.1.4 Automatic Connection Cleanup . 41 A.2 Application
26、 to RTSP/RTP/UDP Streaming 42 A.2.1 ProtocolInfo Definition 42 A.2.2 Implementation of PrepareForConnection() . 42 A.2.3 Implementation of ConnectionComplete() . 42 A.2.4 Automatic Connection Cleanup . 42 A.3 Application to Device-Internal Streaming 42 A.4 Application to IEC61883 Streaming 43 A.4.1
27、ProtocolInfo Definition 43 A.4.2 Implementation of PrepareForConnection() . 44 A.4.3 Implementation of ConnectionComplete() . 45 A.4.4 Automatic Connection Cleanup . 45 A.5 Application to Vendor-specific Streaming 46 Annex B (normative) CM features 47 B.1 Introduction . 47 B.2 Requirements for the C
28、LOCKSYNC feature, Version 1 47 Annex C (informative) Theory of Operation . 53 C.1 Purpose . 53 C.2 ProtocolInfo Concept . 53 C.2.1 4 thField . 54 C.2.2 IEC61883 Exception . 55 C.2.3 Formal EBNF for the 4 thfield 55 C.2.4 ProtocolInfo Conventions for Protected Content 56 C.3 Typical Control Point Ope
29、rations 57 C.3.1 Introduction 57 C.3.2 Establishing a New Connection 57 C.3.3 Dealing with Ongoing Connections . 58 C.4 Relation to Devices without ConnectionManagers . 58 C.5 PrepareForConnection() and ConnectionComplete() . 59 C.5.1 PrepareForConnection() . 59 C.5.2 ConnectionComplete() 59 C.5.3 G
30、eneral Usage Model . 59 C.5.4 Relationship to AVTransport and RenderingControl Services. 60 C.5.5 ConnectionIDs . 60 ISO/IEC 29341-20-11:2017(E) ISO/IEC 2017 All rights reserved v C.5.6 AVTransportIDs and RcsIDs . 61 C.6 Determining if ContentDirectory items are playable . 61 C.7 CLOCKSYNC feature .
31、 66 C.7.1 Examples of CLOCKSYNC feature 67 Annex D (informative) Bibliography 70 List of Tables Table 1 EBNF Operators 7 Table 2 CSV Examples 8 Table 3 Namespace Definitions 9 Table 4 Schema-related Information 11 Table 5 Default Namespaces for the AV Specifications 13 Table 6 State Variables 17 Tab
32、le 7 allowedValueList for A_ARG_TYPE_ConnectionStatus . 20 Table 8 allowedValueList for A_ARG_TYPE_Direction . 20 Table 9 Event Moderation . 28 Table 10 Actions . 28 Table 11 Arguments for GetProtocolInfo() . 29 Table 12 Arguments for PrepareForConnection() . 30 Table 13 Error Codes for PrepareForCo
33、nnection() . 31 Table 14 Arguments for ConnectionComplete() . 32 Table 15 Error Codes for ConnectionComplete() . 32 Table 16 Arguments for GetCurrentConnectionIDs() 32 Table 17 Error Codes for GetCurrentConnectionIDs() 33 Table 18 Arguments for GetCurrentConnectionInfo() . 33 Table 19 Error Codes fo
34、r GetCurrentConnectionInfo() . 34 Table 20 Arguments for GetRendererItemInfo() . 34 Table 21 Error Codes for GetRendererItemInfo() . 35 Table 22 Arguments for GetFeatureList(). 35 Table 23 Error Codes for GetFeatureList() . 35 Table 24 Common Error Codes . 36 Table A.1 for Protocol IEC61883 44 Table
35、 B.1 CM features 47 Table B.2 Required characteristics of the CLOCKSYNC feature element 49 Table B.3 Allowed values for the element . 50 Table B.4 Allowed formats for the element. 51 Table B.5 Allowed values for the element. 51 Table C.1 Defined Protocols and their associated ProtocolInfo Values . 5
36、4 BS ISO/IEC 293412011:2017ISO/IEC 29341-20-11:2017(E) vi ISO/IEC 2017 All rights reserved Foreword ISO (the International Organization for Standardization) and IE C (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are me
37、mbers of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other inte rnational
38、organizations, governmental and nongovernmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. The procedures used to develop this document and those intended for its further m
39、aintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of document should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see http:/www.iso.org/directives).
40、 Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be in th
41、e Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents). Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement. For an explanation on the voluntary nature of Standard, the meaning of the I
42、SO specific terms and expressions related to conformity assessment, as well as information about ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the following URL: Foreword Supplementary information ISO/IEC 293412011 was prepared by UPnP Forum and adopted, under the
43、 PAS procedure, by joint technical committee ISO/IEC JTC 1, Information technology, in parallel with its approval by national bodies of ISO and IEC. The list of all currently available parts of ISO/IEC 29341 series, under the general title Information technology UPnP Device Architecture, can be foun
44、d on the ISO web site. BS ISO/IEC 293412011:2017ISO/IEC 29341-20-11:2017(E) vi ISO/IEC 2017 All rights reserved Foreword ISO (the International Organization for Standardization) and IE C (the International Electrotechnical Commission) form the specialized system for worldwide standardization. Nation
45、al bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest.
46、Other inte rnational organizations, governmental and nongovernmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. The procedures used to develop this document and those inten
47、ded for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of document should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see http:/www
48、.iso.org/directives). Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the d
49、ocument will be in the Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents). Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement. For an explanation on the voluntary nature of Standard, the meaning of the ISO specific terms and expressions related to conformity assessment, as well as information abo
