IMS Registration: MVNO Launch Readiness After 2G/3G

For an MVNO, a 2G or 3G shutdown does not merely remove an older access layer. It changes the commercial definition of a serviceable subscriber, the device population that can be acquired, and the liabilities carried by the host agreement. IMS registration now sits at the centre of launch readiness: it determines whether voice, SMS, emergency calling and number-portability journeys remain operational when circuit-switched fallback disappears.

A network sunset resets the MVNO launch baseline

Legacy fallback allowed wholesale acceptance teams to treat mobile data attach and voice continuity as related but partly separable workstreams. That assumption expires with the radio layer. An LTE-capable handset that attaches for data but cannot register with IMS is not voice-ready. The same principle applies to 5G devices where the commercial proposition still depends on IMS for voice and messaging.

The host must therefore state the scope of VoLTE access precisely. Availability may cover all MVNO IMSIs, selected MNC/MCC ranges, approved tariff profiles, certified device cohorts, or some combination of the four. A general statement that VoLTE is active on the host network is commercially insufficient. Wholesale acceptance needs an attributable entitlement rule and evidence that it survives activation, barring, suspension and reactivation.

Launch gates should cover VoLTE, SMS over IMS and emergency calling before commercial traffic begins. The test plan also needs to follow the subscriber lifecycle through MNP, including the interval between donor-network release, recipient activation and profile recovery after a failed provisioning event. The host’s IMS, HLR/HSS, AuC and policy-control configuration must apply consistently to the MVNO range rather than inheriting assumptions built for the host’s retail base.

Device certification is part of that operating model. The host may retain an IMS whitelist even where the MVNO controls handset distribution or eSIM acquisition. Ownership must be explicit for device submission, firmware regression testing, compatibility publication and customer remediation. Otherwise, each party can meet its narrow obligation while the subscriber remains unable to place a call.

A Tier-2 MNO, Western Europe, ~18M subscribers, found that a national sunset date concealed materially different exposure across regional RAN clusters. Urban traffic had largely migrated to IMS, while selected rural areas still carried a disproportionate volume of fallback voice. The revised wholesale plan used phased acceptance windows by footprint, handset cohort and traffic profile. That approach identified migration cost before the affected MVNO base generated a concentrated support and churn event.

Voice, SMS and emergency failures carry different commercial consequences

An IMS failure should not be treated as one generic incident category. Voice, messaging and emergency service have different customer effects, regulatory implications and settlement consequences. The common commercial risk is a mismatch between the MVNO proposition and the host’s retained control of policy, entitlement and routing.

VoLTE registration depends on aligned configuration across several control points. The data session may be available while the IMS path fails because APN selection, P-CSCF discovery, SIP authentication, subscriber provisioning, device entitlement or policy treatment differs from the approved profile. Acceptance evidence should isolate these layers. A successful call on a host-retail SIM says little about the MVNO configuration.

SMS over IMS also requires explicit wholesale scope. A partial configuration can leave data and VoLTE operational while OTP delivery, bank alerts and porting-related messages fail. This is a commercially damaging fault because the subscriber often attributes it to the MVNO, while the root cause may sit in IMS routing, subscriber flags or the host SMSC path. Complaint volumes can rise before network monitoring records a clear service outage.

Emergency calling requires separate confirmation for routing, location handling and test responsibility across the MVNO IMSI range. Test cases should include subscribers with no credit, ordinary outbound barring and incomplete post-port provisioning. The parties should also document expected behaviour during limited-service registration, roaming, eSIM download failure states and the activation window after MNP. Regulatory responsibility cannot be inferred from a standard voice acceptance result.

Fallback arrangements should be represented accurately in steering papers and customer-impact models. CSFB, 2G voice and 3G voice may persist in selected areas during migration, but none constitutes durable service control once retirement is scheduled. Treating residual coverage as mitigation understates the volume of subscribers that will fail when they move between regions or when the next radio cluster is withdrawn.

Device compatibility then becomes a churn variable rather than a technical footnote. Unsupported imported handsets can generate repeat contacts, returns, replacement subsidies and goodwill credits even when the host network performs to specification. The business case should distinguish host-side registration faults from excluded-device incidents, but the MVNO still needs a funded policy for both. A technically correct exclusion does not remove the acquisition cost already spent on the affected subscriber.

The sunset business case should be priced as a recurring operating cost

IMS readiness is not a one-off integration line that disappears after acceptance. Device releases, firmware changes, provisioning updates and regional shutdown phases create a continuing operating requirement. The wholesale model should assign these costs against the revenue protected through retention, lower complaint volumes and reduced dependency on legacy-network operations.

Implementation charges should separate IMS profile work, provisioning changes, test-SIM supply, device certification and formal acceptance. Recurring charges should then state whether VoLTE, SMS over IMS, emergency-service validation and operational support are included in the per-active-IMSI rate, recovered through a bundled fee, or funded by a minimum commitment. Ambiguity moves cost into change requests and weakens the MVNO’s ability to forecast gross margin.

Settlement cadence matters most during the first billing periods after sunset. Monthly usage and active-base reconciliation gives both parties an earlier view of registration anomalies, unexpected routing and disputed subscriber states. Quarterly true-ups are too slow when a provisioning defect can affect acquisition, usage and churn within days. A defined post-sunset review period should permit operational data to be reconciled before a defect becomes a recurring invoice dispute.

Implementation cost allocation

One-off IMS profile, provisioning, test-SIM and acceptance work; identify host-funded, MVNO-funded and shared items.

Recurring wholesale charge

Per-active-IMSI or bundled service fee for VoLTE, SMS over IMS and relevant IMS operational support.

Settlement cadence

Monthly usage and active-base reconciliation, with defined dispute windows and a post-sunset anomaly review period.

Revenue-at-risk measure

Unsupported-device exposure, projected forced migration rate, and churn risk by device cohort and tenure.

Service-credit trigger

Agreed KPI breach for MVNO IMSI ranges, separated from handset-specific compatibility exclusions.

Service credits should attach to measurable wholesale failures. A sustained IMS registration failure above an agreed threshold, affecting defined MVNO ranges and provisioning states, is suitable for contractual measurement. A device-specific defect outside the certified cohort is not. The contract should specify the denominator, measurement source, exclusion logic and cure period so that a credit can be calculated without reopening the underlying technical debate.

Margin protection also requires advance treatment of high-cost emergency, roaming and interconnect scenarios. Legacy fallback may previously have hidden the actual routing path or shifted cost into an established host-retail arrangement. Once traffic moves to IMS, the wholesale schedule must identify charging responsibility, rating treatment and exception handling before the MVNO sets its tariff. Otherwise, the migration can preserve service while diluting contribution margin.

Contracts need a sunset operating model, not a one-time migration appendix

A durable agreement treats the host sunset roadmap as a controlled contract input. Notification periods should cover changes to 2G, 3G, CSFB, IMS policy, device certification and SMS routing. The obligation should address regional sequencing and material profile changes, not only the final national switch-off date. The MVNO needs enough notice to update device policy, migration communications, support scripts and financial forecasts.

The operating schedule should assign RACI ownership for IMS provisioning, physical SIM and eSIM profile configuration, compatibility publications, emergency-call validation, complaint handling and regulator-facing incident evidence. Control and liability should follow each other. If the host controls the whitelist or policy rule, the MVNO should not carry unlimited liability for a change it cannot inspect or reverse. If the MVNO distributes unsupported devices, the host should not fund the resulting compatibility claims.

Acceptance criteria should cover activation, inbound and outbound VoLTE, SMS over IMS, MNP, barred states, emergency calls and recovery after a provisioning fault. The evidence pack should identify device model, software version, IMSI range, tariff profile, location and expected result. This creates a usable baseline for incident management and service-credit assessment after go-live.

Unsupported-device and legacy machine-to-machine estates need a transparent exception process. The schedule should state cost ownership, migration deadlines, communications approval rights and the point at which continued support becomes commercially unreasonable. Exceptions without an expiry date tend to become an unfunded service tier, particularly where low-usage lines remain profitable only while no device replacement is required.

A Greenfield MVNO, post-2023, multi-IMSI stack should negotiate readiness evidence for each host. A successful integration in one market does not prove that another host uses the same entitlement logic, emergency routing, device policy or SMS treatment. Multi-IMSI architecture can broaden coverage and improve commercial optionality, but it also multiplies acceptance matrices, settlement interfaces and exception ownership.

The commercial question is no longer whether an MVNO can access LTE or 5G coverage. It is whether its host contract, device policy and settlement model can sustain IMS-based voice and messaging without legacy fallback, while containing churn and exception costs as sunset dates advance.