Rate based failure detection

• US 9,857,825 B1
• Filed: 10/28/2013
• Issued: 01/02/2018
• Est. Priority Date: 10/29/2012
• Status: Active Grant

• Current Assignee: Washington State University
• Original Assignee: Washington State University
• Inventors: Johnson, Brett Emery Trabun, Gamage, Thoshitha Thanushka, Bakken, David Edward
• Primary Examiner(s): Wasel, Mohamed
• Assistant Examiner(s): Book, Phyllis A
• Application Number:
  US14/065,225
• Time in Patent Office: 1,527 Days
• Field of Search: None
• CPC Class Codes: G05F 5/00 Systems for regulating electric variables by detecting deviations in the electric input to the system and thereby controlling a device within the system to obtain a regulated output
• CPC Class Codes: G06Q 50/06 Energy or water supply
• CPC Class Codes: H04L 41/0631 using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
• CPC Class Codes: H04L 41/142 using statistical or mathematical methods
• CPC Class Codes: H04L 41/5019 Ensuring fulfilment of SLA
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/0852 Delays
• CPC Class Codes: H04L 43/0894 Packet rate
• CPC Class Codes: Y04S 40/00 Systems for electrical power generation, transmission, distribution or end-user application management characterised by the use of communication or information technologies, or communication or information technology specific aspects supporting them

Abstract

This disclosure describes, in part, a system management component and failure detection component for use in a power grid data network to identify anomalies within the network and systematically adjust the quality of service of data published by publishers and subscribed to by subscribers within the network. In one implementation, subscribers may identify a desired data rate, a minimum acceptable data rate, desired latency, minimum acceptable latency and a priority for each subscription. The failure detection component may identify an anomaly within the network and a source of the anomaly. Based on the identified anomaly, data rates and or data paths may be adjusted in real-time to ensure that the power grid data network does not become overloaded and/or fail.

Claims

1. A method for detecting anomalies in a computer network in which a plurality of publishers publish data and a plurality of subscribers subscribe to published data via network routes in the computer network defined to satisfy corresponding expected quality of service (“

QoS”

) of the individual subscribers, the method comprising;

under control of one or more computing devices configured with executable instructions,

receiving a first notice from a first node within the computer network that data received on an incoming connection is not being received according to an expected quality of service from an upstream node;

determining whether a second notice has been received from a second node within the computer network, the second node being configured to also receive data on an incoming connection from the upstream node;

determining, based at least in part on the first notice and the second notice, that an anomaly exists within the computer network when (i) the first and second notices both indicate that data received on the corresponding incoming connections is not being received according to the corresponding expected qualities of service and (ii) a notice from the upstream node indicating that the data forwarded on an outgoing connection is not being forwarded according to another expected quality of service has not been received;

determining whether one or more other notices have been received from other nodes receiving data from the upstream node; and

in response to determining that one or more other notices have been received from other nodes receiving data from the upstream node, indicating that a cause of the anomaly is at least one of the upstream node or a data path to the upstream node in the computer network.

2. The method of claim 1, wherein determining that the anomaly exists includes indicating that a cause of the anomaly includes a failure of the upstream node.

3. The method of claim 1, further comprising:

determining whether the first node and the second node are on the same path from the upstream node within the computer network; and

wherein determining that the anomaly exists includes indicating that the upstream node is a cause of the anomaly in response to determining that the first and second nodes are on different paths from the upstream node within the computer network.

4. The method of claim 1 wherein:

determining that the anomaly exists includes determining that a path between the first node and the upstream node is a cause of the anomaly when the second notice has not been received from the second node within the computer network indicating that data received on the incoming connections is not being received according to the expected quality of service.

5. The method of claim 1, wherein the anomaly is at least one of a rate failure, a QoS failure, a physical network failure, a node failure, or a path failure.

6. A computing system for detecting anomalies in a computer network in which a plurality of publishers publish data and a plurality of subscribers subscribe to published data via network routes in the computer network defined to satisfy corresponding expected quality of service (“

QoS”

) of the individual subscribers, comprising;

one or more processors; and

a memory coupled to the one or more processors and storing program instructions that when executed by the one or more processors cause the one or more processors to;

receive a first notice from a first node within the computer network;

determine whether the first notice corresponds to that data incoming at the first node is not being received according to an expected quality of service;

in response to determining that the first notice corresponding to that data incoming at the first node is not being received according to an expected quality of service, determine whether a second notice is received from a second node within the network indicating that data forwarded on an outgoing connection is not being forwarded according to another expected quality of service, the second node being upstream of the first node; and

in response to determining that the second notice has been received,

determine based at least in part on the first notice and the second notice that an anomaly exists within the network when the second notice has not been received;

determine whether one or more other notices have been received from other nodes receiving data from the second node; and

in response to determining that one or more other notices have been received from other nodes receiving data from the second node, indicate that a cause of the anomaly is at least one of the second node or a data path to the second node in the computer network.

7. The computing system of claim 6, wherein the program instructions that when executed by the one or more processors further cause the one or more processors to:

in response to determining that one or more other notices have not been received from other nodes receiving data from the second node, indicate that a cause of the anomaly is the data path to the second node in the computer network.

8. The computing system of claim 6, wherein the program instructions that when executed by the one or more processors further cause the one or more processors to:

in response to determining that one or more other notices have been received from other nodes receiving data from the second node,

determine whether the one or more other nodes and the first node are on different data paths to the second node in the computer network; and

in response to determining that the one or more other nodes and the first node are on different data paths to the second node in the computer network, indicate that a cause of the anomaly is the second node.

9. The computing system of claim 6, wherein the program instructions that when executed by the one or more processors further cause the one or more processors to:

in response to determining that one or more other notices have been received from other nodes receiving data from the second node,

determine whether the one or more other nodes and the first node are on different data paths to the second node in the computer network; and

in response to determining that the one or more other nodes and the first node are not on different data paths to the second node in the computer network, indicate that a cause of the anomaly is at least one of the second node or a data path to the second node.

10. A method for detecting anomalies in a computer network in which a plurality of publishers publish data and a plurality of subscribers subscribe to published data via network routes in the computer network defined to satisfy corresponding expected quality of service (“

QoS”

) of the individual subscribers, the method comprising;

under control of one or more computing devices configured with executable instructions, receiving a first notice from a first node within the computer network;

determining whether the first notice corresponds to that data incoming at the first node is not being received according to an expected quality of service;

in response to determining that the first notice corresponding to that data incoming at the first node is not being received according to an expected quality of service, determining whether a second notice is received from a second node within the network indicating that data forwarded on an outgoing connection is not being forwarded according to another expected quality of service, the second node being upstream of the first node; and

in response to determining that the second notice has been received,

determining based at least in part on the first notice and the second notice that an anomaly exists within the network when the second notice has not been received;

determining whether one or more other notices have been received from other nodes receiving data from the second node; and

in response to determining that one or more other notices have been received from other nodes receiving data from the second node, indicating that a cause of the anomaly is at least one of the second node or a data path to the second node in the computer network.

11. The method of claim 10, wherein the quality of service is a measurement of at least one of a data rate, a latency, or an availability.

12. The method of claim 10, further comprising, in response to determining that the anomaly exists within the computer network:

determining an alternative data path through the computer network; and

routing the data over the determined alternative data path.

13. The method of claim 12, wherein the alternative data path is a data path with a highest available capacity.

14. The method of claim 12, wherein the alternative data path is a pre-defined alternative data path for the data.

15. The method of claim 10, further comprising:

determining a priority for the plurality of subscriptions receiving the data;

reducing a quality of service for a lowest priority subscription; and

determining that the quality of service for each of the plurality of subscriptions exceeds a minimum quality of service.

16. The method of claim 10, further comprising in response to determining that one or more other notices have not been received from other nodes receiving data from the second node, indicate that a cause of the anomaly is the data path to the second node in the computer network.

17. The method of claim 10, further comprising:

in response to determining that one or more other notices have been received from other nodes receiving data from the second node,

determine whether the one or more other nodes and the first node are on different data paths to the second node in the computer network; and

in response to determining that the one or more other nodes and the first node are on different data paths to the second node in the computer network, indicate that a cause of the anomaly is the second node.

18. The method of claim 10, wherein the anomaly is at least one of a rate failure, a QoS failure, a physical network failure, a node failure, or a path failure.

19. The method of claim 10, further comprising:

in response to determining that one or more other notices have been received from other nodes receiving data from the second node,

determine whether the one or more other nodes and the first node are on different data paths to the second node in the computer network; and

in response to determining that the one or more other nodes and the first node are not on different data paths to the second node in the computer network, indicate that a cause of the anomaly is at least one of the second node or a data path to the second node.