# US 2016/0261982 A1 · Wireless application protocol (wap) application location based services (lbs)

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2016/0261982 A1
- Document ID: US20160261982A1
- Status: Published application
- Kind: A1
- Application number: 15/155,926
- Filed: 2016-05-16
- Published: 2016-09-08
- Earliest claimed: 2007-12-14
- Assignees: TeleCommunication Systems, Inc.
- Applicants: Telecommunication Systems, Inc.
- Inventors: DREW MORIN
- Web page: https://patentgrep.com/patent/US20160261982A1

## CPC

- H04W 4/029: Location-based management or tracking services
- H04W 4/20: Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/04: specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
- H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70)
- H04L 67/52: specially adapted for the location of the user terminal
- H04L 67/55: Push-based network services
- H04W 4/02: Services making use of location information
- H04W 4/14: Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
- H04W 80/12: Application layer protocols, e.g. WAP [Wireless Application Protocol]
- H04W 88/182: {Network node acting on behalf of an other network entity, e.g. proxy}
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## 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.

## Claims

### Claim 1

(canceled)

### Claim 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.

### Claim 3 (depends on 2)

The method of claim 2, wherein:
the location information is provided to the WAP application server via a WAP reply.

### Claim 4 (depends on 2)

The method of claim 2, wherein:
the WAP application server supports multiple simultaneous WAP sessions.

### Claim 5 (depends on 2)

The method of claim 2, further comprising:
notifying the mobile device that the WAP application server is in communication with the LBS server.

### Claim 6 (depends on 2)

The method of claim 2, wherein:
the mobile-triggered request is generated by a browser operating on the mobile device.

### Claim 7 (depends on 2)

The method of claim 2, wherein:
the mobile device is a wireless phone.

### Claim 8 (depends on 2)

The method of claim 2, wherein:
the mobile device is a laptop computer.

### Claim 9 (depends on 2)

The method of claim 2, wherein:
the mobile device is a personal digital assistant.

### Claim 10 (depends on 2)

The method of claim 2, wherein:
the network-initiated LBS request is a Mobile Location Protocol (MLP) request.

### Claim 11 (depends on 2)

The method of claim 2, wherein:
the network-initiated LBS request is a Location Enabling Server (LES) request.

### Claim 12 (depends on 11)

The method of claim 11, wherein:
the LES request triggers an Assisted Global Positioning System (AGPS) location determination for the mobile device.

### Claim 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.

### Claim 14 (depends on 13)

The WAP application server of claim 13, wherein:
the WAP application network server supports multiple concurrent WAP sessions.

### Claim 15 (depends on 13)

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.

### Claim 16 (depends on 13)

The WAP application server of claim 13, wherein:
a browser operating on the mobile device provides the mobile-triggered request for location information.

### Claim 17 (depends on 13)

The WAP application server of claim 13, wherein:
the mobile device is one of a wireless phone and a laptop computer.

### Claim 18 (depends on 13)

The WAP application server of claim 13, wherein:
the network-initiated LBS request is a Mobile Location Protocol (MLP) request.

### Claim 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.

### Claim 20 (depends on 19)

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.

### Claim 21 (depends on 19)

The method of claim 19, wherein:
the given WAP session is terminated after receipt of the notification.
