# US 2020/0310786 A1 · 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 2020/0310786 A1
- Document ID: US20200310786A1
- Status: Published application
- Kind: A1
- Application number: 16/829,561
- Filed: 2020-03-25
- Published: 2020-10-01
- Earliest claimed: 2019-03-26
- Assignees: Flowfinity Wireless, Inc.
- Applicants: Flowfinity Wireless, Inc.
- Inventors: Dmitry Mikhailov; Vadym Stetsiak
- Web page: https://patentgrep.com/patent/US20200310786A1

## 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 TCP/IP network;
a second controller providing network access communicating the output data over a TCP/IP network;
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.

### Claim 2 (depends on 1)

The redundant Internet-of-things control system of claim 1, wherein the synchronization 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.

### Claim 3 (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 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 conducting service state evaluations for the first and second controllers.

### Claim 5 (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 6 (depends on 1)

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

### Claim 7 (depends on 1)

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

### Claim 8 (depends on 1)

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

### Claim 9 (depends on 1)

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

### Claim 10 (depends on 1)

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

### Claim 11

A method for controlling Internet-of-things things, comprising 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.

### Claim 12 (depends on 11)

The method of claim 11, further comprising repeating the synchronization loop 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.

### Claim 13 (depends on 11)

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

### Claim 14 (depends on 11)

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

### Claim 15 (depends on 11)

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

### Claim 16 (depends on 11)

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

### Claim 17 (depends on 11)

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

### Claim 18 (depends on 11)

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

### Claim 19 (depends on 11)

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

### Claim 20 (depends on 11)

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