OPC UA PubSub over TSN is a communication architecture that combines the decoupled, many-to-many data distribution of the OPC UA PubSub model with the deterministic, time-synchronized network guarantees of Time-Sensitive Networking. This convergence enables a single, converged Ethernet network to carry both best-effort IT traffic and hard real-time operational technology (OT) control data, eliminating the need for separate, proprietary fieldbuses.
Glossary
OPC UA PubSub over TSN

What is OPC UA PubSub over TSN?
A transport profile that combines the publisher-subscriber message pattern of OPC UA with Time-Sensitive Networking to guarantee bounded low latency and jitter for real-time industrial control.
By leveraging TSN's IEEE 802.1 standards for traffic shaping, frame preemption, and precise clock synchronization, this profile ensures that critical control messages are delivered within strict microsecond-level latency bounds. This allows OPC UA to move from supervisory monitoring down to the field-level controller-to-controller communication required for motion control and high-speed automation, unifying the industrial networking stack.
Key Features
OPC UA PubSub over TSN combines a decoupled data exchange model with network-level traffic scheduling to guarantee bounded low latency for real-time industrial control.
Time-Sensitive Networking (TSN) Integration
TSN is a set of IEEE 802.1 standards that provide deterministic, low-latency communication over standard Ethernet. By integrating with TSN, OPC UA PubSub guarantees that critical control messages are delivered within strict time boundaries, preventing jitter and packet loss.
- IEEE 802.1Qbv (Time-Aware Shaper): Schedules traffic into cyclic time windows, separating high-priority real-time frames from best-effort background traffic.
- IEEE 802.1AS (Timing and Synchronization): Establishes a distributed, fault-tolerant clock with sub-microsecond accuracy across all network devices.
- Zero Congestion Loss: Reserved bandwidth ensures that critical automation traffic is never dropped due to buffer overflow.
Publisher-Subscriber Decoupling
Unlike the client-server model, the PubSub pattern allows a single Publisher to send a DataSet to multiple Subscribers simultaneously without establishing individual sessions. This is critical for scalable, one-to-many communication patterns like motion control and emergency stops.
- Multicast Efficiency: A single network message is delivered to all interested nodes, drastically reducing bandwidth compared to repeated unicast transmissions.
- No Session Overhead: Subscribers do not need to maintain a persistent, stateful connection with the Publisher, simplifying failover and redundancy.
- DataSet Messages: Pre-configured groups of variables are encoded and transmitted as a single, cohesive payload, ensuring data consistency.
Bounded Low Latency and Jitter
The core value proposition is the guarantee of bounded latency, often in the microsecond range, and minimal jitter. This is essential for closed-loop control applications like high-speed packaging machines and CNC machining.
- Deterministic Delivery: Network latency is predictable and mathematically calculable, not probabilistic.
- Isochronous Cycles: Communication cycles are synchronized with the application's task cycle, ensuring data arrives exactly when needed for control logic execution.
- Converged Networks: Real-time control traffic, video streams, and standard IT data coexist on a single physical wire without compromising determinism.
Standardized Data Models (Companion Specs)
OPC UA PubSub over TSN leverages existing Companion Specifications to define the semantic meaning of data. This ensures that a drive from Vendor A and a controller from Vendor B can interoperate without custom code.
- OPC UA FX (Field eXchange): Extends PubSub for controller-to-controller communication, standardizing the exchange of process data and configuration at the field level.
- Plug-and-Produce: Devices can be added to the network and immediately understood by the application, as their data structure is pre-defined by an industry-standard Information Model.
- Semantic Interoperability: Moves beyond raw bytes to provide context, such as engineering units, data quality, and alarm states, directly in the payload.
Network Configuration and Stream Reservation
Determinism is achieved through centralized network configuration. A Centralized Network Controller (CNC) calculates transmission schedules and uses Stream Reservation Protocol (SRP) to reserve bandwidth for critical streams before they begin.
- IEEE 802.1Qcc (SRP Enhancements): Provides a management interface for a CNC to configure bridges and talkers/listeners, simplifying the setup of complex deterministic paths.
- Offline Scheduling: Transmission schedules can be pre-calculated and deployed, ensuring that network resources are guaranteed before production starts.
- Fault Tolerance: TSN standards like IEEE 802.1CB (Frame Replication and Elimination) duplicate critical frames over redundant paths, ensuring zero switchover time if a link fails.
Vendor-Agnostic Hardware Abstraction
By combining OPC UA's platform independence with standard Ethernet hardware, this profile eliminates proprietary fieldbus lock-in. Any TSN-compliant switch and network interface card can participate in the deterministic network.
- Standard Ethernet PHY: Uses ubiquitous RJ45 connectors and cabling, reducing infrastructure costs compared to specialized fieldbus wiring.
- Converged IT/OT: Enables seamless integration of operational technology (OT) data with enterprise IT systems for analytics without protocol gateways.
- Scalable Topologies: Supports line, ring, and star topologies, allowing network architects to design for both high availability and cost efficiency.
OPC UA PubSub over TSN vs. Other Transport Profiles
Comparison of deterministic guarantees, latency bounds, and architectural characteristics across OPC UA PubSub transport mappings
| Feature | PubSub over TSN | PubSub over MQTT | PubSub over UDP |
|---|---|---|---|
Deterministic delivery | |||
Bounded latency | |||
Jitter guarantee | < 1 µs | ||
Network infrastructure | TSN-enabled Ethernet switches | Standard MQTT broker | Standard IP network |
Typical use case | Closed-loop motion control | Cloud telemetry and IoT | Local multicast streaming |
Time synchronization protocol | IEEE 802.1AS | ||
Quality of Service levels | Strict priority and scheduled traffic | Configurable QoS 0-2 | Best-effort only |
Bandwidth reservation |
Frequently Asked Questions
Clear, technically precise answers to the most common questions about combining OPC UA Publish-Subscribe with Time-Sensitive Networking for deterministic industrial communication.
OPC UA PubSub over TSN is a transport profile that combines the OPC UA Publish-Subscribe (PubSub) communication model with Time-Sensitive Networking (TSN) to guarantee bounded low latency and jitter for real-time industrial data exchange. In this architecture, a Publisher encodes field-level data into a DataSet and transmits it as a Network Message over a TSN-enabled Ethernet infrastructure. TSN provides the deterministic scheduling via mechanisms like the IEEE 802.1Qbv Time-Aware Shaper, which divides network traffic into cyclic time windows, ensuring that critical PubSub frames bypass non-deterministic queues. This allows controller-to-controller communication with cycle times down to 31.25 microseconds, replacing traditional fieldbus systems while maintaining standard IT convergence on a single physical network.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Understanding OPC UA PubSub over TSN requires familiarity with the underlying communication models, data structuring methods, and related transport profiles that enable deterministic, real-time industrial data exchange.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us