TC_E_14_CS — Stop transaction options - EVDisconnected - Charging Station side
TC_E_14_CS — Stop transaction options - EVDisconnected - Charging Station side
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block E. Transactions, page 145.
Identification
| Field | Value |
|---|---|
| Test case name | Stop transaction options - EVDisconnected - Charging Station side |
| Test case Id | TC_E_14_CS |
| Use case Id(s) | E06(S2) |
| Requirement(s) | E06.FR.02, E06.FR.15 |
| 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 stop options.
Purpose
To verify if the Charging Station stops a transaction when the EV and EVSE are disconnected at the Charging Station side 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 EVConnected is NOT set OR (EnergyTransfer OR PowerPathClosed OR DataSigned OR Authorized is set)).
- If the mutability of TxStopPoint is ReadWrite, then the value EVConnected must be supported.
Before (Preparations)
Configuration State:
- TxStopPoint contains EVConnected
Memory State:
- N/a
Reusable State(s):
- State is EVConnectedPostSession
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| Manual Action: Disconnect the EV and EVSE. | |
| 1. The Charging Station notifies the CSMS about the status change of the connector. | 2. The OCTT responds accordingly. |
| 3. The Charging Station sends a TransactionEventRequest | 4. The OCTT responds with a TransactionEventResponse |
Tool validations
Step 1:
Message: StatusNotificationRequest
- connectorStatus must be Available Message: NotifyEventRequest
- eventData[0].trigger must be Delta
- eventData[0].actualValue must be Available
- eventData[0].component.name must be Connector
- eventData[0].variable.name must be AvailabilityState
Step 3:
Message: TransactionEventRequest
- triggerReason must be EVCommunicationLost
- transactionInfo.chargingState must be Idle
- If the OCTT is configured to stop transactions using a RequestStopTransactionRequest message then transactionInfo.stoppedReason must be Remote Else transactionInfo.stoppedReason must be Local or EVDisconnected
- eventType must be Ended
Post scenario validations
- N/a