Contents
StandardIEEE

IEEE 802.1DG-2025

Time-Sensitive Networking profile for automotive in-vehicle Ethernet communications

IEEE 802.1DG selects Ethernet networking features and settings that help vehicle data arrive within predictable time limits.

What it is

IEEE 802.1DG-2025 is the automotive profile for Time-Sensitive Networking (TSN). TSN is a collection of Ethernet mechanisms for controlling when traffic is transmitted and how competing traffic shares network resources. A profile narrows that collection into features, options and defaults suitable for a particular environment.

Here, that environment is a vehicle’s switched Ethernet network. The goal is bounded latency: an engineered upper limit on network delivery time under stated operating assumptions. IEEE identifies bounded-latency automotive Ethernet as the standard’s scope. (IEEE standard overview)

Who it applies to

The main users are vehicle manufacturers, network architects, Ethernet component suppliers and engineers integrating electronic control units. It is relevant wherever applications share an in-vehicle Ethernet network and need predictable communication.

For a zonal architecture, this can mean coordinating traffic between zone controllers and central computers. Application developers also contribute: the network team needs realistic message sizes, transmission patterns and deadlines before it can establish timing bounds.

This is an engineering standard. Its applicability to a particular vehicle programme depends on the system requirements and contractual commitments adopted by that programme.

What it covers

The standard selects applicable IEEE networking features and explains their automotive use, including choices for optional parameters. Its purpose is to reduce the configuration freedom that would otherwise make independently developed components difficult to integrate. IEEE’s publication description highlights bandwidth, latency and synchronisation needs. (IEEE publication description)

For an engineering team, the practical questions include:

Question Engineering implication
Which profile provisions apply? Establish a shared requirements baseline for suppliers.
Which options and settings are selected? Make switch and endpoint configurations consistent.
What traffic assumptions support the design? Define the conditions under which timing must be verified.

A bounded-latency claim still needs a concrete topology, link capacities, traffic model and compatible implementation. Naming the profile in a specification does not establish an end-to-end application deadline by itself.

How it fits with other documents

IEEE 802.3 supplies the underlying Ethernet foundation. IEEE 802.1 TSN standards provide the networking mechanisms; IEEE 802.1DG profiles their use for automotive networks. Engineers therefore need the relevant underlying standards as well as the profile.

IEEE 802.1AS addresses time synchronisation. The automotive synchronisation amendment project, P802.1DGei, addresses selection of time synchronisation options, defaults and configuration constraints. Treat amendment work separately from the published baseline. (IEEE amendment project)

AUTOSAR communication software, application protocols and vehicle diagnostic services sit alongside this network foundation. Their integration must respect its timing assumptions. Functional safety and cybersecurity documents supply additional obligations that this profile alone does not satisfy.

In practice

Start with a traffic inventory: identify each communicating function, its endpoints, message sizes, burst patterns and timing needs. Map that traffic onto the proposed topology, then document the applicable profile provisions and supplier responsibilities.

Check capabilities in both switches and endpoints before committing to hardware. Record configuration choices in a controlled network description, and verify timing under representative competing traffic and the fault conditions required by the system design.

When topology, software traffic or configuration changes, review the timing evidence. Keep the selected standard edition and configuration baseline explicit so that every supplier is implementing the same agreement.

What it means for your discipline

  • Networks & communicationCore

    Own profile selection, traffic engineering, switch configuration and network timing verification. Translate application requirements into configurations that work across suppliers.

  • E/E architectureCore

    Allocate communication requirements across links, switches and endpoints. Use the profile when defining Ethernet backbones and supplier interface requirements.

  • Hardware & siliconPartial

    Check that Ethernet switches, controllers and timing hardware support the selected profile requirements. Include these capabilities in component selection and integration reviews.

  • Base softwarePartial

    Integrate Ethernet drivers, time synchronisation and network configuration with the platform software. Verify that endpoint behaviour matches the network design.

  • HPC & application softwarePartial

    Specify application traffic rates, deadlines and burst behaviour. Keep application communication within the assumptions used to establish network latency bounds.

  • Functional safetyPartial

    Review communication timing assumptions where safety functions depend on Ethernet. Use network verification evidence within the safety argument; profile conformity alone does not establish functional safety.

  • CybersecurityPartial

    Coordinate security controls with timing and availability requirements. Assess how protection mechanisms and abnormal traffic affect the engineered network.

No direct stake: Diagnostics & lifecycle · Software update & OTA