TC_F_03_CS — Remote start transaction - Remote start first - AuthorizeRemoteStart is false
TC_F_03_CS — Remote start transaction - Remote start first - AuthorizeRemoteStart is false
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block F. Remote Control, page 175.
Identification
| Field | Value |
|---|---|
| Test case name | Remote start transaction - Remote start first - AuthorizeRemoteStart is false |
| Test case Id | TC_F_03_CS |
| Use case Id(s) | F02 |
| Requirement(s) | F02.FR.01, F01.FR.02 |
| System under test | Charging Station |
| Functional block | F. 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 Charging Station is able to start a charging session when the Charging Stations receives a RequestStartTransactionRequest message (while AuthorizeRemoteStart is false), before the EV driver connects the EV and EVSE (within the connectionTimeout). The Charging station does NOT have to authorize beforehand like a local action to start a transaction.
Prerequisite(s)
AuthorizeRemoteStart is NOT implemented with mutability ReadOnly and the value set to true
Before (Preparations)
Configuration State:
- AuthCtrlr.AuthEnabled is true (If implemented AND ReadWrite) AuthCtrlr.DisableRemoteAuthorization is false (If implemented) AuthorizeRemoteStart is false (If ReadWrite)
Memory State:
- N/a
Reusable State(s):
- State is ParkingBayOccupied (Optional state)
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 1. Execute Reusable State Authorized (remote) | |
| 2. Execute Reusable State EnergyTransferStarted |
Tool validations
N/a
Post scenario validations
- N/a