KopherBit
Charging Communication

KopherV2G: ISO 15118 / DIN 70121 V2G software stack

KopherV2G is a V2G charging communication software stack provided by KopherBit, integrating SLAC, SDP, TLS, V2G TP, EXI codec and ISO 15118-2 / ISO 15118-20 / DIN 70121 state machine, which can be deployed in EVCC (vehicle side) and SECC (pile side), and integrated with the KopherSAR + KopherConfig toolchain.

Summary

KopherV2G is a V2G (Vehicle-to-Grid) charging communication software stack provided by KopherBit, integrating SLAC (ISO 15118-3), SDP (SECC Discovery Protocol), TLS, V2G TP (Transfer Protocol), EXI (Efficient XML Interchange) codec, and ISO 15118-2 / ISO 15118-20 / DIN 70121 Three sets of state machines.It can be deployed on EVCC (vehicle side) or SECC (pile side), and integrated with KopherSAR, KopherConfig tool chain, meeting the needs of PnC (Plug & Charge), two-way charging, MCS and other scenarios.

Technical Role

KopherV2G In the overall software architecture:

  • Top: Interface with the vehicle application layer (BMS, VCU, EMS) through CAN/CAN FD.
  • Medium: Implement V2G application layer protocol state machine (charging session process).
  • Bottom: Exchange messages with the peer (EVCC ↔ SECC) via IPv6 / TCP / TLS / V2G TP / EXI.
  • Physical layer: HomePlug Green PHY (HPGP) PLC module, paired by SLAC.

Architecture

LevelsModsCharacters
PhysicalHomePlug Green PHY (HPGP)PLC physical layer, carrying communication on CP/PE lines.
LinkSLACSignal attenuation pairing to ensure EVs are paired with a single EVSE.
NetworkIPv6 / DHCPAutomatically obtain IPv6 link-local and establish a link.
DiscoverySDPThe EV side queries the SECC IPv6 endpoint through broadcast.
TransportTCP / TLSEstablish transport layer connection; PnC forces TLS.
ApplicationV2G TP + EXIV2G message packetization and serialization, binary XML encoding and decoding.
State MachineISO 15118-2 / -20 / DIN 70121Three sets of coexisting charging session state machines.
CryptoCryptoService (KopherSAR Csm)TLS handshake, X.509 chain verification, ECDSA signature, Contract Certificate management.
Vehicle AdapterBMS / EMS / VCUInterfaces with the vehicle network and provides SoC, target voltage, current, and energy requirements.

Key Capabilities

  • Three protocols coexist: ISO 15118-2 (AC/DC PnC + EIM), ISO 15118-20 (DC bidirectional, MCS, WPT), DIN 70121 (DC legacy).
  • Full PnC support: TLS 1.2/1.3, X.509 chain verification, Contract Certificate installation/update/revocation.
  • EVCC shares the stack with SECC: symmetrical implementation, the vehicle side and the pile side can share the underlying sub-module.
  • EXI Efficient Codec: Significantly reduces message size and processing cost compared to original XML.
  • AUTOSAR integration: CryptoService docking KopherSAR Csm/KeyM; configuration is managed uniformly by KopherConfig.
  • HSM Private Key Protection: Store the EVCC private key in the HSM on KCU GEN2 (TC387QP).
  • Interoperability Verification: KCU Gen2 Testbench provides interoperability test procedures with multiple charging piles.

Deployment mode

DeploymentDescription
EVCC is built into KCU GEN2 (Phase B)KopherV2G is an optional module of KCU GEN2 and shares the main processor with BMS/VCU.
EVCC Independent PLC daughter boardAdopt independent hardware deployment to facilitate integration with existing non-KopherBit VCU.
SECC DeploymentUsed at the charging pile end, in conjunction with the pile end PLC module and power control logic.

Engineering Inputs Required

InputPurpose
Charging scenariosAC/DC, one-way/two-way, PnC/EIM, applicable protocol version.
BMS signal matrixSoC, target voltage/current, maximum allowable voltage/current, temperature, error code.
EMS signal (Dynamic Mode)Energy demand, remaining time, charging target SoC.
OEM PKI structureOEM CA, Contract CA, Trust Anchors, OCSP endpoints.
HSM configurationPrivate key storage location and access policy.
Vehicle NetworkCAN/CAN FD signal definition between EVCC and BMS, VCU, EMS.
Interoperability testing requirementsEVSE brands and market areas expected to be supported.

How KopherBit Supports This

  • Software stack: KopherV2G Full software license, including source code or pre-compiled options.
  • INTEGRATION: Deployable on KCU GEN2 with KopherSAR + KopherConfig + KopherBoot.
  • PKI Consultant: Assist customers in designing OEM CA, Contract CA, and Trust Anchors.
  • Interoperability: KCU Internal verification frameworks such as Gen2 Testbench, Charging Plug Lock Test, etc.

FAQ

Does KopherV2G support both EVCC and SECC?

yes.EVCC (vehicle side) and SECC (pile side) share the underlying sub-modules (SLAC, SDP, TLS, V2G TP, EXI), only the state machine direction is different.Both roles can be deployed in the same project.

Does it support two-way charging (V2G/V2H/V2L)?

support.Through the implementation of ISO 15118-20 BPT process, combined with the reversible OBC/DC-DC and BMS discharge permission on the EV side, bidirectional energy flow can be achieved.

What is the installation process for Contract Certificate?

EV passes the CertificateInstallation message process at the charging pile that supports PKI, and the back-end CPS issues and returns the Contract Certificate; EVCC stores it in the secure memory.

Differences from other V2G stacks like OpenV2G?

KopherV2G is a commercial authorized version, including complete three-protocol state machine, PnC TLS, HSM integration and commercial support.OpenV2G is an open source implementation with a limited feature set and requires self-integration.Customers can choose commercial licensing to speed up launch and obtain long-term maintenance.

Does it comply with ISO 15118 interoperability testing?

KopherV2G is designed to comply with the ISO 15118 specification and supports interoperability with the ISO 15118 Test Symposium test brand.The specific test results are subject to the actual project.

JSON-LD

{
"@context": "https://schema.org",
"@type": "TechArticle",
"headline": "KopherV2G: ISO 15118 / DIN 70121 V2G software stack",
"description": "KopherV2G integrates SLAC / SDP / TLS / V2G TP / EXI with ISO 15118-2 / -20 / DIN 70121 state machine, can be deployed in EVCC or SECC.",
"url": "https://kopherbit.com/knowledge/kopherv2g-stack/",
"datePublished": "2026-05-09",
"dateModified": "2026-05-09",
"inLanguage": "zh-TW",
"keywords": ["KopherV2G", "ISO 15118", "DIN 70121", "EVCC", "SECC", "PnC"],
"articleSection": "Charging",
"author": { "@type": "Organization", "name": "KopherBit", "url": "https://kopherbit.com" },
"publisher": { "@type": "Organization", "name": "KopherBit", "logo": { "@type": "ImageObject", "url": "https://kopherbit.com/logo.png" } }
}