ISO 13400-2:2019 道路車両—インターネットプロトコル（DoIP）を介した診断通信—パート2：トランスポートプロトコルとネットワーク層サービス | ページ 6

3.1

diagnostic power mode

abstract vehicle internal power supply state, which affects the diagnostic capabilities of all servers on the in-vehicle networks and which identifies the state of all servers of all gateway sub-networks that allow diagnostic communication

Note 1 to entry: The intent is to provide information to the client DoIP entity about whether diagnostics can be performed on the connected vehicle or whether the vehicle needs to be put into a different diagnostic power mode (i.e. technician interaction required). In this document, the following states are relevant: Not Ready (not all servers accessible via DoIP can communicate), Ready (all servers accessible via DoIP can communicate) and Not Supported (the Diagnostic Information Power Mode Information Request message is not supported).

3.2

DoIP edge node

host (3.4) inside the vehicle ここで, an Ethernet activation line in accordance with ISO 13400-3 is terminated and where the link from the first node/host in the external network is terminated

[SOURCE:ISO 13400‑3:2011, 3.1.2, modified — definition editorially revised.]

3.3

DoIP entity certificate

certificate issued by an intermediate CA (3.5) to the DoIP entity presented during the TLS handshake to the client DoIP entity to verify the authenticity of this DoIP entity

3.4

host

node connected to the IP-based network

3.5

intermediate certificate authority

intermediate CA

authority, which issues subordinal certificates to another intermediate CA or DoIP entities

3.6

intermediate certificate

certificate either stored in the client DoIP entity or is presented during authentication together with the end node certificate to complete the chain of trust

3.7

invalid source address

address outside the reserved range for client(s) DoIP entity

3.8

logical address

address identifying a diagnostic application layer entity

3.9

network node

device connected to the IP-based network (e.g. Ethernet) and which communicates using Internet protocol but does not implement the DoIP protocol

Note 1 to entry: Some network nodes might also be connected to a vehicle sub-network (3.14) , but they are not DoIP gateways as they don’t implement the DoIP protocol. Consequently, these network nodes do not interact with (e.g. respond to) DoIP-compliant client DoIP entity.

3.10

root certificate authority

authority, which acts as the root of trust

Note 1 to entry: Typically issues intermediate certificates (3.6) to allow an intermediate CA (3.5) to further submit certificates.

3.11

root certificate

certificate created by the root certificate authority (3.10) and used as the trust anchor

Note 1 to entry: It is securely stored and used by all entities that wants to validate end node certificates (e.g. from the DoIP entity) together with all necessary intermediate certificates (3.6) in the chain of trust.

3.12

socket

unique identification, as defined in IETF RFC 147, to or from which information is transmitted in the network

3.13

unknown source address

address not listed in the connection table entry

3.14

vehicle sub-network

network not directly connected to the IP-based network

Note 1 to entry: Data can only be sent to and from a vehicle sub-network through the connecting DoIP gateway.