Skip to content
Documentation Menu

TC_048_2_CS — Reservation of a Connector - Occupied

TC_048_2_CS — Reservation of a Connector - Occupied

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

Identification

FieldValue
Test case nameReservation of a Connector - Occupied
Test case IdTC_048_2_CS
System under testCharge Point

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 Charge Point is able to exchange messages in case that a reservation cannot be made.

Prerequisite(s)

The Charge Point supports the Reservation feature profile.

Before (Preparations)

Configuration State(s):

  • N/a

Memory State(s):

  • N/a

Reusable State(s):

  • SetConnectorOccupied

Scenario Detail(s)

Charge Point (SUT)Central System (Tool)
2. The Charge Point responds with a ReserveNow.conf1. The Central System sends a ReserveNow.req

Tool validation(s)

Charge Point side:

Step 2:

(Message: ReserveNow.conf)

  • status should be Occupied

Central System side:

Step 1:

(Message: ReserveNow.req)

  • connectorId is <Configured ConnectorId>

Expected result(s) / behaviour

Charge Point side:

The Charge Point continues normal operation.

Central System side:

  • N/a