OCPP 2.1 is the newest major version from the Open Charge Alliance and is built on top of 2.0.1. The aim is not to redesign the protocol, but to standardise new scenarios in which EV charging is more tightly integrated with the energy system. This article summarises what 2.1 brings and which businesses it matters to.
How OCPP 2.1 relates to 2.0.1
OCPP 2.1 was designed to be largely backward compatible with 2.0.1. The device model, TransactionEvent, security profiles and core messages continue with the same logic. 2.1 adds new functional blocks and messages on top. As a result, an integration built for 2.0.1 does not need to be rewritten from scratch to move to 2.1. The WebSocket subprotocol name is separate: ocpp2.1.
Main new features
Bidirectional charging (V2X)
The most talked-about feature of 2.1 is the set of messages for managing energy flowing from the vehicle battery back to the grid, a building or a home (V2G, V2H, V2X). The CSMS can send discharge targets and limits to the station and the vehicle. The feature requires suitable hardware and vehicle support, but on the protocol side there is now a common language.
Distributed energy resources (DER) control
For sites where solar panels, stationary batteries and chargers work together, 2.1 defines DER functions such as the frequency and voltage responses required by grid codes. This lets the charging station behave as an active part of the energy system.
Tariffs and cost
2.1 supports sending tariffs to the station in a structured form and lets the station calculate the cost itself. This makes it easier to show the driver accurate price information even while offline.
Payment scenarios
Flows for ad-hoc (non-subscription) payments with card readers integrated into the station are clarified. Because European regulation is making card payment increasingly mandatory for public fast charging, this is an important step.
Other improvements
More flexible profiles for smart charging, cooperation with local energy management systems, new use cases such as battery swapping and various bug fixes are also part of 2.1.
Do you need to move to 2.1 right away?
No, for most businesses there is no rush. Most chargers on the market still use OCPP 1.6J; 2.0.1 support is spreading, and 2.1 support is just arriving. The right approach is:
- Ask the manufacturer about their 2.0.1 and 2.1 roadmap when buying new chargers.
- Prioritise 2.1 if you have a business goal such as V2X or card payments.
- Make sure your management software supports all three versions at the same time.
For a detailed comparison, see our guide to the differences between OCPP 1.6J, 2.0.1 and 2.1.
Who is it important for?
- Energy companies and aggregators: For flexibility services and V2G pilots.
- Fast-charging operators: For card payments and transparent pricing.
- Commercial sites: For load management together with solar panels and batteries.
- Fleets: For using vehicle batteries as an energy resource in the future.
The hardware and vehicle side
A feature being defined in the protocol does not mean it will work in the field immediately. Bidirectional charging, for example, requires both the charger (usually DC) and the vehicle to support discharging, and local grid rules must allow it. Card payment requires a certified payment terminal on the charger. So when you assess 2.1 features, consider hardware, vehicle compatibility and regulation together. If you are planning a pilot, ask the charger manufacturer in writing which 2.1 functions are actually enabled in the firmware; "2.1 ready" often only describes connection-level support.
Conclusion
OCPP 2.1 brings features that turn the charging station from a device that simply draws energy into an intelligent part of the energy system. It is not mandatory for everyone today, but it should not be ignored in new investments. Üreticy's OCPP software supports 2.1 chargers alongside OCPP 1.6J and 2.0.1 in the same dashboard.