Location-Based Services – LBS Standards

copyrights:Aleksander Buczkowski 2011-2012

In order to sustain operability, interoperability and reliability of all those systems, which highly important from user point of view the industry introduced several standards.The organizations that play significant roles in the development of LBS standards are the Open Mobile Alliance (OMA) and Open Geospatial Consortium (OGC). In addition to these, there are several other organizations that provide important components of the LBS standards infrastructure.

Open Mobile Alliance
The most important specification that OMA has come up with is MLP (Mobile Location Protocol). MLP enables LBS applications to interoperate with wireless network regardless of its interfaces (GSM, CDMA etc.) and positioning methods. MLP defines a common interface that facilitates exchange of location information between the LBS application and location servers in wireless networks. It also supports the privacy of user providing access to location information only to those who are authorized users. Hence OMA is the key enabler of mobile service specification standards that support the creation of interoperable end-to-end mobile services.
Open Geospatial Consortium
The Open Geospatial Consortium (OGC) is an international standards organization responsible for the development of standards for geospatial- and location-based services. To complement Location Interoperability Forum’s (LIF) advanced MLP services, OGC has come up with OpenLS Services that addresses the geospatial interoperability issues. Key services handled by OpenLS specification are:
  • coordinate transformation,
  • Web Mapping,
  • Geography Markup Language (GML),
  • geoprocessing and
  • Web integration.
The OpenLS platform provides open interfaces to LBS core services such as route determination, directory, location utility (geocoder that obtains x, y co-ordinates from address, and reverse geocoder that obtains address from x,y co-ordinates), presentation (display showing map, point of interest), and gateway (find position of mobile terminal ‘from the network’).
OpenLS Abstract Data Types (ADTs) are the basic information constructs used by these core services. ADTs are ‘application schemas’ of well-known data types and structures for location information encoded in OGC’s XML for Location Services (XLS). These schemas encode location information, for example, route summary and route geometry, route instructions, location, area of interest, and point of interest and address. The specifications of OpenGIS are geared toward the development of interoperable solutions that “geo-enable” the Web, wireless, and locationbased services. These specifications enable developers to make complex spatial information accessible to help deploy various services and useful applications.

In order to make spatial standards interoperable with communication standards, such as, to integrate LBS into Internet, Web and wireless, OGC coordinates its activities with several organizations including OMA, IETF, W3C, OASIS, ISO, Parlay. Parlay is a consortium that develops open APIs based on their Open Systems Architecture (OSA) for mobile networks that provides functionality for authentication, authorization, and access to network services. APIs for OSA/Parlay enable service implementations within existing fixed and mobile telecommunications networks. This architecture/framework complements the GeoMobility Server, described here.

The GeoMobility server
The GeoMobility server provides the basic functionalities on which location-based applications are built (the OpenLS Core Services). It provides subscribers with various location-based application services and content. By using open interfaces to access network location information, this server allows applications to access a set of core services known as the OpenLS Core Services. To summarize, the GeoMobility server provides:
  • The Core Services and their OpenLS interfaces along with the OpenLS Information Model, consisting of Abstract Data Types (ADTs).
  • A set of applications build upon the Core Services and accessing them through OpenLS interfaces.
  • Content such as map data, points of interest, routes, and so on used by the Core Services; this content can also be hosted on other servers and accessed through the Internet.
  • Various supporting functions for personalization, context management, billing, and logging.
Best practices for LBS privacy
There is however lack of established user privacy standards. In 2010 CTIA Wireless Association published “CTIA’s Best Practices and Guidelines for Location Based Services” but the document is not legally valid. The guidelines emphasize user notice and consent since it is the LBS user whose privacy is at risk if location information is misused or disclosed without authorization. Per the guidelines, LBS providers must inform mobile users on how their location data will be used, disclosed and protected for each user to decide whether or not to use the LBS service or authorize disclosure. More information on the CTIA’s “Best Practices and Guidelines for Location-Based Services” is available here.