OCPI 2.2.1
Compare this step across versionsRun one charging session in the simulator and watch each OCPI message travel between the parties.
Let's simulate a complete charging session from authorization to billing. This will demonstrate how different OCPI entities work together.
Session Simulation Steps
Step-by-Step Instructions:
Set up Entities: Add at least one CPO, one EMSP, and one Charger
Connect Entities: Create connections between the entities
Start Simulation: Use the Play button to begin the session
Observe Messages: Watch the messages flow between entities
Examine Details: Click on messages to see their content
Try These Scenarios
Scenario 1: Successful Charging
Simulate a complete, successful charging session with proper authorization
Scenario 2: Authorization Failed
Simulate what happens when authorization is rejected
Scenario 3: Multiple Sessions
Run multiple charging sessions simultaneously
Scenario 4: Error Handling
Simulate network errors and recovery mechanisms
What OCPI 2.2.1 defines for this lesson
Modules in this version
Advertised sender and receiver interfaces
An endpoint declares how another platform can pull or push data. Credentials uses the same interface for both roles.
The header token is encoded
The request header carries an encoded token; the Credentials body still carries the raw token.
Billing records name the Token owner
A charge record names the country and company that own the driver's Token.