ISO/IEC 29341-27-1:2017
(Main)Information technology — UPnP Device Architecture — Part 27-1: Friendly device control protocol — Friendly information update service
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
Buy Standard
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 2017
© 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. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO/IEC 2017 – All rights reserved
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
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
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
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
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
...
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 2017
© 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. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO/IEC 2017 – All rights reserved
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
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
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
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
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
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.