Energy metering and signed meter values
Where the meter sits in AC and DC chargers, how its readings travel in ISO 15118, and how signed meter values, German calibration law, OCMF and transparency software let a customer check a bill.
AC and DC meters
| AC charger | DC charger | |
|---|---|---|
| Where | In the supply path to the outlet or cable | At the DC output, after the power modules |
| What it measures | Active energy per phase | DC voltage times DC current |
| EU approval | MID (Directive 2014/32/EU, annex MI-003) | Not covered by MID; national rules apply |
| Losses it must handle | Small, the cable is short and switched by the car | Cable loss at high current: the reading is corrected to the point of transfer |
| Typical source of the reading in a capture | ChargingStatusRes | CurrentDemandRes, or DC_ChargeLoopRes in ISO 15118-20 |
Measuring on the DC side counts only what reaches the car. A meter on the AC input of a DC charger would bill the customer for the conversion losses, which is why calibration law in Germany asks for DC metering at public DC chargers.
DC meters are approved in Germany under national rules (PTB requirements and the VDE application rule for DC meters) and are covered internationally by IEC 62053-41. Check the current approval path for the market you test for.
MeterInfo in ISO 15118
- ISO 15118-2:
MeterInfois optional inChargingStatusRes(AC) andCurrentDemandRes(DC). It holdsMeterID,MeterReadingin Wh,SigMeterReading(a signature of up to 64 bytes),MeterStatusandTMeter(a timestamp). - With
ReceiptRequiredset, the car answers with aMeteringReceiptReqthat repeats the meter data and is signed with its contract key in Plug and Charge. SQ-10 checks that the receipt is sent. - DIN SPEC 70121 is used for DC, and its DC loop carries no meter information:
CurrentDemandReshas noMeterInfo. Its schema keepsMeterInfoonly in the AC messagesChargingStatusResandMeteringReceiptReq, which a DC session does not send. - ISO 15118-20: the car sets
MeterInfoRequestedin the charge loop request and the charger answers withMeterInfo, which counts charged energy (ChargedEnergyReadingWh) and, in a bidirectional session, discharged energy (BPT_DischargedEnergyReadingWh) separately. The signature field isMeterSignature. - CHAdeMO does not carry meter values to the car. GB/T 27930 reports the delivered energy in the charger's statistics message at the end.
PW-04 checks that the reading never goes backwards within a session. A meter that runs back breaks the receipt and, where calibration law applies, the bill. A reading that restarts at zero in a new session is fine; within one session it is a fault, typically a controller that reads the wrong register or a meter that rebooted.
PW-06 does the same for what the charger tells its backend: with an OCPP log loaded, meterStart, the energy register in MeterValues or TransactionEvent, and meterStop of each connector must never go down. The backend bills the difference, so a reading that goes back bills a wrong amount even when the meter itself is right.
In practice most chargers send no SigMeterReading to the car, even when their meter signs its readings for the backend. The car cannot verify a legal reading on its own; the check a customer relies on is the one described below.
Calibration law in Germany
Charging billed by energy is a measurement in trade, so the German calibration law (Mess- und Eichgesetz and Mess- und Eichverordnung, commonly called Eichrecht) applies to public chargers. The key ideas:
- The measuring system is the whole charge point, not only the meter: the type examination covers the meter, the display, the software that handles the readings and the way they reach the bill.
- Each legally relevant reading is signed inside a protected unit (the meter or a signing module) with a private key that never leaves it. The matching public key is printed on the charger or shown on its display.
- At least the readings at the start and end of a session, with time and the identification of the session, are signed and sent to the backend, which must pass them to the customer with the bill.
- Transparency software, published by the S.A.F.E. e.V. association and approved for the purpose, lets the customer check that the signed values match the public key and that the energy on the bill follows from them.
The legal details (which requirements of the PTB apply, the role of the conformity assessment body, transition periods for older chargers, and how the rules treat DC cable loss) are summarised here from secondary sources and are to be checked against the current texts.
OCMF
The Open Charge Metering Format of S.A.F.E. e.V. is the most common container for a signed reading in Europe. It is plain text in three parts separated by a vertical bar: the word OCMF, a JSON payload, and a JSON signature block. An illustrative example (values invented):
OCMF|{"FV":"1.0","GI":"EXAMPLE GW","GS":"0000001","PG":"T12","MV":"Example","MS":"M0001",
"IS":true,"IT":"ISO14443","ID":"1F2E3D4C",
"RD":[{"TM":"2026-09-28T10:15:02,000+0200 S","TX":"B","RV":1234.567,"RI":"1-b:1.8.0","RU":"kWh","ST":"G"}]}
|{"SA":"ECDSA-secp256r1-SHA256","SD":"3045...."}RDholds the readings: time (TM), transaction point (TX, for example B for begin and E for end), value (RV), OBIS register (RI), unit (RU) and status (ST).SAnames the signature algorithm andSDholds the signature.- Between charger and backend the string usually travels in OCPP: in OCPP 2.0.1 as
signedMeterDataof aSignedMeterValue, next tosigningMethod,encodingMethodandpublicKey; in OCPP 1.6 by vendor specific means.
Field names and transaction codes are given as commonly used in OCMF and are to be checked against the published OCMF specification version the meter claims in FV.
Other markets
- European Union: MID covers AC meters. Several member states other than Germany have their own rules for public charging; the Alternative Fuels Infrastructure Regulation (EU) 2023/1804 adds price transparency requirements.
- United States: NIST Handbook 44 has a code for electric vehicle fueling systems, adopted state by state; California runs its own type evaluation programme.
Scope and adoption dates of these rules change; check them for the market and date you test for.
Sources
- ISO 15118-2:2014, MeterInfoType, MeteringReceipt
- ISO 15118-20:2022, MeterInfo in the charge loop, MeterInfoRequested
- Directive 2014/32/EU (MID), Annex MI-003, active electrical energy meters
- German Mess- und Eichgesetz (MessEG) and Mess- und Eichverordnung (MessEV), calibration law
- Open Charge Metering Format (OCMF), S.A.F.E. e.V., published specification
- OCPP 2.0.1, SignedMeterValueType