TC_037_3_CSMS — Offline Start Transaction - Invalid IdTag - StopTransactionOnInvalidId = true

TC_037_3_CSMS — Offline Start Transaction - Invalid IdTag - StopTransactionOnInvalidId = true

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

Identification

Field	Value
Test case name	Offline Start Transaction - Invalid IdTag - StopTransactionOnInvalidId = true
Test case Id	TC_037_3_CSMS
System under test	Central System

Description

This scenario is used to start a transaction, while being offline.

Purpose

To test if the Central System can handle when a Charge Point starts a transaction, while being offline and queues transaction-related messages, after restoring the connection.

Prerequisite(s)

• N/a

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)
[Remove connectivity between Charge Point and Central System.]; [EV Driver starts offline a transaction with an invalid idTag.]; [Restore connectivity between Charge Point and Central System.]; 1. The Charge Point sends a StartTransaction.req	2. The Central System responds with a StartTransaction.conf
3. The Charge Point sends a StatusNotification.req	4. The Central System responds with a StatusNotification.conf
5. The Charge Point sends a StopTransaction.req	6. The Central System responds with a StopTransaction.conf
7. The Charge Point sends a StatusNotification.req	8. The Central System responds with a StatusNotification.conf

Tool validation(s)

Charge Point side:

Step 3:

(Message: StatusNotification.req) status is Charging

Step 5:

(Message: StopTransaction.req) reason is DeAuthorized

• Step 7 (Message: StatusNotification.req) status is Finishing

Central System side:

Step 2:

(Message: StartTransaction.conf) idTagInfo.status is Invalid

Expected result(s) / behaviour

Charge Point side:

• N/a

Central System side:

• N/a