1、Information Technology Device control and management Part 3: Specification of Reliable Message Delivery Protocol Technologies de linformation Commande et gestion de priphriques Partie 3: Spcification du protocole de livraison fiable de messages ISO/IEC 2014 INTERNATIONAL STANDARD ISO/IEC 17811-3 Fir
2、st edition 2014-10-01 Reference number ISO/IEC 17811-3:2014(E) ISO/IEC 17811-3:2014(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 a
3、ny 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 56 CH-1211
4、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-3:2014(E) ISO/IEC 2014 All rights reserved iii Contents Page Foreword iv Introduction v 1 Scope . 1 2 Terms and definitions . 1 3 Symbols and abbreviated terms . 1 4
5、Overview . 2 5 Protocol Operation . 3 5.1 Node Advertisement 3 5.2 Node Discovery . 3 5.3 Send Message . 4 5.4 Send Event 4 5.5 Object Advertisement 5 6 Messages . 5 6.1 RMDP Message Structure . 5 6.2 Messages according to the Operations . 7 6.3 Error Types of RMDP . 8 6.4 Payload Messages . 9 Bibli
6、ography .14 ISO/IEC 17811-3:2014(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 participate in the development of In
7、ternational 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-governmental, in liai
8、son 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. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint tech
9、nical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is
10、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. ISO/IEC 17811-3 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommit
11、te SC 6, Telecommunications and information exchange between systems. 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 (DCMP) Part 3: Speci
12、fication of Reliable Message Delivery Protocol (RMDP)iv ISO/IEC 2014 All rights reserved ISO/IEC 17811-3:2014(E) Introduction As the IT industry continues to grow, a large number of smart devices have been deployed in the market. Major consumer electronics companies have already provided a variety o
13、f smart devices and appliances; thus, it is expected that the number of smart devices will exceed more than 50% of PCs in the near future. With the growth of smart devices, there is a crucial need for “smart” applications in the market. A smart application represents an application/service that is u
14、sed to control and manage a lot of smart devices with its own purpose over the network, as shown in the examples of smart home appliances, e-health, smart car, and smart works. To provide smart applications or services, the essentially required functionality is to control and manage many devices thr
15、ough the network. However, it is not easy to design the device control and management functions, since the specific requirements for those functions can be very different and affected by various device features, such as device types, capabilities, or manufacturers. In addition, the diverse network e
16、nvironments are also considered in the design of the device control and management function. This International Standard is purposed to make the architecture and protocols for Device Control and Management (DCM). The DCM standard is designed to effectively control and manage various smart devices, r
17、egardless of the device features and underlying network environments. It is expected that the DCM is applicable to a wide range of smart applications. DCM can support the various control and management services, regardless of the network protocols or interfaces. DCM is composed of two protocols: DCM
18、P (Device Control and Management Protocol) and RMDP (Reliable Message Delivery Protocol). This International Standard consists of the following parts: ISO/IEC 17811-1; ISO/IEC 17811-2; ISO/IEC 17811-3. ISO/IEC 17811-1 describes the architecture of DCM which includes definition, general concept, requ
19、irements, design principles, and service scenarios for device management control and management. ISO/IEC 17811-2 specifies the Device Control and Management Protocol (DCMP) which includes the functional entities, protocol operations, message structure, and detailed parameter format associated with D
20、CMP. This part of ISO/IEC 17811 specifies the Reliable Message Delivery Protocol (RMDP) which includes the interworking with DCMP, protocol operations, and message structure associated with RMDP. ISO/IEC 2014 All rights reserved v Information Technology Device control and management Part 3: Specific
21、ation of Reliable Message Delivery Protocol 1 Scope This part of ISO/IEC 17811 provides the specification of Reliable Message Delivery Protocol (RMDP), which is an application-layer protocol used to provide uniform and reliable message delivery among devices regardless of the underlying network prot
22、ocols or interfaces. The network security is out of scope in this part of ISO/IEC 17811. However, the security services might be necessary according to applications of RMDP. RMDP might suffer from many network-specific threats. To countermeasure those threats, some security mechanism can be deployed
23、. 2 Terms and definitions For the purposes of this document, the following terms and definitions apply. 2.1 device control and management DCM operations are purposed to control and manage the various smart devices. For this purpose, DCM is composed of the two protocols: DCMP (Device Control and Mana
24、gement Protocol) and RMDP (Reliable Message Delivery Protocol) SOURCE: ISO/IEC 17811-1:2014, 3.1 2.2 device control and management protocol DCMP used to perform various management operations which are categorized into information retrieval, control, diagnostic, and debugging SOURCE: ISO/IEC 17811-1:
25、2014, 3.2 2.3 reliable message delivery protocol RMDP used to provide uniform and reliable message delivery among devices regardless of the underlying network protocols or interfaces SOURCE: ISO/IEC 17811-1:2014, 3.3 3 Symbols and abbreviated terms The following acronyms are used in this part of ISO
26、/IEC 17811. DCMP Device Control and Management Protocol DCM Device Management Architecture and Protocol INTERNATIONAL ST ANDARD ISO/IEC 17811-3:2014(E) ISO/IEC 2014 All rights reserved 1 ISO/IEC 17811-3:2014(E) RMDP Reliable Message Delivery Protocol NTP Network Time Protocol UUID Universally Unique
27、 Identifier UPnP Universal Plug and Play 4 Overview RMDP is a protocol for the message exchange among the devices. Since each device is connected to a different network, the data transport and network protocols are also different. In addition, some devices are connected directly with different inter
28、faces. Therefore, the RMDP provides a uniform and reliable message exchange protocol among devices regardless of the network protocols or interfaces. Each node has an address translation table, which maintains the mapping information between DCM device identifier (object ID) and physical network ide
29、ntifier such as IP address in IP network. Also, it supports different types of connectivity interfaces such as HDMI and USB. An example of an address translation table is shown in Figure 1. Figure 1 Example address translation table of the RMDP MPType is a protocol type for the multi-target message
30、reception (i.e. UDP or TCP), MCType is a casting type for multi-target message reception (i.e. unicast, broadcast, or multicast), MAddress is a network address for multi-target message reception, MPort is a network port for multi-target message reception, SPType is a protocol type for single-target
31、message reception (i.e. UDP or TCP), SAddress is a network address for single-target message reception, and SPort is a network port for single-target message reception. When a node is initialized first, that node sends a NODE_ADVERTISEMENT message using the broadcast address. Node Information, such
32、as IP address, port number, and so on is included in the NODE_ ADVERTISEMENT message. After sending the NODE_ADVERTISEMENT message, that node can send a NODE_DISCOVERY_REQUEST message using the broadcast address and the corresponding nodes shall return the NODE_DISCOVERY_RESPONSE message. After send
33、ing the NODE_DISCOVERY_RESPONSE message, the corresponding nodes will exchange an OBJECT_ADVERTISEMENT message which includes the information of device identifier. After these processes, each node can send the DCMP message to the other nodes.2 ISO/IEC 2014 All rights reserved ISO/IEC 17811-3:2014(E)
34、 Figure 2 An Example of Reliable Message Delivery Protocol Operation 5 Protocol Operation 5.1 Node Advertisement When a network is enabled or re-configured, a node advertisement operation can be used to inform nodes plug-in or plug-out, as shown in Figure 3. The associated node advertisement transac
35、tion is one- way transaction. This means that only one message is required to finish a transaction, and any response message is not required. Figure 3 Node Advertisement Operation 5.2 Node Discovery For node discovery, NODE_DISCOVERY_REQUEST and NODE_DISCOVERY_RESPONSE messages are exchanged between
36、 the nodes, as shown in Figure 4. A source node sends a NODE_DISCOVERY_REQUEST message to target nodes by broadcast. In response to the NODE_DISCOVERY_REQUEST message, all nodes which fit into the requested information shall respond with a NODE_DISCOVERY_RESPONSE message. ISO/IEC 2014 All rights res
37、erved 3 ISO/IEC 17811-3:2014(E) The node discovery 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
38、transaction or re-issue the transaction. Figure 4 Node Discovery Operation 5.3 Send Message The send message operation is used to send some DCMP message to the other node. The send message operation is performed with a two-message transaction. This operation requires a request message at source and
39、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. Figure 5 Send Message Operation 5.4 Send Event A SEND_EVENT message is used to send some DCMP Message to the other node w
40、ithout any response, as shown in Figure 6. The send event transaction is one-way transaction. This means that only one message is required to finish a transaction and any response message is not required.4 ISO/IEC 2014 All rights reserved ISO/IEC 17811-3:2014(E) Figure 6 Send Event Operation 5.5 Obj
41、ect Advertisement Each node has an address translation table, which maintains the mapping information between device identifier and physical network identifier such as IP address in IP network. If a device is registered in the node, that node shall advertise that fact. The associated object advertis
42、ement transaction is one- way transaction. This means that only one message is required to finish a transaction, and any response message is not required. Figure 7 Object Advertisement Operation 6 Messages 6.1 RMDP Message Structure RMDP message can provide uniform and reliable message exchange prot
43、ocol among devices regardless of the network protocols or interfaces. RMDP message is composed of header and payload. Message header includes the information about Protocol Version, Source Node ID, Target Node ID and Message Type and so on. Message Type, especially, defines the various operations, w
44、hich can be provided by RMDP, and the payload message is determined according to the Message Type. Table 1 and Figure 8 show more details about header message structure of RMDP. ISO/IEC 2014 All rights reserved 5 ISO/IEC 17811-3:2014(E) Figure 8 RMDP Message Header Structure6 ISO/IEC 2014 All rights
45、 reserved ISO/IEC 17811-3:2014(E) Table 1 RMDP Message Header Structure Field Name Size (Byte) Description Version 1 Protocol Version 0x01 Urgent Flag 1 Urgent flag Emergency: 0x01/Normal: 0x00 Partial Flag 1 Indicates whether the current message is the last part of partial message sequence or not 0
46、x00 : the last or partial message sequence Packet Length 2 Message Size (Including Header) Message Length 2 Payload message size Message ID 2 Payload message ID If the message is fragmented, random number message ID will be used. If the value is 0, sequence number is inactive. If the value is not 0,
47、 sequence number will be used. Sequence Number 2 If the message is fragmented, each fragment has a sequence num- ber starting from 1 TransactionID 8 Transaction Identifier The value will be NTP timestamp time_t 8bytes Message Type 2 Message type code for the RMDP operations AppTy pe 2 Payload Messag
48、e Type 0x0000(RMDP), 0x0001(DCMP) CRC 2 Message Error Check Code Packet Length(2Bytes), Message Length(2Bytes), MessageID(2Bytes), AppType(2Bytes), SourceID(Low 2Bytes), DestinationID(Low 2Bytes), TransactionID(2Bytes) XOR value Source ID 16 Source Node ID Random generation using the UUID Can be Ins
49、talled when a device is manufactured Destination ID 16 Destination Node ID (UUID) Source Object ID 16 Source Object ID (ex: Device ID) Destination Object ID 16 Destination Object ID (ex: Device ID) 6.2 Messages according to the Operations Major operations, which can be provided by RMDP, are node information management and DCMP message transmission. These operations can be classified by Message Type and more details about Mes
