Data Synchronization Server Configuration Change Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data synchronization techniques fail to maintain consistency when synchronizing databases across multiple information processing apparatuses, particularly when a function or configuration is enabled after initial synchronization, leading to potential data mismatches and failures.

Innovation Solution

A system and method for differential synchronization that includes a setting value management server and client, where the server manages synchronization conditions and updates setting values based on configuration changes, ensuring that only relevant data is synchronized by checking the server final update time and configuration flags, preventing data mismatches by excluding disabled functions or configurations from synchronization targets.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If differential synchronization is performed by extracting data changed after the final synchronization time, then synchronization efficiency is improved, but data consistency cannot be maintained when functions or configurations are enabled after initial synchronization

Engineering Contradiction:
Improvesynchronization efficiencyVSAvoiddata consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by storing configuration information and function enablement status before synchronization occurs. When a function is enabled, the system proactively identifies and synchronizes related setting values before they are needed, preventing data inconsistency rather than correcting it afterward.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by monitoring function enablement status and configuration changes in real-time. When a function is enabled or configuration changes, the system receives feedback and automatically triggers synchronization of affected setting values to maintain data consistency across the network.

Inventive Principle:
Principle #23Feedback

2Reliability

If all setting values are synchronized regardless of function enablement status, then data consistency is maintained, but unnecessary data transmission and processing increase

Engineering Contradiction:
Improvedata consistencyVSAvoidenergy consumption for data transmission
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system extracts and transmits only the specific setting values related to enabled functions or configuration changes, rather than synchronizing all setting values. This selective extraction approach maintains data consistency for relevant data while reducing unnecessary data transmission and energy consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies local quality by treating different setting values differently based on their relationship to function enablement status. Setting values related to enabled functions receive high-priority synchronization with strict consistency requirements, while other setting values use more efficient, selective synchronization methods.

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If synchronization is performed at any selected timing, then operational flexibility is improved, but data consistency cannot be guaranteed when functions are enabled between synchronization operations

Engineering Contradiction:
Improvesynchronization timing flexibilityVSAvoiddata consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system implements dynamic synchronization by adapting the synchronization process to current function enablement status and configuration changes. Rather than using fixed synchronization intervals, the system dynamically adjusts synchronization behavior based on real-time system state, maintaining consistency even when functions are enabled between scheduled synchronization operations.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP3070619B1Information processing apparatuses performing synchronization of data and data synchronization methods
Publication Date: 2023.08.16 CANON KK
  • EP3070619B1 patent drawingFigure 1
  • EP3070619B1 patent drawingFigure 2A~2B
  • EP3070619B1 patent drawingFigure 3A~3B

AI summary

A server (110) manages first time at which a configuration of a client apparatus (120) is changed, while associating the first time with the client apparatus. The server (110) obtains information indicating second time at which previous synchronization processing of a setting value is performed with the client apparatus (120). In the case where the second time is after the first time, the server (110) sends, in response to a reception of a request for a setting value from the client, the client apparatus (120) a setting value which is updated after the second time and type of which corresponds to the changed configuration of the client apparatus (120). In the case where the second time is before the first time, the server (110) sends, in response to a reception of a request for a setting value from the client, the client apparatus (120) setting information including a setting value which is not updated after the second time.