Wireless IoT Protocols: Breaking Down the Network Stack
We were recently asked, “what is the difference between the MIOTY protocol in MYTHINGS and OPC UA?”. This question made us realize the existing plethora of wireless protocols in industrial IoT (IIoT) and how confusing it can be to distinguish one from the other.
To help orient yourself within the jungle of networking technologies, this week we provide a bird’s eye view of the IoT protocol stack and various Information Technologies (IT) and Operational Technologies (OT) in industrial networks.
The Courier Analogy
In an IoT application, multiple tasks need to be performed to deliver a message from an end device to the cloud. That’s why we need, not a single, but a stack of IoT protocols, each of which is responsible for a set of tasks. To better explain this, let’s look at the following analogy.
Let’s say I want to send a package between two cities in Germany using a courier. The package must first be labeled with the sender’s and receiver’s addresses. Based on these addresses, the courier then decides the best route and means of transportation for the shipment. Sometimes, the package needs to pass through several facilities for routing. For a seamless process, deliveries must be done in the right order, packages must remain intact and errors like false addresses must be reported in a timely fashion. At the end, the package is received, unpacked and the receiver is happy with the content inside.
The process of sending a message is quite similar. There are various tasks involved including transporting, addressing, routing, error reporting, integrity and reliability management. And just like different groups of postal workers are in charge of specific shipping activities, different IoT protocols are responsible for handling a specific set of networking tasks.
The IoT Protocol Stack
The Open Systems Interconnection (OSI) and Transmission Control Protocol/Internet Protocol (TCP/IP) networking models are the most common frameworks to encapsulate networking tasks in the form of multiple layers. Widely adopted IoT protocols can be mapped to these two models as outlined in the below table. For an IoT network to function effectively, protocols at different layers must be interoperable with each other.
IT and OT protocols in Industrial IoT
In industrial IoT, the protocol landscape can be confusing with a vast assortment of available OT and IT. While OT protocols have been the backbone of industrial controls and automation, IT protocols have been newly integrated to enable cloud-based connectivity and IIoT applications.
Note that IT and OT protocols do not always work with each other and the IoT protocol stack may not always be applied to the OT architecture. Typically, network and transport layers are often skipped either because older OT ethernet protocols do not support TCP/IP suite or because time-sensitive, millisecond low-latency data exchange is strictly required.
Furthermore, in IT systems, application layer protocols like MQTT and AMQP are used for message queuing and data transmission to the cloud. In OT systems, application layer protocols such as OPC UA or CIP are used to transfer data from field devices like PLCs to high-level plant control applications like SCADA or MES.
To close the OT/IT gap and enable data exchange from automation systems to the Internet, major industry efforts have been made to promote interoperability between IT and OT protocols. For example, today OPC UA can be paired with MQTT or AMQP to enable data exchange from OPC-UA servers / field devices to the cloud, either directly or via an IoT gateway. Likewise, many modern Industrial Ethernet protocols are now compatible with higher-layer IT protocols. For example, today OPC UA can be paired with MQTT or AMQP to enable data exchange from OPC-UA servers / field devices to the cloud, either directly or via an IoT gateway. Likewise, many modern Industrial Ethernet protocols are now compatible with higher-layer IT protocols.
So, what is the difference between the MIOTY and OPC UA protocols? MIOTY and OPC UA are intended for totally different purposes in IIoT networking. MIOTY belongs to wireless IoT protocols for network access and physical layer, enabling last-mile sensor communication in non-time sensitive IIoT applications. On the other hand, OPC UA is an application layer OT protocol used for tying PLC data to industrial automation solutions like SCADA and MES systems.
In reality, the architecture of wireless IoT protocols is much more complicated than what the OSI or TCP/IP can capture. In bridging the IT/OT gap, there can be a combination of several physical layer and application layer protocols in a single network. Gateways and bridges, latency, bandwidth, range, power usage, and security are pivotal factors to consider in selecting the right set of interoperable protocols for your IIoT network.
Subscribe to our Monthly Blog Roundup
Get Best-in-Class IoT Wireless Protocol for Industrial Applications
Contact a MYTHINGS™ Platform Expert for more information or to book a demo.