TC_049_CS — Reservation of a Charge Point - Transaction
TC_049_CS — Reservation of a Charge Point - Transaction
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 73.
Identification
| Field | Value |
|---|---|
| Test case name | Reservation of a Charge Point - Transaction |
| Test case Id | TC_049_CS |
| System under test | Charge Point |
Description
A Charge Point / unspecified Connector is reserved and a charging transaction takes place.
Purpose
Check whether the Charge Point can reserve an unspecified Connector.
Prerequisite(s)
- The Charge Point supports the Reservation feature profile.
- The value for ReserveConnectorZeroSupported is set to true.
Before (Preparations)
Configuration State(s):
- N/a
Memory State(s):
- N/a
Reusable State(s):
- SetConnectorUnavailable for all unused 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 |
| 3. The Charge Point sends a StatusNotification.req | 4. The Central System responds with a StatusNotification.conf |
| [The tool will start a transaction on the reserved connector] 5.Charging (Sending an Authorize.req is optional) |
Tool validation(s)
Charge Point side:
Step 2:
(Message: ReserveNow.conf)
- The status should be Accepted
Step 3:
(Message: StatusNotification.req)
- The status should be Reserved
Step 5:
- The idTag and reservationId from the StartTransaction.req matches the idTag and reservationId from step 1.
Central System side:
Step 1:
(Message: ReserveNow.req)
- The connectorId is 0
Expected result(s) / behaviour
Charge Point side:
The Charge Point handles the reservation correctly, only the idTag from the reservation can charge, on any available connector of the Charge Point.
Central System side:
- N/a