Latent Intent Clustering in High Latent Spaces
US-2022083568-A1 · Mar 17, 2022 · US
US12111718B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12111718-B2 |
| Application number | US-202117373107-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 12, 2021 |
| Priority date | May 26, 2021 |
| Publication date | Oct 8, 2024 |
| Grant date | Oct 8, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and methods of reconstructing execution call flows to detect anomalies are provided. A device can establish call flows using information extracted from a log file. Each of the call flows can identify information from the log file of a call flowing through a plurality of modules. The device can identify a count of a number of occurrences of one or more keywords in information of each call flow. The device can generate a vector of numbers for each call flow based at least on the count for the one or more keywords for that call flow. The device can classify each call flow into one or more clusters that indicate whether an operation of the call flow is anomalous. The device can classify each call flow using the vector of numbers for each call flow.
Opening claim text (preview).
What is claimed is: 1. A method comprising: establishing, by one or more processors using information extracted from a log file, a plurality of call flows, each of the plurality of call flows identifying information from the log file of a call flowing through a plurality of modules in accessing an application, the one or more processors extracting the information from the log file for each call flow of the plurality of call flows based at least on a timestamp, each call flow having a common unique transaction identifier and information from the log file for each call flow identified by the common unique transaction identifier; identifying, by the one or more processors, a count of a number of occurrences of one or more natural language keywords from the log file in information of each call flow of the plurality of call flows; generate, by the one or more processors, a vector of numbers for each call flow based at least on the count for the one or more keywords for that call flow; and classifying, by the one or more processors using the vector of numbers for each call flow, each call flow into one or more clusters, each of the one or more clusters identifying which modules are performing better than other modules of the plurality of modules; and updating, by the one or more processors, a configuration of one or more of the other modules in accessing the application based at least on the one or more clusters. 2. The method of claim 1 , further comprising sorting, by the one or more processors, identifiers of modules for each call flow by the timestamps for each unique transaction identifier. 3. The method of claim 1 , further comprising converting, by the one or more processors, alpha numeric data from the extracted information for each call flow to a numeric representation of each call flow in the form of the vector of numbers. 4. The method of claim 1 , further comprising: establishing a dictionary of keywords for each call flow of the plurality of call flows based on common keywords of the call flow; and identifying the count of the number of occurrences for each keyword in the dictionary of keywords for the corresponding call flow. 5. The method of claim 1 , further comprising classifying, by the one or more processors, using a k-means clustering function each call flow of the plurality of call flows into the one or more clusters to identify call flows of the plurality of call flows with common characteristics. 6. The method of claim 1 , further comprising classifying, by the one or more processors, each call flow into a cluster of the one or more clusters based on a cosine similarity of each call flow to a baseline vector of each of the one or more clusters. 7. The method of claim 1 , further comprising: identifying, by the one or more processors, a mean cosine similarity for each of the one or more clusters; determining, by the one or more processors, a cosine similarity for a call flow of the plurality of call flows with each of the one or more clusters; and classifying, by the one or more processors, the call flow into a cluster of the one or more clusters based on the cosine similarity for the call flow with the cluster being greater than or equal to the mean cosine similarity for the cluster. 8. The method of claim 1 , further comprising identifying, by the one or more processors based at least on the one or more clusters, which one or more modules of the plurality of modules are operating anomalously. 9. A system to identify anomalous calls flowing through modules, comprising: a device comprising one or more processors coupled to memory, the device to: establish, using information extracted from a log file, a plurality of call flows, each of the plurality of call flows identifying information from the log file of a call flowing through a plurality of modules in accessing an application, wherein the information is extracted from the log file for each call flow of the plurality of call flows based at least on a timestamp, each call flow having a common unique transaction identifier and information from the log file for each call flow identified by the common unique transaction identifier; identify a count of a number of occurrences of one or more natural language keywords from the log file in information of each call flow of the plurality of call flows; generate a vector of numbers for each call flow based at least on the count for the one or more keywords for that call flow; classify, using the vector of numbers for each call flow, each call flow into one or more clusters that indicate whether an operation of the call flow is anomalous; and update a configuration of one or more of the other modules in accessing the application based at least on the one or more clusters. 10. The system of claim 9 , wherein the device is further configured to sort identifiers of modules for each call flow by the timestamps for each unique transaction identifier. 11. The system of claim 9 , wherein the device is further configured to convert alpha numeric data from the extracted information for each call flow to a numeric representation of each call flow in the form of the vector of numbers. 12. The system of claim 9 , wherein the device is further configured to: establish a dictionary of keywords for each call flow of the plurality of call flows based on common keywords of the call flow; and identify the count of the number of occurrences for each keyword in the dictionary of keywords for the corresponding call flow. 13. The system of claim 9 , wherein the device is further configured to classify, using a k-means clustering function, each call flow of the plurality of call flows into the one or more clusters to identify call flows of the plurality of call flows with common characteristics. 14. The system of claim 9 , wherein the device is further configured to classify each call flow into a cluster of the one or more clusters based on a cosine similarity of each call flow to a baseline vector of each of the one or more clusters. 15. The system of claim 9 , wherein the device is further configured to: identify a mean cosine similarity for each of the one or more clusters; determine cosine similarity for a call flow of the plurality of call flows with each of the one or more clusters; and classify the call flow into a cluster of the one or more clusters based on the cosine similarity for the call flow with the cluster being greater than or equal to the mean cosine similarity for the cluster. 16. The system of claim 9 , wherein the device is further configured to identify, based at least on the one or more clusters, which one or more modules of the plurality of modules are operating anomalously. 17. A non-transitory computer readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to identify anomalous calls flowing through modules, the instructions comprising instructions to: establish, using information extracted from a log file, a plurality of call flows, each of the plurality of call flows identifying information from the log file of a call flowing through a plurality of modules, the information extracted from the log file for each call flow of the plurality of call flows based at least on a timestamp, each call flow having a common unique transaction identifier and information from the log file for each call flow identified by the common unique transaction identifier; identify a count of a number of occurrences of one or more natural language keywords from the log file in information of each call flow of t
within a central processing unit [CPU] · CPC title
Clustering or classification · CPC title
Traffic logging, e.g. anomaly detection · CPC title
Error or fault detection not based on redundancy (power supply failures G06F1/30; network fault management H04L41/06) · CPC title
Machine learning · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.