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 PublicationBS ISO/IEC 29341-12-1:2015Information technology UPnP Device ArchitecturePart 12-1: Remote User Interface DeviceControl Protocol - Remote User InterfaceClient DeviceBS ISO/IEC 29341-12-1:2015 BRITISH STANDARDNational forewordThis British Standard is the UK implementation of

2、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 provisions

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

4、he authority of the Standards Policy and Strategy Committee on 30 June 2015.Amendments/corrigenda issued since publicationDate 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 Client DeviceTechnolo

5、gies de linformation Architecture de dispositif UPnP Partie 12-1: Protocole de contrle de dispositif dinterface utilisateur distance Dispositif client dinterface utilisateur distanceINTERNATIONAL STANDARDISO/IEC 29341-12-1Reference numberISO/IEC 29341-12-1:2015(E)Second edition 2015-06-15 ISO/IEC 20

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

7、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 officeCase postale 56 CH-1211 Geneva 20Tel. + 41 22 749 01 11Fax + 41 22 749 09 47E-mail cop

8、yrightiso.orgWeb www.iso.orgPublished in SwitzerlandISO/IEC 29341-12-1:2015(E)BS ISO/IEC 29341-12-1:2015CONTENTS Foreword iv Introduction . v 1. Scope 12. Device Definitions . 22.1. Device Type . 2 2.2. Device Model 2 2.2.1. Description of Device Requirements 2 2.2.2. Relationships Between Services

9、. 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 . 54. Test . 6Annex A (normative) Access Control Definitions (if DeviceSecurity service is implemented) . 7 A.1 Permissions 7 A.2 Profiles . 8 A.3

10、 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 permissions for RemoteUIClient Service 7

11、ISO/IEC 29341-12-1:2015(E)BS ISO/IEC 29341-12-1:2015For 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 members of ISO or IEC participate in the

12、 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, governmental and non-gov

13、ernmental, 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 described in the ISO/IE

14、C 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 to the possibility

15、 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 on the ISO list

16、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 expressions related to conformity assessment, as w

17、ell 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 procedure, by joint technical committee ISO/IEC

18、 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 29341 series, under the general title In

19、formation 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:2015I ntroduction 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 I

20、EC 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 applicants throughout the world. In this r

21、espect, 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 Licensing Department 5200 NE Elam Young Parkway M

22、S: 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 524 /US Information may be obtained from:

23、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; 6 529 936 / US; 6 470 339 / US; 6 571 3

24、88 / 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 from: ISO/IEC 29341-12-1:2015(E)BS ISO/I

25、EC 29341-12-1:2015Digital 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 those identified above. ISO and IEC shall not

26、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 published by ISO/IEC and by UPnP Implementers Cor

27、poration. 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 Architecture:1 ISO/IEC 29341-3-1 UPnP MediaRenderer:1

28、 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 29341-3-13 UPnP MediaRenderer:2 Device IS

29、O/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-12 UPnP RenderingControl:2 Service ISO/IEC

30、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 DigitalSecurityCameraStillImage:1 Service ISO/IEC 2934

31、1-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 HouseStatus:1 Service ISO/IEC 29341-6-13 UPnP

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

33、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 Device ISO/IEC 29341-8-4 UPnP WLANAccessPoi

34、ntDevice: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 WANCableLinkConfig:1 Service ISO/IEC 29341-8-14 UP

35、nP 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 29341-8-19 UPnP WANPPPConnection:1 Service IS

36、O/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:2015UPnP Document Title ISO/IEC 29341 Part UPnP Fe

37、eder: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 UPnP QosPolicyHolder:1 Service ISO/IEC 29341

38、-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 RemoteUIClientDevice:1 Device ISO/IEC 29341-12-1 UPnP Remot

39、eUIServerDevice: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 29341-12-1:2015(E)BS ISO/IEC 29341-12-1:2015ISO

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

41、s 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/IEC 29341-12-1:2015(E)BS ISO/IEC 29341-12-1:20

42、152. 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 with support for securing UPnP actions. It is a

43、lso 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 a device that encompasses the RemoteUIClientDe

44、vice. 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 RemoteUIClient Allows for basic operations on a R

45、emote 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 sessions, and invoking secure actions. 2.2.1.1. Devic

46、eSecurity 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 expose devices of the type urn:schemas-upnp-org

47、: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 ID2RemoteUIClientDevice:1 Yes R RemoteUIClient:1

48、 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 ISO/IEC 29341-12-1:2015Relationship between Servi

49、ces 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 example of this would be where urn:schemas-upnp-org:device: RemoteUIClientDevice:1 is implemented in