US20030134647A1

US20030134647A1 - Use of third party ultra-wideband devices to establish geo-positional data

Info

Publication number: US20030134647A1
Application number: US10/236,213
Authority: US
Inventors: John Santhoff; Rodolfo Arrieta
Original assignee: Pulse Link Inc
Current assignee: Intellectual Ventures Holding 81 LLC
Priority date: 2000-12-14
Filing date: 2002-09-06
Publication date: 2003-07-17
Also published as: JP2004516463A; EP1350399A1; CA2431115A1; US6519464B1; CN1486577A; EP1350399A4; AU2002229073A1; CN1232132C; WO2002049379A1

Abstract

A system, method and article of manufacture are provided for determining a location of a wireless device in a wireless communication system. In one embodiment of the present invention, an initial request is transmitted to wireless devices having known locations for positioning information so that a location can be determined for a first wireless device having an undetermined location. Those wireless devices with known locations that receive the initial request in turn transmit positioning information to the first wireless device. If positioning information from less than a sufficient number of wireless devices with known locations is received by the first mobile wireless device, an additional request is then transmitted to other wireless devices. After responses to the request from one or more of these other wireless devices are received, communication then occurs with at least a portion of the responding wireless devices to obtain information relating to the distance between the first wireless device and the responding wireless devices. A location of the first wireless device is then estimated using the information obtained from the responding wireless devices.

Description

This is a continuation-in-part of co-pending application Ser. No. 09/745,498, titled “Use of Third Party Ultra-Wideband Devices to Establish Geo-Positional Data,” filed Dec. 22, 2000, which is based on U.S. provisional application serial No. 60/255,469, filed Dec. 13, 2000, titled “Ultra-Wideband Communication System and Method,” both of which are incorporated in their entirety by this reference.[0001]

FIELD OF THE INVENTION

The present invention relates generally to wireless communication systems and, more particularly, to accurate geo-location of ultra-wideband transceivers.

BACKGROUND OF THE INVENTION

Ultra-wideband communication systems and devices benefit from the tremendous potential for geo-positional accuracy of ultra-wideband technology. As a separate issue, the FCC has recently required all existing cellular technology providers to employ some means of geographically locating all cellular phones for emergency purposes. This initiative has been termed “e911” and will be a requirement of future cellular technologies. Thus, it is foreseeable that the same demands will be placed on future ultra-wideband devices.

Conventionally, ultra-wideband geo-positional information may be obtained by triangulating signals from three separate ultra-wideband transmission towers whose fixed position is known. However, it is foreseeable that a mobile ultra-wideband device may not always be within range of three fixed transmission towers. In such a situation, the ultra-wideband device's geo-location (i.e., geo-position) may not be determined through the conventional methods.

Thus, it may be appreciated that a geo-location method that takes advantage of other mobile ultra-wideband devices of known location to derive the position of the ultra-wideband device that is in need of location has a better chance of success in these circumstances.

SUMMARY OF THE INVENTION

Alternatively, in some circumstances, the responding wireless devices may simply provide a distance to the first wireless device. An example of such a circumstance is a lost child carrying the first wireless device and several searchers, each with a responding wireless device. In this example, the searchers are not interested in the geo-position of the child, but in the child's distance from each of the searchers. In this scenario a local triangulation without a geo-positional reference is all that is required to find the child. Thus, a location of the first wireless device is estimated using the information (distance or location) obtained from the responding wireless devices and the positioning information received from the wireless devices with known locations.

In one aspect of the present invention, at least a portion of the wireless devices may comprise ultra-wideband devices. In a further aspect of the present invention, the additional request may be retransmitted. In such an aspect, the additional request may also be retransmitted at a higher power level if an insufficient number of responses are received in response to the previous request.

In another embodiment of the present invention, if positioning information is received from a sufficient number of wireless devices with known locations, then the location of the first wireless device may be determined utilizing just the information obtained from the wireless devices with known locations. In yet another embodiment of the present invention, the location of the first wireless device may be estimated using only the information obtained from the other wireless devices.

These and other features and advantages of the present invention will be appreciated from review of the following detailed description of the invention, along with the accompanying figures in which like reference numerals refer to like parts throughout.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other features, aspects and advantages are better understood from the following detailed description, appended claims, and accompanying drawings where: [0011]
FIG. 1 is a schematic diagram of an exemplary ultra-wideband communication system capable of utilizing a multiple access scheme in accordance with an embodiment of the present invention; [0012]
FIG. 2 is a schematic diagram of an ultra-wideband geo-positional model; [0013]
FIG. 3 is a schematic block diagram of an ultra-wideband wireless device/transceiver in accordance with an embodiment of the present invention; [0014]
FIG. 4 is a schematic diagram of an ultra-wideband geo-positional model where multiple mobile devices collaborate with a requesting device to allow the requesting device to determine its location in accordance with an embodiment of the present invention; [0015]
FIG. 5 is a flowchart of a process for triangulation and storage of the geo-positional information based on three fixed position devices in accordance with an embodiment of the present invention; [0016]
FIG. 6 is a flowchart of a process for determining and storing a geographic location of a mobile wireless device in a wireless communication system in accordance with an embodiment of the present invention; [0017]
FIG. 7 is a flowchart processing replies from other wireless devices and [0018] 15 testing for data quantity and quality criteria in accordance with an embodiment of the present invention;
FIG. 8 is a flowchart of a process for performing a ranging dialogue to determine a requesting wireless device's distance from other replying wireless devices in accordance with an embodiment of the present invention; [0019]
FIG. 9 is a flowchart of a process for time correction in a requesting wireless device in accordance with an embodiment of the present invention; [0020]
FIG. 10 is a schematic diagram of a representative hardware environment in accordance with an embodiment of the present invention; [0021]
FIG. 11 is an illustration of different communication methods; [0022]
FIG. 12 is an illustration of two ultra-wideband pulses; and [0023]
FIG. 13 is a schematic diagram of an ultra-wideband geo-positional model where multiple mobile devices collaborate with a requesting device to allow the requesting device to determine its location and elevation in accordance with an embodiment of the present invention;[0024]
It will be recognized that some or all of the Figures are schematic representations for purposes of illustration and do not necessarily depict the actual relative sizes or locations of the elements shown. [0025]

DETAILED DESCRIPTION OF THE INVENTION

In the following paragraphs, the present invention will be described in detail by way of example with reference to the attached drawings. Throughout this description, the preferred embodiment and examples shown should be considered as exemplars, rather than as limitations on the present invention. As used herein, the “present invention” refers to any one of the embodiments of the invention described herein, and any equivalents. Furthermore, reference to various feature(s) of the “present invention” throughout this document does not mean that all claimed embodiments or methods must include the referenced feature(s). [0026]
Embodiments of the present invention use the known geographic position of one or more mobile wireless devices (in a preferred embodiment, ultra-wideband devices) to triangulate the position of additional mobile wireless devices that are not within geographic range of three mobile or fixed wireless devices such as fixed base stations and/or transmission towers, or mobile wireless devices. It should be understood that the mobile wireless devices whose positions are known need not be restricted just to handheld-type mobile devices. Such devices may also include ultra-wideband components in mobile phones, mobile internet devices, portable radios, personal data assistants, desktop computers or appliances located in homes, automobiles, office environments and other ultra-wideband devices. [0027]
A preferred embodiment of the present invention employs ultra-wideband, or impulse radio that comprises a multiplicity of electromagnetic pulses that are emitted at nanosecond or picosecond intervals (generally tens of picoseconds to a few nanoseconds in duration). For this reason, ultra-wideband is often called “impulse radio.” Because the excitation pulse is not a modulated waveform, UWB has also been termed “carrier-free” in that no apparent carrier frequency is evident in the radio frequency (RF) spectrum. That is, the UWB pulses are transmitted without modulation onto a sine wave carrier frequency, in contrast with conventional radio frequency technology. For example, ultra-wideband requires neither an assigned frequency nor a power amplifier. [0028]
Conventional radio frequency technology employs continuous sine waves that are transmitted with data embedded in the modulation of the sine waves' amplitude or frequency. For example, a conventional cellular phone must operate at a particular frequency band of a particular width in the total frequency spectrum. Specifically, in the United States, the Federal Communications Commission has allocated cellular phone communications in the 800 to 900 MHz band. Cellular phone operators use 25 MHz of the allocated band to transmit cellular phone signals, and another 25 MHz of the allocated band to receive cellular phone signals. [0029]
Another example of a conventional radio frequency technology is illustrated in FIG. 11. 802.11a, a wireless local area network (LAN) protocol, transmits radio frequency signals at a 5 GHz center frequency, with a radio frequency spread of about 5 MHz. [0030]
In contrast, an UWB pulse may have a 1.8 GHz center frequency, with a frequency spread of approximately 4 GHz, as shown in FIG. 12, which illustrates two typical UWB pulses. FIG. 12 illustrates that the narrower the UWB pulse is in time, the higher its center frequency and the broader the spread of its frequency spectrum. This is because frequency is inversely proportional to the time duration of the pulse. A 600 picosecond UWB pulse will have about a 1.8 GHz center frequency, with a frequency spread of approximately 4 GHz. And a 300 picosecond UWB pulse will have about a 3 GHz center frequency, with a frequency spread of approximately 8 GHz. Thus, UWB pulses generally do not operate within a specific frequency, as shown in FIG. 11. And because UWB pulses are spread across an extremely wide frequency range, UWB communication systems allow communications at very high data rates, such as 100 megabits per second or greater. [0031]
Also, because the UWB pulse is spread across an extremely wide frequency range, the power sampled at a specific frequency is very low. For example, a UWB one-watt signal of one nano-second duration spreads the one-watt over the entire frequency occupied by the pulse. At any instantaneous frequency, such as at the carrier frequency of a 802.11 a system, the UWB pulse power present is about one nano-watt (for a frequency band of 1 GHz). This is well within the noise floor of the 802.11a system and therefore does not interfere with the transmission of the 802.11a signals. Generally, the multiplicity of UWB pulses are transmitted at relatively low power (when sampled at a specific frequency), for example, at less than −30 power decibels to 60 power decibels. [0032]
FIG. 1 is a flowchart of a [0033] process 100 for determining a geographic location of a mobile wireless device having an undetermined/unknown geographic location in a wireless communication system in accordance with an embodiment of the present invention. In operation 102, at least one initial request is transmitted from a first mobile wireless device having an undetermined/unknown geographic location to fixed position wireless devices having known geographic locations (e.g., such as base stations and/or transmission towers) for positioning information for determining a geographic location of the first mobile wireless device. Those fixed position wireless devices with known geographic locations that receive the initial request (i.e., in the communication range of the first mobile wireless device) transmit, in response, positioning information to the first mobile wireless device with the undetermined geographic location (Note: for purposes of this portions of the description, communication range may be defined as a region inside which wireless communication with the first mobile wireless device may be achieved).
If positioning information from less than a sufficient number of fixed position wireless devices of known geographic location is received by the first mobile wireless device (e.g., such as when less than the sufficient number of fixed position wireless devices are in the communication range of the first mobile wireless device), then in [0034] operation 104, the first mobile wireless device then transmits an additional request for responses/replies from other mobile wireless devices in the communication range of the first mobile wireless device. In one aspect of the present invention, at least a portion of the transmitted requests may be coded (such as in the form of a key sequence request). Responses to the request are then received by the first wireless device from one or more other mobile wireless devices in the communication range in operation 106. Communication is then initiated in operation 108 with at least a portion of the responding other mobile wireless devices to obtain information (i.e., data) relating to the distance between the first mobile wireless device and the responding other mobile wireless devices communicating with the first mobile wireless device.
In [0035] operation 110, a position/location of the first mobile wireless device is 20 then estimated with a triangulation method using the information obtained from the responding other mobile wireless device communicating with the first wireless device and (if any was received by the first mobile wireless device) positioning information received from the less than sufficient number of fixed position wireless devices with known geographic locations.
In an aspect of the present invention, the sufficient number of fixed position wireless devices with known geographic locations may comprises at least three fixed position wireless devices with known geographic locations. In another aspect of the present invention, the additional request (see operation [0036] 104) may be re-transmitted periodically a predetermined number of times. In such an aspect, the additional request may be re-transmitted at a higher power level (i.e., to increase the range that the additional request is transmitted from the first mobile wireless device) if an insufficient number of responses are received (after a predetermined amount of time) in response to the previous transmission of the additional request.
FIG. 2 is a schematic diagram of an ultra-wideband geo-[0037] positional model 200 where fixed, known position wireless devices such as transmitters/ base stations 202, 204, 206 collaborate with a requesting wireless device 208 to allow the requesting device to determine its location in accordance with an embodiment of the present invention. One feature of ultra-wideband communication systems is that highly accurate geographical positional information may be discernable from signals received from at least three ultra-wideband transmitters (e.g., 202, 204, 206) having known geographical positions. Typically, a device/transceiver (e.g., 208) having an unknown/undetermined location receives ultra-wideband signals from three fixed ultra-wideband transmitters, with the signals sent from each transmitter embedding its time of transmission and the geographical position of each respective transmitter. Using the known position of each fixed transmitter, and measuring the slight timing variations between received signals, the device with an unknown geographical location can triangulate and accurately determine its geographical position. Using such triangulation procedures, an ultra-wideband device can determine its geographical position to within a few centimeters.
As previously mentioned, in an aspect of the preset invention, the wireless devices may comprise impulse radio communication devices such as, for example ultra-wideband radio (also know as digital pulse wireless) communication devices. FIG. 3 is a schematic block diagram of an ultra-wideband wireless device/[0038] transceiver 300 in accordance with an embodiment of the present invention. The device 300 has a plurality of components comprising logic (i.e., circuitry), software, or some combination of logic and software. In particular, the device 300 includes a transmitter and a receiver components 302, 304 capable of transmitting and receiving wireless signals 306, 308 (preferably ultra-wideband radio communication signals) respectively. In one embodiment, the signals may carry digital data communication information which may be packetized according to known techniques.
The transmitter and a [0039] receiver components 302, 304 may also be coupled to additional components 310 included in the device 300. In an embodiment of the present invention, one of the additional components may comprise a location component 312. In an aspect of the present invention, the location component 312 may include a timing and location database controller 314 which manages and controls a timing and location database 316 in which information such a geo-positional may be stored.
In fixed ultra-wideband transmission towers/base stations, their geographic position is known and can be stored in local memory. In mobile [0040] ultra-wideband devices 300 that are within range of three or more fixed ultra-wideband transmission towers, geo-positional information can be actively recorded, updated and stored this in the Dynamic Timing and Location Database 316 of the device 300 on an ongoing basis. Active updating and recording of geo-positional information can occur automatically on a predetermined time interval, or queried on command.
For example, in an embodiment of the present invention, the [0041] location component 312 may receive signals from at least three other wireless devices and then use timing relationships and location information provided in these signals to accurately determine a location for the wireless device 300. With the exact location of the transceiver unit 300 known, and the location of the fixed transmitters known, the location component 312 may be able to precisely determine the distance from the wireless device 300 to the other wireless device. In some embodiments, this distance information, in turn, may be provided to the transmit component 302 so that it can be used to help more accurately adjust the level of power the transmit component uses to transmit the subsequent signals.
FIG. 4 is a schematic diagram of an ultra-wideband geo-[0042] positional model 400 where multiple mobile devices collaborate with a requesting device to allow the requesting device to determine its location in accordance with an embodiment of the present invention. In embodiments of the present invention, tertiary mobile wireless devices (e.g., wireless device 402) that are not within range of three or more towers (e.g., transmission towers 404, 406, 408, 410, 412, 414) can request the geo-positional information stored in the Timing and Location Database of mobile ultra-wideband devices (e.g., devices 416, 418, 420) that are in range and have already stored this information. Such tertiary mobile devices 402 can then use the results of their query of other mobile ultra-wideband devices to triangulate their own position.
In an embodiment of the present invention, the geographic location of the first mobile wireless device may be determined just from information obtained from the fixed position wireless devices with known geographic locations utilizing a triangulation method if positioning information is received by the first mobile wireless device from a sufficient number (or more) of fixed position wireless devices with known geographic locations (e.g., such as when the sufficient number of fixed position wireless devices with known geographic locations are in the communication range of the first mobile wireless device). FIG. 5 is a flowchart of a [0043] process 500 for triangulation and storage of the geo-positional information based on three fixed position devices in accordance with an embodiment of the present invention. When an individual mobile ultra-wideband device A requires a location determination in operation 502, it transmits a coded request (in the form of a key sequence) for the geo-position of three other ultra-wideband devices/towers whose position is known in operation 504. This request may be sent several times (polled) at a pre-selected lowest power setting. By starting key-sequence transmissions at the lowest possible power level, the key-sequence will only reach the smallest transmission range and potentially the smallest number of nearby ultra-wideband devices that might respond to the key sequence request for information. The awaited responses are received in a pre-identified communications channel or set of such channels. If device A is in range of three towers (see decision 506), then it triangulates its own position in operation 508 based on the responses and time stamps, and stores this information in its timing and location database 316 via its timing and location database controller 314.
The timing and [0044] location database 316 of the responding ultra-wideband device contains a position value and a time stamp that specifies the time that position value was obtained. In one implementation, the responding device may delay response to the requesting ultra-wideband device until after the responding ultra-wideband device has updated its own most recent geographic position. However, in a preferred implementation, the decision to use the position reported by the responding device lies with the requesting device. The requesting device makes this determination based on the time stamp and other information provided by the responding device. The moving/mobile nature of the responding ultra-wideband devices and the need to synchronize the requesting device with the responding devices also complicate the determination of location.
If the querying wireless device (i.e., device A) is determined not to be in range of at least three towers in [0045] decision 506, then other wireless devices (e.g., other mobile wireless devices) proximate to the querying device may be queried per operation 510. In one embodiment of the present invention, the location of the first mobile wireless device may be estimated with a triangulation method using only the information obtained from the at least a portion of the responding other mobile wireless device if no positioning information is received by the first mobile wireless device from fixed position wireless devices with known geographic locations (i.e., zero (0) fixed position wireless devices). FIG. 6 is a flowchart of a process for determining and storing a geographic location of a mobile wireless device in a wireless communication system per operation 510 in accordance with an embodiment of the present invention. FIG. 6 shows the overall position discovery algorithm based on a requesting mobile device's ability to contact a suitably large number of location-self-aware devices. As was the case in FIG. 5, the device acquiring location is referred to as device A in FIG. 6.
Device “A” first tries to communicate with three or more base stations in order to triangulate its position (per [0046] operations 504, 506, 508). Since the base stations have exact location information and highly accurate timekeeping hardware, this may be the most accurate method of position determination. If fewer than three base stations are available (per decision 506), the device (i.e., device A) starts the request for information from other mobile devices by transmitting a key-sequence at the lowest possible power level per operation 510. In operation 602, replies are processed and tested for data quality and quantity criteria (preferably utilizing the timing and location database and controller 316, 314). In one aspect, each responding device may be identified by its unique ID number. Additionally, the range of IDs for base stations may not overlap those of mobile devices. If there are no replies, or if the replies contain data of low accuracy, device A keeps on polling for respondents. If polling the preprogrammed number of times fails to generate any replies, the requesting device may then ramp up the transmit power. In operation 604, a ranging dialogue is performed to determine the requesting wireless device's distance from other replying wireless devices in order to permit the estimation of the requesting wireless device's position in operation 606 based on the determined distances weighted by their freshness using a triangulation method. In an embodiment of the present invention, a time stamp for the estimated position/location may be generated, and then the estimated position/location and the associated time stamp may be stored in a memory (such as in a timing and location database) of the first mobile wireless device utilizing a timing and location database controller of the first mobile wireless device.
FIG. 7 is a flowchart processing replies from other wireless devices and testing for data quantity and quality criteria per [0047] operation 604 of FIG. 6 in accordance with an embodiment of the present invention. As discussed previously, if device A is not in range of three towers, it then transmits the key sequence in order to locate other mobile devices per operation 510. As the other mobile devices respond, a dialogue is established between the requestor and each responding device to determine distance and clock disparity. If the requesting device does not receive a response in a reasonable time (in a preferred embodiment, up to 5 msec—depending on the environment), the requesting device will retry several times using the same power level and multiple access channels (see decision 702). If no devices have replied to this repeated polling, then a power ramping algorithm is initiated, and the keyed sequence is transmitted again at a higher power level (see operation 704). Once the maximum allowable power is reached without response (see decision 706), the requestor will switch to another multiple access channel in operation 708.
With continuing reference to FIG. 7, important data quality and quantity criteria are also used device A to determine the value of the data it receives. It should be noted that only other wireless devices that have acquired their position will respond to the query of [0048] operation 510. If there are no responses to the polling, device A boosts its output power level until another mobile device responds (per operation 708).
With reference to the YES path of [0049] decision 702, if a device proximate to the requesting device (i.e., device A) receives the request transmitted by device A and has acquired information concerning its own geographic position/location, then such a device may transmit a response to the device A (the responding mobile device will be referred to hereafter as device B). Device “B” may encode several pieces of information into its reply including, for example: (1) the freshness of its position information (i.e., how recently the position information was obtained and/or updated); (2) a time of receipt that the query from device A was received by device B; and (3) a time of reply that a reply to the to the query was transmitted from device B to device A. Upon receiving the reply, device A can decode the reply in order to obtain the encoded information in operation 710.
With continuing reference to FIG. 7, the information obtained from each reply to the request by device A can be tested to determine how much emphasis should put on the information provided in the response of the particular device B. In [0050] decision 712, the information from a device B may be tested to determine whether the position information of device B is stale (i.e., too old and/or has not been updated recently). Clearly, if device B has not updated its information in a long time (for example, in a preferred embodiment, longer than 100 msec), the location of device B may have incurred significant error.
Next, in [0051] decision 714, the information decoded from the response may be tested to determine if the delay taken by device B in responding to the request is above a predetermined threshold (e.g., in a preferred embodiment, greater than 50 msec). For example, if device B took an inordinate amount of time to process the query (hereafter referred to as processing time), device B may be overloaded and prone to thread conflicts that will induce timing errors. In such a case, device B's reply will not be as accurate as device A may require. After performing the tests in decisions 712 and 714, a subsequent determination is made by device A as to whether the replies of three or more devices (i.e., three or more device B's) have been received by device A in decision 716. If three or more device B's have replied and at least three of the replies pass the tests set forth in decisions 712 and 714 (see the YES paths of decisions 712 and 714), then the dialog to determine device A's distance from three other devices may be executed per the YES path of decision 716 and operation 604. Conversely, if the information of a reply fails either of the tests (see the NO paths of decisions 712 and 714), or the replies of less than three device B's have past the tests, then per operation 718, a polling sequence for other devices is initiated.
There are several circumstances where distance calculation based on nearby devices may be prone to certain types of error. For some responding devices the processing delay experienced by device B will be a multiple of the signal's propagation delay. In such cases, the response by “B” may be degraded by simultaneous occurring multi-path reflections from the original query. In such cluttered environments, where reflection of the query may return to “A” at the same time as the reply from “B”, it becomes necessary to re-query “B” and notify it of the multi-path duration. Once “B” receives this information it can resubmit its reply so it will not be degraded by multi-path. On the other hand, if “A” calculates device B to be very far away, then the possibility increases that the reception is not direct line, and significant error is highly probable. [0052]
Once three or more devices have replied, then an estimated position can be obtained per [0053] 606. If more than three devices reply to the query, a determination can be made based on the information provided by the responding devices as to the quality of the estimated distances. Any devices over the required three can be graded and then added to the estimate weighted by a quality factor calculated from the time of last update, chance of multi-path interference, replier overload, and distance degradation.
In yet another aspect of the present invention, the obtained information relating to the distance between the first mobile wireless device and the portion of the responding other mobile wireless devices may include a calculated distance between the first mobile wireless device and the portion of the responding other mobile wireless devices, a transmission time, and a scaling factor. [0054]
FIG. 8 is a flowchart of a process for performing a ranging dialogue to determine a requesting wireless device's distance from other replying wireless devices per [0055] operation 604 in accordance with an embodiment of the present invention. FIG. 8 shows the dialogue that must go on in order for device A to determine its position with respect to device B. In operation 802, device A starts a timer that is used to count the clock ticks between the time device A sends a query and the time “A” receives a response from “B”. This time is denoted as “Δ_tsrA” (or “DtrsA”). This time includes the round trip signal time plus the time it takes for device B to respond to the query (a substantial delay given that device B is likely to be busy at the time the query is received). Since the oscillator on device A may have undergone some drift since the last time device A's position was determined, Δ_tsrAis only an estimate of the true round trip time.
Once device B receives the query in [0056] operation 804, device B marks the receipt time, starts the receive-send delay timer and continues processing those threads that were being processed at the time it received the query until it has enough time to respond to the query (see operations 806 and 808). When device B is ready to respond to the query, “B” stops the timer and calculates the receive-send delay Δ_trsB(or “DtrsB”) and A's time scaling factor in operation 810.
In [0057] operation 812, device A receives the reply, stops the round trip timer, and calculates the round-trip time “Δ_trsA” (or “DtrsA”). Device A then encodes this value into a message to be sent to device B at its next “time beacon” mark in operation 814. A time beacon mark occurs at the end of a specified time period that starts with the sending of the original query. The time beacon period may either be a preprogrammed constant for both devices A and B, or its value may be transmitted by devices A to B in the initial query.
In [0058] operation 816, device B receives the message and decodes the round trip time. Device B then calculates the time difference between the original query and the reply at the “time beacon” mark to calculate the true beacon period (“DtbB”) (see operation 816). In operation 818, device B then uses the ratio of the beacon period preprogrammed in device A to the true beacon period as calculated by device B as a multiplier (i.e., the “scaling factor”) to correct the round trip time as calculated by device A. Once the actual time is obtained, the receive-send delay incurred by device B can be subtracted out to obtain the actual round trip propagation time. Device B then sends the scaling factor, transmission time and calculated distance to device A in operation 820. In operation 822, upon receipt, device A may use this information transmitted from device B for time correction.
FIG. 9 is a flowchart of a process for time correction in a requesting wireless device per [0059] operation 822 of FIG. 8 in accordance with an embodiment of the present invention. As set forth in FIG. 9, shows that as soon as device A receives the transmission from device B (see operation 902), device A resets its clock cycle counter in operation 904. Device A then decodes the transmission and extracts the parameters for storage in its timing and location database (see operation 906).
Besides updating its location, device A can use these parameters to 15 resynchronize its clock. In one aspect of the present invention, at least a portion of the obtained information (such as the transmission time and scaling factor) may be utilized to update an internal clock of the first mobile wireless device. In closer detail, this may be accomplished per [0060] operation 908 by calculating a Receipt Time using the following equation:
Receipt Time=(transmission time of device B+distance/speed of light)+(time required to process transmission and reset clock cycle counter),
where: [0061]
(time required to process transmission and reset clock cycle counter) (cycles required to process transmission and reset the clock cycle counter)*(scaling factor)
Device “A” then stores the calculated Receipt Time in [0062] operation 910. Subsequent time calculations by device A are then based on the following equation:
True Current Time=(value of clock cycle counter)*(scaling factor)+(Receipt Time)+(number of cycles to calculate and process (transmit, store, etc.) True Current Time)
In multi-user environments, it is feasible that dozens of ultra-wideband devices may be within transmit/receive range of the location-requesting ultra-wideband device. Simultaneous responses from all of these devices can “collide” and prove to be unintelligible to the requesting device. In an aspect of the present invention, a set of collision-avoidance schemes may be provided which are designed to reduce collisions when an individual ultra-wideband device requests geo-positional information from multiple nearby ultra-wideband devices in a multi-user environment. [0063]
Implementations of collision avoidance schemes may employ the following: [0064]
1. Pre-identification of several multiple access channels to be used for receiving responses to the geo-positional key sequence and assign one of these channels to each mobile device. This reduces but does not eliminate the possibility that multiple responses to the key sequence request will be received in the same channel; [0065]
2. Superposition of multiple coincident responses using pulse position modulation (a preferred modulation scheme) may lead to disallowed pulse adjacency at the receiver. If this happens, the requesting device may ignore the reply. The responding devices expect a rapid acknowledgement from the requesting device (up to 5 msec depending on the environment). The lack of a prompt acknowledgement from the requesting device may induce the responding devices to retransmit their responses using other pre-identified multiple access channels assigned for positional response information. To decrease the probability that second responses from multiple devices will interfere with each other, these multiple access channels can be chosen at random and/or the transmission can be postponed by random delays. These random factors can be obtained by using a random number generator where the seed is based on an individual device's unique identification code. The individual device's ID codes can also be used directly to institute a lag that is unique to each device; and [0066]
3. The geo-positional key sequence may be generated at the lowest possible power level, and the power level is increased only after between 3 and 10 polling sequences have been transmitted with no response. The power ramping and polling sequence proceeds until the first response is obtained or until the assigned maximum power level has been reached. The power level is increased gradually such that the potential number of new respondents is kept low while insuring the minimum number or respondents, three, is achieved as rapidly as possible. After maximum power is reached with no response, the ultra-wideband device will then switch channels and start the polling and power ramping sequence again at the lowest power setting. [0067]
Embodiments may also include a repetitive polling sequence that helps to assure that a potential respondent will be able to receive the request. Since the requesting device expect a rapid acknowledgement from the responding devices, if the requesting devices do not receive such an acknowledgement in a reasonable time (up to 5 msec depending on the environment), then the requester will retry up to 10 polling sequences before ramping up the power or moving to another multiple access channel. [0068]
Additionally, embodiments may provide a means to simultaneously synchronize the users clock and calculate the distance based on one round trip from the responding device. [0069]
Thus embodiments of the present invention may allow for the employment of geo-positional information in a broader range of environments. It uses and “piggybacks” the existence of multi-user environments to extend the capacity of the ultra-wideband system. It extends the capacity for acquisition of geo-positional information throughout a multi-user ultra-wideband environment. Aspects of the present invention may also help to reduce the probability of collisions in multi-user environments. The ability to extend geo-positional functionality under a wider variety of circumstances may become a future requirement of FCC regulations under extension of their “e911” policy. [0070]
Referring to FIG. 13, a schematic diagram of an ultra-wideband geo-[0071] positional model 1100 is illustrated. Multiple ultra-wideband (UWB) devices collaborate with a requesting UWB device to enable the requesting device to determine its location and elevation in accordance with an embodiment of the present invention. One feature of this embodiment of the present invention is that an elevation of the UWB requesting unit 1105 can be determined. This can be helpful in many situations, for example, where the location of an individual in a high-rise building must be determined. In addition, one feature of this embodiment of the present invention is that it accounts for situations where the elevation between an UWB requesting unit 1105 is not the same as the elevation of the other UWB units 1110.
Referring again to FIG. 13, the location of an [0072] UWB requesting unit 1105 can be determined by measuring the time delay in a signal transmitted by the UWB requesting unit 1105 to each of the UWB units 1110. The UWB units 1110 may have either a fixed location or they may be mobile UWB units. One method of finding the location of the UWB requesting unit 1105 employs radio triangulation and calculates distance from the amount of time required for a signal transmitted by the UWB requesting unit 1105 to reach each of the UWB units 1110. Specifically, the distance between the UWB requesting unit 1105 and each of the UWB units 1110 can be determined based on the amount of time it takes for a signal to travel between the devices. Each distance generates a radius, with each UWB unit 1110 at the center of a circle defined by each radius. The intersection of the three circles defines the location of the UWB requesting unit 1105.
An alternative technique to determine a location of an [0073] UWB requesting unit 1105 may employ two directional antennas that may be incorporated into the UWB units 1110. For example, a phased array antenna or other type of antenna capable of determining direction may be employed and only two antennas would be required to determine the location of an UWB requesting unit 1105. This is because a point (the UWB requesting unit 1105) can be found at the intersection of two arcs formed by the distance and direction information supplied by the UWB units 1110.
As discussed above, the location of the [0074] UWB requesting unit 1105 can also be determined by obtaining information from other devices not initially queried. With reference to FIG. 4, if an initial request transmitted by the UWB requesting unit 1105 does not result in a sufficient amount of data to generate a location, a second request for information from other UWB units may be transmitted. These tertiary devices, fixed or mobile, may then submit information to the UWB units 1110 which will then relay the information to the UWB requesting unit 1105, or the tertiary devices may submit the information directly to the UWB requesting unit 1105.
Again referring to FIG. 13, a method of determining an elevation of an [0075] UWB requesting unit 1105 will now be described. As shown in the Figure, a calculated distance from each UWB unit 1110 may result in three different elevation error points 1115. This may occur when an UWB requesting unit 1105 transmits a request to the UWB units 1110 to determine a location of the UWB requesting unit 1105, and the UWB requesting unit 1105 is at a different elevation than the UWB units 1110. The elevation error points 1115 represent distances that are beyond the actual location of the UWB requesting unit 1105. The additional distance reflects the elevation difference between the UWB requesting unit 1105 and the UWB units 1110.
However, one embodiment of the present invention includes computer logic or computer readable program code to determine a position and elevation of an [0076] UWB requesting unit 1105 when the elevation of the UWB requesting unit 1105 is different than the elevation of the UWB units 1110. One method involves the use of the Pythagorean theorem. This method employs the total distance from a UWB unit 1100 to the elevation error point 1115 as the hypotenuse of a triangle. Another side of the triangle is determined by taking the difference between the distance from the UWB requesting unit 1105 and the elevation error point 1115 and subtracting that distance from the distance between the UWB unit 1100 and the elevation error point 1115. With two sides of an imaginary triangle determined, the third side of the triangle can be found using the Pythagorean theorem. In the present invention, the third side of the triangle represents the elevation of the UWB requesting unit 1105.
In a preferred embodiment of the present invention, the Pythagorean calculation described above is performed three times, using the distance data from each of the three [0077] UWB units 1100 to their respective elevation error points 1115. Thus, the elevation of the UWB requesting unit 1105 is found, and determining the elevation of the UWB requesting unit 1105 eliminates the elevation error and the substantially precise location of the UWB requesting unit 1105 is resolved.
The above-described calculations require an approximate location of the [0078] UWB requesting unit 1105. One embodiment of the present invention determines a centroid of the elevation error area 1120. The centroid of the elevation error area 1120 is then used as an approximate location of the UWB requesting unit 1105. The elevation error area 1120 comprises an area defined by three imaginary lines joining the three elevation error points 1115, and the centroid is the point within the area at which the center of mass would be if the area had a mass.
Alternative methods of determining an approximate location of the [0079] UWB requesting unit 1105 may employ a variety of other optimization techniques, such as adaptive neural networks, or other methods available to those skilled in the art.
As also discussed above, if an insufficient amount of information is received by the [0080] UWB requesting unit 1105 from the UWB units 1110, a second request may be transmitted by the UWB requesting unit 1105 to other more-distant UWB units that can then supply the information necessary to fix the elevation and location of the UWB requesting unit 1105.
In addition, an alternative embodiment to the present invention may include computer logic or computer programs that access a terrain elevation database, such as topographical maps, terrain maps or other elevation information to determine an elevation of a [0081] UWB requesting unit 1105. In addition, a historical map or historical information based on previous elevation determinations in the area of the UWB requesting unit 1105 may also be accessed to determine an elevation of the UWB requesting unit 1105. As discussed above, one feature of the present invention is that a UWB requesting unit 1105 can determine its elevation based on information obtained from either local UWB units 1110 or more-distant units, that directly communicate with the UWB requesting unit 1105, or that are accessed via the UWB units 1110. These more-distant units create an ad hoc network to provide a sufficient amount of information to determine the elevation of the UWB requesting unit 1105.
FIG. 10 illustrates a representative hardware environment [0082] 1000 by which embodiments of the present invention may be carried out is depicted in FIG. 10. In the present description, the various sub-components of each of the components may also be considered components of the system. For example, particular software modules executed on any component of the system may also be considered components of the system. The hardware configuration 1000 illustrated in FIG. 10 includes a central processing unit 1002, such as a microprocessor, and a number of other units interconnected via a system bus 1004.
The hardware configuration [0083] 1000 shown in FIG. 10 includes a Random Access Memory (RAM) 1006, Read Only Memory (ROM) 1008, an 110 adapter 1010 for connecting peripheral devices such as disk storage units 1012 to the bus 1004, a user interface adapter 1014 for connecting a keyboard 1016, a mouse 1018, a speaker 1020, a microphone 1022, and/or other user interface devices such as a touch screen (not shown) to the bus 1004, communication adapter 1024 for connecting the hardware configuration to a communication network 1026 (e.g., a data processing network) and a display adapter 1028 for connecting the bus 1004 to a display device 1030.
An embodiment of the present invention may be written using JAVA, C, and the C++ language and utilize object oriented programming methodology. Object oriented programming (OOP) has become increasingly used to develop complex applications. As OOP moves toward the mainstream of software design and development, various software solutions require adaptation to make use of the benefits of OOP. A need exists for these principles of OOP to be applied to a messaging interface of an electronic messaging system such that a set of OOP classes and objects for the messaging interface can be provided. [0084]
OOP is a process of developing computer software using objects, including the steps of analyzing the problem, designing the system, and constructing the program. An object is a software package that contains both data and a collection of related structures and procedures. Since it contains both data and a collection of structures and procedures, it can be visualized as a self-sufficient component that does not require other additional structures, procedures or data to perform its specific task. OOP, therefore, views a computer program as a collection of largely autonomous components, called objects, each of which is responsible for a specific task. This concept of packaging data, structures, and procedures together in one component or module is called encapsulation. [0085]
In general, OOP components are reusable software modules which present an interface that conforms to an object model and which are accessed at run-time through a component integration architecture. A component integration architecture is a set of architecture mechanisms which allow software modules in different process spaces to utilize each others capabilities or functions. This is generally done by assuming a common component object model on which to build the architecture. It is worthwhile to differentiate between an object and a class of objects at this point. An object is a single instance of the class of objects, which is often just called a class. A class of objects can be viewed as a blueprint, from which many objects can be formed. [0086]
OOP allows the programmer to create an object that is a part of another object. For example, the object representing a piston engine is said to have a composition-relationship with the object representing a piston. In reality, a piston engine comprises a piston, valves and many other components; the fact that a piston is an element of a piston engine can be logically and semantically represented in OOP by two objects. [0087]
OOP also allows creation of an object that “depends from” another object. If there are two objects, one representing a piston engine and the other representing a piston engine wherein the piston is made of ceramic, then the relationship between the two objects is not that of composition. A ceramic piston engine does not make up a piston engine. Rather it is merely one kind of piston engine that has one more limitation than the piston engine; its piston is made of ceramic. In this case, the object representing the ceramic piston engine is called a derived object, and it inherits all of the aspects of the object representing the piston engine and adds further limitation or detail to it. The object representing the ceramic piston engine “depends from” the object representing the piston engine. The relationship between these objects is called inheritance. [0088]
When the object or class representing the ceramic piston engine inherits all of the aspects of the objects representing the piston engine, it inherits the thermal characteristics of a standard piston defined in the piston engine class. However, the ceramic piston engine object overrides these ceramic specific thermal characteristics, which are typically different from those associated with a metal piston. It skips over the original and uses new functions related to ceramic pistons. Different kinds of piston engines have different characteristics, but may have the same underlying functions associated with it (e.g., how many pistons in the engine, ignition sequences, lubrication, etc.). To access each of these functions in any piston engine object, a programmer would call the same functions with the same names, but each type of piston engine may have different/overriding implementations of functions behind the same name. This ability to hide different implementations of a function behind the same name is called polymorphism and it greatly simplifies communication among objects. [0089]
With the concepts of composition-relationship, encapsulation, inheritance and polymorphism, an object can represent just about anything in the real world. In fact, one's logical perception of the reality is the only limit on determining the kinds of things that can become objects in object-oriented software. Some typical categories are as follows: [0090]
Objects can represent physical objects, such as automobiles in a traffic-flow simulation, electrical components in a circuit-design program, countries in an economics model, or aircraft in an air-traffic-control system. [0091]
Objects can represent elements of the computer-user environment such as windows, menus or graphics objects. [0092]
An object can represent an inventory, such as a personnel file or a table of the latitudes and longitudes of cities. [0093]
An object can represent user-defined data types such as time, angles, and complex numbers, or points on the plane. [0094]
With this enormous capability of an object to represent just about any logically separable matters, OOP allows the software developer to design and implement a computer program that is a model of some aspects of reality, whether that reality is a physical entity, a process, a system, or a composition of matter. Since the object can represent anything, the software developer can create an object which can be used as a component in a larger software project in the future. [0095]
If 90% of a new OOP software program consists of proven, existing components made from preexisting reusable objects, then only the remaining 10% of the new software project has to be written and tested from scratch. Since 90% already came from an inventory of extensively tested reusable objects, the potential domain from which an error could originate is 10% of the program. As a result, OOP enables software developers to build objects out of other, previously built objects. [0096]
This process closely resembles complex machinery being built out of assemblies and subassemblies. OOP technology, therefore, makes software engineering more like hardware engineering in that software is built from existing components, which are available to the developer as objects. All this adds up to an improved quality of the software as well as an increased speed of its development. [0097]
Programming languages are beginning to fully support the OOP principles, such as encapsulation, inheritance, polymorphism, and composition-relationship. With the advent of the C++ language, many commercial software developers have embraced OOP. C++ is an OOP language that offers a fast, machine-executable code. Furthermore, C++ is suitable for both commercial-application and systems-programming projects. For now, C++ appears to be the most popular choice among many OOP programmers, but there is a host of other OOP languages, such as Smalltalk, Common Lisp Object System (CLOS), and Eiffel. Additionally, OOP capabilities are being added to more traditional popular computer programming languages such as Pascal. [0098]
The benefits of object classes can be summarized, as follows: [0099]
Objects and their corresponding classes break down complex programming problems into many smaller, simpler problems. [0100]
Encapsulation enforces data abstraction through the organization of data into small, independent objects that can communicate with each other. Encapsulation protects the data in an object from accidental damage, but allows other objects to interact with that data by calling the object's member functions and structures. [0101]
Subclassing and inheritance make it possible to extend and modify objects through deriving new kinds of objects from the standard classes available in the system. Thus, new capabilities are created without having to start from scratch. [0102]
Polymorphism and multiple inheritance make it possible for different programmers to mix and match characteristics of many different classes and create specialized objects that can still work with related objects in predictable ways. [0103]
Class hierarchies and containment hierarchies provide a flexible mechanism for modeling real-world objects and the relationships among them. [0104]
Libraries of reusable classes are useful in many situations, but they also have some limitations. For example: [0105]
Complexity. In a complex system, the class hierarchies for related classes can become extremely confusing, with many dozens or even hundreds of classes. [0106]
Flow of control. A program written with the aid of class libraries is still responsible for the flow of control (i.e., it must control the interactions among all the objects created from a particular library). The programmer has to decide which functions to call at what times for which kinds of objects. [0107]
Duplication of effort. Although class libraries allow programmers to use and reuse many small pieces of code, each programmer puts those pieces together in a different way. Two different programmers can use the same set of class libraries to write two programs that do exactly the same thing but whose internal structure (i.e., design) may be quite different, depending on hundreds of small decisions each programmer makes along the way. Inevitably, similar pieces of code end up doing similar things in slightly different ways and do not work as well together as they should. [0108]
Class libraries are very flexible. As programs grow more complex, more programmers are forced to reinvent basic solutions to basic problems over and, over again. A relatively new extension of the class library concept is to have a framework of class libraries. This framework is more complex and consists of significant collections of collaborating classes that capture both the small scale patterns and major mechanisms that implement the common requirements and design in a specific application domain. They were first developed to free application programmers from the chores involved in displaying menus, windows, dialog boxes, and other standard user interface elements for personal computers. [0109]
Frameworks also represent a change in the way programmers think about the interaction between the code they write and code written by others. In the early days of procedural programming, the programmer called libraries provided by the operating system to perform certain tasks, but basically the program executed down the page from start to finish, and the programmer was solely responsible for the flow of control. This was appropriate for printing out paychecks, calculating a mathematical table, or solving other problems with a program that executed in just one way. [0110]
The development of graphical user interfaces began to turn this procedural programming arrangement inside out. These interfaces allow the user, rather than program logic, to drive the program and decide when certain actions should be performed. Today, most personal computer software accomplishes this by means of an event loop which monitors the mouse, keyboard, and other sources of external events and calls the appropriate parts of the programmer's code according to actions that the user performs. The programmer no longer determines the order in which events occur. Instead, a program is divided into separate pieces that are called at unpredictable times and in an unpredictable order. By relinquishing control in this way to users, the developer creates a program that is much easier to use. Nevertheless, individual pieces of the program written by the developer still call libraries provided by the operating system to accomplish certain tasks, and the programmer must still determine the flow of control within each piece after it's called by the event loop. Application code still “sits on top of” the system. [0111]
Even event loop programs require programmers to write a lot of code that should not need to be written separately for every application. The concept of an application framework carries the event loop concept further. Instead of dealing with all the nuts and bolts of constructing basic menus, windows, and dialog boxes and then making these things all work together, programmers using application frameworks start with working application code and basic user interface elements in place. Subsequently, they build from there by replacing some of the generic capabilities of the framework with the specific capabilities of the intended application. [0112]
Application frameworks reduce the total amount of code that a programmer has to write from scratch. However, because the framework is really a generic application that displays windows, supports copy and paste, and so on, the programmer can also relinquish control to a greater degree than event loop programs permit. The framework code takes care of almost all event handling and flow of control, and the programmer's code is called only when the framework needs it (e.g., to create or manipulate a proprietary data structure). [0113]
A programmer writing a framework program not only relinquishes control to the user (as is also true for event loop programs), but also relinquishes the detailed flow of control within the program to the framework. This approach allows the creation of more complex systems that work together in interesting ways, as opposed to isolated programs, having custom code, being created over and over again for similar problems. [0114]
Thus, as is explained above, a framework basically is a collection of cooperating classes that make up a reusable design solution for a given problem domain. It typically includes objects that provide default behavior (e.g., for menus and windows), and programmers use it by inheriting some of that default behavior and overriding other behavior so that the framework calls application code at the appropriate times. [0115]
There are three main differences between frameworks and class libraries: [0116]
Behavior versus protocol. Class libraries are essentially collections of behaviors that you can call when you want those individual behaviors in your program. A framework, on the other hand, provides not only behavior but also the protocol or set of rules that govern the ways in which behaviors can be combined, including rules for what a programmer is supposed to provide versus what the framework provides. [0117]
Call versus override. With a class library, the code the programmer instantiates objects and calls their member functions. It's possible to instantiate and call objects in the same way with a framework (i.e., to treat the framework as a class library), but to take full advantage of a framework's reusable design, a programmer typically writes code that overrides and is called by the framework. The framework manages the flow of control among its objects. Writing a program involves dividing responsibilities among the various pieces of software that are called by the framework rather than specifying how the different pieces should work together. [0118]
Implementation versus design. With class libraries, programmers reuse only implementations, whereas with frameworks, they reuse design. A framework embodies the way a family of related programs or pieces of software work. It represents a generic design solution that can be adapted to a variety of specific problems in a given domain. For example, a single framework can embody the way a user interface works, even though two different user interfaces created with the same framework might solve quite different interface problems. [0119]
Thus, through the development of frameworks for solutions to various problems and programming tasks, significant reductions in the design and development effort for software can be achieved. [0120]
Thus, it is seen that a system, method and article of manufacture are provided for determining a location of wireless device. One skilled in the art will appreciate that the present invention can be practiced by other than the above-described embodiments, which are presented in this description for purposes of illustration and not of limitation. The description and examples set forth in this specification and associated drawings only set forth preferred embodiment(s) of the present invention. The specification and drawings are not intended to limit the exclusionary scope of this patent document. Many designs other than the above-described embodiments will fall within the literal and/or legal scope of the following claims, and the present invention is limited only by the claims that follow. It is noted that various equivalents for the particular embodiments discussed in this description may practice the invention as well. [0121]

Claims

What is claimed is:

1. A method for determining a location of an ultra-wideband wireless device, comprising:

transmitting a first request to at least two ultra-wideband devices having substantially fixed locations for determining a location of a first ultra-wideband wireless device; and

transmitting a second request to a least one additional ultra-wideband device if the location of the first ultra-wideband wireless device cannot be determined using data received in response to the first request.

2. The method of claim 1, wherein the additional ultra-wideband device has either a substantially fixed location or is a mobile ultra-wideband device.

3. The method of claim 1, wherein the additional ultra-wideband device determines its location from data received from other ultra-wideband devices not queried by the first ultra-wideband device.

4. The method of claim 1, wherein the additional ultra-wideband device determines its location from data received from a combination of ultra-wideband devices queried by the first ultra-wideband device and other ultra-wideband devices not queried by the first ultra-wideband device.

5. The method of claim 1, wherein the first ultra-wideband device determines its location from data received from the additional ultra-wideband device and from at least one of the ultra-wideband devices having substantially fixed locations.

6. The method of claim 1, wherein the first ultra-wideband device determines its location from data received only from the additional ultra-wideband devices.

7. The method of claim 1, wherein the second request is re-transmitted by the first ultra-wideband device.

8. The method of claim 7, wherein the second request is retransmitted at a higher power level if an insufficient number of responses are received in response to the retransmission.

9. The method of claim 1, wherein the first ultra-wideband device obtains information relating to the distance between the first ultra-wideband wireless device and the additional ultra-wideband device, and a scaling factor.

10. The method of claim 1, wherein the first ultra-wideband device obtains information to update an internal clock of the first wireless device.

11. The method of claim 1, wherein the first ultra-wideband device determines a location and an elevation using data received in response to the first and second requests.

12. The method of claim 11, wherein the elevation is an elevation relative to an elevation of an ultra-wideband device responding to the first and second request.

13. The method of claim 11, wherein the elevation is an elevation relative to a sea level.

14. The method of claim 11, wherein the determination of the location and the elevation employs data obtained from any one of: a terrain map, a topographical map, and a historical map.

15. A system for determining a location of an ultra-wideband wireless device, comprising:

logic for transmitting a first request to at least two ultra-wideband devices having substantially fixed locations for determining a location of a first ultra-wideband wireless device; and

logic for transmitting a second request to a least one additional ultra-wideband device if the location of the first ultra-wideband wireless device cannot be determined using data received in response to the first request.

16. The system of claim 15, wherein the additional ultra-wideband device determines its location from data received from other ultra-wideband devices not queried by the first ultra-wideband device.

17. The system of claim 15, wherein the second request is re-transmitted by the first ultra-wideband device.

18. The system of claim 15, wherein the second request is retransmitted at a higher power level if an insufficient number of responses are received in response to the retransmission.

19. The system of claim 15, wherein the first ultra-wideband device obtains information to update an internal clock of the first wireless device.

20. The system of claim 15, wherein the first ultra-wideband device determines a location and an elevation using data received in response to the first and second requests.

21. The system of claim 20, wherein the elevation is an elevation relative to an elevation of an ultra-wideband device responding to the first and second request.

22. The system of claim 20, wherein the elevation is an elevation relative to a sea level.

23. The system of claim 20, wherein the determination of the location and the elevation employs data obtained from any one of: a terrain map, a topographical map, and a historical map.

24. A method for determining a location of an ultra-wideband wireless device, comprising:

transmitting a first request to at least three mobile ultra-wideband devices for determining a location of a first ultra-wideband wireless device; and

25. The method of claim 24, wherein the additional ultra-wideband device has either a substantially fixed location or is a mobile ultra-wideband device.

26. The method of claim 24, wherein the additional ultra-wideband device determines its location from data received from other ultra-wideband devices not queried by the first ultra-wideband device.

27. The method of claim 24, wherein the additional ultra-wideband device determines its location from data received from a combination of ultra-wideband devices queried by the first ultra-wideband device and other ultra-wideband devices not queried by the first ultra-wideband device.

28. The method of claim 24, wherein the first ultra-wideband device determines its location from data received from the additional ultra-wideband device and from at least one of the ultra-wideband devices having substantially fixed locations.

29. The method of claim 24, wherein the first ultra-wideband device determines its location from data received only from the additional ultra-wideband devices.

30. The method of claim 24, wherein the second request is re-transmitted by the first ultra-wideband device.

31. The method of claim 30, wherein the second request is retransmitted at a higher power level if an insufficient number of responses are received in response to the retransmission.

32. The method of claim 24, wherein the first ultra-wideband device obtains information relating to the distance between the first ultra-wideband wireless device and the additional ultra-wideband device, and a scaling factor.

33. The method of claim 24, wherein the first ultra-wideband device obtains information to update an internal clock of the first wireless device.

34. The method of claim 24, wherein the first ultra-wideband device determines a location and an elevation using data received in response to the first and second requests.

35. The method of claim 34, wherein the elevation is an elevation relative to an elevation of an ultra-wideband device responding to the first and second request.

36. The method of claim 34, wherein the elevation is an elevation relative to a sea level.

37. The method of claim 34, wherein the determination of the location and the elevation employs data obtained from any one of: a terrain map, a topographical map, and a historical map.

38. A system for determining a location of an ultra-wideband wireless device, comprising:

logic for transmitting a first request to at least three mobile ultra-wideband devices for determining a location of a first ultra-wideband wireless device; and

39. The system of claim 38, wherein the additional ultra-wideband device determines its location from data received from other ultra-wideband devices not queried by the first ultra-wideband device.

40. The system of claim 38, wherein the second request is re-transmitted by the first ultra-wideband device.

41. The system of claim 38, wherein the second request is retransmitted at a higher power level if an insufficient number of responses are received in response to the retransmission.

42. The system of claim 38, wherein the first ultra-wideband device obtains information to update an internal clock of the first wireless device.

43. The system of claim 38, wherein the first ultra-wideband device determines a location and an elevation using data received in response to the first and second requests.

44. The system of claim 43, wherein the elevation is an elevation relative to an elevation of an ultra-wideband device responding to the first and second request.

45. The system of claim 43, wherein the elevation is an elevation relative to a sea level.

46. The system of claim 43, wherein the determination of the location and the elevation employs data obtained from any one of: a terrain map, a topographical map, and a historical map.