Browse Prior Art Database

Methods to save client battery in Tag based location system

IP.com Disclosure Number: IPCOM000239229D
Original Publication Date: 2014-Oct-22
Included in the Prior Art Database: 2014-Oct-22
Document File: 5 page(s) / 27K

Publishing Venue

Motorola

Related People

Shanmugavadivel, Senthilraj: INVENTOR [+3]

Abstract

There are various hardware and software sensors present on Smartphone. These sensors could be very useful if combined with the solution like locationing. Idea proposes to use available sensor on Smartphone to optimize the scan and location update interval to save client battery. Many use case could be derived like aggressive scan/location update in specific area based on user or specific habits or even based on special offers etc. Idea further extends the concept of neighbor tags to estimate the tags based on the user movement of direction and speed.

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 39% of the total text.

Methods to save client battery in a Tag based Locationing System

By Anil Kaushik, Senthilraj Shanmugavadivel

Motorola Solutions, Inc.

 

ABSTRACT

There are various hardware and software sensors present on Smartphone. These sensors could be very useful if combined with the solution like locationing. Idea proposes to use available sensor on Smartphone to optimize the scan and location update interval to save client battery. Many use case could be derived like aggressive scan/location update in specific area based on user or specific habits or even based on special offers etc. Idea further extends the concept of neighbor tags to estimate the tags based on the user movement of direction and speed.

PROBLEM

·         Tag based locationing system relies upon client application. Client battery remains big concern for such system and if client application is not optimized to use the device smartly, client might drain its battery and finally user might stop using such applications.

·          

·         Client needs to scan the tag, process the result and send it over WLAN or cloud to Location server. Most of the battery consumption would be in scanning the tag and sending it over WLAN/Cloud to the Location server. If the client’s battery is low or below certain threshold, running client application might have adverse impact and user might switch off such application. If scan and Location update interval are set statically, it might not be optimized and even if there is no need for scan and location update, it might be doing both the operations which will result in client’s battery draining faster. Please note those motion sensors are very efficient in terms of energy consumption.

SOLUTION

1)     Using Motion Sensor and Scan result to save client battery by stopping/reducing the scan/Location Update interval

·         Client application scans for BLE tags.

·         Scan result is passed to a handler.

·         If handler gets new tags in the scan from previous scan, it continues to scan for tags (It means user is moving so continue to scan for tag).There is no point of using motions sensor since tags are changing so it means user is moving.

·         If handler sees that scan is returning only a set of tags, it might mean user might be stationary or moving slowly.

·         If previous step return true, Client application registers for motion sensor and start processing the results.

·         Client application  stops scanning for tags (or decrease the scan interval frequency)

·         If motion sensor indicates that user is moving again, client application starts scanning for tags again (or increase scan frequency). Note that application should filter out the cases where user is just moving the station but user itself is almost stationary. One of the ideas could be monitoring change in X, Y and Z. If there is not much change than it might mean that user is not moving only station is moving.

·         If scan result again shows new tags, client application de-registers the motion sensor.

·         Algorithm continues based on the user...