Skip to content
Documentation Menu

TC_B_22_CS — Reset Charging Station - With Ongoing Transaction - Immediate

TC_B_22_CS — Reset Charging Station - With Ongoing Transaction - Immediate

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

Identification

FieldValue
Test case nameReset Charging Station - With Ongoing Transaction - Immediate
Test case IdTC_B_22_CS
Use case Id(s)B12
Requirement(s)B12.FR.02, B12.FR.04, E07.FR.03, B01.FR.03
System under testCharging Station
Functional blockB. Provisioning

Description

This test case covers how the CSMS can remotely request the Charging Station to reset itself by sending a ResetRequest during a transaction. When ResetRequest "Immediate" is send the charging stations will try to stop all transactions before rebooting. This could for example be necessary if the Charging Station is not functioning correctly.

Purpose

To verify if the Charging Station is able to perform the reset mechanism as described at the OCPP specification.

Prerequisite(s)

n/a

Before (Preparations)

Configuration State:

  • N/a

Memory State:

  • N/a

Reusable State(s):

  • State is EnergyTransferStarted

Main (Test scenario)

Charging StationCSMS
2. The Charging Station responds with a ResetResponse1. The OCTT sends a ResetRequest; with type Immediate
3. The Charging Station sends a TransactionEventRequest4. The OCTT responds with a TransactionEventResponse
Note(s):; - Charging Station reboots
5. The Charging Station sends a BootNotificationRequest6. The OCTT responds with a BootNotificationResponse; with status Accepted
7. The Charging Station notifies the CSMS about the current state of all connectors.8. The OCTT responds accordingly.

Tool validations

Step 2:

Message ResetResponse

  • status Accepted

Step 3:

Message TransactionEventRequest

  • eventType Ended
  • triggerReason ResetCommand
  • transactionInfo.chargingState EVConnected
  • transactionInfo.stoppedReason ImmediateReset
  • idToken must be omitted

Step 5:

Message BootNotificationRequest

  • reason RemoteReset

Step 7:

For <Configured connectorId>: Message: StatusNotificationRequest

  • connectorStatus Occupied Message: NotifyEventRequest
  • eventData[0].trigger Delta
  • eventData[0].actualValue "Occupied"
  • eventData[0].component.name "Connector"
  • eventData[0].variable.name "AvailabilityState" For <Other connector(s)>: Message: StatusNotificationRequest
  • connectorStatus Available Message: NotifyEventRequest
  • eventData[0].trigger Delta
  • eventData[0].actualValue "Available"
  • eventData[0].component.name "Connector"
  • eventData[0].variable.name "AvailabilityState"

Post scenario validations

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