Making Sense of it All: AVB, TSN, SOME/IP, DoIP and UDS
As vehicle architectures evolve toward software-defined and connected platforms, engineers increasingly encounter a set of networking and communication technologies—AVB, TSN, SOME/IP, DoIP, and UDS. While each serves a distinct purpose, together they enable modern vehicles to support high-bandwidth data transport, service-oriented software communication, diagnostics, and remote software updates. Understanding how these technologies relate helps clarify the communication stack inside today’s connected vehicles.
At the network layer, Audio Video Bridging (AVB) and Time-Sensitive Networking (TSN) extend Automotive Ethernet to support deterministic communication. AVB introduced mechanisms for guaranteed bandwidth and synchronized streaming, which proved valuable for camera and infotainment data. TSN builds on this foundation, adding precise scheduling, time synchronization, and traffic shaping so that Ethernet can support both high-bandwidth sensor data and real-time control traffic within the same network infrastructure. TSN also includes protocols for building redundancy into Ethernet networks, including duplicate sources of the grand master clock signal, and message de-duplication.
At the software communication layer, SOME/IP (Scalable service-Oriented Middleware over IP) enables service-oriented communication between software components across the vehicle network. Rather than relying solely on static ECU-to-ECU messaging, SOME/IP allows applications to expose services that other components can dynamically discover and consume. Importantly, SOME/IP gateways can expose services originating on non-IP networks such as CAN or LIN, effectively allowing those devices to participate in an IP-addressable service ecosystem within the vehicle.
Diagnostics over IP (DoIP) performs a similar role for diagnostic communication. Traditional diagnostics rely on UDS (Unified Diagnostic Services) transported over CAN. DoIP allows the
same diagnostic services to operate over Ethernet using IP networking, greatly increasing communication speed and enabling diagnostic tools to reach ECUs through the vehicle’s Ethernet backbone. This also enables remote diagnostics and cloud-assisted service workflows.
Beyond diagnostics, UDS also plays a critical role in ECU software updates. In many OTA architectures, the final installation step—often called the re-flash phase—uses UDS programming services to write new firmware into ECU memory. The OTA system handles secure software distribution, validation, and campaign orchestration, while UDS provides the standardized mechanism for transferring firmware blocks and controlling ECU reprogramming. When combined with DoIP, this re-flash process can occur over Ethernet rather than slower CAN channels, significantly improving update speed.
Together, AVB, TSN, SOME/IP, DoIP, and UDS form a layered communication framework that bridges traditional automotive networks with modern IP-based architectures. SOME/IP and DoIP enable IP-addressable services even when underlying devices remain connected through legacy buses, while UDS provides the standardized interface for diagnostics and firmware installation. This layered approach allows automakers to preserve proven control networks while enabling the cloud-connected, updateable software platforms required for software-defined vehicles.
Leave a Comment