Conformance testing: ISO 15118-4, -5 and Testivals

How ISO 15118 implementations are tested for conformance: test systems that play the other side, test suites built from test purposes, PICS and PIXIT, and the CharIN Testivals for interoperability. And why analysing a capture is a different activity.

Which part tests what

Conformance partTests the requirements ofScope
ISO 15118-4ISO 15118-2Network and application layer: SDP, V2GTP, the app handshake, message sequences, parameters, timers, TLS
ISO 15118-5ISO 15118-3Physical and data link layer: signal levels, SLAC, timing on the powerline
ISO 15118-9ISO 15118-8Wireless physical and data link layer
ISO 15118-21:2025ISO 15118-20Second generation: the requirements common to all charging types, network to application layer, as tables of abstract test cases
DIN SPEC 70122DIN SPEC 70121Conformance tests for the DIN protocol

ISO 15118-21 was published in 2025 (ISO catalogue). ISO 15118-22 is an approved work item and ISO/PAS 15118-23 was approved in 2026, as further conformance parts for the second generation; check their scope in the ISO catalogue before quoting it. The edition of DIN SPEC 70122 is to be verified too.

How a conformance test is built

  • The system under test (SUT) is either an EVCC or an SECC. The test system plays the other side: it acts as SECC to test a car and as EVCC to test a charger.
  • The methodology follows ISO/IEC 9646: requirements are turned into test purposes, test purposes into test cases, and the test cases are grouped into a test suite structure (for example by message or by layer).
  • Test cases are written in TTCN-3, a test description language, so different test tool vendors run the same logic.
  • Each test case ends in a verdict: pass, fail or inconclusive. A failed test case names the requirement it traces back to.
  • Test cases deliberately inject faults: a late response, a wrong SessionID, an unknown response code, a missing message, to see that the SUT reacts as the standard requires.

The conformance parts describe what to test, not a product. Several commercial test systems implement them; a lab picks one and runs the test suite with the SUT's PICS and PIXIT.

PICS and PIXIT

DocumentStands forContentUsed for
PICSProtocol Implementation Conformance StatementWhich options of the standard the implementation claims: AC or DC, EIM or PnC, TLS, which energy transfer modes, optional messagesSelecting which test cases apply
PIXITProtocol Implementation eXtra Information for TestingValues the test system needs to run: addresses, ports, the SUT's own timing parameters, certificates, how to trigger a sessionParameterising the selected test cases

A test report is only meaningful together with the PICS it was run against: a charger that does not claim Plug and Charge is not failed for it, it is simply not tested for it.

Testivals and interoperability

Conformance to the standard does not guarantee that two products work together. CharIN, the association behind CCS, organises Testivals where car makers, charger makers and test tool vendors bring their products and run sessions against each other for several days, in Europe, North America and Asia. Findings go back to the implementers and, where the standard is ambiguous, to the standards committees. CharIN also runs a conformance test programme based on the conformance parts.

Captures taken at Testivals are a good source for this tool: record every pairing with a powerline sniffer and, where possible, a CP logger, so a failing combination can be analysed after the event.

How this tool relates

Conformance test systemThis tool
Active: it is one side of the session and drives the SUTPassive: it reads a capture of two real products talking
Injects faults to provoke reactionsSees only what happened in that session
Test cases with pass, fail or inconclusive against numbered requirementsChecks that pass, fail or do not apply, against a configurable limit profile
Runs against the PICS of one productJudges both sides at once and names which side a failure is on
Result can support a certificationResult is for debugging and triage, not for certification

Many of the tool's checks resemble test purposes (message order in SQ-01, response times in TIM-01, SLAC timing in SL-04 and SL-05), and a lab can use the tool to understand why a conformance test case failed if the test system exports a capture. But a passing verdict here does not mean a product is conformant: an untested option or a fault that did not occur in this session is simply not seen.

Sources

  • ISO 15118-4:2018, conformance tests for ISO 15118-2
  • ISO 15118-5:2018, conformance tests for ISO 15118-3
  • ISO 15118-21:2025, conformance tests for the common requirements of ISO 15118-20, ISO catalogue
  • ISO/IEC 9646, conformance testing methodology
  • CharIN, Testival events and conformance programme