TC_049_CSMS — Reservation of a Charge Point - Transaction
TC_049_CSMS — Reservation of a Charge Point - Transaction
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Central System, page 168.
Identification
| Field | Value |
|---|---|
| Test case name | Reservation of a Charge Point - Transaction |
| Test case Id | TC_049_CSMS |
| System under test | Central System |
Description
A Charge Point / unspecified Connector is reserved and a charging transaction takes place.
Purpose
Check whether Central System trigger the Charge Point to reserve an unspecified 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 sends a ReserveNow.conf message to the Central System | 1. The Central System sends a ReserveNow.req with a reservationId, connectorId and idTag to the Charge Point |
| 3 The Charge Point sends a StatusNotification.req to the Central System | 4. The Central System sends a StatusNotification.conf to the Charge Point |
Tool validation(s)
Charge Point side:
Step 3:
(Message: StatusNotification.req) The status is Reserved
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:
The Central System accepts the reservation for the right idTag and reservationId.