Patent Description:
Under provisions of <NUM> U. § <NUM>(e), Applicant claims the benefit of <CIT>.

The present disclosure relates generally to wireless access points.

In computer networking, a wireless Access Point (AP) is a networking hardware device that allows a Wi-Fi compliant client device to connect to a wired network and to communicate with other client devices directly over Wi-Fi. The AP usually connects to a router (directly or indirectly via a wired network) as a standalone device, but it can also be an integral component of the router itself. Several APs may also work in coordination, either through direct wired or wireless connections, or through a central system, commonly called a Wireless Local Area Network (WLAN) controller. An AP is differentiated from a hotspot, which is the physical location where Wi-Fi access to a WLAN is available.

Prior to wireless networks, setting up a computer network in a business, home, or school often required running many cables through walls and ceilings in order to deliver network access to all of the network-enabled devices in the building. With the creation of the wireless AP, network users are able to add devices that access the network with few or no cables. An AP normally connects directly to a wired Ethernet connection and the AP then provides wireless connections using radio frequency links for other devices to utilize that wired connection. Most APs support the connection of multiple wireless devices to one wired connection. APs are built to support a standard for sending and receiving data using these radio frequencies. <CIT> discloses that if a radar signal is detected in a non-primary portion of the occupied bandwidth in <NUM> mode, the transmitter devolves to a <NUM>-in-<NUM> transmission scheme using <NUM> packets in the <NUM> bandwidth primary portion or devolves to a <NUM>-in-<NUM> transmission scheme using <NUM> packets in the <NUM> bandwidth primary portion or devolves to a <NUM> in <NUM> transmission scheme using <NUM> packets within primary channel <NUM>.

The document Tcb Workshop: "U-NII Guidance Updates",, <NUM> November <NUM> discloses that IEEE <NUM>. 11ax defines support of preamble puncture; <NUM> or <NUM> channels are notched in <NUM> portions when radar is detected. Test labs should verify that emissions from non-punctured sub-channels into punctured sub-channels are no worse than existing U-NII operations on adjacent channels.

The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the following description to refer to the same or similar elements. While embodiments of the disclosure may be described, modifications, adaptations, and other implementations are possible. For example, substitutions, additions, or modifications may be made to the elements illustrated in the drawings, and the methods described herein may be modified by substituting, reordering, or adding stages to the disclosed methods. Accordingly, the following detailed description does not limit the disclosure. Instead, the proper scope of the disclosure is defined by the appended claims.

When APs (e.g., <NUM> APs) operating in Dynamic Frequency Selection (DFS) channels detect the presence of radar on their operating channel, they may take one of two approaches. The first approach may be to switch to a different channel (e.g., possibly non-DFS). The second approach may be to lower the Basic Service Set (BSS) bandwidth to avoid the radar if the radar was detected on a non-primary channel. While compliant with the regulations, these approaches may suffer from inefficiency in spectrum utilization if the original bandwidth of operation is large. For example, if the original bandwidth of operation is <NUM>, switching to a different channel may lose the entire <NUM>, and lowering the bandwidth may lose between <NUM> and <NUM> of the spectrum, while in both cases less than <NUM> may be affected by the radar.

Some standards (e.g., <NUM>. 11ax) may support a puncturing process in which certain subcarriers in the operating bandwidth may be muted. For example, an AP may announce a BSS-wide mandate to mute these subcarriers. This process may address the DFS issue, but only when all client devices in a BSS support the puncturing feature. However, legacy clients may not support the puncturing feature. Furthermore, standards may not take into account a client device's filtering qualities on the punctured subcarriers or actual regulatory requirements or interpretations. A client device's poor filtering may result in the violation of regulations if radar is present.

To address the aforementioned issues, embodiments of the disclosure may provide multiple processes by which an AP may utilize puncturing to avoid collision with a detected radar in a large bandwidth. For example, embodiments of the disclosure may: i) classify the filtering quality of client devices using puncturing; and ii) maintain service for client devices that do not support puncturing, while still utilizing the available bandwidth to the advantage of client devices that do support puncturing.

<FIG> shows an operating environment <NUM>. As shown in <FIG>, operating environment <NUM> may comprise an Access Point (AP) <NUM>, a micro cell <NUM>, and a plurality of client devices <NUM>. AP <NUM> may provide wireless network access for plurality of client devices <NUM> and micro cell <NUM> may illustrate the coverage area of AP <NUM>. Plurality of client devices <NUM> may comprise a first client device <NUM>, a second client device <NUM>, a third client device <NUM>, a fourth client device <NUM>, and a fifth client device <NUM>. Each one of plurality of client devices <NUM> may comprise, but is not limited to, a smart phone, a personal computer, a tablet device, a mobile device, a cable modem, a cellular base station, a telephone, a remote control device, a set-top box, a digital video recorder, an Internet-of Things (IoT) device, a network computer, a mainframe, a router, or other similar microcomputer-based device.

As stated above, some standards may include a puncturing process in which certain subcarriers in the bandwidth may be muted. With the puncturing process, an AP may announce this set of subcarriers for the BSS. This puncturing process may allow the client devices that support puncturing to utilize the entire bandwidth minus the radar subchannel that the radar was detected on, however legacy client devices may not support puncturing. Accordingly, embodiments of the disclosure may: i) classify client devices to determine eligibility for puncturing; and ii) maintain service for all client devices in a BSS (e.g., those that may be capable and eligible for puncturing and those that may not be). Embodiments of the disclosure may provide at least two embodiments, one embodiment that may require modification to standard (e.g., <NUM>) specifications (i.e., new client-supported protocol) and one embodiment that may be free from specification dependence (i.e., in practice, minimal additional client support).

The elements described above of operating environment <NUM> (e.g., AP <NUM>, first client device <NUM>, second client device <NUM>, third client device <NUM>, fourth client device <NUM>, and fifth client device <NUM>) may be practiced in hardware and/or in software (including firmware, resident software, micro-code, etc.) or in any other circuits or systems. The elements of operating environment <NUM> may be practiced in electrical circuits comprising discrete electronic elements, packaged or integrated electronic chips containing logic gates, a circuit utilizing a microprocessor, or on a single chip containing electronic elements or microprocessors. Furthermore, the elements of operating environment <NUM> may also be practiced using other technologies capable of performing logical operations such as, for example, AND, OR, and NOT, including but not limited to, mechanical, optical, fluidic, and quantum technologies. As described in greater detail below with respect to <FIG>, the elements of operating environment <NUM> may be practiced in a computing device <NUM>.

<FIG> is a flow chart setting forth the general stages involved in a method <NUM> consistent with an embodiment of the disclosure for bypassing radar in wide Dynamic Frequency Selection (DFS) channels utilizing puncturing. Method <NUM> may be implemented using AP <NUM> as described in more detail above with respect to <FIG>. Ways to implement the stages of method <NUM> will be described in greater detail below.

Method <NUM> may begin at starting block <NUM> and proceed to stage <NUM> where AP <NUM> may classify first client device <NUM> as eligible for puncturing and second client device <NUM> as not eligible for puncturing. Information reported by plurality of client devices <NUM> Power Spectral Density (PSD) information) or information obtained by Over-the-Air (OTA) tests of plurality of client devices <NUM> (embodiment not falling under the scope of protection of the present claims) is used to determine which of plurality of client devices <NUM> is classified as eligible for puncturing and which is classified as not eligible for puncturing. Consistent with embodiments of the disclosure, eligible for puncturing may include both capable of puncturing and proving a Tx Mask when punctured that provides sufficient isolation at the occupied frequency of the radar for example.

Standards may provide a requirement for client device puncturing quality that may not be enough when applied to the DFS scenario in specific regulatory domains. Therefore, AP <NUM> may need to have additional information about the quality of a client device's filtering over the muted subcarriers, such as depth and width, before classifying a client device as eligible for puncturing. When radar is detected by AP <NUM>, a decision may be made based on the radar signal's center frequency and bandwidth for example. Power spectral densities of the client devices may be taken into account along with the radar signal's center frequency and bandwidth for example. If the radar signal falls close to the edge and into an unacceptable level of power leakage from the client device's output spectrum, then the client device may not be considered eligible for puncturing. As will be described in greater detail below, information about a client device's filtering quality may be obtained by AP <NUM> via at least two routes: i) declared by the client device; or ii) measured by AP <NUM>.

With respect to information about a client device's filtering quality being declared by the client device, embodiments of the disclosure may provide an information element that may be added to the standard specification and reported during association with AP <NUM>. This allows client devices to provide information (e.g., PSD information) that describes the quality of filtering possible on their transmit chains when a subchannel is punctured. This information is used by AP <NUM> to determine if any client device in plurality of client devices <NUM> is capable of utilizing the puncturing feature for the given radar.

The protocol for providing this information may range in complexity. For example, a client device may indicate to AP <NUM> yes or no that it supports enough suppression in the muted subcarriers that it can operate in any regulatory domain. In other embodiments, a client device's puncturing performance may be described and reported to AP <NUM> by different classes. For example, the classes may map <NUM>:<NUM> to different regulatory domains. Client devices may indicate the most difficult class that they support (if sortable) and/or a bitmap of which classes they support, which may work for all cases. In yet other embodiments, the client devices may report to AP <NUM> a single transition bandwidth (e.g., in MHz) and depth (e.g., in dB) tuple indicating how deep and sharp it may make its puncturing. Furthermore, since the null may be curved, the client device may report multiple tuples to more fully identify the shape of the puncturing. In other embodiments, AP <NUM> may interrogate the client devices. For example, AP <NUM> may indicate a desired puncturing depth, and the client device may indicate the transition bandwidth (or start and stop frequencies) of the edge of its puncturing. Vice versa, AP <NUM> may indicate the bandwidth of the radar and the client device may indicate the puncturing depth that it can achieve throughout the bandwidth of interest.

Embodiments not falling under the scope of protection of the present claims may, as an alternative to client devices advertising (i.e., reporting) their information (e.g., PSD information), AP <NUM> may perform Over-the-Air (OTA) tests to determine the filtering quality of plurality of client devices <NUM>. In contrast to the aforementioned reporting process, the OTA testing process may not require standards changes. This OTA testing may be performed, for example, by assigning Uplink (UL) Orthogonal Frequency Division Multiple Access (OFDMA) subcarriers to a client device that include a gap, mimicking puncturing on a detected radar subchannel. By measuring the difference in energy between the client device's assigned subchannels (specified by the UL OFDMA subcarriers) and the nulled subchannels, AP <NUM> may infer the client device's filtering quality. AP <NUM> may also inspect the level of a client device's sidelobes of a transmission of contiguous subcarriers.

The client device's sidelobe level may depend on bandwidth, Modulation and Coding Scheme (MCS), and specified power. AP <NUM> may test the client device's PSD in the worst case or in a range of cases to determine its characteristics.

After this measurement, the client devices may be pre-classified and pre-negotiated into groups based on their filtering quality. As will be described in greater detail below, once radar is detected on a channel, broadcast or multicast messages may be transmitted notifying each class of their required action. Client devices' understanding of the group announcement mechanism may require standards support, which may be avoided by sending unicast (extended) channel switch announcement frames.

From stage <NUM>, where access point <NUM> classifies first client device <NUM> as eligible for puncturing and second client device <NUM> as not eligible for puncturing, method <NUM> may advance to stage <NUM> where access point <NUM> may determine that a subchannel in a bandwidth range should not be used. For example, <FIG> illustrates a channel <NUM> that has a bandwidth range Y. Y may comprise, but is not limited to <NUM>. Channel <NUM> may be divided into a plurality of subchannels. These subchannels may comprise a first subchannel <NUM>, a second subchannel <NUM>, a third subchannel <NUM>, and a fourth subchannel <NUM>. Channel <NUM> may be divided into any number of subchannels and is not limited to four. The subchannels shown in <FIG> may have a bandwidth of X. X may comprise, but is not limited to <NUM>. Consistent with embodiments of the disclosure, AP <NUM> may detect radar in fourth subchannel <NUM> and as a result may determine that fourth subchannel <NUM> should not be used.

After access point <NUM> determines that the subchannel (e.g., fourth subchannel <NUM>) in the bandwidth range should not be used in stage <NUM>, method <NUM> may proceed to stage <NUM> where AP <NUM> may steer, in response to determining that the subchannel in the bandwidth range should not be used, first client device <NUM> to a first subset of the bandwidth range and second client device <NUM> to a second subset of the bandwidth range. The second subset of the bandwidth range may be smaller than the first subset of the bandwidth range. For example, once client devices are classified, they may be invited to use different channel bandwidths depending on their capability and eligibility for puncturing.

As stated above, AP <NUM> may detect radar in fourth subchannel <NUM> and, as a result, may determine that fourth subchannel <NUM> should not be used. Due to the previous classification of first client device <NUM> as being eligible for puncturing and after determining that first client device <NUM> has the ability to perform quality filtering of fourth subchannel <NUM> (i.e., can filter the needed transition bandwidth and depth), AP <NUM> may steer first client device <NUM> to the first subset of the bandwidth range. For example, the first subset of the bandwidth range may comprise first subchannel <NUM>, second subchannel <NUM>, and third subchannel <NUM>. While in this example the first subset of the bandwidth range may comprise contiguous subchannels (i.e., first subchannel <NUM>, second subchannel <NUM>, and third subchannel <NUM>), embodiments of the disclosure are not limited to contiguous subchannels, and noncontiguous subchannels may be used in the first subset of the bandwidth range consistent with other example embodiments of the disclosure.

Similarly, due to the previous classification of second client device <NUM> as not being eligible for puncturing and after determining that second client device <NUM> does not have the ability to perform quality filtering of fourth subchannel <NUM> (i.e., may not filter the needed transition bandwidth and depth) or may not be capable of puncturing at all, AP <NUM> may steer second client device <NUM> to the second subset of the bandwidth range. For example, the second subset of the bandwidth range may comprise first subchannel <NUM> and second subchannel <NUM>. In the case of insufficient filtering quality, client device <NUM> may not be able to filter out fourth subchannel <NUM> to a high enough degree while maintaining the required transmission quality on the other three subchannels. In the case of lack of puncturing support, client device <NUM> may be relegated to standards defined channel configurations (e.g., <NUM>, which supports <NUM> and <NUM> channel configurations but not <NUM>). Accordingly in both cases, AP <NUM> may steer second client device <NUM> to the second subset of the bandwidth range having just first subchannel <NUM> and second subchannel <NUM>. In this example, the first subset of the bandwidth range may comprise <NUM> and the second subset of the bandwidth range may comprise <NUM>. While in this example the second subset of the bandwidth range may comprise contiguous subchannels (i.e., first subchannel <NUM> and second subchannel <NUM>), embodiments of the disclosure are not limited to contiguous subchannels, and noncontiguous subchannels may be used in the second subset of the bandwidth range consistent with other example embodiments of the disclosure.

Described below are embodiments of the disclosure for steering the client devices to their respective bandwidths, some of which may require additions to the standard specifications, and some of which may use current protocol fields. Standard specification support may be needed for capability-based and eligibility-based bandwidth announcements.

With respect to capability-based bandwidth announcements, when the AP advertises a lower bandwidth for legacy clients and clients that do not support puncturing (e.g., via the High Throughput (HT)/Very High Throughput (VHT) operation elements), AP <NUM> may also announce a new information element that includes a larger bandwidth and a puncturing indication (e.g., bitmap, or start and stop frequencies, etc.) specifically for client devices that support puncturing. In other embodiments, the element may specify a minimum filtering requirement that would make a client device eligible for using the larger bandwidth. In yet other embodiments, the element may specify the pre-negotiated classifications that are eligible for the larger bandwidth. This element may be announced in beacons and may be used in conjunction with the element that advertises the subcarriers that are to be punctured in the BSS.

With respect to client-specific bandwidth announcements, new information elements may be set by AP <NUM>, taking into account each client device's eligibility based on the filtering quality and the radar signal's center frequency and bandwidth for example.

New elements in, for example, the groupcast Channel-Switch Announcements (CSA) and/or Extended CSA (ECSA) frames may allow AP <NUM> to announce changes in bandwidths that are dependent on either client device capabilities in puncturing, minimum filtering requirements, or client device classification in filtering quality. This may allow client devices to be notified of the upcoming punctured or non-punctured bandwidth (depending on client devices' puncturing eligibility) prior to the channel switch. In other embodiments, AP <NUM> may send each CSA or ECSA frame in a unicast manner or some hybrid of both unicast and groupcast.

Described below are embodiments of the disclosure for steering the client devices to their respective bandwidths that may not require standards support, in contrast to capability-based or eligibility-based bandwidth announcements. In some embodiments, AP <NUM> may announce a reduced bandwidth for the BSS to serve the clients that are not eligible for puncturing, and may reserve a new Basic Service Set Identifier (BSSID) to serve the clients that are eligible for puncturing. The new BSSID may utilize the entire original bandwidth (i.e., the bandwidth prior to the puncturing determination), may announce puncturing for the radar detected subchannel (e.g., fourth subchannel <NUM>), and may advertise the original Service Set Identifier (SSID) (i.e., the same SSID that the original BSSID uses). This new BSSID may be on the same radio as the original BSSID or on a different radio. Steering may comprise inviting the client devices that are eligible for puncturing to the new BSSID (e.g., using methods such as <NUM>. 11v BSS Transition). In other embodiments, the new BSSID may serve the client devices that are not eligible for puncturing and the client devices that are eligible for puncturing may be left on the old BSSID.

Once access point <NUM> steers first client device <NUM> to the first subset of the bandwidth range and second client device <NUM> to the second subset of the bandwidth range in stage <NUM>, method <NUM> may then end at stage <NUM>.

<FIG> shows computing device <NUM>. As shown in <FIG>, computing device <NUM> may include a processing unit <NUM> and a memory unit <NUM>. Memory unit <NUM> may include a software module <NUM> and a database <NUM>. While executing on processing unit <NUM>, software module <NUM> may perform, for example, processes for bypassing radar in wide Dynamic Frequency Selection (DFS) channels utilizing puncturing as described above with respect to <FIG>. Computing device <NUM>, for example, may provide an operating environment for AP <NUM>, first client device <NUM>, second client device <NUM>, third client device <NUM>, fourth client device <NUM>, or fifth client device <NUM>. AP <NUM>, first client device <NUM>, second client device <NUM>, third client device <NUM>, fourth client device <NUM>, and fifth client device <NUM> may operate in other environments and are not limited to computing device <NUM>.

Computing device <NUM> may be implemented using a Wi-Fi access point, a cellular base station, a tablet device, a mobile device, a smart phone, a telephone, a remote control device, a set-top box, a digital video recorder, a cable modem, a personal computer, a network computer, a mainframe, a router, a switch, a server cluster, a smart TV-like device, a network storage device, a network relay devices, or other similar microcomputer-based device. Computing device <NUM> may comprise any computer operating environment, such as hand-held devices, multiprocessor systems, microprocessor-based or programmable sender electronic devices, minicomputers, mainframe computers, and the like. Computing device <NUM> may also be practiced in distributed computing environments where tasks are performed by remote processing devices. The aforementioned systems and devices are examples and computing device <NUM> may comprise other systems or devices.

Embodiments of the disclosure, for example, may be implemented as a computer process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media. The computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process. The computer program product may also be a propagated signal on a carrier readable by a computing system and encoding a computer program of instructions for executing a computer process. Accordingly, the present disclosure may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.). In other words, embodiments of the present disclosure may take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system. A computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

Embodiments of the disclosure may be practiced via a system-on-a-chip (SOC) where each or many of the element illustrated in <FIG> may be integrated onto a single integrated circuit. Such an SOC device may include one or more processing units, graphics units, communications units, system virtualization units and various application functionality all of which may be integrated (or "burned") onto the chip substrate as a single integrated circuit. When operating via an SOC, the functionality described herein with respect to embodiments of the disclosure, may be performed via application-specific logic integrated with other components of computing device <NUM> on the single integrated circuit (chip).

Claim 1:
A method comprising:
classifying a first client device as eligible for puncturing, in which certain subcarriers in an operating bandwidth may be muted, and a second client device as not eligible for puncturing;
determining that a subchannel in a bandwidth range should not be used; and
steering, in response to determining that the subchannel in the bandwidth range should not be used, the first client device to a first subset of the bandwidth range and the second client device to a second subset of the bandwidth range, wherein the second subset of the bandwidth range is smaller than the first subset of the bandwidth range, wherein classifying the first client device as eligible for puncturing comprises:
receiving Power Spectral Density, PSD, information from the first client device, the PSD information describing a quality of filtering the first client device is capable of when the subchannel is punctured; and
determining that the first client device is eligible for puncturing based on the PSD information.