-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Paper discussion 17a: Revisiting Software Defined Radios in the IoT Era #113
Comments
Review Type: Skim Problem Being Solved Contributions |
Reviewer: Niko Reveliotis Problem Being Solved Main Contributions
|
Reviewer: Jacob Cannizzaro Problem: Software radio was once seen as the future of radio technology. They are programmable, easily updateable to new radio technologies, and can simultaneuously read multiple types of wireless communications.The problem with them is that to optimize throughput for different wireless technologies adds a lot of cost that made it more feasible to just optimize hardware of each individual technology. Many IoT devices using many of these technologies at once causes current multi-technology gateways to experience collisions of radio waves from different devices that can be very hard or impossible to decode which leads to a loss in throughput as well as excess battery drain. Main Contributions: This paper introduces GalioT, a framework for a software multi-technology gateway that can handle concurrent decoding of multiple wireless technologies at once using cloud technologies. The prototype in this paper can handle Bee, Z-Wave, and LoRa wireless technologies, three of the most popular used in IoT devices everywhere. It is shown throughout that because IoT devices don't have high needs for throughput in most cases, and can deal with high latency bounds, software radios are enough for their low power needs. Whereas achieving the highest possible throughputs on any one technology with software radios is expensive, having one that can achieve results good enough for the IoT devices is actually cheaper than any existing multi-technology gateway. Throughput is shown to increase on average by 745.96%, fully supporting the goal of the paper. This technology is amazing because not only is it cheaper and more efficient, as new radio technologies come, the software radios can just be updated to keep up with the times instead of having a need for constant hardware replacement. |
Reviewer: Rick Sear Problem being solvedInternet-enabled devices pretty much all use specialized chips (capable only of transmitting/receiving over a particular protocol) to communicate because they have very high throughput. However, there is a cheaper, more general alternative: software defined radios. Important contributions
|
Reviewer: Sam Hanna Problem Being Solved: Important Areas: |
Reviewer: Sam Frey Problem Contributions |
Review Type: Skim Problem Being Solved Contributions
|
Review Type: SkimReviewer: Sean McBrideProblem Being SolvedThe proliferation of competing wireless IoT standards has resulting in the development of multi-protocol hubs with dedicated chips for speaking each of the dominant protocols. However, these different wireless technologies interfere with each other, and the gateway relies on the dedicate chips to handle interference and retransmission. How might a software defined radio that could receive and interpret these different protocols help dis-aggregate overlapping transmissions and reduce interference? ContributionsCreated a Raspberry Pi-powered software defined radio receiver that is able to generate a least-common-denominator "universal preamble" that can detect transmissions of any of the supported wireless protocols. These transmissions are captured and uploaded to a cloud-based system that is able to apply kill filters and successive interference cancellation to separate out interfering instructions. This resulted in an increase in average throughput of 745.96%. |
Review Type: Skim Problem Being Solved Contributions |
Reviewer: Akinori Kahata
|
No description provided.
The text was updated successfully, but these errors were encountered: