BubbleRAN O-RAN compliant stack includes:

1. O-RAN Interfaces: E2AP v3, A1AP v1.x, O1, R1AP, FHI 7.2.
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. MX-RIC: Near-RT MX-RIC, Non-RT MX-RIC, software development kits (SDKs), and an ecosystem of reusable and extendable xApps and rApps.
5. MX-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. MX-Hub: Artifact registry with images, software packages, deployment blueprints.
8. MX-Data: Multi-source data lake with metrics and stats from Infrastructure, 5G RAN and CN, and Energy footprints.

Note: BubbleRAN’s O-RAN Stack is all implemented in-house. It features cloud-native and can be deployed from bare-metal in both private and public clouds. For example you can deploy it on Google K8s Engine (GKE)!

E2AP and 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:

1. O-RAN Compliant E2SM: KPM-v3, RC-v1, CCC-v3, and LLC-v1.
2. BubbleRAN E2SM: MAC, RLC, PDCP, RRC, NGAP, Slice Control, and Traffic Control.

A1AP and R1AP 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: OpenAirInterface, srsRAN, and Open5GS. In addition, BubbbleRAN supports the following industrial-grade 5G stack: Amarisoft 4G/5G, Lite-On All-in-One 5G gNB.

Note: BubbleRAN O-RAN stack is Multi-x by design, refering to various dimensions such as RAN vendor, OS, and cloud, addressing the level of heterogeneity and diversity in the modern networks, and it is considered as a natural extension to the O-RAN

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

Note: Each vendor implements the fronthaul interface differently and therefore the capabilities differ across the vendors.

Yes.

We use an existing open source NetConf client to realize the O1 interface. The O1 is only available for the Lite-on AIO small-cell and O-RU.

Note: We do not use the O-RAN O1-compliant interfaces to configure and manage OpenAirInterface, srsRAN, and Amarisoft since they do not implement the O1 interfaces (i.e. NetConf Server). Recently, there have been some activities for OAI on the O1 interface but they do not provide all the required features for MX-SMO.

Nevertheless, this does not limit our SMO in its functions with respect to the NFs or RAN software, but rather improves it for day-2 operations. If you use the cli extract pcap command to extract the PCAP in the containers, you would see some HTTP messages transported for the REST API between the Workload and the Manager containers that might resemble the O1 messages that you are looking for.

1. MX-ORS: comprehensive educational platform designed for upskilling, learning, teaching and experimenting 5G/6G networks, O-RAN and 3GPP standards, and AI-RAN.
2. MX-PDK: Flexible E2E 5G/6G O-RAN compliant platform designed for R&D, testbeds, PoCs, and demonstration.
3. MX-AI: 5G/6G Automation and Intelligence platform designed for Agentic Network Operation and Optimization, aligned with O-RAN, AI-FOR-RAN and AI-ON-RAN
4. MX-DT: Scaleble E2E 5G/6G network digitial twin platform designed for realistic network simulation, dataset generation, AI/ML validation, what-if analysis.
5. MX-PRO: Industrial-grade Private 5G designed for network deployment in campus, maritime, airport, harbour, factories, and warehouses.

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

Except for MX-PRO, No, the base price includes only the software license and 1 year of software updates and support (dedicated chat channel).

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.

Terminologies (DevOps definitions and benefits according to Amazon)

1. CI/CD/CO: Continuous Integration, Continuous Delivery, and Continuous Optimization.
2. SDK: xApp and rApps software development kit.
3. CDK: Container development kit.
4. Operations: design, install, deploy, test, reconfigure, fail-over, backup, restore, upgrade.
5. Observe: logs, metrics, conditional events, alarm, and alerts.
6. Insight: health, anomaly, inefficiency.
7. Automate: scaling, healing, tuning.

1. BubbleRAN relies on the 3rd party vendors, such as Amarisoft, OpenAirInterface, srsRAN, 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).

Terminologies

1. SMO: Service Management and Orchestration.
2. RIC: RAN Intelligent Controller.
3. xApp: NearRT-RIC applications.
4. rApp: Non-RT-RIC applications.
5. Multi-x: Multi-vendor, Multi-version, Multi-RAT, Multi-RU, Multi-cloud, Multi-OS, Multi-deployment.

1. The BubbleRAN MX-Operator is a new generation of MANO/SMO 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. MX-Operator bases its foundation upon 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 MX-ORS and MX-PDK. 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.

Note: We plan to develop an rApp SDK to facilitate the development of rApps.

1. MX-ORS and MX-PDK support any arbitrary containerized application 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.

Note: BubbleRAN RIC extends FlexRIC with new service models and xApps, providing the most comprehensive features of O-RAN RICs. You can access the BubbleRAN FlexRIC here: BubbleRAN FlexRIC.

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

1. BubbleRAN is a software company dedicated to telecom offering a range of cutting edge feature-rich 5G/6G software-based solutions. Founded in 2021 in the South of France, BubbleRAN specializes in designing and delivering scalable, turnkey 5G solutions with comprehensive long-term support.

2. We maintain a global presence to better serve our clients with strategic bases Sophia-Antipolis, France, California, USA, and Nairobi, Kenya.

3. Our cutting-edge 5G/6G software-based solutions are built with automation, advanced intelligence, and open ecosystem integration at their core which reflects our commitment to driving innovation in the telecom industry.

3. Our mission is to empower public and private mobile networks with fully managed, high-performance 5G/6G software solutions that combine flexibility, customization, and scalability. Powered by pioneering applied research, we create breakthrough technologies that enable smarter and more efficient networks, transforming the future of connectivity.

1. MODERNIZE YOUR 5G NETWORK OR CREATE ONE With our production-grade 5G O-RAN compliant stack, intent-driven 5G Automation, and zerotouch cloud-native 5G
2. BRING INTELLIGENCE INTO 5G AND BEYOND With our observability stack, scalable and intelligent digital twins, Gen-AI network optimization, portfolio of xApps and rApps.
3. UNLOCK INTELLECTUAL PROPERTY AND TECHNOLOGY STREAMS With our Telco CI/CD/CT DevOps Platform, Network Slicing, 5G Direct, 5G Router, and Managed Mobile Private Networks (M-MPN).

Checkout our research and contribution to Open Source here

BubbleRAN is located in French Rivera, south of France.

The postal address is: 450 Route des Chappes, 06410 Biot, France.

1. BubbleRAN is founded in 2021 by Navid Nikaein, the acting CEO/CTO of the company.

2. Currently (01/06/2024), the BubbleRAN team is composed of 9 people.

BubbleRAN develops a complete cloud-native multi-vendor O-RAN stack, all implemented in house. We also work with divers 5G vendors to on-board their 5G stack in our portfolio. Currently we are supporting the following vendors:

1. Open Source: OpenAirInterface, srsRAN, Open5GS
2. Industrial-grade: Amarisoft, and LITEON

BubbleRAN targets the following markets:

1. Education and Learning with MX-ORS product and Open labs and exercises. TRL 4-5, 3GPP, O-RAN, Cloud-Native, AI, and Edge computing.

2. R&D and Measurement with MX-PDK and MX-AI products. TRL 4-7, PoC and MVP.

3. Private5G with our MX-PDK industrial grade products. TRL7-8, Enterprise Networking and Deployment.

Note:

1. We guarantee a seamless transition from education and R&D to deployment with a consistent UI and tool chain and guaranteed reprehensibility.
2. The three products are based on the same core technology.

To book a meeting, please

1. First Contact us by email to provide us more information about your requirement and the topics you would like to discuss during the meeting.
2. Then, after you received our reply, Book a meeting