Decentralized Mapping Data Distribution via IPFS Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Geographic Information Systems (GIS) face challenges in efficiently managing and distributing mapping data, particularly in terms of scalability and latency, due to server-compute intensive operations and limited caching potential, which affects performance and costs.

Innovation Solution

Implementing a decentralized storage system using protocols like InterPlanetary File System (IPFS) and Open Index Protocol (OIP), where mapping data is stored and distributed across a network of nodes, allowing clients to directly access data from identified nodes, reducing reliance on central servers and enhancing peer-to-peer data transfer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If mapping data is stored and distributed from a centralized remote server, then data management is simplified and control is centralized, but server storage and bandwidth requirements increase and scalability is limited

Engineering Contradiction:
Improvedata management complexityVSAvoidserver storage and bandwidth requirements
Core Design Contradiction:
Device complexityVSQuantity of substance

Solution Approach 1:

The patent segments the centralized mapping data storage system into multiple decentralized nodes distributed across the network. Each node stores portions of mapping data, eliminating the need for a single centralized server to hold all data. This segmentation reduces the storage and bandwidth burden on any single server while maintaining data accessibility through the distributed network architecture.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If mapping data is stored on a centralized server, then data access control is simplified, but service interruptions at the server affect data accessibility

Engineering Contradiction:
Improvedata access controlVSAvoiddata accessibility during service interruptions
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent merges multiple independent data access points (decentralized nodes) into the network architecture. Instead of relying on a single centralized server, the system combines multiple nodes that can each provide data access. This merging creates redundancy, ensuring that if one node or server experiences service interruptions, other nodes remain available to provide mapping data, thereby improving reliability without significantly complicating access control through distributed consensus mechanisms.

Inventive Principle:
Principle #5Merging (Combining)

3Quantity of substance

If a decentralized storage system is implemented, then server storage and bandwidth requirements are reduced and reliability is improved, but system complexity increases

Engineering Contradiction:
Improveserver storage and bandwidth requirementsVSAvoidsystem complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent implements self-service mechanisms where decentralized nodes automatically discover and register themselves with the network, and clients autonomously query and retrieve data from appropriate nodes without requiring complex centralized coordination. The system uses automated peer-to-peer communication protocols and distributed data structures that enable nodes to manage their own data storage and sharing, reducing the need for complex centralized management infrastructure while achieving the desired reduction in server requirements.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11880395B2Discovery of mapping data stored on decentralized nodes and distribution of mapping data from decentralized nodes
Publication Date: 2024.01.23 MEDICI VENTURES INC
  • US11880395B2 patent drawing
  • US11880395B2 patent drawing
  • US11880395B2 patent drawing

AI summary

A computing device includes processor(s), memory(s), and network interface(s). The processor(s) is configured to: cause the computing device to request mapping data for a particular physical location from a remote server using the at least one network interface; receive a unique identifier for the mapping data for the particular physical location from the remote server using the at least one network interface; cause the computing device to query a plurality of network nodes using the unique identifier to identify at least one network node of the plurality of network nodes that can provide the mapping data associated with the unique identifier, wherein the plurality of network nodes does not include the remote server; and receiving the mapping data from the at least one network node identified as being able to provide the mapping data associated with the unique identifier.