TC_039_CSMS — Offline Transaction
TC_039_CSMS — Offline Transaction
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Central System, page 150.
Identification
| Field | Value |
|---|---|
| Test case name | Offline Transaction |
| Test case Id | TC_039_CSMS |
| System under test | Central System |
Description
This scenario is used to start and stop a transaction, while the Charge Point is offline.
Purpose
To test if the Central System is able to handle queued transaction-related messages, after a Charge Point comes back online again.
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.]; [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
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