Learning Hub/Scenarios
Explanations use OCPI 2.2.1. Physical and billing-system events are authored examples.

Part of the lesson OCPI charging session lifecycle

Charger asks the CPO about the token

Start here
8 min
OCPI 2.1.1, 2.2.1 and 2.3.0Test this flow runs against an eMSP endpoint you have registered. The endpoint test grades your endpoint's answer to each Session push. It does not read the stored Session back.
Test this flow
Driver taps an RFID card on the charger
Charger asks the CPO about the token

The charger doesn't recognize the token locally. It forwards the authorization request to the CPO's backend system to check if this driver can charge.

CHARGER
CPO
"The Open Charge Point Interface (OCPI) enables a scalable, automated EV roaming setup between Charge Point Operators and e-Mobility Service Providers."OCPI 2.2.1 specification · #introduction_introduction_and_background
PreviousNext
CPO asks the eMSP to authorize the token
Authorization succeeds and charging begins
CPO pushes the new Session to the eMSP
CPO sends Session updates with meter values
Driver unplugs and the final reading arrives
CPO pushes the COMPLETED Session
CPO sends the CDR for billing
eMSP accepts the CDR and bills the driver
Message Flow⚡UUserCChargersenderCCPOreceivereeMSPStep 2 of 10