# US 2026/0089154 A1 · System and Method for Automation Device Configuration

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

- Number: US 2026/0089154 A1
- Document ID: US20260089154A1
- Status: Published application
- Kind: A1
- Application number: 19/337,732
- Filed: 2025-09-23
- Published: 2026-03-26
- Earliest claimed: 2024-09-23
- Assignees: OliverIQ
- Applicants: OliverIQ
- Inventors: Eric Smith; Jory Dunn; Spencer Apsley; Michael Thomas Patrick McNamara; Darrell Burns
- Web page: https://patentgrep.com/patent/US20260089154A1

## CPC

- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/102: {Entity profiles}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

This technology includes a method for executing a configuration process for an automation device. The method can include detecting an automation device on a computer network using a bridge agent associated with an automation hub. Another operation is determining the configuration process used to configure the automation device for operating with the bridge agent by using automation device identification information obtained by the bridge agent. Execution the configuration process may be initiated, which is to be executed by a client application. Donfiguration information for the automation device may be received from the client application.

## Claims

### Claim 1

A method for executing a configuration process for an automation device, comprising:
detecting the automation device on a computer network using a bridge agent associated with an automation hub;
determining the configuration process used to configure the automation device for operating with the bridge agent by using automation device identification information obtained by the bridge agent;
initiating execution of the configuration process which is to be executed by a client application; and
receiving configuration information for the automation device from the client application.

### Claim 2 (depends on 1)

The method as in claim 1, further comprising sending authorization information from the configuration information to an authorization server.

### Claim 3 (depends on 2)

The method as in claim 2, further comprising receiving a token from the authorization server.

### Claim 4 (depends on 3)

The method as in claim 3, further comprising using the token to access third-party services for the automation device.

### Claim 5 (depends on 1)

The method as in claim 1, wherein initiating execution of user interface elements further comprises: initiating an authorization interface using a type of authorization interface determined for the automation device by the automation hub in order to collect authorization information for completing authorization.

### Claim 6 (depends on 4)

The method as in claim 4, wherein determining a type of authorization interface, further comprises:
querying the automation device to determine a device type of the automation device;
determining an authorization interface type for the device type;
obtaining authorization data to send to an authorization server from a user through a client application; and
sending the authorization data to the authorization server.

### Claim 7 (depends on 1)

The method as in claim 1, further comprising, presenting a user interface to a user based on a template to collect data based on an authorization interface type.

### Claim 8 (depends on 1)

The method as in claim 1, further comprising connecting the automation device to an automation hub.

### Claim 9 (depends on 6)

The method as in claim 6, wherein the token is used to make API calls for an authorized person on an account or for the automation device.

### Claim 10 (depends on 1)

The method as in claim 1, further comprising loading a bridge agent for a type of automation device detected.

### Claim 11

A method for providing an interface to enable obtaining a token from an authorization service, comprising:
detecting an automation device on a computer network using a bridge agent associated with an automation hub;
determining a type of authorization interface used to authenticate to an authorization server of a vendor of the automation device by using automation device identification information received by the bridge agent;
initiating the authorization interface using the type of authorization interface and the automation hub to collect authorization information for completing authentication;
sending the authorization information to the authorization server; and
receiving the token from the authorization server.

### Claim 12 (depends on 11)

The method as in claim 11, wherein determining a type of authorization interface, further comprises:
querying the automation device to determine a device type of the automation device;
retrieving an authorization interface type;
obtaining authorization data to send to an authorization server from a user; and
sending the authorization data to the authorization server.

### Claim 13 (depends on 11)

The method as in claim 11, wherein retrieving an authorization interface type further comprises looking up an authorization interface type in a data store using a device type.

### Claim 14 (depends on 11)

The method as in claim 11, further comprising, presenting a user interface to a user based on a template to collect data based on an authentication interface type.

### Claim 15 (depends on 11)

The method as in claim 11, further comprising connecting the automation device to an automation hub.

### Claim 16

A system for determining an authorization process to enable obtaining authorization from an authorization service, comprising:
at least one processor;
at least one memory device including a data store to store a plurality of data and instructions that, when executed, cause the system and processor to:
detect an automation device on a computer network using a bridge agent associated with an automation hub;
determine the authorization process used to authenticate to an authorization server of a vendor of the automation device by using automation device identification information received by the bridge agent;
initiate execution of user interface elements of the authorization process to be executed by a client application; and
receive authorization information from the client application.

### Claim 17 (depends on 16)

The system as in claim 16, further comprising sending the authorization information to the authorization server.

### Claim 18 (depends on 17)

The system as in claim 17, further comprising receiving a token from the authorization server.

### Claim 19 (depends on 18)

The system as in claim 18, further comprising using the token to access third-party services for the automation device.

### Claim 20 (depends on 19)

The system as in claim 19, wherein the token is used to make API calls for an authorized person on an account or for the automation device.
