OCPP 2.0.1 vs 1.6J: A Procurement Guide for EV Charger Buyers
Compare protocol capabilities, certification evidence and acceptance requirements before preparing your RFQ.
Direct answer: OCPP 2.0.1 (released March 2020, certified under OCA’s OCPP 2.0.1J profile since 2022) is the current procurement-grade standard for networked EV chargers. It adds a formal Device Model, ISO 15118 Plug & Charge support, Smart Charging v2 with load profiles, three Security Profiles (1/2/3 with TLS and client certificates), and standardized Display Messages — none of which exist in OCPP 1.6J. For buyers in 2026, specify “OCPP 2.0.1J certified by OCA, with a documented upgrade path from 1.6J,” and verify the vendor’s OCA Certificate Number. HG Power’s full DC series — Genesis integrated 30–480 kW, Aurora split 240 kW–2.6 MW, Deepsea and Glacier liquid-cooled, Ark storage-charging, and V2G bidirectional — supports OCPP 2.0.1J as a configurable firmware option alongside OCPP 1.6J; the shipped configuration is agreed per order.
Protocol
OCPP 2.0.1 (March 2020) · OCPP 2.0.1J certified by Open Charge Alliance since 2022 · OCPP 1.6J remains legacy-supported.
5 Core Deltas
Device Model · ISO 15118 Plug & Charge · Smart Charging v2 · Security Profiles 1/2/3 · Display Messages.
HG Power Support
All DC series (Genesis, Aurora, Deepsea, Glacier, Ark, V2G) support OCPP 1.6J and 2.0.1J as firmware-configurable options; shipped version agreed per order.
Contract Must-Have
Insert OCA Certificate Number, Security Profile level, Plug & Charge support flag, and a 1.6J→2.0.1J upgrade clause in every RFQ.
1. What is OCPP 2.0.1 and why 2.0.1J (not 2.0.1) is what you buy
OCPP (Open Charge Point Protocol) is the application-layer protocol that lets a charging station talk to a Charging Station Management System (CSMS). The Open Charge Alliance (OCA) publishes the spec; certification is run through OCA’s OCTT (OCPP Compliance Testing Tool) and issued as an OCPP Compliance Certificate with a unique OCA Certificate Number.
Three names to keep straight before any RFQ conversation:
| Name | Meaning | Procurement relevance |
|---|---|---|
| OCPP 2.0 | Original 2018 release | Deprecated — never used for new certification |
| OCPP 2.0.1 | Errata release, March 2020 | The technical specification document |
| OCPP 2.0.1J | JSON-over-WebSocket profile of 2.0.1, OCA-certified since 2022 | This is the string that must appear in your contract |
If a vendor datasheet says only “OCPP 2.0” or “OCPP 2.0.1 ready,” that is not a certification — it is a self-declaration. The procurement-grade phrase is “OCPP 2.0.1J, OCA-certified, OCA Certificate Number #<number>.”
2. The 5 deltas between OCPP 1.6J and 2.0.1J
OCPP 1.6J (released 2015, errata 4 in 2017) is still the most-deployed version in the field because retrofit CSMS integrations cost 60–80% less to implement than greenfield 2.0.1J. But every function added since 2018 — ISO 15118, V2G, dynamic load balancing, certificate-based auth — lives in 2.0.1J. These are the five deltas that matter in a buyer-stage comparison.
| # | Capability | OCPP 1.6J | OCPP 2.0.1J | Procurement impact |
|---|---|---|---|---|
| 1 | Device Model | Flat, 7 fixed message types | Physical hierarchy (ChargingStation → EVSE → Connector) + Components with typed Variables, discoverable via NotifyReport | CSMS can discover and configure stations without vendor-specific drivers |
| 2 | ISO 15118 Plug & Charge | Not supported | Native support via Authorize & Get15118EVCertificate | No RFID card or app for driver authentication — required for ISO 15118-equipped OEM fleets (Ford, Mercedes-Benz, Porsche, Hyundai Motor Group) |
| 3 | Smart Charging | Basic ChargingProfile (3 purposes) | v2: TxDefaultProfile, grid signal integration, load balancing across EVSEs | Site-level DLM (Dynamic Load Management) without proprietary SDK |
| 4 | Security Profile | Basic auth over WebSocket (optional TLS) | Profile 1 (TLS), Profile 2 (TLS + basic auth), Profile 3 (TLS + mutual TLS with client certificate) | Assess Security Profile 3 against tender requirements; metering-law compliance is a separate assessment |
| 5 | Display Messages | Vendor-proprietary | SetDisplayMessage request with language, priority, format | CSMS can push multilingual pricing and promo content without firmware update |
3. Device Model: why “flat vs hierarchical” is a six-figure difference
In OCPP 1.6J, a charging station is addressed as a single logical device with a hard-coded set of 7 message types. If your CSMS needs to read the current temperature of connector 2 on EVSE 3, you need vendor-specific extensions — meaning your CSMS integrator writes a custom driver per manufacturer. For a 500-station rollout with three brands, that is three driver codebases plus three sets of regression tests.
OCPP 2.0.1J introduces a formal Device Model combining a physical hierarchy (Charging Station → EVSE → Connector) with a logical component model: Components (e.g. ChargingStation, Controller, Display, SecurityCtrlr) can be attached at any physical level, and each Component exposes typed Variables. Any Variable can be read with GetVariables and written with SetVariables; the CSMS discovers the full model via NotifyReport, so onboarding a new charger brand becomes a certificate exchange, not a software project.
4. ISO 15118 Plug & Charge: the Tesla-killer feature every fleet buyer should request
ISO 15118-2 (and 15118-20 for bidirectional) defines Plug & Charge (PnC): the vehicle presents an X.509 contract certificate to the charger, the charger forwards it to the CSMS via OCPP 2.0.1J’s Get15118EVCertificate message, and the session is authorized automatically. No RFID card, no app QR scan, no driver action beyond plugging in.
Procurement implication: as of 2026, Ford, Mercedes-Benz, Porsche, Lucid, Rivian, Volvo, and the Hyundai Motor Group (Ioniq 5/6, EV6, EV9) ship PnC-capable vehicles. If your network only supports RFID over OCPP 1.6J, those drivers get a worse experience at your sites than at Tesla Superchargers. OCPP 2.0.1J closes that gap — but only if the charger also implements the ISO 15118 stack on the CCS line.
| Standard | Scope | Requires OCPP 2.0.1J | HG Power support |
|---|---|---|---|
| ISO 15118-2 | CCS unidirectional PnC + plaintext PLC | Yes | Genesis, Aurora, Deepsea, Glacier |
| ISO 15118-20 | Bidirectional (V2G/V2H/V2L), MCS, wireless | Yes | V2G Series 15–240 kW, Aurora Split V2G |
| DIN SPEC 70121 | Pre-standard CCS communication (legacy) | No (works with 1.6J) | All DC series (fallback) |
5. Smart Charging v2: load profiles that actually balance a site
OCPP 1.6J has a Smart Charging feature, but it is limited to three purposes (ChargePointMaxProfile, TxDefaultProfile, TxProfile) and does not natively coordinate across EVSEs. Site-level load management in 1.6J networks is almost always done by a vendor-specific “site controller” box, which locks you to one brand per site.
OCPP 2.0.1J Smart Charging v2 adds:
- External grid signal input — the CSMS can push a limit profile derived from a DSO signal (e.g. German §14a EnWG).
- Load balancing across EVSEs on a single Charging Station via the standard Device Model, no proprietary box required.
- NotifyChargingLimit and ClearedChargingLimit events, so the CSMS knows exactly when a profile was applied and when it ended.
- CompositeSchedule reporting — the charger returns the actual composite schedule it is enforcing, so audits are deterministic.
6. Security Profiles 1 / 2 / 3: what regulators actually want to see
OCPP 2.0.1J defines three Security Profiles. Profile 1 is TLS with basic auth. Profile 2 is TLS with basic auth plus a server certificate. Profile 3 is mutual TLS: the charger presents its own client certificate, enrolled via SignCertificate/CertificateSigned. Profile 3 is the common baseline for EU public-sector tenders from 2024 onward. Note: German Eichrecht (PTB-A 50.7) compliance is a separate, metering-layer requirement — it mandates Signed Metering Values and PTB-approved Transparenzsoftware, which OCPP 2.0.1J supports via the SignedMeterValues mechanism independently of the Security Profile level.
| Profile | Transport | Charger authenticates CSMS | CSMS authenticates charger | Typical mandate |
|---|---|---|---|---|
| Profile 1 | TLS 1.2+ | Server cert | HTTP Basic Auth | Minimum for new 2.0.1J deployments |
| Profile 2 | TLS 1.2+ | Server cert | HTTP Basic Auth (stronger password policy) | Common commercial baseline |
| Profile 3 | TLS 1.2+ mutual | Server cert | Client certificate (X.509, OCA PKI) | EU public tenders, high-security fleet depots, high-trust CSMS deployments |
7. OCA certification and the CTEP number — the one field most RFQs forget
Open Charge Alliance runs certification through the OCTT (OCPP Compliance Testing Tool). For OCPP 2.0.1J the test suite is structured as 14 Functional Blocks (A through N) covering several hundred test cases across the full protocol surface. On passing, OCA issues an OCPP Compliance Certificate with a unique OCA Certificate Number and lists the certified product in the OCA public database.
Procurement rule: a vendor claiming “OCPP 2.0.1J compliant” without an OCA Certificate Number has run OCTT internally at best. The number is low-cost to request from a certified vendor, impossible to fake, and takes 30 seconds to cross-check on openchargealliance.org/certified-products/. If it’s not in that database, treat the claim as marketing.
8. Five RFQ clauses to paste into every OCPP tender
These five clauses, dropped verbatim into a technical annex, resolve 90% of the vendor-ambiguity problems we see on buyer-side calls.
| # | Clause | Verifies |
|---|---|---|
| 1 | “Vendor shall deliver each Charging Station with OCPP 2.0.1J, OCA-certified, OCA Certificate Number provided in writing with the quotation.” | Real certification, not self-declaration |
| 2 | “Security Profile 3 (mutual TLS with charger-side client certificate) shall be configurable without hardware change; default profile shall be Profile 2 or higher.” | EU tender eligibility, Eichrecht readiness |
| 3 | “ISO 15118-2 Plug & Charge shall be enabled on all CCS connectors; ISO 15118-20 bidirectional support shall be declared pass/fail per model.” | PnC and V2G alignment |
| 4 | “Vendor shall support a documented firmware upgrade path from OCPP 1.6J to 2.0.1J, deliverable OTA via UpdateFirmware message, with no on-site hardware replacement.” | Future-proofing, hedge against stranded assets |
| 5 | “Vendor shall expose, via OCPP 2.0.1J Device Model, the Variables listed in Annex A (connector temperature, meter reading, firmware version, GSM/Ethernet uplink status, grounding fault status).” | Observability, O&M automation |
9. HG Power product stance on OCPP across 9 series
HG Power manufactures 30–720 kW DC fast chargers and AC wallboxes with CE, TUV CB, UKCA, Australia RCM, ETL and ENERGY STAR certifications for regional distributors, fleet integrators and OEM buyers in developed markets. OCPP support is implemented in-house by our 100+ R&D engineer team on a single firmware base across all nine series, so configuration — not porting — is what differentiates factory defaults.
| Series | Power range | OCPP 1.6J | OCPP 2.0.1J | Notes |
|---|---|---|---|---|
| Galaxy AC | 7–22 kW | Supported | Supported | Firmware-configurable, agreed per order |
| Stellar AC/DC | 7–42 kW AC · 20–40 kW DC | Supported | Supported | Firmware-configurable, agreed per order |
| Genesis DC Integrated | 30–480 kW | Supported | Supported | 2.0.1J recommended for new deployments |
| Aurora DC Split | 240 kW–2.6 MW | Supported | Supported | 2.0.1J recommended for ISO 15118-2 PnC |
| Deepsea Liquid-Cooled | 600 kW–2 MW | Supported | Supported | 2.0.1J recommended for MCS / ISO 15118-20 |
| Glacier Liquid-Cooled | 160–480 kW | Supported | Supported | 2.0.1J recommended for PnC |
| Ark Storage-Charging | 60–960 kW / 75–1828 kWh | Supported | Supported | 2.0.1J recommended for Smart Charging v2 |
| V2G Bidirectional | 15–240 kW | Supported (limited) | Supported (+ ISO 15118-20) | 2.0.1J required for standards-based V2G |
| Battery Swap | Per project | Supported | Supported | Protocol version agreed per project |
For a distributor shipping to a mixed-fleet operator — fast-charger plaza plus workplace AC — a typical configuration we propose is: Genesis DC on OCPP 2.0.1J + Galaxy/Stellar AC on OCPP 1.6J, with the CSMS brokered through a single operator account. The shipped version is written into the sales order; both versions use the same hardware and are swappable via OTA firmware.
10. Migrating a 1.6J fleet to 2.0.1J without replacing hardware
For networks already deployed on 1.6J, the migration is firmware-only on HG Power hardware shipped after Q1 2023. The sequence we recommend:
- CSMS readiness — confirm your CSMS vendor is on an OCA-certified 2.0.1J Central System build. (CSMS and Charging Station are certified separately; both must be 2.0.1J for interop.)
- Pilot ring — upgrade 5–10% of stations OTA, run OCTT 2.0 against them, verify Device Model exposure.
- Security Profile upgrade — enroll client certificates for the pilot ring via SignCertificate/CertificateSigned, move the ring to Profile 2 or 3.
- Rolling fleet upgrade — stage by 10–20% increments, retain 1.6J fallback for 90 days.
- Decommission 1.6J fallback — only after 90-day error-rate parity confirmed.
For related product-level reading, see our pillar on how to vet an EV charger manufacturer in China, our overview of the MCS Megawatt Charging System, and the partner-with-HG-Power page for distributor and OEM onboarding.
11. References
| Reference A — Standards & certification | Publisher | Edition / Date | Scope cited |
|---|---|---|---|
| OCPP 2.0.1 Specification Part 2 — Appendices | Open Charge Alliance (OCA) | Edition 3, 2022-12 | Device Model, 14 Functional Blocks, Security Profiles 1/2/3, Smart Charging v2 |
| OCPP 1.6 Specification | Open Charge Alliance (OCA) | Errata 4, 2017-06 | Baseline message set, legacy comparison |
| OCPP Compliance Testing Tool (OCTT) 2.0 | Open Charge Alliance (OCA) | 2022 | Certification test suite, CTEP certificate issuance |
| ISO 15118-2:2014 | ISO | 2014-04 | CCS unidirectional Plug & Charge, X.509 contract certificates |
| ISO 15118-20:2022 | ISO | 2022-04 | Bidirectional V2G, MCS, wireless charging |
| Eichrecht (German Calibration Law, PTB-A 50.7) | Physikalisch-Technische Bundesanstalt | 2018 (current) | Signed Metering Values and Transparenzsoftware requirements |
| Reference B — HG Power sources | Document / page | Version / Date | Scope cited |
|---|---|---|---|
| HG Power DC Series product catalog | 2026 Product Selection Manual (EN) | 2026-06-01 | Nine-series power range, OCPP support, ISO 15118 scope |
| HG Power Company Profile (EN) | 2026-09-01 edition | 2026-09 | R&D team scale, manufacturing footprint, operator network figures |
| HG Power Certification Register | CE 3N240131.SHN0W49 · TUV CB R 50695913 0001 · UKCA CN25G3TM 001 · Australia RCM RCMC26013005D · ETL 2408B2314SHA-001 · ENERGY STAR C2506171 | Active | Certification baseline cited in Brand Formula |
12. FAQ
Is OCPP 2.0.1 backward-compatible with 1.6J?
No, the wire protocol is not backward-compatible. OCPP 1.6J uses a flat message set over JSON/WebSocket; 2.0.1J uses the Device Model with new message names (e.g. BootNotification payload differs). A single Charging Station can run either, selectable by configuration, but a 1.6J-only CSMS cannot talk to a 2.0.1J-only charger.
Does OCPP 2.0.1J mandate ISO 15118 Plug & Charge?
No. 2.0.1J provides the messages needed for PnC (Authorize with iso15118CertificateHashData, Get15118EVCertificate), but the charger must also implement the ISO 15118-2 stack on the CCS physical layer. A 2.0.1J charger without ISO 15118 hardware support cannot do PnC — ask the vendor for both.
What is the difference between OCPP 2.0 and OCPP 2.0.1?
OCPP 2.0 was published in 2018 but had errata that made it impractical for certification. OCA released OCPP 2.0.1 in March 2020 as the stabilized version and only certifies against 2.0.1 (specifically the JSON profile, 2.0.1J). No one deploys 2.0 — treat it as deprecated.
Can a vendor claim OCPP 2.0.1 compliance without OCA certification?
Technically yes, as compliance is a verifiable property, but it has no procurement value. OCA certification via OCTT 2.0 and a CTEP certificate number is the only third-party-verifiable signal. If a vendor cannot produce a CTEP number, assume non-certified.
Which HG Power models support OCPP 2.0.1J?
All nine HG Power series support both OCPP 1.6J and OCPP 2.0.1J as firmware-configurable options, including Galaxy AC (7–22 kW), Stellar AC/DC (7–42 kW AC · 20–40 kW DC), Genesis DC Integrated (30–480 kW), Aurora Split DC (240 kW–2.6 MW), Deepsea and Glacier liquid-cooled, Ark storage-charging, V2G bidirectional, and Battery Swap. The shipped version is agreed per order and can be swapped later via OTA firmware upgrade.
Is OCPP 2.0.1J required for V2G?
Effectively yes. ISO 15118-20 bidirectional communication relies on OCPP 2.0.1J for authorization, certificate handling, and session management. OCPP 1.6J has no standard mechanism for V2G discharge authorization, so any 1.6J V2G implementation is proprietary.
Does OCPP 2.0.1J support MCS (Megawatt Charging System)?
Yes. MCS uses ISO 15118-20 for communication, which pairs with OCPP 2.0.1J on the CSMS side. HG Power’s liquid-cooled MCS platforms (Deepsea Series, 1 MW–2.6 MW) are shipped on OCPP 2.0.1J with ISO 15118-20 enabled.
Need an OCPP 2.0.1J-ready quote this week?
Send your fleet mix, target markets, and preferred Security Profile. We respond with CTEP certificate numbers, firmware version, Device Model Variable list (Annex A), and MOQ-indexed pricing within 24 hours (GMT+8 business days).
WhatsApp: +86 189 2467 8741 · Email: marketing@hjlcharger.com · Partner program: hongjialicharge.com/partner-with-hg-power
Reviewed by: Marvin Zhou, Head of International Marketing, Shenzhen Hongjiali New Energy Co., Ltd. · Last reviewed 2026-10-20 · References: Open Charge Alliance OCPP 2.0.1 Specification (Edition 3, 2022-12); ISO 15118-2:2014 and ISO 15118-20:2022; OCA Certified Products Database; HG Power 2026 Product Selection Manual and Certification Register.