Contents

Automotive Ethernet

Single-pair Ethernet from 10 Mbit/s to multi-gigabit that forms the backbone of zonal architectures and carries IP, services, cameras and diagnostics.

Why it exists

Cameras, central compute, OTA updates and service-oriented software need far more bandwidth than CAN can offer. Office Ethernet uses four wire pairs and is too heavy and noisy for cars, so the industry standardised single-pair variants that meet automotive EMC and temperature requirements.

What it is

Variant Speed Typical use
10BASE-T1S 10 Mbit/s, multidrop Edge nodes in zones
100BASE-T1 100 Mbit/s ECU links, diagnostics
1000BASE-T1 1 Gbit/s Backbone, HPC links
Multi-gig 2.5–10 Gbit/s+ Central compute, sensor data

Unlike CAN, Ethernet is point-to-point and switched: every link connects two devices, and switches forward frames.

How it works in the vehicle

Zone controllers and HPCs connect over a switched backbone. VLANs separate traffic classes and security domains; QoS and TSN give control traffic deterministic timing; gPTP synchronises clocks. On top run IP, SOME/IP or DDS, DoIP and update protocols.

Automotive Ethernet protocol stack
SOME/IP · DoIPServices and diagnostics
TCP · UDPTransport depends on message type
IPAddressing and routing
Ethernet MACFrames and MAC addresses
Ethernet PHYSignals over the physical link

Read bottom to top; SOME/IP and DoIP use TCP or UDP depending on the communication function.

When to use it

For the backbone, central compute, high-bandwidth sensors and diagnostics. Keep CAN FD and LIN where cost and simplicity matter.

Best practices

  • Plan VLANs and trust zones together with the security team.
  • Reserve bandwidth for worst-case update and logging traffic, not just functional traffic.
  • Use TSN features deliberately (802.1DG profile) rather than enabling everything.

Common pitfalls

  • Treating the vehicle network like an office LAN with permissive defaults.
  • Underestimating switch configuration and its lifecycle management.

What it means for your discipline

  • Networks & communication Core

    Designs switched topologies, VLANs, bandwidth, QoS and time synchronisation; chooses speed grades per link.

  • Hardware & silicon Core

    Selects PHYs and switches, single-pair cabling and connectors, and handles EMC at multi-gigabit speeds.

  • E/E architecture Core

    Ethernet is what lets functions move to central compute — its topology defines the zonal backbone.

  • Cybersecurity Partial

    Enables MACsec, IPsec and TLS, firewalls and VLAN segmentation — but also exposes IP-based attack techniques.

  • HPC & application software Partial

    Service middleware (SOME/IP, DDS) and IP stacks on HPCs depend on Ethernet.

  • Diagnostics & lifecycle Partial

    DoIP and SOVD run over Ethernet, enabling fast flashing and remote diagnostics.

  • Software update & OTA Partial

    Plans update transfer times and bandwidth across Ethernet links and gateways; coordinates VLAN access and QoS so flashing traffic can reach target ECUs without disrupting vehicle functions.

No direct stake: Functional safety · Base software

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 — Drives Ethernet interfaces and exposes hardware capabilities for VLANs, timestamping and traffic prioritisation.
  • Linux — Provides IP networking, routing and network configuration for Ethernet-connected vehicle services.
  • SOME/IP · DDS — Runs SOME/IP or DDS service communication over the Ethernet-backed IP network.
MCU-based ECU · AUTOSAR Classic
  • Communication — Provides communication-stack paths for Ethernet-carried application traffic and network management.
  • ECU abstraction — Abstracts Ethernet controllers, transceivers and switches through interfaces such as EthIf.
  • Microcontroller abstraction (MCAL) — Drives Ethernet controllers and exposes frame transmission, reception and supported hardware timing features.