TC_039_CS — Offline Transaction

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

Identification

Field	Value
Test case name	Offline Transaction
Test case Id	TC_039_CS
System under test	Charge Point

Description

This scenario is used to start and stop a transaction, while the Charge Point is offline.

Purpose

To test if the Charge Point is able to start and stop a transaction, while being offline and if it is able to queue all the transaction-related messages.

Prerequisite(s)

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

Before (Preparations)

Configuration State(s):

LocalAuthorizeOffline is true.
LocalAuthListEnabled is true. (If implemented)
AuthorizationCacheEnabled is true. (If implemented)
AllowOfflineTxForUnknownId is true. (If implemented)

Memory State(s):

IdTagLocalAuthList for <Configured valid IdTag>. (If implemented)
IdTagCached for <Configured valid 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.]; [EV Driver stops offline a transaction.]; [EV driver unplugs the cable.]; [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 StopTransaction.req	4. The Central System responds with a StopTransaction.conf

Tool validation(s)

Charge Point side:

Step 3:

(Message: StopTransaction.req) reason is Local or is omitted

Central System side:

Step 2:

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

Expected result(s) / behaviour

Charge Point side:

Central System side: