For decades, telecom OSS has been built around a simple assumption: the network is fixed.
Sites don’t move. Cells don’t disappear. Coverage doesn’t orbit the earth.
Non-Terrestrial Networks (NTN) break every one of these assumptions.
As LEO and MEO satellite constellations become extensions of 5G networks, operations teams are discovering something uncomfortable: you cannot operate an orbital network with terrestrial OSS thinking. The problem is not only radio or transport. The real disruption is happening in the OSS layer.
NTN is forcing OSS to evolve from a passive monitoring stack into an orbital-aware operational control system.
In a terrestrial network, a cell is tied to a tower. Its neighbors are known. Its coverage is planned. KPIs flow continuously. If a node disappears, it is almost always a fault.
In an NTN network, none of this is true.
A satellite is constantly moving. Its beams sweep across the earth. A logical NTN cell may exist over a city for ten minutes, vanish for an hour, and then reappear with a different geometry, a different gateway, and different service conditions.
Here, coverage is not a planning artifact. Coverage is a real-time variable.
This single difference cascades into everything else:
And this is where classical OSS models collapse.
Most OSS platforms assume always-on infrastructure: continuous telemetry, persistent cells, and communication loss as an exception. In NTN, both observability and provisioning are intermittent.
Beam visibility depends on orbital mechanics and KPIs are meaningful only within active service windows.
Before monitoring begins, OSS must resolve context:
Monitoring becomes orbit- and scheduler-aware. Telemetry without context is noise. Provisioning resembles coordinated orbital activation rather than static service turn-up.
Assurance also shifts. The object of interest is no longer the node – it is the live service footprint on earth: which geo-locations are under which beams, at what quality, now.
Beam-level KPIs and geo-correlated visualization become operational primitives.
Rakuten Symphony’s OSS stack is evolving with a simple principle:
NTN cannot be “integrated.” It must be native.
Instead of forcing satellites into terrestrial abstractions, the platform is being extended to model the things NTN actually cares about.
Rakuten Assurance is shifting from static counter dashboards to real-time beam-coverage intelligence by mapping beam-level KPIs to dynamic footprints, creating geo-visual views that show both performance and its current location – turning coverage into an operational signal. In parallel, service and resource models now incorporate service schedules so KPIs are evaluated within defined availability windows.
At its core, the Rakuten OSS maintains a dynamic topology mapping between geolocation, eNB services, satellite schedules, beams, and ground stations – acting as a translation layer between earth-anchored service logic and orbit-anchored network behavior.
On the provisioning side, it is aligned with orbital inputs, using satellite pass predictions to trigger gateway preparation, eNB cell lifecycle control, and dynamic beam-service binding through automated commissioning.
Finally, the stack is built for multi-tenancy: satellites and gateways are shared infrastructure, while services remain logically isolated – enabling multiple operators to coexist with tenant-aware inventory, SLA, and performance domains.
NTN quietly changes the role of OSS.
OSS is no longer only a system that observes what the network does.
It becomes a system that prepares what the network is about to become.
Rakuten Symphony’s work in this space reflects a broader truth the industry is now confronting:
In non-terrestrial networks, operations are no longer about managing infrastructure.
It is about synchronizing digital systems with physical motion.
And that requires not just new radios or new cores – but a fundamentally new kind of OSS.
