Mobile Location Protocol

Abstract: The Three L's: Location, Location, Location Application Examples and Use Cases People/Asset Management and Tracking Health Care and Mobile Patient Monitoring Security Emergencies Location-Based Network Access/Security Games Retail and Shopping Retail, Advertisement, and Marketing Retail and Postanalysis of Shopping Behavior Tour Guides Other Preconditions and Frameworks for LBS Development Preconditions (LBS Market and Development) A Framework for Developing Indoor Location-Based Services Four Dimensions of Development Three Steps to Location Service Development Infrastructure The Infrastructure Components The Software Infrastructure Communication Infrastructure Example: Crickets in the MIT Facilities Environment Positioning Infrastructure Sensor Systems for Indoor Position Computation Positioning Systems and Algorithms Positioning Algorithms Position Estimation Algorithms Location Awareness and Navigation in Location-Based Systems Indoor Data Sources for Location Data Two-Dimensional vs. Three-Dimensional Spatial Reference Systems Network Path Planning Geocoding Ontology Referencing Algorithms Expressing World Models Spatial Database Systems Navigation Algorithms Map-Matching Algorithms Conclusion Existing Indoor Location Systems: How They Work Featured Indoor Location Positioning Systems Ekahau Positioning System Intel Place Lab and Skyhook WPS Microsoft Research Radar Rosum TV AeroScout BLIP Systems Modeling Location Mobile Location Protocol OGC Languages: SensorML, GML, Etc. Nexus Augmented World Modeling Language and Augmented World Query Language Navigation Modeling Languages Service Deployment Step 1: Site Survey Step 2: Create a Positioning Model Step 3: Calibrate the Positioning Model/Signal Map (Training) Step 4: Access Point Placement and Configuration Step 5: Tracking Step 6: Maintenance (Periodic Accuracy Test) Using the Ekahau Positioning System Using MIT Cricket Using Place Lab References Privacy Concerns and Methods for Safeguarding Privacy Constraints Connection-Level Privacy: Location-Identifier Split Service-Level Privacy: Identifiers as a Privacy Problem Application-Level Privacy: Visualization of Privacy Development and Deployment of Indoor Location-Based Services Trilateration Location Fingerprinting Potential Issues When Deploying a Wi-Fi-Based Positioning System Integrating Different Systems Developing the Location Database Creating the Software Infrastructure Questions to Ask When Selecting Application Servers The Application Data Flow Personalization Using Filters in Servlets Content Comparison and Equivalence Temporal Context Interval Operators Composite/Sequence Pattern Operators Syntax Examples Interfaces to External Services Standards Interoperability and the Role of Standardization Standards Frameworks OMA Location Working Group The Success of Standards: Adoption Index

Abstract: Systems and methods of sending a secure user plane location (SUPL) session initiation message from a location platform to a SUPL-enabled terminal are provided. When a network-based application has an internet protocol (IP) connection with the SUPL-enabled terminal using general packet radio service (GPRS) and needs location information regarding the SUPL-enabled terminal, the network-based application indicates an available GPRS session in mobile location protocol standard location immediate request. The location platform uses an application server hosting the network-based application to request starting a SUPL-enabled terminal-initiated location procedure. Alternatively, the location platform can determine whether a SUPL-enabled terminal has an active IP connection from an authentication, authorization, and accounting server. The IP address of the SUPL-enabled terminal is returned to the location platform, upon which a SUPL session initiation message is sent to an associated GPRS Gateway Support Node. User Datagram Protocol is utilized instead of Wireless Datagram Protocol.

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: The purpose of this specification is to define a simple and secure access method that allows Internet applications to query location information from a wireless network, irrespective of its underlying air interface technologies and positioning methods. This specification covers the core of a Mobile Location Protocol that can be used by a location-based application to request MS location information from a location server (GMLC/MPC or other entity in the wireless network). This specification has been prepared by LIF to provide a simple and secure API (Application Programmer’s Interface) to the location server, but that also could be used for other kinds of location servers and entities in the wireless network. The API is based on existing and well-known Internet technologies as HTTP, SSL/TLS and XML, in order to facilitate the development of location-based applications. Location Inter-operability Forum (LIF) Mobile Location Protocol Page 2 (70) LIF TS 101 v2.0.0 Approved Specification Version 2.0.0 20 Nov 2001