Skip to content

Use Cases

These scenarios describe the VDV 261 protocol semantics and the operational intent behind the data model. In this repository, only payload validation, schema publication, and diagnostic acknowledgement are implemented directly.

  • VAS discovery and HTTPS tunnel establishment during ISO 15118 handshake.
  • Initial parameter synchronisation (seq = 0) carrying the full vehicle dataset.
  • Cyclic delta updates during charging with backend directives in acknowledgements.
  • Backend-driven preconditioning lifecycle.
  • Resilience flows for retries, idle timeouts, and reconnects.
  • Schema discovery for integrators consuming the JSON/OpenAPI definitions.
  • Diagnostic reporting via /vdv261/v2icp/diagnostics.

Sequence Flows

Detailed diagrams and example payloads live in VDV_261_06_Communication_Sequences.md. The happy-path summary:

sequenceDiagram
    participant EV as EVCC
    participant SECC as SECC
    participant BE as Backend

    EV->>SECC: ServiceDiscoveryReq (ISO 15118)
    SECC-->>EV: ServiceDiscoveryRes (ServiceID 3)
    EV->>SECC: Request VAS 3 InternetAccess
    EV->>BE: POST /vdv261/v2icp/messages (seq 0, full set)
    BE-->>EV: 200 OK (seq 0, backend directives)
    EV->>BE: POST /vdv261/v2icp/messages (seq n, deltas)
    BE-->>EV: 200 OK (seq n, updated directives)