Distributed Attribute Management via Server Mediation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database synchronization techniques, such as 'slow synchronization' and 'fast synchronization' using change logs, face challenges like timestamp inaccuracies in mobile devices, leading to missed updates and inefficiencies in managing and propagating attribute changes across multiple devices.
Innovation Solution
A distributed management framework that propagates attributes based on attribute-granularity permissions, using a server to manage updates and permissions across clients, ensuring secure and efficient data exchange by linking entities and granting permissions for attribute propagation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If timestamp-based synchronization is used to determine update propagation, then synchronization efficiency is improved, but reliability deteriorates due to clock inaccuracies and time zone changes in mobile devices
Solution Approach 1:
The patent introduces a server as an intermediary that centralizes timestamp management and coordinates synchronization between devices. The server maintains accurate time and mediates conflict resolution, preventing the reliability issues caused by individual device clock inaccuracies while preserving synchronization efficiency through centralized coordination.
Solution Approach 2:
The system implements feedback mechanisms where devices report their timestamps and change logs to the server, which then provides correction information or coordinates updates based on accurate server time. This feedback loop ensures that timestamp-based synchronization remains reliable even when device clocks drift or change due to time zone transitions.
2Loss of time
If change log-based fast synchronization is implemented, then synchronization time is reduced, but data loss occurs when timestamp conflicts arise from clock changes
Solution Approach 1:
The server acts as an intermediary that receives change logs from multiple devices and coordinates their synchronization. When timestamp conflicts occur due to clock changes, the server mediates the conflict resolution process, ensuring that no valid updates are lost while maintaining the efficiency of change log-based synchronization.
Solution Approach 2:
The system performs preliminary actions by having devices send their change logs and timestamps to the server before actual synchronization occurs. This allows the server to pre-process and coordinate the updates, preventing data loss from timestamp conflicts while maintaining fast synchronization throughput.
3Stability of the object's composition
If centralized database management is used, then data consistency is improved, but device complexity and network dependency increase
Solution Approach 1:
The patent segments the database management function, with the server handling centralized coordination and timestamp management, while individual devices maintain their own local databases and change logs. This segmentation provides data consistency through centralized coordination without requiring full centralization, thereby reducing device complexity and network dependency.
Solution Approach 2:
The server serves as an intermediary that provides centralized coordination for data consistency without requiring constant network connectivity or complex device architecture. Devices can operate semi-independently with the server mediating synchronization conflicts and maintaining overall data consistency across the distributed system.
Data Source
AI summary
A technique for distributed management of attributes includes propagating attributes based upon attribute-granularity permissions. An example of a system according to the technique may include a server, coupled to a first client and a second client, that includes a module that receives attribute data from the first client; a permissions database where first permissions associated with the first client are set at the individual attribute level for the second client; an engine for updating the permissions database and for validating the first permissions for the second client; and an engine for distributing first client updates based on validated permissions to destinations associated with the one or more second destination stores.