Software bypass implementation method and apparatus, and storage medium

Abstract

The present application provides a software BYPASS implementation method and apparatus, and a storage medium. The method comprises: separately acquiring values of performance indexes and related performance indexes of a network device; when a software BYPASS function of the network device is not enabled, if the values of the performance indexes reach a trigger threshold value for the software BYPASS function, triggering the software BYPASS function; and when the software BYPASS function of the network device has been enabled, if the values of the performance indexes and the related performance indexes all reach a software BYPASS exit threshold value, exiting the software BYPASS function. Considering a software BYPASS exit mechanism, the present invention performs associated determination on values of performance indexes and related performance indexes, significantly avoiding repeated oscillations of the software BYPASS state when network devices reach performance bottlenecks, and thus ensuring the continuity of user services.

Description

A software BYPASS implementation method, device and storage medium Technical Field

[0001] The present application relates to the field of network security technology, and in particular to a method, device and storage medium for implementing software BYPASS. Background Art

[0002] With the advent of the cloud computing and big data era, network traffic is increasing rapidly. When traffic levels are high or peak traffic spikes occur, if network equipment reaches its maximum processing capacity, packet loss can occur, leading to network lags at best and even network disconnection at worst. In these situations, hardware BYPASS will not trigger. Therefore, applying software BYPASS technology to address the issue of skipping security services when network equipment reaches performance bottlenecks, prioritizing service connectivity, has become a pressing technical issue.

[0003] In the current existing technology, software BYPASS technology is usually based on trigger conditions such as CPU usage thresholds and memory usage thresholds. When the trigger condition is higher than a certain configuration threshold, the software BYPASS is triggered. The exit mechanism is usually when the trigger condition is lower than a certain configuration threshold, or when the software BYPASS state reaches a certain time.

[0004] Existing technical solutions lack a comprehensive exit mechanism for software BYPASS technology. Increased CPU and memory usage are often caused by network devices processing security services. When software BYPASS is triggered due to excessively high thresholds, security services are no longer processed, causing CPU and memory usage to drop sharply, forcing the network device to exit software BYPASS. However, even after exiting software BYPASS, network traffic may continue, causing CPU and memory usage to rise sharply, triggering software BYPASS again. This causes the network device's software BYPASS status to fluctuate, continuously impacting user services.

[0005] Summary of the Invention

[0006] The present disclosure provides a method, apparatus, device, and storage medium for implementing software BYPASS to at least solve the technical problems in related technologies. The technical solutions of the present disclosure are as follows:

[0007] According to a first aspect of an embodiment of the present disclosure, a method for implementing software BYPASS is proposed, the method comprising:

[0008] Respectively obtaining values ​​of performance indicators and related performance indicators of the network device, wherein the performance indicators and the values ​​of the related performance indicators are used to represent the load degree of the processing capacity of the network device from corresponding dimensions;

[0009] In a case where the software BYPASS function of the network device is not enabled, if the value of the performance indicator reaches a triggering threshold of the software BYPASS function, triggering the software BYPASS function;

[0010] In a case where the software BYPASS function of the network device is enabled, if the values ​​of the performance indicator and the related performance indicator both reach the exit threshold of the software BYPASS, the software BYPASS function is exited.

[0011] Optionally, the performance indicator includes CPU usage and / or memory usage; the related performance indicators include the number of new connections, network throughput and / or the number of concurrent connections.

[0012] Optionally, when the performance indicator includes CPU usage, the relevant performance indicator includes the number of new connections and / or network throughput; when the performance indicator includes memory usage, the relevant performance indicator includes the number of concurrent connections.

[0013] Optionally, the values ​​of the performance indicator and the related performance indicator are instantaneous usage values, or average values ​​of multiple instantaneous usage values ​​collected in a monitoring cycle.

[0014] Optionally, if the collected instantaneous usage value is stable within a preset time period, the value of the performance indicator of the network device and the related performance indicator is the instantaneous usage value.

[0015] Optionally, if the collected instantaneous usage value is unstable within a preset time period, the value of the performance indicator of the network device and the related performance indicator is the average value.

[0016] Optionally, the duration of the monitoring period is negatively correlated with the value of the performance indicator.

[0017] According to a second aspect of the embodiment of the present disclosure, a device for implementing software BYPASS is proposed, the device comprising an acquisition module, a judgment module, an opening module and a closing module, wherein:

[0018] The acquisition module is used to obtain the values ​​of the performance indicator and related performance indicators;

[0019] The judgment module is used to judge whether the value of the performance indicator and / or related performance indicators reaches the trigger or exit threshold set by the software BYPASS;

[0020] The activation module is configured to activate the BYPASS software if the judgment module determines that the value of the performance indicator has reached the set trigger threshold;

[0021] The closing module is used to close the software BYPASS when the judgment module determines that the values ​​of the performance indicator and the related performance indicators have reached the set exit threshold.

[0022] According to a third aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored. When the program is executed by a processor, the method for implementing the software BYPASS described in the first aspect is implemented.

[0023] According to a fourth aspect of an embodiment of the present disclosure, an electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the method for implementing the software BYPASS described in the first aspect above is implemented.

[0024] According to the above solution, based on relevant performance indicators and considering the software BYPASS exit mechanism of the network device, the value of the performance indicator and the value of the related performance indicator are correlated and judged. When the value of the performance indicator reaches the set exit threshold, the value of the related performance indicator needs to be judged. If the value of the related performance indicator does not reach the set exit threshold, it indicates that the service traffic still exceeds the processing capacity of the network device. In this case, the software BYPASS will not be disabled. However, if the value of the related performance indicator reaches the set exit threshold, it indicates that the network device is capable of processing the received service traffic. In this case, the software BYPASS can be disabled. This avoids the situation where the software BYPASS function is turned on and off and the software BYPASS status fluctuates due to disabling the software BYPASS function based solely on performance indicators, thereby ensuring the continuity of user services. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] FIG1 is a flow chart of a method for implementing the BYPASS software provided by the present application;

[0026] FIG2 is a flowchart of a trigger software BYPASS provided by the present application;

[0027] FIG3 is a flowchart of a BYPASS exit software provided by the present application;

[0028] FIG4 is a block diagram of an embodiment of a BYPASS software device provided by the present application;

[0029] FIG5 is a schematic structural diagram of an electronic device provided in this application. DETAILED DESCRIPTION

[0030] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0031] In view of the problem that the exit mechanism of the software BYPASS technology in the existing technical solutions is incomplete, the increase and decrease of CPU utilization and memory utilization will cause the software BYPASS in the network device to be repeatedly opened and closed, causing the software BYPASS status to oscillate back and forth, continuously affecting customers, the embodiment of the present disclosure provides an implementation method of software BYPASS, which can be executed by a network device. The network device can be a DPI (Dots Per Inch) device, a firewall, an IPS (Internet Protocol Suite), a UTM (Unified Threat Management), an IDP, a spam gateway, an antivirus gateway, a dedicated DDOS (Distributed Denial of Service) device, a dedicated logical isolation device in various fields, etc.

[0032] As shown in FIG1 , it is a flowchart of a method for implementing software BYPASS according to an embodiment of the present disclosure, and the method includes:

[0033] In S101, performance indicators and related performance indicators of a network device are obtained, where the values ​​of the performance indicators and / or related performance indicators are used to represent the load level of the processing capability of the network device.

[0034] The values ​​of performance indicators and related performance indicators are used to represent the degree of load on the network device's processing capacity. Generally speaking, a larger value for a performance indicator or related performance indicator indicates a greater degree of utilization of the network device's processing capacity, and the closer the network device's processing capacity approaches its utilization limit, the greater the network device's load. A smaller value for a performance indicator or related performance indicator indicates a lower degree of utilization of the network device's processing capacity and a lower network device load.

[0035] The performance indicator can be CPU usage or memory usage, or a combination of the two. CPU usage refers to the percentage of the computer's CPU processing resources that are being used. It represents the ratio of the time the CPU processor is executing instructions to the idle time. When the CPU usage is high, it means that the CPU processor is performing a large number of tasks, which may cause the computer to slow down or become stuck. Memory usage refers to the percentage of the computer's memory (RAM) that is being used. It represents the proportion of memory occupied by applications. When the memory usage is high, it means that applications in the computer are using a large amount of memory, which may cause the computer to slow down or become stuck.

[0036] Relevant performance metrics can include the number of new connections, network throughput, or concurrent connections, or any two or all three. New connections refer to the number of new network connections established within a period of time. These connections can be either TCP or UDP and are commonly used to monitor network traffic or load. On a server, the number of new connections is an important performance metric because it indicates how many clients are connecting to the server at a given time. A high number of new connections may indicate that the server is receiving too many client requests, potentially causing excessive server load and impacting service response time and stability. Network throughput refers to the amount of data transferred over a network connection within a period of time. It is commonly used to measure network bandwidth and traffic flow, and can also be used to evaluate network performance and optimize network configuration. Network throughput can be expressed in different units, such as bits per second (bps), kilobits per second (Kbps), megabits per second (Mbps), or gigabits per second (Gbps). Network throughput depends on factors such as the bandwidth, latency, and packet loss rate of the network connection. In practice, network throughput can be increased, thereby improving network performance and reliability, by optimizing network topology, upgrading network equipment, using efficient transmission protocols, and reducing data transmission volume. Concurrent connections refer to the number of connections established simultaneously within a given time period. In computer networks, this typically refers to the number of simultaneous connections to a server, but can also refer to the number of concurrent connections to the same destination. Concurrent connections are a crucial metric because they can impact server performance and stability. Excessive concurrent connections can lead to excessive server load, impacting service response time and stability, and even causing server crashes.

[0037] In one embodiment, the value of the performance indicator may be the instantaneous usage value of the network device. If the value of the performance indicator of the network device does not change or changes by less than a preset value over a period of time, this indicates that the value of the performance indicator of the network device is stable during that period, meaning that its utilized processing capacity is in a stable state. In this case, the instantaneous usage value may be used as the value of the performance indicator. Similarly, when the value of a related performance indicator is stable, the value of the related performance indicator may also be the instantaneous usage value of the network device. This description will not be repeated here.

[0038] Instantaneous usage refers to the value of a metric at a specific moment. This can be any metric, such as CPU usage, memory usage, network throughput, number of new connections, number of concurrent connections, and so on. Instantaneous usage values ​​are often dynamic because they reflect the current state of the system. For example, instantaneous CPU usage can reach 100% at one moment and drop to 10% at another. Monitoring instantaneous usage can help you understand the real-time status of the system.

[0039] In another embodiment, the value of the performance indicator can also be the average value of multiple instantaneous performance indicator values ​​collected by the network device during a monitoring cycle. If the value of the performance indicator of the network device changes frequently over a period of time, it means that the value of the performance indicator of the network device is unstable during this period, and its used processing capacity is in an unstable state. At this time, it is not possible to select an instantaneous usage value as the value of the performance indicator. In this case, it is necessary to monitor the value of the performance indicator of the network device and adopt a technical solution that uses the average value of multiple instantaneous usage values ​​in a monitoring cycle as the value of the performance indicator. Similarly, the values ​​of related performance indicators also adopt the same technical solution, which will not be repeated here.

[0040] Taking the average of multiple instantaneous values ​​can smooth out metric fluctuations, better reflecting the metric's long-term trend. For example, when monitoring CPU usage, using a single instantaneous value can be affected by instantaneous fluctuations, leading to misjudgments. However, taking the average of multiple instantaneous values ​​can reduce the impact of these fluctuations and more accurately reflect CPU usage.

[0041] In the above embodiment, the duration of the monitoring period can be a pre-set fixed duration. Alternatively, the duration of the monitoring period can also be a dynamic duration, for example: the larger the value of the performance indicator, the shorter the monitoring period; the smaller the value of the performance indicator, the longer the monitoring period, so that the real-time status and performance of the system can be more accurately reflected. For example, when the value of the performance indicator is relatively larger, it means that the processing capacity of the network device is closer to the usage limit. At this time, by shortening the monitoring period, the status of the network device can be obtained more frequently, making the value of the performance indicator more accurate. For another example, when the value of the performance indicator is relatively smaller, it means that the processing capacity of the network device is further away from the usage limit. At this time, by increasing the monitoring period, there is no need to obtain the status of the network device very frequently, which can save relevant resources and reduce the impact on the normal business functions of the network device.

[0042] The value of each instantaneous performance indicator is used to characterize the degree to which the processing capacity of the network device is being used at the instant of collection. If the instantaneous usage value of the network device is constantly changing, it means that the degree to which the processing capacity of the network device is being used is constantly changing. It is necessary to obtain the average value of multiple instantaneous usage values ​​collected during the monitoring period as the value of the performance indicator of the network device. That is, calculate the sum of the values ​​of multiple instantaneous performance indicators and the quotient of the time length of the monitoring period. At this time, the value of the performance indicator obtained can represent the stability of the degree to which the processing capacity of the network device is being used during the monitoring period. Similarly, the values ​​of related performance indicators are the same.

[0043] Therefore, it can be understood that using the instantaneous usage value as the performance indicator is suitable for situations where the network device's processing capacity is stable over time; using the average of multiple instantaneous usage values ​​collected during a monitoring cycle as the performance indicator is suitable for situations where the network device's processing capacity is unstable over time. Similarly, the same technical solution is used for the values ​​of related performance indicators. This solution does not limit either scenario; which solution to adopt depends on actual needs or user preferences.

[0044] In S102 , when the value of the performance indicator or the related performance indicator reaches a trigger threshold preset by the software BYPASS, the software BYPASS is triggered.

[0045] After determining the load level that characterizes the processing capacity of the network device, it is necessary to compare the value of the performance indicator with the trigger threshold preset by the software BYPASS. The preset trigger threshold can represent whether the degree of utilization of the processing capacity of the network device is close to the utilization limit of the processing capacity of the network device.

[0046] If the value of the performance indicator does not exceed the preset threshold, it means that the degree of utilization of the processing capacity of the network device is not close to the utilization limit of the processing capacity of the network device, and monitoring can be continued.

[0047] If the performance indicator exceeds the preset threshold, it indicates that the network device's processing capacity is nearing its limit. This puts the network device under heavy load, leading to network lag and failure. Therefore, a software BYPASS is triggered to skip security service processing.

[0048] As shown in FIG2 , it is a flowchart of a triggering software BYPASS provided by the present application, which will be described in more detail below in conjunction with the flowchart.

[0049] As shown in step 201: obtain the value of the performance indicator of the target device. The performance indicator can be the CPU usage and / or memory usage as mentioned above.

[0050] In steps 202 and 203, if the performance indicator is CPU usage, the software BYPASS trigger threshold set can be in the form of a percentage. Since CPU usage = (the sum of all non-idle CPU usage time) / (the sum of all state CPU time) * 100%, which is generally expressed in the form of a percentage, the corresponding software bypass judgment of CPU usage can also be set as a percentage. For example, if the threshold set for CPU usage by software BYPASS is 80%, then when the monitoring device detects that the CPU usage of the network device is not less than 80%, it is necessary to trigger software BYPASS to skip the processing of security services, give priority to ensuring the connectivity of the services, and prevent the network device from being forced to stop processing security services due to excessive CPU usage. This embodiment does not require the threshold set for CPU usage, nor does it require whether it is expressed in the form of a percentage. It can be set according to the CPU limit processing capacity of the specific network device.

[0051] If the performance indicator is memory usage, the software BYPASS trigger threshold can also be set in percentage form. Since memory usage = (used memory) / (total memory) * 100%, which is generally expressed as a percentage, it can be set in the same manner as CPU usage. Similarly, this embodiment does not require the threshold set for memory usage, nor does it require it to be expressed in percentage form. It can be set according to the memory usage limit of the specific network device.

[0052] It should be noted that the performance indicators described in this embodiment are not limited to the two above. Any other performance indicator that can represent the load level of the network device's processing capacity can be used as a judgment standard, and this embodiment does not impose any restrictions on this. When determining whether to trigger software BYPASS, it is important to note that as long as the value of any of the performance indicators reaches the set trigger threshold, software BYPASS is triggered to ensure service continuity.

[0053] In step 204, if the value of any performance indicator does not exceed the set trigger threshold, it means that the network device has not reached a performance bottleneck and can still continue to process network security services. At this time, there is no need to trigger the software BYPASS, and you only need to continue monitoring the value of the performance indicator.

[0054] In S103 , when the values ​​of the performance indicator and related performance indicators reach the exit threshold preset by the BYPASS software, the BYPASS software is exited.

[0055] If the value of the performance indicator is lower than the preset software BYPASS exit threshold, it means that the processing capacity of the network device is not being used close to the maximum usage limit of the network device. To avoid the software BYPASS status of the network device from fluctuating, before exiting the software BYPASS, observe whether the value of the relevant performance indicator changes to determine whether the software BYPASS can really be exited.

[0056] In one embodiment, if the performance indicator is CPU usage, then it is necessary to observe related performance indicators such as the number of new connections and network throughput. If the value of the performance indicator and the value of the related performance indicators are both lower than a certain proportion of the peak value when the software BYPASS is triggered, then exit the software BYPASS and resume security business processing. Otherwise, continue to maintain the triggered state of the software BYPASS.

[0057] In another embodiment, if the performance indicator is memory usage, then it is necessary to observe related performance indicators such as the number of concurrent connections. If the value of the performance indicator and the value of the related performance indicators are both lower than a certain proportion of the peak value when the software BYPASS is triggered, then exit the software BYPASS and resume security business processing. Otherwise, continue to maintain the triggered state of the software BYPASS.

[0058] As shown in FIG3 , this is a flowchart of exiting the BYPASS software provided by the present application, which will be described in more detail below in conjunction with the flowchart.

[0059] Since there are problems with the current exit mechanism of the software BYPASS, the most important improvement point of this application is to improve the current exit mechanism of the software BYPASS and effectively solve the problem of the software BYPASS state oscillating back and forth.

[0060] Step 301 is the same as step 201. Both steps require obtaining the value of a performance indicator. However, step 301 also requires obtaining the value of a related performance indicator. The specific performance indicators have been described above. Here, the related performance indicators are described.

[0061] If the relevant performance indicator is the number of new connections, the software BYPASS exit threshold can be set to a numerical value. Since the number of new connections = the number of connections in the current time period - the number of connections in the previous time period, it can be seen that the number of new connections as a relevant performance indicator is a numerical value. Therefore, the corresponding software BYPASS judgment of the number of new connections can be set to a specific numerical value. This embodiment does not set a threshold for the number of new connections. The software BYPASS exit threshold can be specifically set based on the new connection requirements of the specific network device.

[0062] If the relevant performance indicator is network throughput, the software BYPASS exit threshold is typically set in data / second. Since network throughput = data volume transmitted / transmission time, it can be seen that network throughput as a performance indicator is a ratio. Therefore, the software BYPASS threshold for network throughput can be set in data / second. This embodiment does not impose any specific requirements on the threshold set for network throughput; the software BYPASS exit threshold can be specifically set based on the network throughput tolerance of the specific network equipment.

[0063] If the relevant performance indicator is the number of concurrent connections, the software BYPASS exit threshold is typically a numerical value. Since concurrent connections equal the number of connections within a given time period, it can be set to a specific value in the same manner as the number of new connections. This embodiment does not impose any specific requirements on the threshold for concurrent connections; the software BYPASS exit threshold can be specifically set based on the concurrent connection requirements of the specific network device.

[0064] It should be noted that the prerequisite for exiting software BYPASS is that software BYPASS has been triggered. Only when software BYPASS has been triggered will the software BYPASS be closed.

[0065] In steps 302 and 303, the exit thresholds are set in the same format as in the previous steps, but the determination method is different. To determine whether the software BYPASS is triggered, simply compare any one of the acquired performance indicators with the trigger threshold. However, to determine whether the software BYPASS is exited, the performance indicator must be correlated with related performance indicators.

[0066] One reason is that there's a correlation between CPU usage and the number of connections. Generally speaking, as the number of connections increases, so does CPU usage. This is because each connection requires CPU resources to perform operations, such as processing requests and responding to data. When the number of connections is too high, the CPU load increases, leading to higher CPU usage. Therefore, one of the reasons for the current software BYPASS state oscillation is this: when CPU usage reaches the software BYPASS exit threshold, the software BYPASS is shut down. However, the number of new connections may still be high, causing CPU usage to rise again, exceeding the trigger threshold and triggering the software BYPASS. This results in repeated opening and closing of the software BYPASS, severely impacting user services.

[0067] Similarly, there's a correlation between CPU usage and network throughput. Generally speaking, as network throughput increases, CPU usage also increases. This is because network packets must be processed and forwarded by the CPU, including protocol analysis, packet unpacking, and packet assembly. When the network load is excessive, the CPU load also increases, leading to higher CPU usage. Currently, when CPU usage decreases and the conditions for exiting software BYPASS are met, software BYPASS exits. However, network traffic may still be present during this time, causing CPU usage to rise sharply and triggering software BYPASS again. This causes the software BYPASS status of network devices to fluctuate, continuously impacting user services.

[0068] Another aspect is that there's a relationship between memory usage and the number of connections. Generally speaking, as the number of connections increases, so does memory usage. This is because each connection requires memory resources to store related data and status information. When the number of connections is too high, the memory load increases, leading to higher memory usage. Ultimately, this can cause the software's BYPASS state to fluctuate, impacting user services.

[0069] Similarly, there's a correlation between memory usage and network throughput. Generally speaking, as network throughput increases, memory usage also increases. This is because network packets need to be cached and processed in memory, including packet unpacking and assembly, protocol analysis, and data caching. When the network load is excessive, the memory load also increases, leading to higher memory usage, which ultimately causes the aforementioned problems.

[0070] Therefore, it is biased to monitor only CPU usage and memory usage and use these two performance indicators as the only criteria for exiting the software BYPASS. Therefore, in server management and network monitoring, administrators need to optimize and adjust the system by monitoring performance indicators such as CPU usage, memory usage, and the number of new connections, etc.

[0071] In this application, when judging whether to exit the software BYPASS, it is necessary to correlate and analyze each performance indicator and related performance indicator. Only when the value of the performance indicator and the value of the related performance indicator meet the conditions for exiting the software BYPASS, will the software BYPASS function be actually exited, thereby avoiding the problem of the software BYPASS status oscillating back and forth.

[0072] Corresponding to the aforementioned embodiments of the method for implementing the software BYPASS, this specification also provides embodiments of an apparatus for implementing the software BYPASS.

[0073] FIG4 is a block diagram of an embodiment of a device for implementing the BYPASS software provided by the present application. The device 40 includes:

[0074] The acquisition module 401 is used to respectively acquire the values ​​of the performance indicator and the related performance indicator, wherein the values ​​of the performance indicator and the related performance indicator are used to respectively represent the load degree of the processing capability of the network device from corresponding dimensions.

[0075] The enabling module 402 is configured to trigger the software BYPASS function of the network device if the value of the performance indicator reaches a triggering threshold of the software BYPASS function when the software BYPASS function is not enabled.

[0076] The closing module 403 is configured to, when the software BYPASS function of the network device is enabled, exit the software BYPASS function if the values ​​of the performance indicator and the related performance indicator both reach the exit threshold of the software BYPASS.

[0077] Optional,

[0078] The performance indicators include CPU usage and / or memory usage;

[0079] The relevant performance indicators include the number of new connections, network throughput and / or the number of concurrent connections.

[0080] Optional,

[0081] When the performance indicator includes CPU usage, the relevant performance indicator includes the number of new connections and / or network throughput;

[0082] When the performance indicator includes memory usage, the related performance indicator includes the number of concurrent connections.

[0083] Optionally, the values ​​of the performance indicator and the related performance indicator are instantaneous usage values, or average values ​​of multiple instantaneous usage values ​​collected in a monitoring cycle.

[0084] Optionally, if the collected instantaneous usage value is stable within a preset time period, the value of the performance indicator of the network device and the related performance indicator is the instantaneous usage value.

[0085] Optionally, if the collected instantaneous usage value is unstable within a preset time period, the value of the performance indicator of the network device and the related performance indicator is the average value.

[0086] Optionally, the duration of the monitoring period is negatively correlated with the value of the performance indicator.

[0087] The present disclosure also provides an electronic device, as shown in FIG5 , which includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory at the hardware level, and may also include other required hardware. The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a software BYPASS implementation device as shown in FIG4 at the logical level. Of course, in addition to software implementation, this specification does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0088] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements any of the above-mentioned software BYPASS implementation methods.

[0089] Other embodiments of the present disclosure will readily occur to those skilled in the art after considering the specification and practicing the inventions claimed herein. This disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow from the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the following claims.

[0090] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A method for implementing software BYPASS, characterized in that: include: Respectively obtaining a performance indicator and a value of a related performance indicator of a network device, wherein the performance indicator and the value of the related performance indicator are used to represent a load degree of a processing capability of the network device from corresponding dimensions; In the case where the software BYPASS function of the network device is not enabled, if the value of the performance indicator reaches a triggering threshold of the software BYPASS function, triggering the software BYPASS function; In the case where the software BYPASS function of the network device is turned on, if the values ​​of the performance indicator and the related performance indicator both reach the exit threshold of the software BYPASS, the software BYPASS function is exited.

2. The method according to claim 1, characterized in that The performance indicator includes CPU usage and / or memory usage; The relevant performance indicators include the number of newly established connections, network throughput and / or the number of concurrent connections.

3. The method according to claim 2, characterized in that When the performance indicator includes CPU usage, the relevant performance indicator includes the number of newly established connections and / or network throughput; When the performance indicator includes memory usage, the related performance indicator includes the number of concurrent connections.

4. The method according to claim 1, characterized in that The values ​​of the performance indicator and the related performance indicator are instantaneous usage values, or average values ​​of multiple instantaneous usage values ​​collected in a monitoring cycle.

5. The method according to claim 4, characterized in that If the collected instantaneous usage value is stable within a preset time period, the value of the performance indicator of the network device and the related performance indicator is the instantaneous usage value.

6. The method according to claim 4, characterized in that If the collected instantaneous usage value is unstable within a preset time period, the performance indicator of the network device and the value of the related performance indicator are taken as the average value.

7. The method according to claim 6, characterized in that The duration of the monitoring period is negatively correlated with the value of the performance indicator.

8. A device for implementing software BYPASS, characterized in that: The device comprises an acquisition module, an opening module and a closing module, wherein: The acquisition module is used to respectively acquire the values ​​of the performance indicator and the related performance indicator, wherein the performance indicator and the values ​​of the related performance indicator are used to respectively characterize the load degree of the processing capacity of the network device from corresponding dimensions; The enabling module is configured to trigger the software BYPASS function if the value of the performance indicator reaches a triggering threshold of the software BYPASS function when the software BYPASS function of the network device is not enabled; The closing module is used to exit the software BYPASS function when the software BYPASS function of the network device is turned on and if the values ​​of the performance indicator and the related performance indicator both reach the exit threshold of the software BYPASS.

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

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the method according to any one of claims 1 to 8 is implemented.

Images