Guest organisation
OCPI
Learn reference
Guest organisation
OCPI
Learn reference

CPO pushes the remotely started Session

Technical · 5 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 3 of 6 · Remote start and stop
sessionsCPOsendseMSPreceives
sessionseMSPreceivesCPOsendsChargerActorDriverActor
Legend

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

Step 3 of 6 · Paused

Selected step

All 4 actors

eMSP · CPO · Charger · Driver

Selected exchange

ACTIVE with kwh 0 does not establish energy transfer. A later PATCH with kwh above 0 reports energy delivered. The CPO pushes Session SESSION-R001 to the eMSP with PUT.

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 →

The sandbox sends this exchange in a different flow, so there is nothing to run from this step.

Test this flow

Test this flow runs against a CPO endpoint you have registered.