DoIP

Diagnostic Communication over Internet Protocol

Automotive Data and Connectivity Where is DoIP applied? What is DoIP? Advantages of DoIP

Safety Accessibility Engineering Test Manufacturing Service

• Short and simple: “DoIP is the packaging of diagnostic messages Performant handling of huge data volumes
Internet
in Ethernet frames for communication of a diagnostic tester with a vehicle”
Connected
Office Driver Home Production Test After Sales Test
• DoIP is a standardized diagnostic transport protocol according to Time-saving at ECU Flash Programming
Specification
Why D oIP

ISO 13400
Road Test
• DoIP is used in combination with the standardized diagnostic protocol Cost-efficient because no VCI is necessary
Automotive Connected System Integration
Vehicle
UDS (ISO 14229-5: UDSonIP)
Infrastructure Devices Entertainment
Systems

Service & Functional Test, HiL • Services of UDSonIP are identical to UDSonCAN Simple integration to IT Infrastructure
Diagnostics
• DoIP with Ethernet 100 Base-TX instead of CAN enables substantial
System Development Supplementary to legislative CAN
Efficiency Environment • Vehicle inspection and repair
higher bandwidth Flexible use because of standardized communication
ECU Development
• Measurement reading • Vehicle access with DoIP is backwards compatible using discretionary
• Increasing interconnection of vehicles and their environment • Routing of data from internal pins of the existing diagnostic connector Integrated with other standards for vehicle diagnosis
• Driving assistance and infotainment systems cause huge data volume vehicle buses
• DoIP enables easy integration into various network structures,
• Increasing time for flash programming at production line and after-sales service • Online data streaming
• DoIP as a performant and flexible vehicle access • Flash programming even with WLAN Future-proof technology enables various use cases

DoIP in Combination with other Standards DoIP at the OSI Reference Model The DoIP Standard: ISO 13400 DoIP at D-PDU API Standard
Do IP S t andard Ove r view

Comparison to ISO
OTX (Open Test sequence eXchange) OSI Layer ISO UDS on DoIP
UDS on CAN Part 1 – General information and use case definition Two Use Cases:
Tester Application
• ISO 13209 • With physical module: Real MVCI which supports DoIP protocol
• DoIP extensions in preparation ISO 14229-5 ISO 14229-3 • With virtual modules: Direct access of tester to vehicle (=MVCI)
7: Application Part 2 – Transport protocol and network layer services
UDS on IP UDS on CAN

© 2016 Softing Automotive Electronics GmbH. Despite all due care and attention, Softing accepts no liability and extends no guarantee for the correctness, completeness or currentness of the information.
• Assignment of IP address
MCD-3D API OTX Runtime • Vehicle search
6: Presentation
• ISO 22900-3 MCD-3D API • Link connection
Different combination modes / network topologies:
• ASAM MCD-3D 3.0 required • Status information
MVCI D-Server ISO 14229-2 ISO 14229-2
5: Session • Single tester and single ECU (DoIP Entity)
UDS UDS • Data routing to sub buses
D-PDU API D-PDU API • Message types • Single tester and single vehicle (DoIP Vehicle and DoIP Group)
• ISO 22900-2 KWP UDS proprietary 4: Transport TCP / UDP • Error handling • Single tester and multiple vehicles (DoIP Collection and DoIP Group)
• DoIP specified as amendment ISO 13400-2 ISO 15765-2
DoIP Diag on CAN
• Multiple tester and single / multiple vehicles
DoIP (LAN / WLAN) 3: Network IPv4 / IPv6 Part 3 – Wired vehicle interface based on IEEE 802.3
UDS (Unified Diagnostic Services)
• ISO 14229-5 for DoIP FlexRay BroadR-Reach
Gateway 2: Data Link Part 4 – Ethernet-based high-speed data link connector Specification of vehicle identification (discovery)
CAN IEEE 802.3 ISO 13400-3 ISO 11898
WWH-OBD ECU ECU ECU Ethernet DoIP CAN
Definition of DoIP specific Communication Parameter (ComParams)
• ISO 27145 for DoIP and CAN ECU ECU ECU 1: Physical Part 5 – Conformance test specification Description of DoIP socket and protocol handling
ECU
Vehicle

DoIP Communication Principles DoIP Communication Sequence Message Structure DoIP Vehicle Access
DoIP Co mmun icati on

Diagnostic tester communicates with vehicle via Gateway ECU Tester DoIP Gateway ECU DoIP Message Ethernet pin assignment at OBD connector
• Ethernet Activation Line enables Ethernet port of the Gateway DoIP Payload Data (up to 4 GByte) Option #1
Routing Activation Request
• Gateway is routing the message to sub buses CAN / FlexRay / MOST 1 2 3 4 5 6 7 8

9 10 11 12 13 14 15 16
DoIP
Routing Activation Response Header Diagnostic Services (UDS) Option #2
Link connection
1 2 3 4 5 6 7 8

• Configuration of the Gateway with valid IP address (DHCP) 9 10 11 12 13 14 15 16

Diagnostic Request Diagnostic Request Cable

• Tester sends Vehicle Identification Request (UDP) ISO 15031 signals DoIP signals
(for DoIP via Ethernet)
• Gateway responses with Vehicle Announcement Message (UDP), OEM specific CAN signals

Diagnostic Response Diagnostic Response

contains VIN, Gateway address etc.
Ethernet Frame

Ethernet Payload Data (42 – 1500 Byte)

Diagnostic Request Diagnostic Request
Diagnostic commands
• Routing Activation Request: Command for routing of subsequent diagnostic
Ethernet TCP / UDP DoIP Message /
messages to ECUs behind the Gateway (TCP) Header Header Segment of DoIP Message WLAN-Ethernet Bridge VCI
(for DoIP via WLAN) (for DoIP and CAN)
• Diagnostic communication based on UDS (Unified Diagnostic Services)
Simplified illustration

O r d e r a d d i t i o n a l c o p i e s : i n f o . a u t o m o t i v e @ s o f t i n g . c o m / w w w. a u t o m o t i v e . s o f t i n g . c o m