OCPP security certificate management

The OCPP protocol is the key standard for realizing communication between charging piles and central management systems. As network security threats become increasingly severe, certificate management has become the core link to ensure communication security. OCPP security certificates are based on the PKI system and adopt the X.509 standard format. They mainly include charging pile certificates, central system certificates, and CA root certificates for identity authentication, data encryption, and tamper prevention.

Can use smart network connection and Bluetooth card swiping

The issuance of certificates is the basis for establishing a secure communication channel, and its process must strictly follow the OCPP protocol specifications:

  • When the charging pile is initialized or the certificate is about to expire, it sends an application to the central system through the CSR (certificate signing request) mechanism. The CSR contains the public key and identity information of the charging pile.
  • After receiving the CSR, the central system forwards it to the internal CA or a third-party trusted CA. After the CA verifies the identity information, it generates a digital certificate containing the public key of the charging pile. The certificate content includes: version number, serial number, signature algorithm, issuer information, validity period, subject information, public key data, and CA signature. The central system sends the certificate to the charging pile through the InstallCertificate message:

OCPP connects central management system and charging stations

After receiving the certificate, the charging pile verifies its signature and validity chain, stores the certificate in the secure storage area, and returns the processing result through InstallCertificateResponse. To ensure the integrity of the certificate trust chain, the charging pile needs to store both the CA certificate and the intermediate certificate. The central system can query the status of the installed certificate through the GetInstalledCertificateIds command to ensure that the certificates at all levels match.

Certificate deletion is an essential part of security lifecycle management and should be triggered in the following scenarios: certificate expiration, private key leakage, device retirement, or protocol upgrade. The central system initiates a deletion request through the DeleteCertificate command:

OCPP security certificate management framework diagram

After receiving the deletion command, the charging pile performs the following operations: verify the command signature and permissions, delete the target certificate from the secure storage area,

erase the certificate-related cache and logs, and return the result through DeleteCertificateResponse. After the deletion operation is completed, the charging pile must record the event log, including the deletion time, certificate serial number, and operation reason. The central system synchronously updates the certificate status library to ensure the consistency of the global certificate status.

The issuance and deletion of OCPP security certificates are the core links to ensure the security of charging networks. By following PKI standards, strictly implementing protocol processes, and strengthening security measures, risks such as man-in-the-middle attacks and identity forgery can be effectively prevented. In the future, with the development of vehicle-network interaction technology, certificate management will be deeply integrated with power trading, identity authentication, and other functions, becoming an important security cornerstone of the energy Internet.

Update cookies preferences

Get a Quick Quote!

x

    Get a Quick Quote!

    x