Management thread pool system based on MyThread

Abstract

The invention discloses a management thread pool system based on MyThread, relates to the technical field of computer science, and solves the technical problems that in the prior art, after the performance of a thread pool meets a preset performance requirement through running state data, a request updating parameter is sent to a service system, a rejection strategy can be generated due to task accumulation of the thread pool is not considered, and the service performance of the service system is influenced. The technical problem that existing services cannot run normally is solved. According to the method, the basic component is arranged, and the corresponding queue capacity is distributed through the thread pool manager according to the user application; parameters of a thread pool are customized by a user; judging whether the parameter setting of the user-defined thread pool is reasonable or not according to the MyThread; if yes, continuing to operate the system; if not, dynamically changing the parameters in an instantiation mode; judging whether the parameter of the thread pool reaches a threshold value or not; performing point burying on the thread pool parameters to obtain position information, and judging whether a fault occurs at a corresponding position or not according to the position information; and the thread pool can run more efficiently.

Description

Technical Field

[0001] The invention belongs to the field of computer science, relates to thread pool management technology, and specifically is a MyThread-based management thread pool system. Background Art

[0002] The thread pool is a tool for managing threads based on the pooling concept, which often appears in multi-threaded servers. Through the thread pool, multiple threads can be maintained, waiting for the supervisor to assign concurrently executable tasks. Through the thread pool, on the one hand, the cost of creating and destroying threads when processing tasks is avoided, and on the other hand, the problem of over-scheduling caused by the expansion of the number of threads is avoided, ensuring full utilization of the kernel. The creation and destruction of threads is a costly operation, because the operating system needs to allocate and recycle a series of resources for threads. Through the thread pool, existing threads can be reused to avoid frequent creation and destruction of threads, thereby significantly reducing this part of the cost. Each thread requires a certain amount of memory to store its stack, local variables and other information. By controlling the number of threads in the thread pool, memory waste caused by too many threads can be avoided. The thread pool can handle multiple tasks at the same time, improving the concurrent processing capability of the system, which is particularly important for application scenarios that need to handle a large number of concurrent requests. By setting the maximum number of threads in the thread pool, the number of tasks executed simultaneously can be limited to avoid system overload and resource exhaustion, which helps protect the system from the impact of sudden high concurrent requests. The thread pool provides a wealth of configuration options and monitoring mechanisms, allowing developers to easily manage and tune the performance of the thread pool.

[0003] The prior art (invention patent application with publication number CN117170842A) discloses a thread pool management architecture and a thread pool management method; the prior art includes: a business system and a thread pool management system, an SDK tool is deployed in the business system, the SDK tool provides a first interface and a second interface, the business system calls the thread pool provided by the target manufacturer for processing business requests through the first interface, and the business system is connected to the thread pool management system through the second interface; the business system uploads the running status data collected from the thread pool to the thread pool management system through the first interface, and when the thread pool management system determines that the thread pool performance meets the preset performance requirements based on the running status data, it sends a request to update parameters to the business system through the second interface, so that the business system adjusts the thread pool to meet the specifications of the preset performance requirements; the prior art will send a request to update parameters to the business system only after it determines that the thread pool performance meets the preset performance requirements through the running status data, and does not take into account the rejection strategy that will occur when the thread pool tasks are piled up and the monitoring unit is not installed, which may cause the existing business to fail to operate normally and the problem that the cause of the failure cannot be found.

[0004] The present invention provides a MyThread-based management thread pool system to solve the above technical problems. Summary of the invention

[0005] The present invention aims to solve at least one of the technical problems existing in the prior art; to this end, the present invention proposes a management thread pool system based on MyThread, which is used to solve the technical problem that the prior art will only send a request to the business system to update parameters after it concludes that the thread pool performance meets the preset performance requirements through running status data, and does not take into account the rejection strategy caused by thread pool task accumulation and the lack of a monitoring unit, which may cause the existing business to fail to operate normally and the inability to find the cause of a failure.

[0006] To achieve the above-mentioned purpose, the first aspect of the present invention provides a management thread pool system based on MyThread, including: a basic component module, a control management module, a monitoring extension and a notification warning module;

[0007] Basic component module: Set up basic components on the server side, including configuration center, registration center, and console;

[0008] Control management module: obtain the queue capacity of the thread pool and the queue capacity required by the user application; allocate the corresponding queue capacity according to the user application through the thread pool manager; define the parameters of the user-defined thread pool through the user; determine whether the parameter settings of the user-defined thread pool are reasonable according to MyThread; if yes, continue to run the system; if no, MyThread dynamically changes the parameters through instantiation; determine whether the parameters of the thread pool reach the threshold; if yes, issue a warning signal; if no, continue to judge; among them, the thread pool parameters include: the number of core thread pools, the maximum number of thread pools, and the blocking queue capacity;

[0009] Monitoring extension module: Track thread pool parameters to obtain location information, and monitor the location information in real time by connecting Prometheus and Grafana through MyThread; determine whether a fault occurs at the corresponding location based on the location information; if so, issue an alarm signal; if not, continue detection.

[0010] Preferably, the system also includes a notification and warning module, which is used to determine whether a warning signal occurs during the thread pool management process; if so, an alarm signal is issued through a built-in alarm channel to notify the user and the thread pool manager; if not, monitoring continues; wherein the warning signal includes: a warning signal, an alarm signal and a reminder signal.

[0011] The present invention can timely discover system performance bottlenecks and abnormal situations by setting up a notification and warning module to monitor the status of the thread pool in real time; once an abnormality is detected, the system can immediately send an alarm to relevant personnel through the notification and warning module, thereby quickly responding to and solving the problem.

[0012] Preferably, the allocating corresponding queue capacity according to user application through the thread pool manager includes:

[0013] The queue capacity of the thread pool is retrieved and marked as XR, and the required queue capacity requested by the user is marked as DR; the user sets the corresponding priority level when submitting the task and marks it as Ai; the thread pool manager sets the corresponding level according to the user's submitted task and marks it as Bi; where XR≥DR;

[0014] The actual allocated queue capacity is calculated by the formula SR=DR×{[(Ai×α+Bi×β) / ɡ]×100%}; wherein i is the level value; i=1,2,3,4,5; α, β, ɡ are all proportional coefficients greater than 0 and less than 1.

[0015] The present invention allocates corresponding queue capacity according to user application through the thread pool manager, which can reduce the waiting time of user requests in the queue, thereby improving the response speed of the system; when the system faces a large number of concurrent requests, dynamically allocating queue capacity can help balance the load between different users, avoid some users from suffering from performance bottlenecks due to too long queues, and dynamically allocating queue capacity can also help the system use resources more efficiently.

[0016] Preferably, the parameters of the thread pool defined by the user include:

[0017] Call the configuration center on the server side, which allows users to view the configuration of the current thread pool and provides users with several forms to enter new configuration values;

[0018] The new configuration value should be sent to the configuration center through the console; determine whether the console and the configuration center send confirmation notifications at the same time; if yes, the user successfully customizes the parameters of the thread pool; if no, the user fails to customize the parameters of the thread pool and sends a reminder signal.

[0019] The present invention allows users to dynamically adjust the configuration parameters of the thread pool according to actual operating conditions and needs, without restarting the service or making complex configuration modifications; by adjusting the thread pool configuration to optimize performance and resource utilization, the system can more flexibly respond to changes in business volume; and all thread pool configurations are stored in a configuration center for centralized management and maintenance.

[0020] Preferably, judging whether the parameter settings of the user-defined thread pool are reasonable according to MyThread includes:

[0021] Retrieve the parameters of the user-defined thread pool and introduce the parameters of the user-defined thread pool into MyThread;

[0022] Determine whether MyThread's work tasks based on parameters and system resources are blocked; if yes, it is determined that the parameter settings of the user-defined thread pool are unreasonable; if no, it is determined that the parameter settings of the user-defined thread pool are reasonable.

[0023] The present invention allows users to customize parameters. MyThread dynamically adjusts the size of the thread pool according to the specific workload, so that it can flexibly adapt to different application requirements, thereby supporting a wider range of application scenarios and more efficiently utilizing system resources. By monitoring the working status of the thread pool and the usage of system resources, potential blocking problems can be discovered in a timely manner. When there is a shortage of system resources or an overlong task queue, it can be determined whether the parameter settings of the thread pool are reasonable based on preset thresholds or logic, thereby avoiding complete blocking of the system due to resource exhaustion.

[0024] Preferably, the dynamically changing parameters by instantiation includes:

[0025] Call the registration center and create a client, and manage the instance performance indicators of the client registered to the server through the registration center;

[0026] Get the normal performance indicator range from the database to determine whether the instance performance indicator is within the normal performance indicator range; if yes, continue the instantiation process; if not, call the configuration center; in the configuration center, use long polling and asynchronous Servlet mechanism to monitor users who change unreasonable user-defined thread pool parameters in the console.

[0027] It should be noted that operations for managing instance performance indicators include: instance registration, heartbeat, and expiration deletion.

[0028] The present invention allows users to dynamically adjust configuration parameters without restarting applications by using a configuration center, which improves the flexibility and response speed of the system and reduces the downtime required for configuration changes; long polling and asynchronous Servlet mechanisms ensure that the configuration center can push configuration changes to the client end efficiently and in real time, and also reduce the number of communications between the client end and the configuration center, reducing the overall load of the system.

[0029] Preferably, the determining whether the parameter of the thread pool reaches a threshold value includes:

[0030] Call the console and obtain the parameter capacity threshold from the console; use the parameters of the user-defined thread pool as the running parameters;

[0031] Determine whether the number of running parameters is lower than the parameter capacity threshold. If yes, allow the running parameters to enter the thread pool; if not, implement a rejection strategy and feed back the exceeded number of running parameters to the user through the console.

[0032] The present invention can prevent resource overload or system crash caused by too many parameters by checking whether the number of parameters exceeds the capacity threshold before the parameters enter the thread pool, which is conducive to discovering and handling potential error situations in advance, and also helps to improve the stability and reliability of the system; users can also adjust the thread pool parameters according to the actual business load, so that the system can handle concurrent tasks more effectively.

[0033] Preferably, the real-time monitoring of the location information by combining Prometheus and Grafana through MyThread includes:

[0034] Retrieve the location information, write and embed the springboot-starter unit at the corresponding location of the embedding point in MyThread; use the ecological extension technology to seamlessly access the springboot unit;

[0035] The springboot-starter unit is seamlessly integrated with the springboot unit through high-scalability technology; the tomcat and springboot-task thread pools are monitored internally through MyThread.

[0036] It should be noted that when using MyThread to monitor tomcat internally and to monitor the springboot-task thread pool, users must make corresponding configurations in the code according to the required requirements.

[0037] By embedding the spring-boot-starter unit, the present invention can greatly reduce the workload of manual configuration and improve development efficiency. The starter mechanism of Springboot allows users to quickly integrate various functions by adding simple dependencies; this makes it easy to integrate the required functions by embedding the springboot-starter unit inside MyThread without worrying about complex integration issues.

[0038] Preferably, judging whether a fault occurs at a corresponding position according to the position information includes:

[0039] Get the normal location information range from the database, and collect the real-time location information through MyThread; determine whether the real-time location information is within the normal location information range; if yes, determine that there is no fault at the corresponding location; if not, determine that there is a fault at the corresponding location.

[0040] It should be noted that the types of failures include: task accumulation, rejection strategy, system timeout, and circuit breaker problems.

[0041] The present invention collects location information in real time through MyThread, and the system can immediately detect any abnormal changes that deviate from the normal range, which helps to discover potential problems or faults in a timely manner, so as to take necessary measures to prevent or repair them, avoid the expansion of faults or cause more serious consequences.

[0042] Compared with the prior art, the present invention has the following beneficial effects:

[0043] 1. The present invention constructs a thread pool management system through four major modules: data collection, control management, monitoring extension, and notification and warning; basic components are set on the server side through the basic component module; the thread pool capacity is managed through the control management module, so that the system can more effectively manage the allocation and execution order of the thread pool, ensuring that key tasks are given priority, thereby improving the overall efficiency and response speed of the system; the monitoring extension module is used to monitor in real time whether there is a fault at the thread pool parameter position, which enables system administrators and developers to quickly locate potential problems; an alarm signal is issued when a warning signal is detected through the notification and warning module. This automated alarm mechanism can greatly reduce the need for manual intervention and improve the stability and reliability of the system.

[0044] 2. The present invention manages the thread pool through MyThread, allowing users to dynamically adjust the configuration parameters of the thread pool according to actual operating conditions and needs, without restarting the service or making complex configuration changes; by adjusting the thread pool configuration to optimize performance and resource utilization, the system can more flexibly respond to changes in business volume; and all thread pool configurations are stored in the configuration center for centralized management and maintenance; by monitoring the working status of the thread pool and the usage of system resources, potential blocking problems can be discovered in a timely manner; when there is a shortage of system resources or a long task queue, the thread pool parameter settings can be determined to be reasonable based on preset thresholds or logic, thereby avoiding complete blocking of the system due to resource exhaustion. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0046] Figure 1 It is a schematic diagram of the module structure of the present invention;

[0047] Figure 2 A schematic diagram of specific steps for managing a thread pool according to the present invention;

[0048] Figure 3A schematic diagram of the process of controlling and managing a thread pool according to the present invention;

[0049] Figure 4 The figure is a flow chart of monitoring and managing thread pools according to the present invention. DETAILED DESCRIPTION

[0050] The technical solution of the present invention will be clearly and completely described below in conjunction with the embodiments. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0051] See also Figure 1-Figure 2 , the first aspect of the present invention provides a MyThread-based management thread pool system, including: a basic component module, a control management module, a monitoring extension module, and a notification warning module;

[0052] Basic component module: Set up basic components on the server side, including configuration center, registration center, and console;

[0053] Control management module: obtain the queue capacity of the thread pool and the queue capacity required by the user application; allocate the corresponding queue capacity according to the user application through the thread pool manager; define the parameters of the user-defined thread pool through the user; determine whether the parameter settings of the user-defined thread pool are reasonable according to MyThread; if yes, continue to run the system; if no, MyThread dynamically changes the parameters through instantiation; determine whether the parameters of the thread pool reach the threshold; if yes, issue a warning signal; if no, continue to judge; among them, the thread pool parameters include: the number of core thread pools, the maximum number of thread pools, and the blocking queue capacity;

[0054] Monitoring extension module: Track thread pool parameters to obtain location information, and monitor the location information in real time by combining MyThread with Prometheus and Grafana; determine whether a fault occurs at the corresponding location based on the location information; if yes, issue an alarm signal; if no, continue detection;

[0055] Notification and warning module: used to determine whether a warning signal occurs during the thread pool management process; if so, an alarm signal is issued through the built-in alarm channel to notify the user and thread pool manager; if not, continue monitoring; among them, the warning signal includes: warning signal, alarm signal and reminder signal.

[0056] See also Figure 3, control the process of managing the thread pool, set up basic components on the server side, including: configuration center, registration center, console; obtain the queue capacity of the thread pool and mark it as XR, and mark the required queue capacity applied by the user as DR; the user sets the corresponding priority level as Ai when submitting a task; the thread pool manager sets the corresponding level according to the user's submitted task and marks it as Bi; where XR≥DR;

[0057] The actual allocated queue capacity is calculated by the formula SR = DR × {[(Ai × α + Bi × β) / ɡ] × 100%}; where i is the level value; i = 1, 2, 3, 4, 5; α, β, ɡ are all proportional coefficients greater than 0 and less than 1; the configuration center on the server is called, and the configuration center allows the user to view the configuration of the current thread pool, and provides the user with several forms to enter new configuration values;

[0058] The new configuration value should be sent to the configuration center through the console; determine whether the console and the configuration center send confirmation notifications at the same time; if yes, the user successfully customizes the parameters of the thread pool; if no, the user customizes the parameters of the thread pool unsuccessfully and sends a reminder signal; retrieve the parameters of the user-defined thread pool and introduce the parameters of the user-defined thread pool into MyThread;

[0059] Determine whether MyThread's work tasks based on parameters and system resources are blocked; if yes, determine that the parameter settings of the user-defined thread pool are unreasonable; if no, determine that the parameter settings of the user-defined thread pool are reasonable; call the registration center and create the Client, and manage the instance performance indicators of the Client registered to the Server through the registration center;

[0060] Obtain the normal performance indicator range from the database to determine whether the instance performance indicator is within the normal performance indicator range; if yes, continue to execute the instantiation process; if no, call the configuration center; use long polling and asynchronous Servlet mechanism in the configuration center to monitor the unreasonable user-defined thread pool parameters changed by users in the console; call the console and obtain the parameter capacity threshold from the console; use the user-defined thread pool parameters as running parameters;

[0061] Determine whether the number of running parameters is lower than the parameter capacity threshold. If yes, allow the running parameters to enter the thread pool; if not, implement a rejection strategy and feed back the exceeded number of running parameters to the user through the console.

[0062] For example, there is a thread pool that needs to be managed. Basic components are set on the server side, including: configuration center, registration center, and console; the queue capacity XR of the thread pool is obtained as 1000, the required queue capacity DR1 applied by user A is 150; the required queue capacity DR2 applied by user B is 50; user A sets the priority level to level 3 when submitting a task; the thread pool manager sets the corresponding level to 1 according to the user's submitted task; user B sets the priority level to level 2 when submitting a task; the thread pool manager sets the corresponding level to 1 according to the user's submitted task; set α and β to 0.1; set ɡ to 0.5; by calculating 150×{[(3×0.1+1×0.1) / 0.5]×100%}=120, it is concluded The queue capacity actually allocated to user A is 120; by calculating 50×{[(2×0.1+1×0.1) / 0.5]×100%}=30, it can be concluded that the queue capacity actually allocated to user A is 30; call the configuration center on the server side, allow users A and B to view the configuration of the current thread pool through the configuration center, and provide two forms for users A and B to enter new configuration values; user A should send the new configuration value to the configuration center through the console, and the console and the configuration center will send confirmation notifications at the same time, then user A successfully customizes the parameters of the thread pool; user B should send the new configuration value to the configuration center through the console, and the console and the configuration center will not send confirmation notifications at the same time, then user B fails to customize the parameters of the thread pool and sends a reminder signal.

[0063] See also Figure 4 , monitor the process of managing the thread pool, retrieve the location information, write and embed the springboot-starter unit at the corresponding location of the embedding point through MyThread; use the ecological extension technology to seamlessly access the springboot unit;

[0064] The springboot-starter unit is seamlessly integrated with the springboot unit through high-scalability technology; the tomcat and springboot-task thread pools are monitored internally through MyThread; the normal location information range is obtained from the database, and the real-time location information is collected through MyThread; it is determined whether the real-time location information is within the normal location information range; if so, it is determined that there is no fault at the corresponding location; if not, it is determined that there is a fault at the corresponding location.

[0065] Part of the data in the above formula is calculated by removing the dimension and taking its numerical value. The formula is a formula closest to the actual situation obtained by software simulation of a large amount of collected data; the preset parameters and preset thresholds in the formula are set by technical personnel in this field according to actual conditions or obtained through simulation of a large amount of data.

[0066] The working principle of the present invention is as follows: the present invention sets basic components on the server side; obtains the queue capacity of the thread pool and the queue capacity required by the user application; allocates the corresponding queue capacity according to the user application through the thread pool manager; customizes the parameters of the thread pool by the user; determines whether the parameter settings of the user-defined thread pool are reasonable according to MyThread; if yes, continues to run the system; if no, MyThread dynamically changes the parameters by instantiation; determines whether the parameters of the thread pool reach the threshold; embeds the thread pool parameters to obtain the location information, and monitors the location information in real time by combining Prometheus and Grafana through MyThread; determines whether a fault occurs at the corresponding position according to the location information.

[0067] The above embodiments are only used to illustrate the technical method of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical method of the present invention may be modified or replaced by equivalents without departing from the spirit and scope of the technical method of the present invention.

Claims

1. A management thread pool system based on MyThread, characterized in that: include: Basic component module, control management module, monitoring extension and notification warning module; Basic component module: Set up basic components on the server side, including configuration center, registration center, and console; Control management module: obtain the queue capacity of the thread pool and the queue capacity required by the user application; allocate the corresponding queue capacity according to the user application through the thread pool manager; define the parameters of the user-defined thread pool through the user; determine whether the parameter settings of the user-defined thread pool are reasonable according to MyThread; if yes, continue to run the system; if no, MyThread dynamically changes the parameters through instantiation; determine whether the parameters of the thread pool reach the threshold; if yes, issue a warning signal; if no, continue to judge; among them, the thread pool parameters include: the number of core thread pools, the maximum number of thread pools, and the blocking queue capacity; Monitoring extension module: Track thread pool parameters to obtain location information, and monitor the location information in real time by connecting Prometheus and Grafana through MyThread; determine whether a fault occurs at the corresponding location based on the location information; if yes, issue an alarm signal; if not, continue detection.

2. According to the MyThread-based management thread pool system of claim 1, it is characterized in that: The system also includes a notification warning module for determining whether a warning signal occurs during thread pool management; If yes, an alarm signal is sent out through the built-in alarm channel to notify the user and thread pool manager; If not, continue monitoring; the warning signals include: early warning signals, alarm signals and reminder signals.

3. According to the MyThread-based management thread pool system of claim 1, it is characterized in that: The thread pool manager allocates corresponding queue capacity according to the user's application, including: The queue capacity of the thread pool is retrieved and marked as XR, and the required queue capacity requested by the user is marked as DR; the user sets the corresponding priority level when submitting the task and marks it as Ai; the thread pool manager sets the corresponding level according to the user's submitted task and marks it as Bi; where XR≥DR; The actual allocated queue capacity is calculated by the formula SR=DR×{[(Ai×α+Bi×β) / ɡ]×100%}; wherein i is the level value; i=1,2,3,4,5; α, β, ɡ are all proportional coefficients greater than 0 and less than 1.

4. A MyThread-based management thread pool system according to claim 1, characterized in that: The parameters of the user-defined thread pool include: Call the configuration center on the server side, which allows users to view the configuration of the current thread pool and provides users with several forms to enter new configuration values; The new configuration value should be sent to the configuration center through the console; determine whether the console and the configuration center send confirmation notifications at the same time; if yes, the user successfully customizes the parameters of the thread pool; if no, the user fails to customize the parameters of the thread pool and sends a reminder signal.

5. A MyThread-based management thread pool system according to claim 1, characterized in that: The method of judging whether the parameter settings of the user-defined thread pool are reasonable according to MyThread includes: Retrieve the parameters of the user-defined thread pool and introduce the parameters of the user-defined thread pool into MyThread; Determine whether MyThread's parameter-based work tasks and system resources are blocked; if yes, it is determined that the parameter settings of the user-defined thread pool are unreasonable; if not, it is determined that the parameter settings of the user-defined thread pool are reasonable.

6. A MyThread-based management thread pool system according to claim 1, characterized in that: The dynamically changing parameters by instantiation includes: Call the registration center and create a client, and manage the instance performance indicators of the client registered to the server through the registration center; Get the normal performance indicator range from the database to determine whether the instance performance indicator is within the normal performance indicator range; if yes, continue the instantiation process; if not, call the configuration center; in the configuration center, use long polling and asynchronous Servlet mechanism to monitor users who change unreasonable user-defined thread pool parameters in the console.

7. A MyThread-based management thread pool system according to claim 1, characterized in that: The step of determining whether the parameter of the thread pool reaches a threshold value includes: Call the console and obtain the parameter capacity threshold from the console; use the parameters of the user-defined thread pool as the running parameters; Determine whether the number of running parameters is lower than the parameter capacity threshold. If yes, allow the running parameters to enter the thread pool; if not, implement a rejection strategy and feed back the exceeded number of running parameters to the user through the console.

8. A MyThread-based management thread pool system according to claim 1, characterized in that: The real-time monitoring of location information by combining Prometheus and Grafana through MyThread includes: Retrieve the location information, write and embed the springboot-starter unit at the corresponding location of the embedding point in MyThread; use the ecological extension technology to seamlessly access the springboot unit; The springboot-starter unit is seamlessly integrated with the springboot unit through high-scalability technology; the tomcat and springboot-task thread pools are monitored internally through MyThread.

9. A MyThread-based management thread pool system according to claim 1, characterized in that: The determining whether a fault occurs at a corresponding position according to the position information includes: Get the normal location information range from the database, and collect the real-time location information through MyThread; determine whether the real-time location information is within the normal location information range; if yes, determine that there is no fault at the corresponding location; if not, determine that there is a fault at the corresponding location.

Images