TC_062_CS — Data Transfer to a Charge Point
TC_062_CS — Data Transfer to a Charge Point
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 95.
Identification
| Field | Value |
|---|---|
| Test case name | Data Transfer to a Charge Point |
| Test case Id | TC_062_CS |
| System under test | Charge Point |
Description
The Central System sends a vendor specific message to a Charge Point.
Purpose
To check whether the Charge Point can reject vendor specific messages.
Prerequisite(s)
The Charge Point does not support DataTransfer for a specific vendorId.
Before (Preparations)
Configuration State(s):
- N/a
Memory State(s):
- N/a
Reusable State(s):
- N/a
Scenario Detail(s)
| Charge Point (SUT) | Central System (Tool) |
|---|---|
| 2. The Charge Point responds with a DataTransfer.conf message. | 1. The Central System sends a DataTransfer.req message with a specific vendorId to the Charge Point. |
Tool validation(s)
Charge Point side:
Step 2:
(Message: DataTransfer.conf) The status is Rejected OR UnknownMessageId OR UnknownVendorId Note: The statusAccepted is allowed, but the vendor should be warned about this behaviour.
Central System side:
- N/a
Expected result(s) / behaviour
Charge Point side:
The Charge Point does not accept the DataTransfer.req message.
Central System side:
- N/a