A Modular Event-Driven Software Architecture for Open-Source Industrial IoT Edge Gateways

arXiv:2610.10544 · cs.AR, cs.DC, cs.SY, eess.SY · Submitted 2026-07-09 · Read on arXiv

Listen

Radio episode about this paper

Transcript

Introduction to the show: ident: Robotics Radio. Generated commentary on the latest robotics and control papers.

Rosa: Today's paper: "A Modular Event-Driven Software Architecture for Open-Source Industrial IoT Edge Gateways".

Dev: The gist: This paper presents a modular event-driven software architecture designed for open-source IIoT edge gateways that abstracts serial protocol management and network configuration into a responsive web interface.

Rosa: First, who's behind it and why it matters.

Paper summary: Rosa: So to recap, this paper presents a modular event-driven software architecture specifically built for open-source IIoT edge gateways. The core idea is to solve the challenge where industrial machines use rigid, proprietary edge controllers that require tons of manual configuration just to get them talking to the cloud.

Dev: They propose building a containerized web stack that acts as a translator, abstracting away the complexity of translating Modbus data into MQTT messages for platforms like AWS IoT. They focus on creating a standardized way to bridge those local serial protocols with global cloud environments.

Taro: The architecture is structured in three layers: Hardware Interface, Application Middleware, and Cloud Orchestration Layer, which clearly shows how they’re trying to keep the physical world separate from the data processing logic.

Rosa: They claim that this approach accelerates initial deployment by providing a unified configuration webpage where you can assign I/O roles and define MQTT topics without needing to manually write complex scripts for every device.

Dev: The protocol translation workflow is deterministic; during the uplink, the Node.js engine reads Modbus RTU packets from an RS-four hundred eighty-five bus, decodes them using user-defined function codes, and publishes them as structured JSON payloads over MQTT <ref:2610.10544#pg1>.

Taro: During the downlink cycle, the system also listens to command topics on MQTT and translates those cloud execution commands back into Modbus write commands to control the physical actuator.

Rosa: They also built a localized event engine that handles conditional logic right at the edge, which is a key part of their claim about reducing network latency by avoiding sending raw data all the way up for simple threshold evaluations.

Dev: That event engine formalizes decision-making as a finite state evaluation process, where it checks sensor states against user-defined upper and lower thresholds to trigger digital outputs instantly via GPIO pins on the CM4.

Taro: So, what this means for autonomy is that even if the cloud connection hiccups, critical safety or operational thresholds are still met deterministically right there on the gateway.

Rosa: The system is preliminarily deployed and validated on a Raspberry Pi Compute Module four CM4 to check its robustness, scalability, and user-friendliness in an industrial context.

Dev: The experimental results demonstrated a substantial reduction in system integration time and high operational stability during the testing phase, setting up what they call a robust software foundation for real-time edge-based industrial automation.

Conclusion: Rosa: Looking at this paper, "A Modular Event-Driven Software Architecture for Open-Source Industrial IoT Edge Gateways," the authors are essentially showing how you can simplify the deployment of these complex systems by moving away from manual command line configurations.

Dev: They’re arguing that this modular event-driven design effectively abstracts away the hard parts—the serial protocol management and network configuration—into a responsive web interface, which is a big win for usability.

Taro: The implication is that this framework bridges the gap between legacy industrial equipment and modern cloud infrastructure by providing a standardized way to deploy edge gateways that can actually function in those mixed environments.

Rosa: It’s about making integration less of a custom engineering task and more of a manageable deployment task, which helps extend the lifespan of existing machinery.

Dev: The paper establishes this as a reliable software foundation for real-time edge-based industrial automation by focusing on deterministic response times at the edge.

Taro: For someone listening, what this means is that you can take older equipment and get it integrated into modern systems without needing an expert team just to write custom drivers for every piece of hardware.

Pei Yu Wong, Thien Tran, Hudyjaya Siswoyo Jo, Jonathan Kua

Swinburne University of Technology Sarawak Campus

cs.AR, cs.DC, cs.SY, eess.SY

Submitted: 2026-07-09

Updated: 2026-07-09

Comments: 4 pages, 3 figures, 1 table, 1 function, accepted paper on the 24th IEEE International Conference on Industrial Informatics (INDIN), 26-29 July, 2026, Melbourne, Australia

Code: https://github.com/peiyu16/Gateway

License: http://creativecommons.org/licenses/by/4.0/

Importance score: 68/100

The gist: The gist: This paper presents a modular event-driven software architecture designed for open-source IIoT edge gateways that abstracts serial protocol management and network configuration into a

Key concepts

Event-Driven Architecture
This design uses an event-driven approach where the system reacts to specific occurrences (events) rather than following a rigid sequence of commands. This makes it highly responsive and efficient for real-time industrial tasks, as the software triggers actions immediately when a condition is met, such as a sensor reading crossing a threshold.
Protocol Translation Engine
This component acts as a translator between old industrial communication methods and modern internet protocols. It converts data read from physical devices using Modbus RTU over RS-485 into standardized JSON payloads that can be sent to the cloud via MQTT, and vice versa for receiving commands.
Localized Event Engine
This engine performs critical decision-making directly on the edge hardware. Instead of sending all raw data to the cloud for processing, this engine checks sensor values against predefined limits locally. If a threshold is breached, it instantly triggers an output device, guaranteeing immediate safety or operational responses regardless of cloud connectivity.
Containerized Web Stack
The software uses a containerized web stack built with Node.js and React.js to create a unified interface. This allows technicians to configure the entire data pipeline—from setting up Modbus registers to defining cloud connections—through an easy-to-use graphical web interface instead of complex command-line coding.

Summary

The gist: This paper presents a modular event-driven software architecture designed for open-source IIoT edge gateways that abstracts serial protocol management and network configuration into a responsive web interface.

Proposed System Architecture

The proposed system architecture separates the system into three distinct layers: (i) Edge Hardware Interface, (ii) Application Middleware, and (iii) Cloud Orchestration Layer The high-level operational architecture of the proposed IIoT edge gateway is illustrated in Figure 1 Industrial field devices connect to the gateway via established fieldbus protocols, while the aggregated and processed data is transmitted to the cloud using MQTT

Hardware Infrastructure

The primary edge node utilized in this investigation is the IRIV PiControl system This industrial-grade controller integrates a Raspberry Pi Compute Module 4 (CM4) It features isolated RS-485 interfaces, which mitigate the risk of electrical noise disrupting serial communications in harsh factory environments The hardware includes dual Gigabit Ethernet ports and expandable NVMe storage, providing the necessary bandwidth and memory for localized data buffering

Application Middleware and Technology Stack

The Application Middleware resides entirely on the CM4 and handles all computational logic, protocol translation, and state management The backend orchestrator was developed using Node.js and the Express.js framework Node.js utilizes an asynchronous, event-driven runtime environment, making it highly suitable for handling concurrent I/O operations without thread blocking MongoDB was implemented as the localized database engine This document stores network parameters, mapped Modbus registers, and user-defined automation rules The frontend interface was built utilizing React.js This component-based JavaScript framework allows technicians to interact dynamically with the backend API

Protocol Translation Workflow

The software operates as a deterministic and bidirectional translation engine During the uplink cycle, the Node.js polling engine iterates through the MongoDB collection of registered field devices It dispatches read requests over the RS-485 bus utilizing the Modbus RTU protocol Upon receiving the hexadecimal serial payload, the backend decodes the data based on user-defined function codes, such as Read Holding Registers The system wraps the decoded values into a structured JSON payload and publishes it to the designated MQTT broker under specific Quality of Service (QoS) parameters During the downlink cycle, the Node.js client subscribes to command topics on the MQTT broker When a cloud application issues an execution command, the middleware parses the JSON structure and translates it into the corresponding Modbus write command It then transmits this command to the physical actuator

Automated Linkage Event Engine

A localized linkage event engine is engineered to facilitate rapid, autonomous decision-making at the edge Sending raw sensor data to the cloud for simple threshold evaluation introduces unnecessary latency and consumes bandwidth The system formalizes this event engine as a finite state evaluation process Let St represent the continuous state of an analog sensor at time t Let τupper and τlower represent the user-defined upper and lower execution thresholds The system determines the discrete actuation state A(St) of a coupled digital output device using the following piecewise function A(St) =





1 if St ≥ τupper

0 if St ≤ τlower

Aprev otherwise The Node.js backend evaluates this logic locally during every polling cycle When St breaches a threshold, the system triggers the corresponding digital output via the CM4 GPIO pins instantaneously, ensuring critical safety or operational thresholds are met regardless of cloud latency

Performance and Usability Evaluation

The software architecture demonstrated exceptional stability during the validation phase The backend maintained a continuous polling cycle across the Modbus network while simultaneously publishing the JSON payloads to AWS IoT without packet loss The asynchronous Node.js backend maintained a minimal resource footprint During continuous bidirectional communication, the CPU load on the ARM Cortex-A72 processor remained low, leaving substantial computational headroom for future integration The primary pilot achievement is the reduction in deployment overhead Traditional command-line configuration of network interfaces, database schemas, and MQTT daemons on a Linux SBC typically requires several hours of expert engineering time Utilizing our unified RESTful API and graphical interface, technicians can configure the entire data pipeline directly in the web GUI

Conclusions and Future Work

In this paper, a highly adaptable event-driven software architecture is presented that simplifies the deployment of open-source IIoT edge gateways towards new network-centric paradigms such as Cloud-Fog Automation This framework addresses the complexities of manual coding by abstracting serial protocol management and network configuration into a responsive web interface The system effectively bridges the gap between legacy industrial equipment and modern cloud infrastructure The integration of localized threshold evaluation further ensures deterministic response times for critical operations, thus reducing reliance on cloud processing Despite demonstrating reliable performance in device management and automated event controls, the current system scope has several limitations The hardware dependency on RS-485 for physical connectivity restricts network scalability in remote or highly distributed deployments Additionally, the software currently translates exclusively between Modbus and MQTT, limiting interoperability with other prevalent industrial communication standards Future work will address these limitations by expanding both the hardware connectivity and the software’s computational capabilities The authors plan to integrate configuration support for extended wireless modules such as LoRa and 4G/5G to leverage the full connectivity suite of the edge controller They will also implement security mechanisms for the edge-based containerized framework and focus on horizontal scalability by incorporating agentic automation protocols in the era of Large AI models This advancement will enable dynamic task placement and collaborative decision-making across a distributed swarm of networked edge gateways The paper establishes a robust software foundation for real-time edge-based industrial automation by enabling seamless integration with modern industrial infrastructure

How it works

The system is structured into three distinct layers: (i) Edge Hardware Interface, (ii) Application Middleware, and (iii) Cloud Orchestration Layer The hardware infrastructure utilizes the IRIV PiControl system as the primary edge node This controller integrates a Raspberry Pi Compute Module 4 (CM4) It features isolated RS-485 interfaces, mitigating the risk of electrical noise disrupting serial communications in harsh factory environments

Protocol Translation and Event Processing

The protocol translation workflow is deterministic and bidirectional During the uplink cycle, a Node.

Improvements for AI systems

  1. The system can reduce system integration time by allowing technicians to configure the entire data pipeline, from bare-metal hardware connection to active cloud telemetry, directly in the web GUI as shown in Fig 3. This capability eliminates the traditional command-line configuration of network interfaces, database schemas, and MQTT daemons on a Linux SBC typically requires several hours of expert engineering time.

  2. The localized event engine can enable rapid, autonomous decision-making at the edge by implementing a piecewise function: A(St) = 1 if St ≥ τupper / 0 if St ≤ τlower / Aprev otherwise, triggering actuation instantly based on local sensor states rather than waiting for cloud processing.

  3. The architecture can achieve high operational stability by storing all configuration state locally in MongoDB, which ensures the edge gateway maintains autonomous operation even during severe network partitions, an industrial requirement for reliability.

Abstract

Integrating legacy industrial machinery into modern cloud infrastructures poses a significant software engineering challenge. Industrial Internet of Things (IIoT) deployments frequently rely on rigid and proprietary edge controllers that require extensive manual configuration. Open-source single-board computers (SBCs) offer a highly adaptable hardware alternative, but they still lack standardized software deployment frameworks capable of bridging localized serial protocols with global cloud environments. In this paper, we present a modular event-driven software architecture designed specifically for open-source IIoT edge gateways. We built a containerized web stack to provide a unified architecture that abstracts the complexities of Modbus-to-MQTT protocol translation, enabling rapid configuration of telemetry streams to cloud platforms such as Amazon Web Services (AWS) IoT. Furthermore, we designed a localized event engine that processes conditional logic directly at the edge layer, which significantly reducing network latency. The proposed architecture is preliminarily deployed and validated on an industrial-grade Raspberry Pi Compute Module 4 (CM4) to investigate its robustness, scalability and user-friendliness. Experimental results demonstrate a substantial reduction in system integration time and high operational stability, thus establishing a robust software foundation for real-time edge-based industrial automation. This paper contributes to extending the lifespan of legacy machinery by enabling seamless integration with modern industrial infrastructure.

Related papers