TC_C_34_CS — Store Authorization Data in the Authorization Cache - Update on TransactionResponse
TC_C_34_CS — Store Authorization Data in the Authorization Cache - Update on TransactionResponse
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block C. Authorization, page 104.
Identification
| Field | Value |
|---|---|
| Test case name | Store Authorization Data in the Authorization Cache - Update on TransactionResponse |
| Test case Id | TC_C_34_CS |
| Use case Id(s) | C10 |
| Requirement(s) | C10_FR_05, 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 TransactionResponse 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:
- IdTokenCached for <Configured valid IdToken fields>
Reusable State(s):
- State is EVConnectedPreSession
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| Manual Action: Present valid idToken | |
| 1. The Charging Station sends a TransactionEventRequest | 2. The OCTT responds with a TransactionEventResponse with idTokenInfo.status Invalid |
| 3. Execute Reusable State EVDisconnected | |
| 4. Execute Reusable State ParkingBayUnoccupied | |
| 5. Execute Reusable State ParkingBayOccupied | |
| 6. Execute Reusable State EVConnectedPreSession | |
| Manual Action: Present same valid idToken | |
| 7. The Charging Station sends an AuthorizeRequest | 8. The OCTT responds with an AuthorizeResponse with idTokenInfo.status Invalid |
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
Step 7:
Message AuthorizeRequest
- idToken.idToken <Configured valid_idtoken_idtoken>
- idToken.type <Configured valid_idtoken_type>
Post scenario validations
- N/a