When an MVNO launches service on a host operator’s network, subscribers should see nothing but a working service: no sign of the infrastructure underneath. For the vendor handling the integration, the task looks different. The new operator has to fit into a live platform without its traffic ever touching the host’s.
In one of our recent projects, an MVNO launched SMS service on a partner’s network, renting the radio access and SMS infrastructure to start. The host operator’s SMS center was already carrying live traffic, and we needed to build a separate contour inside it for the new operator’s subscribers: their messages had to be recognized, routed and billed under independent rules, with zero impact on the host’s existing traffic. The requirement was strict. One platform, but message handling runs independently per operator, and nothing on one side reflects on the other. Our team reconfigured the signalling stack and Diameter protocol, portability-aware routing for the receiving network, addressing for the new contour, integration with the host’s live billing, and separate anti-spam logic per operator. Some of this work turned out general enough to reuse on later launches instead of rebuilding it each time.
A second part of the project deserves its own mention, and it had nothing to do with traffic. The two sides of the integration ran different signalling interconnection protocols, and reconciling them meant working inside the client’s secured perimeter. Ordinary remote access wasn’t enough. The client needed to control exactly who accessed that perimeter and from what device, so the engineer handling that part was formally employed by the client, signed an NDA, and worked through a client-issued laptop for the duration of the project.
The subscriber never sees any of this. But for anyone evaluating a similar launch, there’s a practical takeaway: the technical side of an integration is usually predictable and easy to scope in engineering hours. Access and security requirements on the client’s side often aren’t, and they tend to move the deadline more than any technical challenge does. At SC.Soft, we build that into project estimates from the start. When an integration touches a client’s secured perimeter, the plan accounts for access provisioning and security sign-off, not just platform configuration.
If you’re evaluating an MVNO launch on your network, or a new operator contour on an existing platform, we’ve handled this kind of integration before and we’re glad to talk through your specific scenario.
