Database Synchronization via Encapsulation Module Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current approaches to synchronizing two database platforms face challenges such as high computational costs, data inconsistencies, and the inability to maintain real-time synchronization due to structural differences and complex query requirements, especially in large DP projects with multiple applications accessing databases concurrently.

Innovation Solution

A computer network system utilizing an encapsulation module that decomposes work units into messages, ensuring efficient data transfer and synchronization between databases by controlling access through the encapsulation module, which converts and sends data in a structured format to maintain data integrity and consistency across different database structures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is transferred continuously from the first database to the second database to maintain synchronization, then data consistency is improved, but computational costs and transfer costs increase

Engineering Contradiction:
Improvedata consistencyVSAvoidcomputational costs
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent segments data changes into discrete work units that are processed and transferred individually rather than continuously. The encapsulation module decomposes changes into manageable units that can be synchronized asynchronously, reducing computational overhead while maintaining consistency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The encapsulation module acts as an intermediary between the first database and the second database. It receives changes from the first database, processes and formats them into work units, and transfers them to the second database, thereby reducing direct computational costs between databases while ensuring synchronization.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If real-time synchronization is implemented to make changes available immediately, then data availability is improved, but transfer costs and computational requirements increase

Engineering Contradiction:
Improvedata availabilityVSAvoidtransfer costs
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The patent implements dynamic synchronization where the system can adapt between real-time and batch processing modes. The encapsulation module dynamically decides when to transfer work units based on system state, allowing real-time availability when needed while reducing transfer costs during lower-priority periods.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system uses periodic work unit processing where changes are transferred at scheduled intervals rather than continuously. This periodic action maintains data availability while significantly reducing transfer costs compared to continuous real-time synchronization.

Inventive Principle:
Principle #19Periodic action

3Adaptability or versatility

If structural differences between database platforms are accommodated through complex mapping, then adaptability is improved, but device complexity increases

Engineering Contradiction:
Improvestructural compatibilityVSAvoidmapping complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The encapsulation module serves as a structural intermediary that handles the complexity of mapping between different database platforms. It abstracts the structural differences and provides a unified interface for work unit processing, thereby maintaining adaptability while reducing the visible complexity of the mapping mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the complex mapping process into discrete work units that can be processed individually. Each work unit contains specific mapping instructions that handle structural differences in a modular way, making the overall system more adaptable while reducing the complexity of any single mapping operation.

Inventive Principle:
Principle #1Segmentation

4Stability of the object's composition

If gradual migration is implemented to minimize disruption, then system stability is improved, but migration time increases

Engineering Contradiction:
Improvesystem stabilityVSAvoidmigration time
Core Design Contradiction:
Stability of the object's compositionVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-processing and preparing work units before they are transferred to the second database. The encapsulation module prepares changes in advance and queues them for systematic transfer, allowing gradual migration while minimizing actual disruption time during the migration process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system maintains continuity of useful action by continuously processing and transferring work units from the first database to the second database during the migration period. This continuous operation ensures system stability through gradual migration while reducing total migration time through uninterrupted progress.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS7526576B2Computer network system using encapsulation to decompose work units for synchronizing and operating a second database from a first database
Publication Date: 2009.04.28 UBS BUSINESS SOLUTIONS AG
  • US7526576B2 patent drawing
  • US7526576B2 patent drawing
  • US7526576B2 patent drawing

AI summary

Computer network system for building and/or synchronising a second database from/with a first database, accesses by work units being carried out at least on the first database from at least one application workstation, to generate, change or delete contents of the database, with at least one first server to guide and maintain the first database, said server being connected to at least one application workstation, at least one second server to guide and maintain the second database, at least one data connection which connects the two servers, the accesses by the work units to the first database taking place by means of an encapsulation module, which is set up and programmed so that the work units are passed to it, work units which it accepts are decomposed into one or more messages, the messages are entered in the first database and the messages are sent to the second database.