Imagine several machines working together on the same production line: a PLC triggering a robotic arm, a drive adjusting motor speed and a vision system inspecting the output. If every device has a slightly different idea of what time it is, coordinating these actions becomes difficult. Packets can arrive reliably and still be useless if devices don’t agree on when things should happen.
This is where IEEE 802.1AS comes in: the Time-Sensitive Networking (TSN) mechanism responsible for keeping devices on the same time base, so coordinated, predictable operations become possible across an industrial Ethernet network.
What Is IEEE 802.1AS?
IEEE 802.1AS is an IEEE standard that defines time synchronisation mechanisms used in Time-Sensitive Networking (TSN) to provide a common time base across networked devices. It’s part of the broader IEEE 802.1 TSN family of standards, which extend standard Ethernet with capabilities for more predictable, time-aware communication.
In a typical Ethernet network, devices run on independent internal clocks. Left uncorrected, these clocks drift apart over time, a phenomenon called clock skew. For everyday IT traffic, small timing differences rarely matter. But in industrial automation, where actions must be coordinated across multiple devices, even small discrepancies can affect how well operations line up. IEEE 802.1AS addresses this by defining how devices exchange timing information so they can align to a shared reference clock, giving TSN networks the synchronised foundation that other TSN features, such as scheduled traffic, depend on.
What Is gPTP?
The mechanism IEEE 802.1AS actually uses to synchronise clocks is called generalised Precision Time Protocol, or gPTP. gPTP is a profile built on concepts from the IEEE 1588 Precision Time Protocol (PTP), adapted specifically for the needs of TSN networks.
In simple terms, gPTP allows devices on a network to agree on a shared understanding of time by exchanging timestamped messages. One device is designated as the grandmaster clock, the reference point the rest of the network synchronises to, while other devices measure their offset from that reference and adjust accordingly.
It’s worth noting that gPTP is not simply identical to every implementation of conventional PTP. It defines a specific, constrained profile suited to TSN environments, with its own rules for message exchange and network behaviour. This distinction matters when evaluating whether a device or switch genuinely supports TSN-grade synchronisation.
How IEEE 802.1AS Time Synchronisation Works
Conceptually, IEEE 802.1AS synchronisation follows a few key steps. First, devices on the network establish a timing hierarchy, often called a synchronisation spanning tree, which determines how timing information flows from the reference clock outward to other devices.
Next, the network selects the appropriate time source, the grandmaster clock, using a selection process defined by the standard. This clock becomes the reference that all other devices align to.
From there, devices exchange timing messages along the hierarchy, and each link measures propagation delay, the time it takes a signal to travel between two connected devices. This matters because network cabling and hardware processing introduce small delays that must be accounted for, not ignored.
Using this information, each device adjusts its local clock to align with the grandmaster’s time. As conditions change devices joining or leaving, delays shifting the network slightly- it continues exchanging messages to maintain synchronisation over time.
A simple industrial example: a PLC issues a coordinated command; it passes through a TSN switch that maintains accurate timing information as it forwards traffic, and an industrial device receives that command with a shared understanding of when it should act, not just that it arrived.
Why Time Synchronisation Matters in TSN
A shared time base is foundational to deterministic networking. Without it, other TSN capabilities like scheduled traffic, where transmission windows are planned, can’t function reliably, since scheduling only makes sense if devices agree on what time it is.
Synchronised time supports coordinated transmission between multiple devices, reduces timing uncertainty across the network, and helps industrial devices act in step with one another. This is particularly relevant in motion-control applications, where multiple axes may need tightly coordinated movement, and in coordinated data acquisition, where readings from multiple sensors need to be aligned in time to be meaningful.
It’s important to distinguish time synchronisation from general network speed. A fast network isn’t necessarily a synchronised one; low latency and shared timing solve different problems, and TSN networks generally need both.
IEEE 802.1AS vs Traditional NTP and PTP
Several timing protocols exist, each suited to different environments.
| Technology | Main Purpose | Typical Use |
|---|---|---|
| NTP | General clock synchronisation | IT networks |
| PTP | High-precision time synchronization | Industrial/scientific networks |
| IEEE 802.1AS/gPTP | Time synchronisation for TSN | Deterministic Ethernet/TSN |
NTP (Network Time Protocol) is widely used in general IT environments to keep clocks reasonably aligned, sufficient for logging, certificates, or scheduling tasks, but not designed for the precision industrial coordination requires.
PTP offers much higher precision and is used across various industrial and scientific applications requiring accurate timing.
IEEE 802.1AS, through gPTP, is based on concepts from PTP but is defined specifically for TSN-related synchronisation. It’s not a competing standard so much as a purpose-built profile narrower in scope, but tailored to how TSN networks need to behave.
What Role Does a TSN Ethernet Switch Play?
TSN-capable Ethernet switches are the infrastructure that timing information actually travels through. As gPTP messages pass from device to device, switches play a direct role in how accurately that timing information is preserved.
Switches that support hardware timestamping can mark the precise moment a timing message enters or leaves a port, rather than relying on software-level timestamps that introduce variable delay. Switches also factor into propagation-delay measurements along each link, and they help maintain the common time base as it’s distributed across the network.
Not every industrial Ethernet switch handles this the same way, which is why switch capabilities are worth examining closely rather than assumed.
Where Is IEEE 802.1AS Used?
IEEE 802.1AS synchronisation is relevant across a range of industrial and time-sensitive applications, including factory automation, motion control, and robotics, where coordinated movement across multiple axes or machines depends on shared timing. It’s also used in automotive Ethernet networks, industrial machine coordination more broadly, time-sensitive data acquisition systems, and in some contexts, audio/video systems where precise timing alignment matters.
The exact synchronisation requirements vary significantly depending on the application, so what’s “sufficient” in one deployment may not be in another.
What Should You Check When Choosing a TSN Switch?
When evaluating a TSN switch for time-synchronised applications, consider:
- IEEE 802.1AS/gPTP support, specifically
- Which other TSN standards are supported (not just a general “TSN-ready” label)
- Hardware timestamping capability
- Port speed and number of ports needed
- Copper, fibre, or SFP connectivity options
- Environmental specifications for the deployment location
- Management and diagnostic tools available
- Compatibility with the automation equipment already on the network
“TSN switch” is a broad label, and it doesn’t guarantee every TSN feature is included. Buyers should verify which specific standards, including IEEE 802.1AS, a switch actually supports before assuming compatibility.
Conclusion
Synchronised time is a foundational requirement for deterministic industrial Ethernet, and IEEE 802.1AS is the standard that makes it possible, giving devices a shared time base that other TSN capabilities build on. As industrial networks bring together PLCs, drives, sensors, and robotics on shared infrastructure, understanding how synchronisation actually works helps engineers and integrators make informed decisions.
Comxus designs industrial Ethernet networking hardware with these requirements in mind, and recommends evaluating switch capabilities carefully against the actual synchronisation needs of your application before deployment.
Read Also: TSN vs Standard Ethernet: What Changes in Industrial Automation?
Read Also: Understanding DIN-Rail Industrial Ethernet Switches
