Patent Description:
The IEEE <NUM> WLAN standards specify a bandwidth of <NUM> and channels are on a <NUM> incremental step. Nominal figures for the channel bandwidth of <NUM> are often given. The <NUM> / <NUM> bandwidth and channel separation of <NUM> means that adjacent channels overlap and signals on adjacent channels will interfere with each other.

The <NUM> Wi-Fi bandwidth includes unlicensed industrial, scientific and medical (ISM) channels as well as numerous channels that fall outside the accepted ISM unlicensed band and, as a result, various restrictions are placed on operation at these frequencies. The main concern for using channels that fall outside the ISM unlicensed band is that the Wi-Fi equipment may interfere with operations of weather-radar and military applications (such as military radar and/or communications). To prevent interference, Wi-Fi equipment that operates in these frequencies must implement Dynamic Frequency Selection (DFS) capabilities on these channels. DFS is supported by the IEEE <NUM> wireless local area network standard. DFS is also mandated in the <NUM>-<NUM> Unlicensed National Information Infrastructure (U-NII) band for radar avoidance.

DFS is a spectrum-sharing mechanism that allows wireless LANs (WLANs) to coexist with radar and other systems. A DFS system listens on a specific band for signal from, e.g., a radar system. If the DFS system detects a signal, the DFS system automatically selects a different frequency channel and examines the different frequency to see if there is any other equipment operating on it. The DFS system then selects and uses a <NUM> frequency channel that does not interfere with any radar system.

DFS rules only apply to the frequency band between <NUM> and <NUM>, which is the frequency band used by weather and military radars. It should be noted that DFS based systems are effective only when the incumbent system includes a transmitter that operates over the same frequency channel and as such announces the existence of a receiver on that frequency channel. <CIT> relates to a system, method, and apparatus for setting a regulatory operating mode of a device. More particularly <CIT> relates to wireless networks and more specifically directed to providing or acquiring an exemplary country code identifier or regulatory domain for a nonlimiting device operating in a reduced functionality radio frequency (regulatory) mode based on exemplary location factors and exemplary confidence rankings. One embodiment includes an exemplary regulatory domain selection component configured to weigh location factors associated with a device, based on reliability associated with the location factors, and configured to determine an overall confidence of a country code identifier or a regulatory domain for the device. Another embodiment includes a device configured to operate in a reduced functionality radio frequency (regulatory) or worldwide compliant mode until a regulatory domain can be determined through a trusted cloud service which can be configured to weigh one or more location factors or data sources to facilitate providing or acquiring an exemplary country code identifier or regulatory domain for the device. <CIT> relates to a network configuration of WiFi networks via a cloud-based WiFi network manager. <CIT> relates to an access point and method for coexistence of Wi-Fi and airborne radars in the <NUM> band. <CIT> relates to a method and apparatus for managing channels in a WLAN system. <CIT> relates to a dynamic frequency selection in distributed Wi-Fi networks.

According to a first aspect of the invention there is provided a method (<NUM>), the method being performed by a network management system (<NUM>) and comprising: receiving (<NUM>), signal strength measurements of signals reported by a plurality of access points (<NUM>, <NUM>, <NUM>, <NUM>) of a wireless network; receiving, from an access point of the plurality of access points, a notification of a detection of a high priority receiver, HPR, (<NUM>) the notification indicating a channel on which the HPR was detected; determining (<NUM>), based on the signal strength measurements and the notification, a set of access points of the plurality of access points, wherein determining the set of access points comprises estimating, based on the signal strength measurements, a signal strength of the HPR at each access point in the plurality of access points, identifying a subset of the plurality of access points having an estimated signal strength of the HPR that meets a criterion, and including the identified subset of access points into the set of access points; and transmitting (<NUM>), to the set of access points, instructions to avoid operation on the channel.

According to a second aspect of the invention there is provided a network management system (<NUM>), comprising: processing circuitry; one or more memories storing instructions that when executed by the processing circuitry, cause the network management system to perform the following operations: receiving signal strength measurements of signals reported by a plurality of access points (<NUM>, <NUM>, <NUM>, <NUM>) of a wireless network; receiving, from an access point of the plurality of access points, a notification of a detection of a high priority receiver , HPR,, (<NUM>) the notification indicating a channel on which the HPR was detected; determining, based on the signal strength measurements and the notification, a set of access points of the plurality of access points, wherein determining the set of access points comprises estimating, based on the signal strength measurements, a signal strength of the HPR at each access point in the plurality of access points, identifying a subset of the plurality of access points having an estimated signal strength of the HPR that meets a criterion, and including the identified subset of access points into the set of access points; and transmitting, to the set of access points, instructions to avoid operation on the channel.

While the DFS ensures that receivers of high priority equipment are not affected by interference from Wi-Fi equipment, it does not address needs of the Wi-Fi network users. Specifically, an AP, in an effort to comply with <NUM> DFS, switches from a channel in use by a HPR to a second channel. In some circumstances, this second channel may also be in use by a HPR. After some time delay the HPR is detected on the second channel, the AP will switch from the second channel to a third channel. This process could, in some circumstances, repeat for even further channels. During this period of channel switching, performance of the AP experiences some level of impact, which can affect the user community in some circumstances. To avoid this degradation in performance, each AP detecting a HPR should perform fewer channel switches before identifying an available channel. Ideally, an AP could identify in advance which channels are available for use and which channels are utilized by high priority receivers.

This disclosure describes a method for maintaining high service level experience (SLE) for users of a Wi-Fi network in the presence of one or more higher priority device. These higher priority devices operate, in some embodiments, on a <NUM> frequency band. Wi-Fi devices detecting these higher priority devices are required to avoid operations that can interfere with the higher priority devices. Ceasing interfering operations can include switching their operations to a different frequency channel on which the higher priority device is not operating.

To comply with the DFS regulations, when a first AP detects that it is potentially interfering with a higher priority receiver on a first communication channel, the first AP is required to switch its own operation from the first communication channel to a different, second communication channel. The first AP then adds the first communication channel to a "blacklist" that keeps track of channels the first AP is prohibited from operating on. Other APs which do not detect that they might interfere with the higher priority receiver can continue utilizing the first channel for communication. In some circumstances, the first AP determines that the higher priority receiver is not only utilizing a single channel, but is instead operating on an entire frequency band, such as an entire <NUM> frequency band. In this case, simply switching channels within the same band will not reduce the risk of interference with the higher priority receiver. Thus, in this situation, the first AP transitions away from use of the frequency band (e.g. <NUM>) and instead utilizes a completely different frequency band (e.g. <NUM> frequency band).

Some of the disclosed embodiments construct a network connectivity graph. The graph is constructed based on signal strength information measured by each AP included in a Wi-Fi Network. The APs included in the Wi-Fi network forward the measured signal strength information to a network management system. The network management system also has information with respect to a geographic location of each AP reporting the signal strength information.

Based on the location information and signal strength information, the network management system is able to determine a network graph for the Wi-Fi network. Nodes in the network graph correspond, in some embodiments, to devices operating within the Wi-Fi network (e.g. wireless transmitters). Edges in the graph represent signal strengths between devices connected by the edge. In some embodiments, edges of a graph data structure are tagged with respective signal strength information and/or attenuation information. In some embodiments, if attenuation is above a threshold or otherwise meets certain criterion, the edge is not included in the network graph.

In some of the disclosed embodiments, when an AP included in the Wi-Fi network detects a high priority receiver, the AP sends a notification to a network management system. The network management system then relies on the network graph, discussed above, to identify other network devices that are at risk of interference with the high priority receiver. These identified other network devices are then instructed to modify their operation as appropriate to avoid interference with the high priority receiver.

In some embodiments, a network management system receiving a notification of a high priority receiver instructs all other network devices on the Wi-Fi network to avoid channels and/or frequencies upon which the HPR operation has been detected. This is accomplished, in some embodiments, by adding channel information describing where the HPR is operating to a blacklist maintained by a NMS. The NMS blacklist is used to determine Wi-FI channels that one or more APs operating on the Wi-Fi network should blacklist. By adding the HPR channel information to the global back list, proactive steps are taken to prevent interference with the HPR. This also avoids additional channel switching that could be required if other network devices within the wireless network were left to discover the HPR independently.

Some other embodiments determine to modify operation of a subset of network devices based on the detection of the HPR. In some of these embodiments, operation of one or more APs. Which AP's operation is modified is based on criterion. For example, one criterion considers attenuation of signals exchanged between a first AP and a second AP that detected the HPR. If the attenuation of these signals is relatively large (e.g. above a predetermined threshold), then it is not necessary to modify operation of the first AP, in at least some embodiments, as the AP is assumed to be far enough away from the HPR to prevent interference with operation of the HPR. If the attention of the signals exchanged between the two APs is below the predetermined threshold, operation of the first AP is modified, in these embodiments, to avoid transmission on channels upon which an HPR was detected by the second AP (in these embodiments). Some embodiments maintain device specific AP blacklists in addition to the NMS blacklist discussed above. To accomplish modified operation of a subset of the network devices, channel information relating to operation of the HPR is added to device specific blacklists for each device included in the subset.

Some embodiments estimate a HPR transmission signal strength at an AP via Equation <NUM> below: <MAT> where:.

In some embodiments, the network management system determines which APs should be notified of a HPR based on the whether an estimated signal strength at the said AP from a transmitter of the HPR is greater than a predetermined threshold. <MAT> where:.

In some embodiments, the network management system notifies a set of APs within a predetermined proximity to the first AP about the operations of the HPR. For example, this set of APs are notified, in some embodiments, to avoid operations on any channels upon which HPR associated transmissions were detected. In some circumstances, the number of APs included in the set of APs is reduced based on a criterion. For example, in some embodiments, APs that are within a threshold distance of the HPR are not included in the set of APs if they are not also within a predetermined distance on the network graph of the first AP. These embodiments reduce a number of APs that switch to a channel in use by the HPR when the HPR is already known by the network management system.

Some embodiments rely on physical locations (geographic locations, e.g. coordinates) of network devices when determining which devices should be notified about an HPR operating in their proximity. Some embodiments utilize triangulation to obtain a position estimate of the HPR. In some embodiments, the triangulation is based on signal strength measurements received from two or more network devices. Once a location estimate of the HPR is determined, these embodiments provide a notification to network devices within a threshold distance of the HPR.

Some specific network topologies e.g., when the APs of the Wi-Fi network are located substantially on a straight line, affect how selection of network devices to notify is made. For example, when network devices are located along a substantially straight line, which APs are notified is determined after at least two APs have detected the HPR.

<FIG> shows an example system <NUM> implemented in accordance with at least one embodiment. System <NUM> includes a plurality of APs (AP <NUM><NUM>,. , AP X <NUM>, AP <NUM>' <NUM>,. , AP X' <NUM>). In various embodiments, an AP is a wireless AP a router, a switch, or any other device capable of providing network access. The system <NUM> also includes a network management system (NMS) <NUM> (e.g., a NMS blacklist management system (server)). The NMS <NUM> is coupled to the network <NUM> via a connection <NUM>. The network devices shown in <FIG> are in communication with each other via a digital network, such as the network <NUM>, (e.g., the Internet and/or an enterprise intranet). The network <NUM> consists of numerous routers <NUM> and numerous switches <NUM>. Network communications links <NUM> and <NUM> couple the APs (AP <NUM><NUM>, AP X <NUM>, AP <NUM>' <NUM>, AP X' <NUM>) respectively, to network <NUM>. The system <NUM> further includes a plurality of user equipment devices (UE <NUM><NUM>,. , UE Z <NUM>, UE <NUM>' <NUM>,. , UE Z' <NUM>) wherein user equipment is any wired, wireless, or optical equipment providing network access to communication devices used by users such as people or automated devices such as IoT devices. Some of the UEs (<NUM>, <NUM>, <NUM>, <NUM>) are wireless devices which may move throughout system <NUM>.

In the example system <NUM>, APs are located at different customer sites. Customer premise site <NUM><NUM>, includes APs (AP <NUM><NUM>,. , AP X <NUM>). Customer premise site <NUM><NUM>, includes APs (AP <NUM>' <NUM>,. , AP X' <NUM>). As shown in <FIG>, UEs (UE <NUM><NUM>,. , UE Z <NUM>) are currently located at customer premise site <NUM><NUM>; UEs (UE <NUM>' <NUM>,. , UE Z' <NUM>) are currently located at customer premise site <NUM><NUM>. In some embodiments, each one of the servers, routers, switches, APs, UEs NMS, and other servers attached to the network optionally include a system log or an error log. Each one of these devices records the status of the device including normal operational status and error conditions in the error log.

An example HPR <NUM> associated with e.g., weather radar is shown in the vicinity of site <NUM><NUM>. Some or all of the APs in site <NUM>, AP <NUM>' <NUM>, AP X' <NUM>, as well as the APs of site <NUM>, AP1 <NUM>, AP X <NUM>, are within the range to weather radar <NUM>. The weather radar <NUM> is shown generating signals 162a and 162b.

The method described herein minimizes the number of times that APs associated with the system switch to frequency channel used by HPR, e.g., weather radar <NUM>, detect the existence of HPR in their vicinity , and then switch again to a new frequency channel.

<FIG> is a block diagram of an example AP <NUM> (e.g., any of APs AP <NUM><NUM>,. , APX <NUM>, AP <NUM>' <NUM>,. , APX' <NUM>) in accordance with one or more of the disclosed embodiments. Various embodiments include one or more of the components discussed below with respect to AP <NUM> and <FIG>. AP <NUM> includes wired interface <NUM>, wireless interfaces <NUM>, <NUM>, a hardware processor <NUM>, (e.g., a CPU or hardware processing circuitry), a memory <NUM>, and an assembly of components <NUM>, e.g., assembly of hardware components, e.g., assembly of circuits, coupled together via a bus <NUM> over which the various elements may interchange data and information. Wired interface <NUM> includes a receiver <NUM> and a transmitter <NUM>. The wired interface <NUM> couples the AP <NUM> to a network (e.g. network <NUM> of <FIG>). First wireless interface <NUM>, e. , a wireless Wi-Fi interface, e.g. <NUM> interface, includes a receiver <NUM> coupled to a receive antenna <NUM>, via which the AP may receive wireless signals from communications devices, e.g., wireless terminals, and a transmitter <NUM> coupled to a transmit antenna <NUM> via which the AP may transmit wireless signals to communications devices, e.g., wireless terminals. Second wireless interface <NUM>,e. , a Bluetooth interface, includes receiver <NUM> coupled to receive antenna <NUM>, via which the AP may receive wireless signals from communications devices, e.g., wireless terminals, and transmitter <NUM> is coupled to a transmit antenna <NUM>. Via the transmit antenna <NUM>, the AP transmits wireless signals to communications devices, e.g., wireless terminals.

Memory <NUM> includes routines <NUM> and data/information <NUM>. Routines <NUM> include assembly of components <NUM>, e.g., an assembly of software components, and an Application Programming Interface (API) <NUM>. Data/information <NUM> includes configuration information <NUM>, device status log including error events and normal events captured as messages in a system log or an error log <NUM> and a black-list <NUM> which identifies all of the <NUM> channels on which higher priority devices such as weather radar, military communications, etc. have been previously discovered and should not be used.

<FIG> is a block diagram of an example network management system. The NMS <NUM>, also discussed above with respect to <FIG>, in some embodiments, is a network management node, e.g., a network management server such as automated network reconfiguration server. In some embodiments, network management system <NUM> of <FIG> is network management system (NMS) <NUM> of <FIG>. In some embodiments the network management system <NUM> is integrated with an AP or other network device, such as any of the APs or devices shown in <FIG>.

Various embodiments of a network management system include one or more of the components discussed below with respect to <FIG>. The example network management system <NUM> includes a communications interface <NUM>, a processor <NUM>, an output device <NUM>, e.g., display, printer, etc., an input device <NUM>, e.g., keyboard, keypad, touch screen, mouse, etc., a memory <NUM> and an assembly of components <NUM>, e.g., assembly of hardware components, e.g., assembly of circuits, coupled together via a bus <NUM> over which the various elements may interchange data and information. The communications interface <NUM> includes an Ethernet interface in some embodiments. Communications interface <NUM> couples the network management system <NUM> to a network and/or the Internet. Communications interface <NUM> includes a receiver <NUM> via which the network monitoring apparatus can receive data and information, e.g., including service related information, e.g., message such as messages logged in a system log or an error log from a variety of devices such as AAA server, DHCP server, Web server (not shown in <FIG> for simplicity sake), routers, switches, and a transmitter <NUM>, via which the network management system <NUM> can send data and information, e.g., including configuration information and instructions, e.g., instructions to APs, routers, switches, or any other server attached to the network, to restart, change operating parameters, download and install another SW version, etc..

Memory <NUM> includes routines <NUM> and data/information <NUM>. Routines <NUM> includes an assembly of components <NUM> (e.g., an assembly of software components), and an Application Programming Interface <NUM> (API). Data/information <NUM> includes configuration information <NUM>, recorded RSSI log <NUM> including RSSI from each one of the operational APs specifically, including ID of a receiving AP <NUM>, ID of a transmitting AP <NUM>, and RSSI received by the receiving AP from the transmitting AP <NUM>. The memory <NUM> also includes Wi-Fi network graph indicative of the network topology <NUM>. In some embodiments the network graph includes a map of physical deployment locations of APs, and/or an attenuation experienced over a radio path between AP pairs. For example, the table shows that AP ID <NUM> received a signal with RSSI <NUM> from AP ID2, signal with RSSI <NUM> from AP ID3,. , and AP ID <NUM> received signal with RSSI x from AP ID j. In general column <NUM> provides a list of the receiving APs, column <NUM> provides a list of the transmitting APs, and column <NUM> provides a list of the corresponding RSSI. This and other tables are provided for illustration only while other more efficient data structures may be used.

The memory <NUM> also includes a table of measured RSSIs <NUM> (only one data entry of the table is showed). Each data entry includes the ID <NUM> of a wireless device that detected a signal from a transmitter associated with an HPR, an RSSI value <NUM> of the detected signal from the transmitter associated with the HPR, e.g., weather radar <NUM> of <FIG>, and a channel <NUM> in which the signal was detected.

The memory <NUM> also includes a table of estimated RSSIs <NUM> (only one data entry of the table is showed). Each data entry includes the ID of the AP <NUM>, for which the system calculated the estimated RSSI signal from the transmitter associated with the HPR, e.g., weather radar <NUM> of <FIG>, a channel <NUM> for which the estimated RSSI is calculated, and an estimated RSSI <NUM>.

As explained above, the estimated RSSIs are calculated in some embodiments using Equation <NUM> and further based on an estimated attenuation between the AP which received the transmission over the specific channel and the said AP. In some embodiments, the estimated direction and/or estimated location <NUM> of the HPR is calculated using the physical map of the AP deployment. RSSI values received by APs originating from the transmitter associated with the HPR as also utilized when determining the estimated direction and/or estimated location <NUM>.

In some embodiments, the estimated RSSIs <NUM> are compared against a predetermined threshold and if the system determines that the RSSI is greater than a predetermined threshold, the blacklist <NUM> of AP <NUM> is augmented by adding the channel <NUM> to the list of blacklisted channels of that AP. The network management system notifies the specific AP 361of any modification to the blacklist associated with that AP.

In some embodiments, blacklist <NUM> includes a table of the blacklists associated with each AP (for sake of simplicity only one entry is provided in the figure). Each entry of the blacklist <NUM> includes the ID of the AP <NUM> and the channel <NUM> that should be added to the blacklist of that AP.

<FIG> shows an example network graph <NUM> of a network included in the system <NUM> discussed above with respect to <FIG>. The illustrative network has nodes (e.g. APs) {A, B, C, D, E, F, and G}, labeled <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> respectively. The nodes use Wi-Fi channels {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>} respectively. An HPR <NUM> operates on channel <NUM>. The HPR <NUM> is shown generating signals 462a-462c.

Since the HPR <NUM> operates on channel <NUM>, only AP <NUM>, which also operates on channel <NUM>, has detected HPR <NUM>. In accordance with one embodiment, as soon as AP <NUM> notifies a network management system (e.g. NMS <NUM>) of the existence of HPR on channel <NUM>, the network management system notifies all of the APs in the network of the existence of the HPR on channel <NUM>. In response to said notification, in some embodiments, each AP receiving the notification adds channel <NUM> to their respective blacklist.

In other embodiments, the network management system notifies devices determined to be peer neighbors of AP <NUM> of the HPR <NUM>. In some embodiments, peer neighbors are those wireless devices whose signals are visible from the AP <NUM> (and/or those wireless devices with visibility to signals from the AP <NUM>). In the example of <FIG>, peer devices of AP <NUM> include APs <NUM>, <NUM>, <NUM>, and <NUM>. APs <NUM> and <NUM> are not peer neighbors given that the network graph <NUM> does not include a direct connection (edge) connecting AP <NUM> with either AP <NUM> or AP <NUM>. In embodiments that only notify peer devices of the AP detecting the HPR <NUM>, only the peer devices update their blacklists to include channel <NUM> (e.g. the set of channels utilized by the HPR). If APs <NUM> or <NUM> attempts to use channel <NUM>, they may detect that HPR operates on that channel. If AP <NUM> detects HPR <NUM>, the AP <NUM> would notify the network management system, which would propagate channel <NUM> to blacklists of the peer devices of AP <NUM> and may forward it also to AP <NUM>. Some embodiments extend this embodiment to a broader notification that includes not only peer devices but also peer devices of the peer devices. Some embodiments may further extend this embodiment to peer devices of peer devices of peer devices.

In some embodiments, attenuation between wireless devices is determined. The attenuation is used to estimate signal strengths of signals generated by the HPR <NUM>. (e.g. via Equation <NUM>).

In some embodiments, a physical (e.g. geographic) location of wireless devices, along with signal strengths of HPR <NUM> generated signals, received at these wireless devices, are used to estimate a geographic position or location of the HPR <NUM> (e.g. via triangulation). Based on the estimated location of the HPR <NUM>, some of the disclosed embodiments then estimate signal strengths of HPR <NUM> signals at the wireless devices. Those devices having signal strengths meeting a criterion (e.g. above a threshold) are then notified to include operating channels and/or frequencies of the HPR <NUM> on their respective blacklists (thus inhibiting operation of those devices on those operating channels).

Some embodiments determine, based on physical locations of wireless devices and signal strengths of the HPR <NUM> at those wireless devices to estimate a location of the HPR <NUM>. In some embodiments, triangulation is used by relating signal strength to distance between HPR and respective AP. The estimated location of the HPR <NUM> is then used to estimate signal strengths of HPR <NUM> signals at other wireless devices. These signal strengths are evaluated against a second criterion (e.g. second predetermined threshold). If the estimated signal strengths meet the second criterion (e.g. are greater than the second predetermined threshold), the HPR <NUM> operating channels are added to the wireless device's blacklist, thus inhibiting operation by the wireless device on those operating channels.

<FIG> is an example network graph <NUM> for a wireless network including a HPR <NUM>. The illustrated network includes nodes (e.g. APs) <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> respectively. The nodes use Wi-Fi channels {<NUM>, <NUM>, <NUM>, <NUM>, and <NUM>} respectively. HPR <NUM> operates on channel <NUM>. The HPR <NUM> is shown generating signals 562a-b.

In the embodiment illustrated by <FIG>, the nodes are oriented on a substantially straight line. Node <NUM> initially operates on the same channel as the HPR <NUM> (e.g. channel <NUM>). As such, the node <NUM> detects, in some embodiments, transmissions of the HPR. In response, node <NUM> switches to an alternate channel (e.g. channel <NUM>). Node <NUM> provides a notification message (not shown) to the network management system (e.g. NMS <NUM>) indicating the detection of HPR <NUM> transmissions on channel <NUM>.

As discussed above, the network management system may use a variety of techniques in determining which wireless devices should include channels and/or frequencies of the HPR <NUM> on their blacklist (e.g. inhibit use of these channels). For example, in embodiments that notify peer devices, the network management system notifies node <NUM> since it is a first level peer of the node <NUM>. Since node <NUM> is not notified to inhibit transmissions on channel <NUM>, node <NUM> may later detect transmissions by HPR <NUM> and provide a second notification to the network management system.

Alternatively, node <NUM> operates, in some embodiments, on channel <NUM>. The HPR <NUM> operates on both channels <NUM> and channel <NUM>. Thus, while operating on channel <NUM>, node <NUM> detects HPR transmissions and notifies the network management system. In this example embodiment, node <NUM> initiates a transition away from channel <NUM> to another channel. Channel <NUM> is included in a blacklist maintained by node <NUM>. In the future AP <NUM> may need to switch to another channel and selects channel <NUM>. Soon after the switch, in this example node <NUM> detects the operations of the HPR on channel <NUM>. AP C switches to another operating channel, marks the channel in his blacklist and notifies the network management.

When nodes are on a substantially straight line as illustrated in <FIG>, a direction and distance to the HPR <NUM> from the nodes can be determined based on estimated signal strength values of the HPR <NUM> at each of the nodes. If the estimated signal strength of the HPR <NUM> at node <NUM> and/or node <NUM> meets a criterion (e.g. smaller than a predetermined threshold), the operating frequency band of HPR <NUM> is not added to blacklists of nodes <NUM> and/or node <NUM> (at least in some embodiments).

<FIG> shows example message portions which are implemented in one or more of the disclosed embodiments. <FIG> shows a first message portion <NUM> a second message portion <NUM>, and a third message portion <NUM>. The first message portion <NUM> is included, in some embodiments, in a notification message which is transmitted by a wireless device (e.g. an AP) to a network management system (e.g. NMS <NUM>). The message portion <NUM> includes a wireless device identifier field <NUM>, a blacklist version field <NUM>, high priority receiver channel(s) field <NUM>, a signal strength field <NUM>, and a detection time field <NUM>. The wireless device identifier field <NUM> identifies a device sending the notification message. The device identified via field <NUM> is, in some embodiments, a device that detected a high priority receiver. In some embodiments, the field <NUM> stores a station address of the identified wireless device. The blacklist version field <NUM> indicates a blacklist version stored by the wireless device sending the message. The blacklist version field <NUM> identifies, in some embodiments, a version of blacklist data provided by an NMS to the wireless device sending the message portion <NUM>. This information is used, in some embodiments, by the NMS to determine whether to update the blacklist information of the wireless device. The high priority receiver channels field <NUM> identifies channels upon which the high priority receiver was detected to be transmitting on. The field <NUM> identifies specific frequency ranges (e.g. channels) of one or more channels in at least some aspects. The signal strength field <NUM> indicates signal strengths received from a transmitter associated with an HPR and detected on the channels identified via field <NUM>. In some embodiments, the signal strength field <NUM> represents signal strengths via received signal strength indication (RSSI) values. The detection time field <NUM> indicates a time when the detection occurred. One or more fields of the example message portion <NUM> are included in a notification message sent by a wireless device to a network management system (e.g. NMS <NUM>). In some embodiments, a wireless device is configured to send one or more fields of the message portion <NUM> upon detection of a transmitter associated with HPR.

Message portion <NUM> includes a wireless device identifier <NUM>, blacklist version field <NUM>, high priority receiver channels identified field <NUM>, a signal strength field <NUM>, a detection time field <NUM>, and a detecting device identifier field <NUM>. The wireless device identifier field <NUM> identifies a wireless device that is sending the message portion <NUM>. The blacklist version field <NUM> indicates a version number to associate with blacklist information provided in the message portion <NUM>. In some embodiments, the blacklist version field <NUM> is used to ensure wireless devices have the most up to date blacklist information from a NMS. For example, the wireless device provides, in some embodiments, the blacklist version information identifying a version of the blacklist maintained by the wireless device to a NMS. The NMS can then determine whether to update the wireless device with new blacklist information. The high priority receiver channels identified field <NUM> identifies channels upon which the HPR has been detected to operate. The signal strength field <NUM> identifies strengths of a signal received from a transmitter associated with an HPR and detected on the one or more channels indicated by field <NUM>. In some embodiments, the signal strength field <NUM> represents signal strengths via received signal strength indication (RSSI) values. The detection time field <NUM> indicates when operation of HPR on the identified channels (e.g. via field <NUM>) were detected. In some embodiments, an access point and/or NMS may delete a channel from a blacklist if the detection of operation of an HPR on a channel occurred more than a predetermined elapsed time prior to a current time. The detecting device identifier field <NUM> identifies a device that originally detected operation of an HPR on the channels identified via field <NUM>. In some embodiments, the message portion <NUM> is included in a message that is transmitted by a network management system (e.g. NMS <NUM>) to one or more wireless devices. The message portion <NUM> functions to notify receiving wireless devices of the presence of the identified HPR and that devices receiving the notification are to avoid operation on the channels identified via field <NUM> (at least until the time indicated by the expiration time field <NUM> in some embodiments).

Message portion <NUM> functions to provide signal strength measurement information to a network management system (e.g. NMS <NUM>) from a wireless device (e.g. any of the APs <NUM>, <NUM>, <NUM>, or <NUM> discussed above with respect to <FIG>). The message portion <NUM> includes a reporting wireless device identifier field <NUM>, and a number of strength measurements field <NUM>. The reporting wireless device identifier field <NUM> identifies a device generating the message portion <NUM>. The field <NUM> also identifies, in some embodiments, the device performing measurement of signal strengths reported by the message portion <NUM>. The number of strength measurements field <NUM> indicates a number of signal strength measurements conveyed by the message portion <NUM>. The signal strength measurements are conveyed via pairs of fields, as shown in <FIG>. These pairs may be repeated in the message portion <NUM> a number of times as indicated by the number of strength measurements field <NUM>. Each of the wireless device identifier fields <NUM><NUM>. <NUM>n identify a device from which a signal was generated, and was measured by the device identified via field <NUM>. Each of signal strength measurement fields <NUM><NUM>. <NUM>n identifies a signal strength measurement of the signal on the respective channel. In some embodiments, the signal strength field(s) <NUM><NUM>. n identify a received signal strength indication (RSSI). In some embodiments, one or more of the fields included in the message portion <NUM> are transmitted by a particular wireless device to a network management system (e.g. NMS <NUM>) to report strength of signals transmitted by other wireless devices and received by the particular wireless device.

<FIG> is an overview diagram showing example blacklists maintained by wireless devices in at least some of the disclosed embodiments. <FIG> shows two wireless devices 702a-b and a network management system <NUM>. Each of the wireless devices 702a-b maintains an AP blacklist <NUM> and an AP blacklist <NUM> respectively. Version identification <NUM> and <NUM> are maintained for each of the AP blacklist <NUM> and AP blacklist <NUM> respectively. Each of the AP blacklists <NUM> and the AP blacklist <NUM> are stored in data stores 704a and 704b respectively. In some embodiments, the network management system <NUM> also stores an NMS blacklist <NUM> in a data store 704c. Each of the AP blacklist <NUM> and AP blacklist <NUM> include at least, in some embodiments, channel information (e.g. channel information 706a, channel information 708a) and detection time information (e.g. detection time information 706b, and detection time information 708b). Each of the AP blacklist <NUM> and AP blacklist <NUM> also stores information identifying a device that detected an HPR operating on a channel identified by the AP blacklist (e.g. 706c and 708c).

The NMS blacklist <NUM> stores the blacklist version information <NUM> and information that allows it to customize a blacklist for each AP managed by the NMS <NUM>. Thus, in the illustrated embodiment, the NMS blacklist <NUM> includes channel information 710a, detection time information 710b of an HPR operating on channel(s) indicated by 710a, a device detecting the HPR operating on said channels 710c, signal strength (e.g. RSSI) of said signals at said device 710d, and an AP list 710e. The AP list 710e identifies zero or more access points that are instructed not to operate on the one or more channels indicated by channel information 710a. The detection time information 710b is used, in some embodiments, to remove prohibitions from operating on particular channels. For example, if no HPR is detected on a channel for more than a predetermined threshold period of time, APs may be notified that they are now permitted to attempt to operate on the channel. When data in the NMS blacklist <NUM> is updated, the NMS increments the blacklist version information <NUM>. The blacklist version information <NUM> is provided in messages transmitted to the APs 702a-b to provide an ability to synchronize blacklist information across the NMS and the APs.

In some embodiments, the network management system <NUM> sends messages to one or more of the wireless devices 702a-b to add or remove channels used by HPR from AP blacklist <NUM> and/or AP blacklist <NUM> respectively. For example, as discussed above, in some embodiments, the network management system <NUM> transmits one or more fields of the message portion <NUM> to one or more of the wireless devices 702a-b to add or remove HPR operating channels (e.g. via field <NUM>) to the wireless device's AP blacklist (e.g. <NUM> and/or <NUM>). The NMS blacklist <NUM> stores HPR information that has been collected and/or determined by the network management system <NUM>. In some embodiments, the network management system <NUM> is configured to transmit information derived from the NMS blacklist <NUM> to wireless devices under management by the network management system <NUM>.

<FIG> is a flowchart of an example process for managing transmission of a plurality of wireless devices so as to prevent interference with one or more high priority receivers. In some embodiments, one or more of the functions discussed below with respect to <FIG> are performed by hardware processing circuitry (e.g. <NUM>, <NUM>). In some aspects, instructions (e.g. <NUM>, <NUM>) stored in a memory (e.g. <NUM>, <NUM>) configure the hardware processing circuitry to perform one or more of the functions discussed below with respect to <FIG>. The process <NUM> is performed by the network management system <NUM>, discussed above with respect to <FIG>. In the discussion below, a device executing the process <NUM> is referred to as an "executing device.

After start operation <NUM>, the process <NUM> moves to operation <NUM>, where signal strength measurements are received from wireless devices. As discussed above, in some embodiments wireless devices on a wireless network, such as any of the APs <NUM>, <NUM>, <NUM>, or <NUM> discussed above with respect to <FIG> or the wireless device 702a and wireless device 702b discussed above with respect to <FIG> report signal strength measurements to a network management system (e.g. NMS <NUM>). In some embodiments, the wireless devices filter signal strength measurements such that only those signal strength measurements above a threshold are provided and thus received in operation <NUM>. In some embodiments, operation <NUM> includes receiving one or more of the message portion <NUM>, discussed above with respect to <FIG>. The message portions <NUM> convey the signal strength information by wireless devices to the executing device (e.g. a network management system such as NMS <NUM>).

In operation <NUM>, a network graph is constructed based on the signal strength measurements. As discussed above, the network graph is constructed, in some embodiments, to represent devices providing signal strength measurements as nodes in the graph, with the signal strength measurements represented as edges in the graph. Thus, if a first wireless device measured a signal from a second wireless device, an edge in the graph would connect a node representing the first wireless device to a second node representing the second wireless device. The signal strength would be stored in association with the edge. As discussed below, some embodiments use the network graph to determine which wireless devices are affected by high priority receivers. Some embodiments may not generate a network graph, but make a determination as to which wireless devices are affected by a high priority receiver using other types of data structures and/or processing methods.

Decision operation <NUM> determines whether a high priority receiver has been detected. For example, in some embodiments, decision operation <NUM> determines if a message similar to message portion <NUM>, discussed above with respect to <FIG>, is received. The message is received from a notifying device. Message portion <NUM> provides an example message which functions as a notification of detection of a transmitter associated with a high priority receiver. The notification can be received from a wireless device included in a wireless network, such as any of the APs <NUM>, <NUM>, <NUM>, or <NUM> discussed above with respect to <FIG> and/or any of the wireless device 702a or wireless device 702b discussed above with respect to <FIG>. The notification identifies a set of channels upon which operation of a high priority receiver device has been detected. The set of channels can indicate one or more channels. If no notification is received, the process <NUM> returns to operation <NUM>. Otherwise, if a notification has been received, the process <NUM> moves to operation <NUM> which determines which wireless devices are to be notified about the high priority receiver.

Operation <NUM> identifies a set of wireless devices utilizing a variety of methods in various embodiments. In some embodiments, operation <NUM> identifies all wireless devices being managed by the executing device. In non-claimed examples, operation <NUM> identifies all access points being managed by the executing device. For example, with respect to <FIG>, the network management server identifies each of the wireless device 702a and the wireless device 702b. With respect to <FIG>, the network management system <NUM> identifies each of APs <NUM>, <NUM>, <NUM>, or <NUM>.

In some other embodiments, operation <NUM> identifies peer devices of the detecting device from which the notification was received (the notifying device discussed above). Peer devices of a subject device are devices, in at least some embodiments directly connected by a single edge of the network graph to the subject device. In some embodiments, peer devices are connected to the subject device via a predetermined number of edges (which can be one, two, three, four, five, or more edges in various embodiments). These peer devices are then included in the set of wireless devices. As discussed above with respect to <FIG>, APs <NUM>, <NUM>, <NUM>, and <NUM> are peer devices of AP <NUM>, as these APs receive signals generated by the AP <NUM>, and/or AP <NUM> receives signals from APs <NUM>, <NUM>, <NUM>, and <NUM> (and/or those signals are above a threshold that qualifies the devices as peer devices). Note that since AP <NUM>, for example, is not connected via the network graph <NUM> of <FIG> with AP <NUM>, AP <NUM> is not a peer device of AP <NUM>. Similarly, since AP <NUM>, is not connected via the network graph <NUM> of <FIG> with AP <NUM>, AP <NUM>, or AP <NUM>, AP <NUM> is not a peer device of these APs. Some embodiments of operation <NUM> identify peer devices at a first, second, third, or fourth level. (e.g. peer devices of peer devices would be second level peer devices, etc.).

In the present claims, operation <NUM> identifies the set of wireless devices with estimated signal strength of HPR signals that meets a criterion e.g. being above a predetermined threshold. In some embodiments, this estimate is made by first determining an estimated geographic location of the HPR and then estimating its signal strength at locations of the wireless devices (e.g. the plurality of wireless devices providing signal strength measurement information in operation <NUM>). The geographic location of the HPR is determined, in some aspects, by triangulating signals received by the HPR across multiple wireless devices (e.g. signals received by the wireless device 702a and wireless device 702b that are generated by HPR <NUM> (e.g. signals 762a and 762b) are used to estimate a location of the HPR <NUM>).

Based on the estimated geographic location of the HPR, and, in some embodiments, the network graph generated in operation <NUM>, estimates of signal strength values of HPR signals at wireless devices included in the plurality of wireless devices are determined. If the estimated signal strength at a particular device is above a threshold or otherwise meets a criterion, that particular device is included in a subset of the plurality of wireless devices. The wireless devices included in the subset are then included in the identified set of wireless devices by operation <NUM>.

In some embodiments, wireless devices are included in the subset based on a geographic distance determined between a device detecting the HPR or an estimated position of the HPR and each of the respective devices. In these embodiments, wireless devices having a distance less than a predetermined threshold value from the detecting device and/or the HPR estimated location are identified, and the identified wireless devices are included in the set of wireless devices of operation <NUM>.

In some embodiments, a network graph is utilized to identify devices to notify. For example, the network graph is utilized, in some embodiments, to identify communication paths between devices having signal attenuation meeting a criterion. For example, in some embodiments, the criterion evaluates whether attenuation between the detecting device and a particular candidate device is smaller than a predetermined threshold. Candidate devices meeting the criterion are then notified in these embodiments. Thus wireless devices are included in the subset based on their respective attenuation with the detecting device. This identified subset of devices having attention meeting the criterion are then added to the set of wireless devices.

In operation <NUM>, instructions are sent to the set of wireless devices identified in operation <NUM>. The instructions generally indicate to wireless devices in the subset to avoid operation on any channels detected to be in use by the detected HPR. In some embodiments, the executing device transmits one or more fields of message portion <NUM> to each of the wireless devices included in the set of wireless devices in operation <NUM>. In some embodiments, operation <NUM> adds the channel information relating to the identified HPR to a NMS blacklist (e.g. <NUM>). The NMS blacklist is used, in some embodiments, to initialize AP blacklists (e.g. <NUM> and/or <NUM>) of other wireless devices. For example, if new wireless devices are added to the network, or an existing device is reinitialized, a network management system (e.g. NMS <NUM>) utilizes the NMS blacklist to initialize the local blacklist of the new or reset device.

<FIG> is a flowchart of an example process for avoiding interference with a high priority receiver. In some embodiments, the process <NUM> discussed below with respect to <FIG> is performed by a wireless device, such as any of the APs <NUM>, <NUM>, <NUM>, or <NUM> of <FIG> or the wireless device 702a and/or the wireless device 702b discussed above with respect to <FIG>. In some embodiments, instructions (e.g. routines <NUM>) stored in a memory (E. <NUM>) configure hardware processing circuitry (e.g. <NUM>) to perform one or more of the functions discussed below with respect to <FIG> and the process <NUM>. In the discussion below, a device performing the process <NUM> is referred to, in some cases, as the "executing device.

In some embodiments, one or more of the functions discussed below with respect to <FIG> are performed by hardware processing circuitry (e.g. <NUM>, <NUM>). In some aspects, instructions (e.g. <NUM>, <NUM>) stored in a memory (e.g. <NUM>, <NUM>) configure the hardware processing circuitry to perform one or more of the functions discussed below with respect to <FIG>. In some embodiments, the process <NUM> is performed by the network management system <NUM>, discussed above with respect to <FIG>. A device executing or performing the process <NUM> is referenced below as an "executing device.

Process <NUM> begins at start operation <NUM> and then moves to operation <NUM>. In operation <NUM> signal strength measurements of signals received by the executing device are performed. In some embodiments, the signal strength measurements are represented as received signal strength indications (RSSIs). The signals are generated by other wireless devices, such as neighboring APs or high priority receivers.

In operation <NUM>, the signal strength measurements are transmitted to a network management system (e.g. NMS <NUM>). For example, as discussed above with respect to <FIG>, some embodiments generate the message portion <NUM> to communicate signal strength measurements from a wireless device to a network management system.

In operation <NUM>, the executing device operates on a current channel. Operating on the current channel includes communicating with other devices (e.g. wireless terminals associated with the executing device) on the current channel. Decision operation <NUM> determines whether a transmitter associated with a high priority receiver has been detected. If no high priority receiver has been detected, process <NUM> moves to decision operation <NUM>. Decision operation <NUM> determines whether a notification has been received. The notification functions to notify the executing device of a channel that is conditionally subject to blacklisting. This channel is referred to as a notified channel. In some embodiments, the notification includes the message portion <NUM>. The notification is received, in some embodiments, from a network management system (e.g. NMS <NUM>). If no notification is received, process <NUM> returns to operation <NUM>. If a notification is received, process <NUM> moves from decision operation <NUM> to decision operation <NUM>, which determines if the executing device is currently operating on the notified channel included in the received notification. If the executing device is currently operating on the notified channel, some embodiments determine that continued operation on the notified channel is acceptable, since the AP has not detected operation of the HPR on the notified channel. Such implementations operate in a manner that preferences local determinations (e.g. by the executing device) of possible interference to determinations of possible interference by an NMS. If the executing device is not operating on the notified channel, process <NUM> moves from decision operation <NUM> to operation <NUM>, which adds the notified channel to the blacklist. After operation <NUM> completes, processing returns to operation <NUM>. If the executing device is operating on the notified channel, the notification is effectively ignored, and processing moves from decision operation <NUM> to operation <NUM>.

Returning to decision operation <NUM>, if a high priority receiver is identified, process <NUM> moves from decision operation <NUM> to operation <NUM>, which notifies a network management system of the detected HPR. In some embodiments, process <NUM> generates a message portion <NUM>, indicating parameters of the HPR. The message portion <NUM> is then transmitted to the network management system (e.g. NMS <NUM>). The process <NUM> then moves to operation <NUM> which includes the current channel on a blacklist. By adding the current channel to the blacklist, operation on the current channel is inhibited. Process <NUM> then moves to operation <NUM>, which switches operation of the executing device to a different channel. Processing then optionally returns to operation <NUM>.

In some embodiments of <FIG> and the process <NUM>, an AP can become constrained with respect to channels upon which it may operate. For example, in certain environments, an AP can be blacklisted from operating on a first set of channels where a HPR has been determined to be operating. HPR operation on this first set of channels is detected by the AP itself. The AP can be further blacklisted from operating on a second set of channels. HPR operation on this second set of channels is detected by other wireless devices, such as other access points. The AP was notified of this second set of blacklisted channels via an NMS, at least in some embodiments. Thus, the AP's operational environment is constrained. In some cases, these constraints may inhibit a reasonable level of performance by the AP. For example, in some operational environments, none of the available channels, that are not in the blacklist, have sufficient quality to enable nominal operation. Thus, there is an absence of available channels sufficient to maintain nominal operation.

In an attempt to maintain nominal operation is such an environment, APs are configured, in some embodiments, to attempt operation on a channel identified in the blacklist. In some embodiments, communication is attempted first on any blacklisted channels communicated to the wireless device by the NMS. For those channels, an HPR was most likely detected via a different AP, and not the AP attempting the communication. Thus, there is a higher likelihood that the AP can operate successfully on the blacklisted channel due to inefficiencies in the blacklisting algorithms that determine which AP should be blacklisted from which channels. If none of the NMS identified channels can be used (e.g. after attempting communication, HPR communication prohibiting operation is detected), some of the AP's are configured to then attempt communication on channels previously blacklisted by the AP itself.

The techniques of various embodiments may be implemented using software, hardware and/or a combination of software and hardware. Various embodiments are directed to apparatus, e.g., management entities, e.g., a network monitoring node, routers, gateways, switches, APs, DHCP servers, DNS servers, AAA servers, user equipment devices, e.g., wireless nodes such as mobile wireless terminals, base stations, communications networks, and communications systems. Various embodiments are also directed to methods, e.g., method of controlling and/or operating a communications device or devices, e.g., a network management node, an AP, wireless terminals (UEs), base stations, control nodes, DHCP nodes, DNS servers, AAA nodes, Mobility Management Entities (MMEs), networks, and/or communications systems. Various embodiments are also directed to machine, e.g., computer, readable medium, e.g., ROM, RAM, CDs, hard discs, etc., which include machine readable instructions for controlling a machine to implement one or more steps of a method.

It is understood that the specific order or hierarchy of steps in the processes disclosed is an example of approaches that may be used in one or more of the disclosed embodiments. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged as long as it remains within the scope of the invention as defined by the claims. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

In various embodiments devices and nodes described herein are implemented using one or more modules to perform the steps corresponding to one or more methods, for example, signal generation, transmitting, processing, analyzing, and/or receiving steps. Thus, in some embodiments various features are implemented using modules. Such modules may be implemented using software, hardware or a combination of software and hardware. In some embodiments each module is implemented as an individual circuit with the device or system including a separate circuit for implementing the function corresponding to each described module. Many of the above described methods or method steps can be implemented using machine executable instructions, such as software, included in a machine readable medium such as a memory device, e.g., RAM, floppy disk, etc. to control a machine, e.g., general purpose computer with or without additional hardware, to implement all or portions of the above described methods, e.g., in one or more nodes. Accordingly, among other things, various embodiments are directed to a machine-readable medium e.g., a computer readable medium, including machine executable instructions for causing a machine, e.g., processor and associated hardware, to perform one or more of the steps of the above-described method(s). Some embodiments are directed to a device including a processor configured to implement one, multiple or all of the operations of the disclosed embodiments.

In some embodiments, the processor or processors, e.g., CPUs, of one or more devices, e.g., communications devices such as routers, switches, network attached servers, network management nodes, wireless terminals (UEs), and/or access nodes, are configured to perform the steps of the methods described as being performed by the devices. The configuration of the processor may be achieved by using one or more modules, e.g., software modules, to control processor configuration and/or by including hardware in the processor, e.g., hardware modules, to perform the recited steps and/or control processor configuration. Accordingly, some but not all embodiments are directed to a communications device, e.g., user equipment, with a processor which includes a module corresponding to each of the steps of the various described methods performed by the device in which the processor is included. In some but not all embodiments a communications device includes a module corresponding to each of the steps of the various described methods performed by the device in which the processor is included. The modules may be implemented purely in hardware, e.g., as circuits, or may be implemented using software and/or hardware or a combination of software and hardware.

Some embodiments are directed to a computer program product comprising a computer-readable medium comprising code for causing a computer, or multiple computers, to implement various functions, steps, acts and/or operations, e.g. one or more steps described above. Depending on the embodiment, the computer program product can, and sometimes does, include different code for each step to be performed. Thus, the computer program product may, and sometimes does, include code for each individual step of a method, e.g., a method of operating a communications device, e.g., a network management node, an AP, a base station, a wireless terminal or node. The code may be in the form of machine, e.g., computer, executable instructions stored on a computer-readable medium such as a RAM (Random Access Memory), ROM (Read Only Memory) or other type of storage device. In addition to being directed to a computer program product, some embodiments are directed to a processor configured to implement one or more of the various functions, steps, acts and/or operations of one or more methods described above. Accordingly, some embodiments are directed to a processor, e.g., CPU, configured to implement some or all of the steps of the methods described herein. The processor may be for use in, e.g., a communications device or other device described in the present application. Additionally or alternatively a computer-readable medium can include transient media such as carrier signals and transmission media.

While described in the context of a communications system including wired, optical, cellular, Wi-Fi, Bluetooth and BLE, at least some of the methods and apparatus of various embodiments are applicable to a wide range of communications systems including IP and non IP based, OFDM and non-OFDM and/or non-cellular systems.

Numerous additional variations on the methods and apparatus of the various embodiments described above will be apparent to those skilled in the art in view of the above description. Such variations are to be considered within the scope. The methods and apparatus may be, and in various embodiments are, used with IP based and non-IP, wired and wireless such CDMA, orthogonal frequency division multiplexing (OFDM), Wi-Fi, Bluetooth, BLE, optical and/or various other types of communications techniques which may be used to provide communications links between network attached or associated devices or other devices including receiver/transmitter circuits and logic and/or routines, for implementing the methods.

Claim 1:
A method (<NUM>), the method being performed by a network management system (<NUM>) and comprising:
receiving (<NUM>), signal strength measurements of signals reported by a plurality of access points (<NUM>, <NUM>, <NUM>, <NUM>) of a wireless network;
receiving, from an access point of the plurality of access points, a notification of a detection of a high priority receiver, HPR, (<NUM>) the notification indicating a channel on which the HPR was detected;
determining (<NUM>), based on the signal strength measurements and the notification, a set of access points of the plurality of access points,
wherein determining the set of access points comprises estimating, based on the signal strength measurements, a signal strength of the HPR at each access point in the plurality of access points, identifying a subset of the plurality of access points having an estimated signal strength of the HPR that meets a criterion, and including the identified subset of access points into the set of access points; and
transmitting (<NUM>), to the set of access points, instructions to avoid operation on the channel.