Terrestrial Networks (TN) and Non-Terrestrial Networks (NTN) are converging into a three-dimensional connectivity fabric. This means ground infrastructure, remote sites, maritime environments, airborne platforms, and satellite-enabled coverage. Managing that fabric requires more than reach: it requires consistent control, automation, observability, and service assurance across heterogeneous radio domains.
BubbleRAN addresses this challenge by combining RIC-Sphere and SMO-Sphere in a unified reference design:
- RIC-Sphere provides Near-RT and Non-RT intelligence, policy control, and closed-loop optimization across native E2 nodes and adapted non-E2 domains.
- SMO-Sphere provides declarative, intent-driven lifecycle automation across RAN, Core, Edge, terminals, cloud resources, and network services from Day 0 planning to Day 2+ operations.
Together, they help operators, NTN platform providers, system integrators, government organizations, and research teams build programmable TN/NTN solutions without tying service innovation to a closed, single-vendor control stack.
Reference-design scope: RIC-Sphere and SMO-Sphere provide the control, management, orchestration, observability, and application layers. The final TN/NTN deployment is integrated with the selected terrestrial and non-terrestrial RAN, transport, core, terminal, and satellite platforms. NTN programmability can be exposed through native O-RAN interfaces or the extensible E2X adaptation framework, depending on the target platform.
One architecture, complementary responsibilities
RIC-Sphere: programmable intelligence and closed-loop control
RIC-Sphere is BubbleRAN’s O-RAN-compliant, cloud-native RIC and application platform. It combines an operational Near-RT RIC, Non-RT RIC, O1/NETCONF OAM, application development toolkits, multi-vendor RAN emulation, and an extensible E2X Proxy Agent.
For converged TN/NTN environments, RIC-Sphere enables:
- Standards-based integration through E2, A1, R1, and O1 interfaces
- E2X adaptation of NTN RATs, legacy RANs, devices, sensing platforms, and other non-E2 domains into standard or custom E2 Service Models
- xApp and rApp development in C, C++, and Python, with SDKs, reusable samples, testing, containerization, and onboarding workflows
- Policy and AI/ML-driven automation across Near-RT and Non-RT control loops
- A reusable application and use-case catalog covering mobility load balancing, slicing, traffic steering, SLA/QoS/QoE assurance, energy optimization, sensing/localization, and dataset collection, with maturity depending on the selected workflow
SMO-Sphere: intent-driven lifecycle automation
SMO-Sphere is BubbleRAN’s O-RAN-compliant, Kubernetes-native Service Management and Orchestration platform. It separates reusable vendor Composition Models from operator-defined Deployment Blueprints, allowing teams to describe what they want to deploy without hard-coding every site-specific infrastructure detail.
For converged TN/NTN environments, SMO-Sphere enables:
- Day 0 planning: resource discovery, network-function onboarding, topology design, and service planning
- Day 1 deployment: scheduling, provisioning, configuration, and dependency resolution
- Day 2+ operations: reconfiguration, upgrades, testing, reconciliation, fault management, and observability
- End-to-end service orchestration across access, core, edge, cloud, terminals, and network slices
- Purpose-built operators for network functions, network services, services, slices, AI Fabric, digital twins, and terminal lifecycles
- Multi-source observability spanning RAN statistics, logs, traces, alarms, infrastructure utilization, and energy consumption
- Security controls including network isolation, signed rootless artifacts, RBAC, runtime network and process security, and Software Bills of Materials
From telemetry to action
| Stage | RIC-Sphere | SMO-Sphere | Operational value |
|---|---|---|---|
| Observe | Collects RAN and application telemetry through E2/E2X, service models, and data interfaces | Aggregates network, service, infrastructure, and energy data into a multi-source observability layer | A consistent operational view across TN and NTN domains |
| Decide | Runs xApps, rApps, policies, analytics, and AI/ML-assisted logic | Interprets service intent and lifecycle state through operators, Composition Models, and Blueprints | Decisions aligned with both radio conditions and service objectives |
| Act | Executes E2 control, distributes A1 policies, exposes R1/O1 services, and uses adapted southbound interfaces where required | Reconciles network functions, services, slices, terminals, and cloud resources | Coordinated closed-loop action across control and management timescales |
| Evolve | Supports reusable apps, service models, SDKs, and validation workflows | Supports repeatable onboarding, deployment, upgrade, and rollback-friendly workflows | Faster introduction of new vendors, use cases, and network capabilities |
Addressing the operational realities of TN/NTN
TN/NTN convergence introduces moving coverage, dynamic topology, variable link conditions, intermittent availability, heterogeneous control interfaces, and strict service-priority requirements. The combined architecture maps those challenges to programmable and automatable capabilities.
| TN/NTN challenge | BubbleRAN capability | Expected outcome |
|---|---|---|
| Heterogeneous TN and NTN domains | Native E2 integration plus E2X adapters for non-E2 or proprietary southbound interfaces | One extensible control framework without redesigning the RIC core |
| Dynamic mobility and topology | Mobility policies, handover control, traffic steering, neighbor configuration, and lifecycle reconciliation | Better continuity and resource use for moving users, cells, and platforms |
| Variable capacity and service demand | KPM-driven analytics, slicing, QoS/QoE policies, and traffic-control logic | Resources can be prioritized according to service intent and operating conditions |
| Distributed infrastructure | Kubernetes-native deployment, resource discovery, Composition Models, and reusable Blueprints | Repeatable rollout across central, edge, remote, and temporary sites |
| Fragmented telemetry | RAN KPIs, logs, traces, alarms, infrastructure metrics, and dataset export | Faster diagnosis, SLA assurance, and data preparation for AI/ML workflows |
| Multi-vendor integration | Standard interfaces, custom service models, E2X adaptation, CDK onboarding, and RAN emulation | Lower integration risk and a practical path for brownfield and greenfield deployments |
| Security and sovereignty | RBAC, isolation, signed rootless artifacts, runtime controls, and SBOM-aware delivery | Greater control over software, data, policies, and operational boundaries |
Priority solution scenarios
Maritime and offshore connectivity
Coordinate terrestrial coastal infrastructure, onboard or offshore private networks, and satellite-enabled coverage. Use policy-driven traffic steering, slicing, mobility optimization, and unified observability to sustain differentiated services across changing link conditions.
Public safety and mission-critical operations
Deploy repeatable network services for incident zones, remote operations, temporary coverage, UAV-enabled services, and priority users. Combine service-aware orchestration with closed-loop radio control and observability to improve operational responsiveness.
Sovereign and defence networks
Build adaptable networks with local control of policies, applications, data, and lifecycle operations. Extend the platform through customer-defined xApps, rApps, service models, and southbound adapters while applying cloud-native isolation and software-supply-chain controls.
TN/NTN research, integration, and validation
Create a controlled environment for developing and validating xApps, rApps, policies, E2/E2X adapters, service models, data pipelines, and multi-vendor workflows before moving into field trials or operational deployments.
Technical foundation
| Layer | Core capabilities |
|---|---|
| Near-RT RIC | xApp hosting, E2AP, standard and custom E2SMs—including KPM, RC, CCC, LLC, TC, SC, and LS—and fine-grained monitoring and control |
| Non-RT RIC | rApp hosting, policy, analytics, AI/ML orchestration, A1 and R1 services |
| E2X Proxy Agent | Adaptation of non-E2 RATs, NTN platforms, devices, sensing systems, and proprietary interfaces into standard or custom E2SMs |
| OAM | O1/NETCONF workflows for fault, configuration, performance, and software management |
| SMO / NMS | Composition Models, Deployment Blueprints, NF and NS Operators, slice and service orchestration, Day 0 to Day 2+ lifecycle management |
| Data and observability | VictoriaMetrics, VictoriaLogs, VictoriaTrace, Grafana, dataset creation and export |
| Cloud and networking | Kubernetes, Cilium, Multus, BGP, resource discovery, heterogeneous compute and network integration |
| Security | Network isolation, signed unprivileged rootless artifacts, RBAC, runtime network/process controls, and SBOMs |
| Developer ecosystem | C/C++/Python SDKs, CDK, reusable xApp/rApp samples, catalogs, emulation, testing, and CI/CD-compatible workflows |
Business value by stakeholder
- Mobile and satellite operators: coordinate services across heterogeneous coverage domains, accelerate use-case rollout, and avoid locking service innovation to one equipment vendor.
- Network and NTN platform vendors: expose differentiated capabilities through standard or custom service models, xApps, rApps, and reusable integration assets.
- System integrators: replace one-off deployments with repeatable Composition Models, Blueprints, adapters, and lifecycle workflows.
- Government and critical-infrastructure organizations: retain greater control over deployment, data, policies, security boundaries, and application evolution.
- R&D and validation teams: move from concept to multi-vendor validation using one continuous development, emulation, onboarding, and closed-loop testing workflow.
Frequently asked questions
Does BubbleRAN provide the NTN radio or satellite infrastructure?
This reference design focuses on the O-RAN control, management, orchestration, observability, and application layers. It integrates with the selected TN/NTN RAN, transport, core, terminal, and satellite platforms through native standard interfaces or tailored E2X adapters.
How is an NTN platform integrated when it does not expose E2?
RIC-Sphere’s E2X Proxy Agent maps supported southbound protocols and platform capabilities into standard or custom E2 Service Models. This allows xApps and rApps to work through a consistent RIC framework while keeping platform-specific integration at the adapter layer.
Which TN/NTN use cases can be implemented?
The architecture provides foundations for mobility and load balancing, traffic steering, QoS/QoE and SLA assurance, slicing, energy-aware optimization, sensing/localization, dataset generation, and policy-driven service continuity. Final use-case scope depends on the telemetry and control capabilities exposed by the integrated TN/NTN platforms.
Can the architecture support brownfield environments?
Yes. Native O-RAN interfaces, E2X adaptation, third-party NF onboarding, and reusable Composition Models and Blueprints provide a migration path for both brownfield and greenfield deployments.
How can a customer start?
Begin with a focused reference scenario: identify the target TN/NTN platforms and interfaces, select one or two measurable closed-loop use cases, define deployment and security constraints, and agree on validation KPIs. BubbleRAN can then map those requirements to the appropriate RIC-Sphere and SMO-Sphere components, adapters, applications, and deployment Blueprints.
Scope your TN/NTN reference scenario with BubbleRAN
Bring us your target topology, radio platforms, available interfaces, operational constraints, and priority use case. BubbleRAN will help map them to the required RIC-Sphere and SMO-Sphere capabilities, identify any platform-specific integration or E2X adaptation, and define a credible path from sandbox validation to a field trial or production-oriented deployment.
- Explore RIC-Sphere
- Explore SMO-Sphere
- Request a TN/NTN technical scoping session