Interleaving ultra-wideband positioning services with other ultra-wideband services

Abstract

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

Description

[0001] Related applications

[0002] This 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 entirety. Technical Field

[0003] This disclosure generally relates to ultra-wideband wireless technology, and more specifically to systems, methods and apparatus for effectively providing ultra-wideband positioning services in coexistence with other ultra-wideband services. Background Technology

[0004] Ultra-wideband (UWB) generally refers to wireless communication technologies that use a wide bandwidth, such as approximately 500 MHz or greater, or typically have a bandwidth greater than 20% of the center frequency by 10 dB. UWB-based positioning systems, such as downlink time difference of arrival (DL-TDoA) systems, can be deployed in areas using other UWB services, such as Hybrid UWB Scheduling (HUS). HUS can refer to the ability to schedule UWB sessions configured in a time-scheduling mode or a contention-based mode at fixed times relative to each other, such that the UWB sessions occur in a deterministic time sequence within HUS ranging rounds. HUS is currently being considered in, for example, the Fine Ranging (FiRa) consortium.

[0005] UWB messages sent within a hybrid session (or HUS session) may interfere with UWB messages sent by the DL-TDoA anchor (DT anchor). As the number and density of UWB services increase, this interference may lead to degradation of the DL-TDoA service, and consequently, users may be unable to receive messages sent by the DT anchor and therefore may be unable to determine their location. Therefore, a solution is needed in complex UWB environments that allows DL-TDoA sessions and HUS sessions to coexist effectively. Summary of the Invention

[0006] Embodiments of this disclosure include systems, apparatus, and methods for interleaving DL-TDoA with other UWB transports.

[0007] In an exemplary aspect, a method performed by a UWB device is disclosed. In some embodiments, the method may include participating in the establishment of an HUS session associated with a Hybrid UWB Scheduling (HUS) secondary session. The method may further include listening for DL-TDoA messages during a ranging block in the DL-TDoA session, wherein the ranging block includes 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 of the ranging block, wherein no DL-TDoA message is detected in the second time block of the ranging block. The method may further include, based on the detection, allocating a second time block in the second ranging block of the DL-TDoA session to the HUS secondary session, wherein the second ranging block has the same structure as the ranging block, and the second ranging block includes a corresponding first time block and a corresponding second time block.

[0008] 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 to listen for DL-TDoA messages via the UWB transceiver during a ranging block in a DL-TDoA session, wherein the ranging block includes a first time block and a second time block. The processor may be further configured to detect at least one DL-TDoA message during the first time block in the ranging block, wherein no DL-TDoA message is detected in the second time block of the ranging block; and based on the detection, to allocate a second time block in the second ranging block of the DL-TDoA session to the HUS secondary session, wherein the second ranging block has the same structure as the ranging block, and the second ranging block includes a corresponding first time block and a corresponding second time block.

[0009] In another exemplary aspect, a non-transitory computer-readable medium (CRM) having program code recorded thereon is provided. In some embodiments, the program code includes code for causing a UWB device to participate in establishing an 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 includes 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 message is detected in the second time block of the ranging block; and code for causing the UWB device to allocate a second time block in the second ranging block of the DL-TDoA session to the HUS secondary session based on the detection, wherein the second ranging block has the same structure as the ranging block and includes a corresponding first time block and a corresponding second time block.

[0010] Further aspects, features, and advantages of this disclosure will become apparent from the following detailed description. Attached Figure Description

[0011] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate several aspects of this disclosure and, together with the description of the drawings, serve to explain the principles of this disclosure.

[0012] Figure 1 Examples of UWB DL-TDoA operation according to some aspects of this disclosure are illustrated.

[0013] Figure 2 Examples of HUS operation based on some aspects of this disclosure are illustrated.

[0014] Figure 3 An example of a DL-TDoA network deployment based on some aspects of this disclosure is illustrated.

[0015] Figure 4 Illustrations based on some aspects of this disclosure Figure 3 Instance configuration of DL-TDoA network.

[0016] Figure 5 This illustration depicts the coexistence of DL-TDoA sessions and HUS sessions according to some aspects of this disclosure.

[0017] Figure 6 An example functional diagram of a UWB device according to some aspects of this disclosure is shown.

[0018] Figure 7 Examples of time slot allocation according to some aspects of this disclosure are illustrated.

[0019] Figure 8 Examples of HUS operation based on some aspects of this disclosure are illustrated.

[0020] Figure 9 Example functional diagrams of HUS controlled devices according to some aspects of this disclosure are shown.

[0021] Figure 10 Examples of UWB message payloads according to some aspects of this disclosure are illustrated.

[0022] Figure 11 Examples of operation of a HUS system according to some aspects of this disclosure are illustrated.

[0023] Figure 12 Example functional diagrams of HUS controlled devices according to some aspects of this disclosure are shown.

[0024] Figure 13 Examples of operation of a HUS system according to some aspects of this disclosure are illustrated.

[0025] Figure 14 Exemplary methods of operating a UWB device according to some aspects of this disclosure are illustrated. Figure 15 This is a block diagram of an example UWB device based on some aspects of this disclosure. Detailed Implementation

[0026] To facilitate understanding of the principles of this disclosure, embodiments illustrated in the drawings will now be discussed, and specific terminology will be used in the description. Nevertheless, it should be understood that this is not intended to limit the scope of this disclosure. Any changes and further modifications to the described apparatus, systems, and methods, as well as any further application of the principles of this disclosure, are fully considered and included within this disclosure, as would normally occur to those skilled in the art to which this disclosure pertains. Specifically, upon careful consideration, features, components, and / or steps described with respect to one embodiment may be combined with features, components, and / or steps described with respect to other embodiments of this disclosure. However, for the sake of brevity, multiple repetitions of these combinations will not be described separately.

[0027] For complex UWB environments, it has been proposed that DL-TDoA sessions and HUS sessions run at different times. For example, as currently proposed within the FiRa Consortium, a DL-TDoA session can be configured to operate from the initial time T0 of the ranging block to time T1. Other UWB services can operate from time T1 until the end of the ranging block, potentially allowing UWB messages sent by those services to avoid interfering with DL-TDoA messages. However, this solution can be inefficient in some cases. For example, suppose the DL-TDoA network participates in the DL-TDoA session during ranging rounds 1 to 6 of the ranging block. Assuming, for example, that the ranging block contains 9 ranging rounds, only one-third of the ranging block (i.e., ranging rounds 7 to 9) will be reserved for other UWB services.

[0028] This document discloses systems, methods, and apparatuses for interleaving DL-TDoA sessions with other UWB transmissions, such as HUS sessions, by controlling the allocation of ranging rounds between DL-TDoA transmissions and other ultra-wideband transmissions. The techniques presented herein allow UWB services using HUS sessions to operate simultaneously with DL-TDoA networks. Therefore, this disclosure allows DL-TDoA transmissions and other UWB transmissions to coexist and operate efficiently in the same environment.

[0029] The disclosed embodiments can be applied to a wide variety of UWB use cases and various UWB system, method, and / or device configurations. A non-exhaustive list of such use cases is provided. For example, in a train station, using DL-TDoA could potentially enable passengers to locate their position within the station, while one or more HUSs could be used at the doors to allow user passage. In a shopping mall, DL-TDoA could potentially enable customers to locate their position, while one or more HUSs could be used for in-store payments.

[0030] DL-TDoA is a UWB feature that typically enables UWB devices to accurately determine their location. DL-TDoA typically utilizes DT anchors, which can be deployed and configured within the area to be covered. Then, at least one device (e.g., acting as a DL-TDoA tag (DT tag)) can typically anonymously locate its position within this area by listening to at least one message sent by the DT anchor, such as DL-TDoA messages (DTMs) (e.g., polling DTMs, responding DTMs, and / or final DTMs).

[0031] Figure 1 Examples of operation of a UWB DL-TDoA 100 according to some aspects of this disclosure are illustrated. In some embodiments, the initiator DT anchor 102 may initially transmit a polling DTM 112 to the responder DT anchor 1 106, and in some embodiments, to 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 the responder DT anchor 1 106, and in some embodiments, to any number of DT anchors N 108. When within the range of DT anchors, such as Figure 1 As assumed in the text, the DT tag is capable of receiving polling DTMs and response DTMs sent by the DT anchors. Next, in step 110, the DT tag 104 can estimate its position using the coordinates of the DT anchors 102, 106, 108 obtained out-of-band or in-band (i.e., in the anchor position fields of some or all DTMs 112, 116, 118).

[0032] A hybrid session (or HUS session) can share ranging rounds with multiple secondary sessions. At the start of a given ranging round, the HUS controller can allocate time slots for this ranging round to one or more secondary sessions. The HUS controller can broadcast the time slot allocation information to HUS subjects in one or more messages (e.g., Control Message (CM) Type 3 messages). One or more CM Type 3 messages can be sent by the HUS controller and received by one or more HUS subjects. HUS subjects can listen for these CM Type 3 messages. In some instances, when a HUS subject is the controller of a given secondary session, the HUS subject can use the time slots allocated in the CM Type 3 messages to communicate with one or more secondary subjects of the secondary session. In some embodiments, the HUS controller or a device including a HUS controller can be considered the master controller. The HUS controller can schedule HUS ranging phases by transmitting CM Type 3 messages. The HUS controller can participate in the HUS ranging phase as either a controller or a subject. The controller can be a FiRa device that defines and controls ranging characteristics by sending control messages. The controlled party can be a FiRa device that utilizes ranging characteristics configured, such as those from control messages from the controller. The HUS controlled party can synchronize with the HUS session by receiving CM Type 3. The HUS controlled party can participate in the HUS ranging phase as either the controller or the controlled party in one or more HUS auxiliary sessions.

[0033] Figure 2 Examples of operation of HUS 200 according to some aspects of this disclosure are illustrated. In some embodiments, in step 1, HUS controller 202 may establish an HUS associated with one or more secondary sessions. For example, HUS may be associated with two secondary sessions having session identifiers (IDs) X and Y. In step 2, HUS controller 202 may allocate one or more time slots to the secondary sessions. HUS controller 202 may then transmit one or more messages 220, such as CM type 3, to devices 204, 206, 208, 210 indicating the range of time slots that each secondary session can communicate. HUS controlled parties 204, 208 (which may also be secondary controllers of the sessions) may then communicate with secondary controlled parties 206, 210 (also referred to as HUS secondary controlled parties) during the time slots allocated for the sessions in one or more messages.

[0034] For example, the HUS controller can transmit CM type 3 220 to HUS controlled party 1 204 (which may also be a secondary controller of session X) and secondary controlled party 1 206, allocating time slots 20 to 59 to session ID X. In this example, CM type 3 220 may contain a time slot index starting at 20 and / or an index ending at 59. In some embodiments, the time slot index may also be referred to as a time slot value. In this example, in step 4.A, HUS controlled party 1 204 (which may also be a secondary controller of session X) may communicate with secondary controlled party 1 206 during time slots 20 to 59. For another example, the HUS controller can transmit CM type 3 220 to HUS controlled party 2 208 (which may also be a secondary controller of session Y) and secondary controlled party 2 210, allocating time slots 60 to 79 to session ID Y. In this example, CM type 3 220 may contain a time slot index starting at 60 and / or ending at 79. In this example, in step 4.B, HUS controlled party 2 208 (which may also be a secondary controlled party of session Y) may communicate with secondary controlled party 2 210 during time slots 60 to 79.

[0035] Figure 3 The illustration depicts an example of a DL-TDoA network deployment 300 based on some aspects of this disclosure. For example, Figure 3 The area shown can be associated with a shopping mall or office. A DL-TDoA network deployment can include one or more DT anchors. For example, a DL-TDoA network deployment can include... Figure 3The twelve DT anchors shown are labeled "DT anchor n" for n=1, 2, ..., 12. A UWB communication device, including, for example, a HUS controller 332, a secondary controller 334, and / or a secondary controlled party 336, can be configured to interact with the DT anchors. The UWB device can be configured to support UWB services that can coexist with the DL-TDoA network. The UWB communication device can include both HUS and DT tag functionality, as further explained herein. To determine its location, the UWB device (acting as a DT tag) (not shown) can listen for messages periodically sent by the DT anchors. The DL-TDoA network can consist of multiple DT anchors organized in clusters 320 and 330. The DT anchors can be distributed over a potentially wide deployment area. Clusters 320 and 330 can be a group of DT anchors exchanging DTMs to provide location services to DT tags in a specific area or zone covered by clusters 320 and 330. Clusters 320 and 330 may typically contain one initiator DT anchor and one or more responder DT anchors. Each DT anchor may be pre-configured with: a set of ranging rounds during which the DT anchor should be transmitted, and the role of the DT anchor during a given ranging round (e.g., initiator DT anchor or responder DT anchor). Depending on the embodiment, HUS controller 332, secondary controller 334, and secondary controlled party 336 may operate in association with a DL-TDoA network deployment.

[0036] For example, HUS controller 2332, secondary controller 334, and secondary controlled party 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 their proximity, HUS controller 2332, secondary controller 334, and secondary controlled party 336 may operate in association with DL-TDoA network deployment 330 to achieve potentially optimal results. In some embodiments, HUS controller 2332, secondary controller 334, and secondary controlled party 336 may all comprise the same means. In some embodiments, HUS controller 2332, secondary controller 334, and secondary controlled party 336 may each be a separate means. In some embodiments, depending on the implementation, HUS controller 2332, secondary controller 334, and secondary controlled party 336 may each be any combination separate from or combined with other corresponding means.

[0037] Figure 4 Illustrations based on some aspects of this disclosure Figure 3The diagram shows an instance configuration of a DL-TDoA network 300. The first column 402 of the diagram represents DT anchors. The second column 404 of the diagram represents the corresponding active ranging round for each DT anchor. In some embodiments, the diagram 400 may indicate whether a DT anchor acts as an initiator, a responder, or both. In some embodiments, the diagram 400 may indicate whether a DT anchor is in one or more active ranging rounds. For example, in some embodiments, DT anchor 1 may act as an initiator during ranging round 2, and DT anchors 2 and 3 may act as responders during ranging round 2.

[0038] Figure 5 An example of coexistence between a DL-TDoA session and a HUS session according to some aspects of this disclosure is illustrated. A ranging block (RB) (e.g., ranging block 1 500) in a DL-TDoA session can contain any number of ranging rounds (RR) 506, for example... Figure 5 The nine RRs shown in the document.

[0039] One solution to ensure indoor positioning always functions correctly is to run DL-TDoA sessions and HUS sessions at different times, and Figure 5 An example of this is illustrated. For instance, a DL-TDoA session can be configured to operate from time T0 (e.g., the start of RR 1 506) to time T1 (e.g., the end of RR 6) for each ranging block. Other UWB services, such as one or more HUSs, can operate from time T1 until the end of each ranging block, thereby increasing the likelihood that UWB messages sent by those services will not interfere with DL-TDoA messages. However, this configuration is not always efficient. For example, in Figure 5 In this context, the DL-TDoA network can operate during RR 1 to RR 6 of each ranging block, thereby establishing the DL-TDoA ranging block. Assuming each ranging block contains nine RRs, only one-third of the ranging block (e.g., RR 7 to RR 9) remains for other UWB services, such as one or more HUS.

[0040] This disclosure addresses the coexistence problem between DL-TDoA and HUS services by allowing HUS communication to occur simultaneously (or synchronously) with the ranging rounds used by the DL-TDoA network, provided that HUS messages do not interfere with messages sent by nearby DT anchors. In some embodiments, the HUS controller or other means can allocate time slots within the HUS such that slots are not used for transmission when there is a risk of interfering with messages sent by DT anchors. Thus, for example, the operation of the HUS can successfully avoid impacting the user experience of indoor positioning services provided by the DL-TDoA network.

[0041] In some embodiments, the apparatus can detect ranging rounds used by the DL-TDoA network near the UWB device. The apparatus can then mark the time slots associated with those occupied ranging rounds as "occupied." In some embodiments, the HUS controlled party can indicate to the HUS controller a list of time slots marked as "occupied" by the HUS controlled party in a UWB message or in a payload sent via a link-layer connection. The HUS controller can then exclude time slots marked as "occupied" when allocating time slots for secondary sessions in which the HUS controlled party participates.

[0042] Figure 6 This diagram illustrates an example functional diagram of a UWB device 600 according to some aspects of this disclosure. The UWB device 600 includes a UWB radio 602 and functionality for implementing a DT tag 604 and a HUS controller 606. The UWB radio 602 may include circuitry for a transceiver, transmitter, receiver, one or more transmit antennas, and / or one or more receive antennas (not shown). The DT tag 604 and the HUS controller 606 can use the UWB radio 602 to transmit and / or receive UWB signals. The DT tag 604 can detect occupied time slots. The DT tag 604 can then transmit 608 the occupied time slots to the HUS controller 606. The HUS controller 606 can then use the UWB radio 602 to transmit information about the occupied time slots. In some embodiments, the DT tag 604 and the HUS controller 606 may be part of the same processor. In some embodiments, the DT tag 604 and the HUS controller 606 may be part of different processors. In some embodiments, the processor may facilitate communication between the DT tag 604 and / or the HUS controller 606. In some embodiments, the DT tag 604 and / or the HUS controller 606 may store information about occupied time slots in memory. In some embodiments, the processor associated with the UWB device 600 may be referred to as the main processor.

[0043] DT tag 604 can be used on UWB device 600 to detect messages sent by DT anchors. When DT tag 604 receives a message (polling DTM, responding DTM, or final DTM) during a given ranging round, UWB device 600 (e.g., HUS controller 606) can mark the time slots associated with this ranging round as "occupied" and can store this information. HUS controller 606 can read the information about the occupied time slots to determine which time slots to allocate to one or more secondary sessions. HUS controller 606 can typically allocate any time slots other than those marked as "occupied" to one or more secondary sessions. Therefore, during ranging rounds used by nearby DT anchors, devices in secondary sessions typically do not send UWB messages within the HUS. Thus, activity for a given UWB service may have minimal impact on the user experience of indoor positioning services provided by the DL-TDoA network.

[0044] In some embodiments, a module can be viewed as an aggregate of computer code that can be assembled to perform functions on a processor. The DT tag 604 and HUS controller 606 can be implemented as modules on the UWB device 600.

[0045] Figure 7 An example of time slot allocation according to some aspects of this disclosure is illustrated. In this example, the DL-TDoA session 700 includes one or more RBs 702, each of which includes six RRs 704. In some embodiments, as in Figures 3 to 4 In at least one of the example DL-TDoA networks described herein, HUS controller 1 710 can detect one or more messages from one or more DT anchors during a ranging round (e.g., ranging round 2). Time slots 10 to 19 714, which can be considered associated with ranging round 2, can then be marked as occupied. HUS controller 710 can allocate any of the remaining time slots to one or more secondary sessions. This allocation can be considered as forming a hybrid ranging block 712, where HUS controller 710 can use 5 / 6 of the time to allocate time slots.

[0046] In some embodiments, such as in Figures 3 to 4 In at least one of the DL-TDoA networks described herein, the HUS controller 2 720 can detect one or more messages from one or more DT anchors during ranging rounds 3 to 4. Then, time slots 20 to 59 724, which can be considered associated with ranging rounds 3 to 4, can be marked as occupied. The HUS controller 720 can allocate any of the remaining time slots to one or more secondary sessions. This allocation can be considered as forming a hybrid ranging block, where the HUS controller 720 can use 2 / 3 of the time to allocate time slots. It is worth noting that, with... Figure 7Related technologies can provide HUS with more than Figure 5 There are far more available time slots for the related technologies.

[0047] In some embodiments, a slot number can be considered as its slot value. For example, slot 10 would have a slot value of 10. In some embodiments, one or more RRs can comprise a range of slots. For example, a first slot in a range of slots can be considered as the first slot in an RR, and the last slot in the range can be considered as the last slot in an RR. In some embodiments, a range of slots can be considered as a range of slots or a set of slots. In some embodiments, a set of RRs can be considered as one RR or more than one RR. In some embodiments, a set of slots can be considered as one slot or more than one slot.

[0048] Figure 8 Examples of operation of HUS 800 according to some aspects of this disclosure are illustrated. In some embodiments, in step 1, HUS controller 802 may establish an HUS session associated with one or more secondary sessions (e.g., two secondary sessions with session IDs X and Y). In some embodiments, as part of this step, one or more HUS controlled parties 804, 806 may establish a secondary session. In step 2, the DT tag of HUS controller 802 may listen for DL-TDoA signals at surrounding DT anchors. HUS controller 802 may receive DL-TDoA signals at one or more time slots and may mark those one or more time slots as "occupied". For example, if HUS controller 802 receives a DL-TDoA signal during any of time slots 10 to 19, HUS controller 802 may mark time slots 10 to 19 as occupied. As a more specific example, during step 2, the DT tag on the HUS controller may listen for DT anchors (during the entire ranging block) and receive some DL-TDoA messages during ranging round 2. Therefore, the DT tag will specify time slots 10 to 19 (as shown in the image). Figure 4 The distance measurement round 2 shown in the image is marked as "occupied".

[0049] In step 3, the HUS controller 802 can allocate unoccupied time slots to one or more secondary sessions. For example, if time slots 10 to 19 are occupied, the HUS controller can allocate any time slot other than 10 to 19 to secondary sessions X and Y. Next, the HUS controller can transmit a message 814 indicating the allocated time slots to one or more HUS controlled parties 804, 806. For example, the HUS controller can transmit a CM type 3 814 indicating that for session ID X, the time slot starts at time slot index 20 and ends at time slot index 59, and for session ID Y, the time slot starts at time slot index 60 and ends at time slot index 79. During the lifetime of the HUS session, the HUS controller can periodically monitor the DT anchor point (to keep the list of time slots marked "occupied" up-to-date).

[0050] In some embodiments, in addition to the HUS controller, the secondary controller may also attempt to detect time slots occupied by one or more DL-TDoA networks and may provide this information to the HUS controller. These embodiments may improve the detection of time slots occupied by DL-TDoA networks (e.g., if the HUS controller is not within the line of sight (LOS) of a nearby DT anchor point installed nearby).

[0051] Figure 9An example functional diagram of a HUS controlled party device 900 according to some aspects of this disclosure is illustrated. In some embodiments, a DT tag 904, a HUS controlled party 906, and a secondary controller 910 can use a UWB radio 902 (which may include a transceiver, transmitter, receiver, one or more transmit antennas, and / or one or more receive antennas) to transmit and receive signals. The DT tag 904 can detect RRs occupied by the DL-TDoA network. The DT tag can transmit 908 the occupied time slots to the HUS controlled party 906. The HUS controlled party 906 can then use the UWB radio 902 to transmit information about the occupied time slots to the HUS controller. The secondary controller 910 can (using the UWB radio 902) transmit and receive signals with one or more secondary controlled parties that typically operate on the same sensing session. In some embodiments, the HUS controlled party 906 can communicate directly with the secondary controller 910 regarding the allocated time slots. In some embodiments, the DT tag 904, HUS controlled party 906, and auxiliary controller 910 may be part of the same processor. In some embodiments, the DT tag 904, HUS controlled party 906, and auxiliary controller 910 may be part of different processors. In some embodiments, the processor may facilitate communication between the DT tag 904 and / or the HUS controlled party 906 and / or the auxiliary controller 910. In some embodiments, the DT tag 904 and / or the HUS controlled party 906 and / or the auxiliary controller 910 may store information about occupied time slots in memory. In some embodiments, the processor associated with the UWB device 900 may be referred to as a secondary processor.

[0052] Figure 10 An example of a UWB message payload 1000 according to some aspects of this disclosure is illustrated. Information regarding time slot allocation can be provided in the payload of one or more UWB messages. For example, DT tags can periodically detect occupied time slots. The HUS controlled party can send those occupied time slots to the HUS controller. This information can be provided in the payload of a dedicated UWB message, such as UWB message payload 1000.

[0053] The UWB message payload 1000 includes parameters 1002, each parameter having a corresponding size 1004 in bits. The UWB message payload 1000 includes a session ID 1010, a number of occupied time slot ranges 1012, and one or more occupied time slot ranges 1014. In some embodiments, the session ID 1010 may be 32 bits, the number of occupied time slot ranges 1012 may be 8 bits, and the occupied time slot range 1014 may be 16 bits. N bits, where N can represent the number of occupied time slot ranges. Session ID 1010 can indicate the session ID of a secondary session, which can also be referred to as a "stage". In some embodiments, one or more octet 0s in the occupied time slot range field can indicate the number of the first time slot in the range, and octet 1s can indicate the number of the last time slot in the range.

[0054] Figure 11 An example of the operation of a HUS system 1100 according to some aspects of this disclosure is illustrated. In some embodiments, in step 1, HUS controller 1102 establishes an HUS session associated with one or more secondary sessions (e.g., session ID X). The HUS controller may then transmit one or more CM type 3 1114 to secondary controller 1104 and secondary controlled party 1106. For example, HUS controller 1102 may transmit CM type 3 1114 for session ID X to use time slots 5 to 35. In step 2, DT tags listen for and determine one or more time slots occupied by the DL-TDoA network. For example, a DT tag associated with secondary controller 1104 may detect time slots 10 to 19 occupied by the DL-TDoA network. Secondary controller 1104 may send a list of occupied time slots to HUS controller 1102 in one or more dedicated UWB messages 1116 (in...). Figure 11 (This is marked as "Scheduling Information"). This list of occupied time slots can also be attached to any existing UWB message, or it can be sent as a data payload in a data session, or the list can be provided out-of-band by the secondary controller using another radio access technology (e.g., Bluetooth Low Energy). In step 3, the HUS controller can allocate unoccupied time slots to the secondary session. Then, the HUS controller 1102 can transmit one or more messages 1118 to the secondary controller 1104 and the secondary controlled party 1106. For example, the HUS controller can transmit CM type 3 1118 of session ID X, which indicates a range of unoccupied time slots to the secondary controller 1104 and the secondary controlled party 1106. As a more specific example, the HUS controller can allocate time slots 20 to 50 to the secondary controlled party 1106 (thus avoiding time slots 10 to 19 marked as "occupied") instead of selecting time slots 5 to 35 as in the previous ranging block. This new time slot allocation can then be provided to the secondary controller 1104 and / or the secondary controlled party 1106 in CM type 3 message 1118.

[0055] In some embodiments, if the HUS controller also detects an occupied time slot (similar to...) Figure 8In at least one associated embodiment, the list of time slots that should not be allocated by the HUS controller to one or more secondary sessions can be considered as a combination of: (1) the list of occupied time slots provided by any HUS controlled party, secondary controller and / or secondary controlled party; and (2) the list of occupied time slots detected by the HUS controller.

[0056] In some embodiments, the secondary controlled party may attempt to detect time slots already occupied by the DL-TDoA and may provide information about those “occupied time slots” to the secondary control party. The secondary control party can then use this information when allocating time slots to one or more secondary controlled parties for transmission or reception. For example, if the secondary session is a ranging session, a Ranging Device Management List (RDML) may be used to transmit information about occupied time slots. Similarly, if the secondary session is a data session, a Data Transmission Phase Control Message (DTPCM) may be used to transmit information about occupied time slots. CM Type 1 and / or CM Type 2 may also be used to transmit information about occupied time slots. CM Type 1, CM Type 2, and / or DTPCM may be sent by the secondary control party and received by one or more secondary controlled parties.

[0057] In some embodiments, the secondary controlled party may indicate to the secondary control party a list of time slots marked as "occupied" by the secondary controlled party in a UWB message or in a payload transmitted via a link layer connection. Alternatively, the secondary controlled party may use another radio access technology, such as Bluetooth Low Energy, to provide information about occupied time slots out of band to the secondary control party. When allocating time slots for a given secondary controlled party, the secondary control party may exclude time slots marked as "occupied".

[0058] Figure 12An example functional diagram of a HUS controlled device 1200 according to some aspects of this disclosure is illustrated. In some embodiments, a DT tag 1204, a HUS controlled device 1206, and a secondary controlled device 1210 can use a UWB radio 1202 (which may include a transceiver, transmitter, receiver, one or more transmit antennas, and / or one or more receive antennas) to transmit and receive signals. The DT tag 1204 can detect RRs occupied by the DL-TDoA network. The DT tag can transmit 1208 of the occupied time slot to the HUS controlled device 1206. The HUS controlled device 1206 can then use the UWB radio 1202 to transmit information about the occupied time slot to the HUS controller. The secondary controlled device 1210 can (using the UWB radio 1202) transmit and receive signals with one or more secondary controllers that typically operate on the same sensing session as the secondary controlled device 1210. In some embodiments, HUS controlled party 1206 may communicate directly with secondary controlled party 1210 regarding allocated time slots. In some embodiments, UWB device 1200 may not include HUS controlled party 1206. In some embodiments, DT tag 1204, HUS controlled party 1206, and secondary controlled party 1210 may be part of the same processor. In some embodiments, DT tag 1204, HUS controlled party 1206, and secondary controlled party 1210 may be part of different processors. In some embodiments, the processor may facilitate communication between DT tag 1204 and / or HUS controlled party 1206 and / or secondary controlled party 1210. In some embodiments, DT tag 1204 and / or HUS controlled party 1206 and / or secondary controlled party 1210 may store information about occupied time slots in memory. In some embodiments, the processor associated with UWB device 1200 may be referred to as a level 3 processor. In some embodiments, one or more UWB devices may include a secondary controlled party module.

[0059] Figure 13 Examples of operation of the HUS system 1300 according to some aspects of this disclosure are illustrated. Furthermore, Figure 13The illustration depicts an instance where the secondary controlled party 1306 detects occupied time slots. In some embodiments, in step 1, the HUS controller 1302 establishes a HUS session associated with one or more secondary sessions (e.g., session ID X). In step 2, the DT tag listens for and determines one or more time slots occupied by the DL-TDoA. The HUS controller may then transmit one or more messages 1320 to the secondary controller 1304 and the secondary controlled party 1306. For example, the HUS controller 1302 may transmit a CM type 3 message 1320 for session ID X to use time slots 20 through 59. In step 3, the secondary controller 1304 may allocate unoccupied time slots to the secondary session. The secondary controller 1304 may then transmit one or more messages 1322 to the secondary controlled party 1306. For example, the secondary controller 1304 may transmit a DTPCM for session ID X to indicate the allocated time slot range to the secondary controlled party 1306. In step 4, after determining that a time slot is occupied, the secondary controlled party 1306 can transmit one or more messages 1324 indicating the occupied time slot to the secondary controlled party. For example, if the secondary controlled party detects that time slots 10 to 30 are occupied, it can send a data message 1324 during time slot 25 to indicate the occupied time slot. In step 5, the secondary controlled party 1304 can allocate a new range of time slots to avoid the occupied time slots. Then, the secondary controlled party 1304 can transmit a message to the secondary controlled party indicating the new time slot range. For example, the secondary controlled party 1304 can allocate a new range of time slots from 31 to 36 to avoid the occupied time slot range from 10 to 30. Then, the secondary controlled party can use one or more messages (e.g., DTPCM) to transmit the new time slot range from 31 to 36 to the secondary controlled party.

[0060] The following section discusses the use of Figure 13A more specific example. In step 1, a HUS associated with one or more secondary sessions can be established. During step 2, the DT tag on the secondary controlled party 1306 can detect that time slots 10 to 30 are occupied by DL-TDoA. In step 3, the secondary control party 1304 can allocate time slots 25 to 30 to the secondary controlled party 1306. This time slot allocation can then be indicated to one or more secondary controlled parties 1306 in a DTPCM message 1322. In step 4, the secondary controlled party 1306 can use one of its allocated time slots (e.g., time slot 25) to provide a list of occupied time slots (e.g., as a payload sent through the link layer). In some embodiments, such as when the secondary session is configured as a "ranging session", time slot allocation information can be piggybacked onto UWB messages sent during ranging. In step 5, the secondary control party 1304 can allocate time slots to the secondary session, bypassing time slots 10 to 30 marked as occupied. This new time slot allocation can then be provided to the secondary controlled party 1306 in message 1326 (e.g., DTPCM), or in RDML if the secondary session is a ranging session.

[0061] In some embodiments, with Figure 13 At least some of the associated embodiments can be and Figure 8 and / or Figure 11 Associated combinations of embodiments. More specifically, in some embodiments, the HUS controller can detect occupied time slots before allocating time slots in CM type 3. In some embodiments, the secondary controlled party can detect occupied time slots before allocating time slots in DTPCM.

[0062] In some embodiments, any device (including any device having a secondary controller and / or a secondary controlled party; and including similar) Figure 6 , 9 Any embodiment of the embodiments depicted in 12 may have a HUS controller and / or a HUS controlled party, and may allocate time slots for itself and / or other devices.

[0063] In some embodiments, the field marked "Occupied Time Slots" can be used for other purposes. In some embodiments, a given time slot can be marked as "Occupied" when some DL-TDoA messages are detected during those time slots. However, marking "Occupied Time Slots" can also be used in other situations. For example, in some embodiments, if a UWB device (e.g., a secondary controller and / or a secondary controlled party) knows in advance that it may not be able to use some specific time slots (e.g., if the device may need to communicate over another radio access technology during those time slots), the UWB device can indicate those time slots as "Occupied Time Slots".

[0064] In some embodiments, the device may indicate an alternative or a list of "preferred time slots" in addition to "occupied time slots". That is, the indication of "preferred time slots" in addition to the indication of "occupied time slots" may also be provided by the UWB device (e.g., a secondary controller and / or a secondary controlled party). For example, in some embodiments, if the UWB device is executing a payment transaction involving some predictable processing time between sent messages, the UWB device may know the earliest time slot it will be able to transmit a given message. Therefore, in some embodiments, the UWB device may be able to avoid wasting time slots (e.g., if the message to be transmitted is not yet ready at the given allocated time slot). In some embodiments, the UWB device may also optimize the duration of a transaction by reserving time slots to be transmitted when the message is ready to be transmitted.

[0065] In some embodiments, the apparatus may be able to handle conflicting time slot preferences. More specifically, in some embodiments, if the same time slot is marked as "preferred" by multiple secondary sessions, a session priority field (e.g., marked "SESSION_PRIORITY") may indicate the priority of a given session. The session priority field may be used by the HUS controller (when allocating a time slot to a secondary session) or by the secondary controller (when allocating a time slot to a secondary controlled party) to determine which session the time slot can be allocated to.

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

[0067] Figure 14 An example method 1400 for operating a UWB device according to some aspects of this disclosure is illustrated. In step 1402, the HUS controller may establish a HUS session associated with one or more secondary sessions. An example of step 1402 is illustrated in... Figure 8 (e.g., step 1), 11 (e.g., step 1), and 13 (e.g., step 1). In step 1404, the DT tag can listen to the DT anchor point and determine that the DL-TDOA occupies a certain range of time slots. An example of step 1404 is illustrated in... Figure 8 (e.g., step 2), 11 (e.g., step 2), and 13 (e.g., step 2). In step 1406, the HUS controller can allocate time slots to one or more secondary sessions, bypassing the time slot range occupied by DL-TDoA. An example of step 1406 is illustrated in... Figure 8(e.g., step 3), 11 (e.g., step 3), and 13 (e.g., step 3). In step 1408, the HUS controller may send control messages, such as CM Type 3 messages or DTPCM messages, to some or all HUS controlled parties, indicating the occupied time slot range. An example of step 1408 is illustrated in... Figure 8 (e.g., 814), 11 (e.g., 1118), and 13 (e.g., step 3).

[0068] Figure 15 This is a block diagram of an example UWB device 1500 according to some aspects of this disclosure. The UWB device 1500 may be capable of operating in any configuration presented herein. For example, the UWB device 1500 may represent at least Figure 6 , 9 One or more of the devices in 12. In this embodiment, UWB device 1500 includes a receiving antenna 1502, a transmitting antenna 1510, a transceiver 1508, a processor 1504, and a memory 1506. In some embodiments, transceiver 1508 is configured to transmit via transmitting antenna 1510 and to receive via receiving antenna 1502. In some embodiments, 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 about occupied time slots and time slot allocation information. Processor 1504 may be used to convert received information into other formats. In some embodiments, other formats may also be stored in memory 1506. In some embodiments, the processor may be configured to implement the functionality of a DT tag, HUS controller, HUS controlled party, auxiliary controller, and / or auxiliary controlled party. In some embodiments, memory 1506 may be a non-transitory computer-readable medium for storing programming instructions and other computer code for performing the various steps described herein. For example, memory 1506 may contain instructions for causing processor 1504 to perform... Figure 14 The steps and / or enabling the UWB device 1500 to implement DT tag, HUS controller, HUS controlled party, auxiliary controller and / or auxiliary controlled party codes.

[0069] In some embodiments, transceiver 1508 may be implemented using a combination of separate transmitter and receiver circuitry (e.g., analog circuitry) connected to other circuitry (e.g., processor 1504 or other circuitry) to perform baseband processing. In other embodiments, a single antenna may be used for both transmission and reception. In other embodiments, UWB device 1500 may include more than two antennas, and the selection of which antennas are used for transmission and which for reception can be dynamically controlled by processor 1504. In such embodiments, using multiple antennas can provide multiple snapshots of the received signal, which can then be combined by the processor to obtain a better overall signal.

[0070] Transceiver 1508 can implement UWB communication capabilities, such as transmitting and / or receiving UWB packets (whether DL-TDoA packets or messages, or HUS session packets or messages), for example regarding... Figure 1 , 2 As described in sections 8, 11, and 13. The communication device 1500 may represent a smartphone or other device that also implements Bluetooth, Wi-Fi, cellular, and / or other communication capabilities, for example, through one or more chips or processors that implement these capabilities. The transceiver 1508 may be implemented as an integrated circuit or chip.

[0071] Memory 1506 may include one or more non-transitory storage devices, which may include locally and / or network-accessible storage devices, disks, drive arrays, optical storage devices, solid-state storage devices (such as random access memory (“RAM” and / or read-only memory (“ROM”)), programmable ROM, flash-updateable ROM, etc. Such storage devices can be configured to implement any suitable data storage, including (but not limited to) various file systems, database structures, etc. Memory 1506 can be used to store programming instructions and other computer code for performing the various steps described herein.

[0072] Those skilled in the art will recognize that the apparatus, systems, and methods described above can be modified in various ways. Therefore, those skilled in the art will understand that the embodiments covered by this disclosure are not limited to the specific exemplary embodiments described above. In this regard, although illustrative embodiments have been shown and described, a wide range of modifications, alterations, and substitutions are disclosed in the foregoing with full consideration. It should be understood that such modifications may be made above without departing from the scope of this disclosure. Therefore, the appended claims should be interpreted broadly and in a manner consistent with this disclosure.

Claims

1. A method performed by an ultra-wideband (UWB) device, the method comprising: Participate in establishing a HUS session associated with a Hybrid UWB Scheduling (HUS) secondary session; Listen for DL-TDoA messages during a ranging block in a downlink time difference of arrival (DL-TDoA) session, wherein the ranging block includes a first time block and a second time block; At least one DL-TDoA message is detected during the first time block of the ranging block, wherein no DL-TDoA message is detected during the second time block of the ranging block; and Based on the detection, a second time block in the second ranging block of the DL-TDoA session is assigned to the HUS auxiliary session, wherein the second ranging block has the same structure as the ranging block, and the second ranging block contains a corresponding first time block and a 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 controlled party, the message indicating that the second time block of the second ranging block can be used for the HUS auxiliary session.

3. The method according to 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, each of the plurality of time periods including 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 message is 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 controlled party, and wherein the method further comprises: A first message is transmitted to the HUS controller, the first message indicating that the first time block of the ranging block is occupied; as well as In response to the first message, a second message is received from the HUS controller, the second message allocating the second time block of the second ranging block for HUS communication. The UWB device uses the HUS auxiliary session to transmit HUS messages during the second time block of the second ranging block.

6. The method of claim 1, wherein each of the time blocks includes 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 message.

8. The method of claim 1, wherein the UWB device is configured as a secondary HUS controlled party in the secondary HUS session, and wherein the method further comprises: Receive a data message indicating the allocation of time slots for data transmission by the HUS controlled party; The second data message is transmitted using the time slot allocation, wherein the data message indicates that the second time block for the second ranging block of the HUS secondary session is available; Receive a third data message instructing the HUS controlled party to use the second time block of the second ranging block for data transmission; and The second time block of the second ranging block is used for the HUS auxiliary session.

9. The method according to claim 8, wherein the data message and the third data message are data transmission phase control messages (DTPCM).

10. An ultra-wideband (UWB) device, comprising: UWB transceiver; as well as The processor is configured as follows: Establish a HUS session associated with a Hybrid UWB Scheduling (HUS) secondary session; During the ranging block in a downlink time difference of arrival (DL-TDoA) session, the UWB transceiver listens for DL-TDoA messages, wherein the ranging block includes a first time block and a second time block. At least one DL-TDoA message is detected during the first time block of the ranging block, wherein no DL-TDoA message is detected during the second time block of the ranging block; and Based on the detection, a second time block in the second ranging block of the DL-TDoA session is assigned to the HUS auxiliary session, wherein the second ranging block has the same structure as the ranging block, and the second ranging block contains a corresponding first time block and a 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 controlled party, the message indicating that the second time block of the second ranging block can be used for the HUS auxiliary 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, each of the plurality of time periods including 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 message is 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 controlled party, and wherein the UWB transceiver is configured to: Transmit a first message to the HUS controller, the first message indicating that the first time block of the ranging block is occupied; and In response to the first message, a second message is received from the HUS controller, the second message allocating the second time block of the second ranging block for HUS communication. The processor is configured to use the HUS secondary session to transmit HUS messages during the second time block of the second ranging block.

15. The UWB device of claim 10, wherein each of the time blocks includes 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 controlled party in the secondary HUS session, wherein the UWB transceiver is configured to: Receive a data message indicating the allocation of time slots for data transmission by the HUS controlled party; The second data message is transmitted using the time slot allocation, wherein the data message indicates that the second time block for the second ranging block of the HUS secondary session is available; and Receive a third data message instructing the HUS controlled party to use the second time block of the second ranging block for data transmission; and The processor is further configured to: The second time block of the second ranging block is used for the HUS auxiliary session.

17. A non-transitory computer-readable medium (CRM) having program code recorded thereon, the program code comprising: Code used to enable ultra-wideband (UWB) devices to participate in the establishment of HUS sessions associated with Hybrid UWB Scheduling (HUS) secondary sessions; Code for enabling the UWB device to listen for DL-TDoA messages during a ranging block in a downlink time difference of arrival (DL-TDoA) session, wherein the ranging block includes 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 of the ranging block, wherein no DL-TDoA message is detected during the second time block of the ranging block; and Code for enabling the UWB device to allocate a second time block in the second ranging block of the DL-TDoA session to the HUS auxiliary session based on the detection, wherein the second ranging block has the same structure as the ranging block, and the second ranging block includes a corresponding first time block and a 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 used to enable the UWB device to transmit a message to the HUS controlled party, the message indicating that the second time block of the second ranging block can be used for the HUS auxiliary session.

19. The non-transitory CRM of claim 17, wherein the UWB device is configured as a HUS controlled party, and wherein the non-transitory CRM further comprises: Code used to enable the UWB device to transmit a first message to the HUS controller, the first message indicating that the first time block of the second ranging block is occupied; as well as Code used to cause the UWB device to receive a second message from the HUS controller in response to the first message, the second message being the second time block for allocating the second ranging block for HUS communication. The UWB device is configured to transmit HUS messages using the HUS secondary session during the second time block of the second ranging block.

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

Images