An Internet of Things (IoT) data acquisition and monitoring management system
By acquiring, analyzing, and evaluating traffic, packet loss rate, and occupancy rate data of IoT communication paths, path-level differentiated monitoring resource allocation is achieved, solving the problem of unreasonable resource allocation in existing technologies and improving the timeliness of critical path monitoring and the reliability of abnormal switching.
Patent Information
- Application Number
- CN202611099348.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-23
- Publication Date
- 2026-11-17
AI Technical Summary
Existing IoT data collection and monitoring management methods are unable to allocate path-level differentiated monitoring resources based on differences in service carrying capacity and operational risks of different communication paths, resulting in insufficient collection frequency for critical paths or waste of resources for low-value paths.
The data acquisition module obtains traffic, packet loss rate, and occupancy data of the communication path; the importance analysis module assesses the importance of the path; the risk assessment module assesses the stability of the path and the reliability of the backup path; the policy projection module determines the monitoring period and anomaly threshold; and the anomaly switching module performs path anomaly switching, thereby realizing path-level differentiated monitoring.
It improves the rationality of resource allocation for IoT communication path monitoring, the timeliness of critical path anomaly detection, and the reliability of anomaly path switching, avoiding the underestimation of critical paths and the waste of resources on non-critical paths.
Smart Images

Figure CN123123376A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of industrial automation control technology, and more specifically to an Internet of Things (IoT) data acquisition and monitoring management system. Background Technology
[0002] With the widespread application of IoT technology in industrial production, building management, warehousing and logistics, energy metering, and environmental monitoring, various sensors, control terminals, and edge devices are constantly connecting to the network and generating operational data, significantly increasing the data transmission scale and the number of communication links in IoT systems. To ensure stable data transmission and continuous business operation between IoT devices, it is necessary to continuously monitor the communication paths, interface status, and data transmission in the network, enabling managers to promptly grasp the network operating status, data acquisition quality, and device communication status.
[0003] Current IoT data acquisition and monitoring management methods typically employ fixed acquisition cycles and fixed anomaly thresholds for unified monitoring of network interfaces or communication links. However, different communication paths within an IoT network exhibit significant differences in business importance, communication activity, operational stability, and substitutability. Applying the same monitoring strategy to all communication paths can easily lead to insufficient acquisition frequency and delayed anomaly detection for critical communication paths, while low-value or low-risk communication paths consume excessive acquisition and computing resources. Summary of the Invention
[0004] To address the technical problem that existing IoT data acquisition and monitoring management methods struggle to allocate path-level differentiated monitoring resources based on differences in service carrying capacity and operational risks across different communication paths, this invention aims to provide an IoT data acquisition and monitoring management system. The specific technical solution adopted is as follows:
[0005] This invention provides an Internet of Things (IoT) data acquisition and monitoring management system, which includes the following modules: Data acquisition module: used to acquire the communication traffic sequence, packet loss rate sequence, and occupancy rate sequence of the communication path and its interfaces; the communication path includes the primary path and the backup path; Importance Analysis Module: Used to determine the importance of a communication path based on the total communication volume, communication activity, and sudden sensitivity of the communication traffic sequence of interfaces in the communication path; Risk assessment module: Used to determine the health of interfaces based on packet loss rate and occupancy rate sequences; determine the path stability of each communication path based on the distribution of health of all interfaces in the communication path; determine the independent reliability score of backup paths based on the interface overlap between the primary and backup paths and the health of backup path interfaces; determine the redundancy reliability based on the independent reliability scores of all backup paths; and determine the monitoring urgency by combining the declining trend of health of interfaces in the primary path, the path stability of the primary path, and the path importance. The strategy projection module is used to determine the path-level monitoring cycle and path-level anomaly threshold based on the urgency of monitoring, and to project the path-level monitoring cycle onto the interfaces through which the communication path passes to obtain the interface-level telemetry cycle. Anomaly switching module: Used to collect interface data according to the interface-level telemetry cycle, determine the anomaly of the communication path according to the path-level anomaly threshold, and determine the recommended backup path according to the independent reliability score of the backup path when the communication path is abnormal.
[0006] Furthermore, determining the path importance of a communication path based on the total communication volume, communication activity, and sudden sensitivity of the communication traffic sequence of interfaces in the communication path includes: For any interface in any communication path, within the preset learning time window of the communication traffic sequence of that interface, the normalized result of the sum of the communication traffic values within all sampling times is recorded as the total communication volume of that interface. The proportion of sampling times with non-zero communication traffic values in all sampling times is recorded as the communication activity of that interface. The mean of all communication traffic values is obtained, and the normalized result of the ratio of the maximum value of the communication traffic value to the mean is recorded as the burst sensitivity of that interface. The path importance of the communication path is determined based on the total communication volume, communication activity, and burst sensitivity of the interface.
[0007] Furthermore, determining the path importance of the communication path based on the total communication volume, communication activity, and burst sensitivity includes: For any interface in any communication path, the product of the total communication volume and the communication activity of that interface is recorded as the stable communication evidence of that interface. By fusing the stable communication evidence and the burst sensitivity of the interface, a local importance index of the interface is obtained; The maximum value of the local importance index of all interfaces in the communication path is denoted as the path importance of the communication path.
[0008] Furthermore, determining the health of the interface based on the packet loss rate sequence and occupancy rate sequence includes: For any interface in any communication path, within a preset learning time window of the packet loss rate sequence of that interface, obtain the average value of the packet loss rate at all sampling times; Within the preset learning time window of the occupancy rate sequence of this interface, obtain the mean value of the occupancy rate value at all sampling times; The packet loss health sub-value is determined based on the ratio of the average packet loss rate value to the preset upper limit of the packet loss error rate. The queue health sub-value is determined based on the ratio of the average occupancy rate value to the preset occupancy rate upper limit; The minimum value between the packet loss health sub-value and the queue health sub-value is taken as the health of the interface.
[0009] Furthermore, determining the path stability of each communication path based on the distribution of health scores of all interfaces in the communication path includes: For any communication path, the minimum health value of all interfaces in that communication path is denoted as the path stability of that communication path.
[0010] Furthermore, the determination of the independent reliability score of the backup path based on the interface overlap between the primary path and the backup path, and the health of the backup path interface, includes: For any backup path, obtain the number of all interfaces contained in the primary path and the backup path, obtain the ratio of the number of interfaces shared by the primary path and the backup path to the total number of interfaces contained in the primary path and the backup path, and record the inverse proportional result of the ratio as the fault domain independence of the backup path relative to the primary path. Obtain the minimum health score of all interfaces in the backup path, and multiply the minimum health score by the fault domain independence score to obtain the independent reliability score of the backup path.
[0011] Furthermore, determining redundancy reliability based on the independent reliability scores of all backup paths includes: Based on the independent reliability score of the backup paths, determine the missing value of the redundancy contribution of each backup path relative to the primary path; Multiply the redundancy contribution missing values of all backup paths relative to the primary path to obtain the overall redundancy missing degree of the primary path. The difference between 1 and the overall redundancy level is denoted as the redundancy reliability.
[0012] Furthermore, the method for obtaining the monitoring urgency level is as follows: The path risk of the primary path is determined based on the path stability, redundancy reliability, and declining health trend of the primary path; wherein, the path risk increases when the path stability, redundancy reliability, or declining health trend of the primary path decreases. The path risk is gating based on the path importance of the primary path to obtain the monitoring urgency level; wherein, when the path importance of the primary path decreases, the impact of the path risk on the monitoring urgency level is reduced.
[0013] Furthermore, the step of determining the path-level monitoring period and path-level anomaly threshold based on the monitoring urgency, and projecting the path-level monitoring period onto the interfaces traversed by the communication path to obtain the interface-level telemetry period includes: The path-level target monitoring cycle and path-level anomaly threshold of the primary path are determined based on the monitoring urgency. The higher the monitoring urgency, the shorter the path-level target monitoring cycle and the more stringent the path-level anomaly threshold. Based on the set of interfaces traversed by the primary path, the path-level target monitoring period is projected onto the corresponding interface. When the same interface is traversed by multiple primary paths, the shortest period among the path-level target monitoring periods corresponding to the multiple primary paths is determined as the interface-level telemetry period of that interface.
[0014] Furthermore, the step of collecting interface data according to the interface-level telemetry cycle, determining communication path anomalies based on the path-level anomaly threshold, and determining a recommended backup path based on the independent reliability score of the backup path when the communication path is abnormal includes: Receive communication traffic, packet loss rate, and occupancy rate values of the switch interface according to the interface-level telemetry cycle; Based on the set of interfaces traversed by the primary path, the maximum packet loss rate of each interface in the set is used as the current path packet loss metric, and the maximum occupancy rate of each interface in the set is used as the current path congestion metric. When the packet loss index of the current path is greater than the path-level anomaly threshold of the primary path, or when the congestion index of the current path is greater than the preset queue threshold for a preset number of consecutive times, the primary path is determined to be abnormal. After the primary path fails, the switching priority is determined based on the independent reliability score of the backup path, and the backup path with the highest switching priority is selected as the recommended backup path.
[0015] The present invention has the following beneficial effects: To address the technical problem of existing IoT data acquisition and monitoring management methods failing to allocate path-level differentiated monitoring resources based on differences in service load and operational risk across different communication paths, this invention first determines the path importance of a communication path based on the total communication volume, communication activity, and sudden sensitivity of the communication traffic sequence of interfaces within the communication path. This allows for the identification of the service load value of a communication path from both stable communication load and sudden communication demand perspectives, avoiding the underestimation of critical path importance due to relying solely on a single traffic indicator. Secondly, the path stability of each communication path is determined based on the health distribution of all interfaces within the path, enabling the identification of the transmission bottleneck of the entire communication path using the interface with the worst-performing state. The overlap of interfaces between the primary and backup paths, along with the health of backup path interfaces, determines the independent reliability score of the backup path. This simultaneously evaluates the backup path's own transmission status and its independence from the primary path's fault domain, preventing paths highly overlapping with the primary path or with poor status from being mistakenly identified as reliable backup paths. Based on the independent reliability scores of all backup paths, redundancy reliability is determined. Combining this with the declining trend of interface health in the primary path, the path stability of the primary path, and its importance, the monitoring urgency is determined. This comprehensively reflects the current transmission risk of the primary path, the redundancy capability of the backup path, and the importance of the service, prioritizing monitoring resources for important communication paths with operational risks. Thus, by determining the interface-level telemetry cycle and path-level anomaly threshold based on monitoring urgency, path anomaly switching control is implemented, improving the rationality of IoT communication path monitoring resource allocation, the timeliness of critical communication path anomaly detection, and the reliability of anomaly path switching recommendations. Attached Figure Description
[0016] To more clearly illustrate the technical solutions and advantages in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0017] Figure 1 This is a flowchart of a module of an Internet of Things (IoT) data acquisition and monitoring management system provided in one embodiment of the present invention. Detailed Implementation
[0018] To further illustrate the technical means and effects adopted by the present invention to achieve its intended purpose, the following, in conjunction with the accompanying drawings and preferred embodiments, details the specific implementation, structure, features, and effects of an Internet of Things (IoT) data acquisition and monitoring management system proposed according to the present invention. In the following description, different "one embodiment" or "another embodiment" do not necessarily refer to the same embodiment. Furthermore, specific features, structures, or characteristics in one or more embodiments can be combined in any suitable form.
[0019] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains.
[0020] The specific solution of the Internet of Things (IoT) data acquisition and monitoring management system provided by the present invention will be described in detail below with reference to the accompanying drawings.
[0021] An embodiment of an Internet of Things (IoT) data acquisition and monitoring management system: Please see Figure 1 This illustrates a module flowchart of an IoT data acquisition and monitoring management system according to an embodiment of the present invention. Figure 1 As shown, the system includes the following modules: Module 101: Data Acquisition Module: Used to acquire the communication traffic sequence, packet loss rate sequence, and occupancy rate sequence of the communication path and its interfaces.
[0022] The purpose of this solution is to collect operational data such as communication traffic, packet loss rate, and occupancy rate of interfaces in the IoT communication path, and to perform path-level status analysis based on the interface composition relationship between the primary and backup paths. This addresses the problem that traditional fixed-period, fixed-threshold monitoring methods struggle to distinguish the importance and operational risks of different communication paths, leading to untimely monitoring of critical paths and wasted resources for collecting data on non-critical paths. Therefore, the solution first involves continuously collecting communication traffic, packet loss, and occupancy status of the interfaces traversed by the primary and backup paths in the IoT communication network.
[0023] Specifically, the system obtains interface statistics through the flow telemetry interface of the switch, and determines the identifiable communication path in the process of IoT data transmission based on the communication relationship between IoT nodes, the forwarding relationship of the switch interface, and the path topology relationship. Among them, the communication path for business data transmission between the current carrying nodes is used as the primary path, and the communication path that is topologically reachable and can be used as a substitute for the primary path is used as the backup path. The system sets an initial sampling period and continuously receives statistical data from the switch interface according to the initial sampling period. A preset learning time window is established, ending with the last sampling time. The preset learning time window is 1 hour, and the initial sampling period is 5 seconds. This embodiment will be described using this as an example. For any interface in any communication path, the system acquires the communication traffic value, packet loss rate value and occupancy rate value of the interface at each sampling time, and forms the communication traffic sequence, packet loss rate sequence and occupancy rate sequence of the interface according to the order of sampling time.
[0024] The communication traffic value characterizes the data transmission scale carried by the interface within the corresponding sampling period. When the data reported by the switch is a cumulative traffic count, the communication traffic value within that sampling period is obtained based on the difference between the cumulative traffic counts between adjacent sampling times. The packet loss rate characterizes the data transmission reliability of the interface within the corresponding sampling period and can be determined based on the number of dropped packets, the number of erroneous packets, and the total number of data packets within that sampling period. The occupancy rate characterizes the queue occupancy of the interface within the corresponding sampling period and can be determined based on the ratio between the current queue occupancy and the queue capacity.
[0025] Module 102: Importance Analysis Module: Used to determine the importance of a communication path based on the total communication volume, communication activity, and sudden sensitivity of the communication traffic sequence of the interfaces in the communication path.
[0026] It should be noted that in IoT data acquisition scenarios, the service value carried by different communication paths is not the same. Some paths bear the core sensor data upload for a long time, and their communication traffic is stable and continuous; some paths, although their traffic is usually small, may experience short-term bursts of traffic during device alarms, sudden status changes, or centralized reporting. Judging the importance of a path solely based on the traffic volume at a single moment may underestimate the importance of paths with sudden alarms; judging solely based on the number of communications may overlook paths with high-load production data. Therefore, this embodiment identifies the importance of communication paths from three perspectives: total communication volume, communication activity, and sudden sensitive situations, so that the importance of a path can reflect both long-term stable service load and short-term bursts of service demand.
[0027] Specifically, for any interface in any communication path, within a preset learning time window of the communication traffic sequence of that interface, the linearly normalized result of the sum of communication traffic values within all sampling moments is recorded as the total communication volume of that interface. The object of linear normalization is the sum of communication traffic values within all sampling moments in each preset learning time window during the historical monitoring process. The proportion of sampling moments with non-zero communication traffic values in all sampling moments is recorded as the communication activity of that interface. The mean of all communication traffic values is obtained, and the normalized result of the ratio of the maximum value of the communication traffic value to the mean is recorded as the burst sensitivity of that interface.
[0028] It should be noted that total traffic volume characterizes the overall scale of business data carried by the interface within a preset learning time window, communication activity characterizes the duration of interface communication behavior over time, and burst sensitivity characterizes whether the interface experiences short-term concentrated reporting or alarm-type traffic. For IoT systems, continuously high traffic paths typically correspond to stable services such as production monitoring and equipment status uploading, while burst sensitive paths may correspond to abnormal alarms, periodic centralized data collection, or batch synchronization services. Therefore, both can make the corresponding communication paths highly valuable for monitoring.
[0029] It should be further explained that judging path importance solely based on total traffic volume or communication activity is insufficient. If the total traffic volume of an interface is high but concentrated only at a few sampling times, it may be sporadic transmission; if the communication activity is high but the data volume each time is extremely small, it may simply be low-value communication. Therefore, this embodiment combines total traffic volume and communication activity to obtain evidence of stable communication, which is used to characterize whether the interface simultaneously possesses the characteristics of large data volume and continuous communication. At the same time, burst sensitivity is used as another type of importance evidence to avoid underestimating low-frequency but highly bursty alarm-type paths.
[0030] Furthermore, for any interface in any communication path, the product of the total communication volume and the communication activity of that interface is recorded as the stable communication evidence of that interface. By fusing the stable communication evidence and the burst sensitivity of the interface, a local importance index of the interface is obtained; The maximum value of the local importance index of all interfaces in the communication path is denoted as the path importance of the communication path.
[0031] As an example, the local importance index of this interface is calculated as follows:
[0032] In the formula, This is the local importance index of the interface; This serves as evidence of stable communication for the interface; This refers to the burst sensitivity of the interface.
[0033] It should be noted that when an interface possesses both strong evidence of stable communication and strong sensitivity to sudden events, its local importance index is high; even when an interface possesses only one of these characteristics, it can still achieve a corresponding increase in importance. The maximum local importance index of all interfaces in the communication path is used as the path importance because any critical interface on the communication path carrying high-value or sudden business events can determine the monitoring priority of the entire path.
[0034] Module 103: Risk Assessment Module: Used to determine the health of interfaces based on packet loss rate and occupancy rate sequences; determine the path stability of each communication path based on the distribution of health of all interfaces in the communication path; determine the independent reliability score of backup paths based on the interface overlap between the primary and backup paths and the health of backup path interfaces; determine the redundancy reliability based on the independent reliability scores of all backup paths; and determine the monitoring urgency by combining the declining trend of health of interfaces in the primary path, the path stability of the primary path, and the path importance.
[0035] It should be noted that whether a communication path needs increased monitoring intensity depends not only on the importance of the path, but also on its current stability, the existence of alternative paths, and whether the path's health status is declining. For IoT communication paths carried by switches, the interface packet loss rate reflects data transmission reliability, and the interface occupancy rate reflects queue congestion pressure; both together determine the data transmission quality of the interface in a connected state.
[0036] Specifically, for any interface in any communication path, the mean value of the packet loss rate is obtained within a preset learning time window of the packet loss rate sequence of that interface at all sampling times. Within the preset learning time window of the occupancy rate sequence of this interface, obtain the mean value of the occupancy rate value at all sampling times; The packet loss health sub-value is determined based on the ratio of the average packet loss rate value to the preset upper limit of the packet loss error rate; wherein, the preset upper limit of the packet loss error rate is 5%, and this embodiment will be described using this as an example; The queue health sub-value is determined based on the ratio of the average occupancy rate value to the preset occupancy rate limit; wherein, the preset occupancy rate limit is 80%, and this embodiment will use this as an example for description; The minimum value between the packet loss health sub-value and the queue health sub-value is taken as the health of the interface.
[0037] It should be noted that the packet loss health sub-value reflects the health of the interface in terms of data transmission reliability, while the queue health sub-value reflects the health of the interface in terms of congestion pressure. The minimum of the two is used as the interface's health score because both abnormal packet loss rate and abnormal occupancy rate can independently lead to a decline in interface transmission quality.
[0038] Furthermore, for any communication path, the minimum health value of all interfaces in that communication path is denoted as the path stability of that communication path.
[0039] It should be noted that higher path stability indicates that all interfaces in the communication path maintain a good transmission state; lower path stability indicates that at least one interface in the communication path is in a relatively unstable state. Since path data needs to pass through each interface in its interface set sequentially, the minimum health score can directly reflect the state of the interface most likely to limit the overall transmission quality in the path.
[0040] It should be further noted that if the backup path shares many interfaces with the primary path, the backup path may also be affected by the same interfaces when the primary path experiences interface congestion or anomalies, thus failing to provide true redundancy. Therefore, this embodiment determines the fault domain independence based on the interface overlap between the primary and backup paths to evaluate the degree of independence of the backup path relative to the primary path.
[0041] Specifically, for any backup path, obtain the number of interfaces contained in the primary path and the backup path, that is, obtain the union of the sets of interfaces traversed by the primary path and the backup path, obtain the ratio of the number of interfaces shared by the primary path and the backup path to the total number of interfaces contained in the primary path and the backup path, and record the inverse proportional result of this ratio as the fault domain independence of the backup path relative to the primary path. Obtain the minimum health score of all interfaces in the backup path, and multiply the minimum health score by the fault domain independence score to obtain the independent reliability score of the backup path.
[0042] As an example, the fault domain independence of the backup path relative to the primary path is calculated as follows:
[0043] In the formula, The fault domain independence of the backup path relative to the primary path; The ratio of the number of interfaces shared by the primary path and the backup path to the total number of interfaces contained in the primary path and the backup path.
[0044] It should be noted that in this calculation method, the more interfaces the primary path and the backup path share, the higher the interface overlap ratio, and the lower the fault domain independence of the backup path. Conversely, the fewer interfaces the primary and backup paths share, the less susceptible the backup path is to being affected by the primary path's interface failures, and the higher its fault domain independence. The independent reliability score reflects both the health status of the backup path's own interfaces and its independence relative to the primary path. If the health status of a backup path's interfaces is low, even if it has little overlap with the primary path's interfaces, it should not be considered a high-priority backup path. If the health status of a backup path's interfaces is high but it highly overlaps with the primary path's interfaces, it may also be affected when the primary path is abnormal. Therefore, combining the minimum health status of interfaces in the backup path with the fault domain independence ensures that the backup path only receives a high score when it is healthy and relatively independent.
[0045] It should be further explained that a primary path may correspond to multiple backup paths, so the redundancy reliability needs to be evaluated by considering all backup paths.
[0046] Specifically, based on the independent reliability score of the backup paths, the redundancy contribution missing value of each backup path relative to the primary path is determined; Multiply the redundancy contribution missing values of all backup paths relative to the primary path to obtain the overall redundancy missing degree of the primary path. The difference between 1 and the overall redundancy level is denoted as the redundancy reliability.
[0047] As an example, redundancy reliability is calculated as follows:
[0048] In the formula, For redundancy reliability; This refers to the number of backup paths; For the first Independent reliability score for each backup path; For the first Missing values for the redundancy contribution of the backup path relative to the primary path; The overall redundancy or lack of the primary path.
[0049] It should be noted that, Indicates the first The extent to which backup paths fail to provide effective redundancy; the product of the missing redundancy contributions of all backup paths indicates the overall extent to which none of the backup paths can effectively replace the missing redundancy of the primary path. Redundancy reliability. The closer the value is to 1, the more likely it is to indicate that there is at least one or more independent and reliable backup paths; redundancy reliability. The closer the value is to 0, the less effective redundancy the primary path lacks. If the primary path fails, the system has limited failover capability. If there is no backup path for the primary path, the redundancy reliability is set to 0.
[0050] It should be further explained that path stability and redundancy reliability mainly reflect the current overall state. However, in actual monitoring, a path may show a continuous deterioration trend even if it has not yet crossed the anomaly threshold. For example, a gradually increasing interface queue and a gradually increasing packet loss rate may indicate subsequent anomalies. Therefore, this embodiment further extracts the health decline trend to identify the primary path that has not yet formed a significant anomaly but has already shown a deterioration direction.
[0051] Specifically, the path risk of the primary path is determined based on the path stability, redundancy reliability, and declining health trend of the primary path; wherein, the path risk increases when the path stability of the primary path decreases, the redundancy reliability decreases, or the declining health trend intensifies.
[0052] As an example, the path risk of the primary path is calculated as follows: A sliding window with a length of 6 sampling moments is established within a preset learning time window. The sliding window slides from left to right with a step size of 1. The average health of each interface at all sampling moments within the sliding window is calculated during each sliding. For any interface, based on the average health value and the sliding order of each sliding within the preset learning time window, a linear fit is performed on the average health value, and the fitting slope in the linear fit result is recorded as the health change slope of the interface. The negative number of the slope of health change is linearly normalized to the maximum value of 0 to obtain the sub-index of the health decline trend of the interface; wherein, the object of linear normalization is the negative number of the slope of health change of all interfaces in each preset learning time window during the historical monitoring process and the maximum value of 0. The maximum value of the health decline trend sub-indices of all interfaces in the primary path is recorded as the health decline index of the primary path.
[0053] It should be noted that when the interface health level continuously decreases within the preset learning time window, the average health level across multiple slides decreases overall with the slide sequence, the slope of the health level change is negative and the absolute value of the negative value increases, causing the health decline trend sub-index to increase accordingly. Therefore, the health decline index represents the overall downward trend of interface health level in the primary path.
[0054] The path risk of the primary path is calculated as follows:
[0055] In the formula, Path risks associated with the primary path; Path stability of the primary path; For redundancy reliability; The health decline index of the primary pathway.
[0056] It should be noted that in this formula, This indicates the level of security support provided by the primary path. When the primary path is stable... High, redundant reliability High and declining health index At lower levels, the level of security support is higher, and path risk is lower. Lower; when , If any one of them decreases, or As the elevation increases, the level of safety support decreases, and path risk increases. The corresponding increase.
[0057] It's important to note that high path risk does not necessarily mean the need for the highest monitoring resources. For low-value, low-business-impact communication paths, even if their risk is high, they should not occupy the same high-frequency telemetry resources as core production paths and alarm paths. Therefore, this embodiment uses path importance to gate path risk, ensuring that the monitoring urgency level increases primarily when the path is important and carries risk. This allows the limited telemetry capabilities of switches and server processing power to be prioritized for critical communication paths. Simultaneously, the gating process retains the fundamental role of path risk in determining monitoring urgency, preventing the complete shielding of high-risk paths when their importance is low.
[0058] Specifically, the path risk is gating based on the importance of the primary path to obtain the monitoring urgency level; wherein, when the importance of the primary path decreases, the impact of the path risk on the monitoring urgency level is reduced.
[0059] As an example, the path risk of the primary path is gating with a lower bound to obtain the monitoring urgency level, calculated as follows:
[0060] In the formula, The urgency level of monitoring the primary path; Path risks associated with the primary path; The importance of the primary path; To preset the basic risk retention coefficient, and In this embodiment, the preset basic risk retention coefficient is 0.5, and this embodiment will be described using this as an example.
[0061] It should be noted that a higher monitoring urgency level indicates that the primary path has both high business importance and high operational risk, and should be monitored with shorter cycles and stricter anomaly thresholds. Conversely, a lower monitoring urgency level indicates that the primary path is less important or less risky, and the data collection frequency can be appropriately reduced and the anomaly judgment threshold relaxed to reduce unnecessary telemetry data volume and alarm pressure. When the primary path has high risk but low importance, the monitoring urgency level still increases with the path risk, thus preventing low-importance primary paths from being excessively weakened in their risk impact and thus requiring a long-term low-intensity monitoring strategy.
[0062] Module 104: Strategy Projection Module: Used to determine the path-level monitoring cycle and path-level anomaly threshold based on the monitoring urgency, and project the path-level monitoring cycle onto the interfaces traversed by the communication path to obtain the interface-level telemetry cycle.
[0063] It should be noted that the monitoring urgency level is a path-level evaluation result, but switch flow telemetry usually uses interfaces as the basic collection object, making it difficult to directly establish a collection cycle independently for each communication path. Therefore, this embodiment first determines the path-level target monitoring cycle and path-level anomaly threshold based on the monitoring urgency level of the primary path, and then projects the path-level target monitoring cycle onto the set of interfaces traversed by the path, so that the path-level monitoring strategy can be transformed into an interface-level telemetry cycle that the switch can execute.
[0064] Specifically, the path-level target monitoring cycle and path-level anomaly threshold of the primary path are determined according to the monitoring urgency. The higher the monitoring urgency, the shorter the path-level target monitoring cycle and the more stringent the path-level anomaly threshold. Based on the set of interfaces traversed by the primary path, the path-level target monitoring period is projected onto the corresponding interface. When the same interface is traversed by multiple primary paths, the shortest period among the path-level target monitoring periods corresponding to the multiple primary paths is determined as the interface-level telemetry period of that interface.
[0065] As an example, the calculation method for the path-level target monitoring cycle and path-level anomaly threshold of the primary path is as follows:
[0066] In the formula, The path-level target monitoring cycle for the primary path; The maximum monitoring period is preset. To preset the shortest monitoring cycle; To monitor the urgency level; the preset maximum monitoring period is 20 seconds, and the preset minimum monitoring period is 1 second. This embodiment will be described using this as an example.
[0067] In the formula, This is the path-level anomaly threshold; The minimum threshold for preset abnormalities; The preset maximum threshold for abnormalities; To monitor the urgency level; wherein, the preset minimum threshold for anomalies is 0.5%, and the preset maximum threshold for anomalies is 5%, this embodiment will be described using this as an example.
[0068] It should be noted that in this mapping relationship, a higher monitoring urgency indicates that the primary path needs to be monitored more promptly, thus requiring a shorter path-level target monitoring cycle. Simultaneously, a stricter path-level anomaly threshold allows the system to identify abnormal fluctuations on critical paths earlier. Conversely, a lower monitoring urgency results in a longer path-level target monitoring cycle and a more lenient path-level anomaly threshold, thereby reducing the consumption of telemetry and server computing resources by low-priority paths. When multiple primary paths share the same interface, this interface only needs to collect basic telemetry data once to provide data for multiple paths. The shortest monitoring cycle among the path-level targets of the multiple primary paths passing through this interface is determined as the interface-level telemetry cycle, ensuring that the interface meets the monitoring requirements of the most stringent paths.
[0069] Module 105: Anomaly Switching Module: Used to collect interface data according to the interface-level telemetry cycle, determine the anomaly of the communication path according to the path-level anomaly threshold, and determine the recommended backup path based on the independent reliability score of the backup path when the communication path is abnormal.
[0070] It should be noted that after obtaining the interface-level telemetry period and path-level anomaly threshold, whether the communication path is abnormal still needs to be determined in real time based on interface data during continuous data collection. Since the data transmission of the primary path depends on each interface it passes through, high packet loss or high queue occupancy at any interface may lead to a deterioration in the transmission quality of the entire path. Therefore, this embodiment collects interface data according to the interface-level telemetry period and reconstructs the path-level packet loss index and path-level congestion index on the server side based on the set of interfaces traversed by the primary path.
[0071] Specifically, the communication traffic value, packet loss rate value, and occupancy rate value of the switch interface are received according to the interface-level telemetry cycle; Based on the set of interfaces traversed by the primary path, the maximum packet loss rate of each interface in the set is used as the current path packet loss metric, and the maximum occupancy rate of each interface in the set is used as the current path congestion metric.
[0072] It should be noted that the maximum packet loss rate of each interface in the interface set is used as the packet loss indicator for the current path because high packet loss at any interface in the path may lead to unreliable data transmission of business data on that path; the maximum occupancy rate of each interface in the interface set is used as the congestion indicator for the current path because excessive queue occupancy at any interface in the path may become a bottleneck for data transmission of the entire path.
[0073] Furthermore, when the current path packet loss index is greater than the path-level anomaly threshold of the primary path, or when the current path congestion index is greater than a preset queue threshold for a preset number of consecutive times, the primary path is determined to be abnormal; wherein, the preset number of times is 2 and the preset queue threshold is 80%, this embodiment is described using this as an example; After the primary path fails, the switching priority is determined based on the independent reliability score of the backup path, and the backup path with the highest switching priority is selected as the recommended backup path.
[0074] It should be noted that when the primary path is determined to be faulty, the backup path should be selected with a higher independent reliability score. A higher independent reliability score indicates a healthier interface for the backup path and a lower degree of overlap with the primary path's interface, making it more likely to take on replacement transmission tasks when the primary path fails. Therefore, identifying the backup path with the highest switching priority as the recommended backup path and using it to replace the faulty primary path for data transmission improves the reliability and recovery efficiency of backup path selection during fault handling.
[0075] It should be noted that the order of the above embodiments of the present invention is merely for descriptive purposes and does not represent the superiority or inferiority of the embodiments. The processes depicted in the accompanying drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0076] The various embodiments in this specification are described in a progressive manner. The same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on describing the differences from other embodiments.
Claims
1. An Internet of Things (IoT) data acquisition and monitoring management system, characterized in that, The system includes the following modules: Data acquisition module: used to acquire the communication traffic sequence, packet loss rate sequence, and occupancy rate sequence of the communication path and its interfaces; the communication path includes the primary path and the backup path; Importance Analysis Module: Used to determine the importance of a communication path based on the total communication volume, communication activity, and sudden sensitivity of the communication traffic sequence of interfaces in the communication path; Risk assessment module: used to determine the health of an interface based on its packet loss rate sequence and occupancy rate sequence; and to determine the path stability of each communication path based on the distribution of the health of all interfaces in the communication path. The independent reliability score of the backup path is determined based on the interface overlap between the primary path and the backup path, and the health of the backup path interfaces. The redundancy reliability is determined based on the independent reliability scores of all backup paths. The monitoring urgency is determined by combining the declining trend of the health of the interfaces in the primary path, the path stability of the primary path, and the path importance. The strategy projection module is used to determine the path-level monitoring cycle and path-level anomaly threshold based on the urgency of monitoring, and to project the path-level monitoring cycle onto the interfaces through which the communication path passes to obtain the interface-level telemetry cycle. Anomaly switching module: Used to collect interface data according to the interface-level telemetry cycle, determine the anomaly of the communication path according to the path-level anomaly threshold, and determine the recommended backup path according to the independent reliability score of the backup path when the communication path is abnormal.
2. The Internet of Things (IoT) data acquisition and monitoring management system according to claim 1, characterized in that, The determination of path importance based on the total communication volume, communication activity, and sudden sensitivity of the communication traffic sequence of interfaces in the communication path includes: For any interface in any communication path, within the preset learning time window of the communication traffic sequence of that interface, the normalized result of the sum of the communication traffic values within all sampling times is recorded as the total communication volume of that interface. The proportion of sampling times with non-zero communication traffic values in all sampling times is recorded as the communication activity of that interface. The mean of all communication traffic values is obtained, and the normalized result of the ratio of the maximum value of the communication traffic value to the mean is recorded as the burst sensitivity of that interface. The path importance of the communication path is determined based on the total communication volume, communication activity, and burst sensitivity of the interface.
3. The Internet of Things (IoT) data acquisition and monitoring management system according to claim 2, characterized in that, The determination of the path importance of the communication path based on the total communication volume, communication activity, and burst sensitivity includes: For any interface in any communication path, the product of the total communication volume and the communication activity of that interface is recorded as the stable communication evidence of that interface. By fusing the stable communication evidence and the burst sensitivity of the interface, a local importance index of the interface is obtained; The maximum value of the local importance index of all interfaces in the communication path is denoted as the path importance of the communication path.
4. The Internet of Things (IoT) data acquisition and monitoring management system according to claim 1, characterized in that, Determining the health of an interface based on its packet loss rate sequence and occupancy rate sequence includes: For any interface in any communication path, within a preset learning time window of the packet loss rate sequence of that interface, obtain the average value of the packet loss rate at all sampling times; Within the preset learning time window of the occupancy rate sequence of this interface, obtain the mean value of the occupancy rate value at all sampling times; The packet loss health sub-value is determined based on the ratio of the average packet loss rate value to the preset upper limit of the packet loss error rate. The queue health sub-value is determined based on the ratio of the average occupancy rate value to the preset occupancy rate upper limit; The minimum value between the packet loss health sub-value and the queue health sub-value is taken as the health of the interface.
5. The Internet of Things (IoT) data acquisition and monitoring management system according to claim 1, characterized in that, The determination of path stability for each communication path based on the distribution of health scores of all interfaces in the communication path includes: For any communication path, the minimum health value of all interfaces in that communication path is denoted as the path stability of that communication path.
6. The Internet of Things (IoT) data acquisition and monitoring management system according to claim 1, characterized in that, The process of determining the independent reliability score of the backup path based on the interface overlap between the primary path and the backup path, and the health status of the backup path interface, includes: For any backup path, obtain the number of all interfaces contained in the primary path and the backup path, obtain the ratio of the number of interfaces shared by the primary path and the backup path to the total number of interfaces contained in the primary path and the backup path, and record the inverse proportional result of the ratio as the fault domain independence of the backup path relative to the primary path. Obtain the minimum health score of all interfaces in the backup path, and multiply the minimum health score by the fault domain independence score to obtain the independent reliability score of the backup path.
7. The Internet of Things (IoT) data acquisition and monitoring management system according to claim 1, characterized in that, The determination of redundancy reliability based on the independent reliability scores of all backup paths includes: Based on the independent reliability score of the backup paths, determine the missing value of the redundancy contribution of each backup path relative to the primary path; Multiply the redundancy contribution missing values of all backup paths relative to the primary path to obtain the overall redundancy missing degree of the primary path. The difference between 1 and the overall redundancy level is denoted as the redundancy reliability.
8. The Internet of Things (IoT) data acquisition and monitoring management system according to claim 1, characterized in that, The method for obtaining the monitoring urgency level is as follows: The path risk of the primary path is determined based on the path stability, redundancy reliability, and declining health trend of the primary path; wherein, the path risk increases when the path stability, redundancy reliability, or declining health trend of the primary path decreases. The path risk is gating based on the path importance of the primary path to obtain the monitoring urgency level; wherein, when the path importance of the primary path decreases, the impact of the path risk on the monitoring urgency level is reduced.
9. The Internet of Things (IoT) data acquisition and monitoring management system according to claim 1, characterized in that, The process of determining the path-level monitoring period and path-level anomaly threshold based on the monitoring urgency, and projecting the path-level monitoring period onto the interfaces traversed by the communication path to obtain the interface-level telemetry period includes: The path-level target monitoring cycle and path-level anomaly threshold of the primary path are determined based on the monitoring urgency. The higher the monitoring urgency, the shorter the path-level target monitoring cycle and the more stringent the path-level anomaly threshold. Based on the set of interfaces traversed by the primary path, the path-level target monitoring period is projected onto the corresponding interface. When the same interface is traversed by multiple primary paths, the shortest period among the path-level target monitoring periods corresponding to the multiple primary paths is determined as the interface-level telemetry period of that interface.
10. The Internet of Things (IoT) data acquisition and monitoring management system according to claim 1, characterized in that, The process of collecting interface data according to the interface-level telemetry cycle, determining communication path anomalies based on the path-level anomaly threshold, and determining a recommended backup path based on the independent reliability score of the backup path when the communication path is abnormal includes: Receive communication traffic, packet loss rate, and occupancy rate values of the switch interface according to the interface-level telemetry cycle; Based on the set of interfaces traversed by the primary path, the maximum packet loss rate of each interface in the set is used as the current path packet loss metric, and the maximum occupancy rate of each interface in the set is used as the current path congestion metric. When the packet loss index of the current path is greater than the path-level anomaly threshold of the primary path, or when the congestion index of the current path is greater than the preset queue threshold for a preset number of consecutive times, the primary path is determined to be abnormal. After the primary path fails, the switching priority is determined based on the independent reliability score of the backup path, and the backup path with the highest switching priority is selected as the recommended backup path.
