OPC UA Pub/Sub

Enables direct, one-to-many data distribution at the network edge without a message broker intermediary. This eliminates the single point of failure and latency introduced by broker-based architectures.

• Transport Mapping: Uses UDP/IP multicast to send a single datagram to multiple subscribing nodes simultaneously.
• Deterministic Latency: Ideal for closed-loop control where sub-millisecond jitter is non-negotiable.
• Network Efficiency: Dramatically reduces bandwidth consumption compared to multiple client-server connections.
• Discovery: Receivers use standard network discovery mechanisms to locate multicast streams without prior configuration.

Provides a secure, stateful transport option for wide-area network communication and cloud ingestion. This mapping bridges the gap between the factory floor and enterprise IT systems.

• Full MQTT 5.0 Support: Leverages features like session expiry, shared subscriptions, and user properties for robust telemetry.
• JSON and UADP Encoding: Supports both verbose, human-readable JSON and the highly efficient, binary UADP format over MQTT topics.
• Stateful Awareness: Unlike pure UDP, MQTT's quality of service levels guarantee delivery for critical alarm and event data.
• Firewall Friendly: Uses standard outbound TCP connections, simplifying secure IT/OT convergence without complex firewall rules.

A highly optimized, binary message encoding designed for minimal wire footprint and maximum processing speed. UADP is the key to achieving true real-time performance on resource-constrained edge hardware.

• Zero-Copy Processing: Network messages can be parsed directly from the wire buffer without memory duplication.
• Field-Level Security: Individual data fields within a single message can be encrypted and signed independently.
• Compact Payload: Reduces message size by up to 80% compared to JSON, conserving bandwidth on high-speed machine networks.
• Schema On-The-Wire: The message structure is self-describing, allowing decoders to parse data without external schema lookups.

OPC UA Pub/Sub is the application-layer protocol designed to exploit IEEE 802.1 TSN standards. This convergence guarantees bounded low latency over standard Ethernet for safety-critical motion control.

• IEEE 802.1Qbv: Uses scheduled traffic shapers to ensure Pub/Sub frames are transmitted in deterministic time windows.
• Frame Preemption: Allows a high-priority Pub/Sub control frame to interrupt a lower-priority bulk data frame mid-transmission.
• Stream Reservation: Network bandwidth is reserved end-to-end for specific Pub/Sub data streams, preventing packet loss under congestion.
• Converged Network: Enables a single physical Ethernet cable to carry both real-time control traffic and best-effort IT data.

Implements a decentralized security model that scales to massive sensor networks without a central key broker. Security is embedded directly into the message, not just the transport session.

• Group Key Distribution: A security key server distributes symmetric keys to authorized publishers and subscribers out-of-band.
• Message-Level Signing: Each UADP message carries a cryptographic signature, allowing subscribers to verify data integrity and origin.
• Field-Level Encryption: Sensitive data fields within a message can be selectively encrypted, allowing non-sensitive metadata to remain visible for routing.
• Rotation Policies: Keys are automatically rotated based on time or message count, limiting the exposure window of any single compromised key.

Allows subscribers to dynamically discover the structure, encoding, and semantics of published data without prior configuration. This enables plug-and-produce interoperability in flexible manufacturing lines.

• Self-Describing Payloads: Publishers periodically broadcast metadata describing the exact field names, data types, and engineering units of their DataSets.
• Dynamic Binding: A subscriber can automatically configure its internal data model to match a newly discovered publisher without manual engineering.
• Version Management: Metadata includes version identifiers, allowing subscribers to gracefully handle schema evolution and backward compatibility.
• Semantic Context: Metadata can reference external information models, linking raw sensor values to their meaning in a manufacturing ontology.

A set of IEEE 802.1 Ethernet standards that guarantee bounded low-latency and jitter for time-critical industrial traffic over standard network infrastructure. TSN provides the deterministic transport layer that allows OPC UA Pub/Sub UDP payloads to coexist with best-effort traffic on converged networks without frame collision or unpredictable delays.

• IEEE 802.1Qbv: Scheduled traffic gating for cyclic data
• IEEE 802.1AS: Precise time synchronization across all network nodes
• Enables microsecond-level determinism for closed-loop control

A lightweight middleware component deployed on the factory floor that routes and buffers telemetry data between sensors, controllers, and cloud gateways. When OPC UA Pub/Sub uses the MQTT transport profile, an edge broker like Mosquitto or NanoMQ acts as the central routing hub, decoupling publishers from subscribers.

• Store-and-forward: Buffers messages during network interruptions
• Topic bridging: Translates between OPC UA Pub/Sub topics and cloud IoT hubs
• Essential for hybrid edge-to-cloud architectures

The ingestion, contextualization, and governance layer that consumes the high-velocity data streams published by OPC UA Pub/Sub. These pipelines transform raw UADP NetworkMessages into structured, queryable assets for analytics, digital twins, and AI model training.

• Schema registry: Maps Pub/Sub DataSet IDs to semantic types
• Stream processing: Real-time filtering and feature engineering on edge nodes
• Ensures data quality before storage in lakehouse architectures

A guaranteed maximum time window within which a computation or data transfer will complete. OPC UA Pub/Sub over TSN delivers deterministic latency for Publisher-to-Subscriber delivery, a non-negotiable requirement for closed-loop control systems where stale data is worse than no data.

• Worst-case execution time (WCET): Bounded, not average
• Jitter: Variation in latency must be minimized
• Critical for motion control and safety interlocks