US20160261982A1

US20160261982A1 - Wireless application protocol (wap) application location based services (lbs)

Info

Publication number: US20160261982A1
Application number: US15/155,926
Authority: US
Inventors: Drew Morin
Original assignee: TeleCommunication Systems Inc
Current assignee: TeleCommunication Systems Inc
Priority date: 2007-12-14
Filing date: 2016-05-16
Publication date: 2016-09-08
Also published as: EP2223551A4; WO2009078966A1; US20090156185A1; EP2223551A1; US9344840B2

Abstract

A Location Based Service (LBS) enabled Wireless Application Protocol (WAP) application operating in a microbrowser of a mobile device is given the ability to trigger a network initiated LBS request from a WAP application server. The WAP application server (or SMS gateway) acts as a proxy and issues an LBS request to a relevant LBS platform. In response, the WAP application server receives the requested location information from the LBS platform and initiates a WAP session with the mobile device using a WAP PUSH command. In this way, the WAP application running on the mobile device can act on requested and received LBS input from a network LBS platform.

Description

The present invention is a continuation of U.S. patent application Ser. No. 12/314549, filed 12 Dec. 2008 (now U.S. Pat. No. 9,344,840), which claims priority from U.S. Provisional Application No. 61/006,013, entitled “WIRELESS APPLICATION PROTOCOL (WAP) APPLICATION LOCATION BASED SERVICES (LBS)” to Drew Morin, filed on 14 Dec. 2007, the entirety of which is expressly incorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention
This invention relates generally to Wireless Application Protocol (WAP) applications. More particularly, it relates to Location Based Service (LBS) enabled Wireless Application Protocol (WAP) applications
2. Background of Related Art
Wireless Application Protocol (WAP) is a global standard for defining an industry-wide standard specification for developing applications over wireless communication networks. The WAP specifications define a set of protocols in application, session, transaction, security, and transport layers, which enable operators, manufacturers, and applications providers to meet the challenges in providing advanced wireless services.
WAP also defines a wireless application environment (WAE) that allows operators, manufacturers, and content developers to develop advanced services and applications including a microbrowser, scripting facilities, e-mail, World Wide Web (WWW)-to-mobile-handset messaging, and mobile-to-telefax access, etc. Based on the Internet model, the wireless device contains a microbrowser, while content WAP applications are hosted on Web servers, commonly referred to as WAP application servers.
WAP browsers provide the basic services of a computer based web browser, but with simplified operation within the restrictions of a wireless device, such as smaller size, limited memory, restricted user inputs, etc. WAP sites are websites written in, or dynamically converted to, WML (Wireless Markup Language) and accessed via the WAP browser.
A location based service (LBS) provides informational services relating to the location of a device. LBS services are accessible by wireless devices through a wireless communication network. LBS makes use of the geographical position of wireless devices.
Conventionally, a user taking advantage of a WAP application, e.g., StreetFinder® (commercially available from TeleCommunication Systems, Inc. in Annapolis, Md.) can manually enter in their current position to retrieve data related to their current position. However, the present inventors have realized that this quickly becomes tiresome if a user desires to view information for a plurality of destinations, e.g., along a route to be traveled. An LBS application operates through a distinct servicing platform, it does not itself provide access to location information for use by a wireless device's WAP applications.
There is a need for a better system and method of directing location information to a WAP application hosted by a WAP application server.

SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, a method and apparatus for providing location based services to a Wireless Application Protocol (WAP)-enabled wireless device, comprises receiving via a wireless network a WAP request from an application operating in a wireless device. A location based service (LBS) request is initiated to an LBS platform, in response to the WAP request. An LBS reply is received in response to the LBS request. Location information received in the LBS is provided to the wireless device.
In accordance with another aspect of the principles of the present invention, a method and apparatus for providing location based services to a Short Messaging Services (SMS)-enabled wireless device, comprises receiving via a wireless network an SMS request from an application operating in a wireless device. A location based service (LBS) request is initiated to an LBS platform, in response to the SMS request. An LBS reply is received in response to the LBS request. Location information received in the LBS is provided to the wireless device.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the present invention will become apparent to those skilled in the art from the following description with reference to the drawings:

FIG. 1 shows a system for servicing an LBS enabled WAP application, in accordance with the principles of the present invention.

FIG. 2 shows an exemplary signal flow for servicing an LBS enabled WAP application, in accordance with the principles of the present invention.

FIG. 3 shows an exemplary signal flow for servicing an LBS enabled WAP application, in accordance with the principles of the present invention.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The present invention introduces a technique and technology that permits a Location Based Service (LBS) enabled Wireless Application Protocol (WAP) application to trigger a network initiated LBS request from a WAP application server. The WAP application server essentially issues an LBS request to an LBS platform. The WAP server receives location information from the LBS platform, and initiates a WAP session with the mobile device through a WAP PUSH. The WAP application then acts on the requested LBS input.
In an alternate aspect, the present invention introduces a technique that permits a Location Based Service (LBS) enabled Wireless Application Protocol (WAP) application to trigger a network initiated LBS request from a mobile device. In operation, an LBS platform determines location information for a requesting mobile device, and returns the location information to the mobile device. The location information is made available to the WAP application via a WAP application server. The WAP application server services the WAP application with LBS input from the received location information.
FIG. 1 shows a system for servicing an LBS enabled WAP application, in accordance with the principles of the present invention.
In particular, as shown in FIG. 1, a system 100 for servicing an LBS enabled WAP application 110 includes a mobile devices 115, a wireless network 120, a wireless gateway 130, an IP network 140, a WAP application server 180, and LBS platforms 190.
In accordance with the principles of the present invention, the WAP application server 180 hosts an LBS enabled WAP application, hereafter referred to as a “WAP application” 110. The WAP application 110 can be hosted as a conventional WAP application, but in accordance with the principles of the invention is permitted to trigger a network initiated LBS request via the WAP application server 180.
The LBS platforms 190 provide location services for mobile devices 115. Exemplary LBS platforms can include, e.g., a Mobile Location Protocol (MLP) Hub 150, a Location Enabling Server (LES) 160, an architecture specific Direct to Platform (DTP) 170, a Position Determining Entity (PDE) 175, etc. The LBS platforms 190 are accessible over the IP network 140.
The mobile devices 115 may be any suitable mobile wireless device that supports WAP and is able to execute a WAP application 110. Exemplary mobile devices 115 that support WAP include, e.g., a cellular telephone, a PDA, a laptop computer, etc. The mobile devices 115 are capable of accessing the WAP application server 180 through a suitable wireless network 120 and/or IP network 140 (e.g., the Internet).
The exemplary mobile devices 115 are preferably capable of supporting multiple WAP sessions simultaneously, to reduce the need to drop a session and reinitiate a WAP application 110 when moving back and forth between WAP sessions.
Alternatively, the application (WAP or SMS Gateway) server can be triggered based on the device request or application state to establish a session with the LBS server to locate the mobile device. The LBS server, independent of the WAP session, can establish a location determination session with the mobile device tunneled through an Internet Protocol session out of band with the WAP session. Once calculated, the location response is then provided back to the application server or alternatively to the device.
In accordance with the principles disclosed herein, the invention can be implemented even with updated WAP version release(s).
Alternately, the mobile devices 115 may be any suitable mobile device capable of supporting Short Message Service (SMS) messaging. In accordance with the principles of the present invention, the mobile device 115 may use SMS to initiate an LBS query, similar to the WAP initiated LBS query.
The wireless network 120 may be a wireless network based on any suitable variety of digital communication technologies, e.g., Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), etc.
The mobile device 115 is capable of executing a microbrowser, with content and a WAP application 110 hosted on the WAP application server 180. Through the use of the microbrowser, the WAP application server 180 receives a request for a particular WAP application 110, and services that WAP application 110 through the establishment of a WAP session between the mobile device 115 and the WAP application server 180.
The mobile device 115, the WAP application server 180, and the LBS platform 190 preferably all support multiple WAP sessions simultaneously. Moreover, the mobile device 115, the WAP application server 180, and the LBS platform 190 preferably support IP sessions simultaneously with WAP sessions.

Scenario 1: WAP Application Initiated by Subscriber

In accordance with a first aspect of the present invention, a WAP application 110 is an LBS enabled WAP application. A user of the mobile device 115 selects a desired WAP application 110, e.g., StreetFinder® through the microbrowser. The WAP application 110, in turn, triggers an IP network 140 initiated LBS request from the WAP application server 180 to any one of the LBS platforms 190.
In response to the LBS request, the WAP application server 180 acts as a proxy and initiates a suitable request to any one of the LBS platforms 190. At this point the WAP application server 180 preferably notifies the particular mobile device 115 operating the WAP application 110 that an LBS request to an LBS platform 190 has been initiated.
Preferably the WAP application server 180 can terminate the WAP session. Alternatively, if the mobile device 115 supports multiple simultaneous WAP sessions, the WAP session associated with the WAP application 110 can be left open.
The relevant LBS platform 190 initiates an IP network 140 initiated LBS request using a WAP PUSH command, with the mobile device 115 having pre-authorized such an LBS request. In response to the LBS request, the relevant LBS platform 190 determines a location of the mobile device 115.
Location of the mobile device can be determined in any number of suitable ways, e.g., using a Global Positioning System (GPS), Assisted GPS (AGPS), Control Plane, User Plane, various variations of Time Difference of Arrival (TDOA), Uplink Time Difference of Arrival (UTDOA), etc.
The relevant LBS platform 190 returns a location of the mobile device 115 to the WAP application server 180. The WAP application server 180 then terminates the WAP session associated with the return of the location of the mobile device 115 to the WAP application server 180. Alternatively, if the WAP application service 180 supports multiple simultaneous WAP sessions, the WAP session associated with the return of the location of the mobile device 115 to the WAP application server 180 may be left open.
The WAP application server 180 then initiates a WAP session with the mobile device 115 through the use of a WAP PUSH command. The WAP application 110 then acts on the requested LBS input.

Scenario 2: WAP Application Initiated by Subscriber

In accordance with another aspect of the present invention, the WAP application 110 is LBS enabled. When the user of the mobile device 115 selects or runs the LBS enabled WAP application 110 (e.g., StreetFinder®) in their microbrowser, the WAP application 110 triggers an IP network 140 initiated LBS request initiated and sent by the WAP application server 180 to any one of the LBS platforms 190.
Any of the LBS Platforms 190 initiates an IP network 140 initiated LBS request using a WAP PUSH command, the mobile device 115 having pre-authorized such an LBS request. Alternatively, any of the LBS platforms 190 can initiate an IP network 140 initiated LBS request over an existing WAP session.
In response to the LBS request, the relevant LBS platform 190 determines a location of the mobile device 115. The location of the mobile device can be determined in any number of ways, e.g., using a Global Positioning System (GPS), Assisted GPS (AGPS), Control Plane, Uplink Time Difference of Arrival (UTDOA), etc.
The relevant LBS platform 190 returns a location of the mobile device 115 to the WAP application server 180. The WAP application server 180 can then terminate the WAP session associated with the return of the location of the mobile device 115 to the WAP application server 180. Alternatively, if the WAP application service 180 supports multiple simultaneous WAP sessions, the WAP session associated with the return of the location of the mobile device 115 to the WAP application server 180 can be left open.
The WAP application server 180 then initiates a WAP session with the mobile device 115 through the use of a WAP PUSH command. The WAP application 110 is then able to act on the received LBS input.

Scenario 3: WAP Application Initiated by Subscriber

In accordance with yet another aspect of the present invention, the WAP application 110 is LBS enabled. When the user of the mobile device 115 selects or runs the LBS enabled WAP application 110 (e.g., StreetFinder®) in their microbrowser, the mobile device 115 triggers the mobile device 115 to initiate an LBS request from any of the LBS platforms 190.
In response to the LBS request, the relevant LBS platform 190 determines a location of the mobile device 115. The location of the mobile device can be determined in any number of ways, e.g., using a Global Positioning System (GPS), Assisted GPS (AGPS), Control Plane, Uplink Time Difference of Arrival (UTDOA), etc.
The relevant LBS platform 190 returns a location of the mobile device 115 to the mobile device 115. The location of the mobile device 115 is then made available to the WAP application server 180 through a WAP session. The WAP application server 180 services the WAP application 110 with LBS input from the received location information.
FIG. 2 shows an exemplary signal flow for servicing an LBS enabled WAP application, in accordance with the principles of the present invention.
In particular, as shown in FIG. 2, a WAP request 210 is initiated from a mobile device 115 that selects a WAP application 110. The WAP request 210 is issued from the mobile device 115 to the WAP application server 180.
The WAP application server 180 then responds to the WAP request 210 in step 220 (included in scenario 1, omitted from scenario 2). In step 220, the WAP application server 180 notifies the mobile device 115 that the request for location from an LBS platform 190 has been initiated.
An LBS request 230 is then passed from the WAP application server 180 to a relevant LBS platform 190. The LBS request includes identification of the particular mobile device 115 issuing the WAP request, so that location for that particular mobile device 115 can be determined.
An LBS reply 240 is then passed from the relevant LBS platform 190 to the WAP application server 180. The LBS reply 240 includes the requested location information for the particular mobile device 115 that initiated the WAP request. A WAP session can be used as a communication path for the LBS reply.
Lastly, a WAP Reply with LBS reply 250 is passed from the WAP application server 180 to the requesting mobile device 115. The WAP reply 250, which can be in the form of a WAP Push, preferably includes the location information provided by the LBS reply 240 from the relevant LBS platform 190.
Now in possession with the requested location information, the mobile device 115 running the WAP application 110 may act on the LBS input.
FIG. 3 shows an exemplary signal flow for servicing an LBS enabled WAP application, in accordance with the principles of the present invention.
In particular, a mobile device 115 running a suitable microbrowser selects and executes an appropriate WAP application 110. Then, at an appropriate time, the WAP application on the mobile device 115 initiates an LBS request 310 directly to a relevant LBS platform 190. In this example, the LBS request 310 is passed from the mobile device 115 to the LBS platform 190.
In response, an LBS reply 320 is then passed from the LBS platform 190 to the mobile device 115. The LBS reply includes the requested location information obtained by the LBS platform 190.
It is at this point that an LBS reply is returned from the mobile device 115 to the WAP application server 180. The LBS reply preferably includes the location information returned in the LBS reply 320 from the LBS platform 190.
The WAP application 110 then acts on its requested LBS input.
While the invention has been described with reference to the exemplary embodiments thereof, those skilled in the art will be able to make various modifications to the described embodiments of the invention without departing from the true spirit and scope of the invention.

Claims

1. (canceled)

2. A method comprising:

receiving, at a Wireless Application Protocol (WAP) application server via a WAP session between the WAP application server and a mobile device, a mobile-triggered request for location information of the mobile device;

terminating, at the WAP application server, a WAP session with the mobile device in response to receiving the mobile-triggered request;

initiating, in response to the mobile-triggered request, a network-initiated location based service (LBS) request from the WAP application server to an LBS server for location information for the mobile device;

receiving, at the WAP application server, the location information for the mobile device from the LBS server; and

pushing, in response to receipt of the location information for the mobile device, the location information to the mobile device via a WAP PUSH command.

3. The method of claim 2, wherein:

the location information is provided to the WAP application server via a WAP reply.

4. The method of claim 2, wherein:

the WAP application server supports multiple simultaneous WAP sessions.

5. The method of claim 2, further comprising:

notifying the mobile device that the WAP application server is in communication with the LBS server.

6. The method of claim 2, wherein:

the mobile-triggered request is generated by a browser operating on the mobile device.

7. The method of claim 2, wherein:

the mobile device is a wireless phone.

8. The method of claim 2, wherein:

the mobile device is a laptop computer.

9. The method of claim 2, wherein:

the mobile device is a personal digital assistant.

10. The method of claim 2, wherein:

the network-initiated LBS request is a Mobile Location Protocol (MLP) request.

11. The method of claim 2, wherein:

the network-initiated LBS request is a Location Enabling Server (LES) request.

12. The method of claim 11, wherein:

the LES request triggers an Assisted Global Positioning System (AGPS) location determination for the mobile device.

13. A Wireless Application Protocol (WAP) application server comprising:

a memory to store machine readable instructions; and

one or more processors to access the memory and execute the machine readable instructions, the machine readable instructions comprising:

a receiver that receives a mobile-triggered request for location information for the mobile device via a given WAP session between the WAP application server and the mobile device;

a location requestor that sends a network-initiated location based service (LBS) request from the WAP server to an LBS server for location information of the mobile device in response to the mobile-triggered request;

a WAP module that provides location information received from the LBS server to the mobile device via a WAP PUSH command on another WAP session between the WAP application server and the mobile device in response to the mobile-triggered request.

14. The WAP application server of claim 13, wherein:

the WAP application network server supports multiple concurrent WAP sessions.

15. The WAP application server of claim 13, wherein:

the WAP module notifies the mobile device that contact with the LBS server has been initiated in response to the location requestor providing the network-initiated LBS request.

16. The WAP application server of claim 13, wherein:

a browser operating on the mobile device provides the mobile-triggered request for location information.

17. The WAP application server of claim 13, wherein:

the mobile device is one of a wireless phone and a laptop computer.

18. The WAP application server of claim 13, wherein:

the network-initiated LBS request is a Mobile Location Protocol (MLP) request.

19. A method comprising:

sending, from a mobile device via a given Wireless Application Protocol (WAP) session a mobile-triggered request for location information of the mobile device; and

receiving, via a WAP PUSH over another WAP session, location information for the mobile device, wherein the location information is generated by a location-based services (LBS) server in communication with the WAP application server.

20. The method of claim 19, further comprising:

receiving, from the WAP server via the given WAP session, an notification that a request for the location information has been initiated by the WAP application server to the LBS server.

21. The method of claim 19, wherein:

the given WAP session is terminated after receipt of the notification.