Skip to content
Documentation Menu

TC_F_04_CSMS — Remote start transaction - Remote start first - Cable plugin timeout

TC_F_04_CSMS — Remote start transaction - Remote start first - Cable plugin timeout

Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block F. Remote Control, page 409.

Identification

FieldValue
Test case nameRemote start transaction - Remote start first - Cable plugin timeout
Test case IdTC_F_04_CSMS
Use case Id(s)F02, E03
Requirement(s)E03.FR.05
System under testCSMS
Functional blockF. Remote Control

Description

OCPP 2.x.x allows an EV driver to either first wait for/trigger a RequestStartTransactionRequest OR connect the EV and EVSE. Both sequences will result in being able to charge.

Purpose

To verify if the CSMS is able to handle a Charging Station that deauthorizes the transaction after the EVConnectionTimeout has been reached.

Prerequisite(s)

N/a

Before (Preparations)

Configuration State:

  • N/a

Memory State:

  • N/a

Reusable State(s):

  • N/a

Main (Test scenario)

Charging StationCSMS
Manual Action: Trigger the CSMS to request the Charging Station to start a transaction.
2. The OCTT responds with a RequestStartTransactionResponse; with status Accepted transactionId is omitted.1. The CSMS sends a RequestStartTransactionRequest
3. The OCTT sends a TransactionEventRequest.; with triggerReason is RemoteStart transactionInfo.remoteStartId is <By OCTT generated remoteStartID> eventType is Started4. The CSMS responds with a TransactionEventResponse.
5. The OCTT sends a TransactionEventRequest.; with triggerReason is EVConnectTimeout eventType is Updated; Note(s):; - This step will be executed after the <Configured Transaction Duration> has been reached.6. The CSMS responds with a TransactionEventResponse.

Tool validations

Step 1:

Message: RequestStartTransactionRequest

  • idToken.idToken <Configured valid_idtoken_idtoken>
  • idToken.type <Configured valid_idtoken_type>

Post scenario validations

  • N/a