Page History

...

• Namespace
  • This always begins with “spBv1.0” to indicate that the topic is using the Sparkplug B version 1.0 specification. This serves as an identifier for the protocol version being used, as well as the encoding used for the associated payload data

• Group ID

  • This identifies a logical grouping of Edge nodes and devices. For example, you might use a group ID to represent a particular factory or plant location. It ensures data segregation between different groups, aiding in efficient data management and security.

• Message Type

  • The message_type component of the topic namespace signals how the MQTT payload should be processed. The following message_type components are defined for the Sparkplug topic namespace:

    NBIRTHSparkplug message types and how they differ: Edge node BIRTH certificate. This is a startup message from an Edge node to announce its presence and share its configurations.

    NDEATHSparkplug message types and how they differ: Notification of an edge node’s disconnection or failure.

    DBIRTHSparkplug message types and how they differ: Device BIRTH certificate. This is a startup message from a device to announce its presence and share its configurations.

    DDEATHSparkplug message types and how they differ: Notification of a device’s disconnection or failure.

    NDATASparkplug message types and how they differ: Data messages from an edge node which include edge node metric data.

    DDATASparkplug message types and how they differ: Data messages from a device which include device metrics.

    NCMDSparkplug message types and how they differ: Command to an edge node.

    DCMDSparkplug message types and how they differ: Command to a device.

    STATESparkplug message types and how they differ: It represents the state of the primary host application. Edge nodes subscribe to it to get the online status of the host.

• Edge Node ID
  • This uniquely identifies a specific edge node within in a group. Edge nodes are responsible for reporting data on behalf of devices they control or are connected to. The Edge Node ID helps in directing commands to the correct node and segregating data from various nodes.
• Device ID (Optional)
  • If the message relates to a specific device controlled by the edge node, the device ID uniquely identifies that device.

...

...

...

...

...