TC_C_13_CS — Authorization through authorization cache - Accepted but cable not connected yet.
TC_C_13_CS — Authorization through authorization cache - Accepted but cable not connected yet.
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block C. Authorization, page 94.
Identification
| Field | Value |
|---|---|
| Test case name | Authorization through authorization cache - Accepted but cable not connected yet. |
| Test case Id | TC_C_13_CS |
| Use case Id(s) | C12 |
| Requirement(s) | C12_FR_02, C12_FR_04 |
| System under test | Charging Station |
| Functional block | C. Authorization |
Description
This test case describes how the EV Driver is authorized to start a transaction while the Charging Station uses Cached IdToken. This enables the EV Driver to Online start a transaction by using the Authorization Cache in which the Charging Station can respond faster, as no AuthorizeRequest is being sent.
Purpose
To verify if the Charging Station is able to Authorize an idToken which has status "Accepted" in its cache but the cable is not connected yet according to the mechanism as described in the OCPP specification.
Prerequisite(s)
AuthCacheCtrlr.AuthCacheAvailable is implemented with value true
Before (Preparations)
Configuration State:
- AuthCacheCtrlr.AuthCacheEnabled is true (If implemented) AuthCtrlr.LocalPreAuthorize is true (If implemented)
Memory State:
- IdTokenCached for <Configured valid IdToken fields> (If implemented)
Reusable State(s):
- If applicable, State is ParkingBayOccupied
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| Manual Action: Present valid idToken which is already configured in the Authorization Cache | |
| 1. The Charging Station sends a TransactionEventRequest; Note(s):; - This step needs to be executed when TxStartPoint contains Authorized OR the transaction already started. So in the case TxStartPoint contains ParkingBayOccupancy. - As long as the cable is not plugged in the energy transfer will not start. | 2. The OCTT responds with a TransactionEventResponse with idTokenInfo.status Accepted |
| 3. Execute Reusable State EVConnectedPreSession | |
| 4. Execute Reusable State EnergyTransferStarted |
Tool validations
Step 1:
Message TransactionEventRequest
- triggerReason Authorized
- idToken.idToken <Configured valid_idtoken_idtoken>
- idToken.type <Configured valid_idtoken_type> if transaction was already started
- eventType Updated else
- eventType Started
Post scenario validations
- Energy transfer is started