Contents
StandardISO

ISO 13400 (DoIP)

Road vehicles — Diagnostic communication over Internet Protocol (DoIP)

ISO 13400 defines how diagnostic tools find a vehicle and exchange diagnostic messages with its electronic control units over IP networks, typically using Ethernet.

What it is

ISO 13400 is the multi-part standard for Diagnostic communication over Internet Protocol, usually called DoIP. It provides the communication framework that lets a diagnostic tester discover a vehicle, establish a connection, and exchange diagnostic messages through a vehicle diagnostic entry point.

Think of DoIP as the delivery mechanism for diagnostic requests and responses. Reading a fault code or requesting a programming operation depends on the diagnostic service carried inside that communication.

Who it applies to

It matters to vehicle manufacturers, ECU and gateway suppliers, diagnostic stack developers, and companies building workshop or production testers. Teams implementing Ethernet diagnostic access need an agreed interpretation of the applicable parts and vehicle requirements.

ISO 13400 is a technical standard rather than a regulation that automatically applies to every vehicle. Its requirements become relevant through the selected architecture, customer specifications, and contractual commitments. The full normative documents are generally paid publications.

What it covers

The series addresses diagnostic communication over IP and the associated vehicle interface. Its transport and network services include vehicle discovery, connection handling, routing activation, diagnostic message delivery, and communication error handling. Routing activation establishes the diagnostic routing context; it should not be treated as permission to execute every diagnostic service.

Mechanism Purpose
Vehicle discovery Find and identify a vehicle on the connected network.
Routing activation Establish diagnostic routing through the vehicle entry point.
Diagnostic transport Carry requests and responses between tester and addressed targets.
Connection handling Maintain communication and handle interruptions or invalid traffic.

DoIP uses UDP and TCP for different communication functions. The applicable edition and vehicle profile determine the secure connection requirements, including whether and how TLS is used. TLS protects a connection; service authorization still needs its own design.

How it fits with other documents

ISO 14229 defines Unified Diagnostic Services, or UDS: the diagnostic operations commonly carried over DoIP. ISO 13400 supplies the communication path, while UDS defines the meaning of service requests and responses.

Ethernet and Internet protocol specifications provide underlying connectivity. An AUTOSAR implementation may provide a DoIP software module, but its configuration still needs to match the vehicle architecture and tester expectations. Manufacturer specifications add project choices such as addressing, supported targets, and access policies.

For software updates, DoIP can carry diagnostic programming traffic. It does not define a complete OTA campaign, package trust model, or update orchestration strategy.

In practice

Start with a tester-to-ECU communication map: identify the entry point, logical target addresses, downstream routes, and required vehicle states. Record the applicable standard editions and project options before configuring stacks or purchasing test equipment.

Validate the whole sequence: network connectivity, discovery, connection establishment, routing activation, and a diagnostic exchange. Then exercise interrupted connections, unavailable targets, ECU resets, and simultaneous tester access. Capture both network traffic and diagnostic logs so engineers can distinguish a failed delivery path from a diagnostic service rejection.

What it means for your discipline

  • Diagnostics & lifecycleCore

    Own vehicle discovery, routing activation, diagnostic addressing, and tester interoperability. Distinguish transport failures from diagnostic service failures when troubleshooting.

  • Networks & communicationCore

    Implement and validate IP connectivity, diagnostic connections, and gateway routing behavior. Check how segmentation and vehicle network states affect diagnostic access.

  • Base softwareCore

    Integrate the DoIP stack with sockets, diagnostic services, and gateway functions. Configure connection handling, addressing, and error behavior against the applicable vehicle profile.

  • E/E architecturePartial

    Place diagnostic entry points and define paths to target ECUs. Allocate responsibilities across gateways, central computers, and downstream networks.

  • CybersecurityPartial

    Review diagnostic exposure, secure connection requirements, and gateway access policies. Check the applicable edition and vehicle profile for TLS support and required deployment choices.

  • Hardware & siliconPartial

    Coordinate the external diagnostic Ethernet interface and applicable activation provisions with network and diagnostics teams. Verify that physical connectivity supports the intended service workflow.

  • Software update & OTAPartial

    Account for DoIP connection behavior when diagnostic services carry programming traffic. Plan reconnection and recovery around ECU resets and changing vehicle network availability.

No direct stake: Functional safety · HPC & application software