Articles in this section

See more

MOBI.E interface

Niklas Wallner
  • Updated
Follow

What is MOBI.E?

MOBI.E is a state-owned company operating as an EGME (Electric Mobility Network Managing Entity) in Portugal. As a charging station operator in Portugal, you need to activate the MOBI.E interface.

You can find more details about MOBI.E on their official website.

 

Step-by-step instructions to use the MOBI.E interface

1) Enabling the interface

In the first step, the interface must be approved by us so that it appears in your be.ENERGISED instance in the "Roaming" tab. Please contact your direct contact person in this regard.

 

2) MOBI.E Charge Point Identifier

To use the MOBI.E interface, you need so-called "Charge Point Identifiers" for your charging stations. Contact MOBI.E in this regard, you will receive the identifiers from them.

 

3) Activating the interface per charging station in be.ENERGISED

In the next step, you have to activate the MOBI.E interface at each charging station located in Portugal.

To do this, go to Infrastructure/Charging stations/Station list in be.ENERGISED and go to the charging station data sheet of the respective charging station. Go to the "Roaming" tab and select "MOBI.E". 

To unlock the interface, the MOBI.E identifier of the charging station must be entered. You can then activate MOBI.E.

mceclip0.png

 

Other comments (questions and answers)

Where is the data stored?

The data is generally stored in be.ENERGISED.

What exactly is the MOBI.E identifier used for?

The MOBI.E identifier is used for communication with MOBI.E so that MOBI.E can distinguish the charging stations from each other. The identifier is included in all messages to MOBI.E so that they know on their side which charging station it is.

How is the data forwarded to MOBI.E?

In general, there is an OCPP flow, which means that we forward data according to OCPP 1.5. The following messages are forwarded:

  • BootNotification
  • MeterValues
  • StartTransaction
  • StopTransaction
  • Responses to RemoteStart, RemoteStop

It seems that BootNotifications are not transmitted to MOBI.E. What can be done?

The BootNotification that be.ENERGISED receives from a charging station is independent of the BootNotification that be.ENERGISED sends to MOBI.E. The BootNotification is sent to the charging station. For this reason, such notifications are not forwarded to MOBI.E.

The BootNotification that be.ENERGISED sends to MOBI.E is used to "register" the charging station with MOBI.E. The BootNotification is not used to register the charging station with MOBI.E.

However, there is the possibility to manually trigger the BootNotifications of all relevant charging stations via the button "Send EVSE information to MOBI.E". You can find this item in be.ENERGISED under Roaming/MOBI.E/Settings. The BootNotifications will then be forwarded to MOBI.E at a certain time on that day.

How to export the data?

OCPP data in general can be exported manually in be.ENERGISED.

What data is returned by MOBI.E?

MOBI.E delivers the data to a sFTP server, be.ENERGISED imports the data from there via a regularly running job (once per day).
The data contains the actual EMP of the charging process and a reference to the specific session (SessionID). This data must be provided because the actual EMP cannot be contained in the OCPP data.
Then the charging process will be updated with the data provided by MOBI.E in be.ENERGISED.
Until then, the charging process is set to invalid in be.ENERGISED plausibility monitor to not start the charging process until all required data is available.

How fast is the data transmitted from MOBI.E to be.ENERGISED?

This is dependent on MOBI.E. As soon as the required data is available, be.ENERGISED queries and updates it once a day.

What form of validation takes place on the part of MOBI.E?

We do not have any information regarding validation at MOBI.E. On our side, charging processes are marked as "INVALID" until the CDRs have been assigned to an actual EMP. Furthermore, all checks of the plausibility monitor can be applied.

What information is exchanged between be.ENERGISED and MOBI.E?

During the charging process

  • be.ENERGISED sends the OCPP data to MOBI.E.
  • From MOBI.E be.ENERGISED receives a transactionId in the StartTransactionResponse.
  • When the charging process is finished, the EMP is unknown. Therefore, each charging process is marked with the INVALID MOBI.E EMP ID error in the plausibility monitor.

After the charging process

  • be.ENERGISED polls the sFTP server defined in the roaming interface on a daily basis.
  • During this process each .xml file is processed
    • If the .xml file contains a "Usage Object", then the idUsage & idServiceProvider fields are taken from it.
  • From the idUsage field the transactionId is derived, which references the charging process. This corresponds to the EMP session ID.
  • The EMP is derived from the idServiceProvider field.
  • The charging process is then assigned to the EMP, evaluated again in the plausibility monitor and recalculated.

Do we use client certificates and TLS 1.2. when connecting to MOBI.E?

  • For the connection between be.ENERGISED and MOBI.E via OCPP: No we are not using Client side certificates and TLS 1.2
  • For the connection between the charging station and be.ENERGISED: It depends how the charging station is connected.

Version: 2023-06-22 06:15:43 UTC

Related articles