Skip to main navigation Skip to search Skip to main content

Benchmarking resource usage for spectrum sensing on commodity mobile devices

  • Stony Brook University

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

7 Scopus citations

Abstract

Effective management of various white space spectra may require spectrum sensing at finer spatial granularity than is feasible with expensive laboratory-grade spectrum sensors. To enable this, we envision a future where commodity mobile devices would be capable of spectrum sensing as needed, possibly via crowd-sourcing. However, since mobile devices are resource limited, understanding their resource usage in this set up is important, specifically in terms of overall latency and energy usage. In this work, we carry out a comprehensive performance benchmarking study using 4 different USB-powered software radios and 2 common smartphone/ embedded computers as mobile spectrum sensing platforms. The study evaluates latency and energy usage using a suite of commonly used sensing algorithms specifically targeting TV white space spectrum. The study shows that latency due to sensing and computation and related energy usage are both modest.

Original languageEnglish
Title of host publicationProceedings of the 3rd Workshop on Hot Topics in Wireless, HotWireless 2016
PublisherAssociation for Computing Machinery
Pages7-11
Number of pages5
ISBN (Print)9781450342513
DOIs
StatePublished - Oct 3 2016
Event3rd ACM Workshop on Hot Topics in Wireless, HotWireless 2016 - New York, United States
Duration: Oct 3 2016Oct 7 2016

Publication series

NameProceedings of the Annual International Conference on Mobile Computing and Networking, MOBICOM

Conference

Conference3rd ACM Workshop on Hot Topics in Wireless, HotWireless 2016
Country/TerritoryUnited States
CityNew York
Period10/3/1610/7/16

Fingerprint

Dive into the research topics of 'Benchmarking resource usage for spectrum sensing on commodity mobile devices'. Together they form a unique fingerprint.

Cite this