Management engine data processing method, system, apparatus, communication device, and storage medium

Abstract

The embodiment of the application provides a kind of management engine data processing method, system, device, communication device and storage medium, comprising: receiving the configuration script sent by user;According to configuration script, obtain the management engine data corresponding to configuration script;Management engine data is converted and handled, and target management engine data is obtained;According to configuration script, target management engine data is classified and handled, and different categories of target management engine data are obtained;Different categories of target management engine data are classified and stored in different data blocks, so that user accesses target management engine data in data block by out-of-band, i.e. the embodiment of the application receives the configuration script configured by user in advance, and ME data can be automatically collected in the case where ME problem or system crash occurs according to configuration script, so that user can not need to manually operate storage when ME problem occurs by external device, and user can access ME data in data block by out-of-band.

Description

Technical Field

[0001] This application relates to the field of data processing, and in particular to a data processing method, system, apparatus, communication device, and storage medium for a management engine. Background Technology

[0002] The Intel Management Engine (Intel ME) is a comprehensive service that manages and monitors Intel hardware modules and software drivers. It is integrated into the motherboard chipset and includes a microcontroller, the firmware-level MEFW (Firmware), and the driver-level MEI (Management Engine Interface). The ME is an important part of the power-on, power-off, and restart sequence, and is equivalent to a small, independent system. After the system is powered on, it can run independently. Therefore, information about the entire system can be obtained through the ME.

[0003] During system operation, issues such as system crashes or unresponsive power buttons may occur. Addressing these problems requires capturing and analyzing ME (Mean Equipment) data. Current platforms address ME failures by reserving two sets of I2C headers on the motherboard to obtain ME information and pinpoint the problem. However, this method only works when the problem is consistently reproducible, and requires manual manipulation and storage of the ME data using external devices. Summary of the Invention

[0004] The purpose of this application is to provide a management engine data processing method, system, device, communication equipment, and storage medium. The specific technical solution is as follows:

[0005] In a first aspect of this application, a management engine data processing method is provided, applied to a management engine system, the method comprising:

[0006] Receive configuration scripts sent by users;

[0007] Obtain the management engine data corresponding to the configuration script based on the configuration script;

[0008] The management engine data is transformed to obtain the target management engine data;

[0009] The target management engine data is classified according to the configuration script to obtain different categories of target management engine data.

[0010] The different categories of target management engine data are categorized and stored in different data blocks, so that the user can access the target management engine data in the data blocks out of the band.

[0011] Optionally, the configuration script includes a management engine data collection flag and a preset management engine data type, wherein the management engine data collection flag is used to determine whether to collect management engine data, and the preset management engine data type is used to determine the category of the collected management engine data;

[0012] The step of obtaining the management engine data corresponding to the configuration script according to the configuration script includes:

[0013] Based on the management engine data collection flag in the configuration script, determine whether to collect management engine data and perform detection and processing on all collected management engine data to obtain the management engine data corresponding to the configuration script;

[0014] The step of classifying the management engine data according to the configuration script to obtain different categories of management engine data includes:

[0015] The category of the collected management engine data is determined according to the preset management engine data type in the configuration script, and the management engine data is classified to obtain different categories of management engine data. The management engine data type is determined based on the data identifier or signal identifier corresponding to different data.

[0016] Optionally, after the step of classifying the target management engine data according to the configuration script to obtain different categories of target management engine data, the method includes:

[0017] The configuration script includes a data filtering script. The conversion logic interface in the conversion logic module of the management engine system is configured according to the data filtering script. The configured conversion logic interface is used to filter the target management engine data to obtain the filtered target management engine data.

[0018] The step of classifying and storing the different categories of target management engine data to obtain data blocks for storing the different categories of target management engine data includes:

[0019] The filtered target management engine data of different categories are classified and stored to obtain data blocks for storing the filtered target management engine data of different categories.

[0020] Optionally, the configuration script sent by the user includes:

[0021] When the system detects that the user's device is powered off, it receives the configuration script sent by the user through the intelligent platform management bus.

[0022] After the step of receiving the configuration script sent by the user, the method includes:

[0023] Receive the power-on startup signal from the user terminal, wherein the power-on startup signal is identified.

[0024] Optionally, after the step of classifying and storing the different categories of target management engine data in different data blocks, the method includes:

[0025] If a basic input / output system startup completion signal is detected or the startup time reaches the preset basic input / output system startup timeout, the acquisition of management engine data and storage of target management engine data shall be stopped, and the configuration script shall be cleared.

[0026] Optionally, the transformation process of the management engine data to obtain the target management engine data includes:

[0027] The management engine data is converted into target management engine data in a preset format, wherein the preset format includes binary.

[0028] In a second aspect of this application, a management engine data processing system is also provided, the system including a user terminal and a management engine system;

[0029] The management engine system includes a data detection module, a transformation logic module, and data blocks;

[0030] The data detection module is used to receive configuration scripts sent by users and obtain management engine data corresponding to the configuration scripts.

[0031] The conversion logic module is used to convert the management engine data to obtain target management engine data; and to classify the target management engine data according to the configuration script to obtain target management engine data of different categories.

[0032] The data block is used to classify and store the target management engine data of different categories;

[0033] The user terminal is used to send a pre-set configuration script to the management engine system via the intelligent platform management bus when the system is powered off, and to access the target management engine data in the data block of the management engine system out of band.

[0034] In a third aspect of this application, a management engine data processing apparatus is also provided, the apparatus comprising:

[0035] The receiving module is used to receive configuration scripts sent by users;

[0036] The acquisition module is used to acquire the management engine data corresponding to the configuration script based on the configuration script;

[0037] The conversion module is used to convert the management engine data to obtain target management engine data;

[0038] The classification module is used to classify the target management engine data according to the configuration script to obtain target management engine data of different categories;

[0039] The storage module is used to classify and store the different categories of target management engine data in different data blocks, so that the user can access the target management engine data in the data blocks out of the band.

[0040] Optionally, the configuration script includes a management engine data collection flag and a preset management engine data type, wherein the management engine data collection flag is used to determine whether to collect management engine data, and the preset management engine data type is used to determine the category of the collected management engine data;

[0041] The acquisition module includes:

[0042] The acquisition submodule is used to determine whether to collect management engine data based on the management engine data collection flag in the configuration script, and to detect and process all collected management engine data to obtain the management engine data corresponding to the configuration script.

[0043] The classification module includes:

[0044] The classification submodule is used to determine the category of the collected management engine data according to the preset management engine data type in the configuration script, and to classify the management engine data to obtain different categories of management engine data. The management engine data type is determined based on the data identifier or signal identifier corresponding to different data.

[0045] Optionally, the device further includes:

[0046] A filtering module is used to configure the conversion logic interface in the conversion logic module of the management engine system according to the configuration script, which includes a data filtering script. The configured conversion logic interface is used to filter the target management engine data to obtain the filtered target management engine data.

[0047] The storage module includes:

[0048] The storage submodule is used to classify and store the filtered target management engine data of different categories into different data blocks.

[0049] Optionally, the receiving module includes:

[0050] The receiving submodule is used to receive configuration scripts sent by the user through the intelligent platform management bus when the user terminal is detected to be in a powered-off state.

[0051] The device further includes:

[0052] A power-on signal receiving module is used to receive the power-on startup signal of the user terminal, wherein the power-on startup signal indicates that the user terminal has started up.

[0053] Optionally, the device further includes:

[0054] The stop module is used to stop acquiring the management engine data and storing the target management engine data, and to clear the configuration script, when a basic input / output system startup completion signal is detected or the startup time reaches the preset basic input / output system startup timeout.

[0055] Optionally, the conversion module includes:

[0056] The conversion submodule is used to convert the management engine data into target management engine data in a preset format, wherein the preset format includes binary.

[0057] In a fourth aspect of this application, a communication device is also provided, comprising: a transceiver, a memory, a processor, and a program stored in the memory and executable on the processor;

[0058] The processor is used to read programs from memory to implement the management engine data processing method as described in any of the first aspects.

[0059] In a fifth aspect of this application, a computer-readable storage medium is also provided, wherein instructions are stored therein, which, when executed on a computer, cause the computer to implement the management engine data processing method as described in any of the first aspects.

[0060] The management engine data processing method provided in this application embodiment receives a configuration script sent by a user; obtains management engine data corresponding to the configuration script; performs transformation processing on the management engine data to obtain target management engine data; classifies the target management engine data according to the configuration script to obtain target management engine data of different categories; and stores the target management engine data of different categories in different data blocks so that the user can access the target management engine data in the data blocks out of band. That is, this application embodiment receives a configuration script pre-configured by the user, and can automatically collect ME data when ME has problems or the system crashes, and process the ME data. The processed ME data can be allocated in different memory data blocks according to categories, so that the user can store the ME data without the need for external devices. The user can access the ME data in the data blocks out of band, and can ensure that ME data from machine startup to hang is collected. That is, the user can obtain ME data from a complete machine startup when the faulty machine recovers, so as to analyze the fault problems such as crashes or hangs based on the collected ME data. Attached Figure Description

[0061] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below.

[0062] Figure 1 The step flow of the management engine data processing method provided in the embodiments of this application Figure 1 ;

[0063] Figure 2 This is a flowchart of the management engine data processing method provided in the embodiments of this application. Figure 2 ;

[0064] Figure 3 This is a flowchart of the management engine data processing method provided in the embodiments of this application. Figure 3 ;

[0065] Figure 4 This is a flowchart of the management engine data processing method provided in the embodiments of this application. Figure 4 ;

[0066] Figure 5 This is a schematic diagram of a management engine data processing system provided in an embodiment of this application;

[0067] Figure 6 This is a block diagram of a management engine data processing apparatus provided in an embodiment of this application;

[0068] Figure 7 This is a schematic diagram of a communication device provided in an embodiment of this application;

[0069] Figure 8 This is a schematic diagram of a management engine data processing system in a related art provided in an embodiment of this application;

[0070] Figure 9 This is a flowchart of an exemplary management engine data processing method provided in an embodiment of this application. Detailed Implementation

[0071] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the various embodiments of this application will be described in detail below with reference to the accompanying drawings. However, those skilled in the art will understand that many technical details have been presented in the various embodiments of this application to enable readers to better understand this application. However, even without these technical details and various changes and modifications based on the following embodiments, the technical solutions claimed in this application can be implemented. The division of the various embodiments below is for the convenience of description and should not constitute any limitation on the specific implementation of this application. The various embodiments can be combined with and referenced by each other without contradiction.

[0072] Reference Figure 1 The flowchart illustrates the steps of the management engine data processing method provided in the embodiments of this application. Figure 1 The embodiments of this application are applied to a management engine system, and the method may include:

[0073] Step 101: Receive the configuration script sent by the user;

[0074] It should be noted that, in this embodiment, the system applied is the Management Engine (ME) system. The ME system can refer to the Intel Management Engine, an embedded microcontroller located within the PCH chipset. It runs management firmware using resources invisible to the host to provide specific management functions and power-on management. This firmware is digitally signed by Intel and authenticated by the ME before execution. The PCH also integrates an SPI flash controller capable of supporting two SPI flash memory components up to 16MB each to meet the storage requirements of the BIOS and ME firmware.

[0075] In one embodiment, SMlink0 is a bus interface used by the ME to transmit data to the outside world, and Host SMBus is a control bus interface used by the ME to receive various data transmitted from the outside world. Therefore, users can add configuration scripts for the data of SMlink0 and Host SMBus in the ME system, and configure the collection of data and filter out the required data through the configuration scripts, or collect all ME-related data.

[0076] It should be noted that, in this embodiment of the application, the collection of ME-related data will only begin after the configuration script has been configured.

[0077] Specifically, users can send configuration scripts to the ME system via the IPMB interface. The Intelligent Platform Management Bus (IPMB) interface is an I2C-based bus that provides standardized interconnection between different boards within the chassis. IPMB can be used as a standard interface for auxiliary or emergency management add-on cards, and it can transmit IPMI commands.

[0078] Step 102: Obtain the management engine data corresponding to the configuration script according to the configuration script;

[0079] It should be noted that in step 101, the ME system has already received the pre-written configuration script sent by the user. Therefore, management engine data can be collected according to the configuration script. For example, data on SMlink0 and Host SMBus in the ME system can be collected.

[0080] Therefore, obtaining the management engine data corresponding to the configuration script can be achieved by detecting the required management engine data in the configuration script from all management engine data.

[0081] Specifically, SMlink0 can communicate with BMC, for example, by transmitting ME version information, ME startup status, temperature information, etc. via I2C commands. Therefore, the ME data in this embodiment may include ME version information, ME startup status, temperature information, or some data sent by the user terminal.

[0082] Furthermore, in this embodiment of the application, a data detection module is set up inside the ME system to obtain the management engine data corresponding to the configuration script. Specifically, it may be responsible for detecting the data transmitted on Host SMBus and SMlink0.

[0083] Step 103: The management engine data is transformed to obtain the target management engine data;

[0084] It should be noted that, in this embodiment of the application, after obtaining the management engine data required by the configuration script, the management engine data needs to be transformed to obtain the target management engine data.

[0085] Furthermore, the step of converting the management engine data to obtain target management engine data includes: converting the management engine data into target management engine data in a preset format, wherein the preset format includes binary.

[0086] Specifically, in this embodiment, the management engine data can be a level signal. Therefore, it is necessary to convert the management engine data into a data format that is more convenient for log storage. For example, the high and low levels in the level signal can be converted into a binary data storage format.

[0087] Furthermore, in this embodiment of the application, a conversion logic module is set up inside the ME system. The conversion logic module is responsible for data conversion and data classification. That is, the detected data can be classified after passing through the conversion logic interface.

[0088] Step 104: Classify the target management engine data according to the configuration script to obtain target management engine data of different categories;

[0089] It should be noted that, in this embodiment of the application, after the data format conversion of the management engine data is performed, the target management engine data can be classified according to the script in the configuration script to obtain different categories of target management engine data.

[0090] Specifically, in one embodiment, the data type can be determined based on the data identifier or signal identifier corresponding to different data, thereby classifying the data collected from Host SMBus and SMlink0 into different categories. The identifier is used to name different data, so the corresponding data type is determined based on the identifier.

[0091] For example, ME version information can be represented as a version identifier, temperature information can be represented as a temperature identifier, and I2C protocol transmission can carry an I2C identifier, etc.

[0092] Step 105: The target management engine data of different categories are classified and stored in different data blocks so that the user can access the target management engine data in the data blocks out of the band.

[0093] It should be noted that, in this embodiment of the application, after different categories of target management engine data are classified and stored in different data blocks, users can access the target management engine data in the data blocks out of the band.

[0094] It should be noted that the final target management engine data can be stored as logs in different data blocks, that is, it can be represented as ME logs, and the ME logs collected in a single instance can be exported and accessed.

[0095] Specifically, users can remotely obtain target management engine data in a data block through IPMI commands, or export target management engine data in a data block through the IPMB interface.

[0096] Furthermore, in this embodiment of the application, a new memory space, namely a data block, is set up inside the ME system, and different data blocks are set up according to the classified data types. The location of the data block is located in the flash memory component inside the ME. Specifically, the data of SMlink0 and Host SMBus are stored in different areas, or different data blocks are set up according to the classified data types.

[0097] The management engine data processing method provided in this application embodiment receives a configuration script sent by a user; obtains management engine data corresponding to the configuration script; performs transformation processing on the management engine data to obtain target management engine data; classifies the target management engine data according to the configuration script to obtain target management engine data of different categories; and stores the target management engine data of different categories in different data blocks so that the user can access the target management engine data in the data blocks out of band. That is, this application embodiment receives a configuration script pre-configured by the user, and can automatically collect ME data when ME has problems or the system crashes, and process the ME data. The processed ME data can be allocated in different memory data blocks according to categories, so that the user can store the ME data without the need for external devices. The user can access the ME data in the data blocks out of band, and can ensure that ME data from machine startup to hang is collected. That is, the user can obtain ME data from a complete machine startup when the faulty machine recovers, so as to analyze the fault problems such as crashes or hangs based on the collected ME data.

[0098] Reference Figure 2 The flowchart illustrates the steps of the management engine data processing method provided in the embodiments of this application. Figure 2 The method may include:

[0099] Step 201: Receive the configuration script sent by the user;

[0100] It should be noted that, in the embodiments of this application, the above step 201 is described in the preceding discussion and will not be repeated here.

[0101] Step 202: Determine whether to collect management engine data based on the management engine data collection flag in the configuration script, and perform detection processing on all collected management engine data to obtain the management engine data corresponding to the configuration script;

[0102] It should be noted that, in the embodiments of this application, the configuration script includes the ME data collection flag.

[0103] Therefore, the management engine data collection and the management engine data required by the configuration script are determined based on the management engine data flag in the configuration script. For example, the flag can be 0 or 1, where 0 means no collection is required and 1 means collection is required.

[0104] Furthermore, the configuration script includes a management engine data collection flag and a preset management engine data type, wherein the management engine data collection flag is used to determine whether to collect management engine data, and the preset management engine data type is used to determine the category of the collected management engine data.

[0105] Step 203: The management engine data is transformed to obtain the target management engine data;

[0106] It should be noted that, in the embodiments of this application, step 203 is described in the preceding discussion and will not be repeated here.

[0107] Step 204: Determine the category of the collected management engine data according to the preset management engine data type in the configuration script, and classify the management engine data to obtain different categories of management engine data. The management engine data type is determined based on the data identifier or signal identifier corresponding to different data.

[0108] It should be noted that, in this embodiment of the application, the configuration script also includes a preset management engine data type.

[0109] Therefore, the category of collected engine data can be determined based on the preset management engine data in the configuration script, and the management engine data can be classified and processed accordingly to obtain different categories of management engine data. Furthermore, the management engine data type is determined based on the data identifier or signal identifier corresponding to different data.

[0110] Specifically, in one embodiment, the data type can be determined based on the data identifier or signal identifier corresponding to different data, thereby classifying the data collected from Host SMBus and SMlink0 into different categories. The identifier is used to name different data, so the corresponding data type is determined based on the identifier.

[0111] For example, ME version information can be represented as a version identifier, temperature information can be represented as a temperature identifier, and I2C protocol transmission can carry an I2C identifier, etc.

[0112] Step 205: The target management engine data of different categories are classified and stored in different data blocks so that the user can access the target management engine data in the data blocks out of the band.

[0113] It should be noted that, in the embodiments of this application, step 205 is described in the preceding discussion and will not be repeated here.

[0114] This application embodiment receives a pre-configured script from the user. Based on the configuration script, it can automatically collect ME data when ME problems occur or the system crashes. The ME data is then processed and allocated into different memory data blocks according to categories. This allows users to store ME data without the need for external devices. Users can access the ME data in the data blocks out of band and ensure that ME data from one machine startup to one hang is collected. That is, users can obtain complete ME data from one machine startup when the faulty machine recovers, which is used to analyze the faults such as crashes or hangs.

[0115] In addition, in this embodiment of the application, the configuration script includes a management engine data collection flag and a preset management engine data type. According to these configuration parameters preset in the configuration script, the ME system can more accurately determine the data that needs to be automatically collected when a fault occurs. The management engine data collection flag is used to determine whether to collect management engine data, and the preset management engine data type is used to determine the category of the collected management engine data. Setting different categories also facilitates the subsequent classification, storage and processing of data.

[0116] Reference Figure 3 The flowchart illustrates the steps of the management engine data processing method provided in the embodiments of this application. Figure 3 The method may include:

[0117] Step 301: Receive the configuration script sent by the user;

[0118] Step 302: Obtain the management engine data corresponding to the configuration script according to the configuration script;

[0119] Step 303: The management engine data is transformed to obtain the target management engine data;

[0120] Step 304: Classify the target management engine data according to the configuration script to obtain target management engine data of different categories;

[0121] It should be noted that, in the embodiments of this application, the above steps 301-304 are described in the preceding discussion and will not be repeated here.

[0122] Step 305: The configuration script includes a data filtering script. The conversion logic interface in the conversion logic module of the management engine system is configured according to the data filtering script. The configured conversion logic interface is used to filter the target management engine data to obtain the filtered target management engine data.

[0123] It should be noted that, in the embodiments of this application, the configuration script data may include a data filtering script. The data filtering script can configure the conversion logic interface in the conversion logic module of the management engine system, so that the configured conversion data interface filters the target management engine data to obtain the filtered target management engine data.

[0124] Specifically, filtering can be performed on target management engine data according to the filtering rules in the script. For example, redundant ME data can be filtered out, or ME data with null values ​​can be filtered out.

[0125] Step 306: The filtered target management engine data of different categories are classified and stored in different data blocks so that the user can access the target management engine data in the data blocks out of the band.

[0126] It should be noted that, in the embodiments of this application, after filtering the target management engine data of different categories, the data is classified and stored in different data blocks so that users can access the ME data in the data blocks out of the band.

[0127] This application embodiment receives a pre-configured script from the user. Based on the configuration script, it can automatically collect ME data when ME problems occur or the system crashes. The ME data is then processed and allocated into different memory data blocks according to categories. This allows users to store ME data without the need for external devices. Users can access the ME data in the data blocks out of band and ensure that ME data from one machine startup to one hang is collected. That is, users can obtain complete ME data from one machine startup when the faulty machine recovers, which is used to analyze the faults such as crashes or hangs.

[0128] In addition, by setting a data filtering script in the configuration script, the ME data can be further filtered during data collection. While ensuring the accuracy of autonomous data collection, the quality of the final ME data, i.e., the ME log, can also be improved, making it easier for users to analyze and process the data and resolve faults.

[0129] Reference Figure 4The flowchart illustrates the steps of the management engine data processing method provided in the embodiments of this application. Figure 4 The method may include:

[0130] Step 401: When the user terminal is detected to be in a powered-off state, the configuration script sent by the user is received through the intelligent platform management bus;

[0131] It should be noted that, in this embodiment of the application, receiving the configuration script sent by the user includes receiving the configuration script sent by the user through the intelligent platform management bus when the power-off state is detected.

[0132] Specifically, for users, when the device is powered off, they can modify the configuration script, set the data collection flag and preset data types, and send them to the ME system via IPMB to make the configuration script take effect.

[0133] Step 402: Receive the user terminal power-on startup signal, wherein the power-on startup signal indicates that the user terminal has started up.

[0134] It should be noted that, in one scenario of this application embodiment, before step 403 is performed, that is, before the ME data is collected, transformed, classified and filtered according to the configuration script, a power-on signal sent by the user terminal is received, wherein the power-on signal indicates that the user terminal has started.

[0135] Step 403: Obtain the management engine data corresponding to the configuration script according to the configuration script;

[0136] Step 404: The management engine data is transformed to obtain the target management engine data;

[0137] Step 405: Classify the target management engine data according to the configuration script to obtain target management engine data of different categories;

[0138] Step 406: The target management engine data of different categories are classified and stored in different data blocks so that the user can access the target management engine data in the data blocks out of the band.

[0139] It should be noted that, in the embodiments of this application, the above steps 403-406 are described in the preceding discussion and will not be repeated here.

[0140] Step 407: If a basic input / output system startup completion signal is detected or the startup time reaches the preset basic input / output system startup timeout, stop acquiring the management engine data and storing the target management engine data, and clear the configuration script.

[0141] It should be noted that in this application, in order to selectively collect single ME data, preset conditions are set to determine whether to stop the acquisition and storage of ME data. After acquiring and storing log information composed of a complete set of ME data, the configuration script is cleared to avoid repeated storage on the next boot.

[0142] This application embodiment receives a pre-configured script from the user. Based on the configuration script, it can automatically collect ME data when ME problems occur or the system crashes. The ME data is then processed and allocated into different memory data blocks according to categories. This allows users to store ME data without the need for external devices. Users can access the ME data in the data blocks out of band and ensure that ME data from one machine startup to one hang is collected. That is, users can obtain complete ME data from one machine startup when the faulty machine recovers, which is used to analyze the faults such as crashes or hangs.

[0143] In addition, since the ME system in this embodiment can operate independently, it receives the configuration script sent by the user while powered off and starts the system. During startup, it begins to collect, transform, classify, and filter ME data. After startup is complete or the startup time expires, it stops collecting and storing log data and clears the configuration script. This avoids data collection and detection from happening again on the next startup and allows for selective collection of log information corresponding to a single set of ME data.

[0144] Reference Figure 5 The diagram illustrates a management engine data processing system according to an embodiment of this application, the system including a user terminal and a management engine system;

[0145] The management engine system includes a data detection module, a transformation logic module, and data blocks;

[0146] The data detection module is used to receive configuration scripts sent by users and obtain management engine data corresponding to the configuration scripts.

[0147] The conversion logic module is used to convert the management engine data to obtain target management engine data; and to classify the target management engine data according to the configuration script to obtain target management engine data of different categories.

[0148] The data block is used to classify and store the target management engine data of different categories;

[0149] The user terminal is used to send a pre-set configuration script to the management engine system via the intelligent platform management bus when the system is powered off, and to access the target management engine data in the data block of the management engine system out of band.

[0150] Reference Figure 8 As shown, during system operation, problems such as system crashes or unresponsive power buttons often occur. For debugging ME on current platforms, the motherboard usually has two sets of I2C interfaces reserved to obtain ME information and thus locate ME problems. This method can only capture data for ME problems that are reproducible. For probabilistic ME problems that are not easy to reproduce, this method cannot capture data.

[0151] It should be noted that the management engine system includes a data detection module, a transformation logic module, and data blocks. Specifically, a data detection module is set up within the ME system to obtain management engine data corresponding to the configuration scripts. Specifically, it can be responsible for detecting data transmitted on Host SMBus and SMlink0. The transformation logic module is also set up within the ME system to handle data transformation and classification; that is, the detected data is categorized after passing through the transformation logic interface. Additionally, new memory space, i.e., data blocks, is set up within the ME system, and different data blocks are set up according to the classified data types. The data blocks are located in the flash memory components within the ME. Specifically, data from SMlink0 and Host SMBus are stored in different areas, or different data blocks are set up according to the classified data types.

[0152] It should be noted that, in the embodiments of this application, reference is made to... Figure 9 For the management engine data processing system, including the user's PC (the user end) and the ME system, the process for ME data collection and storage can be as follows: Figure 9 As shown.

[0153] As can be seen, the ME system detects and collects data based on the configuration scripts written by the user, performs data classification and filtering, and stores the collected and filtered data in a classified manner. Users can obtain data blocks out of the band.

[0154] This application embodiment receives a pre-configured script from the user. Based on the configuration script, it can automatically collect ME data when ME problems occur or the system crashes. The ME data is then processed and allocated into different memory data blocks according to categories. This allows users to store ME data without the need for external devices. Users can access the ME data in the data blocks out of band and ensure that ME data from one machine startup to one hang is collected. That is, users can obtain complete ME data from one machine startup when the faulty machine recovers, which is used to analyze the faults such as crashes or hangs.

[0155] Reference Figure 6 The diagram illustrates a structural schematic of a management engine data processing device according to an embodiment of this application. The device may include:

[0156] The receiving module 601 is used to receive configuration scripts sent by the user;

[0157] The acquisition module 602 is used to acquire the management engine data corresponding to the configuration script according to the configuration script;

[0158] The conversion module 603 is used to convert the management engine data to obtain target management engine data;

[0159] The classification module 604 is used to classify the target management engine data according to the configuration script to obtain target management engine data of different categories;

[0160] Storage module 605 is used to classify and store the different categories of target management engine data in different data blocks, so that the user can access the target management engine data in the data blocks out of the band.

[0161] Optionally, the configuration script includes a management engine data collection flag and a preset management engine data type, wherein the management engine data collection flag is used to determine whether to collect management engine data, and the preset management engine data type is used to determine the category of the collected management engine data;

[0162] The acquisition module includes:

[0163] The acquisition submodule is used to determine whether to collect management engine data based on the management engine data collection flag in the configuration script, and to detect and process all collected management engine data to obtain the management engine data corresponding to the configuration script.

[0164] The classification module includes:

[0165] The classification submodule is used to determine the category of the collected management engine data according to the preset management engine data type in the configuration script, and to classify the management engine data to obtain different categories of management engine data. The management engine data type is determined based on the data identifier or signal identifier corresponding to different data.

[0166] Optionally, the device further includes:

[0167] A filtering module is used to configure the conversion logic interface in the conversion logic module of the management engine system according to the configuration script, which includes a data filtering script. The configured conversion logic interface is used to filter the target management engine data to obtain the filtered target management engine data.

[0168] The storage module includes:

[0169] The storage submodule is used to classify and store the filtered target management engine data of different categories into different data blocks.

[0170] Optionally, the receiving module includes:

[0171] The receiving submodule is used to receive configuration scripts sent by users through the IPMB intelligent platform management bus when the user terminal is detected to be in a powered-off state.

[0172] The device further includes:

[0173] A power-on signal receiving module is used to receive the power-on startup signal of the user terminal, wherein the power-on startup signal indicates that the user terminal has started up.

[0174] Optionally, the device further includes:

[0175] The stop module is used to stop acquiring the management engine data and storing the target management engine data, and to clear the configuration script, when a basic input / output system startup completion signal is detected or the startup time reaches the preset basic input / output system startup timeout.

[0176] Optionally, the conversion module includes:

[0177] The conversion submodule is used to convert the management engine data into target management engine data in a preset format, wherein the preset format includes binary.

[0178] The management engine data processing device provided in this application embodiment receives a configuration script sent by a user; obtains management engine data corresponding to the configuration script; performs conversion processing on the management engine data to obtain target management engine data; classifies the target management engine data according to the configuration script to obtain target management engine data of different categories; and stores the target management engine data of different categories in different data blocks so that the user can access the target management engine data in the data blocks out of band. That is, this application embodiment receives a configuration script pre-configured by the user, and can automatically collect ME data when ME has problems or the system crashes, and process the ME data. The processed ME data can be allocated in different memory data blocks according to categories, so that the user can store the ME data without the need for external devices. The user can access the ME data in the data blocks out of band, and can ensure that ME data from machine startup to hang is collected. That is, the user can obtain ME data from a complete machine startup when the faulty machine recovers, so as to analyze the fault problems such as crashes or hangs based on the collected ME data.

[0179] This application also provides a communication device, such as... Figure 7 As shown, it includes 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 through the communication bus 704.

[0180] Memory 703 is used to store computer programs;

[0181] When processor 701 executes a program stored in memory 703, it can perform the following steps:

[0182] Receive configuration scripts sent by users;

[0183] Obtain the management engine data corresponding to the configuration script based on the configuration script;

[0184] The management engine data is transformed to obtain the target management engine data;

[0185] The target management engine data is classified according to the configuration script to obtain different categories of target management engine data.

[0186] The different categories of target management engine data are categorized and stored in different data blocks, so that the user can access the target management engine data in the data blocks out of the band.

[0187] The communication bus mentioned above can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0188] The communication interface is used for communication between the aforementioned terminal and other devices.

[0189] The memory may include random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0190] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0191] In another embodiment provided in this application, a computer-readable storage medium is also provided, which stores instructions that, when executed on a computer, cause the computer to perform any of the management engine data processing methods described in the above embodiments.

[0192] In another embodiment provided in this application, a computer program product containing instructions is also provided, which, when run on a computer, causes the computer to execute any of the management engine data processing methods described in the above embodiments.

[0193] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially 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, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).

[0194] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0195] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0196] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application are included within the scope of protection of this application.

Claims

1. A data processing method for a management engine, characterized in that, Applied to a management engine system, the method includes: Receive configuration scripts sent by users; Obtain the management engine data corresponding to the configuration script based on the configuration script; The management engine data is transformed to obtain the target management engine data; The target management engine data is classified according to the configuration script to obtain different categories of target management engine data. The target management engine data of different categories are classified and stored in different data blocks so that the user can access the target management engine data in the data blocks out of the band. The configuration script includes a management engine data collection flag and a preset management engine data type. The management engine data collection flag is used to determine whether to collect management engine data, and the preset management engine data type is used to determine the category of the collected management engine data. The step of obtaining the management engine data corresponding to the configuration script according to the configuration script includes: Based on the management engine data collection flag in the configuration script, determine whether to collect management engine data and perform detection and processing on all collected management engine data to obtain the management engine data corresponding to the configuration script; The step of classifying the management engine data according to the configuration script to obtain different categories of management engine data includes: The category of the collected management engine data is determined according to the preset management engine data type in the configuration script, and the management engine data is classified to obtain different categories of management engine data. The management engine data type is determined based on the data identifier or signal identifier corresponding to different data. After the step of classifying the target management engine data according to the configuration script to obtain different categories of target management engine data, the method includes: The configuration script includes a data filtering script. The conversion logic interface in the conversion logic module of the management engine system is configured according to the data filtering script. The configured conversion logic interface is used to filter the target management engine data to obtain the filtered target management engine data. The step of classifying and storing the different categories of target management engine data in different data blocks includes: The filtered target management engine data of different categories are classified and stored in different data blocks.

2. The management engine data processing method according to claim 1, characterized in that, The configuration script sent by the user includes: When the system detects that the user's device is powered off, it receives the configuration script sent by the user through the intelligent platform management bus. After the step of receiving the configuration script sent by the user, the method includes: The system receives the power-on startup signal from the user terminal, wherein the power-on startup signal indicates that the user terminal has started up.

3. The management engine data processing method according to claim 2, characterized in that, After the step of classifying and storing the different categories of target management engine data in different data blocks, the method includes: If a basic input / output system startup completion signal is detected or the startup time reaches the preset basic input / output system startup timeout, the acquisition of management engine data and storage of target management engine data shall be stopped, and the configuration script shall be cleared.

4. The management engine data processing method according to claim 1, characterized in that, The process of transforming the management engine data to obtain the target management engine data includes: The management engine data is converted into target management engine data in a preset format, wherein the preset format includes binary.

5. A management engine data processing system, characterized in that, The system includes a user terminal and a management engine system; The management engine system includes a data detection module, a transformation logic module, and data blocks; The data detection module is used to receive configuration scripts sent by users and obtain management engine data corresponding to the configuration scripts. The conversion logic module is used to convert the management engine data to obtain target management engine data; and to classify the target management engine data according to the configuration script to obtain target management engine data of different categories. The data block is used to classify and store the target management engine data of different categories; The user terminal is used to send a pre-set configuration script to the management engine system through the intelligent platform management bus when the power is off, and to access the target management engine data in the data block of the management engine system out of band. The configuration script includes a management engine data collection flag and a preset management engine data type. The management engine data collection flag is used to determine whether to collect management engine data, and the preset management engine data type is used to determine the category of the collected management engine data. The step of obtaining the management engine data corresponding to the configuration script according to the configuration script includes: Based on the management engine data collection flag in the configuration script, determine whether to collect management engine data and perform detection and processing on all collected management engine data to obtain the management engine data corresponding to the configuration script; The step of classifying the management engine data according to the configuration script to obtain different categories of management engine data includes: The category of the collected management engine data is determined according to the preset management engine data type in the configuration script, and the management engine data is classified to obtain different categories of management engine data. The management engine data type is determined based on the data identifier or signal identifier corresponding to different data. After the step of classifying the target management engine data according to the configuration script to obtain different categories of target management engine data, the system includes: The configuration script includes a data filtering script. The conversion logic interface in the conversion logic module of the management engine system is configured according to the data filtering script. The configured conversion logic interface is used to filter the target management engine data to obtain the filtered target management engine data. The step of classifying and storing the different categories of target management engine data in different data blocks includes: The filtered target management engine data of different categories are classified and stored in different data blocks.

6. A management engine data processing device, characterized in that, The device includes: The receiving module is used to receive configuration scripts sent by users; The acquisition module is used to acquire the management engine data corresponding to the configuration script based on the configuration script; The conversion module is used to convert the management engine data to obtain target management engine data; The classification module is used to classify the target management engine data according to the configuration script to obtain target management engine data of different categories; The storage module is used to classify and store the different categories of target management engine data in different data blocks, so that the user can access the target management engine data in the data blocks out of the band. The configuration script includes a management engine data collection flag and a preset management engine data type. The management engine data collection flag is used to determine whether to collect management engine data, and the preset management engine data type is used to determine the category of the collected management engine data. The acquisition module includes: The acquisition submodule is used to determine whether to collect management engine data based on the management engine data collection flag in the configuration script and to detect and process all collected management engine data to obtain the management engine data corresponding to the configuration script. The classification module includes: The classification submodule is used to determine the category of the collected management engine data according to the preset management engine data type in the configuration script, and to classify the management engine data to obtain management engine data of different categories. The management engine data type is determined based on the data identifier or signal identifier corresponding to different data. The device further includes: A filtering module is used to configure the conversion logic interface in the conversion logic module of the management engine system according to the configuration script, which includes a data filtering script. The configured conversion logic interface is used to filter the target management engine data to obtain the filtered target management engine data.

7. A communication device, characterized in that, include: A transceiver, a memory, a processor, and a program stored in the memory and executable on the processor; The processor is used to read programs from memory to implement the management engine data processing method as described in any one of claims 1-4.

8. A readable storage medium for storing a program, characterized in that, When the program is executed by the processor, it implements the management engine data processing method as described in any one of claims 1-4.

Images