Changing access point (AP) device type based on connectivity to a network
View Patent ↗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.
1. A method for changing a device type of an Access Point (AP) comprising:
creating an all-IAP multicast group comprising a plurality of member Infrastructure Access Points (IAPs) including the Access Point;
multicasting, from at least one multicast heartbeat message (MCHBM) source via a wide area network (WAN), a multicast heartbeat message to the member IAPs of the all-IAP multicast group on a regular basis;
operating the Access Point as an Infrastructure Access Point (IAP) when receiving multicast heartbeat messages (MCHBM) on a WAN port of the Access Point;
determining, at the Access Point, whether the WAN port is connected to the WAN network based on whether the Access Point received at least one multicast heartbeat message on the WAN port; and
operating the Access Point as a Backhaul Mesh Access Point (BMAP) including establishing a route to an IAP for re-establishing connectivity to the WAN network, when it is determined that the WAN port is not connected to the WAN network.
2. A method according to claim 1 , further comprising:
assigning a multicast Internet Protocol (IP) address for the all-IAP multicast group.
3. A method according to claim 1 , wherein determining, at the Access Point, whether the WAN port is connected to the WAN network based on whether the Access Point received at least one of the multicast heartbeat messages, further comprises:
determining, at the Access Point, whether the WAN port is connected to the WAN network based on whether the Access Point has received at least one of the multicast heartbeat messages within a time period.
4. A method according to claim 3 , wherein the Access Point determines that the WAN port is connected to the WAN network when the Access Point has received at least one of the multicast heartbeat messages within the time period.
5. A method according to claim 3 , wherein the Access Point determines that the WAN port is not connected to the WAN network when the Access Point has not received at least one of the multicast heartbeat messages within the time period.
6. A method according to claim 3 , wherein determining, at the Access Point, whether the WAN port is connected to the WAN network based on whether the Access Point has received at least one of the multicast heartbeat messages within a time period, further comprises:
monitoring the WAN network, at the Access Point, for a multicast heartbeat message;
determining, at the Access Point, whether the Access Point has received a multicast heartbeat message from the MCHBM source within a heartbeat window duration;
resetting a missed heartbeat counter of the Access Point when the Access Point has received a multicast heartbeat message from the MCHBM source before the heartbeat window expires;
filtering the multicast heartbeat message to prevent propagation in a Mesh backhaul;
incrementing a missed heartbeat counter of the Access Point when the Access Point has not received a multicast heartbeat message from the MCHBM source within the heartbeat window duration; and
determining, at the Access Point, whether the number of missed multicast heartbeat messages exceeds a threshold number of multicast heartbeat messages.
7. A method according to claim 6 , wherein the Access Point determines that the WAN port is connected to the WAN network when the Access Point determines that the number of missed multicast heartbeat messages is less than or equal to the threshold number.
8. A method according to claim 6 , wherein the Access Point determines that the WAN port is not connected to the WAN network when the Access Point determines that the number of missed multicast heartbeat messages is greater than the threshold number.
9. A method for changing a device type of an Access Point (AP) comprising:
operating the Access point as a Backhaul Mesh Access Point (BMAP) including establishing a route to an Infrastructure Access Point (IAP) for connectivity to a Wide Area Network (WAN) when the Access Point is not connected to the Wide Area Network (WAN);
monitoring, at the Access point, a WAN port for multicast heartbeat messages (MCHBMs) originating from a multicast heartbeat message (MCHBMI source;
determining, at the Access Point, whether the Access Point has received a number of multicast heartbeat messages from the MCHBM source within a time interval;
determining, at the Access Point, that the WAN port of the Access Point has established connectivity to the WAN network when the Access Point determines that the number of multicast heartbeat messages have been received within the time interval; and
operating the Access Point as an Infrastructure Access Point (IAP) when it is determined that the WAN port of the Access Point has established connectivity to the WAN network.
10. A method according to claim 9 , further comprising:
changing the device type of the Access Point to an IAP device type when the Access Point determines that the WAN port of the Access Point has established connectivity to the WAN network.
11. A method according to claim 10 , further comprising:
reconfiguring the Access Point to operate in an IAP mode.
12. A method according to claim 9 , wherein determining, at the Access Point, whether the Access Point has received a number of multicast heartbeat messages from a MCHBM source within a time interval, further comprises:
determining, at the Access Point, whether the Access Point has received a number of multicast heartbeat messages from the MCHBM source within a heartbeat duration;
incrementing a found heartbeat counter that measures a number of multicast heartbeat messages received by the Access point, when the Access Point determines that the Access Point has received a number of multicast heartbeat messages from the MCHBM source within the heartbeat duration;
determining, at the Access Point, whether the number of received multicast heartbeat messages exceeds a threshold number of multicast heartbeat messages; and
determining that the WAN port of the Access Point has established connectivity to the WAN network when the number of received multicast heartbeat messages exceeds the threshold number of multicast heartbeat messages.
13. A method according to claim 12 , further comprising:
resetting the found heartbeat counter that measures a number of multicast heartbeat messages received by the Access Point, when the Access Point determines that the Access Point has not received the number of multicast heartbeat messages from the MCHBM source within the heartbeat window duration.
14. A method according to claim 12 , further comprising:
changing the device type of the Access Point to an IAP device type when the Access Point determines that the WAN port of the Access Point has established connectivity to the WAN network; and
reconfiguring the Access Point to operate in an IAP mode.
15. A method according to claim 14 , further comprising:
ignoring all-IAP multicast group membership reports to prevent a multicast tree from forming to ensure that any multicast heartbeat messages come from a WAN port of the Access Point.