Metadata Syncing via Parent Node Propagation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current delta sync technology for large hierarchical datasets requires significant server resources and bandwidth, as well as being time-consuming, due to the need to transmit all updated data items across endpoints, including children nodes that inherit metadata from parent nodes.

Innovation Solution

A method where a client computing device requests and receives updated metadata only for the parent node, storing it locally and propagating the changes to children nodes without requiring the server to transmit metadata for all children nodes, thereby reducing processor load, memory usage, and network bandwidth.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If current delta sync technology transmits all updated data items including children nodes, then complete data synchronization is achieved, but server resources, bandwidth, and time consumption increase significantly

Engineering Contradiction:
Improvedata synchronization completenessVSAvoidserver resources and bandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent segments the metadata synchronization process by identifying parent-child node relationships in hierarchical datasets. Only metadata changes at parent nodes are transmitted to the client, while children node updates are performed locally through propagation, dividing the sync workload between server and client

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts and transmits only the essential parent node metadata changes from the server, separating this critical information from the redundant children node data that can be derived locally through propagation, thus reducing network transmission volume

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If all updated data items are transmitted across endpoints, then complete metadata synchronization is ensured, but the process becomes time-consuming and resource-intensive

Engineering Contradiction:
Improvemetadata synchronization accuracyVSAvoidsync operation duration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary propagation of parent node metadata changes to children nodes at the client side before full synchronization is complete. This preliminary local update reduces the perceived sync time for users while the background process continues to synchronize remaining data

Inventive Principle:
Principle #10Preliminary action

3Stability of the object's composition

If metadata for all children nodes is transmitted by the service, then complete data consistency is maintained, but network bandwidth and processor load increase

Engineering Contradiction:
Improvedata consistencyVSAvoidnetwork bandwidth usage
Core Design Contradiction:
Stability of the object's compositionVSQuantity of substance

Solution Approach 1:

The patent creates local copies of parent node metadata at the client and propagates these copies to children nodes through local processing. This copying approach maintains data consistency while avoiding the need to transmit original children node data across the network

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11693827B2Syncing and propagation of metadata changes across multiple endpoints
Publication Date: 2023.07.04 MICROSOFT TECHNOLOGY LICENSING LLC
  • US11693827B2 patent drawing
  • US11693827B2 patent drawing
  • US11693827B2 patent drawing

AI summary

Aspects of the present disclosure relate to systems and methods for syncing and propagating updated metadata across multiple endpoints. In one aspect, a request is sent from a client computing device to a service for updated metadata of a dataset. When updated metadata is identified at the service, updated metadata associated with a parent node of the dataset may be received at the client computing device without requiring the service to send updated metadata for one or more children nodes in the dataset. store the updated metadata associated with the parent node of the dataset may be stored in a local data store at the client computing device.