Guest organisation
OCPI
Learn reference
Guest organisation
OCPI
Learn reference

CPO sends Session updates with meter values

Start here · 8 min

OCPI 2.1.1, 2.2.1 and 2.3.0

Showing OCPI 2.2.1. Physical and billing-system events are authored examples.

Part of the lesson OCPI charging session lifecycle

Step 6 of 10 · Complete EV charging session
sessionsCPOsendseMSPreceives
sessionsDriverActorChargerActorCPOsendseMSPreceives
Legend

The line follows the selected step. Actor dots identify the parties; they show no conformance verdict.

Step 6 of 10 · Paused

Selected step

All 4 actors

Driver · Charger · CPO · eMSP

Selected exchange

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

CPO → eMSP · sessions

Source
"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
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.

Explore the sessions module →

Sandbox run · OCPI 2.2.1

Run this exchange in the sandbox

Test this flow

Test 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.