Procescom

MNO Core Network replacement

Replace a legacy MNO core with a virtualised, standards-conformant successor — without losing a subscriber. An 11-phase plan with explicit sign-off gates, carrier-grade DR with hard RTO/RPO targets, and a clean evolution path from 4G EPC into 5G SA on the same operations team.

MNO Core Network replacement illustration
Standards3GPP Releases 8–16GSMA IR.92 / IR.65 / IR.88ETSI TS 187 001VMware ESXi / Proxmox / KVM

11 phases, formal sign-off at every gate

HLR build → LLD documentation → physical infrastructure → core servers → signalling components → support servers → media servers → test environment → MNO IP/signalling integration → MNO routing & CAMEL → final E2E and cutover. Each phase has explicit entry and exit criteria, sign-off before the next begins, and a fallback plan if something fails the test.

11 phases, formal sign-off at every gate
Carrier-grade DR with hard targets

Carrier-grade DR with hard targets

Active/Standby on every critical service, Master/Slave database replication with synchronous commits, multi-home SIGTRAN with automatic failover. A geo-redundant secondary site holds DB, SBC, and API Gateway. RTO four hours, RPO fifteen minutes for database tiers, with a DR drill every three months — measured, not promised.

5G SA on the same operations team

The 4G EPC stack evolves into 5G Standalone on the same VMs and the same hypervisor. SCP and NRF replace the DRA for routing; HTTP/2 SBI APIs (TS 29.518 et al.) sit alongside Diameter; AMF, SMF, UDM, PCF, and CHF take over as the network functions. The NOC keeps Grafana/Prometheus/Zabbix; nothing about how you operate has to change.

5G SA on the same operations team