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

CPO sends Session updates with meter values

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

Technical details off

Driver taps an RFID card on the charger

Charger asks the CPO about the token

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

The charger reports new meter readings. The CPO updates the session with current energy delivered and sends the update to the eMSP.

Sandbox run · OCPI 2.2.1

Run this exchange in the sandbox

Why this matters

The CPO owns the Session. In the push model it sends a new Session with PUT and changes with PATCH; the final status is COMPLETED.

CPO

EMSP

"When the CPO creates a Session object they push it to the corresponding eMSP by calling PUT on the eMSP's Sessions endpoint with the newly created Session object. Any changes to a Session in the CPO system are sent to the eMSP system by calling PATCH on the eMSP's Sessions endpoint with the updated Session object. Sessions cannot be deleted, final status of a session is: `COMPLETED`. When the CPO is not sure about the state or existence of a Session object in the eMSP's system, the CPO can call GET on the eMSP's Sessions endpoint to validate the Session object in the eMSP's system."OCPI 2.2.1 Sessions module · #mod_sessions_push_model

Explore the sessions module →

Previous Next

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 FlowStep 6 of 10