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

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

Identification

Field	Value
Test case name	Offline Start Transaction - Invalid IdTag - StopTransactionOnInvalidId = true
Test case Id	TC_037_3_CS
System under test	Charge Point

Description

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

Purpose

To test if the Charge Point is able to start a transaction, while being offline and is able to queue transaction- related messages, after restoring the connection.

Prerequisite(s)

The Charge Point supports offline transactions using Local Authorization List, Authorization Cache or Unknown Offline Authorization.

Before (Preparations)

Configuration State(s):

LocalAuthorizeOffline is true.
LocalAuthListEnabled is true. (If implemented)
AuthorizationCacheEnabled is true. (If implemented)
AllowOfflineTxForUnknownId is true. (If implemented)
StopTransactionOnInvalidId is true.
MaxEnergyOnInvalidId is 0. (If implemented)

Memory State(s):

IdTagLocalAuthList for <Configured invalid IdTag>. (If implemented)
IdTagCached for <Configured invalid IdTag>. (If implemented)

Reusable State(s):

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:

Central System side: