TC_F_24_CS — Trigger message - StatusNotification - Specific EVSE - Occupied
TC_F_24_CS — Trigger message - StatusNotification - Specific EVSE - Occupied
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block F. Remote Control, page 194.
Identification
| Field | Value |
|---|---|
| Test case name | Trigger message - StatusNotification - Specific EVSE - Occupied |
| Test case Id | TC_F_24_CS |
| Use case Id(s) | F06 |
| Requirement(s) | F06.FR.02,F06.FR.04,F06.FR.05,F06.FR.10 |
| System under test | Charging Station |
| Functional block | F. Remote Control |
Description
The CSMS can request a Charging Station to send Charging Station-initiated messages. In the request the CSMS indicates which message it wishes to receive.
Purpose
To verify if the Charging Station is able to send a StatusNotificationRequest message for a specific occupied EVSE/Connector, after receiving a TriggerMessageRequest message.
Prerequisite(s)
The Charging Station supports sending StatusNotifications triggered by a TriggerMessageRequest.
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 TriggerMessageResponse | 1. The OCTT sends a TriggerMessageRequest; With requestedMessage StatusNotification evse.id <Configured evseId> evse.connectorId <Configured connectorId> |
| 3. The Charging Station notifies the CSMS about the current state of the connector. | 4. The OCTT responds accordingly. |
Tool validations
Step 2:
Message: TriggerMessageResponse
- status must be Accepted
Step 3:
Message: StatusNotificationRequest
- connectorStatus Occupied Message: NotifyEventRequest
- eventData[0].trigger Delta
- eventData[0].actualValue "Occupied"
- eventData[0].component.name "Connector"
- eventData[0].variable.name "AvailabilityState"
Post scenario validations
- N/a