Remote Access Controller Cloud Service Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing remote access controllers (RACs) in servers face challenges with memory constraints due to the need to store a full suite of features, leading to inefficiencies and increased costs, as well as limited customization options and unnecessary hardware dependencies.

Innovation Solution

The implementation of a system that includes a remote access controller (RAC) and a private cloud server (PCS) communicatively coupled to both the server and an external cloud server, where the RAC has a minimal set of built-in controls and features, and additional services are retrieved and executed from the PCS or external cloud as needed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a full suite of features is stored in RAC memory, then functionality and service capabilities are improved, but memory size and cost increase

Engineering Contradiction:
Improveservice capabilitiesVSAvoidmemory size
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system segments services into two categories: core services that remain in RAC firmware and additional services that are downloaded from the cloud. This segmentation allows the RAC to maintain essential functionality with minimal memory while obtaining extended capabilities on-demand from external sources.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts non-essential services from the RAC firmware and relocates them to cloud-based service repositories. This extraction reduces the memory burden on the RAC while preserving the ability to access these services when needed through download and execution mechanisms.

Inventive Principle:
Principle #2Taking out (Extraction)

2Adaptability or versatility

If a full suite of features is stored in RAC memory, then service functionality is improved, but device complexity and cost increase

Engineering Contradiction:
Improvefeature setVSAvoidhardware dependencies
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The RAC is designed with universal communication interfaces and service execution capabilities that can handle both core and additional services. This multi-functionality allows a single, simpler hardware platform to support a wide range of services without requiring specialized hardware for each feature.

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

Solution Approach 2:

The cloud-based service repository acts as an intermediary between the RAC and additional services. This mediator provides services that would otherwise require complex local implementation, allowing the RAC to maintain simplicity while accessing expanded functionality through the cloud intermediary.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Quantity of substance

If services are downloaded and executed from cloud, then RAC memory requirements are reduced, but network dependency increases

Engineering Contradiction:
Improvememory requirementsVSAvoidnetwork dependency
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The system performs preliminary actions by pre-downloading and caching additional services in the RAC's limited memory before they are needed. This preliminary action ensures that services are available locally when required, reducing real-time network dependency while still maintaining reduced memory requirements compared to storing all services permanently.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The service architecture is made dynamic, allowing the RAC to adapt its service set based on current operational needs. Services can be downloaded, cached, and executed dynamically rather than being statically configured, enabling the system to optimize between memory usage and network dependency based on real-time conditions.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS20250028584A1System and method for configuring a remote access controller
Publication Date: 2025.01.23 DELL PROD LP
  • US20250028584A1 patent drawing
  • US20250028584A1 patent drawing
  • US20250028584A1 patent drawing

AI summary

In one or more embodiments, one or more systems may comprise a Remote Access Controller (RAC) configured with a minimum number of built-in features and a private cloud server (PCS) communicatively coupled to the RAC and storing a set of available services retrieved from an external cloud server. The PCS can execute the set of available services to monitor and manage operation of the server. If the available service is a time-critical service, the PCS can install the available service on the RAC. When the available service is no longer needed, the PCS can uninstall the available service from the RAC.