Self-Installing Network Devices Address Allocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network address allocation methods for interconnected devices rely on central servers or authorities, leading to single points of failure, complexity in resource management, and require users to maintain network information, especially when a large number of devices are turned off or added.
Innovation Solution
A self-installing network system where devices assign themselves a network address consisting of a subnet and node identifier, broadcasting it to other devices without waiting for a response, allowing them to keep the address if a conflict occurs, and verifying connections without relying on a central server or authority.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If a central server is used to allocate network addresses (DHCP), then address allocation is automated, but the system introduces a single point of failure and requires users to maintain network information
Solution Approach 1:
The patent segments the centralized address allocation function into distributed peer-to-peer address assignment. Each device independently assigns addresses to itself and other devices on the network, eliminating the single central server and distributing the allocation function across multiple nodes. This segmentation resolves the contradiction by maintaining automation while removing the single point of failure.
Solution Approach 2:
The patent implements self-service through automatic peer-to-peer address assignment where devices autonomously assign and manage their own network addresses without requiring central server intervention or user maintenance. Devices automatically detect address conflicts and resolve them through predefined protocols, eliminating the need for users to maintain network information while ensuring continuous operation even without central coordination.
2Device complexity
If static addressing is used with user assignment, then address allocation is simple, but it becomes cumbersome and difficult to maintain for more than a few devices
Solution Approach 1:
The patent applies self-service by enabling devices to automatically assign and manage their own network addresses without user intervention. Each device independently generates and assigns addresses to itself and other devices, automatically detecting and resolving conflicts through broadcast protocols. This eliminates the need for users to manually track and maintain address assignments, making the system scalable to large numbers of devices while keeping operational complexity low.
3Extent of automation
If hailing approach is used for address assignment, then devices can self-assign addresses, but there is a failure in the system when a device with duplicate resource is turned off and back on
Solution Approach 1:
The patent implements feedback mechanisms where devices continuously broadcast their assigned addresses and monitor for conflicts. When a device restarts, it broadcasts its address and receives feedback from other devices indicating whether the address is already in use. This continuous feedback loop allows the system to dynamically detect and resolve address conflicts, ensuring reliability after device restarts while maintaining self-installation capability.
Solution Approach 2:
The patent applies preliminary action by having devices pre-establish address conflict detection and resolution protocols before conflicts occur. Devices are pre-configured with algorithms to detect duplicate addresses through broadcast protocols and automatically resolve conflicts by assigning alternative addresses. This preliminary preparation ensures that when devices are turned off and back on, the system can quickly detect and resolve any address conflicts without manual intervention.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
One embodiment of the invention employs techniques for the self-installation of network devices using fire-and-forget principles. These devices modify their own network configuration data, but do not modify the network configuration data of other devices. Utilizing fire-and-forget principles, the need for a central database and central authority on the network is not required but may still be used.