1、Information technology Device control and management Part 2: Specification of Device Control and Management Protocol Technologies de linformation Commande et gestion de priphriques Partie 2: Spcifications du protocole de commande et gestion de priphriques ISO/IEC 2015 INTERNATIONAL STANDARD ISO/IEC
2、17811-2 First edition 2015-02-15 Reference number ISO/IEC 17811-2:2015(E) ISO/IEC 17811-2:2015(E)ii 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 f
3、orm 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 address below or ISOs member body in the country of the requester. ISO copyright office Case postale
4、56 CH-1211 Geneva 20 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 17811-2:2015(E) ISO/IEC 2015 All rights reserved iii Contents Page Foreword iv Introduction v 1 Scope . 1 2 Terms and definitions . 1 3 Abbreviation . 2 4 Overvi
5、ew . 2 5 Protocol Operation . 4 5.1 Device Discovery . 4 5.2 Device Advertisement . 5 5.3 Device Information Retrieval 5 5.4 Device Control . 5 5.5 Event Notification . 6 5.6 Event Subscription . 6 5.7 Get File Information . 7 5.8 File Download 7 5.9 File Upload 8 5.10 Apply 9 5.11 Device Registrati
6、on . 9 5.12 Service Registration .10 6 Messages 10 6.1 DCMP Message Structure 10 6.2 Messages according to the Operations 12 6.3 Error Types of DCMP 13 6.4 Payload Messages 15 Annex A (normative) Unit Types and Codes 50 Annex B (normative) Device Types .51 Annex C (informative) XML Schema and Exampl
7、e of DCMP Payload Message .52 Bibliography .130 ISO/IEC 17811-2:2015(E) Foreword 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
8、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 organizations, govern
9、mental 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 maintenance are descr
10、ibed 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.org/directives). Attention is drawn to the
11、 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 the Introduction and/or on t
12、he 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 expressions related to conformity assessme
13、nt, 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 17811-2 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology SC 6, Telecommunications and info
14、rmation exchange between systems.iv ISO/IEC 2015 All rights reserved ISO/IEC 17811-2:2015(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
15、 interfaces. DCM is composed of two protocols; device control and management protocol (DCMP) and reliable message delivery protocol (RMDP). This International Standard, ISO/IEC 17811, consists of the following parts: Part 1: Architecture Part 2: Specification of Device Control and Management Protoco
16、l Part 3: Specification of Reliable Message Delivery Protocol ISO/IEC 17811-1 describes the architecture of DCM, which includes definition, general concept, requirements, design principles, service scenarios for device management control, and management. ISO/IEC 17811-2 specifies the Device Control
17、and Management Protocol (DCMP), which includes the functional entities, protocol operations, message structure, and detailed parameter format associated with DCMP. ISO/IEC 17811-3 specifies the Reliable Message Delivery Protocol (RMDP), which includes the interworking with DCMP, protocol operations,
18、 and message structure associated with RMDP. The International Organization for Standardization (ISO) and International Electrotechnical Commission (IEC) draws attention to the fact that it is claimed that compliance with this International Standard may involve the use of a patent concerning the mes
19、sage structure of DCMP given in Clause 7. ISO and IEC take no position concerning the evidence, validity, and scope of this patent right. The holder of this patent right has assured the ISO and IEC that he is willing to negotiate licences either free of charge or under reasonable and non-discriminat
20、ory terms and conditions with applicants throughout the world. In this respect, the statement of the holder of this patent right is registered with ISO and IEC. Information may be obtained from:Patent Holder: Electronics and Telecommunications Research Institute (ETRI)Address: 138 Gajeongno, Yuseong
21、-gu, Daejeon, 305-700, Korea 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 be held responsible for identifying any or all such patent rights. ISO (www.iso.org/patents) and
22、IEC (http:/ /patents.iec.ch) maintain on-line databases of patents relevant to their standards. Users are encouraged to consult the databases for the most up to date information concerning patents. ISO/IEC 2015 All rights reserved v Information technology Device control and management Part 2: Specif
23、ication of Device Control and Management Protocol 1 Scope This part of ISO/IEC 17811 provides the specification of Device Control and Management Protocol (DCMP), which is an application-layer protocol used to control and manage the various devices. DCMP supports the device and network status informa
24、tion retrieval, device initialization, firmware and software update, file transmission, and so on. This part of ISO/IEC 17811 specifies the protocol operations and message structure of DCMP. The network security is out of scope in this part of ISO/IEC 17811. However, the security services can be nec
25、essary according to applications of DCMP. DCMP can suffer from many network specific threats. To countermeasure those threats, some security mechanism can be deployed. 2 Terms and definitions For the purposes of this document, the following terms and definitions apply. 2.1 device control and managem
26、ent DCM purposed to control and manage the various smart devices Note 1 to entry: For this purpose, DCM is composed of the two protocols; Device Control and Management Protocol (DCMP) and Reliable Message Delivery Protocol (RMDP). SOURCE: ISO/IEC 17811-1 2.2 device control and management protocol DC
27、MP used to perform various management operations which are categorized into information retrieval, control, diagnostic, and debugging SOURCE: ISO/IEC 17811-1 2.3 reliable message delivery protocol RMDP used to provide uniform and reliable message delivery among devices regardless of the underlying n
28、etwork protocols or interfaces SOURCE: ISO/IEC 17811-1 2.4 administrative domain represents a network area where a single administrator can configure and manage a network with the same policy SOURCE: ISO/IEC 17811-1 INTERNATIONAL ST ANDARD ISO/IEC 17811-2:2015(E) ISO/IEC 2015 All rights reserved 1 I
29、SO/IEC 17811-2:2015(E) 2.5 device management server DMS used to keep track of the various device information and also to manage the devices in an administration domain Note 1 to entry: There may be one DMS in an administrative domain, if needed. SOURCE: ISO/IEC 17811-1 3 Abbreviation The following a
30、bbreviations are used in this document. DCMP Device Control and Management Protocol DCM Device Management Architecture and Protocol DMS Device Management Server RMDP Reliable Message Delivery Protocol NTP Network Time Protocol UUID Universally Unique Identifier UPnP Universal Plug and Play 4 Overvie
31、w The DCMP is a protocol used to control and manage a variety of smart devices in the network. The DCMP messages are exchanged between different devices or between device and DMS. The DCMP operates over RMDP for reliable message delivery. In the networking perspective, RMDP provides one or more devi
32、ces with an interface to the network. That is, a group of devices are connected to an RMDP node via an internal API interface or a network, and the RMDP performs the reliable delivery of DCMP messages to the different RMDP nodes which are also connected to other devices. For this purpose, RMDP maint
33、ains the mapping information between DCM device identifier and physical network identifier such as IP address and port number. After RMDP retrieves the target node information, DCMP messages can be exchanged over RMDP. Figure 1 gives a general example of DCM operations between a device and DMS. Thos
34、e operations are divided into RMDP initialization, DCMP initialization, and management service.2 ISO/IEC 2015 All rights reserved ISO/IEC 17811-2:2015(E) Figure 1 DCM Operations The RMDP manages the mapping information between the device identifier and physical network identifier. For an advertiseme
35、nt of the physical network identifier information in the RMDP initialization phase, a “NODE_ADVERTISEMENT” and “NODE_DISCOVERY_REQUEST/RESPONSE” messages are broadcast by the RMDP. To advertise the device identifier information, an OBJECT_ADVERTISEMENT message is then broadcast by the RMDP. The phys
36、ical address information of the DMS can be added in the RMDP module of a device using the API of RMDP. The RMDP module of the device sends a NODE_ ADVERTISEMENT message using a broadcast to the other devices connected in the local network, but the RMDP module of the device uses a unicast when sendin
37、g the NODE_ADVERTISEMENT message to the DMS. The RMDP module of the DMS can manage the physical address information of the device using the socket information, that is, the IP address and port information of the access point (AP) or router. In the DCMP initialization phase, the DCMP modules of DMS a
38、nd device can retrieve the basic information of the concerned devices (e.g. device name, device ID and device type) by using the “DEVICE_ ADVERTISEMENT” and “DEVICE_DISCOVERY_REQUEST/RESPONSE” messages. In these processes, the DCMP module asks its RMDP module with the device ID of the target (corres
39、ponding) device by using a DCMP message, and then the RMDP module will transmit the received DCMP message to the target RMDP module of the target device. In the management service phase, a device can register its basic information (e.g., model name, model number and serial number) on the DMS server
40、by using the “DEVICE_REGISTRATION_REQUEST/RESPONSE” message of DCMP. The protocol operations of DCMP are classified as follows: Device Discovery; Device Advertisement; ISO/IEC 2015 All rights reserved 3 ISO/IEC 17811-2:2015(E) Device Information Retrieval; Device Control; Event Notification; Event S
41、ubscription; Get File Information; File Download; File Upload; Apply; Device Registration; and Service Registration. 5 Protocol Operation 5.1 Device Discovery For device discovery, a DEVICE_DISCOVERY_REQUEST and DEVICE_DISCOVERY_RESPONSE messages are exchanged between devices, as shown in Figure 2.
42、A source device broadcasts a DEVICE_DISCOVERY_ REQUEST message to the target devices. In response to the DEVICE_DISCOVERY_REQUEST message, all devices which fit into the requested information shall respond with a DEVICE_DISCOVERY_RESPONSE message. Figure 2 Device Discovery Operation The device disco
43、very operation is performed with a two-message transaction. This operation requires a request message at source and a response message at the destination. When a response message is not received within a specific time interval, the source may cancel the transaction or re-issue the transaction.4 ISO/
44、IEC 2015 All rights reserved ISO/IEC 17811-2:2015(E) 5.2 Device Advertisement The device advertisement operation can be used to inform devices plug-in or plug-out, as shown in Figure 3. The associated device advertisement transaction is one-way transaction. This means that only one message is requir
45、ed to finish a transaction, and any response message is not required. Figure 3 Device Advertisement Operation 5.3 Device Information Retrieval The device information retrieval operation can be used when a device needs to know the various device information such as device ID, device name, device prop
46、erty, device status and so on. The volume of the device information is various and depends on the type of device and its capability. To accommodate different level of devices, we may categorize the relevant information into device basic information, device configuration, and system and network infor
47、mation. The basic information represents the fixed information for all devices, whereas the other information is variable for each device. The operation of device information retrieval is composed of two-message transaction, as shown in Figure 4. This operation requires a request message at source a
48、nd a response message at destination. When a response message is not received within a specific time interval, the source may cancel the transaction or re-issue the transaction. Figure 4 Device Information Retrieval Operation 5.4 Device Control Device control is used to perform device specific opera
49、tions. For device control, a source device shall provide the control code and parameters associated with the device control operation. When a ISO/IEC 2015 All rights reserved 5 ISO/IEC 17811-2:2015(E) target device receives a DEVICE_CONTROL_REQUEST message, it checks if it the message contains a valid control code for the device and if the control code can be supported. If so, it executes the control operation requested and returns the result to the source device with a DEVICE_CONTROL
