Publish Firmware

Source: OCPP 2.0.1 Part 2 — Specification (Edition 2, 2022-12-15) — Section 1.41 (Messages); Use Case L03 — Publish Firmware file on Local Controller (Functional Block L. FirmwareManagement)

Overview

The CSMS sends PublishFirmwareRequest to a Local Controller (acting as Charging Station in the OCPP topology) instructing it to download a firmware file from a URI and republish it locally — so downstream Charging Stations can fetch the firmware from the Local Controller instead of the public internet.

The Local Controller verifies the file using the MD5 checksum and then makes it available via the URIs reported in subsequent PublishFirmwareStatusNotification messages.

Sequence diagram

1CSMS  ──── PublishFirmwareRequest ────▶  Charging Station (Local Controller)
2            (location, checksum, requestId, retries?, retryInterval?)
3CSMS  ◀─── PublishFirmwareResponse ────  Charging Station (Local Controller)
4            (status, statusInfo?)
5
6(then PublishFirmwareStatusNotificationRequest messages with same requestId)

Initiator

CSMS → Charging Station (Local Controller)

Fields

GenericStatusEnumType values

Accepted, Rejected.

Examples

1{
2  "location": "https://firmware.example.com/cp/2.1.0/firmware.bin",
3  "checksum": "9e107d9d372bb6826bd81d3542a419d6",
4  "requestId": 55,
5  "retries": 3,
6  "retryInterval": 600
7}

Schema

Source: schemas/PublishFirmwareRequest.json, schemas/PublishFirmwareResponse.json (OCPP 2.0.1 FINAL)