Abstract:
An improved User Plane location based service (LBS) architecture and message flow, enabling seamless User Plane location based services even when a mobile or wireless device has roamed among different carrier networks. The present invention overcomes constraints inherent in the current protocol for roaming support defined by the Secure User Plane Location Service specification. A location system is enabled to automatically fall back to a message tunneling mechanism to ensure the security of a communication path between the location service system and the target wireless device, ensuring that the communication path is uninterrupted as the wireless device travels.
Abstract:
An IMS emergency call is reliably handed off within the PS domain or from the PS domain to the CS domain, by providing continuous support of location of a user device on behalf of a PSAP. The invention provides for handover of an IMS emergency call with EPS/GPRS access in a multi-LRF environment. Emergency location services for CS based emergency and/or IMS based emergency location services are often provided by multiple emergency location service providers. The information element that is critical for supporting Location Continuity in Multi-LRF environment can be either the assigned ESQK or the Serving LRF address. ESQK is assigned by the Serving LRF during IMS emergency call setup, and is used to uniquely identify the emergency service provider that operates the serving LRF. A simpler implementation uses the Serving LRF's address to identify the Serving LRF during and after the handover (PS-PS or PS-CS).
Abstract:
A data request is generated (e.g., text, email, SMS, multimedia messaging system (MMS), etc.) from a source device. The data request is delivered to a PSAP or other emergency monitoring service location in a useable format. Exemplary useable formats include a canned voice message, delivery to a call center that translates data to voice, text to speech, and text to instant messaging (IM). Additional information and location are staged for use by the PSAP or other monitoring service location.
Abstract:
A method and mechanism to allow a location server to initiate a user plane location service (e.g., SUPL defined by OMA) procedure to a user plane enabled device via Instant Messaging, or alternatively, via an existing SIP session if a multimedia session is already established. The location request is signaled to the user plane enabled device via a SIP INFO message. The location request uses SIP messaging to overcome firewall and other network security issues. Location using SUPL over SIP may be provided about a caller making an E911 emergency call. An Instant Message may be sent to the user plane enabled device, e.g., a VoIP wireless phone.
Abstract:
A technique to allow a server such as a location server to throttle concurrent or closely timed location requests for the position of a given wireless device such that within a certain time period preferably only one location request will be initiated to the positioning engine and the remaining closely-timed location requests will be buffered or cached. When a position for the given wireless device is returned per the outstanding location request, then the retrieved position will be used to respond to each of the buffered location requests. Thus, a plurality of location requests are satisfied with a single request to the positioning engine. By optimizing the use of cached position requests, throttling of location requests per the invention reduces network traffic significantly, increases the efficiency of a positioning server (therefore reducing business cost), and provides for an improved grade or quality of location based services in general.
Abstract:
A location application can be configured to detect a call to a particular telephone number. The location application can also be configured to receive a plurality of radio frequency (RF) signals provided through a plurality of different RF interfaces. Each of the RF interfaces can be configured to receive RF signals of different protocols. The location application can also be configured to determine an identifier (ID) for a source of each of the RF signals. At least two of the RF signals can be of different protocols. The location application can also be configured to insert the ID for the sources of each of the RF signals into call signaling for the call.
Abstract:
Location based privacy settings for proximity based services that enable an end-user to define one or more geographic areas, and then explicitly opt in or opt out to proximity based services per geographic area: 5 Location based privacy settings can be stored and managed at a network level or stored and managed locally. In the network-centric solution, privacy settings for proximity based services are defined via a subscriber privacy register. In the mobile-centric solution, privacy settings for proximity based services are defined via a user interface on a proximity 10 services enabled device.
Abstract:
A mobile IP. location server that retrieves the location of a mobile device based on the public IP address that a mobile device is using. A mobile IP location server comprises a mobile location protocol interface, an identifier resolver, and a location manager. The mobile location protocol interface interacts with location applications and receives and responds to location requests. The identifier resolver converts a device's public IP address to a real mobile identifier (e.g. MSISDN) and performs address conversion by either interacting with an HTTP proxy server or querying a network address translation (NAT) table. The location manager retrieves the location of a mobile device given the device's real mobile identifier (e.g. MSISDN). A web application requests mobile IP location services by transmitting an IP request to the mobile IP location server. An IP location request contains a mobile device's public IP address, port number, and any application specific information.
Abstract:
Area event triggers are handled by receiving an original area event trigger with an initial target area within a given mobile network, for a given target mobile device. When the target mobile device is outside the mobile network serving the target area, a first changed area event trigger based on entry into the given mobile network is transmitted to the given target mobile device. When the first changed area event trigger becomes satisfied, a second changed area event trigger is generated based on entry into the initial target area, and transmitted to the given target mobile device. The second changed area event trigger may be based on entry into a region larger than, but including, the initial target area. Then when the second changed area event trigger becomes satisfied, the original area event trigger may be transmitted to the target mobile device.
Abstract:
Location based privacy settings for proximity based services that enable an end-user to define one or more geographic areas, and then explicitly opt in or opt out to proximity based services per geographic area. Location based privacy settings can be stored and managed at a network level or stored and managed locally. In the network-centric solution, privacy settings for proximity based services are defined via a subscriber privacy register. In the mobile-centric solution, privacy settings for proximity based services are defined via a user interface on a proximity services enabled device. When a proximity services enabled device receives a request for proximity based services (i.e. a peer discovery signal command for device discovery or a peer-to-peer communications request for direct communications), the device checks the current date/time and a serving network identifier/current location against location based privacy settings to determine if proximity based services are allowed on the device.