Product & tariff catalogue
Define data allowances, validity, destinations and charging rules. Keep the offer customers buy aligned with the rules the platform applies.
Eight connected systems, explored through forty functional modules. From the offer your customer sees to the network that makes it work.
Explore the technical architectureBSS / OCS · Channels · Retail
SIM & eSIM · HLR / HSS / UDM
DRA / STP · GTP · Packet core
A flexible commercial engine for bundles, pay-as-you-go balances and your own service rules. Keep the product, the customer and the charge in the same operational picture.
Launch a prepaid travel product, keep a reusable PAYG wallet, or combine a data pack with a top-up journey.
Apply the rate. Record the charge. Keep the balance in sync.
Define data allowances, validity, destinations and charging rules. Keep the offer customers buy aligned with the rules the platform applies.
Rate usage against the applicable product. Deduct from a wallet or allowance, and make the remaining balance available to customer operations.
Connect a customer account to its subscriptions, service status and assigned resources. Follow the relationship beyond the first purchase.
Manage resource suppliers and IMSI provisioning or termination. Associate each service with the resources and commercial arrangements behind it.
Collect CDRs and usage records for reporting, billing review and reconciliation. Give operations a traceable path from activity to charge.
Orders · Product rules · Network usage
Balance changes · Usage records · Service events
Bring physical SIM resources and digital eSIM fulfilment into one managed lifecycle. Know what is available, what is assigned, and what happens next.
Deliver an eSIM after checkout, allocate profiles to a partner, and follow a connection through activation and ongoing service.
Organise SIM and eSIM resources by supplier, resource pool and status. Keep inventory visible to the services and channels that consume it.
Prepare and assign resources individually or in batches. Support operational launches and partner allocations without repeating each action manually.
Integrate eSIM suppliers and provisioning services. Connect an order to its assigned profile and installation information.
Track assignment, activation and subsequent service changes. Keep profile operations connected to customer and subscription records.
Support over-the-air management and device-assisted provisioning where the SIM configuration requires it. Coordinate these actions with operational workflows.
Product order · Resource allocation
Assigned profile · Installation information · Lifecycle events
The subscriber directory behind a working mobile service. Connect identity, service configuration and provisioning across the relevant network generation.
Provision a new subscriber with the right identity and service template, then keep commercial status and network service in sync.
Maintain the identities and subscriber records used by the network. Associate network-facing identities with the corresponding commercial service.
Work with multiple IMSI resources and resource templates. Organise allocation around the service and network arrangement.
Apply repeatable subscriber configurations. Reduce repetitive setup while keeping product and network provisioning consistent.
Coordinate subscriber service changes with SIM lifecycle and commercial operations. Give the team a consistent view of the service state.
Connect subscriber provisioning to business workflows through an integration API. Keep identity administration part of the wider platform flow.
Subscriber request · IMSI pool · Service template
Provisioned identity · Network service configuration
Route signalling between network systems and partners. Bring SS7 and Diameter routing, message handling and identity-aware rules into a coherent interconnection layer.
Direct a subscriber-related request to the correct network system, based on the subscriber identity and the configured routing policy.
Bring DRA and STP functions into the signalling architecture. Connect legacy and Diameter-based network systems through the relevant interfaces.
Route requests using Application ID, Host, Realm and IMSI criteria. Express the network relationship as a repeatable routing policy.
Apply configured Diameter AVP modifications when an interconnection requires message adaptation. Keep transformations associated with the routing arrangement.
Support the relevant M3UA, M2UA, SCCP and MAP signalling paths. Route using Global Title and IMSI addressing rules.
Map subscriber identities where required by the network arrangement. Coordinate identity translation with the configured signalling routes.
Partner signalling · Subscriber identity · Route policy
Selected signalling route · Adapted network message
Put policy between a session request and its destination gateway. Manage route selection, gateway groups and operational controls without treating every network path as a separate business.
Route a roaming data session to the right gateway group using the subscriber, APN and visited network context.
Support GTP-C-only and full-proxy operating models. Select the control and user-plane arrangement for the required integration.
Apply routing policies using IMSI, APN, RAT type, VPLMN and MSISDN. Turn session context into a deliberate route decision.
Organise PGW groups and load-balancing strategies. Include redundancy and recovery behaviour in the routing design.
Apply blacklist management and signalling-storm detection. Keep controls close to the session traffic they govern.
Expose CDRs, statistics and third-party integration points. Connect routing operations to customer, supplier and reporting workflows.
GTP session · Subscriber / APN / network context
Gateway selection · Session forwarding · CDR & statistics
The packet-core functions behind mobile data connectivity. Manage sessions, IP addressing and user-plane forwarding in the architecture appropriate to the service.
Establish a customer’s data session, allocate its IP resources and connect usage records back to charging and operations.
Provide the gateway role in the relevant mobile data architecture. Connect the access and roaming arrangement to the intended data service.
Separate session-control and user-plane responsibilities where the architecture calls for it. Integrate the relevant SMF and UPF functions.
Configure dynamic and static UE address pools. Apply the IP allocation model required by the product and deployment.
Generate and manage the session records needed by charging and reporting. Relate the network session to the commercial service.
Use an NFV-oriented deployment model with high-availability and backup arrangements. Size the environment around the actual session and traffic requirements.
Session request · Routing decision · Subscriber policy
Data session · UE IP allocation · Usage records
Give distributors and resellers a structured way to work with your products. Connect the channel relationship to catalogue access, subscriptions and usage visibility.
Let a distribution partner offer a selected product range while you retain a clear view of the subscriptions and records behind that channel.
Organise partner accounts and channel relationships. Keep the commercial relationship visible to the operations team.
Define the products available to a channel. Make distribution an intentional part of product administration.
Manage the packages sold through partners and associate subscriptions with the originating channel.
Provide CDR administration and usage views for channel operations. Connect distributed sales to the resulting service activity.
Bring channel orders and resource requests into shared provisioning and support workflows. Avoid losing the service context between teams.
Partner account · Selected products · Channel order
Channel subscription · Resource request · Usage visibility
Connect the physical point of sale to the same product and provisioning platform. Give a sales team a practical path from choosing a package to delivering a service.
Equip a retailer or sales agent to select a plan, issue the appropriate SIM resource and complete the customer activation journey.
Provide a sales-terminal journey for selecting products and creating service orders. Keep retail sales connected to the shared catalogue.
Give agents a focused interface for selling and handling their service orders. Carry the channel context into the transaction.
Coordinate resource allocation when a sale is made. Link the sale to the subscriber and provisioning workflow that fulfils it.
Support compatible Bluetooth SIM writing and management flows where required by a physical SIM sales model.
Follow the order through fulfilment and activation. Give the sales and support teams a shared view of the customer’s next step.
Retail sale · Agent context · Selected package
Allocated resource · Activation workflow · Order status
A branded launch, an embedded product or a deeper network integration: the right combination starts with your requirements.
Work through your system requirementsThe directory groups the platform into eight system areas and forty functional modules. Integration scope, enabled functions and network interfaces are defined for each deployment.
Tell us about your business. We’ll help you find the right way in.
Start a conversation