oSIST prEN IEC 63584-210:2026

SLOVENSKI STANDARD
01-april-2026
Protokol odprte polnilne točke 2.1 (hitri postopek)
Open charge point protocol 2.1 (fast track)
Ta slovenski standard je istoveten z: prEN IEC 63584-210:2026
ICS:
43.120 Električna cestna vozila Electric road vehicles
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

69/1124/CDV
COMMITTEE DRAFT FOR VOTE (CDV)
PROJECT NUMBER:
IEC 63584-210 ED2
DATE OF CIRCULATION: CLOSING DATE FOR VOTING:
2026-02-27 2026-05-22
SUPERSEDES DOCUMENTS:
IEC TC 69 : ELECTRICAL POWER/ENERGY TRANSFER SYSTEMS FOR ELECTRICALLY PROPELLED ROAD VEHICLES AND INDUSTRIAL
TRUCKS
SECRETARIAT: SECRETARY:
Belgium Mr Peter Van den Bossche
OF INTEREST TO THE FOLLOWING COMMITTEES: HORIZONTAL FUNCTION(S):
TC 8,SC 8A,SC 8B,SC 8C,TC 13,TC 23,SC 23A,SC 23B,SC
23E,SC 23G,SC 23H,SC 23J,SC 23K,TC 57,TC 64,SyC
SET,SyC Smart Energy
ASPECTS CONCERNED:
SUBMITTED FOR CENELEC PARALLEL VOTING NOT SUBMITTED FOR CENELEC PARALLEL VOTING
ATTENTION IEC-CENELEC PARALLEL VOTING
THE ATTENTION OF IEC NATIONAL COMMITTEES, MEMBERS OF
CENELEC, IS DRAWN TO THE FACT THAT THIS COMMITTEE
DRAFT FOR VOTE (CDV) IS SUBMITTED FOR PARALLEL VOTING.
THE CENELEC MEMBERS ARE INVITED TO VOTE THROUGH THE
CENELEC ONLINE VOTING SYSTEM.
This document is still under study and subject to change. It should not be used for reference purposes.
Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they
are aware and to provide supporting documentation.
Recipients of this document are invited to submit, with their comments, notification of any relevant “In Some Countries”
clauses to be included should this proposal proceed. Recipients are reminded that the CDV stage is the final stage for
submitting ISC clauses. (SEE AC/22/2007 OR NEW GUIDANCE DOC).

TITLE:
Open Charge Point Protocol 2.1 Ed2 (fast track)

PROPOSED STABILITY DATE: 2029
NOTE FROM TC/SC OFFICERS:
As this is a fast-track process offered by OCP, the Word file is not provided

electronic file, to make a copy and to print out the content for the sole purpose of preparing National Committee positions.
You may not copy or "mirror" the file or printed version of the document, or any part of it, for any other purpose without
permission in writing from IEC.

OCPP 2.1
Part 0 - Introduction
Edition 2, 2025-12-03
Table of Contents
Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  1
Version History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  2
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
1.1. OCPP version 2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
1.2. Terms and abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
1.3. References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
2. New functionality in OCPP 2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
3. OCPP 2.1 Documentation Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  8
3.1. Overview of Specification Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  8
3.2. Functional Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  9
3.3. All Functional Blocks and use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  10
4. Basic implementation of OCPP 2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  15

Disclaimer
The OCA hereby grants to IEC a license to fully exploit the OCPP for commercial and non-commercial purposes and to permit IEC
National Committees to nationally adopt and translate OCPP under the applicable IEC policies. Notwithstanding the foregoing, IEC is
not entitled to share adapted, altered, transformed or otherwise modified versions of the OCPP. Such license includes the right of IEC
to grant sub-licenses to its members for purposes of national adoption, distribution and reproduction in any format including
electronic for purposes of distribution on a commercial or non-commercial basis.
1/15 Part 0 - Introduction
Version History
Version Date Description
2.1 Edition 2 2025-12-03 OCPP 2.1 Edition 2. All errata from OCPP 2.1 Part 0 until and including Errata 2025-
11 have been merged into this version of the specification.
2.1 Edition 1 2025-01-23 OCPP 2.1 Edition 1
2/15 Part 0 - Introduction
Chapter 1. Introduction
Electric Vehicles (EVs) are becoming the new standard for mobility all over the world. This development is only possible with a
good coverage of Charging Stations. To advance the roll out of charging infrastructure, open communication standards play a key
role: to enable switching from charging network without necessarily replacing all the Charging Stations, to encourage innovation
and cost effectiveness and to allow many and diverse players participate in this new industry.
Additionally, the EV charging infrastructure is part of the Smart Grid, a larger and still evolving ecosystem of actors, devices and
protocols. In this Smart Grid ecosystem, open communication standards are key enablers for bidirectional power flows, real time
information exchange, demand control and eMobility services.
The Open Charge Point Protocol (OCPP) is the industry-supported de facto standard for communication between a Charging
Station and a Charging Station Management System (CSMS) and is designed to accommodate any type of charging technique.
OCPP is an open standard with no cost or licensing barriers for adoption.
1.1. OCPP version 2.1
This specification defines version 2.1 of OCPP.
Version 2.1 is an extension of OCPP 2.0.1. OCPP 2.1 has its own JSON schemas, but the schemas are OCPP 2.0.1 schemas that
have been extended with optional fields that are used by OCPP 2.1 functionality. With the minor exceptions mentioned below, all
application logic developed for OCPP 2.0.1 will continue to work in OCPP 2.1 without any changes. The new features of OCPP 2.1,
of course, require new application logic.
Use case A02 & A03
The application logic in a CSMS for OCPP 2.0.1 for use cases A02 & A03 requires a small change in order to work in OCPP
2.1.
The SignCertificateRequest message has been extended with a requestId field, such that the resulting
CertificateSignedRequest message can be accurately mapped to the request that initiated it. Use of requestId is optional for
Charging Station, but when present, CSMS will have to use it in the subsequent CertificateSignedRequest message.
Note, that the updated application logic remains valid to use in OCPP 2.0.1.
Use case N02
The application logic in a Charging Station for OCPP 2.0.1 for use case N02 requires a small change in order to work for
OCPP 2.1.
The message NotifyMonitoringReportRequest has been extended with a required field in VariableMonitoringType:
eventNotificationType. Charging Station has to provide this field. It provides essential information to CSMS about the type of
monitor (HardWiredMonitor, PreconfiguredMonitor, CustomMonitor) that was missing in OCPP 2.0.1. Existing OCPP 2.0.1
logic in a CSMS that is not aware of this new field, will continue to work.
1.2. Terms and abbreviations
This section contains the terminology and abbreviations that are used throughout this document.
1.2.1. Terms
Term Meaning
Charging Station The Charging Station is the physical system where an EV can be charged. A Charging Station has one or
more EVSEs.
Charging Station Charging Station Management System: manages Charging Stations and has the information for authorizing
Management Users for using its Charging Stations.
System (CSMS)
Electric Vehicle EVSE is considered as an independently operated and managed part of the Charging Station that can deliver
Supply Equipment energy to one EV at a time.
(EVSE)
Energy Management In this document this is defined as a device that manages the local loads (consumption and production)
System (EMS) based on local and/or contractual constraints and/or contractual incentives. It has additional inputs, such as
sensors and controls from e.g. PV, battery storage.
3/15 Part 0 - Introduction
1.2.2. Abbreviations
Term Meaning
CSO Charging Station Operator
CSMS Charging Station Management System
EMS Energy Management System.
EV Electric Vehicle
EVSE Electric Vehicle Supply Equipment
RFID Radio-Frequency Identification
4/15 Part 0 - Introduction
1.3. References
Table 1. References
Reference Description
[IEC61851-1] IEC 61851-1 2017: EV conductive charging system - Part 1: General requirements. https://webstore.iec.ch/
publication/33644
[IEC62559-2:2015] Definition of the templates for use cases, actor list and requirements list. https://webstore.iec.ch/
publication/22349
[ISO15118-1] ISO 15118-1 specifies terms and definitions, general requirements and use cases as the basis for the other
parts of ISO 15118. It provides a general overview and a common understanding of aspects influencing the
charge process, payment and load leveling. https://webstore.iec.ch/publication/9272
[OCPP1.5] http://www.openchargealliance.org/downloads/
[OCPP1.6] http://www.openchargealliance.org/downloads/
5/15 Part 0 - Introduction
Chapter 2. New functionality in OCPP 2.1
OCPP 2.1 introduces new functionality compared to OCPP 2.0.1.
The application logic for OCPP 2.0.1 remains valid, but will have to be extended to support the new features of OCPP 2.1.
Most important new features of OCPP 2.1 include support for ISO 15118-20 and extensive support for bidirectional power transfer
(V2X), and control of Charging Stations and EVs as Distributed Energy Resources (DER). New use cases have been added that
describe ad hoc payment, and Charging Stations can now do local cost calculation based on tariff information from CSMS.
Below is a list of sections of Part 2 of the specification that have new or updated functionality.
A Security
A02/A03 A requestId has been added to SignCertificateRequest. Added support for ISO 15118-20 certificates.
A05 Downgrading from security profile 3 to 2 is no longer prohibited.
B Provisioning
B09 SetNetworkProfileRequest has been extended with basicAuthPassword and identity.
B13 New use case to support resuming transaction after a reset.
C Authorization
Length of IdToken has been extended to 255 characters.
IdToken type is now a predefined list instead of enumeration to allow for easier extension.
C07/C08 ISO 15118 authorization use cases updated with ISO 15118-20 flows.
C10 Explicit requirement added about expiration in authorization cache.
C17 New use case for authorization with prepaid card.
C18-C23 New use cases for ad hoc payment with integrated payment terminal.
C24 New use case for ad hoc payment via stand-alone payment terminal.
C25 New use case for ad hoc payment via dynamic QR code.
E Transactions
E16 New use case for transactions with cost, energy, time, SoC limit.
E17 New use case for resuming a transaction after forced reboot.
F Remote Control
F06 Added CustomTrigger to TriggerMessageRequest.
F07 Net use case for remote start of transaction with limits.
G Availability
Availability notification using NotifyEventRequest for component Connector is now the preferred method, instead of
StatusNotification.
I Tariff and Cost
Introducing local cost calculation
I07-I11 New use cases to set default/user tariffs on charging station.
I12 New use case to report calculated cost during and at end of transaction.
J Metervalues
New metervalue location: Upstream.
New measurands for bidirectional charging.
K Smart Charging
New charging profile purposes PriorityCharging and LocalGeneration.
Added operationMode to ChargingSchedulePeriodType to facilitate bidirectional charging scenarios.
K01 Added dynamic charging profiles for frequent and unscheduled updates of limits.
K23-K27 New use cases for topologies with energy management systems.
K18-K20 New uses cases to support ISO 15118-20.
K21-K22 New uses cases for priority charging to allow user to overrule charging profile.
6/15 Part 0 - Introduction
M Certificate Management
M01 Updated use case for ISO 15118-20.
N Diagnostics
N01 Added support for data collector log on charging station.
N02 Added monitoring types TargetDelta and TargetDeltaRelative.
N07 Added severity to NotifyEventRequest.
N11-14 New use cases for optimized frequent periodic variable monitoring via an event stream. This utilizes the new
unconfirmed message type: SEND.
N15 Use case to set a frequent periodic monitoring via event stream.
O Display Message
O01 Added multi-language support.
Q Bidirectional Power Transfer
New section that describes control of bidirectional charging via charging profiles.
Q01-Q04 V2X control with centrally controlled charging profiles.
Q05-Q06 V2X control with externally controlled charging profiles.
Q07-Q08 Central can local frequency control.
Q09 Local load-balancing with V2X.
Q10-Q12 Idle state, offline and resuming after offline.
R DER Control
New section that describes grid control when EV and charging station are considered to be a Distributed Energy Resource
(DER).
U01 DER control in EVSE.
U02 DER control in EV.
U03 Hybrid DER control in both EVSE and EV.
U04 Configure DER controls in charging station.
U05 Charging station reporting a DER event.
S Battery Swapping
New section that describes how to control a battery swap station.
S01 Battery Swap Local Autorization
S02 Battery Swap Remote Start
S03 Battery Swap In/Out
S04 Battery Swap Charging
7/15 Part 0 - Introduction
Chapter 3. OCPP 2.1 Documentation Structure
3.1. Overview of Specification Parts
For readability and implementation purposes, OCPP 2.1 is divided in seven parts.
Table 2. Parts
Part 0 Introduction (this document)
Part 1 Architecture & Topology
Part 2
Specification:
Use Cases and Requirements, Messages, Data Types and Referenced Components and Variables
Appendices:
Security Events, Standardized Units of Measure, Components and Variables
Part 3 Schemas
Part 4 Implementation Guide JSON
Part 5 Certification Profiles
Part 6 Test Cases
The OCPP 2.1 specification is written using a structure, based on [IEC62559-2:2015]: "Use case methodology - Part 2: Definition of
the template for use cases, actor list and requirements list".
Part 2, the specification, is divided into 'Functional Blocks'. These Functional Blocks contain use cases and requirements.
Messages, Data Types and Referenced Components and Variables are described at the end of the document. The Appendices can
be found in the separate document: Part 2 - Appendices.
8/15 Part 0 - Introduction
3.2. Functional Blocks
OCPP 2.1 consists of the following Functional Blocks.
Table 3. Functional Blocks
Clause Functional Block Title Description
A. Security This Functional Block describes a security specification for the OCPP
protocol.
B. Provisioning This Functional Block describes all the functionalities that help a CSO
provision their Charging Stations, allowing them to be registered and
accepted on their network and retrieving basic configuration information
from these Charging Stations.
C. Authorization This Functional Block describes all the authorization related functionality:
AuthorizeRequest message handling/behavior and Authorization Cache
functionality.
D. Local Authorization List Management This Functional Block describes functionality for managing the Local
Authorization List.
E. Transactions This Functional Block describes the basic OCPP Transaction related
functionality for transactions that are started/stopped on the Charging
Station.
F. Remote Control This Functional Block describes three types of use cases for remote control
management from the CSMS: Remote Transaction Control, Unlocking a
Connector and Remote Trigger.
G. Availability This functional Block describes the functionality of sending status
notification messages.
H. Reservation This Functional Block describes the reservation functionality of a Charging
Station.
I. Tariff and Cost This Functional Block provides tariff and cost information to an EV Driver,
when a Charging Station is capable of showing this on a display. Before a
driver starts charging tariff information needs to be given, detailed prices
for all the components that make up the tariff plan applicable to this driver
at this Charging Station. During charging the EV Driver needs to be shown
the running total cost, updated at a regular, fitting interval. When the EV
Driver stops charging the total cost of this transaction needs to be shown.
J. Metering This Functional Block describes the functionality for sending meter values,
on a periodic sampling and/or clock-aligned timing basis.
K. Smart Charging This Functional Block describes all the functionality that enables the CSO
(or indirectly a third party) to influence the charging current/power of a
charging session, or set limits to the amount of power/current a Charging
Station can offer to an EV.
L. Firmware Management This Functional Block describes the functionality that enables a CSO to
update the firmware of a Charging Station.
M. Certificate Management This Functional Block provides the installation and update of certificates.
N. Diagnostics This Functional Block describes the functionality that enables a CSO to
request and track the upload of a diagnostics file from a Charging Station,
and to manage the monitoring of Charging Station data.
O. Display Message With the DisplayMessage feature OCPP enables a CSO to display a
message on a Charging Station, that is not part of the firmware of the
Charging Station. The CSO gets control over these messages: the CSO can
set, retrieve (get), replace and clear messages.
P. Data Transfer This Functional Block describes the functionality that enables a party to add
custom commands to OCPP, enabling custom extension to OCPP.
Q Bidirectional Power Transfer This Functional block extends Smart Charging with bidirectional power
transfer (V2X).
R DER Control This Functional Block describes how charging stations and EVs can be
controlled as Distributed Energy Resources. It provides functions to
configure grid code parameters on a charging station via CSMS. It is
designed to support DER settings from IEC 61850 and IEEE 2030.5 on the
grid side, and ISO 15118-20 Amendment 1 on the EV side.
S Battery Swapping This Functional block describes how to deal with battery swap stations in
OCPP and adds the BatterySwap message.
9/15 Part 0 - Introduction
3.3. All Functional Blocks and use cases
The following table shows the full list of use cases supported by OCPP 2.1 and which use cases were already supported by OCPP
1.6 [OCPP1.6] and OCPP 2.1 .
Clause Functional Block UC ID Use case name OCPP 1.6 New in New in
OCPP OCPP 2.1
2.0.1
A Security A01 Update Charging Station Password for HTTP o
Basic Authentication
A02 Update Charging Station Certificate by o
request of CSMS
A03 Update Charging Station Certificate initiated o
by the Charging Station
A04 Security Event Notification o
A05 Upgrade Charging Station Security Profile o
B Provisioning B01 Cold Boot Charging Station o
B02 Cold Boot Charging Station - Pending o
B03 Cold Boot Charging Station - Rejected o
B04 Offline Behavior Idle Charging Station o
B05 Set Variables o
B06 Get Variables o
B07 Get Base Report o
B08 Get Custom Report o
B09 Setting a new NetworkConnectionProfile o
B10 Migrate to new CSMS o
B11 Reset - Without Ongoing Transaction o
B12 Reset - With Ongoing Transaction o
B13 Reset - With Ongoing Transaction - Resuming o
Transaction
C Authorization C01 EV Driver Authorization using RFID o
C02 Authorization using a start button o
C03 Authorization using credit/debit card o
C04 Authorization using PIN-code o
C05 Authorization for CSMS initiated transactions o
C06 Authorization using local id type o
C07 Authorization using Contract Certificates o
C08 Authorization at EVSE using ISO 15118 o
External Identification Means (EIM)
C09 Authorization by GroupId o
C10 Store Authorization Data in the Authorization o
Cache
C11 Clear Authorization Data in Authorization o
Cache
C12 Start Transaction - Cached Id o
C13 Offline Authorization through Local o
Authorization List
C14 Online Authorization through Local o
Authorization List
C15 Offline Authorization of unknown Id o
C16 Stop Transaction with a Master Pass o
C17 Authorization with prepaid card o
C18 Authorization using locally connected o
payment terminal
10/15 Part 0 - Introduction
Clause Functional Block UC ID Use case name OCPP 1.6 New in New in
OCPP OCPP 2.1
2.0.1
C19 Cancelation prior to transaction o
C20 Cancelation after start of transaction, before o
costs have been incurred.
C21 Settlement at end of transaction o
C22 Settlement is rejected or fails o
C23 Increasing authorization amount o
C24 Ad hoc payment via stand-alone payment o
terminal
C25 Ad hoc payment via static or dynamic QR o
code
D LocalAuthorizationList D01 Send Local Authorization List o
D02 Get Local List Version o
E Transactions E01 Start Transaction Options o
E02 Start Transaction - Cable Plugin First o
E03 Start Transaction - IdToken First o
E04 Transaction started while Charging Station is o
offline
E05 Start Transaction - Id not Accepted o
E06 Stop Transaction Options o
E07 Transaction locally stopped by IdToken o
E08 Transaction stopped while Charging Station o
is offline
E09 When cable disconnected on EV-side: Stop o
Transaction
E10 When cable disconnected on EV-side: o
Suspend Transaction
E11 Connection Loss During Transaction o
E12 Inform CSMS of an Offline Occurred o
Transaction
E13 Transaction related message not accepted o
by CSMS
E14 Check transaction status o
E15 End of charging process o
E16 Transactions with fixed cost, energy, SoC or o
time
E17 Resuming transaction after forced o
E18 Battery Swapping o
F RemoteControl F01 Remote Start Transaction - Cable Plugin First o
F02 Remote Start Transaction - Remote Start First o
F03 Remote Stop Transaction o
F04 Remote Stop ISO 15118 charging from CSMS o
F05 Remotely Unlock Connector o
F06 Trigger Message o
F07 Remote start with fixed cost, energy or time o
G Availability G01 Status Notification o
G02 Heartbeat o
G03 Change Availability EVSE o
G04 Change Availability Charging Station o
G05 Lock Failure o
H Reservation H01 Reservation o
H02 Cancel Reservation o
11/15 Part 0 - Introduction
Clause Functional Block UC ID Use case name OCPP 1.6 New in New in
OCPP OCPP 2.1
2.0.1
H03 Use a reserved EVSE o
H04 Reservation Ended, not used o
I Tariff and Costs I01 Show EV Driver-specific tariff information o
I02 Show EV Driver running total cost during o
charging
I03 Show EV Driver final total cost after charging o
I04 Show fallback tariff information o
I05 Show fallback total cost message o
I06 Update Tariff Information During Transaction o
I07 Local Cost Calculation - Set Default Tariff o
I08 Local Cost Calculation - Receive User Tariff o
I09 Local Cost Calculation - Get Tariffs o
I10 Local Cost Calculation - Clear Tariffs o
I11 Local Cost Calculation - Change transaction o
tariff
I12 Local Cost Calculation - Cost Details of o
Transaction
J Metering J01 Sending Meter Values not related to a o
transaction
J02 Sending transaction related Meter Values o
J03 Charging Loop with metering information o
exchange
K SmartCharging K01 SetChargingProfile o
K02 Central Smart Charging o
K03 Local Smart Charging o
K04 Internal Load Balancing o
K05 Remote Start Transaction with Charging o
Profile
K06 Offline Behavior Smart Charging During o
Transaction
K07 Offline Behavior Smart Charging at Start of o
Transaction
K08 Get Composite Schedule o
K09 Get Charging Profiles o
K10 Clear Charging Profile o
K11 Set / Update External Charging Limit With o
Ongoing Transaction
K12 Set / Update External Charging Limit Without o
Ongoing Transaction
K13 Reset / release external charging limit o
K14 External Charging Limit with Local Controller o
K15 Charging with load leveling based on High o
Level Communication
K16 Optimized charging with scheduling to the o
CSMS
K17 Renegotiating a Charging Schedule o
K18 ISO 15118-20 Scheduled Control Mode o
K19 ISO 15118-20 Dynamic Control Mode o
K20 Adjusting charging schedule when energy o
needs change
K21 Requesting priority charging remotely o
12/15 Part 0 - Introduction
Clause Functional Block UC ID Use case name OCPP 1.6 New in New in
OCPP OCPP 2.1
2.0.1
K22 Requesting priority charging locally o
K23 Smart Charging with EMS connected to o
Charging Stations
K24 Smart Charging with EMS connected to Local o
Controller
K25 Smart Charging with EMS acting as a Local o
Controller
K26 Smart Charging with Hybrid Local & Cloud o
EMS
K27 Smart Charging with EMS and o
LocalGeneration
K28 Dynamic charging profiles o
L Firmware Management L01 Secure Firmware Update o
L02 Non-Secure Firmware Update o
L03 Publish Firmware file on Local Controller o
L04 Unpublish Firmware file on Local Controller o
M Certificate Management M01 Certificate Installation EV o
M02 Certificate Update EV o
M03 Retrieve list of available certificates from a o
Charging Station
M04 Delete a specific certificate from a Charging o
Station
M05 Install CA certificate in a Charging Station o
M06 Get Charging Station Certificate status o
N Diagnostics N01 Retrieve Log Information o
N02 Get Monitoring report o
N03 Set Monitoring Base o
N04 Set Variable Monitoring o
N05 Set Monitoring Level o
N06 Clear / Remove Monitoring o
N07 Alert Event o
N08 Periodic Event o
N09 Get Customer Information o
N10 Clear Customer Information o
N11 Set Frequent Periodic Variable Monitoring o
N12 Get Periodic Event Streams o
N13 Close Periodic Event Streams o
N14 Adjust Periodic Event Streams o
N15 Periodic Event Streams o
O Display Message O01 Set DisplayMessage o
OO2 Set DisplayMessage for Transaction o
O03 Get All DisplayMessages o
O04 Get Specific DisplayMessages o
O05 Clear a DisplayMessage o
O06 Replace DisplayMessage o
P DataTransfer P01 Data Transfer to the Charging Station o
P02 Data Transfer to the CSMS o
Q Bidirectional Power Q01 V2X Authorization o
Transfer
13/15 Part 0 - Introduction
Clause Functional Block UC ID Use case name OCPP 1.6 New in New in
OCPP OCPP 2.1
2.0.1
Q02 Charging only (V2X control) before starting o
V2X
Q03 Central V2X control with charging schedule o
Q04 Central V2X control with dynamic CSMS o
setpoint
Q05 External V2X setpoint control with a charging o
profile from CSMS
Q06 External V2X control with a charging profile o
from an External System
Q07 Central V2X control for frequency support o
Q08 Local V2X control for frequency support o
Q09 Local V2X control for load balancing o
Q10 Idle, minimizing energy consumption o
Q11 Going offline during V2X operation o
Q12 Resuming a V2X operation after an offline o
period
R DER Control R01 Starting a V2X session with DER control in o
EVSE
R02 Starting a V2X session with DER control in EV o
R03 Starting a V2X session with hybrid DER o
control in both EV and EVSE
R04 Configure DER control settings at Charging o
Station
R05 Charging station reporting a DER event o
S Battery Swapping S01 Battery swap local authorization o
S02 Battery swap remote start o
S03 Battery swap in/out o
S04 Battery swap charging o
OCPP is used in many different regions and for many different charging solutions. Not all functionalities offered
by OCPP will be applicable to all implementations. Implementers can decide what specific functionalities apply to
NOTE
their charging solution.
For interoperability purposes, the Open Charge Alliance introduces Certification Profiles in Part 5 of the
specification.
14/15 Part 0 - Introduction
Chapter 4. Basic implementation of OCPP 2.1
This section is informative.
The OCPP protocol describes a large number of use cases and messages, which are not all needed to implement a basic Charging
Station or CSMS. The table below lists messages that are typically implemented to deliver basic functionality for an OCPP managed
Charging Station. The purpose of this list is to guide developers that are new to OCPP.
The basic implementation set for OCPP 2.1 is the same as for OCPP 2.0.1.
this table does not define what needs to be done to become OCPP 2.1 "certified". The functionality that is to be
NOTE
implemented to become OCPP 2.1 certified is described in Part 5 of the specification, "Certification Profiles".
Table 4. OCPP 2.1 Basic Implementation
Functionality Use cases Messages
Booting a Charging Station B01-B04 BootNotification
Configuring a Charging Station B05-B07 SetVariables, GetVariables and GetReportBase (respond
correctly to requests with reportBase = ConfigurationInventory,
FullInventory and SummaryInventory).
Resetting a Charging Station B11-B12 Reset
Authorization options One of C01, C02 and C04 Authorize
Transaction mechanism E01 (one of S1-S6), E02-E03, TransactionEvent
E05, E06 (one of S1-S6), E07-
E08, One of E09-E10, E11-E13
Availability G01, G03-G04 Only ChangeAvailability and StatusNotification.
Monitoring Events G05, N07 A basic implementation of the NotifyEvent message to be used
to report operational state changes and problem/error
conditions of the Charging Station, e.g. for Lock Failure. Also
used for reporting built-in monitoring events.
Sending transaction related J02 TransactionEvent
Meter values
DataTransfer P01-P02 Any OCPP implementations should at least be able to reject any
request for DataTransfer if no (special) functionality is
implemented.
NOTE Please also refer to the section on Minimum Device Model in part 1.
15/15 Part 0 - Introduction
OCPP 2.1
Part 1 - Architecture & Topology
Edition 2, 2025-12-03
Table of Contents
Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  1
Version History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  2
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
1.1. Goal of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
1.2. Terms and abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
2. 3-tier model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
3. Device Model: Addressing Components and Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
3.1. Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
3.2. Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
3.3. Characteristics and Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
3.4. Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  8
3.5. Standardized lists of Components and Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  9
3.6. Minimum Device Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  9
4. Device Model hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  11
5. Information Model vs. Device Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  12
6. Using OCPP for other purposes than EV charging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  13
7. Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  14
7.1. EVSE numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  14
7.2. Connector numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  14
7.3. Transaction IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  14
8. Topologies supported by OCPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  15
8.1. Charging Station(s) directly connected to CSMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  15
8.2. Multiple Charging Stations connected to CSMS via Local Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  15
8.3. Multiple Charging Stations connected to CSMS via Local Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  16
8.4. Non-OCPP Charging Stations connected to CSMS via OCPP Local Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  16
8.5. DSO control signals to CSMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  16
9. Energy management topologies supported by OCPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  18
9.1. Parallel control of charging station by CSMS and smart meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  18
9.2. Parallel control of charging location by CSMS and EMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  18
9.3. EMS via Local Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  19
9.4. EMS as man-in-the-middle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  20
9.5. Hybrid local & cloud EMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  20
9.6. Parallel control by CSMS and EMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  21

Disclaimer
The OCA hereby grants to IEC a license to fully exploit the OCPP for commercial and non-commercial purposes and to permit IEC
National Committees to nationally adopt and translate OCPP under the applicable IEC policies. Notwithstanding the foregoing, IEC is
not entitled to share adapted, altered, transformed or otherwise modified versions of the OCPP. Such license includes the right of IEC
to grant sub-licenses to its members for purposes of national adoption, distribution and reproduction in any format including
electronic for purposes of distribution on a commercial or non-commercial basis.
1/22 Part 1 - Architecture & Topology

Version History
Version Date Description
2.1 Edition 2 2025-12-03 OCPP 2.1 Edition 2. All errata from OCPP 2.1 Part 1 until and including Errata 2025-
11 have been merged into this version of the specification.
2.1 Edition 1 2025-01-23 OCPP 2.1 Edition 1
2/22 Part 1 - Architecture & Topology

Chapter 1. Introduction
1.1. Goal of this document
The goal of this document is to describe a number of architecture related topics for OCPP 2.1 . It is not fundamentally different
from the version for OCPP 2.0.1.
OCPP was originally intended for two way communication between a backoffice, in OCPP the Charging Station Management System
(in this document: CSMS) and a Charging Station. The protocol has become more advanced and with every new revision new
functionalities and options are added. It has evolved into a protocol that can be used in different architectures for different types of
Charging Stations.
This document describes, in addition to the original "simple" setup CSMS <> Charging Station, a number of topologies as an
additional explanation for using OCPP. Furthermore, the Device Management concept to configure and monitor any type of
Charging Station, the OCPP Information Model and the 3-tier model are explained.
This document is partially informative and partially normative and is not intended to limit the use of OCPP. However, it does add an
explanation what kind of use of OCPP the creators of OCPP had in mind when creating this version of the specification. This
document is therefore also intended to support the reader of the protocol specification in Part 2 of OCPP to understand how it can
be used.
1.2. Terms and abbreviations
This section contains the terminology and abbreviations that are used throughout this document.
1.2.1. Terms
Term Meaning
Charging Location A group of one or more Charging Stations that belong together geographically or spatially.
Charging Station The Charging Station is the physical system where EVs can be charged. A Charging Station
has one or more EVSEs.
Connector The term Connector, as used in this specification, refers to an independently operated and
managed electrical outlet on a Charging Station. In other words, this corresponds to a single
physical Connector. In some cases an EVSE may have multiple physical socket types and/or
tethered cable/Connector arrangements(i.e. Connectors) to facilitate different vehicle types
(e.g. four-wheeled EVs and electric scooters).
EVSE An EVSE is considered as an independently operated and managed part of the Charging
Station that can deliver energy to one EV at a time.
Local port Smart Meter The local port on a Smart Meter is a port (for example serial) on a digital electricity meter
that provides access to information about meter readings and usage.
1.2.2. Abbreviations
Abbreviation Meaning
DSO Distribution System Operator
CSO Charging Station Operator
CSMS Charging Station Management System
EMS Energy Management System. In this document this is defined as a device that manages the local loads
(consumption an production) based on local and/or contractual constraints and/or contractual incentives. It
has additional inputs, such as sensors and controls from e.g. PV, battery storage.
EVSE Electric Vehicle Supply Equipment
LC Local Controller. In this document this is defined as a device that can send messages to its Charging
Stations, independently of the CSMS. A typical usage for this is the local smart charging case described in
the Smart Charging chapter of Part 2 of OCPP, where a Local Controller can impose charge limits on its
Charging Stations.
LP Local Proxy. Acts as a message router.
3/22 Part 1 - Architecture & Topology

Chapter 2. 3-tier model
This section is informative.
To understand the terminology in the OCPP specification, it is important to understand the starting point of this specification. The
OCPP specification uses the term Charging Station as the physical system where EVs can be charged. A Charging Station can have
one or more EVSEs (Electric Vehicle Supply Equipment). An EVSE is considered as a part of the Charging Station that can deliver
energy to one EV at a time. The term Connector, as used in this specification, refers to an independently operated and managed
electrical outlet on a Charging Station, in other words, this corresponds to a single physical Connector. In some cases an EVSE may
have multiple physical socket types and/or tethered cable/connector arrangements to facilitate different vehicle types (e.g. four-
wheeled EVs and electric scooters). This setup is referred to as the 3-tier model and visualized in the figure below.
Figure 1. 3-tier model as used in OCPP
A C
...