# US 2026/0093562 A1 · Distributed orchestration architectures, and related systems and methods

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

- Number: US 2026/0093562 A1
- Document ID: US20260093562A1
- Status: Published application
- Kind: A1
- Application number: 19/263,637
- Filed: 2025-07-09
- Published: 2026-04-02
- Earliest claimed: 2024-09-27
- Assignees: LiveView Technologies, LLC
- Applicants: LiveView Technologies, LLC
- Inventors: Roy W. Hayward; Steven R. Lindsey
- Web page: https://patentgrep.com/patent/US20260093562A1

## CPC

- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- G06F 9/4881: {Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues}
- G06F 9/5038: {considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration (scheduling strategies G06F9/4881 and subgroups)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Various embodiments relate to event-driven architectures. An event-driven architecture may include an event bus and an orchestrator communicatively coupled to the event bus. The event-driven architecture may also include a number of components communicatively coupled to the event bus. A first component of the number of components is configured to perform a first workflow in response to a first event. Further, the orchestrator is configured to perform a second workflow in response to a second, different event. Associated methods and systems are also disclosed.

## Claims

### Claim 1

A system including an event-driven architecture, the system comprising:
an event bus;
one or more orchestrators communicatively coupled to the event bus; and
a number of components communicatively coupled to the event bus, wherein, in response to a first event, a first component of the number of components is configured to perform a first workflow of a number of workflows;
wherein the one or more orchestrators is configured to:
distribute the first workflow to the first component; and
perform, in response to a second event, a second workflow of the number of workflows.

### Claim 2 (depends on 1)

The system of claim 1, wherein the number of components includes at least one camera and at least one light.

### Claim 3 (depends on 2)

The system of claim 2, further comprising a mobile surveillance unit including the at least one camera and the at least one light.

### Claim 4 (depends on 1)

The system of claim 1, wherein the orchestrator is configured to:
receive a generated workflow;
determine if a component of the number of components is configured to perform the workflow; and
publish the workflow responsive to determining that the component is configured to perform the workflow.

### Claim 5 (depends on 4)

The system of claim 4, wherein the component is configured to:
assume the workflow; and
subscribe to at least one event associated with the workflow.

### Claim 6 (depends on 1)

The system of claim 1, wherein the orchestrator is configured to:
receive a generated workflow;
determine if at least one component of the number of component is configured to perform the workflow; and
subscribe to at least one event associated with the workflow responsive to determining that the at least one component is not configured to perform the workflow.

### Claim 7 (depends on 1)

The system of claim 1, further comprising a workflow generator for generating workflows for the event-driven architecture.

### Claim 8 (depends on 1)

The system of claim 1, wherein the orchestrator is configured to:
determine that at least one other component is configured to perform its associated workflow; and
send the associated workflow to the at least one other component responsive to determining that the at least one other component is configured to perform its associated workflow.

### Claim 9

A system, comprising:
an event bus;
a number of components communicatively coupled to the event bus, wherein:
a first component of the number of the components is a sophisticated component configured to perform a first workflow; and
a second component of the number of components is an unsophisticated component; and
an orchestrator communicatively coupled to the event bus and configured to distribute a workflow to the first component.

### Claim 10 (depends on 9)

The system of claim 9, wherein the number of components includes at least one sensor and at least one output device.

### Claim 11 (depends on 10)

The system of claim 10, further comprising a mobile surveillance unit including the at least one sensor and at least one output device.

### Claim 12 (depends on 9)

The system of claim 9, wherein the orchestrator is further configured to:
determine, for each component of the number of components, whether the component is sophisticated or unsophisticated;
publish an associated workflow to the event bus responsive to determining that the component is sophisticated; and
subscribe to at least one event associated with the associated workflow responsive to determining that the component is unsophisticated.

### Claim 13 (depends on 9)

The system of claim 9, wherein the first component is configured to subscribe to at least one event associated with the first workflow.

### Claim 14 (depends on 9)

The system of claim 9, further comprising a workflow generator communicatively coupled to the orchestrator and configured to generate a number of workflows.

### Claim 15 (depends on 9)

The system of claim 9, further comprising a mobile unit including at least one component of the number of components.

### Claim 16

A method of operating an event-driven architecture, the method comprising:
receiving, at a bus of the event-driven architecture, a first message associated with an event;
responsive to determining that a service of a number of services does not include a workflow for the event:
generating, via an orchestrator, a second message;
publishing the second message to the bus; and
receiving, via the service, the second message;
receiving, via the service, the first message responsive to determining that the service includes the workflow for the event; and
performing an action via the service.

### Claim 17 (depends on 16)

The method of claim 16, further comprising determining if the service includes the workflow for the event.

### Claim 18 (depends on 16)

The method of claim 16, further comprising determining, for each service of a number of services of the event-driven architecture, whether a service is a sophisticated service or an unsophisticated service.

### Claim 19 (depends on 18)

The method of claim 18, further comprising subscribing, via the orchestrator, to one or more events associated with each service of the number of services determined to be unsophisticated.

### Claim 20 (depends on 16)

The method of claim 16, further comprising:
generating the workflow;
publishing the workflow to the orchestrator;
determining if a service of the number of services is configured to perform the workflow;
publishing the workflow to the bus responsive to determining that the service is configured to perform the workflow; and
subscribe to at least one event associated with the workflow responsive to determining that the service is not configured to perform the workflow.

### Claim 21

An event-driven architecture, comprising:
an event bus;
an orchestrator communicatively coupled to the event bus; and
a number of components communicatively coupled to the event bus;
wherein responsive to a first event, a first component of the number of components performs a first workflow;
wherein, responsive to a second, different event, the orchestrator performs a second workflow.

### Claim 22 (depends on 21)

The event-driven architecture of claim 21, wherein the first component is a sophisticated component, and a second component that is associated with the second, different event is an unsophisticated component.

### Claim 23

A method of operating an event-driven architecture, the method comprising:
receiving a number of workflows at an orchestrator of the event-driven architecture;
determining, for each of a number of components of the event-driven architecture, whether the component is a sophisticated component or an unsophisticated component; and
sending a first workflow of the number of workflows to a first, sophisticated component of the number of components.

### Claim 24 (depends on 23)

The method of claim 23, further comprising performing the first workflow via the first sophisticated component.

### Claim 25 (depends on 23)

The method of claim 23, further comprising performing a second workflow of the number of workflows via the orchestrator.
