Distributed Tree Protocol for Peer-to-Peer Data Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data synchronization methods rely on servers, which introduce delays, increase bandwidth usage, and pose security risks, as well as provide a single point of failure, making them inefficient and unreliable for maintaining data consistency across multiple computing devices.

Innovation Solution

Implementing a peer-to-peer communication protocol using a distributed tree structure that allows computing devices to synchronize data directly without a central server, utilizing a tree protocol for data management and synchronization, where devices communicate directly to maintain data consistency and redundancy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a central server is used for data synchronization, then data consistency can be maintained across devices, but communication delays increase and bandwidth usage increases

Engineering Contradiction:
Improvedata consistencyVSAvoidcommunication delays
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the centralized synchronization architecture into distributed peer-to-peer synchronization. Each computing device maintains its own copy of the data and synchronizes directly with other devices, eliminating the single central server bottleneck. This segmentation allows parallel synchronization operations to occur simultaneously between multiple device pairs, reducing overall communication delays while maintaining data consistency through the tree structure protocol.

Inventive Principle:
Principle #1Segmentation

2Reliability

If a central server is used for data synchronization, then data consistency can be maintained across devices, but bandwidth usage increases

Engineering Contradiction:
Improvedata consistencyVSAvoidbandwidth usage
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent divides the bandwidth burden by eliminating the central server as a single point of data transfer. Instead, each device participates in synchronized data exchange only with its peer devices, segmenting the overall bandwidth consumption across multiple direct connections. This reduces the total bandwidth usage compared to a centralized model where all data must flow through a single server.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements full data copying across all peer devices rather than centralized storage. Each device maintains a complete copy of the data locally, eliminating the need for continuous data retrieval from a central server. This copying approach reduces bandwidth consumption by allowing devices to work with local copies and only synchronize changes when necessary, rather than constantly accessing central storage.

Inventive Principle:
Principle #26Copying

3Reliability

If a central server is used for data synchronization, then data can be stored centrally, but security risks increase and single point of failure becomes possible

Engineering Contradiction:
Improvedata availabilityVSAvoidsecurity risks
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments the centralized data storage into distributed storage across multiple peer devices. No single device holds all data centrally; instead, data is replicated across the peer-to-peer network. This segmentation eliminates the single point of failure inherent in central server architecture, as the system can continue functioning even if individual devices fail or are compromised.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements self-service security mechanisms where each peer device independently validates and encrypts data according to the tree structure protocol. Devices autonomously manage their own security credentials and data protection without relying on central server security enforcement. This distributed self-service approach reduces security risks by eliminating the central target for attacks while maintaining data availability through redundancy.

Inventive Principle:
Principle #25Self-service

4Device complexity

If a central server is used for data synchronization, then data management can be centralized, but the system becomes less robust and more prone to failures

Engineering Contradiction:
Improvecentralized managementVSAvoidsystem robustness
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the centralized management function into distributed autonomous management across peer devices. Each device independently manages its own data copies and synchronization state according to the tree structure protocol, eliminating the single point of failure in centralized management. This segmentation increases system robustness by allowing the network to continue functioning even when individual devices or connections fail.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP2825976B1System and method for managing data using tree structures
Publication Date: 2017.05.03 BLACKBERRY LTD
  • EP2825976B1 patent drawingFigure 1
  • EP2825976B1 patent drawingFigure 2
  • EP2825976B1 patent drawingFigure 3

AI summary

A distributed tree protocol is provided for managing computing devices that form a peer-to-peer overlay network, and for modifying data that is synchronized between the devices. A method for modifying the data includes representing data in a tree structure. The tree structure includes at least one tree node identified by a tree node ID, the tree node ID including a numerical value representing a path from a root node to the at least one node. The root node and the tree structure are identified by a root node ID. The device can send or receive a peer-to-peer message with an other computing device. The message includes a format value specifying a format of the numerical value, the root node ID, an operation value specifying modification of the data, and at least one tree node ID associated with the modification of the data.