Bluetooth LE advertising congestion happens when there are too many Bluetooth devices in an area. As we will show, this rarely happens but with new Bluetooth technologies this situation is becoming more likely. We provide some ways to mitigate congestion.
Bluetooth LE advertising transmits periodically the period of which is configurable from typically 100ms to about 10 seconds.
If two Bluetooth devices happen to transmit at the same time, it’s like two people shouting at the same time. The signal is corrupted, the receiver can’t make sense of the signal and it is lost. This usually doesn’t matter because it’s likely the signal is seen the next time it is sent. The random advDelay in the above diagram ensures that the two sends don’t clash again. It’s very unlikely advertisers clash in the first instance because the transmit duration is very small compared to the advertising period. The above diagram isn’t to scale. Here’s an oscilloscope trace showing some real timing:
The advertising duration is very small, of the order of 1 to 2 ms (milliseconds). Advertising is also sent three times, on three different radio frequencies, so that if one is blocked, the radio signal might be heard on one of the others. All this means that advertising collisions rarely occur.
However, there are some newer Bluetooth protocols that as they are starting to roll out, are making collisisons more likely:
Bluetooth 5 advertising extensions – This allows advertising of more data, that takes longer than the typical 1 to 2 ms and hence increases congestion.
Bluetooth longer range – This transmits further thus effectively increasing the number of beacons advertising in a given area.
Bluetooth Mesh – This works by having relay beacons listen and re-transmit advertising, usually several times, to improve reliability.
Bluetooth direction finding – This also has longer advertising to send a constant tone extension (CTE) that is received by AoA hardware. However, of more affect is advertising more frequently. While beacons on assets used to advertise typically every second or longer, direction finding tends to use faster advertising to improve latency.
You can check how many devices are advertising by using a scanning app on Android. We recommend Nordic Semiconductor’s nRF Connect because it can decode the latest Bluetooth protocols. Use Android for full visibility because Apple made the poor design decision to obfuscate iBeacon advertising to coerce developers to only use the Apple iBeacon-specific APIs. Apple also hides devices’ MAC addresses making them more difficult to physically identify.
If you have a problem with congestion you might be tempted to increase the transmission power or advertise more often to increase the chances of being seen. However, this is counter-productive because you will be increasing congestion, especially if your devices are the main contributor to the congestion.
Lower the transmit power so that beacons cover a smaller area. You can fine tune this using nRF Connect to measure the distance you need rather than needlessly advertising further. This will also conserve battery life.
Increase the advertising period to make collisions less likely.
Increase the receiver scanning period to make detections more likely.
Seek out and remove unwanted devices advertising too frequently, such as fitness devices, smartphones, displays and even cars.
The paper describes the various types of communication:
The paper includes a description of Bluetooth LE including advertising and the different physical layer modes.
There’s an experimental evaluation of the new, more-robust, long-range radio mode when used in smart cities scenarios. The I2V scenario is evaluated, where reception is measured against variation in distance and vehicle speed. The I2P scenario is evaluated against interference from WiFi and classic (non LE) Bluetooth.
The researchers found an overall packet loss of 20–30%, regardless of mobility speed, compared to the static scenarios. The classic Bluetooth 4 mode was found to be more immune to coexistence with the WiFi protocol than any BLE 5.x mode. The researchers say this is because Bluetooth 5 extended advertisements 1) make use of more than one channel and 2) have longer data are both can cause more susceptibility to interference. Nevertheless, the updates introduced with Bluetooth 5 allow broadcasting over much longer distances.
The paper concludes the maturity and low cost of the technology could enable fast, easy deployment in smart cities compared to other solutions.
We previously mentioned how cost, battery life and second sourcing are the main advantages of Bluetooth over Ultra-Wideband (UWB). An additional, rarely mentioned, advantage is scalability.
Servers that process Bluetooth or Ultra-Wideband support a particular maximum throughout. The rate at which updates reach systems depends on the number of assets, how often they report and the area covered (number of gateways/locators). Each update needs to be processed and compared with very recent updates from other gateways/locators to determine an asset’s position.
For Bluetooth, updates tend to be of the order of 2 to 10 seconds but in some scenarios can be 30 seconds or more for stock checking where assets rarely move. Motion triggered beacons can be used to provide variable update periods depending on an asset’s movement patterns. This allows Bluetooth to support high 10s of thousands of assets without overloading the server.
For Ultra-Wideband, refresh rates tend to be of the order of hundreds of milliseconds (ms) thus stressing the system with more updates/sec. This is why most Ultra-Wideband systems support of the order of single digit thousands of assets and/or smaller areas. More frequent advertising is also the reason why the tags use a lot of battery power.
How does all this change with the new Bluetooth 5.1 direction finding standard? The standard was published in January 2019 but solutions have been slow to come to the market. The products that have so far appeared all have shortcomings that mean we can’t yet recommend them to our customers. Aside from this, in evaluating these products we are seeing compromises compared to traditional Bluetooth locating using received signal strength (RSSI).
Bluetooth 5.1 direction finding needs more complex hardware that, at least in current implementations, are reporting much more often. The server has to do complex processing to convert phase differences to angles and angles to positions thus supporting fewer updates/sec. Bluetooth direction finding is looking more like UWB in that cost, scalability and battery life are sacrificed for increased accuracy. Direction finding locators are currently x6 to x10 more costly than existing Bluetooth/WiFi gateways. Beacon battery life is reduced due to the more frequent and longer advertising. We are seeing Bluetooth 5.1 direction finding being somewhere between traditional Bluetooth RSSI-based locating and Ultra-Wideband in terms of flexibility vs accuracy.
Despite these intrinsic compromises, Bluetooth direction finding is set to provide strong competition to UWB for high accuracy applications. We are already seeing UWB providers seeking to diversify into Bluetooth to provide lower cost, longer battery life and greater scalability.
We are starting to see the first beacons and gateways that truly support Bluetooth 5 even though the standard was released in 2016. Up to recently, some have claimed to support Bluetooth 5 in that the internal hardware and software (SDK) was Bluetooth 5 capable but most, if not all, of the Bluetooth 5 features weren’t available.
Compatibility is dependent on smartphones supporting Bluetooth 5 that has also only come to fruition with recent phone models. Most Android smartphones manufactured in the last few years use Android 10 or Android 11 that has Bluetooth 5 software support. However, the Bluetooth chip inside the smartphone also needs to support Bluetooth 5. On iOS, all including and after iPhone 8/8 Plus/iPhone X support Bluetooth 5.
Furthermore, there’s also the complication that Smartphones claim to be Bluetooth 5 capable but might not support many of the optional features. One way to test which features are supported is to use the Nordic Semiconductor nRF Connect app. Here’s an example from the ‘Device Information’ section of the app running on a Pixel 3a XL:
We now have the INGICS iGS03E Bluetooth to Ethernet gateway in stock. This differs to the iGS02E in that it includes Power over Ethernet (PoE) without having to have an external PoE splitter.
Gateways look for Bluetooth LE devices and sends their advertising on to a server via TCP, HTTP(S) or MQTT including AWS IoT. If you use with sensor beacons, this provides a quick and easy way to provide for IoT sensing.
The iGS03E is one of the first gateways to also support Bluetooth 5 in Long Range mode (LE Coded PHY), although very few advertising devices support this yet.
We have a new rugged, UV-resistant, waterproof (IP68) sensor beacon, the AC-BLE-T110G in stock.
This is the first beacon we know of that supports Bluetooth 5 Long Range Coded PHY. While many beacons mention Bluetooth 5 in their specification and a Bluetooth 5 SDK has been used in their development, they only transmit Bluetooth 4.2 advertising. This beacon is the first to support Bluetooth 5 Long Range Coded PHY to achieve a range up to 200m with compatible gateways and smartphones.
This beacon can also be set to detect motion with a user defined threshold (mg) and duration (ms) which sends an alternative iBeacon id, a configurable number of times, instead of normal advertising.
Martin covered scanning, GATT, how to maximise data rates, speed vs reliability and using different PHY for enhanced range or data rates. The second part of the talk covers Bluetooth Mesh and proxy nodes.
One thing not mentioned in the slides, to be careful of, is that connection via a proxy node is relatively slow because it’s limited by the GATT connection. Proxy nodes are good for controlling (sending small amounts of data into) a Bluetooth Mesh but poor if you want to use the connected Android device as a gateway for all outgoing data.
There’s a new virtual Bluetooth Developer Meetup arranged for 15th October 2020. The first event will include talks from experienced Bluetooth developers from Google, Samsung, Foundries.IO and Bluetooth SIG.
The Bluetooth SIG has recently released a 2020 Bluetooth® Market Update identifying new trends and forecasts from ABI Research and other analyst firms.
The use of Bluetooth for location is expected to achieve 32% compound annual growth (CAGR):
Obviously, these and other numbers in the report were analysed prior to the coronavirus crisis.
For Bluetooth Mesh, 90% of end-product Bluetooth® mesh qualifications are lighting focused. As with the introduction of iBeacon, which initially focused on marketing messages, the wider capabilities and opportunities are initially not being fully exploited. Part of the problem is that the standard models that come with Bluetooth Mesh are more lighting focused because the standard was driven by individuals from the lighting industry. Custom models, such used by our SensorMesh™, are possible but take more effort.