Sequences for ultra-wideband ranging

Abstract

This disclosure relates to sequences for ultra-wideband (UWB) ranging. Techniques are provided for utilizing a hybrid of UWB and narrowband (NB) signaling to provide more efficient operating range and operational efficiency. For example, a first device may transmit packets to a second device via NB signals, wherein the packets include information indicating time periods for receiving multiple segments, respectively, via UWB signals. The first device may then transmit a first segment of the multiple segments to the second device via the UWB signals, wherein the first segment includes an intermediate base sequence, which is aperiodic and includes a first set of first sequences and a second set of second sequences. In some embodiments, the intermediate base sequence may include at least one gap interval that can be used to identify a signature of the link between the first device and the second device.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Provisional Application No. 63 / 108862, filed November 2, 2020, entitled “TECHNIQUES FOR HYBRIDIZED ULTRA-WIDEBAND AND NARROWBAND SIGNALING,” filed August 13, 2021, entitled “SEQUENCES FOR ULTRA-WIDEBANDRANGING,” the contents of which are incorporated herein by reference. This application also relates to U.S. Patent Application No. 17 / 453165, filed November 1, 2021, entitled “SIGNALING TECHNIQUES USING FRAGMENTED AND MULTI-PARTITIONED UWB PACKETS” (which claims priority to U.S. Provisional Application No. 63 / 229482, filed August 4, 2021, entitled “SIGNALING TECHNIQUES USING FRAGMENTED AND MULTI-PARTITIONED UWB PACKETS”), and U.S. Patent Application No. 17 / 453163, filed November 1, 2021, entitled “ANNOUNCING UWB / NBA-UWB-MMS RANGING ROUNDS VIA NARROWB AND BASED ADVERTISEMENTS” (which claims priority to U.S. Patent Application No. 63 / 229482, filed August 16, 2021, entitled “ANNOUNCING UWB / NBA-UWB-MMS RANGING ROUNDS VIA NARROWB AND BASED ADVERTISEMENTS”). Priority to U.S. Provisional Application No. 63 / 233598, “ROUNDS VIA NARROWBAND BASEDADVERTISEMENTS”. Background Technology

[0003] Wireless devices can be used for a variety of tasks in short-range wireless applications. For example, a wireless device (e.g., a key card) can be configured to automatically unlock the doors of a vehicle (e.g., a car) when the device enters within a certain proximity. In many cases, regulatory rules and / or other technical restrictions can constrain the use of specific types of wireless signaling. These regulatory rules and / or technical restrictions can vary between different types of wireless signaling. For example, regulatory rules governing ultra-wideband (UWB) signaling may differ from those governing narrowband (NB) signaling, at least in part because they can utilize different frequency bands. In some cases, these regulatory rules and / or technical restrictions make it difficult for the system to achieve the required operating range and / or the required operating efficiency. 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 9This 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 12 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.

[0016] Figure 13 This is another simplified block diagram illustrating at least some exemplary techniques for utilizing NB signaling via NB packet format, according to some implementation schemes.

[0017] Figure 14 This is another simplified block diagram illustrating two devices configured to communicate with each other using a mixture of UWB signaling and NB signaling, according to some implementation schemes.

[0018] Figure 15 This is another simplified block diagram of a hybrid wireless transceiver, according to some implementation schemes, which is configured to communicate with another device using a mixture of UWB signaling and NB signaling.

[0019] Figure 16 This is a simplified flowchart illustrating signal exchange between two devices based on some implementation schemes.

[0020] Figure 17 This is another simplified flowchart illustrating signal exchange between two devices based on some implementation schemes.

[0021] Figure 18 This is another simplified flowchart illustrating an exemplary process performed by the initiating device according to some implementation schemes.

[0022] Figure 19 This is another simplified flowchart illustrating an exemplary process performed by the responder's device according to some implementation schemes.

[0023] Figure 20 This is another simplified block diagram illustrating the use of NB signaling to transmit UWB payload data, based on some implementation schemes.

[0024] Figure 21This is another simplified block diagram illustrating an exemplary waveform that may be included in one or more segments transmitted by the device's UWB signaling layer, according to some implementation schemes.

[0025] Figure 22 This is another simplified block diagram illustrating the first part of an exemplary process performed by a device for hybrid signaling, according to some implementation schemes.

[0026] Figure 23 It is based on some implementation schemes shown. Figure 22 Another simplified block diagram of the remainder of the exemplary process.

[0027] Figure 24 This is another simplified flowchart illustrating signal transmission using one or more NB channels according to a bidirectional redundant packet switching protocol, based on some implementation schemes.

[0028] Figure 25 This is another simplified flowchart illustrating message exchange between two devices using one or more NB channels according to a bidirectional redundant packet switching protocol, based on some implementation schemes.

[0029] Figure 26 This is another simplified flowchart illustrating signal transmission using one or more NB channels according to a one-way redundant packet transmission protocol, based on some implementation schemes.

[0030] Figure 27 This is another simplified flowchart illustrating message exchange between two devices using one or more NB channels according to a one-way redundant packet transport protocol, based on some implementation schemes.

[0031] Figure 28 This is another simplified flowchart illustrating signal transmission using a non-interleaved ranging protocol with a known fixed turnaround time, based on some implementation schemes.

[0032] Figure 29 This is another simplified flowchart illustrating message exchange based on a known fixed turnaround time, according to some implementation schemes.

[0033] Figure 30 This is another simplified flowchart illustrating a non-interleaved ranging protocol according to some implementations, which includes NB signal exchange of round-trip time and / or turnaround time after bidirectional exchange of UWB segments.

[0034] Figure 31 This is another simplified flowchart illustrating message switching using NB signals after bidirectional switching of UWB segments, based on some implementation schemes.

[0035] Figure 32This is another simplified flowchart illustrating signal exchange based on a unidirectional NB and non-interleaved UWB ranging protocol, according to some implementation schemes.

[0036] Figure 33 This is another simplified flowchart illustrating message exchange based on a one-way NB and non-interleaved UWB ranging protocol, according to some implementation schemes.

[0037] Figure 34 This is another simplified flowchart illustrating signal exchange according to the beacon protocol, based on some implementation schemes.

[0038] Figure 35 This is another simplified flowchart illustrating message exchange according to the beacon protocol, based on some implementation schemes.

[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 another simplified block diagram illustrating exemplary sequencing technologies that can be used when transmitting one or more UWB fragments, according to some implementation schemes.

[0044] Figure 41 This is another simplified block diagram illustrating another exemplary sequencing technology that can be used when transmitting one or more UWB fragments, according to some implementation schemes.

[0045] Figure 42 This is another simplified block diagram illustrating another exemplary sequencing technology that can be used when transmitting one or more UWB fragments, according to some implementation schemes.

[0046] Figure 43 This is another simplified block diagram illustrating another exemplary sequencing technology that can be used when transmitting one or more UWB fragments, according to some implementation schemes.

[0047] Figure 44This is a simplified flowchart illustrating sequencing technologies that can be used when transmitting one or more UWB fragments, based on some implementation schemes. Detailed Implementation

[0048] In the following description, various examples will be described. For illustrative purposes, many specific configurations and details are presented to provide a thorough understanding of the examples. However, it will also be apparent to those skilled in the art that some examples can be implemented without these specific details. Furthermore, well-known features may be omitted or simplified to avoid confusion with the examples described herein.

[0049] The embodiments disclosed herein provide techniques for utilizing a hybrid of ultra-wideband (UWB) and narrowband (NB) signaling to provide improved operating range and / or operational efficiency when performing wireless communication between devices. For example, the techniques disclosed herein enable a first device to efficiently determine the location (position) of a second device relative to the first device and / or efficiently determine a distance estimate (e.g., range estimate) between the two devices. For illustration, consider an example where the first and second devices are capable of wireless communication. In this example, hybrid signaling may be performed according to a ranging protocol involving bidirectional NB and UWB signaling between the first and second devices. The two devices may first perform an initial phase during which initial device discovery and initial (e.g., “coarse”) synchronization between the two devices may occur. In some examples, this initial phase may be performed by, for example, the wireless system of each device, equipped with a wireless system to transmit wireless signals using Bluetooth Low Energy (BLE). During this initial phase, the wireless system of the first device may schedule the start time (e.g., discrete time) for transmitting at least one packet (e.g., “NB polling” packet) to the second device via NB signals. The first device may also schedule a window (e.g., a time interval) for the first device to subsequently receive a second packet (e.g., an “NB response” packet transmitted via another NB signal) from the second device.

[0050] Following this initial phase, the first device may then transmit scheduled NB polling packets to the second device via the NB signal at the start time of the scheduling, wherein the packets may 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 packets may include a synchronization ("sync") field and a data payload field. The data payload field may include scheduling data (e.g., it may also be referred to as "scheduling information"). The second device may extract one type of synchronization data from the sync field corresponding to time and frequency synchronization information (e.g., T / Fsync information) using existing synchronization and / or signal acquisition techniques. The second device may also extract another type of synchronization data from the data payload field corresponding to the scheduling data using existing demodulation and decoding techniques. The second device may use this synchronization data to schedule and facilitate the reception of multiple data segments, which will then be transmitted from the first device to the second device via UWB signals in the form of short bursts distributed across multiple intervals. In this example, the NB polling scheduling data may also include scheduling information related to the start time of NB response packet transmission, thereby enabling the second device to schedule the transmission of NB response packets to the first device at the NB response start time. The second device can then transmit an NB response packet at the desired start time, wherein the NB response packet conveys second synchronization data, similar to that described above regarding synchronization data from the first device to the second device. The first device can use this second synchronization data to schedule and assist the reception of a second plurality of segments, which can then be transmitted by the second device to the first device via UWB signals distributed across multiple intervals. In this way, the NB signaling layer of each device can assist the corresponding UWB signaling layer in terms of synchronization and other functions. It should be noted that assisting the reception of UWB signals derived from synchronization data conveyed via NB signals may include configuring UWB reception according to the carrier frequency offset and sample frequency offset relative to the respective associated (second or first) device.

[0051] The first device can then schedule the plurality of UWB fragments based on synchronization data previously obtained by the second device from the first device and transmit the plurality of UWB fragments to the second device for reception. In this example, the plurality of UWB data fragments may collectively represent a Channel Impulse Response Training Sequence (CIRTS) of UWB formatted packets. Upon receiving the CIRTS from the first device (e.g., by aggregating these fragments), the second device can use the CIRTS to estimate the Channel Impulse Response (CIR) and / or determine other synchronization information (e.g., time and frequency information, scheduling data, etc.). After a turnaround time interval (in this example, it may be a fixed time interval known to the first device), the second device may then schedule a second plurality of UWB fragments accordingly based on a second synchronization data previously obtained by the first device from the second device's NB transmission and transmit the second plurality of UWB fragments to the first device for reception. The first device can then similarly calculate the CIR estimate and / or obtain other synchronization information. Subsequently, using the calculated CIR information and taking into account (e.g., subtracting) turnaround time, the first device can determine the time of flight (TOF) associated with the line-of-sight (LOS) path between the two devices. Therefore, the first device may then be able to determine its range and / or position relative to the second device. Thus, by utilizing a combination of NB and UWB signaling, the implementation improves operational range and / or efficiency when performing ranging and / or positioning via UWB signaling.

[0052] To further illustrate, consider a scenario where the first device (e.g., the "initiator" device) and the second device (e.g., the "responder" device) each include a hybrid wireless system (e.g., a hybrid transceiver). Using the first device as a representative exemplary device, the hybrid wireless system of the first device may include an ultra-wideband (UWB) subsystem and a narrowband subsystem. Each subsystem may include wireless transmission and reception circuitry and functions for NB and UWB signaling. Furthermore, the two subsystems may be tightly coupled together. For example, the hybrid transceiver may include a shared time base unit, such as a crystal oscillator (XO) and / or clocking and timing devices. The shared time base unit ensures that the NB and UWB subsystems generate signals that are tightly synchronized in time and frequency. The subsystems for a given device may also share a Media Access Control (MAC) function. The MAC function may 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) functions may also operate based on a common time base between the subsystems.

[0053] Additionally, the hybrid transceiver may include a hybrid system controller. The hybrid system controller coordinates the transmission and reception activities of both the NB and UWB subsystems, as well as the information exchange between them. For example, the hybrid system controller may receive time and frequency synchronization information from the NB subsystem. In some implementations, the hybrid system controller may also receive payload data information from the NB subsystem. The hybrid system controller may also schedule data transmission and reception performed by the NB subsystem. The hybrid system controller may also provide time and frequency configuration information to the UWB subsystem. This allows the UWB subsystem receiver to be configured (e.g., synchronized) more precisely based on time and frequency information extracted from NB signaling. Since the NB and UWB subsystems share a time base unit (including any frequency offset relative to the associated device), this configuration information helps to tailor UWB reception for incoming UWB signals (e.g., corresponding to CIR segments), thereby improving receiver efficiency and CIR estimation performance. The hybrid system controller may also use data received from NB signals to schedule UWB transmission or reception activities based on certain transmission / reception parameters (e.g., carrier frequency, UWB bandwidth, etc.). The hybrid system controller can also receive UWB reception information, including synchronization data (e.g., time and frequency configuration information) and CIR information. While the embodiments described herein may refer to individual components of the hybrid wireless transceiver as performing specific operations, the embodiments should not be construed as being limited in this way. For example, the hybrid system controller may reside within one of the subsystems described herein (e.g., NB or UWB). Any suitable operational division between one or more software and / or hardware components may be applicable to performing the embodiments described herein.

[0054] Continuing the explanation above, consider a scenario where a first device and a second device perform a bidirectional exchange of data (e.g., CIRTS segments) between the two devices. As described herein, the two devices can perform a “coarse” initial synchronization. In one example, where the first device operates as the “initiator” and the second device operates as the “responder,” the first device can schedule a start time (e.g., discrete time) for transmitting packets 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 accordingly schedule a window for receiving packets from the first device via the NB signal. It should be understood that in some embodiments, time may be associated with a specific start time (e.g., discrete moments). In some embodiments, time may be associated with time intervals (e.g., windows and / or time slots), depending on the context. In some embodiments, the information from the data exchanged during the initial phase can enable the two devices to align (e.g., clock synchronization) with deviations within approximately the required time increment (e.g., a 1-millisecond (ms) increment) between the clock devices of the two devices (e.g., managed by a corresponding shared time base unit). In some embodiments, the initial phase can also be used to perform initial device discovery and other connection setup operations. In some implementations, this initial phase may be performed for each device by a separate wireless system from the hybrid wireless transceiver. For example, the separate wireless system may utilize the Bluetooth Low Energy (BLE) protocol and / or reside on a separate system-on-a-chip (SOC) device from the hybrid wireless transceiver. In some implementations, the initial phase, including operations such as service announcement / discovery, connection setup, or coarse synchronization, may be performed by the same system performing the operations of the hybrid wireless transceiver described herein, and in some implementations, particularly by the NB subsystem.

[0055] Upon completion of the initial phase, the first (initiating) device may transmit the packet to the second device via the NB signal at the start time of the scheduling. As described herein, the NB packet may include data conveying synchronization data to the second device. For example, the packet may include data such as a preamble, a start-of-frame delimiter, and / or other synchronization fields. In some embodiments, the second device may use the packet data to extract, for example, synchronization data corresponding to time and / or frequency synchronization information (e.g., from the sync field of the packet). In some embodiments, the packet data may be used to extract, for example, other synchronization data corresponding to scheduling information (e.g., from the payload data of the packet). In one example, the frequency synchronization information may correspond to a relative carrier frequency (which may also be referred to as “F sync” information), which may be used to synchronize the crystal oscillator (XO) offsets of the two devices further described herein. In some examples, the F sync information may be used to configure the 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 may use time synchronization information (which may also be referred to as “T sync” information) to “anchor” subsequent UWB exchanges according to the timing devices of the devices further described herein. In some implementations, time and / or frequency information may be extracted, at least in part, based on detected patterns (e.g., expected signal patterns associated with the synchronization header of the packet). As described herein, in some implementations, the synchronization data may also correspond to scheduling information extracted from the packet payload data. This scheduling information, in one example, can be used to schedule the reception of subsequent UWB packet (e.g., and / or fragment) transmissions from another device (e.g., a first device) by a scheduling device (e.g., a second device) from another device (e.g., a first device). It should be understood that the packet payload data may also include other types of information (e.g., asynchronous data, such as status information, control information, etc.).

[0056] It should be understood that different types of synchronization data may be included in transmissions between devices, depending on the context. In one non-limiting example, a first device (e.g., operating as an initiating device) may transmit data conveying (e.g., indicating and / or enabling retrieval) time and frequency synchronization information as well as scheduling information. In this example, a second device may then transmit data conveying only time and / or frequency information to the first device. In another example, the data transmitted to the first device may also include scheduling information. In yet another example, data included within NB packets may not only convey scheduling information for scheduling NB response packets to another device (e.g., a second (responding) device), but also scheduling information for scheduling subsequent UWB response transmissions performed by the second device.

[0057] Continuing the above description, the second device can then acquire and evaluate the synchronization data from the packet. The second device can use this synchronization data to schedule the subsequent reception of multiple segments received from the first device via corresponding UWB signals. As described herein, the packet may also contain scheduling data, which the second device uses to schedule a second start time for transmitting the 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. When the second packet is received during the scheduled window, the first device can acquire (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.

[0058] Moving to the transmission and reception of UWB segments by each device, the first device can schedule the transmission of these segments to the second device. The scheduling of the transmission of these segments can be based on synchronization data transmitted from the first device to the second device via NB signals. The first device can then transmit these segments to the second device. As further described herein, each of these segments can be time-separated from the other segments by at least a predefined time interval (e.g., 1 ms). In one example, these segments can collectively correspond to (e.g., represent) a CIRTS operable to calculate a CIR estimate associated with the wireless propagation path between the first and second devices. It should be understood that because the CIRTS can be divided into multiple 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 transmitted by the first device for segmented UWB transmissions can be higher than the energy of a single UWB transmission when complying with certain regional regulatory constraints governing energy transmission in a given area. Additionally, the operational range for overall UWB transmission can be greater than the operational range that would otherwise be possible when the CIRTS is transmitted as a single data segment or a single UWB packet. This may be partly due to the ability of the device to aggregate energy from multiple segments. In some implementations, as further described herein, these multiple segments may correspond to specific types of segment sequences (e.g., pseudo-random sequences (STS), periodic sequences, Golay sequences). It should also be noted that limiting UWB to a single segment representing a CIRTS (rather than multiple segments) is already advantageous because in conventional UWB transmissions, available transmit energy needs to be shared between the SHR (Sync Header) and the CIRTS, while in hybrid systems, the functionality of the SHR is at least partially delegated to the NB system, thereby reducing the burden on the UWB system for various synchronization tasks.

[0059] While the first device transmits the plurality of segments via a UWB signal, the second device may receive each segment and then subsequently obtain aggregated information from the plurality of segments. For example, the second device may calculate an estimated CIR based on the CIRTS represented within the plurality of segments. In some embodiments, the second device may also obtain other data (e.g., synchronization data, scheduling data, etc.) from the plurality of segments. Similar to the first device, the second device may then schedule the transmission of a second plurality of segments. The transmission of the second plurality of segments (e.g., UWB segments) may be scheduled based on second synchronization data previously obtained by the first device from the second device (e.g., extracted based on the 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 may also (and / or alternatively) be based on synchronization data obtained from one or more of the plurality of segments received from the first device. The second device may then transmit the second plurality of segments to the first device, similar to what has been described above with respect to the plurality of segments transmitted from the first device to the second device. Upon receiving the second plurality of segments, the first device may calculate an estimated CIR based on the CIRTS represented by the second plurality of segments. In some implementations, the first device may also obtain synchronization data or other suitable data from a second or more segments.

[0060] When the first device calculates the estimated CIR based on the second plurality of segments, the first device may further be able to calculate the time-of-flight (TOF) time in part based on the CIR estimate. For example, the first device may determine a round-trip time interval corresponding to the time increment between a first time when the plurality of segments (e.g., the first segment of the plurality of segments) are transmitted to the second device and a second time when the first device receives the second plurality of segments (e.g., the last segment of the second plurality of segments) from the second device. The first device may also determine a turnaround time interval corresponding to the second time increment between a third time when the second device receives the plurality of segments from the first device and a fourth time when the second device transmits the second plurality of segments to the first device. The first device may then subtract the turnaround time interval at the second device from the round-trip time interval to help determine the TOF. In some embodiments, the TOF may represent a distance (e.g., the distance traveled by a corresponding signal across the direct line-of-sight (LOS) path between the two devices) divided by the speed of light, which can be used to estimate distance by the TOF. In some embodiments, the turnaround time interval may be a fixed time interval known in advance by the first device (and / or the second device). In some implementations, the second device may then transmit relevant information (e.g., timestamp information via another NB signal) to the first device, which can be used to determine the turnaround time at the second device and, based on this, to determine the Time of Flight (TOF). Based on determining the TOF between the two devices, the first device may determine the range and / or relative positioning information between the two devices. In some implementations, only the first device may decide to calculate the range / positioning information. In some implementations, both the first and second devices may decide to calculate the range / positioning information. For example, the second device may similarly receive information from the first device via an NB signal that enables it to calculate or utilize the turnaround time interval at the first device and subsequently calculate the TOF / range information between the two devices. In some implementations, if the second device needs to know the TOF, the second device may also obtain the TOF result calculated by the first device as payload data NB transmission.

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

[0062] In some implementations, as described herein, a protocol may be used by a first device (e.g., an initiating device) to determine the flight time interval and / or range based on a fixed turnaround time interval known to the initiating device. In some implementations, after the first device receives multiple segments from the responding device, a second device (e.g., the responding device) may transmit the turnaround time interval (e.g., including timestamps and / or status information) to the initiating device via an NB signal.

[0063] In some implementations, a protocol can be used in which a unidirectional NB exchange is immediately followed by UWB segments in the same direction. This allows multiple responders to participate in ranging activities by responding in a known sequence or random order. In yet another protocol example, an interleaved ranging protocol can be used, in which the initiating and responding devices can transmit individual segments using the same predetermined time intervals. In this example, instead of the initiating device transmitting multiple segments to the responding device and then the responding device transmitting a second set of packets to the initiating device, segments within the corresponding multiple segments can be interleaved. This reduces the total time used to perform ranging between the two devices.

[0064] In some implementations, the protocol can be used to transmit segmented UWB packets, and the specific format of the fragments can achieve one or more advantages (e.g., autocorrelation properties, better interference suppression). Rejection (e.g., and / or reduced cross-correlation between different sequences), resulting in a flatter spectrum for the transmitted waveform (e.g., thus enabling the transmitter to transmit more energy while meeting regulatory transmission requirements), etc. In one example of a particular format, a specific segment of a UWB packet may include an intermediate base sequence. The intermediate base sequence may be aperiodic and may itself include a first set of first sequences and a second set of second sequences, wherein the first sequence is periodic within the first set and the second sequence is periodic within the second set. In this example, a first gap interval may be included between the first and second sets, and a second gap interval may be included after the second set. In some implementations, these gap intervals may be associated with an increased diversity of the “signature” of the link between the respective device pairs (e.g., facilitating better interference suppression). Furthermore, by formatting UWB packets to include fewer (e.g., 1, 2, 3, etc.) intermediate base sequences (e.g., which are aperiodic), while still allowing the constituent sequences within the first and second sets of intermediate base sequences to be periodic respectively, this protocol can help enable the packets to have autocorrelation properties while also resulting in a flatter spectrum for the transmitted waveform.

[0065] The embodiments of this disclosure provide several technical advantages over the prior art. In one example, embodiments of this disclosure enable hybrid wireless systems to perform hybrid signaling, including tightly coordinated UWB signaling and NB signaling. For example, as described herein, the NB subsystem (e.g., the NB signaling layer) of the hybrid wireless system can be used to assist one or more functions of the UWB subsystem (e.g., the UWB signaling layer). These subsystems can be tightly coupled based on a common (e.g., shared) time base and shared MAC functions on a given physical device, as described herein. The one or more functions of the NB signaling layer can include, for example, coordinating time and frequency synchronization between the UWB signaling layers of the respective devices, performing control, management, and / or status signaling between these devices, etc. Meanwhile, the UWB signaling layer can execute short impulse radio bursts distributed over time intervals (e.g., many milliseconds (MMS)). The bursts can represent (e.g., channel impulse response training sequences (CIRTS) / scrambling time series (STS)) segmented UWB transmissions.

[0066] In some implementations, the hybrid wireless system enables the NB signaling layer to be responsible for conveying synchronization data, such as time and frequency synchronization information, for example via the sync header (SHR) of a regular UWB packet. This is more efficient than distributing the SHR across multiple SHR segments via the UWB signaling layer. For example, transmitting multiple SHR segments without knowing the arrival time of each segment in advance can require significant amounts of memory for buffering and / or processing power. Therefore, the amount of memory and / or processing power can be reduced by utilizing the NB signaling layer instead of the regular UWB SHR. Simultaneously, the CIRTS / STS portion of a UWB packet can be segmented according to a UWB segmentation protocol. Receivers of segmented packets can utilize the synchronization data transmitted via NB signaling to allow the receiver to accurately schedule the reception (e.g., arrival time) of subsequent UWB segments. By implementing segmentation of UWB transmissions, implementations can enable receivers of UWB transmissions to achieve higher performance when measuring the propagation channel used to extract geometric and / or positioning metrics such as distance (e.g., range) or angle. For example, the UWB waveform used for a given measurement period can be segmented into short bursts (e.g., segmented multi-millisecond (MMS) signaling) and distributed across multiple regulatory (e.g., transmit) test intervals (e.g., according to regulatory rules for a specific region). The receiver device can utilize the energy “converged” (e.g., aggregated) from the various intervals (e.g., within each short burst) to achieve a more accurate CIR estimation. Based in part on this CIR estimation, estimates of time of flight, range, location (positioning), and / or angle of arrival (AOA) can be determined. Therefore, by utilizing a hybrid wireless system with tightly coordinated NB and UWB signaling, the implementation achieves at least improved operating range and operational efficiency for UWB-based signaling.

[0067] Figure 1 This 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 divided into short bursts of packet segments distributed across multiple regulatory / transmit measurement intervals to increase the energy radiated by the UWB transmitter during each transmission.

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

[0069] Figure 1 and Figure 2 (Further description below) illustrates a scenario with a device equipped with UWB. In Figure 1 In the schematic diagram 100, handheld device 110 communicates with other handheld devices, fixed devices, or Internet of Things (IoT) devices to measure distance or other positioning metrics, such as the apparent orientation of the devices relative to each other. Devices involved in such communication include telephones (e.g., mobile devices 120), tags (e.g., pet tags 160), wireless speakers (e.g., wireless speakers 170a, 170b, and 170c), televisions, monitors, doors (e.g., door lock devices 140), automobiles, home appliances (e.g., smart speakers 130), thermostats (e.g., thermostat control devices 150), desktop and laptop computers, tablets, etc.

[0070] Figure 2 This is another simplified block diagram 200 illustrating exemplary techniques for exchanging wireless messages between UWB-equipped devices (or "stations") according to some implementations. Figure 2 Schematic diagram 200 illustrates how UWB device A 202 and UWB device B 204 can exchange wireless messages with each other over time in the form of wireless packets 206a-c. In the case of impulse radio (IR) UWB, the waveforms exchanged between the devices include, for example... Figure 2 The p1, p2, p3… UWB pulses are shown in the diagram. This can represent, for example, a series of pulses transmitted from B to A in response to a first set of pulses transmitted from device A 202 to device B 204. In some embodiments, IR-UWB can be used to perform the techniques described in this disclosure.

[0071] Figure 3This is another simplified block diagram 300 illustrating at least some exemplary techniques for calculating the Channel Impulse Response (CIR) according to some embodiments. In some embodiments, the technique used by wireless systems such as UWB to determine the mutual range or location of devices is to calculate the Channel Impulse Response (CIR) 306. The CIR 306 can represent the distribution of direct and indirect (reflected) wireless propagation paths between two devices, such as station A 302 and station B 304, each path being characterized by its propagation delay, magnitude, and radio frequency (RF) phase. Due to the large BW of UWB, the CIR can be calculated at a high resolution level in UWB, which in turn enables a more accurate extraction of the line-of-sight (LOS) path and therefore the TOF / range corresponding to the first path in the CIR.

[0072] For example, such as Figure 3 As shown in schematic diagram 300, a pulse PT 308 is transmitted from station A 302 at time t_A1. In some embodiments, for IR-UWB purposes, pulse PT 308 can be considered as representing a series of long pulses. In this example of schematic diagram 300, pulse PT 308 propagates to station B 304 via a series of propagation paths PP1 310a, PP2 310b, 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. After a volume delay “TOF” (Time of Flight) 314 (representing distance divided by the speed of light), the signal traversing the direct (LOS) path PP1 310a arrives at receiving station B 304 at time t_B1 as pulse PR1 314a. Pulses corresponding to the reflected paths PP2 310b, PP3 310c, and PP4 310d arrive later than the direct path as PR2 314b, PR3 314c, and PR4 314d, and their arrival times will depend on the travel distance from station A 302 to station B 304 via one or more reflectors to which each path belongs. Note that PR1 314a, PR2 314b, PR3 314c, and PR4 314d are examples of the channel impulse response (CIR) 306. In some implementations, CIR306 enables the device to determine metrics such as distance d_AB based on TOF (which itself is derived from the first arrival path PR1 314a).

[0073] While UWB can also be used for more traditional wireless transmission purposes such as data payload transmission, its specific advantage lies in CIR 306 estimation for ToF / ranging / positioning. In some implementations, this advantage of UWB may be partly due to its large bandwidth of 500 MHz or more.

[0074] In some implementations, to estimate CIR 306 (e.g., sometimes referred to as “channel detection”), wireless systems including UWB use what is known as a “channel impulse response training sequence” (CIRTS). The CIRTS can be a waveform in the link between the two devices, known to the transmitter (e.g., device A202) and the receiver (e.g., device B204). If the transmitter transmits a waveform (CIRTS1_TX) containing a specific training sequence 1, the wireless propagation channel with its direct and reflected propagation paths can linearly distort the waveform, resulting in a modified waveform CIRTS1_RX that reaches the receiver. Since the receiver is prior to CIRTS1_TX, it can compare the incoming signal CIRTS1_RX with the known sequence CIRTS1_TX. The receiver can then extract the CIR between the transmitter at device A202 and the receiver at device B204 using mathematical algorithms such as correction and other algorithms commonly referred to in the prior art as “channel estimation.”

[0075] Figure 4 This is based on some implementation examples shown for formatting UWB packets (e.g., Figure 2 Another simplified block diagram 400 of at least some exemplary techniques of group 206). Figure 4 An example of a type of UWB packet format, conforming to the international standard for UWB defined in IEEE 802.15.4z, is shown, with its constituent fields and their respective purposes. The Sync header (SHR) 402 at the beginning of the packet consists of a SYNC preamble 404 and a Start-of-Frame Delimiter (SFD) 406. The SHR 402 serves several purposes, including automatic gain control, frequency offset estimation (frequency Sync or F-Sync), timing estimation (T-Sync), initial channel estimation, etc., which are commonly referred to as “acquisition” or “synchronization”. 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 the Channel Impulse Response Training Sequence, or, in the context of 802.15.4z, the Scrambling 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 implementations, 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: the PHY header (PHR) 410 and the payload data (e.g., PHY Service Data Unit (PSDU)) 412. PHR 410 may contain parameters of the PHY header, and the payload may contain appropriate data content. It should be noted that other packet types are defined for UWB, such as those consisting only of SHR 402 and CIRTS / STS 408 (e.g., "no data packet"), which can be used for channel sensing but without any payload data transmission. There are also payload-only packet formats consisting of SHR 402 and the PHR 410 / payload 412 fields, in which case precise and / or secure channel sensing is not required and the primary purpose is data transmission.

[0076] Figure 5 This is another simplified block diagram 500 illustrating at least some exemplary techniques for determining Time of Flight (TOF) according to some implementation schemes. Figure 5 As depicted in diagram 500, the distance between two stations (station A 502 and station B 504) can be determined based on Time-of-Flight (TOF) measurements. In some implementations, station A 502 at time t... A1 The "polling" message (A to B) 506a is transmitted in real time. For example, if station B determines the LOS path based on CIR at t... B1 Arrival time, where t A1 and t B1 The time increment between these points represents the Time of Flight (TOF). The turnaround time T at station B... B,TO Afterwards, the latter at time t B2 The "response" message is transmitted at time t (B to A 506b). The LOS path of the response message is at time t. A2 The time arrives so that TOF can again be on schematic diagram 500 at t A2 and t B2 The form of the difference is visible. This is achieved by measuring the "round trip" time T. A,RT And subtract the turnaround time T B,TO Station A 502 can calculate TOF. In some embodiments, the technique shown in schematic 500 is in the form of a TOF measurement protocol (or “ranging protocol”). In some embodiments, variations may exist where three or more packets (e.g., packet 206) are involved to improve robustness against real-life radio obstacles, such as the crystal oscillator (XO) offset between station A 502 and station B 504. As further described herein, embodiments provide a ranging protocol that utilizes a novel hybrid radio system context.

[0077] Figure 6Figure 600 is another simplified example illustrating the power spectral density associated with measurements of a UWB signal, according to some embodiments. In some embodiments, the techniques described herein can improve the CIRTS and associated CIR estimation steps at the receiver device across a scenario with multiple segment distributions covering multiple regulatory / transmission test intervals, which can increase the radiated energy transmitted for CIRTS. This distribution can also enable improved operating range.

[0078] use Figure 6 To further illustrate this context, schematic 600 illustrates a power spectral density (PSD) 602 for regulatory measurements of UWB signals. While regulatory rules may vary between countries and regulatory territories, in some regions, exemplary UWB transmit limits may require a maximum PSD of -41.3 dB / MHz across the UWB signal bandwidth (e.g., 500 MHz in this example). The PSD 602 ​​shown in this example meets this requirement for all spectral components, some of which reach the limit of -41.3 dBm / MHz. In some implementations, this measurement can be performed using an average (spectrum analyzer scan) time of 1 millisecond (1 ms). This means that for this scenario, the maximum amount of energy that a UWB system can transmit per ms corresponds to approximately 37e-9 joules = 37 nanojoules (nJ) per ms of a 500 MHz bandwidth. This is illustrated by diagram 604 near the bottom of schematic 600. Available energy (up to 37 nJ) can be transmitted in the form of shorter (“dense”, D) or longer (“flat”, F) pulse trains. The power (shown via the y-axis) is correspondingly higher or lower because energy is calculated by multiplying the power by the duration. In some implementations, peak power constraints may exist, governed by UWB regulatory rules for different regions. Therefore, compression to shorter durations can be effective within certain limits and depends on the density of the IR pulses.

[0079] Figure 7 This is another simplified block diagram 700 illustrating at least some exemplary techniques for transmitting data fragments within a UWB framework, according to some implementation schemes. In some implementations, regulatory constraints are considered at least in part by defining a segmented UWB framework, such as... Figure 7 The schematic diagram 700 is shown.

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

[0081] Figure 8 This is another simplified block diagram 800 illustrating at least some exemplary techniques for transmitting data segments associated with a UWB packet type, according to some embodiments. In some embodiments, an exemplary UWB packet format for performing UWB transmission is the format of a dataless packet 801, as shown in diagram 800. See also above Figure 4 In the example of schematic diagram 800, the dataless 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.

[0082] Figure 9 This is another simplified block diagram 900 illustrating at least some exemplary techniques for transmitting data segments over multiple time intervals within a UWB framework, according to some implementation schemes. Figure 9 In schematic diagram 900, a group 902 without data is shown (e.g., similar to...). Figure 8 The dataless packet 801 depicted may include an SHR field 904 and a CIRTS field 906. The dataless packet is divided into an SHR segment 908 and several (e.g., two, in this example) CIRTS segments 910a-b. Each CIRTS segment 910 may be transmitted in a separate regulatory test interval to benefit from the full energy budget of its transmission. In some implementations, keeping these segments short 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.

[0083] like Figure 9In this scenario, if the CIRTS 906 is distributed across many 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 energy can be "converged" from various intervals such as CIRTS segment 1 910a, CIRTS segment 2 910b, etc., which enables more accurate analysis of these segments and / or over longer distances. Meanwhile, high performance in the Sync / Acquisition step is likely desirable to ensure reliable CIR estimation. This is likely because missynchronization during SHR 904 can degrade CIRTS 906 processing. Figure 9 In this configuration, the SHR 904 benefits from the energy of only one interval, thus creating an inherent imbalance between the energy available for the SHR 904 and the energy available for the CIRTS 906. One potential solution is to distribute the SHR 904 across multiple intervals, thereby increasing operational performance. However, this can lead to a less efficient solution. In some implementations, the arrival time of the packet (e.g., fragments of the packet) cannot be known precisely a priori. Therefore, processing multiple SHR fragments 908 in the Sync / Acquisition step may require significant amounts of memory for buffering and / or processing power. This inefficiency may be particularly undesirable for handheld / portable devices or IoT devices. Therefore, embodiments of this disclosure provide techniques for increasing operational efficiency and / or operational range, for example, via hybrid wireless systems, as further described herein.

[0084] Figure 10Figure 1000 is another simplified illustration of the potential advantages and disadvantages of at least some wireless systems utilizing UWB signaling 1002 and / or NB signaling 1004, according to some implementation schemes. In some implementations described herein, a hybrid wireless system is utilized, wherein narrowband (NB) signaling 1004 and ultra-wideband (UWB) signaling 1002 are combined in a certain manner to address the potential challenges presented herein and improve the operational efficiency and / or operational range of the UWB system. In some implementations, the system performing narrowband signaling may include a wireless system with a bandwidth significantly smaller than that of UWB. In some implementations, UWB may have a minimum bandwidth of 500 MHz, therefore NB may refer to a system exhibiting a small fraction of that bandwidth, such as several 100 kHz, 1 MHz, or 10 to 20 MHz. Some non-limiting examples of NB systems would be narrowband GFSK (Gaussian Frequency Shift Keying) or DPSK (Differential Phase Shift Keying) signaling, such as that used in industry standards like ZigBee or Thread, or in IEEE 802.15.4 O-QPSK (Offset Quadrature Phase Shift Keying Format). Narrower-band modes in wireless local area networks (WLANs), such as IEEE 802.11 modes spanning 20MHz or 40MHz spectrum bandwidth, can also be classified as NB signaling in the context of this disclosure because they have significantly lower bandwidths than UWB and tend to operate in different spectrums. In some implementations, they are also governed by a different set of regulatory constraints than UWB.

[0085] In more detail, go to Figure 10 Previously, and to provide additional context related to regulatory constraints and bandwidth considerations, international regulatory rules governing UWB deployment and associated radiated emissions could define low emission limits for UWB devices, as these often operate in frequency bands below 10 GHz (primarily for commercial or military operations involving point-to-point or satellite links, radar, or other protected applications). Therefore, UWB emissions could be delegated to operate at spurious emission levels permitted by other electronic devices (e.g., mobile devices, home appliances, etc.) without interfering with such licensed use. Transmission power for UWB can be limited on average to -14 dBm in many regions.

[0086] In contrast, there are several narrower-band systems and associated regulatory rules that have significantly more lenient emission limits because they operate in bands intended for such unlicensed use. The 2.4 GHz to 2.5 GHz band, the so-called ISM (Industrial, Scientific, Medical) band, is a prime example of a band suitable for notebook applications such as 1 MHz or 2 MHz wide Bluetooth (BT) or ZigBee / Thread transmissions, or wireless local area networks (WLANs) with bandwidths of 20 MHz or 40 MHz. The 2.4 GHz to 2.5 GHz band is an example of a band available in most regulated areas worldwide. Other spectrum similar to the ISM exists, including the 5.725 GHz to 5.875 GHz band in many countries. Other spectrum, including much of the 5 GHz to 6 GHz band, is also generally open to various unlicensed, non-UWB uses under certain conditions. The transmission power (radiated levels) of these more notebook systems are typically in the 10 dBm, 20 dBm, or even 30 dBm range.

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

[0088] Now go to more details Figure 10Schematic diagram 1000 illustrates a comparison of the advantages and disadvantages of UWB and narrowband (NB) wireless systems from the perspective of a wireless system implementer. UWB signaling 1002 benefits from a large bandwidth of at least 500 MHz, which is highly advantageous for high-resolution CIR measurements, which in turn can be used for precise positioning and ranging, as outlined above. The wide bandwidth also benefits from high-rate data transmission. One of the challenges associated with the larger UWB bandwidth is the increased complexity required, such as higher analog-to-digital converter (ADC) sample rates and associated signal processing work, as well as increased analog and digital power consumption. As explained above, UWB regulatory rules also impose significant constraints on permissible transmissions, making 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 highly resilient to interference, especially when operating in a frequency-hopping manner. NB systems also benefit from significantly larger transmission limits when operating in spectrum designated for NB / ISM use. However, NB systems are not equally suitable for high-resolution CIR estimation (ranging / sensing), partly due to inherently limited bandwidth and therefore limited resolvability of multipath propagation channels.

[0089] Figure 11 This is another simplified block diagram 1100 illustrating at least some exemplary techniques for utilizing a mixture of UWB signaling and NB signaling, according to some implementation schemes. Figure 11 In schematic diagram 1100, a portion of the transmission of a dataless packet 1102 via hybrid signaling is shown. In this case, the Sync / Acquisition (SHR) portion 1104 of the UWB packet is replaced by the NB packet 1108, while CIRTS 1106 continues to use UWB signaling. The NB packet 1108 is transmitted in the band suitable for NB operation, and the UWB CIRTS 1106 is transmitted in the band suitable for UWB operation. Although in schematic diagram 1100, the NB packet 1108 and UWB CIRTS 1106 occur sequentially (continuously) in time, they can also occur simultaneously in different implementations. It should be noted that each of these transmissions will be subject to the regulatory rules governing NB and UWB transmissions respectively.

[0090] In some implementations, this NB / UWB hybrid architecture offers certain benefits, which can be achieved by utilizing devices operating according to the embodiments described herein. In some implementations, the hybrid packet architecture enables these devices to address the challenges described above with respect to packet formats, such as those with segmented CIRTS (e.g., see...). Figure 9 This is in Figure 12 As shown in the image.

[0091] Figure 12This is another simplified block diagram 1200 illustrating at least some exemplary techniques for utilizing a mixture of UWB signaling and NB signaling, according to some implementation schemes. Figure 12 In schematic diagram 1200, the function of SHR 1202 is taken over by NB packet 1204 (e.g., via NB signal transmission), and CIRTS 1206 is divided into multiple (here, N) segments 1208a-n. Although segments 1208 can be transmitted at the beginning of a predefined time interval, the implementation should not be construed as being limited in this way. For example, in Figure 12 In the illustration, the transmission of segment N 1208n deviates slightly from a specific time interval (e.g., the T_test_reg interval, as relative to...). Figure 9 The starting point (described and shown). In some embodiments, the initiating and responding devices may transmit configuration information so that the receiving device (e.g., the responding device) can know in advance the parameters of when the segment will be transmitted. This configuration information may be transmitted via NB signals. Furthermore, although not in Figure 12 As shown, but it should be noted that segmented UWB transmissions occurring in the context of a hybrid NB / UWB system may carry more than just CIRTS data. This can be based on... Figure 4 The "Data Fields" (PHR and Payload / PSDU) in the configuration allocate groupings containing the data payload to replace some CIRTS fragments 1208a-n with data payload fragments. It should also be noted that the hybrid system concept is beneficial for containing a single UWB fragment (N=1, see [link]). Figure 11 UWB transmission and is beneficial for containing multiple UWB segments (N>1, see [link]). Figure 12 UWB transmission is possible, and implementations with N=1 and N>1 are also possible.

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

[0093] It should be understood that, such as Figure 12 or Figure 9The grouping fields are divided into segments for functional purposes. For example, these segments are not necessarily related to the initial non-segmented fields. For example, concatenation is not necessary. Figure 12 and / or Figure 9 The CIRTS segment in the packet receives the initial unsegmented CIRTS field. Therefore, the segmented fields represent alternatives to the initial packet fields for desired functions, such as channel (CIR) estimation in terms of the segmented CIRTS packet structure. As described herein, in some embodiments, the NB packet may include a synchronization field (e.g., within the packet header) and / or a data payload field. In some embodiments, the synchronization field can be used to convey synchronization data. For example, (e.g., during a scheduled window) a receiver device receiving the NB packet can detect a known signaling pattern between the transmitter and receiver devices. In some embodiments, this signaling pattern may be associated with the sync field of the NB packet (e.g., the synchronization header). Upon detection of this pattern, the receiver device may be able to extract the synchronization data in the form of time and frequency information, as described herein. In some embodiments, the receiver device may also extract the 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 subsequent reception of one or more UWB segments.

[0094] Figure 14 This is another simplified block diagram 1400 illustrating two devices configured to communicate with each other using a mixture of UWB signaling and NB signaling, according to some implementation schemes. Figure 14 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. Specifically, each device (1402 and 1404) has a hybrid wireless transceiver (HWT) 1406a or 1406b, which includes an NB subsystem 1408a or 1408b and a UWB subsystem 1410a or 1410b tightly coupled to each other in each respective device, as further described herein. As part of the communication between devices A and B, specifically as previously described by Figure 11 and Figure 12 The diagram illustrates the "division of labor" between NB signaling and UWB signaling. NB subsystem 1408a of device A 1402 can directly communicate with NB subsystem 1408b of device B 1404, and UWB subsystem 1410a of device A 1402 can directly communicate with UWB subsystem 1410b of device B 1404. Figure 14In the diagram, the NB subsystems 1408a-b and UWB subsystems 1410a-b in each device are shown as having their own physical antennas 1412a-b and 1414a-b (e.g., including, for example, a first antenna 1412a of the narrowband system 1408a and a second antenna 1414a of the UWB subsystem 1410a). However, it should be understood that a single shared antenna covering both NB operation and UWB operation may be a suitable implementation, and multi-antenna solutions may be used for such advanced signal processing schemes as antenna diversity, spatial multiplexing, or transmit or receive beamforming.

[0095] Figure 15 This is another simplified block diagram 1500 of a hybrid wireless transceiver 1502 configured to communicate with another device using a mixture of UWB signaling and NB signaling, according to some implementations. Figure 15 Schematic diagram 1500 provides further details of the HWT 1502 in each device and illustrates the details and functional components of the aforementioned tight coupling between the NB subsystem 1504 and UWB subsystem 1506 in the HWT 1502. Each such transceiver includes an NB subsystem 1504 and a UWB subsystem 1506, each containing wireless transmit and receive circuitry and functions for NB and UWB signaling, respectively. The HWT 1502 is also equipped with a shared time base 1508 (e.g., a module or unit) consisting of a crystal oscillator (XO) and any associated clocking and timing devices. The shared time base 1508 enables the NB subsystem 1504 and UWB subsystem 1506 to form signals that are tightly synchronized in time and frequency. That is, if the NB signal operates on the shared time base and has a certain clock frequency and / or carrier frequency defect (measured in parts per million [ppm] offset), the UWB signal in the same HWT 1502 can exhibit the same reference defect in ppm. Since the transmitting and receiving elements of the NB subsystem 1504 and UWB subsystem 1506 of the device can operate on the same shared time base 1508, the clock / carrier offset (in [ppm]) of the NB Tx (NB signal transmission), NB Rx (NB signal reception), UWB Tx (UWB signal transmission), and UWB Rx (UWB reception) circuits can be substantially similar (e.g., identical).

[0096] In addition, such as Figure 15As depicted, a joint controller (hybrid system controller (or control)) 1510 exists to manage the transmission and reception activities of the NB subsystem 1504 and the UWB subsystem 1506, as well as the information exchange 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 first device's subsystem. In some embodiments, the hybrid system controller 1510 can coordinate information exchange between the narrowband subsystem of the first device and the ultra-wideband subsystem of the same (first) device. In some examples, the control block (e.g., the hybrid system controller 1510) can receive time and frequency synchronization (“T and F Sync” or “synchronization data”) information from the NB subsystem. F Sync includes information related to the ppm offset estimated by the NB relative to the associated device. T Sync includes information related to 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 Rx data are collectively referred to as “NB-Rx-Info” herein. The control block also schedules the transmissions and receptions performed by the NB subsystem 1504, which may include certain Tx (transmit) / Rx (receive) parameters utilized by the NB subsystem 1504 and possibly payload Tx data.

[0097] The control block also provides time and frequency (T and F) configuration information to the UWB subsystem 1506. This helps to more accurately configure the UWB receiver based on the T and F information extracted from the NB signaling. Since the NB subsystem 1504 and UWB subsystem 1506 share a time base 1508 (including any frequency offset relative to associated equipment), this configuration helps to tailor UWB reception for incoming UWB signals and maximize the performance of CIR estimation based on CIRTS segments. The control block also uses NB Rx-Info to schedule UWB Tx and Rx activities based on certain Tx / Rx parameters, such as carrier frequency or UWB bandwidth. Subsequently, the control block also receives UWB-Rx-Info, which includes synchronization (time / frequency Sync) and CIR information.

[0098] Figure 16 This is a simplified flowchart 1600 illustrating signal exchange between two devices according to some implementation schemes. Figure 16 Schematic diagram 1600 illustrates the use of the methods outlined herein (e.g., referring to the above). Figure 14 and Figure 15The diagram illustrates the signaling and control flow of the exchange between two associated HWTs in the HWT structure of device A 1602 and device B 1604. Dashed arrows represent wireless exchanges between device A 1602 and device B 1604, while solid arrows represent signals exchanged within each HWT (in either device A 1602 or device B 1604). Note that control blocks are not explicitly shown in the diagram for clarity. The NB subsystem 1606 in device A 1602 transmits the NB packet “NB-A to B” 1610 to the NB subsystem 1612 in device B 1602. The latter extracts T and F Sync information (e.g., which may also 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 segments from device A 1602, as further described below. Device B1604's NB subsystem 1612 responds with its own NB packet "NB-B to A" 1616 returning to device A1602. Device A then extracts T and F Sync information from this NB packet and provides this information to its local UWB subsystem 1618 for later use. Subsequently, UWB subsystem 1618 in device A1602 sends a UWB transmission "UWB-A to B" 1620 (specifically CIRTS or a series of CIRTS fragments) to UWB subsystem 1614 in device B1604. As described above, device B1604 may be able to effectively determine when a UWB transmission from device A1602 is expected, in part, based 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 many ppm offset it will have. This understanding can be used to minimize signaling processing workload and maximize the performance of the receive algorithm and associated receive circuitry. Device B 1604 then transmits the UWB response “UWB-B to A” 1622, which device A 1602 can purposefully receive with greater efficiency and accuracy based on the T and F Sync information obtained during the reception of the “NB-B to A” 1616 packet. In some embodiments, according to... Figure 5 Swapping “UWB-A to B” 1620 and “UWB-B to A” 1622 can be used for TOF measurement.

[0099] In some implementations, the T and F synchronization information extracted from the corresponding NB signal can be of high quality because NB signaling is subject to less stringent transmission rules. Therefore, the signal-to-noise ratio (SNR) at the receiver side of the NB transmission can be higher, allowing for more efficient and accurate acquisition. Compared to the UWB subsystem, T and F processing in the NB subsystem is still less complex and less power-intensive, at least because the sample rate is generally lower. Meanwhile, “NB-assisted” reception of 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 functions. This “division of labor” between the NB and UWB subsystems achieves improved operating range and efficiency when compared to other UWB systems.

[0100] It should be understood that although various modules (e.g., components and / or associated functions) are described as separate from other modules, the implementation scheme should not be construed as being subject to such limitations. For example, Figure 15 Hybrid system controllers are depicted as modules separate from the shared time base unit, each separate from both the NB subsystem and the UWB subsystem. However, in some embodiments, the shared time base module and / or hybrid system control module may reside within one of these subsystems (NB or UWB). In this case, the corresponding other subsystems can benefit from control and time base functions as auxiliary or proxy systems (e.g., delegated and / or subordinate systems). In any case, the different distribution and / or aggregation of characteristics among the different modules can enable hybrid signaling to be executed, as described in the embodiments herein. It should also be understood that... Figure 16 and Figure 17 The signal switching illustrated (described further below) demonstrates a specific type of signal switching in a hybrid wireless system consisting of NB and UWB subsystems. Other types of signal switching 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 utilizing devices that respectively include HWTs (e.g., initiating and responding devices).

[0101] Figure 17 This is another simplified flowchart 1700 illustrating signal exchange between two devices according to some implementation schemes. Figure 17 Schematic diagram 1700 shows devices A and B (e.g., Figure 16 A more detailed schematic diagram of the exemplary signal flow between and within the HWT in devices A (1602) and B (1604). Additionally, Figure 18 and Figure 19A flowchart illustrating the processing steps performed by the respective devices is shown, where device A 1602 is referred to as the "initiator" device (or "first device") and device B 1604 is referred to as the "responder" device (or "second device"). Therefore, a description of the processing steps performed by each device can be found in [reference needed]. Figure 17 This is for further explanation of the signal exchange process. It should be understood that in some embodiments, the initiating device may alternatively operate as a responding device, and similarly, the responding device may alternatively operate as an initiating device, depending on the context.

[0102] For more details, please refer to... Figure 18 The process described in process 1800 involves the processing steps of device A (e.g., device A 1602). At block 1802, the first device may schedule the NB-Tx start time and NB-Rx window. In some embodiments, the operation of this block may be performed by a wireless system of the first device, separate from the HWT. For example, the wireless system may utilize the Bluetooth / BLE protocol. In some embodiments, the operation of this block may be performed within the initial phase of process 1800. The wireless system may be responsible for one or more operations in the initial phase, including processing announcements and / or scans (e.g., device discovery), performing “coarse synchronization” with responding device B (e.g., device B 1604), and / or performing other connection setup steps with device B 1604 (e.g., the second device). As further described herein, in some embodiments, a separate wireless system may be responsible for transmitting NB control information, including, for example, what channels and / or how many hopping channels will be used for NB signaling. In some embodiments, a start time (e.g., discrete time) may be scheduled for transmitting NB polling packets to the second device, and a time window may be scheduled for receiving NB response packets from the second device. In some implementations, coarse synchronization enables the corresponding timing devices of these devices to synchronize to each other within approximately 1ms increments. This initial coarse synchronization enables subsequent “fine” synchronization via the switching of NB signals, as described further below.

[0103] At box 1804, the first device can poll NB packets via a narrowband signal at the start time of scheduling (in Figure 17 The data (described as NB-Tx A to B 1702) is transmitted to device B 1604. Polling packets can convey synchronization data (e.g., time and frequency synchronization data), which the second device can then use to schedule the reception of multiple segments, respectively, via the ultra-wideband signal.

[0104] At box 1806, the first device may wait for an NB response packet, which may be expected to be received by the first device from the second device during a scheduled window (e.g., a time interval).

[0105] At box 1808, the first device can receive NB response packets (in Figure 17 This is described as NB-Rx B to A 1704. For example, the first device may initiate the reception of NB response packets via narrowband signals during a scheduled window.

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

[0107] At block 1812, the first device can schedule the transmission of the plurality of segments (UWB-Tx segments 1706a-n). In some embodiments, this scheduling can be based on synchronization data transmitted to the second device and obtained by the second device from the first device to the second device via NB transmission (e.g., at block 1804), which the second device can then use to schedule and facilitate the reception of the plurality of segments 1706a-n.

[0108] At box 1814, the first device can poll the UWB into multiple fragments (in Figure 17 The signal is transmitted to a second device in the form of UWB-TxA to B-1 ... UWB-Tx A to BN 1706a-n. As described herein, each of these multiple segments 1706a-n may be temporally separated from the other segments 1706a-n by at least a predefined time interval. In some embodiments, this time interval may be determined in part based on regional regulatory rules governing the signal transmission.

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

[0110] At box 1818, the first device can receive a second plurality of segments from the second device (in Figure 17 It is described as UWB-Rx B to A-1 ... UWB-Rx B to AN 1708a-n).

[0111] At box 1820, the first device can obtain aggregated UWB-Rx-Info from a second plurality of fragments. In some implementations, this may include synchronization data and / or other data that can be used to determine the CIR (e.g., a CIR estimate). As stated herein (e.g., relative to...). Figure 3As described herein, the CIR estimate can be associated with the LOS path between the first and second devices. As described herein, the CIR can be used to determine the TOF interval, thereby enabling ranging and / or positioning that can 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 the time interval between the time when the second device receives the plurality of segments and the time when the second device transmits a second plurality of segments to the first device (see [link to documentation]). Figure 5 In some embodiments, the first device may know the turnaround time interval in advance (e.g., a fixed time interval). In some embodiments, the first device may not know the turnaround time interval in advance and may subsequently receive the NB signal from the second device that transmits the information. See, for example, further described herein. Figure 30 In any case, the first device can calculate the TOF by taking into account (e.g., subtracting) the turnaround time from the TOF flight, such as relative to... Figure 5 As stated above.

[0112] As introduced above, Figure 19 This is another simplified flowchart illustrating an exemplary process performed by the responder's device according to some implementation schemes. Figure 18 The description of the initiating device is similar. Figure 19 A description of the processing steps performed by the responder's device can be found in [reference]. Figure 17 (For example, where device B 1604 operates as the responding device) to further illustrate the signal exchange process. Note that... Figure 19 The processing steps can correspond to Figure 18 The same steps as the processing steps (e.g., from the perspective of the responder device).

[0113] For more details, please refer to... Figure 19 The process described in process 1900 involves the processing steps of device B 1602 (which may be referred to as the "second device"), where, at block 1902, the second device can schedule NB-Rx time. In some embodiments, the operation of block 1902 may be similar to the operation of block 1802. For example, the wireless system of the second device may perform the same operations as the first device (e.g., Figure 17 and Figure 18 Coarse synchronization of the initiating device (A 1602).

[0114] At box 1904, the second device may wait for NB polling packets from the first device. For example, NB polling packets may have already been transmitted at box 1804 of process 1800.

[0115] At frame 1906, the second device can receive NB polling packets from the first device (in... Figure 17 It is depicted as NB-Rx A to B 1710.

[0116] At box 1908, the second device may obtain NB-Rx-Info from NB polling packets. As described herein, this may 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 facilitate the reception of multiple segments via UWB signals, which are subsequently received by the second device from the first device. In some embodiments, NB-Rx-Info may also contain data for scheduling the transmission of NB response packets (e.g., at a second start time). In some embodiments, data from NB-Rx-Info may be used for other purposes (e.g., status reporting, etc.).

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

[0118] At box 1912, the second device may, for example, transmit the NB response packet to the first device at a previously scheduled second start time (in...). Figure 17 It is depicted as NB-Tx B to A 1712.

[0119] At box 1914, the second device can schedule and configure the UWB receiver (e.g., UWB subsystem) for the UWB-Rx reception of the multiple segments based on the synchronization data received at box 1908. Here, NB-Rx-Info can also be used to configure the UWB receiver for the reception of the UWB signal before the reception of the UWB signal, specifically for one or more of the corrections for carrier frequency offset, sampling frequency offset, carrier phase, and sample phase.

[0120] At frame 1916, the second device can receive UWB segments (in... Figure 17 These UWB fragments are depicted as UWB-Rx A to B-1 ... UWB-Rx A to BN 1714a-n). Figure 18 The UWB polling packet transmitted at frame 1814.

[0121] At box 1918, the second device can obtain the aggregated UWB-Rx-Info. In some implementations, the operation of this box may be similar to that of box 1820. In this case, the second device can obtain synchronization data and / or other data that can be used to determine the CIR.

[0122] At box 1920, the second device can schedule, configure, and transmit UWB-Tx response fragments (in... Figure 17The data is depicted as UWB-Tx B to A-1 ... UWB-Tx B to AN 1716a-n. In some embodiments, a response segment may correspond to multiple segments (e.g., a second plurality of segments received by the first device from the second device at block 1818 in process 1800). In some embodiments, scheduling the transmission of these multiple segments may be based in part on NB-Rx-Info (e.g., obtained at block 1908) and / or UWB-Rx-Info (e.g., obtained at block 1918, including UWB time / frequency synchronization data, CIR, etc.). In some embodiments, the second device may also be able to perform ranging and / or positioning, similar to that described relative to the first device. For example, the second device may determine turnaround time and / or timestamp information that enables it to determine TOF / range information (see further description herein). Figure 28 Option 2).

[0123] In some implementation schemes, relative to Figure 17 , Figure 18 and Figure 19 In some implementations, the number of UWB segments in the forward (A to B "polling") direction can be the same as the number of UWB segments in the reverse (B to A "response") direction, i.e., N. In some implementations, the number of segments for the forward and reverse directions can be different, and can be given as Nf and Nr for the forward and reverse directions, respectively.

[0124] Figure 20 This is another simplified block diagram 2000 illustrating the use of NB signaling to transmit UWB payload data according to some implementation schemes. Diagram 2000 depicts, for example, some standards-based UWB packet formats (see, for example, [link to relevant documentation]). Figure 4 The implementation of SHR 2004, which is applicable and beneficial to UWB payload data 2002, is connected when processed by the NB signaling layer. In some implementations, the NB subsystems with their associated signaling can facilitate the coordination of devices A and B for various management and maintenance purposes, such as the mutual transmission of status information, as further described herein. In some implementations, the payload data of UWB packets 2006 can also be transmitted via multiple segments, similar to that described with reference to the transmission of CIRTS via UWB segments.

[0125] Figure 21 This is another simplified block diagram 2100 illustrating an exemplary waveform that may be contained in one or more segments transmitted by the device's UWB signaling layer, according to some implementation schemes. Figure 21Schematic diagram 2100 illustrates details of the IR waveforms contained in each CIRTS segment 2102a-n used in the UWB signaling layer. Specifically, it 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 diagram, the pulse polarity sequence used to represent CIRTS is based on a sequence from a cryptographically secure pseudo-random generator (CSPRNG) used for the STS portion of the packet. The case where the same CSPRNG type sequence "R" is used for each segment (e.g., segment 2102) is shown as follows. Figure 21 Row 1 of the table shows the implementation scheme for determining the IR pulse polarity of each segment using different CSPRNG polarity sequences (“R1”, “R2”, etc.). Row 3 shows the implementation scheme for a given CIRTS segment 2102 consisting of a periodically repeating short sequence, i.e., the concept of a traditional ternary Ipatov preamble sequence used in IEEE 802.15.4 UWB. It should be noted that this periodic sequence “E” can be an Ipatov sequence or another periodic sequence in which each CIRTS segment 2102 consists of a series (periodic repetition) 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”. A specific embodiment using Gray sequences uses multiple Gray pairs for each segment 2102, wherein all pairs in a given segment are based on the same pair, such that the segment 2102 contains a periodic sequence, each period of which is given by the same Gray pair. In this latter embodiment, similarly, these segments 2102a-n can utilize the same periodic sequence or Gray-based periodic sequences that vary from segment to segment.

[0126] 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.

[0127] 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.

[0128] 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.

[0129] 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 a device may operate as both an initiating (device) and / or a responding (device), depending on the context. Thus, for example, one or more operations of process 2200 may also be applicable (e.g., similarly) to the first device operating as a responding device.

[0130] 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.

[0131] 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.

[0132] 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.

[0133] 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.

[0134] 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.

[0135] 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.

[0136] continue Figure 23In 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 of the plurality of segments can be time-separated from at least one other 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 Figure 18 The operation of box 1814.

[0137] At block 2216, the first device may schedule the 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 may be similar to Figure 18 Operation of box 1816.

[0138] At block 2218, 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 2218 may be similar to... Figure 18 The operation of box 1818.

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

[0140] Figure 24 This is another simplified flowchart 2400 illustrating signal transmission using one or more NB channels according to a bidirectional redundant packet switching protocol, based on some implementation schemes. Combined use of redundant / repeated NB packet switching (e.g., refer to example...) Figure 18 Frame 1804 and / or Figure 19 The box 1912) and pseudo-random channel hopping sequences can improve reliability against interference and / or multipath fading. Figure 24Schematic diagram 2400 depicts an example of this scheme with triple redundant transmission using a pseudo-random channel. The term "channel" here refers to a specific location in the radio spectrum where the NB is transmitted, such as a carrier frequency in GHz (e.g., 2.450 GHz, 5.806 GHz, or 5.912 GHz), around which the NB signal is centered with its specific spectral bandwidth (e.g., 1 MHz, 2 MHz, or several hundred kHz). Some channels may be congested by other wireless users or suffer from signal fading common in multipath environments, and "hopping" on the channel helps reduce packet loss caused by these phenomena. Initiator 2402 (e.g., one of the initiator devices described herein) initiates a first message within an initiation packet, and responder 2404 attempts to receive that first message. In some implementations, the scheme can be further optimized to save power by using the following rules: (a) if the initiator 2402 receives any of (2), (4), and (6), the remaining portion of the NB exchange can be skipped; (b) the responder 2404 should always listen for (1), (3), and (5), but only transmit (2), (4), and / or (6) if its immediate preceding reception is successful. This scheme can be called bidirectional NB exchange because NB packets are exchanged on both sides. If the subsequent tightly coupled UWB exchange also involves bidirectional messages / fragments (e.g., such as...) Figure 17 If described herein, then the protocol may be useful. As described herein, device radio frequency (RF) protocols can be used to exchange NB redundancy and channel hopping configurations out of band (OOB). In some implementations, a wireless system separate from the on-device HWT (e.g., OOB) can be used to coordinate NB control information (e.g., utilizing Bluetooth / BLE during connection setup).

[0141] Figure 25 This is another simplified flowchart illustrating message exchange between two devices using one or more NB channels according to a bidirectional redundant packet switching protocol, based on some implementation schemes. In some implementation schemes, Figure 25 The message exchange in process 2500 can correspond to the reference. Figure 24 The protocol described herein. It should be understood that some operations associated with process 2500 (e.g., scheduling NB signals, UWB segment transmissions, etc.) (and / or other processes further described herein) may be performed before, during, or after the operations of the box described in process 2500. Therefore, it should be understood that the simplified protocol shown in process 2500 (and / or other processes described herein) may also include other operational and / or protocol variations of this disclosure (e.g., full ranging protocol, beacon protocol, etc.) (and / or included within other operational and / or protocol variations of this disclosure).

[0142] Proceeding to process 2500, at block 2502, the first device (e.g., initiator 2402) may transmit a first initiation packet to the second device (e.g., responder 2404) via a first narrowband channel. As described above, and for example, it should be understood that, prior to the operation of block 2502, one or more operations may be performed to schedule the start time for the transmission of the first initiation packet (e.g., this is similar to...). Figure 18 (One or more operations of box 1802).

[0143] At block 2504, the first device may transmit a second initiation packet to the second device via a second narrowband channel different from the first narrowband channel. The transmission of the second initiation packet may be based at least in part on the determination that the first device has not received a first response packet from the second device via the first narrowband channel in response to the first initiation packet. It should be noted that if the second device has already transmitted the first response packet, the first device may not have yet transmitted the second initiation packet to the second device. In some embodiments, the second initiation packet may still be transmitted even if the first device has received the first response packet from the second device.

[0144] At block 2506, the first device may transmit a third initiation packet to the second device via a third narrowband channel different from the first narrowband channel and / or the second narrowband channel. The transmission of the third initiation packet may be based at least in part on the determination that the first device did not receive a second response packet from the second device via the second narrowband channel in response to the second initiation packet.

[0145] At box 2508, the first device may receive a third response packet from the second device via a third narrowband channel in response to a third initiation packet. At this box, according to reference... Figure 24 The described protocol allows the first device to subsequently terminate the exchange of NB packets.

[0146] Figure 26 This is another simplified flowchart 2600 illustrating signal transmission using one or more NB channels according to a one-way redundant packet transmission protocol, based on some implementation schemes. Figure 26 and Figure 24 Similarly, but in this case, only one side transmits NB packets (e.g., from initiator 2602 to responder 2604). Implementations using the beacon protocol (e.g., as described herein relative to...) Figure 34 (As further described) one can benefit from this method. See reference... Figure 24 In some implementations, the OOB system can be used to coordinate the transmission of NB control information (e.g., via Bluetooth / BLE).

[0147] Figure 27This is another simplified flowchart illustrating message exchange between two devices using one or more NB channels according to a one-way redundant packet transport protocol, based on some implementation schemes. In some implementation schemes, Figure 27 Message exchange can correspond to reference Figure 26 The protocol described.

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

[0149] At frame 2704, the first device may transmit a second initiation packet to the second device via a second narrowband channel that may be different from the first narrowband channel.

[0150] At frame 2706, the first device may transmit a third packet to the second device via a third narrowband channel that may be different from the first narrowband channel and the second narrowband channel.

[0151] Figure 28 This is another simplified flowchart 2800 illustrating signal transmission using a non-interleaved ranging protocol with a known fixed turnaround time, based on some implementation schemes. Figure 28 Schematic diagram 2800 depicts a full ranging protocol utilizing hybrid signaling as described herein. This bidirectional NB-IoT switching... Figure 24 The same applies as shown. Initiator 2802a then sends UWB fragments according to the information exchanged via the NB / OOB protocol. Responder 2804a performs a Time of Arrival (TOA) extraction after receiving all UWB fragments and sends its response UWB fragments starting from a fixed, precise time. This can be referred to as a fixed turnaround time interval (e.g., a fixed time interval), and the granularity of such time can be tens of picoseconds. Since this fixed turnaround time implicitly transmits the precise time increment between the responder's UWB RX and TX, it eliminates the need to transmit this precise time increment via data packets / payload. Initiator 2802a can calculate the TOF after receiving UWB fragments from responder 2804a. Accordingly, if responder 2804a decides to calculate this range, option 2 of schematic 2800 can be utilized. For example, the exchange order of UWB fragments can be reversed so that responder 2804b sends multiple fragments first, and then receives multiple response fragments from initiator 2802b. In option 2, a fixed turnaround time is still used.

[0152] Figure 29 This is another simplified flowchart illustrating message exchange based on a known fixed turnaround time, according to some implementation schemes. In some implementation schemes, Figure 29 The message exchange in process 2900 can correspond to the reference. Figure 28 The protocol described.

[0153] At block 2902 of process 2900, a first device (e.g., initiator 2802) may transmit packets to a second device (e.g., responder 2804) via narrowband signaling. In some embodiments, the packets may convey synchronization data (e.g., time and frequency synchronization data and / or scheduling information). In some embodiments, one or more operations of block 2902 may be similar to... Figure 18 The operation of box 1804. As described herein, the second device may obtain (e.g., extract from the sync header and / or payload data of the packet) and utilize the synchronization data to schedule the reception of multiple UWB segments from the first device. The first device may also schedule the transmission of the multiple UWB segments based on the synchronization data.

[0154] At block 2904, the first device can receive a second packet from the second device, which transmits second synchronization data to the first device via a second narrowband signal. In some embodiments, one or more operations of block 2904 may be similar to... Figure 19 The operation of frame 1808. As described herein, the first device can obtain and utilize the second synchronization data to schedule the reception of multiple UWB segments from the second device. The second device can also schedule the transmission of a second plurality of segments based on the second synchronization data.

[0155] In some implementation schemes, it may be in accordance with the reference Figure 24 and Figure 25 The aforementioned scheme repeats boxes 2902 and 2904.

[0156] At box 2906, the first device may transmit the plurality of segments to the second device via an ultra-wideband signal. In some embodiments, each of the plurality of segments may be time-separated from the other segments by at least a predefined time interval (e.g., according to relevant regulatory rules for transmission standards).

[0157] At block 2908, the first device can receive a second plurality of segments from the second device via a second ultra-wideband signal. In some embodiments, the first time a first segment of the second plurality of segments is transmitted to the first device is offset from the first time 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 range or time of flight. For example, the first device can determine a turnaround time, which can then be used to determine the Time of Flight (TOF).

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

[0159] Figure 30 This is another simplified flowchart 3000 illustrating a non-interleaved ranging protocol according to some implementations, which includes NB signal exchange of round-trip time and / or turnaround time after bidirectional exchange of UWB segments. Figure 30 Schematic diagram 3000 and Figure 28 Similarly, but after the UWB fragment exchange between initiator 3002 and responder 3004, one-way / two-way NB packets are used to transmit round-trip time and / or turnaround time, as well as optional status reports. This can be useful if the device does not have a fixed turnaround time capability or if both sides need to know the range / TOF. Note that one-way NB switching can be used when only one side needs to know the range, while two-way NB switching allows both sides to calculate the range.

[0160] Figure 31 This is another simplified flowchart illustrating message switching using NB signaling after bidirectional switching of UWB segments, based on some implementation schemes. In some implementation schemes, Figure 31 The message exchange in process 3100 can correspond to the reference. Figure 30 The protocol described.

[0161] At block 3102 of process 3100, a first device (e.g., initiator 3002) may transmit packets via narrowband signals to a second device (e.g., responder 3004), the packets conveying synchronization data. In some embodiments, one or more operations of block 3102 may be similar to... Figure 29 The operation of box 2902.

[0162] At block 3104, 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 3104 may be similar to... Figure 29 The operation of box 2904.

[0163] In some implementation schemes, it may be in accordance with the reference Figure 24 and Figure 25 The aforementioned scheme repeats boxes 3102 and 3104.

[0164] At block 3106, the first device can transmit multiple segments to the second device via an ultra-wideband signal, each of the multiple segments being time-separated from the other segments by at least a predefined time interval. In some embodiments, one or more operations of block 3106 may be similar to... Figure 18 The operation of box 1814.

[0165] At block 3108, 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 3108 may be similar to... Figure 18 The operation of box 1818.

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

[0167] In some implementation schemes, it may be in accordance with the reference Figure 24 and Figure 25 and / or Figure 26 and Figure 27 The aforementioned scheme repeats box 3110.

[0168] Figure 32 This is another simplified flowchart 3200 illustrating signal exchange based on a unidirectional NB and non-interleaved UWB ranging protocol, according to some implementation schemes. Figure 32 Schematic diagram 3200 depicts another variation in which a one-way NB exchange between initiator 3202 and responder 3204 is followed immediately by a UWB segment in the same direction. This scheme allows multiple responders 3204 to participate in ranging activities by responding in a known sequence or random order. In some implementations, the response may either include a timestamp in the response NB packet or use a fixed turnaround time scheme (as described herein). Initiator 3202 can then calculate the corresponding range, as described herein.

[0169] Figure 33 This is another simplified flowchart illustrating message exchange according to a one-way NB and non-interleaved UWB ranging protocol, based on some implementation schemes. In some implementation schemes, Figure 33 The message exchange in process 3300 can correspond to the reference. Figure 32 The protocol described.

[0170] 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 18 The operation of box 1804. In some implementations, it can be done according to the reference. Figure 26 and Figure 27 The aforementioned scheme repeats box 3302.

[0171] 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.

[0172] 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 18 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 26 and Figure 27 The aforementioned scheme repeats box 3306.

[0173] 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 18 The operation of box 1818. In some implementations, the first device may then use this information to calculate ToF and / or AoA.

[0174] Figure 34 This is another simplified flowchart 3400 illustrating signal exchange according to a beacon protocol, based on some implementations. As mentioned above, in some implementations, the beacon protocol can be employed when only one side, such as the initiator 3402, transmits NB signals (e.g., NB packets) and UWB signals (e.g., multiple fragments). This can be useful, for example, if a second (receiver) device is one of several devices 3404 of interest that interact 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, the initiator 3402 may send periodic beacon messages. It should be noted that the beacon protocol still utilizes the hybrid signaling methods described herein.

[0175] Figure 35This is another simplified flowchart illustrating message exchange according to the beacon protocol, based on some implementation schemes. In some implementation schemes, Figure 35 The message exchange process 3500 can correspond to the reference. Figure 34 The protocol described.

[0176] At block 3502, a first device (e.g., initiator 3402) can schedule the start time for transmitting packets to one or more interested devices 3404 via narrowband (NB) signals. In some embodiments, the operation of one or more of block 3502 may be similar to... Figure 18 The operation of box 1802.

[0177] At block 3504, the first device may transmit packets via narrowband signals to one or more devices 3404 of interest at the start time of scheduling. In some embodiments, the packets may convey synchronization data used by a second device to schedule the reception of multiple segments, respectively, via ultra-wideband (UWB) signals. In some embodiments, one or more operations of block 3504 may be similar to... Figure 18 The operation of box 1804.

[0178] In some implementation schemes, it may be in accordance with the reference Figure 26 and Figure 27 The aforementioned scheme repeats boxes 3502 and 3504.

[0179] At block 3506, the first device can schedule the transmission of the multiple segments via the ultra-wideband signal based on synchronization data. In some embodiments, one or more operations of block 3306 may be similar to... Figure 18 The operation of box 1812.

[0180] At block 3508, the first device can transmit the plurality of segments to the second device via an ultra-wideband signal. In some embodiments, each of the plurality of segments can be time-separated from the other segments by at least a predefined time interval. In some embodiments, one or more operations of block 3308 can be similar to... Figure 18 The operation of box 1814.

[0181] Figure 36 This is another simplified flowchart illustrating signal exchange according to an interleaved ranging protocol, based on some implementation schemes. Figure 36 In the interleaved ranging protocol shown in process 3600, this protocol allows the initiator 3602 and the responder 3604 to use the same T_test_reg (see...). Figure 7The UWB fragment swapping time is evenly distributed. In this case, the TX and RX UWB fragments are interleaved. This interleaved UWB swapping is preceded by bidirectional NB swapping and followed by unidirectional or bidirectional timestamp / state NB swapping (see [link to UWB swapping]). Figure 30 In some implementations, the protocol can significantly reduce the total ranging exchange time by enabling both the initiator 3602 and the responder 3604 to transmit the corresponding UWB segments using the same time interval. It should be understood that the transmission and / or reception attempts of the UWB segment itself can be conditional upon successful reception of NB packets. In some implementations, this can help optimize power consumption.

[0182] Figure 37 This is another simplified flowchart illustrating message exchange according to an interleaved ranging protocol, based on some implementation schemes. In some implementation schemes, Figure 37 The message exchange in process 3700 can correspond to the reference. Figure 36 The protocol described.

[0183] At block 3702 of process 3700, a first device (e.g., initiator 3602) may transmit packets via narrowband signals to a second device (e.g., responder 3604), the packets conveying synchronization data. In some embodiments, one or more operations of block 3702 may be similar to... Figure 29 The operation of box 2902.

[0184] At block 3704, 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 3704 may be similar to... Figure 29 The operation of box 2904.

[0185] In some implementation schemes, it may be in accordance with the reference Figure 24 and Figure 25 The aforementioned scheme repeats boxes 3702 and 3704.

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

[0187] At block 3708, the first device can receive a first segment of a second plurality of segments from the second device. 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 device receives the first segment of the second plurality of segments within a predefined time interval, the predefined time interval defining the time interval between the first segment and the second segment of the plurality of segments. In some embodiments, one or more operations of block 3708 can be similar to... Figure 18 The operation of box 1818. Note that in this case, individual corresponding segments from multiple segments are interleaved when transmitted / received by the corresponding devices.

[0188] At box 3710, the first device may transmit the second of the plurality of fragments to the second device after a predefined time interval has elapsed.

[0189] At box 3712, the first device may receive a second segment from a second plurality of segments from the second device. It should be understood that multiple rounds of interleaved segments may be exchanged between the two devices (e.g., multiple rounds including the operations of boxes 3710 and 3712) until the complete plurality of segments are exchanged between these devices.

[0190] At block 3714, the first device can receive packets from the second device via a narrowband signal. These packets include information that can be used to determine range or flight time, including at least one of: (I) round-trip time, (II) turnaround time, or (III) status report. In some embodiments, one or more operations of block 3710 may be similar to... Figure 31 The operation of box 3110. It should be noted that in some cases, the first device may also (and / or alternatively) enable the second device to determine the grouping of ranging information via narrowband signal transmission, depending on the context. In some embodiments, it may be done according to reference... Figure 24 and Figure 25 and / or Figure 26 and Figure 27 The aforementioned scheme repeats the operation of box 3714.

[0191] Figure 38This is another simplified block diagram 3800 illustrating the use of a separate wireless system for initial device discovery and connection setup, according to some implementations. Diagram 3800 depicts an extension of the NB-assisted concept to include another wireless system that can assist in the initial device discovery and connection setup as described herein. In this example, the wireless system (e.g., BLE 3802) can be used for initial coarse alignment of the device before control is handed over to the hybrid NB+UWB transceiver 3804. In some implementations, BLE 3802 can handle announcement / scanning, coarse synchronization, and / or connection setup. Meanwhile, the NB subsystem can handle fine synchronization to assist (“anchor”) MMS-UWB (multi-millisecond) transmissions. Additionally, the UWB subsystem can more efficiently “harvest” multi-millisecond UWB energy from dedicated segments 3806a-c used for TOF / AOA estimation.

[0192] Figure 39 This is another simplified block diagram 3900 illustrating the use of a separate wireless system for initial device discovery and connection setup, based on some implementation schemes. Figure 39 Schematic diagram 3900 illustrates a specific implementation of additional wireless systems (such as BLE 3802) and HWT on separate system-on-chips (SOCs 3906a-b and 3908a-b) located on the same devices (device A 3902 or device B 3904, respectively).

[0193] Figure 40 This is another simplified block diagram 4000 illustrating exemplary sequencing techniques that can be used when transmitting one or more UWB fragments of a UWB packet, according to some embodiments. As described above, some fragments 4002a-b contain CIRTS that can be used for CIR estimation and first path estimation. In some embodiments, each CIRTS fragment 4002 may include a periodic sequence, such as the periodic sequences 4004a-r of CIRTS fragment 4002a and the periodic sequences 4006a-r of CIRTS fragment 4002b. For example, the i-th fragment may include R periodic repetitions of the base sequence Ai (i=1, 2, 3…). This is in Figure 40The schematic diagram 4000 illustrates two segments and their base sequences A1 and A2. In one example, Ai can be a sequence of approximately 1 µs in length, and the number of repetitions R can be 32, resulting in a segment length of approximately 32 µs. In some implementations, the base sequence Ai can be selected to have autocorrelation and / or spectral characteristics favorable for the performance and implementation complexity of CIR and first path estimation. An example of such sequences is a set of ternary Ipatov sequences used in the IEEE 802.15.4z UWB standard, which have favorable periodic autocorrelation characteristics. In some implementations, the same Ai sequence can be used for each CIRTS segment 4002 of a given packet (but not necessarily for all transmissions for all users in a multi-user system). This simplifies transmitter, receiver, and protocol design. In some implementations, each segment 4002 can be based on a different Ai sequence (e.g., see...). Figure 21 Line 4), may, but does not necessarily, have a different length. This expands the range of possible sequence combinations for each transmitter-receiver device, thereby contributing to interference suppression in multi-user systems.

[0194] For reference Figure 21 As described in lines 5 and 6, and as referenced below. Figure 41 and Figure 42 In further detail, Gray-type periodic sequences can also be used when transmitting CIRTS segments.

[0195] Figure 41 This is another simplified block diagram 4100 illustrating another exemplary sequencing technique that can be used when transmitting one or more UWB fragments of a UWB packet, according to some implementation schemes. Figure 41Schematic diagram 4100 illustrates another exemplary embodiment, wherein CIRTS fragments 4102a or 4102b comprise R repetitions 4104a-r or 4106a-r of a pair of base sequences Ai and Bi, where i = 1, 2, 3… In one example, A1 and B1 may each have a length of 1024 ns, and the number of repetitions may be 20, thereby producing a CIRTS sequence of length 40.96 µs in each fragment 4102. In some embodiments, sequences Ai and Bi may form a Gray complementary pair. In the context of UWB, each sequence Ai, Bi may comprise a non-zero pulse sequence, possibly extended by a silence period of fixed duration between subsequent pulses, wherein the polarity (e.g., amplitude +1 or -1) follows Gray rules known in the art. Such sequence pairs may have several properties advantageous for CIR and first path estimation. First, the aperiodic autocorrelation functions of the two sequences forming the Gray pair are complementary, meaning that they sum to an ideal autocorrelation function and therefore have complementary spectra, which may be desirable for transmission regulations. They also feature low-complexity generator and correlator implementations. Furthermore, the periodic autocorrelation function of many Gray complement pairs is advantageous for CIR generation and first path extraction. In some implementations, as described herein, each segment 4102 may use the same (Ai,Bi) pair. In some implementations, each segment 4102 may use different (Ai,Bi) pairs. These choices may depend on, for example, the required level of complexity of the device and protocol, the number of users to be supported, and other factors.

[0196] Figure 42 This is another simplified block diagram 4200 illustrating another exemplary sequencing technique that can be used when transmitting one or more UWB fragments of a UWB packet, according to some implementation schemes. Figure 42Schematic diagram 4200 illustrates the use of Gray sequences with gaps between complementary pairs (e.g., Gap11 4204 in the first segment 4202a, Gap21 4212 in the second segment 4202b, etc.) and gaps between consecutive repetitions of each pair (e.g., Gap12 4206 in the first segment 4202a). For example, A1 4208 and B1 4210 may each have a length of 512 ns, Gap11 4204 may have a length of 128 ns, Gap12 4206 may have a length of 256 ns, and the number of repetitions R may be 20, resulting in a segment of length 32 × (2 × 512 + 128 + 256) ns = 45.056 µs. In some embodiments, the gaps help improve autocorrelation and spectral characteristics by expanding the size of the zero autocorrelation window around the autocorrelation peak, which can aid in CIR and first path estimation. Additionally, in some implementations, different transmitter-receiver device pairs (e.g., each pair associated with a corresponding link between the devices) may use different gap lengths between their sequences. This effectively results in different users' CIRTS sequences having different period lengths (in the example above, the period is (2 × 512 + 128 + 256) = 1408 ns). Having different periods can help reduce cross-correlation between different users' sequences, and thus can contribute to interference suppression in multi-user systems. In some implementations, and as... Figure 42 As described, even within the same group, different Gray complement pairs and / or different segment lengths (similar to the first two paragraphs) can be used to further improve interference suppression.

[0197] Figure 43 This is another simplified block diagram 4300 illustrating another exemplary sequencing technology that can be used when transmitting one or more UWB fragments, according to some implementation schemes. Figure 43Schematic diagram 4300 illustrates an embodiment in which the i-th CIRTS fragment consists of M repetitions of a base sequence Ci (e.g., this base sequence may be referred to herein as an “intermediate base sequence”). As described in the preceding paragraphs, each intermediate base sequence Ci may be different or they may all be the same, depending on the desired performance objective. In some embodiments, M may be a small number (e.g., 1, 2, or 3). For example, in the case where M is 2 and Ci has a length of approximately 22 µs, the resulting fragment length may be approximately 44 µs. In some implementations (e.g., having fewer repetitions compared to other implementations that may have more repetitions), having fewer repetitions can help flatten the spectrum of the transmitted waveform and thus allow the transmitter to transmit more energy while meeting regulatory transmission requirements. Additionally, having M>1 makes the segment periodic, but with a much larger period compared to the implementation examples in the preceding paragraphs. As further described herein, having periodic segments can facilitate automatic gain control (AGC) operation of the receiver. As depicted in schematic 4300, C1 4302 may include R repetitions 4308 of sequence A1 4312 followed by a gap (Gap11 4304), followed by sequence B1. 4314 is repeated R times by 4310, followed by a gap (Gap 124306). In an exemplary embodiment, Ai and Bi can be ternary Ipatov sequences. In another exemplary embodiment, Ai and Bi can form a pair of complementary Gray sequences. In yet another exemplary embodiment, Ai and Bi themselves can include shorter complementary Gray sequences. In some embodiments, the resulting sequence Ci itself is not periodic (e.g., aperiodic), even if the sequence has periodic portions (e.g., a first group sequence (Ai) is periodic within a first group, and a second group sequence (Bi) is periodic within a second group). In some embodiments, the sequencing technique depicted in schematic diagram 4300 can be similar to that described in reference [reference missing]. Figure 21 Line 7 describes (e.g., a hybrid sequencing technique in which non-periodic sequences include periodic sequences). In some embodiments, this technique allows the period of the fragment to be at least as large as the length of Ci, which, as mentioned above, flattens the waveform spectrum. Furthermore, the internal structure of Ci itself can still facilitate simple correlation at the receiver. For example, the receiver can first correlate R repetitions of Ai, then correlate R repetitions of Bi, and the two results can be combined, and the same operation can be repeated for each repetition of Ci.

[0198] In some implementations, periodic sequences can also be beneficial for AGC (Automatic Generative Control) of the receiver. When receiving segments at high power, the receiver can observe the early portions of the segment to automatically adjust its amplifier gain to avoid signal distortion and clipping. If the segment is periodic, the receiver can choose to sacrifice any portion of the segment for AGC operation and still be able to use the remaining repetitions in the segment for CIR (Continuous Interpretation) and first path extraction without significantly adjusting its operation.

[0199] Figure 44 This is a simplified flowchart 4400 illustrating sequencing technologies that can be used when transmitting one or more UWB fragments, according to some embodiments. In some embodiments, flowchart 4400 may be similar to that described in reference [reference]. Figure 43 As described.

[0200] At block 4402, a first device (e.g., a client station) transmits a packet to a second device (e.g., another client station) via a narrowband signal. In some embodiments, the packet may include information indicating the time period for receiving multiple segments, respectively, via a UWB signal. In some embodiments, the information included in the packet may correspond to any suitable information that can be used to communicate synchronization data to another device, as described herein. This may include, for example, information associated with (e.g., included therein) the sync field and / or data payload field of the packet. In some embodiments, another (e.g., receiving) device may thereby obtain synchronization data (e.g., for scheduling the reception of multiple segments) based on the information included in the packet. In some embodiments, one or more operations of block 4402 may be similar to, for example, those described herein regarding... Figure 22 As described in frame 2206.

[0201] At block 4404, the first device transmits a first segment of a plurality of segments to the second device via an ultra-wideband signal. In some embodiments, one or more operations of block 4404 may be similar to those described herein, for example, regarding... Figure 23 As described in box 2214. In some embodiments, the first fragment may include at least one intermediate base sequence (e.g., Figure 43 The intermediate base sequence Ci). In some embodiments, the intermediate base sequence may be aperiodic. In some embodiments, the intermediate base sequence may include a first set of first sequences (e.g., R repetitions 4308 of A1 4312, such as...). Figure 43 (as depicted in the text), wherein the first sequence is periodic within the first group. In some embodiments, the intermediate base sequence may also include a second group of second sequences (e.g., R repetitions of B14314 4310, such as...). Figure 43 (as depicted in the text), where the second sequence is periodic within the second group. In some embodiments, the second sequence of the second group follows the first sequence of the first group.

[0202] In some embodiments, the intermediate base sequence may also include a first gap interval (e.g., Figure 43 The gap 114304) and the second gap (e.g., Figure 43 (Gap 12 4306). In some embodiments, the first gap interval is included between the first set of first sequences and the second set of second sequences. In some embodiments, the second gap interval follows the second set of second sequences. In some embodiments, at least one of the first length of the first gap interval or the second length of the second gap interval is transmitted as a first parameter (e.g., within the packet transmitted at block 4402) between the first and second devices before the first segment of the plurality of segments is first transmitted. In some embodiments, the first parameter is different from the second parameter transmitted between the first and third devices. For example, consider the case where the first device transmits the second segment of the second plurality of segments to the third device (e.g., another client station) via a second ultrawideband signal, wherein the second segment is transmitted at least partially based on the second parameter. In this example, the second device can be enabled to distinguish the first segment from the second segment at least partially based on the difference between the first parameter and the second parameter.

[0203] In some embodiments, the first parameter is associated with a first signature (e.g., an identifier) ​​of a first link (e.g., a connection / session) between the first and second devices, wherein the second parameter is associated with a second signature of a second link between the first and third devices. In some embodiments, the first and second signatures differ at least in part based on the difference in the length of the gap interval included in the intermediate base sequence associated with the respective links. In some embodiments, as referenced... Figure 43 As described, at least one of the second or third devices can perform signal interference suppression (e.g., and / or avoid cross-correlation between different link sequences) at least in part based on the difference between the first and second signatures. In some embodiments, by having different (e.g., varying) gap interval lengths between different device pairs (e.g., transmitter-receiver device pairs) their sequences, the techniques of this paper can make the signatures associated with the corresponding links (e.g., between device pairs) more diverse than would be achievable without using varying gap intervals. In some embodiments, when there are many device pairs (e.g., many links) and / or a limited number of sequence types (e.g., A1 4312, B1 4314, A2 4316, B2 4318, etc., as representative examples of different sequence types) exist in a congested space, such as A1 4312, B1 4314, A2 4316, B2 4318, etc., which can be used to distinguish links between devices (e.g., distinguish link signatures) are available. Figure 43 This can be useful when (as depicted in the text).

[0204] As described herein, different sequence types (e.g., including sequence pairing types) may be used (e.g., within intermediate base sequences). For example, in one embodiment, a first sequence in a first set of first sequences (e.g., A1) and a second sequence in a second set of second sequences may together form a pair of complementary sequences (e.g., complementary Gray-type sequences). In some embodiments, as described herein, at least one of the first sequence in the first set of first sequences or the second sequence in the second set of second sequences has autocorrelation properties favorable for first path extraction. For example, either (or both) sequences may include ternary Ipatov sequences. In some embodiments, the first sequence in the first set of first sequences and the second sequence in the second set of second sequences may include complementary sequences (e.g., complementary Gray sequences). As mentioned above, in each of these cases, the resulting intermediate base sequence itself is not periodic (e.g., aperiodic), even if there is a periodic portion within a set of sequences. In some embodiments, the intermediate base sequence is one of a plurality of periodic intermediate base sequences (e.g., M repetitions of C1 4302, as referenced). Figure 43 (As depicted).

[0205] The foregoing describes exemplary techniques for transmitting hybrid NB and UWB wireless signals. Some or all of these systems and methods can be at least partially achieved through methods such as those described above. Figures 1 to 44 The invention may be implemented using one or more of the architectures shown herein, but is not necessarily implemented using these architectures. It should be understood that any suitable device can execute the techniques disclosed herein. Furthermore, various non-limiting examples have been described in the foregoing description. For purposes of explanation, numerous specific configurations and details have been set forth to provide a thorough understanding of the examples. However, it will also be apparent to those skilled in the art that some examples can be implemented without these specific details. In addition, well-known features have sometimes been omitted or simplified to prevent confusion with the examples described herein.

[0206] While numerous implementations of the concepts presented herein may exist, a beneficial option for NB and UWB implementations is to arrange the radio frequency (RF) operating frequencies used for UWB and NB signals close to each other. For example, suitable frequency ranges for NB signaling could be unlicensed National Information Infrastructure (UNII) bands in the 5 GHz 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 often allow NB transmission 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. The advantage of using NB and UWB frequencies close to each other is the easier sharing of antenna hardware between the NB and UWB. However, it should be noted that another suitable operating range for NB subsystems is in the 2.4 GHz to 2.5 GHz ISM band (typically used for ZigBee and Bluetooth as well as other consumer wireless systems), and a variety of UWB center frequencies from 1 GHz to 10 GHz and above 10 GHz can be used for hybrid system concepts.

[0207] Regarding the hardware implementation of 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, NB SOCs, and UWB SOCs, where tightly coupled and joint MAC control processing is accomplished through direct control signals exchanged between the two SOCs.

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

[0209] Clause 1: A computer-implemented method comprising: transmitting a packet from a first device to a second device via a narrowband (NB) signal, the packet including information indicating time periods for reception of a plurality of segments respectively via an ultra-wideband (UWB) signal; and transmitting a first segment of the plurality of segments from the first device to the second device via the UWB signal, the first segment including at least one intermediate base sequence, the at least one intermediate base sequence being aperiodic and including a first set of first sequences and a second set of second sequences, the first sequences being periodic within the first set and the second sequences being periodic within the second set.

[0210] Clause 2: The computer-implemented method according to Clause 1, wherein the second group of second sequences follows the first group of first sequences, wherein the intermediate base sequence further includes a first gap interval and a second gap interval, wherein the first gap interval is included between the first group of first sequences and the second group of second sequences, and wherein the second gap interval follows the second group of second sequences.

[0211] Clause 3: A computer-implemented method according to any one of Clauses 1 or 2, wherein at least one of the first length of the first gap interval or the second length of the second gap interval is transmitted as a first parameter between the first device and the second device before the first segment of the plurality of segments is transmitted, and wherein the first parameter is different from the second parameter transmitted between the first device and the third device.

[0212] Clause 4: The computer-implemented method according to any one of Clauses 1 or 3 further comprises: transmitting a second segment of a second plurality of segments from the first device to the third device via a second ultra-wideband signal, the second segment being transmitted at least partially based on the second parameter, and wherein the second device is enabled to distinguish the first segment from the second segment at least partially based on the difference between the first parameter and the second parameter.

[0213] Clause 5: A computer-implemented method according to any one of Clauses 1 or 4, wherein the first parameter is associated with a first signature of a first link between the first device and the second device, wherein the second parameter is associated with a second signature of a second link between the first device and the third device, and wherein the first signature and the second signature are different at least in part based on a difference in the length of the gap interval included in the intermediate base sequence associated with the respective link.

[0214] Clause 6: A computer-implemented method according to any one of Clauses 1 or 5, wherein at least one of the second or third devices performs signal interference suppression based at least in part on the difference between the first signature and the second signature.

[0215] Clause 7: A computer-implemented method according to any one of Clauses 1 or 6, wherein a first number of distinct signatures includes the first signature and the second signature, and wherein the first number of distinct signatures is greater than a second number of sequence types including the first sequence and the second sequence.

[0216] Clause 8: A computer-implemented method according to any one of Clauses 1 to 4, wherein the first sequence in the first set of first sequences and the second sequence in the second set of second sequences together form a pair of complementary sequences.

[0217] Clause 9: The computer-implemented method according to Clause 8, wherein the pair of complementary sequences comprises complementary Gray sequences.

[0218] Clause 10: A computer-implemented method according to any one of Clauses 1 to 9, wherein at least one of the first sequence in the first set of first sequences or the second sequence in the second set of second sequences has autocorrelation properties.

[0219] Clause 11: The computer-implemented method according to Clause 10, wherein these autocorrelation properties include ternary Ipatov sequences.

[0220] Clause 13: A computer-implemented method according to any one of Clauses 1 to 11, wherein at least one of the first sequence in the first set of first sequences or the second sequence in the second set of second sequences includes a complementary sequence.

[0221] Clause 14: The computer-implemented method according to Clauses 1 to 13, wherein the intermediate base sequence is one of a plurality of periodic intermediate base sequences.

[0222] Other embodiments of this disclosure may relate to an apparatus comprising: a memory including computer-executable instructions; and one or more 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 clauses 1 to 14.

[0223] Other embodiments of this disclosure may relate to one or more computer-readable storage media, including: 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 clauses 1 to 14.

[0224] Other embodiments of this disclosure may relate to an apparatus comprising: a processor circuit configured to perform the method according to any one of clauses 1 to 14.

[0225] Various implementation schemes can be implemented in a wide variety of operating environments, in some cases of which may include one or more user computers, computing devices, or processing devices that can be used to operate any of a number of applications. User devices or client devices may include any of many general-purpose personal computers, such as desktop or laptop computers running standard operating systems, and cellular, wireless, and handheld devices running mobile software and capable of supporting multiple networking and instant messaging protocols. The system may also include multiple 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 may also include other electronic devices, such as virtual terminals, thin clients, gaming systems, and other devices capable of communicating via a network.

[0226] Most implementations utilize at least one network familiar to those skilled in the art to support communication using any of the various commercial protocols such as TCP / IP, OSI, FTP, UPnP, NFS, CIFS, and AppleTalk. The network can be, for example, a local area network (LAN), a wide area network (WAN), a virtual private network (VPN), the Internet, an intranet, an extranet, the public switched telephone network (PSTN), an infrared network, a wireless network, or any combination thereof.

[0227] In implementations utilizing a web server, the web server can run any of a variety of server or middleware applications, including HTTP servers, FTP servers, CGI servers, data servers, Java servers, and business application servers. One or more servers may also be able to execute programs or scripts in response to requests from user devices, such as by executing one or more applications, which can be implemented in any programming language such as Java. ® One or more scripts or programs written in C, C#, or C++, or any scripting language such as Perl, Python, or TCL, and combinations thereof. One or more servers may also include a database server, including but not limited to those retrievable from Oracle. ® Microsoft ® Sybase ® and IBM ® Those obtained through commercial purchases.

[0228] The environment may include various data repositories and other storage media, as described above. These may reside in various locations, such as on storage media local to one or more computers or on storage media of any or all computers on a network (and / or reside within one or more computers). In a particular set of embodiments, information may reside in a storage area network (SAN) familiar to those skilled in the art. Similarly, any necessary files for performing functions belonging to a computer, server, or other network device may be stored locally and / or remotely as needed. When the system includes computerized devices, each such device may include hardware elements electrically coupled via a bus, including, for example, at least one central processing unit (CPU), at least one input device (e.g., mouse, keyboard, controller, touchscreen, or keypad), and at least one output device (e.g., display device, printer, or speaker). Such systems may also include one or more storage devices, such as disk drives, optical storage devices, and solid-state storage devices such as RAM or ROM, as well as removable media devices, memory cards, flash memory cards, and so on.

[0229] Such devices may also include computer-readable storage medium readers, communication devices (e.g., modems, network interface cards (wireless or wired), infrared communication devices, etc.), and working memory as described above. Computer-readable storage medium readers may be connected to or configured to receive non-transitory computer-readable storage media representing remote, local, fixed, and / or removable storage devices, as well as storage media for temporarily and / or more permanently containing, storing, transmitting, and retrieving computer-readable information. Systems and various devices will also typically include multiple software applications, modules, services, or other elements residing within at least one working memory device, including operating systems and applications such as client applications or browsers. It should be understood that alternative embodiments may have many variations as described above. For example, custom hardware may also be used, and / or specific elements may be implemented in hardware, software (including portable software such as applets), or both. Furthermore, connections to other computing devices such as network input / output devices may be used.

[0230] Non-transitory storage media and computer-readable storage media used for portions containing code may include any suitable media known or used in the art, such as, but not limited to, volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing 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 technologies, CD-ROM, DVD or other optical memory, magnetic tape cassettes, magnetic tape, disk storage devices or other magnetic storage devices, or any other media that can be used to store the desired information and is accessible by system devices. Other ways and / or methods for implementing various embodiments will be recognized by those skilled in the art, at least in part, based on the disclosure and teachings provided herein. However, computer-readable storage media do not include transient media such as carrier waves.

[0231] Accordingly, the specification and drawings should be regarded as illustrative rather than restrictive. However, it will be apparent that various modifications and changes may be made thereto without departing from the broader spirit and scope of this disclosure as set forth in the claims.

[0232] Other variations are within the scope of this disclosure. Therefore, although the disclosed technology is susceptible to various modifications and alternative constructions, certain exemplary embodiments are shown in the accompanying drawings and have been described in detail above. However, it should be understood that this disclosure is not intended to be limited to the specific forms disclosed, but rather is intended to cover all modifications, alternative constructions, and equivalents falling within the scope and spirit of this disclosure as defined by the appended claims.

[0233] In the context of describing the disclosed embodiments (particularly in the context of the claims below), the terms “a,” “an,” and “the,” as well as similar indicator words, shall be interpreted to cover both singular and plural forms unless otherwise stated or clearly contradicted by the context. Unless otherwise stated, the terms “comprising,” “having,” “including,” and “containing” shall be interpreted as open-ended terms (i.e., meaning “including but not limited to”). The term “connected” is interpreted as being partially or wholly included, attached, or joined together, even if there is interference. The phrase “at least partially based on” shall be understood as open-ended and not in any way limiting, and is intended to be interpreted or otherwise understood as “at least partially based on” where appropriate. Unless otherwise stated herein, the description of numerical ranges herein is intended merely as a simple way of referring separately to each individual value falling within that range, and each individual value is incorporated into the specification as if separately referenced herein. All methods described herein can be performed in any suitable order unless otherwise stated or clearly contradicted by the context. Unless otherwise stated, the use of any and all examples or exemplary language (e.g., “such as”) provided herein is intended merely to better illustrate embodiments of this disclosure and does not limit the scope of this disclosure. No language in the specification should be construed as indicating that any unstated element is essential to the practice of this disclosure.

[0234] Unless otherwise specifically stated, parse languages ​​such as the phrase “at least one of X, Y, or Z” are understood in the context to generally refer to items, terms, etc., which can be X, Y, or Z, or any combination thereof (e.g., X, Y, and / or Z). Therefore, such parse languages ​​are generally not intended and should not imply that certain embodiments require the existence of at least one of X, at least one of Y, or at least one of Z. Additionally, unless otherwise specifically stated, union languages ​​such as the phrase “at least one of X, Y, and Z” should also be understood to mean X, Y, Z, or any combination thereof, including “X, Y, and / or Z”.

[0235] This document describes preferred embodiments of the present disclosure, including the best known modes for carrying out the present disclosure. Variations of those preferred embodiments will become apparent to those skilled in the art after reading the foregoing description. It is expected that those skilled in the art will appropriately employ such variations and intend to practice these techniques in ways different from those specifically described herein. Therefore, this disclosure includes all modifications and equivalents of the subject matter recited in the appended claims, as permitted by applicable law. Furthermore, unless otherwise indicated herein or clearly contradicted by the context, this disclosure encompasses any combination of all possible variations of the foregoing elements.

[0236] All references cited in this article, including publications, patent applications and patents, are incorporated herein by reference, as each reference is individually and specifically indicated to be incorporated by reference and elaborated in the entire text.

[0237] As described above, one aspect of the present invention is the collection and use of data to wirelessly transmit a secure framework for authentication. This disclosure contemplates that, in some instances, the collected data may include personally identifiable information (PII) data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data (e.g., GPS coordinates), telephone numbers, email addresses, Twitter IDs, home addresses, or any other identifying or personal information.

[0238] This disclosure recognizes that the use of such personal information data in the present invention can benefit a user. For example, personal information data can be used to obtain access to resources controlled by an access control system.

[0239] This disclosure assumes that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to 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 to users and should be updated as data collection and / or use change. Personal information from users should be collected for the entity's lawful and reasonable purposes and not shared or sold outside of these lawful uses. Furthermore, such collection / sharing should be conducted only after obtaining informed consent from users. In addition, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data and ensure that others with access to such personal information data comply with their privacy policies and processes. Additionally, such entities may be subject to third-party evaluations to demonstrate their compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be adapted to the specific types of personal information data collected and / or accessed, and to applicable laws and standards, including specific considerations regarding jurisdiction. For example, in the United States, the collection or acquisition of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while in other countries, health data may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained for different types of personal data in each country.

[0240] Regardless of the foregoing, this disclosure also contemplates implementation schemes for users to selectively block the use or access to personal information data. That is, this disclosure contemplates providing hardware and / or software components to prevent or block access to such personal information data. For example, with respect to services related to tracking a user's location (e.g., via the user's mobile device), the inventive technology can be configured to allow the user to opt-in or opt-out at any time during or after service registration to participate in the collection of personal information data. In addition to providing opt-in and opt-out options, this disclosure envisions providing notifications related to access to or use of personal information. For example, users may be notified when downloading an application that their personal information data will be accessed, and then reminded again just before the application accesses the personal information data.

[0241] Furthermore, the purpose of this disclosure is to manage and process personal information data to minimize the risk of unintentional or unauthorized access or use. Once data is no longer needed, this risk can be minimized by limiting data collection and deleting data. Additionally, and where applicable, including in certain health-related applications, data deidentification can be used to protect user privacy. Deidentification can be facilitated, where appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than the address level), controlling how data is stored (e.g., aggregating data among users), and / or other methods.

[0242] Therefore, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, it is also contemplated that various embodiments can be implemented without access to such personal information data. That is, various embodiments of the present invention will not be unable to function properly due to the absence of all or part of such personal information data.

Claims

1. A computer-implemented method comprising: transmitting, by a first device, a packet to a second device via a narrowband (NB) signal, the packet including information indicating a time period for reception of a plurality of segments via a respective ultra-wideband (UWB) signal; and transmitting, by the first device, a first segment of the plurality of segments to the second device via the ultra-wideband signal, the first segment including at least one midamble sequence, the at least one midamble sequence being aperiodic and including a first set of first sequences and a second set of second sequences, the first sequences being periodic within the first set and the second sequences being periodic within the second set.

2. The computer-implemented method of claim 1, wherein the second set of second sequences follows the first set of first sequences, wherein the midamble sequence further includes a first gap interval and a second gap interval, wherein the first gap interval is included between the first set of first sequences and the second set of second sequences, and wherein the second gap interval follows the second set of second sequences.

3. The computer-implemented method of claim 2, wherein at least one of a first length of the first gap interval or a second length of the second gap interval is communicated as a first parameter between the first device and the second device prior to a first transmission of the first segment of the plurality of segments, and wherein the first parameter is different from a second parameter communicated between the first device and a third device.

4. The computer-implemented method of claim 3, further comprising: transmitting, by the first device, a second segment of a second plurality of segments to the third device via a second ultra-wideband signal, the second segment being transmitted based at least in part on the second parameter, and wherein the second device is enabled to distinguish the first segment from the second segment based at least in part on a difference between the first parameter and the second parameter.

5. The computer-implemented method of any one of claims 3 or 4, wherein the first parameter is associated with a first signature of a first link between the first device and the second device, wherein the second parameter is associated with a second signature of a second link between the first device and the third device, and wherein the first signature and the second signature are different based at least in part on a difference in gap interval length included within a midamble sequence associated with a respective link.

6. The computer-implemented method of claim 5, wherein at least one of the second device or the third device performs signal interference mitigation based at least in part on a difference between the first signature and the second signature.

7. The computer-implemented method of claim 5, wherein a first number of different signatures includes the first signature and the second signature, and wherein the first number of different signatures is greater than a second number of sequence types including the first sequences and the second sequences.

8. The computer-implemented method of any one of claims 1-4, wherein a first sequence of the first set of first sequences and a second sequence of the second set of second sequences together form a pair of complementary sequences.

9. The computer-implemented method of claim 8, wherein the pair of complementary sequences comprises complementary Golay sequences.

10. The computer-implemented method of any one of claims 1-4, wherein at least one of the first sequence of the first set of first sequences or the second sequence of the second set of second sequences has an autocorrelation property.

11. The computer-implemented method of claim 10, wherein the autocorrelation property comprises a ternary Ipatov sequence.

12. The computer-implemented method of any one of claims 1-4, wherein at least one of the first sequence of the first set of first sequences or the second sequence of the second set of second sequences comprises a complementary sequence.

13. The computer-implemented method of claim 12, wherein the complementary sequence comprises a complementary Golay sequence.

14. The computer-implemented method of any one of claims 1-4, wherein the intermediate base sequence is one of a plurality of periodic intermediate base sequences.

15. An electronic device, comprising: a memory comprising 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 one of claims 1-14.

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

17. An electronic device, comprising: a processor circuit configured to perform the method of any one of claims 1-14.

Images