O-Cloud Resource Status Management for Workload Reliability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The challenge in managing Open Radio Access Network (O-RAN) Cloud (O-Cloud) resources is the inefficient allocation and management of their status, particularly in scenarios where critical workloads need to be diverted from resources with performance issues, necessitating a system to update and manage the functional status effectively.

Innovation Solution

A method and system are provided to update the functional status of O-Cloud resources through recommendations from an rApp or manually by an O-Cloud Maintainer via the Service Management and Orchestration Framework (SMO), utilizing Infrastructure Management Services (IMS) to set resources into maintenance mode or other status updates based on observability data and metrics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual status management of O-Cloud resources is performed, then operational control is maintained, but management efficiency and responsiveness deteriorate

Engineering Contradiction:
Improvemanagement efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system enables self-service status management where the O-Cloud resource itself can initiate status change requests without requiring manual intervention. The resource monitors its own health metrics and can autonomously request status updates, reducing the operational burden on administrators while maintaining system control.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback mechanisms where status change requests are processed and confirmed through structured responses. The O-Cloud resource receives feedback about the status change outcome, enabling continuous monitoring and adjustment of resource allocation based on real-time performance data.

Inventive Principle:
Principle #23Feedback

2Reliability

If resources with performance issues are not identified, then resource allocation remains simple, but network performance deteriorates

Engineering Contradiction:
Improvenetwork performanceVSAvoidmonitoring complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system continuously monitors O-Cloud resource performance metrics and uses this feedback to automatically identify resources with performance issues. Health status data is collected and processed to determine when status changes are needed, enabling proactive performance management without excessive complexity.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system replaces manual performance assessment with automated electronic monitoring and analysis. Health metrics are collected through standardized interfaces and processed algorithmically to identify performance degradation, substituting manual inspection with automated systems that operate continuously.

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

3Productivity

If critical workloads are placed on all available resources, then resource utilization is maximized, but system reliability deteriorates when resources have performance issues

Engineering Contradiction:
Improveresource utilizationVSAvoidworkload placement reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system dynamically adjusts resource allocation based on real-time health status data. When a resource's status changes due to performance issues, the system automatically updates workload placement decisions to redirect critical workloads to healthier resources, optimizing both utilization and reliability in a dynamic environment.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system performs preliminary identification of potential performance issues through continuous health monitoring before they affect critical workloads. By detecting status changes early, the system can proactively adjust workload placement to prevent reliability deterioration rather than reacting after problems occur.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250227158A1System and method for managing status of o-cloud resource
Publication Date: 2025.07.10 RAKUTEN SYMPHONY INC
  • US20250227158A1 patent drawing
  • US20250227158A1 patent drawing
  • US20250227158A1 patent drawing

AI summary

Provided are a method, system, and device for changing the status of an Open Radio Access Network (O-RAN) Cloud (O-Cloud) resource, the method may include: obtaining, by a Service Management and Orchestration Framework (SMO) function, a first request or recommendation to update a functional status of an O-Cloud resource, the first request or recommendation being obtained from an rApp of a Non-Real-Time (Non-RT) RAN Intelligent Controller (RIC), or from an O-Cloud Maintainer, or from the SMO function directly; transmitting, by the SMO function to an Infrastructure Management Services (IMS), a second request to update the functional status of the O-Cloud resource based on the received first request or recommendation; and receiving, by the SMO function from the IMS, a first response as to whether the functional status of the O-Cloud resource was updated.