TC_004_2_CSMS — Regular Charging Session – Identification First - ConnectionTimeOut

TC_004_2_CSMS — Regular Charging Session – Identification First - ConnectionTimeOut

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

Identification

Field	Value
Test case name	Regular Charging Session – Identification First - ConnectionTimeOut
Test case Id	TC_004_2_CSMS
System under test	Central System

Description

This scenario is used to make a connector available when it is not used.

Purpose

To test if the Central System can handle when the Charge Point sets the connector back to Available, when the connectionTimeOut is reached.

Prerequisite(s)

• N/a

Before (Preparations)

Configuration State(s):

• N/a

Memory State(s):

• N/a

Reusable State(s):

• Authorized

Scenario Detail(s)

Charge Point (SUT)	Central System (Tool)
1. The Charge Point sends a StatusNotification.req	2. The Central System responds with a StatusNotification.conf
[After the configured connectionTimeOut has expired.]; 3. The Charge Point sends a StatusNotification.req	4. The Central System responds with a StatusNotification.conf

Tool validation(s)

Charge Point side:

Step 1:

(Message: StatusNotification.req) status is Preparing

Step 3:

(Message: StatusNotification.req) status is Available

Central System side:

• N/a

Expected result(s) / behaviour

Charge Point side:

• N/a

Central System side:

• N/a