IEC 61162-450:2011 pdf – Maritime navigation and radio communication equipment and systems – Digitalinterfaces – Part 450:Multiple talkers and multiple listeners -Ethernet interconnection.
5.2 Network protocol requirements (see 8.7.2)
Equipment shall implement IP v4 as generally described in ISOC RFC 5000 with a minimum requirement of support for the following specific network protocols:
• ARP — Address Resolution Protocol as described in ISOC RFC 826 and as updated in ISOC RFC 5227:
• IP — Internet Protocol as described in ISOC RFC 791 and as updated in ISOC RFC 2474;
• UDP — User datagram Protocol as described in ISOC RFC 766;
• ICMP — Internet Control Message Protocol as described in ISOC RFC 792.
5.3 IP Address assignment for equipment (see 8.7.3)
Means shall be provided to configure the equipment to an address in the range 172.16.0.1 to 172.31.255.254 (B type private addresses as described in ISOC RFC 1918) with a 16 bit network address mask, The assigned lP address shall remain fixed during normal operation of the equipment, including powering the equipment down and up.
5.4 Multicast address range
Is.. 8.7.4)
The range 239.192.0.1 to 239.192.0.64 is reserved for current and future use in the
application layer protocols (see 6.2.2).
ONF equipment shall not use multicast addresses in the range 239.192.0.1 to 239.192.0.64,
NOTE ISOC RFC 2365 cf&ines the muItcast address range 239.192.0.0 to 239.192.63.255 as the lPv4
Organization Local Scope. and Is the space from w5.ch an oanlzahon should allocate sub-ranges when defining
scopes for private use. Th. specified range 01 P multicast addresses map to Ethernet UAC resses
OloO5E40000l to 01005E400040 (Kea0ecimall.
6 Transport layer specification
sen 8 8:
6.1 General
This Clause specifies how UDP multicast messages are used to communicate between equipment over an Ethernet network.
Equipment may implement functionality for sending, receiving or both. The provisions In this Clause applies to both, but shall be tested independently as described in Clause 8.
An example of the structure of an Ethernet frame with a IEC 61162-450 sentence is given in Figure 2. The uppermost block shows the full Ethernet frame with the UDP user available data block shown in white. The IP and UDP headers are included in the grey blocks. The lower block shows the UDP user available data block with an IEC 61162•450 formatted sentence included. The numbers above the Ethernet frame gives the size of each block. The numbers in front of the UDP user data block gives the offset from the start of the block (0 — zero).
7 Application layer specification7.1 Datagram header
(see 8.9.2)
7.1.1valid header
AIl UDP multicast datagram shall contain one of the following strings，followed by a nullcharacter(all bits set to zero) as the first six bytes of the datagram:
“UdPbc” for transmission of lEC 61162-1 formatted sentences as described in 7.2;“RaudP” for transmission of binary images as described in 7.3;
.“RrUdP” for transmission of re-transmittable binary images as described in 7.3.
lncoming datagrams with an unknown header should be discarded without processing thecontent beyond the header.
NOTE Future editions of this standard may define other header codes、 Any such header code will be differentfrom the ones already in use and will at least contain six bytes, possibly including a trailing null character.
7.1.2 Error logging
The equipment shall maintain a count of received datagrams that do not have a valid headerand make this available as defined in 4.3.3.
7.2 General lEC 61162-1 sentence transmissions7.2.1Application of this protocol (see 8.9.1)
This protocol provides a mechanism by which lEC 61162-1 sentences can be sent to one ormore receivers on the network. The protocol allows several sentences to be merged into onedatagram.
7.2.2 Types of messages for which this protocol can be used(see 8.9.3)
This protocol shall be used for SBM and MSM (see Annex A) type messages. The protocolshall also be used for CRP message exchanges with provisions specified in Annex C.