TC_011_1_CS — Remote Start Charging Session – Remote Start First

TC_011_1_CS — Remote Start Charging Session – Remote Start First

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

Identification

Field	Value
Test case name	Remote Start Charging Session – Remote Start First
Test case Id	TC_011_1_CS
System under test	Charge Point

Description

This scenario is used to start a transaction remotely.

Purpose

To test if the Charge point is able to start a transaction after receiving a RemoteStartTransaction.req from the Central System.

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)
2. The Charge Point responds with a GetConfiguration.conf	1. The Central System sends a GetConfiguration.req
4. The Charge Point responds with a RemoteStartTransaction.conf	3. The Central System sends a RemoteStartTransaction.req
[If AuthorizeRemoteTxRequests = true (from step 2), send an Authorize.req.]; 5. The Charge Point sends an Authorize.req	6. The Central System responds with an Authorize.conf
7. The Charge Point sends a StatusNotification.req	8. The Central System responds with a StatusNotification.conf
[EV driver plugs in the cable.]; 9. The Charge Point sends a StartTransaction.req	10. The Central System responds with a StartTransaction.conf
11. The Charge Point sends a StatusNotification.req	12. The Central System responds with a StatusNotification.conf

Tool validation(s)

Charge Point side:

Step 2:

(Message: GetConfiguration.conf) The configurationKey.key is AuthorizeRemoteTxRequests

Step 4:

(Message: RemoteStartTransaction.conf) status is Accepted

Step 7:

(Message: StatusNotification.req) status is Preparing

Step 11:

(Message: StatusNotification.req) status is Charging

Central System side:

Step 1:

(Message: GetConfiguration.req) The key is AuthorizeRemoteTxRequests

Step 6:

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

Step 10:

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

Expected result(s) / behaviour

Charge Point side:

• N/a

Central System side:

• N/a