# US 2026/0064513 A1 · ARBITRATION ENGINE FOR CONSOLIDATING ANOMALY DETECTION MEthODS

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

- Number: US 2026/0064513 A1
- Document ID: US20260064513A1
- Status: Published application
- Kind: A1
- Application number: 18/816,272
- Filed: 2024-08-27
- Published: 2026-03-05
- Earliest claimed: 2024-08-27
- Assignees: Bank of America Corporation
- Applicants: Bank of America Corporation
- Inventors: Maharaj Mukherjee; Carl Benda; Rahul Uniyal; Vijay Yarabolu; Aditya Krishnanand Chaubey; Viraj Shah; Duy Minh Pham
- Web page: https://patentgrep.com/patent/US20260064513A1

## CPC

- G06F 11/079: {Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36)}
- G06F 11/0709: {in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems}
- G06N 5/01: Dynamic search techniques; Heuristics; Dynamic trees; Branch-and-bound
- G06N 20/00: Machine learning
- G06N 20/20: Ensemble learning
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS

## Abstract

A computing platform may train, using historical system status information, a plurality of anomaly detection engines, each comprising a different machine learning model. The computing platform may monitor a system to collect system status information. The computing platform may input the system status information into each of the plurality of anomaly detection engines, where each of the plurality of anomaly detection engines may output, based on the system status information, a corresponding binary value indicating whether the system status information is anomalous according the given anomaly detection engine, and a corresponding confidence level associated with corresponding binary value. The computing platform may input the binary values and the corresponding confidence levels into an arbitration engine to generate a weighted average of the corresponding confidence levels and binary values. Based on identifying that the weighted average meets or exceeds a predetermined threshold value, label the system as experiencing anomalous behavior.

## Claims

### Claim 1

A computing platform comprising:
at least one processor;
a communication interface communicatively coupled to the at least one processor; and
memory storing computer-readable instructions that, when executed by the at least one processor, cause the computing platform to:
train, using historical system status information, a plurality of anomaly detection engines, wherein each of the plurality of anomaly detection engines corresponds to a different machine learning model, and wherein training the plurality of anomaly detection engines configures each of the plurality of anomaly detection engines to output, for given system status inputs, a binary value indicating whether or not the system status input indicates an anomaly, and a confidence level associated with the binary value;
monitor a system to collect system status information;
input the system status information into each of the plurality of anomaly detection engines, wherein each of the plurality of anomaly detection engines outputs, based on the system status information, a corresponding binary value indicating whether the system status information is anomalous according to a given anomaly detection engine, and a corresponding confidence level associated with the corresponding binary value;
input the binary values and the corresponding confidence levels into an arbitration engine, wherein the arbitration engine generates a weighted average of the corresponding confidence levels and binary values;
compare the weighted average to a predetermined threshold value;
based on identifying that the weighted average meets or exceeds the predetermined threshold value, label the system as experiencing anomalous behavior; and
execute one or more corrective actions to address the anomalous behavior.

### Claim 2 (depends on 1)

The computing platform of claim 1, wherein the historical system status information comprises one or more of: memory usage, computer processing unit (CPU) usage, available memory, memory consumption, communication patterns, processing speed, or labels indicating anomaly or no anomaly.

### Claim 3 (depends on 1)

The computing platform of claim 1, wherein the confidence level indicates a confidence of the corresponding anomaly detection engine that the binary value correctly indicates whether or not an anomaly is detected.

### Claim 4 (depends on 1)

The computing platform of claim 1, wherein one of the plurality of anomaly detection engines includes an isolation forest model to identify the binary value.

### Claim 5 (depends on 1)

The computing platform of claim 1, wherein the system is labelled as experiencing the anomalous behavior in real time.

### Claim 6 (depends on 1)

The computing platform of claim 1, wherein the system is labelled as experiencing the anomalous behavior in a predictive manner.

### Claim 7 (depends on 1)

The computing platform of claim 1, wherein generating the weighted average comprises:
generating a first average of the confidence values associated with binary values indicating an anomaly;
multiplying the first average by the binary value associated with anomalous behavior to produce a first weighted average;
generating a second average of the confidence values associated with binary values indicating no anomaly;
multiplying the second average by the binary value associated with non-anomalous behavior to produce a second weighted average;
generating absolute values of the first average and the second average; and
selecting, as the weighted average, one of the first average or the second average based on which of the first average or the second average has a higher associated absolute value.

### Claim 8 (depends on 1)

The computing platform of claim 1, wherein executing the one or more corrective actions comprises one or more of: taking the system offline, redistributing load of the system, or adding memory to the system.

### Claim 9 (depends on 1)

The computing platform of claim 1, wherein the memory stores additional computer readable instructions that, when executed by the at least one processor, cause the computing platform to:
send, to a user device of a system administrator, an alert indicating the anomalous behavior and one or more commands directing the user device to display the alert, wherein sending the one or more commands directing the user device to display the alert causes the user device to display the alert.

### Claim 10 (depends on 1)

The computing platform of claim 1, wherein the memory stores additional computer readable instructions that, when executed by the at least one processor, cause the computing platform to:
update, based on the system status information and the label, the plurality of anomaly detection engines.

### Claim 11

A method comprising:
at a computing platform comprising at least one processor, a communication interface, and memory:
training, using historical system status information, a plurality of anomaly detection engines, wherein each of the plurality of anomaly detection engines corresponds to a different machine learning model, and wherein training the plurality of anomaly detection engines configures each of the plurality of anomaly detection engines to output, for given system status inputs, a binary value indicating whether or not the system status input indicates an anomaly, and a confidence level associated with the binary value;
monitoring a system to collect system status information;
inputting the system status information into each of the plurality of anomaly detection engines, wherein each of the plurality of anomaly detection engines outputs, based on the system status information, a corresponding binary value indicating whether the system status information is anomalous according to a given anomaly detection engine, and a corresponding confidence level associated with the corresponding binary value;
inputting the binary values and the corresponding confidence levels into an arbitration engine, wherein the arbitration engine generates a weighted average of the corresponding confidence levels and binary values;
comparing the weighted average to a predetermined threshold value;
based on identifying that the weighted average meets or exceeds the predetermined threshold value, labelling the system as experiencing anomalous behavior; and
executing one or more corrective actions to address the anomalous behavior.

### Claim 12 (depends on 11)

The method of claim 11, wherein the historical system status information comprises one or more of: memory usage, computer processing unit (CPU) usage, available memory, memory consumption, communication patterns, processing speed, or labels indicating anomaly or no anomaly.

### Claim 13 (depends on 11)

The method of claim 11, wherein the confidence level indicates a confidence of the corresponding anomaly detection engine that the binary value correctly indicates whether or not an anomaly is detected.

### Claim 14 (depends on 11)

The method of claim 11, wherein one of the plurality of anomaly detection engines includes an isolation forest model to identify the binary value.

### Claim 15 (depends on 11)

The method of claim 11, wherein the system is labelled as experiencing the anomalous behavior in real time.

### Claim 16 (depends on 11)

The method of claim 11, wherein the system is labelled as experiencing the anomalous behavior in a predictive manner.

### Claim 17 (depends on 11)

The method of claim 11, wherein generating the weighted average comprises:
generating a first average of the confidence values associated with binary values indicating an anomaly;
multiplying the first average by the binary value associated with anomalous behavior to produce a first weighted average;
generating a second average of the confidence values associated with binary values indicating no anomaly;
multiplying the second average by the binary value associated with non-anomalous behavior to produce a second weighted average;
generating absolute values of the first average and the second average; and
selecting, as the weighted average, one of the first average or the second average based on which of the first average or the second average has a higher associated absolute value.

### Claim 18 (depends on 11)

The method of claim 11, wherein executing the one or more corrective actions comprises one or more of: taking the system offline, redistributing load of the system, or adding memory to the system.

### Claim 19 (depends on 11)

The method of claim 11, further comprising:
sending, to a user device of a system administrator, an alert indicating the anomalous behavior and one or more commands directing the user device to display the alert, wherein sending the one or more commands directing the user device to display the alert causes the user device to display the alert.

### Claim 20

One or more non-transitory computer-readable media storing instructions that, when executed by a computing platform comprising at least one processor, a communication interface, and memory, cause the computing platform to:
train, using historical system status information, a plurality of anomaly detection engines, wherein each of the plurality of anomaly detection engines corresponds to a different machine learning model, and wherein training the plurality of anomaly detection engines configures each of the plurality of anomaly detection engines to output, for given system status inputs, a binary value indicating whether or not the system status input indicates an anomaly, and a confidence level associated with the binary value;
monitor a system to collect system status information;
input the system status information into each of the plurality of anomaly detection engines, wherein each of the plurality of anomaly detection engines outputs, based on the system status information, a corresponding binary value indicating whether the system status information is anomalous according to a given anomaly detection engine, and a corresponding confidence level associated with the corresponding binary value;
input the binary values and the corresponding confidence levels into an arbitration engine, wherein the arbitration engine generates a weighted average of the corresponding confidence levels and binary values;
compare the weighted average to a predetermined threshold value;
based on identifying that the weighted average meets or exceeds the predetermined threshold value, label the system as experiencing anomalous behavior; and
execute one or more corrective actions to address the anomalous behavior.
