IP Library › Granted Patent US 12,235,716
Granted Patent B2
US 12,235,716 · App. 18/496,367 · Granted Feb 25, 2025

Message call request data having error frequency metrics

Inventors: Anand Muralidharan (Chennai, IN); Kingbert Thomas (Chennai, IN); Balasubramanian Paulraj (Chennai, IN); Venkateshkumar Muthu (Chennai, IN); Vidyavathi Vennapusa (Chennai, IN); Gareth Harries (Surrey, GB); Neil Hopkins (Bristol, GB); Subramaniam Ramalingasamy (Chennai, IN); Raja Ambigapathy Karuppasamy (Chennai, IN); James Reilly (Surrey, GB)
Assignee: ADP, Inc.
G06F11/0769G06F11/0751G06F11/302G06F11/3065G06F11/3086G06F11/327G06F12/0875G06F2212/1021
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,235,716
App. No.
18/496,367
Filed
Oct 27, 2023
Granted
Feb 25, 2025
Kind
B2
Art Unit
2113
USPC
714/57
Abstract

A method for error management is provided. The method comprises receiving a message call request regarding an error event generated by a software application. The message call request comprises a message ID associated with an error type. In response to the call request a message cache is searched for the message ID. If the ID is in the cache, an error message associated with the ID is returned. The error message provides a description of the error and suggested remedial action. If the message ID is not in the cache, the error message is fetched from a message repository that contains error messages corresponding to respective message IDs. The fetched error message is loaded into the cache and returned. Message call request data is stored in a metrics repository. The message call request data comprises frequency metrics that describe how often the message ID is received.

Claims (66)

1. A system, comprising:

one or more processors coupled with memory, wherein the one or more processors are configured to:

identify, responsive to a message call request to report an error detected in a software application accessed by a client device, an error message to be provided to the client device, the message call request comprising a message identification (“ID”) associated with the error;

receive, responsive to a determination that the message ID is absent from a cache, via an interface in a container image configured to provide access to a message repository, the error message from the message repository;

determine, based on a comparison of an error metric associated with the error and a threshold, to update the error message for a type of the error;

generate, responsive to the determination to update the error message, an updated error message based on the error message; and

transmit, to one or more client devices, in response to one or more message call requests related to the type of the error, the updated error message.

2. The system of claim 1 , wherein the one or more processors are further configured to:

fetch, responsive to the determination that the message ID is absent from the cache, the error message associated with the message ID from the message repository, wherein the message repository contains a plurality of error messages corresponding to respective message IDs; and

store the error message for the message ID in the cache.

3. The system of claim 2 , wherein to fetch the error message, the one or more processors are further configured to:

forward an application programming interface call to a service to access a registry holding container images of a message cloud interface configured to allow access to the message repository.

4. The system of claim 2 , wherein the one or more processors are further configured to:

receive a second message call request for a second error detected in the software application accessed by a second client device, the second message call request comprising the message ID;

determine the message ID is stored in the cache;

retrieve, from the cache, the error message responsive to the message ID; and

provide, to the second client device, the error message retrieved from the cache.

5. The system of claim 1 , wherein to generate the updated error message, the one or more processors are further configured to:

receive, via a repository management interface, a revised description for the error message; and

create the updated error message with the revised description.

6. The system of claim 1 , wherein to generate the updated error message, the one or more processors are further configured to:

configure the error message with an interactive user interface element.

7. The system of claim 1 , wherein to generate the updated error message, the one or more processors are further configured to:

add an expandable element to the error message, the expandable element configured to provide at least one of additional details or a corrective action.

8. The system of claim 1 , wherein to generate the updated error message, the one or more processors are further configured to:

add an interactive user interface element to the error message, the interactive user interface element configured to access a chat feature.

9. The system of claim 1 , wherein the one or more processors are further configured to:

receive a second message call request for a second error detected in the software application accessed by a second client device, the second message call request related to the type of the error; and

provide the updated error message to the second client device, the updated error message displayed via the software application accessed by the second client device without an update being applied to the software application.

10. The system of claim 1 , wherein the error message comprises at least one of text, video, audio, a hyperlink, a uniform resource locator, chat, or multilingual language support.

11. The system of claim 1 , wherein the threshold comprises a frequency threshold, and the one or more processors are further configured to:

receive message call requests from a plurality of client devices that access the software application;

determine one or more types of error messages from the message call requests; and

generate, based on the one or more types of error messages and a count of the message call requests received from the plurality of client devices, the error metric comprising a frequency of occurrence of the type of the error message.

12. The system of claim 1 , wherein the one or more processors are further configured to:

provide an analytics dashboard comprising one or more error metrics related to message call requests received from a plurality of client devices that access the software application.

13. A method, comprising:

identifying, by one or more processors coupled with memory, responsive to a message call request to report an error detected in a software application accessed by a client device, an error message to be provided to the client device, the message call request comprising a message identification (“ID”) associated with the error;

receiving, by the one or more processors, responsive to a determination that the message ID is absent from a cache, via an interface in a container image configured to provide access to a message repository, the error message from the message repository;

determining, by the one or more processors, based on a comparison of an error metric associated with the error and a threshold, to update the error message for a type of the error;

generating, by the one or more processors responsive to determining to update the error message, an updated error message based on the error message; and

transmitting, by the one or more processors to one or more client devices, in response to one or more message call requests related to the type of the error, the updated error message.

14. The method of claim 13 , comprising:

fetching, by the one or more processors, responsive to the determination that the message ID is absent from the cache, the error message associated with the message ID from the message repository, wherein the message repository contains a plurality of error messages corresponding to respective message IDs; and

storing, by the one or more processors, the error message for the message ID in the cache.

15. The method of claim 14 , wherein fetching the error message further comprises:

forwarding, by the one or more processors, an application programming interface call to a service to access a registry holding container images of a message cloud interface configured to allow access to the message repository.

16. The method of claim 14 , comprising:

receiving, by the one or more processors, a second message call request for a second error detected in the software application accessed by a second client device, the second message call request comprising the message ID;

determining, by the one or more processors, the message ID is stored in the cache;

retrieving, by the one or more processors from the cache, the error message responsive to the message ID; and

providing, by the one or more processors to the second client device, an indication of the error message retrieved from the cache.

17. The method of claim 13 , wherein generating the updated error message further comprises:

configuring, by the one or more processors, the error message with an interactive user interface element.

18. The method of claim 13 , wherein generating the updated error message further comprises:

adding, by the one or more processors, an expandable element to the error message, the expandable element configured to provide at least one of additional details or a corrective action.

19. The method of claim 13 , wherein the threshold comprises a frequency threshold, and the method further comprises:

receiving, by the one or more processors, message call requests from a plurality of client devices that access the software application;

determining, by the one or more processors, one or more types of error messages from the message call requests; and

generating, by the one or more processors, based on the one or more types of error messages and a count of the message call requests received from the plurality of client devices, the error metric comprising a frequency of occurrence of the type of the error message.

20. A non-transitory computer-readable medium storing processor executable instructions, wherein the processor executable instructions executed by one or more processors cause the one or more processors to:

identify, responsive to a message call request to report an error detected in a software application accessed by a client device, an error message to be provided to the client device, the message call request comprising a message identification (“ID”) associated with the error;

receive, responsive to a determination that the message ID is absent from a cache, via an interface in a container image configured to provide access to a message repository, the error message from the message repository;

determine, based on a comparison of an error metric associated with the error and a threshold, to update the error message for a type of the error;

generate, responsive to the determination to update the error message, an updated error message based on the error message; and

transmit, to one or more client devices, in response to one or more message call requests related to the type of the error, the updated error message.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 22, 2025
From: MURALIDHARAN, ANAND; THOMAS, KINGBERT; PAULRAJ, BALASUBRAMANIAN; MUTHU, VENKATESHKUMAR; VENNAPUSA, VIDYAVATHI; HARRIES, GARETH; HOPKINS, NEIL; RAMALINGASAMY, SUBRAMANIAM; KARUPPASAMY, RAJA AMBIGAPATHY; REILLY, JAMES
To: ADP, INC.
Reel/Frame 069970/0377 →
Continuity (2)
Continuation 17305676 · Jul 13, 2021
Related Publication 20240061737A1 · Feb 22, 2024
References Cited (15)
US 9798607B1 · Kulkarni et al. · 2017 [cited by applicant]
US 10783053B1 · Demeuse et al. · 2020 [cited by applicant]
US 11269712B1 · Ahmed et al. · 2022 [cited by applicant]
US 11411811B2 · Paradkar et al. · 2022 [cited by applicant]
US 11803438B2 · Muralidharan · 2023 [cited by examiner]
US 20050138486A1 · Gromyko · 2005 [cited by applicant]
US 20100100777A1 · Ziegler · 2010 [cited by applicant]
US 20140068343A1 · Nakajima et al. · 2014 [cited by applicant]
US 20180005246A1 · Basam · 2018 [cited by examiner]
US 20190026172A1 · Wu et al. · 2019 [cited by applicant]
US 20200201699A1 · Yu et al. · 2020 [cited by applicant]
US 20200394091A1 · Kokubun et al. · 2020 [cited by applicant]
Notice of Allowance issued in corresponding U.S. Appl. No. 17/305,676, dated Jun. 28, 2023 (5 pages). [cited by applicant]
US Office Action issued in corresponding U.S. Appl. No. 17/305,676, dated Apr. 19, 2023 (13 pages). [cited by applicant]
US Office Action issued in corresponding U.S. Appl. No. 17/305,676, dated Aug. 17, 2022 (11 pages). [cited by applicant]