Sign In to Follow Application
View All Documents & Correspondence

A Method Of Generating Ontology Based On Plurality Of Tickets And An Enterprise System Thereof

Abstract: Disclosed herein is a method and system for generating an ontology based on plurality of tickets in an enterprise system 100. The method includes processing, by the enterprise system 100, input data associated with the plurality of tickets to obtain a structured data 228 associated with each of the plurality of tickets. Also, the method comprises performing multi-level clustering on the structured data 228 to obtain a plurality of clusters and corresponding error indicators, based on one or more parameters associated with the plurality of tickets. Further, the method comprises mapping each of the plurality of clusters with each of the error indicators, to obtain a mapped data at each cluster of the plurality of clusters and generating the ontology using the mapped data at each cluster of the plurality of clusters, corresponding to the plurality of tickets. FIG. 4

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
17 February 2017
Publication Number
34/2018
Publication Type
INA
Invention Field
COMPUTER SCIENCE
Status
Email
ipo@knspartners.com
Parent Application
Patent Number
Legal Status
Grant Date
2023-07-28
Renewal Date

Applicants

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

Inventors

1. SELVAKUBERAN KARUPPASAMY
5/74, Chandru Homes, Pillayar Kovil Street, Medavakkam, Chennai 600100, Tamil Nadu, India.

Specification

Claims:We claim:
1. A method of generating an ontology based on a plurality of tickets in an enterprise system 100, the method comprising:
processing, by the enterprise system 100, input data associated with the plurality of tickets to obtain a structured data 228 associated with each of the plurality of tickets;
performing multi-level clustering, by the enterprise system 100, on the structured data 228 to obtain a plurality of clusters and corresponding error indicators, based on one or more parameters associated with the plurality of tickets;
mapping, by the enterprise system 100, each cluster of the plurality of clusters with each of the error indicators, to obtain a mapped data at each cluster of the plurality of clusters; and
generating, by the enterprise system 100, the ontology using the mapped data at each cluster of the plurality of clusters, corresponding to the plurality of tickets.

2. The method as claimed in claim 1, wherein the input data comprises at least one of ticket dump, one or more data sources of the enterprise system 100 and user input data.

3. The method as claimed in claim 2, wherein the ticket dump comprises at least one of a ticket identification (ID) 212, a ticket number 214, a ticket title 216, a problem description 220, a resolution category and a resolution description 222 associated with each ticket.

4. The method as claimed in claim 2, wherein each of the one or more data sources comprises a ticket description 218, a resolution date 224 and a resolution time 226.

5. The method as claimed in claim 1, wherein processing the input data to obtain the structured data 228 comprises:
filtering ticket description 218 of the input data using at least one parameter associated with a ticket of the plurality of tickets to obtain a first filtered data 230;
filtering resolution description 222 of the input data using the at least one parameter associated with the ticket to obtain a second filtered data 232; and
obtaining the structured data 228 associated with each of the plurality of tickets using the first filtered data 230 and second filtered data 232.

6. The method as claimed in claim 5, wherein performing the multi-level clustering on the structured data 228 comprises:
mapping data associated with the first filtered data 230 and the second filtered data 232 based on a plurality of first error indicators 234, to obtain a first cluster group 236;
mapping data associated with the first filtered data 230 and the second filtered data 232 based on a plurality of second error indicators 238 encountered by a user, to obtain a second cluster group 240; and
mapping each of the error indicators associated with the first cluster group 236 and the second cluster group 240 based on a resolution obtained to generate a third cluster group 242.

7. The method as claimed in claim 1, wherein the mapping each cluster of the plurality of clusters with each of the error indicators comprises:
obtaining relationship for each of the plurality of clusters with the error indicators using modified natural language processing (NLP);
identifying a root node using the obtained relationship for each of the plurality of clusters with the error indicators;
generating a relationship from a higher level of the cluster to next level of the cluster using the root node; and
aligning the relationships for each of the plurality of clusters from a higher level to a lower level.

8. The method as claimed in claim 1, wherein the mapped data at each of the plurality of clusters comprises a root error indicator 244 corresponding to each of the plurality of clusters.

9. The method as claimed in claim 8, wherein generating the ontology using the mapped data at each cluster of the plurality of clusters comprises grouping each of the plurality of clusters based on the root error indicator 244.

10. An enterprise system 100 for generating an ontology based on plurality of tickets, the enterprise system 100 comprising:
a processor 204; and
a memory 206, communicatively coupled to the processor 204, wherein the memory 206 stores processor-executable instructions, which, on execution, causes the processor 204 to:
process input data associated with the plurality of tickets to obtain a structured data 228 associated with each of the plurality of tickets;
perform multi-level clustering on the structured data 228 to obtain a plurality of clusters and corresponding error indicators, based on one or more parameters associated with the plurality of tickets;
map each cluster of the plurality of clusters with each of the error indicators, to obtain a mapped data at each cluster of the plurality of clusters; and
generate the ontology using the mapped data at each cluster of the plurality of clusters, corresponding to the plurality of tickets.

11. The enterprise system as claimed in claim 10, wherein the input data comprises at least one of ticket dump, one or more data sources of the enterprise system 100 and user input data.

12. The enterprise system as claimed in claim 11, wherein the ticket dump comprises at least one of a ticket identification (ID) 212, a ticket number 214, a ticket title 216, a problem description 220, a resolution category and a resolution description 222 associated with each ticket.

13. The enterprise system as claimed in claim 11, wherein each of the one or more data sources comprises a ticket description 218, a resolution date 224 and a resolution time 226.

14. The enterprise system as claimed in claim 10, wherein to process the input data to obtain the structured data 228, the instructions cause the processor 204 to:
filter ticket description 218 of the input data using at least one parameter associated with a ticket of the plurality of tickets to obtain a first filtered data 230;
filter resolution description 222 of the input data using the at least one parameter associated with the ticket to obtain a second filtered data 232; and
obtain the structured data 228 associated with each of the plurality of tickets using the first filtered data 230 and second filtered data 232.

15. The enterprise system as claimed in claim 14, wherein to perform multi-level clustering on the structured data 228, the instructions cause the processor 204 to:
map data associated with the first filtered data 230 and the second filtered data 232 based on a plurality of first error indicators 234, to obtain a first cluster group 236;
map data associated with the first filtered data 230 and the second filtered data 232 based on a plurality of second error indicators 238 encountered by a user, to obtain a second cluster group 240; and
map each of the error indicators associated with the first cluster group 236 and the second cluster group 240 based on a resolution obtained to generate a third cluster group 242.

16. The enterprise system as claimed in claim 10, wherein to map each cluster of the plurality of clusters with each of the error indicators, the instructions causes the processor 204 to:
obtain a relationship for each of the plurality of clusters with the error indicators using modified natural language processing (NLP);
identify a root node using the obtained relationship for each of the plurality of clusters with the error indicators;
generate a relationship from a higher level of the cluster to next level of the cluster using the root node; and
align the relationships for each of the plurality of clusters from a higher level to a lower level.

17. The enterprise system as claimed in claim 10, wherein the mapped data at each of the plurality of clusters comprises a root error indicator 244 corresponding to each of the plurality of clusters.

18. The enterprise system as claimed in claim 17, wherein to generate the ontology using the mapped data at each cluster of the plurality of clusters, the instructions causes the processor 204 to group each of the plurality of clusters based on the root error indicator 244.

Dated this 17th day of February, 2017

SRAVAN KUMAR GAMPA
OF K & S PARTNERS
AGENT FOR THE APPLICANT
, Description:
TECHNICAL FIELD
The present subject matter is related, in general to an enterprise system, and more particularly, but not exclusively to a method and a system for generating an ontology based on a plurality of tickets.

Documents

Orders

Section Controller Decision Date

Application Documents

# Name Date
1 201741005774-IntimationOfGrant28-07-2023.pdf 2023-07-28
1 Power of Attorney [17-02-2017(online)].pdf 2017-02-17
2 201741005774-PatentCertificate28-07-2023.pdf 2023-07-28
2 Form 5 [17-02-2017(online)].pdf 2017-02-17
3 Form 3 [17-02-2017(online)].pdf 2017-02-17
3 201741005774-Written submissions and relevant documents [27-07-2023(online)].pdf 2023-07-27
4 Form 18 [17-02-2017(online)].pdf_296.pdf 2017-02-17
4 201741005774-AMENDED DOCUMENTS [07-07-2023(online)].pdf 2023-07-07
5 Form 18 [17-02-2017(online)].pdf 2017-02-17
5 201741005774-Correspondence to notify the Controller [07-07-2023(online)].pdf 2023-07-07
6 Drawing [17-02-2017(online)].pdf 2017-02-17
6 201741005774-FORM 13 [07-07-2023(online)].pdf 2023-07-07
7 Description(Complete) [17-02-2017(online)].pdf_295.pdf 2017-02-17
7 201741005774-POA [07-07-2023(online)].pdf 2023-07-07
8 Description(Complete) [17-02-2017(online)].pdf 2017-02-17
8 201741005774-US(14)-HearingNotice-(HearingDate-13-07-2023).pdf 2023-07-03
9 201741005774-FER.pdf 2021-10-17
9 REQUEST FOR CERTIFIED COPY [22-02-2017(online)].pdf 2017-02-22
10 201741005774-CLAIMS [16-02-2021(online)].pdf 2021-02-16
10 PROOF OF RIGHT [07-06-2017(online)].pdf 2017-06-07
11 201741005774-COMPLETE SPECIFICATION [16-02-2021(online)].pdf 2021-02-16
11 Correspondence by Agent_Form 1_12-06-2017.pdf 2017-06-12
12 201741005774-CORRESPONDENCE [16-02-2021(online)].pdf 2021-02-16
12 abstract201741005774.jpg 2017-06-15
13 201741005774-DRAWING [16-02-2021(online)].pdf 2021-02-16
13 201741005774-RELEVANT DOCUMENTS [16-02-2021(online)].pdf 2021-02-16
14 201741005774-FER_SER_REPLY [16-02-2021(online)].pdf 2021-02-16
14 201741005774-PETITION UNDER RULE 137 [16-02-2021(online)].pdf 2021-02-16
15 201741005774-FORM 3 [16-02-2021(online)].pdf 2021-02-16
15 201741005774-OTHERS [16-02-2021(online)].pdf 2021-02-16
16 201741005774-Information under section 8(2) [16-02-2021(online)].pdf 2021-02-16
17 201741005774-OTHERS [16-02-2021(online)].pdf 2021-02-16
17 201741005774-FORM 3 [16-02-2021(online)].pdf 2021-02-16
18 201741005774-PETITION UNDER RULE 137 [16-02-2021(online)].pdf 2021-02-16
18 201741005774-FER_SER_REPLY [16-02-2021(online)].pdf 2021-02-16
19 201741005774-DRAWING [16-02-2021(online)].pdf 2021-02-16
19 201741005774-RELEVANT DOCUMENTS [16-02-2021(online)].pdf 2021-02-16
20 201741005774-CORRESPONDENCE [16-02-2021(online)].pdf 2021-02-16
20 abstract201741005774.jpg 2017-06-15
21 201741005774-COMPLETE SPECIFICATION [16-02-2021(online)].pdf 2021-02-16
21 Correspondence by Agent_Form 1_12-06-2017.pdf 2017-06-12
22 201741005774-CLAIMS [16-02-2021(online)].pdf 2021-02-16
22 PROOF OF RIGHT [07-06-2017(online)].pdf 2017-06-07
23 201741005774-FER.pdf 2021-10-17
23 REQUEST FOR CERTIFIED COPY [22-02-2017(online)].pdf 2017-02-22
24 Description(Complete) [17-02-2017(online)].pdf 2017-02-17
24 201741005774-US(14)-HearingNotice-(HearingDate-13-07-2023).pdf 2023-07-03
25 Description(Complete) [17-02-2017(online)].pdf_295.pdf 2017-02-17
25 201741005774-POA [07-07-2023(online)].pdf 2023-07-07
26 Drawing [17-02-2017(online)].pdf 2017-02-17
26 201741005774-FORM 13 [07-07-2023(online)].pdf 2023-07-07
27 Form 18 [17-02-2017(online)].pdf 2017-02-17
27 201741005774-Correspondence to notify the Controller [07-07-2023(online)].pdf 2023-07-07
28 Form 18 [17-02-2017(online)].pdf_296.pdf 2017-02-17
28 201741005774-AMENDED DOCUMENTS [07-07-2023(online)].pdf 2023-07-07
29 Form 3 [17-02-2017(online)].pdf 2017-02-17
29 201741005774-Written submissions and relevant documents [27-07-2023(online)].pdf 2023-07-27
30 Form 5 [17-02-2017(online)].pdf 2017-02-17
30 201741005774-PatentCertificate28-07-2023.pdf 2023-07-28
31 201741005774-IntimationOfGrant28-07-2023.pdf 2023-07-28
31 Power of Attorney [17-02-2017(online)].pdf 2017-02-17

Search Strategy

1 SearchStrategyE_09-09-2020.pdf

ERegister / Renewals

3rd: 16 Oct 2023

From 17/02/2019 - To 17/02/2020

4th: 16 Oct 2023

From 17/02/2020 - To 17/02/2021

5th: 16 Oct 2023

From 17/02/2021 - To 17/02/2022

6th: 16 Oct 2023

From 17/02/2022 - To 17/02/2023

7th: 16 Oct 2023

From 17/02/2023 - To 17/02/2024

8th: 15 Feb 2024

From 17/02/2024 - To 17/02/2025

9th: 15 Feb 2025

From 17/02/2025 - To 17/02/2026