Message-Based Synchronization for Mobile Business Objects

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Traditional methods for synchronizing data between mobile devices and enterprise systems do not effectively manage conflicts or provide reliable communication for updates, especially when data is outdated or updated by multiple devices during disconnected periods.

Innovation Solution

A method involving a notification query derived from a download cursor to identify updated subscriptions, generating result rows, and sending them to a client device in an import message, along with mechanisms for receiving and processing messages to handle replay instructions and conflict resolution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional complete synchronization is performed whenever connectivity is available, then data consistency between mobile devices and enterprise systems is maintained, but network bandwidth is wasted by transmitting all data including unchanged records, and synchronization time increases

Engineering Contradiction:

Improvedata consistencyVSAvoidnetwork bandwidth

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts and transmits only the changed data records (inserts, updates, deletes) from the complete data set during synchronization. The server identifies and sends only modified records based on change tracking mechanisms, eliminating the need to transmit unchanged data and reducing network bandwidth consumption while maintaining data consistency.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The synchronization process is segmented into identifying changed records, packaging them in efficient formats, and transmitting only necessary data. The patent divides the synchronization task into discrete change events rather than treating it as a monolithic complete data transfer, allowing selective transmission of only required data portions.

Inventive Principle:

Principle #1Segmentation

2Reliability

Engineering Contradiction:

Improvedata consistencyVSAvoidsynchronization time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of performing complete synchronization, the patent applies partial action by synchronizing only the subset of data that has changed since the last synchronization event. This selective approach reduces synchronization time and network usage while maintaining data consistency across devices.

Inventive Principle:

Principle #16Partial or excessive action

3Adaptability or versatility

If mobile devices update data during disconnected periods, then device autonomy and offline functionality are improved, but conflicts arise when multiple devices update the same data simultaneously

Engineering Contradiction:

Improveoffline functionalityVSAvoiddata conflict resolution

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies preliminary action by establishing conflict resolution rules and mechanisms before conflicts occur. Change tracking identifiers are assigned to records before updates happen, and conflict detection logic is pre-configured to compare these identifiers when devices reconnect, enabling automatic resolution without manual intervention.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The synchronization system implements feedback mechanisms where devices report their local changes to the server, which then provides feedback about conflicts detected and resolution actions taken. This feedback loop ensures that all devices eventually reach a consistent state by informing them of any conflicts that occurred during offline periods and how they were resolved.

Inventive Principle:

Principle #23Feedback

4Loss of energy

If message-based synchronization with notification queries is used, then network bandwidth usage is reduced by sending only changed data, but system complexity increases due to message management and conflict resolution mechanisms

Engineering Contradiction:

Improvenetwork bandwidthVSAvoidmessage management

Core Design Contradiction:

Loss of energyVSDevice complexity

Solution Approach 1:

The patent introduces a synchronization server as an intermediary that manages the complexity of message-based synchronization. The server handles notification queries, tracks changes across multiple devices, detects conflicts, and coordinates resolutions, thereby centralizing the complex message management logic and reducing the burden on individual mobile devices.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS9336291B2Message based synchronization for mobile business objects

Publication Date: 2016.05.10 SYBASE INC

AI summary

A system, method, and computer program product are provided for executing a notification query derived from a download cursor for a business object to identify an updated subscription. The download cursor is run against the updated subscription to generate result rows. The result rows are sent to a client device in an import message. Additional systems, methods, and computer program products are provided for guaranteeing at-least-once delivery of a message.