TC_E_16_CSMS — Stop transaction options - Deauthorized - Invalid idToken
TC_E_16_CSMS — Stop transaction options - Deauthorized - Invalid idToken
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block E. Transactions, page 395.
Identification
| Field | Value |
|---|---|
| Test case name | Stop transaction options - Deauthorized - Invalid idToken |
| Test case Id | TC_E_16_CSMS |
| Use case Id(s) | E06(S3) |
| Requirement(s) | E06.FR.04,E01.FR.11,E01.FR.12 |
| System under test | CSMS |
| Functional block | E. Transactions |
Description
OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points to be configured differently. This test covers one of the start options.
Purpose
To verify if the CSMS is able to handle a Charging Station that stops a transaction when the transaction gets deauthorized by the status from the idTokenInfo at a TransactionEventResponse message and it has been configured to do so.
Prerequisite(s)
N/a
Before (Preparations)
Configuration State:
- N/a
Memory State:
- N/a
Reusable State(s):
- N/a
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 1. The OCTT sends a TransactionEventRequest; With triggerReason is Authorized idToken.idToken <Configured invalid_idtoken_idtoken> idToken.type <Configured invalid_idtoken_type> eventType is Started | 2. The CSMS responds with a TransactionEventResponse |
| 3. The OCTT sends a TransactionEventRequest; With eventType Ended triggerReason Deauthorized transactionInfo.stoppedReason DeAuthorized | 4. The CSMS responds with a TransactionEventResponse |
Tool validations
Step 2:
Message: TransactionEventResponse
- idTokenInfo.status must be Invalid or Unknown+
Post scenario validations
- N/a