Skip to content

DoIP

Diagnostics over IP transports diagnostic communication across IP networks, often for Ethernet-based vehicle diagnostics.

Status Examples Runtime example Source posture
draft-structure-only synthetic/passive docs-only atlas metadata plus public/tooling cross-checks

Identity

Diagnostics over IP transports diagnostic communication across IP networks, often for Ethernet-based vehicle diagnostics.

What This Protocol Teaches

  • Once the car has Ethernet, diagnostics start looking like enterprise software with sharper edges.
  • It teaches how to inspect vehicle announcement, routing activation, diagnostic message encapsulation without mistaking field extraction for meaning.
  • It keeps observer inference separate from system truth.

Operational Context

DoIP / ISO 13400 appears in automotive, diagnostics contexts and is modeled in the atlas at the transport, network, application layer(s). The binder treats it as an inspection surface: what evidence appears, what timing matters, and what outside authority is required before assigning meaning.

Draft status

draft-structure-only: this is not yet a final-copy binder page. It has an atlas-grounded teaching hook and source notes, but still needs a stronger worked trace, page-specific ambiguity case, and reviewer-validated visual before promotion.

A Concrete Artifact

# synthetic DoIP diagnostic message summary
TCP 192.0.2.10:13400 -> 192.0.2.20:49152  payload: 22 f1 90

Synthetic

Synthetic offline sample for explanation; not a real operational trace or live-system instruction.

Worked Decode

  1. Read the line as an already-observed TCP payload summary, not a connection recipe.
  2. 192.0.2.10 and 192.0.2.20 are documentation-network addresses used as synthetic endpoints.
  3. Port 13400 is protocol-shape context; it does not authorize live diagnostic discovery or routing.
  4. 22 f1 90 is diagnostic payload evidence whose DID meaning belongs to UDS and vehicle authority.

Field Layout / Anatomy

Element Shape Inspection meaning
vehicle announcement artifact-specific evidence Inspect with timing and source context before naming meaning.
routing activation artifact-specific evidence Inspect with timing and source context before naming meaning.
diagnostic message encapsulation artifact-specific evidence Inspect with timing and source context before naming meaning.
TCP/UDP roles artifact-specific evidence Inspect with timing and source context before naming meaning.
semantic authority external source Dictionary, profile, map, or integration document that turns evidence into named meaning.
timing context cadence / gap / slot / timestamp Freshness and ordering evidence for observer reconstruction.

Visual Model

sequenceDiagram participant Initiator participant Bus participant Responder Initiator->>Bus: synthetic request or scheduled evidence Bus->>Responder: framed artifact Responder-->>Bus: response or periodic value Bus-->>Initiator: observed result

Timing And Authority

An offline record can establish ordering among visible DoIP headers and diagnostic payloads. Network timing, retries, and paired responses may support a transaction hypothesis, but they do not prove routing state, endpoint ownership, or ECU health.

Semantic authority

DoIP defines transport framing, not the vehicle-specific meaning of a diagnostic payload. Interpreting a DID or routine still requires UDS semantics plus the correct vehicle or ECU catalog; an IP address is not that authority.

Failure And Ambiguity

  • IP endpoints in an offline record do not prove ECU identity.
  • Diagnostic payload bytes need UDS and vehicle authority before DID meaning.
  • Routing-activation and live discovery workflows are outside this passive page.

Observer Lesson

A passive observer can correlate visible DoIP payload types, logical addresses, and synthetic diagnostic exchanges. It cannot establish live routing activation, endpoint identity, diagnostic authorization, or physical state.

Python Model

No current runtime example is claimed for this draft page. Keep reader claims at the artifact and source level until a separate implementation plan adds a tested model.

Local Teaching Notes

Simplification

The artifact and diagrams are synthetic teaching material. The page intentionally omits conformance timing tables, electrical design detail, proprietary configuration, and exhaustive standard behavior.

Source Confidence

Source confidence is high for scope and terminology, with semantic claims limited to public metadata, public source notes, and synthetic teaching artifacts.

Source Notes

Field Value
Governance tier Tier 2 Field Note
Canonical source status yes
Public explainer status yes
Open-source tool status yes
Sample-data status none listed; use synthetic teaching artifacts
Confidence high
Citation specificity document-metadata-level
Canonical source(s) ISO 13400-2 Diagnostic communication over Internet Protocol (DoIP) (ISO; ISO 13400-2:2019; paywalled; metadata-only)
Public explainer/tooling source(s) DoIP overview (Softing Automotive; public-web; link-only)
Open-source tool references Scapy automotive layers: automotive layer structure and packet inspection docs
Wireshark: Protocol dissectors and PCAP analysis

References

Public Sources