VDV 463 Overview¶
VDV 463 defines the interface between a Charging and Load Management System (CMS) and upstream operational systems such as depot management systems, fleet management systems, or ITCS platforms.
Scope of this repository
This repository implements a FastAPI WebSocket facade and documentation generator for VDV 463. It validates message envelopes and payloads, returns placeholder confirmations for a subset of inbound actions, and publishes AsyncAPI and JSON schema artifacts. It does not implement full depot orchestration, authentication, subprotocol negotiation, or the full outbound charging-information lifecycle.
What the repo exposes¶
| Artifact | Purpose |
|---|---|
WS /vdv463/ws |
WebSocket endpoint that validates VDV 463 message envelopes and handles a subset of actions. |
GET /vdv463/docs/asyncapi |
Runtime-generated AsyncAPI 3.0.0 document describing the CMS WebSocket contract. |
docs/VDV463/schema/asyncapi.yaml |
Checked-in AsyncAPI source used for published documentation assets. |
docs/VDV463/schema/*.json |
Raw JSON schema snapshots for the major message payloads. |
docs/VDV463/asyncapi/index.html |
Generated interactive AsyncAPI viewer. |
Standard context¶
- Roles: CMS hosts the WebSocket server, upstream presystems connect as clients.
- Main message families:
BootNotification,ProvideChargingRequests, andProvideChargingInformation. - Transport expectations from the standard: secure WebSocket, TLS, HTTP Basic Authentication during the handshake, and WebSocket subprotocol
v1.463.vdv.de. - Current code coverage: envelope and payload validation, placeholder confirmations, error envelopes, and documentation generation.