TC_003_CS — Regular Charging Session - Plugin First
TC_003_CS — Regular Charging Session - Plugin First
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 9.
Identification
| Field | Value |
|---|---|
| Test case name | Regular Charging Session - Plugin First |
| Test case Id | TC_003_CS |
| System under test | Charge Point |
Description
This scenario is used to start a Charging session.
Purpose
To test if the Charge Point is able to start a Charging Session when first doing plugin cable.
Prerequisite(s)
- N/a
Before (Preparations)
Configuration State(s):
- N/a
Memory State(s):
- N/a
Reusable State(s):
- N/a
Scenario Detail(s)
| Charge Point (SUT) | Central System (Tool) |
|---|---|
| [EV driver plugs in the cable.]; 1. The Charge Point sends a StatusNotification.req | 2. The Central System responds with a StatusNotification.conf |
| [EV driver presents identification.]; 3. The Charge Point sends an Authorize.req | 4. The Central System responds with an Authorize.conf |
| [Step 5 and step 7 may be reversed.]; 5. The Charge Point sends a StartTransaction.req | 6. The Central System responds with a StartTransaction.conf |
| [Step 5 and step 7 may be reversed.]; 7. The Charge Point sends a StatusNotification.req | 8. The Central System responds with a StatusNotification.conf |
Tool validation(s)
Charge Point side:
Step 1:
(Message: StatusNotification.req) status is Preparing
Step 7:
(Message: StatusNotification.req) status is Charging
Central System side:
Step 4:
(Message: Authorize.conf) idTagInfo.status is Accepted
Step 6:
(Message: StartTransaction.conf) idTagInfo.status is Accepted
Expected result(s) / behaviour
Charge Point side:
- N/a
Central System side:
- N/a