TC_083_CS — Upgrade security profile

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

Identification

Field	Value
Test case name	Upgrade security profile
Test case Id	TC_083_CS
System under test	Charge Point

Description

The Central System can upgrade the connection using a higher Security Profile, the Central System can send a new value for the SecurityProfile Configuration key.

Purpose

To check if the Charge Point is able to upgrade the Security Profile.

Prerequisite(s)

The Charge Point is connected with SecurityProfile 1 or 2.

Before (Preparations)

Configuration State(s):

Memory State(s):

CertificateInstalled if SecurityProfile is 1.
RenewChargePointCertificate if SecurityProfile is 2.

Reusable State(s):

Scenario Detail(s)

Charge Point (SUT)	Central System (Tool)
2. The Charge Point responds with a ChangeConfiguration.conf	1. The Central System sends a ChangeConfiguration.req
4. The Charge Point responds with a Reset.conf	3. The Central System sends a Reset.req
5. The Charge Point sends a BootNotification.req	6. The Central System responds with a BootNotification.conf
[Send per connector and connectorId=0]; 7. The Charge Point sends a StatusNotification.req	8. The Central System responds with a StatusNotification.conf
The following steps are only executed when this testcase is upgrading from Security Profile 1 to Security Profile 2.
16. The Charge Point does NOT reconnect to the Central System using Security Profile 1.	15. The Central System closes the connection and restarts the WebSocket server using Security profile 1 and waits the <Configured long operation timeout>.
18. The Charge Point reconnects to the Central System using Security Profile 2.	17. The Central System restarts the WebSocket server using Security Profile 2.

Tool validation(s)

Charge Point side:

Step 2:

(Message: ChangeConfiguration.conf)

status should be Accepted or RebootRequired

Step 4:

(Message: Reset.conf)

status should be Accepted

Step 7:

(Message: StatusNotification.req)

status should be Available

Central System side:

Step 1:

(Message: ChangeConfiguration.req)

key is SecurityProfile
value is <One level higher than the configured security profile>

Step 3:

(Message: Reset.req)

type is Hard

Step 6:

(Message: BootNotification.conf)

status is Accepted

Expected result(s) / behaviour

Charge Point side:

Central System side: