TC_E_21_CS — Stop transaction options - StopAuthorized - Remote
TC_E_21_CS — Stop transaction options - StopAuthorized - Remote
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block E. Transactions, page 149.
Identification
| Field | Value |
|---|---|
| Test case name | Stop transaction options - StopAuthorized - Remote |
| Test case Id | TC_E_21_CS |
| Use case Id(s) | E06(S3) AND F03 |
| Requirement(s) | E06.FR.03, E06.FR.15 AND F03.FR.09 |
| System under test | Charging Station |
| 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 stop options.
Purpose
To verify if the Charging Station stops a transaction when it receives a RequestStopTransactionRequest and it has been configured to do so.
Prerequisite(s)
- The Charging Station does NOT have the following configuration; The mutability of TxStopPoint is ReadOnly AND the value Authorized is NOT set OR PowerPathClosed is set.
- If the mutability of TxStopPoint is ReadWrite, then the value Authorized must be supported.
Before (Preparations)
Configuration State:
- TxStopPoint contains Authorized
Memory State:
- N/a
Reusable State(s):
- State is EnergyTransferStarted
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 2. The Charging Station responds with a RequestStopTransactionResponse | 1. The OCTT sends a RequestStopTransactionRequest; with transactionId <transactionId provided by the Charging Station in TransactionEventRequest> |
| 3. The Charging Station sends a TransactionEventRequest | 4. The OCTT responds with a TransactionEventResponse |
Tool validations
Step 2:
Message: RequestStopTransactionResponse
- status must be Accepted
Step 3:
Message: TransactionEventRequest
- triggerReason must be RemoteStop
- transactionInfo.stoppedReason must be Remote
- eventType must be Ended
Post scenario validations
- N/a