Key Points

Overview of OCPP 2.0.1 Edition 3

This document outlines the Open Charge Point Protocol (OCPP) 2.0.1 Edition 3, detailing the communication between charging stations and management systems. It covers various use cases, requirements, security, authorization, transactions, and more. Think of it as your guide to understanding how electric vehicle charging stations talk to the network!

Expected outcomes: 1.Understand the requirements for charging station communication. 2.Learn how to ensure secure charging processes. 3.Discover how to manage transactions efficiently. 4.Gain insights into smart charging and diagnostics.

Core Content:

1. Key Protocol Aspects:

Scope: Defines the communication protocol between a Charging Station (CS) and a Charging Station Management System (CSMS) within an EV charging infrastructure.
JSON Compatibility: OCPP 2.0.1 is limited to JSON for widespread compatibility. Details for this implementation are in "Part 4 - JSON over WebSockets implementation guide".
Version Updates: OCPP 2.0.1 includes fixes for known issues, replacing OCPP 2.0. Edition 3 merges errata from OCPP 2.0.1 Edition 2 up to Errata 2024-04, without altering OCPP message schemas.

2. Security Implementation

Security Objectives: Ensuring data confidentiality, integrity, and authentication between the CS and CSMS.
Security Profiles: Defines specific security configurations. Basic Security Profile (mandatory). Advanced Security Profile (optional).
Key Management: Discusses the types of keys used in OCPP, including their roles and secure handling.
Certificate Management: Covers the processes for updating and managing certificates on the charging station, including use cases initiated by both the CSMS and the charging station.

3. Provisioning Processes

Booting: Involves the CS establishing a connection with the CSMS upon startup, including scenarios for cold boots, pending acceptance, and rejection by the CSMS.
Configuration: Describes how the CSMS can set and get variables on the CS, request base or custom reports, set up new network connection profiles, and migrate to a new CSMS.
Resetting: Details the procedures for resetting a charging station, both with and without ongoing transactions, ensuring minimal disruption to users.

4. Authorization Framework

Token Handling: Includes various methods such as RFID, start buttons, credit/debit cards, PIN codes, and local ID types.
ISO 15118 Support: Focuses on authorization using contract certificates and External Identification Means (EIM).
Caching: Explain the use of authorization caches to store and clear authorization data.
Local Authorization List: Manages offline authorization through a local list.

5. Transaction Control

Flexibility: Details options for starting transactions (like cable plugin first or ID token first).
Offline Handling: Covers the behavior of charging stations when starting or stopping transactions offline and then reconnecting.
Error Handling: Describes scenarios where a transaction-related message is not accepted by the CSMS and how to check transaction statuses.
ISO 15118 Integration: Manages transaction interruptions in the context of ISO 15118 charging.

6. Remote Control Capabilities

Starting and Stopping: The use cases detail how the CSMS can start and stop transactions remotely, including scenarios tailored to ISO 15118 charging.
Connector Management: Details remote unlocking of connectors to resolve charging issues.

7. Availability Management

Status Notification: Communication of charging station and EVSE status changes.
Heartbeat: Regular communication signal to confirm online status.
Remote Control: Managing availability of EVSE/Connectors and entire Charging Stations.
Failure Handling: Dealing with lock failures and reporting these issues.

8. Smart Charging Implementations

Profiles: Setting, getting, and clearing charging profiles to manage energy distribution.
Load Balancing: Implementing internal and external load balancing strategies.
External Charging Limits: Setting and resetting external charging limits with local controllers.
ISO 15118 Renegotiation: Detailing the processes for renegotiating charging parameters.

Q&A

Q: What is the difference between OCPP 2.0 and OCPP 2.0.1?

A: OCPP 2.0.1 is essentially a corrected version of OCPP 2.0. After the release of OCPP 2.0, some issues were found and fixed in OCPP 2.0.1. So, you should skip 2.0 and go straight to 2.0.1 to avoid any headaches.

Q: Why is security so important in OCPP?

A: Security is critical because charging stations handle personal data and control energy distribution. OCPP includes security profiles and certificate management to protect against vulnerabilities.

Q: How does OCPP handle offline scenarios?

A: OCPP specifies behaviors for when charging stations lose connection to the CSMS, including authorizing users, starting/stopping transactions, and storing data until reconnection.

Q: What are charging profiles and why are they used?

A: Charging profiles are sets of rules that manage how much power a charging station delivers to an EV. They're used for smart charging, load balancing, and optimizing energy use based on grid needs.

MindMap

Target Audience

This specification is intended for developers, manufacturers, and operators involved in the electric vehicle (EV) charging infrastructure ecosystem. It is particularly relevant for those designing, implementing, and maintaining charging stations and charging station management systems (CSMS). The document assumes a strong understanding of networking protocols, security concepts, and EV charging technologies. It caters to engineers, software architects, product managers, and technical consultants working in the EV industry, as well as certification bodies and regulatory agencies involved in ensuring interoperability and compliance of EV charging infrastructure.

Author Background

The Open Charge Alliance (OCA) is a global consortium of public and private entities that collaborate to develop and promote open standards for EV charging infrastructure. OCA facilitates interoperability, reduces complexity, and fosters innovation in the EV charging market. The organization comprises experts from various sectors, including EV manufacturers, charging station vendors, energy providers, and research institutions. OCA's work is driven by the collective knowledge and experience of its members, who contribute to the development and maintenance of OCPP and other open standards. The alliance aims to create a level playing field for all stakeholders in the EV charging ecosystem, enabling seamless and reliable charging experiences for EV drivers worldwide.

Historical Context

The Open Charge Point Protocol (OCPP) was created to standardize communication between EV charging stations and management systems. Before OCPP, the lack of a unified protocol led to interoperability issues, hindering the growth of the EV charging infrastructure. OCPP 1.0 was the first attempt to address this problem, followed by OCPP 1.5 and 1.6, which gained widespread adoption. OCPP 2.0 and 2.0.1 represent significant advancements, incorporating new functionalities, enhanced security features, and improved support for smart charging applications. These versions reflect the evolving needs of the EV market, driven by the increasing adoption of EVs, the demand for faster charging, and the integration of charging infrastructure with smart grids and energy management systems. The development of OCPP 2.0.1 also takes into account the growing importance of ISO 15118 for advanced charging functionalities.

OCPP 2.0.1: Part 2 - Specification