TC_061_CS — Clear Authorization Data in Authorization Cache
TC_061_CS — Clear Authorization Data in Authorization Cache
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 17.
Identification
| Field | Value |
|---|---|
| Test case name | Clear Authorization Data in Authorization Cache |
| Test case Id | TC_061_CS |
| System under test | Charge Point |
Description
The Central System can clear the Authorization Cache of a Charge Point.
Purpose
Check whether the Charge Point can handle the message to clear the Authorization Cache.
Prerequisite(s)
- The Charge Point has an authorization cache implemented.
Before (Preparations)
Configuration State(s):
- Value for "AuthorizationCacheEnabled" is "true".
- Value for "LocalPreAuthorize" is "true".
- Value for "ConnectionTimeOut" is <Configured ConnectionTimeout>.
Memory State(s):
- N/a
Reusable State(s):
- Authorized
Scenario Detail(s)
| Charge Point (SUT) | Central System (Tool) |
|---|---|
| 1. The Charge Point sends an StatusNotification.req to the Central System. | 2. The Central system responds with an StatusNotification.conf |
| [EV driver authorizes / swipes valid card OR wait for the connectionTimeout if the Charge Point does not deauthorize the transaction after swiping again.]; 3. The Charge Point sends an StatusNotification.req to the Central System. | 4. The Central system responds with an StatusNotification.conf |
| 6. The Charge Point responds with a ClearCache.conf | 5. The Central System sends a ClearCache.req |
| [The EV driver authorizes / swipes card with the authorization token which was used at step 1.]; 7. The Charge Point sends an Authorize.req | 8. The Central System responds with an Authorize.conf |
Tool validation(s)
Charge Point side:
Step 1:
(Message: StatusNotification.req) status is Preparing
Step 3:
(Message: StatusNotification.req) status is Available
Step 6:
(Message: ClearCache.conf) status is Accepted
Central System side:
Step 8:
(Message: Authorize.conf) idTagInfo.status is Accepted
Expected result(s) / behaviour
Charge Point side:
The Charge Point Authorization Cache is cleared.
Central System side:
The Central System is able to send a message to clear the cache.