MOBILE DEVICE FREQUENCY OFFSET DETERMINATION AND TDoA LOCALIZATION

Abstract

A method of estimating a clock frequency offset in a mobile device relative to a clock frequency of a controller within a UWB network comprises (a) determining, for each of a plurality of anchors, an anchor clock frequency offset relative to the controller clock frequency, (b) broadcasting an anchor data packet from each anchor, the anchor data packet including the respective anchor clock frequency offset, (c) receiving at least one anchor data packet at the mobile device, (d) estimating a mobile device clock frequency offset relative to the anchor clock frequency of the anchor from which the at least one anchor data packet was received, and (e) estimating the clock frequency offset in the mobile device based on the estimated mobile device clock frequency offset and the anchor clock frequency offset included in the at least one received anchor data packet. Furthermore, a TDoA-based localization method and a TDoA-based localization system are described.

Claims

1-15. (canceled)

16. A method of estimating a clock frequency offset in a mobile device relative to a clock frequency of a controller within a UWB network, the UWB network comprising a plurality of anchors in communication with the controller and the mobile device, each anchor in the plurality of anchors having a respective anchor clock, the method comprising: determining, for each of the plurality of anchors, an anchor clock frequency offset relative to the controller clock frequency; broadcasting an anchor data packet from each anchor, the anchor data packet including the respective anchor clock frequency offset; receiving at least one anchor data packet at the mobile device; estimating a mobile device clock frequency offset relative to the anchor clock frequency of the anchor from which the at least one anchor data packet was received; and estimating the clock frequency offset in the mobile device based on the estimated mobile device clock frequency offset and the anchor clock frequency offset included in the at least one received anchor data packet.

17. The method according to claim 16, wherein estimating the mobile device clock frequency offset relative to the anchor clock frequency utilizes carrier frequency offset estimation based on carrier integration.

18. The method according to claim 16, wherein estimating the clock frequency offset in the mobile device comprises calculating a sum of the estimated mobile device clock frequency offset and the anchor clock frequency offset included in the at least one received anchor data packet.

19. The method according to claim 16, wherein determining the anchor clock frequency offset relative to the controller clock frequency comprises: receiving a first controller data packet at the anchor, the first controller data packet comprising a first controller timestamp indicating the time of transmission at the controller, and recording the time of receipt of the first controller data packet at the anchor as a first anchor timestamp; receiving a second controller data packet at the anchor, the second controller data packet comprising a second controller timestamp indicating the time of transmission at the controller, and recording the time of receipt of the second controller data packet at the anchor as a second anchor timestamp; and determining the anchor clock frequency offset by calculating a difference between the second controller timestamp and the first controller timestamp and dividing the calculated difference with a difference between the second anchor timestamp and the first anchor timestamp.

20. The method according to claim 16, further comprising: receiving a plurality of anchor data packets at the mobile device; estimating, for each of the received anchor data packets, a mobile device clock frequency offset relative to the anchor clock frequency of the anchor from which the anchor data packet was received; and estimating the clock frequency offset in the mobile device relative to the clock frequency of the controller based on the estimated mobile device clock frequency offsets relative to the anchor clock frequencies and the anchor clock frequency offsets relative to the controller clock frequency included in the received anchor data packets.

21. The method according to claim 20, wherein estimating the clock frequency offset in the mobile device comprises calculating, for each of the anchors from which the plurality of anchor data packets was received, a sum of the estimated mobile device clock frequency offset and the anchor clock frequency offset included in the anchor data packet received from the corresponding anchor.

22. The method according to claim 21, wherein estimating the clock frequency offset in the mobile device further comprises statistical processing of the calculated sums.

23. The method according to claim 22, wherein the statistical processing comprises calculating an average value of the calculated sums.

24. A TDoA-based method of localizing a mobile device within a UWB network, the UWB network comprising a controller and a plurality of anchors in communication with the controller and the mobile device, each anchor in the plurality of anchors having a respective anchor clock and the controller having a controller clock, the method comprising: determining, for each of the plurality of anchors, an anchor clock frequency offset relative to the controller clock frequency; broadcasting an anchor data packet from each anchor, the anchor data packet including the respective anchor clock frequency offset and an anchor timestamp; receiving a plurality of anchor data packets at the mobile device, each anchor data packet originating from one of the plurality of anchors; recording, for each of the received anchor data packets, a corresponding timestamp of arrival; estimating, for each of the received anchor data packets, a mobile device clock frequency offset relative to the anchor clock frequency of the anchor from which the anchor data packet was received; estimating a clock frequency offset in the mobile device relative to the clock frequency of the controller based on the estimated mobile device clock frequency offsets relative to the anchor clock frequencies and the anchor clock frequency offsets included in the received anchor data packets; and determining a location of the mobile device based on the anchor timestamps in the received anchor data packets, the recorded timestamps of arrival for each of the received anchor data packets, and the estimated clock frequency offset in the mobile device.

25. The method according to claim 24, wherein estimating the mobile device clock frequency offset relative to the anchor clock frequency utilizes carrier frequency offset estimation based on carrier integration.

26. The method according to claim 24, wherein determining, for each of the plurality of anchors, the anchor clock frequency offset relative to the controller clock frequency comprises: receiving a first controller data packet at the anchor, the first controller data packet comprising a first controller timestamp indicating the time of transmission at the controller, and recording the time of receipt of the first controller data packet at the anchor as a first anchor timestamp; receiving a second controller data packet at the anchor, the second controller data packet comprising a second controller timestamp indicating the time of transmission at the controller, and recording the time of receipt of the second controller data packet at the anchor as a second anchor timestamp; and determining the anchor clock frequency offset by calculating a difference between the second controller timestamp and the first controller timestamp and dividing the calculated difference with a difference between the second anchor timestamp and the first anchor timestamp.

27. The method according to claim 24, wherein estimating the clock frequency offset in the mobile device comprises calculating, for each of the anchors from which the plurality of anchor data packets was received, a sum of the estimated mobile device clock frequency offset and the anchor clock frequency offset included in the anchor data packet received from the corresponding anchor.

28. The method according to claim 27, wherein estimating the clock frequency offset in the mobile device further comprises statistical processing of the calculated sums.

29. The method according to claim 28, wherein the statistical processing comprises calculating an average value of the calculated sums.

30. A TDoA-based localization system, the system comprising: at least one UWB enabled mobile device having a mobile device clock; and a UWB network, the UWB network comprising a controller and a plurality of anchors, each anchor in the plurality of anchors having a respective anchor clock and the controller having a controller clock, wherein each of the anchors is configured to: determine an anchor clock frequency offset relative to the controller clock frequency; and broadcast an anchor data packet, the anchor data packet including the respective anchor clock frequency offset and an anchor timestamp; wherein the at least one mobile device is configured to: receive a plurality of anchor data packets, each anchor data packet originating from one of the plurality of anchors; record, for each of the received anchor data packets, a corresponding timestamp of arrival; estimate, for each of the received anchor data packets, a mobile device clock frequency offset relative to the anchor clock frequency of the anchor from which the anchor data packet was received; estimate a clock frequency offset in the mobile device relative to the clock frequency of the controller based on the estimated mobile device clock frequency offsets relative to the anchor clock frequencies and the anchor clock frequency offsets included in the received anchor data packets; and determine a location of the mobile device based on the anchor timestamps in the received anchor data packets, the recorded timestamps of arrival for each of the received anchor data packets, and the estimated clock frequency offset in the mobile device.

31. The system according to claim 30, wherein the at least one mobile device is configured to estimate the mobile device clock frequency offset relative to the anchor clock frequency by utilizing carrier frequency offset estimation based on carrier integration.

32. The system according to claim 30, wherein each of the anchors is configured to determine the anchor clock frequency offset relative to the controller clock frequency by: receiving a first controller data packet at the anchor, the first controller data packet comprising a first controller timestamp indicating the time of transmission at the controller, and recording the time of receipt of the first controller data packet at the anchor as a first anchor timestamp; receiving a second controller data packet at the anchor, the second controller data packet comprising a second controller timestamp indicating the time of transmission at the controller, and recording the time of receipt of the second controller data packet at the anchor as a second anchor timestamp; and determining the anchor clock frequency offset by calculating a difference between the second controller timestamp and the first controller timestamp and dividing the calculated difference with a difference between the second anchor timestamp and the first anchor timestamp.

33. The system according to claim 30, wherein the at least one mobile device is configured to estimate the clock frequency offset in the mobile device by calculating, for each of the anchors from which the plurality of anchor data packets was received, a sum of the estimated mobile device clock frequency offset and the anchor clock frequency offset included in the anchor data packet received from the corresponding anchor.

34. The system according to claim 33, wherein the at least one mobile device is further configured to estimate the clock frequency offset in the mobile device by performing statistical processing of the calculated sums.

35. The method according to claim 34, wherein the statistical processing comprises calculating an average value of the calculated sums.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0048] FIG. 1 shows a TDoA localization system according to an embodiment.

[0049] FIG. 2 shows a typical message sequence in a downlink TDoA localization system.

[0050] FIG. 3 shows a block diagram of a method of determining clock frequency offset in a mobile device in accordance with an embodiment.

[0051] FIG. 4 shows a block diagram of a method of localizing a mobile device within a UWB network in accordance with an embodiment.

DETAILED DESCRIPTION

[0052] The illustration in the drawing is schematic. It is noted that in different figures, similar or identical elements are provided with the same reference signs or with reference signs, which differ only within the first digit.

[0053] FIG. 1 shows a TDoA localization system 100 according to an embodiment. The system 100 comprises one or more mobile devices M and a UWB network 105. The UWB network comprises a plurality of anchors A1, A2, A3, A4. One of the anchors A1, A2, A3, A4 acts as a controller, i.e., it defines a reference clock (controller clock) for the system 100 and coordinates broadcasting of data packets from the other anchors in the UWB network 105, as will be described further below. In other embodiments, the controller may differ from the anchors in various ways. FIG. 1 shows four anchors A1, A2, A3, A4. However, it should be understood, that the UWB network 105 may comprise any number of anchors, including tens, hundreds or even thousands of anchors. Each anchor A1, A2, A3, A4 is fixed at a known location within the localization system 100 and may in some embodiments also be interconnected by a wired network in addition to being able to communicate wirelessly with each other via UWB communication. In the following description, the anchor A1 will generally be referred to as the controller. However, in other embodiments, any of the other anchors A2, A3, A4 may be configured as the controller. Similarly, the system 100 may comprise any number of mobile devices M, including tens, hundreds or even thousands of mobile devices M. As generally known in the art, the anchors A1, A2, A3, A4 broadcast data packets which allow the mobile device(s) M to determine the time differences between the arrivals of the respective data packets at the mobile device M. These time differences of arrival are caused by the different distances and thereby different times of flight TOF1-TOF4 to the anchors A1, A2, A3, A4. Based on the determined time differences and the known location of each anchor A1, A2, A3, A4, the mobile device M can then determine its position within the system 100 using so-called hyperbolic localization.

[0054] FIG. 2 shows a typical message sequence 201 in a downlink TDoA localization system, such as the system 100 shown in FIG. 1. It is noted that other message sequences are possible, as known in the art. The controller anchor A1 transmits a first controller data packet S at time t=T1. The first controller data packet S (synch) is then received somewhat later at anchor A2, then at anchor A3 and finally at the mobile device M. Then, at t=T2, the controller anchor A1 transmits a second controller data packet B1 (blink 1) which, like the first controller data packet S, is received by the anchor A2, then by the anchor A3, and finally by the mobile device M. Somewhat later, at t=T3, the anchor A2 transmits an anchor data packet B2 blink 2), which later on arrives at the anchor A3, then at the mobile device M. Finally, the anchor A3 transmits an anchor data packet B3 (blink 3) which is later received by the mobile device M. It is noted that the order in which the data packets are received has no impact on the procedure. The mobile device M measures the received (RX) timestamps of all data packets S, B1, B2, B3 and obtain the transmission (TX) timestamps in the common time base (CTB) of the controller A1. To this end, all anchor data packets include the TX timestamp in the transmitted packets. Alternatively, they can also include the time elapsed between the last controller packet and their transmissions (e.g., the time between the Blink from the controller and the Blink of each anchor or the time between the POLL of the controller and the RESP of each anchor).

[0055] To perform TDoA localization, the set of anchors A1-A4 must be time synchronized, e.g., in order to translate all timestamps to a common time domain, i.e., the common time base (CTB) of the controller A1. The anchors A1-A4 may be synchronized using a wired infrastructure (not shown) where the controller clock is directly distributed to all controlled anchors A2-A4 or using in-band wireless clock synchronization. In the latter case, the anchors must measure their clock offset and clock frequency offset with regard to the controller anchor A1. To measure the clock offset θ.sub.i,ref between controlled anchor i (the controlled anchor may also be denoted controlee) and the controller ref, the controlled anchors A2-A4 must simply compare the TX and RX timestamp of a controller packet and account for the known time of flight (ToF) τ.sub.i,ref between them as follows:

θ.sub.i,ref=r.sub.i.sup.SYNCH−t.sub.ref.sup.SYNCH−τ.sub.i,ref

where r.sub.i.sup.SYNCH and t.sub.ref.sup.SYNCH denote the RX and TX timestamp of the Synch packet at the controlled anchor and at the controller, respectively. Note that any other controller message can be used for this purpose.

[0056] In turn, to determine the frequency offset of anchors A2-A4 with regard to the controller A1, the anchors A2-A4 can compare the time elapsed as measured at the receiver and at the transmitter between two consecutive packets from the controller, e.g., the Synch-Blink pair S, B1 or two other data packets from consecutive TDoA exchanges. In the case of two consecutive Synch packets, we obtain:

[00001]$K_{i,\mathrm{ref}}=\frac{t_{\mathrm{ref}}^{\mathrm{SYNCH},N}-t_{\mathrm{ref}}^{\mathrm{SYNCH},N-1}}{r_i^{\mathrm{SYNCH},N}-r_i^{\mathrm{SYNCH},N-1}}$

[0057] The estimated clock offset θ.sub.i,ref and frequency offset K.sub.i,ref can be then used to translate TX timestamps to the common time base (CTB) of the controller or to compensate for the frequency offset of the anchors A2-A4 during their response delays. This information must be shared with mobile devices M so that they can perform TDoA localization.

[0058] To improve TDoA localization, the mobiles devices M must also estimate their frequency offset with regard to the controller anchor A1. The conventional approach to do this is based on two consecutive packets from the controller as shown in FIG. 1. In these cases, the mobile estimates its frequency offset K.sub.M,ref as follows:

[00002]$K_{M,\mathrm{ref}}=\frac{t_{\mathrm{ref}}^{\mathrm{Blink}}-t_{\mathrm{ref}}^{\mathrm{SYNCH}}}{r_M^{\mathrm{Blink}}-r_M^{\mathrm{SYNCH}}}$

[0059] Afterwards, it can compensate for its frequency offset in each TDoA measurement Δt.sub.i,ref as follows:

{circumflex over (Δ)}t.sub.i,ref=K.sub.M,ref(r.sub.M.sup.Blink,i−r.sub.M.sup.Blink,ref)−(t.sub.i.sup.Blink,i−t.sub.ref.sup.Blink,ref)

[0060] Here, r.sub.m,Blink,i, r.sub.M.sup.Blink,ref denote the RX timestamps of the Blink data packet Bi from anchor i and the controller ref, while t.sub.i.sup.Blink,i, t.sub.ref.sup.Blink,ref denote the TX timestamps in CTB of the same packets.

[0061] The main problem in existing approaches is that the mobile devices M need to receive the two transmitted packets S and B1 from the controller A1 to estimate their frequency offset, see FIG. 1. This implies longer packet exchanges, which lead to higher energy consumption, shorter battery lifetime, and lower scalability/update rates. More importantly, in the case that a mobile device M misses or does not receive one of the two packets, it cannot estimate its frequency offset and therefore, it cannot compensate for it in the TDoA equation above, thereby decreasing the attainable accuracy and precision of the proposed TDoA scheme.

[0062] These and other issues are addressed by the methods of determining clock frequency offset relative to the controller clock as presented herein.

[0063] FIG. 3 shows a block diagram 302 of a method of determining clock frequency offset in a mobile device M relative to the clock frequency of the controller A1 within UWB network 105 in accordance with an embodiment. As described above in conjunction with FIG. 1, the UWB network comprises a plurality of anchors A2-A4 in communication with the controller A1 and the mobile device M. Each anchor A2-A4 has a respective anchor clock. The method comprises a step 310 of determining, for each of the plurality of anchors A2-A4, an anchor clock frequency offset relative to the controller A1 clock frequency. The method 302 further comprises a step 320 of broadcasting an anchor data packet from each anchor A2-A4, the anchor data packet including the respective anchor clock frequency offset. The method further comprises a step 330 of receiving at least one anchor data packet at the mobile device M. The method further comprises a step 340 of estimating a mobile device clock frequency offset relative to the anchor clock frequency of the anchor A2-A4 from which the at least one anchor data packet was received. This step 340 may in particular utilize carrier frequency offset estimation based on carrier integration. The method further comprises a step 350 of estimating the clock frequency offset in the mobile device M based on the estimated mobile device clock frequency offset and the anchor clock frequency offset included in the at least one received anchor data packet. The step 350 may in particular involve calculating a sum of the estimated mobile device clock frequency offset and the anchor clock frequency offset included in the at least one received anchor data packet:

∈.sub.M,ref=∈.sub.M,i+∈.sub.i,ref

[0064] Here, ∈.sub.M,i denotes the estimated mobile device clock frequency offset relative to anchor i, while ∈.sub.i,ref denotes the anchor clock frequency offset included in the anchor data packet received from anchor i.

[0065] In many practical implementations, the mobile device M may receive anchor packets from a plurality of anchors A2-A4. It should be noted that any number of anchors may be used depending on the specific implementation and other circumstances. In these cases, the mobile device M may estimate its clock frequency offset in the manner described above based on each received anchor data packet and then perform statistical processing, such as averaging, to obtain one single estimate for the clock frequency offset relative to the controller clock frequency. For example, in a case where anchor data packets are received from a total of N anchors, the resulting estimate may be calculated by averaging the individual sums for all N anchors:

[00003]${ϵ}_{M,\mathrm{ref}}=\frac{{.Math.}_{i=1}^N\left({ϵ}_{M,i}+{ϵ}_{i,\mathrm{ref}}\right)}{N}$

[0066] To illustrate this, a simple example is provided: Assume that a mobile node has a clock that runs at a frequency offset 5 ppm faster than the clock of the controller, while anchors A2 and A3 have +2 ppm and −3 ppm, respectively. In such case, the mobile node may estimate (based on CFO carrier integration) during packet receptions that the clocks of anchors A2 and A3 run at respectively 3 ppm and 8 ppm slower than its own clock. In this case, the above general formula yields:

[00004]${ϵ}_{M,\mathrm{ref}}=\frac{{.Math.}_{i=1}^N\left({ϵ}_{M,i}+{ϵ}_{i,\mathrm{ref}}\right)}{N}=\frac{\left(3\mathrm{ppm}+2\mathrm{ppm}\right)+\left(8\mathrm{ppm}+\left(-3\mathrm{ppm}\right)\right)}{2}=\frac{10}{2}=5\mathrm{ppm}$

[0067] It should be noted that each CFO estimate may suffer from an error in the order of hundreds of ppb. However, by aggregating multiple estimates from different anchors, the final estimate can be significantly improved.

[0068] FIG. 4 shows a block diagram 403 of a method of localizing a mobile device M within a UWB 105 network in accordance with an embodiment. More specifically, FIG. 4 shows a TDoA-based method of localizing the mobile device M within UWB network 105, the UWB network 105 comprising a controller A1 and a plurality of anchors A2-A4 in communication with the controller A1 and the mobile device M, each anchor A2-A4 having a respective anchor clock and the controller A1 having a controller clock. The method 403 comprises a step 411 of determining, for each of the plurality of anchors A2-A4, an anchor clock frequency offset relative to the controller clock frequency. The method 403 further comprises a step 421 of broadcasting an anchor data packet from each anchor A2-A4, the anchor data packet including the respective anchor clock frequency offset and an anchor timestamp. The method 403 further comprises a step 431 of receiving a plurality of anchor data packets at the mobile device M, each anchor data packet originating from one of the plurality of anchors A2-A4. The method 403 further comprises a step 441 of recording, for each of the received anchor data packets, a corresponding timestamp of arrival. The method 403 further comprises a step 451 of estimating, for each of the received anchor data packets, a mobile device clock frequency offset relative to the anchor clock frequency of the anchor from which the anchor data packet was received. This step 451 may in particular utilize carrier frequency offset estimation based on carrier integration. The method 403 further comprises a step 461 of estimating a clock frequency offset in the mobile device M relative to the clock frequency of the controller A1 based on the estimated mobile device clock frequency offsets relative to the anchor clock frequencies and the anchor clock frequency offsets included in the received anchor data packets. The method 403 further comprises a step 471 of determining a location of the mobile device M based on the anchor timestamps in the received anchor data packets, the recorded timestamps of arrival for each of the received anchor data packets, and the estimated clock frequency offset in the mobile device M.

[0069] It is noted that, unless otherwise indicated, the use of terms such as “upper”, “lower”, “left”, and “right” refers solely to the orientation of the corresponding drawing.

[0070] It is noted that the term “comprising” does not exclude other elements or steps and that the use of the articles “a” or “an” does not exclude a plurality. Also, elements described in association with different embodiments may be combined. It should also be noted that reference signs in the claims should not be construed as limiting the scope of the claims.