TC_032_1_CS — Power failure boot charging point - configured to stop transaction(s) before going down

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

Identification

Field	Value
Test case name	Power failure boot charging point - configured to stop transaction(s) before going down
Test case Id	TC_032_1_CS
System under test	Charge Point

Description

This scenario is used to stop all transactions before going down, when a power failure occurs.

Purpose

To test if the Charge Point first stops all transactions before going down, when a power failure occurs.

Prerequisite(s)

The Charge Point has a back-up power source and thereby is configured to stop transactions before going down.

Before (Preparations)

Configuration State(s):

Memory State(s):

Reusable State(s):

Charging

Scenario Detail(s)

Charge Point (SUT)	Central System (Tool)
[Disconnect the power of the Charge Point.]; 1. The Charge Point sends a StopTransaction.req	2. The Central System responds with a StopTransaction.conf
3. The Charge Point sends a StatusNotification.req	4. The Central System responds with a StatusNotification.conf
[Reconnect the power of the Charge Point.]; 5. The Charge Point sends a BootNotification.req	6. The Central System responds with a BootNotification.conf
[Send per connector and connectorId = 0.]; 7. The Charge Point sends a StatusNotification.req	8. The Central System responds with a StatusNotification.conf

Tool validation(s)

Charge Point side:

Step 1:

(Message: StopTransaction.req) reason is PowerLoss

Step 3:

(Message: StatusNotification.req) status is Finishing

Step 7:

(Message: StatusNotification.req) connectorId is <The connector which had the ongoing transaction> status is Finishing OR Preparing (Message: StatusNotification.req) The other StatusNotification messages. status is Available

Central System side:

Step 6:

(Message: BootNotification.conf) status is Accepted

Expected result(s) / behaviour

Charge Point side:

Central System side: