PXE terminal generation method, electronic equipment, storage medium and program product

Abstract

Embodiments of the present application provide a PXE terminal generation method, an electronic device, a storage medium and a program product, the method comprising: sending a production request to a production server, the production request at least comprising product demand information; receiving configuration file information returned by the production server; wherein the configuration file information is determined by the production server according to the product demand information and the identification information of the PXE terminal; acquiring a configuration file corresponding to the configuration file information according to the configuration file information; and after the configuration file is loaded, the target PXE terminal is generated, so that the problem that different operating systems (namely software products) cannot be installed on the same PXE client is solved, and the generation efficiency of the PXE terminal is improved.

Description

Technical Field

[0001] The present application relates to the field of integrated circuit technology. Specifically, it relates to a method for generating a PXE terminal, an electronic device, a storage medium, and a program product. Background Art

[0002] In a production workshop, thousands of machines, namely PXE terminals, may be mass-produced in a day. Different PXE terminals may need to install different versions of operating systems, and the efficiency is relatively low. In order to improve production efficiency and installation accuracy. In the traditional PXE method, it is necessary to configure in the DHCP that the PXE client obtains the path of the startup file (pxelinux.0) from the TFTP server. However, when the device needs to install different products (such as firewall products, vulnerability scanning products) developed by the company and different versions (such as V3.3, V6.0) of operating systems, since the content of the startup file is the same, the file paths of different products and different versions of operating systems cannot be specified. Therefore, how to generate different PXE terminals according to different needs is a technical problem that urgently needs to be solved at present. Summary of the Invention

[0003] Some embodiments of the present application aim to provide a method for generating a PXE terminal, an electronic device, a storage medium, and a program product. Through the technical solutions of the embodiments of the present application, by sending a production request to a production server, where the production request at least includes product requirement information; receiving the configuration file information returned by the production server; where the configuration file information is determined by the production server according to the product requirement information and the identification information of the PXE terminal; according to the configuration file information, obtaining a configuration file corresponding to the configuration file information; after loading the configuration file is completed, generating a target PXE terminal, solving the problem that the same PXE client cannot install different operating systems (i.e., software products), and improving the efficiency of generating PXE terminals.

[0004] In a first aspect, some embodiments of the present application provide a method for generating a PXE terminal, including:

[0005] Sending a production request to a production server, where the production request at least includes product requirement information;

[0006] Receiving the configuration file information returned by the production server; where the configuration file information is determined by the production server according to the product requirement information and the identification information of the PXE terminal;

[0007] According to the configuration file information, obtaining a configuration file corresponding to the configuration file information;

[0008] After loading the configuration file is completed, generating a target PXE terminal.

[0009] Some embodiments of the present application produce different configuration file information by a production server according to different product requirement information, and send the configuration file information to different PXE terminals. Then, the PXE terminals are loaded according to the different configuration file information to obtain target PXE terminals. In this way, different target PXE terminals can be produced according to different product requirement information, improving the efficiency of generating target PXE terminals.

[0010] Optionally, before sending a production request to the production server, the method further includes:

[0011] Receiving the IP address of the PXE terminal sent by an address server through the DHCP protocol.

[0012] Some embodiments of the present application configure different address information for different PXE terminals by an address server. The fixed IP of the TFTP server accessed by the PXE client does not need to reconfigure the DHCP server or re-burn the BootLoader as the production environment changes, solving the system problem that the DHCP server configuration needs to be modified after the IP of the TFTP server changes.

[0013] Optionally, after sending the production request to the production server, the method further includes:

[0014] Receiving a normal production response message returned by the production server.

[0015] Optionally, the identification information of the PXE terminal includes at least a product serial number barcode or a QR code.

[0016] Optionally, the product serial number barcode is obtained by scanning with a scanning device.

[0017] In some embodiments of the present application, the product serial number is scanned into by a barcode scanner, and the device to be produced obtains the product serial number from the production filling system through TCP communication without directly connecting to the device, greatly improving the production efficiency.

[0018] Optionally, obtaining the configuration file corresponding to the configuration file information according to the configuration file information includes:

[0019] Sending a file request to a file server, where the file request includes at least the configuration file information;

[0020] Receiving the configuration file corresponding to the configuration file information returned by the file server, where the configuration file includes an installation command file.

[0021] Some embodiments of the present application obtain the serial number of the product through TCP communication, and then obtain the pre-configured configuration file through the serial number. The configuration file contains the list of operating system files to be installed, and the degree of freedom of the configuration file is relatively high.

[0022] Optionally, the method further includes;

[0023] After obtaining the target PXE terminal, obtain the authorization file sent by the license server to enable the target PXE terminal to perform a registration operation.

[0024] In some embodiments of the present application, the PXE client starts the registration process, obtains the authorization file from the license system, enables the relevant functions, and reports the registration progress.

[0025] In a second aspect, some embodiments of the present application provide a generating device for a PXE terminal, including:

[0026] A sending module, configured to send a production request to a production server, where the production request at least includes product requirement information;

[0027] A receiving module, configured to receive the configuration file information returned by the production server; where the configuration file information is determined by the production server according to the product requirement information and the identification information of the PXE terminal;

[0028] An obtaining module, configured to obtain a configuration file corresponding to the configuration file information according to the configuration file information;

[0029] A loading module, configured to generate a target PXE terminal after completing the loading of the configuration file.

[0030] In some embodiments of the present application, the production server produces different configuration file information according to different product requirement information, and sends the configuration file information to different PXE terminals. Then, the PXE terminals perform loading according to different configuration file information to obtain the target PXE terminals. In this way, different target PXE terminals can be produced according to different product requirement information, improving the efficiency of generating the target PXE terminals.

[0031] Optionally, the receiving module is configured to:

[0032] Receive the IP address of the PXE terminal sent by the address server through the DHCP protocol.

[0033] In some embodiments of the present application, different address information is configured for different PXE terminals by an address server. The fixed IP of the TFTP server accessed by the PXE client does not need to be reconfigured for the DHCP server or the BootLoader to be rewritten as the production environment changes, thus solving the system problem that the DHCP server configuration needs to be modified after the IP of the TFTP server changes.

[0034] Optionally, the receiving module is configured to:

[0035] Receive the normal production response information returned by the production server.

[0036] Optionally, the identification information of the PXE terminal includes at least a product serial number barcode or a QR code.

[0037] Optionally, the product serial number barcode is obtained by scanning with a scanning device.

[0038] In some embodiments of the present application, the product serial number is scanned into by a barcode scanner, and the device to be produced obtains the product serial number from the production filling system through TCP communication without directly connecting to the device, greatly improving production efficiency.

[0039] Optionally, the obtaining module is configured to:

[0040] Send a file request to the file server, where the file request includes at least the configuration file information;

[0041] Receive the configuration file corresponding to the configuration file information returned by the file server, where the configuration file includes an installation command file.

[0042] In some embodiments of the present application, the product serial number is obtained through TCP communication, and then the pre-configured configuration file is obtained through the serial number. The configuration file contains the list of operating system files to be installed, and the degree of freedom of the configuration file is relatively high.

[0043] Optionally, the obtaining module is further configured to;

[0044] After obtaining the target PXE terminal, obtain the authorization file sent by the license server to enable the target PXE terminal to perform a registration operation.

[0045] In some embodiments of the present application, the PXE client starts the registration process, obtains the authorization file from the license system, enables the relevant functions, and reports the registration progress.

[0046] In a third aspect, some embodiments of the present application provide an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the method for generating a PXE terminal as described in any embodiment of the first aspect can be implemented.

[0047] In a fourth aspect, some embodiments of the present application provide a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, the method for generating a PXE terminal as described in any embodiment of the first aspect can be implemented.

[0048] In a fifth aspect, some embodiments of the present application provide a computer program product, which includes a computer program. When the computer program is executed by a processor, the method for generating a PXE terminal as described in any embodiment of the first aspect can be implemented. Description of the Drawings

[0049] In order to more clearly illustrate the technical solutions of some embodiments of the present application, the drawings required to be used in some embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present application and should not be regarded as a limitation of the scope. For those of ordinary skill in the art, other related drawings can be obtained based on these drawings without creative efforts.

[0050] Figure 1 It is a schematic flowchart of a method for generating a PXE terminal provided by an embodiment of the present application;

[0051] Figure 2 It is a schematic flowchart of another method for generating a PXE terminal provided by an embodiment of the present application;

[0052] Figure 3 It is a schematic diagram of the address configuration of a DHCP server provided by an embodiment of the present application;

[0053] Figure 4 It is a schematic flowchart of yet another method for generating a PXE terminal provided by an embodiment of the present application;

[0054] Figure 5 It is a schematic diagram of the network configuration stage provided by an embodiment of the present application;

[0055] Figure 6 It is a schematic structural diagram of a device for generating a PXE terminal provided by an embodiment of the present application;

[0056] Figure 7 It is a schematic diagram of an electronic device provided by an embodiment of the present application. Detailed Embodiments

[0057] The technical solutions in some embodiments of the present application will be described below with reference to the accompanying drawings in some embodiments of the present application.

[0058] It should be noted that: Similar reference numerals and letters denote similar items in the following accompanying drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. At the same time, in the description of the present application, terms such as "first", "second", etc. are only used for differential description and cannot be construed as indicating or implying relative importance.

[0059] Glossary:

[0060] PXE is a network boot protocol that is mainly applied to clients and servers, aiming to enable clients to download and install operating systems from remote servers through the network. PXE is commonly used in scenarios such as computer network booting, remote deployment, and recovery, especially in environments where large-scale server or workstation configuration is required.

[0061] The working principle of PXE is that after the PXE client (here refers to the computer to install the operating system) is powered on, a PXE firmware on the local network card is started. This firmware can send a DHCP Discover broadcast request to find a DHCP server. Then the DHCP server responds and allocates an IP address from the configured address pool, and then returns the IP address and the path where the startup file pxelinux.0 is located (usually on a TFTP server) to the client. Then after the PXE client receives this file, it starts to execute this file. This file will instruct the PXE client to request the computer configuration information pxelinux.cfg from the TFTP server. The PXE client reads this configuration file, which will tell which files there are, such as the operating system image. Then the PXE client will request these files from the TFTP server, and then load the operating system image into memory for installation and startup, so that the same operating system can be automatically installed on the client in batches through the network.

[0062] The DHCP (Dynamic Host Configuration Protocol) protocol is a network protocol used to automatically assign necessary network configuration information such as IP addresses, subnet masks, default gateways, and DNS server addresses to network devices.

[0063] TFTP (Trivial File Transfer Protocol) is a simple file transfer protocol mainly used for transferring small files in a network.

[0064] In a production workshop, thousands of controlled machines, namely PXE terminals, may need to be mass-produced in a day. Different PXE terminals may require different versions of the operating system to be installed, resulting in relatively low efficiency. To improve production efficiency and installation accuracy. In the traditional PXE method, it is necessary to configure the PXE client in the DHCP to obtain the path of the boot file (pxelinux.0) from the TFTP server. However, when the device needs to install different products developed by the company (such as firewall products, vulnerability scanning products) and different versions (such as V3.3, V6.0) of the operating system, since the content of the boot file is the same, it is impossible to specify the file paths of different products and different versions of the operating system. Therefore, how to generate different PXE terminals according to different needs is a technical problem that needs to be solved urgently at present. In view of this, some embodiments of the present application provide a method for generating a PXE terminal. The method includes sending a production request to a production server, where the production request at least includes product requirement information; receiving configuration file information returned by the production server; where the configuration file information is determined by the production server according to the product requirement information and the identification information of the PXE terminal; obtaining a configuration file corresponding to the configuration file information according to the configuration file information; and generating a target PXE terminal after the configuration file is loaded, so as to solve the problem that the same PXE client cannot install different operating systems (i.e., software products), and improve the efficiency of generating PXE terminals.

[0065] As Figure 1 shown, embodiments of the present application provide a method for generating a PXE terminal. The method includes:

[0066] S101. Send a production request to a production server, where the production request at least includes product requirement information;

[0067] Specifically, the PXE terminal includes a hardware structure and loaded software functions. Since the loaded software functions are different, the produced PXE terminals are also different. For example, a PXE terminal installed with a firewall system, or a PXE terminal installed with a security monitoring system, and different versions of application software.

[0068] For the hardware structure of the PXE terminal, send a production request to the production server, and the production request at least includes product requirement information. For example, the product requirement information is used to perform different functions.

[0069] S102. Receive configuration file information returned by the production server; where the configuration file information is determined by the production server according to the product requirement information and the identification information of the PXE terminal;

[0070] Specifically, after receiving a production request sent by a PXE terminal, the production server obtains the identification information of the PXE terminal, and then generates configuration file information based on the identification information of the PXE terminal and product requirement information, and sends the generated configuration file information to the corresponding PXE terminal.

[0071] S103. Obtain a configuration file corresponding to the configuration file information according to the configuration file information;

[0072] Specifically, the PXE terminal obtains a configuration file corresponding to the configuration file information from a TFTP server according to the configuration file information. For example, it may be an operating system or application software, etc. The configuration file supports high customization and does not require intervention and generation by a pre-set production server. The content of the configuration file is controlled by each product line, and the configuration file is uploaded to an ftp server.

[0073] S104. After the configuration file is loaded, generate a target PXE terminal.

[0074] After obtaining the configuration file, the PXE terminal loads the configuration file. After the loading is completed, a target PXE terminal that meets the product requirement information is obtained.

[0075] In some embodiments of the present application, the production server produces different configuration file information according to different product requirement information, and sends the configuration file information to different PXE terminals. Then, the PXE terminals perform loading according to different configuration file information to obtain target PXE terminals. In this way, different target PXE terminals can be produced according to different product requirement information, improving the efficiency of generating target PXE terminals.

[0076] Another embodiment of the present application further supplements and explains the method for generating a PXE terminal provided in the above embodiment.

[0077] Optionally, before sending a production request to the production server, the method further includes:

[0078] Receiving the IP address of the PXE terminal sent by an address server through the DHCP protocol.

[0079] Specifically, the PXE terminal obtains an assigned IP address through the DHCP protocol. The IP address pool of the address server, that is, the DHCP server, needs to be pre-allocated, that is, a corresponding IP address is set for each PXE terminal. As Figure 3 shown, the range of the IP address is 192.168.1.x to 192.168.1.x.

[0080] In some embodiments of the present application, different address information is configured for different PXE terminals by an address server. The fixed IP of the TFTP server accessed by the PXE client does not need to be reconfigured for the DHCP server or the BootLoader to be rewritten as the production environment changes, thus solving the system problem that the DHCP server configuration needs to be modified after the IP of the TFTP server changes.

[0081] Optionally, after sending a production request to the production server, the method further includes:

[0082] Receiving a normal production response message returned by the production server.

[0083] Specifically, the PXE terminal (i.e., the PXE client) communicates with the production filling system on the production server through the TCP protocol to request the production system to input the production mode. The production filling system transmits "P" (indicating that the mode is normal production) back to the PXE client. The PXE client waits for the production system to transmit the PSN.

[0084] Optionally, the identification information of the PXE terminal includes at least the product serial number barcode or QR code.

[0085] Optionally, the product serial number barcode is obtained by scanning with a scanning device.

[0086] Exemplarily, the production filling system automatically pops up a window for scanning the product serial number and waits for the production workshop personnel to scan the product serial number (abbreviated as PSN) or QR code. The staff scans the product serial number barcode or QR code on the device with a barcode scanner. After the production server obtains the scanned serial number, it transmits the identification information of the PXE terminal, such as the PSN, to the PXE client through the TCP (Transmission Control Protocol, a connection-oriented, reliable, byte-stream-based transport layer communication protocol) protocol. At the same time, the production server generates <psn>_prod_conf configuration file information.

[0087] That is, in the embodiments of the present application, to obtain the configuration file, only the product serial number needs to be passed in, without other information such as the server address, the IP address of the device, and the IP address mask of the device, unlike before when the product serial number was used to obtain the configuration file from the ftp server.

[0088] In some embodiments of the present application, the product serial number is scanned into by a barcode scanner, and the device to be produced obtains the product serial number from the production filling system through TCP communication without directly connecting to the device, greatly improving production efficiency.

[0089] Optionally, according to the configuration file information, obtain the configuration file corresponding to the configuration file information, including:

[0090] Send a file request to the file server, where the file request includes at least the configuration file information;

[0091] Receive the configuration file corresponding to the configuration file information returned by the file server, where the configuration file includes an installation command file.

[0092] Specifically, the PXE client requests to download from the production filling system <psn>_prod_conf configuration file information. The production filling system returns <psn>_prod_conf configuration file information. The PXE client accesses the TFTP server of the production filling system, which is the file server, to obtain the corresponding configuration file, that is <psn>The files listed in the _prod_conf configuration file include the installation command file.

[0093] In some embodiments of the present application, the serial number of the product is obtained through TCP communication, and then the pre-configured configuration file is obtained through the serial number. The configuration file contains the list of operating system files to be installed, and the degree of freedom of the configuration file is relatively high.

[0094] Optionally, the method further includes;

[0095] After obtaining the target PXE terminal, obtain the authorization file sent by the license server to enable the target PXE terminal to perform the registration operation.

[0096] In some embodiments of the present application, the PXE client starts the registration process, obtains the authorization file from the license system, enables the relevant functions, and reports the registration progress.

[0097] Such as Figure 2 As shown, the embodiments of the present application provide a method for supporting the installation of different versions of the operating system by the PXE client, including:

[0098] 1. The PXE client (device) is plugged in and powered on, and the customized bootloader starts.

[0099] 2. The PXE client obtains the assigned IP through the DHCP protocol.

[0100] The IP address pool of the DHCP server needs to be allocated in advance, as shown in the following figure: the IP range is 192.168.1.x to 192.168.1.x, as Figure 3 shown.

[0101] 3. The DHCP server assigns an IP to the PXE client.

[0102] 4. The PXE client communicates with the production filling system through the TCP protocol and requests the production system to input the production mode.

[0103] 5. The production filling system transmits "P" (indicating the normal production mode) back to the PXE client. The PXE client waits for the production system to transmit the PSN.

[0104] 6. The production filling system automatically pops up a window for scanning the product serial number and waits for the production workshop personnel to scan the product serial number (abbreviation: PSN).

[0105] 7. The staff scans the product serial number barcode on the device with a barcode scanner.

[0106] 8. After the production system obtains the scanned serial number, it transmits the PSN to the PXE client through TCP communication. And generate <psn>_prod_conf configuration file.

[0107] 9. The PXE client requests to download from the production filling system <psn>_prod_conf configuration file information.

[0108] 10. Production filling system returns <psn>_prod_conf configuration file information.

[0109] 11. The PXE client accesses the TFTP server of the production filling system to obtain the configuration file corresponding to the configuration file information, that is <psn>The files listed in the _prod_conf configuration file include the installation command file.

[0110] 12. The PXE client starts installing the operating system according to the installation command file and reports the installation progress.

[0111] 13. After the PXE client installs the operating system, restart the PXE client.

[0112] 14. The PXE client starts the registration process, obtains the authorization file from the license system to enable the relevant functions, and reports the registration progress.

[0113] Exemplarily, (1) The operators of the production filling system will upload different operating systems (software packages of security products) and configuration files to different folders on the TFTP server in advance. The folders are named after the software packages, such as V3.1_N.

[0114] (2) Each production task contains PSN information and software version information. The production filling system obtains the software version information V3.1_N according to the scanned PSN.

[0115] (3) The production filling system finds the folder V3.1_N corresponding to the software version on the TFTP server.

[0116] (4) The production filling system copies the configuration file in the folder to the local disk of the production filling system and names it <psn>_prod_conf configuration file. This configuration file specifies the software packages required for the current operating system.

[0117] (5) The PXE client obtains from the production filling system <psn>After the _prod_conf configuration file, download the specified operating system software package and install it.

[0118] The embodiments of the present application can be applied to the design of fully autonomous automated production and filling of multiple products and multiple versions. Based on fully autonomous automated production and filling, this application proposes a method for producing and filling multiple products and multiple versions based on PXE. In the fully autonomous automated production and filling of multiple products and multiple versions, the operating systems for producing multiple products and multiple versions are installed by modifying the way of obtaining the configuration file.

[0119] As Figure 4 shown, Figure 4 FIG. 10 is a schematic flow chart of another method for generating a PXE terminal provided by an embodiment of the present application. First, deploy a production and filling system, that is, a production server, and synchronize the tasks to be produced to the production and filling system. This system is used to obtain the system version information in the production task through the PSN entered by scanning the code. The system is used to display the production progress and equipment status, and this system communicates with the PXE client through TCP to return the version information of the production task.

[0120] The production and filling system locally enables the TFTP service and maps the files copied from the TFTP server. The IP address corresponding to this TFTP service can be specified as 192.168.1.100. The PXE client only needs to access this IP address to obtain the operating system file, and does not need to change the address as the production environment changes.

[0121] The address service, that is, the PXE server, enables the DHCP service: used to allocate IPs to the PXE clients.

[0122] Deploy the TFTP server: Store system software of different versions in different paths, and then the production and filling system obtains the operating system files according to the configuration file and stores them in the local disk of the production system.

[0123] The PXE client installs an adapted BootLoader, which is used to communicate with the PXE server through TCP and download the operating system file through TFTP.

[0124] The specific process is as follows:

[0125] 1) Startup phase: After the PXE client device is plugged in and powered on, the BootLoader starts automatically.

[0126] 2) Network configuration phase: The PXE client dynamically obtains an IP address through the DHCP protocol. The DHCP server manages the IP address pool, including the management policies of the IP address pool, such as the allocation and recycling mechanisms of IP addresses. As Figure 5 shown:

[0127] 3) IP Assignment Phase: The DHCP server responds to the IP request from the PXE client and assigns an IP address.

[0128] 4) Mode Selection Phase: The PXE client enters the mode selection state.

[0129] 5) Production Mode Confirmation Phase: The production filling system automatically returns a confirmation signal "P", instructing the PXE client to wait for further operations by the workshop production personnel.

[0130] 6) PSN Entry Phase: The workshop production personnel use a barcode scanner to scan the bar code and automatically enter the Product Serial Number (PSN) into the production system.

[0131] 7) PSN Transmission Phase: How the production filling system transmits the scanned PSN to the PXE client via TCP communication. And upload <psn>The _prod_conf configuration file and the operating system files contained in the configuration file are uploaded to the local server of the production system.

[0132] 8) Configuration file request phase: The PXE client requests a specific configuration file on the TFTP directory of the production filling system according to the PSN. This configuration file includes the operating system kernel file and the installation command file.

[0133] 9) Configuration file provision phase: The production filling system responds to the request of the PXE client and provides the corresponding configuration file <psn>_prod_conf。

[0134] 10) File acquisition stage: The PXE client reads <psn>_prod_conf configuration file, and then access the TFTP server of the production filling system to obtain the files specified in the configuration file.

[0135] (a) The content of the configuration file is as follows:

[0136] VERSION = V3.1_N

[0137] KERNEL = V3.1_N_kernel

[0138] ROOTFS = V3.1_N_r2.2

[0139] INSTALL_CFG_BOOT = V3.1_N_disk_write.cfg ...

[0141] #end

[0142] (b) Example of the storage paths of these files: ftp: / / 192.168.1.100 / ftp / v3.1 / v3.1_N_kernel

[0143] 11) Operating system installation stage: The PXE client starts the installation process of the operating system.

[0144] 12) Device restart stage: After the operating system installation is completed, the PXE client automatically restarts the device.

[0145] 13) Function authorization stage: After the PXE client restarts, it automatically registers with the license system and obtains the authorization file, and decrypts the authorization file to enable the relevant functions.

[0146] The main technical effects of the present invention are as follows:

[0147] (1) Different versions of the operating system can be installed and reinstalled. This effect is because the PXE client supports obtaining different versions of the operating system files on the TFTP server.

[0148] (2) Support for human-computer interaction to select different operating system versions. This effect is because the production system supports human input of the product serial number PSN, and subsequently generates a configuration file through the PSN, which contains the software package files required for the specified operating system.

[0149] (3) The PXE client does not need to reconfigure the DHCP server or re-burn the BootLoader due to the change of the IP of the TFTP server.

[0150] (4) The PSN can be transmitted without the need for a direct connection to the PXE client. The direct connection methods include ssh login or serial communication. This effect is because the PXE client communicates with the production filling system through the TCP protocol and triggers the QR code scanning pop-up window of the production filling system, waiting for the staff to scan and enter the product serial number PSN.

[0151] To overcome the deficiencies of the prior art, the embodiments of the present application solve the problems that the same PXE client cannot install different operating systems (i.e., software products), the problem of being unable to select a specified operating system (i.e., software product), the system problem that the IP of the TFTP server needs to be modified after it changes, the problem of too much incoming device information to be installed, the problem of inflexible configuration file generation methods, and the problem of low efficiency and easy errors caused by the need to directly connect to the device to transmit the product serial number.

[0152] It should be noted that each implementable method in this embodiment can be implemented independently or in any combination without conflict. The present application makes no limitation.

[0153] Another embodiment of the present application provides a generating device for a PXE terminal, which is used to execute the method for generating a PXE terminal provided in the above embodiment.

[0154] As Figure 6 shown, it is a schematic structural diagram of the generating device for a PXE terminal provided in the embodiment of the present application. The generating device for a PXE terminal includes a sending module 601, a receiving module 602, an obtaining module 603, and a loading module 604, where:

[0155] The sending module 601 is used to send a production request to the production server, where the production request at least includes product demand information;

[0156] The receiving module 602 is used to receive the configuration file information returned by the production server; where the configuration file information is determined by the production server according to the product demand information and the identification information of the PXE terminal;

[0157] The obtaining module 603 is used to obtain the configuration file corresponding to the configuration file information according to the configuration file information;

[0158] The loading module 604 is used to generate a target PXE terminal after the configuration file is loaded.

[0159] Regarding the device in this embodiment, the specific manners in which each module performs operations have been described in detail in the embodiments related to the method, and will not be elaborated here.

[0160] In some embodiments of the present application, the production server produces different configuration file information according to different product requirement information, and sends the configuration file information to different PXE terminals. Then, the PXE terminals are loaded according to the different configuration file information to obtain the target PXE terminals. In this way, different target PXE terminals can be produced according to different product requirement information, improving the efficiency of generating the target PXE terminals.

[0161] Another embodiment of the present application further supplements the generating device of the PXE terminal provided in the above embodiment.

[0162] Optionally, the receiving module is configured to:

[0163] Receive the IP address of the PXE terminal sent by the address server through the DHCP protocol.

[0164] In some embodiments of the present application, the address server configures different address information for different PXE terminals. The fixed IP of the TFTP server accessed by the PXE client does not need to be reconfigured for the DHCP server or the BootLoader to be rewritten as the production environment changes, solving the system problem that the DHCP server configuration needs to be modified after the IP of the TFTP server changes.

[0165] Optionally, the receiving module is configured to:

[0166] Receive the normal production response information returned by the production server.

[0167] Optionally, the identification information of the PXE terminal includes at least the product serial number barcode or two-dimensional code.

[0168] Optionally, the product serial number barcode is obtained by scanning with a scanning device.

[0169] In some embodiments of the present application, the product serial number is scanned into by a barcode scanner, and the device to be produced obtains the product serial number from the production filling system through TCP communication without directly connecting to the device, greatly improving the production efficiency.

[0170] Optionally, the obtaining module is configured to:

[0171] Send a file request to the file server, where the file request includes at least the configuration file information;

[0172] Receive the configuration file corresponding to the configuration file information returned by the file server, where the configuration file includes an installation command file.

[0173] Some embodiments of the present application obtain the serial number of the product through TCP communication, and then obtain the pre-configured configuration file through the serial number. The configuration file contains the list of operating system files to be installed, and the degree of freedom of the configuration file is relatively high.

[0174] Optionally, the obtaining module is further configured to;

[0175] After obtaining the target PXE terminal, obtain the authorization file sent by the license server to enable the target PXE terminal to perform the registration operation.

[0176] In some embodiments of the present application, the PXE client starts the registration process, obtains the authorization file from the license system, enables the relevant functions, and reports the registration progress.

[0177] Regarding the device in this embodiment, the specific manners in which each module performs operations have been described in detail in the embodiments related to the method, and will not be elaborated herein.

[0178] It should be noted that each feasible manner in this embodiment can be implemented independently, or can be combined in any combination manner without conflict. The present application makes no limitation.

[0179] The embodiments of the present application also provide a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, the operations corresponding to any of the embodiments in the method for generating a PXE terminal provided in the above embodiments can be implemented.

[0180] The embodiments of the present application also provide a computer program product. The computer program product includes a computer program. When the computer program is executed by a processor, the operations corresponding to any of the embodiments in the method for generating a PXE terminal provided in the above embodiments can be implemented.

[0181] As Figure 7 As shown, some embodiments of the present application provide an electronic device 700, which includes: a memory 710, a processor 720, and a computer program stored on the memory 710 and executable on the processor 720. When the processor 720 reads the program from the memory 710 through the bus 730 and executes the program, the methods of any of the embodiments included in the method for generating a PXE terminal as described above can be implemented.

[0182] The processor 720 can process digital signals and can include various computing architectures. For example, a complex instruction set computer architecture, a reduced instruction set computer architecture, or an architecture that implements a combination of multiple instruction sets. In some examples, the processor 720 can be a microprocessor.

[0183] The memory 710 can be used to store instructions executed by the processor 720 or data related to the instruction execution process. These instructions and / or data may include code for implementing some or all of the functions of one or more modules described in the embodiments of the present application. The processor 720 according to the embodiments of the present disclosure can be used to execute the instructions in the memory 710 to implement the method as shown above. The memory 710 includes a dynamic random access memory, a static random access memory, a flash memory, an optical memory, or other memories well known to those skilled in the art.

[0184] The above are only embodiments of the present application and are not intended to limit the protection scope of the present application. For those skilled in the art, the present application can have various changes and modifications. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that similar reference numerals and letters denote similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings.

[0185] As described above, the above are only the specific implementation manners of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed by the present application, and all of them should be covered by the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

[0186] It should be noted that in this document, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variation thereof is intended to cover a non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the phrase "comprising a..." does not exclude the presence of additional identical elements in the process, method, article or device comprising the element.< / psn> < / psn> < / psn> < / psn> < / psn> < / psn> < / psn> < / psn> < / psn> < / psn> < / psn> < / psn> < / psn>

Claims

1. A method for generating a PXE terminal, characterized in that: The method comprises: Sending a production request to a production server, wherein the production request at least includes product demand information; Receiving configuration file information returned by the production server; wherein the configuration file information is determined by the production server according to the product requirement information and the identification information of the PXE terminal; According to the configuration file information, obtaining a configuration file corresponding to the configuration file information; After the configuration file is loaded, a target PXE terminal is generated.

2. The method for generating a PXE terminal according to claim 1, characterized in that: Before sending the production request to the production server, the method further includes: The IP address of the PXE terminal sent by the address server is received through the DHCP protocol.

3. The method for generating a PXE terminal according to claim 1, characterized in that: After sending the production request to the production server, the method further includes: Receive normal production response information returned by the production server.

4. The method for generating a PXE terminal according to claim 1, characterized in that: The identification information of the PXE terminal includes at least a product serial number barcode or a QR code.

5. The method for generating a PXE terminal according to claim 4, characterized in that: The product serial number barcode is obtained by scanning with a scanning device.

6. The method for generating a PXE terminal according to claim 1, characterized in that: The acquiring, according to the configuration file information, a configuration file corresponding to the configuration file information includes: Sending a file request to a file server, wherein the file request at least includes the configuration file information; A configuration file corresponding to the configuration file information and returned by the file server is received, wherein the configuration file includes an installation command file.

7. The method for generating a PXE terminal according to claim 1, characterized in that: The method further comprises: After obtaining the target PXE terminal, an authorization file sent by a license server is obtained, so that the target PXE terminal performs a registration operation.

8. An electronic device, characterized in that: The invention comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor can implement the method for generating a PXE terminal according to any one of claims 1 to 7 when executing the program.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein when the program is executed by a processor, the method for generating a PXE terminal according to any one of claims 1 to 7 can be implemented.

10. A computer program product, comprising a computer program, wherein: When the computer program is executed by a processor, the method for generating a PXE terminal according to any one of claims 1 to 7 can be implemented.

Images