O-Cloud Node Draining via SMO and O2 Coordination
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing O-RAN cloud (O-Cloud) resources face inefficiencies, including waste and potential failures, necessitating proactive management and resource optimization.
Innovation Solution
A method and system for draining O-Cloud Nodes by marking them as cordoned or unschedulable, allowing Network Functions to be relocated or terminated, based on recommendations from rApps or manual input, using the SMO and O2 interface to manage resource allocation and migration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If O-Cloud resources are continuously allocated without active management, then resource availability is maintained, but resource waste increases and system reliability deteriorates
Solution Approach 1:
The system performs preliminary actions by proactively identifying underutilized or failing O-Cloud nodes through monitoring metrics and draining them before actual failures occur. This prevents service disruptions and optimizes resource allocation in advance, resolving the contradiction between maintaining reliability and reducing resource waste.
Solution Approach 2:
The system implements continuous feedback loops by monitoring O-Cloud node performance metrics, analyzing resource utilization patterns, and automatically triggering drainage operations when thresholds are exceeded. This feedback mechanism enables dynamic resource management that simultaneously improves reliability through early failure detection and reduces waste by deallocating unused resources.
2Productivity
If O-Cloud nodes are proactively drained based on recommendations, then resource efficiency is improved, but system complexity increases
Solution Approach 1:
The patent introduces an intermediary O2 interface between the SMO and O-Cloud nodes that standardizes the drainage control process. This intermediary layer abstracts the complexity of resource management operations, providing a uniform mechanism for issuing drain commands and receiving status updates, thereby improving resource efficiency without proportionally increasing overall system complexity.
Solution Approach 2:
The system manages complexity by focusing on changing key operational parameters such as node status states (active, draining, cordoned) and resource allocation thresholds. By standardizing these parameter transitions through the O2 interface, the system achieves efficient resource management through controlled parameter changes rather than complex operational procedures.
3Loss of energy
If Network Functions are relocated during node drainage, then resource optimization is achieved, but service disruption risk increases
Solution Approach 1:
The system performs preliminary actions by initiating the drainage process well before actual node failure or resource exhaustion occurs. This advance notice allows Network Functions to be gradually relocated to other nodes while maintaining service continuity, achieving resource optimization without causing disruptions. The cordoned status is applied proactively to enable controlled migration.
Solution Approach 2:
The drainage process is implemented dynamically through controlled status transitions rather than abrupt node shutdowns. The system transitions nodes through staged states (active → draining → cordoned) that allow Network Functions to be progressively relocated. This dynamic approach enables resource optimization while maintaining service continuity through gradual redistribution of workloads.
Data Source
AI summary
Provided are a method, system, and an Service Management and Orchestration Framework (SMO) and O-Cloud to drain one or more O-Cloud Nodes based on recommendations from an rApp or manually by an O-Cloud Maintainer via the SMO. In particular, the method may include: receiving, by a SMO function, a first request or recommendation to drain at least one O-Cloud Node, the first request or recommendation being received from an rApp of a Non-Real-Time (Non-RT) RAN Intelligent Controller (RIC) or from an O-Cloud Maintainer; transmitting, by the SMO function to an Infrastructure Management Services (IMS) and/or Deployment Management Services (DMS) via an O2 interface, a second request to drain the at least one O-Cloud Node based on the received first request or recommendation; and receiving, from the IMS/DMS, a first notification as to whether the at least one O-Cloud Node has been drained.