O-RAN Data Delivery Orchestration for Multi-Vendor 5G Scaling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing 5G wireless telecommunication networks face challenges in scalability, innovation, and cost-effectiveness due to vendor lock-in, which limits the deployment of best-in-class technologies and increases the cost-per-bit.

Innovation Solution

A disaggregated data construct is implemented in a cloud-native, Open Radio Access Network (O-RAN) 5G NR cellular telecommunication network, utilizing open APIs to decouple software from hardware, enabling flexible and virtualized network components that can be easily swapped and scaled, and leveraging multi-vendor collaboration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If vendor lock-in is maintained in traditional 5G networks, then network stability and reliability are preserved, but scalability and innovation are limited

Engineering Contradiction:
ImprovescalabilityVSAvoidnetwork stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the 5G network into independent virtualized network functions (VNFs) that can be individually managed, deployed, and scaled. This segmentation allows different vendors to provide different network functions through standardized interfaces, enabling scalability and innovation while maintaining overall network stability through modular architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a universal cloud-native architecture with standardized APIs and interfaces that can accommodate multiple vendors and different network functions. This universality allows the network to integrate best-in-class technologies from various vendors while maintaining consistent operation through a unified management plane.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If best-in-class technologies from multiple vendors are deployed, then innovation and network capability are enhanced, but device complexity and integration difficulty increase

Engineering Contradiction:
Improvenetwork capabilityVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a cloud-native management platform and standardized API interfaces as intermediaries between multiple vendor technologies and the core network. This intermediary layer abstracts the complexity of integrating best-in-class technologies from different vendors, allowing network capability enhancement while managing integration complexity through unified interfaces.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent utilizes cloud-native virtualization parameters and software-defined networking approaches to dynamically configure and manage network functions. By changing from hardware-bound configurations to software-defined parameters, the system can integrate multiple vendor technologies with varying capabilities while maintaining manageable complexity through virtualized resource orchestration.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If traditional centralized network architecture is used, then network management is simplified, but latency and bandwidth efficiency are reduced

Engineering Contradiction:
Improvemanagement simplicityVSAvoidnetwork latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent transitions from a traditional centralized two-dimensional network architecture to a multi-dimensional cloud-native architecture that distributes network functions across edge computing nodes. This dimensional change allows the network to maintain simplified centralized management through cloud orchestration while reducing latency through distributed edge deployment closer to users.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Solution Approach 2:

The patent creates virtual copies of network functions that can be deployed at multiple locations including network edges. These copied virtual network functions handle local traffic processing, reducing latency for local operations while the original centralized management system maintains overall network coordination and simplicity.

Inventive Principle:
Principle #26Copying

4Reliability

If hardware-based network functions are used, then network performance is reliable, but cost-effectiveness and deployment flexibility are reduced

Engineering Contradiction:
Improveperformance reliabilityVSAvoiddeployment flexibility
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent replaces hardware-based network functions with software-based virtualized network functions (VNFs) that run on standardized cloud infrastructure. This substitution maintains performance reliability through virtualization technologies while dramatically improving deployment flexibility, as software functions can be rapidly deployed, scaled, and updated without physical hardware changes.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent changes the fundamental parameter of network function implementation from hardware-bound to software-defined. This parameter change enables the same network function to be deployed across different hardware platforms, improving deployment flexibility while maintaining performance reliability through consistent software virtualization layers that abstract underlying hardware differences.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20250344076A1Data delivery automation of a cloud-managed wireless telecommunication network
Publication Date: 2025.11.06 BOOST SUBSCRIBERCO LLC
  • US20250344076A1 patent drawing
  • US20250344076A1 patent drawing
  • US20250344076A1 patent drawing

AI summary

Example embodiments are directed towards data delivery automation of a cloud-managed wireless telecommunication network. A disaggregated data construct is provided in a cloud-native, Open Radio Access Network (O-RAN), fifth-generation New Radio (5G NR) cellular telecommunication network. MNO cloud-native, O-RAN, 5G cellular telecommunication network engines are electronically mapped to components or services of a disaggregated network orchestrator. In an example embodiment, providing the disaggregated data construct may include electronically generating a mapping, via an open application programming interface (API), between a mobile network operator (MNO) cloud-native, O-RAN, 5G NR cellular telecommunication network service disaggregated slice design engine and a disaggregated intent engine of a disaggregated cellular telecommunication network orchestrator. The system operates the cloud-native, O-RAN, 5G NR cellular telecommunication network using the disaggregated data construct.