TC_011_2_CSMS — Remote Start Charging Session – Time Out

TC_011_2_CSMS — Remote Start Charging Session – Time Out

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

Identification

Field	Value
Test case name	Remote Start Charging Session – Time Out
Test case Id	TC_011_2_CSMS
System under test	Central System

Description

This scenario is used to set a connector back to available, after receiving a RemoteStartTransaction.req and it takes to long to plugin the cable.

Purpose

To test if the Central System can handle when a Charge Point sets the connector back to available, after reaching the configured connection timeout.

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)
2. The Charge Point responds with a RemoteStartTransaction.conf	1. The Central System sends a RemoteStartTransaction.req
3. The Charge Point sends an Authorize.req	4. The Central System responds with an Authorize.conf
5. The Charge Point sends a StatusNotification.req	6. The Central System responds with a StatusNotification.conf
[After the configured connection timeout has been reached.]; 7. The Charge Point sends a StatusNotification.req	8. The Central System responds with a StatusNotification.conf

Tool validation(s)

Charge Point side:

Step 2:

(Message: RemoteStartTransaction.conf) status is Accepted

Step 5:

(Message: StatusNotification.req) status is Preparing

Step 7:

(Message: StatusNotification.req) status is Available

Central System side:

Step 4:

(Message: Authorize.conf) idTagInfo.status is Accepted

Expected result(s) / behaviour

Charge Point side:

• N/a

Central System side:

• N/a