The software-defined vehicle requires high-throughput, low-latency in-vehicle communication. Transitioning from legacy signal matrices over CAN and LIN to high-bandwidth Ethernet demands specialized automotive middleware capable of handling remote procedure calls, sensor telemetry streaming, and deterministic cycle times.
In legacy vehicle architectures, sensors and ECUs broadcast periodic CAN messages containing packed bits without any intrinsic metadata. If a developer adds a new sensor or expands a telemetry field, every receiving ECU requires a recompilation of its DBC communication matrix. In a Service-Oriented Architecture (SOA), applications treat functionality as discoverable network services. Applications request sensor streams by name, receive strongly typed data models, and communicate across language boundaries through formal interface definition languages (such as Franca IDL or protobuf).
SOME/IP is the automotive industry standard middleware developed specifically to fit inside resource-constrained embedded systems while powering AUTOSAR Adaptive applications. The protocol consists of a compact 16-byte header prepended to serialized payload data. It provides three primary communication primitives: Request/Response for RPC method invocation, Fire & Forget for asynchronous commands, and Eventgroups for publish/subscribe notification. The companion SOME/IP Service Discovery (SOME/IP-SD) protocol runs over UDP multicast to announce service availability, handle subscriptions, and monitor link health.
While SOME/IP excels at control messaging, autonomous driving systems generate gigabytes of camera frames, LiDAR point clouds, and radar tracks per second. Data Distribution Service (DDS), maintained by the Object Management Group (OMG), provides a decentralized, brokerless publish-subscribe architecture built upon the Real-Time Publish-Subscribe (RTPS) wire protocol. DDS allows architects to declare fine-grained Quality of Service (QoS) contracts per topic: Reliability (BEST_EFFORT vs RELIABLE), Durability (transient local caching for late joiners), Deadline (guaranteeing telemetry updates within strict time windows), and Liveliness.
Standard commercial Ethernet is non-deterministic: under heavy network traffic, buffer bloat and packet collisions introduce unpredictable jitter and transmission delays that violate automotive functional safety (ISO 26262 ASIL D). Time-Sensitive Networking (TSN) defines a suite of IEEE standards implemented in automotive Ethernet switches. IEEE 802.1AS synchronizes clocks across all ECUs to sub-microsecond precision, while IEEE 802.1Qbv (Time-Aware Shaper) slices time into repeating transmission gates. This allows safety-critical steer-by-wire and braking commands to pass through Ethernet backbones without encountering queue congestion.