Management Processor Peripheral Registration Script

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional management processors, such as Baseboard Management Controllers (BMCs), often fail to effectively manage and monitor peripheral devices due to outdated logic, limited memory, and diversity in peripheral vendors and feature sets, leading to incomplete management and control capabilities.

Innovation Solution

The management processor reads API information from peripheral devices to register them as data providers, allowing the devices to self-describe and provide management resources, eliminating the need for firmware updates and enabling management, monitoring, or control through a RESTful interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the management processor uses conventional firmware-based logic to manage peripheral devices, then the management logic is fixed and reliable, but the adaptability to new peripheral devices and vendors is poor

Engineering Contradiction:

Improveadaptability to new peripheral devicesVSAvoidfirmware update complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The management processor transitions from static firmware-based logic to dynamic script-based logic that can be loaded and executed at runtime. This allows the management processor to adapt to new peripheral devices and vendors without requiring firmware updates, as scripts can be dynamically added to extend functionality.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system uses script files that copy and encapsulate management logic for specific peripheral devices. These scripts are stored externally and loaded into the management processor as needed, allowing the system to replicate management capabilities across different device types without modifying the core firmware.

Inventive Principle:

Principle #26Copying

2Adaptability or versatility

If the management processor includes built-in logic for all peripheral device types, then comprehensive management capability is achieved, but the memory and storage requirements increase significantly

Engineering Contradiction:

Improvemanagement capability coverageVSAvoidmemory and storage requirements

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The management logic is extracted from the management processor's internal firmware and stored as external script files. This separates the core management processor from device-specific logic, allowing comprehensive peripheral support without embedding all logic within the processor's limited memory.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The management processor is designed with a universal script execution environment that can load and run scripts for various peripheral device types. This single universal architecture replaces the need for multiple dedicated firmware implementations, reducing overall memory requirements while maintaining broad compatibility.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If the management processor firmware is updated to support new peripheral devices, then the management capability is improved, but the development and maintenance costs increase

Engineering Contradiction:

Improvesupport for new peripheral devicesVSAvoiddevelopment and maintenance cost

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The management system is segmented into a core management processor and separate device-specific script modules. Each script is an independent, self-contained unit that can be developed, tested, and maintained separately, reducing the complexity and cost of updates compared to modifying monolithic firmware.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Instead of investing in expensive, long-term firmware development cycles for each new device type, the system uses lightweight script files that can be quickly created, deployed, and replaced. These scripts are simpler to produce and maintain, reducing ongoing development costs.

Inventive Principle:

Principle #27Cheap short-living objects (Disposable)

4Measurement precision

If the management processor uses detailed information about peripheral devices for monitoring, then the reporting quality is improved, but the information processing complexity increases

Engineering Contradiction:

Improvereporting qualityVSAvoidinformation processing complexity

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

Script files act as intermediaries between the management processor and peripheral devices. These scripts contain device-specific knowledge and translate detailed device information into standardized management formats, allowing high-quality reporting without increasing the processing complexity of the core management processor.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10235074B2Management processor executing peripheral device registration script

Publication Date: 2019.03.19 HEWLETT PACKARD ENTERPRISE DEV LP

AI summary

Various examples described herein provide for a management processor that reads a registration script from a peripheral device, and uses the script to act in proxy to register the peripheral device as a data provider on the management processor. Once a peripheral device is registered as a data provider on the management processor, the management processor can permit the peripheral device to host a management resource on the management processor. By accessing the hosted management resource through the management processor, a client can manage, monitor, or control the peripheral device.