Location based tracking

RELATED APPLICATIONS

This application claims benefit of priority of U.S. Provisional Patent Application Ser. No. 60/914,222, filed on Apr. 26, 2007, which is hereby incorporated by reference in its entirety.

BACKGROUND

1. Field

The subject matter disclosed herein relates to obtaining position fixes using a position determination method in response to a change in a radio frequency (RF) environment.

2. Information

A satellite positioning system (SPS) typically comprises a system of transmitters positioned to enable entities to determine their location on the Earth based, at least in part, on signals received from the transmitters. Such a transmitter typically transmits a signal marked with a repeating pseudo-random noise (PN) code of a set number of chips and may be located on ground-based control stations, user equipment and/or space vehicles. In a particular example, such transmitters may be located on Earth orbiting satellites. For example, a satellite in a constellation of a Global Navigation Satellite System (GNSS) such as Global Positioning System (GPS), Galileo, Glonass, or Compass may transmit a signal marked with a PN code that is distinguishable from PN codes transmitted by other satellites in the constellation.

To estimate a position at a receiver, a navigation system may determine pseudorange measurements to satellites “in view” of the receiver using well known techniques based, at least in part, on detections of PN codes in signals received from the satellites. Such a pseudorange to a satellite may be determined based, at least in part, on a code phase detected in a received signal marked with a PN code associated with the satellite during a process of acquiring the received signal at a receiver. To acquire the received signal, a navigation system typically correlates the received signal with a locally generated PN code associated with a satellite. For example, such a navigation system typically correlates such a received signal with multiple code and/or time shifted versions of such a locally generated PN code. Detection of a particular time and/or code shifted version yielding a correlation result with the highest signal power may indicate a code phase associated with the acquired signal for use in measuring pseudorange as discussed above.

<figref idrefs="DRAWINGS">FIG. 1</figref> illustrates an application of an SPS system, whereby a mobile station (MS) <b>100</b> in a wireless communications system may receive transmissions from satellites <b>102</b><i>a</i>, <b>102</b><i>b</i>, <b>102</b><i>c</i>, <b>102</b><i>d </i>in the line of sight to MS <b>100</b>, and derives time measurements from a plurality of such transmissions. MS <b>100</b> may provide such measurements to location server <b>104</b>, which may determine the position of the station from the measurements. Location server <b>104</b> may comprise any one of several platforms capable of determining the position of MS <b>100</b> including, for example, a position determination entity (PDE), serving mobile location center (SMLC), stand-alone SMLC (SAS) or a SUPL location platform (SUPL), just to name a few examples. Alternatively, MS <b>100</b> may determine its own position independently of such a location server.

MS <b>100</b> may search for a transmission from a particular satellite by correlating the PN code for the satellite with a received signal. The received signal typically comprises a composite of transmissions from one or more satellites within a line of sight to a receiver at MS <b>100</b> in the presence of noise. Though MS <b>100</b> may be capable of determining its position from received satellite transmission signals, buildings or other structures may “block” such signals, for example. In other words, whether or not a sufficient number of SPS satellites are in view of MS <b>100</b> may depend, at least in part, on the radio frequency (RF) environment of MS <b>100</b>. In such an RF environment that may prevent MS <b>100</b> from acquiring signals from SPS satellites, determination of the position of MS <b>100</b> may instead be facilitated through communication with location server <b>104</b>. Here, for example, MS <b>100</b> may obtain pseudorange measurements to terrestrial base stations using advanced forward link trilateration (AFLT) and forward such pseudorange measurements and other information (e.g., pseudorange measurements to one or more SPS satellites) to location server <b>104</b>. Alternatively, MS <b>100</b> may employ other techniques for obtaining measurements for use in determining a range to a terrestrial base station such as, for example, observed time difference of arrival (OTDOA), enhanced observed time difference (E-OTD) and uplink time difference of arrival (U-TDOA), just to name a few examples.

BRIEF DESCRIPTION OF THE FIGURES

Non-limiting and non-exhaustive features will be described with reference to the following figures, wherein like reference numerals refer to like parts throughout the various figures.

<figref idrefs="DRAWINGS">FIG. 1</figref> is a schematic diagram of a satellite positioning system (SPS), according to one aspect.

<figref idrefs="DRAWINGS">FIG. 2</figref> is a schematic diagram of a timeline for one aspect of a mobile station subjected to favorable and unfavorable RF environments, according to one implementation.

<figref idrefs="DRAWINGS">FIG. 3</figref> is a flow chart showing a process for reducing the rate of MSA fixes, according to one implementation.

<figref idrefs="DRAWINGS">FIG. 4</figref> is a schematic diagram showing a geofence, according to one implementation.

<figref idrefs="DRAWINGS">FIG. 5</figref> is a schematic diagram showing a mobile station trajectory through varying RF environments, according to one implementation.

<figref idrefs="DRAWINGS">FIG. 6</figref> is a schematic diagram of a device capable of communication with a wireless network, according to one implementation.

SUMMARY

In one particular implementation, a device is adapted to transition from obtaining one or more position fixes using a first position determination method to obtain one or more position fixes using a second position determination method in response to a first change in an RF environment. It should be understood, however, that this is merely one example implementation and that claimed subject matter is not limited to this particular implementation.

DETAILED DESCRIPTION

Reference throughout this specification to “one example”, “one feature”, “an example” or “one feature” means that a particular feature, structure, or characteristic described in connection with the feature and/or example is included in at least one feature and/or example of claimed subject matter. Thus, the appearances of the phrase “in one example”, “an example”, “in one feature” or “a feature” in various places throughout this specification are not necessarily all referring to the same feature and/or example. Furthermore, the particular features, structures, or characteristics may be combined in one or more examples and/or features.

Methodologies 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, software, and/or combinations thereof. 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 designed to perform the functions described herein, and/or combinations thereof.

For a firmware and/or software implementation, methodologies may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. Any machine-readable medium tangibly embodying instructions may be used in implementing the methodologies described herein. For example, software codes may be stored in a memory, for example the memory of a mobile station, and executed by a processor. Memory may be implemented within the processor or external to the processor. As used herein the term “memory” refers to any type of long term, short term, volatile, nonvolatile, or other memory and is not to be limited to any particular type of memory or number of memories, or type of media upon which memory is stored.

A “space vehicle” (SV) as referred to herein relates to an object that is capable of transmitting signals to receivers on the Earth's surface. In one particular example, such an SV may comprise a geostationary satellite. Alternatively, an SV may comprise a satellite traveling in an orbit and moving relative to a stationary position on the Earth. However, these are merely examples of SVs and claimed subject matter is not limited in these respects.

Position determination and/or estimation techniques described herein may be used for 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), 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-AMPS), 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 comprise an IEEE 802.11x network, and a WPAN may comprise a Bluetooth network, an IEEE 802.15x, for example. Such position determination techniques described herein may also be used for any combination of WWAN, WLAN and/or WPAN.

Techniques described herein may be used with any one of several SPSs and/or combinations of SPSs. Furthermore, such techniques may he used with positioning determination systems that utilize pseudolites or a combination of satellites and pseudolites. Pseudolites may comprise ground-based transmitters that broadcast a PN code or other ranging code (e.g., similar to a GPS or CDMA cellular signal) modulated on an L-band (or other frequency) carrier signal, which may be synchronized with time. Such a transmitter may be assigned a unique PN code so as to permit identification by a remote receiver. Pseudolites may be useful in situations where GPS signals from an orbiting satellite might be unavailable, such as in tunnels, mines, buildings, urban canyons or other enclosed areas. Another implementation of pseudolites is known as radio-beacons. The term “satellite”, as used herein, is intended to include pseudolites, equivalents of pseudolites, and possibly others. The term “SPS signals”, as used herein, is intended to include SPS-like signals from pseudolites or equivalents of pseudolites.

An entity such as a wireless terminal may communicate with a network to request data and other resources. A mobile station (MS), including a cellular telephone, a personal digital assistant (PDA), or a wireless computer are just a few examples of such an entity. Communication of such an entity may include accessing network data, which may tax resources of a communication network, circuitry, or other system hardware. In wireless communication networks, data may be requested and exchanged among entities operating in the network. For example, an MS may request data from a wireless communication network to determine the position of the MS operating within the network: data received from the network may he beneficial or otherwise desired for such a position determination. However, these are merely examples of data exchange between an MS and a network in a particular aspect, and claimed subject matter is not limited in these respects.

In an implementation, utilizing SPS satellite transmission signals, an MS may attempt to obtain one or more position fixes using a first position determination method. Such an MS may automatically transition to a second position determination method in response to detection of a change in an RF environment. For example, an MS having a clear view of SPS satellites may attain position fixes from time to time using an MS-based determination method, which will be discussed below. If the MS, however, is carried into a building, for example, MS-based position fixes may not be possible due to an RF environment that limits reception of SPS signals at the MS. In such a case, the MS may automatically transition from an MS-based determination method to another position determination method, such as an MS-assisted position determination method, which is also described below. As described below according to particular implementations, the MS may transition to such an alternative position method in response to detection of a change in an RF environment evidence by a history of attempts to obtain one or more position fixes using the MS-based determination method.

Because a particular position determination method may include an associated cost, e.g., a fixed cost per use, it may be desirable to limit use of such a method. Accordingly, processes to determine and modify use of one or more position determination methods are discussed below.

As in at least one implementation mentioned above, utilizing SPS satellite transmission signals, an MS <b>100</b> (<figref idrefs="DRAWINGS">FIG. 1</figref>) may determine its position using pseudorange measurements to SVs and/or other information obtained from communication with a location server (such as location server <b>104</b>, for example), through a communication network, for example. In an MS-based (MSB) position mode, according to one particular example, position for MS <b>100</b> may be determined at MS <b>100</b> based upon pseudorange measurements to SVs obtained at MS <b>100</b> without communication with a location server. On the other hand, position information for MS <b>100</b> in an MS-assisted (MSA) position mode may be determined at a location server instead of at MS <b>100</b>, thus using resources of a communication network to facilitate communication between MS <b>100</b> and the location server. In this case, position information may then be transmitted from location server <b>104</b> to MS <b>100</b>. In one particular implementation, an MSA position mode may employ Advanced Forward Link Trilateration (AFLT) to obtain pseudorange measurements to terrestrial base stations. MS <b>100</b> may forward such pseudorange measurements, along with other information, to location server <b>104</b> where a position of MS <b>100</b> may be determined. Alternatively, MS <b>100</b> may employ any of the aforementioned observed time difference of arrival (OTDOA), enhanced observed time difference (E-OTD) and uplink time difference of arrival (U-TDOA) techniques for obtaining measurements for use in determining ranges to terrestrial base stations, and forward such measurements to location server <b>104</b> for estimating a position of MS <b>100</b>. Use of such an MSA mode may enable a fix if, for example, MS <b>100</b> is not in a favorable RF environment to acquire a sufficient number of SPS signals from SVs for a position fix, but is nevertheless able to communicate with location server <b>104</b>, for example.

In MSA mode according to a particular implementation, MS <b>100</b> may from time to time communicate with location server <b>104</b> to receive location information for a position fix. Because at least a portion of a communication network's resources, including location server <b>104</b>, may be occupied by such a communication, it may be desirable to reduce the number of position fixes using such network resources. For example, in a particular implementation, a network carrier may desire to reduce the number of MSA position fixes for which MS <b>100</b> communicates with the network, during, say, a location based services (LBS) tracking session for the MS. In one aspect, reducing a number and/or rate of MSA position fixes during an LBS tracking session may include a geofencing LBS application. In this context, the term geofencing may refer to demarcation of an area defined by location; e.g., an area that is bound by a perimeter comprising, for example, a certain radius around a central point. Such an application will be described below in detail.

In another aspect, a “throttling” process may enable a reduction in use of network resources by reducing a rate of MSA position fixes by an MS, for example. In a particular example, MS <b>100</b> may obtain position fixes in an MSB position mode while in desirable RF environments, and control if and when an MS transitions to obtaining position fixes in an MSA mode while in undesirable RF environments. Such control may include a process that reduces use of network resources. Such a reduction may, for example, increase a data capacity of a network, such as increased network spectra and IP address pools, just to name a few examples. Also, a throttling process may reduce power consumption, and thus improve battery life for example, of an MS.

<figref idrefs="DRAWINGS">FIG. 2</figref> is a schematic diagram of a timeline for an MS, such as MS <b>100</b> shown in <figref idrefs="DRAWINGS">FIG. 1</figref>, for example, subjected to favorable and unfavorable RF environments, according to one implementation. At the left portion of the horizontal timeline, at time A, an MS is shown to be operating in an MS-based mode, assuming an RF environment that permits position fixes while operating in the MS-based mode. An MS may periodically initiate attempts to obtain position fixes using an MS-based mode, for example, every second. At time B, MS-based position fixes may begin to fail. This may occur, for example, if an MS enters an RF environment with marginal conditions for receiving or processing SPS signals, such as, but not limited to, indoors or an urban canyon. During an interval of time t<b>0</b> between times B and C, an MS may continue to attempt MS-based fixes one or more times by receiving or processing an SPS signal. If such attempts are unsuccessful, say a given number of consecutive times, then an MS may automatically transition to an MS-assisted position mode. Here, this is one particular example of automatically transitioning to an alternative position determination method in response to detection of a change in an RF environment based, at least in part on a history of attempts to obtain a position fix, and claimed subject matter is not limited in this respect. In a particular example, the time interval t<b>0</b> may be a constant or may be determined according to an algorithm based on such variables as the number of consecutive times that MS-based fixes are unsuccessful over a given time interval, for example. In a specific implementation, interval t<b>0</b>, beginning from the time when an MS-based position fix fails, at time B, may be thirty or more seconds during which failed attempts at MS-based fixes continue, but this is only an example to which claimed subject matter is not limited. For example, the process described above is merely one way to determine a change in an RF environment.

After interval t<b>0</b>, as mentioned above, an MS may automatically transition to an MS-assisted position mode, indicated as “MSA fix” on the timeline at time D. Here, a single MS-assisted position fix may be attempted, though additional MSA position fixes may be performed in other implementations. At time E, a time interval t<b>1</b> after the MS-assisted fix at time D, an MS-based fix may be attempted, indicated as “MSB fixes” on the timeline. Such an interval t<b>1</b> may be a constant or may be a variable as determined according to a geofencing LBS or throttling process, mentioned above, for example. Of course, these processes are only examples, and claimed subject matter is not limited in this respect.

At time E, if the MS-based position fix is successful, an MS may automatically continue in MS-based mode, such as at time A. By successfully fixing at time E, another change in RF environment may be detected. It should be understood, however, that this is merely one particular example of how a change in an RF environment may be detected according to a particular implementation and claimed subject matter is not limited in this respect. If, however, the MS-based position fix is unsuccessful, an MS may continue with an MS-assisted position fix, such as at time D. Thereafter, interval t<b>1</b> may be increased to a value greater than its previous value before attempting to transition back to MS-based mode, at time E, for example. In other words, time interval t<b>1</b>, which starts at an MS-assisted position fix at time D, may be lengthened to a greater value than the previous time interval t<b>1</b>, which started at the previous MS-assisted fix. In this manner, position fix requests to a network, such as location server <b>104</b>, may be reduced by increasing the time interval between consecutive MS-assisted position fixes while time D repeats in response to continued failure of MS-based fixes at time E. After such an increased time interval, an MS-based position fix may again be attempted at time E, and such a process may repeat according to whether the MS-based position fix at time E is successful or not, as described above. This process will be explained in more detail below.

In a particular implementation, a process may be used to successively increase time interval t<b>1</b> for each subsequent MS-assisted position fix. Such a process may include a process of changing time interval t<b>1</b> in an exponential fashion, for example, or by changing t<b>1</b> based upon values and/or other variables of a system that includes an MS and/or a network. Such system variables may include, for example, an amount of network traffic, capacity of network resources, MS user settings, or MS user history stored in a system memory, just to name a few examples. In one particular implementation, time interval t<b>1</b> may be increased, as in the process described above, to a maximum value.

<figref idrefs="DRAWINGS">FIG. 3</figref> is a flow chart showing a process <b>444</b> for reducing a rate of MSA position fixes, according to one implementation. At block <b>450</b>, an MS, such as MS <b>100</b> shown in <figref idrefs="DRAWINGS">FIG. 1</figref>, may be initially configured to operate in a mobile station-based (MSB) position mode. Such a mode, as mentioned above, may include a stand-alone mode, wherein an MS determines its own position without utilizing location server <b>104</b>, for example.

An MS may continue to operate in MSB mode, as at block <b>452</b>, as it successfully receives MSB position fixes. An MS may initiate such position fixes periodically, for example. At block <b>454</b>, a determination is made whether or not the MSB position fix of block <b>452</b> was successful. If so, then an MS may continue to operate in MSB mode, returning to block <b>452</b>, as the process of initiating MSB position fixes repeats. If, however, the MSB position fix of block <b>452</b> was not successful, e.g., because of a change in RF environment, then process <b>444</b> proceeds to block <b>456</b> where the number of consecutive unsuccessful MSB position fixes may be counted up to a number N<b>1</b>. Process <b>444</b> may omit such counting of consecutive unsuccessful MSB position fixes, e.g., N<b>1</b> may equal one. Of course, this is merely an example, and claimed subject matter is not limited by such examples. Returning to explaining block <b>456</b>, if the number of consecutive unsuccessful MSB position fixes is below a number N<b>1</b>, an MS may continue to initiate MSB position fixes as blocks <b>452</b> through <b>456</b> repeat. On the other hand, if the number of consecutive unsuccessful MSB position fixes reaches number N<b>1</b>, which may occur, for example, if an MS operates in an undesirable RF environment for an extended period, process <b>444</b> may proceed to block <b>458</b> where an MS transitions from obtaining position fixes using MSB mode to obtaining position fixes using an MSA mode. In MSA mode, an MS may initiate an MSA position fix in order to acquire a position fix even in the presence of undesirable RF environments. Next, at block <b>460</b>, process <b>444</b> may include a waiting interval of interval t<b>1</b>, which is also shown in <figref idrefs="DRAWINGS">FIG. 2</figref>. During waiting interval t<b>1</b>, no position fixes may be initiated. Accordingly, resources of location server <b>104</b> may not be burdened with MSA position fix requests during interval t<b>1</b>.

At block <b>462</b>, an MS initiates an MSB position fix after interval t<b>1</b> ends. At block <b>464</b>, a determination is made whether or not the MSB position fix of block <b>462</b> was successful, which may indicate a change in RF environment. If so, then an MS may continue to operate in MSB mode, returning to block <b>452</b>, as the process of initiating MSB position fixes repeats. If, however, the MSB position fix of block <b>462</b> was not successful, then process <b>444</b> proceeds to block <b>466</b> where the number of consecutive unsuccessful MSB position fixes may be counted up to a number N<b>2</b>. Process <b>444</b> may omit such counting of consecutive unsuccessful MSB position fixes, e.g., N<b>2</b> may equal one. If the number of consecutive unsuccessful MSB position fixes is below number N<b>2</b>, then an MS may continue to initiate MSB position fixes as blocks <b>462</b> through <b>466</b> repeat. On the other hand, if the number of consecutive unsuccessful MSB position fixes reaches number N<b>2</b>, which may occur, for example, if an MS operates in an undesirable RF environment for an extended interval, then process <b>444</b> may proceed to block <b>468</b> Where an MS transitions from obtaining position fixes using MSB mode to obtaining position fixes using MSA mode. In MSA mode, an MS may initiate an MSA position fix in order to acquire a position fix even during undesirable RF environments. Next, at block <b>470</b>, process <b>444</b> includes a waiting period of interval t<b>1</b>+t<b>2</b>, wherein t<b>2</b> is a time increase above interval t<b>1</b>, which is the first waiting interval, shown at block <b>460</b>. During the waiting interval, no position fixes may be initiated. Accordingly, network resources used in communication with location server <b>104</b> may not be burdened with MSA position fix requests during this interval. In the particular implementation of process <b>444</b>, the increasing nature of the waiting interval, such as interval t<b>1</b> at block <b>460</b> and interval t<b>1</b>+t<b>2</b> at block <b>470</b>, may effectively decrease a rate of MSA position fix requests made to location server, for example.

At block <b>472</b>, an MS initiates an MSB position fix after interval t<b>1</b>+t<b>2</b> ends. At block <b>474</b>, a determination is made as to whether or not the MSB position fix of block <b>472</b> was successful, which may indicate a change in RF environment. If so, then an MS may continue to operate in MSB mode, returning to block <b>452</b>, as the process of initiating MSB position fixes repeats. If, however, the MSB fix of block <b>472</b> was not successful, then process <b>444</b> may proceed to block <b>476</b> where the number of consecutive unsuccessful MSB fixes may be counted up to a number N<b>3</b>. Process <b>444</b> may omit such counting of consecutive unsuccessful MSB position fixes, e.g., N<b>3</b> may equal one. Of course, this is merely an example of a process to determine a change in an RF environment, and claimed subject matter is not limited by such examples. If the number of consecutive unsuccessful MSB fixes is below number N<b>3</b>, then MS <b>100</b> may continue to initiate MSB position fixes as blocks <b>472</b> through <b>476</b> repeat. On the other hand, the number of consecutive unsuccessful MSB position fixes may reach number N<b>3</b>, which may occur, for example, if an MS operates in an undesirable RF environment for an extended interval. In such a case, process <b>444</b> may proceed to block <b>478</b> where an MS transitions from obtaining position fixes using MSB mode to obtaining position fixes using MSA mode. In MSA mode, an MS may initiate an MSA fix in order to acquire a position fix even during undesirable RF environments. Next, at block <b>480</b>, process <b>444</b> includes a waiting interval of time t<b>1</b>+t<b>2</b>+t<b>3</b>, wherein time t<b>3</b> is the time increase above waiting interval t<b>1</b>+t<b>2</b>, which was the previous waiting interval, shown at block <b>470</b>. During the waiting interval, no position fixes may be initiated. Accordingly, resources of location server <b>104</b> may not be burdened with MSA position fix requests during this interval. In the particular implementation of process <b>444</b>, the increasing nature of the waiting interval, such as t<b>1</b> at block <b>460</b>, t<b>1</b>+t<b>2</b> at block <b>470</b>, and t<b>1</b>+t<b>2</b>+t<b>3</b> may effectively decrease the rate of MSA position fix requests made to location server for example.

Process <b>444</b> may continue in a repeating fashion while MSB position fixes remain unsuccessful. For example, each time an MSB position fix fails, or a number of consecutive MSB position fixes fail, as at blocks <b>456</b>, <b>466</b>, and <b>476</b>, process <b>444</b> may include initiating an MSA position fix followed by a waiting interval. Each such waiting interval is lengthened beyond its previous value such that (t<b>1</b>+t<b>2</b>+t<b>3</b>)&gt;(t<b>1</b>+t<b>2</b>) &gt;t<b>1</b>. Lengths of such consecutive waiting intervals may be determined from a look-up table in a memory <b>404</b> (<figref idrefs="DRAWINGS">FIG. 6</figref>), or calculated using an algorithm, just to name a few examples. Such an algorithm may increase each consecutive waiting interval linearly, exponentially, or by any other mathematical relation, for example. Process <b>444</b> may include a maximum length Tmax for the waiting interval, as mentioned above. At blocks <b>459</b>, <b>469</b>, and <b>479</b> in process <b>444</b> may determine whether an algorithm has reached a waiting interval equal to or greater than Tmax, for example. If not, then a waiting interval at blocks <b>460</b>, <b>470</b>, and <b>480</b> may occur. If, however, Tmax has been reached or exceeded, a maximum wait time of Tmax, at block <b>461</b>, <b>471</b>, and <b>481</b> may occur. For example, a maximum waiting interval Tmax may be four times t<b>1</b>. Also, N<b>1</b>, N<b>2</b>, and N<b>3</b> may each be equal to one or greater. In one particular implementation, N<b>1</b>=N<b>2</b>=N<b>3</b>=<b>1</b>, so that an MSA position fix will occur, as at blocks <b>458</b>, <b>468</b>, and <b>478</b>, for example, after only one unsuccessful position fix. Of course, claimed subject matter is not limited to these examples, which are only described here to help illustrate various implementations.

As mentioned above, lengthening waiting intervals before retrying an MSB position fix may reduce a burden on network resources used in communicating with location server <b>104</b> by increasing the time between MSA fixes.

<figref idrefs="DRAWINGS">FIG. 4</figref> is a schematic diagram showing a geofence <b>550</b>, according to an implementation. As mentioned above, the term geofence may refer to demarcation of an area defined by location. In a particular implementation, an MS, such as MS <b>100</b> shown in <figref idrefs="DRAWINGS">FIG. 1</figref>, may operate responsive, at least in part, to its location relative to geofence <b>550</b>. For example, an MS may reduce the rate that it initiates MSA location fixes while operating within geofence <b>550</b>. Accordingly, waiting interval t<b>1</b>, as described in the implementation of <figref idrefs="DRAWINGS">FIG. 2</figref> or process <b>444</b> of <figref idrefs="DRAWINGS">FIG. 3</figref>, may be determined based at least in part on whether an MS is inside or outside geofence <b>550</b>. To describe a specific example, if an MS is outside geofence <b>550</b>, then t<b>1</b> may be <b>30</b> seconds. If an MS is in inside geofence <b>550</b>, then t<b>1</b> may be 45 seconds. Such a longer t<b>1</b> inside geofence <b>550</b> may reflect the fact that less frequent position fixes may be acceptable while an MS is within a known location, i.e., geofence <b>550</b>. In other words, the location of geofence <b>550</b> may provide information regarding the location of an MS if it is within geofence <b>550</b>. For example, geofence <b>550</b> may define an area inside a large shopping mall, which may be an area where one would expect an MS to travel at or below walking speed. Such an MS may include a cell phone or a PDA in a walking shopper's pocket, for example. In contrast, an MS may travel at highway speeds, in this example, outside geofence <b>550</b>, where an MS may include a cell phone or a PDA in an automobile. Accordingly, within geofence <b>550</b>, an MS may travel a relatively short distance during waiting interval t<b>1</b> compared to travel distance outside of geofence <b>550</b>, where higher speed may occur. Therefore, in a particular implementation, for a given location uncertainty, waiting interval t<b>1</b> may be longer if an MS is within geofence <b>550</b> than if an MS is outside geofence <b>550</b>. As mentioned above, a longer waiting interval t<b>1</b> implies a reduced rate of MSA location fixes and a reduced burden on network resources used in communicating with a location server, for example.

<figref idrefs="DRAWINGS">FIG. 5</figref> is a schematic diagram showing an MS trajectory <b>620</b> through varying RF environments, according to one implementation. Boundary <b>650</b> between region <b>610</b> and region <b>630</b> may represent a transition from a first RF environment to a second RF environment. For example, region <b>610</b> may include a desirable RF environment enabling an MS, such as MS <b>100</b> shown in <figref idrefs="DRAWINGS">FIG. 1</figref>, to attain MSB position fixes because a sufficient number of SPS satellites may be “in view” of the MS. In contrast, region <b>630</b> may include an undesirable RF environment that prevents an MS from attaining MSB position fixes. Such an undesirable RF environment may occur indoors or in an urban canyon, for example.

In the implementation of <figref idrefs="DRAWINGS">FIG. 5</figref>, an MS may engage in MSB position fixes, as at block <b>452</b> of <figref idrefs="DRAWINGS">FIG. 3</figref>, for example, as it travels through points P<b>1</b>, P<b>2</b>, P<b>3</b>, and so on along route <b>620</b> in region <b>610</b>, which allows such MSB fixes. At each point, an MS may determine, as at block <b>454</b>, whether the MSB position fix at that point was successful. Such success is assumed in the implementation of <figref idrefs="DRAWINGS">FIG. 5</figref> in region <b>610</b>. Accordingly, an MS may continue to operate in MSB mode. But at point P<b>4</b> along route <b>620</b>, an MS has traveled into region <b>630</b> having an RF environment that prevents successful MSB fixes. Accordingly, an MS may attempt and fail to attain MSB position fixes N<b>1</b> times, as at block <b>456</b> of <figref idrefs="DRAWINGS">FIG. 3</figref>. After such failure, an MS may transition from MSB mode to MSA mode at point P<b>5</b> along route <b>620</b>. In MSA mode, an MS may attain an MSA position fix, perhaps utilizing a location server <b>104</b>, for example.

An MS may travel from point P<b>5</b> to point P<b>6</b> during a waiting interval t<b>1</b>, as at block <b>460</b>, for example. At point P<b>6</b>, an MS may attempt an MSB position fix. Since an MS is still in region <b>630</b> having an undesirable RF environment, this MSB position fix will fail, in this particular example. Accordingly, an MS may initiate an MSA position fix, after which a waiting interval may occur, which will be lengthened compared to the previous waiting interval. Such a lengthened waiting interval may be indicated at block <b>470</b> of <figref idrefs="DRAWINGS">FIG. 3</figref>, for example. After this longer waiting interval, during which an MS travels from point P<b>6</b> to point P<b>7</b>, another attempt may be made at acquiring an MSB position fix. As in the previous attempt at point P<b>6</b>, an MS may attempt an MSB position fix at point P<b>7</b>. Since an MS is still in region <b>630</b> having an undesirable RF environment, this MSB position fix will fail, in this particular example. Accordingly, an MS may initiate an MSA position fix, after which a waiting interval may occur, which will be lengthened compared to the previous waiting interval. Such a lengthened waiting interval may be indicated at block <b>480</b> of <figref idrefs="DRAWINGS">FIG. 3</figref>, for example. After this longer waiting interval, during which an MS travels from point P<b>7</b> to point P<b>8</b>, another attempt is made at acquiring an MSB position fix. During the latest waiting interval, an MS traveled into region <b>610</b> having a desirable RF environment. Accordingly, the attempt at acquiring an MSB position fix at point P<b>8</b> may be successful. With this success, an MS may transition from MSA mode to MSB mode at point P<b>8</b>. In MSB mode, an MS may attain MSB position fixes while in region <b>610</b>, for example.

<figref idrefs="DRAWINGS">FIG. 6</figref> is a schematic diagram of a device capable of communication with a wireless network, according to one implementation. In a particular implementation, an MS, such as MS <b>100</b> shown in <figref idrefs="DRAWINGS">FIG. 1</figref>, may comprise a device <b>400</b> as shown in <figref idrefs="DRAWINGS">FIG. 6</figref>, which is capable of processing SPS signals received at an antenna <b>414</b> for determining pseudorange measurements and communicating with a wireless communication network through antenna <b>410</b>. Here, a radio transceiver <b>406</b> may be adapted to modulate an RF carrier signal with baseband information, such as data, voice and/or SMS messages, onto an RF carrier, and demodulate a modulated RF carrier to obtain such baseband information. Antenna <b>410</b> may be adapted to transmit a modulated RF carrier over a wireless communications link and receive a modulated RF carrier over a wireless communications link.

Baseband processor <b>408</b> may be adapted to provide baseband information from central processing unit (CPU) <b>402</b> to transceiver <b>406</b> for transmission over a wireless communications link. Here, CPU <b>402</b> may obtain such baseband information from a local interface <b>416</b> which may include, for example, environmental sensory data, motion sensor data, altitude data, acceleration information (e.g., from an accelerometer), proximity to other networks (e.g., ZigBee, Bluetooth, WiFi, peer-to-peer). Such baseband information may also include position information such as, for example, an estimate of a position of device <b>400</b> and/or information that may be used in computing same such as, for example, pseudorange measurements.

SPS receiver (SPS Rx) <b>412</b> may be adapted to receive and demodulate transmissions from SVs, and provide demodulated information to correlator <b>418</b>. Correlator <b>418</b> may be adapted to derive correlation functions from the information provided by SPS receiver <b>412</b>. Correlator <b>418</b> may also be adapted to derived pilot-related correlation functions from information relating to pilot signals provided by transceiver <b>406</b>. This information may be used by device acquire a wireless communications network.

Channel decoder <b>420</b> may be adapted to decode channel symbols received from baseband processor <b>408</b> into underlying source bits. In one example where channel symbols comprise convolutionally encoded symbols, such a channel decoder may comprise a Viterbi decoder. In a second example, where channel symbols comprise serial or parallel concatenations of convolutional codes, channel decoder <b>420</b> may comprise a turbo decoder.

Memory <b>404</b> may be adapted to store machine-readable instructions which are executable to perform one or more of processes, examples, implementations, or examples thereof which have been described or suggested. CPU <b>402</b> may be adapted to access and execute such machine-readable instructions. However, these are merely examples of tasks that may be performed by a CPU in a particular aspect and claimed subject matter is not limited in these respects.

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. 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.