TC_F_18_CS — Trigger message - FirmwareStatusNotification - Idle
TC_F_18_CS — Trigger message - FirmwareStatusNotification - Idle
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block F. Remote Control, page 190.
Identification
| Field | Value |
|---|---|
| Test case name | Trigger message - FirmwareStatusNotification - Idle |
| Test case Id | TC_F_18_CS |
| Use case Id(s) | F06 |
| Requirement(s) | F06.FR.04,F06.FR.05,F06.FR.10,F06.FR.16,L01.FR.25 |
| 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 FirmwareStatusNotificationRequest with status Idle, after receiving a TriggerMessageRequest while NOT downloading a firmware file.
Prerequisite(s)
The Charging Station supports sending FirmwareStatusNotifications triggered by a TriggerMessageRequest.
Before (Preparations)
Configuration State:
- N/a
Memory State:
- N/a
Reusable State(s):
- N/a
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 2. The Charging Station responds with a TriggerMessageResponse | 1. The OCTT sends a TriggerMessageRequest; With requestedMessage FirmwareStatusNotification |
| 3. The Charging Station sends a FirmwareStatusNotificationRequest | 4. The OCTT responds with a FirmwareStatusNotificationResponse |
Tool validations
Step 2:
Message: TriggerMessageResponse
- status must be Accepted
Step 3:
Message: FirmwareStatusNotificationRequest
- status must be Idle
Post scenario validations
- N/a