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 Architecture Part 31-1: Energy management device control protocol Energy management service BS ISO/IEC 29341-31-1:2017 BSI Standards Publication WB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06Information technology UPnP Device Architecture Part 31-1: Energ

2、y management device control protocol Energy management service Technologies de linformation Architecture de dispositif UPnP Partie 31-1: Protocole de contrle du dispositif de management de lnergie Service de management de lnergie INTERNATIONAL STANDARD ISO/IEC 29341-31-1 Reference number ISO/IEC 293

3、41-31-1:2017(E) First edition 2017-09 ISO/IEC 2017 National foreword This 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

4、 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 2017 ISBN 978 0 580 90

5、906 1 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 affected BRITISH ST

6、ANDARD BS ISO/IEC 29341311:2017Information technology UPnP Device Architecture Part 31-1: Energy management device control protocol Energy management service Technologies de linformation Architecture de dispositif UPnP Partie 31-1: Protocole de contrle du dispositif de management de lnergie Service

7、de management de lnergie INTERNATIONAL STANDARD ISO/IEC 29341-31-1 Reference number ISO/IEC 29341-31-1:2017(E) First edition 2017-09 ISO/IEC 2017 BS ISO/IEC 29341311:2017 ii ISO/IEC 2017 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2017, Published in Switzerland All rights reserved. Unle

8、ss 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 a

9、ddress 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-31-1:2017(E) BS ISO/IEC 29341311:2017 ii ISO/IEC 2017 All right

10、s 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 photocopying, or posting on the interne

11、t 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. +41 22 749 01 11 Fax +41 22 749 09 47 co

12、pyrightiso.org www.iso.org ISO/IEC 29341-31-1:2017(E) ISO/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

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

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

15、ral . 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 Ove

16、rview . 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 WakeOnPatte

17、rn signaling operation 21 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 operation . 22 6.4 EnergyManagement service theory of operation . 23 6.5 EnergyManagement control point theory of op

18、eration . 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 Assignme

19、nt 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 ServiceSub

20、scription() . 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 BS ISO/IEC 29341311:2017ISO/IEC 29341-31-1:2017(E) iv ISO/IEC 2017 All rights reserved 6.2.4 Usability

21、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 de

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

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

24、 ServiceRelease() . 19 Table 15 Error codes for ServiceRelease() 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 standa

25、rdization. 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

26、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 joint technical committee, ISO/IEC J TC 1. The procedures used to develop this documen

27、t and those intended f or it s f ur th er 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,

28、 Part 2 (see http:/www.iso.org/directives). Attention is drawn to the possibility that some of the elements of this document m a y b e t h e s u b j e c t o f p a t e n t r i g h t s . I S O a n d I E C s h a l l n o t b e h eld responsible for identifying any or all such patent rights. Details of a

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

30、nt. 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 the following URL: Foreword Supplementary

31、 information ISO/IEC 29341311 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

32、 the general title Information technology UPnP Device Architecture, can be found on the ISO web site. 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 i

33、nvolve 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 co

34、nditions 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 Sta

35、ndards 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

36、 / 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 6687755 / US; 6

37、910068 / 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 b

38、e 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 Electronics Co. Ltd. has informed IEC and ISO th

39、at 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. I

40、nformation 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 More

41、house 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 o

42、r granted patents. Information may be obtained from: Cisco Systems, Inc. 170 West Tasman Drive San Jose, 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 s

43、ubject 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 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

44、 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-31-1:2017(E) ISO/IEC 2017 All rights reserved ix Original UPnP Document Reference may be made in this docume

45、nt 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

46、 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 UP

47、nP 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 Media

48、Renderer: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 Conne

49、ctionManager: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 UP