Central Local Data Model Synchronization via Manipulation Requests

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing data synchronization methods in computer networks face challenges in ensuring high interaction levels while maintaining data security and preventing server crashes that could lead to data integrity issues.

Innovation Solution

A method where a central data model on the server synchronizes data with local models on clients, using presentation and control programs for user interaction, with mechanisms for error checking and conflict resolution, and asynchronous transmission to manage manipulation requests and ensure data consistency across the network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Stability of the object's composition

If a central data model on the server synchronizes data with local models on clients, then data consistency across the network is improved, but server complexity increases

Engineering Contradiction:

Improvedata consistencyVSAvoidserver complexity

Core Design Contradiction:

Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The system divides the data model into a central data model on the server and local data models on each client. This segmentation allows data consistency to be maintained through synchronization while distributing the computational load, thereby reducing server complexity. Each client maintains its own local data model that corresponds to and synchronizes with the central data model.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces manipulation requests as an intermediary mechanism between clients and the central data model. These requests serve as a controlled interface that allows clients to interact with the central data model without directly accessing or potentially corrupting it. The server mediates all changes through this request system, maintaining consistency while managing complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Stability of the object's composition

If manipulation requests are transmitted to all clients when central data model changes successfully, then data synchronization is improved, but network traffic increases

Engineering Contradiction:

Improvedata synchronizationVSAvoidnetwork traffic

Core Design Contradiction:

Stability of the object's compositionVSLoss of energy

Solution Approach 1:

Instead of transmitting all manipulation requests to all clients, the system applies partial action by only transmitting requests that result in successful changes to the central data model. The server evaluates each manipulation request and only broadcasts those that successfully modify the central data model, reducing unnecessary network traffic while maintaining synchronization.

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The system implements feedback mechanisms where clients check whether they have received all manipulation requests submitted since a specified point in time. Clients verify the completeness of received requests and can request retransmission of missing ones, ensuring synchronization without requiring continuous broadcast of all requests.

Inventive Principle:

Principle #23Feedback

3Reliability

If manipulation requests are processed in a single-threaded program on the server, then data integrity is improved, but processing speed decreases

Engineering Contradiction:

Improvedata integrityVSAvoidprocessing speed

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system applies preliminary action by having clients execute manipulations in their local data models before submitting manipulation requests to the server. This pre-execution allows the server to validate requests more efficiently and process them in a single-threaded manner without sacrificing overall system responsiveness, as the heavy lifting is done locally beforehand.

Inventive Principle:

Principle #10Preliminary action

4Reliability

If clients check for missing manipulation requests and request retransmission, then data completeness is improved, but communication overhead increases

Engineering Contradiction:

Improvedata completenessVSAvoidcommunication overhead

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

Inventive Principle:

Principle #23Feedback

Data Source

PatentEP2706474B1Method for synchronising data in a computer network

Publication Date: 2018.10.10 FREQUENTIS

Figure 1~2
Figure 3

AI summary

The method involves carrying out data manipulation corresponding to a manipulation request (3), and synchronizing local data model (21) corresponding to the central data model (11) provided at each client (2). The manipulation request is developed while carrying out data manipulation with the control program (24) and is forwarded to the local data model. The manipulation request is transferred to all clients and the local data models are changed corresponding to the manipulation request after successful execution of the manipulation of central data model of the server (1). An independent claim is included for a computer network for provision and management of synchronized data, particularly air traffic information.