Skip to content
Documentation Menu

TC_E_35_CS — Stop transaction options - PowerPathClosed - Remote stop

TC_E_35_CS — Stop transaction options - PowerPathClosed - Remote stop

Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block E. Transactions, page 141.

Identification

FieldValue
Test case nameStop transaction options - PowerPathClosed - Remote stop
Test case IdTC_E_35_CS
Use case Id(s)E06(S5)
Requirement(s)E06.FR.06, E06.FR.15
System under testCharging Station
Functional blockE. 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 is remotely stopped the CSMS and TxStopPoint contains PowerPathClosed.

Prerequisite(s)

  • The Charging Station does NOT have the following configuration; The mutability of TxStopPoint is ReadOnly AND (the value PowerPathClosed is NOT set OR Authorized is set).
  • If the mutability of TxStopPoint is ReadWrite, then the value PowerPathClosed must be supported.

Before (Preparations)

Configuration State:

  • TxStopPoint contains PowerPathClosed

Memory State:

  • N/a

Reusable State(s):

  • State is EnergyTransferStarted

Main (Test scenario)

Charging StationCSMS
2. The Charging Station responds with a RequestStopTransactionResponse1. The OCTT sends a RequestStopTransactionRequest; with transactionId <transactionId provided by the Charging Station in TransactionEventRequest>
3. The Charging Station sends a TransactionEventRequest4. 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