OPC UA Pub/Sub

Unlike the classic client-server model requiring direct, persistent connections, Pub/Sub decouples data producers (Publishers) from data consumers (Subscribers). Publishers send data to a logical topic without knowing the recipients. Subscribers express interest in a topic and receive data asynchronously. This loose coupling allows systems to scale independently, adding or removing sensors and applications without reconfiguring the entire network. It eliminates the point-to-point spaghetti architecture that plagues traditional SCADA integrations.

OPC UA Pub/Sub is transport-agnostic, allowing architects to choose the best protocol for their infrastructure without changing the application logic. Two primary transports are defined:

• UADP (UA Datagram Protocol): A lightweight, binary protocol optimized for Layer 2 multicast on time-sensitive networks (TSN). Ideal for high-speed, controller-to-controller communication on the factory floor.
• MQTT (Message Queuing Telemetry Transport): A TCP-based protocol designed for cloud connectivity and constrained networks. It uses a central broker for store-and-forward messaging, enabling secure data egress to AWS IoT Core or Azure IoT Hub. This flexibility bridges the gap between deterministic shop-floor control and enterprise analytics.

Security is not an afterthought; it is built directly into the Pub/Sub specification, mirroring the robust security of client-server OPC UA. The framework provides message-level security for confidentiality and integrity, independent of the transport layer. Key features include:

• Signing & Encryption: Messages can be digitally signed to prevent tampering and encrypted to prevent eavesdropping, using industry-standard algorithms.
• Key Management: A dedicated Security Key Service (SKS) distributes symmetric keys to authorized Publishers and Subscribers, ensuring only trusted nodes participate in the data exchange. This allows secure multicast even on shared Ethernet networks.

To enable true plug-and-produce interoperability, Pub/Sub uses DataSetMetaData. Before sending raw data, a Publisher transmits a structured description of the data payload, including field names, data types, and engineering units. Subscribers use this metadata to dynamically interpret incoming messages without needing a pre-configured, static schema. This self-describing mechanism is critical for semantic interoperability, allowing a robot from Vendor A to understand a sensor from Vendor B without manual mapping, drastically reducing commissioning time.

For applications requiring minimal latency and maximum throughput, such as motion control, Pub/Sub specifies highly efficient binary encodings. UADP uses a compact binary format that avoids the overhead of XML or JSON. It supports raw encoding, where the payload is a direct binary dump of the system's memory structure, eliminating serialization overhead entirely. Combined with TSN, this enables deterministic delivery guarantees in the sub-millisecond range, making it suitable for hard real-time control loops that were previously the domain of proprietary fieldbuses.

A defining feature for industrial automation is the ability to operate without a broker. Using UADP over UDP multicast, Publishers can send a single message that is simultaneously received by all interested Subscribers on the network segment. When combined with Time-Sensitive Networking (TSN), this becomes a deterministic, lossless communication channel. TSN guarantees bounded low latency and zero congestion loss, enabling the replacement of legacy hard-wired signal lines with a converged Ethernet network that carries both real-time control data and best-effort traffic.