GB/T 43258.2-2023Road vehicles - Diagnostic communication over Internet Protocol (DoIP) - Part 2: Transport protocol and network layer services (English PDF)

Foreword

This document is drafted in accordance with the rules provided in GB/T 1.1-2020

Directives for standardization - Part 1.Rules for the structure and drafting of

standardizing documents.

This document is part 2 of GB/T 43258 Road vehicles - Diagnostic communication over

Internet Protocol (DoIP). The following parts have been issued for GB/T 43258.

— Part 2.Transport protocol and network layer services;

— Part 3.Wired vehicle interface based on IEEE 802.3;

— Part 4.Ethernet-based high-speed data link connector.

This document adopts ISO 13400-2.2019 Road vehicles - Diagnostic communication

over Internet Protocol (DoIP) - Part 2.Transport protocol and network layer services

by modification.

The technical differences between this document and ISO 13400-2.2019, and the causes

for these differences are as follows.

— USE the normatively referenced GB 16735 to replace ISO 3779 (see Table 4 and

Table 5), to adapt to the technical conditions in China and to improve operability;

— ADD the symbol < k> (see 4.1), to improve the usability of the document;

— ADD the abbreviated terms AutoIP, PDU and OTA, and DELETE the unused

abbreviated term FMI (see 4.2), to improve the usability of the document;

— CHANGE "the DoIP entity has an IP address configured in approximately two

seconds" to "the DoIP entity has an IP address configured in approximately seven

seconds", and CHANGE "an IP address is configured after approximately seven

seconds" to "an IP address is configured after approximately two seconds" (see

9.1.2.2), so that the timing parameters are consistent with those in Table 15;

— CHANGE "node management (××1616)" to "0×××16" (see 9.2), to adapt to the

technical conditions in China and improve the operability;

— CHANGE "Response by the DoIP gateway" to "Response by the DoIP entity" (see

Table 48), to improve the technical application flexibility.

1 Scope

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).

2 Normative references

The following documents are referred to in the text in such a way that some or all of

their content constitutes requirements of this document. For dated references, only the

edition cited applies. For undated references, the latest edition of the referenced

document (including any amendments) applies.

GB/T 9387.1-1998, Information technology - Open systems interconnection-basic

reference model - Part 1.The basic model (idt ISO/IEC 7498-1.1994)

3 Terms and definitions

For the purposes of this document, the terms and definitions given in GB/T 9387.1-

1998 and the following apply.

4 Symbols and abbreviated terms

For the purpose of this document, the following symbols apply.

5 Conformance

This document is based on the conventions discussed in the OSI Service Conventions

(as specified in ISO/IEC 10731) as they apply to diagnostic services.

6 DoIP introduction

In a direct connection scenario with no networking infrastructure, a "crossover"

Ethernet cable is used or Auto-MDI(X) is supported by the Ethernet controller by either

the client DoIP entity or the DoIP entity (server), in order to directly connect the vehicle

to the client DoIP entity.

This subclause gives an example of a sequence by which the external client DoIP entity

may be able to identify and group server DoIP entities of all connected vehicles within

a network.

7 Application (APP) requirements

A group identification (GID) is a decentralized approach for identifying multiple DoIP

entities within one vehicle. This implies that there is a VIN/GID master (e.g., the DoIP

edge node) from which all other DoIP entities receive the VIN/GID during a

synchronization process.

8 Service interface

All transport layer services have the same general structure. To define the services, three

types of service primitive are specified.

9 Application layer (AL)

Depending on whether a DoIP entity is in an infrastructure environment or whether it

operates in a direct peer to peer connection, IP addresses need to be assigned taking into

consideration the specifics of IPv4.This subclause describes how an IP address can be

configured in a minimum of time, to ensure fast connection establishment.

......