Skip to content
Documentation Menu

TC_G_11_CS — Change Availability EVSE - With ongoing transaction

TC_G_11_CS — Change Availability EVSE - With ongoing transaction

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

Identification

FieldValue
Test case nameChange Availability EVSE - With ongoing transaction
Test case IdTC_G_11_CS
Use case Id(s)G03
Requirement(s)G03.FR.01, G03.FR.02, G03.FR.04, G03.FR.05
System under testCharging Station
Functional blockG. Availability

Description

This test case covers how the CSMS requests the Charging Station to change the availability of one of the EVSEs from Operative to Inoperative. An EVSE is considered Operative in any status other than Faulted and Unavailable.

Purpose

To verify if the Charging Station is able to perform the change availability during a transaction according to the mechanism as described at the OCPP specification.

Prerequisite(s)

n/a

Before (Preparations)

Configuration State:

  • N/a

Memory State:

  • N/a

Reusable State(s):

  • N/a

Main (Test scenario)

Charging StationCSMS
2. The Charging Station responds with a ChangeAvailabilityResponse1. The OCTT sends a ChangeAvailabilityRequest; with operationalStatus Inoperative and evse.id <Configured evseId>
Note(s): Wait for <Configured Transaction Duration>
3. Execute Reusable State StopAuthorized
4. The Charging Station notifies the CSMS about the current state of the connectors of the configured evse.5. The OCTT responds accordingly.
6. Execute Reusable State EVConnectedPostSession
7. The Charging Station notifies the CSMS about the current state of the connectors of the configured evse.8. The OCTT responds accordingly.
9. Execute Reusable State EVDisconnected
10. The Charging Station notifies the CSMS about the current state of the connectors of the configured evse.11. The OCTT responds accordingly.
12. Execute Reusable State ParkingBayUnoccupied
13. The Charging Station notifies the CSMS about the current state of the connectors of the configured evse.14. The OCTT responds accordingly.
Note(s): Steps 4, 5, 7, 8, 10, 11, 13, and 14 will only be executed if the previous step ended the transaction

Tool validations

Step 2:

Message ChangeAvailabilityResponse

  • status Scheduled

Step 4, 7, 10, 13:

Message: StatusNotificationRequest

  • connectorStatus Unavailable
  • evseId <Configured evseId> Message: NotifyEventRequest
  • eventData[0].trigger Delta
  • eventData[0].actualValue "Unavailable"
  • eventData[0].component.name "Connector"
  • eventData[0].component.evse.id <Configured evseId>
  • eventData[0].variable.name "AvailabilityState"

Post scenario validations

  • A message to report the state of a connector has been received for all connectors.