Fransiscus Setiawan

Technical articles on AI agents, Azure, .NET, architecture, and EV charging systems from Sydney.

Category: EV & Smart Mobility

Architecting Scalable OCPP Compliant EV Charging Platforms

By

On April 29, 2025

In EV & Smart Mobility

Architecting Scalable OCPP Compliant EV Charging Platforms

  • Understanding OCPP: A pivotal standard for interoperability in charging networks.
  • Benefits: Highlights include hardware agnosticism, interoperability, and enhanced security.
  • Key Components: Focuses on backend design, CSMS, and certification compliance.
  • Real-World Examples: Showcases implementations by EV Connect and AMPECO.
  • Future Considerations: Emphasizes upgradeability, scalability, and evolving security needs.

Table of Contents

Understanding OCPP

The Open Charge Point Protocol (OCPP) serves as the communication backbone between EV chargers and Charging Station Management Systems (CSMS). By facilitating interoperability, OCPP allows network operators to seamlessly integrate different brands of charging stations into a unified ecosystem. As a widely embraced standard, OCPP is crucial in establishing cohesive charging networks without being constrained by vendor-specific technologies.

Currently, multiple versions of OCPP are in play:

  • OCPP 1.5: The initial version that introduced basic functionalities for communication between chargers and CSMS.
  • OCPP 1.6: A more robust version adding features like improved error handling and enhanced security protocols.
  • OCPP 2.0.1: The latest iteration emphasizing advanced security and additional capabilities, which offers certifications for core and advanced modules through the Open Charge Alliance (OCA).

With the impending rollout of more certification modules in March 2025, OCPP compliance is set to become an industry-standard requirement that platform architects must consider when designing scalable charging solutions.

Benefits of OCPP-Based Architecture

Hardware Agnosticism

One of the standout features of OCPP is its ability to enable hardware-agnostic charging platforms. Network operators can integrate any OCPP-compliant charger, independent of the manufacturer. For instance, AMPECO’s platform claims compatibility with over 70 leading charging station manufacturers, emphasizing OCPP’s flexibility and adaptability. This characteristic allows businesses to scale their operations without being locked into a specific vendor’s ecosystem, providing freedom for future growth and innovation.

Interoperability and Future-Proofing

Adopting OCPP standards is pivotal for ensuring that charging networks remain compatible across generations of equipment. By focusing on OCPP compliance, operators mitigate the risk of fragmented systems that could render investments obsolete when technology advances. This forward-thinking approach is essential for maintaining competitive advantages in a fast-evolving marketplace.

Security Enhancements

With OCPP 2.0.1, security is elevated to new heights. The implementation of advanced security modules helps safeguard charging networks against emerging threats. For example, EV Connect’s OCPP 2.0.1 certification signifies a commitment to robust security measures, ensuring that as charging infrastructures scale, they retain their integrity and protection against potential vulnerabilities.

Key Components for Scalable Architecture

Architecting a scalable, OCPP-compliant platform necessitates careful consideration of several key components:

Backend System Design

A robust backend design is crucial for supporting multiple OCPP versions concurrently. Given that charging networks often incorporate a mix of equipment operating on different protocol versions, the architecture must be flexible and capable of handling various communication standards. For instance, AMPECO’s platform supports a triad of versions: OCPP 1.5, 1.6, and 2.0.1, demonstrating the importance of backward compatibility in charging network design.

Charging Station Management System (CSMS)

The CSMS acts as the nerve center for the entire charging network, directing communication between connected charging stations and managing their operational status. This component must be designed for horizontal scalability, enabling additional charging points to be integrated seamlessly as demand grows.

Certification Compliance

Pursuing official OCPP certification through the OCA is vital for ensuring interoperability and long-term viability. A certified platform is not only a mark of quality; it also guarantees adherence to global standards, laying the foundation for seamless integration with certified charging hardware. This compliance is fundamental for engendering trust among network operators and users alike.

Real-World Implementation Examples

EV Connect’s OCPP 2.0.1 Implementation

In March 2025, EV Connect announced its achievement of OCPP 2.0.1 certification for both Core and Advanced Security modules. This milestone illustrates their dedication to open standards and the interoperability of their solutions. By leveraging OCPP compliance, EV Connect enhances user experiences through a reliable and efficient charging ecosystem, marking a significant step toward long-term stability and adaptability in the industry.

AMPECO’s Multi-Version Support

AMPECO’s EV Charging Platform stands out as a prime example of scalable architecture capable of supporting multiple OCPP versions simultaneously. Their hardware-agnostic approach allows them to integrate diverse manufacturers through OCPP compliance, proving the viability and flexibility of their solution. Such an adaptable architecture is essential for operators seeking to broaden their network without compromising on service quality.

Future Considerations

When designing scalable OCPP-compliant platforms, architects and engineers must contemplate several key future-oriented factors:

  • Future Upgradeability: Establish a framework that allows for seamless upgrades to future OCPP versions without requiring a complete overhaul.
  • Backward Compatibility: Ensure that newer systems can still interact with older OCPP implementations, preserving existing investments.
  • Scalability: Design systems that can efficiently handle thousands to millions of charging sessions, accommodating growth trajectories as EV adoption rises significantly.
  • Evolving Security Protocols: Regularly update security measures to keep pace with emerging threats and standards in the cybersecurity landscape.
  • Integration with Energy Management Systems: Explore the potential for integrating charging platforms with broader energy management infrastructures for optimized performance and resource utilization.

Summary

In conclusion, designing scalable OCPP-compliant EV charging platforms involves intricate knowledge of the OCPP standard and its implications for interoperability, security, and future-proofing. As the EV market continues its rapid expansion, architects must emphasize the importance of building robust, flexible, and certification-compliant systems that can support a diverse ecosystem of charging stations.

By leveraging OCPP standards, businesses can forge ahead in developing agile, adaptable charging infrastructures that are not only capable of handling present demands but are also well-prepared for future innovations in the electric vehicle landscape.

If you’d like to discuss innovative approaches to OCPP compliance or explore architectural strategies for your next project, connect with me on LinkedIn, or check out my GitHub for implementation examples!

FAQs

What is OCPP?

OCPP stands for Open Charge Point Protocol, which is a communication standard that allows for interoperability between electric vehicle chargers and management systems.

Why is security important in OCPP?

Security in OCPP is vital to protect charging networks from cyber threats and to ensure the integrity and reliability of EV charging systems.

How does hardware agnosticism benefit operators?

Hardware agnosticism allows operators to choose among various OCPP-compliant chargers without being locked into a specific manufacturer, enhancing efficiency and scalability.

What are the key features of OCPP 2.0.1?

Key features of OCPP 2.0.1 include enhanced security protocols, better error handling, and the ability to support a broader range of functionalities for charging stations.

OCPP 1.6: The Unsung Hero Powering Your EV Charge (But It’s Getting a Major Upgrade!) – A Deep Dive

By

On March 22, 2025

In EV & Smart Mobility

Ever pulled up to a charging station, plugged in, and watched your electric vehicle magically start to juice up? That seamless experience isn’t magic; it’s the result of a communication protocol called OCPP – the Open Charge Point Protocol. And for a significant chapter in the EV revolution, version 1.6 was the quiet workhorse behind the scenes, ensuring smooth communication between your car and the charging infrastructure. Think of it as the universal translator that made charging stations and management systems speak the same language.

Why Should You Care About OCPP 1.6? (Even If “Protocol” Sounds Like Tech Jargon)

Let’s be honest, “protocol” doesn’t exactly scream excitement. But here’s why OCPP 1.6 mattered, and why it’s worth a quick chat:

  • Charging Anywhere, Anytime: Imagine if your phone only worked with certain cell towers. Chaos, right? OCPP 1.6 prevented that in the EV world. It meant you could plug into a wider range of chargers, regardless of who made them or managed them.
  • Remote Control for Operators: Think of charging station operators as air traffic controllers for electricity. OCPP 1.6 gave them the ability to monitor, control, and update stations remotely. This meant faster fixes, better service, and even dynamic pricing adjustments.
  • Data-Driven Optimization: OCPP 1.6 allowed for the collection of valuable data on charging patterns. This data helped operators understand usage, optimize pricing, and improve the overall charging experience.

Taking a Slightly Deeper Dive (But Still Keeping it Real)

So, how did this “universal translator” actually work? It broke down charging tasks into manageable “profiles,” like departments in a well-organized company:

  • Core Profile: The Front Desk: This is where the basic interactions happened: verifying user IDs, starting and stopping charging sessions, and reporting energy usage. Messages like Authorize, BootNotification, and MeterValues handled these crucial tasks.
  • Firmware Management: The IT Department: Keeping charging stations up-to-date is vital for security and functionality. This profile allowed for remote firmware updates, ensuring stations were running the latest software.
  • Local Authorization List: The Offline Backup: Ever lose internet connection? This profile allowed charging to continue even when the network was down, using a local list of authorized users.
  • Reservation Profile: The Booking System: This allowed users to reserve charging slots, ensuring a spot was available when needed.
  • Smart Charging Profile: The Energy Optimizer: This profile enabled dynamic energy management, balancing grid load and optimizing charging schedules.
  • Remote Trigger Profile: The On-Demand Information Request: This allowed the central system to request specific data from the charging station whenever needed.

Understanding Message Structure: JSON (OCPP-J)

Since JSON is the more prevalent format in OCPP 1.6, let’s focus on that. Remember, JSON messages are structured as arrays with four key elements:

  1. MessageTypeId: Indicates the message type (2 = CALL, 3 = CALLRESULT, 4 = CALLERROR).
  2. UniqueId: Matches requests and responses.
  3. Action: The OCPP message name (e.g., “Authorize,” “MeterValues”).
  4. Payload: The message’s data in JSON object format.

Example Messages:

  1. Authorize Request (CALL):
    • [ 2, “12345”, “Authorize”, { “idTag”: “ABCDEF1234567890” } ]
  2. Authorize Response (CALLRESULT):
    • [ 3, “12345”, “Authorize”, { “idTagInfo”: { “status”: “Accepted” } } ]
  3. MeterValues Request (CALL):
    • [ 2, “67890”, “MeterValues”, { “connectorId”: 1, “transactionId”: 9876, “meterValue”: [ { “timestamp”: “2024-10-27T10:00:00Z”, “sampledValue”: [ { “value”: “1234”, “unit”: “Wh”, “measurand”: “Energy.Active.Import.Register” } ] } ] } ]
  4. StatusNotification Request (CALL):
    • [ 2, “13579”, “StatusNotification”, { “connectorId”: 1, “status”: “Charging”, “timestamp”: “2024-10-27T10:05:00Z” } ]

OCPP 1.6 Message Rundown:

Here’s a quick overview of all the messages in OCPP 1.6, organized by profile:

Core Profile:

  • Authorize: Checks user authorization.
  • BootNotification: Charge Point sends upon startup.
  • ChangeAvailability: Sets Charge Point/connector availability.
  • ChangeConfiguration: Modifies Charge Point configuration.
  • ClearCache: Clears local authorization cache.
  • DataTransfer: Vendor-specific data exchange.
  • GetConfiguration: Retrieves Charge Point configuration.
  • Heartbeat: Charge Point sends to indicate online status.
  • MeterValues: Reports energy consumption.
  • RemoteStartTransaction/RemoteStopTransaction: Remote charging control.
  • Reset: Reboots the Charge Point.
  • StartTransaction: Charge Point sends at charging start.
  • StatusNotification: Reports Charge Point status.
  • StopTransaction: Charge Point sends at charging end.
  • UnlockConnector: Remote connector release.

Firmware Management Profile:

  • GetDiagnostics: Requests diagnostic logs.
  • DiagnosticsStatusNotification: Reports diagnostic log upload status.
  • FirmwareStatusNotification: Reports firmware update status.
  • UpdateFirmware: Initiates firmware update.

Local Authorization List Management Profile:

  • GetLocalListVersion: Checks local list version.
  • SendLocalList: Updates local authorization list.

Reservation Profile:

  • ReserveNow: Requests a reservation.
  • CancelReservation: Cancels a reservation.

Smart Charging Profile:

  • SetChargingProfile: Sets charging schedules/limits.
  • ClearChargingProfile: Removes charging profiles.
  • GetCompositeSchedule: Requests active charging schedule.

Remote Trigger Profile:

  • TriggerMessage: Requests specific messages from Charge Point.

Security: The Silent Guardian (And Where We Need to Step Up)

Security is paramount in the EV world. After all, we’re dealing with sensitive data and high-voltage electricity. OCPP 1.6 incorporated:

  • TLS Encryption: The Secure Tunnel: This encrypted communication between charging stations and management systems, protecting data from unauthorized access.
  • Authentication Mechanisms: The ID Check: This verified the identity of users and devices, ensuring only authorized parties could access the charging infrastructure.
  • Secure Firmware Updates: The Software Integrity Check: This ensured that firmware updates were legitimate and not malicious software.

However, OCPP 1.6 wasn’t perfect. Some of the older security methods, like basic username/password authentication, were vulnerable to attacks. And vulnerabilities regarding how messages were handled, have been discovered.

The Future is Here: OCPP 2.0.1 and Beyond – A Necessary Evolution

While OCPP 1.6 served its purpose, the EV landscape is rapidly evolving. That’s why we’re seeing the rise of OCPP 2.0.1 and OCPP 2.1 – a major upgrade in terms of features and security:

  • Enhanced Device Management: More granular control and monitoring of charging stations.
  • Stronger Security Protocols: Advanced encryption, certificate-based authentication, and defined security profiles.
  • Advanced Smart Charging Capabilities: Integration with energy management systems, dynamic load balancing, and support for ISO 15118.
  • Native ISO 15118 Support: Enabling features like “Plug & Charge,” where EVs can automatically authenticate and charge without user intervention.
  • Bidirectional Charging (V2G/V2X): Enabling EVs to send power back to the grid, transforming them into mobile energy storage units.
  • Improved Error Handling and Data Compression: Making the system more robust and efficient.

The Human Takeaway: Embracing the Future of EV Charging

OCPP 1.6 was a crucial stepping stone in the EV revolution, laying the foundation for interoper

What is OCPP? A Complete Guide to the EV Charging Communication Protocol

By

On March 22, 2025

In EV & Smart Mobility

As electric vehicles (EVs) become more mainstream, the infrastructure that powers them is evolving rapidly. Behind the scenes of every public EV charger is a smart communication layer that ensures chargers operate efficiently, securely, and interoperably. That communication standard is called OCPP — Open Charge Point Protocol.

In this article, we’ll break down what OCPP is, why it matters, how it works, and the different versions available today. Whether you’re an EV driver, charging network operator, or tech enthusiast, this guide will help you understand how OCPP is shaping the future of electric mobility.

? What is OCPP?

OCPP (Open Charge Point Protocol) is an application protocol used to enable communication between Electric Vehicle Supply Equipment (EVSE)—commonly known as EV chargers—and a Central Management System (CMS), often referred to as a Charge Point Operator (CPO) backend.

It is vendor-neutral and open-source, developed by the Open Charge Alliance (OCA) to standardize how EV chargers and management systems talk to each other.

Think of OCPP as the universal “language” between the charging station and the software that manages it.

⚙️ How OCPP Works

OCPP defines a set of WebSocket-based or SOAP-based messages that are exchanged between the client (charge point) and the server (backend system).

For example:

  • When a driver plugs in their EV, the charger sends a StartTransaction message to the backend.
  • The backend authenticates the session and sends a StartTransactionConfirmation.
  • Once charging ends, the charger sends a StopTransaction message.

Other key message types include:

  • Heartbeat: to ensure the charger is online
  • StatusNotification: to report charger availability
  • BootNotification: sent when the charger powers up
  • MeterValues: for usage data and billing
  • FirmwareUpdate, Diagnostics, and RemoteStart/Stop commands

These interactions enable remote control, monitoring, diagnostics, and software updates — all of which are essential for smart charging infrastructure.

? Why is OCPP Important?

  • Interoperability: OCPP allows chargers from different manufacturers to connect to any compliant backend, reducing vendor lock-in.
  • Scalability: Operators can manage thousands of chargers efficiently using a single system.
  • Smart Charging: OCPP supports load balancing, grid integration, and energy optimization.
  • Security: Latest versions support enhanced encryption, authentication, and access control mechanisms.

OCPP is especially important for public EV charging networks, fleet operators, municipalities, and utility companies that require flexibility and operational efficiency.

? OCPP Versions Explained

Over the years, OCPP has evolved to meet the growing demands of EV infrastructure. Here’s a look at its major versions:

✅ OCPP 1.2 (2009)

  • The first version
  • Limited functionality
  • Largely outdated and no longer used

✅ OCPP 1.5

  • Improved stability
  • Better message structure
  • Still lacks advanced features

✅ OCPP 1.6 (2015)

  • Most widely deployed version
  • Supports JSON over WebSocket and SOAP
  • Adds:
    • Remote Start/Stop
    • Smart Charging (Load Profiles)
    • Firmware Management
    • Diagnostics
  • Still supported by most major networks today

✅ OCPP 2.0 (2018)

  • Major overhaul of the protocol
  • Adds:
    • Device Management
    • Security Profiles
    • ISO 15118 integration (Plug & Charge)
    • Improved Smart Charging
    • Better data modeling

✅ OCPP 2.0.1 (2020)

  • The latest and stable version
  • Focused on bug fixes and practical enhancements from real-world implementations
  • Growing adoption in next-generation networks

? Note: OCPP 2.x is not backward compatible with 1.6, but many platforms support dual-stack operation.

?️ Technical Architecture Overview

A typical OCPP-based EV charging setup consists of:

  1. Charge Point (Client):
    • Hardware installed at EV charging stations
    • Acts as the OCPP client
    • Initiates communication
  2. Central System (Server):
    • Backend system that processes OCPP messages
    • Manages user sessions, pricing, diagnostics, and energy usage
  3. Communication Layer:
    • Typically uses WebSockets over TLS for secure, real-time, full-duplex communication
    • Some older implementations use SOAP over HTTP
  4. Optional Add-ons:
    • Token authentication (RFID, app-based)
    • OCPI/OSCP/ISO 15118 integration for roaming and advanced smart grid features

? Security in OCPP

Starting with OCPP 2.0, the protocol includes support for secure communication profiles, including:

  • TLS Encryption
  • Client-side and server-side certificates
  • Secure firmware updates
  • Signed metering and transaction data

These features make OCPP ready for enterprise-scale, mission-critical deployments.

? Real-World Use Cases

  • Public Charging Networks: Roaming across different charger brands
  • Fleet Management: Real-time diagnostics and energy consumption tracking
  • Retail Sites & Fuel Stations: Revenue tracking and load optimization
  • Smart Cities & Utilities: Demand response and grid integration

? Final Thoughts

OCPP is the backbone of modern EV charging infrastructure. As the electric vehicle ecosystem expands, having a universal, open, and future-ready protocol like OCPP ensures that EV charging remains reliable, scalable, and secure.

Whether you’re deploying 5 chargers in a parking lot or 5,000 across a city, OCPP gives you the flexibility to choose the hardware and software that suit your needs — all while ensuring interoperability with the rest of the EV ecosystem.

Want to learn more about OCPP, EV charging, or smart infrastructure? Follow this blog for future deep-dives, comparisons, and real-world implementation guides!

Powered by WordPress & Theme by Anders Norén