TC_C_04_CS — Local Stop Transaction - Different idToken
TC_C_04_CS — Local Stop Transaction - Different idToken
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block C. Authorization, page 86.
Identification
| Field | Value |
|---|---|
| Test case name | Local Stop Transaction - Different idToken |
| Test case Id | TC_C_04_CS |
| Use case Id(s) | C01, C04, E07 |
| Requirement(s) | N/a |
| System under test | Charging Station |
| Functional block | C. Authorization |
Description
The EV Driver is able to stop an ongoing transaction, by locally presenting his IdToken.
Purpose
To verify whether the Charging Station does not stop the charging session when a different idToken is presented, than the one used to start the transaction.
Prerequisite(s)
- The Charging Station supports at least one authorization method described at the following Use cases; C01, C04.
- The Charging Station does NOT use one idToken reader for multiple EVSE.
Before (Preparations)
Configuration State:
- AuthCtrlr.AuthEnabled is true (If implemented AND ReadWrite) AuthCtrlr.DisableRemoteAuthorization is false (If implemented)
Memory State:
- N/a
Reusable State(s):
- State is EnergyTransferStarted
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| Manual Action: Present a different idToken than used to start the transaction. | |
| 1. The Charging Station sends an AuthorizeRequest | 2. The OCTT responds with an AuthorizeResponse; with idTokenInfo.status Accepted |
| Note(s):; - The Charging Station SHALL NOT send an AuthorizeRequest AND/OR a TransactionEventRequest message after receiving an idToken that is different, than the one used to start the transaction.; - The OCTT waits <Configured message timeout> seconds, before ending the testcase. |
Tool validations
N/a
Post scenario validations
- N/a