Skip to main content
Getz Hub

International hub connectivity

Roaming across borders through hub-to-hub peering

Getz Hub can peer with other roaming hubs as equals, so drivers of apps connected elsewhere can roam onto participating Zimbabwean networks, and the other way round.

One decision, check by check: the trace the Hub records for every message. Synthetic demo data.

  1. What you see: the checks a charge record passed, in the order they ran
  2. Why it matters: the same fixed checks for every partner, recorded for audit

The challenge

Visiting drivers fall between networks

Tourists, cross-border freight and regional fleets cross networks that have never integrated with each other.

  • National silos

    Each country’s networks connect to different apps and hubs.

  • Version mix

    Peer hubs and their partners run different OCPI versions.

  • Routing loops

    Without safeguards, messages can bounce between hubs.

How it works

How peering works

  1. Step 1: Peer as equals

    A peer hub connects over OCPI like any partner, classified as a hub, and its parties are reached through it.

  2. Step 2: Loop prevention

    A message never goes back to a party already in its path, and Hub never re-publishes to the source.

  3. Step 3: Hop limit

    At most 4 hops between hubs, so traffic cannot circulate indefinitely.

  4. Step 4: Same rules

    Agreements, visibility and assurance apply to peered traffic exactly as to direct partners.

Interactive illustration

CPO to Hub to app: the architecture

Select a participant to read how it connects and what Hub does for it.

Illustration

How Getz Hub connects charge point operators and mobility apps

Operators publish once to Hub over OCPI. Hub applies agreements and visibility rules, then delivers to each participating app in the OCPI version it speaks.

CPO back officeCPO on Getz NetworkForecourt networkGetz HubEV charging appFleet or brand appPeer roaming hubData customers

Getz Hub: the neutral roaming layer

Hub checks every message against roaming agreements, visibility rules and each partner’s capabilities, records why it routed it, translates between OCPI versions and checks roamed charge records against the agreed tariff.

Use Tab to reach the diagram, then the arrow keys to move between parts.

Capabilities

Why peer with Getz Hub

  • Version translation

    Peer on 2.1.1, 2.2.1 or 2.3.0; Hub translates for its own partners.

  • Connection status

    Peer hubs receive connection status for every party, as OCPI Hub Client Info intends.

  • Several currencies

    Charge records are checked in the currency their tariff was agreed in.

  • Built for Zimbabwe

    Tariffs in US dollars or ZWG with 15.5% VAT today, and a visiting driver’s charge record kept in the currency its tariff was agreed in.

Questions

International hub connectivity: questions

How does a peer hub connect?

Over OCPI, like any partner: it is classified as a hub, its parties are reached through it, and agreements, visibility and assurance apply to its traffic as to any other.

Which networks can our app or owners reach through peering?

Only participating networks reached through hubs that have peered and through agreements with each party. Peering makes access possible; it does not make every network available. Ask about the markets and corridors you need.

As an operator, who decides whether an app behind a peer hub sees our sites?

You do, as for a direct partner: the app needs a roaming agreement with you, and your visibility rules apply across the peering link.

What does a blocked route look like?

A message that would loop or exceed the hop limit is not delivered, and the decision is recorded in its routing trace with the check that stopped it.

Why a 4-hop limit?

It keeps traffic from circulating between hubs indefinitely while still allowing chains of peered hubs. It is a configured default.

Peer with Getz Hub

Tell us about your hub, the regions you cover and the OCPI version you use.