Telecom Is Moving Toward a Multi-Bearer World

The mobile network is starting to become less tied to the ground.

This week, reports emerged that Deutsche Telekom, Orange, Vodafone Group and Telefónica are discussing a potential consortium to bid for EU spectrum supporting direct-to-mobile satellite services. The discussions are still preliminary, but the direction is significant: major mobile operators are increasingly treating satellite connectivity as part of the broader connectivity ecosystem rather than as a separate service.

The same shift is visible elsewhere. Regulators are looking at additional spectrum for space-based wireless services, while the industry continues working on interoperability between terrestrial and non-terrestrial networks.

For operators and MVNOs, this creates a less obvious challenge.

A subscriber may eventually move between terrestrial 4G/5G, private networks, Wi-Fi and satellite connectivity without thinking about which network is carrying the session. The customer experience is expected to remain one service.

Behind that experience, however, provisioning, entitlement management, usage records, charging, partner settlement and service policies become considerably more complicated.

This is where the telecom stack starts to matter. A multi-bearer connectivity model cannot be supported efficiently if every new network partner requires another isolated operational workflow. Platforms need to be able to absorb new connectivity models without rebuilding the surrounding BSS and OSS processes each time.

For companies building MVNO and IoT services, this could become particularly important. TelcoEdge’s focus on API-driven subscriber management, provisioning, billing and multi-network operations reflects the broader industry move toward making connectivity infrastructure more programmable rather than treating each network relationship as a separate system.

The interesting part is that satellite connectivity may not replace mobile networks at all. It may simply become another layer that the telecom platform has to orchestrate.

If customers eventually expect connectivity to follow them wherever terrestrial coverage ends, should operators start designing their BSS/OSS around the concept of a single connectivity experience rather than individual networks?

I’d give “one connectivity experience” a measurable definition for each service. A sensor upload that can wait and a live voice call need different continuity targets. For each access transition, I’d record the packet gap, whether the application session survives or reconnects, and the policy applied. Then correlate that with the usage records. If the customer reports an interruption while billing sees a successful session, support needs a shared timeline to explain the mismatch. That link between service evidence and BSS/OSS deserves a place in the design.