GPS-assisted cooperative signaling-assisted WLAN DFS operation
By leveraging databases and beaconing devices, WLAN devices can efficiently select DFS channels with reduced radar interference, addressing detection inaccuracies and regulatory compliance issues, ensuring uninterrupted operation.
Patent Information
- Application Number
- JP2021554998
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-03-12
- Filing Date
- 2020-01-16
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2040-01-16
AI Technical Summary
WLAN devices operating in DFS channels face challenges in accurately detecting radar signals due to vehicle movement, leading to unreliable operations and network outages, and regulatory requirements for frequent channel availability checks cause interruptions.
Implementing a database of radar interference information, either centralized or local, to assist WLAN devices in selecting DFS channels with reduced interference, and using beaconing devices to broadcast DFS beacons for real-time channel switching.
Reduces the need for lengthy channel availability checks, minimizes interference with radar operations, and ensures continuous WLAN operation by enabling proactive channel switching based on crowdsourced or locally stored radar interference data.
Smart Images

Figure 0007577677000001 
Figure 0007577677000002 
Figure 0007577677000003
Abstract
Description
[Technical field]
[0001] Related Applications This application is a continuation of U.S. Non-provisional Patent Application No. 16 / 299,850, filed March 12, 2019, which is hereby incorporated by reference in its entirety.
[0002] Technical Field The technology of this application relates generally to Wireless Local Area Network (WLAN) systems, and more specifically to systems and methods for devices or vehicles operating within WLAN Dynamic Frequency Selection (DFS) channels to minimize interference to coexisting radar systems. [Background technology]
[0003] WLAN systems that comply with the IEEE 802.11 standard can operate at 2.4 GHz, 5 GHz, or higher frequency bands. Channels in the 5 GHz band are classified as indoor or outdoor channels based on their permitted usage. WLAN outdoor channels in the 5 GHz band are increasingly used in automobiles for in-vehicle networking and to exchange information between automobiles and to receive information from the system infrastructure in support of autonomous driving and other applications. In some countries, some, if not all, WLAN outdoor 5 GHz channels are also used by radars, e.g., weather radars, military radars, and civil radars. These 5 GHz channels where WLAN and radar operations coexist are called Dynamic Frequency Selection (DFS) channels. A WLAN device that has the ability to detect the presence of radar at its operating frequency and can direct its connected network components away from the radar operating frequency is called a WLAN DFS master device. A WLAN device that does not have this capability and is subordinate to a master device for operation in a DFS channel is called a slave device.
[0004] To minimize the interference that WLAN devices cause to radar, regulatory authorities in many jurisdictions impose strict requirements on the behavior of WLAN devices operating in DFS channels. For example, before a WLAN DFS master device can start transmitting in a WLAN DFS channel, the device is required to perform a radar scan, called a Channel Availability Check (CAC), to detect radar signals. This CAC can last from one minute for civil radar to 10 minutes or more for weather and military radar. During the CAC, the WLAN DFS master device can be prohibited from performing any WLAN operations. If no radar signals are detected, the WLAN DFS master device can operate on the channel. During operation, the WLAN DFS master device is required to constantly monitor for any radar signals in the same channel in a process called in-service monitoring (ISM). If a radar signal is detected in the DFS channel at any time during CAC or ISM, the WLAN DFS master device is required to quickly transition to a different channel. If this second channel is also another DFS channel, the WLAN DFS master device may have to perform CAC and ISM again until a DFS channel without a radar signal is found.
[0005] A radar can transmit a narrow beam of radio pulses that rotate 360 degrees around the radar. If a vehicle is continuously moving, a WLAN DFS master device deployed in the vehicle may not detect radar signals accurately compared to a stationary device. Even if the WLAN DFS master device detects radar signals, the information collected about the detected signals may be out of date as the vehicle moves to another location. Inaccurate and out-of-date radar detection and signal information may cause unreliable WLAN DFS operation, which may further increase interference with radar operation. In addition, the WLAN operation of the WLAN DFS master device is interrupted during the long CAC period used to scan for radar signals, resulting in network outages for end-user WLAN operation in slave devices.
[0006] The embodiments herein and their advantages can be best understood by referring to the following description in conjunction with the accompanying drawings, which are in no way limiting of any changes in form and detail that may be made by those skilled in the art to the embodiments herein without departing from the concept and scope of the embodiments herein. [Brief description of the drawings]
[0007] [Figure 1] FIG. 1 illustrates an exemplary outdoor wireless local area network (WLAN) architecture deployed for a vehicle, according to some embodiments of the present disclosure. [Diagram 2] FIG. 1 illustrates an example system in which automobiles access a cooperative network server for geotagged radar interference data as an aid for selecting a WLAN dynamic frequency selection (DFS) channel, in accordance with some embodiments of the present disclosure. [Diagram 3]FIG. 1 illustrates an example system in which a vehicle accesses a local database of geotagged radar interference data as an aid for selecting a WLAN DFS channel, in accordance with some embodiments of the present disclosure. [Figure 4] 1 is a flowchart illustrating a method for a WLAN device deployed in a vehicle to access a cooperative network server or a local database of geotagged radar interference data as an aid for selecting a WLAN DFS channel, according to some embodiments of the present disclosure. [Diagram 5] FIG. 1 is a block diagram of a WLAN DFS device deployed in a vehicle configured to access a cooperative network server or a local database of geotagged radar interference data as an aid for selecting a WLAN DFS channel, in accordance with some embodiments of the present disclosure. [Figure 6] FIG. 2 illustrates an example system in which a car receives DFS action frames from a beaconing device as an aid for selecting a WLAN DFS channel, in accordance with some embodiments of the present disclosure. [Figure 7] 1 is a flow chart illustrating a method for a WLAN device deployed in an automobile to receive DFS beacons from a beacon emitting device as an aid for selecting a WLAN DFS channel, according to some embodiments of the present disclosure. [Figure 8A] FIG. 2 is a block diagram of a DFS action frame beacon originating device according to some embodiments of the present disclosure. [Figure 8B] FIG. 2 is a block diagram of a WLAN DFS device deployed in an automobile configured to receive DFS action frames from a beaconing device as an aid for selecting a WLAN DFS channel, in accordance with some embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0008] Examples of various aspects and variations of the technology of the present application are described herein and illustrated in the accompanying drawings. The following description is not intended to limit the invention to those embodiments, but rather to enable one of ordinary skill in the art to make and use the invention.
[0009] In accordance with one aspect of the present technology, a database of radar interference sources can be collected from wireless local area networks (WLANs) deployed in one or more automobiles, and the database can be queried by WLAN devices in the field to assist the WLAN devices in selecting operating dynamic frequency selection (DFS) channels that minimize the probability of radar interference.
[0010] According to one embodiment, information about radar interference can be crowdsourced by automobiles operating in the field equipped with WLAN devices that support reporting of radar signal information detected on DFS channels. WLAN devices, such as WLAN DFS master devices, can detect the presence of radar signals and report information such as detection location, DFS channel used, and operation time to a centralized server, which consolidates the reported information to build a database. WLAN devices in automobiles that want to operate in DFS channels and include slave devices that are not capable of detecting radar signals can query this database to obtain information about possible nearby radar signals and select DFS channels with reduced radar interference probability.
[0011] According to one embodiment, a database of radar interference can be stored locally on the WLAN device or vehicle instead of on a centralized server. The WLAN device can store information about detected radar interference over time in a local database. To avoid DFS channels that may have radar interference, the WLAN device can query the local database when the vehicle approaches a location. Advantageously, leveraging a database of radar information remotely or locally can reduce the need for channel availability checks (DFS-CAC), allowing WLAN operation to continue without interruptions due to DFS-CAS scans.
[0012] According to another aspect of the technology of the present application, a dedicated WLAN beacon emitting device located at the border of the radar interference range can broadcast a DFS beacon or dedicated action frame to notify or warn a WLAN device in a vehicle approaching the radar interference range of a radar operation to avoid the DFS channel used by the radar. The WLAN beacon emitting device can broadcast a periodic dedicated action frame that carries information about the DFS channel used by a nearby radar, the GPS coordinates of the radar interference range or the border of the radar interference range, the DFS candidate channel recommended to the WLAN device for switching, etc. The WLAN beacon emitting device can broadcast a dedicated action frame on a WLAN DFS channel that is the same as and overlaps with the radar signal but outside the border of the radar interference range, so that the action frame does not interfere with the radar operation. The WLAN device operating in the same DFS channel as the radar signal can receive the dedicated action frame when the vehicle approaches the border of the radar interference and can switch to a different DFS channel before entering the radar interference range. Advantageously, when a dedicated action frame is received as a WLAN packet, the DFS master device and the DFS slave device can quickly and reliably switch to a different DFS channel to avoid a DFS channel carrying a radar signal.
[0013] FIG. 1 illustrates an exemplary outdoor wireless local area network (WLAN) architecture deployed for automobiles according to some embodiments of the present disclosure. WLAN devices may be deployed in automobiles 101 and 103 to communicate using the IEEE 802.11 standard. The WLAN devices may be user stations (STAs) configured to associate with an access point (AP) 105 deployed at the roadside when the automobiles 101 and 103 are within range of the AP 105. The WLAN devices in automobiles 101 and 103 and the AP 105 may form a basic service set (BSS). Once associated with the AP 105, the WLAN devices may receive information from the AP 105, such as road conditions, traffic conditions, environmental and other infrastructure information, which assists the automobiles 101 and 103 in navigating the road. According to one scenario, the automobiles 101 and 103 may exchange vehicle information, such as speed, direction of travel, etc., in peer-to-peer communication using the WLAN devices without routing data traffic through the AP 105. Vehicle 101 or 103 can use information received from the other vehicle and / or from AP 105 to facilitate autonomous driving. According to another scenario, vehicle 101 can play the role of a SoftAP host or peer-to-peer group owner (P2P GO), and in-vehicle WLAN clients inside vehicle 101 (e.g., WLAN-capable mobile phones carried by passengers or in-vehicle entertainment consoles at passenger seats) can connect to said host or group owner and thereby exchange infotainment content.
[0014] The WLAN system may operate on one or more 5 GHz WLAN DFS channels shared with a radar system. The WLAN device in the automobile 101 or 103 may be a WLAN DFS master device configured to detect the presence of radar signals in the operating channel, and may direct itself and connected slave devices without radar detection capability away from the operating channel if radar interference is detected. Before the WLAN DFS master device can start operating in a DFS channel, regulations may require the WLAN DFS master device to perform a DFS-CAS scan for a minimum period of time to ensure that the channel is free of radar interference. During operation, even after clearing DFS-CAC, the WLAN DFS master device may still be required to constantly monitor for any radar signals in the operating channel using in-service monitoring (ISM). If a radar signal is detected in the DFS channel at any time during CAC or ISM, the WLAN DFS master device and connected slave devices are required to quickly transition to a different channel. Assistance information regarding radar interference may be provided to WLAN devices to assist them in selecting DFS channels with reduced radar interference probability and to reduce interference caused by the WLAN devices to radar operations.
[0015] The examples, implementations and embodiments described herein are primarily described in the context of WLANs. According to one embodiment, the WLAN system may be a WLAN network using various versions of the IEEE 802.11 standard, although other WLAN systems are contemplated.
[0016] 2 illustrates an example system in which automobiles access a cooperative network server 206 for geotagged radar interference data to aid in selecting a WLAN DFS channel, according to some embodiments of the present disclosure. Three vehicles are shown: vehicle 201, vehicle 203, and vehicle 209.
[0017] A vehicle 201 capable of carrying a WLAN DFS master device may move into the operating range 207 of a radar 205. According to one embodiment, the radar 205 may be an air traffic control radar operating at an airport. The WLAN DFS master device may initially operate on a DFS channel before the vehicle 201 enters the radar operating range 207. If the radar 205 is operating on the same DFS channel as the vehicle 201, then after the vehicle 201 enters the radar operating range 207, a DFS-ISM scan of the WLAN DFS master device may detect a radar signal on the operating DFS channel. In addition, the WLAN DFS master device may record the DFS channel of the radar 205, the GPS coordinates of the vehicle 201, and the time when the radar signal was detected by the DFS-ISM scan. The recorded GPS coordinates may represent a geographic point on the boundary of the radar operating range 207. The recorded time may represent a time when the radar 205 is operating. The WLAN DFS master device may upload information about the detected radar signal, including the DFS channel of the radar 205, the recorded GPS coordinates, and the recorded time to the cooperative network server 206. According to one embodiment, the WLAN DFS master device may communicate with the cooperative network server 206 over a cellular network operating in GSM, LTE, 5G, or other type of wide area network. According to one embodiment, the cooperative network server 206 may be connected to the wide area network via the Internet.
[0018] Similarly, vehicle 203, or another vehicle equipped with a WLAN DFS master device, may move into radar operating range 207. If the WLAN DFS master device on vehicle 203 is operating on the same DFS channel as radar 205, then its DFS-ISM scan may similarly detect radar signals on the operating DFS channel when vehicle 203 enters radar operating range 207. According to one embodiment, the DFS channel detected by vehicle 203 may be the same as the DFS channel detected by vehicle 201. According to one embodiment, if radar 205 changes its operating DFS channel, then the DFS channel detected by vehicle 203 may be different from the DFS channel detected by vehicle 201. As in the case of vehicle 201, the WLAN DFS master device in vehicle 203 may record the DFS channel of radar 205, the GPS coordinates of vehicle 203, and the time when a radar signal was detected by its DFS-ISM scan. The recorded GPS coordinates may thus represent different geographic points on the boundary of the radar operating range 207, and the recorded time points may represent different times when the radar 205 is operating. The WLAN DFS master device in the vehicle 203 may similarly upload information about the detected radar signal to the cooperative network server 206, including the DFS channel of the radar 205, the recorded GPS coordinates, and the recorded time points.
[0019] The cooperative network server 206 can store information about detected radar interference collected from vehicle 201, vehicle 203 and other vehicles in a centralized database. The crowdsourced database can thus represent the estimated boundaries of the ranges of multiple radar zones expressed in GPS coordinates, the DFS channels on which radars are expected to operate, and the estimated time of their operation. According to one embodiment, the crowdsourced database can be updated or overwritten when operating parameters of existing radars are changed, new radars are commissioned, or old radars are decommissioned. Information that has not been updated for a threshold period of time can be declared out of date and removed from the database.
[0020] A vehicle having a WLAN device that may wish to operate in a DFS channel at a geographic location for a particular time may query the centralized database for possible radar interference near the desired geographic location and desired time to determine if the DFS channel is free or if it may be prudent to switch to another DFS channel to reduce the radar interference probability. According to one embodiment, the cooperative network server 206 may analyze the operating characteristics of the radar zones contained in the centralized database to suggest a DFS channel that minimizes the radar interference probability based on the location and time of the querying vehicle. According to one embodiment, the vehicle may periodically transmit its current GPS coordinates to the cooperative network server 206 to receive information regarding any possible approaching radar zones. If this information indicates that a radar zone is approaching, the vehicle may proactively switch to a DFS channel to avoid any radar interference. For example, the vehicle 209 may periodically transmit its GPS coordinates to the cooperative network server 206. The WLAN device on board the vehicle 209 may be a WLAN DFS master device or a slave device. Based on its expected travel path, the cooperative network server 206 can query a centralized database to predict that the vehicle 209 is approaching the boundary of the operating range 207 of the radar 205. The centralized database can indicate that the radar 205 is operating on a particular DFS channel. The cooperative network server 206 can transmit the GPS coordinates of one or more locations on the boundary of the operating range 207 where the vehicle 209 is expected to enter the operating range 207 of the radar 205, and the expected operating channel of the radar 205. If a WLAN device in the vehicle 209 is operating on the same DFS channel, the device can be prepared to switch to a different DFS channel before encountering radar interference from the radar 205.According to one embodiment, the cooperative network server 206 can suggest a DFS channel to which the WLAN device can switch. The vehicle 209 can use this information to switch to a different DFS channel that will cause minimal interruption to its WLAN operation.
[0021] According to one embodiment, once a route for the vehicle has already been selected, for example by using an in-vehicle navigation system, the vehicle can query the centralized database to predict possible radar interference zones along the route. The WLAN device in the vehicle can select a DFS channel that is expected to cause minimal or no radar interference. Advantageously, the WLAN device can avoid disruptions to WLAN operation associated with switching channels, such as the WLAN interruption encountered when the WLAN DFS master device performs a DFS-CAC scan on a new channel. Similarly for the WLAN DFS slave device, a reduction or reduction in channel switching operations, or the ability to switch channels before the vehicle approaches an expected radar zone, reduces disruptions to WLAN operation and reduces interference of WLAN operation with radar operation in interaction. According to one embodiment, the WLAN device can pre-fetch or download the centralized database for offline use.
[0022] 3 illustrates an exemplary system in which an automobile accesses a local database of geotagged radar interference data as an aid for selecting a WLAN DFS channel, according to some embodiments of the present disclosure. According to one embodiment, the database stored locally in the vehicle may include information about radar interference collected only by the vehicle. Using current or desired GPS coordinates, the WLAN device in the vehicle may query the local database to identify possible radar interference near the GPS coordinates based on a record of locations where the vehicle has been and where radar interference has been detected by the vehicle. While a locally stored database eliminates the need for the WLAN device to access a remote cooperative network server 206, it may not be as comprehensive or up-to-date as a crowdsourced database.
[0023] A vehicle 301, which may be equipped with a WLAN DFS master device, may move within the operating range 207 of radar 205 at a location 302. If the WLAN DFS master device on vehicle 301 is operating on the same DFS channel as radar 205, its DFS-ISM scan may detect a radar signal on the DFS channel when vehicle 301 enters radar operating range 207 at location 302. The WLAN DFS master device may record in a local database on vehicle 301 the DFS channel of radar 205, the GPS coordinates of vehicle 301 at location 302, and the time when radar interference was detected. The local database may be built by vehicle 301 over time to include a local knowledge base of time-stamped, geo-tagged radar zones. Later, when the vehicle 301 approaches the radar operating range 207 of the radar 205 at the location 303, the WLAN device can query the local database based on its current GPS coordinates at the location 303 to receive warnings about nearby radar interference. If the WLAN device is operating on the same DFS channel as the radar 205, the WLAN device can prepare to switch to a different channel before the vehicle 301 encounters radar interference from the radar 205. According to one embodiment, the local database can suggest a DFS channel to which the WLAN device should switch. According to one embodiment, if the path of the vehicle 301 is known, the WLAN device can query the local database to predict possible zones of radar interference and select a DFS channel that is expected to cause minimal or no radar interference.
[0024] According to one embodiment, the locally stored database can be a crowdsourced database that the vehicle 301 has downloaded or pre-fetched from a cooperative network server (e.g., 206) for offline use. For example, the WLAN device in the vehicle 301 can download the crowdsourced database into the locally stored database before a trip. In this way, the vehicle 301 can take advantage of the crowdsourced information to identify possible radar interference sources while traveling, even if the vehicle is offline. According to one embodiment, the WLAN device can communicate a planned travel route to the cooperative network server 206 and can download a portion of the crowdsourced database, including information about radar zones near the planned travel route, into the locally stored database before or even while traveling. The WLAN device can then switch to an offline mode to access the locally stored database. According to one embodiment, the WLAN device of the vehicle 301 can download the locally stored databases of other vehicles into the locally stored database of the vehicle 301 using peer-to-peer WLAN operation to take advantage of information about radar interference collected by other vehicles. According to one embodiment, the WLAN device of vehicle 301 can download databases of other vehicles via peer-to-peer operation using LTE, 5G or other types of cellular networks.
[0025] 4 illustrates a flow chart of a method 400 for a WLAN device deployed in a vehicle to access a cooperative network server (e.g., 206) or a local database of geotagged radar interference data as an aid for selecting a WLAN DFS channel, according to some embodiments of the present disclosure. Method 400 may be implemented by processing logic, which may comprise hardware (e.g., circuitry, dedicated logic, programmable logic, processing device, etc.), software (e.g., instructions operating / executed on a processing device), firmware (e.g., microcode), or a combination thereof. According to some embodiments, method 400 may be implemented by a WLAN DFS master device or a processing device included within a WLAN device (e.g., processing device 501 shown in FIG. 5).
[0026] A request to start WLAN operation in a DFS channel is initiated in step 401. For example, a WLAN DFS master device in a vehicle may request to operate in a DFS channel because only DFS channels are available for WLAN operation in a certain geographic region, or because a scan of free channels indicates that non-DFS channels may not have sufficient bandwidth to support the desired WLAN operation due to high data traffic, or for some other reason.
[0027] According to one embodiment, the WLAN DFS master device can transmit GPS coordinates of its current location to a database, such as database 407 containing time-stamped, geo-tagged radar interference data, to receive information regarding candidate DFS channels for WLAN operation. Database 407 can be a centralized, crowd-sourced database at a cooperative network server (e.g., 206) or a locally stored database at the WLAN DFS master device. According to one embodiment, the locally stored database can be built over time by the WLAN DFS master device to include a local knowledge base of time-stamped, geo-tagged radar zones as discussed in connection with FIG. 3. According to one embodiment, the locally stored database can be a crowd-sourced database downloaded or pre-fetched by the WLAN DFS master device from a centralized database for offline use.
[0028] Based on the current GPS location of the WLAN DFS master device and the current time, database 407 can instruct the WLAN DFS master device on DFS channels that may be in use by radar operating near the current GPS location, in step 405. According to one embodiment, database 407 can suggest one or more DFS channels that can be used with a minimum probability of radar interference.
[0029] In step 403, method 400 can determine candidate DFS channels for WLAN operation. According to one embodiment, when the WLAN DFS master device receives information from database 407 regarding DFS channels in use in nearby radar zones, the WLAN DFS master device can select a DFS channel that avoids possible radar interference. According to one embodiment, when the WLAN DFS master device receives a suggestion from database 407 regarding a DFS channel that minimizes radar interference probability, the WLAN DFS master device can select one of the proposed DFS channels.
[0030] At step 409, method 400 may perform a DFS-CAC scan on the selected DFS channel. According to one embodiment, rules may require the WLAN DFS master device to perform a DFS-CAS scan for a minimum period of time to ensure that the selected DFS channel is free of radar interference before the WLAN DFS master device can begin operating in that channel.
[0031] In step 411, method 400 can determine whether a radar signal is detected during a DFS-CAC scan. For example, the WLAN DFS master device may be located in a location where database 407 may not have any information or up-to-date information regarding radar interference. Thus, DFS-CAC can detect radar interference on a selected DFS channel even if information from database 407 does not indicate that the selected DFS channel is being used by a nearby radar.
[0032] If a radar signal is detected on the selected DFS channel, then in step 413, method 400 can update database 407 with a time-stamped, geotagged entry containing information about the detected radar signal. For example, the WLAN DFS master device can record the DFS channel on which the radar signal was detected, the GPS coordinates of the vehicle, and the time when the radar signal was detected. The WLAN DFS master device can update database 407 with the recorded information about the DFS channel, the recorded GPS coordinates, and the recorded time. According to one embodiment, if database 407 is a centralized database, the WLAN DFS master device can upload the information to a collaborative network server (e.g., 206) to update the crowd-sourced database. The WLAN DFS master device can select a new candidate DFS channel by querying database 407, and method 400 can repeat steps 403, 409, and 411 until a selected DFS channel without channel interference is found during the DFS-CAS scan.
[0033] If no radar signals are detected on the selected DFS channel, then method 400 may start WLAN operation on the selected DFS channel at step 415. In parallel, method 400 may perform a DFS-ISM scan to monitor for any radar signals that may appear on the operating channel as the vehicle moves. Method 400 may continually query database 407 based on the vehicle's current GPS coordinates to determine whether the operating channel is likely to encounter radar interference, for example, based on the vehicle's current location or its planned route.
[0034] If a radar signal is detected on an operating DFS channel during the DFS-ISM scan in step 417, method 400 can update database 407 with a time-stamped, geotagged entry containing information about the detected radar signal. For example, the WLAN DFS master device can record the operating DFS channel on which the radar signal was detected, the GPS coordinates of the vehicle, and the time when the radar signal was detected. The WLAN DFS master device can update database 407 with the recorded information about the operating DFS channel, the recorded GPS coordinates, and the recorded time. The WLAN DFS master device can select a new candidate DFS channel for WLAN operation in step 403 by querying database 407, and method 400 can repeat the DFS-CAC and DFS-ISM scans in steps 409, 411, 415, and 417.
[0035] If no radar signal is detected on the operating channel during the DFS-ISM scan in step 419, method 400 may continue WLAN operation on the operating channel. Method 400 may continually query database 407 based on the vehicle's current GPS coordinates to determine if the operating channel is likely to encounter radar interference. For example, if radar interference is expected on the operating channel based on the vehicle's planned travel path, the WLAN DFS master device may switch to a different operating channel before the radar interference occurs. The WLAN DFS master device may select a new candidate DFS channel for WLAN operation in step 403 by querying database 407, and method 400 may repeat DFS-CAC and DFS-ISM scans in steps 409, 411, 415, and 417.
[0036] While method 400 is illustrated using a WLAN DFS master device, a WLAN DFS slave device may also perform some steps of method 400 to access a cooperative network server (e.g., 206) or a local database of time-stamped, geotagged radar interference data to aid in selecting a WLAN DFS channel. For example, in step 403, the slave device may determine candidate channels by receiving information from database 407 about DFS channels used in nearby radar zones or suggestions about DFS channels that minimize radar interference probability. In step 419, the slave device may select an operating channel and continually query database 407 based on the vehicle's current GPS coordinates to determine whether the operating channel is likely to encounter radar interference. If radar interference is expected on the operating channel, the slave device may switch to a different operating channel before radar interference occurs.
[0037] 5 is a block diagram of a WLAN DFS device 501 deployed in an automobile configured to access a cooperative network server (e.g., 206) or a local database of geotagged radar interference data as an aid for selecting a WLAN DFS channel, according to some embodiments of the present disclosure. The WLAN DFS device 501 may be a WLAN device in a vehicle 201, 203, 209, 301, which may perform the steps of method 400.
[0038] The WLAN DFS device 501 can be a WLAN DFS master device or a slave device. The WLAN DFS device 501 can include a GPS subsystem 503, a map service 505, a WLAN subsystem 507, a system clock 509, a wide area network (WAN) connectivity subsystem 511, a local storage subsystem 513, and a DFS channel selector application 515.
[0039] A GPS subsystem 503 can be configured to provide GPS coordinates of the WLAN DFS device 501. The GPS coordinates can be used to geotag detected radar signals for the WLAN DFS master device. A map service 505 can be configured to map the GPS coordinates provided by the GPS subsystem 503 to a travel path, which can also provide navigation services for the vehicle. The travel path can be used with a database of time-stamped, geotagged radar interference to predict possible radar interference zones along the path.
[0040] The WLAN Subsystem 507 may be configured to use a selected channel for WLAN operation. For example, the WLAN Subsystem 507 may be configured to transmit or receive data packets, control frames, etc., with other WLAN DFS devices or access points over the WLAN channel. The System Clock 509 may be configured to maintain a system time that is used to timestamp radar signals detected by the WLAN DFS master device. According to one embodiment, the GPS Subsystem 503 may be configured to provide the system time.
[0041] The WAN connectivity subsystem 511 can be configured by the WLAN DFS master device to upload information about the detected radar signal to a cooperative network server (e.g., 206), including the DFS channel of the detected radar signal, the recorded GPS coordinate, and the recorded time when the radar signal was detected. The WAN connectivity subsystem 511 can also be configured by both the WLAN DFS master device and the WLAN DFS slave device to transmit the current GPS coordinate of the WLAN DFS device 501 and receive information about radar interference near the current GPS coordinate from the cooperative network server (e.g., 206).
[0042] The local storage subsystem 513 can be configured to store a local database of time-stamped, geo-tagged radar interference data. According to one embodiment, the local storage subsystem 513 can include a local knowledge base of time-stamped, geo-tagged radar zones detected by the WLAN DFS device 501. According to one embodiment, the local storage subsystem 513 can store a crowd-sourced centralized database of time-stamped, geo-tagged radar zones downloaded from a collaborative network server (e.g., 206).
[0043] A DFS channel selector application 515 may be run on the processor to perform one or more of the operations in the method 400 of FIG. 4 for the WLAN DFS device 501 to access a cooperative network server (e.g., 206) or a local storage subsystem 513 to obtain time-stamped, geotagged radar interference information as an aid in selecting a WLAN DFS channel for WLAN operation.
[0044] According to one embodiment, the WLAN DFS device 501 may include a memory and a processing device. The memory may be a synchronous dynamic random access memory (DRAM), a read-only memory (ROM), or other type of memory, which may be configured to store the DFS channel selector application 515 or the local storage subsystem 513. The processing device may be provided by one or more general-purpose processing devices, such as a microprocessor, a central processing unit, or the like. In an exemplary embodiment, the processing device may have a complex instruction set computing (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, or a processor implementing other instruction sets, or a processor implementing a combination of multiple instruction sets. The processing device may also have one or more special-purpose processing devices, such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), a network processor, or the like. To perform the operations and steps described herein, the processing device may be configured to perform the operations described herein in accordance with one or more aspects of the present disclosure.
[0045] FIG. 6 illustrates an example system in which a vehicle receives DFS action frames from a beaconing device as an aid for selecting a WLAN DFS channel, according to some embodiments of the present disclosure.
[0046] A radar 205 is operating on a WLAN DFS channel. The radar 205 may have an operating range 207. For example, the radar 205 may be an air traffic control radar operating at an airport. A dedicated WLAN beacon emitting device, sometimes referred to as a WLAN DFS action frame beacon emitting device 601 or 603, may be installed at the boundary of the radar operating range 207. To alert WLAN devices in vehicles approaching the radar operating range 207 that the radar 205 is operating nearby and to avoid the DFS channel used by the radar 205, the WLAN DFS action frame beacon emitting device may broadcast a dedicated WLAN action frame, sometimes referred to as a DFS beacon, on the DFS channel of the radar 205.
[0047] The DFS beacon may carry information including a timestamp, one or more WLAN DFS channels that are being used by the radar 205 and that the WLAN device should avoid, one or more recommended WLAN DFS channels that the WLAN device may use as alternative channels, information about the radar operating range 207, a digital signature, etc. According to one embodiment, when the WLAN DFS action frame beacon originating device 601 / 603 recommends an alternative channel, the WLAN traffic of the multiple WLAN devices may be more evenly distributed over multiple free DFS channels, the WLAN DFS action frame beacon originating device 601 / 603 may scan for traffic on the free DFS channels that are not being used by the radar. According to one embodiment, the WLAN DFS action frame beacon originating device 601 / 603 may prioritize the alternative channels so that the less loaded channels may be recommended first. According to one embodiment, the information about the radar operating range 207 may be represented by GPS coordinates of the boundary of the radar operating range 207. Such GPS coordinates of the boundary may define the validity area of the information carried by the DFS beacon. According to one embodiment, digital signatures can be used by WLAN devices to check the authenticity or validity of the information carried by the DFS beacons. According to one embodiment, these DFS beacons can be transmitted periodically.
[0048] The WLAN DFS action frame beacon originating device 601 broadcasts a DFS beacon on a DFS channel used by the radar 205 so that WLAN devices operating on the same DFS channel can receive the DFS beacon, quickly discover radar interference on the DFS channel, and switch to another channel, such as one of multiple alternative channels recommended by the DFS beacon. According to one embodiment, the WLAN DFS action frame beacon originating device 601 can broadcast a DFS beacon outside of the radar operating range 207 so that the transmission of the DFS beacon itself does not cause interference to the operation of the radar 205.
[0049] Advantageously, vehicles approaching radar operating range 207 and having WLAN devices operating on a DFS channel of radar 205 can detect these DFS beacons and can switch their operating channel to a free DFS channel before the vehicle enters radar operating range 207 to minimize any interference with radar operation. Additionally, because DFS beacons are transmitted as WLAN packets, both WLAN DFS master and WLAN DFS slave devices can detect the DFS beacons and quickly avoid DFS channels carrying radar signals.
[0050] For example, a WLAN device in a vehicle 605 approaching the radar operating range 207 from one direction can receive a DFS beacon from the beacon emitting device 601 if the WLAN device is operating on the same DFS channel as the radar 205. The WLAN device can authenticate the validity of the DFS beacon using the digital signature carried in the DFS beacon. The WLAN device can receive the validity area of the information carried by the DFS beacon, expressed as GPS coordinates of the boundaries of the radar operating range 207. Based on the validity area and the planned travel path, the WLAN device can determine that the vehicle 605 is likely to enter the radar operating range 207. The WLAN device can receive from the DFS beacon the DFS channels to avoid and the recommended alternative DFS channels to transition to. According to one embodiment, the DFS channels to avoid can include the current operating channel of the WLAN device and other DFS channels that may be used by the radar 205. The WLAN device can switch its operating channel to one of multiple alternative DFS channels that were recommended as the new channel before the vehicle 605 entered the radar operating range 207. During the time that the vehicle 605 is within the radar operating range 207, the WLAN device can continue WLAN operation using the new DFS channel without interfering with the operation of the radar 205. When the vehicle 605 leaves the radar operating range 207, the WLAN device can remain on its new channel or can switch back to its previous operating channel.
[0051] Similarly, a WLAN device in another vehicle 609 approaching the radar operating range 207 from the other direction can receive a DFS beacon from the beacon emitting device 603 if the WLAN device is operating on the same DFS channel as the radar 205. Similarly, the WLAN device can switch to a new DFS channel before the vehicle 609 enters the radar operating range 207. The new channel used by the WLAN device in the vehicle 609 can be the same channel as the new channel used by the WLAN device in the vehicle 605, or it can be a different channel. In addition to avoiding interference with the operation of the radar 205, the new DFS channels used by the vehicles 605, 609 and other vehicles 607, 611 for WLAN operation can be prioritized by the beacon emitting devices 601 / 603 to more evenly distribute the load of WLAN traffic on those new DFS channels. Additionally, even WLAN DFS slave devices that normally cannot detect radar signals may receive DFS beacons and be able to switch to a new DFS channel to avoid interfering with the operation of radar 205.
[0052] 7 illustrates a flow chart of a method 700 for a WLAN device deployed in an automobile to receive DFS beacons from a beacon emitting device as an aid for selecting a WLAN DFS channel, according to some embodiments of the present disclosure. The method 700 may be implemented by processing logic, which may comprise hardware (e.g., circuitry, dedicated logic, programmable logic, processor, processing device, central processing unit (CPU), multi-core processor, system on chip (SoC), etc.), software (e.g., instructions running / executed on a processing device), firmware (e.g., microcode), or a combination thereof. According to some embodiments, the method 700 may be implemented by a WLAN DFS master device, a WLAN DFS slave device, or a processing device included within a WLAN device (e.g., processing device 811 shown in FIG. 8B).
[0053] In step 701, a WLAN device may operate in a DFS channel. For example, a WLAN DFS master device or a WLAN DFS slave device in a vehicle may operate in a DFS channel because only DFS channels are available for WLAN operation in a certain geographical area, or because a scan of free channels indicates that non-DFS channels may not have sufficient bandwidth to support the desired WLAN operation due to high data traffic, or for some other reason. According to one embodiment, before starting operation in this DFS channel, the WLAN device may have completed a DFS-CAS scan to ensure that there is no radar operating in this DFS channel.
[0054] In step 703, the WLAN device may monitor the DFS channel for DFS beacons to alert the presence of a radar operating on the same DFS channel. In parallel with this, the WLAN device may perform a DFS-ISM scan to monitor any radar signals that may appear in the operating channel. For example, a WLAN DFS master device may perform a DFS-ISM scan on the operating channel in addition to monitoring the DFS beacons. For a WLAN DFS slave device that does not have the capability to detect radar signals, in addition to monitoring the DFS beacons, the device may monitor the operating channel for messages from an associated WLAN DFS master device indicating that a radar signature has been detected by the WLAN DFS master device.
[0055] In step 705, the WLAN DFS master device can determine through the DFS-ISM whether a radar signal is detected on the operating channel. In step 711, if a radar signal is detected on the operating channel, the WLAN DFS master device can identify a candidate channel to switch to and, if the channel is a DFS channel, can perform a DFS-CAS scan. The WLAN DFS master device can repeat this process through the candidate channel list until it finds a candidate channel without radar activity. According to one embodiment, the WLAN DFS master device can send a message on the operating channel to an associated slave device to signal the slave device to switch from the operating channel. The slave device that receives the message can identify a candidate channel to switch to if the slave device is currently using the operating channel.
[0056] In step 713, the WLAN device may determine whether the candidate channel is a DFS channel. If the candidate channel is a DFS channel, the WLAN device may switch to the candidate channel as a new WLAN operating channel and monitor DFS beacons on the new channel to alert that a radar is operating on the new channel in step 703. In parallel, the WLAN device may perform a DFS-ISM scan to monitor for any radar signals that may appear on the new channel if the WLAN device is a WLAN DFS master device. If the candidate channel is not a DFS channel, in step 715, the WLAN device may switch to the candidate channel for WLAN operation.
[0057] If the WLAN DFS master device has not detected a radar signal on the operating channel through a DFS-ISM scan, or if the WLAN DFS slave device has not received a message from an associated WLAN DFS slave device indicating that a radar signature has been detected by the WLAN DFS master device, then in step 707 the WLAN device may determine whether a DFS beacon has been received on the operating channel.
[0058] If no DFS beacons were received on the operating channel, the WLAN device may continue to monitor the operating channel for DFS beacons to alert it to radar operating on the operating channel in step 703. In parallel, the WLAN device may continue to perform DFS-ISM scans to monitor for any radar signals that may appear in the operating channel if the WLAN device is a WLAN DFS master device, or may continue to monitor the operating channel for messages from an associated WLAN DFS master device indicating that a radar signature has been detected if the WLAN device is a slave device.
[0059] If the DFS beacon is received on the operating channel, the WLAN device can authenticate the validity of the DFS beacon in step 709 using the digital signature carried in the DFS beacon. If the DFS beacon is authenticated, the WLAN device can receive information about the validity area of the DFS beacon, which can represent a radar operating area, in step 710. Based on this information and the vehicle's planned travel path, the WLAN device can determine that the vehicle may enter a radar operating area. The WLAN device can receive DFS channels to avoid, which may include the current operating channel, and recommended alternative DFS channels to transition to from the DFS beacon. In step 711, the WLAN device can switch to one of the multiple alternative DFS channels recommended as a new channel for WLAN operation before the vehicle enters the radar operating area. Then, in step 713, the WLAN device can determine whether the new channel is a DFS channel. If the new channel is a DFS channel, in step 703, the WLAN device can monitor DFS beacons on the new channel to alert that a radar is operating on the new channel. In parallel, the WLAN device may perform a DFS-ISM scan to monitor for any radar signals that may appear on the new channel if the WLAN device is a WLAN DFS master device. If the new channel is not a DFS channel, then in step 715 the WLAN device may operate using the new channel.
[0060] 8A is a block diagram of a DFS action frame beacon originating device 801 according to some embodiments of the disclosure. The beacon originating device 801 may be the beacon device 601 or 603 of FIG.
[0061] The DFS action frame beacon originating device 801 may include a DFS action frame trigger application 803, a WLAN driver 805, and a WLAN hardware 807. The DFS action frame trigger application 803 is operable on a processor to periodically generate DFS beacon information including a timestamp, one or more WLAN DFS channels being used by a nearby radar, one or more recommended WLAN DFS channels that the WLAN device may use as alternate channels, information about radar operating range, a digital signature, etc. According to one embodiment, the DFS action frame trigger application 803 may use the WLAN hardware 807 to scan for traffic on free DFS channels not being used by a radar, such that WLAN traffic of multiple WLAN devices may be more evenly distributed on multiple free DFS channels when multiple alternate channels are recommended.
[0062] A WLAN driver 805 is operable on the processor to generate WLAN packets including a payload carrying DFS beacon information provided by the DFS action frame trigger application 803. The WLAN hardware 807 can be configured to periodically transmit the WLAN packets as DFS action frames or DFS beacons on the DFS channel being used by the radar.
[0063] 8B is a block diagram of a WLAN DFS device 811 deployed in an automobile configured to receive DFS action frames from a beaconing device (e.g., 601, 603, 801) as an aid for selecting a WLAN DFS channel, according to some embodiments of the present disclosure. The WLAN DFS device 811 can be a WLAN DFS master device or a slave device. The WLAN DFS device 811 can be a WLAN device in a vehicle 605, 607, 609, 611, and the device can perform the steps of method 700.
[0064] The WLAN DFS device 811 can include WLAN hardware 813 and a WLAN driver 815. The WLAN driver 815 can include a WLAN Tx / Rx controller 817, conventional WLAN DFS logic 819, and DFS action frame monitoring logic 821. The WLAN hardware can be configured to transmit or receive WLAN packets on one operating channel, including receiving DFS beacons from the DFS action frame beacon originating device 801.
[0065] The WLAN Tx / Rx controller 817 may be configured to demodulate and decode received WLAN packets and to encode and modulate the WLAN packets for transmission. The DFS action frame monitoring logic 821 may be configured to detect DFS beacons. If a DFS beacon is received, the DFS action frame monitoring logic 821 may authenticate the validity of the DFS beacon using a digital signature carried in the DFS beacon. If the DFS beacon is authenticated, the DFS action frame monitoring logic 821 may obtain information regarding one or more WLAN DFS channels used by nearby radars, one or more recommended WLAN DFS channels that the WLAN DFS device 811 can use as alternative channels, information regarding radar operating range, etc.
[0066] If the current operating channel is being used by a nearby radar, the conventional WLAN DFS logic 819 can be configured to switch to one of the recommended WLAN DFS channels obtained from the DFS beacon, or to a non-DFS channel if available. According to one embodiment, if the WLAN DFS device 811 is a WLAN DFS master device, the conventional WLAN DFS logic 819 can be configured to generate a message to be transmitted on the current operating channel to signal an associated slave device to switch from the current operating channel when a radar signal is detected on the operating channel through a DFS-CAC scan or a DFS-ISM scan. According to one embodiment, if the WLAN DFS device 811 is a WLAN DFS slave device, the conventional WLAN DFS logic 819 can be configured to select a new channel for WLAN operation when the device receives a message from an associated WLAN DFS master device to switch its current operating channel.
[0067] According to one embodiment, the DFS action frame beacon originating device 801 or the WLAN DFS device 811 may include a memory and a processing device. The memory may be a synchronous dynamic random access memory (DRAM), a read-only memory (ROM), or other type of memory, and may be configured to store code for implementing the functions of the WLAN driver 805 or 815. The processing device may be provided by one or more general-purpose processing devices, such as a microprocessor, a central processing unit, or the like. In an exemplary embodiment, the processing device may have a complex instruction set computing (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, or a processor implementing other instruction sets, or a processor implementing a combination of multiple instruction sets. The processing device may also have one or more special-purpose processing devices, such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), a network processor, or the like. To perform the operations and steps described herein, a processing device can be configured to perform the operations described herein in accordance with one or more aspects of the present disclosure.
[0068] Unless otherwise specified, terms such as "receive," "generate," "collate," "perform," "correct," "identify," or the like refer to actions and processes performed or implemented by computing devices that manipulate data represented as physical (electronic) quantities within their registers and memories, and convert it into other data that is also represented as physical quantities within their memory or registers or other such information storage, transmission or display devices.
[0069] The embodiments described herein also relate to an apparatus for performing the operations described herein. The apparatus may be specially configured for the required purpose or may comprise a general-purpose computing device that is selectively programmed by a computer program stored in the computing device. Such a computer program may be stored in a computer-readable non-transitory storage medium.
[0070] Certain embodiments may be implemented as a computer program product that may include instructions stored on a machine-readable medium. A general-purpose or special-purpose processor may be programmed with those instructions to perform the operations described above. A machine-readable medium may include any mechanism for storing or transmitting information in a form (e.g., software, processing application) readable by a machine (e.g., a computer). A machine-readable medium may include, but is not limited to, a magnetic storage medium (e.g., floppy disk), an optical storage medium (e.g., CD-ROM), a magneto-optical storage medium, a read-only memory (ROM), a random access memory (RAM), an erasable programmable memory (e.g., EPROM and EEPROM), a flash memory, or any other type of medium suitable for storing electronic instructions. A machine-readable medium may also be referred to as a non-transitory machine-readable medium.
[0071] The methods and illustrative embodiments described herein are not inherently linked to any particular computer or other apparatus. Various general-purpose systems may be used in accordance with the teachings described herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these systems will be apparent from the description above.
[0072] The above description is intended to be illustrative and not limiting. Although the present disclosure has been described with reference to certain illustrative embodiments, it is understood that the present disclosure is not limited to the described embodiments. The scope of the present disclosure should be determined in accordance with the following claims, along with the full scope of equivalents to which they are entitled.
[0073] As used herein, the singular indefinite and definite articles are intended to include the plural forms as well, unless the context clearly indicates otherwise. It is further understood that the terms "have," "having," "including," and / or "comprising," when used herein, identify the presence of a stated feature, whole, step, operation, element, and / or component, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or groups thereof. Similarly, the terms "first," "second," "third," "fourth," and the like, as used herein, are intended as labels to distinguish between different elements, and may not necessarily have a sequential meaning according to their numerical designation. Thus, the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting.
[0074] It should also be noted that in some alternative embodiments, the functions / acts described need not be performed in the order shown in the figures. For example, two figures shown in succession may in fact be performed substantially simultaneously or may sometimes be performed in the reverse order, depending on the functions / acts involved.
[0075] Although the acts of the methods have been described in a particular order, it should be understood that other acts may be performed between the acts described, that the acts described may be adjusted so that they occur at somewhat different times, or that the acts described may be distributed within a system such that the acts of a process occur at various intervals associated with the process.
[0076] Various units, circuits, or other components may be described or claimed as being "configured to" or "configurable to" perform a task or tasks. In this context, the phrase "configured to" or "configurable to" is used to imply structure by indicating that the unit / circuit / component includes structure (e.g., circuitry) that performs the task or tasks during operation. The units / circuits / components may thus be said to be configured to perform a task or to be configurable to perform a task even if the particular unit / circuit / component is not currently operating (e.g., not in an on state). A unit / circuit / component used with the words "configured to" or "configurable to" includes hardware such as circuits, memories that store executable program instructions to implement operations. Describing a unit / circuit / component as being "configured to" or "configurable to" perform one or more tasks is expressly intended to exclude the application of 35 U.S.C. § 112, paragraph 6 to the unit / circuit / component. Additionally, "configured to" or "configurable to" can include general purpose structure (e.g., general purpose circuitry) that is manipulated by software and / or firmware (e.g., an FPGA or a general purpose processor running software) to operate in a manner capable of performing a task of interest. "Configured to" can also include coordinating a manufacturing process (e.g., a semiconductor manufacturing facility) to create a device (e.g., an integrated circuit) that is adapted to implement or perform one or more tasks.It is expressly intended that "configurable to" does not apply to blank media, unprogrammed processors or unprogrammed general purpose computers, or unprogrammed programmable logic devices, programmable gate arrays, or other unprogrammed devices, unless accompanied by a programming medium that confers the capability to cause the unprogrammed device to be configured to perform the disclosed functions.
[0077] The foregoing description has been described with reference to specific embodiments for purposes of illustration. However, the above exemplary discussion is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Numerous modifications and variations are possible in light of the above teachings. These embodiments have been chosen and described in order to best explain the principles and their practical applications, so that others skilled in the art can best utilize these embodiments and various modifications that may be suitable for their respective intended uses. Thus, the present embodiments should be considered as illustrative and not restrictive, and the invention should not be limited to the details given herein, but may be modified within the scope of the appended claims and their equivalents.
Claims
1. 1. A method of operating a wireless local area network (WLAN) device, the method comprising: operating the WLAN device on a first dynamic frequency selection (DFS) channel of a plurality of DFS channels; scanning, by the WLAN device, the first DFS channel for the presence of a radar signal from a radar; receiving, by the WLAN device, assistance information obtained by one or more WLAN devices capable of scanning the first DFS channel, the assistance information indicating whether the first DFS channel is being used by the radar; in response to at least one of the scan detecting the presence of the radar signal on the first DFS channel or the aiding information being received indicating that the first DFS channel is being used by the radar, changing operation of the WLAN device from using the first DFS channel to a second DFS channel of the plurality of DFS channels; having Receiving the assistance information by the WLAN device comprises receiving the assistance information from a crowd-sourced database over a cellular network, the crowd-sourced database including a plurality of geo-tagged radar zones detected by a plurality of the WLAN devices capable of scanning the first DFS channel; a geotagged radar zone of the plurality of geotagged radar zones having a geographical area in which an operating radar is detected by a WLAN device of the plurality of WLAN devices capable of scanning the first DFS channel, and one or more DFS channels of the plurality of DFS channels detected as being in use by an operating radar in the geographical area; The method further comprises transmitting, by the WLAN device, a geographical position of the WLAN device to the crowdsourcing database, the received aiding information comprising a received geotagged radar zone of the plurality of geotagged radar zones, the received aiding information indicating that the radar is operational near the geographical position of the WLAN device; The method further includes changing a DFS channel of a second WLAN device to a DFS channel different from the first DFS channel when the radar changes its operating DFS channel. method.
2. the received aiding information indicating that the first DFS channel is being used by the radar comprises information indicating that the first DFS channel is the same as the one or more DFS channels detected as being used by a radar operating in a geotagged radar zone among the plurality of geotagged radar zones. The method of claim 1.
3. the aiding information is received from a locally stored database, the locally stored database including a plurality of geotagged radar zones previously detected by the WLAN device; The method of claim 1.
4. and scanning the first DFS channel for the presence of the radar signal by the WLAN device includes receiving a message from the second WLAN device indicating that the second WLAN device has detected the presence of the radar signal on the first DFS channel. The method of claim 1.
5. 1. A wireless local area network (WLAN) device, the WLAN device comprising: a WLAN interface configured to operate the WLAN device on a first dynamic frequency selection (DFS) channel of a plurality of DFS channels; A processing device; having The processing device comprises: scanning the first DFS channel for the presence of a radar signal from a radar; receiving aiding information obtained by one or more WLAN devices capable of scanning the first DFS channel and indicative of whether the first DFS channel is being used by the radar; switching the first DFS channel used for WLAN operations to a second DFS channel of the plurality of DFS channels in response to at least one of the scan detecting the presence of the radar signal on the first DFS channel or the aiding information being received indicating that the first DFS channel is being used by the radar; It is structured as follows: The aiding information is received from a crowd-sourced database via a cellular network, the crowd-sourced database including a plurality of geo-tagged radar zones detected by a plurality of the WLAN devices capable of scanning the first DFS channel; a geotagged radar zone of the plurality of geotagged radar zones having a geographical area in which an operating radar is detected by a WLAN device of the plurality of WLAN devices capable of scanning the first DFS channel, and one or more DFS channels of the plurality of DFS channels detected as being in use by an operating radar in the geographical area; The processing device is further configured to transmit a geographical position of the WLAN device to the crowdsourcing database, the received aiding information comprising a received geotagged radar zone of the plurality of geotagged radar zones, the received aiding information indicating that the radar is operational near the geographical position of the WLAN device; When the radar changes its operating DFS channel, the DFS channel of the second WLAN device is changed to a DFS channel different from the first DFS channel. WLAN devices.
6. the received aiding information indicating that the first DFS channel is being used by the radar comprises information indicating that the first DFS channel is the same as the one or more DFS channels detected as being used by a radar operating in a geotagged radar zone among the plurality of geotagged radar zones. The WLAN device of claim 5.
7. the aiding information is received from a locally stored database of the WLAN device, the locally stored database including a plurality of geotagged radar zones previously detected by the WLAN device; The WLAN device of claim 5.
8. the processing device configured to scan the first DFS channel for the presence of the radar signal, the processing device further configured to receive a message from the second WLAN device, the message indicating that the second WLAN device has detected the presence of the radar signal on the first DFS channel. The WLAN device of claim 5.
Citation Information
Patent Citations
Radio communication device, radio communication method and radio communication system
JP2015211263A
Method and device related to direct adaptive control of dynamic channel selection band in wireless network
JP2017063404A
Channel availability coordination for wi-fi and unlicensed bands using radio access network
US20170094651A1
System, method, and apparatus for setting device geolocation via location proxies
US20170245280A1
Over the air signaling of dynamic frequency selection (DFS) operating parameters to client devices
US20180192422A1
