System environment deployment method and electronic equipment

Abstract

The invention discloses a system environment deployment method and electronic equipment. The method and the device are used for realizing automatic deployment of a customized operating system environment, improving deployment efficiency and saving labor cost. The method comprises the steps that FRU information is obtained through a BMC, OS information is determined according to the FRU information, and an OS corresponding to the OS information is installed; obtaining a target component corresponding to the OS according to the FRU information; and updating the to-be-updated component in the OS into the target component.

Description

Technical Field

[0001] The present invention relates to the field of computer software technology, and in particular to a system environment deployment method and electronic equipment. Background Art

[0002] Most of the current system environment deployment methods are for general-purpose operating system system environment deployment, but general-purpose operating systems cannot meet customized system requirements, cannot adapt to customized systems, and cannot deploy test environments for customized systems. General-purpose operating systems are also unable to associate with firmware (FW) versions, driver versions, test tool versions, etc.

[0003] In the current system environment deployment process, the corresponding executive operating system (OS) is usually installed. After the OS is installed, components such as FW and drivers need to be manually updated, which requires human intervention and does not achieve fully automated deployment.

[0004] When it is necessary to meet the requirements of customized OS system environment deployment, it is impossible to automatically adapt specific FW, drivers, testing tools and other components according to the customized OS, and it is impossible to realize automatic deployment of customized operating system environment. Summary of the invention

[0005] The present invention provides a system environment deployment method and electronic equipment, which are used to realize automatic deployment of a customized operating system environment, improve deployment efficiency, and save labor costs.

[0006] In a first aspect, an embodiment of the present invention provides a system environment deployment method, the method comprising:

[0007] Use the BMC to obtain FRU information, determine OS information based on the FRU information, and install the OS corresponding to the OS information;

[0008] Acquire a target component corresponding to the OS according to the FRU information;

[0009] The component to be updated under the OS is updated to the target component.

[0010] This embodiment establishes an association between the OS and the target component, obtains the corresponding target component after the OS is automatically installed, and automatically updates it, thereby achieving full automatic deployment of the system environment, improving deployment efficiency, and saving labor costs.

[0011] As an optional implementation, the method further includes:

[0012] A test tool corresponding to the OS is obtained according to the FRU information, and the test tool is installed.

[0013] This embodiment uses the association relationship between the OS and the test tool to determine the corresponding test tool from the FRU information after the OS is installed, and automatically installs the test tool, thereby realizing automated deployment and installation of the test tool based on the customized system. The automated installation of the test tool is applicable to any operating system, thereby improving the deployment efficiency and universality of the test tool.

[0014] As an optional implementation, after the test tool is installed, the method further includes:

[0015] Debugging the test tool, and determining whether an abnormality occurs in the test tool according to the debugging result;

[0016] If the test tool is abnormal, the abnormal information is output.

[0017] After the test tool is automatically installed, this embodiment can also debug and verify the test tool to check whether an abnormality occurs in the test tool, thereby providing a more comprehensive installation and debugging function for automatically detecting the availability of the test tool.

[0018] As an optional implementation manner, determining OS information according to FRU information and installing OS corresponding to the OS information includes:

[0019] Determine OS information according to the first field of the FRU information;

[0020] The OS corresponding to the OS information is obtained from a PXE resource pool, and the OS is installed.

[0021] This embodiment can obtain a universal or customized OS from a PXE resource pool and install it. This embodiment stores different operating systems in a PXE resource pool, so that when installing different operating systems, the required type of OS can be obtained from one resource pool, thereby automatically installing the OS, thereby improving the universality and versatility of operating system deployment.

[0022] As an optional implementation manner, obtaining the target component corresponding to the OS according to the FRU information includes:

[0023] Determine target component information according to the second field of the FRU information;

[0024] Acquire a target component corresponding to the target component information from a remote warehouse.

[0025] This embodiment can obtain target components such as firmware or drivers from a remote warehouse, and can automatically install different target components, thereby improving the universality and versatility of automatic deployment of firmware or drivers.

[0026] As an optional implementation manner, the acquiring a test tool corresponding to the OS according to the FRU information includes:

[0027] Determine test tool information according to the third field of the FRU information;

[0028] Acquire a test tool corresponding to the test tool information from a remote repository.

[0029] This embodiment can obtain the test tools from the remote warehouse and perform automatic installation and deployment for different test tools, thereby improving the universality and versatility of automatic deployment of test tools for any system.

[0030] As an optional implementation manner, before obtaining the target component or test tool corresponding to the OS, the method further includes:

[0031] Determine current configuration information corresponding to the OS;

[0032] Determine target configuration information corresponding to the OS according to the FRU information;

[0033] If the current configuration information is the same as the target configuration information, a target component or a test tool corresponding to the OS is obtained.

[0034] After installing the OS, this embodiment determines whether the current actual configuration meets the configuration requirements by comparing the current configuration information with the target configuration information, thereby ensuring that the current device configuration is available and meets the configuration requirements when installing the target components or test tools, which can improve the accuracy of automated deployment.

[0035] As an optional implementation, the current configuration information and the target configuration information are determined in the following manner:

[0036] Determine the current configuration information corresponding to the OS according to the current configuration under the OS;

[0037] According to the fourth field of the FRU information, target configuration information corresponding to the OS is determined.

[0038] This embodiment automatically captures the current configuration information of the current configuration and the fourth field of the FRU information to compare whether the current actual configuration is the same as the target configuration, thereby ensuring that the configuration of the current device is available and meets the configuration requirements when installing the target component or test tool, thereby improving the accuracy of automated deployment.

[0039] In a second aspect, an embodiment of the present invention further provides an electronic device, the electronic device comprising a processor and a memory, the memory being used to store a program executable by the processor, the processor being used to read the program in the memory and perform the following steps:

[0040] Use the BMC to obtain FRU information, determine OS information based on the FRU information, and install the OS corresponding to the OS information;

[0041] Acquire a target component corresponding to the OS according to the FRU information;

[0042] The component to be updated under the OS is updated to the target component.

[0043] As an optional implementation, the processor is further configured to execute:

[0044] A test tool corresponding to the OS is obtained according to the FRU information, and the test tool is installed.

[0045] As an optional implementation, after the test tool is installed, the processor is further configured to execute:

[0046] Debugging the test tool, and determining whether an abnormality occurs in the test tool according to the debugging result;

[0047] If the test tool is abnormal, the abnormal information is output.

[0048] As an optional implementation, the processor is specifically configured to execute:

[0049] Determine OS information according to the first field of the FRU information;

[0050] The OS corresponding to the OS information is obtained from a PXE resource pool, and the OS is installed.

[0051] As an optional implementation, the processor is specifically configured to execute:

[0052] Determine target component information according to the second field of the FRU information;

[0053] Acquire a target component corresponding to the target component information from a remote warehouse.

[0054] As an optional implementation, the processor is specifically configured to execute:

[0055] Determine test tool information according to the third field of the FRU information;

[0056] Acquire a test tool corresponding to the test tool information from a remote repository.

[0057] As an optional implementation manner, before obtaining the target component or test tool corresponding to the OS, the processor is further configured to execute:

[0058] Determine current configuration information corresponding to the OS;

[0059] Determine target configuration information corresponding to the OS according to the FRU information;

[0060] If the current configuration information is the same as the target configuration information, a target component or a test tool corresponding to the OS is obtained.

[0061] As an optional implementation manner, the processor is specifically configured to determine the current configuration information and the target configuration information in the following manner:

[0062] Determine the current configuration information corresponding to the OS according to the current configuration under the OS;

[0063] According to the fourth field of the FRU information, target configuration information corresponding to the OS is determined.

[0064] In a third aspect, an embodiment of the present invention further provides a system environment deployment device, the device comprising:

[0065] A system installation module, used to obtain FRU information using the BMC, determine OS information according to the FRU information, and install the OS corresponding to the OS information;

[0066] A component acquisition module, used for acquiring a target component corresponding to the OS according to the FRU information;

[0067] The component updating module is used to update the component to be updated under the OS to the target component.

[0068] As an optional implementation, the device further includes a test installation module for:

[0069] A test tool corresponding to the OS is obtained according to the FRU information, and the test tool is installed.

[0070] As an optional implementation, after the test tool is installed, the device further includes a debugging module for:

[0071] Debugging the test tool, and determining whether an abnormality occurs in the test tool according to the debugging result;

[0072] If the test tool is abnormal, the abnormal information is output.

[0073] As an optional implementation, the system installation module is specifically used for:

[0074] Determine OS information according to the first field of the FRU information;

[0075] The OS corresponding to the OS information is obtained from a PXE resource pool, and the OS is installed.

[0076] As an optional implementation manner, the component acquisition module is specifically used to:

[0077] Determine target component information according to the second field of the FRU information;

[0078] Acquire a target component corresponding to the target component information from a remote warehouse.

[0079] As an optional implementation, the test installation module is specifically used for:

[0080] Determine test tool information according to the third field of the FRU information;

[0081] Acquire a test tool corresponding to the test tool information from a remote repository.

[0082] As an optional implementation manner, before obtaining the target component or test tool corresponding to the OS, the device further includes a judgment module specifically used for:

[0083] Determine current configuration information corresponding to the OS;

[0084] Determine target configuration information corresponding to the OS according to the FRU information;

[0085] If the current configuration information is the same as the target configuration information, a target component or a test tool corresponding to the OS is obtained.

[0086] As an optional implementation manner, the judgment module is specifically used to determine the current configuration information and the target configuration information in the following manner:

[0087] Determine the current configuration information corresponding to the OS according to the current configuration under the OS;

[0088] According to the fourth field of the FRU information, target configuration information corresponding to the OS is determined.

[0089] In a fourth aspect, an embodiment of the present invention further provides a computer storage medium on which a computer program is stored, and when the program is executed by a processor, it is used to implement the steps of any one of the methods described in the first aspect above.

[0090] In a fifth aspect, the present application provides a computer program product, comprising: a computer program code, when the computer program code is run on a computer, the computer executes any one of the methods described in the first aspect.

[0091] These and other aspects of the present application will be more clearly understood in the description of the following embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0092] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0093] Figure 1 A flowchart of a system environment deployment method provided by an embodiment of the present invention;

[0094] Figure 2 A flowchart of a method for automatically deploying a system environment provided by an embodiment of the present invention;

[0095] Figure 3 A flowchart of a system environment deployment method provided by an embodiment of the present invention;

[0096] Figure 4 A schematic diagram of an electronic device provided by an embodiment of the present invention;

[0097] Figure 5 A schematic diagram of a system environment deployment device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0098] In order to make the purpose, technical scheme and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0099] In the embodiments of the present invention, the term "and / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent three situations: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0100] The application scenarios described in the embodiments of the present invention are intended to more clearly illustrate the technical solutions of the embodiments of the present invention, and do not constitute a limitation on the technical solutions provided by the embodiments of the present invention. It is known to those skilled in the art that with the emergence of new application scenarios, the technical solutions provided by the embodiments of the present invention are also applicable to similar technical problems. In the description of the present invention, unless otherwise specified, "multiple" means two or more.

[0101] Before introducing the system environment deployment method provided in the embodiment of the present application, in order to facilitate understanding, the technical background of the embodiment of the present application is first introduced in detail below.

[0102] Most of the current system environment deployment methods are for system environment deployment of general operating systems, but general operating systems cannot meet customized system requirements, cannot adapt to customized systems, and cannot deploy test environments for customized systems. General operating systems are also unable to associate with firmware (FW) versions, driver versions, test tool versions, etc. In the current system environment deployment process, the corresponding executive operating system (OS) is usually installed. After the OS is installed, it is necessary to manually update FW, drivers and other components, which requires manual intervention and does not achieve fully automated deployment. When it is necessary to meet the requirements of customized OS system environment deployment, it is impossible to automatically adapt specific FW, drivers, test tools and other components according to the customized OS, and it is impossible to achieve automatic deployment of customized operating system environment.

[0103] It should be noted that OS refers to the operating system running on the machine (device). It is a computer program that manages and controls computer hardware and software resources. It is the most basic system software that runs directly on the "bare metal". Any other software or system must be supported by the operating system to run. FW is a program written into EPROM (Erasable Programmable Read-Only Memory) or EEPROM (Electrically Erasable Programmable read only memory). Firmware refers to the device "driver" stored inside the device. Through firmware, the operating system can implement the operation of a specific machine according to the standard device driver. For example, optical drives and burners have internal firmware. Firmware is the software that performs the most basic and lowest-level work in a system. In hardware devices, firmware is the soul of the hardware device, because some hardware devices have no other software components except firmware, so firmware determines the function and performance of the hardware device.

[0104] At present, the server test environment deployment method has not achieved complete automatic deployment. In addition, general automated deployment is only for general test models, and there is no test tool deployment method for customized test environments. In other words, there is currently no automatic deployment of the test environment based on a specific OS to match specific component FW, drivers, and different versions of test tools.

[0105] At present, the industry does not have much demand for customized OS. Most of them are general-purpose servers. However, general-purpose servers are not targeted at all and only need to meet the test-as-you-go approach. There is little meaning in automated deployment because changes need to be made after a test is completed. However, there is an increasing demand for customization. As long as a certain model or certain models need to be adapted to the customer system, there is a demand for automatic deployment of customized systems. The previous general-purpose OS could not be associated with the FW, driver version, and test tool version of the component. The customer's customized OS needs to be fully adapted to the customer's production environment, that is, the customer's customized OS-component FW, driver-component, and whole machine test tools need to be strongly bound. Therefore, how to meet the deployment of customized test tools and system environments has become a technical problem that needs to be solved urgently.

[0106] In order to solve the above technical problems, an embodiment of the present application provides a system environment deployment method, the core idea of ​​which is to automatically install the OS through the operation information OS information contained in the FRU (Field Replaceable Unit) information, and obtain the target component corresponding to the OS according to the FRU information, and automatically update the components to be updated under the OS. By establishing an association between the OS and the target component, the corresponding target component is obtained and automatically updated after the OS is automatically installed. That is, after the OS is installed, the driver and firmware corresponding to the OS are automatically updated through the association between the OS and the target component (such as the driver, firmware). Fully automatic deployment of the system environment is achieved, deployment efficiency is improved, and labor costs are saved.

[0107] like Figure 1 As shown, the implementation process of the system environment deployment method provided in this embodiment is as follows:

[0108] Step 100: Obtain FRU information using the BMC, determine OS information based on the FRU information, and install the OS corresponding to the OS information;

[0109] During implementation, after the device is powered on, the BMC is used to automatically capture FRU information, where the FRU information is information written into the BMC chip during the device manufacturing process. Therefore, the BMC is used to obtain the FRU information, and the OS information, including OS name, OS version and other information, is determined from the FRU information. The OS corresponding to the OS information is automatically obtained and the OS is automatically installed.

[0110] The BMC (Baseboard Management Controller) in this embodiment is a dedicated microcontroller embedded in the mainboard of the device, responsible for managing the system and the interface between the management software and the server platform hardware. The BMC provides management functions for the FRU (Field Replaceable Unit) through the IPMI (Intelligent Platform Management Interface) specification, including reading and updating FRU data. In this embodiment, the BMC is used to manage and read the FRU information in the device.

[0111] FRU refers to a device component / part or module that can be replaced or repaired on site. BMC usually maintains FRU information so that it can accurately identify and locate the parts that need to be replaced when the device needs to be replaced or repaired. FRU usually contains the physical component information of the device, and part of this information may include the device's VPD (Virtual Product Data), such as manufacturer, model, serial number, etc. This design can help the management system accurately identify and locate the parts that need to be replaced when the device needs to be replaced or repaired, and provide key device attribute information. For example, FRU information is replaceable device components / parts, such as motherboards, power supplies, fans, etc. The detailed information of these components / parts (such as manufacturer, product number, etc.) is usually stored in non-volatile memory, such as EEPROM. The detailed information of these components can be obtained by reading FRU information through BMC, which helps administrators perform fault diagnosis and maintenance.

[0112] Optionally, the FRU information in this embodiment includes but is not limited to any one or more of the following: model, serial number (SN), configuration information, OS information, FW information, driver information, test tool information, etc.

[0113] Among them, SN refers to the enlistment number, sequence number, number (of equipment documents, etc.), etc. SN is unique and is used to record the identification code of the product. SN is usually a set of characters consisting of numbers, letters, or a combination of both, used to identify and track individual items or equipment. SN is usually assigned by the manufacturer. The SN of each product is unique and can be used to verify the authenticity of the product and provide after-sales service.

[0114] Configuration information includes but is not limited to hard disk information, memory information, network card information, etc. Hard disk information includes but is not limited to hard disk size, hard disk usage, available hard disk size, etc.; memory information includes but is not limited to memory size, memory usage, available memory size, etc.

[0115] OS information includes but is not limited to at least one or more of the OS name, OS version, OS manufacturer, configuration information corresponding to the OS, application scenarios corresponding to the OS, FW information corresponding to the OS, driver information corresponding to the OS, and test tool information corresponding to the OS; FW information includes but is not limited to at least one or more of the FW name, FW version, FW manufacturer, and FW number; driver information includes but is not limited to at least one or more of the driver name, driver version, driver manufacturer, and driver number; test tool information includes but is not limited to at least one or more of the test tool name, test tool version, test tool manufacturer, and test tool number.

[0116] In some embodiments, the FRU information in this embodiment includes but is not limited to the first field, the second field, the third field, the fourth field, etc.; different fields are used to represent different information. The first field is used to represent OS information; the second field is used to represent target component information, which includes but is not limited to firmware, driver and other information; the third field is used to represent test tool information; the fourth field is used to represent configuration information, which includes existing memory information, hard disk information, network card information, etc.

[0117] Among them, FRU information can be expressed as a string of numbers, a string of numbers plus text descriptions, or English, that is, any field in the FRU information can be a combination of numbers, text descriptions, English, etc., or a combination of multiple forms, and the information contained in each field represents a type of information of the device. FRU information can represent the storage of all information of the device. For example, FRU information is expressed as a string of numbers plus text descriptions, where a string of numbers such as: 10101010..., the number represents the OS version that needs to be installed on this device, such as the first number represents Linux or Windows system, the second number represents the release version such as CentOS (a release version of Linux) or Red Hat system, the third number represents the system version of the same manufacturer, such as the seventh or eighth generation system, the fourth number represents the minor version number, and the fifth number represents the kernel version information, and so on. The more numbers in the FRU information, the clearer the OS version used. In theory, there is no upper limit to this level of detail. Similarly, in customized projects, customers will provide the OS used by their own manufacturers. Usually, such OS will record the system version, kernel version and other information more accurately. Therefore, by reading the FRU information, the OS information can be read more accurately to ensure the adaptability and accuracy of the corresponding parts / components. This embodiment fully meets the reading requirements of FRU information in terms of data length reading.

[0118] In some embodiments, this embodiment determines OS information according to FRU information and installs OS corresponding to the OS information through the following steps:

[0119] According to the first field of the FRU information, OS information is determined; an OS corresponding to the OS information is acquired from a PXE resource pool, and the OS is installed.

[0120] During implementation, according to the pre-set reading rules, the first field of the FRU information is read by the BMC, the first field is converted into a language that the script itself can recognize, and the OS information, such as the OS version, OS manufacturer, etc., is determined based on the first field; after the OS information is determined, the OS corresponding to the OS information is obtained from the PXE resource pool, for example, the OS with the same OS manufacturer and OS version is downloaded from the PXE resource pool, and the OS is automatically installed.

[0121] It should be noted that Preboot eXecution Environment (PXE) is a network boot technology that allows computers to obtain operating system images or boot loaders from servers over the network during the boot process, rather than booting from local hard disks or optical drives. PXE technology was developed by Intel to provide a standardized way to boot operating systems without local storage devices. Working in a Client / Server network mode, it supports workstations to download images from remote servers over the network, and thus supports booting operating systems over the network. During the boot process, the terminal requires the server to assign an IP address, and then uses TFTP (Trivial File Transfer Protocol) or MTFTP (Multicast Trivial File Transfer Protocol) protocols to download a boot software package to the local memory for execution. This boot software package completes the basic software settings of the terminal (client), thereby booting the terminal operating system pre-installed in the server. PXE can boot a variety of operating systems.

[0122] PXE resource pool refers to a network resource pool built using PXE (Preboot Execution Environment) technology, which is mainly used to realize remote network booting and operating system installation of computers. PXE resource pool usually includes the following components: PXE server: responsible for providing boot images and installation files, usually needs to configure DHCP (Dynamic Host Configuration Protocol) and TFTP services to allocate IP (Internet Protocol) addresses to PXE clients and transfer boot files. PXE client: a network card that supports PXE technology, which can download boot images from the server through the PXE protocol when booting. Network environment: ensure that the PXE client can access the PXE server through the network. The working principle of PXE resource pool is as follows: when the computer is turned on, the BIOS (Basic Input Output System) calls the PXE client into memory for execution, the PXE client obtains the IP address through the DHCP server, and then downloads the boot image through the TFTP server. The downloaded boot image contains a small operating system environment, which can further download the complete operating system installation package through the network to achieve unattended installation.

[0123] Optionally, the PXE resource pool in this embodiment is used to store a general OS and OS customized by different manufacturers. After determining the OS information required by this device according to the first field, the PXE resource pool is searched to see whether the OS corresponding to the OS information exists. If so, the OS corresponding to the OS information is downloaded directly from the PXE resource pool.

[0124] Step 101, obtaining a target component corresponding to the OS according to the FRU information;

[0125] In implementation, after obtaining the OS and automatically installing the OS, the target components corresponding to the currently installed OS may also be obtained according to the FRU information. The target components include but are not limited to: FW, driver, etc.

[0126] In some embodiments, this embodiment obtains the target component corresponding to the OS according to the FRU information in the following manner:

[0127] According to the second field of the FRU information, target component information is determined; and a target component corresponding to the target component information is acquired from a remote warehouse.

[0128] In implementation, according to the pre-set reading rules, the second field of the FRU information is read by the BMC, the second field is converted into a language that the script itself can recognize, and the target component information is determined according to the second field, including but not limited to determining the firmware information and driver information according to the second field. The firmware corresponding to the firmware information and the driver corresponding to the driver information are downloaded from the remote warehouse. The firmware information includes but is not limited to the firmware name, firmware manufacturer, firmware version, etc.; the driver information includes but is not limited to the driver name, driver manufacturer, driver version, etc.

[0129] Optionally, the remote warehouse in this embodiment can be an FTP (File Transfer Protocol) resource pool, which stores FW, drivers, test tools, etc. required for general OS, as well as FW, drivers, test tools, etc. required for OS customized by different manufacturers. Components in the remote warehouse can be called for automated deployment when necessary. Among them, FTP is a widely used standard protocol for file transfer in the network. As a basic tool in network communication, FTP allows users to interact with the server through client software to upload, download and other file operations. FTP works at the application layer of the OSI (Open System Interconnect) model, and usually uses TCP (Transmission Control Protocol) as its transmission protocol to ensure the reliability and sequentiality of data transmission.

[0130] It should be noted that a remote repository refers to an Internet-based code hosting platform that allows developers to host files in local version repositories to remote servers for storage, so that multiple developers can collaborate on development, share code, and back up code. Common remote repository platforms include GitHub, GitLab, Bitbucket, etc. FTP resource pool is a resource pool used to manage FTP (File Transfer Protocol) connections. Its main goal is to improve the performance and efficiency of applications. Through the FTP resource pool, applications can efficiently manage and reuse FTP connections, reduce the time for connection establishment and disconnection, and thus improve overall performance. The FTP resource pool achieves the reuse of FTP connections by maintaining a connection pool. When an application needs to connect to an FTP server, it obtains an idle connection from the resource pool and returns the connection to the resource pool after use, instead of closing it immediately. In this way, the overhead of connection establishment and disconnection is spread over multiple requests, significantly improving efficiency.

[0131] The system environment deployment method provided in this embodiment can be implemented by a script. The script can be written according to Python and combined with ipmitool (Intelligent Platform Management Interface tool), using the ipmitool fru command (a command line tool for obtaining hardware information), and installing the corresponding OS, FW, driver, testing tools, etc. in a targeted manner according to the read FRU information.

[0132] Optionally, the target component in this embodiment includes but is not limited to: FW, at least one or more of the drive.

[0133] It should be noted that in this embodiment, a correspondence between the OS and the FW, driver, and test tools required by the OS is established. After the OS is installed, the FW, driver, and test tools required by the OS are automatically installed by obtaining the FW, driver, and test tools required by the OS. The system environment can be automatically deployed for any customized OS or general OS. The accuracy of automated deployment can be improved, and the efficiency and universality of automated deployment can be improved.

[0134] Step 102: Update the component to be updated under the OS to the target component.

[0135] Optionally, the components to be updated in this embodiment include but are not limited to firmware, drivers, etc.; if the version of the components to be updated is different from the version of the target component, the components to be updated are updated to the same type of target components, that is, the firmware in the components to be updated is updated to the firmware in the target component, and the driver in the components to be updated is updated to the driver in the target component.

[0136] It should be noted that during the OS installation process, the OS itself already has components to be updated (such as firmware and drivers to be updated), but the versions of the components to be updated may be different from the versions of the target components required by the OS, and are usually the lowest version configurations. Therefore, after obtaining the target components such as firmware and drivers required by the currently installed OS, the low-version components to be updated under the currently installed OS are updated to high-version target components, for example, the low-version firmware under the currently installed OS is updated to high-version firmware, and the low-version driver under the currently installed OS is updated to high-version driver. This makes the target component more compatible with the current OS.

[0137] In some embodiments, this embodiment may also obtain a test tool corresponding to the OS according to the FRU information, and install the test tool.

[0138] In implementation, after the OS is automatically installed and the target components corresponding to the OS are automatically updated, a test tool adapted to the OS may also be automatically installed.

[0139] In some embodiments, the test tool corresponding to the OS is obtained according to the FRU information in the following manner:

[0140] Determine test tool information according to the third field of the FRU information; and obtain a test tool corresponding to the test tool information from a remote warehouse.

[0141] During implementation, according to the pre-set reading rules, the third field of the FRU information is read by the BMC, and the third field is converted into a language that the script itself can recognize. The test tool information is determined based on the third field. The test tool information includes the test tool name, test tool manufacturer, test tool version and other information. The test tool corresponding to the test tool information is downloaded from the remote warehouse. During implementation, it can be determined first whether the test tool corresponding to the test tool information exists in the remote warehouse. If so, the test tool corresponding to the test tool information is downloaded from the remote warehouse.

[0142] In some embodiments, after installing the OS corresponding to the OS information and before acquiring the target component corresponding to the OS, the present embodiment may also confirm the current configuration of the device, as shown below:

[0143] Determine current configuration information corresponding to the OS; determine target configuration information corresponding to the OS according to the FRU information; if the current configuration information is the same as the target configuration information, obtain the target component corresponding to the OS.

[0144] Optionally, the target components include but are not limited to target firmware, target driver, etc.

[0145] In some embodiments, the current configuration information and the target configuration information are determined in the following manner:

[0146] According to the current configuration under the OS, current configuration information corresponding to the OS is determined; according to the fourth field of the FRU information, target configuration information corresponding to the OS is determined.

[0147] During implementation, after installing the OS, in order to verify whether the current actual configuration under the OS is the target configuration corresponding to the OS, this embodiment first captures the current configuration information under the OS, where the current configuration includes but is not limited to the current hard disk, current memory, current network card, etc. The current configuration information includes but is not limited to the current hard disk information, current memory information, current network card information, etc.; then the target configuration information corresponding to the OS is determined based on the FRU information. Specifically, the fourth field of the FRU information is read using the BMC, and the fourth field is converted into a language that can be recognized by the script, and the target configuration information is determined based on the fourth field, that is, the ideal configuration information corresponding to the current OS. Among them, one current configuration corresponds to one target configuration; one current configuration information corresponds to one target configuration information. The target configuration includes but is not limited to: target hard disk, target memory, target network card, etc. The target configuration information includes but is not limited to: target hard disk information, target memory information, target network card information, etc.

[0148] After obtaining the current configuration information and the target configuration information, compare whether the current configuration information and the target configuration information are the same. If the current hard disk information and the target hard disk information are the same, the current memory information and the target memory information are the same, and the current network card information and the target network card information are the same, then obtain the target component corresponding to the OS, that is, obtain the target firmware, target driver, etc. corresponding to the current OS, so as to automatically install the target firmware and target driver.

[0149] In some embodiments, after installing the OS corresponding to the OS information and before obtaining the test tool corresponding to the OS, the present embodiment may also confirm the current configuration of the device, as shown below:

[0150] Determine current configuration information corresponding to the OS; determine target configuration information corresponding to the OS according to the FRU information; if the current configuration information is the same as the target configuration information, obtain a test tool corresponding to the OS.

[0151] During implementation, after installing the OS, in order to verify whether the current actual configuration under the OS is the target configuration corresponding to the OS, this embodiment first captures the current configuration information under the OS, where the current configuration includes but is not limited to the current hard disk, current memory, current network card, etc. The current configuration information includes but is not limited to the current hard disk information, current memory information, current network card information, etc.; then the target configuration information corresponding to the OS is determined based on the FRU information. Specifically, the fourth field of the FRU information is read using the BMC, and the fourth field is converted into a language that can be recognized by the script, and the target configuration information is determined based on the fourth field, that is, the ideal configuration information corresponding to the current OS. Among them, one current configuration corresponds to one target configuration; one current configuration information corresponds to one target configuration information. The target configuration includes but is not limited to: target hard disk, target memory, target network card, etc. The target configuration information includes but is not limited to: target hard disk information, target memory information, target network card information, etc.

[0152] After obtaining the current configuration information and the target configuration information, compare whether the current configuration information and the target configuration information are the same. If the current hard disk information and the target hard disk information are the same, the current memory information and the target memory information are the same, and the current network card information and the target network card information are the same, then obtain the target component corresponding to the OS, that is, obtain the test tool corresponding to the current OS, and automatically install the test tool.

[0153] In some embodiments, after installing the test tool, the method further includes:

[0154] The test tool is debugged, and whether an abnormality occurs in the test tool is determined according to the debugging result; if the test tool is abnormal, abnormality information is output.

[0155] During implementation, after the test tool is installed, the test tool can also be automatically debugged to verify whether the test tool can work normally. When the test tool is abnormal, abnormal information is output to prompt the user to perform manual installation.

[0156] It should be noted that the test tools in this embodiment include but are not limited to at least one of hardware test tools and software test tools. The test tools are used to debug and test the software and / or hardware of the device. Optionally, the test tools in this embodiment include but are not limited to: various stress testing software, cycle scripts, FIO, etc. Wherein FIO refers to FIO (Flexible Input / Output) on the server, which is a command-line-based tool for performance testing and load testing of storage devices. Through FIO, various read and write scenarios and load modes can be simulated to evaluate the performance and stability of storage devices. FIO can create multiple threads on the server and perform I / O operations concurrently. Parameters such as concurrency, queue depth, I / O size, and operation mode can be flexibly set to simulate the load conditions in various actual application scenarios. In performance testing, FIO can be used to test and evaluate performance indicators such as random read and write, sequential read and write, and random mixed read and write of storage devices. In addition, FIO can also output detailed test reports and logs to help users analyze performance bottlenecks and potential problems of storage devices. In short, FIO is a powerful performance testing tool that can help users evaluate and optimize the storage performance of servers.

[0157] It should be noted that the system environment deployment method in this embodiment is applied to a device, which may be a server or other types of electronic devices, and this embodiment does not impose too many limitations on this.

[0158] The system environment deployment method in this embodiment can be implemented through a script. The script automatically reads the FRU information, automatically obtains the OS information, obtains the corresponding OS from the PXE resource pool for automatic installation, and then obtains the target components and test tools corresponding to the OS, and automatically installs the target components and test tools.

[0159] Optionally, the system environment deployment method in this embodiment can be used for batch installation of multiple devices, by reading the OS in the PXE resource pool and the target components and test tools in the remote warehouse through a script, and when multiple devices are powered on at the same time, the FRU information of each device is obtained in parallel through the script, and the corresponding OS, target components and test tools are obtained from the PXE resource pool for automatic installation. Thus, automatic deployment of batch system environments for large quantities of devices is realized.

[0160] In this embodiment, when the current tester is not familiar with the information such as FW, driver and test tools used in this customized OS, there is no need for manual installation. The FRU information can be directly obtained through the BMC, and the customized OS, corresponding FW, driver and test tools, etc. can be determined according to the FRU information, which not only saves the time spent on equipment configuration, but also reduces labor costs and effectively improves deployment efficiency. In addition, when a large number of test tools need to be replaced for some reason, and the information such as component FW and driver needs to be updated, it is only necessary to obtain different test tools, FW and drivers, etc., without confirming the specific configuration of each item, which greatly saves manpower and material resources, and the time consumed is only the process of installing the system.

[0161] This embodiment can not only install the specified operating system as required, but also determine the FW of the system configuration after the corresponding system is installed, confirm the driver, and update the FW, driver, etc. corresponding to the system. After confirming the customized system version, FW version, and driver version, the customized test tool version required by the customer can be installed. It is also possible to install operating systems, component FW, drivers, and test tools in batches. It greatly saves labor costs. When using this system for batch installation, no selection is required and no interactive operations are required. The FW, driver, and test tools corresponding to the operating systems required by different customers are different. The system environment deployment method provided in this embodiment will install the corresponding system version, the corresponding FW, driver, and test tools, etc., regardless of the model of the device, as long as the corresponding operating system (OS) is selected, and the full automation of environment deployment is supported.

[0162] like Figure 2 As shown, this embodiment provides a method for automatic deployment of a system environment, and the specific implementation process of the method is as follows:

[0163] Step 200, power on the device;

[0164] Optionally, the device includes a server.

[0165] Step 201: read OS information from the PXE resource pool, read target component information and test tool information from the remote warehouse, and record OS information, target component information and test tool information;

[0166] Step 202: Obtain FRU information using BMC;

[0167] Step 203: determine OS information according to the first field of the FRU information, determine target component information according to the second field of the FRU information, and determine test tool information according to the third field of the FRU information;

[0168] Step 204a: determining from the recorded OS information that the OS information exists in the PXE resource pool, obtaining the OS corresponding to the OS information from the PXE resource pool, and automatically installing the OS;

[0169] Step 204b: If the OS information is not found in the recorded OS information, the OS installation fails;

[0170] Step 205: Capture the current configuration information corresponding to the OS, and determine the target configuration information corresponding to the OS according to the fourth field of the FRU information;

[0171] Step 206, determine whether the current configuration information and the target configuration information are the same, if yes, execute step 207, otherwise execute step 213;

[0172] Step 207: Determine from the recorded target component information and test tool information that the target component information and the test tool information exist in the remote warehouse, and obtain the target component and the test tool corresponding to the target component information and the test tool information respectively from the remote warehouse;

[0173] Step 208: automatically install the target component and the test tool;

[0174] Step 209, determine whether the installation is complete, if yes, go to step 210, otherwise go to step 212;

[0175] Step 210: Print the version information of the current FW, driver and test tool on the screen;

[0176] Step 211: The installation is displayed as normal, and the screen prints information such as BMC and OS.

[0177] Step 212, displaying that the installation failed, and printing an error message on the screen;

[0178] Step 213: Prompt the user of different configuration information.

[0179] For example, the user is prompted that the hard disks are different, and the screen outputs the specific configuration information of the hard disk inconsistency for manual debugging. If any of the FW, driver and test tools cannot be successfully installed after multiple attempts, the screen prints an error message and prompts the user to install manually.

[0180] This embodiment proposes a system for automatically deploying customized test tools based on PXE resource pool and FTP resource pool. Not only can the customer-specified operating system be installed on the server according to user requirements, but also the system configuration can be determined by FW, driver confirmation, and the corresponding FW and driver can be updated after the corresponding system is installed. After confirming the customized required system version, the FW and driver of the tested component, the customized test tool version required by the customer can be installed, such as FIO and other test tools, cycle scripts, etc. Not only can the required specified operating system, the required component FW, driver, and the required test tool be installed, that is, after providing a required server, everything can be installed through the method provided in this embodiment, and the operating system can be batch installed, component FW, driver, and test tool batch installed through this method. Greatly save labor costs. The method provided in this embodiment does not require any selection during batch installation. Different customers need different versions of component FW, driver, and test tools corresponding to the operating system. No matter what type of server to be tested is, as long as the FRU information is read, the corresponding operating system version will be installed, and the corresponding FW, driver, and test tool of the operating system will be installed accordingly. It can greatly save manpower and improve the testing efficiency of the entire testing cycle.

[0181] like Figure 3 As shown, this embodiment also provides an implementation process of a system environment deployment method, as shown below:

[0182] Step 300: Obtain FRU information using BMC;

[0183] Step 301, determine OS information according to the first field of FRU information;

[0184] Step 302: Obtain the OS corresponding to the OS information from the PXE resource pool, and install the OS;

[0185] Step 303: Determine the current configuration information corresponding to the OS according to the current configuration under the OS, and determine the target configuration information corresponding to the OS according to the fourth field of the FRU information;

[0186] Step 304: determine whether the current configuration information is the same as the target configuration information, if yes, execute step 305, otherwise execute step 311;

[0187] Step 305: Determine the firmware information and the driver information according to the second field of the FRU information;

[0188] Step 306: Obtain the firmware corresponding to the firmware information and the driver corresponding to the driver information from the remote warehouse;

[0189] Step 307: update the current firmware under the OS to the firmware corresponding to the firmware information, and update the current driver to the driver corresponding to the driver information;

[0190] Step 308: Determine the test tool information according to the third field of the FRU information;

[0191] Step 309: Obtain the test tool corresponding to the test tool information from the remote warehouse, and install the test tool;

[0192] Step 310: Debug the test tool and determine whether an abnormality occurs in the test tool according to the debugging result;

[0193] Step 311: Output different configuration information.

[0194] This embodiment can automatically install the OS and the FW, drivers, test tools, etc. of the required components according to the read FRU information. There is no need to check the model, and there is no need to sort out the machine SN before automatic deployment. Since this embodiment determines the FW, driver, and test tool of the component through FRU information, that is, "upstream", it is only necessary to store the FW, driver, and test tool of the component in the remote warehouse, and store the OS in the PXE resource pool. There is no need to spend energy manually selecting which component needs to update the driver, which component needs to update the FW, or which server needs to use which test tool. It can greatly save labor costs and improve the efficiency and versatility of automated deployment.

[0195] Based on the same inventive concept, an embodiment of the present invention further provides an electronic device. Since the electronic device is the electronic device in the method in the embodiment of the present invention, and the principle of solving the problem by the electronic device is similar to that of the method, the implementation of the electronic device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0196] like Figure 4 As shown, the electronic device includes a processor 400 and a memory 401, wherein the memory 401 is used to store a program executable by the processor 400, and the processor 400 is used to read the program in the memory 401 and perform the following steps:

[0197] Use the BMC to obtain FRU information, determine OS information based on the FRU information, and install the OS corresponding to the OS information;

[0198] Acquire a target component corresponding to the OS according to the FRU information;

[0199] The component to be updated under the OS is updated to the target component.

[0200] As an optional implementation manner, the processor 400 is further configured to execute:

[0201] A test tool corresponding to the OS is obtained according to the FRU information, and the test tool is installed.

[0202] As an optional implementation, after the test tool is installed, the processor 400 is further configured to execute:

[0203] Debugging the test tool, and determining whether an abnormality occurs in the test tool according to the debugging result;

[0204] If the test tool is abnormal, the abnormal information is output.

[0205] As an optional implementation manner, the processor 400 is specifically configured to execute:

[0206] Determine OS information according to the first field of the FRU information;

[0207] The OS corresponding to the OS information is obtained from a PXE resource pool, and the OS is installed.

[0208] As an optional implementation manner, the processor 400 is specifically configured to execute:

[0209] Determine target component information according to the second field of the FRU information;

[0210] Acquire a target component corresponding to the target component information from a remote warehouse.

[0211] As an optional implementation manner, the processor 400 is specifically configured to execute:

[0212] Determine test tool information according to the third field of the FRU information;

[0213] Acquire a test tool corresponding to the test tool information from a remote repository.

[0214] As an optional implementation manner, before obtaining the target component or test tool corresponding to the OS, the processor 400 is further configured to execute:

[0215] Determine current configuration information corresponding to the OS;

[0216] Determine target configuration information corresponding to the OS according to the FRU information;

[0217] If the current configuration information is the same as the target configuration information, a target component or a test tool corresponding to the OS is obtained.

[0218] As an optional implementation manner, the processor 400 is specifically configured to determine the current configuration information and the target configuration information in the following manner:

[0219] Determine the current configuration information corresponding to the OS according to the current configuration under the OS;

[0220] According to the fourth field of the FRU information, target configuration information corresponding to the OS is determined.

[0221] Based on the same inventive concept, an embodiment of the present invention also provides a system environment deployment device. Since the device is the device in the method in the embodiment of the present invention, and the principle of solving the problem by the device is similar to that of the method, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0222] like Figure 5 As shown, the device comprises:

[0223] The system installation module 500 is used to obtain FRU information using the BMC, determine OS information according to the FRU information, and install the OS corresponding to the OS information;

[0224] A component acquisition module 501 is used to acquire a target component corresponding to the OS according to the FRU information;

[0225] The component updating module 502 is used to update the component to be updated under the OS to the target component.

[0226] As an optional implementation, the device further includes a test installation module for:

[0227] A test tool corresponding to the OS is obtained according to the FRU information, and the test tool is installed.

[0228] As an optional implementation, after the test tool is installed, the device further includes a debugging module for:

[0229] Debugging the test tool, and determining whether an abnormality occurs in the test tool according to the debugging result;

[0230] If the test tool is abnormal, the abnormal information is output.

[0231] As an optional implementation, the system installation module 500 is specifically used for:

[0232] Determine OS information according to the first field of the FRU information;

[0233] The OS corresponding to the OS information is obtained from a PXE resource pool, and the OS is installed.

[0234] As an optional implementation manner, the component acquisition module 501 is specifically used for:

[0235] Determine target component information according to the second field of the FRU information;

[0236] Acquire a target component corresponding to the target component information from a remote warehouse.

[0237] As an optional implementation, the test installation module is specifically used for:

[0238] Determine test tool information according to the third field of the FRU information;

[0239] Acquire a test tool corresponding to the test tool information from a remote repository.

[0240] As an optional implementation manner, before obtaining the target component or test tool corresponding to the OS, the device further includes a judgment module specifically used for:

[0241] Determine current configuration information corresponding to the OS;

[0242] Determine target configuration information corresponding to the OS according to the FRU information;

[0243] If the current configuration information is the same as the target configuration information, a target component or a test tool corresponding to the OS is obtained.

[0244] As an optional implementation manner, the judgment module is specifically used to determine the current configuration information and the target configuration information in the following manner:

[0245] Determine the current configuration information corresponding to the OS according to the current configuration under the OS;

[0246] According to the fourth field of the FRU information, target configuration information corresponding to the OS is determined.

[0247] Based on the same inventive concept, an embodiment of the present disclosure provides a computer storage medium, the computer storage medium includes: a computer program code, when the computer program code is executed on a computer, the computer executes any of the system environment deployment methods discussed above. Since the principle of solving the problem by the above computer storage medium is similar to that of the system environment deployment method, the implementation of the above computer storage medium can refer to the implementation of the method, and the repeated parts will not be repeated.

[0248] In the specific implementation process, the computer storage medium may include: Universal Serial Bus Flash Drive (USB), mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, and other storage media that can store program codes.

[0249] Based on the same inventive concept, the embodiment of the present disclosure also provides a computer program product, which includes: computer program code, when the computer program code is run on a computer, the computer executes any of the system environment deployment methods discussed above. Since the principle of solving the problem by the above computer program product is similar to that of the system environment deployment method, the implementation of the above computer program product can refer to the implementation of the method, and the repeated parts will not be repeated.

[0250] The computer program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more conductors, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0251] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) containing computer-usable program code.

[0252] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that has the functions specified in one or more boxes.

[0253] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0254] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0255] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A system environment deployment method, characterized in that: The method includes: Use the BMC to obtain FRU information, determine OS information based on the FRU information, and install the OS corresponding to the OS information; Acquire a target component corresponding to the OS according to the FRU information; The component to be updated under the OS is updated to the target component.

2. The method according to claim 1, characterized in that: The method further includes: A test tool corresponding to the OS is obtained according to the FRU information, and the test tool is installed.

3. The method according to claim 2, characterized in that After installing the test tool, the method further includes: Debugging the test tool, and determining whether an abnormality occurs in the test tool according to the debugging result; If the test tool is abnormal, the abnormal information is output.

4. The method according to claim 1, characterized in that: The determining of OS information according to the FRU information and installing the OS corresponding to the OS information includes: Determine OS information according to the first field of the FRU information; The OS corresponding to the OS information is obtained from a PXE resource pool, and the OS is installed.

5. The method according to claim 1, characterized in that: The step of obtaining a target component corresponding to the OS according to the FRU information includes: Determine target component information according to the second field of the FRU information; Acquire a target component corresponding to the target component information from a remote warehouse.

6. The method according to claim 2, characterized in that The step of obtaining a test tool corresponding to the OS according to the FRU information includes: Determine test tool information according to the third field of the FRU information; Acquire a test tool corresponding to the test tool information from a remote repository.

7. The method according to claim 1 or 2, characterized in that: Before acquiring the target component or test tool corresponding to the OS, the method further includes: Determine current configuration information corresponding to the OS; Determine target configuration information corresponding to the OS according to the FRU information; If the current configuration information is the same as the target configuration information, a target component or a test tool corresponding to the OS is obtained.

8. The method according to claim 7, characterized in that Determine the current configuration information and the target configuration information in the following ways: Determine the current configuration information corresponding to the OS according to the current configuration under the OS; According to the fourth field of the FRU information, target configuration information corresponding to the OS is determined.

9. An electronic device, characterized in that: The electronic device comprises a processor and a memory, wherein the memory is used to store a program executable by the processor, and the processor is used to read the program in the memory and execute the steps of any one of the methods of claims 1 to 8.

10. A computer storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

Images