Contents

DoIP — Diagnostics over IP

How diagnostic communication moves from CAN to Ethernet — for much faster flashing and access to Ethernet-based ECUs.

Why it exists

Flashing gigabytes of software over CAN at 500 kbit/s takes too long. DoIP carries the same UDS messages over Ethernet.

What it is

  • Vehicle discovery: the tester finds the vehicle on the network.
  • Routing activation: the tester asks the DoIP edge node to route diagnostics into the vehicle.
  • Transport: UDS messages wrapped in TCP/UDP.
From discovery to diagnostics
Vehicle discoveryTester finds the vehicle
Routing activationTester requests diagnostic routing
Diagnostic exchangeUDS messages travel over TCP

Discovery and routing activation establish access before diagnostic messages are exchanged.

Tester and DoIP edge node
Tester
DoIP edge node
Vehicle announcementUDP; also answers vehicle identification requests
Routing activation request
Routing activation responseSuccessful activation shown
Diagnostic messageCarries a UDS request
Diagnostic acknowledgementDoIP acceptance, not UDS completion
Diagnostic messageCarries the target ECU’s UDS response

Simplified successful exchange: after UDP discovery, the tester establishes TCP before routing activation; the edge node may forward diagnostics to another ECU.

Best practices

  • Enable the Ethernet diagnostic connection only when needed (activation line).
  • Authenticate before routing requests to internal ECUs.

Common pitfalls

  • Leaving DoIP reachable from infotainment or connectivity networks.

What it means for your discipline

  • Diagnostics & lifecycle Core

    Uses DoIP for fast flashing in production and service.

  • Networks & communication Core

    DoIP edge nodes and gateways route diagnostics between Ethernet and internal buses.

  • Cybersecurity Partial

    An Ethernet diagnostic port is a powerful entry point; activation and authentication matter.

  • Base software Partial

    DoIP module and SoAd configuration in Ethernet ECUs.

  • Software update & OTA Partial

    Uses DoIP to transport flashing requests to Ethernet-connected ECUs; routing activation, access controls and throughput determine whether programming succeeds within the update window.

No direct stake: E/E architecture · Functional safety · HPC & application software · Hardware & silicon

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)
  • Diagnostics — Uses DoIP to exchange UDS requests with Ethernet ECUs and manages diagnostic routing when acting as a gateway.
MCU-based ECU · AUTOSAR Classic
  • Communication — Carries UDS messages through DoIP and socket adaptation over the Ethernet TCP/IP stack.
  • Diagnostics — Processes UDS requests delivered over DoIP and returns diagnostic responses.
  • Flash bootloader · secure boot — Handles firmware download and programming requests transported over DoIP during Ethernet flashing.