Cloud RAN Infrastructure Profiles for Consistent Multi-Site Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for configuring and managing cloud-based Radio Access Network (RAN) infrastructure are manual, error-prone, and not scalable, leading to deployment issues due to mismatched parameters and non-compliance with RAN node requirements, especially in large deployments across multiple data centers.

Innovation Solution

A profile-based infrastructure management system that applies standardized data models and monitors settings to ensure compliance, involving Compute, Networking, Accelerator, Storage, and Application profiles, with actions like BIOS updates and interface configurations, to create a consistent deployment environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual configuration methods are used for cloud infrastructure, then flexibility in handling diverse hardware is maintained, but deployment efficiency and consistency deteriorate due to human error and non-scalability

Engineering Contradiction:
Improvedeployment efficiencyVSAvoidconfiguration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent replaces manual mechanical configuration processes with automated software-based profile application. The system automatically applies pre-defined configuration profiles to cloud infrastructure elements, substituting human operators with automated scripts and tools that enforce consistent configuration across diverse hardware platforms.

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

Solution Approach 2:

The patent transforms configuration management from manual parameter setting to automated profile-based parameter application. Configuration parameters are predefined in profiles that can be automatically applied to multiple infrastructure elements, changing the management approach from individual parameter configuration to bulk profile deployment.

Inventive Principle:
Principle #35Parameter changes

2Manufacturing precision

If manual configuration procedures are used, then adaptability to specific hardware is maintained, but configuration accuracy and compliance deteriorate due to parameter mismatches

Engineering Contradiction:
Improveconfiguration accuracyVSAvoiddeployment time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-defining configuration profiles that contain all necessary configuration parameters and settings. These profiles are prepared in advance and validated before deployment, ensuring configuration accuracy is built into the system beforehand rather than verified during manual configuration.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent incorporates feedback mechanisms through automated validation that checks whether applied configurations match the defined profiles. The system provides feedback on configuration compliance and can automatically correct deviations, ensuring accuracy while maintaining rapid deployment.

Inventive Principle:
Principle #23Feedback

3Stability of the object's composition

If standardized profile-based management is implemented, then deployment consistency is improved, but initial system complexity increases due to profile definition and management overhead

Engineering Contradiction:
Improvedeployment consistencyVSAvoidsystem complexity
Core Design Contradiction:
Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The patent applies universality by designing configuration profiles that can be reused across multiple cloud infrastructure elements and different hardware platforms. A single profile can serve multiple purposes and be applied universally, reducing the need for custom configurations and simplifying the overall system despite the initial standardization effort.

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

4Productivity

If automated profile application is used, then scalability to large deployments is improved, but monitoring and validation complexity increases

Engineering Contradiction:
Improvedeployment scalabilityVSAvoidvalidation complexity
Core Design Contradiction:
ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements self-service through automated validation mechanisms that independently check configuration compliance without requiring manual intervention. The system automatically detects configuration deviations and can self-correct or report issues, enabling scalable deployment while keeping validation complexity managed through automation rather than manual processes.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12563435B2Methods for profile based management of infrastructure of a cloud used for ran applications
Publication Date: 2026.02.24 MAVENIR US INC
  • US12563435B2 patent drawing
  • US12563435B2 patent drawing
  • US12563435B2 patent drawing

AI summary

A method is presented which enables a controlled mechanism of applying the required set of settings, e.g., for cloud-based network infrastructure, by means of “profiles”. Infrastructure Management Service (IMS) applies one or more of Compute profile, Networking profile, Storage profile, Accelerator profile, and Application (“App”) profile to cloud infrastructure. The following set of procedures are defined to achieve the profile-based infrastructure management: a) profile definition; b) cloud-infrastructure-preparation based on profile(s); c) cloud audit and monitoring; and d) cloud preparation based on capability. Applying of a profile can involve one or more of: updating the BIOS settings, e.g., using Intelligent Platform Management Interface (IPMI) commands; updating the GRUB settings; updating the system/kernel parameters; updating interfaces (e.g., alias, bonding, etc.); creating required resources (e.g., virtual functions (VFs) and corresponding bindings); creating resource maps to be used by plug-ins; and running any scripts for custom needs of the RAN application.