TC_015_CS — Hard Reset With Transaction

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

Identification

Field	Value
Test case name	Hard Reset With Transaction
Test case Id	TC_015_CS
System under test	Charge Point

Description

This scenario is used to hard reset a Charge Point, while a transaction is active.

Purpose

To test if the Charge Point will hard reset, after being requested by the Central System.

Prerequisite(s)

Before (Preparations)

Configuration State(s):

Memory State(s):

Reusable State(s):

Charging

Scenario Detail(s)

Charge Point (SUT)	Central System (Tool)
2. The Charge Point responds with a Reset.conf	1. The Central System sends a Reset.req
[Needs to be sent either before or after step 7.]; 3. The Charge Point sends a StopTransaction.req	4. The Central System responds with a StopTransaction.conf
[Needs to be sent if step 3 is sent. Otherwise it is optional.]; 5. The Charge Point sends a StatusNotification.req	6. The Central System responds with a StatusNotification.conf
7. The Charge Point sends a BootNotification.req	8. The Central System responds with a BootNotification.conf
[Send per connector and connectorId=0.]; 9. The Charge Point sends a StatusNotification.req	10. The Central System responds with a StatusNotification.conf

Tool validation(s)

Charge Point side:

Step 2:

(Message: Reset.conf) status is Accepted

Step 3:

(Message: StopTransaction.req) reason is HardReset

Step 5:

(Message: StatusNotification.req) status is Finishing

Step 9:

(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 1:

(Message: Reset.req) The type is Hard

Step 8:

(Message: BootNotification.conf) status is Accepted

Expected result(s) / behaviour

Charge Point side:

Central System side: