Automotive Ethernet

Automotive Ethernet uses a single unshielded twisted pair (100BASE-T1, 1000BASE-T1) instead of standard Ethernet's 4-pair cables, reducing weight and cost. It operates in harsh automotive environments (-40°C to +125°C) with EMC requirements. Physical layer standards: BroadR-Reach (100Mbps) and Multi-Gig (1-10Gbps). Same upper-layer protocols (TCP/IP, UDP) but automotive-specific middleware (SOME/IP) and time synchronization (TSN/gPTP).

100BASE-T1 (IEEE 802.3bw) provides 100Mbps Ethernet over a single unshielded twisted pair with PAM-3 encoding. Key features: full-duplex on one pair, reach up to 15 meters, designed for automotive EMC requirements, and lower cost/weight than standard 100BASE-TX. It uses echo cancellation for simultaneous TX/RX on the same pair. Common PHYs: NXP TJA1100/1101, Broadcom BCM89810. Successor: 1000BASE-T1 (IEEE 802.3bp) for Gigabit.

SOME/IP is the automotive middleware protocol for service-oriented communication over Ethernet. It provides: request/response methods (RPC), event notifications (publish/subscribe), field getters/setters, and serialization. SOME/IP-SD (Service Discovery) enables dynamic service registration and discovery. Defined by AUTOSAR, it runs over UDP (events, notifications) or TCP (reliable methods, large data). Default ports: 30490 (SD), 30491+ (services).

SOME/IP-SD uses UDP multicast (default 224.0.0.251:30490) for service announcement and discovery. Server sends OfferService entries with service ID, instance ID, TTL, and endpoint options. Clients send FindService to locate services. Subscription uses SubscribeEventgroup/SubscribeEventgroupAck. SD supports: initial wait phase, repetition phase, and main phase for offer timing. TTL-based expiration handles server disappearance.

DoIP (ISO 13400) enables UDS diagnostic communication over Ethernet/TCP. It replaces CAN-based diagnostics for Ethernet-connected ECUs. DoIP entity types: DoIP node (ECU), DoIP gateway (routes between CAN and Ethernet). Discovery uses UDP broadcast for vehicle identification. Diagnostic messages use TCP for reliable delivery. Supports: routing activation, alive checking, and diagnostic power mode. Standard port: 13400.

TSN is a set of IEEE 802.1 standards providing deterministic Ethernet communication. Key standards: 802.1AS (time synchronization - gPTP), 802.1Qbv (time-aware shaper - scheduled traffic), 802.1Qci (stream filtering and policing), 802.1CB (frame replication and elimination - redundancy), and 802.1Qcc (stream reservation). TSN guarantees bounded latency and zero packet loss for critical traffic like ADAS sensor data.

gPTP (IEEE 802.1AS) synchronizes clocks across all Ethernet nodes. A Grandmaster clock distributes time via Sync/Follow-Up messages. Each switch/bridge measures and compensates for link and processing delays using Pdelay_Req/Resp messages. Accuracy: sub-microsecond synchronization. This enables time-triggered scheduling (802.1Qbv) and correlating sensor data timestamps. One Grandmaster is elected via Best Master Clock Algorithm.

An Ethernet switch operates at Layer 2 (MAC addresses) - forwards frames based on destination MAC, supports VLANs, and provides TSN capabilities. A gateway operates at Layer 3+ - routes between different network domains (CAN↔Ethernet), translates protocols, and enforces security policies. In modern architectures, central gateways often combine both: Ethernet switching for the backbone and gateway functionality for CAN/LIN domain bridging.

VLAN (Virtual LAN, IEEE 802.1Q) logically segments an Ethernet network into isolated broadcast domains using tags in the Ethernet frame. Automotive use: separate ADAS traffic (VLAN 10) from infotainment (VLAN 20) from diagnostics (VLAN 30). Benefits: traffic isolation (security), bandwidth management, and broadcast storm containment. VLAN tags add 4 bytes to the frame including priority (PCP) for QoS.

QoS prioritizes critical traffic. Mechanisms: IEEE 802.1Q PCP (Priority Code Point) - 8 priority levels mapped to traffic classes. 802.1Qbv (Time-Aware Shaper) - scheduled time gates for deterministic delivery. 802.1Qav (Credit-Based Shaper) - rate limiting for AVB streams. Strict Priority queuing - highest priority first. CBS (Credit Based Shaper) - smooth traffic for audio/video. Configuration maps SOME/IP services to appropriate QoS classes.

SoAd bridges the PDU-based AUTOSAR communication stack with the socket-based TCP/IP stack. It maps I-PDUs to TCP/UDP sockets: PduR sends a PDU to SoAd, which sends it via TcpIp on the configured socket. On reception, SoAd receives data from TcpIp, identifies the corresponding PDU, and delivers to PduR. SoAd manages: socket connections, routing groups (enable/disable PDU routing), and PDU-to-socket assignment.

Ethernet II frame: Preamble (7B) + SFD (1B) + Destination MAC (6B) + Source MAC (6B) + [802.1Q VLAN tag (4B optional)] + EtherType (2B) + Payload (46-1500B) + FCS (4B). EtherType values: 0x0800 (IPv4), 0x0806 (ARP), 0x86DD (IPv6), 0x8100 (VLAN tagged). With 802.1Q: adds TPID + PCP (3 bits priority) + DEI + VID (12 bits VLAN ID). MTU is typically 1500 bytes; jumbo frames up to 9000B for high-bandwidth ADAS data.

ARP (Address Resolution Protocol) resolves IP addresses to MAC addresses. A node broadcasts an ARP request asking 'Who has IP x.x.x.x?' and the target responds with its MAC address. The result is cached. In automotive: ARP cache is typically preconfigured (static ARP) for deterministic behavior and security (prevents ARP spoofing attacks). Dynamic ARP is used in flexible environments but requires ARP inspection for security.

Static IP: each ECU has a preconfigured IP address - deterministic, no DHCP dependency, simpler. Used in most production vehicles. DHCP: addresses assigned dynamically - flexible, supports aftermarket devices. Used in diagnostic networks and some infotainment. Automotive link-local addressing (169.254.x.x) via Auto-IP provides fallback. Some architectures use static for safety-critical and DHCP for non-critical domains.

TCP: connection-oriented, reliable (retransmission, ordering), flow control. Used for: DoIP diagnostics (reliability needed), large file transfers, OTA updates, and SOME/IP methods requiring guaranteed delivery. UDP: connectionless, fast, no retransmission. Used for: SOME/IP events/notifications (low latency), SOME/IP-SD (multicast), AVB/TSN streams, and real-time sensor data. Choice depends on reliability vs latency requirements.

Multicast sends data to a group of subscribers simultaneously using special IP addresses (224.0.0.0/4). SOME/IP-SD uses multicast for service discovery. Event notifications can use multicast for efficient one-to-many delivery. IGMP (Internet Group Management Protocol) manages multicast group membership. Ethernet switches forward multicast only to ports with subscribers (IGMP snooping), preventing unnecessary bandwidth usage.

Ethernet wake-up brings ECUs from sleep mode. Methods: 1) Wake-up pattern - PHY detects specific signaling on the wire and wakes the MAC/CPU. 2) Wake-on-LAN - specific Ethernet frame triggers wake-up. 3) Link-up detection - PHY detecting link establishment triggers wake. Standards: IEEE 802.3 wake frames, NXP TJA1100 wake-up pin. Used for: partial networking (only wake needed ECUs), remote diagnostics, and OTA scheduling.

802.1Qbv defines time-triggered gates on switch output ports. Each priority queue has a gate that opens/closes on a precise schedule (Gate Control List). This guarantees time slots for critical traffic: during the ADAS time slot, only ADAS traffic passes; during best-effort slot, general traffic passes. Result: deterministic, bounded latency for scheduled traffic, independent of other traffic load. Requires gPTP time synchronization.

Frame preemption allows high-priority (express) frames to interrupt transmission of low-priority (preemptable) frames. The preempted frame is fragmented, the express frame is sent, and the preempted frame resumes. This reduces worst-case latency for critical traffic from one max-frame-time (~123μs for 1500B at 100Mbps) to near-zero without wasting bandwidth. Works with 802.1Qbv for even tighter latency bounds.

SOA replaces static signal-based communication with dynamic service-based communication. Ethernet enables SOA through: SOME/IP (service middleware), dynamic service discovery (no hardcoded routing), sufficient bandwidth (100Mbps-10Gbps vs CAN's 500kbps), IP-based addressing (scalable), and standard protocols (HTTP, MQTT for cloud connectivity). This supports: software-defined vehicles, OTA feature updates, and third-party app integration.

The backbone architecture uses a high-speed Ethernet network (typically Gigabit or higher) connecting zone controllers or domain controllers. Zone controllers aggregate CAN/LIN from local sensors/actuators and bridge to the Ethernet backbone. Benefits: reduced wiring (shorter CAN runs to nearby zone controller), high bandwidth for central computing, scalable, and supports centralized software architecture. Used in modern E/E architectures by VW, BMW, Tesla.

Tools and methods: Wireshark for packet capture (via switch mirror port or TAP). SOME/IP dissectors for protocol analysis. PTP/gPTP timing analysis tools. Cable quality testing (return loss, insertion loss for 100BASE-T1). Switch statistics (error counters, queue utilization). AUTOSAR DEM DTCs for Ethernet stack errors. DoIP diagnostic gateway logs. Network simulation tools (Vector CANoe.Ethernet) for integration testing.

EthSwt driver manages the automotive Ethernet switch hardware. It provides: port configuration (speed, duplex, VLAN membership), MAC address table management, port mirroring (for IDS/debugging), traffic statistics, STP configuration, and QoS settings. Works with EthSwtIf (interface abstraction) for hardware independence. Switch configuration includes: VLAN assignments, multicast groups, rate limiting, and TSN schedule tables.

Typical bandwidth requirements: Surround-view cameras: 4×3Gbps (raw) or 4×50Mbps (compressed). LIDAR point cloud: 100-700Mbps. Radar: 10-100Mbps. Infotainment streaming: 5-25Mbps. CAN gateway traffic: <5Mbps. Diagnostic communication: <1Mbps. OTA updates: 10-50Mbps desired. This drives the need for multi-Gbps backbone Ethernet (1000BASE-T1, 2.5GBASE-T1, or 10GBASE-T1) in ADAS-equipped vehicles.

IEEE 802.1CB provides hitless redundancy by: sending duplicate frames over disjoint paths, and eliminating duplicates at the receiver. If one path fails, the other delivers without delay. Applied to safety-critical streams (ADAS sensor data, brake-by-wire commands). Combined with 802.1Qci (stream filtering), it ensures only valid frames are forwarded. This achieves zero-recovery-time redundancy required for fail-operational ADAS systems.

SOME/IP serialization encodes data types into byte streams: basic types (uint8-64, float32/64) with defined byte order, strings (BOM + UTF-8/16 + length prefix), arrays (length prefix + elements), structs (sequential fields with optional length prefix), unions (type selector + data), and enumerations (underlying integer type). Optional fields use TLV (Tag-Length-Value) encoding. Serialization rules are defined in the SOME/IP specification and ARXML.

AVB (IEEE 802.1BA) provides synchronized streaming over Ethernet for audio/video. Key components: gPTP for time sync, 802.1Qav (Credit-Based Shaper) for bandwidth reservation, and AVTP (Audio/Video Transport Protocol) for media streaming. In automotive: distributing audio to multiple speakers, rear-seat entertainment video, surround-view camera streams, and driver monitoring camera feeds. AVB guarantees bounded latency and zero packet loss for media.

A network TAP (Test Access Point) is a passive hardware device that copies all traffic on a link for monitoring without affecting the original traffic. A mirror port (SPAN port) on a switch copies selected traffic to a designated port. Both enable: packet capture with Wireshark, IDS monitoring, and debugging. Mirror ports are software-configurable but may miss frames under heavy load; TAPs are more reliable but require physical installation.

AUTOSAR TCP/IP initialization sequence: 1) Eth driver init (Eth_Init - MAC controller). 2) EthTrcv init (PHY configuration). 3) EthIf init (interface abstraction). 4) TcpIp init (stack initialization, socket creation). 5) SoAd init (PDU-socket mapping). 6) IP address assignment (static config or DHCP). 7) ARP table population. 8) Socket binding and connection establishment. Each module's MainFunction must be scheduled cyclically for ongoing operation.

Automotive Ethernet PHYs include cable diagnostics: Time Domain Reflectometry (TDR) sends a pulse and measures reflections to detect: open circuit (broken cable), short circuit, impedance mismatch (bad connector), and cable length. Diagnostics are triggered via PHY registers and report results as: cable status, fault distance, and signal quality. Used during: production line testing, vehicle service, and runtime monitoring for link quality degradation.