Use Case K11: Set / Update External Charging Limit With Ongoing Transaction

EVerest / libocpp

C++ implementation of the Open Charge Point Protocol

Apache License 2.0

83 stars 44 forks source link

Scenario

External control system sends charging limit/schedule to Charging Station.
Optional: Charging Station calculates new charging schedule.
Charging Station adjusts the charging speed of the ongoing transaction(s).
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.
The CSMS responds with NotifyChargingLimitResponse to the Charging Station.
If the charging rate changes by more than: LimitChangeSignificance, the Charging Station sends a TransactionEventRequest message to inform the CSMS.
The CSMS responds with TransactionEventResponse to the Charging Station.

Functional Requirements

[ ] K11.FR.01: When an external charging limit/schedule is received during an ongoing transaction, the Charging Station SHALL NOT charge the ongoing transaction faster than this given limit/schedule.
[ ] K11.FR.02: When K11.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.
[ ] K11.FR.03: When K11.FR.02 AND EnableNotifyCharging LimitWithSchedules is true, The NotifyChargingLimitRequest SHALL contain the charging limits/schedules as set by the external system.
[ ] K11.FR.04: When K11.FR.01 AND Charging rate changed by more than: LimitChangeSignificance, the Charging Station SHALL send a TransactionEventRequest message to the CSMS with trigger = ChargingRateChanged
[ ] K11.FR.05: When K11.FR.02, the Charging Station SHALL NOT set the 'chargingLimitSource' to CSO in the 'NotifyChargingLimitRequest'.
[ ] K11.FR.06: 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 (future) charging profile.

Scenario

External control system sends charging limit/schedule to Charging Station.

Optional: Charging Station calculates new charging schedule.

Charging Station adjusts the charging speed of the ongoing transaction(s).

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.

The CSMS responds with NotifyChargingLimitResponse to the Charging Station.

If the charging rate changes by more than: LimitChangeSignificance, the Charging Station sends a TransactionEventRequest message to inform the CSMS.

The CSMS responds with TransactionEventResponse to the Charging Station.

Functional Requirements

[ ] K11.FR.01: When an external charging limit/schedule is received during an ongoing transaction, the Charging Station SHALL NOT charge the ongoing transaction faster than this given limit/schedule.

[ ] K11.FR.02: When K11.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.

[ ] K11.FR.03: When K11.FR.02 AND EnableNotifyCharging LimitWithSchedules is true, The NotifyChargingLimitRequest SHALL contain the charging limits/schedules as set by the external system.

[ ] K11.FR.04: When K11.FR.01 AND Charging rate changed by more than: LimitChangeSignificance, the Charging Station SHALL send a TransactionEventRequest message to the CSMS with trigger = ChargingRateChanged

[ ] K11.FR.05: When K11.FR.02, the Charging Station SHALL NOT set the 'chargingLimitSource' to CSO in the 'NotifyChargingLimitRequest'.

[ ] K11.FR.06: 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 (future) charging profile.

EVerest / libocpp