TC_067_CS — Clear Charging Profile

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

Identification

Field	Value
Test case name	Clear Charging Profile
Test case Id	TC_067_CS
System under test	Charge Point

Description

The Central Systems sets charging profiles and clears it.

Purpose

To check whether the Charge Point is able to clear charging profiles.

Prerequisite(s)

The Charge Point supports the Smart Charging feature profile.

Before (Preparations)

Configuration State(s):

Memory State(s):

F SetChargingProfile with ChargingProfile 1: chargingProfilePurpose is TxDefaultProfile chargingProfileKind should be Absolute stackLevel should be 1 connectorId<Configured connectorId> startSchedule<current dateTime - <Configured max time deviation> seconds> numberPhases<Configured numberPhases> ChargingSchedule: duration<400 + <Configured max time deviation> seconds> chargingRateUnit<Configured chargingRateUnit>
Note: If <Configured chargingRateUnit> is W, then the limit field will be multiplied by 1000. startPeriod0,60,200, limit6,8,10

Reusable State(s):

Scenario Detail(s)

Charge Point (SUT)	Central System (Tool)
2. The Charge Point responds with a ClearChargingProfile.conf	1. The Central System sends a ClearChargingProfile.req
4. The Charge Point responds with a GetCompositeSchedule.conf	3. The Central System sends a GetCompositeSchedule.req
6. The Charge Point responds with a ClearChargingProfile.conf	5. The Central System sends a ClearChargingProfile.req
8. The Charge Point responds with a GetCompositeSchedule.conf	7. The Central System sends a GetCompositeSchedule.req
10. The Charge Point responds with a ClearChargingProfile.conf	9. The Central System sends a ClearChargingProfile.req
12. The Charge Point responds with a GetCompositeSchedule.conf	11. The Central System sends a GetCompositeSchedule.req

Tool validation(s)

Charge Point side:

Step 2 / 6 / 10:

(Message: ClearChargingProfile.conf)

The status is Accepted

Step 4:

(Message: GetCompositeSchedule.conf) statusAccepted connectorId is <Configured ConnectorId> ChargingSchedule: duAration350 chargingRateUnit<Configured chargingRateUnit> scheduleStart<The time the GetCompositeSchedule.req was transmitted +/- <Configured max time deviation>> Note: If <Configured chargingRateUnit> is W, then the limit field will be multiplied by 1000. R Note: The period of time between the scheduleStart from the SetChargingProfile.req with ChargingProfile 2 and the scheduleStart from the GetCompositeSchedule.conf is called x. startPeriod0, limit7 startPeriod(100 - x), limit9

Step 8:

(Message: GetCompositeSchedule.conf) statusAccepted connectorId is <Configured ConnectorId> ChargingSchedule: duration350 chargingRateUnit<Configured chargingRateUnit> scheduleStart<The time the GetCompositeSchedule.req was transmitted +/- <Configured max time deviation>> Note: If <Configured chargingRateUnit> is W, then the limit field will be multiplied by 1000. TNote: The period of time between the scheduleStart from the SetChargingProfile.req with ChargingProfile 3 and the scheduleStart from the GetCompositeSchedule.conf is called y. startPeriod0, limit11 startPeriod(200 - y), limit12

Step 12:

(Message: GetCompositeSchedule.conf) statusAccepted connectorId is <Configured ConnectorId> ChargingSchedule: duration350 chargingRateUnit<Configured chargingRateUnit> scheduleStart<The time the GetCompositeSchedule.req was transmitted +/- <Configured max time deviation>> Note: If <Configured chargingRateUnit> is W, then the limit field will be multiplied by 1000. startPeriod0, limit<The local limit of the Charging Station>

Central System side:

Step 1:

(Message: ClearChargingProfile.req)

The id is the chargingProfileId from the first ChargingProfile.
All other fields are omitted.

Step 5:

(Message: ClearChargingProfile.req)

The chargingProfilePurpose is the purpose from the second ChargingProfile.
The stackLevel is the stackLevel from the second ChargingProfile.
All other fields are omitted.

Step 9:

(Message: ClearChargingProfile.req)

All fields are omitted.

Expected result(s) / behaviour

Charge Point side:

Central System side: