CPO updates the running Session cost

Advanced · 4 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.

Step 2 of 4 · Tariff and billing
sessionsCPOsendseMSPreceives
sessionsCPOsendseMSPreceivesDriverActor
Legend

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

Step 2 of 4 · Paused

Selected step

All 3 actors

CPO · eMSP · Driver

Selected exchange

The CPO updates the running Session cost. Charging periods reference the applicable tariff; restrictions can change which price elements apply during the Session.

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.