Determining UWB / NBA-UWB-MMS ranging rounds via narrowband-based advertising

Abstract

The present disclosure relates to declaring a UWB / NBA-UWB-MMS ranging round via a narrowband-based advertisement. Techniques are provided for utilizing a mixture of ultra wide band (UWB) and narrowband (NB) signaling to provide more efficient operating range and operating efficiency. In one example, a first subsystem of a first device may determine parametric data for a ranging round (e.g., UWB and / or NB Assisted (NBA) UWB Multi-milliseconds (MMS) ranging), and transmit the parametric data to a second subsystem of the first device. The parameter data may indicate a first time associated with a first time domain for performing ranging. The second subsystem may determine a second time based on the first time, whereby the second time is associated with a second time domain for performing NB signaling (e.g., via a Bluetooth Low Energy (BLE) protocol). The first device may transmit, via the NB signal, an advertisement packet indicating the second time. The first device may then initiate the ranging round at the first time.

Description

[0001] This application is a divisional application of a Chinese patent application with an application date of August 4, 2022, an application number of 202210933682.6, and an invention title of "Method, apparatus, medium, and device for interaction between UWB and NB radio". Background Art

[0002] Wireless devices can perform many different tasks using short-range wireless applications. For example, a wireless device (e.g., a key fob) can be configured to automatically unlock a vehicle's door when the device enters a certain proximity of a vehicle (e.g., a car). In many cases, regulatory rules and / or other technical limitations can constrain the use of certain types of wireless signaling. These regulatory rules and / or technical limitations can vary between different types of wireless signaling. For example, the regulatory rules governing ultra-wideband (UWB) signaling can be different from those governing narrowband (NB) signaling, at least in part because they can utilize different frequency bands. In some cases, these conventional rules and / or technical limitations make it difficult for a system to achieve a desired operating range and / or a desired operating efficiency. Brief Description of the Drawings

[0003] Figure 1 is a simplified block diagram of an exemplary UWB-equipped device according to some embodiments.

[0004] Figure 2 is another simplified block diagram showing an exemplary technique for exchanging wireless messages between UWB-equipped devices according to some embodiments.

[0005] Figure 3 is another simplified block diagram showing at least some exemplary techniques for calculating a channel impulse response (CIR) according to some embodiments.

[0006] Figure 4 is another simplified block diagram showing at least some exemplary techniques for formatting UWB packets according to some embodiments.

[0007] Figure 5 is another simplified block diagram showing at least some exemplary techniques for determining time of flight (TOF) according to some embodiments.

[0008] Figure 6 is another simplified diagram showing an example of a power spectral density associated with measurements of a UWB signal according to a certain embodiment.

[0009] Figure 7 is another simplified block diagram showing at least some exemplary techniques for transmitting data segments within a UWB frame according to some embodiments.

[0010] Figure 8Another simplified block diagram showing at least some exemplary techniques for transmitting data segments associated with UWB packet types, according to some embodiments.

[0011] Fig. 9 Another simplified block diagram showing at least some exemplary techniques for transmitting data segments within multiple time intervals in a UWB framework, according to some embodiments.

[0012] Fig.10 Another simplified diagram showing the potential advantages and disadvantages of at least some wireless systems utilizing UWB signaling and / or NB signaling, according to some embodiments.

[0013] Fig.11 Another simplified block diagram showing at least some exemplary techniques for utilizing a mixture of UWB signaling and NB signaling, according to some embodiments.

[0014] Fig.12 Another simplified block diagram showing at least some exemplary techniques for utilizing a mixture of UWB signaling and NB signaling, according to some embodiments.

[0015] Fig.13 Another simplified block diagram showing at least some exemplary techniques for utilizing NB signaling via an NB packet format, according to some embodiments.

[0016] Fig.14 Another simplified block diagram showing two devices respectively configured to communicate with each other using a mixture of UWB signaling and NB signaling, according to some embodiments.

[0017] Fig.15 Another simplified block diagram showing a hybrid wireless transceiver of a device configured to communicate with another device using a mixture of UWB signaling and NB signaling, according to some embodiments.

[0018] Fig.16 A simplified flowchart showing the signal exchange between two devices, according to some embodiments.

[0019] Fig.17 Another simplified flowchart showing the signal exchange between two devices, according to some embodiments.

[0020] Fig.18 Another simplified flowchart showing an exemplary process performed by an initiating device, according to some embodiments.

[0021] Fig.19 Another simplified flowchart showing an exemplary process performed by a responding device, according to some embodiments.

[0022] Fig. 20 is another simplified block diagram showing the use of NB signaling to transmit UWB payload data, according to some embodiments.

[0023] Fig.21 is another simplified block diagram showing exemplary waveforms that may be included in one or more segments transmitted by the UWB signaling layer of a device, according to some embodiments.

[0024] Fig. 22 is another simplified block diagram showing the first part of an exemplary process performed by a device for hybrid signaling, according to some embodiments.

[0025] Fig.23 is according to some embodiments showing Fig. 22 the remainder of the exemplary process, according to some embodiments.

[0026] Fig.24 is another simplified flowchart showing signal transmission using one or more NB channels according to a two-way redundant packet switching protocol, according to some embodiments.

[0027] Fig.25 is another simplified flowchart showing message exchange between two devices using one or more NB channels according to a two-way redundant packet switching protocol, according to some embodiments.

[0028] Fig.26 is another simplified flowchart showing signal transmission using one or more NB channels according to a one-way redundant packet transmission protocol, according to some embodiments.

[0029] Fig. 27 is another simplified flowchart showing message exchange between two devices using one or more NB channels according to a one-way redundant packet transmission protocol, according to some embodiments.

[0030] Fig.28 is another simplified flowchart showing signal transmission using a non-interleaved ranging protocol with a known fixed round-trip time, according to some embodiments.

[0031] Fig.29 is another simplified flowchart showing message exchange based on a known fixed round-trip time, according to some embodiments.

[0032] Fig.30 is another simplified flowchart showing a non-interleaved ranging protocol that includes NB signal exchange of round-trip time and / or round-trip delay after two-way exchange of UWB segments, according to some embodiments.

[0033] Fig.31Another simplified flowchart showing message exchange using NB signal exchange after two-way exchange of UWB segments, according to some embodiments.

[0034] Fig.32 Another simplified flowchart showing signal exchange according to a unidirectional NB and non-interleaved UWB ranging protocol, according to some embodiments.

[0035] Fig.33 Another simplified flowchart showing message exchange according to a unidirectional NB and non-interleaved UWB ranging protocol, according to some embodiments.

[0036] Fig.34 Another simplified flowchart showing signal exchange according to a beacon protocol, according to some embodiments.

[0037] Fig.35 Another simplified flowchart showing message exchange according to a beacon protocol, according to some embodiments.

[0038] Fig.36 Another simplified flowchart showing signal exchange according to an interleaved ranging protocol, according to some embodiments.

[0039] Fig.37 Another simplified flowchart showing message exchange according to an interleaved ranging protocol, according to some embodiments.

[0040] Fig.38 Another simplified block diagram showing the use of a standalone wireless system for initial device discovery and connection setup, according to some embodiments.

[0041] Fig.39 Another simplified block diagram showing the use of a standalone wireless system for initial device discovery and connection setup, according to some embodiments.

[0042] Fig.40 A simplified block diagram showing techniques for announcing ranging rounds (e.g., UWB and / or Narrowband-Assisted (NBA) UWB Multi-Millisecond (MMS) (NB-UWB-MMS) ranging rounds) via NB signals, according to some embodiments.

[0043] Fig.41 A simplified flowchart showing techniques for announcing UWB / NBA-UWB-MMS ranging rounds via NB signals, according to some embodiments.

[0044] Fig.42 A simplified block diagram showing techniques for operating a hybrid (UWB / NB) system in an environment including an anchor station and a client station, according to some embodiments.

[0045] Fig.43 is another simplified block diagram showing a technique for performing ranging rounds using a combination of UWB signaling and NB signaling, according to some embodiments.

[0046] Fig.44 is a simplified block diagram showing ranging session parameters, according to some embodiments.

[0047] Fig.45 is a simplified block diagram showing ranging parameters that can be dynamically adjusted between ranging rounds, according to some embodiments.

[0048] Fig.46 is a simplified block diagram showing the use of random / adaptive channel hopping between ranging rounds, according to some embodiments.

[0049] Fig.47 is a simplified block diagram showing the situation where synchronization data used in a previous ranging round can also be used in the next ranging round, according to some embodiments.

[0050] Fig.48 is a simplified block diagram showing the adaptive asymmetric transmission of UWB segments within a ranging round according to a non-interleaved ranging protocol, according to some embodiments.

[0051] Fig.49 is another simplified block diagram showing the adaptive asymmetric transmission of UWB segments within a ranging round according to a non-interleaved ranging protocol, according to some embodiments.

[0052] Fig.50 is a simplified block diagram showing the adaptive asymmetric transmission of UWB segments within a ranging round according to an interleaved ranging protocol, according to some embodiments.

[0053] Fig.51 is another simplified block diagram showing the adaptive asymmetric transmission of UWB segments within a ranging round according to an interleaved ranging protocol, according to some embodiments. DETAILED DESCRIPTION

[0054] In the following description, various examples will be described. For purposes of explanation, numerous specific configurations and details are set forth in order to provide a thorough understanding of the examples. However, it will also be apparent to those skilled in the art that some examples may be practiced without these specific details. Additionally, well-known features may be omitted or simplified to prevent obscuring the examples described herein.

[0055] Embodiments of the present disclosure may provide techniques for using a hybrid of ultra-wideband (UWB) and narrowband (NB) signaling to provide improved operating range and / or operating efficiency when performing wireless communication between execution devices. For example, the techniques disclosed herein may enable a first device to effectively determine the location (position) of a second device relative to the first device and / or effectively determine a distance estimate (e.g., range estimate) between the two devices. To illustrate, consider an example in which two devices, a first device and a second device, are capable of wireless communication. In this example, hybrid signaling may be performed according to a ranging protocol involving two-way NB and UWB signaling between the first device and the second device. The two devices may first perform an initial phase during which there may be initial device discovery and initial (e.g., "coarse") synchronization between the two devices. In some examples, this initial phase may be performed by, for example, the wireless systems of each device, which are equipped to transmit wireless signals using low-power Bluetooth (BLE). During this initial phase, the wireless system of the first device may schedule a start time (e.g., a discrete moment) for transmitting at least one packet (e.g., an "NB poll" packet) to the second device via an NB signal. The first device may also schedule a window (e.g., a time interval) for subsequently receiving a second packet (e.g., an "NB response" packet transmitted via another NB signal) from the second device by the first device.

[0056] After this initial phase, the first device may then transmit the scheduled NB poll packet to the second device via an NB signal at the scheduled start time, where the packet 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 packet may include a synchronization (“sync”) field and a data payload field. The data payload field may include scheduling data (e.g., which 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) by using prior art 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 by using prior art demodulation and decoding techniques. The second device may use this synchronization data to schedule and assist in the reception of a plurality of data segments, which will subsequently be transmitted by the first device to the second device via UWB signals in the form of bursts and distributed over a plurality of intervals. In this example, the scheduling data for the NB poll may also include scheduling information related to the start time of the NB response packet transmission, enabling the second device to schedule the transmission of the NB response packet to the first device at the NB response start time. The second device may then transmit the NB response packet at the desired start time, where the NB response packet conveys second synchronization data, similar to that described above with respect to the synchronization data from the first device to the second device. The first device may use this second synchronization data to schedule and assist in the reception of a second plurality of segments, which may subsequently be transmitted by the second device to the first device via UWB signals distributed over a plurality of intervals. Thus, the NB signaling layer of each device may assist the corresponding UWB signaling layer in terms of synchronization and other functions. Note that assisting the reception of UWB signals resulting from the synchronization data conveyed via the NB signal may include configuring the UWB reception in accordance with the carrier frequency offset and sample frequency offset with respect to the corresponding associated (second or first) device.

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

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

[0059] Additionally, the hybrid wireless transceiver may include a hybrid system controller. The hybrid system controller may coordinate the transmission and reception activities of both the NB and UWB subsystems, as well as the information exchange between the NB and UWB subsystems. For example, the hybrid system controller may receive time and frequency synchronization information from the NB subsystem. In some embodiments, 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 by the NB subsystem. The hybrid system controller may also provide time and frequency configuration information to the UWB subsystem. This may enable the UWB subsystem receiver to configure (e.g., synchronize) more precisely based on the time and frequency information extracted from the NB signaling. Since the time base unit is shared between the NB and UWB subsystems (including any frequency offset relative to the associated device), this configuration information helps to customize the UWB reception for incoming UWB signals (e.g., corresponding to CIRTS segments), thereby improving the receiver efficiency and the performance of CIR estimation. The hybrid system controller may also schedule UWB transmission or reception activities based on the data received from the NB signal and certain transmission / reception parameters (e.g., carrier frequency, UWB bandwidth, etc.). Subsequently, the hybrid system controller may also receive UWB reception information, which includes synchronization data (e.g., time and frequency configuration information) and CIR information. Although the embodiments described herein may refer to separate components of the hybrid wireless transceiver as performing specific operations, the embodiments should not be construed as being so limited. For example, the hybrid system controller may reside within one of the subsystems described herein (e.g., NB or UWB). Any suitable operational partitioning between one or more software and / or hardware components may be applicable to perform the embodiments described herein.

[0060] Continuing with the description introduced above, consider a scenario where a first device and a second device perform two-way exchange of data (e.g., CIRTS fragments) between the two devices. As described herein, the two devices can perform "coarse" initial synchronization. In one example, in a case where the first device operates as an "initiator" device and the second device operates as a "responder" device, the first device can schedule a start time (e.g., discrete time) for transmitting a packet to the second device via an NB signal that conveys synchronization data (e.g., including time and frequency synchronization information). The second device can also schedule a window for receiving the packet from the first device via the NB signal accordingly. It should be understood that in some embodiments, time can be associated with a specific start time (e.g., discrete moment). In some embodiments, time can be associated with a time interval (e.g., window and / or time slot), depending on the context. In some embodiments, the information of the data exchanged during the initial phase can enable the two devices to align (e.g., clock synchronization) with a deviation within an approximately required time increment (e.g., 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 embodiments, this initial phase can be performed for each device by a separate wireless system from a hybrid wireless transceiver. For example, the separate wireless system can utilize the Bluetooth Low Energy (BLE) protocol and / or reside on a separate System on Chip (SOC) device from the hybrid wireless transceiver. In some embodiments, the initial phase including operations such as service advertisement / discovery, connection setup, or coarse synchronization can be performed by the same system that performs the operations of the hybrid wireless transceiver described herein, particularly by the NB subsystem in some embodiments.

[0061] Upon completion of the initial phase, the first (initiator) device may transmit the packet to the second device via an NB signal at the scheduled start time. As described herein, the NB packet may include data that conveys synchronization data to the second device. For example, the packet may include data such as a preamble, a frame start delimiter, and / or other synchronization fields. In some embodiments, the second device may use the packet data to extract synchronization data corresponding to, for example, 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 other synchronization data corresponding to, for example, 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 "Fsync" information), which may be used to synchronize the crystal oscillators (XOs) of two devices described further herein. In some examples, the F sync information may be used to configure the UWB receiver of a device to optimize its frequency correction circuit in preparation for receiving a UWB signal from another device. In some examples, a device may use the time synchronization information (which may also be referred to as "T sync" information) to "anchor" subsequent UWB exchanges according to the timing means of the device described further herein. In some embodiments, the time and / or frequency information may be extracted at least in part based on detecting a pattern (e.g., an expected signal pattern associated with the synchronization header of the packet). As described herein, in some embodiments, the synchronization data may also correspond to scheduling information extracted from the packet payload data. The scheduling information may be used in one example to schedule the reception of subsequent UWB packets (e.g., and / or fragments) from another device (e.g., the first device) by a device (e.g., the second device). It should be understood that the packet payload data may also include other types of information (e.g., non-synchronization data such as status information, control information, etc.).

[0062] It should be understood that different types of synchronization data may be included in transmissions between devices, depending on the context. In a non-limiting example, the first device (e.g., operating as an initiator device) may transmit data that conveys (e.g., indicates and / or enables extraction of) time and frequency synchronization information as well as scheduling information. In this example, the second device may subsequently transmit data that conveys 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, the data included in the NB packet may convey not only the scheduling information for scheduling an NB response packet to another device (e.g., the second (responder) device), but also the scheduling information for scheduling a subsequent UWB response transmission by the second device.

[0063] Continuing with the above description, the second device may then obtain and evaluate the synchronization data from the packet. The second device may use the synchronization data to schedule subsequent reception of the plurality of segments received from the first device via the respective UWB signals. As described herein, the packet may also include scheduling data that the second device uses to schedule a second start time for transmitting a second packet to the first device via a second NB signal. Accordingly, the first device may also schedule a time (e.g., and / or 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 may 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 may obtain (e.g., extract) second synchronization data from the second packet. The first device may then utilize the second synchronization data extracted from the second packet to schedule and facilitate reception of a second plurality of segments to be received from the second device.

[0064] Turning to the transmission and reception of UWB segments performed by each device, the first device may schedule transmission of the plurality of segments to the second device. The scheduling of the transmission of the plurality of segments may be based on synchronization data communicated from the first device to the second device via an NB signal. The first device may then transmit the plurality of segments to the second device. As further described herein, each of the plurality of segments may be temporally separated from the other segments of the plurality of segments by at least a predefined time interval (e.g., 1 ms). In one example, the plurality of segments may collectively correspond to (e.g., represent) a CIRTS that is operable to compute a CIR estimate associated with the wireless propagation path between the first device and the second device. It should be understood that since the CIRTS may be divided into multiple segments (e.g., rather than being transmitted as part of a continuous UWB signal transmission within a single segment), the total amount of energy that may be transmitted by the first device for the segmented UWB transmission may be higher than the energy of a single UWB transmission when complying with certain regional regulatory constraints governing energy emissions in a given area. Additionally, the operating range for the overall UWB transmission may be greater than what might otherwise be possible when the CIRTS is transmitted as a single data segment or a single UWB packet. This may be partly due to enabling the device to aggregate energy from multiple segments. In some embodiments, as further described herein, the plurality of segments may correspond to a particular type of segment sequence (e.g., a pseudo-random sequence (STS), a periodic sequence, a Golay sequence). It should also be noted that limiting the UWB to a single segment representing the CIRTS (rather than multiple segments) is already beneficial because in a conventional UWB transmission, the available transmit energy needs to be shared between the SHR (Sync header) and the CIRTS, while in a hybrid system, the function of the SHR is at least partly delegated to the NB system, thereby alleviating the burden on the UWB system to perform various synchronization tasks.

[0065] When the first device transmits the plurality of segments via UWB signals, 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 according to 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, which is similar to that 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 embodiments, the first device may also obtain synchronization data or other suitable data from the second plurality of segments.

[0066] When a first device calculates an estimated CIR based on a second plurality of segments, the first device may further be capable of calculating a time-of-flight interval, at least 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 at which the plurality of segments (e.g., a first segment of the plurality of segments) are transmitted to a second device and a second time at which the first device receives the second plurality of segments (e.g., a last segment of the second plurality of segments) from the second device. The first device may also determine a turnaround time interval corresponding to a second time increment between a third time at which the second device receives the plurality of segments from the first device and a fourth time at which 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 assist in determining the time-of-flight (TOF). In some embodiments, the TOF may represent the distance (e.g., the distance traveled by a corresponding signal through a direct line-of-sight (LOS) path between the two devices) divided by the speed of light, which may be used to estimate the distance from the TOF. In some embodiments, the turnaround time interval may be a fixed time interval that is known (e.g., in advance) by the first device (and / or the second device). In some embodiments, the second device may then transmit relevant information (e.g., timestamp information via another NB signal) to the first device, which may be used to determine the turnaround time at the second device and to determine the TOF based thereon. 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 embodiments, only the first device may decide to calculate the range / location information. In some embodiments, both the first device and the second device may decide to calculate the range / location 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 then calculate the TOF / range information between the two devices. In some embodiments, 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 in an NB transmission.

[0067] In some embodiments, the exchange of one or more signals (e.g., NB signals and / or UWB signals) may be according to one or more protocols. The use of a particular protocol may depend on, for example, the context and / or intended use for which the signal exchange is performed. For example, one protocol may correspond to the two-way exchange of NB signals (e.g., packets) and may include the combined use of redundant and / or repeated NB packet exchanges with a pseudo-random channel hopping sequence. This may improve the reliability against interference and / or multipath fading phenomena when performing NB signaling to assist in coordinating UWB signaling. In some embodiments of this protocol, NB control information (which may correspond to what channels to use and / or how many hopping channels to use) may be predefined during connection setup (e.g., during an initial phase, as described herein) or exchanged via an out-of-band system (e.g., Bluetooth, BLE, etc.). In another example of a protocol, a one-way NB exchange (including redundant transmissions with channel hopping) may be used. This may be used, for example, to perform a one-way exchange of UWB fragments (e.g., transmitting multiple fragments from a first device to a second device, but not vice versa) in combination with using a beacon protocol. For example, in one beacon protocol, the second (receiver) device may be one of several devices (e.g., an anchor device) 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, at least in part based on an estimated CIR.

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

[0069] In some embodiments, a protocol may be utilized in which a one-way NB exchange is followed by UWB fragments in the same direction. This may allow multiple responder devices to participate in a ranging activity by having the multiple responder devices respond in a known sequence or random order. In yet another example of a protocol, a staggered ranging protocol may be utilized by which an initiator device and a responder device may transmit individual fragments using the same pre-determined time interval. In this example, rather than having the initiator device transmit multiple fragments to the responder device and then the responder device transmit a second multiple of packets to the initiator device, the fragments within the respective multiples of fragments may be staggered. This may reduce the total time used to perform ranging between the two devices.

[0070] In some embodiments, a device may include (e.g., within a separate integrated circuit (IC), combined chip, etc.) at least two partitions, including a first partition that includes an NB entity (e.g., a BLE entity); and a second partition that includes a UWB or NB-UWB entity. In the case where the second partition includes a UWB entity, the UWB entity may conduct UWB ranging rounds. In the case where the second partition includes an NB-UWB entity, the NB-UWB entity may conduct narrowband-assisted (NBA)-UWB-MMS ranging rounds, as described herein. In this example, and as further described herein, a technique may be performed where a device (e.g., a client station) may utilize the BLE entity to receive a BLE advertisement packet (e.g., from another device, such as an anchor station), the BLE advertisement packet may advertise a UWB / NBA-UWB-MMS ranging round (e.g., a UWB ranging round and / or an NBA-UWB-MMS ranging round) that will soon be initiated by the anchor station. At the same time, the BLE entity of the client station may communicate internally with the UWB / NB-UWB entity (e.g., via a data bus connecting the two partitions). For example, the BLE entity may provide the UWB / NB-UWB entity with timing information (e.g., time) that may be operative to schedule the reception of packets and / or fragments (e.g., NB packets, UWB packets, and / or UWB MMS fragments) of the ranging round initiated by the anchor station. In some examples, the timing information may first be converted (e.g., translated) to another time domain (e.g., suitable for scheduling the reception of UWB fragments by the UWB / NB-UWB entity).

[0071] In another example, a device (e.g., an anchor station that may be similarly partitioned to include a BLE entity and a UWB / NB-UWB entity) may determine (e.g., via the UWB / NB-UWB entity) that a ranging round is upcoming. The UWB / NB-UWB entity may transmit (e.g., via the data bus) parameter information to the BLE entity, including the time at which the ranging round will start. The BLE entity may convert (translate) the time to a new time domain (e.g., according to the BLE entity / protocol), and subsequently transmit an advertisement packet including the new time via BLE.

[0072] In some embodiments, this technique may enable a device to utilize the BLE entity to listen for (and / or transmit) advertisements, and then only involve the UWB / NB-UWB entity when appropriate, e.g., when the device determines to participate in a particular ranging round. This mechanism may enable a device to use NB and / or UWB radios to avoid incurring additional discovery and / or acquisition cost penalties. This mechanism may also scale to a large number of devices, many of which may already use BLE for various applications (e.g., indoor navigation, locating lost items, tracking inventory movement, in / out detection, etc.).

[0073] Embodiments of the present disclosure provide several technical advantages over the prior art. In one example, embodiments of the present disclosure enable a hybrid wireless system to perform hybrid signaling that includes tightly coordinated UWB signaling and NB signaling. For example, as described herein, the NB subsystem (e.g., NB signaling layer) of a hybrid wireless system can be used to assist one or more functions of the UWB subsystem (e.g., UWB signaling layer). These subsystems can be tightly coupled based on a common (e.g., shared) timebase and shared MAC functionality 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, and the like. At the same time, the UWB signaling layer can perform short impulse radio bursts distributed over a time interval (e.g., many milliseconds (MMS)). The bursts can represent a segmented UWB transmission (e.g., channel impulse response training sequence (CIRTS) / scrambled time sequence (STS)).

[0074] In some embodiments, the hybrid wireless system can enable the NB signaling layer to be responsible for communicating synchronization data such as time and frequency synchronization information, for example, via the sync header (SHR) of a conventional UWB packet, which can be more efficient than distributing the SHR in multiple SHR fragments via the UWB signaling layer. For example, transmitting multiple SHR fragments without prior knowledge of the arrival time of each fragment may require a large amount of memory for buffering and / or a large amount of processing power. Thus, the amount of memory and / or processing power can be reduced by leveraging the NB signaling layer without using a conventional UWB SHR. At the same time, the CIRTS / STS portion of the UWB packet can be segmented according to the UWB segmentation protocol. The receiver of the segmented packet can utilize the synchronization data transmitted via the NB signaling so that the receiver can accurately schedule the reception (e.g., arrival time) of subsequent received UWB fragments. By implementing segmentation of the UWB transmission, embodiments can enable the receiver of the UWB transmission to achieve higher performance when measuring the propagation channel for extracting geometric and / or positioning metrics such as distance (e.g., range) or angle. For example, the UWB waveform for a given measurement period can be segmented into short bursts (e.g., segmented multi-millisecond (MMS) signaling) and distributed over multiple regulatory (e.g., transmit) test intervals (e.g., according to the regulatory rules of a particular region). The receiver device can utilize the energy “collected” (e.g., aggregated) from various intervals (e.g., within each short burst), thereby achieving a more accurate CIR estimate. Based in part on this CIR estimate, the time of flight, range, position (localization), and / or angle of arrival (AOA) estimates can be determined. Thus, by leveraging a hybrid wireless system capable of tightly coordinated NB and UWB signaling, embodiments achieve at least an improved operating range and operating efficiency of UWB-based signaling.

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

[0076] Due to its large bandwidth (BW) of 500 MHz or more, one beneficial use case of UWB is the "ranging" use case. In some embodiments, ranging may 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 resolve the dense electromagnetic reflections that may exist in the vicinity of these devices, such as floors, ceilings, walls, furniture, cars, plants, electrical appliances, or other artificial 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 car door locks, or other consumer devices can facilitate novel user experiences.

[0077] Figure 1 And Figure 2 (described further below) illustrates a scenario with UWB-equipped devices. In Figure 1 schematic diagram 100, the handheld device 110 communicates with other handheld devices, fixed devices, or Internet of Things (IoT) devices to measure distances or other positioning metrics such as the apparent direction of the devices relative to each other. Devices participating in such communications include phones (e.g., mobile device 120), tags (e.g., pet tag 160), wireless speakers (e.g., wireless speakers 170a, 170b, and 170c), televisions, monitors, doors (e.g., door lock device 140), cars, household appliances (e.g., smart speaker 130), thermostats (e.g., thermostatic control device 150), desktop computers and laptop computers, tablets, etc.

[0078] Figure 2 FIG. 2 is another simplified block diagram 200 showing an example technique for exchanging wireless messages between UWB-equipped devices (or "stations"). Figure 2 Schematic diagram 200 of FIG. 2 shows how UWB device A 202 and UWB device B 204 may exchange wireless messages with each other over time in the form of wireless packets 206a to 206c. In the case of impulse radio (IR) UWB, the waveforms exchanged between the devices contain at Figure 2The UWB pulses shown as p1, p2, p3. This can represent, for example, a string of pulses transmitted from device B 204 to device A 202 in response to a first set of pulses transmitted from A to B. In some embodiments, IR-UWB can be used to perform the techniques described in this disclosure.

[0079] Figure 3 is another simplified block diagram 300 showing at least some example techniques for calculating a channel impulse response (CIR) according to some embodiments. In some embodiments, to enable determination of the mutual range or position of devices, the technique used by a wireless system such as UWB is to calculate the channel impulse response (CIR) 306. The CIR 306 can represent the profile of the direct and indirect (reflected) wireless propagation paths between two devices, such as station A 302 and station B 304, with each path 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 thus the TOF / range corresponding to the first path in the CIR.

[0080] For example, as Figure 3As shown in the schematic diagram 300, a pulse PT 308 is transmitted from station A 302 at time t_A1. In some embodiments, in the case of IR-UWB, the pulse PT 308 can be regarded as representing a long sequence of pulses. In this example of the schematic diagram 300, the 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 an overall delay "TOF" (time of flight) 314 (representing distance divided by the speed of light), the signal passing through the direct (LOS) path PP1 310a arrives at the receiving station B 304 in the form of a pulse PR1 314a at time t_B1. The pulses corresponding to the reflected paths PP2 310b, PP3 310c, and PP4 310d arrive later than the direct path in the forms of PR2 314b, PR3 314c, and PR4 314d, and their arrival times will depend on the travel distances from station A 302 to station B 304 via one or more reflectors experienced by each path. Note that PR1 314a, PR2 314b, PR3 314c, and PR4 314d are examples of the channel impulse response (CIR) 306. In some embodiments, the CIR 306 enables the device to determine a metric such as distance d_AB based on the TOF (derived from the first arrival path PR1 314a itself).

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

[0082] In some embodiments, to estimate the CIR 306 (e.g., sometimes referred to as "channel sounding"), a wireless system including UWB uses what is referred to as a "channel impulse response training sequence" (CIRTS). The CIRTS can be a waveform in the link between two devices that is known to both the transmitter (e.g., device A 202) and the receiver (e.g., device B 204). If the transmitter sends out 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 so that the modified waveform CIRTS1_RX will reach the receiver. Since the receiver knows CIRTS1_TX in advance, it can compare the incoming signal CIRTS1_RX with the known sequence CIRTS1_TX. Subsequently, using algorithms such as corrective mathematical algorithms and other algorithms generally known in the prior art as "channel estimation", the receiver can extract the CIR between the transmitter at device A 202 and the receiver at device B 204.

[0083] Figure 4 is another simplified block diagram 400 showing at least some example techniques for formatting a UWB packet (e.g., Figure 2 packet 206). Figure 4 Shows an example of a type of UWB packet format with its constituent fields and their corresponding purposes, in accordance with the international standard defined for UWB in IEEE 802.15.4z. The Sync header (SHR) 402 at the start of the packet consists of a synchronization (SYNC) preamble 404 and a frame start delimiter (SFD) 406. The SHR 402 has multiple purposes, including automatic gain control generally referred to as "acquisition" or "synchronization" (Sync), frequency offset estimation (frequency Sync or F-Sync), timing estimation (T-Sync), initial channel estimation, etc. 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 case of 802.15.4z, the scrambled timestamp sequence (STS). The STS refers to the CIRTS containing pseudo-random pulses known only to the transmitter and receiver of a given link to ensure secure channel estimation and secure distance measurement. In some embodiments, the CIRTS / STS 408 can be used for accurate and / or secure channel estimation and / or timestamp verification. Figure 4Two additional packet fields are shown, namely a PHY header (PHR) 410 and a payload data (e.g., PHY service data unit (PSDU)) 412. The PHR 410 may contain parameters of the PHY header, and the payload may contain appropriate data content. Note that other packet types are defined for UWB, such as consisting only of the SHR 402 and CIRTS / STS 408 (e.g., "no data packet"), which may be used for channel sounding but without any payload data transmission. There is also a payload-only packet format consisting of the SHR 402 and PHR 410 / payload 412 fields, in which case precise and / or secure channel sounding is not required and the main purpose is data transmission.

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

[0085] Figure 6Another simplified diagram 600 showing an example of the power spectral density associated with the measurement of a UWB signal, according to some embodiments. In some embodiments, the techniques described herein can improve the scenario where CIRTS and the associated CIR estimation steps are distributed across multiple segments covering multiple regulatory / transmission test intervals at a receiver device, which can increase the radiated energy for the transmission of CIRTS. This distribution can also enable an improvement in the operating range.

[0086] Using Figure 6 To further illustrate this context, schematic diagram 600 shows the power spectral density (PSD) 602 for regulatory measurements of a UWB signal. While regulatory rules can vary between countries and regulatory regions, in some regions, exemplary UWB emission 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 embodiments, this measurement can be made using an averaging (spectrum analyzer scan) time of 1 millisecond (1 ms). This means that for this scenario, the maximum amount of energy that the UWB system can transmit per ms corresponds approximately to 37e-9 joules = 37 nanojoules (nJ) per 500 MHz bandwidth per ms. This is shown by the graph 604 near the bottom of schematic diagram 600. The available energy (up to 37 nJ) is 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, since energy is calculated as duration multiplied by power. In some embodiments, there may be peak power constraints governed by UWB regulatory rules in different regions. Thus, compression towards shorter durations can work within certain limits and depends on the density of IR pulses.

[0087] Figure 7 Another simplified block diagram 700 showing at least some example techniques for transmitting data segments within a UWB framework, according to some embodiments. In some embodiments, regulatory constraints are taken into account at least in part by defining a segmented UWB framework, as Figure 7 shown in schematic diagram 700.

[0088] In schematic diagram 700, the transmit frame (TXF) 702 is depicted as being divided into multiple segments 704a to 704c, which are distributed across multiple regulatory test intervals of duration T_test_reg 706. For example, the first segment ("Frag1") 704a can be transmitted during the time interval of T_test_reg 706. For Figure 6 and Figure 7In the example shown, up to 37 nJ can be radiated on each of the segments 704a to 704c. Thus, 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 a predefined time interval of any suitable duration (e.g., 1 millisecond, 1.5 ms, 2 ms, etc.).

[0089] Figure 8 Another simplified block diagram 800 shows at least some example techniques for transmitting data segments associated with UWB packet types, according to some embodiments. In some embodiments, an example UWB packet format for performing UWB transmissions is the packet format of the no-data packet 801, as shown in the schematic diagram 800. Also see above Figure 4 In the example of the schematic diagram 800, the no-data packet 801 includes a Sync header (SHR) 802 and STS / CIRTS 804. Note that the Sync header 802 can include a SYNC preamble and an SFD.

[0090] Fig. 9 Another simplified block diagram 900 shows at least some example techniques for transmitting data segments within multiple time intervals in a UWB frame, according to some embodiments. In Fig. 9 the schematic diagram 900, a no-data packet 902 is shown (e.g., similar to Figure 8 the no-data packet 801 depicted in). The no-data packet can include an SHR field 904 and a CIRTS field 906. The no-data packet is divided into an SHR segment 908 and several (e.g., two in this example) CIRTS segments 910a to 910b. Each CIRTS segment 910 can be transmitted in a separate regulatory test interval to benefit from the full energy budget of its transmission. In some embodiments, it is beneficial to keep these segments short, at least because UWB signal processing can consume a large amount of power due to the high bandwidth and sample rate in the radio and digital modem circuits. Additionally, using shorter segment durations (e.g., and thus longer silent periods between segments) can help minimize the chance of collisions between different links using the same UWB spectrum.

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

[0092] Fig.10Another simplified diagram 1000 shows the potential advantages and disadvantages of at least some wireless systems that utilize UWB signaling 1002 and / or NB signaling 1004, according to some embodiments. In some embodiments described herein, a hybrid wireless system is utilized, in which narrowband (NB) signaling 1004 and ultra-wideband (UWB) 1002 signaling are combined in a manner that addresses the potential challenges presented herein and improves the operational efficiency and / or operational range of the UWB system. In some embodiments, the system that performs narrowband signaling may include a wireless system having a bandwidth significantly less than that of UWB. In some embodiments, UWB may have a minimum bandwidth of 500 MHz, so NB may refer to a system exhibiting a fraction of this bandwidth, such as a few 100 kHz, 1 MHz, or 10 MHz 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 utilized in industrial standards such as Bluetooth or IEEE 802.15.4 O-QPSK (offset quadrature phase shift keying format) such as ZigBee or Thread. Even narrower band modes in wireless local area networks (WLANs) such as IEEE 802.11 modes spanning 20 MHz or 40 MHz spectral bandwidths may also be classified as NB signaling in the context of this disclosure, as they have a bandwidth significantly lower than that of UWB and tend to operate in different spectrums. In some embodiments, they are also regulated by a different set of regulatory constraints than UWB.

[0093] Before turning more specifically to Fig.10 and to provide another background related to regulatory constraints and bandwidth considerations, international regulatory rules governing UWB deployments and associated radiated emissions may define low emission limits for UWB devices, as the latter tend to operate in frequency bands below 10 GHz (primarily for commercial or military operations of point-to-point or satellite links, radar, or other protected applications). Thus, UWB transmissions may be mandated to operate at the level of spurious emissions allowed for other electronic devices (e.g., mobile devices, household devices, etc.), so as not to interfere with such licensed uses. The transmit power for UWB may be limited to -14 dBm on average in many regions.

[0094] In contrast, there are a variety of more narrowband systems and associated regulatory rules that have significantly more relaxed emission limits as they operate in frequency bands targeted for such unlicensed use. The so-called ISM (Industrial, Scientific, Medical) band from 2.4 GHz to 2.5 GHz is a prime example accommodating NB applications such as Bluetooth (BT) or ZigBee / Thread transmissions that are 1 MHz or 2 MHz wide 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 regulatory regions worldwide. There are other ISM-like spectrums which, in many countries, include the 5.725 GHz to 5.875 GHz band. Other spectrums (including much of the 5 GHz to 6 GHz band) are generally also open for various unlicensed, non-UWB uses under certain conditions. The transmit power (radiation level) of these more NB systems is typically in the region of 10 dBm, 20 dBm or even 30 dBm.

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

[0096] Turning now more specifically to Fig.10 , schematic diagram 1000 shows a comparison of the advantages and disadvantages of UWB and narrowband (NB) wireless systems from the perspective of an implementer of a wireless system. UWB signaling 1002 benefits from a larger bandwidth of at least 500 MHz, which is highly beneficial for high-resolution CIR measurements, which in turn can be used for precise positioning and ranging, as outlined above. The wide bandwidth is also beneficial for high-rate data transmission. One of the challenges associated with the larger UWB bandwidth is its need for higher complexity, such as higher analog-to-digital converter (ADC) sample rates and associated signal processing efforts as well as increased analog and digital power consumption. As explained above, UWB regulatory rules also impose significant constraints on the allowed emissions, 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 have higher resistance to interference, especially when operating in a frequency-hopping manner. NB systems also benefit from significantly larger emission limits when operating in spectrums designated for NB / ISM use. However, NB systems are not equally suitable for high-resolution CIR estimation (ranging / sensing), partly due to the inherently restricted bandwidth and thus the restricted resolvability of multipaths in the propagation channel.

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

[0098] In some embodiments, this NB / UWB hybrid structure has certain benefits, which can be achieved by using devices operating according to the embodiments described herein. In some embodiments, the hybrid packet structure enables these devices to address the challenges described above with respect to packet formats such as those having segmented CIRTS (e.g., see Fig. 9 ). This is shown in Fig.12 .

[0099] Fig.12 is another simplified block diagram 1200 showing at least some example techniques for utilizing a hybrid of UWB signaling and NB signaling, according to some embodiments. In Fig.12 schematic diagram 1200, the function of the SHR 1202 is taken over by the NB packet 1204 (e.g., transmitted via an NB signal), and wherein the CIRTS 1206 is divided into multiple (here N) segments 1208a through 1208n. Although the segments 1208 can be transmitted at the start of a predetermined time interval, the embodiments should not be construed as being so limited. For example, in Fig.12 s illustration, the transmission of segment N 1208n is slightly offset from the start of a particular time interval (e.g., the T_test_reg interval, as described and shown for Fig. 9 ). In some embodiments, the initiator and responder devices can transmit configuration information so that the receiver device (e.g., the responder device) can know in advance when the parameters for transmitting the segment will occur. This configuration information can be transmitted via an NB signal. Additionally, although not shown in Fig.12 , note that the segmented UWB transmissions that occur in the context of a hybrid NB / UWB system can carry more than just CIRTS data. It can be based on in accordance with Figure 4The allocation of "data fields" (PHR and payload / PSDU) in replaces some of the CIRTS segments 1208a to 1208n with data payload segments for packets containing data payloads. It should also be noted that the hybrid system concept is beneficial for UWB transmissions that include a single UWB segment (N = 1, see Fig.11 ) and for UWB transmissions that include multiple UWB segments (N > 1, see Fig.12 ), and embodiments with N = 1 and N > 1 are possible.

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

[0101] It should be understood that the division of packet fields into segments as Fig.12 or Fig. 9 shown is for functional purposes. For example, these segments are not necessarily related to the initial non-segmented fields. For example, there is no need to concatenate Fig.12 and / or Fig. 9 the CIRTS segments in to obtain the initial non-segmented CIRTS field. Thus, the segmented fields represent alternatives to the initial packet fields in terms of the required functionality (such as channel (CIR) estimation in the case of segmenting the CIRTS packet structure for the CIRTS field). As described herein, in some embodiments, the NB packet may include a sync field (e.g., within the packet header) and / or a data payload field. In some embodiments, the sync field can be used to convey synchronization data. For example, a receiver device receiving an NB packet (e.g., during a scheduled window) can detect a signal pattern known between the transmitter device and the receiver device. In some embodiments, this signal pattern may be associated with the sync field (e.g., sync header) of the NB packet. When this pattern is detected, the receiver device may be able to extract synchronization data in the form of time and frequency information, as described herein. In some embodiments, the receiver device may also extract synchronization data from the data payload field of the NB packet in the form of scheduling information, for example, that can be used to schedule the subsequent reception of one or more UWB segments.

[0102] Fig.14 Another simplified block diagram 1400 showing two devices configured to communicate with each other using a combination of UWB signaling and NB signaling, according to some embodiments. Fig.14 Schematic diagram 1400 shows 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 that are tightly coupled to each other in each respective device, as further described herein. As part of the communication between Devices A and B, particularly using an "artificial division" between NB and UWB signaling, as previously shown by Fig.11 and Fig.12 shown, the NB subsystem 1408a of Device A 1402 can communicate directly with the NB subsystem 1408b of Device B 1404, and the UWB subsystem 1410a of Device A 1402 can communicate directly with the UWB subsystem 1410b of Device B 1404. In Fig.14 , the NB subsystems 1408a to 1408b and the UWB subsystems 1410a to 1410b in each device are shown as having their own physical antennas 1412a to 1412b and 1414a to 1414b (e.g., including a first antenna 1412a for the narrowband system 1408a and a second antenna 1414a for the UWB subsystem 1410a), but it should be understood that a single shared antenna covering both NB and UWB operations can be a suitable implementation, and multi-antenna solutions can be used for such advanced signal processing schemes as antenna diversity, spatial multiplexing, or transmit or receive beamforming.

[0103] Fig.15 Another simplified block diagram 1500 showing a hybrid wireless transceiver 1502 of a device configured to communicate with another device using a combination of UWB signaling and NB signaling, according to some embodiments. Fig.15The schematic diagram 1500 provides more details of the HWT 1502 in each device and shows the details and functional components of the above-mentioned tight coupling between the NB subsystem 1504 and the UWB subsystem 1506 in the HWT 1502. Each such transceiver includes an NB subsystem 1504 and a UWB subsystem 1506, and each of the subsystems contains wireless transmit and receive circuitry and functions for NB and UWB signaling, respectively. The HWT 1502 is also provided with a shared time base 1508 (e.g., a module or unit), which consists of a crystal oscillator (XO) and any associated clock control and timing devices. The shared time base 1508 enables the NB subsystem 1504 and the UWB subsystem 1506 to form signals that are tightly synchronized in time and frequency. That is, if the NB signal deviates from the shared time base operation and has a certain clock frequency and / or carrier frequency defect (measured in parts per million [ppm] offset), then the UWB signal in the same HWT 1502 may exhibit the same reference defect in ppm. Since the transmit and receive elements of the NB subsystem 1504 and the UWB subsystem 1506 of the device may deviate from the operation of the same shared time base 1508, the clock / carrier offsets (in [ppm]) of the NB Tx (NB signal transmission), NB Rx (NB signal reception), UWB Tx (UWB signal transmission), and UWB Rx (UWB reception) circuitry may be substantially similar (e.g., the same).

[0104] In addition, as Fig.15As depicted, there is a junction controller (hybrid system controller (or control)) 1510 that manages the transmit and receive activities of both 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 transmit or receive activities between a subsystem of a first device and another subsystem of a second device of the same type as the subsystem of the first device. In some embodiments, the hybrid system controller 1510 can coordinate the information exchange between the narrowband subsystem of a first device and the ultra-wideband subsystem of the same (first) device. In some examples, a control block (such as 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 of the NB estimate relative to the associated device. T Sync includes information associated with the air packet timing as measured by the NB subsystem 1504. The control block can also receive payload data information (Rx data) from the NB subsystem 1504. T and F Sync and Rx data can be collectively referred to herein as “NB-Rx-Info”. The control block also schedules the transmit and receive operations performed by the NB subsystem 1504, which can include certain Tx (transmit) / Rx (receive) parameters utilized by the NB subsystem 1504 and possibly payload Tx data.

[0105] The control block also provides time and frequency (T and F) configuration information to the UWB subsystem 1506. This helps to more precisely set the UWB receiver based on the T and F information extracted from the NB signaling. Since there is a shared timebase 1508 (including any frequency offset relative to the associated device) between the NB subsystem 1504 and the UWB subsystem 1506, this configuration helps to customize the UWB reception for incoming UWB signals and maximize the performance of CIR estimation based on CIRTS fragments. The control block also schedules UWB Tx and Rx activities using the NB Rx-Info based on certain Tx / Rx parameters (such as carrier frequency or UWB bandwidth). Subsequently, the control block also receives UWB-Rx-Info that includes synchronization (time / frequency Sync) and CIR information.

[0106] Fig.16 is a simplified flowchart 1600 showing the signal exchange between two devices according to some embodiments. Fig.16 The schematic diagram 1600 of shows the use, respectively, of the overview described herein (e.g., with reference to the above Fig.14 and Fig.15) Signal and control flow diagram for the exchange between two associated HWTs of the HWT structure. The dashed arrows represent wireless exchange between device A 1602 and device B 1604, while the solid arrows represent signals exchanged within each HWT (in device A 1602 or device B 1604). Note that for clarity, the control blocks are not explicitly shown in schematic diagram 1600. 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 the T and F Sync information (which may alternatively 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. The NB subsystem 1612 of device B 1604 responds with its own NB packet "NB-B to A" 1616 back to device A 1602, and device A then extracts the T and F Sync information from the NB packet, and provides the information to its local UWB subsystem 1618 for later use. Subsequently, the UWB subsystem 1618 in device A 1602 sends a UWB transmission "UWB-A to B" 1620 (specifically a series of CIRTS or CIRTIS segments) to the UWB subsystem 1614 in device B 1604. As described above, device B 1604 may be able to effectively determine when to expect a UWB transmission from device A 1602, at least 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 a UWB signal from device A 1602 and how much ppm offset it will have, and the UWB subsystem can use this understanding to minimize signaling processing and maximize the performance of the receiving algorithm and associated receiving circuitry. Device B 1604 then transmits a UWB response "UWB-B to A" 1622, and device A 1602 can receive the UWB response in a targeted manner with higher 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, in accordance with Figure 5 , the exchange of "UWB-A to B" 1620 and "UWB-B to A" 1622 can be a TOF measurement.

[0107] In some embodiments, the T and F synchronization information extracted from the respective NB signals can be of high quality because NB signaling can be subject to less stringent transmission emission rules. Accordingly, the signal-to-noise ratio (SNR) at the receiver side of NB transmissions can be higher and allow for more efficient and accurate acquisition. Compared to the UWB subsystem, the T and F processing in the NB subsystem is also of low complexity and low power, at least because the sample rate is substantially lower than in the UWB subsystem. At the same time, the “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. When compared to other UWB systems, this “division of labor” between the NB and UWB subsystems enables improved operating range and operating efficiency.

[0108] It should be understood that although various modules (e.g., components and / or associated functions) are described as separate from other modules, embodiments should not be construed as being so limited. For example, Fig.15 the hybrid system controller is depicted as a module separate from the shared time base unit, each being separate from both the NB subsystem and the UWB subsystem. However, in some embodiments, the shared time base module and / or the hybrid system control module can reside within one of the subsystems (NB or UWB). In such a case, the respective other subsystem can benefit from the control and time base functions as an auxiliary system or a proxy system (e.g., a delegated system and / or a subordinate system). In any case, the different distribution and / or aggregation of features between different modules can enable hybrid signaling to be performed, as described in the embodiments herein. It should also be understood that, Fig.16 and Fig.17 the signal exchanges shown (described further below) illustrate a particular type of signal exchange of a hybrid wireless system composed of NB and UWB subsystems. Other types of signal exchanges via other hybrid protocols are described further herein. These protocols correspond to different arrangements of NB and UWB transmissions while still employing a hybrid signaling method using devices (e.g., initiator and responder devices) that each include an HWT.

[0109] Fig.17 is another simplified flowchart 1700 showing signal exchange between two devices according to some embodiments. Fig.17 The schematic diagram 1700 is a more detailed schematic of an example signal flow between and within the HWTs of devices A and B (e.g., Fig.16 device A1602 and device B 1604). Additionally, Fig.18 and Fig.19A flowchart showing the processing steps performed by the respective devices, 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"). Thus, the description of the processing steps performed by each device may refer to Fig.17 for further illustration of the signal exchange process. It should be understood that in some embodiments, the initiator device may alternatively operate as the responder device, and similarly, the responder device may alternatively operate as the initiator device, depending on the context.

[0110] Turning more specifically to the processing steps of device A (e.g., device A 1602) depicted in process 1800 as Fig.18 At block 1802, the first device may schedule the NB-Tx start time and the NB-Rx window. In some embodiments, the operation of this block may be performed by the 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 stage of process 1800. The wireless system may be responsible for one or more operations of the initial stage, including processing advertisements and / or scans (e.g., device discovery), performing "coarse synchronization" with the responder 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, the 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., a discrete moment) for transmitting an NB poll packet to the second device may be scheduled, and a time window for receiving an NB response packet from the second device may be scheduled. In some embodiments, the coarse synchronization may enable the respective timing devices of these devices to be synchronized to within approximately 1 ms of each other. This initial coarse synchronization enables subsequent "fine" synchronization via the exchange of NB signals as further described below.

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

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

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

[0114] At block 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) that the first device may use to schedule reception of a second plurality of segments, which are subsequently received by the first device from the second device.

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

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

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

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

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

[0120] As introduced above, Fig.19 is another simplified flowchart showing an exemplary process performed by a responder device according to some embodiments. Similar to the description of the initiator device in Fig.18 , the description of the processing steps performed by the responder device in Fig.19 can refer to Fig.17 (e.g., where device B 1604 operates as the responder device) for further illustration of the signal exchange process. Note that the processing steps in Fig.19 can correspond to equivalent steps of the processing steps in Fig.18 (e.g., from the perspective of the responder device).

[0121] Turning more specifically to the processing steps of device B 1602 (which may be referred to as the "second device") depicted in process 1900 as in Fig.19 , at block 1902, the second device can schedule an NB-Rx time. In some embodiments, the operation of block 1902 can be similar to the operation of block 1802. For example, the wireless system of the second device can perform coarse synchronization with the first device (e.g., Fig.17 and Fig.18 's initiator device A1602).

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

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

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

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

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

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

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

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

[0130] At block 1920, the second device may schedule, configure, and transmit UWB-Tx response segments (in Fig.17depicted as UWB-Tx B to A-1... UWB-Tx B to A-N 1716a to 1716n). In some embodiments, the response segments may correspond to multiple segments (e.g., a second plurality of segments of process 1800 received by the first device from the second device at block 1818). In some embodiments, scheduling the transmission of the plurality of 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 with respect to the first device. For example, the second device may determine round-trip time and / or timestamp information that enables it to determine TOF / range information (see Option 2 of Fig.28 described further herein).

[0131] In some embodiments, with respect to Fig.17 , Fig.18 and Fig.19 embodiments, the number of UWB segments in the forward (A to B "polling") direction may be the same as the number of UWB segments in the reverse (B to A "response") direction, i.e., N. In some embodiments, the number of segments for the forward and reverse directions may be different and may be given as Nf and Nr for the forward and reverse directions, respectively.

[0132] Fig. 20 is another simplified block diagram 2000 showing the use of NB signaling to transmit UWB payload data according to some embodiments. The schematic diagram 2000 depicts embodiments applicable and beneficial in some standards-based UWB packet formats (e.g., see Figure 4 ), where UWB payload data 2002 is concatenated with the SHR 2004 when processed by the NB signaling layer. In some embodiments, the NB subsystem with its associated signaling may assist in coordinating devices A and B for various management and maintenance purposes such as the mutual transmission of status information, as described further herein. In some embodiments, the payload data of UWB packet 2006 may also be transmitted via multiple segments, similar to that described with reference to transmitting CIRTS via UWB segments.

[0133] Fig.21 is another simplified block diagram 2100 showing example waveforms that may be included in one or more segments transmitted by the UWB signaling layer of a device according to some embodiments. Fig.21The schematic diagram 2100 shows the details of the IR waveforms contained in each CIRTS segment 2102a through 2102n used in the UWB signaling layer. Specifically, the schematic diagram lists the various types of sequences that can be used to determine the polarity of the UWB IR pulses in each CIRTS segment 2102. In the packet format compliant with 802.15.4z (see Figure 4 ), the pulse polarity sequence used to represent the CIRTS is based on the sequence from a cryptographically secure pseudorandom generator (CSPRNG) for the STS part of the packet. The case where the same CSPRNG type sequence “R” is used for each section (e.g., segment 2102) is shown as row 1 in the table in Fig.21 . Row 2 shows an implementation where different CSPRNG polarity sequences (“R1”, “R2”, …) determine the IR pulse polarity for each segment. Row 3 represents an implementation where a given CIRTS segment 2102 consists of a periodically repeated short sequence, i.e., the concept of the traditional ternary Ipatov preamble sequence used in IEEE 802.15.4 UWB. Note that such a periodic sequence “E” can use the Ipatov sequence or other periodic sequences where each CIRTS segment 2102 consists of a series (periodically repeated) 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, each CIRTS segment 2102 can use a different periodic sequence (“E1”, “E2”, …). In rows 5 and 6, Gray waveforms are used for each segment. The Gray waveform consists of a pair of sequences transmitted continuously, which 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 expected CIR) can be used to represent “G” in each segment 2102. Different selections of Gray pairs (one or more pairs for each segment 2102) can be used across N segments 2102, such as “G1”, “G2”, … “GN”. A specific implementation using Gray sequences uses multiple Gray pairs for each segment 2102, where 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 one and the same Gray pair. In this latter implementation, again, segments 2102a through 2102n can utilize the same periodic sequence or Gray-based periodic sequences that vary by segment.

[0134] As described herein, embodiments describe a tight coupling of the NB and UWB subsystems to improve the effective operating range. As further described herein, there can be several protocol variants that utilize hybrid signaling via the tight coupling of the NB and UWB subsystems to achieve improved operating range and / or efficiency.

[0135] Fig. 22is another simplified flowchart showing a first part of an exemplary process performed by a device for hybrid signaling, according to some embodiments. In some embodiments, Fig. 22 and Fig.23 process 2200 corresponds to a process for the initiator device to determine a CIR estimate value. (Note that Fig.23 the box of Fig. 22 is a continuation of process 2200 of Fig.18 .) In some embodiments, this process may be similar to process 1800 of Fig.14 and / or Fig.15 performed by the initiator. Process 2200 (and other process flows described herein) are shown as logic flowcharts, where each operation represents a series of operations that can be implemented in hardware, computer instructions, or a combination thereof. In the context of computer instructions, an operation represents computer-executable instructions stored on one or more computer-readable storage media, which, when executed by one or more processors, perform the operation. 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 described operations may be performed in any order and / or in parallel combination 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 hybrid wireless transceiver including reference Fig.14 and / or Fig.15 .

[0136] Additionally, some, any, or all of these processes may be executed under the control of one or more computer systems configured to have executable instructions, and may be implemented as code (e.g., executable instructions, one or more computer programs, or one or more applications) executed jointly on one or more processors, by hardware, or a combination thereof. As described above, the code may be stored on a computer-readable storage medium, such as in the form of a computer program including multiple instructions executable by one or more processors. The computer-readable storage medium is non-transitory.

[0137] In some embodiments, process 2200 may be performed by an initiator device (e.g., “first device”) that exchanges one or more signals with a responder device (e.g., “second device”). As described herein, it should be understood that, depending on the environment, a device may operate as an initiator (device) and / or a responder (device). Thus, for example, one or more operations of process 2200 may also apply (e.g., be similar) to a first device operating as a responder device.

[0138] Turning more specifically to process 2200, at block 2202, a first device (initiator) may schedule a start time (e.g., discrete time) for transmitting a packet to a second device (responder) via a narrowband (NB) signal. In some embodiments, one or more operations of block 2202 may be similar to Fig.18 the operations of block 1802 of

[0139] At block 2204, the first device may schedule a window for receiving a second packet transmitted from the second device to the first device via a second narrowband signal. In some embodiments, one or more operations of block 2204 may be similar to Fig.18 the operations of block 1802 of

[0140] At block 2206, the first device may transmit the packet to the second device via the narrowband signal at the start time. In some embodiments, the packet may include data indicating to the second device, e.g., a time period for receiving a plurality of segments. For example, the packet may convey synchronization data that may be used by the second device to schedule and / or assist in receiving the plurality of segments via an ultra-wideband (UWB) signal, respectively. In some embodiments, one or more operations of block 2206 may be similar to Fig.18 the operations of block 1804 of

[0141] At block 2208, the first device may receive the second packet from the second device via the second narrowband signal during the window. In some embodiments, one or more operations of block 2208 may be similar to Fig.18 the operations of block 1808 of

[0142] 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 Fig.18 the operations of block 1810 of

[0143] At block 2212, the first device may schedule the transmission of the plurality of segments via the ultra-wideband signal. In some embodiments, the scheduling may be performed according to the synchronization data previously communicated to the second device (e.g., at block 2206, including scheduling information). In some embodiments, one or more operations of block 2212 may be similar to Fig.18 the operations of block 1812 of

[0144] Continue Fig.23In block 2214, the first device may 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 may be temporally 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 may be similar to Fig.18 the operations of block 1814 of

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

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

[0147] At block 2220, the first device may determine a channel impulse response (CIR) estimate based at least on the 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 device and the second device. In some embodiments, one or more operations of block 2220 may be similar to Fig.18 the operations of block 1820 of

[0148] Fig.24 is another simplified flowchart 2400 showing signal transmission according to a two-way redundant packet switching protocol using one or more NB channels, according to some embodiments. Joint use of redundant / repeated NB packet switching (e.g., referring to, for example, Fig.18 block 1804 of Fig.19 and / or block 1912 of Fig.24The schematic diagram 2400 depicts an example of this scheme with triple redundant transmissions using pseudo-random channels. The term "channel" herein refers to the specific radio spectrum location when transmitting an NB, such as a carrier frequency in GHz (such as, for example, 2.450 GHz or 5.806 GHz or 5.912 GHz), around which the NB signal is centered with its specific spectral bandwidth (such as 1 MHz or 2 MHz or several hundred kHz). Some channels may be congested by other wireless users or suffer from signal fading common in wireless communications in a multipath environment, and "hopping" across channels helps reduce packet loss caused by these phenomena. The initiator 2402 (for example, one of the initiator devices described herein in the initiator device) initiates a first message in an initiation packet, and the responder 2404 attempts to receive the first message. In some embodiments, this scheme can be further optimized to save power by using the following rules: (a) the initiator 2402 skips the remainder of the NB exchange when it receives any of (2), (4), and (6); (b) the responder 2404 should always listen to (1), (3), and (5), but transmit (2), (4), and / or (6) only when its immediately preceding reception is successful. This scheme can be referred to as a two-way NB exchange since NB packets are exchanged on both sides. If the subsequent closely coupled UWB exchange also involves two-way messages / fragments (for example, as Fig.17 depicted), then this protocol may be useful. As described herein, an NB redundancy and channel hopping configuration can be exchanged out-of-band (OOB) using a device radio frequency (RF) protocol. In some embodiments, a wireless system separate from the HWT on the device (for example, OOB) can be used to coordinate NB control information (for example, leveraging Bluetooth / BLE during connection setup).

[0149] Fig.25 is another simplified flowchart according to some embodiments showing message exchange between two devices according to a two-way redundant packet exchange protocol using one or more NB channels. In some embodiments, Fig.25 the message exchange of the process 2500 can correspond to the protocol depicted in reference Fig.24 should be understood that some operations associated with the process 2500 (such as scheduling NB signals, transmission of UWB fragments, etc.) (and / or other processes further described herein) can be performed additionally before, during, or after the operations of the blocks depicted in the process 2500. Therefore, it should be understood that the simplified protocol shown in the process 2500 (and / or other processes described herein) can also include other operations and / or protocol variations of the present disclosure (such as full ranging protocol, beacon protocol, etc.) (and / or be included within other operations and / or protocol variations of the present disclosure).

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

[0151] 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 second initiation packet may be transmitted at least in part based on determining 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. Note that if the second device has transmitted the first response packet, the first device may not have transmitted the second initiation packet to the second device. In some embodiments, the second initiation packet may be transmitted even if the first device has received the first response packet from the second device.

[0152] 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 third initiation packet may be transmitted at least in part based on determining that the first device has not received a second response packet from the second device via the second narrowband channel in response to the second initiation packet.

[0153] At block 2508, the first device may receive a third response packet from the second device via the third narrowband channel in response to the third initiation packet. At this block, the first device may then terminate the exchange of NB packets according to the protocol described in reference Fig.24 .

[0154] Fig.26 FIG. 2600 is another simplified flowchart showing signal transmission according to a unidirectional redundant packet transmission protocol using one or more NB channels according to some embodiments. Fig.26 Similar to Fig.24 , but in this case, only one side transmits NB packets (e.g., initiator 2602 to responder 2604). Embodiments employing a beacon protocol (e.g., further described herein with respect to Fig.34 ) may benefit from this method. As described in reference Fig.24 , in some embodiments, an OOB system may be used to coordinate the transmission of NB control information (e.g., via Bluetooth / BLE).

[0155] Fig. 27 FIG. is another simplified flowchart showing message exchange between two devices according to a unidirectional redundant packet transmission protocol using one or more NB channels according to some embodiments. In some embodiments, Fig. 27 The message exchange of Fig.26 may correspond to the protocol depicted in

[0156] At block 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.

[0157] At block 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.

[0158] At block 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 and second narrowband channels.

[0159] Fig.28 is another simplified flowchart 2800 showing signal transmission of a non-interleaved ranging protocol using a known fixed round-trip time according to some embodiments. Fig.28 The schematic diagram 2800 of Fig.24 depicts a full ranging protocol using hybrid signaling as described herein. This two-way NB exchange is the same as that shown in

[0160] Fig.29 is another simplified flowchart showing message exchange based on a known fixed round-trip time according to some embodiments. In some embodiments, Fig.29 the message exchange of the process 2900 of Fig.28 may correspond to the protocol depicted in

[0161] At block 2902 of process 2900, a first device (e.g., initiator 2802) may transmit a packet to a second device (e.g., responder 2804) via a narrowband signal. In some embodiments, the packet 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 Fig.18 the operations of block 1804 of

[0162] 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 a plurality of UWB segments from the first device. The first device may also schedule the transmission of the plurality of UWB segments based on the synchronization data. Fig.19 At block 2904, the first device may receive a second packet from the second device, the second packet conveying second synchronization data to the first device via a second narrowband signal. In some embodiments, one or more operations of block 2904 may be similar to

[0163] the operations of block 1808 of Fig.24 and Fig.25 As described herein, the first device may obtain and utilize the second synchronization data to schedule the reception of a plurality of UWB segments from the second device. The second device may also schedule the transmission of a second plurality of segments based on the second synchronization data.

[0164] In some embodiments, blocks 2902 and 2904 may be repeated according to the scheme described in reference

[0165] At block 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 temporally separated from other segments of the plurality of segments by at least a predefined time interval (e.g., according to relevant regulatory rules for the transmission standard).

[0166] At block 2908, the first device may receive a second plurality of segments from the second device via a second ultra-wideband signal, respectively. In some embodiments, the first time at which the first segment of the second plurality of segments is transmitted to the first device is offset from the first time at which the 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 may be used to calculate range or time of flight. For example, the first device may determine the round-trip time and then may use the round-trip time to determine the TOF.

[0167] Fig.30 Another simplified flowchart 3000 showing a non-interleaved ranging protocol according to some embodiments, the non-interleaved ranging protocol including NB signal exchange for transmitting round-trip time and / or turn-around time after two-way exchange of UWB segments. Fig.30 The schematic diagram 3000 of Fig.28 is similar, but after the exchange of UWB segments between the initiator 3002 and the responder 3004, unidirectional / bidirectional NB packets are used to transmit round-trip time and / or turn-around time and an optional status report. This may be useful if the device does not have a fixed turn-around time capability or if both sides need to know the range / TOF. Note that unidirectional NB exchange can be used when only one side needs to know the range, and bidirectional NB exchange enables both sides to calculate the range.

[0168] Fig.31 Another simplified flowchart showing message exchange using NB signal exchange after two-way exchange of UWB segments according to some embodiments. In some embodiments, Fig.31 the message exchange of the process 3100 of Fig.30 may correspond to the protocol depicted in

[0169] At block 3102 of process 3100, a first device (e.g., initiator 3002) may transmit a packet to a second device (e.g., responder 3004) via a narrowband signal, the packet conveying synchronization data. In some embodiments, one or more operations of block 3102 may be similar to Fig.29 the operations of block 2902 of

[0170] At block 3104, the first device may receive a second packet from the second device, the second packet conveying second synchronization data via a second narrowband signal. In some embodiments, one or more operations of block 3104 may be similar to Fig.29 the operations of block 2904 of

[0171] In some embodiments, blocks 3102 and 3104 may be repeated according to the scheme described in Fig.24 and Fig.25 At block 3106, the first device may transmit a plurality of segments to the second device via an ultra-wideband signal, each segment of the plurality of segments being temporally separated from other segments of the plurality of segments by at least a predefined time interval. In some embodiments, one or more operations of block 3106 may be similar to

[0172] the operations of block 1814 of Fig.18 At block 3106, the first device may transmit a plurality of segments to the second device via an ultra-wideband signal, each segment of the plurality of segments being temporally separated from other segments of the plurality of segments by at least a predefined time interval. In some embodiments, one or more operations of block 3106 may be similar to

[0173] At block 3108, the first device may receive a second plurality of segments from the second device via a second ultra-wideband signal, respectively. In some embodiments, one or more operations of block 3108 may be similar to Fig.18 the operations of block 1818 of

[0174] 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, the information may include at least one of the following: (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. The fourth packet may convey a similar type of information as the information included in the third narrowband signal. This data may allow the second device to also calculate the range. As described 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.

[0175] In some embodiments, block 3110 may be repeated according to the schemes referenced in Fig.24 and Fig.25 and / or Fig.26 and Fig. 27 as described.

[0176] Fig.32 FIG. 3200 is another simplified flowchart showing signal exchange according to a one-way NB and non-interleaved UWB ranging protocol, according to some embodiments. Fig.32 Schematic diagram 3200 of FIG. depicts another variant, where a one-way NB exchange between an initiator 3202 and a responder 3204 is followed immediately by UWB segments in the same direction. By having multiple responders 3204 respond in a known sequence or random order, this scheme may allow the multiple responders to participate in a ranging exercise. In some embodiments, the responder may either include a timestamp in the response NB packet or respond using a fixed turnaround time scheme (as described herein). The initiator 3202 may thereby calculate the corresponding range, as described herein.

[0177] Fig.33 FIG. is another simplified flowchart showing message exchange according to a one-way NB and non-interleaved UWB ranging protocol, according to some embodiments. In some embodiments, Fig.33 the message exchange of process 3300 of FIG. may correspond to the protocol depicted in reference Fig.32 FIG.

[0178] At block 3302, a first device (e.g., initiator 3202) may transmit a packet to a second device (e.g., responder 3204) via a narrowband signal, the packet conveying synchronization data. In some embodiments, one or more operations of block 3302 may be similar to Fig.18 the operations of block 1804 of Fig.26 and Fig. 27 The scheme described is repeated for block 3302.

[0179] At block 3304, the first device may transmit the plurality of fragments to the second device via an ultra-wideband signal. In some embodiments, one or more operations of block 3304 may be similar to Fig.18 the operations of block 1814 of

[0180] At block 3306, the first device may receive a second packet from the second device, the second packet conveying second synchronization data via a second narrowband signal. In some embodiments, one or more operations of block 3306 may be similar to Fig.18 the operations of block 1808 of Fig.26 and Fig. 27 The scheme described is repeated for block 3306. Note that in this case, the first device may receive the second packet after the transmission of the plurality of fragments at block 3304. In some embodiments,

[0181] At block 3308, the first device may receive a second plurality of fragments from the second device via a second ultra-wideband signal, respectively. In some embodiments, one or more operations of block 3308 may be similar to Fig.18 the operations of block 1818 of

[0182] Fig.34 FIG. 3400 is another simplified flowchart showing signal exchange according to a beacon protocol according to some embodiments. As described above, in some embodiments, the beacon protocol may be employed when NB signals (e.g., NB packets) and UWB signals (e.g., a plurality of fragments) are transmitted on only one side (such as the initiator 3402). For example, this may be useful if the second (receiver) device is one of several devices of interest 3404 that interact with the 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, at least in part based on an estimated CIR. In some embodiments, the initiator 3402 may send periodic beacon messages. Note that the beacon protocol still utilizes the hybrid signaling method as described herein.

[0183] Fig.35is another simplified flowchart showing message exchange according to a beacon protocol, according to some embodiments. In some embodiments, Fig.35 the message exchange of process 3500 may correspond to the protocol depicted in reference Fig.34 described.

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

[0185] At block 3504, the first device may transmit the packet to one or more devices of interest 3404 via the narrowband signal at the scheduled start time. In some embodiments, the packet may convey synchronization data that is used by the second device to schedule the reception of multiple segments, respectively, via an ultra-wideband (UWB) signal. In some embodiments, one or more operations of block 3504 may be similar to Fig.18 the operations of block 1804 of

[0186] In some embodiments, blocks 3502 and 3504 may be repeated according to the scheme described in reference Fig.26 and Fig. 27 described.

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

[0188] At block 3508, the first device may transmit the multiple segments to the second device via the ultra-wideband signal. In some embodiments, each of the multiple segments may be temporally separated from other segments of the multiple segments by at least a predefined time interval. In some embodiments, one or more operations of block 3308 may be similar to Fig.18 the operations of block 1814 of

[0189] Fig.36 is another simplified flowchart showing signal exchange according to an interleaved ranging protocol, according to some embodiments. In the interleaved ranging protocol as shown in Fig.36 process 3600, the protocol works by having initiator 3602 and responder 3604 use the same T_test_reg (see Figure 7) to bisect the UWB segment exchange time. In this case, the TX and RX UWB segments are interleaved. This interleaved UWB exchange is preceded by a two-way NB exchange and followed by a one-way or two-way timestamp / status NB exchange (see Fig.30 ). In some embodiments, by enabling both the initiator 3602 and the responder 3604 to transmit their respective UWB segments using the same time interval, this protocol can significantly reduce the total ranging exchange time. It should be understood that the transmission and / or reception attempts of the UWB segments themselves can be conditional upon the successful reception of NB packets. In some embodiments, this can help optimize power.

[0190] Fig.37 is another simplified flowchart showing message exchange according to an interleaved ranging protocol in accordance with some embodiments. In some embodiments, Fig.37 the message exchange of process 3700 may correspond to the protocol depicted in reference Fig.36 .

[0191] At block 3702 of process 3700, a first device (e.g., initiator 3602) may transmit a packet to a second device (e.g., responder 3604) via a narrowband signal, the packet conveying synchronization data. In some embodiments, one or more operations of block 3702 may be similar to Fig.29 the operations of block 2902 of

[0192] At block 3704, the first device may receive a second packet from the second device, the second packet conveying second synchronization data via a second narrowband signal. In some embodiments, one or more operations of block 3704 may be similar to Fig.29 the operations of block 2904 of

[0193] In some embodiments, blocks 3702 and 3704 may be repeated according to the scheme described in reference Fig.24 and Fig.25 .

[0194] At block 3706, the first device may 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 Fig.18 the operations of block 1814 of

[0195] At block 3708, the first device may receive a first fragment of the second plurality of fragments from the second device. In some embodiments, the first fragment of the second plurality of fragments may be transmitted via a second ultra-wideband signal. In some embodiments, the first device receives the first fragment of the second plurality of fragments within a predefined time interval that defines the time spacing between the first and second fragments of the plurality of fragments. In some embodiments, one or more operations of block 3708 may be similar to Fig.18 the operations of block 1818. Note that in this case, the individual respective fragments from each plurality of fragments are interleaved when transmitted / received by the respective devices.

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

[0197] At block 3712, the first device may receive a second fragment of the second plurality of fragments from the second device. It should be understood that multiple rounds of interleaved fragments may be exchanged between the two devices (e.g., multiple rounds of operations including blocks 3710 and 3712) until the complete respective plurality of fragments have been exchanged between the devices.

[0198] At block 3714, the first device may receive a packet from the second device via a narrowband signal, the packet including information that may be used to determine range or time of flight, the information including at least one of the following: (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 Fig.31 the operations of block 3110. Note that in some cases, the first device may also (and / or alternatively) transmit a packet via a narrowband signal that enables the second device to also determine ranging information, depending on the context. In some embodiments, the operations of block 3714 may be repeated in accordance with the schemes referenced in Fig.24 and Fig.25 and / or Fig.26 and Fig. 27 and

[0199] Fig.38Another simplified block diagram 3800 showing the use of a separate wireless system for initial device discovery and connection setup, according to some embodiments. Diagram 3800 depicts the NB-assisted concept extended to include another wireless system that can assist with initial device discovery and connection setup as described herein. In this example, a wireless system (e.g., BLE 3802) can be used for initial coarse alignment of the device before handing control over to the hybrid NB+UWB transceiver 3804. In some embodiments, BLE 3802 can handle advertisement / 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 "collect" multiple milliseconds of UWB energy from dedicated segments 3806a to 3806c for TOF / AOA estimation.

[0200] Fig.39 Another simplified block diagram 3900 showing the use of a separate wireless system for initial device discovery and connection setup, according to some embodiments. Fig.39 Diagram 3900 shows a specific implementation where an additional wireless system (such as BLE 3802) and an HWT are located on separate system-on-chips (SOCs 3906a to 3906b and 3908a to 3908b) on the same device (device A 3902 or device B 3904), respectively.

[0201] Fig.40 A simplified block diagram 4000 showing a technique for advertising UWB / narrowband-assisted (NBA)-UWB-MMS ranging rounds via NB signals, according to some embodiments. Specifically, Fig.40 Figure 4000 shows a mechanism that allows multiple UWB and / or NBA-UWB-MMS devices to use BLE advertisements to provide discovery and timing acquisition. For additional environments, BLE is available in many devices that can benefit from range measurements for a variety of use cases, such as indoor navigation, locating lost items, tracking inventory movement, in / out detection, etc. Ranging techniques based on pure UWB impulse radio and / or NBA UWB MMS are applicable to many of these use cases. Thus, these UWB and / or NBA-UWB-MMS devices can use the ubiquitous BLE technology for device discovery and timing acquisition. In some devices, the BLE entity (e.g., BLE subsystem 4002) and the UWB / NBA-UWB entity (e.g., UWB / NBA-UWB subsystem 4004) are juxtaposed as separate integrated circuits (ICs) on a printed circuit board (PCB) in a single package or combined chip. By using a conveyance / signaling conduit (e.g., Fig.40As used herein, NB-UWB-BT transport 4006 enables the coordination of over-the-air (OTA) activities between these technologies. In some embodiments, NB-UWB-BT transport 4006 may include any suitable data bus, including, for example, a Serial Peripheral Interface (SPI), a Direct Memory Access (DMA) interface, or a Peripheral Component Interconnect Express (PCIe) interface. In some embodiments, these two different technology entities (e.g., chips and / or partitions) may establish a shared time concept via PCIe using various well-established methods such as Precise Time Measurement (PTM). In some embodiments, a UWB / NBA-UWB beacon device (e.g., associated with a UWB / NBA-UWB entity) may share its beacon schedule or next beacon time (e.g., together with ranging metadata) via NB-UWB-BT transport 4006. A BLE entity may use this knowledge to advertise this time (translated into the BT domain) via BLE advertisement packets 4008 to dual-purpose its role as both a BLE discovery / acquisition and a UWB / NBA-UWB acquisition mechanism. In FIG. 4000, the NB-UWB entity first transmits the start time of its ranging round (denoted as Tx) to the BLE entity. The BLE then converts the time into its own time domain (denoted as f(Tx)), potentially referencing the advertisement packet in which it was transmitted. Once ranging round X 4010 is complete, the NB-UWB entity transmits the start time (Tx+1) of the next ranging round X+1 4012 to the BLE entity. The BLE entity transmits two advertisement packets 4014a to 4014b referencing the same ranging round X+1 4012 since the ranging round is the next ranging round in both cases. This mechanism allows a device receiving BLE advertisement packets 4014a to 4014b to also connect to UWB / NBA-UWB-MMS ranging at any time using the time reference of the next ranging round without incurring additional discovery or acquisition penalties using the NB and / or UWB radios. In some embodiments, this mechanism may be extended to a large number of devices and allows for various ranging techniques, such as those further described herein Fig.42 The ranging techniques shown in

[0202] Fig.41 is a simplified flowchart showing a technique for advertising UWB / NBA-UWB-MMS ranging rounds via an NB signal (e.g., BLE) according to some embodiments. In some embodiments, process 4100 describes operations similar to those described with reference to Fig.40 as described

[0203] At block 4102, a first subsystem of a first device (e.g., a client station or an anchor station) (e.g., Fig.40The NB-UWB entity 4004) determines parameter data for a UWB / NBA-UWB-MMS ranging round, the parameter data indicating a first time (e.g., Fig.40 the time Tx in) for initiating the ranging round 4010. In some embodiments, the first time is associated with a first time domain (e.g., the UWB entity time domain) for performing UWB ranging. In some embodiments, the parameter data further includes metadata associated with the UWB / NBA-UWB-MMS ranging round 4010, the metadata indicating at least one of the following: (I) packet type, (II) number of segments to be transmitted, (III) channel type, (IV) channel hopping pattern, (V) security parameters, or (VI) timestamp exchange method. It should be understood that these are representative examples of metadata that can be transmitted and are used to indicate parameters for participating in a UWB / NBA-UWB-MMS ranging round.

[0204] At block 4104, the first subsystem transmits the parameter data to a second subsystem of the first device (e.g., Fig.40 the BLE entity 4002 of), whereby the first subsystem and the second subsystem are communicatively coupled via a data bus of the first device (e.g., Fig.40 the NB-UWB-BT conveyance). In some embodiments, the first subsystem and the second subsystem are partitioned within the same IC or different ICs, as described with reference to Fig.40 . In some embodiments, the data bus connects different partitions. In some embodiments, the second subsystem includes an NB subsystem that performs wireless signaling via the Bluetooth Low Energy (BLE) protocol. In some embodiments, as described herein, the data bus includes at least one of the following: (I) Serial Peripheral Interface (SPI), (II) Direct Memory Access (DMA) interface, or (III) Peripheral Component Interconnect Express (PCIe) interface. In some embodiments, the first subsystem includes a UWB subsystem. In some embodiments, the first subsystem further includes an NB subsystem, whereby the UWB and the NB subsystem are coupled together within a hybrid wireless transceiver of the first subsystem (e.g., for performing NBA-UWB-MMS ranging), as described herein.

[0205] At block 4106, the second subsystem determines a second time (e.g., Fig.40 f(Tx) in) at least in part based on the first time, whereby the second time is associated with a second time domain (e.g., the BLE entity time domain) for performing NB signaling via BLE. In some embodiments, the second time may correspond to a time offset when an advertisement packet (described further below) is scheduled for transmission by the first device.

[0206] At block 4108, the first device transmits an advertisement packet 4008 indicating a second time via an NB signal (e.g., via BLE). In some embodiments, the advertisement packet 4008 may also indicate one or more of the metadata described with reference to block 4102 (e.g., including ranging round parameters). In some embodiments, the advertisement packet 4008 includes second parameter data associated with the ranging round 4010. In some embodiments, the second parameter data may include metadata and / or other suitable information, similar to that described with reference to block 4102. In some embodiments, the advertisement packet is received by a second device (e.g., another client station or an anchor station). In some embodiments, the second device determines a first time using the second time. For example, a third subsystem (e.g., a BLE subsystem) of the second device may determine the first time based on the second time. In some embodiments, if the second device determines to participate in a UWB / NBA-UWB-MMS ranging round, the third subsystem may transmit data (e.g., indicating the first time and / or other ranging round parameters included in the advertisement packet) to a fourth subsystem (e.g., a UWB / NB-UWB entity) of the second device via a data bus (e.g., similar to that described for the first device). In some embodiments, the fourth subsystem may then schedule, at least in part, one or more ranging packets / fragments received by the second device from the first device during the UWB / NBA-UWB-MMS ranging round based on data indicating the first time (e.g., Tx) and / or the second parameter data included in the advertisement packet. In some embodiments, as Fig.40 depicted, the first device (e.g., an anchor station) may broadcast a periodic advertisement for performing a UWB ranging round. In some embodiments, the second device (e.g., a client station) is one of a plurality of client stations configured to receive NB signals from the anchor station, as further described below with reference to Fig.42 . In some embodiments, the second device may determine not to participate in the UWB / NBA-UWB-MMS ranging round. It should be understood that, as described herein, the first device and the second device may have similar (or different) architectures. In some embodiments, the devices may be enabled to perform the role of either / both an initiating device (e.g., transmitting an advertisement packet for performing a ranging round, as Fig.40 depicted) or a responding device (e.g., receiving the advertisement packet and then using the information to schedule participation in the ranging round).

[0207] At block 4110, the first device initiates a UWB / NBA-UWB-MMS ranging round 4010 at a first time. In some embodiments, one or more operations of block 4110 may be similar to those described with reference to block 2214 of Fig.23 or block 2206 of Fig. 22 .

[0208] Fig.42 is a simplified block diagram showing techniques for operating a hybrid (UWB / NB) system (e.g., including a hybrid wireless transceiver as described herein) in an environment including an anchor station and a client station, according to some embodiments. Fig.42 Schematic diagram 4200 shows an embodiment of a hybrid system among multiple stations in two device categories - anchor stations 4202a to 4202n and client stations 4204a to 4204n. In some embodiments, anchor stations A1, A2, … A10 4202a to 4202n represent devices with synthetic system capabilities, which may be fixed devices, possibly mounted on a wall or ceiling, and connected to a permanent power source (such as a conventional 110V or 220V main system). In some embodiments, client stations C1, C2, … to C100 4204a to 4204n can be mobile battery-operated devices, such as a mobile phone or a wrist-worn smartwatch. The anchor stations 4202a to 4202n, which can be installed in a home, a shopping mall, or a warehouse, can provide positioning services to the client stations 4204a to 4204n, which may be in an indoor or outdoor local area. In this infrastructure-type embodiment of the present invention, the anchor stations 4202a to 4202n can transmit hybrid signals composed of NB and fragmented UWB packets according to the present invention in a synchronized manner at certain time instances offset from each other. This allows the client stations 4204a to 4204n to use the NB signal in a listen-only mode to assist in the effective reception of fragmented UWB transmissions and use a trilateration technique to determine their own positions in a local geographic map, assuming the positions of the anchor stations 4202a to 4202n are known. Alternatively, also using NB-assisted fragmented UWB signaling, the anchor stations 4202a to 4202n can communicate actively and bidirectionally with each other in a point-to-point or point-to-multipoint manner. In this case, the client stations 4204a to 4204n can listen to these anchor-to-anchor communications and deduce their respective positions based on the anchor-to-anchor communications. In some embodiments, as referred to above Fig.40As described, a station (e.g., an anchor station 4202) may include a BLE entity that can transmit periodic advertisement packets, whereby nearby stations (e.g., client stations 4204a to 4204n) may include their own respective BLE entities that listen for the advertisement packets. In the event that a particular client station 4204 determines to participate in a ranging round using a particular anchor station 4202, the client station 4204 may use the information included in the advertisement packet to schedule the reception of a UWB packet (e.g., including UWB fragments) for the next ranging round. In some embodiments, the anchor station 4202 is one of a plurality of anchor stations 4202a to 4202n located within a local area that also includes the client station 4204. In this case, the client station 4204 may determine its position within the local area at least in part based on measuring the respective ranges between the client station 4204 and at least two of the plurality of anchor stations 4202a to 4202n.

[0209] Fig.43 is another simplified block diagram 4300 showing a technique for performing a ranging round using a hybrid of UWB signaling and NB signaling, according to some embodiments. Fig.43 The schematic diagram 4300 shows the overall structure of a single ranging round. In some embodiments, during a ranging round, a single ranging measurement is performed between two devices. In some embodiments, a ranging round has three parts: an NB preamble exchange 4306, a UWB MMS exchange 4308, and an NB epilogue exchange 4310. In some embodiments, the NB preamble exchange 4306 and / or the NB epilogue exchange 4310 may optionally be used only when beneficial. For example, either / both exchanges may be performed based on pre-negotiated session parameters and / or the dynamic conditions / status of the ranging itself. In some embodiments, all NB exchanges within a ranging round may use a single channel to maximize the collective success of all exchanges. In some embodiments, the responder 4302 obtains time (T) and frequency (F) synchronization data by receiving an NB_POLL, and the initiator 4304 does the same when it receives an NB_RSP. In some embodiments, as described above, depending on various pre-negotiated session parameters and / or dynamic conditions, NB_DATA may optionally transmit status, configuration, and timestamp parameters. In some embodiments, the UWB MMS exchange 4308 is the only mandatory part of a ranging round, and it may use an interleaved ranging protocol or a non-interleaved ranging protocol. In some embodiments, if the initiator 4304 attempts to determine the range between the initiator 4304 and the responder 4302 (e.g., via pre-negotiation of session parameters), the responder 4302 may transmit data (NB_DATA_RI, as Fig.43 depicted therein) to the initiator 4304, thereby indicating the round-trip time (e.g., see Figure 5)。In some embodiments, if responder 4302 attempts to determine range, initiator 4304 may transmit data (NB_DATA_IR, as depicted in Fig.43 ) to responder 4302 to indicate round-trip time. In some embodiments, if two devices negotiate a fixed turn-around time, NB epilogue exchange 4310 may not be performed (e.g., because the range may be determined by the devices of interest partly based on the fixed turn-around time). In some embodiments, if the devices do not negotiate a fixed turn-around time, the devices may "back off" data (depending on the device transmitting the packet) via NB_POLL and / or NB_RSP packets for the next ranging round, rather than transmitting data via NB epilogue exchange 4310. For example, in the case where only responder 4302 wishes to calculate range, initiator 4304 may transmit the round-trip time to responder 4302 within a subsequent NB_POLL transmitted to initiate the next ranging round. In some embodiments, as described herein, for example, if the environmental conditions (e.g., SNR) between the devices render NB preamble exchange 4306 unnecessary, NB preamble exchange 4306 may not occur.

[0210] Fig.44 is a simplified block diagram 4400 showing ranging session parameters according to some embodiments. Fig.44 The schematic diagram 4400 lists various parameters (non-exhaustive), such as NB parameters 4402 controlling the ranging rounds and UWB MMS parameters 4404. These parameters may be exchanged out-of-band (OOB) via another radio protocol such as Bluetooth (e.g., BLE), in-band via NB packets, and / or some parameters may be exchanged OOB and other parameters via NB.

[0211] Fig.45 is a simplified block diagram 4500 showing ranging parameters that may be dynamically adjusted between ranging rounds according to some embodiments. Fig.45 The schematic diagram 4500 lists example status, configuration, and timestamp information (e.g., parameters 4502) that may be exchanged between the devices. In some embodiments, these parameters 4502 may vary dynamically (e.g., between ranging rounds). In some embodiments, these parameters 4502 may be exchanged via the NB system (e.g., the NB subsystem of a hybrid radio transceiver, as described herein). In some embodiments, these parameters 4502 may be exchanged via a BT / BLE companion link.

[0212] Fig.46 is a simplified block diagram 4600 showing the use of random / adaptive channel hopping between ranging rounds according to some embodiments. Fig.46The schematic diagram 4600 shows an implementation of random or adaptive channel hopping. In some implementations, NB packets (e.g., for transmitting NB_POLL, NB_RSP, and / or NB_DATA) use different channels in different ranging rounds. For example, as depicted in Fig.46 , ranging round X 4602 may use channel A 4606, and subsequent ranging round Y 4604 may use channel B 4608. The channel selection scheme for each ranging round can be purely random or adaptive based on channel conditions. The UWB MMS exchange 4610 can perform channel hopping independently of the NB.

[0213] Fig.47 Simplified block diagram 4700, according to some implementations, shows a situation where the synchronization data used in a previous ranging round can also be used in the next ranging round. In Fig.47 the schematic diagram 4700, the NB preamble exchange including NB_POLL and NB_RSP can be skipped in a ranging round (e.g., as described with reference to Fig.43 ). For example, as depicted in Fig.47 , NB_POLL 4704 and NB_RSP 4706 are skipped for ranging round Y 4702. In some implementations, the decision to skip the NB preamble in the current (e.g., and / or next) ranging round can be based on whether the time (T) and frequency (F) Sync obtained in a previous successful ranging round are available. The criteria for the usefulness of the previous T and F Sync depend on various factors that may affect the clock drift on both devices and the tolerance of UWB MMS reception.

[0214] Fig.48 Simplified block diagram 4800, according to some implementations, shows the adaptive asymmetric transmission of UWB segments within a ranging round according to a non-interleaved ranging protocol. Fig.48The schematic diagram 4800 shows an example of the concept where the number of UWBMMS segments exchanged between devices does not have to be the same. This asymmetry technique allows an inefficient front-end to receive more segments to compensate for its losses, while an efficient front-end can achieve the same performance level with a smaller number of segments. Using the knowledge of the front-end efficiency and / or dynamic selection of each ranging round of the participating devices, based on the estimated range, received signal strength (first path / rule), signal-to-noise ratio (first path / rule), etc., the number of segments in each direction can be determined once during the establishment of the ranging session. This information can be exchanged in-band on any / all of NB_POLL 4812, NB_RSP 4814, and NB_DATA by the NB, or exchanged out-of-band, such as via Bluetooth. The schematic diagram 4800 shows a responder 4804 that needs to receive only two UWB MMS segments 4806a to 4806b, while the initiator needs four segments 4810a to 4810d to achieve the same / similar performance level.

[0215] Fig.49 is another simplified block diagram 4900 according to some embodiments showing the adaptive asymmetric transmission of UWB segments within a ranging round according to a non-interleaved ranging protocol. The schematic diagram 4900 shows a concept similar to Fig.48 but with the directions swapped. Note that the number of segments shown in these diagrams is for illustration only, and the actual number can be any suitable number. Fig.48 and Fig.49 both show ranging rounds using a non-interleaved MMS exchange protocol with a fixed turnaround option. However, it is also applicable to non-fixed turnaround situations. In some embodiments, this method improves playback time and power efficiency because only the required number of segments are exchanged in either direction.

[0216] Fig.50 and Fig.51 are simplified block diagrams according to some embodiments showing the adaptive asymmetric transmission of UWB segments within a ranging round according to an interleaved ranging protocol. In some embodiments, the interleaved ranging protocol can be similar to that described herein (e.g., for Fig.36 and / or Fig.37 ). In this case, there may be an asymmetric transmission of segments between the initiator and responder devices when using the interleaved ranging protocol. In some embodiments, although the total duration of the ranging exchange in this method may not be significantly reduced, it can provide better coexistence and power performance. This can contribute to coexistence because a smaller number of segments can result in lower overall interference. Avoiding segment transmission / reception can also save power. As Fig.50As depicted in schematic diagram 5000, initiator 5002 transmits two UWB MMS segments 5006a to 5006b, and responder 5004 transmits four UWB MMS segments 5008a to 5008d. Schematic diagram 5100 shows a similar concept but with the directions swapped. Fig.50 A similar concept.

[0217] Exemplary techniques for transmitting NB and UWB wireless signals in combination were described above. Some or all of these systems and methods may be implemented, at least in part, by architectures such as those shown in at least one or more of the above Figures 1 to 51 However, they need not be implemented by the described architectures. It should be understood that any suitable device may perform the techniques disclosed herein. Additionally, various non-limiting examples were described in the foregoing description. For purposes of explanation, numerous specific configurations and details were set forth to provide a thorough understanding of the examples. However, it should also be apparent to those skilled in the art that some examples may be practiced without these specific details. Additionally, well-known features were sometimes omitted or simplified to prevent obscuring the examples described herein.

[0218] Although there may be many implementations of the concepts presented herein, a beneficial option for NB and UWB implementations may be to arrange the radio frequency (RF) operating frequencies for UWB and NB signals to be close to each other. For example, a suitable frequency range for NB signaling may be the unlicensed National Information Infrastructure (UNII) bands in the range of 5 GHz and 6 GHz, 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 typically allow NB transmissions at power levels up to 10 dBm or 20 dBm or more. For the UWB subsystem, typical RF operating frequencies will be the so-called UWB channels 5 and 9 at center frequencies of approximately 6.5 GHz and 8.0 GHz, respectively. The benefit of using adjacent NB and UWB frequencies is that it is easier to share antenna hardware between NB and UWB. However, note that another suitable operating range for the NB subsystem is within the 2.4 GHz to 2.5 GHz ISM band (commonly used for ZigBee and Bluetooth and other consumer wireless systems), and a variety of UWB center frequencies from 1 GHz to 10 GHz and above may be used for the hybrid system concept.

[0219] 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-chip (SOC), which can also be referred to as an integrated circuit (e.g., including suitable processor circuitry). They can also be embodied as separate SOCs, an NB SOC and a UWB SOC, where tight coupling and joint MAC control processing are accomplished through direct control signals exchanged between the two SOCs.

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

[0221] Clause 1: A computer-implemented method, comprising: determining, by a first subsystem of a first device, parameter data for a ranging round, the parameter data indicating a first time for initiating the ranging round, and the first time being associated with a first time domain for performing ranging; transmitting, by the first subsystem, the parameter data to a second subsystem of the first device, the first subsystem being communicatively coupled to the second subsystem via a data bus of the first device; determining, by the second subsystem, at least in part based on the first time, a second time associated with a second time domain for performing narrowband (NB) signaling; transmitting, by the first device via a narrowband signal, an announcement packet indicating the second time; and initiating, by the first device, the ranging round at the first time.

[0222] Clause 2: The computer-implemented method according to clause 1, wherein the ranging round corresponds to an ultra-wideband (UWB) ranging round or a narrowband-assisted (NBA) ultra-wideband multi-millisecond (MMS) ranging round.

[0223] Clause 3: The computer-implemented method according to any one of clauses 1 to 2, wherein the announcement packet is received by a second device, wherein a third subsystem of the second device determines the first time using the second time, wherein a fourth subsystem of the second device receives data indicating the first time from the third subsystem, and wherein the fourth subsystem schedules, at least in part based on the data indicating the first time, reception by the second device of one or more segments transmitted during the ranging round by the first device.

[0224] Clause 4: The computer-implemented method according to any one of clauses 1 to 3, wherein the parameter data includes metadata associated with performing the ranging round, and wherein the fourth subsystem schedules, at least in part based on the metadata, reception of the one or more segments transmitted during the ranging round.

[0225] Clause 5: The computer-implemented method according to any one of Clauses 1 to 4, wherein the third subsystem of the second device is configured to manage narrowband signaling of the second device using the Bluetooth Low Energy (BLE) protocol, and wherein the fourth subsystem of the second device is configured to manage at least one of ultra-wideband signaling or narrowband-assisted ultra-wideband multi-millisecond signaling of the second device.

[0226] Clause 6: The computer-implemented method according to any one of Clauses 1 to 5, wherein the first subsystem and the second subsystem are partitioned within the same integrated circuit (IC) or different integrated circuits, and wherein the data bus connects the different partitions.

[0227] Clause 7: The computer-implemented method according to any one of Clauses 1 to 6, wherein the second subsystem includes a narrowband subsystem that performs wireless signaling via the Bluetooth Low Energy (BLE) protocol, and wherein the advertisement packet corresponds to a Bluetooth Low Energy advertisement transmitted via the narrowband signal.

[0228] Clause 8: The computer-implemented method according to any one of Clauses 1 to 7, wherein the first subsystem includes an ultra-wideband subsystem that is operable to perform ultra-wideband signaling.

[0229] Clause 9: The computer-implemented method according to any one of Clauses 1 to 8, wherein the first subsystem further includes a narrowband subsystem, and the ultra-wideband subsystem and the narrowband subsystem are coupled together within a hybrid wireless transceiver of the first subsystem, and the hybrid wireless transceiver is operable to perform narrowband-assisted ultra-wideband multi-millisecond signaling.

[0230] Clause 10: The computer-implemented method according to any one of Clauses 1 to 9, wherein the parameter data further includes metadata associated with the ranging round, and the metadata indicates at least one of the following: (I) packet type, (II) number of segments to be transmitted, (III) channel type, (IV) channel hopping pattern, (V) security parameter, or (VI) timestamp exchange method, and wherein the metadata is also included in the advertisement packet.

[0231] Clause 11: The computer-implemented method according to any one of Clauses 1 to 10, wherein the first device corresponds to an anchor station that broadcasts periodic advertisements for ranging rounds, and wherein the second device corresponds to a client station.

[0232] Clause 12: A computer-implemented method according to any one of Clauses 1 to 11, wherein the client station is one of a plurality of client stations configured to receive a narrowband signal from the anchor station, and wherein the client station determines not to participate in the ranging round.

[0233] Clause 13: A computer-implemented method according to any one of Clauses 1 to 12, wherein the anchor station is one of a plurality of anchor stations located within a local area, the local area further including the client station, and wherein the client station determines a position within the local area at least in part based on measuring respective ranges between the client station and at least two of the plurality of anchor stations.

[0234] Clause 14: A computer-implemented method according to any one of Clauses 1 to 13, wherein the second time corresponds to a time offset from when the announcement packet is scheduled to be transmitted by the first device.

[0235] Clause 15: A computer-implemented method according to any one of Clauses 1 to 14, wherein the data bus includes at least one of the following: (I) a Serial Peripheral Interface (SPI), (II) a Direct Memory Access (DMA) interface, or (III) a Peripheral Component Interconnect Express (PCIe) interface.

[0236] Clause 16: A computer-implemented method according to any one of Clauses 1 to 15, the computer-implemented method further comprising: receiving, by the second subsystem of the first device, a second announcement packet including second parameter data indicating a third time for initiating a second ranging round by a second device and including metadata corresponding to ranging parameters of the second ranging round, and the third time being associated with the second time domain for performing narrowband signaling; determining, by the first device, to participate in the second ranging round indicated by the second announcement packet; determining, by the second subsystem, a fourth time at least in part based on the third time, the fourth time being associated with the first time domain for performing ranging; transmitting, by the second subsystem, data to the first subsystem, the data indicating the fourth time and including the metadata corresponding to the ranging parameters; and scheduling, by the first subsystem, one or more fragments received during the second ranging round at least in part based on the fourth time and the metadata.

[0237] Clause 17: A computer-implemented method according to any one of Clauses 1 to 16, wherein the announcement packet includes second parameter data associated with the ranging round, the second parameter data indicating the second time, and includes metadata associated with scheduling the one or more segments transmitted during the ranging round.

[0238] Other embodiments of the present disclosure may be directed to an apparatus that includes: a memory that includes computer-executable instructions; and one or more processors that communicate with the memory and are configured to access the memory and execute the computer-executable instructions to perform the method according to any one of Clauses 1 to 17.

[0239] Other embodiments of the present disclosure may be directed to one or more computer-readable storage media that include 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 17.

[0240] Other embodiments of the present disclosure may relate to a device that includes: processor circuitry configured to perform the method according to any one of Clauses 1 to 17.

[0241] The various embodiments may also be implemented in a variety of operating environments, which in some cases may include one or more user computers, computing devices, or processing devices that may be used to operate any one of a plurality of applications. The user device or client device may include any of a number of general-purpose personal computers, such as a desktop or laptop computer running a standard operating system, as well as cellular, wireless, and handheld devices that run mobile software and are capable of supporting multiple networking and instant messaging protocols. This system may also include a number of workstations running any one 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.

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

[0243] In an implementation that utilizes a network server, the network server can run any one of various 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 capable of executing a program or script in response to a request from a user device, such as by executing one or more applications, which may be implemented as one or more scripts or programs written in any programming language such as 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 commercially available from and those available commercially.

[0244] The environment can include various data repositories and other memories and storage media, as described above. These can reside in various locations, such as on a storage medium local to one or more computers or on a storage medium remote from any or all of the computers on the network (and / or reside within one or more computers). In a particular set of implementations, the information can reside in a storage area network (SAN) familiar to those skilled in the art. Similarly, any necessary files for performing the functions attributed to a computer, server, or other network device can be stored locally and / or remotely as needed. When the system includes computerized devices, each such device can 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, touch screen, or keypad), and at least one output device (e.g., display device, printer, or speaker). Such systems can 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 cards, and so on.

[0245] Such devices may also include a computer-readable storage medium reader, a communication device (e.g., a modem, a network card (wireless or wired), an infrared communication device, etc.), and a working memory as described above. The computer-readable storage medium reader may be connected to or configured to receive a non-transitory computer-readable storage medium representing a remote, local, fixed, and / or removable storage device, as well as a storage medium for temporarily and / or more permanently containing, storing, transmitting, and retrieving computer-readable information. The system and various devices will generally also include a plurality of software applications, modules, services, or other elements located within at least one working memory device, including an operating system and applications, such as client applications or browsers. It should be understood that alternative embodiments may have many variations in accordance with the above description. 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. Additionally, connections to other computing devices, such as network input / output devices, may be used.

[0246] The non-transitory storage medium and computer-readable storage medium for containing code or portions of code may include any suitable medium known or used in the art, e.g., 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 cartridges, tapes, magnetic disk storage devices, or other magnetic storage devices, or any other medium that can be used to store the required information and can be accessed by the system device. Based at least in part on the disclosures and teachings provided herein, those of ordinary skill in the art will recognize other ways and / or methods of implementing the various embodiments. However, computer-readable storage media do not include transitory media such as carrier waves, etc.

[0247] Accordingly, the specification and drawings should be regarded in an illustrative rather than a restrictive sense. However, it is obvious that various modifications and changes can be made thereto without departing from the broader spirit and scope of the disclosure set forth in the claims.

[0248] Other variations are within the spirit of the disclosure. Thus, although the disclosed technology is susceptible to various modifications and alternative configurations, certain illustrative embodiments thereof have been shown in the drawings and described in detail above. However, it should be understood that the intention is not to limit the disclosure to the particular forms disclosed, but on the contrary, to cover all modifications, alternative configurations, and equivalent forms falling within the spirit and scope of the disclosure as defined by the appended claims.

[0249] In the context of describing the disclosed embodiments (specifically, in the context of the following claims), the terms "a," "an," and "the" and similar referential terms are to be construed to cover both the singular and the plural, unless otherwise specified or clearly contradicted by the context. Unless otherwise specified, the terms "comprising," "having," "including," and "containing" are to be construed as open-ended terms (i.e., meaning "including, but not limited to"). The term "connected" is construed to mean included, attached, or joined together in whole or in part even with something intervening. The phrase "at least partially based on" is to be understood as open-ended and not limiting in any way and is intended to be construed or otherwise understood as "at least partially based on" as appropriate. Unless otherwise indicated herein, the recitation of numerical ranges herein is merely intended to be a convenient method for separately referring to each individual value falling within the range, and each individual value is incorporated into the specification as if it were individually recited herein. All methods described herein can be performed in any suitable order, unless otherwise indicated herein or otherwise 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 merely intended to better illustrate the embodiments of the present disclosure and does not limit the scope of the present disclosure. No language in the specification should be construed as indicating any non-recited element as essential to the practice of the present disclosure.

[0250] Unless otherwise specifically stated, disjunctive language such as the phrase "at least one of X, Y, or Z" is understood in context to generally be used to present items, terms, etc., which may be X, Y, or Z, or any combination thereof (e.g., X, Y, and / or Z). Thus, such disjunctive language is generally not intended and should not be construed to imply that certain embodiments require the presence of at least one of each of X, at least one of Y, or at least one of Z. Additionally, unless otherwise specifically stated, conjunctive language 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".

[0251] Preferred embodiments of the present disclosure are described herein, including the best mode known for carrying out the present disclosure. Variations of those preferred embodiments may become apparent to those of ordinary skill in the art after reading the foregoing description. It is expected that those skilled in the art will appropriately adopt such variations and are intended to practice these techniques in a manner different than specifically described herein. Accordingly, as permitted by applicable law, the present disclosure includes all modifications and equivalent forms of the subject matter recited in the appended claims. Additionally, unless otherwise indicated herein or clearly contradicted by the context, the present disclosure includes any combination of all possible variations of the above elements.

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

[0253] As described above, one aspect of the techniques of the present invention is to collect and use data to wirelessly transmit a security framework for authentication. The present disclosure contemplates that, in some instances, the data collected may include personal 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), phone numbers, email addresses, Twitter IDs, home addresses, or any other identifying or personal information.

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

[0255] The present disclosure contemplates 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 recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be readily accessible to users and should be updated as the collection and / or use of the data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. In addition, such collection / sharing should be done after receiving informed consent from the user. In addition, such entities should consider taking any necessary steps to safeguard and secure access to such personal information data and ensure that others with access to the personal information data comply with their privacy policies and procedures. Additionally, such entities may subject themselves to third-party assessments to demonstrate their compliance with widely accepted privacy policies and practices. Additionally, policies and practices should be adjusted so as to collect and / or access particular types of personal information data and apply to applicable laws and standards that include specific considerations of the 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 health data in other countries may be subject to other regulations and policies and should be handled accordingly. Thus, different privacy practices should be maintained for different types of personal data in each country.

[0256] Notwithstanding the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates that hardware elements and / or software elements may be provided 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 may be configured to allow a user to select "opt-in" or "opt-out" of participation in the collection of personal information data during or at any time after registration for the service. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notices relating to access or use of personal information. For example, a user may be notified at the time of downloading an application that their personal information data will be accessed and then again just prior to the personal information data being accessed by the application.

[0257] In addition, it is an object of the present disclosure that personal information data should be managed and processed to minimize risks of inadvertent or unauthorized access or use. Once data is no longer needed, the risk can be minimized by limiting data collection and deleting the data. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data at the city level rather than at the address level), controlling how the data is stored (e.g., aggregating data among users), and / or other methods.

[0258] Thus, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that the various embodiments may also be implemented without access to such personal information data. That is, the various embodiments of the inventive technology will not fail to operate properly due to the lack of all or a portion of such personal information data.

Claims

1. A computer-implemented method, comprising: determining, by a device, a first parameter associated with a first ranging round, the first parameter indicating a first channel; transmitting, by the device, a first ranging packet associated with the first ranging round via a first narrowband signal and using the first channel; determining, by the device, a second parameter associated with a second ranging round, the second parameter indicating a second channel different from the first channel; and transmitting, by the device, a second ranging packet associated with the second ranging round via a second narrowband signal and using the second channel.

2. The computer-implemented method according to claim 1, wherein at least one of the first ranging round or the second ranging round comprises an Ultra-Wideband (UWB) ranging round or a Narrowband-Assisted (NBA) UWB MMS ranging round.

3. The computer-implemented method according to claim 1, wherein at least the first ranging packet comprises one or more first Ultra-Wideband (UWB) Multi-Millisecond (MMS) segments or the second ranging packet comprises one or more second UWB MMS segments.

4. The computer-implemented method according to claim 1, further comprising: transmitting, by the device, a first announcement packet associated with the first ranging round via a third narrowband signal and using the first channel; and transmitting, by the device, a second announcement packet associated with the second ranging round via a fourth narrowband signal and using the second channel.

5. The computer-implemented method according to claim 1, wherein the first ranging round is at least partially based on an interleaved ranging protocol.

6. The computer-implemented method according to claim 1, wherein determining the first parameter or the second parameter is at least partially based on a channel hopping pattern.

7. The computer-implemented method according to claim 1, wherein the first parameter comprises first metadata associated with performing the first ranging round, and the second parameter comprises second metadata associated with performing the second ranging round.

8. One or more non-transitory computer-readable storage media, the one or more non-transitory computer-readable storage media comprising computer-executable instructions that, when executed by one or more processors of a first device, cause the one or more processors to perform operations comprising: determining, by a device, a first parameter associated with a first ranging round, the first parameter indicating a first channel; transmitting, by the device, a first ranging packet associated with the first ranging round via a first narrowband signal and using the first channel; determining, by the device, a second parameter associated with a second ranging round, the second parameter indicating a second channel different from the first channel; and transmitting, by the device, a second ranging packet associated with the second ranging round via a second narrowband signal and using the second channel.

9. The one or more non-transitory computer-readable storage media according to claim 8, wherein at least one of the first ranging round or the second ranging round comprises a UWB ranging round or a narrowband-assisted (NBA) UWB MMS ranging round.

10. The one or more non-transitory computer-readable storage media according to claim 8, wherein at least the first ranging packet comprises one or more first ultra-wideband (UWB) multi-millisecond (MMS) segments or the second ranging packet comprises one or more second UWB MMS segments.

11. The one or more non-transitory computer-readable storage media according to claim 8, wherein the instructions further comprise: transmitting, by the device, a first announcement packet associated with the first ranging round via a third narrowband signal and using the first channel; and transmitting, by the device, a second announcement packet associated with the second ranging round via a fourth narrowband signal and using the second channel.

12. The one or more non-transitory computer-readable storage media according to claim 8, wherein the second ranging round is at least partially based on an interleaved ranging protocol.

13. The one or more non-transitory computer-readable storage media according to claim 8, wherein determining the first parameter or the second parameter is at least partially based on a channel hopping pattern.

14. The one or more non-transitory computer-readable storage media according to claim 8, wherein the first parameter comprises first metadata associated with performing the first ranging round, and the second parameter comprises second metadata associated with performing the second ranging round.

15. A device, comprising: a memory configured to store computer-executable instructions; and one or more processors in communication with the memory and configured to execute the computer-executable instructions to perform the following operations: determining a first parameter associated with a first ranging round, the first parameter indicating a first channel; transmitting, via a first narrowband signal and using the first channel, a first ranging packet associated with the first ranging round; determining a second parameter associated with a second ranging round, the second parameter indicating a second channel different from the first channel; and transmitting, via a second narrowband signal and using the second channel, a second ranging packet associated with the second ranging round.

16. The device according to claim 15, wherein at least one of the first ranging round or the second ranging round comprises a UWB ranging round or a narrowband-assisted (NBA) UWB MMS ranging round.

17. The device according to claim 15, wherein at least the first ranging packet comprises one or more first ultra-wideband (UWB) multi-millisecond (MMS) segments or the second ranging packet comprises one or more second UWB MMS segments.

18. The device according to claim 15, wherein the one or more processors are further configured to perform the following operations: Transmit, by the device, a first announcement packet associated with the first ranging round via a third narrowband signal and using the first channel; and Transmit, by the device, a second announcement packet associated with the second ranging round via a fourth narrowband signal and using the second channel.

19. The device according to claim 15, wherein the first ranging round is at least partially based on an interleaved ranging protocol.

20. The device according to claim 15, wherein determining the first parameter or the second parameter is at least partially based on a channel hopping pattern.

Images