TL;DR
- ▸TSN was originally Ethernet-only. 5G's URLLC service class extends the same deterministic guarantees over wireless, opening up applications wired TSN couldn't address.
- ▸Making this work depends on the 5G network's timing fabric being precise enough to preserve TSN's bounded latency guarantees end to end.
- ▸That means G.8275.1 PTP across the 5G fronthaul, 802.1AS at the TSN edge, and a grandmaster that can deliver both profiles simultaneously.
TSN crosses the wireless boundary
TSN started as an Ethernet specification — a set of IEEE 802.1 standards (802.1AS for time, 802.1Qbv for traffic shaping, 802.1CB for redundancy) that delivered bounded latency over standard Ethernet. Industrial automation adopted it as the substrate for safety-critical control loops because it could deliver the deterministic timing and latency guarantees that closed industrial buses had previously needed dedicated wiring for.
5G's URLLC service class extends those guarantees over wireless. The combination — TSN over 5G — lets industrial operators run deterministic control loops over the air for applications wired TSN couldn't address: mobile robots, AGVs (automated guided vehicles), wireless control of moving machinery, drone-based inspection systems, mobile collaborative robotics. The technology is moving from research to early commercial deployment.
The integration challenge
Making TSN over 5G actually work depends on the 5G network's timing fabric being precise enough to preserve TSN's bounded latency guarantees end to end. That means G.8275.1 PTP across the 5G fronthaul (the standard 5G timing requirement), 802.1AS gPTP at the TSN edge (the industrial control timing requirement), and a grandmaster that can deliver both profiles simultaneously across a converged network.
Get any link in the chain wrong and the deterministic guarantees collapse. A misconfigured G.8275.1 grandmaster on the 5G side, a missing 802.1AS profile on the TSN side, or an asymmetric path delay anywhere in between will produce timing errors that propagate through the URLLC service and into the industrial control loop. The failure modes are subtle and only surface when the control loop misbehaves.
What this requires of the timing fabric
A grandmaster running G.8275.1 on its 5G-facing ports and 802.1AS on its TSN-facing ports, simultaneously and consistently. Most grandmasters historically supported one or the other; the converged TSN-over-5G use case requires both at once.
Where this is heading
Wireless TSN deployment is still early — most production industrial control still happens over wired TSN or over closed industrial buses. The 5G TSN integration work is happening at major automotive OEMs, industrial automation suppliers and a handful of ports and logistics operators that are willing to be early adopters. Over the next 3-5 years we expect TSN over 5G to become the dominant approach for industrial wireless control as the technology matures and the timing infrastructure catches up.
TimeBeat hardware supports both G.8275.1 and 802.1AS gPTP simultaneously on per-port configuration, so a single grandmaster can serve both the 5G fronthaul and the TSN edge in a converged industrial deployment. For early adopters of TSN over 5G, the conversation usually starts with whether the existing timing fabric is ready for the converged use case.