Centralized Database System for Data Redundancy and Conflict Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database systems face challenges in maintaining data redundancy, including determining the frequency of backups, data transmission speed, and identifying missing or incomplete data sections across backup systems, which can lead to data loss during failures or catastrophes.

Innovation Solution

A centralized database system that includes multiple database servers, backup storage devices, and CPUs, which dynamically adjusts associations and transmits data through communications channels, detects conflicts, allocates resources, and optimizes CPU configurations to ensure data integrity and redundancy by managing backup processes and channel throughput.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is transmitted frequently to backup storage devices, then data redundancy and reliability are improved, but system complexity and coordination overhead increase

Engineering Contradiction:
Improvedata redundancyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

A centralized database is introduced as an intermediary component that coordinates between multiple database servers and backup storage devices. The centralized database receives lists of servers and devices, manages associations, detects conflicts, and transmits instructions to ensure data is transmitted to the appropriate backup storage device, thereby simplifying the overall system architecture while maintaining reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The centralized database serves multiple functions: it stores data, maintains lists of database servers and backup storage devices, determines conflicts between internal backup end times and data receipt startup times, transmits conflict messages, and coordinates data transmission instructions to multiple backup devices. This multi-functional approach reduces the need for separate specialized components.

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

2Productivity

If data transmission speed is increased, then backup efficiency is improved, but data integrity and conflict detection capability may deteriorate

Engineering Contradiction:
Improvebackup efficiencyVSAvoiddata integrity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The centralized database performs preliminary conflict detection by comparing the internal backup end time of database servers with the startup time of backup storage devices before data transmission begins. By identifying potential conflicts in advance and transmitting conflict messages to resolve them, the system ensures data integrity is maintained while allowing efficient transmission to proceed without interruptions from undetected conflicts.

Inventive Principle:
Principle #10Preliminary action

3Speed

If CPU configuration rate is increased, then data processing and transmission speed are improved, but energy consumption and system resource usage increase

Engineering Contradiction:
Improvedata transmission speedVSAvoidenergy consumption
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

The system dynamically adjusts CPU configuration rates based on real-time system conditions and requirements. The centralized database monitors and transmits instructions to optimize CPU allocation for data transmission tasks, allowing the system to scale computational resources up or down as needed, thereby achieving high transmission speeds when necessary while conserving energy during periods of lower demand.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9703646B2Centralized database system
Publication Date: 2017.07.11 BANK OF AMERICA CORP
  • US9703646B2 patent drawing
  • US9703646B2 patent drawing
  • US9703646B2 patent drawing

AI summary

A centralized database system is provided. The centralized database system may include a centralized database, a plurality of database server, a plurality of backup storage devices and a plurality of CPUs. The centralized database system may include interaction between components of the centralized database system. The centralized database may receive data from the database server, the plurality of backup storage devices and a plurality of CPUs. The centralized database may also transmit instructions to the components of the centralized database system. The instructions may be associated with conflicts, CPU configurations, missing back-ups, communication channel throughputs and any other suitable instructions.