Skip to content
Documentation Menu

TC_048_3_CSMS — Reservation of a Connector - Unavailable

TC_048_3_CSMS — Reservation of a Connector - Unavailable

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

Identification

FieldValue
Test case nameReservation of a Connector - Unavailable
Test case IdTC_048_3_CSMS
System under testCentral System

Description

The Central System attempts to reserve a Connector, but the reservation is not made, instead the status Unavailable is returned by the Charge Point.

Purpose

Check whether the Central System can handle messages in case that a reservation cannot be made.

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 ChangeAvailability.conf1. The Central System sends a ChangeAvailability.req
3. The Charge Point sends a StatusNotification.req4. The Central System responds with a StatusNotification.conf
6. The Charge Point responds with a ReserveNow.conf5. The Central System sends a ReserveNow.req

Tool validation(s)

Charge Point side:

Step 3:

(Message: StatusNotification.req)

  • The Status is Unavailable
  • The connectorId equals the connectorId from step 1.

Step 6:

(Message: ReserveNow.conf)

  • The status is Unavailable

Central System side:

Step 1:

(Message: ChangeAvailability.req)

  • The connectorId should be <Configured ConnectorId>
  • The type is Inoperative

Step 5:

(Message: ReserveNow.req)

  • The connectorId should be the connectorId from step 1.
  • The idTag should be <Configured Valid IdTag>

Expected result(s) / behaviour

Charge Point side:

  • N/a

Central System side:

The Central System accepts the Reservation message with the not Accepted status.