Sign In to Follow Application
View All Documents & Correspondence

Method And System For Determining Automation Sequences For Resolution Of An Incident Ticket

Abstract: The present disclosure relates to a method and system for determining automation sequences for resolution of an incident ticket by an automation system. The automation system retrieves data associated with plurality of incident tickets received from a ticketing system during predefined time duration and groups the plurality of incident tickets into one or more clusters based on the data. The automation system receives a plurality of user actions associated with the plurality of incident tickets performed across a plurality of user devices and identifies similarity among sequences of the plurality of user actions for each ticket cluster. Based on the similarity, the automation system groups the sequences of the plurality of user actions into one or more bucket and determines automation sequences for resolution of the incident ticket by correlating the data associated with plurality of incident tickets with one or more buckets of the sequences. Fig.1a

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
30 July 2016
Publication Number
33/2016
Publication Type
INA
Invention Field
ELECTRICAL
Status
Email
ipo@knspartners.com
Parent Application
Patent Number
Legal Status
Grant Date
2023-03-24
Renewal Date

Applicants

WIPRO LIMITED
Doddakannelli, Sarjapur Road, Bangalore 560035, Karnataka, India.

Inventors

1. ARTHI VENKATARAMAN
47, Tennis House, 7th Main, Egipura, Bangalore 560047, Karnataka, India
2. AMIT SINGH
C-41 Saurabh Vihar, Badarpur, New Delhi 110044, India
3. RAHUL PRAJAPATI
MS-13, DAV Professors Multi, Khandwa Road, Indore 452001, Madhya Pradesh, India

Specification

Claims:WE CLAIM

1. A method for determining automation sequences for resolution of an incident ticket, the method comprising:
retrieving, by an automation system, data associated with plurality of incident tickets received from a ticketing system during a predefined time duration;
grouping, by the automation system, the plurality of incident tickets into one or more clusters based on the data;
receiving, by the automation system, a plurality of user actions associated with the plurality of incident tickets performed across a plurality of user devices;
identifying, by the automation system, similarity among sequences of the plurality of user actions for each ticket cluster;
grouping, by the automation system, the sequences of the plurality of user actions into one or more buckets based on the similarity; and
determining, by the automation system, automation sequences for resolution of the incident ticket by correlating the data associated with plurality of incident tickets with one or more buckets of the sequences.

2. The method as claimed in claim 1, wherein the data associated with the plurality of incident tickets comprises description of issues associated with each of the tickets.

3. The method as claimed in claim 1, wherein the plurality of user actions comprise information about at least one of launching an application, mouse and cursor movement, types of keystrokes, touch screen data, web portal access data, remote device access data, navigations across different applications, command and data entered and field data.

4. The method as claimed in claim 3, wherein the field data comprise application name, keys pressed by the users, location data of the key pressed, timestamps and user details performing the user actions.

5. The method as claimed in claim 1, wherein identifying similarity among sequences of the plurality of user actions comprises:
assigning, by the automation system, a unique identifier to each type of action of the plurality of user actions;
identifying, by the automation system, one or more parameterized variables between each pair of sequences based on greatest common sub-sequence between each pair of sequences; and
assigning, by the automation system, a score to the each pair of sequences based on the one or more parameterized variables and one or more parameters, wherein the score indicates similarity among sequences of the plurality of the user actions.

6. The method as claimed in claim 5, wherein the one or more parameters comprise at least one of length of matched patterns between the pair of sequences, number of the one or more parameterized variables in the pair of sequences, sequences matching at end points and in between in the pair of the sequences.

7. The method as claimed in claim 1 further comprising eliminating the one or more buckets based on minimum number of sequences in the corresponding bucket.

8. An automation system for determining automation sequences for resolution of an incident ticket comprising:
a processor; and
a memory communicatively coupled to the processor, wherein the memory stores processor instructions, which, on execution, causes the processor to:
retrieve data associated with plurality of incident tickets received from a ticketing system during a predefined time duration;
group the plurality of incident tickets into one or more clusters based on the data;
receive a plurality of user actions associated with the plurality of incident tickets performed across a plurality of user devices;
identify similarity among sequences of the plurality of user actions for each ticket cluster;
group the sequences of the plurality of user actions into one or more buckets based on the similarity; and
determine automation sequences for resolution of the incident ticket by correlating the data associated with the plurality of incident tickets with one or more buckets of the sequences.

9. The automation system as claimed in claim 8, wherein the data associated with the plurality of incident tickets comprises description of issues associated with each of the tickets.

10. The automation system as claimed in claim 8, wherein the plurality of user actions comprise information about at least one of launching an application, mouse and cursor movement, types of keystrokes, touch screen data, web portal data, remote device access data, navigations across different applications, command and data entered and field data.

11. The automation system as claimed in claim 10, wherein the field data comprise application name, keys pressed by the users, location data of the key pressed, timestamps and user details performing the user actions.

12. The automation system as claimed in claim 8, wherein the processor identifies similarity among sequences of the plurality of user actions by:
assigning a unique identifier to each type of action of the plurality of user actions;
identifying one or more parameterized variables between each pair of sequences based on greatest common sub-sequence between each pair of sequences; and
assigning a score to the each pair of sequences based on the one or more parameterized variables and one or more parameters, wherein the score indicates similarity among sequences of the plurality of the user action.

13. The automation system as claimed in claim 12, wherein the one or more parameters comprise at least one of length of matched patterns between the pair of sequences, number of the one or more parameterized variables in the pair of sequences, sequences matching at end points and in between in the pair of the sequences.

14. The automation system as claimed in claim 8, wherein the processor eliminates the one or more buckets based on minimum number of sequences in the corresponding bucket.

Dated this 30th day of July, 2016

R Ramya Rao
Of K&S Partners
Agent for the Applicant
, Description:TECHNICAL FIELD

The present subject matter is related in general to the field of incident ticket resolution, more particularly, but not exclusively to a method and system for determining automation sequences for resolution of an incident ticket.

Documents

Application Documents

# Name Date
1 Form 9 [30-07-2016(online)].pdf_157.pdf 2016-07-30
2 Form 9 [30-07-2016(online)].pdf 2016-07-30
3 Form 5 [30-07-2016(online)].pdf 2016-07-30
4 Form 3 [30-07-2016(online)].pdf 2016-07-30
5 Form 18 [30-07-2016(online)].pdf_156.pdf 2016-07-30
6 Form 18 [30-07-2016(online)].pdf 2016-07-30
7 Drawing [30-07-2016(online)].pdf 2016-07-30
8 Description(Complete) [30-07-2016(online)].pdf 2016-07-30
9 abstract201641026134 .jpg 2016-08-04
10 REQUEST FOR CERTIFIED COPY [06-08-2016(online)].pdf 2016-08-06
11 Form 26 [10-08-2016(online)].pdf 2016-08-10
12 Other Patent Document [06-09-2016(online)].pdf 2016-09-06
13 201641026134-Power of Attorney-160816.pdf 2016-09-06
14 201641026134-Correspondence-PA-160816.pdf 2016-09-06
15 201641026134-Form 1-120916.pdf 2016-11-18
16 201641026134-Correspondence-F1-120916.pdf 2016-11-18
17 Form 3 [28-12-2016(online)].pdf 2016-12-28
18 201641026134-FER.pdf 2020-03-06
19 201641026134-Information under section 8(2) [04-09-2020(online)].pdf 2020-09-04
20 201641026134-FORM 3 [04-09-2020(online)].pdf 2020-09-04
21 201641026134-OTHERS [05-09-2020(online)].pdf 2020-09-05
22 201641026134-FER_SER_REPLY [05-09-2020(online)].pdf 2020-09-05
23 201641026134-DRAWING [05-09-2020(online)].pdf 2020-09-05
24 201641026134-CORRESPONDENCE [05-09-2020(online)].pdf 2020-09-05
25 201641026134-COMPLETE SPECIFICATION [05-09-2020(online)].pdf 2020-09-05
26 201641026134-CLAIMS [05-09-2020(online)].pdf 2020-09-05
27 201641026134-US(14)-HearingNotice-(HearingDate-07-03-2023).pdf 2023-02-06
28 201641026134-POA [09-02-2023(online)].pdf 2023-02-09
29 201641026134-FORM 13 [09-02-2023(online)].pdf 2023-02-09
30 201641026134-Correspondence to notify the Controller [09-02-2023(online)].pdf 2023-02-09
30 Form 18 [30-07-2016(online)].pdf 2016-07-30
31 Form 18 [30-07-2016(online)].pdf_156.pdf 2016-07-30
31 201641026134-AMENDED DOCUMENTS [09-02-2023(online)].pdf 2023-02-09
32 Form 3 [30-07-2016(online)].pdf 2016-07-30
32 201641026134-Written submissions and relevant documents [22-03-2023(online)].pdf 2023-03-22
33 Form 5 [30-07-2016(online)].pdf 2016-07-30
33 201641026134-FORM-26 [22-03-2023(online)].pdf 2023-03-22
34 201641026134-PatentCertificate24-03-2023.pdf 2023-03-24
34 Form 9 [30-07-2016(online)].pdf 2016-07-30
35 201641026134-IntimationOfGrant24-03-2023.pdf 2023-03-24
35 Form 9 [30-07-2016(online)].pdf_157.pdf 2016-07-30

Search Strategy

1 searchSTRE_05-03-2020.pdf
2 2021-02-2616-02-09AE_26-02-2021.pdf

ERegister / Renewals

3rd: 12 Jun 2023

From 30/07/2018 - To 30/07/2019

4th: 12 Jun 2023

From 30/07/2019 - To 30/07/2020

5th: 12 Jun 2023

From 30/07/2020 - To 30/07/2021

6th: 12 Jun 2023

From 30/07/2021 - To 30/07/2022

7th: 12 Jun 2023

From 30/07/2022 - To 30/07/2023

8th: 12 Jun 2023

From 30/07/2023 - To 30/07/2024

9th: 17 Jul 2024

From 30/07/2024 - To 30/07/2025

10th: 25 Jul 2025

From 30/07/2025 - To 30/07/2026