TC_C_32_CS — Store Authorization Data in the Authorization Cache - Persistent over reboot
TC_C_32_CS — Store Authorization Data in the Authorization Cache - Persistent over reboot
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block C. Authorization, page 102.
Identification
| Field | Value |
|---|---|
| Test case name | Store Authorization Data in the Authorization Cache - Persistent over reboot |
| Test case Id | TC_C_32_CS |
| Use case Id(s) | C10 |
| Requirement(s) | C10_FR_02 |
| System under test | Charging Station |
| Functional block | C. Authorization |
Description
This test case covers how the Charging Station autonomously stores a record of previously presented identifiers that have been successfully authorized by the CSMS in the Authorization Cache. (Successfully meaning: a response received on a message containing an IdToken)
Purpose
To verify if the Charging Station is able to store the identifiers persistent over reboot according to the mechanism as described in the OCPP specification.
Prerequisite(s)
- The Charging Station supports the Authorization Cache feature
- Authorization cache is stored in the non-volatile memory.
Before (Preparations)
Configuration State:
- AuthCacheEnabled is true (If implemented) LocalPreAuthorize is true
Memory State:
- IdTokenCached for <Configured valid IdToken fields>
Reusable State(s):
- N/a
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 1. Execute Reusable State Booted | |
| Manual Action: Present valid idToken which is already configured in the Authorization Cache | |
| 2. 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. | 3. The OCTT responds with a TransactionEventResponse with idTokenInfo.status Accepted |
| 4. Execute Reusable State EVConnectedPreSession | |
| 5. Execute Reusable State EnergyTransferStarted |
Tool validations
Step 2:
Message TransactionEventRequest
- triggerReason Authorized
- idToken.idToken <Configured valid_idtoken_idtoken>
- idToken.type <Configured valid_idtoken_type>
Post scenario validations
- N/a