TC_E_27_CS — Disconnect cable on EV-side - Suspend transaction - Fixed cable connection timeout
TC_E_27_CS — Disconnect cable on EV-side - Suspend transaction - Fixed cable connection timeout
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block E. Transactions, page 155.
Identification
| Field | Value |
|---|---|
| Test case name | Disconnect cable on EV-side - Suspend transaction - Fixed cable connection timeout |
| Test case Id | TC_E_27_CS |
| Use case Id(s) | E10 |
| Requirement(s) | E10.FR.02, E10.FR.03 |
| 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 suspends the transaction when the EV and EVSE are disconnected at the EV side and it has been configured to do so AND deauthorizes the transaction after the configured connection timeout expires.
Prerequisite(s)
- The Charging Station does NOT have the following configuration; The mutability of TxStopPoint is ReadOnly AND (the value Authorized OR ParkingBayOccupancy is NOT set OR (EnergyTransfer OR PowerPathClosed OR DataSigned OR EVConnected is set)).
- If the mutability of TxStopPoint is _ReadWrite, then the value Authorized OR ParkingBayOccupancy must be supported.
- The Charging Station has a permanently attached cable at the Charging Station side.
Before (Preparations)
Configuration State:
- TxStopPoint contains Authorized (If supported) TxStopPoint contains ParkingBayOccupancy (If supported) UnlockOnEVSideDisconnect is false StopTxOnEVSideDisconnect 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 |
| 3. The Charging Station notifies the CSMS about the current state of the connector.; Note(s):; - This step needs to be executed when the Charging Station has a permanently attached cable on the Charging Station side. | 4. The OCTT responds accordingly. |
| Manual Action: Reconnect the EV and EVSE on EV side.; Note(s):; - If the Charging Station has a permanently attached cable on the Charging Station side, then this step needs to be executed before the configured EVConnectionTimeout expires. | |
| 5. The Charging Station sends a TransactionEventRequest | 6. The OCTT responds with a TransactionEventResponse |
| Note(s): Optionally the Charging Station can send a StatusNotificationRequest or NotifyEventRequest with status Available |
Tool validations
Step 1:
Message: TransactionEventRequest
- triggerReason must be EVCommunicationLost
- transactionInfo.chargingState must be Idle
- eventType must be Updated
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"
Step 5:
Message: TransactionEventRequest
- triggerReason must be EVConnectTimeout If <Configured TxCtrlr.TxStopPoint> contains Authorized then eventType must be Ended transactionInfo.stoppedReason must be Timeout else if <Configured TxCtrlr.TxStopPoint> contains ParkingBayOccupancy then eventType must be Updated
Post scenario validations
- N/a