Abstract: A technique is provided for providing resolution to tickets in an incident management system. The technique includes dynamically creating, by an analytics module, a taxonomy based on at least a database comprising one or more historical tickets, a description of incidents corresponding to each of the one or more historical tickets, and a corresponding resolution of each of the incidents. The technique further includes receiving, by an input module, one or more current tickets corresponding to an incident encountered by a user. The technique further includes, determining, by a pre-processing module, incident data corresponding to the received one or more current tickets based on pre-processing each of the one or more current tickets. Furthermore, a learning module determines one or more resolution steps corresponding to the received one or more current tickets based on at least the dynamically created taxonomy and the determined incident data. Figure 3
Claims:WE CLAIM
1. A method of providing resolution to tickets in an incident management system, the method comprising:
dynamically creating, by an analytics module, a taxonomy based on at least a database comprising one or more historical tickets, a description of incidents corresponding to each of the one or more historical tickets, and a corresponding resolution of each of the incidents;
receiving, by an input module, one or more current tickets corresponding to an incident encountered by a user;
determining, by a pre-processing module, incident data corresponding to the received one or more current tickets based on pre-processing each of the one or more current tickets;
determining, by a learning module, one or more resolution steps corresponding to the received one or more current tickets based on at least the dynamically created taxonomy and the determined incident data.
2. The method of claim, wherein the dynamic creation of the taxonomy comprises:
initializing a database with the one or more ticket dumps corresponding to one or more historical tickets; and
classifying the one or more historical tickets stored in the database, based on at least the incident description and a corresponding resolution of the incident.
3. The method of claim 2, wherein the one or more ticket dumps comprise at least: an identification of a ticket, summary of a ticket, severity of a ticket, time of reporting a ticket, time of resolution of a ticket, a category of resolution of a ticket.
4. The method of claim 1, wherein the incident data corresponds to at least: a category of the incident, a severity of the incident, a domain of an incident.
5. The method of claim 1, wherein the determination of the incident data comprises iteratively determining, via a clarification module, one or more additional inputs corresponding to the one or more current tickets, from the user.
6. The method of claim 1, wherein the pre-processing of the one or more current tickets is performed based on at least a Natural Language Processing (NLP) algorithm and a text analyzer.
7. The method of claim 1, further comprising performing incremental learning, by the learning module, based on the determined one or more resolution steps corresponding to the one or more current tickets.
8. The method of claim 1, wherein the one or more resolution steps are executed automatically by an output module, for resolving the incident encountered by the user.
9. A system for providing resolution to tickets in an incident management system, the system comprising:
a processor; and
a memory communicatively coupled to the processor, wherein the memory stores the processor-executable instructions, which, on execution, causes the processor to:
dynamically create a taxonomy based on at least a database comprising one or more historical tickets, a description of incidents corresponding to each of the one or more historical tickets, and a corresponding resolution of each of the incidents;
receive one or more current tickets corresponding to an incident encountered by a user;
determine incident data corresponding to the received one or more current tickets based on pre-processing each of the one or more current tickets;
determine one or more resolution steps corresponding to the received one or more current tickets based on at least the dynamically created taxonomy and the determined incident data
10. The system of claim 9, wherein the dynamic creation of the taxonomy comprises:
initializing a database with the one or more ticket dumps corresponding to one or more historical tickets; and
classifying the one or more historical tickets stored in the database, based on at least the incident description and a corresponding resolution of the incident.
11. The system of claim 10, wherein the one or more ticket dumps comprise at least: an identification of a ticket, summary of a ticket, severity of a ticket, time of reporting a ticket, time of resolution of a ticket, a category of resolution of a ticket.
12. The system of claim 9, wherein the incident data corresponds to at least: a category of the incident, a severity of the incident, a domain of an incident.
13. The system of claim 9, wherein the determination of the incident data comprises iteratively determining, via a clarification module, one or more additional inputs corresponding to the one or more current tickets, from the user.
14. The system of claim 9, wherein the pre-processing of the one or more current tickets is performed based on at least a Natural Language Processing (NLP) algorithm and a text analyzer.
15. The system of claim 9, further comprising performing incremental learning, by the learning module, based on the determined one or more resolution steps corresponding to the one or more current tickets.
16. The system of claim 9, wherein the one or more resolution steps are executed automatically by an output module, for resolving the incident encountered by the user.
Dated this 28th day of November, 2016
R Ramya Rao
Of K&S Partners
Agent for the Applicant
, Description:TECHNICAL FIELD
This disclosure relates generally to incident management system, and more particularly to method and system for providing resolution to tickets in an incident management system.
| Section | Controller | Decision Date |
|---|---|---|
| # | Name | Date |
|---|---|---|
| 1 | 201641040622-FORM 3 [13-02-2024(online)].pdf | 2024-02-13 |
| 1 | Form5_As Filed_28-11-2016.pdf | 2016-11-28 |
| 2 | 201641040622-FORM-26 [13-02-2024(online)].pdf | 2024-02-13 |
| 2 | Form3_As Filed_28-11-2016.pdf | 2016-11-28 |
| 3 | Form2 Title Page_Complete_28-11-2016.pdf | 2016-11-28 |
| 3 | 201641040622-Information under section 8(2) [13-02-2024(online)].pdf | 2024-02-13 |
| 4 | Form18_Express request_28-11-2016.pdf | 2016-11-28 |
| 4 | 201641040622-Written submissions and relevant documents [13-02-2024(online)].pdf | 2024-02-13 |
| 5 | Drawings_As Filed_28-11-2016.pdf | 2016-11-28 |
| 5 | 201641040622-AMENDED DOCUMENTS [18-01-2024(online)].pdf | 2024-01-18 |
| 6 | Description Complete_As Filed_28-11-2016.pdf | 2016-11-28 |
| 6 | 201641040622-Correspondence to notify the Controller [18-01-2024(online)].pdf | 2024-01-18 |
| 7 | Claims_As Filed_28-11-2016.pdf | 2016-11-28 |
| 7 | 201641040622-FORM 13 [18-01-2024(online)].pdf | 2024-01-18 |
| 8 | Abstract_As Filed_28-11-2016.pdf | 2016-11-28 |
| 8 | 201641040622-POA [18-01-2024(online)].pdf | 2024-01-18 |
| 9 | 201641040622-Duplicate-US(14)-HearingNotice-(HearingDate-29-01-2024).pdf | 2024-01-15 |
| 9 | Form26_General Power Of Attorney_04-12-2016.pdf | 2016-12-04 |
| 10 | 201641040622-US(14)-HearingNotice-(HearingDate-29-01-2024).pdf | 2024-01-14 |
| 10 | Correspondence by Agent_Request For Certified Copy_04-12-2016.pdf | 2016-12-04 |
| 11 | 201641040622-FER_SER_REPLY [26-11-2020(online)].pdf | 2020-11-26 |
| 11 | abstract 201641040622.jpg | 2016-12-20 |
| 12 | 201641040622-FORM 3 [26-11-2020(online)].pdf | 2020-11-26 |
| 12 | 201641040622-Proof of Right (MANDATORY) [20-12-2017(online)].pdf | 2017-12-20 |
| 13 | 201641040622-PETITION UNDER RULE 137 [26-11-2020(online)]-1.pdf | 2020-11-26 |
| 13 | Correspondence by Agent_Form 1_26-12-2017.pdf | 2017-12-26 |
| 14 | 201641040622-FER.pdf | 2020-05-26 |
| 14 | 201641040622-PETITION UNDER RULE 137 [26-11-2020(online)].pdf | 2020-11-26 |
| 15 | 201641040622-FER.pdf | 2020-05-26 |
| 15 | 201641040622-PETITION UNDER RULE 137 [26-11-2020(online)].pdf | 2020-11-26 |
| 16 | 201641040622-PETITION UNDER RULE 137 [26-11-2020(online)]-1.pdf | 2020-11-26 |
| 16 | Correspondence by Agent_Form 1_26-12-2017.pdf | 2017-12-26 |
| 17 | 201641040622-Proof of Right (MANDATORY) [20-12-2017(online)].pdf | 2017-12-20 |
| 17 | 201641040622-FORM 3 [26-11-2020(online)].pdf | 2020-11-26 |
| 18 | 201641040622-FER_SER_REPLY [26-11-2020(online)].pdf | 2020-11-26 |
| 18 | abstract 201641040622.jpg | 2016-12-20 |
| 19 | 201641040622-US(14)-HearingNotice-(HearingDate-29-01-2024).pdf | 2024-01-14 |
| 19 | Correspondence by Agent_Request For Certified Copy_04-12-2016.pdf | 2016-12-04 |
| 20 | 201641040622-Duplicate-US(14)-HearingNotice-(HearingDate-29-01-2024).pdf | 2024-01-15 |
| 20 | Form26_General Power Of Attorney_04-12-2016.pdf | 2016-12-04 |
| 21 | 201641040622-POA [18-01-2024(online)].pdf | 2024-01-18 |
| 21 | Abstract_As Filed_28-11-2016.pdf | 2016-11-28 |
| 22 | 201641040622-FORM 13 [18-01-2024(online)].pdf | 2024-01-18 |
| 22 | Claims_As Filed_28-11-2016.pdf | 2016-11-28 |
| 23 | 201641040622-Correspondence to notify the Controller [18-01-2024(online)].pdf | 2024-01-18 |
| 23 | Description Complete_As Filed_28-11-2016.pdf | 2016-11-28 |
| 24 | 201641040622-AMENDED DOCUMENTS [18-01-2024(online)].pdf | 2024-01-18 |
| 24 | Drawings_As Filed_28-11-2016.pdf | 2016-11-28 |
| 25 | Form18_Express request_28-11-2016.pdf | 2016-11-28 |
| 25 | 201641040622-Written submissions and relevant documents [13-02-2024(online)].pdf | 2024-02-13 |
| 26 | Form2 Title Page_Complete_28-11-2016.pdf | 2016-11-28 |
| 26 | 201641040622-Information under section 8(2) [13-02-2024(online)].pdf | 2024-02-13 |
| 27 | Form3_As Filed_28-11-2016.pdf | 2016-11-28 |
| 27 | 201641040622-FORM-26 [13-02-2024(online)].pdf | 2024-02-13 |
| 28 | Form5_As Filed_28-11-2016.pdf | 2016-11-28 |
| 28 | 201641040622-FORM 3 [13-02-2024(online)].pdf | 2024-02-13 |
| 1 | searchstratE_06-03-2020.pdf |