TC_E_10_CS — Start transaction options - Authorized - Local
TC_E_10_CS — Start transaction options - Authorized - Local
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block E. Transactions, page 125.
Identification
| Field | Value |
|---|---|
| Test case name | Start transaction options - Authorized - Local |
| Test case Id | TC_E_10_CS |
| Use case Id(s) | E01(S3) AND (C01 OR C02 OR C04 OR C06) |
| Requirement(s) | E01.FR.03, E01.FR.07, E01.FR.10, E01.FR.15, E01.FR.16 AND C01.FR.02, C02.FR.01, C06.FR.02 |
| 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 supports at least one authorization method described at the following Use cases; C01, C02, C04, C06.
- 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 |
|---|---|
| Manual Action: Present IdToken. | |
| 1. The Charging Station sends an AuthorizeRequest; Note(s):; - This step needs to be executed, unless AuthEnabled is implemented with mutability ReadOnly AND the value is set to false OR a start button as described at Use case C02 is used (This must be configured at the OCTT). | 2. The OCTT responds with a AuthorizeResponse; with idTokenInfo.status Accepted |
| 3. The Charging Station sends a TransactionEventRequest | 4. The OCTT responds with a TransactionEventResponse |
Tool validations
Step 1:
Message: AuthorizeRequest
- idToken.idToken <Configured valid_idtoken_idtoken>
- idToken.type <Configured valid_idtoken_type>
Step 3:
Message: TransactionEventRequest
- eventType must be Started
- triggerReason must be Authorized
- idToken.idToken <Configured valid_idtoken_idtoken>
- idToken.type <Configured valid_idtoken_type>
Post scenario validations
- N/a