User Story

In order to introduce competitive roaming offerings, a Mobile Network Operator (MNO) or Mobile Virtual Network Operator (MVNO) wants to natively support multi-IMSI eSIM profiles within PortaBilling. This will enable integrations for provisioning, streamline product management, and enhance the end-user experience for frequent travelers.

Example of use

  • Scenario A: A truck driver frequently travels on the Munich-Viena route. Their mobile operator (a German MNO) offers a "EU Neighbour - Austria" bundle that includes service in Germany and Austria. The eSIM profile for this bundle contains the MNO's own IMSI for use in Germany and a partner IMSI (from an IMSI Sponsor in Austria) for use in Austria, optimizing roaming costs and service quality.
  • Scenario B: A private transfer service driver travels weekly between Munich (Germany), Opatija (Croatia) and occasionally reaches Montenegro. They would benefit from a "Balkan Traveller" bundle, which includes an eSIM with the German MNO's IMSI and partner IMSIs with optimal cost for use in Austria, Slovenia, Croatia and Montenegro ensuring seamless service across borders.
  • Scenario C: A sales representative frequently visits trade shows world-wide. They would sign-up for regional or global bundles with world-wide coverage. The eSIM profile for this bundle contains the MNO's own IMSI for use in Germany and a dynamic partner IMSI which is chosen, replaced & provisioned automatically as the subscriber arrives Japan or United States.

Business model

MNO, MVNO

Technology

Each eSIM profile is identified by ICCID and may have single or multiple (2+) embedded IMSIs. MNO/MVNO often embed more than one IMSI into profile to optimize roaming costs - the first IMSI is typically owned by the operator, the other IMSIs in the profile - given by partners. In addition, eSIM profile contains applet with allowed MCCs and rules to prioritize this or that IMSI and preferable MNC. Therefore, switching between IMSIs is automatically done by device and no end user action is required.

The overall solution assumes integration and orchestration between several platforms:

  • PortaBilling B/OSS: For subscriber management, product catalog, billing, charging, and SIM inventory.
  • Nordic SM-DP+: For eSIM profile generation and management.
  • Home HSS/PCRF: For MNOs/full MVNOs to manage subscriber authentication and policy control.
  • MVNE Platform: For light MVNOs to manage IMSI activation and service control.
  • sFTP Interface: For secure file transfer between the operator and the SM-DP+.

Current Solution

Currently, multi-IMSI profiles are handled via a workaround that maps multiple IMSIs to existing PortaBilling data objects. This involves creating separate SIM inventory records for the primary (eSIM) and secondary (IMSI) identities, linked by a custom "Profile ICCID" field. This approach has limitations, particularly in product-to-eSIM mapping, automation, and scalability.

Stakeholders and their benefits

Benefit/StakeholdersMore ComfortIncreased EfficiencySaves TimeTighter ControlReplaces Human
CSP
✓✓✓✓
Network operations /Support of CSP✓✓✓✓✓
End user✓



The CSP owner will gain an increased source of revenue through optimized roaming costs, enhanced scalability and reduced operational expenditure (OPEX) on manual provisioning tasks.

Use Cases

Use case #1: Local MNO / (Full) MVNO

Roles: eSIM Profile Manager, Product Manager, PortaBilling (PB), Onboarding App, End User, Home HSS/PCRF, Provisioning System

Preconditions:

  1. Local MNO/MVNO in Germany has a roaming agreement with Partner X, an IMSI Sponsor and MNO in Austria with MNC 77 and 78

    • A batch of 1000 IMSIs has been negotiated with Partner X.
    • Partner X shall charge Local MNO/MVNO for IMSI usage:
    CountryMCCMNCPrice per GB
    Austria232771.01
    Austria232781.01
    • Partner X core network is configured to route network registrations and credit control of those IMSIs to the mobile core network of Local MNO/MVNO (3gpp interfaces based on diameter: S6a, Gy, Ro)

  2. Local MNO/MVNO in Germany has a roaming agreement with Partner Y, an IMSI Sponsor and MNO in Austria with MNC 55 who has its own direct roaming agreements with operators in Austria, Slovenia, Croatia and Montenegro.

    • A batch of 10000 IMSIs has been negotiated with Partner Y.
    • Partner Y shall charge Local MNO/MVNO for IMSI usage:
    CountryMCCMNCPrice per GB
    Austria232551.1
    Slovenia293561.01
    Croatia219020.99
    Montenegro297010.41
    • Partner Y core network is configured to route network registrations and credit control of those IMSIs to the mobile core network of Local MNO/MVNO (3gpp interfaces based on diameter: S6a, Gy, Ro)

  3. An sFTP interface is established with Nordic SM-DP+ for eSIM profile generation.

  4. Gy/Ro interfaces are configured between PortaBilling and Local MNO/MVNO core network for real-time credit control.

Use scenario #1.1: Partner Tariff

  • Product Manager (PortaBilling Admin): Defines partner tariffs in PortaBilling service catalog as per rate sheets in pre-conditions:
    • "Partner X - Data"
    • "Partner Y - Data"
  • PortaBilling provides capability to associate those tariffs with the relevant partner to track cost xDRs for reconcilation and settlements with the partner (#1.6)

Use scenario #1.2: eSIM profile generation

  • The eSIM Profile Manager combines the following into a specially formatted file:
    • a batch of own IMSIs with sponsor IMSIs (from Partner X/Y)
    • rules for IMSI and MNC selection per country (MCC) based on Partner Tariff, e.g.
      • if IMSI2 sponsored by Partner X
        • 232 77 IMSI2 (high preference)
        • 232 78 IMSI2 (med preference)
        • 232 * IMSI1 (low preference)
      • if IMSI2 sponsored by Partner Y
        • 232 55 IMSI2 (high preference)
        • 232 * IMSI1 (low preference)
        • 293 56 IMSI2 (high preference)
        • 219 02 IMSI2 (high preference)
        • 297 01 IMSI2 (high preference)
  • The file is encrypted and securely transmitted to the Nordic SM-DP+ via the sFTP interface.
  • The SM-DP+ generates the eSIM profiles, each containing a primary IMSI, a partner IMSI, and an applet with rules for IMSI and MNC selection in allowed countries (i.e. per MCC).
  • An output file containing the generated profile data (Profile ICCID, Ki, OPc) is received, decrypted, and automatically loaded into the PortaBilling SIM inventory and Nordic profile inventory. Each eSIM is represented as a single logical entity with multiple associated IMSIs and their security credentials.

Use scenario #1.3: Product Offerings

  • Product Manager (PortaBilling Admin): Defines service bundles in PortaBilling service catalog:
    • "EU Neighbour - Austria 30-Day Pass" as renewable PortaBilling Bundle with 100GB netaccess allowance for
      • E212-23277
      • E212-23278
    • "EU Neighbour - Austria 7-Day Pass" as renewable PortaBilling Bundle with 10GB netaccess allowance for
      • E212-23277
      • E212-23278
    • "Balkan Traveller 10-Day Pass" as renewable PortaBilling Bundle with 50GB netaccess allowance for
      • E212-23255
      • E212-23956
      • E212-21902
      • E212-29701
  • PortaBilling demonstrates the product offering capability to map specific service bundles above to corresponding multi-IMSI eSIM profile batches in the inventory so that:
    • Availability of eSIM resource suitable for chosen service bundle could be validated before purchase by Onboarding App in #1.5
    • Specific eSIM resource could be bundled with multiple offerings, e.g.
      • eSIM profile using Partner X IMSI is available for use with
        • "EU Neighbour - Austria 30-Day Pass"
        • "EU Neighbour - Austria 7-Day Pass"
      • eSIM profile using Partner Y IMSI is available for use with
        • "Balkan Traveller 10-Day Pass"
        • "EU Neighbour - Austria 30-Day Pass" (when cost-effective eSIM profiles using Partner X IMSI are depleted)
        • "EU Neighbour - Austria 7-Day Pass" (when cost-effective eSIM profiles using Partner X IMSI are depleted)

Use scenario #1.4: eSIM Stock levels

  • The eSIM Profile Manager accesses a dashboard or report in PortaBilling that shows the current stock levels of available multi-IMSI eSIM profiles for different partner and bundle configurations, e.g.
    • "Own+X" profiles
    • profiles suitable for "Balkan Traveller 10-Day Pass"
  • As subscribers purchase bundles, the respective eSIM stock is depleted.
  • PortaBilling provides alerts or notifications when stock levels fall below a predefined threshold, allowing the manager to initiate a new profile generation batch (#1.2) in a timely manner.

Use scenario #1.5: Onboarding

  • End User A (Truck Driver): Opens the Onboarding App and browses available plans for travel between Germany and Austria. The app lists all suitable bundles, particularly the "EU Neighbour - Austria 30-Day Pass" bundle.
  • PortaBilling can intelligently link this bundle to an available eSIM profile containing IMSI from Partner X.
  • End User B (Transfer Driver): Opens the Onboarding App for travel between Germany and Croatia. The app displays a "Balkan Traveller 10-Day Pass" bundle, which is linked to an eSIM profile batch containing IMSIs from a different partner - Partner Y.
  • An end user selects and pays for the "EU Neighbour - Austria 30-Day Pass" bundle.
  • A subscriber account is created in PortaBilling, the service bundle is applied, and a multi-IMSI eSIM profile from the appropriate batch is assigned to the account.
  • An eSIM activation code (QR code) is delivered to the end user.
  • Upon successful installation of the eSIM profile by the end user, the account and service bundle is activated (or was activated at the time of purchase).
  • PortaBilling notifies Provisioning System
  • Provisioning System creates all associated IMSIs (own and partner) with their Ki/OPc secrets in the Home HSS for an MNO/full MVNO.

Use scenario #1.6: Usage & Charging

  • The end user is in Germany. The device uses the own IMSI for all services (Voice, Text, Data). Usage is authorized in real-time via Gy/Ro against the user's bundle in PortaBilling.
  • The end user travels to Austria. The applet on the eSIM automatically switches the active IMSI to the Partner X IMSI. Data Usage is routed to the Home operator's network, and is authorized and charged in real-time via Gy against the same bundle in PortaBilling.
  • Partner xDRs are created in PortaBilling, real-time based on Partner Tariff (#1.1)

Use scenario #1.7: Fair usage

  • The "EU Neighbour - Austria 30-Day Pass" bundle includes a Fair Usage Policy (FUP) threshold (e.g., 50GB of high-speed data).
  • The end user consumes 50GB of data while in both countries.
  • Upon hitting the threshold, PortaBilling triggers a dynamic service profile change for all IMSIs associated with the eSIM profile.
  • Provisioning System updates the subscriber profile for own IMSI in Home PCRF to apply a new policy (e.g., reduced QoS, throttled speed).
  • Provisioning System doesn't update the subscriber profile for Partner X IMSI

Use scenario #1.8: Account closure

  • The subscriber account in PortaBilling is terminated by the operator.
  • The eSIM profile status is updated to "Disposed" in the PortaBilling inventory.
  • PortaBilling triggers a de-provisioning event
  • Provisioning System:
    • Removes all IMSIs associated with the eSIM profile from the Home HSS.

Use scenario #1.9: Recycling

  • Upon account closure (#1.8), a business rule determines that the eSIM profile can be recycled.
  • An automated process triggers the recreation of the eSIM profile with new ICCID and Ki, OPc and other secrets, including all its previously associated IMSIs, up2date MCC-MNC rules and reloads it into the Nordic SM-DP+ and PortaBilling inventories as an "Available" resource.

Use scenario #1.10: History Audit

  • An administrator needs to investigate who used the IMSI 26201... on a specific date and time in the past.
  • The administrator uses an audit trail feature in PortaBilling to query the assignment history of that specific IMSI.
  • The system returns a historical record showing which account and end user was assigned the eSIM profile containing that IMSI during the specified time frame, even if the IMSI has since been recycled and reassigned.

Use case #2: Global MVNO

Roles: PortaBilling System (PB), End User, Home HSS/PCRF or MVNE Platform.

Preconditions:

  1. The Global MVNO has agreements with multiple IMSI sponsors worldwide.
  2. PortaBilling maintains a "Pool" of available IMSIs from these various sponsors, not yet embedded into any eSIM profile. Each IMSI in the pool is tagged with metadata indicating its optimal country or region and associated cost rates.
  3. The end user has an active account with a global roaming product and a multi-IMSI capable eSIM.
  4. The system is capable of tracking the subscriber's location (e.g., via HSS location updates).

Use scenario #2.1: Location Update and OTA IMSI Swap

  • An end user with an eSIM profile containing IMSIs for Europe and North America travels to Japan.
  • The network reports a location update for the subscriber in Japan (MCC 440).
  • PortaBilling detects that the user is in a country for which their current eSIM profile has no optimal IMSI.
  • The system consults the IMSI Pool and identifies an available IMSI from a Japanese sponsor that offers the best cost rates and QoS for that location.
  • PortaBilling initiates an Over-The-Air (OTA) update to the subscriber's eSIM profile, replacing one of the existing (less relevant) IMSIs with the new, optimal Japanese IMSI.
  • The end user's device seamlessly begins using the new IMSI without any manual intervention.

Use scenario #2.2: Recycling

  • Following the OTA swap in #2.1, the IMSI that was replaced (e.g., the North American partner IMSI) is now unattached from the user's account.
  • The provisioning system deactivates the replaced IMSI in the (a) Home HSS/PCRF or (b) MVNE platform.
  • The IMSI is returned to the "Pool" in PortaBilling's inventory, its status changed back to "Available," ready to be assigned to another subscriber.

Use scenario #2.3: History Audit

  • An administrator needs to track the full lifecycle of a specific partner IMSI.
  • They query the IMSI in PortaBilling's audit log.
  • The system displays a complete history of the IMSI's assignments, showing every account it was attached to, the dates of attachment (via OTA) and detachment (via OTA), demonstrating a clear chain of custody no matter how many times it has been used.