Wireless AP Upgrade Scheduling for Seamless Client Roaming

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing wireless infrastructure upgrades cause service downtime and disrupt client devices due to unmanaged reboots and association changes, particularly in Software-Defined Access environments where central switching is local and Single Sign On structures are less common.

Innovation Solution

An SDN controller orchestrates AP and WLC upgrades by considering criticality of data transfers, Target Wake Time schedules, and client device sensitivity, using residual-light maps and TWT elasticity profiles to minimize disruption by scheduling reboots and associations based on client device characteristics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If wireless infrastructure upgrades are performed without scheduling, then upgrade speed is improved, but service downtime and client disruption increase

Engineering Contradiction:
Improveupgrade speedVSAvoidservice downtime
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by scheduling AP reboots and client associations in advance based on TWT profiles and criticality assessments. The controller identifies which clients can be reassigned before the reboot occurs and pre-establishes association parameters, ensuring seamless transitions without service disruption.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically adjusts the upgrade schedule based on real-time conditions. The controller monitors client traffic patterns, TWT schedules, and network load to optimize reboot timing. This dynamic scheduling allows the system to adapt to changing network conditions while minimizing service downtime.

Inventive Principle:
Principle #15Dynamics

2Ease of manufacture

If AP reboots are performed without client association management, then reboot simplicity is improved, but client connectivity reliability deteriorates

Engineering Contradiction:
Improvereboot simplicityVSAvoidclient connectivity
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The controller acts as an intermediary between the AP reboot process and client devices. It manages the association transitions by identifying clients that can be reassigned to other APs during the reboot, calculating optimal association parameters, and coordinating the reassociation process to maintain connectivity reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system changes critical parameters such as association parameters, TWT schedules, and power levels before and during the reboot process. By adjusting these parameters in advance and during the transition, the system maintains client connectivity while simplifying the reboot operation.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If all client devices are managed during upgrade, then service continuity is improved, but system complexity increases

Engineering Contradiction:
Improveservice continuityVSAvoidmanagement complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system applies local quality by treating different client devices differently based on their criticality and TWT profiles. Critical clients with strict TWT requirements receive specialized management, while non-critical clients follow standard procedures. This differentiated approach maintains service continuity for essential services while reducing overall management complexity.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The controller segments clients into different groups based on criticality and TWT schedules. This segmentation allows the system to manage clients in batches according to their specific requirements, reducing the complexity of managing all clients simultaneously while ensuring continuous service for critical traffic.

Inventive Principle:
Principle #1Segmentation

4Productivity

If TWT schedules are not considered during upgrade, then upgrade speed is improved, but energy efficiency deteriorates

Engineering Contradiction:
Improveupgrade speedVSAvoidenergy efficiency
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The system performs preliminary assessment of TWT schedules and criticality before scheduling reboots. It identifies clients whose TWT schedules allow for temporary suspension during the upgrade and pre-calculates energy-saving opportunities, ensuring that reboots are scheduled to minimize energy consumption while maintaining service continuity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20260101205A1Upgrading wireless infrastructure through scheduling
Publication Date: 2026.04.09 CISCO TECHNOLOGY INC
  • US20260101205A1 patent drawing
  • US20260101205A1 patent drawing
  • US20260101205A1 patent drawing

AI summary

Wireless infrastructure upgrading may be provided. An Access Point (AP) may be caused to decline new association requests received from client devices not associated with the AP. Next, the AP may be caused to instruct client devices associated with the AP that detect a signal level from the AP to be below their roaming margin to roam away from the AP. Then the power of the signal level from the AP may be decreased by a predetermined amount. Causing the AP to instruct client devices associated with the AP that detect the signal level from the AP to be below their roaming margin to roam away from the AP and decreasing the power of the signal level from the AP may be repeated until the power of the signal level from the AP is at a predetermined level.