ISO/IEC 29341-27-1:2017

Information technology — UPnP Device Architecture — Part 27-1: Friendly device control protocol — Friendly information update service

ISO/IEC 29341-27-1:2017 is compliant with the UPnP Device Architecture version 1.0. It defines a service type referred to herein as FriendlyInfoUpdate service . It is scoped to the Device Description Document (DDD) and is a service allowing control points to create orderly updates to the and elements. Once a change has taken place the status of the DDD might not reflect that of the advertised description because the device can not leave the network during ongoing activities. Therefore a state variable is provided to indicate if the DDD contains non-advertised (pending) values. If for any reason the device goes off line, power cycles, or reboots it will most likely advertise its new DDD. If DeviceProtection UPnP DP is implemented on the device then it will support restricting control point actions to control points with specific Roles.

Technologies de l'information — Architecture de dispositif UPnP — Partie 27-1: Protocole de contrôle de dispositif convivial — Service de présence — Service convivial de mise à jour de l'information

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-27-1
First edition
2017-09
Information technology — UPnP
Device Architecture —
Part 27-1:
Friendly device control protocol —
Friendly information update service
Technologies de l'information — Architecture de dispositif UPnP —
Partie 27-1: Protocole de contrôle de dispositif convivial — Service de
présence — Service convivial de mise à jour de l'information
Reference number
ISO/IEC 29341-27-1:2017(E)
©
ISO/IEC 2017

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


Contents
Contents . iii
List of Tables . iv
List of Figures . iv
1 Scope . v
2 Introduction . 1
3 Normative References . 1
4 Terms, definitions, symbols and abbreviated terms . 2
4.1 Provisioning terms . 2
4.1.1 conditionally allowed . 2
4.1.2 conditionally required . 2
4.1.3 not allowed . 2
4.2 Terms . 2
4.2.1 Clean . 2
4.2.2 Pending . 2
4.2.3 Friendly . 2
4.2.4 Non-Restrictable . 2
4.2.5 Restrictable . 2
4.3 Abbreviated terms . 3
4.3.1 3
4.3.2 3
5 Notations and Conventions . 3
5.1.1 Data Types . 3
5.2 Management of XML Namespaces in Standardized DCPs . 3
5.3 Vendor-defined Extensions . 3
6 Service Modeling Definitions (Normative) . 4
6.1 Service Type . 4
6.2 Security Feature . 4
6.2.1 Restrictable and Non-Restrictable actions . 4
6.3 FriendlyInfoUpdate Service Architecture . 5
6.4 State Variables . 5
6.4.1 State Variable Overview . 5
6.4.2 FriendlyNameStatus . 5
6.4.3 FriendlyIconListStatus . 6
6.4.4 A_ARG_TYPE_NewName . 9
6.4.5 A_ARG_TYPE_IconURI . 9
6.4.6 A_ARG_TYPE_UpdateType . 9
6.4.7 A_ARG_TYPE_Token . 9
6.4.8 A_ARG_TYPE_RestoreType . 9
6.5 Eventing and Moderation. 10
6.6 Actions . 10
6.6.1 GetFriendlyName() . 11
6.6.2 GetFriendlyIconList() . 11
6.6.3 SetFriendlyName() . 12
 ISO/IEC 2017 – All rights reserved iii

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

6.6.4 SetFriendlyIconList() . 13
6.6.5 RestoreFriendlyInfo() . 17
7 Theory of Operation (Informative) . 18
7.1 Changing the device . 18
7.2 Changing the device . 19
8 XML Service Description . 25

List of Tables
Table 6-1:  Assignment of Restrictable/Non-Restrictable Roles . 4
Table 6-2:  State Variables . 5
Table 6-3:  AllowedValueList for A_ARG_TYPE_UpdateType . 9
Table 6-4:  AllowedValueList for A_ARG_TYPE_RestoreType . 10
Table 6-5:  Eventing and Moderation. 10
Table 6-6:  Actions . 10
Table 6-7:  Arguments for GetFriendlyName() . 11
Table 6-8:  Error Codes for GetFriendlyName() . 11
Table 6-9:  Arguments for GetFriendlyIconList() . 12
Table 6-10:  Error Codes for GetFriendlyIconList() . 12
Table 6-11:  Arguments for SetFriendlyName() . 12
Table 6-12:  Error Codes for SetFriendlyName() . 13
Table 6-13:  Specific behavior for SetFriendlyIconList() upon valid input . 14
Table 6-14:  Arguments for SetFriendlyIconList() . 15
Table 2-16:  Error Codes for SetFriendlyIconList() . 16
Table 6-16:  Arguments for RestoreFriendlyInfo() . 17
Table 6-17:  Error Codes for RestoreFriendlyInfo() . 18

List of Figures
Figure 1 - Allowed icon@status transitions . 16

iv   ISO/IEC 2017 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 29341-27-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‐27‐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-27-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:
vi   ISO/IEC 2017 – All rights reserved

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

Matsushita Electric Industrial Co. Ltd.
1-3-7 Shiromi, Chuoh-ku
JP – Osaka 540-6139
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
 ISO/IEC 2017 – All rights reserved vii

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

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.

viii   ISO/IEC 2017 – All rights reserved

---------------------- Page: 8 ----------------------
ISO/IEC 29341-27-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
 ISO/IEC 2017 – All rights reserved ix

---------------------- Page: 9 ----------------------
ISO/IEC 29341-27-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
UPnP ContentSync:1 ISO/IEC 29341-15-10:2011
x   ISO/IEC 2017 – All rights reserved

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

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
UPnP MultiScreen Screen:1 Device
ISO/IEC 29341-28-2
UPnP MultiScreen Application Management:2 Service
ISO/IEC 29341-29-10
 ISO/IEC 2017 – All rights reserved xi

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

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
xii   ISO/IEC 2017 – All rights reserved

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

1 Scope
This service definition is compliant with the UPnP Device Architecture version 1.0. It defines a
service type referred to herein as FriendlyInfoUpdate service . It is scoped to the Device
Description Document (DDD) and is a service allowing control points to create orderly
updates to the and elements. Once a change has taken
place the status of the DDD might not reflect that of the advertised description because the
device can not leave the network during ongoing activities. Therefore a state variable is
provided to indicate if the DDD contains non-advertised (pending) values. If for any reason
the device goes off line, power cycles, or reboots it will most likely advertise its new DDD. If
DeviceProtection UPnP DP is implemented on the device then it will support restricting
control point actions to control points with specific Roles.
2 Introduction
The FriendlyInfoUpdate service is a UPnP service that enables control points to update
specific, friendly, elements of a UPnP device’s DDD. The DDD elements updateable by the
service are:


The service also describes how to reset the value to the original factory setting and in the
case of , a method for updating the actual device icon binaries using HTTP
methods. It is assumed that the device, when supporting the updating of icon binaries, will
have the means to manage image binaries, such as determining MIME image type, height,
width and color depth, as well as, negating undesired behavior associated with binary
transfers involving potential malware.
3 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.
UPnP CDS4, UPnP ContentDirectory Service version 4.0 UPnP Forum, Available
at http://upnp.org/specs/av/UPnP-av-ContentDirectory-v4-Service.pdf .
ISO/IEC 29341-1, UPnP Device Architecture, version 1.0, UPnP Forum.
Available at: http://upnp.org/specs/arch/UPnPDA10_20000613.pdf
Latest version available at: http://www.upnp.org/specs/arch/UPnP-arch-
DeviceArchitecture.pdf
UPnP DP, UPnP DeviceProtection Service, version 1, UPnP Forum. Available
at http://upnp.org/specs/gw/UPnP-gw-DeviceProtection-v1-Service.pdf .
RFC 2616, IETF RFC 2616, HyperText Transport Protocol – HTTP/1.1, R. Fielding, J. Gettys,
J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee, June 1999.
Available at: http://www.ietf.org/rfc/rfc2616.txt.
XML-FIS-SCHEMA, XML Schema for FriendlyIconListStatus state variable document.
Available at: http://upnp.org/schemas/fd/fis-events.xsd.
XML-FNS-SCHEMA, – XML Schema for FriendlyNameStatus state variable document.
Available at: http://upnp.org/schemas/fd/fns-events.xsd.
XML SCHEMA-2, 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.
 ISO/IEC 2017 – All rights reserved 1

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


4 Terms, definitions, symbols and abbreviated terms
For the purposes of this document, the terms and definitions given in ISO/IEC 29341-1
and the following apply.
4.1 Provisioning terms
4.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.
4.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.
4.1.3 not allowed
The definition or behavior is prohibited by this specification. Opposite of required.
4.2 Terms
4.2.1 Clean
A notional device state scoped to this specification in which all internal states related to the
DDD are identical to its last advertised Device Description Document.
4.2.2 Pending
The pending state is a notional device state scoped to this specification in which one or more
of the internal states related to the DDD are different from its last advertised Device
Description Document.
4.2.3 Friendly
DDD element(s) which can be interpreted as human identifiable and not tied directly to the
device manufacturer information; specifically the and device icons,
defined in the element, are considered friendly.
4.2.4 Non-Restrictable
A category of action, that when the DeviceProtection UPnP DP service is implemented on the
device, cannot be blocked according to the presence or absence of a specific Role attached
to a Control Point Identity or User Identity. See UPnP CDS4 for further explanation of Role,
Control Point Identit
...