Products & Services

BSS Suite

One multi-tenant suite for every telecom business, from catalogue to cash.

Bonyan BSS Suite is a complete, carrier-grade business support system: customer management, product catalogue and pricing, order orchestration, real-time charging, billing, payments, collections and settlement, with open APIs on top. One installation can serve many brands, each fully isolated.

It is sold as focused solutions. An operator, an MVNO or a wholesale department buys the part it needs and grows into the rest on the same installation. Bonyan System delivers, localises and operates it.

Request a briefing

Billing care showing an enterprise bill with charges by service, charges from sub-accounts and the payment applied
At a glance

Built for the Operators It Serves

One installation, many isolated brands
1 → n
Charging across every generation, including 5G converged charging
2G–5G
TM Forum Open APIs for channels, partners and IT
9
Persian and English on the same records, with Jalali dates
فاEN
Solutions & use cases

One Suite, Six Solutions

Full-stack platforms for each kind of business, a front office that works over existing billing, and wholesale roaming, all on the same installation.

Full stack

MVNE Platform

Many mobile brands on one multi-tenant BSS, for hosts, enablers and MVNOs.

Full stack

B2B Platform

Enterprise hierarchies, a business catalogue and one bill per company.

Full stack

IoT Management System

Fleets of SIMs, pooled plans and device-traffic rating.

Full stack

MVNO BSS

A single MVNO's whole operation on one installation.

Front office

CRM & Order Management

A new front office and order orchestration over existing billing.

Wholesale

Roaming Management System

Roaming partners, TAP, RAP and settlement in-house.

Capabilities

Why Operators Choose the Suite

The advantages that every solution inherits from the suite underneath.

01 · Multi-tenancy

Many Brands on One Installation

The suite is multi-tenant by design. An operator, an MVNE or a group of companies runs several brands on one installation, and each brand is a tenant with its own customers, catalogue, numbers, bill cycles, invoices and staff.

  • Isolation is enforced in every module (CRM, catalogue, orders, charging and billing), not filtered in reports
  • Each API token and each agent login is scoped to one tenant
  • A new brand is a new tenant on a running platform, not a new BSS project
  • Software, infrastructure, upgrades and the operations team are shared, so the cost per brand falls
One installation · three tenants
Tenant 1 · نکسا موبایل
CRM account list signed in as the first virtual operator: its brand in the header, only its own NEXA accounts
Tenant 2 · ValuTel
The same CRM screen signed in as a second operator: its own brand and VALU accounts, nothing of the first

The same CRM screen, signed in as two different operators. Each sees its own brand, accounts and numbers, and nothing of the other. Demo data.

02 · One catalogue

Design an Offer Once, Sell It Everywhere

Offers, bundles, allowances and discounts are designed once in pricing design and published together to sales, real-time charging and billing.

  • No re-keying of tariffs between CRM, charging and billing
  • Change sets let a launch be prepared, validated and published in one step
  • The same catalogue serves consumer, enterprise, IoT and MVNO offers
Pricing design · Prepaid 30 GB
Prepaid 30 GB
  • Data allowance 30 GB
  • Voice 500 min
  • Roaming add-on
  • Launch discount −20%
Published to salesReal-time chargingBilling
One change set · every channel and engine updated together
03 · Real-time charging

Convergent Charging from 2G to 5G

Voice, data and messaging are charged as the session happens, against one balance, for prepaid and postpaid subscribers alike.

  • Diameter Gy / Ro for 4G, 5G converged charging, CAMEL for legacy networks
  • Spending-limit counters for policy control
  • Offline rating for CDR files, roaming and interconnect on the same pricing
Balance · subscriber 98912•••••31
Data18.6 of 30 GB
Voice175 of 500 min
2G / 3G CAMEL4G Diameter Gy / Ro5G CHFSpending limits
Prepaid and postpaid on the same balance
04 · Order to activation

Every Order Tracked to the Network

Orders captured in CRM, in a shop or through an API are orchestrated through billing, number and SIM inventory and network activation, and the result is written back to the customer record.

  • Each step visible with its state and timing
  • Failed steps are retried or handled without re-entering the order
  • The agent sees the activation in the customer's history
Order INT-2-85449 · activation
  • Validate against catalogue & CRMDone
  • Create customer in billingDone
  • Assign number & SIMDone
  • Provision HLR / HSS / UDMRetried · done
  • Write result back to CRMRunning
Fallout handled · failed steps retried without re-keying the order
05 · Open APIs & standards

Channels and Partners Plug In

Self-care apps, dealers, partners and the operator's own IT use the suite through TM Forum Open APIs behind an API gateway, with 3GPP and GSMA interfaces towards the network and roaming partners.

  • Nine TM Forum Open APIs for catalogue, orders, customers, usage, balances, bills and payments
  • Integration platform for files, events and third-party systems
  • Standard interfaces keep integration predictable
API gateway · published interfaces
TMF620 CatalogueTMF622 Product orderTMF629 CustomerTMF632 PartyTMF635 UsageTMF654 Prepay balanceTMF666 AccountTMF676 PaymentTMF678 Customer bill
Network & partner standards
3GPP chargingGSMA TAP / RAP / NRTRDEOAuth 2.0
06 · Built for the local market

Persian, Right-to-Left and Jalali, Built In

The suite is localised as part of the product, not as a customisation: agents work in Persian or English on the same records.

  • Right-to-left screens in Persian, left-to-right in English
  • Jalali dates and Jalali bill cycles
  • Rial pricing, local tax and national integrations
Account · نیروگستر پارس
  • Languageفارسی · English
  • ScreensRight-to-left · left-to-right
  • Calendar۱۴۰۵/۰۷/۲۱ · 13 Oct 2026
  • Bill cycleJalali month
  • CurrencyRial
Reference architecture

The Suite and Its Ecosystem

The suite in context: the channels that use it, the integration layer, the OSS and network it drives, and the external parties, data platforms and shared services around it. Solid lines are requests in real time; dashed lines are files and batch; the amber line is the online charging path from the network.

BSS Suite reference architecture in eight zones: channels and engagement; integration and APIs; the BSS Suite with CRM, Pricing Design Center, Billing Care, Collections, BRM, Pipeline Manager, IN charging and ECE; OSS with order orchestration, inventory, activation, service design and orchestration, assurance and mediation; the network and 5G core; external parties; data and analytics; and shared services
In the product

A Look at the Suite

Screens from the product, shown with demo data.

Pricing design screen listing catalogue charge offers
Pricing design: the product catalogue with charge offers ready to publish.
Order management process history
Order orchestration: each activation step, from validation to the CRM write-back, with its state.
Billing screen showing an enterprise account hierarchy
An enterprise hierarchy: the enterprise, its regional accounts and their bill units.
Billing care payment details
A payment allocated across the bills it settles.
Why it matters

Benefits

Buy What You Need

Start with one solution and add the rest on the same installation.

Many Brands, One Platform

Every brand is an isolated tenant on shared software and operations.

One Catalogue

An offer is designed once and reaches sales, billing and charging together.

Standards-Based

TM Forum, 3GPP and GSMA interfaces keep integration predictable.

Talk to us

See the Suite End to End

A live demonstration follows an order from capture in CRM through activation, charging and the bill.

Request a briefing

Or e-mail info@bonyansystem.com.