TC_023_CS — Start Charging Session – Authorize invalid
TC_023_CS — Start Charging Session – Authorize invalid
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 37.
Identification
| Field | Value |
|---|---|
| Test case name | Start Charging Session – Authorize invalid |
| Test case Id | TC_023_CS |
| System under test | Charge Point |
Description
This scenario is used to inform the Charge Point that the EV Driver is not Authorized to start a transaction.
Purpose
To test if the Charge Point does not start a transaction after Authorization fails.
Prerequisite(s)
- N/a
Before (Preparations)
Configuration State(s):
- Value for "MinimumStatusDuration" is "10".
- Value for "LocalPreAuthorize" is "true".
Memory State(s):
- N/a
Reusable State(s):
- N/a
Scenario Detail(s)
| Charge Point (SUT) | Central System (Tool) |
|---|---|
| [EV driver presents invalid identification.]; 1. The Charge Point sends an Authorize.req | 2. The Central System responds with an Authorize.conf |
| [EV driver plugs in the cable.]; 3. The Charge Point sends a StatusNotification.req | 4. The Central System responds with a StatusNotification.conf |
Tool validation(s)
Charge Point side:
Step 2:
(Message: Authorize.conf) idTagInfo.status is Invalid
Step 3:
(Message: StatusNotification.req) status is Preparing
Central System side:
- N/a
Expected result(s) / behaviour
Charge Point side:
The Charge Point does NOT start a transaction.
Central System side:
- N/a