TC_007_CS — Regular Start Charging Session – Cached Id

TC_007_CS — Regular Start Charging Session – Cached Id

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

Identification

Field	Value
Test case name	Regular Start Charging Session – Cached Id
Test case Id	TC_007_CS
System under test	Charge Point

Description

This scenario is used to start a transaction with an id stored in the Authorization cache.

Purpose

To test if the Charge Point is able to start a transaction with an id which is stored in the Authorization cache.

Prerequisite(s)

The Charge Point has a cache.

Before (Preparations)

Configuration State(s):

• AuthorizationCacheEnabled is true.
• LocalPreAuthorize is true.

Memory State(s):

• IdTagCached for <Configured valid IdTag>

Reusable State(s):

• N/a

Scenario Detail(s)

Charge Point (SUT)	Central System (Tool)
[EV driver presents identification.]
1. The Charge Point sends a StatusNotification.req	2. The Central System responds with a StatusNotification.conf
[EV driver plugs in the cable]
[Steps 3 and 6 may be reversed]; 3. The Charge Point sends a StartTransaction.req	4. The Central System responds with a StartTransaction.conf
5. The Charge Point sends a StatusNotification.req	6. The Central System responds with a StatusNotification.conf

Tool validation(s)

Charge Point side:

Step 1:

(Message: StatusNotification.req) status is Preparing

Step 5:

(Message: StatusNotification.req) status is Charging

Central System side:

Step 4:

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

Expected result(s) / behaviour

Charge Point side:

• N/a

Central System side:

• N/a