Skip to content
Documentation Menu

TC_E_19_CS — Stop transaction options - ParkingBayUnoccupied

TC_E_19_CS — Stop transaction options - ParkingBayUnoccupied

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

Identification

FieldValue
Test case nameStop transaction options - ParkingBayUnoccupied
Test case IdTC_E_19_CS
Use case Id(s)E06(S1)
Requirement(s)E06.FR.01, 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 EV left the parking bay and it 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 ParkingBayOccupied is NOT set OR (EnergyTransfer OR PowerPathClosed OR DataSigned OR Authorized OR EVConnected is set)).
  • If the mutability of TxStopPoint is ReadWrite, then the value ParkingBayOccupied must be supported.

Before (Preparations)

Configuration State:

  • TxStopPoint contains ParkingBayOccupied

Memory State:

  • N/a

Reusable State(s):

  • State is EVDisconnected

Main (Test scenario)

Charging StationCSMS
Manual Action: Drive EV out of parking bay.
1. The Charging Station sends a TransactionEventRequest2. The OCTT responds with a TransactionEventResponse

Tool validations

Step 1:

Message: TransactionEventRequest

  • triggerReason must be EVDeparted
  • If the OCTT is configured to stop transactions using a RequestStopTransactionRequest message then transactionInfo.stoppedReason must be Remote Else transactionInfo.stoppedReason must be Local
  • eventType must be Ended

Post scenario validations

  • N/a