System and method for creating bots for automating first party touchpoints
US-11218594-B1 · Jan 4, 2022 · US
US11546206B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11546206-B2 |
| Application number | US-202017094406-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 10, 2020 |
| Priority date | Nov 10, 2020 |
| Publication date | Jan 3, 2023 |
| Grant date | Jan 3, 2023 |
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.
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.
Opening claim text (preview).
The invention claimed is: 1. 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 is generated and included in a flat file transmitted by the network support system to the device, and 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; updating, for the one or more RPA BOTs, a database with RPA BOT information comprising the RPA BOT performance data; analyzing a status of the one or more RPA BOTs based on the updating the database; 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; and providing a graphical user interface for facilitating further management of the one or more RPA BOTs, wherein the graphical user interface provides selectable options for on demand regression testing management of the one or more RPA bots, wherein the selectable options include options for predetermined tests to run for the one or more RPA bots, wherein the graphical user interface further enables defining of fallout threshold settings associated with each of the one or more RPA BOTs and provides statistics on fallout, and wherein the statistics include fallout count and fallout percentage over a predefined period of time. 2. The device of claim 1 , wherein the managing the one or more RPA BOTs further effectuates operations comprising 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, identifying a record processing failure cause, or identifying whether a hosted virtual disk (HVD) is ready for use. 4. The device of claim 1 , wherein the managing the one or more RPA BOTs further effectuates operations comprising providing one or more alerts based on the analyzing the status of the one or more RPA BOTs, conducting hosted virtual disk 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 the operations further comprise identifying whether a hosted virtual disk (HVD) is ready for use, wherein the graphical user interface further provides a listing of 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, and 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 further effectuates operations comprising comparing the RPA BOT information 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 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 instructs the one or more RPA BOTs to obtain diagnostic information regarding the telecommunications network, and 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; updating, for the one or more RPA BOTs, a database with BOT information comprising the RPA BOT performance data; analyzing a status of the one or more RPA BOTs based on the updating the database; 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; and providing a graphical user interface for facilitating further management of the one or more RPA BOTs, wherein the graphical user interface provides selectable options for on demand regression testing management of the one or more RPA bots, wherein the selectable options include options for predetermined tests to run for the one or more RPA bots, wherein the graphical user interface further enables defining of fallout threshold settings associated with each of the one or more RPA BOTs and provides statistics on fallout, and wherein the statistics include fallout count and fallout percentage over a predefined period of time. 9. The computer-implemented method of claim 8 , wherein the managing the one or more RPA BOTs further effectuates operations comprising 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, identifying a record processing failure cause, or identifying whether a hosted virtual disk (HVD) is ready for use. 11. The computer-implemented method of claim 8 , wherein the managing the one or more RPA BOTs further effectuates operations comprising providing one or more alerts based on the analyzing the status of the one or more RPA BOTs, conducting hosted virtual disk 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 , further comprising identifying whether a hosted virtual disk (HVD) is ready for use, wherein the graphical user interface further provides a listing of 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, and 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
Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF] · CPC title
Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements · CPC title
Localisation of faults · CPC title
mobile agents · CPC title
Additional information in the notification, e.g. enhancement of specific meta-data · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.