O-RAN API for Dynamic Signal Processing Allocation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing default allocation of signal processing operations in Open Radio Access Networks (O-RAN) between radio units (RUs) and distributed units (DUs) is limiting, as it restricts bandwidth, latency, and flexibility, failing to optimize network performance for diverse user requirements such as autonomous vehicles and standard voice services.

Innovation Solution

Implementing an Application Programming Interface (API) to dynamically allocate signal processing operations between O-RAN RUs and DUs, allowing for flexible configuration based on specific client needs by indicating functional splits, such as the 7.2 split, and utilizing APIs to communicate split information and allocate functions between RUs and DUs, enabling dynamic adaptation of L1 processing and acceleration techniques.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If default allocation of signal processing operations is used between RU and DU, then network configuration is simple, but bandwidth utilization and latency are suboptimal

Engineering Contradiction:
Improvebandwidth utilizationVSAvoidallocation configuration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements dynamic allocation of signal processing operations between RU and DU using an API that allows runtime configuration of functional splits. The system transitions from static default allocation to dynamic allocation where the network controller can adjust which operations (e.g., FFT, channel estimation, beamforming) are performed at RU versus DU based on real-time network conditions, user requirements, and resource availability, thereby optimizing bandwidth utilization and latency without permanent configuration changes

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the allocation parameter from fixed default values to dynamically adjustable parameters through an API interface. The API accepts input parameters specifying functional split configurations (e.g., which signal processing operations are allocated to RU vs DU) and translates them into operational configurations. This allows continuous adjustment of allocation parameters to optimize performance metrics such as bandwidth utilization and latency while maintaining simple configuration through standardized interface calls

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If default allocation settings are used, then system setup is straightforward, but flexibility to accommodate diverse user requirements is limited

Engineering Contradiction:
Improveflexibility for diverse user requirementsVSAvoidsystem configuration ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent creates a universal API interface that can accommodate multiple user requirements and service types (e.g., autonomous vehicles, voice services, data services) through a single standardized configuration mechanism. The API provides multi-functionality by supporting various functional split configurations and allocation scenarios, allowing the same interface to serve diverse user needs without requiring separate configuration systems for each service type or user category

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

Solution Approach 2:

The system transitions from static default allocation to dynamic allocation where the network controller can adjust which operations are performed at RU versus DU based on real-time network conditions, user requirements, and resource availability. This dynamic adaptation enables the system to flexibly accommodate diverse user requirements such as low-latency autonomous vehicle communications versus standard voice services while maintaining ease of operation through automated API-based configuration

Inventive Principle:
Principle #15Dynamics

3Reliability

If static functional split is implemented, then resource allocation is simple, but network performance optimization is restricted

Engineering Contradiction:
Improvenetwork performance optimizationVSAvoiddynamic allocation mechanism
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an API as an intermediary layer between the network controller and the RU/DU units. This intermediary translates high-level allocation requests into specific functional split configurations, managing the complexity of dynamic resource allocation while presenting a simple interface to users. The API handles the coordination and configuration details, shielding the complexity of dynamic allocation mechanisms from end users while enabling sophisticated network performance optimization

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If default allocation is used, then implementation is straightforward, but computing resource efficiency is reduced

Engineering Contradiction:
Improvecomputing resource efficiencyVSAvoidallocation configuration
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent enables self-service automated allocation where the network controller automatically determines and configures the optimal functional split between RU and DU based on current network conditions, user requirements, and resource availability. The system monitors performance metrics and autonomously adjusts allocations without requiring manual configuration, thereby improving computing resource efficiency while maintaining ease of operation through automated decision-making and configuration

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20250021411A1Application programming interface to cause software program allocation
Publication Date: 2025.01.16 NVIDIA CORP
  • US20250021411A1 patent drawing
  • US20250021411A1 patent drawing
  • US20250021411A1 patent drawing

AI summary

Apparatuses, systems, and techniques to perform an API to indicate an allocation of wireless signal processing operations. In at least one embodiment, a distributed unit and radio unit perform one or more operations based, at least in part, on an indicated allocation. In at least one embodiment, a processor comprising one or more circuits performs an application programming interface (API) to indicate an allocation of wireless signal processing operations between one or more Open Radio Access Network (O-RAN) radio units (RUs) and one or more O-RAN distributed units (DUs).