Why it exists
Standard Ethernet is “best effort”: a large camera or update transfer can delay a small control message. Vehicles need guarantees, so IEEE extended Ethernet with time-awareness.
What it is
- Time synchronisation (802.1AS / gPTP) gives all nodes a common clock.
- Traffic shaping (credit-based) and scheduling (time-aware gates) reserve bandwidth and time slots.
- Preemption lets urgent frames interrupt long ones.
- Redundancy features can send critical frames over two paths.
How it is used
A subset of features — defined for vehicles in IEEE 802.1DG — is configured on switches and endpoints. Control traffic gets a guaranteed class; bulk data uses the rest.
Best practices
- Start from the 802.1DG profile instead of enabling every TSN feature.
- Model and measure end-to-end latency, including software stacks — not just the network.
Common pitfalls
- Assuming TSN fixes latency caused by operating systems and middleware on the endpoints.