TC_046_2_CS — Reservation of a Connector - Remote start transaction

TC_046_2_CS — Reservation of a Connector - Remote start transaction

Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 69.

Identification

Field	Value
Test case name	Reservation of a Connector - Remote start transaction
Test case Id	TC_046_2_CS
System under test	Charge Point

Description

A Connector is reserved and a charging transaction takes place.

Purpose

Check whether the Charge Point can reserve a Connector.

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):

• 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.Charging (Sending an Authorize.req is optional)

Tool validation(s)

Charge Point side:

Step 2:

(Message: ReserveNow.conf)

• The status is Accepted

Step 3:

(Message: StatusNotification.req)

• The status is 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 <Configured ConnectorId>
• The idTag is <Configured Valid IdTag>

Expected result(s) / behaviour

Charge Point side:

The Charge Point handles the reservation correctly, only the idTag from the reservation can charge on the reserved Connector.

Central System side:

• N/a