Generate network impact values for alarms associated with network resources.
By combining network fault status and redundancy models with the controller system to calculate alarm impact values, the problem of the inability to assess the overall impact of network device alarms in existing technologies is solved, and efficient network resource management and fault handling are achieved.
Patent Information
- Application Number
- CN202610592263.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2025-05-07
- Filing Date
- 2026-04-30
- Publication Date
- 2026-11-10
AI Technical Summary
Existing technologies cannot effectively assess the overall impact of network device alarms and alerts, leading to wasted resources and improper handling of potential network failures.
The controller system receives network fault status data and redundancy models, combines them with telemetry data to generate telemetry alarms, calculates the impact value of each alarm, and prioritizes displaying alarms with high impact values.
It saves computing and network resources, improves the efficiency and accuracy of network fault handling, and avoids wasting resources on processing non-serious alarms.
Smart Images

Figure CN123074904A_ABST
Abstract
Description
Background Technology
[0001] Network device alerts and network device key performance indicators (KPIs) health status are used to track the health status of network devices provided in the network. Summary of the Invention
[0002] Some implementations described herein relate to a method. This method may include receiving current fault state data associated with a network and a redundancy model associated with the network, and receiving telemetry data and network device alarms associated with multiple network devices of the network. The method may include generating telemetry alarms based on the telemetry data, and generating multiple alarms when the telemetry alarms are combined with network device alarms, and calculating an impact value for each of the multiple alarms based on the current fault state data and the redundancy model to generate multiple impact values. This method may include managing the network based on the multiple impact values.
[0003] Some embodiments described herein relate to an apparatus. The apparatus may include one or more memories and one or more processors. The one or more processors may be configured to receive current fault state data associated with a network and a redundancy model associated with the network, and to receive telemetry data and network device alarms associated with a plurality of network devices of the network. The one or more processors may be configured to generate telemetry alarms based on the telemetry data, and to generate multiple alarms when telemetry alarms are combined with network device alarms, and to calculate an impact value for each of the multiple alarms based on the current fault state data and the redundancy model to generate multiple impact values. The one or more processors may be configured to manage the network based on the multiple impact values, and to provide a corresponding alarm associated with one of the multiple impact values for display based on determining that one of the impact values meets an impact threshold.
[0004] Some embodiments described herein relate to a non-transitory computer-readable medium storing a set of instructions. When executed by one or more processors of a device, the set of instructions enables the device to receive current fault state data associated with a network and a redundancy model associated with the network, wherein the redundancy model specifies the maximum number of network events that can occur without affecting network operation. When executed by one or more processors of the device, the set of instructions enables the device to receive telemetry data and network device alarms associated with multiple network devices in the network, and to generate telemetry alarms based on the telemetry data, and to generate multiple alarms when telemetry alarms are combined with network device alarms. When executed by one or more processors of the device, the set of instructions enables the device to calculate an impact value for each of the multiple alarms based on the current fault state data and the redundancy model to generate multiple impact values, and to manage the network based on these multiple impact values. Attached Figure Description
[0005] Figures 1A to 1I This is a schematic diagram illustrating an example of how network impact values are associated with generating alarms related to network resources.
[0006] Figure 2 This is a schematic diagram of an example environment in which the systems and methods described in this article can be implemented.
[0007] Figure 3 and Figure 4 yes Figure 2 A schematic diagram of example components of one or more devices.
[0008] Figure 5 This is a flowchart of an example process for generating network impact values for alarms associated with network resources. Detailed Implementation
[0009] The following detailed description of exemplary embodiments is with reference to the accompanying drawings. The same reference numerals in different drawings may identify the same or similar elements.
[0010] The current system maps the severity of alerts and alarms to categories such as critical, major, and minor. While the severity of alerts and alarms changes over time, the current system considers their severity in isolation and not based on network status. Therefore, from a severity perspective, alerts and alarms are static and isolated, failing to indicate their overall impact on the network. For example, a link failure might generate a corresponding alarm. This link failure can be handled as long as redundant links capable of carrying traffic exist. However, based on the overall network load or the available operational links, this link failure could lead to a catastrophic network failure, thus requiring a critical impact severity rating. The current system provides the ability to create additional rules to generate new alerts based on existing alerts. However, these additional rules do not work without user customization and are limited to a specific set of rules already created. Therefore, current technologies for handling network device alarms and alerts consume computing resources (e.g., processing resources, memory resources, communication resources, and / or similar resources), network resources, and / or similar resources, which are associated with the inability to define the severity of alarms and alerts, processing less severe alarms and alerts based on the inability to define the severity of alarms and alerts, processing network failures and data loss based on the inability to process more severe alarms and alerts, and / or similar situations.
[0011] Some implementations described herein relate to controller systems for generating network impact values for alarms associated with network resources. For example, the controller system may receive current fault state data associated with the network and a redundancy model associated with the network, and may receive telemetry data and network device alarms associated with multiple network devices. The controller system may generate telemetry alarms based on the telemetry data, and generate multiple alarms when telemetry alarms are combined with network device alarms, and may calculate impact values for each of the multiple alarms based on the current fault state data and the redundancy model to generate multiple impact values. The controller system may then manage the network based on these multiple impact values.
[0012] In this way, the controller system can generate network impact values for alarms associated with network resources. For example, the controller system can receive telemetry data, network device alarms associated with network devices, and the current fault status of the network. The controller system can determine telemetry alarms based on the telemetry data and can convert network device alarms into network device alarms. The controller system can combine telemetry alarms and network device alarms into multiple alarms and can calculate the impact value for each of the multiple alarms based on the current fault status of the network. The controller system can use these impact values to prioritize displaying these multiple alarms to network operators. Therefore, the controller system can save computing resources, network resources, and / or similar resources that would otherwise be consumed by the inability to define the severity of alarms and alerts, processing less severe alarms and alerts based on the inability to define their severity, and handling network failures and data loss and / or similar situations based on the inability to handle more severe alarms and alerts.
[0013] Figures 1A to 1I This is a schematic diagram of example 100 related to the generation of network impact values for alarms associated with network resources. For example... Figure 1A As shown, Example 100 includes terminal devices and a controller system associated with a network. The network may include multiple network devices, such as network device D1, network device D2, network device D3, network device D4, network device D5, network device D6, and network device D7, with links provided between one or more of these network devices. Further details regarding the terminal devices, controller system, network, and network devices are provided elsewhere in this document.
[0014] like Figure 1AAs shown, and via reference numeral 105, the controller system can receive current fault state data associated with the network and a redundancy model associated with the network. For example, the controller system can receive data associated with the network state and can determine the current fault state data based on the received data. The received data may include identifiers: data of operating network devices among the plurality of network devices, data of operating links associated with the plurality of network devices, the current traffic engineering bandwidth allocation of the network, the available bandwidth of the network, predicted upcoming traffic patterns (e.g., based on bucketing, trend analysis, or seasonality), scheduled demands based on events (e.g., holidays, sporting events, entertainment activities, etc.), and / or similar data. The current fault state data may include a dynamic combination of the received data. In some embodiments, the controller system may receive the current fault state data from a subsystem of the controller system, rather than from the network devices of the network.
[0015] In some implementations, users (e.g., network administrators) can define redundancy models for the network. For example, a redundancy model may include a data center redundancy model with user-defined parameters. These parameters may include the minimum number of [unspecified parameters] required to keep the network operational and functioning correctly. N The number of network devices and / or network resources that may not function without rendering the network inoperable (e.g., + m This redundancy model can be applied to every service, link, network device, and component (within a network device) of the network, and can include thresholds for each service, link, network device, and component. In some implementations, the redundancy model may include specifying the maximum number of network events that may occur without affecting network operation.
[0016] In some implementations, the redundancy model may include 2 N Redundancy model (e.g., providing a complete replication of all critical components), 2 N +1 redundancy model (e.g., is 2) N The model can be extended and additional redundancy layers can be added, such as active-passive redundancy models (e.g., one component is active and performs the required task, while another component remains passive and only becomes active when the main component fails), active-active redundancy models (e.g., both components are active and share the load), geographic redundancy models (e.g., redundant components are located in different geographic locations), hybrid redundancy models (e.g., components that combine different redundancy models), and / or similar models.
[0017] In one example, under current traffic conditions, the network might have four network devices, eight power supplies, and forty links failing, yet still be able to meet the Network Service Level Agreement (SLA). Depending on which component fails, the failed component may cause one or more other components to fail. For example, a network device failure might cause eight links and a redundant power supply to fail. After such an event, the network might have three network devices, seven power supplies, and thirty-two links available. In another example, a power supply failure might result in the network having four network devices, seven power supplies, and forty links available.
[0018] like Figure 1A As further shown, and via reference numeral 110, the controller system can receive telemetry data and network device alarms associated with multiple network devices in the network. For example, the controller system can receive telemetry data from network devices, network links, components of network devices, sub-components of network devices, and / or telemetry sensors associated with the network. The telemetry data may include data identifying network devices, network links, components of network devices, sub-components of network devices, and / or key performance indicators and health status of the network.
[0019] In some implementations, telemetry data may include a wide variety of metrics and information that help assess the health, performance, and status of network devices and services. For example, telemetry data may include network traffic data that identifies the size and type of traffic flowing through network devices. Telemetry data may include latency and response time, indicating the time required for data to travel from one point to another within the network. Telemetry data may include bandwidth utilization, indicating the amount of bandwidth being used by network devices and links. Telemetry data may include error rates and packet loss rates, indicating the frequency and type of errors occurring in the network. Telemetry data may include device health metrics, indicating the operational status and health of network devices. Telemetry data may include link status and performance, identifying the status and performance of links. Telemetry data may include QoS metrics associated with Quality of Service (QoS) policies and configuration performance. Telemetry data may include security metrics associated with network security status. Telemetry data may include network topology data regarding network layout and structure.
[0020] In some implementations, the controller system may receive network device alarms from the network device. Network device alarms may include alerts providing information about the network device's condition (e.g., the condition of the network device's network interface, chassis, system software, etc.) that may prevent the network device from functioning properly. In some implementations, from the controller system's perspective, network device alarms may be considered alarms (e.g., triggered by the network device rather than the controller system).
[0021] like Figure 1B As shown, and via reference numeral 115, the controller system can generate telemetry alarms based on telemetry data. For example, the controller system can utilize multiple steps to generate telemetry alarms based on telemetry data. In some implementations, the controller system can process the raw telemetry data to make it suitable for analysis. For example, the controller system can utilize normalization to convert telemetry data from different sources into a common format, can utilize filtering to remove irrelevant or redundant data from the telemetry data to focus on key metrics, and / or can utilize aggregation to summarize the telemetry data within a specific time interval.
[0022] Alternatively or additionally, the controller system can analyze processed telemetry data to identify patterns, trends, and anomalies. For example, the controller system can define Key Performance Indicators (KPIs) that reflect network health and performance (e.g., latency, packet loss rate, and bandwidth utilization). The controller system can establish thresholds for each KPI to indicate normal and abnormal conditions (e.g., processor utilization >80%). The controller system can utilize statistical methods and machine learning models to analyze trends and detect deviations from normal behavior. The controller system can implement anomaly detection techniques to identify anomalous patterns or peaks in telemetry data that may indicate potential problems.
[0023] Alternatively or additionally, the controller system can generate telemetry alarms based on the analysis of telemetry data. For example, the controller system can compare KPI values to predefined thresholds. If a KPI exceeds its threshold, the controller system can generate a telemetry alarm. The controller system can analyze trends over time to detect gradual changes that may not trigger threshold-based alarms, and generate telemetry alarms when significant trends are detected. The controller system can utilize anomaly detection models to identify anomalous patterns in the telemetry data and generate telemetry alarms when anomalies are detected.
[0024] like Figure 1CAs shown, and via reference numeral 120, the controller system can convert network device alerts into device alarms. For example, the controller system can perform several steps to convert network device alerts into device alarms. In some embodiments, the controller system can utilize data normalization to convert network device alerts into a common format for consistent processing. For example, the controller system can convert alerts from different network devices and formats into a standardized format, and can normalize data fields to ensure consistency (e.g., converting timestamps to a common time zone and format, standardizing severity levels, and unifying device identifiers). In some embodiments, the controller system can classify the normalized alerts based on predefined criteria to facilitate alarm generation. For example, the controller system can classify alerts based on severity level (e.g., hardware failure alerts can be classified as severe, while configuration warnings can be classified as minor), and can classify them based on alert type (e.g., alerts associated with link status changes, hardware failures, configuration errors, and performance issues). The controller system can associate alerts with specific network devices to facilitate targeted alarm generation. In some embodiments, the controller system can use a threshold-based alarm mechanism to generate device alarms based on the classified alerts. For example, the controller system can establish thresholds for different types of alarms (e.g., a threshold for link status changes might be set to generate an alarm when a link is interrupted). The controller system can continuously compare the severity and type of each alarm against predefined thresholds. If an alarm exceeds its threshold, the controller system can generate the corresponding device alarm.
[0025] like Figure 1DAs shown, and via reference numeral 125, the controller system can combine telemetry alarms and device alarms to generate multiple alarms associated with multiple network devices. For example, combining telemetry alarms and device alarms may include integrating data from different sources to provide a comprehensive view of network health and performance. The combined alarms ensure that they have context, priority, and actionability. In some implementations, the controller system can correlate relevant telemetry alarms and device alarms to generate multiple alarms associated with multiple network devices. For example, the controller system may utilize an interrelation model to identify relevant telemetry alarms and device alarms (e.g., high processor utilization (e.g., telemetry alarm) and hardware failure (e.g., device alarm) on the same network device may be related). In some implementations, the controller system can combine relevant telemetry alarms and device alarms into a comprehensive alarm. This may include merging information from both types of alarms to provide a complete picture of the problem. The controller system can add context to the combined alarms by including relevant information from telemetry data and device alerts. For example, the combined data might include detailed information about high processor utilization, hardware failures, and their impact on network performance. In this way, the controller system can effectively combine telemetry and device data, providing a comprehensive view of network problems and ensuring timely response and resolution.
[0026] like Figure 1E As shown, and via reference numeral 130, the controller system can calculate an impact value for each of a plurality of alarms based on current fault state data and a redundancy model to generate multiple impact values. For example, calculating an impact value for each alarm involves assessing the alarm's potential impact on overall network performance and reliability. The controller system can utilize current fault state data and a redundancy model to determine the criticality of each alarm. In some implementations, the controller system can analyze each alarm to understand its nature and context. For example, the controller system can determine the type of alarm (e.g., hardware failure, high processor utilization, or link outage) based on the analysis and can identify which network devices, links, or services are affected by the alarm. The controller system can assess the severity of the alarm (e.g., severe, major, or minor) based on predefined criteria or thresholds.
[0027] In some implementations, the controller system may apply a redundancy model to understand the network's ability to tolerate faults or events indicated by alarms. For example, the controller system may determine the current redundancy level of affected components (e.g., check if there are available passive network devices or links). The controller system may assess whether the network can continue to operate normally after a fault occurs. For example, if a link fails, the controller system may check if there are redundant links that can handle the traffic. In some implementations, the controller system may calculate the impact value of each alarm based on current fault state data and by applying a redundancy model. For example, the controller system may assess how an alarm affects network operation (e.g., operational impact). For example, the operational impact of a critical router failure may be greater than that of a minor switch failure. The controller system may consider the impact on a specific service or application (e.g., service impact). For example, the impact value may be higher if the alarm affects network devices that are critical to high-priority services. The controller system may incorporate a redundancy model to determine how a fault affects network redundancy (e.g., redundancy impact). For example, the impact value may be higher if the alarm causes the redundancy level to fall below an acceptable level. In some implementations, the controller system can use a weighted formula to combine operational impact, service impact, and redundancy impact into a single impact value, as shown below: in Wo , Ws ,as well as Wr The weights are assigned to each influence based on its importance.
[0028] like Figure 1F As shown, and via reference numeral 135, the controller system can determine whether one of a plurality of impact values meets an impact threshold. For example, the user of the controller system can define this impact threshold. When an impact value meets the impact threshold, the controller system can provide a notification to the user, indicating that an alarm associated with that impact value may lead to a network problem and should be addressed. In some embodiments, the controller system can determine that one of a plurality of impact values meets the impact threshold. Alternatively, the controller system can determine that one of a plurality of impact values does not meet the impact threshold. In some embodiments, in the absence of an impact threshold, when a fault associated with this impact value is only one step away from a network failure, the controller system can by default identify an impact value as high impact.
[0029] like Figure 1FAs further shown, and via reference numeral 140, the controller system can prevent the display of a corresponding alarm associated with a given impact value based on the determination that one of a plurality of impact values fails to meet an impact threshold. For example, if the controller system determines that one of a plurality of impact values fails to meet an impact threshold, it can prevent the display of the corresponding alarm associated with that one of the plurality of impact values. In this way, users (e.g., network operators) are not overwhelmed by alarms with low impact values (e.g., those associated with faults that do not affect the network).
[0030] like Figure 1F Further, and via reference numeral 145, the controller system can provide a display of a corresponding alarm associated with one of a plurality of impact values based on determining that one of the impact values meets an impact threshold. For example, if the controller system determines that one of the plurality of impact values meets an impact threshold, the controller system can provide data identifying the corresponding alarm associated with that one of the plurality of impact values to the terminal device. The terminal device can then display the corresponding alarm associated with one of the plurality of impact values to its user. In this way, users (e.g., network operators) can quickly be informed of alarms with high impact values (e.g., associated with faults that will damage the network), allowing users to attempt to correct these faults.
[0031] like Figure 1G As shown by reference numeral 150 in the accompanying figure, the controller system can determine whether one of a plurality of influence values meets a dynamic influence threshold based on predicted faults in the network over a given time period. For example, the controller system can use a machine learning model to make forward-looking predictions about the network's resource utilization and predict how many faults will typically occur in the network over a given time period (e.g., a day). The controller system can use the resource utilization predictions and the predicted faults to generate a dynamic influence threshold. In some implementations, the dynamic influence threshold can be set such that the number of redundancy pools maintained by the network is higher than the number expected to be consumed during that time period. In some implementations, the controller system can determine that one of a plurality of influence values meets the dynamic influence threshold. Alternatively, the controller system can determine that one of a plurality of influence values does not meet the dynamic influence threshold.
[0032] like Figure 1GAs further illustrated by reference numeral 155, the controller system can prevent the display of a corresponding alarm associated with one of a plurality of impact values based on the determination that one of the impact values fails to meet a dynamic impact threshold. For example, if the controller system determines that one of the plurality of impact values fails to meet the dynamic impact threshold, it can prevent the display of the corresponding alarm associated with that one of the impact values. This prevents users (e.g., network operators) from being overwhelmed by alarms with low impact values (e.g., those associated with faults that do not affect the network).
[0033] like Figure 1G As further illustrated by reference numeral 160, the controller system can provide a corresponding alarm associated with one of a plurality of impact values for display, based on the determination that one of the impact values meets a dynamic impact threshold. For example, if the controller system determines that one of the impact values meets the dynamic impact threshold, it can provide data to the terminal device identifying the corresponding alarm associated with that impact value. The terminal device can then display the corresponding alarm associated with that impact value to its user. This allows the user to quickly learn about alarms with high impact values (e.g., those associated with faults that could damage the network), enabling the user to attempt to correct these faults.
[0034] like Figure 1H As shown in Figure 165, the controller system can utilize simulated, synthetic, or predicted utilization rates to determine a certain number of impact values that are generated and meet an impact threshold. For example, the controller system can use a machine learning model to make forward predictions about the network's resource utilization and determine how many faults typically occur in the network over a given time period (e.g., a day). The controller system can use the faults predicted and determined by resource utilization to determine a certain number of impact values that are generated and meet an impact threshold.
[0035] In some implementations, the controller system may utilize synthetic data (e.g., traffic) to monitor endpoint services provided by the network. The controller system may use the endpoint services monitored during the use of synthetic data to determine a certain number of impact values that are generated and meet an impact threshold. Alternatively or additionally, the controller system may utilize simulation to model the loss of any resource and the net impact of alarms generated based on that loss. The simulation may include impact values and may identify one or more resources that, upon failure in the simulation, would result in the generation of an impact alarm and meet the impact threshold.
[0036] like Figure 1HAs further shown by reference numeral 170 in the accompanying drawings, the controller system can provide corresponding alarms associated with the given number of impact values for display. For example, the controller system can provide data to a terminal device identifying a corresponding alarm associated with one of a plurality of impact values. The terminal device can then display the corresponding alarm associated with that impact value to its user (e.g., a network administrator).
[0037] like Figure 1I As shown in Figure 175, the controller system can sort multiple alarms based on multiple impact values to generate a sorted list of alarms. For example, the controller system can place the alarm with the largest impact value at the first position in the sorted list, the alarm with the second largest impact value at the second position, and so on. The controller system can continue sorting until the alarm with the smallest impact value is placed at the last position in the sorted list.
[0038] like Figure 1I As further shown by reference numeral 180 in the accompanying drawings, the controller system can provide a sorted list of alarms for display. For example, the controller system can provide the sorted list of alarms to a terminal device, which can then display the sorted list to its users (e.g., a network operator). Alternatively, the controller system can provide the top portion of the sorted list of alarms (e.g., the top 10%, 20%, etc.) to the terminal device, which can then display the top portion of the sorted list to the user. In this way, the user can prioritize multiple alarms based on the order provided in the sorted list.
[0039] In this way, the controller system can generate network impact values for alarms associated with network resources. For example, the controller system can receive telemetry data, network device alarms associated with network devices, and the current fault status of the network. The controller system can determine telemetry alarms based on the telemetry data and convert network device alarms into network device alarms. The controller system can combine telemetry alarms and network device alarms into multiple alarms and calculate the impact value for each alarm based on the current fault status of the network. The controller system can use these impact values to prioritize displaying multiple alarms to the network operator. Therefore, the controller system can save computing and network resources that might otherwise be consumed by the inability to define the severity of alarms and alerts, processing less severe alarms and alerts based on the inability to define their severity, or causing network failures and data loss due to the inability to process more severe alarms and alerts.
[0040] As mentioned above, Figures 1A to 1I This is provided as an example. Other examples may differ. Figures 1A to 1IThe content described in the text. Figures 1A to 1I The number and arrangement of devices shown are provided as an example. In reality, there may be more. Figures 1A to 1I The additional, fewer, different, or differently arranged devices shown. Furthermore, Figures 1A to 1I The two or more devices shown can be implemented within a single device, or Figures 1A to 1I The single device shown can be implemented as multiple distributed devices. Alternatively, Figures 1A to 1I The set of devices shown (e.g., one or more devices) can perform actions described as being performed by Figures 1A to 1I One or more functions performed by another set of devices shown.
[0041] Figure 2 This is a schematic diagram of an example environment 200 in which the systems and methods described in this paper can be implemented. For example... Figure 2 As shown, environment 200 may include controller system 201, which may include one or more components of cloud computing system 202 and / or may execute within cloud computing system 202. Cloud computing system 202 may include one or more components 203-212, as described in more detail below. Figure 2 As further shown, environment 200 may include network 220, network device 230, and / or terminal device 240. The devices and / or components of environment 200 may be interconnected via wired and / or wireless connections.
[0042] The cloud computing system 202 may include computing hardware 203, a resource management component 204, a host operating system (OS) 205, and / or one or more virtual computing systems 206. The cloud computing system 202 may run on, for example, an Amazon Web Services platform, a Microsoft Azure platform, or a Snowflake platform. The resource management component 204 may perform virtualization (e.g., abstraction) of the computing hardware 203 to create one or more virtual computing systems 206. Using virtualization, the resource management component 204 enables a single computing device (e.g., a computer or server) to operate as multiple computing devices, such as by creating multiple isolated virtual computing systems 206 from the computing hardware 203 of a single computing device. In this way, the computing hardware 203 can operate more efficiently with lower power consumption, higher reliability, higher availability, higher utilization, greater flexibility, and lower cost compared to using a single computing device.
[0043] Computing hardware 203 may include hardware and corresponding resources from one or more computing devices. For example, computing hardware 203 may include hardware from a single computing device (e.g., a single server) or hardware from multiple computing devices (e.g., multiple servers), such as multiple computing devices in one or more data centers. As shown, computing hardware 203 may include one or more processors 207, one or more memories 20, and / or one or more network components 209. Examples of processors, memories, and network components (e.g., communication components) are described elsewhere herein.
[0044] Resource management component 204 may include virtualization applications (e.g., executed on hardware, such as computing hardware 203) capable of virtualizing computing hardware 203 to start, stop, and / or manage one or more virtual computing systems 206. For example, resource management component 204 may include a hypervisor (e.g., a bare-metal or Type 1 hypervisor, a managed or Type 2 hypervisor, or other types of hypervisors) or a virtual machine monitor, such as when virtual computing system 206 is virtual machine 210. Additionally or alternatively, resource management component 204 may include a container manager, such as when virtual computing system 206 is container 211. In some implementations, resource management component 204 executes within and / or in coordination with host operating system 205.
[0045] Virtual computing system 206 may include virtual environments that enable the execution of the operations and / or processes described herein in the cloud using computing hardware 203. As shown, virtual computing system 206 may include virtual machines 210, containers 211, or hybrid environments 212 including virtual machines and containers, etc. Virtual computing system 206 may use a file system that includes binaries, software libraries, and / or other resources required to execute applications on a guest operating system (e.g., within virtual computing system 206) or host operating system 205 to execute one or more applications.
[0046] Although controller system 201 may include one or more components 203-212 of cloud computing system 202, may execute within cloud computing system 202, and / or may be hosted within cloud computing system 202, in some implementations, controller system 201 may not be cloud-based (e.g., may be implemented outside of cloud computing system) or may be partially cloud-based. For example, controller system 201 may include one or more devices that are not part of cloud computing system 202, such as... Figure 3 Device 300 may include a standalone server or another type of computing device. Controller system 201 may perform one or more operations and / or processes as described in more detail elsewhere herein.
[0047] Network 220 may include one or more wired and / or wireless networks. For example, network 220 may include cellular networks, public land mobile networks (PLMNs), local area networks (LANs), wide area networks (WANs), private networks, the Internet, and / or combinations of these or other types of networks. Network 220 enables communication between devices in environment 200.
[0048] Network device 230 may include one or more devices capable of receiving, processing, storing, routing, and / or providing traffic (e.g., packets and / or other information or metadata) in the manner described herein. For example, network device 230 may include routers such as label switching routers (LSRs), label edge routers (LERs), ingress routers, egress routers, provider routers (e.g., provider edge routers or provider core routers), virtual routers, or another type of router. Additionally or alternatively, network device 230 may include gateways, switches, firewalls, hubs, bridges, reverse proxies, servers (e.g., proxy servers, cloud servers, or data center servers), load balancers, and / or similar devices. In some embodiments, network device 230 may be a physical device implemented within a enclosure such as a chassis or base. In some embodiments, network device 230 may be a virtual device implemented by one or more computing devices in a cloud computing environment or data center. In some embodiments, network device group 230 may be a group of data center nodes used to route traffic over a network.
[0049] Terminal device 240 may include one or more devices capable of receiving, generating, storing, processing, and / or providing information as described elsewhere herein. Terminal device 240 may include communication devices and / or computing devices. For example, terminal device 240 may include wireless communication devices, mobile phones, user equipment, laptop computers, tablet computers, desktop computers, game consoles, set-top boxes, wearable communication devices (e.g., smartwatches, smart glasses, head-mounted displays, or virtual reality headsets), or similar types of devices.
[0050] Figure 2 The number and arrangement of devices and networks shown are for illustrative purposes only. In practice, there may be more. Figure 2 The additional equipment and / or networks, fewer equipment and / or networks, different equipment and / or networks, or the arrangement of equipment and / or networks shown are different from those shown. Figure 2 The difference is shown. Furthermore, Figure 2 The two or more devices shown can be implemented within a single device, or Figure 2The single device shown can be implemented as multiple distributed devices. Additionally or alternatively, the set of devices in environment 200 (e.g., one or more devices) can perform one or more functions described as being performed by another set of devices in environment 200.
[0051] Figure 3 yes Figure 2 Example component diagrams of one or more devices are provided. These example components may be included in device 300, which may correspond to controller system 201, network device 230, and / or terminal device 240. In some embodiments, controller system 201, network device 230, and / or terminal device 240 may include one or more devices 300 and / or one or more components of device 300. Figure 3 As shown, device 300 may include bus 310, processor 320, memory 330, input component 340, output component 350, and communication interface 360.
[0052] Bus 310 includes one or more components capable of enabling wired and / or wireless communication between components of device 300. Bus 310 can... Figure 3 Two or more components are coupled together, such as via operational coupling, communication coupling, electronic coupling, and / or electrical coupling. Processor 320 includes a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a controller, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and / or another type of processing component. Processor 320 is implemented in hardware, firmware, or a combination of hardware and software. In some embodiments, processor 320 includes one or more processors capable of being programmed to perform one or more operations or processes described elsewhere herein.
[0053] Memory 330 includes volatile and / or non-volatile memory. For example, memory 330 may include random access memory (RAM), read-only memory (ROM), hard disk drive, and / or another type of memory (e.g., flash memory, magnetic storage, or optical storage). Memory 330 may include internal memory (e.g., RAM, ROM, or hard disk drive) and / or removable memory (e.g., removable via a universal serial bus). Memory 330 is a non-transitory computer-readable medium. Memory 330 stores information, instructions, and / or software (e.g., one or more software applications) related to the operation of device 300. In some embodiments, memory 330 includes one or more memories coupled to one or more processors (e.g., processor 320), such as via bus 310.
[0054] Input component 340 enables device 300 to receive input, such as user input and / or sensed input. For example, input component 340 may include a touchscreen, keyboard, keypad, mouse, button, microphone, switch, sensor, GPS sensor, accelerometer, gyroscope, and / or actuator. Output component 350 enables device 300 to provide output, such as via a display, speaker, and / or light-emitting diode. Communication interface 360 enables device 300 to communicate with other devices via wired and / or wireless connections. For example, communication interface 360 may include a receiver, transmitter, transceiver, modem, network interface card, and / or antenna.
[0055] Device 300 may perform one or more of the operations or procedures described herein. For example, a non-transitory computer-readable medium (e.g., memory 330) may store a set of instructions (e.g., one or more instructions or code) for processor 320 to execute. Processor 320 may execute the set of instructions to perform one or more of the operations or procedures described herein. In some embodiments, one or more processors 320 execute the set of instructions such that the one or more processors 320 and / or device 300 perform one or more of the operations or procedures described herein. In some embodiments, hardwired circuitry may be used in place of or in combination with instructions to perform one or more of the operations or procedures described herein. Additionally or alternatively, processor 320 may be configured to perform one or more of the operations or procedures described herein. Therefore, the embodiments described herein are not limited to any particular combination of hardware circuitry and software.
[0056] Figure 3 The number and arrangement of components shown are for illustrative purposes only. Device 300 may include more than Figure 3 The additional components, fewer components, different components, or components arranged differently shown. Additionally or alternatively, the component set of device 300 (e.g., one or more components) can perform one or more functions described as being performed by another component set of device 300.
[0057] Figure 4 yes Figure 2 Example component diagrams of one or more devices. These example components may be included in device 400. Device 400 may correspond to network device 230. In some embodiments, network device 230 may include one or more devices 400 and / or one or more components of device 400. Figure 4As shown, device 400 may include one or more input components 410-1 to 410-B (B≥1) (hereinafter collectively referred to as input components 410, individually referred to as input components 410), switching component 420, one or more output components 430-1 to 430-C (C≥1) (hereinafter collectively referred to as output components 430, individually referred to as output components 430), and controller 440.
[0058] Input component 410 may be one or more connection points for a physical link and may be the entry point for one or more incoming traffic (e.g., packets). Input component 410 may process incoming traffic, such as by performing data link layer encapsulation or decapsulation. In some embodiments, input component 410 may send and / or receive packets. In some embodiments, input component 410 may include an input line card that includes one or more packet processing components (e.g., in the form of an integrated circuit), such as one or more interface cards (IFCs), packet forwarding components, line card controller components, input ports, processors, memory, and / or input queues. In some embodiments, device 400 may include one or more input components 410.
[0059] Switching component 420 interconnects input component 410 with output component 430. In some embodiments, switching component 420 may be implemented via one or more crossbar switches, buses, and / or shared memory. Shared memory may serve as a temporary buffer for storing packets from input component 410 before they are finally scheduled to be sent to output component 430. In some embodiments, switching component 420 enables input component 410, output component 430, and / or controller 440 to communicate with each other.
[0060] Output component 430 can store packets and schedule packets for transmission over the output physical link. Output component 430 can support data link layer encapsulation or decapsulation, and / or various higher-level protocols. In some embodiments, output component 430 can send and / or receive packets. In some embodiments, output component 430 may include an output line card that includes one or more packet processing components (e.g., in the form of integrated circuits), such as one or more IFCs, packet forwarding components, line card controller components, output ports, processors, memory, and / or output queues. In some embodiments, device 400 may include one or more output components 430. In some embodiments, input component 410 and output component 430 may be implemented from the same set of components (e.g., the input / output component may be a combination of input component 410 and output component 430).
[0061] Controller 440 includes a processor, which may take the form of, for example, a CPU, GPU, APU, microprocessor, microcontroller, DSP, FPGA, ASIC, and / or another type of processor. The processor is implemented in hardware, firmware, or a combination of hardware and software. In some embodiments, controller 440 may include one or more processors that can be programmed to perform functions.
[0062] In some implementations, controller 440 may include RAM, ROM, and / or another type of dynamic or static storage device (e.g., flash memory, magnetic storage, optical storage, etc.) for storing information and / or instructions for use by controller 440.
[0063] In some implementations, controller 440 can communicate with other devices, networks, and / or systems connected to device 400 to exchange information about the network topology. Controller 440 can create routing tables based on the network topology information, create forwarding tables based on the routing tables, and forward the forwarding tables to input component 410 and / or output component 430. Input component 410 and / or output component 430 can use the forwarding tables to perform route looks for incoming and / or outgoing packets.
[0064] Controller 440 can execute one or more processes described herein. Controller 440 can execute these processes by executing software instructions stored in a non-transitory computer-readable medium. Herein, a computer-readable medium is defined as a non-transitory memory device. A memory device includes storage space within a single physical storage device or storage space distributed across multiple physical storage devices.
[0065] Software instructions may be read from another computer-readable medium or from another device via a communication interface into the memory and / or storage components associated with controller 440. When executed, the software instructions stored in the memory and / or storage components associated with controller 440 may cause controller 440 to perform one or more processes described herein. Additionally or alternatively, hardwired circuitry may be used in place of or in combination with the software instructions to perform one or more processes described herein. Therefore, the embodiments described herein are not limited to any particular combination of hardware circuitry and software.
[0066] Figure 4 The number and arrangement of components shown are provided as an example. In reality, device 400 may include more than [a specific number of components]. Figure 4 The components shown are additional, fewer, different, or arranged differently. Additionally or alternatively, the component set of device 400 (e.g., one or more components) may perform one or more functions described as being performed by another component set of device 400.
[0067] Figure 5 This is a flowchart of an example process 500 for generating network impact values for alarms associated with network resources. In some implementations, Figure 5 One or more process blocks can be executed by a device (e.g., controller system 201). In some implementations, Figure 5 One or more process blocks may be executed by another device or a group of devices including that device, such as a terminal device (e.g., terminal device 240) and / or a network device (e.g., network device 230). Additionally or alternatively, Figure 5 One or more process blocks can be executed by one or more components of device 300, such as processor 320, memory 330, input component 340, output component 350, and / or communication interface 360. Additionally or alternatively, Figure 5 One or more process blocks may be executed by one or more components of the device 400, such as input component 410, switching component 420, output component 430, and / or controller 440.
[0068] like Figure 5 As shown, process 500 may include receiving current fault state data associated with the network and a redundancy model associated with the network (block 510). For example, as described above, the device may receive current fault state data associated with the network and a redundancy model associated with the network. In some embodiments, the current fault state data includes data identifying one or more of the following: operating network devices among a plurality of network devices, operating links associated with the plurality of network devices, current traffic-engineered bandwidth allocation of the network, available bandwidth of the network, predicted upcoming traffic patterns, or event-based predetermined demands. In some embodiments, the redundancy model specifies the maximum number of network events that can occur without affecting network operation.
[0069] like Figure 5 As further shown, process 500 may include receiving telemetry data and network device alarms associated with multiple network devices in the network (block 520). For example, as described above, the device may receive telemetry data and network device alarms associated with multiple network devices in the network.
[0070] like Figure 5As further shown, process 500 may include generating telemetry alarms based on telemetry data, and generating multiple alarms when telemetry alarms are combined with network device alarms (block 530). For example, as described above, the device may generate telemetry alarms based on telemetry data, and generate multiple alarms when telemetry alarms are combined with network device alarms. In some embodiments, generating telemetry alarms based on telemetry data includes: calculating key performance indicators (KPIs) based on telemetry data, identifying KPIs among the calculated KPIs that fail to meet their respective KPI thresholds, and generating telemetry alarms for the KPIs that fail to meet their respective KPI thresholds.
[0071] like Figure 5 As further shown, process 500 may include calculating an impact value for each of the multiple alarms based on the current fault state data and the redundancy model to generate multiple impact values (block 540). For example, as described above, the device may calculate an impact value for each of the multiple alarms based on the current fault state data and the redundancy model to generate multiple impact values.
[0072] like Figure 5 As further shown, process 500 may include managing the network based on multiple impact values (block 550). For example, as described above, the device may manage the network based on multiple impact values.
[0073] In some implementations, process 500 includes determining whether one of a plurality of influence values meets an influence threshold. In some implementations, process 500 includes preventing the display of a corresponding alarm associated with an influence value based on the determination that one of the plurality of influence values fails to meet the influence threshold. In some implementations, process 500 includes providing the display of a corresponding alarm associated with an influence value based on the determination that one of the plurality of influence values meets the influence threshold.
[0074] In some implementations, process 500 includes determining whether one of a plurality of impact values meets a dynamic impact threshold for a predicted fault in the network over a time period. In some implementations, process 500 includes preventing the display of a corresponding alarm associated with one of the plurality of impact values based on the determination that one of the impact values fails to meet the dynamic impact threshold. In some implementations, process 500 includes providing the display of a corresponding alarm associated with one of the plurality of impact values based on the determination that one of the impact values meets the dynamic impact threshold.
[0075] In some embodiments, process 500 includes using simulated or synthetic data to determine a certain number of influence values that are generated and meet an influence threshold. In some embodiments, process 500 includes providing and displaying corresponding alarms associated with the certain number of influence values. In some embodiments, process 500 includes sorting multiple alarms based on multiple influence values to generate a sorted list of alarms, and providing and displaying the sorted list of alarms.
[0076] although Figure 5 An exemplary block of process 500 is shown, but in some implementations, process 500 may include more than Figure 5 The additional, fewer, different, or dissimilar blocks described in the diagram. Alternatively, two or more blocks of process 500 can be executed in parallel.
[0077] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit the embodiments to the precise forms disclosed. Modifications can be made based on the foregoing disclosure or from practice of the embodiments.
[0078] As used herein, the term "component" is intended to be interpreted broadly as hardware, firmware, or a combination of hardware and software. Clearly, the systems and methods described herein can be implemented in various forms of hardware, firmware, and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the implementation. Therefore, no specific software code is referenced in the description of the operation and behavior of the systems and / or methods herein—it should be understood that the systems and / or methods can be implemented using software and hardware based on the description herein.
[0079] Although specific combinations of features are listed in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various embodiments. In fact, many of these features can be combined in ways not listed in the claims and / or not disclosed in the specification. Although each dependent claim listed below may depend directly on only one claim, the disclosure of various embodiments includes combinations of each dependent claim with every other claim in the claim set.
[0080] Unless explicitly described as critical or necessary, no element, action, or instruction used herein should be construed as critical or necessary. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Furthermore, as used herein, the article “described” is intended to include one or more items associated with the article “described” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the term “set” is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.) and may be used interchangeably with “one or more.” When referring to only one item, the phrase “only one” or similar language is used. Additionally, as used herein, the terms “have,” “possess,” “have,” etc., are intended to be open-ended terms. Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Additionally, as used herein, the term “or” when used in a series is intended to be inclusive and may be used interchangeably with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “any” or “only one of them”).
[0081] Various exemplary embodiments have been described in the foregoing specification with reference to the accompanying drawings. However, it will be apparent that various modifications and alterations can be made thereto, and additional embodiments can be implemented, without departing from the broader scope of the invention as set forth in the appended claims. Therefore, the specification and drawings should be considered illustrative rather than restrictive.
Claims
1. A method comprising: The device receives current fault status data associated with the network and a redundancy model associated with the network. The device receives telemetry data and network device alarms associated with multiple network devices in the network; The device generates telemetry alarms based on the telemetry data, and generates multiple alarms when the telemetry alarms are combined with network device alarms. The device calculates the impact value for each of the multiple alarms based on the current fault status data and the redundancy model, to generate multiple impact values. as well as The device manages the network based on the plurality of influence values.
2. The method according to claim 1, further comprising: Determine whether one of the multiple influence values meets the influence threshold.
3. The method according to claim 2, further comprising: Based on the determination that one of the plurality of influence values fails to meet the influence threshold, the display of the corresponding alarm associated with the one of the plurality of influence values is prevented.
4. The method according to claim 2, further comprising: Based on the determination that one of the plurality of influence values meets the influence threshold, a corresponding alarm associated with the one of the plurality of influence values is provided for display.
5. The method according to claim 1, further comprising: Determine whether one of the plurality of influence values satisfies a dynamic influence threshold based on a predicted fault in the network over a time period.
6. The method according to claim 5, further comprising: Based on the determination that one of the plurality of influence values fails to meet the dynamic influence threshold, the display of the corresponding alarm associated with the one of the plurality of influence values is prevented.
7. The method according to claim 5, further comprising: Based on the determination that one of the plurality of influence values meets the dynamic influence threshold, a corresponding alarm associated with the one of the plurality of influence values is provided for display.
8. An apparatus comprising: One or more memory units; as well as One or more processors, said one or more processors being used for: Receive current fault status data associated with the network and a redundancy model associated with the network; Receive telemetry data and network device alarms associated with multiple network devices in the network; Telemetry alarms are generated based on the telemetry data, and multiple alarms are generated when the telemetry alarms are combined with the network device alarms. Based on the current fault status data and the redundancy model, an impact value is calculated for each of the multiple alarms to generate multiple impact values; The network is managed based on the aforementioned multiple influence values; as well as Based on the determination that one of the plurality of influence values meets the influence threshold, a corresponding alarm associated with one of the plurality of influence values is provided for display.
9. The device of claim 8, wherein the one or more processors are further configured to: Simulated or synthetic data are used to determine a certain number of influence values that are generated and meet the influence threshold.
10. The device of claim 9, wherein the one or more processors are further configured to: Provide corresponding alarms associated with the stated number of impact values for display.
11. The device of claim 8, wherein the one or more processors are further configured to: The multiple alarms are sorted based on the multiple influence values to generate a sorted list of alarms; and Provide a sorted list of the alarms for display.
12. The device of claim 8, wherein the current fault status data includes data identifying one or more of the following: a network device in operation among the plurality of network devices, an operational link associated with the plurality of network devices, current traffic engineering bandwidth allocation for the network, available bandwidth of the network, predicted upcoming traffic patterns, or event-based predetermined demand.
13. The apparatus of claim 8, wherein the one or more processors for generating the telemetry alarm based on the telemetry data are configured to: Key performance indicators (KPIs) are calculated based on the telemetry data. Identify the KPIs among the calculated KPIs that fail to meet the corresponding KPI threshold; and The telemetry alarm is generated for the KPI that fails to meet the corresponding KPI threshold.
14. The device of claim 8, wherein the redundancy model specifies the maximum number of network events that can occur without affecting the operation of the network.
15. A non-transitory computer-readable medium storing an instruction set, the instruction set comprising: One or more instructions, which, when executed by one or more processors of the device, cause the device to: Receive current fault status data associated with the network and a redundancy model associated with the network. The redundancy model specifies the maximum number of network events that can occur without affecting the operation of the network; Receive telemetry data and network device alarms associated with multiple network devices in the network; Telemetry alarms are generated based on the telemetry data, and multiple alarms are generated when the telemetry alarms are combined with the network device alarms. Based on the current fault status data and the redundancy model, an impact value is calculated for each of the multiple alarms to generate multiple impact values; as well as The network is managed based on the aforementioned multiple influence values.
16. The non-transitory computer-readable medium of claim 15, wherein one or more instructions further cause the device to: Determine whether one of the plurality of influence values meets the influence threshold; and Selectively: Based on the determination that one of the plurality of influence values fails to meet the influence threshold, the display of the corresponding alarm associated with that one of the plurality of influence values is blocked; or Based on the determination that one of the plurality of influence values meets the influence threshold, a corresponding alarm associated with the one of the plurality of influence values is provided for display.
17. The non-transitory computer-readable medium of claim 15, wherein one or more instructions further cause the device to: Determine whether one of the plurality of influence values satisfies a dynamic influence threshold based on a predicted fault in the network over a time period; and Selectively: Based on the determination that one of the plurality of influence values fails to meet the dynamic influence threshold, the display of the corresponding alarm associated with that one of the plurality of influence values is prevented; or Based on the determination that one of the plurality of influence values meets the dynamic influence threshold, a corresponding alarm associated with the one of the plurality of influence values is provided for display.
18. The non-transitory computer-readable medium of claim 15, wherein one or more instructions further cause the device to: Using simulated or synthetic data, a certain number of influence values that are generated and meet the influence threshold are determined; and Provide corresponding alarms associated with the stated number of impact values for display.
19. The non-transitory computer-readable medium of claim 15, wherein one or more instructions further cause the device to: The multiple alarms are sorted based on the multiple influence values to generate a sorted list of alarms; and Provide a sorted list of the alarms for display.
20. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions that cause the device to generate the telemetry alarm based on the telemetry data cause the device to: Key performance indicators (KPIs) are calculated based on the telemetry data. Identify the KPIs that, after calculation, cannot meet the corresponding KPI threshold; as well as The telemetry alarm is generated for the KPI that fails to meet the corresponding KPI threshold.
