Skip to content
Documentation Menu

TC_F_17_CS — Trigger message - FirmwareStatusNotification - Specific EVSE not relevant

TC_F_17_CS — Trigger message - FirmwareStatusNotification - Specific EVSE not relevant

Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block F. Remote Control, page 189.

Identification

FieldValue
Test case nameTrigger message - FirmwareStatusNotification - Specific EVSE not relevant
Test case IdTC_F_17_CS
Use case Id(s)F06
Requirement(s)F06.FR.03,F06.FR.04,F06.FR.05,F06.FR.10
System under testCharging Station
Functional blockF. 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, after receiving a TriggerMessageRequest even when the CSMS an evseId which is not relevant for the requestedMessage FirmwareStatusNotification.

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 StationCSMS
2. The Charging Station responds with a TriggerMessageResponse1. The OCTT sends a TriggerMessageRequest; With requestedMessage FirmwareStatusNotification evse.id is <Configured evseId>
3. The Charging Station sends a FirmwareStatusNotificationRequest4. 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