Cloud Telemetry Streaming for Minimal-Memory Server RACs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing remote access controllers (RACs) in servers are resource-intensive due to storing a full suite of features regardless of actual usage, leading to inefficiencies and limitations in customization and licensing, particularly with increasing memory requirements and hardware-specific feature ties.
Innovation Solution
Implementing a remote access controller (RAC) with minimal built-in features and leveraging a private cloud server to dynamically retrieve and execute needed services from an external cloud, allowing for vendor-agnostic, unified management and subscription-based licensing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a full suite of features is stored in the RAC regardless of actual usage, then the system provides complete functionality, but memory usage increases and resource efficiency decreases
Solution Approach 1:
The patent segments the RAC features into two categories: a minimal built-in feature set that resides in the RAC's local memory, and additional services that are stored remotely in the private cloud server. The RAC dynamically retrieves and executes only the services it needs from the cloud, rather than storing all services locally. This segmentation resolves the contradiction by providing complete functionality through the combination of local and remote features while keeping local memory usage minimal.
2Reliability
If hardware-specific features are tightly coupled, then device functionality is optimized, but customization and licensing flexibility are reduced
Solution Approach 1:
The patent implements a universal service management architecture where the RAC can dynamically access and execute services from a centralized private cloud server that serves multiple RACs. This universal approach allows the same RAC hardware to be customized for different applications by retrieving different service sets from the cloud, enabling flexible licensing and customization without requiring hardware-specific feature coupling. The private cloud acts as a universal repository that can serve any RAC with appropriate services.
3Reliability
If telemetry data is collected from all devices on the server, then comprehensive monitoring is achieved, but data transmission volume increases
Solution Approach 1:
The patent extracts the telemetry data processing function from the individual RACs and centralizes it in the private cloud server. Each RAC collects telemetry data from its local devices and transmits it to the private cloud, which then aggregates, filters, and processes the data. This extraction resolves the contradiction by maintaining comprehensive monitoring through centralized collection while reducing the data transmission burden on individual RACs and network bandwidth through intelligent data processing at the cloud level.
4Quantity of substance
If a minimal RAC feature set is implemented, then memory usage is reduced, but the system requires external cloud services for full functionality
Solution Approach 1:
The patent introduces a private cloud server as an intermediary between the minimal RAC devices and the external cloud services. The private cloud acts as a local service repository and management layer that RACs can access without requiring direct connections to external cloud providers. This intermediary resolves the contradiction by enabling the minimal RAC architecture to access comprehensive services while reducing system architecture complexity through localized service management and caching capabilities.
Data Source
AI summary
In one or more embodiments, one or more information handling 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 telemetry services. The PCS can execute the telemetry services to monitor and manage telemetry operations of a plurality of servers. The PCS may receive a first set of telemetry data from one or more servers, receive outgoing telemetry traffic associated with the first set of telemetry data, determine one or more telemetry collection requirements and communicate a second set of telemetry data and communicate a second set of telemetry data to the external cloud server, wherein the second set of telemetry data communicated to the external cloud server contains less data than the first set of telemetry data and meets the one or more telemetry collection requirements.