Cloud Data Synchronization via Mediator and Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Businesses using cloud computing face challenges in maintaining real-time synchronization of data across disparate cloud data sources with heterogeneous designs, limiting the ability to use data in novel or alternative ways, as existing solutions are not viable for constant, up-to-date data management.

Innovation Solution

A system comprising a local database, database data conversion software, initial remote database acquisition software, steady state database synchronization software, and failsafe database synchronization software modules, which receive, convert, and reconcile data between multiple cloud data sources, ensuring real-time synchronization through API calls and error handling mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data is copied and stored in separate locations for alternative use, then data availability is improved, but data synchronization and consistency deteriorate

Engineering Contradiction:
Improvedata availabilityVSAvoiddata synchronization
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a cloud service provider's database as an intermediary layer between the enterprise's existing database and alternative data uses. This mediator handles all data access, transformation, and synchronization operations, allowing the enterprise to access data in multiple formats and locations while maintaining a single source of truth in the cloud database, thus preserving data consistency while enabling versatile data utilization

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If data is accessed in real-time from a single source, then data consistency is improved, but data accessibility and flexibility deteriorate

Engineering Contradiction:
Improvedata consistencyVSAvoiddata accessibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments data access into multiple independent pathways while maintaining a unified data source. The cloud service provider's database is divided into multiple accessible interfaces and connection points that allow different applications and users to access data in real-time simultaneously. Each segment maintains the same data consistency rules while providing flexible access methods, thus enabling both real-time consistency and enhanced accessibility

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If multiple copies of data are maintained for different purposes, then data accessibility is improved, but data integrity and synchronization deteriorate

Engineering Contradiction:
Improvedata accessibilityVSAvoiddata integrity
Core Design Contradiction:
Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The patent uses controlled copying mechanisms where data can be replicated into different formats and stored in multiple locations for various purposes. The cloud service provider's database system manages these copies with automated synchronization protocols that ensure any changes to the source data are automatically propagated to all copies, maintaining data integrity while enabling flexible access. The system allows copying for alternative uses but prevents unauthorized modifications to preserve precision

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10911536B2Real-time synchronization of data between disparate cloud data sources
Publication Date: 2021.02.02 TALKCYCLE LLC DBA FRONTSPIN
  • US10911536B2 patent drawing
  • US10911536B2 patent drawing
  • US10911536B2 patent drawing

AI summary

Real-time synchronization of data between disparate cloud data sources; local database receives data from various sources then supplies data to various destinations. A steady state database synchronization software module monitors local database for changes to data, reconciles any local change with changes to the same data in remote database, forwards reconciled data to a destination database, and monitors messages announcing that data in remote database has changed. Finally, the failsafe database synchronization software module polls the remote database periodically for changes, compares changes made to remote data and local data, outstanding changes are applied to local and remote databases as determined.