BS ISO IEC 29341-20-11-2017 Information technology UPnP Device Architecture Audio video device control protocol Level 4 Connection manager service《信息技术 UPnP设备体系结构 音视频设备控制协议 第4级 连接管.pdf

《BS ISO IEC 29341-20-11-2017 Information technology UPnP Device Architecture Audio video device control protocol Level 4 Connection manager service《信息技术 UPnP设备体系结构 音视频设备控制协议 第4级 连接管.pdf》由会员分享，可在线阅读，更多相关《BS ISO IEC 29341-20-11-2017 Information technology UPnP Device Architecture Audio video device control protocol Level 4 Connection manager service《信息技术 UPnP设备体系结构 音视频设备控制协议 第4级 连接管.pdf（88页珍藏版）》请在麦多课文档分享上搜索。

1、Information technology UPnP Device ArchitecturePart 20-11: Audio video device control protocol Level 4 Connection manager serviceBS ISO/IEC 29341-20-11:2017BSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06Information technology UPnP Device Architecture Part 20-11: Aud

2、io video device control protocol Level 4 Connection manager serviceTechnologies de linformation Architecture de dispositif UPnP Partie 20-11: Protocole de contrle de dispositif audio-vido Niveau 4 Service de gestionnaire de connexionINTERNATIONAL STANDARDISO/IEC 29341-20-11Reference numberISO/IEC 29

3、341-20-11:2017(E)First edition2017-09 ISO/IEC 2017National forewordThis 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 represented on

4、 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 2017ISBN 978 0 580 90845 3

5、ICS 35.200Compliance 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 publicationDate Text affectedBRITISH STANDARDBS IS

6、O/IEC 293412011:2017Information technology UPnP Device Architecture Part 20-11: Audio video device control protocol Level 4 Connection manager serviceTechnologies de linformation Architecture de dispositif UPnP Partie 20-11: Protocole de contrle de dispositif audio-vido Niveau 4 Service de gestionna

7、ire de connexionINTERNATIONAL STANDARDISO/IEC 29341-20-11Reference numberISO/IEC 29341-20-11:2017(E)First edition2017-09 ISO/IEC 2017BS ISO/IEC 293412011:2017ii ISO/IEC 2017 All rights reservedCOPYRIGHT PROTECTED DOCUMENT ISO/IEC 2017, Published in SwitzerlandAll rights reserved. Unless otherwise sp

8、ecified, 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 either ISO at the address below or

9、 ISOs member body in the country of the requester.ISO copyright officeCh. de Blandonnet 8 CP 401CH-1214 Vernier, Geneva, SwitzerlandTel. +41 22 749 01 11Fax +41 22 749 09 47copyrightiso.orgwww.iso.orgISO/IEC 29341-20-11:2017(E)BS ISO/IEC 293412011:2017ii ISO/IEC 2017 All rights reservedCOPYRIGHT PRO

10、TECTED DOCUMENT ISO/IEC 2017, Published in SwitzerlandAll 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 posting on the internet or an intranet, without

11、 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 officeCh. de Blandonnet 8 CP 401CH-1214 Vernier, Geneva, SwitzerlandTel. +41 22 749 01 11Fax +41 22 749 09 47copyrightiso.orgwww.iso.orgISO/IE

12、C 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 Conventions . 5 4.1 Notation . 5 4.1.1 Data Types . 5 4.1.2 St

13、rings 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 Names, Namespace Versioning and Schema Versioning 13 4.3.3 N

14、amespace 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 Service Modeling Definitions 16 5.1 ServiceType 16 5.2 State

15、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_ConnectionStatus . 20 5.2.9 A_ARG_TYPE_ConnectionManager . 20 5.2.10

16、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_RenderingInfoList . 22 5.3 Eventing and Moderation . 28 5.

17、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 GetCurrentConnectionIDs() 32 5.4.6 GetCurrentConnectionInfo() . 33 5.4.7

18、 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.2 Implementation of PrepareForConnection() . 41 A.1.3 I

19、mplementation 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 ConnectionComplete() . 42 A.2.4 Automatic Connection Cleanup .

20、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 Connection Cleanup . 45 A.5 Application to Vendor-specifi

21、c 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 4thField . 54 C.2.2 IEC61883 Exception . 55 C.2.3 Formal EBNF for the 4

22、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 without ConnectionManagers . 58 C.5 PrepareForConnection() and C

23、onnectionComplete() . 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/IEC 29341-20-11:2017(E) iv ISO/IEC 2017 All rights reserve

24、d 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 Service Description 36 7 Test . 40 Annex A (normative) Protocol

25、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 to RTSP/RTP/UDP Streaming 42 A.2.1 ProtocolInfo Definitio

26、n 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 ProtocolInfo Definition 43 A.4.2 Implementation of Prepare

27、ForConnection() . 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 CLOCKSYNC feature, Version 1 47 Annex C (informative) Theor

28、y of Operation . 53 C.1 Purpose . 53 C.2 ProtocolInfo Concept . 53 C.2.1 4thField . 54 C.2.2 IEC61883 Exception . 55 C.2.3 Formal EBNF for the 4thfield 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 Co

29、nnection 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 General Usage Model . 59 C.5.4 Relationship to AVTransport an

30、d 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 . 66 C.7.1 Examples of CLOCKSYNC feature 67 Annex D (informat

31、ive) 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 Table 7 allowedValueList for A_ARG_TYPE_ConnectionStatus . 20 T

32、able 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 PrepareForConnection() . 31 Table 14 Arguments for ConnectionComplete()

33、. 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 for GetCurrentConnectionInfo() . 34 Table 20 Arguments for Get

34、RendererItemInfo() . 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 B.1 CM features 47 Table B.2 Required characteristics of th

35、e 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 . 54 BS ISO/IEC 293412011:2017ISO/IEC 29341-20-11:2017(E) vi IS

36、O/IEC 2017 All rights reserved Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of Interna

37、tional 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 international organizations, governmental and nongovernmental, in liaison wi

38、th 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 maintenance are described in the ISO/IEC Directives, Part 1. In

39、 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). Attention is drawn to the possibility that some of the elemen

40、ts 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 the Introduction and/or on the ISO list of patent declarations r

41、eceived (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 assess

42、ment, 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 PAS procedure, by joint technical committee ISO/IEC JTC 1, In

43、formation 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 found on the ISO web site. BS ISO/IEC 293412011:2017ISO/IEC 29341-

44、20-11:2017(E) vi ISO/IEC 2017 All rights reserved Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the dev

45、elopment 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 international organizations, governmental and nongovernme

46、ntal, 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 maintenance are described in the ISO/IEC Dir

47、ectives, 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). Attention is drawn to the possibility that

48、 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 the Introduction and/or on the ISO list of pa

49、tent 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 about ISOs adherence to the WTO principles in the Technical Barrier