Skip to content

Use Cases

These scenarios describe the VDV 463 operating model and the lifecycle shown in the supporting communication-sequence material. In this repository, the directly implemented behaviour is narrower: the runtime currently validates and confirms BootNotification and ProvideChargingRequests, while the broader charging-information flow is documented for alignment and future completion.

  • Presystem connection establishment through BootNotification.
  • Charging request publication from the upstream system through ProvideChargingRequests.
  • CMS publication of depot, station, charging point, and vehicle telemetry through ProvideChargingInformation.
  • Charging lifecycle transitions such as preparing, charging, finishing, and availability reset.
  • Updated departure or charging targets arriving while a session is active.
  • Recovery after temporary CMS or upstream unavailability.
  • Documentation and schema discovery via AsyncAPI and JSON schema artifacts.

Sequence Flows

Detailed business flows and example payloads live in VDV_463_6_Communication_Sequences.md and the BDD source material in test/vdv463/router_sequences.feature.

sequenceDiagram
    participant UP as Upstream Presystem
    participant CMS as CMS

    UP->>CMS: BootNotification request
    CMS-->>UP: BootNotification confirmation
    UP->>CMS: ProvideChargingRequests request
    CMS-->>UP: ProvideChargingRequests confirmation
    CMS->>UP: ProvideChargingInformation update
    UP-->>CMS: ProvideChargingInformation confirmation