Skip to content
Documentation Menu

TC_C_37_CS — Clear Authorization Data in Authorization Cache - Accepted

TC_C_37_CS — Clear Authorization Data in Authorization Cache - Accepted

Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block C. Authorization, page 106.

Identification

FieldValue
Test case nameClear Authorization Data in Authorization Cache - Accepted
Test case IdTC_C_37_CS
Use case Id(s)C11
Requirement(s)C11_FR_01, C11.FR.02, C11.FR.03
System under testCharging Station
Functional blockC. 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 clear all identifiers from the Authorization Cache 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)

Memory State:

  • IdTokenCached for <Configured valid IdToken fields>

Reusable State(s):

  • N/a

Main (Test scenario)

Charging StationCSMS
2. The Charging Station responds with a ClearCacheResponse1. The OCTT sends a ClearCacheRequest
3. Execute Reusable State ParkingBayOccupied
4. Execute Reusable State EVConnectedPreSession
Manual Action: Present valid idToken which was configured in the Authorization Cache
5. The Charging Station sends an AuthorizeRequest6. The OCTT responds with an AuthorizeResponse with idTokenInfo.status Accepted
7. The Charging Station sends an TransactionEventRequest8. The OCTT responds with an TransactionEventResponse with triggerReason Authorized
9. Execute Reusable State EnergyTransferStarted

Tool validations

Step 2:

Message ClearCacheResponse

  • status Accepted

Step 5:

Message AuthorizeRequest

  • idToken.idToken <Configured valid_idtoken_idtoken>
  • idToken.type <Configured valid_idtoken_type>

Post scenario validations

  • N/a