Method for transmitting time length instruction, method for starting device, and electronic device

Abstract

The application discloses a time length instruction transmission method, a starting method of a device and an electronic device, and relates to the technical field of computers. The time length instruction transmission method comprises the following steps: receiving an overtime length determined by a target object based on a network influence parameter of a device to be started; generating a first time length instruction based on the overtime length; and transmitting the first time length instruction to a baseboard management controller to instruct the baseboard management controller to store the overtime length. That is, the dynamically determined overtime length is stored in the baseboard management controller, and in the case where the baseboard management controller receives a second time length instruction for the device to be started, the dynamically determined overtime length is transmitted to the device to be started. Compared with a fixed overtime length, the dynamic overtime length determined by the network influence parameter avoids the problems of excessively long or excessively short waiting response time in network starting, and can effectively improve the starting performance of the device to be started in network starting.

Description

Technical Field

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

[0002] With the development of computer technology, network boot technology has played an increasingly important role. It allows computers to load operating systems from remote servers over a network without local storage media (such as hard drives), enabling remote management and automated deployment of computers.

[0003] However, despite the numerous conveniences offered by network boot technology, some problems and limitations still exist, particularly regarding the setting of network boot timeout duration. In most scenarios, the network boot timeout duration is a fixed preset. This can lead to boot failures in complex network environments or unnecessary waiting in simple network environments, impacting computer boot performance. Summary of the Invention

[0004] This application provides a method for transmitting duration instructions, a method for starting a device, and an electronic device, in order to at least solve the problem in the related art that the setting of a fixed timeout duration affects the device startup performance.

[0005] This application provides a method for transmitting a duration instruction, comprising: receiving a timeout duration determined by a target object based on network impact parameters of a device to be started; wherein the network impact parameters are parameters that affect the network startup state of the device to be started, and the timeout duration is a set maximum duration for the device to be started to wait for a response during network startup; generating a first duration instruction based on the timeout duration; transmitting the first duration instruction to a baseboard management controller of the device to be started to instruct the baseboard management controller to store the timeout duration; wherein the timeout duration stored by the baseboard management controller is to be transmitted to the device to be started when the baseboard management controller receives a second duration instruction for the device to be started.

[0006] This application also provides a timeout instruction transmission device, comprising: a first receiving module, configured to receive a timeout duration determined by a target object based on network impact parameters of a device to be started; wherein the network impact parameters are parameters that affect the network startup state of the device to be started, and the timeout duration is a set maximum duration for the device to be started to wait for a response during network startup; a first generating module, configured to generate a first timeout instruction based on the timeout duration; and a first transmitting module, configured to transmit the first timeout instruction to a baseboard management controller of the device to be started, to instruct the baseboard management controller to store the timeout duration; wherein the timeout duration stored by the baseboard management controller is to be transmitted to the device to be started when the baseboard management controller receives a second timeout instruction for the device to be started.

[0007] This application also provides an electronic device, including: a memory for storing a computer program; and a processor for executing the computer program to implement the steps of any of the above-described duration instruction transmission methods.

[0008] This application also provides a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, it implements the steps of any of the above-described duration instruction transmission methods.

[0009] This application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of any of the above-described duration instruction transmission methods.

[0010] This application involves receiving a timeout duration determined by the target device based on network impact parameters of the device to be started, and then generating a first duration instruction based on the timeout duration. This first duration instruction is transmitted to the baseboard management controller (BMDC) of the device to be started, instructing the BMDC to store the timeout duration. Thus, when the BMDC receives a second duration instruction from the device to be started, the timeout duration can be transmitted to the device. In other words, by storing a dynamically determined timeout duration in the BMDC and transmitting it to the device when the BMDC receives a second duration instruction for the device to be started, this dynamic timeout duration, determined by network impact parameters, avoids the problem of excessively long or short response times during network startup, effectively improving the startup performance of the device during network startup, compared to a fixed timeout duration.

[0011] This application also provides a method for transmitting a duration instruction, comprising: receiving a first duration instruction generated based on a timeout duration transmitted by a computer terminal, wherein the timeout duration is a duration determined by a target object based on network impact parameters of a device to be started, the network impact parameters being parameters that affect the network startup state of the device to be started, and the timeout duration being a set maximum duration for the device to be started to wait for a response during network startup; in response to the first duration instruction, storing the timeout duration carried in the first duration instruction; and, upon the baseboard management controller receiving a second duration instruction for the device to be started, transmitting the timeout duration to the device to be started.

[0012] This application also provides a duration instruction transmission device, comprising: a second receiving module, configured to receive a first duration instruction generated based on a timeout duration transmitted by a computer terminal, wherein the timeout duration is a duration determined by a target object based on network influence parameters of a device to be started, the network influence parameters being parameters that affect the network startup state of the device to be started, and the timeout duration being a set maximum duration for the device to be started to wait for a response during network startup; a response module, configured to respond to the first duration instruction and store the timeout duration carried in the first duration instruction; and a second transmission module, configured to transmit the timeout duration to the device to be started when the baseboard management controller receives a second duration instruction for the device to be started.

[0013] This application allows the system to receive a first duration instruction transmitted from a computer terminal, and in response to the first duration instruction, store the timeout duration carried in the first duration instruction. Upon receiving a second duration instruction for the device to be started, the baseboard management controller transmits the timeout duration to the device to be started. In other words, the baseboard management controller can store a timeout duration determined by network influence parameters based on the target object, and transmit the timeout duration to the device to be started upon receiving the second duration instruction. Compared to a fixed timeout duration, this dynamic timeout duration determined by network influence parameters avoids the problem of excessively long or short response times during network startup, effectively improving the startup performance of the device to be started during network startup.

[0014] This application embodiment also provides a device startup method, including: generating a second duration instruction when the device to be started is in local startup mode; transmitting the second duration instruction to the baseboard management controller of the device to be started to obtain a timeout duration from the baseboard management controller; wherein the timeout duration is a duration determined by a target object based on the network influence parameters of the device to be started, the network influence parameters being parameters that affect the network startup state of the device to be started, and the timeout duration being a set maximum duration for the device to be started to wait for a response during network startup; obtaining the timeout duration fed back by the baseboard management control, and performing network startup of the device to be started based on the timeout duration fed back by the baseboard management control.

[0015] This application embodiment also provides a device startup apparatus, comprising: a second generation module, configured to generate a second duration instruction when the device to be started is in local startup mode; a third transmission module, configured to transmit the second duration instruction to the baseboard management controller of the device to be started, so as to obtain a timeout duration from the baseboard management controller; wherein the timeout duration is a duration determined by a target object based on the network influence parameters of the device to be started, the network influence parameters being parameters that affect the network startup state of the device to be started, and the timeout duration being a set maximum duration for the device to be started to wait for a response during network startup; and an execution module, configured to obtain the timeout duration fed back by the baseboard management control, and execute the network startup of the device to be started based on the timeout duration fed back by the baseboard management control.

[0016] This application generates a second duration command when the device to be started is in local startup mode. This second duration command can then be transmitted to the baseboard management controller of the device to be started, allowing the acquisition of a timeout duration from the baseboard management controller. The timeout duration is determined by the target object based on the network impact parameters of the device to be started. These network impact parameters are parameters that affect the network startup state of the device to be started, and the timeout duration is the maximum set time for the device to wait for a response during network startup. The application also acquires the timeout duration feedback from the baseboard management control and executes the network startup of the device to be started based on this timeout duration. Compared to a fixed timeout duration, this dynamic timeout duration determined by network impact parameters avoids the problem of excessively long or short response waiting times during network startup, effectively improving the startup performance of the device to be started during network startup. Attached Figure Description

[0017] To more clearly illustrate the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 A structural block diagram of a computer terminal for a method of transmitting duration instructions provided in an embodiment of this application;

[0019] Figure 2 One of the flowcharts for a method of transmitting a duration instruction provided in an embodiment of this application;

[0020] Figure 3 A second flowchart illustrating another method for transmitting duration instructions provided in an embodiment of this application;

[0021] Figure 4 One of the flowcharts for the device startup method provided in the embodiments of this application;

[0022] Figure 5 A hardware structure block diagram of the duration instruction transmission method provided in the embodiments of this application;

[0023] Figure 6 The third flowchart of the method for transmitting duration instructions provided in the embodiments of this application;

[0024] Figure 7 The fourth flowchart of the method for transmitting duration instructions provided in the embodiments of this application;

[0025] Figure 8 A second flowchart illustrating the device startup method provided in this application embodiment;

[0026] Figure 9 One of the structural block diagrams of a duration instruction transmission device provided in this application embodiment;

[0027] Figure 10 A second structural block diagram of a duration instruction transmission device provided in an embodiment of this application;

[0028] Figure 11 This is a structural block diagram of a device starting apparatus provided in an embodiment of this application. Detailed Implementation

[0029] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the protection scope of this application.

[0030] It should be noted that, in the description of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. The terms "first," "second," etc., in this application are used to distinguish similar objects and are not used to describe a specific order or sequence.

[0031] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0032] The duration instruction transmission method embodiments provided in this application can be executed in a computer device, such as a computer terminal or a similar computing device. Taking running on a computer terminal as an example, Figure 1 This is a hardware structure block diagram of a computer terminal for a method of transmitting duration instructions according to an embodiment of this application. Figure 1 As shown, a computer terminal may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The computer terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the computer terminal described above. For example, the computer terminal may also include components that are more complex than those described above. Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0033] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the duration instruction transmission method in this embodiment. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thus implementing the above-described method. The memory 104 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to a computer terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0034] The transmission device 106 is used to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider for the server device. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module used for wireless communication with the Internet.

[0035] This application provides an embodiment of a method for transmitting duration instructions, applied to the aforementioned computer terminal. The method for transmitting duration instructions is described in detail below, along with its execution flow. For example... Figure 2 As shown, the method includes the following steps S202-S206:

[0036] S202, Receive the timeout duration determined by the target object based on the network impact parameters of the device to be started; wherein, the network impact parameters are parameters that affect the network startup status of the device to be started, and the timeout duration is the maximum duration set for the device to be started to wait for a response during network startup.

[0037] In this context, the target object refers to the entity that actively initiates a request to modify the timeout duration during network startup. The target object can be a system administrator, network administrator, automated management software, remote management tools, etc., and the timeout duration can be determined based on network impact parameters and specific requirements.

[0038] A device to be booted refers to an electronic device that can be remotely booted over a network, such as using PXE (Preboot Execution Environment, a network boot technology). During boot, a device to be booted may rely on network services, such as a DHCP (Dynamic Host Configuration Protocol) server or a TFTP (Trivial File Transfer Protocol) server, to obtain necessary boot parameters or an operating system image.

[0039] Network impact parameters refer to various factors that can affect the network startup status of the device to be started. Network impact parameters may include, but are not limited to, application scenarios, network bandwidth, latency, packet loss rate, network interface capabilities of the device to be started, and hardware performance involved in the startup process (network card type and speed, processor performance, memory size, etc.).

[0040] The timeout period refers to the maximum time limit for waiting for a network response during network startup. If no response is received from the network service within the timeout period, the startup process will be considered a failure or will switch to other startup options.

[0041] In some embodiments, the timeout duration can be calculated using a pre-defined algorithm or model based on network impact parameters. The timeout duration needs to fully consider the potential time extension caused by network impact parameters, while also minimizing excessively long waiting times to improve efficiency. For example, decision tree algorithms, neural network models, and rule-based methods can be used to calculate the timeout duration. When using decision tree algorithms, the timeout duration can be determined based on branch decisions under different network conditions. For example, in environments with high latency and high packet loss rates, a longer timeout duration than normal may need to be set. When using neural network models, by training on a large amount of historical data, the neural network can learn the non-linear relationship between different network environments and the timeout duration. Furthermore, for rule-based methods, a set of rules can be designed, such as "when network latency exceeds twice the average, the timeout duration increases by 50%."

[0042] In one exemplary embodiment, different network impact parameters can be assigned different weights when calculating the timeout duration. For example, in a network environment with a long server response time, the parameter weight for server response time may be higher in order to generate a longer timeout duration.

[0043] S204, Generate a first duration instruction based on the timeout duration;

[0044] In some embodiments, when the timeout duration is determined, a first duration instruction can be generated. The first duration instruction is a specific control instruction that can carry a predefined timeout duration and a duration identifier. The first duration instruction can be transmitted to the BMC (Baseboard Management Controller) via a specific network protocol (such as IPMI (Intelligent Platform Management Interface)) so that the BMC can instruct it to wait for the timeout duration or perform subsequent operations.

[0045] S206, a first duration instruction is transmitted to the baseboard management controller of the device to be started, instructing the baseboard management controller to store a timeout duration; wherein the timeout duration stored by the baseboard management controller is to be transmitted to the device to be started when the baseboard management controller receives a second duration instruction for the device to be started.

[0046] Understandably, the first duration instruction can generate a first duration instruction carrying the timeout duration. This first duration instruction carries the specific timeout duration and is transmitted to the BMC of the device to be started via the IPMI protocol. The IPMI protocol provides a set of command and communication mechanisms that allow computer terminals to interact with the BMC.

[0047] After receiving the first timeout instruction, the BMC can parse the instruction header to confirm that it is a correct IPMI command format. Then, the BMC searches for and identifies the fields related to the timeout duration for network startup, namely the timeout duration in the first timeout instruction.

[0048] Furthermore, after confirming the validity of the first timeout instruction, the BMC can store the timeout duration in its internal non-volatile memory, such as EEPROM (Electrically Erasable Programmable Read-Only Memory). The stored timeout duration can be used in subsequent network startup processes to control the time spent waiting for server responses during network startup.

[0049] It should be noted that when the device to be started needs to perform network startup or when network conditions change, a second duration command can be generated. This second duration command can be transmitted from the device to be started to the BMC or from the computer terminal to the BMC.

[0050] In some embodiments, when a device to be booted performs a network boot, the BMC can transmit a stored timeout duration as part of the boot parameters to the device's BIOS (Basic Input / Output System) or bootloader via a specific network protocol (such as PXE). The device's BIOS or bootloader (such as a server) then controls the waiting time during the network boot process based on the timeout duration received from the BMC. For example, when attempting to obtain network configuration information from a DHCP server, the maximum waiting time is determined based on the timeout duration.

[0051] In the above embodiments, by transmitting the first duration instruction to the BMC of the device to be started, and dynamically adjusting and transmitting the timeout duration to the device to be started when the BMC receives the second duration instruction, this process realizes the flexible configuration and automatic adaptation of network startup parameters.

[0052] In steps S202-S206 above, the target object receives the timeout duration determined based on the network impact parameters of the device to be started. Then, a first duration instruction is generated based on the timeout duration. This first duration instruction is transmitted to the baseboard management controller of the device to be started, instructing the baseboard management controller to store the timeout duration. Thus, when the baseboard management controller receives a second duration instruction from the device to be started, the timeout duration can be transmitted to the device. In other words, storing the dynamically determined timeout duration in the baseboard management controller and transmitting it to the device when the baseboard management controller receives a second duration instruction for the device to be started provides a dynamic timeout duration determined by network impact parameters, compared to a fixed timeout duration. This avoids excessively long or short response times during network startup, effectively improving the startup performance of the device during network startup.

[0053] In some exemplary embodiments, receiving the timeout duration determined by the target object based on the network impact parameters of the device to be started includes: receiving a path access instruction from the target object; accessing a parameter setting interface in response to the path access instruction; and receiving the timeout duration determined by the target object based on the network impact parameters of the device to be started based on the parameter setting interface.

[0054] Here, a path access command refers to a command or request issued by the target object to access the parameter setting interface. Path access commands can be implemented through network management software, command-line tools, or automation scripts. The parameter setting interface refers to the interface or screen that allows the target object to modify the timeout duration. In this embodiment, the parameter setting interface can be a BIOS settings menu, an IPMI command interface, or a settings page provided through a management interface such as a RESTful API (Representational State Transfer Application Programming Interface). The parameter setting interface is the interaction point between the target object and the device to be started for adjusting the timeout duration.

[0055] In some embodiments, the target object sends an IPMI command or API request to a computer terminal via network management software or a command-line tool to access the parameter setting interface. The computer terminal responds to the path access command, providing the parameter setting interface or API, allowing the target object to view and modify the PXE boot timeout duration. Further, the target object can enter a timeout duration determined based on network impact parameters in the parameter setting interface, and send the modified timeout duration to the BMC via an update command or API request to update the PXE boot timeout setting of the device to be booted.

[0056] In the above embodiments, the determination and adjustment of the timeout duration of the target object based on network impact parameters are effectively supported, thereby optimizing the network response waiting time of the PXE startup process and improving startup efficiency and reliability.

[0057] In some exemplary embodiments, receiving the timeout duration determined by the target object based on the network impact parameters of the device to be started, based on the parameter setting interface, includes: querying the duration setting option in the parameter setting interface to obtain the query result; wherein, the duration setting option is used to set the timeout duration parameter in the duration setting option to the written timeout duration when the written timeout duration is received; if the query result shows that the duration setting option exists in the parameter setting interface, the timeout duration determined by the target object based on the network impact parameters of the device to be started is written into the duration setting option; if the query result shows that the duration setting option does not exist in the parameter setting interface, a new duration setting option is added, and the timeout duration determined by the target object based on the network impact parameters of the device to be started is written into the newly added duration setting option.

[0058] The duration setting option refers to the network startup configuration options, allowing users or management software to customize the timeout duration.

[0059] In some instances, the timeout duration setting option is queried through the parameter settings interface to check its existence or configuration. If the timeout setting option exists in the parameter settings interface, the timeout duration determined for the target object is directly entered into it. If the timeout setting option does not exist, a new timeout setting option is first added to the parameter settings interface, and then the timeout duration is entered into the new option.

[0060] In a specific application, the duration setting option refers to "PXE BOOT TIMEOUT," which is located under the "Advanced->Miscellaneous Configuration" menu in the computer terminal and is a numerical option. The timeout duration can be set from 5 to 300 seconds and is used to control the waiting time during the network startup process.

[0061] The above embodiments ensure the flexibility and accuracy of the timeout duration setting, enabling the device to be started to dynamically adjust the startup strategy according to the actual network conditions, thereby improving the efficiency and success rate of network startup.

[0062] In an exemplary embodiment, the first duration instruction carries a timeout duration; transmitting the first duration instruction to the baseboard management controller of the device to be started to instruct the baseboard management controller to store the timeout duration includes: transmitting the first duration instruction to the baseboard management controller to instruct the baseboard management controller to parse the first duration instruction, extract a duration identifier from the first duration instruction, and, if it is determined based on the duration identifier that the first duration instruction is for network startup, extract the timeout duration from the first duration instruction and store the timeout duration.

[0063] The duration identifier is used to distinguish instruction types, ensuring that the BMC can recognize that the first duration instruction is for setting a network startup timeout duration. The duration identifier can be any identifier that can be used for type identification, such as letters, numbers, or feature codes. In this embodiment, the duration identifier can be implemented through a specific header, such as "_PXETO_", which helps the BMC identify and correctly process the instruction.

[0064] Specifically, the computer terminal sends a first duration command to the BMC via the network management interface. This command includes a duration identifier "_PXETO_" and a timeout duration. Upon receiving the first duration command, the BMC parses the command and extracts the duration identifier, determining whether the command is related to the network startup timeout setting. If the duration identifier is "_PXETO_", the command is confirmed to be related to the network startup timeout setting, and the BMC further extracts the timeout duration from the command. Furthermore, the BMC stores the extracted timeout duration in a specified location in the EEPROM, completing the timeout duration update.

[0065] In the above embodiments, the accuracy and reliability of the timeout duration setting are ensured, enabling the BMC to correctly store and apply the first duration instruction sent by the computer terminal through the network management interface.

[0066] In an exemplary embodiment, the method for transmitting the duration instruction further includes: obtaining a target status identifier of the device to be started; matching the target status identifier of the device to be started with status identifiers in a pre-set status identifier database to determine a status identifier that matches the target status identifier; wherein the status identifier database includes multiple status identifiers and device states corresponding to the multiple status identifiers respectively; if the device state of the device to be started corresponding to the status identifier that matches the target status identifier is a local startup state, determining a second duration instruction; wherein the second duration instruction carries a timeout duration; and transmitting the second duration instruction to the baseboard management controller of the device to be started to instruct the baseboard management controller to feed back the timeout duration to the device to be started.

[0067] It should be noted that the target status identifier of the device to be started refers to the identifier used to characterize the current startup status of the device to be started, indicating whether the device to be started is currently in the network startup phase, the local startup phase, or other startup phases.

[0068] A status identifier database is a database or configuration file stored in a system that contains multiple status identifiers and their corresponding device states. In this application, the status identifier database is used to store status identifiers for different boot modes, such as "PXE" and "LOCAL (local)," as well as the specific device states represented by these identifiers (such as network boot and local boot). Querying the status identifier database helps determine the current boot mode of the device to be booted.

[0069] The second duration instruction is a command that carries a timeout duration. It is generated and sent when the device status corresponding to the target status identifier of the device to be booted is in network boot status. Unlike the first duration instruction, the purpose of the second duration instruction is to notify the BMC to send the timeout duration to the BIOS of the booting device for application in subsequent network boots.

[0070] Specifically, the computer terminal can query the status identifier database of the device to be booted to determine the target status identifier of the device and confirm whether it is in a local boot state. The target status identifier is matched with the status identifiers in the status identifier database to determine the current boot state of the device to be booted. If the device state corresponding to the matched status identifier is in a local boot state, a second duration command carrying the timeout duration is generated. The second duration command is sent to the BMC of the device to be booted through the network management interface. The BMC receives and parses the second duration command, and then feeds back the timeout duration to the BIOS to ensure that the PXE boot timeout duration is correctly applied in the local boot state.

[0071] In the above embodiments, the timeout duration of PXE startup can be intelligently adjusted according to the device status of the device to be started, thereby improving the efficiency of the startup process and the user experience.

[0072] In an exemplary embodiment, the method for transmitting the duration instruction further includes: upon receiving an update timeout duration determined by the target object, generating a third duration instruction; wherein the update timeout duration is a new timeout duration determined by the target object based on the current network startup state of the network startup of the device to be started; transmitting the third duration instruction to the baseboard management controller of the device to be started to instruct the baseboard management controller to clear the stored timeout duration; upon receiving a clear instruction from the baseboard management controller, generating a fourth duration instruction based on the update timeout duration; and sending the fourth duration instruction to the baseboard management controller of the device to be started to instruct the baseboard management controller to store the update timeout duration.

[0073] The update timeout duration refers to the new timeout duration adjusted by the target object based on the current network startup status of the device to be started (such as network latency, server response time, etc.). The determination of the update timeout duration aims to optimize the PXE startup process and ensure that the startup process can be carried out more efficiently and reliably when network conditions change.

[0074] The third timeout instruction is used to instruct the Baseboard Management Controller (BMC) of the device to be started to clear the currently stored timeout duration. Before updating the network startup timeout duration, the original timeout setting must be cleared to avoid the old setting affecting the effectiveness of the new setting.

[0075] After successfully clearing the stored timeout duration, the BMC sends a fourth timeout instruction to the computer terminal. Receiving the fourth timeout instruction is a prerequisite for generating the fifth timeout instruction, ensuring that the old timeout duration setting has been deleted so that the new timeout duration can be applied correctly.

[0076] The fifth duration instruction is used to instruct the BMC to store the update timeout duration determined for the target object. After the fourth duration instruction is received, the fifth duration instruction is generated based on the update timeout duration to ensure that the new timeout duration setting is permanently saved for use on the next startup.

[0077] Specifically, upon receiving the updated timeout duration, a third duration command is first generated, instructing the BMC to clear the original timeout duration setting. This third duration command is sent to the BMC via the network management interface, and the BMC performs the clearing operation. Upon receiving confirmation from the BMC that the clearing command has been received, it is confirmed that the old setting has been cleared. Based on the updated timeout duration, a fourth duration command is generated and sent to the BMC via the network management interface, instructing it to store the new timeout duration.

[0078] In the above embodiments, the update process of network startup timeout duration is ensured to proceed in an orderly manner, avoiding interference from old settings to new settings, and improving the flexibility and efficiency of network startup.

[0079] In an exemplary embodiment, after receiving the timeout duration determined by the target object based on the network impact parameters of the device to be started, and before generating a first duration instruction based on the timeout duration, the method for transmitting the duration instruction further includes: responding to a duration verification operation triggered by the target object; obtaining a preset standard duration range based on the duration verification operation; comparing the timeout duration with the preset standard duration range; and, if the timeout duration is not within the standard duration range, sending a warning message to the target object.

[0080] Understandably, the timeout validation operation is initiated by the target object to verify whether the timeout duration is within the standard range. This operation ensures the reasonableness of the PXE startup timeout setting and avoids problems that might arise from setting the timeout too short or too long.

[0081] The preset standard timeout range is set based on best practices and requirements for network startup. The effective range for the timeout is, as mentioned in the embodiments of this application, 5 seconds to 300 seconds. The establishment of the standard timeout range is to ensure the stability and efficiency of network startup and to avoid inappropriate timeout value settings.

[0082] Specifically, after receiving the timeout duration determined by the target object based on the network impact parameters of the device to be started, the computer terminal automatically triggers a duration verification operation to prepare for verifying the reasonableness of the timeout duration. Further, it obtains the valid range of the PXE startup timeout duration (e.g., 5-300 seconds) from the system configuration or preset rules. It compares the timeout duration provided by the target object with the preset standard duration range to check if it exceeds the reasonable range. If the timeout duration is not within the standard duration range, a warning message is sent to the target object, indicating that the timeout duration setting is unreasonable and may affect PXE startup performance or stability.

[0083] In the above embodiments, the verification mechanism ensures the security and effectiveness of the network startup timeout setting, avoiding startup failure or resource waste due to improper settings.

[0084] In one exemplary embodiment, such as Figure 3 As shown, this application also provides a method for transmitting duration instructions, applied to a baseboard management controller, including the following steps S302-S306:

[0085] S302, receive a first duration instruction generated based on the timeout duration transmitted by the computer terminal, wherein the timeout duration is the duration determined by the target object based on the network impact parameters of the device to be started, the network impact parameters are parameters that affect the network startup status of the device to be started, and the timeout duration is the maximum duration set for the device to be started to wait for a response during network startup.

[0086] In this context, the computer terminal refers to an external device or system capable of communicating with the Baseboard Management Controller (BMC), such as a server management interface, remote management software, or a PC running automated scripts. The computer terminal sends a first duration command to the BMC via a network interface (such as IPMI or a RESTful API interface) to set the PXE boot timeout duration for the device to be started.

[0087] S304, in response to the first duration instruction, stores the timeout duration carried in the first duration instruction.

[0088] Specifically, the BMC receives a first duration command from the computer terminal via the network interface. It extracts the timeout duration from the first duration command and verifies whether the timeout duration is within a preset reasonable range. If the timeout duration parameter passes the verification, the BMC stores it in non-volatile memory (such as EEPROM) for use on the next network startup.

[0089] S306: When the board management controller receives a second duration instruction for the device to be started, it transmits the timeout duration to the device to be started.

[0090] Specifically, when the BMC receives the second duration instruction, it can first determine whether the second duration instruction carries a duration identifier. If it is determined that the duration identifier is carried, the BMC can transmit the timeout duration to the BIOS or boot control module of the device to be booted.

[0091] In steps S302-S306 above, a first duration instruction transmitted from the computer terminal is received, and in response to the first duration instruction, the timeout duration carried in the first duration instruction is stored. Upon receiving a second duration instruction for the device to be started, the baseboard management controller transmits the timeout duration to the device to be started. In other words, the baseboard management controller can store the timeout duration determined by the target object based on network influence parameters, and transmit the timeout duration to the device to be started upon receiving the second duration instruction. Compared to a fixed timeout duration, this dynamic timeout duration determined by network influence parameters avoids the problem of excessively long or short response waiting times during network startup, effectively improving the startup performance of the device to be started in network startup.

[0092] In an exemplary embodiment, in response to a first duration instruction, storing the timeout duration carried in the first duration instruction includes: parsing the first duration instruction and extracting the duration identifier carried in the first duration instruction; if it is determined based on the duration identifier that the first duration instruction is for network startup, extracting the timeout duration from the first duration instruction and storing the timeout duration.

[0093] Specifically, after receiving the first duration instruction, the BMC decodes the instruction content and identifies the duration identifier within it. Based on the duration identifier, it determines whether the first duration instruction is related to network startup. If the first duration instruction is for network startup, the BMC further parses the instruction and extracts the timeout duration. The extracted timeout duration parameter is stored in the BMC's non-volatile memory (such as EEPROM) for use during subsequent network startup.

[0094] In the above embodiments, the BMC intelligently identifies and executes the first duration instruction for network startup, ensuring that the device to be started can store the timeout duration dynamically determined based on network impact parameters, thereby improving the efficiency and reliability of subsequent network startup.

[0095] In an exemplary embodiment, the method for transmitting the duration instruction further includes: obtaining a second duration instruction for the device to be started; wherein the second duration instruction is obtained through one of the following methods: obtaining a target status identifier of the device to be started through a computer terminal; matching the target status identifier of the device to be started with status identifiers in a pre-set status identifier database to determine a status identifier that matches the target status identifier; determining the device status of the device to be started corresponding to the status identifier that matches the target status identifier when it is in a local startup state; wherein the status identifier database includes multiple status identifiers and device states corresponding to the multiple status identifiers respectively; determining the device to be started when it determines that it is in a local startup state; and feeding back the stored timeout duration to the device to be started based on the second duration instruction, so that the device to be started can enter network startup.

[0096] Specifically, the target device obtains the target status identifier of the device to be started via a computer terminal to determine the device's startup mode. It matches the target status identifier with status identifiers in the status identifier database to determine if the device is currently in a local startup state. If the device status matches as local startup, it prepares to send a timeout duration, i.e., generates a second duration instruction; alternatively, the device to be started can generate the second duration instruction after determining it is in a local startup state. After obtaining the second duration instruction for the device to be started, the BMC sends the stored timeout duration back to the device to support its entry into network startup mode.

[0097] In the above embodiments, the BMC can obtain a second timeout instruction for the device to be started and feed back the stored timeout duration to the device to be started to support it in entering the network boot mode, thus ensuring the flexibility and efficiency of the boot process.

[0098] In an exemplary embodiment, the method for transmitting the duration instruction further includes: acquiring a third duration instruction transmitted by a computer terminal; wherein the third duration instruction is generated by the computer terminal upon receiving an update timeout duration determined by the target object; wherein the update timeout duration is a new timeout duration determined by the target object based on the actual network startup status of the device to be started; clearing the stored timeout duration based on the third duration instruction and feeding back a fourth duration instruction to the computer terminal; acquiring a fifth duration instruction fed back by the computer terminal; wherein the fifth duration instruction is generated by the computer terminal based on the update timeout duration upon receiving the fourth duration instruction; and storing the update timeout duration based on the fifth duration instruction.

[0099] Specifically, the BMC receives a third timeout instruction from the computer terminal to clear the stored timeout duration. The BMC performs the clearing operation, resetting the stored timeout duration to zero or setting it to a default value. After completing the clearing operation, the BMC generates and sends a fourth timeout instruction back to the computer terminal, indicating that the stored timeout duration has been cleared. After confirming the fourth timeout instruction, the computer terminal sends a fifth timeout instruction to the BMC, containing the updated timeout duration. The BMC parses the fifth timeout instruction and stores the updated timeout duration in non-volatile memory (such as EEPROM) for use during the next network boot of the device.

[0100] In the above embodiments, dynamic updates of the timeout duration are implemented, ensuring that the network startup of the device to be started can adjust the timeout duration according to the latest network environment changes, thereby improving the flexibility and efficiency of startup.

[0101] In one exemplary embodiment, such as Figure 4As shown, this application also provides a device startup method applied to a basic input / output system, including the following steps S402-S406:

[0102] S402 generates a second duration instruction when the device to be started is in local boot mode.

[0103] In this context, local boot refers to the booting process performed by the device from its internal hard drive or other local storage media, rather than booting from a network resource. In this application, the local boot state is defined in contrast to the network boot state.

[0104] Specifically, when the device to be started is in local boot state, the Basic Input / Output System (BIOS) generates a second duration command for subsequent querying of the timeout duration. The BIOS sends the second duration command to the BMC via a network interface (such as IPMI or RESTful API) to prepare to receive the timeout duration stored in the BMC.

[0105] S404, the second duration instruction is transmitted to the baseboard management controller of the device to be started, so as to obtain the timeout duration from the baseboard management controller; wherein, the timeout duration is the duration determined by the target object based on the network impact parameters of the device to be started, the network impact parameters are parameters that affect the network startup status of the device to be started, and the timeout duration is the maximum duration set for the device to be started to wait for a response during network startup.

[0106] S406: Obtain the timeout duration of the board management control feedback, and perform network startup of the device to be started based on the timeout duration of the board management control feedback.

[0107] Through steps S402-S406 above, when the device to be started is in local startup mode, a second duration command is generated. This second duration command can then be transmitted to the baseboard management controller of the device to be started to obtain the timeout duration from the baseboard management controller. The timeout duration is determined by the target object based on the network influence parameters of the device to be started. The network influence parameters are parameters that affect the network startup state of the device to be started, and the timeout duration is the maximum duration for the device to wait for a response during network startup. The timeout duration fed back by the baseboard management control is obtained, and the network startup of the device to be started is executed based on this timeout duration. Compared to a fixed timeout duration, this dynamic timeout duration determined by the network influence parameters avoids the problem of excessively long or short response waiting times during network startup, effectively improving the startup performance of the device to be started during network startup.

[0108] In one exemplary embodiment, performing network startup of the device to be started based on the timeout duration feedback from the baseboard management control includes: obtaining the timeout duration recorded by the basic input / output system; and performing network startup of the device to be started based on the timeout duration recorded by the basic input / output system or the timeout duration feedback from the baseboard management control.

[0109] The Basic Input / Output System (BIOS) is the firmware program on the device to be booted, used to initialize the hardware and load the operating system. It records, stores, and manages the timeout settings during the network boot process, ensuring that the device can perform network boot based on the latest timeout parameters.

[0110] The timeout duration fed back by the Baseboard Management Controller (BMC) refers to the timeout duration fed back to the BIOS of the device to be booted by the BMC, used to adjust the waiting time during network boot. The timeout duration recorded by the Basic Input / Output System (BMC) is a time parameter set within the BIOS; specifically, it refers to the time threshold stored in the BIOS used to control the waiting time for network response during network boot. This timeout duration can be directly modified by the user in the device's BIOS settings, or it can be dynamically updated through feedback information from the BMC.

[0111] Network boot refers to the process by which a device boots its operating system from a network resource (such as an operating system image on a TFTP server). The timeout setting determines how long the device waits for a network response during network boot, affecting boot speed and success rate.

[0112] Specifically, the BIOS of the device to be booted can obtain the timeout duration from local storage and feedback from the BMC. Based on the two obtained timeout durations, the BIOS can initiate the network boot process, interact with network resources such as DHCP server and TFTP server, and complete the loading of the operating system.

[0113] In the above embodiments, it is ensured that the device to be started can perform network boot according to the latest and more optimized timeout duration parameters, thereby improving the efficiency and reliability of the boot process. The BMC's feedback mechanism enables the timeout duration setting to be dynamically adjusted according to changes in the network environment, enhancing the system's adaptability to complex network conditions.

[0114] In an exemplary embodiment, network startup of the device to be started is performed based on the timeout duration recorded by the Basic Input / Output System (BIOS) or the timeout duration fed back by the Baseboard Management Control (BMC). This includes: if the timeout duration fed back by the BMC is a first target value, performing network startup of the device to be started based on the timeout duration recorded by the BIOS; and performing network startup of the device to be started based on the timeout duration fed back by the Baseboard Management Controller (BMC) in any of the following situations: the timeout duration recorded by the BIOS and the timeout duration fed back by the BMC are inconsistent; the timeout duration recorded by the BIOS is a second target value; wherein the first target value and the second target value are different; and the timeout duration recorded by the BIOS and the timeout duration fed back by the BMC are consistent.

[0115] The first target value refers to the specific timeout duration reported by the BMC to the BIOS under certain conditions. When the timeout duration reported by the BMC is the first target value, the BIOS will prioritize using its own stored timeout duration for network booting. This means that the first target value may be considered a default or a special value that is not applied. Unlike the first target value, the second target value is another specific timeout duration value. When the timeout duration recorded by the BIOS is the second target value, but it differs from the timeout duration reported by the BMC, network booting will use the timeout duration reported by the BMC, indicating that the second target value activates the dynamic adjustment mechanism for the timeout duration.

[0116] Specifically, during the boot process, the BIOS checks whether the timeout duration recorded locally matches the timeout duration reported by the BMC. If the timeout duration reported by the BMC is the first target value, the BIOS will ignore the feedback and use the locally recorded timeout duration to perform network boot. If the timeout duration recorded by the BIOS and reported by the BMC are inconsistent, or if the timeout duration recorded by the BIOS is the second target value, the BIOS will use the timeout duration reported by the BMC for network boot. Based on the finally determined timeout duration, the BIOS initiates the network boot process, attempting to obtain boot files or configuration information from network resources.

[0117] In the above embodiments, it is ensured that the device to be started can perform network boot according to the most suitable timeout settings. Through the intervention of BMC, the ability to dynamically adjust the timeout duration is provided, which enhances the flexibility and adaptability of network boot.

[0118] In one exemplary embodiment, performing network startup of the device to be started based on the timeout duration recorded by the basic input / output system or the timeout duration fed back by the board management controller includes: obtaining the actual timeout duration of the network startup process; comparing the actual timeout duration with the timeout duration recorded by the basic input / output system or the timeout duration fed back by the board management controller; and determining that the network startup process has timed out if the actual timeout duration is greater than the timeout duration recorded by the basic input / output system or the timeout duration fed back by the board management controller.

[0119] The actual timeout duration is the time the device actually waits for a network response during the network boot process. This time can vary dynamically and is affected by factors such as network latency and server response speed. When the actual timeout duration of the network boot process exceeds the timeout duration recorded by the BIOS or reported by the BMC, the network boot process is considered to have timed out. This usually results in the network boot attempt being terminated, and the device will attempt to boot from another boot source.

[0120] Specifically, when performing network boot, the BIOS records the time from the start of the boot attempt to receiving a network response. The actual timeout duration is compared with the timeout duration recorded by the BIOS or reported by the BMC. If the actual timeout duration exceeds the preset timeout duration, the network boot process is determined to have timed out, triggering a timeout handling procedure, such as attempting to boot from another source.

[0121] In the above embodiments, the efficiency and reliability of network startup are ensured. By comparing the dynamic actual network response time with the preset timeout duration, timeout situations during network startup can be identified and handled in real time, avoiding unnecessary waiting and improving the efficiency of device startup.

[0122] The embodiments described above are merely some embodiments of this application, and not all embodiments. To better understand the above methods, the following description, in conjunction with embodiments, illustrates the process, but is not intended to limit the technical solutions of the embodiments of this application. Specifically:

[0123] PXE (Preboot Execution Environment) is a network boot technology that allows users to boot computers from a network without using local storage (such as a hard drive). PXE uses a special network protocol called the Preboot Execution Protocol (PXE), which allows client machines to obtain the necessary boot files from the network. PXE supports multiple operating systems, including Windows, Linux, and Mac OS X. Its main applications include automated system installation, system maintenance, system disaster recovery, remote system updates, virtualization deployment, and network booting. It offers significant advantages in various scenarios, including reduced installation time, lower maintenance costs, improved security and reliability, timely updates, reduced deployment time, improved deployment efficiency, and improved system boot efficiency. Due to these advantages, PXE booting has become increasingly popular and has become an important component of enterprise network management, while also being widely used on servers. During the PXE boot process, the client interacts with DHCP (Dynamic Host Configuration Protocol) servers, TFTP (Trivial File Transfer Protocol) servers, and HTTP (Hypertext Transfer Protocol) servers to obtain necessary network configuration information and boot files.

[0124] Setting the timeout duration becomes a crucial step in this process. Different stages have different timeout requirements. For example, when the client requests the address and startup file from the server, if the server does not respond for a long time, the client cannot wait indefinitely; otherwise, it will greatly prolong the startup time and may even lead to startup failure. For enterprise environments that prioritize efficiency, such a waiting time is unacceptable. Similarly, in the scenario where the boot menu is displayed during PXE startup, a reasonable timeout duration also needs to be set. If the timeout duration is too long, users may become frustrated due to the prolonged wait; if it is too short, users may not have enough time to make a selection, resulting in a startup process that is not what the user expects.

[0125] Furthermore, when a PXE client sends a boot service discovery message and does not receive a response from the server, it typically checks for a response from the server once per second by default, continuing this check for 4 seconds before giving up. However, in some complex network environments, a 4-second wait time may be too short, causing some potentially successful boot operations to be prematurely abandoned; while in other scenarios where rapid response is crucial, 4 seconds may be too long. Therefore, the timeout duration should not be a fixed value, but rather something that can be arbitrarily set by the target object based on the application scenario, client configuration, network card capabilities, etc. Thus, a solution for setting the PXE boot timeout duration is needed.

[0126] refer to Figure 5 The diagram shown illustrates the hardware structure of the timing instruction transmission method in this application. Specifically, it may involve a Baseboard Management Controller (BMC), a Basic Input / Output System (BIOS), and Intelligent Platform Management Interface (IPMI) software, i.e., IPMI management software and the IPMI interface. The BMC and BIOS can be components on the device to be booted. External or remote devices, such as computer terminals, can establish communication connections with the BMC and BIOS through the IPMI management software. The BMC and BIOS can also communicate with each other through the IPMI interface.

[0127] Taking the BMC end as an example, refer to Figure 6 The diagram shown illustrates the information storage process (i.e., storage of timeout duration), which includes the following steps:

[0128] S601 generates the first duration instruction, i.e., the IPMI command, which is used to set the timeout duration for network startup, including: _PXETO_ (flag bit, i.e., duration identifier), timeout duration PXETO, etc.

[0129] S602, when the BMC receives the IPMI command to add a new PXE startup timeout duration, it parses and determines whether the information header is _PXETO_;

[0130] S603, if the information header, i.e. the identifier bit, is _PXETO_, proceed to S604; otherwise, proceed to S605;

[0131] S604, add a new variable UINT16 (unsigned 16-bit integer) PXETO to store the desired PXE startup timeout duration, and then proceed to S606.

[0132] S605, returned 01, indicating an error in the header information, end;

[0133] S606, parse IPMI command information sequentially;

[0134] S607, determine the validity of the parsed information. If valid, proceed to S608; otherwise, proceed to S609.

[0135] S608 updates the timeout duration to the storage cell, i.e., the information at a specified location in the non-volatile memory EEPROM;

[0136] S609, Return 03, Flag data setting error.

[0137] refer to Figure 7 The diagram shown illustrates the information query process (i.e., the query for timeout duration), which includes the following steps:

[0138] S701 adds a second duration command, namely the IPMI command, which is used to query the PXE boot timeout duration;

[0139] S702, when the BMC receives the IPMI command to query the PXE startup timeout duration, it parses and determines that the information header is _PXETO_;

[0140] S703, if the message header is _PXETO_, proceed to S704; otherwise, proceed to S705;

[0141] S704, add a new variable UINT16 PXETO to store the set PXE startup timeout duration, and then proceed to S706;

[0142] S705, returned 01, indicating an error in the header information, end;

[0143] S706: Obtain the PXE boot timeout duration from the specified location in the EEPROM as required and fill it into PXETO. If there is no information, the value will be 0.

[0144] S707, After the PXETO message is escaped, it returns successfully according to the specified rules; End.

[0145] The information deletion process (i.e., deletion of timeout duration) is as follows: A new IPMI command is added to delete the PXE boot timeout duration. When the BMC receives the IPMI command to delete the PXE boot timeout duration, it parses and determines whether the header is _PXETO_. If the header is _PXETO_, the area storing the PXE boot timeout duration in the EEPROM is erased and 00 is returned, indicating that the PXE boot timeout duration has been successfully deleted; otherwise, 01 is returned, indicating an error in the header, and the process ends.

[0146] During the device startup process, the BIOS acts as the execution entity, referencing... Figure 8 The diagram shown illustrates the startup process of the device, which includes the following steps:

[0147] S801, the server (i.e., the device to be started) is powered on;

[0148] S802, add a new UINT16 local variable A (i.e. PxeTimeoutEeprom (EEPROM storage variable for PXE boot timeout duration)) and assign it an initial value of 0. The BIOS queries the PXE boot timeout duration command to check whether a timeout duration has been set. If the query returns a value, the query return value is assigned to PxeTimeoutEeprom.

[0149] S803, add a new UINT16 local variable B (PxeBootTimeout (page setup variable for PXE boot timeout duration)) and assign it an initial value of 20. Use the getVariable function (a function used to read variable values) to get the current value of the page setup option (i.e., PXE BOOT TIMEOUT) from NVRAM and assign the return value to PxeBootTimeout.

[0150] S804, determine whether PxeTimeoutEeprom is equal to PxeBootTimeout or whether PxeTimeoutEeprom is equal to 0. If yes, proceed to S806; otherwise, proceed to S805.

[0151] S805, assign PxeTimeoutEeprom to PxeBootTimeout, use PxeBootTimeout to update the current value of the PXE BOOT TIMEOUT option in NVRAM (non-volatile random access memory) through the setVariable function (a function used to update the value of a specific variable), and then proceed to S806;

[0152] S806, determine whether the boot process starts from PXE; if yes, proceed to S807; otherwise, end.

[0153] S807, add a new UINT16 (unsigned 16-bit integer) local variable PxeBootTimeout and assign it an initial value of 20. Use the getVariable function to get the current value of the PXE BOOT TIMEOUT option from NVRAM and assign the return value to PxeBootTimeout. If the return value is abnormal, use the initial value.

[0154] S808 passes PxeBootTimeout as a timeout duration parameter to the function, and performs timeout duration determination inside the function.

[0155] S809, if the duration of entering PXE exceeds the input timeout duration, then proceed to S810; otherwise, proceed to S811.

[0156] S810, determined that BOOT (boot) timed out and proceeded to the next boot option;

[0157] S811, PXE boot successful, proceed with further operations; End.

[0158] This application proposes a solution for setting the PXE boot timeout duration. This effectively resolves platform and device compatibility issues, improving platform compatibility and preventing frequent customer complaints caused by incompatibility problems leading to PXE or HTTP access failures. This flexible configuration also allows for precise fault location; setting a short timeout quickly exposes DHCP / TFTP service unreachability issues, and combined with packet capture analysis, it can quickly pinpoint network or service layer anomalies. It also provides a user-configurable option, allowing users to resolve issues themselves from the client side, avoiding the need to provide customized BIOS versions each time, effectively reducing manpower requirements. This also allows for quick client-side resolution, giving users greater confidence in using the device, providing better service, and winning more market share.

[0159] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method.

[0160] Embodiments of this application also provide a duration instruction transmission device and a device startup device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the modules described in the following embodiments are preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0161] Figure 9 This is a structural block diagram of a duration instruction transmission device according to an embodiment of this application. The device includes:

[0162] The first receiving module 902 is used to receive the timeout duration determined by the target object based on the network impact parameters of the device to be started; wherein, the network impact parameters are parameters that affect the network startup state of the device to be started, and the timeout duration is the maximum duration set for the device to be started to wait for a response during network startup;

[0163] The first generation module 904 is used to generate a first duration instruction based on the timeout duration;

[0164] The first transmission module 906 is configured to transmit the first duration instruction to the baseboard management controller of the device to be started, so as to instruct the baseboard management controller to store the timeout duration; wherein the timeout duration stored by the baseboard management controller is to be transmitted to the device to be started when the baseboard management controller receives a second duration instruction for the device to be started.

[0165] The aforementioned device receives the timeout duration determined by the target object based on the network impact parameters of the device to be started. Then, it generates a first duration instruction based on the timeout duration and transmits this instruction to the baseboard management controller of the device to be started, instructing the baseboard management controller to store the timeout duration. Thus, when the baseboard management controller receives a second duration instruction from the device to be started, the timeout duration can be transmitted to the device. In other words, by storing the dynamically determined timeout duration in the baseboard management controller and transmitting it to the device when the baseboard management controller receives a second duration instruction for the device to be started, compared to a fixed timeout duration, this dynamic timeout duration determined by network impact parameters avoids the problem of excessively long or short response times during network startup, effectively improving the startup performance of the device to be started in network startup.

[0166] In an exemplary embodiment, the first receiving module 902 is further configured to receive a path access instruction for the target object; in response to the path access instruction, access the parameter setting interface; and based on the parameter setting interface, receive the timeout duration determined by the target object based on the network impact parameters of the device to be started.

[0167] In an exemplary embodiment, the first receiving module 902 is further configured to query the duration setting option in the parameter setting interface and obtain a query result; wherein, the duration setting option is configured to, when a written timeout duration is received, set the timeout duration parameter in the duration setting option to the written timeout duration; when the query result indicates that the duration setting option exists in the parameter setting interface, write the timeout duration determined by the target object based on the network impact parameters of the device to be started into the duration setting option; when the query result indicates that the duration setting option does not exist in the parameter setting interface, add the duration setting option and write the timeout duration determined by the target object based on the network impact parameters of the device to be started into the newly added duration setting option.

[0168] In an exemplary embodiment, the first duration instruction carries the timeout duration; the first transmission module 906 is further configured to transmit the first duration instruction to the baseboard management controller to instruct the baseboard management controller to parse the first duration instruction, extract a duration identifier from the first duration instruction, and, if it is determined based on the duration identifier that the first duration instruction is for network startup, extract the timeout duration from the first duration instruction and store the timeout duration.

[0169] In an exemplary embodiment, the first transmission module 906 is further configured to: acquire a target status identifier of the device to be started; match the target status identifier of the device to be started with status identifiers in a pre-set status identifier database to determine a status identifier that matches the target status identifier; wherein the status identifier database includes multiple status identifiers and device states corresponding to the multiple status identifiers respectively; if the device state of the device to be started corresponding to the status identifier that matches the target status identifier is a local startup state, determine a second duration instruction; wherein the second duration instruction carries the timeout duration; and transmit the second duration instruction to the baseboard management controller of the device to be started to instruct the baseboard management controller to feed back the timeout duration to the device to be started.

[0170] In an exemplary embodiment, the first transmission module 906 is further configured to, upon receiving an update timeout duration determined by the target object, generate a third duration instruction; wherein the update timeout duration is a new timeout duration determined by the target object based on the current network startup state of the network startup of the device to be started; transmit the third duration instruction to the baseboard management controller of the device to be started to instruct the baseboard management controller to clear the stored timeout duration; upon receiving a fourth duration instruction from the baseboard management controller, generate a fifth duration instruction based on the update timeout duration; and send the fifth duration instruction to the baseboard management controller of the device to be started to instruct the baseboard management controller to store the update timeout duration.

[0171] In an exemplary embodiment, the device further includes a verification module; the verification module is configured to respond to a duration verification operation triggered by the target object; obtain a preset standard duration range based on the duration verification operation; compare the timeout duration with the preset standard duration range; and, if the timeout duration is not within the standard duration range, send a warning message to the target object.

[0172] Figure 10 This is a structural block diagram of a transmission apparatus for duration instructions according to another embodiment of this application, the apparatus comprising:

[0173] The second receiving module 1002 is used to receive a first duration instruction generated based on a timeout duration transmitted by a computer terminal, wherein the timeout duration is the duration determined by the target object based on the network influence parameters of the device to be started, the network influence parameters are parameters that affect the network startup status of the device to be started, and the timeout duration is the maximum duration set for the device to be started to wait for a response during network startup.

[0174] The response module 1004 is configured to respond to the first duration instruction by storing the timeout duration carried in the first duration instruction;

[0175] The second transmission module 1006 is used to transmit the timeout duration to the device to be started when the baseboard management controller receives a second duration instruction for the device to be started.

[0176] The aforementioned device receives a first duration instruction transmitted from a computer terminal, and in response to the first duration instruction, stores the timeout duration carried in the first duration instruction. Upon receiving a second duration instruction for the device to be started, the baseboard management controller transmits the timeout duration to the device to be started. In other words, the baseboard management controller can store a timeout duration determined by network influence parameters based on the target object, and transmit the timeout duration to the device to be started upon receiving the second duration instruction. Compared to a fixed timeout duration, this dynamic timeout duration determined by network influence parameters avoids the problem of excessively long or short response times during network startup, effectively improving the startup performance of the device to be started during network startup.

[0177] In an exemplary embodiment, the response module 1004 is further configured to parse the first duration instruction, extract the duration identifier carried by the first duration instruction; and, if it is determined based on the duration identifier that the first duration instruction is for network startup, extract the timeout duration from the first duration instruction and store the timeout duration.

[0178] In an exemplary embodiment, the second transmission module 1006 is further configured to acquire a second duration instruction for the device to be started; wherein the second duration instruction is obtained through one of the following methods: acquiring a target status identifier of the device to be started through the computer terminal; matching the target status identifier of the device to be started with status identifiers in a pre-set status identifier database to determine a status identifier that matches the target status identifier; determining the device status of the device to be started corresponding to the status identifier that matches the target status identifier when it is in a local startup state; wherein the status identifier database includes multiple status identifiers and device states corresponding to the multiple status identifiers respectively; determining the device to be started when it determines that it is in a local startup state; and feeding back the stored timeout duration to the device to be started based on the second duration instruction, so that the device to be started can enter network startup.

[0179] In an exemplary embodiment, the second transmission module 1006 is further configured to acquire a third duration instruction transmitted by the computer terminal; wherein the third duration instruction is generated by the computer terminal upon receiving an update timeout duration determined by the target object; wherein the update timeout duration is a new timeout duration determined by the target object based on the actual network startup status of the device to be started; based on the third duration instruction, clear the stored timeout duration and feed back a fourth duration instruction to the computer terminal; acquire a fifth duration instruction fed back by the computer terminal; wherein the fifth duration instruction is generated by the computer terminal based on the update timeout duration upon receiving the fourth duration instruction; and store the update timeout duration based on the fifth duration instruction.

[0180] Figure 11 This is a structural block diagram of a device starting apparatus according to an embodiment of this application. The apparatus includes:

[0181] The second generation module 1102 is used to generate a second duration instruction when the device to be started is in local startup mode.

[0182] The third transmission module 1104 is used to transmit the second duration instruction to the baseboard management controller of the device to be started, so as to obtain the timeout duration from the baseboard management controller; wherein, the timeout duration is the duration determined by the target object based on the network influence parameters of the device to be started, the network influence parameters are parameters that affect the network startup status of the device to be started, and the timeout duration is the maximum duration set for the device to be started to wait for a response during network startup;

[0183] The execution module 1106 is used to obtain the timeout duration of the baseboard management control feedback, and to perform network startup of the device to be started based on the timeout duration of the baseboard management control feedback.

[0184] Using the aforementioned device, when the device to be started is in local startup mode, a second duration command is generated. This second duration command can then be transmitted to the baseboard management controller of the device to be started, so as to obtain the timeout duration from the baseboard management controller. The timeout duration is determined by the target object based on the network influence parameters of the device to be started. The network influence parameters are parameters that affect the network startup state of the device to be started, and the timeout duration is the maximum duration for the device to wait for a response during network startup. The timeout duration fed back by the baseboard management control is obtained, and the network startup of the device to be started is executed based on the timeout duration fed back by the baseboard management control. Compared to a fixed timeout duration, this dynamic timeout duration determined by the network influence parameters avoids the problem of excessively long or short waiting times for responses during network startup, and can effectively improve the startup performance of the device to be started during network startup.

[0185] In an exemplary embodiment, the execution module 1106 is further configured to obtain the timeout duration recorded by the basic input / output system; and to perform network startup of the device to be started based on the timeout duration recorded by the basic input / output system or the timeout duration fed back by the baseboard management control.

[0186] In an exemplary embodiment, the execution module 1106 is further configured to perform network startup of the device to be started based on the timeout duration recorded by the basic input / output system when the timeout duration fed back by the baseboard management control is a first target value; and to perform network startup of the device to be started based on the timeout duration fed back by the baseboard management controller in any of the following situations: the timeout duration recorded by the basic input / output system is inconsistent with the timeout duration fed back by the baseboard management controller; the timeout duration recorded by the basic input / output system is a second target value; wherein the first target value and the second target value are different; and the timeout duration recorded by the basic input / output system is consistent with the timeout duration fed back by the baseboard management controller.

[0187] In an exemplary embodiment, the execution module 1106 is further configured to obtain the actual timeout duration of the network startup process; compare the actual timeout duration with the timeout duration recorded by the basic input / output system or the timeout duration fed back by the baseboard management controller; and determine that the network startup process has timed out if the actual timeout duration is greater than the timeout duration recorded by the basic input / output system or the timeout duration fed back by the baseboard management controller.

[0188] For a description of the features in the embodiment corresponding to the duration instruction transmission device, please refer to the relevant description of the embodiment corresponding to the duration instruction transmission method. For a description of the features in the embodiment corresponding to the device startup device, please refer to the relevant description of the embodiment corresponding to the device startup method. They will not be repeated here.

[0189] Embodiments of this application also provide an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any of the above-described duration instruction transmission method or device startup method embodiments.

[0190] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in the embodiments of the transmission method or device startup method of any of the above-described duration instructions when it is run.

[0191] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0192] The embodiments of this application also provide a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the steps in the embodiments of the transmission method or device startup method of any of the above-described duration instructions.

[0193] Embodiments of this application also provide another computer program product, including a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in the embodiments of the transmission method or device startup method of any of the above-described duration instructions.

[0194] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0195] The foregoing has provided a detailed description of the method for transmitting duration instructions and the method for starting a device provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are merely for the purpose of helping to understand the method and its core ideas. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from its principles, and these improvements and modifications also fall within the protection scope of the claims of this application.

Claims

1. A method for transmitting duration instructions, characterized in that, include: The system receives a timeout duration determined by the target object based on the network impact parameters of the device to be started; wherein the network impact parameters are parameters that affect the network startup state of the device to be started, and the timeout duration is a set maximum duration for the device to be started to wait for a response during network startup; A first duration instruction is generated based on the timeout duration; The first duration instruction is transmitted to the baseboard management controller of the device to be started, instructing the baseboard management controller to store the timeout duration; wherein, the timeout duration stored by the baseboard management controller is to be transmitted to the device to be started when the baseboard management controller receives a second duration instruction for the device to be started; the second duration instruction is generated when the device state of the device to be started is a local startup state; the second duration instruction is used to instruct the baseboard management controller to feed back the timeout duration to the device to be started.

2. The method for transmitting duration instructions according to claim 1, characterized in that, The timeout duration determined by the target receiving object based on the network impact parameters of the device to be started includes: Receive path access instructions for the target object; In response to the path access command, access the parameter setting interface; Based on the parameter setting interface, the target object receives the timeout duration determined by the network impact parameters of the device to be started.

3. The method for transmitting duration instructions according to claim 2, characterized in that, The step of receiving the timeout duration determined by the target object based on the network impact parameters of the device to be started, based on the parameter setting interface, includes: In the parameter setting interface, query the duration setting option to obtain the query results; wherein, the duration setting option is used to set the timeout duration parameter in the duration setting option to the timeout duration of the write operation when the timeout duration of the write operation is received; If the query result indicates that the duration setting option exists in the parameter setting interface, the timeout duration determined by the target object based on the network impact parameters of the device to be started is written into the duration setting option; If the query result indicates that the duration setting option is not present in the parameter setting interface, a new duration setting option is added, and the timeout duration determined by the target object based on the network impact parameters of the device to be started is written into the newly added duration setting option.

4. The method for transmitting a duration instruction according to claim 1, wherein the first duration instruction carries the timeout duration; characterized in that, The step of transmitting the first duration instruction to the baseboard management controller of the device to be started, to instruct the baseboard management controller to store the timeout duration, includes: The first duration instruction is transmitted to the baseboard management controller to instruct the baseboard management controller to parse the first duration instruction, extract the duration identifier from the first duration instruction, and, if it is determined based on the duration identifier that the first duration instruction is for network startup, extract the timeout duration from the first duration instruction and store the timeout duration.

5. The method for transmitting duration instructions according to claim 1, characterized in that, The method for transmitting the duration instruction further includes: Obtain the target status identifier of the device to be started; The target status identifier of the device to be started is matched with the status identifiers in a pre-set status identifier database to determine the status identifier that matches the target status identifier; wherein, the status identifier database includes multiple status identifiers and device statuses corresponding to the multiple status identifiers respectively; If the device status of the device to be started corresponding to the status identifier that matches the target status identifier is local startup status, a second duration instruction is determined; wherein, the second duration instruction carries the timeout duration; The second duration instruction is transmitted to the baseboard management controller of the device to be started, so as to instruct the baseboard management controller to feed back the timeout duration to the device to be started.

6. The method for transmitting duration instructions according to claim 1, characterized in that, The method for transmitting the duration instruction further includes: Upon receiving the update timeout duration determined by the target object, a third duration instruction is generated; wherein, the update timeout duration is a new timeout duration determined by the target object based on the current network startup status of the network startup of the device to be started; The third duration instruction is transmitted to the baseboard management controller of the device to be started, instructing the baseboard management controller to clear the stored timeout duration; Upon receiving the fourth duration instruction from the baseboard management controller, a fifth duration instruction is generated based on the update timeout duration; The fifth duration instruction is sent to the baseboard management controller of the device to be started, instructing the baseboard management controller to store the update timeout duration.

7. The method for transmitting duration instructions according to claim 1, characterized in that, After receiving the timeout duration determined by the target object based on the network impact parameters of the device to be started, and before generating the first duration instruction based on the timeout duration, the method for transmitting the duration instruction further includes: In response to a duration verification operation triggered by the target object; Based on the aforementioned duration verification operation, a preset standard duration range is obtained; Compare the timeout duration with the preset standard duration range; If the timeout duration is not within the standard duration range, a warning message is sent to the target object.

8. A method for transmitting duration instructions, applied to a baseboard management controller, characterized in that, include: The system receives a first duration instruction generated based on a timeout duration from a computer terminal. The timeout duration is a duration determined by the target object based on the network impact parameters of the device to be started. The network impact parameters are parameters that affect the network startup status of the device to be started. The timeout duration is the maximum duration set for the device to be started to wait for a response during network startup. In response to the first duration instruction, the timeout duration carried in the first duration instruction is stored; When the baseboard management controller receives a second duration instruction for the device to be started, it transmits the timeout duration to the device to be started; the second duration instruction is generated when the device status of the device to be started is local startup state; the second duration instruction is used to instruct the baseboard management controller to feed back the timeout duration to the device to be started.

9. The method for transmitting duration instructions according to claim 8, characterized in that, The step of responding to the first duration instruction and storing the timeout duration carried in the first duration instruction includes: Parse the first duration instruction and extract the duration identifier carried by the first duration instruction; If it is determined that the first duration instruction is for network startup based on the duration identifier, the timeout duration is extracted from the first duration instruction and stored.

10. The method for transmitting duration instructions according to claim 8, characterized in that, The method for transmitting the duration instruction further includes: Obtain a second duration instruction for the device to be started; wherein the second duration instruction is obtained through one of the following methods: obtaining a target status identifier of the device to be started through the computer terminal; matching the target status identifier of the device to be started with status identifiers in a pre-set status identifier database to determine a status identifier that matches the target status identifier; determining the device status of the device to be started corresponding to the status identifier that matches the target status identifier when it is in a local startup state; wherein the status identifier database includes multiple status identifiers and device states corresponding to the multiple status identifiers respectively; determining the device to be started when it determines that it is in a local startup state; Based on the second duration instruction, the stored timeout duration is fed back to the device to be started, so that the device to be started can enter network startup.

11. The method for transmitting duration instructions according to claim 8, characterized in that, The method for transmitting the duration instruction further includes: The computer terminal transmits a third duration instruction; wherein the third duration instruction is generated by the computer terminal upon receiving an update timeout duration determined by the target object; wherein the update timeout duration is a new timeout duration determined by the target object based on the actual network startup status of the device to be started. Based on the third duration instruction, the stored timeout duration is cleared, and a fourth duration instruction is sent back to the computer terminal; Obtain the fifth duration instruction fed back by the computer terminal; wherein, the fifth duration instruction is generated by the computer terminal based on the update timeout duration upon receiving the fourth duration instruction; Based on the fifth duration instruction, the update timeout duration is stored.

12. A method for starting a device, applied to a basic input / output system, characterized in that, include: If the device to be started is in local boot mode, a second duration instruction is generated; The second duration instruction is transmitted to the baseboard management controller of the device to be started, so as to obtain the timeout duration from the baseboard management controller; wherein, the timeout duration is the duration determined by the target object based on the network influence parameters of the device to be started, the network influence parameters are parameters that affect the network startup status of the device to be started, and the timeout duration is the maximum duration set for the device to be started to wait for a response during network startup; The timeout duration of the baseboard management control feedback is obtained, and the network startup of the device to be started is performed based on the timeout duration of the baseboard management control feedback.

13. The device startup method according to claim 12, characterized in that, The step of performing network startup of the device to be started based on the timeout duration fed back by the baseboard management control includes: Obtain the timeout duration recorded by the basic input / output system; Based on the timeout duration recorded by the basic input / output system or the timeout duration fed back by the baseboard management control, the network startup of the device to be started is performed.

14. The device startup method according to claim 13, characterized in that, The process of performing network startup of the device to be started based on the timeout duration recorded by the basic input / output system or the timeout duration fed back by the baseboard management control includes: If the timeout duration of the baseboard management control feedback is a first target value, network startup of the device to be started is performed based on the timeout duration recorded by the basic input / output system. In any of the following situations, network startup of the device to be started is performed based on the timeout duration fed back by the baseboard management controller: The timeout duration recorded by the basic input / output system is inconsistent with the timeout duration reported by the baseboard management controller; The timeout duration recorded by the basic input / output system is a second target value; wherein the first target value and the second target value are different. The timeout duration recorded by the basic input / output system is consistent with the timeout duration reported by the baseboard management controller.

15. The device startup method according to claim 13, characterized in that, The process of performing network startup of the device to be started based on the timeout duration recorded by the basic input / output system or the timeout duration fed back by the baseboard management control includes: Obtain the actual timeout duration of the network startup process; The actual timeout duration is compared with the timeout duration recorded by the basic input / output system or the timeout duration fed back by the baseboard management controller; If the actual timeout duration is greater than the timeout duration recorded by the basic input / output system or the timeout duration reported by the baseboard management controller, the network startup process is determined to have timed out.

16. A device for transmitting duration instructions, characterized in that, include: The first receiving module is used to receive the timeout duration determined by the target object based on the network impact parameters of the device to be started; wherein, the network impact parameters are parameters that affect the network startup state of the device to be started, and the timeout duration is the maximum duration set for the device to be started to wait for a response during network startup; The first generation module is used to generate a first duration instruction based on the timeout duration; A first transmission module is configured to transmit the first duration instruction to the baseboard management controller of the device to be started, so as to instruct the baseboard management controller to store the timeout duration; wherein, the timeout duration stored by the baseboard management controller is to be transmitted to the device to be started when the baseboard management controller receives a second duration instruction for the device to be started; the second duration instruction is generated when the device state of the device to be started is a local startup state; the second duration instruction is used to instruct the baseboard management controller to feed back the timeout duration to the device to be started.

17. A device for transmitting duration instructions, characterized in that, include: The second receiving module is used to receive a first duration instruction generated based on a timeout duration transmitted by a computer terminal, wherein the timeout duration is the duration determined by the target object based on the network impact parameters of the device to be started, the network impact parameters are parameters that affect the network startup status of the device to be started, and the timeout duration is the maximum duration set for the device to be started to wait for a response during network startup. A response module is configured to respond to the first duration instruction by storing the timeout duration carried in the first duration instruction; The second transmission module is used to transmit the timeout duration to the device to be started when the baseboard management controller receives a second duration instruction for the device to be started; the second duration instruction is generated when the device status of the device to be started is local startup state; the second duration instruction is used to instruct the baseboard management controller to feed back the timeout duration to the device to be started.

18. A starting device for an apparatus, characterized in that, include: The second generation module is used to generate a second duration instruction when the device to be started is in local boot mode. The third transmission module is used to transmit the second duration instruction to the baseboard management controller of the device to be started, so as to obtain the timeout duration from the baseboard management controller; wherein, the timeout duration is the duration determined by the target object based on the network impact parameters of the device to be started, the network impact parameters are parameters that affect the network startup status of the device to be started, and the timeout duration is the maximum duration set for the device to be started to wait for a response during network startup; An execution module is used to obtain the timeout duration from the baseboard management control feedback, and to perform network startup of the device to be started based on the timeout duration from the baseboard management control feedback.

19. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor, configured to execute the computer program to implement the steps of the method for transmitting duration instructions as claimed in any one of claims 1 to 7, or to execute the method for transmitting duration instructions as claimed in any one of claims 8 to 11, or the device startup method as claimed in claims 12 to 15.

20. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, it implements the steps of the method for transmitting duration instructions as described in any one of claims 1 to 7, or executes the method for transmitting duration instructions as described in any one of claims 8 to 11, or the device startup method as described in claims 12 to 15.

Images