TC_032_1_CSMS — Power failure boot charging point-configured to stop transaction(s)

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

Identification

Field	Value
Test case name	Power failure boot charging point-configured to stop transaction(s)
Test case Id	TC_032_1_CSMS
System under test	Central System

Description

This scenario is used to stop all transactions, when a power failure occurred.

Purpose

To test if the Central System can handle when a Charge Point stops all transactions, when a power failure occurred.

Prerequisite(s)

Before (Preparations)

Configuration State(s):

Memory State(s):

Reusable State(s):

Charging

Scenario Detail(s)

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

Tool validation(s)

Charge Point side:

Step 3:

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

Step 5:

(Message: StopTransaction.req) reason is PowerLoss

Central System side:

Step 2:

(Message: BootNotification.req) status is Accepted

Expected result(s) / behaviour

Charge Point side:

Central System side: