ISO DIS 13400-2
Road vehicles - Diagnostic communication over Internet Protocol (DoIP) - Part 2: Transport protocol and network layer services
|Publication Date:||15 January 2019|
|ICS Code (Diagnostic, maintenance and test equipment):||43.180|
|ICS Code (Electrical and electronic equipment):||43.040.10|
This document specifies the requirements for secured and unsecured diagnostic communication between client DoIP entity and server(s) installed in the vehicle using Internet Protocol (IP) as well as the transmission control protocol (TCP) and user datagram protocol (UDP). This includes the definition of vehicle gateway requirements (e.g. for integration into an existing computer network) and test equipment (client DoIP entity) requirements (e.g. to detect and establish communication with a vehicle).
This document specifies features that are used to detect a vehicle in a network and enable communication with the vehicle gateway as well as with its sub-components during the various vehicle states. These features are separated into two types: mandatory and optional.
This document specifies the following mandatory features:
- vehicle network integration (IP address assignment);
- vehicle announcement and vehicle discovery;
- vehicle basic status information retrieval (e.g. diagnostic power mode);
- connection establishment (e.g. concurrent communication attempts), connection maintenance and vehicle gateway control;
- data routing to and from the vehicle's sub-components;
- error handling (e.g. physical network disconnect).
This document specifies the following optional features:
- DoIP entity status monitoring;
- transport layer security (TLS);
- DoIP entity firewall capabilities.
This protocol standard is implemented by one or more DoIP entities, depending on the vehicle's network architecture. Figure 2 shows an example of the vehicle network architecture.
In this document, the requirements are assigned a unique number of the form "X.DoIP-yyy", allowing for easier requirement tracking and reference.
- X = OSI layer number; and
- DoIP-yyy = requirement number; and
- xL = x = OSI layer abbrevation[8 = APP, 7 = AL, 6 = PL, 5 = SL, 4 = TL, 3 = NL, 2 = DLL, 1 = PHY, 0 = 240 SPP].
NOTE Requirements in this document are not numbered sequentially because the order of individual requirements changed during document development.
Requirements formulated as "The vehicle shall implement …" imply that all DoIP entities "shall" implement the required functionality if not explicitly stated otherwise. If multiple DoIP entities are present on a vehicle network, implementation details may differ slightly for each DoIP entity (e.g. for identification purposes), so that the client DoIP entity is able to identify the individual DoIP gateways that support this protocol standard.
Where reference is made to RFC documents, note that the forms "shall/shall not" are used to express requirements in these documents.