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

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

1、Information technology UPnP Device ArchitecturePart 26-14: Telephony device control protocol Level 2 Address book serviceBS ISO/IEC 29341-26-14:2017BSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06Information technology UPnP Device Architecture Part 26-14: Telephony d

2、evice control protocol Level 2 Address book serviceTechnologies de linformation Architecture de dispositif UPnP Partie 26-14: Protocole de contrle de dispositif de tlphonie Niveau 2 Service de carnet dadressesINTERNATIONAL STANDARDISO/IEC 29341-26-14Reference numberISO/IEC 29341-26-14:2017(E)First e

3、dition2017-09 ISO/IEC 2017National forewordThis British Standard is the UK implementation of ISO/IEC 29341-26-14: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 o

4、btained 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 90892 7ICS 35.200Compliance wit

5、h 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 ISO/IEC 293412614:2017Info

6、rmation technology UPnP Device Architecture Part 26-14: Telephony device control protocol Level 2 Address book serviceTechnologies de linformation Architecture de dispositif UPnP Partie 26-14: Protocole de contrle de dispositif de tlphonie Niveau 2 Service de carnet dadressesINTERNATIONAL STANDARDIS

7、O/IEC 29341-26-14Reference numberISO/IEC 29341-26-14:2017(E)First edition2017-09 ISO/IEC 2017BS ISO/IEC 293412614:2017ii ISO/IEC 2017 All rights reservedCOPYRIGHT PROTECTED DOCUMENT ISO/IEC 2017, Published in SwitzerlandAll rights reserved. Unless otherwise specified, no part of this publication may

8、 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 country of the

9、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-26-14:2017(E)BS ISO/IEC 293412614:2017ii ISO/IEC 2017 All rights reservedCOPYRIGHT PROTECTED DOCUMENT ISO/IEC 2017, Published

10、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 prior written permission. Permission ca

11、n 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/IEC 29341-26-14:2017(E)ISO/IEC 29341-26-14

12、:2017(E) ISO/IEC 2017 All rights reserved iii CONTENTS 1 Scope. v 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 . 4 4.2 Vendor-defined Extensions . 4 5 Service Modeling Definitions 4 5.1 Service

13、Type 4 5.2 AddressBook Service Architecture 4 5.3 State Variables . 5 5.3.1 State Variable Overview 5 5.3.2 IncomingRequest 5 5.3.3 A_ARG_TYPE_IncomingRequests 7 5.3.4 A_ARG_TYPE_SharedContacts 8 5.3.5 A_ARG_TYPE_SharedInfo 9 5.3.6 A_ARG_TYPE_TargetContacts . 9 5.3.7 A_ARG_TYPE_ReqID 10 5.3.8 A_ARG_

14、TYPE_NetworkAddressBookID 10 5.4 Eventing and Moderation . 10 5.4.1 Eventing of IncomingRequest . 10 5.5 Actions 10 5.5.1 ShareContacts() . 11 5.5.2 FetchContactInfo() . 12 5.5.3 SharePCC() . 13 5.5.4 Accept() . 14 5.5.5 Reject() . 16 5.5.6 ImportContacts() 16 5.5.7 RetrieveIncomingRequests() 17 5.5

15、.8 Error Code Summary . 18 5.6 Service Behavioral Model 19 6 XML Service Description . 19 Annex A (normative) XML complex type peerType 22 Annex B (normative) XML Schema . 26 Annex C (informative) Theory of Operation . 28 Annex D (informative) Bibliography 32 Figure 1 AddressBook Service Architectur

16、e . 5 Figure C.1 Contact Share with WAN User . 28 Figure C.2 Handling of incoming contact share request . 29 Figure C.3 Fetching contact information from network address book . 30 Figure C.4 Sharing PCC information . 30 BS ISO/IEC 293412614:2017ISO/IEC 29341-26-14:2017(E) iv ISO/IEC 2017 All rights

17、reserved Figure C.5 Contact Invitation request handling 31 Table 1 State Variables . 5 Table 2 Event Moderation . 10 Table 3 Actions 10 Table 4 Arguments for ShareContacts() 11 Table 5 Error Codes for ShareContacts() 12 Table 6 Arguments for FetchcontactInfo() . 12 Table 7 Error Codes for FetchConta

18、ctInfo() . 13 Table 8 Arguments for SharePCC() . 13 Table 9 Error Codes for SharePCC() . 14 Table 10 Arguments for Accept () . 15 Table 11 Error Codes for Accept() 15 Table 12 Arguments for Reject() . 16 Table 13 Error Codes for Reject() . 16 Table 14 Arguments for ImportContacts() 16 Table 15 Error

19、 Codes for ImportContacts() 17 Table 16 Arguments for RetrieveIncomingRequests() 17 Table 17 Error Codes for RetrieveIncomingRequests() 18 Table 18 Error Code Summary 18 BS ISO/IEC 293412614:2017ISO/IEC 29341-26-14:2017(E) iv ISO/IEC 2017 All rights reserved Figure C.5 Contact Invitation request han

20、dling 31 Table 1 State Variables . 5 Table 2 Event Moderation . 10 Table 3 Actions 10 Table 4 Arguments for ShareContacts() 11 Table 5 Error Codes for ShareContacts() 12 Table 6 Arguments for FetchcontactInfo() . 12 Table 7 Error Codes for FetchContactInfo() . 13 Table 8 Arguments for SharePCC() . 1

21、3 Table 9 Error Codes for SharePCC() . 14 Table 10 Arguments for Accept () . 15 Table 11 Error Codes for Accept() 15 Table 12 Arguments for Reject() . 16 Table 13 Error Codes for Reject() . 16 Table 14 Arguments for ImportContacts() 16 Table 15 Error Codes for ImportContacts() 17 Table 16 Arguments

22、for RetrieveIncomingRequests() 17 Table 17 Error Codes for RetrieveIncomingRequests() 18 Table 18 Error Code Summary 18 ISO/IEC 29341-26-14:2017(E) ISO/IEC 2017 All rights reserved v Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commiss

23、ion) form the specialized 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 a

24、nd IEC technical 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/IE

25、C 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 different approval criteria needed for the different types of document should be noted. This document was drafted in accordance with

26、 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 be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. De

27、tails 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/patents). Any trade name used in this document is information given for the convenience of users and does not constitute an

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

29、plementary information ISO/IEC 293412614 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 se

30、ries, under the general title Information technology UPnP Device Architecture, can be found on the ISO web site. BS ISO/IEC 293412614:2017ISO/IEC 29341-26-14:2017(E) vi ISO/IEC 2017 All rights reserved Introduction ISO and IEC draw attention to the fact that it is claimed that compliance with this d

31、ocument 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 -these patent rights have assured ISO and IEC that they are willing to negotiate licenses under reasonable and non-discriminatory

32、 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 Corporation has informed IEC and ISO that it has patent applications or granted patents. Information may be obtained from: Intel Co

33、rporation 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 applications or granted patents as listed below: 6101499 / US; 6687755 / US; 6910068 / US; 7130895 / US; 6725281 / US; 7089307

34、/ 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 and ISO that it has patent applications or granted patents. Information may be obtained from: Philips International B.V. IP 66

35、87755 / 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 and ISO that it has patent applications or granted patents. Info

36、rmation 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 obtained from: Hewlett Packard Company 1501 Page Mill Road USA Palo Alto, CA 94304 Samsung Electronics Co. Ltd. has informed I

37、EC 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, Yeongtang-Gu, KR Suwon City 443-742 Huawei Technologies Co., Ltd. has informed IEC and ISO that it has patent applications or grant

38、ed patents. Information may be obtained from: Huawei Technologies Co., Ltd. Administration Building, Bantian Longgang District Shenzhen China 518129 Qualcomm Incorporated has informed IEC and ISO that it has patent applications or granted patents. Information may be obtained from: Qualcomm Incorpora

39、ted 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 from: Telecom Italia S.p.A. Via Reiss Romoli, 274 Turin - Italy 10148 Cisco Systems informed IEC and ISO that it has patent a

40、pplications 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

41、 not be held responsible for identifying any or all such patent rights. BS ISO/IEC 293412614:2017ISO/IEC 29341-26-14:2017(E) viii ISO/IEC 2017 All rights reserved Original UPnP Document Reference may be made in this document to original UPnP documents. These references are retained in order to maint

42、ain consistency between the specifications as published by ISO/IEC and by UPnP Implementers Corporation and later by UPnP Forum. The following table indicates the original UPnP document titles and the corresponding part of ISO/IEC 29341: UPnP Document Title ISO/IEC 29341 Part UPnP Device Architectur

43、e 1.0 ISO/IEC 29341-1:2008 UPnP Device Architecture Version 1.0 ISO/IEC 29341-1:2011 UPnP Device Architecture 1.1 ISO/IEC 29341-1-1:2011 UPnP Device Architecture 2.0 ISO/IEC 29341-1-2 UPnP Basic:1 Device ISO/IEC 29341-2 UPnP AV Architecture:1 ISO/IEC 29341-3-1:2008 UPnP AV Architecture:1 ISO/IEC 293

44、41-3-1:2011 UPnP AVTransport:1 Service ISO/IEC 29341-3-10 UPnP ConnectionManager:1 Service ISO/IEC 29341-3-11 UPnP ContentDirectory:1 Service ISO/IEC 29341-3-12 UPnP RenderingControl:1 Service ISO/IEC 29341-3-13 UPnP MediaRenderer:1 Device ISO/IEC 29341-3-2 UPnP MediaRenderer:2 Device ISO/IEC 29341-

45、3-2:2011 UPnP MediaServer:1 Device ISO/IEC 29341-3-3 UPnP AVTransport:2 Service ISO/IEC 29341-4-10:2008 UPnP AVTransport:2 Service ISO/IEC 29341-4-10:2011 UPnP ConnectionManager:2 Service ISO/IEC 29341-4-11:2008 UPnP ConnectionManager:2 Service ISO/IEC 29341-4-11:2011 UPnP ContentDirectory:2 Service

46、 ISO/IEC 29341-4-12 UPnP RenderingControl:2 Service ISO/IEC 29341-4-13:2008 UPnP RenderingControl:2 Service ISO/IEC 29341-4-13:2011 UPnP ScheduledRecording:1 ISO/IEC 29341-4-14 UPnP ScheduledRecording:2 ISO/IEC 29341-4-14:2011 UPnP MediaRenderer:2 Device ISO/IEC 29341-4-2 UPnP MediaServer:2 Device I

47、SO/IEC 29341-4-3 UPnP AV Datastructure Template:1 ISO/IEC 29341-4-4:2008 UPnP AV Datastructure Template:1 ISO/IEC 29341-4-4:2011 UPnP DigitalSecurityCamera:1 Device ISO/IEC 29341-5-1 UPnP DigitalSecurityCameraMotionImage:1 Service ISO/IEC 29341-5-10 UPnP DigitalSecurityCameraSettings:1 Service ISO/I

48、EC 29341-5-11 UPnP DigitalSecurityCameraStillImage:1 Service ISO/IEC 29341-5-12 UPnP HVAC_System:1 Device ISO/IEC 29341-6-1 UPnP ControlValve:1 Service ISO/IEC 29341-6-10 UPnP HVAC_FanOperatingMode:1 Service ISO/IEC 29341-6-11 UPnP FanSpeed:1 Service ISO/IEC 29341-6-12 UPnP HouseStatus:1 Service ISO

49、/IEC 29341-6-13 UPnP HVAC_SetpointSchedule:1 Service ISO/IEC 29341-6-14 UPnP TemperatureSensor:1 Service ISO/IEC 29341-6-15 UPnP TemperatureSetpoint:1 Service ISO/IEC 29341-6-16 BS ISO/IEC 293412614:2017ISO/IEC 29341-26-14:2017(E) viii ISO/IEC 2017 All rights reserved Original UPnP Document Reference may be made in this document to original UPnP documents. These refe