IP Library › Granted Patent US 10,783,453
Granted Patent B2
US 10,783,453 · App. 15/622,749 · Granted Sep 22, 2020

Systems and methods for automated incident response

Inventors: Hani El Sayyed (Bournemouth, GB); Gary Ford (Winchester, GB); Kevin Thomas (Dorset, GB); Daniel J. Christian (Bournemouth, GB); Salwa Husam Alamir (Bournemouth, GB); Simon Bench (Bournemouth, GB); Ian Maile (Poole, GB)
Assignee: JPMorgan Chase Bank, N.A.
G06N20/00G06F16/254G06N7/005
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,783,453
App. No.
15/622,749
Filed
Jun 14, 2017
Granted
Sep 22, 2020
Kind
B2
Art Unit
2123
USPC
706/12
Abstract

Systems and methods for automated incident response are disclosed. In one embodiment, a method for managing response to an incident may include (1) receiving training incident data from a training data source; (2) identifying at plurality of incident-related training keywords in the training data; (3) receiving one of a plurality of tags for each of the plurality of training keywords from a trainer; (4) executing a machine learning process to associate the received tags with the training keywords; (5) receiving incident data related to an incident from an incident data source; (6) identifying a plurality of incident-related keywords in the incident data; (7) automatically tagging the incident-related keyword with one of the plurality of tags; (8) automatically identifying at least one incident pattern from the tags; (9) automatically retrieving a solution for the incident based on similar resolved incidents; and (10) automatically applying the solution to the incident.

Claims (55)

1. A method for managing response to an incident, comprising:

at least one computer processor in an incident response system performing the following:

receiving training incident data from a training data source;

identifying at plurality of incident-related training keywords in the training data;

receiving one of a plurality of tags for each of the plurality of training keywords from a trainer;

executing a machine learning process to associate the received tags with the training keywords;

receiving incident data related to an incident from an incident data source;

identifying a plurality of incident-related keywords in the incident data;

automatically tagging the incident-related keyword with one of the plurality of tags;

automatically identifying at least one incident pattern from the tags;

automatically retrieving a solution for the incident based on similar resolved incidents;

automatically applying the solution to the incident;

receiving at least one search term for searching the incident data;

identifying at least one prior incident in the incident data responsive to the at least one search term;

calculating a relevancy score between the search term and at least one prior incident; and

outputting an identification of the at least one prior incident and the relevancy score.

2. The method of claim 1 , wherein the machine learning process is a Term Frequency-Inverse Document Frequency process.

3. The method of claim 1 , wherein natural language processing or cosine similarity is used to measure a similarity between the at least one search term and incident data for the at least one prior incident.

4. The method of claim 1 , wherein the solution comprises a work-around.

5. The method of claim 1 , wherein the incident data source comprises a centralized incident data repository.

6. The method of claim 1 , wherein the incident data source comprises at least one of a hardware source and a software source.

7. The method of claim 1 , wherein the incident data source comprises an incident chat transcript, an incident voice file, and an incident text report.

8. The method of claim 1 , further comprising:

automatically enriching the incident data with enrichment data.

9. The method of claim 8 , wherein the enrichment data identifies at least one of a weekend incident, a beginning of the day incident, an end of the day incident, and an end of month incident.

10. The method of claim 1 , further comprising:

clustering the incident with at least one prior incident.

11. The method of claim 10 , wherein the incident is clustered with at least one prior incident using a hierarchical clustering algorithm or a K-means clustering algorithm.

12. The method of claim 1 , the method may further comprise identifying at least one prior incident that is similar to the incident.

13. The method of claim 1 , wherein the solution comprises a software patch.

14. A system for managing response to an incident, comprising:

an incident response system comprising at least one computer processor and comprising a training engine and a learning engine;

at least one source of training data;

at least one source of incident data

an incident data repository; and

at least one user interface;

wherein:

the training engine receives training incident data from the source of training data;

the training engine identifies a plurality of incident-related training keywords in the training data;

the training engine receives one of a plurality of tags for each of the plurality of training keywords from a trainer;

the training engine executes a machine learning process to associate the received tags with the training keywords;

the learning engine receives incident data related to an incident from the source of incident data;

the learning engine identifies a plurality of incident-related keywords in the incident data;

the learning engine automatically tags the incident-related keyword with one of the plurality of tags;

the incident response system automatically identifies at least one incident pattern from the tags;

the incident response system automatically retrieves a solution for the incident based on similar resolved incidents in the incident data repository;

the incident response system automatically applies the solution to the incident;

the incident response system receives at least one search term for searching the incident data from the user interface;

the incident response system identifies at least one prior incident in the incident data responsive to the at least one search term;

the incident response system calculates a relevancy score between the search term and at least one prior incident; and

the incident response system outputs an identification of the at least one prior incident and the relevancy score to the user interface.

15. The system of claim 14 , wherein natural language processing or cosine similarity is used to measure a similarity between the at least one search term and incident data for the at least one prior incident.

16. The system of claim 14 , wherein the incident data source comprises a centralized incident data repository.

17. The system of claim 14 , wherein the incident data source comprises at least one of a hardware source and a software source.

18. The system of claim 14 , wherein the incident data source comprises an incident chat transcript, an incident voice file, and an incident text report.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 16, 2017
From: ALAMIR, SALWA HUSAM; BENCH, SIMON; EL SAYYED, HANI; FORD, GARY; THOMAS, KEVIN; CHRISTIAN, DANIEL J.; MAILE, IAN
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 042729/0696 →
Continuity (2)
Provisional Application 62349953 · Jun 14, 2016
Related Publication 20190228342A1 · Jul 25, 2019
Cited By (2)
US 12,367,094 US 12,554,549