BMC customization plug-in running method and device based on cloud distribution, and medium

CN122431749APending Publication Date: 2026-07-21NINGCHANG INFORMATION TECH (HANGZHOU) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
NINGCHANG INFORMATION TECH (HANGZHOU) CO LTD
Filing Date
2026-04-29
Publication Date
2026-07-21

AI Technical Summary

Technical Problem

Traditional BMC firmware uses a monolithic architecture, resulting in insufficient customization capabilities, serious waste of storage space, and a time-consuming and risky update process. Existing package managers or containerization solutions have security and stability issues in the BMC environment.

Method used

The BMC custom plugin runtime method, based on cloud distribution, enables on-demand deployment and fine-grained updates of plugins through a lightweight dynamic library loading mechanism, hardware root trust signature verification, and behavior baseline monitoring. Combined with atomic pointer swapping and hardware metric observation period verification, security and stability are ensured.

Benefits of technology

It significantly reduces storage consumption and update risks, improves the flexibility and reliability of server-level management, reduces business interruption risks, and is compatible with BMC's resource-constrained environment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122431749A_ABST
    Figure CN122431749A_ABST
Patent Text Reader

Abstract

The application relates to the computer technical field, and particularly discloses a BMC customization plug-in running method and device based on cloud distribution, and a medium. The method comprises the following steps: obtaining plug-in installation requirements, determining a target plug-in identifier, and obtaining a cloud-distributed lightweight target plug-in package according to the target plug-in identifier; after successful acquisition, performing digital signature verification on the target plug-in package by using a public key pre-stored in a BMC end, parsing a manifest file in the target plug-in package after the verification, and obtaining dependency relationship information, resource requirement information and permission declaration information; checking whether the currently installed plug-in satisfies the dependency relationship indicated by the dependency relationship information, and checking the available resources of the BMC end according to the resource requirement information; if both the checks are passed, installing the target plug-in package, setting an upper limit of resource usage of a runtime of the target plug-in according to the permission declaration information and the resource requirement information; starting runtime monitoring, establishing a normal behavior baseline, and isolating the target plug-in when detecting that the actual behavior of the target plug-in deviates from the normal behavior baseline.
Need to check novelty before this filing date? Find Prior Art