TC_E_31_CS — Check Transaction status - Transaction with id ended - with message in queue
TC_E_31_CS — Check Transaction status - Transaction with id ended - with message in queue
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block E. Transactions, page 160.
Identification
| Field | Value |
|---|---|
| Test case name | Check Transaction status - Transaction with id ended - with message in queue |
| Test case Id | TC_E_31_CS |
| Use case Id(s) | E14 |
| Requirement(s) | E14.FR.03,E14.FR.04 |
| System under test | Charging Station |
| Functional block | E. Transactions |
Description
The CSMS is able to request the status of a transaction and to find out whether there are queued transaction-related messages, using the GetTransactionStatusRequest message.
Purpose
To verify if the Charging Station is able to correctly respond to a GetTransactionStatusRequest with a transactionId, while there is a message queued belonging to an ended transaction with the requested id.
Prerequisite(s)
The Charging Station supports at least one authorization method described at the following Use cases; C01, C02, C04.
Before (Preparations)
Configuration State:
- OfflineThreshold is <Configured RetryBackOffWaitMinimum_duration> + 60.0 RetryBackOffWaitMinimum is <Configured RetryBackOffWaitMinimum_duration> RetryBackOffRandomRange is 0
- Note: <Configured RetryBackOffWaitMinimum_duration> should be long enough to execute manual tasks after waiting for <Configured Transaction Duration> seconds
Memory State:
- N/a
Reusable State(s):
- State is EnergyTransferStarted
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| The OCTT closes the WebSocket connection AND does not accept a reconnect. | |
| Manual Action: Present the same idToken as used to start the transaction. | |
| Manual Action: Disconnect the EV and EVSE. | |
| Manual Action: Drive EV out of parking bay. (Only needed if TxStopPoint is ParkingBayOccupancy) | |
| Notes(s): The tool will wait for <Configured Transaction Duration> seconds | |
| The OCTT accepts reconnection attempt from the Charging Station. | |
| 2. The Charging Station responds with a GetTransactionStatusResponse | 1. The OCTT sends a GetTransactionStatusRequest; with transactionId <Generated transactionId from Before>; Note: This step will be executed the moment the WebSocket connection is restored. |
| 3. The Charging Stations sends a TransactionEventRequest; Note(s):; - The Charging Station will empty its Transaction message queue. This will contain all TransactionEventRequest messages from the Transaction. | 4. The OCTT responds with a TransactionEventResponse |
Tool validations
Step 2:
Message: GetTransactionStatusResponse
- ongoingIndicator must be false
- messagesInQueue must be true
Step 3:
Message: TransactionEventRequest The tool validations from the reusable states need to be used to verify whether all required TransactionEventRequests have been received. From StopAuthorized through ParkingBayUnoccupied
Post scenario validations
- N/a