1、Information technology UPnP Device Architecture Part 27-1: Friendly device control protocol Friendly information update service BS ISO/IEC 29341-27-1:2017 BSI Standards Publication WB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06Information technology UPnP Device Architecture Part 27-1: Frie
2、ndly device control protocol Friendly information update service Technologies de linformation Architecture de dispositif UPnP Partie 27-1: Protocole de contrle de dispositif convivial Service de prsence Service convivial de mise jour de linformation INTERNATIONAL STANDARD ISO/IEC 29341-27-1 Referenc
3、e number ISO/IEC 29341-27-1:2017(E) First edition 2017-09 ISO/IEC 2017 National foreword This British Standard is the UK implementation of ISO/IEC 29341-27-1:2017. The UK participation in its preparation was entrusted to Technical Committee ICT/-/1, Information systems co-ordination. A list of organ
4、izations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2017 Published by BSI Standards Limited 20
5、17 ISBN 978 0 580 90895 8 ICS 35.200 Compliance with a British Standard cannot confer immunity from legal obligations. This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 September 2017. Amendments/corrigenda issued since publication Date Text
6、 affected BRITISH STANDARD BS ISO/IEC 29341271:2017Information technology UPnP Device Architecture Part 27-1: Friendly device control protocol Friendly information update service Technologies de linformation Architecture de dispositif UPnP Partie 27-1: Protocole de contrle de dispositif convivial Se
7、rvice de prsence Service convivial de mise jour de linformation INTERNATIONAL STANDARD ISO/IEC 29341-27-1 Reference number ISO/IEC 29341-27-1:2017(E) First edition 2017-09 ISO/IEC 2017 BS ISO/IEC 29341271:2017 ii ISO/IEC 2017 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2017, Published i
8、n 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 ca
9、n be requested from either ISO at the address below or ISOs 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 copyrightiso.org www.iso.org ISO/IEC 29341-27-1:2017(E) BS ISO/IEC
10、29341271:2017 ii ISO/IEC 2017 All rights reserved 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
11、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 ISOs member body in the country of the requester. ISO copyright office Ch. de Blandonnet 8 CP 401 CH-1214 Vernier, Geneva, Switzerland Tel. +
12、41 22 749 01 11 Fax +41 22 749 09 47 copyrightiso.org www.iso.org ISO/IEC 29341-27-1:2017(E) ISO/IEC 29341-27-1:2017(E) ISO/IEC 2017 All rights reserved iii Contents Contents iii List of Tables . iv List of Figures iv 1 Scope . v 2 Introduction 1 3 Normative References . 1 4 Terms, definitions, symb
13、ols 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 N
14、otations 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 Se
15、rvice 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 an
16、d Moderation. 10 6.6 Actions . 10 6.6.1 GetFriendlyName() . 11 6.6.2 GetFriendlyIconList() . 11 6.6.3 SetFriendlyName() 12 BS ISO/IEC 29341271:2017ISO/IEC 29341-27-1:2017(E) iv ISO/IEC 2017 All rights reserved 6.6.4 SetFriendlyIconList() . 13 6.6.5 RestoreFriendlyInfo() 17 7 Theory of Operation (Inf
17、ormative) 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_A
18、RG_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
19、: 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 Restor
20、eFriendlyInfo() . 17 Table 6-17: Error Codes for RestoreFriendlyInfo() . 18 List of Figures Figure 1 - Allowed iconstatus transitions 16 BS ISO/IEC 29341271:2017ISO/IEC 29341-27-1:2017(E) iv ISO/IEC 2017 All rights reserved 6.6.4 SetFriendlyIconList() . 13 6.6.5 RestoreFriendlyInfo() 17 7 Theory of
21、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: AllowedVal
22、ueList 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() .
23、 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: Argume
24、nts for RestoreFriendlyInfo() . 17 Table 6-17: Error Codes for RestoreFriendlyInfo() . 18 List of Figures Figure 1 - Allowed iconstatus transitions 16 ISO/IEC 29341-27-1:2017(E) ISO/IEC 2017 All rights reserved v Foreword ISO (the International Organization for Standardization) and IEC (the Internat
25、ional 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 field
26、s of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and nongovernmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joi
27、nt 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
28、was drafted in accordance with the editori al 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 an
29、y 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 u
30、sers 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 ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT) see
31、the following URL: Foreword Supplementary information ISO/IEC 29341271 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 avail
32、able parts of ISO/IEC 29341 series, under the general title Information technology UPnP Device Architecture, can be found on the ISO web site. BS ISO/IEC 29341271:2017ISO/IEC 29341-27-1:2017(E) vi ISO/IEC 2017 All rights reserved Introduction ISO and IEC draw attention to the fact that it is claimed
33、 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 reaso
34、nable 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 ma
35、y 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
36、/ 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: Phil
37、ips International B.V. IP 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 applicati
38、ons or granted patents. Information may be obtained from: Philips International B.V. IP 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 Electro
39、nics 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
40、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 obtai
41、ned 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
42、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 BS ISO/IEC 29341271:2017ISO/IEC 29341-27-1:2017(E) viii ISO/IEC 2017 All rights reserved Attention is drawn to the possibility that some of t
43、he 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. BS ISO/IEC 29341271:2017ISO/IEC 29341-27-1:2017(E) viii ISO/IEC 2017 All rights reserved Attention is drawn to
44、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 29341-27-1:2017(E) ISO/IEC 2017 All rights reserved ix Original UPnP Docu
45、ment 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 docu
46、ment 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
47、-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 RenderingContro
48、l: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 S
49、ervice 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 Datastr
