Out-of-Domain Backup in P2P Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing Peer to Peer (P2P) networks face challenges in ensuring data availability and reliability, particularly when a large number of nodes exit the network abnormally, as current backup methods are limited to internal DHT network backups and fail to guarantee data recovery in high-reliability scenarios.

Innovation Solution

The method involves out-of-domain backup operations in a P2P network, where nodes with different domain identifiers collaborate to backup and recover resource information, using a system that includes initiating nodes, connecting nodes, and out-of-domain backup nodes to ensure data availability and reliability across domains.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If resource information is backed up only within the same DHT network using internal backup methods, then the maintenance complexity is low, but the data availability and reliability cannot be guaranteed when many nodes exit abnormally

Engineering Contradiction:
Improvedata availabilityVSAvoidbackup system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a new dimension by enabling backup nodes to exist in different domains (out-of-domain backup) rather than limiting backups to the same domain. This cross-domain backup mechanism increases the search space for available backup copies, improving data availability when nodes within the local domain fail, while maintaining manageable complexity through systematic domain-based organization.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If multiple backup copies are stored in different nodes, then data reliability improves, but the maintenance overhead and storage requirements increase

Engineering Contradiction:
Improvedata reliabilityVSAvoidstorage amount
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies local quality by differentiating between in-domain and out-of-domain backup strategies. Instead of uniformly storing multiple copies everywhere, the system strategically places backup copies both within the same domain (in-domain backup) and in different domains (out-of-domain backup), optimizing the balance between reliability and storage requirements based on local failure scenarios.

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If nodes are organized into domains with different domain identifiers, then out-of-domain backup capability is enabled, but the system complexity and routing overhead increase

Engineering Contradiction:
Improvebackup domain flexibilityVSAvoidnetwork structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the P2P network into multiple domains with different domain identifiers, allowing nodes to be organized in a hierarchical manner. This segmentation enables out-of-domain backup operations while managing complexity through domain-based routing tables and structured communication protocols that handle cross-domain requests systematically.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8856581B2Method for resource information backup operation based on peer to peer network and peer to peer network thereof
Publication Date: 2014.10.07 ZTE CORP
  • US8856581B2 patent drawing
  • US8856581B2 patent drawing
  • US8856581B2 patent drawing

AI summary

The present invention provides a method for resource information backup operation based on peer to peer network, comprising: an initiating node sending an out-of-domain backup node determining request to a connecting node in backup domain, and said out-of-domain backup node determining request including the resource global identifier of said resource information to be backed up, and the connecting node in said backup domain and said host node in which the resource information is saved have different domain identifiers; the connecting node in said backup domain determining an out-of-domain backup node according to information of said resource global identifier and out-of-domain backup rules, and sending routing information of said out-of-domain backup node to said initiating node; and said initiating node sending an out-of-domain backup operation request to said out-of-domain backup node according to said routing information, and said out-of-domain backup node implementing corresponding processing according to said out-of-domain backup operation request.