Devices, systems and methods for dynamically allocating portions of channels to different communication protocols

A method can include selecting a channel from a network operating according to a first protocol (e.g., an IEEE 802.11ax channel). Designating at least one portion of the channel as a shared resource unit (RU) and another portion as a dedicated RU. When an associated device is communicating according to a different protocol (e.g., a Bluetooth standard), allocating frequencies of the shared RU for use by the associated device and allocating the dedicated RUs for use by the network operating according to the first protocol.

TECHNICAL FIELD

The present disclosure relates generally to wireless systems, and more particularly to wireless systems having collocated devices that can communicate according to different protocols that can share a bandwidth.

BACKGROUND

FIG.11is a diagram showing the allocation of bandwidth between collocated devices according to a conventional approach. One device can operate according to a 2.4 GHz IEEE 802.11 standard (WLAN 2.4) while the other device can operate according to a Bluetooth (BT) Standard and/or BT Low Energy Standard (BT/BLE). WLAN 2.4 can operate on a number of different overlapping 22 MHz channels, shown as CH1to CH14. CH1at one end of the WLAN spectrum can have a center frequency of 2.412 GHz. CH14at the other end of the WLAN spectrum can have a center frequency of 2.484 GHz. BT/BLE can adaptively frequency hop (AFH) between 2.402 GHz and 2.481 GHz on 1 or 2 MHz channels. Accordingly, channels CH1to CH14can overlap BT/BLE channels. As a result, WLAN 2.4 channels can interfere with BT/BLE operations.

For example, as shown inFIG.11, if a WLAN 2.4 device is operating on channel CH9, it can interfere with a corresponding range of the BT/BLE spectrum (shown as UNAVAILABLE). As a result, BT/BLE operations can exclude the bands corresponding to CH9, restricting the number of channels for AFH operations. This can reduce the performance of BT/BLE operations.

Further, whileFIG.11shows 20 MHz IEEEE 802.11 channels, WLAN can also divide a spectrum into 40 MHz channels. In such cases, the use of one WLAN channel can interfere with a large number of BT/BLE channels, greatly restricting BT/BLE operations.

It would be desirable to arrive at some way of improving the availability of transmission spectra for collocated devices that have overlapping transmission spectra.

DETAILED DESCRIPTION

According to embodiments, systems and devices can operate according to different wireless protocols having overlapping bandwidths. A first protocol can include a number of channels, each divisible into multiple portions, or Resource Units (RUs). RUs can be designated as “shared” RUs which can be used by both protocols. For example, when a second protocol is active, the frequencies of a shared RU can be available for transmissions according to the second protocol, but not available for transmissions according to the first protocol. However, when the second protocol is not active, the RU can return for use by the first protocol.

In some embodiments, systems and devices can include first circuits operating according to the IEEE 802.11ax standard and second circuits operating according to a second, different protocol. The second protocol can support shorter range transmissions than the IEEE 802.11ax standard. The IEEE 802.11ax channels can be divided into two or more RUs, which can be designated as shared RUs or non-shared RUs. While operations are occurring according to the second protocol, the shared RU is excluded from use by IEEE 802.11ax operations. However, when second protocol operations have ended, the shared RU can be used for IEEE 802.11ax operations. In some embodiments, RUs may also be non-shared. Non-shared RUs can be excluded from second protocol operations.

In some embodiments, a device can include collocated IEEE 802.11ax and Bluetooth (BT/BLE) circuits. RUs of channels can be designated as shared RUs. When BT/BLE circuits are active, they can have access to BT/BLE channels within the shared RU. However, when BT/BLE circuits are not active, the shared RU can be used by the IEEE 802.11ax circuits.

In the various embodiments below, like items are referred to by the same reference characters, but with the leading digit(s) corresponding to the figure number.

FIGS.1A and1Bare a diagrams showing RU sharing according to an embodiment. It is assumed that the bandwidth of the channel100A/B can be shared by two different protocols. A channel100A/B can occupy a range of frequencies and can be divided into a number of RUs102. Each different RU can enable communication with a separate device. In the embodiment shown, channel100A can be divided into four RUs102, but this should not be construed as limiting. A channel100A/B could be divided into a fewer or greater number of RUs according to the communication standards/protocols being used.

FIG.1Ashows RU allocation when a first protocol is active, but the second protocol is not active. Because the second protocol is not active, all RUs102can be allocated to the first protocol (shown as WLAN).

FIG.1Bshows RU allocation when a first protocol is active, but the second protocol is active. InFIG.1Bit is assumed that RUs labeled RU1and RU2have been designated as shared RUs102′. The frequencies of such shared RUs102′ are available for use by the second protocol but excluded for use by the first protocol.

In some embodiments, a first protocol can be operated according to the IEEE 802.11ax standard. A second protocol can be any suitable protocol. In some embodiments, a second protocol can support a shorter transmission range than the IEEE 802.11ax standard. In particular embodiments, a second protocol can be operations according to a BT/BLE standard.

FIG.2is a block diagram of a combination system204according to an embodiment. A combination system204can include different communication circuits collocated in a same system. A combination system204can include control circuits206, first communication circuits208, second communication circuits210, and radio circuits212. First communication circuits208can be wireless communication circuits compatible with a first protocol. First communication circuits208can include an RU control section208-0, which can control when RUs are not available for first communication circuits204when communicating according to the first protocol.

Second communication circuits210can be wireless communication circuits compatible with a second protocol. Second communication circuits210can be associated with first communication circuits208. Second communication circuits210can include a channel list210-0and channel selector210-1. A channel list210-0can be a list of channels used in a second communication protocol. It is understood that channels of the second protocol are not the same as channels of the first protocol. Channel selector210-1can select channels from the channel list210-0during communications according to the second protocol. It is understood that in other embodiments second communication circuits210can be located remotely from first communication circuits208.

Control circuits206can provide control signals to first and second communication circuits208and210. Control circuits206can include a channel map206-0which includes data correlating channels of a first protocol to those of a second protocol. Control circuits206can control operations between first and second communication circuits208and210. For example, control circuits206can indicate to first communication circuits208when second communication circuits210are active, resulting in second communication circuits208excluding shared RUs from use. Further, control circuits206can also indicate to second communication circuits210when channels should not be used, based on channels used by first communication circuits208.

Radio circuits212can transmit data according to the first and second protocols. In particular embodiments, radio circuits212can enable the first and second communication circuits to share a common band (e.g., 2.4 GHz).

In particular embodiments, first communication circuits208can be IEEE 802.11ax compatible circuits and second communication circuits210can be BT/BLE compatible circuits.

FIGS.3A to3Care diagrams showing channel divisions that can be included in embodiments.FIG.3Ashows a first channel-RU arrangement. A channel300A can have a bandwidth of about 20 MHz and can be subdivided into RUs of various sizes. Example302-0shows nine RUs, each of about 2 MHz. Example302-1shows four RUs of about 4 MHz and one of about 2 MHz. Example302-2shows two RUs of about 8 MHz and one of about 2 MHz. It is understood, the various RUs could be mixed (e.g., one 8 MHz RU, one two MHz RU, and two 4 MHz RUs).

FIG.3Bshows divisions for a channel300B of about 40 MHz. The RU sizes are understood from the descriptions ofFIG.3A. InFIG.3B, as shown by example302-3a channel division can include one or two 20 MHz RUs.

FIG.3Cshows divisions for a channel300C of about 80 MHz and can include RUs of the sizes shown inFIG.3B, as well as RUs of 40 MHz.

According to embodiments, a system can include a protocol which can select a channel (300A,300B,300C). The selected channel can be divided into different RUs, as understood fromFIGS.3A to3C. It is understood that any or all RUs can overlap with the bandwidth of another protocol. Any such overlapping RU can be selectively designated as a shared RU. When the second protocol is active, frequencies of the shared RU are not used by the first protocol, and thus made available for the second protocol. In addition, some RUs can be designated as non-shared RUs. The frequencies of non-shared RUs can be excluded from use by the second protocol.

In particular embodiments, channels (300A,300B,300C) and RUs (302-0to -4) can be those specified in the IEEE 802.11ax standard.

FIG.4Ais a block diagram of a combination device404according to another embodiment. In some embodiments, combination device404can be one particular implementation of the system shown inFIG.2as204. A combination device404can include WLAN communication circuits408, BT communication circuits410, controller406, radio circuits412, and input/output (I/O) circuits422. BT communication circuits410can be circuits compatible with a BT standard, and can include BT control circuits410-0and BT baseband circuits410-1. BT communication circuits410can operate in a 2.4 GHz band. BT control circuits410-0can control BT operations, including the formation and transmission of BT packets. BT control circuits410-0can include a channel list414and channel hop control416. Channel hop control416can control which channels are used in an adaptive frequency hopping (AFH) operation during BT transmissions. Channel list414can include information on BT channels, and can indicate which BT channels can be included and which channels can be excluded from AFH operations.

WLAN communication circuits408can be WLAN circuits that can operate according to the IEEE 802.11ax and possibly other IEEE 802.11 standards. WLAN communication circuits408can include WiFi control circuit408-0and WiFi media access control (MAC) circuits408-1. WLAN circuits can operate in the 2.4 GHz band, and optionally, other IEEE 802.11 bands (e.g., 5 GHz, 6 GHz). WiFi control circuit408-0can include a channel list420-0and channel selection section420-1for selecting channels for WLAN communications. Channel list420-0can include channels available for WLAN transmission, including those for use in the 2.4 GHz band (which can overlap BT channels). Channel list420-0can also track RUs of selected channels, including how the RUs are allocated, as described for other embodiments herein and equivalents (i.e., available for BT use or not).

Controller circuits406can control operations of a combination device404, including determining when BT communication circuits410are active, and relaying such information to WLAN communication circuits408. In response, WLAN communication circuits408can exclude RUs designated as shared RUs from WLAN operations. In some embodiment, controller circuits406can include channel-to-channel map data406-0, to determine [s]how BT channels map to WLAN channels and vice versa. In some embodiments, controller circuits406can indicate to BT communication circuits410BT channels to be excluded (e.g., BT channels corresponding to a WLAN RU that is not to be shared). In response, BT control communication circuits410can update channel list414accordingly. In the embodiment shown, controller circuits406can include one or more processors418-0and a memory system418-1. However, any other suitable circuits could be employed, including application specific logic, both fixed or programmable.

Radio circuits412can take the form of any of those described herein or equivalents.

I/O circuits422can enable control of combination device404from sources external to the combination device404. I/O circuits422can include circuits that enable communication with the combination device404according to any suitable method. Such methods can include any of various serial data communication standards/methods including but not limited to: serial digital interface (SDI), universal serial bus (USB), universal asynchronous receiver transmitter (UART), I2C, or I2S.

FIG.4Bis a diagram showing operations according to an embodiment. Such operations can be executed by the systems devices shown herein, and equivalents.FIG.4Bis a timing diagram showing WLAN channels428and BT/BLE channels430. WLAN channels428can be 20 MHz channels according to the IEEE 802.11ax standard, and so are divisible into RUs. Further, such RUs can be designated as shared RUs as described herein and equivalents. BT/BLE channels430can overlap various WLAN channels428.

FIG.4Bshows one particular configuration in which WLAN channel9(CH9) can have five RUs (e.g., four 4 MHz RUs and one 2 MHz RU). Four RUs can be designated as shared RUs402′. Consequently, during BT/BLE operations, the corresponding BT/BLE channels, shown as424, can be unavailable for WLAN operations but available for BT/BLE operations. In the embodiment shown, RU402is designated as not shared (i.e., dedicated to WLAN), thus the corresponding BT/BLE channels, shown as426, can be excluded from BT/BLE operations.

It is understood that any of the channels shown inFIG.4Bcan have RUs of any suitable size designated as shared RUs or dedicated RUs (not for BT/BLE use). Further, whileFIG.4Bshows a 20 MHz channels, the same operations can occur for channels of any other size (e.g., 40 MHz, as shown inFIG.3Bor 80 MHz, as shown inFIG.3C).

FIG.5is a block diagram of a combination device504according to another embodiment. In some embodiments, combination device504can be one particular implementation of either of those shown asFIG.2or4A. A combination device504can include a BT section510and a WLAN section508. A BT section510can include a controller506, BT control circuits510-0, media control circuit530, and first I/O circuits522-0in communication with one another over a bus532. A controller506can control operations of combination device504, including operations within WLAN section508. In some embodiments, a controller506can issue control signals over bus532that can be transmitted to WLAN section508over bridge534via media control circuits530. A controller506can include one or more processors518-0and a memory system518-1. A controller506can designate an RU as a shared RU or dedicated RU, as described herein and equivalents. A controller506can also indicate to WLAN section508when a BT section510is, or will be, active. This can enable WLAN section508to exclude shared RUs from WLAN operations in response to such indications.

BT control circuits510-0can include circuits for performing functions according to one or more BT standards, including determining BT channels514and controlling channel hopping516among the BT channels. BT control circuits510-0can also include channel quality circuits517. Channel quality circuits517can determine a quality of BT channels. Based on such quality data, BT channel can be excluded from an AFH operation. In particular embodiments, quality data can include a bit error rate for each channel. BT control circuits510-0can control BT radio512-0to operate according to one or more BT protocols.

Media control circuits530can communicate with WLAN section508over bridge534to coordinate communications between BT and WLAN sections (510,508), including messages to WLAN section508that indicate when BT circuits are/will be active. First I/O circuits522-0can enable communication with the combination device504according to any of the embodiments described herein or equivalents.

A WLAN section508can include IEEE 802.11ax circuits508-0, bridge control circuit534, WLAN control circuits536, and second I/O circuits522-1in communication with one another over a backplane538. IEEE 802.11ax circuits508-0can include circuits for performing functions according to the IEEE 802.11ax standard, as well as other IEEE 802.11 standards. As such, IEEE 802.11ax circuits508-0can divide channels into RUs using Orthogonal Frequency-Division Multiple Access (OFDMA). IEEE 802.11ax circuits508-0can also include WLAN quality circuits519, which can determine a quality of IEEE 802.11ax with respect to IEEE 802.11ax transmissions.

Multi-band radio circuits512-1can transmit and receive data on one or more WLAN bands (e.g., 2.4 GHz, 5 GHz). Media control circuit530can control data transfer operations between BT section510and WLAN section508over bridge534, including indicating channels selection and/or RU configurations. Second I/O circuits522-1can enable communication with the combination device504according to any of the embodiments described herein or equivalents, including communications with BT section510over bridge534. WLAN control circuits536can include channel control circuits520-0/1which can determine which channels are available for use by WLAN section508.

A combination device504can also include an antenna system540connected to BT radio circuits512-0and multi-band radio circuits512-1. Antenna system540can include one or more physical antennas, as well as switches for enabling different connections to such antennas.

FIG.6is a flow diagram of method650for controlling RUs according to an embodiment. A method650can include selecting a first protocol channel that is sub-dividable650-0. Such an action can include selecting a channel from a number of channels, each channel spanning a range of frequencies used by a protocol for communicating between two devices. The selected channel is dividable into portions (e.g., RUs), but method650should not be construed as being limited to any particular protocol. An RU can be selected for the channel650-1. Such an action can include selecting the RU according to any suitable criteria.

If a second protocol is not active (N from650-2), a method650can include the selected RU in transmissions according to the first protocol650-3. In contrast, if the second protocol is active (Y from650-2), a method650can exclude the selected RU from transmissions according to the first protocol650-3. Thus, frequencies of the RU can be available for transmissions according to the second protocol.

In the embodiment shown, if there is a restart, re-configuration or similar action (Y from650-5) a method650can return to650-0. Otherwise, a method650can return to650-2.

FIG.7is a flow diagram of method750for controlling RUs according to another embodiment. A method can include selecting an RU from an IEEE 802.11ax channel750-0. A method750can determine if the selected RU overlaps a BT spectrum750-1. Such an action can include determining if the RU overlaps the BT spectrum as indicated by a BT standard. However, such an action can also include determining if the RU overlaps a BT spectrum as modified by a device. That is, a BT spectrum may have already been modified to discard some BT channels due other criteria, such as bit error rate. This can result in a modified BT spectrum having fewer channels than that dictated by a standard. If an RU is composed of BT channels already determined as undesirable, the RU may not be selected as a shared RU.

If the selected RU is determined to overlap a BT spectrum (Y from750-1), a method750can designate, or not designate, the RU as a shared RU750-2. Such an action can include making such a determination based on any suitable method. As but one example, a quality of communications using frequencies of the RU can be used. However, in some embodiments, a method750may not include an action750-2(i.e., a selected RU can be automatically designated as a shared RU).

If an RU is designated as a shared RU (Y from750-2) a method750can determine if BT circuits are active750-3. Such an action can include determining if BT circuits are, or will be, transmitting and/or receiving over the BT spectrum, including portions that overlap the shared RU. If BT circuits are determined to be active (Y from750-3), the selected RU can be excluded from IEEE 802.11ax operations750-4. If BT circuits are not active (N from750-3) a method750can include the selected RU in IEEE 802.11ax operations750-6.

If an RU is not designated as a shared RU (N from750-2), the RU can be excluded from BT operations750-5. Such an action can include removing those BT channels corresponding to the selected RU from a BT channel hopping sequence. A method750then include the selected RU in IEEE 802.11ax operations750-6.

In the embodiment shown, if there is a restart, re-configuration or other such action (Y from750-7) a method750can return to750-0. Otherwise, a method750can return to750-3.

While embodiments can include the automatic designation of an RU as a shared RU, in some embodiment RUs can be selected based on quality determinations of WLAN and/or BT channels. One such embodiment is shownFIG.8.

FIG.8is a flow diagram of method850according to another embodiment. A method850can include selecting an IEEE 802.11ax channel850-0. One of multiple RUs of the channel can then be selected850-1. If the 802.11ax quality of the RU is above a predetermined level (Good from850-2), a method850can determine if the RU overlaps a BT spectrum850-5. If the selected RU overlaps the BT spectrum (Y from850-5), a quality determination for BT channels of the selected RU can be made850-6. If BT channels included in the frequencies of the RU are above a predetermined quality level (Good from850-6), a method850can designate the RU as a shared RU850-7. As a result, the selected RU can be excluded from IEEE 802.11ax operations when BT circuits are active. If BT channels of the RU are below a predetermined level (Poor from850-6), a method850can designate the RU as not shared850-8. As a result, BT channels corresponding to the not shared RU can be excluded from BT operations.

Once an RU has, or has not, been designated as a shared RU, a method850can determine if a last RU of the channel has been checked850-3. If a last RU of the channel has not been checked (N from850-3), a method850can proceed to a next RU of the channel850-4, and the various quality determinations can be repeated.

If an IEEE 802.11ax quality of the selected RU is below a predetermined level (Poor from850-2) or the RU does not overlap a BT spectrum (N from850-5), a method850can proceed to850-3.

While embodiments can include systems with various interconnected components, embodiments can include unitary devices which can selectively exclude RUs (i.e., portions of channels) used in operations of one protocol while another protocol is active. Such unitary devices can be advantageously compact single integrated circuits (i.e., chips).FIG.9Ashow one particular example of a packaged single chip combination device904. However, it is understood that a combination device according to embodiments can include any other suitable integrated circuit packaging type, as well as direct bonding of a combination device chip onto a circuit board or substrate.

While embodiments can include compact systems, such as integrated circuit packages, embodiments can also include systems employing multiple devices on multiple networks, with such networks operating according to a different protocol. One such embodiment is shown inFIG.9B.

FIG.9Bis a diagram showing a system970according to another embodiment. A system970can include a combination device904B, other WLAN devices, including an Access Point (AP)960and stations (STA)962, and other BT devices966. A combination device904B can include BT circuits (BT/BLE) and IEEE 802.11ax compatible circuits (shown as 802.11ax).

Combination device904B and WLAN devices (960,962) can form a Basic Service Set (BSS)964and can communicate with another according to the IEEE 802.11ax standard. Combination device904B and other BT devices966can form a BT piconet968and communicate with one another according to a BT standard.

According to any of the embodiments disclosed herein, and equivalents, a combination device904B can selectively exclude RUs from transmission on BSS964when BT/BLE circuits are active.

It is noted that while BSS964is shown with an AP960, in other embodiments, a combination device904B could be an AP. Similarly, combination device904B can operate as a slave and/or master in piconet968. In addition, while combination device904B can allocate RUs for BT/BLE circuits, in addition or alternatively, combination device904B can allocate RUs for other BT devices966. That is, a device associated with 802.11ax circuits can be BT/BLE circuits of a combination device and/or any or all of BT devices966.

Referring toFIGS.10A to10D, various other systems according to embodiments are shown in series of diagrams.FIG.10Ashows a handheld computing device1080A. Handheld computing device1080A can include a combination device1004A that can selectively exclude RUs of one protocol when another protocol is active.

FIG.10Bshows an automobile1080B according to an embodiment. Automobile1080B can have numerous sub-systems, including a communication subsystem1082. In some embodiments, a communication subsystem1082can enable an automobile to provide WiFi communications as well as enable other devices to pair to the system via Bluetooth. Communication subsystem1082can include a combination device1004B as described herein, or equivalents, serving as an access point, or part of an access point. In such an arrangement, combination device1004B can provide greater reliability for Bluetooth communications by selectively excluding possibly interfering RUs when Bluetooth communications are active.

FIG.10Cshows a router device1080C. Router device1080C can provide routing functions according to an IEEE 802.11ax protocol, while also enabling access via a closer range protocol (e.g., Bluetooth). Router device1080C can include a combination device1004C as described herein, or equivalents.

FIG.10Dshows a human interface device (HID)1080D. HID1080D can enable a person to interact or control other devices and should not be construed as limited to any particular HID. As but a few of many possible examples, HID1080D can control a computing system, manufacturing equipment or other systems. HID1080D can include a combination device1004D as described herein, or equivalents.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure aiding in the understanding of one or more of the various inventive aspects. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claims require more features than are expressly recited in each claim. Rather, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.