BS EN IEC 61162-450:2018
$102.76
Maritime navigation and radiocommunication equipment and systems. Digital interfaces – Multiple talkers and multiple listeners. Ethernet interconnection
Published By | Publication Date | Number of Pages |
BSI | 2018 | 90 |
IEC 61162-450:2018 is also available as /2 which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition. IEC 61162-450:2018 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 document 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 document specifies an Ethernet based bus type network where any listener can receive messages from any sender with the following properties. – This document 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 file), for example between radar and VDR, and also includes provisions for multicast distribution of information formatted according to IEC 61162-3, for example position fixes and other measurements. – This document 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 document provides requirements only for equipment interfaces. By specifying protocols for transmission of IEC 61162-1 sentences, IEC 61162-3 PGN messages and general binary file data, these requirements will guarantee interoperability between equipment implementing this document as well as a certain level of safe behaviour of the equipment itself. – This document permits equipment using other protocols than those specified in this document to share a network infrastructure, provided that it is supplied with interfaces which satisfy the requirements described for ONF. – This document includes provisions for filtering of the network traffic in order to limit the amount of traffic to manageable level for each individual equipment. This document does not contain any system requirements other than the ones that can be inferred from the sum of individual equipment requirements. An associated standard, IEC 61162-460, further addresses system requirements. This second edition of IEC 61162-450 cancels and replaces the first edition published in 2011 and Amendment 1:2016. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) network traffic filtering based on IGMP snooping added; b) network traffic balancing added; c) new encapsulation of IEC 61162-3 PGNs added; d) new alternative for binary file transfer added: TCP/IP based on Annex H of IEC 62388:2007 on radars; e) general authentication tag “a:” added to support managing of cyber security risk.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
7 | CONTENTS |
12 | FOREWORD |
14 | 1 Scope 2 Normative references |
15 | 3 Terms and definitions |
19 | 4 General network and equipment requirements 4.1 Network topology example |
20 | 4.2 Basic requirements 4.2.1 Requirements for equipment to be connected to the network Figures Figure 1 – Network topology example |
21 | 4.2.2 Additional requirements for network infrastructure equipment 4.3 Network function (NF) requirements 4.3.1 General requirements 4.3.2 Maximum data rate requirements |
22 | 4.3.3 Error logging function |
23 | Tables Table 1 – Syslog message format |
24 | 4.3.4 Provisions for network traffic filtering – IGMP 4.4 System function block (SF) requirements 4.4.1 General requirements 4.4.2 Assignment of unique system function ID (SFI) Table 2 – Syslog error message codes |
25 | 4.4.3 Implementing configurable transmission groups 4.5 Serial to network gateway function (SNGF) requirements 4.5.1 General requirements |
26 | 4.5.2 Serial line output buffer management |
27 | 4.5.3 Datagram output requirements 4.5.4 Multi SF serial port 4.5.5 Handling malformed data received on serial line |
28 | 4.6 PGN to network gateway function (PNGF) requirements 4.6.1 General requirements 4.6.2 Output buffer management from IEC 61162-450 network to IEC 61162-3 network 4.6.3 Datagram output requirements 4.6.4 PGN group number |
29 | 4.7 Other network function (ONF) requirements 5 Low level network requirements 5.1 Electrical and mechanical requirements |
30 | 5.2 Network protocol requirements Table 3 – Interfaces, connectors and cables |
31 | 5.3 IP address assignment for equipment 5.4 Multicast address range 5.5 Device address for instrument networks 6 Transport layer specification 6.1 General |
32 | 6.2 UDP messages 6.2.1 UDP multicast protocol 6.2.2 Use of multicast addresses and port numbers Figure 2 – Ethernet frame example for a SBMfrom a rate of turn sensor |
33 | Table 4 – Destination multicast addresses and port numbers |
34 | 6.2.3 UDP checksum 6.2.4 Datagram size Table 5 – Destination multicast addresses and port numbersfor binary data transfer Table 6 – Destination multicast addresses and port numbersfor other services |
35 | 7 Application layer specification 7.1 Datagram header 7.1.1 Valid header 7.1.2 Error logging 7.2 General IEC 61162-1 sentence transmissions 7.2.1 Application of this protocol 7.2.2 Types of messages for which this protocol can be used 7.2.3 TAG block parameters for sentences transmitted in the datagram |
39 | 7.2.4 Requirements for processing incoming datagrams 7.2.5 Error logging for processing incoming datagrams 7.3 Binary file transfer using UDP multicast – Single transmitter, multiple receivers 7.3.1 Application of this protocol |
40 | 7.3.2 Binary file structure 7.3.3 61162-450 header Table 7 – Description of terms Table 8 – Binary file structure |
41 | Table 9 – 61162-450 header format |
42 | 7.3.4 Binary file descriptor structure |
43 | 7.3.5 Binary file data fragment Table 10 – Binary file descriptor format Table 11 – Examples of MIME content type for DataType codes Table 12 – Binary file data fragment format |
44 | 7.3.6 Sender process for binary file transfer |
45 | Figure 3 – Non re-transmittable sender process |
47 | 7.3.7 Receiver process for binary file transfer Figure 4 – Re-transmittable sender process |
49 | 7.3.8 Other requirements Figure 5 – Re-transmittable receive process |
51 | 7.3.9 Error logging 7.4 General IEC 61162-3 PGN message transmissions 7.4.1 Message structure Table 13 – Structure for PGN message |
52 | 7.4.2 Message format 7.4.3 Address translation requirements Table 14 – PGN message descriptor |
53 | 7.4.4 Message processing 7.4.5 Additional management requirements 7.5 System function ID resolution 7.5.1 General |
54 | 7.5.2 Transmitter functions 7.6 Binary file transfer using TCP point-to-point 7.6.1 Definition Table 15 – Description of terms |
55 | 7.6.2 Data field structure for transfer of files Table 16 – Binary file structure Table 17 – Header structure |
56 | Table 18 – Package data structure |
57 | 7.6.3 Structure of the transfer stream 7.6.4 TCP port and IP addresses 7.6.5 Implementation guidance |
58 | 8 Methods of test and required results 8.1 Test set-up and equipment |
59 | 8.2 Basic requirements 8.2.1 Equipment to be connected to the network 8.2.2 Network infrastructure equipment 8.2.3 Documentation 8.3 Network function (NF) 8.3.1 Maximum data rate |
60 | 8.3.2 Error logging function 8.4 System function block (SF) 8.4.1 General 8.4.2 Assignment of unique system function ID (SFI) 8.4.3 Implementing configurable transmission groups 8.5 Serial to network gateway function (SNGF) 8.5.1 General |
61 | 8.5.2 Serial line output buffer management 8.5.3 Datagram output 8.5.4 Datagram output multi SF serial port |
62 | 8.5.5 Handling malformed data received on serial line |
63 | 8.6 Other network function (ONF) |
64 | 8.7 Low level network 8.7.1 Electrical and mechanical requirements 8.7.2 Network protocol 8.7.3 IP address assignment for equipment 8.7.4 Multicast address range 8.8 Transport layer |
65 | 8.9 Application layer 8.9.1 Application 8.9.2 Datagram header 8.9.3 Types of messages 8.9.4 TAG block parameters |
66 | 8.9.5 General authentication |
67 | 8.10 Error logging 8.11 Binary file transfer using UDP multicast – Single transmitter, multiple receiver 8.11.1 Sender process test |
68 | 8.11.2 Receiver process test |
69 | 8.11.3 Binary file descriptor test 8.11.4 Binary file transfer error logging |
70 | 8.11.5 Maximum outgoing rate 8.12 PGN to network gateway function (PNGF) 8.12.1 General 8.12.2 Output buffer management 8.12.3 Datagram output 8.12.4 PGN group 8.12.5 Address conflicts 8.13 System function ID resolution 8.14 Binary file transfer using TCP point-to-point |
71 | 8.14.1 Test of transmit client 8.14.2 Test of receiver server |
72 | 8.14.3 Maximum outgoing rate 8.14.4 TCP port and IP addresses |
73 | Annexes Annex A (normative) Classification of IEC 61162-1 talker identifiermnemonics and sentences A.1 General A.2 Talker identifier mnemonic to transmission group mapping Table A.1 – Classification of IEC 61162-1 talker identifier mnemonics |
75 | A.3 List of all sentence formatters and the sentence type Table A.2 – Classification of IEC 61162-1 sentences |
79 | Annex B (normative) TAG block definitions B.1 Validity B.2 Valid TAG block characters B.3 TAG block format |
80 | B.4 TAG block “hexadecimal checksum” (*hh) B.5 TAG block “line” |
81 | B.6 TAG block parameter-code dictionary Table B.1 – Defined parameter-codes |
82 | Annex C (normative) Reliable transmission of command-response pair messages C.1 Purpose C.2 Information exchange examples C.3 Characteristics C.4 Requirements Figure C.1 – Command response communications |
83 | C.5 Data flow description C.5.1 Heartbeat message C.5.2 Command response pair |
84 | Annex D (informative) Compatibility between IEC 61162-450 nodes based on IEC 61162-450:2011 connected to network which uses methods based on IEC 61162-450:2018 D.1 General D.2 Alternative methods for compatibility D.2.1 Use of IGMP proxy node D.2.2 Use of virtual LAN (VLAN) |
85 | D.2.3 Use of static multicast switch configuration |
86 | Annex E (informative) Use of switch setup configuration to filter network traffic |
87 | Annex F (normative) Sentence to support SFI collision detection F.1 General F.2 SRP – System function ID resolution protocol |
88 | Bibliography |