Skip to content
Documentation Menu

TC_B_47_CS — Migrate to new ConnectionProfile - Fallback after NetworkProfileConnectionAttempts per

TC_B_47_CS — Migrate to new ConnectionProfile - Fallback after NetworkProfileConnectionAttempts per

NetworkConfigurationPriority failed - New CSMS Root - New CSMS

Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block B. Provisioning, page 70.

Identification

FieldValue
Test case nameMigrate to new ConnectionProfile - Fallback after NetworkProfileConnectionAttempts per; NetworkConfigurationPriority failed - New CSMS Root - New CSMS
Test case IdTC_B_47_CS
Use case Id(s)B09,B10,M05
Requirement(s)B10.FR.07,M05.FR.15,M05.FR.16
System under testCharging Station
Functional blockB. Provisioning

Description

The CSMS updates the connection details on the Charging Station. For instance in preparation of a migration to a new CSMS.

Purpose

To verify if the Charging Station is able to correctly handle the fallback mechanism in the case it fails to connect to the other CSMS.

Prerequisite(s)

  • The Charging Station supports AS-2: AdditionalRootCertificateCheck.
  • Configured (new) CSMS Root certificate 2 must be signed by the configured (old) CSMS Root certificate 2.
  • At least two configuration slots for networkConnectionProfiles must be supported

Before (Preparations)

Configuration State:

  • OCPPCommCtrlr.NetworkProfileConnectionAttempts is 1

Memory State:

  • CertificateInstalled for certificateType CSMSRootCertificate and certificate <Configured (new) CSMS Root certificate 2>

Reusable State(s):

  • N/a

Main (Test scenario)

Charging StationCSMS
2. The Charging Station responds with a SetNetworkProfileResponse1. The OCTT sends a SetNetworkProfileRequest; with configurationSlot is <Configured configurationSlot> or <Configured configurationSlot> depending on which one is already in use; - connectionData.messageTimeout <Configured messageTimeout2>; - connectionData.ocppCsmsUrl <ocppCsmsUrl that is not currently active>; - connectionData.ocppInterface <Configured ocppInterface2>; - connectionData.ocppVersion OCPP20; - connectionData.securityProfile <Configured securityProfile2>
4. The Charging Station responds with a SetVariablesResponse3. The OCTT sends a SetVariablesRequest; with variable.name is "NetworkConfigurationPriority" component.name is "OCPPCommCtrlr" attributeValue is <Configured configurationSlot2>
6. The Charging Station responds with a ResetResponse5. The OCTT sends a ResetRequest; with type OnIdle
8. During the TLS handshake the Charging Station validates the CSMS certificate.; Note(s):; - This connection attempt fails, because the Charging Station will use the new CSMS Root certificate to validate the CSMS certificate.7. During the TLS handshake the OCTT provides a CSMS certificate which is signed by the <Configured old CSMS Root certificate>
9. The Charging Station switches back to the previous networkprofile configuration and validates the CSMS certificate, using the (fallback) CSMS Root certificate.; Note(s):; - This connection attempt succeeds, because the Charging Station will now use the (old) CSMS Root certificate to validate the CSMS certificate.
10. Execute Reusable State Booted
12. The Charging Station responds with a GetInstalledCertificateIdsResponse11. The OCTT sends a GetInstalledCertificateIdsRequest; with certificateType is CSMSRootCertificate

Tool validations

Step 6:

Message ResetResponse

  • status Accepted

Step 12:

Message: GetInstalledCertificateIdsResponse

  • status must be Accepted
  • certificateHashDataChain must contain an entry with following values:
  • certificateType is CSMSRootCertificate
  • certificateHashData contains <HashData from configured old CSMS Root certificate>

Post scenario validations

  • N/a