Browse Prior Art Database

Methods to save the power of mobile device in Location Based Service

IP.com Disclosure Number: IPCOM000200655D
Original Publication Date: 2010-Oct-24
Included in the Prior Art Database: 2010-Oct-24
Document File: 6 page(s) / 481K

Publishing Venue

Motorola

Related People

Zhang, L.J.: INVENTOR [+3]

Abstract

Location Based Service (LBS) plays a more and more important role in the current telecom application. GPS/A-GPS has been introduced to the current LBS specs such as SUPL. As the resource is limited in mobile device such as power, it is very important to save the power of the mobile device in order to make LBS more popular. And the computing resource of LBS Server can be considered as unlimited compared to mobile device. This paper focus on moving some complicated logic from mobile device to LBS server to save power of mobile device.

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 24% of the total text.

Methods to save the power of mobile device in Location Based Service

 

Laijun Zhang, Edmund Zheng, Tong Tang

Motorola, Inc.

HNMSO

 

ABSTRACT

Location Based Service (LBS) plays a more and more important role in the current telecom application.

GPS/A-GPS has been introduced to the current LBS specs such as SUPL. As the resource is limited in mobile device such as power, it is very important to save the power of the mobile device in order to make LBS more popular. And the computing resource of LBS Server can be considered as unlimited compared to mobile device.

This paper focus on moving some complicated logic from mobile device to LBS server in SUPL (Secure User Plane Location) service to save power of mobile device.

PROBLEM

Location triggered service are supported by both the user plane (SUPL) and control plane. The triggers could be:

Periodic Triggered service: The periodicity of reporting defined by an interval time

Event Triggered service: A Change of Area defined as the event “change of area”, including geography and area-ids. (The geography can be mapped to area-id list)

An event triggered service session will be established between Location Server and Mobile Device when the LCS Client starts a positioning request, and the session will persist until the stop time is reached.

In some case, there will be some resource (including power) wasting of the mobile device, which is one of the key factors for the real use of location event triggered service:

[Problem #1] The trigger criteria is “entering city A”, while the user is in city B which is far away from city A. In this case, the trigger criteria may not be met forever until the stop time is reached. So the resource for setting up the data connection, the protocol initialization etc will be wasted.

[Problem #2] The trigger criteria is “entering city A”, while the user enters city A and stays in the center of the city instead of the edge (The LCS client often sends the event triggered service request with large target area) until the stop time is reached. As a result, the possibility to leaving and entering city A again is low. So the resource for maintaining the session, data connection etc will be wasted.

[Problem #3] In the location related standard, it is the responsibility of the Mobile Device to determine when these trigger criteria are met, which will add burden to Mobile Device such as periodical checking the criteria which consuming more power.

In some application context, it will be better if the Location Server can control the event triggered session by checking trigger criteria on server side to help the mobile device to save resource.

The reports show that the LBS service will expand rapidly in recent year. So there will be more and more situations that one mobile device is located by more than one service providers or applications simultaneously. And in this case, based on the current spec, the mobile device needs to setup/maintain/destroy multiple sessions and do multi...