Basic implementation of OCPP 2.0
This section is informative.
The OCPP protocol describes a large number of use cases and messages, which are not all needed to implement a basic Charging Station or CSMS. The table below lists messages that are typically implemented to deliver basic functionality for an OCPP managed Charging Station. The purpose of this list is to guide developers that are new to OCPP. Please note: this table does not define what needs to be done to become OCPP 2.0 "certified". The functionality that is to be implemented to become OCPP 2.0 certified is described in Part 5 of the specification, "Certification Profiles".
Table 4. OCPP 2.0 Basic Implementation
| Functionality | Use cases | Messages |
|---|---|---|
| Booting a Charging Station | B01-B04 | BootNotification |
| Configuring a Charging Station | B05-B07 | SetVariables, GetVariables and GetReportBase (respond correctly to requests with reportBase = ConfigurationInventory, FullInventory and SummaryInventory). |
| Resetting a Charging Station | B11-B12 | Reset |
| Authorization options | One of C01, C02 and C04 | Authorize |
| Transaction mechanism | E01 (one of S1-S6), E02-E03, E05, E06 (one of S1-S6), E07-E08, One of E09-E10, E11-E13 | TransactionEvent |
| Availability | G01, G03-G04 | Only ChangeAvailability and StatusNotification. |
| Monitoring Events | G05, N07 | A basic implementation of the NotifyEvent message to be used to report operational state changes and problem/error conditions of the Charging Station, e.g. for Lock Failure. Also used for reporting built-in monitoring events. |
| Sending transaction related Meter values | J02 | TransactionEvent |
| DataTransfer | P01-P02 | Any OCPP implementations should at least be able to reject any request for DataTransfer if no (special) functionality is implemented. |
NOTE Please also refer to the section on Minimum Device Model in part 1.