BS ISO IEC 29341-26-12-2017 Information technology UPnP Device Architecture Telephony device control protocol Level 2 Messaging service《信息技术 UPnP设备体系结构 电话设备控制协议 第2级 信息服务》.pdf

《BS ISO IEC 29341-26-12-2017 Information technology UPnP Device Architecture Telephony device control protocol Level 2 Messaging service《信息技术 UPnP设备体系结构 电话设备控制协议 第2级 信息服务》.pdf》由会员分享，可在线阅读，更多相关《BS ISO IEC 29341-26-12-2017 Information technology UPnP Device Architecture Telephony device control protocol Level 2 Messaging service《信息技术 UPnP设备体系结构 电话设备控制协议 第2级 信息服务》.pdf（86页珍藏版）》请在麦多课文档分享上搜索。

1、Information technology UPnP Device Architecture Part 26-12: Telephony device control protocol Level 2 Messaging service BS ISO/IEC 29341-26-12:2017 BSI Standards Publication WB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06Information technology UPnP Device Architecture Part 26-12: Telephony

2、device control protocol Level 2 Messaging service Technologies de linformation Architecture de dispositif UPnP Partie 26-12: Protocole de contrle de dispositif de tlphonie Niveau 2 Service de messagerie INTERNATIONAL STANDARD ISO/IEC 29341-26-12 Reference number ISO/IEC 29341-26-12:2017(E) First edi

3、tion 2017-09 ISO/IEC 2017 National foreword This British Standard is the UK implementation of ISO/IEC 29341-26-12:2017. The UK participation in its preparation was entrusted to Technical Committee ICT/-/1, Information systems co-ordination. A list of organizations represented on this committee can b

4、e 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 978 0 580 90889 7 ICS 35.200 Complia

5、nce 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 affected BRITISH STANDARD BS ISO/IEC 293412

6、612:2017Information technology UPnP Device Architecture Part 26-12: Telephony device control protocol Level 2 Messaging service Technologies de linformation Architecture de dispositif UPnP Partie 26-12: Protocole de contrle de dispositif de tlphonie Niveau 2 Service de messagerie INTERNATIONAL STAND

7、ARD ISO/IEC 29341-26-12 Reference number ISO/IEC 29341-26-12:2017(E) First edition 2017-09 ISO/IEC 2017 BS ISO/IEC 293412612:2017 ii 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 p

8、ublication 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 ISOs member body in the c

9、ountry 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-26-12:2017(E) BS ISO/IEC 293412612:2017 ii ISO/IEC 2017 All rights reserved COPYRIGHT PROTECTED DOCUMENT

10、 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 posting on the internet or an intranet, without prior written

11、 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 Fax +41 22 749 09 47 copyrightiso.org www.iso.org ISO/IEC 2934

12、1-26-12:2017(E) ISO/IEC 29341-26-12:2017(E) ISO/IEC 2017 All rights reserved iii CONTENTS 1 Scope vi 2 Normative references 1 3 Terms, definitions, symbols and abbreviated terms 2 4 Notations and conventions . 4 4.1 Text conventions 4 4.2 Data Types . 4 4.3 Vendor-defined Extensions . 5 5 Service Mo

13、deling Definitions 5 5.1 Service Type 5 5.2 Messaging Service Architecture 5 5.3 State Variables . 6 5.3.1 State Variable Overview 6 5.3.2 A_ARG_TYPE_MessagingCapabilities 7 5.3.3 NewMessages 8 5.3.4 SessionUpdates 9 5.3.5 A_ARG_TYPE_TelephonyServerIdentity 10 5.3.6 A_ARG_TYPE_MessageID . 10 5.3.7 A

14、_ARG_TYPE_MessageClass . 11 5.3.8 A_ARG_TYPE_MessageFolder 11 5.3.9 A_ARG_TYPE_MessageStatus 12 5.3.10 A_ARG_TYPE_Message 12 5.3.11 A_ARG_TYPE_MessageList . 15 5.3.12 A_ARG_TYPE_SessionID 16 5.3.13 A_ARG_TYPE_SessionClass . 16 5.3.14 A_ARG_TYPE_RecipientsList 17 5.3.15 A_ARG_TYPE_SessionInfo 18 5.3.

15、16 A_ARG_TYPE_SessionsList 20 5.3.17 A_ARG_TYPE_SupportedContentType 21 5.3.18 A_ARG_TYPE_Subject 22 5.3.19 A_ARG_TYPE_SessionStatus 22 5.3.20 A_ARG_TYPE_FileInfoList . 22 5.4 Eventing and Moderation . 24 5.4.1 Eventing of NewMessages . 24 5.4.2 Eventing of SessionUpdates . 24 5.5 Actions 25 5.5.1 G

16、etTelephonyIdentity() . 26 5.5.2 GetMessagingCapabilities() . 27 5.5.3 GetNewMessages() 28 5.5.4 SearchMessages() . 29 5.5.5 ReadMessage() . 30 5.5.6 SendMessage() 31 5.5.7 DeleteMessage() 33 5.5.8 CreateSession() . 34 BS ISO/IEC 293412612:2017ISO/IEC 29341-26-12:2017(E) iv ISO/IEC 2017 All rights r

17、eserved 5.5.9 ModifySession() . 35 5.5.10 AcceptSession() . 36 5.5.11 GetSessionUpdates() . 37 5.5.12 GetSessions() 38 5.5.13 JoinSession() . 39 5.5.14 LeaveSession() 40 5.5.15 CloseSession() 41 5.5.16 StartFileTransfer() . 42 5.5.17 CancelFileTransfer() 43 5.5.18 GetFileTransferSession() . 44 5.5.1

18、9 Error Code Summary . 45 5.6 Service Behavioral Model 46 5.6.1 State Diagrams 46 6 XML Service Description . 47 Annex A (normative) XML complex type peerType 56 Annex B (normative) XML Schema . 60 Annex C (informative) Theory of Operation . 64 Annex D (informative) Bibliography 69 Figure 1 Architec

19、ture of the Messaging Service . 5 Figure 2 Lifecycle of Messages . 46 Figure 3 Lifecycle of Sessions 47 Figure C.1 Message handling . 64 Figure C.2 Session handling in the Session Mode Messaging . 66 Figure C.3 Incoming Session handling in the Session Mode Messaging. 66 Figure C.4 File Transfer Sess

20、ion handling 67 Figure C.5 File Transfer Session handling 68 Table 1 State Variables . 6 Table 2 Allowed values for sessionEvent and the corresponding values of the sessionStatus 9 Table 3 allowedValueList for the A_ARG_TYPE_MessageClass state variable 11 Table 4 allowedValueList for the A_ARG_TYPE_

21、MessageFolder state variable . 12 Table 5 allowedValueList for the A_ARG_TYPE_MessageStatus state variable . 12 Table 6 allowedValueList for the A_ARG_TYPE_SessionClass state variable 16 Table 7 allowedValueList for the A_ARG_TYPE_SessionStatus state variable . 22 Table 8 Event Moderation . 24 Table

22、 9 Actions 25 Table 10 Arguments for GetTelephonyIdentity() 26 Table 11 Error Codes for GetTelephonyIdentity() 27 Table 12 Arguments for GetMessagingCapabilities() . 27 Table 13 Error Codes for GetMessagingCapabilities() . 28 Table 14 Arguments for GetNewMessages() . 28 Table 15 Error Codes for GetN

23、ewMessages 29 BS ISO/IEC 293412612:2017ISO/IEC 29341-26-12:2017(E) iv ISO/IEC 2017 All rights reserved 5.5.9 ModifySession() . 35 5.5.10 AcceptSession() . 36 5.5.11 GetSessionUpdates() . 37 5.5.12 GetSessions() 38 5.5.13 JoinSession() . 39 5.5.14 LeaveSession() 40 5.5.15 CloseSession() 41 5.5.16 Sta

24、rtFileTransfer() . 42 5.5.17 CancelFileTransfer() 43 5.5.18 GetFileTransferSession() . 44 5.5.19 Error Code Summary . 45 5.6 Service Behavioral Model 46 5.6.1 State Diagrams 46 6 XML Service Description . 47 Annex A (normative) XML complex type peerType 56 Annex B (normative) XML Schema . 60 Annex C

25、 (informative) Theory of Operation . 64 Annex D (informative) Bibliography 69 Figure 1 Architecture of the Messaging Service . 5 Figure 2 Lifecycle of Messages . 46 Figure 3 Lifecycle of Sessions 47 Figure C.1 Message handling . 64 Figure C.2 Session handling in the Session Mode Messaging . 66 Figur

26、e C.3 Incoming Session handling in the Session Mode Messaging. 66 Figure C.4 File Transfer Session handling 67 Figure C.5 File Transfer Session handling 68 Table 1 State Variables . 6 Table 2 Allowed values for sessionEvent and the corresponding values of the sessionStatus 9 Table 3 allowedValueList

27、 for the A_ARG_TYPE_MessageClass state variable 11 Table 4 allowedValueList for the A_ARG_TYPE_MessageFolder state variable . 12 Table 5 allowedValueList for the A_ARG_TYPE_MessageStatus state variable . 12 Table 6 allowedValueList for the A_ARG_TYPE_SessionClass state variable 16 Table 7 allowedVal

28、ueList for the A_ARG_TYPE_SessionStatus state variable . 22 Table 8 Event Moderation . 24 Table 9 Actions 25 Table 10 Arguments for GetTelephonyIdentity() 26 Table 11 Error Codes for GetTelephonyIdentity() 27 Table 12 Arguments for GetMessagingCapabilities() . 27 Table 13 Error Codes for GetMessagin

29、gCapabilities() . 28 Table 14 Arguments for GetNewMessages() . 28 Table 15 Error Codes for GetNewMessages 29 ISO/IEC 29341-26-12:2017(E) ISO/IEC 2017 All rights reserved v Table 16 Arguments for SearchMessages() . 29 Table 17 Error Codes for SearchMessages() . 30 Table 18 Arguments for ReadMessage()

30、 . 31 Table 19 Error Codes for ReadMessage() . 31 Table 20 Arguments for SendMessage() . 32 Table 21 Error Codes for SendMessage() . 33 Table 22 Arguments for DeleteMessage() . 33 Table 23 Error Codes for DeleteMessage() . 34 Table 24 Arguments for CreateSession() 34 Table 25 Error Codes for CreateS

31、ession() 35 Table 26 Arguments for ModifySession() . 35 Table 27 Error Codes for ModifySession() . 36 Table 28 Arguments for AcceptSession() 36 Table 29 Error Codes for AcceptSession() 37 Table 30 Arguments for GetSessionUpdates() . 37 Table 31 Error Codes for GetSessionUpdates() 38 Table 32 Argumen

32、ts for GetSessions() . 38 Table 33 Error Codes for GetSessions() . 39 Table 34 Arguments for JoinSession() 39 Table 35 Error Codes for JoinSession() 40 Table 36 Arguments for LeaveSession() . 40 Table 37 Error Codes for LeaveSession() . 41 Table 38 Arguments for CloseSession() 41 Table 39 Error Code

33、s for CloseSession() 42 Table 40 Arguments for StartFileTransfer() . 42 Table 41 Error Codes for StartFileTransfer() . 43 Table 42 Arguments for CancelFileTransfer() 43 Table 43 Error Codes for CancelFileTransfer() 44 Table 44 Arguments for GetFileTransferSession() . 44 Table 45 Error Codes for GetF

34、ileTransferSession() . 45 Table 46 Error Code Summary 45 BS ISO/IEC 293412612:2017ISO/IEC 29341-26-12: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

35、worldwide standardization. National 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 collabora

36、te in fields of mutual interest. Other international 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 devel

37、op this document and those intended 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 D

38、irectives, Part 2 (see http:/www.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 res ponsible for identifying any or all such patent rights. Details of any patent rights identif i

39、ed during the development of the document 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

40、 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 Barriers to Trade (TBT) see the following URL: Foreword Supplementary information ISO/IEC 2934

41、12612 was prepared by UPnP Forum and adopted, under the 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 Infor

42、mation technology UPnP Device Architecture, can be found on the ISO web site. BS ISO/IEC 293412612:2017ISO/IEC 29341-26-12:2017(E) vi ISO/IEC 2017 All rights reserved Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the sp

43、ecialized system for worldwide standardization. National 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

44、 committees collaborate in fields of mutual interest. Other international 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 pro

45、cedures used to develop this document and those intended 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 r

46、ules of the ISO/IEC Directives, Part 2 (see http:/www.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 res ponsible for identifying any or all such patent rights. Details of any pa

47、tent rights identif ied during the development of the document 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.

48、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 Barriers to Trade (TBT) see the following URL: Foreword Supplementary inf

49、ormation ISO/IEC 293412612 was prepared by UPnP Forum and adopted, under the 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 Info