Automated ticket resolution

US10380520B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10380520-B2
Application numberUS-201715645440-A
CountryUS
Kind codeB2
Filing dateJul 10, 2017
Priority dateMar 13, 2017
Publication dateAug 13, 2019
Grant dateAug 13, 2019

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.

A device may communicate with a server to obtain historical ticket data. The device may generate a data model, based on the historical ticket data. The device may communicate with a client device to obtain ticket data relating to an issue associated with a project. The device may classify, using the data model, the ticket data into a ticket type. The device may generate, using the data model and based on the ticket type, a set of recommended resolutions for resolving the issue associated with the project. The device may select, from the set of recommended resolutions, a particular resolution based on a set of selection criteria. The device may automatically perform one or more actions to implement the particular resolution to resolve the issue associated with the project.

First claim

Opening claim text (preview).

What is claimed is: 1. A device, comprising: a memory storing instructions; and one or more processors to execute the instructions to: communicate with a server to obtain historical ticket data; generate a plurality of data models based on processing the historical ticket data, a different data model, of the plurality of data models, being generated for a different ticket type in the historical ticket data; communicate with a client device to obtain ticket data relating to an issue associated with a project; classify, using a particular data model of the plurality of data models to apply a natural language processing technique, the ticket data into a first ticket type; train the particular data model by receiving an indication as to whether to modify a classification of the ticket data from the first ticket type to a second ticket type; modify, based on receiving the indication, the classification of the ticket data from the first ticket type to the second ticket type; process, using the particular data model based on training the particular data model and based on modifying the classification of the ticket data, a subset of the historical ticket data; generate, using the particular data model and based on processing the subset of the historical ticket data, a set of recommended resolutions for resolving the issue; select, from the set of recommended resolutions, a particular resolution based on one or more values that indicate an effectiveness level of the particular resolution for one or more issues associated with the historical ticket data; perform one or more actions to implement the particular resolution to resolve the issue, the one or more actions being based on the issue being internal to the device and including at least one of: an automatic generation of additional code directed to resolving the issue, an automatic alteration of existing code of the project to produce altered code directed to resolving the issue, or an automatic removal of existing code of the project to resolve the issue; apply a machine learning technique to one or more of the ticket data or the historical ticket data, the machine learning technique being applied to predict another issue; generate additional ticket data based on predicting the other issue, the additional ticket data being different than the ticket data or the historical ticket data; and generate, using the particular data model, another set of recommended resolutions for resolving the other issue. 2. The device of claim 1 , where the one or more processors, when communicating with the client device to obtain the ticket data, are to: provide, for display on the client device, a user interface that includes one or more fields associated with the ticket data, and automatically populate at least a portion of the one or more fields associated with the ticket data by applying the natural language processing technique. 3. The device of claim 1 , where the one or more processors are further to: parse information included in the ticket data using the natural language processing technique, and compare the information included in the ticket data and information included in the historical ticket data, and where the one or more processors, when classifying the ticket data into the first ticket type, are to: automatically classify the ticket data into the first ticket type based on comparing the ticket data and the historical ticket data. 4. The device of claim 1 , where the set of recommended resolutions is a first set of recommended resolutions; where the other set of recommended resolutions is a second set of recommended resolutions; and where the one or more processors are further to: determine that the particular resolution did not succeed; obtain additional historical ticket data based on determining that the particular resolution did not succeed; process at least a portion of the additional historical ticket data; and generate a third set of recommended resolutions based on the portion of the additional historical ticket data. 5. The device of claim 1 , where the one or more actions include: a determination of a developer to resolve the issue; and a communication with the client device to provide information associated with the particular resolution and the issue to the developer to cause the issue to be resolved. 6. The device of claim 1 , where the particular resolution is a first resolution; and where the one or more processors are to: provide, for display via a user interface, information identifying a second resolution of the set of recommended resolutions; detect, via the user interface, a user interaction associated with whether to implement the second resolution or another resolution of the set of recommended resolutions; and store information associated with whether the user interface indicated to implement the second resolution or the other resolution. 7. A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by one or more processors of a device, cause the one or more processors to: communicate with a server to obtain historical ticket data; generate a plurality of data models based on processing the historical ticket data, a different data model, of the plurality of data models, being generated for a different ticket type in the historical ticket data; communicate with a client device to obtain ticket data relating to an issue associated with a project; classify, using a particular data model of the plurality of data models to apply a natural language processing technique, the ticket data into a first ticket type; train the particular data model by receiving an indication as to whether to modify a classification of the ticket data from the first ticket type to a second ticket type; modify, based on receiving the indication, the classification of the ticket data from the first ticket type to the second ticket type; process, using the particular data model based on training the data model and based on modifying the classification of the ticket data, a subset of the historical ticket data; generate, using the particular data model and based on processing the subset of the historical ticket data, a set of recommended resolutions for resolving the issue; select, from the set of recommended resolutions, a particular resolution based on one or more values that indicate an effectiveness level of the particular resolution for one or more issues associated with the ticket data; perform one or more actions to implement the particular resolution to resolve the issue, the one or more actions being based on the issue being internal to the device and including at least one of: an automatic generation of additional code directed to resolving the issue, an automatic alteration of existing code of the project to produce altered code directed to resolving the issue, or an automatic removal of existing code of the project to resolve the issue; apply a machine learning technique to one or more of the ticket data or the historical ticket data, the machine learning technique being applied to predict another issue; generate additional ticket data based on predicting the other issue, the additional ticket data being different than the ticket data or the historical ticket data; and generate, using the particular data model, another set of recommended resolutions for resolving the other issue. 8. The non-transitory computer-readable medium of claim 7 , where the particular resolution is a first particular resolution; and where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: rec

Assignees

Inventors

Classifications

  • Handling of user complaints or trouble tickets · CPC title

  • using machine learning or artificial intelligence · CPC title

  • Resource planning in a project environment · CPC title

  • wherein the managed service relates to distributed or central networked applications · CPC title

  • Inference or reasoning models · 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 US10380520B2 cover?
A device may communicate with a server to obtain historical ticket data. The device may generate a data model, based on the historical ticket data. The device may communicate with a client device to obtain ticket data relating to an issue associated with a project. The device may classify, using the data model, the ticket data into a ticket type. The device may generate, using the data model an…
Who is the assignee on this patent?
Accenture Global Solutions Ltd
What technology area does this patent fall under?
Primary CPC classification G06Q10/063118. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Aug 13 2019 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 3 related publications on this page (citations in our corpus or others sharing the same primary CPC).