The Open Charge Alliance (OCA) has officially published the final release of OCPP 2.1, marking the most significant protocol evolution since the jump from 1.6 to 2.0. For CPOs and CSMS vendors, this release resolves several pain points that have plagued real-world deployments.
Key Changes in OCPP 2.1
The headline feature is full ISO 15118-20 support, enabling bidirectional power transfer (V2G) communication through the CSMS. This is not just a theoretical addition — with European grid operators increasingly interested in vehicle-to-grid services, OCPP 2.1 provides the protocol foundation that was previously missing.
Tariff handling has been completely reworked. The new CostUpdated and tariff-related messages allow the CSMS to communicate complex, time-of-use pricing structures to the charging station in real time. This directly supports AFIR's requirement for transparent per-kWh pricing.
Device management improvements include better firmware update orchestration, more granular status reporting, and enhanced security certificate management — critical for large-scale fleet operations.
Migration Considerations
For CPOs currently running OCPP 2.0.1, the upgrade path to 2.1 is manageable but not trivial. The message structure changes are backward-compatible in most cases, but the new tariff and ISO 15118-20 messages require CSMS-side implementation work.
For CPOs still on OCPP 1.6 — which remains the majority of deployed infrastructure — the jump to 2.1 is significant. This is where a hybrid coexistence strategy becomes critical: running 1.6 and 2.1 simultaneously on the same CSMS, with protocol translation for legacy chargers.
Strategic Implication
OCPP 2.1 is not just a protocol update — it's the foundation for the next generation of charging services. V2G, dynamic tariffs, advanced security, and better interoperability are all built into the specification. CPOs who delay adoption risk being locked out of emerging revenue streams and regulatory compliance pathways.
The smart approach is not a big-bang migration but a staged transition: deploy 2.1-capable infrastructure alongside existing 1.6 fleets, use protocol translation layers where needed, and progressively migrate as hardware refresh cycles allow.