RELATED MATTERS

This PCT application claims benefit of and priority to co-pending U.S. Provisional Patent Application No. 62/121 ,480, filed February 26, 2015, titled OPPORTUNISTIC CALIBRATION OF A BAROMETER IN A MOBILE DEVICE," and co-pending U.S. Non-provisional Application No. 15/052,598, filed February 24, 2016, titled OPPORTUNISTIC CALIBRATION OF A

BAROMETER IN A MOBILE DEVICE," which are assigned to the assignee hereof and which are hereby incorporated in their entirety by reference.

Background

1. Field

[0001] The subject matter disclosed herein relates to electronic devices, and more particularly to methods, apparatuses and articles of manufacture for use in a mobile device having a barometer.

2. Information

[0002] As its name implies, a mobile device may be moved about, e.g. typically being carried by a user and/or possibly a machine. By way of some non-limiting examples, a mobile device may take the form of a cellular telephone, a smart phone, a tablet computer, a laptop computer, a wearable computer, a navigation and/or tracking device, etc.

[0003] In certain instances, particularly with indoor navigation applications, it may be useful to determine an altitude level of a mobile device. This may be particularly useful in navigating multi-story environments in which a mobile device may be provided with navigation assistance data such as locations of transmitters, radio heatmaps, digital maps for display, routing maps, etc.

[0004] A mobile device may be determined to be located on a particular floor of a building using one or more wireless signal-based positioning techniques. In particular scenarios, it may be desirable to provide estimated locations of a mobile device to include an altitude level component. In a dense urban environment including multistory skyscrapers, for example, merely providing longitude and latitude components for a location in the absence of an altitude level component may be of limited utility for some services (e.g., emergency 91 1 services).

[0005] While obtaining a position fix from acquisition of satellite positioning system (SPS) signals in a rural or single-story suburban environment may provide an altitude level component of sufficient accuracy for most services, an SPS or other like signal-based position fix may not provide an altitude level component with sufficient accuracy or precision.

[0006] In certain implementations, a network carrier may populate a dense urban environment with low-power beacon transmitters and/or femtocells to assist subscriber mobile devices in accurately resolving an altitude level component of locations of the mobile devices. Such a deployment of low power beacon transmitters and/or femtocells may, however, prove too costly and/or provide for limited/sporadic coverage.

[0007] In another particular implementation, a mobile device may resolve an altitude level component of its location (e.g., as being on a particular floor of a building) by obtaining atmospheric pressure measurements using an onboard barometer and comparing such to a reference atmospheric pressure. However, atmospheric pressure tends to change overtime, and hence a reference atmospheric pressure (local to the mobile device) may need to be updated frequently. Rather than relying on other devices to provide reference atmospheric pressure updates, it may be useful for a mobile device to determine a reference atmospheric pressure on its own, for example, through one or more barometer calibration processes which may identify a reference atmospheric pressure corresponding to a particular altitude level.

SUMMARY

[0008] Briefly, one particular implementation is directed to a method, at a mobile device, comprising: determining that the mobile device is located at a first frequently visited location based, at least in part on an association of measured characteristics of radio frequency signals with expected signature values or detection that the mobile device is receiving power from an external power source, or a combination thereof; determining that a barometric pressure sensor on board the mobile device is in a calibrated state; obtaining a first pressure measurement from the barometric pressure sensor while located at the first frequently visited location; storing a first indication of an altitude of the mobile device and an indication of the first frequently visited location, the indication of the altitude of the mobile device being based, at least in part, on the first pressure measurement; determining that the mobile device has returned to the first frequently visited location; obtaining a second pressure measurement from the barometric pressure sensor while located at the frequently visited location; and calibrating the barometric pressure sensor based, at least in part, on the stored first indication of the altitude of the mobile device and on the second pressure measurement.

[0009] Another particular implementation is directed to a mobile device comprising: a barometric pressure sensor; and one or more processors coupled to the barometric pressure sensor by a bus, the one or more processors being configured to: determine that the mobile device is located at a first frequently visited location based, at least in part on an association of measured characteristics of radio frequency signals with expected signature values or detection that the mobile device is receiving power from an external power source, or a combination thereof; determine that the barometric pressure sensor is in a calibrated state; obtain a first pressure measurement from the barometric pressure sensor while the mobile device is located at the frequently visited location; store a first indication of an altitude of the mobile device and an indication of the first frequently visited location, the first indication of the altitude of the mobile device being based, at least in part, on the first pressure measurement; determine that the mobile device has returned to the first frequently visited location; obtain a second pressure measurement from the barometric pressure sensor while located at the first frequently visited location; and calibrate the barometric pressure sensor based, at least in part, on the stored first indication of the altitude of the mobile device and on the second pressure measurement.

[0010] Another particular implementation is directed to non-transitory storage medium comprising computer readable instructions stored thereon which are executable by a processor of a mobile device to: determine that the mobile device is located at a first frequently visited location based, at least in part on an association of measured characteristics of radio frequency signals with expected signature values or detection that the mobile device is receiving power from an external power source, or a combination thereof; determine that a barometric pressure sensor on board the mobile device is in a calibrated state; obtain a first pressure measurement from the barometric pressure sensor while the mobile device is located at the first frequently visited location; store a first indication of an altitude of the mobile device and an indication of the first frequently visited location, the indication of the altitude of the mobile device being based, at least in part, on the first pressure measurement; determine that the mobile device has returned to the first frequently visited location; obtain a second pressure measurement from the barometric pressure sensor while located at the first frequently visited location; and calibrate the barometric pressure sensor based, at least in part, on the stored first indication of the altitude of the mobile device and on the second pressure measurement.

[0011] Another particular implementation is directed to a mobile device comprising: means for determining that the mobile device is located at a first frequently visited location based, at least in part on an association of measured characteristics of radio frequency signals with expected signature values or detection that the mobile device is receiving power from an external power source, or a combination thereof; means for determining that a barometric pressure sensor on board the mobile device is in a calibrated state; means for obtaining a first pressure measurement from the barometric pressure sensor while located at the first frequently visited location; means for storing a first indication of an altitude of the mobile device and an indication of the first frequently visited location, the first indication of the altitude of the mobile device being based, at least in part, on the first pressure measurement; means for determining that the mobile device has returned to the first frequently visited location; means for obtaining a second pressure measurement from the barometric pressure sensor while located at the first frequently visited location; and means for calibrating the barometric pressure sensor based, at least in part, on the stored first indication of the altitude of the mobile device and on the second pressure measurement.

[0012] It should be understood that the aforementioned implementations are merely example implementations, and that claimed subject matter is not necessarily limited to any particular aspect of these example implementations.

BRIEF DESCRIPTION OF DRAWINGS

[0013] Non-limiting and non-exhaustive aspects are described with reference to the following figures, wherein like reference numerals refer to like parts throughout the various figures unless otherwise specified.

[0014] FIG. 1 is a schematic block diagram illustrating an arrangement of representative electronic devices including a mobile device comprising an apparatus for opportunistically calibrating a barometer onboard the mobile device, in accordance with an example implementation.

[0015] FIG. 2 is an illustrative diagram representing certain example structural and natural features of an environment wherein a mobile device, for example, as in FIG. 1 , may be transported about by a person, and wherein in certain instances a barometer onboard the mobile device may be opportunistically calibrated, in accordance with certain example

implementations.

[0016] FIG. 3A and FIG. 3B are flow diagrams illustrating some example processes that may be implemented using a mobile device, for example, as in FIG. 1 , to opportunistically calibrate a barometer onboard the mobile device, in accordance with certain example implementations.

[0017] FIG. 3C is an illustrative diagram showing certain features of the interior of a multistory building according to an embodiment.

[0018] FIG. 3D is a flow diagram of a process to calibrate measurements obtained at an altimeter of a mobile device according to an embodiment.

[0019] FIG. 3E is a flow diagram of a process to calibrate measurements obtained at an altimeter of a mobile device according to an alternative implementation.

[0020] FIG. 3F is a flow diagram of a process for obtaining measurements of altitudes for discrete vertical levels, according to an embodiment.

[0021] FIG. 3G is a flow diagram of a process that may be used for calibrating a barometric pressure sensor, according to an embodiment.

[0022] FIG. 4 is a flow diagram of a process that may be used for calibrating a barometric pressure sensor according to an alternative embodiment.

[0023] FIG. 5 is a schematic diagram illustrating certain features of an example special purpose computing platform that may be provisioned within a mobile device, for example, as in FIG. 1 , and which may benefit from the techniques for opportunistic barometer calibration, for example, as in FIGs. 3A, 3B, 3D, 3E, 3F, 3G and 4 in accordance with certain example implementations. DETAILED DESCRIPTION

[0024] Various techniques are described herein which may be implemented in a mobile device to initiate one or more calibration processes corresponding to a barometer onboard a mobile device under certain circumstances/conditions. As mentioned, it may be useful to calibrate a barometer onboard a mobile device from time to time since atmospheric pressure often changes with over time due to various weather-related phenomena. Further, in certain instances, it may be useful for a mobile device to determine a reference atmospheric pressure corresponding to a particular altitude. For example, with knowledge of such a reference atmospheric pressure and corresponding altitude, it may be possible to estimate an altitude of the barometer (and hence, mobile device) by accounting for the known relationship between altitude and atmospheric pressure.

[0025] In certain instances, a mobile device may be able to obtain an applicable reference atmospheric pressure for a particular altitude (e.g., via one or more messages from a network resource, a local weather service computer, etc.). However, in certain instances a mobile device may be unable to obtain such information. For example, a mobile device may be unable at times to send/receive messages. Furthermore, in certain instances, a process to obtain such information from time to time may consume precious resources (e.g., processing resources at the mobile device and/or other devices, communication bandwidth, power supply resources, memory resources, etc.). For these or other reasons, it may be useful for a mobile device to be able to perform one or more calibration processes, for example, to identify a reference atmospheric pressure value for a particular altitude.

[0026] As described herein, certain techniques may be implemented in a manner that allows for calibration of a barometer onboard a mobile device at certain times, possibly more "opportunistic" times. For example, there may be times when a calibration of a barometer may be less desirable and hence more likely to fail or include too much uncertainty. One example is that calibrating a barometer while the mobile device is carried by a person riding in a moving elevator may be wasteful of resources. In another example, it may be wasteful of resources to perform a barometer calibration process without being able to estimate a likely current altitude (a discernable altitude level) of a mobile device.

[0027] However, as described herein, some detectable motions or types of motions (motion modes) of a mobile device may actually be indicative, at least in part, of a potential opportunity to initiate one or more barometer calibration processes. For example, there may be certain types of motion of a mobile device that may support an inference that the mobile device may be located at a discernable altitude level for an adequate period of time during which there may exist an opportunity to perform one or more barometer calibration processes. For example, it may prove beneficial to initiate a barometer calibration process in response to an estimation that a mobile device may be located at a discernible altitude level. By way of some initial non-limiting examples, there may be an opportunity to initiate a barometer calibration process while a person may be walking along a sidewalk of a portion of a street that may be at a discernable (ground) level within a city, or perhaps riding in a car, bus or train on a roadway or railway at a discernable (ground) level, or perhaps at an elevated level (e.g., a bridge, an highway, etc.), or conversely at a lowered level (e.g., a tunnel, an underpass, etc.). Of course, it may be useful for such motion to occur or remain within a discernible altitude level during the calibration process(es).

[0028] Several techniques are provided by way of various examples herein that may be used to estimate, at least in part, whether a mobile device may be, or have been, in a qualifying motion at a discernable altitude level to possibly trigger (initiate) one or more barometer calibration processes. It should be understood, however, that the examples provided herein are not necessarily intended to limit claimed subject matter. Moreover, it should also be understood that there may be a variety of different known barometer calibration processes that may be performed and that claimed subject matter is not intended to necessarily be limited to any particular process. Indeed, since such processes are well known and may be particular to a given manufacture of barometer or type of barometer, no specific barometer calibration process will be described herein. As may be appreciated, however, an example barometer calibration process may provide a measured atmospheric pressure serving as, or otherwise support calculation of, a reference atmospheric pressure for a discernible altitude level.

[0029] With this in mind, in certain example implementations it may be estimated that a mobile device may be in a qualifying motion at a discernible altitude level based, at least in part, on one or more signals obtained from one or more sensors onboard the mobile device. Such sensor(s) may comprise, for example, one or more environmental sensors, such as, for example, a barometer, a magnetometer, a light sensor, a sound sensor, a thermometer, a proximity sensor, and/or the like or some combination thereof. Such sensor(s) may comprise, for example, one or more inertial sensors, such as, for example, an accelerometer, a gyroscope, and/or the like or some combination thereof.

[0030] In another implementation, a mobile device may determine that the mobile device at a discernable altitude based, at least in part, on an inference that the mobile device is located at a particular frequently visited location such as a room in a house, office in a commercial building, place of worship, grocery store, gym, just to provide a few examples.

[0031] Additionally, in certain example implementations, it may be estimated that a mobile device may be in a qualifying motion at a discernible altitude level based, at least in part, on an electronic map indicative of a local terrain (e.g., indicative of various altitudes, elevations, a topography, etc.). For example, an electronic map may be indicative of altitude(s) of a ground level of a local terrain, e.g., a street level, sidewalk level, etc. For example, an electronic map may be indicative of an altitude of a raised roadway or railway, or conversely a tunnel. For example, an electronic map may be indicative of a suspended pedestrian bridge or walkway between certain buildings/structures, possibly along with other information that may be useful in navigating between and/or within such building(s)/structure(s).

[0032] It should be noted that as used herein the term "altitude" may comprise a traditional altitude measurement, e.g. , relating to a distance from a reference point/level such as a mean sea level, an Earth-centered coordinate system, etc. , and may also or alternatively comprise other types of distance measurements such as a height, an elevation, an offset, etc., that may be relatable to or otherwise correspond to an altitude. Accordingly, as used herein, the phrase "altitude level" may be considered to represent a likely particular "altitude" (e.g. , a given distance above sea level, a specific distance from the center of Earth, etc.), a likely range of altitudes (e.g., between two given distances from a reference point, or a particular altitude plus or minus some potential error distance (a measure of uncertainty in this example)), a

quantifiable level of a structure (e.g., a floor level of a building, a deck of a bridge, etc.).

[0033] As mentioned, in response to an estimation that a mobile device is located at a discernible altitude level (e.g. , a ground level, a bridge level, a tunnel level, a floor level, a particular altitude, etc.), one or more calibration processes corresponding to a barometer onboard the mobile device may be opportunistically initiated to identify a reference atmospheric pressure for the discernible altitude level. In one particular implementation, a mobile device may be determined to be located at a particular discernable altitude if the mobile device is determined to be in a particular qualifying motion, for example.

[0034] In certain example implementations, an estimation that a mobile device may be in a qualifying motion at a discernible altitude level may be based, at least in part, on an estimation that a trajectory of the mobile device is "level". For example, an estimation that a trajectory of the mobile device is level may be based, at least in part, on a comparison of signals and/or

measurements obtained from one or more of the sensors onboard the mobile device, and/or possibly with comparison to one or more applicable level trajectory threshold values. For example, a trajectory of a mobile device may be deemed level if a measured barometric pressure does not change more than some applicable level trajectory threshold amount over a period of time or at different times. For example, a trajectory of a mobile device may be deemed level if certain inertial sensor measurements remain below some applicable level trajectory threshold levels. For example, such one or more inertial sensors may indicate vertical motion of the mobile device in a direction of a gravity vector, the absence of which or less than some threshold level of which may support an inference of a level trajectory. Of course, these are just a few examples.

[0035] In certain example implementations, a trajectory of a mobile device may be estimated to be level based, at least in part, on an estimated velocity of the mobile device, and/or an estimated mode of transportation. For example, a trajectory may be level for a period of time while a person carrying the mobile device is walking, running, riding in a vehicle, etc., which may correspond to an estimated velocity and/or mode of transportation. Here, it may be further useful to consider applicable routes of travel, etc., as indicated may be indicated in an electronic map, along with information from a pedometer, a vehicle

speedometer, or other like known function depending on the mode of transportation.

[0036] In certain example implementations, a mobile device may be estimated as in motion at a discernible altitude level, based, at least in part, on an estimated movement routine corresponding to the mobile device. Here, for example, a person carrying the mobile device may follow certain routines with regard to their movements. For example, a movement routine may comprise a period of commuting between a place of work and a home during certain times of a day on certain days of a week. Accordingly, during such movement routines, a person may be traveling in according to some more of transportation that may correspond to a level trajectory at times. In another example, a movement routine may be recognized or identified based on a history and/or a schedule that may be identified as corresponding to the mobile device and/or person carrying the mobile device. For example, a person may walk along a sidewalk, ride a train, etc. , to attend a lunch meeting, a doctor appointment, a golf tee-time, and/or the like, possibly according to common pattern or routine, and/or some schedule (e.g., possibly identifiable, at least in part, via a text message, a voice message, an electronic mail message, a calendar event, a timer, etc.).

[0037] In certain example implementations, a mobile device may be determined to be in a qualifying motion at a discernible altitude level, based, at least in part, on one or more wireless signals acquired from one or more transmitting devices. For example, motion of a mobile device may be indicated via various changes in a wireless signal from a terrestrial-based transmitting device that is not itself moving, e.g., there may be increase or decrease a received signal strength measurement as the mobile device moves closer or farther from a transmitting device, there may be frequency Doppler affect as the mobile device moves closer or farther from such a transmitting device, there may be a loss of signal, there may be a new signal, there may be a handoff of a mobile device from one serving transmitting device to another, etc., just to name a few examples.

[0038] Furthermore, in certain instances, an acquired signal may be indicative, at least in part, of a possible discernible altitude level. For example, some transmitting devices may be arranged to provide service to mobile devices within a particular portion of a building or structure, or possibly an outdoor space, which may be indicative of one or more discernible altitude levels. Indeed, in certain instances, a wireless signal of a transmitting device may indicate a certain location that may be indicative of one or more discernible altitude levels. For example, a wireless local area network or hotspot on a train may indicate via its signal that it may correspond to a discernible altitude level. In certain instances, one or more satellite positioning system (SPS) signals may be acquired by a mobile device, which may be used, at least in part, to determine an altitude level, and/or a possible direction of travel for the mobile device.

[0039] In another example, a mobile device may be paired with a computing device onboard an automobile (e.g., via Bluetooth, or other like communication capability), which may be indicative of a mode of transportation, and/or possibly lead to sharing of other information corresponding to the vehicle or its motion, such as, for example, location information, speed/velocity, heading, pitch, yaw, tilt, etc.

[0040] In certain example implementations, one or more barometer calibration processes may be selectively initiated based, at least in part, on a time-based threshold value. For example, it may be useful to initiate a barometer calibration process after a certain period of time corresponding to a time-based threshold value has passed since a last barometer calibration process. Conversely, it may be useful to not initiate a barometer calibration process until a certain period of time corresponding to a time-based threshold value has passed since a last barometer calibration process.

[0041] In certain example implementations, it may be useful for a mobile device to further identify an altitude uncertainty value corresponding to a discernible altitude level, and/or a reference pressure uncertainty value corresponding to reference atmospheric pressure. Such uncertainty values may, for example, be useful in other functions within the mobile device and/or possibly in other devices that may make use of the barometer onboard the mobile device. Similarly, an estimated altitude obtained from barometric pressure measurements may be associated with an estimated error in the estimated altitude.

[0042] In certain example implementations, it may be useful for a mobile device to obtain a weather report from another device and to affect an estimation of motion at a discernible altitude level based, at least in part, on the weather report. For example, in certain instances a forecasted rapid change in atmospheric pressure due to a storm front may indicate that, for a period of time, measurements from the barometer onboard the mobile device may be suspect, or that an operative mode of the barometer may be adjusted in some manner (e.g. , increase samples, decrease samples), or possibly that more or fewer or different barometer calibration processes may be desirable, or the barometer-based altitude readings given more or less weight, just to name a few examples.

[0043] In certain example implementations, it may be useful for a mobile device to transmit one or more messages to one or more other devices which are indicative of a discernible altitude level and a reference atmospheric pressure. Thus, for example, a plurality of mobile devices may report such information and/or the like to a crowd sourcing server, a research service, etc., that may further process, refine, share, study, record, and/or otherwise use the information in some manner. [0044] In certain example implementations, a mobile device may maintain a calibration history corresponding to a plurality of completed barometer calibration processes. For example, a calibration history may be indicative of a plurality of estimated discernible altitude levels and corresponding identified reference atmospheric pressures. For example, a calibration history may be indicative of various factors that may have been considered and/or otherwise used by the applicable techniques provided herein. In another example, a calibration history may be indicative of a learned routine, pattern, habit, schedule, etc., that may be of use to certain techniques as provided herein.

[0045] In another embodiment, in response to a determination that an estimated error of an estimate of an altitude of a mobile device is lower than a threshold value, the mobile device may perform a first operation to calibrate a barometric pressure sensor of the mobile device. The mobile device may then determine that the mobile device is located at one or more frequently visited locations. The mobile device may then store measurements of altitude at the determined one or more frequently visited locations based, at least in part, on one or more altitude measurements obtained by the barometric pressure sensor while the barometric pressure sensor is still in a calibrated state. The mobile device may then perform a second operation to calibrate the barometric pressure sensor in response to a determination that the mobile device has returned to at least one of the one or more frequently visited locations based, at least in part, on the stored measurements and a pressure measurement obtained by the barometric pressure sensor at the at least one of the one or more frequently visited locations. [0046] Attention is now drawn to FIG. 1 , which is a schematic block diagram illustrating an example arrangement 100 comprising various example electronic devices within an environment 102. Environment 102 may comprise an outdoor space, one or more indoor spaces, and/or some combination thereof, in which a mobile device 104 may be located and moved about.

[0047] Mobile device 104 may be representative of any electronic device capable of being moved (carried and transported) in some manner by a person within environment 102. Hence, by way of example, mobile device 104 may comprise a cellular telephone, a smart phone, a tablet computer, a laptop computer, a wearable computer, a navigation and/or tracking device, etc. As illustrated, mobile device 104 may comprise an apparatus 106, which may be configured to provide and/or support in some manner one or more of the techniques provided herein. In certain instances, apparatus 106 may comprise hardware/firmware components, or possibly a combination of

hardware/firmware and software components.

[0048] Accordingly, at times mobile device 104 may be capable of acquiring wireless signals 109 from one or more terrestrial-based transmitting devices 108, and/or wireless signals 1 1 1 from network(s) 1 10. Transmitting device 108 and/or network(s) 1 10 may be representative of various types of devices, including by way of some examples, a cellular base station, a repeater device, a fempto or pico cell device, a wireless local area network access device, a location beacon transmitting device, etc.

[0049] As illustrated in FIG. 1 , mobile device 104, transmitting device 108 and network(s) 1 10 may, for example, communicate via wireless communication links 105, 109 and 1 1 1. Further, as illustrated network(s) 1 10 may be further connected over communication link 1 13 to one or more other devices 1 12. While communication link 1 13 is illustrated as comprising wired communication links, it should be understood that in certain instances communication link 113 may comprise various wired and/or wireless communication links.

[0050] Network(s) 1 10 is intended to represent all or part of one or more other electronic devices and/or communication facilities and/or resources capable of supporting wired and/or wireless electronic communication. Thus for example, network(s) 1 10 may comprise all or part of a telephone network, a cellular telephone network, a wireless communication network, transceivers in a local or indoor environment (e.g., wireless local area network or personal area network), an intranet, the Internet, and/or the like or some combination thereof.

[0051] Further, as shown in FIG. 1 , mobile device 104 may, at times, acquire one or more SPS signals 134 transmitted by one or more space vehicles (SVs) 132 of one or more SPS systems 130.

[0052] Example arrangement 100 also comprises a reference

barometer/pressure sensors 1 16 and 1 17 that may provide reference pressure measurements to other devices on network(s) 1 10 via wireless links 1 18. Here, reference barometer/pressure sensor 1 16 may be located at a known altitude and in sufficient proximity to mobile device 104 to experience or be affected by the same or similar weather conditions. In a particular implementation, reference barometer/pressure sensor 1 16 may be located at an airport or may be integrated with a BTS/cell tower (e.g., a BTS/cell tower serving mobile device 116).

[0053] In a particular alternative implementation, a separate pressure reference server 1 15 may keep track of various pressure reference values and be capable of providing mobile device 104 with a closest reference pressure value at known altitude, or providing an almanac of such preference reference values allowing mobile device 104 to seek out the closest pressure reference value. For example, mobile device 104 may transmit one or more messages to pressure reference server 1 15 including indicators or parameters indicating a location of mobile device 104. Such indicators or parameters may include, for example, latitude and longitude, a cell identifier for a serving cell, MAC address of a serving WLAN access point, postal code, and street address, just to provide a few examples.

[0054] In response to the one or more messages from mobile device 104, pressure reference server 1 15 may provide a response message to mobile device 104 including a reference pressure and an altitude at which the reference pressure was obtained (e.g., altitude or reference barometer/pressure sensor 1 16 or 1 17), or it may provide a pressure referenced to mean sea level, or some other reference altitude. For example, the response message may identify a reference pressure source (e.g., reference barometer/pressure sensors 116 and 1 17) that is closest to a location of mobile device 104. From this reference pressure and altitude in a response message, a current altitude of mobile device 104 and current measurement from an on-board altimeter, mobile device 104 may calibrate the on-board altimeter.

[0055] In an alternative implementation, separate pressure reference server 115 or other source may also provide an altitude terrain map enabling mobile device 104 to determine an altitude ground level for its present estimated location. For example, mobile device may apply coordinates of its location (e.g., latitude and longitude or street address) to the altitude terrain map to determine a corresponding altitude for this location (e.g., using well known interpolation techniques). Alternatively, as mentioned elsewhere herein, mobile device 104 may determine its altitude from an SPS fix. Also, mobile device 104 may determine its altitude based, at least in part, on an inference that the mobile device is located at a particular frequently visited location.

[0056] In this context an "altitude terrain map" may include any expression (e.g., such as in electronic form and/or stored in a memory) that relates a horizontal location to a corresponding altitude. In this context, a "horizontal location" means attributes of a location irrespective of an altitude component. For example, a horizontal location may comprise a location in a plane or expressed by coordinates such as latitude and longitude, street address, landmark indication, cell ID, etc., irrespective of an altitude component. It should be understood, however, that these are merely examples of parameters descriptive of horizontal location and claimed subject matter is not limited in this respect. Also, an "estimated horizontal location" may comprise estimated parameters descriptive of a horizontal location. For example, an altitude terrain map may be expressed as one or more arrays in electronic form and/or as metadata provided with or a part of an electronic map. In a particular implementation, values in an altitude terrain map may define an altitude relative to a reference altitude (e.g., sea level) at a "ground level" indicative of an altitude of a terrain surface. In one particular implementation, an altitude terrain map may comprise metadata that is indicative of a plurality of discrete vertical levels that may be navigated in a particular horizontal region such as discrete floors of a building over a building footprint over a terrain. In one

implementation, based on an altitude terrain map a special purpose computing apparatus, such as a processor in a mobile device, may be capable of determining or estimating an altitude of such a ground level at a corresponding horizontal location using well known interpolation techniques, for example.

[0057] According to an embodiment, a terrain surface at a ground level may comprise portions of an area are natural or graded portions including, for example, portions that are not enclosed by a structure. A ground level may also comprise the surface of a natural body of water such as a river or a lake. A ground level may also be indicative of an altitude of terrain on which a structure or building is supported. In a particular example, a ground level at the entrance of a building may be at about the same altitude as a lobby floor, for example. Here, other floors above or below the lobby floor may be above or below a ground level of the terrain.

[0058] According to an embodiment, mobile device 104 may apply a conversion to a pressure reference value obtained from reference

barometer/sensor if mobile device 104 and reference barometer/sensor are located at different altitudes (e.g. , where atmospheric pressure decreases as altitude increases). For example, mobile device 104 may estimate a pressure drift ΔΡ dnft to calibrate subsequent measurements obtained from its on-board altimeter according to expression (1 ) as follows:

APdrift = Ph - Poe- ^m 9 ^h/kT - ΔΡ weather ( 1 )

Where

P _h is the pressure measured at point h (e.g. , altitude of a mobile device); Po is the pressure at reference point 0 (e.g., as provided in a message from a barometric pressure reference sever); e is Euler's constant; m is the mass per air molecule; g is acceleration due to gravity; h is a height difference from reference point 0 (e.g., a difference between an altitude at which P ₀ is measured and an altitude of a mobile device as determined from a terrain map); k is the Boltzmann constant;

T is temperature at the mobile device in Kelvin; and

APweather is the pressure change due to differences in weather between a location of the mobile device and a location of a sensor measuring P ₀ .

[0059] If Po is obtained from a source that is very near to the location of the mobile device, may be APweather negligible and possibly ignored without substantially affecting calibration of a barometric pressure sensor. A mobile device may apply APdnft computed according to expression (1) to calibrate subsequent pressure measurements obtained from a barometric pressure sensor used for estimating an altitude of the mobile device. It should be understood that expression (1 ) provides merely an example of how a value of a pressure drift, and claimed subject matter is not limited in this respect.

[0060] Attention is drawn next to FIG. 2, which is an illustrative diagram representing certain example structural and natural features of an urban environment 200 wherein a mobile device, for example, as in FIG. 1 , may be transported about by a person, and wherein in certain instances a barometer onboard the mobile device may be opportunistically calibrated, in accordance with certain example implementations. As shown, different example altitude levels may be associated with such features.

[0061] As illustrated in FIG. 2, example environment 200 includes a side/cross-sectional view of cityscape having a ground level 202 from which multiple-floor buildings 204, 206 and 208 rise above. Ground level 202 may, for example, support a qualifying motion of person carrying mobile device 104 (FIG. 1). For example, such a person may walk or run (in pedestrian motion), or otherwise be transported may some vehicle or other form of conveyance operating at or about ground level 202.

[0062] In building 204, a higher floor 205 is indicated. Here, for example, in certain instances higher floor 205 may correspond to a work location for a person at certain times. Higher floor 205 may, for example, support a qualifying (pedestrian) motion of person carrying mobile device 104.

[0063] In building 208, a portion 209 of a mid-level floor is indicated. Here, for example, in certain instances portion 209 may correspond to a home location for a person. Portion 209 may, for example, support a qualifying

(pedestrian) motion of person carrying mobile device 104 (FIG. 1 ).

[0064] A suspended bridge 207 is shown as connecting buildings 206 and 208 at an altitude level that is higher than ground level 202. Bridge 207 may, for example, support a qualifying (pedestrian) motion of person carrying mobile device 104. [0065] A raised portion 210 is also shown at an altitude level that is higher than ground level 202. Raised portion 207 may, for example, support a qualifying motion of person carrying mobile device 104. For example, a person may walk along an elevated pathway or bridge, or may be carried by some mechanism along an elevated roadway or railway, etc., as represented by raised portion 207.

[0066] A lowered portion 212 is also shown at an altitude level that is lower than ground level 202. Lowered portion 212 may, for example, support a qualifying motion of person carrying mobile device 104. For example, a person may walk along a below-ground trench or tunnel, or may be carried by some mechanism along an underground roadway or railway, etc., as represented by lowered portion 212.

[0067] As shown in FIG. 2, in certain instances, ground level 202 may itself be offset by some distance 215 from some other reference level and/or point represented by item 214. By way of example, item 214 may represent a mean sea level, a center point of an Earth centered coordinate system, as are well known. By way further reference, a three axis coordinate system that may be applied is indicated by item 220, showing an x-axis, a y-axis and a z-axis, that may have its origin at Earth center. Thus, in such example coordinate system, different altitude levels increase/decrease along the z-axis. Similarly, as known, a gravity vector may be detected by certain inertial sensors which may similarly be aligned with the z-axis.

[0068] As pointed out above, a mobile device may calibrate an on-board altimeter based on a reference pressure and an altitude at which the reference pressure was obtained (e.g. , from a server), the mobile device's current altitude and a current reading from the on-board altimeter. Also as pointed out above, a mobile device may apply coordinates of its location to an altitude terrain map to estimate or determine its altitude under certain conditions such as the mobile device being located a ground level such that its altitude at a particular location matches an altitude in the altitude terrain map corresponding to a current location of the mobile device. This may not be the case, however, if the mobile device is located in a multistory building above ground or on some other structure above ground as defined in the altitude terrain map. As discussed below in particular implementations, a mobile device may infer its altitude relative to a ground level as defined in an altitude terrain map based, at least in part, on motion attributes.

[0069] Attention is drawn next to FIG. 3A, which is a flow diagram illustrating an example process 300 that may be implemented using a mobile device to opportunistically calibrate a barometer onboard the mobile device. By way of example, process 300 may be implemented in whole or in part by mobile device 104 and/or apparatus 106 provisioned therein (FIG. 1 ). At block 301 , a mobile device may determine that it is located on a ground level in an outdoor environment based on any one of several observations. In one implementation, signals from an onboard sensor (e.g. , SPS receiver, light sensor, camera, temperature sensor or vibrational sensor, or any combination thereof). For example, a mobile device may determine that it is located on a ground level and in an outdoor environment based, at least in part, on a GNSS position fix based on acquisition of SPS signals. In another example, as discussed above, a mobile device may infer that it is in an outdoor environment if it is detected that the mobile device is in a qualifying motion reflective of a location on a ground level and in an outdoor environment.

[0070] In another example, a mobile device may comprise an almanac indicating horizontal locations and displacement of local buildings and subterranean structures (e.g. , subways). Here, if an estimate of a horizontal location is determined to be located where no buildings or subterranean structures are present, a mobile device may infer that the mobile device is located on a ground level and an outdoor area.

[0071] In another example, a mobile device may be determined to be located on a ground level and in an outdoor area based, at least in part, on a history of movements (e.g., as detected based on signals generated by one or more inertial sensors onboard the mobile device) suggestive of travelling over a particular outdoor contour (e.g., matching a particular portion of an electronic terrain map).

[0072] A mobile device may determine that it is located in an outdoor environment and at a ground level based, at least in part, on one or more signals obtained from one or more sensors onboard the mobile device, an electronic map indicative of a local terrain, or some combination thereof. As mentioned, certain detectable motions of a mobile device may qualify as providing an opportunity to perform a barometer calibration, given a discernible altitude level being identified. For example, an estimated level trajectory may support an inference of a qualifying motion. For example, an estimated motion mode or mode of transportation may be indicative of a qualifying motion. [0073] In an example scenario, a motion speed of a mobile device may be sufficiently high and sustained to infer that the mobile device is not constrained within a building or other indoor environment. For example, from a sufficiently high and sustained speed of a mobile device it may be inferred that the mobile device is travelling in an automobile on a road at a discernable "ground level." In a particular example implementation, a latitude and longitude of the mobile device may be known roughly (e.g., from terrestrial positioning techniques such as Advanced Forward Trilateration (AFLT) or cell ID of a serving cell). If it is inferred that the mobile device is on a non-indoor ground level (e.g. , based on a sufficiently high and sustained speed), an altitude of the mobile device may be estimated from an altitude terrain map by referencing the latitude and longitude to the map.

[0074] At block 302, a mobile device may determine that it is located at a discernable altitude with sufficient accuracy and precision to reliably calibrate a barometric pressure sensor. As discussed below at example block 304, this estimated altitude may then be used in a process to calibrate a barometric pressure sensor or altimeter on the mobile device (e.g. , by computing APdrm according to expression (1)). In one implementation, a mobile device may determine that it is located at a discernable altitude based, at least in part, on a reliable GNSS position fix that provides an altitude component.

[0075] In other example implementations, different types of motion may be used to infer an altitude of a mobile device. For example, if it is known that a mobile device is close to a body of water and a motion speed of the mobile device is similar to that of a boat travelling on the top surface of the body of water, it may be inferred that the altitude of the mobile device is that of the body of water. In another example, if it is known that a mobile device is close to a train track and a motion speed of the mobile device is similar to that of a train travelling on the train track, it may be inferred that the altitude of the mobile device is that of a train travelling on the train tracks. It should be understood, however, that these are merely examples of how it may be determined that a mobile device is at a discernable level based on motion, and claimed subject matter is not limited in this respect.

[0076] At example block 304, in response to determination that the mobile device is located at a discernible altitude level, one or more calibration processes corresponding to a barometer onboard the mobile device may be initiated, for example, to identify a reference atmospheric pressure for the discernible altitude level. As may be appreciated, such a reference atmospheric pressure may subsequently be used for a period of time to estimate an altitude level based on further atmospheric pressure measurement(s). For example, a difference between a subsequent atmospheric pressure measurement and such reference atmospheric pressure may indicate that the mobile device may be located on a particular floor or level of a building.

[0077] Attention is drawn next to FIG. 3B, which is a flow diagram illustrating an example process 300' that may be implemented using a mobile device to opportunistically calibrate a barometer onboard the mobile device. By way of example, process 300' may be implemented in whole or in part by mobile device 104 and/or apparatus 106 provisioned therein. In comparison with process 300 of FIG. 3A, example process 300' comprises additional example blocks 306, 308 and 310 that may, in certain instances, be performed as part of example block 302', additional example blocks 318 and 320 that may, in certain instances, be performed as part of example block 304', and/or additional example blocks 322 and/or 324 that may, in certain instances, be performed in addition to example blocks 302, 302', 304, and/or 304'.

[0078] At example block 302 ', a mobile device may estimate that it is located at a discernible altitude level based, at least in part, on one or more signals obtained from one or more sensors onboard the mobile device, an electronic map indicative of a local terrain, or some combination thereof .

[0079] In the particular embodiment illustrated in FIG. 3B, block 302' may be executed by multiple actions shown at blocks 306, 308 and 310. Block 306 may comprise obtaining estimates of latitude and longitude of a location of a mobile device, and estimated errors in these estimates. This may be obtained from one or more signals obtained from a sensor onboard the mobile device such as, for example, an SPS receiver, accelerometers, gravitometers, gyroscopes, microphones, WLAN transceiver, WWAN transceiver, WPAN transceiver, just to provide a few examples. Block 308 may apply an electronic terrain map (e.g. , stored locally in a memory) to the estimated horizontal location and estimated error in that estimate to provide an estimated altitude and an estimated error in that altitude estimate (e.g., using well known interpolation techniques as discussed above). At block 310, if the estimated error in the altitude estimate is less than a threshold value, the discernable altitude may be determined to be the estimated altitude.

[0080] At example block 304', in response to an estimation that the mobile device is located at the discernible altitude level, one or more calibration processes corresponding to a barometer onboard the mobile device may be initiated, for example, to identify a reference atmospheric pressure for the discernible altitude level.

[0081] As previously mentioned and now shown at example block 318, a mobile device may obtain one or more current barometric pressure

measurements from an onboard barometric pressure sensor. The one or more current barometric pressure measurements obtained at block 318 may be obtained contemporaneously with measurements for determining the estimated horizontal location at block 306 or estimated altitude at block 308. Block 320 may then associate the one or more current barometric pressure measurements obtained at block 318 with the discernable altitude determined at block 310. The barometric pressure sensor obtaining the one or more barometric pressure measurements at block 318 may then be calibrated according to expression (1) above to, for example, compute a value for APdnft for use in calibrating future barometric pressure measurements form the barometric pressure sensor by, for example, adjusting the future barometric pressure measurements by an amount based on APdnft.

[0082] In certain example implementations, process 300' may, at example block 322, comprise having the mobile device transmit one or more messages to one or more other devices, and such messages may indicate, at least in part, a discernible altitude level and corresponding reference atmospheric pressure, or it may provide a reference pressure, relative to an agreed standard altitude, such as mean sea level.

[0083] In certain example implementations, process 300' may, at example block 324, comprise maintaining a calibration history. For example, a calibration history may correspond to one or more completed barometer calibration processes and may be indicative of one or more estimated discernible altitude levels and corresponding identified reference atmospheric pressures.

[0084] In particular scenarios, a mobile device may not be able to discern an altitude of its location with sufficient reliability or accuracy for calibration of an onboard barometric pressure sensor. For example, an estimated error in an estimated altitude determined at block 308 may exceed a threshold value at block 310, indicating that the estimated altitude is not sufficiently reliable or accurate. Nevertheless, in particular implementations, a mobile device may still be capable of correcting for weather effects. As pointed out above in

connection with FIG. 1 , reference pressure server 1 15 may store a history of reference barometric pressure measurements obtained by reference barometric pressure sensors 1 16 and 1 17. This stored history of barometric pressure measurements may be used to calibrate measurements obtained at a current time ti from an onboard barometric pressure sensor for changes in weather according to expression (2) as follows:

APweather(tl) = Pref(tl) - Pref(to) (2) where:

Pref(ti) is a reference pressure value obtained at a current time h at a reference point (e.g. , at a location of a reference barometric pressure sensor);

Pref(to) is a reference pressure value obtained at a time in the past to (e.g., at a time when an onboard barometric pressure sensor was previously calibrated). [0085] According to an embodiment, a mobile device may calibrate an onboard barometric pressure sensor according to expression (2) to correct for changes in weather from a time to, when the mobile device was previously calibrated, to a time U. In one particular implementation, a mobile device may obtain a value for Pmf(to) from a reference pressure server at some time in the past, and then store the obtained value for Pmf(to) in an onboard memory device. For example, the mobile device may have used the obtained value for P f(to) in a previous calibration operation. Alternatively, the mobile device may transmit a query message to a reference pressure server (e.g. , reference pressure server 1 15) requesting a pressure reference value for a particular reference barometer/pressure sensor obtained at time to.

[0086] A mobile device may reliably calibrate an onboard barometric pressure sensor based on a value for Pmf(to) (e.g., using expression (1 ) above) if the mobile device at time to is sufficiently proximate to a location of a reference sensor obtaining value Pmf(to) to avoid significant variation in weather between the location of the reference sensor and a location of the mobile at time to. Similarly, the mobile device may reliably calibrate the onboard barometric pressure sensor at time h if the mobile device at time h is also sufficiently proximate to the reference sensor obtaining value Pmf(ti) to avoid significant variation in weather between the location of the reference sensor and a location of the mobile at time h.

[0087] In particular environments, such as indoor environments, a mobile device may not be capable of acquiring SPS signals that are sufficiently accurate to estimate its location with a threshold for horizontal or vertical accuracy. In particular environments, a mobile device in a multilevel indoor environment (e.g., a multistory building) may be inferred to be located on one of a number of discrete vertical levels (e.g., different floors of a building on which a mobile device may be located). The mobile device may then from time to time calibrate its altimeter to correct for measurement drift. For example, if a mobile device is located on a particular floor of a building, it may be desirable to perform a calibration operation sufficiently often to avoid a drift of more than one half an altitude separation between the particular floor and an adjacent floor. As such, particular example implementations are directed to determining a duration (e.g., a maximum duration) between consecutive calibration operations.

[0088] As pointed out above, a mobile device may calibrate an on-board altimeter based on a reference pressure and an altitude at which the reference pressure was obtained or referenced to (e.g., obtained from reference pressure server 1 15), the mobile device's current altitude and a current measurement reading from the on-board altimeter. Also as pointed out above, in particular environments where a mobile device may not reliably obtain a GNSS position fix (e.g., in indoor environments), the mobile device may employ different means for obtaining its current altitude. As pointed out above, by periodically calibrating an altimeter according to an estimated measurement drift of an altimeter, a mobile device in a building with discrete vertical levels may be able to maintain calibration of measurements from the altimeter to support positioning operations.

[0089] FIG. 3C shows floors 303 and 305 of a multistory building according to embodiment. Floor 303 may comprise a floor at a known or verifiable altitude (e.g., a lobby floor) while floors 305 are on levels set off vertically from floor 303. FIG. 3C shows that floors 305 are above (i.e. , have a higher altitude than) floor 303. In other embodiments however, one or more floors of a building may be below a lobby level. As shown in FIG. 3C, for the purposes of illustration, adjacent floors are separated by a uniform altitude separation d. In other scenarios, however, an altitude separation between adjacent floors need not be uniform. For example, a lobby of a building (e.g. , a hotel lobby) may be separated from a first floor (floor adjacently above the lobby floor) by a twelve- foot altitude separation while the first floor may be separated from a second floor (floor adjacently above the first floor) by a ten-foot altitude separation.

[0090] In the presently illustrated embodiment, a mobile device entering a building as depicted in FIG. 3C may enter floor 303 from an outdoor

environment where an altitude is known or reliably estimated by the mobile device from a GNSS position fix. If an altitude of the outdoor environment at the entrance to the lobby is roughly the same as that of floor 303, the mobile device may maintain an accurate estimate of an altitude of floor 303 in a memory (e.g., based on a last position fix before entering the building). In other scenarios, floor 303 need not be at a lobby level but instead comprise a floor leading to an outdoor area such as a terrace or balcony that is at about the same altitude as floor 303. In a particular implementation, following estimation of a current altitude based on a GNSS position fix in an outdoor environment and as the mobile device proceeds to floor 303, a mobile device may assess whether the estimated current altitude remains reliable based, at least in part on signals from inertial sensors which may indicate any vertical accelerations indicative of a change in altitude.

[0091] Based on a stored estimate of the altitude of floor 303, a mobile device may calibrate an on-board altimeter or barometric pressure sensor. For example, the mobile device may compute a measurement drift based on expression (1 ) based on the stored estimated altitude of floor 303, a raw measurement obtained while located on floor 303, and a reference pressure and corresponding reference altitude (e.g., obtained from reference pressure server 1 15). If the mobile device subsequently moves from floor 303 to a different floor (e.g., a floor 305), however, the stored estimated altitude of floor and raw measurement obtained while located on floor 303, by themselves, may not be sufficient for performing a subsequent calibration operation according to expression (1 ).

[0092] As may be observed from FIG. 3C, adjacent floors are separated by the same altitude separation d. According to an embodiment, a mobile device moving from floor 303 to a different floor may experience a change in altitude from that of floor 303 by an integer multiple of d. Here, an altitude of a mobile device moving from floor 303 to a different floor may be inferred to be located on one a plurality of discrete vertical levels set off in altitude from floor 303 by integer multiples of d.

[0093] Following an initial calibration of an on-board altimeter at floor 303 as discussed above, a mobile device may obtain a subsequent altitude

measurement from its on-board altimeter. An altitude of the mobile device may be inferred to be that of a particular discrete vertical level (from among the aforementioned plurality of discrete vertical levels) corresponding to (e.g., closest to) the subsequent altitude measurement. The mobile device may then calibrate its on-board altimeter according to expression (1 ) using the

subsequent altitude measurement (or corresponding barometric pressure measurement), the altitude of the particular discrete vertical level corresponding to the subsequent altitude measurement, and a reference pressure and corresponding reference altitude.

[0094] According to an embodiment, a mobile device performing an initial calibration of its altimeter while located at floor 303 may periodically perform subsequent calibration operations based on expression (1 ) thereafter. If the subsequent calibration operations are performed sufficiently often relative to an expected measurement drift rate for an on-board barometric pressure sensor obtaining the draft rate, a mobile device may maintain calibration indefinitely. In a particular implementation, it may be desirable or useful to recalibrate an altimeter before a drift of the altimeter (since the most recent calibration) operation exceeds one half an altitude separation between adjacent floors (e.g., d). For example, a permitted or maximum duration between consecutive executions of a calibration operation may be set according to expression (3) as follows:

T < d/{2xDR) (3) where:

7 ^~ is a duration between consecutive calibration operations; and

DR is an expected rate of drift of altimeter measurements.

[0095] FIG. 3D is a flow diagram of a process to calibrate an onboard barometric pressure sensor of a mobile device according to an embodiment. Block 352 may determine an expected measurement drift rate for a barometric pressure sensor using any one of several different techniques. Such an expected measurement drift rate may comprise a signal or a state value that is stored in a memory and represents an expected amount by which a deviation of measured barometric pressure or altitude from actual barometric pressure increases over time. Such a measurement drift rate may also be expressed in units of atm/sec or m/sec. In a particular implementation, block 352 may be performed, at least in part, by a computing device such as processing unit(s) 502 in combination with memory 504, for example. Block 354 may then determine a permitted (e.g. , maximum) duration between consecutive operations to calibrate the sensor based, at least in part, on the expected measurement drift rate of the barometric pressure sensor and an expected change in altitude between discrete vertical levels of the building the expected drift rate. In a particular implementation, a mobile device may periodically calibrate an on-board barometric pressure sensor and the duration determined at block 354 may specify a duration of a period between calibration operations. As such, the period for performing such a periodic calibration may be determined based, at least in part, on an expected measurement drift rate of the barometric pressure sensor and an expected change in altitude between discrete vertical levels of the building. An expected change in altitude may comprise a signal or state stored in a memory representing an expected altitude separation between adjacent floors of a building. The duration (e.g., period) may also comprise a signal or state stored in a memory representing a time period between consecutive operations to calibrate the barometric pressure sensor. In a particular implementation, blocks 352 and 354 may be performed, at least in part, by a computing device such as processing unit(s) 502 in combination with memory 504, to calibrate altimeter/barometric pressure sensor(s) 524, for example. [0096] FIG. 3E is a flow diagram of a process by which a mobile device may calibrate measurements of an on-board barometric pressure sensor or altimeter according to an alternative implementation. Block 362 may determine an expected drift rate of an altimeter or barometric pressure sensor using any one of several techniques. For example, block 362 may obtain an expected drift rate determined as a factory setting and stored in a memory. Alternatively, block 362 may evaluate a history of measurements obtained by the altimeter or barometric pressure sensor paired with actual/reference values of altitude or barometric pressure to characterize a rate at which measurements obtained by the altimeter or barometric pressure sensor deviate over time. It should be understood, however, that these are merely example techniques for determining an expected drift rate of a barometric pressure sensor, and claimed subject matter is not limited in this respect.

[0097] Block 364 may determine an altitude of a first or initial discrete vertical of a building. As discussed above, this may be accomplished by obtaining an GNSS position fix in an outdoor area at an entrance to the first or initial discrete vertical level (e.g., at the entrance to a lobby, or a balcony or terrace as discussed above). Alternatively, the altitude of a first or initial floor of a building may be provided through a different sensor (e.g., a bar code reading) or user input provided to a user interface (e.g., provided to a touchscreen).

[0098] Block 366 may perform an initial calibration operation based on the altitude of the first discrete vertical level determined at block 364. As discussed above, this may be accomplished by estimating a pressure drift according to expression (1 ) based, at least in part, the first discrete vertical level determined at block 364, a contemporaneous raw measurement obtained by the on-board altimeter, and a reference pressure and corresponding reference altitude at which the reference pressure was obtained.

[0099] Block 368 may determine an altitude separation between discrete vertical levels of a building (e.g. , d as shown in FIG. 3C). This may be provided to the mobile device as positioning assistance data provided by a server (e.g. , pressure reference sensor 1 15). Alternatively, an altitude separation between discrete vertical levels of a building may be provided as a user input to a user interface. Based, at least in part, on the altitude separation between discrete vertical levels of the building and the expected drift rate determined at block 362, block 368 may further compute a calibration period. For example, block 368 may compute a duration between consecutive calibration operations subject to a constraint in expression (3) discussed above.

[00100] In one particular embodiment, discrete vertical levels in a building may not be separated by a uniform altitude separation. Here, to compute a duration between consecutive calibration operations block 368 may determine a single value to represent an altitude separation between discrete vertical levels. Block 368 may determine an average separation or a minimum separation between adjacent discrete vertical levels for computation of a duration according to expression (3).

[00101] Following an initial wait based on the computed duration calibration period at block 370, block 372 may perform calibration operation. Here, block 372 may identify candidate altitudes as the altitude of the first discrete level determined at block 364 and additional altitudes set off from the first discrete level at the altitude separation between discrete vertical levels determined at block 368. The mobile device may obtain a current measurement of an altitude based on a pressure measurement obtained by the on-board altimeter or barometric pressure sensor (which is calibrated according to a pressure drift computed in a most recent calibration operation). Then, the mobile device may select a candidate altitude from among the candidate altitudes as being closest to the measured altitude. The mobile device may then compute an updated pressure drift value according to expression (1 ) based, at least in part, on the selected candidate altitude, the current measurement of altitude, and a reference pressure and corresponding reference altitude. The mobile device may then wait for the duration at block 370 before repeating a calibration operation at block 372. Accordingly, a mobile device may move about on different floors of a multi-story building and maintain calibration of its barometric pressure measurements provided that calibrated barometric pressure measurements are sufficiently accurate to correctly correlate with one of the candidate altitudes.

[00102] In one particular implementation, the duration computed at block 368 may specify a period for a periodic calibration of an on-board barometric pressure sensor. For example, without user interaction, a mobile device may cycle between blocks 370 and 372 on the determined duration to maintain calibration of measurements provided by the on-board barometric pressure sensor. If while waiting at block 370 the mobile device performs a calibration operation in response to an external event (e.g. , a user initiate calibration operation), the mobile device may restart the wait at block 370 before proceeding to a subsequent calibration operation at block 372.

[00103] As discussed above, a mobile device may measure or determine a drift experienced by a barometric pressure sensor expressed as a drift rate (e.g., atm/min). If a mobile device is located within a multistory building there may be no need to return to a known altitude (e.g., lobby level) to calibrate the barometric pressure sensor if the barometric pressure sensor is re-calibrated sufficiently frequent for a given drift rate. For example, pressure may be monitored using periodic sampling.

[00104] In the particular implementation of FIG. 3C, discrete vertical levels may be presumed to be offset by a uniform vertical spacing. FIGs. 3F and 3G are directed to an alternative embodiment in which discrete vertical levels at a frequently visited location (e.g., vertical floors in a building such as a home where a user lives, an office building where the user works, a building of a school where the user is a student, etc). In one example, a mobile device may determine a location of the mobile device to be at or in the vicinity of the frequently visited location based, at least in part, on an outdoor GNSS position fix from acquisition of SPS signals (e.g., at an entrance to a particular building comprising the frequently visited location). In a particular implementation, blocks 362, 364, 366, 368, 370 and 372 may be performed, at least in part, by a computing device such as processing unit(s) 502 in combination with memory 504, to calibrate altimeter/barometric pressure sensor(s) 524, for example.

[00105] FIG. 3F is a flow diagram of a process for obtaining measurements of altitudes for discrete vertical levels to be maintained as a reference for future calibration operations according to an embodiment. At block 374, a mobile device may determine that it is located at a frequently visited location (e.g. , as described above, for example) and that an onboard barometric pressure sensor is in a calibrated state. In this context, a "frequently visited location" comprises a portion of a navigable region that a mobile device has visited in the past or is expected to visit at some time in the future. For example, a frequently visited location may comprise an office building, a single family dwelling or an apartment building. In a particular implementation, a frequently visited location may comprise a location determined with reference to an electronic map. In one example, a frequently visited location may be determined by a user input to a device such as labels applied to locations defined as a "home," "office," "gym," "store," etc. In another example, a frequently visited location may comprise an area within a map region through which a location of a mobile device has been tracked through over time (e.g., a history of past location estimates being in the area within the map). It should be understood, however, that these are merely examples of a frequently visited location and claimed subject matter is not limited in this respect. A "calibrated state" of a barometric pressure sensor, as used herein, indicates a condition in which measurements of the barometric pressure obtained from the barometric pressure sensor may be mapped to an actual barometric pressure with sufficient accuracy to support an application or perform a particular task. Referring to expression (1 ) for a particular non- limiting embodiment, a barometric pressure sensor may be in a calibrated state if values for APdnft or APweather, or a combination of APdnft or APweather, are known (e.g., by a mobile device as stored in a memory) with a certain accuracy or certainty (e.g., an expected error in estimates of APdnft or APweather, or a combination of APdnft or APweather is less than a threshold value). It should be understood, however, that this is merely an example of how a barometric pressure sensor may be determined to be in a calibrated state and claimed subject matter is not limited in this respect. According to an embodiment, a mobile device may calibrate its onboard barometric pressure sensor (e.g., place the barometric pressure sensor in a calibrated state) for subsequent pressure measurements in an outdoor area as discussed above (e.g., by obtaining GNSS position fix providing an accurate/reliable altitude estimate and a reference pressure value).

[00106] Block 376 may determine that the mobile device is located at a particular discrete vertical level (e.g. , a floor of a building). In one embodiment, the mobile device may store a map identifying the frequently visited area as a point of interest, structure, etc., and including other details or metadata regarding the frequently visited location such as specific boundaries of the frequently visited location area such as locations of exterior walls, number of floors, etc. However, the map may not contain altitudes of discrete vertical levels (e.g., specific building floors) with sufficient accuracy for use in calibrating a barometric pressure sensor. In one implementation, a user may provide an input signal to a user interface (e.g., a touchscreen, microphone, detectable gesture etc.) to indicate that the mobile device is located on a particular discrete vertical level. Alternatively, a mobile device may process signals from one or more accelerometers to detect transitions between discrete vertical levels followed by a duration of time in which a barometric pressure measured at an onboard barometric pressure sensor moves within a very small range. These measurements may be combined with acquisitions of local indoor signals (e.g., from IEEE std. 802.1 1 transmitters indicating a particular floor of a building) for inferring that the mobile device is located on a particular discrete vertical level of a plurality of discrete vertical levels. It should be understood, however, that these are merely examples of how a mobile device may determine that it is located on a particular discrete vertical level of a plurality of discrete vertical levels at a frequently visited location, and claimed subject matter is not limited in this respect.

[00107] At block 378, with a calibrated barometric pressure sensor (as discussed above), the mobile device may measure an altitude at a particular discrete vertical level and store the measured altitude in a memory (e.g., in a table or other structure associating discrete vertical levels of the frequently visited location with altitude values). Here, for example, the mobile device may compute an altitude at the particular vertical level based, at least in part, on barometric pressure measurements obtained at the barometric pressure sensor and corrected for APdrm or APweamer, or a combination of APdnn and APweamer. Blocks 376 and 378 may be repeated for multiple discrete vertical levels.

Alternatively, after an altitude of a first discrete vertical level is determined at block 378 the altitudes of other discrete levels may be determined if it is assumed that the other discrete vertical levels are offset in altitude from the first discrete vertical level by known amounts. Block 380 may store altitude values determined at block 378 in a memory device (e.g., memory 404) for use in future calibration operations such as a calibration operation performed according to the process of FIGs. 3E or 3F.

[00108] Using altitude values associated with discrete vertical levels stored in a memory (e.g. , using the process of FIG. 3F), a mobile device may calibrate (or recalibrate) barometric pressure measurements of its onboard barometric pressure sensor as it approaches or returns to a discrete vertical level. FIG. 3G is a flow diagram of a process that may be used for calibrating a barometric pressure sensor, according to an embodiment. At block 382, a mobile device may determine that it is located on a discrete vertical level at a frequently visited location as described above at blocks 376, for example. At block 384, the mobile device may obtain a barometric pressure measurement from its onboard barometric pressure sensor. Block 386 may select a discrete level from among a plurality of discrete vertical levels based, at least in part, on barometric pressure measurement(s) obtained at block 384. In one implementation, a memory device on the mobile device may store altitude values corresponding to the discrete vertical levels (e.g. , linear altitude values or barometric pressure values stored in association with discrete vertical levels of the frequently visited location as indicate above for block 380). Here, block 386 may apply a well known conversion of the obtained barometric pressure measurement to units of altitude (e.g. , meters). For example, block 386 may map barometric pressure sensor measurements obtained at block 384 to estimated altitude values according to may be mapped according to expression (4) as follows: est. (alt) = kT/mg ln[(P _meas - APdnn - ΔΡ weather) IP sea] (4) where:

Pmeas is a value of a pressure measurement obtained at a barometric pressure sensor; and

Psea is a barometric pressure at sea level

[00109] Here, block 386 may compare a value for est. (alt) with altitude values stored in a memory device corresponding to the plurality of discrete vertical levels. It should be understood, however, that expression (4) is merely an example of a mapping of a barometric pressure measurement to an estimated, and claimed subject matter is not limited in this respect. [00110] Block 388 may then align the barometric pressure measurement obtained at block 384 and the stored altitude value of the selected discrete level to calibrate subsequent barometric pressure measurements according to expression (1 ) above, for example.

[00111] According to an embodiment, recalibration may be performed as set forth in FIG. 3G based on pre-stored altitudes corresponding to floors at a known location. For a relatively stable barometric pressure sensor, this can be done relatively infrequently, possibly triggered by measured pressure drift corresponding to weather while on a discrete level (e.g. , not associated with walking/riding/movement between floors) or triggered periodically (daily) or by some action (plugged into a charge at known location) or triggered by a periodic pressure reading showing that the measured pressure is different from the pressure assigned to a discrete level in the table of floors by greater than some threshold value (for example, the pressure change associated with a change in altitude of 1/3 of a floor.

[00112] FIG. 4 is a flow diagram of a process for calibrating a mobile device (e.g., mobile device 104 or 500) according to an alternative embodiment. In certain aspects, the process of FIG. 4 may be used for performing operations to calibrate a barometric pressure sensor onboard a mobile device (e.g. , altimeter/barometric pressure sensor(s) 524) in response to a determination or recognition that the mobile device has returned to a frequently visited location. Also, particular operations or aspects of the process of FIG. 4 may be performed by a computing device (e.g., processing unit(s) 502 and memory 504 as controlled by instructions 522 stored on computer readable medium 520). According to an embodiment, a mobile device may perform an initial calibration operation in response to determining that an estimated error in an estimate of an altitude of the mobile device is less than a threshold error value (e.g., detected at processing unit(s) 502). Here, such an initial calibration operation may be performed according to expression (1 ) as discussed above, for example. In one implementation, a calibration operation may compute one or more calibration factors (e.g., APdnft) using different techniques or sources, and select a computed calibration factor for use in calibrating measurements of a barometric pressure sensor in computing altitude measurements. In one example implementation, a calibration operation may compute multiple calibration factors based, at least in part, on the plurality of barometric pressure measurements; and select a computed calibration factor based, at least in part, on one or more reliability metrics.

[00113] According to an embodiment, a determination that an expected estimated error of an estimate of an altitude of the mobile device is less than a threshold value (as initiating or triggering an initial calibration operation as discussed above) may be performed using any one of several different techniques without deviating from claimed subject matter. In one embodiment, a mobile device may combine altitude components of multiple GNSS position fixes to obtain an estimated altitude (e.g., based on signals acquired at SPS receiver 518 and processed at processing units 510). For example, the mobile device may continue obtaining GNSS position fixes and combining respective altitude components of same to compute an estimate of an altitude until an expected error of the estimate of the altitude is less than the threshold value. In one particular alternative aspect, the mobile device may determine whether conditions for obtaining GNSS position fixes are likely to be sufficient for this purpose using known pseudorange consistency checks.

[00114] In another embodiment, an initial calibration operation may be performed in response to a measure of confidence of the estimated altitude of the mobile device. This measure of confidence may be based, at least in part, on a number of measurements used to determine the estimate of the altitude, a known bias, inferred movement of the mobile device while measurements are obtained for determining the estimate of the altitude, a dilution of precision in the measurements used to determine the estimate of the altitude or an estimate of error in measurements used to determine the estimate of the altitude, or a combination thereof. In another example, such a measure of confidence of an estimated altitude may be further based, at least in part, on a user input (e.g., from a an input device such as a keypad, touchscreen, microphone, etc.) specifying a degree of confidence, a confidence in an estimated horizontal location of the mobile device or an accuracy of a terrain map, or any

combination thereof. In a particular implementation, a degree of confidence may be determined to be above a threshold value. Also, a confidence of the estimated altitude of the mobile device may be based, at least in part, on a level of confidence in a state of calibration of a barometric pressure sensor used to obtain measurements for determining the estimated altitude. For example, a level of confidence in a state of calibration of a barometric pressure sensor used to obtain a particular pressure measurement for determining an estimated altitude may be based, at least in part, on a duration of time since most recent calibration operation at a time that the particular measurement is obtained. If there are pre-existing altitude estimates, the pre-existing altitude estimates may be combined with a most recent altitude estimate based on associated levels of confidence when corresponding pressure measurement are obtained. For example, pre-existing altitude estimates may be combined with a most recent altitude estimate by computing a weighted combination (e.g. , weighted average) of altitude estimates based on associated levels of confidence in states of calibration of the barometric pressure sensor when pressure measurements are obtained. In another implementation, an estimated altitude for use in calibrating the barometric pressure sensor may be based, at least in part, on an acquisition of a beacon signal from a reference transmitter (e.g., at receiver(s) 510). An initial operation to calibrate the barometric pressure sensor of the mobile device further occur in response to a measure of confidence of the estimate of the altitude of the mobile device based, at least in part, on a measured signal strength of the acquired beacon signal.

[00115] In another implementation, an initial operation to calibrate the barometric pressure sensor may comprise: determining a condition for an extended period for calibration of the barometric pressure sensor; obtaining one or more measurements of altitude during the extended period; obtaining at least one barometric pressure measurement from the barometric pressure sensor during the extended period; and calibrating the barometric pressure sensor based, at least in part, on at least one of the one or more measurements of altitude and the at least one barometric pressure measurement. In one example implementation, a mobile device may determine a condition for the extended period based on a detection of an absence of motion of the mobile device (e.g. , based on signals processed at receiver(s) 510 or sensor(s) 516). In another alternative, the mobile device may detect a condition for the extended period by detecting that it is not being used to place a call or any other user activity.

[00116] In another example implementation, a mobile device may determine the condition for the extended period by detecting that the mobile device is powered from an external power source. In another aspect, the extended period may be terminated in response to detection of a disconnection from the external power source. In another aspect, the external power source may comprise a charger adapter. Here, such a condition that the mobile device is powered by a charger adapter plugged into a wall socket may indicate that the mobile device is in a static state. Additionally, such a condition that the mobile device is connected to an external power source may further indicate that the mobile device may perform several power intensive GNSS position fix operations without depleting battery resources.

[00117] In another embodiment, a mobile device may detect a condition for the extended period by detecting an approximate location of the mobile device or a time of day, or a combination thereof. In another embodiment, a mobile device may combine measurements of altitude to provide the estimated altitude, and terminate the extended period in response to an estimated uncertainty in the altitude estimate being smaller than a threshold uncertainty value. For example, the mobile device may combine combining measurements of altitude obtained during the extended period to provide the altitude estimate and terminate the extended period in response to an estimated uncertainty in the altitude estimate being smaller than a threshold uncertainty value. In another particular alternative, a relatively consistent reported output position may be used to confirm that the mobile device is in a static or non-moving state. [00118] According to an embodiment, block 402 may determine that the mobile device is located at one or more frequently visited locations such as, for example, a room in a home, an office in an office building, grocery store, school, gym, etc. using any one of several different techniques. In a particular implementation, block 402 may follow an initial calibration operation as discussed above. Block 402 may determine or infer that the mobile device is located at multiple different frequently visited locations at different time instances. In an implementation, block 402 may associate various RF signals (e.g., received and detected at receiver(s) 510 or SPS receiver 518) with signature values characteristic of the frequently visited location(s) (e.g. , in a radio heatmap). For example, a mobile device may associate measured characteristics (e.g., RSSI, round-trip time (RTT), angle of arrival (AoA), etc.) of RF signals received from one or more sources (e.g. , cellular, WiFi, Bluetooth ^® , etc.) with expected signature values associated with particular locations (e.g. , in a radio heatmap associating expected values of RSSI, RTT or AoA of signals acquired from specific transmitters with particular locations in an area of interest) to determine that the mobile device is located at, or at least near, the frequently visited location. It should be understood, however, that this is merely an example of how a mobile device may determine that it is located at a frequently visited location based on an association of measured characteristics of RF signals with expected signature values, and claimed subject matter is not limited in this respect. Alternatively, or in addition to an association of measured characteristics of RF signals with expected signature values, a mobile device may determine that it is at a frequently visited location based on whether the mobile device is currently receiving power from an external source such as from a charger adapter that is plugged into a wall socket (e.g. , while being typically charged at a particular "frequently visited" location such as a bedroom or office). It should be understood, however that this is merely an example of a technique for determining or inferring that a mobile device is located at a particular frequently visited location and claimed subject matter is not limited in this respect.

[00119] While located at a frequently visited location as determined at block 402, the barometric pressure sensor of the mobile device may still be in a calibrated state following a previous calibration operation. Further while located at the frequently visited locations and while the barometric pressure sensor is still in the calibrated state, the mobile device may obtain measurements of altitude (e.g. , computed according to expression (4)) computed based, at least in part, on one or more first pressure measurements obtained by the barometric pressure sensor at block 406. Block 408 may then store the measurements of altitude obtained while located at the frequently visited locations in a memory device (e.g. , memory 504) in association with unique identifiers of particular frequently visited locations.

[00120] In a particular implementation, an indication of an altitude of a mobile device stored at block 408 may comprise an altitude expressed in distance relative to a reference altitude (e.g., feet above sea level), floor of a building, or other value or identifier that is indicative of an altitude of the mobile device. Additionally, indication of a frequently visited location may comprise an identifier of a landmark, horizontal location (e.g., latitude and longitude), identifier of a floor of a building, room on a floor or in a dwelling, just to provide a few examples. [00121] According to an embodiment, the first indication of altitude stored at block 408 may be updated based, at least in part, on subsequent pressure measurements obtained at the pressure sensor while located at the first frequently visited location (e.g., at different times upon returning to the first frequently visited location). In one example implementation, the first indication of the altitude may be updated by weighting the subsequent pressure measurements based, at least in part, on levels of confidence in states of calibration of the barometric pressure sensor while the subsequent pressure measurements are obtained. As pointed out above, a barometric pressure sensor on a mobile device may drift increasingly out of calibration over time. As such, levels of confidence in states of calibration of a barometric pressure sensor may be determined based, at least in part, on a duration of time since a most recent calibration operation.

[00122] According to an embodiment, a barometric pressure sensor is determined to be in a "calibrated" state at block 404 if an uncertainty or expected error in an altitude measurement obtained based on raw

measurements of the barometric pressure sensor is sufficiently small for a particular desired application. For example, the barometric pressure sensor may be determined to be in a "calibrated" state if an uncertainty or expected error in an altitude measurement obtained from the barometric pressure sensor is less than a threshold value. In another example implementation, the barometric pressure sensor may be determined to be in a "calibrated" state if an uncertainty or expected error in one or more particular calibration factors (e.g., ΔΡ da or APweather) are less than a threshold value. In one particular

implementation, block 404 may determine that the barometric pressure sensor is in a calibrated state based, at least in part, on a duration of time since the most recent calibration operation (e.g. , an initial operation to calibrate). In particular implementations, actual computation of an uncertainty or an expected error in a calibration factor to determine whether a pressure sensor is in a calibrated state. For example, a pressure sensor may be determined to be in a calibrated state or no longer in a calibrated state based, at least in part, on a duration since a most recent calibration operation. It should be understood, however, that these are merely examples of how a barometric pressure sensor may be determined to be in a calibrated state and claimed subject matter is not limited in this respect.

[00123] Following block 406, over time the barometric pressure sensor may become uncalibrated (e.g., an uncertainty or expected error in a value for APdnft or APweather has increased significantly over time). At block 414, the mobile device may perform an operation to calibrate the barometric pressure sensor in response to a determination or inference that the mobile device has returned to at least one of the one or more frequently visited locations determined at block 410. Block 410 may determine or infer that the mobile device has returned to one of the one or more frequently visited locations using techniques discussed above in connection with block 402, for example. Block 412 may then obtain one or more barometric pressure measurements from the barometric pressure sensor and retrieve from the memory device indicative of the altitude

measurement stored at block 408 to perform the calibration operation at block 414. For example, block 414 may retrieve an altitude measurement stored at block 408 in association with an identifier of the frequently visited location to which the mobile device had returned at block 410. Calibration at block 414 may be performed to estimate a calibration factor (e.g., APdnft) according to expression (1 ), for example.

[00124] According to an embodiment, a mobile device may store indications of altitude of multiple different frequently visited locations for use in subsequent operations to calibrate a barometric pressure sensor. For example, a mobile device may execute blocks 402 through 414 for a second frequently visited location, third frequently visited location, and so forth. Thus a mobile may have opportunities for calibrating its barometric pressure sensor on returning to any one of the frequently visited locations for which an indication of altitude is maintained in a memory device.

[00125] The particular operations shown in FIG. 4 are directed to opportunistic calibration of a barometric pressure sensor as a mobile device returns to a particular frequently visited location. In other embodiments, a mobile device user may have multiple frequently visited locations at particular known altitudes providing similar opportunities to calibrate the barometric pressure sensor. As such, it should be understood that blocks 404 through 414 may be repeated to provide multiple indications of altitude to be stored in association with corresponding frequently visited locations. As such, the mobile device may opportunistically calibrate its barometric pressure sensor if returning to any of the frequently visited location for which there is a pre-stored indication of altitude (e.g. , stored at an operation discussed above in connection with block 408).

[00126] A mobile device may determine that it is located at or has returned to a frequently visited location (e.g., at block 402 or block 410) using any one of several techniques, employed individually or in combination with techniques identified above. In one example technique, a mobile device may determine that it is located at a particular altitude of a frequently visited location, at least in part, by determining that the mobile device is located within a certain horizontal distance of the frequently visited location. Here, for example, it may be inferred that an altitude of a navigable surface (e.g., terrain or floor of a building) does not vary significantly from the frequently visited location extending outwardly the certain horizontal distance. In a particular example implementation, a location of a mobile device on a particular floor or vertical level in a known dwelling (e.g., a map of the particular floor is known) may be detected based, at least in part, on detection of a particular known signal. For example, the mobile device may determine that it is located on a particular floor with a sufficient level of confidence by determining a match of received signals with signal signatures expected for receivers located on the particular floor. In a particular

embodiment, a frequently visited location may comprise a particular room within a known dwelling (e.g., a bedroom) wherever the mobile device may be connected charger that is plugged into a wall socket, or in a more general area such as a first floor of the known dwelling.

[00127] In another embodiment, a mobile device may determine that it is located at a frequently visited location based on acquisition/detection of a combination of signals across multiple different technologies such as WiFi, Bluetooth ^® , Infrared Data Association (IrDA) data link (e.g., if a mobile device is located near a television or set-top box and capable of detecting an infrared data link) or GNSS transmissions, just to provide a few examples. In another particular implementation, a mobile device may be determined to be located at a frequently visited location based, at least in part, on dead reckoning techniques using signal generated by sensors (e.g., pressure sensors and/or inertial sensors in sensors 516). For example, a mobile device may obtain a GNSS position fix to determine that the mobile device is located in a known dwelling at a particular floor or vertical level, and then process signals from inertial a barometric pressure sensor and/or sensors to determine whether the mobile device transitioned to a higher or lower level (e.g., up or down stairs). In another particular implementation, a mobile device may run a time counter in combination with signals from inertial sensors to determine whether the mobile device is dwelling at a particular location to determine, for example, how often or how long a user of a mobile device dwells at a particular location (e.g., infer a location where the user spends his/her workday or where the user sleeps at night). For example, a mobile device may evaluate some times of day when the user is likely to be at a workplace (e.g., at desk in office) and other times of day when the user is likely to be at home sleeping in a bedroom, watching TV in the living room, etc. Alternatively, the mobile device may determine times that the mobile device is plugged into a charger at a known location (again, typically the same place, so that could trigger you to look at the signals and if they match up too, you're probably in the same place).

[00128] Attention is now drawn to FIG. 5, which is a schematic diagram illustrating certain features of an example special purpose computing platform 400 that may be provisioned within a mobile device 104 and/or apparatus 106, in accordance with certain example implementation.

[00129] As illustrated special computing platform 500 may comprise one or more processing units 502 (e.g., to perform data processing in accordance with certain techniques provided herein) coupled to memory 504 via one or more connections 506 (e.g., one or more electrical conductors, one or more electrically conductive paths, one or more buses, one or more fiber-optic paths, one or more circuits, one or more buffers, one or more transmitters, one or more receivers, etc.). Processing unit(s) 502 may, for example, be implemented in hardware or a combination of hardware and software. Processing unit(s) 502 may be representative of one or more circuits configurable to perform at least a portion of a data computing procedure or process. By way of example but not limitation, a processing unit may include one or more processors, controllers, microprocessors, microcontrollers, application specific integrated circuits, digital signal processors, programmable logic devices, field programmable gate arrays, or the like, or any combination thereof. Processing unit(s) 502 may, for example, perform computer implementable instructions corresponding to one or more applications(s) 152 (FIG. 1 ).

[00130] Memory 504 may be representative of any data storage mechanism. Memory 504 may include, for example, a primary memory 504-1 and/or a secondary memory 504-2. Primary memory 504-1 may comprise, for example, a random access memory, read only memory, etc. While illustrated in this example as being separate from the processing units, it should be understood that all or part of a primary memory may be provided within or otherwise co- located and coupled with processing unit 502 or other like circuitry within mobile device 104. Secondary memory 504-2 may comprise, for example, the same or similar type of memory as primary memory and/or one or more data storage devices or systems, such as, for example, a disk drive, an optical disc drive, a tape drive, a solid motion state memory drive, etc. [00131] In certain implementations, secondary memory may be operatively receptive of, or otherwise configurable to couple to, a non-transitory computer readable medium 520. Memory 504 and/or non-transitory computer readable medium 520 may comprise instructions 522 for use in performing data processing, e.g. , in accordance with the applicable techniques as provided herein.

[00132] Special purpose computing platform 500 may, for example, further comprise one or more communication interface 508. Communication interface 508 may, for example, comprise one or more wired and/or wireless network interface units, radios, modems, etc., represented here by one or more receivers 510 and one or more transmitters 512. It should be understood that in certain implementations, communication interface 508 may comprise one or more transceivers, and/or the like. Further, it should be understood that although not shown, communication interface 508 may comprise one or more antennas and/or other circuitry as may be applicable given the communication interface capability.

[00133] In accordance with certain example implementations, communication interface 408 may, for example, be enabled for use with various wired communication networks, e.g. , such as telephone system, a local area network, a wide area network, a personal area network, an intranet, the Internet, etc.

[00134] In accordance with certain example implementations communication interface 508 may, for example, be enabled for use with various wireless communication networks such as a wireless wide area network (WWAN), a wireless local area network (WLAN), a wireless personal area network (WPAN), and so on. The term "network" and "system" may be used interchangeably herein. A WWAN may be a Code Division Multiple Access (CDMA) network, a Time Division Multiple Access (TDMA) network, a Frequency Division Multiple Access (FDMA) network, an Orthogonal Frequency Division Multiple Access (OFDMA) network, a Single-Carrier Frequency Division Multiple Access (SC- FDMA) network, and so on. A CDMA network may implement one or more radio access technologies (RATs) such as cdma2000, Wideband-CDMA (W- CDMA), Time Division Synchronous Code Division Multiple Access (TD- SCDMA), to name just a few radio technologies. Here, cdma2000 may include technologies implemented according to IS-95, IS-2000, and IS-856 standards. A TDMA network may implement Global System for Mobile Communications (GSM), Digital Advanced Mobile Phone System (D-AMBP capability), or some other RAT. GSM and W-CDMA are described in documents from a consortium named "3rd Generation Partnership Project" (3GPP). Cdma2000 is described in documents from a consortium named "3rd Generation Partnership Project 2" (3GPP2). 3GPP and 3GPP2 documents are publicly available. A WLAN may include an IEEE 802.1 1x network, and a WPAN may include a Bluetooth network, an IEEE 802.15x, for example. Wireless communication networks may include so-called next generation technologies (e.g., "4G"), such as, for example, Long Term Evolution (LTE), Advanced LTE, WiMAX, Ultra Mobile Broadband (UMB), and/or the like. Additionally, communication interface(s) 408 may further provide for infrared-based communications with one or more other devices. A WLAN may, for example, comprise an IEEE 802.1 1x network, and a WPAN may comprise a Bluetooth network, an IEEE 802.15x, for example. Wireless communication implementations described herein may also be used in connection with any combination of WWAN, WLAN or WPAN. [00135] Mobile device 104 may, for example, further comprise one or more input and/or output units 514. Input and/or output units 514 may represent one or more devices or other like mechanisms that may be used to obtain inputs from and/or provide outputs to one or more other devices and/or a user. Thus, for example, input and/or output units 514 may comprise various buttons, switches, a touch pad, a trackball, a joystick, a touch screen, a keyboard, a microphone, a camera, and/or the like, which may be used to receive one or more user inputs. In certain instances, input and/or output units 514 may comprise various devices that may be used in producing a visual output, an audible output, and/or a tactile output for a user. For example, input and/or output units 514 may be used to present a video display, graphical user interface, positioning and/or navigation related information, visual

representations of electronic map, routing directions, etc., via a display mechanism and/or audio mechanism.

[00136] Mobile device 104 may, for example, comprise one or more sensors 516. For example, sensor(s) 516 may represent one or more environmental sensors, such as, e.g., a magnetometer or compass, a barometer or altimeter, etc., and which may be useful for positioning. For example, sensor(s) 516 may represent one or more inertial sensors, which may be useful in detecting certain movements of mobile device 104. Thus for example, sensor(s) 516 may comprise one or more accelerometers, one or one or more gyroscopes. Further, in certain instances sensor(s) 516 may comprise and/or take the form of one or more input devices such as a microphone, a camera, a light sensor, etc. In addition, mobile device may comprise altimeter/barometric pressure sensor(s) 524 capable of obtaining barometric pressure measurements and/or measuring an altitude. Measurements obtained from altimeter/barometric pressure sensor(s) 524 may be stored in memory 504 for use in positioning operations, for example. In addition, Measurements obtained from altimeter/barometric pressure sensor(s) 524 may be calibrated using processes and techniques described herein. In this context, barometer, barometric pressure sensor and altimeter may be used interchangeably throughout this specification.

[00137] Mobile device 104 may, for example, comprise an SPS receiver 518 capable of acquiring SPS signals 134 via one or more antennas (not shown). SPS receiver 518 may also process, in whole or in part, SPS signals 134 for estimating a position and/or a motion of mobile device 104. In certain instances, SPS receiver 518 may comprise one or more processing unit(s) (not shown), e.g., one or more general purpose processors, one or more digital signal processors DSP(s), one or more specialized processors that may also be utilized to process acquired SPS signals, in whole or in part, and/or calculate an estimated location of mobile device 104. In certain implementations, all or part of such processing of acquired SPS signals may be performed by other processing capabilities in mobile device 104, e.g., processing unit(s) 502, memory 504, etc., in conjunction with SPS receiver 518. Storage of SPS or other signals for use in performing positioning operations may be performed in memory 504 or registers (not shown).

[00138] In certain instances, sensor(s) 516 may generate analog or digital signals that may be stored in memory 504 and processed by DSP(s) (not shown) or processing unit(s) 502 in support of one or more applications such as, for example, applications directed to positioning or navigation operations based, at least in part, on one or more positioning functions. [00139] Processing unit(s) 502 may comprise a dedicated modem processor or the like that may be capable of performing baseband processing of signals acquired and downconverted at receiver(s) 510 of communication interface 508 or SPS receiver 518. Similarly, a modem processor or the like may perform baseband processing of signals to be upconverted for transmission by

(wireless) transmitter(s) 512. In alternative implementations, instead of having a dedicated modem processor, baseband processing may be performed by a general purpose processor or DSP (e.g., general purpose and/or application processor). It should be understood, however, that these are merely examples of structures that may perform baseband processing, and that claimed subject matter is not limited in this respect. Moreover, it should be understood that the example techniques provided herein may be adapted for a variety of different electronic devices, mobile devices, transmitting devices, environments, position fix modes, etc.

[00140] The techniques described herein may be implemented by various means depending upon applications according to particular features and/or examples. For example, such methodologies may be implemented in hardware, firmware, and/or combinations thereof, along with software. In a hardware implementation, for example, a processing unit may be implemented within one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, electronic devices, other devices units designed to perform the functions described herein, and/or combinations thereof. [00141] In the preceding detailed description, numerous specific details have been set forth to provide a thorough understanding of claimed subject matter. However, it will be understood by those skilled in the art that claimed subject matter may be practiced without these specific details. In other instances, methods and apparatuses that would be known by one of ordinary skill have not been described in detail so as not to obscure claimed subject matter

[00142] Some portions of the preceding detailed description have been presented in terms of algorithms or symbolic representations of operations on binary digital electronic signals stored within a memory of a specific apparatus or special purpose computing device or platform. In the context of this particular specification, the term specific apparatus or the like includes a general purpose computer once it is programmed to perform particular functions pursuant to instructions from program software. Algorithmic descriptions or symbolic representations are examples of techniques used by those of ordinary skill in the signal processing or related arts to convey the substance of their work to others skilled in the art. An algorithm is here, and generally, is considered to be a self-consistent sequence of operations or similar signal processing leading to a desired result. In this context, operations or processing involve physical manipulation of physical quantities. Typically, although not necessarily, such quantities may take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared or otherwise manipulated as electronic signals representing information. It has proven convenient at times, principally for reasons of common usage, to refer to such signals as bits, data, values, elements, symbols, characters, terms, numbers, numerals, information, or the like. It should be understood, however, that all of these or similar terms are to be associated with appropriate physical quantities and are merely convenient labels. Unless specifically motion stated otherwise, as apparent from the following discussion, it is appreciated that throughout this specification discussions utilizing terms such as "processing", "computing", "calculating", "determining", "generating", "obtaining", "modifying", "selecting", "identifying", and/or the like refer to actions or processes of a specific apparatus, such as a special purpose computer or a similar special purpose electronic computing device. In the context of this specification, therefore, a special purpose computer or a similar special purpose electronic computing device is capable of manipulating or transforming signals, typically represented as physical electronic or magnetic quantities within memories, registers, or other information storage devices, transmission devices, or display devices of the special purpose computer or similar special purpose electronic computing device. In the context of this particular patent application, the term "specific apparatus" may include a general purpose computer once it is programmed to perform particular functions pursuant to instructions from program software.

[00143] While there has been illustrated and described what are presently considered to be example features, it will be understood by those skilled in the art that various other modifications may be made, and equivalents may be substituted, without departing from claimed subject matter. Additionally, many modifications may be made to adapt a particular situation to the teachings of claimed subject matter without departing from the central concept described herein.

[00144] Therefore, it is intended that claimed subject matter not be limited to the particular examples disclosed, but that such claimed subject matter may also include all aspects falling within the scope of appended claims, and equivalents thereof.