1、 Reference number ISO/IEC 14908-4:2012(E) ISO/IEC 2012INTERNATIONAL STANDARD ISO/IEC 14908-4 First edition 2012-02-15 Information technology Control network protocol Part 4: IP communication Technologies de linformation Protocole de rseau de contrle Partie 4: Communication IP ISO/IEC 14908-4:2012(E)
2、 COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2012 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the addr
3、ess 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 www.iso.org Published in Switzerland ii ISO/IEC 2012 All rights reserved - 2 - 14908-4 ISO/IEC:201 (E) Conten
4、ts Page FOREWORD .4 Introduction5 1 Scope.7 2 Normative references .8 3 Terms, definitions and abbreviations8 3.1 Terms and definitions.8 3.2 Abbreviations9 4 Requirements9 5 CNP/IP device specification .10 5.1 IP Related device specifications10 5.2 CNP related device specifications.10 6 IP channel1
5、1 6.1 Specification11 6.2 IP transport mechanisms .13 7 CNP/IP device14 7.1 Configuration of a CNP/IP device 14 7.2 Configuration parameters 14 7.3 Configuration techniques.16 8 CNP/IP messages17 8.1 Definition of CNP/IP messages and modes of operation.17 8.2 Common message header .18 8.3 Packet seg
6、mentation 19 8.4 Data packet exchange 22 8.5 Configuration server interactions24 8.6 Miscellaneous Status Messages32 8.7 Vendor Specific Messages.36 8.8 Authentication of CNP Packets36 9 Packet formats 38 9.1 Packet Types.38 9.2 Common CNP/IP Header 39 9.3 Segment Packet 41 9.4 CNP Data Packets .42
7、9.5 CNP/IP Device Registration/configuration packets42 9.6 Channel Membership Packet .46 9.7 Channel Routing Packet.47 9.8 Request Packet .49 9.9 Acknowledge Packet 50 9.10 Send List Packet .51 9.11 Node Status/Health/Statistics Response Message 52 Annex A (normative) Specifications for the CNP stan
8、dard .55 Annex B (informative) Specifications for CNP .57 Figures Figure 1 Typical CNP/IP application. 7 Figure 2 IP protocol stack. 13 14908-4 ISO/IEC:2012 (E) - 3 - Figure 3 Packet bunching. 19 Figure 4 Authentication encoding and decoding of CNP packets . 37 Tables Table 1 Device Registration wit
9、h Configuration Server Protocol . 28 Table 2 Server to Device Unsolicited Configuration Message Protocol 29 Table 3 Device to Server Channel Membership Request Protocol. 29 Table 4 Device to Server Send List Request Protocol 31 Table 5 Device to Server Channel Routing Update Protocol 31 Table 6 6 De
10、vice to Server Channel Routing Request Protocol . 32 Table 7 Protocol for Requesting a Devices Configuration 35 Table 8 Protocol for Requesting a Devices Send List 35 Table 9 Protocol for Requesting a Devices Channel Definition 35 Table 10 Protocol for Requesting a Devices Channel Routing Informatio
11、n 36 Table 11 Message type cross reference.39 Table 12 Common Packet Header format . 39 Table 13 Segment Packet format 41 Table 14 Data Packet format 42 Table 15 Device registration/configuration packet format. 43 Table 16 Channel Membership Packet format 46 Table 17 Channel Routing Packet formats.
12、47 Table 18 Configuration Request Packet format 49 Table 19 Request Reason codes . 50 Table 20 Request Amount codes . 50 Table 21 Request Action codes 50 Table 22 Acknowledge Packet formats 51 Table 23 Send List Packet format 52 Table 24 Node Status/Health/Statistics Response Message 53 - 4 - 14908-
13、4 ISO/IEC:2012 (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 International Stand
14、ards 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 liaison with ISO and
15、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 technical committee i
16、s 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. ISO/IEC 14908-4 was prepared b
17、y CEN/TC 247 and was adopted, under a special “fast-track procedure”, by Joint Technical Committee ISO/IEC JTC 1, Information technology, in parallel with its approval by the national bodies of ISO and IEC. ISO/IEC 14908 consists of the following parts, under the general title Information technology
18、 Control network protocol: Part 1: Protocol stack Part 2: Twisted pair communication Part 3: Power line channel specification Part 4: IP communication 14908-4 ISO/IEC:2012 (E) - 5 - Introduction This International Standard has been prepared to provide mechanisms through which various vendors of loca
19、l area control networks may exchange information in a standardised way. It defines communication capabilities. This International Standard is used by all involved in design, manufacture, engineering, installation and commissioning activities. The International Organization for Standardization (ISO)
20、and International Electrotechnical Commission (IEC) draw attention to the fact that it is claimed that compliance with this International Standard may involve the use of patents held by Echelon Corporation The ISO and IEC take no position concerning the evidence, validity and scope of this patent ri
21、ght. The holder of this putative patent right has assured the ISO and IEC that they are willing to negotiate licences under reasonable and non-discriminatory terms and conditions with applicants throughout the world. In this respect, the statement of the holder of the putative patent rights is regis
22、tered with the ISO and IEC. Information may be obtained from: Echelon Corporation, 4015 Meridian Avenue, San Jose, CA 94304, USA, phone +1-408- 938-5234, fax: +1-408-790-3800 http:/. Attention is drawn to the possibility that some of the elements of this International Standard may be the subject of
23、patent rights other than those identified above. ISO and IEC shall not be held responsible for identifying any or all such patent rights. - 7 - INFORMATION TECHNOLOGY CONTROL NETWORK PROTOCOL Part 4: IP communication 1 Scope This International Standard specifies the transporting of the Control Netwo
24、rk Protocol (CNP) packets for commercial local area control networks over Internet Protocol (IP) networks using a tunnelling mechanism wherein the CNP packets are encapsulated within IP packets. It applies to both CNP nodes and CNP routers. The purpose of this International Standard is to insure int
25、eroperability between various CNP devices that wish to use IP networks to communicate using the CNP protocol. The main body of this International Standard is independent of the CNP protocol being transported over the IP network. The reader is directed to Annex A and Annex B for the normative and inf
26、ormative, respectively, aspects of this specification that are specific to ISO/IEC 14908-1. Figure 1 shows a possible configuration of such CNP devices and networks connected to an IP network. Workstation running CNP Stack Embedded CNP Device CNP/IP to CNP/IP Router CNP/IP to CNP/IP Router CNP/IP Ro
27、uter CNP/IP Router CNP/IP Router INTERNET CNP Nodes CNP Nodes CNP Nodes CNP Channel CNP Channel CNP Channel IP Channel IP ChannelFigure 1 Typical CNP/IP application Figure 1 depicts two types of CNP devices: CNP nodes and CNP routers. It should be noted that the routers shown can route packets betwe
28、en typical CNP channels (such as twisted pair or power line) and an IP channel or it can route CNP packets between two IP channels. In this International Standard the IP channel will be defined in such a way to allow it to be used like any other CNP channel. In the above diagram the IP network can b
29、e considered to be one or more IP channels. This International Standard covers only how CNP packets are transported over IP channels. It does not cover how CNP packets are routed between standard CNP channels and IP channels. This specification is not intended to cover the lower layers (physical, MA
30、C and link layers) of either standard CNP or IP channels. 14908-4 ISO/IEC:2012 (E) - 8 - 2 Normative references None. 3 Terms, definitions and abbreviations 3.1 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1.1 tunneling encapsulation of one pr
31、otocols packet within the payload of another protocols packets 3.1.2 channel common communications transport mechanism that a specific collection of CNP devices share and communicate over without the use of a router NOTE 1 Channels are used to transport CNP packets below the link layer of the CNP pr
32、otocol stack. NOTE 2 Typically this refers to some type of physical media such as power line, RF, or twisted pair, but in the case of IP networks this channel is not physical, but a protocol tunnel. 3.1.3 CNP device device that uses the CNP protocol to communicate with other CNP devices NOTE Specifi
33、cally a CNP/IP device is a CNP device that communicates with other CNP devices over an IP channel. 3.1.4 CNP router special type of CNP device that routes CNP protocol packets between two or more channels NOTE Specifically a CNP/IP router is a CNP router in which at least one of the channels it rout
34、es packets over is an IP channel. 3.1.5 CNP node special type of CNP device that can send or receive CNP protocol packets, but does not route them between channels NOTE 1 Specifically a CNP/IP node is a CNP node in which at least one of the channels it sends and receives packets over is an IP channe
35、l. NOTE 2 All CNP devices are either routers, nodes or both. 3.1.6 CNP group collection of CNP devices that share a common multicast address 3.1.7 node ID logical network address that differentiates nodes within the same subnet or domain 14908-4 ISO/IEC:2012 (E) - 9 - 3.1.8 Must Be Zero (MBZ) reserv
36、ed field that may be used in the following versions of the protocol NOTE Such fields shall be sent as zero and ignored by the receiver in implementations conforming to the current version of the specification. 3.2 Abbreviations CTP Channel Timeout Period CNP Control Network Protocol LFS Last Forward
37、ed Sequence MBZ Must Be Zero NTP Network Time Protocol PSN Packet Sequence Number SA/DA Source Address / Destination Address SID Session Identifier SNTP Simple Network Time Protocol UDP User Datagram Protocol 4 Requirements The following is a set of general requirements for the transporting of CNP p
38、ackets over IP channels: be as efficient as possible to allow quasi real-time operation; be independent of the application level interface used to receive the packets. For example the tunnelling protocol should not rely on the existence of a socket interface or how that interface may be used; insure
39、 that CNP packet ordering is preserved; insure that CNP packets that are “stale” (outside the maximum timeout characteristics of the IP channel) are not forwarded; detect packets that get duplicated in the IP network; support IP routing devices that prioritise IP packets; optional security measures
40、to prevent malicious users from tampering with devices; scalable; allow status information to be extracted from CNP/IP devices; support the exchange of configuration information between CNP/IP devices and configuration servers. 14908-4 ISO/IEC:2012 (E) - 10 - 5 CNP/IP device specification 5.1 IP Rel
41、ated device specifications A CNP/IP device shall behave like any standard IP host capable of exchanging IP packets with any other IP host either on the same IP subnet or anywhere else in the Internet cloud. A CNP/IP device shall have a single unicast IP address and may be capable belonging to as man
42、y as 32 multi-cast groups. It is optional that a CNP/IP device support multi-casting. This document does not address the routing of IP packets between subnets or through the Internet. The CNP/IP devices shall be compatible with whatever standard mechanisms (IP routers, switches etc.) are required to
43、 perform the IP routing functions. 5.2 CNP related device specifications 5.2.1 Packet formats The general format of CNP packets which are tunnelled over the IP channel are those packets that are received from or sent to the Link layer (layer 2) of the CNP protocol stack. Refer to Annex A for a preci
44、se specification of the packet formats corresponding to the CNP protocol. 5.2.2 Addressing schemes Different CNP protocols generally use different addressing schemes to exchange packets. Although it is generally not necessary to understand the contents of a CNP packet or its addresses in order to tu
45、nnel CNP packets over IP, some aspects of the CNP addressing scheme are reflected in the process of configuration. This is especially true when it comes to setting up the IP channels that are used for tunnelling. Since CNP protocols use different addressing schemes the terminology used in the main b
46、ody of this specification for describing addresses are meant to be general and rich enough to describe the superset of addressing schemes used in all CNP protocols. The following CNP addressing terms are used in this specification. Unique ID. This refers to an ID that is globally unique to all devic
47、es within a specific protocol. Unique IDs are generally fixed in nature in that they never change through the life of a device. Domain. This is the highest level of a three level hierarchical addressing scheme. Domain IDs should be unique within a particular network. This means that in a particular
48、network where Domains are used if two devices have the same Domain ID they belong to the same Domain. Domain IDs are generally logical in nature and can be changed and configured. Subnet. This is the middle level of a three level hierarchical addressing scheme. Subnet IDs should be unique within a p
49、articular domain. This means that in a particular network where subnet IDs are used if two devices have the same Domain ID and the same Subnet ID then they belong to the same Subnet. Some CNPs do not use Domains in which case the Subnet may be the highest level of address for a device. Subnet IDs are generally logical in nature and can be changed and configured. Node. This is the lowest level of any hierarchical addressing scheme. Node
