ISO/IEC 29341-26-1:2017

Information technology — UPnP Device Architecture — Part 26-1: Telephony device control protocol — Level 2 — Telephony architecture

ISO/IEC 29341-26-1:2017 describes an architecture that allows UPnP Telephony devices, services and control points defined in the propoded DCP to be deployed in the home network environment and to enable management of incoming and outgoing telephony calls, messaging, presence information and phone features configuration through UPnP means from devices within the home. In order to accommodate the above mentioned goals, the Telephony Architecture defines several UPnP devices and services that can be embedded to the devices defined for telephony. The architecture model describes interaction among the telephony devices, services and control points. The architecture also describes various deployment scenarios. The architecture does not describe any interfaces to "service" gateways that will enable non-UPnP entities to interact with the UPnP devices, services and control points physically attached to the home network.

Technologies de l'information — Architecture de dispositif UPnP — Partie 26-1: Protocole de contrôle de dispositif de téléphonie — Niveau 2 — Architecture de téléphonie

General Information

• Status: Published
• Publication Date: 12-Sep-2017
• ICS: 35.200 - Interface and interconnection equipment
• Technical Committee: ISO/IEC JTC 1 - Information technology
• Drafting Committee: ISO/IEC JTC 1 - Information technology
• Current Stage: 9060 - Close of review
• Start Date: 03-Mar-2028

Relations

• Consolidated By: ISO 8528-10:2022 - Reciprocating internal combustion engine driven alternating current generating sets — Part 10: Measurement of airborne noise
• Effective Date: 06-Jun-2022

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 29341-26-1
First edition
2017-09
Information technology — UPnP
Device Architecture —
Part 26-1:
Telephony device control protocol —
Level 2 — Telephony architecture
Technologies de l'information — Architecture de dispositif UPnP —
Partie 26-1: Protocole de contrôle de dispositif de téléphonie —
Niveau 2 — Architecture de téléphonie
Reference number
ISO/IEC 29341-26-1:2017(E)
©
ISO/IEC 2017

---------------------- Page: 1 ----------------------
ISO/IEC 29341-26-1:2017(E)

COPYRIGHT PROTECTED DOCUMENT
© 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 permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. [phone]
Fax [phone]
[e-mail]
www.iso.org
ii © ISO/IEC 2017 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 29341-26-1:2017(E)
CONTENTS

1  Scope. v
2  Normative references . 1
3  Terms, definitions and abbreviated term s . 1
3.1  Provisioning terms . 1
3.2  Symbols . 1
3.3  General telephony te rms . 2
4  Text conventions . 2
5  Introduction . 2
6  Telephony Reference Architecture . 3
6.1  Telephony Basic Architecture 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 Se rvic e . 8
6.2.5  Presence Se rvic e . 9
6.2.6  Calendar Service . 9
6.2.7  Address Book Service . 10
6.2.8  Phone Management 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-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 — Architecture for Media Management Service . 8
Figure 9 — Messaging Service Interaction Diagram. 8
Figure 10 — Architecture for Presence Service . 9
Figure 11 — Architecture for Calendar Servic e . 10
Figure 12 — Architecture for Address Book Service . 10
Figure 13 — Phone Management via Data Model Interaction Diagram . 11
Figure 14 — Architecture for InputConfig Service (IS) . 11
Figure 15 — Architecture for Security Service . 12
 ISO/IEC 2017 – All rights reserved  iii

---------------------- Page: 3 ----------------------
ISO/IEC 29341-26-1:2017(E)
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 Telephony
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 Physical 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 –
Multiple 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 . 18
Figure A.13 — Multiple Telephony Servers in a telephone . 19

iv   ISO/IEC 2017 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 29341-26-1:2017(E)
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 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 non‐governmental, 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 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 (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. 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/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
ISO’s adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the
following URL: Foreword – Supplementary information
ISO/IEC 29341‐26‐1 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
Information technology — UPnP Device Architecture, can be found on the ISO web site.
 ISO/IEC 2017 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO/IEC 29341-26-1:2017(E)
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 -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. 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 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 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&S
High Tech campus, building 44 3A21
NL – 5656 Eindhoven
NXP B.V. (NL) has informed IEC and ISO that it has patent applications or granted patents.
Information may be obtained from:
NXP B.V. (NL)
High Tech campus 60
NL – 5656 AG Eindhoven
Matsushita Electric Industrial Co. Ltd. has informed IEC and ISO that it has patent
applications or granted patents.
Information may be obtained from:
Matsushita Electric Industrial Co. Ltd.
1-3-7 Shiromi, Chuoh-ku
JP – Osaka 540-6139
vi   ISO/IEC 2017 – All rights reserved

---------------------- Page: 6 ----------------------
ISO/IEC 29341-26-1:2017(E)
Hewlett Packard Company has informed IEC and ISO that it has patent applications or
granted patents as listed below:
5 956 487 / US; 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 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
granted 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 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 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 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.

 ISO/IEC 2017 – All rights reserved vii

---------------------- Page: 7 ----------------------
ISO/IEC 29341-26-1:2017(E)
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/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.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 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 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 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 ISO/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/IEC 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/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
viii   ISO/IEC 2017 – All rights reserved

---------------------- Page: 8 ----------------------
ISO/IEC 29341-26-1:2017(E)
UPnP HVAC_UserOperatingMode:1 Service ISO/IEC 29341-6-17
UPnP HVAC_ZoneThermostat:1 Device ISO/IEC 29341-6-2
UPnP BinaryLight:1 Device ISO/IEC 29341-7-1
UPnP Dimming:1 Service ISO/IEC 29341-7-10
UPnP SwitchPower:1 Service ISO/IEC 29341-7-11
UPnP DimmableLight:1 Device ISO/IEC 29341-7-2
UPnP InternetGatewayDevice:1 Device ISO/IEC 29341-8-1
UPnP LANHostConfigManagement:1 Service ISO/IEC 29341-8-10
UPnP Layer3Forwarding:1 Service ISO/IEC 29341-8-11
UPnP LinkAuthentication:1 Service ISO/IEC 29341-8-12
UPnP RadiusClient:1 Service ISO/IEC 29341-8-13
UPnP WANCableLinkConfig:1 Service ISO/IEC 29341-8-14
UPnP WANCommonInterfaceConfig:1 Service ISO/IEC 29341-8-15
UPnP WANDSLLinkConfig:1 Service ISO/IEC 29341-8-16
UPnP WANEthernetLinkConfig:1 Service ISO/IEC 29341-8-17
UPnP WANIPConnection:1 Service ISO/IEC 29341-8-18
UPnP WANPOTSLinkConfig:1 Service ISO/IEC 29341-8-19
UPnP LANDevice:1 Device ISO/IEC 29341-8-2
UPnP WANPPPConnection:1 Service ISO/IEC 29341-8-20
UPnP WLANConfiguration:1 Service ISO/IEC 29341-8-21
UPnP WANDevice:1 Device ISO/IEC 29341-8-3
UPnP WANConnectionDevice:1 Device ISO/IEC 29341-8-4
UPnP WLANAccessPointDevice:1 Device ISO/IEC 29341-8-5
UPnP Printer:1 Device ISO/IEC 29341-9-1
UPnP ExternalActivity:1 Service ISO/IEC 29341-9-10
UPnP Feeder:1.0 Service ISO/IEC 29341-9-11
UPnP PrintBasic:1 Service ISO/IEC 29341-9-12
UPnP Scan:1 Service ISO/IEC 29341-9-13
UPnP Scanner:1.0 Device ISO/IEC 29341-9-2
UPnP QoS Architecture:1.0 ISO/IEC 29341-10-1
UPnP QosDevice:1 Service ISO/IEC 29341-10-10
UPnP QosManager:1 Service ISO/IEC 29341-10-11
UPnP QosPolicyHolder:1 Service ISO/IEC 29341-10-12
UPnP QoS Architecture:2 ISO/IEC 29341-11-1
UPnP QosDevice:2 Service ISO/IEC 29341-11-10
UPnP QosManager:2 Service ISO/IEC 29341-11-11
UPnP QosPolicyHolder:2 Service ISO/IEC 29341-11-12
UPnP QOS v2 Schema Files ISO/IEC 29341-11-2
UPnP RemoteUIClientDevice:1 Device ISO/IEC 29341-12-1
UPnP RemoteUIClient:1 Service ISO/IEC 29341-12-10
UPnP RemoteUIServer:1 Service ISO/IEC 29341-12-11
UPnP RemoteUIServerDevice:1 Device ISO/IEC 29341-12-2
UPnP DeviceSecurity:1 Service ISO/IEC 29341-13-10
UPnP SecurityConsole:1 Service ISO/IEC 29341-13-11
UPnP ContentDirectory:3 Service ISO/IEC 29341-14-12:2011
UPnP MediaServer:3 Device ISO/IEC 29341-14-3:2011
 ISO/IEC 2017 – All rights reserved ix

---------------------- Page: 9 ----------------------
ISO/IEC 29341-26-1:2017(E)
UPnP ContentSync:1 ISO/IEC 29341-15-10:2011
UPnP Low Power Architecture:1 ISO/IEC 29341-16-1:2011
UPnP LowPowerProxy:1 Service ISO/IEC 29341-16-10:2011
UPnP LowPowerDevice:1 Service ISO/IEC 29341-16-11:2011
UPnP QoS Architecture:3 ISO/IEC 29341-17-1:2011
UPnP QosDevice:3 Service ISO/IEC 29341-17-10:2011
UPnP QosManager:3 Service ISO/IEC 29341-17-11:2011
UPnP QosPolicyHolder:3 Service ISO/IEC 29341-17-12:2011
UPnP QosDevice:3 Addendum ISO/IEC 29341-17-13:2011
UPnP RemoteAccessArchitecture:1 ISO/IEC 29341-18-1:2011
UPnP InboundConnectionConfig:1 Service ISO/IEC 29341-18-10:2011
UPnP RADAConfig:1 Service ISO/IEC 29341-18-11:2011
UPnP RADASync:1 Service ISO/IEC 29341-18-12:2011
UPnP RATAConfig:1 Service ISO/IEC 29341-18-13:2011
UPnP RAClient:1 Device ISO/IEC 29341-18-2:2011
UPnP RAServer:1 Device ISO/IEC 29341-18-3:2011
UPnP RADiscoveryAgent:1 Device ISO/IEC 29341-18-4:2011
UPnP SolarProtectionBlind:1 Device ISO/IEC 29341-19-1:2011
UPnP TwoWayMotionMotor:1 Service ISO/IEC 29341-19-10:2011
UPnP AV Architecture:2 ISO/IEC 29341-20-1
UPnP AVTransport:3 Service ISO/IEC 29341-20-10
UPnP ConnectionManager:3 Service ISO/IEC 29341-20-11
UPnP ContentDirectory:4 Device ISO/IEC 29341-20-12
UPnP RenderingControl:3 Service ISO/IEC 29341-20-13
UPnP ScheduledRecording:2 Service ISO/IEC 29341-20-14
UPnP MediaRenderer:3 Service ISO/IEC 29341-20-2
UPnP MediaServer:4 Device ISO/IEC 29341-20-3
UPnP AV Datastructure Template:1 ISO/IEC 29341-20-4
UPnP InternetGatewayDevice:2 Device ISO/IEC 29341-24-1
UPnP WANIPConnection:2 Service ISO/IEC 29341-24-10
UPnP WANIPv6FirewallControl:1 Service ISO/IEC 29341-24-11
UPnP WANConnectionDevice:2 Service ISO/IEC 29341-24-2
UPnP WANDevice:2 Device ISO/IEC 29341-24-3
UPnP Telephony Architecture:2 ISO/IEC 29341-26-1
UPnP CallManagement:2 Service ISO/IEC 29341-26-10
UPnP MediaManagement:2 Service ISO/IEC 29341-26-11
UPnP Messaging:2 Service ISO/IEC 29341-26-12
UPnP PhoneManagement:2 Service ISO/IEC 29341-26-13
UPnP AddressBook:1 Service ISO/IEC 29341-26-14
UPnP Calendar:1 Service ISO/IEC 29341-26-15
UPnP Presense:1 Service ISO/IEC 29341-26-16
UPnP TelephonyClient:2 Device ISO/IEC 29341-26-2
UPnP TelephonyServer:2 Device ISO/IEC 29341-26-3
UPnP Friendly Info Update:1 Service ISO/IEC 29341-27-1
UPnP MultiScreen MultiScreen Architecture:1
ISO/IEC 29341-28-1
UPnP MultiScreen Application Management:1 Service
ISO/IEC 29341-28-10
x   ISO/IEC 2017 – All rights reserved

---------------------- Page: 10 ----------------------
ISO/IEC 29341-26-1:2017(E)
UPnP MultiScreen Screen:1 Device
ISO/IEC 29341-28-2
UPnP MultiScreen Application Management:2 Service
ISO/IEC 29341-29-10
UPnP MultiScreen Screen:2 Device
ISO/IEC 29341-29-2
UPnP IoT Management and Control Architecture Overview:1
ISO/IEC 29341-30-1
UPnP DataStore:1 Service
ISO/IEC 29341-30-10
UPnP IoT Management and Control Data Model:1 Service
ISO/IEC 29341-30-11
UPnP IoT Management and Control Transport Generic:1
Service ISO/IEC 29341-30-12
UPnP IoT Management and Control:1 Device
ISO/IEC 29341-30-2
UPnP Energy Management:1 Service ISO/IEC 29341-31-1
 ISO/IEC 2017 – All rights reserved xi

---------------------- Page: 11 ----------------------
ISO/IEC 29341-26-1:2017(E)
1 Scope
This document describes an architecture that allows UPnP Telephony devices, services and
control points defined in the propoded DCP to be deployed in the home network environment
and to enable management of incoming and outgoing telephony calls, messaging, presence
information and phone features configuration through UPnP means from devices within the
home.
In order to accommodate the above mentioned goals, the Telephony Architecture defines
several UPnP devices and services that can be embedded to the devices defined for
telephony. The architecture model describes interaction among the telephony devices,
services and control points. The architecture also describes various deployment scenarios.
The architecture does not describe any interfaces to “service” gateways that will enable non-
UPnP entities to interact with the UPnP devices, services and control points physically
attached to the home network.
2 Normative references
[1] – UPnP Device Architecture, version 1.0, UPnP Forum, October 15, 2008. Available
at: http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0-20081015.pdf. Latest
version available at: http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0.pdf.
3 Terms, definitions and abbreviated terms
For the purposes of this document, the terms and definitions given in [1] and the following
apply.
3.1 Provisioning terms
3.1.1
conditionally allowed
CA
The definition or behavior depends on a condition. If the specified condition is met, then the
definition or behavior is allowed, otherwise it is not allowed.
3.1.2
conditionally required
CR
The definition or behavior depends on a condition. If the specified condition is met, then the
definition or behavior is required, otherwise it is not allowed.
3.1.3
not allowed
The definition or behavior is prohibited by this specification. Opposite of required.
3.2 Symbols
3.2.1
::
signifies a hierarchical parent-child (parent::child) relationship between the two objects
separated by the double colon. This delimiter is used in multiple contexts, for example:
Service::Action(), Action()::Argument, parentProperty::childProperty.
 ISO/IEC 2017 – All rights reserved  1

---------------------- Page: 12 ----------------------
ISO/IEC 29341-26-1:2017(E)
3.3 General telephony terms
3.3.1
Telephony Server
TS
a logical device that provides common telephony features (e.g. call/video call, messaging,
address book) via UPnP to other devices in the home network. A TS is usually connected to a
telephony service on its WAN interface, either wire line or mobile. For example, a TS may be
a mobile phone or a home gateway with VoIP features.
3.3.2
Telephony Client
TC
a networked logical device that allows the user to enjoy the telephony features provided by
the Telephony Server via UPnP. A TC may usually provide input/output features for voice and
video. An example of a TC is a networked TV Set.
3.3.3
Telephony Control Point
TelCP
a software feature able to control the functionalities of both TS and TC. It may be embedded
in a TS, a TC or also being a physical device on its own.
3.3.4
InputConfig Control Point
ICP
a software feature that is able to control the functionalities of UPnP devices to be used to
provide user-friendly input features. The control here refers to getting capabilities of UPnP
dveices to be used for input, matching capabilities and selecting the appropriate dveice role
such as receving side or sending side etc.
3.3.5
InputConfig Service
IS
a software feature that is able to provide user-friendly input capability via UPnP means and
expose interfaces to describe capabilities of sender/receiver of devices to be used for input
services and setup the input session between the devices using the matching profile
(capability) from the ICP .
4 Text conventions
 Strings that are to be taken literally are enclosed in “double quotes”.
 Words that are emphasized are printed in italic.
 Keywords that are defined by the UPnP Working Committee are printed using the forum
character style.
 Keywords that are defined by the UPnP Device Architecture are printed using the arch
character style.
5 Introduction
The objective of the UPnP Telephony specification is to provide a means for interactions
between telephony devices and other (non-telephony) devices, without using native telephony
2  ISO/IEC 2017 – All rights reserved

---------------------- Page: 13 ----------------------
ISO/IEC 29341-26-1:2017(E)
features, but exploiting UPnP features of the phone device (e.g. messaging, calling, presence,
etc.).
An examtple of such a scenario, for a calling use case, is shown in Figure 1 where a Phone
device communicates with a non-phone (TV) using UPnP interaction model. The non-phone
device as shown here is a TV, and using UPnP mechanism can control the phone device
which receives call from outside of the home network via non-UPnP means. However, this
phone device can make the media session for this call available in the UPnP network to other
non-phone device via UPnP mechanism. The non-phone device can have a control point that
can control this media session via UPnP control mechanism on the phone device. The phone
device and the non-phone device establishes media session for the call between them and
this media session gets established using UPnP command and control mechanism.

Phone
Out of scope
of UPnP
Home Network
TV Phone
Control
Telephony
Notification
Control
Phone
Point Telephony
Network
Server
Media
(TS)
Telephony
Client

Figure 1 — UPnP Telephony Basic Architecture
Also the other use cases such as messaging, managing local presence, managing contacts
and accessing presence information, and managing the phone configuration are addressed
by the Telephony DCP according to this basic architecture model.
Note that the interaction of actual telephony call with a callee or a caller, on any kind of
telecommunication network (PSTN/ISDN, Mobile, Internet), is handled by the phone device
and is out of scope of this specification.
6 Telephony Reference Architecture
6.1 Telephony Basic Architecture Paradigm
Clause 6 describes the basic architectural model for telephony features.
The basic architecture for UPnP telephony features can be described in a 3-box model which
is shown below in Figure 2. Figure 2 represents a 3-box model where the Telephony Control
Point (TelCP) resides on a box outside of the Telephony Server (TS) and the Telephony
Client (TC). The Telephony Control Point (TelCP) discovers both the Telephony Client (TC)
and the Telephony Server (TS) and can establish the media session between them. And can
control the media session between the Telephony Client (TC) and the Telephony Server (TS).
This model can be collapsed into a 2-box model by having the Telephony Control Point
(TelCP) reside either in the Telephony Server (TS) or the Telephony Client (TC). The
Telephony Control Point (TelCP) can also directly interact with the Telephony Serve
...