TC_E_10_CSMS — Start transaction options - Authorized - Local
TC_E_10_CSMS — Start transaction options - Authorized - Local
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block E. Transactions, page 388.
Identification
| Field | Value |
|---|---|
| Test case name | Start transaction options - Authorized - Local |
| Test case Id | TC_E_10_CSMS |
| Use case Id(s) | E01(S3) |
| Requirement(s) | E01.FR.03 |
| System under test | CSMS |
| Functional block | E. Transactions |
Description
OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points to be configured differently. This test covers one of the start options.
Purpose
To verify if the CSMS is able to handle a Charging Station that starts a transaction when the EV and EVSE are connected.
Prerequisite(s)
N/a
Before (Preparations)
Configuration State:
- N/a
Memory State:
- N/a
Reusable State(s):
- N/a
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 1. The OCTT sends an AuthorizeRequest; With idToken.idToken <Configured valid_idtoken_idtoken> idToken.type <Configured valid_idtoken_type> | 2. The CSMS responds with an AuthorizeResponse |
| 3. The OCTT sends a TransactionEventRequest; With eventType is Started triggerReason is Authorized idToken.idToken <Configured valid_idtoken_idtoken> idToken.type <Configured valid_idtoken_type> | 4. The CSMS responds with a TransactionEventResponse |
Tool validations
Step 2:
Message: AuthorizeResponse
- idTokenInfo.status must be Accepted
Step 4:
Message: TransactionEventResponse
- idTokenInfo.status must be Accepted
Post scenario validations
- N/a