Skip to content
Documentation Menu

TC_E_22_CS — Stop transaction options - EnergyTransfer stopped - SuspendedEV

TC_E_22_CS — Stop transaction options - EnergyTransfer stopped - SuspendedEV

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

Identification

FieldValue
Test case nameStop transaction options - EnergyTransfer stopped - SuspendedEV
Test case IdTC_E_22_CS
Use case Id(s)E06(S6)
Requirement(s)E06.FR.07, 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 the energy transfer stopped by the EV and the Charging Station 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 EnergyTransfer is NOT set.
  • If the mutability of TxStopPoint is ReadWrite, then the value EnergyTransfer must be supported.

Before (Preparations)

Configuration State:

  • TxStopPoint contains EnergyTransfer

Memory State:

  • N/a

Reusable State(s):

  • State is EnergyTransferStarted

Main (Test scenario)

Charging StationCSMS
Manual Action: The EV suspends the energy transfer.
1. The Charging Station sends a TransactionEventRequest2. The OCTT responds with a TransactionEventResponse

Tool validations

Step 1:

Message: TransactionEventRequest

  • triggerReason must be ChargingStateChanged
  • transactionInfo.chargingState must be EVConnected + OR
  • transactionInfo.chargingState must be SuspendedEV AND
  • transactionInfo.stoppedReason must be StoppedByEV
  • eventType must be Ended (if chargingState is EVConnected) OR
  • eventType must be Updated (if chargingState is SuspendedEV)

Post scenario validations

  • N/a