Get15118EVCertificate
Relays an ISO 15118 certificate installation or update request from the vehicle.
- Version
- OCPP 2.0.1
- Direction
- Charge Point → CSMS
- Functional block
- ISO 15118 Certificate Management
Plug-and-charge requires the vehicle to hold a valid contract certificate. When the vehicle needs one installed or renewed, it produces an exchange the station cannot resolve on its own, and forwards it here.
The station is a relay: it does not interpret the payload.
Request
| Field | Type | Required | Description |
|---|---|---|---|
iso15118SchemaVersion | string | Required | The ISO 15118 schema version in use. |
action | CertificateActionEnumType | Required | Install or Update. |
exiRequest | string | Required | The vehicle's request, EXI-encoded and base64-wrapped. |
json
[2, "19223201", "Get15118EVCertificate", {
"iso15118SchemaVersion": "urn:iso:15118:2:2013:MsgDef",
"action": "Install",
"exiRequest": "gAABAAEBVSTb..."
}]Response
| Field | Type | Required | Description |
|---|---|---|---|
status | Iso15118EVCertificateStatusEnumType | Required | Accepted or Failed. |
exiResponse | string | Required | The response to pass back to the vehicle, EXI-encoded. |
statusInfo | StatusInfoType | Optional | Reason code. |
json
[3, "19223201", {
"status": "Accepted",
"exiResponse": "gAABAAEBVSTc..."
}]Implementation notes
Neither side parses the EXI payload. The station relays it and the CSMS forwards it to the contract certificate pool. Debugging failures here means looking at the 15118 layer, not at OCPP.
Install is for a vehicle with no certificate; Update renews one that exists.