Skip to content
Documentation Menu

TC_037_1_CS — Offline Start Transaction - Valid IdTag

TC_037_1_CS — Offline Start Transaction - Valid IdTag

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

Identification

FieldValue
Test case nameOffline Start Transaction - Valid IdTag
Test case IdTC_037_1_CS
System under testCharge 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)

Memory State(s):

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

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 a valid idTag.]; [Restore connectivity between Charge Point and Central System.]; 1. The Charge Point sends a StartTransaction.req2. The Central System responds with a StartTransaction.conf
3. The Charge Point sends a StatusNotification.req4. The Central System responds with a StatusNotification.conf

Tool validation(s)

Charge Point side:

Step 3:

(Message: StatusNotification.req) status is Charging

Central System side:

Step 2:

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

Expected result(s) / behaviour

Charge Point side:

  • N/a

Central System side:

  • N/a