Transactional Autosave Queues for Local Remote Data Sync
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile application development platforms face challenges in simplifying development, ensuring security, and accommodating diverse mobile devices and enterprise systems, particularly due to differences in communication protocols and security protocols, which complicates access and synchronization.
Innovation Solution
The system employs a declarative browser-based client application development tool using the Mobile Cloud Service (MCS) for rapid mobile application composition, facilitating communication between mobile devices and enterprise systems through a cloud-based interface that translates protocols to a standardized REST architecture, and provides a mobile security suite for secure data management and access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If traditional mobile application development platforms are used, then application development can be simplified, but security requirements and protocol compatibility issues arise
Solution Approach 1:
The patent introduces a cloud service layer as an intermediary between mobile devices and enterprise systems. This cloud service acts as a mediator that handles protocol translation, security authentication, and data synchronization, allowing simplified client applications to securely communicate with diverse enterprise systems without requiring complex client-side code.
Solution Approach 2:
The cloud service platform provides universal connectivity to multiple enterprise systems through standardized RESTful APIs. The system can adapt to different communication protocols and security requirements of various enterprise systems while presenting a uniform interface to mobile clients, thus achieving both simplicity and reliability.
2Adaptability or versatility
If multiple enterprise systems with different protocols are connected, then system versatility is improved, but access complexity increases
Solution Approach 1:
The cloud service functions as a protocol translation layer that converts diverse enterprise system protocols into a standardized RESTful interface. This intermediary handles the complexity of protocol conversion and security authentication centrally, allowing clients to access multiple enterprise systems through a uniform simplified interface without needing to understand the underlying protocol differences.
3Stability of the object's composition
If real-time data synchronization is implemented, then data consistency is improved, but network dependency and failure risk increase
Solution Approach 1:
The system performs preliminary actions by queuing change records locally before network synchronization. When network connectivity is unavailable, the client continues to operate and accumulates changes in a queue. Once connectivity is restored, the queued changes are automatically synchronized with the server, ensuring data consistency without immediate network dependency.
Solution Approach 2:
The change queue mechanism provides a buffer that cushions against network failures. By maintaining a local queue of pending changes, the system can tolerate network disconnection without losing data or requiring continuous network connectivity, thus reducing the impact of network dependency on system reliability.
4Ease of operation
If change records are queued for undo/redo operations, then operational flexibility is improved, but processing complexity increases
Solution Approach 1:
The system segments change records into discrete units that can be individually managed in the queue. Each change record represents a specific operation (insert, update, delete) with associated data, allowing the system to maintain operational history without processing the entire dataset. This segmentation enables efficient undo/redo operations by processing only relevant changes rather than scanning all data.
Data Source
AI summary
A system performs autosave. The system receives, by a web browser of a client device, a user action performed by a user that interacts with a website corresponding to a server. The system determines a change record corresponding to the user action, queues the change record in a first queue to commit corresponding changes to local models, and queues the change record in a second queue that communicates with the server to persist the change record at the serve. The first queue may be an ordered persistence queue that maintains a history of change records for performing undo and redo operations in interacting with the website. The second queue may be an ordered queue where change records are processed one at a time and each change record is sent to the server only if a prior change record in the second queue has been successfully recorded on the server.