Mesh Network Configuration Synchronization via Version Tracking

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Mesh network systems face inconsistencies in configuration settings among APs due to environmental interference and unpredictable situations, leading to disconnected networks and inconsistent operations.

Innovation Solution

A configuration synchronization method where extender network devices transmit configuration version numbers to a root device, which updates and synchronizes configuration values if they differ, ensuring all devices have the same settings and version numbers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Area of stationary object

If APs automatically connect to each other to extend coverage in a mesh network, then network coverage is improved, but configuration consistency deteriorates due to unpredictable situations like environmental interference and temporary shutdowns

Engineering Contradiction:

Improvenetwork coverageVSAvoidconfiguration consistency

Core Design Contradiction:

Area of stationary objectVSReliability

Solution Approach 1:

The system performs preliminary actions by establishing configuration version numbers before network operations begin. Each AP is pre-configured with a version number that identifies its configuration state, allowing the network to detect and resolve inconsistencies before they cause operational failures. This preliminary version tracking enables proactive synchronization rather than reactive troubleshooting.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements a feedback mechanism where APs continuously report their configuration version numbers to the network manager. When the network manager detects version mismatches, it triggers re-synchronization operations. This closed-loop feedback system ensures that configuration inconsistencies are automatically detected and corrected, maintaining reliability while APs dynamically adjust their positions and connections to extend coverage.

Inventive Principle:

Principle #23Feedback

2Adaptability or versatility

If new settings are applied to some APs while others retain old settings, then adaptability to local conditions is improved, but network operation consistency deteriorates

Engineering Contradiction:

Improvelocal configuration adaptabilityVSAvoidnetwork operation consistency

Core Design Contradiction:

Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The configuration management system is segmented into hierarchical levels: a network manager that handles global configuration policies and individual APs that can have local customizations. The version number system segments configuration tracking into manageable units, allowing the network manager to apply updates selectively to different AP segments while maintaining overall network consistency through version control.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent uses configuration version numbers as parameters to track and manage changes. When local adaptations are needed, the system modifies specific configuration parameters at the AP level while maintaining the version number framework. This allows parameter-level flexibility (local adaptability) while preserving the overall configuration structure (network consistency) through versioned change management.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If configuration synchronization is performed frequently to maintain consistency, then configuration consistency is improved, but network traffic overhead increases

Engineering Contradiction:

Improveconfiguration consistencyVSAvoidnetwork traffic overhead

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

Instead of continuous synchronization, the system implements periodic configuration checks based on version number comparisons. APs report their version numbers at intervals or when changes occur, and the network manager triggers synchronization only when version mismatches are detected. This periodic action reduces unnecessary traffic while maintaining configuration consistency through targeted updates.

Inventive Principle:

Principle #19Periodic action

Solution Approach 2:

The configuration synchronization system operates with a degree of self-service through automatic version number comparison and triggered updates. APs autonomously report their version status, and the network manager automatically initiates synchronization only when needed. This self-service mechanism reduces manual intervention and minimizes network traffic by eliminating redundant synchronization operations.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS11044687B2Configuration synchronization method and mesh network system

Publication Date: 2021.06.22 WISTRON NEWEB CORP

AI summary

A configuration synchronization method includes a first extender network device transmitting an extender configuration version to a root network device; the root network device determining whether the extender configuration version is the same as a second root configuration version currently owned by the root network device; and when the extender configuration version is different from the second root configuration version, the root network device transmitting the second root configuration version and a plurality of root network configurations corresponding to the second root configuration version to the first extender network device; a first extender network device updating a plurality of extender network configurations thereof to be the plurality of root network configurations, and updating the extender configuration version thereof to be the second root configuration version.