OCPP Proxy offline behavior

The OCPP Proxy offline behavior makes charging possible, even if there’s a loss of communication to the third party backend, e.g. due to an unstable internet connection. The offline behavior ensures that the OCPP connection between ChargePilot and charger is kept alive.

Glossary

offline period Period where there is no connection between ChargePilot and the TPBE

TPBE Third Party Backend

Charger Connectivity during an offline period

• Case 1: Charger is connected to ChargePilot and was authorized by the TPBE before the offline period started

  • The charger is fully recognized by ChargePilot, no impact to other functionalities.

  • As long as the local controller has internet connection, the charger will stay online in the ChargePilot UI.

  • All transactions will be stored and send to the TPBE when the connection is restored.

All transaction data will be stored and send to the TPBE when the connection is restored.

• Case 2: Charger is trying to (re)connect during the offline period to the TPBE

  • Examples:

    • charger reboots

    • charger was not connected to ChargePilot before the offline behavior

  • The charger cannot be verified by the TPBE.

  • The charger will not be connected to ChargePilot.

  • The charger will be offline in the ChargePilot UI.

If a charger reboots/(re)connects during an offline period, it is rejected. If OCPP Proxy restarts during an offline period, all chargers that use OCPP Proxy will be rejected.

 RFID Authentication during an offline period

• Case 1: RFID tag has previously been successfully authorized by the TPBE while ChargePilot had connection to the TPBE

  • ChargePilot will allow charging.

• Case 2: RFID tag has not previously been successfully authorized by the TPBE while ChargePilot had connection to the TPBE

  • ChargePilot will not allow charging.

• Case 3: RFID tag has previously been successfully authorized by the TPBE while ChargePilot had connection to the TPBE but is now marked as expired

  • Examples:

    • RFIDs that are only allowed for a determined timespan, which is set by the TPBE

  • ChargePilot will not allow charging.

RFID tags, that were previously authorized by the TPBE, will be stored locally on the ChargePilot Controller. They will still be present, even after a reboot of the Controller.