ISO/IEC 29341-31-1:2017

Information technology — UPnP Device Architecture — Part 31-1: Energy management device control protocol — Energy management service

ISO/IEC 29341-31-1:2017 is compliant with the UPnP Device Architecture version 1.0. It defines a service type named EnergyManagement service. It is scoped to any UPnP Device that needs to convey energy management functionality available for the UPnP Device and its services.

Technologies de l'information — Architecture de dispositif UPnP — Partie 31-1: Protocole de contrôle du dispositif de management de l'énergie — Service de management de l'énergie

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-31-1
First edition
2017-09
Information technology — UPnP
Device Architecture —
Part 31-1:
Energy management device control
protocol — Energy management
service
Technologies de l'information — Architecture de dispositif UPnP —
Partie 31-1: Protocole de contrôle du dispositif de management de
l'énergie — Service de management de l'énergie
Reference number
ISO/IEC 29341-31-1:2017(E)
©
ISO/IEC 2017

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


CONTENTS

1  Scope . v
2  Normative references . 1
3  Terms, definitions, symbols and abbreviated terms . 2
4  Notations and Conventions . 2
4.1  Notation . 2
4.1.1  Data Types . 2
4.2  Derived Data Types . 3
4.3  Management of XML Namespaces in Standardized DCPs . 3
4.3.1  Namespace Prefix Requirements . 4
4.3.2  Namespace Names, Namespace Versioning and Schema
Versioning . 5
4.3.3  Namespace Usage Examples . 7
4.4  Vendor-defined Extensions . 7
4.4.1  Vendor-defined Action Names . 7
4.4.2  Vendor-defined State Variable Names . 8
4.4.3  Vendor-defined XML Elements and attributes . 8
4.4.4  Vendor-defined Property Names . 8
5  Service modelling definitions . 8
5.1  Service type . 8
5.2  Security feature . 8
5.2.1  Overview . 8
5.2.2  Restrictable and non-restrictatable actions . 8
5.3  State variables . 9
5.3.1  General . 9
5.3.2  State variable overview . 9
5.3.3  NetworkInterfaceInfo . 9
5.3.4  ProxiedNetworkInterfaceInfo . 13
5.3.5  A_ARG_TYPE_Duration . 13
5.3.6  A_ARG_TYPE_ServiceSubscriptionID . 13
5.3.7  A_ARG_TYPE_UniqueServiceName . 13
5.3.8  A_ARG_TYPE_URI . 14
5.4  Eventing and moderation . 14
5.5  Actions . 14
5.5.1  Overview . 14
5.5.2  GetInterfaceInfo() . 16
5.5.3  ServiceSubscription() . 16
5.5.4  ServiceRenewal() . 18
5.5.5  ServiceRelease() . 19
6  Theory of operations . 20
6.1  Overview . 20
6.2  WakeOnPattern theory of operation . 20
6.2.1  Overview . 20
6.2.2  EnergyManagement service operation . 21
6.2.3  WakeOnPattern signaling operation . 21
 ISO/IEC 2017 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 29341-31-1:2017(E)
6.2.4  Usability considerations . 21
6.3  Service subscription theory of operation . 22
6.4  EnergyManagement service theory of operation . 23
6.5  EnergyManagement control point theory of operation . 23
6.6  Network Interface Mode of Operation . 23
6.7  ProxiedNetworkInterfaceInfo theory of operation . 24
7  XML service description . 24

Table 1 — Namespace Definitions . 4
Table 2 — Schema-related Information . 4
Table 3 — Default Namespaces for the EnergyManagement Specifications . 5
Table 4 — Assignment of Restrictable/Non-Restrictable Roles . 9
Table 5 — State variables . 9
Table 6 — Event moderation . 14
Table 7 — Actions . 15
Table 8 — Arguments for GetInterfaceInfo() . 16
Table 9 — Error codes for GetInterfaceInfo() . 16
Table 10 — Arguments for ServiceSubscription() . 16
Table 11 — Error Codes for ServiceSubscription() . 18
Table 12 — Arguments for ServiceRenewal() . 18
Table 13 — Error codes for ServiceRenewal() . 19
Table 14 — Arguments for ServiceRelease() . 19
Table 15 — Error codes for ServiceRelease() . 20


iv  ISO/IEC 2017 – All rights reserved

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

---------------------- Page: 6 ----------------------
ISO/IEC 29341-31-1:2017(E)
Information may be obtained from:
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-31-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-31-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
UPnP HVAC_UserOperatingMode:1 Service ISO/IEC 29341-6-17
 ISO/IEC 2017 – All rights reserved ix

---------------------- Page: 9 ----------------------
ISO/IEC 29341-31-1:2017(E)
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
UPnP Low Power Architecture:1 ISO/IEC 29341-16-1:2011
x  ISO/IEC 2017 – All rights reserved

---------------------- Page: 10 ----------------------
ISO/IEC 29341-31-1:2017(E)
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
UPnP MultiScreen Screen:2 Device
ISO/IEC 29341-29-2
 ISO/IEC 2017 – All rights reserved xi

---------------------- Page: 11 ----------------------
ISO/IEC 29341-31-1:2017(E)
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-31-1:2017(E)
1 Scope
This specification is compliant with the UPnP Device Architecture version 1.0. It
defines a service type named EnergyManagement service. It is scoped to any UPnP
Device that needs to convey energy management functionality available for the UPnP
Device and its services.
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.
ISO/IEC 29341-1, Information Technology – UPnP Device Architecture – Part 1-1:
UPnP Device Architecture Version 1.0
ISO/IEC 29341-4-12, Information Technology – UPnP Device Architecture – Part 4-12:
Audio video Device Control Protocol – Level 2 – Content Directory Service
IETF RFC 1738, Uniform Resource Locators (URL), Tim Berners-Lee, et. Al.,
December 1994.
Available at: http://www.ietf.org/rfc/rfc1738.txt.
IETF RFC 2396, Uniform Resource Identifiers (URI): Generic Syntax, Tim Berners-
Lee, et al, 1998.
Available at: http://www.ietf.org/rfc/rfc2396.txt.
IETF RFC 4291, IP Version 6 Addressing Architecture, February 2006
Available at: http://www.ietf.org/rfc/rfc4291.txt
IETF RFC 5952, A Recommendation for IPv6 Address Text Representation, August
2010
Available at: http:/www.ietf.org/rfc/rfc5952.txt
W3C XML, Extensible Markup Language (XML) 1.0 (Third Edition), W3C
Recommendation, February 4, 2004.
Available at: http://www.w3.org/TR/2004/REC-xml-20040204.
W3C XML-NS, The “xml:” Namespace, October 26, 2009.
Available at: http://www.w3.org/XML/1998/namespace.
W3C XML-XSD, XML Schema for the “xml:” Namespace.
Available at: http://www.w3.org/2001/xml.xsd.
W3C XML-NMSP, Namespaces in XML, Tim Bray, Dave Hollander, Andrew Layman,
eds., W3C Recommendation, January 14, 1999.
Available at: http://www.w3.org/TR/1999/REC-xml-names-19990114.
W3C XML Schema-1, XML Schema Part1: Structures, Second Edition, Henry S.
Thompson, David Beech, Murray Maloney, Noah Mendelsohn, W3C Recommendation,
28 October 2004.
Available at: http://www.w3.org/TR/2004/REC-xmlschema-1-20041028.
W3C 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.
W3C XML Schema, XML Schema for XML Schema.
Available at: http://www.w3.org/2001/XMLSchema.xsd.
 ISO/IEC 2017 – All rights reserved 1

---------------------- Page: 13 ----------------------
ISO/IEC 29341-31-1:2017(E)
UPnP DP, DeviceProtection:1, UPnP Forum, February 24, 2011.
Available at: http://www.upnp.org/specs/gw/UPnP-gw-DeviceProtection-v1-Service-
20110224.pdf.
Latest version available at: http://www.upnp.org/specs/gw/UPnP-gw-DeviceProtection-
v1-Service.pdf.
UPnP EM-NII-XSD, XML Schema for EnergyManagement NetworkInterfaceInfo, UPnP
Forum, June 30, 2013.
Available at: http://www.upnp.org/schemas/lp/em-NetworkInterfaceInfo-v1-
20130830.xsd.
Latest version available at: http://www.upnp.org/schemas/lp/ em-
NetworkInterfaceInfo.xsd
3 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.
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 Abbreviated terms
3.2.1
A
allowed
4 Notations and Conventions
4.1 Notation
 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 EnergyManagement Working Committee
are printed using the forum character style.
 Keywords that are defined by the UPnP Device Architecture specification
[ISO/IEC 29341-1] are printed using the arch character style.
4.1.1 Data Types
This specification uses data type definitions from two different sources. The UPnP
Device Architecture [ISO/IEC 29341-1] defined data types are used to define state
variable and action argument data types. The XML Schema namespace is used to
define property data types [W3C XML Schema-2].
For UPnP Device Architecture [ISO/IEC 29341-1] defined boolean data types, it is
strongly recommended to use the value “0” for false, and the value “1” for true.
However, when used as input arguments, the values “false”, “no”, “true”, “yes” can
2  ISO/IEC 2017 – All rights reserved

---------------------- Page: 14 ----------------------
ISO/IEC 29341-31-1:2017(E)
also be encountered and shall be accepted. Nevertheless, it is strongly recommended
that all boolean state variables and output arguments be represented as “0” and “1”.
For XML Schema [W3C XML Schema-2] defined Boolean data types, it is strongly
recommended to use the value “0” for false, and the value “1” for true. However, when
used as input properties, the values “false”, “true” can also be encountered and shall
be accepted. Nevertheless, it is strongly recommended that all Boolean properties be
represented as “0” and “1”.
4.2 Derived Data Types
Subclause 4.2 defines a derived data type that is represented as a string data type
with special syntax. This specification uses string data type definitions that originate
from two different sources. The UPnP Device Architecture defined string data type is
used to define state variable and action argument string data types. The XML
Schema namespace is used to define property xsd:string data types. The following
definition applies to both string data types.
4.3 Management of XML Namespaces in Standardized DCPs
UPnP specificati
...