Distributed Ledger Software Acquisition in Wireless Ad Hoc Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Autonomous machines operating in wireless ad hoc networks face challenges in distributing software modules to perform specific data processing tasks without human intervention, as they often lack the necessary software modules and require complex communication protocols.
Innovation Solution
A distributed ledger-based system that enables autonomous machines to autonomously determine the need for software modules, search for and acquire them across a network of nodes, and utilize them for task execution, with features like immutable entries for access rights and network synchronization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If autonomous machines are pre-loaded with software modules, then they can perform data processing tasks independently, but the system lacks adaptability when new software modules are needed during mission operations
Solution Approach 1:
The autonomous machine autonomously determines its own software needs, searches for required software modules in the distributed ledger, negotiates with other nodes, and completes the software acquisition process without human intervention. The system self-manages the entire software distribution lifecycle including need identification, searching, authorization verification, and module installation.
Solution Approach 2:
The distributed ledger serves multiple functions: it stores software module information, manages authorization rights, tracks software locations across the network, and facilitates peer-to-peer transactions. This universal data structure enables the autonomous machine to perform diverse software acquisition tasks using a single unified system.
2Productivity
If software modules are distributed manually with human intervention, then authorization and control can be maintained, but operational efficiency and response time are significantly reduced
Solution Approach 1:
The autonomous machine independently identifies software needs, queries the distributed ledger for available modules, verifies authorization rights, negotiates with other nodes in the network, and completes the software installation process entirely autonomously without requiring human operators to intervene in each software acquisition event.
Solution Approach 2:
The distributed ledger is pre-configured with software module information, authorization rights, and node location data before the autonomous machine needs the software. This preliminary structuring of data enables rapid autonomous queries and transactions when software is needed during mission operations.
3Reliability
If a centralized software distribution system is used, then control and authorization are simplified, but the system lacks robustness and fails when the central server is unavailable
Solution Approach 1:
The centralized software distribution system is segmented into multiple independent nodes that each maintain a copy of the distributed ledger. Software module information is distributed across the network rather than centralized in a single server, allowing any node to serve software requests and maintaining system functionality even when individual nodes fail or are unavailable.
Solution Approach 2:
Each node in the distributed network maintains local copies of the distributed ledger with software module information specific to its context and capabilities. This local quality enables nodes to independently verify authorization and provide software services without requiring constant communication with a central authority, enhancing system robustness.
Data Source
AI summary
A method of acquiring software by a source node in a wireless ad hoc network. The method includes the source node executing application software from which a need to perform a task is identified, and making a determination that the source node is incapable of performing the task. Responsive to the determination, the source node searches a local module repository (MR) of the source node for a software module usable to perform the task, and responsive to the source node failing to locate the software module in the local MR, broadcasts a request for the software module to neighbor nodes of the plurality of nodes in radio range of the source node. The source node receives the software module from the neighbor node, and uses the software module to perform the task.