Skip to content

Topology & Architecture

flowchart LR
    EVCC["EVCC (Vehicle)"]
    SECC["SECC (Charger)"]
    VAS["VAS 3 InternetAccess<br/>HTTPS tunnel"]
    CMS["Depot Backend / CMS"]
    OCPP["OCPP Backend"]

    EVCC -- ISO 15118 (PLC) --> SECC
    SECC -. exposes .-> VAS
    VAS --> CMS
    SECC -- OCPP (optional) --> OCPP
  • Network directionality: outbound HTTPS from EVCC through SECC to backend; SECC acts as a gateway only.
  • Trust boundaries: TLS terminates at backend; EVCC validates backend cert; SECC does not inspect payloads.
  • Dependencies: IPv6 routing plus DNS or static addressing per V2ICP-pre variants; optional OCPP 2.0.1 for charger certificate and config management.
  • Repository scope: this codebase lives at the backend boundary and documents the CMS-facing HTTP contract rather than the EVCC or SECC behaviour.
  • Related spec content: see VAS background and network variants in VDV_261_04_Technical_Specification.md.