Operating system version matching method and device, computer equipment and storage medium

Abstract

The invention relates to an operating system version matching method and device, computer equipment and a storage medium. According to the method, the target server node can be automatically matched with the self-developed operating system version through the corresponding relation between the server product model and the operating system version, the pre-installed guide file of the server node is generated, and the starting menu item is generated according to the pre-installed guide file to complete automatic pre-installation of the self-developed operating system. The situation that the operating system cannot be installed due to the fact that the operating system is not matched with the model of the server during installation is avoided, the self-developed operating system is automatically matched with the model of the server product, the maintenance cost is reduced, and management of various operating system versions is facilitated.

Description

Technical Field

[0001] The present application relates to the field of server technology, and in particular to an operating system version matching method, device, computer equipment and storage medium. Background Art

[0002] As the community enterprise operating system (Cent OS) stops updating and vulnerabilities are no longer fixed, many after-sales problems caused by incompatibility between third-party operating systems and server hardware are becoming increasingly prominent. Developing self-developed operating systems is the general trend.

[0003] Server products need to be installed with self-developed operating systems before leaving the factory. This requires that each server be pre-installed with a self-developed operating system. However, there are many server product models, and different servers have different hardware product models. The operating system's adaptability to the hardware is also different, which makes it impossible to install the same version of the operating system. This means that the self-developed operating system will have multiple versions. How to systematically and correctly maintain server product models and operating system versions is an urgent problem that needs to be solved in the server product production process. Summary of the invention

[0004] Based on this, an operating system version matching method, device, computer equipment and storage medium are provided, which can achieve the adaptation of the operating system version to the server product model, so as to solve the technical problem of how to match the server product model when installing the self-developed operating system when it is incompatible with the server model during installation, resulting in the inability to install the same version of the operating system and the existence of multiple versions of the self-developed operating system.

[0005] In one aspect, a method for matching operating system versions is provided, the method comprising:

[0006] Acquire an operating system version that matches the server product model, and construct a version configuration data structure that matches the server product model and the operating system version;

[0007] Constructing a version characteristic data structure for each operating system version, wherein the version characteristic data structure includes an automatic installation file, a system image standard path, a kernel file, and a system image extension file;

[0008] Building a pre-start execution environment server for providing a server node with a download network file, and storing the version characteristic data structure as a network file on the pre-start execution environment server;

[0009] In response to the target server node accessing the pre-boot execution environment server, a network file matching the target server node is identified according to the version configuration data structure and a pre-installed boot file is downloaded and generated, and a boot menu item is generated according to the pre-installed boot file.

[0010] In one embodiment, constructing a version configuration data structure that matches the server product model with the operating system version includes:

[0011] Obtain the hardware information corresponding to the server product model, and obtain the supported operating system version based on the hardware information;

[0012] Get the name of the server product model, get the name of the operating system version, and use {name of the server product model: name of the server product model} as the version configuration data structure.

[0013] In one embodiment, constructing a version characteristic data structure for each operating system version includes:

[0014] Set a data table, the header of which includes version, KS file, ISO path, kernel file and Img file;

[0015] Fill in the name of the operating system version corresponding to the version, fill in the name of the automatic installation file corresponding to the KS file, fill in the system image standard path corresponding to the ISO path, fill in the name of the kernel file corresponding to the kernel file, and fill in the name of the system image extension file corresponding to the Img file;

[0016] The filled data in the data table is converted into a version characteristic data structure corresponding to each operating system version.

[0017] In one embodiment, the step of building a pre-boot execution environment server for providing a server node with a network file for downloading, and storing the version characteristic data structure as a network file on the pre-boot execution environment server includes:

[0018] Building a pre-startup execution environment server, and storing the version characteristic data structure as a network file on the pre-startup execution environment server corresponding to the version configuration data structure;

[0019] Deploying a hypertext transfer protocol service and a file transfer protocol service on the pre-start execution environment server to provide network file downloading;

[0020] Deploy a dynamic host configuration protocol service on the pre-boot execution environment server to allocate an Internet Protocol address to a server node accessing the network;

[0021] A network file system service is deployed on the pre-start execution environment server to authorize server nodes connected to the network to access network files.

[0022] In one embodiment, in response to the target server node accessing the pre-boot execution environment server, identifying a network file matching the target server node according to the version configuration data structure and downloading and generating a pre-installed boot file, and generating a boot menu item according to the pre-installed boot file includes:

[0023] Real-time detection of the network of the pre-start execution environment server to determine whether there is a target server node applying for network access;

[0024] If there is a target server node applying for access to the network, an Internet Protocol address is allocated to the target server node accessing the network through the dynamic host configuration protocol service;

[0025] After the target server node is connected to the pre-start execution environment server, identifying the target hardware product model of the target server node;

[0026] Acquire a target operating system version that matches the target hardware product model according to the version configuration data structure;

[0027] Determining whether there is a network file corresponding to the target operating system version in the version characteristic data structure stored in the pre-boot execution environment server;

[0028] If it exists, download the network file corresponding to the target operating system version through the hypertext transfer protocol service and the file transfer protocol service; if it does not exist, download the network file corresponding to the preset default operating system version through the hypertext transfer protocol service and the file transfer protocol service;

[0029] Generate a pre-installed boot file from the acquired network file;

[0030] Generate a startup menu item according to the preinstalled boot file.

[0031] In one embodiment, the operating system version matching method further includes:

[0032] In response to generating the startup menu item, the target server node is restarted, and an operating system is installed on the target server node according to the startup menu item.

[0033] In one embodiment, the operating system version matching method further includes:

[0034] In response to the target server node successfully installing the operating system, the server product model, product serial number, installed operating system version and installation time are recorded to form an operating system version data set;

[0035] The operating system version data set is regularly analyzed to count the pre-installed amount of the operating system installed on the server node and the distribution data of each operating system version, and to generate operating system usage and user installation preference reports.

[0036] On the other hand, a device for matching operating system versions is provided, the device comprising:

[0037] A version configuration data structure building module is used to obtain an operating system version that matches the server product model and build a version configuration data structure that matches the server product model and the operating system version;

[0038] A version characteristic data structure construction module is used to construct a version characteristic data structure of each operating system version, wherein the version characteristic data structure includes an automatic installation file, a system image standard path, a kernel file, and a system image extension file;

[0039] Building a pre-startup execution environment server module, used for building a pre-startup execution environment server for providing a server node with a download network file, and storing the version characteristic data structure as a network file on the pre-startup execution environment server;

[0040] A startup menu item generation module is used to respond to the target server node accessing the pre-start execution environment server, identify the network file matching the target server node according to the version configuration data structure and download and generate a pre-installed boot file, and generate a startup menu item according to the pre-installed boot file.

[0041] In another aspect, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the following steps are implemented:

[0042] Acquire an operating system version that matches the server product model, and construct a version configuration data structure that matches the server product model and the operating system version;

[0043] Constructing a version characteristic data structure for each operating system version, wherein the version characteristic data structure includes an automatic installation file, a system image standard path, a kernel file, and a system image extension file;

[0044] Building a pre-start execution environment server for providing a server node with a download network file, and storing the version characteristic data structure as a network file on the pre-start execution environment server;

[0045] In response to the target server node accessing the pre-boot execution environment server, a network file matching the target server node is identified according to the version configuration data structure and a pre-installed boot file is downloaded and generated, and a boot menu item is generated according to the pre-installed boot file.

[0046] In another aspect, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0047] Acquire an operating system version that matches the server product model, and construct a version configuration data structure that matches the server product model and the operating system version;

[0048] Constructing a version characteristic data structure for each operating system version, wherein the version characteristic data structure includes an automatic installation file, a system image standard path, a kernel file, and a system image extension file;

[0049] Building a pre-start execution environment server for providing a server node with a download network file, and storing the version characteristic data structure as a network file on the pre-start execution environment server;

[0050] In response to the target server node accessing the pre-boot execution environment server, a network file matching the target server node is identified according to the version configuration data structure and a pre-installed boot file is downloaded and generated, and a boot menu item is generated according to the pre-installed boot file.

[0051] The above-mentioned operating system version matching method, device, computer equipment and storage medium realize automatic matching of the self-developed operating system version of the target server node and generate a pre-installed boot file for the server node through the correspondence between the server product model and the operating system version, and complete the automatic pre-installation of the self-developed operating system based on the generated startup menu item based on the pre-installed boot file, thereby avoiding the situation where the operating system is incompatible with the server model during installation, resulting in the inability to install, and realizing automatic matching of the self-developed operating system with the server product model, reducing maintenance costs and facilitating the management of various operating system versions. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. 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 creative work.

[0053] Figure 1 This is an application environment diagram of the operating system version matching method in one embodiment of the present application;

[0054] Figure 2 A flowchart of an operating system version matching method in one embodiment of the present application;

[0055] Figure 3 A logic diagram of an operating system version matching method in one embodiment of the present application;

[0056] Figure 4 A flowchart of the steps of constructing a version configuration data structure that matches the server product model with the operating system version in one embodiment of the present application;

[0057] Figure 5 A flowchart of the steps of constructing a version characteristic data structure for each operating system version in one embodiment of the present application;

[0058] Figure 6 A flowchart of a step of building a pre-startup execution environment server for providing a server node with a network file for downloading the network file in one embodiment of the present application, and storing the version characteristic data structure as a network file on the pre-startup execution environment server;

[0059] Figure 7 This is a structural block diagram of an operating system version matching device in one embodiment of the present application;

[0060] Figure 8 This is a diagram of the internal structure of a computer device in one embodiment of the present application. DETAILED DESCRIPTION

[0061] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0062] As described in the background technology, before the development of this system, the version of the self-developed operating system pre-installed in the server product was the same, and there was no coexistence of multiple versions. Since a single version is not compatible with all hardware configurations, there have been cases in which the pre-installation of a self-developed operating system on a server product failed during laboratory testing and factory production. This also reflects from the side that the self-developed operating system needs to be adapted to different hardware and different server products, so there are multiple versions of the self-developed operating system. The pre-installation of the self-developed operating system can be achieved through the PXE environment in the factory LAN. Among them, PXE (preboot execute environment) is a technology developed by Intel, which works in a client / server network mode, supports workstations to download images from remote servers through the network, and thus supports starting the operating system through the network.

[0063] The current server products are pre-installed with the same self-developed operating system version, and there are no coexistence of multiple versions. Since a single version is not compatible with all hardware configurations, there have been cases where the pre-installation of the self-developed operating system on a certain product model failed during laboratory testing and factory production. The self-developed operating system cannot be pre-installed on the failed product model, which cannot meet the company's strategic requirements. In addition, a single version of the self-developed operating system cannot meet the needs of all users. When fixing vulnerabilities or security issues, all users may be affected. In addition, a single version of the self-developed operating system will also cause the product to lack competitiveness.

[0064] To solve the above problems, an operating system version matching method is creatively proposed in an embodiment of the present invention, which aims to manage different versions of self-developed operating systems, manage the correspondence between different server product models and self-developed operating system versions, automatically match the self-developed operating system version according to the correspondence and generate a pre-installed boot file for the server node, complete the automatic pre-installation of the self-developed operating system based on the pre-installed boot file, and generate an archival record of the pre-installation information of the server node and the self-developed operating system version.

[0065] The operating system version matching method provided in this application can be applied to Figure 1 In the application environment shown in FIG. 1 , the terminal 102 communicates with the server 104 through a network. The terminal 102 may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, and portable wearable devices, and the server 104 may be implemented as an independent server or a server cluster composed of multiple servers. The terminal 102 is a server product, and the server 104 is a cloud platform for installing an operating system as a web maintenance tab.

[0066] In one embodiment, Figure 2 As shown, a method for matching operating system versions is provided, and the method is applied to Figure 1 Taking the server 104 in the example as an example, the following steps are included:

[0067] Step S1, obtaining an operating system version that matches a server product model, and constructing a version configuration data structure that matches the server product model with the operating system version;

[0068] Step S2, constructing a version characteristic data structure of each operating system version, wherein the version characteristic data structure includes automatic installation files, system image standard paths, kernel files, and system image extension files;

[0069] Step S3, building a pre-start execution environment server for providing a server node with a download network file, and storing the version characteristic data structure as a network file on the pre-start execution environment server;

[0070] Step S4, in response to the target server node accessing the pre-boot execution environment server, identifying the network file matching the target server node according to the version configuration data structure and downloading and generating a pre-installed boot file, and generating a boot menu item according to the pre-installed boot file.

[0071] Among them, Figure 3 As shown, the operating system is a self-developed operating system, and the self-developed operating system is preferably called KeyarchOS. This application can effectively manage and pre-install different versions of self-developed operating systems. It allows automatic identification of product models of different target server nodes, and selects the adapted self-developed operating system version accordingly. This automated process greatly reduces the need for manual intervention and improves the efficiency and consistency of the production line. By keeping a record of the pre-installed self-developed operating system version for each server node, the system can accurately count the pre-installed quantity of various versions and their distribution. This provides important data support for enterprises, enables in-depth understanding of product usage and market feedback, and facilitates more accurate production planning and product optimization.

[0072] like Figure 4 As shown, in this embodiment, the version configuration data structure for building the server product model to match the operating system version includes:

[0073] Step S11, obtaining hardware information corresponding to the server product model, and obtaining the supported operating system version according to the hardware information;

[0074] Step S12, obtaining the name of the server product model, obtaining the name of the operating system version, and using {name of the server product model: name of the server product model} as the version configuration data structure.

[0075] Among them, the version configuration data structure that defines the correspondence between product models and self-developed operating system versions, and the web maintenance tab is developed. The format is as follows:

[0076]

[0077] like Figure 5 As shown, in this embodiment, the version characteristic data structure of each operating system version is constructed including:

[0078] Step S21, setting a data table, wherein the header of the data table includes version, KS file, ISO path, kernel file and Img file;

[0079] Step S22, fill in the name of the operating system version corresponding to the version, fill in the name of the automatic installation file corresponding to the KS file, fill in the system image standard path corresponding to the ISO path, fill in the name of the kernel file corresponding to the kernel file, and fill in the name of the system image extension file corresponding to the Img file;

[0080] Step S23, converting the filled data in the data table into a version characteristic data structure corresponding to each operating system version.

[0081] The format of the data table is shown in Table 1.

[0082] Table 1

[0083] Version KS File ISO Path Kernel Files Img file

[0084] The KS file refers to the file that can be installed automatically. KS is actually Kickstart, a fast customized installation method developed by Red Hat.

[0085] ".img" files are often called disk image files or disk image files. It is essentially a binary file that contains file system structures and data and can be considered a copy of a complete disk or disk partition. Img files can be used to create, copy, restore or back up disk partitions.

[0086] Based on the version feature data structure, develop and maintain web tabs in the following format:

[0087]

[0088] like Figure 6 As shown, in this embodiment, the pre-start execution environment server for providing a server node with a network file for downloading is established, and the version characteristic data structure is stored as a network file on the pre-start execution environment server, including:

[0089] Step S31, building a pre-startup execution environment server, and storing the version characteristic data structure as a network file on the pre-startup execution environment server corresponding to the version configuration data structure;

[0090] Step S32, deploying a hypertext transfer protocol service and a file transfer protocol service on the pre-start execution environment server to provide network file downloading;

[0091] Step S33, deploying a dynamic host configuration protocol service on the pre-boot execution environment server to allocate an Internet Protocol address to a server node accessing the network;

[0092] Step S34, deploying a network file system service on the pre-start execution environment server to authorize server nodes connected to the network to access network files.

[0093] Among them, the hypertext transfer protocol service is referred to as http service, the file transfer protocol service is referred to as ftp service, the dynamic host configuration protocol service is referred to as dhcp service, and the network file system service is referred to as nfs service.

[0094] In this embodiment, in response to the target server node accessing the pre-boot execution environment server, identifying a network file matching the target server node according to the version configuration data structure and downloading and generating a pre-installed boot file, and generating a boot menu item according to the pre-installed boot file includes:

[0095] Real-time detection of the network of the pre-start execution environment server to determine whether there is a target server node applying for network access;

[0096] If there is a target server node applying for access to the network, an Internet Protocol address is allocated to the target server node accessing the network through the dynamic host configuration protocol service;

[0097] After the target server node is connected to the pre-start execution environment server, identifying the target hardware product model of the target server node;

[0098] Acquire a target operating system version that matches the target hardware product model according to the version configuration data structure;

[0099] Determining whether there is a network file corresponding to the target operating system version in the version characteristic data structure stored in the pre-boot execution environment server;

[0100] If it exists, download the network file corresponding to the target operating system version through the hypertext transfer protocol service and the file transfer protocol service; if it does not exist, download the network file corresponding to the preset default operating system version through the hypertext transfer protocol service and the file transfer protocol service;

[0101] Generate a pre-installed boot file from the acquired network file;

[0102] Generate a startup menu item according to the preinstalled boot file.

[0103] It is understandable that when the network file corresponding to the target operating system version does not exist in the version characteristic data structure stored in the pre-boot execution environment server, the operating system version matching method includes:

[0104] Obtaining the hardware configuration information of the target server node, and searching for automatic installation files, system image standard paths, kernel files, and system image extension files corresponding to all operating system versions supported for installation on each hardware according to the hardware configuration information;

[0105] Analyze the compatibility of the automatic installation file, the system image standard path, the kernel file, and the system image extension file corresponding to the hardware configuration information of the target server node, find out the latest version of the automatic installation file, the system image standard path, the kernel file, and the system image extension file that can be adapted for installation, and download them;

[0106] Generate a pre-installed boot file from the downloaded automatic installation file, system image standard path, kernel file and system image extension file;

[0107] Generate a startup menu item according to the preinstalled boot file, restart the target server node, and install the operating system on the target server node according to the startup menu item;

[0108] Determining whether the installed operating system runs stably in the target server node;

[0109] If the operation is stable, the target server node is associated with the downloaded automatic installation file, the system image standard path, the kernel file and the system image extension file, added to the version characteristic data structure, and stored in the pre-start execution environment server;

[0110] If it cannot run stably, the network file corresponding to the preset default operating system version is downloaded through the hypertext transfer protocol service and the file transfer protocol service.

[0111] This application automatically adapts the automatic installation files, system image standard paths, kernel files and system image extension files of the new model of the target server node by retrieving historical version data, and can form corresponding network files to facilitate the automatic installation of subsequent repeated versions. It has the function of automatically deploying the latest version of the operating system version, saving manual input.

[0112] Specifically, when the server node is connected to the network, the main program uses the tool ipmitool to automatically identify the product model of the server node motherboard, and then obtains the operating system version according to the above. If the product model has no corresponding operating system version, the preset default operating system version is obtained; next, the defined version characteristics are obtained, and the main program gives the obtained operating system version characteristics to the pre-installed boot file generation module to generate the corresponding boot menu items.

[0113] Wherein, 100.10.0.10 is set to be the IP address of the PXE server. As shown in Table 1, the name of the operating system version is KOS5.8-SP1-U2 corresponding to the version, the name of the automatic installation file is KOS5.8-SP1-U2_x86.20240226.cfg corresponding to the KS file, the system image standard path is KOS5.8-SP1-U2_x86.20240226 corresponding to the ISO path, the kernel file name is vmlinuz-5.10.134-15.2.15.kos5.x86_64 corresponding to the kernel file, and the name of the system image extension file is initrd-5.10.134-15.2.15.kos5.x86_64.img corresponding to the Img file. For example:

[0114] KOS5.8-SP1-U2

[0115] kernel

[0116] tftp: / / 100.10.0.10 / KOS5.8-SP1-U2_x86.20240226 / vmlinuz-5.10.134-15.2.15.kos5.x86_64initrd=initrd-5.10.134-15.2.15.kos5.x86_64.img

[0117] ksdevice=link

[0118] inst.repo=http: / / 100.10.0.10 / KOS5.8-SP1-U2_x86.20240226

[0119] ks=http: / / 100.10.0.10 / KOS5.8-SP1-U2_x86.20240226.cfg

[0120] initrd

[0121] tftp: / / 100.10.0.10 / KOS5.8-SP1-U2_x86.20240226 / initrd-5.10.134-15.2.15.kos5.x86_64.img

[0122] boot.

[0123] like Figure 2 As shown, in this embodiment, the operating system version matching method further includes:

[0124] Step S5: in response to generating the startup menu item, restarting the target server node, and installing the operating system on the target server node according to the startup menu item.

[0125] like Figure 2 As shown, in this embodiment, the operating system version matching method further includes:

[0126] Step S6, in response to the target server node successfully installing the operating system, recording the server product model, product serial number, installed operating system version and installation time to form an operating system version data set;

[0127] Step S7, regularly analyzing the operating system version data set, counting the pre-installed amount of the operating system installed on the server node and the distribution data of each operating system version, and generating an operating system usage and user installation preference report.

[0128] Taking the server product NFxxxxxx as an example, after the factory received the upgraded version of the EC (an engineering process in the manufacturing industry) file, it added or updated the maintenance data on the developed web maintenance tab, and the self-developed operating system version corresponding to the NFxxxxxx product was upgraded to KOS5.8-SP1-U2.

[0129] If the self-developed operating system version KOS5.8-SP1-U2 is a new version, then the version characteristics of this version need to be maintained. If it has been maintained before, there is no need to change it. After the product model, self-developed operating system version, and self-developed operating system version characteristics are determined, the NFxxxxxx server node will be connected to the PXE pre-installed network after completing the factory aging test. It will automatically parse the self-developed operating system version characteristics that need to be installed, further generate pre-installed boot menu items, and record the pre-installed self-developed operating system version information. By comparison, the difference in version characteristics before and after the upgrade can be seen. Further, the earliest record of the new version pre-installation time can be determined, and the approximate time of the new version upgrade can be inferred.

[0130] In the above operating system version matching method, the correspondence between the server product model and the operating system version is used to realize automatic matching of the target server node with the self-developed operating system version and generate a pre-installed boot file for the server node. The startup menu item is generated according to the pre-installed boot file to complete the automatic pre-installation of the self-developed operating system, thereby avoiding the situation where the operating system is incompatible with the server model during installation, resulting in the inability to install. The self-developed operating system is automatically matched to the server product model, which reduces maintenance costs and facilitates the management of various operating system versions.

[0131] It should be understood that although Figure 2-Figure 6The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 2-Figure 6 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0132] In one embodiment, Figure 7 As shown, an operating system version matching device 10 is provided, including: a version configuration data structure building module 1, a version characteristic data structure building module 2, a pre-startup execution environment server building module 3, and a startup menu item generating module 4.

[0133] The version configuration data structure building module 1 is used to obtain an operating system version that matches the server product model, and build a version configuration data structure that matches the server product model and the operating system version.

[0134] The version characteristic data structure building module 2 is used to build a version characteristic data structure of each operating system version, and the version characteristic data structure includes automatic installation files, system image standard paths, kernel files and system image extension files.

[0135] The module 3 for building a pre-boot execution environment server is used to build a pre-boot execution environment server for providing a server node with a download network file, and the version characteristic data structure is stored as a network file on the pre-boot execution environment server.

[0136] The startup menu item generating module 4 is used for responding to the target server node accessing the pre-startup execution environment server, identifying the network file matching the target server node according to the version configuration data structure and downloading and generating a pre-installed boot file, and generating a startup menu item according to the pre-installed boot file.

[0137] In this embodiment, the construction of a version configuration data structure that matches the server product model with the operating system version includes:

[0138] Obtain the hardware information corresponding to the server product model, and obtain the supported operating system version based on the hardware information;

[0139] Get the name of the server product model, get the name of the operating system version, and use {name of the server product model: name of the server product model} as the version configuration data structure.

[0140] In this embodiment, the construction of the version characteristic data structure of each operating system version includes:

[0141] Set a data table, the header of which includes version, KS file, ISO path, kernel file and Img file;

[0142] Fill in the name of the operating system version corresponding to the version, fill in the name of the automatic installation file corresponding to the KS file, fill in the system image standard path corresponding to the ISO path, fill in the name of the kernel file corresponding to the kernel file, and fill in the name of the system image extension file corresponding to the Img file;

[0143] The filled data in the data table is converted into a version characteristic data structure corresponding to each operating system version.

[0144] In this embodiment, the building of a pre-boot execution environment server for providing a server node with a network file for downloading, and storing the version characteristic data structure as a network file on the pre-boot execution environment server includes:

[0145] Building a pre-startup execution environment server, and storing the version characteristic data structure as a network file on the pre-startup execution environment server corresponding to the version configuration data structure;

[0146] Deploying a hypertext transfer protocol service and a file transfer protocol service on the pre-start execution environment server to provide network file downloading;

[0147] Deploy a dynamic host configuration protocol service on the pre-boot execution environment server to allocate an Internet Protocol address to a server node accessing the network;

[0148] A network file system service is deployed on the pre-start execution environment server to authorize server nodes connected to the network to access network files.

[0149] In this embodiment, in response to the target server node accessing the pre-boot execution environment server, identifying a network file matching the target server node according to the version configuration data structure and downloading and generating a pre-installed boot file, and generating a boot menu item according to the pre-installed boot file includes:

[0150] Real-time detection of the network of the pre-start execution environment server to determine whether there is a target server node applying for network access;

[0151] If there is a target server node applying for access to the network, an Internet Protocol address is allocated to the target server node accessing the network through the dynamic host configuration protocol service;

[0152] After the target server node is connected to the pre-start execution environment server, identifying the target hardware product model of the target server node;

[0153] Acquire a target operating system version that matches the target hardware product model according to the version configuration data structure;

[0154] Determining whether there is a network file corresponding to the target operating system version in the version characteristic data structure stored in the pre-boot execution environment server;

[0155] If it exists, download the network file corresponding to the target operating system version through the hypertext transfer protocol service and the file transfer protocol service; if it does not exist, download the network file corresponding to the preset default operating system version through the hypertext transfer protocol service and the file transfer protocol service;

[0156] Generate a pre-installed boot file from the acquired network file;

[0157] Generate a startup menu item according to the preinstalled boot file.

[0158] In this embodiment, if Figure 7 As shown, the operating system version matching device 10 also includes an operating system installation module 5.

[0159] The operating system installation module 5 is used to: in response to generating a startup menu item, restart the target server node, and install the operating system on the target server node according to the startup menu item.

[0160] In this embodiment, if Figure 7 As shown, the operating system version matching device 10 also includes: a data statistical analysis module 6.

[0161] The data statistics and analysis module 6 is used to: in response to the successful installation of the operating system on the target server node, record the server product model, product sequence, installed operating system version and installation time to form an operating system version data set; regularly analyze the operating system version data set, count the pre-installed amount of the operating system installed on the server node and the distribution data of each operating system version, and generate an operating system usage and user installation preference report.

[0162] In the above-mentioned operating system version matching device, the correspondence between the server product model and the operating system version is used to realize automatic matching of the target server node with the self-developed operating system version and generate a pre-installed boot file for the server node. The startup menu item is generated according to the pre-installed boot file to complete the automatic pre-installation of the self-developed operating system, thereby avoiding the situation where the operating system is incompatible with the server model during installation, resulting in the inability to install. The self-developed operating system is automatically matched to the server product model, which reduces maintenance costs and facilitates the management of various operating system versions.

[0163] For the specific definition of the operating system version matching device, please refer to the definition of the operating system version matching method above, which will not be repeated here. Each module in the above operating system version matching device can be implemented in whole or in part by software, hardware and a combination thereof. The above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0164] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0165] Acquire an operating system version that matches the server product model, and construct a version configuration data structure that matches the server product model and the operating system version;

[0166] Constructing a version characteristic data structure for each operating system version, wherein the version characteristic data structure includes an automatic installation file, a system image standard path, a kernel file, and a system image extension file;

[0167] Building a pre-start execution environment server for providing a server node with a download network file, and storing the version characteristic data structure as a network file on the pre-start execution environment server;

[0168] In response to the target server node accessing the pre-boot execution environment server, a network file matching the target server node is identified according to the version configuration data structure and a pre-installed boot file is downloaded and generated, and a boot menu item is generated according to the pre-installed boot file.

[0169] In one embodiment, the computer program further implements the following steps when executed by a processor:

[0170] The version configuration data structure for building the server product model to match the operating system version includes:

[0171] Obtain the hardware information corresponding to the server product model, and obtain the supported operating system version based on the hardware information;

[0172] Get the name of the server product model, get the name of the operating system version, and use {name of the server product model: name of the server product model} as the version configuration data structure.

[0173] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0174] The construction of the version characteristic data structure of each operating system version includes:

[0175] Set a data table, the header of which includes version, KS file, ISO path, kernel file and Img file;

[0176] Fill in the name of the operating system version corresponding to the version, fill in the name of the automatic installation file corresponding to the KS file, fill in the system image standard path corresponding to the ISO path, fill in the name of the kernel file corresponding to the kernel file, and fill in the name of the system image extension file corresponding to the Img file;

[0177] The filled data in the data table is converted into a version characteristic data structure corresponding to each operating system version.

[0178] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0179] The step of establishing a pre-startup execution environment server for providing a server node with a network file for downloading, and storing the version characteristic data structure as a network file on the pre-startup execution environment server comprises:

[0180] Building a pre-startup execution environment server, and storing the version characteristic data structure as a network file on the pre-startup execution environment server corresponding to the version configuration data structure;

[0181] Deploying a hypertext transfer protocol service and a file transfer protocol service on the pre-start execution environment server to provide network file downloading;

[0182] Deploy a dynamic host configuration protocol service on the pre-boot execution environment server to allocate an Internet Protocol address to a server node accessing the network;

[0183] A network file system service is deployed on the pre-start execution environment server to authorize server nodes connected to the network to access network files.

[0184] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0185] In response to the target server node accessing the pre-boot execution environment server, identifying a network file matching the target server node according to the version configuration data structure and downloading and generating a pre-installed boot file, and generating a boot menu item according to the pre-installed boot file includes:

[0186] Real-time detection of the network of the pre-start execution environment server to determine whether there is a target server node applying for network access;

[0187] If there is a target server node applying for access to the network, an Internet Protocol address is allocated to the target server node accessing the network through the dynamic host configuration protocol service;

[0188] After the target server node is connected to the pre-start execution environment server, identifying the target hardware product model of the target server node;

[0189] Acquire a target operating system version that matches the target hardware product model according to the version configuration data structure;

[0190] Determining whether there is a network file corresponding to the target operating system version in the version characteristic data structure stored in the pre-boot execution environment server;

[0191] If it exists, download the network file corresponding to the target operating system version through the hypertext transfer protocol service and the file transfer protocol service; if it does not exist, download the network file corresponding to the preset default operating system version through the hypertext transfer protocol service and the file transfer protocol service;

[0192] Generate a pre-installed boot file from the acquired network file;

[0193] Generate a startup menu item according to the preinstalled boot file.

[0194] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0195] In response to generating the startup menu item, the target server node is restarted, and an operating system is installed on the target server node according to the startup menu item.

[0196] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0197] In response to the target server node successfully installing the operating system, the server product model, product serial number, installed operating system version and installation time are recorded to form an operating system version data set;

[0198] The operating system version data set is regularly analyzed to count the pre-installed amount of the operating system installed on the server node and the distribution data of each operating system version, and to generate operating system usage and user installation preference reports.

[0199] For specific limitations on the steps implemented when the computer program is executed by the processor, please refer to the limitations on the method for matching operating system versions above, which will not be repeated here.

[0200] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 8 As shown. The computer device includes a processor, a memory, a network interface and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store operating system version matching data. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, an operating system version matching method is implemented.

[0201] Those skilled in the art will understand that Figure 8 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0202] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program:

[0203] Acquire an operating system version that matches the server product model, and construct a version configuration data structure that matches the server product model and the operating system version;

[0204] Constructing a version characteristic data structure for each operating system version, wherein the version characteristic data structure includes an automatic installation file, a system image standard path, a kernel file, and a system image extension file;

[0205] Building a pre-start execution environment server for providing a server node with a download network file, and storing the version characteristic data structure as a network file on the pre-start execution environment server;

[0206] In response to the target server node accessing the pre-boot execution environment server, a network file matching the target server node is identified according to the version configuration data structure and a pre-installed boot file is downloaded and generated, and a boot menu item is generated according to the pre-installed boot file.

[0207] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0208] The version configuration data structure for building the server product model to match the operating system version includes:

[0209] Obtain the hardware information corresponding to the server product model, and obtain the supported operating system version based on the hardware information;

[0210] Get the name of the server product model, get the name of the operating system version, and use {name of the server product model: name of the server product model} as the version configuration data structure.

[0211] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0212] The construction of the version characteristic data structure of each operating system version includes:

[0213] Set a data table, the header of which includes version, KS file, ISO path, kernel file and Img file;

[0214] Fill in the name of the operating system version corresponding to the version, fill in the name of the automatic installation file corresponding to the KS file, fill in the system image standard path corresponding to the ISO path, fill in the name of the kernel file corresponding to the kernel file, and fill in the name of the system image extension file corresponding to the Img file;

[0215] The filled data in the data table is converted into a version characteristic data structure corresponding to each operating system version.

[0216] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0217] The step of establishing a pre-startup execution environment server for providing a server node with a network file for downloading, and storing the version characteristic data structure as a network file on the pre-startup execution environment server comprises:

[0218] Building a pre-startup execution environment server, and storing the version characteristic data structure as a network file on the pre-startup execution environment server corresponding to the version configuration data structure;

[0219] Deploying a hypertext transfer protocol service and a file transfer protocol service on the pre-start execution environment server to provide network file downloading;

[0220] Deploy a dynamic host configuration protocol service on the pre-boot execution environment server to allocate an Internet Protocol address to a server node accessing the network;

[0221] A network file system service is deployed on the pre-start execution environment server to authorize server nodes connected to the network to access network files.

[0222] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0223] In response to the target server node accessing the pre-boot execution environment server, identifying a network file matching the target server node according to the version configuration data structure and downloading and generating a pre-installed boot file, and generating a boot menu item according to the pre-installed boot file includes:

[0224] Real-time detection of the network of the pre-start execution environment server to determine whether there is a target server node applying for network access;

[0225] If there is a target server node applying for access to the network, an Internet Protocol address is allocated to the target server node accessing the network through the dynamic host configuration protocol service;

[0226] After the target server node is connected to the pre-start execution environment server, identifying the target hardware product model of the target server node;

[0227] Acquire a target operating system version that matches the target hardware product model according to the version configuration data structure;

[0228] Determining whether there is a network file corresponding to the target operating system version in the version characteristic data structure stored in the pre-boot execution environment server;

[0229] If it exists, download the network file corresponding to the target operating system version through the hypertext transfer protocol service and the file transfer protocol service; if it does not exist, download the network file corresponding to the preset default operating system version through the hypertext transfer protocol service and the file transfer protocol service;

[0230] Generate a pre-installed boot file from the acquired network file;

[0231] Generate a startup menu item according to the preinstalled boot file.

[0232] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0233] In response to generating the startup menu item, the target server node is restarted, and an operating system is installed on the target server node according to the startup menu item.

[0234] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0235] In response to the target server node successfully installing the operating system, the server product model, product serial number, installed operating system version and installation time are recorded to form an operating system version data set;

[0236] The operating system version data set is regularly analyzed to count the pre-installed amount of the operating system installed on the server node and the distribution data of each operating system version, and to generate operating system usage and user installation preference reports.

[0237] For specific limitations on the steps implemented when the processor executes a computer program, please refer to the limitations on the operating system version matching method above, which will not be repeated here.

[0238] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0239] Acquire an operating system version that matches the server product model, and construct a version configuration data structure that matches the server product model and the operating system version;

[0240] Constructing a version characteristic data structure for each operating system version, wherein the version characteristic data structure includes an automatic installation file, a system image standard path, a kernel file, and a system image extension file;

[0241] Building a pre-start execution environment server for providing a server node with a download network file, and storing the version characteristic data structure as a network file on the pre-start execution environment server;

[0242] In response to the target server node accessing the pre-boot execution environment server, a network file matching the target server node is identified according to the version configuration data structure and a pre-installed boot file is downloaded and generated, and a boot menu item is generated according to the pre-installed boot file.

[0243] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0244] The version configuration data structure for building the server product model to match the operating system version includes:

[0245] Obtain the hardware information corresponding to the server product model, and obtain the supported operating system version based on the hardware information;

[0246] Get the name of the server product model, get the name of the operating system version, and use {name of the server product model: name of the server product model} as the version configuration data structure.

[0247] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0248] The construction of the version characteristic data structure of each operating system version includes:

[0249] Set a data table, the header of which includes version, KS file, ISO path, kernel file and Img file;

[0250] Fill in the name of the operating system version corresponding to the version, fill in the name of the automatic installation file corresponding to the KS file, fill in the system image standard path corresponding to the ISO path, fill in the name of the kernel file corresponding to the kernel file, and fill in the name of the system image extension file corresponding to the Img file;

[0251] The filled data in the data table is converted into a version characteristic data structure corresponding to each operating system version.

[0252] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0253] The step of establishing a pre-startup execution environment server for providing a server node with a network file for downloading, and storing the version characteristic data structure as a network file on the pre-startup execution environment server comprises:

[0254] Building a pre-startup execution environment server, and storing the version characteristic data structure as a network file on the pre-startup execution environment server corresponding to the version configuration data structure;

[0255] Deploying a hypertext transfer protocol service and a file transfer protocol service on the pre-start execution environment server to provide network file downloading;

[0256] Deploy a dynamic host configuration protocol service on the pre-boot execution environment server to allocate an Internet Protocol address to a server node accessing the network;

[0257] A network file system service is deployed on the pre-start execution environment server to authorize server nodes connected to the network to access network files.

[0258] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0259] In response to the target server node accessing the pre-boot execution environment server, identifying a network file matching the target server node according to the version configuration data structure and downloading and generating a pre-installed boot file, and generating a boot menu item according to the pre-installed boot file includes:

[0260] Real-time detection of the network of the pre-start execution environment server to determine whether there is a target server node applying for network access;

[0261] If there is a target server node applying for access to the network, an Internet Protocol address is allocated to the target server node accessing the network through the dynamic host configuration protocol service;

[0262] After the target server node is connected to the pre-start execution environment server, identifying the target hardware product model of the target server node;

[0263] Acquire a target operating system version that matches the target hardware product model according to the version configuration data structure;

[0264] Determining whether there is a network file corresponding to the target operating system version in the version characteristic data structure stored in the pre-boot execution environment server;

[0265] If it exists, download the network file corresponding to the target operating system version through the hypertext transfer protocol service and the file transfer protocol service; if it does not exist, download the network file corresponding to the preset default operating system version through the hypertext transfer protocol service and the file transfer protocol service;

[0266] Generate a pre-installed boot file from the acquired network file;

[0267] Generate a startup menu item according to the preinstalled boot file.

[0268] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0269] In response to generating the startup menu item, the target server node is restarted, and an operating system is installed on the target server node according to the startup menu item.

[0270] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0271] In response to the target server node successfully installing the operating system, the server product model, product serial number, installed operating system version and installation time are recorded to form an operating system version data set;

[0272] The operating system version data set is regularly analyzed to count the pre-installed amount of the operating system installed on the server node and the distribution data of each operating system version, and to generate operating system usage and user installation preference reports.

[0273] For specific limitations on the steps implemented when the computer program is executed by the processor, please refer to the limitations on the method for matching operating system versions above, which will not be repeated here.

[0274] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0275] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0276] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A method for matching operating system versions, characterized in that: include: Acquire an operating system version that matches the server product model, and construct a version configuration data structure that matches the server product model and the operating system version; Constructing a version characteristic data structure for each operating system version, wherein the version characteristic data structure includes an automatic installation file, a system image standard path, a kernel file, and a system image extension file; Building a pre-start execution environment server for providing a server node with a download network file, and storing the version characteristic data structure as a network file on the pre-start execution environment server; In response to the target server node accessing the pre-boot execution environment server, a network file matching the target server node is identified according to the version configuration data structure and a pre-installed boot file is downloaded and generated, and a boot menu item is generated according to the pre-installed boot file.

2. The operating system version matching method according to claim 1, characterized in that: The version configuration data structure for building the server product model to match the operating system version includes: Obtain hardware information corresponding to the server product model, and obtain supported operating system versions based on the hardware information; Get the name of the server product model, get the name of the operating system version, and use {name of the server product model: name of the server product model} as the version configuration data structure.

3. The operating system version matching method according to claim 2, characterized in that: The construction of the version characteristic data structure of each operating system version includes: Set a data table, the header of which includes version, KS file, ISO path, kernel file and Img file; Fill in the name of the operating system version corresponding to the version, fill in the name of the automatic installation file corresponding to the KS file, fill in the system image standard path corresponding to the ISO path, fill in the name of the kernel file corresponding to the kernel file, and fill in the name of the system image extension file corresponding to the Img file; The filled data in the data table is converted into a version characteristic data structure corresponding to each operating system version.

4. The operating system version matching method according to claim 1, characterized in that: The step of establishing a pre-startup execution environment server for providing a server node with a network file for downloading, and storing the version characteristic data structure as a network file on the pre-startup execution environment server comprises: Building a pre-startup execution environment server, and storing the version characteristic data structure as a network file on the pre-startup execution environment server corresponding to the version configuration data structure; Deploying a hypertext transfer protocol service and a file transfer protocol service on the pre-start execution environment server to provide network file downloading; Deploy a dynamic host configuration protocol service on the pre-boot execution environment server to allocate an Internet Protocol address to a server node accessing the network; A network file system service is deployed on the pre-start execution environment server to authorize server nodes connected to the network to access network files.

5. The operating system version matching method according to claim 4, characterized in that: In response to the target server node accessing the pre-boot execution environment server, identifying a network file matching the target server node according to the version configuration data structure and downloading and generating a pre-installed boot file, and generating a boot menu item according to the pre-installed boot file includes: Real-time detection of the network of the pre-start execution environment server to determine whether there is a target server node applying for network access; If there is a target server node applying for access to the network, an Internet Protocol address is allocated to the target server node accessing the network through the dynamic host configuration protocol service; After the target server node is connected to the pre-start execution environment server, identifying the target hardware product model of the target server node; Acquire a target operating system version that matches the target hardware product model according to the version configuration data structure; Determining whether there is a network file corresponding to the target operating system version in the version characteristic data structure stored in the pre-boot execution environment server; If it exists, download the network file corresponding to the target operating system version through the hypertext transfer protocol service and the file transfer protocol service; if it does not exist, download the network file corresponding to the preset default operating system version through the hypertext transfer protocol service and the file transfer protocol service; Generate a pre-installed boot file from the acquired network file; Generate a startup menu item according to the preinstalled boot file.

6. The operating system version matching method according to claim 5, characterized in that: The operating system version matching method further includes: In response to generating the startup menu item, the target server node is restarted, and an operating system is installed on the target server node according to the startup menu item.

7. The operating system version matching method according to claim 1, characterized in that: The operating system version matching method further includes: In response to the target server node successfully installing the operating system, the server product model, product serial number, installed operating system version and installation time are recorded to form an operating system version data set; The operating system version data set is regularly analyzed to count the pre-installed amount of the operating system installed on the server node and the distribution data of each operating system version, and to generate operating system usage and user installation preference reports.

8. An operating system version matching device, characterized in that: The device comprises: A version configuration data structure building module is used to obtain an operating system version that matches the server product model and build a version configuration data structure that matches the server product model and the operating system version; A version characteristic data structure construction module is used to construct a version characteristic data structure of each operating system version, wherein the version characteristic data structure includes an automatic installation file, a system image standard path, a kernel file, and a system image extension file; Building a pre-startup execution environment server module, used for building a pre-startup execution environment server for providing a server node with a download network file, and storing the version characteristic data structure as a network file on the pre-startup execution environment server; A startup menu item generation module is used to respond to the target server node accessing the pre-start execution environment server, identify the network file matching the target server node according to the version configuration data structure and download and generate a pre-installed boot file, and generate a startup menu item according to the pre-installed boot file.

9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the operating system version matching method described in any one of claims 1 to 7 are implemented.

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

Images