The messaging stack
MVNOs launch on.
Whether you are standing up a new MVNO or pulling an existing one off an MVNE's messaging dependency, BroadNet supplies the layers that decide your margins: hosted SMSC, A2P monetization with an inline firewall, sender-ID governance, HLR intelligence, eSIM enablement, and the wholesale routes underneath — operated since 2003.
The stack
Six layers. Take what your launch needs, add the rest later.
Every layer runs standalone against your host MNO or MVNE, and every layer shares the same traffic ledger when combined. No forklift migration, no all-or-nothing contract.
Hosted SMSC
Carrier-grade SMS core without the capex — SMPP 3.4/5.0, SS7 MAP, active-active HA, real-time CDRs. Run it managed in BroadNet's Tier-3 MENA hosting, on-prem, or hybrid.
Learn moreA2P monetization + firewall
The firewall that classifies grey-route traffic and the commercial engine that converts it to billed A2P — one stack, one traffic ledger, with the recoverable share measured on your own traffic.
Learn moreSender-ID registry
Centralized registration with KYB verification and approval workflows — the 10DLC-style governance layer regulators increasingly expect, sized for an MVNO's brand list.
Learn moreHLR / number intelligence
Live MAP SRI-SM and MNP lookups across 200+ countries. Know which numbers ported in, which ported out, and which are reachable — before you route or bill a message.
Learn moreeSIM enablement
GSMA SGP.22 Remote SIM Provisioning — SM-DP+ and SM-DS with an HSM-backed vault. The same platform family behind BroadNet's consumer travel eSIM brand.
Learn moreWholesale routes
1,000+ direct operator connections and 200+ countries of A2P termination, live since 2003. Your enterprise messaging revenue rides routes BroadNet already operates.
Learn moreLaunch timeline
Discovery to live traffic, in honest ranges.
Three to six months end to end for a full stack; a single layer can be live in weeks. The variable is almost always the host-MNO or MVNE interface work — these ranges assume it goes normally, not perfectly.
Discovery & design
Numbering plan, host-MNO or MVNE interfaces, regulatory posture, traffic forecast. Output is a signed integration design: binds, routes, registry scope, and billing model.
Integration & test
SMPP/SS7 binds brought up against staging, firewall in mirror mode, sender IDs migrated into the registry, CDR reconciliation dry-runs against your BSS.
Go-live & ramp
Controlled traffic ramp with the firewall enforcing, commercial A2P agreements activated, 24/7 NOC handover. Recovery reporting starts with the first billing cycle.
Size the opportunity
Run your own numbers before we run ours.
Interactive estimate
How much A2P revenue is your network leaking?
Move the sliders to your network's shape and your own assumptions. The model prices the grey-route gap at your own effective rate — it is your estimate, not a BroadNet benchmark.
SIMs on your network (or your MVNO base)
OTPs, alerts, notifications terminating per SIM
Blended per-message termination rate you bill today
Traffic arriving over SIM boxes, SS7 bypass or unmonitored aggregator binds
How much of the identified grey traffic you expect to bring onto billed routes
A2P value arriving over unbilled routes at your grey-share estimate
the grey-route value you expect to convert to billed A2P
- Grey share and conversion are your own inputs. BroadNet does not publish a benchmark for either — the operator assessment measures your actual grey-route volume in mirror mode.
- Leakage is priced at your current effective rate.
Estimate from your inputs only — not a BroadNet benchmark or a promised outcome.
Proof
The same stack, already carrying operator traffic.
running BroadNet inside MENA, Africa and Asia
grey-route volume sized on your own traffic before enforcement
re-offered to senders as billed A2P under your commercial terms
firewall decisions and settlement lines in one audit trail
“Challenge: a growing MVNO had no visibility into which A2P traffic its MVNE was actually billing. Approach: BroadNet's firewall ran in mirror mode first, then moved to enforcement and commercial conversion.”
Six answers
for the launch committee.
Yes. The stack is modular — most MVNOs start with one layer (typically the firewall + A2P monetization, or HLR lookups) connected alongside the MVNE, then move layers over as contracts allow. The hosted SMSC only becomes relevant when you want messaging custody out of the MVNE's hands; nothing forces that on day one. Each layer exposes standard interfaces (SMPP, SS7 MAP, REST), so the MVNE relationship stays intact while you regain visibility and revenue control.
Both models exist, and the honest answer is that the right one depends on your traffic baseline. A revenue-share arrangement keeps upfront cost near zero and aligns incentives while your A2P volumes are still forming; a license flips the economics in your favour once recovered revenue is predictable. Many engagements start on revenue share and convert to license after the first year's recovery curve is known. Any figures discussed pre-audit are illustrative estimates, not contract terms.
False positives are the first thing an MVNO should ask about, because a blocked OTP is a support call and a churn risk. BroadNet deployments start in mirror mode — the firewall classifies live traffic without enforcing — so you see exactly what would be blocked before anything is. The rule engine and behavioural ML run in parallel with per-sender allow-lists, and every block decision is logged with a reason code, so the ramp from mirror to enforcement is driven by your own review, not ours.
Sender-ID continuity is handled in the registry layer. Existing sender IDs are bulk-imported from the incumbent whitelist with KYB deferred, so approved brands keep delivering through the cutover without re-registration. Number portability is covered on the routing side: HLR/MNP lookups resolve ported-in and ported-out numbers in real time, so messages follow the subscriber rather than the stale prefix.
For messaging layers: your MVNO licence, an agreed interface to the host MNO or MVNE (SMPP bind or SS7 access, depending on your model), and a view of current A2P traffic if any exists. For eSIM enablement: your profile requirements and the host network's provisioning interfaces. Discovery exists precisely to inventory this — most gaps found there (numbering ranges, GT addressing, registry scope) are resolved during integration rather than blocking it.
The typical envelope is three to six months end to end, and where you land in it depends mostly on the host-MNO or MVNE interface work, not on BroadNet's side. A single-layer start (firewall in mirror mode, or HLR lookups over REST) can be live in weeks. A full stack with hosted SMSC, registry migration and eSIM enablement sits at the longer end. The timeline section above reflects ranges we consider honest, not best cases.
Need a working session with the engineers who run these stacks? Talk to our carrier team →
Related
The rest of the operator platform.
Protect and monetize at the signaling layer.
In-network SMS and SS7 firewalls stop grey routes and fraud at line rate while legitimate traffic flows untouched.
Scope your stack
Tell us where your MVNO is — we'll map the stack to it.
A carrier engineer replies within one business day with a concrete starting layer, an integration outline against your host MNO or MVNE, and an illustrative recovery estimate for your traffic shape.
- Launching MVNOs — numbering, binds, registry and eSIM from day one
- Scaling MVNOs — recover A2P revenue without breaking the MVNE contract
- MVNEs — white-label the stack under your own enablement platform