ISO 13400-2:2019
(Main)Road vehicles — Diagnostic communication over Internet Protocol (DoIP) — Part 2: Transport protocol and network layer services
Road vehicles — Diagnostic communication over Internet Protocol (DoIP) — Part 2: Transport protocol and network layer services
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.
Véhicules routiers — Communication de diagnostic au travers du protocole internet (DoIP) — Partie 2: Protocole de transport et services de la couche réseau
General Information
Relations
Buy Standard
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 13400-2
Second edition
2019-12
Road vehicles — Diagnostic
communication over Internet Protocol
(DoIP) —
Part 2:
Transport protocol and network layer
services
Véhicules routiers — Communication de diagnostic au travers du
protocole internet (DoIP) —
Partie 2: Protocole de transport et services de la couche réseau
Reference number
©
ISO 2019
© ISO 2019
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2019 – All rights reserved
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
4 Symbols and abbreviated terms . 4
4.1 Symbols . 4
4.2 Abbreviated terms . 4
5 Conformance . 6
6 DoIP introduction . 6
6.1 General information . 6
6.2 Connection establishment and vehicle discovery . 6
6.2.1 Direct connection scenario . 6
6.2.2 Network connection scenario . 7
6.2.3 Internal tester scenario (optional) . 8
6.2.4 Unsecured DoIP session . 8
6.2.5 Secured (TLS) DoIP session.10
6.3 Vehicle network integration .11
6.3.1 Vehicle identification .11
6.3.2 Multiple vehicles in a single network.12
6.4 Communication examples using message sequence charts .13
6.5 IP-based vehicle communication protocol — General information .14
7 Application (APP) requirements .14
7.1 APP implementation of DoIP requirements .14
7.2 APP data transmission order .14
7.3 APP DoIP entity synchronization of a vehicle's GID.14
7.4 APP vehicle identification and announcement request message .17
7.5 APP diagnostic power mode information request and response .24
7.6 APP DoIP entity status information request and response .25
7.7 APP timing and communication parameters .25
7.8 APP logical addressing .26
7.9 APP communication environments and recommended timings .27
7.10 APP DoIP entity functional requirements .28
8 Service interface .28
8.1 General .28
8.2 Service primitive parameters (SPP) .30
8.2.1 SPP data type definitions .30
8.2.2 SPP DoIP_AI, address information .30
8.2.3 SPP Length, length of PDU .31
8.2.4 SPP PDU, protocol data unit .31
8.2.5 SPP DoIP_Result.31
8.3 SPP DoIP layer service interface .31
8.3.1 SPP DoIP_Data.request .31
8.3.2 SPP DoIP_Data.confirm.32
8.3.3 SPP DoIP_Data.indication .32
9 Application layer (AL) .32
9.1 AL dynamic host control protocol (DHCP).32
9.1.1 AL general .32
9.1.2 AL IP address assignment .34
9.1.3 AL IP address validity and renewal .37
9.2 AL generic DoIP protocol message structure .38
9.3 AL handling of UDP packets and TCP data .43
9.4 AL supported payload types over TCP and UDP ports .43
9.5 AL diagnostic message and diagnostic message acknowledgement .44
9.6 AL alive check request and alive check response .49
10 Transport layer security (TLS) .50
10.1 TLS secure diagnostic communication .50
10.2 TLS DoIP application profile .52
10.2.1 TLS general .52
10.2.2 TLS accepted TLS versions for DoIP .52
10.2.3 TLS accepted cipher suites .52
10.2.4 TLS accepted TLS extensions .53
11 Transport layer (TL) .54
11.1 TL transmission control protocol (TCP) .54
11.2 TL user datagram protocol (UDP) .57
11.3 TL handling of UDP messages .61
12 Network layer (NL) .61
12.1 NL internet protocol (IP) .61
12.2 NL IPv4 address resolution protocol (ARP).61
12.3 NL IPv6 neighbour discovery protocol (NDP) .62
12.4 NL internet control message protocol (ICMP) .62
12.5 NL IP-based vehicle communication protocol .63
12.6 NL socket handling .68
12.6.1 NL connection states .68
12.6.2 NL general inactivity timer .70
12.6.3 NL initial inactivity timer .71
12.6.4 NL socket handler and alive check .72
13 Data link layer (DLL) .
...
INTERNATIONAL ISO
STANDARD 13400-2
Second edition
2019-12
Road vehicles — Diagnostic
communication over Internet Protocol
(DoIP) —
Part 2:
Transport protocol and network layer
services
Véhicules routiers — Communication de diagnostic au travers du
protocole internet (DoIP) —
Partie 2: Protocole de transport et services de la couche réseau
Reference number
©
ISO 2019
© ISO 2019
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2019 – All rights reserved
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
4 Symbols and abbreviated terms . 4
4.1 Symbols . 4
4.2 Abbreviated terms . 4
5 Conformance . 6
6 DoIP introduction . 6
6.1 General information . 6
6.2 Connection establishment and vehicle discovery . 6
6.2.1 Direct connection scenario . 6
6.2.2 Network connection scenario . 7
6.2.3 Internal tester scenario (optional) . 8
6.2.4 Unsecured DoIP session . 8
6.2.5 Secured (TLS) DoIP session.10
6.3 Vehicle network integration .11
6.3.1 Vehicle identification .11
6.3.2 Multiple vehicles in a single network.12
6.4 Communication examples using message sequence charts .13
6.5 IP-based vehicle communication protocol — General information .14
7 Application (APP) requirements .14
7.1 APP implementation of DoIP requirements .14
7.2 APP data transmission order .14
7.3 APP DoIP entity synchronization of a vehicle's GID.14
7.4 APP vehicle identification and announcement request message .17
7.5 APP diagnostic power mode information request and response .24
7.6 APP DoIP entity status information request and response .25
7.7 APP timing and communication parameters .25
7.8 APP logical addressing .26
7.9 APP communication environments and recommended timings .27
7.10 APP DoIP entity functional requirements .28
8 Service interface .28
8.1 General .28
8.2 Service primitive parameters (SPP) .30
8.2.1 SPP data type definitions .30
8.2.2 SPP DoIP_AI, address information .30
8.2.3 SPP Length, length of PDU .31
8.2.4 SPP PDU, protocol data unit .31
8.2.5 SPP DoIP_Result.31
8.3 SPP DoIP layer service interface .31
8.3.1 SPP DoIP_Data.request .31
8.3.2 SPP DoIP_Data.confirm.32
8.3.3 SPP DoIP_Data.indication .32
9 Application layer (AL) .32
9.1 AL dynamic host control protocol (DHCP).32
9.1.1 AL general .32
9.1.2 AL IP address assignment .34
9.1.3 AL IP address validity and renewal .37
9.2 AL generic DoIP protocol message structure .38
9.3 AL handling of UDP packets and TCP data .43
9.4 AL supported payload types over TCP and UDP ports .43
9.5 AL diagnostic message and diagnostic message acknowledgement .44
9.6 AL alive check request and alive check response .49
10 Transport layer security (TLS) .50
10.1 TLS secure diagnostic communication .50
10.2 TLS DoIP application profile .52
10.2.1 TLS general .52
10.2.2 TLS accepted TLS versions for DoIP .52
10.2.3 TLS accepted cipher suites .52
10.2.4 TLS accepted TLS extensions .53
11 Transport layer (TL) .54
11.1 TL transmission control protocol (TCP) .54
11.2 TL user datagram protocol (UDP) .57
11.3 TL handling of UDP messages .61
12 Network layer (NL) .61
12.1 NL internet protocol (IP) .61
12.2 NL IPv4 address resolution protocol (ARP).61
12.3 NL IPv6 neighbour discovery protocol (NDP) .62
12.4 NL internet control message protocol (ICMP) .62
12.5 NL IP-based vehicle communication protocol .63
12.6 NL socket handling .68
12.6.1 NL connection states .68
12.6.2 NL general inactivity timer .70
12.6.3 NL initial inactivity timer .71
12.6.4 NL socket handler and alive check .72
13 Data link layer (DLL) .
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.