# US 11,436,003 B2 · Non-stop internet-of-things (IoT) controllers

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 11,436,003 B2
- Document ID: US11436003B2
- Status: Granted
- Kind: B2
- Application number: 16/829,561
- Filed: 2020-03-25
- Published: 2020-10-01
- Granted: 2022-09-06
- Earliest claimed: 2019-03-26
- Assignees: Flowfinity Wireless, Inc.
- Applicants: Flowfinity Wireless, Inc.
- Inventors: Dmitry Mikhailov; Vadym Stetsiak
- Web page: https://patentgrep.com/patent/US11436003B2

## CPC

- G06F 8/656: while running
- 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
- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 11/165: {with continued operation after detection of the error}
- G06F 11/1654: {where the output of only one of the redundant processing components can drive the attached hardware, e.g. memory or I/O}
- G06F 11/2038: {with a single idle spare processing component}
- G06F 11/3006: {where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50)}
- G06F 11/3089: {Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents (software debugging using additional hardware using a specific debug interface G06F11/3656; performance evaluation by tracing or monitoring G06F11/3466)}
- G06F 11/3466: {Performance evaluation by tracing or monitoring}
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04L 69/16: Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L 69/163: In-band adaptation of TCP data exchange; In-band control procedures
- G16Y 10/75: Information technology; Communication
- G16Y 40/40: Maintenance of things
- G16Y 40/50: Safety; Security of things, users, data or systems
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G16Y: INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]

## Abstract

Internet-of-Things (“IoT”) controllers built using hardened industrial technologies which improve functionality and reliability, such as a fixed-loop model in which a loop is repeated with configured time periodicity where sensors are queried, sensor responses are read, configured calculations are performed, and logic rules are evaluated resulting in decisions made and outputs activated. A variety of redundancy techniques are utilized to provide continuous non-stop operation of IoT controllers to compensate for possible hardware and software failures. Robust IoT controller redundancy also allows periodic maintenance, software updates and security patch installation without shutting down the IoT controllers.

## Claims

### Claim 1

A redundant Internet-of-things control system, comprising:
a plurality of Internet-of-things devices, each producing output data;
a first controller providing network access communicating the output data over a network;
a second controller providing network access communicating the output data over the network wherein the first controller and the second controller comprise processors;
wherein the first and second controllers provide the network access through a synchronization loop in which the first and second controllers change roles as a master node and a backup node to provide the network access continuously while upgrading or evaluating service states of the first and second controllers;
wherein the first controller performs the role of the master node periodically repeating the synchronization loop including querying sensors, reading sensor responses, applying logic rule, and outputting calculation and rule evaluation results;
wherein the second controller performs the role of the backup node repeating the same synchronization loop as the first controller without outputting its calculation and rule evaluation results, validates the calculation and rule evaluation results of the first controller, and if the second controller determines that the first controller has failed, initiates a failover procedure in which the second controller takes over the role of the master node, outputs its calculation and rule evaluation results, and sends a demotion signal to the first controller indicating that the first controller has been demoted to the role of the backup node; and
if the first controller is operational when it receives demotion signal from the second controller, the first controller relinquishes control of the outputs and assumes the role of the backup node.

### Claim 2 (depends on 1)

The redundant Internet-of-things control system of claim 1, wherein the first and second controllers each comprise a plurality of services, wherein each service comprises a plurality of service states and associated state rules, actions, measures and variables.

### Claim 3 (depends on 1)

The redundant Internet-of-things control system of claim 1, wherein the first and second controllers provide the network access continuously while conducting service state evaluations for the first and second controllers.

### Claim 4 (depends on 1)

The redundant Internet-of-things control system of claim 1, wherein the first and second controllers provide the network access continuously while updating service states for the first and second controllers.

### Claim 5 (depends on 1)

The redundant Internet-of-things control system of claim 1, where the first and second controllers comprise physically distinct controllers.

### Claim 6 (depends on 1)

The redundant Internet-of-things control system of claim 1, where the first and second controllers comprise physically distinct processors within a common controller.

### Claim 7 (depends on 1)

The redundant Internet-of-things control system of claim 1, where the first and second controllers comprise separate virtual machine software instances running on a common processor.

### Claim 8 (depends on 1)

The redundant Internet-of-things control system of claim 1, where the Internet-of-things devices comprise sensors.

### Claim 9 (depends on 1)

The redundant Internet-of-things control system of claim 1, where the Internet-of-things devices comprise output devices.

### Claim 10

A method for controlling Internet-of-things devices comprising a synchronization loop in which a first controller and a second controller change roles as a master node and a backup node to provide a network access continuously while upgrading or evaluating service states of the first controller and the second controller; wherein the first controller and the second controller comprising processors;
wherein the first controller performs the role of the master node periodically repeating the synchronization loop including querying sensors, reading sensor responses, applying logic rule, and outputting calculation and rule evaluation results;
wherein the second controller performs the role of the backup node repeating the same synchronization loop as the first controller without outputting its calculation and rule evaluation results, validates the calculation and rule evaluation results of the first controller, and if the second controller determines that the first controller has failed, initiates a failover procedure in which the second controller takes over the role of the master node, outputs its calculation and rule evaluation results, and sends a demotion signal to the first controller indicating that the first controller has been demoted to the role of the backup node; and
if the first controller is operational when it receives demotion signal from the second controller, the first controller relinquishes control of the outputs and assumes the role of the backup node.

### Claim 11 (depends on 10)

The method of claim 10, further comprising configuring each of the first and second controller with a plurality of services, wherein each service comprises a plurality of service states and associated state rules, actions, measures and variables.

### Claim 12 (depends on 10)

The method of claim 10, further comprising providing the network access continuously while conducting service state evaluations for the first and second controllers.

### Claim 13 (depends on 10)

The method of claim 10, further comprising providing the network access continuously while updating service states for the first and second controllers.

### Claim 14 (depends on 10)

The method of claim 10, further comprising configuring the first and second controllers as physically distinct controllers.

### Claim 15 (depends on 10)

The method of claim 10, further comprising configuring the first and second controllers as physically distinct processors within a common controller.

### Claim 16 (depends on 10)

The method of claim 10, further comprising configuring the first and second controllers separate virtual machine software instances running on a common processor.

### Claim 17 (depends on 10)

The method of claim 10, further comprising configuring the Internet-of-things devices as sensors.

### Claim 18 (depends on 10)

The method of claim 10, further comprising configuring the Internet-of-things devices as sensors output devices.
