Documentation Menu

TC_E_11_CS — Start transaction options - DataSigned

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

Identification

Field	Value
Test case name	Start transaction options - DataSigned
Test case Id	TC_E_11_CS
Use case Id(s)	E01(S4)
Requirement(s)	E01.FR.04, E01.FR.07, E01.FR.10, E01.FR.15, E01.FR.16
System under test	Charging Station
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 Charging Station starts a transaction when the EV and EVSE are connected and it has been configured to do so.

Prerequisite(s)

The Charging Station does NOT have the following configuration; The mutability of TxStartPoint is ReadOnly AND (the value DataSigned is NOT set OR (ParkingBayOccupancy OR EVConnected OR Authorized), is set).
If the mutability of TxStartPoint is ReadWrite, then the value DataSigned must be supported.

Before (Preparations)

Configuration State:

If the mutability of TxStartPoint is ReadWrite then TxStartPoint contains DataSigned SampledDataCtrlr.SignReadings is true

Memory State:

Reusable State(s):

State is Authorized

Main (Test scenario)

Charging Station	CSMS
Manual Action: Connect the EV and EVSE.
1. The Charging Station notifies the CSMS about the status change of the connector.	2. The OCTT responds accordingly.
3. The Charging Station sends a TransactionEventRequest	4. The OCTT responds with a TransactionEventResponse
5. The Charging Station sends a TransactionEventRequest	6. The OCTT responds with a TransactionEventResponse

Tool validations

Step 1:

Message: StatusNotificationRequest

connectorStatus must be Occupied Message: NotifyEventRequest
eventData[0].trigger must be Delta
eventData[0].actualValue must be Occupied
eventData[0].component.name must be Connector
eventData[0].variable.name must be AvailabilityState

Step 3:

Message: TransactionEventRequest

eventType must be Started
If the OCTT is configured to start transactions using a RequestStartTransactionRequest message then triggerReason must be RemoteStart or SignedDataReceived Else triggerReason must be SignedDataReceived
idToken.idToken <Configured valid_idtoken_idtoken>
idToken.type <Configured valid_idtoken_type>
evse must be provided
evse.connectorId must be provided
meterValue is provided with the following values: sampledValue.context is Transaction.Begin sampledValue.signedMeterValue.encodingMethod is not omitted sampledValue.signedMeterValue.publicKey is not omitted sampledValue.signedMeterValue.signedMeterData is not omitted sampledValue.signedMeterValue.signingMethod is not omitted

Step 5:

Message: TransactionEventRequest

eventType must be Updated
triggerReason must be ChargingStateChanged
transactionInfo.chargingState must be Charging

TC_E_11_CS — Start transaction options - DataSigned