ISO/IEC 14908-4:2012
(Main)Information technology - Control network protocol - Part 4: IP communication
Information technology - Control network protocol - Part 4: IP communication
ISO/IEC 14908-4:2011 specifies the transporting of the Control Network 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 ISO/IEC 14908-4:2011 is to ensure interoperability between various CNP devices that wish to use IP networks to communicate using the CNP.
General Information
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 14908-4
First edition
2012-02-15
Information technology — Control
network protocol —
Part 4:
IP communication
Technologies de l'information — Protocole de réseau de contrôle —
Partie 4: Communication IP
Reference number
©
ISO/IEC 2012
© 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 address below or
ISO's 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 copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2012 — All rights reserved
- 2 - 14908-4 © ISO/IEC:201 (E)
Contents
Page
FOREWORD .4
Introduction.5
1 Scope.7
2 Normative references .8
3 Terms, definitions and abbreviations.8
3.1 Terms and definitions.8
3.2 Abbreviations.9
4 Requirements.9
5 CNP/IP device specification .10
5.1 IP Related device specifications.10
5.2 CNP related device specifications.10
6 IP channel.11
6.1 Specification.11
6.2 IP transport mechanisms .13
7 CNP/IP device.14
7.1 Configuration of a CNP/IP device .14
7.2 Configuration parameters .14
7.3 Configuration techniques.16
8 CNP/IP messages.17
8.1 Definition of CNP/IP messages and modes of operation.17
8.2 Common message header .18
8.3 Packet segmentation .19
8.4 Data packet exchange .22
8.5 Configuration server interactions.24
8.6 Miscellaneous Status Messages.32
8.7 Vendor Specific Messages.36
8.8 Authentication of CNP Packets.36
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
9.5 CNP/IP Device Registration/configuration packets.42
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 standard .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 with 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 Device to Server Channel Routing Request Protocol . 32
Table 7 — Protocol for Requesting a Device’s Configuration. 35
Table 8 — Protocol for Requesting a Device’s Send List. 35
Table 9 — Protocol for Requesting a Device’s Channel Definition. 35
Table 10 — Protocol for Requesting a Device’s Channel Routing Information. 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. 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-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 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
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.
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 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.
ISO/IEC 14908-4 was prepared by 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 — 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 local 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) 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
right. 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 registered 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://www.echelon.com.
Attention is drawn to the possibility that some of the elements of this International Standard
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.
14908-4 © ISO/IEC:2012 (E) - 7 -
INFORMATION TECHNOLOGY – CONTROL NETWORK PROTOCOL –
Part 4: IP communication
1 Scope
This International Standard specifies the transporting of the Control Network 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 interoperability 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 informative,
respect
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.