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

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

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

2、evice control protocol Level 2 Calendar service Technologies de linformation Architecture de dispositif UPnP Partie 26-15: Protocole de contrle de dispositif de tlphonie Niveau 2 Service de calendrier INTERNATIONAL STANDARD ISO/IEC 29341-26-15 Reference number ISO/IEC 29341-26-15:2017(E) First editi

3、on 2017-09 ISO/IEC 2017 National foreword This British Standard is the UK implementation of ISO/IEC 29341-26-15: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 be

4、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 90893 4 ICS 35.200 Complianc

5、e 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 29341261

6、5:2017Information technology UPnP Device Architecture Part 26-15: Telephony device control protocol Level 2 Calendar service Technologies de linformation Architecture de dispositif UPnP Partie 26-15: Protocole de contrle de dispositif de tlphonie Niveau 2 Service de calendrier INTERNATIONAL STANDARD

7、 ISO/IEC 29341-26-15 Reference number ISO/IEC 29341-26-15:2017(E) First edition 2017-09 ISO/IEC 2017 BS ISO/IEC 293412615: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 publ

8、ication 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 coun

9、try 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-15:2017(E) BS ISO/IEC 293412615:2017 ii ISO/IEC 2017 All rights reserved COPYRIGHT PROTECTED DOCUMENT IS

10、O/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 pe

11、rmission. 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 29341-2

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

13、ling Definitions 4 5.1 Service Type 4 5.2 Calendar Service Architecture 4 5.3 State Variables . 5 5.3.1 State Variable Overview 5 5.3.2 CalendarItem 6 5.3.3 TriggeredItem . 6 5.3.4 MemoInfo 7 5.3.5 A_ARG_TYPE_TriggeredItems 8 5.3.6 A_ARG_TYPE_CalItems . 8 5.3.7 A_ARG_TYPE_ItemIDs . 9 5.3.8 A_ARG_TYP

14、E_Memo 10 5.3.9 A_ARG_TYPE_MemoID . 10 5.3.10 A_ARG_TYPE_ItemDeliveryMethod . 10 5.3.11 A_ARG_TYPE_MemoInfoList . 11 5.3.12 A_ARG_TYPE_TelCPName . 12 5.3.13 A_ARG_TYPE_TelCPNameList 12 5.3.14 A_ARG_TYPE_Expires 12 5.4 Eventing and Moderation . 12 5.4.1 Eventing of CalendarItem . 13 5.4.2 Eventing of

15、 TriggeredItem 13 5.4.3 Eventing of MemoInfo 13 5.5 Actions 13 5.5.1 AddCalendarItems() . 14 5.5.2 DeleteCalendarItems() . 15 5.5.3 UpdateCalendarItems() 15 5.5.4 GetCalendarItems() 16 5.5.5 GetTriggeredItems() . 17 5.5.6 PostMemo() . 18 5.5.7 RegisterItemDelivery() . 19 5.5.8 GetMemo() 20 5.5.9 Reg

16、isterTelCPName() 21 5.5.10 UnregisterTelCPName() . 22 5.5.11 GetTelCPNameList() 23 5.5.12 Error Code Summary . 24 5.6 Service Behavioral Model 24 BS ISO/IEC 293412615:2017ISO/IEC 29341-26-15:2017(E) iv ISO/IEC 2017 All rights reserved 6 XML Service Description . 24 Annex A (normative) XML Schema . 2

17、9 Annex B (informative) Theory of Operation . 32 Annex C (informative) Bibliography 36 Figure 1 Calendar Service Architecture 4 Figure B.1 Memo handling 32 Figure B.2 Logical flows for calendar service 34 Figure B.3 Multiple TelCP handling for Alarm use case . 35 Table 1 State Variables . 5 Table 2

18、Event Moderation . 12 Table 3 Actions 13 Table 4 Arguments for AddCalendarItems(). 14 Table 5 Error Codes for AddCalendarItems() 14 Table 6 Arguments for DeleteCalendarItems() . 15 Table 7 Error Codes for DeleteCalendarItems() . 15 Table 8 Arguments for UpdateCalendarItems() 15 Table 9 Error Codes f

19、or UpdateCalendarItems() 16 Table 10 Arguments for GetCalendarItems() . 16 Table 11 Error Codes for GetCalendarItems() . 17 Table 12 Arguments for GetTriggeredItems() 17 Table 13 Error Codes for GetTriggeredItems() 18 Table 14 Arguments for PostMemo() . 18 Table 15 Error Codes for PostMemo() . 19 Ta

20、ble 16 Arguments for RegisterItemDelivery() . 19 Table 17 Error Codes for RegisterItemDelivery() . 20 Table 18 Arguments for GetMemo() 20 Table 19 Error Codes for GetMemo() 21 Table 20 Arguments for RegisterTelCPName() 21 Table 21 Error Codes for RegisterTelCPName() 22 Table 22 Arguments for Unregis

21、terTelCPName() . 22 Table 23 Error Codes for UnregisterTelCPName() . 23 Table 24 Arguments for GetTelCPNameList() 23 Table 25 Error Codes for GetTelCPNameList() 23 Table 26 Error Code Summary 24 BS ISO/IEC 293412615:2017ISO/IEC 29341-26-15:2017(E) iv ISO/IEC 2017 All rights reserved 6 XML Service De

22、scription . 24 Annex A (normative) XML Schema . 29 Annex B (informative) Theory of Operation . 32 Annex C (informative) Bibliography 36 Figure 1 Calendar Service Architecture 4 Figure B.1 Memo handling 32 Figure B.2 Logical flows for calendar service 34 Figure B.3 Multiple TelCP handling for Alarm u

23、se case . 35 Table 1 State Variables . 5 Table 2 Event Moderation . 12 Table 3 Actions 13 Table 4 Arguments for AddCalendarItems(). 14 Table 5 Error Codes for AddCalendarItems() 14 Table 6 Arguments for DeleteCalendarItems() . 15 Table 7 Error Codes for DeleteCalendarItems() . 15 Table 8 Arguments f

24、or UpdateCalendarItems() 15 Table 9 Error Codes for UpdateCalendarItems() 16 Table 10 Arguments for GetCalendarItems() . 16 Table 11 Error Codes for GetCalendarItems() . 17 Table 12 Arguments for GetTriggeredItems() 17 Table 13 Error Codes for GetTriggeredItems() 18 Table 14 Arguments for PostMemo()

25、 . 18 Table 15 Error Codes for PostMemo() . 19 Table 16 Arguments for RegisterItemDelivery() . 19 Table 17 Error Codes for RegisterItemDelivery() . 20 Table 18 Arguments for GetMemo() 20 Table 19 Error Codes for GetMemo() 21 Table 20 Arguments for RegisterTelCPName() 21 Table 21 Error Codes for Regi

26、sterTelCPName() 22 Table 22 Arguments for UnregisterTelCPName() . 22 Table 23 Error Codes for UnregisterTelCPName() . 23 Table 24 Arguments for GetTelCPNameList() 23 Table 25 Error Codes for GetTelCPNameList() 23 Table 26 Error Code Summary 24 ISO/IEC 29341-26-15:2017(E) ISO/IEC 2017 All rights rese

27、rved v 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 International Standards through

28、 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 with ISO and IEC, also tak

29、e 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 particular the differen

30、t 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 elements of this document may

31、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 received (see www.iso.org

32、/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 informa

33、tion about ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the following URL: Foreword Supplementary information ISO/IEC 293412615 was prepared by UPnP Forum and adopted, under the PAS procedure, by joint technical committee ISO/IEC JTC 1, Information technology, in

34、 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 293412615:2017ISO/IEC 29341-26-15:2017(E) vi ISO/IEC

35、 2017 All rights reserved Introduction ISO and IEC draw attention to the fact that it is claimed that compliance with this document may involve the use of patents as indicated below. ISO and IEC take no position concerning the evidence, validity and scope of these patent rights. The holders of -thes

36、e patent rights have assured ISO and IEC that they are willing to negotiate licenses under reasonable and non-discriminatory terms and conditions with applicants throughout the world. In this respect, the statements of the holders of these patent rights are registered with ISO and IEC. Intel Corpora

37、tion has informed IEC and ISO that it has patent applications or granted patents. Information may be obtained from: Intel Corporation Standards Licensing Department 5200 NE Elam Young Parkway MS: JFS-98 USA Hillsboro, Oregon 97124 Microsoft Corporation has informed IEC and ISO that it has patent app

38、lications or granted patents as listed below: 6101499 / US; 6687755 / US; 6910068 / US; 7130895 / US; 6725281 / US; 7089307 / US; 7069312 / US; 10/783 524 /US Information may be obtained from: Microsoft Corporation One Microsoft Way USA Redmond WA 98052 Philips International B.V. has informed IEC an

39、d ISO that it has patent applications or granted patents. Information may be obtained from: Philips International B.V. IP 6687755 / US; 6910068 / US; 7130895 / US; 6725281 / US; 7089307 / US; 7069312 / US; 10/783 524 /US Information may be obtained from: Microsoft Corporation One Microsoft Way USA R

40、edmond WA 98052 Philips International B.V. has informed IEC and ISO that it has patent applications or granted patents. Information may be obtained from: Philips International B.V. IP 6 170 007 / US; 6 139 177 / US; 6 529 936 / US; 6 470 339 / US; 6 571 388 / US; 6 205 466 / US Information may be ob

41、tained from: Hewlett Packard Company 1501 Page Mill Road USA Palo Alto, CA 94304 Samsung Electronics Co. Ltd. has informed IEC and ISO that it has patent applications or granted patents. Information may be obtained from: Digital Media Business, Samsung Electronics Co. Ltd. 416 Maetan-3 Dong, Yeongta

42、ng-Gu, KR Suwon City 443-742 Huawei Technologies Co., Ltd. has informed IEC and ISO that it has patent applications or granted patents. Information may be obtained from: Huawei Technologies Co., Ltd. Administration Building, Bantian Longgang District Shenzhen China 518129 Qualcomm Incorporated has i

43、nformed IEC and ISO that it has patent applications or granted patents. Information may be obtained from: Qualcomm Incorporated 5775 Morehouse Drive San Diego, CA USA 92121 Telecom Italia S.p.A.has informed IEC and ISO that it has patent applications or granted patents. Information may be obtained f

44、rom: Telecom Italia S.p.A. Via Reiss Romoli, 274 Turin - Italy 10148 Cisco Systems informed IEC and ISO that it has patent applications or granted patents. Information may be obtained from: Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA USA 95134 Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights other than those identified above. ISO and IEC shall not be held responsible for identifying any or all such patent rights. BS ISO/IEC 293412615:2017