Report Charging Profiles

Source: OCPP 2.0.1 Part 2 — Specification (Edition 2, 2022-12-15) — Section 1.43 (Messages); Use Case K09 — Get Charging Profiles (Functional Block K. SmartCharging)

Overview

After the CSMS sends GetChargingProfilesRequest, the Charging Station reports the matching installed charging profiles using one or more ReportChargingProfilesRequest messages. The report can be split — for instance because charging profiles for different sources need to be reported, or because there is too much data for one message.

Each message carries a chargingLimitSource (so different sources are reported in separate messages), an evseId, the list of chargingProfile[], and a tbc flag.

requestId SHALL match the requestId from the originating GetChargingProfilesRequest.

Sequence Diagram

Charging Station  ──── ReportChargingProfilesRequest ────▶  CSMS
                       (requestId, chargingLimitSource, tbc?, evseId, chargingProfile[])
Charging Station  ◀─── ReportChargingProfilesResponse ────  CSMS

(repeated until tbc = false)

Initiator

Charging Station → CSMS

Fields

Examples

{
  "requestId": 99,
  "chargingLimitSource": "CSO",
  "evseId": 1,
  "tbc": false,
  "chargingProfile": [
    {
      "id": 100,
      "stackLevel": 0,
      "chargingProfilePurpose": "TxProfile",
      "chargingProfileKind": "Absolute",
      "transactionId": "tx-1234",
      "chargingSchedule": [
        {
          "id": 1,
          "chargingRateUnit": "W",
          "chargingSchedulePeriod": [
            { "startPeriod": 0,    "limit": 11000.0 },
            { "startPeriod": 1800, "limit": 7400.0  }
          ]
        }
      ]
    }
  ]
}

{}

Schema

Source: schemas/ReportChargingProfilesRequest.json, schemas/ReportChargingProfilesResponse.json (OCPP 2.0.1 FINAL)