1、Information technology UPnP Device ArchitecturePart 26-1: Telephony device control protocol Level 2 Telephony architectureBS ISO/IEC 29341-26-1:2017BSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06Information technology UPnP Device Architecture Part 26-1: Telephony de
2、vice control protocol Level 2 Telephony architectureTechnologies de linformation Architecture de dispositif UPnP Partie 26-1: Protocole de contrle de dispositif de tlphonie Niveau 2 Architecture de tlphonieINTERNATIONAL STANDARDISO/IEC29341-26-1Reference numberISO/IEC 29341-26-1:2017(E)First edition
3、2017-09 ISO/IEC 2017National forewordThis British Standard is the UK implementation of ISO/IEC 29341-26-1: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 obtained
4、 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 90865 1ICS 35.200Compliance with a Bri
5、tish 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 29341261:2017Information
6、technology UPnP Device Architecture Part 26-1: Telephony device control protocol Level 2 Telephony architectureTechnologies de linformation Architecture de dispositif UPnP Partie 26-1: Protocole de contrle de dispositif de tlphonie Niveau 2 Architecture de tlphonieINTERNATIONAL STANDARDISO/IEC29341-
7、26-1Reference numberISO/IEC 29341-26-1:2017(E)First edition2017-09 ISO/IEC 2017BS ISO/IEC 29341261: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 be reproduced
8、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 requester.ISO c
9、opyright 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-1:2017(E)BS ISO/IEC 29341261:2017ii ISO/IEC 2017 All rights reservedCOPYRIGHT PROTECTED DOCUMENT ISO/IEC 2017, Published in SwitzerlandAll
10、 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 can be requested fr
11、om 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-1:2017(E)ISO/IEC 29341-26-1:2017(E) ISO/IEC 20
12、17 All rights reserved iii CONTENTS 1 Scope. v 2 Normative references 1 3 Terms, definitions and abbreviated terms . 1 3.1 Provisioning terms 1 3.2 Symbols . 1 3.3 General telephony terms . 2 4 Text conventions . 2 5 Introduction . 2 6 Telephony Reference Architecture . 3 6.1 Telephony Basic Archite
13、cture Paradigm 3 6.2 Telephony Components Overview . 5 6.2.1 Call Management Service . 6 6.2.2 Media Management Service 7 6.2.3 Interaction of Media and Call Management Service . 7 6.2.4 Messaging Service 8 6.2.5 Presence Service 9 6.2.6 Calendar Service 9 6.2.7 Address Book Service 10 6.2.8 Phone M
14、anagement via Data Model . 10 6.2.9 InputConfig Service 11 6.2.10 Security . 12 Annex A (informative) Deployment Scenarios . 13 Annex B (informative) Bibliography 20 Figure 1 UPnP Telephony Basic Architecture . 3 Figure 2 Architecture with a Telephny Control Point (TelCP) on an independent Device (3
15、-Box Model) 4 Figure 3 Service Level Architectural View 4 Figure 4 UPnP Devices and Services for Telephony Architecture . 5 Figure 5 A Deployment Scenario with Two Telephony Server Devices in a Single Physical Box 6 Figure 6 Call Management Service 7 Figure 7 Media Management Service . 7 Figure 8 Ar
16、chitecture for Media Management Service . 8 Figure 9 Messaging Service Interaction Diagram 8 Figure 10 Architecture for Presence Service 9 Figure 11 Architecture for Calendar Service 10 Figure 12 Architecture for Address Book Service 10 Figure 13 Phone Management via Data Model Interaction Diagram .
17、 11 Figure 14 Architecture for InputConfig Service (IS) . 11 Figure 15 Architecture for Security Service . 12 BS ISO/IEC 29341261:2017ISO/IEC 29341-26-1:2017(E) iv ISO/IEC 2017 All rights reserved Figure A.1 Architecture with Telephony Control Point on a TV . 13 Figure A.2 Deployment with a TelCP on
18、 a TC - Multiple TV Model . 13 Figure A.3 Deployment with a TelCP on a TV - Multiple Phone Model 14 Figure A.4 An Architecture with a Telephony Control Point (TelCP) and a Telephony Client (TC) on a TV (2-Box Model) 14 Figure A.5 Deployment model with a Telephony Control Point (TelCP) and a Telephon
19、y Client (TC) on a TV (2-Box Model) Multiple TV Model . 15 Figure A.6 Deployment model with a Telephony Control Point (TelCP) and a Telephony Server (TS) on a Phone (2-Box Physical Model) . 15 Figure A.7 Deployment with a phone having a Telephony Server (TS) and a Telephony Control Point (TelCP) - M
20、ultiple TV Model 16 Figure A.8 Deployment with a Telephony Control Point (TelCP) on a Phone 16 Figure A.9 Deployment with a Telephony Control Point (TelCP) on a Phone Multiple TV Model . 17 Figure A.10 Deployment with an independent Telephony Control point (TelCP) -3 Box Scenario 17 Figure A.11 Depl
21、oyment with an independent Telephony Control Point (TelCP) 3-Box with Multiple TV Model . 18 Figure A.12 Messaging Service Deployment with Phone as the Messaging Aggregator . 18 Figure A.13 Multiple Telephony Servers in a telephone . 19 BS ISO/IEC 29341261:2017ISO/IEC 29341-26-1:2017(E) iv ISO/IEC 2
22、017 All rights reserved Figure A.1 Architecture with Telephony Control Point on a TV . 13 Figure A.2 Deployment with a TelCP on a TC - Multiple TV Model . 13 Figure A.3 Deployment with a TelCP on a TV - Multiple Phone Model 14 Figure A.4 An Architecture with a Telephony Control Point (TelCP) and a T
23、elephony Client (TC) on a TV (2-Box Model) 14 Figure A.5 Deployment model with a Telephony Control Point (TelCP) and a Telephony Client (TC) on a TV (2-Box Model) Multiple TV Model . 15 Figure A.6 Deployment model with a Telephony Control Point (TelCP) and a Telephony Server (TS) on a Phone (2-Box P
24、hysical Model) . 15 Figure A.7 Deployment with a phone having a Telephony Server (TS) and a Telephony Control Point (TelCP) - Multiple TV Model 16 Figure A.8 Deployment with a Telephony Control Point (TelCP) on a Phone 16 Figure A.9 Deployment with a Telephony Control Point (TelCP) on a Phone Multip
25、le TV Model . 17 Figure A.10 Deployment with an independent Telephony Control point (TelCP) -3 Box Scenario 17 Figure A.11 Deployment with an independent Telephony Control Point (TelCP) 3-Box with Multiple TV Model . 18 Figure A.12 Messaging Service Deployment with Phone as the Messaging Aggregator
26、. 18 Figure A.13 Multiple Telephony Servers in a telephone . 19 ISO/IEC 29341-26-1:2017(E) ISO/IEC 2017 All rights reserved v Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardiz
27、ation. 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 collaborate in fields of mutu
28、al 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 develop this document and
29、 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 Directives, Part 2 (s
30、ee 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. Details of any patent rights identified during the developm
31、ent 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 the voluntary nature
32、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 29341261 was prepared by U
33、PnP 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 Information technology UPnP
34、Device Architecture, can be found on the ISO web site. BS ISO/IEC 29341261:2017ISO/IEC 29341-26-1: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 document may involve the use of patents as indicated below. I
35、SO 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 terms and conditions with applicants throughout the world.
36、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 Corporation Standards Licensing Department 5200 NE Elam Young
37、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 / US; 7069312 / US; 10/783 524 /US Information may be obtain
38、ed 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 6687755 / US; 6910068 / US; 7130895 / US; 6725281 / US; 708930
39、7 / 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
40、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 IEC and ISO that it has patent applications or granted patent
41、s. 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 granted patents. Information may be obtained from: Huawei Technol
42、ogies 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 Incorporated 5775 Morehouse Drive San Diego, CA USA 92121 Telecom Ita
43、lia 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 applications or granted patents. Information may be obtained
44、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 pat
45、ent rights. BS ISO/IEC 29341261:2017ISO/IEC 29341-26-1: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 maintain consistency between the specifications as published by ISO
46、/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 Architecture 1.0 ISO/IEC 29341-1:2008 UPnP Device Architecture Version 1.
47、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 29341-3-1:2011 UPnP AVTransport:1 Service ISO/IEC 29341-3-10 UPnP
48、 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-3-2:2011 UPnP MediaServer:1 Device ISO/IEC 29341-3-3 UPnP AVTr
49、ansport: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 ISO/IEC 29341-4-12 UPnP RenderingControl:2 Service ISO/IEC 29341-4-13:2008 UPnP RenderingControl:2 Service ISO/IEC 29341-4-13:
