System, method, and computer program for automatically remediating fallouts in an ordering system of a consumer telecommunications network

• US 10,282,775 B1
• Filed: 04/16/2014
• Issued: 05/07/2019
• Est. Priority Date: 05/08/2013
• Status: Active Grant

• Current Assignee: Amdocs Development Limited (Amdocs Ltd.), Amdocs Software Systems Limited (Amdocs Ltd.)
• Original Assignee: Amdocs Development Limited (Amdocs Ltd.)
• Inventors: Guez, Yoav, Eini, Yakov, Sadan, Tomer
• Primary Examiner(s): Smith, Jeffrey A.
• Assistant Examiner(s): Smith, Lindsey B
• Application Number:
  US14/254,754
• Time in Patent Office: 1,847 Days
• Field of Search: 714100-800, 705 261- 272
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 30/0635 Processing of requisition or of purchase orders
• CPC Class Codes: G06Q 30/0637 Approvals
• CPC Class Codes: G06Q 30/0641 Shopping interfaces

Abstract

A system, method, and computer program product are provided for automatically remediating fallouts in an ordering system of a consumer telecommunications network. In use, one or more fallout errors are detected in one or more ordering systems associated with a consumer telecommunications network. Information associated with the one or more fallout errors is stored in a fallout error repository associated with the one or more ordering systems. Additionally, it is determined whether the one or more fallout errors are known fallout errors associated with one or more automatic processes for remediating the one or more fallout errors. Further, the one or more fallout errors are automatically remediated utilizing the one or more automatic processes for remediating the one or more fallout errors, in response to determining that the one or more fallout errors are known fallout errors associated with one or more automatic processes for remediating the one or more fallout errors.

Claims

1. A computer program product embodied on a non-transitory computer readable medium, comprising computer code for:

capturing, by one or more ordering systems associated with a consumer telecommunications network, orders for one or more services and activating the one or more services responsive to the orders;

detecting, by the one or more ordering systems, one or more fallout errors from information gathered from invoked application programming interfaces (APIs) of one or more monitored systems, the one or more fallout errors each preventing an associated order from being completed;

storing, by the one or more ordering systems in a fallout error repository associated with the one or more ordering systems, previously detected fallout errors and associated automatic processes previously utilized by the one or more ordering systems for remediating the one or more previously detected fallout errors;

determining, by the one or more ordering systems, whether the one or more fallout errors are included in the fallout error repository;

when an ordering system of the one or more ordering systems determine that a fallout error of the one or more fallout errors is not included in the fallout error repository;

updating, by the ordering system, the fallout error repository to include the fallout error and an indication that the fallout error will be resolved manually, and

triggering, by the ordering system, an application programming interface (API) to a ticketing system to open a manual handling ticket for use by one or more users to manually resolve the fallout error; and

when an ordering system of the one or more ordering systems determine that a fallout error of the one or more fallout errors is included in the fallout error repository;

updating, by the ordering system, a fallout status of the fallout error in the fallout error repository to indicate that the fallout error is being handled automatically,

automatically remediating, by the ordering system, the fallout error utilizing the associated automatic process in the fallout error repository for remediating the fallout error, and

confirming, by the ordering system, whether the fallout error was fixed by repeatedly checking a status of the order associated with the fallout error over a predetermined time period,

when the ordering system confirms within the predetermined time period that the fallout error was fixed, updating by the ordering system the fallout status to indicate that the fallout error was fixed, and

when the ordering system does not confirm within the predetermined time period that the fallout error was fixed, updating by the ordering system the fallout status to indicate that the fallout error was not fixed and triggering the API to the ticketing system to open the manual handling ticket for use by the one or more users to manually resolve the fallout error.

2. The computer program product of claim 1, wherein the computer program product is operable such that the one or more ordering systems includes a plurality of ordering sub-systems.

3. The computer program product of claim 2, wherein the computer program product is operable such that the one or more fallout errors are detected in a first subset of the plurality of ordering sub-systems.

4. The computer program product of claim 3, further comprising computer code for determining a second subset of the plurality of ordering sub-systems in which to remediate the one or more fallout errors.

5. The computer program product of claim 1, further comprising computer code for receiving a security authentication from one or more systems associated with a service provider of the consumer telecommunications network for use in the automatic remediation.

6. The computer program product of claim 1, wherein the computer program product is operable such that the automatic remediation includes performing screen scraping for gathering information and invoking actions.

7. The computer program product of claim 1, wherein the automatic remediation correcting an issue associated with the one or more of the hardware processor, the hardware memory, or the database.

8. A method, comprising:

capturing, by one or more ordering systems associated with a consumer telecommunications network, orders for one or more services and activating the one or more services responsive to the orders;

detecting, by the one or more ordering systems, one or more fallout errors from information gathered from invoked application programming interfaces (APIs) of one or more monitored systems, the one or more fallout errors each preventing an associated order from being completed;

storing, by the one or more ordering systems in a fallout error repository associated with the one or more ordering systems, previously detected fallout errors and associated automatic processes previously utilized by the one or more ordering systems for remediating the one or more previously detected fallout errors;

determining, by the one or more ordering systems, whether the one or more fallout errors are included in the fallout error repository;

when an ordering system of the one or more ordering systems determine that a fallout error of the one or more fallout errors is not included in the fallout error repository;

updating, by the ordering system, the fallout error repository to include the fallout error and an indication that the fallout error will be resolved manually, and

triggering, by the ordering system, an application programming interface (API) to a ticketing system to open a manual handling ticket for use by one or more users to manually resolve the fallout error; and

when an ordering system of the one or more ordering systems determine that a fallout error of the one or more fallout errors is included in the fallout error repository;

updating, by the ordering system, a fallout status of the fallout error in the fallout error repository to indicate that the fallout error is being handled automatically,

automatically remediating, by the ordering system, the fallout error utilizing the associated automatic process in the fallout error repository for remediating the fallout error, and

confirming, by the ordering system, whether the fallout error was fixed by repeatedly checking a status of the order associated with the fallout error over a predetermined time period,

when the ordering system confirms within the predetermined time period that the fallout error was fixed, updating by the ordering system the fallout status to indicate that the fallout error was fixed, and

when the ordering system does not confirm within the predetermined time period that the fallout error was fixed, updating by the ordering system the fallout status to indicate that the fallout error was not fixed and triggering the API to the ticketing system to open the manual handling ticket for use by the one or more users to manually resolve the fallout error.

9. A system comprising:

a memory system in one or more ordering systems; and

one or more processing cores in the one or more ordering systems and coupled to the memory system and that are each configured for;

capturing, by one or more ordering systems associated with a consumer telecommunications network, orders for one or more services and activating the one or more services responsive to the orders;

detecting, by the one or more ordering systems, one or more fallout errors from information gathered from invoked application programming interfaces (APIs) of one or more monitored systems, the one or more fallout errors each preventing an associated order from being completed;

storing, by the one or more ordering systems in a fallout error repository associated with the one or more ordering systems, previously detected fallout errors and associated automatic processes previously utilized by the one or more ordering systems for remediating the one or more previously detected fallout errors;

determining, by the one or more ordering systems, whether the one or more fallout errors are included in the fallout error repository;

when an ordering system of the one or more ordering systems determine that a fallout error of the one or more fallout errors is not included in the fallout error repository;

updating, by the ordering system, the fallout error repository to include the fallout error and an indication that the fallout error will be resolved manually, and

triggering, by the ordering system, an application programming interface (API) to a ticketing system to open a manual handling ticket for use by one or more users to manually resolve the fallout error; and

when an ordering system of the one or more ordering systems determine that a fallout error of the one or more fallout errors is included in the fallout error repository;

updating, by the ordering system, a fallout status of the fallout error in the fallout error repository to indicate that the fallout error is being handled automatically,

automatically remediating, by the ordering system, the fallout error utilizing the associated automatic process in the fallout error repository for remediating the fallout error, and

confirming, by the ordering system, whether the fallout error was fixed by repeatedly checking a status of the order associated with the fallout error over a predetermined time period,

when the ordering system confirms within the predetermined time period that the fallout error was fixed, updating by the ordering system the fallout status to indicate that the fallout error was fixed, and

when the ordering system does not confirm within the predetermined time period that the fallout error was fixed, updating by the ordering system the fallout status to indicate that the fallout error was not fixed and triggering the API to the ticketing system to open the manual handling ticket for use by the one or more users to manually resolve the fallout error.