Skip to Content

ChangeLog Summary – System Update

Version 3.0 – last updated 25.05.2025

 General Changes 


  • UTF-8 Requirement: All systems (legacy and ECHX) now expect UTF-8 encoding for OCHP and OCPI.
  •  FIFO Processing: Pushing data (Location, Token, Tariff, Session, CDR) is pushed based on a FIFO queue, with minimal delay.
  • CSV Export: New frontend feature enables export of Location, Tariff, Session, and CDR data by network/partner and date range.
  • Case Sensitivity: all IDs are Case Sensitive (Token ID, Tariff ID, Location ID, Evse UID, Session ID, CDR ID) to support OCHP Protocol and OCPI Protocol 2.1.1
  •  Last Updated Field: Replaced by ECHX entry date/time.
  • Normalization: IDs (in OCHP and OCPI) which can have optional separators are normalized. Separators are removed, and object is converted to upper case for the case insensitive values – Example EVSE-ID.
  •  Duplicated Values/Objects: In legacy, if a list contained duplicates, the request got rejected. In ECHX, the repeated values will be ignored.
  • Fallbacks and Defaults:
o Missing required fields are filled with a hyphen (-).
o If timezone is not set in OCHP, OCPI 2.2.1 defaults to UTC.
o Unknown location in OCPI CDR uses EVSE ID instead of dummy values.
o CDR IDs and Object IDs - for the cross-mapping and compatibility, internal IDs are generated and passed to the partner API to map IDs exists, Search Option in the FrontEnd and Export CSV with IDs
  • Recommended IDs: All partners are advised to use PREFIX in their IDs example "DELNDxxxxxxxxxx".
  • Business objects/relations: changes to Roaming Connections, networks, credentials, users and partners may take up to 2 minutes to become active.

OCHP-Updates


  •  CDR Revisions: System allows revised CDRs with same cdr_id.
 

OCPI-Updates


  • EXCEPTION: OCPI 2.2.1 is treated case sensitive values for compatibility with OCPI 2.1.1 and OCHP protocols.
  • Command Mapping: Direct commands map DirectID to OCPI 2.2.1’s authorization_reference.
  • Charging Profiles: Not implemented yet in 2.2.1.
  • Timezone Handling: Defaults to UTC if unspecified for charge points.
  • Locations without EVSE ID: ECHX allows Evses without evse_id.
  •  Patch requests: Fields which are Lists/Objects are requires full list/object to be processed.
  • Additional Limitation Field: in ECHX, OCPI requests can use additional implemented Limit fields to retrieve data, which is EMP-ID or CPO-ID.

Examples: https://echs-q.e-clearing.net/ocpi/cpo/2.1.1/locations?cpo=DELND https://echs-q.e-clearing.net/ocpi/cpo/2.1.1/locations?limit=1000&cpo=DELND

  • OCPI maximum page size/limit

 X LIMIT TOKENS = 1 000 000 

X LIMIT LOCATIONS = 50 000 

X LIMIT CDRS = 50 000 

X LIMIT TARIFFS = 50 000 

X LIMIT HUBCLIENTINFO = 50 000 

X LIMIT SESSIONS = 50 000 

X LIMIT LIVE LOCATIONS = 1 000 000

  • OCPI Pagination: The Partner should follow the URL in "Link" header returned in the Response for best performance as long as link has value.
         o X-Total-Count does not deliver the real information. The partners need to check the frontend for Total Count info.



Metadata and API Access


  • Metadata Endpoints:

o Support for OCHP and OCPI (Locations, Sessions, Tariffs, CDRs).

o Include pagination, date filters, EMP/CPO filters.

Example URLS:

CDRs:

  https://echs-q.e-clearing.net/echs/ocpi/cpo/2.1.1/cdrs/metadata o https://echs-q.e-clearing.net/echs/ocpi/cpo/2.2.1/cdrs/metadata

Tariffs :

https://echs-q.e-clearing.net/echs/ocpi/cpo/2.1.1/tariffs/metadata o https://echs-q.e-clearing.net/echs/ocpi/cpo/2.2.1/tariffs/metadata

Sessions:

  https://echs-q.e-clearing.net/echs/ocpi/cpo/2.1.1/sessions/metadata o https://echs-q.e-clearing.net/echs/ocpi/cpo/2.2.1/sessions/metadata

Locations:

  https://echs-q.e-clearing.net/echs/ocpi/cpo/2.1.1/locations/metadata o https://echs-q.e-clearing.net/echs/ocpi/cpo/2.2.1/locations/metadata

terminated roaming locations are delivered for 14 days after termination

CDRs 35 days.

------ New added partner to a network will inherit the same roaming connections for the network. (or highest)