1、BSI Standards Publication BS ISO/IEC 29341-12-2:2015 Information technology UPnP Device Architecture Part 12-2: Remote User Interface Device Control Protocol Remote User Interface Server DeviceBS ISO/IEC 29341-12-2:2015 BRITISH STANDARD National foreword This British Standard is the UK implementatio
2、n of ISO/IEC 29341-12-2: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 pro
3、visions 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 88291 3 ICS 35.200 Compliance with a British Standard cannot confer immunity from legal obligations. This British Standard was publ
4、ished 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 dBS ISO/IEC 29341-12-2:2015 Information technology UPnP Device Architecture Part 12-2: Remote User Interface Device Control Protocol Rem
5、ote User Interface Server Device Technologies de linformation Architecture de dispositif UPnP Partie 12-2: Protocole de contrle de dispositif dinterface utilisateur distance Dispositif serveur dinterface utilisateur distance INTERNATIONAL STANDARD ISO/IEC 29341-12-2 Reference number ISO/IEC 29341-12
6、-2:2015(E) Second edition 2015-06-15 ISO/IEC 2015 BS ISO/IEC 29341-12-2: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,
7、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 the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20
8、Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ISO/IEC 29341-12-2:2015(E)BS ISO/IEC 29341-12-2: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
9、 Device Requirements 2 2.2.2. Relationships Between Services . 4 2.3. Theory of Operation . 4 2.3.1. Secure Remote UI Servers (if DeviceSecurity implemented in Remote UI server device) 4 3. XML Device Description . 5 4. Test . 6 Annex A (normative) Access Control Definitions (if DeviceSecurity servi
10、ce is implemented) . 7 A.1 Permissions 7 A.2 Profiles . 8 A.3 Access Control List (ACL) entry . 9 LIST OF TABLES Table 1: RemoteUIServerDevice Service Descriptions 2 Table 2: Device Requirements for stand-alone RemoteUIServerDevice . 2 Table 3: Device Requirements for embedded RemoteUIServerDevice .
11、 3 Table 4: Defined permissions for RemoteUIServer Service . 7 ISO/IEC 29341-12-2:2015(E)BS ISO/IEC 29341-12-2:2015 For ewor d ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. N
12、ational 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 inter
13、est. 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
14、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
15、:/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
16、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 meaning of the ISO speci
17、fic 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 information ISO/IEC 29341-12-2 was prepared by UPnP Implementers Corporation and adopte
18、d, 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. This second edition replaces the first edition (ISO/IEC 29341-12-2:2008), which has been technically revised. The list of all currently ava
19、ilable 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 29341-12-2:2015(E)BS ISO/IEC 29341-12-2:2015 I ntroduction ISO and IEC draw attention to the fact that it is claimed that compliance with this docu
20、ment 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
21、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 ISO and IEC that it has patent applications or granted patents. Information may be obtained from: Intel Cor
22、poration Standards Licensing 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 /
23、 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 ISO and IEC that it has patent applications or granted patents. Information may be obtained from: Philips International B.V. IP 6 1
24、70 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 ISO and IEC that it has patent applications or granted patents.
25、Information may be obtained from: ISO/IEC 29341-12-2:2015(E)BS ISO/IEC 29341-12-2: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 pa
26、tent rights other than those 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 th
27、e specifications as published 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
28、29341-2 UPnP AV Architecture: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 Renderi
29、ngControl:1 Service ISO/IEC 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:
30、2 Service ISO/IEC 29341-4-12 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 2
31、9341-5-11 UPnP DigitalSecurityCameraStillImage: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 I
32、SO/IEC 29341-6-12 UPnP HouseStatus: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:
33、1 Device ISO/IEC 29341-7-1 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 U
34、PnP WANConnectionDevice:1 Device 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/I
35、EC 29341-8-13 UPnP WANCableLinkConfig: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 WANPOTSLinkC
36、onfig:1 Service ISO/IEC 29341-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 UPnP Feeder:1.0 Service ISO/I
37、EC 29341-9-11 ISO/IEC 29341-12-2:2015(E)BS ISO/IEC 29341-12-2:2015 UPnP Document Title ISO/IEC 29341 Part 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 Se
38、rvice ISO/IEC 29341-10-11 UPnP 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-
39、11-12 UPnP RemoteUIClientDevice: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/I
40、EC 29341-13-11 ISO/IEC 29341-12-2:2015(E)BS ISO/IEC 29341-12-2:2015 ISO/IEC 29341-12-2:2015(E)BS ISO/IEC 29341-12-2:2015 INFORMATION TECHNOLOGY UPNP DEVICE ARCHITECTURE Part 12-2: Remote User Interface Device Control Protocol Remote User Interface Server Device 1. Scope This device template is compl
41、iant with the UPnP Architecture, Version 1.0. This document defines the device urn:schemas-upnp-org:device:RemoteUIServerDevice:1. This device can be a UPnP root device, or embedded within a different device. The RemoteUIServerDevice encapsulates all services for the Remote UI Server Device Control
42、Protocol (DCP). ISO/IEC 2015 - All rights reserved ISO/IEC 29341-12-2:2015(E)BS ISO/IEC 29341-12-2: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:RemoteUIServerDevice:1 2.2. Device Model It i
43、s recommended that RemoteUIServerDevice be implemented 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
44、either inside RemoteUIServerDevice implementation or in a device that encompasses the RemoteUIServerDevice. These two models are described below. 2.2.1. Description of Device Requirements The following table briefly describes the service used in RemoteUIServerDevice. Table 1: RemoteUIServerDevice Se
45、rvice Descriptions Service Name Service Description RemoteUIServer Allows for basic discovery of available and remotable user interfaces. DeviceSecurity Actions for taking ownership, configuring access control, establishing secure sessions, and invoking secure actions. 2.2.1.1. DeviceSecurity within
46、 RemoteUIServerDevice This model is typically applicable to physical devices that need DeviceSecurity functionality (including device ownership and access control) to be used only by the RemoteUIServerDevice. In this case, products that expose devices of the type urn:schemas-upnp-org:device:RemoteUI
47、ServerDevice:1 must implement minimum version numbers of the required service specified in the table below. Table 2: Device Requirements for stand-alone RemoteUIServerDevice DeviceType Root Req. or Opt. 1ServiceType Req. or Opt. 1Service ID 2RemoteUIServerDevice:1 Yes R RemoteUIServer:1 R RemoteUISe
48、rver 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: Relationship between Services ISO/IEC 2015 - All rights reserved ISO/IEC 29341-12-2:2015(E)BS
49、 ISO/IEC 29341-12-2:2015 Figure 1 shows the logical structure of the device and services defined by the working group for UPnP technology enabled Remote UI servers. Figure 1: DeviceSecurity within RemoteUIServerDevice 2.2.1.2. DeviceSecurity outside RemoteUIServerDevice This model is typically applicable to physical devices that implement Remote UI server functionality, but the RemoteUIServerDevice may use DeviceSecurity that is already part of another device. An example of this would be wher
