TC_046_CSMS — Reservation of a Connector - Transaction
TC_046_CSMS — Reservation of a Connector - Transaction
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Central System, page 163.
Identification
| Field | Value |
|---|---|
| Test case name | Reservation of a Connector - Transaction |
| Test case Id | TC_046_CSMS |
| System under test | Central System |
Description
A Connector is reserved and a charging transaction takes place.
Purpose
Check whether Central System can trigger a Charge Point to Reserve a Connector.
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) |
|---|---|
| 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 |
| 5. Execute Reusable StateCharging |
Tool validation(s)
Charge Point side:
- SAtep 2: (Message: ReserveNow.conf)
- The status is Accepted
Step 3:
(Message: StatusNotification.req)
- The status is Reserved
Step 5:
(Reusable State: Charging)
- The reservationId is the reservationId from step 1
Central System side:
Step 1:
(Message: ReserveNow.req)
- The connectorId should be <Configured ConnectorId>
- The idTag should be <Configured Valid IdTag>
Expected result(s) / behaviour
Charge Point side:
- N/a
Central System side:
- N/a