Operator Glossary
This glossary explains terms the way an operating user needs them: what it is, why it matters and when you need to care.
| Term | What it means | Why / when the operator cares |
|---|---|---|
| Activation catalog | The list printed by evse start --dry-run and evse external-evcc-session-policy with the listener and EVCC commands for every protocol. | It is the authoritative recipe for your build; copy commands from it rather than from memory. |
| Annex B (ISO 15118-20) | The certificate profile of ISO 15118-20: ECDSA secp521r1 with SHA-512, defined key usages and identifiers. | Production TLS 1.3 material for ISO 15118-20 must follow it; the SECC identity is validated as an Annex B chain, not by DNS name. |
| Artifact root | Directory where ChargeLink stores run outputs: manifest, traces, reports, evidence. | Pass it explicitly on every command; back it up; verify integrity before sharing. |
| ATS | Abstract Test Suite: the structured inventory of test cases for a standard (ISO 15118-4, -21, -23). | Source of the case identifiers in packages and campaigns; ChargeLink ships identifiers and bindings, not standards text. |
| BPT | Bidirectional Power Transfer. | Select a BPT profile only when the DUT and bench support it; BPT is a reference-responder lane. |
| Campaign | A concrete selection of cases chosen and executed for one protocol, role and configuration. | Produced by test plan/test run or a package; keep the plan with the verdicts. |
| CAN / CAN-FD | Controller Area Network. | The scripted DC-CAN lanes model CAN virtually; their adapter names are descriptors and open no hardware. |
| Claim boundary | A field in every artifact that states what the evidence proves and does not prove. | Read it before quoting a result; it is the product's own limit statement. |
| API access token | A random 256-bit token the gRPC server writes to <state-root>\api-token at every start and requires as a bearer header on every call. | ChargeLink clients read it from CHARGELINK_API_TOKEN_FILE or the runtime root's integration\api-token; third-party clients must send it themselves. |
| Bench kit | The ChargeLink delivery package (ChargeLink-0.5.0-rc2-bench-kit-win64.zip): the CLI, the NI VeriStand owner host and broker, the plant model, the PC1 and PC2 scripts, manifests and notices. | Its docs\ folder describes the two-PC bench procedure; this manual documents the same binary. |
Contract (native-core-0.55) | The version tag of the JSON result format. | Automation should check it; a change means result shapes may have changed. |
| CP / PP | Control Pilot and Proximity Pilot, the low-level signalling of the charging interface. | Not implemented as protocol behaviour; exposed only as HIL adapter signals. |
| DUT / SUT | Device / System Under Test: the charger, vehicle or controller being tested. | Record its identity and firmware in every run and ticket. |
| EIM | External Identification Means: authorization outside Plug & Charge. | Use it first; it removes PKI from the problem. |
| Entitlement | A string in the license (base.runtime, role.evse, protocol.iso15118-20, package.iso15118_2.evse, ...). | Missing entitlements produce CL-LICENSE-001 on protected commands. |
| EVCC | Electric Vehicle Communication Controller, the vehicle side. | ChargeLink's EVCC role; see its boundaries in the EVCC Role Guide. |
| Evidence manifest | The JSON file (chargelink.protocol_test_evidence.v1) that binds a live or replayed capture to test cases with reviewed checks and hashes. | The only source of PASS/FAIL for protocol-first campaigns. |
| EVSE / SECC | Electric Vehicle Supply Equipment (the charger) and its Supply Equipment Communication Controller. | ChargeLink's EVSE role implements the SECC. |
| EXI | Efficient XML Interchange, the binary encoding of ISO 15118 messages. | ChargeLink's native codec; EXI decode verdicts appear in the frame trace. |
| Full-wire oracle manifest | A set of reference encodings for an ISO 15118-20 session, delivered as pc2\cases\full-wire-session-manifest.json. | Required by the EVCC live lane through an environment variable. |
| gRPC Integration API | chargelink.integration.v1, the automation boundary. | Loopback only; a per-start bearer access token on every call; no TLS transport. |
| HIL / SIL / MIL | Hardware-, Software-, Model-in-the-Loop. | ChargeLink runs SIL, with a deterministic HIL reference; it drives no physical HIL equipment. |
| Interface index / zone | Windows identifier of a NIC used with link-local IPv6 (%19). | Always the local machine's index; the wrong zone is the most common EVCC connection failure. |
| Link-local IPv6 | Addresses in fe80::/10 used by ISO 15118 discovery and sessions. | No router needed; firewall rules should be scoped to it. |
| Live case | The EVCC's identity and electrical parameters file for the ISO 15118-20 live lane (CHARGELINK_ISO20_LIVE_SEMANTIC_CASE). | Required; values are validated before the first packet. |
Manifest (manifest.json) | Inventory of a run with SHA-256 per file and redaction class. | Basis of integrity verification and support bundles. |
| Owner host | ChargeLink.Veristand.XilHost in pc1\host: owns the VeriStand plant, starts the SECC and the gRPC bridge, and writes the session result. | Started by Start-SeccSession.ps1 for every plant-coupled ISO 15118-20 session. |
| Package | A licensed test collection with catalogue, PICS/PIXIT templates, runner and reports. | Select by protocol and DUT role; check the entitlement. |
| PICS / PIXIT | Protocol Implementation Conformance Statement (what the SUT supports) and eXtra Information for Testing (values needed to run tests). | Generated per package; changing them creates a different campaign. |
| Plant-coupled lane | The ISO 15118-20 DC EIM runtime in which responses are computed from session state and plant measurements. | Requires the runtime profile, a plant gRPC endpoint and TLS 1.3 mutual. |
| PLC / SLAC | Power Line Communication and its link setup on the charging cable. | Not implemented; the bench's Ethernet path provides the link. A real PLC link to a vehicle or charger is connected through the DEVlink PLC Relay Unit, which is in development; see Connecting to Real PLC Hardware. |
| PnC | Plug & Charge: certificate-based authorization. | Fixture-driven; see the TLS page. |
| Profile | Named configuration: protocol, role, connector family, EXI mode. | Discover with profile list; deployment values are not profile data. |
| Reference responder | An EVSE lane that answers each decoded request with the validated reference response for that message. | Exercises transport, TLS and sequencing; does not compute dynamic values. |
| Replay | Hash verification of a deterministic simulation report (sim replay), or a validated capture used as campaign evidence. | Reproducibility without hardware; not new interoperability evidence. |
| Role lock | active\evse.lock.json / evcc.lock.json: one live session per role per runtime root. | Stale locks block starts; recover with runtime recover --stale-only. |
| Run ID | Identifier of one run, session and evidence set. | Pass it with --run-id; record it everywhere. |
| Runtime profile | JSON with the electrical tolerances and safe limits of the plant-coupled ISO 15118-20 lane. | A reviewed engineering decision recorded in evidence. |
| Runtime root | Directory with session state, locks and heartbeats. | Pass it explicitly; the license home is derived from it. |
| SDP | SECC Discovery Protocol on UDP 15118. | If SDP fails, nothing else starts; check NIC, IPv6 and firewall first. |
| Signal (canonical) | One of 67 transport-neutral values such as Vehicle.SocPct. | The mapping target of every integration. |
| TLS adapter | rustls (default) or Windows SChannel. | ISO 15118-20 requires rustls TLS 1.3 mutual; SChannel is TLS 1.2 for ISO 15118-2 peers. |
| Trace | Chronological machine-readable record of events and frames. | Primary evidence for where a session diverged; potentially sensitive. |
| V2GTP | Vehicle-to-Grid Transport Protocol framing that carries EXI payloads. | Its own troubleshooting layer between TCP/TLS and the application. |
| Verdict | pass, fail, inconclusive, blocked; trace verdicts observed, accepted, rejected, timeout, unsupported, faulted. | Blocked and inconclusive are not failures. |
| Watchdog / command age | Freshness check on plant commands (Runtime.CommandAge_ms, 500 ms lease). | Expiry drives the plant to the safe state. |
| XIL (ASAM) | Standardised test-bench interface (Framework, MAPort, EESPort). | A deterministic reference lane; not used by the VeriStand bench. |