TC_067_CSMS — Clear Charging Profile
TC_067_CSMS — Clear Charging Profile
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Central System, page 176.
Identification
| Field | Value |
|---|---|
| Test case name | Clear Charging Profile |
| Test case Id | TC_067_CSMS |
| System under test | Central System |
Description
The Central Systems sets a Charging Profile and clears it.
Purpose
To check whether the Central System can clear a charging profile.
Prerequisite(s)
The Central System supports the Smart Charging feature profile.
Before (Preparations)
Configuration State(s):
- N/a
Memory State(s):
- N/a
Reusable State(s):
- Charging
Scenario Detail(s)
| Charge Point (SUT) | Central System (Tool) |
|---|---|
| Manual Action: Set three different charging profiles. Steps 1-2 are therefor repeated three times. | |
| 2. The Charge Point responds with a SetChargingProfile.conf | 1. The Central System sends a SetChargingProfile.req |
| Manual Action: Clear a charging profile based on ID. | |
| 4. The Charge Point responds with a ClearChargingProfile.conf | 3. The Central System sends a ClearChargingProfile.req |
| Manual Action: Clear a charging profile based on criteria. | |
| 6. The Charge Point responds with a ClearChargingProfile.conf | 5. The Central System sends a ClearChargingProfile.req |
| Manual Action: Clear all remaining charging profiles. | |
| 8. The Charge Point responds with a ClearChargingProfile.conf | 7. The Central System sends a ClearChargingProfile.req |
Tool validation(s)
Charge Point side:
Step 2:
(Message: SetChargingProfile.conf)
- The status is Accepted
Step 4/6/8:
(Message: ClearChargingProfile.conf)
- The status is Accepted
Central System side:
Step 1:
(Message: SetChargingProfile.req) Charging profile 1:
- The connectorId should be 0
- The chargingProfilePurpose should be ChargePointMaxProfile
- The stackLevel should be <Configured Stack Level>
- The transactionId should be <Omitted>
- The chargingProfileId should be <Different than the chargingProfileId from profile 2 and 3> Charging profile 2:
- The connectorId should be <Configured ConnectorId>
- The chargingProfilePurpose should be TxDefaultProfile
- The stackLevel should be <Configured Stack Level>
- The transactionId should be <Omitted>
- The chargingProfileId should be <Different than the chargingProfileId from profile 1 and 3> Charging profile 3:
- The connectorId should be <Configured ConnectorId>
- The chargingProfilePurpose should be TxProfile
- The stackLevel should be <Configured Stack Level>
- The transactionId should be <Generated transactionId by Central System>
- The chargingProfileId should be <Different than the chargingProfileId from profile 1 and 2>
Step 3:
(Message: ClearChargingProfile.req)
- The id should be <Generated Id from charging profile 1>
- The connectorId, chargingProfilePurpose and stackLevel fields should be omitted.
Step 5:
(Message: ClearChargingProfile.req)
- The id should be omitted
- The connectorId should be <Configured ConnectorId>
- The chargingProfilePurpose should be TxDefaultProfile
- The stackLevel should be <Configured Stack Level>
Step 7:
(Message: ClearChargingProfile.req)
- All fields should be omitted.
Expected result(s) / behaviour
Charge Point side:
- N/a
Central System side:
The Central System was able to clear the ChargingProfile of the Charge Point.