TC_P_01_CS — Data Transfer to the Charging Station - Rejected / Unknown VendorId / Unknown MessageId
TC_P_01_CS — Data Transfer to the Charging Station - 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 297.
Identification
| Field | Value |
|---|---|
| Test case name | Data Transfer to the Charging Station - Rejected / Unknown VendorId / Unknown MessageId |
| Test case Id | TC_P_01_CS |
| Use case Id(s) | P01 |
| Requirement(s) | P01.FR.05, P01.FR.06 |
| System under test | Charging Station |
| Functional block | P. DataTransfer |
Description
The DataTransfer message to send information for functions that are not supported by OCPP.
Purpose
To verify whether the Charging Station is able to handle receiving a DataTransferRequest, even if it does not support any vendor-specific implementations.
Prerequisite(s)
The configured vendorId should not be implemented and the configured messageId should be unused.
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 DataTransferResponse | 1. The OCTT sends a DataTransferRequest; with vendorId org.openchargealliance.octt messageId <Configured messageId> |
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