TC_E_31_CSMS — Check Transaction status - Transaction with id ended - with message in queue
TC_E_31_CSMS — 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 402.
Identification
| Field | Value |
|---|---|
| Test case name | Check Transaction status - Transaction with id ended - with message in queue |
| Test case Id | TC_E_31_CSMS |
| Use case Id(s) | E14 |
| Requirement(s) | E14.FR.03,E14.FR.04 |
| System under test | CSMS |
| 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 CSMS is able to request the status of queued TransactionEventRequest messages from a specific transaction by sending a GetTransactionStatusRequest with a transactionId. The OCTT will respond that there are message(s) queued belonging to an ended transaction with the requested id.
Prerequisite(s)
N/a
Before (Preparations)
Configuration State:
- N/a
Memory State:
- N/a
Reusable State(s):
- State is EnergyTransferStarted
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 1. The OCTT closes the WebSocket connection. | |
| 2. The OCTT waits a number of seconds equal to <Configured Transaction duration>, then it will reconnect to the CSMS. | |
| 3. The OCTT sends a TransactionEventRequest; With eventType is Ended offline is true triggerReason is EVCommunicationLost transactionInfo.chargingState is Idle seqNo <Skips two sequence number values> | 4. The CSMS responds with a TransactionEventResponse |
| 6. The OCTT responds with a GetTransactionStatusResponse With ongoingIndicator is false messagesInQueue is true | 5. The CSMS sends a GetTransactionStatusRequest |
| 7. The OCTT sends a TransactionEventRequest; With triggerReason is StopAuthorized eventType is Updated offline is true seqNo <This is the first of the two skipped values> | 8. The CSMS responds with a TransactionEventResponse |
| 9. The OCTT sends a TransactionEventRequest; With triggerReason is ChargingStateChanged transactionInfo.chargingState is EVConnected eventType is Updated offline is true seqNo <This is the second of the two skipped values> | 10. The CSMS responds with a TransactionEventResponse |
Tool validations
Step 5:
Message: GetTransactionStatusRequest
- transactionId <Generated transactionId from Before>
Post scenario validations
- N/a