TC_050_2_CS — Reservation of a Charge Point - Occupied
TC_050_2_CS — Reservation of a Charge Point - Occupied
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 74.
Identification
| Field | Value |
|---|---|
| Test case name | Reservation of a Charge Point - Occupied |
| Test case Id | TC_050_2_CS |
| System under test | Charge Point |
Description
The Central System attempts to reserve a Charge Point, but the reservation is not made, instead the status Occupied is returned.
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.
- ReserveConnectorZeroSupported is true
Before (Preparations)
Configuration State(s):
- N/a
Memory State(s):
- N/a
Reusable State(s):
- SetConnectorOccupied for all connectors
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 |
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 0
Expected result(s) / behaviour
Charge Point side:
The Charge Point continues normal operation.
Central System side:
- N/a