SyncGUID Hash Synchronization for Network Service Nodes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for synchronizing services across network nodes using counters are inadequate, as they fail to account for events like reboots, firmware upgrades, and disconnections, leading to errors and excessive bandwidth usage due to unnecessary transmission of full service lists.
Innovation Solution
The use of a persistent globally unique identifier (SyncGUID) generated using a hash function to represent the nature and type of services available at a node, which is multicasted upon changes, allowing for efficient synchronization while accounting for various events and reducing the amount of detailed data transmitted.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If counter values are used to synchronize services between nodes, then synchronization can be triggered when changes occur, but the counter values become useless or lead to errors after events like reboots, firmware upgrades, or disconnections
Solution Approach 1:
The patent changes the synchronization parameter from a simple counter value to a hash-based identifier (SyncGUID) that is derived from the service list. This parameter change allows the system to reliably detect synchronization needs while adapting to various network events like reboots and disconnections, as the hash will naturally differ when services change and can be regenerated after events.
Solution Approach 2:
The patent introduces a hash function as an intermediary between the service list and the synchronization identifier. Instead of directly using counter values or service list details, the hash function transforms the service list into a compact SyncGUID that serves as a reliable mediator for detecting synchronization needs without being affected by the underlying events.
2Loss of information
If full service lists are transmitted between nodes upon synchronization needs, then complete service information is synchronized, but significant bandwidth and network resources are consumed
Solution Approach 1:
The patent extracts only the essential synchronization information from the full service list by computing a hash value (SyncGUID). Instead of transmitting or comparing entire service lists, nodes only exchange these compact hash identifiers, which represent the complete service state without the detailed data, thereby minimizing bandwidth consumption while maintaining synchronization completeness.
Solution Approach 2:
The patent transforms the service list information into a different representation form (hash-based identifier) that preserves the essential synchronization information while occupying minimal space. This transformation is analogous to changing the 'color' or form of data representation, converting detailed service information into a compact SyncGUID that can be efficiently transmitted and compared.
Applied Scientific Principles
This section explains which scientific principles are used to turn an abstract innovation direction into a practical engineering solution.
Function Achieved in This Case
This approach ensures accurate synchronization of services across network nodes, accounting for events like reboots and disconnections, while minimizing bandwidth consumption by only transmitting necessary data.
Implementation Method 1
generates a SyncGUID by using a hash function applied to the list of services available locally at the network-enabled device
Data Source
AI summary
A network-enabled device is synchronized with other nodes. Services are run on the device, including at least a node service and a service repository service. Peer nodes on a network are accessed, and a service list which includes services available locally at the network-enabled device and services available remotely at peer nodes is maintained at the service repository service. The node service manages synchronized access to the service list by multicasting a change notification responsive to a change in the services available locally, and by listening to multicasts of change notifications from peer nodes. Responsive to a change in local services, the node service collects a list of local services at the device, generates a SyncGUID by using a hash function applied to the list of services, formats a change notification message which includes the SyncGUID, and multicasts the formatted change notification message to peer nodes on the network.