Ad-hoc Network Nodes for Distributed Function Execution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing technologies fail to enable effective cooperation among distributed hardware nodes to perform collective functions without a central controller, leading to limitations in network robustness and functionality.

Innovation Solution

A method for creating a temporary collaborative ad-hoc network of hardware nodes that operates peer-to-peer, allowing nodes to dynamically form, modify, and disband networks without a central controller, and maintain lists of network members with a desired level of correctness for initiating functions based on available capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a central controller is used to manage hardware nodes, then network coordination and function execution are simplified, but network robustness and scalability are reduced

Engineering Contradiction:
Improvenetwork coordinationVSAvoidnetwork robustness
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent extracts the central controller from the network architecture, allowing hardware nodes to operate autonomously in a peer-to-peer manner. Each node maintains its own list of other nodes and can independently initiate and execute functions, eliminating the single point of failure that a central controller would represent while still maintaining coordinated network operation through distributed node lists and inter-node communication.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If hardware nodes maintain completely accurate membership lists, then network function execution is ensured, but communication overhead and processing time increase

Engineering Contradiction:
Improvefunction execution accuracyVSAvoidmembership list maintenance time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies partial action by allowing hardware nodes to maintain membership lists with a threshold level of correctness rather than requiring complete accuracy. Nodes can execute functions when the membership list satisfies a predefined threshold, enabling the system to proceed with sufficiently accurate information without incurring the full overhead of maintaining perfectly accurate lists at all times.

Inventive Principle:
Principle #16Partial or excessive action

3Adaptability or versatility

If hardware nodes frequently update membership lists, then network dynamics are captured accurately, but energy consumption and communication overhead increase

Engineering Contradiction:
Improvenetwork dynamics trackingVSAvoidenergy consumption
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent implements periodic action by having hardware nodes update their membership lists at scheduled intervals rather than continuously or with every network change. This periodic update mechanism allows nodes to capture network dynamics over time while significantly reducing the frequency of communication and processing operations, thereby lowering energy consumption and communication overhead.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS9295097B2Temporary collaborative ad-hoc network of hardware nodes to perform function
Publication Date: 2016.03.22 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US9295097B2 patent drawing
  • US9295097B2 patent drawing
  • US9295097B2 patent drawing

AI summary

That a trigger for creating a temporary collaborative ad-hoc network of hardware nodes has occurred is detected. In response, the temporary collaborative ad-hoc network is created via intercommunication among the hardware nodes. After the temporary collaborative ad-hoc network has been created, the temporary collaborative ad-hoc network performs a given function. A particular hardware node within the temporary collaborative ad-hoc network can perform a roll call request so that it ascertains a list of the hardware nodes within the temporary collaborative ad-hoc network. Performing the roll call request can include ascertaining that a correctness of the list of the hardware nodes satisfies a threshold, such that the correctness of the list of the hardware nodes is not necessarily completely correct.