Skip to content
Documentation Menu

TC_046_1_CS — Reservation of a Connector - Local start transaction

TC_046_1_CS — Reservation of a Connector - Local start transaction

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

Identification

FieldValue
Test case nameReservation of a Connector - Local start transaction
Test case IdTC_046_1_CS
System under testCharge 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):

  • SetConnectorUnavailable for all unused connectors

Scenario Detail(s)

Charge Point (SUT)Central System (Tool)
2. The Charge Point responds with a ReserveNow.conf1. The Central System sends a ReserveNow.req
3 The Charge Point sends a StatusNotification.req to the Central System4. The Central System responds with a StatusNotification.conf to the Charge Point
[EV driver authorizes / swipes a card (not the idTag from step 1)]; 5. The Charge Point does NOT send an Authorize.req to the Central System
[EV driver authorizes / swipes the card with the idTag from step 1]; 6. The Charge Point sends an optional Authorize.req to the Central System7. The Central System responds with an Authorize.conf to the Charge Point
8. The Charge Point sends a StatusNotification.req9. The Central System responds with a StatusNotification.conf
[EV driver plugs in cable at the reserved Connector]; 10. The Charge Point sends a StartTransaction.req11. The Central System responds with a StartTransaction.conf
12 The Charge Point sends a StatusNotification.req13. The Central System responds with a StatusNotification.conf

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

(Message: Authorize.req)

  • The idTag matches the idTag from step 1.

Step 8:

(Message: StatusNotification.req)

  • The status is Preparing

Step 10:

(Message: StartTransaction.req)

  • The reservationId matches the reservationId from step 1.
  • The idTag matches the idTag from step 1.
  • The idTag and reservationId are included in the message.

Step 12:

(Message: StatusNotification.req)

  • The status is Charging

Central System side:

Step 1:

(Message: ReserveNow.req)

  • The connectorId is <Configured ConnectorId>
  • The idTag is <Configured Valid IdTag>

Step 9:

(Message: Authorize.conf)

  • The idTagInfo.status is Accepted

Step 11:

(Message: StartTransaction.conf)

  • The status is Accepted

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