nserway
commented
9 months ago - [ ] K15.FR.01: When the Charging Station receives charging needs from the EV The Charging Station SHALL send a
NotifyEVChargingNeedsRequestto the CSMS. - [ ] K15.FR.02: Precondition - K15.FR.01 In response to a
NotifyEVChargingNeedsRequestthe CSMS SHALL send aNotifyEVChargingNeedsResponse. - [ ] K15.FR.03: Precondition - K15.FR.02 If the CSMS is able to provide a charging schedule, it SHALL indicate this by setting the status field in the
NotifyEVChargingNeedsResponseto 'Accepted'. - [ ] K15.FR.04: Precondition - K15.FR.02 If the CSMS is not able to provide a charging schedule, it SHALL indicate this by setting the status field in the
NotifyEVChargingNeedsResponseto 'Rejected'. - [ ] K15.FR.05 K15.FR.02 If the CSMS is able to provide a charging schedule; but needs processing time, it SHAL indicate this by setting the status field in the
NotifyEVChargingNeedsResponseto 'Processing'. Note: The Charging Station does not have to wait for theSetChargingProfileRequest. CSMS will send it later and trigger a renegotiation as per use case K16. - [ ] K15.FR.06 A
NotifyEVChargingNeedsRequestSHALL contain either ACChargingParameters or DCChargingParameters. - [ ] K15.FR.07: Precondition - K15.FR.03 or K15.FR.05 The CSMS SHALL send a
SetChargingProfileRequestwith chargingProfilePurpose = TxProfile and a transactionId and at most three chargingSchedule and optional salesTariff elements, that each contain no more periods than specified by maxScheduleTuples inNotifyEVChargingNeedsRequestand by device model variable Smart ChargingCtrlr.PeriodsPerSchedule. Note: The Charging Station will calculate the composite schedule(s) for the EVSE (taking into account a ChargingStationMaxProfile or ChargingStationExternalConstraints if present) and will convert that to the SAScheduleList format for ISO 15118 - [ ] K15.FR.08: Precondition- K15.FR.01 The CSMS SHOULD send a
SetChargingProfileRequestto the Charging Station within 60 seconds. Note: This is to satisfy the ISO 15118 ChargeParameterDiscoveryReq timeout. - [ ] K15.FR.09: Precondition - K15.FR.07 AND EV returns a charging profile. Charging Station SHALL verify that provided charging profile is within boundaries of the ChargingSchedule from CSMS. In ISO 15118 EV can sent its charging profile as part of PowerDeliveryReq.
- [ ] K15.FR.10: Precondition K15.FR.09 Charging Station SHALL send the EV charging profile in a
NotifyEVChargingScheduleRequestmessage to CSMS. - [ ] K15.FR.11: Precondition K15.FR.10 AND EV charging profile is within limits of CSMS. ChargingSchedule CSMS responds with
NotifyEVChargingScheduleResponsewith status Accepted to Charging Station. Note: Already checked by Charging Station, but CSMS does its own check. - [ ] K15.FR.12: Precondition K15.FR.10 AND EV charging profile is NOT within limits of CSMS ChargingSchedule CSMS responds with
NotifyEVChargingScheduleResponsewith status Rejected to Charging Station. - [ ] K15.FR.13: Precondition K15.FR.12 CSMS starts new renegotiation as per use case K16.
- [ ] K15.FR.14: Precondition K15.FR.11 The Charging Station SHOULD take the schedule from the
NotifyEVChargingScheduleRequestinto account when calculating the actual Composite schedule. - [ ] K15.FR.15: Precondition K15.FR.03 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.
- [ ] K15.FR.16: Precondition K15.FR.07 It is RECOMMENDED to configure the Charging Station, such that a TransactionEvent with idToken has been sent prior to the
NotifyEVChargingNeedsRequestMessage, so that CSMS can take the user into account when creating a charging schedule. - [ ] K15.FR.17: Precondition When Charging Station receives a
SetChargingProfileRequestimmediately after the transaction has tarted and before it has sent theNotifyEVChargingNeedsRequestto CSMS. The Charging Station SHOULD respond withSetChargingProfileResponsewith status = Rejected and a statusInfo with reasonCode= InvalidMessageSequence. CSMS sent profile too early. It does not harm if CS accepts the charging profile instead of rejecting it, as long as it sends a charging profile again when it receives theNotifyEVChargingNeedsRequest. - [ ] K15.FR.18: Precondition K15.FR.03 OR K15.FR.05. CSMS IS RECOMMENDED to use only one chargingSchedule in a SetChargingProfileRequest. This ensures that there is no doubt about which schedule the EV will follow, even when no NotifyEVChargingScheduleRequest is received.
- [ ] K15.FR.19: Precondition K15.FR.07 AND 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) In ISO 15118-2 the EV charging profile and the selected schedule are returned as ChargingProfile and SAScheduleTupleId in PowerDeliveryReq.
Functional Requirements
[ ] K15.FR.01: When the Charging Station receives charging needs from the EV The Charging Station SHALL send a
NotifyEVChargingNeedsRequestto the CSMS.[ ] K15.FR.02: Precondition - K15.FR.01 In response to a
NotifyEVChargingNeedsRequestthe CSMS SHALL send aNotifyEVChargingNeedsResponse.[ ] K15.FR.03: Precondition - K15.FR.02 If the CSMS is able to provide a charging schedule, it SHALL indicate this by setting the status field in the
NotifyEVChargingNeedsResponseto 'Accepted'.[ ] K15.FR.04: Precondition - K15.FR.02 If the CSMS is not able to provide a charging schedule, it SHALL indicate this by setting the status field in the
NotifyEVChargingNeedsResponseto 'Rejected'.[ ] K15.FR.05 K15.FR.02 If the CSMS is able to provide a charging schedule; but needs processing time, it SHAL indicate this by setting the status field in the
NotifyEVChargingNeedsResponseto 'Processing'. Note: The Charging Station does not have to wait for theSetChargingProfileRequest. CSMS will send it later and trigger a renegotiation as per use case K16.[ ] K15.FR.06 A
NotifyEVChargingNeedsRequestSHALL contain either ACChargingParameters or DCChargingParameters.[ ] K15.FR.07: Precondition - K15.FR.03 or K15.FR.05 The CSMS SHALL send a
SetChargingProfileRequestwith chargingProfilePurpose = TxProfile and a transactionId and at most three chargingSchedule and optional salesTariff elements, that each contain no more periods than specified by maxScheduleTuples inNotifyEVChargingNeedsRequestand by device model variable Smart ChargingCtrlr.PeriodsPerSchedule. Note: The Charging Station will calculate the composite schedule(s) for the EVSE (taking into account a ChargingStationMaxProfile or ChargingStationExternalConstraints if present) and will convert that to the SAScheduleList format for ISO 15118[ ] K15.FR.08: Precondition- K15.FR.01 The CSMS SHOULD send a
SetChargingProfileRequestto the Charging Station within 60 seconds. Note: This is to satisfy the ISO 15118 ChargeParameterDiscoveryReq timeout.[ ] K15.FR.09: Precondition - K15.FR.07 AND EV returns a charging profile. Charging Station SHALL verify that provided charging profile is within boundaries of the ChargingSchedule from CSMS. In ISO 15118 EV can sent its charging profile as part of PowerDeliveryReq.
[ ] K15.FR.10: Precondition K15.FR.09 Charging Station SHALL send the EV charging profile in a
NotifyEVChargingScheduleRequestmessage to CSMS.[ ] K15.FR.11: Precondition K15.FR.10 AND EV charging profile is within limits of CSMS. ChargingSchedule CSMS responds with
NotifyEVChargingScheduleResponsewith status Accepted to Charging Station. Note: Already checked by Charging Station, but CSMS does its own check.[ ] K15.FR.12: Precondition K15.FR.10 AND EV charging profile is NOT within limits of CSMS ChargingSchedule CSMS responds with
NotifyEVChargingScheduleResponsewith status Rejected to Charging Station.[ ] K15.FR.13: Precondition K15.FR.12 CSMS starts new renegotiation as per use case K16.
[ ] K15.FR.14: Precondition K15.FR.11 The Charging Station SHOULD take the schedule from the
NotifyEVChargingScheduleRequestinto account when calculating the actual Composite schedule.[ ] K15.FR.15: Precondition K15.FR.03 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.
[ ] K15.FR.16: Precondition K15.FR.07 It is RECOMMENDED to configure the Charging Station, such that a TransactionEvent with idToken has been sent prior to the
NotifyEVChargingNeedsRequestMessage, so that CSMS can take the user into account when creating a charging schedule.[ ] K15.FR.17: Precondition When Charging Station receives a
SetChargingProfileRequestimmediately after the transaction has tarted and before it has sent theNotifyEVChargingNeedsRequestto CSMS. The Charging Station SHOULD respond withSetChargingProfileResponsewith status = Rejected and a statusInfo with reasonCode= InvalidMessageSequence. CSMS sent profile too early. It does not harm if CS accepts the charging profile instead of rejecting it, as long as it sends a charging profile again when it receives theNotifyEVChargingNeedsRequest.[ ] K15.FR.18: Precondition K15.FR.03 OR K15.FR.05. CSMS IS RECOMMENDED to use only one chargingSchedule in a SetChargingProfileRequest. This ensures that there is no doubt about which schedule the EV will follow, even when no NotifyEVChargingScheduleRequest is received.
[ ] K15.FR.19: Precondition K15.FR.07 AND 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) In ISO 15118-2 the EV charging profile and the selected schedule are returned as ChargingProfile and SAScheduleTupleId in PowerDeliveryReq.