Process management method and device of gateway device, electronic device and storage medium

Abstract

Embodiments of the present application provide a process management method and device of a gateway device, an electronic device and a storage medium, wherein the method comprises: obtaining a configuration file, the configuration file comprising a restart mode of a service process of the gateway device; in response to a signal that a target process is abnormal; obtaining the restart mode of the target process and / or the restart mode of the gateway device in the configuration file; and re-running the target process according to the restart mode of the target process and / or the restart mode of the gateway device. The above-mentioned embodiments can solve the problem of single processing mode in the existing process monitoring process.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of network equipment, in particular to a process management method and device of a gateway equipment, an electronic equipment and a computer readable storage medium. BACKGROUND

[0002] Process monitoring refers to real-time monitoring of the state of various running processes in an operating system, analyzing various index information of the process running, reporting the security status of the current system running to the user, and maintaining the process state operation. At present, there are some process monitoring programs in Linux operating system. After the system starts, the service process monitoring program is loaded to monitor the state of other service processes in the system in real time. When a service process fails, the process can be maintained in time to reduce the occurrence of a long time of no response of the system caused by the hanging of some processes, so as to enhance the robustness of the system.

[0003] The processor performance of the gateway equipment is not as stable as that of the server, and a large amount of traffic messages also need to be processed, so the probability of process crash is relatively large. In the prior art, the process is activated by directly restarting, the processing mode is single, and the real-time business of the system is affected. SUMMARY

[0004] The purpose of the embodiment of the present application is to provide a process management method and device of a gateway equipment, an electronic equipment and a computer readable storage medium, so as to solve the technical problem of single processing mode in the existing process monitoring process.

[0005] In a first aspect, the embodiment of the present application provides a process management method of a gateway equipment, comprising:

[0006] obtaining a configuration file, wherein the configuration file comprises a restart mode of a service process of the gateway equipment;

[0007] in response to a signal that a target process occurs abnormally;

[0008] obtaining the restart mode of the target process and / or the restart mode of the gateway equipment in the configuration file;

[0009] re-running the target process according to the restart mode of the target process and / or the restart mode of the gateway equipment.

[0010] In the above implementation process, the gateway equipment and the process restart mode are combined to re-run the target process, the configuration file is used to define the restart mode of the gateway equipment and the restart mode of the process, and multiple modes are used to re-run the target process. The restart mode of the target process and / or the restart mode of the gateway equipment can be pre-configured in the configuration file based on real-time business, so as to avoid the influence of mechanical restart of the target process on real-time business.

[0011] Further, the step of re-running the target process according to the restart method of the target process and / or the restart method of the system includes:

[0012] Step 1: Restart the target process. If the restart fails, proceed to Step 2.

[0013] Step 2: Record the number of times the target process has been restarted;

[0014] Step 3: Determine whether the number of restarts exceeds the first preset threshold. If yes, proceed to Step 4; otherwise, proceed to Step 1.

[0015] Step 4: Restart the gateway device and repeat Step 1.

[0016] In the above implementation process, a direct restart is first attempted. If the restart fails, the gateway device is then restarted. By restarting the gateway device, the success rate of restarting the target process is improved.

[0017] Further, the step of re-running the target process according to the restart method of the target process and / or the restart method of the system includes:

[0018] Step 1: Restart the target process. If the restart fails, proceed to Step 2.

[0019] Step 2: Record the number of times the target process has been restarted;

[0020] Step 3: If the number of restarts exceeds the first preset threshold but is less than the second preset threshold, proceed to step 4; if the number of restarts exceeds the second preset threshold, proceed to step 5; if the number of restarts is less than the first preset threshold, proceed to step 1.

[0021] Step 4: Restart the gateway device and repeat Step 1;

[0022] Step 5: Stop re-running the target process.

[0023] In the above implementation process, the number of restarts is preset. When the number of restarts of the gateway device reaches the preset number, the target process is stopped from running again to avoid wasting the resources of the gateway device.

[0024] Further, the step of re-running the target process according to the restart method of the target process and / or the restart method of the system includes:

[0025] Step 1: Restart the target process. If the restart fails, proceed to Step 2.

[0026] Step 2: Record the number of restarts and the duration of the target process;

[0027] Step 3: If the number of restarts exceeds the third preset threshold and the duration does not exceed the preset time, proceed to step 4; if the duration exceeds the preset time, proceed to step 5.

[0028] Step 4: If so, restart the gateway device and proceed to Step 1;

[0029] Step 5: Stop re-running the target process.

[0030] In the above implementation process, a preset time is set. If the restart fails within the preset time, the process will not be restarted by restarting the system, thus avoiding the waste of gateway device resources.

[0031] Further, the step of re-running the target process according to the restart method of the target process and / or the restart method of the system includes:

[0032] Step 1: Restart the target process. If the restart fails, proceed to Step 2.

[0033] Step 2: Record the number of times the target process has been restarted;

[0034] Step 3: If the number of restarts exceeds a first preset threshold within a preset duration, proceed to Step 4;

[0035] Step 4: Restart the gateway device. If the restart fails, proceed to Step 1.

[0036] In the above implementation process, a preset time is set. If the number of restarts exceeds a certain number within the preset time, the system will be restarted, which can minimize the impact of the restart process on business.

[0037] Further, the step of obtaining the restart method of the target process and / or the restart method of the gateway device from the configuration file includes:

[0038] Get the number of internal network devices currently connected to the gateway device;

[0039] The restart method of the target process and / or the restart method of the gateway device are obtained from the configuration file based on the number of connected intranet devices.

[0040] In the above implementation process, different restart methods for target processes and / or gateway devices have different degrees of impact on the normal operation of gateway devices. The number of connections of internal network devices reflects the importance of gateway devices in the entire network. Based on this, the restart methods for target processes and / or gateway devices are determined to minimize the impact of restarting target processes on services.

[0041] Further, the step of obtaining the restart method of the target process and / or the restart method of the gateway device from the configuration file includes:

[0042] Obtain the priority of the current gateway device;

[0043] The restart method of the target process and / or the restart method of the gateway device are obtained from the configuration file according to the priority.

[0044] In the above implementation process, different restart methods for target processes and / or gateway devices have different degrees of impact on the normal operation of gateway devices. Priority reflects the importance of gateway devices in the entire network. Based on this, the restart methods for target processes and / or gateway devices are determined to minimize the impact of restarting target processes on services.

[0045] Secondly, embodiments of this application provide a process management device, including:

[0046] The configuration file acquisition module is used to acquire the configuration file, which includes the restart method of the service process of the gateway device;

[0047] The response module is used to respond to a signal that an abnormality has occurred in the target process, and to obtain the restart method of the target process and / or the restart method of the system from the configuration file;

[0048] The restart module is used to rerun the target process according to the restart method of the target process and / or the restart method of the system.

[0049] In the above implementation, the target process is re-run by combining gateway device and process restart methods. The restart methods for both the gateway device and the process are defined in the configuration file, enabling multiple modes for re-running the target process. The restart methods for the target process and / or the gateway device can be pre-configured in the configuration file based on real-time business needs, avoiding the impact of mechanically restarting the target process on real-time services.

[0050] Thirdly, an electronic device provided in this application includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the method as described in any of the first aspects.

[0051] Fourthly, embodiments of this application provide a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the method described in any of the first aspects.

[0052] Other features and advantages disclosed in this application will be set forth in the following description, or some features and advantages may be inferred from the description or determined without doubt, or may be learned by practicing the above-described technology disclosed in this application.

[0053] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0054] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0055] Figure 1 A flowchart illustrating the process management method provided in an embodiment of this application;

[0056] Figure 2 This is a schematic diagram of the structure of the process management device provided in the embodiments of this application;

[0057] Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0058] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0059] It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. Furthermore, in the description of this application, terms such as "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0060] Process monitoring refers to the real-time monitoring of the status of various running processes in the operating system, analyzing various metrics during process execution, reporting the current system's security status to the user, and maintaining process status. Currently, Linux operating systems typically include process monitoring programs that load after system startup. These programs monitor the status of other service processes in real time, allowing for timely maintenance of failed processes when they malfunction. This reduces the likelihood of prolonged system unresponsiveness due to process hangs, thereby enhancing system robustness.

[0061] Gateway devices have less stable processor performance compared to servers and need to handle a large number of traffic packets, making them more prone to process crashes. Current technologies use a direct restart to activate processes, resulting in a simplistic processing model that impacts real-time system operations.

[0062] In view of this, the purpose of this application is to provide a process management method, apparatus, electronic device and computer-readable storage medium for a gateway device, so as to solve the technical problem of the single processing mode in the existing process monitoring process.

[0063] Example 1

[0064] See Figure 1 This application provides a process management method for a gateway device, including:

[0065] S101: Obtain the configuration file, which includes the restart method for the gateway device's service processes;

[0066] S102: In response to a signal indicating an error in the target process, retrieve the restart method for the target process and / or the restart method for the gateway device from the configuration file;

[0067] S103: Rerun the target process according to the restart method of the target process and / or the restart method of the gateway device.

[0068] The configuration file can define the restart methods for all processes of the gateway device and / or the restart method of the gateway device itself, using service modules as units. Specifically, it can be specified that all relevant processes of service module A use the first process restart method and the gateway device restart method to rerun the target process, while all relevant processes of service module B use the second process restart method and the gateway device restart method to rerun the target process.

[0069] In the above implementation, the target process is re-run by combining gateway device and process restart methods. The restart methods for both the gateway device and the process are defined in the configuration file, enabling multiple modes for re-running the target process. The restart methods for the target process and / or the gateway device can be pre-configured in the configuration file based on real-time business needs, avoiding the impact of mechanically restarting the target process on real-time services.

[0070] This application provides several ways to rerun the target process.

[0071] In one possible implementation, S103 includes: restarting the process in an infinite loop until the state is restored.

[0072] In one possible implementation, S103 includes: Step 1: Restart the target process; if the restart fails, proceed to Step 2.

[0073] Step 2: Record the number of times the target process is restarted;

[0074] Step 3: Determine if the number of restarts exceeds the first preset threshold. If yes, proceed to Step 4; otherwise, proceed to Step 1.

[0075] Step 4: Restart the gateway device and repeat Step 1.

[0076] In the above implementation process, a direct restart is first attempted. If the restart fails, the gateway device is then restarted. By restarting the gateway device, the success rate of restarting the target process is improved.

[0077] In one possible implementation, S103 includes: Step 1: Restart the target process; if the restart fails, proceed to Step 2.

[0078] Step 2: Record the number of times the target process is restarted;

[0079] Step 3: If the number of restarts exceeds the first preset threshold but is less than the second preset threshold, proceed to step 4; if the number of restarts exceeds the second preset threshold, proceed to step 5; if the number of restarts is less than the first preset threshold, proceed to step 1.

[0080] Step 4: Restart the gateway device and repeat Step 1;

[0081] Step 5: Stop rerunning the target process.

[0082] In the above implementation process, the number of restarts is preset. When the number of restarts of the gateway device reaches the preset number, the target process is stopped from running again to avoid wasting the resources of the gateway device.

[0083] In one possible implementation, S103 includes: Step 1: Restart the target process; if the restart fails, proceed to Step 2.

[0084] Step 2: Record the number of restarts and the duration of the target process;

[0085] Step 3: If the number of restarts exceeds the third preset threshold and the duration does not exceed the preset time, proceed to Step 4; if the duration exceeds the preset time, proceed to Step 5.

[0086] Step 4: If so, restart the gateway device and then perform Step 1;

[0087] Step 5: Stop rerunning the target process.

[0088] In the above implementation process, a preset time is set. If the restart fails within the preset time, the process will not be restarted by restarting the system, thus avoiding the waste of gateway device resources.

[0089] In one possible implementation, S103 includes: Step 1: Restart the target process; if the restart fails, proceed to Step 2.

[0090] Step 2: Record the number of times the target process is restarted;

[0091] Step 3: If the number of restarts exceeds the first preset threshold within the preset duration, proceed to Step 4;

[0092] Step 4: Restart the gateway device. If the restart fails, proceed to Step 1.

[0093] In the above implementation process, a preset time is set. If the number of restarts exceeds a certain number within the preset time, the system will be restarted, which can minimize the impact of the restart process on business.

[0094] In a server cluster with multiple gateway devices, each gateway device is connected to multiple servers. Based on this, S103 includes: obtaining the number of internal network devices connected to the current gateway device;

[0095] Based on the number of connected intranet devices, obtain the restart method for the target process and / or the restart method for the gateway device from the configuration file.

[0096] In the above implementation process, different restart methods for target processes and / or gateway devices have different degrees of impact on the normal operation of gateway devices. The number of connections of internal network devices reflects the importance of gateway devices in the entire network. Based on this, the restart methods for target processes and / or gateway devices are determined to minimize the impact of restarting target processes on services.

[0097] In one possible implementation, S103 includes: obtaining the priority of the current gateway device;

[0098] Based on priority, obtain the restart method for the target process and / or the restart method for the gateway device from the configuration file.

[0099] In the above implementation process, different restart methods for target processes and / or gateway devices have different degrees of impact on the normal operation of gateway devices. Priority reflects the importance of gateway devices in the entire network. Based on this, the restart methods for target processes and / or gateway devices are determined to minimize the impact of restarting target processes on services.

[0100] Example 2

[0101] See Figure 2 This application provides a process management device, including:

[0102] Configuration file acquisition module 1 is used to acquire configuration files, which include the restart methods for the service processes of the gateway device;

[0103] Response module 2 is used to respond to signals indicating an exception in the target process and to obtain the restart method of the target process and / or the system restart method from the configuration file.

[0104] Restart module 3 is used to rerun the target process based on the restart method of the target process and / or the restart method of the system.

[0105] In the above implementation, the target process is re-run by combining gateway device and process restart methods. The restart methods for both the gateway device and the process are defined in the configuration file, enabling multiple modes for re-running the target process. The restart methods for the target process and / or the gateway device can be pre-configured in the configuration file based on real-time business needs, avoiding the impact of mechanically restarting the target process on real-time services.

[0106] In one possible implementation, the restart module 3 is also used to perform the following steps: Step 1: Restart the target process; if the restart fails, proceed to Step 2.

[0107] Step 2: Record the number of times the target process is restarted;

[0108] Step 3: Determine if the number of restarts exceeds the first preset threshold. If yes, proceed to Step 4; otherwise, proceed to Step 1.

[0109] Step 4: Restart the gateway device and repeat Step 1.

[0110] In one possible implementation, the restart module 3 is also used to perform the following steps: Step 1: Restart the target process; if the restart fails, proceed to Step 2.

[0111] Step 2: Record the number of times the target process is restarted;

[0112] Step 3: If the number of restarts exceeds the first preset threshold but is less than the second preset threshold, proceed to step 4; if the number of restarts exceeds the second preset threshold, proceed to step 5; if the number of restarts is less than the first preset threshold, proceed to step 1.

[0113] Step 4: Restart the gateway device and repeat Step 1;

[0114] Step 5: Stop rerunning the target process.

[0115] In one possible implementation, the restart module 3 is also used to perform the following steps: Step 1: Restart the target process; if the restart fails, proceed to Step 2.

[0116] Step 2: Record the number of restarts and the duration of the target process;

[0117] Step 3: If the number of restarts exceeds the third preset threshold and the duration does not exceed the preset time, proceed to Step 4; if the duration exceeds the preset time, proceed to Step 5.

[0118] Step 4: If so, restart the gateway device and then perform Step 1;

[0119] Step 5: Stop rerunning the target process.

[0120] In one possible implementation, the restart module 3 is also used to perform the following steps: Step 1: Restart the target process; if the restart fails, proceed to Step 2.

[0121] Step 2: Record the number of times the target process is restarted;

[0122] Step 3: If the number of restarts exceeds the first preset threshold within the preset duration, proceed to Step 4;

[0123] Step 4: Restart the gateway device. If the restart fails, proceed to Step 1.

[0124] In one possible implementation, the restart module 3 is also used to obtain the number of intranet device connections of the current gateway device;

[0125] Based on the number of connected intranet devices, obtain the restart method for the target process and / or the restart method for the gateway device from the configuration file.

[0126] In one possible implementation, the restart module 3 is also used to obtain the priority of the current gateway device;

[0127] Based on priority, obtain the restart method for the target process and / or the restart method for the gateway device from the configuration file.

[0128] This application also provides an electronic device, please refer to [link to application]. Figure 3 , Figure 3 This is a structural block diagram of an electronic device provided in an embodiment of this application. The electronic device may include a processor 31, a communication interface 32, a memory 33, and at least one communication bus 34. The communication bus 34 is used to enable direct communication between these components. In this embodiment, the communication interface 32 of the electronic device is used for signaling or data communication with other node devices. The processor 31 may be an integrated circuit chip with signal processing capabilities.

[0129] The processor 31 described above can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor, or the processor 31 can be any conventional processor.

[0130] The memory 33 may be, but is not limited to, random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), etc. The memory 33 stores computer-readable instructions. When these computer-readable instructions are executed by the processor 31, the electronic device can perform the various steps involved in the above method embodiments.

[0131] Alternatively, the electronic device may also include a storage controller and an input / output unit.

[0132] The memory 33, memory controller, processor 31, peripheral interface, and input / output unit are electrically connected directly or indirectly to achieve data transmission or interaction. For example, these components can be electrically connected to each other through one or more communication buses 34. The processor 31 is used to execute executable modules stored in the memory 33, such as software function modules or computer programs included in electronic devices.

[0133] Input / output units are used to enable users to create tasks and set optional start periods or preset execution times for those tasks, facilitating user-server interaction. Input / output units can be, but are not limited to, a mouse and keyboard.

[0134] Understandable. Figure 3 The structure shown is for illustrative purposes only; the electronic device may also include components that are more advanced than those shown. Figure 3 The more or fewer components shown, or having the same Figure 3 The different configurations shown. Figure 3The components shown can be implemented using hardware, software, or a combination thereof.

[0135] This application also provides a computer-readable storage medium storing instructions. When the instructions are executed on a computer, the computer program is executed by a processor to implement the method of the method embodiment. To avoid repetition, the details will not be repeated here.

[0136] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0137] In addition, the functional modules in the various embodiments of this application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0138] If a function is implemented as a software module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0139] The above are merely embodiments of this application and are not intended to limit the scope of protection of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application. It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0140] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0141] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, 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. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

Claims

1. A process management method for a gateway device, characterized in that, include: Obtain the configuration file, which includes the restart method for the service process of the gateway device; In response to a signal indicating an error in the target process; The restart method of the target process and / or the restart method of the gateway device are obtained from the configuration file; The target process will be rerun according to the restart method of the target process and / or the restart method of the gateway device; The step of obtaining the restart method of the target process and / or the restart method of the gateway device from the configuration file includes: Get the number of internal network devices currently connected to the gateway device; The restart method of the target process and / or the restart method of the gateway device are obtained from the configuration file based on the number of connected intranet devices.

2. The process management method for a gateway device according to claim 1, characterized in that, The step of re-running the target process according to the restart method of the target process and / or the restart method of the system includes: Step 1: Restart the target process. If the restart fails, proceed to Step 2. Step 2: Record the number of times the target process has been restarted; Step 3: Determine whether the number of restarts exceeds the first preset threshold. If yes, proceed to Step 4; otherwise, proceed to Step 1. Step 4: Restart the gateway device and repeat Step 1.

3. The process management method for a gateway device according to claim 1, characterized in that, The step of re-running the target process according to the restart method of the target process and / or the restart method of the system includes: Step 1: Restart the target process. If the restart fails, proceed to Step 2. Step 2: Record the number of times the target process has been restarted; Step 3: If the number of restarts exceeds the first preset threshold but is less than the second preset threshold, proceed to step 4; if the number of restarts exceeds the second preset threshold, proceed to step 5; if the number of restarts is less than the first preset threshold, proceed to step 1. Step 4: Restart the gateway device and repeat Step 1; Step 5: Stop re-running the target process.

4. The process management method for a gateway device according to claim 2, characterized in that, The step of re-running the target process according to the restart method of the target process and / or the restart method of the system includes: Step 1: Restart the target process. If the restart fails, proceed to Step 2. Step 2: Record the number of restarts and the duration of the target process; Step 3: If the number of restarts exceeds the third preset threshold and the duration does not exceed the preset time, proceed to step 4; if the duration exceeds the preset time, proceed to step 5. Step 4: If so, restart the gateway device and proceed to Step 1; Step 5: Stop re-running the target process.

5. The process management method for a gateway device according to claim 1, characterized in that, The step of re-running the target process according to the restart method of the target process and / or the restart method of the system includes: Step 1: Restart the target process. If the restart fails, proceed to Step 2. Step 2: Record the number of times the target process has been restarted; Step 3: If the number of restarts exceeds a first preset threshold within a preset duration, proceed to Step 4; Step 4: Restart the gateway device. If the restart fails, proceed to Step 1.

6. The process management method for a gateway device according to claim 1, characterized in that, The step of obtaining the restart method of the target process and / or the restart method of the gateway device from the configuration file includes: Obtain the priority of the current gateway device; The restart method of the target process and / or the restart method of the gateway device are obtained from the configuration file according to the priority.

7. A process management device for a gateway device, characterized in that, The configuration file acquisition module is used to acquire the configuration file, which includes the restart method of the service process of the gateway device; The response module is used to respond to a signal that an abnormality has occurred in the target process, and to obtain the restart method of the target process and / or the restart method of the system from the configuration file; The restart module is used to rerun the target process according to the restart method of the target process and / or the restart method of the system; The response module is specifically used for: Get the number of internal network devices currently connected to the gateway device; The restart method of the target process and / or the restart method of the gateway device are obtained from the configuration file based on the number of connected intranet devices.

8. An electronic device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the steps of the method as described in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-6.

Images