TC_004_1_CS — Regular Charging Session – Identification First
TC_004_1_CS — Regular Charging Session – Identification 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 – Identification First |
| Test case Id | TC_004_1_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 authorization.
Prerequisite(s)
- N/a
Before (Preparations)
Configuration State(s):
- Value for "MeterValueSampleInterval" is <Configured Meter Value interval>.
Memory State(s):
- N/a
Reusable State(s):
- N/a
Scenario Detail(s)
| Charge Point (SUT) | Central System (Tool) |
|---|---|
| 1. Execute Reusable State Authorized | |
| 2.Manual Action: EV driver plugs in the cable. | |
| 3. The Charge Point sends a StartTransaction.req | 4. The Central System responds with a StartTransaction.conf |
| 5. The Charge Point sends a StatusNotification.req | 6. The Central System responds with a StatusNotification.conf |
| Note: Step 3 and step 5 may be reversed. |
Tool validation(s)
Charge Point side:
Step 5:
(Message: StatusNotification.req) status is Charging
Central System side:
Step 4:
(Message: StartTransaction.conf) idTagInfo.status is Accepted
Expected result(s) / behaviour
Charge Point side:
- N/a
Central System side:
- N/a