BS ISO IEC 29341-31-1-2017 Information technology UPnP Device Architecture Energy management device control protocol Energy management service《信息技术 UPnP设备体系结构 能量管理设备控制协议 能源管理处》.pdf

1、Information technology UPnP Device ArchitecturePart 31-1: Energy management device control protocol Energy management serviceBS ISO/IEC 29341-31-1:2017BSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06Information technology UPnP Device Architecture Part 31-1: Energy ma

2、nagement device control protocol Energy management serviceTechnologies de linformation Architecture de dispositif UPnP Partie 31-1: Protocole de contrle du dispositif de management de lnergie Service de management de lnergieINTERNATIONAL STANDARDISO/IEC29341-31-1Reference numberISO/IEC 29341-31-1:20

3、17(E)First edition2017-09 ISO/IEC 2017National forewordThis British Standard is the UK implementation of ISO/IEC 29341-31-1:2017.The UK participation in its preparation was entrusted to Technical Committee ICT/-/1, Information systems co-ordination.A list of organizations represented on this committ

4、ee 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 2017ISBN 978 0 580 90906 1ICS 35.200Com

5、pliance 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 publicationDate Text affectedBRITISH STANDARDBS ISO/IEC 2934131

6、1:2017Information technology UPnP Device Architecture Part 31-1: Energy management device control protocol Energy management serviceTechnologies de linformation Architecture de dispositif UPnP Partie 31-1: Protocole de contrle du dispositif de management de lnergie Service de management de lnergieIN

7、TERNATIONAL STANDARDISO/IEC29341-31-1Reference numberISO/IEC 29341-31-1:2017(E)First edition2017-09 ISO/IEC 2017BS ISO/IEC 29341311:2017ii ISO/IEC 2017 All rights reservedCOPYRIGHT PROTECTED DOCUMENT ISO/IEC 2017, Published in SwitzerlandAll rights reserved. Unless otherwise specified, no part of th

8、is 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 ISOs member body in t

9、he country of the requester.ISO copyright officeCh. de Blandonnet 8 CP 401CH-1214 Vernier, Geneva, SwitzerlandTel. +41 22 749 01 11Fax +41 22 749 09 47copyrightiso.orgwww.iso.orgISO/IEC 29341-31-1:2017(E)BS ISO/IEC 29341311:2017ii ISO/IEC 2017 All rights reservedCOPYRIGHT PROTECTED DOCUMENT ISO/IEC

10、2017, Published in SwitzerlandAll 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 permissio

11、n. Permission can be requested from either ISO at the address below or ISOs member body in the country of the requester.ISO copyright officeCh. de Blandonnet 8 CP 401CH-1214 Vernier, Geneva, SwitzerlandTel. +41 22 749 01 11Fax +41 22 749 09 47copyrightiso.orgwww.iso.orgISO/IEC 29341-31-1:2017(E)ISO/

12、IEC 29341-31-1:2017(E) ISO/IEC 2017 All rights reserved iii 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 Standardize

13、d 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

14、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 NetworkInter

15、faceInfo 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 ServiceSubs

16、cription() . 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 BS ISO/IEC 29341311:2017ISO/IEC

17、29341-31-1:2017(E) iv ISO/IEC 2017 All rights reserved 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

18、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 Stat

19、e 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() 1

20、8 Table 13 Error codes for ServiceRenewal() . 19 Table 14 Arguments for ServiceRelease() . 19 Table 15 Error codes for ServiceRelease() 20 BS ISO/IEC 29341311:2017ISO/IEC 29341-31-1:2017(E) iv ISO/IEC 2017 All rights reserved 6.2.4 Usability considerations . 21 6.3 Service subscription theory of ope

21、ration . 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 Sch

22、ema-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

23、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 ServiceRel

24、ease() 20 ISO/IEC 29341-31-1:2017(E) ISO/IEC 2017 All rights reserved v 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

25、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, govern

26、mental 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 joint technical committee, ISO/IEC JTC 1. The procedures used to develop this document and those intended for its further maintenance are descri

27、bed 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 t

28、o 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

29、 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

30、 expressions related to conformity assessment, as well as information about ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the following URL: Foreword Supplementary information ISO/IEC 29341311 was prepared by UPnP Forum and adopted, under the PAS procedure, by joi

31、nt 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.

32、 BS ISO/IEC 29341311:2017ISO/IEC 29341-31-1:2017(E) vi ISO/IEC 2017 All rights reserved 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, v

33、alidity 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 thes

34、e 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 Microso

35、ft 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 R

36、edmond 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 6687755 / US; 6910068 / US; 7130895 / US; 6725281 / US; 7089307 / US; 7069312 / US; 10/783 524 /US Information may b

37、e 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 6 170 007 / US; 6 139 177 / US; 6 529 936 / US; 6 470

38、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 Bus

39、iness, 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 Longg

40、ang 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

41、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 Jo

42、se, CA USA 95134 BS ISO/IEC 29341311:2017ISO/IEC 29341-31-1:2017(E) viii ISO/IEC 2017 All rights reserved 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

43、for identifying any or all such patent rights. BS ISO/IEC 29341311:2017ISO/IEC 29341-31-1:2017(E) viii ISO/IEC 2017 All rights reserved 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

44、shall not be held responsible for identifying any or all such patent rights. ISO/IEC 29341-31-1:2017(E) ISO/IEC 2017 All rights reserved ix Original UPnP Document Reference may be made in this document to original UPnP documents. These references are retained in order to maintain consistency between

45、 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:2

46、008 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 AVTran

47、sport: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 MediaServ

48、er: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 UPn

49、P 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:2