Role-Based Network Startup Timing to Prevent Attachment Collisions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing load control systems face challenges in efficient network formation due to message collisions during the attachment process of control devices, leading to delayed network installation and operation, especially as the scale of the network increases.
Innovation Solution
Control devices are configured to form a network at a unique coordinated startup time based on their assigned roles in a previously-formed network, with specific procedures for attachment and message transmission to avoid collisions and ensure reliable network formation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If control devices attach to the network simultaneously during startup, then network formation can begin quickly, but message collisions occur leading to failed attachments and delayed network installation
Solution Approach 1:
The patent applies preliminary action by having control devices determine their startup sequence based on role information obtained before actual network attachment. Devices query existing networks or receive role assignments in advance, then use this information to calculate offset values that stagger their startup times. This preliminary role determination enables coordinated startup without simultaneous attachment attempts, resolving the contradiction between quick network formation and attachment success rate.
Solution Approach 2:
The patent implements dynamics by making startup times adaptive rather than static. Each control device dynamically adjusts its startup offset based on its assigned role, the network type, and the number of hops from the leader device. This dynamic timing adjustment ensures that devices with different roles attach at different times, preventing message collisions while maintaining efficient network formation. The startup sequence is flexible and can be modified based on real-time network conditions.
2Device complexity
If control devices use fixed startup times, then network formation is simple to implement, but message collisions occur during attachment processes
Solution Approach 1:
The patent applies parameter changes by modifying the startup time parameter based on multiple factors including device role, network type, and hop count. Instead of using a fixed startup time, each device calculates its startup offset by combining a base offset with role-specific and topology-specific adjustments. This parameter transformation approach maintains relatively simple implementation while significantly improving message transmission reliability by staggering attachment times and avoiding collisions.
3Loss of time
If all control devices attach to the network at the same time, then network installation is faster, but the likelihood of message collisions and attachment failures increases
Solution Approach 1:
The patent applies segmentation by dividing the network startup process into distinct phases and time segments based on device roles. Instead of simultaneous attachment, devices are segmented into different attachment groups (leader devices, router devices, end devices) that attach at different offset times. This segmentation prevents message collisions by ensuring that only one device type attempts attachment at any given time, while the overall process remains efficient because the segmentation is based on predetermined role information rather than sequential one-by-one attachment.
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
A control device may be configured to form a network at a unique coordinated startup time. The control device may identify a role assigned to the control device in a previously-formed network that the control device was attached to. The control device may determine a unique coordinated startup time for the control device based on the role assigned to the control device in the previously-formed network. The control device may initiate a network formation procedure at the unique coordinated startup time for the device. For example, the network formation procedure may cause the control device to attach to another control device in the network. The network formation procedure is configured to enable the control device to assume the role assigned to the control device in the previously-formed network in the new network.