Skip to content
Documentation Menu

TC_081_CS — Secure Firmware Update - Invalid Signature

TC_081_CS — Secure Firmware Update - Invalid Signature

Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 105.

Identification

FieldValue
Test case nameSecure Firmware Update - Invalid Signature
Test case IdTC_081_CS
System under testCharge Point

Description

The Charge Point validates the Signature and deems it invalid.

Purpose

To check whether the Charge Point validates the signature.

Prerequisite(s)

  • The Charge Point supports the FirmwareManagement feature profile AND
  • The Charge Point supports a security profile AND
  • A firmware is prepared on a server (For example ftp) AND
  • The tester configured the signature calculated over the firmware at the 'Invalid signature' test data field.

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 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]; [Step 7 through 10 can be sent in any order.]; 7. The Charge Point sends a SignedFirmwareStatusNotification.req.8. The Central System responds with a SignedFirmwareStatusNotification.conf.
9. The Charge Point sends a SecurityEventNotification.req10. The Central System responds with a SecurityEventNotification.conf

Tool validation(s)

Charge Point side:

Step 2:

(Message: SignedUpdateFirmware.conf) The status is Accepted

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

Step 9:

(Message: SecurityEventNotification.req) The type is InvalidFirmwareSignature

Central System side:

Step 1:

(Message: SignedUpdateFirmware.req) The firmware.location is <Configured firmware location> 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:

  • N/a