TC_E_26_CSMS — Disconnect cable on EV-side - Suspend transaction
TC_E_26_CSMS — Disconnect cable on EV-side - Suspend transaction
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block E. Transactions, page 399.
Identification
| Field | Value |
|---|---|
| Test case name | Disconnect cable on EV-side - Suspend transaction |
| Test case Id | TC_E_26_CSMS |
| Use case Id(s) | E10 |
| Requirement(s) | E10.FR.01 |
| System under test | CSMS |
| 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 CSMS can handle a Charging Station that suspends the transaction when the EV and EVSE are disconnected at the EV side AND is able restart the energy transfer after reconnecting the EV and EVSE.
Prerequisite(s)
N/a
Before (Preparations)
Configuration State:
- N/a
Memory State:
- N/a
Reusable State(s):
- State is EnergyTransferSuspended
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 1. The OCTT sends a TransactionEventRequest; With triggerReason is EVCommunicationLost transactionInfo.chargingState is Idle eventType is Updated | 2. The CSMS responds with a TransactionEventResponse |
| 3. The OCTT notifies the CSMS about the current state of the connector.; Message: StatusNotificationRequest; - connectorStatus Available; - evseId <Configured evseId>; - connectorId <Configured connectorId>; Message: NotifyEventRequest; - trigger Delta; - actualValue "Available"; - component.name "Connector"; - component.evse.id <Configured evseId>; - component.evse.connectorid <Configured connectorId>; - variable.name "AvailabilityState" | 4. The CSMS responds accordingly. |
| 5. The OCTT sends a TransactionEventRequest; With triggerReason is CablePluggedIn transactionInfo.chargingState is EVConnected eventType is Updated | 6. The CSMS responds with a TransactionEventResponse |
| 7. The OCTT sends a TransactionEventRequest; With triggerReason is ChargingStateChanged transactionInfo.chargingState is Charging eventType is Updated | 8. The CSMS responds with a TransactionEventResponse |
Tool validations
N/a
Post scenario validations
- N/a