ISO/IEC 29341-26-16:2017

Information technology — UPnP Device Architecture — Part 26-16: Telephony device control protocol — Level 2 — Presence service

ISO/IEC 29341-26-16:2017 is compliant with the [1]. It defines a service type referred to herein as Presence service. The Presence service is a UPnP service that allows control points, or better known as Telephony Control Points (TelCP), to manage presence information through a Telephony Server (TS) device or a Telephony Client (TC) device (in the role of UPnP server device for Presence service). This service provides control points with the following functionality: - Presence of contacts, access the presence information of contacts, as provided by the UPnP Telephony Server device. Contacts referenced by the Presence service may be managed via PhoneManagement service and the Phone Data Model. - Managing presence information, update the presence status stored in the TS; This service does not provide the following functionality: - To update the presence status of the local UPnP network, from the UPnP server device to remote presence servers (i.e. outside the local UPnP network). - To retrieve the presence information of contacts from remote presence servers (i.e. outside the local UPnP network). When the features provided by the Presence service are associated to the PhoneManagement features, then an integrated management of the address book and the presence of contacts in the address book can be delivered.

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

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

Standards Content (Sample)

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

---------------------- Page: 1 ----------------------
ISO/IEC 29341-26-16: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-16:2017(E)

CONTENTS

1  Scope. v
2  Normative references . 1
3  Terms, definitions, symbols and abbreviated terms . 2
4  Notations and c onventions . 3
4.1  Text conventions . 3
4.1.1  Data Types . 4
4.2  Vendor-defined Extensions . 4
5  Service Modeling Definiti ons . 4
5.1  Service Type . 4
5.2  Presence Service Architecture . 4
5.3  State Variables . 5
5.3.1  State Variable Overview . 5
5.3.2  UserPresenceInfo . 5
5.3.3  PresenceOfContactsUpdate . 7
5.3.4  A_ARG_TYPE_UserPresenceInfo . 8
5.3.5  A_ARG_TYPE_PresenceOfContactsList . 10
5.3.6  A_ARG_TYPE_ContactId . 11
5.3.7  A_ARG_TYPE_RegistrationResult . 12
5.3.8  A_ARG_TYPE_Expires . 12
5.3.9  Watcher . 12
5.3.10  A_ARG_TYPE_WatcherList . 13
5.4  Eventing and Moderation . 14
5.4.1  Eventing of UserPresenceInfo . 14
5.4.2  Eventing of PresenceOfContactsUpdate . 15
5.4.3  Eventing of Watcher . 15
5.5  Actions . 15
5.5.1  GetPresence() . 15
5.5.2  UpdatePresence() . 16
5.5.3  GetContactPresence() . 17
5.5.4  GetPresenceOfContactsUpdate() . 18
5.5.5  RegisterForContactPresence() . 19
5.5.6  AuthorizePresenceReactive() . 20
5.5.7  AuthorizePresenceProactive() . 21
5.5.8  Error Code Summary . 22
5.6  Service Behavioral Model . 22
6  XML Service Description . 22
Annex A (normative) XML complex type peerType . 26
Annex B (normative) XML Schema . 30
Annex C (informative) Theory of Operation . 32
Annex D (informative) Bibliography . 34

Figure 1 — Presence Service Architecture . 5
 ISO/IEC 2017 – All rights reserved iii

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

Figure C.1 — Presence registration and notification . 32
Figure C.2 — Reactive Authorization of a request for Presence information . 33
Figure C.3 — Proactive Authorization for Presence information . 33

Table 1 — State Variables . 5
Table 2 — Event Moderation . 14
Table 3 — Actions . 15
Table 4 — Arguments for GetPresence() . 15
Table 5 — Error Codes for GetPresence() . 16
Table 6 — Arguments for UpdatePresence() . 16
Table 7 — Error Codes for UpdatePresence() . 17
Table 8 — Arguments for GetContactPresence() . 17
Table 9 — Error Codes for GetContactPresence() . 18
Table 10 — Arguments for GetPresenceOfContactsUpdate() . 18
Table 11 — Error Codes for GetPresenceOfContactsUpdate() . 18
Table 12 — Arguments for RegisterForContactPresence() . 19
Table 13 — Error Codes for RegisterForContactPresence() . 19
Table 14 — Arguments for AuthorizePresenceReactive() . 20
Table 15 — Error Codes for AuthorizePresenceReactive() . 21
Table 16 — Arguments for AuthorizePresenceProactive() . 21
Table 17 — Error Codes for AuthorizePresenceProactive() . 22
Table 18 — Error Code Summary . 22

iv   ISO/IEC 2017 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 29341-26-16: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‐16 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-16: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-16: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-16: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-16: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-16: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-16: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-16:2017(E)

1 Scope
This service definition is compliant with the [1]. It defines a service type referred to herein as
Presence service.
The Presence service is a UPnP service that allows control points, or better known as
Telephony Control Points (TelCP), to manage presence information through a Telephony
Server (TS) device or a Telephony Client (TC) device (in the role of UPnP server device for
Presence service). This service provides control points with the following functionality:
 Presence of contacts, access the presence information of contacts, as provided by the
UPnP Telephony Server device. Contacts referenced by the Presence service may be
managed via PhoneManagement service and the Phone Data Model.
 Managing presence information, update the presence status stored in the TS;
This service does not provide the following functionality:
 To update the presence status of the local UPnP network, from the UPnP server device to
remote presence servers (i.e. outside the local UPnP network).
 To retrieve the presence information of contacts from remote presence servers (i.e.
outside the local UPnP network).
When the features provided by the Presence service are associated to the
PhoneManagement features, then an integrated management of the address book and the
presence of contacts in the address book can be delivered.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document
and are indispensable for its application. For dated references, only the edition cited applies.
For undated references, the latest edition of the referenced document (including any
amendments) applies.
[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.
[2] – Data elements and interchange formats – Information interchange -- Representation of
dates and times, International Standards Organization, December 21, 2000.
Available at: ISO 8601:2000.
[3] – IETF RFC 2046, Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types,
N. Freed, Innosoft, N. Borenstein, First Virtual, November 1996. Available
at: http://www.ietf.org/rfc/rfc2046.txt.
[4] – IETF RFC 2119, Key words for use in RFCs to Indicate Requirement Levels, S. Bradner,
1997. Available at: http://www.faqs.org/rfcs/rfc2119.html.
[5] – IETF RFC 2396, Uniform Resource Identifiers (URI): Generic Syntax, T. Berners-Lee,
MIT/LCS, R. Fielding, U.C. Irvine, L. Masinter, Xerox Corporation, August 1998. Available
at: http://www.ietf.org/rfc/rfc2396.txt
 ISO/IEC 2017 – All rights reserved  1

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

[6] – IETF RFC 3339, Date and Time on the Internet: Timestamps, G. Klyne, Clearswift
Corporation, C. Newman, Sun Microsystems, July 2002. Available
at: http://www.ietf.org/rfc/rfc3339.txt.
[7] – IETF RFC 3966, The tel URI for Telephone Numbers, H. Schulzrinne, Columbia
University, December 2004. Available at: http://www.ietf.org/rfc/rfc3966.txt.
[8] – Extensible Markup Language (XML) 1.0 (Third Edition), François Yergeau, Tim Bray,
Jean Paoli, C. M. Sperberg-McQueen, Eve Maler, eds., W3C Recommendation, February 4,
2004. Available at: http://www.w3.org/TR/2004/REC-xml-20040204.
[9] – XML Schema Part 2: Data Types, Second Edition, Paul V. Biron, Ashok Malhotra, W3C
Recommendation, 28 October 2004. Available at: http://www.w3.org/TR/2004/REC-
xmlschema-2-20041028.
[10] – PhoneManagement:2, UPnP Forum, December 10, 2012. Available
at: http://upnp.org/specs/phone/UPnP-phone-PhoneManagement-v2-Service-20121210.pdf.
Latest version available at: http://upnp.org/specs/phone/UPnP-phone-PhoneManagement-
Service.pdf.
[11] – IETF RFC 3863, Presence Information Data Format (PIDF), H. Sugano, S. Fujimoto,
Fujitsu, G. Klyne, Nine by Nine, A. Bateman, VisionTech, W. Carr, Intel, J. Peterson NeuStar,
August 2004. Available at: http://www.ietf.org/rfc/rfc3863.txt.
[12] – IETF RFC 4660, Functional Description of Event Notification Filtering, H. Khartabil,
Telio, E. Leppanen, M. Lonnfors, J. Costa-Requena, Nokia, September 2006. Available
at: http://www.ietf.org/rfc/rfc4660.txt.
[13] – IETF RFC 4661, An Extensible Markup Language (XML)-Based Format for Event
Notification Filtering, H. Khartabil, Telio, E. Leppanen, M. Lonnfors, J. Costa-Requena, Nokia,
September 2006. Available at: http://www.ietf.org/rfc/rfc4661.txt.
3 Terms, definitions, symbols 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.
2  ISO/IEC 2017 – All rights reserved

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

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.
3.3 General terms
3.3.1
Watcher
Any uniquely identifiable entity that requests the presence information of a TS or user owning
the TS.
3.4 Abbreviated terms
3.4.1
GUI
Graphical User Interface
3.4.2
ID
Identifier
3.4.3
TC
Telephony Client
3.4.4
TelCP
Telephony Control Point
3.4.5
TS
Telephony Server
3.4.6
VoIP
Voice over IP
3.4.7
WAN
Wide Area Network
4 Notations and conventions
4.1 Text conventions
 Strings that are to be taken literally are enclosed in “double quotes”.
 Words that are emphasized are printed in italic.
 ISO/IEC 2017 – All rights reserved  3

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

 Keywords that are defined by the UPnP Working Committee are printed using the forum
character style.
 Keywords that are defined by [1] are printed using the arch character style.
4.1.1 Data Types
This specification uses data type definitions from two different sources. Data types from [1]
are us
...