Since 24.01.2023, a new service is responsible for the processing of charging processes with signed meter values. The advantages of the new service compared to the previous service are:
- The entire transaction is ALWAYS checked for signed readings.
- More detailed information about errors that occurred during the check.
How does the new service work?
The new service checks charging sessions for signed meter values and verifies them using the transparency software. During a charging process, messages such as StartTransaction, MeterValues and StopTransaction are sent to be.ENERGISED via OCPP.
Upon receipt of the StopTransaction, the transaction is verified via the new service using the transparency software. The calculated verification status is then stored accordingly in the database.
What is the transparency software?
With the transparency software, one has the possibility to check digitally signed meter values for their correctness. This is to be able to ensure that the values have not been manipulated by others. More information about the transparency software can be found on the official website of S.A.F.E. under the following link: Transparenzsoftware (safe-ev.de)
Verification in be.ENERGISED
You can see the information about signed meter values and their verification status in the charging process data sheet in be.ENERGISED.
You can access the charging process data sheet of charging processes in be.ENERGISED under Infrastructure/Charging Processes/Charging process list by clicking on the data sheet icon of the respective charging process.
The three possible statuses are VERIFIED (verified), PENDING (still under review) or FAILED (could not be verified). These refer to the entire charging process, recognizable by the text "Verification status VERIFIED/PENDING/FAILED"(formerly "Verification of chargelog: VERIFIED/PENDING/FAILED").
If you move the mouse over the field, you will get additional information regarding the verification of the signed meter values.
- Valid: yes or no
- Additional context: More information about the verification status
- Validator: Transparency software
- Version: Indicates which version of the transparency software was used for validation. The possible versions are currently 1.0, 1.1.0 and 1.2.0 (latest version)
- Checked at: Exact time when the check took place, in the format DD.MM.YYY hh:mm:ss.
- Error codes: Error messages that provide information about the reasons for the validity status.
Is it possible to see via the Export Wizard or via API whether a charging process has been digitally signed?
In a charging process export via the Export Wizard in be.ENERGISED there is the column "SignedValuesURL". In this field, a URL is listed for charging processes with signed meter values, via which you can download the XML file, which you can in turn import into the transparency software. Thus, if a URL is displayed in this field, the charging process contains signed meter values, which can be verified by means of the transparency software.
Via API it is currently not possible to trace whether a charging process has signed meter values.
Which formats for signed meter values can be.ENERGISED process?
The formats that can be processed are identical to those available in the transparency software. These are then converted into a XML file and are available for you to download via be.ENERGISED.
When are the signed meter values of a charging process displayed with the verification status "FAILED"?
A so-called "retry mechanism" is implemented in our system. This means that if the verification initially fails, the system tries to verify the transaction again after five minutes, twelve hours, and twenty-four hours. If these repeated attempts are also unsuccessful, the verification status "FAILED" is issued.
What data must be transmitted by the charging station so that a charging process can be verified?
The "Public Key" must be transmitted in any case. Normally this is transmitted via a "BootNotification" or "DataTrans".
If there are problems with the public key, it can help in individual cases to execute the "GetConfig" command manually.
A "Transaction_End" message must also be present. This is mandatory according to the protocol. In addition, individual "MeterValues" with signed data can also be transmitted. Please note that the representation of these messages may differ from manufacturer to manufacturer.
Version: 2023-01-25 06:57:25 UTC