Solutions
Alepo AAA Solutions
Telco Type
Tier-1 Mobile Network Operator
Country
Saudi Arabia
Upgrading a Live BSS and AAA Estate Without Downtime: A Middle East Tier-1 Program
A case study of how a Middle East Tier-1 operator, the largest telecommunications company in its market serving fixed and mobile broadband subscribers, upgraded its BSS and AAA platforms ahead of demand growth, with no subscriber-visible downtime and every customization retained. Prepared for operators evaluating platform upgrades on live networks.
Zero
subscriber-visible downtime through the full migration
100%
of existing customizations retained and ported
No new hardware
capacity gains delivered on the existing estate
Since 2012
upgrade executed within a long-term partnership
Background
The operator anticipated that subscriber growth and rising data consumption on its fixed broadband network would outpace its existing BSS and AAA platforms. Rather than wait for degradation, it initiated a proactive upgrade with three aims: system stability, security, and scalability.
The Upgrade-in-Place Decision
Upgrading live revenue-critical systems carries a different risk profile than a greenfield deployment. The program was framed around four requirements, the same ones any operator faces when upgrading platforms already carrying traffic:
Continuity is non-negotiable
The migration had to complete with no downtime and no visible change for subscribers.
Customizations are assets, not debt
Years of operator-specific configuration had to be retained and ported to the new platform, not rebuilt.
Security hardening belongs in scope
Safeguards recommended by the operator’s own security team were built into the upgrade itself, not deferred to a later phase.
Capacity growth without capital spend
Performance gains had to come from the platform, on existing hardware.
Program Scope
The upgrade covered the full BSS stack (CRM, web self-care, dunning portal, web services, and reporting) alongside the AAA platform, voucher management, recharge management, and monitoring tools. Existing integrations were preserved and extended across the operator’s broadband access infrastructure, external accounting systems, messaging, and provisioning services.
What the Upgraded Platform Supports
Resilient charging continuity
An automatic emergency mode generates usage records locally if database connectivity is lost and reconciles them once restored, supporting accounting continuity through the transition.
Multi-level authentication
Port-based, CLID-based, and credential-based, reducing network noise and improving reliability.
Bandwidth on demand
Subscribers purchase temporary speed boosts directly from self-care.
Configurable service provisioning
A provisioning framework that integrates with third-party and network systems without custom development for each flow.
Outcomes
The migration completed with no subscriber-visible downtime or service change. All existing customizations, accumulated over a partnership running since 2012, were retained and ported, and the security team’s hardening requirements were applied within the upgrade window rather than deferred. Following the upgrade, the operator recorded its fastest CRM processing times to date, a multi-fold increase in network capacity on unchanged hardware, and improved operational efficiency within a few months of deployment.
Accumulated customization was treated as an asset: upgrading in place ported years of operator-specific configuration instead of rebuilding it.
Capacity came from software: the gains were measured on unchanged hardware, with no hidden hardware refresh.
Security hardening was applied inside the upgrade window, not deferred to a later phase competing with the next budget.
What to Verify Before Upgrading a Live BSS and AAA Estate
Checks drawn from this program, useful regardless of vendor:
Can the migration be executed with no subscriber-visible downtime, and who has proven it at your scale?
What happens to your accumulated customizations: ported, rebuilt, or lost?
Is your security team’s input part of the upgrade scope, or handled after go-live?
Can capacity targets be met on existing hardware, or does the upgrade conceal a hardware refresh?
How is charging continuity protected if connectivity fails mid-upgrade?
