TC_004_2_CS — Regular Charging Session – Identification First - ConnectionTimeOut

TC_004_2_CS — Regular Charging Session – Identification First - ConnectionTimeOut

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

Identification

Field	Value
Test case name	Regular Charging Session – Identification First - ConnectionTimeOut
Test case Id	TC_004_2_CS
System under test	Charge Point

Description

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

Purpose

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

Prerequisite(s)

• N/a

Before (Preparations)

Configuration State(s):

• Value for "ConnectionTimeOut" is <Configured connectionTimeout>.

Memory State(s):

• N/a

Reusable State(s):

• N/a

Scenario Detail(s)

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

Tool validation(s)

Charge Point side:

Step 2:

(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