TC_010_CSMS — Remote Start Charging Session – Cable Plugged in First

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

Identification

Field	Value
Test case name	Remote Start Charging Session – Cable Plugged in First
Test case Id	TC_010_CSMS
System under test	Central System

Description

This scenario is used to start a transaction remotely.

Purpose

To test if the Central System can handle when a Charge point starts a transaction after receiving a RemoteStartTransaction.req from the Central System.

Prerequisite(s)

Before (Preparations)

Configuration State(s):

Memory State(s):

Reusable State(s):

Scenario Detail(s)

Charge Point (SUT)	Central System (Tool)
[EV driver plugs in the cable.]; 1. The Charge Point sends a StatusNotification.req	2. The Central System responds with a StatusNotification.conf
4. The Charge Point responds with a RemoteStartTransaction.conf	3. The Central System sends a RemoteStartTransaction.req
5. The Charge Point sends an Authorize.req	6. The Central System responds with an Authorize.conf
7. The Charge Point sends a StartTransaction.req	8. The Central System responds with a StartTransaction.conf
9. The Charge Point sends a StatusNotification.req	10. The Central System responds with a StatusNotification.conf

Tool validation(s)

Charge Point side:

Step 1:

(Message: StatusNotification.req) status is Preparing

Step 4:

(Message: RemoteStartTransaction.conf) status is Accepted

Step 9:

(Message: StatusNotification.req) status is Charging

Central System side:

Step 6:

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

Step 8:

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

Expected result(s) / behaviour

Charge Point side:

Central System side: