BubbleRAN O-RAN compliant stack includes:

1. O-RAN Interfaces: E2, A1, O1, R1, FHI 7.2a.
2. O-RAN E2SMs: Key performance measurement (KPM v2/3), RAN Control (RC v1.x), Cell Configuration and Control (CCC v3.x) and Low Layer Control (LLC v1.x). In addition BubbleRAN has developped additional custom service models including MAC/RLC/PDCP/RRC status, MAC Sched, RAN slicing and Traffic Control.
3. O-Cloud: Scalability (128 Compute nodes), synchronization, auto-device discovery, optimized data plane (Cilium and BGP), and eBPF Observability.
4. RIC: Near-RT and Non-RT RICs, software development kits (SDKs), and an ecosystem of reusable and extendable xApps and rApps.
5. SMO: E2E Network Management Systems and O-RAN SMO/OAM, Observability Stack, FCAPS, Network Operator, Slice Operator, DT Operator.
6. O-RUs: LITEON and Benetel O-RAN RUs, indoor and outdoor, n77/78/79/41.
7. Hub: Artifact registry with images, software packages, deployment blueprints.
8. Data: Multi-source data lake with metrics and stats from Infrastructure, 5G RAN and CN, and Energy footprints.

E2AP, A1AP compliant Interfaces, Real-time Control(<800us OWD), Multi-vendor, E2 Agent Emulator, cloud-native, xApp SDK in C and Python. Supported service Models are:

A1AP, R1AP, and O1 compliant Interfaces, cloud-native, rApp SDK in C and Python. Supported service are:

1. OAM Services
2. A1 Services
3. AI/ML Services
4. Data management and exposure (DME) Services
5. Service management and exposure (SME) Services

1. Full Day-0, Day-1, Day-2 Level-5 Autopilot. Refer to the list of capabilities here
2. Slice definition, assignment, and scaling
3. Multiple interfaces support for the RAN and CN
4. Full scheduling control on the container placement
5. DNS scoping and Edge services
6. High scalability with minimum deployment time (E2E less than a minute)
7. Reconfiguration and full-stack observability
8. Full customization and extensibility for both the Manager and Operators
9. Fully cloud-native with non-privileged containers supporting both private (on-premise) and public cloud providers
10. Automatic device discovery and mapping for GPUs, SDRs, RRHs, etc.
11. Network terminal management
12. Application in the loop
13. Idempotent and declarative logic design
14. Off-cluster resources in that MX-SMO fully supports external interfaces and each of the NFs can be configured to connect externally (as clients) or listen for external connection (as servers). In addition, we support external DNS entries.

1. O-RAN KPM E2SM: Performance Monitoring, Data-set collections, Load Distribution, Congestion Detection
2. O-RAN RC E2SM: Mobility management (HO), RAN Slicing, Load Balancing, QoS Control, Energy Management, Cell Management
3. O-RAN CCC E2SM: BWP reconfiguration, Frequency reconfiguration
4. O-RAN LLC E2SM: Sensing, Interference detection, Object Detection
5. BubbleRAN Custom MAC/RLC/PDCP/GTP E2SMs: Dataset collection, RAN monitroing and telemetry
6. BubbleRAN Custom Slice Control E2SM: Radio Resource Slicing, Resource Allocation Policy, Slicing Policy, MCS Control
7. BubbleRAN Custom Traffic Control E2SM: DPI, Packet classification, PAcket scheduling, Shaping, QoS Control, Flow-level Slicing

Yes. BubbleRAN supports a variety and mix-and-match of the vendors that could be concurrently deployed within the same network blueprint. BubbleRAN supports the following Open Source 5G Stack: LFN Duranta project (OpenAirInterface), LF OCUDU project(srsRAN), and Open5GS. In addition, BubbbleRAN supports the following industrial-grade 5G stack: Amarisoft 4G/5G, Lite-On All-in-One 5G gNB.

Yes. O-RAN 7.2 fronthaul split is supported for LFN Duranta project (OpenAirInterface), LF OCUDU project(srsRAN), and Amarisoft 5G stack with Lite-On FlexFI O-RU and Benetel RAN550 and RAN650. We also support VVDN 7.2 RU.

Yes.

O1 interface is implemented in house from scratch. It also supports E2E TLS for industrial-grade 5G stack.

BubbleRAN organizes its portfolio around two complementary families built on a common technology foundation:

1. MX-PDK Family: Designed for R&D, education, experimentation, O-RAN and AI-RAN innovation, PoCs, validation, and campus-scale deployments. It provides a consistent path from integrated 5G/6G labs to programmable O-RAN and agentic AI-RAN environments.
2. Sphere Family: Designed for enterprise and operational environments, covering RAN control, service management and orchestration, automation, observability, Network Digital Twins, and intelligent network optimization. The common foundation helps teams move from research and validation toward real-world deployment and operations without rebuilding the toolchain.

Soft UEs, 5G modules such as Quectel, and majority of smartphnes (Google phone, Samsung Galaxy, iPhone, oneplus) or 5G modules such as Quectel.

No. Unless hardware is explicitly included in a commercial quotation or package, BubbleRAN pricing covers the software license and the associated software support and updates defined in the offer. Hardware can be sourced separately or integrated with supported partner platforms.

it is recommended to have at least three machines, Intel-based or AMD-based, with the following minimum specifications:

1. Machines: AVX512, >4GHz, >24C, >64GB RAM, >1TB NVMe or SSD write-intensive, Intel E810-XXVDA2, Form Factor: Tower or Rack, Cooling: Fan Liquid cooling (preferred).
2. GPUs (Optional): NVIDIA RTX PRO 6000 Blackwell Server Edition, 96GB GDDR7, PCIe 5, 600W. NVIDIA RTX PRO 5000 Blackwell PCIe 5 48GB, NVIDIA H100/H200/A100.

While this depends on the network configuration (e.g. bandwidth, number of MIMO layers, and radio frontend), indicatively for 100MHz 2x2 single carrier with an Intel i9, 4GHz/24C, 64RAM, NIC: 10Gbps, you can run the either of the following combinations: (a) 3x gNBs, (b) 1 gNB and 4-6 UEs, (c) 2 gNBs and 2-4 UEs.

1. The BubbleRAN DevOps Technology leverages the best practices to deliver an agile and consistent Cloud-Native Multi-vendor 5G/6G CI/CD/CO platform providing more than 10x faster on-boarding, performance and conformance testing (3GPP and O-RAN), efficiency and delivery cycles targeting telco network functions and applications (5G/6G).

2. The BubbleRAN DevOps is realized using GitOps operational framework that leverages the best practices used for network functions and application development/integration/testing such as CI/CD/CO and applies them to the infrastructure and multi-vendor 5G/6G network automation.

3. The BubbleRAN Telco Devs include on-boarding & migration, building & packaging, testing & validation, and releasing artifacts via the BubbleRAN hub.

4. The BubbleRAN Telco Ops includes provisioning, Operations, Observe, insight & automate that are accessible via a powerful cli & APIs.

5. Vendors and Developers can now simply develop/customize/on-board their network functions and xApps/rApps as well as their Kubernetes custom resource definitions (CRDs) via the CI/CD/CO platform using the BubbleRAN SDK and CDK.

6. Operators and Service Providers can leverage multi-x software-based operators to design and deploy a 5G/6G network tailors to a particular use-case requirements and yield the required level of control and observability to the customers.

1. BubbleRAN relies on the 3rd party vendors, such as Amarisoft, OpenAirInterface, OCUDU, and Open5GS among the others, to create and validate an optimized multi-x 5G artifacts in conformance with the 3GPP, O-RAN and public cloud requirements.

2. BubbleRAN develops cloud-native Open RAN components including MX-RIC as NearRT and Non-RT RIC with xApps and rApps, MX-Operator as SMO/OAM, FCAPS, Observability stack, compliant with the O-RAN specification, where both legacy and emerging Operators and service providers are one click away to mix-and-match one x in multi-x to another one (one vendor to another or one deployment to another).

1. BubbleRAN provides a new generation of cloud-native MANO/SMO technology that fully adheres to the cloud-native principles, while fostering innovation and sustainable deployment for 4G, 5G, and beyond. It elicits an agile and intelligent, dynamic control over variety of vendors and radio stacks (multi-x) coexisting on the same network with built-in observability and at the scale.

2. The management and orchestration layer builds on the Operator Framework to assist or replace the human in the loop, approaching six dimensions including Cloud-Native Intelligent, Closed-Loop Observability, 4C Secure Networking, Sustainability, Agile and Consistent DevOps, and Open Ecosystem, for RAN and its hardware resources, CN, and edge applications.

1. Telco is moving towards a software-based telco solution empowered with hardware resources (e.g. look aside or inline accelerated cards). Today’s legacy public operators as well as emerging private Operators are calling for a faster and more efficient 5G delivery cycles on daily basis to meet their business application requirements while at the same time lowering the operating costs and energy footprint of the overall network.

2. By leveraging CI/CD/CO/DevOps, the entire delivery cycle can be automated in an agile, consistent manner helping Operators to deal with network fixes and upgrade. One simple example is an important security patch on a running network or release a new features in a matter of an hour rather than days or months while retaining the service assurance and continuity.

From the technical perspective, one of the main challenges is the transition from VNF to CNF and from physical infrastructure to private/public clouds. This means more software-based 5G/6G solutions that are empowered by the hardware accelerators to sustain the promised performance. This brings another challenges, which is to expose hardware capabilities as a soft and composable resources to the CNF to maximize the efficiency and multiplexing gain.

A 4G/5G network components by design relies on a heterogeneous, distributed, and synchronous infrastructure resources, namely hardware accelerators, radio units, network functions, and edge apps, that usually provided by different vendors.

A Docker-based or Helm-based automation can only provide level 1 and 2 life-cycle operations and are limited to a single vendor and single infrastructure.

1. Open documentation includes xApp and SM documentation for users and developers.
2. In the figure below you can see the xApp /rApp lifecycle from development to production.
3. A software-development kit (SDK) is provided for the development of an xApp (see documentation link above).
4. To onboard an xApp or an NF as a container, a Container Development Kit (CDK) is provided in the DevOps package, allowing you to integrate your custom function into the MX-PDK family. We are currently working on documentation for this. Your xApps can also run as normal processes outside the cluster and connect to the RIC and gNBs running inside the cluster.

This is the same as developing a new xApp from the MX-ORS and MX-PDK. Please refer to Q12. We also have a number of xApp examples that support AI/ML, delivered in a source code format so that the clients could reproduce and extend the use-case.

1. Since the rApps in BubbleRAN are using cloud-native Kubernetes APIs, any SDK supporting Kubernetes clients would do. This means, you could implement your own logic in any language (Python, Go, JavaScript, or any REST-client implementation) by just consuming the Custom Resource Definitions (CRDs) created by our SMO.
2. Currently, three rApps are available: Cell manager, Spectrum sharing, Dynamic resource and NF scaling.

1. The MX-PDK family supports arbitrary containerized applications to be attached to the user-terminal and be deployed at the edge cloud.
2. The actual integration might need our support, and requires evaluation.

1. You can access the container of any NF in a given deployment.
2. If the containers come with the source code, you can modify the source code on the fly. Some of our xApps provide such features.
3. You can change the source codes of any open-source based NFs that are supported by BubbleRAN (OAI, srsRAN), and connect to the MX-ORS and MX-PDK product family as external off-cluster resources (see Q19). To on-board such a NF you would need the CDK (see Q12) included in the BubbleRAN DevOps package.

Yes. Note that the number of concurrent networks deployed on your infrastructure depends on the available compute/memory/network resources. This is indeed an effective infrastructure sharing across different users and networks. In K8s, there is the concept of namespace which allows to logically separate the infrastructures across different users and/or networks.

We don’t have any limitations regarding this whether it is in the same namespace or across different namespaces.

As long as other RICs are compliant with E2AP v3 and the O-RAN service models (KPM v3, RC v1.1, and CCC v3.0), you can integrate them with other RIC platforms. Note that the most important part of a RIC is the xApps and rApps, as the RIC itself does not realize any intelligence; the intelligence resides in the xApps.

You can publish results and explore commercial applications, but you can’t transfer the license. Please have a look at the license agreement.

BubbleRAN is an international telecom innovator founded in 2021 in Sophia Antipolis, France. We specialize in cloud-native 5G/6G, O-RAN, and AI-RAN technologies, combining multi-vendor network software, intelligent automation, programmable control, and development environments to help organizations move from research and validation to real-world network operation and optimization.

Our mission is to make 5G/6G networks open, programmable, and intelligent. We empower researchers, engineers, and operators with software platforms and DevKits that accelerate the full network lifecycle, from experimentation and interoperability testing to automation, control, and optimization of real networks.

1. Deep technology foundation: Expertise across 3GPP, Kubernetes, O-RAN, and AI-RAN in a common multi-vendor software foundation.
2. From lab to operations: A consistent path from research and validation to deployment, control, automation, and optimization without rebuilding the toolchain.
3. Intelligence by design: Observability, programmable RIC/SMO control, agentic AI, closed-loop automation, and scalable Network Digital Twin capabilities.
4. Open ecosystem: Standards, interoperability, open interfaces, modular architectures, open-source foundations, and TelcoFabric help preserve customer choice and accelerate reusable innovation.

BubbleRAN organizes its portfolio into two complementary product families built on a common technology foundation:

1. MX-PDK Family — R&D and Innovation: Integrated 5G/6G labs, O-RAN experimentation, agentic AI-RAN, Network Digital Twins, interoperability testing, PoCs, and campus-scale validation.
2. Sphere Family — Enterprise and Operations: Programmable RAN control, service management and orchestration, observability, automation, and intelligent network optimization for test, integration, and operational environments. This common foundation lets organizations evolve from experimentation and validation toward larger-scale deployment and operations without rebuilding their tools and workflows.

BubbleRAN combines 3GPP, Kubernetes, O-RAN, and AI-RAN with cloud-native management, programmable RICs and SMO, observability, agentic automation, intelligent optimization, and scalable Network Digital Twins. The technology is designed for multi-vendor environments and integrates both open-source and industrial-grade telecom components.

1. Universities, R&D Centers and Innovation Labs: For teaching, experimentation, testbeds, datasets, O-RAN/AI-RAN research, and reproducible validation.
2. Operators and Enterprises: For programmable network control, service management, observability, automation, optimization, and advanced private or campus network use cases.
3. Telecom Vendors and System Integrators: For interoperability, product integration, reference designs, joint solutions, field validation, and customer deployments.
4. Technology and Application Partners: For integrating applications, AI models, xApps, rApps, agents, datasets, and other reusable telecom artifacts into complete solutions.

BubbleRAN works with technology providers, application developers, system integrators, resellers, and managed-service partners through three complementary models:

1. Build: Build, validate, and package complete telecom solutions or applications using BubbleRAN technology, then deliver and promote them to your customers. This is well suited to partners developing applications, AI solutions, integrations, or vertical use cases that need a realistic 5G/6G, O-RAN, or AI-RAN environment.
2. Resell: Deliver BubbleRAN’s turnkey platforms and solutions to your customers as part of your own portfolio, while adding your integration, professional services, hardware, or domain expertise where needed.
3. Sell With: Collaborate with BubbleRAN on joint customer opportunities, combining our technology with your integration, managed services, applications, or market reach to deliver complete solutions together.

Open source is a strategic foundation of BubbleRAN, not simply a technology choice. We build on mature open-source technologies and combine them with production-grade engineering, integration, validation, automation, observability, lifecycle management, and support. Through open standards, documented APIs, modular architectures, and initiatives such as TelcoFabric, we extend openness beyond source code so applications, AI agents, datasets, models, and blueprints can be discovered, reused, validated, and improved across the telecom community.

BubbleRAN was founded in 2021 by Navid Nikaein, who serves as CEO. The company is headquartered in Sophia Antipolis on the French Riviera, in the south of France.

Send a short description of your requirements, target use case, deployment environment, and expected timeline to contact@bubbleran.com. We will route the request to the appropriate technical, product, or business team and arrange a discussion when useful.