Skip to content
Documentation Menu

TC_F_23_CSMS — Trigger message - StatusNotification - Specific EVSE - Available

TC_F_23_CSMS — Trigger message - StatusNotification - Specific EVSE - Available

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

Identification

FieldValue
Test case nameTrigger message - StatusNotification - Specific EVSE - Available
Test case IdTC_F_23_CSMS
Use case Id(s)F06
Requirement(s)F06.FR.01,F06.FR.02,F06.FR.13
System under testCSMS
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 CSMS is able to trigger the Charging Station to send a StatusNotificationRequest for a specific available EVSE, using a TriggerMessageRequest.

Prerequisite(s)

N/a

Before (Preparations)

Configuration State:

  • N/a

Memory State:

  • N/a

Reusable State(s):

  • N/a

Main (Test scenario)

Charging StationCSMS
2. The OCTT responds with a TriggerMessageResponse; with status Accepted1. The CSMS sends a TriggerMessageRequest
3. The OCTT notifies the CSMS about the current state of the connector.; Message: StatusNotificationRequest; - connectorStatus Available; - evseId <Configured evseId>; - connectorId <Configured connectorId>; Message: NotifyEventRequest; - trigger Delta; - actualValue "Available"; - component.name "Connector"; - component.evse.id <Configured evseId>; - component.evse.connectorid <Configured connectorId>; - variable.name "AvailabilityState"4. The CSMS responds accordingly.

Tool validations

Step 1:

Message: TriggerMessageRequest

  • requestedMessage must be StatusNotification
  • evse.id must be <Configured evseId>

Post scenario validations

  • N/a