Refresh the knowledge on OCPP and see what changes have been implemented over the last years!

Piotr Majcher

 on OCPI. Given how widely read it was, we thought it’d be a good idea to continue the series on open protocols in the EV charging diligence.

Standing at the forefront of EV mass adoption, open standards and protocols are essentially responsible for the communication within the industry. They connect all involved parties (i.e. CPOs, EMPs, EVSE) altogether and allow for the data exchange, staying up-to-date and allowing for EV drivers to actually facilitate the charging sessions.

We have already covered quite a lot on the subject of open standards, for those interested, here’s the list of some entries so far:

EV roaming with open standards - OICP and eMIP

EV roaming with open standards - OCPI and OCHP


In this piece, all the focus goes into the Open Charge Point Protocol - OCPP.

OCPP has been developed by the Open Charge Alliance, a consortium of electric vehicle infrastructure providers, automakers, utilities, and other stakeholders. OCPP is a communication protocol used by charging stations and electric vehicle service providers. It enables two-way communication between the EVSE and CPOs, allowing for the monitoring and control of charging sessions.

OCPP is an open protocol, and anyone can develop applications that use it. Yet, it has not been officially deemed as standard, meaning that as much as OCA highly recommends using it, it’s not obligatory for EVSE manufacturers to produce hardware compliant with OCPP.

In terms of what it does, understanding of the OCPP placement in the entire ecosystem is crucial. As it has been stated earlier, OCPP is the syntax connecting the CSMS (Charging Station Management System used by CPOs to control their networks) with the actual hardware appliances (charging stations). Amongst operations covered by OCPP there are:

: enables identifying the EV driver and starting/finishing the charging event

: the charging event data is transferred to the backed system to define the chargers and bill the EV user accordingly

: CPOs can monitor the stations’ statuses (i.e. which are currently occupied, which have some issues detected)

Throughout the years, there have been a few versions of OCPP published. Two most recent ones are - OCPP 2.0 and 2.0.1. We’re gonna focus on these two, as they’re currently the most relevant.

In terms of the migration from the previous version (OCPP 1.6), we have covered that subject in this article. When it comes to OCPP 1.6, this version was enriched with multiple new features compared to its 1.5 predecessor (now mostly out of use). As we read in the documentation, to OCPP 1.6 there have been added:

A binding to JSON over WebSocket as a transport protocol is added, reducing data usage and enabling OCPP communication through NAT routers, see: OCPP JSON Specification

Extra statuses are added to the ChargePointStatus enumeration, giving the CPO and ultimately end-users more information about the current status of a Charge Point Structure of MeterValues.req is changed to eliminate use of XML Attributes, this is needed for support of JSON (no attribute support in JSON).

Extra values are added to the Measurand enumeration, giving Charge Point manufacturers the possibility to send new information to a Central System, such as the State of Charge of an EV

The TriggerMessage message is added, giving the Central System the possibility to request information from the Charge Point

A new Pending member is added to the RegistrationStatus enumeration used in BootNotification.conf

More and clearer configuration keys are added, making it clearer to the CPO how to configure the different business cases in a Charge Point

The messages and configuration keys are split into profiles, making it easier to implement OCPP gradually or only in part

Known ambiguities are removed (e.g. when to use UnlockConnector.req, how to respond to RemoteStart/Stop, Connector numbering)

(please note, this extract comes from the OCPI 1.6 documentation and can be downloaded in full from their website)

Now let’s focus on the two latest versions. OCPP 2.0 was first introduced in April 2018. Since then, some issues have been found. As it turned out, some of the problems couldn't have been solved by fixing textual nuances in the documentation and needed bigger changes, to the point where they weren’t backward compatible. This included i.e. messages improvements (like the length of the security message certificate which happened to be too short). This is when OCPP 2.0.1 was introduced and it's recommended by OCA to use this one only.

As the OCPP standard continues to evolve, it is important for charging station operators to stay up-to-date on the latest version of the OCPP protocol. Doing so will ensure that their charging stations are compatible with the latest CSMS software and able to take advantage of the newest OCPP features.

In terms of how OCPP 2.0 followed by 2.0.1 have changed compared to OCPP 1.6, there’s been some major changes. First and foremost an ISO 15118 support has been introduced. In return, this has opened up the possibilities such as the Plug and Charge functionality. In the newest version SOAP is no longer supported as it has been entirely replaced by JSON websockets. There have also been some major improvements in the security area. Amongst some slightly smaller changes,

device management & monitoring replaced formerly used Status Notifications. The transaction handling has been improved so that it could support bigger and more complex networks.

The official OCPP documentation consists of 7 parts:

JSON over WebSockets implementation guide

Open Charge Point Protocol

See details of the upcoming event and the Innovation stage we'll get the chance to lead!

Martyna Tonia

At Solidstudio, we got the chance to attend many conferences, it’s time to start sharing at least some of them!

In less than a week we’ll get a chance to lead the Innovation stage at the Intercharge Network Conference in Berlin, Germany.

The 10th edition of the Hubject’s event known to be the biggest eMobility meetup in this part of the world is certainly a huge opportunity to meet the most eminent players in the field as well as catch up with some of our partners from different countries.


Given the fast-changing nature of eMobility and all faced obstacles, we’re thrilled to see events of that scale being organized and attended by so many people! As stated by the organizators:

“We need to unravel the digital DNA of eMobility, to understand the different strands that interlink into one coherent, functioning, evolving system.”

After 4 years devoted strictly to the EV industry, we couldn’t agree more. Besides, a similar approach has accompanied us throughout all these years of implementing open standards and looking for the best solutions in digital products.

As mentioned earlier, Solidstudio will lead the Innovation stage. It’s to no surprise as innovation plays a humongous role in tech solutions, much like the ones we’re delivering whether they are the CPO backend systems or EMP apps for the end-users.

Innovative approach has been leading us since the very first moment of deciding that eMobility was supposed to be our main field of interest and we’re especially excited to be sharing some thoughts on it along with our great guests!

Our stage will take place through both of the conference days - 12th and 13th of September.

We welcome everyone to come and say hi, enjoy the presentations and exchange some thoughts on the industry. We will have our tech and business representatives, so no matter whether it's a technical or partnership inquiry, we’ll get you covered!

Solidstudio news! The ICNC22 conference

See what's behind the electronic system that controls the lithium-ion batteries in EVs

Paweł Głogowski

, we’ve briefly touched upon some of the emerging technologies in the world of eMobility. One of them (admittedly, not-so-emerging as it's been going on for a while) was the 

 used in EVs. It’s now time to shed some more light on what it is.

Surely, the batteries may be regarded as the core of any electric vehicle. Essentially, it is what gets the car going. It’s also what determines to a great extent how appealing an EV can get for the potential buyers. Thus, ensuring the battery runs smoothly, safely and efficiently is paramount in the EV formation process. Here’s where BMS kicks in.


) is a system that monitors and manages a rechargeable battery (or group of batteries), such as those found in electric vehicles, UPS systems, and solar energy storage systems.

The BMS is responsible for protecting the battery from operating outside its safe limits, maximizing its lifespan, and providing accurate information about the battery's state of charge, state of health, and current capacity. 

In short, its primary functions can be narrowed down to ensuring the battery remains safe and reliable.

A BMS typically consists of a control unit, sensors, and connection wires. The control unit may be a separate device or integrated into the battery pack. The sensors monitor various parameters of the battery, such as voltage, current, temperature, and state of charge. The connection wires carry power and data between the battery and the BMS.

The control unit uses the information from the sensors to determine when to charge or discharge the battery, how much power to allow in or out, and whether the battery is operating within its safe limits. If the battery is operating outside its safe limits, the BMS will take action to protect the battery, such as disconnecting it from the load or shutting off power altogether.

The BMS may also provide information about the battery to a user or system, such as the current state of charge, state of health, and remaining capacity. This information can be used to optimize the performance of the system in which the battery is used.

A BMS typically includes safety features to protect the battery, such as overcharge and over discharge protection, short circuit protection, and thermal runaway protection. These safety features help to prevent damage to the battery and ensure that it operates safely.

The BMS may also include features to maximize the lifespan of the battery, such as balancing. Balancing equalizes the voltage of the cells in a battery pack, which helps to prevent capacity loss and extends the lifespan of the battery.

Battery management systems are used in a variety of applications, including electric vehicles, UPS systems, and solar energy storage systems. BMSs are an important part of these systems, as they help to protect the battery from damage, extend its lifespan, and provide accurate information about the battery's state.

With lithium-ion, an average battery module consists of packs of single battery cells. That is because a singular cell doesn’t hold enough capacity to power the bigger establishments. In such cases (where there are multiple modules connected to make up for a battery) monitoring and managing becomes rather complicated, as the singular cells can charge differently.

BMS collects data gathered from the batteries (in real-time) and based on the information it acts accordingly. Amongst the parameters collected  there are:

Once these are collected, the BMS system will process it. The outcomes of such processing is the below data:

State of charge (SOC)- an estimation of how much charge the battery currently has - while in use

State of health (SOH) - an estimation of the capacity/condition of the battery, it measures how well the battery is able to hold a charge

Issues - monitoring and addressing any recognized malfunctions

Based on the outputs, the BMS then takes action to protect the battery, such as turning off charging when the SOC is full or shutting down the system when a cell is over temperature.

There are two main types of BMSs. The first is a 

, which uses one control unit to manage all of the battery cells in the system. The second type of BMS is a 

, which uses multiple control units to manage the battery cells in the system.

The main advantage of using a centralized BMS is that it is simpler and cheaper to design and build. The main disadvantage of using a centralized BMS is that if the control unit fails, the entire system will fail.


The main advantage of using a distributed BMS is that it is more resilient and can continue to operate even if one or more of the control units fails. The main disadvantage of using a distributed BMS is that it is more complex and expensive to design and build.

Which type of BMS is best for a given application depends on the specific requirements of the application. For example, if cost is the primary concern, then a centralized BMS may be the best choice. If reliability is the primary concern, then a distributed BMS may be the best choice.

In terms of the use of BMS in automotive, it doesn’t differ from any other means. It helps to ensure that the battery pack lasts for as long as possible and performs at its best. A well-designed BMS can make the difference between a battery pack that lasts for years and one that needs to be replaced frequently. This can have a significant impact on the overall cost of ownership of an electric vehicle.

Amongst the vital aspects that get covered by BMS in EVs, there are:

Thermal management - much like any other batteries, the ones installed in EVs can overheat. With thermal management, the censor units control the temperature and, if it get too high, they trigger the cooling mechanisms

Discharge and charge control - the primary function of any BMS is to protect the cells within the battery pack from being over-discharged or overcharged. To do this, the BMS will cut off the discharge path when the cell voltage drops below a certain threshold, and will also cut off the charging path when the cell voltage reaches a higher threshold.

Battery balancing - In order to ensure that all the cells in the battery pack are at the same voltage, the BMS will occasionally "balance" them by equalizing the voltages of all the cells. This is usually done during charging, when the cell voltages are highest.

Communication and Safety monitoring - Some BMS systems also have a communication interface that allows them to be connected to a computer or other devices. This can be used for firmware updates, data logging, or even remote control of the BMS. Additionally, BMS systems have built-in safety features that can monitor the system for faults and take appropriate action if a problem is detected.

Battery Management System (BMS)

Learn about the wireless EV charging and its possibilities and obstacles.

Grzegorz Bar

It wasn't that long ago when electric cars were nothing short of a pipe dream and a daring vision of the future. It didn't take that much time for it to become the new reality, still in development, but definitely no longer a futuristic delusion. As much as there's yet a lot of work at the grass root to be carried out, especially in terms of the charging infrastructure, major technological advancements can be observed at any level of eMobility undertakings.


This is further true when we take a closer look at some of the latest trends in eMobility. We can see that many new technologies are being developed to make electric cars more efficient, more reliable and cheaper to maintain. Some of these trends include:

- allows for the quick and easy exchange of batteries in electric vehicles. This means that drivers will no longer have to wait for their batteries to charge, which will make electric cars more convenient to use.

 - allows drivers to charge their electric vehicles without having to plug them into a charging station. instead, they can simply place their car on a special pad that will wirelessly charge the battery.

 - allows electric vehicles to be charged by the sun. Solar panels can be used to collect solar energy and then convert it into electrical energy that can be used to charge an electric vehicle. This renewable source of energy will make it easier for people to use electric cars.

Electric Vehicle Battery Management Systems

 - helps to keep electric vehicle batteries healthy and working properly. These systems can monitor the battery's health, charge level, and temperature. They can also help to extend the life of the battery.

 - can charge an electric vehicle's battery in a matter of minutes. This will make it easier for people to use electric cars, as they will not have to wait long for their batteries to charge.

 - these cars are connected to the internet and can drive themselves

Big Data and Predictive Analytics for Electric Vehicles

 - can help to predict when an electric vehicle will need to be charged. It can also help to find the best route for an electric vehicle to take.

Blockchain Technology for Electric Vehicles

 - can help to secure data about electric vehicles. It can also help to provide a way for people to pay for electric car charging.

 - can help to create a network of electric vehicles that can provide power to a grid

In this entry, wireless charging is what we’re going to focus on. First, let’s see what wireless charging is in general. Wireless charging is a technology that allows devices to be charged without the need for a physical connection (i.e. through the cable). This means that instead of plugging your device into a power outlet, you can simply place it on a wireless charging pad.  What's interesting is that the first prototypes of such technology were created by Nikolai Tesla, back in the late 1800's, when he managed to transmit the electricity through air.

Wireless charging technology uses an electromagnetic field to transfer energy between a charging pad and a device. The charging pad is connected to a power outlet, and the device has a built-in receiver that converts the energy into electricity that can be used to charge the battery. This is accomplished by using a copper coil, which creates an oscillating magnetic field. The receiver then converts the current into DC power, which is used to charge the battery.

There are mainly two types of wireless charging: inductive and resonant. Inductive charging is the most common type, and it uses magnetic fields to transfer energy between the charger and the device. Resonant charging uses electromagnetic resonance to transfer energy, and it is less common.

Now, how does it work for EVs? There isn’t any difference to how this happens with electric cars. The car charging session starts when electricity is transferred from one magnetic coil in the charger to another by way of an induction process. The coils need both be aligned with each other, which means that the driver has to park directly over it to enable the charging event. The wireless chargers come in the shape of a flat pad, making it relatively easy to maneuver the car over them.


Wireless EV charging is still in its infancy but there are already a few companies working on the technology, including big automotive players like BMW or Volvo. The big obstacle in working with wireless charging is the lack of broad, widely-accepted standardization. Here’s where The Society of Automotive Engineers has come to help by developing a standard for wireless EV charging, which should help to speed up the adoption of the technology.

SAE J2954 is the aforementioned standard for wireless EV charging. In the official documentation about the standard we read:

“ The SAE J2954 standard establishes an industry-wide specification that defines acceptable criteria for interoperability, electromagnetic compatibility, EMF, minimum performance, safety, and testing for wireless power transfer (WPT) of light-duty plug-in electric vehicles. The specification defines various charging levels that are based on the levels defined for SAE J1772 conductive AC charge levels 1, 2, and 3, with some variations. A standard for WPT based on these charge levels enables selection of a charging rate based on vehicle requirements, thus allowing for better vehicle packaging and ease of customer use. The specification supports home (private) charging and public wireless charging.”

The charge levels mentioned above are (at least for now): 3.7kWh, 7kWh and 11kWh, leaving the room for improvements in this area for sure. The standard’s development took almost a decade, meaning that the upcoming changes may take a bit of time to be included.

Wireless EV charging - the benefits and the obstacles

For as long as wireless charging remains in its infancy, it's a bit hard to speak about the advantages, as currently there aren't many in practical use. Although, it doesn't mean that the technology itself won't have much to offer in case it gets developed to the point of mass adoption.

Wireless charging for electric vehicles would be a convenient and efficient way to keep your car charged without the hassle of dealing with cords and plugs or finding a parking spot near a charging station. Wireless charging would make a perfect case scenario for electric taxis or buses, which all have their frequent stops. Such an undertaking is already taking place in Gothenburg, Sweden. The pilot project involves a fleet of taxis (consisting of the electric Volvo XC40s) and a suite of charging pads developed by an US company - Momentum Dynamics. The chargers are installed in specially prepared parking spaces. Such a venture allows not only for the electric taxi fleet to remain charged but also makes up for a great test-environment to gather the data, learn about some issues and implement solutions.

However, before we ever get to witness and enjoy the giftings of wireless charging, there are some quite substantial obstacles to overcome.One of the biggest obstacles to widespread adoption of wireless EV charging is the lack of infrastructure. Wireless chargers need to be installed in convenient locations where EV owners can easily access them, and right now there are very few public places that offer wireless charging. This means that most people who want to use wireless charging will have to install a charger at their home or workplace, which can be expensive and time-consuming.

Wireless charging technology is still in its early stages of development, and there are a number of technical challenges that need to be overcome before it can be widely used. For example, current wireless chargers can only transfer a limited amount of power, which means that they can take a long time to charge an EV. These technical challenges are being addressed by research and development, but it will take some time before they are resolved.

Wireless charging technology is currently more expensive than traditional wired charging, both in terms of the initial cost of the equipment and the cost of installation. This is one of the main reasons why wireless charging has not been more widely adopted so far. However, as the technology develops and becomes more widespread, the costs are likely to come down.

There are some safety concerns associated with wireless EV charging, as the chargers emit electromagnetic fields (EMFs). Although there is no evidence that EMFs are harmful to humans, some people are still worried about the potential health effects. These concerns need to be addressed before wireless charging can be fully accepted by the public.

Wireless EV charging is a promising technology that has the potential to make EV ownership more convenient and reduce the environmental impact of transportation. However, there are a number of obstacles that need to be overcome before it can be widely adopted. These include the lack of infrastructure, technical challenges, cost, safety concerns, and the lack of standardization. With continued research and development, these obstacles can be overcome and wireless charging can become a mainstream technology.

Wireless EV charging

Get our informative PDF on ISO 15118 and learn more about the standard.

Please note, this is just the introductory part. The full piece can be downloaded for free from the box on the right side of the page.

Interoperability and standardization have become a big part of the EV transformation. As the industry evolves, more and more players come to the game, bringing new developments and ideas. With that, the entire ecosystem undergoes massive changes and it may get difficult to keep track of what’s happening.

That way, interoperability is critical for eMobility. 

Open standards are necessary to ensure that different types of electric vehicles can interoperate with each other and with the infrastructure that supports them, which is run by multiple CPOs and EMPs.

ISO 15118 is an international standard that defines the communication protocols and data structures used in electric vehicle charging. It specifies the two-way communication between Electric Vehicles (EV), including Battery Electric Vehicles and Plug-In Hybrid Electric Vehicles, and the Electric Vehicle Supply Equipment (EVSE).

Communication protocols and data structures

ISO 15118 is designed to be interoperable, meaning that EVs and EVSEs from different manufacturers should be able to communicate with each other. The standard is also designed to be scalable, so that it can be used for both residential and public charging stations.

It enables interoperability between electric vehicles and charging stations, and allows for sophisticated features such as billing based on time of use or energy consumption. ISO 15118 also provides a framework for charging station operators to manage access control and load balancing.

ISO 15118 is built upon Public Key Infrastructure (PKI)

, which means  electric vehicles can be identified and authenticated. This authentication can take place before, during or after a transaction.

The standard is built out of 8 parts, each defining a different aspect covered by ISO 15118 as a whole.

To learn more about ISO 15118, its specifications and features as well as how it works and what are the documents defining each functionality, download the paper from the box on the right side of the page.

ISO 15118 - what is it?

We're shedding the light on what to choose when facing a hosting dilemma.

Magdalena Betlińska

The right decision-making in business certainly plays a crucial part in ensuring the most optimal operation. When it comes to software solutions, decisions to be made are coming in nearly every step of the way, whether it’s the project management or the product development itself. We have already covered one dilemma - 

It’s time to now look at another hot topic. 

It’s nothing else than choosing the way a digital product is bound to be stored. As much as it sounds rather straightforward, there’s quite a bit of hustle in making the best decision. The analysis of business requirements must be done in order to choose between two approaches (given it’s reduced down to the choice between on-prem and cloud). Once this has been decided, one needs to find a reliable technology partner who can provide them with services of varying levels according to their preference. The process for selecting an appropriate strategy starts by determining what type or technologies are most suitable based on the organization’s anticipated needs.

Now, let’s take a closer look at what these two really are.

On-premise - what does it mean and how does it work?

On-premise software deployment means that the software is installed and deployed on the customer's own premises, usually within their own organization. The customer is responsible for managing and maintaining the on-premise software system. On-premise systems can be either physical or virtual.

 has allowed for greater flexibility in on-premise software deployments. With virtualization, customers can run multiple virtual machines (VMs) on a single physical server. This can provide significant cost savings compared to traditional on-premise deployments, where each application would require its own dedicated server.

On-premise software deployments are typically used by organizations that have specific needs that cannot be met by other deployment types, such as SaaS. Organizations that use on-premise software deployments typically have in-house IT staff who are responsible for managing and maintaining the system.

On-premise software deployments are typically more expensive than other deployment types, such as Software as a Service (SaaS). This is because the customer is responsible for all of the costs associated with managing and maintaining the system, including hardware, software, and IT staff. Despite the higher upfront cost, on-premise deployments can provide greater control and flexibility for customers. With on-premise systems, customers can customize the software to meet their specific needs and requirements. They are also not subject to the same level of service outages that can occur with cloud-based systems.

On-premise hosting - benefits and disadvantages

In terms of the benefits of the on-premise solutions, there are:

: with an on-premises solution, the organization has full control over its data, as it is stored locally.

: on-premises solutions can be customized to a greater extent than cloud-based solutions, as they are not subject to the same restrictions.

: on-premises solutions can offer greater security than cloud-based solutions, as they are not accessible from the internet.

 an on-premises solution can be used without any internet connection, as all the hardware and software are stored on-site.

When it comes to the disadvantages, we can differentiate:

 on-premises solutions can be more expensive than cloud-based solutions, as they require the purchase of hardware and software, and the hiring of IT staff.

 on-premises solutions can be more complex to set up and maintain than cloud-based solutions.

 on-premises solutions can be less flexible than cloud-based solutions, as they are more difficult to scale up or down.

 implementation is a time-consuming process that takes longer due to the need for server installations.

Cloud computing - what does it mean and how does it work?

In its simplest form, cloud computing is the delivery of software and IT services over the internet. This means that instead of having a program installed on your computer or server, you can access it, or store it, ‘in the cloud’.Cloud computing services are provided by specialist providers (known as ‘cloud providers’), who make their services available to customers via the internet. Customers can then access these services as and when they need to, using any internet-connected device.Some of the most popular cloud computing services include:


 This is where files and data are stored ‘in the cloud’, instead of on your computer or other device. Popular examples include iCloud (used by Apple devices) and Google Drive.

 This is where your files and data are backed up ‘in the cloud’, as well as (or instead of) on your own computer or other device. This can give you an extra layer of protection in case your computer or device is lost, stolen, or damaged.

 This is where software and applications are hosted ‘in the cloud’, instead of on your own computer or server. This can include everything from office suites and project management tools to email and customer relationship management (CRM) systems.

 This is where websites are hosted ‘in the cloud’, instead of on your own web server.

Cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.

In general, one can oftentimes meet three service models and four deployment models described for cloud computing.

: The capability provided to the consumer is to use the provider’s applications running on a cloud infrastructure. The applications are accessible from various client devices through either a thin client interface, such as a web browser (e.g., web-based email), or a program interface. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.

: The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.

: The capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).

The cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.

The cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.

The cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).

 The cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on-premises or off-premises.

Cloud hosting - benefits and disadvantages

When it comes to the benefits of cloud solutions, there are:

 Cloud solutions eliminate the need for these upfront investments, and instead use a subscription-based pricing model. This can lead to significant cost savings, especially for businesses that are growing rapidly.

Cloud solutions are very flexible and can be easily scaled up or down to meet the changing needs of your business.

 Cloud solutions make it easy for employees to share files and work on projects together. This is because the files are stored on a central server that can be accessed by anyone with the proper permissions.

 With on-premise solutions, you are responsible for ensuring that your data is backed up and secure. However, with cloud solutions, this responsibility is typically taken care of by the service provider. This can lead to increased peace of mind and improved security for your business.

However, there are also some disadvantages to using cloud solutions, including:

 When you use a cloud solution, you are relying on the service provider to keep your data safe and secure. This can lead to reduced control over your data and your business’s destiny.

 While cloud providers are typically very reliable, there have been occasional outages that have caused businesses to lose access to their data.

 When you use a cloud solution, you are essentially outsourcing a critical part of your business to a third-party. This can lead to increased dependence on the service provider and can make it difficult to switch providers if you are dissatisfied with the service.

On premise vs cloud - the comparison in short

On-premise software is installed and runs on the company's own servers. This gives the company full control over the software and its data, but it also means that the company is responsible for maintaining and updating the software. On-premise software can be more expensive to set up and run than cloud-based software, but it can offer better security and performance.

Cloud-based software is hosted on the provider's servers and accessed over the internet. This type of software is usually cheaper to set up and run than on-premise software, and it can be easier to scale up or down as needed. However, the company does not have full control over the software or its data, and it is reliant on the provider for maintenance and updates.

On premise vs cloud computing - the breakdown

Learn about the plug and charge technology and see how it simplifies the charging experience.

In the last few years, there have been plenty of ameliorations introduced to ease the EV charging experience. Whether it’s hardware or software, major changes for the better can be observed even in places where eMobility does not have its wings spread with a full potential. Yet, even the major progress in EV charging technology, doesn’t stop frequent comparisons to what it looks like with maintaining an ICE car, which tends to be described as less complicated and simply easier.

Luckily, this view is being gradually changed by technologies implemented into the world of EV charging. In this article, we’ll take a closer look at one of the most promising charging-simplifying facilities.

allows for an EV charging event without the necessity of additional means, such as RFID cards or apps.

 With Plug and Charge, the data exchange between a charger and an electric vehicle occurs entirely automatically. This includes the authentication and authorization processes. It makes the charging process much more convenient for drivers. They don’t have to worry about connecting their vehicle to the charger or starting the charging process manually. In addition, Plug and Charge also offers improved security, as the data exchange between charger and vehicle is encrypted. It makes an EV charging experience more similar to fueling an ICE car, which does not require a sequence of minor actions to authorize a charging session.

The technology behind Plug and Charge is based on the 

. This standard defines the communication protocols and data formats that are necessary for an automated, interoperable charging process (more about it in the next section).

In order to use Plug and Charge, an electric vehicle must be equipped with a so-called Charging Control Unit (CCU). The CCU is the interface between the vehicle and the charging station. It manages the data exchange with the charger and controls the charging process. What must be remembered is that plug and charge facilitates the communication between all parties involved in the charging process, that is:

In simple words, with Plug and Charge compatible devices, the EV contains provisioning certificate and contract certificate (between the driver and EMP) and charging station contains EVSE certificate.User is identified by the ID called E-Mobility Account Identifier (eMAID) stored in the contract certificate. eMAID is also known to the eMSP for billing purposes. Thanks to that, eMSP knows which user has to be charged for the transaction started automatically just by plugging the cable. The moment an EV cable is plugged into the socket, the charging station identifies the car's certificates and vice versa.

When plugging in at a Plug and Charge enabled charger, the CCU will automatically initiate the data exchange with the charger. This includes exchanging information about the maximum current that can be drawn, the maximum voltage that can be applied, and the plug type.

Based on this information, the charger will adapt its settings accordingly. Once the connection is established, the charger will start supplying electrical energy to the vehicle. The entire process happens automatically and doesn’t require any interaction from the driver.

ISO 15118 is a joint venture of the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) and one of a group of standards for electric vehicles. It describes the communication between a vehicle and a charging point. It has few use cases and Plug and charge is one of them.



Whole ISO 15118 is built upon Public Key Infrastructure. In Plug and Charge - The EV has the contract certificate stored (X.509 certificate). The certificate associates the end-user with the public key. Because the certificate is issued by a trusted Certificate Authority, the charging station is able to check it, and if it’s valid, the charging station believes that the user presented in the certificate is not fake. The standard ensures high security of the data exchange amongst all involved parties. The security is provided via authenticity (the verification of certificates) and confidentiality (data exchange happening via encrypted channels).

As it rapidly gains popularity amongst eMobility-related operators, ISO 15118 can be deemed one of the crucial means in ensuring the seamless operation in the world of EV charging.

In terms of its other use cases, we dive deeper into the smart charging and V2G functionalities and importance in our recent downloadable guide 

OPCP is an open standard launched by Hubject. The launch of OPCP simplifies the process of adopting the Plug and Charge technology for developers and eMobility stakeholders looking to deliver the best solutions for EV users. Standardization of said technology is a great step towards increased interoperability and unification across the industry.

Being an open protocol, OPCP gives everyone interested the opportunity to utilize Plug and Charge technology. As stated by Hubject:

“This measure is particularly relevant because the rapidly growing market for Plug&Charge results in a range of very different processes from different manufacturers. After all, unhindered access without lock-in effects will be an essential criterion for Charging Station Operators and Mobility Service Providers, offering charging solutions. In addition, qualities such as the simple and secure authentication methods for different applications and the option for further joint development in cross-sector mode are convincing. Furthermore, the opportunity for multi-contract handling is given. Multiroot handling is also implemented and compliant with ISO15118-20.”

The protocol is constantly being developed and Hubject invites any feedback and improvement ideas.

OPCP is in productive use since 2019 and is gaining more and more users amongst Charge Point Operators, eMobility Service Providers and OEMs.

It’s to no surprise, as the launch of OPCP opens the door for many to enjoy the benefits of the technology., making the charging experience a lot more effortless for the end-customers - EV drivers.


The protocol covers the following use-cases:

 (Root Certificate Pool: used for communication between the Root Certificate Pool and the various Certificate Authorities of ISO 15118 participants (V2G, OEM, MO, CPS)

 (The Provisioning Certificate Pool: providing interfaces to exchange Provisioning Certificates between OEMs and MOs)

Let’s read our posts

Open Charge Point Protocol

Recommended

eRoaming Hubs explained

Why does software matter in eMobility?

All about Smart Charging

Solidstudio news! The ICNC22 conference

Battery Management System (BMS)

Wireless EV charging

ISO 15118 - what is it?

On premise vs cloud computing - the breakdown

Plug and charge - a seamless charging experience.