TC_051_CS — Cancel Reservation
TC_051_CS — Cancel Reservation
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 76.
Identification
| Field | Value |
|---|---|
| Test case name | Cancel Reservation |
| Test case Id | TC_051_CS |
| System under test | Charge Point |
Description
The Central System cancels an existing, not expired reservation.
Purpose
Check whether the Charge Point is able to cancel a reservation.
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):
- Reserved with <Configured Valid IdTag>
Scenario Detail(s)
| Charge Point (SUT) | Central System (Tool) |
|---|---|
| 2. The Charge Point responds a CancelReservation.conf | 1. The Central System sends a CancelReservation.req |
| 3. The Charge Point sends a StatusNotification.req | 4. The Central System responds a StatusNotification.conf |
| 5.Charging with <Configured Valid IdTag 2> |
Tool validation(s)
Charge Point side:
Step 2:
(Message: CancelReservation.conf)
- status should be Accepted
Step 3:
(Message: StatusNotification.req)
- status should be Available
- connectorId should match the connectorId used for reservation
Step 5:
(Reusable state: Charging)
- reservationId should be omitted.
Central System side:
Step 1:
(Message: CancelReservation.req)
- reservationId matches the reservationId from the reusable state Reserved
Expected result(s) / behaviour
Charge Point side:
The Charge Point handles the reservation correctly, cancelling only the reservation with the right reservationId.
Central System side:
- N/a