Page 76/95
21January2021/Version 0
LEM International SA
Chemin des Aulx 8
1228 PLAN-LES-OUATES Switzerland
www.lem.com
7.4. Data authenticity
7.4.1. Overview
In the context of metering, data are signed to ensure their authenticity (authentication and integrity).
Signatures secure the following sets of data:
•
/ocmf
certified, billable transaction data structure
•
/legal
LEM proprietary transaction data structure
•
/logbook
buffer
A signature cannot be used alone. The following set of inputs is necessary as a whole:
•
Content to be verified
• Signature for this content
• Associated public key
Once gathered, data authenticity can be verified with the following solutions:
Verifiable data
structure
/ocmf
API
/legal
API
/logbook
API
Description
Transaction data structure,
in certified, billable, OCMF-
compliant format
Transaction data structure, in
LEM proprietary format
Event logbook
Verification solution
OCMF official transparency
software
LEM DCBM verification software
Table 10: Solutions for signatures verification
Verification solutions are given as examples.
•
LEM DCBM verification software is available on LEM website or from LEM support
• OCMF transparency software is available at https://transparenz.software/
!
For
/legal
to be usable for billing in regards to certification, it shall be re-signed by the charger
controller. That is why
/ocmf
shall be preferred for external backup.
7.4.2. Keys specifics
Two unique public keys coexist in each DCBM, to be used according to the dataset to check.
Public key
publicKeyOcmf
publicKey
Allows check of
/ocmf
/legal
,
/logbook
Availability
In
/status
API
On the Meter Unit front face marking
In
/status
API
In
/legal
API
On the display (boot, end of transaction, maintenance screens)
Figure 43: Keys specifics for signature checks
publicKeyOcmf
is composed of an fix RFC5480 header and the
publicKey
i