Risk control management method and system for concentrator

Abstract

The present invention discloses a risk control management method and system for a concentrator, and relates to the technical field of concentrators. The method and system are used to solve the problem that the concentrator itself has no ability to solve faults, and maintenance personnel are required to be on-site to check and maintain the concentrator regardless of whether the concentrator has a simple fault or a complex fault. The system log in the concentrator is analyzed to quickly determine the sending status of the corresponding data packet of the concentrator, so as to analyze whether the concentrator itself is online or offline, and can take corresponding measures in time to solve the offline problem or prompt the maintenance personnel with the specific cause of the fault, thereby improving the work efficiency of the maintenance personnel and ensuring that the concentrator can work normally online. If the concentrator cannot upload a data packet to the monitoring platform, the maintenance personnel on site can confirm the fault and carry out maintenance work in the first time through targeted fault troubleshooting, thereby improving the efficiency and accuracy of the concentrator fault handling and the maintenance efficiency of the maintenance personnel.

Description

Technical Field

[0001] The present invention relates to the technical field of concentrators, and in particular to a risk control management method and system for concentrators. Background Art

[0002] A concentrator is a central connection point device that connects terminals, computers or communication equipment. It becomes the central point where cables converge. In areas where several terminals are densely populated, in order to reduce communication lines, the terminals are usually connected to the concentrator first, and then the concentrator is connected to the computer's communication controller via a high-speed line. Therefore, the concentrator is also an effective device for sharing lines and improving line utilization.

[0003] As a complex device, the concentrator contains multiple components and functional modules. When a concentrator fails, the concentrator itself does not have the ability to resolve the fault. Regardless of whether the concentrator has a simple or complex fault, maintenance personnel are required to be present for inspection and maintenance. This takes a lot of time to locate the specific cause and location of the fault, and requires step-by-step troubleshooting and testing, which reduces the work efficiency of maintenance personnel and increases their time costs. Summary of the invention

[0004] The purpose of the present invention is to provide a risk control management method and system for a concentrator to solve the problems raised by the above background technology.

[0005] The object of the present invention can be achieved by the following technical solutions: a risk control management system for a concentrator, comprising a concentrator self-check module, a troubleshooting module, a monitoring platform, a light display module, a local database and a cloud database;

[0006] The concentrator self-check module is used to analyze the collection status of the concentrator, collect downlink data from the downlink device according to the preset collection frequency, verify the downlink data, and if there is a null value in the downlink data, mark the downlink data as abnormal data and count the number of abnormal data, count the number of corresponding downlink data, and obtain the collection anomaly index of the concentrator through analysis. Based on the collection anomaly index, the collection status of the concentrator is determined to be normal or abnormal, and the data collected by the concentrator with a normal collection status is summarized and processed to obtain a data packet, which is sent to the monitoring platform, and the corresponding system log is obtained at the same time to determine whether the sending status of the corresponding data packet of the concentrator is sent or not sent;

[0007] The troubleshooting module includes a self-correction unit and a troubleshooting detection unit. The self-correction unit is used to analyze the reasons why the concentrator collects abnormal data from downlink devices. When an abnormal collection signal is identified, the number of occurrences of the abnormal collection signal is counted. When the abnormal collection signal is identified, the system time and terminal address code of the concentrator are covered or corrected. After the covering or correction is completed, a collection signal is generated and sent to the concentrator self-check module; the troubleshooting unit is used to analyze the reasons why the concentrator fails to upload data packets. When a troubleshooting signal is identified, the number of occurrences of the collection signal is counted, the network address of the monitoring platform is obtained from the database, and a number of data packets are sent to the monitoring platform through a network detection command to obtain statistical information of the network detection command. The data packet loss rate and network delay are extracted from the statistical information of the network detection command, and the communication anomaly index of the concentrator is analyzed to further analyze the concentrator and generate a communication fault signal or a system fault signal;

[0008] The monitoring platform is used to receive data packets sent by the concentrator, parse the data packets uploaded by the concentrator to obtain the number of the online concentrator, obtain the concentrator list from the cloud database, match the number of the online concentrator with the concentrator list to obtain the list of concentrators to be tested, record the concentrators in the list of concentrators to be tested as concentrators to be tested, analyze the operating status of the concentrators to be tested, send several acquisition signals to the concentrators to be tested and wait for receiving new data packets, parse the new data packets to obtain the number of the concentrator, match the number of the concentrator with the number of the concentrator to be tested, if the number of the concentrator matches the number of the concentrator to be tested successfully, the state of the concentrator to be tested is determined to be an indirect offline state, otherwise the state of the concentrator to be tested is determined to be a continuous offline state;

[0009] The light display module is used to receive communication fault signals and system fault signals, and display them in the form of LED prompt lights according to the communication fault signals and system fault signals;

[0010] The local database is used to store the preset network configuration information of the concentrator and the preset terminal address code of the concentrator;

[0011] The cloud database is used to store the concentrator list and the data packets sent by the concentrator.

[0012] Preferably, the collection status of the concentrator is analyzed, and the analysis process is as follows:

[0013] The concentrator collects downlink data from the downlink device according to the preset collection frequency or when the collection signal is identified, counts the number of downlink data collected by the concentrator, obtains the value of the sub-data corresponding to the downlink data and compares the null value. When any sub-data in the downlink data is a null value, the downlink data is marked as null data, and the number of null data is counted. When all the sub-data in the downlink data are not null values, the downlink data is marked as valid data, and the number of valid data is counted.

[0014] By formula Calculate the collection anomaly index YC of the concentrator, where N is the number of downlink data, a1 is the weight factor of valid data, a2 is the weight factor of empty data, and e is a natural constant. Compare the collection anomaly index of the concentrator with the preset collection anomaly index threshold. If the anomaly index of the concentrator is greater than the preset collection anomaly index threshold, the collection state of the concentrator is determined to be abnormal, and a collection anomaly signal is generated. The troubleshooting signal is sent to the troubleshooting module. If the anomaly index of the concentrator is less than the preset collection anomaly index threshold, the collection state of the concentrator is determined to be normal, and a collection normal signal is generated.

[0015] Summarize and process the valid data to form a data packet, send the data packet to the monitoring platform, collect the system time of the current concentrator and record it as the capture time, obtain the system log of the concentrator, where the system log includes time, event level, event description and specific information, and the event level includes information class (INFO), warning class (WARN I NG) and error class (ERROR), select the system log after the capture time and filter the system log with the event level of error class according to the event level keyword;

[0016] The event description corresponding to the system log of the error class is matched according to the preset data packet information keyword. When the preset data packet information keyword matches the event description corresponding to the system log of the error class successfully, the data packet sending status of the concentrator is determined to be an upload failure status, and a troubleshooting signal is generated and sent to the troubleshooting module. When the preset data packet information keyword does not match the event description corresponding to the system log of the error class successfully, the data packet sending status of the concentrator is determined to be an upload success status, and a normal signal is generated.

[0017] Preferably, the reason why the concentrator collects abnormal data of the downstream device is analyzed, and the analysis process is as follows:

[0018] When an abnormal acquisition signal is identified, the GPRS signal strength of the concentrator is obtained, and the GPRS signal strength of the concentrator is compared with the set signal strength threshold. If the GPRS signal strength of the concentrator is less than the set signal strength threshold, it is determined that the cause of the abnormal acquisition of the concentrator is caused by the network signal strength, and a collection signal is generated and sent to the concentrator self-check module. When the GPRS signal strength of the concentrator is greater than the set signal strength threshold, the preset network configuration information corresponding to the concentrator is obtained from the local database;

[0019] The preset network configuration information is compared with the network configuration information in the current concentrator one by one. If the comparison between the preset network configuration information and the network configuration information in the current concentrator fails, it means that the reason for the abnormal collection of the concentrator is caused by the error of the network configuration information. The network configuration information in the current concentrator is overwritten with the preset network configuration information. After the overwriting is completed, a collection signal is generated and sent to the concentrator self-test module. If the preset network configuration information is successfully compared with the network configuration information in the current concentrator, the terminal address code of the current concentrator is obtained, and the preset terminal address code of the concentrator is obtained from the local database. The terminal address code of the current concentrator is compared with the preset terminal address code. If If the comparison between the terminal address code of the current concentrator and the preset terminal address code is unsuccessful, it means that the reason for the abnormal collection of the concentrator is caused by the incorrect configuration of the terminal address code. The terminal address code of the current concentrator is overwritten with the preset terminal address code. After the overwriting is completed, an acquisition signal is generated and sent to the concentrator self-test module. If the comparison between the terminal address code of the current concentrator and the preset terminal address code is successful, it means that the reason for the abnormal collection of the concentrator is caused by the system time error of the concentrator. Then, the system time in the monitoring platform is obtained, and the system time in the concentrator is calibrated based on the system time in the monitoring platform. After the calibration is completed, an acquisition signal is generated and sent to the concentrator self-test module.

[0020] Preferably, the reason why the concentrator fails to upload the data packet is analyzed, and the analysis process is as follows:

[0021] When a troubleshooting signal is identified, the network address of the monitoring platform is obtained from the local database, and a number of data packets are sent to the network address of the monitoring platform through a network detection command to obtain statistical information of the network detection command. The data packet loss rate DS and network delay MS are extracted from the statistical information of the network detection command, and the communication anomaly index TX of the concentrator is calculated by the formula TX=DS×b1+MS×b2, where b1 is the preset loss rate weight factor and b2 is the preset network delay weight factor;

[0022] The communication anomaly index of the concentrator is compared with the preset communication anomaly index threshold. When the communication anomaly index of the concentrator is greater than the preset communication anomaly index threshold, it means that there is a problem with the communication module of the concentrator, and a communication fault signal is generated. When the communication anomaly index of the concentrator is less than the preset communication anomaly index threshold, the number of times the collection abnormality signal is identified is counted and compared with the preset threshold of the number of abnormal signals within the collection time. When the number of times the collection abnormality signal is identified is greater than the threshold of the number of abnormal signals within the preset collection time, it means that the communication module of the concentrator is normal, and it is judged that the system of the concentrator has a fault, then a system fault signal is generated, and the communication fault signal or system abnormality is sent to the light display module.

[0023] Preferably, the operating status of the concentrator to be tested is analyzed, and the analysis process is as follows:

[0024] Receive the data packet sent by the concentrator and send it to the cloud database for storage, parse the data packet sent by the concentrator to obtain the number of the online concentrator and record it as the online number, obtain the concentrator list from the cloud database, where the concentrator list contains the numbers of all concentrators, match the number of the online concentrator with the concentrator list, and when a certain online number exists in the concentrator list, remove the online number from the concentrator list, so as to remove all online numbers from the concentrator list and obtain the concentrator list to be verified;

[0025] The concentrators in the list of concentrators to be tested are recorded as concentrators to be tested. According to the number of the concentrator to be tested, several collection signals are sent to the corresponding concentrators and wait for receiving new data packets. If the monitoring platform receives a new data packet, the new data packet is parsed to obtain the number of the concentrator, and the number of the concentrator is matched with the list of concentrators to be tested. If the number of the concentrator matches the list of concentrators to be tested successfully, the operating status of the concentrator to be tested is determined to be an intermittent offline state. If the number of the concentrator fails to match the list of concentrators to be tested, the operating status of the concentrator to be tested is determined to be a continuous offline state, and a prompt signal is generated according to the operating status of the concentrator to be tested.

[0026] When the running state of the concentrator is an indirect offline state, the system log of the concentrator is obtained, and the event level in the system log of the concentrator is identified as an error class and an offline keyword, so as to count the number of times the concentrator is offline, and the offline frequency of the concentrator is calculated according to the preset statistical time and the number of times the concentrator is offline, and the offline frequency of the concentrator is compared with the preset offline frequency threshold. If the offline frequency of the concentrator is greater than the preset offline frequency threshold, a frequent offline signal is generated;

[0027] When the running status of the concentrator is continuously offline, the area where the concentrator is located is queried from the cloud database according to the concentrator number to obtain the power supply and network conditions of the area where the concentrator is located. If the power supply and network conditions of the area where the concentrator is located are normal, a continuous offline signal is generated;

[0028] Corresponding maintenance information is generated according to the frequent offline signal or the continuous offline signal, and the maintenance information is sent to the corresponding intelligent terminal.

[0029] The risk control management method for a concentrator comprises the following steps:

[0030] Q1. Collect the downlink data from the downlink device according to the preset collection frequency, verify the downlink data to determine whether the collection state of the concentrator is normal or abnormal, and generate a normal collection signal or an abnormal collection signal;

[0031] Q2: When an abnormal signal is detected, the concentrator is self-calibrated. When a normal signal is detected, the data of the downstream device is aggregated and processed to form a data packet, which is sent to the monitoring platform. Based on the system log in the concentrator, the sending status of the corresponding data packet of the concentrator is determined as sent or not sent, thereby generating a troubleshooting signal or a regular signal.

[0032] Q3. When the troubleshooting signal is identified, the network of the concentrator is analyzed or the number of times the abnormal signal is collected is counted, so as to generate a communication fault signal or a network fault signal and display it in the form of an LED light display;

[0033] Q4. Receive the data packet sent by the concentrator and parse it to obtain the number of the online concentrator, obtain the list of concentrators to be tested based on the number of the online concentrator, send a collection signal to the concentrator according to the list of concentrators to be tested and wait for receiving new data packets, so as to determine the operating status of the concentrator to be tested as an indirect offline state or a continuous offline state, generate corresponding prompt information based on the operating status of the concentrator to be tested and send it to the corresponding smart terminal.

[0034] Beneficial effects of the present invention:

[0035] 1. Analyze the system logs in the concentrator and quickly determine the sending status of the corresponding data packets of the concentrator. In this way, the concentrator can be analyzed to determine whether it is online or offline. In this way, corresponding measures can be taken in time to solve the offline problem or to prompt the maintenance personnel with the specific cause of the fault, thereby improving the work efficiency of the maintenance personnel and ensuring that the concentrator can work normally online.

[0036] 2. When the concentrator collects abnormal data, the GPRS signal strength, network configuration information and terminal address code of the concentrator are judged one by one, so that when a simple fault occurs in the concentrator, data can be sent to the monitoring platform on time through corresponding remedial measures, avoiding the concentrator being offline for a long time or the fault affecting the timeliness of the data, and reducing the workload and time cost of maintenance personnel;

[0037] 3. If the concentrator fails to upload data packets to the monitoring platform, targeted troubleshooting will enable on-site maintenance personnel to immediately identify the fault and start maintenance work, thus improving the efficiency and accuracy of concentrator fault handling and the maintenance efficiency of maintenance personnel;

[0038] 4. By determining whether the offline state of the concentrator is indirect offline state or continuous offline state, it can help the administrator better understand the fault condition of the concentrator, thereby reducing unnecessary maintenance operations and helping maintenance personnel to better handle the offline state of the concentrator. At the same time, it saves the time and energy of maintenance personnel and ensures the pertinence and effectiveness of maintenance work. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The present invention will be further described below in conjunction with the accompanying drawings.

[0040] Figure 1 It is a system block diagram of the present invention.

[0041] Figure 2 It is a flow chart of the method steps of the present invention. DETAILED DESCRIPTION

[0042] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not 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.

[0043] See also Figure 1 As shown, the present invention provides a concentrator risk control management system on the one hand, including a concentrator self-check module, a troubleshooting module, a monitoring platform, a light display module, a local database and a cloud database;

[0044] The concentrator self-check module analyzes the collection status of the concentrator. The analysis process is as follows:

[0045] The concentrator collects downlink data from the downlink device according to the preset collection frequency or when the collection signal is identified, and counts the number of downlink data collected by the concentrator, obtains the value of the sub-data corresponding to the downlink data and compares the null value. When any sub-data in the downlink data is a null value, the downlink data is marked as null data, and the number of null data Nck is counted. When all the sub-data in the downlink data are not null values, the downlink data is marked as valid data, and the number of valid data Nyx is counted.

[0046] By formula Calculate the collection anomaly index YC of the concentrator, where N is the number of downlink data, a1 is the weight factor of valid data, a2 is the weight factor of empty data, and e is a natural constant. Compare the collection anomaly index of the concentrator with the preset collection anomaly index threshold. If the anomaly index of the concentrator is greater than the preset collection anomaly index threshold, the collection state of the concentrator is determined to be abnormal, and a collection anomaly signal is generated. The troubleshooting signal is sent to the troubleshooting module. If the anomaly index of the concentrator is less than the preset collection anomaly index threshold, the collection state of the concentrator is determined to be normal, and a collection normal signal is generated.

[0047] The present invention determines the collection state of the concentrator according to the collection anomaly index of the concentrator. When the collection state of the concentrator is abnormal, it provides a basis for analyzing the cause of the abnormal collection state of the concentrator, thereby ensuring the accuracy and completeness of the downlink device data collected by the concentrator.

[0048] Summarize and process the valid data to form a data packet, send the data packet to the monitoring platform, collect the system time of the current concentrator and record it as the capture time, obtain the system log of the concentrator, where the system log includes time, event level, event description and specific information, and the event level includes information class (INFO), warning class (WARN I NG) and error class (ERROR), select the system log after the capture time and filter the system log with the event level of error class according to the event level keyword;

[0049] The event description corresponding to the system log of the error class is matched according to the preset data packet information keyword. When the preset data packet information keyword matches the event description corresponding to the system log of the error class successfully, the data packet sending status of the concentrator is determined to be an upload failure status, and a troubleshooting signal is generated and sent to the troubleshooting module. When the preset data packet information keyword does not match the event description corresponding to the system log of the error class successfully, the data packet sending status of the concentrator is determined to be an upload success status, and a normal signal is generated.

[0050] The present invention analyzes the system log in the concentrator to quickly determine the sending status of the corresponding data packet of the concentrator, thereby analyzing whether the concentrator itself is in an online state or an offline state. It can take corresponding measures in time to solve the offline problem or prompt the maintenance personnel with the specific cause of the fault, thereby improving the work efficiency of the maintenance personnel and ensuring that the concentrator can work normally online.

[0051] The troubleshooting module includes a self-correction unit and a troubleshooting detection unit. The self-correction unit analyzes the cause of abnormalities in the data collected by the concentrator for the downstream device. The analysis process is as follows:

[0052] When an abnormal acquisition signal is identified, the GPRS signal strength of the concentrator is obtained, and the GPRS signal strength of the concentrator is compared with the set signal strength threshold. If the GPRS signal strength of the concentrator is less than the set signal strength threshold, it is determined that the cause of the abnormal acquisition of the concentrator is caused by the network signal strength, and a collection signal is generated and sent to the concentrator self-check module. When the GPRS signal strength of the concentrator is greater than the set signal strength threshold, the preset network configuration information corresponding to the concentrator is obtained from the local database;

[0053] The preset network configuration information is compared with the network configuration information in the current concentrator one by one. If the comparison between the preset network configuration information and the network configuration information in the current concentrator fails, the network configuration information in the current concentrator is overwritten with the preset network configuration information. After the overwriting is completed, a collection signal is generated and sent to the concentrator self-test module. If the preset network configuration information is successfully compared with the network configuration information in the current concentrator, the terminal address code of the current concentrator is obtained, the preset terminal address code of the concentrator is obtained from the local database, and the terminal address code of the current concentrator is compared with the preset terminal address code. If the comparison between the terminal address code of the current concentrator and the preset terminal address code is successful, the terminal address code of the current concentrator is overwritten with the preset terminal address code. After the overwriting is completed, a collection signal is generated and sent to the concentrator self-test module. If the comparison between the terminal address code of the current concentrator and the preset terminal address code is successful, the system time in the monitoring platform is obtained, and the system time in the concentrator is calibrated based on the system time in the monitoring platform. After the calibration is completed, a collection signal is generated and sent to the concentrator self-test module.

[0054] The present invention determines the GPRS signal strength, network configuration information and terminal address code of the concentrator one by one, so as to obtain the reason for the abnormal data collection of the downlink device by the concentrator. If the abnormal data collection of the downlink device by the concentrator is caused by the GPRS signal strength, a collection signal is generated to collect the data of the downlink device again to ensure the integrity of the data. If the abnormal data collection of the downlink device by the concentrator is caused by the network configuration information or the system time of the concentrator, the network configuration information or the system time of the concentrator is overwritten or corrected, so as to achieve the goal that when the concentrator is offline, data can be sent to the monitoring platform on time through corresponding remedial measures, so as to avoid the influence of the long-term offline of the concentrator on the timeliness of the data, and reduce the workload and time cost of the maintenance personnel.

[0055] It should be noted that when the system time of the concentrator is different from the system time of the monitoring platform, it is easy for the monitoring platform to be unable to receive the data packets sent by the concentrator. When the terminal address code of the concentrator is inconsistent with the terminal address code in the monitoring platform, it is also easy for the monitoring platform to be unable to receive the data packets sent by the concentrator.

[0056] The troubleshooting unit analyzes the reasons why the concentrator fails to upload data packets. The analysis process is as follows:

[0057] When a troubleshooting signal is identified, the network address of the monitoring platform is obtained from the local database, and a number of data packets are sent to the network address of the monitoring platform through a network detection command to obtain statistical information of the network detection command. The data packet loss rate DS and network delay MS are extracted from the statistical information of the network detection command, and the communication anomaly index TX of the concentrator is calculated by the formula TX=DS×b1+MS×b2, where b1 is the preset loss rate weight factor and b2 is the preset network delay weight factor;

[0058] The communication anomaly index of the concentrator is compared with the preset communication anomaly index threshold. When the communication anomaly index of the concentrator is greater than the preset communication anomaly index threshold, it means that there is a problem with the communication module of the concentrator, and a communication fault signal is generated. When the communication anomaly index of the concentrator is less than the preset communication anomaly index threshold, the number of times the collection abnormality signal is identified is counted and compared with the preset threshold of the number of abnormal signals within the collection time. When the number of times the collection abnormality signal is identified is greater than the threshold of the number of abnormal signals within the preset collection time, it means that the communication module of the concentrator is normal, and it is judged that the system of the concentrator has a fault, then a system fault signal is generated, and the communication fault signal or system abnormality is sent to the light display module.

[0059] Furthermore, if the concentrator is unable to upload data packets to the monitoring platform, targeted troubleshooting allows on-site maintenance personnel to immediately identify the fault and begin maintenance work, thereby improving the efficiency and accuracy of concentrator fault handling and the maintenance efficiency of maintenance personnel.

[0060] The monitoring platform receives the data packets sent by the concentrator and analyzes the operating status of the concentrator to be tested. The analysis process is as follows:

[0061] Receive the data packet sent by the concentrator and send it to the cloud database for storage, parse the data packet sent by the concentrator to obtain the number of the online concentrator and record it as the online number, obtain the concentrator list from the cloud database, where the concentrator list contains the numbers of all concentrators, match the number of the online concentrator with the concentrator list, and when a certain online number exists in the concentrator list, remove the online number from the concentrator list, so as to remove all online numbers from the concentrator list and obtain the concentrator list to be verified;

[0062] The concentrators in the list of concentrators to be tested are recorded as concentrators to be tested. According to the number of the concentrator to be tested, several collection signals are sent to the corresponding concentrators and wait for receiving new data packets. If the monitoring platform receives a new data packet, the new data packet is parsed to obtain the number of the concentrator, and the number of the concentrator is matched with the list of concentrators to be tested. If the number of the concentrator matches the list of concentrators to be tested successfully, the operating status of the concentrator to be tested is determined to be an intermittent offline state. If the number of the concentrator fails to match the list of concentrators to be tested, the operating status of the concentrator to be tested is determined to be a continuous offline state, and a prompt signal is generated according to the operating status of the concentrator to be tested.

[0063] When the running state of the concentrator is an indirect offline state, the system log of the concentrator is obtained, and the event level in the system log of the concentrator is identified as an error class and an offline keyword, so as to count the number of times the concentrator is offline, and the offline frequency of the concentrator is calculated according to the preset statistical time and the number of times the concentrator is offline, and the offline frequency of the concentrator is compared with the preset offline frequency threshold. If the offline frequency of the concentrator is greater than the preset offline frequency threshold, a frequent offline signal is generated;

[0064] When the running status of the concentrator is continuously offline, the area where the concentrator is located is queried from the cloud database according to the concentrator number to obtain the power supply and network conditions of the area where the concentrator is located. If the power supply and network conditions of the area where the concentrator is located are normal, a continuous offline signal is generated;

[0065] Corresponding maintenance information is generated according to the frequent offline signal or the continuous offline signal, and the maintenance information is sent to the corresponding intelligent terminal.

[0066] The present invention can help the administrator better understand the fault condition of the concentrator by determining whether the offline state of the concentrator is an indirect offline state or a continuous offline state, thereby reducing unnecessary maintenance operations and helping maintenance personnel to better handle the offline state of the concentrator. At the same time, it saves the time and energy of maintenance personnel and ensures the pertinence and effectiveness of maintenance work.

[0067] The light display module receives the communication fault signal and the system fault signal, and displays the communication fault signal and the system fault signal in the form of an LED prompt light accordingly.

[0068] The local database stores the preset network configuration information of the concentrator and the preset terminal address code of the concentrator.

[0069] The cloud database stores the concentrator list and the data packets sent by the concentrator.

[0070] See also Figure 2 As shown, another aspect of the present invention provides a risk control management method for a concentrator, comprising the following steps:

[0071] The downlink device is collected at a preset collection frequency to obtain downlink data, and the downlink data is verified to determine whether the collection state of the concentrator is normal or abnormal, thereby generating a normal collection signal or an abnormal collection signal;

[0072] When an abnormal signal is detected, the concentrator is self-calibrated. When a normal signal is detected, the data of the downstream devices is aggregated and processed to form a data packet, which is sent to the monitoring platform. Based on the system log in the concentrator, the sending status of the corresponding data packet of the concentrator is determined as sent or not sent, thereby generating a troubleshooting signal or a regular signal.

[0073] When the troubleshooting signal is identified, the network of the concentrator is analyzed or the number of occurrences of the collected abnormal signal is counted, thereby generating a communication fault signal or a network fault signal and displaying it in the form of an LED light display;

[0074] Receive the data packet sent by the concentrator and parse it to obtain the number of the online concentrator, obtain the list of concentrators to be tested based on the number of the online concentrator, send a collection signal to the concentrator according to the list of concentrators to be tested and wait for receiving new data packets, so as to determine the operating status of the concentrator to be tested as an indirect offline state or a continuous offline state, generate corresponding prompt information based on the operating status of the concentrator to be tested and send it to the corresponding smart terminal.

[0075] The above contents are merely examples and explanations of the structure of the present invention. The technical personnel in the relevant technical field may make various modifications or additions to the specific embodiments described or replace them in a similar manner. As long as they do not deviate from the structure of the invention or exceed the scope defined by the claims, they should all fall within the protection scope of the present invention.

Claims

1. A risk control management system for a concentrator, including a light display module, a local database and a cloud database, characterized in that: Includes concentrator self-check module, troubleshooting module and monitoring platform; The concentrator self-check module is used to analyze the collection state of the concentrator, collect downlink data from the downlink device according to the preset collection frequency, verify the downlink data, and if there is a null value in the downlink data, mark the downlink data as abnormal data and count the number of abnormal data, count the number corresponding to the downlink data, and obtain the collection abnormality index of the concentrator through analysis, and determine the collection state of the concentrator as a normal state or an abnormal state based on the collection abnormality index, and further analyze the concentrator whose collection state is a normal state to obtain the sending state of the corresponding data packet of the concentrator as a sent state or an unsent state; The troubleshooting module includes a self-correction unit and a troubleshooting detection unit. The self-correction unit is used to analyze the reason why the concentrator collects abnormal data of the downlink device. When an abnormal collection signal is identified, the number of occurrences of the abnormal collection signal is counted. When the abnormal collection signal is identified, the system time and terminal address code of the concentrator are covered or corrected. After the covering or correction is completed, a collection signal is generated and sent to the concentrator self-check module; the troubleshooting detection unit is used to analyze the reason why the concentrator fails to upload a data packet. When a troubleshooting signal is identified, the number of occurrences of the collection signal is counted, and further analysis of the concentrator is performed to generate a communication fault signal or a system fault signal; The monitoring platform is used to receive data packets sent by the concentrator, parse the data packets uploaded by the concentrator to obtain the number of the online concentrator, obtain the concentrator list from the cloud database, match the number of the online concentrator with the concentrator list to obtain a list of concentrators to be tested, record the concentrators in the list of concentrators to be tested as concentrators to be tested, analyze the operating status of the concentrators to be tested, send several acquisition signals to the concentrators to be tested and wait for receiving new data packets, so as to determine the status of the concentrators to be tested as an indirect offline state or a continuous offline state; The light display module is used to receive communication fault signals and system fault signals, and to display correspondingly in the form of LED prompt lights according to the communication fault signals and the system fault signals.

2. The risk control management system for a concentrator according to claim 1, characterized in that: The collection status of the concentrator is analyzed, and the analysis process is as follows: The concentrator collects downlink data from the downlink device according to the preset collection frequency or when the collection signal is identified, counts the number of downlink data collected by the concentrator, obtains the value of the sub-data corresponding to the downlink data and compares the null value. When any sub-data in the downlink data is a null value, the downlink data is marked as null data, and the number of null data is counted. When all the sub-data in the downlink data are not null values, the downlink data is marked as valid data, and the number of valid data is counted. The collection anomaly index of the concentrator is obtained by analysis, and the collection anomaly index of the concentrator is compared with the preset collection anomaly index threshold. If the anomaly index of the concentrator is greater than the preset collection anomaly index threshold, the collection state of the concentrator is determined to be abnormal, and a collection anomaly signal is generated, and the troubleshooting signal is sent to the troubleshooting module. Otherwise, the collection state of the concentrator is determined to be normal, and a collection normal signal is generated. The concentrator whose collection status is normal is analyzed to obtain the sending status of the corresponding data packet of the concentrator as sent status or unsent status.

3. The risk control management system for a concentrator according to claim 1, characterized in that: The concentrator whose collection status is normal is analyzed, and the analysis process is as follows: Summarize and process the valid data to form a data packet, send the data packet to the monitoring platform, collect the system time of the current concentrator and record it as the capture time, obtain the system log of the concentrator, select the system log after the capture time and filter the system log with the event level of error according to the event level keyword; The event description corresponding to the system log of the error class is matched according to the preset data packet information keyword. When the preset data packet information keyword matches the event description corresponding to the system log of the error class successfully, the data packet sending status of the concentrator is determined to be an upload failure status, and a troubleshooting signal is generated and sent to the troubleshooting module. When the preset data packet information keyword does not match the event description corresponding to the system log of the error class successfully, the data packet sending status of the concentrator is determined to be an upload success status, and a normal signal is generated.

4. The risk control management system for a concentrator according to claim 1, characterized in that: The analysis concentrator collects the reasons for abnormalities in downlink device data. The analysis process is as follows: When an abnormal signal is detected, the GPRS signal strength of the concentrator is obtained, and the GPRS signal strength of the concentrator is compared with the set signal strength threshold. If the GPRS signal strength of the concentrator is less than the set signal strength threshold, a collection signal is generated and sent to the concentrator self-check module. Otherwise, the preset network configuration information corresponding to the concentrator is obtained from the local database. The preset network configuration information is compared with the network configuration information in the current concentrator one by one. If the comparison between the preset network configuration information and the network configuration information in the current concentrator fails, the network configuration information in the current concentrator is overwritten with the preset network configuration information. After the overwriting is completed, a collection signal is generated and sent to the concentrator self-test module. If the preset network configuration information is successfully compared with the network configuration information in the current concentrator, the terminal address code of the current concentrator is obtained, the preset terminal address code of the concentrator is obtained from the local database, and the terminal address code of the current concentrator is compared with the preset terminal address code. If the comparison between the terminal address code of the current concentrator and the preset terminal address code is successful, the terminal address code of the current concentrator is overwritten with the preset terminal address code. After the overwriting is completed, a collection signal is generated and sent to the concentrator self-test module. If the comparison between the terminal address code of the current concentrator and the preset terminal address code is successful, the system time in the monitoring platform is obtained, and the system time in the concentrator is calibrated based on the system time in the monitoring platform. After the calibration is completed, a collection signal is generated and sent to the concentrator self-test module.

5. The risk control management system for a concentrator according to claim 1, characterized in that: The reason why the concentrator fails to upload a data packet is analyzed as follows: When a troubleshooting signal is identified, the network address of the monitoring platform is obtained from the local database, and a number of data packets are sent to the network address of the monitoring platform through a network detection command to obtain the statistical information of the network detection command. The data packet loss rate and network delay are extracted from the statistical information of the network detection command, and the communication anomaly index of the concentrator is obtained by analysis; The communication anomaly index of the concentrator is compared with the preset communication anomaly index threshold. When the communication anomaly index of the concentrator is greater than the preset communication anomaly index threshold, a communication fault signal is generated. When the communication anomaly index of the concentrator is less than the preset communication anomaly index threshold, the number of times the collection anomaly signal is identified is counted and compared with the preset threshold of the number of abnormal signals within the collection time. When the number of times the collection anomaly signal is identified is greater than the threshold of the number of abnormal signals within the preset collection time, a system fault signal is generated, and the communication fault signal or system anomaly is sent to the light display module.

6. The risk control management system for a concentrator according to claim 1, characterized in that: The operating status of the concentrator to be tested is analyzed, and the analysis process is as follows: Receive the data packet sent by the concentrator and send it to the cloud database for storage, parse the data packet sent by the concentrator to obtain the number of the online concentrator and record it as the online number, obtain the concentrator list from the cloud database, match the number of the online concentrator with the concentrator list, and when a certain online number exists in the concentrator list, remove the online number from the concentrator list, so as to remove all online numbers from the concentrator list and obtain the concentrator list to be verified; The concentrators in the list of concentrators to be tested are recorded as concentrators to be tested. According to the number of the concentrator to be tested, several collection signals are sent to the corresponding concentrators and wait for receiving new data packets. If the monitoring platform receives a new data packet, the new data packet is parsed to obtain the number of the concentrator, and the number of the concentrator is matched with the list of concentrators to be tested. If the number of the concentrator matches the list of concentrators to be tested successfully, the operating status of the concentrator to be tested is determined to be an intermittent offline state. If the number of the concentrator fails to match the list of concentrators to be tested, the operating status of the concentrator to be tested is determined to be a continuous offline state, and a prompt signal is generated according to the operating status of the concentrator to be tested.

7. The risk control management system for a concentrator according to claim 6, characterized in that: The process of generating a prompt signal according to the operating status of the concentrator to be tested is as follows: When the running state of the concentrator is an indirect offline state, the system log of the concentrator is obtained, and the event level in the system log of the concentrator is identified as an error class and an offline keyword, so as to count the number of times the concentrator is offline, and the offline frequency of the concentrator is calculated according to the preset statistical time and the number of times the concentrator is offline, and the offline frequency of the concentrator is compared with the preset offline frequency threshold. If the offline frequency of the concentrator is greater than the preset offline frequency threshold, a frequent offline signal is generated; When the running status of the concentrator is continuously offline, the area where the concentrator is located is queried from the cloud database according to the concentrator number to obtain the power supply and network conditions of the area where the concentrator is located. If the power supply and network conditions of the area where the concentrator is located are normal, a continuous offline signal is generated; Corresponding maintenance information is generated according to the frequent offline signal or the continuous offline signal, and the maintenance information is sent to the corresponding intelligent terminal.

8. The risk control management system for a concentrator according to any one of claims 1 to 7, characterized in that: The management method of the system comprises the following steps: Q1. Collect the downlink data from the downlink device according to the preset collection frequency, verify the downlink data to determine whether the collection state of the concentrator is normal or abnormal, and generate a normal collection signal or an abnormal collection signal; Q2: When an abnormal signal is detected, the concentrator is self-calibrated. When a normal signal is detected, the data of the downstream device is aggregated and processed to form a data packet, which is sent to the monitoring platform. Based on the system log in the concentrator, the sending status of the corresponding data packet of the concentrator is determined as sent or not sent, thereby generating a troubleshooting signal or a regular signal. Q3. When the troubleshooting signal is identified, the network of the concentrator is analyzed or the number of times the abnormal signal is collected is counted, so as to generate a communication fault signal or a network fault signal and display it in the form of an LED light display; Q4. Receive the data packet sent by the concentrator and parse it to obtain the number of the online concentrator, obtain the list of concentrators to be tested based on the number of the online concentrator, send a collection signal to the concentrator according to the list of concentrators to be tested and wait for receiving new data packets, so as to determine the operating status of the concentrator to be tested as an indirect offline state or a continuous offline state, generate corresponding prompt information based on the operating status of the concentrator to be tested and send it to the corresponding smart terminal.

Images