TC_081_CSMS — Secure Firmware Update - Invalid Signature
TC_081_CSMS — Secure Firmware Update - Invalid Signature
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Central System, page 190.
Identification
| Field | Value |
|---|---|
| Test case name | Secure Firmware Update - Invalid Signature |
| Test case Id | TC_081_CSMS |
| System under test | Central System |
Description
The Charge Point validates the Signature and deems it invalid.
Purpose
To check whether the Central System is able to handle messages from a Charge Point when it reports that the signature is invalid.
Prerequisite(s)
- The Central System supports the Firmware Management feature profile AND
- The Central System supports a security profile.
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 sends a SignedUpdateFirmware.conf | 1. The Central System sends a SignedUpdateFirmware.req |
| [The Charge Point starts downloading the firmware]; 3. The Charge Point sends a SignedFirmwareStatusNotification.req | 4. The Central System responds with a SignedFirmwareStatusNotification.conf |
| [The Charge Point has finished downloading the firmware]; 5. The Charge Point sends a SignedFirmwareStatusNotification.req | 6. The Central System responds with a SignedFirmwareStatusNotification.conf |
| [The Charge Point verifies the signature and deems it invalid]; 7. The Charge Point sends a SignedFirmwareStatusNotification.req | 8. The Central System responds with a SignedFirmwareStatusNotification.conf |
Tool validation(s)
Charge Point side:
Step 3:
(Message: SignedFirmwareStatusNotification.req) The status is Downloading
Step 5:
(Message: SignedFirmwareStatusNotification.req) The status is Downloaded
Step 7:
(Message: SignedFirmwareStatusNotification.req) The status is InvalidSignature
Central System side:
Step 1:
(Message: SignedUpdateFirmware.req) The firmware.location is <Firmware Download URL from test data> The firmware.signature is <An invalid signature.>
Expected result(s) / behaviour
Charge Point side:
The Charge Point rejects the firmware, because of an invalid signature.
Central System side:
The Central System receives and responds to the FirmwareStatusNotification messages.