TC_K_38_CS — Remote start transaction with charging profile - Ignore chargingProfile
TC_K_38_CS — Remote start transaction with charging profile - Ignore chargingProfile
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block K. SmartCharging, page 232.
Identification
| Field | Value |
|---|---|
| Test case name | Remote start transaction with charging profile - Ignore chargingProfile |
| Test case Id | TC_K_38_CS |
| Use case Id(s) | F01 |
| Requirement(s) | F01.FR.12 |
| System under test | Charging Station |
| Functional block | K. SmartCharging |
Description
The CSMS sets a TxProfile on a specific EVSE inside a RequestStartTransactionRequest message.
Purpose
To verify if the Charging Station is able to ignore a TxProfile on a specific EVSE when receiving one in a RequestStartTransactionRequest message, when it does not support Smart Charging.
Prerequisite(s)
The Charging Station does NOT support Smart Charging.
Before (Preparations)
Configuration State:
- N/a
Memory State:
- N/a
Reusable State(s):
- State is EVConnectedPreSession
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 2. The Charging Station responds with a RequestStartTransactionResponse | 1. The OCTT sends a RequestStartTransactionRequest; with idToken.idToken <Configured valid_idtoken_idtoken> idToken.type <Configured valid_idtoken_type> evseId <Configured evseId> chargingProfile.chargingProfilePurpose is TxProfile chargingProfile.transactionId is omitted. chargingProfile.chargingProfileKind is Relative chargingProfile.chargingSchedule.chargingSchedul ePeriod[0].numberPhases <Configured numberPhases> chargingProfile.chargingSchedule.chargingSchedul ePeriod[0].startPeriod 0 If <Configured chargingRateUnit> is A: chargingProfile.chargingSchedule.chargingSchedul ePeriod[0].limit 6 If <Configured chargingRateUnit> is W: chargingProfile.chargingSchedule.chargingSchedul ePeriod[0].limit 6000 |
| 3. The Charging Station sends an AuthorizeRequest; Note(s):; - This step needs to be executed when AuthCtrlr.AuthorizeRemoteStart is true, unless (AuthEnabled is implemented with mutability ReadOnly AND the value is set to false) OR the idToken is cached. In case the idToken is used for a reservation, sending the AuthorizeRequest message is optional. | 4. The OCTT responds with an AuthorizeResponse; with idTokenInfo.status Accepted |
| 5. The Charging Station sends a TransactionEventRequest; Note(s):; - This step needs to be executed when TxStartPoint contains Authorized OR the transaction already started. So in the case TxStartPoint contains ParkingBayOccupancy or (EVConnected, in the case this testcase was initiated from state EVConnectedPreSession.) | 6. The OCTT responds with a TransactionEventResponse; Note(s):; - The first TransactionEventRequest sent after authorization contains the idToken field. The TransactionEventResponse of this request message contains idTokenInfo; with status Accepted |
| 7. Execute Reusable State EnergyTransferStarted |
Tool validations
Step 2:
Message: RequestStartTransactionResponse
- status must be Accepted If the transaction has already been started, so if TxStartPoint contains ParkingBayOccupancy OR (TxStartPoint contains EVConnected AND State pre reusable state execution was EVConnectedPreSession) then
- transactionId must be <Provided transactionId in first TransactionEventRequest>
Step 3:
Message: AuthorizeRequest
- idToken.idToken <Configured valid_idtoken_idtoken>
- idToken.type <Configured valid_idtoken_type>
Step 5:
Message: TransactionEventRequest
- triggerReason must be RemoteStart
- transactionInfo.remoteStartId must be present.
Post scenario validations
- N/a