Distributed processing system

• US 10,379,873 B2
• Filed: 08/20/2014
• Issued: 08/13/2019
• Est. Priority Date: 02/28/2014
• Status: Active Grant

• Current Assignee: Tyco Fire & Security GmbH (Johnson Controls International plc)
• Original Assignee: Tyco Fire & Security GmbH (Johnson Controls International plc)
• Inventors: Leon, Gustavo, Hall, Stewart E., Trivelpiece, Craig, Rasband, Paul B.
• Primary Examiner(s): Parry, Chris
• Assistant Examiner(s): Abderrahmen, Chouat
• Application Number:
  US14/464,091
• Publication Number:
  US 20150249588A1
• Time in Patent Office: 1,819 Days
• Field of Search: 3405721, 340 101, 3405681, 3405727, 3405728, 3405729, 340506, 340514, 340577, 3406918, 3405724, 3406911, 340 103, 340 105, 340571, 340540, 3405723, 340628, 340 102, 3405725, 34081545, 340 104, 340 57, 3406861, 340505, 3405722, 3408154, 340 1042, 340501, 340541, 3405685, 340 1034, 340 1051, 340 1052, 340 106, 340 24, 34053911, 34053926, 34053927, 3405726, 709206, 709204, 709208, 709220, 709224
• CPC Class Codes: A61B 17/00 Surgical instruments, devices or methods, e.g. tourniquets A61B18/00 takes precedence; contraceptive devices, pessaries, or applicators therefor A61F6/00; eye surgery A61F9/007; ear surgery A61F11/00
• CPC Class Codes: G01S 13/765 with exchange of information between interrogator and responder
• CPC Class Codes: G01S 13/876 Combination of several spaced transponders or reflectors of known location for determining the position of a receiver G01S13/874 takes precedence
• CPC Class Codes: G01S 5/0236 Assistance data, e.g. base station almanac
• CPC Class Codes: G01S 5/0284 Relative positioning
• CPC Class Codes: G01S 5/0295 Proximity-based methods, e.g. position inferred from reception of particular signals
• CPC Class Codes: G06F 8/63 Image based installation; Cloning; Build to order
• CPC Class Codes: G06F 9/4416 Network booting; Remote initial program loading [RIPL]
• CPC Class Codes: G07C 9/27 with central registration
• CPC Class Codes: G08B 13/19608 Tracking movement of a target, e.g. by detecting an object predefined as a target, using target direction and or velocity to predict its new position
• CPC Class Codes: G08B 13/19613 Recognition of a predetermined image pattern or behaviour pattern indicating theft or intrusion
• CPC Class Codes: G08B 13/19634 Electrical details of the system, e.g. component blocks for carrying out specific functions
• CPC Class Codes: G08B 13/19671 Addition of non-video data, i.e. metadata, to video stream
• CPC Class Codes: G08B 13/19697 Arrangements wherein non-video detectors generate an alarm themselves
• CPC Class Codes: G08B 25/007 Details of data content structure of message packets; data protocols
• CPC Class Codes: G08B 25/009 Signalling of the alarm condition to a substation whose identity is signalled to a central station, e.g. relaying alarm signals in order to extend communication range
• CPC Class Codes: G08B 29/181 due to failing power supply
• CPC Class Codes: G08B 29/188 Data fusion; cooperative systems, e.g. voting among different detectors
• CPC Class Codes: G08B 7/062 indicating emergency exits
• CPC Class Codes: G08B 7/066 guiding along a path, e.g. evacuation path lighting strip
• CPC Class Codes: H04L 12/4625 : Single bridge functionality, e.g. connection of two networks over a single bridge
• CPC Class Codes: H04L 12/6418 : Hybrid transport
• CPC Class Codes: H04L 2101/672 : Short addresses
• CPC Class Codes: H04L 43/0805 : by checking availability
• CPC Class Codes: H04L 43/0876 : Network utilisation, e.g. volume of load or congestion level
• CPC Class Codes: H04L 61/106 : across networks, e.g. mapping telephone numbers to data network addresses
• CPC Class Codes: H04L 61/59 : using proxies for addressing
• CPC Class Codes: H04L 67/104 : Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1051 : Group master selection mechanisms
• CPC Class Codes: H04L 67/1093 : Some peer nodes performing special functions
• CPC Class Codes: H04L 67/12 : specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/34 : involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 9/004 : for fault attacks
• CPC Class Codes: H04N 23/65 : Control of camera operation in relation to power supply
• CPC Class Codes: H04N 5/76 : Television signal recording
• CPC Class Codes: H04W 16/26 : Cell enhancers or enhancement, e.g. for tunnels, building shadow
• CPC Class Codes: H04W 24/02 : Arrangements for optimising operational condition
• CPC Class Codes: H04W 4/38 : for collecting sensor information
• CPC Class Codes: H04W 8/26 : Network addressing or numbering for mobility support
• CPC Class Codes: H04W 84/18 : Self-organising networks, e.g. ad-hoc networks or sensor networks
• CPC Class Codes: H04W 88/04 : adapted for relaying to or from another terminal or user
• CPC Class Codes: H04W 92/02 : Inter-networking arrangements
• 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
• CPC Class Codes: Y04S 40/18 : Network protocols supporting networked applications, e.g. including control of end-device applications over a network
• CPC Class Codes: Y04S 40/20 : Information technology specific aspects, e.g. CAD, simulation, modelling, system security

Abstract

Described is a system that includes a queue cluster including first network devices that cooperate to communicate with end nodes of a network and to store information from the end nodes in memory, a processing cluster comprising second network devices that cooperate to perform one or more tasks on the information from the queue cluster, and a database cluster including third network devices that cooperate to provide storage for use by the processing cluster, with the queue cluster, the processing cluster, and the database cluster being part of a local network that is connectable to an external network, the local network including a wireless mesh network and for the one or more tasks, a network device among the second network devices is selected as a leader responsible for task execution.

Claims

1. A system comprising:

a distributed queue cluster comprising a plurality of first device nodes that cooperate to;

receive messages comprising information from sensor devices over a wireless mesh network;

store the information in local memory of at least one of the first device nodes; and

wherein each of the plurality of first device nodes presents a RESTful API;

a distributed processing cluster comprising a plurality of second device nodes that cooperate to;

retrieve the information stored in the distributed queue cluster;

select a device node among the second device nodes as a leader, wherein the leader launches one or more worker routines distributed across the plurality of second device nodes, wherein the one or more worker routines comprise one or more rules to act on the information to produce processing results; and

wherein the leader launches one or more additional worker routines in response to determining a worker is over-loaded;

a distributed database cluster comprising a plurality of third device nodes that cooperate to store in local memory the processing results produced from the distributed processing cluster; and

wherein the distributed queue cluster, the distributed processing cluster, and the distributed database cluster are configured to connect to the wireless mesh network, the wireless mesh network configurable to connect to an external network, and with each of the first, second and third device nodes are configurable by assigning functional roles as either a node of the distributed queue cluster or a node of the distributed processing cluster or a node of the distributed database cluster.

2. The system of claim 1, wherein the distributed queue cluster of first device nodes, the distributed processing cluster of second device nodes, and the distributed database cluster of third device nodes are further configurable to comprise at least some devices in common.

3. The system of claim 1, wherein at least some of the functions of the first, second and third device nodes are redundant in each of the distributed queue cluster, the distributed processing cluster, and the distributed database cluster.

4. The system of claim 1, wherein the leader is a first leader and the distributed processing cluster is configured to select a second leader in response to an event associated with the first leader.

5. The system of claim 4, wherein the event comprises failure of the first leader.

6. The system of claim 1, wherein the one or more worker routines are configured to share the processing results.

7. The system of claim 1, wherein the distributed processing cluster is configured to define a maximum number of worker routines.

16. The system of claim 6, wherein sharing the processing results comprises at least one of storing the processing results in the distributed queue cluster, storing the processing results in the distributed database cluster, or passing the results to a different worker routine of the one or more worker routines.

8. A computer program product tangibly stored on one or more computer-readable hardware storage devices, the computer program product comprising instructions executable by a processor to:

cause first local device nodes to cooperate to form a queue cluster to communicate via a RESTful API with sensor end nodes (end nodes) of a wireless mesh network, receive information from the end nodes of the wireless mesh network, store the information from the end nodes in memory;

cause second local device nodes to cooperate to;

form a processing cluster to retrieve the information stored in the queue cluster;

select an end node as a leader, wherein the leader launches one or more worker routines distributed across the second local device nodes, wherein the one or more worker routines comprises one or more rules to act on the information to produce results; and

wherein the leader launches one or more additional worker routines in response to determining a worker routine is over-loaded;

cause third local device nodes to cooperate to;

form a database cluster to provide storage for the results produced from the processing cluster; and

wherein the first, the second, and the third local device nodes configured to connect to the wireless mesh network, and the wireless mesh network configurable to connect to an external network, and with each of the first, the second, and the third local device nodes configurable to be assigned functional roles as either a node of the queue cluster or a node of the processing cluster or a node of the database cluster.

9. The computer program product of claim 8, wherein the queue cluster of first local device nodes, the processing cluster of second local device nodes, and the database cluster of third local device nodes all comprise at least some devices in common.

10. The computer program product of claim 8, wherein at least some of the functions of the first, second and third local device nodes are redundant in each of the queue cluster, the processing cluster, and the database cluster.

11. The computer program product of claim 8, wherein the leader is a first leader and the processing cluster is configured to select a second leader in response to an event associated with the first leader.

12. The computer program product of claim 11, wherein the event comprises failure of the first leader.

13. The computer program product of claim 8, wherein the one or more worker routines are configured to share the processing results.

14. The computer program product of claim 8, wherein the processing cluster is configured to define a maximum number of worker routines.

17. The system of claim 13, wherein sharing the processing results comprises at least one of storing the processing results in the queue cluster, storing the processing results in the database cluster, or passing the results to a different worker routine of the one or more worker routines.

15. A method, comprising:

configuring local nodes as first local device nodes to form a distributed queue cluster, second local device nodes to form a processing cluster, and third local device nodes to form a database cluster, with any of the first, second and third local device nodes configurable to be assigned functional roles as either a node of the distributed queue cluster or a node of the processing cluster or a node of the database cluster;

receiving information from sensor end nodes (end nodes) over a wireless mesh network by the distributed queue cluster, the distributed queue cluster communicating with the end nodes using a RESTful API, which stores the information from the end nodes in memory;

performing one or more tasks on the information from the distributed queue cluster by the processing cluster that selects a node among the second local device nodes as a leader, wherein the leader retrieves information stored in the distributed queue cluster and launches one or more worker routines to process the information to produce processing results;

storing the processing results from the processing cluster in the database cluster; and

wherein the leader launches one or more additional worker routines in response to determining a worker is over-loaded; and

connecting the first local device nodes, the second local device nodes, and the third local device nodes to the wireless mesh network and the wireless mesh network configurable to connect to an external network.

18. The method of claim 15, wherein the distributed queue cluster of the first local device nodes, the processing cluster of the second local device nodes, and the database cluster of the third local device nodes are further configurable to comprise at least some nodes in common.

19. The method of claim 15, wherein the leader is a first leader and the processing cluster is configured to select a second leader in response to an event associated with the first leader.

20. The method of claim 19, wherein the event comprises a failure of the first leader.