Middleware Association Table for Mobile Data Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional middleware solutions for managing business data on occasionally-connected mobile devices face inefficiencies due to storage and bandwidth issues, as well as challenges in maintaining data consistency and integrity, particularly with the store-and-forward approach and connect-and-compute methods.
Innovation Solution
The proposed middleware system employs an association table and message store to efficiently manage business data by associating business object instances with mobile devices, optimizing message storage, and performing synchronization and integrity checks, allowing for robust data management and reduced storage and processing inefficiencies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If store-and-forward approach is used to manage mobile device data synchronization, then data consistency can be maintained, but storage requirements increase and bandwidth efficiency decreases
Solution Approach 1:
The patent segments data synchronization into two distinct phases: pre-computed synchronization messages are generated and stored separately from the actual data payload. The association table stores only metadata (device IDs, operation types, timestamps) rather than complete data records, enabling selective transmission of only necessary changes to mobile devices.
Solution Approach 2:
The system performs preliminary computation of synchronization messages before actual data transmission occurs. By pre-computing which records need to be synchronized and preparing the association table in advance, the system eliminates the need to store and forward all historical messages, reducing storage requirements while maintaining data consistency.
2Reliability
If store-and-forward approach is used, then data synchronization is maintained, but processing efficiency decreases due to redundant message forwarding
Solution Approach 1:
The patent extracts the synchronization metadata from the actual data payload and stores it separately in the association table. This allows the system to forward only the essential synchronization information (operation type, timestamp, affected records) rather than forwarding complete data messages, significantly reducing processing overhead while maintaining synchronization reliability.
Solution Approach 2:
The association table maintains local quality by storing device-specific synchronization state information. Each entry in the association table is optimized for a specific mobile device, tracking only the synchronization status relevant to that device, which enables more efficient processing compared to handling all messages for all devices.
3Productivity
If connect-and-compute approach is used, then processing is optimized, but control over data synchronization is reduced
Solution Approach 1:
The association table provides continuous feedback about the synchronization state of each mobile device. By tracking which records have been synchronized and their timestamps, the system gains granular control over data synchronization, allowing administrators to monitor and manage data consistency without requiring continuous device connection.
Solution Approach 2:
The system performs preliminary identification of synchronization requirements before actual data transmission. The association table is updated in advance with synchronization metadata, enabling the system to prepare and control data synchronization autonomously without waiting for device connection, thus maintaining control while optimizing processing.
4Ease of operation
If conventional middleware is used for mobile devices, then basic data access is provided, but data integrity management is insufficient
Solution Approach 1:
The patent segments data integrity management into distinct validation phases: conflict detection, integrity checking, and synchronization validation. Each phase operates independently on specific aspects of data integrity, allowing comprehensive integrity management while maintaining simple data access through the association table's structured metadata storage.
Solution Approach 2:
The system performs preliminary integrity checks and conflict detection before data synchronization occurs. By pre-validating data integrity rules and identifying potential conflicts in advance using the association table, the system ensures data integrity is maintained without adding complexity to the basic data access operations.
Data Source
AI summary
Middleware for mobile data management may include an association table and a message store. The middleware may operate to receive a business object instance from a backend system, determine one or more mobile devices associated with the business object instance, associate the business object instance with the one or more mobile devices and with an insert state in an association table, and associate, in the association table, the business object instance and the one or more mobile devices with a full-state message in the message store.