POS Integrations

The POS Integration sections show how to integrate a POS terminal with the charger of CPO

Topics in this document:

Introduction

POS provider uses Tridens EV Charge for POS as a gateway to the chargers of CPOs by OCPI/OICP. POS provider communicates with Tridens EV Charge for POS, which forwards the requests to OCPI/OICP CPO’s charger for the session control and receives responses and notifications for the related actions.

POS Communication Topology

Diagram 1-1: POS Communication Topology

Configuration

Tridens configures the environment for POS integrations and applies the new POS provider. Further configuration depends on the selected roaming protocol, whether it is OCPI or OICP.

OCPI

  1. Configure environment of POS provider in Tridens EV Charge for POS (configured by POS provider).

    a. Configure Operator’s Roaming Profile of OCPI, representing POS provider’s settings.

    b. Configure Operator’s Roaming Platform of OCPI, representing the CPO client.

    c. Generate platform’s registration token to use for credentials exchange by the CPO client.

  2. Configure environment of CPO client (configured by CPO client).

    a. Use POS provider’s registration token (of Roaming Platform).

    b. Initialize credentials exchange.

OCPI Sequence

Diagram 1-2: OCPI Communication Sequence

OICP

  1. Configure environment of POS provider in Tridens EV Charge for POS to communicate with the roaming hub (configured by POS provider).

    a. Onboard POS provider as mobility provider in OICP hub.

    b. Configure Operator’s Roaming Profile of OICP, representing the POS provider settings to the OICP hub.

    c. Configure Operator’s Roaming Platform as a roaming hub, which contains CPOs.

    d. Enable POS provider in Tridens EV Charge for POS to communicate with the roaming hub in scope of mutual certificate authentication (configured by POS provider and roaming hub provider).

    • POS provider on Tridens EV Charge for POS generates a private/public key pair and certificate signing request (CSR).

    • POS provider handles the public key and CSR to the roaming hub provider manager.

    • Roaming hub manager signs the CSR by roaming hub’s trusted certificate authority, resulting in a signed trusted certificate of POS provider.

    • Roaming hub manager handles the signed trusted certificate to the POS provider.

    • Roaming hub trusts and identifies the communication with such signed certificate, as it was signed by its trusted certificate authority.

    • Assign certificate to the the hub Roaming Platform. The certificate will be used for the outgoing communication to the hub.

    e. Enable the roaming hub to communicate with Tridens EV Charge for POS in scope of mutual certificate authentication (configured by roaming hub provider and POS provider).

    • Roaming hub manager generates a private/public key pair and CSR.

    • Roaming hub manager handles the public key and CSR to the POS manager of Tridens EV Charge for POS.

    • POS provider signs the CSR by the POS’s trusted certificate authority, resulting in a signed trusted certificate of a hub.

    • POS provider handles the signed trusted certificate to the roaming hub manager.

    • POS provider trusts and identifies the communication with such signed certificate, as it was signed by its trusted certificate authority.

  2. Configure environment of CPO to communicate with the roaming hub (configured by CPO client).

    a. Onboard CPO provider as the charging infrastructure operator on the hub.

    b. Configure the CPO environment for the communication with the hub.

    c. Enable CPO to communicate with the roaming hub in scope of mutual certificate authentication (configured by CPO and roaming hub provider).

    d. Enable the roaming hub to communicate with the CPO in scope of mutual certificate authentication (configured by roaming hub provider and CPO).

OICP Sequence

Diagram 1-3: OICP Communication Sequence

Session Control from POS Provider to Tridens EV Charge for POS

Operations by which the POS Provider can request EV Charge to start and stop the charging session on the charging infrastructure.

Resulting and intermediate charging session actions are forwarded back to the POS Provider by API, as configured and specified in section Tridens EV Charge Reporting Session Progress to POS Provider.

Request Identifiers Disambiguation​

IdentifierDescription
Roaming Platform IdentifierPOS provider’s roaming platform identifier in Tridens EV Charge.

Configured by Tridens.
Roaming Partner IdentifierCPO provider’s roaming identifier in scope of Roaming Platform.

Configured by Tridens.
Roaming Partner’s Connector IdentifierCPO provider’s charging infrastructure’s composite identifier, consisting of OCPI’s {location-id}.{evse-id}.{connector-id}.​ Composite identifier is generated by OCPI CPO platform you are integrating with. ​

In scope of CPO’s in Tridens EV Charge, it reflects {area-id}.{charger-id}.{connector-id}, so it can be determined in that way as well.​

POS provider can determine the Area, Charger, Connector structure, by requesting the API and using id/code attributes to construct the identifier. To obtain this, follow API guidelines of Read Charging Infrastructure of Roaming CPO.

Table: Request identifiers

Read Charging Infrastructure of Roaming CPO

API request:

Below is the API response containing paginated list of Areas with nested Charging Stations, Chargers and Connectors

Request Charging Session to Start

API Reference:

For authentication and authorization details, refer to the Tridens EV Charge API Reference.

Request Charging Session to Stop

API Reference:

For authentication and authorization details, refer to the Tridens EV Charge API Reference.

Tridens EV Charge for POS Reporting Session Progress to POS Provider

Configure Notification Rules for actions of charging session start, meter value reports and session stop. Provide a filter over Roaming Platform and assign publishing by REST call out. POS provider needs to provide API endpoints to which the reports will be published.

Notification Rule Configuration in System Operations of POS Provider Operator:

  1. Add Notification Rule and determine name.

  2. Assign Publisher of URL action.

    a. Assign headers which are attached to the URL request. Here you can specify the access token.

    b. Assign URL to which the call will be executed. Select Base type and enter URL.

  3. Select Charging Sessions scope of notification. Create a Notification Rule for scopes of:

    a. Session started

    b. Meter values reported

    c. Session ended

  4. Add filter to limit notifications for this specific Site’s Operator.

    a. Select logical operator of Equal to (==), with value of contents.session.roaming_platform.id

  5. Set notification rule as enabled.

Below is an example of how to configure notification rule: