Diagnosing incidents for information technology service management

US2016196501A1 · US · A1

Patent metadata
FieldValue
Publication numberUS-2016196501-A1
Application numberUS-201615069276-A
CountryUS
Kind codeA1
Filing dateMar 14, 2016
Priority dateNov 8, 2012
Publication dateJul 7, 2016
Grant date

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Diagnosing and detecting causes of an incident may comprise classifying the incident by keywords, searching for co-occurring and reoccurring group of incidents, summarizing commonalities in the group of incidents, correlating the group of incidents with causes, defining association rules between the commonalities, and predicting potential problems based on the correlated group of incidents with causes.

First claim

Opening claim text (preview).

We claim: 1 . A computer-implemented method of diagnosing and detecting causes of an incident interactively, the method performed by one or more processors, the method comprising: classifying the incident by keywords by searching a problem ticket generated in an information technology (IT) system, the problem ticket describing the incident for the keywords; adding dependency keywords to the keywords, the dependency keywords representing dependent components among IT components involved in the problem ticket, wherein the dependency keywords are respectively given a boosting weight based on an impact of the respective keyword; assigning accuracy weight to the respective keyword based on a validity of the respective keyword and the boosting weight; searching for co-occurring and reoccurring group of incidents based on the keywords with respective accuracy weights and boosting weights; summarizing commonalities in the group of incidents; correlating the group of incidents with causes; defining association rules between the commonalities; and predicting potential problems based on the correlated group of incidents with causes. 2 . The method of claim 1 , wherein the searching for co-occurring and reoccurring group of incidents further comprises searching for similarity among the incidents in the group. 3 . The method of claim 1 , wherein the searching for co-occurring and reoccurring group of incidents further comprises searching for dependency among the incidents in the group. 4 . The method of claim 1 , wherein the searching for co-occurring and reoccurring group of incidents further comprises searching for shared environment among the incidents in the group. 5 . The method of claim 1 , wherein the causes comprise changes to an information technology system, traffic of the information technology system, maintenance of the information technology system. 6 . The method of claim 1 , wherein the classifying comprises: extracting keywords from consolidated incident data; validating the keywords using provided and automatically learned domain knowledge built from historical incident data, wherein the automatically learned domain knowledge comprises at least said defined association rules; and assigning accuracy weight for each of the keywords based on confidence level associated with each of the association rules. 7 . The method of claim 1 , wherein the searching comprises: finding incidents matching the keywords and other keywords with one or more dependency relationships specified in the association rules; and calculating relevancy score of each of the found incidents based on accuracy of matched keywords, dependency, and context relevancy. 8 . The method of claim 1 , wherein the correlating comprises: finding common events comprising one or more of changes, traffic anomaly patterns, and other events preceding the group of incidents; statistically determining a correlation relationship between the common events and the incidents. 9 . The method of claim 1 , further comprising: generating diagnosis comprising creating a report showing the co-occurring and reoccurring incidents, the causes, the defined association rules between the commonalities of the incident group and the causes. 10 . The method of claim 9 , further comprising: collecting user feedback on the report and iteratively improving the diagnosis. 11 . A computer readable storage medium storing a program of instructions executable by a machine to perform a method of diagnosing and detecting causes of an incident interactively, comprising: classifying the incident by keywords by searching a problem ticket generated in an information technology (IT) system, the problem ticket describing the incident for the keywords; adding dependency keywords to the keywords, the dependency keywords representing dependent components among IT components involved in the problem ticket, wherein the dependency keywords are respectively given a boosting weight based on an impact of the respective keyword; assigning accuracy weight to the respective keyword based on a validity of the respective keyword and the boosting weight; searching for co-occurring and reoccurring group of incidents based on the keywords with respective accuracy weights and boosting weights; summarizing commonalities in the group of incidents; correlating the group of incidents with causes; defining association rules between the commonalities; and predicting potential problems based on the correlated group of incidents with causes. 12 . The computer readable storage medium of claim 11 , wherein the searching for co-occurring and reoccurring group of incidents further comprises searching for shared environment among the incidents in the group. 13 . The computer readable storage medium of claim 11 , wherein the searching comprises: finding incidents matching the keywords and other keywords with one or more dependency relationships specified in the association rules; and calculating relevancy score of each of the found incidents based on accuracy of matched keywords, dependency, and context relevancy. 14 . The computer readable storage medium of claim 11 , wherein the correlating comprises: finding common events comprising one or more of changes, traffic anomaly patterns, and other events preceding the group of incidents; statistically determining correlation relationship between the common events and the incidents. 15 . The computer readable storage medium of claim 11 , further comprising: generating diagnosis comprising creating a report showing the co-occurring and reoccurring incidents, the causes, the defined association rules between the commonalities of the incident group and the causes; and collecting user feedback on the report and iteratively improving the diagnosis. 16 . A system for diagnosing and detecting causes of an incident interactively, comprising: a processor; a user interface operable to execute on the processor and issue a query; a search engine operable to execute on the processor, and further operable to receive the query, transform the query into sub-queries comprising a structured search and a free-text search, to search for co-occurring and reoccurring group of incidents, the search engine further operable to correlate the group of incidents with causes based on common events found in the group of incidents, and present the co-occurring and reoccurring group of incidents and the causes to the user interface, wherein the query is built based on searching a problem ticket describing one of the incidents for the keywords, the problem ticket generated in an information technology (IT) system, the keywords assigned accuracy weights respectively based on a validity of the respective keyword and boosting weights respectively based on impact of the respective keyword, wherein dependency keywords are added to the keywords, the dependency keywords representing dependent components among IT components involved in the problem ticket, wherein the dependency keywords are respectively given boosting weights. 17 . The system of claim 16 , further comprising: a text mining module operable to receive incident data and information associated with maintenance schedule, traffic data, and change plan of an information technology system, classify the incident data by keywords, and store the classified data as consolidated incident data. 18 . The system of claim 17 , further comprising: a learning module operable to summarize commonalities in the group of incidents

Assignees

Inventors

Classifications

  • G06N7/01Primary

    Probabilistic graphical models, e.g. probabilistic networks · CPC title

  • Query execution (filtering based on additional data G06F16/335) · CPC title

  • Risk analysis of enterprise or organisation activities · CPC title

  • Clustering; Classification · CPC title

  • Summarisation for human users · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US2016196501A1 cover?
Diagnosing and detecting causes of an incident may comprise classifying the incident by keywords, searching for co-occurring and reoccurring group of incidents, summarizing commonalities in the group of incidents, correlating the group of incidents with causes, defining association rules between the commonalities, and predicting potential problems based on the correlated group of incidents with…
Who is the assignee on this patent?
IBM
What technology area does this patent fall under?
Primary CPC classification G06N7/01. Mapped technology areas include Physics.
When was this patent published?
Publication date Thu Jul 07 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (A1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).