How TSN Brings Deterministic Timing to Industrial Ethernet

July 31, 2026

Abhishek Jadhav

Time-Sensitive Networking enables predictable, low-latency communication across converged industrial Ethernet networks

Source: thien/stock.adobe.com; generated with AI

By Abhishek Jadhav for Mouser Electronics

Published July 29, 2026

Modern industrial automation is a hyper-connected environment in which synchronized multi-axis motion control and collaborative robotics must operate within a shared networked architecture where timing is as critical as throughput. For example, in coordinated multi-robot welding, even a few milliseconds’ delay in a control signal to one robot can disrupt synchronization, trigger a fault condition, or reduce process accuracy.

In high-stakes manufacturing and motion control applications, time synchronization among robots, sensors, controllers, and actuators is vital. Any unpredictable delay can lead to misalignment and production errors. Deterministic communication in such systems ensures that every component operates within a predictable window and executes its programmed tasks with the required accuracy.

Ethernet has become the common networking platform for industrial automation, but traditional Ethernet was never designed to provide bounded delivery times for critical data. As factories increasingly combine motion control, robotics, sensors, machine vision, and information technology (IT) systems on shared infrastructure, predictable communication timing has become essential. Time-Sensitive Networking (TSN) addresses this challenge by adding deterministic capabilities to standard Ethernet.

In this first blog of our series on industrial Ethernet, we explore how TSN uses time synchronization, traffic scheduling, frame preemption, and reliability mechanisms to deliver the bounded latency and low jitter required by modern industrial applications.

What Is Time-Sensitive Networking?

TSN is a suite of IEEE 802.1 standards that extends traditional Ethernet with tools for deterministic performance.^[1]TSN aims to provide bounded latency, low packet delay variation (i.e., jitter), and improved reliability for selected traffic by reserving resources for critical traffic and applying advanced queuing and shaping techniques.

TSN allows the same network to carry real-time motion control traffic, video streams, and standard IT traffic simultaneously, provided the network is engineered so that each traffic class receives the required Quality of Service (QoS). TSN operates at Layer 2 (Data Link Layer) of the Open Systems Interconnection (OSI) model, which makes it the foundation on which higher-layer protocols can build.

TSN Standards: Time, Scheduling, Preemption, and Reliability

The fundamental requirement for deterministic operation within TSN is a shared understanding of time among all network participants. Without a common time base, the network switches cannot coordinate transmission windows and end stations cannot align time-sensitive communication. The task of establishing and maintaining this network-wide time synchronization is specified in the IEEE 802.1AS standard, also known as the generalized Precision Time Protocol (gPTP).

IEEE 802.1AS provides Layer 2 timing and synchronization and can support sub-microsecond clock alignment in properly designed TSN networks.^[2] In a TSN time-aware domain, network bridges and end stations synchronize their local clocks to a shared Grandmaster (GM) clock. The protocol operates via logical syntonization, in which the ratio between the local clock and the GM clock is calculated to offset for frequency drift.

After IEEE 802.1AS synchronizes the clocks of all participating devices to create a common network-wide clock, TSN can implement traffic scheduling. Among the TSN traffic scheduling mechanisms, the most critical for hard real-time industrial control is the IEEE 802.1Qbv Time-Aware Shaper (TAS).^[3] The TAS applies a Time-Division Multiple Access (TDMA) concept to Ethernet switches by dividing transmission time into repeated scheduled cycles. Each egress port on a TSN switch is equipped with transmission gates for each of its priority queues. A Gate Control List (GCL) defines a schedule of when these gates are open or closed.

For example, a 1ms cycle can be divided into separate time windows. In the first window, only the gate for high-priority scheduled traffic is open, allowing time-critical motion control packets to be transmitted. In the second window, the gates for best-effort traffic open, allowing regular IT or diagnostic data to pass. This protected time window prevents motion control packets from being delayed by lower-priority traffic.

While the TAS protects scheduled traffic from other data streams, problems can still occur. A low-priority Ethernet frame might begin transmission just before a high-priority critical frame arrives at the egress queue. Even if the TAS gate for the critical frame is open, it must wait for the large frame’s transmission to be completed, introducing significant blocking delay. For a 1Gbps link, transmitting a full-size frame takes over 12μs, a delay that may be unacceptable for some control applications.

To address this, TSN uses frame preemption, defined by IEEE 802.1Qbu (Frame Preemption) and IEEE 802.3br (Interspersing Express Traffic).^[4] The two standards allow a high-priority frame to interrupt a lower-priority, preemptable frame mid-transmission. The interrupted frame is fragmented, the priority frame is sent immediately, and the remaining fragments are transmitted once the priority frame is finished.

Other applicable standards include:

IEEE 802.1CB (Frame Replication and Elimination for Reliability) improves resilience by replicating frames over redundant paths and eliminating duplicates at the receiver.^[5]
IEEE 802.1Qci (Per-Stream Filtering and Policing) helps prevent a misbehaving or misconfigured stream from monopolizing network resources or degrading other traffic.^[6]
IEEE 802.1Qcc (Stream Reservation Protocol) provides models for network configuration and resource management^[7]

How Industrial Protocols Use TSN

The bounded latency of TSN as a unified, deterministic Layer 2 Ethernet framework has led industrial automation standards organizations to adapt their existing protocols for TSN-enabled networks. This approach allows these organizations to retain the features, diagnostics, and object models of their protocols while using TSN to achieve deterministic Ethernet behavior at the network layer.

One of the most important examples of this shift is the integration of Open Platform Communications Unified Architecture (OPC UA) over TSN. This integration supports vendor-neutral, interoperable communication across controllers, devices, and higher-level systems. In this approach, OPC UA uses the publish/subscribe (Pub/Sub) model rather than the traditional client/server model. Pub/Sub is better suited for control and automation traffic because a single publisher can efficiently distribute data to multiple subscribers. The messages are encoded using the UA Datagram Protocol (UADP) and sent over User Datagram Protocol/Internet Protocol (UDP/IP).

TSN then provides the underlying Ethernet timing and traffic control operations. IEEE 802.1AS provides a shared time base across time-aware devices, while IEEE 802.1Qbv schedules when specific traffic classes can transmit. In this way, OPC UA defines the information model and communication semantics, while TSN helps provide predictable transport behavior for time-sensitive industrial communication.

Other industrial Ethernet ecosystems, including PROFINET, EtherNet/IP using the Common Industrial Protocol (CIP), and CC-Link IE TSN, have also adapted their protocols to TSN-enabled Ethernet.

Conclusion

Time-Sensitive Networking is a set of deterministic Ethernet capabilities that allows an industrial network to be designed with more predictable timing and better coexistence between critical and non-critical traffic. For industrial automation, that matters because factory communication is about servo coordination, distributed sensing, vision, edge analytics, and the convergence of operational technology (OT) and IT on shared infrastructure.

The future of industrial automation will continue to depend on how well the network can handle mixed traffic. Now that we’ve examined how TSN factors into that future, we will next explore the role of Single Pair Ethernet (SPE) in enabling efficient communication in automation systems.

[1]https://1.ieee802.org/tsn/
[2]http://standards.ieee.org/ieee/802.1AS/11968/
[3]http://standards.ieee.org/ieee/802.1Qbv/6068/
[4]http://standards.ieee.org/ieee/802.1Qbu/5464/; https://standards.ieee.org/ieee/802.3br/5814/
[5]https://standards.ieee.org/ieee/802.1CB/5703/
[6]https://standards.ieee.org/ieee/802.1Qci/6159/
[7]https://standards.ieee.org/ieee/802.1Qcc/5784/