DoIP is one of those terms that gets thrown around constantly in current-generation diagnostic work, often without much explanation of what it's actually replacing or why it was necessary. This guide breaks down what this protocol does, layer by layer, and why it matters more with each new model year.
What DoIP Stands For, and What It Doesn't Replace
DoIP (Diagnostics over Internet Protocol) is standardized in ISO 13400, and it defines how diagnostic messages are transported over IP networks in practice, this means Ethernet inside or around the vehicle. It's important to be precise about what this framework actually changes: it does not replace UDS (Unified Diagnostic Services, ISO 14229), which remains the diagnostic service layer used for tasks like ECU identification, reading trouble codes, running routines, and ECU programming. It changes how that UDS traffic gets transported instead of moving over CAN or K-Line, it moves over IP.
The Three Parts of the ISO 13400 Standard
| Standard Part | What It Covers |
|---|---|
| ISO 13400-1 | General information and use case definitions the scenarios the standard is designed to support |
| ISO 13400-2 | Transport protocol and network layer services defines discovery, message framing, and routing activation |
| ISO 13400-3 | Data link layer requirements the physical Ethernet-based connection layer |
How the Communication Actually Works
- Discovery: handled using UDP, allowing a diagnostic client to identify a vehicle and its diagnostic nodes on the network
- Diagnostic payload exchange: handled using TCP, once a route has been established
- Routing activation: a required step that activates and confirms the diagnostic route before any diagnostic messages are exchanged
- Logical addressing: allows a diagnostic client to address a specific ECU or functional group through the primary gateway, rather than broadcasting to the whole network
An IP-based diagnostic server is typically built into an ECU, and it responds to requests from a client usually an external diagnostic tool, though the standard also allows for on-board test devices. A single vehicle can contain multiple networked entities across different network configurations, all reachable through the same gateway architecture.
Why This Design Exists
ISO 13400's stated intent is to describe a standardized vehicle interface that separates in-vehicle network technology from the diagnostic client's connection requirements, providing a long-term stable external communication interface regardless of what's changed inside the vehicle's own network architecture. This matters because it lets automakers evolve their internal vehicle networks without breaking the diagnostic interface external tools rely on, and it allows the same standard to serve both legislated diagnostic requirements and manufacturer-specific use cases.
Why DoIP Matters More With Each Model Year
- Faster data transfer: Ethernet-based communication moves significantly more data per second than legacy CAN, which matters directly for ECU flashing, variant coding, and large calibration file transfers.
- Gateway routing: an Ethernet gateway routes UDS requests to individual ECUs, many of which still sit on CAN or other legacy in-vehicle buses this means the protocol doesn't require every ECU in the vehicle to run its own IP stack, only the gateway.
- Scales with vehicle complexity: as vehicles add more control units and more data-heavy features, IP-based transport avoids the bottlenecks that increasingly show up on CAN-based architectures under heavier diagnostic and programming workloads.
What This Means for Diagnostic Hardware
Not every interface that claims DoIP compatibility is built to the full ISO 13400 specification. A device that establishes a basic connection but doesn't correctly implement routing activation or logical addressing can appear to work while failing to reach specific modules which is a worse outcome than an outright connection failure, since it isn't obvious until a specific job needs that missing coverage. Confirming genuine ISO 13400 certification, rather than assuming compatibility from a product description, is worth doing before relying on an interface for programming work on current-generation vehicles.
Frequently Asked Questions
Does DoIP replace CAN entirely inside the vehicle?
No. Many ECUs remain on CAN or other legacy buses internally the central gateway bridges external IP-based diagnostic traffic to those internal networks, rather than requiring every module to run IP directly.
Is the new standard only relevant for ECU programming, or does it affect basic diagnostics too?
It affects both. DoIP is the transport layer for all UDS-based communication on supported vehicles, including routine fault code reading, not only programming-specific sessions though the speed benefit is most noticeable on larger data transfers like flashing.
Can an older CAN-only interface be updated to support Ethernet diagnostics through a firmware update?
Generally no, since the technology requires Ethernet-based hardware at the physical layer (ISO 13400-3), which a CAN-only device doesn't have. IP-based diagnostic support is a hardware requirement, not purely a software one.
For brand-specific detail on where the new architecture applies, our JLR DoIP guide covers a real-world implementation in depth. Browse the full diagnostic tools range for DoIP-capable interfaces across supported brands.