Skip to content
Documentation Menu

OCPP 1.6 Actions

Full reference for every OCPP 1.6 message, one page each.

Core Profile

  • Boot Notification — After start-up, a Charge Point SHALL send a request to the Central System with information about its configuration (e.g. version, vendor, etc.). The Central System SHALL respond to indicate whether…
  • Authorize — Before the owner of an electric vehicle can start or stop charging, the Charge Point has to authorize the operation. The Charge Point SHALL only supply energy after authorization. When stopping a T…
  • Start Transaction — The Charge Point SHALL send a StartTransaction.req PDU to the Central System to inform about a transaction that has been started. If this transaction ends a reservation (see Reserve Now operation)…
  • Stop Transaction — When a transaction is stopped, the Charge Point SHALL send a StopTransaction.req PDU, notifying the Central System that the transaction has stopped.
  • Meter Values — A Charge Point MAY sample the energy meter or other sensor/transducer hardware to provide extra information about its meter values. It is up to the Charge Point to decide when it will send meter va…
  • Heartbeat — To let the Central System know that a Charge Point is still connected, a Charge Point sends a heartbeat after a configurable time interval.
  • Status Notification — A Charge Point sends a notification to the Central System to inform the Central System about a status change or an error within the Charge Point.
  • Data Transfer (Charge Point → Central System) — If a Charge Point needs to send information to the Central System for a function not supported by OCPP, it SHALL use the DataTransfer.req PDU.
  • Change Availability — Central System can request a Charge Point to change its availability. A Charge Point is considered available (operative) when it is charging or ready for charging. A Charge Point is considered unav…
  • Change Configuration — Central System can request a Charge Point to change configuration parameters. To achieve this, Central System SHALL send a ChangeConfiguration.req. This request contains a key-value pair, where key…
  • Get Configuration — To retrieve the value of configuration settings, the Central System SHALL send a GetConfiguration.req PDU to the Charge Point.
  • Clear Cache — Central System can request a Charge Point to clear its Authorization Cache. The Central System SHALL send a ClearCache.req PDU for clearing the Charge Point's Authorization Cache.
  • Remote Start Transaction — Central System can request a Charge Point to start a transaction by sending a RemoteStartTransaction.req. Upon receipt, the Charge Point SHALL reply with RemoteStartTransaction.conf and a status in…
  • Remote Stop Transaction — Central System can request a Charge Point to stop a transaction by sending a RemoteStopTransaction.req to the Charge Point with the identifier of the transaction. Charge Point SHALL reply with Remo…
  • Reset — The Central System SHALL send a Reset.req PDU for requesting a Charge Point to reset itself. The Central System can request a hard or a soft reset. Upon receipt of a Reset.req PDU, the Charge Point…
  • Unlock Connector — Central System can request a Charge Point to unlock a connector. To do so, the Central System SHALL send an UnlockConnector.req PDU.

Firmware Management Profile

  • Update Firmware — Central System can notify a Charge Point that it needs to update its firmware. The Central System SHALL send an UpdateFirmware.req PDU to instruct the Charge Point to install new firmware. The PDU…
  • Firmware Status Notification — A Charge Point sends notifications to inform the Central System about the progress of the firmware update. The Charge Point SHALL send a FirmwareStatusNotification.req PDU for informing the Central…
  • Get Diagnostics — Central System can request a Charge Point for diagnostic information. The Central System SHALL send a GetDiagnostics.req PDU for getting diagnostic information of a Charge Point with a location whe…
  • Diagnostics Status Notification — Charge Point sends a notification to inform the Central System about the status of a diagnostics upload.

Local Authorization List Management Profile

  • Send Local List — Central System can send a Local Authorization List that a Charge Point can use for authorization of idTags. The list MAY be either a full list to replace the current list in the Charge Point or it…
  • Get Local List Version — In order to support synchronisation of the Local Authorization List, Central System can request a Charge Point for the version number of the Local Authorization List. The Central System SHALL send…

Reservation Profile

  • Reserve Now — A Central System can issue a ReserveNow.req to a Charge Point to reserve a connector for use by a specific idTag.
  • Cancel Reservation — To cancel a reservation the Central System SHALL send a CancelReservation.req PDU to the Charge Point.

Smart Charging Profile

  • Set Charging Profile — A Central System can send a SetChargingProfile.req to a Charge Point, to set a charging profile, in the following situations:
  • Clear Charging Profile — If the Central System wishes to clear some or all of the charging profiles that were previously sent to the Charge Point, it SHALL use the ClearChargingProfile.req PDU.
  • Get Composite Schedule — The Central System MAY request the Charge Point to report the Composite Charging Schedule by sending a GetCompositeSchedule.req PDU. The reported schedule, in the GetCompositeSchedule.conf PDU, is…

Remote Trigger Profile

  • Trigger Message — During normal operation, the Charge Point informs the Central System of its state and any relevant occurrences. If there is nothing to report the Charge Point will send at least a heartbeat at a pr…

Security Extensions

  • Extended Trigger Message — ExtendedTriggerMessage is the OCPP 2.0.1 TriggerMessage ported back into OCPP 1.6 security extension. It was renamed from TriggerMessage because the original name conflicts with the OCPP 1.6 messag…
  • Sign Certificate — The Charge Point uses SignCertificate.req to request that the Certificate Authority sign its public key into a Charge Point certificate. The Charge Point sends the public key in the form of a Certi…
  • Certificate Signed — CertificateSigned.req is sent by the Central System to the Charge Point to deliver a Charge Point client-side certificate that has been signed by a Certificate Authority. It is used in both certifi…
  • Install Certificate — The Central System uses InstallCertificate.req to install a new root/CA certificate (Central System Root or Manufacturer Root) into the Charge Point's trust store. This is not for installing the Ch…
  • Delete Certificate — To facilitate the management of the Charge Point's installed certificates, the Central System can request the Charge Point to delete a specific installed certificate by sending a DeleteCertificate…
  • Get Installed Certificate Ids — To facilitate the management of the Charge Point's installed certificates, the Central System can request the Charge Point to send a list of installed certificates of a given type by sending a GetI…
  • Signed Update Firmware — The Central System uses SignedUpdateFirmware.req to instruct the Charge Point to download and install a digitally-signed firmware image. This message is the OCPP 2.0.1 UpdateFirmware ported into OC…
  • Signed Firmware Status Notification — The Charge Point uses SignedFirmwareStatusNotification.req to inform the Central System about the progress of a secure firmware update started by SignedUpdateFirmware.req. This message is the OCPP…
  • Get Log — The Central System can request a Charge Point to upload a log file (security log or diagnostics log) to a given location. The format of the log file is not prescribed.
  • Log Status Notification — The Charge Point uses LogStatusNotification.req to inform the Central System about the progress of a log file upload that was started by GetLog.req. The CP sends one or more notifications during th…
  • Security Event Notification — The Charge Point uses SecurityEventNotification.req to immediately inform the Central System of changes in system security. The Central System acknowledges receipt with SecurityEventNotification.conf.