Patent Application
20180324616
Various embodiments described herein generally relate to position sensors, and more particularly to generation of location data while conserving resources.
Communications networks offer increasingly sophisticated capabilities associated with the motion and/or position location sensing of a mobile device. New software applications, such as, for example, those related to personal productivity, collaborative communications, social networking, and/or data acquisition, may utilize motion and/or position sensors to provide new features and services to consumers. Moreover, some regulatory requirements of various jurisdictions may require a network operator to report the location of a mobile device when the mobile device places a call to an emergency service, such as a “911” call in the United States.
Such motion and/or position determination capabilities have conventionally been provided using Satellite Positioning Systems (SPS). SPS wireless technologies which may include, for example, the Global Positioning System (GPS) and/or a Global Navigation Satellite System (GNSS). A mobile device supporting SPS may obtain positioning signals as wireless transmissions received from one or more satellites equipped with transmitting devices. The positioning signal may be used to generate SPS-based location data.
The mobile device may also be associated with one or more terrestrial networks. For example, the one or more terrestrial networks may conform to specifications such as Long-Term Evolution (LTE) (provided by the Third Generation Partnership Project (3GPP)), Ultra Mobile Broadband (UMB) and Evolution Data Optimized (EV-DO) (provided by the Third Generation Partnership Project 2 (3GPP2)), 802.11 (provided by the Institute of Electrical and Electronics Engineers (IEEE)), etc. As terrestrial networks become more sophisticated, they may use the SPS-based location data generated by the mobile device to better serve the mobile device. For example, the terrestrial network may use the generated SPS-based location data to estimate a geographic position and heading of the mobile device, and allocate resources or prepare for a handover based on the estimate.
For the foregoing reasons, the terrestrial network may occasionally request a position report from the mobile device. However, the reporting tasks performed by the mobile device can be costly. For example, the mobile device may consume large amounts of resources in a scenario where the SPS-based location data can not be obtained readily or accurately. Accordingly, new techniques are needed for conserving resources when generating location data.
The following summary is an overview provided solely to aid in the description of various aspects of the disclosure and is provided solely for illustration of the aspects and not limitation thereof.
In one example, an apparatus is disclosed. The apparatus, the apparatus may include, for example, a wireless transceiver configured to transmit and receive wireless signals, a satellite positioning service (SPS) receiver configured to receive SPS signals, memory, and a processor coupled to the wireless transceiver, the SPS receiver, and the memory. One or more of the processor and the memory may be configured to generate SPS-based location data using the SPS receiver in response to receipt of a minimization of drive test (MDT) measurement request, determine whether the SPS-based location data is accurate or not accurate, in response to a determination that the SPS-based location data is not accurate, generate network-based location data using the wireless transceiver and include the network-based location data in an MDT report, in response to a determination that the SPS-based location data is accurate, include the SPS-based location data in the MDT report, and transmit the MDT report, wherein the MDT report includes one or both of the SPS-based location data and/or the network-based location data.
In another example, a method is disclosed. The method may include, for example, generating SPS-based location data using the SPS receiver in response to receipt of a minimization of drive test (MDT) measurement request, determining that the SPS-based location data is not accurate, in response to the determination that the SPS-based location data is not accurate, generating network-based location data using the wireless transceiver and including the network-based location data in an MDT report, in response to a determination that the SPS-based location data is accurate, including the SPS-based location data in the MDT report, and transmitting the MDT report, wherein the MDT report includes one or both of the SPS-based location data and/or the network-based location data.
In yet another example, an apparatus is disclosed. The apparatus, the apparatus may include, for example, a wireless transceiver configured to transmit and receive wireless signals, a satellite positioning service (SPS) receiver configured to receive SPS signals, memory, and a processor coupled to the wireless transceiver, the SPS receiver, and the memory. One or more of the processor and the memory is configured to generate first SPS-based location data using received SPS signals, determine that the first SPS-based location data is not accurate, in response to the determination that the first SPS-based location data is not accurate, record accuracy factor data relating to one or more accuracy factors, determine whether to generate second SPS-based location data based on whether the recorded accuracy factor data indicates that the second SPS-based location data will be accurate, and in response to a determination to generate second SPS-based location data, generate the second SPS-based location data.
In yet another example, a method is disclosed. The method may include, for example, generating first SPS-based location data using a satellite positioning service (SPS), determining that the first SPS-based location data is not accurate, in response to the determination that the first SPS-based location data is not accurate, recording accuracy factor data relating to one or more accuracy factors, determining whether to generate second SPS-based location data based on whether the recorded accuracy factor data indicates that the second SPS-based location data will be accurate, in response to a determination to generate second SPS-based location data, generating the second SPS-based location data.
The accompanying drawings are presented to aid in the description of various aspects of the disclosure and are provided solely for illustration of the aspects and not limitation thereof.
Various aspects are disclosed in the following description and related drawings. Alternate aspects may be devised without departing from the scope of the disclosure. Additionally, well-known elements of the disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of the disclosure. The words “exemplary” and/or “example” are used herein to mean “serving as an example, instance, or illustration”. Any aspect described herein as “exemplary” and/or “example” is not necessarily to be construed as preferred or advantageous over other aspects. Likewise, the term “aspects of the disclosure” does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation.
The terminology used herein is for the purpose of describing particular embodiments only and not to limit any embodiments disclosed herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “includes” and/or “including”, when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
Further, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be recognized that various actions described herein can be performed by specific circuits (e.g., an application specific integrated circuit (ASIC)), by program instructions being executed by one or more processors, or by a combination of both. Additionally, these sequence of actions described herein can be considered to be embodied entirely within any form of non-transitory computer-readable storage medium having stored therein a corresponding set of computer instructions that upon execution would cause or instruct an associated processor to perform the functionality described herein, such as, for example, the functionality associated with any of
As depicted in
In a SPS, a system of transmitting devices (depicted as transmitting devices 120, 130, 140) enable devices such as the mobile device 110 to sense a position on or above the earth based, at least in part, on signals received from transmitting devices analogous to the transmitting devices 120, 130, 140. The transmitting devices 120, 130, 140 may transmit a signal that includes a code, for example, a repeating pseudo-random noise (PRN) code. The transmitting devices 120, 130, 140 may be located on ground-based control stations, user equipment and/or space vehicles. In some implementations, the transmitting devices 120, 130, 140 may be located on Earth-orbiting satellite vehicles (SVs). For example, a SV 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 particular code that is distinguishable from codes transmitted by other SVs in the constellation (e.g., using different codes for each satellite as in GPS or using the same code on different frequencies as in Glonass). In accordance with certain aspects, the techniques presented herein are not restricted to global systems (e.g., GNSS) for SPS. For example, the techniques provided herein may be applied to or otherwise enabled for use in various regional systems, such as, e.g., Quasi-Zenith Satellite System (QZSS) over Japan, Indian Regional Navigational Satellite System (IRNSS) over India, Beidou over China, etc., and/or various augmentation systems (e.g., an Satellite Based Augmentation System (SBAS)) that may be associated with or otherwise enabled for use with one or more global and/or regional navigation satellite systems. By way of example but not limitation, an SBAS may include an augmentation system(s) that provides integrity information, differential corrections, etc., such as, e.g., Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multi-functional Satellite Augmentation System (MSAS), GPS Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN), and/or the like. Thus, as used herein an SPS may include any combination of one or more global and/or regional navigation satellite systems and/or augmentation systems, and SPS signals may include SPS, SPS-like, and/or other positioning signals associated with such one or more SPS.
The position sensing environment 100 depicted in
Additionally or alternatively, the positioning signal 141 may be reflected off the one or more intervening structures, resulting in a reflected positioning signal 143. Because the positioning signal 141 reaches the mobile device 110 indirectly, it may not facilitate position sensing. As will be discussed in greater detail below, the mobile device 110 may sense position based on estimated times of flight (TOF) associated with the positioning signals 121, 131, 141. Because the positioning signal 141 is reflected and received as the reflected positioning signal 143, the path of the positioning signal 141 is lengthened. Accordingly, the TOF estimated by the mobile device 110 may also be lengthened. As a result, the reflected positioning signal 143 received by the mobile device 110 may cause an inaccurate estimation of the distance between the transmitting device 140 and the mobile device 110. The position sensing capability of the 110 may therefore be degraded.
It will be understood that in some scenarios, a direct line of sight to the transmitting devices 120, 130, 140 may not be reliably obtained. Accordingly, if one or more terrestrial networks associated with the mobile device 110 requests a location report, the mobile device 110 may not be able to perform accurate measurements. As a result, the efficiency of the one or more terrestrial networks may be reduced.
The processor 210 may include one or more microprocessors, microcontrollers, and/or digital signal processors that provide processing functions, as well as other calculation and control functionality. The memory 220 may be configured to store data and/or instructions for executing programmed functionality within the mobile device 200. The memory 220 may include on-board memory that is, for example, in a same integrated circuit package as the processor 210. Additionally or alternatively, memory 220 may be external to the processor 210 and functionally coupled over the common bus 201.
The SPS receiver 230 may be configured to receive one or more positioning signals 231 from a transmitting device, for example, a transmitting device analogous to the transmitting devices 120, 130, 140 depicted in
The SPS receiver 230 may further comprise any suitable hardware and/or software for receiving, processing, and/or storing the received positioning signals, as will be discussed in greater detail below by reference to
The wireless transceiver 240 may be configured to send and receive various signals in accordance with one or more terrestrial networks, for example, an LTE network, a UMB network, an EV-DO network, an 802.11 network, etc. The wireless transceiver 240 may be configured to receive report requests from the one or more terrestrial networks, for example, MDT measurement requests (wherein the abbreviation MDT stands for Minimization of Drive Test). In response to a received MDT measurement request, the mobile device 200 may be configured to generate location data and report the generated location data to a location server.
The location server may be associated with one or more of the one or more terrestrial networks. The wireless transceiver 240 may be further configured to transmit the requested report, including the location data, to the location server. As noted above, the location data may include SPS-based location data generated by the mobile device 200 using the SPS receiver 230. Additionally or alternatively, the location data may include network-based location data generated by the mobile device 200 using the wireless transceiver 240. In order to generate the network-based location data, the mobile device 200 may be configured to receive network-based location signals, for example, signals associated with an Enhanced Cell ID (E-CID) positioning method, Position Reference Signals (PRS), or any combination thereof. Using the received network-based location signals, the mobile device 200 may be configured to generate the network-based location data.
The interface 280 may be used to provide interface data 281 of the mobile device 200 to an external entity. For example, the interface 280 may comprise a user interface and the interface data 281 may include audio output, visual output, tactile output, or any other output suitable for a user of the mobile device 200 (for example, a screen, a speaker, etc.). Additionally or alternatively, the interface data 281 may include audio input, visual input, tactile input, or any other suitable input from a user of the mobile device 200 (for example, from a microphone, a touch screen, a keyboard, a button, etc.). Additionally or alternatively, the interface 280 may comprise an electrical coupling and the interface data 281 may include one or more signals (for example, a sensed position of the mobile device 200) to another device (for example, an external user interface, a vehicle, etc.). Additionally or alternatively, the interface 280 may comprise a transceiver and the interface data 281 may include one or more transmitted signals (for example, a sensed position of the mobile device 200).
The other components 290 may include, for example, wide area network transceivers, local area network transceivers, or any other components suitable for inclusion in a mobile device such as the mobile device 200. It will be understood that the mobile device 200 may be a music player, a video player, an entertainment unit, a navigation device, a communications device, a mobile device, a mobile phone, a smartphone, a personal digital assistant, a fixed location terminal, a tablet computer, a computer, a wearable device, an Internet of things (IoT) device, a laptop computer, a server, a device in a automotive vehicle, and/or any other device with a need for position sensing capability. As such, the mobile device 200 may include any number of other components 290.
The processor 310 and the memory 320 may be analogous in some respects to the processor 210 and the memory 220 described above. The processor 310 and/or memory 320 may be configured to process and/or store the signals received by the antenna 330. The processor 310 and/or memory 320 may be further configured to generate position data 381 indicating a position of the SPS receiver 230. The position data 381 may be provided by the processor 310 and/or memory 320 to the interface 380. The interface 380 may be used to provide the position data 381 to an external entity, for example, the common bus 201 of the mobile device 200.
The antenna 330 may be configured to receive one or more positioning signals 231. In some implementations, the antenna 330 may include a plurality of antennas, for example, one or more main antennas and/or one or more reference antennas. However, for simplicity of illustration, the one or more antennas included in the SPS receiver 230 will be referred to in the singular as the antenna 330. The one or more positioning signals 231 may be analogous to the positioning signals 121, 131, 141 depicted in
In some implementations, the one or more positioning signals 231 may include a pseudo-random noise (PRN) code. Each transmitting device may be associated with a unique and/or specific code. The memory 320 may store a plurality of replica codes and the identity and/or position of a specific transmitting device to which each of the replica codes corresponds. For example, “CODE120” may correspond to the transmitting device 120 depicted in
The receiver clock 350 may be configured to keep time. The receiver clock 350 may be synchronized with a transmitter clock incorporated into the transmitting device 120. In some implementations, each of the transmitting devices 120, 130, 140 may be equipped with a high-precision transmitter clock, for example, an atomic clock. The transmitter clocks in each of the transmitting devices 120, 130, 140 may be synchronized with one another.
The start time tT for the transmission of a particular code may be predetermined and known to, for example, the SPS receiver 230. Moreover, the receiver clock 350 may be configured to determine a time tR at which a particular code, for example, the CODE120, is received. Accordingly, the delay tTOF caused by the time of flight of the positioning signal 121 from the transmitting device 120 to the antenna 330 may be determined based on the predetermined transmission time tT and the receiving time tR. In particular, the delay tTOF may be equal to tR−tT.
For example, “CODE120” may have a 1.00 ms duration and may be transmitted at 1.00 ms intervals beginning at a transmission start time t0. Accordingly, “CODE120” will be transmitted at a plurality of transmitting times tT, wherein tT=t0+N*(1.00 ms), N being an integer. As noted above, the transmission start time t0 may be scheduled or predetermined such that it is known in advance by both the transmitting device 120 and the SPS receiver 230.
The one or more positioning signals 231 may travel from the transmitting device to the antenna 330 at the speed of light and may reach the antenna 330 after a delay tTOF caused by the time of flight. For example, suppose that CODE120 is transmitted at a predetermined transmitting time tT=1.00 ms, and that the receiver clock 350 determines that the code is received at receiving time tR=1.20 ms. The SPS receiver 230 may therefore conclude that the delay tTOF is equal to 0.20 ms. Because the speed of light is ˜300 km/ms, a delay tTOF equal to 0.20 ms would indicate a distance of ˜60 km. The estimated distance may be referred to as a “range estimate”, a “pseudorange”, and/or a “code-phase measurement”. It will be understood that this is a simplified description of how the SPS receiver 230 estimates a code-phase measurement, and that other factors affecting the estimating of the code-phase measurement have been omitted for brevity.
As noted above, each transmitting device may be associated with a different PRN code. Accordingly, the SPS receiver 230 may perform a plurality of code-phase measurements based on a plurality positioning signal analogous to the one or more positioning signals 231. Each code-phase measurement may correspond to a different transmitting device. After, for example, three or more code-phase measurements are performed, the position of the SPS receiver 230 can be calculated using triangulation based on the known positions of the three or more corresponding transmitting devices. In some implementations, code-phase measurements may be used to sense a position of the SPS receiver 230 with precision on the order of several meters.
The SPS receiver 230 can achieve greater precision using carrier-phase measurements. As noted above, each of the one or more positioning signals 231 may include a repeating PRN code used for generating code-phase measurements. However, the code cycle may have a first frequency and may be carried on a carrier wave having a second frequency that is significantly greater than the first frequency. Because the frequency of the carrier wave is greater than the frequency of the code cycle, position sensing that is based on carrier-phase measurements may be more precise than position sensing based on code-phase measurements. For example, if the delay tTOF can be determined using the carrier wave, then the SPS receiver 230 may be able to sense position with precision on the order of tens of centimeters.
At 410, the method 400 receives a MDT measurement request. The MDT measurement request may be received from, for example, a terrestrial network with which the mobile device 200 is associated. The receiving 410 may be performed by, for example, the wireless transceiver 240 depicted in
At 420, the method 400 generates SPS-based location data using received SPS signals, such as the one or more positioning signals 231. The SPS-based location data may be, for example, first SPS-based location data. The generating 420 may be performed by, for example, the SPS receiver 230. Accordingly, the SPS receiver 230 may constitute means for generating SPS-based location data.
At 430, the method 400 determines whether the SPS-based location data is accurate or not accurate. The accuracy determining 430 may be performed by, for example, the processor 210 and/or the memory 220 depicted in
The accuracy determining 430 may be performed in any suitable manner In some implementations, the mobile device 200 may count the number of available transmitting devices, (for example, satellites) and determine if the count exceeds a threshold. If the count exceeds the threshold, then the mobile device 200 may determine that the SPS-based location data is accurate. If the count does not exceed the threshold, then the mobile device 200 may determine that the SPS-based location data is not accurate.
In other implementations, the mobile device 200 may estimate a signal characteristic of the SPS signals from the available satellites, for example, signal to noise ratio (SNR) and determine if the SNR values or an average thereof exceed a threshold. If the SNR exceeds the threshold, then the mobile device 200 may determine that the SPS-based location data is accurate. If the SNR does not exceed the threshold, then the mobile device 200 may determine that the SPS-based location data is not accurate.
In other implementations, the mobile device 200 may estimate an SPS fix value and determine if the fix value associated with the generated SPS-based location data exceeds a threshold. If the SPS fix value does not exceed the threshold, then the mobile device 200 may determine that the SPS-based location data is accurate. If the SPS fix value does exceed the threshold, then the mobile device 200 may determine that the SPS-based location data is not accurate.
In other implementations, the mobile device 200 may estimate dilution of precision values and determine if the dilution of precision estimate exceeds a threshold. If the dilution of precision estimate does not exceed the threshold, then the mobile device 200 may determine that the SPS-based location data is accurate. If the dilution of precision estimate does exceed the threshold, then the mobile device 200 may determine that the SPS-based location data is not accurate. Dilution of precision is a relation between a change in measured data versus a change in output location. In geometric dilution of precision (GDOP) techniques, satellites in divergent areas of the sky offer comparatively more precise results and less dilution of precision than satellites that are clustered more closely together. Other techniques such as horizontal dilution of precision (HDOP), vertical dilution of precision (DOP), position dilution of precision (PDOP) and time dilution of precision (TDOP) are available.
The accuracy determining 430 (which implies SPS-based location data generation 420) may be repeated such that the accuracy determining 430 is performed multiple times (not shown in
Alternatively, the mobile device 200 may only proceed to 450 in response to multiple determinations that the SPS-based location data is not accurate, for example, multiple consecutive determinations. As an example, the mobile device 200 may not proceed to 450 until the generating 420 has been performed X number of times and/or determined at 430 to be inaccurate X number of times.
At 440, the method 400 transmits accurate location data to a location server. The transmitting 440 may be performed by, for example, the wireless transceiver 240 depicted in
A conventional MDT report may include data such as a timestamp and location information. The location information may be provided as, for example, an octet identifying a set of coordinates, for example, an ellipsoid point and/or altitude. The conventional MDT report may further include a horizontal velocity. However, if a fix for the SPS-based location data is not available, the location information provided in the MDT report may be empty or null.
An MDT report in accordance with aspects of the disclosure, for example, an MDT report being transmitted at 440, may include location data even if a fix for the SPS-based location data is not available. For example, the MDT report transmitted at 440 may include a timestamp and, for example, an enhanced cell identifier (E-CID) measurement result and/or a transmission/reception time difference result.
At 450, the method 400 powers down the SPS receiver. For example, the mobile device 200 may terminate the generating 420 described above. The powering down 450 may be performed by, for example, the processor 210 and/or memory 220 depicted in
At 452, the method 400 starts a backoff timer. The backoff timer may begin at a backoff timer start value. The backoff timer value may indicate the length of a period during which the mobile device 200 generates network-based location data, as will be discussed in greater detail below. If no backoff timer value has been set, then a default backoff timer start value maybe set. The starting 452 may be performed by, for example, the processor 210 and/or the memory 220 depicted in
At 460, the method 400 generates network-based location data. The generating 460 may be performed by, for example, the wireless transceiver 240 depicted in
At 470, the method 400 determines if the network-based location data generated at 460 is accurate or not accurate. The accuracy determining 470 may be performed by, for example, the processor 210 and/or the memory 220 depicted in
At 480, the method 400 determines if the backoff timer has expired. The timer expiration determining 480 may be performed by, for example, the processor 210 and/or the memory 220 depicted in
At 490, the method 400 increment the backoff timer value. The incrementing 490 may be performed by, for example, the processor 210 and/or the memory 220 depicted in
At 510, the method 500 receives a MDT measurement request. The MDT measurement request may be received from, for example, a terrestrial network with which the mobile device 200 is associated. The receiving 510 may be performed by, for example, the wireless transceiver 240 depicted in
At 520, the method 500 determines whether to generate SPS-based location data. The determination may be based on one or more accuracy factors, for example, one or more previously-recorded accuracy factors analogous to the accuracy factors described in greater detail below (block 570). If it is determined not to generate SPS-based location data (‘no’ at block 520), then the method 500 proceeds to 530. If it is determined to generate SPS-based location data (‘yes’ at block 520), then the method 500 proceeds to 540. The determining 520 may be performed by, for example, the processor 210 and/or the memory 220 depicted in
At 530, the method 500 ends. By ending the method 500 prior to generation of SPS-based location data, the mobile device 200 may be able to conserve resources, as will be discussed in greater detail below.
At 540, the method 500 generates SPS-based location data. The generating 540 may be performed by, for example, the SPS receiver 230 depicted in
At 550, the method 500 determines if the SPS-based location data is accurate. The determining 550 may be performed by, for example, the processor 210 and/or the memory 220 depicted in
At 560, the method 500 transmits accurate location data to a location server. The transmitting 560 may be performed by, for example, the wireless transceiver 240 depicted in
At 570, the method 500 records accuracy factor data. The recording 570 may be performed by, for example, the processor 210 and/or the memory 220 depicted in
The one or more accuracy factors may include, for example, an accuracy value associated with the SPS-based location data, a distance from a particular wireless access point at the time of the generating of the first SPS-based location data, a density of wireless access points in a surrounding area at the time of the generating of the first SPS-based location data, geofence data associated with the surrounding area at the time of the generating of the first SPS-based location data, or any combination thereof. By recording the one or more accuracy factors over time, the mobile device 200 may be able to identify a correlation between the accuracy of the SPS-based location data and the one or more accuracy factors.
In some implementations, the distance from a particular wireless access point (for example, a familiar private Wi-Fi router) may correlate with inaccurate SPS signals. For example, the processor 210 and/or memory 220 may determine that at times when the particular wireless access point is in range of the mobile device 200, SPS signals are inaccurate. This may be because, for example, the wireless access point is located deep indoors. The processor 210 and/or memory 220 may record data resulting from the accuracy determining 550 and may further record whether a certain access point is present (and/or a distance thereto) at the time that the SPS-based location data was generated. It will be understood that over time, the processor 210 and/or memory 220 may be configured to detect a correlation between the presence/absence of a particular access point and the accuracy/inaccuracy of SPS range estimates. Once the correlation is established, the mobile device 200 may infer that the SPS range estimates are inaccurate based on detection of the presence of the particular access point.
Geofence data, which indicates that the mobile device 200 is within a certain area (based on, for example, radio frequency identification (RFID) technology), may be used in the same manner Over time, the processor 210 and/or memory 220 may be configured to detect a correlation between a particular geofenced location and the accuracy/inaccuracy of SPS range estimates. Once the correlation is established, the mobile device 200 may infer that the SPS range estimates are inaccurate based on detection of the presence of the particular geofenced location.
The density of wireless access points may also correlate with inaccurate SPS signals. For example, an office building might have a dozen access points, all of which may be in range of the mobile device 200 at a particular time. The mobile device 200 may infer that the SPS range estimates are unlikely to be accurate based on the simultaneous detection of a certain number of wireless access points.
At 610, the method 600 generates SPS-based location data using the SPS receiver in response to receipt of a minimization of drive test (MDT) measurement request. The generating 610 may be performed by, for example, the SPS receiver 230 depicted in
At 620, the method 600 determines whether the SPS-based location data generated at 610 is accurate or not accurate. The determining 620 may be performed by, for example, the processor 210 and/or memory 220 depicted in
At 630, the method 600 generates network-based location data using the wireless transceiver and include the network-based location data in an MDT report in response to a determination that the SPS-based location data is not accurate. The generating 630 may be performed by, for example, the processor 210 and/or memory 220 depicted in
At 640, the method 600 includes the SPS-based location data in the MDT report in response to a determination that the SPS-based location data is accurate. The including 640 may be performed by, for example, the processor 210 and/or memory 220 depicted in
At 650, the method 600 transmits the MDT report, wherein the MDT report includes one or both of the SPS-based location data and/or the network-based location data. The transmitting 650 may be performed by, for example, the wireless transceiver 240 depicted in
At 710, the method 700 generates first SPS-based location data using a satellite positioning service (SPS). The generating 710 may be performed by, for example, the SPS receiver 230 depicted in
At 720, the method 700 determines that the first SPS-based location data is not accurate. The determining 720 may be performed by, for example, the processor 210 and/or memory 220 depicted in
At 730, the method 700 records accuracy factor data relating to one or more accuracy factors in response to the determination that the first SPS-based location data is not accurate. The recording 730 may be performed by, for example, the processor 210 and/or memory 220 depicted in
At 740, the method 700 determines whether to generate second SPS-based location data based on whether the recorded accuracy factor data indicates that the second SPS-based location data will be accurate. The determining 740 may be performed by, for example, the processor 210 and/or memory 220 depicted in
At 750, the method 700 generates the second SPS-based location data in response to a determination to generate second SPS-based location data. The generating 750 may be performed by, for example, the wireless transceiver 240 depicted in
Those of skill in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
Further, those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted to depart from the scope of the present disclosure.
The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an ASIC, an field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).
The methods, sequences and/or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in an IoT device. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.
In one or more exemplary aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes CD, laser disc, optical disc, DVD, floppy disk and Blu-ray disc where disks usually reproduce data magnetically and/or optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
While the foregoing disclosure shows illustrative aspects of the disclosure, it should be noted that various changes and modifications could be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the aspects of the disclosure described herein need not be performed in any particular order. Furthermore, although elements of the disclosure may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.
