Robotic process automation bot operational management system
Abstract
A device includes a processor and a memory. The processor effectuates operations including monitoring enterprise network traffic associated with one or more user device (UE). The processor further effectuates operations including comparing the enterprise network traffic to a UE profile associated with each of the one or more UE. The processor further effectuates operations including determining whether the comparison indicates that a predetermined threshold has been exceeded. The processor further effectuates operations including in response to the indication that the predetermined threshold has been exceeded, generating an alert, wherein exceeding the predetermined threshold is indicative of a denial of service attack on an enterprise network or an attempt to remove enterprise data via the one or more UE.
Claims
exact text as granted — not AI-modified1 . A device, comprising:
a processor; and a memory coupled with the processor, the memory storing executable instructions that, when executed by the processor, cause the processor to effectuate operations comprising: obtaining, from a network support system associated with a telecommunications network, workflow information that identifies network resources associated with a process of the telecommunications network; deploying, based on the workflow information, one or more robotic process automation (RPA) BOTs in the telecommunications network, wherein the workflow information instructs the one or more RPA BOTs to obtain diagnostic information regarding the telecommunications network; gathering RPA BOT performance data associated with a performance of the one or more RPA BOTs using virtual machines deployed in the telecommunications network; analyzing a status of the one or more RPA BOTs based on the RPA BOT performance data; managing the one or more RPA BOTs based on the status, wherein the managing includes starting, stopping, or rebooting an RPA BOT in the telecommunications network based on the status; monitoring multiple hosted virtual disks (HVDs) for readiness for use; and providing a graphical user interface for facilitating further management of the one or more RPA BOTs in relation to the multiple HVDs, wherein the graphical user interface provides a listing of the multiple HVDs being monitored, information regarding a monitored capacity of each HVD of the multiple HVDs, and a schedule identifying scheduled and available timeslots for the monitored capacity of each HVD of the multiple HVDs.
2 . The device of claim 1 , wherein the managing the one or more RPA BOTs comprises performing one or more actions on the telecommunications network or the one or more RPA BOTs, wherein the obtaining the workflow information comprises obtaining the workflow information from an input file drop, and wherein the operations further comprise providing fallout information to a fallout file drop for transmission to the input file drop.
3 . The device of claim 2 , wherein the one or more actions comprise identifying a BOT failure cause or identifying a record processing failure cause.
4 . The device of claim 1 , wherein the managing the one or more RPA BOTs comprises providing one or more alerts based on the analyzing the status of the one or more RPA BOTs, conducting HVD management, or providing reporting and analytics based on the analyzing the status of the one or more RPA BOTs.
5 . The device of claim 1 , wherein at least some of the one or more RPA BOTs are schedulable to a given HVD of the multiple HVDs according to the schedule thereof for maintenance so as to avoid HVD underutilization or overutilization.
6 . The device of claim 1 , wherein the analyzing the status of the one or more RPA BOTs comprises comparing RPA BOT information derived from the RPA BOT performance data to at least one service level agreement (SLA).
7 . The device of claim 6 , wherein the operations further comprise determining a performance of the one or more RPA BOTs based on the comparing the RPA BOT information derived from the RPA BOT performance data to the at least one SLA.
8 . A computer-implemented method comprising:
obtaining, from a network support system associated with a telecommunications network, workflow information that identifies network resources associated with a process of the telecommunications network; deploying, based on the workflow information, one or more robotic process automation (RPA) BOTs in the telecommunications network, wherein the workflow information is generated and included in a flat file transmitted by the network support system; gathering RPA BOT performance data associated with a performance of the one or more RPA BOTs using virtual machines deployed in the telecommunications network; analyzing a status of the one or more RPA BOTs based on the RPA BOT performance data; managing the one or more RPA BOTs based on the status, wherein the managing includes starting an RPA BOT in the telecommunications network based on the status; monitoring a status of multiple hosted virtual disks (HVDs); and providing a graphical user interface for facilitating further management of the one or more RPA BOTs in relation to the multiple HVDs, wherein the graphical user interface provides a listing of the multiple HVDs being monitored, information regarding a monitored capacity of each HVD of the multiple HVDs, and a schedule identifying scheduled timeslots for the monitored capacity of each HVD of the multiple HVDs.
9 . The computer-implemented method of claim 8 , wherein the managing the one or more RPA BOTs comprises performing one or more actions on the telecommunications network or the one or more RPA BOTs, wherein the obtaining the workflow information comprises obtaining the workflow information from an input file drop, and wherein the method further comprises providing fallout information to a fallout file drop for transmission to the input file drop.
10 . The computer-implemented method of claim 9 , wherein the one or more actions comprise identifying a BOT failure cause or identifying a record processing failure cause.
11 . The computer-implemented method of claim 8 , wherein the managing the one or more RPA BOTs comprises providing one or more alerts based on the analyzing the status of the one or more RPA BOTs, conducting HVD management, or providing reporting and analytics based on the analyzing the status of the one or more RPA BOTs.
12 . The computer-implemented method of claim 8 , wherein at least some of the one or more RPA BOTs are schedulable to a given HVD of the multiple HVDs according to the schedule thereof for maintenance so as to avoid HVD underutilization or overutilization.
13 . The computer-implemented method of claim 8 , wherein the analyzing the status of the one or more RPA BOTs comprises comparing BOT information to at least one service level agreement (SLA).
14 . The computer-implemented method of claim 13 , further comprising determining a performance of the one or more RPA BOTs based on the comparing the BOT information to the at least one SLA.
15 . A system comprising:
a user device, wherein the user device comprises a graphical user interface; and a management system comprising:
a processor; and
a memory coupled with the processor, the memory storing executable instructions that, when executed by the processor, cause the processor to effectuate operations comprising:
obtaining, from a network support system associated with a telecommunications network, workflow information that identifies network resources associated with a process of the telecommunications network;
deploying, based on the workflow information, one or more robotic process automation (RPA) BOTs in the telecommunications network, wherein the workflow information instructs the one or more RPA BOTs to obtain diagnostic information regarding the telecommunications network;
gathering RPA BOT performance data associated with a performance of the one or more RPA BOTs using virtual machines deployed in the telecommunications network;
analyzing a status of the one or more RPA BOTs based on the RPA BOT performance data;
managing the one or more RPA BOTs based on the status using the user device, wherein the managing includes stopping an RPA BOT in the telecommunications network based on the status;
monitoring multiple hosted virtual disks (HVDs) for availability for use; and
providing the graphical user interface to the user device for facilitating further management of the one or more RPA BOTs, wherein the graphical user interface provides a listing of the multiple HVDs being monitored, information regarding a monitored capacity of each HVD of the multiple HVDs, and a schedule identifying available timeslots for the monitored capacity of each HVD of the multiple HVDs.
16 . The system of claim 15 , wherein the managing the one or more RPA BOTs comprises performing one or more actions on the telecommunications network or the one or more RPA B OTs, wherein the obtaining the workflow information comprises obtaining the workflow information from an input file drop, and wherein the operations further comprise providing fallout information to a fallout file drop for transmission to the input file drop.
17 . The system of claim 16 , wherein the one or more actions comprise identifying a BOT failure cause or identifying a record processing failure cause.
18 . The system of claim 15 , wherein the managing the one or more RPA BOTs comprises providing one or more alerts based on the analyzing the status of the one or more RPA BOTs, conducting HVD management, or providing reporting and analytics based on the analyzing the status of the one or more RPA BOTs.
19 . The system of claim 15 , wherein the analyzing the status of the one or more RPA BOTs comprises comparing RPA BOT information derived from the RPA BOT performance data to at least one service level agreement (SLA).
20 . The system of claim 19 , wherein the operations further comprise determining a performance of the one or more RPA BOTs based on the comparing the RPA BOT information derived from the RPA BOT performance data to the at least one SLA.Join the waitlist — get patent alerts
Track US2023099448A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.