BS ISO IEC 29341-12-1-2015 Information technology UPnP Device Architecture Remote User Interface Device Control Protocol Remote User Interface Client Device《信息技术 UPnP设备架构 .pdf

1、BSI Standards Publication BS ISO/IEC 29341-12-1:2015 Information technology UPnP Device Architecture Part 12-1: Remote User Interface Device Control Protocol - Remote User Interface Client DeviceBS ISO/IEC 29341-12-1:2015 BRITISH STANDARD National foreword This British Standard is the UK implementat

2、ion of ISO/IEC 29341-12-1:2015. The UK participation in its preparation was entrusted to Technical Committee IST/6, Data communications. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary p

3、rovisions of a contract. Users are responsible for its correct application. The British Standards Institution 2015. Published by BSI Standards Limited 2015 ISBN 978 0 580 88290 6 ICS 35.200 Compliance with a British Standard cannot confer immunity from legal obligations. This British Standard was pu

4、blished under the authority of the Standards Policy and Strategy Committee on 30 June 2015. Amendments/corrigenda issued since publication Date T e x t a f f e c t e dInformation technology UPnP Device Architecture Part 12-1: Remote User Interface Device Control Protocol - Remote User Interface Clie

5、nt Device Technologies de linformation Architecture de dispositif UPnP Partie 12-1: Protocole de contrle de dispositif dinterface utilisateur distance Dispositif client dinterface utilisateur distance INTERNATIONAL STANDARD ISO/IEC 29341-12-1 Reference number ISO/IEC 29341-12-1:2015(E) Second editio

6、n 2015-06-15 ISO/IEC 2015 BS ISO/IEC 29341-12-1:2015ii ISO/IEC 2015 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2015 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

7、, 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 the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 F

8、ax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ISO/IEC 29341-12-1:2015(E)BS ISO/IEC 29341-12-1:2015 CONTENTS Foreword iv Introduction . v 1. Scope 1 2. Device Definitions . 2 2.1. Device Type . 2 2.2. Device Model 2 2.2.1. Description of Device Requirements 2 2

9、.2.2. Relationships Between Services . 4 2.3. Theory of Operation . 4 2.3.1. Secure Remote UI Clients (if DeviceSecurity implemented in Remote UI client device) . 4 3. XML Device Description . 5 4. Test . 6 Annex A (normative) Access Control Definitions (if DeviceSecurity service is implemented) . 7

10、 A.1 Permissions 7 A.2 Profiles . 8 A.3 Access Control List (ACL) entry . 9 LIST OF TABLES Table 1: RemoteUIClientDevice Service Descriptions . 2 Table 2: Device Requirements for stand-alone RemoteUIClientDevice . 2 Table 3: Device Requirements for embedded RemoteUIClientDevice 3 Table 4: Defined pe

11、rmissions for RemoteUIClient Service 7 ISO/IEC 29341-12-1:2015(E)BS ISO/IEC 29341-12-1:2015 For ewor d ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are

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

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

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

15、). 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

16、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 meaning of the ISO specific terms and expression

17、s 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 29341-12-1 was prepared by UPnP Implementers Corporation and adopted, under the PAS procedu

18、re, by joint technical committee ISO/IEC JTC 1. Information technology, in parallel with its approval by national bodies of ISO and IEC. This second edition replaces the first edition (ISO/IEC 29341-12-1:2008), which has been technically revised. The list of all currently available parts of ISO/IEC

19、29341 series, under the general title Information technology UPnP Device Architecture, can be found on the ISO web site. ISO/IEC 29341-12-1:2015(E)BS ISO/IEC 29341-12-1:2015 I ntroduction ISO and IEC draw attention to the fact that it is claimed that compliance with this document may involve the use

20、 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 a

21、pplicants 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 ISO and IEC that it has patent applications or granted patents. Information may be obtained from: Intel Corporation Standards Licensin

22、g Department 5200 NE Elam Young Parkway MS: JFS-98 USA Hillsboro, Oregon 97124 Microsoft Corporation has informed ISO and IEC 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 5

23、24 /US Information may be obtained from: Microsoft Corporation One Microsoft Way USA Redmond WA 98052 Philips International B.V. has informed ISO and IEC 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

24、; 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 ISO and IEC that it has patent applications or granted patents. Information may be obtained

25、 from: ISO/IEC 29341-12-1:2015(E)BS ISO/IEC 29341-12-1:2015 Digital Media Business, Samsung Electronics Co. Ltd. 416 Maetan-3 Dong, Yeongtang-Gu, KR Suwon City 443-742 Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights other than thos

26、e identified above. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Original UPnP Documents Reference may be made in this document to original UPnP documents. These references are retained in order to maintain consistency between the specifications as publish

27、ed by ISO/IEC and by UPnP Implementers Corporation. 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 UPnP Basic:1 Device ISO/IEC 29341-2 UPnP AV Architectur

28、e:1 ISO/IEC 29341-3-1 UPnP MediaRenderer:1 Device ISO/IEC 29341-3-2 UPnP MediaServer:1 Device ISO/IEC 29341-3-3 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

29、 29341-3-13 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 UPnP AVTransport:2 Service ISO/IEC 29341-4-10 UPnP ConnectionManager:2 Service ISO/IEC 29341-4-11 UPnP ContentDirectory:2 Service ISO/IEC 29341-4-1

30、2 UPnP RenderingControl:2 Service ISO/IEC 29341-4-13 UPnP ScheduledRecording:1 ISO/IEC 29341-4-14 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 DigitalSecur

31、ityCameraStillImage:1 Service ISO/IEC 29341-5-12 UPnP HVAC_System:1 Device ISO/IEC 29341-6-1 UPnP HVAC_ZoneThermostat:1 Device ISO/IEC 29341-6-2 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 Hous

32、eStatus: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 UPnP BinaryLight:1 Device ISO/IEC 29341-7-1

33、UPnP DimmableLight:1 Device ISO/IEC 29341-7-2 UPnP Dimming:1 Service ISO/IEC 29341-7-10 UPnP SwitchPower:1 Service ISO/IEC 29341-7-11 UPnP InternetGatewayDevice:1 Device ISO/IEC 29341-8-1 UPnP LANDevice:1 Device ISO/IEC 29341-8-2 UPnP WANDevice:1 Device ISO/IEC 29341-8-3 UPnP WANConnectionDevice:1 D

34、evice ISO/IEC 29341-8-4 UPnP WLANAccessPointDevice:1 Device ISO/IEC 29341-8-5 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 WANCable

35、LinkConfig: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 293

36、41-8-19 UPnP WANPPPConnection:1 Service ISO/IEC 29341-8-20 UPnP WLANConfiguration:1 Service ISO/IEC 29341-8-21 UPnP Printer:1 Device ISO/IEC 29341-9-1 UPnP Scanner:1.0 Device ISO/IEC 29341-9-2 UPnP ExternalActivity:1 Service ISO/IEC 29341-9-10 ISO/IEC 29341-12-1:2015(E)BS ISO/IEC 29341-12-1:2015 UPn

37、P Document Title ISO/IEC 29341 Part 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 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 U

38、PnP QosPolicyHolder:1 Service ISO/IEC 29341-10-12 UPnP QoS Architecture:2 ISO/IEC 29341-11-1 UPnP QOS v2 Schema Files ISO/IEC 29341-11-2 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 RemoteUIClientDe

39、vice:1 Device ISO/IEC 29341-12-1 UPnP RemoteUIServerDevice:1 Device ISO/IEC 29341-12-2 UPnP RemoteUIClient:1 Service ISO/IEC 29341-12-10 UPnP RemoteUIServer:1 Service ISO/IEC 29341-12-11 UPnP DeviceSecurity:1 Service ISO/IEC 29341-13-10 UPnP SecurityConsole:1 Service ISO/IEC 29341-13-11 ISO/IEC 2934

40、1-12-1:2015(E)BS ISO/IEC 29341-12-1:2015 ISO/IEC 29341-12-1:2015(E)BS ISO/IEC 29341-12-1:2015 INFORMATION TECHNOLOGY UPNP DEVICE ARCHITECTURE Part 12-1: Remote User Interface Device Control Protocol Remote User Interface Client Device 1. Scope This device template is compliant with the UPnP Device A

41、rchitecture, Version 1.0. This document defines the device urn:schemas-upnp-org:device:RemoteUIClientDevice:1. This device can be a UPnP root device, or embedded within a different device. The RemoteUIClientDevice encapsulates all services for the Remote UI Client Device Control Protocol (DCP). ISO/

42、IEC 29341-12-1:2015(E)BS ISO/IEC 29341-12-1:2015 2. Device Definitions 2.1. Device Type The following device type identifies a device that is compliant with this template: urn:schemas-upnp-org:device:RemoteUIClientDevice:1 2.2. Device Model It is recommended that RemoteUIClientDevice be implemented

43、with support for securing UPnP actions. It is also recommended that securing of UPnP action is done using the DeviceSecurity service as defined by the UPnP security working committee. If implemented, the DeviceSecurity service must be contained either inside RemoteUIClientDevice implementation or in

44、 a device that encompasses the RemoteUIClientDevice. These two models are described below. 2.2.1. Description of Device Requirements The following table briefly describes the services used in RemoteUIClientDevice. Table 1: RemoteUIClientDevice Service Descriptions Service Name Service Description Re

45、moteUIClient Allows for basic operations on a Remote UI client including: user interface connection management, optionally user interface availability management and optionally basic user interaction. DeviceSecurity Actions for taking ownership, configuring access control, establishing secure sessio

46、ns, and invoking secure actions. 2.2.1.1. DeviceSecurity within RemoteUIClientDevice This model is typically applicable to physical devices that need DeviceSecurity functionality (including device ownership and access control) to be used only by the RemoteUIClientDevice. In this case, products that

47、expose devices of the type urn:schemas-upnp-org:device:RemoteUIClientDevice:1 must implement minimum version numbers of the required service specified in the table below. Table 2: Device Requirements for stand-alone RemoteUIClientDevice DeviceType Root Req. or Opt. 1ServiceType Req. or Opt. 1Service

48、 ID 2RemoteUIClientDevice:1 Yes R RemoteUIClient:1 R RemoteUIClient DeviceSecuirty:1 O DeviceSecurity Non-standard services embedded by an UPnP vendor go here. X To be defined by vendor 1R = Required, O = Optional, X = Non-standard. 2Prefixed by urn:upnp-org:serviceId: . ISO/IEC 29341-12-1:2015(E)BS

49、 ISO/IEC 29341-12-1:2015 Relationship between Services Figure 1 shows the logical structure of the device and services defined by the working group for UPnP technology enabled Remote UI clients. Figure 1: DeviceSecurity within RemoteUIClientDevice 2.2.1.2. DeviceSecurity outside RemoteUIClientDevice This model is typically applicable to physical devices that implement Remote UI Client functionality, but the RemoteUIClientDevice may use DeviceSecurity that is already part of another device. An exampl