IEC 61162-450:2011

IEC 61162-450 ®
Edition 1.0 2011-06
INTERNATIONAL
STANDARD
Maritime navigation and radiocommunication equipment and systems – Digital
interfaces –
Part 450: Multiple talkers and multiple listeners – Ethernet interconnection

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 IEC or IEC's member National Committee in the country of the requester.
If you have any questions about IEC copyright or have an enquiry about obtaining additional rights to this publication,

please contact the address below or your local IEC member National Committee for further information.

IEC Central Office
3, rue de Varembé
CH-1211 Geneva 20
Switzerland
Email: inmail@iec.ch
Web: www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
 Catalogue of IEC publications: www.iec.ch/searchpub
The IEC on-line Catalogue enables you to search by a variety of criteria (reference number, text, technical committee,…).
It also gives information on projects, withdrawn and replaced publications.
 IEC Just Published: www.iec.ch/online_news/justpub
Stay up to date on all new IEC publications. Just Published details twice a month all new publications released. Available
on-line and also by email.
 Electropedia: www.electropedia.org
The world's leading online dictionary of electronic and electrical terms containing more than 20 000 terms and definitions
in English and French, with equivalent terms in additional languages. Also known as the International Electrotechnical
Vocabulary online.
 Customer Service Centre: www.iec.ch/webstore/custserv
If you wish to give us your feedback on this publication or need further assistance, please visit the Customer Service
Centre FAQ or contact us:
Email: csc@iec.ch
Tel.: +41 22 919 02 11
Fax: +41 22 919 03 00
IEC 61162-450 ®
Edition 1.0 2011-06
INTERNATIONAL
STANDARD
Maritime navigation and radiocommunication equipment and systems – Digital
interfaces –
Part 450: Multiple talkers and multiple listeners – Ethernet interconnection

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XB
ICS 47.020.70 ISBN 978-2-88912-492-3

– 2 – 61162-450  IEC:2011(E)
CONTENTS
FOREWORD . 5

1 Scope . 7

2 Normative references . 7

3 Terms and definitions . 8

4 General network and equipment requirements . 11

4.1 Network topology example . 11

4.2 Basic requirements . 12

4.2.1 Requirements for equipment to be connected to the network . 12
4.2.2 Additional requirements for network infrastructure equipment . 12
4.3 Network function (NF) requirements . 13
4.3.1 General requirements . 13
4.3.2 Maximum data rate requirements . 13
4.3.3 Error logging function . 13
4.4 System function (SF) requirements . 15
4.4.1 General requirements . 15
4.4.2 Assignment of unique system function ID (SFI) . 15
4.4.3 Implementing configurable transmission groups . 15
4.5 Serial to network gateway function (SNGF) requirements . 16
4.5.1 General requirements . 16
4.5.2 Serial line output buffer management . 16
4.5.3 Datagram output requirements . 17
4.6 Other network function (ONF) requirements . 17
5 Low level network requirements. 17
5.1 Electrical and mechanical requirements. 17
5.2 Network protocol requirements . 19
5.3 IP Address assignment for equipment . 19
5.4 Multicast address range . 19
6 Transport layer specification . 19
6.1 General . 19
6.2 UDP messages. 20
6.2.1 UDP multicast protocol . 20
6.2.2 Use of multicast addresses and port numbers. 20

6.2.3 UDP checksum . 21
6.2.4 Datagram size . 21
7 Application layer specification . 22
7.1 Datagram header . 22
7.1.1 Valid header . 22
7.1.2 Error logging. 22
7.2 General IEC 61162-1 sentence transmissions . 22
7.2.1 Application of this protocol . 22
7.2.2 Types of messages for which this protocol can be used . 22
7.2.3 TAG block parameters for sentences transmitted in the datagram . 22
7.2.4 Requirements for processing incoming datagrams . 24
7.2.5 Error logging. 24
7.3 Binary image transfer using UDP multicast . 24
7.3.1 Application of this protocol . 24

61162-450  IEC:2011(E) – 3 –
7.3.2 Binary image structure . 25

7.3.3 Header . 25

7.3.4 Binary image descriptor structure . 27

7.3.5 Binary image data fragment . 28

7.3.6 Sender process for binary image transfer . 28

7.3.7 Receiver process for binary image transfer . 29

7.3.8 Other requirements . 30

7.3.9 Error logging. 31

8 Methods of test and required results . 32

8.1 Test set-up and equipment . 32
8.2 Basic requirements . 32
8.2.1 Equipment to be connected to the network . 32
8.2.2 Network infrastructure equipment . 32
8.3 Network function (NF) . 32
8.3.1 Maximum data rate . 32
8.3.2 Error logging function . 33
8.4 System function (SF) . 33
8.4.1 General . 33
8.4.2 Assignment of unique system function ID (SFI) . 33
8.4.3 Implementing configurable transmission groups . 33
8.5 Serial to network gateway function (SNGF) . 33
8.5.1 General . 33
8.5.2 Serial line output buffer management . 33
8.5.3 Datagram output . 34
8.6 Other network function (ONF) . 34
8.7 Low level network . 34
8.7.1 Electrical and mechanical requirements . 34
8.7.2 Network protocol . 34
8.7.3 IP address assignment for equipment . 35
8.7.4 Multicast address range . 35
8.8 Transport layer . 35
8.9 Application layer . 35
8.9.1 Application . 35
8.9.2 Datagram header . 35
8.9.3 Types of messages . 36

8.9.4 TAG block parameters . 36
8.10 Error logging . 36
8.11 Binary image transfer using UDP multicast . 37
8.11.1 Sender process test . 37
8.11.2 Receiver process test . 38
8.11.3 Image descriptor test . 38
8.11.4 Image transfer error logging . 38
Annex A (normative) Classification of IEC 61162-1 talker identifier mnemonics and
sentences . 39
Annex B (informative) TAG block example . 45
Annex C (normative) Reliable transmission of command-response pair messages . 47
Annex D (informative) Network and system design guidance . 52
Bibliography . 60

– 4 – 61162-450  IEC:2011(E)
Figure 1 – Network topology example . 12

Figure 2 – Ethernet frame example for a SBM from a rate of turn sensor . 20

Figure C.1 – Command response communications . 47

Figure C.2 – State diagram . 49

Figure D.1 – General system design architecture . 52

Figure D.2 – Example of ship-shore communication architecture . 53

Figure D.3 – Security infrastructure . 54

Figure D.4 – Decoupled system . 56
Figure D.5 – Loosely coupled system . 56
Figure D.6 – Strongly coupled system . 57

Table 1 – Syslog message format . 14
Table 2 – Syslog error message codes . 14
Table 3 – Interfaces, connectors and cables . 18
Table 4 – Destination multicast addresses and port numbers . 21
Table 5 – Destination multicast addresses and port numbers for binary data transfer . 21
Table 6 – Destination multicast addresses and port numbers for other services . 21
Table 7 – Description of terms . 25
Table 8 – Binary image structure . 25
Table 9 – Header format . 26
Table 10 – Binary image descriptor format . 27
Table 11 – Examples of MIME content type for DataType codes . 28
Table 12 – Binary image data fragment format . 28
Table A.1 – Classification of IEC 61162-1 talker identifier mnemonics . 39
Table A.2 – Classification of IEC 61162-1 sentences . 41
Table B.1 – Defined parameter-codes . 46
Table D.1 – Overview of possible security functions . 55
Table D.2 – Network failure propagation possibilities . 58

61162-450  IEC:2011(E) – 5 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION

____________
MARITIME NAVIGATION AND RADIOCOMMUNICATION

EQUIPMENT AND SYSTEMS –
DIGITAL INTERFACES –
Part 450: Multiple talkers and multiple listeners –

Ethernet interconnection
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.

9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC 61162-450 has been prepared by IEC technical committee 80:
Maritime navigation and radiocommunication equipment and systems.
The text of this standard is based on the following documents:
FDIS Report on voting
80/615/FDIS 80/621/RVD
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.

– 6 – 61162-450  IEC:2011(E)
The committee has decided that the contents of this publication will remain unchanged until

the stability date indicated on the IEC web site under "http://webstore.iec.ch" in the data

related to the specific publication. At this date, the publication will be

• transformed into an International standard,

• reconfirmed,
• withdrawn,
• replaced by a revised edition, or

• amended.
A bilingual version of this publication may be issued at a later date.

61162-450  IEC:2011(E) – 7 –
MARITIME NAVIGATION AND RADIOCOMMUNICATION

EQUIPMENT AND SYSTEMS –
DIGITAL INTERFACES –
Part 450: Multiple talkers and multiple listeners –

Ethernet interconnection
1 Scope
This part of IEC 61162 specifies interface requirements and methods of test for high speed
communication between shipboard navigation and radiocommunication equipment as well as
between such systems and other ship systems that need to communicate with navigation and
radio-communication equipment. This part of IEC 61162 is based on the application of an
appropriate suite of existing international standards to provide a framework for implementing
data transfer between devices on a shipboard Ethernet network.
This standard provides a higher speed and higher capacity alternative to the IEC 61162-1 and
IEC 61162-2 standards while retaining these standards’ basic data format. This standard
provides a higher data capacity than IEC 61162-3.
This standard specifies an Ethernet based bus type network where any listener may receive
messages from any sender with the following properties.
• This standard includes provisions for multicast distribution of information formatted
according to IEC 61162-1, for example position fixes and other measurements, as well as
provisions for transmission of general data blocks (binary image), for example between
radar and VDR.
• This standard is limited to protocols for equipment (Network nodes) connected to a single
Ethernet network consisting only of OSI level one or two devices and cables (Network
infrastructure).
• This standard provides requirements only for equipment interfaces. By specifying
protocols for transmission of IEC 61162-1 sentences and general binary image data these
requirements will guarantee interoperability between equipment implementing this
standard as well as a certain level of safe behaviour of the equipment itself.
• This standard permits equipment using other protocols than those specified in this
standard to share a network infrastructure provided that it is supplied with interfaces which
satisfy the requirements described for ONF (see 4.6).

• This standard does not contain any system requirements other than the ones that can be
inferred from the sum of individual equipment requirements. Thus, to ascertain system
properties that cannot be derived from equipment requirements alone, additional analysis
or standards will be required. In particular, this applies to requirements to maintain system
functionality in the face of a single point failure in equipment or networks. Informative
Annex D contains guidance on how to address such issues.
2 Normative references
The following referenced documents are indispensable for the application of this document.
For dated references, only the edition cited applies. For undated references, the latest edition
of the referenced document (including any amendments) applies.
IEC 60825-2, Safety of laser products – Part 2: Safety of optical fibre communication systems
(OFCS)
– 8 – 61162-450  IEC:2011(E)
IEC 60945, Maritime navigation and radiocommunication equipment and systems – General

Requirements – Methods of testing and required test results

IEC 61162-1, Maritime navigation and radiocommunication equipment and systems – Digital

interfaces – Part 1: Single talker and multiple listeners

IEEE 802.3, IEEE Standards for Local Area Networks: Carrier Sense Multiple Access with

Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications

ISOC RFC 768, User Datagram Protocol, Standard STD0006

ISOC RFC 791, Internet Protocol (IP), Standard STD0005 (and updates)
ISOC RFC 792, Internet Control Message Protocol (ICMP), Standard STD0005 (and updates)
ISOC RFC 826, An ethernet Address Resolution Protocol
ISOC RFC 1918, Address Allocation for Private Internets, Best Current Practice BCP0005
ISOC RFC 2474, Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6
Headers
ISOC RFC 5000, Internet Official Protocol Standards, Standard 0001
ISOC RFC 5227, IPv4 Address Conflict Detection
ISOC RFC 5424, The Syslog Protocol
NMEA 0183:2008, Standard for interfacing marine electronic devices, Version 4.00
NOTE The standards of the Internet Society (ISOC) are available on the IETF websites http://www.ietf.org. Later
updates can be tracked at http://www.rfc-editor.org/rfcsearch.html
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
ASCII
printable 7 bit character encoded in one byte
3.2
binary image
data block without formatting known to this protocol, i.e., non IEC 61162-1 formatted data,
that can be transmitted with the protocol defined in 7.3.
NOTE The term “binary image” is used to differentiate the general data transfer protocol (which may or may not
be in ordinary text format) from the transmission of sentences that is always in 7 bit ASCII format.
3.3
byte
group of 8 bits treated as one unit; this corresponds to what is also sometimes called an octet

61162-450  IEC:2011(E) – 9 –
3.4
command-response pair
CRP
messages exchanged between parties that synchronize state changes on both sides through

the exchange
NOTE 1 CRP are defined in Annex A.

NOTE 2 Both the command and the reply message may also be used as a sensor broadcast message in some

cases. Thus, the implementation of the semantics of the message exchange is somewhat different between

different users of the exchange.

3.5
datagram
one atomic UDP transmission unit on the Ethernet as defined in ISOC RFC 768 and as
constrained elsewhere in this standard
3.6
Ethernet
a carrier sense, multiple access collision detect (CSMA/CD) local area network protocol
standard as defined in IEEE 802.3 and later revisions and additions to IEEE 802
NOTE The types of Ethernet media that can be used for implementation of this standard are defined in Clause 5.
3.7
function block
specified functionality implemented by equipment
NOTE Equipment normally implements multiple function blocks. Requirements to equipment are the sum of
requirements to the function blocks it implements. Function blocks are defined in Clause 4. Types of function
blocks are System Function Block (SF), Other Network Function Block (ONF), Network Function Block (NF) and
Serial to Network Gateway Function Block (SNGF).
3.8
internet assigned number authority
IANA
global coordination of the Domain Name Server (DNS) Root, IP addressing, and other Internet
protocol resources, including UDP and TCP port numbers
NOTE The currently assigned numbers are listed in http://www.iana.org/assignments/port-numbers.
3.9
internet protocol
IP
used and defined in ISOC RFC 791 (and updates)

3.10
message
collection of one or more sentences that are grouped by mechanisms internal to the sentence,
for instance by sequence numbers as in the TXT sentence, i.e. a stand alone sentence is a
message
3.11
message type
classification of IEC 61162-1 sentence formatters into SMB, MSM and CRP types
NOTE 1 SMB, MSM and CRP types are defined in Annex A.
NOTE 2 This standard defines different requirements to the transmission of different message types.

– 10 – 61162-450  IEC:2011(E)

3.12
multi-sentence messages
MSM
logical group of messages and/or sentences where the full meaning of the group is dependent

on the receiver reading the full group

NOTE 1 Multi-sentence messages that are grouped together with a TAG construct is also a sentence group.

NOTE 2 MSM are defined in Annex A.

3.13
network
one physical Ethernet network with one Internet address space, consisting only of the network
nodes, switches, cables and supporting equipment such as power supply units
3.14
network function block
NF
function block responsible for physical connectivity to the network and connectivity to the
transport layer as described in 4.3
3.15
network infrastructure
the part of the Network that provides a transmission path between network nodes
NOTE The network nodes are not part of the network infrastructure.
3.16
network node
physical device connected to the network and which have an Internet address (also called an
Internet host)
NOTE A network node will normally correspond to equipment as the latter term is used in this standard.
3.17
other network function block
ONF
function block that interfaces to the network, but which is not using the protocol definition in
Clauses 5, 6 and 7 of this standard (for example real time streaming of Radar and CCTV
image transfer, VDR sound transfer, etc.)
NOTE Requirements as defined in 4.6 ensure that an ONF can co-reside with SF network nodes and function
blocks that make use of this standard’s protocol.

3.18
sensor broadcast message
SBM
messages consisting of only one sentence
NOTE 1 SBM type messages are sent with a sufficiently high update rate to ensure that the receiver can maintain
the correct status even in environments where some messages may be lost.
NOTE 2 SBM are defined in Annex A.
3.19
sentence
standard information carrying unit as defined in IEC 61162-1
3.20
sentence group
logical group of sentences (which may consist of only one) that need to be processed
together to give full meaning to the information contained in the sentence(s)

61162-450  IEC:2011(E) – 11 –

NOTE 1 The grouping of sentences into sentence group is done by TAG block mechanisms. The sentences in a

sentence group may or may not have the same formatter. A multi sentence message grouped by this mechanism is
also a sentence group.
NOTE 2 This standard allows the explicit grouping of sentences by using coding in a datagram. This standard
does not enforce any relationship between datagram and sentence group. Thus a datagram may contain more than

one sentence group or a sentence group may be split over two or more datagrams.

3.21
serial to network gateway function block

SNGF
function block that enables transfer of sentences between the network and devices that are

compliant with the IEC 61162-1 and IEC 61162-2 serial line interface

3.22
system function block
SF
function block, identified by a unique system function ID (SFI), that is the only function block
that can send information in a datagram format as defined in clause 7
3.23
system function ID
SFI
parameter string as defined in 4.4.2
3.24
transmission group
a pair of a multicast address and a port number that are used by an SF to transmit sentences
NOTE The transmission groups are defined in Table 4 and Annex A defines default transmission groups for the
SF.
3.25
transport annotate and group
TAG
formatted block of data, defined in NMEA 0183, that adds parameters to IEC 61162-1
sentences
NOTE Informative Annex B gives an overview of the TAG blocks used in this standard.
3.26
user datagram protocol
UDP
connection-less datagram protocol defined by ISOC RFC 768; it makes no provision for

transport-layer acknowledgement of packets received
4 General network and equipment requirements
4.1 Network topology example
Figure 1 shows a possible IEC 61162-450 network topology consisting of one IP Local Area
Network (LAN) and a number of different network nodes, each containing different function
blocks. This diagram is informal and does not imply any requirements other than the ones
defined in the following subclauses.

– 12 – 61162-450  IEC:2011(E)

IEC IEC
61162-1 61162-1
SF 3 SF 4
SNGF
SF 1 SF 2 SF 5 SF 6
ONF 1 ONF 2
NF 1 NF 2 NF3 NF 4
Network
IEC  1014/11
SF is “System Function Block”  NF is “Network Function Block”

SNGF is “Serial to Network Gateway Function Block” ONF is “Other Network Function Block”

Figure 1 – Network topology example

Some examples of network nodes are (see Figure 1):
• a sensor, for example a GNSS receiver that is also a network node (SF2 and NF2).
• a device that sends or receives IEC 61162-450 compliant data (sentences and/or binary
image) as well as other types of information onto the network, for example an ECDIS that
can also load chart data from another device (SF1, ONF2 and NF1).
• two independent functions, such as a gyrocompass also approved as a rate of turn sensor
that are implemented in one network node (SF5, SF6 and NF4).
• a system device function block represented by an IEC 61162-1 compliant equipment
connected to a serial to network gateway function (SNGF). In this case, the SNGF will
format outgoing sentences according to requirements in this standard (SF3, SF4, SNGF
and NF3)
• a device that does not send or receive IEC 61162-450 compliant data (sentences and/or
binary image), but which satisfies minimum requirements for compatible use of the same
network (ONF1).
4.2 Basic requirements
4.2.1 Requirements for equipment to be connected to the network
(see 8.2.1)
The requirements for equipment connected to the network are as follows.
• All equipment connected to the network including network infrastructure equipment, shall
satisfy the relevant physical and electrical requirements defined in 5.1.
• All equipment that implements one or more of SF and/or SNGF shall implement the NF.
This equipment shall satisfy the requirements to the function blocks they implement as
defined in 4.3 (NF), 4.4 (SF) and 4.5 (SNGF).

• All other equipment that is not network infrastructure equipment and that shares the
network infrastructure shall comply with requirements to an ONF as defined in 4.6.
• Network infrastructure equipment, i.e., switches, shall satisfy requirements in 4.2.2.
• All equipment connected to a network shall satisfy the requirements of IEC 60945.
Any other equipment is not allowed to be connected to the network.
4.2.2 Additional requirements for network infrastructure equipment
(see 8.2.2)
The following requirements are included to avoid potential problems with certain network
infrastructure equipment:
• routers and repeater hubs shall not be used to interconnect components of an
IEC 61162-450 network;
61162-450  IEC:2011(E) – 13 –

• switches that are used to interconnect equipment compliant with IEC 61162-450 shall not

implement multicast filtering techniques, such as IGMP snooping or CGMP.

NOTE 1 IGMP is Internet Group Management Protocol and CGMP is Cisco Group Management Protocol. If

switches are capable of implementing multicast filtering techniques, then this functionality should be disabled.

NOTE 2 Routers are network infrastructure devices that can forward datagrams between networks. Repeater hubs

are network infrastructure devices without internal storage that repeat incoming datagrams onto all outgoing

connections. Switches are network infrastructure devices that based on forwarding tables can process, and forward
datagrams between nodes on the same network, using intermediate storage in the switch before retransmission.

4.3 Network function (NF) requirements

4.3.1 General requirements
All equipment that implements a NF shall satisfy the requirements in Clauses 5 and 6.
4.3.2 Maximum data rate requirements
(see 8.3.1)
The manufacturer shall specify the maximum input rate under which the equipment can still
perform all functions required by its performance standards.
Maximum input rate shall be specified as:
a) maximum number of datagrams per second received, intended for and processed by the
equipment;
b) maximum number of datagrams per second received by but not intended for the
equipment;
c) maximum number of datagrams per second received by, but not intended for, the
equipment at 50 % of the maximum load for item a).
NOTE “Received by” means datagrams that are received on a transmission group that the equipment listens to.
“Intended for” are datagrams that are processed by the equipment as part of its specified function.
The maximum data rates shall be the mean rate over a 10 s measurement period.
4.3.3 Error logging function
(see 8.3.2)
4.3.3.1 Internal logging
Means shall be provided in each NF to record errors that occur in the NF itself as well as SF

and SNGF using it. Subclauses 4.5.2, 7.1.2, 7.2.5 and 7.3.9 give minimum requirements as to
what shall be logged.
As a minimum, the manufacturer shall provide mechanisms by which error logs can be
inspected by a human operator. It is allowed that the inspection is done through a simple
network mechanism such as a terminal emulator, a datagram as defined in this standard or
any other reasonable method.
The minimum requirements for the log are to count the number of each occurrence. The
counter may reset itself by a manufacturer specified method.
4.3.3.2 External logging
A NF may be configured to support external logging, where non-trivial information is sent to a
logging server. In this case a “syslog” message, as defined in ISOC RFC 5424, shall be used.

– 14 – 61162-450  IEC:2011(E)

Syslog messages shall be formatted as ASCII text messages and sent as UDP packets on

port 514 and the multicast address defined in Table 6. Error messages defined in this

standard shall be reported through a simplified message as described in Table 1, where

italicised words are place-holders for data explained in the right hand column. Other

characters shall be transmitted as shown, including spaces.

Table 1 – Syslog message format

Element Description
The combined priority and facility code (number from 0 to 199 inclusive) enclosed in pointed

brackets. For the errors defined in this standard, the value 131 shall be used (facility “local
use 0” and priority “error condition”).

Version The version code. The code 1 (one) shall be used for messages from this version of the
standard.
Space One space character.
Timestamp Timestamp, containing date and time and optional UTC offset, in a valid format, for example
1985-04-12T23:20:50-03:00. The example shows date, followed by upper case “T”, then
local time and finally offset from UTC (3 hours west – negative, east offsets shall be
prefixed by a ‘+’. UTC offset can be abbreviated to a single upper case “Z”, without leading
‘-‘ or ‘+’). Alternatively, the timestamp field may be nil (‘-‘, a single dash character).
Space One space character
Hostname The host name of the network node, represented as the IP address in dotted decimal
notation. Alternatively, this field may be nil (‘-‘, a single dash character).
Space A space character
Appname The application name. This shall be the string “450-“ followed by the configured SFI code if
the error originates in the SF or SNGF, “NF” if the error originates from the network function
block or “ONF” if it originates in the ONF function block.
Space A space character
Procid Normally, this field should be nil (‘-‘ a dash character). Other values as defined in the
Syslog standard may be used.
Space A space character
Msgid For errors defined in this standard, this field shall be the error code as defined in Table 2.
Space A space character
Structured This field can be nil (‘-‘, a single dash character) or contain information as defined in
ISOC RFC 5424.
Space A space character
Msg A free format message in ASCII format.

A ”syslog” packet shall not exceed 480 bytes and shall be sent as a single UDP datagram.

NOTE This standard does not specify requirements for equipment receiving syslog messages. This type of
equipment would fall into the category of ONF. As the above specification is a subset of the full ISOC RFC 5424
specification, implementers of such equipment should refer to ISOC RFC 5424 and make sure that syslog
messages from other ONF can be received and processed without problems.
To facilitate the use of the syslog protocol, the errors defined in this standard have been
assigned a message identity as defined in Table 2.
Table 2 – Syslog error message codes
Message identity Description Sub-clause
101 SNGF buffer overflow 4.5.2
102 Datagram header error 7.1.2
103 TAG or sentence format error 7.2.5
104 Binary image error 7.3.9
61162-450  IEC:2011(E) – 15 –

Additional information can be given in the “Msg” field, if available.

4.4 System function (SF) requirements

4.4.1 General requirements
(see 8.4.1)
Equipment that implements an SF shall satisfy the following requirements:

• requirements in 6.2 shall be satisfied for all equipment implementing SF;

• requirements in 7.2 shall be satisfied for all equipment implementing IEC 61162-1

sentence transmitting or receiving function blocks;
NOTE This also includes function blocks with the ability to send heartbeat (HBT) sentences.
• requirements in 7.3 shall be satisfied for equipment that implements an SF that can
transmit or receive binary image data.
4.4.2 Assignment of unique system function ID (SFI)
(see 8.4.2)
The format of the SFI parameter string shall be “ccxxxx” where “cc” is two valid characters as
defined in IEC 61162-1 and “xxxx” is four numeric characters.
An SF implementing the functionality of an equipment that has been given a talker mnemonic
code in IEC 61162-1 shall use this talker mnemonic as the “cc” characters in the SFI.
NOTE Other SF may have their SFI string format defined in other standards or the manufacturer may have to
choose a code. In the latter case, the already defined talker mnemonic codes should be avoided.
The numeric character string "xxxx" will be an instance number in the range "0000" to "9999"
The numeric character string “9999” is reserved for an un-configured SF and shall not be
used by any transmitting SF during normal operation. However, all receiving equipment shall
accept the “9999” string.
During normal operation, the SFI parameter string shall be unique for all SF in an
IEC 61162-450 network.
NOTE It is recommended that all SF on a ship, independent on whether they are residing on one common network
or not, are given a ship unique SFI.
Means shall be provided by the manufacturer to configure the SFI for each SF (see 7.2.3.4).

4.4.3 Implementing configurable transmission groups
(see 8.4.3)
Each SF shall be assigned a single transmission group for all outgoing messages. The default
for this transmission group is determined by the SFI as described in Annex A.
For each SF that the equipment implements, the man
...