SYSTEM AND METHOD FOR DETERMINING HEIGHT OF A MOBILE DEVICE FROM A SURFACE - Patent application

Abstract

Determining one or more heights of one or more mobile devices above a surface. Specific embodiments described herein include an apparatus that acquires first data (e.g., measurements determined by sensors on the mobile devices or estimated locations of the mobile devices), determines a location context based on the first data, identifies second data (e.g., measurements determined by sensors on the mobile devices or status indicators of equipment on the mobile devices) to acquire for use in determining the estimated height at which the mobile devices are located above the surface based on the determined location context, acquires the second data, and determines the estimated height at which the mobile devices are located above the surface based on the acquired second data.

Description

[Technical field]

[0001] Background technology Knowing the height at which a mobile device is located above a surface (e.g., an outdoor ground surface or a floor of a structure) has many valuable uses. For example, the height above a surface can be used to calibrate a pressure sensor in the mobile device, estimate the altitude of the mobile device relative to a known altitude of a surface, or estimate the altitude of a surface (e.g., a building floor). Past approaches have typically assumed that the mobile device is located at a commonly expected height above the surface, such as approximately 0.9 meters or 3 feet, which corresponds to the height of something the mobile device might be placed on (e.g., furniture, a pocket, or a bag). In some cases, the commonly expected height above the surface can differ from the true height of the mobile device above the surface by more than a meter (e.g., when the mobile device is held against a user's ear during a call rather than in the user's pocket). Thus, the use of the commonly expected height is unreliable, and using the commonly expected height in different cases leads to potentially unacceptable results and results that could be improved. As a result, a more accurate estimate of the height at which a mobile device is located above a surface would be advantageous to use in improving the usefulness of the height. SUMMARY OF THE DISCLOSURE Systems and methods for determining an improved estimated height of a mobile device are described herein. [Brief description of the drawings]

[0002] [Figure 1] FIG. 1 illustrates an environment in which systems and methods for determining the height of a mobile device from a surface may function.

[0003] [Figure 2A] FIG. 2 illustrates a first process for determining the height of a mobile device from a surface. [Figure 2B] FIG. 13 illustrates a second process for determining the height of a mobile device from a surface.

[0004] [Figure 3A-H] FIG. 1 illustrates a process for estimating the height at which a mobile device is located above a surface based on a determined position context and other data.

[0005] [Figure 4] FIG. 1 illustrates transmitter, mobile device, and server components of an environment in which systems and methods for determining the height of a mobile device above a surface may function. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0006] Systems and methods for determining the height of a mobile device above a surface are described. For purposes of illustration, FIG. 1 illustrates an environment 100 including a positioning system (e.g., a network of terrestrial transmitters 110 and / or a network of satellites 150) configured to transmit positioning signals used to estimate the location of a mobile device 120, as is known to those skilled in the art. The estimated location may be determined at the mobile device 120 or at a server 130. By way of example, the mobile device 120 may be a mobile phone or other wireless communication device, a portable computer, a navigation device, a tracking device, a receiver, or other suitable device. Examples of possible components of the transmitter 110, the mobile device 120, and the server 130 are illustrated in FIG. 4 and discussed in the "Other Aspects" section near the end of this specification and elsewhere herein. Pressure and temperature sensors (not shown) may be co-located with any of the transmitters 110 to determine the unknown altitude h of a particular mobile device according to the well-known barometric pressure equation: mobile It is possible to generate pressure and temperature measurements that are used to estimate JPEG0007635127000001.jpg21153...(Formula 1) Here, P mobile is the pressure estimate obtained from the pressure sensor on the mobile device, and P sensoris the estimate of pressure, T is the estimate of temperature from the transmitter location, and h sensor is the estimated altitude of the transmitter, and g is the acceleration due to gravity (e.g., -9.8 m / s 2 ), where R is the gas constant and M is the molar mass of the atmosphere. Altitude estimates often have some level of error due to drift in the pressure sensor of the mobile device, necessitating accurate calibration of the pressure sensor over time. Some aspects of the invention relate to determining the height at which a mobile device is located above a surface, which can also be used to calibrate the pressure sensor of the mobile device, among other applications.

[0007] As described herein, various "position contexts" of a mobile device can be determined, and the determined position contexts can be used to estimate the height at which the mobile device is located above a surface (e.g., the ground, a floor, or other type of surface). The resulting estimated height has many uses, as described herein below, including use in calibrating a pressure sensor of the mobile device, use in estimating the altitude of the mobile device, or use in estimating the altitude of a surface. By way of example, the position contexts can include a state where a particular mobile device is in a known location, a state where a particular mobile device is stationary, a state where a particular mobile device is mounted on a bicycle, a state where a particular mobile device is with a user walking or running, a state where a particular mobile device is in a vehicle, or other position contexts described herein. For purposes of illustration, FIG. 1 illustrates some of the aforementioned position contexts. As described herein below, a particular position context of a particular mobile device can be determined using first data, and the determined position context is then used in conjunction with second data to determine an estimated height at which the mobile device is located above a surface. More details regarding the first data and second data are provided below.

[0008] Various approaches for estimating the height at which a mobile device is located relative to a surface are described herein, including (i) using first data to identify a location context, using the location context to identify second data, and using the second data to determine an estimated height; and (ii) using the first data to identify a location context, using the location context to identify possible estimated heights, using the possible estimated heights to identify second data, and using the second data to select an estimated height from among the possible estimated heights. As shown in FIG. 1, one or more data sources 140 can be used to store the various location contexts. For each location context, data source 140 may store first data used to identify the location context from among other location contexts, and may store specific second data and / or specific possible heights in association with the particular location context. In some embodiments, the specific possible heights are stored in association only with the specific second data, and the second data is stored in association with the particular location context.

[0009] A first process for determining the height of a mobile device from a surface is shown in FIG. 2A and includes the steps of: acquiring (210) first data including one or more of (i) at least one measurement result determined by at least one sensor of the mobile device and (ii) at least one estimated position of the mobile device; determining (220) a location context based on the first data; identifying (230) second data to acquire for use in determining an estimated height of the mobile device from the surface based on the determined location context, the second data including one or more of (i) at least one measurement result determined by at least one sensor of the mobile device and (ii) at least one condition indicator of equipment of the mobile device; acquiring (240) the second data; determining (250) an estimated height of the mobile device from the surface based on the acquired second data; and (optionally) using the estimated height from the surface to achieve a result (260). An embodiment of each of these steps is described below.

[0010] Initially, first data is acquired (210). In alternative embodiments of step 210, the first data includes (i) at least one measurement determined by at least one sensor of the mobile device, (ii) at least one estimated location of the mobile device, or both (i) and (ii). By way of example, acquiring data in step 210 may include receiving data from a source of data (e.g., a sensor, memory, or other data source) and, if desired, requesting data from the source of data. The request may be in any known manner.

[0011] A location context is determined (220) based on the first data. The location context identifies a location situation of the mobile device that can be used to determine the height of the mobile device above a surface. In one embodiment of step 220, the determined location context identifies the mobile device as being in a known location (e.g., the mobile phone user's residence or workplace, or other type of area or location). In another embodiment of step 220, the location context identifies an estimated location situation of the mobile device as being one of: (i) with a user on foot, (ii) on or with a user riding a bicycle, (iii) in a vehicle, such as an automobile or public transportation, (iv) stationary, and (v) on a surface after a fall. For such alternative embodiments, the location context may be selected from a set of possible location contexts including different combinations of the estimated location conditions (i)-(v), thereby enabling customized implementations, such as a first embodiment with a set of one possible location context, a second embodiment with a set of two possible location contexts, a third embodiment with a set of three possible location contexts, a fourth embodiment with a set of four possible location contexts, and a fifth embodiment with a set of five possible location contexts. An example of determining different location contexts based on different values ​​of the first data is provided below in the section entitled "Determining Location Context Based on Acquired First Data."

[0012] Based on the determined location context, second data to be acquired is identified (230) for use in determining an estimated height at which the mobile device is located above the surface. In another embodiment of step 230, the second data includes (i) at least one measurement result obtained by at least one sensor of the mobile device, (ii) at least one condition indicator of equipment of the mobile device, or both (i) and (ii). Examples of various second data are provided below under the heading "Second Data". In a first embodiment of step 230, one or more types of data related to the determined location context are identified as the second data to be acquired. As an example, the determined location context may be used in a search query of a data source that stores various data types, each having an association to a location context, and the determined location context is used to search for the data type related to the location context as the second data to be acquired. The stored data type may be an identifier that specifies a particular type of data to be acquired, such as, for example, either a measurement result obtained from a sensor of the mobile device or one or more condition indicators from an API of the mobile device. In a second embodiment of step 230, one or more values ​​of data associated with the determined location context are identified as second data to be obtained. As an example, the determined location context may be used in a search query of a data source that stores various data associated with any number of location contexts, and the determined location context is used to search all values ​​of data associated with the location context as second data to be obtained. For example, the stored data may be measurements obtained by a sensor of the mobile device, or one or more situation indicators from an API of the mobile device. As an example, FIG. 1 shows a data source 140 that stores various sets of data types or data values ​​(e.g., second data 1 to second data N), each set of data types or data values ​​being associated with one or more location contexts (e.g., location context 1 to location context N).In some implementations of the first and second embodiments of step 230, additional data types or data values ​​associated with another location context other than the determined location context may also be identified for search without regard to the determined location context, or such additional data types or data values ​​may be excluded from the search. Also, previously obtained values ​​of data obtained in association with a previously determined location context may be cached for later retrieval in case the currently determined location context is identical to the previous location context and a new value for that data is not available.

[0013] Second data is acquired (240). By way of example, acquiring data at step 240 may include receiving data from a source of data (e.g., a sensor, a memory, a data source, or any other suitable source of data) and, optionally, requesting data from the source of data. The request may be in any known manner.

[0014] Based on the acquired second data, an estimated height at which the mobile device is located relative to the surface is determined 250. Examples of determining various estimated heights based on various location contexts and associated second data are shown in Figures 3A-3H, which are described below.

[0015] If necessary, an estimated height from the surface is used to arrive at the result (260). In a first embodiment of optional step 260, the estimated height above the surface is used to calibrate a pressure sensor of the mobile device based on the difference between the estimated altitude of the mobile device and the sum of the known altitude of the surface and the estimated height determined in step 250. By way of example, the estimated altitude of the mobile device may be determined using any known means (e.g., satellite or terrestrial positioning systems, barometric positioning systems, or otherwise), and the description in the section entitled "Calibration" herein shows how the estimated height above the surface can be used to calibrate a pressure sensor of the mobile device. A second embodiment of optional step 260 uses an estimated height above the surface to determine an estimated altitude of the mobile device as the sum of the known altitude of the surface and the estimated altitude determined in step 250. By way of example, the known altitude of the surface may be accessed from a data source, such as a building or terrain database that stores known altitudes in association with a location matching the initial estimated location of the mobile device, or with a local beacon (e.g., a WiFi beacon) in communication with the mobile device, a floor or location identified by the user of the mobile device, or other information. A third optional embodiment of step 260 uses an estimated height above the surface to estimate the altitude of the surface as the difference between the estimated altitude of the mobile device and the estimated height determined in step 250. By way of example, the estimated altitude of the mobile device may be determined using any known means (e.g., a satellite or terrestrial positioning system, a barometric positioning system, or otherwise).

[0016] A second process for determining a height of a mobile device from a surface is shown in FIG. 2B and includes the steps of: obtaining (215) first data including one or more of: (i) at least one measurement obtained by at least one sensor of the mobile device; and (ii) at least one estimated location of the mobile device; determining (225) a location context based on the first data; identifying (235) one or more possible estimated heights from the surface at which the mobile device is located based on the determined location context; and (optionally) determining (245) whether the one or more possible estimated heights include two or more possible estimated heights. ), (optionally) if the one or more possible estimated heights include only one possible estimated height, selecting (255) the one possible estimated height as the height above the surface at which the mobile device is located, identifying (265) second data to acquire for use in selecting one of the possible estimated heights as the estimated height above the surface at which the mobile device is located, acquiring (275) the second data, using the acquired second data to determine (285) which of the possible estimated heights is the estimated height above the surface at which the mobile device is located, and (optionally) using the estimated height above the surface to achieve a result (295). Each of these steps is described below.

[0017] First data is acquired 215, and based on the first data, a location context is determined 225. Details of steps 215 and 225 are the same as details of steps 210 and 220 of FIG.

[0018] Based on the determined location context, one or more possible estimated heights from a surface at which the mobile device is located are identified 235. As an example, the one or more possible heights may be stored in association with the determined location context in a data source, and the determined location context may be used in a search query of the data source to retrieve the one or more possible estimated heights.

[0019] Optionally, a determination is made (245) as to whether the one or more possible estimated heights include more than one possible estimated height, which may be a simple query of the number of possible heights, or a determination as to whether the number of possible heights is greater than one, and if the one or more possible estimated heights include only one possible estimated height, then that one possible estimated height is selected (255) as the height at which the mobile device is located from the surface.

[0020] The second data to be acquired is identified (265) for use in selecting one of the possible estimated heights as the height at which the mobile device is located from the surface. As an example, one or more possible estimated heights may be stored in a data source in association with a respective set of second data, and the identified possible estimated heights may be used in a search query to the data source to retrieve second data related to the possible estimated heights. Alternatively, the determined location context may retrieve both the possible estimated heights and the second data related to the possible estimated heights. Details of step 265 are the same as details of step 230 of FIG. 2A.

[0021] The identified second data is then obtained 275. The details of step 275 are the same as the details of step 240 of FIG.

[0022] One of the possible estimated heights is selected as the estimated height at which the mobile device is located from the surface based on the acquired second data (285). Examples of determining different estimated heights based on different second data are shown in Figures 3A-3H, which are described below. The determined estimated height is the selected height.

[0023] If necessary, an estimated height from the surface is used to arrive at the result 295. The details of step 295 are the same as the details of step 260 of Figure 2A.

[0024] 2A and 2B, including (i) different approaches for determining a location context based on acquired first data, (ii) examples of second data, and (iii) different approaches for estimating the height at which the mobile device is located above a surface. Before proceeding, attention is directed to examples of mobile device equipment that may be involved in the various embodiments described below. As an example, such an arrangement of a mobile device (e.g., any of the mobile devices 120 in FIG. 1) is shown in FIG. 4, where the mobile device may include a transmitter interface 21 for exchanging information with a transmitter (e.g., an antenna and RF front-end components, as known or otherwise disclosed herein), one or more processors 22, a memory / data source 23 for storing and retrieving data and instructions from modules related to the methods of operation described herein or other processing that may be performed by the processor 22 or other components, a user interface 26 (e.g., a display, keyboard, microphone, speaker, etc.) for allowing a user to provide input and receive output, another interface 27 (e.g., an antenna, network interface, or other known wired or wireless link) for exchanging information with a server or other device external to the mobile device, a GNSS interface and GNSS processing unit (not shown), and any other components of a typical mobile device known to those of skill in the art. The mobile device may include various sensors 24 (e.g., an accelerometer for measuring the acceleration of the mobile device, a gyroscope for measuring the orientation of the mobile device, an optional inertial measurement unit (IMU) for otherwise measuring the motion aspects of the mobile device, a pressure sensor for measuring the pressure at altitude of the mobile device, a temperature sensor for measuring the internal temperature of the mobile device, a light sensor for measuring ambient light, a microphone for measuring sound, a camera for capturing images, or other known sensors).These sensors are used to generate data (e.g., first data and / or second data), as described below. The mobile device may also include one or more application programming interfaces (APIs) 25 that provide various condition indicators, as described below in the "Second Data" section.

[0025] As shown in FIG. 4, memory / data source 23 may include memory that stores software modules containing executable instructions, and processor 22 may execute instructions from the modules to perform various operations, including (i) performing some or all of the methods described herein or that one of ordinary skill in the art would understand to be executable on a mobile device (e.g., at least one of determining a location context, estimating a height, using the estimated height, obtaining first data, and obtaining second data), (ii) estimating an altitude of the mobile device, (iii) processing received GNSS or terrestrial signals to determine location information (e.g., at least one of a time of arrival or time of travel of the received signal, a pseudorange between the mobile device and the transmitters, atmospheric information from the transmitters, and a position associated with each transmitter, or other information), (iv) using the location information to compute an estimated position of the mobile device, (v) determining movement based on measurements from an inertial sensor in the mobile device, or (vi) processing otherwise required by the operations described herein.

[0026] [Determining the location context based on the first data acquired] In one embodiment of step 220 of FIG. 2A or step 225 of FIG. 2B, the location context determines an estimated location status of the mobile device as being one of: (i) with a user on foot, (ii) with a user on a bicycle, (iii) in a vehicle, (iv) stationary, and (v) on the ground or floor after a fall. Any combination of the estimated location situations of the mobile device (e.g., with a user on foot, on or attached to a user on a bicycle, in a vehicle, stationary, or on the ground or floor after a drop) can be considered as a location context that may arise in various embodiments, such as only one of the estimated location situations being determined in a first embodiment (e.g., the location context determining whether or not the location is stationary), only two of the estimated location situations being determined in a second embodiment (e.g., the location context determining whether or not the location is with a user on foot or in a vehicle), only three of the estimated location situations being determined in a third embodiment, only four of the estimated location situations being determined in a fourth embodiment, or all five of the estimated location situations being determined in a fifth embodiment.

[0027] If the first data includes one or more measurements determined by one or more inertial sensors of the mobile device (e.g., an inertial measurement unit (IMU), a separate accelerometer, and / or a separate gyroscope), determining the location context based on the first data may use any of the various combinations of decisions described below with respect to the first through fifth sets of embodiments.

[0028] In a first set of embodiments, the determined location context identifies an estimated location situation of the mobile device as being with a user on foot (e.g., walking or running) when one or more measurements indicate a movement associated with the user while walking or running. In another embodiment, the one or more measurements indicate a walking or running movement by a user if they represent a stepping movement of the user (e.g., a repetitive movement recorded over time associated with a walking or running movement, as known to those skilled in the art) or include periodic measurements of the same angular orientation (or periodic measurements of the same series of angular orientations) from a gyroscope indicating a direction (or directions) in which the mobile device is periodically oriented when carried by a walking or running user (e.g., when carried in the user's hand or pocket).

[0029] In a second set of embodiments, the determined location context identifies an estimated location status of the mobile device as being on or with a user on a bicycle when one or more measurements indicate motion associated with a moving bicycle. In one embodiment, one or more measurements indicate motion associated with a moving bicycle when the motion measured by the mobile device's IMU includes vibrations when traveling on an uneven bicycle path, such as a particular vibration that may be represented by sporadic, irregular, or consistent up and down Z-axis acceleration of various degrees of acceleration. As an example, the spread of up and down Z-axis acceleration measurements is above a threshold (e.g., 2 m / s 2 ) for a percentage of the period over which the Z-axis acceleration is measured. 2 50% of the period, the measured Z-axis acceleration indicates that the mobile device is placed on a bicycle. In another embodiment, one or more measurements indicate motion associated with a moving bicycle when the XY-axis motion measured by the mobile device's accelerometer represents sporadic, irregular, or consistent increases and decreases in acceleration of varying degrees as the bicycle speeds up and down while moving. As an example, the spread of the XY-axis acceleration increases and decreases measurements may be greater than or equal to a threshold (e.g., 5 m / s) over a percentage of the period during which the XY-axis acceleration is measured.2 75% of the time period, the measured increasing or decreasing XY axis acceleration indicates that the mobile device is placed on a bicycle.

[0030] In a third set of embodiments, the determined location context identifies an estimated location situation of the mobile device as being in a vehicle when one or more measurements indicate motion associated with a moving vehicle (e.g., an automobile). In one embodiment, one or more measurements indicate motion associated with a moving vehicle when the motion measured by the IMU of the mobile device includes vibrations as the vehicle moves over a ground surface, such as specific vibrations that may be represented by sporadic, irregular, or consistent up and down Z-axis accelerations of varying accelerations. As an example, the spread of the up and down Z-axis acceleration measurements is greater than or equal to a threshold (e.g., 3 m / s) for a percentage of the period during which the Z-axis acceleration is measured. 2 50% of the period, the measured up and down Z-axis acceleration indicates that the mobile device is in a vehicle. In another embodiment, one or more measurements indicate motion associated with a moving vehicle when the XY motion measured by the mobile device's accelerometer represents sporadic, irregular, or consistent increases and decreases in acceleration of varying degrees as the vehicle speeds up and down while traveling. As an example, the spread of the measured XY-axis acceleration increases and decreases may be greater than or equal to a threshold (e.g., 10 m / s) over a percentage of the period during which the XY-axis acceleration is measured. 2 50% of the time period, the measured increasing or decreasing XY axis acceleration indicates that the mobile device is within a vehicle.

[0031] In a fourth set of embodiments, the determined location context identifies the estimated location status of the mobile device as stationary when one or more measurements indicate no motion. As an example, the difference between two accelerometer measurements taken within a given time period (e.g., 1 second, 10.0 seconds) is greater than or equal to an acceleration threshold (e.g., 1 m / s 2As another example, when the angular deviation between two orientation measurements of a gyroscope measured within a given time period (e.g., 1 second, 10.0 seconds) is less than an orientation threshold (e.g., an angular deviation less than 10 degrees, taking into account possible measurement errors), one or more measurements indicate no motion.

[0032] In a fifth set of embodiments, the determined location context identifies the estimated location status of the mobile device as dropped and resting on a surface when one or more measurements indicate motion associated with a dropped and resting state on the surface. As an example, when an accelerometer of the mobile device measures a large shock with a sudden change in Z-axis acceleration from one measurement to another that exceeds a threshold change (e.g., the first measurement of Z-axis acceleration is 9.8 m / s due to gravity). 2 The next measurement of the Z-axis acceleration is 10m / s 2 Changes in speed exceed the threshold of 100m / s 2 ), or the mobile device's accelerometer detects the Z-axis acceleration associated with a fall (e.g., 9.8 m / s due to gravity). 2 ), when no Z-axis acceleration is measured, one or more measurements indicate motion associated with dropping onto a surface and coming to rest on that surface.

[0033] If the first data includes two or more estimated locations of the mobile device (e.g., via a positioning application on the mobile device, proximity to an access point, or other known positioning techniques), determining the location context based on the first data including two or more estimated locations (e.g., consecutive estimated locations) of the mobile device may use any of the various combinations of decisions described below with respect to embodiments in sets 6 through 10.

[0034] In a sixth set of embodiments, the determined location context identifies the estimated location status of the mobile device as being with a user on foot (e.g., walking or running) when two or more estimated locations indicate a movement associated with the user walking or running. As an example, the two or more estimated locations indicate a walking or running movement by the user when the speed of the mobile phone (e.g., speed as calculated by dividing the distance between two estimated locations by the time elapsed between the time when each of the two estimated locations was determined) is above a first threshold associated with a minimum walking speed (e.g., 1 km / h) and below a second threshold associated with a maximum running speed (e.g., 5 km / h).

[0035] In a seventh set of embodiments, the determined location context identifies the estimated location status of the mobile device as being on a bicycle or with a user on a bicycle when two or more estimated positions indicate bicycle-related movement. As an example, two or more estimated positions indicate bicycle-related movement when the speed of the mobile phone (e.g., as calculated by dividing the distance between two estimated positions by the time elapsed between when each of the two estimated positions was determined) is above a second threshold associated with a maximum riding speed (e.g., 5 km / h) and below a third threshold associated with a maximum bicycle speed or a speed at which a vehicle is unlikely to be traveling (e.g., 10 km / h).

[0036] In an eighth set of embodiments, the determined location context identifies the estimated location status of the mobile device as being in a vehicle when two or more estimated positions indicate vehicle-related movement. As an example, two or more estimated positions indicate vehicle-related movement when the speed of the mobile phone (e.g., as calculated by dividing the distance between two estimated positions by the time elapsed between when each of the two estimated positions was determined) is above a third threshold associated with a maximum bicycle speed or a speed at which a vehicle is unlikely to travel (e.g., 10 km / h) and below a fourth threshold associated with a maximum vehicle speed (e.g., 200 km / h).

[0037] In a ninth set of embodiments, the determined location context identifies the estimated location status of the mobile device as a stationary state when two or more estimated positions indicate motion associated with a stationary state. As an example, two or more estimated positions indicate a stationary state when the speed of the mobile phone (e.g., as calculated by dividing the distance between the two estimated positions by the time elapsed between when each of the two estimated positions is determined) falls below a first threshold associated with a minimum walking speed (e.g., 1 km / h) and, optionally, the vertical speed of the mobile device falls below a vertical speed threshold (e.g., 1 m / s).

[0038] In a tenth set of embodiments, the determined location context identifies the estimated location status of the mobile device as being on a surface after a fall when two or more estimated locations indicate motion associated with falling onto and reaching the surface. As an example, the two or more estimated locations indicate a falling onto and reaching the surface state when the second estimated location is lower than the first estimated location, the vertical velocity of the mobile phone (e.g., velocity as calculated by dividing the Z-axis distance between the two estimated locations by the time elapsed between the time when each of the two estimated locations was determined) exceeds a vertical velocity threshold (e.g., 1 m / s), and, optionally, the horizontal velocity of the mobile phone (e.g., velocity as calculated by dividing the XY-axis distance between the two estimated locations by the time elapsed between the time when each of the two estimated locations was determined) falls below a first threshold associated with a minimum walking speed (e.g., 1 km / h).

[0039] If the first data includes an estimated location of the mobile device (e.g., from a mobile device positioning application, proximity to an access point, or another known positioning technique), the determined location context may identify the mobile device as being in a known location (e.g., the user's residence, the user's workplace, or another identifiable location). Alternatively, the determined location context may identify the mobile device as being (i) with a user on foot if the estimated location is at a shopping location, fitness location, park, or other location where the user may be walking or running with the mobile device, (ii) on a bicycle or with a user on a bicycle if the estimated location is on (or within a distance threshold from) a bicycle path where the user may be biking with the mobile device, (iii) in a vehicle if the estimated location is on (or within a distance threshold from) a highway or freeway, or (iv) stationary if the estimated location is at the user's residence or workplace.

[0040] If the first data includes measurements taken by a pressure sensor in the mobile device, the determined location context may identify the mobile device as being in a vehicle when the measurements change drastically (e.g., the pressure measurements vary widely from one side to the other), which occurs when ambient air passes over the moving vehicle and changes the pressure inside the vehicle. As an example, the drastically changing measurements can be quantified as (1) the variance or standard deviation of the last N pressure measurements (e.g., N=10) over the last T seconds (e.g., T=5 seconds), and if the standard deviation exceeds a threshold (e.g., 10 Pa), then the location context is likely to be an "in-vehicle condition"; or (2) the range or difference between the maximum and minimum measurements of the last N pressure measurements (e.g., N=10) collected over the last T seconds (e.g., T=5 seconds), and if the range exceeds a threshold (e.g., 20 Pa), then the location context is likely to be an "in-vehicle condition."

[0041] [Second data] Step 230 of Figure 2A and step 265 of Figure 2B identify second data to acquire based on different considerations (e.g., the determined location context, or two or more possible estimated heights above a surface at which the mobile device may be located). Such second data may include one or more of (i) at least one measurement result determined by at least one sensor of the mobile device, (ii) at least one condition indicator of equipment of the mobile device, and both (i) and (ii).

[0042] Examples of measurements determined by sensors on a mobile device include at least one of the following: (i) An orientation measurement obtained from a gyroscope sensor on the mobile device (e.g., obtained by querying a gyroscope sensor API on the mobile device, as is known), which may identify three angles in three dimensional space in which three planes (i.e., XY, XZ, YZ) lie when the orientation measurement is made, and which can be used to determine whether the mobile device is upright, upright, level, or off-level, as described further below. (ii) Light measurements from a light sensor on a mobile device (e.g., by querying a light sensor API on a mobile device, as is known), which may be measured in lux and may identify the intensity of light received by the light sensor (e.g., a camera on a mobile device), which may be used to determine whether a surface of the mobile device is obscured (e.g., by being covered, by being in a pocket or bag, or by being placed face down on a counter or table). (iii) Sound measurements from a mobile device microphone (e.g., measurements obtained by querying an API on the mobile device, as is known), which can be used to determine whether the mobile device is likely to be in close proximity to a user's mouth (e.g., less than 0.5 meters).

[0043] Examples of mobile device equipment status indicators include at least one of the following: (i) A motion state indicator from the mobile device's pedometer (e.g., obtained by querying a mobile device's pedometer API, as is known) that identifies whether walking or running motion has been recorded by recording the number of steps per unit time associated with walking or running, or by recording pedaling motion associated with cycling, which motion state indicator can be used to determine whether the mobile phone is with a user who is walking, running, or riding a bicycle. (ii) A battery temperature measurement from a temperature sensor on the mobile device (e.g., obtained by querying an API on the mobile device, as is known) that measures the internal temperature near the mobile device's battery, which can be used to determine whether the mobile device is outside of a bag or inside of a bag with little or no ambient airflow to cool the mobile device. (iii) a call status indicator (obtained, for example, by querying an API on the mobile device, as is known in the art), which can be used to determine whether the user is actually on a phone call. (iv) a hands-free call status indicator (e.g., obtained by querying an API of the mobile device, as is known), which can be used to determine whether the user is actually on a phone call and that the mobile device is unlikely to be in an upright orientation held up to the user's ear (because the hands-free feature enables hands-free in combination with a wired or wireless microphone and speaker adapter), but instead is being held in front of the user (e.g., for video chat), held on the user's waist, or in the user's pocket or bag. (v) a speaker call status indicator (e.g., obtained by querying an API of the mobile device, as is known in the art) that can be used to determine whether the user is actually on a phone call and that the mobile device is unlikely to be in an upright position against the user's ear, unlikely to be held at the user's waist, or unlikely to be in the user's pocket or bag (because the speaker function is activated), but instead likely to be held in the user's upper body region below the user's mouth. (vi) a video call status indicator (e.g., obtained by querying an API of the mobile device or by determining that the camera and phone are active simultaneously, as is known in the art) that can be used to determine whether the user is actually on a phone call and that the mobile device is unlikely to be in an upright position against the user's ear, unlikely to be held at the user's waist, or unlikely to be in the user's pocket or bag (because the video camera function is active), but instead likely to be held in the user's upper body region within view of the user's head. (vii) a video recording status indicator (e.g., obtained by querying an API of the mobile device, as is known), which can be used to determine whether a user is recording video with the mobile device and the mobile device is not in the user's bag or pocket, or the mobile device is not being used to make a phone call. (viii) a descent recorder usage indicator that identifies whether a descent recorder measurement is being displayed (e.g., obtained by querying an API of the mobile device, as known in the art), which can be used to determine that the mobile device is likely within the user's field of view. (ix) a battery charge state indicator (e.g., obtained by querying an API on the mobile device, as is known), which can be used to determine whether the mobile device is connected to a power source, and depending on the voltage measurement, may determine whether the power source is a wall outlet, a computer, a car inverter, a portable battery pack, or other type of power source, which can help determine whether the mobile device is likely to be on furniture such as a desk, or on the ground or floor (e.g., if the power source is a wall outlet or computer), on the console of a car (e.g., if the power source is a car inverter), or in a user's pocket or bag (e.g., if the power source is a portable charger). The various types of data discussed above may be obtained in step 240 or step 275 and used to determine an estimated height above a surface at which the mobile device is located in step 250 of FIG. 2A or step 285 of FIG. 2B, respectively.

[0044] [Estimating the height of the mobile device from a surface] Various methods for estimating the height at which a mobile device is located from a surface are described in Figures 3A to 3H as follows.

[0045] A first method for estimating the height at which a mobile device is located above a surface when the determined location context is with a user on foot is shown in FIG. 3A. This first method may be used when the second data includes various combinations of measurements or indicators used by various approaches described below. As an example, the various combinations of measurements or indicators may include any of a first status indicator identifying whether wired or wireless hands-free calling is being used, a second status indicator identifying whether speakerphone or video calling is being used, a light measurement from a light sensor of the mobile device, an orientation measurement from a gyroscope of the mobile device, a motion status indicator from a pedometer of the mobile device identifying whether walking or running motion has been recorded, a sound measurement from a microphone of the mobile device, and a camera status indicator indicating that the mobile phone's camera (e.g., front-facing camera) is active. A determination is made whether the mobile device is being used to conduct a call, which may be determined by obtaining a call state indicator that identifies the mobile device as being used to conduct a call (or being unable to obtain such a call state indicator), or by obtaining a call state indicator that identifies the mobile device as not being used to conduct a call. The estimated height at which the mobile device is located above the surface is determined using one or more of the following approaches for determining the estimated height. (I) In the first approach, when the mobile device is being used to make a phone call and a first state indicator is obtained to identify that hands-free calling is being used during the phone call, the estimated height is determined to be a first predetermined height. As an example, the first predetermined height is set to an expected height of a user's waist, such as 1.0 meter, or a predetermined percentage of the user's height, such as 50%, if obtainable from the user's profile data, which is an expected position when the mobile device is held by the user or in the user's pocket with hands-free calling being used during the phone call. (II) In a second approach, when the mobile device is being used to make a phone call, the estimated height is determined to be the second predetermined height if any of the following conditions apply: (i) a second status indicator is obtained to identify that speakerphone or video calling is being used during the phone call, or (ii) a light measurement from a light sensor of the mobile device is obtained to be above a first light level (and, optionally, below a second light level) and an orientation measurement from a gyroscope of the mobile device is obtained to indicate that the mobile device is not in an upright orientation, and, optionally, the first status indicator is not obtained or the obtained first status indicator identifies that hands-free calling is not being used during the phone call, or (iii) a sound measurement from a microphone is above a volume threshold associated with a user's voice emanating within less than 0.5 meters of the microphone. Various embodiments of this approach may consider various combinations (e.g., only one, some, or all) of the above-listed conditions. As an example, the second predetermined height is set to an expected height of the user's upper body, such as 1.5 meters, or, if obtainable from the user's profile data, a predetermined percentage such as 75% of the user's height, which is the expected position of the mobile device being held by the user when speakerphone or video calling is used during a call, or when the light sensor is exposed to light (e.g., not covered) and the mobile device is close enough for the microphone of the mobile device to receive the user's voice and be heard by the user through the speaker, but is unlikely to be held against the user's ear (e.g., not in an upright orientation). Examples of light levels include a first light level of 10,000 lux and a second light level of 20,000 lux. Examples of sound volume thresholds include 50 dB. The upright orientation can be defined in various ways.In one embodiment where the mobile device is in standard Cartesian coordinates (XYZ), the mobile device is in an upright orientation when the angle between the mobile device's screen and the Z axis (or ZX axis plane or ZY axis plane) is within a maximum threshold (e.g., 20 degrees), and the mobile device is not in an upright orientation when the angle between the mobile device's screen and the Z axis (or ZX axis plane or ZY axis plane) is not within a maximum threshold (e.g., 20 degrees). (III) In a third approach, the mobile device is used to make a phone call and determines that the estimated height is the third predetermined height if any of the following conditions apply: (i) the first status indicator is not obtained or the obtained first status indicator identifies that hands-free calling is not used during the call and the second status indicator is not obtained or the obtained second status indicator identifies that speakerphone or video calling is not used during the call, or (ii) a light measurement from a light sensor of the mobile device is obtained that is not above a first light level and an orientation measurement from a gyroscope of the mobile device is obtained that indicates that the mobile device is in an upright orientation. Various embodiments of this approach may consider various combinations (e.g., only one, some, or all) of the above-listed conditions. As an example, the third predetermined height is set to the assumed height of the user's ears, such as 2.0 meters, or, if obtainable from the user's profile data, a predetermined percentage, such as 95% or more, of the user's height, which is the assumed position when the mobile device is held by the user when hands-free or speakerphone is not used during a call or when no light or only negligible light is detected when the mobile device is held upright against the user's ear. (IV) In a fourth approach, when the mobile device is not being used to make a call, when a motion state indicator is obtained to identify that a walking or running motion has been recorded, and when a light measurement from a light sensor of the mobile device is below a first light level, the estimated height is determined to be a fourth predetermined height. As an example, the fourth predetermined height is set to an assumed height of a user's waist, such as 1.0 meter, or a predetermined percentage of the user's height, such as 50%, if obtainable from the user's profile data, which is an assumed position when the mobile device is placed in a user's pocket when no call is being made and the light sensor (e.g., camera) is covered. (V) In a fifth approach, when the mobile device is not being used to make a phone call, when a motion state indicator is obtained to identify that a walking or running motion has been recorded, and when a light measurement from a light sensor of the mobile device is above the first light level (or another light level), the estimated height is determined to be a fifth predetermined height. As an example, the fifth predetermined height is set to an expected height of a user's upper body, such as 1.5 meters, or, if obtainable from the user's profile data, a predetermined percentage such as 75% of the user's height, which is an expected position when the mobile device is carried on the user's arm when the user is walking or running under the aforementioned detected conditions. (VI) In a sixth approach, when the mobile device is not being used to make a phone call and either the motion state indicator is not obtained or the obtained motion state indicator identifies that walking or running motion was not recorded, the estimated height is determined to be a sixth predetermined height. As an example, the sixth predetermined height is set to an assumed height of a wheeled bag being pushed or pulled by a user, such as 0.5 meters, or, if obtainable from the user's profile data, a predetermined percentage such as 25% of the user's height, which is a location where the mobile device is assumed to be when the user is assumed to be walking and no steps of the user are detected. (VII) In a seventh approach, if the mobile device is not being used to make a call and the camera status indicator indicates that the camera (e.g., the front camera) is active (e.g., capturing an image), the estimated height is determined to be a seventh predetermined height. As an example, the seventh predetermined height is set to an expected height of the user's face, such as 2.0 meters, or a predetermined percentage, such as 95% or more, of the user's height if obtainable from the user's profile data, which is the expected position in which the mobile device is held when the user is taking a picture of themselves. Various embodiments of the first method may use any number (eg, any one or all) of the approaches described above.

[0046] A second method for estimating the height at which a mobile device is located above a surface when the determined location context is with a user on foot is shown in FIG. 3B. This second method may be used where the second data includes various combinations of measurements or indicators used by various approaches described below. As an example, the various combinations of measurements or indicators may include any of a first status indicator identifying whether wired or wireless hands-free calling is being used, a second status indicator identifying whether speakerphone or video calling is being used, a light measurement from a light sensor of the mobile device, and an orientation measurement from a gyroscope of the mobile device. A determination is made that the mobile device is being used to conduct a telephone call, which may be determined by obtaining a call state indicator that identifies the mobile device as being used to conduct a telephone call. The estimated height at which the mobile device is located above the surface is determined using one or more of the following approaches for determining the estimated height. (I) In a first approach, when the mobile device is being used to make a phone call and a first state indicator is obtained to identify that hands-free calling is being used during the phone call, the estimated height is determined to be a first predetermined height. As an example, the first predetermined height is set to an expected height of a user's waist, such as 1.0 meter, or a predetermined percentage of the user's height, such as 50%, if obtainable from the user's profile data, which is an expected position when the mobile device is held by the user or in the user's pocket with hands-free calling being used during the phone call. (II) In a second approach, when the mobile device is being used to make a phone call, the estimated height is determined to be the second predetermined height if any of the following conditions apply: (i) a second status indicator is obtained to identify that speakerphone or video calling is being used during the phone call, or (ii) a light measurement from a light sensor of the mobile device is obtained to be above a first light level (and, optionally, below a second light level) and an orientation measurement from a gyroscope of the mobile device is obtained to indicate that the mobile device is not in an upright orientation, and, optionally, the first status indicator is not obtained or the obtained first status indicator identifies that hands-free calling is not being used during the phone call, or (iii) a sound measurement from a microphone is above a volume threshold associated with a user's voice emanating within less than 0.5 meters of the microphone. Various embodiments of this approach may consider various combinations (e.g., only one, some, or all) of the above-listed conditions. As an example, the second predetermined height is set to an expected height of the user's upper body, such as 1.5 meters, or, if obtainable from the user's profile data, a predetermined percentage such as 75% of the user's height, which is the expected position the mobile device is held by the user when speakerphone or video calling is used during a call, or when the light sensor is exposed to light (e.g., not covered) and the mobile device is close enough for the microphone of the mobile device to receive the user's voice and be heard by the user from the speaker, but is unlikely to be held against the user's ear (e.g., not in an upright orientation). Examples of light levels include a first light level of 10,000 lux and a second light level of 20,000 lux. Examples of sound volume thresholds include 50 dB. The upright orientation can be defined in various ways.In one embodiment where the mobile device is in standard Cartesian coordinates (XYZ), the mobile device is in an upright orientation when the angle between the mobile device's screen and the Z axis (or ZX axis plane or ZY axis plane) is within a maximum threshold (e.g., 20 degrees), and the mobile device is not in an upright orientation when the angle between the mobile device's screen and the Z axis (or ZX axis plane or ZY axis plane) is not within a maximum threshold (e.g., 20 degrees). (III) In a third approach, the mobile device is used to make a phone call and determines that the estimated height is the third predetermined height if any of the following conditions apply: (i) the first status indicator is not obtained or the obtained first status indicator identifies that hands-free calling is not used during the call, and the second status indicator is not obtained or the obtained second status indicator identifies that speakerphone or video calling is not used during the call, or (ii) a light measurement from a light sensor of the mobile device is obtained and does not exceed a first light level, and an orientation measurement from a gyroscope of the mobile device is obtained and indicates that the mobile device is in an upright orientation. Various embodiments of this approach may consider various combinations (e.g., only one, some, or all) of the above-listed conditions. As an example, the third predetermined height is set to the assumed height of the user's ears, such as 2.0 meters, or, if obtainable from the user's profile data, a predetermined percentage, such as 95% or more, of the user's height, which is the assumed position when the mobile device is held by the user when hands-free or speakerphone is not used during a call or when no light or only negligible light is detected when the mobile device is held upright against the user's ear. Various embodiments of the second method may use any number (eg, any one or all) of the approaches described above.

[0047] A third method for estimating the height at which a mobile device is located above a surface when the determined location context is with a user on foot is shown in FIG. 3C. This third method may be used when the second data includes various combinations of measurements or metrics used by various approaches described below. As an example, the various combinations of measurements or metrics may include either a motion status indicator from a pedometer in the mobile device that identifies whether walking or running motion was recorded, and a light measurement from a light sensor in the mobile device. A determination that the mobile device is not being used to conduct a call is made, which may be determined by obtaining a call state indicator that identifies the mobile device is not being used to conduct a call or by being unable to obtain a call state indicator that identifies the mobile device is being used to conduct a call. The estimated height at which the mobile device is located above the surface is determined using one or more of the following approaches for determining the estimated height. (I) In a first approach, when the mobile device is not being used to make a call, when a motion state indicator is obtained to identify that a walking or running motion has been recorded, and when a light measurement from a light sensor of the mobile device is below a first light level, the estimated height is determined to be a first predetermined height. As an example, the first predetermined height is set to an assumed height of a user's waist, such as 1.0 meter, or a predetermined percentage of the user's height, such as 50%, if obtainable from the user's profile data, which is an assumed position when the mobile device is placed in a user's pocket when no call is being made and the light sensor (e.g., camera) is covered. (II) In a second approach, when the mobile device is not being used to make a call, and the motion state indicator is obtained to identify that walking or running motion has been recorded, and when the light measurement from the light sensor of the mobile device is above the first light level (or another light level), the estimated height is determined to be the second predetermined height. As an example, the second predetermined height is set to an expected height of the user's upper body, such as 1.5 meters, or a predetermined percentage of the user's height, such as 75%, if obtainable from the user's profile data, which is the expected position of the mobile device being carried on the user's arm when the user is walking or running under the aforementioned detected conditions. (III) In a third approach, when the mobile device is not being used to make a phone call and no motion state indicator is obtained or the obtained motion state indicator identifies that no walking or running motion was recorded, the estimated height is determined to be a third predetermined height. As an example, the third predetermined height is set to an assumed height of a wheeled bag being pushed or pulled by a user, such as 0.5 meters, or a predetermined percentage of the user's height, such as 25%, if obtainable from the user's profile data, which is a location where the mobile device is assumed to be when the user is assumed to be walking and no steps of the user are detected. (IV) In a fourth approach, when the mobile device is not being used to make a call and the camera status indicator indicates that the camera (e.g., the front camera) is active (e.g., capturing an image), the estimated height is determined to be a fourth predetermined height. As an example, the fourth predetermined height is set to an expected height of the user's face, such as 2.0 meters, or a predetermined percentage, such as 95% or more, of the user's height if obtainable from the user's profile data, which is the expected position at which the mobile device is held when the user is taking a picture of themselves. Various embodiments of the third method may use any number (eg, any one or all) of the approaches described above.

[0048] A fourth method for estimating the height at which a mobile device is located relative to a surface when the determined location context is while mounted on a bicycle or with a user on a bicycle is shown in FIG. 3D. This fourth method may be used when the second data includes various combinations of measurements or indicators used by various approaches described below. As an example, the various combinations of measurements or indicators may include any of a light measurement from a light sensor of the mobile device, an orientation measurement from a gyroscope of the mobile device, a video recording status indicator that identifies whether a video is being recorded by a camera of the mobile device, and a descent status indicator that identifies whether movement information is being displayed on a screen of the mobile device. As an example, the movement information may include speed, distance traveled, or other data. The estimated height at which the mobile device is located above the surface is determined using one or more of the following approaches for determining the estimated height. (I) In a first approach, when a light measurement from a light sensor of the mobile device is obtained that is below a first light level, the estimated height is determined to be a first predetermined height. As an example, the first predetermined height is set to an expected height of the bicycle equipment, such as 1.0 meter, or, if obtainable from the user's profile data, the actual height of the bicycle equipment, such as a seat or bag, attached to the bicycle or carried by the user, which is the expected position when the mobile device is stored in the user's pocket or bag while the user is riding the bicycle and no light is detected above a certain level. (II) In the second approach, the estimated height is determined to be the second predetermined height if any of the following conditions are met: (i) a light measurement from a light sensor of the mobile device is obtained that is above a first light level (or another light level) and an orientation measurement from a gyroscope of the mobile device is obtained that indicates that the mobile device is not in an upright orientation; or (ii) a odometer usage indicator is obtained that identifies that the mobile device is displaying movement information on the screen of the mobile device. Various embodiments of this approach may consider various combinations (e.g., only one, some, or all) of the above listed conditions. As an example, the second predetermined height is set to an assumed height of the bicycle equipment, such as a handlebar, 1.0 meter, or, if obtainable from the user's profile data, the actual height of the bicycle equipment, which is the assumed position that the mobile device is carried when the user is riding the bicycle and light above a certain level is detected and not in an upright orientation such that the user can view the mobile device screen while riding the bicycle. The upright orientation can be defined in various ways. In one embodiment where the mobile device is in standard Cartesian coordinates (XYZ), the mobile device is in an upright orientation when the angle between the mobile device's screen and the Z axis (or ZX axis plane or ZY axis plane) is within a maximum threshold (e.g., 20 degrees), and the mobile device is not in an upright orientation when the angle between the mobile device's screen and the Z axis (or ZX axis plane or ZY axis plane) is not within a maximum threshold (e.g., 20 degrees). (III) In a third approach, the estimated height is determined to be the third predetermined height if any of the following conditions are met: (i) a light measurement from a light sensor of the mobile device is obtained and exceeds the first light level (or another light level) and an orientation measurement from a gyroscope of the mobile device is obtained and indicates that the mobile device is in an upright orientation; or (ii) a video recording state indicator identifies that a video is being recorded and an orientation measurement from a gyroscope of the mobile device is obtained and indicates that the mobile device is in an upright orientation. Various embodiments of this approach may consider various combinations (e.g., only one, some, or all) of the above listed conditions. As an example, the third predetermined height is set to an assumed height of a bicycle handlebar or a user's head when riding a bicycle, such as 1.0 meter or 2.0 meter, which is an assumed position in which the mobile device is carried when the mobile device is recording a video. Since two positions at different heights are assumed as possible positions for the mobile device, additional processing can be performed to select between these different positions (for example, by looking at the image recorded by the camera of the mobile device, it is possible to determine whether a particular element, such as the user's hands or handlebars, is visible in a particular part of the image, such as the bottom edge of the image, and since the particular element is recognized as being in a particular part of the image, it is concluded that the assumed height is 2.0 meters of the user's head). Various embodiments of the fourth method may use any number (eg, any one or all) of the approaches described above.

[0049] A fifth method for estimating the height at which a mobile device is located from a surface when the determined position context is in a vehicle is shown in FIG. 3E. This fifth method may be used when the second data includes various combinations of measurements or indicators used by various approaches described below. As an example, the various combinations of measurements or indicators may include any of a light measurement from a light sensor of the mobile device, an orientation measurement from a gyroscope of the mobile device, a battery charge status indicator that identifies whether the battery of the mobile device is being charged, a call status indicator that identifies whether the mobile device is being used to conduct a call, a first status indicator that identifies whether wired or wireless hands-free calling is being used when the call is being conducted, and a second status indicator that identifies whether speakerphone calling is being used when the call is being conducted. The estimated height at which the mobile device is located above the surface is determined using one or more of the following approaches for determining the estimated height. (I) In the first approach, the estimated height is determined to be the first predetermined height if any of the following conditions are met: (i) a light measurement from a light sensor of the mobile device is obtained and is below a first light level, or (ii) a light measurement from a light sensor of the mobile device is obtained and is above a first light level (or another light level) and a battery charge status indicator is obtained and identifies that the battery of the mobile device is being charged, or (iii) a battery charge status indicator is obtained and identifies that the battery of the mobile device is being charged and a call status indicator is obtained and identifies that the mobile device is not being used to make a call, or (iv) a first status indicator is obtained and identifies that hands-free calling is being used while making a call. Various embodiments of this approach may consider various combinations (e.g., only one, some, or all) of the above listed conditions. As an example, the first predetermined height is set to an assumed height of the vehicle seat, such as 0.75 meters, or, if obtainable from the user profile data, the actual height of the vehicle seat, which is the assumed position when the mobile device is placed in the user's pocket, in a bag or purse on the seat, or placed face down on the seat, center console pedestal, or on the user's lap (when no light above a certain level is detected), or placed face up on the seat, center console, or lap (when light above a certain level is detected and the battery is charging, or when the battery is charging and no call is being made), or any of the aforementioned positions when a call is being made and hands-free calling is being used. (II) In the second approach, the estimated height is determined to be the second predetermined height if any of the following conditions apply: (i) a second state indicator is obtained to identify that speakerphone is being used during a call, or (ii) a call state indicator is obtained to identify that the mobile device is being used to perform a call, a light measurement from a light sensor of the mobile device is obtained to exceed a first light level, and an orientation measurement from a gyroscope of the mobile device is obtained to indicate that the mobile device is not in an upright orientation. Various embodiments of this approach may consider various combinations (e.g., only one, some, or all) of the above-listed conditions. As an example, the second predetermined height is set to a pre-determined distance from the height of the vehicle seat, such as 1.25 meters, which is an assumed height of the user's upper body when the user is seated in the vehicle seat, or, if obtainable from the user's profile data, such as 0.5 meters, which is an assumed position of the mobile device held by the user when speakerphone is being used during a call. (III) In a third approach, the estimated height is determined to be the third predetermined height when a call status indicator is obtained to identify that the mobile device is being used to make a call and any of the following conditions apply: (i) the first status indicator is not obtained or the call is identified as not using hands-free calling (and, optionally, the second status indicator is not obtained or the call is identified as not using speaker calling), or (ii) a light measurement from a light sensor of the mobile device is obtained and does not exceed a first light level (or another light level), or (iii) an orientation measurement from a gyroscope of the mobile device is obtained and indicates that the mobile device is in an upright orientation. Various embodiments of this approach may consider various combinations (e.g., only one, some, or all) of the above-listed conditions. As an example, the third predetermined height is set to a predetermined distance, such as 1.75 meters, the assumed height of the user's ears when the user is sitting in the vehicle seat, or, if obtainable from the user's profile data, 1.0 meter above the vehicle seat, which is the assumed position when the mobile device is held by the user when a call is in progress and hands-free or speakerphone is not in use. Various embodiments of the fifth method may use any number (eg, any one or all) of the approaches described above.

[0050] A sixth method for estimating the height at which a mobile device is located above a surface when the determined position context is in a state where the mobile device is above the surface after a fall is shown in FIG. 3F. This sixth method may be used when the second data includes various combinations of measurements or metrics used by various approaches described below. As an example, the various combinations of measurements or metrics may include any of one or more measurements from an accelerometer of the mobile device and one or more measurements from a pressure sensor of the mobile device. The estimated height at which the mobile device is located above the surface is determined using one or more of the following approaches for determining the estimated height. (I) In the first approach, the first measurement of the accelerometer is taken during a fall (e.g., g=9.8m / s 2 The acceleration in the z-axis direction up to 0 m / s is then measured, and the accelerometer measurement is then used to determine the stationary state (e.g., 0 m / s 2 ) (the acceleration of the mobile device relative to the surface) to determine that the estimated height is a first predetermined height (e.g., 0 meters, which is the position that the mobile device is expected to be above the surface after being dropped). (II) In the second approach, accelerometer measurements are used to measure the impact of a mobile device on a hard surface (e.g., up to 10 × g = 10 × 9.8 m / s 2 z-axis acceleration) and (if necessary) the subsequent accelerometer measurements are taken at rest (e.g., 0 m / s 2 The estimated height is determined to be the first predetermined height by determining that the estimated height is a specific height (the acceleration of the vehicle). (III) In a third approach, the estimated height is determined to be the first predetermined altitude by determining that (i) both the first measurement of pressure and the subsequent second measurement of pressure are measured by a pressure sensor in the mobile device within a period of time that does not exceed a threshold time (e.g., 1 second), and (ii) the second measurement of pressure is higher than the first measurement of pressure, such that the relatively higher second measurement of pressure reflects a relatively lower altitude of the mobile device after it has fallen from the first altitude at which the first measurement of pressure was measured. (IV) A first pressure corresponding to a first altitude before the fall is identified, and a second measurement of the pressure sensor identifies a second (higher) pressure corresponding to a second (lower) altitude after the fall when the mobile device is stationary (i.e., an additional pressure measurement is associated with no motion of the mobile device but within a pressure threshold that accounts for possible measurement error for the same pressure). These values ​​may be retrieved from the cache and compared. Various embodiments of the sixth method may use any number (eg, any one or all) of the approaches described above. In some embodiments, if the height of the mobile device before it was dropped is known, then information in the post-drop position context of the mobile device can be used to determine a new height relative to the height of the mobile device before it was dropped. Using JPEG0007635127000002.jpg21153, the pressure difference can be converted to the drop when the mobile device is dropped, which can then be subtracted from the height the mobile device was dropped to determine the height the mobile device was dropped to. As another example, the magnitude of z-axis acceleration over time, or the acceleration shock value (e.g., 10×g or 98 m / s 2 ) can be mapped against the drop that the mobile device was dropped from (e.g. 10×g translates to roughly a 1 meter drop, which can be determined by laboratory testing and can be specific to an individual mobile device or cover or cushioning for the mobile device) and that drop can be subtracted from the height of the mobile device before the drop to determine the height of the mobile device after the drop.

[0051] A seventh method for estimating the height at which a mobile device is located above a surface when the determined position context is stationary is shown in Figures 3G and 3H. This seventh method may be used where the second data includes various combinations of measurements or indicators used by various approaches described below. As an example, the various combinations of measurements or indicators may include any of a battery charge status indicator identifying whether the mobile device's battery is charging, an orientation measurement from a mobile device's gyroscope, a light measurement from a mobile device's light sensor, a battery temperature measurement from a mobile device's temperature sensor, a call status indicator identifying whether a video call is in progress, a camera status indicator identifying whether a camera is capturing an image, and data identifying an area in which the mobile device is located. As an example, the data identifying an area in which the mobile device is located may be determined by detecting an overlap between a known location of the area and an estimated location of the mobile device, by determining that the mobile device is in communication with an access point (e.g., a WiFi beacon) accessible only within the area, by receiving user input identifying the area, or by any other known approach for determining such an area. The estimated height at which the mobile device is located above the surface is determined using one or more of the following approaches for determining the estimated height. (I) In a first approach, the estimated height is determined to be the first predetermined height if any of the following conditions apply: (i) a battery state of charge indication is obtained and identifies the mobile device's battery as being charged, an orientation measurement from the mobile device's gyroscope is obtained and indicates that the mobile device is in a horizontal orientation, and data identifying an area in which the mobile device is located is obtained and identifies the mobile device as being in a first type of location likely to be resting on a table, desk, or counter, or (ii) a battery state of charge indication is obtained and identifies the mobile device's battery as not being charged, a light measurement from a mobile device's light sensor is obtained and does not exceed a first light level, and an orientation measurement from the mobile device's gyroscope is obtained and indicates that the mobile device is in a horizontal orientation, or (iii) a battery state of charge indication is obtained and identifies the mobile device's battery as not being charged, a light measurement from a mobile device's light sensor is obtained and does not exceed a first light level, and an orientation measurement from the mobile device's gyroscope is obtained and indicates that the mobile device is in a horizontal orientation. An indication is obtained to identify that the mobile device's battery is not charging, a light measurement from a light sensor of the mobile device is obtained and is above a first light level (or another light level), and an orientation measurement from a gyroscope of the mobile device is obtained and indicates that the mobile device is in a horizontal orientation, or (iv) a battery temperature measurement is obtained and indicates that the mobile device's battery temperature is below a first temperature level, an orientation measurement from a gyroscope of the mobile device is obtained and indicates that the mobile device is in a horizontal orientation, and (optionally) a battery charge status indication is obtained and identifies that the mobile device's battery is not charging, or (v) an application for presenting media (e.g., music or video) is running. Various embodiments of this approach may consider various combinations (e.g., only one, some, or all) of the above enumerated conditions.As an example, the first predefined height is set to 1.0 meter, or, if obtainable from the user's profile data, the actual height of the table, desk, or counter in a first type of location, such as the user's residence or workplace, that is the assumed height of a table, desk, or counter when the mobile device is in a horizontal orientation and charging, does not detect light above the threshold and is not charging, detects light above the threshold but is not charging, is not contained in a bag or pocket or the like and has adequate airflow, or when the media presentation application is actually outputting media, since the internal battery temperature of a mobile device is typically 0-15°C higher than the ambient temperature, which is typically 25-40°C. In one embodiment, the first temperature level is less than 40°C. The horizontal orientation can be defined in a variety of ways. In one implementation where the mobile device is in standard Cartesian coordinates (XYZ), the mobile device is in a horizontal orientation when the angle between the mobile device's screen and the XY axis plane (or one or both of the X and Y axes) is within a maximum threshold (e.g., 15 degrees), and otherwise the mobile device is not in a horizontal orientation when the angle between the mobile device's screen and the XY axis plane (or one or both of the X and Y axes) is not within a maximum threshold (e.g., 15 degrees). (II) In a second approach, when a battery charge status indicator is obtained to identify that the mobile device battery is charging, an orientation measurement from the mobile device gyroscope is obtained to indicate that the mobile device is in a horizontal orientation, and data is obtained to identify an area in which the mobile device is located to identify that the mobile device is in a second type of location where the mobile phone is likely to be located in a chair, a user's lap, or a pocket of a bag placed on a surface. As an example, the second predetermined height is set to 0.5 meters, or an expected height of a portion of a bag (e.g., a glove compartment) resting on a surface, seat, or a user's lap, such as the actual height of a bag pocket or seat if obtainable from the user's profile data or another data source, which is the expected location of the mobile device when the mobile device is charging and stored in a public space such as an airport, mall, hospital, convention center, coffee shop, or other location. As an example, the second type of location may be a residence or a workplace. (III) In a third approach, the estimated height is determined to be the third predetermined height when a light measurement from a light sensor of the mobile device is obtained and does not exceed a first light level, an orientation measurement from a gyroscope of the mobile device is obtained and indicates that the mobile device is not in a horizontal orientation, and (optionally) a battery charge status indicator is obtained and identifies that the battery of the mobile device is not being charged. As an example, the third predetermined height is set to an assumed height when the mobile device is held by a user who is sitting or standing for various purposes, such as 1.0 to 2.0 meters, which is assumed to be the state at which the mobile device is located when held by a user in a non-horizontal orientation for various purposes, such as viewing digital information or games on a screen of the mobile device when sitting, or capturing images with a camera of the mobile device when standing. Further conditions may be considered, such as determining whether digital information is being displayed on the screen, whether an image is being captured by the camera, or whether a game is being actively displayed on the screen, and a particular height may be selected from a number of heights associated with those conditions, such as 1.0 meter if digital information or a game is being displayed, 2.0 meters if an image is being captured, or the user's height, if available. (IV) In a fourth approach, the estimated height is determined to be a fourth predetermined height (e.g., 1.0 meter) or is not determinable if any of the following conditions apply: (i) a battery charge state indication is obtained and identifies a mobile device battery as being charged, and an orientation measurement from a mobile device gyroscope is obtained and indicates that the mobile device is not in a horizontal orientation, or (ii) a battery charge state indication is obtained and identifies a mobile device battery as not being charged, a light measurement from a mobile device light sensor is obtained and does not exceed a first light level, and an orientation measurement from a mobile device gyroscope is obtained and indicates that the mobile device is not in a horizontal orientation. Various embodiments of this approach may consider various combinations (e.g., only one, some, or all) of the above-listed conditions. As an example, the fourth predetermined height may be an average height (e.g., the average of 0.5 meters and 1.0 meters), or another type of height, of possible states in which the mobile device may be located when the mobile device is not in a horizontal orientation while charging its battery, such as when the mobile device may be in a bag on a surface, seat, or table, or when the mobile device is not charging its battery, is not in a horizontal orientation, and no light is detected. (V) In a fifth approach, the estimated height is determined to be a fifth predetermined height (e.g., 1.0 meter) or is not determinable if any of the following conditions apply: (i) a battery temperature measurement is obtained indicating that the mobile device's battery temperature is below a first temperature level, an orientation measurement from the mobile device's gyroscope is obtained indicating that the mobile device is not in a horizontal orientation, and (optionally) a battery charge state indicator is obtained to identify that the mobile device's battery is not charging, or (ii) a battery temperature measurement is obtained indicating that the mobile device's battery temperature is not below a first temperature level, and (optionally) a battery charge state indicator is obtained to identify that the mobile device's battery is not charging. Various embodiments of this approach may consider various combinations (e.g., only one, some, or all) of the above listed conditions. As an example, the fifth predetermined height may be an average height (e.g., an average of 0.5 meters and 1.0 meters), or another type of height, at which the mobile device is expected to be located when it is overheated or not in a horizontal orientation, such as when it is not charging in a bag on a surface, seat, or table. (VI) In a sixth approach, when a call status indicator is obtained to identify that a video call is taking place, the estimated height is determined to be a sixth predetermined height (e.g., 1.5 meters). As an example, the sixth predetermined height is set to an expected height of a user's upper body, such as 1.5 meters, or, if obtainable from the user's profile data, a predetermined percentage, such as 75% of the user's height, which is the expected position of the mobile device being held by the user when a video call is taking place. (VII) In a seventh approach, when a camera state indicator is obtained to identify that the camera is capturing an image, the estimated height is determined to be a seventh predetermined height (e.g., 2.0 meters). As an example, the seventh predetermined height is set to the expected height of a standing user's face, such as 2.0 meters, or a predetermined percentage, such as 95% or more, of the user's height if obtainable from the user's profile data, which is the expected position that the mobile device is held when the user is photographing themselves. Various embodiments of the seventh method may use any number (eg, any one or all) of the approaches described above.

[0052] Alternatively, the determined location context may be at a known location (e.g., a user's residence or workplace) and the second data may include various types of data that may be used to determine a predetermined height at which the mobile device is assumed to be located at the known location. The use and determination of the various data regarding the predetermined height may be similar to the use and determination of the location context for a stationary and walking user or may be different to the use and determination of the predetermined height. Examples of particular types of data that may be obtained include: (i) data indicating whether the mobile device's battery is charging; (ii) data indicating the mobile device is oriented in a particular orientation, such as horizontal, not horizontal, upright, or not upright; (iii) data indicating a light sensor on the mobile device measures light above or below a first light level; (iv) data indicating an inertial sensor on the mobile device measures a particular type of motion (e.g., no motion of the mobile device, moving with a user who is walking or running); (v) data indicating whether a call is being made on the mobile device; (vi) data indicating whether hands-free or speakerphone is being used during a call; (vii) data indicating an image is being captured by the mobile device's camera; (viii) data indicating digital media or a game is being displayed on the mobile device screen; or (ix) data indicating whether the battery temperature is below a first temperature level. Examples of uses and determinations may include a combination of one or more of the following: (a) determining that the predetermined height of the mobile device is 1.0 meter or the height of a countertop, desk, or table when the data indicates that the mobile device's battery is charging or the mobile device is oriented in a horizontal orientation or the mobile device's inertial sensors measure no motion or the data indicates that hands-free calling is being used during the call, (b) determining that the predetermined height of the mobile device is 1.0 meter or the height of the mid-upper body of a seated user when the data indicates that digital media or a game is being displayed on the mobile device screen, or (c) determining that the predetermined height of the mobile device is 1.0 meter or the height of the mid-upper body of a seated user when a call is being conducted on the mobile device and the mobile device is oriented in an upright orientation or the data indicates that hands-free calling is being used during the call. If the data indicates that handset or speakerphone is not being used, the height may be determined to be 1.5 or 2.0 meters, or the height of the user's ears when the user is sitting or standing, respectively, and 1.5 meters may be selected if walking motion is not detected by the inertial sensor, and 2.0 meters may be selected if walking motion is detected by the inertial sensor, or if sitting or standing cannot be determined, an average of 1.75 meters may be used, or the first predetermined height may be selected rather than the second predetermined height if the sum of the known surface elevation and the first predetermined height (e.g., 1.5 meters) is closer to the estimated elevation of the mobile device than the sum of the known surface elevation and the second predetermined height (e.g., 2.0 meters).

[0053] Various embodiments are contemplated for performing various combinations of the processes described herein, including embodiments for performing various combinations of the processes enumerated for estimating the height at which the mobile device is located from a surface based on second data (e.g., the methods of FIGS. 3A through 3H ) and the methods enumerated for determining a location context based on first data (e.g., the embodiments of sets 1 through 10, and any other enumerated embodiments for determining a location context based on first data). By way of example, some embodiments may include the methods of FIGS. 3A, 3D, 3E, 3F, 3G, 3H ... Figures 3G and 3H (where each embodiment implements various combinations of the approaches described for each method). Another embodiment may implement the methods of FIGS. 3A, 3D, 3E, 3F, Figures 3G and 3Hor various combinations thereof may be performed individually. When multiple types of second data are enumerated for a location context, not all types of second data enumerated for that location context need to be used, obtained, or tested against conditions to determine a particular predetermined height. Various embodiments of a particular location context may use, obtain, and test different types of enumerated second data. For example, in some embodiments, only the types of second data required to test only one or some of the enumerated groups of conditions are used and obtained to determine whether the enumerated predetermined height is an estimated height. When multiple possible conditional tests of second data are enumerated to determine whether the estimated height is a particular predetermined height, not all of the enumerated conditional tests of second data for the particular predetermined height need to be performed, and various embodiments that determine whether the estimated height is a particular predetermined height may test different types of second data for each condition. When examining a set of conditions for a type of second data to determine whether the estimated height is a particular predetermined height, the examination of the set may stop when one of the conditions for one of the types of second data is not satisfied. Similarly, if multiple predetermined heights (e.g., first, second, ..., Nth predetermined heights) are possibly enumerated for a location context, not all enumerated predetermined heights need to be used or considered, and various embodiments may determine whether the estimated height is a predetermined height in a different set of enumerated predetermined heights for the location context, where the set includes one or more predetermined heights. Thus, various embodiments may use any of the enumerated location contexts, different types of second data enumerated for the location contexts, and different combinations of the different predetermined heights enumerated for the location contexts.

[0054] The estimated height values ​​given herein are exemplary and are not the only possible heights, and while meters have been used primarily to indicate possible heights from a surface, any unit of measurement for height may be used.

[0055] In some embodiments, instead of a single height (e.g., 2.0 meters), a range of heights (e.g., 1.5-2.25 meters) can be used, which may be useful in accounting for unknown heights of a user or other objects (e.g., a car seat, a pocket in a bag, the position of a bag on top of an object, etc.). When using a range of heights, a predetermined height (e.g., 1.5 meters to 2.25 meters) that does not exceed an outer edge height limit (e.g., 1.5 meters or 2.25 meters) of the range (e.g., 1.5 meters to 2.25 meters) can be used as an estimated height if the predetermined height matches the difference between the initial estimated altitude of the mobile device and the known altitude of the surface, or any of the outer edge height limits of the range is used as an estimated height if the predetermined height of the outer edge height limit is close to said difference, with the assumption that the closer the predetermined height is to said difference, the more accurate the predetermined height is compared to other predetermined heights. Such an assumption reduces the possibility of over-calibration that may occur if another outer edge height limit is used. A similar approach can be used when no range is used, but two or more possible predetermined heights are used, and the selection among the possible predetermined heights includes selecting the predetermined height that is closest to the difference.

[0056] In some uses of the processes described herein, the height may be determined to a fine degree (e.g., within a foot, an inch, or other distance from the actual height), which may be useful in directing a user to a particular item at a particular height (e.g., on a shelf, in which case the mobile device may instruct the user to "look one shelf down to find low-sodium chicken noodle soup"). Of course, such fine precision need not be achieved during use of each process described herein, and coarser precision (e.g., within 0.5 to 1.0 meters from the actual height) is acceptable for other uses, such as those described in connection with step 260 of FIG. 2A and step 295 of FIG. 2B.

[0057] Various possible heights above a surface (e.g., ground or floor) at which a mobile device may be located are described herein. In some embodiments, the height of something the mobile phone is expected to be on or in (e.g., the height of a counter, desk, table, pant pocket, bicycle handlebars, car console, etc.) is known and can be used as a possible estimated height. Such known heights can be surveyed over time or obtained from a data source. In some embodiments, the height of an object can be adjusted based on the height of another object (e.g., the height of a pant pocket can be adjusted depending on the height of the shoes (e.g., flats, boots, heels, etc.) worn by the user).

[0058] [calibration] There are various approaches to estimating the altitude of a mobile device (e.g., mobile device 120 of FIG. 1). In a barometric positioning system, pressure measurements from a pressure sensor in the mobile device, along with atmospheric pressure measurement(s) from a network of calibrated reference pressure sensors and ambient temperature measurements from the network or other sources, can be used to calculate the altitude. mobile) may be calculated by the mobile device, server, or other device receiving the required information as follows: JPEG0007635127000003.jpg21153...(Formula 2) Here, P mobile is an estimate of the pressure, which must be accurate to within a tolerance (e.g., less than 5 Pa) from the true pressure at the location of the mobile device, as measured by the pressure sensor in the mobile device, and P sensor is an estimate of the pressure at the reference pressure sensor location, T is an estimate of the temperature (e.g., in Kelvin) at the reference pressure sensor location or another location where a remote temperature sensor is located, and altitude sensor is the estimated altitude of the reference pressure sensor estimated within a desired altitude error (e.g., less than 1.0 meter), g corresponds to acceleration due to gravity, R is the gas constant, and M is the molar mass of air (e.g., dry air or otherwise). The minus sign (-) may be replaced with a plus sign (+) in alternative embodiments of Equation 2, as will be appreciated by those skilled in the art. The estimate of pressure at the reference pressure sensor location can be converted to an estimated reference level pressure corresponding to the reference pressure sensor, in that it specifies an estimate of pressure at the latitude and longitude of the reference pressure sensor, but at a reference level altitude that is likely to be different from the altitude of the reference pressure sensor. The reference level pressure may be determined as follows: JPEG0007635127000004.jpg21153...(Formula 3) Here, P sensor is the estimate of the pressure at the reference pressure sensor location, and P ref is the reference level pressure estimate, and h ref is the reference level altitude. mobile can be calculated using Equation 3, where altitude ref is altitude sensor Replaced by P ref , P sensor can be replaced by. JPEG0007635127000005.jpg21153...(Formula 4) Reference altitude ref can be any altitude, and is often set to mean sea level (MSL). When two or more reference level pressure estimates are available, they are combined (e.g., using an average, weighted average, or other suitable combination of reference pressures) into a single reference level pressure estimate, which is referred to as the reference level pressure estimate P ref Used for.

[0059] Pressure sensors in mobile devices are typically inexpensive and prone to drift over time. Thus, pressure sensors in mobile devices must be calibrated frequently to ensure that the pressure measurements at the mobile device's altitude have the accuracy required for accurate estimation of the mobile device's altitude. One approach to calibrating a pressure sensor in a mobile device involves determining a calibration adjustment (C) that is applied to the pressure measurements (P) made by the pressure sensor. mobile ), the true altitude at which the mobile device is located. truth ) within the allowable distance of the estimated altitude ( mobile ) is obtained. One such approach uses the following equation to determine the calibration adjustment (C): JPEG0007635127000006.jpg21153...(Formula 5) The true altitude at which the mobile device is located. truth ) is the known altitude of the surface. surface ) and the estimated height (h estimated ), it can be replaced as follows: JPEG0007635127000007.jpg21153...(Formula 6) This results in the following equation: JPEG0007635127000008.jpg21153...(Formula 7) Alternatively, the left and right sides of Equation 7 may not be equal, but may be within a tolerable altitude from each other, such as 0.0 to 0.5 meters. The known altitude of the surface surface ) can be determined in a variety of ways. For example, an identifier for the surface can be determined and the identifier can be used to look up the elevation of the surface from a floor or terrain database. The identifier can be determined in a variety of ways, such as user input identifying the surface, detection of communication between a mobile device and a device (e.g., a POS system, a thermostat, a WiFi beacon) that is in an area associated with the surface, an initial estimated location of the mobile device that is in the area of ​​the surface, or otherwise.

[0060] Alternatively, pressure differences depending on height can be used to assist in determining the calibration adjustment (C) as described below. For example, Equation 8 below can be used to derive Equation 9: JPEG0007635127000009.jpg21153...(Formula 8) JPEG0007635127000010.jpg21153...(Formula 9) Here, P represents the mobile pressure in this particular context in showing how slight height discrepancies of the mobile device may translate into the calibration value of the mobile device's pressure sensor. Thus, the calibration adjustment value (C) can be determined as follows: JPEG0007635127000011.jpg21153...(Formula 10) At this time, JPEG0007635127000012.jpg21153...(Formula 11) It is.

[0061] [Technical benefit] Mobile devices are used to estimate the altitude of a user in various environments or to estimate the altitude of a surface on which the mobile device resides (e.g., a floor in a building or the ground outside). When the estimated altitude is based on (i) a reference pressure from a network of reference pressure sensors and (ii) pressure measurements from a pressure sensor in the mobile device, limitations in the functionality of the pressure sensor in the mobile device, such as sensor drift over time, can affect the accuracy of the estimated mobile device altitude by as much as several meters or can prevent the accuracy from being within an altitude threshold (e.g., 1.0 meter or less). Periodic calibration of the pressure sensor in the mobile device is necessary for accurate altitude estimation. Conventional approaches to calibrating a pressure sensor with respect to a known altitude of a surface make assumptions about the unknown height at which the mobile device is located above the surface, but these assumptions can introduce errors into the calibration results if the true height of the mobile device above the surface differs from the assumed height by more than a height threshold (0.5 meters or 1.0 meters). When the altitude of a surface above which the mobile device is located is used to determine the estimated altitude of the mobile device, the uncertainty introduced in the altitude of the mobile device from the surface due to lack of technology for determining those altitudes can affect the accuracy of the estimated mobile device altitude by as much as several meters or can prevent accuracy to within an altitude threshold (e.g., 1.0 meter or less). The process described herein overcomes the above technical limitations and generates new useful data, such as an improved estimated height from the surface that is more accurate and more reliable compared to an assumed or unknown height. The improved estimated height generated by the process described herein allows for (i) improved calibration results, (ii) an improved estimated location that allows for faster emergency response times or otherwise improves the usefulness of the estimated location, and (iii) an improved estimated altitude of the surface.

[0062] [Other aspects] Any methodology (also referred to as a "process" or "approach") described herein or enabled by the disclosure herein may be implemented by hardware components (e.g., devices), software modules (e.g., stored on a machine-readable medium), or a combination thereof. In particular, any methodology described herein or enabled by the disclosure herein may be implemented by any concrete and specific system described herein. As an example, a device may include at least one of one or more computing devices, processors, controllers, integrated circuits, chips, systems on a chip, servers, programmable logic devices, field programmable gate arrays, electronic devices, special purpose circuits, and suitable devices described herein or otherwise known to those of skill in the art. Contemplated herein are one or more non-transitory machine-readable media embodying program instructions that, when executed by one or more devices, cause the one or more devices to perform or implement operations including steps of any of the methods described herein. As used herein, a machine-readable medium includes all forms of machine-readable media (e.g., one or more non-volatile or volatile storage media, removable or non-removable media, integrated circuit media, magnetic storage media, optical storage media, or any other storage media, including RAM, ROM, and EEPROM), such as may be patentable under the laws of the jurisdiction in which the invention is filed, but does not include machine-readable media that may not be patentable under the laws of the jurisdiction in which the invention is filed. Also contemplated herein are systems including one or more apparatuses and one or more non-transitory machine-readable media for performing any of the methods described herein. Also contemplated herein are one or more apparatuses configured, operable, or adapted to perform or implement, or to perform or implement, operations including steps of any of the methods described herein. Not in the prior art, each method described herein exhibits a particular set of rules in a process flow that provide significant advances in the field of determining one or more heights of one or more mobile devices from a surface.The steps of the methods described herein may be out of sequence and may be performed in parallel or, where possible, out of the order described. As will be appreciated by those skilled in the art, the steps of the various methods described herein may be combined to form any number of methods. Any method step or feature disclosed herein may be omitted from the claims for any reason. Some well-known structures and devices have not been shown in the drawings to avoid obscuring the concept of the invention. When two things are "coupled" to each other, the two things may be directly connected to each other or separated by one or more intervening objects. When no line or intervening object connects two particular things, coupling of the things is contemplated in at least one embodiment unless otherwise noted. When an output of one thing and an input of another thing are coupled to each other, the information sent from the output is received by the input in its output form or a modified form thereof, even if the information has passed through one or more intermediaries. Any known communication paths and protocols may be used to transmit the information disclosed herein (e.g., data, commands, signals, bits, symbols, chips, etc.) unless otherwise noted. Terms such as "comprise," "comprising," "include," "including," and the like should be construed in the inclusive sense (i.e., not limited to) rather than the exclusive sense (i.e., consisting only of). Also, terms using the singular or plural include the plural or singular, respectively, unless specifically stated otherwise. The terms "or" and "and," when used in the detailed description, include any and all of the listed items unless specifically stated otherwise. The terms "some," "any," and "at least one" refer to one or more.The terms "may" or "can" are used herein to illustrate examples rather than requirements, e.g., something may or can perform an action or have a characteristic, but not necessarily have to perform that action or have that characteristic in each embodiment, and in at least one embodiment, something will perform that action or have that characteristic. Unless a different approach is described, access to data from the source of the data may be performed using known techniques (e.g., the requesting component requests the data from the source via a query or other known approach, the source searches and finds the data, the source collects the data and sends it to the requesting component).

[0063] 4 illustrates components of a transmitter, a mobile device, and a server. Example communication paths are indicated by arrows between the components.

[0064] As an example in FIG. 4, each transmitter may include a mobile device interface 11 (e.g., an antenna and RF front-end components known to those of skill in the art or disclosed herein) for exchanging information with a mobile device, one or more processors 12, memory / data sources 13 for storing and retrieving information and / or program instructions, an air sensor 14 for measuring environmental conditions (e.g., pressure, temperature, etc.) at or near the transmitter, a server interface 15 (e.g., an antenna, network interface, etc.) for exchanging information with a server, and any other components known to those of skill in the art. The memory / data source 13 may include a memory that stores software modules containing executable instructions from which the processor 12 may execute various operations, including (i) performing some or all of the methods as described herein or as one of ordinary skill in the art would understand to be executable by the transmitter, (ii) generating positioning signals for transmission using at least one of a selected time, frequency, code, and phase, (iii) processing signals received from the mobile device or other sources, or (iv) processing otherwise required by the operations described herein. The signals generated and transmitted by the transmitter may convey various information that may identify the transmitter, its location, environmental conditions at or near the transmitter, and / or other information as determined by the mobile device or server, and / or as otherwise known to one of ordinary skill in the art. The air sensor 14 may be integral with the transmitter or may be separate from the transmitter and may be co-located with the transmitter or located near (e.g., within a distance threshold) the transmitter.

[0065] As an example of FIG. 4, the server may include a mobile device interface 21 (e.g., an antenna or network interface, etc.) for exchanging information with the mobile device, one or more processors 32, a memory / data source 33 for storing and retrieving information and / or program instructions, a transmitter interface 34 (e.g., an antenna or network interface, etc.) for exchanging information with the transmitter, and any other components known to those of skill in the art. The memory / data source 33 may include memory for storing software modules containing executable instructions, and the processor 32 may execute instructions from the software modules to perform various operations, including (i) performing some or all of the methods as described herein or as those of skill in the art would understand to be executable by the server, (ii) estimating the altitude of the mobile device, (iii) calculating an estimated location of the mobile device, or (iv) otherwise processing required by the operations described herein. The steps performed by the server as described herein may be performed on another device remote from the mobile device, including an enterprise computer or any other suitable device.

[0066] Certain aspects disclosed herein relate to estimating the location of a mobile device, where the location may be represented, for example, by latitude, longitude, and / or altitude coordinates, x-axis, y-axis, and / or z-axis coordinates, angular coordinates, or other representations. Various techniques for estimating the location of a mobile device may be used, including trilateration, which is a process that uses geometry to estimate the location of a mobile device using the distance traveled by different "positioning" (or "ranging") signals received by the mobile device from different beacons (e.g., terrestrial transmitters and / or satellites). If location information, such as the time of transmission and the time of receipt of a positioning signal from a beacon, is known, the difference in those times multiplied by the speed of light provides an estimate of the distance traveled by the positioning signal from the beacon to the mobile device. The different estimated distances corresponding to the different positioning signals from different beacons may be used along with location information, such as the locations of the beacons, to estimate the location of a mobile device. Positioning systems and methods for estimating a mobile device's location (in terms of at least one of latitude, longitude, and altitude) based on positioning signals from beacons (e.g., transmitters and / or satellites) and / or atmospheric measurements are described in commonly assigned U.S. Patent No. 8,130,141, issued March 6, 2012, and U.S. Patent Publication No. 2012 / 0182180, published July 19, 2012. Note that the term "positioning system" may refer to satellite systems (e.g., Global Navigation Satellite Systems (GNSS) such as GPS, GLONASS, Galileo, and Compass / Beidou), terrestrial transmitter systems, and hybrid satellite / terrestrial systems.

[0067] This application is related to the following related application: U.S. Patent Application No. 6,279,849, filed Jan. 13, 2019, and entitled "SYSTEM AND METHOD FOR DETERMINING HEIGHT OF A MOBILE DEVICE ABOVE A SURFACE," the contents of which are incorporated herein by reference in their entirety.

Claims

1. 1. A method for determining one or more heights of one or more mobile devices from a surface, comprising: determining, by one or more processors, a location context of the mobile device by selecting a location context from among two or more of: (i) with a user on foot; (ii) on or with a user on a bicycle; (iii) in a vehicle; (iv) stationary; (v) dropped and on the surface; and (vi) at a known location; identifying, by the one or more processors, second data to be acquired for use in determining an estimated height at which the mobile device is located above the surface based on the determined location context, the second data including one or more of: (i) at least one measurement result determined by at least one sensor of the mobile device; and (ii) at least one condition indicator of equipment of the mobile device; acquiring, by the one or more processors, the second data; determining, by the one or more processors, the estimated height at which the mobile device is located above the surface based on the acquired second data; calibrating a pressure sensor of the mobile device by the one or more processors based on the estimated height from the surface, or estimating an altitude of the mobile device as a sum of an altitude of the surface and the estimated height from the surface, or determining an estimated altitude of the surface as a difference between the estimated altitude of the mobile device and the estimated height from the surface; A method comprising:

2. The step of identifying second data to be acquired comprises: identifying, by the one or more processors, one or more possible estimated heights at which the mobile device may be located from the surface based on the determined location context; identifying, by the one or more processors, data associated with the probable estimated height as the second data; The method of claim 1 , comprising:

3. The method of claim 1 , comprising calibrating, by the one or more processors, the pressure sensor of the mobile device based on the estimated height from the surface.

4. 2. The method of claim 1, comprising estimating, by the one or more processors, the sum of the altitude of the surface and the estimated height above the surface relative to the altitude of the mobile device.

5. 2. The method of claim 1, comprising determining, by the one or more processors, the difference between the estimated altitude of the mobile device and the estimated height above the surface as the estimated altitude of the surface.

6. the location context identifies the mobile device as being with a user on foot; The step of determining the estimated height at which the mobile device is located above the surface comprises: determining, by the one or more processors, whether the mobile device is being used to conduct a telephone call; The estimated height is (a) a first predetermined height if the mobile device is being used to conduct a telephone call and the second data includes a first state indicator that identifies a hands-free call being used during the telephone call; (b) a second predetermined height when the mobile device is being used to conduct a phone call and the second data indicates any of the following conditions: (i) a second state indication is obtained and identifies that speakerphone or video calling is being used during the phone call; or (ii) a light measurement from a light sensor of the mobile device is obtained and exceeds a first light level and an orientation measurement from a gyroscope of the mobile device is obtained and indicates that the mobile device is not in an upright orientation; or (iii) a sound measurement from a microphone of the mobile device exceeds a volume threshold. (c) a third predetermined height if the mobile device is being used to conduct a phone call and the second data indicates any of the following conditions: (i) the first status indication is not obtained, or the first status indication is obtained and identifies that hands-free calling is not being used during the call, and the second status indication is not obtained, or the second status indication is obtained and identifies that speakerphone or video calling is not being used during the call; or (ii) the light measurement from the light sensor of the mobile device is obtained and does not exceed the first light level, and the orientation measurement from the gyroscope of the mobile device is obtained and indicates that the mobile device is in an upright orientation; (d) a fourth predetermined height when the mobile device is not being used to conduct a phone call and the second data includes (i) a motion state indicator from a pedometer of the mobile device that identifies a walking or running motion as having been recorded, and (ii) the light measurement from the light sensor of the mobile device that is below the first light level; (e) a fifth predetermined height if the mobile device is not being used to conduct a telephone call and the second data includes (i) the motion state indicator identifying a walking or running motion as having been recorded, and (ii) the light measurement from the light sensor of the mobile device that exceeds the first light level; (f) a sixth predetermined height if the mobile device is not being used to conduct a telephone call and the second data includes the motion state indicator identifying that a walking motion or a running motion was not recorded; or (g) a seventh predetermined height when the mobile device is not being used to conduct a phone call and the second data includes a camera status indicator indicating that the camera of the mobile device is active; determining, by the one or more processors, that The method of claim 1 , comprising:

7. the location context identifies the mobile device as being with a user on foot; The step of determining the estimated height at which the mobile device is located above the surface comprises: determining, by the one or more processors, that the mobile device is being used to perform a telephone call; The estimated height is (a) a first predetermined height if the second data includes a first status indicator that identifies that a hands-free call is being used during the call; (b) a second predetermined height if the second data indicates any of the following conditions: (i) a second state indication is obtained and identifies that speakerphone or video calling is being used during the call; or (ii) a light measurement from a light sensor of the mobile device is obtained and exceeds a first light level and an orientation measurement from a gyroscope of the mobile device is obtained and indicates that the mobile device is not in an upright orientation; or (iii) the sound measurement from a microphone of the mobile device exceeds a volume threshold; or (c) a third predetermined height if the second data indicates any of the following conditions: (i) the first status indication is not obtained, or the first status indication is obtained and identifies that hands-free calling is not used during the call, and the second status indication is not obtained, or the second status indication is obtained and identifies that speakerphone or video calling is not used during the call; or (ii) the light measurement from the light sensor of the mobile device is obtained and does not exceed the first light level, and the orientation measurement from the gyroscope of the mobile device is obtained and indicates that the mobile device is in an upright orientation. determining, by the one or more processors, that The method of claim 1 , comprising:

8. the location context identifies the mobile device as being with a user on foot; The step of determining the estimated height at which the mobile device is located above the surface comprises: determining, by the one or more processors, that the mobile device is not being used to conduct a call; The estimated height is (a) if the second data includes (i) a motion state indicator from a pedometer of the mobile device that identifies a walking or running motion as having been recorded, and (ii) a light measurement from a light sensor of the mobile device that is below a first light level, a first predetermined height; (b) if the second data includes (i) the motion state indicator identifying a walking or running motion recorded, and (ii) the light measurement from the light sensor of the mobile device exceeding the first light level, a second predetermined height; (c) a third predetermined height if the second data includes the motion status indicator that identifies that a walking motion or a running motion was not recorded; or (d) if the second data indicates that the camera of the mobile device is active, a fourth predetermined height; determining, by the one or more processors, that The method of claim 1 , comprising:

9. the location context identifies the mobile device as being mounted on a bicycle or with a user on a bicycle; The step of determining the estimated height at which the mobile device is located above the surface comprises: The estimated height is (a) a first predetermined height if the second data includes a light measurement from a light sensor of the mobile device that is below a first light level; (b) a second predetermined height if the second data indicates any of the following conditions: (i) the light measurement from the light sensor of the mobile device is obtained and exceeds the first light level, and an orientation measurement from a gyroscope of the mobile device is obtained and indicates that the mobile device is not in an upright orientation; or (ii) a descent recorder usage indicator is obtained and identifies that movement information is displayed on a screen of the mobile device; or (c) a third predetermined height if the second data indicates any of the following conditions: (i) the light measurement from the light sensor of the mobile device is obtained and exceeds the first light level, and the orientation measurement from the gyroscope of the mobile device is obtained and indicates that the mobile device is in an upright orientation; or (ii) a video recording state indicator identifies that video is being recorded and the orientation measurement from the gyroscope of the mobile device is obtained and indicates that the mobile device is in an upright orientation. The method of claim 1 , comprising determining, by the one or more processors, that

10. the location context identifies the mobile device as being in a vehicle; The step of determining the estimated height at which the mobile device is located above the surface comprises: The estimated height is (a) a first predetermined height if the second data indicates any of the following conditions: (i) a light measurement from a light sensor of the mobile device is obtained below a first light level; or (ii) the light measurement from the light sensor of the mobile device is obtained above the first light level and a battery charge status indicator is obtained to identify that a battery of the mobile device is being charged; or (iii) the battery charge status indicator is obtained to identify that the battery of the mobile device is being charged and a call status indicator is obtained to identify that the mobile device is not being used to conduct a call; or (iv) a first status indicator is obtained to identify that hands-free calling is being used while a call is being conducted; (b) a second predetermined height if the second data indicates any of the following conditions: (i) a second state indicator is obtained and identifies speakerphone as being used during a call; or (ii) the call state indicator is obtained and identifies the mobile device as being used to conduct a call, the light measurement from the light sensor of the mobile device is obtained and exceeds the first light level, and an orientation measurement from a gyroscope of the mobile device is obtained and indicates the mobile device is not in an upright orientation; or (c) a third predetermined height if the call status indicator is obtained and identifies the mobile device as being used to conduct a call and the second data indicates any of the following conditions: (i) the first status indicator is not obtained or a hands-free call is not being used during the call; or (ii) the light measurement from the light sensor of the mobile device is obtained and does not exceed the first light level; or (iii) the orientation measurement from the gyroscope of the mobile device is obtained and indicates the mobile device is in an upright orientation. The method of claim 1 , comprising determining, by the one or more processors, that

11. the location context identifies the mobile device being on the surface after a drop; the second data includes any one or more of measurements from an accelerometer of the mobile device; The step of determining the estimated height at which the mobile device is located above the surface comprises: (a) a first initial measurement of the accelerometer identifies a falling motion of the mobile device and a first subsequent measurement of the accelerometer identifies a stationary state of the mobile device; or (b) a second initial measurement of the accelerometer identifies a crash of the mobile device against the surface and a second subsequent measurement of the accelerometer identifies a stationary state of the mobile device. determining, by the one or more processors, that the estimated height is zero in a unit of height measurement.

12. the location context identifies the mobile device being on the surface after a drop; the second data includes one or more measurements from a pressure sensor of the mobile device; The step of determining the estimated height at which the mobile device is located above the surface comprises:

2. The method of claim 1, comprising determining, by the one or more processors, that the estimated height is zero in height measurement units when (i) both a first measurement of pressure and a subsequent second measurement of pressure are measured by the pressure sensor of the mobile device during a period of time that does not exceed a time threshold, and (ii) the second measurement of pressure is higher than the first measurement of pressure.

13. The location context identifies the mobile device as being stationary; The step of determining the estimated height at which the mobile device is located above the surface comprises: The estimated height is (a) if the second data indicates any of the following conditions: (i) a battery charge state indication is obtained and identifies the mobile device's battery as being charged, an orientation measurement is obtained from a gyroscope of the mobile device and indicates that the mobile device is in a horizontal orientation, and data identifying an area in which the mobile device is located is obtained and identifies the mobile device as being in a first type of location that is likely to be placed on a table, desk, or counter; or (ii) the battery charge state indication is obtained and identifies the mobile device's battery as not being charged, a light measurement from a light sensor of the mobile device is obtained and does not exceed a first light level, and the orientation measurement is obtained from the gyroscope of the mobile device and indicates that the mobile device is in a horizontal orientation; or (iii) the battery charge state indication is obtained and identifies the mobile device's battery as not being charged and a first predetermined height if the light measurement from the light sensor of the mobile device is obtained above the first light level and the orientation measurement from the gyroscope of the mobile device indicates that the mobile device is in a horizontal orientation, or (iv) a battery temperature measurement is obtained indicating that the battery temperature of the mobile device is below a first temperature level, the orientation measurement from the gyroscope of the mobile device indicates that the mobile device is in a horizontal orientation, and the battery charge state indication is obtained to identify that the battery of the mobile device is not charging, or (v) the battery temperature measurement is obtained indicating that the battery temperature of the mobile device is below the first temperature level and the orientation measurement from the gyroscope of the mobile device indicates that the mobile device is in a horizontal orientation, or (vi) an application for presenting media is running; (b) a second predetermined height if the second data includes (i) the battery charge state indicator identifying the battery of the mobile device as being charged, (ii) the orientation measurement from the gyroscope of the mobile device indicating the mobile device is in a horizontal orientation, and (iii) the data identifying an area in which the mobile device is located identifying the mobile device as being in a second type of location where the mobile device is likely to be located on a chair, on a user's lap, or in a bag on a surface; (c) a third predetermined height if the second data indicates any of the following conditions: (i) the light measurement obtained from the light sensor of the mobile device is not above the first light level, the orientation measurement obtained from the gyroscope of the mobile device is not in a horizontal orientation, and the battery charge state indication is obtained to identify that the battery of the mobile device is not charging; or (ii) the light measurement obtained from the light sensor of the mobile device is not above the first light level, and the orientation measurement obtained from the gyroscope of the mobile device is not in a horizontal orientation; (d) a fourth predetermined height if the second data indicates any of the following conditions: (i) the battery charge state indication is obtained and identifies the battery of the mobile device as being charged, and the orientation measurement from the gyroscope of the mobile device is obtained and indicates that the mobile device is not in a horizontal orientation; or (ii) the battery charge state indication is obtained and identifies the battery of the mobile device as not being charged, the light measurement from the light sensor of the mobile device is obtained and does not exceed the first light level, and the orientation measurement from the gyroscope of the mobile device is obtained and indicates that the mobile device is not in a horizontal orientation; (e) if the second data indicates any of the following conditions: (i) the battery temperature measurement is taken to indicate that the battery temperature of the mobile device is below the first temperature level, the orientation measurement from the gyroscope of the mobile device is taken to indicate that the mobile device is not in a horizontal orientation, and the battery charge state indication is taken to identify that the battery of the mobile device is not charging; or (ii) the battery temperature measurement is taken to indicate that the battery temperature of the mobile device is below the first temperature level. a fifth predetermined height if (iii) the orientation measurement from the gyroscope of the mobile device is obtained to indicate that the mobile device is not in a horizontal orientation, or (iii) the battery temperature measurement is obtained to indicate that the battery temperature of the mobile device is not below the first temperature level and the battery charge state indication is obtained to identify that the battery of the mobile device is not charging, or (iv) the battery temperature measurement is obtained to indicate that the battery temperature of the mobile device is not below the first temperature level; (f) if the second data includes a call status indicator that identifies a video call being used, a sixth predetermined height; or (g) a seventh predetermined height if the second data includes a camera state indicator that identifies the camera of the mobile device as capturing an image. The method of claim 1 , comprising determining, by the one or more processors, that

14. The location context identifies that the mobile device is in a known location; The step of determining the estimated height at which the mobile device is located above the surface comprises: The estimated height is (a) the height of a countertop, desk, or table if the second data includes (i) data indicating that a battery of the mobile device is charging, or (ii) data indicating that the orientation of the mobile device is horizontal, or (iii) data indicating that an inertial sensor of the mobile device does not measure motion, or (iv) data indicating that hands-free calling is being used during the call; (b) if the second data includes data indicating that digital media or a game is being displayed on a screen of the mobile device, the height of the mid-torso of a seated user; or (c) if the second data includes data indicating that (i) a call is being conducted on the mobile device and the mobile device is in an upright orientation, or (ii) a hands-free or speakerphone is not being used during the call, the height of the user's ears when the user is sitting or standing. The method of claim 1 , wherein the one or more processors determine that:

15. A system for determining one or more heights of one or more mobile devices from a surface, the system comprising one or more processors configured to perform a method according to any of claims 1 to 14.

Images