Challenges of satellite network integration
According to the Ericsson Mobility Report 2025, the number of satellite broadband subscriptions is projected to grow from 9 million at the end of 2025 to 30 million by 2031. For large enterprises, this forecasted growth presents a new challenge: existing telecom infrastructure, designed for stable terrestrial channels, becomes a bottleneck when integrating LEO/MEO segments.
Traditional monolithic BSS/OSS systems are not adapted to the dynamic parameters of satellite networks, where latency and jitter metrics fluctuate constantly due to orbital dynamics and weather conditions. Furthermore, the lack of API standardization among various satellite providers complicates billing and quality of service monitoring.
Architectural approaches to modernization
To address this issue, telecom system architects are turning to the principles of Open Digital Architecture (ODA) from the TM Forum, which involves moving away from monoliths toward component-based, API-first solutions. Implementing a middleware layer allows for the abstraction of business logic from specific technical operator interfaces, performing data normalization into a unified CDR format.
Typical architectural scenarios include:
- Intelligent routing (LCR): Automatic traffic switching between fiber and satellite based on latency thresholds, where channel quality is the priority criterion.
- Unified billing: A middleware layer that converts heterogeneous traffic consumption data from satellite APIs into a format compatible with internal enterprise systems.
Technological implementation and security
As a technological foundation for building such integration systems, enterprises utilize the UnityBase platform. It enables the development of flexible integration gateways using domain metadata for automatic API generation, access control (RBAC/RLS), and auditing. For specific tasks involving voice traffic and IoT service management, solutions such as DooxSwitch are applied, providing LCR routing that accounts for the dynamics of satellite channel quality. Modernizing infrastructure in this way is critical, as according to the ENISA Threat Landscape 2025, digital infrastructure remains vulnerable, accounting for a significant portion of data breaches, while the overall level of system optimization in the industry remains limited.
Algorithm for adapting BSS/OSS to the satellite segment
| Stage | Action |
|---|---|
| 1 | Audit satellite provider APIs for the availability of latency and jitter metrics. |
| 2 | Deploy a middleware layer for data normalization into CDR format. |
| 3 | Configure LCR logic considering dynamic quality thresholds. |
| 4 | Integrate normalized data into internal billing modules. |
| 5 | Test failover switching between terrestrial and non-terrestrial links. |
FAQ
How can satellite provider APIs be integrated into legacy billing systems?
It is necessary to implement an API-first middleware layer that normalizes data from various satellite APIs into a unified CDR format, which is compatible with existing billing infrastructure.
What are the BSS architectural requirements when using LEO satellites?
The system must be based on a component-based architecture (in accordance with TM Forum ODA standards), support the processing of dynamic quality metrics (latency/jitter), and ensure integration via APIs.
How can routing be configured to account for satellite channel latency?
Use intelligent routing (LCR) solutions that monitor channel quality in real-time and automate traffic switching when latency thresholds are exceeded.