Why CAN FD still wasn't enough

CAN FD's 64-byte frames and multi-megabit data phase (see CAN FD Explained) is a large step up from classic CAN, but a single forward-facing ADAS camera can produce tens of megabits per second on its own - before adding a full surround-view camera set, radar, lidar, or a high-resolution infotainment display. That's office-network territory, which is exactly where automotive Ethernet borrows from: the same IEEE 802.3 Ethernet used everywhere else, adapted for the automotive environment.

What's actually different from office Ethernet

Office EthernetAutomotive Ethernet
Cabling4-pair (Cat5e/6)Single unshielded twisted pair (100BASE-T1, 1000BASE-T1)
PriorityBest-effort by defaultDeterministic timing via Time-Sensitive Networking (TSN/AVB)
TopologySwitched star, flexibleFixed, designed against EMC and weight constraints

The single-pair physical layer (100BASE-T1 and faster variants) is the key automotive-specific piece - it gives Ethernet-class bandwidth over cabling that's a similar weight and cost to a CAN pair, which matters a great deal at vehicle scale.

SOME/IP: the application layer on top

Raw Ethernet just moves packets - it doesn't define what a "vehicle speed" service looks like on the wire, the way a CAN identifier or a J1939 PGN does. SOME/IP (Scalable service-Oriented MiddlewarE over IP) is the automotive standard that fills that role for Ethernet-based systems: services are published, discovered, and subscribed to dynamically (an infotainment module can discover "is a rear-camera service available on this network?" instead of every consumer needing a fixed, pre-agreed message list.

This is a meaningfully different design philosophy from CAN's fixed, broadcast-everything model - closer to how a modern web API is structured than to a DBC-defined message table - though CAN's traditional gateway/backbone role for chassis and powertrain data isn't going away; Ethernet is layered in for the systems that specifically need its bandwidth.

Where CAN and Ethernet meet

Most current vehicle architectures run both: a CAN (or CAN FD) backbone for the traditional powertrain/chassis/body domains, and an Ethernet backbone for ADAS, infotainment, and high-bandwidth sensors, bridged through a central gateway. Diagnosing or logging a modern vehicle increasingly means understanding both networks and where a given signal actually lives, not assuming everything is reachable from a single CAN tap.

Where this fits into the ONAC platform

Automotive Ethernet isn't something ONAC Network Studio captures today - it focuses on CAN, CAN FD, LIN, SENT and FlexRay. This module is here because Ethernet increasingly sits alongside those buses in modern vehicles, and knowing how the domains connect through gateways helps when you're tracing a signal from one network to another.