NMEA
Facebook  Tweet  LinkedIn  Instagram YouTube



 
OneNet Standard for IP Networking of Marine Electronic Devices
Estimated publication date: Q4 2019

The OneNet Standard for IP Networking of Marine Electronic Devices is an open industry standard based
on Internet Protocol, Version 6 (IPv6) and the IEEE 802.3 Ethernet Local Area Network. OneNet provides a
common network infrastructure for marine devices and/or services on IPv6. All OneNet application
protocols, such as PGN Messages, are designed to use a standard IPv6 network protocol stack. This allows OneNet
to coexist with other protocols and services that operate parallel on the same network (including other
marine standards such as IEC 61162-450). The standard also specifies mechanisms for connecting OneNet networks, NMEA 2000 networks, and other networks via gateway devices. Like NMEA 2000, all OneNet products will need to be certified by the manufacturer and verified by NMEA.

OneNet Goals

• To specify the transport of NMEA Network Messages over IPv6
• To utilize standard IP network and addressing infrastructure
• To facilitate the safe and secure communication and operations among equipment
• To co-exist with other IP protocols / services on the same cable
• To discover devices and services automatically to create an extendible and scalable network architecture
• To define an open interface to interoperate with current and upcoming open services
• To deliver interoperability with the established industry standards including NMEA 2000 (i.e., establishing gateway rules between NMEA 2000 and OneNet)
• To support high-bandwidth applications such as audio/video data transport

Key Benefits

• Standardized architecture. Transport of NMEA Network Messages as well as other protocols over IPv6-based networks (this aligns with M2M, IoT trends)
• Greater bandwidth. With a range of 100Megabit per second to 10 Gigabit per second transfer speeds directly to OneNet Devices, Ethernet is about 400 to     40,000 times faster than NMEA 2000.
• Much greater number of potential devices (addresses). OneNet allows larger and more complex networks to be created than can be achieved with the 252 address limitation on NMEA 2000.
• Greater power capacity. With Power over Ethernet (PoE), each OneNet Device may be separately powered up to 25.5Watts directly from the Ethernet Switch (refer to IEEE 802.3at).
• Ubiquitous technology. Ethernet is used everywhere in homes, offices and industrial environments and is well understood. Many marine electronic products already implement and support Ethernet.

Organization of the OneNet Standard


The OneNet Standard is organized into the following sections:

1) Introduction – provides context for the OneNet standard, defines the basic scope, explains requirement terminology, and lists all definitions.

2) Device Architecture – introduces the components of a OneNet Device, explains how they are related  to each other, and lists the section where the component is described in detail. Also contains requirements for the network protocol stack that each OneNet Device must use to communicate on a OneNet network.

3) Physical Layer –
includes environmental, radio frequency, power, and physical interface considerations, such as EMI, PoE, auto negotiation, auto-MDIX, and signaling rates.

4) Discovery – identifies OneNet discovery of devices, applications and services on the OneNet Network. Discovery provides clients on a local area network with an extendable way to learn what OneNet Devices are present on a network, what each device is, and what its capabilities and services are. Discovery is built on top of the widely adopted protocols DNS (RFC 6762Multicast DNS) and DNS-SD (RFC6763 DNS-Based Service Discovery).

5) Application Information – describes the OneNet Application Information Service, which provides information about a OneNet Application including product name, NMEA product code, model, NMEA manufacturer code, manufacturer name, serial number, and other metadata.

6) Datagram Protocol –
is built on top of IP’s User Datagram Protocol (UDP), but defines the extension header mechanisms needed to support security and the PGN transport.

7) PGN Transport –
specifies the minimum requirements for implementing NMEA Parameter Group Messages identified by their Parameter Group Number (PGN). These requirements include the IPv6 PGN extension header, utilizing discovery services with the NMEA NAME, application of the ISO Address Claim PGN (NMEA NAME), and minimum required PGNs.

8) Application Security – describes the security model used in OneNet and the protocols needed for OneNet Applications to operate within that model. Security is provided through the secrecy of a Master NMEA OneNet® Standard for IP Networking of Marine Electronic Devices Key, which is distributed by pairing Applications to the Secure Network where it is used to authenticate and encrypt network communications.

9) Datagram Security –
describes how the Datagram Services of a paired Application safeguard the datagrams they send using authenticated encryption. The Master Key is used to establish secure relationships between Datagram Services, known as Security Associations. All datagrams are encrypted and transmitted within the context of a Security Association.

10) Gateway – describes devices that interconnect a OneNet Network to other networks and devices. Specifies which OneNet sections the Gateway must adhere to, as well and the requirements specific to their respective operation. Gateways connected to OneNet convert data bi-directionally to and from the OneNet protocol format with other protocols, such as NMEA 2000.

11) Certification Verification –
describes how a Public-Key Infrastructure is used to verify the certification status of OneNet Applications. It contains requirements for storing and distributing a digital certificate issued as part of the certification process, as well as requirements for retrieving certificates from other Devices or Applications and reporting on their certification status. Future versions of this standard may resolve outstanding issues or integrate other technologies. Additional sections will be created and published to meet technology innovations and continual changing needs of the market. Topics may include:

 • Test method documentation and required results for certifying OneNet Devices
 • Functionality to deliver data to remote devices (WAN connectivity)
 • OneNet switches, including power and protocol
 • OneNet Application configuration through web pages
 • Redundant implementation of OneNet networks
 • Wireless connectivity

The OneNet standard utilizes the PGN Messages documented in the NMEA Network Message Database. It is not the intention of the OneNet Standard Committee that the reader possess either a full copy or any prior knowledge of the NMEA 2000 standard. To that end, certain aspects of NMEA 2000 operation are described in the OneNet documents.
 
 National Marine Electronics Association
692 Ritchie Highway, Suite 104, Severna Park, MD USA 21146  
410-975-9425
info@nmea.org  
 
 Copyright© 2019 NMEA. All Rights Reserved.
 
Website Created and maintained by NSNA - A Bellingham WA Web Design Company