TC_C_06_CS — Local start transaction - Authorization Blocked
TC_C_06_CS — Local start transaction - Authorization Blocked
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block C. Authorization, page 87.
Identification
| Field | Value |
|---|---|
| Test case name | Local start transaction - Authorization Blocked |
| Test case Id | TC_C_06_CS |
| Use case Id(s) | C01 |
| Requirement(s) | C01.FR.02 |
| System under test | Charging Station |
| Functional block | C. Authorization |
Description
When a Charging Station needs to charge an EV, it needs to authorize the EV Driver first at the CSMS before the charging can be started or stopped.
Purpose
To verify whether the Charging Station is able to handle receiving an Blocked idToken.
Prerequisite(s)
The Charging Station does NOT have a cable lock, which prevents the EV driver to connect the EV and EVSE before authorization.
Before (Preparations)
Configuration State:
- AuthCtrlr.AuthEnabled is true (If implemented AND ReadWrite) AuthCtrlr.DisableRemoteAuthorization is false (If implemented)
Memory State:
- N/a
Reusable State(s):
- State is EVConnectedPreSession
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| Manual Action: Present idToken. | |
| 1. The Charging Station sends an AuthorizeRequest | 2. The OCTT responds with an AuthorizeResponse; with idTokenInfo.status Blocked |
| Note(s):; - The Charging Station SHALL NOT send a TransactionEventRequest message after the AuthorizeRequest from step 7.; - The OCTT waits <Configured message timeout> seconds, before ending the testcase. |
Tool validations
Step 1:
Message: AuthorizeRequest
- idToken.idToken <Configured blocked_idtoken_idtoken>
- idToken.type <Configured blocked_idtoken_type>
Post scenario validations
- N/a