Multi-Hop Network Clustering for Broadcast Collision Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-hop connection networks, especially in dense sections, broadcast message flooding leads to high collision probabilities, resulting in unsuccessful message transmission to some or all network participants, and existing methods require significant resources and cause delays in propagating messages effectively.
Innovation Solution
A self-organizing method where network participants form clusters with each participant potentially acting as a cluster head, using gateways for message transmission and employing parallel routes to monitor and ensure message delivery, reducing the need for a higher-level control unit and minimizing resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If broadcast message flooding is used to ensure all network participants receive the message, then message delivery coverage is improved, but collision probability increases significantly in dense network sections
Solution Approach 1:
The network is divided into clusters with cluster heads that coordinate message repetition. Instead of every node flooding messages independently, only designated cluster members repeat messages, segmenting the flooding function to reduce collisions while maintaining coverage.
Solution Approach 2:
Cluster heads act as intermediaries that receive broadcast messages and coordinate their repetition by member nodes. This intermediary structure organizes the flooding process, reducing random collisions while ensuring messages reach all participants through coordinated retransmission.
2Productivity
If a higher-level control unit is used to manage cluster formation and message routing, then message transmission efficiency is improved, but device complexity and resource requirements increase
Solution Approach 1:
The network performs self-organization through distributed cluster formation algorithms where nodes autonomously select cluster heads and establish membership. Message routing is determined by cluster topology rather than centralized control, enabling efficient transmission without requiring resource-intensive control units.
Solution Approach 2:
The system changes the control parameter from centralized hierarchical management to distributed autonomous decision-making. Each node uses local information and simple rules to determine cluster membership and message repetition behavior, achieving efficiency without complex control logic.
3Reliability
If relatively long waiting times are provided between broadcast packet reception and possible packet repetition to reduce collision probabilities, then collision probability is reduced, but noticeable delays occur in broadcast propagation
Solution Approach 1:
Nodes perform preliminary actions during cluster formation by storing identification data of their own cluster head and neighboring cluster heads. This preliminary preparation enables immediate recognition and coordinated repetition of broadcast messages without requiring long waiting times, reducing propagation delay while maintaining low collision probability.
4Quantity of substance
If network participants with low processor performance and memory capacity are used, then device cost and resource consumption are reduced, but the ability to manage complex cluster formation and message routing deteriorates
Solution Approach 1:
The system changes the operational parameters of low-resource devices by simplifying their tasks to local cluster management rather than global network control. Nodes only need to store cluster head identifiers and follow simple repetition rules based on cluster membership, enabling low-resource devices to participate effectively in complex multi-cluster networks.
Data Source
Figure 1~3a
Figure 2
Figure 3b~3c
AI summary
The method involves transmitting an initialization broadcast by a network subscriber that is defined as cluster head. The initialization broadcast is received with sufficient signal strength by all subscribers. The cluster head stores the network subscribers identifications. The cluster head receives the acknowledgment message of a network subscriber, whose identification is not stored. The network subscribers receives a rejection message. A cluster element of a cluster is selected as a gateway for communication between the cluster head of the cluster and neighboring cluster.