TC_E_13_CS — Start transaction options - Authorized - Remote
TC_E_13_CS — Start transaction options - Authorized - Remote
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block E. Transactions, page 126.
Identification
| Field | Value |
|---|---|
| Test case name | Start transaction options - Authorized - Remote |
| Test case Id | TC_E_13_CS |
| Use case Id(s) | E01(S3) AND F02 |
| Requirement(s) | E01.FR.03 AND F01.FR.03, F01.FR.04, F01.FR.06, F01.FR.19, F02.FR.01 |
| System under test | Charging Station |
| Functional block | E. Transactions |
Description
OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points to be configured differently. This test covers one of the start options.
Purpose
To verify if the Charging Station starts a transaction when the EV and EVSE are connected and it has been configured to do so.
Prerequisite(s)
- The Charging Station does NOT have the following configuration; The mutability of TxStartPoint is ReadOnly AND the value Authorized is NOT set.
- If the mutability of TxStartPoint is ReadWrite, then the value Authorized must be supported.
Before (Preparations)
Configuration State:
- If the mutability of TxStartPoint is ReadWrite then TxStartPoint contains Authorized AuthCtrlr.AuthEnabled is true (If implemented AND ReadWrite) AuthCtrlr.DisableRemoteAuthorization is false (If implemented)
Memory State:
- N/a
Reusable State(s):
- N/a
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 2. The Charging Station responds with a RequestStartTransactionResponse | 1. The OCTT sends a RequestStartTransactionRequest; with idToken.idToken <Configured valid_idtoken_idtoken> idToken.type <Configured valid_idtoken_type> evseId <Configured evseId> |
| 3. The Charging Station sends an AuthorizeRequest; Note(s):; - This step needs to be executed when AuthCtrlr.AuthorizeRemoteStart is true, unless AuthEnabled is implemented with mutability ReadOnly AND the value is set to false. | 4. The OCTT responds with an AuthorizeResponse with: idTokenInfo.status Accepted |
| 5. The Charging Station sends a TransactionEventRequest | 6. The OCTT responds with a TransactionEventResponse |
Tool validations
Step 2:
Message: RequestStartTransactionResponse
- status must be Accepted
Step 3:
Message: AuthorizeRequest
- idToken.idToken <Configured valid_idtoken_idtoken>
- idToken.type <Configured valid_idtoken_type>
Step 5:
Message: TransactionEventRequest
- eventType must be Started
- triggerReason must be RemoteStart
- idToken.idToken <Configured valid_idtoken_idtoken>
- idToken.type <Configured valid_idtoken_type>
- transactionInfo.remoteStartId must be present
Post scenario validations
- N/a