Use Case K17: Renegotiating a Charging Schedule

EVerest / libocpp

C++ implementation of the Open Charge Point Protocol

Apache License 2.0

80 stars 39 forks source link

[ ] K17.FR.01: Precondition EV triggers a renegotiation and sends new charging needs The Charging Station SHALL send a NotifyEVChargingNeedsRequest to the CSMS.
[ ] K17.FR.02: Precondition K17.FR.01. In response to a NotifyEVChargingNeedsRequest the CSMS SHALL send a NotifyEVChargingNeedsResponse.
[ ] K17.FR.03: Precondition K17.FR.02. If the CSMS is able to provide a charging schedule, it SHALL indicate this by setting the status field in the NotifyEVChargingNeedsResponse to 'Accepted'.
[ ] K17.FR.04: Precondition K17.FR.02. If the CSMS is not able to provide a charging schedule, it SHALL indicate this by setting the status field in the NotifyEVChargingNeedsResponse to 'Rejected'.
[ ] K17.FR.05: Precondition K17.FR.02 If the CSMS is able to provide a charging schedule; but needs processing time, it SHALL indicate this by setting the status field in the NotifyEVChargingNeedsResponse to 'Processing'.
[ ] K17.FR.06: A NotifyEVChargingNeedsRequest SHALL contain either ACChargingParameters or DCChargingParameters.
[ ] K17.FR.07: Precondition K17.FR.03 or K17.FR.05. The CSMS SHALL send a SetChargingProfileRequest with chargingProfilePurpose = TxProfile and at most three chargingSchedule and optional salesTariff elements, that each contain no more periods than specified by maxScheduleTuples in NotifyEVChargingNeedsRequest and by device model variable SmartChargingCtrlr.PeriodsPerSchedule.
[ ] K17.FR.08: Precondition K17.FR.01. The CSMS SHOULD send a SetChargingProfileRequest to the Charging Station within 60 seconds. Note: This is to satisfy the ISO 15118 ChargeParameterDiscoveryReq timeout.
[ ] K17.FR.09: Precondition K17.FR.07 AND EV returns a charging profile. Charging Station SHALL verify that provided charging profile is within boundaries of the ChargingSchedule from CSMS. Note: In ISO 15118 EV can sent its charging profile as part of PowerDeliveryReq.
[ ] K17.FR.10: Precondition K17.FR.09. Charging Station SHALL send the EV charging profile in a NotifyEVChargingScheduleRequest message to CSMS.
[ ] K17.FR.11: Precondition K17.FR.10 AND EV charging profile is within limits of CSMS ChargingSchedule. CSMS responds with NotifyEVChargingScheduleResponse with status Accepted to Charging Station. Note: Already checked by Charging Station, but CSMS does its own check.
[ ] K17.FR.12: Precondition K17.FR.10 AND EV charging profile is NOT within limits of CSMS ChargingSchedule. CSMS responds with NotifyEVChargingScheduleResponse with status Rejected to Charging Station.
[ ] K17.FR.13: Precondition K17.FR.12. CSMS starts new renegotiation as per use case K16.
[ ] K17.FR.14: Precondition K17.FR.11. The Charging Station SHOULD take the schedule from the NotifyEVChargingScheduleRequest into account when calculating the actual Composite schedule.
[ ] K17.FR.15: Precondition K17.FR.01 AND Charging Station is offline. The Charging Station SHALL use the TxDefaultProfile (if present) and generate a charging schedule within the limits of its composite schedule.
[ ] K17.FR.16: Precondition K17.FR.07 EV does not return a charging profile. Charging Station IS RECOMMENDED to return an EV charging profile as a chargingSchedule in a NotifyEVChargingScheduleRequest message to CSMS that matches the schedule that was selected by the EV (i.e. chargingSchedule.id = SAScheduleTupleId). Note: In ISO 15118-2 the EV charging profile and the selected schedule are returned as ChargingProfile and SAScheduleTupleId in PowerDeliveryReq.

[ ] K17.FR.01: Precondition EV triggers a renegotiation and sends new charging needs The Charging Station SHALL send a NotifyEVChargingNeedsRequest to the CSMS.
[ ] K17.FR.02: Precondition K17.FR.01. In response to a NotifyEVChargingNeedsRequest the CSMS SHALL send a NotifyEVChargingNeedsResponse.
[ ] K17.FR.03: Precondition K17.FR.02. If the CSMS is able to provide a charging schedule, it SHALL indicate this by setting the status field in the NotifyEVChargingNeedsResponse to 'Accepted'.
[ ] K17.FR.04: Precondition K17.FR.02. If the CSMS is not able to provide a charging schedule, it SHALL indicate this by setting the status field in the NotifyEVChargingNeedsResponse to 'Rejected'.
[ ] K17.FR.05: Precondition K17.FR.02 If the CSMS is able to provide a charging schedule; but needs processing time, it SHALL indicate this by setting the status field in the NotifyEVChargingNeedsResponse to 'Processing'.
[ ] K17.FR.06: A NotifyEVChargingNeedsRequest SHALL contain either ACChargingParameters or DCChargingParameters.
[ ] K17.FR.07: Precondition K17.FR.03 or K17.FR.05. The CSMS SHALL send a SetChargingProfileRequest with chargingProfilePurpose = TxProfile and at most three chargingSchedule and optional salesTariff elements, that each contain no more periods than specified by maxScheduleTuples in NotifyEVChargingNeedsRequest and by device model variable SmartChargingCtrlr.PeriodsPerSchedule.
[ ] K17.FR.08: Precondition K17.FR.01. The CSMS SHOULD send a SetChargingProfileRequest to the Charging Station within 60 seconds. Note: This is to satisfy the ISO 15118 ChargeParameterDiscoveryReq timeout.
[ ] K17.FR.09: Precondition K17.FR.07 AND EV returns a charging profile. Charging Station SHALL verify that provided charging profile is within boundaries of the ChargingSchedule from CSMS. Note: In ISO 15118 EV can sent its charging profile as part of PowerDeliveryReq.
[ ] K17.FR.10: Precondition K17.FR.09. Charging Station SHALL send the EV charging profile in a NotifyEVChargingScheduleRequest message to CSMS.
[ ] K17.FR.11: Precondition K17.FR.10 AND EV charging profile is within limits of CSMS ChargingSchedule. CSMS responds with NotifyEVChargingScheduleResponse with status Accepted to Charging Station. Note: Already checked by Charging Station, but CSMS does its own check.
[ ] K17.FR.12: Precondition K17.FR.10 AND EV charging profile is NOT within limits of CSMS ChargingSchedule. CSMS responds with NotifyEVChargingScheduleResponse with status Rejected to Charging Station.
[ ] K17.FR.13: Precondition K17.FR.12. CSMS starts new renegotiation as per use case K16.
[ ] K17.FR.14: Precondition K17.FR.11. The Charging Station SHOULD take the schedule from the NotifyEVChargingScheduleRequest into account when calculating the actual Composite schedule.
[ ] K17.FR.15: Precondition K17.FR.01 AND Charging Station is offline. The Charging Station SHALL use the TxDefaultProfile (if present) and generate a charging schedule within the limits of its composite schedule.
[ ] K17.FR.16: Precondition K17.FR.07 EV does not return a charging profile. Charging Station IS RECOMMENDED to return an EV charging profile as a chargingSchedule in a NotifyEVChargingScheduleRequest message to CSMS that matches the schedule that was selected by the EV (i.e. chargingSchedule.id = SAScheduleTupleId). Note: In ISO 15118-2 the EV charging profile and the selected schedule are returned as ChargingProfile and SAScheduleTupleId in PowerDeliveryReq.

EVerest / libocpp

Use Case K17: Renegotiating a Charging Schedule #316