Skip to content
Documentation Menu

TC_E_11_CSMS — Start transaction options - DataSigned

TC_E_11_CSMS — 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 389.

Identification

FieldValue
Test case nameStart transaction options - DataSigned
Test case IdTC_E_11_CSMS
Use case Id(s)E01(S4)
Requirement(s)E01.FR.04
System under testCSMS
Functional blockE. 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 signed meter values are received.

Prerequisite(s)

N/a

Before (Preparations)

Configuration State:

  • N/a

Memory State:

  • N/a

Reusable State(s):

  • N/a

Main (Test scenario)

Charging StationCSMS
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 notifies the CSMS about the status change of the connector.; Message: StatusNotificationRequest; - connectorStatus is Occupied; Message: NotifyEventRequest; - trigger is Delta; - actualValue is Occupied; - component.name is Connector; - variable.name is AvailabilityState4. The CSMS responds accordingly.
5. The OCTT sends a TransactionEventRequest; With eventType is Started triggerReason is SignedDataReceived idToken.idToken <Configured valid_idtoken_idtoken> idToken.type <Configured valid_idtoken_type> evse.id is <Configured evseId> evse.connectorId is <Configured connectorId> meterValue is provided with the following values: sampledValue.value is 0.0 sampledValue.context is Transaction.Begin sampledValue.signedMeterValue is <Generated SignedMeterValueType>6. The CSMS responds with a TransactionEventResponse
7. The OCTT sends a TransactionEventRequest; With eventType is Updated triggerReason is ChargingStateChanged transactionInfo.chargingState is Charging8. The CSMS responds with a TransactionEventResponse

Tool validations

Step 2:

Message: AuthorizeResponse

  • idTokenInfo.status must be Accepted

Step 6:

Message: TransactionEventResponse

  • idTokenInfo.status must be Accepted

Post scenario validations

  • N/a