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.
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.