TC_053_CSMS — Use a reserved Connector with parentIdTag
TC_053_CSMS — Use a reserved Connector with parentIdTag
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Central System, page 170.
Identification
| Field | Value |
|---|---|
| Test case name | Use a reserved Connector with parentIdTag |
| Test case Id | TC_053_CSMS |
| System under test | Central System |
Description
The Charge Point has been reserved and is used with a parentIdTag
Purpose
Check whether the Central System can handle messages for a reservation that is used by a parentIdTag
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) |
|---|---|
| Manual Action: Reserve a connector on the Charge Point. | |
| 2. The Charge Point sends a ReserveNow.conf. | 1. The Central System sends a ReserveNow.req with a reservationId, an idTag and a parentIdTag. |
| 3. The Charge Point sends a StatusNotification.req. | 4. The Central System sends a StatusNotification.conf. |
| [EV driver authorizes / swipes card with the parentIdTag from step 1, but a different IdTag]; 5. Execute reusable state Charging |
Tool validation(s)
Charge Point side:
Step 2:
(Message: ReserveNow.conf) The status is Accepted
Step 3:
(Message: StatusNotification.req) The status is Reserved
Central System side:
Step 1:
(Message: ReserveNow.req) The connectorId does not equal 0
Expected result(s) / behaviour
Charge Point side:
The Charge Point handles the reservation correctly, the parentIdTag from the reservation can charge on the reserved Connector.
Central System side:
The Central System accepts the reservation for the right parentIdTag and reservationId.