Explanations use OCPI 2.2.1. Physical and billing-system events are authored examples.
Part of the lesson OCPI charging session lifecycle
CPO pushes the remotely started Session
Technical
5 min
CPO pushes the remotely started SessionExplore the sessions module →
The charger is delivering energy. The CPO creates Session SESSION-R001 and pushes it to the eMSP with PUT. This Session, not either ACCEPTED, is the evidence that charging started.
The sandbox sends this exchange in a different flow, so there is nothing to run from this step.
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
Message FlowStep 3 of 6