TC_047_CSMS — Reservation of a Connector - Expire

TC_047_CSMS — Reservation of a Connector - Expire

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

Identification

Field	Value
Test case name	Reservation of a Connector - Expire
Test case Id	TC_047_CSMS
System under test	Central System

Description

A Connector is reserved, a charging transaction could take place, but the reservation is not used (in time)

Purpose

Check whether Central System can handle messages when the reservation is not used (in time).

Prerequisite(s)

The Central System supports the Reservation feature profile.

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 ReserveNow.conf	1. The Central System sends a ReserveNow.req
3 The Charge Point sends a StatusNotification.req	4. The Central System responds with a StatusNotification.conf
[EV driver does not arrive at the reserved Connector before the expiry date]; 5. The Charge Point sends a StatusNotification.req	6. The Central System responds with a StatusNotification.conf

Tool validation(s)

Charge Point side:

Step 2:

(Message: ReserveNow.conf)

• The status is Accepted

Step 3:

(Message: StatusNotification.req)

• The status is Reserved

Step 5:

(Message: StatusNotification.req)

• The status is Available

Central System side:

Step 1:

(Message: ReserveNow.req)

• The connectorId should be <Configured ConnectorId>
• The idTag should be <Configured Valid IdTag>
• The expiryDate should be the current time plus <Configured Expiry Date Offset>

Expected result(s) / behaviour

Charge Point side:

• N/a

Central System side:

• N/a