Context Data Replication in Multi-User Systems

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Multi-user systems face inefficiencies in information access, as users often cannot easily find desired information due to large volumes of data and the need to repeatedly provide the same information, leading to increased bandwidth usage and processor load.

Innovation Solution

Implementing a context-driven multi-user system that replicates context data subsets between computing devices, allowing each user to access relevant information efficiently while reducing bandwidth and processor load, and managing queries by executing them on devices with readily available input data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all context data is stored centrally on the server, then data consistency is maintained, but bandwidth usage increases and access latency increases

Engineering Contradiction:

Improvedata consistencyVSAvoidbandwidth usage

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The patent segments context data into multiple partitions distributed across different computing devices. Each device stores and processes a specific portion of the context data, allowing parallel access and reducing the load on any single device while maintaining overall data consistency through coordinated updates.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a distributed file system as an intermediary layer between users and the context data. This intermediary manages data replication, caching, and consistency protocols, enabling efficient access to context information without requiring direct connections to the central server for every operation.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Loss of time

If context data is replicated to multiple computing devices, then access latency is reduced, but data consistency becomes more difficult to maintain

Engineering Contradiction:

Improveaccess latencyVSAvoiddata consistency

Core Design Contradiction:

Loss of timeVSReliability

Solution Approach 1:

The patent implements feedback mechanisms where computing devices continuously report their local context data state to the distributed file system. The system uses this feedback to coordinate updates, resolve conflicts, and maintain consistency across all replicated instances of context data without requiring constant central server intervention.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The patent employs preliminary actions by pre-fetching and caching context data that is likely to be needed based on usage patterns. This allows users to access frequently used context information from local caches before it would otherwise need to be retrieved from remote devices, reducing access latency while maintaining consistency through background synchronization.

Inventive Principle:

Principle #10Preliminary action

3Speed

If users access context data from local caches, then access speed increases, but cache coherence becomes more complex

Engineering Contradiction:

Improveaccess speedVSAvoidcache coherence

Core Design Contradiction:

SpeedVSDevice complexity

Solution Approach 1:

The patent creates a universal distributed file system that handles multiple functions including caching, replication, consistency management, and conflict resolution in a unified manner. This multi-functional system provides standardized interfaces and protocols that simplify cache coherence management compared to implementing separate solutions for each function.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Ease of operation

If the system stores complete context data on each device, then access autonomy is improved, but storage requirements and processor load increase

Engineering Contradiction:

Improveaccess autonomyVSAvoidstorage requirements

Core Design Contradiction:

Ease of operationVSQuantity of substance

Solution Approach 1:

The patent applies partial action by storing only the necessary portions of context data locally on each computing device rather than complete datasets. The distributed file system selectively replicates and caches specific context information based on access patterns and user needs, reducing storage requirements while maintaining sufficient local data for autonomous operations.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS11537629B2Replicating data using a replication server of a multi-user system

Publication Date: 2022.12.27 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

A context-driven multi-user system may include distributed computing resource(s) that replicate proper subset(s) of user-relevant context data to computing device(s). A replication server may receive an update record corresponding to stored context data and determine propagation records based at least in part thereon. Each propagation record may correspond to a respective, different proper subset of the context data. The replication server may transmit the propagation records to respective replication clients. A replication client may receive a propagation record and modify local context data in response. The replication client may receive a data record and determine an update record in response and using the local context data. The computing device may transmit the determined update record. A server may receive a query specification referencing a data source and transmit the query specification to a replication client of the multi-user system, the client corresponding to the data source.