The present invention relates to wireless networks and more specifically to systems and methods for selecting available channels free of occupying signals from a plurality of radio frequency channels. Embodiments of the present invention provide methods and systems for exploiting licensed and unlicensed bands requiring radar detection and detection of other occupying signals, such as the Dynamic Frequency Selection (DFS) channels in the Unlicensed National Information Infrastructure (U-NII) bands, to enable additional bandwidth for 802.11 ac/n and LTE in unlicensed spectrum (LTE-U) networks employing a wireless agility agent.
Wi-Fi networks are crucial to today's portable modern life. Wi-Fi is the preferred network in the growing Internet-of-Things (IoT). But, the technology behind current Wi-Fi has changed little in the last ten years. The Wi-Fi network and the associated unlicensed spectrum are currently managed in inefficient ways. For example, there is little or no coordination between individual networks and equipment from different manufacturers. Such networks generally employ primitive control algorithms that assume the network consists of “self-managed islands,” a concept originally intended for low density and low traffic environments. The situation is far worse for home networks, which are assembled in completely chaotic ad hoc ways. Further, with more and more connected devices becoming commonplace, the net result is growing congestion and slowed networks with unreliable connections.
Similarly, LTE-U networks operating in the same or similar unlicensed bands as 802.11ac/n Wi-Fi suffer similar congestion and unreliable connection issues and will often create congestion problems for existing Wi-Fi networks sharing the same channels. Additional bandwidth and better and more efficient utilization of spectrum is key to sustaining the usefulness of wireless networks including the Wi-Fi and LTE-U networks in a fast growing connected world.
Devices operating in certain parts of the 5 GHz U-NII-2 band, known as the DFS channels, require active radar detection. This function is assigned to a device capable of detecting radar known as a DFS master, which is typically an access point or router. The DFS master actively scans the DFS channels and performs a channel availability check (CAC) and periodic in-service monitoring (ISM) after the channel availability check. The channel availability check lasts 60 seconds as required by the FCC Part 15 Subpart E and ETSI 301 893 standards. The DFS master signals to the other devices in the network (typically client devices) by transmitting a DFS beacon indicating that the channel is clear of radar. Although the access point can detect radar, wireless clients typically cannot. Because of this, wireless clients must first passively scan DFS channels to detect whether a beacon is present on that particular channel. During a passive scan, the client device switches through channels and listens for a beacon transmitted at regular intervals by the access point on an available channel.
Once a beacon is detected, the client is allowed to actively scan on that channel. If the DFS master detects radar in that channel, the DFS master no longer transmits the beacon, and all client devices upon not sensing the beacon within a prescribed time must vacate the channel immediately and remain off that channel for 30 minutes. For clients associated with the DFS master network, additional information in the beacons (i.e. the channel switch announcement) can trigger a rapid and controlled evacuation of the channel. Normally, a DFS master device is an access point with only one radio and is able to provide DFS master services for just a single channel. A significant problem of this approach is, in the event of a radar event or a more-common false-detect, the single channel must be vacated and the ability to use DFS channels is lost. This disclosure recognizes and addresses, in at least certain embodiments, the problems with current devices for detecting occupying signals including current DFS devices.
The present invention relates to wireless networks and more specifically to systems and methods for selecting available channels free of occupying signals from a plurality of radio frequency channels. The present invention employs a wireless agility agent to access additional bandwidth for wireless networks, such as IEEE 802.11ac/n and LTE-U networks. The additional bandwidth is derived from channels that require avoidance of channels with occupying signals. For example, additional bandwidth is derived from special compliance channels that require radar detection, such as the DFS channels of the U-NII-2 bands, by employing multi-channel radar detection and in-service monitoring, and active channel selection controls.
In an embodiment, the present invention utilizes an agility agent employing proprietary embedded radio techniques including continuous multi-carrier spectrum monitoring, an embedded computation element employing proprietary real-time spectrum analysis algorithms, and proprietary signaling and control protocols to provide detection and continuous real-time monitoring of multiple radar types and patterns, and other signals such as interferers and measures of congestion and traffic, across simultaneous multiple channels.
The present invention may also utilize a cloud-based computation and control element, which together with the wireless agility agent forms a split-intelligence architecture. In this architecture, the embedded sensor information from the agility agent—such as radar detection channel availability check and in-service monitoring together with measurements of interference, traffic, identification of neighboring devices, and other spectrum and location information—is communicated to and integrated over time within the cloud intelligence engine. Also the embedded sensor information from the agility agent may be fused with spectrum information from other agility agents distributed in space, filtered, and post-processed. The embedded sensor information from the agility agent may further be merged with other data from other sources to provide improvements to fundamental signal measurement and network reliability problems such as augmented radar sensitivity, reduced false-detect rates, and reliable discovery of hidden nodes.
Other embodiments and various examples, scenarios and implementations are described in more detail below. The following description and the drawings set forth certain illustrative embodiments of the specification. These embodiments are indicative, however, of but a few of the various ways in which the principles of the specification may be employed. Other advantages and novel features of the embodiments described will become apparent from the following detailed description of the specification when considered in conjunction with the drawings.
The aforementioned objects and advantages of the present invention, as well as additional objects and advantages thereof, will be more fully understood herein after as a result of a detailed description of a preferred embodiment when taken in conjunction with the following drawings in which:
The present invention relates to wireless networks and more specifically to systems and methods for selecting available channels free of occupying signals from a plurality of radio frequency channels. As used herein, a channel “free” of occupying signals may include a channel with occupying signals that are lower than a signal threshold including signal strength, quantity, or traffic. The present invention employs a wireless agility agent to access additional bandwidth for wireless networks, such as IEEE 802.11ac/n and LTE-U networks. The additional bandwidth is derived from channels that require avoidance of occupying signals. For example, additional bandwidth is derived from special compliance channels that require radar detection—such as the DFS channels of the U-NII-2 bands—by employing multi-channel radar detection and in-service monitoring, and active channel selection controls. The DFS master actively scans the DFS channels and performs a channel availability check and periodic in-service monitoring after the channel availability check.
When used in an 802.11ac/n or LTE-U wireless network, the agility agent of the present invention functions as an autonomous DFS master device. In contrast to conventional DFS master devices, the agility agent is not an access point or router, but rather is a standalone wireless device employing inventive scanning techniques described herein that provide DFS scan capabilities across multiple channels, enabling one or more access point devices and peer-to-peer client devices to exploit simultaneous multiple DFS channels. The standalone autonomous DFS master of the present invention may be incorporated into another device such as an access point, LTE-U host, base station, cell, or small cell, media or content streamer, speaker, television, mobile phone, mobile router, software access point device, or peer to peer device but does not itself provide network access to client devices. In particular, in the event of a radar event or a false-detect, the enabled access point and clients or wireless device are able to move automatically, predictively and very quickly to another DFS channel.
The host access point 218 and any other access point devices 223 under control of the autonomous DFS master 200 typically have the control agent portion 219, 224 installed within their communication stack. The control agent 219, 224 is an agent that acts under the direction of the agility agent 200 to receive information and commands from the agility agent 200. The control agent 219, 224 acts on information from the agility agent 200. For example, the control agent 219, 224 listens for information like a whitelist or blacklist from the agility agent. If a radar signal is detected by the agility agent 200, the agility agent 200 communicates that to the control agent 219, 224, and the control agent 219, 224 acts to evacuate the channel immediately. The control agent can also take commands from the agility agent 200. For example, the host access point 218 and network access point 223 can offload DFS monitoring to the agility agent 200 as long as they can listen to the agility agent 200 and take commands from the agility agent regarding available DFS channels.
The host access point 218 is connected to a wide area network 233 and includes an access point control agent 219 to facilitate communications with the agility agent 200. The access point control agent 219 includes a security module 220 and agent protocols 221 to facilitate communication with the agility agent 200, and swarm communication protocols 222 to facilitate communications between agility agents, access points, client devices, and other devices in the network. The agility agent 200 connects to the cloud intelligence engine 235 via the host access point 218 and the wide area network 233. The access point sets up a secure tunnel to communicate with the cloud intelligence engine 235 through, for example, an encrypted control API in the host access point 218. The agility agent 200 transmits information to the cloud intelligence engine 235 such as whitelists, blacklists, state information, location information, time signals, scan lists (for example, showing neighboring access points), congestion (for example, number and type of re-try packets), and traffic information. The cloud intelligence engine 235 communicates information to the agility agent 200 via the secure communications tunnel such as access point location (including neighboring access points), access point/cluster current state and history, statistics (including traffic, congestion, and throughput), whitelists, blacklists, authentication information, associated client information, and regional and regulatory information. The agility agent 200 uses the information from the cloud intelligence engine 235 to control the access points and other network devices.
The agility agent 200 may communicate via wired connections or wirelessly with the other network components. In the illustrated example, the agility agent 200 includes a primary radio 215 and a secondary radio 216. The primary radio 215 is for DFS and radar detection and is typically a 5 GHz radio. The agility agent 200 may receive radar signals, traffic information, and/or congestion information through the primary radio 215. And the agility agent 200 may transmit information such as DFS beacons via the primary radio 215. The second radio 216 is a secondary radio for sending control signals to other devices in the network and is typically a 2.4 GHz radio. The agility agent 200 may receive information such as network traffic, congestion, and/or control signals with the secondary radio 216. And the agility agent 200 may transmit information such as control signals with the secondary radio 216. The primary radio 215 is connected to a fast channel switching generator 217 that includes a switch and allows the primary radio 215 to switch rapidly between a radar detector 211 and beacon generator 212. The channel switching generator 217 allows the radar detector 211 to switch sufficiently fast to appear to be on multiple channels at a time.
In one embodiment, a standalone multi-channel DFS master includes a beacon generator 212 to generate a beacon in each of a plurality of 5 GHz radio channels, a radar detector 211 to scan for a radar signal in each of the plurality of 5 GHz radio channels, a 5 GHz radio transceiver 215 to transmit the beacon in each of the plurality of 5 GHz radio channels and to receive the radar signal in each of the plurality of 5 GHz radio channels, and a fast channel switching generator 217 coupled to the radar detector, the beacon generator, and the 5 GHz radio transceiver. The fast channel switching generator 217 switches the 5 GHz radio to a first channel of the plurality of 5 GHz radio channels and then causes the beacon generator 212 to generate the beacon in the first channel of the plurality of 5 GHz radio channels. Then the fast channel switching generator 217 causes the radar detector 211 to scan for the radar signal in the first channel of the plurality of 5 GHz radio channels. The fast channel switching generator 217 then repeats these steps for each other channel of the plurality of 5 GHz radio channels during a beacon transmission duty cycle and, in some examples, during a radar detection duty cycle. The beacon transmission duty cycle is the time between successive beacon transmissions on a given channel and the radar detection duty cycle which is the time between successive scans on a given channel. Because the agility agent 200 cycles between beaconing and scanning in each of the plurality of 5 GHz radio channels in the time window between a first beaconing and scanning in a given channel and a subsequent beaconing and scanning the same channel, it can provide effectively simultaneous beaconing and scanning for multiple channels.
The agility agent 200 also may contain a Bluetooth radio 214 and an 802.15.4 radio 213 for communicating with other devices in the network. The agility agent 200 may include various radio protocols 208 to facilitate communication via the included radio devices.
The agility agent 200 may also include a location module 209 to geolocate or otherwise determine the location of the agility agent 200. As shown in
As shown in
The cloud intelligence engine 235 includes a database 248 and memory 249 for storing information from the agility agent 200, other agility agents (not shown) connected to the intelligence engine 235, and external data sources (not shown). The database 248 and memory 249 allow the cloud intelligence engine 235 to store information over months and years received from agility agents and external data sources.
The cloud intelligence engine 235 also includes processors 250 to perform the cloud intelligence operations described herein. The roaming and guest agents manager 238 in the cloud intelligence engine 235 provides optimized connection information for devices connected to agility agents that are roaming from one access point to other or from one access point to another network. The roaming and guest agents manager 238 also manages guest connections to networks for agility agents connected to the cloud intelligence engine 235. The external data fusion engine 239 provides for integration and fusion of information from agility agents with information from external data sources for example GIS information, other geographical information, FCC information regarding the location of radar transmitters, FCC blacklist information, NOAA databases, DOD information regarding radar transmitters, and DOD requests to avoid transmission in DFS channels for a given location. The cloud intelligence engine 235 further includes an authentication interface 240 for authentication of received communications and for authenticating devices and users. The radar detection compute engine 241 aggregates radar information from agility agents and external data sources and computes the location of radar transmitters from those data to, among other things, facilitate identification of false positive radar detections or hidden nodes and hidden radar. The radar detection compute engine 241 may also guide or steer multiple agility agents to dynamically adapt detection parameters and/or methods to further improve detection sensitivity. The location compute and agents manager 242 determines the location the agility agent 200 and other connected devices through Wi-Fi lookup in a Wi-Fi location database, querying passing devices, scan lists from agility agents, or geometric inference.
The spectrum analysis and data fusion engine 243 and the network optimization self organization engine 244 facilitate dynamic spectrum optimization with information from the agility agents and external data sources. Each of the agility agents connected to the cloud intelligence engine 235 have scanned and analyzed the local spectrum and communicated that information to the cloud intelligence engine 235. The cloud intelligence engine 235 also knows the location of each agility agent and the access points proximate to the agility agents that do not have a controlling agent as well as the channel on which each of those devices is operating. With this information, the spectrum analysis and data fusion engine 243 and the network optimization self-organization engine 244 can optimize the local spectrum by telling agility agents to avoid channels subject to interference. The swarm communications manager 245 manages communications between agility agents, access points, client devices, and other devices in the network. The cloud intelligence engine includes a security manager 246. The control agents manager 247 manages all connected control agents.
Independent of a host access point 218, the agility agent 200, in the role of an autonomous DFS master device, may also provide the channel indication and channel selection control to one or more peer-to-peer client devices 231, 232 within the coverage area by (a) signaling availability of one or more DFS channels by simultaneous transmission of one or more beacon signals; (b) transmitting a listing of both the authorized available DFS channels, herein referred to as a whitelist and the prohibited DFS channels in which a potential radar signal has been detected, herein referred to as a blacklist along with control signals and a time-stamp signal, herein referred to as a dead-man switch timer via an associated non-DFS channel; and (c) receiving control, coordination and authorized and preferred channel selection guidance information from the cloud intelligence engine 235. The agility agent 200 sends the time-stamp signal, or dead-man switch timer, with communications to ensure that the devices do not use the information, including the whitelist, beyond the useful lifetime of the information. For example, a whitelist will only be valid for certain period of time. The time-stamp signal avoids using noncompliant DFS channels by ensuring that a device will not use the whitelist beyond its useful lifetime.
Such peer-to-peer devices may have a user control interface 228. The user control interface 228 includes a user interface 229 to allow the client devices 231, 232 to interact with the agility agent 200 via the cloud intelligence engine 235. For example, the user interface 229 allows the user to modify network settings via the agility agent 200 including granting and revoking network access. The user control interface 228 also includes a security element 230 to ensure that communications between the client devices 231, 232 and the agility agent 200 are secure. The client devices 231, 232 are connected to a wide area network 234 via a cellular network for example. Peer-to-peer wireless networks are used for direct communication between devices without an access point. For example, video cameras may connect directly to a computer to download video or images files using a peer-to-peer network. Also, device connections to external monitors and device connections to drones currently use peer-to-peer networks. Because there is no access point in a peer-to-peer network, traditional peer-to-peer networks cannot use the DFS channels because there is no access point to control the DFS channel selection and tell the devices what DFS channels to use. The present invention overcomes this limitation.
The agility agent may operate in multiple modes executing a number of DFS scan methods employing different algorithms. Two of these methods are illustrated in
At the first scan after startup or reset, if a radar pattern is detected in the first channel scanned, the DFS master may repeat the above steps until a channel free of radar signals is found. Alternatively, after a startup or reset, the DFS master may be provided a whitelist indicating one or more channels that have been determined to be free of radar signals. For example, the DFS master may receive a message that channel 52 is free of radar signals from the cloud intelligence engine 235 along with information fused from other sources.
If at step 406 the DFS master does not detect a radar pattern 410, the DFS master marks this channel in the whitelist and switches the embedded radio to transmit (Tx) (not shown in
For the next channel scan after the DFS master finds a channel free of radar, the DFS master sets the radio to receive and tunes the radio to the next DFS channel 404 (for example channel 60). The DFS master then performs a non-continuous CAC radar detection scan 405 for period of X, which is the maximum period between beacons allowable for a client device to remain associated with a network (PM) less a period of n required for a quick radar scan and the transmission of the beacon itself (X=PM−n) 408. At 411, the DFS master saves the state of current non-continuous channel state (SC) from the non-continuous CAC scan so that the DFS master can later resume the current non-continuous channel scan at the point where the DFS master left off. Then, at step 412, the DFS master switches the radio to transmit and tunes to the first DFS channel (in this example it was CH 52), performs quick receive radar scan 413 (for a period of D called the dwell time) to detect radar 414. If a radar pattern is detected, the DFS master marks the channel to the blacklist 418. When marking the channel to the blacklist, the DFS master may also include additional information about the detected radar pattern including signal strength, type of radar, and a time stamp for the detection. If no radar pattern is detected, the DFS master transmits again 415 the DFS master beacon for the first channel (channel 52 in the example). Next, the DFS master determines if the current channel (CB) is the last channel in the whitelist (WL) 416. In the current example, the current channel, channel 52, is the only channel in the whitelist at this point. Then, the DFS master restores 417 the channel to the saved state from step 411 and switches the radio back to receive mode and tunes the radio back to the current non-continuous CAC DFS channel (channel 60 in the example) 404. The DFS master then resumes the non-continuous CAC radar scan 405 for period of X, again accommodating the period of n required for the quick scan and transmission of the beacon. This is repeated until 60 seconds of non-continuous CAC scanning is accumulated 409—in which case the channel is marked in the whitelist 410—or until a radar pattern is detected—in which case this channel is marked in the blacklist 407.
Next, the DFS master repeats the procedure in the preceding paragraph for the next DFS channel (for example channel 100). The DFS master periodically switches 412 to previous whitelisted DFS channels to do a quick scan 413 (for a period of D called the dwell time), and if no radar pattern detected, transmits a beacon 415 for period of n in each of the previously CAC scanned and whitelisted DFS channels. Then the DFS master returns 404 to resume the non-continuous CAC scan 405 of the current CAC channel (in this case CH 100). The period X available for non-continuous CAC scanning before switching to transmit and sequentially beaconing the previously whitelisted CAC scanned channels is reduced by n for each of the previously whitelisted CAC scanned channels, roughly X=PM−n*(WL) where WL is the number of previously whitelisted CAC scanned channels. This is repeated until 60 seconds of non-continuous CAC scanning is accumulated for the current channel 409. If no radar pattern is detected the channel is marked in the whitelist 410. If a radar pattern is detected, the channel is marked in the blacklist 407 and the radio can immediately switch to the next DFS channel to be CAC scanned.
The steps in the preceding paragraph are repeated for each new DFS channel until all desired channels in the DFS band have been CAC scanned. In
During the ISM phase, the DFS master does not scan the channels in the blacklist 421. The DFS master switches 422 to the first channel in the whitelist and transmits 423 a DFS beacon on that channel. Then the DFS master scans 424 the first channel in the whitelist for a period of DISM (the ISM dwell time) 425, which may be roughly PM (the maximum period between beacons allowable for a client device to remain associated with a network) minus n times the number of whitelisted channels, divided by the number of whitelisted channels (DISM=(PM−n*WL)/n). Then the DFS master transmits 423 a beacon and scans 424 each of the channels in the whitelist for the dwell time and then repeats starting at the first channel in the whitelist 422 in a round robin fashion for each respective channel. If a radar pattern is detected 426, the DFS master beacon for the respective channel is stopped 427, and the channel is marked in the blacklist 428 and removed from the whitelist (and no longer ISM scanned). The DFS master sends alert messages 429, along with the new whitelist and blacklist to the cloud intelligence engine. Alert messages may also be sent to other access points and/or client devices in the network.
If the DFS master does not detect radar patterns, it marks this channel in the whitelist 509. The DFS master determines if the current channel C is the last channel to be CAC scanned R at step 510. If not, then the DFS master tunes the receiver to the next DFS channel (for example channel 60) 504. Then the DFS master performs a continuous scan 505 for full period of 60 seconds 507. If a radar pattern is detected, the DFS master marks the channel in the blacklist 508 and the radio can immediately switch to the next DFS channel 504 and repeat the steps after step 504.
If no radar pattern is detected 509, the DFS master marks the channel in the whitelist 509 and then tunes the receiver next DFS channel 504 and repeats the subsequent steps until all DFS channels for which a CAC scan is desired. Unlike the method depicted in
The ISM phase 502 in
In the ISM phase 601, the DFS master switches to the first channel in the whitelist. In the example in
One embodiment of the present invention provides a standalone multi-channel DFS master that includes a beacon generator 212 to generate a beacon in each of a plurality of 5 GHz radio channels, a radar detector 211 to scan for a radar signal in each of the plurality of 5 GHz radio channels, a 5 GHz radio transceiver 215 to transmit the beacon in each of the plurality of 5 GHz radio channels and to receive the radar signal in each of the plurality of 5 GHz radio channels, and a fast channel switching generator 217 and embedded processor 203 coupled to the radar detector, the beacon generator, and the 5 GHz radio transceiver. The fast channel switching generator 217 and embedded processor 203 switch the 5 GHz radio transceiver 215 to a first channel of the plurality of 5 GHz radio channels and cause the beacon generator 212 to generate the beacon in the first channel of the plurality of 5 GHz radio channels. The fast channel switching generator 217 and embedded processor 203 also cause the radar detector 211 to scan for the radar signal in the first channel of the plurality of 5 GHz radio channels. The fast channel switching generator 217 and embedded processor 203 then repeat these steps for each of the other channels of the plurality of 5 GHz radio channels. The fast channel switching generator 217 and embedded processor 203 perform all of the steps for all of the plurality of 5 GHz radio channels during a beacon transmission duty cycle which is a time between successive beacon transmissions on a specific channel and, in some embodiments, a radar detection duty cycle which is a time between successive scans on the specific channel.
In the embodiment illustrated in
The agility agent 700 may operate in the 5 GHz band and the plurality of radio frequency channels may be in the 5 GHz band and the occupying signals are radar signals. The host device 701 may be a Wi-Fi access point or an LTE-U host device.
Further, the agility agent 700 may also be programmed to transmit the indication of the available channels by simultaneously transmitting multiple beacon signals. And the agility agent 700 may be programmed to transmit the indication of the available channels by transmitting a channel whitelist of the available channels and to transmit the indication of the unavailable channels by transmitting a channel blacklist of the unavailable channels. In addition to saving the channel in the channel blacklist, the agility agent 700 may also be programmed to determine and save in the channel blacklist information about the detected occupying signals including signal strength, traffic, and type of the occupying signals.
As shown in
In another embodiment shown in
The in-service monitoring and beaconing 1250 for each of the plurality of radio frequency channels includes determining if the one of the plurality of radio frequency channels is in the channel whitelist and if so, tuning the embedded radio receiver in the autonomous frequency selection master device to the one of the plurality of radio frequency channels and transmitting a beacon in the one of the plurality of radio frequency channels with an embedded radio transmitter in the autonomous frequency selection master device 1251. Next, the in-service monitoring and beaconing 1250 includes initiating a discrete channel availability scan (a quick scan as described previously) in the one of the plurality of radio frequency channels with the embedded radio receiver 1252. Next, the in-service monitoring and beaconing 1250 includes determining if the occupying signal is present in the one of the plurality of radio frequency channels during the discrete channel availability scan 1253. If the occupying signal is present, the in-service monitoring and beaconing 1250 includes stopping transmission of the beacon, removing the one of the plurality of radio frequency channels from the channel whitelist, adding the one of the plurality of radio frequency channels to the channel blacklist, and ending the discrete channel availability scan 1254. If the occupying signal is not present in the one of the plurality of radio frequency channels during the discrete channel availability scan for a second scan period, the in-service monitoring and beaconing 1250 includes ending the discrete channel availability scan 1255. Thereafter, the in-service monitoring and beaconing 1250 includes repeating steps 1251, 1252, and 1253 as well as either 1254 or 1255 for each of the plurality of radio frequency channels.
In the present specification, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. Moreover, articles “a” and “an” as used in this specification and annexed drawings should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.
In addition, the terms “example” and “such as” are utilized herein to mean serving as an instance or illustration. Any embodiment or design described herein as an “example” or referred to in connection with a “such as” clause is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the terms “example” or “such as” is intended to present concepts in a concrete fashion. The terms “first,” “second,” “third,” and so forth, as used in the claims and description, unless otherwise clear by context, is for clarity only and does not necessarily indicate or imply any order in time.
What has been described above includes examples of one or more embodiments of the disclosure. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing these examples, and it can be recognized that many further combinations and permutations of the present embodiments are possible. Accordingly, the embodiments disclosed and/or claimed herein are intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the detailed description and the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.
This application claims priority to U.S. patent application Ser. No. 14/920,568 titled METHOD AND APPARATUS FOR USE OF SIMULTANEOUS MULTIPLE CHANNELS IN THE DYNAMIC FREQUENCY SELECTION BAND IN WIRELESS NETWORKS and filed on Oct. 22, 2015 which claims priority to U.S. Provisional Patent Application No. 62/200,764 titled METHOD AND APPARATUS FOR USE OF SIMULTANEOUS MULTIPLE CHANNELS IN THE DYNAMIC FREQUENCY SELECTION BAND IN WIRELESS NETWORKS and filed on Aug. 4, 2015, the disclosures of which is hereby incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
5978669 | Sanmugam | Nov 1999 | A |
6181952 | Murata | Jan 2001 | B1 |
6870815 | McFarland et al. | Mar 2005 | B2 |
6882851 | Sugar | Apr 2005 | B2 |
7457628 | Blumberg et al. | Nov 2008 | B2 |
7548750 | Kruys et al. | Jun 2009 | B2 |
7606193 | McFarland et al. | Oct 2009 | B2 |
7813744 | Johnson | Oct 2010 | B2 |
8213942 | Likar et al. | Jul 2012 | B2 |
8239337 | Madani | Aug 2012 | B2 |
8260357 | Likar et al. | Sep 2012 | B2 |
8472334 | Likar et al. | Jun 2013 | B2 |
8483059 | Likar et al. | Jul 2013 | B2 |
8565106 | Likar et al. | Oct 2013 | B2 |
8654782 | Meil et al. | Feb 2014 | B2 |
8699341 | Likar et al. | Apr 2014 | B2 |
8867490 | Krishna et al. | Oct 2014 | B1 |
8879996 | Kenney et al. | Nov 2014 | B2 |
8885511 | Likar et al. | Nov 2014 | B2 |
9060289 | Chandrasekhar et al. | Jun 2015 | B2 |
9066251 | Madan et al. | Jun 2015 | B2 |
9131391 | Madan et al. | Sep 2015 | B2 |
9131392 | Madan et al. | Sep 2015 | B2 |
9131504 | Kenney et al. | Sep 2015 | B2 |
9307413 | Lenzini et al. | Apr 2016 | B2 |
9363743 | Xue et al. | Jun 2016 | B2 |
9439197 | Ngo et al. | Sep 2016 | B1 |
9622089 | Ngo et al. | Apr 2017 | B1 |
9699786 | Ngo et al. | Jul 2017 | B2 |
9807625 | Ngo et al. | Oct 2017 | B2 |
9832791 | Ngo et al. | Nov 2017 | B2 |
9999055 | Ngo et al. | Jun 2018 | B2 |
10104665 | Ngo et al. | Oct 2018 | B2 |
20020116380 | Chen et al. | Aug 2002 | A1 |
20030107512 | McFarland | Jun 2003 | A1 |
20030181213 | Sugar et al. | Sep 2003 | A1 |
20040033789 | Tsien | Feb 2004 | A1 |
20040146022 | Lewis | Jul 2004 | A1 |
20040151137 | McFarland et al. | Aug 2004 | A1 |
20040156336 | McFarland et al. | Aug 2004 | A1 |
20040242188 | Uchida et al. | Dec 2004 | A1 |
20050059364 | Hansen et al. | Mar 2005 | A1 |
20050192016 | Zimmermann | Sep 2005 | A1 |
20050215266 | Tsien | Sep 2005 | A1 |
20050272435 | Tsien et al. | Dec 2005 | A1 |
20060082489 | Liu | Apr 2006 | A1 |
20060189311 | Cromer | Aug 2006 | A1 |
20070060065 | Kruys | Mar 2007 | A1 |
20070126622 | Nallapureddy | Jun 2007 | A1 |
20080016556 | Selignan | Jan 2008 | A1 |
20080049918 | Heinze et al. | Feb 2008 | A1 |
20080075038 | Jin | Mar 2008 | A1 |
20080089280 | Hu | Apr 2008 | A1 |
20090077620 | Ravi et al. | Mar 2009 | A1 |
20090116411 | Castagnoli et al. | May 2009 | A1 |
20090146866 | Matsumoto et al. | Jun 2009 | A1 |
20090160696 | Pare et al. | Jun 2009 | A1 |
20090201851 | Kruys et al. | Aug 2009 | A1 |
20100061289 | Mun et al. | Mar 2010 | A1 |
20100216480 | Park et al. | Aug 2010 | A1 |
20100271948 | Challapali et al. | Oct 2010 | A1 |
20100302966 | Matsuura | Dec 2010 | A1 |
20110126110 | Vilke et al. | May 2011 | A1 |
20120039265 | Patel et al. | Feb 2012 | A1 |
20120258749 | Lenzini et al. | Oct 2012 | A1 |
20120300759 | Patanapongpibul et al. | Nov 2012 | A1 |
20130072106 | Koskela | Mar 2013 | A1 |
20130171941 | Kenney | Jul 2013 | A1 |
20130201928 | Kim et al. | Aug 2013 | A1 |
20130252640 | Kenney et al. | Sep 2013 | A1 |
20130314267 | Kenney et al. | Nov 2013 | A1 |
20140036691 | Madan et al. | Feb 2014 | A1 |
20140059218 | Ganu et al. | Feb 2014 | A1 |
20140171060 | Cook et al. | Jun 2014 | A1 |
20140220964 | Kurucz, Jr. et al. | Aug 2014 | A1 |
20140241226 | Jia et al. | Aug 2014 | A1 |
20140253361 | Rezk et al. | Sep 2014 | A1 |
20140301328 | Yacovitch | Oct 2014 | A1 |
20140328286 | Crowle et al. | Nov 2014 | A1 |
20140349669 | Qi et al. | Nov 2014 | A1 |
20140362782 | Yuk et al. | Dec 2014 | A1 |
20150023271 | Nakano | Jan 2015 | A1 |
20150063321 | Sadek et al. | Mar 2015 | A1 |
20150177720 | Anderson et al. | Jun 2015 | A1 |
20150189528 | Carbajal | Jul 2015 | A1 |
20150208330 | Park et al. | Jul 2015 | A1 |
20150256323 | Gandarillas et al. | Sep 2015 | A1 |
20150263886 | Wang et al. | Sep 2015 | A1 |
20150271829 | Amini et al. | Sep 2015 | A1 |
20160014613 | Ponnampalam et al. | Jan 2016 | A1 |
20160044673 | Liu et al. | Feb 2016 | A1 |
20160095108 | Ryoo et al. | Mar 2016 | A1 |
20160157168 | Xue et al. | Jun 2016 | A1 |
20160249357 | Green et al. | Aug 2016 | A1 |
20160261657 | Bruhn et al. | Sep 2016 | A1 |
20160285611 | Fischer et al. | Sep 2016 | A1 |
20160345323 | Krishnamoorthy et al. | Nov 2016 | A1 |
20170026845 | Garg | Jan 2017 | A1 |
20170034707 | Green et al. | Feb 2017 | A1 |
20170041949 | Ngo et al. | Feb 2017 | A1 |
20170041954 | Tsai et al. | Feb 2017 | A1 |
20170048728 | Ngo et al. | Feb 2017 | A1 |
20170048864 | Ngo et al. | Feb 2017 | A1 |
20170063665 | Casebolt et al. | Mar 2017 | A1 |
20170079007 | Carbajal | Mar 2017 | A1 |
20170123049 | Tsai et al. | May 2017 | A1 |
20170142728 | Tsai et al. | May 2017 | A1 |
20170156113 | Visuri et al. | Jun 2017 | A1 |
20170188293 | Mizusawa | Jun 2017 | A1 |
20170273084 | Yi et al. | Sep 2017 | A1 |
20170290075 | Carbajal et al. | Oct 2017 | A1 |
20180020453 | Lin et al. | Jan 2018 | A1 |
20180059213 | Wallstedt et al. | Mar 2018 | A1 |
20180070253 | Kleinbeck et al. | Mar 2018 | A1 |
20180234974 | Ngo et al. | Aug 2018 | A1 |
Number | Date | Country |
---|---|---|
2512169 | Oct 2012 | EP |
1925108 | Mar 2014 | EP |
3128779 | Feb 2017 | EP |
2004-535095 | Nov 2004 | JP |
2005-523616 | Aug 2005 | JP |
2012-120033 | Jun 2012 | JP |
2007032790 | Mar 2007 | WO |
2007032790 | Apr 2009 | WO |
20140176503 | Oct 2014 | WO |
2014190004 | Nov 2014 | WO |
Entry |
---|
Office Action for Japanese Application No. 2016-153596 dated Dec. 12, 2017, 7 pages. |
Office Action for U.S. Appl. No. 15/225,966 dated Nov. 7, 2017, 26 pages. |
Office Action for U.S. Appl. No. 15/259,386 dated Dec. 18, 2017, 41 pages. |
Office Action for U.S. Appl. No. 15/416,568 dated Nov. 17, 2017, 39 pages. |
Notice of Allowance for U.S. Appl. No. 15/225,966 dated Jan. 19, 2018, 32 pages. |
Office Action for U.S. Appl. No. 15/711,649 dated Jan. 26, 2018, 28 pages. |
Japanese Office Action for Japanese Patent Application No. 2016-142261 dated Jan. 16, 2018, 6 pages (with translation). |
Notice of Allowance dated Jul. 3, 2017 for U.S. Appl. No. 15/263,985, 28 pages. |
Office Action for U.S. Appl. No. 14/920,568, dated Mar. 29, 2016, 29 pages. |
Office Action for U.S. Appl. No. 15/085,573, dated Jun. 24, 2016, 15 pages. |
Notice of Allowance dated Jul. 19, 2016 for U.S. Appl. No. 15/085,573, 27 pages. |
Office Action for U.S. Appl. No. 14/920,568, dated Sep. 30, 2016, 28 pages. |
Extended European Search Report for EP Patent Application Serial No. 16182722.5, dated Dec. 15, 2016, 11 pages. |
Kerry et al., “Liaison Statement on the Compatibility Between IEEE 802.11a and Radars in the Radiolocation and Radionavigation Service in the 5250-5350 MHz and 5470-5725 MHz bands”, Jan. 2001, IEEE, 6 pages. |
Extended European Search Report for EP Patent Application Serial No. 16182672.2, dated Dec. 16, 2016, 8 pages. |
Office Action for U.S. Appl. No. 15/214,437 dated Jan. 23, 2017, 33 pages. |
Office Action for U.S. Appl. No. 14/920,568, dated Jan. 20, 2017, 26 pages. |
Extended European Search Report for EP Patent Application Serial No. 16187611.5, dated Jan. 30, 2017, 8 pages. |
Office Action for U.S. Appl. No. 15/259,386, dated Jan. 9, 2017, 37 Pages. |
Office Action for U.S. Appl. No. 15/171,911, dated Feb. 28, 2017, 34 Pages. |
Office Action for U.S. Appl. No. 15/263,985, dated Mar. 7, 2017, 33 Pages. |
Notice of Allowance dated Apr. 12, 2017 for U.S. Appl. No. 15/171,911, 30 pages. |
European Office Action dated Feb. 13, 2017 for European Application Serial No. 16182722.5, 2 pages. |
Office Action for U.S. Appl. No. 15/428,658, dated May 10, 2017, 20 pages. |
Office Action for U.S. Appl. No. 15/416,568. dated May 18, 2017, 39 pages. |
Extended European Search Report for EP Patent Application 16200660.5, dated May 8, 2017, 6 pages. |
Office Action for U.S. Appl. No. 15/454,805 dated May 11, 2017, 22 pages. |
Office Action for U.S. Appl. No. 14/920,568 dated Jun. 16, 2017, 51 pages. |
Office Action for U.S. Appl. No. 15/225,966 dated Jul. 7, 2017, 37 pages. |
Office Action for U.S. Appl. No. 15/259,386 dated Jul. 6, 2017, 43 pages. |
Office Action for U.S. Appl. No. 15/588,474 dated Jul. 11, 2017, 21 pages. |
Office Action for U.S. Appl. No. 15/483,406 dated Aug. 4, 2017, 29 pages. |
European Search Report for European Application Serial No. 17163289.6 dated Jul. 12, 2017, 11 pages. |
Holma et al., “LTE for UMTS. Evolution to LTE-advanced, ” Mar. 4, 2011, pp. 26-29, XP055386245. |
Office Action for U.S. Appl. No. 15/450,940 dated Aug. 10, 2017, 28 pages. |
Notice of Allowance for U.S. Appl. No. 14/920,568 dated Sep. 25, 2017, 27 pages. |
Office Action for U.S. Appl. No. 15/613,726 dated Oct. 13, 2017, 28 pages. |
European Office Action dated Oct. 9, 2017 for European Application Serial No. 17163289.6, 2 pages. |
Notice of Allowance for U.S. Appl. No. 15/483,406 dated Nov. 7, 2017, 29 pages. |
Notice of Allowance for U.S. Appl. No. 15/454,805 dated Aug. 16, 2017, 38 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/259,359, dated Apr. 17, 2018, 58 pages. |
Notice of Allowance received for U.S. Appl. No. 15/259,359, dated Jun. 13, 2018, 25 Pages. |
Final Office Action received for U.S. Appl. No. 15/711,649, dated Jun. 22, 2018, 30 Pages. |
Decision to Grant a Patent received for Japanese Patent Application Serial No. 2016-153596, dated Mar. 27, 2018, 6 pages. |
Communication pursuant to Rules 70(2) and 70a(2) EPC and reference to Rule 39(1) EPC for European Application Serial No. 16182672.2, dated Feb. 20, 2017, 2 pages. |
Communication pursuant to Rules 70(2) and 70a(2) EPC and reference to Rule 39(1) EPC for European Application Serial No. 16187611.5 dated Mar. 13, 2017, 2 pages. |
Communication pursuant to Rules 70(2) and 70a(2) EPC and reference to Rule 39(1) EPC for European Application Serial No. 16200660.5 dated Jun. 12, 2017, 2 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/715,239, dated Nov. 30, 2017, 20 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/416,568, dated Jun. 29, 2018, 43 pages. |
Notice of Allowance for U.S. Appl. No. 15/711,649 dated Mar. 7, 2019, 30 pages. |
Notice of Allowance for U.S. Appl. No. 15/368,462 dated Mar. 13, 2019, 36 pages. |
Indian Office Action for Indian Application Serial No. 201614040060 dated Oct. 11, 2018, 5 pages. |
Decision to Grant a Patent received for Japanese Patent Application Serial No. 2016-142261 dated Sep. 18, 2018, 6 pages (including English translation). |
European Office Action for European Application Serial No. 17163289.6 dated Sep. 12, 2018, 7 pages. |
Non-Final Office Action for U.S. Appl. No. 15/711,649, dated Oct. 16, 2018, 26 pages. |
Notice of Allowance for U.S. Appl. No. 15/950,689, dated Feb. 13, 2019, 31 pages. |
Office Action for U.S. Appl. No. 16/130,423 dated Mar. 5, 2019, 39 pages. |
Office Action for U.S. Appl. No. 15/259,386 dated Mar. 21, 2019, 39 pages. |
Notice of Allowance for U.S. Appl. No. 15/711,649 dated Mar. 7, 2013, 30 pages. |
Notice of Allowance for U.S. Appl. No. 15/368,462 dated Mar. 13, 2013, 36 pages. |
Office Action dated Aug. 3, 2018 for U.S. Appl. No. 15/259,386, 44 pages. |
Office Action dated Aug. 1, 2018 for U.S. Appl. No. 15/368,462, 64 pages. |
Office Action received for U.S. Appl. No. 15/950,689, dated Aug. 1, 2018, 35 pages. |
Office Action received for U.S. Appl. No. 15/214,431, dated Aug. 10, 2018, 60 pages. |
Office Action for U.S. Appl. No. 15/713,099 dated Sep. 6, 2018, 45 pages. |
Number | Date | Country | |
---|---|---|---|
20180035457 A1 | Feb 2018 | US |
Number | Date | Country | |
---|---|---|---|
62200764 | Aug 2015 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14920568 | Oct 2015 | US |
Child | 15729900 | US |