A method for processing device information and an electronic device

Abstract

This application discloses a method and electronic device for processing device information, belonging to the field of computer technology, and is used to improve the processing efficiency of device information in electronic devices. The method is executed by a first electronic device and includes: obtaining a mirror system file; mounting the mirror system file to a second electronic device; wherein the second electronic device supports loading the mirror system file and running the mirror system, and the mirror system contains an application for modifying device information; sending a processing instruction to the second electronic device; the processing instruction instructs the device information to be modified, and the second electronic device modifies the device information by running the application.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method for processing device information and an electronic device. Background Technology

[0002] In the processes of equipment production, sales, and reuse, it is necessary to process equipment information in computing devices, such as modifying, deleting, and adding equipment information in brand-new computing devices. For example, with the continuous development of business needs and the accelerating pace of product upgrades, the market demand for independent and modular computing devices is constantly increasing. Therefore, the demand for white-label devices is also rising. At the same time, enterprises also need to perform white-label operations on equipment in scenarios such as sales, reuse, or inventory recycling. Therefore, the current need for white-label operations on computing devices is constantly increasing. Currently, management tools are commonly used to perform white-label operations on computing devices one by one through scripts or commands, which cannot perform batch white-label operations.

[0003] In related technologies, the Intelligent Platform Management Interface (IPMI) is typically relied upon to process device information for batch computing devices.

[0004] However, IPMI is based on the User Datagram Protocol (UDP), which has poor stability, resulting in a low success rate for device information processing. IPMI may even become unavailable frequently, making batch device information processing impossible and consequently reducing the efficiency of device information processing in electronic devices. Summary of the Invention

[0005] This application provides a method and electronic device for processing device information, which improves the processing efficiency of device information in electronic devices. The technical solution is as follows:

[0006] In a first aspect, a method for processing device information is provided, which is executed by a first electronic device. The method includes: obtaining a mirror system file; mounting the mirror system file to a second electronic device; wherein the second electronic device supports loading the mirror system file and running the mirror system, and the mirror system contains an application for modifying device information; sending a processing instruction to the second electronic device; the processing instruction is used to instruct the device information to be modified, and the second electronic device modifies the device information by running the application.

[0007] As can be seen from the above, by mounting the image system file to the second electronic device and having the application in the image system modify the device information, the device information can be processed in-band, thereby improving the success rate of the first electronic device in processing the device information of the second electronic device and thus improving the processing efficiency of the device information of the electronic device.

[0008] In one possible implementation, a query instruction is sent to a second electronic device; the query instruction is used to instruct the retrieval of processing information from the mirror system; the processing information includes processing results and / or processing progress; and the processing information is received.

[0009] As can be seen from the above, by sending a query command to the second electronic device, processing information can be obtained through the mirror system of the second electronic device, and the execution status of the processing command can be monitored, thereby improving the processing efficiency of the device information of the electronic device.

[0010] In one possible implementation, the image system file is obtained in the event of an anomaly in communication between the first electronic device and the second electronic device via the IPMI interface.

[0011] As can be seen from the above, by mounting the image system file to the second electronic device, the influence of the IPMI interface is avoided, and the device information is modified in-band, thereby improving the processing efficiency of the electronic device's device information.

[0012] In one possible implementation, where the electronic device communicates normally with the second electronic device via the IPMI interface and the device information is stored in the BMC of the second electronic device, the method further includes sending an IPMI processing script to the second electronic device via the IPMI interface; the IPMI processing script supports execution via the BMC of the second electronic device and modification of the device information.

[0013] As can be seen from the above, when the first electronic device communicates normally with the second electronic device through the IPMI interface and the device information is stored in the BMC of the second electronic device, the electronic device can complete the device information processing through the IPMI processing script, which can save the computing power of the electronic device and thus improve the processing efficiency of the device information.

[0014] In one possible implementation, a Hypertext Transfer Protocol (HTTP) service is initiated to send processing instructions to the respective BMCs of at least two second electronic devices via the Redfish interface.

[0015] As can be seen from the above, by enabling the HTTP service, electronic devices can send processing instructions in batches via HTTP commands, thereby enabling the first electronic device to process device information from a batch of second electronic devices, thus improving the processing efficiency of device information.

[0016] In one possible implementation, the architecture information of the second electronic device is obtained; based on the architecture information, the image system file is determined.

[0017] As can be seen from the above, a second electronic device that can be compatible with different architectures can realize device information processing, thereby improving the device information processing efficiency of the electronic device.

[0018] In one possible implementation, the second electronic device includes an ARM-based computing device and / or an x86-based computing device.

[0019] In one possible implementation, device information includes an electronic tag stored in the BMC and / or the BIOS system identifier (BIOS Logo) stored in the BIOS chip.

[0020] Secondly, a method for processing device information is provided, which is executed by a second electronic device. The method includes: loading an image system file and running an image system; wherein the image system file is obtained by a first electronic device; the first electronic device is used to mount the image system file to the second electronic device; an application for modifying device information runs in the image system; receiving a processing instruction sent by the first electronic device; the processing instruction is used to instruct the device information to be modified; and modifying the device information by running the application.

[0021] In one possible implementation, a query instruction sent by an electronic device is received; the query instruction is used to instruct the acquisition of processing information from the mirror system; the processing information includes processing results and / or processing progress; and the processing information is sent to the electronic device.

[0022] In one possible implementation, if the first electronic device malfunctions in communicating with the second electronic device via the IPMI interface, the image system file is loaded and the image system is run.

[0023] In one possible implementation, where the first electronic device communicates normally with the second electronic device via the IPMI interface and the device information is stored in the BMC of the second electronic device, the method further includes: receiving an IPMI processing script sent by the first electronic device via the IPMI interface; the IPMI processing script supports execution via the BMC of the second electronic device and modification of the device information.

[0024] In one possible implementation, architecture information is sent to a first electronic device; the architecture information is used by the first electronic computing device to determine the image system file.

[0025] Thirdly, a device information processing apparatus is provided, which is applied to an electronic device. In embodiments of this application, the device information processing apparatus can be divided into functional modules according to the method provided in the first aspect. For example, each function can be divided into its own functional modules, or two or more functions can be inherited into one processing module. For instance, embodiments of this application can divide the device information processing apparatus into a connection module and a transmission module according to function. The descriptions of the possible technical solutions and beneficial effects of the various functional modules described above can be found in the technical solutions provided in the first aspect or its corresponding possible implementations, and will not be repeated here.

[0026] Fourthly, embodiments of this application provide an electronic device, which includes a processor and a memory. The memory stores computer instructions, which are loaded and executed by the processor to enable the electronic device to perform the device information processing method as described in the first or second aspect above.

[0027] Fifthly, embodiments of this application provide a computer-readable storage medium storing at least one computer program, which is loaded and executed by a processor to implement the device information processing method as described in the first aspect above.

[0028] Sixthly, embodiments of this application provide a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computing device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computing device to perform the device information processing method provided in the various optional implementations of the first aspect described above.

[0029] For a detailed description of the third to sixth aspects and their various implementations in the embodiments of this application, please refer to the detailed description in the first aspect and its various implementations; and for a detailed description of the beneficial effects of the second to sixth aspects and their various implementations, please refer to the beneficial effect analysis in the first aspect and its various implementations, which will not be repeated here.

[0030] These or other aspects of the embodiments of this application will become more apparent in the following description. Attached Figure Description

[0031] Figure 1 This illustration shows a hardware architecture diagram of a device information processing system 100 provided in an embodiment of this application;

[0032] Figure 2 This document illustrates a hardware structure diagram of a first electronic device 110 provided in an embodiment of this application.

[0033] Figure 3 A flowchart illustrating a device information processing method provided in an embodiment of this application is shown;

[0034] Figure 4 A schematic diagram of the first interface 001 of a device information processing system 100 provided in an embodiment of this application is shown;

[0035] Figure 5 A schematic diagram of the second interface 002 of a device information processing system 100 provided in an embodiment of this application is shown;

[0036] Figure 6 This illustration shows an interactive flowchart of a device information processing method provided in an embodiment of this application;

[0037] Figure 7 This illustration shows a logic diagram of a method for performing white-label operation on at least two second electronic devices according to an embodiment of this application;

[0038] Figure 8 A schematic diagram of the structure of a device information processing apparatus 400 provided in an embodiment of this application is shown. Detailed Implementation

[0039] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. In addition, in order to clearly describe the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish the same or similar items with basically the same function and effect.

[0040] Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or order of execution, and that "first," "second," etc., are not necessarily different. Furthermore, in some embodiments of this application, words such as "exemplary" or "for example" are used to indicate that something is being described as an example, illustration, or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner for ease of understanding.

[0041] Furthermore, the device architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of device architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0042] First, the application scenarios of the embodiments of this application will be introduced by way of example.

[0043] To adapt to rapidly evolving market demands and corporate transformation, equipment manufacturers need to process equipment information for completed computing devices, including modifying, deleting, or updating device information. For example, with business growth and market upgrades, coupled with the need to expand sales channels and achieve more refined inventory management, companies are increasingly demanding white-label equipment. Therefore, more and more scenarios require the implementation of white-label operations on computing devices.

[0044] White-label devices refer to computing devices that are not authorized by a brand or do not contain brand-related information. These devices do not bear any brand logo and typically have some basic specifications and functions. White-label operation is used to instruct the erasure of electronic tags in the basic input / output system (BIOS) settings or baseboard management controller (BMC) that may contain original brand information.

[0045] This application provides a method for processing device information. The method includes: a first electronic device acquiring a mirror system file and mounting the mirror system file to a second electronic device. The second electronic device supports loading and running the mirror system file, and the mirror system contains an application for modifying device information. The first electronic device sends a processing instruction to the second electronic device, and the second electronic device processes the device information by running the application in the mirror system. The processing instruction is used to instruct modifications to the device information.

[0046] The above method avoids the impact of IMPI interface instability and solves the problem of device information processing on the second electronic device when IPMI is unavailable or the processing instructions indicate in-band operations within the second electronic device. This device information processing includes white-label operations on the second electronic device, meaning the processing instructions include white-label instructions. This improves the efficiency of device information processing for the electronic device.

[0047] Secondly, the system architecture of the embodiments of this application will be described by way of example.

[0048] Figure 1 This diagram illustrates the hardware architecture of a device information processing system 100 provided in an embodiment of this application. Figure 1 As shown, the device information processing system 100 includes a first electronic device 110 and a second electronic device 120. The first electronic device 110 and the second electronic device 120 can communicate with each other via the IPMI interface protocol and / or the Redfish management protocol.

[0049] The first electronic device 110 may include mobile phones, smartwatches, tablets, foldable electronic devices, desktop computers, laptops, handheld computers, laptops, Ultra-Mobile Personal Computers (UMPCs), netbooks, cellular phones, Personal Digital Assistants (PDAs), Augmented Reality (AR) devices, Virtual Reality (VR) devices, Artificial Intelligence (AI) devices, wearable devices, in-vehicle devices, and other electronic devices with communication capabilities. This application does not impose any special limitations on the specific type of electronic device.

[0050] The second electronic device 120 includes a BMC 130, which can be a standard general-purpose server, specifically a blade server, high-density server, rack server, or high-performance server. The BMC 130 is an independent management unit of the second electronic device 120, and includes a microprocessor, memory, BMC firmware, and an interface. The microprocessor executes various instructions and runs the BMC firmware. The memory stores data and programs generated during BMC firmware operation and performs read and / or write operations during BMC firmware operation. The BMC firmware is a set of software programs that provide the basic functions of the BMC. The interface is used for communication and information exchange between the BMC and external devices. Specifically, the BMC 130 can be an intelligent baseboard management controller (iBMC).

[0051] After the first electronic device 110 obtains the image system file, it mounts the image system file to the second electronic device 120. The second electronic device 120 supports loading and running the image system from the image file. The image system contains an application for modifying device information. The image system file is a file containing a complete operating system. Specifically, the image system 140 can be a Linux system.

[0052] The first electronic device 110 is also configured to send processing instructions to the second electronic device 120, the processing instructions being used to instruct changes to device information. The second electronic device 120 executes the processing instructions and runs an application in the mirror system to change the device information.

[0053] For example, Figure 2 This diagram illustrates the hardware structure of a first electronic device 110 according to an embodiment of this application. Figure 2 As shown, the first electronic device 110 includes a processor 210, a memory 220, an electronic screen 230, and a bus 240. The processor 210, memory 220, and electronic screen 230 communicate with each other via the bus 240. It should be understood that this application does not limit the number of processors and memories in the electronic device.

[0054] The processor 210 is used to acquire the image system file and mount it to the second electronic device 120. The processor 210 is also used to send processing instructions to the second electronic device 120. Specifically, the processor 210 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0055] The memory 220 stores executable program code, and the processor 210 executes the executable program code to implement the above-described device information processing method.

[0056] The electronic screen 230 is used to display the interface of the device information processing system 100.

[0057] It should be noted that the system architecture and application scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0058] For ease of understanding, the method for processing device information provided in this application is described below with reference to the accompanying drawings. This method for processing device information is... Figure 1 The first electronic device 110 shown is used for execution.

[0059] Figure 3 A flowchart illustrating a device information processing method provided in an embodiment of this application is shown. Figure 3 As shown, the information processing method of this device is executed by a first electronic device and includes the following steps:

[0060] S101, the first electronic device acquires the image system file.

[0061] The second electronic device supports loading and running an image system file. The image system contains an application for modifying device information.

[0062] In this embodiment of the application, the image system file is a file containing a complete operating system, specifically a Linux system image file.

[0063] Optionally, if communication between the first electronic device and the second electronic device via the IPMI interface fails, the image system file can be obtained. Specific reasons for communication failure between the first electronic device and the second electronic device via the IPMI interface include hardware failure, connection line failure, switch not supporting IPMI, network configuration errors, or incompatibility with IPMI management software.

[0064] In one possible implementation, the first electronic device obtains the architecture information of the second electronic device; based on the architecture information, it determines the image system file.

[0065] For example, the second electronic device includes a computing device based on an ARM architecture and / or a computing device based on an x86 architecture.

[0066] For example, the first electronic device can query the architecture information of the second electronic device through the Redfish interface. Based on the returned architecture information, the first electronic device determines the image system file. If the second electronic device is an ARM architecture computing device, the first electronic device determines the image system file to be the first image system file loaded by an ARM-based electronic device. The first image system file contains the core operating system files and drivers for the ARM architecture. If the second electronic device is a computing device based on the Intel 8086 and backward compatible central processing unit instruction set architecture (x86 architecture), the first electronic device determines the image system file to be the second image system file loaded by an x86-based electronic device. The second image system file contains the core operating system files and drivers for the x86 architecture. Specifically, the first or second image system file can be a Windows image system file or a Linux image system file.

[0067] Optionally, the architecture information of the second electronic device can be obtained by relevant technical personnel through hardware manuals, product documents, etc., and based on the architecture information, the relevant technical personnel can upload the image system file to the first electronic device. There are no specific limitations on how the first electronic device obtains the architecture information of the second electronic device.

[0068] S102, the first electronic device mounts the image system file to the second electronic device.

[0069] In this embodiment of the application, the first electronic device can send the image system file to the second electronic device through the Redfish interface. The second electronic device receives the image system file through the BMC and stores the image system file in the memory of the second electronic device, thereby enabling the central processing unit (CPU) of the second electronic device to start the image system through the driver in the image system file.

[0070] S103, the first electronic device sends a processing instruction to the second electronic device.

[0071] The processing instruction is used to instruct changes to the device information, and the second electronic device changes the device information by running an application.

[0072] Additionally, the second electronic device initiates the mirror system. The mirror system obtains the BMC's Redfish token via IPMI, enabling the BMC of the second electronic device to interact with the mirror system and thus allowing the mirror system to receive processing instructions. The Redfish token is a token mechanism used for authentication in the Redfish protocol.

[0073] For example, the first electronic device sends processing instructions to the BMC of the second electronic device through the Redfish interface, and the second electronic device sends the processing instructions to the mirror system through the BMC, so that the second electronic device can change the device information by running an application.

[0074] In one possible implementation, device information includes an electronic tag stored in the BMC and / or the BIOS system identifier (BIOS Logo) stored in the BIOS chip.

[0075] For example, if the communication between the first electronic device and the second electronic device malfunctions via the IPMI interface, the first electronic device sends processing instructions to the BMC of the second electronic device via the Redfish interface. These instructions include a white-label instruction. The white-label instruction instructs the mirroring system to delete electronic tags and / or the BIOS logo in the second electronic device. The white-label instruction includes white-label content, which represents the electronic tag and / or BIOS logo that needs to be deleted.

[0076] for example, Figure 4 This diagram illustrates a first interface 001 of a device information processing system 100 provided in an embodiment of this application. For example... Figure 4 As shown, the first interface 001 runs on the first electronic device. The first interface 001 includes input fields for task name, image system file, and the second electronic device, as well as selection controls for execution strategies, including "execute later" and "execute immediately." Preview controls are also included after each input field to display uploaded information or files. Create and cancel controls are also included below the first interface 001. The first interface 001 is used to realize the interaction between the device information processing system 100 and the user, allowing the user to process information on the second electronic device through the first interface 001.

[0077] Taking a user performing a white-label operation on a second electronic device via the first interface 001 displayed on the electronic device as an example, the user creates a task name using the task name input field. Based on the architecture information of the second electronic device, the user determines the image system file and uploads it through the image system file input field. Alternatively, the user can first upload the identification code, serial number, model number, etc., of the second electronic device through the input field, and the first electronic device will automatically fill in the image system file. No specific limitations are specified here. After selecting the execution method through the execution strategy selection control, the user clicks "Create Control" to create a task for the electronic device to perform a white-label operation on the second electronic device.

[0078] During the white card operation, the first electronic device sends a white card command to the second electronic device via the Redfish interface. The mirror system of the second electronic device obtains the white card command through the BMC and parses it to obtain the location information where the white card content is stored, as follows:

[0079] / home / Project / tools / BatchIsoTools / oem / config.json

[0080] The mirroring system retrieves the white card content based on location information. Following the white card instructions, the mirroring system runs the application and executes the white card operation. The white card content is shown below:

[0081] "Fw Upgrade Version Require": "1.0.1",

[0082] "Product Name": "KL 2280 V2",

[0083] "Custom Manufacturer": "KL",

[0084] "Custom Board Manufacturer": "KL",

[0085] "Board Product Name": "KL 2280 V2",

[0086] "Machine Name": "KL 2280 V2",

[0087] "BIOS Logo": ".. / oem / bios / Logo.bmp",

[0088] "BMC Hpm File": ".. / oem / bmc / hpm / bmc_arm_V3.hpm",

[0089] "Redfish Oem": "HW"

[0090] "IPMI OEM": "0xdb 0x07 0x00",

[0091] “SNMP Oem”: “a”

[0092] "BMC oft Name": "iBMC",

[0093] "Custom Alarm Name": "iBMC",

[0094] "Custom Log Ibma Name": "iBMC",

[0095] "Custom Log Ibma Name": "iBMC",

[0096] "Clp Command": "iBMC",

[0097] "QR code State": "0x01"

[0098] Among them, "Fw Upgrade Version Require" indicates the firmware upgrade version requirement of the management tool used by the first electronic device; "Product Name" indicates the product name of the second electronic device; "Custom Manufacturer" indicates the custom manufacturer of the second electronic device; "Custom Board Manufacturer" indicates the custom motherboard manufacturer of the second electronic device; "Board Product Name" indicates the motherboard product name of the second electronic device; "Machine Name" indicates the machine name of the second electronic device; "BIOS Logo" indicates the boot logo of the second electronic device; "BMC HpmFile" indicates the BMC upgrade file of the second electronic device; "Redfish Oem" indicates the Redfish manufacturer-specific extension; "IPMI Oem" indicates the IPMI manufacturer-specific extension; "SNMP Oem" indicates the network protocol manufacturer extension; "BMC oftName" indicates the BMC software name; "Custom Alarm Name" indicates the custom alarm name; "Custom Log IbmaName" indicates the custom log name; "Clp Command" indicates the command line processor; and "QR code State" indicates the QR code status of the BMC in the second electronic device.

[0099] It should be understood that the above white-label content is only an example and does not constitute a limitation. The specific fields and contents included in the white-label content are related to the second electronic device and the first electronic device where the device information is processed in the actual application scenario.

[0100] As can be seen from the "BIOS Logo" field and the address information ".. / oem / bios / Logo.bmp" in the white card content, the white card operation specifically involves deleting the BIOS Logo stored in ".. / oem / bios / Logo.bmp" on the second electronic device. The mirror system reads the white card content and, based on the device model of the first device (e.g., "Product Name": "KL 2280 V2" in the white card content), determines the corresponding deletion tool. If the device model is V3, the V3 deletion tool is used to perform the white card operation and delete the BIOS Logo. If the device model is V2, the V2 deletion tool is used to perform the white card operation and delete the BIOS Logo. If the white card content is empty, the mirror system does not perform the white card operation.

[0101] Optionally, before the first electronic device sends the white card instruction to the BMC of the second electronic device via the Redfish interface, the first electronic device verifies the white card content in the white card instruction to determine its legality. Taking the white card content mentioned above as an example, the white card field is "BIOS Logo": ".. / oem / bios / Logo.bmp". The electronic device verifies whether the content of the field conforms to the field rules. If the white card content is "BIOS Logo", then the data of the field content is in image format; if it is in string format, then the white card content is not legal.

[0102] As can be seen from the above, the first electronic device provides a first interface 001, which can increase the interactivity and convenience between the user and the device information processing system 100, thereby improving the efficiency of device information processing and further improving the efficiency of white-label operation of the first electronic device.

[0103] In one possible implementation, the first electronic device initiates a Hypertext Transfer Protocol (HTTP) service and sends processing instructions to the respective BMCs of at least two second electronic devices via the Redfish interface.

[0104] For example, the Redfish management protocol is built on top of the Hypertext Transfer Protocol (HTTP) service. The first electronic device sends processing instructions to the respective BMCs of at least two second electronic devices via HTTP requests, according to the instruction format requirements supported by the second electronic devices.

[0105] For example, in the case of a first electronic device performing batch white-card operations on at least two second electronic devices, the first electronic device can share image files with at least two second electronic devices via the Redfish interface using a network file system (NFS). After all the corresponding image systems of at least two second electronic devices are started, the first electronic device sends white-card instructions to the respective BMCs of at least two second electronic devices via HTTP requests. This enables the respective image systems of at least two second electronic devices to run applications and perform white-card operations based on the white-card content included in the white-card instructions, thereby realizing batch white-card operations by the first electronic device on at least two second electronic devices.

[0106] In one possible implementation, the first electronic device sends a query instruction to the second electronic device; the query instruction is used to instruct the acquisition of processing information from the mirror system; the processing information includes processing results and / or processing progress; the first electronic device receives the processing information.

[0107] For example, the first electronic device forwards a query command through the BMC of the second electronic device, causing the mirror system to execute the query command and obtain the execution information of the processing command executed in the mirror system. By obtaining the execution information through the forwarding of the BMC in the second electronic device, the first electronic device can monitor the execution of the processing command.

[0108] for example, Figure 5 This diagram illustrates a second interface 002 of a device information processing system 100 provided in an embodiment of this application. For example... Figure 5 As shown, the second interface 002 is used to display processing information, which may include task name, execution status, creation time, completion time, and time elapsed. The execution status may include "execution completed" or "in progress."

[0109] The second interface 002 also includes a list of second electronic devices. The main fields of this list may include identification code, status, serial number, model, start time, end time, and reason for failure. Figure 5 Taking a second electronic device with identification code 12.24.567, serial number 123467T, and model V2 as an example, the "Execution Completed" field in the "Status" field indicates that the image system file execution processing instructions of the second electronic device have been completed. The characters in the "Failure Reason" field indicate that the image system file execution processing instructions of the second electronic device were successful. If the image system file execution processing instructions of the second electronic device fail, the "Failure Reason" field provides a detailed description of the failure reason.

[0110] As can be seen from the above, the second interface 002 provided by the first electronic device can effectively display the results of device information processing, increase the interactivity of the device information processing system 100, thereby improving the efficiency of device information processing and further improving the efficiency of white-label operation of the electronic device.

[0111] In one possible implementation, where the first electronic device communicates normally with the second electronic device via the IPMI interface and the device information is stored in the BMC of the second electronic device, the method further includes sending an IPMI processing script to the second electronic device via the IPMI interface; the IPMI processing script supports execution via the BMC of the second electronic device and modification of the device information.

[0112] The IPMI processing script includes connection information and processing instructions. Connection information typically includes the IP address of the second electronic device and / or the username and password of the BMC.

[0113] For example, when the first electronic device is communicating normally with the second electronic device through the IPMI interface, if the first electronic device determines that the device information in the processing instruction is stored in the BMC, the first electronic device sends an IPMI processing script to the second electronic device. The second electronic device receives the IPMI processing script through the BMC and executes the processing instructions in the IPMI processing script, changing the target device information stored in the BMC. The IPMI processing script may include an IPMI white-label script.

[0114] As can be seen from the above, when the first electronic device communicates normally with the second electronic device through the IPMI interface and the target device information is stored in the BMC, the first device completes the device information processing through the IPMI processing script. There is no need to mount the mirror system on the second electronic device, which can save the computing power of the first electronic device and thus improve the processing efficiency of the device information of the electronic device. Specifically, it can improve the efficiency of white-label operation of the electronic device.

[0115] The method for processing the above-mentioned device information is described below from the perspective of the interaction between the BMC 130 and the mirror system 140 in the first electronic device 110 and the second electronic device 120. Figure 6 This illustration shows an interactive flowchart of a device information processing method provided in an embodiment of this application. Figure 6 As shown, the mirror system 140 is mounted in the second electronic device 120, and the method includes:

[0116] In the event of a communication failure between the first electronic device 110 and the second electronic device 120 via the IPMI interface, the first electronic device 110 sends a system image file to the BMC 130 via the Redfish interface (S201). The BMC 130 stores the system image file in the memory of the second electronic device, enabling the CPU of the second electronic device to boot the system image 140 using the driver in the system image file (S202). After the system image 140 boots, it obtains the Redfish token of the BMC 130 via IPMI, enabling the BMC 130 to interact with the system image 140. The first electronic device 110 sends a processing instruction to the BMC 130 via the Redfish interface (S203). This processing instruction instructs the modification of device information, which is stored in the BMC or the BIOS chip of the second electronic device.

[0117] BMC 130 sends processing instructions to mirror system 140 (S204). Mirror system 140 runs an application to modify device information (S205). The first electronic device sends a query instruction to BMC 130 via the Redfish interface (S206), whereby the query instruction instructs BMC to retrieve processing information from the mirror system; the processing information includes processing results and / or processing progress. BMC 130 sends the query instruction to mirror system 140 (S207). BMC 130 retrieves the processing information from the mirror system (S208). BMC 130 sends the processing information to the first electronic device via the Redfish interface (S209). The above method can not only process device information stored in the BIOS chip of the second electronic device, but also enable the first electronic device to process the device information of the second electronic device in the event of a communication failure between the first electronic device 110 and the second electronic device 120 via the IPMI interface.

[0118] Figure 7 This illustration shows a logic diagram of a method for performing white-label operation on at least two second electronic devices according to an embodiment of this application. The method is executed by a first electronic device, such as... Figure 7As shown, the first electronic device acquires the white tag content (S301), which represents the electronic tag and / or BIOS logo to be deleted. The first electronic device determines whether the white tag content includes the BIOS logo (S302). If so, the first electronic device determines the image system file (S304). Specifically, the first electronic device can determine the image system file based on the architecture information of at least two second electronic devices. If the second electronic device is an ARM architecture computing device, the first electronic device determines the image system file to be the first image system file loaded by an electronic device supporting the ARM architecture. The first image system file contains the operating system kernel files and drivers under the ARM architecture. If the second electronic device is an x86 architecture computing device, the first electronic device determines the image system file to be the second image system file loaded by an electronic device supporting the x86 architecture.

[0119] If not, the first electronic device determines whether IPMI is available (S303). Specifically, the first electronic device can attempt to connect to at least two second electronic devices using the IPMI management tool. If all connections are successful and the temperature and / or fan speed of the second electronic devices are obtained, it indicates that IPMI is available. If IPMI is available, the first electronic device sends an IPMI white-label script to at least two second electronic devices via IPMI (S305). The IPMI white-label script includes connection information, white-label instructions, and white-label content. At least two second electronic devices receive the IPMI processing script through their respective BMCs and execute the white-label instructions in the IPMI processing script, deleting the white-label content that needs to be white-labeled from each second electronic device. The first electronic device receives the execution result of the IPMI white-label script (S306), and the process ends (S311). If IPMI is unavailable, the first electronic device determines the image system file (S304).

[0120] The first electronic device sends a mirror system file to at least two second electronic devices via a Redfish interface (S307). Each second electronic device receives the mirror system file through its respective BMC and stores it in its BMC's memory, thereby starting the mirror system using the driver in the mirror system file. After each second electronic device starts its mirror system, the first electronic device sends a white-card processing instruction to the BMCs of the at least two second electronic devices via the Redfish interface (S308). Specifically, the first electronic device starts a Hypertext Transfer Protocol (HTTP) service and sends a white-card instruction to the respective BMCs of the at least two second electronic devices via an HTTP request. The mirror system corresponding to each second electronic device obtains the white-card instruction from its BMC, runs the application based on the white-card content, and executes the white-card instruction. The first electronic device sends a query instruction to the BMCs of the at least two second electronic devices via the Redfish interface (S309). The respective BMCs of each second electronic device forward the query instruction to their respective mirror systems, execute the query instruction, and obtain processing information, including processing results and / or processing progress. The first electronic device obtains the processing information sent by the BMC of each second electronic device (S310). After the mirror system in the second electronic device successfully executes the white card instruction, the first electronic device can delete the mirror system files in each second electronic device through the Redfish interface, and the process ends (S311).

[0121] As can be seen from the above, the first electronic device adaptively selects the white card operation channel according to the content of the white card, which not only enables the first electronic device to perform batch white card operations, but also improves the success rate of white card operations, thereby improving the efficiency of white card operations of the electronic device.

[0122] In summary, this application provides a method for processing device information to improve the processing efficiency of device information in a first electronic device, specifically improving the efficiency of white-label operations on the electronic device. This method, executed by the first electronic device, includes: the first electronic device acquiring a mirror system file and mounting the mirror system file to a second electronic device. The second electronic device supports loading and running the mirror system file, and the mirror system contains an application for modifying device information. The first electronic device sends a processing instruction to the second electronic device, and the second electronic device processes the device information by running the application in the mirror system. The processing instruction instructs the modification of the device information. This method, by mounting the mirror system file to the second electronic device and running the application in the mirror file to perform device information processing operations on the second electronic device, improves the success rate of device information processing, thereby increasing the efficiency of device information processing.

[0123] The foregoing mainly describes the solutions of the embodiments of this application from a methodological perspective. It is understood that, in order to achieve the above functions, the device information processing apparatus includes at least one of the hardware structures and software modules corresponding to each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this application.

[0124] This application embodiment can divide the device information processing apparatus into functional units according to the above method example. For example, each function can be divided into separate functional units, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software functional unit. It should be noted that the unit division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0125] For example, Figure 8 A schematic diagram of the structure of a device information processing apparatus 400 provided in an embodiment of this application is shown. Figure 8 As shown, the device information processing apparatus 400 can be applied to a management computing device, and the device information processing apparatus 400 includes:

[0126] The connection module 410 is used to obtain the image system file and mount the image system file to the second electronic device. The second electronic device supports loading the image system file and running the image system, which contains an application for changing device information.

[0127] The sending module 420 is used to send processing instructions to the second electronic device; the processing instructions are used to instruct changes to device information, and the second electronic device changes the device information by running an application.

[0128] In one possible implementation, the connection module 410 is also used to obtain the architecture information of the second electronic device; and determine the image system file based on the architecture information.

[0129] In one possible implementation, the connection module 410 is also configured to obtain the image system file in the event of an abnormal communication between the first electronic device and the second electronic device via the IPMI interface.

[0130] In one possible implementation, the sending module 420 is further configured to send a query instruction to the second electronic device; the query instruction is used to instruct the acquisition of processing information from the mirror system; the processing information includes processing results and / or processing progress.

[0131] In one possible implementation, the sending module 420 is further configured to, when the first electronic device is communicating normally with the second electronic device via the IPMI interface and the device information is stored in the BMC of the second electronic device, the method further includes:

[0132] The IPMI processing script is sent to the second electronic device via the IPMI interface; the IPMI processing script can be run through the BMC of the second electronic device and modify the device information.

[0133] In one possible implementation, the sending module 420 is also used to initiate a Hypertext Transfer Protocol (HTTP) service to send processing instructions to the respective BMCs of at least two second electronic devices via the Redfish interface.

[0134] In one possible implementation, the device information processing apparatus 400 further includes a receiving module for receiving processing information.

[0135] Optionally, the aforementioned equipment information processing device 400 can be applied to Figure 1 The first electronic device 110 shown implements the above-mentioned Figure 3 The method for processing device information as described herein.

[0136] Both the connection module 410 and the transmission module 420 can be implemented in software or in hardware.

[0137] For example, the implementation of connection module 410 will be described below. Similarly, the implementation of connection module 410 and transmission module 420 can refer to the implementation of connection module 410.

[0138] As an example of a software functional unit, the connectivity module 410 may include code running on a computing instance. The computing instance may include at least one of a physical host (computing device), a virtual machine, or a container. Further, the aforementioned computing instance may be one or more. For example, the connectivity module 410 may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the code may be distributed in the same region or in different regions. Further, the multiple hosts / virtual machines / containers used to run the code may be distributed in the same availability zone (AZ) or in different AZs, each AZ including one or more geographically proximate data centers. Typically, a region may include multiple AZs.

[0139] Similarly, multiple hosts / virtual machines / containers used to run this code can be distributed within the same Virtual Private Cloud (VPC) or across multiple VPCs. Typically, a VPC is set up within a region. Communication between two VPCs within the same region, as well as between VPCs in different regions, requires a communication gateway to be set up within each VPC to enable interconnection between VPCs.

[0140] As an example of a hardware functional unit, the connection module 410 may include at least one computing device, such as a server. Alternatively, the connection module 410 may also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be implemented using a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), generic array logic (GAL), or any combination thereof.

[0141] The multiple computing devices included in the connection module 410 can be distributed in the same region or in different regions. Similarly, the multiple computing devices included in the connection module 410 can be distributed in the same Availability Zone (AZ) or in different AZs. Likewise, the multiple computing devices included in the connection module 410 can be distributed in the same Virtual Private Cloud (VPC) or in multiple VPCs. These multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0142] It should be noted that, in other embodiments, the connection module 410 can be used to execute any step in the device information processing method, and the sending module 420 can be used to execute any step in the device information processing method. The steps implemented by the connection module 410 and the sending module 420 can be specified as needed. The device information processing device 400 can achieve all functions by implementing different steps in the device information processing method through the connection module 410 and the sending module 420 respectively.

[0143] For a detailed description of the above-mentioned optional methods, please refer to the foregoing method embodiments, which will not be repeated here. Furthermore, explanations of any of the above-provided device information processing apparatus 400 and descriptions of its beneficial effects can be found above. Figure 3 The corresponding method implementations will not be described in detail.

[0144] This application also provides a computer-readable storage medium storing instructions that, when executed on a computing device, cause the computing device to perform any implementation scheme and various feasible implementation schemes corresponding to the device information processing method.

[0145] This application also provides a computer program product containing instructions that, when run on a computing device, cause the computing device to perform any implementation scheme and various feasible implementation schemes corresponding to the device information processing method.

[0146] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0147] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0148] This application also provides a chip system, including: a processor coupled to a memory, the memory being used to store programs or instructions, and when the program or instructions are executed by the processor, the chip system enables the methods in any of the above method embodiments.

[0149] Optionally, the chip system may contain one or more processors. These processors can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory.

[0150] Optionally, the chip system may contain one or more memories. The memory may be integrated with the processor or disposed separately from it; this application embodiment does not limit this. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or disposed separately on different chips. This application embodiment does not specifically limit the type of memory or the arrangement of the memory and processor.

[0151] For example, the chip system can be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0152] The electronic devices, computer storage media, or computer program products provided in this application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0153] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0154] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another apparatus, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0155] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units, located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0156] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0157] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to the solution, or all or part of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0158] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for processing equipment information, characterized in that, The method is performed by a first electronic device and includes: Obtain the image system file; The image system file is mounted to a second electronic device; wherein the second electronic device supports loading the image system file and running the image system, and the image system contains an application for modifying device information; A processing instruction is sent to the second electronic device; the processing instruction is used to instruct changes to device information, and the second electronic device changes the device information by running the application.

2. The method according to claim 1, characterized in that, The method further includes: A query command is sent to the second electronic device; the query command is used to instruct the acquisition of processing information from the mirror system; the processing information includes processing results and / or processing progress. Receive the processing information.

3. The method according to claim 1 or 2, characterized in that, The process of obtaining the image system file includes: If the communication between the first electronic device and the second electronic device via the IPMI interface fails, obtain the image system file.

4. The method according to claim 3, characterized in that, When the first electronic device is communicating normally with the second electronic device via the IPMI interface, and the device information is stored in the BMC of the second electronic device, the method further includes: An IPMI processing script is sent to the second electronic device via the IPMI interface; the IPMI processing script can be run through the BMC of the second electronic device and modify device information.

5. The method according to claim 1 or 2, characterized in that, Sending processing instructions to the second electronic device includes: Initiate the Hypertext Transfer Protocol (HTTP) service and send the processing instructions to the BMCs of at least two of the second electronic devices via the Redfish interface.

6. A method for processing equipment information, characterized in that, The method is performed by a second electronic device and includes: Loading and running an image system file; wherein, the image system file is obtained by a first electronic device; the first electronic device is used to mount the image system file to a second electronic device; the image system runs an application for modifying device information; Receive a processing instruction sent by the first electronic device; the processing instruction is used to instruct changes to device information; The device information is changed by running the application.

7. The method according to claim 6, characterized in that, The method further includes: The system receives a query instruction sent by the first electronic device; the query instruction is used to instruct the second electronic device to obtain processing information from the mirror system; the processing information includes processing results and / or processing progress. The processing information is sent to the first electronic device.

8. The method according to claim 6 or 7, characterized in that, The process of loading the image system file and running the image system includes: In the event of an abnormal communication between the first electronic device and the second electronic device via the IPMI interface, the image system file is loaded and the image system is run.

9. The method according to claim 8, characterized in that, When the first electronic device is communicating normally with the second electronic device via the IPMI interface, and the device information is stored in the BMC of the second electronic device, the method further includes: The IPMI processing script sent by the first electronic device is received via the IPMI interface; the IPMI processing script can be run through the BMC of the second electronic device and modify device information.

10. An electronic device, characterized in that, The electronic device includes: a processor and a memory for storing instructions executable by the processor; The processor is configured to execute the instructions, causing the electronic device to perform the device information processing method as described in any one of claims 1-5 or 6-9.

Images