Worklist Cache Synchronization Using Timestamps
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Integrated platforms experience performance degradation and system instability due to superfluous requests for items from multiple providers, leading to unnecessary network traffic and increased CPU and memory utilization, as they periodically retrieve all items even if some are already cached.
Innovation Solution
Implement a method where timestamps are used to determine which items have changed since the last synchronization, allowing only updated items to be retrieved and cached, thereby reducing redundant requests and optimizing resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all items from all providers are periodically retrieved and stored in item cache, then the worklist is kept up-to-date, but network traffic increases and CPU and memory utilization increase
Solution Approach 1:
The patent extracts only the changed items from providers since the last synchronization, rather than retrieving all items. This is achieved by sending a request with a synchronization timestamp to each provider, which returns only items modified after that timestamp, thereby reducing network traffic and processing requirements while maintaining data freshness.
Solution Approach 2:
The system performs preliminary synchronization by storing timestamps of last synchronization with each provider. Before periodic retrieval, it uses these pre-stored timestamps to determine which items have changed, avoiding redundant retrieval of unchanged items and reducing resource consumption.
2Ease of operation
If all items are retrieved from providers on each user log in, then the worklist is populated completely, but superfluous requests are made and system performance degrades
Solution Approach 1:
Instead of retrieving all items from providers during user login, the system extracts only the subset of items that have changed since the last synchronization by using stored timestamps. This reduces the number of requests and processing load while ensuring the worklist contains all relevant updated items.
3Reliability
If periodic retrieval of all items is performed, then data consistency is maintained, but unnecessary requests increase and system stability decreases
Solution Approach 1:
The system implements feedback by storing and utilizing synchronization timestamps from previous interactions with providers. Each periodic retrieval uses these timestamps to determine what has changed, creating a feedback loop that prevents redundant requests and reduces system load while maintaining data consistency.
Data Source
AI summary
Methods, systems, and computer-readable storage media for providing a worklist of a user with at least one item. In some implementations, actions include determining one or more timestamps, each timestamp indicating a time, at which an item cache was synchronized for a respective provider of one or more providers, transmitting one or more requests to one or more respective providers of the one or more providers, the one or more requests each including the one or more timestamps and indicating a user, receiving one or more responses, each response including a sub-set of items, each item in the sub-set of items being included in the sub-set of items based on the one or more timestamps, populating the worklist of the user with one or more items in the sub-set of items reusing a previously synchronized worklist database cache, and providing the worklist for display to the user on a display.