Meshnet IP Address Resolution via Third-Party Mediator

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mesh networks face challenges in efficiently managing and optimizing communication between meshnet devices, particularly in configuring and updating correlations between devices and their respective meshnet IP addresses, which leads to inefficient resource utilization.

Innovation Solution

The proposed solution involves a method where a first meshnet device communicates with a third-party web application to transmit and receive associations between meshnet devices and unique identifiers, enabling the retrieval and transmission of meshnet IP addresses and communication packets, thereby facilitating efficient communication without the need for storing correlations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If meshnet devices store and manage correlations between devices and meshnet IP addresses locally, then communication can be established, but device complexity and resource utilization increase

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidcorrelation management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a third-party web application as an intermediary service that centrally manages the correlation between meshnet devices and their IP addresses. Instead of each device maintaining its own correlation tables, the system uses this external mediator to resolve IP address mappings, significantly reducing the complexity burden on individual meshnet devices while maintaining communication reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system uses unique identifiers as copies or references to device identities rather than storing complete device correlation data locally. Each meshnet device stores only the unique identifier and queries the web application for the corresponding meshnet IP address, replacing complex local correlation storage with simpler identifier-based references.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If meshnet devices continuously update and reconfigure correlations, then network adaptability improves, but resource consumption and overhead increase

Engineering Contradiction:
Improvenetwork adaptabilityVSAvoiddevice resource utilization
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The web application serves as a centralized mediator that handles all correlation updates and reconfigurations. When network conditions change or devices join/leave the network, the system updates the central database and notifies affected devices only when necessary, eliminating the need for continuous local reconfiguration and reducing overall system overhead.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Instead of continuous correlation updates, the system employs periodic or event-driven updates where changes are propagated to meshnet devices only when necessary (e.g., when a device joins or leaves the network). This periodic action model maintains network adaptability while minimizing resource consumption compared to continuous updates.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS12273319B2Optimizing communication between meshnet devices in a mesh network
Publication Date: 2025.04.08 UAB 360 IT
  • US12273319B2 patent drawing
  • US12273319B2 patent drawing
  • US12273319B2 patent drawing

AI summary

A method in a mesh network including a first device and a second device, the method including receiving, by the first device from a third-party application installed on the first device, an initiation packet including information to be received by the second device, the initiation packet indicating a meshnet IP address assigned to the second device as a destination address; transmitting, by the first device via a meshnet connection between the first device and the second device, the initiation packet to the second device; receiving, by the first device via the meshnet connection and based at least in part on transmitting the initiation packet, a response packet from the second device, the response packet including information to be received by the third-party application; and transmitting, by the first device, the response packet to the third-party application is disclosed. Various other aspects are contemplated.