Open OCPP 1.6

Table of contents

• Open OCPP 1.6
• Table of contents
• Features
  • Key features
  • Supported OCPP feature profiles
  • Supported OCPP configuration keys
  • OCPP security extensions
  • Security profiles
  • Security events
  • Extended trigger messages
  • Certificate management
  • Signed firmware update
  • OCPP ISO15118 PnC extensions
  • Charge Point role
  • Central System role
  • Internal configuration keys
  • Common keys
  • Charge Point keys
  • Central System keys
  • Local Controller keys
• Quick start
  • Charge Point role
  • Configuration interface
  • Event handler interface
  • Charge Point object
  • Central System role
  • Configuration interface
  • Event handler interfaces
  • Central System object

Features

Key features

Open OCPP is composed of the 4 layers defined by the protocol :

• Websockets (Client or Server)
• OCPP-J RPC
• JSON messages serialization/deserialization
• OCPP role (Charge Point, Central System or Local Controller)

As of this version :

• All the messages defined in the OCPP 1.6 edition 2 protocol have been implemented
• All the configuration keys defined in the OCPP 1.6 edition 2 protocol have been implemented for the Charge Point role
• All the messages defined in the OCPP 1.6 security whitepaper edition 2 have been implemented
• All the messages defined in the Using ISO 15118 Plug & Charge with OCPP 1.6 Application Note v1.0 have been implemented

The user application will have to implement some callbacks to provide the data needed by Open OCPP or to handle OCPP events (boot notification, remote start/stop notifications, meter values...).

The persistent data handled by Open OCPP is stored into a single file which is an SQLite database. It contains :

• For Charge Point role :

• Internal configuration

• Persistent data : Central System's registration status, connector state, OCPP transaction related messages when offline, StopTx meter values
• Badge cache and local list
• Smart charging profile
• Logs

• X.509 Certificates

• For Central System or Local Controller role :

• Internal configuration

• Logs

The standard OCPP configuration persistency has to be handled by the user application.

Supported OCPP feature profiles

Supported OCPP configuration keys

The OCPP configuration keys support applies to Charge Point role only.

In the "Owner" column, "S" means that the configuration key behavior is handled by the stack, "U" means that it must handled by the user application.