Methods, apparatus, computer-readable storage medium, and devices for communication

Abstract

The present disclosure relates to signaling techniques using fragmented and multi-partitioned UWB packets. Techniques are provided for utilizing a mix of ultra-wideband (UWB) and narrowband (NB) signaling to provide more efficient operating range and operating efficiency. In one example, a first device can transmit a first packet to a second device via a NB signal, whereby the first packet includes information indicating to the second device a time period for receiving a second UWB packet. In this example, the second packet can include a first partition and a second partition, whereby the first partition includes a first plurality of fragments and the second partition includes a second plurality of fragments. Respective fragments of each plurality of fragments can be transmitted via a UWB signal. The first device can then transmit the first plurality of fragments and subsequently transmit the second plurality of fragments to the second device, the first and second pluralities of fragments being respectively associated with different fragment types.

Description

[0001] Cross Reference to Related Applications

[0002] This application claims priority under 35 U.S.C. § 119(e) to U.S. Provisional Application No. 63 / 108,862, filed November 2, 2020, entitled “TECHNIQUES FOR HYBRIDIZED ULTRA-WIDEBAND AND NARROWBAND SIGNALING,” and U.S. Provisional Application No. 63 / 229,482, filed August 4, 2021, entitled “SIGNALING TECHNIQUES USING FRAGMENTED AND MULTI-PARTITIONED UWB PACKETS.” This application is also related to U.S. Patent Application No. 17 / 453,164, filed November 1, 2021, entitled “SEQUENCES FOR ULTRA-WIDEBAND RANGING” (which claims priority to U.S. Provisional Application No. 63 / 233,109, filed August 13, 2021, entitled “SEQUENCES FOR ULTRA-WIDEBAND RANGING”), and U.S. Patent Application No. 17 / 453,163, filed November 1, 2021, entitled “ANNOUNCING UWB / NBA-UWB-MMS RANGING ROUNDS VIA NARROWBAND BASED ADVERTISEMENTS” (which claims priority to U.S. Provisional Application No. 63 / 233,598, filed August 16, 2021, entitled “ANNOUNCING UWB / NBA-UWB-MMS RANGING ROUNDS VIA NARROWBAND BASED ADVERTISEMENTS”), the contents of all of which are incorporated by reference herein. BACKGROUND

[0003] Wireless devices can employ short-range wireless applications for many different tasks. For example, a wireless device (e.g., a key fob) can be configured such that when the device enters within a certain proximity of a vehicle (e.g., a car), the device automatically unlocks the door of the vehicle. In many cases, regulatory rules and / or other technical limitations can constrain the use of particular types of wireless signaling. These regulatory rules and / or technical limitations can vary between different types of wireless signaling. For example, regulatory rules governing ultra-wideband (UWB) signaling can differ from rules governing narrowband (NB) signaling, at least in part because they can utilize different frequency bands. In some cases, these conventional rules and / or technical limitations make it difficult for systems to achieve a desired range of operation and / or a desired efficiency of operation. Attached Figure Description

[0004] Figure 1 This is a simplified block diagram of an exemplary device equipped with UWB according to some implementation schemes.

[0005] Figure 2 This is another simplified block diagram illustrating exemplary techniques for exchanging wireless messages between devices equipped with UWB, according to some implementation schemes.

[0006] Figure 3 This is another simplified block diagram illustrating at least some exemplary techniques for calculating the channel impulse response (CIR) according to some implementation schemes.

[0007] Figure 4 This is another simplified block diagram illustrating at least some exemplary techniques for formatting UWB packets according to some implementation schemes.

[0008] Figure 5 This is another simplified block diagram illustrating at least some exemplary techniques for determining Time of Flight (TOF) according to some implementation schemes.

[0009] Figure 6 This is another simplified diagram illustrating an example of power spectral density associated with a measurement of a UWB signal, according to one embodiment.

[0010] Figure 7 This is another simplified block diagram illustrating at least some exemplary techniques for transmitting data fragments within a UWB framework, according to some implementation schemes.

[0011] Figure 8 This is another simplified block diagram illustrating at least some exemplary techniques for transmitting data fragments associated with UWB packet types, according to some implementation schemes.

[0012] Figure 9 This is another simplified block diagram illustrating at least some exemplary techniques for transmitting data fragments over multiple time intervals within a UWB framework, according to some implementation schemes.

[0013] Figure 10 This is another simplified diagram illustrating the potential advantages and disadvantages of at least some wireless systems utilizing UWB signaling and / or NB signaling, based on some implementation schemes.

[0014] Figure 11 This is another simplified block diagram illustrating at least some exemplary techniques for utilizing a mixture of UWB signaling and NB signaling, according to some implementation schemes.

[0015] Figure 12is another simplified block diagram illustrating at least some exemplary techniques for utilizing a mix of UWB signaling and NB signaling, in accordance with some embodiments.

[0016] Figure 13 is another simplified block diagram illustrating at least some exemplary techniques for utilizing NB signaling via a NB packet format, in accordance with some embodiments.

[0017] Figure 14 is another simplified block diagram illustrating two devices configured to communicate with each other utilizing a mix of UWB signaling and NB signaling, respectively, in accordance with some embodiments.

[0018] Figure 15 is another simplified block diagram illustrating a hybrid wireless transceiver of a device configured to communicate with another device utilizing a mix of UWB signaling and NB signaling, in accordance with some embodiments.

[0019] Figure 16 is a simplified flow diagram illustrating a signal exchange between two devices, in accordance with some embodiments.

[0020] Figure 17 is another simplified flow diagram illustrating a signal exchange between two devices, in accordance with some embodiments.

[0021] Figure 18 is another simplified flow diagram illustrating an exemplary process by an initiator device, in accordance with some embodiments.

[0022] Figure 19 is another simplified flow diagram illustrating an exemplary process by a responder device, in accordance with some embodiments.

[0023] Figure 20 is another simplified block diagram illustrating the transmission of UWB payload data utilizing NB signaling, in accordance with some embodiments.

[0024] Figure 21 is another simplified block diagram illustrating an exemplary waveform that can be included in one or more segments transmitted by a UWB signaling layer of a device, in accordance with some embodiments.

[0025] Figure 22 is another simplified block diagram illustrating a first portion of an exemplary process by a device for hybrid signaling, in accordance with some embodiments.

[0026] Figure 23 is another simplified block diagram illustrating a remaining portion of an exemplary process of Figure 22 , in accordance with some embodiments.

[0027] Figure 24is another simplified flow diagram illustrating signal transmission utilizing one or more NB channels according to a two-way redundant packet-switched protocol, according to some embodiments.

[0028] Figure 25 is another simplified flow diagram illustrating message exchange between two devices utilizing one or more NB channels according to a two-way redundant packet-switched protocol, according to some embodiments.

[0029] Figure 26 is another simplified flow diagram illustrating signal transmission utilizing one or more NB channels according to a one-way redundant packet transmission protocol, according to some embodiments.

[0030] Figure 27 is another simplified flow diagram illustrating message exchange between two devices utilizing one or more NB channels according to a one-way redundant packet transmission protocol, according to some embodiments.

[0031] Figure 28 is another simplified flow diagram illustrating signal transmission utilizing a non-interleaved ranging protocol with a known fixed turnaround time, according to some embodiments.

[0032] Figure 29 is another simplified flow diagram illustrating message exchange based on a known fixed turnaround time, according to some embodiments.

[0033] Figure 30 is another simplified flow diagram illustrating a non-interleaved ranging protocol including NB signal exchange of round trip times and / or turnaround times after two-way exchange of UWB fragments, according to some embodiments.

[0034] Figure 31 is another simplified flow diagram illustrating message exchange utilizing NB signal exchange after two-way exchange of UWB fragments, according to some embodiments.

[0035] Figure 32 is another simplified flow diagram illustrating signal exchange according to a one-way NB and non-interleaved UWB ranging protocol, according to some embodiments.

[0036] Figure 33 is another simplified flow diagram illustrating message exchange according to a one-way NB and non-interleaved UWB ranging protocol, according to some embodiments.

[0037] Figure 34 is another simplified flow diagram illustrating signal exchange according to a beacon protocol, according to some embodiments.

[0038] Figure 35 is another simplified flow diagram illustrating message exchange according to a beacon protocol, according to some embodiments.

[0039] Figure 36 This is another simplified flowchart illustrating signal exchange according to an interleaved ranging protocol, based on some implementation schemes.

[0040] Figure 37 This is another simplified flowchart illustrating message exchange according to the interleaved ranging protocol, based on some implementation schemes.

[0041] Figure 38 This is another simplified block diagram illustrating the use of a separate wireless system for initial device discovery and connection setup, based on some implementation schemes.

[0042] Figure 39 This is another simplified block diagram illustrating the use of a separate wireless system for initial device discovery and connection setup, based on some implementation schemes.

[0043] Figure 40 This is a simplified block diagram illustrating the use of fragmented UWB signaling, including UWB packets, across multiple partitions according to some implementation schemes.

[0044] Figure 41 This is another simplified block diagram illustrating the use of fragmented UWB signaling across multiple partitions, including UWB packets, according to some implementation schemes.

[0045] Figure 42 This is another simplified block diagram illustrating the use of fragmented UWB signaling across multiple partitions, including UWB packets, according to some implementation schemes.

[0046] Figure 43 This is a simplified flowchart illustrating the use of fragmented UWB signaling, including UWB packets, across multiple partitions according to some implementation schemes.

[0047] Figure 44 This is another simplified block diagram illustrating the technology by which an asymmetric number of segments are transmitted between two directions of a link, according to some implementation schemes.

[0048] Figure 45 This is another simplified block diagram illustrating, according to some implementation schemes, the technology by which multiple UWB frequency channels can be used for fragmented transmission.

[0049] Figure 46 This is another simplified block diagram illustrating a technique for performing antenna switching to facilitate UWB fragmented transmission, based on some implementation schemes.

[0050] Figure 47 This is a simplified block diagram illustrating techniques for operating a hybrid (UWB / NB) system in an environment including anchor stations and client stations, based on some implementation schemes.

[0051] Figure 48 is another simplified block diagram illustrating techniques for performing environmental sensing via UWB fragmentation transmission, in accordance with some embodiments. DETAILED DESCRIPTION

[0052] In the following description, various examples will be described. For the purpose of explanation, specific configurations and details are set forth in order to provide a thorough understanding of the examples. However, it will also be apparent to one skilled in the art that the examples can be practiced without these specific details. Furthermore, well-known features can be omitted or simplified in order not to obscure the examples being described herein.

[0053] Embodiments of the present disclosure can provide techniques for utilizing a mix of ultra-wideband (UWB) and narrowband (NB) signaling when performing wireless communications between devices to provide improved operating ranges and / or operating efficiencies. For example, the techniques disclosed herein can enable a first device to efficiently determine a positioning (location) of a second device relative to the first device and / or to efficiently determine a distance estimate (e.g., a range estimate value) between the two devices. To illustrate, consider an example in which a first device and a second device are capable of wirelessly communicating. In this example, mixed signaling can be performed in accordance with a ranging protocol involving bidirectional NB and UWB signaling between the first device and the second device. The two devices can first perform an initial phase during which there can be initial device discovery and initial (e.g., “coarse”) synchronization between the two devices. In some examples, this initial phase can be performed by, for example, a wireless system of each device, which is equipped to transmit wireless signals using Bluetooth Low Energy (BLE). During this initial phase, the wireless system of the first device can schedule a start time (e.g., a discrete time instant) for transmission of at least one packet (e.g., an “NB poll” packet) to the second device via a NB signal. The first device can also schedule a window (e.g., a time interval) for subsequent reception of a second packet (e.g., an “NB response” packet transmitted via another NB signal) from the second device by the first device.

[0054] After this initial phase, the first device can then transmit a scheduled NB poll packet to the second device via a NB signal at the scheduled start time, where the packet can convey (e.g., indicate) one or more types of synchronization data for a second (e.g., "fine") synchronization between the two devices. For example, the packet can include a synchronization ("sync") field and a data payload field. The data payload field can include scheduling data (e.g., which can also be referred to as "scheduling information"). The second device can extract one type of synchronization data from the sync field corresponding to time and frequency synchronization information (e.g., T / Fsync information) by using prior art synchronization and / or signal acquisition techniques. The second device can also extract another type of synchronization data from the data payload field corresponding to scheduling data by using prior art demodulation and decoding techniques. The second device can use this synchronization data to schedule and facilitate reception of a plurality of data segments that will be subsequently transmitted by the first device to the second device via UWB signals in the form of short bursts and distributed over multiple intervals. In this example, the scheduling data of the NB poll can also include scheduling information related to a NB response packet transmission start time, enabling the second device to schedule transmission of a NB response packet to the first device at the NB response start time. The second device can then transmit the NB response packet at the required start time, where the NB response packet conveys second synchronization data, similar as described above with respect to synchronization data from the first device to the second device. The first device can use this second synchronization data to schedule and facilitate reception of a second plurality of segments that can be subsequently transmitted by the second device to the first device via UWB signals distributed over multiple intervals. In this way, the NB signaling layer of each device can facilitate the respective UWB signaling layer in terms of synchronization and other functions. Note that the facilitation of reception of UWB signals from the synchronization data conveyed via the NB signals can include configuring the UWB reception in terms of carrier frequency offset and sample frequency offset with respect to the respective associated (second or first) device.

[0055] The first device can then schedule and transmit the plurality of UWB segments to the second device for reception at the second device in accordance with synchronization data previously obtained by the second device from the first device. In this example, the plurality of UWB data segments can collectively represent a channel impulse response training sequence (CIRTS) of a UWB formatted packet. Upon receiving the CIRTS from the first device (e.g., by aggregating the segments), the second device can use the CIRTS to estimate a channel impulse response (CIR) and / or determine other synchronization information (e.g., time and frequency information, scheduling data, etc.). After a turnaround time interval (which, in this example, can be a fixed time interval known to the first device), the second device can then schedule and transmit a second plurality of UWB segments to the first device for reception at the first device in accordance with second synchronization data previously obtained by the first device from the NB transmission of the second device. The first device can then similarly compute a CIR estimate and / or obtain other synchronization information. Thereafter, with the computed CIR information and taking into account (e.g., subtracting) the turnaround time, the first device can determine a time of flight (TOF) associated with a line of sight (LOS) path between the two devices. Thus, the first device can then be able to determine a range and / or location of the first device relative to the second device. In this way, by utilizing a hybrid of NB and UWB signaling, implementations improve operational range and / or efficiency when performing ranging and / or positioning via UWB signaling.

[0056] To further illustrate, consider a scenario in which a first device (e.g., an “initiator” device) and a second device (e.g., a “responder” device) each include a hybrid wireless system (e.g., a hybrid wireless transceiver). Using the first device as a representative example device, the hybrid wireless system of the first device can include an ultra-wideband subsystem and a narrowband subsystem. Each subsystem can include wireless transmission and reception circuitry and functionality for NB and UWB signaling. Additionally, the two subsystems can be tightly coupled together. For example, the hybrid wireless transceiver can include a shared time base unit, such as including a crystal oscillator (XO) and / or clocking and timing device. The shared time base unit can ensure that the NB and UWB subsystems generate signals that are tightly synchronized in time and frequency. The subsystems for a given device can also share medium access control (MAC) functionality. The MAC functionality can utilize a common time base (e.g., based on the shared time base unit) to coordinate between the subsystems on a given device. Additionally, radio and physical layer (PHY) functionality can also operate based on the common time base between the subsystems.

[0057] Additionally, the hybrid wireless transceiver can include a hybrid system controller. The hybrid system controller can coordinate transmission and reception activities of both the NB and UWB subsystems, as well as information exchange between the NB and UWB subsystems. For example, the hybrid system controller can receive time and frequency synchronization information from the NB subsystem. In some embodiments, the hybrid system controller can also receive payload data information from the NB subsystem. The hybrid system controller can also schedule data transmission and reception by the NB subsystem. The hybrid system controller can also provide time and frequency configuration information to the UWB subsystem. This can enable the UWB subsystem receiver to more accurately configure (e.g., synchronize) based on the time and frequency information extracted from the NB signaling. Since the time base unit is shared between the NB and UWB subsystems (including any frequency offset with respect to the associated device), this configuration information helps tailor UWB reception for incoming UWB signals (e.g., corresponding to CIRTS segments), improving receiver efficiency as well as performance of CIR estimation. The hybrid system controller can also use data received from the NB signal to schedule UWB transmission or reception activities based on certain transmission / reception parameters (e.g., carrier frequency, UWB bandwidth, etc.). In turn, the hybrid system controller can also receive UWB reception information, including synchronization data (e.g., time and frequency configuration information) and CIR information. Although embodiments described herein can refer to separate components of the hybrid wireless transceiver as performing particular operations, embodiments should not be interpreted as being so limited. For example, the hybrid system controller can reside within one of the subsystems described herein (e.g., NB or UWB). Any suitable division of operations between one or more software and / or hardware components can be suitable for performing embodiments described herein.

[0058] Continuing with the above-described explanation, consider a scenario in which the first device and the second device engage in a bidirectional exchange of data (e.g., CIRTS fragments) between the two devices. As described herein, the two devices can perform a“coarse” initial synchronization. In one example, in a case in which the first device operates as an“initiator” device and the second device operates as a“responder” device, the first device can schedule a start time (e.g., a discrete time) for transmission of a packet to the second device via an NB signal that conveys synchronization data (e.g., including time and frequency synchronization information). The second device can also schedule a window for reception of the packet from the first device via the NB signal accordingly. It should be understood that, in some embodiments, a time can be associated with a particular start time (e.g., a discrete time instant). In some embodiments, a time can be associated with a time interval (e.g., a window and / or a time slot), depending on the context. In some embodiments, the information of the data exchanged during the initial phase can enable the two devices to align (e.g., clock synchronization) within about a required time increment (e.g., a 1 millisecond (ms) increment) between the clocking devices of the two devices (e.g., managed by respective shared time base units). In some embodiments, the initial phase can also be used to perform initial device discovery and other connection setup operations. In some embodiments, this initial phase can be performed on each device by a separate wireless system from the hybrid wireless transceiver. For example, the separate wireless system can utilize a Bluetooth Low Energy (BLE) protocol and / or reside on a separate System on a Chip (SOC) device from the hybrid wireless transceiver. In some embodiments, the initial phase including operations such as service advertisement / discovery, connection setup, or coarse synchronization can be performed by the same system that performs the operations of the hybrid wireless transceiver described herein, in some embodiments particularly by the NB subsystem.

[0059] At the time the initial phase is complete, the first (initiator) device can transmit the packet to the second device via the NB signal at the scheduled start time. As described herein, the NB packet can include data that conveys synchronization data to the second device. For example, the packet can include data such as a preamble, a frame start delimiter, and / or other synchronization fields. In some embodiments, the second device can use the packet data to extract synchronization data (e.g., from the sync fields of the packet) corresponding to, for example, time and / or frequency synchronization information. In some embodiments, the packet data can be used to extract other synchronization data (e.g., from the payload data of the packet) corresponding to, for example, scheduling information. In one example, the frequency synchronization information can correspond to a relative carrier frequency (which can also be referred to as "F sync" information) that can be used to shift synchronization of the crystal oscillators (XOs) of the two devices described further herein. In some examples, the F sync information can be used to configure a UWB receiver of one device to optimize its frequency correction circuitry in preparation for receiving UWB signals from the other device. In some examples, the devices can use the time synchronization information (which can also be referred to as "T sync" information) to "anchor" subsequent UWB exchanges according to the timing arrangements of the devices described further herein. In some embodiments, the time and / or frequency information can be extracted based at least in part on detecting a pattern (e.g., an expected signal pattern associated with the synchronization header of the packet). As described herein, in some embodiments, the synchronization data can also correspond to scheduling information extracted from the packet payload data. The scheduling information can be used, in one example, to schedule the reception of subsequent UWB packet (e.g., and / or fragment) transmissions by a device (e.g., the second device) from another device (e.g., the first device). It should be appreciated that the packet payload data can also include other types of information (e.g., non-synchronization data such as status information, control information, etc.).

[0060] It should be appreciated that different types of synchronization data can be included in transmissions between devices depending on the context. In one non-limiting example, a first device (e.g., operating as an initiator device) can transmit data that conveys (e.g., indicates and / or enables extraction of) both time and frequency synchronization information as well as scheduling information. In this example, a second device can subsequently transmit data to the first device that conveys only time and / or frequency information. In another example, the data transmitted to the first device can also include scheduling information. In yet another example, the data included within the NB packet can convey not only scheduling information for scheduling a NB response packet to another device (e.g., a second (responder) device), but can also convey scheduling information for scheduling a subsequent UWB response transmission by the second device.

[0061] Continuing with the above description, the second device can then obtain and evaluate the synchronization data from the packet. The second device can use the synchronization data to schedule the subsequent reception of the plurality of segments received from the first device via the respective UWB signals. As described herein, the packet can also include scheduling data that the second device uses to schedule a second start time for transmitting a second packet to the first device via a second NB signal. Accordingly, the first device can also schedule a time (e.g., and / or a time window) for receiving the second packet, which is then transmitted from the second device to the first device at the second start time. The second device can then transmit the second packet to the first device via the second NB signal at the second start time. Upon receiving the second packet during the scheduled window, the first device can obtain (e.g., extract) second synchronization data from the second packet. The first device can then utilize the second synchronization data extracted from the second packet to schedule and facilitate the reception of a second plurality of segments to be received from the second device.

[0062] Turning to the transmission and reception of UWB segments by each device, the first device can schedule the transmission of the plurality of segments to the second device. The scheduling of the transmission of the plurality of segments can be in accordance with the synchronization data communicated by the first device to the second device via the NB signal. The first device can then transmit the plurality of segments to the second device. As described further herein, each segment of the plurality of segments can be separated in time from other segments of the plurality of segments by at least a predefined time interval (e.g., 1 ms). In one example, the plurality of segments can collectively correspond to (e.g., represent) a CIRTS, which can be operable to compute a CIR estimate associated with a wireless propagation path between the first device and the second device. It should be appreciated that because the CIRTS can be divided into a plurality of segments (e.g., rather than transmitted within a single segment as part of a continuous UWB signal transmission), the total amount of energy that can be emitted by the first device for the segmented UWB transmission can be higher than the energy of a single UWB transmission when following certain regional regulatory constraints that govern the emission of energy in a given region. Additionally, the operational range for the overall UWB transmission can be greater than would otherwise be possible if the CIRTS were transmitted as a single data segment or a single UWB packet. This can be due in part to enabling the device to aggregate energy from multiple segments. In some embodiments, as described further herein, the plurality of segments can correspond to a particular type of sequence of segments (e.g., a pseudo-random sequence (STS), a periodic sequence, a Golay sequence). It is also noted that limiting UWB to a single segment (rather than multiple segments) representing a CIRTS is already beneficial because in a regular UWB transmission, the emission energy available needs to be shared between the SHR (Sync Header) and the CIRTS, whereas in the hybrid system, the functionality of the SHR is at least partially delegated to the NB system, thereby alleviating the burden of the UWB system to perform various synchronization tasks.

[0063] While the first device transmits the plurality of fragments via UWB signals, the second device can receive each fragment and then subsequently obtain aggregated information from the plurality of fragments. For example, the second device can compute an estimated CIR based on the CIRTS represented within the plurality of fragments. In some embodiments, the second device can also obtain other data (e.g., synchronization data, scheduling data, etc.) from the plurality of fragments. Similar to the first device, the second device can then schedule transmission of a second plurality of fragments. The transmission of the second plurality of fragments (e.g., UWB fragments) can be scheduled in accordance with second synchronization data previously obtained by the first device from the second device (e.g., extracted based on sync header information of a second packet transmitted by the second device to the first device via a second NB signal). In some embodiments, the scheduling can also (and / or alternatively) be based on synchronization data obtained from one or more of the plurality of fragments received from the first device. The second device can then transmit the second plurality of fragments to the first device, similar as described above with respect to the plurality of fragments transmitted from the first device to the second device. Upon receiving the second plurality of fragments, the first device can compute an estimated CIR based on the CIRTS represented by the second plurality of fragments. In some embodiments, the first device can also obtain synchronization data or other suitable data from the second plurality of fragments.

[0064] When the first device computes an estimated CIR based on the second plurality of segments, the first device can be further capable of computing a time-of-flight interval based in part on the CIR estimate. For example, the first device can determine a round-trip time interval that corresponds to a time increment between a first time that the plurality of segments (e.g., a first segment of the plurality of segments) is transmitted to the second device and a second time that the second plurality of segments (e.g., a last segment of the second plurality of segments) is received by the first device from the second device. The first device can also determine a turnaround time interval that corresponds to a second time increment between a third time that the plurality of segments is received by the second device from the first device and a fourth time that the second plurality of segments is transmitted by the second device to the first device. The first device can then subtract the turnaround time interval at the second device from the round-trip time interval to help determine a time-of-flight (TOF). In some embodiments, the TOF can represent a distance (e.g., traveled by a respective signal that traverses a line-of-sight (LOS) path between the two devices) divided by the speed of light, which can be used to estimate a distance from the TOF. In some embodiments, the turnaround time interval can be a fixed time interval that is known (e.g., in advance) by the first device (and / or the second device). In some embodiments, the second device can subsequently communicate relevant information (e.g., timestamp information via another NB signal) to the first device that can be used to determine the turnaround time at the second device and determine the TOF based thereon. Based on determining the TOF between the two devices, the first device can determine a range and / or relative positioning information between the two devices. In some embodiments, only the first device can decide to compute the range / positioning information. In some embodiments, both the first device and the second device can decide to compute the range / positioning information. For example, the second device can similarly receive information from the first device via a NB signal that enables it to compute or utilize the turnaround time interval at the first device and subsequently compute the TOF / range information between the two devices. In some embodiments, if the second device needs to know the TOF, the second device can also obtain the TOF result computed by the first device as payload data NB transmission.

[0065] In some embodiments, the exchange of one or more signals (e.g., NB signals and / or UWB signals) can be in accordance with one or more protocols. The use of a particular protocol can depend on, for example, the context and / or intended use for performing the signal exchange. For example, one protocol can correspond to a bidirectional exchange of NB signals (e.g., packets) and can include joint utilization of redundant and / or repeated NB packet exchanges with a pseudo-random channel hopping sequence. This can improve reliability against interference and / or multipath fading phenomena when performing NB signaling to help coordinate UWB signaling. In some embodiments of this protocol, NB control information (which can correspond to what channels to use and / or how many hopping channels to use) can be predefined during connection setup (e.g., during an initial phase, as described herein) or exchanged via an out-of-band system (e.g., Bluetooth, BLE, etc.). In another example of a protocol, a unidirectional NB exchange (including redundant transmissions with channel hopping) can be used. This can be used, for example, to perform a unidirectional exchange of UWB fragments in conjunction with a beaconing protocol (e.g., to transmit multiple fragments from a first device to a second device, but not the other way around). For example, in one beaconing protocol, the second (receiver) device can be one of several devices (e.g., anchor devices) that interact with the first (initiator) device according to the beaconing protocol. In one example, the second device subsequently performs ranging and / or positioning based on triangulation with one or more other devices, in part based on an estimated CIR.

[0066] In some embodiments, a protocol can be utilized, by which a first device (e.g., an initiator device) can determine a time-of-flight interval and / or range based on a fixed turnaround time interval known to the initiator device, as described herein. In some embodiments, after the first device receives multiple fragments from a responder device, the second device (e.g., the responder device) can transmit a turnaround time interval (e.g., including a timestamp and / or status information) to the initiator device via a NB signal.

[0067] In some embodiments, a protocol can be utilized, by which a unidirectional NB exchange is followed by a UWB fragment in the same direction. This can allow multiple responders to participate in a ranging activity by having them respond in a known sequence or in a random order. In yet another example of a protocol, a staggered ranging protocol can be utilized, by which an initiator device and a responder device can utilize the same predetermined time interval to transmit individual fragments. In this example, rather than having the initiator device transmit multiple fragments to the responder device, followed by the responder device transmitting a second plurality of packets to the initiator device, the fragments within the respective plurality of fragments can be staggered. This can reduce the total time for performing ranging between the two devices.

[0068] In some embodiments, a UWB signaling protocol can be utilized whereby a UWB packet can be partitioned to include at least a first partition and a second partition. In some embodiments, each partition can be associated with a different type of UWB fragment (e.g., CIRTS, pseudo-random training sequence (PRTS), data payload, etc.). By enabling a UWB packet to be partitioned to transmit different types of fragments, additional use cases can be implemented (e.g., in addition to performing ranging between two devices). In one example, a first device transmits a first packet to a second device via a NB signal, whereby the first packet includes data indicating to the second device a time period for receiving a second packet (e.g., a UWB packet). In this example, the second packet can be formatted to include a first partition including a first plurality of fragments (e.g., CIRTS type fragments) and a second partition including a second plurality of fragments (e.g., PRTS type fragments). The first device can then transmit the first plurality of fragments of the second packet via a UWB signal, respectively. The first device can then transmit the second plurality of fragments of the second packet via a UWB signal, respectively. In this example, the second device can be enabled to not only compute a CIR estimate and perform a propagation path extraction (e.g., based on the first plurality of fragments) but can also be able to authenticate the first propagation path extraction based in part on the second plurality of fragments (e.g., because a particular PRTS sequence can only be shared between the first device and the second device). In some embodiments, other use cases can also be enabled, such as including audio and / or data payloads within a UWB packet (e.g., in addition to a plurality of CIRTS fragments also included within the packet).

[0069] Embodiments of the present disclosure provide several technical advantages over the prior art. In one example, embodiments of the present disclosure enable a hybrid wireless system to perform a hybrid of UWB signaling and NB signaling that includes tight coordination. For example, as described herein, a NB subsystem (e.g., a NB signaling layer) of a hybrid wireless system can be used to assist one or more functions of a UWB subsystem (e.g., a UWB signaling layer). These subsystems can be tightly coupled based on a common (e.g., shared) timing on a given physical device and shared MAC functionality, as described herein. The one or more functions of the NB signaling layer can include, for example, coordinating time and frequency synchronization between UWB signaling layers of respective devices, performing control, management, and / or status signaling between these devices, etc. At the same time, the UWB signaling layer can perform a short burst of radio pulses distributed over a certain time interval (e.g., many milliseconds (MMS)). The burst can represent a segmented UWB transmission (e.g., of channel impulse response training sequences (CIRTS) / scrambled time sequences (STS)).

[0070] In some embodiments, a hybrid wireless system can enable the NB signaling layer to be responsible for communicating synchronization data such as time and frequency synchronization information, for example, via the sync header (SHR) of a regular UWB packet, which can be more efficient than distributing the SHR within multiple SHR fragments via the UWB signaling layer. For example, transmitting multiple SHR fragments without prior knowledge of the arrival time of each fragment can require a large amount of memory for buffering and / or a large amount of processing power. Thus, the amount of memory and / or processing power can be reduced by utilizing the NB signaling layer without utilizing the regular UWB SHR. At the same time, the CIRTS / STS portion of the UWB packet can be fragmented according to the UWB fragmentation protocol. A receiver of the fragmented packet can utilize the synchronization data communicated via the NB signaling so that the receiver can accurately schedule the reception (e.g., arrival time) of subsequently received UWB fragments. By implementing fragmentation of UWB transmissions, embodiments can enable a receiver of the UWB transmissions to achieve higher performance when measuring the propagation channel for extracting geometry and / or positioning metrics such as distance (e.g., range) or angle. For example, a UWB waveform for a given measurement period can be fragmented into short bursts (e.g., fragmented multi-millisecond (MMS) signaling) and distributed within multiple regulatory (e.g., emission) test intervals (e.g., according to regulatory rules of a particular region). A receiver device can utilize energy "coalesced" (e.g., aggregated) from various intervals (e.g., within each short burst), thereby enabling a more accurate CIR estimate. Based in part on the CIR estimate, a time-of-flight, range, position (location), and / or angle-of-arrival (AOA) estimate can be determined. Thus, by utilizing a hybrid wireless system that is capable of tightly coordinated NB and UWB signaling, embodiments achieve at least improved operating range and operating efficiency of UWB-based signaling.

[0071] Figure 1 is a simplified block diagram of an exemplary UWB-equipped device according to some embodiments. In some embodiments, various types of ultra-wideband (UWB) devices can be improved at least in terms of operating range, operating efficiency, and / or other feature enhancements. In some embodiments described herein, UWB transmissions are broken into short bursts of packet fragments distributed within multiple regulatory / emission measurement intervals in order to increase the energy radiated by the UWB transmitter at each transmission.

[0072] One beneficial use case for UWB, due to its large bandwidth (BW) of 500 MHz or more, is the "ranging" use case. In some embodiments, ranging can correspond to an accurate measurement of the time of flight (TOF) of a radio wave between two UWB-equipped devices A and B and an estimate of the distance (e.g., "range") between these devices. This large BW can help resolve dense electromagnetic reflections that can exist in the vicinity of these devices such as in floors, ceilings, walls, furniture, cars, plants, appliances, or other man-made or natural objects in an indoor or outdoor environment. Measuring the ToF / range between devices such as mobile phones, wireless audio speakers, TVs, desktop or laptop computers, home or car door locks, or other consumer devices can facilitate the implementation of novel user experiences.

[0073] Figure 1 and Figure 2 Figures (described further below) illustrate scenarios with UWB-equipped devices. In Figure 1 schematic diagram 100, handheld devices 110 communicate with other handheld devices, fixed devices, or Internet of Things (IoT) devices to measure distance or other positioning metrics such as apparent direction of devices relative to each other. Devices participating in such communications include phones (e.g., mobile devices 120), tags (e.g., pet tags 160), wireless speakers (e.g., wireless speakers 170a, 170b, and 170c), televisions, displays, doors (e.g., door lock devices 140), cars, home appliances (e.g., smart speaker 130), thermostats (e.g., thermostat control devices 150), desktop computers and laptops, tablets, etc.

[0074] Figure 2 is another simplified block diagram 200 illustrating an example technique for exchanging wireless messages between UWB-equipped devices (or "stations") in accordance with some embodiments. Figure 2 schematic diagram 200 illustrates how UWB device A 202 and UWB device B 204 can exchange wireless messages between each other over time in the form of wireless packets 206a-c. In the case of Impulse Radio (IR) UWB, the waveforms exchanged between devices contain a series of UWB pulses shown as pi, p2, p3 in Figure 2 This can represent, for example, a series of pulses transmitted from device B 204 to device A 202 in response to a first set of pulses transmitted from A to B. In some embodiments, IR-UWB can be used to perform the techniques described in this disclosure.

[0075] Figure 3is another simplified block diagram 300 illustrating at least some example techniques for computing a channel impulse response (CIR) in accordance with some embodiments. In some embodiments, in order to enable determination of mutual range or location of devices, a technique used by wireless systems such as UWB is to compute a channel impulse response (CIR) 306. The CIR 306 can represent a profile of the direct and indirect (reflected) wireless propagation paths between two devices, such as station A 302 and station B 304, each path characterized by its propagation delay, magnitude, and radio frequency (RF) phase. Due to the large BW of UWB, the CIR can be computed in UWB at a high resolution level, which in turn enables more accurate extraction of the line-of-sight (LOS) path and thus the TOF / range corresponding to the first path in the CIR.

[0076] For example, as Figure 3 As shown in the diagram 300, a pulse PT 308 is transmitted from station A 302 at time t_A1. In some embodiments, the pulse PT 308 can be viewed as representing a long sequence of pulses in the case of IR-UWB. In this example of the diagram 300, the pulse PT 308 propagates to station B 304 via a series of propagation paths PP1 310a, PP2310b, PP3 310c, and PP4 310d. PP1 310a is a direct line-of-sight path, while PP2 310b, PP3 310c, and PP4 310d are reflections from objects Ob2 312a, Ob3 312b, and Ob4 312c in the environment. The signal that traverses the direct (LOS) path PP1 310a arrives at the receiving station B 304 in the form of a pulse PR1 314a at time t_B1 after an overall delay “TOF” (time of flight) 314, which represents the distance divided by the speed of light. Pulses corresponding to the reflected paths PP2 310b, PP3 310c, and PP4 310d arrive later in the form of PR2314b, PR3314c, and PR4 314d than the direct path, and their arrival times will depend on the distance traveled from station A 302 to station B 304 via one or more reflectors experienced by each path. Note that PR1 314a, PR2314b, PR3314c, and PR4 314d are examples of a channel impulse response (CIR) 306. In some embodiments, the CIR 306 can enable devices to determine a metric such as distance d_AB based on the TOF, which is itself derived from the first arrival path PR1 314a.

[0077] While UWB can also be used for more traditional wireless transmission purposes, such as data payload transmission, the estimation of the CIR 306 for ToF / ranging / positioning is a particular advantage of UWB. In some embodiments, part of the reason for this advantage of UWB can be its large bandwidth of 500 MHz or more.

[0078] In some embodiments, to estimate the CIR 306 (e.g., sometimes referred to as “channel sounding”), a wireless system including UWB uses what is referred to as a “channel impulse response training sequence” (CIRTS). The CIRTS can be a waveform in the link between a transmitter (e.g., device A 202) and a receiver (e.g., device B 204) that is known to both. If the transmitter sends out a waveform containing a specific training sequence 1 (CIRTS1_TX), the wireless propagation channel with its direct and reflected propagation paths can linearly distort the waveform, so that a modified waveform CIRTS1_RX will arrive at the receiver. Since the receiver knows CIRTS1_TX in advance, it can compare the incoming signal CIRTS1_RX with the known sequence CIRTS1_TX. Then, using mathematical algorithms such as correction and other algorithms generally referred to as “channel estimation” in the art, the receiver can extract the CIR between the transmitter at device A 202 and the receiver at device B 204.

[0079] Figure 4 is another simplified block diagram 400 showing at least some example techniques for formatting a UWB packet (e.g., packet 206) in accordance with some embodiments. Figure 2 is another simplified block diagram 400 showing at least some example techniques for formatting a UWB packet (e.g., packet 206) in accordance with some embodiments. Figure 4 An example of one type of UWB packet format is shown with its constituent fields and their respective purposes in accordance with the international standard defined for UWB in IEEE 802.15.4z. The Sync Header (SHR) 402 at the beginning of the packet consists of a Sync (SYNC) preamble 404 and a Start of Frame Delimiter (SFD) 406. The SHR 402 has multiple purposes, including automatic gain control, frequency offset estimation (frequency Sync or F-Sync), timing estimation (T-Sync), initial channel estimation, etc., generally referred to as “acquisition” or “synchronization” (Sync). The SFD 406 terminates the SHR 402 and also participates in coordinating packet timing (e.g., frame timing estimation). The subsequent field shown as CIRTS / STS 408 refers to a Channel Impulse Response Training Sequence, or in the case of 802.15.4z, a Scrambled Timestamp Sequence (STS). The STS refers to a CIRTS containing pseudo-random pulses known only to the transmitter and receiver of a given link to ensure secure channel estimation and secure distance measurement. In some embodiments, the CIRTS / STS 408 can be used for accurate and / or secure channel estimation and / or timestamp verification.Figure 4 Two additional packet fields are shown, namely a PHY header (PHR) 410 and payload data (e.g., a PHY service data unit (PSDU)) 412. The PHR 410 can contain parameters of the PHY header, and the payload can contain suitable data content. Note that other packet types are defined for UWB, e.g., consisting only of the SHR 402 and CIRTS / STS 408 (e.g., a "dataless packet"), which can be used for channel sounding, but without any payload data transmission. There is also a payload-only packet format consisting of the SHR 402 and PHR 410 / payload 412 fields, in which case no precise and / or secure channel sounding is needed, and the main purpose is data transmission.

[0080] Figure 5 is another simplified block diagram 500 showing at least some example techniques for determining time of flight (TOF) according to some embodiments. As Figure 5 depicted in the schematic diagram 500, based on the determination of TOF, the distance between two stations, station A 502 and station B 504 can be determined. In some embodiments, station A 502 transmits a "poll" message (A to B) 506a at time t A1 . The LOS path as determined by station B based on the CIR arrives at t B1 , where the time increment between t A1 and t B1 represents the TOF. After a turnaround time T B,TO at station B, the station transmits a "response" message (B to A 506b) at time t B2 . The LOS path of the response message arrives at time t A2 , such that the TOF is again visible on the schematic diagram 500 in the form of the difference between t A2 and t B2 . By measuring the "round trip" time T A,RT and subtracting the turnaround time T B,TO , station A 502 can calculate the TOF. In some embodiments, the technique shown in the schematic diagram 500 is in the form of a TOF measurement protocol (or "ranging protocol"). In some embodiments, there can be variations involving three or more packets (e.g., packet 206) to improve robustness against real-life radio impairments, such as crystal oscillator (XO) offsets between station A 502 and station B 504. As further described herein, embodiments provide a ranging protocol that utilizes a new mixed wireless system environment.

[0081] Figure 6is another simplified diagram 600 illustrating examples of power spectral density associated with measurements of UWB signals, according to some embodiments. In some embodiments, the techniques described herein can improve scenarios where CIRTS and associated CIR estimation steps at a receiver device are distributed across multiple segments covering multiple regulatory / transmission test intervals, which can increase the radiated energy for transmissions of CIRTS. This distribution can also enable improvements in operating range.

[0082] Using Figure 6 To further illustrate this context, diagram 600 illustrates a power spectral density (PSD) 602 for a regulatory measurement of a UWB signal. While regulatory rules can differ between countries and regulatory regions, in some regions, an example UWB emission limit can require a maximum PSD of -41.3 dB / MHz across the UWB signal bandwidth (e.g., 500 MHz in this example). The PSD 602 illustrated in this example meets this requirement for all spectral components, some of which reach the limit of -41.3 dBm / MHz. In some embodiments, this measurement can be made using an averaging (spectrum analyzer sweep) time of 1 millisecond (1 ms). This means that for this scenario, the maximum amount of energy that a UWB system can emit per ms corresponds to approximately 37 e-9 Joules = 37 nanoJoules (nJ) per 500 MHz bandwidth per ms. This is illustrated by plot 604 near the bottom of diagram 600. The available energy (up to 37 nJ) can be transmitted in the form of shorter (“dense”, D) or longer (“flat”, F) bursts. The power (shown via the y-axis) is correspondingly higher or lower, as energy is calculated as time duration times power. In some embodiments, there can be peak power constraints governed by UWB regulatory rules of different regions. Thus, compression to shorter time durations can work within certain limits and depend on the density of IR pulses.

[0083] Figure 7 is another simplified block diagram 700 illustrating at least some example techniques for transmitting data segments within a UWB framework, according to some embodiments. In some embodiments, regulatory constraints are considered at least in part by defining a segmented UWB framework, as illustrated by diagram 700. Figure 7 of diagram 700.

[0084] In diagram 700, a transmission frame (TXF) 702 is depicted as being divided into multiple segments 704a-c, which are distributed across multiple regulatory test intervals of a time duration T test reg 706. For example, a first segment (“Fragl”) 704a can be transmitted during a time interval of T test reg 706. For Figure 6 and Figure 7The example shown can radiate up to 37 nJ on each of segments 704a to 704c. Therefore, if N segments 704 are used for a given UWB emission, the total emission can radiate up to N. 37nJ. It should be understood that the duration of T_test_reg 706 can be any suitable duration, such as a predefined time interval (e.g., 1 millisecond, 1.5 ms, 2 ms, etc.).

[0085] Figure 8 This is another simplified block diagram 800 illustrating at least some example techniques for transmitting data segments associated with a UWB packet type, according to some embodiments. In some embodiments, an example UWB packet format for performing UWB transmission is a packet format without data packets 801, as shown in diagram 800. See also above Figure 4 In the example of schematic diagram 800, the no-data packet 801 includes a Sync header (SHR) 802 and an STS / CIRTS 804. Note that the Sync header 802 may include a SYNC preamble and an SFD.

[0086] Figure 9 This is another simplified block diagram 900 illustrating at least some example techniques for transmitting data segments over multiple time intervals within a UWB framework, based on some implementation schemes. Figure 9 In schematic diagram 900, a data-free group 902 is shown (e.g., similar to...). Figure 8 The no-data packet 801 depicted may include an SHR field 904 and a CIRTS field 906. The no-data packet is divided into an SHR segment 908 and several (e.g., two in this example) CIRTS segments 910a to 910b. Each CIRTS segment 910 may be transmitted in a separate regulatory test interval to benefit from its full-energy budget. In some implementations, keeping these segments shorter is advantageous, at least because UWB signal processing can consume significant power due to the high bandwidth and sample rate in radio and digital modem circuitry. Furthermore, using shorter segment durations (e.g., and therefore longer silence periods between segments) can help minimize the chance of collisions between different links utilizing the same UWB spectrum.

[0087] As in Figure 9In particular, if the CIRTS 906 is distributed over multiple intervals, the receiver side (Station B) of the UWB link will be able to achieve higher performance when estimating the CIR. This is at least because the energy can be "pooled" from the various intervals of CIRTS segment 1 910a, CIRTS segment 2 910b, etc., which enables more accurate analysis of the segments and / or over longer distances. At the same time, to ensure that the CIR estimation works reliably, high performance of the Sync / Harvesting step can be desirable. This can be because mis-synchronization during the SHR 904 can degrade the CIRTS 906 processing. Because the CIRTS 906 is distributed over multiple intervals, the CIRTS 906 can be able to tolerate a certain amount of mis-synchronization. However, if the SHR 904 is also distributed over multiple intervals, the SHR 904 can be able to tolerate less mis-synchronization. This is because the SHR 904 is only benefiting from the energy of one interval, so there is an inherent imbalance between the energy available to the SHR 904 and the energy available to the CIRTS 906. One possible solution can be to distribute the SHR 904 over multiple intervals, and thus improve the operational performance. However, this can result in a less efficient solution. In some embodiments, the arrival times of the packets (e.g., segments of the packets) cannot be known exactly a priori. Thus, processing multiple SHR segments 908 in the Sync / Harvesting step can require the use of a large amount of memory for buffering and / or a large amount of processing power. This inefficiency can be undesirable, particularly for handheld / portable devices or Internet of Things devices. Thus, embodiments of the present disclosure provide techniques for increasing operational efficiency and / or operational range, e.g., via a hybrid wireless system, as further described herein. Figure 9

[0088] Figure 10 ​is another simplified diagram 1000 showing potential advantages and drawbacks of utilizing at least some wireless systems of UWB signaling 1002 and / or NB signaling 1004, according to some embodiments. In some embodiments described herein, a hybrid wireless system is utilized, where narrowband (NB) signaling 1004 and ultra-wideband (UWB) 1002 signaling are combined in a manner that addresses potential challenges presented herein and improves operational efficiency and / or operational range of the UWB system. In some embodiments, a system performing narrowband signaling can include a wireless system with a bandwidth that is significantly less than UWB. In some embodiments, UWB can have a minimum bandwidth of 500 MHz, so NB can refer to a system exhibiting a fraction of that bandwidth, such as a few 100 kHz, 1 MHz, or 10-20 MHz. Some non-limiting examples of NB systems would be narrowband GFSK (Gaussian frequency-shift keying) or DPSK (differential phase-shift keying) signaling utilized in Bluetooth or IEEE 802.15.4 O-QPSK (offset quadrature phase-shift keying format) as used in industry standards such as ZigBee or Thread. Narrower band modes in wireless local area networks (WLANs) such as IEEE 802.11 modes spanning 20 or 40 MHz of spectral bandwidth can also be classified as NB signaling in the context of the present disclosure, as they have a bandwidth that is significantly lower than UWB and tend to operate in different spectrums. In some embodiments, they are also regulated by a different set of regulatory constraints than UWB.

[0089] Turning in more detail to Figure 10 Before, and to provide another background related to regulatory constraints and bandwidth considerations, international regulatory rules governing UWB deployments and associated radiation emissions can define low emission limits for UWB devices, as the latter tend to operate in frequency bands below 10 GHz (mainly for commercial or military operations targeting point-to-point or satellite links, radars, or other protected applications). UWB emissions can thus be entrusted to operate at a level of spurious emissions allowed for other electronic devices (e.g., mobile devices, home devices, etc.), so as not to interfere with such permitted uses. Transmission power for UWB can be limited to -14 dBm on average in many regions.

[0090] In contrast, there are a variety of more narrowband systems and associated regulatory rules that have significantly more relaxed emission limits because they operate in frequency bands that are intended for such unlicensed use. The 2.4 GHz to 2.5 GHz so-called ISM (Industrial, Scientific, Medical) band is a prime example for NB applications such as 1 MHz or 2 MHz wide Bluetooth (BT) or ZigBee / Thread transmissions or wireless local area networks (WLANs) with bandwidth in the order of 20 MHz or 40 MHz. The 2.4 GHz to 2.5 GHz band is an example of a frequency band that is available in most regulatory regions worldwide. There are other ISM-like spectrums that include the 5.725 GHz to 5.875 GHz band in many countries. Other spectrums, including a large portion of the 5 to 6 GHz band, are also generally open to various unlicensed, non-UWB uses under certain conditions. The transmission power (radiated level) of these more NB systems is typically in the order of 10 dBm, 20 dBm, or even 30 dBm.

[0091] UWB is particularly advantageous for advanced ranging and sensing applications due to its large bandwidth (500 MHz, 1 GHz, or more), where the precise measurement of the propagation channel between associated devices allows the extraction of metrics such as time-of-flight (ToF) and corresponding distances between devices. However, the limited emission poses a challenge to the operating range. In contrast, the higher emission / transmission (Tx) power of NB systems allows for better operating range, but does not have enough potential for high-precision estimation due to its more limited bandwidth.

[0092] Turning now in more detail to Figure 10 , a diagram 1000 illustrates a comparison of the advantages and disadvantages of UWB and narrowband (NB) wireless systems from the perspective of an implementer of a wireless system. UWB signaling 1002 benefits from a large bandwidth of at least 500 MHz, which is very advantageous for high-resolution CIR measurements, which in turn can be used for precise positioning and ranging, as outlined above. The wide bandwidth is also beneficial for high-rate data transmission. One of the challenges associated with the larger UWB bandwidth is that it requires higher complexity, such as higher analog-to-digital converter (ADC) sample rates and associated signal processing effort as well as increased analog and digital power consumption. As explained above, UWB regulatory rules also impose significant constraints on the allowed emissions, which makes it more difficult to achieve the required operating range. In contrast, NB signaling 1004 tends to require considerably lower complexity and power consumption and can be more resistant to interference, especially when operating in a frequency-hopping manner. NB systems also benefit from significantly larger emission limits when operating in the spectrum designated for NB / ISM use. However, NB systems are not as well suited for high-resolution CIR estimation (ranging / sensing), partly because of the inherently limited bandwidth and thus limited resolvability of multipaths in the propagation channel.

[0093] Figure 11 is another simplified block diagram 1100 illustrating at least some example techniques for utilizing a mix of UWB signaling and NB signaling, according to some embodiments. In Figure 11 the diagram 1100, a portion of a no-data packet 1102 is shown being transmitted via mixed signaling. In this case, the Sync / Harvesting portion (SHR) 1104 of the UWB packet is replaced by an NB packet 1108, while the CIRTS 1106 continues to use UWB signaling. The NB packet 1108 is transmitted in a frequency band suitable for NB operation, and the UWB CIRTS 1106 is transmitted in a frequency band suitable for UWB operation. While in the diagram 1100, the NB packet 1108 and the UWB CIRTS 1106 occur in a time sequence (consecutively), they can also occur simultaneously in different embodiments. Note that each of these transmissions will be in accordance with regulatory rules governing NB and UWB transmissions, respectively.

[0094] In some embodiments, this NB / UWB mixed structure has certain benefits, which can be realized by utilizing devices operating in accordance with embodiments described herein. In some embodiments, the mixed packet structure enables these devices to cope with the challenges described above, for example, with respect to packet formats having segmented CIRTS (see, for example, Figure 9 ). This is illustrated in Figure 12 .

[0095] Figure 12 is another simplified block diagram 1200 illustrating at least some example techniques for utilizing a mix of UWB signaling and NB signaling, according to some embodiments. In Figure 12 the diagram 1200, the function of the SHR 1202 is taken over by an NB packet 1204 (e.g., transmitted via an NB signal), and where the CIRTS 1206 is segmented into a plurality (here, N) of segments 1208a-1208n. While the segments 1208 can be transmitted at the start of a predetermined time interval, embodiments should not be interpreted as being so limited. For example, in the illustration of Figure 12 , the transmission of segment N 1208n is slightly offset from the start of a particular time interval (e.g., a T test reg interval, as described and illustrated with respect to Figure 9 In some embodiments, the initiator and responder devices can communicate configuration information so that a receiver device (e.g., a responder device) can know in advance when to expect the parameters of this segment to be transmitted. This configuration information can be communicated via an NB signal. Further, while not illustrated in Figure 12 , note that segmented UWB transmissions occurring in the context of a mixed NB / UWB system can carry more than just CIRTS data. This can be based on the Figure 4"Data field" (PHR and payload / PSDU) allocation in the Figure 11 containing a single UWB fragment (N = 1, see Figure 12 ) and to UWB transmissions containing multiple UWB fragments (N > 1, see ) and implementations with N = 1 and N > 1 are possible.

[0096] Figure 13 is another simplified block diagram 1300 showing at least some example techniques for utilizing NB signaling via NB packet formats 1302, according to some embodiments. Figure 13 diagram 1300 shows two NB packet formats 1304a-b known in the art: the top NB packet format shows a Bluetooth format 1304a consisting of an access code, a header, and a payload portion. The bottom NB packet format shows an O-QPSK packet format 1304b from IEEE 802.15.4 (commonly used for ZigBee or Thread technologies). It should be understood that other suitable NB packet formats 1302 can be used to perform embodiments of the present disclosure.

[0097] It should be understood that the division of the packet field into fragments as shown in Figure 12 or Figure 9 is for functional purposes. For example, the fragments are not necessarily related to the original non-fragmented field. For example, it is not necessary that concatenating Figure 12 and / or Figure 9 the CIRTS fragments in results in the original non-fragmented CIRTS field. Thus, the fragmented fields represent a replacement of the original packet field in terms of the required functionality (such as channel (CIR) estimation in terms of the CIRTS packet structure fragmenting the CIRTS field). As described herein, in some embodiments, the NB packet can include a synchronization (sync) field (e.g., within the packet header) and / or a data payload field. In some embodiments, the sync field can be used to convey synchronization data. For example, a receiver device receiving the NB packet (e.g., during a scheduled window) can detect a signal pattern known between the transmitter device and the receiver device. In some embodiments, this signal pattern can be associated with the sync field (e.g., sync header) of the NB packet. Upon detecting this pattern, the receiver device can be able to extract synchronization data in the form of time and frequency information, as described herein. In some embodiments, the receiver device can also extract synchronization data from the data payload field of the NB packet, for example, in the form of scheduling information that can be used to schedule the subsequent reception of one or more UWB fragments.

[0098] Figure 14 is another simplified block diagram 1400 showing two devices configured to communicate with each other utilizing a mix of UWB signaling and NB signaling, respectively, according to some embodiments. Figure 14 The schematic diagram 1400 illustrates a view of two devices (device A 1402 and device B 1404) communicating with each other according to a hybrid wireless system approach, according to some embodiments. In particular, each device (1402 and 1404) has a hybrid wireless transceiver (HWT) 1406a or 1406b that includes an NB subsystem 1408a or 1408b and a UWB subsystem 1410a or 1410b closely coupled to each other in each respective device, as further described herein. As part of the communication between devices A and B, in particular using an “artificial division” between NB and UWB signaling, as previously shown by Figure 11 and Figure 12 As shown, the NB subsystem 1408a of device A 1402 can communicate directly with the NB subsystem 1408b of device B 1404, and the UWB subsystem 1410a of device A 1402 can communicate directly with the UWB subsystem 1410b of device B 1404. In Figure 14 , the NB subsystem 1408a-b and UWB subsystem 1410a-b in each device are shown as having their own physical antennas 1412a-b and 1414a-b (e.g., including a first antenna 1412a for the narrowband system 1408a and a second antenna 1414a for the UWB subsystem 1410a, for example), although it is understood that a single shared antenna covering both NB and UWB operations can be a suitable implementation, and multiple antenna solutions can be used for such advanced signal processing schemes as antenna diversity, spatial multiplexing, or transmit or receive beamforming.

[0099] Figure 15 is another simplified block diagram 1400 showing two devices configured to communicate with each other utilizing a mix of UWB signaling and NB signaling, respectively, according to some embodiments. Figure 15The schematic diagram 1500 provides more detail of the HWT 1502 in each device and shows details and functional components of the aforementioned tight coupling between the NB subsystem 1504 and the UWB subsystem 1506 in the HWT 1502. Each such transceiver includes an NB subsystem 1504 and a UWB subsystem 1506, each of which contains wireless transmit and receive circuitry and functionality for NB and UWB signaling, respectively. The HWT 1502 is also provided with a shared time base 1508 (e.g., module or unit) that consists of a crystal oscillator (XO) and any associated clocking and timing devices. The shared time base 1508 can enable the NB subsystem 1504 and the UWB subsystem 1506 to form signals that are tightly synchronized in time and frequency. That is, if the NB signals operate off the shared time base and have some clock frequency and / or carrier frequency defect (measured in parts per million [ppm] offset), the UWB signals in the same HWT 1502 can exhibit the same reference defect in ppm. Since the transmit and receive elements of the NB subsystem 1504 and the UWB subsystem 1506 of a device can operate off the same shared time base 1508, the clock / carrier offsets (in [ppm]) of the NB Tx (NB signal transmission), NB Rx (NB signal reception), UWB Tx (UWB signal transmission), and UWB Rx (UWB reception) circuitry can be substantially similar (e.g., the same).

[0100] Furthermore, as Figure 15As depicted in the middle, there is a junction controller (hybrid system controller (or control)) 1510 that governs both the transmission and reception activities of the NB subsystem 1504 and the UWB subsystem 1506, as well as the exchange of information between the NB system and the UWB system. In some embodiments, the hybrid system controller 1510 can be used to coordinate transmission or reception activities between a subsystem of a first device and another subsystem of a second device of the same type as the subsystem of the first device. In some embodiments, the hybrid system controller 1510 can coordinate the exchange of information between a narrowband subsystem of a first device and a super wideband subsystem of the same (first) device. In some examples, a control block (e.g., the hybrid system controller 1510) can receive time and frequency synchronization ("T and F Sync" or "Sync Data") information from the NB subsystem. The F Sync includes information related to the NB's estimated ppm offset with respect to the associated device. The T Sync includes information associated with the over-the-air packet timing as measured by the NB subsystem 1504. The control block can also receive payload data information (Rx Data) from the NB subsystem 1504. The T and F Sync and the Rx Data can be referred to herein together as "NB-Rx-Info." The control block also schedules the transmission and reception by the NB subsystem 1504, which can include certain Tx (transmission) / Rx (reception) parameters utilized by the NB subsystem 1504 as well as possible payload Tx data.

[0101] The control block also provides time and frequency (T and F) configuration information to the UWB subsystem 1506. This helps to set the UWB receiver more accurately based on the T and F information extracted from the NB signaling. Since there is a shared time base 1508 between the NB subsystem 1504 and the UWB subsystem 1506 (including any frequency offset with respect to the associated device), this configuration helps to tailor the UWB reception for the incoming UWB signal and maximizes the performance of the CIR estimate based on the CIRTS fragments. The control block also uses the NB Rx-Info to schedule UWB Tx and Rx activities based on certain Tx / Rx parameters such as carrier frequency or UWB bandwidth. In turn, the control block also receives UWB-Rx-Info that includes synchronization (time / frequency Sync) and CIR information.

[0102] Figure 16 is a simplified flowchart 1600 showing the exchange of signals between two devices according to some embodiments. Figure 16 The schematic diagram 1600 shows the use of the above-described (e.g., with reference to the above-described Figure 14 and Figure 15Figure 16 shows a signal and control flow diagram of an exchange between two associated HWTs of the HWT architecture of Figure 15. Dashed arrows represent wireless exchanges between device A 1602 and device B 1604, while solid arrows represent signals exchanged internally within each HWT (in device A 1602 or device B 1604). Note that control blocks are not explicitly shown in diagram 1600 for clarity of illustration. The NB subsystem 1606 in device A 1602 transmits an NB packet "NB-A to B" 1610 to the NB subsystem 1612 in device B 1602. The latter extracts T and F Sync information (which can additionally be referred to as "synchronization data") and provides this information to the UWB subsystem 1614 for later use. For example, the synchronization data can be used to schedule, configure, and / or receive subsequent UWB fragments from device A 1602, as further described below. The NB subsystem 1612 of device B 1604 responds with its own NB packet "NB-B to A" 1616 back to device A 1602, which in turn extracts T and F Sync information from the NB packet and provides the information to its local UWB subsystem 1618 for later use. Subsequently, the UWB subsystem 1618 in device A 1602 sends a UWB transmission "UWB-A to B" 1620 (specifically a CIRTS or CIRTIS fragment series) to the UWB subsystem 1614 in device B 1604. As described above, device B 1604 can be able to efficiently determine when to expect the UWB transmission from device A 1602 based in part on the previously stored T and F sync extracted from the NB packet reception. That is, the UWB subsystem 1614 in device B 1604 has a more accurate understanding of when to expect the UWB signal from device A 1602 and how much ppm offset it will have, which the UWB subsystem can use to minimize signaling processing effort and maximize performance of the reception algorithm and associated reception circuitry. Device B 1604 then transmits a UWB response "UWB-B to A" 1622, which device A 1602 can receive in a more efficient and accurate manner based on the T and F Sync information obtained during reception of the "NB-B to A" 1616 packet. In some implementations, the exchange "UWB-A to B" 1620 and "UWB-B to A" 1622 can be a TOF measurement. Figure 5

[0103] ​In some embodiments, the T and F synchronization information extracted from the respective NB signals can be of high quality, as NB signaling can be subject to less stringent transmission emission rules. As a result, the signal-to-noise ratio (SNR) at the receiver side of the NB transmission can be higher and allow for more efficient and accurate acquisition. The T and F processing in the NB subsystem is also low-complexity and low-power compared to the UWB subsystem, at least because the sample rate is substantially lower in the NB subsystem than in the UWB subsystem. At the same time, the "NB-assisted" reception of the UWB CIRTS segments will be of high quality (and high SNR) due to the aggregation of energy from multiple segments, thus enabling high-precision CIR extraction and corresponding positioning / ranging functionality. This "division of labor" between the NB and UWB subsystems when compared to other UWB systems enables improved operating range and operating efficiency.

[0104] It should be understood that while various modules (e.g., components and / or associated functionality) are described as being separate from other modules, embodiments should not be interpreted as being so limited. For example, Figure 15 The hybrid system controller is depicted as a module separate from the shared timebase unit, which is itself separate from both the NB subsystem and the UWB subsystem. However, in some embodiments, the shared timebase module and / or the hybrid system control module can reside within one of the subsystems (NB or UWB). In such cases, the respective other subsystem can benefit from the control and timebase functionality as a secondary or proxy system (e.g., a delegate system and / or a subordinate system). In any case, different distributions and / or aggregations of features between different modules can enable hybrid signaling to be performed as described in embodiments herein. It should also be understood that, Figure 16 and Figure 17 The signal exchange diagram shown (further described below) illustrates a particular type of signal exchange for a hybrid wireless system composed of NB and UWB subsystems. Other types of signal exchanges via other hybrid protocols are further described herein. These protocols correspond to different arrangements of NB and UWB transmissions while still employing a hybrid signaling approach with devices (e.g., initiator and responder devices) that each include an HWT.

[0105] Figure 17 is another simplified flow diagram 1700 showing a signal exchange between two devices, in accordance with some embodiments. Figure 17 The diagram 1700 is a more detailed diagram of example signal flows between and within the HWTs in devices A and B (e.g. Figure 16 The devices A 1602 and B 1604 of the diagram 1700. Additionally, Figure 18 and Figure 19A flow diagram illustrating processing steps by respective devices, with device A 1602 referred to as the "initiator" device (or "first device"), and device B 1604 referred to as the "responder" device (or "second device"). Thus, the description of the processing steps by each device can refer to Figure 17 for further illustration of the signal exchange process. It should be understood that in some embodiments, the initiator device can alternatively operate as the responder device, and similarly, the responder device can alternatively operate as the initiator device, depending on the context.

[0106] Turning in more detail to the processing steps of device A (e.g., device A 1602) as depicted by the process 1800 of Figure 18 At block 1802, the first device can schedule a NB-Tx start time and a NB-Rx window. In some embodiments, the operations of this block can be by a wireless system of the first device that is separate from the HWT. For example, the wireless system can utilize Bluetooth / BLE protocols. In some embodiments, the operations of this block can be performed within an initial phase of the process 1800. The wireless system can be responsible for one or more operations of the initial phase including processing advertisements and / or scanning (e.g., device discovery), performing a "coarse synchronization" with a responder device B (e.g., device B 1604), and / or performing other connection setup steps with the device B 1604 (e.g., second device). As described further herein, in some embodiments, a separate wireless system can be responsible for transmitting NB control information including, for example, what channel and / or how many hop channels will be used for NB signaling. In some embodiments, a start time (e.g., a discrete instant) for transmission of a NB poll packet to the second device can be scheduled, and a time window for receiving a NB response packet from the second device can be scheduled. In some embodiments, the coarse synchronization can enable respective timekeeping devices of the devices to synchronize to within about 1 ms increments of each other. This initial coarse synchronization can enable subsequent "fine" synchronization via exchange of NB signals as described further below.

[0107] At block 1804, the first device can transmit a NB poll packet (depicted in Figure 17 as NB-Tx A to B 1702) to the device B 1604 via a narrowband signal at the scheduled start time. The poll packet can convey synchronization data (e.g., time and frequency synchronization data) that the second device can subsequently use to schedule reception of multiple segments via ultra-wideband signals, respectively.

[0108] At block 1806, the first device can wait for a NB response packet, for example, which it can expect to receive from the second device during the scheduled window (e.g., time interval).

[0109] At block 1808, the first device can receive a NB response packet (depicted in Figure 17 FIG. 17B as NB-Rx B to A 1704). For example, the first device can initiate reception of the NB response packet via the narrowband signal during the scheduled window.

[0110] At block 1810, the first device can obtain NB-Rx-Info from the NB response packet. As described herein, this can include second synchronization data (e.g., time and frequency synchronization data) that the first device can use to schedule reception of a second plurality of segments, which are subsequently received by the first device from the second device.

[0111] At block 1812, the first device can schedule transmission of a plurality of segments (UWB-Tx segments 1706a-1706n). In some embodiments, this scheduling can be in accordance with synchronization data that is communicated to the second device and obtained by the second device from the NB transmission by the first device to the second device (e.g., at block 1804), which in turn can be used by the second device to schedule and assist reception of the plurality of segments 1706a-1706n.

[0112] At block 1814, the first device can transmit a UWB poll packet to the second device in the form of the plurality of segments (depicted in Figure 17 FIG. 17B as UWB-Tx A to B-1... UWB-Tx A to B-N 1706a-1706n). As described herein, each segment of the plurality of segments 1706a-1706n can be spaced apart in time from other segments of the plurality of segments 1706a-1706n by at least a predefined time interval. In some embodiments, this time interval can be determined based in part on regional regulatory rules governing signal transmission.

[0113] At block 1816, the first device can schedule reception of a second plurality of segments based on the second synchronization data obtained at block 1810 (e.g., from the NB-Rx-Info).

[0114] At block 1818, the first device can receive the second plurality of segments (depicted in Figure 17 FIG. 17B as UWB-Rx B to A-1... UWB-Rx B to A-N 1708a-1708n) from the second device.

[0115] At block 1820, the first device can obtain aggregated UWB-Rx-Info from the second plurality of segments. In some embodiments, this can include synchronization data and / or other data that can be used to determine a CIR (e.g., a CIR estimate). As described herein (e.g., with respect to Figure 3The CIR estimate can be associated with a LOS path between the first device and the second device. As described herein, the CIR can be used to determine a TOF interval, which in turn can enable ranging and / or positioning to be determined by the first device (e.g., relative to the second device). For example, the first device can determine a turnaround time interval, which represents a time interval between a time at which the second device receives the plurality of segments and a time at which the second device transmits the second plurality of segments to the first device (see Figure 5 ). In some embodiments, the first device can know the turnaround time interval in advance (e.g., a fixed time interval). In some embodiments, the first device can not know the turnaround time interval in advance, and can subsequently receive the NB signal from the second device that conveys this information. See, e.g., Figure 30 , further described herein. In any case, the first device can calculate the TOF by considering (e.g., subtracting) the turnaround time from the TOF flight, as described with respect to Figure 5 .

[0116] As introduced above, Figure 19 is another simplified flow diagram illustrating an exemplary process by a responder device, in accordance with some embodiments. Similar to the description of the initiator device of Figure 18 , Figure 19 the description of the processing steps by the responder device in Figure 17 may refer to Figure 19 (e.g., with device B 1604 operating as a responder device) for further illustration of the signal exchange process. Note that Figure 18 the processing steps of may correspond to equivalent steps (e.g., from the perspective of the responder device) of the processing steps of

[0117] . Figure 19 Turning in more detail to the processing steps of device B 1602 (which can be referred to as a “second device”), as depicted by the process 1900, at block 1902, the second device can schedule a NB-Rx time. In some embodiments, the operations of block 1902 can be similar to the operations of block 1802. For example, a wireless system of the second device can perform coarse synchronization with the first device (e.g., initiator device A 1602 of Figure 17 and Figure 18 .

[0118] At block 1904, the second device can wait for a NB poll packet from the first device. For example, the NB poll packet can have been transmitted at block 1804 of the process 1800.

[0119] At block 1906, the second device can receive the NB poll packet from the first device (depicted as NB-Rx A-to-B 1710 in Figure 17 .

[0120] At block 1908, the second device can obtain NB-Rx-Info from the NB poll packet. As described herein, this can include extracting synchronization data (e.g., time and frequency synchronization data and / or scheduling information) that the second device can use to schedule and / or assist reception of a plurality of segments via UWB signals that are subsequently received by the second device from the first device. In some embodiments, the NB-Rx-Info can also contain data used to schedule transmission of a NB response packet (e.g., at a second start time). In some embodiments, data from the NB-Rx-Info can be used for other purposes (e.g., status reporting, etc.).

[0121] At block 1910, the second device can schedule transmission of a NB response packet (e.g., at a second start time). As described above, in some embodiments, this scheduling can be based on the NB-Rx-Info obtained at block 1908. In some embodiments, this scheduling can be performed independently of data in the NB-Rx-Info.

[0122] At block 1912, the second device can transmit the NB response packet to the first device (e.g., at the previously scheduled second start time) (depicted in Figure 17 as NB-Tx B to A 1712).

[0123] At block 1914, the second device can schedule and configure a UWB receiver (e.g., a UWB subsystem) for UWB-Rx reception of the plurality of segments based on the synchronization data received at block 1908. Here, the NB-Rx-Info can also be used to configure the UWB receiver prior to and for reception of the UWB signals, particularly one or more of correction for carrier frequency offset, sampling frequency offset, carrier phase, and sample phase.

[0124] At block 1916, the second device can receive UWB segments (depicted in Figure 17 as UWB-Rx A to B-1... UWB-Rx A to B-N 1714a to 1714n). These UWB segments can be the UWB segments transmitted at block 1814 of Figure 18 .

[0125] At block 1918, the second device can obtain aggregated UWB-Rx-Info. In some embodiments, the operations of this block can be similar to the operations of block 1820. In this case, the second device can obtain synchronization data and / or other data that can be used to determine a CIR.

[0126] At block 1920, the second device can schedule, configure, and transmit UWB-Tx response segments (depicted in Figure 17The response fragment can correspond to a plurality of fragments (e.g., a second plurality of fragments of the process 1800 received by the first device from the second device at block 1818). In some embodiments, scheduling transmission of the plurality of fragments can be based in part on the NB-Rx-Info (e.g., obtained at block 1908) and / or the UWB-Rx-Info (e.g., obtained at block 1918, including UWB time / frequency synchronization data, CIR, etc.). In some embodiments, the second device can also be capable of performing ranging and / or positioning, similar as described with respect to the first device. For example, the second device can determine turn-around time and / or timestamp information that enables it to determine TOF / range information (see further described herein Figure 28 Option 2 of

[0127] In some embodiments, the number of UWB fragments in the forward (A-to-B "polling") direction can be the same as the number of UWB fragments in the reverse (B-to-A "response") direction, i.e., N, with respect to embodiments of Figure 17 , Figure 18 and Figure 19 . In some embodiments, the number of fragments for the forward and reverse directions can be different, and can be given as Nfand Nrfor the forward and reverse directions, respectively.

[0128] Figure 20 is another simplified block diagram 2000 showing transmission of UWB payload data with NB signaling, according to some embodiments. The schematic 2000 depicts embodiments as applicable and beneficial in some standard-based UWB packet formats (e.g., see Figure 4 ), where the UWB payload data 2002 is concatenated with the SHR 2004 when processed by the NB signaling layer. In some embodiments, the NB subsystem with its associated signaling can facilitate coordination of devices A and B for various management and maintenance purposes such as mutual transmission of status information, as further described herein. In some embodiments, the payload data of the UWB packet 2006 can also be transmitted via a plurality of fragments, similar as described with respect to transmission of CIRTS via UWB fragments.

[0129] Figure 21 is another simplified block diagram 2100 showing example waveforms that can be contained in one or more fragments transmitted by the UWB signaling layer of a device, according to some embodiments. Figure 21Schematic diagram 2100 illustrates details of the IR waveforms contained in each CIRTS segment 2102a to 2102n used in the UWB signaling layer. Specifically, the diagram lists various types of sequences that can be used to determine the polarity of the UWB IR pulses in each CIRTS segment 2102. This is done in a packet format conforming to 802.15.4z (see [link to diagram]). Figure 4 In the sequence, the pulse polarity sequence used to represent CIRTS is based on the sequence of the Cryptographic Secure Pseudo-Random Generator (CSPRNG) used for the STS portion of the packet. The same CSPRNG type sequence "R" is used for each segment (e.g., segment 2102) in... Figure 21 The following is shown as row 1 in the table. Row 2 shows an implementation scheme for determining the IR pulse polarity of each segment using different CSPRNG polarity sequences (“R1”, “R2”, etc.). Row 3 represents an implementation scheme where a given CIRTS segment 2102 consists of a periodically repeating short sequence, i.e., the concept of a traditional ternary Ipatov preamble sequence used in IEEE 802.15.4 UWB. Note that this periodic sequence “E” can be an Ipatov sequence or another periodic sequence in which each CIRTS segment 2102 consists of a series (periodically repeating) of a given base sequence. In row 3 of the table, the same periodic sequence “E” is used for each CIRTS segment 2102, while in row 4, different periodic sequences (“E1”, “E2”, etc.) can be used for each CIRTS segment 2102. In rows 5 and 6, Gray waveforms are used for each segment. Gray waveforms consist of a pair of continuously transmitted sequences that together have highly accurate autocorrelation properties. One or more Gray pairs (with a sufficiently long guard (silent) interval between them to cover the length of the intended CIR) can be used to represent “G” in each segment 2102. Different choices of Gray pairs (one or more pairs per segment 2102) can be used across N segments 2102, such as “G1”, “G2”, ..., “GN”. In one specific embodiment using Gray sequences, each segment 2102 uses multiple Gray pairs, wherein all pairs in a given segment are based on the same pair, such that segment 2102 contains a periodic sequence, each period of which is given by one and the same Gray pair. In a later embodiment, similarly, segments 2102a to 2102n can utilize the same periodic sequence or Gray-based periodic sequences that vary from segment to segment.

[0130] As described herein, the implementation scheme describes tight coupling of the NB and UWB subsystems to improve effective operating range. As further described herein, several protocol variations may exist that utilize hybrid signaling via tight coupling of the NB and UWB subsystems to achieve improved operating range and / or efficiency.

[0131] Figure 22This is another simplified flowchart illustrating the first part of an exemplary process performed by a device for hybrid signaling, according to some embodiments. In some embodiments, Figure 22 and Figure 23 Process 2200 corresponds to the process used by the initiating device to determine the CIR estimate. (Note that...) Figure 23 The frame is Figure 22 (This is a continuation of process 2200.) In some implementations, this process may be similar to that performed by the initiator. Figure 18 Process 1800. Process 2200 (and other process flows described herein) are shown as logic flowcharts, each operation representing a series of operations that can be implemented in hardware, computer instructions, or combinations thereof. In the context of computer instructions, an operation represents computer-executable instructions stored on one or more computer-readable storage media that perform the operation when executed by one or more processors. Generally, computer-executable instructions include routines, programs, objects, components, data structures, etc., that perform a particular function or implement a particular data type. The order in which the operations are described is not intended to be construed as limiting, and any number of the operations may be implemented in any order and / or in parallel combinations to implement the process. In some embodiments, any one or more of the flows described herein may be implemented by a hybrid wireless system, such as a reference Figure 14 and / or Figure 15 The hybrid wireless transceiver described.

[0132] Furthermore, some, any, or all of these processes can be executed under the control of one or more computer systems configured to have executable instructions, and can be implemented as code (e.g., executable instructions, one or more computer programs, or one or more application programs) that executes on one or more processors, by hardware, or a combination thereof. As described above, the code can be stored on a computer-readable storage medium, for example, in the form of a computer program comprising multiple instructions executable by one or more processors. The computer-readable storage medium is non-transitory.

[0133] In some implementations, process 2200 may be performed by an initiating device (e.g., a "first device") that exchanges one or more signals with a responding device (e.g., a "second device"). As described herein, it should be understood that, depending on the environment, the device may operate as both an initiating (device) and / or a responding (device). Therefore, for example, one or more operations of process 2200 may also be applicable (e.g., similar) to the first device operating as a responding device.

[0134] Turning more specifically to process 2200, at block 2202, the first device (initiator) can schedule the start time (e.g., discrete time) for transmitting packets to the second device (responder) via narrowband (NB) signals. In some embodiments, one or more operations of block 2202 may be similar to... Figure 18 The operation of box 1802.

[0135] At block 2204, the first device can schedule a window for receiving a second packet transmitted by the second device via a second narrowband signal to the first device. In some embodiments, one or more operations of block 2204 may be similar to... Figure 18 The operation of box 1802.

[0136] At block 2206, the first device may transmit the packet to the second device via a narrowband signal at the start time. In some embodiments, the packet may include data instructing the second device, for example, time periods for the reception of multiple segments. For example, the packet may convey synchronization data, which the second device may use to schedule and / or assist the reception of multiple segments, respectively, via an ultra-wideband (UWB) signal. In some embodiments, one or more operations of block 2206 may be similar to... Figure 18 The operation of box 1804.

[0137] At block 2208, the first device can receive a second packet from the second device via a second narrowband signal during this window. In some embodiments, one or more operations of block 2208 may be similar to... Figure 18 Operation of box 1808.

[0138] At block 2210, the first device may obtain (e.g., extract) second synchronization data based at least in part on the second packet (e.g., the sync header and / or data payload of the second packet). In some embodiments, one or more operations of block 2210 may be similar to... Figure 18 Operation of box 1810.

[0139] At block 2212, the first device can schedule the transmission of the multiple segments via an ultra-wideband signal. In some embodiments, this scheduling can be performed based on synchronization data previously communicated to the second device (e.g., scheduling information at block 2206). In some embodiments, one or more operations of block 2212 can be similar to... Figure 18 The operation of box 1812.

[0140] continue Figure 23At block 2214, the first device can transmit the plurality of segments to the second device via an ultra- wideband signal. In some embodiments, at least one segment of the plurality of segments can be separated in time from at least one other segment of the plurality of segments by at least a predetermined time interval. In some embodiments, one or more operations of block 2214 can be similar to operations of block 1814 of FIG. 18. Figure 18

[0141] At block 2216, the first device can schedule reception of a second plurality of segments based at least in part on the second synchronization data. In some embodiments, one or more operations of block 2216 can be similar to operations of block 1816 of FIG. 18. Figure 18

[0142] At block 2218, the first device can receive the second plurality of segments from the second device via a second ultra- wideband signal, respectively. In some embodiments, one or more operations of block 2218 can be similar to operations of block 1818 of FIG. 18. Figure 18

[0143] At block 2220, the first device can determine a channel impulse response (CIR) estimate value based at least on the second plurality of segments. In some embodiments, the channel impulse response estimate value can be associated with a line-of-sight (LOS) path between the first device and the second device. In some embodiments, one or more operations of block 2220 can be similar to operations of block 1820 of FIG. 18. Figure 18

[0144] Figure 24 is another simplified flow diagram 2400 showing signal transmission with one or more NB channels according to a bidirectional redundant packet switching protocol, according to some embodiments. Joint use of redundant / repeated NB packet switching (e.g., see block 1804 of FIG. 18 and / or block 1912 of FIG. 19) with a pseudo-random channel hopping sequence can improve reliability against interference and / or multipath fading phenomena. Figure 18 Figure 19 Figure 24 ​​​​​​FIG. 24 is a simplified flow diagram illustrating an example of this scheme with three redundant transmissions using pseudo-random channels. The term "channel" here refers to a specific wireless frequency spectrum location at which an NB is transmitted, such as a carrier frequency in GHz (such as, for example, 2.450 GHz or 5.806 GHz or 5.912 GHz) around which the NB signal is centered with its specific spectrum bandwidth (such as 1 MHz or 2 MHz or a few hundred kHz). Certain channels can be congested by other wireless users or suffer from signal fading that is common when communicating wirelessly in a multipath environment, and "hopping" across channels helps reduce packet loss due to these phenomena. An initiator 2402 (such as one of the initiator devices described herein) initiates a first message within an initiation packet, and a responder 2404 attempts to receive the first message. In some embodiments, this scheme can be further optimized to save power by using the following rules: (a) the initiator 2402 skips the rest of the NB exchange when it receives any of (2), (4), and (6); (b) the responder 2404 should always listen to (1), (3), and (5), but only transmits (2), (4), and / or (6) if its immediately preceding reception was successful. This scheme can be referred to as a bidirectional NB exchange, since both sides exchange NB packets. This protocol can be useful if the next tightly coupled UWB exchange also involves bidirectional messages / fragments (e.g., as depicted in Figure 17

[0145] Figure 25 is another simplified flow diagram illustrating message exchange between two devices utilizing one or more NB channels according to a bidirectional redundant packet exchange protocol, according to some embodiments. In some embodiments, Figure 25 The message exchange of process 2500 can correspond to the protocol depicted with reference to Figure 24 It should be understood that some operations associated with process 2500 (e.g., scheduling transmission of NB signals, UWB fragments, etc.) (and / or other processes described further herein) can additionally be performed before, during, or after the operations of the blocks depicted in process 2500. Thus, it should be understood that the simplified protocol illustrated by process 2500 (and / or other processes described herein) can also include other operations and / or protocol variations of the present disclosure (e.g., full ranging protocols, beaconing protocols, etc.) (and / or be included within other operations and / or protocol variations of the present disclosure).

[0146] ​Turning to the process 2500, at block 2502, a first device (e.g., initiator 2402) can transmit a first initiation packet to a second device (e.g., responder 2404) via a first narrowband channel. As described above, and for example, it should be appreciated that one or more operations can be performed prior to the operation of block 2502 to schedule a start time for transmission of the first initiation packet (e.g., similar to one or more operations of block 1802 of FIG. 18 Figure 18 ).

[0147] At block 2504, the first device can transmit a second initiation packet to the second device via a second narrowband channel that is different from the first narrowband channel. The second initiation packet can be transmitted based at least in part on determining, in response to the first initiation packet, that the first device did not receive a first response packet from the second device via the first narrowband channel. Note that the first device can not have transmitted the second initiation packet to the second device if the second device has transmitted the first response packet. In some embodiments, the second initiation packet can be transmitted even if the first device received the first response packet from the second device.

[0148] At block 2506, the first device can transmit a third initiation packet to the second device via a third narrowband channel that is different from the first narrowband channel and / or the second narrowband channel. The third initiation packet can be transmitted based at least in part on determining, in response to the second initiation packet, that the first device did not receive a second response packet from the second device via the second narrowband channel.

[0149] At block 2508, the first device can receive a third response packet from the second device via the third narrowband channel in response to the third initiation packet. At this block, the first device can then terminate the exchange of NB packets in accordance with the protocol described with reference to Figure 24

[0150] Figure 26 is another simplified flow diagram 2600 illustrating signal transmission with one or more NB channels according to a unidirectional redundant packet transmission protocol, in accordance with some embodiments. Figure 26 Similar to Figure 24 , but in this case, only one side transmits NB packets (e.g., initiator 2602 to responder 2604). Embodiments that employ a beaconing protocol (e.g., as further described herein with respect to Figure 34 ) can benefit from this approach. As described with reference to Figure 24 , in some embodiments, an OOB system can be used to coordinate transmission of NB control information (e.g., via Bluetooth / BLE).

[0151] Figure 27 is another simplified flow diagram illustrating message exchange between two devices with one or more NB channels according to a unidirectional redundant packet transmission protocol, in accordance with some embodiments. In some embodiments,​Figure 27 The message exchange of FIG. 2800 can correspond to the protocol depicted with reference to Figure 26 FIG. 2800.

[0152] At block 2702, a first device (e.g., initiator 2602) can transmit a first initiation packet to a second device (e.g., responder 2604) via a first narrowband channel.

[0153] At block 2704, the first device can transmit a second initiation packet to the second device via a second narrowband channel that can be different from the first narrowband channel.

[0154] At block 2706, the first device can transmit a third packet to the second device via a third narrowband channel that can be different from the first narrowband channel and the second narrowband channel.

[0155] Figure 28 is another simplified flowchart 2800 showing signal transmission of a non-interleaved ranging protocol with a known fixed turnaround time, in accordance with some embodiments. Figure 28 The diagram 2800 of FIG. 2800 depicts a full ranging protocol with hybrid signaling as described herein. This bidirectional NB exchange is the same as shown in Figure 24 The initiator 2802a then sends UWB segments in accordance with the information exchanged through the NB / OOB protocol. After receiving all UWB segments, the responder 2804a performs ToA (time of arrival) extraction and sends its response UWB segments starting from a fixed precise time. This can be referred to as a fixed turnaround time interval (e.g., fixed time interval) and the granularity of such time can be tens of picoseconds. Since this fixed turnaround time itself conveys the precise time increment between the responder UWB RX and TX implicitly, it eliminates the need to convey this precise time increment through data packet / payload. The initiator 2802a can calculate the TOF after receiving the UWB segments from the responder 2804a. Accordingly, if the responder 2804a determines to calculate the range, Option 2 of FIG. 2800 can be utilized. For example, the order of exchange of UWB segments can be swapped such that the responder 2804b first sends a plurality of segments and then receives a response plurality of segments from the initiator 2802b. In this Option 2, the fixed turnaround time is still employed.

[0156] Figure 29 is another simplified flowchart showing message exchange based on a known fixed turnaround time, in accordance with some embodiments. In some embodiments, Figure 29 The message exchange of process 2900 of FIG. 2900 can correspond to the protocol depicted with reference to Figure 28 FIG. 2900.

[0157] At block 2902 of the process 2900, a first device (e.g., the initiator 2802) can transmit a packet to a second device (e.g., the responder 2804) via a narrowband signal. In some embodiments, the packet can convey synchronization data (e.g., time and frequency synchronization data and / or scheduling information). In some embodiments, one or more operations of block 2902 can be similar to operations of block 1804 of the process 1800 described with reference to FIG. 18. As described herein, the second device can obtain (e.g., extract from a sync header and / or payload data of the packet) and utilize the synchronization data to schedule reception of a plurality of UWB segments from the first device. The first device can also schedule transmission of the plurality of UWB segments in accordance with the synchronization data. Figure 18

[0158] At block 2904, the first device can receive a second packet from the second device, the second packet conveying second synchronization data to the first device via a second narrowband signal. In some embodiments, one or more operations of block 2904 can be similar to operations of block 1808 of the process 1800 described with reference to FIG. 18. As described herein, the first device can obtain and utilize the second synchronization data to schedule reception of a plurality of UWB segments from the second device. The second device can also schedule transmission of a second plurality of segments in accordance with the second synchronization data. Figure 19

[0159] In some embodiments, blocks 2902 and 2904 can be repeated in accordance with the schemes described with reference to Figure 24 and Figure 25

[0160] At block 2906, the first device can transmit the plurality of segments to the second device via an ultra-wideband signal. In some embodiments, each segment of the plurality of segments can be separated in time from other segments of the plurality of segments by at least a predefined time interval (e.g., in accordance with relevant regulatory rules for the transmitting standard).

[0161] At block 2908, the first device can receive a second plurality of segments from the second device via a second ultra-wideband signal, respectively. In some embodiments, a first time at which a first segment of the second plurality of segments is transmitted to the first device is offset from a first time at which a first segment of the plurality of segments is transmitted from the first device to the second device by at least a fixed time interval known to the first device. In some embodiments, the fixed time interval can be used to calculate a range or a time of flight. For example, the first device can determine a turnaround time, which can then be used to determine a TOF.

[0162] At block 2910, the first device can determine a channel impulse response (CIR) estimate value based at least on the second plurality of segments. In some embodiments, the channel impulse response estimate value can be associated with a line of sight (LOS) path between the first device and the second device.

[0163] ​​​Figure 26 is another simplified flow diagram 3000 illustrating a non-interleaved ranging protocol that includes the exchange of a narrowband signal to communicate round trip times and / or turn-around times after the exchange of UWB fragments, according to some embodiments. Figure 27 The schematic 3000 of FIG. 30 is similar to Figure 32 but after the exchange of UWB fragments between the initiator 3002 and the responder 3004, a unidirectional / bidirectional NB packet is used to communicate the round trip times and / or turn-around times and optional status report. This can be useful if the devices do not have fixed turn-around time capabilities or both sides need to know the range / TOF. Note that a unidirectional NB exchange can be used when only one side needs to know the range and a bidirectional NB exchange can enable both sides to calculate the range.

[0164] Figure 32 is another simplified flow diagram illustrating the exchange of messages with a narrowband signal exchange after the exchange of UWB fragments, according to some embodiments. In some embodiments, Figure 33 the message exchange of the process 3100 can correspond to the protocol depicted with reference to Figure 33 .

[0165] At block 3102 of the process 3100, the first device (e.g., the initiator 3002) can transmit a packet to the second device (e.g., the responder 3004) via a narrowband signal, the packet communicating synchronization data. In some embodiments, one or more operations of block 3102 can be similar to the operations of block 2902 of the process 2900. Figure 32 .

[0166] At block 3104, the first device can receive a second packet from the second device, the second packet communicating second synchronization data via a second narrowband signal. In some embodiments, one or more operations of block 3104 can be similar to the operations of block 2904 of the process 2900. Figure 18 .

[0167] In some embodiments, blocks 3102 and 3104 can be repeated in accordance with the schemes described with reference to Figure 26 and Figure 27 .

[0168] At block 3106, the first device can transmit a plurality of fragments to the second device via an ultra-wideband signal, each fragment of the plurality of fragments being separated in time from other fragments of the plurality of fragments by at least a predefined time interval. In some embodiments, one or more operations of block 3106 can be similar to the operations of block 1814 of the process 1800. Figure 18 .

[0169] At block 3108, the first device can receive a second plurality of fragments from the second device via a second ultra-wideband signal, respectively. In some embodiments, one or more operations of block 3108 can be similar to operations of block 1818 of FIG. 18. Figure 18

[0170] At block 3110, the first device can receive a third packet from the second device via a third narrowband signal. In some embodiments, the third packet can include information that can be used to determine a range or time of flight. In some embodiments, this information can include at least one of (I) a round trip time, (II) a turnaround time, or (III) a status report. In some embodiments, the first device can also transmit a fourth packet to the second device via a fourth narrowband signal, as described herein. This fourth packet can convey a similar type of information as that included in the third narrowband signal. This data can allow the second device to also calculate the range. As described above, this technique can be useful if the devices do not have fixed turnaround time capabilities or if both sides need to know the range / TOF.

[0171] In some embodiments, block 3110 can be repeated according to the schemes described with reference to Figure 26 and Figure 27 and / or Figure 18 and Figure 34

[0172] Figure 35 is another simplified flowchart 3200 illustrating signal exchanges according to a one-way NB and non-interleaved UWB ranging protocol, according to some embodiments. Figure 35 The schematic 3200 depicts another variation in which a one-way NB exchange between an initiator 3202 and a responder 3204 is followed immediately by a UWB fragment in the same direction. By having multiple responders 3204 respond in a known sequence or in a random order, this scheme can allow the multiple responders to participate in a ranging exercise. In some embodiments, the responses can either include a timestamp in the responding NB packet or respond using a fixed turnaround time scheme (as described herein). The initiator 3202 can thereby calculate the respective ranges, as described herein.

[0173] Figure 34 is another simplified flowchart illustrating message exchanges according to a one-way NB and non-interleaved UWB ranging protocol, according to some embodiments. In some embodiments, Figure 18 the message exchanges of process 3300 of FIG. 33 can correspond to the protocol depicted with reference to Figure 18

[0174] ​​​At block 3302, a first device (e.g., initiator 3202) may transmit packets via narrowband signals to a second device (e.g., responder 3204), the packets conveying synchronization data. In some embodiments, one or more operations of block 3302 may be similar to... Figure 26 The operation of box 1804. In some implementations, it can be done according to the reference. Figure 27 and Figure 18 The aforementioned scheme repeats box 3302.

[0175] At block 3304, the first device can transmit the multiple segments to the second device via an ultra-wideband signal. In some embodiments, one or more operations of block 3304 may be similar to... Figure 18 The operation of box 1814.

[0176] At block 3306, the first device can receive a second packet from the second device, which transmits second synchronization data via a second narrowband signal. In some embodiments, one or more operations of block 3306 may be similar to... Figure 36 The operation of box 1808. Note that in this case, the first device can receive the second packet after the transmission of the plurality of segments at box 3304. In some embodiments, it can be done according to reference... Figure 36 and Figure 7 The aforementioned scheme repeats box 3306.

[0177] At block 3308, the first device can receive a second plurality of segments from the second device via a second ultra-wideband signal. In some embodiments, one or more operations of block 3308 may be similar to... Figure 30 The operation of box 1818. In some implementations, the first device may then use this information to calculate ToF and / or AoA.

[0178] Figure 37 This is another simplified flowchart 3400 illustrating signal exchange according to a beacon protocol, based on some implementations. As described above, in some implementations, the beacon protocol can be employed when only one side (such as initiator 3402) transmits NB signals (e.g., NB packets) and UWB signals (e.g., multiple segments). For example, this can be useful if a second (receiver) device is one of several devices of interest 3404 interacting with a first device according to the beacon protocol. In one example, the receiver device then performs ranging and / or positioning based on triangulation with one or more other devices, partly based on the estimated CIR. In some implementations, initiator 3402 may send periodic beacon messages. It should be noted that the beacon protocol still utilizes the hybrid signaling approach as described herein.

[0179] Figure 37is another simplified flow diagram illustrating message exchanges according to a beaconing protocol, according to some embodiments. In some embodiments, Figure 36 The message exchanges of process 3500 can correspond to the protocol described with reference to Figure 29

[0180] At block 3502, a first device (e.g., initiator 3402) can schedule a start time for transmitting a packet to one or more devices of interest 3404 via a narrowband (NB) signal. In some embodiments, one or more operations of block 3502 can be similar to the operations of block 1802 of process 1800. Figure 29

[0181] At block 3504, the first device can transmit the packet to the one or more devices of interest 3404 via the narrowband signal at the scheduled start time. In some embodiments, the packet can convey synchronization data used by a second device to schedule reception of a plurality of segments via an ultra-wideband (UWB) signal, respectively. In some embodiments, one or more operations of block 3504 can be similar to the operations of block 1804 of process 1800. Figure 24

[0182] In some embodiments, blocks 3502 and 3504 can be repeated according to the schemes described with reference to Figure 25 and Figure 18

[0183] At block 3506, the first device can schedule transmission of the plurality of segments via the ultra-wideband signal according to the synchronization data. In some embodiments, one or more operations of block 3306 can be similar to the operations of block 1812 of process 1800. Figure 18

[0184] At block 3508, the first device can transmit the plurality of segments to the second device via the ultra-wideband signal. In some embodiments, each segment of the plurality of segments can be separated in time from other segments of the plurality of segments by at least a predefined time interval. In some embodiments, one or more operations of block 3308 can be similar to the operations of block 1814 of process 1800. Figure 31

[0185] Figure 24 is another simplified flow diagram illustrating signal exchanges according to an interleaved ranging protocol, according to some embodiments. In the interleaved ranging protocol as illustrated in process 3600, Figure 25 In the interleaved ranging protocol as illustrated in process 3600, Figure 26 ​​​​​​to split the UWB fragment exchange time in half. In this case, the TX and RX UWB fragments are interleaved. This interleaved UWB exchange is preceded by a bidirectional NB exchange and followed by a unidirectional or bidirectional timestamp / status NB exchange (see Figure 27 ). In some embodiments, this protocol can enable a significant reduction in total ranging exchange time by enabling both the initiator 3602 and the responder 3604 to transmit respective UWB fragments using the same time interval. It will be appreciated that the transmission and / or reception attempts of the UWB fragments themselves can be conditioned on successful reception of the NB packets. In some embodiments, this can help to optimize power.

[0186] Figure 38 is another simplified flow diagram showing message exchanges according to an interleaved ranging protocol, in accordance with some embodiments. In some embodiments, Figure 39 the message exchanges of the process 3700 can correspond to the protocol depicted with reference to Figure 39 .

[0187] At block 3702 of the process 3700, the first device (e.g., the initiator 3602) can transmit a packet to the second device (e.g., the responder 3604) via a narrowband signal, the packet conveying synchronization data. In some embodiments, one or more operations of block 3702 can be similar to the operations of block 2902 of the process 2900 described with reference to Figure 40 .

[0188] At block 3704, the first device can receive a second packet from the second device, the second packet conveying second synchronization data via a second narrowband signal. In some embodiments, one or more operations of block 3704 can be similar to the operations of block 2904 of the process 2900 described with reference to Figure 21 .

[0189] In some embodiments, blocks 3702 and 3704 can be repeated in accordance with the schemes described with reference to Figure 21 and Figure 21 .

[0190] At block 3706, the first device can transmit a first fragment of a plurality of fragments to the second device via an ultra-wideband signal. In some embodiments, one or more operations of block 3706 can be similar to the operations of block 1814 of the process 1800 described with reference to Figure 41 .

[0191] At block 3708, the first device can receive, from the second device, a first segment of a second plurality of segments. In some embodiments, the first segment of the second plurality of segments can be transmitted via a second ultra-wideband signal. In some embodiments, the first segment of the second plurality of segments is received by the first device within a predefined time interval that defines a time separation between the first segment and a second segment of the plurality of segments. In some embodiments, one or more operations of block 3708 can be similar to operations of block 1818 of FIG. 18. Note that in this case, the individual respective segments from the respective pluralities of segments are interleaved together as they are transmitted / received by the respective devices. Figure 41

[0192] At block 3710, the first device can transmit, to the second device, a second segment of the plurality of segments after completion of the predefined time interval.

[0193] At block 3712, the first device can receive, from the second device, the second segment of the second plurality of segments. It will be appreciated that multiple rounds of interleaved segments can be exchanged between the two devices (e.g., multiple rounds of operations including blocks 3710 and 3712) until the full respective pluralities of segments are exchanged between the devices.

[0194] At block 3714, the first device can receive, from the second device via a narrowband signal, a packet that includes information that can be used to determine a range or a time of flight, the information including at least one of: (I) a round trip time, (II) a turn around time, or (III) a status report. In some embodiments, one or more operations of block 3710 can be similar to operations of block 3110 of FIG. 31. Note that in some cases, the first device can also (and / or alternatively) transmit, via the narrowband signal, a packet that enables the second device to determine ranging information as well, depending on the context. In some embodiments, the operations of block 3714 can be repeated in accordance with the schemes described with reference to Figure 40 Figure 42 and Figure 43 and / or Figure 40 and Figure 41

[0195] Figure 42 ​​​is another simplified block diagram 3800 showing the use of separate wireless systems for initial device discovery and connection setup, according to some embodiments. The diagram 3800 depicts the NB assistance concept extended to include another wireless system that can assist with initial device discovery and connection setup as described herein. In this example, a wireless system (e.g., BLE 3802) can be used for initial coarse alignment of the device before handing over control to the hybrid NB+UWB transceiver 3804. In some embodiments, the BLE 3802 can handle advertising / scanning, coarse synchronization, and / or connection setup. At the same time, the NB subsystem can handle fine synchronization to help (“anchor”) the MMS-UWB (multi-millisecond) transmission. Additionally, the UWB subsystem can more efficiently “harvest” the UWB energy from dedicated slots 3806a-3806c for TOF / AOA estimation.

[0196] Figure 22 is another simplified block diagram 3900 showing the use of separate wireless systems for initial device discovery and connection setup, according to some embodiments. Figure 41 The diagram 3900 illustrates a specific implementation where the additional wireless system (such as BLE 3802) and the HWT are located on separate system-on-chips (SOCs) 3906a-3906b and 3908a-3908b on the same device (device A 3902 or device B 3904, respectively).

[0197] Figure 42 is a simplified block diagram 4000 showing the use of fragmented UWB signaling including multiple partitions of UWB packets, according to some embodiments. The diagram 4000 shows two partitions (two types) of consecutive UWB packet fragments, namely N fragments 4002a-4002n containing CIRTS (e.g., one fragment type) in a first partition, followed by M fragments 4004a-4004m containing a pseudo-random training sequence (PRTS) (e.g., another fragment type) in a second partition. In one advantageous implementation of this partitioned framework structure of fragments, each of the CIRTS fragments 4002a-4002n in the first partition is followed by a PRTS fragment 4004a-4004m, as referenced to FIG. 3. Figure 21The described periodic pulse sequence composition. Meanwhile, each of the segments 4004a-4004m of the second partition is composed of a different sequence of pulses of pseudo-random pulse polarity. Similar to the scrambled timestamp sequence (STS) in IEEE 802.15.4z, the pulse polarity in the PRTS segments 4004a-4004m is pseudo-random and known only to the associated devices in the secure ranging scenario. Specifically, the CIRTS segments 4002a-4002n can be used by the receiving device to efficiently estimate the channel (CIR) estimate and extract the 1st propagation path. Then, the PRTS segments 4004a-4004m can be used by the receiver station to verify (e.g., authenticate) the legitimacy of this 1st path estimate in a secure manner by the CIR obtained in the CIRTS segments 4002a-4002n and the (secret but known) pulse polarity contained in the segments of the PRTS 4004a-4004m. Using Figure 40 the description and nomenclature of possible sequence types in Table 1, the N segments containing the periodic CIRTS sequence can be based on rows 3, 4, 5, and / or 6 in the illustrated table, while the M PRTS segments 4004a-4004m can be based on row 2 in the table shown in Figure 42 .

[0198] Figure 44 is another simplified block diagram 4100 showing the use of a fragmented UWB signaling including multiple partitions of UWB packets according to some embodiments. Figure 44 The diagram 4100 of FIG. 41 shows the fragmented UWB packet implementation from Figure 45 with different partitions. Specifically, the first partition contains CIRTS segments 4102a-4102n (e.g., one segment type), while the second partition contains DATA segments 4104a-4104m (e.g., a different segment type). As previously described, this CIRTS segments 4102a-4102n can be evaluated by the receiver to obtain a CIR and a first path estimate. The DATA segments 4104a-4104m can be used to transmit user payload data 4106. Such user payload data 4106 can include sensor data, e.g., readings from an inertial measurement unit (IMU) or accelerometer module, control / management and status data, or data for audio and / or video purposes such as microphone data or audio and / or video stream data. Note that the DATA segments 4104a-4104m can contain short “pilot” data symbols that are known to both the transmitter and receiver. Such pilot data symbols can help resynchronize and / or refine the channel estimate (CIR) in order to improve the accuracy and performance of the DATA payload detection.

[0199] Figure 45is another simplified block diagram 4200 illustrating use of fragmented UWB signaling including multiple zones of UWB packets according to some embodiments. The diagram 4200 illustrates an example embodiment of a fragmented UWB packet having three zones. In this example, there are N CIRTS fragments 4202a-4202n, followed by M PRTS fragments 4204a-4204m and P DATA fragments 4206a-4206p. Note that N, M and P can be 1, 2, 3 or any other integer; also note that N, M, P can be different from one another.

[0200] Figure 45 is a simplified flowchart illustrating use of fragmented UWB signaling including multiple zones of UWB packets according to some embodiments. In some embodiments, one or more of the operations of the flowchart 4300 can be similar to operations described with reference to Figure 45 , Figure 45 and / or Figure 46 .

[0201] At block 4302, the first device transmits a first packet to the second device via the narrowband signal. In some embodiments, the first packet can include information indicating to the second device a time period for reception of a second packet. In some embodiments, the information included within the first packet can correspond to any suitable information that can be used to communicate synchronization data to the second device, as described herein. For example, this can include information associated with (e.g., included within) a synchronization field and / or a data payload field of the first packet. In some embodiments, the second device can thereby obtain synchronization data (e.g., for scheduling reception of the second packet) based on the information included within the first packet. In some embodiments, one or more operations of block 4302 can be similar to operations described with reference to, for example, block 2206 herein. Figure 46 In some embodiments, the second packet can include a first zone including a first plurality of fragments and a second zone including a second plurality of fragments, whereby respective fragments of each plurality of fragments are transmitted via the UWB signal. In some embodiments, the first zone is associated with CIR estimation and / or first propagation path extraction, and the second zone is associated with security verification of the first propagation path extraction. However, embodiments should not be understood as so limited. For example, as exemplified with respect to Figure 46 the second zone can be associated with a data payload type (e.g., containing video data or audio data). Thus, it should be understood that any suitable type of fragment of the plurality of fragment types (e.g., CIRTS fragments 4202a-4202n, Data fragments 4204a-4204m or PRTS fragments 4206a-4206p) can be used to perform the techniques herein.

[0202] In some embodiments, the second packet can include more than two partitions, as depicted (e.g., partitions associated with particular segment types). In some embodiments, as described with reference to Figure 46 Figure 46 and Figure 47 segment types can be associated with (e.g., correspond to) particular sequence types. For example, a first plurality of segments (e.g., including CIRTS segments 4202a-4202n) can be respectively associated with a periodic sequence type, while a second plurality of segments (e.g., including PRTS segments 4204a-4204m) can be respectively associated with a pseudo-random sequence type. In some embodiments, a first number of the first plurality of segments can be the same or different than a second number of the second plurality of segments (e.g., see Figure 47 , depicting N CIRTS segments 4202a-4202n, M PRTS segments 4204a-4204m, and P Data segments 4206a-4206p). In some embodiments, the first packet can include a security parameter (e.g., one of a plurality of configurable ranging session parameters) indicating a pseudo-random sequence security key (and / or seed or key index or key index offset). In some embodiments, this key or partial key can be shared between only the first device and the second device (e.g., a secret key), and the key information can be distributed between a priori reference key agreed upon between the first device and the second device during connection establishment, and the partial key (or seed or key index or key index offset) can be included in the first packet.

[0203] At block 4304, the first device transmits, via the UWB signal, a first plurality of packets to the second device, respective segments of the first plurality of segments being associated with a first segment type (e.g., CIRTS type for performing CIR estimation).

[0204] At block 4306, the first device transmits, via the UWB signal, a second plurality of packets to the second device, respective segments of the second plurality of segments being associated with a second segment type (e.g., PRTS type). In some embodiments, the second device can authenticate the first propagation path extraction based at least in part on the second plurality of segments, as described herein. In some embodiments, the second device can utilize a pseudo-random sequence security key (e.g., transmitted to the second device as a session parameter at block 4302) to perform this authentication.

[0205] Figure 48 is another simplified block diagram 4400 illustrating techniques by which asymmetric numbers of segments are transmitted between two directions of a link, in accordance with some embodiments. Figure 48 ​diagram 4400 shows one embodiment in which the number of segments used for CIRTS purposes differs between the two directions of the link. Notably, the A-to-B direction uses N AB segments 4402a-4402n, while the B-to-A direction uses N BA segments 4404a-4404n, where N AB and N BA can be the same integer, such as 1, 2, 3, or higher, but can also be different. An asymmetric (unequal) choice for N AB and N BA can be beneficial in scenarios in which one direction of the link is more heavily stressed due to higher antenna efficiency or radio front-end signal level loss at one of the associated devices A or B. Thus, using a higher number of segments can be used to compensate for the asymmetry in the strength (and operating) range of the link. In some embodiments, a symmetric (balanced) link in both directions is beneficial, as the weaker link tends to dominate the overall system performance in a wireless system, thus requiring communication in both directions to extract all the desired amount.

[0206] Figures 1 to 48 is another simplified block diagram 4500 showing the technology by which multiple UWB frequency channels can be made available for segmented transmission, according to some embodiments. ​ diagram 4500 depicts an embodiment in which multiple UWB frequency channels can be advantageously used for segmented transmission. In some embodiments, UWB signaling according to international standards can use a spectral bandwidth of about 500 MHz, and carrier frequencies (center frequencies) such as about 6.5 GHz (so-called UWB channel 5), 8 GHz (so-called UWB channel 9), or 8.5 GHz (UWB channel 10). In ​In the illustration, this can be interpreted as UWB transmissions from station A to station B as part of an NB-assisted fragmented UWB exchange, with three UWB channels used for a total of 3 times N fragments, with N fragments arranged on each of the three channels. The three channels can be referred to as “UCH1” 4502, “UCH2” 4504, and “UCH3” 4506, where each of those labels can be associated with a physical spectrum. In the illustration, UCH1 4502 refers to a 500 MHz channel centered at 8.5 GHz, UCH2 4504 refers to 8 GHz, and UCH3 4506 refers to 6.5 GHz. The fragments transmitted in UCH1 4502, depicted as CIRTS fragments CIRTS(1,1), CIRTS(1,2)... CIRTS(1,N) 4508a-4508n, are at least T_reg_test apart in order to satisfy regulatory emission requirements. Fragments CIRTS(2,1), CIRTS(2,2)... CIRTS(2,N) 4510a-4510n transmitted on channel UCH2 4504 can occur within the same period, as each partition of the wireless spectrum is governed by a separate emission limit. That is, CIRTS(1,1) 4508a and CIRTS(2,1) 4510a (both representing the first fragment in their respective sequence of fragments in channels UCH1 4502 and UCH2 4504, respectively) can occur consecutively very quickly, respectively, if desired. In some embodiments, they can occur simultaneously. In some embodiments, a wireless transceiver can only be able to service one channel at any given time. The same logic applies to fragments transmitted on UCH3 4506 (e.g., 4512a-4512n), which is controlled by its own emission limit, and fragments on that channel can occur within the same test period T_reg_test as fragments transmitted on channels UCH1 4502 or UCH2 4504. Note that transmissions on multiple channels (e.g., as in the example of 3 channels, depicted) can be beneficial for frequency diversity purposes. Due to the real physical constraints of antenna hardware, radiation in certain directions at one frequency channel can be severely attenuated due to antenna nulls, while the same directions can have strong support on another frequency channel. Furthermore, utilizing multiple channels can also be beneficial to effectively increase the bandwidth of the wireless exchange, allowing for better estimation accuracy, such as the range (distance) between devices A and B. While the number of fragments N in each channel can be the same across channels, as in the example, the number of fragments N can be different across channels. ​ transmissions on multiple channels (e.g., as in the example of 3 channels, depicted) can be beneficial for frequency diversity purposes. Due to the real physical constraints of antenna hardware, radiation in certain directions at one frequency channel can be severely attenuated due to antenna nulls, while the same directions can have strong support on another frequency channel. Furthermore, utilizing multiple channels can also be beneficial to effectively increase the bandwidth of the wireless exchange, allowing for better estimation accuracy, such as the range (distance) between devices A and B. While the number of fragments N in each channel can be the same across channels, as in the example, the number of fragments N can be different across channels. ​As shown, these can also be different, e.g., N1 segments for UCH1 4502, N2 segments for UCH2 4504, and N3 segments for UCH3 4506. In some embodiments, the number of channels can be 2, 3, or any suitable number.

[0207] ​ is another simplified block diagram 4600 showing techniques for performing antenna switching to facilitate UWB segmenting transmissions according to some embodiments. ​ The upper portion of the schematic 4600 shows one embodiment in which an antenna switching module and its control during segmenting transmissions can be beneficial. As depicted in the upper portion of the schematic 4600, a UWB subsystem 4602 has a single UWB transmit chain and two UWB receive chains, which are connected to an antenna switching module 4604. In this example embodiment, the latter is also connected to various antennas, four of which are labeled AntO 4606a, Antl 4606b, Ant2 4606c, and Ant3 4606d. In transmit operations, the antenna switching module 4604 allows one of these antennas to be selected or assigned with the single transmit chain of the UWB subsystem 4602 according to antenna switching control signals from a hybrid system control block 4608. In receive operations, the antenna switching module 4604 allows two of the antennas 4606 to be selected to have their signals forwarded to the two receive chains of the UWB subsystem 4602. Note that any number of antennas 4606, 1, 2, 3, 4, or more antennas 4606 can be beneficial, and the UWB subsystem 4602 can provide 1 or more transmit chains and 1, 2, or more receive chains. The purpose of the antenna switching module 4604 is then to select the antennas 4606 for actual transmit and receive operations. Antenna switching can be beneficial to achieve antenna diversity, similar to channel / frequency diversity, which can help overcome antenna nulls or multipath fading effects. It can also be beneficial to angle of departure and angle of arrival estimation techniques. In one embodiment of the invention, the antenna switching technique can be used in conjunction with segmenting UWB transmissions as part of a hybrid NB / UWB wireless system. This is illustrated by means of ​ the lower portion of the schematic 4600. ​Embodiments in the lower portion use N1+N2 CIRTS segments (e.g., 4610a-4610n and 4612a-4612n). Two antenna switching configurations are used, ASC1 and ASC2 during the first N1 segments and the second N2 segments, respectively. For transmission operations, ASC1 and ASC2 can each refer to the selection of one of the 4 antenna elements Ant0 / 1 / 2 / 3 4606a-4606d used for transmission. For example, ASC1 can refer to Ant0 4606a and ASC2 can refer to Ant3 4606d. For reception operations, ASC1 and ASC2 can represent the selection of 2 of the 4 available antennas, such as (Ant0 4606a, Ant2 4606c) and (Ant0 4606a, Ant1 4606b), respectively. During the time period between start time t_start and switch time t_switch, the antenna configuration ASC1 is used, while after time t_switch, the antenna configuration is changed to ASC2. Note that any number of switching configuration intervals are possible, not just the two intervals targeted at ASC1 and ASC2, but also more intervals providing more antenna configurations ASC1, ASC2, ASC3, etc. Also note that in the example embodiments shown in the lower portion, the segments represent CIRTS sequences, while in other embodiments, other segment types such as PRTS or DATA can be used, and different antenna switching intervals can use different segment types. For example, during intervals t_start to t_switch, CIRTS segments can be used, while between t_switch and the end of the transmission, DATA segments can be used. ​ In the example embodiments shown in the lower portion, the segments represent CIRTS sequences, while in other embodiments, other segment types such as PRTS or DATA can be used, and different antenna switching intervals can use different segment types. For example, during intervals t_start to t_switch, CIRTS segments can be used, while between t_switch and the end of the transmission, DATA segments can be used.

[0208] ​ is a simplified block diagram 4700 illustrating techniques for operating a hybrid (UWB / NB) system within an environment including anchor stations and client stations, according to some embodiments. ​diagram 4700 shows an implementation of a hybrid system in a plurality of stations in two device classes - anchor stations and client stations. In some implementations, anchor stations Al, A2,...A10 4702a-4702n represent devices with hybrid system capabilities, which can be fixed devices, possibly mounted on a wall or ceiling, and connected with a permanent power supply such as a regular 110V or 220V mains system. In some implementations, client stations CI, C2,... to C100 4704a-4704n can be mobile battery operated devices such as mobile phones or wrist-worn smartwatches. Anchor stations 4702a-4702n, which can be installed in a home, shopping mall or warehouse, can provide positioning services to client stations 4704a-4704n, which can be in a local area, possibly indoors or outdoors. In this infrastructure type implementation of the invention, anchor stations 4702a-4702n can transmit hybrid signals consisting of NB and fragmented UWB packets in a synchronized manner at certain time instances offset from each other according to the invention. This allows client stations 4704a-4704n to use the NB signals in a listen-only mode to assist in efficient reception of the fragmented UWB transmissions, and to determine their own position in a local geographical map using a three-point positioning technique, assuming the positions of anchor stations 4702a-4702n are known. Alternatively, also using NB assisted fragmented UWB signaling, anchor stations 4702a-4702n can actively and bidirectionally communicate among each other in a point-to-point or point-to-multipoint manner; in this case, client stations 4704a-4704n can listen to these anchor-to-anchor communications and derive their respective positions based on them.

[0209] ​ is another simplified block diagram 4800 showing techniques for performing environmental sensing via UWB fragmentation transmission according to some implementations. ​ diagram 4800 illustrates the use of hybrid NB / UWB signaling for environmental sensing (depth sensing and mapping, DSM) techniques. In this implementation, station A 4802 and station B 4804 perform an exchange of NB and UWB to determine effective CIRs and ranges (distances) as described herein. In addition, while transmitting UWB fragments, particularly for the case of a sequence of CIRTS fragments, each station (station A 4802 and station B 4804) also receives and correlates its own transmissions for channel estimation purposes. The CIRs obtained from A-to-B and B-to-A signaling can be used for "multi-static radar" DSM, while the CIRs obtained from A-to-A and B-to-B "loopback" (LB) operations can be used for "mono-static radar" DSM. The CIRs from mono-static and multi-static measurements (the latter possibly derived from communications among multiple stations A, B, C,... ) can then be interpreted for detecting presence, movement or other environmental parameters or events.

[0210] Exemplary techniques for transmitting a hybrid of NB and UWB wireless signals are described above. Some or all of these systems and methods can be implemented at least in part through architectures such as those shown in one or more of the above-referenced ​ architectures, but need not be implemented through these architectures. It should be understood that any suitable device can perform the techniques disclosed herein. Moreover, various non-limiting examples are described in the foregoing description. For purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the examples. It will be apparent, however, to one skilled in the art that some examples can be practiced without these specific details. In other instances, well-known features are omitted or simplified in order not to obscure the illustrative examples described herein.

[0211] While there can be many implementations of the concepts presented herein, one beneficial option for NB and UWB implementations can be to arrange the radio frequency (RF) operating frequencies for UWB and NB signals to be close to each other. For example, a suitable frequency range for NB signaling can be the Unlicensed National Information Infrastructure (UNII) bands in the 5 and 6 GHz range, including the UNII-3 band from 5.725 GHz to 5.850 GHz or the UNII-5 band from 5.925 GHz to 6.425 GHz. These bands tend to allow for NB transmissions at power levels up to 10 dBm or 20 dBm or more. For the UWB subsystem, typical RF operating frequencies would be the so-called UWB channels 5 and 9 at center frequencies of approximately 6.5 GHz and 8.0 GHz, respectively. A benefit of using NB and UWB frequencies that are close to each other is that it is easier to share antenna hardware between the NB and UWB. Note, however, that another suitable operating range for the NB subsystem is in the 2.4 to 2.5 GHz ISM band (commonly used for ZigBee and Bluetooth and other consumer wireless systems), and a variety of UWB center frequencies from 1 GHz to 10 GHz and above can be used for the hybrid system concept.

[0212] In terms of hardware implementation for the hybrid system concept, it should be noted that the NB and UWB subsystems can reside on the same system on a chip (SOC), which can also be referred to as an integrated circuit (e.g., including suitable processor circuitry). They can also be embodied as separate SOCs, an NB SOC and a UWB SOC, with tight coupling and joint MAC control processing accomplished through direct control signals exchanged between the two SOCs.

[0213] Other preferred and non-limiting implementations or aspects will be set forth in the following numbered clauses:

[0214] Clause 1 : A computer-implemented method comprising: transmitting, by a first device to a second device via a narrowband (NB) signal, a first packet, the first packet including information indicating to the second device a time period for receiving a second packet, the second packet including a first partition and a second partition, the first partition including a first plurality of segments and the second partition including a second plurality of segments, and a respective segment of each plurality of segments being transmitted via an ultra-wideband (UWB) signal; transmitting, by the first device to the second device via the UWB signal, the first plurality of segments, the respective segment of the first plurality of segments being associated with a first segment type; and transmitting, by the first device to the second device via the UWB signal, the second plurality of segments, the respective segment of the second plurality of segments being associated with a second segment type.

[0215] Clause 2: The computer-implemented method of clause 1, wherein the first partition is associated with a channel impulse response (CIR) estimation and a first propagation path extraction, and the second partition is associated with a security verification of the first propagation path extraction.

[0216] Clause 3: The computer-implemented method of any of clauses 1-2, wherein the first segment type of the first plurality of segments corresponds to a periodic sequence, and wherein the second segment type corresponds to a pseudo-random sequence.

[0217] Clause 4: The computer-implemented method of any of clauses 1-3, wherein a first number of the first plurality of segments and a second number of the second plurality of segments are different numbers.

[0218] Clause 5: The computer-implemented method of any of clauses 1-4, wherein the second device authenticates the first propagation path extraction based at least in part on the second plurality of segments.

[0219] Clause 6: The computer-implemented method of any of clauses 1-5, wherein the first packet includes a security parameter, the security parameter indicating a pseudo-random sequence security key shared between only the first device and the second device, and wherein the second device authenticates the first propagation path extraction based at least in part on the security parameter.

[0220] Clause 7: The computer-implemented method of any of clauses 1-6, wherein the second packet is associated with a first ranging round, and wherein a second packet is one of a series of packets respectively divided into including a first partition and a second partition.

[0221] Clause 8: The computer-implemented method of any of clauses 1-6, wherein the second packet is further divided into a third plurality of segments that include a data payload in common association.

[0222] Clause 9: The computer-implemented method of any of clauses 1-8, wherein the data payload includes audio data or video data.

[0223] Clause 10: The computer-implemented method of any of clauses 1-9, wherein the first partition is associated with a channel impulse response (CIR) estimate and the second partition is associated with a data payload.

[0224] Other embodiments of the disclosure can be directed to an apparatus comprising: memory including computer-executable instructions; and one or more processors in communication with the memory and configured to access the memory and execute the computer-executable instructions to perform the method of any of clauses 1-10.

[0225] Other embodiments of the disclosure can be directed to one or more computer- readable storage media comprising computer-executable instructions, which, when executed

[0226] Other embodiments of the disclosure can relate to an apparatus comprising: processor circuitry configured to perform the method of any of clauses 1-10.

[0227] Various embodiments can also be implemented in a wide variety of operating environments, which in some cases can include one or more user computers, computing devices or processing devices which can be used to operate any of a number of applications. User or client devices can include any of a number of general purpose personal computers, such as desktop or laptop computers running a standard operating system, as well as cellular, wireless and handheld devices running mobile software and being able to support a number of networking and messaging protocols. Such a system also can include a number of workstations running any of a variety of commercially-available operating systems and other known applications for purposes such as development and database management. These devices also can include other electronic devices, such as virtual terminals, thin clients, gaming systems and other devices capable of communicating via a network.

[0228] Most embodiments make use of at least one network familiar to those skilled in the art for facilitating communication of any of the various commercial protocols such as TCP / IP, OSI, FTP, UPnP, NFS, CIFS, and AppleTalk, among others. The network can be, for example, an intranet, the Internet, a virtual private network, an extranet, a local area network, a wide area network, a wireless network, a public switched telephone network, an infra-red network, a wireless network, a public switched telephone network, an infra-red network, a wireless network, and any combination thereof.

[0229] In embodiments utilizing a network server, the network server can run any of a variety of server or mid-tier applications, including HTTP servers, FTP servers, CGI servers, data servers, Java servers, and business application servers. One or more server(s) can also be capable of executing programs or scripts in response to requests from user devices, such as by executing one or more applications that can be implemented as one or more scripts in any programming language, such as Java, C, C# or C++, or any scripting language, such as Perl, Python, or TCL, as well as combinations thereof. The server(s) can also include database servers, including without limitation those commercially available from Oracle®, Microsoft®, Sybase®, ® ® ® ® ® and IBM®.

[0230] The environment can include a variety of data stores and other memory and storage media as discussed above. These can reside in a variety of locations, such as on a storage medium local to (and / or resident to) one or more of the computers or remote from any or all of the computers across the network. In a particular set of embodiments, the information can reside in a storage-area network (SAN) familiar to those skilled in the art. Similarly, any necessary files for performing the functions attributed to the computers, servers, or other network devices can be stored locally and / or remotely, as appropriate. Where a system includes computers in the form of servers or other network devices, each such device can include hardware sufficient to operate as attributed to the devices in this context, including aspects for receiving, processing, and communicating information under direction of one or more applications, threads, processes, and / or modules stored thereon. Examples of hardware that can be employed in such computers include computers, servers, and other network devices, which can be of various construction and form, including personal computers, desktop computers, laptop computers, notebooks, netbooks, tablets, smart phones, application-specific circuitry, or other devices of various sizes and performance. Where appropriate, one or more of the computers can be located remotely from the other computers and can be accessed by the various servers as a cloud resource.

[0231] ​​​​Such devices also can include a computer-readable storage media reader, a communications device (e.g., a modem, a

[0232] Non-transitory storage media and computer-readable storage media for containing code or portions of code can include any appropriate media known or used in the art, such as but not limited to, any volatile or non-volatile, removable or non-removable media implemented in any method or technology for storage and / or transmission of information such as computer readable instructions, data structures, program modules, or other data, including RAM, ROM, Electrically Erasable Programmable Read-Only Memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a system device. Based at least in part on the disclosure and teachings provided herein, a person of ordinary skill in the art will appreciate other ways and / or methods to implement the various embodiments. However, computer-readable storage media do not include transitory media such as carrier waves and the like.

[0233] Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. It will be apparent, however, that various modifications and changes can be made thereto without departing from the broader spirit and scope of the disclosure as set forth in the claimed subject matter.

[0234] Other variations are within the spirit of the present disclosure. Thus, while the disclosed technology is susceptible to various modifications and alternative constructions, certain illustrated embodiments thereof are shown in the drawings and have been described above in detail. It should be understood, however, that there is no intent to limit the disclosure to the particular forms disclosed but to the contrary this disclosure is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the appended claims.

[0235] The use of the terms “a” and “an” and “the” and similar referents in the context of describing the disclosed embodiments (especially in the context of the following claims) are to be construed to cover both the singular and the plural, unless otherwise indicated herein or clearly contradicted by context. The terms “comprising,” “having,” “including,” and “containing” are to be construed as open-ended terms (i.e., meaning “including, but not limited to,”) unless otherwise noted. The term “connected” is to be construed as partly or fully inclusive, unless otherwise indicated herein or clearly contradicted by context. The phrase “based on” is to be construed as meaning “based, at least in part, on,” unless otherwise indicated herein or clearly contradicted by context. Unless otherwise stated herein, recitation of numerical ranges by endpoints is merely intended to serve as a shorthand method of referring individually to each number falling within the range. Each numbering endpoint is to be rounded to the nearest whole number, unless otherwise indicated. All methods described herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The use of any and all examples, or exemplary language (e.g., “such as”) provided herein, is intended merely to better illuminate embodiments of the disclosure and does not pose a limitation on the scope of the disclosure unless otherwise claimed. No language in the specification should be construed as indicating any non-claimed element as essential to the practice of the disclosure.

[0236] Unless specifically stated otherwise, the use of certain language or terminology, for example, the phrase “at least one of’ the list “X, Y, and Z,” is construed to cover all of the individual integers of the list and any combination of the individual integers of the list (e.g., X, Y, and / or Z). Accordingly, unless specifically stated otherwise, such

[0237] Preferred embodiments of the present disclosure are described herein, including the best mode known to the inventors for practicing the present disclosure. Variations of those preferred embodiments can become apparent to those of ordinary skill in the art upon reading the foregoing description. The skilled artisan appreciates that such variations are within the scope of this disclosure and the accompanying claims. It is intended to claim each of those potential variations as falling within the scope of the present disclosure. Moreover, unless specifically stated otherwise, it is intended that the present disclosure survive any invalidity of one or more of the appended claims by virtue of 35 U.S.C. § 112, sixth paragraph.

[0238] All references cited herein, including publications, patent applications, and patents, are hereby incorporated by reference as if each individual reference were individually and specifically indicated to be incorporated by reference and clearl set forth in its entirety herein.

[0239] As described above, one aspect of the present technology is the collection and use of data to wirelessly transmit a secure framework for authentication. The present disclosure contemplates that, in some instances, such collected data can include personal identifiable information (PII) data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, twitter ID's, home addresses, or any other identifying or personal information.

[0240] The present disclosure recognizes that the use of such personal information data in the present technology can be used to the benefit of users. For example, the personal information data can be used to obtain access to resources that a user desires to access.

[0241] The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and / or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible by users, and should be updated as the collection and / or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection / sharing should occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, users should have the opportunity to opt in or opt out of certain data collection, sharing, and / or use practices of the entities. Furthermore, users should be able to learn about the collection and use of their personal information data by the entities to which they provide such information. For example, individuals can obtain access to the personal information data maintained by such entities which is relevant to the individual by submitting a request and madeing the steps necessary to verify the requestor's identity.

[0242] Notwithstanding the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and / or software elements can be provided to prevent or block access to such personal information data. For example, in the case of service related to tracking the location of a user (e.g., via a mobile device), the present technology can be configured to allow users to opt- in or opt-out of enabling the collection of personal information data at any time, including but not limited to during an initial set-up process. In addition to providing “opt-in” and “opt-out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information data. For instance, a user can be notified upon download of an application that their personal information data will be accessed and then reminded again just prior to the data being accessed.

[0243] Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a manner that minimizes risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, data de-identification can be used to protect a user’s privacy. De-identification can be facilitated, when appropriate, through removal of certain identifiers (e.g., date of birth, etc.), control of the amount or specificity of data stored (e.g., collecting location data at a city level rather than at a more specific level like a street address), control how data is stored (e.g., aggregating data across users), and / or other methods.

[0244] Thus, while the present disclosure has been broadly categorized as using personal information data to implement one or more variously disclosed embodiments, the present disclosure also contemplates that various embodiments can also be implemented without the need for access to such personal information data. That is, various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of any such personal information data.

Claims

1. A computer-implemented method, comprising: A first packet is transmitted from a first device to a second device via a narrowband (NB) signal. The first packet includes information indicating to the second device a time period for receiving a second packet. The second packet includes a first partition and a second partition. The first partition includes a first plurality of segments and the second partition includes a second plurality of segments. A corresponding segment in each plurality of segments is transmitted via an ultra-wideband (UWB) signal. The first device transmits the first plurality of segments to the second device via the ultra-wideband signal, wherein the corresponding segment among the first plurality of segments is associated with a first segment type; as well as The first device transmits the second plurality of segments to the second device via the ultra-wideband signal, wherein the corresponding segments in the second plurality of segments are associated with a second segment type.

2. The computer-implemented method of claim 1, wherein the first partition is associated with channel impulse response (CIR) estimation and first propagation path extraction, and the second partition is associated with security verification of the first propagation path extraction.

3. The computer-implemented method according to any one of claims 1 to 2, wherein the first segment type of the first plurality of segments corresponds to a periodic sequence, and wherein the second segment type corresponds to a pseudo-random sequence.

4. The computer-implemented method according to any one of claims 1 to 2, wherein the first number of the first plurality of segments and the second number of the second plurality of segments are different numbers.

5. The computer-implemented method of claim 2, wherein the second device authenticates the first propagation path extraction based at least in part on the second plurality of fragments.

6. The computer-implemented method of claim 2, wherein the first group includes a security parameter indicating a pseudo-random sequence security key shared only between the first device and the second device, and wherein the second device authenticates the first propagation path extraction based at least in part on the security parameter.

7. The computer-implemented method according to any one of claims 1 to 2 and 5 to 6, wherein the second group is associated with the first ranging round, and wherein the second group is one of a series of groups that are respectively divided into a first partition and a second partition.

8. The computer-implemented method according to any one of claims 1 to 2 and 5 to 6, wherein the second group is further divided into a third plurality of segments associated with the data payload.

9. The computer-implemented method of claim 8, wherein the data payload includes audio data or video data.

10. The computer-implemented method according to any one of claims 1, 2, 5, 6 and 9, wherein the first partition is associated with channel impulse response (CIR) estimation and the second partition is associated with data payload.

11. A device for communication, comprising: The memory includes computer-executable instructions; as well as One or more processors, the processors communicating with the memory and configured to access the memory and execute the computer-executable instructions to perform the method according to any one of claims 1 to 10.

12. One or more computer-readable storage media, the computer-readable storage medium comprising computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform the method according to any one of claims 1 to 10.

13. A device for communication, comprising: A processor circuit configured to perform the method according to any one of claims 1 to 10.

Images