TC_E_12_CS — Start transaction options - ParkingBayOccupied
TC_E_12_CS — Start transaction options - ParkingBayOccupied
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block E. Transactions, page 129.
Identification
| Field | Value |
|---|---|
| Test case name | Start transaction options - ParkingBayOccupied |
| Test case Id | TC_E_12_CS |
| Use case Id(s) | E01(S1) |
| Requirement(s) | E01.FR.01, E01.FR.07, E01.FR.10, E01.FR.15, E01.FR.16 |
| System under test | Charging Station |
| Functional block | E. 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 start options.
Purpose
To verify if the Charging Station starts a transaction when the EV and EVSE are connected and it has been configured to do so.
Prerequisite(s)
- The Charging Station does NOT have the following configuration; The mutability of TxStartPoint is ReadOnly AND the value ParkingBayOccupancy is NOT set.
- If the mutability of TxStartPoint is ReadWrite, then the value ParkingBayOccupancy must be supported.
Before (Preparations)
Configuration State:
- If the mutability of TxStartPoint is ReadWrite then TxStartPoint contains ParkingBayOccupancy
Memory State:
- N/a
Reusable State(s):
- N/a
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| Manual Action: Drive EV into parking bay. | |
| 1. The Charging Station sends a TransactionEventRequest | 2. The OCTT responds with a TransactionEventResponse |
Tool validations
Step 1:
Message: TransactionEventRequest
- eventType must be Started
- triggerReason must be EVDetected
Post scenario validations
- N/a