Access Point Device Type Switching via Multicast Heartbeat

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In wireless mesh networks, existing technologies lack efficient methods to dynamically adjust node types from Infrastructure Access Points (IAPs) to Backhaul Mesh Access Points (BMAPs) in response to changes in connectivity to a Customer Enterprise Network (CEN), leading to service disruptions and lack of layer 2 notification during failures.

Innovation Solution

Implementing a multicast heartbeat message (MCHBM) system where IAPs and BMAPs change device types based on the receipt of MCHBMs from strategically placed sources within the CEN, allowing IAPs to switch to BMAP mode upon connectivity loss and vice versa when connectivity is restored, using IGMP protocols and multicast processing engines to manage membership and routing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If IAPs operate in infrastructure mode with fixed configuration, then network management is simplified, but adaptability to connectivity changes is reduced

Engineering Contradiction:
Improveadaptability to connectivity changesVSAvoiddevice configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic device type changing where IAPs can automatically transition between infrastructure mode and mesh backhaul mode based on real-time connectivity status. The system monitors heartbeat signals from CEN and dynamically reconfigures node roles, allowing the network topology to adapt flexibly to connectivity changes without manual intervention.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent enables self-organizing behavior where IAPs autonomously detect connectivity status through heartbeat messages and automatically determine when to switch between operational modes. The system uses IGMP protocols and multicast processing to enable nodes to self-manage their configuration based on network conditions, eliminating the need for centralized control during failures.

Inventive Principle:
Principle #25Self-service

2Loss of time

If nodes manually reconfigure device types in response to failures, then control precision is improved, but response time increases

Engineering Contradiction:
Improveresponse time to connectivity changesVSAvoidautomatic reconfiguration capability
Core Design Contradiction:
Loss of timeVSExtent of automation

Solution Approach 1:

The patent implements preliminary configuration where IAPs are pre-programmed with the capability to automatically detect and respond to connectivity failures through heartbeat monitoring. The system is prepared in advance with the necessary protocols (IGMP, multicast processing) so that when failures occur, nodes can immediately begin the reconfiguration process without delay for manual configuration.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses heartbeat messages as a feedback mechanism where IAPs continuously monitor connectivity status from CEN. When heartbeat signals are lost or degraded, the system automatically triggers reconfiguration actions. This closed-loop feedback enables real-time detection and automatic response to connectivity changes, eliminating manual intervention delays.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If the network uses static routing information, then routing stability is improved, but adaptability to topology changes is reduced

Engineering Contradiction:
Improverouting adaptability to topology changesVSAvoidrouting stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements dynamic routing where routing information is automatically updated when IAPs transition between operational modes. The system maintains routing stability during normal operation but enables rapid adaptation when topology changes occur, using multicast heartbeat messages to trigger routing updates only when necessary, thus balancing stability with adaptability.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS7742442B2Changing access point (AP) device type based on connectivity to a network
Publication Date: 2010.06.22 ARRIS ENTERPRISES LLC
  • US7742442B2 patent drawing
  • US7742442B2 patent drawing
  • US7742442B2 patent drawing

AI summary

Techniques are provided for determining whether a particular Access Point (AP) is to be designated as an Infrastructure Access Point (IAP) or a Backhaul Mesh Access Point (BMAP) based on the connectivity of the particular AP to a network which includes at least one multicast heartbeat message (MCHBM) source. Techniques are provided which can allow an Infrastructure Access Point (IAP) to change its device type to a Backhaul Mesh Access Point (BMAP) device type when the IAP determines that connectivity to the network is lost. Other techniques are provided which can allow a Backhaul Mesh Access Point (BMAP) to change its device type to an Infrastructure Access Point (IAP) device type when the BMAP determines that connectivity to the network is established.