Check out the presentation about the leading eMobility players presented by our CEO.

After founding Solidstudio, Pawel was an originator in terms of pursuing expertise in eMobility. With the build-up of a solid knowledge-base on industry’s needs & wants, he now keeps a close eye on products’ development. He’s also hugely responsible for the business’ side and designs the business models for our products.

Paweł Małkowiak

Below, we add the script for those who prefer to read through.

Hello, I’m Paweł and I'm co-founder and CEO of Solidstudio. Today I'd like to cover the topic of the digital products in the eMobility ecosystem to build a basic understanding of what is doing what and what the responsibilities are.

I covered this slide many many times before for all our partners to basically be on the same page, regarding the vocabulary. Which products are what and what they are doing in this ecosystem? Today we don’t have a major presentation in front of me, instead I'm going to take you through this very basic slide. I hope that after this brief session you will have a little bit more understanding of how different actors are communicating with each other in this ecosystem. We won’t take on more advanced subjects (like eRoaming Hubs). We’ll go through the two basic digital products you can build on your own - be the software provider or buy off-the-shelf solutions either on the Saas license basis. We will cover roaming a little bit but more like peer-to-peer for the sake of linking those products together.

The roles within the ecosystem - eMobility Service Provider

Let’s start with the end-user perspective. What's actually happening is that the EV driver needs to have the possibility to search for the charging station. We have got our EV driver, who has the mobile application. Users are holding their phone with the eMSP application in place ( eMSP or eMP - it’s the eMobility service provider application). In this kind of applications usually you can: login, register, find charging stations, see the tariffs, navigate to them and basically start charging. That would be the first player - a company that acts as an eMSP. What we briefly covered are the functionalities that every eMSP should be able to offer

. The eMSP is actually that party that takes care of the customers.

 It should: know how to set pricing and present it to the EV drivers, how to do the marketing, how to manage subscriptions and how to make their users reuse their app again. This is very basic differentiation, but I believe that in this case, the EMSP application is responsible for handling EV drivers and is mostly focused on the B2C market. Of course, I mentioned before that the EV driver should be able to search for the stations in the eMSP site, but since the eMSP doesn't really know them at this place yet, there is a need to present a second player.

The roles within the ecosystem - Charge Point Operator

So, the second player is the Charge Point Operator, who needs to use the software to manage their charging network. In essence, the Charge Point Operator is an organization or a company that is managing their stations. This is the main, fundamental differentiation between the EMSP and the CPO. We will cover how they communicate in a second part. We need to realize that EMSP is covering the user interactions and CPO is covering everything that goes with the charger. Here we get the link. So how does it happen that those two parties understand each other and know what to display? This is where the OCPI protocol comes in. But, let's take a pause here.

You can meet many different instances that actually mix those two digital products into one - it is also possible. In Solidstudio, we believe that clear separation of duties and responsibilities is a very important factor, when it comes to building digital products. So in our solutions, you can find a very clear differentiation. This division allows you to actually buy or build one of those products, without necessity to have both. There’s of course a challenge how to make them talk to each other.

The custom API is always the option.This is not always the best one, because even though it can work in your internal ecosystem. We need to remember that there are multiple players in the market. If you've got the custom API (either on the eMSP side or on the CPO side) everybody who wants to connect to you, will be required to actually fulfill your contract. If there's going to be 10 different parties that like to connect to you, basically they need to do the same work 10 times. That's why the Open Standards has been invented and that's why we basically structure all our domain models on the OCPI.

Of course, if you've got two products: the CPO and the EMSP and they can be seen from a very high perspective as the one digital entity, under the hood those are two separated products that talk to each other through the OCPI. This is where the magic happens. Even though the CPO is in charge of managing the stations, it pushes all the locations with all the data to all different eMSP’s that are linked to it, because OCPI connection and the peer-to-peer connections are meant for many relationships. You can have one partner, you can have multiple partners and their partners can have other CPO’s connected to them.

CPOs know which charging stations they are operating and they’re pushing their locations to the eMSP application. eMSP got the back-end, so on the server side everything is computed and this pushes - in our case - through the rest API to the EV driver. EV drivers are able to start charging by pressing the button. There are two basic ways to start charging. First one is the remote start/stop, which is ultimately pressing the button on the mobile application. The second one is the RFID.

Let's focus on the remote start-stop first. When the EV driver presses the remote start-stop, under the hood the mobile application ( it can be the iOS or the Android app) calls over the rest API the eMSP server side. This server knows which CPO pushes the data with a given charging station and over the OCPI and OCPI connectivity, it calls the charging platform to start the charging.

Here we are getting into another open standard that we need to talk about. It's OCPP.

Open Charge Point Protocol in the eMobility ecosystem 

OCPP is the open standard that allows CPO’s to talk to different stations. We can imagine the situation that each of the manufacturers has their own proprietary protocol. In this case, the development of the CPO platform would be enormous, because we've got hundreds of different device providers and those would be a hundred different standards. Plus, they would have to invent it from their hardware perspective. So OCPP actually allows different charging stations manufacturers to implement it on the hardware side. And CPO platforms can implement it on the software side. Thanks to that, we, as the CPOs, are allowed to actually use multiple manufacturers of the charging stations. As mentioned before, we've got the OCPP connection between the CPO and the station, in our case we are using web sockets to actually keep this connection open. CPO Platform is able to tell the charger to start the charge.

The circle is closed.  The EV driver successfully started charging. And from now on, the charging station will report to the CPO Platform about the current charging session e.g. the current power or how much energy has been consumed. The CPO will push this information to the eMSP and eMSP will display that information to our EV driver. This is how it looks from the EV driver perspective.

Of course, we've got more business or admin side of things. Both eMSP and CPO should expose the admin portal. As I’ve mentioned before, the main duty of the eMSP is actually serving the EV driver. In order to that, in the EMSP admin portal you have to have possibilities such as: setting up the tarfiifs for the EV drivers or managing the RFID’s, because RFID’s needs to be linked with the driver, so we need to know which account to charge.

On the other hand, in the CPO admin portal, you need to have the ability to manage your charging stations. You need features like: add a new charity station, remove or make it unavailable, change the tariffs for B2B purposes, manage other admins, manage OCPI connections and many more.

Everything that we know so far is crucial to understand how the tariffs should work in the eMobility ecosystem, because both: the EMSP admin portal and CPO admin portal user are setting up their tariffs. What is important, the CPO’s tariffs are B2B tariffs so for all CDRs, the charging events that have been completed on their stations under their management, that tariff will apply to them, but only for the eMSPs connected.

So those are going to be B2B money transfers. And those do not necessarily have to be the same tariffs that the end user EV driver is paying. eMSP admin can set up the tariff for instance on the basis of adding the margin. In the simple case, if 1kWh costs 1€ on the B2B level then the other in the portal can add 0,5€ margin, so the end user will pay 1,5€ per each kWh consumed. All the money goes to the eMSP, but then depending on the settlement between those two parties, the 1€ will go back to the CPO. This is how it works.

Of course adding the margin is just one possibility. We can imagine that the eMSP admins got some kind of loyalty scheme for the users e.g. every 10th charging is for free. Nevertheless this EMSP will have to settle the bill with the CPO. You can also ask the question: 

. We can see all different players on the market and some of them are both CPOs and EMSPs. In this case, let's say using this ecosystem, the tariffs can be set on the CPO side. For instance eMSP can add zero margin just to keep it transparent, so all the profits are in the CPO or vice versa - so the CPO admin can set up the tariffs for zero and all the billing is done by the EMSP.

This is covering the digital ecosystem from a very high level. We need to remember that we brought up the closed ecosystem. There is a possibility to lean different EMSP’s to different CPO’s over peer-to-peer OCPI connectivity, but we need to remember that there are other ways e.g. a hub integration.

That's it. If you've got any questions, please do not hesitate to contact us.

Two actively supported independent open standards for EV roaming.

Being an eMobility leader in various projects across multiple startups, Piotr was responsible for OCPI and OCPP integration as well as EMP and CPO platforms development. With extensive expertise in the open standards field and eMobility tech solutions, he is leading teams of experienced developers and contributing with invaluable knowledge and experience.

Piotr Majcher

In a search for interoperability, the e-mobility market players need to speak the same language. Demand for coherent infrastructure is dictated by rapid EV penetration. Several factors, such as local policies and incentives, contribute to an enthusiastic approval of electrically-powered vehicles. Hence, the focus has been transferred to the network and its ability to create open, accessible infrastructure. To match the pace - resonate with market expectations and work together to create an accessible, open environment - the new order needs EV roaming.

EV roaming is something users cannot see but witness, and whether knowingly or not, appreciate. Open standards create the road to consistent and complete e-roaming. With a large pool of contributors, up-to-date and secure solutions are available at hand to any participant in the rapidly growing e-mobility market. To understand the role of open standards in e-mobility here are explanations for widely approved models.

Note: In the e-mobility world there are four main open standards facilitating e-roaming. Two are developed and maintained by non-commercial hub operator and independent knowledge board - OCPI Open Charge Point Interface and OCHP - Open Clearing House Protocol & OCHPDirect. Two others were developed by commercial roaming hub operators. These are OICP Open InterCharge Protocol designed by Hubject and eMIP - eMobility Interoperation Protocol maintained by GIREVE.


Originally developed by eViolin, a Dutch association of Charging Station Operators and eMobility Service Providers, that pursues national roaming with international connection, using open standards. In cooperation with ElaadNL -  the knowledge and innovation center in the field of Smart Charging and the charging infrastructure in the Netherlands - major Dutch grid operators. Initially governed by the Nederlands Kennisplatform Laadinfrastructuur (NKL) - Netherlands Knowledge Platform for Public Charging Infrastructure - a partnership of business organizations, governmental figures, and research institutes. From May 2020 the OCPI is managed and maintained by the EVRoaming Foundation. Open Charge Point Interface offers p2p and any roaming hub integration business model.

OCPI is registration-free, openly available at no cost. Published under the Creative Commons Attribution-NoDerivatives 4.0 International Public License. Hence, the distribution is free when given proper credit. Although blocks the distribution of the modified versions of the protocol. The most recent version (v2.2) was released in October 2019. Open Charge Point Interface offers a modular set-up, a very convenient way of deployment - it is up to the individual decision which modules to include. It also covers a variant check, a significant factor for peer-to-peer mutuality as there is no fundamental actor applying updates or completing to support previous protocol versions.

Open Charge Point Interface is the only, so far, set on JSON/rest and is a real-time protocol. It maintains synchronous and asynchronous operations.

Open Charge Point Interface carries multiple explications for Eichrecht (German calibration law for electric vehicle charging), as recommended by the top European e-mobility providers - Has-to-be, Alfen, eBee, and Mennekes. In March 2021 EVRoaming Foundation announced the start of the first independent Roaming Agreement pool. The organization aims to support setting up trusted agreements between parties, for either p2p or via a (virtual) roaming Hub. The pool is available for all Full Contributors (The foundation distinguishes the following membership classification categories: Full Contributor, Associate Contributor, Sponsors, and Managing Contributors).

The protocol’s documentation describes market roles as follows:

The EV user connects to a charge point in can be provided information from the MSP

The e-mobility service provider (eMSP), grants EV services to EV users. eMSP connects to Charge Point Operator (CPO) to offer e-roaming services.

The CPO manages, maintains, and operates charge points (charge stations), on the technical and administrative side. CPO is open to connecting to MSPs to offer roaming services.

The e-mobility service provider ensures charge point location information.

The eMSP influences smart charging sessions depending on extra sources of information.

The purpose of a roaming hub is to facilitate information exchange between market players. In this division Open Charge Point Interface supports:

Roaming via hub - OCPI facilitates data exchange between eMSPs and CPOs via hubs, for this operation, the protocol offers a separate hub supporting module.

Roaming peer-to-peer (p2p) - Both eMobility Service Providers and Charge Point Operators can correlate immediately via OCPI. Separate interfaces are designed for eMSPs and CPOs.

Authorization - The token module in the OCPI architecture supplies Charge Point Operators with the knowledge of any token information of eMSP. There are two ways to execute authorization, which could be real-time or via a whitelist.

Reservation - On the eMSP side, the OCPI offers to make and cancel a reservation.

Billing - OCPI supports the basis for invoicing - sending CDRs - Charge Detail Records.

Tariff information - The protocol supports the exchange of the key details related to energy tariffs. Complex tariff calculations depend on the time charged and energy. All this information is included in the tariff module.

Static charge point information - This covers: IDs, CPOs, charge point site, host, charge point name, charge point location details (name, address, geocode, type, image, platform level, directions), nearby facilities, link to a website, time zone, opening times, current availability status, scheduled availability status, accessibility, tariffs, authorization modes, payment methods, terms and conditions, charge mode, connector type, maximum power, voltage, amperage, energy mix, remote start/stop, reservation, smart charging support, and the last update mark.

Real-time charge point information - Stats: available, blocked, charging, inoperative, out of order, planned, removed, and reserved.

Session information (real-time & static) - Covers: sessions ID, start time, end time, energy consumed, CDR ID, authorization method, location, charge point ID, meter ID, currency, charging periods, total cost, sessions status, and last update. The same information can also be in real-time.

CDR information - CDR IDs, time, duration, finish status, and more.

Callibration law (Eichrecht) support - OCPI maintains the exchange of signed meter data which can be used to conform to Eichrecht - German calibration law.

Remote start/stop - The start and stop of any charging session can be done remotely via the eMSP app.

Smart charging - Several charging profiles are supported by OCPI: the cheapest charging, the fastest charging, the most environmentally-friendly charging, or no particular choices. The preferences can be registered per session by the user. The CPO can accept or decline the option. Although the smart charging profile module does provide certain options, these cannot be ensured, since other factors influence the charging session.

OCPI’s ultimate goal is to allow any EV driver to charge at any charging station in the EU. In fact, the protocol is used intensively throughout Europe (Netherlands, Belgium, Luxembourg, UK, Germany, France, Spain, Italy, Denmark, Austria, Poland), but not limited. It also gains recognition, among others, in the USA, Canada, South Africa, and India. The protocol is gaining acceptance in ever-widening circles and the number of countries is steadily increasing.

OCHP - Open Clearing House Protocol and OCHPDirect

OCHP is the second protocol that offers a hub or p2p connection. Integration with hubs is done via OCHP, and the direct peer-to-peer connection is possible with OCHPDirect. The solution is maintained and expanded by Smartlab Innovationsgesellschaft GmbH.

and ElaadNL (ElaadNL also supports aforementioned OCPI), organizations established by German and Dutch entities. OCHP is used by the roaming hub e-clearing.net (e-clearing.net also offers connectivity via mentioned above OCPI) operated by Smartlab and owned by Smartlab and ElaadNL. As a not-for-profit platform, the main interest of e-clearing.net is to develop the e-mobility market. Both available current versions OCHP v1.4 and OCHPDirect v0.2.6 were released in August 2016 (In October 2020 OCHP introduced to members the newest update 1.5, but no further public information was provided, the valid version remains 1.4).

The OCHP documentation is free to download and does not demand registration. Thanks to the MIT license, the protocol allows for open distribution and alteration. The administration of the OCHP lies on the Smartlab/ElaadNL side, which has the remaining right to apply and execute edits to the protocol. Prior and complete implementation testing needs to be conducted before a participant gains access to the e-clearing.net roaming platform. To support a coherent development of the OCHP protocol each year developers collect user feedback.

The Open Clearing House Protocol is based on the SOAP (Simple Object Access Protocol) computer protocol. It largely relies on asynchronous communication (opposed to real-time communications, as for OCPI). For instance, e-clearing.net does not store transaction data. Instead of real-time authentication, OCHP forms lists of users who are allowed to authenticate. This approach allows avoiding a single point of failure (SPOF) - if the roaming hub breaks down, charging sessions remain active.

The OCHP protocol documentation describes the following market roles:

The EV user, that has a direct or indirect contract with an eMobility Service Provider, charges an EV at a charge point/charge station.

The eMSP grants access to charge points/charge stations to the EV owner. The eMSP provides the EV user access via an RFID card or certificates. The service is supported by CPOs. The CPO operates charge points and acts as a contract agent for the eMSP. Each charging session is settled between the eMSP and the CPO under agreed conditions.

The parking spot operator (PSO) owns and operates the parking spots with access to the charging infrastructure operated by the CPO. The PSO offers a parking spot where a charge point is located and can supply information on location and availability to the CPO.

The clearinghouse operator (hub operator), runs a software platform to enable data exchange between MSPs, CPOs, and NSPs*.

*The documentation of OCHP protocol also distinguishes the role of the Navigation Service Provider (NSP), similar or equivalent to the role of Charge Point Operator. It applies to service towards the EV user for searching, locating, and routing to charge points. The party may have contracts with CPOs or MSPs.

Roaming via hub - Hub’s roaming platform connects the associated partners. OCHP is used by the roaming hub e-clearing.net, but the documentation does not specify if the roaming hub should necessarily be run by e-clearing.net.

Authorization - EV owners are recognized by tokens. The eMSP supplies a list with contract IDs of registered EV users to the hub, that can later be downloaded by CPOs. If an EV is charged at a CPO, the operator’s system checks the ID against the roaming authorization list downloaded from the roaming hub.

Billing - Charge detail records (CDRs) collect charge data, hence CDRs describe the billing. The CPO exports the CDRs to the roaming hub. The hub performs a basic plausibility check. Correct CDRs are forwarded to the eMSP. In case the CDRs fail the validation of reliability check, are sent back to the CPO for the fixing. Besides, the roaming hub also archives CDRs.

Static charge point information - OCHP can be applied to show the charge point ID, CPO, charge point site owner, charge point location (name, address, geocode, type, image), nearby facilitates, link to a website, time zone, current status, scheduled availability status, accessibility, tariffs, authorization forms, payment options, charge mode, connector type, maximum power, guaranteed power, voltage, support phone number, reservation possibility, the maximum time for the reservation, languages of the interface, user feedback form, and the time of the last update. Besides, the tariff model can handle complex advanced tariff schemes based on time of the day, date, charged energy, charging speed, and duration based on input from CPO. The CPO supplies static charge point information to the roaming hub, which can be then processed and transferred to contracted EV owners by eMSP.

Real-time charge point information - OCHP provides the current status of a charge point (available, reserved, occupied, blocked, out of order, unknown). OCHP divides real-time from static data. The dynamic data is stored in a separate database, dedicated to this kind of access. Real-time charge point information is sent to the roaming hub, then is transferred to the signed users of an eMSP.

Session information - refers to CDR ID, charge point ID, token ID, contract ID, CDR status, start time, end time, duration, charge point address, charge point type, connector type, tariffs, meter ID, total cost, and currency.

Remote start/stop - Charging sessions can be controlled via an eMSP app.


The OCHPDirect (dedicated for p2p connections) supports the following functionalities:

Roaming peer-to-peer - Achieving e-roaming is possible without a connection with a hub.

Authorization - Charging sessions can be controlled via an eMSP app.

Real-time sessions information - Start of a charging session, end of a charging session, metering information, power management information, handy invoicing.

Remote start/stop - The charging process can be controlled when stationary started via the eMSP application.

E-clearing.net, unlike commercially orientated hubs, is an open platform that facilitates the exchange of roaming authorization, charge transaction, and charge point information data (all transactions are free). At the moment, e-clearing.net requires only a fee for joining the platform.


Why apply at least one open standard? To save time and open your network to a larger number of users, increase opportunities and reap profits. Or, in other words, applying open EV roaming charging software protects against being excluded from the market. Both, Open Charge Point Interface and Open Clearing House Protocol & OCHPDirect are classified as stable, reliable, and secure solutions. The growing number of countries that support the development and promotion of both solutions indicate openness, independence, and royalty-freedom. Open and modern approach contributes to fast penetration and enthusiastic approval. Many countries are in the early phase of charging infrastructure development. Open standards are meant to facilitate rapid growth and ensure up-to-date functionality.

OCPI and OCHP support installing a public open charging network

Open Charge Point Interface and Open Clearing House Protocol are developed and supervised by non-commercial organizations. Demand for roaming includes cross-border connectivity. The future of the open network will largely depend on the willingness of partners to collaborate and regulatory guidance. For instance, some countries already established conditions for operation on the domestic market. Slovakia requires new parties within three months of the commissioning of the recharging points, to be connected to any roaming platform that connects more than 80 operators. In Norway, Oslo authorities formed an open policy for sharing with third parties. Berlin expects every Charge Point Operator operating a recharging point in the public domain to register it in a central authentication platform managed by the city, offering access to the customers of each eMobility Service Provider under comparable conditions. To meet the conditions, it is necessary to open a network. Following the 2050 EU strategy, soon it might be mandatory to provide seamless connection on large networks in the Union.

An extensive scientific analysis of the four most commonly developed protocols in terms of the search for the ideal protocol can be found 

Two actively supported independent open standards for EV roaming. Discover cross-border e-mobility standards for accessible charging network.

EV roaming with open standards - OCPI and OCHP 

Actively supported two commercial open standards facilitating EV roaming.

Interoperability demands a flexible approach and cooperation between market participants. For opening the electric car charging market open standards have been established. Two are an initiative of independent associations (responsible for the development of Open Charge Point Interface and Open Clearing House Protocol). The two other open standards for EV roaming are privately held but similarly open and free to apply. Hub operators GIREVE and Hubject offer innovative customer-friendly service networks for cross-border charging. Both hubs actively support network growth. Becoming a marketplace for charge point operators, e-mobility service providers, car manufacturers, energy suppliers, and public institutions Hubject and GIREVE offer a broad range of profitable solutions and facilitated communication benefits.

Hubject’s network expands beyond Europe. At the moment hub operator connects 767 partners in 52 countries offering over 250 000 charging stations. Hubject is a joint venture of the BMW Group, Bosch, EnBW, Enel X, Mercedes-Benz, innogy, Siemens, and the Volkswagen Group. Initiated in 2012, forms now the largest pool of charging stations. Via intercharge, the dedicated e-mobility platform, provides standardized access to charging infrastructure. Besides, Hubject advises automotive manufacturers, charging providers, and other EV-related businesses launching e-mobility services or implementing Plug&Charge with ISO 15118.

GIREVE has been created as a startup by leading French players in electric mobility: Renault, CNR, la Caisse des Dépôts, EDF et Enedis. At the moment GIREVE operates on 31 European markets and offers 185 charging networks with 109 476 charging stations accessible via EV roaming. Following the open policy in November 2020 hub operator announced becoming a Full Contributor of EV Roaming Foundation (the one responsible for the development of the OCPI open standard). This provides enhanced opportunities for partners. For instance, for an operator being already OCPI compliant, there is no extra cost to connect to GIREVE. Offering two standards for interoperability enables innovation and progress for e-mobility.

OICP was designed in 2012 by Hubject - formed by leading automotive experts in Germany. Besides being the roaming platform, Hubject offers technical connection and contractual arrangements for e-roaming. The general structure of the OICP is divided into two parts - for the eMobility Service Providers and Charge Point Operators, nevertheless, the product offer is constantly being developed. Hubject proclaims the OCIP is “the most widely implemented communication standard between European eMSP and CPO systems”. The most recent version, 2.3, was released in October 2020. The newest update of the protocol follows market requirements - improves the POI quality in an upscaling market, calibration law compatibility, data process performance, and offers higher transparency on the different charging use cases. Additionally, Hubject offers helpful and relevant for CPOs set of remote testing functionalities, for complex examination of various use cases. With the recent protocol update, from July 1st, OCPI 2.1 will be withdrawn.

The protocol is publicly available at no cost and requires no registration. From May 2019, OICP became an open-source protocol, free of charge, distributed on Hubject’s website and on open code distribution systems. The aim is to include more stakeholders in the evolution of OICP. The protocol is published under the Creative Commons Attribution-ShareAlike 4.0 International License. This grants easy distribution and to be shared under the same consent. Additionally, Hubject offers Hubject-compatibility certification.

OICP is formed on SOAP (Simple Object Access Protocol) and uses an object-based approach. It’s a real-time protocol, that also offers asynchronous operations. Although a back-up database is provided, Hubject doesn’t actively support downloads to the charging station. The platform maintains a record of the transaction data.

The OICP protocol documentation establishes market roles as follows:

The EV user/owner wants to charge an EV at a charge point/charge station, and has an agreement with the eMSP.

The eMobility Service Provider wants to enable EV owners the access the charge points. In most cases, the eMSP has a valid contract and transfers information with the Charge Point Operator via Hubject’s platform. Hubject offers connection via eMSP aggregator, which enables communication with the platform. This means several eMSPs can integrate via an eMSP aggregator, hence, the sub-partners do not need to associate with Hubject.

The Charge Point Operator (CPO) manages a charge point. The operator has a signed contract and exchanges information via Hubject’s platform. Like eMSPs, several CPOs can integrate via a CPO aggregator. Appropriately the sub-partners do not need to register with Hubject, because the communication with Hubject is done via the CPO aggregator.

Hubject, being a roaming hub, facilitates communication between eMSPs and CPOs via the EV roaming platform Hubject Brokering System.

OICP supports the following functionalities:

Roaming via hub - The CPO and the eMSP system connect to based on web services Hubject B2B Service Platform. Both parties, the CPO and MSP, have an e-roaming contract through Hubject.

Ad hoc payment - ‘Intercharge direct’ is an ad hoc payment dedicated solution integrated in OICP and Hubject platform. This allows any contractless EV owner to charge up and pay at any charging station.

Authorization - Hubject links the IDs of eMSPs or CPOs and SSL certificate information. Then each does or does not authorize the charge session. Hubject’s database performs as back-up, but not actively support downloads from their database to the charging station.

Reservation - An EV owner can book a charge point e.g. via eMSP app. Hubject checks charge point compatibility with the EV.  If matches send the request to the CPO, which in return responds whether the booking was successful. A reservation can also be withdrawn.

Billing - Charge session data is recorded in Charge detail records (CDRs). Hubject passes on the CDR to the eMSP and stores the CDR in the system.

Charge point information - Uploaded charge point information can be distributed between CPOs and eMSPs via Hubject’s platform. The information areas are charge point ID, CPO, charge point name, charge point location (name, address, geocode, type), time zone, opening times, current availability, accessibility, tariffs, authorization modes, means of payment, charge mode, connector type, maximum power, hub connection, support contact number, reservation possible, real-time status information possible, predictive charge point usage, smart charging services, and the date of the last update. OICP maintains flexible pricing based on charge facility, charge point location, and time-of-use.

Real-time charge point information - This covers dynamic charge point availability status and tariff information.

Session information - Session ID, service specifics, charge point ID, authentication data, start and end time of charging, start and end time of connection, starting and stopping meter value, meter value in between, consumed energy, CPO ID, MSP ID.

Remote start/stop - From within the eMSP application, a charging session can be operated.


eMIP is designed and developed by a French start-up. Created in 2013 by leading French players in electric mobility: Renault, CNR, la Caisse des Dépôts, EDF et Enedis with the main objective to provide “open access to vehicle charging stations”. The core business of GIREVE is to offer a roaming platform for eMSPs and CPOs.

The eMobility Interoperation Protocol enables roaming via clearinghouse data. The protocol provides access to charging point databases, and smart charging features. Although the GIREVE’s main market is France, in 2017 expansion covered the connection of European operators in Austria, Germany, Netherlands, Switzerland, Sweden, UK, Italy, Romania, Norway, Czech Republic, Lettonia, Hungary, Denmark, Belgium, Spain, Slovakia, Irland, and Luxembourg. In 2018 GIREVE’s platform was made compatible with the open protocol OCPI. Currently, the roaming platform operates in 28 countries.

The most recent version, eMIP 1.0.7, was released at the end of July 2019. eMIP is open for free although requires registration. GIREVE also proposes certification services. Moreover, to join GIREVE, the before-mentioned certification is required to connect to the platform. The eMIP protocol is open and, when a partner is approved by GIREVE, allows complete benefits. This includes connecting with a different hub platform or conducting peer-to-peer connections. Note, the protocol documentation explicitly declares GIREVE as the hub platform, the eMIP in practice does not apply to peer-to-peer connections. To ensure a high level of architectural openness and up-to-date offering, GIREVE consults with stakeholders potential future functionalities. GIREVE entirely takes responsibility for the eMIP protocol, in contrast to the previously mentioned approaches (commercial and non-commercial), there is no formal eMIP-member association.

eMIP is based on SOAP (Simple Object Access Protocol). Although eMIP is designed as a real-time protocol, it also supports asynchronous operations. The peculiarity of eMIP’s architecture makes it fairly adaptable and flexible. Any new sorts of data messages, or identification methods, can quickly be added via definition tables.

eMobility Interoperation Protocol documentation defines market roles as follows:

The EV user/owner wants to charge a vehicle at a charge point and an authorization medium.

The eMobility Services Providers warrant EV owners different services amongst which EV charging service, rental, car-sharing, navigation services, etc. The eMSP has a B2C agreement with the EV owner/user and a subscription to GIREVE’s platform.

The Charge Point Operator (CPO) accesses charging infrastructure and other services to EV users/owners and has a subscription to GIREVE’s platform.

The data aggregator applies to a system controlling charging infrastructure data in a given area and which can be inquired via GIREVE’s platform.

GIREVE, as a hub, manages the eMobility Services Platform which offers and ensures technical and functional means to standard services between the eMSPs, CPOs, and data aggregators.

eMobility Interopeational Protocol supports the following functionalities:

Roaming via hub - eMSPs, CPOs, and data aggregators join, based on web services, GIREVE’s roaming platform. The protocol documentation indicates GIREVE as the hub platform.

Authorization - eMIP offers several authorization processes.

Synchronous Authorization - check-in via the charge point (e.g. with an RFID card) or via the eMSP (e.g. an app).

Asynchronous Authorisation: Authentication Data Exchange. The eMSPs upload a list of approved subscribers to GIREVE’s platform. The list can be downloaded by CPOs. When charging at the charge point, e.g. via a RFID card, the CPO verifies the ID with the list provided.

Asynchronous Authentication Data Exchange & Synchronous Authorisation covers an event when CPOs do not download the list but request GIREVE to review the EV user ID. The decision on which authorization process to implement lies at the CPO's discretion.

Reservation - An EV driver can reserve a charge point via the eMSP app. (If the option is implemented and supported)

Billing - CDRs between CPOs and eMSPs are exchanged via GIREVE’s platform. This forms the foundation for invoicing. Via Asynchronous Exchange, the eMSP can download a CDR supplied by the CPO at any time, or via Synchronous Exchange - the eMSP gets quickly a CDR uploaded by the CPO.

Static charge point information - CPOs upload charge point information to GIREVE’s platform. GIREVE verifies the CPOs contract before updating their repository. The aforementioned data can be regained by CPOs, MSPs, and data aggregators. The information hold charge point ID, CPO, charge point manufacturer, charge point name, charge point location (address, geocode, type), time zone, opening times, current availability status, scheduled availability status, accessibility, tariffs, authorization modes, payment methods, charge mode, connector type, maximum power, guaranteed power, voltage, amperage, support contact, remote start/stop possible, reservation possible, and the time of the last update.

Real-time charge point information - GIREVE’s platform receives from CPOs the current availability status of the charge point. The CPOs agreement is verified before updating GIREVE’s repository. This includes scheduled status changes (e.g. for reservation).

Charge point search - The “charge point finder” function eMSPs can retrieve a list of charge points located in a given area and fulfill a set of charging criteria, (e.g. connector type).

Session information - Recorded and sent in the CDR - Charge Detail Record, covers the session ID, CPO ID, eMSP ID, EV user ID, charge point ID, contract ID, start and end time of charging session, metering report.

Real-time session information - With offered message service, CPOs can report events to eMSPs, and eMSPs can request actions while a charging session is in progress.

Remote start/stop - A charging session can be started or terminated by the eMSP.

Platform monitoring - GIREVE’s platform introduces a monitoring ability to check whether eMSPs, CPOs, and data aggregators have a valid connection to the platform. Specially designed “Heartbeat” tests the connection. The system sends “Heartbeat” requests to the associated companies.

EV roaming charging software of the e-mobility community

Privately held protocols offer great support and match users’ expectations. Joining at least one hub will be beneficial since emobility operators and providers can easily improve services and provide a top-notch experience. GIREVE and Hubject on a road to EV roaming extend charging infrastructure with additional user-friendly features. A cross-border network is on hand, and the support of emobility experts and industry leaders ensures the coherence and sustainability of the network. Keep in mind that even though both hubs are developing their individual protocols (OICP and eMIP), they also contribute to OCPI and OCHP growth.

OICP and eMIP refine the EV charging experience

The fact that both hubs were created at the initiative of automotive leaders makes the established EV charging e-roaming solution a guarantee of stability and accelerated growth of the whole network. Besides coverage of crucial functionalities, both protocols offer and develop additional services. The proof is in the numbers. Hubject operates on more than 50 markets on 4 continents and GIREVE offers a pan-European connection in nearly 30 countries. In light of the reality that the e-mobility market is growing rapidly and 2020 was a record year for electric car sales, it is expected that the scope of both hubs will continue to expand.

Actively supported two commercial open standards facilitating EV roaming. Discover cross-border e-mobility standards for accessible charging network.

EV roaming with open standards - OICP and eMIP

Get our comprehensive PDF packed with knowledge on eRoaming, hubs and protocols!

Certainly, roaming is something known to everyone at this point. However, what that has to do with eMobility?

Being a broad term for services allowing for connection outside of the usual network, roaming turns out to be an on-point solution for EV charging. With many players in the eMobility game (i.e. Charging Point Operators, eMobility Service Providers), some type of a connector is a must. Here’s exactly where eRoaming comes into play allowing for multi-dimensional connection between operators and EV drivers.

In short, eRoaming can be established via the use of hubs and protocols. A hub here can be an open platform which, after subscribing, can be used by many operators, who operate on common terms. This all happens in such a way that a certain charging pool introduced to a common hub can then be easily used by clients (EV drivers) of different providers. Such a solution allows electric vehicle users to charge their car across cities/countries with limited hussle.

In order to facilitate such a solution, the hubs developed their own open protocols, which are essentially responsible for the connection. They also define the functionalities of each eRoaming platform.

Amongst the existing hubs, we can differentiate three major ones. They all come with their own open standards and unify hundreds of CPOs and EMPs as well as millions of EV drivers.

The three biggest hubs and their protocols are:

(eMobility Inter-Operation Protocol - eMIP)

Apart from the proprietary protocols coming from hubs, it’s worth mentioning that there's also an independent one - 

Open Charge Point Interface Protocol (OCPI)

. It allows for eRoaming between the hubs as well as peer-to-peer connection.

To learn more about eRoaming, hubs & protocols, their importance and functionality as well as the future of eMobility - take a look at our exclusive paper covering all that needs to be covered on the topic!

eMobility Ecosystem Overview - video script

02 MARCH 2023 • 7 MIN READ