1、Information technology Device control and management Part 1: Architecture Technologies de linformation Commande et gestion de priphriques Partie 1: Architecture ISO/IEC 2014 INTERNATIONAL STANDARD ISO/IEC 17811-1 First edition 2014-06-15 Reference number ISO/IEC 17811-1:2014(E) ISO/IEC 17811-1:2014(
2、E)ii ISO/IEC 2014 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2014 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 intern
3、et 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 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web w
4、ww.iso.org Published in Switzerland ISO/IEC 17811-1:2014(E) ISO/IEC 2014 All rights reserved iii Contents Page Foreword iv Introduction v 1 Scope . 1 2 Normative references 1 3 T erms and definitions . 1 4 Abbreviations. 2 5 Overview . 2 6 DCM Service Environments . 3 6.1 Case 1: Local Network with
5、Device Management Server . 3 6.2 Case 2: Local Network without Device Management Server 3 6.3 Case 3: Public Network with Device Management Server . 4 7 Requirements 4 7.1 Self-Configuration 4 7.2 Multiple Administrative networks . 5 7.3 Uniform device interface 5 7.4 Common device control and manag
6、ement . 5 7.5 Open Service Interface . 5 7.6 Security and privacy concerns . 5 8 Design Principles . 6 8.1 Auto Configuration 6 8.2 Network Abstraction 6 8.3 Common control and management protocols 6 8.4 Transaction Management 6 8.5 Device Security . 6 Annex A (informative) Example of DCM Operation
7、. 7 Annex B (informative) Standardization activities on Device Control and Management 8 ISO/IEC 17811-1:2014(E) Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. Nationa
8、l 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 interest. O
9、ther 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 intend
10、ed 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 www.iso.or
11、g/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 the document
12、 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 ISO specific terms and ex
13、pressions 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 The committee responsible for this document is ISO/IEC JTC 1, Information technology, SC
14、31, Automatic identification and data capture techniques. ISO/IEC 17811 consists of the following parts, under the general title Information technology Device control and management: Part 1: Architecture Part 2: Specification of Device Control and Management Protocol Part 3: Specification of Reliabl
15、e Message Delivery Protocoliv ISO/IEC 2014 All rights reserved ISO/IEC 17811-1:2014(E) Introduction This International Standard provides the architecture for device control and management (DCM). DCM can support the various control and management services, regardless of the network protocols or inter
16、faces. DCM is composed of two protocols: DCMP (Device Control and Management Protocol) and RMDP (Reliable Message Delivery Protocol). This International Standard consists of the following parts: Part 1: Architecture Part 2: Specification of Device Control and Management Protocol (DCMP) Part 3: Speci
17、fication of Reliable Message Delivery Protocol (RMDP) Part 1 of ISO/IEC 17811 describes the architecture of DCM, which includes definition, general concept, requirements, design principles, service scenarios for device management control, and management. Part 2 of ISO/IEC 17811 specifies the Device
18、Control and Management Protocol (DCMP), which includes the functional entities, protocol operations, message structure, and detailed parameter format associated with DCMP. Part 3 of ISO/IEC 17811 specifies the Reliable Message Delivery Protocol (RMDP), which includes the interworking with DCMP, prot
19、ocol operations, and message structure associated with RMDP. ISO/IEC 2014 All rights reserved v Information technology Device control and management Part 1: Architecture 1 Scope This International Standard provides the relationship between DCMP and RMDP with use cases. Also, this International Stand
20、ard specifies the requirements and design principles. 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest e
21、dition of the referenced document (including any amendments) applies. ISO/IEC 17811-2, Information technology Device control and management Part 2: Specification of Device Control and Management Protocol ISO/IEC 17811-3, Information technology Device control and management Part 3: Specification of R
22、eliable Message Delivery Protocol 3 T erms a nd definiti ons For the purposes of this document, the following terms and definitions apply. 3.1 device control and management DCM operations are purposed to control and manage the various smart devices. For this purpose, DCM is composed of two protocols
23、; DCMP (Device Control and Management Protocol) and RMDP (Reliable Message Delivery Protocol) 3.2 device control and management protocol DCMP used to perform various management operations which are categorized into information retrieval, control, diagnostic, and debugging 3.3 reliable message delive
24、ry protocol RMDP used to provide uniform and reliable message delivery among devices regardless of the underlying network protocols or interfaces 3.4 administrative domain represents a network area where a single administrator can configure and manage a network with the same policy INTERNATIONAL ST
25、ANDARD ISO/IEC 17811-1:2014(E) ISO/IEC 2014 All rights reserved 1 ISO/IEC 17811-1:2014(E) 3.5 device management server DMS used to keep track of the various device information and also to manage the devices in an administrative domain Note 1 to entry: There can be one DMS in an administrative domain
26、, if needed. 3.6 DCM device represents a device that supports the RMDP and DCMP message exchange, parsing, and processing 3.7 node information information which is managed by RMDP, such as physical address identifier, device identifier, and so on 4 Abbreviations The following acronyms are used in th
27、is International Standard. DCM device control and management DCMP device control and management protocol DHCP dynamic host configuration protocol DMS device management server RMDP reliable message delivery protocol UUID universally unique identifier UPnP universal plug and play 5 Overview DCM provid
28、es various functions for the device management. DCM supports the device and network status information retrieval, device and network initialization, firmware and software update, file transmission and so on. In an administrative domain, there may be a device management server that collects, controls
29、, and manages devices using DCMP. To exchange DCMP messages among the devices, RMDP is needed. RMDP is a message exchange protocol among the devices regardless of the network protocols or interfaces. The detailed protocol stack of DCM is illustrated in the Figure 1. Figure 1 Protocol Stack for the D
30、CM Basically, DCMP messages can be exchanged using the RMDP. RMDP has node information, which maintains the mapping information between DCM device identifier and physical network identifier, such as the IP address and port number in IP network. If there is a device management server (DMS) in an admi
31、nistrative domain, the RMDP might be able to obtain the node information about all devices that 2 ISO/IEC 2014 All rights reserved ISO/IEC 17811-1:2014(E) are connected in the administrative domain from the DMS. Note : There are several ways to retrieve node information. For example, the RMDP is abl
32、e to request node information by using the RMDP messages when there is no DMS or when DMS does not response. Therefore the node retrieval mechanisms depend on implementation. When the RMDP retrieves the node information without DMS, the integrity of node information may not be guaranteed After RMDP
33、retrieves the target node information, DCMP messages, such as DEVICE_INFORMATION_ REQUEST or DEVICE_CONTROL_REQUEST, can be transferred to the target device using RMDP. 6 DCM Service Environments 6.1 Case 1: Local Network with Device Management Server Figure 2 shows an example of DCM service environ
34、ment where all devices and a management server are connected in a local network with device management server (DMS). The DMS retrieves device information in the administrative domain and manages devices with DCMP. In this environment the information device, such as smart phone, is able to control th
35、e devices using the DCMP. When smart phone join the administrative domain, RMDP on smart phone could find the DMS and receive the node information about whole devices which are connected in that administrative domain from the DMS. Then DCMP on the smart phone sends the device discovery request messa
36、ge to the other devices and receives the response message by using the RMDP. After that, smart phone is able to see the all devices in the network. If the target device is selected and control information is available by user, DCMP generates and transmits the device control request messages to the t
37、arget device by using the RMDP. Figure 2 DCM service environment case 1: Local network with device management server 6.2 Case 2: Local Network without Device Management Server Figure 3 shows the example of DCM service environment where all devices are connected in the local network without device ma
38、nagement server. The information device, such as smart phone, can control the DCM devices by using the DCM based application. When a node discovery request message is broadcasted by RMDP on the smart phone, RMDPs on the other devices which receive the node discovery request message would response wi
39、th their node information. Then DCMP on the smart phone sends the device discovery request message to the other devices and receives the response message by using the RMDP. After that, smart phone is able to see the all devices in the network. If the target device is selected and control information
40、 is entered by user, DCMP generates the device control request message and sends that control message to the target device by using the RMDP. ISO/IEC 2014 All rights reserved 3 ISO/IEC 17811-1:2014(E) Figure 3 DCM service environment case 2: Local network without device management server 6.3 Case 3:
41、 Public Network with Device Management Server Recently, more devices are connected to the internet directly and provide various services to users as shown in Figure 4. For example, one of the health care product manufacturers sells the scales that are connected to the internet and upload the users w
42、eight and fat data to the manufacturer server automatically. Then, users can check the changes of their own body weight and fat easily by using the smart phone application. For this service, each scale sends the node advertisement message to the device management server using the RMDP that is instal
43、led when the device is manufactured. Then, also DCMP on scale sends the device advertisement message, device registration message and user registration message to the device management server using the RMDP. After these processes, DCMP on scale is able to upload their own data to device management s
44、erver using RMDP. Figure 4 DCM service environment case 3: Public network with device management server 7 Requirements 7.1 S elf-C onfigur ation When a device is connected to a network, the device is automatically plugged in and is used by many different users. The auto configuration can be achieved
45、 in two levels. First is the network auto configuration. When a device is connected to the network, the network configuration shall be set up 4 ISO/IEC 2014 All rights reserved ISO/IEC 17811-1:2014(E) automatically. For example, when a device is connected to the IP network, IP address could be assig
46、ned by the DHCP (Dynamic Host Configuration Protocol) or Auto IP. In addition, all service available in a network are detected and advertised automatically. Each device has different capabilities and thus available services are different. Therefore users know a set of available services for each dev
47、ice. Then user detects available services and start services among them. The service detection and running is performed automatically without any intervention. 7.2 Multiple Administrative networks Devices are connected to the different networks where it is located. So, the network protocols for the
48、networks shall not be network dependant. This means that network independent device management mechanism is required regardless of where a device is located. Since a device is access through multiple administrative network depending on the network hierarchy. Different administrative policy may be en
49、forced to each device where it is located. So, the device management scheme is required to deal with the multiple administrative policies. 7.3 Uniform device interface A user wants to control many different types of device regardless of the manufacturer, device type and device location. However, different types of device provide different device functions while same type of devices is provide some common functions. So, device control and management architecture covers various types of devices. Since the dev
