TC_P_02_CSMS — Data Transfer to the CSMS - Rejected / Unknown VendorId / Unknown MessageId
TC_P_02_CSMS — Data Transfer to the CSMS - Rejected / Unknown VendorId / Unknown MessageId
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block P. DataTransfer, page 480.
Identification
| Field | Value |
|---|---|
| Test case name | Data Transfer to the CSMS - Rejected / Unknown VendorId / Unknown MessageId |
| Test case Id | TC_P_02_CSMS |
| Use case Id(s) | P02 |
| Requirement(s) | P02.FR.06, P02.FR.07 |
| System under test | CSMS |
| Functional block | P. DataTransfer |
Description
The DataTransfer message to send information for functions that are not supported by OCPP.
Purpose
To verify whether the CSMS is able to handle receiving a DataTransferRequest, even if it does not support any vendor-specific implementations.
Prerequisite(s)
N/a
Before (Preparations)
Configuration State:
- N/a
Memory State:
- N/a
Reusable State(s):
- N/a
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 1. The OCTT sends a DataTransferRequest; with vendorId <Configured vendorId> messageId <Configured messageId> | 2. The CSMS responds with a DataTransferResponse |
Tool validations
Step 2:
Message: DataTransferResponse
- status must be UnknownVendorId OR UnknownMessageId OR Rejected (Rejected will also be allowed, because there are implementers that like to just reject the message when the Charging Station does not support any vendor-specific features.
Post scenario validations
- N/a