Use Case K12: Set / Update External Charging Limit Without Ongoing Transaction

[drmrd]

No description provided.

[Giavotto]

Scenario

1. External Control System sends a charging limit to Charging Station (not during a transaction).
2. Optional: Charging Station calculates new charging schedule.
3. Charging Station adjusts the charging speed.
4. If the charging limit changed by more than: LimitChangeSignificance, the Charging
   Station sends a NotifyChargingLimitRequest message to CSMS with optionally the set charging
   limit/schedule.
5. The CSMS responds with a NotifyChargingLimitResponse to the Charging Station.

Functional Requirements

• K12.FR.01: When an external charging limit/schedule is received while no transactions are ongoing, the total load of all EVSEs SHALL NOT exceed this given limit. (This may not apply)
• K12.FR.02: When K12.FR.01 AND Charging limit changed by more than: LimitChangeSignificance, the Charging Station SHALL inform the CSMS of the new charging limit/schedule imposed by the external system by sending a NotifyChargingLimitRequest.
• K12.FR.03: When K12.FR.02 AND EnableNotifyChargingLimitWithSchedules is true, the NotifyChargingLimitRequest SHALL contain the charging limit/schedule as set by the external system.
• K12.FR.04: When K12.FR.02, the Charging Station SHALL NOT set the chargingLimitSource to CSO in the NotifyChargingLimitRequest.
• K12.FR.05: When an external charging limit/schedule is received, the Charging Station SHALL use purpose ChargingStationExternalConstraints when reporting about this limit (e.g. in a ReportChargingProfilesRequest).
  • It is RECOMMENDED to use negative values for the id of a ChargingStationExternalConstraints profile, to minimize the risk of a clash with an id that CSMS might use for a