EV Charge Web Docs | Tridens Technology – Roaming

Docs: Roaming Profile

Mon, 01 Jan 0001 00:00:00 +0000

To access this section in EV Charge, from the Menu, click Roaming.

Roaming Profile

Represents roaming node settings of CPO or eMSP, which is primarly using Tridens EV Charge as the central system. Settings are used to represent the CPO or eMSP entity in protocol specific roaming network communication with other third-party roaming platform nodes.
Entity can be related to Operator, otherwise it belongs to a general Site context.

General locational, monetary and informal settings are taken from the Site and Operator context.

Required to configure:

Protocol
Roaming identifier
Platform type

In the scope of Roaming Profile, Roaming Platforms can be configured for the communication and integration with third-party roaming service. See Roaming Platforms.

When desired to expose the charging infrastructure as a charge point operator (CPO) to the third-party providers/services, it is required to populate the charging infrastructure entries, as stated below.

Area: Set area’s roaming id to the unique identifier non-blank value and also populate the phone number of Area or related Operator. Roaming id attribute is required for roaming, but please note that this identifier may not be used in every roaming protocol, due to different protocol rules.

Charger: Set charger’s roaming id to the unique identifier non-blank value and also mark roaming attribute as enabled. Roaming id attribute is required for roaming, but please note that this identifier may not be used in every roaming protocol, due to different protocol rules.

Connector: Set connector’s roaming id to the unique identifier non-blank value. Roaming id attribute is required for roaming, but please note that this identifier may not be used in every roaming protocol, due to different protocol rules.

See Table 1 for the mapping of roaming identifiers in different roaming protocols.

Table 1: Roaming protocol’s attribute mapping from Tridens EV Charge.

Roaming Protocol	Roaming Protocol Attribute	Mapping from Tridens EV Charge	Example
OCPI 2.2.1	location id	Constructed based on Area’s roaming id.	010107
OCPI 2.2.1	evse uid	Constructed based on Connector’s roaming id.	010107
OCPI 2.2.1	evse id	Constructed based on Roaming Profile’s country code, roaming id and Connector’s roaming id.	SI TRI E010107
OCPI 2.2.1	connector id	Constructed based on Connector’s roaming id.	010107
OICP 2.3	evse id	Constructed based on Roaming Profile’s country code, roaming id and Connector’s roaming id.	SI TRI E010107

Docs: Roaming Platform

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Roaming Platform
OCPI Access Configuration
OICP Access Configuration

To access this section in EV Charge, from the Menu, click Roaming.

Roaming Platform

Represents a third-party roaming platform node which is configured to communicate with roaming node configured by roaming profile in Tridens EV Charge central system. Third-party platform node can be a Hub or specific CPO, eMSP, PTP, NAP, NSP or other. Roaming platform is configured in the scope of Roaming Profile, making platform dependent on the profile settings.

Definition of roles for the Platform:

CPO: Charge Point Operator
eMSP: eMobility Service Provider
PTP: Payment Terminals Provider
NAP: National Access Point
NSP: Navigation Service Provider
Hub: Hub connecting CPOs and eMSPs

Required to configure:

Roaming identifier
Platform type (hub, CPO, eMSP, PTP, NAP, NSP, …)
Base API URL of platform
Country

Roaming Access Configuration

In order to enable the communication between the roaming node of Tridens EV Charge and the third-party roaming node, the selected roaming protocol’s specific access configuration is required.

The configuration is separated on two parts, depending on which communication protocol is selected:

OCPI Access Configuration
OICP Access Configuration

OCPI Access Configuration

Applies for protocols: OCPI

Communication between the two OCPI nodes, whether CPO, eMSP, PTP, NAP, NSP, hub or other is initiated by registration and credentials exchange.

As OCPI protocol defines, one of the two integrating nodes provide a registration token to the second node. The second node uses the registration token to initiate the communication between the two nodes, by exchanging and deciding the common protocol version, available operational modules with addresses and to finalize the credentials exchange.

Credentials exchange is done when both nodes determine to each other a new access token and registration token is revoked.

Access Initiation Setup and Guidelines

Step-by-step registration example #1, when roaming node of Tridens EV Charge initiates the registration to the third-party roaming platform node.

Third-party roaming platform generates the registration token.
Registration token is forwarded in a safe way to the roaming client of Tridens EV Charge. How this step is done, depends on the onboarding communication channel between the roaming sides.
Roaming node of Tridens EV Charge uses registration token provided by the third-party roaming platform and assigns it on the roaming platform configuration by using the “Use Registration Token → Assign Registration Token” feature.
Trigger credentials registration by using “Register Credentials” feature.

Step-by-step registration example #2, when third-party roaming platform node initiates the registration to the roaming node of Tridens EV Charge.

Roaming client on Tridens EV Charge provides registration token to the third-party roaming platform by using the feature “Provide Registration Token → Generate and Assign Registration Token”.
Read the generated token for the roaming platform by using the feature “Read Credentials → Read Registration Token”.
Forward the token in a safe way to the third-party roaming platform. How this step is done, depends on the onboarding communication channel between the roaming sides.
Third-party roaming platform initiates the credentials registration.

Operations to manage OCPI credentials on Tridens EV Charge:

Assigning Registration Token
- Provide Registration Token
  - Generate and Assign Registration Token
  - Assign Registration Token
- Use Registration Token
  - Assign Registration Token
Register Credentials
Update Credentials
Invalidate Credentials
Read Credentials

Assigning the Registration Token

Serves for setup of credentials registration for later communication establishment between the Tridens EV Charge and the third-party roaming platform.

To initiate the credentials registration, one of the two integrating OCPI nodes need to provide the registration token to the other node. By the registration token, the other node will initiate the communication and complete the registration process.

There are exclusionary options on how to determine and use the registration token for OCPI nodes registration, as further described in this section. However, token can be provided or used.

Provide Registration Token

A registration token is provided by the Tridens EV Charge OCPI node, so the other OCPI node platform needs to use this registration token to initiate the OCPI credentials registration and connection establishment.

Generate and Assign Registration Token

By this operation, Tridens EV Charge auto-generates a new registration token for a third-party roaming platform. Platform uses the registration token in later steps, to initialize the OCPI credentials registration and connection establishment.

Assign Registration Token

By this operation, a custom registration token for a third-party roaming platform is assigned on the Tridens EV Charge. Platform uses the registration token in later steps, to initialize the OCPI credentials registration and connection establishment.

Use Registration Token

A registration token is provided by the third-party roaming platform node, so the Tridens EV Charge OCPI node platform needs to use this registration token to initiate the OCPI credentials registration and connection establishment.

Assign Registration Token

Assigns the registration token, which is provided by the third-party roaming platform, so it can be used by Tridens EV Charge to initialize the OCPI credentials registration and connection establishment in later steps.

Register Credentials

Serves to trigger credentials exchange based on registration settings and establishes communication between the Tridens EV Charge and the third-party roaming platform.

Executes the credentials registration process with the third-party roaming platform. Operation uses the assigned registration token and invalidates it after, which means that new assigned credentials need to be used in further communication, as of OCPI.

This is an operation which needs to be initiated by the side to whom the registration token is provided.

Update Credentials

Executes the credentials update for the third-party roaming platform. Operation invalidates an existing access token, which means that new assigned credentials need to be used in further communication to Tridens EV Charge, as of OCPI.

Operation notifies other roaming party with new credentials to access Tridens EV Charge.

Invalidate Credentials

Invalidates all roaming platform’s existing access credentials. Includes revocation of access token, remote access token and registration token.

Read Credentials

Serves to read an existing assigned access credentials used in communication between the roaming platforms.

OICP Access Configuration

Applies for protocols: OICP.

Communication between the two OICP nodes, usually CPO/eMSP with the hub requires mutual certificate authentication, also referred to as mTLS. Thus, each of the two roaming nodes must present itself to the other one with a signed certificate, which is trusted and acceptable by the other side. The signed certificate also serves for identification purposes.

Table 1: Terminology of access certificates configuration on Roaming Platform

Term	Description
Access Certificate	Access certificate for the third-party roaming platform, by which it gains access to Tridens EV Charge’s roaming protocol specific API. This is a client certificate, which the third-party roaming platform needs to present.
Remote Access Certificate	Access certificate which Tridens EV Charge’s roaming node needs to use when accessing the third-party roaming platform node’s protocol specific API. This is a client certificate, which Tridens EV Charge’s roaming node presents when calling the third-party roaming platform API.
Remote Root Certificate	Public authority certificate of the third-party roaming platform node, so Tridens EV Charge can trust the certificates signed by this authority.

Access Setup and Guidelines

Let’s say a CPO and roaming hub platform wants to integrate with each other by OICP.

To enable a CPO to communicate with the roaming hub in scope of mutual certificate authentication:

CPO manager on Tridens EV Charge generates a private/public key pair and certificate signing request (CSR).
CPO manager handles the public key and CSR to the roaming hub provider manager.
Roaming hub provider manager signs the CSR by roaming hub’s trusted certificate authority, resulting in a signed trusted certificate of CPO.
Roaming hub manager handles the signed trusted certificate to the CPO manager.
Roaming hub trusts and identifies the communication with such signed certificate, as it was signed by its trusted certificate authority.

To enable a roaming hub to communicate with a CPO in scope of mutual certificate authentication:

Roaming hub manager generates a private/public key pair and CSR.
Roaming hub manager handles the public key and CSR to the CPO manager on Tridens EV Charge.
CPO manager signs the CSR by the CPO’s trusted certificate authority, resulting in a signed trusted certificate of a hub.
CPO manager handles the signed trusted certificate to the roaming hub manager.
CPO trusts and identifies the communication with such signed certificate, as it was signed by its trusted certificate authority.

Access Setup Operations

Tridens EV Charge provides operations over the Roaming Platform, to provide management of mutual certificate verification access.

Access Certificate

Operations to manage access certificate for the third-party roaming platform, by which it gains access to Tridens EV Charge’s roaming protocol specific API.

Can be done by either by:

a) Directly assigning the access certificate and its private key to the roaming platform configuration.

b) By preparing and signing the certificate signing request (CSR), where resulting certificate is assigned to the roaming platform configuration.

Available Operations:

Assign Access Certificate
Generate Private Key and Certificate Signing Request (CSR)
Sign CSR and Assign Access Certificate

Assign Access Certificate

Accepts PEM or plain Base64 encoded binary data of certificate with its correlated private key and assigns it to the roaming platform.

Used to verify/identify an access certificate of the third-party roaming node.

Generate Keys and Certificate Signing Request (CSR)

Provides a form to issue a certificate. Form accepts required attributes for the certificate signing and generates a private/public key pair. As a result, Base64 encoded binary data of CSR is returned, along with the Base64 encoded representation of private and public key.

Used to generate a certificate signing request with private/public keys, so the Tridens EV Charge or trusted authority can be requested to sign an access certificate.

Sign CSR and Assign Access Certificate

Accepts PEM or plain Base64 encoded binary data of CSR and a reference to the existing system’s trust root certificate which signs this certificate. Certificate is assigned to the roaming platform. Base64 encoded certificate content is returned back. Used to sign certificate signing request and obtain an access certificate.

Remote Access Certificate

Operations to manage access certificate which Tridens EV Charge’s roaming node needs to use when accessing the third-party roaming platform node’s protocol specific API.

Available Operations:

Generate Keys and Certificate Signing Request (CSR)
Assign Remote Access Certificate
Assign Remote Trusted Root/Intermediate Certificate

Generate Keys and Certificate Signing Request (CSR)

Used to help you generate a certificate signing request with private/public keys, so the third-party roaming platform’s authority can be requested to sign an access certificate.

Assign Remote Access Certificate

Accepts PEM or plain Base64 encoded binary data of certificate with its correlated private key and assigns it to the roaming platform.

Required to use for access to the third-party roaming platform.

Assign Remote Trusted Root/Intermediate Certificate

Accepts PEM or plain Base64 encoded binary data of a trusted public root/intermediate authority certificate of the third-party roaming platform node and assigns it to the roaming platform in Tridens EV Charge, so it can trust the certificates signed by this authority.

Required to trust the communication with the third-party roaming platform.

Invalidate

Invalidates all roaming platform’s existing access credentials. Includes revocation of access certificate, remote access certificate and remote root certificate.

Docs: Roaming Tariffs

Mon, 01 Jan 0001 00:00:00 +0000

General information about tariffs in EV charging roaming:

Roaming tariffs are owned and defined by the charging infrastructure operators (CPO).
Roaming tariffs define charging expenses for the usage of the charging infrsatructure (energy, duration, parking, reservation, flat fee).
CPO in roaming does not know the end customer (EV driver), as the customer is the subject of mobility service provider (MSP). Thus, Monetization is not utilized to charge these kinds of end customers.
CPO side calculates the expenses for each session and provides charge detail record (CDR) to the mobility service provider (MSP).
Mobility service providers (MSP) who have the end customers/drivers base, cannot change the CPO’s roaming tariffs. CPO provides the tariffs as informative and as the base for the charge details record breakdown.
Tariffs are matched by validity (date and time). Recurrency modes are available in daily, weekly, one-time.
Roaming tariffs apply for a charging infrastructure where they are being used (referenced).
Roaming tariff applies for the third-party end customers for a roaming platform where the reference is assigned.
Third-party roaming providers can use push and pull models to obtain tariffs. When roaming tariff is being managed, integrated roaming third-party platforms are also being notified about the updates.
While home network roaming sessions are handled on Tridens EV Charge, expenses are calculated based on valid tariffs. Handling mid-session and at session completion.

Topics in this document:

Define Roaming Tariffs
Assign Roaming Tariffs to Charging Infrastructure
Assign Roaming Tariffs to Roaming Platform

To access this section in EV Charge, from the Menu, click Roaming and then Roaming Tariff.

Roaming Tariff

Roaming tariff defines the pricing that applies for charging infrastructure�s roaming usage and contains tariff details which define prices for metric types (energy, charge time, park time, reservation, flat), recurrency policy and constraints.

To add or manage Roaming Tariffs, navigate to EV Charge and while in the Menu, click Roaming and select the Roaming Tariffs tab. By using the button to add the tariff, wizard form shows up.

Assign name, alphanumeric code, status and validity restrictions for the whole Roaming Tariff structure.

Add roaming tariff details with the date-time recurrence policy and assign the desired monetary prices for metric types of energy, charging time, parking time, reservation time, reservation flat or just a flat fee. Monetary prices are determined without VAT, meanwhile VAT needs to be entered in a separate field. Unpopulated value means 0 (zero) expense for such metric type.

Roaming Tariff:

Defines validity restrictions for the whole tariff.
Validity frames should not overlap.
Provides transitions among the tariffs. E.g., one tariff stops on 2025-01-01 at 02:59:59 and the next one starts at 2025-01-01 03:00:00. Tariff element’s start/stop date and time attributes are optional. If no date-time restrictions are set, elements last indefinitely.
Accumulates the tariff details.

Roaming Tariff Detail:

Defines the schedules (recurring, one-time) and the cost at the moment when the schedule applies.
Defines prices and VAT for kWh energy, reservation time, charging time, parking time, flat fee and flat reservation fee.
Empty price means zero cost for the schedule.

Figure 1: Roaming Tariff Detail Configuration

Troubleshoot:

Tariffs not exposed in roaming integration or sessions have no monetary impact?

Please ensure the following is well set:

Roaming tariff is assigned on a proper context level: Charger/Operator/Site.
Roaming tariff is assigned on an integrated Roaming Platform.

Assign Roaming Tariff to Charging Infrastructure

Once Roaming Tariffs are configured, assign them on the charging infrastructure context, so the tariffs will apply in calculating the roaming expenses on the belonging chargers.

Tariffs can be set on Session settings of Site/Operator/Charger, where the lowest assigned level applies. The lowest level is Charger, so if Roaming Tariff is specified there, it overrides any tariff configurations on higher levels of Operator and Site.

To assign Roaming Tariff to the charging context, navigate to Site, Operator or Charger view and enter the wizard form. While managing the Session settings, there is a Roaming Tariffs selection where the desired tariffs can be picked to apply for the belonging charging sessions.

Assigning Roaming Tariffs to Roaming Platform

Once Roaming Tariffs are configured, assign them on the Roaming Platform context, so the tariffs will apply in calculating the roaming expenses for the events related to such roaming integration.

To assign Roaming Tariff to Roaming Platform, navigate to EV Charge and while in the Menu, click Roaming and select the Roaming Profiles tab. Select the desired Roaming Profile to see the Roaming Platforms. Select the platform and hit the Update button, so the wizard shows up. In the first step of wizard, find the Roaming Tariffs selection and pick the tariffs that are meant to apply for the sessions related to the specific roaming platform integration.

Docs: Terminals

Mon, 01 Jan 0001 00:00:00 +0000

A Terminal represents a physical unit (for example, a payment terminal) that can be assigned to the charging infrastructure.

In the context of Tridens EV Charge, terminals enable seamless interaction between the charging environment and payment systems, ensuring secure transactions and operational efficiency.

Topics in this document:

Terminals
Payment Terminals Integration
View Terminals
Assign Terminal to Charging Infrastructure
Unassign Terminal from Charging Infrastructure

Terminals

A Terminal consists of the following attributes:

Identification (id, code): Unique identifiers used to distinguish the terminal.
Naming (name, description): Human-readable name and additional descriptive information.
Type (payment): Defines the terminal type, such as a payment terminal.
Address (address, city, zip, state, country): Specifies the official physical location of the terminal.
Geolocation (latitude, longitude): Indicates the terminal’s exact geographical coordinates.
Roaming (platform, roaming id, roaming reference): Indicates whether the terminal belongs to a third-party roaming platform (Payment Terminal Provider — PTP) and provides its roaming identification details.
Operator: Optional site operator associated with the terminal. When present, the terminal configuration applies to the operator context; otherwise, it applies to the general site environment.

Payment Terminals Integration

Terminals can be stored through roaming integrations with Payment Terminal Providers (PTPs), where the integrating party is the Charge Point Operator (CPO) managing the charging infrastructure in Tridens EV Charge.

To set up the roaming integration, see Roaming - Roaming Platforms.

Tridens EV Charge automatically persists payment terminals received from an integrated PTP roaming platform either:

on pull demand, or
through automatic push updates.

Once integrated, the charge point operator can assign payment terminals to Areas or Connectors, ensuring accurate terminal association within the charging network.

View Terminals

Operators can view all integrated terminals through a filterable table view, allowing quick access to terminal details and management actions.

Assign Terminal to Charging Infrastructure

A charging infrastructure operator can connect a terminal by assigning it to a specific Area or Connector.
When roaming integration with Payment Terminal Provider is active, the assigned terminal will reflect as assigned on the charging infrastructure in roaming to ensure data consistency across platforms.

Unassign Terminal from the Charging Infrastructure

A charging infrastructure operator can disconnect a terminal by unassigning it from an Area or Connector.
When roaming integration with Payment Terminal Provider is enabled, such Terminal will reflect as unassigned from the charging infrastructure in roaming to ensure data consistency across platforms.