Page History

...

By combining these features, Sparkplug transforms MQTT from a flexible data transport protocol into a robust, self-describing communication standard for IIoT. It eliminates the need for custom parsing logic, reduces integration headaches, and enables true plug-and-play scalability across industrial networks.

Key Differences

The design of Sparkplug revolves around three key system components: the Edge Node, the Host Application, and the MQTT Broker. Each plays a distinct role in managing data flow and maintaining system state.

Edge Node

An Edge Node is any device or system that collects data from sensors, machines, or other field devices. It acts as the primary data source in a Sparkplug environment.

Edge Nodes publish data to the MQTT Broker using Sparkplug’s defined topic structure and payload format. Crucially, they are also responsible for sending birth certificates when they come online and death certificates if they unexpectedly disconnect. These messages keep the system aware of device status — a critical feature for ensuring data integrity.

This is the MQTT Transmission module

Host Application

The Host Application is the system that consumes data from Edge Nodes. Typically, this is an industrial control system, IoT platform, or data analytics tool.

The Host Application subscribes to Sparkplug-compliant topics, ensuring it receives data in a structured format. Additionally, Host Applications monitor device status messages (birth and death certificates) to maintain awareness of which devices are active or offline. This helps streamline alarm management, data visualization, and system diagnostics.

This is the MQTT Engine module

MQTT Broker

The MQTT Broker serves as the central hub for all data exchanges. Acting as a message router, it handles incoming data from Edge Nodes and distributes it to Host Applications based on Sparkplug’s standardized topic structure.

Unlike traditional MQTT brokers that only relay messages, a Sparkplug-enabled broker plays a vital role in maintaining system state. It stores session details for connected devices and ensures that death certificates are published when connections are lost, providing essential visibility within the Sparkplug system.

This is the MQTT Distributor module or Chariot® MQTT Server

How MQTT Sparkplug Works

By introducing standardized messaging rules, Sparkplug ensures that data is not only delivered efficiently but also consistently understood across devices and applications.At  At the core of this system are Sparkplug’s defined message types, topic structure, and state management mechanisms.

MQTT Topic Namespace and Hierarchy

Sparkplug enforces a strict topic structure that organizes data consistently across devices and systems. Each topic follows a predefined format:

Sparkplug's topic format: spBv1.0/<Group ID>/<Message Type>/<Edge Node ID>
spBv1.0 – Identifies the Sparkplug protocol version.
Group ID – Represents a logical grouping of devices (e.g., production line, factory floor).
Message Type – Defines the message purpose (e.g., NBIRTH, NDATA, NDEATH).
Edge Node ID – Identifies the originating device.
This structure simplifies data organization, ensuring that all systems can identify device sources and message types without custom logic.

Payload Format

Sparkplug uses Google’s Protocol Buffers (Protobuf) to encode data efficiently. Protobuf structures data in a compact binary format that reduces bandwidth usage while maintaining flexibility for complex data models.

...

Metrics – The actual data points being transmitted.
Timestamps – For precise data tracking.
Metadata – Additional details about the device or data source.
This structured payload eliminates the ambiguity seen in traditional MQTT deployments, where payloads can vary significantly between devices.

Birth and Death Certificates

To maintain system awareness, Sparkplug introduces birth and death certificates.

Birth Certificate (NBIRTH): Sent by an Edge Node when it comes online. This message announces the node’s presence, publishes its available metrics, and signals to the system that the device is active.
Death Certificate (NDEATH): Sent by the MQTT Broker if an Edge Node unexpectedly disconnects. This ensures the system is immediately aware when a device goes offline.

Real-Time State Awareness

Sparkplug’s state management goes beyond simple message delivery. By requiring devices to maintain active connections with the broker, Sparkplug ensures that system state is always known. When devices disconnect, the broker automatically alerts Host Applications by publishing a death certificate — preventing stale or inaccurate data from being mistaken as live.

Unified Namespace for Simplified Data Management

Sparkplug’s structured topics and payloads enable a unified namespace, where all devices adhere to the same data model. This simplifies the integration of new devices, reduces configuration overhead, and ensures data is always delivered in a predictable format — critical for scaling IIoT ecosystems.

...