Documentation Menu

TC_C_47_CSMS — Stop Transaction with a Master Pass - With UI - All transactions

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

Identification

Field	Value
Test case name	Stop Transaction with a Master Pass - With UI - All transactions
Test case Id	TC_C_47_CSMS
Use case Id(s)	C16
Requirement(s)	C16_FR_01
System under test	CSMS
Functional block	C. Authorization

Description

This test case covers how somebody with a Master Pass (User) can stop (selected) ongoing transactions, so the cable becomes unlocked. This Master Pass can be configured in: MasterPassGroupId. This could for example be usefull for Law Enforcement officials.

Purpose

To verify if the CSMS is able to correctly respond on a request to stop all transactions when an idToken which has the MasterPass as GroupId is used and the user has selected to stop all transactions in the User Interface according to the mechanism as described in the OCPP specification.

Prerequisite(s)

Before (Preparations)

Configuration State:

Memory State:

An idToken with the MastersPass as GroupId is configured

Reusable State(s):

State is EnergyTransferStarted for EVSE 1 with idToken valid idToken State is EnergyTransferStarted for EVSE 2 with idToken valid idToken2

Main (Test scenario)

Charging Station	CSMS
1. The OCTT sends an AuthorizeRequest with idToken.idToken <Configured masterpass_idtoken_idtoken> idToken.type <Configured masterpass_idtoken_type>	2. The CSMS responds with an AuthorizeResponse
3. The OCTT sends a TransactionEventRequest with; - transactionInfo.stoppedReason MasterPass; - idToken.idToken <Configured masterpass_idtoken_idtoken>; - idToken.type <Configured masterpass_idtoken_type>; - eventType Ended for both EVSE	4. The CSMS responds with a TransactionEventResponse for both EVSE

TC_C_47_CSMS — Stop Transaction with a Master Pass - With UI - All transactions