Controller Synchronization for Wireless Access Point Configuration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing wireless network access point configurations are not efficiently managed, leading to delays and outages when client devices transition between access points, as current systems often result in unnecessary reconfigurations and downtime due to lack of synchronization of configuration revisions across access point controllers.

Innovation Solution

A system where a team of controller devices manages access points by ensuring each access point is aware of the most recent configuration revision, using a master controller to propagate updated configurations and configuration version indicators across the network, allowing seamless transitions and minimizing reconfiguration delays.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If access points are managed independently without configuration synchronization, then each access point can operate autonomously, but configuration inconsistencies cause seamless transitions to fail and increase network downtime

Engineering Contradiction:

Improveseamless client device connectivityVSAvoidconfiguration management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

A central controller is introduced as an intermediary to manage configuration synchronization across multiple access points. The controller receives configuration data from a master controller and distributes it to all access points, ensuring consistent settings without requiring direct peer-to-peer communication between access points. This mediator approach maintains reliability while managing complexity centrally.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms where access points report their current configuration state and operational status to the central controller. The controller uses this feedback to determine whether configuration updates are needed and to verify successful synchronization. This feedback loop ensures configuration consistency while enabling automated management.

Inventive Principle:

Principle #23Feedback

2Stability of the object's composition

If configuration updates are propagated to all access points immediately, then configuration consistency is maintained, but network downtime increases during transitions

Engineering Contradiction:

Improveconfiguration consistencyVSAvoidnetwork downtime

Core Design Contradiction:

Stability of the object's compositionVSLoss of time

Solution Approach 1:

Configuration updates are prepared and staged in advance by the master controller before being propagated to access points. The central controller queues configuration changes and distributes them systematically, allowing access points to prepare for transitions without immediate reconfiguration. This preliminary action reduces disruption during client device transitions.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The configuration propagation system dynamically adjusts the timing and sequence of updates based on network conditions and access point status. Rather than forcing simultaneous updates to all access points, the system adapts the propagation schedule to minimize impact on ongoing client connections, balancing consistency requirements with downtime reduction.

Inventive Principle:

Principle #15Dynamics

3Measurement precision

If access points reconfigure upon controller changes, then configuration accuracy is ensured, but service interruption occurs during reconfiguration

Engineering Contradiction:

Improveconfiguration accuracyVSAvoidnetwork service continuity

Core Design Contradiction:

Measurement precisionVSProductivity

Solution Approach 1:

The central controller maintains a current copy of the authoritative configuration data received from the master controller. When access points need configuration updates, the controller copies the relevant configuration data and transmits it to the access points. This copying mechanism ensures configuration accuracy without requiring access points to perform complex verification procedures that would cause service interruption.

Inventive Principle:

Principle #26Copying

4Loss of information

If configuration version indicators are tracked across all controllers, then configuration revisions are synchronized, but communication overhead between controllers increases

Engineering Contradiction:

Improveconfiguration revision synchronizationVSAvoidcontroller communication overhead

Core Design Contradiction:

Loss of informationVSLoss of energy

Solution Approach 1:

The configuration version indicator tracking function is extracted from individual access point controllers and centralized in the central controller. The central controller maintains the authoritative version information and distributes it to access points only when configuration changes occur. This extraction eliminates redundant version tracking across multiple controllers, reducing communication overhead while maintaining synchronization.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS9161239B2Network access point management

Publication Date: 2015.10.13 HEWLETT PACKARD ENTERPRISE DEV LP

AI summary

Network access point management includes: connecting to a network access point with a first controller device implemented by at least one processor; transmitting an updated configuration for the network access point from the first controller device to the network access point; transmitting a new value for a configuration version value stored by the network access point to the network access point; and transmitting the new value for the configuration version value stored by the network access point from the first controller device to each controller device in a group of controller devices to which the first controller device belongs.