VDV 261 Overview

VDV 261 defines the Vehicle-to-Infrastructure Communication Protocol (V2ICP) used to exchange operational charging data between the EVCC in the vehicle and a depot backend over ISO 15118 Value Added Service 3 InternetAccess.

Scope of this repository

This repository implements a FastAPI facade for the VDV 261 wire contract. It validates request and response payload shapes, publishes JSON/OpenAPI schemas, and provides documentation assets. It does not establish VAS sessions, enforce TLS or HTTP Basic Authentication, persist diagnostics, or compute depot directives.

What the repo exposes

Artifact	Purpose
POST /vdv261/v2icp/messages	Validate a V2ICP vehicle payload and return a placeholder backend response.
POST /vdv261/v2icp/diagnostics	Accept a diagnostic event and acknowledge it with 202 Accepted.
GET /vdv261/schemas	List the published schema identifiers.
GET /vdv261/schemas/{schema_name}	Return the JSON schema for a documented model.
GET /vdv261/openapi.json	Internal OpenAPI source used to generate the published Redoc page.

Standard context

• Purpose: tunnel HTTPS telemetry and directives between the EVCC and the depot backend during an ISO 15118 charging session.
• Roles: EVCC (vehicle), SECC (charging station gateway), backend/CMS (terminates HTTPS and orchestrates depot logic).
• Protocol expectations from the standard: IPv6 networking, VAS 3 InternetAccess, TLS, VIN-based HTTP Basic Authentication, and JSON payloads with a rolling seq counter.
• Current code coverage: request validation, schema publication, and documentation generation only.

Read This Section In Order

• Topology & Architecture
• API
• Data Models
• Use Cases
• Implementation Details
• References