TC_B_57_CS — Network Reconnection - After connection loss
TC_B_57_CS — Network Reconnection - After connection loss
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block B. Provisioning, page 83.
Identification
| Field | Value |
|---|---|
| Test case name | Network Reconnection - After connection loss |
| Test case Id | TC_B_57_CS |
| Use case Id(s) | Part 4 section 5.3. Reconnecting |
| Requirement(s) | Described at section 5.3. |
| System under test | Charging Station |
| Functional block | B. Provisioning |
Description
When the connection is lost, the Charging Station SHALL try to reconnect. When reconnecting, the Charging Station SHALL use an increasing back-off time until it has successfully reconnected.
Purpose
To verify if the Charging Station is able to reconnect to the CSMS using the described OCPP reconnecting mechanism from part 4.
Prerequisite(s)
N/a
Before (Preparations)
Configuration State:
- OCPPCommCtrlr.RetryBackOffRepeatTimes is 2 OCPPCommCtrlr.RetryBackOffRandomRange is 0 OCPPCommCtrlr.RetryBackOffWaitMinimum is <Configured RetryBackOffWaitMinimum>
Memory State:
- N/a
Reusable State(s):
- N/a
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 1. The OCTT closes the websocket connection. | |
| 2. The Charging Station waits for the duration of the configured RetryBackOffWaitMinimum and reconnects to the OCTT. | 3. The connection attempt is accepted by the OCTT. |
| 4. The OCTT closes the websocket connection. | |
| 5. The Charging Station waits for the duration of the configured RetryBackOffWaitMinimum and reconnects to the OCTT. | 6. The connection attempt is not accepted by the OCTT. |
| 7. The Charging Station waits for the duration of the at step 3 doubled RetryBackOffWaitMinimum and reconnects to the OCTT. | 8. The connection attempt is accepted by the OCTT. |
Tool validations
Step 2:
- The reconnection time is at least the configured RetryBackOffWaitMinimum.
Step 7:
- The reconnection time is at least 3 times the reconnection time from step 2.
Post scenario validations
- N/a