TC_C_33_CS — Store Authorization Data in the Authorization Cache - Update on AuthorizeResponse
TC_C_33_CS — Store Authorization Data in the Authorization Cache - Update on AuthorizeResponse
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block C. Authorization, page 103.
Identification
| Field | Value |
|---|---|
| Test case name | Store Authorization Data in the Authorization Cache - Update on AuthorizeResponse |
| Test case Id | TC_C_33_CS |
| Use case Id(s) | C10 |
| Requirement(s) | C10_FR_04, C12.FR.06 |
| 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 correctly upon an AutorizeResponse according to the mechanism as described in the OCPP specification.
Prerequisite(s)
- AuthCacheCtrlr.AuthCacheAvailable is implemented with value true
Before (Preparations)
Configuration State:
- AuthCacheEnabled is true (If implemented) LocalPreAuthorize is true LocalAuthListEnabled is true
Memory State:
- N/a
Reusable State(s):
- State is EVConnectedPreSession
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| Manual Action: Present valid idToken | |
| 1. The Charging Station sends an AuthorizeRequest | 2. The OCTT responds with an AuthorizeResponse with idTokenInfo.status Accepted |
| 3. The Charging Station sends a TransactionEventRequest; Note(s):; - This step needs to be executed when TxStartPoint contains ParkingBayOccupancy, EVConnected, Authorized, or PowerPathClosed | 4. The OCTT responds with a TransactionEventResponse with idTokenInfo.status Accepted |
| 5. Execute Reusable State EnergyTransferStarted | |
| 6. Execute Reusable State EVConnectedPostSession | |
| 7. Execute Reusable State EVDisconnected | |
| 8. Execute Reusable State ParkingBayUnoccupied | |
| 9. Execute Reusable State ParkingBayOccupied | |
| 10. Execute Reusable State EVConnectedPreSession | |
| Manual Action: Present same valid idToken | |
| 12. 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. | 13. The OCTT responds with a TransactionEventResponse with idTokenInfo.status Invalid |
Tool validations
- N/a
Post scenario validations
- N/a