Remote Access Controller Firmware Binding to Proxy Services
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing remote access controllers (RACs) in data centers face inefficiencies due to unnecessary storage of all features in memory, limited customization options, and unnecessary ties to specific hardware capabilities, leading to increased memory requirements and complexity, with only about 35% of servers having the latest firmware, and subscription-based licensing being limited.
Innovation Solution
Implementing a system where RACs have minimal built-in firmware with augmentable features, allowing retrieval of needed services from a private cloud server, enabling vendor-agnostic, unified, and seamless system management with accelerated delivery of new services through subscription-based granular licensing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If all features are stored in RAC memory, then complete functionality is available, but memory requirements and system complexity increase
Solution Approach 1:
The patent segments RAC firmware into a minimal core set stored in RAC memory and additional features stored externally on the server. The minimal core includes only essential functions needed for basic operation, while optional features are maintained on the server and loaded dynamically when needed, thereby reducing RAC memory requirements while preserving complete functionality.
Solution Approach 2:
The patent moves firmware storage from a single dimension (RAC memory) to multiple dimensions by introducing external storage on the server. This allows the system to access firmware features both locally in RAC memory and remotely on the server, enabling complete functionality with reduced local memory requirements through cloud-based firmware repositories.
2Adaptability or versatility
If all features are stored in RAC memory, then complete functionality is available, but device complexity increases
Solution Approach 1:
The patent extracts non-essential firmware features from the RAC system and stores them externally on the server. The RAC retains only the minimal core firmware necessary for basic operation, while advanced or optional features are maintained separately on the server and loaded on-demand, thereby reducing system complexity while maintaining complete functionality.
Solution Approach 2:
The patent creates a universal firmware management system where the server acts as a centralized repository for all RAC features across multiple servers. This multi-functional approach allows a single external storage system to serve numerous RAC units, reducing individual RAC complexity while providing access to complete functionality through the shared firmware infrastructure.
3Reliability
If RAC firmware is updated traditionally, then latest features are available, but firmware adoption rate remains low at 35%
Solution Approach 1:
The patent implements preliminary action by pre-storing multiple firmware versions and feature sets on the server before they are needed. When a RAC requires an update or additional features, the firmware is already available on the server and can be rapidly deployed, eliminating the need for complex update coordination and significantly accelerating firmware adoption rates.
Solution Approach 2:
The patent enables self-service firmware updates where RACs can automatically retrieve and install firmware from the server without manual intervention. The system allows RACs to autonomously check for updates, download necessary firmware components, and apply updates themselves, dramatically improving firmware adoption rates by eliminating human-in-the-loop bottlenecks.
Data Source
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 RAC may be configured to communicate with a DHCP service, an onboarding service and a RAC proxy service to send a RAC hardware identity certificate and receive a RAC proxy service certificate. If the RAC hardware identity certificate and the RAC proxy service certificate are authenticated, the RAC proxy service may establish a binding with RAC firmware.