Systems & modules

A complete platform.
In full detail.

Eight connected systems, explored through forty functional modules. From the offer your customer sees to the network that makes it work.

Explore the technical architecture
01 / SELL & OPERATECommercial platform

BSS / OCS · Channels · Retail

02 / ENABLE THE SERVICEService enablement

SIM & eSIM · HLR / HSS / UDM

03 / CONNECT THE NETWORKNetwork foundation

DRA / STP · GTP · Packet core

01 / Commercial platform05 FUNCTIONAL MODULES
BSS / OCS

Turn data usage
into a product.

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.

IN PRACTICE

Launch a prepaid travel product, keep a reusable PAYG wallet, or combine a data pack with a top-up journey.

ONE USAGE EVENT. THE RIGHT COMMERCIAL RULE.
Usage received250 MBSample event
RATING ENGINE
PAY AS YOU GOWallet balance updated.

Apply the rate. Record the charge. Keep the balance in sync.

What’s inside BSS / OCS

FUNCTION → PURPOSE
01

Product & tariff catalogue

Define data allowances, validity, destinations and charging rules. Keep the offer customers buy aligned with the rules the platform applies.

02

Online charging & balances

Rate usage against the applicable product. Deduct from a wallet or allowance, and make the remaining balance available to customer operations.

03

Customer & subscription management

Connect a customer account to its subscriptions, service status and assigned resources. Follow the relationship beyond the first purchase.

04

Supplier & resource administration

Manage resource suppliers and IMSI provisioning or termination. Associate each service with the resources and commercial arrangements behind it.

05

Usage records & reconciliation

Collect CDRs and usage records for reporting, billing review and reconciliation. Give operations a traceable path from activity to charge.

TAKES IN

Orders · Product rules · Network usage

PASSES ON

Balance changes · Usage records · Service events

02 / Service enablement05 FUNCTIONAL MODULES
SIM & eSIM

Every profile.
Its whole lifecycle.

Bring physical SIM resources and digital eSIM fulfilment into one managed lifecycle. Know what is available, what is assigned, and what happens next.

IN PRACTICE

Deliver an eSIM after checkout, allocate profiles to a partner, and follow a connection through activation and ongoing service.

THE SAME RESOURCE. A CLEAR NEXT STEP.
YOUR RESOURCE POOLReady for
its next journey.
ICCID •••• 0841
Profile assigned
InventoryAssignedDeliveredActive

What’s inside SIM & eSIM

FUNCTION → PURPOSE
01

Resource inventory

Organise SIM and eSIM resources by supplier, resource pool and status. Keep inventory visible to the services and channels that consume it.

02

Batch provisioning & allocation

Prepare and assign resources individually or in batches. Support operational launches and partner allocations without repeating each action manually.

03

Multi-vendor eSIM delivery

Integrate eSIM suppliers and provisioning services. Connect an order to its assigned profile and installation information.

04

Lifecycle & service controls

Track assignment, activation and subsequent service changes. Keep profile operations connected to customer and subscription records.

05

OTA & device-assisted workflows

Support over-the-air management and device-assisted provisioning where the SIM configuration requires it. Coordinate these actions with operational workflows.

TAKES IN

Product order · Resource allocation

PASSES ON

Assigned profile · Installation information · Lifecycle events

03 / Service enablement05 FUNCTIONAL MODULES
HLR / HSS / UDM

Know the subscriber.
Control the service.

The subscriber directory behind a working mobile service. Connect identity, service configuration and provisioning across the relevant network generation.

IN PRACTICE

Provision a new subscriber with the right identity and service template, then keep commercial status and network service in sync.

ONE IDENTITY. THE RIGHT SERVICE PROFILE.
Subscriber directory Illustrative
IMSI ••• 0143Travel data
IMSI ••• 0258PAYG service
IMSI ••• 0396Partner plan
HLRHSSUDM

What’s inside HLR / HSS / UDM

FUNCTION → PURPOSE
01

Subscriber identity directory

Maintain the identities and subscriber records used by the network. Associate network-facing identities with the corresponding commercial service.

02

IMSI resource configuration

Work with multiple IMSI resources and resource templates. Organise allocation around the service and network arrangement.

03

Service provisioning templates

Apply repeatable subscriber configurations. Reduce repetitive setup while keeping product and network provisioning consistent.

04

Service status synchronisation

Coordinate subscriber service changes with SIM lifecycle and commercial operations. Give the team a consistent view of the service state.

05

REST-based provisioning integration

Connect subscriber provisioning to business workflows through an integration API. Keep identity administration part of the wider platform flow.

TAKES IN

Subscriber request · IMSI pool · Service template

PASSES ON

Provisioned identity · Network service configuration

04 / Network foundation05 FUNCTIONAL MODULES
DRA / STP

The right message.
The right network.

Route signalling between network systems and partners. Bring SS7 and Diameter routing, message handling and identity-aware rules into a coherent interconnection layer.

IN PRACTICE

Direct a subscriber-related request to the correct network system, based on the subscriber identity and the configured routing policy.

A MESSAGE ARRIVES. A ROUTE IS CHOSEN.
SS7 / MAPDiameter
DRA / STPMatch · Adapt · Route
AppIdHost / RealmGT / IMSI

What’s inside DRA / STP

FUNCTION → PURPOSE
01

Converged signalling routing

Bring DRA and STP functions into the signalling architecture. Connect legacy and Diameter-based network systems through the relevant interfaces.

02

Diameter routing policies

Route requests using Application ID, Host, Realm and IMSI criteria. Express the network relationship as a repeatable routing policy.

03

AVP message handling

Apply configured Diameter AVP modifications when an interconnection requires message adaptation. Keep transformations associated with the routing arrangement.

04

SS7 transport & addressing

Support the relevant M3UA, M2UA, SCCP and MAP signalling paths. Route using Global Title and IMSI addressing rules.

05

IMSI mapping

Map subscriber identities where required by the network arrangement. Coordinate identity translation with the configured signalling routes.

TAKES IN

Partner signalling · Subscriber identity · Route policy

PASSES ON

Selected signalling route · Adapted network message

05 / Network foundation05 FUNCTIONAL MODULES
GTP Proxy

More route options.
One place to steer.

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.

IN PRACTICE

Route a roaming data session to the right gateway group using the subscriber, APN and visited network context.

ONE SESSION. A DELIBERATE DATA PATH.
IMSIAPNVPLMNRAT
GTP ProxyApply route policy
Gateway group A Gateway group B

What’s inside GTP Proxy

FUNCTION → PURPOSE
01

GTP proxy modes

Support GTP-C-only and full-proxy operating models. Select the control and user-plane arrangement for the required integration.

02

Context-aware route selection

Apply routing policies using IMSI, APN, RAT type, VPLMN and MSISDN. Turn session context into a deliberate route decision.

03

Gateway pools & resilience

Organise PGW groups and load-balancing strategies. Include redundancy and recovery behaviour in the routing design.

04

Traffic protection & policy controls

Apply blacklist management and signalling-storm detection. Keep controls close to the session traffic they govern.

05

Usage & external integration

Expose CDRs, statistics and third-party integration points. Connect routing operations to customer, supplier and reporting workflows.

TAKES IN

GTP session · Subscriber / APN / network context

PASSES ON

Gateway selection · Session forwarding · CDR & statistics

06 / Network foundation05 FUNCTIONAL MODULES
PGW / SMF / UPF

A data product needs
a working data path.

The packet-core functions behind mobile data connectivity. Manage sessions, IP addressing and user-plane forwarding in the architecture appropriate to the service.

IN PRACTICE

Establish a customer’s data session, allocate its IP resources and connect usage records back to charging and operations.

CONTROL THE SESSION. CARRY THE DATA.
4G PATHPGWGateway & session services
5G PATHSMF ↔ UPFSession control & user plane
Subscriber
Data network
UE IP poolsUsage recordsResilience

What’s inside PGW / SMF / UPF

FUNCTION → PURPOSE
01

Packet gateway services

Provide the gateway role in the relevant mobile data architecture. Connect the access and roaming arrangement to the intended data service.

02

Session & user-plane functions

Separate session-control and user-plane responsibilities where the architecture calls for it. Integrate the relevant SMF and UPF functions.

03

UE IP address management

Configure dynamic and static UE address pools. Apply the IP allocation model required by the product and deployment.

04

Usage records & charging handoff

Generate and manage the session records needed by charging and reporting. Relate the network session to the commercial service.

05

Virtualised deployment & resilience

Use an NFV-oriented deployment model with high-availability and backup arrangements. Size the environment around the actual session and traffic requirements.

TAKES IN

Session request · Routing decision · Subscriber policy

PASSES ON

Data session · UE IP allocation · Usage records

07 / Commercial platform05 FUNCTIONAL MODULES
Channels

Grow your reach.
Keep the structure clear.

Give distributors and resellers a structured way to work with your products. Connect the channel relationship to catalogue access, subscriptions and usage visibility.

IN PRACTICE

Let a distribution partner offer a selected product range while you retain a clear view of the subscriptions and records behind that channel.

DISTRIBUTED SALES. CONNECTED OPERATIONS.
Your platform
Distributor Reseller Digital partner
Products & resources ↓Orders & usage ↑

What’s inside Channels

FUNCTION → PURPOSE
01

Agent & partner administration

Organise partner accounts and channel relationships. Keep the commercial relationship visible to the operations team.

02

Channel product catalogue

Define the products available to a channel. Make distribution an intentional part of product administration.

03

Subscription package management

Manage the packages sold through partners and associate subscriptions with the originating channel.

04

Channel usage records

Provide CDR administration and usage views for channel operations. Connect distributed sales to the resulting service activity.

05

Operational handoff

Bring channel orders and resource requests into shared provisioning and support workflows. Avoid losing the service context between teams.

TAKES IN

Partner account · Selected products · Channel order

PASSES ON

Channel subscription · Resource request · Usage visibility

08 / Commercial platform05 FUNCTIONAL MODULES
Retail

A sale becomes
a connected service.

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.

IN PRACTICE

Equip a retailer or sales agent to select a plan, issue the appropriate SIM resource and complete the customer activation journey.

FROM A SALES COUNTER TO A WORKING SERVICE.
Sales terminal ●
SELECTED PACKAGETravel data.
Ready to issue.
Customer resourceAssigned when the sale completes
Order → Allocate → Activate
Agent appConnected to the same platform.

What’s inside Retail

FUNCTION → PURPOSE
01

Point-of-sale application

Provide a sales-terminal journey for selecting products and creating service orders. Keep retail sales connected to the shared catalogue.

02

Sales agent application

Give agents a focused interface for selling and handling their service orders. Carry the channel context into the transaction.

03

Provision-on-sale fulfilment

Coordinate resource allocation when a sale is made. Link the sale to the subscriber and provisioning workflow that fulfils it.

04

Bluetooth-assisted SIM workflows

Support compatible Bluetooth SIM writing and management flows where required by a physical SIM sales model.

05

Order & activation tracking

Follow the order through fulfilment and activation. Give the sales and support teams a shared view of the customer’s next step.

TAKES IN

Retail sale · Agent context · Selected package

PASSES ON

Allocated resource · Activation workflow · Order status

Built as a whole. Usable in parts.

Start where you need.
Keep the pieces connected.

A branded launch, an embedded product or a deeper network integration: the right combination starts with your requirements.

Work through your system requirements

The directory groups the platform into eight system areas and forty functional modules. Integration scope, enabled functions and network interfaces are defined for each deployment.

Let’s build something

Your next product
could be mobile.

Tell us about your business. We’ll help you find the right way in.

Start a conversation

Privacy settings

Choose your cookie preferences. You can update them at any time from the footer.

Essential

Website operation, security verification and remembering your privacy choice.

Always active

Analytics

Help us understand how visitors use the website and improve the experience.

Marketing

Help us measure campaigns and make marketing more relevant.

Read the Privacy Policy