Supported fields and extensions

Which OCPI fields the MOBI.Hub guarantees to support, and how the optional mobie_* extensions work.

The tables presented throughout this document describe the fields and operations supported by the Mobi.e Interoperability Hub for each OCPI object and endpoint.

Only the fields explicitly listed in the corresponding tables are guaranteed to be supported by the platform. Fields defined in the OCPI specification but not referenced in this document may not be processed by the Mobi.e platform and can therefore be ignored during validation and interoperability procedures.

Mobi.e extensions

Mobi.e adopts the standard OCPI data model as the primary mechanism for interoperability between Charge Point Operators (CPOs) and Electric Mobility Service Providers (EMSPs).

Whenever additional Mobi.e-specific information is required, optional extensions may be provided using fields prefixed with mobie_*. These extensions are not part of the OCPI specification, and their implementation is entirely optional.

The absence of mobie_* fields shall not affect the interoperability between participants nor prevent the successful exchange of standard OCPI messages.

Additional Mobi.e services, such as campaign management and relationship management between CPOs and EMSPs, are implemented independently from the OCPI protocol and are documented separately.