Open RAN Hardware Resource Orchestration for Multi-Vendor Functions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing Open RAN systems lack a comprehensive framework for dynamically identifying and allocating hardware resources to network function applications, limiting interoperability and flexibility across different vendor solutions.

Innovation Solution

A framework is provided that dynamically identifies and allocates hardware resources based on processing requirements, enabling communication between application processes and hardware resources, and supports a software-defined RAN controller (SDRC) and RAN inter-process communication (RAN-IPC) to facilitate interoperability and flexibility.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If hardware and software components are tightly coupled in traditional RAN systems, then system reliability and performance are improved, but adaptability and flexibility deteriorate

Engineering Contradiction:
Improvesystem reliabilityVSAvoidadaptability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the traditional monolithic RAN system into distinct hardware resources and software application processes. The hardware is divided into identifiable resource units with specific capabilities, while software is separated into independent application processes that can be dynamically allocated to different hardware configurations, enabling both reliability through specialized components and adaptability through flexible allocation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal resource management framework that can accommodate multiple types of hardware resources (GPUs, FPGAs, ASICs, CPUs) and multiple application processes within a single system. This multi-functional architecture allows the same management infrastructure to handle diverse hardware-software pairings, improving adaptability while maintaining system reliability through standardized interfaces.

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

2Reliability

If proprietary hardware and software are used from a single vendor, then system reliability and performance are improved, but adaptability and vendor diversity deteriorate

Engineering Contradiction:
Improvesystem reliabilityVSAvoidvendor diversity
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a resource management framework as an intermediary layer between hardware resources and application processes. This intermediary abstracts the underlying hardware specifics and provides standardized interfaces, allowing applications to run reliably across different vendor hardware while enabling vendor diversity. The framework mediates between proprietary components from different vendors, ensuring interoperability without sacrificing reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Stability of the object's composition

If static hardware allocation is used in traditional systems, then system stability is improved, but resource utilization efficiency and flexibility deteriorate

Engineering Contradiction:
Improvesystem stabilityVSAvoidresource utilization efficiency
Core Design Contradiction:
Stability of the object's compositionVSProductivity

Solution Approach 1:

The patent implements dynamic hardware resource allocation where the system can identify available hardware resources, assess their capabilities, and allocate them to application processes based on current needs and compatibility. This dynamic allocation maintains system stability through controlled management while dramatically improving resource utilization efficiency by matching hardware capabilities to application requirements in real-time.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent incorporates feedback mechanisms where the system continuously monitors hardware resource availability, application performance, and resource utilization. This feedback enables the resource management framework to make informed allocation decisions, maintaining system stability while optimizing resource utilization by adjusting allocations based on actual system state and performance metrics.

Inventive Principle:
Principle #23Feedback

4Power

If hardware-specific programming is required, then processing performance is improved, but ease of development and interoperability deteriorate

Engineering Contradiction:
Improveprocessing performanceVSAvoidease of development
Core Design Contradiction:
PowerVSEase of manufacture

Solution Approach 1:

The patent introduces a capability description interface as an intermediary that translates hardware-specific capabilities into a standardized format. This allows application developers to write hardware-agnostic code while the resource management framework handles the translation to hardware-specific optimizations, maintaining high processing performance without requiring hardware-specific programming and thus improving ease of development and interoperability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP4657243A1A method and framework for managing resources in a network function of an open radio access network, a method of compiling a computer program, a computing device and a computer program
Publication Date: 2025.12.03 VODAFONE GROUP SERVICES LTD
  • EP4657243A1 patent drawingFigure 1
  • EP4657243A1 patent drawingFigure 2
  • EP4657243A1 patent drawingFigure 3

AI summary

A method of managing resources in a network function of an Open Radio Access Network, Open RAN, is provided. The method comprises dynamically identifying a plurality of hardware resources available to the network function. Each hardware resource supports one or more processing capabilities. The method further comprises facilitating a plurality of application processes by: dynamically allocating hardware resources from the plurality of hardware resources to the plurality of application processes, based on one or more processing requirements of each of the plurality of application processes and the processing capabilities of each hardware resource; and communicating instructions and data between each of the plurality of application processes and the hardware resources allocated to the respective application process.