Adaptive Business Object Synchronization via Temporal Constraints
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In distributed business applications, ensuring timely and efficient synchronization of business objects across replicated systems while adhering to temporal constraints is challenging, particularly due to varying update durations and network latencies, which can lead to inconsistencies if not managed properly.
Innovation Solution
The method involves adaptive synchronization by determining update durations based on business object and system profiles, generating change messages, and transmitting synchronization messages efficiently to maintain consistency across replicas, with options for complete or incremental changes, and bulk messaging to reduce network traffic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If synchronous updates are performed across all replicas immediately, then data consistency is improved, but network traffic and processing overhead increase significantly
Solution Approach 1:
The patent segments the synchronization process into two phases: an asynchronous phase where changes are propagated to replicas without immediate confirmation, and a synchronous phase where confirmed changes are applied. This segmentation allows the system to maintain data consistency while reducing unnecessary network traffic by not immediately synchronizing every change across all replicas.
Solution Approach 2:
The patent implements dynamic synchronization by adjusting the synchronization strategy based on system state. The system dynamically switches between asynchronous and synchronous update modes depending on factors like network conditions, replica status, and change characteristics, thereby optimizing the balance between consistency and network overhead.
2Reliability
If update duration is extended to ensure complete data transfer, then data completeness is improved, but temporal constraints for real-time synchronization are violated
Solution Approach 1:
The patent applies preliminary action by preparing change messages in advance and using buffered structures to store update information before actual synchronization occurs. This allows the system to ensure data completeness is maintained while reducing the actual synchronization time by having data ready for rapid transmission when needed.
Solution Approach 2:
The patent implements periodic synchronization checks and batch processing of changes. Instead of continuously attempting immediate synchronization, the system uses periodic cycles to process and transmit changes, which ensures data completeness while respecting temporal constraints through controlled batching intervals.
3Reliability
If all changes are synchronized immediately, then data consistency is improved, but system complexity and processing load increase
Solution Approach 1:
The patent extracts the synchronization logic into separate, dedicated components including a change message generator, a synchronization manager, and replica update modules. This extraction reduces overall system complexity by isolating synchronization responsibilities in dedicated subsystems that can be managed independently.
Solution Approach 2:
The patent introduces intermediary components such as change message buffers and synchronization queues that mediate between change generation and actual replica updates. These intermediaries simplify the overall process by decoupling the producers of changes from the consumers (replicas), reducing processing complexity while maintaining consistency.
4Loss of energy
If selective synchronization is implemented, then network overhead is reduced, but ensuring temporal constraints and consistency becomes more difficult
Solution Approach 1:
The patent applies local quality by customizing synchronization behavior for different replicas based on their individual characteristics, such as update frequency, data importance, and network conditions. This allows the system to reduce network overhead by not synchronizing everything to every replica, while maintaining temporal constraints through localized quality adjustments in synchronization timing and scope.
Data Source
AI summary
In some implementations, a method includes changing a master business object that is resident at a first location on a network, generating a change message for changing a replicated business object, the replicated business object being based on the master business object and being resident at a second location on the network remote from the first location, determining an update duration for updating the replicated business object, incorporating the change routine into a synchronization message when the update duration is less than a temporal constraint, and transmitting the synchronization message from the first location to the second location to update the replicated business object based on the synchronization message.