TC_E_25_CS — Disconnect cable on EV-side - Deauthorize transaction - UnlockOnEVSideDisconnect is false
TC_E_25_CS — Disconnect cable on EV-side - Deauthorize transaction - UnlockOnEVSideDisconnect is false
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block E. Transactions, page 152.
Identification
| Field | Value |
|---|---|
| Test case name | Disconnect cable on EV-side - Deauthorize transaction - UnlockOnEVSideDisconnect is false |
| Test case Id | TC_E_25_CS |
| Use case Id(s) | E09 |
| Requirement(s) | E09.FR.01, E09.FR.03, E09.FR.04 |
| System under test | Charging Station |
| Functional block | E. Transactions |
Description
The Charging Station can behave in several different ways when the cable is disconnected at the EV side, based on its configuration. This test case tests one of the possible configuration settings.
Purpose
To verify if the Charging Station deauthorizes the transaction when the EV and EVSE are disconnected at the EV side and it has been configured to do so AND keeps the cable locked at Charging Station side.
Prerequisite(s)
N/a
Before (Preparations)
Configuration State:
- StopTxOnEVSideDisconnect is true UnlockOnEVSideDisconnect is false
Memory State:
- N/a
Reusable State(s):
- State is EnergyTransferSuspended
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| Manual Action: Disconnect the EV and EVSE on EV side (EVSE loses connection with EV). | |
| 1. The Charging Station sends a TransactionEventRequest | 2. The OCTT responds with a TransactionEventResponse |
| Manual Action: Present the IdToken that was used to start the transaction.; Note(s):; - This manual action needs to be executed when the Charging Station has a detachable cable on the Charging Station side. | |
| Manual Action: Disconnect the EV and EVSE on Charging Station side.; Note(s):; - This manual action needs to be executed when the Charging Station has a detachable cable on the Charging Station side. | |
| 3. The Charging Station notifies the CSMS about the current state of the connector. | 4. The OCTT responds accordingly. |
Tool validations
Step 1:
Message: TransactionEventRequest
- triggerReason must be EVCommunicationLost
- transactionInfo.chargingState must be Idle
Step 3:
Message: StatusNotificationRequest
- connectorStatus Available Message: NotifyEventRequest
- eventData[0].trigger Delta
- eventData[0].actualValue "Available"
- eventData[0].component.name "Connector"
- eventData[0].variable.name "AvailabilityState"
Post scenario validations
- N/a