Skip to content
Documentation Menu

TC_048_2_CSMS — Reservation of a Connector - Occupied

TC_048_2_CSMS — Reservation of a Connector - Occupied

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

Identification

FieldValue
Test case nameReservation of a Connector - Occupied
Test case IdTC_048_2_CSMS
System under testCentral System

Description

The Central System attempts to reserve a Connector, but the reservation is not made, instead the status Occupied 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)
[EV driver plugs in cable]; 1. The Charge Point sends a StatusNotification.req2. The Central System responds with a StatusNotification.conf
4. The Charge Point responds with a ReserveNow.conf3. The Central System sends a ReserveNow.req

Tool validation(s)

Charge Point side:

Step 1:

(Message: StatusNotification.req)

  • The status is Preparing
  • The connectorId is <Configured ConnectorId>

Step 4:

(Message: ReserveNow.conf)

  • The status is Occupied

Central System side:

Step 3:

(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.