Skip to content
Documentation Menu

TC_B_02_CSMS — Cold Boot Charging Station - Pending

TC_B_02_CSMS — Cold Boot Charging Station - Pending

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

Identification

FieldValue
Test case nameCold Boot Charging Station - Pending
Test case IdTC_B_02_CSMS
Use case Id(s)B02
Requirement(s)B02.FR.01, B02.FR.06
System under testCSMS
Functional blockB. Provisioning

Description

The booting mechanism allows a Charging Station to provide some general information about the Charging Station to the CSMS on startup AND it allows the Charging Station to request whether it is allowed to start sending other OCPP messages. The CSMS may respond to the BootNotificationRequest with status Pending. The Pending status can indicate that the CSMS wants to retrieve or set certain information on the Charging Station before it will accept the Charging Station.

Purpose

To verify whether the CSMS is able to accept the communications of a registered Charging Station.

Prerequisite(s)

The CSMS is configured to first respond to a BootNotificationRequest with status Pending.

Before (Preparations)

Configuration State:

  • N/a

Memory State:

  • N/a

Reusable State(s):

  • N/a

Main (Test scenario)

Charging StationCSMS
1. The OCTT sends a BootNotificationRequest; with reason PowerUp chargingStation.model <Configured model> chargingStation.vendorName <Configured vendorName>2. The CSMS responds with a BootNotificationResponse
Note(s):; - If the interval in the BootNotificationResponse equals 0, the OCTT will wait <Configured heartbeatInterval> seconds, before sending another BootNotificationRequest.; - If the interval in the BootNotificationResponse > 0, the OCTT will wait <Interval provided at the BootNotificationResponse> seconds, before sending another BootNotificationRequest.; - During this interval, the CSMS may send messages to retrieve information from the Charging Station (as described in use cases B06, B07, B08) or change its configuration by SetVariablesRequest (as described in use case B05). The OCTT will respond to these messages.
3. The OCTT sends a BootNotificationRequest; with reason PowerUp chargingStation.model <Configured model> chargingStation.vendorName <Configured vendorName>4. The CSMS responds with a BootNotificationResponse
5. The OCTT notifies the CSMS about the current state of all connectors.; Message: StatusNotificationRequest; with connectorStatus Available; Message: NotifyEventRequest; with trigger Delta actualValue "Available" component.name "Connector" variable.name "AvailabilityState"6. The CSMS responds accordingly.

Tool validations

Step 2:

Message: BootNotificationResponse

  • status Pending

Step 3:

Message: BootNotificationResponse

  • status Accepted

Post scenario validations

  • N/a