A Survey on Low-Power GNSS

Research output: Contribution to journalReview Articlepeer-review

34 Citations (Scopus)
39 Downloads (Pure)

Abstract

With the miniaturization of electronics, Global Navigation Satellite Systems (GNSS) receivers are getting more and more embedded into devices with harsh energy constraints. This process has led to new signal processing challenges due to the limited processing power on battery-operated devices and to challenging wireless environments, such as deep urban canyons, tunnels and bridges, forest canopies, increased jamming and spoofing. The latter is typically tackled via new GNSS constellations and modernization of the GNSS signals. However, the increase in signal complexity leads to higher computation requirements to recover the signals; thus, the trade-off between precision and energy should be evaluated for each application. This paper dives into low-power GNSS, focusing on the energy consumption of satellite-based positioning receivers used in battery-operated consumer devices and Internet of Things (IoT) sensors. We briefly overview the GNSS basics and the differences between legacy and modernized signals. Factors dominating the energy consumption of GNSS receivers are then reviewed, with special attention given to the complexity of the processing algorithms. Onboard and offloaded (Cloud/Edge) processing strategies are explored and compared. Finally, we highlight the current challenges of today’s research in low-power GNSS.
Original languageEnglish
Pages (from-to)1482-1509
JournalIEEE Communications Surveys and Tutorials
Volume25
Issue number3
DOIs
Publication statusPublished - 2023
Publication typeA2 Review article in a scientific journal

Keywords

  • Global Navigation Satellite Systems
  • Global Positioning Systems
  • Low-power electronics
  • Digital Signal Processing
  • Approximate Computing

Publication forum classification

  • Publication forum level 2

Fingerprint

Dive into the research topics of 'A Survey on Low-Power GNSS'. Together they form a unique fingerprint.

Cite this