Patent Application
20110148700
Certain embodiments of the invention relate to signal processing for satellite navigation systems. More specifically, certain embodiments of the invention relate to a method and system for mobile device based GNSS position computation without ephemeris data.
Location based services (LBS) are emerging as a new type of value-added service provided by mobile communication network. LBS are mobile services in which the user location information is used in order to enable various LBS applications such as, for example, enhanced 911 (E-911) services. A position of a mobile device is determined in different ways such as, for example, using network-based technology, using terminal-based technology, and/or hybrid technology (a combination of the former technologies). Many positioning technologies such as, for example, Cell of Origin (COO), Time of Arrival (TOA), Observed Time Difference of Arrival (OTDOA), Enhanced Observed Time Difference (E-OTD) as well as the Global navigation satellite-based systems (GNSS) such as GPS, GLONASS, Galileo, and/or Assisted-GNSS (A-GNSS), are in place to estimate the position (latitude and longitude) of the mobile device and convert it into a meaningful X, Y coordinate for LBS applications. A-GNSS technology combines satellite positioning and communication networks such as mobile networks to reach performance levels allowing the wide deployment of Location-Based Services. The A-GNSS technology uses assistance data provided from an A-GNSS server via, for example, a mobile telephony network, to speed up the process of acquiring a position of a GNSS-enabled mobile device especially in a weak signal environment. The A-GNSS server has access to a reference network of GNSS receivers that are placed in ideal locations (direct line-of-sight to satellites). The reference network may be used as a source for providing the assistance data, which comprise an ephemeris model (ephemeris data). The ephemeris data may be valid only for the visibility period of each detected satellite, which may be approximately 4 hours assuming that the receiver is static and the satellite is just rising above the horizon.
Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of skill in the art, through comparison of such systems with some aspects of the present invention as set forth in the remainder of the present application with reference to the drawings.
A method and/or system for mobile device based GNSS position computation without ephemeris data, substantially as shown in and/or described in connection with at least one of the figures, as set forth more completely in the claims.
These and other advantages, aspects and novel features of the present invention, as well as details of an illustrated embodiment thereof, will be more fully understood from the following description and drawings.
Certain embodiments of the invention may be found in a method and system for mobile device based GNSS position computation without ephemeris data. Various aspects of the invention may comprise a GNSS enabled mobile device that is operable to receive GNSS assistance data comprising acquisition assistance data, from an A-GNSS server. Acquisition assistance data may comprise range and range rate information with associated uncertainties. Range and range rate information may be communicated in code phase and/or Doppler fields of the acquisition assistance data. Acquisition assistance data may also comprise expected code delay, azimuth and/or elevation information for each GNSS satellite in view. The GNSS enabled mobile device may be operable to utilize the received acquisition assistance data to acquire satellite signals faster. A relative GNSS position for the GNSS enabled mobile device is calculated utilizing acquisition assistance data in the received GNSS assistance data and a local code delay measurement for at least one GNSS satellite. The received GNSS assistance data does not comprise ephemeris data, but instead, may comprise an initial or approximate position for the GNSS enabled mobile device, an approximate time, extra resolution, for example, better than one GNSS chip, on the code phase, expected code delay, acquisition assistance data associated with the approximate position and time as well as satellite almanac data, and/or azimuth and elevation fields for the at least one GNSS satellite. Azimuth and elevation fields may be used to calculate unit vectors, namely, line-of-sight vectors, in the direction of the at least one GNSS satellite for the GNSS position calculation. The A-GNSS server is operable to identify an approximate position for the GNSS enabled mobile device. The A-GNSS server is operable to calculate acquisition assistance data at current time instant and/or one or more future time instants for the identified approximate position. In instances where the received GNSS assistance data does not comprise the azimuth and elevation fields for each of the GNSS satellites in view, the GNSS enabled mobile device is operable to calculate unit vectors in the direction of each GNSS satellite utilizing an approximate time, an almanac and/or an approximate position in the received GNSS assistance data. Azimuth and elevation fields for each GNSS satellite in view may be calculated utilizing the almanac and approximate position in the received GNSS assistance data so as to compute the unit vectors in the direction of each GNSS satellite. The GNSS enabled mobile device is operable to generate local GNSS measurements for each GNSS satellite in view to be used, together with the acquisition assistance data, and the azimuth and elevation fields for each GNSS satellite in view, for calculating the relative GNSS position with respect to the approximate position. In instances where the received GNSS assistance data comprises the approximate position for the GNSS enabled mobile device, an actual (absolute) GNSS position is generated by adding the calculated relative GNSS position to the approximate position. The calculated relative GNSS position and/ actual (absolute) GNSS position for the GNSS enabled mobile device may be transmitted to an associated communication network for LBS applications.
A GNSS enabled mobile device such as the GNSS enabled mobile device 112 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to receive satellite broadcast signals from GNSS satellites in view such as, for example, the GNSS satellites 162-166. The received satellite signals may be used to generate a plurality of local GNSS measurements such as code delay measurements, phase measurements and pseudorange measurements. The GNSS enabled mobile device 112 may be operable to use the generated local GNSS measurement to determine its own GNSS position (latitude and longitude). The GNSS enabled mobile device 112 may be operable to transmit and/or receive radio signals across the communication network 130, which may support various telecommunication standards such as, for example, 3GPP, 3GPP2, LTE, WiFi and WiMAX. In order to achieve a fast position fix, the GNSS enabled mobile device 112 may be operable to acquire A-GNSS assistance data from the A-GNSS server 140 via the communication network 130. In this regard, the GNSS enabled mobile device 112 may be operable to generate an A-GNSS assistance data request and transmit to the A-GNSS server 140. In response, the GNSS enabled mobile device 112 may be operable to receive acquired A-GNSS assistance data from the A-GNSS server 140. In this regard, the acquired GNSS assistance data does not comprise ephemeris data. Instead, the acquired GNSS assistance data may comprise various other navigation elements such as, for example, current and/or predicted acquisition assistance data, satellite almanac data, extra resolution, for example, better than one GNSS chip, on the code phase, azimuth and elevation fields for each GNSS satellite, and/or an approximate position for the GNSS enabled mobile device 112. The azimuth and elevation fields may comprise azimuth and elevation data for corresponding GNSS satellites with resolution better than, for example, ten degrees. The approximate position for the GNSS enabled mobile device 112 may be a known GNSS position that the GNSS enabled mobile device 112 locks to. For example, the approximate position for the GNSS enabled mobile device 112 may be the GNSS position or position related information of a serving base station such as the BS 120.
The GNSS enabled mobile device 112 may be operable to utilize the acquired GNSS assistance data, namely, acquisition assistance data, extra resolution on the code phase, azimuth and elevation fields for each GNSS satellite, and/or satellite almanac data, to compute a relative GNSS position with respect to the approximate position for the GNSS enabled mobile device 112. More specifically, a relative GNSS position with respect to the approximate position for the GNSS enabled mobile device 112 may be calculated utilizing local GNSS measurements such as local code delay measurements from at least one satellite, and the acquired GNSS assistance data, without utilizing ephemeris data. In instances where the acquired GNSS assistance data may not comprise extra resolution on the code phase, azimuth and elevation fields for each GNSS satellite, the GNSS enabled mobile device 112 may be operable to use the approximate position and the satellite almanac data to calculate the azimuth and elevation fields with a desired resolution for each GNSS satellite. The calculated satellite azimuth and elevation fields together with, for example, current and/or predicted acquisition assistance data, and satellite almanac data may be utilized to compute the relative GNSS position for the GNSS enabled mobile device 112. In instances where an actual (absolute) GNSS position for the GNSS enabled mobile device 112 may be required, the GNSS enabled mobile device 112 may be operable to generate the actual GNSS position for the GNSS enabled mobile device 112 by adding the computed relative GNSS position to the approximate position. The GNSS enabled mobile device 112 may be operable to provide the computed relative GNSS position and/or the generated actual GNSS position to the communication network 130 to support various LBS applications such as location-based friends finding.
The BS 120 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to perform air interface processing and schedule communication resources in both uplink communications and downlink communications for various associated mobile devices in a timely manner. The GNSS position for the BS 120 may be known at the A-GNSS server 140 and may be utilized as an approximate position for associated mobile devices such as the GNSS enabled mobile device 112. In this regard, information such as ranges from the BS 120 to each of the GNSS satellites in view such as, for example, the GNSS satellites 162-166, and range rates from each of the GNSS satellites 162-166 to the BS 120 may be utilized to compute relative GNSS positions for corresponding mobile devices such as the GNSS enabled mobile device 112.
The communication network 130 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to provide various data services on a large-scale basis by using various technologies such as, for example, Ethernet, 3GPP, 3GPP2, LTE, WiFi and WiMAX. The communication network 130 may be a wired high-speed connection such as an Ethernet network, or may be a wireless network, for example, a WiMAX network.
The A-GNSS server 140 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to access a satellite reference network such as, for example, the WWRN 150, to collect GNSS satellite data by tracking GNSS satellite constellations through the WWRN 150. The A-GNSS server 140 may be operable to generate A-GNSS assistance data, which may be utilized for acquiring a fast GNSS position for a GNSS-enabled mobile device especially in a weak signal environment. The generated A-GNSS assistance data may comprise various navigation elements such as, for example, acquisition assistance data, satellite almanac data, extra resolution on the code phase, azimuth and elevation fields for each of the GNSS satellites in view, and/or an approximate position for a GNSS enabled mobile device of interest. In addition, the A-GNSS server 140 may be operable to use Long Term Orbits (LTO) technology to provide accurate predicted A-GNSS assistance data for all healthy GNSS satellites in view. The predicted A-GNSS assistance data may be valid for up to, for example, 10 days in the future. In this regard, the A-GNSS server 140 may be operable to provide both current and predicted A-GNSS assistance data to a GNSS enabled mobile device of interest via the communication network 130. The A-GNSS server 140 may be operable to communicate with the communication network 130 via either a user-plane (data transmission) or a control-plane (signaling) for delivering the generated A-GNSS assistance data to users of interest. The A-GNSS server 140 may be operable to support messaging in exemplary formats that may be compatible with telecommunication networks such as 3GPP, 3GPP2, LTE, WiFi, WiMAX, and variants thereof. For example, the A-GNSS server 140 may be 3GPP standard compliant by supporting messaging in RRLP format, PCAP interface and OMA SUPL v1.0.
The WWRN 150 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to collect and distribute data for GNSS satellites on a continuous basis. The WWRN 150 may comprise a plurality of GNSS reference tracking stations located around the world to A-GNSS coverage all the time in both a home network and/or any visited network. This allows users of the GNSS enabled devices such as the GNSS enabled mobile device 112 to roam with associated LBS applications anywhere in the world. The WWRN 150 may be operable to ensure high levels of availability and reliability for LBS performance.
The GNSS satellites 162 through 166 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to generate and broadcast satellite navigational information in suitable radio-frequency (RF) signals to various GNSS capable devices such as, the GNSS enabled device 112. The broadcast satellite navigational information may be utilized to support LBS services. The GNSS satellites 162 through 166 may be GPS, Galileo, GLONASS and any other global or local navigation satellites.
In an exemplary operation, a GNSS enabled mobile device such as the GNSS enabled mobile device 112 may be operable to receive satellite broadcast signals from GNSS satellites in view such as the GNSS satellites 162-166. The received satellite signals may be used to generate local GNSS measurements such as code delay measurements, phase measurements and pseudorange measurements. To achieve a fast position the GNSS enabled mobile device 112 may be operable to send an A-GNSS assistance data request to the A-GNSS server 140 to acquire A-GNSS assistance data. In response, the A-GNSS server 140 may be operable to identify or determine an approximate position for the GNSS enabled mobile device 112. The identified approximate position may be, for example, the position of the BS 120. According to the identified approximate position for the GNSS enabled mobile device 112, the A-GNSS server 140 may be operable to calculate acquisition assistance data at current and/or future time instances using GNSS satellite data collected via the WWRN 150. The calculated acquisition assistance data for the identified approximate position may be used to generate A-GNSS assistance data for the GNSS mobile device 112. In addition, the generated A-GNSS assistance data may also comprise other navigation elements, for example, satellite almanac data, extra resolution, for example, better than one GNSS chip, on the code phase, azimuth and elevation fields for each of the GNSS satellites, and/or the identified approximate position. The generated A-GNSS assistance data may be communicated to the GNSS enabled mobile device 112 via the communication network 130. The GNSS enabled mobile device 112 may be operable to utilize the generated local GNSS measurements such as, for example, a code delay measurement from at least one GNSS satellite, and satellite navigation information in the received GNSS assistance data from the A-GNSS server 140 to compute a relative GNSS position for the GNSS enabled mobile device 112. In instances where the received GNSS assistance data comprises the approximate position for the GNSS enabled mobile device 112, the GNSS enabled mobile device 112 may be operable to generate an actual (absolute) GNSS position by adding the computed relative GNSS position to the approximate position. Depending on application and the availability of the approximate position, the GNSS enabled mobile device 112 may be operable to transmit the computed relative GNSS position and/or the generated actual GNSS position for the GNSS enabled mobile device 112 to the communication network 130.
The processor 202 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to generate A-GNSS assistance data for associated GNSS enabled mobile devices to achieve fast position fix. The processor 202 may be operable to collect GNSS satellite data from the WWRN 150. The collected GNSS satellite data may be utilized to generate A-GNSS assistance data in instances when it may be required. The processor 202 may be operable to receive a request for GNSS satellite data from, for example, the GNSS enabled mobile device 112. In response, the processor 202 may be operable to identify or determine an approximate position that the GNSS enabled mobile device 112 utilizes. The processor 202 may be operable to calculate acquisition assistance data according to the identified approximate position using the collected valid GNSS satellite data. The calculated acquisition assistance data are corresponding to specific time instants. In instances where the LTO technology may be implemented at the A-GNSS server 200, the processor 202 may be operable to utilize the collected valid GNSS satellite data to calculate and/or predict acquisition assistance data for the identified approximate position at specific time instances in the future. The predicted acquisition assistance data may be valid for, for example, up to 10 days in the future. The calculated and/or predicted acquisition assistance data may be utilized to generate A-GNSS assistance data for the GNSS mobile device 112. Depending on system capacity and/or the types of LBS applications, the generated A-GNSS assistance data may also comprise other navigation elements, for example, satellite almanac data, extra resolution on the code phase, azimuth and elevation fields for each of the GNSS satellites in view, and/or the identified approximate position. The processor 202 may be operable to communicate the generated A-GNSS assistance data to the GNSS enabled mobile device 112 via the communication network 130.
The positioning database 204 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to manage and store reference positions and/or A-GNSS assistance data. The contents in the positioning database 204 may comprise, for example, reference position information, acquisition assistance data, satellite almanac data, and/or extra resolution on the code phase, azimuth and elevation fields for each of the GNSS satellites in view. The reference position information may comprise actual positions and/or position related identifiers such as, for example, Cell-ID, BS ID, and/or spectrum channel ID. The contents in the positioning database 204 may be updated aperiodically as needed, or periodically.
The memory 206 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to store information such as executable instructions and data that may be utilized by the processor 202. The executable instructions may comprise algorithms that may be utilized to calculate A-GNSS assistance data using collected satellite data from the WWRN 150 automatically or upon request/signaled. The data may comprise ephemeris data. The memory 206 may comprise RAM, ROM, low latency nonvolatile memory such as flash memory and/or other suitable electronic data storage.
In an exemplary operation, the processor 202 may be operable to collect GNSS satellite data via the WWRN 150. The collected GNSS satellite data may be used to generate A-GNSS assistance data for an associated plurality of GNSS enabled mobile devices such as the GNSS enabled mobile device 112 in instances when it may be required. For example, the processor 202 may be operable to receive a request from the GNSS enabled mobile device 112 for A-GNSS assistance data. In response, the processor 202 may be operable to communicate with the positioning database 204 to determine a reference position, namely an approximate position, for the GNSS enabled mobile device 112. Acquisition assistance data at specific time instances may be calculated using the collected GNSS satellite data for the determined approximate position. The processor 202 may be operable to generate A-GNSS assistance data for the GNSS enabled mobile device 112 using the calculated acquisition assistance data for the determined approximate position. The generated A-GNSS assistance data may also comprise other navigation elements, for example, satellite almanac data, extra resolution on the code phase, azimuth and elevation fields for each of the GNSS satellites in view, and/or the determined approximate position. The generated A-GNSS assistance data may be communicated to the GNSS enabled mobile device 112 via the communication network 130 for a fast position fix.
The GNSS radio 302 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to receive GNSS satellite broadcast signals and convert them to GNSS baseband signals, which may be suitable for further processing in the processor 306 for a navigation solution, whether GNSS based or A-GNSS based.
The telecommunication radio 304 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to transmit and/or receive radio frequency (RF) signals over a telecommunication network such as the communication network 130. The received RF signals may be converted into corresponding baseband signals, which may be suitable for further processing by the processor 306. In this regard, the received radio signals may comprise A-GNSS assistance data with various navigation elements such as, for example, an approximate position, acquisition assistance data for the approximate position, satellite almanac data, and/or extra resolution on the code phase, azimuth and elevation fields for each GNSS satellite. In instances where the LTO technology may be implemented at the A-GNSS server 140, the received A-GNSS assistance data may also comprise predicted acquisition assistance data valid for, for example, up to 10 days in the future.
The processor 306 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to process satellite signals directly received via the GNSS radio 302 as well as signals received via the telecommunication radio 304. The processor 306 may be operable to extract navigational information from the received satellite signal to generate local GNSS measurements. The generated local GNSS measurements may be utilized to compute a GNSS position for the GNSS enabled mobile device 300. To achieve a fast position fix, the processor 306 may be operable to acquire GNSS assistance data from the A-GNSS server 140. In this regard, the acquired GNSS assistance data may not comprise ephemeris data, instead, may comprise acquisition assistance data for an approximate position, satellite almanac data, extra resolution on the code phase, azimuth and elevation fields for each GNSS satellite, and/or the approximate position for the GNSS enabled mobile device 300. The processor 306 may be programmed or configured to calculate the GNSS position for the GNSS enabled mobile device 300 using the generated local GNSS measurements and A-GNSS assistance data. Specifically, a relative GNSS position for the GNSS enabled mobile device 300 is calculated with respect to the approximate position using GNSS measurements and navigation information such as acquisition assistance data. In instances where LTO A-GNSS assistance data may be available, the processor 306 may be operable to calculate a relative GNSS position for the GNSS enabled mobile device 300 using the generated local GNSS measurements and predicted acquisition assistance data in the acquired LTO A-GNSS assistance data even without a network connection between the GNSS enabled mobile device 300 and the A-GNSS server 140.
The memory 308 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to store information such as executable instructions and data that may be utilized by the processor 306. The executable instructions may comprise algorithms that may be applied to calculate a GNSS position using local GPS measurements and A-GPS assistance data received from the A-GNSS server 140. The data may comprise the local GNSS measurements and the A-GNSS assistance data. The AGPS assistance data comprises satellite ranges and range rates for an approximate position, satellite almanac data, extra resolution on the code phase, azimuth and elevation fields for each GNSS satellite, and/or the approximate position. The memory 308 may comprise RAM, ROM, low latency nonvolatile memory such as flash memory and/or other suitable electronic data storage.
In an exemplary operation, the GNSS enabled mobile device 300 may be operable to receive satellite broadcast signals via the GNSS radio 302 and radio signals from the communication network 130 via the telecommunication radio 304, respectively. The received signals may be converted to corresponding baseband signals for further processing in the processor 306. The processor 306 may also be operable to utilize navigational information in the received satellite signal to generate local GNSS measurements. The processor 306 may also be operable to acquire GNSS assistance data from the A-GNSS server 140 to determine a fast position fix. The acquired A-GNSS assistance data may comprise satellite ranges and range rates for an approximate position, satellite almanac data, extra resolution on the code phase, azimuth and elevation fields for each GNSS satellite, and/or the approximate position for the GNSS enabled mobile device 300. The processor 302 may be operable to calculate a relative GNSS position with respect to the approximate position for the GNSS enabled mobile device 300 using the generated local GNSS measurements and the acquired A-GNSS assistance data. In instances where the approximate position may be available, the processor 306 may be operable to generate an actual (absolute) GNSS position for the GNSS enabled mobile device 300 by adding the calculated relative GNSS position to the approximate position. The processor 306 may be operable to transmit the calculated relative GNSS position and/or the generated actual GNSS position to the communication network 130 to support various LBS services such as location-based friends finding that is used to track and find friends and/or family members according to associated location information.
In step 410, it may be determined that whether the acquired A-GNSS assistance data may comprise the approximate position. In instances where the acquired A-GNSS assistance data may comprise the approximate position, then in step 412, it may be determined that whether the acquired A-GNSS assistance data may comprise satellite almanac data. In instances where the acquired A-GNSS assistance data may comprise satellite almanac data, then in step 414, the A-GNSS server 140 may be operable to generate A-GNSS data comprising the calculated satellite ranges and range rates, the approximate position and satellite almanac data. The exemplary steps continue in step 420, where the A-GNSS server 140 may be operable to transmit the generated A-GNSS data to the GNSS enabled mobile device 300 via the communication network 130.
In step 404, in instances where A-GNSS assistance data is not required for the GNSS enabled mobile device 300, then the exemplary steps remain in step 404.
In step 410, in instances where the acquired A-GNSS assistance data may not comprise the approximate position, then the exemplary steps continue in step 418, the A-GNSS server 140 may be operable to generate A-GNSS assistance data for the GNSS enabled mobile device 300, the generated A-GNSS assistance data comprises the calculated acquisition assistance data, and increased resolution on the code phase, azimuth and elevation fields for each GNSS satellite. The exemplary steps continue in step 420.
In step 412, in instances where the acquired A-GNSS assistance data may not comprise satellite almanac data, then in step 416, the A-GNSS server 140 may be operable to generate A-GNSS Data comprising the calculated satellite ranges and range rates, the approximate position and increased resolution on the code phase, azimuth and elevation fields for each GNSS satellite. The exemplary steps continue in step 420.
In step 506, in instances where the acquired A-GNSS assistance data comprise satellite azimuth and elevation fields for each of the GNSS satellites in view, then the exemplary steps continue in step 508, where
In step 512, in instances where the approximate position for the GNSS enabled mobile device 112 is not available in the acquired A-GNSS assistance data, then the exemplary steps continue in step 520, where the GNSS enabled mobile device 112 may be operable to transmit the computed relative GNSS position for the GNSS enabled mobile device to the communication network 130.
In step 514, in instances where an actual (absolute) GNSS position for the GNSS enabled mobile device 112 may not be required to support LBS services of interest, then the exemplary steps continue in step 520.
Aspects of a method and system for mobile device based GNSS position computation without ephemeris data are provided. In accordance with various embodiments of the invention, a GNSS enabled mobile device such as the GNSS enabled mobile device 112 may be operable to receive GNSS assistance data from the A-GNSS server 140. The received GNSS assistance data may comprise acquisition assistance data. The GNSS enabled mobile device 112 may be operable to calculate a relative GNSS position with respect to the approximate position using the acquisition assistance data in the received GNSS assistance data and a local code delay measurement for at least one GNSS satellite, without utilizing ephemeris data. The received GNSS assistance data does not comprise ephemeris data, instead, may comprise an approximate position for the GNSS enabled mobile device 112, extra resolution, for example, better than one GNSS chip, on the code phase, expected code delay, acquisition assistance data associated with the approximate position, satellite almanac data, and/or azimuth and elevation fields for the at least one GNSS satellite.
For a fast position fix, the GNSS enabled mobile device 112 may be operable to send a request to the A-GNSS server 140 for GNSS assistance data. In response, the A-GNSS server 140 may be operable to communicate with the positioning database 204 to identify and/or determine an approximate position (reference position) for the GNSS enabled mobile device 112. The identified approximate position for the GNSS enabled mobile device 112 may be, for example the GNSS position for the BS 120 that the GNSS enabled mobile device utilizes. The A-GNSS server 140 may be operable to calculate acquisition assistance data for the identified approximate position using GNSS satellite data collected via the WWRN 150. The calculated acquisition assistance data may correspond to a current time instant and/or one or more future time instants where the LTO technology may be implemented at the A-GNSS server 140. In instances where the received GNSS assistance data may not comprise an extra resolution on the code phase, azimuth and elevation fields for each of the GNSS satellites in view, the GNSS enabled mobile device 112 may be operable to calculate satellite azimuth and elevation fields for each GNSS satellite in view using the acquisition assistance data in the received GNSS assistance data.
The GNSS enabled mobile device 112 may be operable to receive GNSS broadcast data directly from GNSS satellites in view such as, for example, the GNSS satellites 162-166. The received GNSS satellites data may be used to generate one or more local GNSS measurements for each GNSS satellite in view. The GNSS enabled mobile device 112 may be operable to calculate the relative GNSS position for the GNSS enabled mobile device 112 with respect to the approximate position using the generated local GNSS measurements, the acquisition assistance data, and the azimuth and elevation fields for each GNSS satellite in view. In instances where the received GNSS assistance data may comprise the approximate position, the GNSS enabled mobile device 112 may be operable to generate an actual (absolute) GNSS position for the GNSS enabled mobile device 112 by adding the calculated relative GNSS position to the approximate position. Depending on corresponding LBS application, the GNSS enabled mobile device 112 may be operable to transmit the calculated relative GNSS position and/or the calculated actual (absolute) GNSS position for the GNSS enabled mobile device 112 to an associated communication network such as the communication network 130.
Other embodiments of the invention may provide a non-transitory computer readable medium and/or storage medium, and/or a non-transitory machine readable medium and/or storage medium, having stored thereon, a machine code and/or a computer program having at least one code section executable by a machine and/or a computer, thereby causing the machine and/or computer to perform the steps as described herein for mobile device based GNSS position computation without ephemeris data.
Accordingly, the present invention may be realized in hardware, software, or a combination of hardware and software. The present invention may be realized in a centralized fashion in at least one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system or other apparatus adapted for carrying out the methods described herein is suited. A typical combination of hardware and software may be a general-purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein.
The present invention may also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods. Computer program in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form.
While the present invention has been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the scope of the present invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present invention without departing from its scope. Therefore, it is intended that the present invention not be limited to the particular embodiment disclosed, but that the present invention will include all embodiments falling within the scope of the appended claims.
This patent application makes reference to, claims priority to and claims the benefit from U.S. Provisional Patent Application Ser. No. 61/288,243 filed on Dec. 18, 2009. The above stated application is hereby incorporated herein by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 61288243 | Dec 2009 | US |
| Child | 12754715 | US |
