Electric Vehicle (EV) charging involves multiple workflows, from discovering charging stations to making payments and tracking the charging process. This document provides a structured use case description for developers implementing the Beckn Protocol for EV charging, helping them map their workflows to Beckn API calls.
The EV Charging ecosystem follows an open network architecture, divided into multiple layers to ensure interoperability and transparency:
graph TD;
A["Application Layer (UEI)"] -->|"User Interactions"| B["Transaction Layer (Beckn)"]
B -->|"Standardized Protocol APIs"| C["Payments Layer"]
B -->|"Trust Mechanisms"| D["Trust Layer"]
B -->|"Support Services"| E["Support Layer"]
B -->|"Real-time Updates"| F["Real-time Data Streaming Layer"]
- Application Layer (UEI): User-facing apps and charging platforms.
- Transaction Layer (Beckn): Standardized interactions between BAP and BPP.
- Payments Layer: Handles secure payment processing.
- Trust Layer: Ensures identity verification and security.
- Support Layer: Customer service and dispute resolution.
- Real-time Data Streaming Layer: Provides live updates on charging sessions.
This document covers key interactions between a consumer (BAP) and a charging point operator (BPP):
- Discovery of charging sources (location, charger type, vehicle type, operator, etc.)
- Placing an order for charging (time, money, or units)
- Fetching quote
- Terms of service (payment, cancellation, refunds)
- Confirmation (advance, instant, etc.)
- Fulfillment of a charging order
- Status updates
- Order updates
- Cancellation
- Real-time tracking of power delivery
- Post-charging interactions
- Rating
- Grievance and support
- Refunds
A user searches for EV charging stations based on their preferences.
sequenceDiagram
participant User
participant UI
participant BAP
participant BPP
User->>UI: Search for EV chargers
UI->>BAP: Forward search request
BAP->>BPP: Fetch available chargers
BPP-->>BAP: Return charger list
BAP-->>UI: Send charger list
UI-->>User: Display available chargers
Once a charging station is selected, the user places an order.
sequenceDiagram
participant User
participant UI
participant BAP
participant BPP
User->>UI: Request charging quote
UI->>BAP: Forward quote request
BAP->>BPP: Fetch quote
BPP-->>BAP: Return quote
BAP-->>UI: Display quote & terms
UI-->>User: Show quote & terms
User->>UI: Confirm order
UI->>BAP: Forward order confirmation
BAP->>BPP: Place order
BPP-->>BAP: Confirm order
BAP-->>UI: Show confirmation
UI-->>User: Notify order confirmation
This includes real-time status updates, tracking, and cancellations.
sequenceDiagram
participant User
participant UI
participant BAP
participant BPP
User->>UI: Start charging session
UI->>BAP: Forward request
BAP->>BPP: Initiate charging
BPP-->>BAP: Charging started
BAP-->>UI: Notify charging in progress
UI-->>User: Show charging status
BPP-->>BAP: Periodic updates
BAP-->>UI: Forward updates
UI-->>User: Show live charging updates
User can provide feedback, raise grievances, or request refunds.
sequenceDiagram
participant User
participant UI
participant BAP
participant BPP
BPP-->>BAP: Notify charging completion
BAP-->>UI: Forward completion status
UI-->>User: Show final bill & request rating
User->>UI: Provide rating & feedback
UI->>BAP: Submit rating
BAP->>BPP: Record feedback
User->>UI: Raise grievance (if any)
UI->>BAP: Forward grievance request
BAP->>BPP: Process grievance
BPP-->>BAP: Respond to grievance
BAP-->>UI: Forward resolution
UI-->>User: Update grievance status
To clearly distinguish Beckn protocol APIs from other interactions, we use color coding:
- 🟢 Beckn Protocol APIs (BAP <> BPP)
- 🔵 UI Interactions (UI <> BAP, UI <> BPP)
| Workflow Step | API Endpoint | Type |
|---|---|---|
| Search charging stations | search |
🟢 BAP <> BPP |
| Fetch quote | select |
🟢 BAP <> BPP |
| Confirm order | confirm |
🟢 BAP <> BPP |
| Order status updates | track |
🟢 BAP <> BPP |
| Start charging | UI Action | 🔵 UI <> BAP |
| Provide rating | rating |
🟢 BAP <> BPP |
| Raise grievance | support |
🟢 BAP <> BPP |
This document follows an open network architecture, ensuring developers implementing Beckn Protocol for EV charging can map their business workflows to Beckn API calls effectively.