data solutions

ROAMING MANAGEMENT SERVICES

OFFER BETTER ROAMING MANAGEMENT SERVICES TO YOUR CUSTOMERS

Mobile Network Operators (MNO), Mobile Virtual Network Operators (MVNO) and Mobile Virtual Network Enablers (MVNE) that provide their service abroad need a powerful tool for connectivity control outside their usual territory. If the same tool can help them during price negotiations with every Roaming partner, the tool’s value increases.

Existing and competing roaming management solutions differ according to the following design decisions:

  • What roaming detection method shall be used?
    Two methods dominate the market: Network based detection and SIM based detection. These two methods are usually referred to as network trigger and SIM trigger.
  • How advanced and how dynamic shall card updates preparation (Business Logic) be?
    Here, the existing solutions range from very simple static PLMN list update, over multiple EF’s update to advanced dynamic personalized update.

Valid left these decisions to our customers and designed the Roaming Management solution which is:

  • compatible with both detection methods,
  • open for both static and dynamic update lists and
  • able to interwork with 3rd party Roaming business logic (SoR) providers.

Four main combinations of Detection methods and business logics include:

Network based trigger with external BL

  1. When abroad, the SIM card will attempt network registration on one of the available networks. The visited network will, over the signaling channel, send a Location Update to the home network.
  2. The LU event is captured by the probing node. The information is passed to the business logic node, either in a sequence or by periodic file transfer.
  3. Based on the business logic rules, the instruction for the OTA is compiled and sent over the dedicated API.
  4. The OTA creates relevant campaigns and executes requested updates.
  5. SIM card is updated and refreshed, causing registration on the new network, based on newly received PLMN list.

Network based trigger with internal BL

  1. When abroad, SIM card will attempt network registration on one of the available networks. Visited network will, over signaling channel, send the Location Update to the home network.
  2. The event is captured by the probing node. The information is sent to the internal business logic node, either in a sequence or by periodic file transfer.
  3. Based on the business logic rules, personalized PLMN list, FPLMN list, LOCI update, LOCIgprs update and Refresh command (or a subset of these) are created.
  4. The OTA executes requested updates.
  5. SIM card is updated and refreshed, causing registration on a new network, based on newly received PLMN list.

SIM based trigger with external BL

  1. When abroad, SIM card will attempt network registration on one of the available networks. If successful, the resident Roaming applet will send the polling keyword ROA mcc&mnc up to the OTA platform.
  2. The OTA will, on reception of the keyword, pass the ICCID and the MCC&MNC data to the external business logic over dedicated SoR API.
  3. Based on the business logic rules, the instruction for the OTA is compiled and sent over the dedicated API.
  4. The OTA creates relevant campaigns and executes requested updates.
  5. SIM card is updated and refreshed, causing registration on a new network, based on newly received PLMN list.

SIM based trigger with internal BL

  1. When abroad, SIM card will attempt network registration on one of the available networks. If successful, the resident Roaming applet will send the polling keyword ROA mcc&mnc up to the OTA platform.
  2. The OTA will, on reception of the keyword pass control to the internal business logic node. Based on the business logic rules, the update instruction is compiled.
  3. The OTA creates relevant campaigns and executes requested updates.
  4. SIM card is updated and refreshed, causing registration on a new network, based on newly received PLMN list.

The main features of the solution are:

  • Supports both Network and SIM location triggers.
  • Works with either inbuilt Business Rules or connected to an external Business Rules node.
  • Inbuilt Business Rules range from simple static rules to quite advanced dynamic rules.
  • Refresh feature insures immediate service effect.

As part of OTA Connectivity Suite services, the Roaming Management solution relies on it for common framework features (provisioning, reporting and similar).

The Roaming Management solution is fully transparent to end customers. They can simply enjoy lower roaming prices in a more convenient way.

Main benefits of this solution:

  • Decreased roaming cost.
  • Increased roaming service accessibility.
  • Increased control over Roaming traffic.
  • Excellent tool during Roaming agreement negotiations.
Contact Us for More Information >