TC_E_33_CSMS — Check Transaction status - Without transactionId - 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 403.

Identification

Field	Value
Test case name	Check Transaction status - Without transactionId - with message in queue
Test case Id	TC_E_33_CSMS
Use case Id(s)	E14
Requirement(s)	E14.FR.06,E14.FR.07
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 by sending a GetTransactionStatusRequest without a transactionId. The OCTT will respond that there are message(s) queued.

Prerequisite(s)

N/a

Before (Preparations)

Configuration State:

Memory State:

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.
4. The OCTT responds with a GetTransactionStatusResponse With ongoingIndicator is omitted. messagesInQueue is true	3. The CSMS sends a GetTransactionStatusRequest
5. The OCTT sends a TransactionEventRequest; With eventType is Updated meterValues is present. offline is true	6. The CSMS responds with a TransactionEventResponse

Tool validations

Step 3:

Message: GetTransactionStatusRequest

transactionId must be omitted.

TC_E_33_CSMS — Check Transaction status - Without transactionId - with message in queue