ISO 15118-2:2014 道路車両— Vehicle-to-Grid通信インターフェース—パート2：ネットワークおよびアプリケーションプロトコルの要件 | ページ 6

3.1

Basic Charging

BC

charging phase during a charging session controlled by IEC 61851-1 only

3.2

charging limits

set of physical constraints (e.g. voltage, current, energy, power) that is negotiated during a V2G Communication Session for a charging session

3.3

Communication Setup Timer

Timer monitoring the time from plug-in until the Session Setup message

3.4

Contract Certificate

certificate issued to EVCC either by V2G Root CA or by Sub-CA, which is used in XML Signatures in application layer so that SECC or secondary actor can verify the Contract issued to the EVCC and signatures issued by the EVCC

3.5

CP State

Control Pilot (Vehicle) State according to IEC 61851-1 signalled on Control Pilot Line

3.6

credentials

anything that provides the basis for confidence, belief, credit, etc.

3.7

Data Link Setup

setup phase for establishing the data link

Note 1 to entry: Entry Condition: Any valid control pilot signal according to IEC 61851-1; Exit Condition: D-LINK_READY.indication(DLINKSTATUS=LinkEstablished).

3.8

Distinguished Encoding Rules = ASN-1 encoding rule

DER

method for encoding a data object, such as an X.509 certificate, to be digitally signed or to have its signature verified

3.9

global address

IP address with unlimited scope

3.10

High Level Communication Charging

HLC-C

charging phase during a charging session controlled by ISO 15118

3.11

link-local address

IP address with link-only scope that can be used to reach neighbouring interfaces attached to the same link

3.12

Identification Mode

mandatory and optional messages and parameters with respect to charging scenarios using External Identification Means (EIM) and charging scenarios using Plug and Charge (PnC) for identification

Note 1 to entry: An Identification Mode covers a set of similar charging scenarios for a specific identification means.

3.13

(IP) address

IP-layer identifier for an interface or a set of interfaces

3.14

Maximum Transfer Unit

MTU

maximum size (in bytes) of the largest protocol data unit that the Data Link Layer that can be pass onwards

3.15

Message Set

set of mandatory V2G messages and parameters for the EVCC or SECC covering one or multiple use case elements

3.16

Message Timer

Timer monitoring the exchange of a Request-Response-Pair

3.17

network segment

collection of devices that can exchange data on Data Link Layer level directly via Data Link Addresses

3.18

node

device that implements IPv6

3.19

OEM Provisioning Certificate

certificate issued to the EVCC, so that a Contract Certificate can be securely requested and received from a secondary actor

3.20

Performance Time

non-functional timing requirement defining the time a V2G Entity shall not exceed when executing or processing certain functionality

Note 1 to entry: This is a fixed time value.

3.21

private environment

area with (physical) access limited to a small number of vehicles (EVs), which may be a private parking garage or a garage/ parking lot of a company with its own EV fleet ここで, one or several private wall-box(es) are used instead of public charging stations as EVSE, and where in order to keep the private wall-box simple and cheap in production and operation it is allowed to stay offline permanently, which allows a private wall-box to use leaf certificates with a longer maximum validity than allowed for public charging stations and using a private root certificate which is different to the V2G root certificates and which has to be installed into each EV that is allowed to charge within this specific private environment, resulting in a limited number of EVs belonging to one private environment, the difference to a “trusted environment” being that in a (pure; i.e. not additionally “trusted”) private environment TLS and the corresponding data encryption at connection level is always used, and solely certificate handling is simplified for the private wall-box (EVSE) since it may stay offline permanently, resulting in unrestricted certificate validity periods, shorter certificate chain length, omitting OCSP, and an additional “pairing mode”

3.22

Identification Mode

group of mandatory and optional Message Sets covering a set of similar charging scenarios for a specific identification means

3.23

renegotiation

messaging for updating the agreement on the charging schedule between EV and EVSE during a V2G Communication Session by retransmitting the parameters SASchedule and ChargingProfile

3.24

Request-Response Message Pair

request message and the corresponding response message

3.25

Request-Response Message Sequence

predefined sequence of Request-Response Message Pairs

3.26

SDP Client

V2G Entity that uses the SDP server to get configuration information about the SECC to be able to access the SECC

3.27

SDP Server

V2G Entity providing configuration information for accessing the SECC

3.28

SECC Certificate

certificate issued to SECC either by V2G Root CA or by Sub-CA, which is used in TLS so that the EVCC can verify the authenticity of the SECC

3.29

Sequence Timer

Timer monitoring a Request-Response Message Sequence

3.30

Sub-CA

subordinate certificate authority who issues SECC Certificates and/or Contract Certificates on behalf of the V2G Root CA

Note 1 to entry: The ability of issuing the certificates are delegated from V2G Root CA, and V2G Root CA can revoke the Sub-CA at any time.

3.31

Sub-CA Certificate

certificate issued to Sub-CA

3.32

TCP_DATA

socket/interface for data transfer based on TCP connection

3.33

Timeout

timing requirement defining the time a V2G Entity monitors the communication system for a certain event to occur

Note 1 to entry: If the specified time is exceeded the respective V2G Entity initiates the related error handling. This is a fixed time value.

3.34

Timer

device or piece of software used in an implementation for measuring time.

Note 1 to entry: Depending on the specific use case a timer is used to trigger certain system events as well.

3.35

Trusted Environment

closed user group (e. g. members of car sharing system) with some pre-distributed token for access to the SECC charging service (e.g. key to home garage, RFID token for car sharing), which is something where a person or instance is responsible for, for example (not limited to) a person with its home garage, a car sharing operator or a taxi operator

3.36

V2G Charging Loop

V2G messaging phase for controlling the charging process by ISO 15118

3.37

V2G Communication Session

association of two specific V2G Entities for exchanging V2G messages

3.38

V2G Entity

primary actor participating in the V2G communication using a mandatory or optional transmission protocol defined by ISO 15118-2

3.39

V2G Message

message exchanged on application layer

Note 1 to entry: Refer to Clause 8 Application Layer messages.

3.40

V2G Setup

setup phase for V2G messaging

Note 1 to entry: Entry Condition: D-LINK_READY.indication(DLINKSTATUS=LinkEstablished); Exit Condition: PowerDeliveryReq with ChargeProgress equals Start or Stop.

3.41

V2G Transfer Protocol

communication protocol to transfer V2G messages between two V2GTP entities

3.42

V2GTP Entity

V2G Entity supporting the V2G Transfer Protocol

3.43

V2G Root CA

certificate Authority (CA) who issues Contract Certificates and/or SECC Certificates, or who delegates ability to issue such Certificates to Sub-CA

3.44

V2G Root Certificate

certificate issued to V2G Root CA