PATENT DOCUMENT

Publication Number: US-8942725-B2
Application Number: US-201213715183-A
Country: US
Kind Code: B2

Title: Location determination using a state space estimator

Abstract:
Methods, program products, and systems for using a location fingerprint database to determine a location of a mobile device are described. A mobile device can use location fingerprint data and readings of a sensor to obtain a location observation. The mobile device can use the location observation in a particle filter for determining a location of the mobile device at a venue. Using state of movement of the mobile device and a map of the venue, the mobile device can determine one or more candidate locations of the device. The mobile device can then update the candidate locations using a next observation, and determine a probability density function based on the candidate locations. The mobile device can then present to a user a most probable location as a current location of the device in the venue.

Claims:
What is claimed is: 
     
       1. A method comprising:
 determining, by a mobile device, an initial location of the mobile device, the initial location being at a venue, the venue comprising a space accessible by a pedestrian and one or more constraints of movement of the pedestrian; 
 determining, based on a reading of a sensor of the mobile device, a state of motion of the mobile device; 
 determining a plurality of candidate locations of the mobile device based at least in part on the initial location, the state of motion, and a map of the venue specifying the one or more constraints, wherein determining the candidate locations comprises:
 upon determining that the mobile device is stationary, generating the candidate locations based on a state space system noise model; or 
 upon determining that the mobile device is moving, generating the candidate locations that avoids moving the mobile device into the constraints; 
 
 receiving, by the mobile device, a location observation, the location observation including an estimated location of the mobile device in the space, the estimated location being determined based on readings of one or more sensors of the mobile device and location fingerprint data describing attributes of signals measurable by the one or more sensors when the mobile device is at the venue; 
 filtering the candidate locations using the location observation, including determining a likely location of the mobile device based on the candidate locations, the observation, and a probability model, wherein:
 the probability model comprises a particle filter; and 
 filtering the candidate locations comprises feeding the candidate locations and the observation as inputs to the particle filter, wherein the particle filter estimates a probability density of the candidate locations using a previous location of the mobile device conditioned upon the observations and filters the candidate locations according to the probability density; and 
 
 providing the likely location for output as a current location of the mobile device. 
 
     
     
       2. The method of  claim 1 , wherein determining the initial location comprises estimating the initial location based on a prior location observation. 
     
     
       3. The method of  claim 1 , wherein determining the state of motion comprises determining at least one of a speed or a heading of the mobile device, the speed or heading being determined based on a reading of at least one of an accelerometer, a magnetometer, a barometer, or a gyroscope of the mobile device. 
     
     
       4. The method of  claim 1 , wherein determining the candidate locations of the mobile device comprises upon determining that the mobile device moves:
 determining a likelihood that the mobile device is moving from the initial location in a direction that avoids the constraints; and 
 generating the candidate locations, wherein more candidate locations are generated in a direction that is associated with a higher likelihood. 
 
     
     
       5. The method of  claim 4 , wherein determining the likelihood that the mobile device is moving from the initial location in the direction that avoids the constraints comprises:
 determining a path of the venue based on the constraints; 
 determining a destination type of a point on the path based on the map, the destination type indicative of a likelihood that the pedestrian will move toward a destination of the path when the pedestrian is moving along the path; and 
 determining the likelihood that the mobile device is moving from the initial location in the direction based on the destination type of the path. 
 
     
     
       6. The method of  claim 1 , comprising:
 determining that a count of the one or more candidate locations satisfies a depletion threshold; and 
 generating a candidate location at a random location in the venue for location determination. 
 
     
     
       7. The method of  claim 1 , comprising:
 designating the current location as an initial location for estimating a next current location of the mobile device. 
 
     
     
       8. The method of  claim 1 , wherein the location fingerprint data comprise at least one of:
 wireless access point fingerprint data; 
 radio-frequency identification (RFID) fingerprint data; 
 near field communication (NFC) fingerprint data; 
 Bluetooth™ fingerprint data; 
 magnetic field fingerprint data; 
 cellular fingerprint data; or 
 computer vision fingerprint data. 
 
     
     
       9. The method of  claim 1 , wherein the location fingerprint data comprise a plurality of pre-specified locations inside of the venue and a fingerprint of each pre-specified location. 
     
     
       10. A system comprising:
 a mobile device, and 
 a non-transitory storage device storing instructions operable to cause the mobile device to perform operations comprising:
 determining an initial location of the mobile device, the initial location being at a venue, the venue comprising a space accessible by a pedestrian and one or more constraints of movement of the pedestrian; 
 determining, based on a reading of a sensor of the mobile device, a state of motion of the mobile device; 
 determining a plurality of candidate locations of the mobile device based at least in part on the initial location, the state of motion, and a map of the venue specifying the one or more constraints, wherein determining the candidate locations comprises: 
 upon determining that the mobile device is stationary, generating the candidate locations based on a state space system noise model; or 
 upon determining that the mobile device is moving, generating the candidate locations that avoids moving the mobile device into the constraints; 
 receiving a location observation, the location observation including an estimated location of the mobile device in the space, the estimated location being determined based on readings of one or more sensors of the mobile device and location fingerprint data describing attributes of signals measurable by the one or more sensors when the mobile device is at the venue; 
 filtering the candidate locations using the location observation, including determining a likely location of the mobile device based on the candidate locations, the observation, and a probability model, wherein: 
 the probability model comprises a particle filter; and 
 filtering the candidate locations comprises feeding the candidate locations and the observation as inputs to the particle filter, wherein the particle filter estimates a probability density of the candidate locations using a previous location of the mobile device conditioned upon the observations and filters the candidate locations according to the probability density; and 
 providing the likely location for output as a current location of the mobile device. 
 
 
     
     
       11. The system of  claim 10 , wherein determining the initial location comprises estimating the initial location based on a prior location observation. 
     
     
       12. The system of  claim 10 , wherein determining the state of motion comprises determining at least one of a speed or a heading of the mobile device, the speed or heading being determined based on a reading of at least one of an accelerometer, a magnetometer, a barometer, or a gyroscope of the mobile device. 
     
     
       13. The system of  claim 10 , wherein determining the candidate locations of the mobile device comprises, upon determining that the mobile device moves:
 determining a likelihood that the mobile device is moving from the initial location in a direction that avoids the constraints; and 
 generating the candidate locations, wherein more candidate locations are generated in a direction that is associated with a higher likelihood. 
 
     
     
       14. The system of  claim 13 , wherein determining the likelihood that the mobile device is moving from the initial location in the direction that avoids the constraints comprises:
 determining a path of the venue based on the constraints; 
 determining a destination type of a point on the path based on the map, the destination type indicative of a likelihood that the pedestrian will move toward a destination of the path when the pedestrian is moving along the path; and 
 determining the likelihood that the mobile device is moving from the initial location in the direction based on the destination type of the path. 
 
     
     
       15. The system of  claim 10 , the operations comprising:
 determining that a count of the one or more candidate locations satisfies a depletion threshold; and 
 generating a candidate location at a random location in the venue for location determination. 
 
     
     
       16. The system of  claim 10 , the operations comprising:
 designating the current location as an initial location for estimating a next current location of the mobile device. 
 
     
     
       17. The system of  claim 10 , wherein the location fingerprint data comprise at least one of:
 wireless access point fingerprint data; 
 radio-frequency identification (RFID) fingerprint data; 
 near field communication (NFC) fingerprint data; 
 Bluetooth™ fingerprint data; 
 magnetic field fingerprint data; 
 cellular fingerprint data; or 
 computer vision fingerprint data. 
 
     
     
       18. The system of  claim 10 , wherein the location fingerprint data comprise a plurality of pre-specified locations inside of the venue and a fingerprint of each pre-specified location. 
     
     
       19. A non-transitory computer-readable medium storing instructions operable to cause one or more processors to perform operations comprising:
 determining, by a mobile device, an initial location of the mobile device, the initial location being at a venue, the venue comprising a space accessible by a pedestrian and one or more constraints of movement of the pedestrian; 
 determining, based on a reading of a sensor of the mobile device, a state of motion of the mobile device; 
 determining a plurality of candidate locations of the mobile device based at least in part on the initial location, the state of motion, and a map of the venue specifying the one or more constraints, wherein determining the candidate locations of the mobile device comprises: 
 determining a plurality of random locations that are reachable by the mobile device under constraints of the state of motion and the one or more constraints; and 
 designating the random locations as the candidate locations; 
 receiving, by the mobile device, a current location observation, the current location observation including an estimated location of the mobile device in the space, the estimated location being determined based on readings of one or more sensors of the mobile device and location fingerprint data describing attributes of signals measurable by the one or more sensors when the mobile device is at the venue; 
 filtering the candidate locations using the initial location and the current location observation, including determining a likely location of the mobile device based on the initial location, the candidate locations, the observation, and a probability model, wherein:
 the probability model comprises a particle filter; and 
 filtering the candidate locations comprises feeding the initial location, the candidate locations, and the current location observation as inputs to the particle filter, wherein the particle filter estimates a probability density of the candidate locations using the initial location of the mobile device conditioned upon the observations and filters the candidate locations according to the probability density, the initial location being estimated from a prior location observation that was received by the mobile device at a pre-specified duration prior to receiving the current location observation; and 
 
 providing the likely location for output as a current location of the mobile device. 
 
     
     
       20. The computer-readable medium of  claim 19 , wherein the pre-specified duration is one second or five seconds, corresponding to motion speed of the pedestrian. 
     
     
       21. The computer-readable medium of  claim 19 , wherein determining the state of motion comprises determining at least one of a speed or a heading of the mobile device, the speed or heading being determined based on a reading of at least one of an accelerometer, a magnetometer, a barometer, or a gyroscope of the mobile device. 
     
     
       22. The computer-readable medium of  claim 19 , wherein determining the candidate locations of the mobile device comprises, determining that the mobile device moves:
 determining a likelihood that the mobile device is moving from the initial location in a direction that avoids the constraints; and 
 generating the candidate locations, wherein more candidate locations are generated in a direction that is associated with a higher likelihood. 
 
     
     
       23. The computer-readable medium of  claim 22 , wherein determining the likelihood that the mobile device is moving from the initial location in the direction that avoids the constraints comprises:
 determining a path of the venue based on the constraints; 
 determining a destination type of a point on the path based on the map, the destination type indicative of a likelihood that the pedestrian will move toward a destination of the path when the pedestrian is moving along the path; and 
 determining the likelihood that the mobile device is moving from the initial location in the direction based on the destination type of the path. 
 
     
     
       24. The computer-readable medium of  claim 19 , the operations comprising:
 determining that a count of the one or more candidate locations satisfies a depletion threshold; and 
 generating a candidate location at a random location in the venue for location determination. 
 
     
     
       25. The computer-readable medium of  claim 19 , the operations comprising:
 designating the current location as an initial location for estimating a next current location of the mobile device. 
 
     
     
       26. The computer-readable medium of  claim 19 , wherein the location fingerprint data comprise at least one of:
 wireless access point fingerprint data; 
 radio-frequency identification (RFID) fingerprint data; 
 near field communication (NFC) fingerprint data; 
 Bluetooth™ fingerprint data; 
 magnetic field fingerprint data; 
 cellular fingerprint data; or 
 computer vision fingerprint data. 
 
     
     
       27. The computer-readable medium of  claim 19 , wherein the location fingerprint data comprise a plurality of pre-specified locations inside of the venue and a fingerprint of each pre-specified location.

Description:
TECHNICAL FIELD 
     This disclosure relates generally to location determination. 
     BACKGROUND 
     Some mobile devices have features for determining a geographic location. For example, a mobile device can include a receiver for receiving signals from a global satellite system (e.g., global positioning system or GPS). The mobile device can determine a geographic location, including latitude and longitude, using the received GPS signals. In many places, GPS signals can be non-existent, weak, or subject to interference, such that it is not possible to accurately determine a location using the GPS functions of the mobile device. For example, a conventional mobile device often fails to determine a location based on GPS signals when the device is inside a building or tunnel. 
     SUMMARY 
     Methods, program products, and systems for using a location fingerprint database to determine a location of a mobile device are described. Where GPS signals are unavailable, a mobile device can apply statistical classification using a location fingerprint database generated by extrapolation and interpolation to determine the location. 
     In one aspect, a server can generate location fingerprint data for the database. The server can generate the location fingerprint data using crowd sourcing, using known locations of signal sources, or both. The server can receive, from a sampling device, measurements of environment variables, e.g., signals from a signal source at one or more sampling points. The server can extrapolate and interpolate, from the received measurements, estimated measurements at one or more locations in a venue. The server can store the extrapolated or interpolated measurements as location fingerprint data. The server can send the location fingerprint data to a mobile device for determining a location of the mobile device when the mobile device is at the venue. 
     In one aspect, a mobile device can use location fingerprint data received from a server to determine a location of the mobile device at the venue. The mobile device can obtain, from a sensor of the mobile device, a vector of sensor readings, each sensor reading can measure an environment variable, e.g., a signal received by the sensor from a signal source. The mobile device can perform a statistical match between the vector and the location fingerprint data. The mobile device can then estimate a current location of the mobile device based on the statistical match. 
     In one aspect, a mobile device can use location fingerprint data and readings of a sensor to obtain a location observation. The mobile device can use the location observation in a particle filter for determining a location of the mobile device in a venue. The mobile device can make an initial observation. The initial observation can include measuring environment variables, e.g., signals detected by a sensor, and comparing the measurement with the location fingerprint data. The mobile device can then determine, using a motion sensor, state of movement of the device (e.g., direction and speed). Using the state of movement and a map of the venue or pathway information, the mobile device can determine one or more candidate locations of the device. The mobile device can then update the candidate locations using a next observation, and determine a probability density function based on the candidate locations. The mobile device can then present to a user a most probable location as a current location of the device in the venue. 
     The location fingerprint techniques can be implemented to achieve the following advantages. A mobile device can determine a location even when GPS signals are unavailable, and when conventional location-determination functions fail. For example, the mobile device can determine where the mobile device is located when the mobile device is inside of a building or tunnel, where the mobile device cannot detect GPS signals. 
     Compared to a mobile device that uses conventional location estimate techniques, a mobile device using location fingerprint data can determine a location with higher resolution. For example, when a mobile device is indoors, a conventional device can use cellular signals for triangulation. The triangulation may have a resolution of a few street blocks. By comparison, a mobile device using location fingerprint data can determine whether a user carrying the device is walking along a hallway, entering a cafeteria, or entering an office in the building. The mobile device can determine on which floor the user is located, through which door the user has passed. 
     The mobile device can obtain location fingerprint data on an as-needed basis. For example, the mobile device can obtain location fingerprint data for a building only when the mobile device is about to enter the building. Accordingly, the memory footprint, network bandwidth usage, and processor load for location determination can be minimized. 
     The details of one or more implementations of location determination using a location fingerprint database are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of location determination using a location fingerprint database will become apparent from the description, the drawings, and the claims. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  is a block diagram providing an overview of location determination using location fingerprint data. 
         FIG. 2  illustrates exemplary survey techniques for generating location fingerprint data. 
         FIG. 3  is a block diagram of an exemplary fingerprint engine for generating location fingerprint data. 
         FIG. 4A  illustrates exemplary interpolation and extrapolation techniques used in surveying a venue. 
         FIG. 4B  illustrates exemplary techniques for generating location fingerprint data based on prediction. 
         FIG. 5  illustrates an exemplary feature vector in location fingerprint data. 
         FIG. 6  illustrates an exemplary logical structure of a location fingerprint database. 
         FIG. 7  illustrates exemplary techniques of estimating a current location using statistical classification. 
         FIG. 8  is a flowchart of an exemplary procedure of generating a location observation using kernel estimation. 
         FIG. 9  is a block diagram illustrating an exemplary mobile device estimating a current location using a particle filter. 
         FIG. 10  illustrates exemplary application of constraints to a particle filter. 
         FIGS. 11A-11C  illustrate exemplary techniques of configuring a particle filter using readings from sensors of a mobile device. 
         FIG. 12  is a flowchart of an exemplary procedure of generating location fingerprint data. 
         FIG. 13  is a flowchart of an exemplary procedure of estimating a location using location fingerprint data. 
         FIG. 14  is a flowchart of an exemplary procedure of estimating a location using a particle filter. 
         FIG. 15  is an exemplary user interface for displaying a location of a mobile device at a venue. 
         FIG. 16  is a block diagram of an exemplary system architecture for implementing the features and operations of  FIGS. 1-15 . 
         FIG. 17  is a block diagram illustrating an exemplary device architecture of a mobile device implementing the features and operations described in reference to  FIGS. 1-15 . 
         FIG. 18  is a block diagram of an exemplary network operating environment for the mobile devices of  FIGS. 1-15 . 
     
    
    
     Like reference symbols in the various drawings indicate like elements. 
     DETAILED DESCRIPTION 
     Overview 
       FIG. 1  is a block diagram providing an overview of location determination using location fingerprint data. Location server  102  can include one or more computers programmed to generate location fingerprint data and store the location fingerprint data in location fingerprint database  104 . Location server  102  can provide the location fingerprint data to mobile device  106 . Mobile device  106  can determine a location of mobile device  106  using the location fingerprint data received from location server  102 . 
     The location fingerprint data generated by location server  102  can include a set of features associated with a venue. The venue can be a space accessible by a pedestrian. The venue can include one or more constraints limiting the pedestrian&#39;s movement in the space. These constraints can include, for example, map constraints (e.g., walls, railings, or cubicle separators), pathway constraints (e.g., a pedestrian walking on a pathway defined by road signs tends to follow the pathway), or pedestrian motion constraints (e.g., a pedestrian cannot move faster than X miles per hour, or move vertically when not in a stairway or elevator). The venue can be a physical structure. The physical structure can be closed (e.g., a building) or open (e.g., an open stadium). The space can be indoor space inside of the physical structure, or space inside of a bounding space of the physical structure if the physical structure is open. The venue can be mobile (e.g., an airplane, a cruise ship, or a mobile oil platform). 
     For example, a venue can be a multi-story office building having a lobby, offices, walls, doors, elevators, and hallways. A pedestrian can be a human or a device that moves at a speed that is similar to a human&#39;s walking or running speed. 
     Location server  102  can generate the location fingerprint data by designating measurements of environment variables as the set of features associated with a venue. The environment variables can be signals from one or more signal sources. The measurements of environment variables can include data obtained through one or more Wi-Fi™ access point radio frequency (RF) scans. The data can include service set identifier (SSID) or received signal strength indicator (RSSI). The measurements of environment variables can include magnetic field properties, including static and dynamic properties. For example, the measurements can include a magnitude and a direction of a magnetic field and their respective rate of change. The measurements of environment variables can include Bluetooth™ scan data, e.g., an identifier or RSSI. The measurements of environment variables can include cellular data, e.g., cell identifier or RSSI. The measurements of environment variables can include vision-based features, e.g., light intensity, color, or visual features determined by a feature recognition device. The measurements of signals can include measurement of near field communication (NFC) signals or radio frequency identification (RFID) signals. 
     Location server  102  can generate location fingerprint data using fingerprint engine  108 . Fingerprint engine  108  can generate the location fingerprint data using survey or prediction. To generate location fingerprint data using survey, fingerprint engine  108  can receive crowd-sourced data, or survey data, from one or more sampling devices. Fingerprint engine  108  can generate the location fingerprint data based on the received crowd-sourced data using interpolation. The crowd-sourced data can include measurements of environment variables submitted by the one or more sampling devices. Each sampling device can be a mobile device having a sensor (e.g., an RF receiver) for measuring an environment variable (e.g., an RF signal) and configured to provide the measurement to fingerprint engine  108 . To measure the signal, the sampling device can be programmed to record detectable signals while being placed at various sampling points. For example, a user or a vehicle can carry the sampling device and walk or otherwise travel (e.g., move up or down with an elevator) inside of venue (e.g., a building). Meanwhile, the sample device can record measured signals, and submit the recorded signals to location server  102  in real time or in batches. The recorded signals can be from diverse signal sources. For example, the recorded signals can include some or all of magnetic field measurements, RF measurements, and light measurements. The recorded measurements and interpolation can be associated with the venue. 
     To generate location fingerprint data using prediction, fingerprint engine  108  can use predicted signal measurements generated by signal estimator  110 . Predication can include extrapolation using truth data on access points. The truth data can include known locations of the access points. Signal estimator  110  can be a component of location server  102  that is configured to generate estimated signal measurements based on a map (or other structural information specifying signal barriers) of a venue and the known locations of signal sources in the venue. Signal estimator  110  can receive the map, the locations, and attributes of signal sources. Signal estimator  110  can determine an estimated signal measurement at a given location based on attributes of the signal sources, locations of the signal sources, and features in the map. For example, signal estimator  110  can determine one or more sampling points in a venue, and determine a distance between a sampling point and a wireless access point. Based on a type, make, or model of the wireless access point, signal estimator  110  can determine a signal strength of the access point. Based on number of walls between the sampling point and the access point, signal estimator  110  can determine an attenuation of signal from the access point. Using the signal strength and attenuation, signal estimator  110  can determine the estimated measurement (e.g., RSSI) at the sampling point and provide the estimated measurement and coordinates of the sampling point to fingerprint engine  108 . 
     Location server  102  can send location fingerprint data to mobile device  106  upon receiving a request from mobile device  106 . Mobile device  106  can send the request to location server  102  on an as-needed bases, for example, when mobile device  106  enters a venue. Mobile device  106 , upon receiving the location fingerprint data, can store the location fingerprint data in location fingerprint database  112 . Mobile device  106  can obtain a set of measurements of environment variables (e.g., results from one or more Wi-Fi™ scans) using sensors  114 . Sensors  114  can send the measurements to scan analyzer  116  as measurement vectors. Scan analyzer  116  can be a component of mobile device  106  configured to derive a highest probable location of mobile device  106  based on the measurement vectors and location fingerprint data. Mobile device  106  can use scan analyzer  116  to match readings in the measurement vectors from sensors  114  against location fingerprint data stored in location fingerprint database  112 . The match can be multi-dimensional. For example, the match can be performed on a signal source dimension (measurement of signal source  1 , measurement of signal source  2 . . . ) and a location dimension (e.g., latitude, longitude, and altitude). The match can include a statistical classification of the measurement vectors where the location fingerprint data are training data for the statistical classification. Scan analyzer  116  can derive the highest probable location as a function of the multidimensional match. 
     In some implementations, scan analyzer  116  can designate the highest probable location as a location observation, and provide the location observation to particle filter engine  118 . Particle filter engine  118  is a component of mobile device  106  configured to use available data to estimate a current location of mobile device  106 . Particle filter engine  118  can determine an initial location of mobile device  106 , for example, by using random location in the venue or using a first observation. In addition, particle filter engine  118  can receive from sensors  114  motion information of mobile device  106 . Using the motion information and a map of the venue, particle filter engine  118  can configure parameters of a particle filter to model candidate locations of mobile device  106 . Particle filter engine  118  can then update the particle filter using the location observation from scan analyzer  116 . Updating the particle filter can include determining a current location estimate based on a past location estimate and the observation. The current location estimate can be determined using a probability density function on the candidate locations. Particle filter engine  118  can provide a representation of current location estimate as an output for display to a user of mobile device  106 . 
     Generating Location Fingerprint Data 
       FIG. 2  illustrates exemplary survey techniques for generating location fingerprint data. Sampling device  202  can survey available features of venue  204 . Surveying venue  204  can include measuring one or more environment variables using a sensor of sampling device  202 . Each environment variable can be a radio signal characteristic, a magnetic field intensity or direction, a temperature, a sound level, a light intensity or color. The environment variables can include signals from signal sources  206 ,  208 , and  210 . Signal sources  206 ,  208 , and  210  can transmit signals that are detectable by sampling device  202  inside of venue  204 . Signal sources  206 ,  208 , and  210  need not be physically located in venue  204 . 
     Sampling device  202  can be carried to various sampling points in venue  204 . Sampling device  202  can determine the sampling point based on a user input on a map of venue  204  displayed on sampling device  202 . At each sampling point, sampling device  202  can record a sensor reading measuring signals from one or more signal sources. For example, if signal sources  206 ,  208 , and  210  are wireless access points, sampling device  202  can record SSID received from the access points, and record RSSI from each wireless access point when sampling device  202  can detect a wireless signal from each wireless access point (as indicated in dashed lines in  FIG. 2 ). Sampling device  202  can designate the measurement at each sampling point as a measurement vector of the sampling point. At each sampling point, sampling device  202  need not detect signals from all signal sources to generate the measurement vector for a sampling point. Sampling device  202  can send the measurement vectors to location server  102  as survey data for additional processing. 
     Venue  204  may include space  214  for which no sampling data exist. Space  214  can be a space not reached by sampling device  202 , or a space where sampling device  202  moved through without staying long enough to obtain a reading of the signals. Fingerprint engine  108  of location server  102  can determine measurements at space  214  through interpolation or extrapolation. Additional details of operations of fingerprint engine  108  will be described below in reference to  FIG. 3 . 
       FIG. 3  is a block diagram of exemplary fingerprint engine  108  for generating location fingerprint data. Fingerprint engine  108  can be programmed to receive survey data from one or more individual sampling devices (e.g., sampling device  202  of  FIG. 2 ) and generate the location fingerprint data based on the received survey data. Fingerprint engine  108  can include data filter  302 . Data filter  302  is a component of fingerprint engine  108  configured to pre-process the received survey data. Pre-processing the survey data can include discarding abnormal survey data (e.g., incomplete readings or outliers) and compensating for differences among different sampling devices. 
     Fingerprint engine  108  can include data interpolator  304 . Data interpolator  304  is a component of fingerprint engine  108  configured to up-sample a feature resolution. Data interpolator  304  can determine that the survey data are sparse, and apply an interpolation scheme in the up-sampling. 
     Fingerprint engine  108  can include feature extrapolator  306 . Feature extrapolator  306  is a component of fingerprint engine  108  configured to determine whether a confidence value of a specific feature satisfies a threshold and to extrapolate a feature from survey data if the threshold is satisfied. The feature can reflect a characteristic of signals received at a given sampling point. 
     Fingerprint engine  108  can include data verifier  308 . Data verifier  308  is a component of fingerprint engine  108  configured to maintain integrity of the features by verifying a feature derived from survey data against one or more existing features stored in location fingerprint database  104 . Data verifier  308  can verify that each feature at a given venue that has a given set of constraints can yield at least one matching result at a high degree of confidence. Data verifier  308  can facilitate maintaining location fingerprint database  104 , including keeping location fingerprint database  104  up to date. In addition, data verifier  308  can evaluate integrity of location fingerprint database  104  by determining uniqueness of location fingerprint database  104  as a function of spatial difference. 
       FIG. 4A  illustrates exemplary interpolation and extrapolation techniques used in surveying a venue. The interpolation and extrapolation can be performed by data interpolator  304  and feature extrapolator  306  as described above in reference to  FIG. 3 , respectively. For convenience, the techniques will be described in reference to two exemplary surveys. 
     In a first survey, data interpolator  304  can receive survey data from a sampling device (e.g., sampling device  202  of  FIG. 2 ). The survey data can include measurement of one or more environment variables in a venue. For example, the survey data can include one or more measurements of RSSI of an RF signal received by the sampling device from a wireless access point when the sampling device moved inside of a building having one or more interior walls. Data interpolator  304  may or may not have information on the physical location of the wireless access point. The measurements of RSSI can be associated with locations  402  and  406 . Data interpolator  304  may not have received RSSI measurements at location  404  or  408 . Locations  402  and  406  can be provided by a surveyor, e.g., a user carrying the sampling device while walking in the venue. Data interpolator  304  can up-sample the received survey data and determine expected RSSI at locations  404  and  408  based on signal propagation properties of RF signals transmitted by the wireless access point. 
     Feature extrapolator  306  can receive a map (or other structural information) of the venue. Based on the map, feature extrapolator  306  can determine that wall  410  lies on the rectilinear path ahead of location  408 . The map may include a wall type of wall  410 , e.g., whether wall  410  is a thin glass screen or a thick weight-bearing wall. Feature extrapolator  306  may not have RSSI data for location  412  or  414 . Based on historical data and the wall type, feature extrapolator  306  can determine, for example, wall  410  can attenuate a signal from a wireless access point by 20 dB. Accordingly, feature extrapolator  306  can determine that an expected RSSI at location  412  is −20 dB, and an expected RSSI at location  414  is −100 dB. 
       FIG. 4B  illustrates exemplary techniques for generating location fingerprint data based on prediction. In some implementations, location server  102  may not have survey data for a venue. Location server  102  can use a map of the venue, and locations and types of signal sources in the venue to generate predicted measurements of environment variables in place of survey data. Specifically, signal estimator  110  of location server  102  can generate predicted signal measurements for one or more sampling points based on the map and the locations and types of the signal sources. 
     For example, signal estimator  110  can receive a map of a building that indicates wall  442  is located in the building. The map may also include information on a type of wall  442 . In addition, signal estimator  110  can receive information on signal source  444 , which can be a wireless access point. Signal source  444  may be located inside or outside of the building. Signal estimator  110  can determine, based on a relative location of the building and signal source  444 , signal from signal source  444  can be detected in the building. Accordingly, signal estimator  110  can determine that signal source  444  can be used to determine location fingerprint data to be associated with the building. Signal estimator  110  can then calculate an expected signal measurement, e.g., an expected RSSI, for signal source  444  at sampling points (e.g., sampling points  446 ,  448 , and  450 ). The calculation can be based on a characteristic of signal source  444  (e.g., a transmission power of a wireless access point), signal attenuation pattern  452  of signal source  444 , and a distance between each sampling point and the signal source. Signal attenuation pattern  452  may be different for different types of signal sources. For example, an attenuation pattern for a signal from a wireless access point may be different from an attenuation pattern for a signal from a light source, a magnetic field source, a sound source, or a heat source. 
     When signal estimator  110  calculates expected signal readings, signal estimator  110  can adjust a value of signal reading expected based on an attenuation pattern based on structures of the building as indicated in a map. For example, signal estimator  110  can determine that, based on a location of wall  442  in the building and a type of wall  442 , signals received by a mobile device at location  454 , which is located behind wall  442  from signal source  444 . Accordingly, signal estimator  110  can further attenuate the expected value of signal reading by a constant (e.g., 20 dB) or a function for location  454 . 
     Signal estimator  110  can determine sampling points  446 ,  448 , and  450  based on the map and the location of signal source  444 . Signal estimator  110  can select points from pedestrian accessible space (e.g., not inside of walls or columns) where a mobile device may receive signal from signal source  444  loud and clear such that a feature match, if exists, can have a high confidence value. 
       FIG. 5  illustrates an exemplary feature vector in location fingerprint data. Sampling device  202  can conduct a survey in a venue. Sampling device  202  can detect four signal sources when sampling device  202  is inside of the venue. Each of the four signal sources can be a wireless access point. Each of the four signal sources can have an identifier, e.g., a media access control (MAC) address. The identifiers can be, for example, AP 1 , AP 2 , AP 3 , and AP 4 , respectively. A height of each vertical line in  FIG. 5  represents a measured signal strength. The vertical lines have equal height, and each corresponds to a circle. Each circle around a signal source represents a measurement (e.g., RSSI) of the corresponding signal source that is equal to a measurement represented (e.g., 20 dB) by the height of the vertical line. A circle (e.g., the one around AP 2 ) can be larger than another one (e.g., the one around AP 4 ). The different in size can indicate that sampling device  202  can receive signals having a same signal strength in a larger area around one signal source (AP 2 ) than around another signal source (AP 4 ). 
     At location  502 , sampling device  202  can detect signals from AP 1 , AP 2 , AP 3 , and AP 4 . The signal strength of the signals from AP 1 , AP 2 , AP 3 , and AP 4  can be +20 dB, −95 dB, −95 dB, and −95 dB, respectively. Sampling device  202  can submit the signal strengths as measurement vector  504  to location server  102 . Location server  102  can determine feature vector  506  based on measurement vector  504 . Feature vector  506  can have multiple elements, each element corresponding to a signal source. A value of each element can indicate a probability that the corresponding signal source is detectable by a mobile device. Feature vector  506  can be derived from measurement vector  504 . Feature vector  506  can indicate that some measurements may bear more information than other measurements. For example, if at a given location, four access points AP 1 , AP 2 , AP 3 , and AP 4  are detected, whereas signals from one access point (AP 1 ) is very strong compared to signals from the other three access points. Location server  102  can determine that a strong RSSI measurement can only be observed in a spatially limited region, and accordingly, strong access point AP 1  can have higher information content (entropy) than AP 2 , AP 3 , and AP 4 . For example, location server  102  can assign entropy values 0.7, 0.1, 0.1, and 0.1 to AP 1  through AP 4 , respectively. Feature vector  506  can be associated with location  502 , indicating that, at location  502 , a mobile device is likely to detect a signal from AP 1 , but unlikely to detect signals from AP 2 , AP 3 , and AP 4 . Location server  102  can store feature vector  506  in a location fingerprint database as a portion of the location fingerprint data associated with the venue surveyed by sampling device  202 . 
     In some implementations, location server  102  can designate a feature vector as a good feature vector when a measurement pattern indicates a high probability that sampling device  202  is located proximate to a given signal source. Location server  102  can designate a feature vector as a good feature vector based on factors including observed power level or existence of a given frequency, among other factors. In the example shown, when location server  102  receives measurement vector  504 , location server  102  can determine sampling device  202  has a high likelihood of being close to AP 1 , if an area around AP 1  where a device can measure an RSSI of 20 dB is small. Accordingly, location server  102  can designate feature vector  506  as a good feature vector. A good feature vector can be associated with higher weight in location determination by a mobile device. 
     Exemplary Location Fingerprint Data 
       FIG. 6  illustrates an exemplary logical structure of a location fingerprint database. Location fingerprint data can include, for each location among multiple locations in a venue, at least one of measurements (or lack of measurements thereof) of various signal sources, expected measurements of the signal sources, variance of the expect measurements, and a feature vector. For example, location fingerprint data can include at least one of: wireless access point fingerprint data; RFID fingerprint data; NFC fingerprint data; Bluetooth™ fingerprint data; magnetic field fingerprint data; cellular fingerprint data; or computer vision fingerprint data. The various fingerprint data can be aggregated to form the location fingerprint data for a given location. 
     Location fingerprint data can be stored as multi-dimensional data in association with a venue. Some of the dimensions of the multi-dimensional data can be space dimensions. The space dimensions can include X (e.g., latitude), Y (e.g., longitude), and Z (e.g., altitude, not shown). The space dimension can be continuous, expressed in a function, or discrete, where the space dimension can include locations (e.g., locations  606 ,  608   610 ,  612 , and  614 ) distributed in the venue. The distribution can be even and uniform, or concentrated around areas where good feature vectors exist. 
     At least one dimension of the multi-dimensional data can be a signal source dimension. Feature vector  602  can correspond to a location represented by (X, Y, Z), and have one or more values of each signal source. The values can include one or more of an expected value of an environment variable (e.g., an expected RSSI), a variance of the expected value, or a probability that a mobile device can detect the signal from the signal source. Fingerprint engine  108  of location server  102  can determine the expected value and variance based on measurements and variance of the measurements received from a sampling device (e.g., sampling device  202  of  FIG. 2 ). The measurements can be diverse. For example, the signal source dimension can include dimension variables AP 1 , AP 2 , and a magnetic field measurement. 
     In some implementations, the space dimensions can be normalized. Fingerprint engine  108  can receive measurements from one or more sampling devices. Each measurement can correspond to a sampling point. For example, a surveyor can carry the sample device and follow path  604  to survey a venue. Fingerprint engine  108  can normalize path  604  to locations  606 ,  608   610 ,  612 , and  614  according to distribution of  606 ,  608   610 ,  612 , and  614 . 
     Exemplary Location Estimate 
       FIG. 7  illustrates exemplary techniques of estimating a current location using statistical classification. Mobile device  106  (of  FIG. 1 ) can receive location fingerprint data  712  from location server  102 . Location fingerprint data  712  can be associated with a venue. Location fingerprint data  702  can include all data in a location fingerprint database specific for the venue. Mobile device  106  can match multi-dimensional measurement vector  702  derived from one or more sensors  114  against location fingerprint data  712  to derive a highest probable location of mobile device  106  at the venue. The highest probable location can be a function of multi-dimensional measurement vector  702 . 
     Scan analyzer  116  of mobile device  106  can determine the highest probable location of mobile device  106  using an adaptive scheme between statistical classification and regression. In the statistical classification, scan analyzer  116  can identify to which locations in a set of locations (e.g., locations  704 ,  706 ,  708 , or  710  of the venue) a vector of sensor measurements belong based on training data. The set of locations can be estimated locations of mobile device  106 . The vector of sensor measurements can include multi-dimensional measurement vector  702 . The training data can include measurements associated with known locations. Scan analyzer  116  can use location fingerprint data  712  as the training data. 
     Scan analyzer  116  of mobile device  106  can employ a point-wise kernel estimation procedure to determine a category of multi-dimensional measurement vector  702 . The category can be location  704 ,  706 ,  708 , or  710 . Scan analyzer  116  can determine a probability density function (PDF) of a location of mobile device  106  among locations  704 ,  706 ,  708 , and  710 . To determine the PDF, scan analyzer  116  can determine a probability that multi-dimensional measurement vector  702  is located at each of locations  704 ,  706 ,  708 , and  710  by applying a kernel function to a difference between multi-dimensional measurement vector  702  and respective feature vectors or measurement vectors corresponding to locations  704 ,  706 ,  708 , and  710 . Scan analyzer  116  can apply a symmetric function that integrates to one (e.g., a Gaussian function, uniform function, or cosine function) as a choice of the kernel function for the point-wise kernel estimation. 
     Scan analyzer  116  can employ the feature vector in the kernel estimation procedure. In some implementations, the feature vector can use a derived entropy vector. Scan analyzer  116  can use the feature vector to increase significance of an access point the signals from which measure strong. The entropy vector can include as elements entropy of each subset of the locations. Scan analyzer  116  can use the entropy vector to express information content of multi-dimensional measurement vector  702 . Scan analyzer  116  can determine that a subset of multi-dimensional measurement vector  702  having lower readings (e.g., lower RSSI measurements) possesses a lower information content than a subset of multi-dimensional measurement vector  702  having higher readings (e.g., higher RSSI measurements) possesses. The determination can indicate that, for a venue, a subset of regions having low readings can be greater than a subset of regions having higher readings. 
     In some implementations, scan analyzer  116  can optimize the determination by reducing a search space. A search space can correspond to a location of a mobile device and an uncertainty associated with the location. Scan analyzer  116  can start from an initial estimate, which can be designated as an initial search space. For example, when scan analyzer  116  has no information on location of mobile device  106 , scan analyzer can designate the world as the initial search space. When scan analyzer  116  obtain some location information, scan analyzer  116  can reduce the search space to the United States, the state of California, the city of Cupertino, or a particular street block or building, based on the location information. Each location estimate can be derived from the estimate before. 
     Reducing the search space can include reducing, when possible, a number of discrete points (e.g., locations) for calculating probabilities in the PDF. Scan analyzer  116  can execute the kernel function in an a priori domain provided to scan analyzer  116 . The a priori domain can be an a posteriori state estimate at time k given observations up to and including at time k by particle filter engine  118 . For example, particle filter engine  118  can determine that, based on a constraint of the venue (e.g., a wall) and a limit of a speed of movement of mobile device  106  (to a maximum speed of a human walking or running), location  710  is not a possible location and shall be filtered out. Scan analyzer  116  can then determine a location observation based on probability densities on locations  704 ,  706 , and  708 . The a priori domain can be associated with uncertainty, which may increase or decrease. For example, in an attempt to reduce the search space, mobile device  106  can lose signals, causing location uncertainty and search space to increase. 
       FIG. 8  is a flowchart of exemplary procedure  800  of generating a location observation using kernel estimation. Procedure  800  can be performed by exemplary scan analyzer  116  as described above in reference to  FIG. 1 . 
     Scan analyzer  116  can define ( 802 ) statistical classification parameters using location fingerprint data and sensor measurements. Scan analyzer  116  can define classification categories, a sample vector, and training data for the statistical classification. The classification categories can be one or more candidate locations of mobile device  106 . The candidate locations can be one or more locations in a location fingerprint database. The sample vector can be multi-dimensional measurement vector  702  received from one or more sensors. The training data can be vectors stored in the location fingerprint database. Scan analyzer  116  can map the sample vector into the location categories (or “bins”). The mapping can be classification or regression. Classification can include a strict association where the sample vector is mapped into exactly one bin. Regression can include a derived association, where the sample vector is mapped into multiple bins. In regression, scan analyzer  116  can derive a final category of the sample vector by performing statistical analysis on the multiple bins. 
     Scan analyzer  116  can define ( 804 ) information content of measurements. Defining information content of measurements can include determining a weight of each measurement in the multi-dimensional measurement vector by applying a feature vector (e.g., an entropy vector). 
     Scan analyzer  116  can reduce ( 806 ) search space by a priori estimate. Reducing the search space can include executing a kernel function over an a priori domain, which can be an a posteriori state estimate provided to scan analyzer  116  by particle filter engine  118 . 
     Scan analyzer  116  can generate ( 808 ) a location observation. Generating the location observation can include performing a point-wise kernel estimation procedure to estimate of a PDF of location of mobile device  106  in the reduced search space. Generating the location observation can include aggregating statistics out of a set of most likely matches according to the PDF. Scan analyzer  116  can provide the location observation to particle filter engine  118  for estimating a current location of mobile device  106 . 
     Exemplary Particle Filter 
       FIG. 9  is a block diagram illustrating an exemplary mobile device estimating a current location using a particle filter. The mobile device can be mobile device  106  as described in reference to  FIG. 1 . 
     Mobile device  106  can use “available information” to estimate a location when GPS signals are unavailable. The available information can include, for example, motion models, motion measurements, environmental constraints, and map constraints. Mobile device  106  can then use a state space model to fuse available information from different information sources. 
     The state space model can be a simulation-based estimation model, e.g., a particle filter. Particle filter engine  118  of mobile device  106  can estimate a probability density of current locations X k  of mobile device  106  using the particle filter based on a previous location X k−1  conditioned upon a current observation Z k , where k is a given point in time, k−1 is a point prior to k in time. The time length between k and k−1 can be configurable (e.g., one second or five seconds). 
     Particle filter engine  118  can include state space estimator  902 . State space estimator  902  can be configured to receive available information and fold the available information into location estimator  904 , which is a component of particle filter engine  118  configured to provide a location estimate. 
     State space estimator  902  can receive, from a storage device of a server or of mobile device  106 , map data  906 . Map data  906  can include attributes of one or more constraints in a venue that includes a space accessible by a pedestrian carrying mobile device  106 . The constraints can include structural constraints (e.g., walls). State space estimator  902  can determine that the pedestrian cannot transition through the structural constraint. State space estimator  902  can determine a likelihood where the pedestrian may move within a given time interval, given limited motion speed of the pedestrian. 
     The constraints in map data  906  can include attributes of regions in the space of the venue. For example, the constraints in map data  906  can define a pathway (e.g., a hallway) and an open area (e.g., a lobby, a cafeteria, or an office). State space estimator  902  can determine that, when a pedestrian walks in the pathway, the pedestrian is likely to adhere to the pathway, whereas when the pedestrian walks in the open area, the pedestrian can float, e.g., move in random directions, without adhering to a pathway. State space estimator  902  can determine that the movement of the pedestrian is subject to constraint probabilities. For example, state space estimator  902  can determine a probability that the pedestrian enters an open space that opens to a pathway when a pedestrian is walking along a pathway. The probability that the pedestrian enters the open space can be higher or lower than a probability that the pedestrian stays on the pathway, based on a type of the open space (e.g., whether the open space is a lobby, a cafeteria, or an office) or a relative position of the pathway and the open space (e.g., whether the pathway ends at the open space). Additional details on determining limits on likelihood of where the pedestrian may move within a given time interval will be described below in reference to  FIG. 10 . 
     State space estimator  902  can receive, from sensors  114 , a motion context. The motion context can include readings of sensors  114 . Sensors  114  can include micro-electromechanical systems (MEMS) of mobile device  106 . For example, sensors  114  can include compass  907  configured to determine a direction of a pedestrian&#39;s heading, accelerometer  908  configured to determine whether a pedestrian&#39;s movement is walking or running, a pace of the movement, and a stride of the movement. Sensors  114  can include barometer  910  configured to determine whether a pedestrian is moving upwards or downwards (e.g., in an elevator or on stairs) based on air pressure. Sensors  114  can include gyroscope  912  configured to determine whether a pedestrian is turning. 
     Based on the motion context, state space estimator  902  can determine if a pedestrian carrying mobile device  106  is stationary or non-stationary. If state space estimator  902  determines that the pedestrian is stationary, state space estimator  902  can configure location estimator  904  using state space system noise (e.g., random locations). If state space estimator  902  determines that the pedestrian is non-stationary, state space estimator  902  can configure location estimator  904  using motion speed of the pedestrian to drive state space update of location estimator  904 . 
     State space estimator  902  can determine attitude information based on the motion context data received from sensor  114 . The attitude information can include a heading of the pedestrian determined using a series of motion context data received from sensor  114 . State space estimator  902  can receive the series of motion context data over time, and estimate a heading based on the series of motion context data using a filter configured to use a series of measurements observed over time to produce estimates of unknown variables. In some implementations, the filter can be a Kalman filter. 
     Based on the map constraints, the motion context, and the attitude information, state space estimator  902  can determine candidate locations of mobile device  106 . State space estimator  902  can designate the candidate locations as samples (or “particles”) for propagation in particle filter P(X k |X k−1 ), where X k  are current locations of mobile device  106  at time k, X k−1  are previous locations at time k−1. Propagating the particle filter can include applying the available information, including map data, motion context, and attitude information to the particle filter to determine probability density of the candidate locations in at least a portion of the venue, given previous locations. Propagating the particle filter can be based on a stochastic process for explore some or all potential constraints. In some implementations, the stochastic process can be a discretized Wiener process. Propagating the particle filter can be subject to a multi-dimensional correlation function based on availability of the constraints. 
     State space estimator  902  can detect particle depletion when a number of candidate locations fall below a threshold number sufficient for probability density calculation. Upon such detection, state space estimator  902  can perform a parallel resampling of a portion of the venue or the entire venue to recover from filter divergence. 
     Upon propagating the particle filter, state space estimator  902  can provide the particle filter to location estimator  904  for update. Location estimator  904  can update the particle filter using a location observation received from a scan analyzer (e.g., scan analyzer  116  as described in reference to  FIG. 1 ). Updating the particle filter can include feeding estimated fingerprint location into the particle filter. The location observation can be subject to a measurement model having a given system uncertainty. Updating the particle filter can include calculating probability density P(X k |X k−1 , Z k ) where Z k  is a location observation at time k. Location estimator  904  can then determine a current location of mobile device  106  (location at time k) using the probability density, including designating a most likely location of mobile device  106  as the current location of mobile device  106 . 
       FIG. 10  illustrates exemplary application of constraints to a particle filter. A state space sampler (e.g., state space estimator  902  as described above in reference to  FIG. 9 ) can receive map data of venue  204 . The map data can specify that venue  204  includes open space  1002 , hallway  1004 , and office  1006 . 
     For a given time k, mobile device  106  can determine initial location  1007  corresponding to time k−1. The initial location can be a previously estimated location of mobile device  106 . Immediately after mobile device  106  entered venue  204 , or immediately after mobile device  106  is turned on at venue  204 , it is possible that mobile device  106  has not performed a previous location estimate. In such cases, mobile device  106  can determine that initial location  1007  is a random location in venue  204 . Initial location  1007  is illustrated as a single point. In some implementations, initial location  1007  can be a probability density function on multiple possible locations, each possible location being associated with a probability that mobile device  106  is located at that location. The probability density function can be discrete or continuous. 
     Mobile device  106  can determine, using one or more sensors, that mobile device  106  is stationary, e.g., when linear and angular speed and linear and angular acceleration are zero or near zero (e.g., undistinguishable from system error margin). Upon determining that mobile device  106  is stationary, mobile device  106  can generate candidate locations  1008 ,  1010 ,  1012 , and  1014  for time k for a particle filter. Candidate locations  1008 ,  1010 ,  1012 , and  1014  can be generated based on state space system noise. In addition, initial location  1007  can be a candidate location. Mobile device  106  can apply constraints of movement in venue  204  to the particle filter. For example, mobile device  106  can determine that, since initial location  1007  is in open space  1002 , no directional constraint need to be applied; candidate locations  1008 ,  1010 ,  1012 , and  1014  can be in any direction from initial location  1007 . In addition, mobile device  106  can determine that candidate location  1014  represents an impossibility, because mobile device  106  needs to go through a barrier (e.g., a wall) or to travel at a speed exceeding a walking or running speed for a pedestrian to go around hallway  1004  to reach candidate location  1014  from initial location  1007 . Mobile device  106  can remove candidate location  1014  from the particle filter based on the impossibility. 
     At given time t, mobile device  106  can determine initial location  1018  of mobile device  106 . Initial location  1018  can correspond to time t−1. Mobile device  106  can determine, using one or more sensors, that mobile device  106  is non-stationary, e.g., when linear or angular speed or acceleration is nonzero. Upon determining that mobile device  106  is non-stationary, mobile device  106  can generate candidate locations for time t for a particle filter. The candidate locations can include location distribution sampled by the particle filter. Mobile device  106  can decide that initial location  1018  is on a path in venue  204  following hallway  1004 . Accordingly, mobile device  106  can determine that a direction of movement of mobile device  106  is limited to a direction of the path as defined by hallway  1004 . Based on a heading of mobile device  106 , mobile device  106  can determine candidate location  1020 , which is in front of mobile device  106  according to the heading, and candidate location  1022 , which can be behind mobile device  106  according to the heading. Mobile device  106  can determine that candidate location  1020  is a more likely location of mobile device  106  than candidate location  1022  is. In addition, mobile device  106  can determine that initial location  1018  is sufficiently close to an entrance of office  1006  such that a pedestrian, moving at walking speed, can enter office  1006  during the time between t−1 and t. Accordingly, mobile device  106  can place candidate location  1024  in office  1006 . Mobile device  106  can assign a distinct weight to each of the candidate locations  1020 ,  1022 , and  1024  for the particle filter. 
       FIGS. 11A-11C  illustrate exemplary techniques of configuring a particle filter using readings from sensors of a mobile device. The mobile device can be mobile device  106  as described above in reference to  FIG. 1 . 
       FIG. 11A  illustrates determining current location estimates based on initial location  1102  when the mobile device is moving at velocity v 1 . The mobile device can determine the velocity v 1  based on rate of change of readings of a sensor. In some implementations, the mobile device can determine the velocity v based on a frequency of change of acceleration measured by an accelerometer, where a higher frequency indicates a faster pace of a pedestrian. In addition, the mobile device can determine the velocity v 1  based on a magnitude of the acceleration, where a greater magnitude indicates a larger stride. 
     The mobile device can determine current location estimates  1104 ,  1106 ,  1108 ,  1110 , and  1112 . The mobile device can generate more current location estimates (e.g., location estimates  1106 ,  1108 ,  1110 , and  1112 ) in a direction of the heading of mobile device than current location estimates (e.g., location estimates  1104 ) in a direction away from the heading. The difference in number of location estimates can simulate situation where the mobile device has a higher likelihood to continue moving in an original heading than to turn back. The current location estimates can be subject to constraints of a venue, e.g., wall  1114 . The mobile device can then configure a particle filter using the estimated locations  1104 ,  1106 ,  1108 ,  1110 , and  1112 , subject to a location observation provided by a scan analyzer (e.g., scan analyzer  116  of  FIG. 1 ). The observation can be derived from location fingerprint data and can include a single location or discrete or continuous probability densities of multiple locations. 
       FIG. 11B  illustrates determining current location estimates based on initial location  1118  when the mobile device is moving at velocity v 2 . The mobile device can determine that, based on readings of the sensors, velocity v 2  is high (e.g., higher than velocity v 1  of  FIG. 11A ). Upon determining that velocity v 2  is high, the mobile device can determine that a pedestrian carrying the device is more likely to continue according to the current heading, and less likely to turn back than the pedestrian of  FIG. 11A . Accordingly, the mobile device can generate more current location estimates (e.g., location estimates  1120 ,  1122 ,  1124 ,  1126 ,  1128 , and  1130 ) in a direction of the heading. The mobile device can generate estimated location  1132  in a direction that is away from the heading, to model the possibility that the pedestrian turns back. 
     The mobile device can generated location estimates  1122  and  1126  on a path the mobile device is projected to be traveling. The mobile device can use location estimates  1122  and  1126  for calculating probabilities the pedestrian is traveling at different velocities, to verify or correct the current velocity (v 2 ) as determined by the motion sensors. 
     The mobile device can generate location estimates  1120 ,  1124 ,  1128  and  1130  for calculating probabilities that the mobile device changes directions. Comparing to  FIG. 11A , the velocity v 2  is higher than velocity v 1 . Accordingly, the distribution of location estimates  1120 ,  1122 ,  1124 ,  1126 ,  1128 , and  1130  can be more concentrated along the heading of the mobile device than location estimates  1106 ,  1108 ,  1110 , and  1112  are, where in a higher concentration, the location estimates are in a narrower beam along the heading and have less divergence away from the heading. For example, in some implementations, an expected number of location estimates is proportional to the velocity of the mobile device; a variance of directions of the location estimate can be inversely proportional to the velocity. 
       FIG. 11C  illustrates determining current location estimates based on initial location  1140  when the mobile device is moving along a pathway. A mobile device can determine initial location  1140  of the mobile device and a motion velocity v 3 . Based on map data of a venue, the mobile device can determine that the mobile device is heading in a hallway towards a corner. The mobile device can determine that movement of the mobile device is constrained by walls of the hallway. Accordingly, the mobile device can configure a particle filter using location estimates that are on the pathway, e.g., in the hallway. The mobile device can determine current location estimates  1142 ,  1144 ,  1146 , and  1148  that are not along the heading of the mobile device, but are locations the mobile device is likely to be if the mobile device continues on the heading and then turns that follow the hallway. The mobile device can place more current location estimates (e.g., current location estimates  1142 ,  1144 ,  1146 , and  1148 ) in front of the mobile device in the pathway then current location estimates (e.g., current location estimate  1150 ) behind the mobile device. 
     Exemplary Processes 
       FIG. 12  is a flowchart an exemplary procedure  1200  of generating location fingerprint data. Procedure  1200  can be performed by a location server, e.g., location server  102  of  FIG. 1 . 
     The location server can identify ( 1202 ) one or more environment variables to be associated with a venue. Each environment variable can measure a signal. Each environment variable can correspond to a signal source. The signal source can include a wireless access point, a light source, a sound source, a magnetic source, or a heat source. Identifying the one or more environment variables can include receiving an identifier of each signal source from a sampling device (e.g., sampling device  202  of  FIG. 2 ) that is configured to survey the venue. 
     The location server can determine ( 1204 ) multiple locations where the signal is detectable by a sensor of a mobile device when the mobile device is located at the venue. Each location can include location coordinates in a reference frame. For example, when the reference frame is Earth, the location coordinates can include latitude, longitude, and altitude. When the reference frame is the venue, the location coordinates can be vertical and horizontal distances from a given point in the venue. 
     The location server can determine ( 1206 ) location fingerprint data for the venue. The location fingerprint data can include a fingerprint for each of the locations. The fingerprint can include a set of one or more measurements that the mobile device is expected to receive when the mobile device measures the signal at the corresponding location. Each of the measurements can include at least one of an RSSI, a round-trip time, a magnetic field strength, a temperature, a sound level, or an air pressure level. 
     The location fingerprint data can include multi-dimensional data having an environment variable dimension and a location dimension. The environment variable dimension of the location fingerprint data can correspond to the one or more environment variables. The location dimension of the location fingerprint data corresponds to coordinates of the one or more locations. The location dimension can include a longitude sub-dimension, a latitude sub-dimension, and an altitude sub-dimension. One or more values in the location fingerprint data at a given location and given environment variable corresponds to a probability distribution that includes an expected value and a variance of the environment variable at the given location. 
     The location server can determine the location fingerprint data of a venue by surveying the venue. In a survey, the location server can receive, from a sampling device (e.g., sampling device  202  of  FIG. 2 ), measurements of signals from the one or more signal sources at one or more sampling locations. The location server can extrapolate an estimated measurement of the environment variables at each of the locations from the measurement of signals at the one or more sampling locations. The location server can then generate the location fingerprint data based on the received measurements, the extrapolated measurements, and the corresponding locations. 
     In some implementations, extrapolating the estimated measurement can include determining an attenuation of the measurements of signals based on the constraints. The constraints can include one or more walls, floors, or columns. 
     In some implementations, the location server can determine the location fingerprint data of a venue by prediction. Determining the location fingerprint data by prediction can include receiving a map of the venue, and receiving location coordinates of a signal source. The location coordinates can be absolute coordinates (e.g., latitude, longitude, and altitude) or relative coordinates (e.g., on second floor, north wall, three meters from the west corner). The location server can determine multiple locations and designate the locations as sampling points. The location server can determine a transmission characteristics of the signal source. The transmission characteristics can include a propagation pattern (e.g., a rate of attenuation) of a signal from the signal source in space and in various structural barriers (e.g., various types of walls and columns). For each of the sampling points, the location server can determine an expected measurement and a variance of a signal from the signal source based on a location of the signal source, spaces and barriers between the signal source and the sampling point, an estimated propagation pattern of the signal from the signal source in the spaces, and an estimated propagation pattern of the signal from the signal source in the barriers. The location server can store the expected measurements, the variance, an identifier of the signal source, and the corresponding location as the location fingerprint data. 
     The location server can provide ( 1208 ) the location fingerprint data and an identifier of the venue to a mobile device for determining a location of the mobile device at the venue. Providing the location fingerprint data to the mobile device can occur upon an entrance of the mobile device into the venue. The location server can receive a request for location fingerprint data of a venue from the mobile device. In some implementations, the request can be triggered when the mobile device loses reception of GPS signals. The request can include a last location determined by the GPS signals. The location server can determine a venue located at the last location, and provide the location fingerprint data of the venue to the mobile device. In some implementations, the request can be triggered when the mobile device is turned on inside a venue and receives a user request for location determination. The mobile device can send the request to the location server through a wireless access point. Based on an identifier of the wireless access point, the location server can determine a venue and provide location fingerprint data of the venue to the mobile device. 
       FIG. 13  is a flowchart of exemplary procedure  1300  of estimating a location using location fingerprint data. Procedure  1300  can be performed by a mobile device, e.g., mobile device  106  of  FIG. 1 . 
     The mobile device can receive ( 1302 ), from a server (e.g., location server  102  of  FIG. 1 ), location fingerprint data. The location fingerprint data can include multiple locations at a venue and a fingerprint of each location. The venue can include a space accessible by a pedestrian and one or more constraints of movement of the pedestrian. Each fingerprint can include one or more expected measurements of an environment variable at the corresponding location. Each environment variable can include a signal from a signal source detectable by the mobile device. The one or more signal sources can include at least one of an RF source (e.g., a wireless access point), a light source, a sound source, a magnetic source, or a heat source. The one or more expected measurements can include at least one of an RSSI, a round-trip time, a magnetic field strength, a temperature, a noise level, or an air pressure level. 
     The mobile device can receive the location fingerprint data by request. The mobile device can request the location fingerprint data from the server when the mobile device determines that the mobile device is located in proximity to the venue based on a threshold. For example, the mobile device can determine, based on GPS signals and a map stored on the mobile device, that the mobile device is located within a threshold distance to a building. The mobile device can then request location fingerprint data of the building from the server. The mobile device can receive the location fingerprint data in response. 
     The mobile device can receive ( 1304 ) a measurement vector from one or more sensors of the mobile device. The measurement vector can include one or more readings of the one or more sensors on the environment variable. 
     The mobile device can determine ( 1306 ) a location of the mobile device at the venue using the measurement vector and the location fingerprint data. Determining the location can include performing a statistical classification categorizing the measurement vector into one or more possible locations where the measurement vector can be received by the one or more sensors. Each possible location can be associated with a likelihood that the measurement vector matching a fingerprint of the respective possible location. Performing the statistical classification can include categorizing, based on training data, a sample vector to one or more categories each being associated with a probability that the sample vector belongs to the corresponding category. The mobile device can designate the location fingerprint data as the training data. The mobile device can designate the measurement vector as the sample vector. The one or more categories each can correspond to a possible location of the mobile device at the venue. The probability associated with each category can indicate a likelihood that the mobile device is located at the possible location corresponding to the category. 
     The mobile device can determine the probability associated with each category. Determining the probability can include determining a point-wise kernel estimation of a probability density of the measurement vector is measured at each of the possible locations. The point-wise kernel estimation can have a kernel function. The mobile device can apply the kernel function to a difference between the measurement vector and a fingerprint of the respective possible location. The kernel function can be a symmetric function that integrates to one (e.g., a Gaussian function). 
     In some implementations, the mobile device can apply the kernel function to an a priori domain provided by a particle filter. The a priori domain can be a portion of search space represented in the location fingerprint data selected before the probability densities are calculated. The a priori domain can be provided by a particle filter. For example, the a priori domain can be an a posteriori state estimate from the particle filter. 
     In some implementations, determining the location of the mobile device comprises aggregating statistics of a group of possible locations. In some implementations, determining the location of the mobile device can include calculating the location using the group of locations based on a context. The context can be a motion context. The context can include one or more readings of at least one of an accelerometer, a magnetic sensor, a gyroscope, or a barometer. 
       FIG. 14  is a flowchart of exemplary procedure  1400  of estimating a location using a particle filter. Exemplary procedure  1400  can be performed by a mobile device, e.g., mobile device  106  of  FIG. 1 . 
     The mobile device can determine ( 1402 ) an initial location of the mobile device. The initial location can be at a venue (e.g., inside of a building). The venue can include a space accessible by a pedestrian and one or more constraints of movement of the pedestrian. The initial location can be an a priori location estimate being associated with a given uncertainty value. In some implementations, determining the initial location can include estimating the initial location based on a prior location observation using scan analyzer  116  of  FIG. 1 . In some implementations, when an initial observation is unavailable, the initial location can be a random location at or near the venue having an initial uncertainty value (e.g., plus or minus 1000 meters), or a last known location determined by GPS signals having an initial uncertainty value (e.g., a value calculated based on time of the last GPS location determination and current time). When the mobile device has no prior location knowledge (e.g., when a new device is turned on for the first time inside of a building), the mobile device can determine that the initial location is a random location, and the uncertainty value is infinity. 
     The mobile device can determine ( 1404 ), based on a reading of a sensor of the mobile device, a state of motion of the mobile device. Determining the state of motion can include determining at least one of a speed or a heading of the mobile device, or rate of change of the speed or heading of the mobile device. The speed, heading, and rate of change of the speed or heading can be determined based on a reading of at least one of an accelerometer, a magnetometer, a barometer, or a gyroscope of the mobile device. 
     The mobile device can determine ( 1406 ) multiple candidate location of the mobile device based at least in part on the initial location, the state of motion, and a map of the venue specifying the one or more constraints. Determining the candidate locations can include determining whether the mobile device is stationary. If the mobile device is stationary, the mobile device can generate the candidate locations based on a state space system noise model, e.g., by generating the candidate locations randomly around the initial location. If the mobile device moves, the mobile device can determine a likelihood that the mobile device is moving from the initial location in a direction that avoids the constraints. The mobile device can then generate the candidate locations. The mobile device can generate more candidate locations are generated in a direction that is associated with a higher likelihood (e.g., a direction that is along a heading of the mobile device). 
     In some implementations, determining the likelihood that the mobile device is moving from the initial location in the direction that avoids the constraints can include determining a path (e.g., hallway) of the venue based on the constraints. The mobile device can determine a destination type of a point the path based on the map. The destination type (e.g., office, cafeteria, or lobby) can be indicative of a likelihood that the pedestrian will move toward a destination of the path when the pedestrian is moving along the path. The point can be located at an end of the path or on the path. The mobile device can determine the likelihood that the mobile device is moving from the initial location in the direction based on the destination type of the path. For example, if the destination type of a point in the middle of the path is a cafeteria, lobby, or conference room, the mobile device can determine that a pedestrian is more likely to enter the cafeteria or lobby than if the destination type of the point is an office. 
     The mobile device can determine whether the candidate locations are depleted. The mobile device can determine that a count of the one or more candidate locations satisfies a depletion threshold. Upon such determination, the mobile device can generate a candidate location at a random location in the venue for location determination. 
     The mobile device can receive ( 1408 ) a location observation. The location observation can include an estimated location of the mobile device in the space of the venue. The estimated location can be determined based on readings of one or more sensors of the mobile device and location fingerprint data describing attributes of signals measurable by the one or more sensors when the mobile device is at the venue. 
     The mobile device can filter ( 1410 ) the candidate locations using the location observation, including determining a likely location of the mobile device based on the candidate locations, the observation, and a probability model. Determining the likely location of the mobile device can include determining a probability density based on the candidate locations. 
     The mobile device can provide ( 1412 ) the likely location for output as a current location of the mobile device. The mobile device can designate the current location as an initial location for estimating a next current location of the mobile device. Providing the likely location for output can include displaying the likely location as a pin on a map of the venue displayed on a screen of the mobile device. 
     Exemplary System Architecture 
       FIG. 15  is an exemplary user interface for displaying a location of a mobile device at a venue. The mobile device can be mobile device  106  as described in reference to  FIG. 1 . 
     The user interface can include map  1502  of a venue, e.g., a building. Map  1502  can include walls, spaces, rooms, and room designations of a particular floor. The mobile device can estimate a current location of the mobile device, and provide the current location for display as location marker  1504  in map  1502  on a display device of the mobile device. The mobile device can determine which floor is displayed based on an altitude aspect of the estimate a current location of the mobile device. The estimated location can include an uncertainty region. The uncertainty region can include a region around the estimated current location where probability density of the mobile device is located in locations in the region exceeds a threshold. The uncertainty region can be displayed as uncertainty region area  1506  around location marker  1504 . Uncertainty region and uncertainty region area  1506  need not be a perfectly circular area, given locations rendered impossible by movement constraints in venue  204  and motion speed of a pedestrian. 
     The user interface can include search box  1508 . Search box  1508  can be configured to receive input for a search term. Upon receiving the search term through search box  1508 , the mobile device can search data associated with map  1502  and determine if the search term matches a portion of the venue. The mobile device can emphasize or otherwise mark the portion if a match is found. For example, when the mobile device receives a search term “kitchen” and a portion of the venue is designated as “kitchen,” the mobile device can highlight the kitchen portion on map  1502 . In some implementations, the mobile device can designate the found portion (e.g., “kitchen”) as a destination. The mobile device can determine path  1510  that leads from the current location to the destination, and display path  1510  on map  1502 . 
     Exemplary System Architecture 
       FIG. 16  is a block diagram of an exemplary system architecture for implementing the features and operations of  FIGS. 1-15 . Other architectures are possible, including architectures with more or fewer components. In some implementations, architecture  1600  includes one or more processors  1602  (e.g., dual-core Intel® Xeon® Processors), one or more output devices  1604  (e.g., LCD), one or more network interfaces  1606 , one or more input devices  1608  (e.g., mouse, keyboard, touch-sensitive display) and one or more computer-readable mediums  1612  (e.g., RAM, ROM, SDRAM, hard disk, optical disk, flash memory, etc.). These components can exchange communications and data over one or more communication channels  1610  (e.g., buses), which can utilize various hardware and software for facilitating the transfer of data and control signals between components. 
     The term “computer-readable medium” refers to a medium that participates in providing instructions to processor  1602  for execution, including without limitation, non-volatile media (e.g., optical or magnetic disks), volatile media (e.g., memory) and transmission media. Transmission media includes, without limitation, coaxial cables, copper wire and fiber optics. 
     Computer-readable medium  1612  can further include operating system  1614  (e.g., a Linux® operating system), network communication module  1616 , survey manager  1620 , fingerprint manager  1630 , and fingerprint distributor  1640 . Operating system  1614  can be multi-user, multiprocessing, multitasking, multithreading, real time, etc. Operating system  1614  performs basic tasks, including but not limited to: recognizing input from and providing output to devices  1606 ,  1608 ; keeping track and managing files and directories on computer-readable mediums  1612  (e.g., memory or a storage device); controlling peripheral devices; and managing traffic on the one or more communication channels  1610 . Network communications module  1616  includes various components for establishing and maintaining network connections (e.g., software for implementing communication protocols, such as TCP/IP, HTTP, etc.). 
     Survey manager  1620  can include computer instructions that, when executed, cause processor  1602  to provide survey instructions and maps to a sampling device (e.g., sampling device  202  of  FIG. 2 ) and receive survey data from the sampling device. Fingerprint manager  1630  can include computer instructions that, when executed, cause processor  1602  to perform operations of signal estimator  110  and fingerprint engine  108  as described above in reference to  FIG. 1 . Fingerprint distributor  1640  can include computer instructions that, when executed, cause processor  1602  to respond a fingerprint request from a mobile device (e.g., mobile device  106  of  FIG. 1 ), including sending location fingerprint data to the requesting mobile device. 
     Architecture  1600  can be implemented in a parallel processing or peer-to-peer infrastructure or on a single device with one or more processors. Software can include multiple software components or can be a single body of code. 
     The described features can be implemented advantageously in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a data storage system, at least one input device, and at least one output device. A computer program is a set of instructions that can be used, directly or indirectly, in a computer to perform a certain activity or bring about a certain result. A computer program can be written in any form of programming language (e.g., Objective-C, Java), including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, a browser-based web application, or other unit suitable for use in a computing environment. 
     Suitable processors for the execution of a program of instructions include, by way of example, both general and special purpose microprocessors, and the sole processor or one of multiple processors or cores, of any kind of computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memories for storing instructions and data. Generally, a computer will also include, or be operatively coupled to communicate with, one or more mass storage devices for storing data files; such devices include magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and optical disks. Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, ASICs (application-specific integrated circuits). 
     To provide for interaction with a user, the features can be implemented on a computer having a display device such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor or a retina display device for displaying information to the user. The computer can have a touch surface input device (e.g., a touch screen) or a keyboard and a pointing device such as a mouse or a trackball by which the user can provide input to the computer. The computer can have a voice input device for receiving voice commands from the user. 
     The features can be implemented in a computer system that includes a back-end component, such as a data server, or that includes a middleware component, such as an application server or an Internet server, or that includes a front-end component, such as a client computer having a graphical user interface or an Internet browser, or any combination of them. The components of the system can be connected by any form or medium of digital data communication such as a communication network. Examples of communication networks include, e.g., a LAN, a WAN, and the computers and networks forming the Internet. 
     The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In some embodiments, a server transmits data (e.g., an HTML page) to a client device (e.g., for purposes of displaying data to and receiving user input from a user interacting with the client device). Data generated at the client device (e.g., a result of the user interaction) can be received from the client device at the server. 
     A system of one or more computers can be configured to perform particular actions by virtue of having software, firmware, hardware, or a combination of them installed on the system that in operation causes or cause the system to perform the actions. One or more computer programs can be configured to perform particular actions by virtue of including instructions that, when executed by data processing apparatus, cause the apparatus to perform the actions. 
     While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any inventions or of what may be claimed, but rather as descriptions of features specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination. 
     Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. 
     Thus, particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous. 
     Exemplary Mobile Device Architecture 
       FIG. 17  is a block diagram of an exemplary architecture  1700  for the mobile devices of  FIGS. 1-15 . A mobile device (e.g., mobile device  106 ) can include memory interface  1702 , one or more data processors, image processors and/or processors  1704 , and peripherals interface  1706 . Memory interface  1702 , one or more processors  1704  and/or peripherals interface  1706  can be separate components or can be integrated in one or more integrated circuits. Processors  1704  can include application processors, baseband processors, and wireless processors. The various components in mobile device  106 , for example, can be coupled by one or more communication buses or signal lines. 
     Sensors, devices, and subsystems can be coupled to peripherals interface  1706  to facilitate multiple functionalities. For example, motion sensor  1710 , light sensor  1712 , and proximity sensor  1714  can be coupled to peripherals interface  1706  to facilitate orientation, lighting, and proximity functions of the mobile device. Location processor  1715  (e.g., GPS receiver) can be connected to peripherals interface  1706  to provide geopositioning. Electronic magnetometer  1716  (e.g., an integrated circuit chip) can also be connected to peripherals interface  1706  to provide data that can be used to determine the direction of magnetic North. Thus, electronic magnetometer  1716  can be used as an electronic compass. Motion sensor  1710  can include one or more accelerometers configured to determine change of speed and direction of movement of the mobile device. Barometer  1717  can include one or more devices connected to peripherals interface  1706  and configured to measure pressure of atmosphere around the mobile device. 
     Camera subsystem  1720  and an optical sensor  1722 , e.g., a charged coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) optical sensor, can be utilized to facilitate camera functions, such as recording photographs and video clips. 
     Communication functions can be facilitated through one or more wireless communication subsystems  1724 , which can include radio frequency receivers and transmitters and/or optical (e.g., infrared) receivers and transmitters. The specific design and implementation of the communication subsystem  1724  can depend on the communication network(s) over which a mobile device is intended to operate. For example, a mobile device can include communication subsystems  1724  designed to operate over a GSM network, a GPRS network, an EDGE network, a Wi-Fi™ or WiMax™ network, and a Bluetooth™ network. In particular, the wireless communication subsystems  1724  can include hosting protocols such that the mobile device can be configured as a base station for other wireless devices. 
     Audio subsystem  1726  can be coupled to a speaker  1728  and a microphone  1730  to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, and telephony functions. Audio subsystem  1726  can be configured to receive voice commands from the user. 
     I/O subsystem  1740  can include touch screen controller  1742  and/or other input controller(s)  1744 . Touch-screen controller  1742  can be coupled to a touch screen  1746  or pad. Touch screen  1746  and touch screen controller  1742  can, for example, detect contact and movement or break thereof using any of a plurality of touch sensitivity technologies, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen  1746 . 
     Other input controller(s)  1744  can be coupled to other input/control devices  1748 , such as one or more buttons, rocker switches, thumb-wheel, infrared port, USB port, and/or a pointer device such as a stylus. The one or more buttons (not shown) can include an up/down button for volume control of speaker  1728  and/or microphone  1730 . 
     In one implementation, a pressing of the button for a first duration may disengage a lock of the touch screen  1746 ; and a pressing of the button for a second duration that is longer than the first duration may turn power to mobile device  106  on or off. The user may be able to customize a functionality of one or more of the buttons. The touch screen  1746  can, for example, also be used to implement virtual or soft buttons and/or a keyboard. 
     In some implementations, mobile device  106  can present recorded audio and/or video files, such as MP3, AAC, and MPEG files. In some implementations, mobile device  106  can include the functionality of an MP3 player. Mobile device  106  may, therefore, include a pin connector that is compatible with the iPod. Other input/output and control devices can also be used. 
     Memory interface  1702  can be coupled to memory  1750 . Memory  1750  can include high-speed random access memory and/or non-volatile memory, such as one or more magnetic disk storage devices, one or more optical storage devices, and/or flash memory (e.g., NAND, NOR). Memory  1750  can store operating system  1752 , such as Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks. Operating system  1752  may include instructions for handling basic system services and for performing hardware dependent tasks. In some implementations, operating system  1752  can include a kernel (e.g., UNIX kernel). 
     Memory  1750  may also store communication instructions  1754  to facilitate communicating with one or more additional devices, one or more computers and/or one or more servers. Memory  1750  may include graphical user interface instructions  1756  to facilitate graphic user interface processing; sensor processing instructions  1758  to facilitate sensor-related processing and functions; phone instructions  1760  to facilitate phone-related processes and functions; electronic messaging instructions  1762  to facilitate electronic-messaging related processes and functions; web browsing instructions  1764  to facilitate web browsing-related processes and functions; media processing instructions  1766  to facilitate media processing-related processes and functions; GPS/Navigation instructions  1768  to facilitate GPS and navigation-related processes and instructions; camera instructions  1770  to facilitate camera-related processes and functions; magnetometer data  1772  and calibration instructions  1774  to facilitate magnetometer calibration. The memory  1750  may also store other software instructions (not shown), such as security instructions, web video instructions to facilitate web video-related processes and functions, and/or web shopping instructions to facilitate web shopping-related processes and functions. In some implementations, the media processing instructions  1766  are divided into audio processing instructions and video processing instructions to facilitate audio processing-related processes and functions and video processing-related processes and functions, respectively. An activation record and International Mobile Equipment Identity (IMEI) or similar hardware identifier can also be stored in memory  1750 . Memory  1750  can include venue location instructions  1776  that can be used to request location fingerprint data and determine a location of the mobile device when the mobile device is at a venue, e.g., inside of a building where GPS signals are unavailable. 
     Each of the above identified instructions and applications can correspond to a set of instructions for performing one or more functions described above. These instructions need not be implemented as separate software programs, procedures, or modules. Memory  1750  can include additional instructions or fewer instructions. Furthermore, various functions of the mobile device may be implemented in hardware and/or in software, including in one or more signal processing and/or application specific integrated circuits. 
     Exemplary Operating Environment 
       FIG. 18  is a block diagram of an exemplary network operating environment  1800  for the mobile devices of  FIGS. 1-15 . Mobile devices  1802   a  and  1802   b  can, for example, communicate over one or more wired and/or wireless networks  1810  in data communication. For example, a wireless network  1812 , e.g., a cellular network, can communicate with a wide area network (WAN)  1814 , such as the Internet, by use of a gateway  1816 . Likewise, an access device  1818 , such as an 802.11g wireless access point, can provide communication access to the wide area network  1814 . 
     In some implementations, both voice and data communications can be established over wireless network  1812  and the access device  1818 . For example, mobile device  1802   a  can place and receive phone calls (e.g., using voice over Internet Protocol (VoIP) protocols), send and receive e-mail messages (e.g., using Post Office Protocol 3 (POP3)), and retrieve electronic documents and/or streams, such as web pages, photographs, and videos, over wireless network  1812 , gateway  1816 , and wide area network  1814  (e.g., using Transmission Control Protocol/Internet Protocol (TCP/IP) or User Datagram Protocol (UDP)). Likewise, in some implementations, the mobile device  1802   b  can place and receive phone calls, send and receive e-mail messages, and retrieve electronic documents over the access device  1818  and the wide area network  1814 . In some implementations, mobile device  1802   a  or  1802   b  can be physically connected to the access device  1818  using one or more cables and the access device  1818  can be a personal computer. In this configuration, mobile device  1802   a  or  1802   b  can be referred to as a “tethered” device. 
     Mobile devices  1802   a  and  1802   b  can also establish communications by other means. For example, wireless device  1802   a  can communicate with other wireless devices, e.g., other mobile devices, cell phones, etc., over the wireless network  1812 . Likewise, mobile devices  1802   a  and  1802   b  can establish peer-to-peer communications  1820 , e.g., a personal area network, by use of one or more communication subsystems, such as the Bluetooth™ communication devices. Other communication protocols and topologies can also be implemented. 
     The mobile device  1802   a  or  1802   b  can, for example, communicate with one or more services  1830  and  1840  over the one or more wired and/or wireless networks. For example, one or more location services  1830  can conduct surveys of venues, generate location fingerprint data for each venue, and provide the location fingerprint data to mobile device  1802   a  or  1802   b . Map service  1840  can, for example, provide maps of venues, e.g., maps of structures of buildings to mobile device  1802   a  or  1802   b.    
     Mobile device  1802   a  or  1802   b  can also access other data and content over the one or more wired and/or wireless networks. For example, content publishers, such as news sites, Really Simple Syndication (RSS) feeds, web sites, blogs, social networking sites, developer networks, etc., can be accessed by mobile device  1802   a  or  1802   b . Such access can be provided by invocation of a web browsing function or application (e.g., a browser) in response to a user touching, for example, a Web object. 
     A number of implementations of the invention have been described. Nevertheless, it will be understood that various modifications can be made without departing from the spirit and scope of the invention.

Metadata:
Filing Date: 20121214
Publication Date: 20150127
Grant Date: 20150127
Priority Date: 20121214
Inventors: MARTI LUKAS M.
MAYOR ROBERT
MA SHANNON M.
Assignee: APPLE INC
CPC Classifications: [{"code": "G01S5/0278", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04W4/025", "inventive": true, "first": true, "tree": "[]"}, {"code": "G01S5/02", "inventive": true, "first": true, "tree": "[]"}, {"code": "G01S5/0294", "inventive": true, "first": false, "tree": "[]"}, {"code": "G01S5/0294", "inventive": true, "first": false, "tree": "[]"}, {"code": "G01S5/0278", "inventive": true, "first": true, "tree": "[]"}, {"code": "G01S5/02522", "inventive": true, "first": false, "tree": "[]"}, {"code": "G01S5/02522", "inventive": true, "first": false, "tree": "[]"}, {"code": "G01S5/02522", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04W4/025", "inventive": true, "first": true, "tree": "[]"}, {"code": "G01S5/0278", "inventive": true, "first": false, "tree": "[]"}, {"code": "G01S5/0252", "inventive": true, "first": false, "tree": "[]"}, {"code": "G01S5/0294", "inventive": true, "first": false, "tree": "[]"}]
Family ID: 49841808