Notify EV Charging Schedule
Source: OCPP 2.0.1 Part 2 — Specification (Edition 2, 2022-12-15) — Section 1.37 (Messages); Use Case K17 — Renegotiation initiated by EV (Functional Block K. SmartCharging)
Overview
When the EV (via ISO 15118) calculates its own charging schedule and provides it to the Charging Station, the CS forwards that schedule to the CSMS via NotifyEVChargingScheduleRequest. This is typically part of an ISO 15118 renegotiation initiated by the EV.
The CSMS responds with a status indicating whether it could process the message. The response does not imply approval of the schedule.
Sequence Diagram
Charging Station ──── NotifyEVChargingScheduleRequest ────▶ CSMS
(timeBase, evseId, chargingSchedule)
Charging Station ◀─── NotifyEVChargingScheduleResponse ──── CSMS
(status, statusInfo?)
Initiator
Charging Station → CSMS
Fields
| Field Name | Field Type | Card. | Description |
|---|---|---|---|
| timeBase | dateTime | 1..1 | Required. Periods contained in the charging profile are relative to this point in time. |
| evseId | integer (> 0) | 1..1 | Required. The EVSE the schedule applies to. Must be > 0. |
| chargingSchedule | ChargingScheduleType | 1..1 | Required. Planned energy consumption of the EV over time, relative to timeBase. |
| Field Name | Field Type | Card. | Description |
|---|---|---|---|
| status | GenericStatusEnumType | 1..1 | Required. Whether the CSMS processed the message. Does not imply approval of the schedule. |
| statusInfo | StatusInfoType | 0..1 | Optional. Detailed status information. |
Examples
{
"timeBase": "2026-04-27T13:00:00Z",
"evseId": 1,
"chargingSchedule": {
"id": 1,
"chargingRateUnit": "W",
"chargingSchedulePeriod": [
{ "startPeriod": 0, "limit": 11000.0 },
{ "startPeriod": 1800, "limit": 7400.0 }
]
}
}{
"status": "Accepted"
}Schema
Source:
schemas/NotifyEVChargingScheduleRequest.json,schemas/NotifyEVChargingScheduleResponse.json(OCPP 2.0.1 FINAL)