Guardivia

Outcome-led solution

Roaming and Interworking

Roaming and interworking covers the signaling, charging-record and messaging functions that let subscribers use partner networks and let IMS, legacy and application domains exchange messages.

The challenge

  • Roaming signaling across SS7, Diameter and 5G
  • Settlement records and disputes
  • SMS continuity for VoLTE and VoNR subscribers

What does Guardivia provide for roaming?

Guardivia provides the Roaming Suite (inbound and outbound roaming over SS7 and Diameter, CAMEL prepaid roaming, GRX/IPX integration, welcome SMS, TAP3 and RAP, Diameter Edge Agent, N32/SEPP and NRF discovery where supported) and the IP-SM-GW for IMS-to-SMS interworking, within the Guardivia Core Network Suite.

Last reviewed 2026-09-12 by the Guardivia QoS Engineering Team. Product facts on this page describe current capabilities; items marked “where supported”, “optional”, “integration” or “consultancy” are confirmed per deployment.

Solution flow

Derived from this solution
  1. 01
    Roaming signalingDEA, S6a/S9 proxy, SS7 roaming and N32/SEPP where supported.
  2. 02
    SettlementTAP3 generation, RAP handling, reconciliation and roaming analytics.
  3. 03
    Messaging continuityIP-SM-GW interworking with the Operator SMSC.
The complete approach and product responsibilities remain listed below.

Approach

How Guardivia addresses it

  1. 01

    Roaming signaling

    DEA, S6a/S9 proxy, SS7 roaming and N32/SEPP where supported.

    Guardivia Core Network Suite →
  2. 02

    Settlement

    TAP3 generation, RAP handling, reconciliation and roaming analytics.

    Guardivia Core Network Suite →
  3. 03

    Messaging continuity

    IP-SM-GW interworking with the Operator SMSC.

    Guardivia Operator SMSC →

Outcomes

  • Roaming under the operator's control
  • Reconciled settlement
  • SMS across generations

Products involved

FAQ

Questions about this solution

Is 5G roaming supported?

N32/SEPP, NRF-based discovery and slice-aware roaming are supported where confirmed for the target release and network.

See it running on your traffic profile.

Talk to the engineers who build the platform. Demos use your protocols, your integration points and your policy questions.