# US 2022/0037041 A1 · Enterprise iot system for onboarding and maintaining peripheral devices

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

- Number: US 2022/0037041 A1
- Document ID: US20220037041A1
- Status: Published application
- Kind: A1
- Application number: 16/983,092
- Filed: 2020-08-03
- Published: 2022-02-03
- Earliest claimed: 2020-08-03
- Assignees: Bank of America Corporation
- Applicants: Bank of America Corporation
- Inventors: Rebbecca Nelson; Robert Cain Durbin, JR.; Chiamaka Azih; Jo-Ann Taylor; Vicky Kivuti; Angelica Barrera; Michael Robert Young; Michael Sbandi; Son Huynh; Adam Kristian King
- Web page: https://patentgrep.com/patent/US20220037041A1

## CPC

- G06F 11/0793: {Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40)}
- G06F 11/0709: {in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems}
- G06F 11/0736: {in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function (testing or monitoring of automated control systems G05B23/02)}
- G06F 21/44: Program or device authentication
- G06N 20/00: Machine learning
- G16Y 10/75: Information technology; Communication
- G16Y 20/40: relating to personal data, e.g. biometric data, records or preferences
- G16Y 40/50: Safety; Security of things, users, data or systems
- H04L 63/107: {wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04W 12/08: Access security
- H04W 12/63: Location-dependent; Proximity-dependent
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G16Y: INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Apparatus and methods for establishing a user Internet of Things (“IoT”) system is provided. The method may be performed by a central IoT hub run on a user's personal computing device. The method may include detecting user devices in electronic communication with the central IoT hub and onboarding, to the user IoT system, user devices determined to be in conformance with baseline security protocols and performance characteristics. The onboarded user device may be IoT nodes. The method may include monitoring enterprise data to pre-emptively identify and address probable failures of the IoT nodes prior to failure of the IoT nodes. The method may also include addressing known failures for each IoT node on the user IoT system.

## Claims

### Claim 1

A method for establishing and supporting a user Internet of Things (“IoT”) system, the method being performed by a central IoT hub run on a user's personal computing device, the method comprising:
detecting user devices in electronic communication with the central IoT hub;
assessing the user devices for conformance with baseline security protocols and performance characteristics;
onboarding, to the user IoT system, user devices determined to be in conformance with the baseline security protocols and performance characteristics, each of the onboarded user devices being an IoT node on the user IoT system and being associated with a device identifier;
monitoring enterprise data to pre-emptively identify and address probable failures of the IoT nodes prior to failure of the IoT nodes, the monitoring including, for each IoT node on the user IoT system:
periodically requesting, from an enterprise error database, error messages generated from devices associated with the IoT node's device identifier;
applying a machine learning model to error messages received from the enterprise database to extract a first subset of error messages, the error messages in the first subset being generated by devices positioned at a geospatial location that is within a predetermined distance of the IoT node;
in response to the identification of a threshold number of first error messages in the first subset, pulling from the enterprise error database a first remediation routine built to address the first error messages, wherein the first error messages are a group of identical error messages; and
transmitting to the IoT node the first remediation routine and instructions to run the first remediation routine, wherein the transmission is performed prior to transmission of the first error message from the IoT node to the IoT hub; and
addressing known failures for each IoT node on the user IoT system by:
receiving from the IoT node a second error message, the second error message having been generated by the IoT node and indicating a failure of the IoT node;
pulling, from the enterprise error database, second error messages generated by devices associated with the same device identifier as the IoT node, wherein the pulled second error messages are identical to the second error message generated by the IoT node;
applying the machine learning model to the pulled error data to extract a second subset of error messages from the pulled error data, the second error messages in the second subset having been generated by devices positioned at a geospatial location within the predetermined distance of the IoT node;
transmitting a first query to the enterprise error database to return a second remediation routine built to address the second error messages in the second subset;
when first query returns a second remediation routine, transmitting the second remediation routine extracted by the first query to the IoT node together with instructions to run the second remediation routine;
when the first query returns a null value, transmitting a second query to the enterprise error database to return a second remediation routine built to address the second error messages in a third subset of error messages, the third subset including the pulled second error messages less the second subset of error messages; and
when second query returns a second remediation routine, transmitting the second remediation routine extracted by the second query to the IoT node together with instructions to run the second remediation routine.

### Claim 2 (depends on 1)

The method of claim 1 wherein the detecting the user devices further comprises proactively scanning an area immediately surrounding the IoT hub for user devices.

### Claim 3 (depends on 1)

The method of claim 1 wherein the assessing the user devices for conformance with baseline security protocols and performance characteristics includes:
accessing a job description of the user stored in a central database; and
identifying the baseline security protocols and the performance characteristics, the baseline security protocols and performance characteristics being associated with the job description in the central database.

### Claim 4 (depends on 3)

The method of claim 3 further comprising:
determining that a user device is not in conformance with the baseline security protocols and performance characteristics; and
blocking communication between the user's personal computer and the user device determined not to be in conformance.

### Claim 5 (depends on 4)

The method of claim 4 wherein the determining that the user device is not in conformance includes determining that the user device includes hardware or software that the user is not allowed to use based on the accessed job description of the user.

### Claim 6 (depends on 1)

The method of claim 1 wherein the assessing the user devices for conformance with baseline security protocols and performance characteristics includes:
accessing a geospatial location of the user stored in a central database; and
identifying the baseline security protocols and the performance characteristics, the baseline security protocols and performance characteristics being associated with the geospatial location in the central database.

### Claim 7 (depends on 6)

The method of claim 6 further comprising:
determining that a user device is not in conformance with the baseline security protocols and performance characteristics; and
blocking communication between the user's personal computer and the user device determined not to be in conformance.

### Claim 8 (depends on 7)

The method of claim 7 wherein the determining that the user device is not in conformance includes determining that the user device includes hardware or software that the user is not allowed to use based on the accessed geospatial location of the user.

### Claim 9 (depends on 1)

The method of claim 1 further comprising, for each of the user devices and prior to the onboarding:
accessing a remote server to pull baseline security protocols and performance characteristics associated with the user device;
requesting, from the user device, configuration settings for a configurable setting of the user device;
identifying a discrepancy between the pulled performance characteristics and the configuration settings of the user device;
transmitting a patch to the user device to update the configuration settings and bring the configuration settings in conformance with the performance characteristics;
receiving a failure message from the user device indicating a failure of the user device to update the configuration settings; and
declining to onboard the user device to the user IoT system;
wherein:
the performance characteristics include configuration settings.

### Claim 10 (depends on 1)

The method of claim 1 further comprising:
receiving, from an IoT node included in the user IoT system, a third error message and a fourth error message; and
determining which error message to process first by:
accessing a job description of the user;
identifying, based on stored information associated with the job description, one of the third error message and the fourth error message as a higher impact error message; and
processing first the error message identified as the higher impact error message.

### Claim 11 (depends on 1)

The method of claim 1 further comprising proactively pinging each IoT node on the user IoT system to request a transfer of an error message generated by each IoT node to the IoT hub.

### Claim 12 (depends on 1)

The method of claim 1 wherein the monitoring the enterprise data to pre-emptively identify and address probable failures of the IoT nodes prior to failure of the IoT nodes further includes, for each IoT node on the user IoT system:
identifying a help desk identifier associated with the user IoT system, the help desk identifier identifying a help desk assigned to the user IoT system for remediating failures of the user IoT system;
periodically requesting, from a help desk historical database associated with the help desk identifier, error messages received by the help desk that were generated by devices associated with a device identifier identical to a device identifier of the IoT node;
in response to accumulating a threshold number of identical error messages generated within a predetermined time period, pulling from the help desk historical database a remediation routine built to remediate the identical error messages; and
transmitting, to the IoT node, the pulled remediation routine and instructions to run the pulled remediation routine.

### Claim 13 (depends on 12)

The method of claim 12 further comprising:
receiving a null value from the help desk historical database in response to the pulling of the remediation routine; and
generating a message, to the user, of a possible failure of the IoT node.

### Claim 14 (depends on 1)

The method of claim 1 further comprising, for each of the IoT nodes:
requesting the IoT node to transmit to the IoT hub customized configuration settings of the IoT node;
pinging the IoT node and not receiving a response from the IoT node;
determining, based on a lack of response from the IoT node to the pinging over a predetermined time period, that the IoT node has deleted itself from the IoT system;
detecting a new user device in electronic communication with the central IoT hub, the new user device being a similar or identical piece of hardware to the IoT node that deleted itself from the IoT system; and
when the new user device is onboarded to the IoT system and becomes a new IoT node, transmitting to the new IoT node the configuration settings and instructing the new IoT node to adopt the transferred configuration settings.

### Claim 15

A method for establishing and supporting a user Internet of Things (“IoT”) system, the method being performed by a central IoT hub run on a user's personal computing device, the user being employed in a line of business (“LOB”) in a company, the method comprising:
detecting user devices in electronic communication with the central IoT hub;
assessing the user devices for conformance with baseline security protocols and performance characteristics;
onboarding, to the user IoT system, user devices determined to be in conformance with the baseline security protocols and performance characteristics, each of the onboarded user devices being an IoT node on the user IoT system and being associated with a device identifier;
monitoring enterprise data to pre-emptively identify and address probable failures of the IoT nodes prior to failure of the IoT nodes, the monitoring including, for each IoT node on the user IoT system:
periodically requesting, from an enterprise error database, error messages generated from devices associated with the IoT node's device identifier;
applying a machine learning model to error messages received from the enterprise database to extract a first subset of error messages, the error messages in the first subset being generated by devices associated with an employee employed in the LOB;
in response to the identification of a threshold number of first error messages in the first subset, pulling from the enterprise error database a first remediation routine built to address the first error messages, wherein the first error messages are a group of identical error messages; and
transmitting to the IoT node the first remediation routine and instructions to run the first remediation routine, wherein the transmission is performed prior to transmission of the first error message from the IoT node to the IoT hub; and
addressing known failures for each IoT node on the user IoT system by:
receiving from the IoT node a second error message, the second error message having been generated by the IoT node and indicating a failure of the IoT node;
pulling, from the enterprise error database, second error messages generated by devices associated with the same device identifier as the IoT node, wherein the pulled second error messages are identical to the second error message generated by the IoT node;
applying the machine learning model to the pulled error data to extract a second subset of error messages from the pulled error data, the second error messages in the second subset having been generated by devices associated with an employee employed in the LOB;
transmitting a first query to the enterprise error database to return a second remediation routine built to address the second error messages in the second subset;
when first query returns a second remediation routine, transmitting the second remediation routine extracted by the first query to the IoT node together with instructions to run the second remediation routine;
when the first query returns a null value, transmitting a second query to the enterprise error database to return a second remediation routine built to address the second error messages in a third subset of error messages, the third subset including the pulled second error messages less the second subset of error messages; and
when second query returns a second remediation routine, transmitting the second remediation routine extracted by the second query to the IoT node together with instructions to run the second remediation routine.

### Claim 16 (depends on 15)

The method of claim 15 wherein the assessing the user devices for conformance with baseline security protocols and performance characteristics includes:
accessing a central database storing a plurality of baseline security protocols and performance characteristics; and
identifying the baseline security protocols and the performance characteristics, the baseline security protocols and performance characteristics being associated with the LOB in the central database.

### Claim 17 (depends on 16)

The method of claim 16 further comprising:
determining that a user device is not in conformance with the baseline security protocols and performance characteristics; and
blocking communication between the user's personal computer and the user device determined not to be in conformance.

### Claim 18 (depends on 17)

The method of claim 17 wherein the determining that the user device is not in conformance includes determining that the user device includes hardware or software that the user is not allowed to use based on the LOB of the user.

### Claim 19

A method for establishing and supporting a user Internet of Things (“IoT”) system, the method being performed by a central IoT hub run on a user's personal computing device, the method comprising:
detecting user devices in electronic communication with the central IoT hub;
assessing the user devices for conformance with baseline security protocols and performance characteristics, wherein the assessing the user devices includes:
accessing a job description of the user stored in a central database; and
identifying the baseline security protocols and the performance characteristics, the baseline security protocols and performance characteristics being associated with the job description in the central database;
onboarding, to the user IoT system, user devices determined to be in conformance with the baseline security protocols and performance characteristics, each of the onboarded user devices being an IoT node on the user IoT system and being associated with a device identifier; and
monitoring enterprise data to pre-emptively identify and address probable failures of the IoT nodes prior to failure of the IoT nodes, the monitoring including, for each IoT node on the user IoT system:
periodically requesting, from an enterprise error database, error messages generated from devices associated with the IoT node's device identifier;
applying a machine learning model to error messages received from the enterprise database to extract a first subset of error messages, the error messages in the first subset being generated by devices positioned at a geospatial location that is within a predetermined distance of the IoT node;
in response to the identification of a threshold number of first error messages in the first subset, pulling from the enterprise error database a first remediation routine built to address the first error messages, wherein the first error messages are a group of identical error messages; and
transmitting to the IoT node the first remediation routine and instructions to run the first remediation routine, wherein the transmission is performed prior to receipt transmission of the first error message from the IoT node to the IoT hub.

### Claim 20 (depends on 19)

The method of claim 19 further comprising, for each of the IoT nodes:
requesting the IoT node to transmit to the IoT hub customized configuration settings of the IoT node;
pinging the IoT node and not receiving a response from the IoT node;
determining, based on a lack of response from the IoT node to the pinging over a predetermined time period, that the IoT node has deleted itself from the IoT system;
detecting a new user device in electronic communication with the central IoT hub, the new user device being a similar or identical piece of hardware to the IoT node that deleted itself from the IoT system; and
when the new user device is onboarded to the IoT system and becomes a new IoT node, transmitting to the new IoT node the configuration settings and instructing the new IoT node to adopt the transferred configuration settings.
