Wi-LE: Can WiFi replace Bluetooth? (2019) [pdf]
web.cs.ucla.edu
web.cs.ucla.edu
Look at what was necessary in this papet, thr IoT device pretends to be an access point to bypass all the layers in the stack that would filter out thr packet.
In this case they found a hack to workaround chipset/firmware limitations, but what other innovations havent happened due to inaccesible wireless physical layers?
Edit: one public, easy to digest source
https://www.reddit.com/r/RocketLeague/comments/8wvf9u/contro...
Regardless, it was the common perception at the time and thus affected the behavior of players.
It was not "the common perception". At best it was common among your peer group?
I played a LOT of Call of Duty and PS3. I never noticed input latency issues.
I think shooters where more popular on XBox because Halo took over a ton of the initial market share.
Caring about slight latency differences but then still using joysticks for a shooter seems rather weird.
For aiming in a shooter you have: keyboard < joystick < mouse or gyro.
For the military applications, the inertia of the thing you are aiming is important. In the most concrete example, think of swinging a rifle around to aim it. For a slightly more abstract think of aiming artillery.
It’s also part of why I can’t stand the trend of remove the headphone jack from devices.
They messed up the low power part by spec'ing a complicated baseband that had everything but the kitchen sink. Basically duplicated the USB spec but then added authentication and encryption on top of it. Which is even more complicated because everything runs over a unreliable frequency hopping rf channel. Frequency hopping messes with a lot of things.
Pretty complex.
I also have the one for WiFi (802.11-2012) and that is 2793 pages, so I'd say they are of roughly equal complexity.
It helps, of course, that the bandwidth required for VR streaming is fairly low using the Oculus link protocol.
There's a user experience benefit of the semantic separation between BT and Wifi; you move around and change SSID all the time with a portable device like a phone, which is for connecting to "other" things. Your BT connections "travel with you" as they are part of a personal area network.
There are weird boundary conditions (connecting to your friend's BT speaker, using wifi to cast to a chromecast or AppleTV) for which neither is perfect; frankly I think those wifi cases are more like the BT use case.
Just because the two use the same BT spectrum doesn't mean they should be unified.
Their first revision was 20-23 byte packets. The first thing anyone looks for when doing BLE is “how to send larger data”. BLE 4.2 and packet length extension helped this but it’s still pretty rough because you aren’t promised any specific MTU size by spec, just hope you can the packet size you need on connection.
I have a BLE product in the wild, but the amount of work I did to get around packet limitations was probably not worth it all said and done.
BLE is good for event based data transfer of flags and small data, but you outgrow that pretty damn quickly.
I have a new interest in BLE on account of myself recently becoming bluetooth enabled.
there are some technical means. one could use usb-ip[1] to bridge peripherals, for example. but few rise to the status of "flows", good well paved paths.
rec -p | nc -l 7777
nc 192.168.1.11 7777 | play -v 0.1 -As it is my Airpods ALMOST reach to the kitchen, just as I open the fridge they disconnect.
And they don't reconnect until I'm very close (though I suspect this is because they decide to connect to my phone).
Now that I think about it I should just join the meetings twice ...
Best way to be on calls. Need to walk around no problem. But can still see full screen when desired. Also can work if your home internet is spotty and you transfer to phones internet service.
Compared to 2.4/5G wifi Halow uses narrower bandwidths so has lower data rates but is still much higher than BLE. BLE can do up to ~2MBit with a 2MHz BW, 802.11ah can do up to ~8MBit with a 2MHz BW but can go up to 16MHz BW. Additionally 802.11ah supports MIMO, so it can also scale the bandwidth up with more antennas.
There are some other new fun features in 802.11ah namely TWT (target wake time) which is a powersaving method that solves a lot of the problems the article mentioned with powersaving in wifi.
Also, when the topic of Bluetooth comes up, many people complain that they have Bluetooth issues. Sadly, some manufacturers do not care about interoperability. Maybe I'm just lucky but I don't even recall when I would've had issues with Bluetooth. I use several devices practically every day (car, headphones, speakers).
The whole premise of the article is that this allows for efficient use of WiFi hardware to emulate BLE like behaviour.
Table 1.
Wi-Le Energy/packet: 84 uJ
Wi-Le Idle current: 2.5 uA
BLE Energy/packet: 71 uJ
BLE Idle current: 1.1 uA
You can see this from Figure 4 as well.So, like I wrote, Bluetooth consumes less battery.
In addition there are unsolved issues, which are likely to add to the overall consumption.
Edit: formatting
Line from right above the table so it could possibly go the other direction and use less.
And that's just the well-behaving honest Wi-Fi access points, not all the other crap on these frequencies that periodically destroys signal with interference.
And Bluetooth hops around these channels, dynamically selecting the one with less interference.
The product I made uses BLE to connect between device and mobile for things such as connecting the device to a wifi router. Otherwise the device connects to wifi normally.
Ultimately, your BT experience will vary depending on whether your device vendor has implemented advanced features, and done interoperability tests.
Lastly, BT could relatively easily move to the shiny new 6 GHz spectrum and make use of Very Low Power (VLP) assuming there is some spectrum harmonization done all over the world. https://docs.fcc.gov/public/attachments/DOC-363490A1.pdf