Telecom 3 min read

Integrating LEO satellite connectivity: BSS/OSS architecture for dynamic traffic

Optimizing BSS/OSS for LEO satellite integration. Strategies to resolve billing gaps and monitoring errors caused by high jitter and dynamic session variability.

The rapid adoption of LEO (Low Earth Orbit) broadband connectivity creates critical challenges for enterprise BSS/OSS. Traditional billing and monitoring systems are architecturally optimized for stable terrestrial channels. Switching to satellite links, characterized by high latency variation (jitter) and dynamic session duration, leads to "billing gaps" and false positives in monitoring systems. According to the CFCA Global Fraud Loss Survey 2025, global losses from telecom fraud have reached $41.82 billion, highlighting the critical need for reliable mediation layers.

Why LEO satellites create billing gaps in legacy systems

Legacy systems often rely on fixed timeouts and stable CDR streams. When switching between fiber and satellite, timestamping issues occur during handovers. This leads to duplicate records or data loss, making accurate billing impossible. Given that a significant portion of organizations in critical sectors have faced security incidents (ENISA Threat Landscape 2025), any inaccuracy in mediation data creates additional risks for business process integrity.

Architectural challenges: Jitter and data mediation

Latency variation in LEO channels exceeds fiber metrics by orders of magnitude (milliseconds versus microseconds). Traditional OSS systems interpret this jitter as network degradation, generating a flood of false alerts. Transitioning to a cloud-native architecture, as defined by 3GPP standards, is a necessary modernization step to ensure resilience against such fluctuations.

Evolution to ODA-compliant architecture

In accordance with the TM Forum Open Digital Architecture (ODA) concept, the path to solving these issues lies in transitioning to component-based, API-first structures. Instead of monolithic processing, the mediation layer must support real-time rating, allowing for dynamic adaptation to changing latency profiles.

Mediation layer readiness checklist for LEO integration

  • Support for real-time rating for dynamic latency changes.
  • Correct timestamp handling during handovers between channels.
  • Configuration of adaptive thresholds for OSS alerts, accounting for LEO-specific jitter.
  • API-first access to mediation data for BSS integration.
  • Flexible billing configuration for sessions with high disconnection dynamics.

Intecracy Group specialists can assist with auditing telecom architecture and integrating new communication channels into your existing stack. Expertise includes modernizing billing systems (specifically based on the DooxSwitch platform) and implementing solutions capable of real-time billing and SIP routing. Additionally, the UnityBase platform can be used to create integration components that ensure secure data exchange, process auditing, and access management as part of infrastructure modernization.

FAQ

How to avoid double billing when switching between satellite and terrestrial connections?

It is necessary to implement a mediation layer that supports precise timestamp synchronization and atomic sessions, which correctly identify handovers between different interface types.

What architectural changes are needed in BSS to support LEO traffic?

Transitioning from monolithic systems to an API-first architecture based on TM Forum ODA principles, where billing logic is moved to an adaptive mediation layer.

How to configure OSS monitoring to ignore satellite channel jitter?

Adaptive metrics and dynamic thresholds should be applied, which automatically adjust latency tolerances depending on the gateway type through which the traffic passes.

Data sources