Interface adaptation method and apparatus, and communication device and storage medium
By generating function trees and calculating interface feature likelihood, and automatically adapting to the Redfish interface of different server models, the compatibility problem of server management software for non-standardized Redfish interfaces is solved, and management efficiency is improved.
Patent Information
- Application Number
- PCT/CN2023/139263
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-09
- Filing Date
- 2023-12-15
- Publication Date
- 2024-11-14
AI Technical Summary
The Redfish interface configuration provided by servers produced by different server manufacturers is not standardized, making it difficult for server management software to quickly be compatible and adapt, increasing management complexity and workload.
By generating a function tree, scanning the server Redfish interface, calculating the interface feature likelihood, generating a backup interface, and determining the actual interface when the interface return value matches to the preset value, automatically adapting to the server interfaces of different models is achieved.
It realizes automatic adaptation of server interfaces for different manufacturers and different models, improving the compatibility of the server management platform and user management efficiency.
Smart Images

Figure CN2023139263_14112024_PF_FP_ABST
Abstract
Description
Interface adaptation method, device, communication equipment and storage medium
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on May 9, 2023, with application number 202310515300.2 and application name “Interface Adaptation Method, Device, Communication Equipment and Storage Medium”, all contents of which are incorporated by reference into this application. Technical Field
[0003] The present application relates to the field of server management technology, and in particular to an interface adaptation method, apparatus, communication equipment, and non-volatile readable storage medium. Background Art
[0004] For server management, the Redfish protocol based on the HyperText Transfer Protocol (HTTP) is a commonly used protocol for managing servers.
[0005] However, in actual use, the Redfish interfaces provided by servers produced by different server manufacturers are not standardized. For users, when purchasing different models of servers from different manufacturers or different models of servers from the same manufacturer, the Redfish interface configurations corresponding to different models may not be the same standard. It is more complicated for server management software to manage all servers.
[0006] Therefore, in order to solve the above problems in the relevant technology, users need to analyze how to use the interface by reading the interface documents corresponding to different models. However, this method will result in the inability to match the actual server interface when the interface documents are not standardized, and the number is too large, which causes a lot of workload for the compatibility adaptation of the server management software, and it is impossible to quickly obtain the actual server interface of the function required by the user.
[0007] Summary of the Invention
[0008] The purpose of the embodiments of the present application is to provide an interface adaptation method, apparatus, communication device, and non-volatile readable storage medium to solve the technical problem in the prior art of being unable to quickly obtain the actual server interface of the function required by the user. The specific technical solution is as follows:
[0009] In a first aspect of the present application, an interface adaptation method is provided, which is applied to a server management platform. The method includes:
[0010] Generate a function tree according to the target model, wherein the function tree includes standard Redfish interfaces corresponding to preset functions in the target model;
[0011] Scan the server Redfish interface corresponding to the target model and generate an interface tree based on the interface characteristics of the server Redfish interface;
[0012] According to the standard Redfish interface corresponding to the leaf node in the interface tree, the likelihood is compared with all interfaces in the interface tree to generate a preliminary interface;
[0013] When it is detected that the preliminary interface is in a calling state and the interface return value of the preliminary interface has a matching degree greater than a preset value in the preset model library, the actual interface adapted by the target model is determined to be the preliminary interface.
[0014] In some embodiments, before the step of generating a function tree according to the target model, the method includes:
[0015] A first initialization process is performed on a preset model library, where the preset model library includes a standard Redfish interface and characteristic values corresponding to return values of the Redfish interface of the adapted model.
[0016] In some embodiments, the interface tree includes a root node which is a standard Redfish interface, child nodes which are resource interfaces, sub-resource interfaces corresponding to the resource interfaces, and at least one of interfaces corresponding to the sub-resource interface after data parsing, and leaf nodes which are the actual path and parameter format of the Redfish interface.
[0017] In some embodiments, the resource interface includes at least one of the following:
[0018] System resources, chassis resources, management resources, session service resources, account service resources, upgrade service resources, and event subscription service resources.
[0019] In some embodiments, the function tree includes a root node which is the target model, child nodes which are preset function types and basic functions corresponding to the preset function types, and leaf nodes which are standard Redfish interfaces corresponding to the basic functions.
[0020] In some embodiments, after the step of generating a function tree according to the target model, the method includes:
[0021] Determine whether the target model exists in the preset model library;
[0022] If the target model exists in the preset model library, the actual interface list adapted to the target model is directly obtained.
[0023] If the target model does not exist in the preset model library, it is determined whether there is a second function tree similar to the function tree corresponding to the target model in the preset model library.
[0024] In some embodiments, after determining whether there is a second function tree similar to the function tree corresponding to the target model in the preset model library, the method includes:
[0025] If there is a second function tree similar to the function tree corresponding to the target model in the preset model library, the second function tree is used as the function tree corresponding to the target model;
[0026] If there is no second function tree similar to the function tree corresponding to the target model in the preset model library, a second initialization process is performed on the function tree corresponding to the target model according to a user instruction.
[0027] In some embodiments, performing the second initialization process on the function tree corresponding to the target model includes:
[0028] According to the interface characteristics of the standard Redfish interface, the total number of matching feature values corresponding to the standard Redfish interface in the preset model library is initialized.
[0029] In some embodiments, scanning the server Redfish interface corresponding to the target model and generating an interface tree according to interface features of the server Redfish interface includes:
[0030] According to the preset program settings, the server Redfish interface corresponding to the target model is automatically scanned, and the interface tree is generated from the root node level. The interface tree includes the actual path and parameter format of the server Redfish interface.
[0031] In some embodiments, the leaf nodes in the interface tree include the actual path of the server Redfish interface. Based on the likelihood comparison of the standard Redfish interface corresponding to the leaf node in the interface tree with all interfaces in the interface tree, generating the preliminary interface includes:
[0032] Calculate the likelihood between the actual path of each server's Redfish interface and the interface path corresponding to the standard Redfish interface;
[0033] The backup interface is determined based on the likelihood.
[0034] In some embodiments, calculating the likelihood between the actual path of each server Redfish interface and the interface path corresponding to the standard Redfish interface includes:
[0035] Cut the interface path corresponding to each standard Redfish interface to generate keyword information;
[0036] The feature value is extracted according to the keyword information, and the likelihood is generated according to the weight corresponding to the feature value and the matching degree between the feature value and the actual path of the server Redfish interface.
[0037] In some embodiments, the likelihood is obtained by the following formula:
[0038] Where f(x) is the likelihood, p1, p2, and pn are the weights corresponding to each eigenvalue, x1, x2, and xn are the matching degrees between each eigenvalue and the actual path of the server Redfish interface in the interface tree, y1, y2, and yn are the maximum matching degrees between each eigenvalue and the actual path of the server Redfish interface in the interface tree, and n is a positive integer greater than 0 and less than or equal to the number of keyword information.
[0039] In some embodiments, when it is detected that the preliminary interface is in a calling state and the interface return value of the preliminary interface has a matching degree greater than a preset value in the preset model library, determining that the actual interface adapted to the target model is the preliminary interface includes:
[0040] Call the preparation interface and obtain the interface return value of the preparation interface;
[0041] Extract the feature items of the preliminary interface according to the interface return value, match the feature items of the preliminary interface with the feature library corresponding to the preliminary interface in the preset model library, and generate the matching degree corresponding to the preliminary interface;
[0042] When it is detected that the matching degree is greater than a preset value, the actual interface adapted by the target model is determined to be the preliminary interface.
[0043] In some embodiments, after detecting that the preliminary interface is in a calling state and the interface return value of the preliminary interface has a matching degree greater than a preset value in the preset model library, determining that the actual interface adapted to the target model is the preliminary interface, the method includes:
[0044] Connect the actual interface;
[0045] If the actual interface is in normal working condition, the actual interface is adapted to the target model;
[0046] If the actual interface is in an abnormal working state, the second standby interface is obtained and called.
[0047] In some embodiments, after the step of adapting the actual interface to the target model if the actual interface is in a normal working state, the method includes:
[0048] Extract features from the server interface tree corresponding to the target model, and fill the extracted features into the preset model library.
[0049] In some embodiments, after the step of adapting the actual interface to the target model if the actual interface is in a normal working state, the method includes:
[0050] Extract the features corresponding to the interface return value of the actual interface, and fill the features corresponding to the interface return value of the actual interface into the preset model library.
[0051] In some embodiments, scanning the server Redfish interface corresponding to the target model and generating an interface tree according to interface features of the server Redfish interface includes:
[0052] Determine the server based on the target model;
[0053] Scan the server's Redfish interface and generate an interface tree based on the interface characteristics of the server's Redfish interface.
[0054] In another aspect of the present application, an interface adapter device is provided for use on a server management platform. The device includes:
[0055] A first generating module is configured to generate a function tree according to a target model, wherein the function tree includes standard Redfish interfaces corresponding to preset functions in the target model;
[0056] The second generation module is used to scan the server Redfish interface corresponding to the target model and generate an interface tree according to the interface characteristics of the server Redfish interface;
[0057] The third generation module is used to compare the likelihood of the standard Redfish interface corresponding to the leaf node in the interface tree with all the interfaces in the interface tree to generate a preliminary interface;
[0058] The determination module is used to determine that the actual interface adapted by the target model is the preparation interface when it is detected that the preparation interface is in a calling state and the interface return value of the preparation interface has a matching degree greater than a preset value in the preset model library.
[0059] In another aspect of the present application, an electronic device is provided, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus;
[0060] Memory for storing computer programs;
[0061] The processor is configured to implement any of the above interface adaptation methods when executing a program stored in the memory.
[0062] In another aspect of the present application, a computer non-volatile readable storage medium is provided, in which instructions are stored. When the computer non-volatile readable storage medium is run on a computer, the computer executes any of the above-mentioned interface adaptation methods.
[0063] In another aspect of the implementation of the present application, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute any of the above-mentioned interface adaptation methods.
[0064] The interface adaptation method provided by the embodiment of the present application generates a function tree according to the target model, wherein the function tree includes the standard Redfish interface corresponding to the preset function in the target model; scans the server Redfish interface corresponding to the target model, and generates an interface tree according to the interface characteristics of the server Redfish interface; compares the likelihood of the standard Redfish interface corresponding to the leaf node in the interface tree with all the interfaces in the interface tree to generate a preliminary interface; when it is detected that the preliminary interface is in a calling state and the interface return value of the preliminary interface has a matching degree greater than a preset value in the preset model library, it is determined that the actual interface adapted to the target model is the preliminary interface. The interface adaptation method provided by the embodiment of the present application is applied to a server management platform equipped with server management software, and generates a function tree according to each model, wherein the function tree includes the standard Redfish interface required for function use. The interface is automatically scanned for the server Redfish interface corresponding to the target model and the result can be persisted in a tree structure through analysis of the Redfish interface characteristics to generate an interface tree. Since the real interface (server Redfish interface) and the standard interface (standard Redfish interface using the Redfish protocol) of each model are not necessarily consistent, it is necessary to calculate the likelihood between the standard Redfish interface in the function tree and the leaf nodes in each interface tree, determine the prepared interface by taking the likelihood, and call the prepared interface to determine the actual interface adapted to the target model. The interface adaptation method provided in the embodiment of the present application can realize automatic adaptation of server interfaces of different models, and through the persistence of the tree structure, the server management platform can be quickly compatible with servers of different models from different manufacturers, thereby improving the user's management efficiency of the server. BRIEF DESCRIPTION OF THE DRAWINGS
[0065] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art.
[0066] FIG1 shows a flowchart of the steps of the interface adaptation method provided in an embodiment of the present application;
[0067] FIG2 shows a second flow chart of the steps of the interface adaptation method provided in an embodiment of the present application;
[0068] FIG3 shows a flowchart of the third step of the interface adaptation method provided in an embodiment of the present application;
[0069] FIG4 shows a flowchart of the fourth step of the interface adaptation method provided in an embodiment of the present application;
[0070] FIG5 shows a flowchart of the fifth step of the interface adaptation method provided in an embodiment of the present application;
[0071] FIG6 shows an interface adapter device provided in an embodiment of the present application;
[0072] FIG7 shows a structural block diagram of a communication device provided in an embodiment of the present application;
[0073] FIG8 shows a schematic diagram of a function tree provided in an embodiment of the present application. DETAILED DESCRIPTION
[0074] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.
[0075] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, each embodiment of the present application will be described in detail below with reference to the accompanying drawings. However, it will be understood by those skilled in the art that in each embodiment of the present application, many technical details are proposed in order to enable the reader to better understand the present application. However, even without these technical details and various changes and modifications based on the following embodiments, the technical solutions claimed in the present application can be implemented. The division of the following embodiments is for convenience of description and should not constitute any limitation on the specific implementation of the present application. The various embodiments can be combined with each other and referenced to each other under the premise of no contradiction.
[0076] 1 , a flowchart of the first step of the interface adaptation method provided in an embodiment of the present application is shown. The method may include:
[0077] Step 101: Generate a function tree according to a target model, wherein the function tree includes standard Redfish interfaces corresponding to preset functions in the target model.
[0078] It should be noted that in the embodiments of the present application, it is applied to a server management platform, which can be equipped with server management software. Users can view and call server-related interfaces through the server management platform. It is mainly used for the server management software to quickly identify the path and parameters corresponding to the Redfish interface. Among them, Redfish can be understood as a server management function developed and provided by the server manufacturer.
[0079] In an embodiment of the present application, through the server management software installed in the server management platform, a server management software function tree can be constructed with the model as the root node, and this function tree can be persisted. Specifically, as shown in Figure 8, Figure 8 shows a function tree schematic diagram provided by an embodiment of the present application. The function tree includes a root node as the target model, child nodes as preset function types and basic functions corresponding to the preset function types, and leaf nodes as standard Redfish interfaces corresponding to the basic functions.
[0080] Specifically, the overall structure of the function tree may include: the root node is the machine model, the lower layer is the major categories of various functions, the major categories are basic function items such as user management, Network Time Protocol (NTP) management, Baseboard Management Controller (BMC) upgrade, Basic Input Output System (BIOS) upgrade, system installation, etc., and the bottom layer is the Redfish interface required for the implementation of basic functions.
[0081] Specifically, different manufacturers and different types of servers correspond to different models, so the Redfish interface in the server corresponding to the model is different. Therefore, the model is used as the root node of the function tree, and the child nodes can be preset function types, such as configuration functions, operation functions, upgrade functions, etc. Furthermore, one of the preset function types can be further subdivided, that is, the basic functions corresponding to the preset function type, such as raid acquisition, system installation, and hard disk erasure. Furthermore, for example, for system installation, the mount image interface, set read-only optical disk storage (Compact Disc Read-Only Memory, CD-ROM) startup interface, restart interface, read system log interface, and uninstall interface provided by Redfish are required. Therefore, the standard Redfish interface under the Redfish protocol is used as the initialization interface. Because the actual interface of each model may not be consistent with the standard Redfish interface, the interface needs to be calibrated to determine the actual interface required by the target model when executing a preset function.
[0082] Step 102: Scan the server Redfish interface corresponding to the target model, and generate an interface tree according to the interface characteristics of the server Redfish interface.
[0083] In an embodiment of the present application, the server Redfish interface of the corresponding model can be scanned based on the server management software, a tree structure of the server Redfish interface can be generated, and the data can be persisted.
[0084] Furthermore, the interface tree includes a root node which is a standard Redfish interface, child nodes which are resource interfaces, sub-resource interfaces corresponding to resource interfaces, and at least one of interfaces corresponding to sub-resource interface data after parsing, and leaf nodes which are actual paths and parameter formats of Redfish interfaces.
[0085] The resource interface includes at least one of the following: system resources, chassis resources, management resources, session service resources, account service resources, upgrade service resources, and event subscription service resources.
[0086] Specifically, for setting the interface tree, the first level is the root node, which can be represented as / Redfish / v1. The second level can be seven resource interfaces, such as system resources, chassis resources, management resources, session service resources, account service resources, upgrade service resources and event subscription service resources. For one of the system resources, it can be represented as / Redfish / v1 / Systems. The third level is the sub-resource interface under one of the resource interfaces. For example, one of the system resource sub-interfaces under the system resource can be represented as / Redfish / v1 / Systems / 1. The fourth level is obtained by continuing to parse the data returned by the fourth-level interface to obtain the main categories of interfaces of the fourth level, such as Action, Simple Taking the Action interface as an example, by continuously calling the Action interface, you can get the Action sub-interface, which is the fifth level. By analyzing the data returned by the fifth-level interface, you can get some of the most basic operation paths and parameters. For example, the path for remote service power on and off is / Redfish / v1 / Systems / 1 / Actions / ComputerSystem.Reset, and the corresponding parameters are "On", "ForceOff", "GracefulShutdown", "ForceRestart", "ForcePowerCycle", and so on. By cyclically calling all Redfish interfaces, you can generate a tree-structured data.
[0087] It should be noted that for the interface tree, the leaf nodes are the actual paths and parameter formats of the Redfish interface, that is, the most basic operation paths and parameters, such as the path for remote service power on and off.
[0088] Furthermore, scanning the server Redfish interface corresponding to the target model and generating an interface tree according to the interface characteristics of the server Redfish interface include:
[0089] According to the preset program settings, the server Redfish interface corresponding to the target model is automatically scanned, and the interface tree is generated from the root node level. The interface tree includes the actual path and parameter format of the server Redfish interface.
[0090] Specifically, the server Redfish interface corresponding to the target model is automatically scanned according to a preset program, starting from the root node (Redfish / v1), traversing the hierarchy, and finally generating a Redfish interface tree, wherein the interface tree includes the actual path and parameter format of the server Redfish interface.
[0091] Step 103: perform likelihood comparison between the standard Redfish interface corresponding to the leaf node in the interface tree and all interfaces in the interface tree to generate a preliminary interface.
[0092] It should be noted that in the embodiment of the present application, the standard Redfish interface in the function tree is traversed, and the likelihood of each leaf node in the interface tree is calculated, where each leaf node in the interface tree is the actual path and parameter format of the server Redfish interface. The three interfaces with the largest likelihood can be used as preliminary interfaces.
[0093] It should be noted that the prepared interface is the Redfish interface in the server corresponding to the actual target model, not the standard Redfish interface during initialization.
[0094] Step 104 : when it is detected that the preliminary interface is in a calling state and the matching degree of the interface return value of the preliminary interface in the preset model library is greater than a preset value, the actual interface adapted to the target model is determined to be the preliminary interface.
[0095] In an embodiment of the present application, each preliminary interface can be actually called, and feature items can be extracted based on the interface return value returned by each preliminary interface, so as to determine the matching value of each preliminary interface in the preset model library, find the preliminary interface with the largest matching value or one greater than the preset value, and use the preliminary interface as the final actual interface.
[0096] Specifically, actually call the prepared interface, obtain the interface return value, extract the feature items of the interface return value, match the feature items with the feature library of the interface in the model library, and the number of features required to match each interface, calculate the matching degree of the three interfaces with the maximum likelihood in the model library, and take the one with the maximum matching degree as the actual interface.
[0097] Furthermore, for the preset model library, before step 101, a first initialization process needs to be performed on the preset model library. The preset model library includes a standard Redfish interface and characteristic values corresponding to the return values of the Redfish interface of the adapted model.
[0098] It should be noted that the initialization process is to pre-load some parameters and feature values into the preset model library. The preset model library is indexed by the Redfish interface used by the service management platform to provide external functions, and collects the feature values of the standard Redfish interface and the server Redfish interface return value of the adapted model as the basic data of the preset model library. The establishment of the preset model library is a continuous process. Each time any model is automatically adapted, the feature extraction of the server Redfish interface (actual interface) used by the service management platform corresponding to the model is performed, and after the extraction is completed, it is filled into the preset model library.
[0099] The interface adaptation method provided by the embodiment of the present application generates a function tree according to the target model, wherein the function tree includes the standard Redfish interface corresponding to the preset function in the target model; scans the server Redfish interface corresponding to the target model, and generates an interface tree according to the interface characteristics of the server Redfish interface; compares the likelihood of the standard Redfish interface corresponding to the leaf node in the interface tree with all the interfaces in the interface tree to generate a preliminary interface; when it is detected that the preliminary interface is in a calling state and the interface return value of the preliminary interface has a matching degree greater than a preset value in the preset model library, it is determined that the actual interface adapted to the target model is the preliminary interface. The interface adaptation method provided by the embodiment of the present application is applied to a server management platform equipped with server management software, and generates a function tree according to each model, wherein the function tree includes the standard Redfish interface required for function use. The interface is automatically scanned for the server Redfish interface corresponding to the target model and the result can be persisted in a tree structure through analysis of the Redfish interface characteristics to generate an interface tree. Since the real interface (server Redfish interface) and the standard interface (standard Redfish interface using the Redfish protocol) of each model are not necessarily consistent, it is necessary to calculate the likelihood between the standard Redfish interface in the function tree and the leaf nodes in each interface tree, determine the prepared interface by taking the likelihood, and call the prepared interface to determine the actual interface adapted to the target model. The interface adaptation method provided in the embodiment of the present application can realize automatic adaptation of server interfaces of different models, and through the persistence of the tree structure, the server management platform can be quickly compatible with servers of different models from different manufacturers, thereby improving the user's management efficiency of the server.
[0100] 2 , a second flowchart of the interface adaptation method provided in an embodiment of the present application is shown. The method may include:
[0101] Step 201: Generate a function tree according to a target model, wherein the function tree includes standard Redfish interfaces corresponding to preset functions in the target model.
[0102] It should be noted that the above step 201 is described with reference to the previous discussion and will not be repeated here.
[0103] Step 202, determining whether the target model exists in the preset model library;
[0104] Step 203: If the target model exists in the preset model library, directly obtain the actual interface list adapted to the target model.
[0105] Step 204 : If the target model does not exist in the preset model library, it is determined whether there is a second function tree in the preset model library that is similar to the function tree corresponding to the target model.
[0106] Step 205: If there is a second function tree similar to the function tree corresponding to the target model in the preset model library, the second function tree is used as the function tree corresponding to the target model;
[0107] Step 206 : If there is no second function tree similar to the function tree corresponding to the target model in the preset model library, a second initialization process is performed on the function tree corresponding to the target model according to a user instruction.
[0108] In the above steps 202-206, the server management software can initialize the function tree for the target model. If the model has been initialized by the server management platform, no processing is required and the actual interface of the adapted model is directly used without executing steps 207-209.
[0109] If this model has not been initialized, determine whether there are similar models to this model. If so, copy the function tree of the similar model and manually correct the different items. If not, build a function tree for this model and initialize it, manually correct the different items, and then execute step 207.
[0110] Furthermore, performing a second initialization process on the function tree corresponding to the target model includes: initializing the total number of matching feature values corresponding to the standard Redfish interface in the preset model library according to the interface features of the standard Redfish interface.
[0111] Step 207: Scan the server Redfish interface corresponding to the target model, and generate an interface tree according to the interface characteristics of the server Redfish interface.
[0112] Step 208: perform likelihood comparison between the standard Redfish interface corresponding to the leaf node in the interface tree and all interfaces in the interface tree to generate a preliminary interface.
[0113] Step 209 : When it is detected that the preliminary interface is in a calling state and the matching degree of the interface return value of the preliminary interface in the preset model library is greater than a preset value, the actual interface adapted by the target model is determined to be the preliminary interface.
[0114] It should be noted that the above steps 207-209 refer to the previous discussion and will not be repeated here.
[0115] The interface adaptation method provided in the embodiment of the present application is applied to a server management platform equipped with server management software. A function tree is generated according to each model. The function tree contains the standard Redfish interface required for function use, and by analyzing the characteristics of the Redfish interface, the server Redfish interface corresponding to the target model can be automatically scanned and the results can be persisted in a tree structure to generate an interface tree. Since the real interface (server Redfish interface) and the standard interface (standard Redfish interface using the Redfish protocol) of each model are not necessarily consistent, it is necessary to calculate the likelihood between the standard Redfish interface in the function tree and the leaf node in each interface tree, determine the preliminary interface by taking the likelihood, and call the preliminary interface to determine the actual interface adapted to the target model. The interface adaptation method provided in the embodiment of the present application can realize automatic adaptation of server interfaces of different models, and through the persistence of the tree structure, the server management platform can be quickly compatible with servers of different models from different manufacturers, thereby improving the user's management efficiency of the server.
[0116] 3 , a flowchart of the third step of the interface adaptation method provided in an embodiment of the present application is shown. The method may include:
[0117] Step 301: Generate a function tree according to a target model, wherein the function tree includes standard Redfish interfaces corresponding to preset functions in the target model.
[0118] Step 302: Scan the server Redfish interface corresponding to the target model, and generate an interface tree according to the interface characteristics of the server Redfish interface.
[0119] Furthermore, the interface tree includes a root node which is a standard Redfish interface, child nodes which are resource interfaces, sub-resource interfaces corresponding to resource interfaces, and at least one of interfaces corresponding to sub-resource interface data after parsing, and leaf nodes which are actual paths and parameter formats of Redfish interfaces.
[0120] The resource interface includes at least one of the following: system resources, chassis resources, management resources, session service resources, account service resources, upgrade service resources, and event subscription service resources.
[0121] It should be noted that the above steps 301-302 refer to the previous discussion and will not be repeated here.
[0122] Step 303: The leaf nodes in the interface tree include the actual path of the server Redfish interface, and the likelihood between the actual path of each server Redfish interface and the interface path corresponding to the standard Redfish interface is calculated;
[0123] Furthermore, calculating the likelihood between the actual path of each server Redfish interface and the interface path corresponding to the standard Redfish interface includes: cutting the interface path corresponding to each standard Redfish interface to generate keyword information; extracting feature values according to the keyword information, and generating the likelihood according to the weight corresponding to the feature value and the matching degree between the feature value and the actual path of the server Redfish interface.
[0124] Furthermore, the likelihood is obtained by the following formula:
[0125] In the above formula 1, f(x) is the likelihood, p1, p2, and pn are the weights corresponding to each eigenvalue, x1, x2, and xn are the matching degrees of each eigenvalue and the actual path of the server Redfish interface in the interface tree, y1, y2, and yn are the maximum matching degrees of each eigenvalue and the actual path of the server Redfish interface in the interface tree, and n is a positive integer greater than 0 and less than or equal to the number of keyword information.
[0126] It should be noted that in the above step 303 of the embodiment of the present application, in order to further determine the actual interface adapted by the server, it is necessary to calculate the likelihood of the standard Redfish interface in the function tree and the server Redfish interface in the interface tree, wherein the path format corresponding to the standard Redfish interface can be expressed as Redfish / v1 / Managers / 1 / DiagnosticService / WorkRecord / Actions / WorkRecord.addRecord, therefore, the standard Redfish interface is cut into Managers, 1, DiagnosticServiice, etc., wherein Managers, 1, and DiagnosticService are all keyword information, and the leaf nodes of the interface tree are traversed to obtain the likelihood between each server Redfish interface and the standard rdfish interface in the function tree (preset standard rdfish interface path).
[0127] Specifically, the likelihood is calculated by referring to the above formula 1, where the matching degree can be understood as the length of the feature value. For example, Managers has a total of 8 letters. If it matches m, a, and n, the ratio is 3 to 8, and the matching degree is obtained. In addition, the maximum value of f(x) is 1.
[0128] Step 304: Determine a preliminary interface based on the likelihood.
[0129] After the likelihood is calculated, the three server Redfish interfaces with the largest likelihood can be used as preliminary interfaces. It should be noted that in the embodiment of the present application, the number of likelihoods is not limited and can be determined according to actual conditions.
[0130] Step 305 : When it is detected that the preliminary interface is in a calling state and the matching degree of the interface return value of the preliminary interface in the preset model library is greater than a preset value, the actual interface adapted by the target model is determined to be the preliminary interface.
[0131] Furthermore, step 305 may include: calling the preliminary interface to obtain the interface return value of the preliminary interface; extracting the preliminary interface feature items based on the interface return value, matching the preliminary interface feature items with the feature library corresponding to the preliminary interface in the preset model library, and generating a matching degree corresponding to the preliminary interface; when it is detected that the matching degree is greater than the preset value, determining that the actual interface adapted to the target model is the preliminary interface.
[0132] It should be noted that in the above step 305, after obtaining the three interfaces with the highest likelihood, the corresponding server Redfish interface is used as the preliminary interface, and the preliminary interface is actually called. After the call, the interface return value corresponding to each interface can be obtained, and the feature items are extracted from the interface return value. The feature items are matched with the feature library corresponding to the interface in the preset model library, as well as the number of features required to match each interface. The matching degree of the three interfaces with the highest likelihood in the preset model library is calculated, and the interface with the highest matching degree is used as the actual interface.
[0133] The interface adaptation method provided in the embodiment of the present application is applied to a server management platform equipped with server management software. A function tree is generated according to each model. The function tree contains the standard Redfish interface required for function use, and by analyzing the characteristics of the Redfish interface, the server Redfish interface corresponding to the target model can be automatically scanned and the results can be persisted in a tree structure to generate an interface tree. Since the real interface (server Redfish interface) and the standard interface (standard Redfish interface using the Redfish protocol) of each model are not necessarily consistent, it is necessary to calculate the likelihood between the standard Redfish interface in the function tree and the leaf node in each interface tree, determine the preliminary interface by taking the likelihood, and call the preliminary interface to determine the actual interface adapted to the target model. The interface adaptation method provided in the embodiment of the present application can realize automatic adaptation of server interfaces of different models, and through the persistence of the tree structure, the server management platform can be quickly compatible with servers of different models from different manufacturers, thereby improving the user's management efficiency of the server.
[0134] 4 , a fourth flowchart of the interface adaptation method according to an embodiment of the present application is shown. The method may include:
[0135] Step 401: Generate a function tree according to the target model, wherein the function tree includes standard Redfish interfaces corresponding to preset functions in the target model.
[0136] Step 402: Scan the server Redfish interface corresponding to the target model, and generate an interface tree according to the interface characteristics of the server Redfish interface.
[0137] Furthermore, the interface tree includes a root node which is a standard Redfish interface, child nodes which are resource interfaces, sub-resource interfaces corresponding to resource interfaces, and at least one of interfaces corresponding to sub-resource interface data after parsing, and leaf nodes which are actual paths and parameter formats of Redfish interfaces.
[0138] The resource interface includes at least one of the following: system resources, chassis resources, management resources, session service resources, account service resources, upgrade service resources, and event subscription service resources.
[0139] Step 403: perform likelihood comparison between the standard Redfish interface corresponding to the leaf node in the interface tree and all interfaces in the interface tree to generate a preliminary interface.
[0140] It should be noted that the above steps 401-403 refer to the previous discussion and will not be repeated here.
[0141] Step 404 : when it is detected that the preliminary interface is in a calling state and the matching degree of the interface return value of the preliminary interface in the preset model library is greater than a preset value, the actual interface adapted by the target model is determined to be the preliminary interface.
[0142] Step 405, connecting to the actual interface;
[0143] Step 406: If the actual interface is in a normal working state, the actual interface is adapted to the target model.
[0144] It should be noted that in the above steps 404-405, by actually applying the determined actual interface, it is possible to calibrate again whether the interface is adapted correctly. If not, return to step 403 and adapt the other two of the three likelihoods until the correct interface is found. Or if none of the three interfaces work, it means that the current function has no supported interface in the target model, that is, the target model does not support the current function.
[0145] Furthermore, in one embodiment, after step 406, that is, after the step of adapting the actual interface to the target model if the actual interface is in normal working condition, the method includes: extracting features from the interface tree of the server corresponding to the target model, and filling the extracted features into the preset model library.
[0146] It should be noted that if the actual interface meets expectations during actual operation, the interface tree corresponding to the target model of this adaptation can be feature extracted and the features can be filled into the preset model library.
[0147] In another embodiment, after step 406, if the actual interface is in a normal working state, then after the step of adapting the actual interface to the target model, the method includes: extracting the features corresponding to the interface return value of the actual interface, and filling the features corresponding to the interface return value of the actual interface into the preset model library.
[0148] In addition, if the actual interface is determined to be correctly adapted through actual application of the determined actual interface, the correct interface call is used to obtain the interface return value, and the features of the interface return value are extracted to supplement the feature library in the preset model library of the interface.
[0149] Step 407: If the actual interface is in an abnormal working state, obtain a second standby interface for calling.
[0150] It should be noted that in the above step 407, by actually applying the determined actual interface, it is possible to calibrate again whether the interface is adapted correctly. If not, return to step 403 and adapt the other two of the three likelihoods until the correct interface is found. If all three interfaces fail, it means that the current function does not have a supported interface in the target model, that is, the target model does not support the current function.
[0151] The interface adaptation method provided in the embodiment of the present application is applied to a server management platform equipped with server management software. A function tree is generated according to each model. The function tree includes the standard Redfish interface required for function use, and by analyzing the characteristics of the Redfish interface, the server Redfish interface corresponding to the target model can be automatically scanned and the results can be persisted in a tree structure to generate an interface tree. Since the real interface (server Redfish interface) and the standard interface (standard Redfish interface using the Redfish protocol) of each model are not necessarily consistent, it is necessary to calculate the likelihood between the standard Redfish interface in the function tree and the leaf node in each interface tree, determine the preliminary interface by taking the likelihood, and call the preliminary interface to determine the actual interface adapted to the target model. The interface adaptation method provided in the embodiment of the present application can realize automatic adaptation of server interfaces of different models, and through the persistence of the tree structure, the server management platform can be quickly compatible with servers of different models from different manufacturers, thereby improving the user's management efficiency of the server.
[0152] 5 , a flowchart of the fifth step of the interface adaptation method provided in an embodiment of the present application is shown. The method may include:
[0153] Step 501: Generate a function tree according to a target model, wherein the function tree includes standard Redfish interfaces corresponding to preset functions in the target model.
[0154] It should be noted that the above step 501 is described with reference to the previous discussion and will not be repeated here.
[0155] Step 502: Determine the server according to the target model.
[0156] Step 503: Scan the server Redfish interface of the server, and generate an interface tree according to the interface characteristics of the server Redfish interface.
[0157] It should be noted that in the embodiment of the present application, after obtaining the target model, the specific server can be determined according to the target model, and the server management platform can connect to the Redfish interface in the server to manage and set up the server.
[0158] It should be noted that the target model can be determined based on data such as the server type or ID.
[0159] Step 504: perform likelihood comparison between the standard Redfish interface corresponding to the leaf node in the interface tree and all interfaces in the interface tree to generate a preliminary interface.
[0160] Step 505 : When it is detected that the preliminary interface is in a calling state and the interface return value of the preliminary interface has a matching degree greater than a preset value in the preset model library, the actual interface adapted to the target model is determined to be the preliminary interface.
[0161] It should be noted that the above steps 504-505 refer to the previous discussion and will not be repeated here.
[0162] The interface adaptation method provided in the embodiment of the present application is applied to a server management platform equipped with server management software. A function tree is generated according to each model. The function tree contains the standard Redfish interface required for function use, and by analyzing the characteristics of the Redfish interface, the server Redfish interface corresponding to the target model can be automatically scanned and the results can be persisted in a tree structure to generate an interface tree. Since the real interface (server Redfish interface) and the standard interface (standard Redfish interface using the Redfish protocol) of each model are not necessarily consistent, it is necessary to calculate the likelihood between the standard Redfish interface in the function tree and the leaf node in each interface tree, determine the preliminary interface by taking the likelihood, and call the preliminary interface to determine the actual interface adapted to the target model. The interface adaptation method provided in the embodiment of the present application can realize automatic adaptation of server interfaces of different models, and through the persistence of the tree structure, the server management platform can be quickly compatible with servers of different models from different manufacturers, thereby improving the user's management efficiency of the server.
[0163] 6 , which shows an interface adapter device provided in an embodiment of the present application, the device may include:
[0164] A first generating module 601 is configured to generate a function tree according to a target model, wherein the function tree includes standard Redfish interfaces corresponding to preset functions in the target model;
[0165] The second generating module 602 is used to scan the server Redfish interface corresponding to the target model and generate an interface tree according to the interface characteristics of the server Redfish interface;
[0166] The third generation module 603 is used to perform likelihood comparison between the standard Redfish interface corresponding to the leaf node in the interface tree and all the interfaces in the interface tree to generate a preliminary interface;
[0167] The determination module 604 is configured to determine that the actual interface adapted to the target model is the preparation interface when it is detected that the preparation interface is in a calling state and the interface return value of the preparation interface has a matching degree greater than a preset value in the preset model library.
[0168] The interface adapter provided by the embodiment of the present application generates a function tree according to the target model, wherein the function tree includes the standard Redfish interface corresponding to the preset function in the target model; scans the server Redfish interface corresponding to the target model, and generates an interface tree according to the interface characteristics of the server Redfish interface; compares the likelihood of the standard Redfish interface corresponding to the leaf node in the interface tree with all the interfaces in the interface tree to generate a preliminary interface; when it is detected that the preliminary interface is in a calling state and the interface return value of the preliminary interface has a matching degree greater than a preset value in the preset model library, it is determined that the actual interface adapted to the target model is the preliminary interface. The interface adapter provided by the embodiment of the present application is applied to a server management platform equipped with server management software, and generates a function tree according to each model, wherein the function tree includes the standard Redfish interface required for function use. The interface is automatically scanned for the server Redfish interface corresponding to the target model and the result can be persisted in a tree structure through analysis of the Redfish interface characteristics to generate an interface tree. Since the real interface (server Redfish interface) and the standard interface (standard Redfish interface using the Redfish protocol) of each model are not necessarily consistent, it is necessary to calculate the likelihood between the standard Redfish interface in the function tree and the leaf nodes in each interface tree, determine the prepared interface by taking the likelihood, and call the prepared interface to determine the actual interface adapted to the target model. The interface adaptation method provided in the embodiment of the present application can realize automatic adaptation of server interfaces of different models, and through the persistence of the tree structure, the server management platform can be quickly compatible with servers of different models from different manufacturers, thereby improving the user's management efficiency of the server.
[0169] The embodiment of the present application further provides an electronic device, as shown in FIG7 , including a processor 701, a communication interface 702, a memory 703, and a communication bus 704, wherein the processor 701, the communication interface 702, and the memory 703 communicate with each other via the communication bus 704.
[0170] Memory 703, for storing computer programs;
[0171] When the processor 701 is used to execute the program stored in the memory 703, it can implement the following steps:
[0172] Generate a function tree according to the target model, wherein the function tree includes standard Redfish interfaces corresponding to preset functions in the target model;
[0173] Scan the server Redfish interface corresponding to the target model and generate an interface tree based on the interface characteristics of the server Redfish interface;
[0174] According to the standard Redfish interface corresponding to the leaf node in the interface tree, the likelihood is compared with all interfaces in the interface tree to generate a preliminary interface;
[0175] When it is detected that the preliminary interface is in a calling state and the interface return value of the preliminary interface has a matching degree greater than a preset value in the preset model library, the actual interface adapted by the target model is determined to be the preliminary interface.
[0176] The communication bus mentioned in the terminal can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. This communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is used in the figure, but this does not mean that there is only one bus or only one type of bus.
[0177] The communication interface is used for communication between the above terminal and other devices.
[0178] The memory may include random access memory (RAM) or non-volatile memory, such as at least one disk storage. In some embodiments, the memory may also be at least one storage device located away from the processor.
[0179] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components.
[0180] In another embodiment provided by the present application, a computer non-volatile readable storage medium is also provided. The computer non-volatile readable storage medium stores instructions, which, when executed on a computer, enable the computer to perform the interface adaptation of any of the above embodiments.
[0181] In another embodiment provided by the present application, a computer program product including instructions is also provided, which, when executed on a computer, enables the computer to perform the interface adaptation in any one of the above embodiments.
[0182] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable devices. The computer instructions can be stored in a non-volatile computer readable storage medium, or transmitted from a non-volatile computer readable storage medium to another non-volatile computer readable storage medium. For example, the computer instructions can be transmitted from a website, a computer, a server or a third database by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or third database. The non-volatile computer readable storage medium can be any available medium that a computer can access or a data storage device such as a server or a third database that includes one or more available media integrations. Available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)).
[0183] It should be noted that, in this document, relational terms such as first and first are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or device comprising the element.
[0184] The various embodiments in this specification are described in a related manner. Similar portions between the various embodiments can be referenced to each other. Each embodiment focuses on the differences between the other embodiments. In particular, the system embodiments are generally similar to the method embodiments, so their description is relatively simple. For related portions, reference can be made to the description of the method embodiments.
[0185] The above are only preferred embodiments of the present application and are not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application are included in the scope of protection of the present application.
Claims
1. An interface adaptation method, It is characterized in that Applied to a server management platform, the method comprises: Generate a function tree according to the target model, wherein the function tree includes a standard Redfish interface corresponding to a preset function in the target model; Scan the server Redfish interface corresponding to the target model, and generate an interface tree according to the interface characteristics of the server Redfish interface; According to the standard Redfish interface corresponding to the leaf node in the interface tree, a likelihood comparison is performed with all interfaces in the interface tree to generate a preliminary interface; When it is detected that the prepared interface is in a calling state and the matching degree of the interface return value of the prepared interface in the preset model library is greater than a preset value, it is determined that the actual interface adapted by the target model is the prepared interface.
2. The interface adaptation method according to claim 1, It is characterized in that Before the step of generating a function tree according to the target model, the method includes: A first initialization process is performed on a preset model library, wherein the preset model library includes a standard Redfish interface and a characteristic value corresponding to a return value of the Redfish interface of an adapted model.
3. The interface adaptation method according to claim 1, It is characterized in that The interface tree includes a root node which is the standard Redfish interface, a child node which is a resource interface, a sub-resource interface corresponding to the resource interface, and at least one of an interface corresponding to the sub-resource interface after data parsing, and a leaf node which is an actual path and parameter format of the Redfish interface.
4. The interface adaptation method according to claim 3, It is characterized in that The resource interface includes at least one of the following: system resources, chassis resources, management resources, session service resources, account service resources, upgrade service resources, and event subscription service resources.
5. The interface adaptation method according to claim 1, It is characterized in that The function tree includes a root node which is the target model, child nodes which are preset function types and basic functions corresponding to the preset function types, and leaf nodes which are standard Redfish interfaces corresponding to the basic functions.
6. The interface adaptation method according to claim 1, It is characterized in that After the step of generating a function tree according to the target model, the method comprises: Determine whether the target model exists in the preset model library; If the target model exists in the preset model library, directly obtain the actual interface list adapted by the target model; If the target model does not exist in the preset model library, it is determined whether there is a second function tree similar to the function tree corresponding to the target model in the preset model library.
7. The interface adaptation method according to claim 6, It is characterized in that After the step of determining whether there is a second function tree similar to the function tree corresponding to the target model in the preset model library, the method includes: If there is a second function tree similar to the function tree corresponding to the target model in the preset model library, the second function tree is used as the function tree corresponding to the target model; If there is no second function tree similar to the function tree corresponding to the target model in the preset model library, a second initialization process is performed on the function tree corresponding to the target model according to a user instruction.
8. The interface adaptation method according to claim 7, It is characterized in that The performing second initialization processing on the function tree corresponding to the target model includes: According to the interface characteristics of the standard Redfish interface, the total number of matching characteristic values corresponding to the standard Redfish interface in the preset model library is initialized.
9. The interface adaptation method according to claim 1, It is characterized in that The step of scanning the server Redfish interface corresponding to the target model and generating an interface tree according to the interface characteristics of the server Redfish interface includes: The server Redfish interface corresponding to the target model is automatically scanned according to the preset program setting, and the interface tree is generated from the root node level traversal. The interface tree includes the actual path and parameter format of the server Redfish interface.
10. The interface adaptation method according to claim 1, It is characterized in that The leaf nodes in the interface tree include the actual path of the server Redfish interface, and the likelihood comparison is performed between the standard Redfish interface corresponding to the leaf nodes in the interface tree and all interfaces in the interface tree to generate a preliminary interface, including: Calculating the likelihood between the actual path of each of the server Redfish interfaces and the interface path corresponding to the standard Redfish interface; The prepared interface is determined according to the likelihood.
11. The interface adaptation method according to claim 10, It is characterized in that The calculating the likelihood between the actual path of each server Redfish interface and the interface path corresponding to the standard Redfish interface comprises: Cut the interface path corresponding to each of the standard Redfish interfaces to generate keyword information; A feature value is extracted according to the keyword information, and the likelihood is generated according to a weight corresponding to the feature value and a matching degree between the feature value and an actual path of the server Redfish interface.
12. The interface adaptation method according to claim 10, It is characterized in that The likelihood is obtained by the following formula: Wherein, f(x) is the likelihood, p1, p2, and pn are the weights corresponding to each feature value, x1, x2, and xn are the matching degrees between each feature value and the actual path of the server Redfish interface in the interface tree, and y1, y2, and yn are the maximum matching degrees of each feature value and the actual path of the server Redfish interface in the interface tree, wherein n is a positive integer greater than 0 and less than or equal to the number corresponding to the keyword information. .
13. The interface adaptation method according to claim 1, It is characterized in that When it is detected that the prepared interface is in a calling state and the interface return value of the prepared interface has a matching degree greater than a preset value in a preset model library, determining that the actual interface adapted by the target model is the prepared interface includes: Calling the prepared interface to obtain an interface return value of the prepared interface; Extracting the feature item of the preliminary interface according to the interface return value, matching the feature item of the preliminary interface with the feature library corresponding to the preliminary interface in the preset model library, and generating the matching degree corresponding to the preliminary interface; When it is detected that the matching degree is greater than a preset value, it is determined that the actual interface adapted by the target model is the prepared interface.
14. The interface adaptation method according to claim 1, It is characterized in that After the step of determining that the actual interface adapted by the target model is the prepared interface when it is detected that the prepared interface is in a calling state and the interface return value of the prepared interface has a matching degree greater than a preset value in the preset model library, the method includes: connecting the actual interface; If the actual interface is in a normal working state, the actual interface is adapted to the target model; If the actual interface is in an abnormal working state, the second prepared interface is obtained for calling.
15. The interface adaptation method according to claim 14, It is characterized in that After the step of adapting the actual interface to the target model if the actual interface is in a normal working state, the method includes: Feature extraction is performed on the interface tree of the server corresponding to the target model, and the extracted features are filled into the preset model library.
16. The interface adaptation method according to claim 14, It is characterized in that After the step of adapting the actual interface to the target model if the actual interface is in a normal working state, the method includes: The features corresponding to the interface return value of the actual interface are extracted, and the features corresponding to the interface return value of the actual interface are filled into the preset model library.
17. The interface adaptation method according to claim 1, It is characterized in that The step of scanning the server Redfish interface corresponding to the target model and generating an interface tree according to the interface characteristics of the server Redfish interface includes: Determine a server according to the target model; The server Redfish interface of the server is scanned, and an interface tree is generated according to interface features of the server Redfish interface.
18. An interface adapter device, It is characterized in that The device comprises: A first generating module, configured to generate a function tree according to a target model, wherein the function tree includes a standard Redfish interface corresponding to a preset function in the target model; A second generating module is used to scan the server Redfish interface corresponding to the target model and generate an interface tree according to the interface characteristics of the server Redfish interface; A third generation module is used to compare the likelihood of the standard Redfish interface corresponding to the leaf node in the interface tree with all the interfaces in the interface tree to generate a preliminary interface; The determination module is used to determine that the actual interface adapted by the target model is the prepared interface when it is detected that the prepared interface is in a calling state and the interface return value of the prepared interface has a matching degree greater than a preset value in a preset model library.
19. A communication device, It is characterized in that include: A transceiver, a memory, a processor, and a program stored on the memory and executable on the processor; The processor is used to read the program in the memory to implement the interface adaptation method as described in any one of claims 1-17.
20. A non-volatile readable storage medium for storing a program, It is characterized in that When the program is executed by a processor, the interface adaptation method as described in any one of claims 1 to 17 is implemented.
Citation Information
Patent Citations
Server management method and system
CN112199197A
Server compatibility method, system and device and computer readable storage medium
CN113672389A
Server compatibility management method and device, equipment and medium
CN115080107A
Interface adaptation method and device, communication equipment and storage medium
CN116233103A
Method for accessing redfish data via a unified extensible firmware interface application
US20220335055A1
Cited By
Interface mapping method and electronic equipment
CN121255501A
