TC_001_CS — Cold Boot Charge Point

TC_001_CS — Cold Boot Charge Point

Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 7.

Identification

Field	Value
Test case name	Cold Boot Charge Point
Test case Id	TC_001_CS
System under test	Charge Point

Description

This scenario is used to startup the Charge Point and let it register itself at the Central System.

Purpose

To test if the Charge Point sends the correct messages during the 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)
[Power cycle the Charge Point.]; 1. The Charge Point sends a BootNotification.req	2. The Central System responds with a BootNotification.conf
3. The Charge Point sends a BootNotification.req	4. The Central System responds with a BootNotification.conf
[Send a StatusNotification per connector and connectorId=0.]; 5. The Charge Point sends a StatusNotification.req	6. The Central System responds with a StatusNotification.conf
[Every x seconds.]; 7. The Charge Point sends a Heartbeat.req	8. The Central System responds with a Heartbeat.conf

Tool validation(s)

Charge Point side:

Step 3:

(Message: BootNotification.req) Send BootNotification after interval specified in BootNotification.conf from step 2.

Step 5:

(Message: StatusNotification.req) status is Available

Step 7:

(Message: Heartbeat.req) Send a Heartbeat.req every x seconds. x equals interval from step 4.

Central System side:

Step 2:

(Message: BootNotification.conf) The status is Rejected

Step 4:

(Message: BootNotification.conf) The status is Accepted The interval is <Configured Heartbeat interval>

Expected result(s) / behaviour

Charge Point side:

• N/a

Central System side:

• N/a