System and method for managing automatic service requests for workload management

US12360857B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-12360857-B2
Application numberUS-202318324216-A
CountryUS
Kind codeB2
Filing dateMay 26, 2023
Priority dateMay 26, 2023
Publication dateJul 15, 2025
Grant dateJul 15, 2025

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 method for managing a client environment includes obtaining a notification for an auto-generated service request, wherein the auto-generated service request is associated with an issue with the client environment, in response to the notification: obtaining metadata associated with the auto-generated service request, analyzing the metadata to extract pattern information, comparing the pattern information to a service request pattern database, making a determination, using the service request pattern database, that a recommendation is associated with the pattern information, and based on the determination, performing a remediation action associated with the recommendation.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for managing a client environment, the method comprising: obtaining a notification for an auto-generated service request, wherein the auto-generated service request is associated with an issue with the client environment, wherein the auto-generated service request is generated based on a criticality and a tolerance value of telemetry information associated with an alert, and wherein the alert corresponds to the issue with the client environment; in response to the notification: obtaining metadata associated with the auto-generated service request; analyzing the metadata to extract pattern information; comparing the pattern information to a service request pattern database; making a determination, using the service request pattern database, that a recommendation is associated with the pattern information; and based on the determination, performing a remediation action associated with the recommendation. 2. The method of claim 1 , wherein the metadata comprises application logs, logs of a data protection module, system logs, and alerts. 3. The method of claim 2 , wherein analyzing the metadata comprises: making a second determination that at least one of the system logs specifies a cause of the issue with the client environment; and specifying the at least one of the system logs in the pattern information. 4. The method of claim 1 , wherein the determination is based on the pattern information matching identical pattern information specified in the service request pattern database. 5. The method of claim 1 , wherein the service request pattern database comprises a mapping between the pattern information and the recommendation. 6. The method of claim 5 , wherein the remediation action comprises sending the recommendation to a client device of the client environment using an update notification associated with updating the client environment. 7. The method of claim 1 , further comprising: obtaining a second notification for a second auto-generated service request, wherein the second auto-generated service request is associated with a second issue with the client environment; in response to the second notification: obtaining second metadata associated with the second auto-generated service request; analyzing the second metadata to extract second pattern information; comparing the second pattern information to the service request pattern database; making a second determination, using the service request pattern database, that no recommendation is associated with the second pattern information; based on the second determination, sending the second auto-generated service request to an administrator of the client environment; and updating the service request pattern database based on a response of the administrator to the second auto-generated service request to obtain an updated service request pattern database. 8. The method of claim 1 , wherein the alert specifies at least one of: a client name associated with the alert, an instance identifier of an application associated with the alert, an alert type, an alert message, a number of occurrences within a previous 24 hour period, a tolerance level of the alert, and a resulting action. 9. The method of claim 1 , wherein the alert is associated with a discovery of a node in the client environment. 10. The method of claim 1 , wherein the recommendation specifies that the client environment needs to be reconfigured. 11. A method for managing a client environment, the method comprising: obtaining a notification for an auto-generated service request, wherein the auto-generated service request is associated with an issue with the client environment; in response to the notification: obtaining metadata associated with the auto-generated service request, wherein the metadata comprises application logs, logs of a data protection module, system logs, and alerts, wherein the auto-generated service request is generated based on a criticality and a tolerance value of telemetry information associated with an alert, and wherein the alert corresponds to the issue with the client environment; analyzing the metadata to extract pattern information, wherein analyzing the metadata comprises: making a second determination that at least one of the system logs specifies a cause of the issue with the client environment; and specifying the at least one of the system logs in the pattern information; comparing the pattern information to a service request pattern database; making a determination, using the service request pattern database, that a recommendation is associated with the pattern information; and based on the determination, performing a remediation action associated with the recommendation. 12. The method of claim 11 , wherein the determination is based on the pattern information matching identical pattern information specified in the service request pattern database. 13. The method of claim 11 , wherein the service request pattern database comprises a mapping between the pattern information and the recommendation. 14. The method of claim 13 , wherein the remediation action comprises sending the recommendation to a client device of the client environment using an update notification associated with updating the client environment. 15. A method for managing a client environment, the method comprising: obtaining a notification for an auto-generated service request, wherein the auto-generated service request is associated with an issue with the client environment, wherein the auto-generated service request is generated based on a criticality and a tolerance value of telemetry information associated with an alert, and wherein the alert corresponds to the issue with the client environment; in response to the notification: obtaining metadata associated with the auto-generated service request; analyzing the metadata to extract pattern information; comparing the pattern information to a service request pattern database, wherein the service request pattern database comprises a mapping between the pattern information and a recommendation; making a determination, using the service request pattern database, that the recommendation is associated with the pattern information, wherein the determination is based on the pattern information matching identical pattern information specified in the service request pattern database; and based on the determination, performing a remediation action associated with the recommendation, wherein the remediation action comprises sending the recommendation to a client device of the client environment using an update notification associated with updating the client environment. 16. The method of claim 15 , wherein the metadata comprises application logs, logs of a data protection module, system logs, and alerts. 17. The method of claim 16 , wherein analyzing the metadata comprises: making a second determination that at least one of the system logs specifies a cause of the issue with the client environment; and specifying the at least one of the system logs in the pattern information. 18. The method of claim 15 , wherein the alert specifies at least one of: a client name associated with the alert, an instance identifier of an application associated with the alert, an alert type, an alert message, a number of occurrences within a previous last 24 hour period, a tolerance level, and a resulting action.

Assignees

Inventors

Classifications

  • Change logging, detection, and notification (replication G06F16/27) · CPC title

  • for networked environments · 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 US12360857B2 cover?
A method for managing a client environment includes obtaining a notification for an auto-generated service request, wherein the auto-generated service request is associated with an issue with the client environment, in response to the notification: obtaining metadata associated with the auto-generated service request, analyzing the metadata to extract pattern information, comparing the pattern …
Who is the assignee on this patent?
Dell Products Lp
What technology area does this patent fall under?
Primary CPC classification G06F16/2358. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Jul 15 2025 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 10 related publications on this page (citations in our corpus or others sharing the same primary CPC).