Contents

TSN — Time-Sensitive Networking

A family of IEEE 802.1 standards that gives Ethernet a common clock and deterministic timing, so control traffic can share the backbone with bulk data.

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.

What it means for your discipline

  • Networks & communication Core

    Selects and configures TSN features (time sync, shapers, schedules) and verifies end-to-end latency.

  • E/E architecture Partial

    TSN is what makes moving control functions onto the Ethernet backbone realistic.

  • Functional safety Partial

    Deterministic latency and redundancy support safety arguments for time-critical communication.

  • Hardware & silicon Partial

    Switches and MACs must support the chosen TSN features in hardware.

  • Software update & OTA Partial

    Fits update transfers within the bandwidth available to bulk traffic; checks transfer rates and throttling so downloads preserve control-traffic timing.

No direct stake: Cybersecurity · Base software · HPC & application software · Diagnostics & lifecycle

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)
  • BSP · drivers — Configures Ethernet hardware timestamping, traffic queues and supported scheduling features through device drivers.
  • Cortex-A cores · GPU/NPU · LPDDR — Ethernet MAC capabilities determine which endpoint TSN features can be implemented in hardware.
  • QNX / RT Linux — Bounds task scheduling and software processing delays that contribute to end-to-end communication latency.
MCU-based ECU · AUTOSAR Classic
  • Microcontroller abstraction (MCAL) — Ethernet drivers expose hardware timestamping and supported traffic scheduling controls.
  • Microcontroller · HSM — Integrated Ethernet hardware must support the timestamping and traffic controls required by the selected TSN features.
  • OS — Schedules communication tasks within the endpoint latency budget; network scheduling alone cannot bound software delays.