1. Field of the Invention
This invention relates generally to the providing of location-based services, including position information of a mobile station (MS) such as a cellular handset. More particularly, the invention relates to the distribution of location-based services over a network, particularly a network utilizing TCP/IP protocols such as the Internet and Web Services.
2. Related Art
Location-based services (LBS) or location-dependent services generally refer to the concept of providing wireless services that are dependent on a certain location, for example, the current position of a mobile station. The mobile station is typically a cellular handset but could also be a personal digital assistant (PDA) or some other type of mobile device, mobile station, or user terminal capable of interfacing with a network. A system providing LBS enables the user of a mobile station, or some other network component or entity (e.g., an application server), to make a request for the position of the mobile station or additionally for a service or application dependent on the position of the mobile station. The request may be a one-time request initiated by the user of the mobile station. For example, a mobile station may request a map showing its current location, driving directions from its current location to a desired destination, information regarding the existence and/or location of a certain type of business (e.g., restaurant, hospital, gas station, etc.) proximate to its current location, and the like. The request may also be triggered at predetermined intervals of time or in response to the occurrence of an event. For example, an application server may request the position of a mobile station in response to the mobile station passing from one geographical area to another area, for tracking or emergency purposes or to provide location-based information such as advertisements or coupons relating to proximate businesses. Hence, once the position of a mobile station is determined, location-based information may be provided to the requesting party. This information may be accessible from databases (which may be owned by content providers and made accessible to subscribers) and provided in a specific format in accordance with a specific application (e.g., maps, travel instructions, business-related content) and filtered in accordance with the position of the requesting party and as well as according to personal preferences set by or for the user and/or according to other predetermined rules. Generally, the position of a mobile station is obtained from a wireless network and/or a suitable positioning service such as a satellite positioning system, and particularly the Global Positioning System (GPS).
GPS (known as GPS NAVSTAR in the US) positioning technology is well-known to persons skilled in the art and thus need not be described in detail herein. Briefly, GPS is based on an existing constellation of twenty-four satellites and five monitoring stations situated around the planet enabling the satellites to broadcast spread-spectrum signals. These GPS signals may be utilized as references in determining the position of a mobile station. In addition to GPS, another positioning technology that may be utilized is the Russian system GLONASS (Global Navigation Satellite System), or the future European system currently known as the Galileo System, which operate in a similar fashion. In GPS, the satellites have 12-hour orbits and are positioned in six orbital planes with nominally four satellites in each plane, equally spaced at sixty degrees apart and inclined at fifty-five degrees relative to the equatorial plane. The satellites transmit carrier signals in two frequencies in the L-band, L1 (1.575.42 MHz) and L2 (1.227.60 MHz). Position is determined by operating a GPS receiver, which may be built into a cellular telephone or other mobile device, to acquire a sufficient number of satellites for pinpointing the location of the GPS receiver. Typically, a minimum of three satellites must be acquired so that their positions relative to the GPS receiver may be trilaterated. However, four satellites are preferred in order to obtain altitude information and ensure that the clock in the GPS receiver is synchronized with the more precise atomic clock in the satellites. Generally, the position of the GPS receiver is computed using the known position of the satellites in space (i.e., the orbits and times are known) and the known distances of the satellites from the GPS receiver (i.e., the travel times of radio signals from the satellites to the GPS receiver may be determined because their velocity at which radio signals propagate is known), and correcting or compensating for any delays and errors such as ephemeris errors. To enable measurement of the distance from a satellite to a GPS receiver, the satellite transmits a Pseudo Random Code (PRC) at precise intervals. The PRC is a stream of bits carrying the timing signal. The PRC also includes the satellite's address and thus each satellite has a unique PRC, enabling a GPS receiver to discriminate among the signals of different satellites. The PRC carried on the L1 carrier frequency, known as the Coarse Acquisition (C/A) code, is designated for civilian use.
Because a GPS receiver does not initially know its position, it must search for satellite signals in order to take the measurements needed to determine its position. From a cold start, the search can take approximately twelve minutes, which is considered much too long for the user of a mobile station. The time to acquire satellite data may be shortened by providing almanac data that essentially describe a long-term model of satellite trajectories, in addition to ephemeris, clock and satellite position data. Almanac data may be provided on a wireless network and updated regularly as new data is received from the satellites. Almanac data enables a GPS receiver to look for specific satellites by letting the GPS receiver know when they are likely to be overhead and visible to the GPS receiver, thereby reducing search time.
In order to improve the performance of GPS-based communications systems, advanced positioning methodologies have been developed. One such methodology is known as assisted-GPS or A-GPS technology, which generally refers to a system in which outside source such as an assistance server and reference network assist a GPS receiver in performing the tasks required for making range measurements, rendering position solutions, and the like. A-GPS promises to be a cost-efficient and time-efficient method for using a wireless network to distribute assistance or aiding data to GPS receivers, particularly GPS receivers integrated in mobile stations such as cellular handsets. Conventional implementations of A-GPS are well-known to persons skilled in the art and thus need not be described in detail herein. Briefly, in an A-GPS implementation, by utilizing the GPS receivers incorporated in a wireless network and estimating the location of a mobile station (e.g., the cell or sector in which the mobile station is located), the GPS signal that the mobile station will receive may be predicted and this information may be transmitted to the mobile station. The use of such assistance greatly reduces the size of the search space and shortens the time-to-first-fix (TTFF) down to a few seconds and potentially one second or less. Moreover, the A-GPS receiver in a mobile station may detect and demodulate signals that are an order of magnitude weaker than those required by conventional GPS receivers. In addition, while a mobile station could be equipped with a chip having all the functionalities of a full A-GPS receiver, only a partial A-GPS receiver is required in an A-GPS enabled mobile station. In the latter case, satellite data is downloaded over the mobile network, and the GPS receiver in the mobile station receives the data needed to calculate position every time the data are needed. In the typical architecture for an A-GPS system envisioned by industry, the system includes a mobile station whose position is sought and that is equipped with a partial GPS receiver, an A-GPS server equipped with a reference GPS receiver that can acquire the same satellites as the mobile station, and a wireless network infrastructure that includes cellular base stations and a mobile switching center. The A-GPS server obtains the estimated position of the mobile station (e.g., at the level of cell and sector) from the mobile switching center, monitors signals from GPS satellites seen by the mobile station, collects specific measurements from the mobile station, collects position results, and communicates the results to the mobile station.
The advantages provided by A-GPS and other advanced permutations of conventional GPS technology, such as improved accuracy, reduced positioning solution times and lower cost, make these advanced positioning technologies attractive for use in conjunction with location-based services. Ideally, a system capable of providing and distributing location-based services should be able to manage a large number of mobile stations over a large number of geographical areas without requiring the costly build-out of additional network infrastructure and without burdening existing infrastructure. In currently developing approaches for integrating GPS technology with wireless networks, a request for the position of a mobile station initiates the acquisition and refinement of GPS data as well as the generation any assistance or aiding data needed to compute the final position solution for the mobile station. In such a system, it can be appreciated that a large number of positioning requests by multiple users could have the potential for significantly overtaxing the networks involved and consequently defeating the advantages enabled by the positioning technology employed.
Therefore, there is a need for a distributed GPS processing system, and particularly one implementing location-based services, which overcomes the disadvantages set forth above and others previously experienced. In particular, there is a need for a system that distributes only one set of aiding data to all A-GPS users in the same location area without the need for a complex infrastructure for point-to-point and cell broadcasting position methods in as in current A-GPS technology.
A method is described for providing location-based information over a network. In this method, a plurality of GPS reference data sets, corresponding to a plurality of respective local areas, are acquired at intervals such that each GPS reference data set is updated on a continuous basis. A plurality of aiding data sets are generated at intervals based on the respective GPS data sets, whereby each aiding data set is updated on a continuous basis. The generated aiding data sets are stored at intervals on a data-storing network server, whereby updated aiding data sets are available on a continuous basis for access by a requesting entity via communication with the data-storing network server.
According to another aspect of the subject matter disclosed, a method is described for providing location-based information over a network. In the method, a plurality of GPS reference data sets, corresponding to a plurality of respective local areas, are acquired at intervals such that each GPS reference data set is updated on a continuous basis. A plurality of aiding data sets are generated at intervals based on the respective GPS data sets, whereby each aiding data set is updated on a continuous basis. The generated aiding data sets are stored at intervals on a data-storing network server, whereby updated aiding data sets are available on a continuous basis. In response to a request for the position of a mobile station located in one of the local areas, a stored aiding data set is selected based on the local area in which the mobile station is located, and the selected aiding data set is utilized to compute a final position result indicative of the position of the mobile station.
According to an implementation disclosed, a system is described for providing location-based information over a network. The system may include an A-GPS server, a data-storing network server communicating with the A-GPS server, and an LBS application center communicating with the data-storing network server. The A-GPS server is adapted for generating GPS aiding data sets corresponding to a plurality of local areas and computing a final position result for a mobile station positioned in one of the local areas. The data-storing network server is adapted for receiving the aiding data sets from the A-GPS server and storing the aiding data sets. The LBS application center is adapted for transferring a selected aiding data set to a mobile station and position results from the mobile station to the data-storing network server for use by the A-GPS server in computing the final position result. In some cases, the final position of the mobile station can be computed inside the mobile station and transferred to the LBS application center for direct application without having the A-GPS server to refine the position result.
Other systems, methods, features and advantages of the invention will be or will become apparent to one with skill in the art upon examination of the following figures and detailed description. It is intended that all such additional systems, methods, features and advantages be included within this description, be within the scope of the invention, and be protected by the accompanying claims.
The invention can be better understood by referring to the following figures. The components in the figures are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the invention. In the figures, like reference numerals designate corresponding parts throughout the different views.
In the following description, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration one or more specific exemplary embodiments in which the invention may be practiced. It is to be understood that other embodiments may be utilized and structural changes may be made without departing from the scope of this invention.
The subject matter disclosed according to one aspect provides a system architecture and methodology that extend A-GPS positioning beyond the point-to-point and cell broadcast positioning services currently being employed and developed in the industry. An example of an implementation of the subject matter will now be described with reference to
System 100 includes one or more location-based services (LBS service) areas 110. An LBS service area 110 may constitute, for example, an area for Enterprise application, a WASP network, a Mobile Virtual Network Operator, or the like. As illustrated in
Each local area GPS reference data center 212 may communicate with a global GPS reference network 130 via appropriate data links 132, which may include a TCP/IP ftp site or other reference network. The global GPS reference network 130 may be any network that supports GPS data for global coverage. One example of a suitable global GPS reference network 130 is the existing JPL reference network, although the subject matter is not limited to the use of this network. The global GPS reference network 130 may communicate with a secondary reference data center 134 via an appropriate data link 136, enabling the secondary reference data center 134 to collect GPS data from the global GPS reference network 130. The GPS data collected can include, but is not limited to, ephemeris, almanac, GPS time, bits per second nav message, DGPS correction, and other types of GPS data for use in A-GPS positioning. As further described below, the secondary GPS reference data center 134 may be utilized as a backup system to support the GPS reference data in the event a local area GPS reference data center 212 fails to support GPS data due to hardware failure, software failure, link failure, or the like.
Each local area GPS reference data center 212 may also communicate with an A-GPS server 140 over an appropriate communication link 142 such as a TCP/IP link. The A-GPS server 140 may thus receive local GPS reference data (e.g., ephemeris, almanac, GPS time, bits per second nav message, DGPS correction, and other types of GPS data for use in A-GPS positioning) from the local area GPS reference data centers 212. The A-GPS server 140 may in turn communicate with the secondary reference data center 134 via an appropriate communication link 144 such as a TCP/IP link to receive global GPS reference data (e.g., ephemeris, almanac, GPS time, bits per second nav message, DGPS correction, and other types of GPS data for use in A-GPS positioning). In addition, the A-GPS server 140 may communicate with a data-storing network server 150 such as, for example, a secured Internet server (e.g., an ftp server or web server), via an appropriate communication link 152 such as a TCP/IP link to enable the transfer of data between these two network components as described below. The A-GPS server 140 performs a number of functions. These functions include managing the GPS reference data collected from local area GPS reference data centers 212 and/or the secondary reference data center 134, validating such GPS data, generating and formatting GPS aiding data for storage on the data-storing network server 150, computing the final position of a target A-GPS enabled mobile station 160 based on position results outputted by the mobile station 160, and providing the final position to the data-storing network server 150. Many of these functions are further described below. The data-storing network server 150 manages the storage of a variety of location-based data, including A-GPS data provided by the A-GPS server 140, position results, and the like. In addition, the data-storing network server 150 can be employed to manage the storage of application site information, user information, and the like. Still further, the data-storing network server 150 can be employed to control user access to the data files and keep track of the number of users accessing data, the number of times a particular user has accessed data, billing processes, and so on.
Mobile station 160 may be capable of multiple modes of operation, including non-assisted as well as assisted modes, wherein at least one mode is manually or automatically selectable in which mobile station 160 is A-GPS enabled for compatibility with implementations described in this disclosure. Mobile station 160 may, for instance, take the form of a wireless device such as a cellular telephone (also known as a wireless handset, cellphone, mobile telephone or mobile phone) or any other type of mobile device, including, but not limited to, personal digital assistants (“PDAs”), pagers, computer, two-way radio, trunked radio, specialized mobile radio (“SMR”) or any other device for which it is desirable to determine location information. In the case of a cellular telephone, mobile station 160 may utilize a cellular transceiver in its communication section that operates at any radio frequency (“RF”) band utilizing any transmission schemes including but not limited to CDMA, CDMA-2000, W-CDMA, TDMA, FDMA, GSM, UMTS, AMPS, Bluetooth, Wi-Fi and/or any combination or extension of these transmission schemes or similar schemes. Mobile station 160 may be an Aided Location Communication Device (“ALCD”) as disclosed in copending U.S. patent application Ser. No. 10/885,507, filed Jul. 3, 2004, titled “Aided Location Communication System”, assigned to the assignee of this disclosure.
A location-based services (LBS) application center or server 170 communicates with the data-storing network server 150 via an appropriate communication link 172 such as a TCP/IP link to enable the transfer of data between these two network components. The LBS application center 170 is provided to manage communications with a number of network components. The LBS application center 170 communicates with any number of mobile stations 160 participating in a wireless network, including the target mobile station 160 illustrated in
An example of the operation of the system illustrated in
In the event that a local GPS reference receiver 214 fails to provide GPS data, the corresponding local area GPS reference data center 212 in advantageous embodiments switches the GPS data collection from the local GPS reference receiver 214 to the global GPS reference network 130. The GPS data collected from the global GPS reference network 130 will be filtered out for local visible satellites 120 based on the position of the local area GPS reference data center 212. The secondary GPS reference data center 134 collects the global GPS data from the global GPS reference network 130 and provides the data to the A-GPS server 140 in response to a request by the A-GPS server 140.
The A-GPS server 140 stores the sets or packets of GPS data for each local area in a memory location and processes the data sets to generate sets or packets of aiding data corresponding to each local area. The aiding data are available only for those mobile terminals 160 located within a particular local service area. Aiding data are generated without any request by a requesting entity (such as the mobile station 160) because every mobile station 160 in the same service area can use the aiding data applicable to that service area. The A-GPS server 140 can format the aiding data into any protocol type supported by the industry. Examples of protocols and aiding types include, but are not limited to, those set forth in TABLES 1 and 2 below.
It will be noted that for mobile station-based (MS-based) aiding types, with the A-GPS data, position is computed inside the mobile station 160 and returns to the A-GPS server 140. For mobile station-assisted (MS-assisted) aiding types, with the A-GPS data, position is computed inside the A-GPS server 140 based on the GPS results returned from the mobile station 160. It will be further noted that a given aiding message can include position aiding data indicative of the position of the local area GPS reference data center 212.
Once the A-GPS server 140 processes a set of aiding data into an aiding protocol message format, the A-GPS server 140 writes the aiding data to the data-storing network server 150. In this manner, updated aiding data for each local area are always obtainable by accessing the data-storing network server 150. Hence, the system 100 does not need to wait for a user-initiated position request in order to compute aiding data, unlike systems of the prior art. It thus can be seen that the architecture and operation of the system 100 offer several advantages. In the event that a request is made for the position of a mobile station 160, existing, current aiding data can be retrieved from the data-storing network server 150 in response to the request—i.e., the request itself is not needed to generate aiding data-thus reducing network latency and time required for create the A-GPS data and improving the time-to-first-fix (TTFF), as well as reducing the network bandwidth required for data transfer. The structure of the aiding data written to the data-storing network server 150 may include, but is not limited to, the structures set forth in TABLES 3 and 4 below.
The aiding data generated by the A-GPS server 140 can be utilized to fulfill a request for the position of a target mobile station 160. Such a request can be made by any appropriate requesting entity communicating with the system 100. The requesting entity can be, for example, an application, site, or end user that utilizes the position of a mobile station 160 in order to provide location-based services (e.g., map information, travel directions, tracking, commercial information) or emergency services (e.g., E911 service) to the user of the mobile station 160. The requesting entity can also be the target mobile station 160 itself or another mobile station that seeks the position of the target mobile station 160. For convenience, the remainder of the description of the operation of the exemplary system 100 illustrated in
In one exemplary implementation, a positioning request is made to the LBS application center 170. Upon receiving the positioning request, the LBS application center 170 maps the mobile station 160 to a service area based on, for example, the ID of the mobile station 160 (e.g., a cell phone number, a user tag for enterprise applications, etc.) and on the approximate position of the mobile station 160 (e.g., a cell position for commercial applications, etc.). The LBS application center 170 can also determine which aiding protocol is to be used for the mobile station 160 based on the ID of the mobile station 160 and/or other types of information. Once it has determined the appropriate aiding protocol and identified the service area, the LBS application center 170 accesses a service area directory stored on the data-storing network server 150 and retrieves the aiding data pertinent for the area in which the target mobile station 160 is located. The LBS application center 170 passes the aiding data from the data-storing network server 150 to the mobile station 160 as a data packet without decoding and reformatting the data. The LBS application center 170 can also choose to add a service area ID to the aiding message, and the service area ID can be attached to the position result message returned by the mobile station 160. The LBS application center 170 can quickly pass the position result to the appropriate destination in the data-storing network server 150.
In one exemplary implementation, the mobile station 160 is A-GPS enabled and hence an A-GPS unit is integrated with the mobile station 160 as represented by the GPS antenna 196 illustrated in
Once the LBS application center 170 receives the position result from the mobile station 160, the LBS application center 170 determines the service area in which the mobile station 160 resides. The LBS application center 170 then sends the position result message to the data-storing network server 150 on a first-come-first-serve basis. In the exemplary implementation, it will be noted that the LBS application center 170 itself does not need to decode and encode the position result in the protocol message. In addition, the position result is returned in one protocol message format regardless of whether it is MS-based or MS-assisted. The A-GPS server 140 does not need to use the position mode information (MS-based or MS-assisted) to compute the position of the mobile station 160. For commercial applications, the LBS application center 170 may receive a position result in more than one protocol, for example, RRLP, RRC, IS-801, or the like. However, based on the terminal ID, the LBS application center 170 is able to determine what type of protocol is used in the position return message and hence the position result message can be stored in the protocol based directory in the data-storing network server 150.
The data structure of the position result that is written to the data-storing network server 150 can include, but is not limited to, the structures set forth in TABLES 5 and 6 below.
In one exemplary implementation, the A-GPS server 140 continuously scans the position result directory in the data-storing network server 150 for new position result messages. For any such position result data, the A-GPS server 140 computes the final position result for the mobile station 160 using the navigation engine operating in the A-GPS server 140. The final position result can include, but is not limited to, the following parameters: position in longitude, latitude, altitude, position error, time of the position, speed, heading info, and the like. Upon computing a final position result, the A-GPS server 140 transmits the final position result to the data-storing network server 150, where this set of data is stored in an appropriate directory in the data-storing network server 150. Once stored in the data-storing network server 150, the final position data can be accessed by an appropriate network component for use in providing final position information, and/or applications or services based on the final position information, to a requesting entity (e.g., a mobile station, application, site, end user, or the like). A non-limiting example of the directory structure in the data-storing network server 150 is set forth in TABLE 7 below.
In one exemplary implementation, the LBS application center 170 retrieves the final position information from the data-storing network server 150. The LBS application center 170 can use the final position information as well as the ID of the target mobile station 160 (e.g., cellular telephone number) to generate location-based applications or services for the target mobile station 160, such as by interfacing with the GIS server 180 to obtain street maps, points of interest, street route information, and the like, and/or interfacing with the application server 190 of a content or service provider to generate content (e.g., advertisements, coupons, tickets, local business, traffic or weather information, etc.) pertinent to the determined location of the target mobile station 160. It can be appreciated by persons skilled in the art that once the final position and ID of the target mobile station 160 are made available at the LBS application center 170, a wide variety of different types of location services and content applications can be developed for presentation to the requesting entity.
Referring now to
For example, as described above, the aiding data may be stored on a data-storing network server 150. Hence, the aiding data is available at the time the position request is made, i.e., the actions summarized in blocks 300, 310, and 320 does not need to be initiated in response to the position request. As described above, it is advantageous that the actions summarized in blocks 300, 310, and 320 be repeated at regular intervals so that the aiding data being made available for access are updated for any given locality in which a mobile station 160 whose position is sought is located.
The foregoing system 100 and its operation may provide a number of advantages over prior art approaches to creating and distributing location-based information over a network or networks. For example, complex infrastructures conventionally required for A-GPS data transfer across a network are eliminated. Network latency and time needed to create A-GPS data, and network bandwidth required for data transfer, are reduced. The time-to-first-fix is shortened. LBS solutions for enterprise and commercial applications are easily scalable. Moreover, the system 100 provides an economical and easy way to generate location-based revenues for content providers. The system 100 facilitates the tracking of A-GPS transactions via history of access to the data-storing network server 150 and thus facilitates billing processes.
It will be understood, and is appreciated by persons skilled in the art, that one or more processes, sub-processes, or process steps described in connection with
While the foregoing description refers to the use of a GPS-based communications system, the subject matter is not limited to such a system. Any positioning technology that could benefit from the functionality provided by network components described above, such as the data-storing network server 150 and the LBS application center 170, could be implemented in the system 100.
Moreover, it will be understood that the foregoing description of an implementation has been presented for purposes of illustration and description. It is not exhaustive and does not limit the claimed inventions to the precise form disclosed. Modifications and variations are possible in light of the above description or may be acquired from practicing the invention. The claims and their equivalents define the scope of the invention.
This application is a continuation-in-part of U.S. patent application Ser. No. 10/885,507, filed Jul. 3, 2004, titled “Aided Location Communication System”. U.S. patent application Ser. No. 10/885,507 is a continuation-in-part of PCT application Serial No. PCT/US03/16308, filed May 22, 2003, titled “Search Domain Reducing Frequency Transfer in a Multi-mode Global Positioning System Used With Wireless Networks,” which is a continuation-in-part of U.S. patent application Ser. No. 10/155,614, filed May 22, 2002, titled “Search Domain Reducing Frequency Transfer in a Multi-mode Global Positioning System Used With Wireless Networks,” now U.S. Pat. No. 6,684,158, which is a continuation-in-part of U.S. patent application Ser. No. 09/795,871, filed Feb. 28, 2001, titled “Information Transfer in a Multi-mode Global Positioning System Used with Wireless Networks,” now U.S. Pat. No. 6,427,120, which claims priority under Section 119(e) to U.S. Provisional Application Ser. No. 60/225,076, filed Aug. 14, 2000, all of which are incorporated into this application by reference. U.S. patent application Ser. No. 10/885,507 is also a continuation-in-part of U.S. patent application Ser. No. 10/385,198, filed Mar. 10, 2003 now U.S. Pat. No. 6,915,208, titled “Information Transfer in a Multi-mode GPS Used with Wireless Networks,” which is a continuation of U.S. patent application Ser. No. 10/127,229, filed Apr. 19, 2002, titled “Information Transfer in a Multi-mode GPS Used with Wireless Networks,” now U.S. Pat. No. 6,542,823, which is a continuation of U.S. patent application Ser. No. 09/795,871, filed Feb. 28, 2001, titled “Information Transfer in a Multi-mode Global Positioning System Used with Wireless Networks,” now U.S. Pat. No. 6,427,120, which claims priority under Section 119(e) to U.S. Provisional Application Ser. No. 60/225,076, filed Aug. 14, 2000, all of which are incorporated into this application by reference. U.S. patent application Ser. No. 10/885,507 is also a continuation-in-part of U.S. patent application Ser. No. 10/194,627, filed Jul. 12, 2002, titled “Multi-mode GPS For Use with Wireless Networks,” which is a continuation of U.S. patent application Ser. No. 10/068,751, filed Feb. 5, 2002, titled “Multi-mode Global Positioning System For Use with Wireless Networks,” now U.S. Pat. No. 6,519,466, which is a continuation of U.S. patent application Ser. No. 09/781,068, filed Feb. 8, 2001, titled “Multi-mode Global Positioning System For Use with Wireless Networks,” now U.S. Pat. No. 6,389,291, which claims priority under Section 119(e) to U.S. Provisional Application Ser. No. 60/225,076, filed Aug. 14, 2000, all of which are incorporated into this application by reference.
Number | Name | Date | Kind |
---|---|---|---|
4426712 | Gorski-Popiel | Jan 1984 | A |
4445118 | Taylor et al. | Apr 1984 | A |
4463357 | MacDoran | Jul 1984 | A |
4578678 | Hurd | Mar 1986 | A |
4667203 | Counselman, III | May 1987 | A |
4701934 | Jasper | Oct 1987 | A |
4754465 | Trimble | Jun 1988 | A |
4785463 | Janc et al. | Nov 1988 | A |
4809005 | Counselman, III | Feb 1989 | A |
4821294 | Thomas, Jr. | Apr 1989 | A |
4890233 | Ando et al. | Dec 1989 | A |
4894662 | Counselman | Jan 1990 | A |
4998111 | Ma et al. | Mar 1991 | A |
5014066 | Counselman, III | May 1991 | A |
5036329 | Ando | Jul 1991 | A |
5043736 | Darnell et al. | Aug 1991 | A |
5108334 | Eschenbach et al. | Apr 1992 | A |
5177490 | Ando et al. | Jan 1993 | A |
5202829 | Geier | Apr 1993 | A |
5223844 | Mansell et al. | Jun 1993 | A |
5225842 | Brown et al. | Jul 1993 | A |
5257195 | Hirata | Oct 1993 | A |
5293170 | Lorenz et al. | Mar 1994 | A |
5311195 | Mathis et al. | May 1994 | A |
5323164 | Endo | Jun 1994 | A |
5343209 | Sennott et al. | Aug 1994 | A |
5345244 | Gildea et al. | Sep 1994 | A |
5347284 | Volpi et al. | Sep 1994 | A |
5347536 | Meehan | Sep 1994 | A |
5365450 | Schuchman et al. | Nov 1994 | A |
5379224 | Brown et al. | Jan 1995 | A |
5402347 | McBurney et al. | Mar 1995 | A |
5402441 | Washizu et al. | Mar 1995 | A |
5416712 | Geier et al. | May 1995 | A |
5420593 | Niles | May 1995 | A |
5422813 | Schuchman et al. | Jun 1995 | A |
5440313 | Osterdock et al. | Aug 1995 | A |
5450344 | Woo et al. | Sep 1995 | A |
5504684 | Lau et al. | Apr 1996 | A |
5506587 | Lans | Apr 1996 | A |
5535278 | Cahn et al. | Jul 1996 | A |
5535728 | Cahn et al. | Jul 1996 | A |
5546445 | Dennison et al. | Aug 1996 | A |
5587715 | Lewis | Dec 1996 | A |
5592173 | Lau et al. | Jan 1997 | A |
5594425 | Ladner et al. | Jan 1997 | A |
5625668 | Loomis et al. | Apr 1997 | A |
5663734 | Krasner | Sep 1997 | A |
5663735 | Eshenbach | Sep 1997 | A |
5666330 | Zampetti | Sep 1997 | A |
5701328 | Schuchman et al. | Dec 1997 | A |
5724660 | Kausner et al. | Mar 1998 | A |
5726893 | Schuchman et al. | Mar 1998 | A |
5739786 | Greenspan et al. | Apr 1998 | A |
5757786 | Joo | May 1998 | A |
5764184 | Hatch et al. | Jun 1998 | A |
5781156 | Krasner | Jul 1998 | A |
5786789 | Janky | Jul 1998 | A |
5812087 | Krasner | Sep 1998 | A |
5825327 | Krasner | Oct 1998 | A |
5828694 | Schipper | Oct 1998 | A |
5831574 | Krasner | Nov 1998 | A |
5841396 | Krasner | Nov 1998 | A |
5845203 | LaDue | Dec 1998 | A |
5854605 | Gildea | Dec 1998 | A |
5874914 | Krasner | Feb 1999 | A |
5877724 | Davis | Mar 1999 | A |
5877725 | Kalafus | Mar 1999 | A |
5883594 | Lau | Mar 1999 | A |
5884214 | Krasner | Mar 1999 | A |
5889474 | LaDue | Mar 1999 | A |
5903654 | Milton et al. | May 1999 | A |
5907578 | Pon et al. | May 1999 | A |
5907809 | Molnar et al. | May 1999 | A |
5917444 | Loomis et al. | Jun 1999 | A |
5920283 | Shaheen et al. | Jul 1999 | A |
5923703 | Pon et al. | Jul 1999 | A |
5926131 | Sakumoto et al. | Jul 1999 | A |
5936572 | Loomis et al. | Aug 1999 | A |
5940027 | Forseth et al. | Aug 1999 | A |
5943363 | Hanson et al. | Aug 1999 | A |
5945944 | Krasner | Aug 1999 | A |
5963582 | Stansell, Jr. | Oct 1999 | A |
5963851 | Blanco et al. | Oct 1999 | A |
5966403 | Pon | Oct 1999 | A |
5977909 | Harrison et al. | Nov 1999 | A |
5982324 | Watters et al. | Nov 1999 | A |
5987016 | He | Nov 1999 | A |
5999124 | Sheynblat | Dec 1999 | A |
6002362 | Gudat | Dec 1999 | A |
6002363 | Krasner | Dec 1999 | A |
6009551 | Sheynblat | Dec 1999 | A |
6016119 | Krasner | Jan 2000 | A |
6040798 | Kinal et al. | Mar 2000 | A |
6041222 | Horton et al. | Mar 2000 | A |
6047017 | Cahn et al. | Apr 2000 | A |
6052081 | Krasner | Apr 2000 | A |
6058338 | Agashe et al. | May 2000 | A |
6061018 | Sheynblat | May 2000 | A |
6064336 | Krasner | May 2000 | A |
6081229 | Soliman et al. | Jun 2000 | A |
6085090 | Yee et al. | Jul 2000 | A |
6097974 | Camp, Jr. et al. | Aug 2000 | A |
6104338 | Krasner | Aug 2000 | A |
6104340 | Krasner | Aug 2000 | A |
6104712 | Robert et al. | Aug 2000 | A |
6107960 | Krasner | Aug 2000 | A |
6111540 | Krasner | Aug 2000 | A |
6111541 | Karmel | Aug 2000 | A |
6122506 | Lau et al. | Sep 2000 | A |
6131067 | Girerd et al. | Oct 2000 | A |
6133871 | Krasner | Oct 2000 | A |
6133873 | Krasner | Oct 2000 | A |
6133874 | Krasner | Oct 2000 | A |
6105980 | Krasner | Nov 2000 | A |
6150980 | Krasner | Nov 2000 | A |
6172640 | Durst et al. | Jan 2001 | B1 |
6178195 | Durboraw, III et al. | Jan 2001 | B1 |
6185427 | Krasner et al. | Feb 2001 | B1 |
6188351 | Bloebaum | Feb 2001 | B1 |
6208290 | Krasner | Mar 2001 | B1 |
6208291 | Krasner | Mar 2001 | B1 |
6211817 | Eschenbach | Apr 2001 | B1 |
6211819 | King et al. | Apr 2001 | B1 |
6215441 | Moeglein | Apr 2001 | B1 |
6215442 | Sheynblat | Apr 2001 | B1 |
6222483 | Twitchell et al. | Apr 2001 | B1 |
6222484 | Seiple et al. | Apr 2001 | B1 |
6225944 | Hayes | May 2001 | B1 |
6236354 | Krasner | May 2001 | B1 |
6236365 | LeBlanc et al. | May 2001 | B1 |
6239742 | Krasner | May 2001 | B1 |
6249245 | Watters et al. | Jun 2001 | B1 |
6252543 | Camp | Jun 2001 | B1 |
6259399 | Krasner | Jul 2001 | B1 |
6263280 | Stingone, Jr. | Jul 2001 | B1 |
6272430 | Krasner | Aug 2001 | B1 |
6289041 | Krasner | Sep 2001 | B1 |
6295024 | King et al. | Sep 2001 | B1 |
6307504 | Sheynblat | Oct 2001 | B1 |
6313786 | Sheynblat et al. | Nov 2001 | B1 |
6314308 | Sheynblat | Nov 2001 | B1 |
6327473 | Soliman et al. | Dec 2001 | B1 |
6343290 | Cossins et al. | Jan 2002 | B1 |
6347228 | Ludden et al. | Feb 2002 | B1 |
6353412 | Soliman | Mar 2002 | B1 |
6377209 | Krasner | Apr 2002 | B1 |
6389291 | Pande et al. | May 2002 | B1 |
6400314 | Krasner | Jun 2002 | B1 |
6405132 | Breed et al. | Jun 2002 | B1 |
6408196 | Sheynblat | Jun 2002 | B2 |
6411254 | Moeglein et al. | Jun 2002 | B1 |
6411811 | Kingdon et al. | Jun 2002 | B2 |
6411892 | Van Diggelen | Jun 2002 | B1 |
6414987 | Pon | Jul 2002 | B1 |
6417801 | Van Diggelen | Jul 2002 | B1 |
6421002 | Krasner | Jul 2002 | B2 |
6427120 | Garin et al. | Jul 2002 | B1 |
6429809 | Vayanos et al. | Aug 2002 | B1 |
6429814 | Van Diggelen et al. | Aug 2002 | B1 |
6429815 | Soliman | Aug 2002 | B1 |
6433731 | Sheynblat | Aug 2002 | B1 |
6433733 | Syrarinne et al. | Aug 2002 | B2 |
6433739 | Soliman | Aug 2002 | B1 |
6453237 | Fuchs et al. | Sep 2002 | B1 |
6456234 | Johnson | Sep 2002 | B1 |
6462708 | Tsujimoto et al. | Oct 2002 | B1 |
6466612 | Kohli et al. | Oct 2002 | B2 |
6473030 | McBurney et al. | Oct 2002 | B1 |
6477363 | Ayoub et al. | Nov 2002 | B1 |
6480145 | Hasegawa | Nov 2002 | B1 |
6484097 | Fuchs et al. | Nov 2002 | B2 |
6487499 | Fuchs et al. | Nov 2002 | B1 |
6505161 | Brems | Jan 2003 | B1 |
6510387 | Fuchs et al. | Jan 2003 | B2 |
6519466 | Pande et al. | Feb 2003 | B2 |
6526283 | Jang | Feb 2003 | B1 |
6526352 | Johnson et al. | Feb 2003 | B1 |
6429829 | Turetzky et al. | Mar 2003 | B1 |
6529829 | Turetzky et al. | Mar 2003 | B2 |
6535815 | Bloebaum | Mar 2003 | B2 |
6542821 | Krasner | Apr 2003 | B2 |
6542823 | Garin et al. | Apr 2003 | B2 |
6546232 | Sack | Apr 2003 | B1 |
6559793 | Eschenbach | May 2003 | B1 |
6559794 | Nakajima et al. | May 2003 | B1 |
6570530 | Gaal et al. | May 2003 | B2 |
6583734 | Bates et al. | Jun 2003 | B2 |
6583757 | Krasner | Jun 2003 | B2 |
6597311 | Sheynblat | Jul 2003 | B2 |
6633255 | Krasner | Oct 2003 | B2 |
6650694 | Brown et al. | Nov 2003 | B1 |
6671620 | Garin et al. | Dec 2003 | B1 |
6677894 | Sheynblat et al. | Jan 2004 | B2 |
6684158 | Garin et al. | Jan 2004 | B1 |
6707423 | Turetzky et al. | Mar 2004 | B2 |
6720920 | Breed et al. | Apr 2004 | B2 |
6731238 | Johnson | May 2004 | B2 |
6738630 | Ashmore | May 2004 | B2 |
6748198 | Salo | Jun 2004 | B1 |
6748217 | Hunzinger et al. | Jun 2004 | B1 |
6771625 | Beal | Aug 2004 | B1 |
6788885 | Agashe et al. | Aug 2004 | B2 |
6829534 | Fuchs et al. | Dec 2004 | B2 |
6871061 | Koorapaty et al. | Mar 2005 | B1 |
6873288 | Heppe | Mar 2005 | B2 |
6915208 | Garin et al. | Jul 2005 | B2 |
7010270 | Thomas et al. | Mar 2006 | B1 |
7091904 | Vantalon et al. | Aug 2006 | B2 |
7107064 | Ito | Sep 2006 | B2 |
7154436 | Chadha | Dec 2006 | B1 |
20010012771 | Ruiz | Aug 2001 | A1 |
20020019698 | Vilppula et al. | Feb 2002 | A1 |
20020064209 | Turetzky et al. | May 2002 | A1 |
20020072854 | Fuchs et al. | Jun 2002 | A1 |
20020080063 | Bloebaum et al. | Jun 2002 | A1 |
20020082774 | Bloebaum | Jun 2002 | A1 |
20020107030 | Syrjarinne | Aug 2002 | A1 |
20020142783 | Yoldi et al. | Oct 2002 | A1 |
20020145560 | Tsujimoto et al. | Oct 2002 | A1 |
20020186165 | Eschenbach | Dec 2002 | A1 |
20030016170 | Jandrell | Jan 2003 | A1 |
20030069694 | Fuchs et al. | Apr 2003 | A1 |
20030104818 | Kotzin | Jun 2003 | A1 |
20030112176 | Vayanos et al. | Jun 2003 | A1 |
20030112178 | Bajikar | Jun 2003 | A1 |
20030125044 | Deloach et al. | Jul 2003 | A1 |
20030176204 | Abraham | Sep 2003 | A1 |
20030201931 | Durst et al. | Oct 2003 | A1 |
20030212487 | Dooley et al. | Nov 2003 | A1 |
20040130484 | Krasner | Jul 2004 | A1 |
20040162084 | Wang | Aug 2004 | A1 |
20040254717 | Sugahara et al. | Dec 2004 | A1 |
20040263386 | King et al. | Dec 2004 | A1 |
20050186968 | Durst et al. | Aug 2005 | A1 |
20060038719 | Pande et al. | Feb 2006 | A1 |
20060181452 | King et al. | Aug 2006 | A1 |
20070063875 | Hoffberg | Mar 2007 | A1 |
20080005275 | Overton et al. | Jan 2008 | A1 |
20080055154 | Martucci et al. | Mar 2008 | A1 |
20080167049 | Karr et al. | Jul 2008 | A1 |
Number | Date | Country |
---|---|---|
1589059 | Mar 2005 | CN |
0511741 | Nov 1992 | EP |
1 092 987 | Apr 2001 | EP |
1 427 236 | Jun 2004 | EP |
1 452 886 | Sep 2004 | EP |
1452886 | Sep 2004 | EP |
2115195 | Jan 1983 | GB |
2 335 554 | Mar 1998 | GB |
58-105632 | Jun 1983 | JP |
7-36035 | May 1986 | JP |
4-326079 | Nov 1992 | JP |
H. 07-107550 | Apr 1995 | JP |
2000-102058 | Apr 2000 | JP |
2001-128226 | May 2001 | JP |
2001-223601 | Aug 2001 | JP |
2002-290308 | Jan 2002 | JP |
2002-199451 | Jul 2002 | JP |
2003-032140 | Jan 2003 | JP |
2003-284156 | Oct 2003 | JP |
2004-023753 | Jan 2004 | JP |
2004271310 | Sep 2004 | JP |
WO 9011652 | Oct 1990 | WO |
9947943 | Sep 1999 | WO |
WO 9947943 | Sep 1999 | WO |
WO 0010031 | Feb 2000 | WO |
WO 0045191 | Aug 2000 | WO |
WO 0162034 | Aug 2001 | WO |
02004975 | Jan 2002 | WO |
WO 0204975 | Jan 2002 | WO |
02063782 | Aug 2002 | WO |
WO 03098258 | Nov 2003 | WO |
2004031794 | Apr 2004 | WO |
2004034082 | Apr 2004 | WO |
WO2006014170 | Feb 2006 | WO |
2007126401 | Nov 2007 | WO |
Number | Date | Country | |
---|---|---|---|
20050227709 A1 | Oct 2005 | US |
Number | Date | Country | |
---|---|---|---|
60225076 | Aug 2000 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 10127229 | Apr 2002 | US |
Child | 10385198 | US | |
Parent | 09795871 | Feb 2001 | US |
Child | 10127229 | US | |
Parent | 10068751 | Feb 2002 | US |
Child | 10194627 | US | |
Parent | 09781068 | Feb 2001 | US |
Child | 10068751 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 10885507 | Jul 2004 | US |
Child | 11089455 | US | |
Parent | PCT/US03/16308 | May 2003 | US |
Child | 10885507 | US | |
Parent | 10155614 | May 2002 | US |
Child | PCT/US03/16308 | US | |
Parent | 09795871 | Feb 2001 | US |
Child | 10155614 | US | |
Parent | 10385198 | Mar 2003 | US |
Child | 10885507 | US | |
Parent | 10194627 | Jul 2002 | US |
Child | 10885507 | US |