Synchronizing a radio network with end user radio terminals

Information

  • Patent Grant
  • 8437693
  • Patent Number
    8,437,693
  • Date Filed
    Thursday, March 24, 2011
    13 years ago
  • Date Issued
    Tuesday, May 7, 2013
    11 years ago
Abstract
A wireless communications device comprises a communication receiver and a positioning system receiver in the wireless mobile communication device. An absolute time signal is received at the positioning system. A network time signal is received at the communication receiver of the wireless mobile communication device. A controller is in signal communication with the position system receiver and the communication receiver. The controller is configured to determine an offset of the absolute time signal from the network time signal and generates a timing mark. The timing mark is tagged by the positioning system receiver with an internal clock value wherein the timing mark has a known relationship with the absolute time signal. A memory stores the offset of the absolute time signal from the network time signal. A transmitter in the wireless mobile communication device transmits the offset for receipt by another wireless mobile communication device.
Description
BACKGROUND OF THE INVENTION

1. Field of the Invention


The present invention relates in general to Global Satellite System (GSS) receivers, and in particular to a method for synchronizing a radio network using end user radio terminals.


2. Related Art


Cellular telephony, including Personal Communication System (PCS) devices, has become commonplace. The use of such devices to provide voice, data, and other services, such as Internet access, provides many conveniences to cellular systems users. Further, other wireless communications systems, such as two-way paging, trunked radio, Specialized Mobile Radio (SMR) used by first responders, such as police, fire, and paramedic departments, have also become essential for mobile communications.


The Federal Communication Commission (FCC) has implemented a requirement that Mobile Stations (MS), such as cellular telephones be locatable within 50 feet once an emergency call, such as a “911” call (also referred to as “Enhanced 911” or “E911”) is placed by a given cellular telephone. Such position data assists police, paramedics, and other law enforcement and public service personnel, as well as other agencies that may need or have legal rights to determine the cellular telephone's position.


Currently, cellular and PCS systems are incorporating Global Positioning Systems (GPS) technology that uses GPS receivers in cellular telephone devices and other wireless transceivers to meet the FCC location requirement.


Such data can be of use for other than E911 calls, and would be very useful for wireless network users, such as cellular and PCS subscribers. For example, GPS data may be used by the MS user to locate other mobile stations, determine the relative location of the mobile station user to other landmarks, obtain directions for the cellular user via internet maps or other GPS mapping techniques, etc.


One significant problem with GPS receivers in a MS is that the GPS receiver may not always have an unobstructed view of the sky causing the received signals to be very weak. Often, the receiver is unable to demodulate the Almanac or Ephemeris data, making it impossible to determine the user's location or accurate GPS time. This problem may be addressed by transmitting Ephemeris and/or Almanac data and GPS time to the receiver over a communication network. A common feature of communication networks is a large and variable transmission delay, making it difficult to transmit accurate (uncertainty less than 1 millisecond) time.


The concept of locating a mobile unit by triangulating a set of ranges from either a set of fixed points (such as cellular transmitters) or mobile transmitters (such as GPS satellites) have a common requirement that the time of transmission is known. This implies that the time at all transmitters must be common, or the differences known. In many systems today, this information is not immediately available since the systems are focused on data transmission rather than ranging. Therefore, there is a need in the art to overcome the problem of transmission delay in both synchronized and unsynchronized networks.


Code Division Multiple Access (CDMA)(TIA/IS-95B) networks use a GPS time reference standard at every base station, and all transmission frames are absolutely synchronized onto GPS time. Therefore, a Mobile Station, by observing particular transitions on frame, master frame or hyper frame, may predict absolute GPS time within tens of microseconds, including radio transmission delay and group delays inside the mobile station or wireless handset.


Other classes of wireless networks, e.g., Time Division Multiple Access (TDMA), GSM, Analog Mobile Phone Systems (AMPS, TACS), DTV, etc., are not synchronized onto GPS time. Still, the accuracy, precision and stability of the master clock used at the base stations is fairly stable, and slowly varies relative to GPS time. Hence, both the time offset and frequency drift are very stable compared to GPS time, and can be monitored at relatively large intervals. However, any timing information derived solely from such a system has limited value, as there is currently no way to derive absolute GPS time from it.


One solution that has been proposed is to locate stationary monitoring entities, called LMU (Local Measurement Units), which are in radio visibility of several base stations (BS) in a given area. The LMU consists of a wireless section and a GPS timing receiver. At intervals, they measure time offset and frequency drift of every base station in the area, relative to GPS time. As one LMU can cover only a few Base Stations, the overlay monitoring network can become quite large and expensive. It necessitates communication links between the LMU's and a central network entity, which logs this information per BS, merges information from different sources (if several LMU's monitor the same Base Station), and delivers this information to a geolocation server if time assistance has to be delivered to a particular MS in the BS's visibility area. This requires several pieces of additional network infrastructure, as well as additional software and maintenance costs for the network operator to enable such a feature. Thus, there is a need in the art to eliminate the need for LMU's and the associated costs.


It can be seen, then, that there is a need in the art for delivering GPS data in a wireless communications systems, including cellular and PCS subscribers, in an efficient manner. It can also be seen that there is a need in the art for GPS capable MS, such as wireless handsets. It can also be seen that there is a need in the art to be able to aid the GPS receiver to speed acquisition and for position determination. It can also be seen that there is a need in the art to be able to aid the GPS receiver to provide more precise position determination. It can also be seen that there is a need in the art for a large cellular system that can use and/or supply GPS information to cellular users for a number of applications, including E911 without the requirement of geographically proximate base stations.


SUMMARY

Approaches consistent with the present invention provide synchronization of a radio network through the use of end user radio terminals. An end user radio terminal, such as Mobile Stations (MS) having a GPS receiver is able to determine the relationship between the Base Station signal timing events and GPS time, and to determine its clock frequency offset. This data may then be transferred to the Base Station (i.e. the network) for synchronization of the network. 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.





BRIEF DESCRIPTION OF THE 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.



FIG. 1 illustrates a typical OPS architecture.



FIG. 2 illustrates an implementation of synchronizing a radio network with end user radio terminals.



FIG. 3 is a diagram of the time tagging of GSM transmissions.



FIG. 4 is a diagram of GSM frames carrying GPS TOW.



FIG. 5 is a flow diagram of offset determination.



FIG. 6 is a flow diagram of a wireless handset using the offset determined in FIG. 5.





DETAILED DESCRIPTION

In FIG. 1 a typical GPS architecture is shown. System 100 comprises GPS satellite 102, which is illustrative of the constellation of GPS satellites that are in orbit, a MS (i.e. wireless handset 104) which may include a GPS receiver, a base station 106, a geolocation (server) service center 108, a geolocation end application 110, and a Public Safety Answering Point (PSAP) 112. The Mobile Station (MS) 104, such as a wireless handset, Personal Digital Assistant (PDA), or similar mobile device may have location technology of the present invention and may use GPS technology in support of various MS device implementations of E911 and geolocation services. The PSAP 112 and the geolocation end application 110 are included for reference only.


The GPS satellite 102 transmits spread spectrum signals 114 that are received at the wireless handset 104 and the geolocation server 108. For ease of illustrative purposes, the other GPS satellites are not shown, however, other GPS satellites also are transmitting signals that are received by the wireless handset 104 and the geolocation server 108. If the wireless handset 104 receives strong enough spread spectrum signals 114, the GPS receiver (not shown) in the wireless handset 104 may autonomously compute the position of the wireless handset 114 as is typically done in the GPS system. However, unless they are in open sky environments wireless handsets 104 are typically not able to receive strong enough spread spectrum signals 114 to autonomously compute the position of the wireless handset 104, but can still communicate with base station 106. Thus, base station 106 may communicate information via signals 116 to wireless handset 104 to allow wireless handset 104 to compute the location, or may transmit information from wireless handset 104 to the geolocation server 108 to enable the geolocation server 108 to compute the position of the wireless handset 104. If the base station 106 is transferring information to the wireless handset 104 to allow the wireless handset 104 to compute position, it is called “wireless aided GPS” or “MS Based,” whereas when the base station 106 transfers information from the wireless handset 104 to the geolocation server 108 for the geolocation server 108 to compute the position of the wireless handset 104, it is called “network-centric GPS” or “MS Assisted.”


Geolocation server 108 may also communicates with geolocation application 110 via signals 118 and with PSAP 112 via signals 120. These signals 118 and 120 may either be via wireless links, such as cellular, WiFi, Blue Tooth, to name but a few, or may be through the landline network, such as PSTN, Ethernet, or other such wired networks, to name but a few.


If it is a cellular telephone, for example, the wireless handset 104 may include a typical wireless handset section that performs the call processing (CP) function, and a GPS section for position computation, pseudorange measurement, and other GPS functions. A serial communication link, or other communication link, performs the communications between the CP section and the GPS section. A collection of hardware lines may be utilized to transmit signals between the CP and GPS section. In yet another implementation, both the CP and GPS sections may share circuitry.


If the MS 104 has the ability to compute GPS position, it gets GPS time from the GPS signal, and is able to calculate the offset between GPS time and the cell site clock. This is true whether or not the GPS portion of the MS 104 received assistance data from the geolocation service center 108. In unsynchronized networks, each cell site clock will have a different offset from GPS time, necessitating the pairing of cell site identifiers with the measured offset. In some wireless handset designs, the frequency error of the base station clock may also be computed.


The offset and frequency error may then be stored in the phone, and/or transmitted to the network (via signals 116) for storage in a database (possibly contained in the geolocation service center 108). Each time a wireless handset goes through that cell, the offset and error may be updated. If it is not possible to make a direct measurement of base station frequency error, then multiple clock-offset measurements may be used to determine drift rates.


Non-network related storage that is capable of being accessed via a data link such as SMS or GPRS may also be used such that independent service providers could store and forward time assistance information to other wireless handset units independent of the network.


This concept may also be used in conjunction with other localized networks like Nextel, SMS, FRS, etc. where a group of wireless handsets or mobile communication devices may help each other to determine location. For example, where a wireless handset gets a fix, that wireless handset can transmit offset information, or transmit other information via a non-cellular network, such as SMS, CB bands, WiFi, Blue Tooth, or whatever, to other wireless handsets that use that network, or are part of a group of devices used by the same company.


If the MS 104 lacks the ability to compute GPS position, it may capture simultaneous events from the GPS signals and the Base Station signals, and send them via signals 116 to a server, which is able to compute GPS position of the MS 104. After such computation, the server will be able to determine precise GPS time, and compute the offset (and drift) between GPS time and the clock in the Base Station. This information may then be transmitted via signals 116 to other MS 104 devices to assist their acquisition of GPS signals, whether or not those MS devices have the ability to compute their own GPS position.


Turning to FIG. 2, an implementation of synchronizing a radio network using end user radio terminals is shown. System 100 has a set of GPS satellites (illustrated by 102), a base station 106, a geolocation service center 108 and two wireless handsets 104 and 105.


As described earlier, wireless handset 104 receives signals from satellites 102 and either computes a GPS position locally, or transmits via signals 116 sufficient information to allow a server, such as the geolocation service center 108, to compute the position. Concomitant with computing the GPS position, a controller (not shown) in the wireless handset 104 or the geolocation service center 108 or some other device (not shown), determines the time offset and/or drift between GPS time and the clock in the base station 106.


Wireless handset 105 is illustrative of a wireless device containing a GPS receiver which requires knowledge of the clock offset and/or drift of the base station 106 clock in order to acquire satellite 102 signals and produce a GPS position fix. Depending on the type of network and its design, wireless handset 105 may receive the required data from wireless handset 104 directly via signals 202, from base station 106 via signals 204, or from the geolocation service center via signals 116 and 204 in sequence. Other sources of this information may include non-network devices (not shown) that may be implemented by independent service providers.


In another implementation, wireless handset 105 and wireless handset 104 may be the same wireless handset, used at different times. Wireless handset 104 may compute the clock offset and drift at one time, then be turned off and forget the previously computed data. Upon being re-powered, wireless handset 104 may require this data and may retrieve it (or a more recently computed value) from the base station 106, the geolocation service center 108 or some other source.


Alternatively, wireless handset 104 may compute the clock offset and/or drift of the clock in base station 106, then be turned off, but store the previously computed data. Upon being re-powered, the wireless handset may recall the data from its own memory without making use of any external data store. In some cases, this may eliminate the need for timekeeping in the MS when the MS is powered off which may increase battery time between charging.


The wireless handset may also build up a database of offsets computed for several different base stations, and since the base station clocks are stable for long periods, that information is useful when the wireless handset returns to that base station. Thus, when the mobile GPS receiver in a wireless handset or similar enabled device returns to a known cell site at a later time, the mobile GPS receiver already knows the offset between the cell site clock and GPS time, making a TTFF shorter for that mobile GPS receiver.


In FIG. 3, the time tagging of GSM transmissions is shown. A GSM network has been chosen for illustration. Other networks will have a similar implementation. This time-tagging is essential to the process of measuring the offset between GPS time and “network” time.


The CP section of the wireless handset 104 that has a valid GPS solution, generates a time mark 110 that may be implemented as a hardware pulse that the GPS receiver in the wireless handset tags with its own clock that has a known relation with the GPS system time that includes a “Time of Week” (TOW) portion. The CP section may also send a message to the GPS receiver identifying the GSM frame and bit number associated with the time mark, and the base station being used, as shown in Table 1. In the current implementation, a GPS time tag for the received GSM bit may be used for time tagging of the GSM transmission. By subtracting the time lag for transmission between the base station location and the wireless handset location, the wireless handset knows the GPS time when the GSM bit left the transmitting antenna. The subtraction may be done in the wireless handset or the geolocation services center (i.e. a relocation server), but the server is used in the current embodiment.


In yet another implementation, the wireless handset 104 may measure the frequency difference between the GPS clock and the call processing clock (provided the GPS clock and call processing clocks are not the same clock). The GPS receiver in the wireless handset 104 may already have the ability to measure the frequency difference between its clock and the GPS system frequency standard. Similarly, the wireless handset may also already have the ability to measure the frequency difference between its call processing clock and the frequency received from the Radio Network transmitter located at a base station. Thus, all the components may be incorporated into a wireless handset to measure the frequency difference between the GPS system frequency standard and the wireless network transmitter frequency and may be located in the CP section of the wireless handset or the GPS receiver section depending on the design and implementation of the wireless handset.


Table 1 contains the information supplied by the CP section to accompany the time mark:












TABLE 1







Name
Description









Base Station
Unique ID for current base station



CP_GSM_Frame
GSM Frame Number



CP_GSM_BIT
GSM Bit Number



Time_mark_uncertainty
Probable error between time mark and




received bit edge (1 sigma)










The geolocation server 108 may receive a number of parameters 112 from the wireless handset 104 including, but not limited to a GSM bit identifier, the associated GPS TOW and base station ID, position data, and frequency error. Once the clock offset and frequency difference is determined, a Kalman Filter or other estimation method may be used to model the wireless network's transmitter clock. In other implementations, the transmitter clock may be adjusted to minimize the errors. Such knowledge of the transmitter clock frequency and time error, enables better performance of the GPS receiver's TTFF, energy usage and position accuracy.


At a later time, the geolocation service center may propagate the stored time-tagged GSM frame/bit information to an approximate current time. This propagated time may then be transmitted to an acquiring wireless handset that does not currently have a GPS solution as described below.


Turning to FIG. 4, a diagram of GSM frames carrying GPS TOW. This functionality provides for accurate GPS time to a wireless handset 104 that does not yet have a GPS position. It also illustrates the method by which the present invention compensates for network delays.


When the wireless handset 104 requests aiding from the geolocation service center 108, a message from the server to the wireless handset is sent. The message identifies the GPS time with a specific GSM frame/bit, identified as “GSM Bit Y” in the figure. The server creates this message from earlier measurements made by this, or other, wireless handsets as described above. When the message is received at the wireless handset 104, the CP section of the wireless handset 104 generates a time mark aligned with a current GSM frame/bit, identified as “GSM Bit X” in the figure. The CP section may also send a message to the GPS receiver identifying the GSM frame and bit number associated with the time mark, and the base station being used, as shown in Table 1. The GPS receiver will then propagate the GPS time from the bit identified in the message (Y) to the bit that is aligned to the time mark (X), using nominal, (or corrected, if clock drifts are available) frame rates, thus compensating for the network delay and geolocation service center 108 time estimation errors. Because the wireless handset 104 location is unknown, there is an unknown transmission delay from the base station 106 to the wireless handset 104. This delay presents an unavoidable error in the received GPS time, but is limited by the typically small sizes of cellular radio sites.


In Table 2, an example of one possible message sent from the geolocation server 108 to the GPS receiver in an acquiring wireless handset 104 is the following:


















NAME
Description
Units
Notes




















gps_time_tag
VLMU_GPS_Week
GPS Week
Weeks
These are




Number

shown as



VLMU_GPS_TOW
GPS Time of
Usec
GPS TOW in




Week

FIG. 4.


freq
VLMU_Freq_Error
Base Station
Nsec/sec
This is ‘freq’




Freq. Error

in FIG. 4.


List_of_meas_uncertainties
VLMU_Time_Accuracy
Uncertainty
Usec




of GPS time



VLMU_Freq_Err_Acc
Uncertainty
Nsec/sec




of Clock




Error


network_reference_time
VLMU_GSM_Frame
GSM Frame
None
This is bit Y




Number

in FIG. 4



VLMY_GSM_Bit
BSM Bit
None




Number









The items in Table 2 may be repeated once for each base station identified in a data structure such as a neighbor list that identifies base stations near the current base station in the wireless network. In some implementations, the CP section of the wireless handset 104 may filter the list of base stations and only provide data for the serving base station.


Using the data items in Table 1 and Table 2, the algorithms used to convert time-tagged GSM frames to precise GPS time employed in the current implementations are:














CP_Bits = CP_GSM_Frame * 1250 + CP GSM_Bit


VLMU_Bits = VLMU_GSM_Frame * 1250 + VLMU_GSM_Bit


deltaGSM = CP_Bits-VLMU_Bits


IF deltaGSM < −2710000 * 1250


 deltaGSM += 2715648 * 1250


ELSEIF deltaGSM > 2710000 * 1250


 deltaGSM −= 2715648 * 1250


ENDIF


DeltaTime = deltaGSM * SecPerGSMBit/(1+VLMU_Freq_error*1e.sup.−9)


GPS_TOW = VLMU_GPS_TOW + deltaTime * 1e.sup.6


GPS_Week = VLMU_GPS_Week


IF (GPS_TOW >= 604800 * 1e.sup.6)


 {GPS_TOW −= 604800 * 1e.sup.6


 GPS Week++


 }


ELSEIF (GPS_TOW < 0


 {GPS_TOW += 604800 * 1e.sup.6


 GPS_Week--


 }


time_uncertainty=VLMU_Time_Accuracy+time_mark_uncertainty.









In FIG. 5, a flow diagram 500 of offset determination is shown. A wireless handset 104 receives a GPS signal 114 at a GPS receiver in step 502. The wireless handset 104 also receives a communication signal 116 from the wireless network in step 504 that contains timing information. The controller then determines the time offset and/or drift between the clock at base station 106 sent in the received communication signal 116 and the GPS time sent in GPS signal 114 in step 506. The offset may then be sent back to the current base station 508.


Turning to FIG. 6, a flow diagram 600 of a wireless handset using offset determined in FIG. 5 is illustrated. A wireless handset 104 requests aiding from the geolocation server 108 in step 602, a message from the geolocation server 108 to the wireless handset is sent, step 604. The message identifies the GPS time with a specific GSM frame/bit, identified as “GSM Bit Y” in FIG. 4. The geolocation server 108 creates this message from earlier measurements made by this, or other, wireless handsets. When the message is received at the wireless handset 104, the CP section of the wireless handset 104 generates a time mark aligned with a (possibly) different GSM frame/bit, identified as “GSM Bit X” in FIG. 4, see step 606. In step 608, the CP section may also send a message to the GPS receiver identifying the GSM frame and bit number associated with the time mark, and the base station being used, as shown in Table 1. The GPS section of the wireless handset 104 propagates the GPS time from the bit identified in the message to the bit associated with the time mark, thus compensating for network delays and time errors caused by the geolocation service center server 108 in step 610. Because the wireless handset 104 location is unknown, there is an unknown transmission delay from the base station 106 to the wireless handset 104. This delay presents an unavoidable error in the received GPS time, but is limited by the typically small sizes of cellular radio sites.


The flow diagrams in FIG. 5 and FIG. 6 may be implemented in software or hardware or a combination of software and hardware. The software may be presented on a signal-bearing medium that contains machine-readable instructions such as magnetic tape, compact disc, paper punch cards, smart cards, or other optical, magnetic, or electrical digital storage device. A controller may execute the software presented on the signal-bearing medium. Examples of a controller may include a microprocessor, digital signal processor, digital circuits configured to function as a state machine, analog circuits configures to function as a state machine, a combination of any of the above configured to execute the programmed instructions, such as presented on the signal-bearing medium.


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. For example, the described implementation includes software but the invention may be implemented as a combination of hardware and software or in hardware alone. Note also that the implementation may vary between systems. The claims and their equivalents define the scope of the invention.

Claims
  • 1. A wireless mobile communication device, comprising: a communication receiver in the wireless mobile communication device;a positioning system receiver in the wireless mobile communication device;an absolute time signal received at the positioning system receiver of the wireless mobile communication device; a network time signal received at the communication receiver of the wireless mobile communication device;a controller in signal communication with the position system receiver and the communication receiver, where the controller is configured to determine an offset of the absolute time signal from the network time signal;a memory that stores the offset of the absolute time signal from the network time signal; anda transmitter in the wireless mobile communication device that transmits the offset for receipt by another wireless mobile communication device.
  • 2. The wireless mobile communication device of claim 1, where the absolute time signal is a Global Positioning System (GPS) clock signal.
  • 3. The wireless mobile communication device of claim 1, where the positioning system receiver is a Global Positioning System (GPS) receiver in receipt of the absolute time signal that is a GPS clock signal.
  • 4. The wireless mobile communication device of claim 3, comprising: a frequency error of a clock associated with the network time signal calculated by the controller.
  • 5. The wireless mobile communication device of claim 3, comprising: a drift rate determination made by the controller based on a plurality of offset measurements.
  • 6. The wireless mobile communication device of claim 3, where the transmitter transmits the offset for receipt by a base station.
  • 7. The wireless mobile communication device of claim 3, where the timing mark has a known relationship with the GPS clock signal.
  • 8. The wireless mobile communication device of claim 7, comprising: a frame and a bit number associated with the timing mark being sent to the GPS receiver.
  • 9. The wireless mobile communication device of claim 8, wherein the frame is a GSM frame.
  • 10. The wireless mobile communication device of claim 1, where the offset is transmitted over another communication network other than a communication network that provides service to the communication receiver.
  • 11. The wireless mobile communication device of claim 1, wherein the controller generates a timing mark, the timing mark being tagged by the positioning system receiver with an internal clock value wherein the timing mark has a known relationship with the absolute time signal.
  • 12. A method for wireless communication, comprising: receiving a network time signal over a first communication network at a communication receiver in a wireless mobile communication device;receiving an absolute time signal at a positioning system receiver in the wireless mobile communication device;determining an offset of the absolute time signal from the network time signal by a controller;storing in a memory the offset of the absolute time signal from the network time signal;transmitting, by a transmitter in the wireless mobile communication device, the offset for receipt by another wireless mobile communication device.
  • 13. The method for wireless communication of claim 12, where the absolute time signal is a Global Positioning System (GPS) clock signal.
  • 14. The method for wireless communication of claim 12, where the positioning system receiver is a Global Positioning System (GPS) receiver, the method comprising: receiving the absolute time signal that is a GPS clock signal.
  • 15. The method for wireless communication of claim 14, comprising: calculating a frequency error of a clock associated with the network time signal.
  • 16. The method for wireless communication of claim 14, comprising: determining a drift rate by the controller based upon multiple offset measurements.
  • 17. The method for wireless communication of claim 14, comprising: transmitting with a transmitter, the offset for receipt by a base station.
  • 18. The method of wireless communication of claim 14, where the timing mark has a known relationship with GPS clock signal.
  • 19. The method of wireless communication of claim 18, comprising: sending a frame and a bit number associated with the timing mark to the GPS receiver.
  • 20. The method for wireless communication of claim 12, where the offset is transmitted over a second communication network.
  • 21. The method for wireless communication of claim 12, comprising: generating a timing mark by the controller; andtagging the timing mark, by the position system receiver, with an internal clock value of the positioning system receiver, wherein the timing mark has a known relationship with the absolute time signal.
  • 22. An article, comprising: a non-transitory machine-readable storage medium comprising machine-readable instructions for:receiving a network time signal at a communication receiver in a wireless mobile communication device;receiving an absolute time signal at a positioning system receiver in the wireless mobile communication device;determining an offset of the absolute time signal from the network signal by a controller;storing in a memory the offset of the absolute time signal from the network time signal;transmitting by a transmitter in the wireless mobile communication device the offset for receipt by another wireless mobile communication device.
  • 23. The article of claim 22, where the absolute time signal is a Global Positioning System (GPS) clock signal.
  • 24. The article of claim 22, where the network time signal is a cellular telephone time signal.
  • 25. The article of claim 22, where the positioning system receiver is a Global Positioning System (GPS) receiver the method comprising: receiving the absolute time signal that is a GPS clock signal.
  • 26. The article of claim 25, comprising: machine-readable instructions for calculating a frequency error of a clock associated with the network time signal.
  • 27. The article of claim 25, comprising: machine-readable instructions for determining a drift rate by the controller based upon multiple offset measurements.
  • 28. The article of claim 25, comprising: machine-readable instructions for transmitting with a transmitter in the wireless mobile communication device, the offset for receipt by a base station.
  • 29. The article of claim 25, comprising: machine-readable instructions for generating a timing mark that the controller tags with an internal clock, where the timing mark has a known relationship with the GPS Clock Signal.
  • 30. The article of claim 29, comprising: machine-readable instructions for sending a frame and a bit number associated with the timing mark to the GPS receiver.
  • 31. The article of claim 22, where the offset is transmitted over another communication network other than a communication network that provides service to the communication receiver.
  • 32. The article of claim 22, comprising machine-readable instructions for: generating a timing mark by the controller; andtagging the timing mark, by the positioning system receiver, with an internal clock value of the positioning system receiver, wherein the timing mark has a known relationship with the absolute timing signal.
CROSS REFERENCE TO RELATED APPLICATIONS

This non-provisional application for patent is a divisional of patent application Ser. No. 11/205,510 filed Aug. 16, 2005, now U.S. Pat. No. 7,925,210, issued on Apr. 12, 2011, which is a continuation-in-part of patent application Ser. No. 10/154,138, filed May 21, 2002, now U.S. Pat. No. 7,877,104, issued on Jan. 25, 2011, and which further claims the benefit of U.S. Provisional Patent Application No. 60/292,774 filed on May 21, 2001, and the disclosure of each is herein incorporated by reference in its entirety.

US Referenced Citations (243)
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
5202829 Geier Apr 1993 A
5225842 Brown et al. Jul 1993 A
5293170 Lorenz et al. Mar 1994 A
5296131 Raterman 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
5347536 Meehan Sep 1994 A
5379224 Brown et al. Jan 1995 A
5402347 McBurney et al. Mar 1995 A
5416712 Geier et al. May 1995 A
5416808 Witsaman et al. May 1995 A
5420593 Niles May 1995 A
5440313 Osterdock et al. Aug 1995 A
5450344 Woo et al. Sep 1995 A
5481258 Fawcett et al. Jan 1996 A
5504684 Lau et al. Apr 1996 A
5508708 Ghosh et al. Apr 1996 A
5592173 Lau et al. Jan 1997 A
5608412 Welles et al. Mar 1997 A
5613193 Ishikawa et al. Mar 1997 A
5625668 Loomis et al. Apr 1997 A
5663734 Krasner Sep 1997 A
5663735 Eshenbach Sep 1997 A
5697051 Fawcett Dec 1997 A
5736964 Ghosh et al. Apr 1998 A
5739786 Greenspan et al. Apr 1998 A
5764188 Ghosh et al. Jun 1998 A
5768266 Thompson et al. Jun 1998 A
5774829 Cisneros et al. Jun 1998 A
5781156 Krasner Jul 1998 A
5784695 Upton et al. Jul 1998 A
5786789 Janky Jul 1998 A
5790939 Malcolm et al. Aug 1998 A
5809397 Harthcock et al. Sep 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
5936572 Loomis et al. Aug 1999 A
5943363 Hanson et al. Aug 1999 A
5945944 Krasner Aug 1999 A
5945948 Buford et al. Aug 1999 A
5963582 Stansell et al. 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
6018667 Ghosh et al. Jan 2000 A
6041222 Horton et al. Mar 2000 A
6047017 Cahn et al. Apr 2000 A
6052081 Krasner Apr 2000 A
6054950 Fontana Apr 2000 A
6061018 Sheynblat May 2000 A
6061337 Light et al. May 2000 A
6064336 Krasner May 2000 A
6104338 Krasner Aug 2000 A
6104340 Krasner Aug 2000 A
6107960 Krasner Aug 2000 A
6111540 Krasner Aug 2000 A
6131067 Girerd et al. Oct 2000 A
6133871 Krasner Oct 2000 A
6133873 Krasner Oct 2000 A
6133874 Krasner Oct 2000 A
6150980 Krasner Nov 2000 A
6166691 Lindqvist Dec 2000 A
6192247 Dillon et al. Feb 2001 B1
6208871 Hall et al. Mar 2001 B1
6236359 Watters et al. May 2001 B1
6240276 Camp, Jr. May 2001 B1
6249245 Watters et al. Jun 2001 B1
6285316 Nir et al. Sep 2001 B1
6308076 Hoirup et al. Oct 2001 B1
6331836 Jandrell Dec 2001 B1
6332086 Avis Dec 2001 B2
6356740 Malcolm et al. Mar 2002 B1
6389291 Pande et al. May 2002 B1
6427120 Garin et al. Jul 2002 B1
6430416 Loomis Aug 2002 B1
6433734 Krasner Aug 2002 B1
6433739 Soliman Aug 2002 B1
6438382 Boesch et al. Aug 2002 B1
6449290 Willars et al. Sep 2002 B1
6473030 McBurney et al. Oct 2002 B1
6490455 Park et al. Dec 2002 B1
6493539 Falco et al. Dec 2002 B1
6498585 Jandrell Dec 2002 B2
6519466 Pande et al. Feb 2003 B2
6539004 Sawyer Mar 2003 B1
6539217 Syed et al. Mar 2003 B1
6542823 Garin et al. Apr 2003 B2
6564057 Chun et al. May 2003 B1
6603978 Carlsson et al. Aug 2003 B1
6611755 Coffee et al. Aug 2003 B1
6650285 Jandrell Nov 2003 B2
6665332 Carlson et al. Dec 2003 B1
6665541 Krasner et al. Dec 2003 B1
6678510 Syrjarinne et al. Jan 2004 B2
6684158 Garin et al. Jan 2004 B1
6703971 Pande et al. Mar 2004 B2
6704547 Kuwahara et al. Mar 2004 B2
6708019 McLain et al. Mar 2004 B2
6748202 Syrjarinne et al. Jun 2004 B2
6771625 Beal Aug 2004 B1
6847826 Wesby et al. Jan 2005 B1
6850557 Gronemeyer Feb 2005 B1
6865380 Syrjarinne Mar 2005 B2
6873612 Steer et al. Mar 2005 B1
6891500 Hall et al. May 2005 B2
6901264 Myr May 2005 B2
6903683 Nicholson Jun 2005 B1
6907224 Younis Jun 2005 B2
6915208 Garin et al. Jul 2005 B2
6925292 Syrjarinne et al. Aug 2005 B2
6937872 Krasner Aug 2005 B2
6952158 Kennedy, Jr. Oct 2005 B2
6985542 Nir et al. Jan 2006 B1
6987979 Carlsson Jan 2006 B2
6999778 DiBuduo Feb 2006 B2
7013111 Kuwahara et al. Mar 2006 B2
7013147 Kuwahara et al. Mar 2006 B1
7039098 Younis May 2006 B2
7053824 Abraham May 2006 B2
7057553 Jandrell Jun 2006 B2
7057556 Hall et al. Jun 2006 B2
7065374 Lipp et al. Jun 2006 B2
7085546 Syrjarinne et al. Aug 2006 B2
7139225 Farmer Nov 2006 B2
7146516 Dhupar et al. Dec 2006 B2
7151944 Hashem et al. Dec 2006 B2
7154436 Chadha Dec 2006 B1
7164117 Breed Jan 2007 B2
7171225 Krasner Jan 2007 B2
7174243 Lightner et al. Feb 2007 B1
7194017 Hervey, Jr. Mar 2007 B2
7215967 Kransmo et al. May 2007 B1
7218938 Lau et al. May 2007 B1
7236883 Garin et al. Jun 2007 B2
7254402 Vayanos Aug 2007 B2
7283091 Loomis Oct 2007 B1
7295156 Loomis Nov 2007 B2
7302225 Younis Nov 2007 B2
7304606 Pande et al. Dec 2007 B2
7324465 Lim et al. Jan 2008 B2
7355995 Ogino et al. Apr 2008 B2
7373175 Carter et al. May 2008 B2
7412266 Underbrink Aug 2008 B2
7471244 Omura et al. Dec 2008 B2
7551129 Farmer Jun 2009 B2
7551888 Kopra et al. Jun 2009 B2
7554487 Abraham Jun 2009 B2
7577448 Pande et al. Aug 2009 B2
7620403 Korneluk et al. Nov 2009 B2
7639179 Hansen et al. Dec 2009 B2
7656350 Abraham Feb 2010 B2
7679554 Hwang et al. Mar 2010 B1
7701387 Syrjarinne Apr 2010 B2
7706754 Krasner Apr 2010 B2
7711376 Ogino May 2010 B2
7801108 Krasner Sep 2010 B2
7852267 Duffett-Smith et al. Dec 2010 B2
7877104 Turetzky Jan 2011 B2
7884762 Abraham Feb 2011 B2
7898983 Laroia et al. Mar 2011 B2
8289206 Wigren et al. Oct 2012 B2
20010002822 Watters et al. Jun 2001 A1
20010030625 Doles et al. Oct 2001 A1
20010039192 Osterling et al. Nov 2001 A1
20010052849 Jones Dec 2001 A1
20020111171 Boesch et al. Aug 2002 A1
20020146982 McLain et al. Oct 2002 A1
20020160788 Duffett-Smith et al. Oct 2002 A1
20020168988 Younis Nov 2002 A1
20030026225 Ogino et al. Feb 2003 A1
20030109264 Syrjarinne et al. Jun 2003 A1
20030151506 Luccketti Aug 2003 A1
20030162550 Kuwahara et al. Aug 2003 A1
20050003833 Younis Jan 2005 A1
20050037724 Walley et al. Feb 2005 A1
20050062643 Pande et al. Mar 2005 A1
20050066373 Rabinowitz et al. Mar 2005 A1
20050080561 Abraham et al. Apr 2005 A1
20050162306 Babitch et al. Jul 2005 A1
20050231425 Coleman et al. Oct 2005 A1
20050265306 Schrum et al. Dec 2005 A1
20060013347 Brown Jan 2006 A1
20060038719 Pande et al. Feb 2006 A1
20060119505 Abraham Jun 2006 A1
20060234724 Syrjarinne et al. Oct 2006 A1
20060290566 Syrjarinne et al. Dec 2006 A1
20070159387 Syrjarinne et al. Jul 2007 A1
20070239356 Woz Oct 2007 A1
20080084850 Chen et al. Apr 2008 A1
20080161014 Monnerat Jul 2008 A1
20090010231 Laroia et al. Jan 2009 A1
20090010232 Laroia et al. Jan 2009 A1
20090010244 Laroia et al. Jan 2009 A1
20090013081 Laroia et al. Jan 2009 A1
20090135887 Andersson et al. May 2009 A1
20090153398 Hani et al. Jun 2009 A1
20090153399 Abraham et al. Jun 2009 A1
20090219198 Zhang et al. Sep 2009 A1
20090315768 Abraham Dec 2009 A1
20100225537 Abraham Sep 2010 A1
20100328152 Abraham et al. Dec 2010 A1
20110158114 Novak et al. Jun 2011 A1
Foreign Referenced Citations (7)
Number Date Country
0511741 Nov 1992 EP
2115195 Jan 1983 GB
58-105632 Jun 1983 JP
7-36035 May 1986 JP
4-326079 Nov 1992 JP
WO 9011652 Oct 1990 WO
WO 0178260 Oct 2001 WO
Non-Patent Literature Citations (11)
Entry
Non-Final Rejection mailed Jun. 27, 2008 in U.S. Appl. No. 11/205,510.
Final Rejection mailed Mar. 17, 2009 in U.S. Appl. No. 11/205,510.
Non-Final Rejection mailed Dec. 4, 2009 in U.S. Appl. No. 11/205,510.
Final Rejection mailed Jul. 16, 2010 in U.S. Appl. No. 11/205,510.
Notice of Allowance mailed Dec. 9, 2010 in U.S. Appl. No. 11/205,510.
Non-Final Rejection mailed Sep. 10, 2004 in U.S. Appl. No. 10/154,138.
Final Rejection mailed Aug. 16, 2005 in U.S. Appl. No. 10/154,138.
Non-Final Rejection mailed Jul. 5, 2006 in U.S. Appl. No. 10/154,138.
Non-Final Rejection mailed Mar. 7, 2007 in U.S. Appl. No. 10/154,138.
Final Rejection mailed Sep. 24, 2007 in U.S. Appl. No. 10/154,138.
Notice of Allowance mailed Sep. 29, 2010 in U.S. Appl. No. 10/154,138.
Related Publications (1)
Number Date Country
20110183606 A1 Jul 2011 US
Provisional Applications (1)
Number Date Country
60292774 May 2001 US
Divisions (1)
Number Date Country
Parent 11205510 Aug 2005 US
Child 13071310 US
Continuation in Parts (1)
Number Date Country
Parent 10154138 May 2002 US
Child 11205510 US