RPA Bot Management System for Telecommunications Network Oversight

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional telecommunications network management lacks real-time insight and effective management of robotic process automation (RPA) BOTs, leading to delays in identifying and addressing issues such as BOT failures, underutilization, and poor performance, which can result in poor network performance.

Innovation Solution

A system and method that deploy RPA BOTs in telecommunications networks, update a database with BOT status information, and analyze this information to manage the BOTs, providing real-time oversight and visibility into their operations, including status updates, debug logs, and performance metrics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If RPA BOTs are deployed in telecommunications networks to automate tasks, then productivity and efficiency are improved, but the complexity of managing and monitoring these BOTs increases

Engineering Contradiction:
Improveautomation efficiencyVSAvoidBOT management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a BOT management system that acts as an intermediary between network operators and RPA BOTs. This system provides centralized deployment, monitoring, and control capabilities, allowing operators to manage multiple BOTs through a unified interface. The management system handles BOT lifecycle operations including deployment, status monitoring, debugging, and performance analysis, thereby reducing the complexity of direct BOT management while maintaining high automation efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If real-time monitoring of BOT status is implemented, then reliability and issue detection are improved, but the loss of time for data collection and analysis increases

Engineering Contradiction:
ImproveBOT operation reliabilityVSAvoidstatus analysis time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by proactively collecting and storing BOT status information, debug logs, and operational data in a database before issues arise. The system continuously updates this information and maintains it in an accessible format, so when problems occur, analysts can immediately retrieve pre-collected data without waiting for real-time queries. This approach ensures high reliability through continuous monitoring while minimizing the time lost during incident investigation.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If comprehensive BOT information is collected and stored in a database, then measurement precision and troubleshooting capability are improved, but the quantity of data and storage requirements increase

Engineering Contradiction:
ImproveBOT status monitoring precisionVSAvoiddata volume
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The patent extracts and stores only the most critical BOT information in the database, including key status indicators, error logs, and performance metrics. Rather than storing all possible data, the system selectively captures information that is most valuable for troubleshooting and monitoring. This extraction approach maintains high measurement precision for critical parameters while minimizing the overall data volume and storage requirements by focusing on essential operational data.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11546206B2Robotic process automation bot operational management system
Publication Date: 2023.01.03 AT&T DIGITAL LIFE
  • US11546206B2 patent drawing
  • US11546206B2 patent drawing
  • US11546206B2 patent drawing

AI summary

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.