Skip to content
Documentation Menu

TC_010_CS — Remote Start Charging Session – Cable Plugged in First

TC_010_CS — 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: Charge Point, page 19.

Identification

FieldValue
Test case nameRemote Start Charging Session – Cable Plugged in First
Test case IdTC_010_CS
System under testCharge 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.conf1. The Central System sends a GetConfiguration.req; - key[0] is AuthorizeRemoteTxRequests
Manual Action: Plugin cable on both EV and CS side
3. The Charge Point sends a StatusNotification.req4. The Central System responds with a StatusNotification.conf
6. The Charge Point responds with a RemoteStartTransaction.conf5. The Central System sends a RemoteStartTransaction.req; - connectorId is <Configured ConnectorId>; - idTag is <Configured Valid IdTag>
[If AuthorizeRemoteTxRequests is true]; 7. The Charge Point sends an Authorize.req8. The Central System responds with an Authorize.conf; - idTagInfo.status is Accepted
[Steps 9 and 11 may be reversed]; 9. The Charge Point sends a StartTransaction.req10. The Central System responds with a StartTransaction.conf; - idTagInfo.status is Accepted
11. The Charge Point sends a StatusNotification.req12. The Central System responds with a StatusNotification.conf

Tool validation(s)

Charge Point side:

Step 3:

(Message: StatusNotification.req)

  • connectorId should be <Configured ConnectorId>
  • status should be Preparing

Step 6:

(Message: RemoteStartTransaction.conf)

  • status should be Accepted

Step 7:

(Message: Authorize.req)

  • idTag should be <Configured Valid IdTag>

Step 9:

(Message: StartTransaction.req)

  • connectorId should be <Configured ConnectorId>
  • idTag should be <Configured Valid IdTag>

Step 11:

(Message: StatusNotification.req)

  • connectorId should be <Configured ConnectorId>
  • status should be Charging

Central System side:

  • N/a

Expected result(s) / behaviour

Charge Point side:

  • N/a

Central System side:

  • N/a