Bookmark Synchronization via Timestamped Master Database

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods require manual and time-consuming updates of website bookmarks across multiple devices, and often fail to ensure that all devices have access to the most current bookmark data, especially in scenarios where devices are offline or unavailable.

Innovation Solution

A method where a designated bookmark server maintains a master database with timestamps for each URL, receiving and processing transaction requests to add, change, or delete bookmarks, ignoring outdated requests and ensuring only the most recent changes are applied, and then synchronizing these updates across connected devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual updates are used to synchronize bookmarks across multiple devices, then each device can have its own bookmark data, but the process becomes time-consuming and labor-intensive

Engineering Contradiction:
Improvebookmark update processVSAvoidtime to update bookmarks
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system enables automatic self-updating of bookmarks across all devices by implementing a centralized bookmark server that automatically distributes bookmark data to connected devices without requiring manual intervention from users

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

A centralized bookmark server acts as an intermediary between multiple devices, receiving bookmark updates from any device and automatically distributing them to all other connected devices, eliminating the need for manual synchronization

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If bookmarks are stored locally on each device, then each device has independent access to bookmark data, but updates must be propagated to each device separately

Engineering Contradiction:
Improvedevice independenceVSAvoidbookmark synchronization speed
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system divides bookmark data management into two segments: local storage on each device for immediate access, and centralized management on the bookmark server for coordination, allowing devices to maintain independence while achieving rapid synchronized updates

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system combines local bookmark storage with centralized server management, merging the advantages of both distributed and centralized approaches to enable fast local access while maintaining efficient synchronized updates across all devices

Inventive Principle:
Principle #5Merging (Combining)

3Extent of automation

If a centralized bookmark server is implemented to automate updates, then bookmark synchronization becomes efficient and automatic, but the system complexity increases

Engineering Contradiction:
Improvebookmark update automationVSAvoidsystem architecture
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The bookmark server is designed as a universal platform that can serve multiple devices simultaneously, handling various operations (add, delete, update bookmarks) and supporting different device types, which simplifies the overall system architecture by consolidating functionality in a single multi-purpose component

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS7711707B2Method for synchronizing and updating bookmarks on multiple computer devices
Publication Date: 2010.05.04 X CORP
  • US7711707B2 patent drawing
  • US7711707B2 patent drawing
  • US7711707B2 patent drawing

AI summary

Multiple computer devices are networked, and one device is designated as a bookmark server. The bookmark server stores and maintains a master bookmark database that is available to all the networked devices. Each bookmark in the bookmark database includes a bookmark time stamp. If a bookmark is added, deleted or changed at any device, then a transaction request is sent to the bookmark server. The transaction request includes a transaction time stamp indicating the time that the transaction request was created. The bookmark server analyzes the transaction requests according to the time stamps. If multiple transaction requests are received for a single bookmark, then only the most recent transaction request is honored and other transaction requests related to the bookmark are ignored. Also, a transaction request is ignored if the transaction time stamp is older than the corresponding bookmark time stamp.