Market Research for the Commercial Use of Bluetooth Low-Energy Wakeup ReceiversI

of one

Risks of Bluetooth Low-Energy Wakeup ReceiversI

Key Takeaways


Performance losses and false wake-ups are risks associated with WRX technology in its current use. Performance losses are mainly caused by an extremely low power design, which leads to high energy costs. False wake-ups lead to notable energy wastage on the node.

Performance Losses

  • One of the risks facing wake-up receiver technology in its current application is performance losses. Performance losses are caused by an extremely low-power design, indirectly leading to rising energy costs.
  • Thus, finding the right balance when using the technology is vital. WRX technology helps in reducing the overall power consumption of the system.
  • The technology also reduces the delay in frame delivery to the target node, which is especially important in delay-sensitive applications particularly in Industry 4.0. WRX technology uses a receiver with a low power consumption such that it can be kept active all the time.
  • However, the performance loss is an inherent risk if the technology is not designed appropriately. In this regard, limiting bitrate, limiting sensitivity, and modulation techniques must be carefully applied in the design phase of the technology.

False Wake-Ups

  • Another risk associated with WRX technology is false wake-ups. The technology uses energy detection architectures to reduce energy consumption.
  • However, any signal transmitted at the proper frequency can cause a false wake-up of the receivers. The false wake-ups lead to notable energy wastage on the node.
  • The overall effect of the false wake-ups is a degradation of the WRX’s performance. They also reduce battery life.
  • Currently, most of the existing WRX technology architectures are deficient in false and poor wake-up filtering. Thus, they are vulnerable to this risk.
  • To counter the risk, a WRX should have ample local processing to differentiate a wake-up event from interference without using the node’s main processor.

Did this report spark your curiosity?