Interleaving ultra-wideband positioning services and other ultra-wideband services

Abstract

Systems, devices, and methods of interleaving DL-TDoA with other UWB transmissions are disclosed. In an exemplary aspect, a method performed by a UWB device is disclosed. The method may include participating in establishing a HUS session associated with a HUS secondary session. The method may further include listening for DL-TDoA messages during a ranging block in a DL-TDoA session, wherein the ranging block comprises a first time block and a second time block. The method may further include detecting at least one DL-TDoA message during the first time block in the ranging block, wherein no DL-TDoA messages are detected in the second time block of the ranging block. The method may further include, based on the detecting, allocating to the HUS secondary session a second time block in a second ranging block of the DL-TDoA session, wherein the second ranging block has a same structure as the ranging block.

Description

Interleaving Ultra-Wideband Positioning Services and Other Ultra-Wideband ServicesChristophe Le Thierry d’Ennequin and Eric PerraudRELATED APPLICATIONS

[0001] The present application claims the benefit of U.S. Provisional Application No. 63 / 602,913, filed November 27, 2023, which is incorporated herein by reference in its entiretyTECHNICAL FIELD

[0002] The present disclosure relates generally to ultra-wideband wireless technology, and, more specifically to systems, methods, and devices for efficiently providing for the coexistence of ultra- wideband positioning services with other ultra- wideband services.BACKGROUND

[0003] Ultra-wideband (UWB) generally refers to a wireless communication technology that uses a wide bandwidth, such as about 500 megahertz (MHz) or larger, or generally has a 10 dB bandwidth greater than 20% of the center frequency. U WB-based positioning systems, such as downlink time difference of arrival (DL-TDoA) systems, may be deployed in areas where other UWB services, such as Hybrid UWB Scheduling (HUS), are being used. HUS may refer to a feature that allows for scheduling UWB sessions configured in time- scheduled mode or contention-based mode with a fixed time relation to each other, such that they occur in the HUS ranging round in a deterministic time sequence. HUS is currently being considered, for example, in the Fine-Ranging (FiRa) Consortium.

[0004] UWB messages sent within a hybrid session (or HUS session) may interfere with UWB messages sent by DL-TDoA Anchors (DT-Anchors). As the number and density of UWB services increase, interference may result in a degradation of DL-TDoA services, and, in turn, users may be unable to receive messages sent by DT-Anchors and therefore may be unable to determine their location. Thus, there is a need in complex UWB environments for solutions to allow DL-TDoA sessions and HUS sessions to efficiently coexist.SUMMARY

[0005] Embodiments of the present disclosure include systems, devices, and methods of interleaving DL-TDoA with other UWB transmissions.

[0006] In an exemplary aspect, a method performed by a UWB device is disclosed. In some embodiments, the method may include participating in establishing a Hybrid UWBScheduling (HUS) session associated with a HUS secondary session. The method may further include listening for DL-TDoA messages during a ranging block in a DL-TDoA session, wherein the ranging block comprises a first time block and a second time block. The method may further include detecting at least one DL-TDoA message during the first time block in the ranging block, wherein no DL-TDoA messages are detected in the second time block of the ranging block. The method may further include based on the detecting, allocating to the HUS secondary session a second time block in a second ranging block of the DL-TDoA session, wherein the second ranging block has a same structure as the ranging block including a corresponding first time block and the corresponding second time block.

[0007] In another exemplary aspect, a UWB device is disclosed. In some embodiments, the UWB device may include a UWB transceiver and a processor. The processor may be configured to establish a HUS session associated with a HUS secondary session; and listen for DL-TDoA messages, via the UWB transceiver, during a ranging block in a DL-TDoA session, wherein the ranging block comprises a first time block and a second time block. The processor may further be configured to detect at least one DL-TDoA message during the first time block in the ranging block, wherein no DL-TDoA messages are detected in the second time block of the ranging block; and based on the detecting, allocate to the HUS secondary session a second time block in a second ranging block of the DL-TDoA session, wherein the second ranging block has a same structure as the ranging block including a corresponding first time block and the corresponding second time block.

[0008] In another exemplary aspect, a non-transitory computer-readable medium (CRM) having program code recorded thereon. In some embodiments, the program code includes code for causing a UWB device to participate in establishing a HUS session associated with a HUS secondary session; and code for causing the UWB device to listen for DL-TDoA messages during a ranging block in a DL-TDoA session, wherein the ranging block comprises a first time block and a second time block. The program code may further include code for causing the UWB device to detect at least one DL-TDoA message during the first time block in the ranging block, wherein no DL-TDoA messages are detected in the second time block of the ranging block; and code for causing the UWB device to detect, based on the detecting, allocate to the HUS secondary session a second time block in a second ranging block of the DL-TDoA session, wherein the second ranging block has a same structure as the ranging block including a corresponding first time block and the corresponding second time block.

[0009] Additional aspects, features, and advantages of the present disclosure will become apparent from the following detailed description.BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description, serve to explain the principles of the disclosure.

[0011] FIG. 1 illustrates an example of operation of UWB DL-TDoA, according to some aspects of the present disclosure.

[0012] FIG. 2 illustrates an example of operation of a HUS, according to some aspects of the present disclosure.

[0013] FIG. 3 illustrates examples of a DL-TDoA network deployment, according to some aspects of the present disclosure.

[0014] FIG. 4 illustrates an example configuration of a DL-TDoA network from FIG. 3, according to some aspects of the present disclosure.

[0015] FIG. 5 illustrates of coexistence between DL-TDoA and HUS sessions, according to some aspects of the present disclosure.

[0016] FIG. 6 illustrates an example functional diagram of a UWB device, according to some aspects of the present disclosure.

[0017] FIG. 7 illustrates an example of slot allocation, according to some aspects of the present disclosure.

[0018] FIG. 8 illustrates an example of operation of a HUS, according to some aspects of the present disclosure.

[0019] FIG. 9 illustrates an example functional diagram of a HUS controlee device, according to some aspects of the present disclosure.

[0020] FIG. 10 illustrates an example of an UWB message payload, according to some aspects of the present disclosure.

[0021] FIG. 11 illustrates an example of operation of a HUS system, according to some aspects of the present disclosure.

[0022] FIG. 12 illustrates an example functional diagram of a HUS controlee device, according to some aspects of the present disclosure.

[0023] FIG. 13 illustrates an example of operation of a HUS system, according to some aspects of the present disclosure.

[0024] FIG. 14 illustrates an example method of UWB device operation, according to some aspects of the present disclosure.FIG. 15 is a block diagram of an example UWB device, according to some aspects of the present disclosure.DETAILED DESCRIPTION

[0025] For the purposes of promoting an understanding of the principles of the present disclosure, reference will now be made to the embodiments illustrated in the drawings, and specific language will be used to describe the same. It is nevertheless understood that no limitation to the scope of the disclosure is intended. Any alterations and further modifications to the described devices, systems, and methods, and any further application of the principles of the present disclosure are fully contemplated and included within the present disclosure as would normally occur to one skilled in the art to which the disclosure relates. In particular, it is fully contemplated that the features, components, and / or steps described with respect to one embodiment may be combined with the features, components, and / or steps described with respect to other embodiments of the present disclosure. For the sake of brevity, however, the numerous iterations of these combinations will not be described separately.

[0026] For complex UWB environments, it has been proposed for a DL-TDoA session and a HUS session to run at different times. For example, as currently proposed within the FiRa Consortium, a DL-TDoA session may be configured to operate from an initial time, TO, to a time T1 of a ranging block. Other UWB services may operate from time T1 until the end of the ranging block, thereby potentially enabling UWB messages sent by those services to avoid interfering with DL-TDoA messages. However, this solution may be inefficient in some instances. For example, suppose a DL-TDoA network is engaged in a DL-TDoA session during Ranging Round 1 to Ranging Round 6 of a ranging block. Assuming, for example, a ranging block contains 9 ranging rounds, only one third of the ranging block (i.e., Ranging Round 7 to Ranging Round 9) would be left for other UWB services.

[0027] Disclosed herein are systems, methods, and devices for interleaving DL-TDoA sessions with other UWB transmissions, such as HUS sessions, by controlling the allocation of ranging rounds between DL-TDoA and other ultra-wideband transmissions. Techniques presented herein allow UWB services using HUS sessions to operate simultaneously with a DL-TDoA network. Thus, the present disclosure allows for DL-TDoA and other UWB transmissions to coexist and run efficiently in the same environment.

[0028] The disclosed embodiments may be applied in a wide variety of UWB use cases and a variety of UWB system, method, and / or device configurations. A non-exhaustive list of such use cases is included. For example, in a train station, using DL-TDoA may potentiallyenable passengers to locate their position within the stations, while HUS(s) may be used at gates to allow users to go through. In a shopping mall, DL-TDoA may potentially enable customers to locate their position, while HUS(s) may be used for payment within shops.

[0029] DL-TDoA is an UWB feature which typically enables an UWB device to accurately determine its position. DL-TDoA typically utilizes DT-Anchors which may be deployed and may be configured within the area which is to be covered. Then, at least one device (for example, acting as a DL-TDoA Tag (DT-Tag)) is typically able to anonymously locate its position within this area by listening to at least one message, such as a DL-TDoA Message (DTM) (for example, a Poll DTM, a Response DTM, and / or a Final DTM) sent by DT-Anchors.

[0030] FIG. 1 illustrates an example of operation of UWB DL-TDoA 100, according to some aspects of the present disclosure. In some embodiments, an initiator DT- Anchor 102 may initially transmit a Poll DTM 112 to a responder DT-Anchor 1 106, and, in some embodiments, any number of DT-Anchors N 108. In response, the responder DT-Anchor 1 106 may transmit a response DTM 116 back to the initiator DT-Anchor 102. In some embodiments, any number of DT-Anchors N 106 may transmit a Response DTM 118 back to the initiator DT-Anchor 102. In some embodiments, the initiator DT-Anchor 102 may transmit a final DTM 114 to a responder a DT-Anchor 1 106, and, in some embodiments, any number of DT-Anchors N 108. When within the range of the DT-Anchors, as assumed in FIG. 1, the DT-Tag is able to receive the Poll DTM and Response DTM sent by the DT- Anchors. Then, in step 1 10, the DT-Tag 104 may estimate its position using the DT-Anchor 102, 106, 108 coordinates obtained out-of-band or in-band (i.e., located in the Anchor Location field in some or all of DTMs 112, 116, 118).

[0031] A Hybrid session (or HUS session) may share a ranging round with multiple secondary sessions. At the beginning of a given ranging round, a HUS Controller may allocate the slots of this ranging round to Secondary Session(s). A HUS controller may broadcast slot-allocation information to HUS Controlees in one or more messages, such as a Control Message (CM) Type 3 message. CM Type 3 message(s) may be sent by a HUS Controller and may be received by HUS Controlee(s). HUS Controlees may listen to this CM Type 3 message. In some examples, when a HUS Controlee is the Controller of a given Secondary Session, the HUS Controlee may use the slots allocated in the CM Type 3 message to communicate with Secondary Controlee(s) of a Secondary Session. In some embodiments, a HUS Controller or a device comprising a HUS Controller may be considered a primary controller. A HUS Controller may schedule HUS Ranging Phases by transmitting aCM Type 3. A HUS Controller may participate to HUS Ranging Phases as a Controller or as a Controlee. A Controller may be a FiRa Device that defines and controls the ranging features by sending Control Message. A Controlee may be a FiRa Device that utilizes the ranging features as configured via Control Message from the Controller. An HUS Controlee may synchronize to the HUS session by receiving a CM Type 3. A HUS Controlee may participate in HUS Ranging Phases as a Controller or a Controlee of HUS secondary session(s).

[0032] FIG. 2 illustrates an example of operation of a HUS 200, according to some aspects of the present disclosure. In some embodiments, in step 1 , a HUS Controller 202 may establish a HUS associated with one or more Secondary Sessions. For example, the HUS may be associated with two Secondary Sessions with session identification (ID) X and Y. In step 2, the HUS Controller 202 may allocate one or more slots to a Secondary Session. Then the HUS Controller 202 may transmit one or more messages 220, such as a CM Type 3, indicating to devices 204, 206, 208, 210 a slot range in which each Secondary Session may communicate. Then a HUS Controlee 204, 208 (which also may be a Secondary Controller of a session) may communicate with a Secondary Controlee 206, 210 (also referred to as a HUS Secondary Controlee) during the slots allocated for that session in the one or more messages.

[0033] For example, the HUS Controller may transmit a CM type 3 220 to a HUS Controlee 1 204 (which may also be the Secondary Controller of Session X) and a Secondary Controlee 1 206 allocating slots 20 to slot 59 to Session ID X. In this example, the CM type 3 220 may include a slot index start at 20 and / or a slot index end at 59. In some embodiments, a slot index may also be referred to as a slot value. In this example, in step 4. A, the HUS Controlee 1 204 (which may also be the Secondary Controller of Session X) may communicate with the Secondary Controlee 1 206 during slots 20 to 59. For another example, the HUS Controller may transmit a CM type 3 220 a HUS Controlee 2 208 (which may also be the Secondary Controller of Session Y) and a Secondary Controlee 2 210 allocating slots 60 to slot 79 to Session ID Y. In this example, the CM type 3 220 may include a slot index start at 60 and / or a slot index end at 79. In this example, in step 4.B, the HUS Controlee 2 208 (which may also be the Secondary Controller of Session Y) may communicate with the Secondary Controlee 2 210 during slots 60 to 79.

[0034] FIG. 3 illustrates an example DL-TDoA network deployment 300, according to some aspects of the present disclosure. The area shown in FIG. 3 may be associated with a mall or an office, for example. A DL-TDoA network deployment may include one or more DT-Anchors. For example, a DL-TDoA network deployment may include twelve DT- Anchors as shown in FIG. 3, where the anchors are labeled as “DT-Anchor n” forn=l,2,. . . 12. An UWB communication device, including, for example, a HUS Controller 332, a Secondary Controller 334, and / or a Secondary Controlee 336, may be configured to engage with the DT- Anchors. An UWB device may be configured support UWB services which may coexist with the DL-TDoA network. An UWB communication device may include both HUS and DT-Tag functionality, as explained further herein. To determine its location, the UWB device (acting as a DT-Tag) (not shown) may listen to the messages regularly sent by DT- Anchors. A DL-TDoA network may be composed of multiple DT-Anchors organized in clusters 320, 330. DT-Anchors may be distributed over a potentially wide deployment area. A cluster 320, 330 may be a set of DT-Anchors which exchange DTMs to provide positioning services to the DT-Tags in the specific area or region covered by the cluster 320, 330. The cluster 320, 330 may generally include one Initiator DT-Anchor and one or more Responder DT-Anchors. Each DT-Anchor may be configured in advance with: a set of ranging rounds during which it shall transmit and its role (e.g., Initiator DT-Anchor or Responder DT- Anchor) during a given ranging round. Depending on the embodiment, a HUS Controller 332; Secondary Controller 334; and a Secondary Controlee 336 may operate in association with a DL-TDoA network deployment.

[0035] For example, HUS Controller 2 332, Secondary Controller 334, and a Secondary Controlee 336 may operate in association with DL-TDoA network deployment 300, DL- TDoA network deployment 320, and / or DL-TDoA network deployment 330. Due to proximity, HUS Controller 2 332, Secondary Controller 334, and a Secondary Controlee 336 may operate in association with DL-TDoA network deployment 330 for potentially optimal results. In some embodiments, HUS Controller 2 332, Secondary Controller 334, and a Secondary Controlee 336 may all include a same device. In some embodiments, HUS Controller 2 332, Secondary Controller 334, and a Secondary Controlee 336 may each be a separate device. In some embodiments, HUS Controller 2 332, Secondary Controller 334, and a Secondary Controlee 336 may each be any combination of separate from or combined with the other respective devices depending on the embodiment.

[0036] FIG. 4 illustrates an example configuration of the DL-TDoA network 300 from FIG. 3, according to some aspects of the present disclosure. A first column 402 of the chart 400 represents the DT-Anchor. A second column 404 of chart 400 represents corresponding active ranging rounds for each DT-Anchor. In some embodiments, the chart 400 may inform if a DT-Anchor acts as an initiator, responder, or both an initiator and a responder. In some embodiments, the chart 400 may inform on the ranging round or ranging rounds in which a DT-Anchor is active. For example, in some embodiments, DT-Anchor 1 may act as aninitiator during ranging round 2, and DT- Anchors 2 and 3 may act as responders during ranging round 2.

[0037] FIG. 5 illustrates example of coexistence between DL-TDoA and HUS sessions, according to some aspects of the present disclosure. A ranging block (RB) in a DL-TDoA session (for example, ranging block 1 500) may include any number of ranging rounds (RR) 506, such as nine RRs as shown in FIG. 5.

[0038] One solution to make sure that indoor positioning works properly at all times is to run DL-TDoA and HUS sessions at different times, and FIG. 5 illustrates one such example. For example, a DL-TDoA session may be configured to operate from time TO (for example, the beginning of RR 1 506) to time T1 (for example, the end of RR 6) of every ranging block. Other UWB services, such as HUS(s), may operate from time T1 until the end of every ranging block, thereby increasing the likelihood that UWB messages sent by those services do not interfere with the DL-TDoA messages. However, this configuration is not always efficient. For example, in the FIG. 5, a DL-TDoA network may operate during RR 1 to RR 6 of each ranging block, thereby establishing a DL-TDoA ranging block. Assuming that each ranging block contains nine RRs, only one third of the ranging block (for example, RR 7 to RR 9) may be remaining for other UWB services, such as HUS(s).

[0039] This disclosure addresses the issue of coexistence between DL-TDoA and HUS services by allowing HUS communication at the same time as (or simultaneous with) ranging rounds used by the DL-TDoA network, as long as the HUS messages do not interfere with messages sent by nearby DT-Anchors. In some embodiments, a HUS Controller or other device may allocate slots within a HUS so that the slots are not used for transmission at times when there is a risk of interference with messages sent by a DT-Anchor. Thus, the operation of HUS may successfully avoid impacting a user experience of an indoor positioning service provided by a DL-TDoA network, for example.

[0040] In some embodiments, a device may detect the ranging rounds used by a DL- TDoA network in the vicinity of an UWB Device. Then the device may mark the slots associated with those occupied ranging rounds as “occupied.” In some embodiments, a HUS Controlee may indicate to a HUS Controller, in an UWB message or in a payload sent over a link layer connection, the lists of slots marked as “occupied” by the HUS Controlee. Then the HUS Controller may exclude the slots marked as “occupied” when allocating slots for a Secondary Session to which the HUS Controlee is participating.

[0041] FIG. 6 illustrates an example functional diagram of a UWB device 600, according to some aspects of the present disclosure. The UWB device 600 includes a UWB radio 602and functionality to implement a DT-Tag 604 and a HUS Controller 606. The UWB radio 602 may include circuitry for a transceiver, transmitter, receiver, transmit antenna(s), and / or receive antenna(s)) (not shown). The DT-Tag 604 and HUS Controller 606 may transmit and / or receive UWB signals using the UWB radio 602. The DT-Tag 604 may detect occupied slots. Then the DT-Tag 604 may communicate 608 the occupied slots to the HUS Controller 606. Then the HUS Controller 606 may transmit information regarding the occupied slots using the UWB radio 602. In some embodiments, a DT-Tag 604 and a HUS Controller 606 may he part of the same processor. In some embodiments, a DT-Tag 604 and a HUS Controller 606 may be part of different processors. In some embodiments, a processor may facilitate communication between a DT-Tag 604 and / or HUS Controller 606. In some embodiments, a DT-Tag 604 and / or HUS Controller 606 may store information regarding the occupied slots in a memory. In some embodiments, a processor associated with UWB device 600 may be referred to as the primary processor.

[0042] A DT-Tag 604 may be used on the UWB device 600 to detect messages sent by DT-Anchors. When a message (a Poll DTM, a Response DTM, or a Final DTM) is received by the DT-Tag 604 during a given ranging round, the UWB device 600 (e.g., the HUS Controller 606), may mark the slots associated with this ranging round as “occupied” and may store this information. A HUS Controller 606 may read information regarding occupied slots to determine which slots to allocate to secondary session(s). The HUS Controller 606 may generally allocate any slot to secondary session(s) except those marked as “occupied.” Thus, devices in a secondary session typically will not send an UWB message within a HUS during the ranging rounds used by nearby DT-Anchors. As a result, the activity of a given UWB service may have minimal impact on a user experience of an indoor positioning service provided by a DL-TDoA network.

[0043] In some embodiments, a module may be considered an aggregate unit of computer code which may be equipped to perform a function on a processor. The DT-Tag 604 and the HUS Controller 606 may be implemented as modules on UWB device 600.

[0044] FIG. 7 illustrates an example of slot allocation, according to some aspects of the present disclosure. In this example, a DL-TDoA Session 700 includes one or more RBs 702, each of which includes six RRs 704. In some embodiments, as in at least one of the example DL-TDoA networks described in FIGS. 3-4, a HUS Controller 1 710 may detect one or more messages from DT-Anchor(s) during a Ranging Round, such as Ranging Round 2. Then slots 10 to slot 19 714, which may be considered associated with Ranging Round 2, may be marked as occupied. The HUS Controller 710 may allocate any of the remaining slots toSecondary Session(s). This allocation may be considered to form a Hybrid Ranging Block 712, in which 5 / 6th of the time may be used by the HUS Controller 710 to allocate slots.

[0045] In some embodiments, as in at least one of the example DL-TDoA networks described in FIGS. 3-4, a HUS Controller 2 720 may detect one or more messages from DT- Anchor(s) during Ranging Rounds 3-4. Then slots 20 to slot 59 724, which may be considered associated with Ranging Rounds 3-4, may be marked as occupied. The HUS Controller 720 may allocate any of the remaining slots to Secondary Session(s). This allocation may be considered to form a Hybrid Ranging Block, in which 2 / 3rd of the time may be used by the HUS Controller 720 to allocate slots. Notably, the techniques associated with FIG. 7 may offer considerably more available slots for HUS than the techniques associated with FIG. 5.

[0046] In some embodiments, a slot’s number may be considered its slot value. For example, slot 10 would have a slot value of 10. In some embodiments, one or more RRs may include a range of slots. For example, the first slot in a range of slots may be considered the first slot of a RR and the last slot in the slot range may be considered the last slot in a RR. In some embodiments, a range of slots may be considered a slot range or a set of slots. In some embodiments, a set of RRs may be considered one RR or more than one RR. In some embodiments, a set of slots may be considered one slot or more than one slot.

[0047] FIG. 8 illustrates an example of operation of a HUS 800, according to some aspects of the present disclosure. In some embodiments, in step 1, a HUS Controller 802 may establish a HUS session associated with one or more secondary sessions, for example two secondary sessions with sessions IDs X and Y. In some embodiments, as part of this step, one or more HUS Controlees 804, 806 may establish secondary sessions. In step 2, a HUS Controller’s 802 DT-Tag may listen to surrounding DT-Anchors for DL-TDoA signals. A HUS Controller 802 may receive DL-TDoA signals at one or more slots and may mark those one or more slots as “occupied.” For example, if a HUS Controller 802 received a DL-TDoA signal during any of slots 10 to 19, the HUS Controller 802 may mark slots 10 to 19 as occupied. As a more concrete example, during step 2, the DT-Tag on the HUS Controller may listen (during a whole ranging block) to DT-Anchors and receive some DL-TDoA messages during Ranging Round 2. Therefore, the DT-Tag marks slots 10 to 19 (associated with Ranging Round 2 as shown in Figure 4) as “occupied”.

[0048] In step 3, a HUS Controller 802 may allocate unoccupied slots to secondary session(s). For example, if slots 10 to 19 are occupied, a HUS Controller may allocate any slots not from slots 10 to 19 for Secondary Sessions X and Y. Then a HUS Controller maytransmit a message 814 to one or more HUS Controlees 804, 806 indicating the allocated slots. For example, a HUS Controller may transmit a CM type 3 814 indicating for Session ID: X to begin at slot index start 20 and end at slot index end 59 and for Session ID: Y to begin at slot index start 60 and slot index end 79. During the lifetime of the HUS session, the HUS Controller may listen to DT-Anchors at regular intervals (to maintain the list of slots marked as "occupied" up to date).

[0049] In some embodiments, in addition to the HUS Controller, a Secondary Controller may also attempt to detect the slots occupied by DL-TDoA network(s) and may provide this information to the HUS Controller. These embodiments may improve detection of slots occupied by DL-TDoA (for example, if the HUS Controller is not within the line of sight (LOS) of a nearby DT-Anchor installed in the vicinity).

[0050] FIG. 9 illustrates an example functional diagram of a HUS controlee device 900, according to some aspects of the present disclosure. In some embodiments, a DT-Tag 904, a HUS Controlee 906, and a Secondary Controller 910 may transmit and receive signals using an UWB radio 902 (the UWB radio 902 may include a transceiver, transmitter, receiver, transmit antenna(s), and / or receive antenna(s)). A DT-Tag 904 may detect RRs occupied by a DL-TDoA network. The DT-Tag may communicate 908 the occupied slots to the HUS Controlee 906. Then the HUS Controlee 906 may transmit information regarding the occupied slots to a HUS Controller using the UWB radio 902. A Secondary Controller 910 may transmit and receive signals (using an UWB radio 902) from one or more Secondary Controlees typically operating on the same sensing session. In some embodiments, a HUS Controlee 906 may communicate directly with a Secondary Controller 910 regarding allocated slots. In some embodiments, a DT-Tag 904, a HUS Controlee 906, and a Secondary Controller 910 may be part of the same processor. In some embodiments, a DT-Tag 904, a HUS Controlee 906, and a Secondary Controller 910 may be part of different processors. In some embodiments, a processor may facilitate communication between a DT-Tag 904 and / or a HUS Controlee 906 and / or a Secondary Controller 910. In some embodiments, a DT-Tag 904 and / or a HUS Controlee 906 and / or a Secondary Controller 910 may store information regarding the occupied slots in a memory. In some embodiments, a processor associated with UWB device 900 may be referred to as the secondary processor.

[0051] FIG. 10 illustrates an example of an UWB message payload 1000, according to some aspects of the present disclosure. Information regarding allocation of slots may be provided within the pay load of one or more UWB messages. For example, a DT-Tag may detect occupied slots at regularintervals. The HUS Controlee may those occupied slots to an HUS Controller. This information may be provided within the payload of dedicated UWB message, such as UWB message payload 1000.

[0052] The UWB message payload 1000 includes parameters 1002, each with a corresponding size 1004 in bits. The UWB message payload 1000 includes a Session ID 1010, Number of Occupied Slot Ranges 1012, and Occupied Slot Range(s) 1014. In some embodiments, Session ID 1010 may be 32 bits, Number of Occupied Slot Range(s) 1012 may be 8 bits, and Occupied Slot Ranges 1014 may be 16*N bits where N may represent the number of occupied slot ranges. Session ID 1010 may indicate the session ID of a secondary session, which may also be referred to as a “phase.” In some embodiments, octet 0 of the Occupied Slot Range(s) field may indicate the number of the first slot within the range and octet 1 may indicate the number of the last slot within the range.

[0053] FIG. 11 illustrates an example of operation of a HUS system 1100, according to some aspects of the present disclosure. In some embodiments, in step I, a HUS Controller 1 102 establishes a HUS session associated with one or more secondary sessions, such as session ID X. Then a HUS Controller may transmit one or more CM Type 3 1114 to a Secondary Controller 1104 and a Secondary Controlee 1106. For example, a HUS Controller 1102 may transmit in a CM type 3 1114 for Session ID X to use slots 5 to 35. In step 2, a DT- Tag listens and determines one or more slots occupied by a DL-TDoA network. For example, a DT-Tag associated with a Secondary Controller 1104 may detect that slots 10 to 19 are occupied by a DL-TDoA network. The Secondary Controller 1104 may send the list of occupied slots to a HUS Controller 1102 in one or more dedicated UWB messages 1116 (labeled as “Scheduling Information” in FIG. 11). This list of occupied slots may also be piggy -backed to any existing UWB message, or may be sent as a data payload in a data session, or the list may be provided by the Secondary Controller to the HUS Controller out of band using another radio access technology (such as Bluetooth Low Energy). In step 3, a HUS Controller may allocate unoccupied slots to a Secondary Session. Then a HUS Controller 1102 may transmit one or more messages 11 18 to a Secondary Controller 1104 and a Secondary Controlee 1106. For example, a HUS Controller may transmit a CM type 3 1118 for session ID X indicating to a Secondary Controller 1104 and a Secondary Controlee 1106 a range of unoccupied slots. As a more specific example, instead of choosing the slots 5 to 35 as in the previous ranging block, the HUS Controller may allocate the slots 20 to 50 to a Secondary Controlee 1106 (thus, avoiding the slots 10 to 19 marked as “occupied”). This new slot allocation may then be provided to a Secondary Controller 1104 and / or a Secondary Controlee 1106 in a CM Type 3 message 1118.

[0054] In some embodiments, if a HUS Controller also detects occupied slots (similar to at least one embodiment associated with FIG. 8), the list of slots that should not be allocated by the HUS Controller to one or more Secondary Sessions may be considered a union of: (1) the list of occupied slots provided by any HUS Controlee, Secondary Controller, and / or Secondary Controlee; and (2) the list of occupied slots detected by the HUS Controller.

[0055] In some embodiments, a Secondary Controlee may attempt to detect the slots occupied by DL-TDoA and may provide information regarding those “occupied slots” to a Secondary Controller. This information may then be used by Secondary Controller when allocating slots to one or more Secondary Controlees for transmission or reception. For example, if a Secondary Session is a ranging session, a Ranging Device Management List (RDML) may be used to transmit information regarding the occupied slots. For another example, if a Secondary Session is a data session, a Data Transfer Phase Control Message (DTPCM) may be used to transmit information regarding the occupied slots. A CM type 1 and / or a CM type 2 might also be used to transmit information regarding the occupied slots. A CM Type 1, CM Type 2, and / or DTPCM may be sent by a Secondary Controller and may be received by Secondary Controlee(s).

[0056] In some embodiments a Secondary Controlee may indicate to a Secondary Controller, in an UWB message or in a payload sent over a link layer connection, the list of slots marked as “occupied” by the Secondary Controlee. Alternatively, information on occupied slots may be provided by the Secondary Controlee to the Secondary Controller out of band, using another radio access technology, such as Bluetooth Low Energy. The Secondary Controller may exclude the slots marked as “occupied” when allocating slots for a given Secondary Controlee.

[0057] FIG. 12 illustrates an example functional diagram of a HUS controlee device 1200, according to some aspects of the present disclosure. In some embodiments, a DT-Tag 1204, a HUS Controlee 1206, and a Secondary Controlee 1210 may transmit and receive signals using an UWB radio 1202 (the UWB radio 1202 may include a transceiver, transmitter, receiver, transmit antenna(s), and / or receive antenna(s)). A DT-Tag 1204 may detect RRs occupied by a DL-TDoA network. The DT-Tag may communicate 1208 the occupied slots to the HUS Controlee 1206. Then the HUS Controlee 1206 may transmit information regarding the occupied slots to a HUS Controller using the UWB radio 1202. A Secondary Controlee 1210 may transmit and receive signals (using an UWB radio 1202) to one or more Secondary Controller typically operating on the same sensing session as the Secondary Controlee 1210. In some embodiments, a HUS Controlee 1206 may communicatedirectly with a Secondary Controlee 1210 regarding allocated slots. In some embodiments an UWB device 1200 may not include a HUS Controlee 1206. In some embodiments, a DT-Tag 1204, a HUS Controlee 1206, and a Secondary Controlee 1210 may be part of the same processor. In some embodiments, a DT-Tag 1204, a HUS Controlee 1206, and a Secondary Controlee 1210 may be part of different processors. In some embodiments, a processor may facilitate communication between a DT-Tag 1204 and / or a HUS Controlee 1206 and / or a Secondary Controlee 1210. In some embodiments, a DT-Tag 1204 and / or a HUS Controlee 1206 and / or a Secondary Controlee 1210 may store information regarding the occupied slots in a memory. In some embodiments, the processor associated with UWB device 1200 may be referred to as the tertiary processor. In some embodiments, one or more UWB devices may include a secondary controlee module.

[0058] FIG. 13 illustrates an example of operation of a HUS system 1300, according to some aspects of the present disclosure. Among other things, FIG. 13 illustrate an example of detection of occupied slots by a Secondary Controlee 1306. In some embodiments, in step 1, a HUS Controller 1302 establishes a HUS Session associated with one or more Secondary Sessions, such as session ID X. In step 2, a DT-Tag listens and determines one or more slots occupied by DL-TDoA. Then a HUS Controller may transmit one or more messages 1320 to a Secondary Controller 1304 and a Secondary Controlee 1306. For example, a HUS Controller 1302 may transmit in a CM type 3 message 1320 for Session ID X to use slots 20 to 59. In step 3, a Secondary Controller 1304 may allocate unoccupied slots to a Secondary Session. Then a Secondary Controller 1304 may transmit one or more messages 1322 to a Secondary Controlee 1306. For example, a Secondary Controller 1304 may transmit a DTPCM for session ID X indicating to a Secondary Controlee 1306 an allocated slot range. In step 4, a Secondary Controlee 1306, having determine occupied slots, may transmit one or more messages 1324 indicating the occupied slots to a Secondary Controller. For example, if a Secondary Controlee detected slots 10 to 30 as occupied, the Secondary Controlee may send a data message 1324 during slot 25, indicating the occupied slots. In step 5, a Secondary Controller 1304 may allocate a new range of slots avoiding the occupied slots. Then a Secondary Controller 1304 may transmit a message to a Secondary Controlee indicating the new slot range. For example, a Secondary Controller 1304 may allocate a new slot range from 31 to 36 avoiding the occupied slot range of 10 to 30. Then the Secondary Controller may transmit the new slot range of 31 to 36 to the Secondary Controlee using a one or more messages, such as a DTPCM.

[0059] A more concrete example using FIG. 13 is discussed below. In step 1, a HUS associated with one or more Secondary Sessions may be established. During step 2, a DT-Tag on a Secondary Controlee 1306 may detect that slots 10 to 30 are occupied by DL-TDoA. During step 3, a Secondary Controller 1304 may allocate slots 25 to 30 to a Secondary Controlee 1306. This slot allocation may then indicated to one or more Secondary Controlees 1306 in a DTPCM message 1322. In step 4, a Secondary Controlee 1306 may use one of its allocated slots (for example, slot 25) to provide the list of occupied slots (for example, as a payload sent over link layer). In some embodiments, such as when a secondary session is configured as a “ranging session,” slot- allocation information may be piggy-backed to an UWB message sent during ranging. In step 5, the Secondary Controller 1304 may allocate slots to the Secondary Session, avoiding the slots 10 to 30 marked as occupied. This new slot allocation may then be provided to the Secondary Controlee 1306 in a message 1326, such as a DTPCM or if the Secondary Session is a ranging session, in a RDML.

[0060] In some embodiments, at least some of the embodiments associated with FIG. 13 may be combined with the embodiments associated with FIG. 8 and / or FIG. 11. More specifically, in some embodiments, a HUS Controller may detect occupied slots before allocating slots in a CM Type 3. In some embodiments, a Secondary Controlee may detect occupied slots before allocating slots in a DTPCM.

[0061] In some embodiments, any device (including any device with a Secondary Controller and / or Secondary Controlee; and including any embodiment analogous to the embodiments depicted in Figs. 6, 9, and 12) may have a HUS controller and / or HUS controlee and may allocate slots for itself and / or other devices.

[0062] In some embodiments, fields labeled as “occupied slots” may be used for other purposes. In some embodiments, a given slot may be marked as “occupied” when some DL- TDoA messages are detected during those slots. However, the marking “occupied slots” may also be utilized in other situations. For example, in some embodiments, if an UWB device (for example, a Secondary Controller and / or a Secondary Controlee) knows in advance that it may not be able to use some specific slots (e.g., if the device might need to communicate on another radio access technology during those slots), the UWB device may indicate those slots as “occupied slots.”

[0063] In some embodiments, a device may indicate lists of “preferred slots” instead or in addition to “occupied slots.” That is, an indication on “preferred slots” may also be provided by an UWB device (for example, a Secondary Controller and / or a Secondary Controlee) instead of or in addition to the indication on “occupied slots.” For example, in someembodiments, if an UWB device is performing a payment transaction involving some predictable processing time between the messages sent, an UWB device may know the earliest slots during which it will be able to transmit a given message. Thus, in some embodiments, the UWB device may be able to avoid wasting slots (for example, if the message to be sent is not yet ready at a given allocated slot). In some embodiments, the UWB device may also optimize the duration of a transaction by reserving a slot to transmit as soon as the message is ready to be transmitted.

[0064] In some embodiments, a device may be able to handle conflicting slot preferences. More specifically, in some embodiments, if the same slot is marked as “preferred” by multiple Secondary Sessions, a session priority field (for example, labeled “SESSION_PRIORITY”) may indicate the priority of a given session. Session priority fields may be used by a HUS Controller (when allocating slots to Secondary Sessions) or by a Secondary Controller (when allocating slots to Secondary Controlees) to determine to which session a slot may be allocated.

[0065] In some embodiments, a session, a controller, or a device may be assigned one or more session priority values which may indicate the priority of the associated session. A session priority value may be stored in the field SESSION_PRIORITY or any other field.

[0066] FIG. 14 illustrates an example method 1400 of UWB device operation, according to some aspects of the present disclosure. In step 1402, a HUS controller may establish a HUS session associated with Secondary Session(s). Examples of step 1402 are illustrated in FIGS. 8 (e.g., step 1), 11 (e.g., step 1), and 13 (e.g., step 1). In step 1404, a DT-Tag may listen to DT-Anchors and may determine that a range of slots are occupied by DL-TDOA. Examples of step 1404 are illustrated in FIGS. 8 (e.g., step 2), 11 (e.g., step 2), and 13 (e.g., step 2). In step 1406, a HUS Controller may allocate slots to Secondary Session(s) that avoid the slot range occupied by DL-TDoA. Examples of step 1406 are illustrated in FIGS. 8 (e.g., step 3), 11 (e.g., step 3), and 13 (e.g., step 3). In step 1408, a HUS Controller may send a control message, such as a CM Type 3 message or DTPCM message, to some or all HUS Controlee(s) indicating the occupied slot range. Examples of step 1408 are illustrated in FIGS. 8 (e.g., 814), 11 (e.g., 1118), and 13 (e.g., step 3).

[0067] FIG. 15 is a block diagram of an example UWB device 1500, according to some aspects of the present disclosure. The UWB device 1500 may be capable of operating in any of the configurations presented herein. For example, the UWB device 1500 may represent one or more of the devices in at least Figs. 6, 9, and 12. In this embodiment, the UWB device 1500 includes a receive antenna 1502, a transmit antenna 1510, a transceiver 1508, aprocessor 1504, and a memory 1506. In some embodiments, the transceiver 1508 is configured to transmit via the transmit antenna 1510, and the transceiver 1508 is configured to receive via the receive antenna 1502. In some embodiments, the transceiver 1508 may be configured to transmit and / or receive any type of UWB signal including but not limited to radio signals, sensing signals, DL-TDoA, TDoA, ranging, two-way ranging, and HUS messages. Received information may be stored in memory 1506. Information stored in memory 1506 may include but is not limited to information regarding occupied slots and slot allocation information. The processor 1504 may be used to convert the received information into other formats. In some embodiments, the other formats may also be stored in the memory 1506. In some embodiments, the processor may be configured to implement functionality for a DT-Tag, a HUS Controller, a HUS Controlee, a Secondary Controller, and / or a Secondary Controlee. In some embodiments, the memory 1506 may be a non- transitory computer-readable medium used for storing programming instructions and other computer code for carrying out various steps described herein. For example, the memory 1506 may include code for causing the processor 1504 to perform the steps in FIG. 14 and / or to cause the UWB device 1500 to implement DT-Tag, a HUS Controller, a HUS Controlee, a Secondary Controller, and / or a Secondary Controlee.

[0068] In some embodiments, the transceiver 1508 may be implemented using a combination of separate transmitter and receiver circuitry (such as analog circuitry) that is connected to other circuitry, such as the processor 1504 or other circuitry, for performing baseband processing. In other embodiments, a single antenna may be used for both transmission and reception. In other embodiments the UWB device 1500 may include more than two antennas and the selection of which antenna(s) is / are used in transmission and which antenna(s) is / are used for reception may be dynamically controlled by the processor 1504. In such an embodiment, the use of multiple antennas may provide multiple snapshots of the received signal which may be then combined by the processor to get a better overall signal.

[0069] The transceiver 1508 may implement UWB communication capability, such as for transmitting and / or receiving UWB packets (whether DL-TDoA packets or messages or HUS session packets or messages), such as described with respect to Figs. 1, 2, 8, 11, 13. The communication device 1500 may represent a smartphone or other device, that also implements Bluetooth, Wi-Fi, cellular, and / or other communication capability, such as by including one or more chips or processors that implement this capability. The transceiver 1508 may be implemented as an integrated circuit, or chip.

[0070] Memory 1506 may include one or more non-transitory storage devices that may include local and / or network accessible storage, a disk drive, a drive array, an optical storage device, a solid-state storage device such as a random access memory (“RAM”) and / or a readonly memory (“ROM”), a programmable ROM, a flash-updateable ROM, and / or the like. Such storage devices may be configured to implement any appropriate data storage, including without limitation, various file systems, database structures, and / or the like. The memory 1506 may be used for storing programming instructions and other computer code for carrying out various steps described herein.

[0071] Persons skilled in the art will recognize that the apparatus, systems, and methods described above can be modified in various ways. Accordingly, persons of ordinary skill in the art will appreciate that the embodiments encompassed by the present disclosure are not limited to the particular exemplary embodiments described above. In that regard, although illustrative embodiments have been shown and described, a wide range of modification, change, and substitution is contemplated in the foregoing disclosure. It is understood that such variations may be made to the foregoing without departing from the scope of the present disclosure. Accordingly, it is appropriate that the appended claims be construed broadly and in a manner consistent with the present disclosure.

Claims

CLAIMSWhat is claimed is:

1. A method performed by an ultra- wideband (UWB) device, the method comprising: participating in establishing a Hybrid UWB Scheduling (HUS) session associated with a HUS secondary session; listening for downlink time difference of arrival (DL-TDoA) messages during a ranging block in a DL-TDoA session, wherein the ranging block comprises a first time block and a second time block; detecting at least one DL-TDoA message during the first time block in the ranging block, wherein no DL-TDoA messages are detected in the second time block of the ranging block; and based on the detecting, allocating to the HUS secondary session a second time block in a second ranging block of the DL-TDoA session, wherein the second ranging block has a same structure as the ranging block including a corresponding first time block and the corresponding second time block.

2. The method of claim 1, wherein the UWB device is configured as a HUS Controller, and wherein the method further comprises transmitting a message to a HUS Controlee that indicates that the second time block of the second ranging block is available for the HUS secondary session.

3. The method of claim 2, wherein the message is a CM Type 3 message.

4. The method of claim 1 , wherein each of the time blocks is subdivided into a plurality of time periods, wherein each of the plurality of time periods comprises a first time period and a second time period, wherein the at least one DL-TDoA message is detected during the first time period of the first time block of the ranging block, and wherein no DL-TDoA messages are detected during the second time period of the first time block of the ranging block.

5. The method of claim 1, wherein the UWB device is configured as a HUS Controlee, and wherein the method further comprises:transmitting a first message to a HUS Controller that indicates that the first time block of the ranging block is occupied; and in response to the first message, receiving a second message from the HUS Controller that allocates the second time block of the second ranging block for HUS communication, wherein the UWB device communicates HUS messages using the HUS secondary session during the second time block of the second ranging block.

6. The method of claim 1 , wherein each of the time blocks comprises a ranging round in a DL-TDoA session.

7. The method of claim 5, wherein the second time block of the second ranging block is subdivided into time slots for the HUS messages.

8. The method of claim 1, wherein the UWB device is configured as a secondary HUS Controlee in the HUS secondary session, and wherein the method further comprises: receiving a data message indicating a time slot allocation for the HUS Controlee to use for data transmission; transmitting a second data message using the time slot allocation, wherein the data message indicates the second time block of the second ranging block for the HUS secondary session is available; receiving a third data message indicating for the HUS Controlee to use the second time block of the second ranging block for data transmission; and using the second time block of the second ranging block for the HUS secondary session.

9. The method of claim 8, wherein the data message and the third data message are Data Transfer Phase Control Messages (DTPCMs).

10. An ultra-wideband (UWB) device comprising: a UWB transceiver; and a processor configured to: establish a Hybrid UWB Scheduling (HUS) session associated with a HUS secondary session;listen for downlink time difference of arrival (DL-TDoA) messages, via the UWB transceiver, during a ranging block in a DL-TDoA session, wherein the ranging block comprises a first time block and a second time block; detect at least one DL-TDoA message during the first time block in the ranging block, wherein no DL-TDoA messages are detected in the second time block of the ranging block; and based on the detecting, allocate to the HUS secondary session a second time block in a second ranging block of the DL-TDoA session, wherein the second ranging block has a same structure as the ranging block including a corresponding first time block and the corresponding second time block.

11. The UWB device of claim 10, wherein the processor is further configured as a HUS Controller, and wherein the UWB transceiver is configured to transmit a message to a HUS Controlee that indicates that the second time block of the second ranging block is available for the HUS secondary session.

12. The UWB device of claim 11, wherein the message is a CM Type 3 message.

13. The UWB device of claim 10, wherein each of the time blocks is subdivided into a plurality of time periods, wherein each of the plurality of time periods comprises a first time period and a second time period, wherein the at least one DL-TDoA message is detected during the first time period of the first time block of the ranging block, and wherein no DL- TDoA messages are detected during the second time period of the first time block of the ranging block.

14. The UWB device of claim 10, wherein the processor is further configured as a HUS Controlee, and wherein the UWB transceiver is configured to: transmit a first message to a HUS Controller that indicates that the first time block of the ranging block is occupied; and in response to the first message, receive a second message from the HUS Controller that allocates the second time block of the second ranging block for HUS communication, wherein the processor is configured to communicate HUS messages using the HUS secondary session during the second time block of the second ranging block.

15. The UWB device of claim 10, wherein each of the time blocks comprises a ranging round in a DL-TDoA session.

16. The UWB device of claim 10, wherein the processor is further configured as a secondary HUS Controlee in the HUS secondary session, wherein UWB transceiver is configured to: receive a data message indicating a time slot allocation for the HUS Controlee to use for data transmission; transmit a second data message using the time slot allocation, wherein the data message indicates the second time block of the second ranging block for the HUS secondary session is available; and receive a third data message indicating for the HUS Controlee to use the second time block of the second ranging block for data transmission, and wherein the processor is further configured to: use the second time block of the second ranging block for the HUS secondary session.

17. A non-transitory computer-readable medium (CRM) having program code recorded thereon, the program code comprising: code for causing an ultra-wideband (UWB) device to participate in establishing a Hybrid UWB Scheduling (HUS) session associated with a HUS secondary session; code for causing the UWB device to listen for downlink time difference of arrival (DL-TDoA) messages during a ranging block in a DL-TDoA session, wherein the ranging block comprises a first time block and a second time block; code for causing the UWB device to detect at least one DL-TDoA message during the first time block in the ranging block, wherein no DL-TDoA messages are detected in the second time block of the ranging block; and code for causing the UWB device to detect, based on the detecting, allocate to the HUS secondary session a second time block in a second ranging block of the DL-TDoA session, wherein the second ranging block has a same structure as the ranging block including a corresponding first time block and the corresponding second time block.

18. The non-transitory CRM of claim 17, wherein the UWB device is configured as a HUS Controller, and wherein the non-transitory CRM further comprises:code for causing the UWB device to transmit a message to a HUS Controlee that indicates that the second time block of the second ranging block is available for the HUS secondary session.

19. The non-transitory CRM of claim 17, wherein the UWB device is configured as a HUS Controlee, and wherein the non-transitory CRM further comprises: code for causing the UWB device to transmit a first message to a HUS Controller that indicates that the first time block of the ranging block is occupied; and code for causing the UWB device to, in response to the first message, receive a second message from the HUS Controller that allocates the second time block of the second ranging block for HUS communication, wherein the UWB device is configured to communicate HUS messages using the HUS secondary session during the second time block of the second ranging block.

20. The non-transitory CRM of claim 17, wherein each of the time blocks comprises a ranging round in a DL-TDoA session.

Images