Managing malfunction reports using death signals

Abstract

The outage is detected by a first node at layer N of the multi-layer mesh network, which is in communication with a root node via the mesh network. After waiting for an outage duration to expire, the first node waits for a layer-specific time interval based on a topology of the second layer. The first node receives a death signal from a second node at layer N+1 of the multi-layer mesh network. The death signal includes an identifier for the second node and an indication of layer N+1. After the layer-specific time interval expires, the first node transmits a combined death signal including an identifier for the first node, an indication of layer N, an identifier for the second node, and an indication of layer N+1.

Description

[Technical field]

[0001] The present disclosure relates generally to managing outage reports in a mesh network. More specifically, but not by way of limitation, the present disclosure relates to managing outage reports using one or more last gasps in a mesh network to transmit outage information. [Background technology]

[0002] Some resource providers utilize mesh networks to provide a communication platform for various networked nodes. For example, resource providers such as utility companies, home automation, industrial monitoring, or scientific application providers may monitor the networked nodes via the mesh network. In some cases, network malfunctions may be managed by reporting such events using a death signal. Summary of the Invention [Problem to be solved by the invention]

[0003] The present disclosure provides for management of malfunction reports using end-of-life signals. [Means for solving the problem]

[0004] The disclosed system and method provide communication techniques in a mesh network. A device located in a premises may include a node. The node may be connected to a network with a number of other nodes and may communicate with a central system via the mesh network. The device may be configured to detect and report network outages using a death signal in the network. Furthermore, the device can reliably relay reports of network outages across the mesh network, ensuring that network outages are reported even from the outermost edge of the mesh network. The device transmits the death signal towards a collector using intelligent processing and filtering, and different timings associated with different network layers.

[0005] The present disclosure includes a malfunction management system relaying reporting information to a head end using a death signal. The death signal reports information about a node experiencing a malfunction condition. After a malfunction duration, the reporting node receives one or more death signals from nodes in the mesh network. Also, if the reporting node itself is experiencing a malfunction condition, the reporting node generates an aggregated death signal including the one or more death signals and its own death signal information. The reporting nodes transmit the aggregated death signal according to their respective scheduled death signal times directed to the head end. Thus, certain aspects described herein improve reporting of malfunction conditions across a mesh network.

[0006] One exemplary method for reporting outage information in a multi-layer mesh network includes: detecting, by a first node at a layer N of the multi-layer mesh network, a malfunction condition; waiting a predetermined malfunction duration after detecting the malfunction condition; continuing to wait for a layer-specific time interval based on the topology of layer N after the predetermined outage duration expires; receiving a death signal from a second node in layer N+1 of the multi-layer mesh network, the death signal including a second identifier for the second node and an indication of layer N+1; and transmitting, after expiration of the layer-specific time interval, an integrated death signal including a first identifier for the first node, an indication of layer N, a second identifier for the second node, and an indication of layer N+1. In some example methods, reception of end-of-life signals from other layers may begin at the end of the dysfunction duration and continue over a number k intervals, e.g., until each of the k intervals and their randomized periods are completed, and then a consolidated end-of-life signal may be transmitted.

[0007] Another example system includes a first node in a layer N of a multi-layer mesh network including a processor configured to execute computer-readable instructions and a memory comprising the computer-readable instructions. When executed by the processor, the computer readable instructions Detecting a malfunction condition; and waiting a predetermined malfunction duration after detecting the malfunction condition; continuing to wait for a layer-specific time interval based on the topology of layer N after the predetermined outage duration expires; receiving a death signal from a second node in layer N+1 of the multi-layer mesh network, the death signal including a second identifier for the second node and an indication of the layer N+1 identifier; The method is configured to cause the processor to perform operations including transmitting, before expiration of the layer-specific time interval, an integrated death signal including a first identifier for the first node, an indication of layer N, a second identifier for the second node, and an indication of layer N+1. In some example systems, reception of end-of-life signals from other layers may begin at the end of the dysfunction duration and continue over a number k intervals, e.g., until each of the k intervals and their randomized periods are completed, and then a consolidated end-of-life signal may be transmitted.

[0008] These and other features, aspects, and advantages of the present disclosure will be better understood when the following detailed description is read in conjunction with the accompanying drawings. [Brief description of the drawings]

[0009] [Figure 1] 1 illustrates an example network environment for reporting malfunctions using a death-line signal in a mesh network, in accordance with certain aspects of the present disclosure. [Diagram 2] 1 illustrates a death signal packet and an aggregated death signal for reporting a malfunction using a death signal in a mesh network, according to certain aspects of the present disclosure. [Diagram 3] 1 illustrates example network communications in a network environment for reporting malfunctions using a death-line signal in a mesh network in accordance with certain aspects of the present disclosure. [Figure 4] 1 illustrates an example node according to certain aspects of the present disclosure. [Diagram 5] 1 illustrates an example method for reporting a malfunction using a death-line signal in a mesh network according to certain aspects of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Aspects of the present disclosure use a death signal to report an outage in a mesh network. Additional aspects of the present disclosure may improve the likelihood of effectively reporting an outage using one or more death signals in a mesh network. Certain aspects of the present disclosure include using a death signal to report network outage information. The following non-limiting examples are provided to introduce certain aspects of the present disclosure.

[0011] Some existing outage management solutions process a single death signal for an endpoint experiencing an outage condition that immediately causes it to cease operation. Some existing outage management solutions may have limitations in the case of large-scale or total network outages. For example, nodes that do not have a direct connection to devices that are still powered and connected to the headend may not report their particular outage. Furthermore, some existing outage management solutions may fail to report network outages from nodes that still have connections to powered nodes, even if their remaining connections are sufficient to operate as expected. Thus, there is a need for existing outage management solutions to improve the execution of outage reporting events.

[0012] Certain aspects described herein can achieve improved performance results with respect to outage reporting events. Some aspects of the present disclosure can eliminate reporting of false positive outage events. Additionally, some aspects can minimize or eliminate modifications to the headend. Other aspects utilize currently available hardware. In doing so, certain aspects are applicable to multiple versions of RF mesh protocols, multiple layers, and / or multiple families of meters.

[0013] In one embodiment, the failure management system relays the reporting information to the headend using a death signal. For example, the death signal can ensure that all endpoints experiencing a failure condition (e.g., loss of power) transmit their death signal after calculating the outage duration. The outage duration is added to a time interval that depends on the topological layer in which the particular endpoint resides in the mesh network. The outage duration may be substantially the same for all nodes in the mesh network. Furthermore, all nodes may receive a death signal from the network, starting immediately after the completion of the calculated outage duration. Each node continues to receive the death signal until it transmits its own death signal.

[0014] Each node experiencing a malfunction condition concatenates and transmits multiple death signals (e.g., an aggregated death signal or a composite death signal) to relay the malfunction information. The aggregated death signal or composite death signal may include a common header, a malfunction header, a malfunction message, and node IDs from one or more nodes experiencing the malfunction condition. The malfunction condition may include a loss of power. In some embodiments, the malfunction condition may include other conditions, such as determining that a node is about to be unable to continue to operate properly. Additionally, the receiving node may receive this malfunction information regarding one or more nodes experiencing a malfunction condition in the form of a death signal packet from each of the one or more nodes. The receiving node may receive the malfunction information in the form of one or more death signal packets, an aggregated death signal, or more than one aggregated death signal.

[0015] Continuing with this embodiment, each node experiencing a malfunction condition transmits an aggregated death signal according to their respective scheduled death signal time. Each node experiencing a malfunction condition begins transmitting an aggregated death signal beginning at a scheduled death signal time based on a predetermined malfunction duration and its layer-specific time interval (e.g., based on the topological layer in which the particular node resides within the mesh network). Each node with power processes the aggregated death signals and converts them into a malfunction message destined for the head end. In some embodiments, the death signal may be optimized based on the length of the predetermined malfunction duration, the length of the layer-specific time interval, the amount of energy reserves associated with the node, or a combination thereof. Certain aspects described herein enhance reporting of various malfunction conditions across a multi-layer mesh network to one or more collectors, such as a powered root node or a head end.

[0016] Example Operating Environment The present disclosure may operate within a node of a network that includes the capability to communicate a terminal signal. Figure 1 illustrates an example network environment 100, including a mesh network (e.g., a radio frequency ("RF") mesh network, a powerline communication ("PLC") network, a channel hopping mesh network, a time-slotted channel hopping ("TSCH") mesh network, a wireless smart ubiquitous network ("Wi-SUN"), a Wi-SUN field area network ("Wi-SUN FAN"), a non-synchronized mesh network, etc.). Network environment 100 includes a root node 106 and nodes 110, 112, 114, 116, 118, 120, 122, 124, 126, 128, 130, 132, 134, 136, 138, 140, 142, and 144, each of which may be in communication with a headend 104 via a communications network 102.

[0017] The headend 104 communicates with the root node 106 and the nodes 110-144 via the communications network 102. The communications network 102 may include a telephone network, a wireless telephone network, a wireless personal area network ("WPAN"), a local area network ("LAN"), a wide area network ("WAN"), a metro area network ("MAN"), other data network, or any other suitable communications network. In some embodiments, the headend 104 may provide centralized control for the mesh network via the communications network 102.

[0018] The headend 104 may distribute network information using various types of communication signals. The headend 104 may communicate network information using RF signals, global system for mobile communications (GSM) signals, low power radio ("LPR") signals, media independent signals, consumption signals, other suitable electrical signals, etc. In some embodiments, the headend 104 may provide monitoring services (e.g., regarding outages, uptime, or health status), geographic information, data collection (e.g., regarding meter data, connectivity, quality of service, etc.), scheduling information, other operational information, etc. The headend 104 may be capable of sending messages or notifications to various network components, such as the root node 106 and the nodes 110-144.

[0019] The network environment 100 also includes a root node 106. The root node 106 facilitates communication across the network environment 100. The root node 106 includes a collector 108 (e.g., a collector node, a collector radio, or other data collection device). The collector 108 may receive data from the nodes using an integrated antenna. The collector 108 may also include a collector ID and may communicate with the headend 104. The root node 106 resides in a first layer (e.g., layer 1) of a mesh network in the network environment 100.

[0020] The root node 106 may be a PAN coordinator, a border router, a gateway router, an external router, or any other suitable gateway device. Additionally, the root node 106 may maintain network information for the nodes 110-144 in the network environment 100. The root node 106 may also include data storage, energy storage, memory, other data repositories, etc., that contain the network information. Such network information may include lists of node IDs, network IDs, network topology (e.g., including network layers), network information for any number of connected devices (e.g., asynchronous unicast schedules for the nodes 110-144), broadcast schedules, other network characteristics, combinations thereof, etc. The root node 106 may be continuously maintained as a powered node.

[0021] Network environment 100 further includes nodes 110-144. Node 110 is a parent node to child nodes 114, 116. Similarly, node 110 is a grandparent node to grandchild nodes 120, 122. Nodes 110 and 112 reside at layer 2 of the mesh network, each of which is a child node of and communicates with root node 106. Nodes 110 and 112 share a common layer-specific time interval because both nodes reside at the same topological layer (e.g., layer 2) within the mesh network.

[0022] Nodes 114, 116, and 118 have the same layer-specific time interval, which is calculated based on topological features of layer 3. Layer 4 includes nodes 120-124, each having the same layer-specific time interval. Similarly, layer N-1 includes nodes 126-134, each having the same layer-specific time interval, layer N includes nodes 136-144, each having the same layer-specific time interval, etc. It should be appreciated that while each of the nodes in a particular layer may share the same layer-specific time interval, each of the layers may have different layer-specific time intervals based on unique topological features.

[0023] Each node 110-144 may reside in its respective layer (e.g., layer 2, 3, 4, N-1, or N) and may have a different death signal interval. The death signal interval may vary based on a predetermined outage duration (e.g., a predetermined outage duration of 30 seconds). In some embodiments, the predetermined outage duration is followed by a quasi-random time interval (e.g., a predetermined duration measured in milliseconds ("ms")). This quasi-random time interval may also vary depending on one or more capabilities of a given node. These capabilities may include the amount of stored energy, the efficiency of one or more processors, available storage capacity, etc. The predetermined outage duration may be dictated by the headend 104 or the root node 106.

[0024] The network environment 100 includes a failure management system that relays reporting information to the root node 106 and / or the headend 104 using a death signal. The death signal may be implemented to ensure that all endpoints experiencing a failure condition transmit their death signal after calculating a predetermined failure duration. The failure duration is added to a layer-specific time interval that depends on one or more configuration parameters, such as topological features associated with the layer in which the node resides. The death signal may use a randomization factor such that multiple nodes in the same layer transmit their death signals at different times within the layer-specific time interval.

[0025] The length or duration of the death signal interval may be "adjusted" according to the needs of the resource provider, for example, by modifying one or more of the layer-specific time interval configuration parameters. The configuration parameters may include a predetermined outage duration length, a value of a coefficient associated with a given layer topology used to calculate the layer-specific time interval, the layer in which the node resides, a maximum number of death signal packets, aggregated death signal, or other outage messages, or other suitable configuration parameters. The configuration parameters may be updated without performing a firmware update. For example, the configuration parameters may be transmitted over-the-air ("OTA") to the nodes. Additionally, either the headend 104 and the root node 106 may transmit such changes to the configuration parameters to the nodes 110-144.

[0026] 2 illustrates an embodiment of a death signal 200, including a death signal packet 202 and an integrated (composite) death signal 204. Death signal packet 202 includes a failure header 206, a node layer 208, and a node ID 210. Death signal packet 202 has a total packet size of 13 bytes and includes a death signal information field that includes the failure header 206 (4 bytes), the node layer 208 (1 byte), and the node ID 210 (8 bytes).

[0027] The outage header 206 includes information regarding the outage condition. For example, the outage header 206 may include an alarm, alert, or other notification indicating the type of outage condition. The outage header 206 may include an indication of a state change or timing information associated with the outage condition. The node layer 208 is a terminal signal information field that includes an indication of the network layer at which the outage condition occurred (e.g., a network layer identifier). For example, the node layer 208 may indicate the network layer or other location information corresponding to the node experiencing the outage condition.

[0028] Node ID 210 is a death signal information field that contains information for reporting the failure of a node experiencing a failure condition (e.g., a dead node). Either the failure header 206 or the node ID 210 may contain a description of the failure condition, the ID of the node experiencing the failure condition, or a timestamp corresponding to the time of the failure condition (e.g., indicating the time when a power outage occurred), etc. In additional or alternative embodiments, both the failure header 206 and the node ID 210 may contain a predetermined amount of redundant failure information to ensure delivery of notification of the failure condition.

[0029] The failure header 206 of the death signal packet 202 may also include header fields such as a physical layer ("PHY") header, a medium access control ("MAC") layer header, an Internet Protocol ("IP") header, a ("UDP") header, an application header, etc. In one embodiment, the failure header 206 includes a PHY header and a MAC layer header. These header fields may be used to indicate the type of packet (e.g., that the packet is a death signal packet 202). Additionally, a receiving node may use such header fields to determine the need to parse the death signal packet 202 using a particular format or decoding technique.

[0030] It should be appreciated that the death signal packet 202 may include any number of additional information fields. Similarly, the death signal packet 202 need not be limited to 13 bytes and may include any suitable amount of data. The structure of the death signal packet 202 may be simplified or the overall size of the death signal packet 202 may be reduced to minimize the amount of power and / or energy required by a node experiencing a malfunction condition to generate and transmit the death signal packet 202.

[0031] The consolidated dying signal 204 includes information regarding the failure condition. For example, the consolidated dying signal 204 includes a failure header 212, a dying signal 1 214, a dying signal 2 216, a dying signal 3 218, and a dying signal N 220. The failure header 212 has a length of 4 bytes and may include substantially similar information as the failure header 206 (e.g., header fields, a description of the failure condition, an ID of the node experiencing the failure condition, and / or a timestamp associated with the failure condition, etc.). Each of the dying signals 214-220 has a length of 13 bytes. Additionally, each of the dying signals 214-220 may include substantially similar information and / or structure as the dying signal packet 202 described above.

[0032] For example, a node (e.g., node 116) may transmit an aggregated end-of-life signal 204 that includes end-of-life signal 1 214 that itself represents end-of-life signal packet 202. Node 116 may also transmit an aggregated end-of-life signal 204 that includes end-of-life signal 2 216 from node 120, end-of-life signal 3 218 from node 126, and end-of-life signal N 220 from node 128. Each of these end-of-life signals 216-220 in the aggregated end-of-life signal 204 may include concatenated end-of-life signal packets 202 from nodes 120, 126, and 128, respectively.

[0033] Each consolidated dying signal 204 may include a maximum number of dying signals (e.g., dying signal 1 214, dying signal 2 216, dying signal 3 218, dying signal N 220, etc.). Each consolidated dying signal 204 may also include a maximum number of node IDs. In one embodiment, a single consolidated dying signal 204 may include up to 12 node IDs. A single consolidated dying signal 204 may include the contents of 12 dying signal packets 202 (e.g., each of the 12 dying signal packets 202 includes one or more dysfunction headers 206, node layers 208, and / or node IDs 210). In some embodiments, a node transmits a dying signal that includes one or more dying signal packets 202, consolidated dying signals 204, or both. It should be appreciated that any suitable communication protocol or format may be used to transmit and receive one or more dying signals.

[0034] FIG. 3 illustrates an example network communication in a network environment 300 for reporting malfunctions using a death signal in a mesh network. One or more operations described with respect to FIG. 3 include communicating in a mesh network (e.g., network environment 100). Network environment 300, like network environment 100, facilitates communication between various network devices (e.g., head end 104, root node 106, nodes 110-144, 400, etc.) according to aspects described herein. The communication devices (e.g., nodes 106, 110-144, or 400) perform the operations illustrated in FIG. 3 by executing appropriate program code (e.g., software components associated with death signal packet 202, integrated death signal 204, etc.). For illustrative purposes, network environment 300 is described with reference to certain implementations shown in the drawings. However, other implementations are possible.

[0035] The network environment 300 exhibits predetermined outage durations for a wide range of network outages, including outages and durations 302. The outages and durations 302 may be determined in a manner similar to that described above with respect to the predetermined outage durations of FIG. 1. Similar to the multi-layer mesh network shown in FIG. 1, the network environment 300 includes several layers, layer N, layer N-1, layer N-2, layer 4, layer 3, layer 2, and collector layer 1. The network environment 300 also includes various layer-specific time intervals 304-316 corresponding to each of the layers in the multi-layer mesh network. Each of the layer-specific time intervals 304-316 corresponds to five layers in the multi-layer mesh network. In some embodiments, the death signal packet 202 and / or the aggregated death signal 204 are transmitted during the layer-specific time intervals 304-316.

[0036] In a simplified embodiment, multiple nodes experience an outage condition. One node in layer N (e.g., node 136) experiences an outage condition that includes a loss of power. In response to detecting the loss of power, node 136 waits for a predetermined outage duration. The predetermined outage duration may be dictated by the root node 106 or the headend 104. In other embodiments, node 136 calculates the predetermined outage duration based on its available resources (e.g., based on a backup battery power source). Node 136 waits for the predetermined outage duration, which is shown in FIG. 3 as expiring at outage and duration 302.

[0037] Each of the lines between layers represents the transmission of a death signal from a node at a particular layer to other nodes in the network. After the malfunction and duration 302 has passed, node 136 broadcasts a death signal packet (e.g., death signal packet 202) that is received by a layer N-1 node (e.g., node 126) during a layer-specific time interval 304 (e.g., based on the topography of layer N). Node 136 may transmit death signal packet 202 to node 126 via broadcast, multicast, unicast, or any other suitable type of message. In additional or alternative embodiments, a node residing in a layer further away from layer 1 than layer N may transmit its own death signal during the same layer-specific time interval 304 used by the layer N node.

[0038] Node 126 receives malfunction information, including a death-death signal packet 202, from node 136. Node 126 also experiences a malfunction condition. In response, node 126 generates an aggregated death-death signal (e.g., aggregated death-death signal 204) that includes the malfunction information from node 136 along with its own malfunction information (e.g., having the form of other death-death signal packets 202). Node 126 relays the aggregated death-death signal 204 during a layer N-1 specific time interval 306.

[0039] The mesh network may include any number of additional layers, such as layer N-2. Each of these additional layers may include their own particular layer-specific time interval. For example, node 120 receives the consolidated death-death signal 204 with malfunction information forwarded by the nodes during previous layer-specific time intervals (e.g., layer-specific time intervals 304, 306, 308, etc.). A layer 4 node (e.g., node 120) receives the consolidated death-death signal 204 with malfunction information for nodes 126 and 136 during layer-specific time interval 310. Node 120 relays the consolidated death-death signal 204 to a layer 3 node (e.g., node 116) during layer-specific time interval 312. Similarly, node 116 relays the consolidated death-death signal 204 to a layer 2 node (e.g., node 110) during layer-specific time interval 314. The node 110 transmits the consolidated terminal signal 204 to a collector layer 1 node (eg, the root node 106 ) during the layer-specific time interval 316 .

[0040] The first layer-specific time interval 304 includes two solid lines each representing a transmission of a death signal from a layer N node to a layer N-1 node. Similarly, while waiting for the expiration of the second layer N-1 specific time interval 306, four solid lines represent transmissions from four nodes in layer N-1 to a node in layer N-2, each of which is experiencing an outage condition. Additionally, the second layer N-1 specific time interval 306 includes a dotted line representing a death signal from one of the nodes experiencing an outage condition, the death signal being received by a layer 4 node. For example, in some mesh networks, a layer 4 node may listen and capture communications from a given node in layer N-1. In additional or alternative aspects, the layer 4 node may receive a death signal based on physical proximity from layer N-1 to the transmitting node. The third layer N-2 specific time interval 308 represents the ability to use any suitable number of layers and corresponding layer-specific time intervals.

[0041] The Layer 4 node receives four death-death signals during layer-specific time interval 310. The Layer 3 node receives four death-death signals during layer-specific time interval 312. During layer-specific time interval 312, the Layer 2 node also receives two death-death signals, represented by dashed lines, from the Layer 4 node. Subsequently, during layer-specific time interval 314, the Layer 2 node receives four death-death signals, represented by solid lines, from one or more Layer 3 nodes.

[0042] Because the layer 2 node previously received two of the death-death signals from the layer 4 node (e.g., during layer-specific time interval 312), the four death-death signals received during layer-specific time interval 314 from one or more layer 3 nodes may include some overlapping death-death signals. The four death-death signals include at least two overlapping death-death signals. The at least two overlapping death-death signals may include more than two overlapping death-death signals if the overlapping death-death signals include the consolidated death-death signal 204. Although the layer 2 node gets two death-death signals during layer-specific time interval 312 and four death-death signals during layer-specific time interval 314, the layer 2 node waits to transmit the consolidated death-death signal 204 until the expiration of its own death-death signal interval (e.g., the sum of all of the layer-specific time intervals prior to the outage and duration 302 + the layer-specific time interval 314, i.e., the outage and duration 302 + the layer-specific time interval 304-314).

[0043] During the layer-specific time interval 314, a collector layer 1 node (e.g., root node 106) receives two terminal signals from one or more layer 3 nodes. Finally, during the layer-specific time interval 316, root node 106 receives five terminal signals from one or more layer 2 nodes, which may also include overlapping terminal signals (e.g., at least two overlapping terminal signals as described above) received during the layer-specific time interval 314. As described more particularly below with respect to FIG. 5, each of the nodes receiving overlapping terminal signals across multiple layers may de-duplicate these terminal signals before, during, or after generating the consolidated terminal signal 204.

[0044] Example Node 4 illustrates an exemplary node 400. Some or all of the components of the exemplary node 400 may belong to one or more of the nodes of FIG. 1 (e.g., nodes 106 and 110-144). The node 400 includes a communications module 402, a metering module 404, and a power source 406, each of which are connected via a local or serial connection. The communications module 402, the metering module 404, and the power source 406 may be communicatively connected via a bus.

[0045] The node 400 includes a communications module 402. The communications module 402 provides functionality for sending and receiving various messages to other nodes in the network environment 100. For example, the communications module 402 sends and receives messages such as end-of-life signal packets 202, aggregated end-of-life signals 204, other malfunction messages, or network communication messages. The communications module 402 includes a communications device 408, a processor 412, and a memory 416.

[0046] The communications device 408 may include an antenna, a radio device, or any other device providing suitable wireless or wired communications. In one embodiment, the communications device 402 includes a transceiver device, such as an RF transceiver, capable of transmitting and receiving RF communications from other nodes in the network environment 100. The transceiver may include an antenna, be communicatively coupled, or be physically connected, and the transceiver may be used to transmit and receive communications over the network (e.g., communications with other nodes, such as unicast messages or broadcast messages).

[0047] The processor 412 controls the functions performed by the communication module 402, including one or more operations described herein. The processor 412 may include a microprocessor, an application-specific integrated circuit ("ASIC"), a state machine, a field programmable gate array ("FPGA"), or other suitable computing device. The processor 412 may include any number of computing devices and may be communicatively connected to a computer-readable medium, such as a memory 416. The processor may execute computer-executable program instructions or access information stored in memory to perform the operations described herein. The instructions may include processor-specific instructions generated by a compiler and / or interpreter from code written in any suitable computer programming language. When the instructions are executed, they may configure the node 400 to perform any of the operations described herein.

[0048] The memory 416 may be utilized to store data used by the processor 412 to perform various functions. The memory 416 may store information regarding a particular meter, layer, or malfunction information in the node 400. Other information and configuration may be stored in the memory. The memory may be a computer readable medium, and in addition to storing information and configuration, may store computer executable instructions that, when executed, may configure the communications module to perform the operations described herein.

[0049] The node 400 also includes a metering module 404. The metering module 404 includes a measuring device 410, a processor 414, and a memory 418. The metering module 404 provides the functionality required for the node 400 to manage resources. The metering module 404 may provide access to the resources and may be used to measure the amount of the resource being consumed. For example, the measuring device 410 includes a meter. The measuring device 410 may use a meter to measure the consumption of a resource such as gas, electricity, or water in a premises. The meter may be included in the node 400, which transmits the consumption information to a central or head-end system.

[0050] The metering module 404 may also include additional components, such as metering components, which may include one or more metering devices 410, metering applications or software components, metering scripts, sensors, metering circuitry, etc. Additionally, a central system (e.g., headend 104) may analyze the consumption information to manage resources on the premises and to manage other aspects of the system.

[0051] The processor 414 in the instrumentation module 404 controls the functioning of the instrumentation module 404 by executing computer-executable program instructions or accessing information stored in memory to perform the operations described herein. The memory 418 stores data needed by the processor 414 to perform these operations. The processor 414 and memory 418 may include all of the capabilities described above with respect to the processor 412 and memory 416.

[0052] The node 400 also includes a power source 406. The power source 406 provides power to the components of the node 400. The power source 406 may include an A / C power source or a low energy source such as a battery. The power source 406 is connected to and configured to continuously power the communications module 402 and the metering module 404. The communications module 402, the metering module 404, and the power source 406 may be configured to communicate state information over the local connection. For example, the communication state information may include shared performance data, such as power state data of the node 400.

[0053] The power source 406 may be capable of storing energy. In the event of a power outage (e.g., when the power source 406 experiences a failure), the power source 406 may provide a predetermined amount of stored energy (e.g., energy stored in a capacitor of the power source 406) to the communications module 402 and / or the measurement module 404 to enable the performance of the operations described herein. The power source 406 is also configured to provide a sufficient amount of stored energy to power the node 400 during a malfunction condition to ensure proper shutdown of the node 400, thereby enabling the node 400 to generate and transmit, for example, a death signal packet 202, an integrated death signal 204, or other malfunction messages.

[0054] Other components, connections between components, and arrangements of components other than those shown in Figure 4 are also possible. Although Figure 4 illustrates the communications module 402, the instrumentation module 404, the power source 406, the communications device 408, the measurement device 410, the processors 412, 414, and the memory 416, 418 as separate components in communication with each other, other implementations are possible. The processor 412 and the memory 416 may be included in a single component, such as a microcontroller. The systems and components discussed herein are not limited to any particular hardware architecture or configuration.

[0055] Exemplary Methods of Operation FIG. 5 illustrates an exemplary method 500 performed by a node. FIG. 5 illustrates an embodiment for reporting network outages using a death signal in a mesh network. One or more operations described with respect to FIG. 5 include communicating in a mesh network (e.g., network environment 100 or 300). Network environment 100 facilitates communication among various network devices (e.g., head end 104, root node 106, nodes 110-144, 400, etc.) according to aspects described herein. A communication device (e.g., node 400) performs the operations illustrated in FIG. 5 by executing appropriate program code (e.g., software components associated with death signal packet 202, aggregated death signal 204, etc.). For illustrative purposes, method 500 is described with reference to certain embodiments shown in the drawings. However, other embodiments are possible.

[0056] The method begins at block 502, where a node (e.g., node 110) listens for signals from other nodes. Node 110 is in communication with one or more other nodes (e.g., node 116). As discussed above with respect to FIG. 1, node 110 listens for death signals transmitted by these other nodes, among other nodes. Node 110 may listen for death signals from child nodes, grandchild nodes, etc. Node 110 listens for a death signal, a death signal packet 202, an aggregated death signal 204, or other malfunction message according to any of the techniques described herein.

[0057] At block 504, the node 110 detects a malfunction condition. For example, the node 110 may detect a power outage after receiving status or other notification information from a module (e.g., the communication module 402, the metering module 404, or the power source 406). The node 110 may detect the malfunction condition and generate a death signal packet 202. The node 110 may generate the death signal packet 202 including information about the malfunction condition. Additionally, the node 110 may generate the death signal packet 202 according to any of the techniques described herein.

[0058] The method proceeds from block 504 to block 506, where the node 110 waits for a predetermined outage duration. The node 110 waits for a predetermined outage duration after experiencing a malfunction condition itself. The predetermined outage duration begins when a malfunction condition is detected by the node 110. As previously mentioned, multiple nodes may experience their own outage conditions.

[0059] A large-scale, widespread, or total network outage may not be experienced by each of these nodes at exactly the same moment. For example, node 110 may experience an outage condition before, during, or after one or more of nodes 112-144. Typically, the outage is reported after a predetermined outage duration has elapsed. However, in some embodiments, the predetermined outage duration may begin when the first node experiences or reports the outage condition.

[0060] In alternative embodiments, the predetermined outage duration may begin when a first node in a given layer experiences or reports an outage condition. Additionally, the predetermined outage duration for each of the nodes 110-144 may vary. For example, the predetermined outage duration may vary based on one or more underlying conditions, such as the amount of network traffic, network delay, available bandwidth, number of nodes, proximity to the first node, relative position within a given layer, processing delay, transmission delay, etc.

[0061] The node 110 may wait for a predetermined outage duration defined by the headend 104. In some embodiments, the root node 106 may assign the predetermined outage duration. In other embodiments, the predetermined outage duration may be dictated by one or more capabilities of the node 110. For example, the predetermined outage duration may be determined based on an estimate of the length of time the node 110 can transmit a death signal before total failure. The predetermined outage duration may be based on the length of time remaining before a backup battery or capacitor is depleted (e.g., the stored energy of the power source 406 is drawn). The predetermined outage duration may be offset from the total discharge of the power source 406 in such a way as to ensure that the remaining energy stored in the node 110 was sufficient to generate and transmit a death signal, a death signal packet 202, an aggregated death signal 204, other outage messages, etc.

[0062] The death signal may be implemented using configuration parameters. The death signal may be tailored to the needs of the resource provider, for example, by modifying one or more configuration parameters. Modifying the configuration parameters may be used to selectively filter the death signal based on the topology of the mesh network. Advantageously, by filtering some death signals based on the topology of the mesh network, the resource provider may reduce the number of duplicated death signals. Furthermore, the resource provider may adjust the configuration parameters to minimize the number of death signals that are filtered to ensure that filtering does not falsely cause a failure to report an outage.

[0063] In one embodiment, the death signal may be implemented without modifying or updating existing firmware in node 110. The death signal may use the predetermined malfunction duration described above. Expiration of the predetermined malfunction duration may represent the time that node 110 verified a malfunction condition and / or reported the event. The predetermined malfunction duration may be 30 seconds.

[0064] At block 508, after the predetermined outage duration expires, the node 110 continues to wait for a layer-specific time interval. The layer-specific time interval is calculated based on the topology of the layer (e.g., layer 2) in which the node 110 resides. For example, the layer-specific time interval may be calculated using the following formula:

[0065] Layer-specific time interval = (k (NM)) + random(k)

[0066] where k represents a coefficient value that is adjustable according to the network layer topology, N represents the "cap" routing layer to be considered by the node (e.g., the furthest routing layer removed from layer 1 in the network topology), M represents the routing layer of the node performing this calculation (e.g., node 110), and random(k) represents a randomly selected timing offset amount. The value of random(k) may include a timing offset amount between 0 and k milliseconds. In an additional or alternative aspect, the value of random(k) may be a pseudo-random integer between 0 and an upper limit of k milliseconds.

[0067] The death signal may include additional configuration parameters. For example, the death signal may be implemented with a specified timing value k. As previously described, for the layer-specific time intervals 304-316 shown in FIG. 3, the duration of each of the layer-specific time intervals 304-316 may vary. Thus, the value of the factor k may be adjusted to modify the layer-specific time intervals (e.g., the layer-specific time intervals 304-316). In addition to being adjustable according to the topology of the network layers, the value of k may be selected to ensure a minimum duration for the layer-specific time intervals. The value of k may be optimized to ensure that the layer-specific time intervals are allocated a sufficient length of time for the nodes to process and transmit the death signal (e.g., a minimum layer-specific time interval of at least 2.5 seconds). The value of k may also be optimized to make the layer-specific time intervals sufficiently short in length to minimize the risk of high collision counts.

[0068] The death signal may also include a configuration parameter for the value of N. In some embodiments, the value of N may provide a value that sets an upper limit on the highest layer that will be used for the mesh network. In one embodiment, the value of N may be predetermined (e.g., a maximum value of 5). The maximum value of N=5 may be assigned (e.g., by the headend 104 or root node 106) based on the majority of nodes that are in (or below) layer 5 of the mesh network. Setting a maximum value for N may ensure that widespread or total network outages are accurately reported.

[0069] Advantageously, setting a maximum value of N to 5 (or less) can minimize the overall length of the death signal segment, which in turn may reduce the length of time between the occurrence of a first outage condition and receipt of an outage report by the root node 106 and / or the headend 104. Additionally, minimizing the overall length of the death signal segment may also reduce network costs by reducing the amount of stored energy required by a node (e.g., nodes 110-144). In this manner, reducing the amount of stored energy required to transmit a death signal may enable the use of a less expensive power source (e.g., power source 406). Thus, service providers may use power sources 406 that use lower cost batteries, capacitors, and the like. Certain aspects described herein may therefore improve the overall reliability of outage reporting while reducing network costs.

[0070] At block 510, node 110 receives a death signal from node 116 while waiting for a layer-specific time interval. The death signal from node 116 includes an identifier ("ID") of node 116 and layer-specific information about node 116. Node 110 generates an integrated death signal 204 that includes malfunction information from one or more additional nodes. The malfunction information may originate from one or more other nodes that reside in a different layer, the same layer, or a combination thereof.

[0071] The node 116 experiencing the malfunction condition detects a power outage within itself after receiving notification from a module within the node 114 (e.g., from the communication module 402, the metering module 404, or the power source 406). Upon detecting a power outage, the node 116 experiencing the malfunction condition initiates a proper shutdown process, such as turning off various components, saving relevant data to storage, and the like. In response to the detected power outage, the node 116 also transmits a death signal packet 202. The node 110 receives the death signal packet 202 from the node 116 during a layer-specific time interval associated with layer 2 (e.g., based on the calculations described above with respect to block 508). The node 110 may receive the death signal packet 202, the aggregated death signal 204, or other malfunction information from any number of nodes (e.g., nodes 114, 116, 120, 122, 126, 128, 130, 136, 138, 140, etc.).

[0072] The method proceeds from block 510 to block 512, where the node 110 transmits the consolidated death signal after the layer-specific time interval expires. For example, the node 110 generates the consolidated death signal 204 that includes the death signal packets 202 from the nodes (e.g., node 116) experiencing the malfunction condition. The node 110 may retrieve (e.g., from memory 416) the consolidated death signal 204 that includes the death signal packets 202 from the nodes 116.

[0073] Node 110 may then transmit the consolidated death-death signal 204 to the root node 106. Each node (e.g., nodes 110-144) may select a random time within its own layer-specific time interval to transmit the death-death signal. Additionally, node 110 may transmit the consolidated death-death signal 204 to the root node 106 via a unicast, multicast, broadcast, or any other suitable type of message.

[0074] The node 110 transmits the consolidated death signal 204 to the root node 106 with instructions to relay the malfunction information to the headend 104. If the node 110 is a powered node, the node 110 may relay the consolidated death signal 204 or other malfunction message to the headend 104 (e.g., via the root node 106). Such a powered node 110 may act as a proxy and randomize the transmission of the death signal packet 202, consolidated death signal 204, or other malfunction message to the root node 106. A powered node 110 may not follow layer-specific interval processing, although the powered node 110 may still transmit a relay message (e.g., consolidated malfunction message) to report the malfunction after receiving a death signal.

[0075] Node 110 transmits an integrated near-death signal 204 that includes malfunction information from more than two nodes (e.g., nodes 110 and 116). For example, node 110 may transmit an integrated near-death signal 204 that includes any suitable number of near-death signals. Node 110 generates the integrated near-death signal 204 using near-death signal packets 202, integrated near-death signals 204, or other malfunction information from multiple nodes at multiple different layers. Node 110 may be configured to process or ignore near-death signals received from nodes within its own layer (e.g., from node 112 at the same layer 2). Node 110 may generate the integrated near-death signal 204 by concatenating multiple near-death signals.

[0076] For example, node 110 residing in layer 2 may generate an aggregated death signal 204 that concatenates an aggregated death signal 204 from node 114 in layer 3, a death signal packet 202 from node 116 in layer 3 described above, an aggregated death signal 204 from node 120 in layer 4, and a death signal packet 202 from node 126 in layer N-1. Node 110 generates the aggregated death signal 204 that includes malfunction information from each of nodes 114, 116, 120, and 126. Node 110 may generate the aggregated death signal 204 to include an identifier (e.g., node ID 210) of each of nodes 114, 116, 120, and 126 and an indication of their respective layers (e.g., node layer 208).

[0077] The node 110 may generate the consolidated death signal 204 according to any of the techniques described herein. The node 110 may transmit a maximum number of consolidated death signals 204 (e.g., up to five consolidated death signals 204). For example, the node 110 may transmit five consolidated death signals 204 during a layer-specific time interval for layer 2. Since a single consolidated death signal 204 may include up to 12 node IDs, by transmitting five consolidated death signals 204, the node 110 reports malfunction information for up to 60 nodes.

[0078] In some embodiments, node 110 defrays one or more of the consolidated end-of-life signals 204 prior to transmission. For example, node 110 may determine a need to defray the consolidated end-of-life signal 204, which includes malfunction information (e.g., node ID 210) from each of nodes 114, 116, 120, and 126. Node 110 may determine that a end-of-life signal (e.g., consolidated end-of-life signal 204) from layer 4 node 120 includes a duplicate end-of-life signal (e.g., end-of-life signal packet 202 from layer N-1 node 126). In response, node 110 defrays the duplicate end-of-life signals prior to generating consolidated end-of-life signal 204 by removing and / or discarding copies of the duplicate messages. In additional or alternative embodiments, node 110 may defray the duplicate messages after generating consolidated end-of-life signal 204 (e.g., but prior to transmission). Additionally, node 110 may retain or remove any node IDs present in the aggregated terminal signal 204 .

[0079] Overall consideration Numerous specific details are set forth herein to provide a thorough understanding of the claimed subject matter. Those skilled in the art will understand that the claimed subject matter may be practiced without these specific details. In other instances, methods, apparatus, or systems that would be known by one of ordinary skill in the art have not been described in detail so as not to obscure the claimed subject matter.

[0080] The features described herein are not limited to any particular hardware architecture or configuration. A computing device may include any suitable device of components that provide a result conditioned on one or more inputs. Suitable computing devices include general-purpose microprocessor-based computer systems that access stored software (e.g., computer-readable instructions stored on the computer system's memory) that programs or configures the computing system from a general-purpose computing device to a specialized computing device that implements one or more aspects of the present disclosure. The software used to program or configure the computing device may use any suitable programming, scripting, or other type of language, or combination of languages, to implement the disclosure contained herein.

[0081] Aspects of the methods disclosed herein may be implemented in the operation of such a computing device. The order of the blocks presented in the above examples may be changed, e.g., the blocks may be rearranged, combined, and / or divided into sub-blocks. Certain blocks or operations may be performed in parallel.

[0082] Use of "adapted to" or "configured to" herein is intended to be open and inclusive, not excluding apparatus adapted or configured to perform additional tasks or steps. Furthermore, use of "based on" is intended to be open and inclusive, in that a process, step, calculation, or other action "based on" one or more recited conditions or values ​​may in fact be based on additional conditions or values ​​beyond those recited. Headings, lists, and numbers contained in this application are for ease of description only and are not intended to be limiting.

[0083] The foregoing description has been provided for purposes of illustrating, describing, and explaining aspects of the disclosure and is not intended to be exhaustive or to limit the disclosure to the precise forms disclosed. Further modifications and adaptations of these aspects will become apparent to those skilled in the art and may be made without departing from the scope and spirit of the disclosure. Different configurations of the components described above are possible, as are components and steps not shown and described. Similarly, some features and subcombinations are useful and may be used without reference to other features and subcombinations. Aspects of the disclosure have been described by way of example, and not by way of limitation, and alternative aspects will become apparent to readers of this patent.

Claims

1. 1. A method for reporting outage information in a multi-layer mesh network, the method comprising: detecting, by a first node at a layer N of the multi-layer mesh network, a malfunction condition; waiting a predetermined malfunction duration after detecting the malfunction condition; continuing to wait for a layer-specific time interval based on a topology of layer N after the predetermined outage duration expires; receiving a death signal from a second node at layer N+1 of the multi-layer mesh network, the death signal including a second identifier for the second node and an indication of layer N+1; transmitting, after the layer-specific time interval expires, an integrated death signal including a first identifier for the first node, an indication of layer N, a second identifier for the second node, and an indication of layer N+1. method.

2. receiving, by a powered node, the integrated end-of-life signal; transmitting, by the powered node, an aggregated malfunction message to a headend, the malfunction message including malfunction information associated with the aggregated end-of-life signal. The method of claim 1.

3. the powered node is a root node in a first layer, the root node having a collector; the method further comprising transmitting the consolidated failure message to the headend via a separate communication network after the layer-specific time interval expires. The method of claim 2.

4. receiving, by a third node at layer N-1 of the multi-layer mesh network, the integrated terminal signal; The method of claim 1.

5. the death signal includes a death signal packet including a timestamp corresponding to a time of the failure condition. The method of claim 1.

6. the malfunction condition is a first malfunction condition, the integrated end-of-life signal is a first integrated end-of-life signal, The above method is determining, by the first node, that the death signal from the second node is a second integrated death signal including a third identifier for a third node and an indication of layer N+2; determining, by the first node, a second malfunction condition of the third node based on the second integrated end-of-life signal; generating, by the first node, the first integrated end-of-life signal; the first integrated terminal signal includes a third identifier for the third node and an indication of the layer N+2. The method of claim 1.

7. the death signal is a first death signal, The above method is receiving, by the first node, a second death signal from a third node at layer N+2 of the multi-layer mesh network, the second death signal including a third identifier for the third node and an indication of layer N+2; generating, by the first node, the integrated end-of-life signal; the combined death signal includes a third identifier for the third node and an indication of the layer N+2. The method of claim 1.

8. determining, by the first node, that the second terminal signal from the third node contains a duplicate message; and prior to generating the consolidated terminal signal, de-duplicating the second terminal signal by removing copies of the duplicate messages, by the first node. The method of claim 7.

9. determining, by the first node, that the second terminal signal from the third node contains a duplicate message; and de-duplicating, by the first node, the consolidated terminal signal by removing copies of the duplicate messages. The method of claim 7.

10. and generating, by the first node, the combined end-of-life signal by combining the first end-of-life signal and the second end-of-life signal. The method of claim 7.

11. A system comprising a first node in a layer N of a multi-layer mesh network, The first node comprises: Detecting malfunctions, waiting a predetermined malfunction duration after detecting said malfunction condition; continue to wait for a layer-specific time interval based on a topology of a layer N of the multi-layer mesh network after the predetermined outage duration expires; receiving a death signal from a second node at layer N+1 of the multi-layer mesh network, the death signal including a second identifier for the second node and an indication of layer N+1; configured to transmit, after the layer-specific time interval expires, an integrated death signal including a first identifier for the first node, an indication of layer N, a second identifier for the second node, and an indication of layer N+1. system.

12. The system further comprises a third node at layer N-1 of the multi-layer mesh network; The third node comprises: receiving said integrated death signal, configured to transmit to a head end an integrated malfunction message including malfunction information associated with the integrated near-death signal; The system of claim 11.

13. the malfunction condition is a first malfunction condition, the integrated end-of-life signal is a first integrated end-of-life signal, The first node comprises: determining that the death signal from the second node is a second integrated death signal including a third identifier for a third node and an indication of layer N+1; determining a second malfunction condition of the third node based on the second integrated end-of-life signal; further configured to generate the first integrated end-of-life signal; the first integrated terminal signal includes a third identifier for the third node and an indication of the layer N+1. The system of claim 11.

14. the death signal is a first death signal, The above system is receiving a second death signal from a third node at layer N+1 of the multi-layer mesh network, the second death signal including a third identifier for the third node and an indication of layer N+1; generating said integrated end-of-life signal; the combined death signal includes a third identifier for the third node and an indication of the layer N+1. The system of claim 11.

15. determining that the second terminal signal from the third node contains a duplicate message; and before generating the combined end-of-life signal, de-duplicating the second end-of-life signal by removing copies of the duplicate messages.

15. The system of claim 14.

16. and generating the combined end-of-life signal by combining the first end-of-life signal and the second end-of-life signal.

15. The system of claim 14.

17. A first node at a layer N of a multi-layer mesh network, the first node comprising: A processor configured to execute computer readable instructions; and a memory comprising computer readable instructions. The computer readable instructions, when executed by the processor, Detecting a malfunction condition; and waiting a predetermined malfunction duration after detecting the malfunction condition; continuing to wait for a layer-specific time interval based on a topology of layer N after the predetermined outage duration expires; receiving a death signal from a second node at layer N+1 of the multi-layer mesh network, the death signal including a second identifier for the second node and an indication of layer N+1; transmitting, after expiration of the layer-specific time interval, an integrated death signal including a first identifier for the first node, an indication of layer N, a second identifier for the second node, and an indication of layer N+1. The first node.

18. the malfunction condition is a first malfunction condition, the integrated end-of-life signal is a first integrated end-of-life signal, The above operation is determining that the death signal from the second node is a second integrated death signal including a third identifier for a third node and an indication of layer N+1; determining a second malfunction condition of the third node based on the second integrated end-of-life signal; and generating the first integrated end-of-life signal; the first integrated terminal signal includes a third identifier for the third node and an indication of the layer N+2. The first node of claim 17.

19. the death signal is a first death signal, The above operation is receiving a second death signal from a third node at layer N+2 of the multi-layer mesh network, the second death signal including a third identifier for the third node and an indication of layer N+2; generating said integrated end-of-life signal; the combined death signal includes a third identifier for the third node and an indication of the layer N+2. The first node of claim 17.

20. The above operation is determining that the second terminal signal from the third node contains a duplicate message; and before generating the combined end-of-life signal, de-duplicating the second end-of-life signal by removing copies of the duplicate messages.

20. The first node of claim 19.

21. The operations further include concatenating the first end-of-life signal and the second end-of-life signal to generate the combined end-of-life signal.

20. The first node of claim 19.

22. the malfunction condition is a first malfunction condition, the death signal is a first death signal, The operation includes, during the layer-specific time interval: a second death signal from a third node at layer N+2 of the multi-layer mesh network, the second death signal including a third identifier for the third node and an indication of the layer N+2; receiving a third death signal from a fourth node at layer N+3 of the multi-layer mesh network, the third death signal including a fourth identifier for the fourth node and an indication of the layer N+3; generating said integrated end-of-life signal; the combined death signal includes a first identifier for the first node, an indication of the layer N, a second identifier for the second node, an indication of the layer N+1, a third identifier for the third node, an indication of the layer N+2, a fourth identifier for the fourth node, and an indication of the layer N+3. The first node of claim 17.

23. A first node at a layer N of a multi-layer mesh network, the first node comprising: A processor configured to execute computer readable instructions; and a memory comprising computer readable instructions. The computer readable instructions, when executed by the processor, Detecting a malfunction condition; and waiting a predetermined malfunction duration after detecting the malfunction condition; continuing to wait for a layer-specific time interval based on a topology of a layer N of the multi-layer mesh network after the predetermined outage duration expires; receiving a death signal from a second node at layer N+1 of the multi-layer mesh network, the death signal including a second identifier for the second node and an indication of layer N+1; transmitting, before the layer-specific time interval expires, an integrated death signal including a first identifier for the first node, an indication of layer N, a second identifier for the second node, and an indication of layer N+1. The first node.

Images