Silicon Labs
|
Silicon Labs Community Silicon Labs Community
  • Products
    1. 8-bit MCU
    2. 32-bit MCU
    3. Bluetooth
    4. Proprietary
    5. Wi-Fi
    6. Zigbee & Thread
    7. Z-Wave
    8. Interface
    9. Isolation
    10. Power
    11. Sensors
    12. Timing
  • Development Tools
    1. Simplicity Studio
    2. Third Party Tools
  • Expert's Corner
    1. Announcements
    2. Blog
    3. General Interest
    4. Projects
How to Buy
English
  • English
  • 简体中文
  • 日本語
//
Community // Blog

Tech Talks Blog: Wireless Coexistence

06/164/2020 | 04:58 PM
May Ledesma
Employee

Level 5


In this Tech Talk session, Kris Young, Field Applications Engineer for Silicon Labs, talked about the increasing challenges in wireless coexistence, its impacts on IoT application, and how Silicon Labs manage and offer built-in support for solving these challenges. Click here to watch the complete webinar and register now for future Tech Talks. Here are some key points from Kris’ session.

The Wireless Coexistence Challenge

What challenges exist in wireless coexistence? We have an ISM band at 2.4 GHz that’s very heavily used mostly because of different wireless protocols that share or coexist in the same band: Wi-Fi, Bluetooth, and IEEE 802.15.4 (Zigbee and Thread).

Although these wireless protocols have different modulation schemes, channel frequencies, and bandwidths, they all overlap when co-located, making a signal from one protocol sounds like noise interference to the other protocol. This causes problems in receiving messages between protocols because if the desired received signal is weaker than the noise, the radio is then unable to receive messages properly.

In the past, wireless devices seem to work even without specifically addressing coexistence issues. Unfortunately, ignoring the issues does not work anymore because of the following trends:

  • Greater device integration and radio colocation
  • Increased Wi-Fi transmit power (+30dBm)
  • Larger throughput needed for Wi-Fi streaming

Coexistence Impacts

Looking further on the impacts of coexistence in IoT device development, we’ve determined two categories:

  • Co-Channel – As far as IoT is concerned, IoT receivers are blocked if the Wi-Fi interference exists in the same channel and is stronger at the receiver than the signal being received from the remote IoT device. Also, Zigbee uses Clear Channel Assessment (CCA) to test the channel before transmit; and transmit is blocked with energy detection > -75 dBm per 802.15.4 specifications.
  • Receiver Blocking/Selectivity – issues exist even when protocols are not on the same channel. For instance, even when Wi-Fi and IoT devices are on different channels, the Wi-Fi energy is still in-band for the LNA, AGC, Mixer, etc. because 2.4 GHz IoT RX sensitivity is being degraded by high amplitude 2.4GHz Wi-Fi. Multiprotocol gateways present a different issue – high power 2.4 GHz Wi-Fi TX in the same enclosure as IoT is difficult to isolate.

Coexistence Issues

  • For End Devices – this issue can be clearly illustrated with a use case of a Zigbee security system with battery-powered sensors. In this case, Wi-Fi is co-located within radio range, and the traffic is used for streaming videos. The effect on the customer is manifested through delayed or missing reports as well as reduced battery life. This results in a high rate of retries and latency due to CCA failures. We recommend an Unmanaged Coexistence strategy to mitigate this issue.
  • For Gateways – in a use case wherein Zigbee, Bluetooth, and Wi-Fi coexist in a small form factor, and the device is used as a Wi-Fi Access Point and as a home IoT gateway simultaneously (e.g., communicating with sensors), the effect to the customer is demonstrated through poor command responsiveness, delayed or missing Zigbee reports, dropped Bluetooth connections, and reduced battery life on Zigbee devices due to retries. We recommend deploying both an Unmanaged Coexistence and Managed Coexistence strategies to solve these issues.

Improving Coexistence

  • Unmanaged – a key value of this strategy is frequency separation. This means selecting a Zigbee channel as far from the 2.4 GHz channel as possible and using a Bluetooth Low Energy channel map. Another scheme in this setup is antenna isolation, where you provide as much isolation between IoT and 2.4 GHz Wi-Fi antennas as possible. If IoT and 2.4 GHz are in separate physical units, it is recommended to implement install guidelines for minimum clearance. Another idea is to use a 20 MHz Wi-Fi bandwidth (avoid 40 MHz) and rely on protocol Retry Mechanisms.
  • Managed – this setup is recommended in addition to (not in place of) the unmanaged coexistence techniques if you have a device that has all the radios built into it. The strategy calls for the separation of radio activity in time, which requires coordination between the radios. We use Packet Traffic Arbitration (PTA) to accomplish this. PTA is a recommendation provided in 802.15.2: “Coexistence of Wireless Personal Area Networks with Other Wireless Devices Operating in Unlicensed Frequency Bands.” PTA establishes that the IoT device asserts REQUEST and optionally asserts the PRIORITY signal and that if the Wi-Fi device can grant airtime, it asserts the GRANT signal back to the IoT device(s). The Wi-Fi device is expected to stop transmitting before asserting GRANT and is expected not to begin a new transmission while GRANT is asserted. Thus, when the IoT transaction is completed, the IoT device de-asserts REQUEST, and the Wi-Fi device follows by de-asserting GRANT.

Get Additional Documentation and Support

Either you want to increase your knowledge of Zigbee Coexistence with Wi-Fi, or Bluetooth Coexistence with Wi-Fi, there are several ways to get started with boosting your understanding of Silicon Labs' wireless coexistence strategies. To get answers for more specific and/or complex questions, and access our Training Resources, Community, Forum, and Knowledge Base Articles, visit our Tech Support page.

  • Wireless
  • Blog Posts

Tags

  • Wireless
  • High Performance Jitter Attenuators
  • EFR32FG22 Series 2 SoCs
  • EFR32MG21 Series 2 SoCs
  • Security
  • Bluegiga Legacy Modules
  • Zigbee SDK
  • ZigBee and Thread
  • EFR32BG13 Series 1 Modules
  • Internet Infrastructure
  • Sensors
  • Wireless Xpress BGX13
  • Blue Gecko Bluetooth Low Energy SoCs
  • Z-Wave
  • Micrium OS
  • Blog Posts
  • Low Jitter Clock Generators
  • Bluetooth Classic
  • Makers
  • Flex SDK
  • Tips and Tricks
  • timing
  • Smart Cities
  • Smart Homes
  • IoT Heroes
  • Reviews
  • RAIL
  • Simplicity Studio
  • Tiny Gecko
  • EFR32MG22 Series 2 SoCs
  • Mighty Gecko SoCs
  • Timing
  • Temperature Sensors
  • Blue Gecko Bluetooth Low Energy Modules
  • Ultra Low Jitter Clock Generators
  • General Purpose Clock Generators
  • EFR32BG22 Series 2 SoCs
  • Industry 4.0
  • Giant Gecko
  • 32-bit MCUs
  • Bluetooth Low Energy
  • 32-bit MCU SDK
  • Gecko
  • Microcontrollers
  • Jitter Attenuators
  • EFR32BG21 Series 2 SoCs
  • News and Events
  • Industrial Automation
  • Wi-Fi
  • Bluetooth SDK
  • Community Spotlight
  • Clock Generators
  • Biometric Sensors
  • General Purpose Jitter Attenuators
  • Giant Gecko S1
  • WF200
  • Flex Gecko
  • Internet of Things
  • 8-bit MCUs
  • Wireless Jitter Attenuators
  • Isolation
  • Powered Devices
  • Power

Top Authors

  • Avatar image Siliconlabs
  • Avatar image Jackie Padgett
  • Avatar image Nari Shin
  • Avatar image lynchtron
  • Avatar image deirdrewalsh
  • Avatar image Lance Looper
  • Avatar image lethawicker

Archives

  • 2016 January
  • 2016 February
  • 2016 March
  • 2016 April
  • 2016 May
  • 2016 June
  • 2016 July
  • 2016 August
  • 2016 September
  • 2016 October
  • 2016 November
  • 2016 December
  • 2017 January
  • 2017 February
  • 2017 March
  • 2017 April
  • 2017 May
  • 2017 June
  • 2017 July
  • 2017 August
  • 2017 September
  • 2017 October
  • 2017 November
  • 2017 December
  • 2018 January
  • 2018 February
  • 2018 March
  • 2018 April
  • 2018 May
  • 2018 June
  • 2018 July
  • 2018 August
  • 2018 September
  • 2018 October
  • 2018 November
  • 2018 December
  • 2019 January
  • 2019 February
  • 2019 March
  • 2019 April
  • 2019 May
  • 2019 June
  • 2019 July
  • 2019 August
  • 2019 September
  • 2019 October
  • 2019 November
  • 2019 December
  • 2020 January
  • 2020 February
  • 2020 March
  • 2020 April
  • 2020 May
  • 2020 June
  • 2020 July
  • 2020 August
  • 2020 September
  • 2020 October
  • 2020 November
  • 2020 December
  • 2021 January
Silicon Labs
Stay Connected With Us
Plug into the latest on Silicon Labs products, including product releases and resources, documentation updates, PCN notifications, upcoming events, and more.
  • About Us
  • Careers
  • Community
  • Contact Us
  • Corporate Responsibility
  • Privacy and Terms
  • Press Room
  • Investor Relations
  • Site Feedback
  • Cookies
Copyright © Silicon Laboratories. All rights reserved.
粤ICP备15107361号
Also of Interest:
  • Bring Your IoT Designs to Life with Smart,...
  • IoT Hero CoreTigo Drives New Wireless Standard...
  • A Guide to IoT Protocols at Works With...