User's Manual

User Manual VC-EVCC

5.6 Value Added Services

Value Added Services (VAS) are specified as a part of ISO 15118-1 standard. The objective

of VAS is to exchange information between Vehicle (Vehicle Charging Controller Unit) and

SECC (Infrastructure) which is not a part of V2G communication.

The VC-EVCC supports VAS according to the VDV 261 specification [8]. Vehicle to

Infrastructure Communication Protocol (V2ICP) as defined in VDV 261 is used to exchange

this information.

Note

VAS is an optional service and is not mandatory for charging.

5.6.1 Functionality

The communication with the backend server is started if

 TLS communication has been successfully established for V2G Session

 Service ID: 3 was available in ServiceList

 ParameterSet ID: 4 was available in ServiceParameterList with parameter name as

“https” and parameter port as 443

 AuthorizationRes has been received with ResponseCode = OK and EVSEProcessing

= Finished

 VAS Configuration parameters and the TLS certificate are configured correctly

5.6.1.1 HTTP Request

If the above conditions are fulfilled successfully, the VC-EVCC will try to establish a

connection with the backend and will send the HTTP Request. The request contains a

payload with signals encoded in Json format.

5.6.1.2 HTTP Response

The VC-EVCC expects a HTTP Response with Response Code 200 from the backend

with its signals encoded in Json format.

5.6.1.3 Request Response Loop

The request-response loop will continue, and the data exchange will take place between

the vehicle and the backend.

The request-response loop will end if

 V2G Session has ended

 Sending of HTTP Request is not possible

 No response is received from the backend for 3 consecutive HTTP requests.

Once the VAS communication has ended, the reconnection will take place only after a new

V2G session has started.