Network Node Clock Synchronization Timeout Mechanism

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mesh network synchronization methods consume significant network resources due to unnecessary beacon propagation from leaf nodes, which can lead to inefficiencies in clock synchronization and channel hopping processes.

Innovation Solution

Implementing a synchronization timeout period and leaf node classification to determine if a node is a leaf node, allowing it to refrain from sending beacons and adjusting synchronization timeout periods based on node roles, thereby reducing network traffic and improving synchronization efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If classical beacon broadcast synchronization is used, then clock synchronization is achieved, but network resources are consumed excessively due to unnecessary propagation from leaf nodes

Engineering Contradiction:
Improveclock synchronizationVSAvoidnetwork resources
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts and removes the unnecessary beacon propagation function from leaf nodes. By classifying nodes as parent or leaf nodes, the system eliminates the redundant action of leaf nodes broadcasting beacons, thereby reducing network resource consumption while maintaining synchronization reliability through parent node beacon transmission only.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If all nodes propagate beacons continuously, then synchronization is maintained, but network traffic increases unnecessarily

Engineering Contradiction:
ImprovesynchronizationVSAvoidnetwork traffic
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent removes the beacon propagation function from leaf nodes entirely. By implementing node classification, the system extracts only the necessary beacon transmission actions from parent nodes, eliminating redundant network traffic from leaf nodes while preserving synchronization reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of having all nodes broadcast beacons continuously, the patent inverts the approach by having only parent nodes transmit beacons and leaf nodes receive them. This reversal of the traditional all-nodes-broadcast model reduces network traffic while maintaining synchronization.

Inventive Principle:
Principle #13The other way round (Inversion)

3Productivity

If synchronization timeout period is short, then synchronization efficiency improves, but beacon requests may be lost due to busy channels

Engineering Contradiction:
Improvesynchronization efficiencyVSAvoidbeacon reception
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements dynamic adjustment of the synchronization timeout period based on channel conditions and node state. The timeout period is extended when channels are busy or when beacon requests might be lost, and shortened when conditions are favorable, thereby balancing synchronization efficiency with reliable beacon reception.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS8737378B2Synchronization of nodes in a network
Publication Date: 2014.05.27 ITRON GLOBAL SARL
  • US8737378B2 patent drawing
  • US8737378B2 patent drawing
  • US8737378B2 patent drawing

AI summary

Techniques for synchronization of clocks in nodes in a network are described. In one example, a node times or measures a synchronization timeout period. During the synchronization timeout period, the node may hear a beacon. In that event, the node may reset its clock using a time indicator found within the beacon. If the node does not hear a beacon before the end of the synchronization timeout period, the node may send a beacon request to one of its parents. In response, the parent node will broadcast a beacon, which may be heard by other nodes in the vicinity of the parent node. Upon receipt of the beacon and an included time indicator, the node will update its clock. Upon clock update, another synchronization timeout period is then started and the cycle is repeated, thereby maintaining synchronization of the clock with clocks of other nodes.