# US 2023/0403215 A1 · Systems and methods of monitoring and controlling remote assets

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

- Number: US 2023/0403215 A1
- Document ID: US20230403215A1
- Status: Published application
- Kind: A1
- Application number: 18/456,334
- Filed: 2023-08-25
- Published: 2023-12-14
- Earliest claimed: 2019-11-14
- Assignees: Trideum Corporation
- Applicants: Trideum Corporation
- Inventors: Kurt Lessmann; Mark Riecken; Michael J. O'Connor
- Web page: https://patentgrep.com/patent/US20230403215A1

## CPC

- H04L 43/065: related to network devices
- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- H04L 43/50: Testing arrangements
- H04L 41/0213: Standardised network management protocols, e.g. simple network management protocol [SNMP]
- H04L 41/046: comprising network management agents or mobile agents therefor
- H04L 43/0817: by checking functioning
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems, methods, and computer readable media for monitoring distributed computing events are disclosed. The method includes defining parameters for a plurality of monitored assets, receiving status data for each monitored asset during the event, determining if each monitored asset's status is within the defined parameters during the event, providing an indication to a user if a monitored asset's status is outside the defined parameters, receiving instructions from the user for each monitored asset outside of the defined parameters, transmitting the instructions to the monitored asset outside of the defined parameters, executing the instructions on the monitored asset outside of the defined parameters, and providing an assessment of the event after the event concludes.

## Claims

### Claim 1

A method for monitoring distributed computing assets during events, comprising the steps of:
determining a set of assets to be monitored during an event, wherein the monitored assets comprise at least one physical asset and at least one simulated asset;
defining parameters for the event;
receiving status data from each monitored asset during the event;
determining if each monitored asset's status is within the defined parameters during the event;
providing an indication to a user if a monitored asset's status is outside the defined parameters;
receiving instructions from the user for each monitored asset outside of the defined parameters;
transmitting the instructions to the monitored asset outside of the defined parameters;
executing the instructions on the monitored asset outside of the defined parameters; and
providing an assessment of the event after the event concludes.

### Claim 2 (depends on 1)

The method of claim 1, wherein the event is a simulated training event.

### Claim 3 (depends on 1)

The method of claim 1, wherein the monitored assets are at least one of computers, laptops, desktops, rack-mounted, virtualized, or Internet of Things (IoT) devices, smartphones, tablets, network devices, software-defined radios, unmanned aerial vehicles (UAVs), ground control stations, tactical solutions, training solutions, software applications, network devices, and data transmission devices.

### Claim 4 (depends on 1)

The method of claim 1, wherein the step of defining parameters for a plurality of monitored assets is one of a new set of parameters or is based on parameters from a previous event.

### Claim 5 (depends on 1)

The method of claim 1, wherein the parameters include at least one of what and when monitored assets are involved in the event, specifications of each monitored asset, what each monitored asset should be doing during the event, how the monitored assets communicate, central processing unit (CPU) utilization, memory utilization, hardware performance, software performance, and data file and application version information.

### Claim 6 (depends on 1)

The method of claim 1, further comprising installing data gathering agents on each monitored asset.

### Claim 7 (depends on 1)

The method of claim 1, further comprising testing each monitored asset prior to each event.

### Claim 8 (depends on 1)

The method of claim 1, further comprising monitoring network data.

### Claim 9 (depends on 8)

The method of claim 8, further comprising monitoring for and reporting at least one of out of bounds system performance, incorrect data, potential cybersecurity issues, unexpected data on the network, and unexpected IP addresses.

### Claim 10 (depends on 1)

The method of claim 1, wherein the assessment of the event includes at least one of number of times and/or durations a monitored asset exceeded some parameters, and trends for events, sites, or monitored assets.

### Claim 11 (depends on 10)

The method of claim 10, wherein the assessment is organized by at least one of overall event, by site, and by individual monitored asset.

### Claim 12 (depends on 1)

The method of claim 1, wherein the step of determining if each monitored asset's status is within the defined parameters during the event includes determining if each monitored asset's status is at or above a threshold for the parameters, below the threshold for the parameters but within an acceptable range below the threshold, or exceeding the acceptable range below the threshold.

### Claim 13 (depends on 12)

The method of claim 12, further comprising providing different indications for each monitored asset below the threshold for the parameters but within an acceptable range below the threshold, and each monitored asset exceeding the acceptable range below the threshold.

### Claim 14 (depends on 1)

The method of claim 1, further comprising displaying event information to the user.

### Claim 15 (depends on 14)

The method of claim 14, wherein the event information includes at least one of status and trends of events, sites, and monitored assets, geographical locations of sites, events currently in the database, event participant locations, and network diagrams.

### Claim 16 (depends on 1)

The method of claim 1, wherein the data is at least one of Security Information and Event Management (SIEM) data, Simple Network Management Protocol (SNMP) data, High Level Architecture (HLA) data, Distributed Interactive Simulation (DIS) data, and Data Distribution System (DDS) data.

### Claim 17 (depends on 1)

The method of claim 1, wherein the instructions include at least one of starting or stopping a process or application, installing software updates, and steps to remedy monitored asset outside of the defined parameters.

### Claim 18 (depends on 1)

The method of claim 1, wherein the method is a cloud-based deployment or an on-site deployment.

### Claim 19

Non-transitory computer readable media for monitoring distributed computing assets during events, the computer readable media directing a central processor to:
determine a set of assets to be monitored during an event, wherein the monitored assets comprise at least one physical asset and at least one simulated asset;
define parameters for the event;
receive status data from each monitored asset during the event;
determine if each monitored asset's status is within the defined parameters during the event;
provide an indication to a user if a monitored asset's status is outside the defined parameters;
receive instructions from the user for each monitored asset outside of the defined parameters;
transmit the instructions to the monitored asset outside of the defined parameters; and
provide an assessment of the event after the event concludes.

### Claim 20 (depends on 19)

The non-transitory computer readable media of claim 19, wherein the event is a simulated training event.

### Claim 21 (depends on 19)

The non-transitory computer readable media of claim 19, wherein the monitored assets are at least one of computers, laptops, desktops, rack-mounted, virtualized, or Internet of Things (IoT) devices, smartphones, tablets, network devices, software-defined radios, unmanned aerial vehicles (UAVs), ground control stations, tactical solutions, training solutions, software applications, network devices, and data transmission devices.

### Claim 22 (depends on 19)

The non-transitory computer readable media of claim 19, wherein the parameters are one of a new set of parameters or is based on parameters from a previous event.

### Claim 23 (depends on 19)

The non-transitory computer readable media of claim 19, wherein the parameters include at least one of what and when monitored assets are involved in the event, specifications of each monitored asset, what each monitored asset should be doing during the event, how the monitored assets communicate, central processing unit (CPU) utilization, memory utilization, hardware performance, software performance, and data file and application version information.

### Claim 24 (depends on 19)

The non-transitory computer readable media of claim 19, wherein the computer readable media further directs the central processor to install data gathering agents on each monitored asset.

### Claim 25 (depends on 19)

The non-transitory computer readable media of claim 19, wherein the computer readable media further directs the central processor to test each monitored asset prior to each event.

### Claim 26 (depends on 19)

The non-transitory computer readable media of claim 19, wherein the computer readable media further directs the central processor to monitor network data.

### Claim 27 (depends on 26)

The non-transitory computer readable media of claim 26, wherein the computer readable media further directs the central processor to monitor for and report at least one of out of bounds system performance, incorrect data, potential cybersecurity issues, unexpected data on the network, and unexpected IP addresses.

### Claim 28 (depends on 19)

The non-transitory computer readable media of claim 19, wherein the assessment of the event includes at least one of number of times and/or durations a monitored asset exceeded some parameters, and trends for events, sites, or monitored assets.

### Claim 29 (depends on 28)

The non-transitory computer readable media of claim 28, wherein the assessment is organized by at least one of overall event, by site, and by individual monitored asset.

### Claim 30 (depends on 19)

The non-transitory computer readable media of claim 19, wherein the determination of each monitored asset's status is a determination of if the monitored asset's status is within the defined parameters during the event includes determining if each monitored asset's status is at or above a threshold for the parameters, below the threshold for the parameters but within an acceptable range below the threshold, or exceeding the acceptable range below the threshold.

### Claim 31 (depends on 30)

The non-transitory computer readable media of claim 30, wherein the computer readable media further directs the central processor to provide different indications for each monitored asset below the threshold for the parameters but within an acceptable range below the threshold, and each monitored asset exceeding the acceptable range below the threshold.

### Claim 32 (depends on 19)

The non-transitory computer readable media of claim 19, wherein the computer readable media further directs the central processor to display event information to the user.

### Claim 33 (depends on 32)

The non-transitory computer readable media of claim 32, wherein the event information includes at least one of status and trends of events, sites, and monitored assets, geographical locations of sites, events currently in the database, event participant locations, and network diagrams.

### Claim 34 (depends on 19)

The non-transitory computer readable media of claim 19, wherein the data is at least one of Security Information and Event Management (SIEM) data, Simple Network Management Protocol (SNMP) data, High Level Architecture (HLA) data, Distributed Interactive Simulation (DIS) data, and Data Distribution System (DDS) data.

### Claim 35 (depends on 19)

The non-transitory computer readable media of claim 19, wherein the instructions include at least one of starting or stopping a process or application, installing software updates, and steps to remedy monitored asset outside of the defined parameters.

### Claim 36

A system for monitoring distributed computing assets during events, comprising:
a plurality of monitored assets, each monitored asset adapted to transmit the monitored asset's status information data and receive instructions during an event, wherein the plurality of monitored assets comprise at least one physical asset and at least one simulated asset;
a central processing unit adapted to receive status information data from each monitored asset and send instructions to each monitored asset during the event;
software executing on the central processing unit, wherein the software:
defines parameters for the event;
receives status data from each monitored asset during the event;
determines if each monitored asset's status is within the defined parameters during the event;
provides an indication to a user if a monitored asset's status is outside the defined parameters;
receives instructions from the user for each monitored asset outside of the defined parameters;
transmits the instructions to the monitored asset outside of the defined parameters; and
provides an assessment of the event after the event concludes.

### Claim 37 (depends on 36)

The system of claim 36, wherein the event is a simulated training event.

### Claim 38 (depends on 36)

The system of claim 36, wherein the monitored assets are at least one of computers, laptops, desktops, rack-mounted, virtualized, or Internet of Things (IoT) devices, smartphones, tablets, network devices, software-defined radios, unmanned aerial vehicles (UAVs), ground control stations, tactical solutions, training solutions, software applications, network devices, and data transmission devices.

### Claim 39 (depends on 36)

The system of claim 36, wherein the parameters are one of a new set of parameters or is based on parameters from a previous event.

### Claim 40 (depends on 36)

The system of claim 36, wherein the parameters include at least one of what and when monitored assets are involved in the event, specifications of each monitored asset, what each monitored asset should be doing during the event, how the monitored assets communicate, central processing unit (CPU) utilization, memory utilization, hardware performance, software performance, and data file and application version information.

### Claim 41 (depends on 36)

The system of claim 36, wherein the software installs data gathering agents on each monitored asset.

### Claim 42 (depends on 36)

The system of claim 36, wherein the software tests each monitored asset prior to each event.

### Claim 43 (depends on 36)

The system of claim 36, wherein the software monitors network data.

### Claim 44 (depends on 43)

The system of claim 43, wherein the software monitors for and reports at least one of out of bounds system performance, incorrect data, potential cybersecurity issues, unexpected data on the network, and unexpected IP addresses.

### Claim 45 (depends on 36)

The system of claim 36, wherein the assessment of the event includes at least one of number of times and/or durations a monitored asset exceeded some parameters, and trends for events, sites, or monitored assets.

### Claim 46 (depends on 45)

The system of claim 45, wherein the assessment is organized by at least one of overall event, by site, and by individual monitored asset.

### Claim 47 (depends on 36)

The system of claim 36, wherein the determination of each monitored asset's status is a determination of if the monitored asset's status is within the defined parameters during the event includes determining if each monitored asset's status is at or above a threshold for the parameters, below the threshold for the parameters but within an acceptable range below the threshold, or exceeding the acceptable range below the threshold.

### Claim 48 (depends on 47)

The system of claim 47, wherein the software provides different indications for each monitored asset below the threshold for the parameters but within an acceptable range below the threshold, and each monitored asset exceeding the acceptable range below the threshold.

### Claim 49 (depends on 36)

The system of claim 36, wherein the software displays event information to the user.

### Claim 50 (depends on 49)

The system of claim 49, wherein the event information includes at least one of status and trends of events, sites, and monitored assets, geographical locations of sites, events currently in the database, event participant locations, and network diagrams.

### Claim 51 (depends on 36)

The system of claim 36, wherein the data is at least one of Security Information and Event Management (SIEM) data, Simple Network Management Protocol (SNMP) data, High Level Architecture (HLA) data, Distributed Interactive Simulation (DIS) data, and Data Distribution System (DDS) data.

### Claim 52 (depends on 36)

The system of claim 36, wherein the instructions include at least one of starting or stopping a process or application, installing software updates, and steps to remedy monitored asset outside of the defined parameters.
