geofenceAPI.pdf - GeoFence services Dmitry Namiot Abstract This paper describes a geo-fence approach Paper analyzes the basic elements of the service

geofenceAPI.pdf - GeoFence services Dmitry Namiot Abstract...

This preview shows page 1 - 2 out of 4 pages.

Abstract — This paper describes a geo-fence approach. Paper analyzes the basic elements of the service, the various approaches for the applied services and proposes a way for integrating geo fence API’s into mobile OS directly. Also we describe operator’s API for geo fencing. By our opinion, this area is one of directions where telecom operators can use their advantages over the Internet companies. Keywords — LBS, geo services, geofence, messaging API. I. I NTRODUCTION Geo-fence is a virtual perimeter for a real-world geographic area. Virtual perimeters could be static (pre- defined) or dynamic. A typical example of dynamically generated geo-fence is a radius around a store or point location. The statical geofence can be a predefined set of boundaries, like school attendance zones or neighborhood boundaries. Custom digitized geo-fences are also in use. When the location-aware device of a location-based service (LBS) user enters or exits a geo-fence, the device receives a generated notification. This notification might contain information about the location of the device. The geo-fence notice might be sent to a mobile phone for example as well raise any another form of actions [1]. We can describe geo fencing as proactive LBS. In the many cases proactive systems are much more convenient than reactive ones, where the user has to explicitly request for location-based data. There are different kinds of location events the GPS position fix can be tested for, for example, whether the user is in close proximity to a point of interest (POI) or to another user. Why it is interesting? It looks like geo-fences become one of the hottest areas in Location Based Services. Right now the original development for LBS is more or less completed. We can see some common standards and applications (think about the various implementations of Places services like Foursquare, Twitter places, Google places, Facebook places, etc.) All of them let you either share location info or get some things nearby. And geo-fence opens the door to some personalization. You can get some custom tailored data right on the place, especially when both data stream and place (area) for receiving it are dynamically generated. At the second, geo-fence will be in the nearest future tight integrated with sensors and M2M applications. City sensors Manuscript received November 21, 2013 Dmitry Namiot is senior scientist with Faculty of Computantional Mathematics and Cybernetics of Lomonosov Moscow State University, Moscow, Russia (e-mail: [email protected]). in the various “Smart City” projects will define geofences and notification messages. Another reason why geo-fences are hot is the complexity of the implementation. There are simply much more “places” - based LBS applications comparing with geo-fences systems. Geo-fences being conceptually simple are actually not so easy to implement.
Image of page 1
Image of page 2

You've reached the end of your free preview.

Want to read all 4 pages?

  • Fall '14
  • Location-based service, Cell ID, cell id info, SUPL

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture