Special Use Cases

Special use Cases — Built for Real-World Complexity

MVNEs and operators with complex multi-IMSI environments need more than standard HSS configurations. The NextGen HSS includes advanced capabilities designed for scenarios where per-IMSI granularity, dynamic USSD profiles, and PDP context management are not optional — they are essential.

Per IMSI roaming controls

The challenge

When dealing with multi-IMSI scenarios, the conditions for roaming on each IMSI might be completely different. Different mobile subscribers might need completely different conditions — for example a world roaming subscription, or a limited national subscription. Any platform that provides only global configurations per IMSI range or per operator would force administrators to add overlapping rules, increasing complexity on the HLR/HSS.

The solution

NextGen HSS provides a per individual IMSI roaming profile. The administrator creates PLMNs and associates rules to those PLMNs. Once per-PLMN configurations are done, the administrator builds Roaming Profiles linked to each IMSI with the right conditions.

IMSI 333444XXXXXX can have world roaming with full quality and conditions, while IMSI 333444ZZZZZZ has only local roaming with lower quality services — both managed from the same platform.

Per IMSI USSD codes

The challenge

MVNEs usually have multitudes of customers on the same IMSI range, each needing different USSD commands mapped to different services. For example, an MVNE with one customer offering prepaid services and another offering post-paid: the prepaid subscriber uses USSD code 456 to check their balance, while the post-paid subscriber does not need that code at all. Furthermore, the same code 456 might redirect to a different USSD Gateway for each customer — one for a weather service, another for stock exchange data.

The solution

NextGen HSS provides a per individual USSD profile, allowing administrators to define completely different profiles and use them in any combination across subscribers.

Profiles can be updated via API on the fly to adjust subscribers when they request different services — changes take effect immediately.

Context identifiers per IMSI

The challenge

The MAP protocol has a limitation on how many PDP contexts can be sent per protocol message. MVNEs can have multitudes of customers, each requiring multiple PDP combinations defined per IMSI. When dealing with a large number of PDP contexts, numeric ID conflicts arise: if PDP context Z is assigned ID 35, another context like E might be assigned the same ID, leading to configuration errors and unpredictable behaviour.

The solution

NextGen HSS provides a PDP Assignation system. When dealing with more than 50 PDP contexts, the numbering is managed at the assignation level — PDP contexts themselves have no fixed numbering, which is only assigned when building the PDP Assignation for each IMSI.

The administrator can decide, per IMSI, the ordering of up to 50 PDPs — providing maximum flexibility when building complex subscriptions without any ID conflict.