A Localized Location based architecture for path tracking and mapping services

location based services

Generally, Location Based Services are provided with the help of local servers that the service provider maintains and the customer is provided any information, as per his interest, by the service provider at a price. We propose a method, wherein instead of maintaining the location based server which services the Mobile node based on the location information it, we maintain intelligence local to the Mobile Node. We propose services like path tracking, landmarking and blogging over the architectural framework that we propose.
This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
A Localized Location based architecture for path tracking and mapping services
Bhuvanendran Boopathy
CDMA MM TE - I dd /CDMA/GSG
bhuvan.b@motorola.com
Liyaqatali.G.Nadaf
NAT & CDMA-DD - IL362/CDMA/GSG
liyaqatali@motorola.com
Shivanand Kadadi
NAT & CDMA-DD - IL362/CDMA/GSG
A22063@motorola.com
Varun Srinivas
WAP Department - Senate - IF133 /Apps, Messaging & Connectivity/ GSG
varun@motorola.com
Abstract
Generally, Location Based Services are provided with the help of local servers that the service provider maintains and the customer is provided any information, as per his interest, by the service provider at a price. We propose a method, wherein instead of maintaining the location based server which services the
Mobilenode based on the location information it, we maintain intelligence local to the Mobile Node. We propose services like path tracking, landmarking and blogging over the architectural framework that we propose.
1 Introduction
Traditionally, location based services are server based i.e. all the intelligence provided by such services are located in the server that is usually provided by the service provider, which is inevitably coupled with a cost.
Cost, here, is not the only issue, but so is the limited range of service, in the sense that in areas outside the purview of the service provider, the customer is incapable of availing the same service.
The architecture in our scheme of things functions as follows. After ascertaining its position, the required service is run locally at the Mobile Node according to the location or is accessed by the same through its service provider. With the steady growth of technology, processing and storage costs are becoming cheaper. Similarly, the size of the devices is also becoming smaller. Considering the customer’s view, this is a one time investment and is highly customizable. Also, seeing how it is a [(n) distributed and] independent entity, it is scalable and, for all practical purposes, the chances of having an external point of failure are remote.
The principal function of this system would be to keep track of the path the user takes, along with any comments one might have – noting down landmarks, places frequented, and, most importantly, to customize a map so as to help when the same place is visited again. This can be used, either in lieu of pre-existing map services, or along with it. It keeps track of the places, any comments one might have about the same, and can even be stored online, thus making it similar to a blog, making anyone capable of having access to someone else’s details when necessary.
2 System View
2.1 Components
2.1.1 Positioning Client
This component which is a part of the mobile terminal records its latitude and longitude values periodically.
2.1.2 Processing Unit
This is the heart of the system where most of the intelligence...