TC_B_41_CS — Reset Charging Station - With multiple ongoing transactions - OnIdle
TC_B_41_CS — Reset Charging Station - With multiple ongoing transactions - OnIdle
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block B. Provisioning, page 58.
Identification
| Field | Value |
|---|---|
| Test case name | Reset Charging Station - With multiple ongoing transactions - OnIdle |
| Test case Id | TC_B_41_CS |
| Use case Id(s) | B12 |
| Requirement(s) | B12.FR.01, B12.FR.03, E07.FR.03 |
| System under test | Charging Station |
| Functional block | B. Provisioning |
Description
This test case covers how the CSMS can remotely request the Charging Station to reset itself by sending a ResetRequest during a transaction. When ResetRequest "OnIdle" is send the charging stations schedules a reboot after all transactions are stopped. This could for example be necessary if the Charging Station is not functioning correctly.
Purpose
To verify if the Charging Station is able to perform the reset mechanism while there are multiple ongoing transactions as described at the OCPP specification.
Prerequisite(s)
The Charging Station has more than one EVSE.
Before (Preparations)
Configuration State:
- N/a
Memory State:
- N/a
Reusable State(s):
- State is EnergyTransferStarted for EVSE.id = 1 State is EnergyTransferStarted for EVSE.id = 2
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 2. The Charging Station responds with a ResetResponse | 1. The OCTT sends a ResetRequest; with type OnIdle |
| 3. Execute Reusable State StopAuthorized for EVSE.id = 1 | |
| 4. Execute Reusable State EVConnectedPostSession for EVSE.id = 1 | |
| 5. Execute Reusable State EVDisconnected for EVSE.id = 1 | |
| 6. Execute Reusable State ParkingBayUnoccupied for EVSE.id = 1 | |
| 7. Execute Reusable State StopAuthorized for EVSE.id = 2 | |
| 8. Execute Reusable State EVConnectedPostSession for EVSE.id = 2; Note(s): If TxStopPoint contains one of the following values; Authorized, EnergyTransfer, PowerPathClosed, DataSigned. Then the transaction will have ended at the EVConnectedPostSession state AND the Charging Station will proceed with resetting itself. Proceed to step 10 Else proceed with step 9. | |
| 9. Execute Reusable State EVDisconnected for EVSE.id = 2; Note(s): If TxStopPoint contains the value EVConnected. Then the transaction will have ended at the EVDisconnected state AND the Charging Station will proceed; with resetting itself. Proceed to step 11 Else proceed with step 10 | |
| 10. Execute Reusable State ParkingBayUnoccupied for EVSE.id = 2; Note(s): The transaction will end at this state, if it was not ended at an earlier state. Proceed to step 11. | |
| 11. The Charging Station sends a BootNotificationRequest | 12. The OCTT responds with a BootNotificationResponse |
| 13. The Charging Station notifies the CSMS about the current state of all connectors. | 14. The OCTT responds accordingly. |
Tool validations
Step 2:
Message ResetResponse
- status Scheduled
Step 11:
Message BootNotificationRequest
- reason ScheduledReset
Step 13:
Message: StatusNotificationRequest
- If the transaction was stopped at step 3, then connectorStatus Occupied Else connectorStatus Available Message: NotifyEventRequest
- If the transaction was stopped at step 3, then eventData[0].actualValue "Occupied" Else eventData[0].actualValue "Available"
- eventData[0].trigger Delta
- eventData[0].component.name "Connector"
- eventData[0].variable.name "AvailabilityState"
Post scenario validations
- A message to report the state of a connector has been received for all connectors.