Heterogeneous server out-of-band control system based on unified semantic abstraction

Abstract

The invention provides a heterogeneous server out-of-band control system based on unified semantic abstraction, which comprises a protocol compatible device, the protocol compatible device is provided with a semantic abstraction module, and Redfish protocol requests of servers of different manufacturers are converted into a unified format and sent to a server control center; the server control center issues a Redfish request instruction to the protocol compatible device, and then the Redfish request instruction is converted into a Redfish protocol request of a specific server through the semantic abstraction module and sent to the specific server. Standardized operation interfaces (such as startup and shutdown, firmware upgrading and fan speed regulation) are provided for a multi-manufacturer and multi-generation server cluster and a server control center. And the system automatically and dynamically maps the request into an equivalent Redfish instruction of each manufacturer device, uniformly returns a value format and a state code, shields hardware difference, and realizes cross-platform non-inductive operation.

Description

Technical Field

[0001] This invention belongs to the field of server hardware management technology, and in particular relates to an out-of-band control system for heterogeneous servers based on unified semantic abstraction. Background Technology

[0002] With the advancement of cloud computing, big data, and information technology innovation projects, data centers often house servers from multiple vendors and generations, including Dell, HPE, Inspur, Lenovo, Huawei, and Sugon. To achieve automated management and monitoring of large-scale server clusters, out-of-band management is typically used to monitor server hardware status and perform corresponding remote operations.

[0003] Existing patent CN116827757A discloses a remote cluster management method and system. The method includes: establishing a connection between a management terminal and servers in a server cluster via the Redfish protocol; sending an information retrieval request to the server cluster by calling the server's Redfish interface to obtain basic information about the server cluster; sending a remote modification command to the server by calling the server's Redfish interface to remotely modify the configuration information on the server; sending a data retrieval request to the server by calling the server's Redfish interface to obtain real-time monitoring data of the server, and performing server fault diagnosis based on the real-time monitoring data; and sending a fault repair command to the faulty server by calling the Redfish interface of the faulty server to perform remote fault repair operations on the faulty server. Through the technical solution of this invention, remote monitoring, configuration, and maintenance of servers can be achieved, thereby saving time and resources and improving management efficiency. Summary of the Invention

[0004] Data centers often house servers from multiple vendors and generations, including Dell, HPE, Inspur, Lenovo, Huawei, and Sugon, with significant differences in their implementations of the DMTF Redfish protocol. Current technologies, such as Open BMC, Ansible modules, or vendor-provided SDKs, only address single-brand or single-function scenarios, failing to provide unified out-of-band management across vendors and versions, and also lacking a rapid expansion mechanism for domestic IT innovation platforms.

[0005] To solve the above-mentioned technical problems, the technical solution provided by the present invention is as follows: a heterogeneous server out-of-band control system based on unified semantic abstraction, including a protocol compatibility unit. The protocol compatibility unit is equipped with a semantic abstraction module, which converts Redfish protocol requests from servers of different vendors into a unified format and sends them to the server control center. The server control center issues Redfish request instructions to the protocol compatibility unit, which then converts them into Redfish protocol requests for specific servers through the semantic abstraction module and sends them to the specific servers.

[0006] Specifically, the protocol compatibility unit also includes a server monitoring module, which continuously monitors the server's capability description file and detects whether any new servers have been added.

[0007] Specifically, the protocol compatibility device has a script extension interface. The extended logic scripts accessed through the script extension interface are isolated from the main code sandbox, so that the system stability is not affected during upgrades or rollbacks.

[0008] Specifically, the semantic abstraction module automatically maps the "path-parameter-authentication-error code" quadruples of Redfish interfaces from different vendors into unified atomic operation primitives through deep reverse modeling and semantic mapping.

[0009] Specifically, the semantic abstraction module has a two-way mapping table for unified atomic operation primitives. When the server vendor upgrades the Redfish version, causing changes to fields or paths, the system uses the two-way mapping table to complete the conversion between the old and new fields in real time, and is backward compatible.

[0010] Specifically, the semantic abstraction module uses a two-layer description of JSON Schema and semantic tags to normalize the heterogeneous data returned by various vendors into a standardized business model in real time and send it to the server control center. When communicating with the server control center, the semantic abstraction module exposes only a single data format and retains the original field traceability within the semantic abstraction module.

[0011] Specifically, when relevant business processes within the server control center communicate with the semantic abstraction module, all out-of-band server control operations can be completed using only a single function signature.

[0012] Specifically, the protocol compatibility module also has a log output module that uses a centralized token gateway to converge various vendors' private authentication protocols into a single OAuth2 or bidirectional TLS channel, and outputs all operation logs in a unified audit format.

[0013] Specifically, when the server monitoring module detects a new server accessing the network, it reads the server's capability description file and compares it with the local capability description file to identify its Redfish version and feature subset, and automatically loads the corresponding adaptation plugin.

[0014] Specifically, when a server vendor upgrades its Redfish version, the bidirectional mapping table uses an incremental distribution strategy, which does not affect the interaction between the server control center and servers from other vendors, ensuring the continuous operation of upper-layer applications.

[0015] The beneficial effect of this invention is that it solves the compatibility pain points caused by Redfish version fragmentation and vendor implementation differences in heterogeneous server hardware management. By constructing a lightweight Redfish version compatibility manager, with "downward shielding of differences and upward unification of semantics" as its core, it automatically adapts to mainstream vendors such as Dell, HPE, and Inspur and their various versions of Redfish interfaces without modifying the upper-layer business logic. This achieves standardized, seamless invocation and one-time integration for multi-terminal reuse in server lifecycle management, thereby significantly reducing operational complexity and development costs. Attached Figure Description

[0016] Figure 1 This is a system structure diagram of the present invention. Detailed Implementation

[0017] The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0018] Example 1: An out-of-band control system for heterogeneous servers based on unified semantic abstraction, such as... Figure 1 As shown, the system includes a protocol compatibility module, which incorporates a semantic abstraction module. This module transforms Redfish protocol requests from servers of different vendors into a unified format and sends them to the server control center. The server control center issues Redfish request commands to the protocol compatibility module, which then uses the semantic abstraction module to transform them into Redfish protocol requests specific to each server before sending them to that server. For multi-vendor, multi-generation server clusters, the server control center provides standardized operation interfaces (such as power on / off, firmware upgrades, and fan speed adjustments). The system automatically and dynamically maps requests to equivalent Redfish commands for each vendor's devices and unifies the return value format and status codes, masking hardware differences and enabling seamless cross-platform operation.

[0019] The protocol compatibility adapter also includes a server monitoring module. This module continuously monitors the server's capability description file (CAPM) to detect any newly connected servers. The server monitoring module introduces a self-discovery mechanism based on the CapabilityManifest: after a new brand / model server connects to the network, the system identifies its Redfish version and feature subset within seconds and automatically loads the corresponding adapter plugin, without requiring a management platform restart or modification of business code—truly achieving "plug and play." When adding a server (including new vendors or new generation models), only its Redfish version and interface prefix configuration need to be entered in the management center according to the standardized format. The management center automatically recognizes this configuration and, after registering the server's MAC address, instantly retrieves complete hardware information from the configuration file, achieving plug-and-play functionality with zero manual intervention.

[0020] The protocol compatibility server features a script extension interface. The extended logic scripts accessed through this interface are sandboxed and isolated from the main codebase, ensuring platform stability during upgrades or rollbacks. The server control center provides an open ScriptableExtension Slot interface, supporting Python / Go / Lua hot scripts and containerized micro-plugins. Users can quickly add custom strategies (such as AI predictive fan speed control and national cryptographic algorithm authentication) without touching the main codebase, ensuring stability while unleashing the ecosystem's innovative potential.

[0021] The semantic abstraction module uses deep reverse modeling and semantic mapping to automatically map the "path-parameter-authentication-error code" quadruples of Redfish interfaces from different vendors into unified atomic operation primitives. Through deep reverse modeling and semantic mapping, the differences between Redfish interfaces from various vendors in dimensions such as path, parameters, authentication, pagination, and error codes are converged into a set of atomic-level operation primitives. Upper-layer business logic only needs to call the same function signature to complete all operations such as power control, firmware updates, and sensor readings, achieving true "vendor-free" integration and reducing integration workload by more than 80%. The semantic abstraction module uses a runtime mapping engine to automatically map the "path-parameter-authentication-error code" quadruples of Redfish interfaces from different vendors into unified atomic operation primitives; upper-layer business code can complete all out-of-band operations such as power, firmware, and sensor operations with only a single function signature, without needing to be aware of vendor differences.

[0022] The semantic abstraction module includes a two-way mapping table. When a server vendor upgrades its Redfish version, causing changes to fields or paths, the system uses this mapping table to convert between old and new fields in real time, ensuring backward compatibility. The mapping table can be incrementally deployed, ensuring that upper-layer applications can continue to run with "zero modifications."

[0023] The semantic abstraction module employs a two-layer description system of JSON Schema and semantic tags to normalize heterogeneous data returned by various vendors into standardized business models in real time before sending them to the server control center. When communicating with the server control center, the semantic abstraction module exposes only a single data format and retains the original field traceability within itself. This two-layer system of JSON Schema and semantic tags translates heterogeneous fields returned by different vendors into standardized business models in real time and includes a built-in version routing engine. When vendors upgrade their Redfish versions or when field naming changes, the system automatically maps the old and new fields and performs compatibility rollback, ensuring continuous operation of upper-layer applications with "zero modifications."

[0024] The protocol compatibility module also includes a log output module. Through a centralized token gateway, it consolidates various vendors' proprietary authentication protocols into a single OAuth2 or bidirectional TLS channel, outputting all operation logs in a unified audit format. The centralized token gateway consolidates various vendors' proprietary authentication protocols (Basic, Session, Token, X-Auth, etc.) into a single OAuth2 / bidirectional TLS channel; all operation logs are output in a unified audit format, meeting compliance requirements for information security standards and financial institutions.

[0025] This embodiment constructs a sustainable and evolving open ecosystem, enabling any third-party developer to quickly output scenario-based plugins based on this platform, forming a win-win three-layer pattern of "platform-plugin-application".

[0026] Example 2: An out-of-band control system for heterogeneous servers based on unified semantic abstraction includes a protocol compatibility unit. The protocol compatibility unit has a semantic abstraction module that converts Redfish protocol requests from servers of different vendors into a unified format and sends them to the server control center. The server control center issues Redfish request commands to the protocol compatibility unit, which then uses the semantic abstraction module to convert them into Redfish protocol requests specific to each server and sends them to that server. For multi-vendor, multi-generation server clusters, the server control center provides standardized operation interfaces (such as power on / off, firmware upgrades, and fan speed control). The system automatically and dynamically maps requests to equivalent Redfish commands for each vendor's devices and unifies the return value format and status codes, masking hardware differences and achieving seamless cross-platform operation.

[0027] The protocol compatibility adapter also includes a server monitoring module. This module continuously monitors the server's capability description file (CAPM) to detect any newly connected servers. The server monitoring module introduces a self-discovery mechanism based on the CapabilityManifest: after a new brand / model server connects to the network, the system identifies its Redfish version and feature subset within seconds and automatically loads the corresponding adapter plugin, without requiring a management platform restart or modification of business code—truly achieving "plug and play." When adding a server (including new vendors or new generation models), only its Redfish version and interface prefix configuration need to be entered in the management center according to the standardized format. The management center automatically recognizes this configuration and, after registering the server's MAC address, instantly retrieves complete hardware information from the configuration file, achieving plug-and-play functionality with zero manual intervention.

[0028] The protocol compatibility server features a script extension interface. The extended logic scripts accessed through this interface are sandboxed and isolated from the main codebase, ensuring platform stability during upgrades or rollbacks. The server control center provides an open ScriptableExtension Slot interface, supporting Python / Go / Lua hot scripts and containerized micro-plugins. Users can quickly add custom strategies (such as AI predictive fan speed control and national cryptographic algorithm authentication) without touching the main codebase, ensuring stability while unleashing the ecosystem's innovative potential.

[0029] The semantic abstraction module uses deep reverse modeling and semantic mapping to automatically map the "path-parameter-authentication-error code" quadruples of Redfish interfaces from different vendors into unified atomic operation primitives. Through deep reverse modeling and semantic mapping, the differences between Redfish interfaces from various vendors in dimensions such as path, parameters, authentication, pagination, and error codes are converged into a set of atomic-level operation primitives. Upper-layer business logic only needs to call the same function signature to complete all operations such as power control, firmware updates, and sensor readings, achieving true "vendor-free" integration and reducing integration workload by more than 80%. The semantic abstraction module uses a runtime mapping engine to automatically map the "path-parameter-authentication-error code" quadruples of Redfish interfaces from different vendors into unified atomic operation primitives; upper-layer business code can complete all out-of-band operations such as power, firmware, and sensor operations with only a single function signature, without needing to be aware of vendor differences.

[0030] The semantic abstraction module includes a two-way mapping table. When a server vendor upgrades its Redfish version, causing changes to fields or paths, the system uses this mapping table to convert between old and new fields in real time, ensuring backward compatibility. The mapping table can be incrementally deployed, ensuring that upper-layer applications can continue to run with "zero modifications."

[0031] The semantic abstraction module employs a two-layer description system of JSON Schema and semantic tags to normalize heterogeneous data returned by various vendors into standardized business models in real time before sending them to the server control center. When communicating with the server control center, the semantic abstraction module exposes only a single data format and retains the original field traceability within itself. This two-layer system of JSON Schema and semantic tags translates heterogeneous fields returned by different vendors into standardized business models in real time and includes a built-in version routing engine. When vendors upgrade their Redfish versions or when field naming changes, the system automatically maps the old and new fields and performs compatibility rollback, ensuring continuous operation of upper-layer applications with "zero modifications."

[0032] The protocol compatibility module also includes a log output module. Through a centralized token gateway, it consolidates various vendors' proprietary authentication protocols into a single OAuth2 or bidirectional TLS channel, outputting all operation logs in a unified audit format. The centralized token gateway consolidates various vendors' proprietary authentication protocols (Basic, Session, Token, X-Auth, etc.) into a single OAuth2 / bidirectional TLS channel; all operation logs are output in a unified audit format, meeting compliance requirements for information security standards and financial institutions.

[0033] This embodiment constructs a sustainable and evolving open ecosystem, enabling any third-party developer to quickly output scenario-based plugins based on this platform, forming a win-win three-layer pattern of "platform-plugin-application".

[0034] Compared to existing single-type out-of-band server management systems, this embodiment represents a significant improvement across all dimensions. At the server access level, existing out-of-band server management systems require the separate development of adaptation scripts or plugins for each new brand / model server, necessitating weekly or monthly manual maintenance. In contrast, this embodiment, through the server monitoring module's self-discovery mechanism and Capability Manifest, achieves "plug and play" functionality within minutes, reducing labor costs by over 70%.

[0035] At the server operation and maintenance interaction level, existing out-of-band server management systems require multiple CLI / Web interfaces, login addresses, and account systems for servers of various brands and models, necessitating the use of multiple sets of different communication and interaction terminology, which is prone to errors. This embodiment, however, unifies REST / JSON semantics through a semantic abstraction module, allowing a single portal / script to operate servers from vendors such as Dell, HPE, Lenovo, and Inspur, enabling operation of servers from all brands.

[0036] At the server upgrade level, existing out-of-band management systems can cause scripts to malfunction when vendors upgrade Redfish versions or change fields, requiring emergency hotfixes. This embodiment, however, incorporates version routing and field mapping. When vendors upgrade Redfish versions or cause breaking changes in field naming, the system automatically completes the mapping between old and new fields and rolls back to compatibility, ensuring continuous operation of upper-layer applications with "zero modifications" and achieving 100% business compatibility.

[0037] At the extension script level, existing out-of-band server management systems often have proprietary, closed SDKs, requiring reverse engineering or waiting for vendor roadmaps for secondary development. This embodiment, however, opens up a Scriptable Extension Slot, supporting hot-plugging of Python / Go / Lua scripts, allowing the ecosystem to grow organically.

[0038] At the data auditing level, existing out-of-band server management systems face difficulties in compliance auditing due to the presence of servers from multiple vendors and inconsistent credentials, protocols, and audit formats. This embodiment, however, features unified authentication, unified audit logs, and a unified national cryptographic / encrypted channel, meeting the requirements for information security level protection and financial-grade compliance.

[0039] Example 3: An out-of-band control system for heterogeneous servers based on unified semantic abstraction includes a protocol compatibility unit. The protocol compatibility unit has a semantic abstraction module that converts Redfish protocol requests from servers of different vendors into a unified format and sends them to the server control center. The server control center issues Redfish request commands to the protocol compatibility unit, which then uses the semantic abstraction module to convert them into Redfish protocol requests specific to each server and sends them to that server. For multi-vendor, multi-generation server clusters, the server control center provides standardized operation interfaces (such as power on / off, firmware upgrades, and fan speed control). The system automatically and dynamically maps requests to equivalent Redfish commands for each vendor's devices and unifies the return value format and status codes, masking hardware differences and achieving seamless cross-platform operation.

[0040] The protocol compatibility adapter also includes a server monitoring module. This module continuously monitors the server's capability description file (CAPM) to detect any newly connected servers. The server monitoring module introduces a self-discovery mechanism based on the CapabilityManifest: after a new brand / model server connects to the network, the system identifies its Redfish version and feature subset within seconds and automatically loads the corresponding adapter plugin, without requiring a management platform restart or modification of business code—truly achieving "plug and play." When adding a server (including new vendors or new generation models), only its Redfish version and interface prefix configuration need to be entered in the management center according to the standardized format. The management center automatically recognizes this configuration and, after registering the server's MAC address, instantly retrieves complete hardware information from the configuration file, achieving plug-and-play functionality with zero manual intervention.

[0041] The protocol compatibility server features a script extension interface. The extended logic scripts accessed through this interface are sandboxed and isolated from the main codebase, ensuring platform stability during upgrades or rollbacks. The server control center provides an open ScriptableExtension Slot interface, supporting Python / Go / Lua hot scripts and containerized micro-plugins. Users can quickly add custom strategies (such as AI predictive fan speed control and national cryptographic algorithm authentication) without touching the main codebase, ensuring stability while unleashing the ecosystem's innovative potential.

[0042] The semantic abstraction module uses deep reverse modeling and semantic mapping to automatically map the "path-parameter-authentication-error code" quadruples of Redfish interfaces from different vendors into unified atomic operation primitives. Through deep reverse modeling and semantic mapping, the differences between Redfish interfaces from various vendors in dimensions such as path, parameters, authentication, pagination, and error codes are converged into a set of atomic-level operation primitives. Upper-layer business logic only needs to call the same function signature to complete all operations such as power control, firmware updates, and sensor readings, achieving true "vendor-free" integration and reducing integration workload by more than 80%. The semantic abstraction module uses a runtime mapping engine to automatically map the "path-parameter-authentication-error code" quadruples of Redfish interfaces from different vendors into unified atomic operation primitives; upper-layer business code can complete all out-of-band operations such as power, firmware, and sensor operations with only a single function signature, without needing to be aware of vendor differences.

[0043] The semantic abstraction module includes a two-way mapping table. When a server vendor upgrades its Redfish version, causing changes to fields or paths, the system uses this mapping table to convert between old and new fields in real time, ensuring backward compatibility. The mapping table can be incrementally deployed, ensuring that upper-layer applications can continue to run with "zero modifications."

[0044] The semantic abstraction module employs a two-layer description system of JSON Schema and semantic tags to normalize heterogeneous data returned by various vendors into standardized business models in real time before sending them to the server control center. When communicating with the server control center, the semantic abstraction module exposes only a single data format and retains the original field traceability within itself. This two-layer system of JSON Schema and semantic tags translates heterogeneous fields returned by different vendors into standardized business models in real time and includes a built-in version routing engine. When vendors upgrade their Redfish versions or when field naming changes, the system automatically maps the old and new fields and performs compatibility rollback, ensuring continuous operation of upper-layer applications with "zero modifications."

[0045] The protocol compatibility module also includes a log output module. Through a centralized token gateway, it consolidates various vendors' proprietary authentication protocols into a single OAuth2 or bidirectional TLS channel, outputting all operation logs in a unified audit format. The centralized token gateway consolidates various vendors' proprietary authentication protocols (Basic, Session, Token, X-Auth, etc.) into a single OAuth2 / bidirectional TLS channel; all operation logs are output in a unified audit format, meeting compliance requirements for information security standards and financial institutions.

[0046] This embodiment constructs a sustainable and evolving open ecosystem, enabling any third-party developer to quickly output scenario-based plugins based on this platform, forming a win-win three-layer pattern of "platform-plugin-application".

[0047] Compared to existing single-type out-of-band server management systems, this embodiment represents a significant improvement across all dimensions. At the server access level, existing out-of-band server management systems require the separate development of adaptation scripts or plugins for each new brand / model server, necessitating weekly or monthly manual maintenance. In contrast, this embodiment, through the server monitoring module's self-discovery mechanism and Capability Manifest, achieves "plug and play" functionality within minutes, reducing labor costs by over 70%.

[0048] At the server operation and maintenance interaction level, existing out-of-band server management systems require multiple CLI / Web interfaces, login addresses, and account systems for servers of various brands and models, necessitating the use of multiple sets of different communication and interaction terminology, which is prone to errors. This embodiment, however, unifies REST / JSON semantics through a semantic abstraction module, allowing a single portal / script to operate servers from vendors such as Dell, HPE, Lenovo, and Inspur, enabling operation of servers from all brands.

[0049] At the server upgrade level, existing out-of-band management systems can cause scripts to malfunction when vendors upgrade Redfish versions or change fields, requiring emergency hotfixes. This embodiment, however, incorporates version routing and field mapping. When vendors upgrade Redfish versions or cause breaking changes in field naming, the system automatically completes the mapping between old and new fields and rolls back to compatibility, ensuring continuous operation of upper-layer applications with "zero modifications" and achieving 100% business compatibility.

[0050] At the extension script level, existing out-of-band server management systems often have proprietary, closed SDKs, requiring reverse engineering or waiting for vendor roadmaps for secondary development. This embodiment, however, opens up a Scriptable Extension Slot, supporting hot-plugging of Python / Go / Lua scripts, allowing the ecosystem to grow organically.

[0051] At the data auditing level, existing out-of-band server management systems face difficulties in compliance auditing due to the presence of servers from multiple vendors and inconsistent credentials, protocols, and audit formats. This embodiment, however, features unified authentication, unified audit logs, and a unified national cryptographic / encrypted channel, meeting the requirements for information security level protection and financial-grade compliance.

[0052] In this embodiment, the software is released in three forms: SDK, CLI, and container image. Each file is less than 5 MB and can be embedded in Ansible, Terraform, and Kubernetes Operator. Offline dependency packages can also be provided, allowing deployment even in data center environments without external network access.

Claims

1. A unified semantic abstraction based out-of-band control system for heterogeneous servers, comprising: This includes a protocol compatibility module, which has a semantic abstraction module that converts Redfish protocol requests from servers of different vendors into a unified format and sends them to the server control center. The server control center issues Redfish request instructions to the protocol compatibility module, which then uses the semantic abstraction module to convert them into Redfish protocol requests for specific servers and sends them to those servers.

2. The unified semantic abstraction based out-of-band control system of heterogeneous servers as claimed in claim 1, wherein, The protocol compatibility adapter also includes a server monitoring module, which continuously monitors the server's capability description file and detects whether any new servers have been added.

3. The out-of-band control system for heterogeneous servers based on unified semantic abstraction according to claim 1, characterized in that, The protocol compatibility device has a script extension interface. The extended logic scripts accessed through the script extension interface are isolated from the main code sandbox, so that the overall stability of the system is not affected during upgrades or rollbacks.

4. The out-of-band control system for heterogeneous servers based on unified semantic abstraction according to claim 1, characterized in that, The semantic abstraction module automatically maps the "path-parameter-authentication-error code" quadruples of Redfish interfaces from different vendors into unified atomic operation primitives through deep reverse modeling and semantic mapping.

5. The out-of-band control system for heterogeneous servers based on unified semantic abstraction according to claim 1 or 4, characterized in that, The semantic abstraction module has a bidirectional mapping table for unified atomic operation primitives. When the server vendor upgrades the Redfish version, causing changes to fields or paths, the system uses the bidirectional mapping table to complete the conversion between the old and new fields in real time, and is backward compatible.

6. The unified semantic abstraction based out-of-band control system of heterogeneous servers according to claim 1 or 4, c h a r a c t e r i z e d i n that, The semantic abstraction module uses a two-layer description of JSON Schema and semantic tags to normalize the heterogeneous data returned by various vendors into a standardized business model in real time and send it to the server control center. When communicating with the server control center, the semantic abstraction module exposes only a single data format and retains the original field traceability within the semantic abstraction module.

7. The unified semantic abstraction based out-of-band control system of heterogeneous servers as claimed in claim 1 wherein, When communicating with the semantic abstraction module within the server control center, all out-of-band server control operations can be completed using only a single function signature.

8. The unified semantic abstraction based out-of-band control system of heterogeneous servers as claimed in claim 1 wherein, The protocol compatibility module also includes a log output module that uses a centralized token gateway to converge various vendors' proprietary authentication protocols into a single OAuth2 or bidirectional TLS channel, and outputs all operation logs in a unified audit format.

9. The unified semantic abstraction based out-of-band control system of heterogeneous servers as claimed in claim 2, wherein, When the server monitoring module detects a new server accessing the network, it reads the server's capability description file and compares it with the local capability description file to identify its Redfish version and feature subset, and automatically loads the corresponding adaptation plugin.

10. The unified semantic abstraction based out-of-band control system of heterogeneous servers as claimed in claim 5 wherein, When a server vendor upgrades its Redfish version, the bidirectional mapping table uses an incremental distribution strategy, which does not affect the interaction between the server control center and servers from other vendors, ensuring the continuous operation of upper-layer applications.

Images