Location-Based Service LBS Navigation Service

Copyright © 2002-2008 Open Geospatial Consortium, Inc. All Rights Reserved. 5 13 Symbols and abbreviated terms The following symbols and abbreviated terms are used in this document. ADT Abstract Data Type API Application Program Interface GMLC Gateway Mobile Location Center GMS GeoMobility Server LBS Location Based Service LIF Location Interoperability Forum MLP Mobile Location Protocol MPC Mobile Positioning Center OGC Open Geospatial Consortium OMA Open Mobile Alliance OSA Open Service Architecture XLS XML for Location Services XML eXtended Markup Language 14 Top-Level Architecture Figure 2 shows how the concept GeoMobility Server relates to the other elements of an LBS architecture. The GeoMobility server is an element offering basic functions on which location-based applications are built the OpenLS Core Services. This server uses open interfaces to access network location capacity provided through a GMLC, for instance and provides a set of interfaces allowing applications hosted on this server, or on another server, to access the OpenLS Core Services see definition of Core Services in section 15. The GeoMobility Server also provides content such as maps, routes, addresses, points of interest, traffic, etc. It can also access other local content databases via the Internet. In summary, the GeoMobility Server contains:  The Core Services and their OpenLS interfaces; Copyright © 2002-2008 Open Geospatial Consortium, Inc. All Rights Reserved. 6  The OpenLS Information Model, consisting of ADTs;  Possibly, a set of local 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; and  Possibly other supporting functions for personalization, context management, billing, logging, etc. Figure 2. Role of the GeoMobility Server 15 OpenLS Core Services The Core Services are location-based application services that form the Services Framework for the GeoMobility Server. See the associated specifications for these services for details about each of these services these references are listed in section 3. Copyright © 2002-2008 Open Geospatial Consortium, Inc. All Rights Reserved. 7 The GeoMobility Server Core Network Service Provider GeoMobility Server GeoMobility Server Position Determination Equipment GMLCMPC Portal Service Platform Authentication, Billing, etc. • Route • Presentation –Route Displa y –Map Displa y –Route Directions Display • Geocode Reverse Geocode LIF OpenLS O p e n L S OpenLS-based Applications Personal Navigator, Concierge, Tracker… O p en LS Applications Residing on Mobile Terminals Desktops OpenLS • Road Net works • Navigation Info • Maps Location Content • Directories • Addresses • Traffic Info • Gate wa y LIF • Directory OpenLS Core Services Figure 3. The GeoMobility Server Note: It is not necessary to specify a Coordinate Reference System for Point geometries that are used by these services because the default for all coordinates used by the GeoMobility Server is WGS 84. The coordinate conventions are as follows: - Default Coordinate Reference System - WGS 84 srsName=EPSG4326; - Coordinate Order - Latitude, Longitude; - Value Type - Decimal Degrees; - Latitude Sign is +90 at North Pole to -90 at South Pole; - Longitude Sign is -180 west from Greenwich at the International Dateline to +180 east from Greenwich at the International Dateline.

15.1 Part 1: Directory Service

This service provides subscribers with access to an online directory to find the nearest or a specific place, product or service. Through a suitably equipped OpenLS application, the subscriber starts to formulate the search parameters in the service request, identifying the place, product or service that they seek by entering the name, type, category, keyword, phone number, or some other ‘user-friendly’ identifier. A position must also be employed Copyright © 2002-2008 Open Geospatial Consortium, Inc. All Rights Reserved. 8 in the request when the subscriber is seeking the nearest place, product or service, or if they desire a place, product or service at a specific location or within a specific area. The position may be the current Mobile Terminal position, as determined through the Gateway Service, or a remote position determined in some other manner. The directory type may also be specified e.g. yellow pages, restaurant guide, etc. Given the formulated request, the Directory Service searches the appropriate online directory to fulfill the request, finding the nearest or specific place, product or service, depending on the search criteria. The service returns one or more responses to the query with locations and complete descriptions of the place, product, or service, depending upon directory content, where the responses are in ranked order based upon the search criteria.

15.1.1 Pinpoint Directory Service

Provides subscribers with access to an online directory to find the location of a specific place, product or service. This service is independent of subscriber location e.g., the subscriber may wish to ‘pinpoint’ a place in a distant country.

15.1.2 Proximity Directory Service

Provides subscribers with access to an online directory to find the nearest place, product or service. From the Usage Scenarios below, it seems unnecessary to separate these usages into two services, when they are simply special cases of the same underlying Directory Service request. The examples below will illustrate that there are two simple cases for finding a particular point of interest that roughly correspond to the Pinpoint and Proximity requests: 1. By some property of the Point of Interest e.g., unique identifier, name, description, phone number, absolute location 2. By its location relative to some other point of interest e.g., Nearest to me, within some distance of a specified entity, within some defined boundary. Any of these or combinations of these may be made using the combined Directory Services request which is specified below.

15.1.3 Use Cases

The user of the Directory Service wishes to locate a particular Place, Product or Service. The user may constrain the request by specifying parameters that filter out candidate placesproductsservices according to some identifier, attribute, or location. Example usage scenarios for Directory Service are captured below.