TC_001_CSMS — Cold Boot Charge Point
TC_001_CSMS — Cold Boot Charge Point
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Central System, page 123.
Identification
| Field | Value |
|---|---|
| Test case name | Cold Boot Charge Point |
| Test case Id | TC_001_CSMS |
| System under test | Central System |
Description
This scenario is used to startup the Charge Point and let it register itself at the Central System.
Purpose
To test if the Central System is able to handle a boot process.
Prerequisite(s)
- N/a
Before (Preparations)
Configuration State(s):
- N/a
Memory State(s):
- N/a
Reusable State(s):
- N/a
Scenario Detail(s)
| Charge Point (SUT) | Central System (Tool) |
|---|---|
| 1. The Charge Point sends a BootNotification.req | 2. The Central System responds with a BootNotification.conf |
| [Send a StatusNotification per connector and connectorId=0.]; 3. The Charge Point sends a StatusNotification.req | 4. The Central System responds with a StatusNotification.conf |
| [Every x seconds.]; 5. The Charge Point sends a Heartbeat.req | 6. The Central System responds with a Heartbeat.conf |
Tool validation(s)
Charge Point side:
Step 1:
(Message: BootNotification.req)
Step 3:
(Message: StatusNotification.req) status is Available
Step 5:
(Message: Heartbeat.req) Send a Heartbeat.req every x seconds. x equals interval from step 2.
Central System side:
Step 2:
(Message: BootNotification.conf) The status is Accepted
Expected result(s) / behaviour
Charge Point side:
- N/a
Central System side:
- N/a