Distributed Database Maintenance Action Replication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems for maintaining digital computing platforms lack efficient and scalable methods for identifying, analyzing, and mitigating system disruptions, as they often require manual troubleshooting and lack effective ways to replicate successful maintenance actions across different platforms.

Innovation Solution

A computing platform with a processor, memory, and communication interface that uses distributed databases to receive maintenance action reports, history logs, and status reports to determine success scores, identify potential solutions, and send commands for maintenance actions, thereby facilitating efficient troubleshooting and solution replication across platforms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual troubleshooting methods are used to maintain digital computing platforms, then flexibility and adaptability to specific problems are improved, but troubleshooting efficiency and scalability deteriorate

Engineering Contradiction:
Improveadaptability to specific problemsVSAvoidtroubleshooting efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent creates virtual copies of successful maintenance actions by capturing and storing detailed records of troubleshooting steps, commands, and outcomes in a distributed database. These copied actions can be automatically applied to similar future problems, replicating the effectiveness of manual expert troubleshooting while enabling scalable automation across multiple computing platforms.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system transforms maintenance knowledge from unstructured human expertise into structured parameters by capturing specific details of successful actions (commands executed, systems modified, outcomes achieved) and storing them as queryable data. This parameterization enables automated matching of current problems with historical solutions based on comparable parameters, maintaining adaptability while improving efficiency.

Inventive Principle:
Principle #35Parameter changes

2Stability of the object's composition

If traditional centralized databases are used to store maintenance history, then data consistency is improved, but system scalability and performance deteriorate

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem scalability
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent divides the centralized database into multiple distributed database nodes across different computing platforms. Each node stores local maintenance action records and can independently query its own data, while the distributed architecture enables shared access to maintenance knowledge across the entire network, achieving both scalability and data consistency through decentralized storage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The distributed database system provides universal access to maintenance knowledge across diverse computing platforms and environments. The same maintenance action records can be queried and applied across different system types, enabling the system to scale across heterogeneous platforms while maintaining consistent data access patterns and knowledge sharing.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If comprehensive maintenance action records are collected and stored, then solution accuracy and reliability are improved, but data storage requirements and system complexity increase

Engineering Contradiction:
Improvesolution accuracyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts only the essential and relevant parameters from comprehensive maintenance action records for storage and analysis. By identifying and capturing key elements (specific commands, system configurations, problem descriptions, outcomes) while filtering out redundant information, the system achieves high solution accuracy with reduced data storage requirements and simplified processing.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11966884B2Using distributed databases for network regression analysis
Publication Date: 2024.04.23 BANK OF AMERICA CORP
  • US11966884B2 patent drawing
  • US11966884B2 patent drawing
  • US11966884B2 patent drawing

AI summary

A computing platform may communicate with a device agent to receive digital system maintenance reporting, which may include information regarding steps taken to resolve issues of a digital system during a troubleshooting process. The computing platform may analyze the steps taken, and determine whether the steps resolved the troubleshooting. The computing platform may filter ineffective steps, and store steps associated with successful solutions in one or more distributed databases. The computing platform may receive information identifying a problem faced by a different system. The computing platform may analyze the distributed database to identify similar steps that successfully resolved the problem in the past, and mitigate the problem using the similar successful steps.