Localization of static remote devices using smartphones

Research output: Chapter in Book/Report/Conference proceedingConference contribution

8 Citations (Scopus)
59 Downloads (Pure)

Abstract

Vehicles need to locate other vehicles and network infrastructure elements on unmanned autonomous vehicle (UAV) systems. Human passengers also need to locate and be located by the vehicles, preferentially using a portable device, such as a smartphone. This paper analyses the accuracy of several localization algorithms in the remote location of entities running WiFi access points, using measurements collected in moving vehicles using a new application developed by us. The algorithms analysed include closed form estimators and one based on second order cone programming (SOCP) relaxation, which exhibits the best accuracy and is capable of estimating the path loss exponent and the transmission power. Although, due its lower complexity, the Levenberg-Marquardt algorithm was better suited for the stand-alone Android prototype application. The results show that real-time accurate positioning of static/slow moving remote entities is possible, even though the accuracy degrades when the measuring vehicle's speed increases.

Original languageEnglish
Title of host publication2018 IEEE 87th Vehicular Technology Conference, VTC Spring 2018 - Proceedings
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages1-5
Number of pages5
Volume2018-June
ISBN (Electronic)9781538663554
DOIs
Publication statusPublished - 20 Jul 2018
Event87th IEEE Vehicular Technology Conference, VTC Spring 2018 - Porto, Portugal
Duration: 3 Jun 20186 Jun 2018

Conference

Conference87th IEEE Vehicular Technology Conference, VTC Spring 2018
CountryPortugal
CityPorto
Period3/06/186/06/18

Keywords

  • Android application.
  • Location algorithms
  • Vehicular-based performance evaluation
  • WiFi localization

Fingerprint Dive into the research topics of 'Localization of static remote devices using smartphones'. Together they form a unique fingerprint.

Cite this