Decentralized Image Management via Peer-to-Peer Distribution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Centralized image repositories face issues with availability, efficiency, and scalability due to technical issues, network problems, and hardware constraints, leading to non-persistent images that are not readily accessible when the central server is unavailable, and overburdened repositories result in decreased download and execution speed.

Innovation Solution

A decentralized image management system using a peer-to-peer network with a distribution engine that distributes images across multiple nodes, allowing images to be stored and retrieved efficiently, even if one node is unavailable, and enabling scalable storage and retrieval by determining optimal nodes based on availability and storage capacity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If images are stored in a centralized repository, then image management is simplified, but availability decreases when the central server is unavailable

Engineering Contradiction:
Improveimage management complexityVSAvoidimage availability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the centralized image repository into multiple distributed nodes across a peer-to-peer network. Each node stores copies of images, allowing the system to maintain availability even when individual nodes fail. This segmentation transforms the single point of failure into a distributed architecture where images are replicated across multiple locations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements copying by creating multiple replicas of images across different nodes in the peer-to-peer network. Instead of storing a single copy in a centralized repository, the system distributes copies to multiple nodes, ensuring that if one node becomes unavailable, other nodes still hold the image data.

Inventive Principle:
Principle #26Copying

2Device complexity

If a single centralized repository is used, then storage infrastructure is simplified, but retrieval speed decreases due to overburdening

Engineering Contradiction:
Improvestorage infrastructure complexityVSAvoidimage retrieval speed
Core Design Contradiction:
Device complexityVSSpeed

Solution Approach 1:

The patent segments the storage infrastructure into multiple distributed nodes rather than a single centralized repository. This segmentation allows retrieval operations to be distributed across multiple nodes, reducing the load on any single node and improving overall retrieval speed through parallel data fetching.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent transitions from a one-dimensional centralized storage model to a multi-dimensional distributed storage model across the peer-to-peer network. This dimensional change enables simultaneous access from multiple nodes, effectively increasing the throughput and retrieval speed without proportionally increasing infrastructure complexity.

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

3Quantity of substance

If a centralized repository is scaled up, then storage capacity increases, but system complexity and hardware requirements increase

Engineering Contradiction:
Improvestorage capacityVSAvoidsystem complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent segments the storage capacity requirement across multiple peer-to-peer nodes rather than concentrating it in a single scaled-up centralized repository. Each node stores a portion of the data, and the collective capacity of all nodes provides the required storage volume. This segmentation allows linear scaling of capacity without quadratic increase in system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses copying to replicate data across multiple nodes, enabling storage capacity to scale by adding more nodes rather than by expanding a single centralized system. Each additional node contributes to the total storage capacity while maintaining relatively simple individual node implementations.

Inventive Principle:
Principle #26Copying

4Device complexity

If images are stored non-persistently in a centralized repository, then infrastructure cost is reduced, but accessibility decreases when the repository is unavailable

Engineering Contradiction:
Improveinfrastructure costVSAvoidimage accessibility
Core Design Contradiction:
Device complexityVSEase of operation

Solution Approach 1:

The patent implements copying by creating multiple replicas of images across different nodes in the peer-to-peer network. Instead of storing a single copy in a centralized repository, the system distributes copies to multiple nodes, ensuring that if one node becomes unavailable, other nodes still hold the image data.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent applies beforehand cushioning by pre-distributing image copies to multiple nodes before any failure occurs. This proactive replication ensures that when node failures happen, image accessibility is maintained without interruption, as redundant copies are already in place across the distributed network.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS10970308B2Method and system for decentralized image management
Publication Date: 2021.04.06 SAP SE
  • US10970308B2 patent drawing
  • US10970308B2 patent drawing
  • US10970308B2 patent drawing

AI summary

Various embodiments of systems and methods for decentralized image management are described herein. The method includes generating, distributing, and retrieving images on peer-to-peer network. Request for generating an image is received. Multiple components/layers of a to-be-generated image is identified. A layer is stored as a file. Files corresponding to the layers are packaged as an image file representing the image. The packaged image file and/or files of respective layers are distributed across the network, e.g., across a plurality of available nodes upon receiving a distribution command/request. When a request for retrieving the image is received, the nodes storing the multiple layers of the image are identified. The layers are retrieved from the identified multiple nodes. Using the retrieved multiple layers, the image is recreated/generated.