Charging Profiles

OCPI 2.2.1

By Abhishek Uniyal · Updated

Charging Profiles in OCPI 2.2.1

A Charging Profile requests a maximum limit over time for an ongoing Session. It does not promise that the EV will charge at that limit. This relative profile limits current to 16 A per phase; local limits and the EV can reduce the actual rate.

Sources (5)
charging_profile · ChargingProfile · cardinality 1: Contains limits for the available power or current over time. response_url · URL · cardinality 1: URL that the ChargingProfileResult POST should be sent to. This URL might contain a unique ID to be able to distinguish between GET ActiveChargingProfile requests.OCPI 2.2.1 specification · #mod_charging_profiles_set_charging_profile_objectstart_date_time · DateTime · cardinality ?: Starting point of an absolute profile. If absent the profile will be relative to start of charging. duration · int · cardinality ?: Duration of the charging profile in seconds. If the duration is left empty, the last period will continue indefinitely or until end of the transaction in case start_date_time is absent. charging_rate_unit · ChargingRateUnit · cardinality 1: The unit of measure. min_charging_rate · number · cardinality ?: Minimum charging rate supported by the EV. The unit of measure is defined by the chargingRateUnit. This parameter is intended to be used by a local smart charging algorithm to optimize the power allocation for in the case a charging process is inefficient at lower charging rates. Accepts at most one digit fraction (e.g. 8.1) charging_profile_period · ChargingProfilePeriod · cardinality *: List of ChargingProfilePeriod elements defining maximum power or current usage over time.OCPI 2.2.1 specification · #mod_charging_profiles_charging_profile_classstart_period · int · cardinality 1: Start of the period, in seconds from the start of profile. The value of StartPeriod also defines the stop time of the previous period. limit · number · cardinality 1: Charging rate limit during the profile period, in the applicable chargingRateUnit, for example in Amperes (A) or Watts (W). Accepts at most one digit fraction (e.g. 8.1).OCPI 2.2.1 specification · #mod_charging_profiles_charging_profile_period_class"NOTE: Charging Profiles set via this module are no guarantee that the EV will charge with the exact given limit, it is a maximum limit, not a target. A lot of factors influence the charging speed. The EV might not take the amount of energy that the EVSE is willing to provide to it, the battery might be too warm or almost full. A single phase cable might be used on a three phase Charge Point. There can be local energy limits (load balancing between EVSEs on a relative small energy connection to a group of EVSEs) that might limit the energy offered by the EVSE to the EV even further."OCPI 2.2.1 specification · #mod_charging_profiles_moduleW: Watts (power) This is the total allowed charging power. It is usually more convenient to use this for DC charging. A: Amperes (current) The amount of Ampere per phase, not the sum of all phases. It is usually more convenient to use this for AC charging.OCPI 2.2.1 specification · #mod_charging_profiles_chargingrateunit

Example payload · set-relative-current-profile

{
  "charging_profile": {
    "charging_rate_unit": "A",
    "charging_profile_period": [
      {
        "start_period": 0,
        "limit": 16
      }
    ]
  },
  "response_url": "https://sender.example.invalid/results/example-profile"
}

Which endpoints does this module define?

These paths illustrate the requests. Use the URLs advertised by your partner, replace the placeholders and choose the matching interface. A listed method does not establish that this site's simulator implements it.

CPO · receiver interface

  • Gets the ActiveChargingProfile for a specific charging session.

    GET
    /ocpi/2.2.1/chargingprofiles/{session_id}?duration={duration}&response_url={response_url}
  • Creates/updates a ChargingProfile for a specific charging session.

    PUT
    /ocpi/2.2.1/chargingprofiles/{session_id}
  • Cancels an existing ChargingProfile for a specific charging session.

    DELETE
    /ocpi/2.2.1/chargingprofiles/{session_id}?response_url={response_url}
Source
Method: Description GET: Gets the ActiveChargingProfile for a specific charging session. POST: n/a PUT: Creates/updates a ChargingProfile for a specific charging session. PATCH: n/a DELETE: Cancels an existing ChargingProfile for a specific charging session.OCPI 2.2.1 specification · #mod_charging_profiles_cpo_interface

eMSP / SCSP · sender interface

  • Receive the asynchronous response from the Charge Point.

    POST
    {response_url}
  • Receiver (typically CPO) can send an updated ActiveChargingProfile when other inputs have made changes to existing profile.

    PUT
    /ocpi/2.2.1/chargingprofiles/{session_id}
Source
Method: Description GET: n/a POST: Receive the asynchronous response from the Charge Point. PUT: Receiver (typically CPO) can send an updated ActiveChargingProfile when other inputs have made changes to existing profile.OCPI 2.2.1 specification · #mod_charging_profiles_emsp_interface

Try an endpoint

Send a request to this site's OCPI endpoints and read the answer. It never reaches your own system.