TC_023_2_CSMS — Start Charging Session – Authorize expired
TC_023_2_CSMS — Start Charging Session – Authorize expired
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Central System, page 141.
Identification
| Field | Value |
|---|---|
| Test case name | Start Charging Session – Authorize expired |
| Test case Id | TC_023_2_CSMS |
| System under test | Central System |
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 Central System is able to provide an expired response on an Authorize.req.
Prerequisite(s)
The Central System has an idTag in memory with status 'Expired'.
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 presents expired identification.]; 1. The Charge Point sends an Authorize.req | 2. The Central System responds with an Authorize.conf |
Tool validation(s)
Charge Point side:
- N/a
Central System side:
Step 1:
(Message: Authorize.conf) idTagInfo.status is Expired
Expected result(s) / behaviour
Charge Point side:
- N/a
Central System side:
- N/a