Get15118EVCertificate

CertificateManagement CS->CSMS OCPP 2.0.1

Sent by the Charging Station to retrieve an EV's V2G certificate from the CSMS during ISO 15118 Plug and Charge authentication.

Quick Reference

Required Fields

iso15118SchemaVersion string(50)

ISO 15118 schema version (e.g., urn:iso:15118:2:2013:MsgDef)

action CertificateActionEnumType

Install or Update

exiRequest string(5600)

Base64-encoded EXI request from the EV

Example Payload

{
  "iso15118SchemaVersion": "urn:iso:15118:2:2013:MsgDef",
  "action": "Install",
  "exiRequest": "gA8BAAAAAAAAAA=="
}

Example Full Frame

[
  2,
  "msg-001",
  "Get15118EVCertificate",
  {
    "iso15118SchemaVersion": "urn:iso:15118:2:2013:MsgDef",
    "action": "Install",
    "exiRequest": "gA8BAAAAAAAAAA=="
  }
]

Format: [MessageType, MessageId, Action, Payload]

Open in Builder Go to Validator

Overview

Get15118EVCertificate is part of the ISO 15118 Plug & Charge flow. The Charging Station requests the CSMS to retrieve or install a certificate for the connected EV. This enables automatic authorization without a physical RFID card.

When to Send

When an EV initiates a Plug & Charge session via ISO 15118
When the EV requests a certificate installation or update

Expected Response

status: Accepted or Failed
exiResponse: Base64-encoded EXI response to forward to the EV

Usage Notes

This is an advanced feature requiring full ISO 15118 implementation on both EV and EVSE
The CSMS acts as an intermediary to the V2G PKI infrastructure
exiRequest and exiResponse are binary data encoded as Base64

Testing Tips

Requires a full ISO 15118 test setup — use an EV simulator supporting V2G
Verify the EXI response from the CSMS can be forwarded to the EV successfully

Common Errors

`TypeConstraintViolation`

Cause: action uses an unsupported value

Solution: Use Install or Update

`PropertyConstraintViolation`

Cause: exiRequest exceeds 5600 characters

Solution: Keep the base64-encoded EXI request under 5600 characters