Sessions

The Sessions module: how sessions are authorized, how often they are updated and the Session object.

On this page

Technical considerations

The implementation shall take into consideration the following:

No reservations shall be considered.
Sessions originating in the CPO, for example via an RFID card, may be authorized through MOBI.Hub when operating in Centralized Authentication mode. Depending on the selected authorization model, authorization may be performed through real-time authorization or whitelist mechanisms.
When operating in Classic Hub mode, authorization may be performed directly by the CPO and/or EMSP according to the applicable interoperability relationship. MOBI.Hub shall route the resulting session information according to the configured relationships.
If a session or session update cannot be associated with a valid token or authorized interoperability relationship, the request may be rejected by the MOBI.Hub. The corresponding information may nevertheless be integrated where applicable, but no CDR shall be generated by MOBI.Hub as a result of that request.
CPOs are recommened provide session updates at regular intervals, with an advised maximum interval of 5 minutes.
Although charging_periods are not mandatory, CPOs are strongly encouraged to provide this information as part of the Session updates. If charging_periods are not provided, the MOBI.Hub shall estimate the applicable charging periods when the Session is terminated.

Methods to be implemented

EMSP (and MOBI.Hub)

`Sessions` methods for the EMSP (and MOBI.Hub)
Method	Direction	Description of usage
`GET`	Request	Retrieve `Sessions`, paginated and filtered and ordered by `last_updated`.
`PUT`	Response	Send a new or updated `Session` object to the EMSP.
`PATCH`	Response	Update an existing `Session` object.

CPO (and MOBI.Hub)

`Sessions` methods for the CPO (and MOBI.Hub)
Method	Direction	Description of usage
`GET`	Response	Retrieve a `Session` by its identifier.
`PUT`	Request	Send a new or updated `Session` object to the Mobi.e HUB.
`PATCH`	Request	Update an existing `Session` object in the Mobi.e HUB.

The MOBI.Hub does not currently support Charging Preferences. EMSPs cannot therefore use this functionality to provide charging preferences during an active Session.

Objects description

Sessions

Table 4 – `Session` object properties
Property	Mandatory	Value	Comments
`country_code`	TRUE	`PT`
`party_id`	TRUE
`id`	TRUE		Provided by the HUB for OCPP connections or generated by the CPO for OCPI connections.
`start_date_time`	TRUE
`end_date_time`	FALSE		Optional due to the start object
`kwh`	TRUE
`cdr_token`	TRUE
`auth_method`	TRUE	`AUTH_REQUEST` `COMMAND` `WHITELIST`
`location_id`	TRUE
`evse_uid`	TRUE
`connector_id`	TRUE
`currency`	TRUE	`EUR`
`charging_periods`	FALSE		Optional due to the start object
`status`	TRUE	`ACTIVE` `COMPLETED` `INVALID` `PENDING`
`last_updated`	TRUE