Bluetooth-ultra wide band synchronization

Through synchronization between Bluetooth radio components and UWB radio components, the timing information is transmitted using Bluetooth communication, which solves the problem of high power consumption of UWB radio components during initial synchronization, and achieves more efficient power management and accurate time synchronization.

CN118945628APending Publication Date: 2024-11-12APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411024259.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2020-01-16
Filing Date
2020-08-31
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

In the prior art, high-power radio components such as ultra-wideband (UWB) consume a lot of power during initial synchronization, resulting in wasting system power. Low-power radio components such as Bluetooth consume high power when monitoring incoming communications, lacking efficient synchronization. method.

Method used

Through the Bluetooth radio component synchronizes with the UWB radio component in a low power state, the timing information is transmitted using Bluetooth communication to synchronize the high power state of the UWB radio component, ensuring that the UWB radio component enters the high power state to send and receive communication within a narrow time window, and Return to the low power state upon completion.

Benefits of technology

Improves the power efficiency of UWB radio components, reduces system power consumption, and achieves more precise timing synchronization, allowing UWB radio components to operate within a narrower time window, reducing the high cost of initial synchronization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945628A_ABST
    Figure CN118945628A_ABST
Patent Text Reader

Abstract

The invention relates to Bluetooth-ultra wide band synchronization. Methods, systems, and apparatus are disclosed that utilize Bluetooth (BT) radios to synchronize ultra wide band (UWB) radios to allow the UWB radios to operate within a narrow transmit / receive window, which may result in power savings. In some implementations, a transmitting UWB radio and a receiving UWB radio can synchronize expected times of UWB transmissions based on BT events, such as receiving BT announcements or establishing BT connections. In some implementations, the transmitting UWB radio and the receiving UWB radio can synchronize the expected time of the UWB transmission based on a synchronization event counter maintained by the BT radio. In some implementations, information regarding UWB transmission start-up times can also be communicated via BT communications.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the invention patent application with application date of August 31, 2020, application number 202010894315.0, and invention name “Bluetooth-Ultra-Wideband Synchronization”.

[0002] Priority claim

[0003] This patent application claims the benefit of priority to U.S. Provisional Patent Application Serial No. 62 / 897,100, filed on September 6, 2019, and entitled “Bluetooth-Ultra Wideband Synchronization,” which is hereby incorporated by reference in its entirety as if fully and completely set forth herein. Technical Field

[0004] The present application relates to wireless communications, including techniques for synchronizing high power radio components via communications conducted through low power radio components. Background Art

[0005] The use of wireless communication systems is growing rapidly. In addition, wireless communication technology has evolved from only voice communication to also include the transmission of data (such as the Internet and multimedia content).

[0006] Mobile electronic devices may take the form of smartphones or tablets that are commonly carried by users. Wearable devices (also known as accessory devices) are a newer form of mobile electronic device, an example being a smartwatch. In addition, low-cost, low-complexity wireless devices intended for static or dynamic deployment are also increasing rapidly as part of the development of the "Internet of Things". In other words, the complexity, capabilities, traffic patterns and other characteristics of the devices required are becoming increasingly broad.

[0007] Such different wireless communication devices may utilize a variety of different radio access technologies (RATs) and / or radio components. For example, various RATs may have advantages and disadvantages relative to other RATs. For example, a first RAT, such as Bluetooth, can operate with relatively small power consumption. A second RAT, such as ultra-wideband (UWB), may be more capable of performing multipath isolation or ranging operations, but may consume power at a higher rate when operating in a fully operational state. In particular, certain high-power radio components such as UWB may consume a lot of power during initial synchronization because, traditionally, they may be required to remain in a fully operational state for a long time when listening to neighboring devices.

[0008] Therefore, improvements in this area are desired. Summary of the invention

[0009]

[0013] In particular, embodiments of systems, devices, and methods for utilizing a Bluetooth (BT) radio to synchronize an ultra-wideband (UWB) radio to allow the UWB radio to operate within a narrow transmit / receive window are presented herein.

[0010] The present invention discloses a wireless communication device, which may include a first radio component, a second radio component, and a processor. The first radio component may be configured to establish a connection with a remote wireless device according to a first radio access technology (RAT), and provide an indication to the processor that the connection has been established. After providing the indication, the first radio component may receive a notification from the remote wireless device that the remote wireless device will send a communication according to a second RAT, wherein the notification includes an offset time. The first radio component may be further configured to provide the offset time to the processor. The processor may be configured to store a timestamp indicating the time when the processor receives the indication that the connection has been established; and provide an instruction to the second radio component to receive the communication according to the second RAT at a set time, wherein the set time is determined by adding the offset time to the time indicated by the timestamp. The second radio component may be configured to, in response to receiving the instruction to receive the communication according to the second RAT, switch from a low power state to a high power state at the set time, and receive the communication according to the second RAT. The second radio may be configured to transition from the high power state to the low power state after receiving the communication according to the second RAT.

[0011] In some scenarios, the first RAT may be Bluetooth and the second RAT may be Ultra Wideband (UWB).

[0012] In some scenarios, in establishing the connection with the remote wireless device according to the first RAT, the first radio component may be configured to receive a notification message from the remote wireless device according to the first RAT; and in response to receiving the notification message, send a connection request message to the remote wireless device according to the first RAT. In some scenarios, in providing the processor with the indication that the connection has been established, the first radio component is configured to provide the processor with an indication that the connection request has been sent.

[0013] In some scenarios, in providing the instruction to the second radio component to receive the communication according to the second RAT at a set time, the processor may be configured to start a timer, the timer being configured to expire at the set time. In response to the expiration of the timer, the processor may provide the instruction to the second radio component to immediately receive the communication according to the second RAT.

[0014] In some scenarios, when transitioning from the low power state to the high power state at the set time, the second radio component may be configured to receive from the processor an indication of the remaining time until the set time. In response to the remaining time expiring, the second radio component may transition from the low power state to the high power state.

[0015] In some scenarios, the communication according to the second RAT may be an ultra-wideband (UWB) ranging request message. In such scenarios, the second radio component may be further configured to transition from the low power state to the high power state at a predetermined time after receiving the UWB ranging request message; in response to receiving the UWB ranging request message, send a UWB ranging response message while operating in the high power state; and after sending the UWB ranging response message, transition from the high power state to the low power state.

[0016] The present invention discloses a wireless communication device, which may include a first radio component and a second radio component. The first radio component may be configured to maintain an event counter that is incremented in response to a periodic handshake process with a remote wireless device according to a first radio access technology (RAT). The first radio component may be further configured to receive a notification from the remote wireless device that the remote wireless device will send a communication according to a second RAT, wherein the notification indicates a future value of the event counter when the communication will be sent. The second radio component may be configured to transition from a low power state to a high power state when the event counter reaches the future value indicated in the notification that the remote wireless device will send the communication according to the second RAT. The second radio component may be further configured to receive the communication according to the second RAT and transition from the high power state to the low power state after receiving the communication according to the second RAT.

[0017] In some scenarios, the first radio component may be further configured to establish a connection with the remote wireless device according to the first RAT prior to receiving the notification that the remote wireless device will send the communication according to the second RAT.

[0018] In some scenarios, the wireless communication device may further include a processor. The first radio component may be further configured to provide the future value of the event counter to the processor, and the current value of the event counter when the first radio component provides the future value of the event counter to the processor. The processor may be configured to provide an instruction to the second radio component to receive the communication according to the second RAT in response to determining that the event counter has reached the future value. The second radio component may transition from the low power state to the high power state in response to receiving the instruction from the processor.

[0019] In some scenarios, the first radio component may be further configured to periodically provide the processor with a current value of the event counter.

[0020] In some scenarios, the first radio component may be further configured to provide an indication to the processor that the event counter has reached the future value.

[0021] In some scenarios, the first radio component may be further configured to provide an indication to the second radio component that the event counter has reached the future value. The second radio component may transition from the low power state to the high power state in response to receiving the indication that the event counter has reached the future value.

[0022] In some scenarios, the value of the event counter matches a value in a remote event counter maintained by the remote wireless device.

[0023] The present invention discloses a wireless communication device, which may include a first radio component and a second radio component. The first radio component may be configured to receive a notification message from a remote wireless device according to a first radio access technology (RAT); and provide an indication that the notification message has been received to the second radio component, wherein the indication includes a timestamp indicating the time when the first radio component receives the notification message. The second radio component may be configured to, in response to receiving the indication that the notification message has been received, switch from a low power state to a high power state at a set time, wherein the set time is determined by adding a first offset time to the time indicated by the timestamp. When operating in the high power state, the second radio component may receive acquisition information about subsequent communications according to the second RAT according to the second RAT, wherein the subsequent communication is after the acquisition information after a second offset time, wherein the acquisition information indicates the second offset time. The second radio component may be further configured to switch from the high power state to the low power state after receiving the acquisition information.

[0024] In some scenarios, the second radio component may be further configured to transition from the low power state to the high power state in response to expiration of the second offset time. While operating in the high power state, the second radio component may receive the subsequent communication according to the second RAT. The second radio component may be configured to transition from the high power state to the low power state after receiving the subsequent communication according to the second RAT.

[0025] In some scenarios, the notification message may indicate the value of the first offset time. In other scenarios, the offset time may be predetermined.

[0026] In some scenarios, the indication that the announcement message has been received may include a media access control (MAC) address to which the announcement message is addressed. The second radio component may be further configured to confirm that the acquisition information is also addressed to the MAC address.

[0027] In some scenarios, the first radio may include a first clock and the second radio may include a second clock. The second radio may be further configured to determine a value of the second clock upon detecting a signal edge on an interface between the first radio and the second radio, and to receive a value of the first clock from the first radio upon detecting the signal edge on the interface between the first radio and the second radio. The second radio may be further configured to determine a difference between the value of the second clock and the value of the first clock. Determining the time indicated by the timestamp may include adjusting the value of the timestamp by the difference between the value of the second clock and the value of the first clock.

[0028] Methods for performing functions similar to those performed by the wireless communication device outlined above are presented herein.

[0029] This summary is intended to provide a brief overview of some of the topics described in this document. Therefore, it should be understood that the above features are only examples and should not be interpreted as narrowing the scope or essence of the subject matter described in this invention in any way. Other features, aspects and advantages of the subject matter described herein will become apparent through the following detailed description, drawings and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] A better understanding of the present subject matter may be obtained when the following detailed description of the embodiments is considered in conjunction with the following drawings.

[0031] Figure 1 An exemplary wireless communication system is shown in accordance with various exemplary embodiments described herein.

[0032] Figure 2-Figure 3 is a block diagram illustrating an exemplary wireless device in accordance with various exemplary embodiments described herein.

[0033] Figure 4 A signal flow diagram for synchronizing BT communications and UWB communications in a BT connected scenario using standardized BT radio components is shown according to some embodiments.

[0034] Figure 5 A signal flow diagram is shown for synchronizing BT communications and UWB communications in a BT connected scenario using an enhanced BT radio according to some embodiments.

[0035] Figure 6 A signal flow diagram for synchronizing BT communications and UWB communications in a BT non-connected scenario according to some embodiments is shown.

[0036] Although the features described herein are susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are described in detail herein. However, it should be understood that the drawings and detailed description thereof are not intended to limit this document to the specific forms disclosed, but on the contrary, the purpose is to cover all modifications, equivalents and alternatives that fall within the spirit and scope of the subject matter as defined by the appended claims. DETAILED DESCRIPTION

[0037] Incorporated by Reference

[0038] Various details of an exemplary UWB communication protocol are disclosed in IEEE 802.15.4-2015, which is hereby incorporated by reference as if fully disclosed herein.

[0039] the term

[0040] The following are definitions of terms used in this disclosure:

[0041] Storage media —Any of various types of non-transitory memory devices or storage devices. The term "memory medium" is intended to include installation media, for example, CD-ROM, floppy disk or tape device; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, for example, hard disk drive or optical storage device; registers or other similar types of memory elements, etc. The memory medium may also include other types of non-transitory memory or their combination. In addition, the memory medium may be located in the first computer system executing the program, or may be located in a different second computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory medium" may include two or more memory media that may reside in different locations in different computer systems connected, for example, via a network. The memory medium may store program instructions (e.g., expressed as a computer program) that may be executed by one or more processors.

[0042] Carrier medium —Memory media as described above, and physical transmission media such as buses, networks and / or other physical transmission media that transmit signals such as electrical signals, electromagnetic signals or digital signals.

[0043] Programmable hardware components — includes various hardware devices that include multiple programmable function blocks connected via programmable interconnects. Examples include FPGAs (field programmable gate arrays), PLDs (programmable logic devices), FPOAs (field programmable object arrays), and CPLDs (complex PLDs). Programmable function blocks can vary from fine-grained (combinational logic units or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "configurable logic units."

[0044] Computer Systems —Any of various types of computing or processing systems, including a personal computer system (PC), a mainframe computer system, a workstation, a network appliance, an Internet appliance, a personal digital assistant (PDA), a television system, a grid computing system, or other devices or combinations of devices. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0045] User Equipment (UE) (or "UE Device") —Any of various types of computer system devices that are mobile or portable and perform wireless communication. Examples of UE devices include mobile phones or smart phones (e.g., iPhone TM , based on Android TM phones), portable gaming devices (e.g., Nintendo DS TM , PlayStation Portable TM 、Gameboy Advance TM , iPhone TM ), laptops, wearable devices (e.g., smart watches, smart glasses), PDAs, portable Internet devices, music players, data storage devices or other handheld devices, etc. In general, the term "UE" or "UE device" can be broadly defined to cover any electronic device, computing device and / or telecommunication device (or combination of devices) that can be easily transmitted by a user and capable of wireless communication.

[0046] Wireless Devices —Any of various types of computer system devices that perform wireless communications. A wireless device may be portable (or mobile), or may be stationary or fixed at a location. A UE is an example of a wireless device. Other examples may include less mobile devices such as desktop computers, entertainment centers, set-top boxes, climate control modules, security modules, smart home control modules, smart appliances, electronic doors / locks, vehicles, etc.

[0047] Communications equipment—Any of various types of computer systems or devices that perform communication, where the communication may be wired or wireless. A communication device may be portable (or mobile), or may be stationary or fixed at a location. A wireless device is an example of a communication device. A UE is another example of a communication device.

[0048] Base Station —The term “base station” (also referred to as “eNB” or “gNB”) has the full breadth of its ordinary meaning and includes at least a wireless communication station installed at a fixed location and used to communicate as part of a wireless cellular communication system.

[0049] Link budget limited —includes the full scope of its ordinary meaning and includes at least the characteristics of a wireless device (e.g., UE) that exhibits limited communication capabilities or limited power relative to a device that is not link budget limited or relative to a device for which a radio access technology (RAT) standard has been developed. A link budget limited wireless device may experience relatively limited receive capabilities and / or transmit capabilities, which may be due to one or more factors, such as device design, device size, battery size, antenna size or design, transmit power, receive power, current transmission medium conditions, and / or other factors. Such devices may be referred to herein as "link budget limited" (or "link budget constrained") devices. A device may be inherently link budget limited due to the size of the device, battery power, and / or transmit / receive power. For example, a smart watch that communicates with a base station via LTE or LTE-A may be inherently link budget limited due to its reduced transmit / receive power and / or antenna reduction. Wearable devices such as smart watches are generally link budget limited devices. Alternatively, a device may not be inherently link budget limited, e.g., may have sufficient size, battery power, and / or transmit / receive power for normal communication over LTE or LTE-A, but may be temporarily link budget limited due to current communication conditions, e.g., a smartphone at a cell edge, etc. It is noted that the term "link budget limited" includes or encompasses power limitations, and thus a link-limited device may be considered a link budget limited device.

[0050] Processing element (or processor) —refers to various elements or combinations of elements. Processing elements include, for example, circuits such as ASICs (application specific integrated circuits), portions or circuits of individual processor cores, entire processor cores, individual processors, programmable hardware devices (such as field programmable gate arrays (FPGAs)), and / or larger portions of systems including multiple processors.

[0051] Wi-Fi—The term "Wi-Fi" has the full scope of its ordinary meaning and includes at least wireless communication networks or RATs that are served by Wireless LAN (WLAN) access points and provide connectivity to the Internet through these access points. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and are marketed under the name "Wi-Fi". Wi-Fi (WLAN) networks are distinct from cellular networks.

[0052] automatic —refers to an action or operation performed by a computer system (e.g., software executed by a computer system) or a device (e.g., a circuit, a programmable hardware element, an ASIC, etc.) without the need for user input to directly specify or perform the action or operation. Thus, the term "automatically" is contrasted with a user manually performing or specifying an action, where the user provides input to directly perform the action. An automatic process may be initiated by input provided by a user, but the subsequent actions performed "automatically" are not specified by the user, i.e., are not performed "manually," where the user specifies each action to be performed. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing in information, selecting check boxes, radio selections, etc.) is manually filling out the form, even though the computer system must update the form in response to user actions. The form may be automatically filled out by a computer system, where the computer system (e.g., software executed on the computer system) analyzes the fields of the form and fills out the form without any user input specifying the answers to the fields. As indicated above, a user may invoke the automatic filling out of a form, but not participate in the actual filling out of the form (e.g., the user does not manually specify the answers to the fields but they are automatically completed). This specification provides various examples of operations that are automatically performed in response to actions taken by a user.

[0053] Configured as —Various components may be described as being “configured to” perform one or more tasks. In such environments, “configured to” is a broad statement that generally means “having a structure” that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when the component is not currently performing the task (e.g., a set of electrical conductors can be configured to electrically connect a module to another module even when the two modules are not connected). In some environments, “configured to” can be a broad statement that generally means “having a circuit system that performs one or more tasks during operation.” Thus, the component can be configured to perform a task even when the component is not currently turned on. Typically, circuits that form the structure corresponding to “configured to” may include hardware circuits.

[0054] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". The description of a component being configured to perform one or more tasks is expressly intended to not invoke the interpretation of the sixth paragraph of Section 112 of Title 35 of the United States Code on that component.

[0055] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0056] Figure 1 – Wireless communication system

[0057] Figure 1 An exemplary (and simplified) wireless communication system 100 is shown in which aspects of the present disclosure may be implemented. Figure 1 The system is only one example of possible systems, and embodiments of the present disclosure may be implemented in any of a variety of systems as desired.

[0058] As shown, the exemplary wireless communication system includes a ("first") wireless device 102 communicating with another ("second") wireless device 104. The first wireless device 102 and the second wireless device 104 may communicate wirelessly using any of a variety of wireless communication techniques, possibly including secure ranging wireless communication techniques.

[0059] As one possibility, the first wireless device 102 and the second wireless device 104 can communicate using ultra-wideband (UWB) communication technology (e.g., IEEE 802.15.4 WPAN communication), Wi-Fi (e.g., IEEE 802.11), and / or other technologies based on WPAN or WLAN wireless communication. One or both of the wireless device 102 and the wireless device 104 can also communicate via one or more additional wireless communication protocols, such as Bluetooth (BT), Bluetooth Low Energy (BLE), Near Field Communication (NFC), GSM, UMTS (WCDMA, TDSCDMA), LTE, LTE-Advanced (LTE-A), NR, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-MAX, GPS, etc.

[0060] The wireless devices 102, 104 may be any of a variety of types of wireless devices. As one possibility, one or more of the wireless devices 102, 104 may be substantially portable wireless user equipment (UE) devices, such as a smartphone, a handheld device, a wearable device, a tablet, a motor vehicle, or virtually any type of mobile wireless device. As another possibility, one or more of the wireless devices 102, 104 may be substantially stationary devices, such as a set-top box, a media player (e.g., an audio or audio-visual device), a game console, a desktop computer, an appliance, an environmental controller, a door, or any of a variety of other types of devices.

[0061] Each of the wireless devices 102, 104 may include wireless communication circuitry configured to facilitate the performance of wireless communications, which may include various digital and / or analog radio frequency (RF) components, a processor configured to execute program instructions stored in a memory, a programmable hardware element such as a field programmable gate array (FPGA), and / or any of various other components. The wireless device 102 and / or the wireless device 104 may use any or all of such components to perform any method implementation described herein, or any portion of any method implementation described herein.

[0062] Each of the wireless devices 102, 104 may include one or more antennas for communicating using one or more wireless communication protocols. In some cases, one or more parts of the receiving and / or transmitting chain may be shared between multiple wireless communication standards. For example, the device may be configured to communicate using either Bluetooth or UWB using a partially or completely shared wireless communication circuit (e.g., using a shared radio or at least a shared radio component). The shared communication circuit may include a single antenna, or may include multiple antennas for performing wireless communication (e.g., for MIMO). Alternatively, the device may include an independent transmitting chain and / or receiving chain (e.g., including independent antennas and other radio components) for each wireless communication protocol configured to communicate with it. As another possibility, the device may include one or more radios or radio components shared between multiple wireless communication protocols, and one or more radios or radio components used exclusively by a single wireless communication protocol. For example, the device may include a shared radio component for communicating using any one of LTE or CDMA2000, 1xRTT, and an independent radio component for communicating using each of UWB, Wi-Fi and / or Bluetooth. Other configurations are also possible.

[0063] As mentioned above, it can be combined with Figure 1 For example, wireless devices 102, 104 may use the wireless communication system described herein with respect to Figures 4 to 6 By utilizing such techniques (and / or other techniques described herein), wireless devices (at least according to some embodiments) can achieve more efficient communication.

[0064] Figures 2 to 3 - Example device block diagram

[0065] Figure 2 An exemplary wireless device 200 is shown that can be configured for use in conjunction with various aspects of the present disclosure. For example, device 200 can be an example of wireless device 102 or wireless device 104. Device 200 can be any of a variety of types of devices and can be configured to perform any of a variety of types of functions. Device 200 can be a substantially portable device, or can be a substantially fixed device, possibly including any of a variety of types of devices. Device 200 can be configured to perform one or more synchronization techniques or features, such as those described later herein with respect to Figures 4 to 6 Any or all of the techniques or features shown and / or described herein.

[0066] As shown, device 200 may include processing element 202. The processing element may include or be coupled to one or more memory elements. For example, device 200 may include one or more storage media (e.g., memory 206), which may include any of various types of memory and may be used for any of a variety of functions. For example, memory 206 may be RAM used as system memory for processing element 202. Other types and functions are also possible.

[0067] Additionally, device 200 may include wireless communication circuitry 230. The wireless communication circuitry may include any of a variety of communication elements (e.g., an antenna for wireless communication, analog and / or digital communication circuitry / controllers, etc.), and may enable the device to communicate wirelessly using one or more wireless communication protocols.

[0068] Note that in some cases, wireless communication circuitry 230 may include its own processing element (e.g., a baseband processor) in addition to processing element 202, for example. For example, processing element 202 may be (or include) an "application processor" whose primary function may be to support application layer operations in device 200, while wireless communication circuitry 230 may include a "baseband processor" whose primary function may be to support baseband layer operations in device 200 (e.g., to facilitate wireless communications between device 200 and other devices). In other words, in some cases, device 200 may include multiple processing elements (e.g., may be a multi-processor device). Other configurations utilizing a multi-processor architecture (e.g., instead of or in addition to an application processor / baseband processor configuration) are also possible.

[0069] Depending on the intended functionality of device 200, device 200 may additionally include any of a variety of other components (not shown) for implementing device functionality, which may also include processing elements and / or memory elements (e.g., audio processing circuitry), one or more power elements (which may rely on battery power and / or an external power source), user interface elements (e.g., a display, a speaker, a microphone, a camera, a keyboard, a mouse, a touch screen, etc.), and / or any of a variety of other components.

[0070] The components of the device 200, such as the processing element 202, the memory 206 and the wireless communication circuit 230, can be operably coupled via one or more interconnect interfaces, and the interconnect interface can include any of various types of interfaces, and may include a combination of multiple types of interfaces. As an example, a USB high-speed chip-to-chip (HSIC) interface can be provided for inter-chip communication between processing elements. Alternatively (or in addition), any of a universal asynchronous receiver-transmitter (UART) interface, a serial peripheral interface (SPI), an internal integrated circuit (I2C), a system management bus (SMBus) and / or various other communication interfaces can be used for communication between various device components. Other types of interfaces (e.g., an intra-chip interface for communication within the processing element 202, a peripheral device interface for communicating with peripheral components inside or outside the device 200, etc.) can also be provided as a part of the device 200.

[0071] Figure 3 A possible block diagram of a wireless device 300 is shown, which may be Figure 2300. As shown, the wireless device 300 may include a system on chip (SOC) 301, which may include parts for various purposes. For example, as shown, the SOC 301 may include one or more processors 302 and display circuit 304, and the one or more processors 302 may execute program instructions for the wireless device 300, and the display circuit 304 may perform graphics processing and provide display signals to the display 360. The SOC 301 may also include a motion sensing circuit 370, which may detect the motion of the wireless device 300, for example, using any of a gyroscope, an accelerometer, and / or various other motion sensing components. The one or more processors 302 may also be coupled to a memory management unit (MMU) 340, which may be configured to receive addresses from the one or more processors 302 and convert these addresses to locations in a memory (e.g., a memory 306 and a read-only memory (ROM) 350, a flash memory 310). MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, MMU 340 may be included as part of processor 302.

[0072] As shown, SOC 301 may be coupled to various other circuits of wireless device 300. For example, wireless device 300 may include various types of memory (e.g., including NAND flash memory 310), connector interface 320 (e.g., for coupling to a computer system, a docking station, a charging station, etc.), display 360, and wireless communication circuitry 330 (e.g., for UWB, LTE, LTE-A, CDMA2000, Bluetooth, Wi-Fi, NFC, GPS, etc.).

[0073] The wireless device 300 may include at least one antenna and in some embodiments may include multiple antennas 335a and 335b for performing wireless communications with base stations and / or other devices. For example, the wireless device 300 may use antennas 335a and 335b to perform wireless communications. As described above, the wireless device 300 may be configured in some embodiments to perform wireless communications using multiple wireless communication standards or radio access technologies (RATs).

[0074] The wireless communication circuit 330 may include a UWB logic component 332, a cellular modem 334, and an additional WLAN / PAN logic component 336. The UWB logic component 332 is used to enable the wireless device 300 to perform UWB communications and / or for ranging communications, for example, according to the 802.15.4 protocol. The WLAN / PAN logic component 336 is used to enable the wireless device 300 to perform other WLAN and / or PAN communications, such as Wi-Fi and / or Bluetooth communications. The cellular modem 334 may be capable of performing cellular communications according to one or more cellular communication technologies.

[0075] As described herein, the wireless device 300 may include hardware components and software components for implementing embodiments of the present disclosure. For example, one or more components of the wireless communication circuit 330 (e.g., the UWB logic component 332) of the wireless device 300 may be configured to implement part or all of the methods described herein, for example, by a processor executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), a processor configured as an FPGA (field programmable gate array), and / or using dedicated hardware components that may include an ASIC (application-specific integrated circuit).

[0076] Auxiliary timing synchronization

[0077] Various RATs may have advantages and disadvantages relative to other RATs, which may result in each RAT being advantageous for a particular application. For example, UWB communications (e.g., as described in IEEE 802.15.4-2015, incorporated by reference above) are sometimes referred to as pulse radio components, which are capable of providing wireless communications with low transmit power over a large bandwidth (e.g., 500 MHz or greater) with precise timing. Therefore, this technology is very suitable for short-range communications where multipath interference is a concern. For example, among other applications, UWB communications are very suitable for indoor ranging and positioning applications. However, UWB radio components may consume a lot of power when they are in a full-power state. Therefore, since UWB communications are typically characterized by short pulses between long periods of inactivity, it is very wasteful for UWB radio components to continue to be in a full-power state to listen for incoming communications. Therefore, in some scenarios, for example, in the case where one or more of the UWB radio components in the UWB radio components must scan for initial discovery messages or synchronization messages over an extended period of time, the initial synchronization between the UWB radio components may be a high-cost operation.

[0078] As another example, a BT radio component may consume less power than a UWB radio component when listening for incoming communications. In addition, BT communications may have a longer range than UWB communications. Therefore, BT communications may be well suited for discovery of surrounding devices.

[0079] In view of the above, the first wireless device may use BT communication to perform discovery of neighboring wireless devices and / or connection with neighboring wireless devices. During the BT message exchange for discovery and / or connection, the first wireless device may pass various information to the neighboring wireless device to synchronize subsequent UWB communications. For example, the first wireless device may use BT communication to pass timing information about the time when the first wireless device will send subsequent UWB messages. In addition, the first wireless device and the neighboring wireless device may use the timing information of one or more BT communication events to synchronize the timing of their respective UWB radio components for transmitting subsequent UWB messages.

[0080] By synchronizing the timing of a UWB radio of a first wireless device with the timing of a UWB radio of an adjacent wireless device, the power efficiency of the UWB radio may be improved. For example, a UWB radio may operate in a low power state (such as a sleep state) for most of the time. However, the UWB radio may enter a high power state (such as a full power state or a communication state) to send and / or receive UWB communications in one or more brief time windows, for example, based on timing information transmitted via one or more BT communications. After such a time window, the UWB radio may return to a low power state. Greater precision and accuracy in the timing of synchronized UWB radios may allow the UWB radio to utilize narrower time windows to send and / or receive UWB communications, which may result in increased power savings.

[0081] Performing timing synchronization of UWB radio components may be performed according to any of a variety of methods, for example, as outlined below.

[0082] It should be understood that UWB communication and BT communication are examples only, and other RATs may be substituted. For example, any discussion of UWB communication throughout the following methods may apply to any RAT that can benefit from a precise wake-up cycle. Similarly, any discussion of BT communication throughout the following methods may apply to any RAT that can transmit synchronization information within such a wake-up cycle.

[0083] Figure 4 -Synchronization during BT connection

[0084] Figure 4 A signal flow diagram for synchronizing BT communication and UWB communication in a BT connection scenario using standardized BT radio components according to some embodiments is shown. As shown, the signal flow may include a Tx device 400 and an Rx device 410. The Tx device 400 and the Rx device 410 may each be a wireless communication device (such as any of the wireless devices 102, 104, 200, or 300), include a wireless communication device, or be included in a wireless communication device.

[0085] As shown, the Tx device 400 may include a Tx CPU 402, a Tx UWB radio 404, and a Tx BT radio 406, which can be communicatively coupled to each other in various configurations. For example, the modules shown within the Tx device 400 may be connected via one or more serial connections, general purpose input / output (GPIO) connections, and / or other connectors. The Tx CPU 402 may be an application processor (such as the processor 302), include an application processor, or be included in an application processor, and may be configured to run one or more applications or other software, such as to perform high-level communication processes of the Tx UWB radio 404 and / or the Tx BT radio 406. The Tx UWB radio 404 may be a UWB logic component 332, include a UWB logic component 332, or be included in a UWB logic component 332, and may be configured to perform UWB communications, such as including the steps outlined below. The BT radio component 406 may be, include, or be included in the WLAN / PAN logic component 336 and may be configured to perform BT communications, for example including the steps outlined below.

[0086] As shown, the Rx device 410 may include an Rx CPU 412, an Rx UWB radio 414, and an Rx BT radio 416, which can be communicatively coupled to each other in various configurations. For example, the Rx CPU 412, the Rx UWB radio 414, and the Rx BT radio 416 may be substantially similar to the Tx CPU 402, the Tx UWB radio 404, and the Tx BT radio 406, respectively.

[0087] As shown, Tx BT 406 may send an announcement (or set of announcements) 420. In some scenarios, Tx BT 406 may send such announcements periodically, for example, at regular intervals such as 30ms or 100ms. In some scenarios, announcements 420 may be formatted or configured as defined by the relevant BT standard.

[0088] In response to receiving the notification 420, the Rx BT radio component 416 may send a connection request 422. The connection request 422 may be configured to initiate a connection between the Rx BT radio component 416 and the Tx BT radio component 406, and may include any information suitable for initiating such a connection. In some specific implementations, the connection request 422 may be configured as defined by the relevant BT standard. When sending the connection request 422, the Rx BT radio component 416 may provide a connection completion message 424 to the Rx CPU 412. The connection completion message 424 may be provided substantially immediately after sending the connection request 422. Upon receiving the connection completion message 424, the Rx CPU 412 may generate a record of the time T at which the connection completion message 424 was received. RxC Specifically, the time T can be recorded according to the local clock of RxCPU 412. RxC .

[0089] In response to receiving the connection request 422, the Tx BT radio 406 may provide a connection completion message 426 to the Tx CPU 402. The connection completion message 426 may be provided substantially immediately after receiving the connection request 422. Upon receiving the connection completion message 426, the Tx CPU 402 may generate a message recording the time T at which the connection completion message 426 was received. TxC Specifically, the time T can be recorded according to the local clock of Tx CPU 402. TxC .

[0090] Even though the connection completion message 424 and the connection completion message 426 may be received by the Rx CPU 412 and the Tx CPU 402 respectively at substantially the same time, since the local clock of the Tx CPU 402 may not be synchronized with the local clock of the Rx CPU 412, they are recorded as T RxC and T TxC The time of may be different. Therefore, the time T RxC and T TxC Can be used as a known reference time that can be used to coordinate subsequent communications.

[0091] It should be understood that for simplicity, Figure 4 Additional signaling, such as connection setup messages, etc., may follow the connection complete message 424 and the connection complete message 426, which are not shown in FIG.

[0092] Tx CPU 402 may execute an application or other software that attempts to initiate UWB communication (such as UWB ranging). Tx CPU 402 may determine to send UWB communication at a specific time. After receiving connection completion message 426, Tx CPU 402 may further determine an offset time T off, the offset time indicates the time T at which the UWB communication will begin. TxC The amount of time after. For example, T off A value of 300 ms may be indicated, indicating that the Tx UWB radio 404 will TxC After 300ms, the UWB communication starts to be sent. In other words, the sending time may be at time T TxC +T off Occurs everywhere.

[0093] The Tx CPU 402 may communicate information about upcoming UWB communications to the Rx CPU 412 via BT communications. For example, the TX CPU 402 may pass the information to the Tx BT radio 406, which may send the information as an initiate UWB command 428 to the Rx BT radio 416. The information passed to the Tx BT radio 406 and included in the initiate UWB command 428 may include an indication that the Tx UWB radio 404 will send a UWB communication, and the Tx UWB radio 406 may send the information to the Rx BT radio 416. off In some scenarios, this information may also include other information, such as the type of communication to be sent.

[0094] As shown, the start UWB command 428 may not be successfully sent on the first attempt. For example, the start UWB command 428a may represent the first attempt of the Tx BT radio component 406 to send the start UWB command 428, and the Rx BT radio component 416 may not successfully receive the start UWB command. For example, the Rx BT radio component 416 may respond to the start UWB command 428a with a NAK message (not shown), or may not respond with an ACK message. In response, the Tx BT radio component 406 may make subsequent attempts to complete the communication as needed. In the example scenario shown, the first two attempts 428a and 428b failed, but the Rx BT radio component 416 successfully received the start UWB command 428c.

[0095] The Rx BT radio 416 may pass the payload received in the Start UWB Command 428 to the Rx CPU 412, the payload including information regarding the upcoming UWB communication, which may include, for example, T off In response to receiving the information regarding the upcoming UWB communication, Rx CPU 412 may prepare to receive the UWB communication via Rx UWB radio 414. For example, Rx CPU 412 may transmit information or instructions 430 to Rx UWB radio 414 to cause Rx UWB radio 414 to attempt to receive the UWB communication at time T. RxC +T offIn some implementations, the information or instructions 430 may alternatively or additionally be transmitted by the Rx BT radio component 416 to the Rx UWB radio component 414.

[0096] In some implementations, the Tx UWB radio 404 and / or the Rx UWB radio 414 may be configured to remain in a low power state, such as a sleep state, under normal conditions, but enter an active state (e.g., wake up) to send and / or receive UWB communications at specific times. In such implementations, attempting to receive UWB communications may include the Rx UWB radio 514 temporarily entering an active state to receive UWB communications.

[0097] For example, the Tx CPU 402 may cause the Tx UWB radio 404 to wake up at a specific time to transmit the UWB beacon 432. The transmission time may be at time T TxC +T off After transmitting the UWB beacon 432, the Tx UWB radio 404 may return to the low power mode.

[0098] In response to receiving information regarding an upcoming UWB communication, the Rx CPU 412 (or the Rx BT radio 416) may cause the Rx UWB radio 414 to communicate at time T RxC +T off 432. For example, the Rx CPU 412 may start a CPU configured to receive the UWB beacon 432 at time T. RxC +T off The Rx CPU 412 may provide an instruction 430 to the Rx UWB radio component 414 to wake up immediately when the timer expires. For another example, the Rx CPU 412 may provide an instruction 430 to the Rx UWB radio component 414, which includes an instruction to wake up at the time T. RxC +T off The Rx UWB radio 414 may then initiate a call configured to start at time T based on the time value provided by the Rx CPU 412. RxC +T off In either example, the Rx UWB radio 414 may wake up at time T RxC +T off The time window starting at (or centered at or including this time, etc.). RxC With time T TxCThe Rx CPU 412 and / or Rx UWB radio 414 can be synchronized so that they can know with high accuracy when the UWB beacon 432 will be sent, and thus the wake-up window of the RX UWB radio 414 can be short. The length of the wake-up window can be determined based on various factors, such as the expected length of the UWB beacon 432 and / or other communications, and the accuracy of synchronization, taking into account factors such as hardware latency, software latency, clock accuracy, transmission time, etc. In some scenarios, the length of the wake-up window can be a fixed predetermined value. After the wake-up window, the Rx UWB radio 414 can return to a low power mode.

[0099] In some scenarios, subsequent communications may be performed within similarly brief wake-up windows. For example, if the UWB beacon 432 is a UWB ranging request message, the Rx UWB radio 414 may send a UWB ranging response message at a fixed predetermined time after receiving the UWB beacon 432, for example, as known in the art. Thus, the Rx UWB radio 414 and the Tx UWB radio 404 can each wake up in a time window suitable for sending / receiving UWB ranging response messages. Alternatively or in addition, the Rx UWB radio 414 and the Tx UWB radio 404 may be configured to wake up periodically after the first transmission. Alternatively or in addition, the UWB beacon 432 may include information about one or more subsequent communications, including timing information, which may enable the Rx UWB radio 414 and / or the Tx UWB radio 404 to wake up at one or more subsequent times to send and / or receive subsequent communications.

[0100] In some implementations, BT events other than connection completion signals may alternatively or additionally be used to synchronize the timing of the Tx UWB radio component 404 and the Rx UWB radio component 414. For example, in some scenarios, the Tx BT radio component 406 may send a connection update message to the Rx BT radio component 416, for example, to indicate a periodic change in the BT announcement message. When transmitting such a connection update message, the Tx BT radio component 406 may provide a connection update event message to the Tx CPU 402. Upon receiving the connection update event message, the Tx CPU 402 may, for example, generate a time T based on a local clock of the Tx CPU 402 to record the time when the connection update event message was received. TxU Similarly, upon receiving a connection update message, the Rx BT radio component 416 may provide a connection update event message to the Rx CPU 412. Upon receiving a connection update event message, the Rx CPU 412 may generate a time T to record the time when the connection update event message was received, for example, based on a local clock of the Rx CPU 412.RxU Because the two connection update event messages can be received by Rx CPU 412 and TxCPU 402 at substantially the same time, the time T RxU and T TxU Can be used as can be used with T RxC and T TxC The known reference time for subsequent communications is coordinated in substantially the same manner. This may allow the synchronization of the UWB radio to be updated, for example periodically, at a time after the connection is established.

[0101] In some implementations, other BT events can similarly be used to synchronize or update the synchronization of the Tx UWB radio 404 and the Rx UWB radio 414 .

[0102] Figure 5 - Enhanced synchronization when connected to BT

[0103] Figure 5 A signal flow diagram for synchronizing BT communication and UWB communication in a BT connection scenario using an enhanced BT radio component according to some embodiments is shown. As shown, the signal flow may include a Tx device 500 and an Rx device 510. The Tx device 500 and the Rx device 510 may each be a wireless communication device (such as any of the wireless devices 102, 104, 200, or 300), include a wireless communication device, or be included in a wireless communication device.

[0104] As shown, the Tx device 500 may include a Tx CPU 502, a Tx UWB radio 504, and a Tx BT radio 506, which can be communicatively coupled to each other in various configurations. For example, the modules shown within the Tx device 500 may be connected via one or more serial connections, general purpose input / output (GPIO) connections, and / or other connectors. The Tx CPU 502 may be an application processor (such as the processor 302), include an application processor, or be included in an application processor, and may be configured to run one or more applications or other software, such as to perform high-level communication processes of the Tx UWB radio 504 and / or the Tx BT radio 506. The Tx UWB radio 504 may be a UWB logic component 332, include a UWB logic component 332, or be included in a UWB logic component 332, and may be configured to perform UWB communications, such as including the steps outlined below. The BT radio component 506 may be, include, or be included in the WLAN / PAN logic component 336 and may be configured to perform BT communications, for example including the steps outlined below.

[0105] As shown, the Rx device 510 may include an Rx CPU 512, an Rx UWB radio 514, and an Rx BT radio 516, which can be communicatively coupled to each other in various configurations. For example, the Rx CPU 512, the Rx UWB radio 514, and the Rx BT radio 516 may be substantially similar to the Tx CPU 502, the Tx UWB radio 504, and the Tx BT radio 506, respectively.

[0106] exist Figure 5 In the scenario shown, the Tx BT 506 has established a BT connection with the Rx BT radio 516. For example, Figure 4 The BT connection is established in substantially the same manner, for example, by transmitting an announcement (or set of announcements) 420 , a connection request 422 , a connection complete message 424 , and a connection complete message 426 .

[0107] After the connection is established, the Tx BT radio 506 may periodically perform a handshake function with the Rx BT radio 516 . Figure 5 A plurality of handshake functions are shown in dashed lines. For example, the periodicity of the handshake function may be set during connection establishment or at some other time, but the periodicity may be known to both the Tx BT radio component 506 and the Rx BT radio component 516. The Tx BT radio component 506 and the Rx BT radio component 516 may each maintain a corresponding event counter (EC) that is incremented each time a handshake function is performed. Therefore, the value of the EC and / or the number of recent handshake functions may be used as a known reference time value that can be used to coordinate subsequent communications.

[0108] The Tx CPU 502 may execute an application or other software that attempts to initiate a UWB communication, such as a UWB ranging measurement. The Tx CPU 502 may determine to send a UWB communication at a particular time. The Tx CPU 402 may receive a read EC message 526 from the Tx BT radio 506, which includes the current EC value EC. current .exist Figure 5 In the scenario shown, EC current is 200.

[0109] In response to receiving the read EC message 526, the Tx CPU 502 may determine the EC value EC UWB , which indicates what the EC value will be when UWB communication will start. For example, if UWB communication will start within 300ms and the handshake function is performed in a 30ms cycle, the EC value will be incremented 10 times before UWB communication starts. currentis 200, so Tx CPU 502 can determine EC UWB will be 210. Tx CPU 502 may, for example, communicate EC UWB to the RxCPU 512. For example, the TX CPU 502 may UWB The Tx BT radio 506 may transmit the information as a Start UWB Command 528 to the Rx BT radio 516. The Start UWB Command 528 may also include the Tx UWB radio 504 sending the information to the EC UWB In some scenarios, the initiate UWB command 528 may also include other information, such as the type of communication to be sent.

[0110] In some implementations, after (or simultaneously with) sending the Start UWB command 528, the Tx CPU 502 or Tx UWB radio 504 can start a timer to identify the time when UWB communications are to be sent. In this example, the timer can have a value of 300 ms, which is consistent with the timing information sent in the Start UWB command 528. The Tx CPU 502 can cause the Tx UWB radio 504 to send UWB communications when the timer expires.

[0111] In other specific implementations, the Tx CPU 502 and / or the Tx UWB radio 504 may use any other method to determine the start time of UWB communication. UWB Thereafter, the Tx CPU 502 may periodically obtain the current value of EC, and in response to determining that the EC value has reached EC UWB (For example, in Figure 5 210 in the example of FIG. 5 ), causing the Tx UWB radio 504 to transmit UWB communications.

[0112] The Rx BT radio 516 may pass the payload received in the Start UWB Command 528 to the Rx CPU 512, the payload including information regarding the upcoming UWB communication, which may include, for example, EC UWB The Rx BT radio 516 may also provide EC to the Rx CPU 512 based on an event counter maintained by the Rx BT radio 516. currentFor example, the Rx BT radio 516 may provide the Rx CPU 512 with a read EC message 529, which may include, for example, an EC value determined when (or near) the Rx BT radio 516 receives the start UWB command 528 or when (or near) the Rx BT radio 516 provides information about an upcoming UWB communication to the Rx CPU 512. current The goal may be to strive to communicate to Rx CPU 512 (eg, via read EC message 529 ) the same EC value that was communicated to Tx CPU 502 via read EC message 526 .

[0113] In response to receiving the EC UWB and EC current , the Rx CPU 512 can start a timer to identify when a UWB communication is to be sent (e.g., Figure 5 The Rx CPU 512 may cause the Rx UWB radio 514 to attempt to receive UWB communications upon expiration of the timer, for example, by transmitting information or instructions 530 to the Rx UWB radio 514.

[0114] Alternatively, the Rx CPU 502, the Rx UWB radio section 514, and / or the Rx BT radio section 516 can use any other method to perform the operation based on the received EC UWB For example, in some implementations, the Rx BT radio 516 may periodically provide the current value of EC to the Rx CPU 512, for example, whenever the value of EC is incremented, or at some less frequent interval. In response, the Rx CPU 512 may cause the Rx UWB radio 514 to initiate a UWB communication upon determining that EC has reached EC. UWB For example, in some implementations, the Rx BT radio component 516 can determine EC from the start UWB command 528. UWB In response, after incrementing EC to EC UWB The value of (for example, in Figure 5 210 in the example of ), Rx BT radio 516 may provide an indication (e.g., raising a GPIO signal or reporting the current value of EC) to Rx CPU 512 and / or Rx UWB radio 514. In response to the indication, Rx UWB radio 514 may attempt to receive UWB communication, or Rx CPU 512 may cause Rx UWB radio 514 to attempt to receive UWB communication, for example, by transmitting information or instructions 530 to Rx UWB radio 514.

[0115] In some implementations, the Tx UWB radio 504 and / or the Rx UWB radio 514 may be configured to remain in a low power state, such as a sleep state, under normal conditions, but enter an active state (e.g., wake up) to send and / or receive UWB communications at specific times. In such implementations, attempting to receive UWB communications may include the Rx UWB radio 514 temporarily entering an active state to receive UWB communications.

[0116] For example, the Tx CPU 502 may cause the Tx UWB radio 504 to wake up at a specific time to transmit the UWB beacon 532. The transmit time may be at a value of EC UWB time (e.g., after detecting that EC has incremented to the value EC UWB After sending the UWB beacon 532, the Tx UWB radio 504 may return to low power mode.

[0117] As described above, the Rx CPU 512 can cause the Rx UWB radio 514 to wake up to receive the UWB beacon 532 at the appropriate time. Because the BT event counter of the Rx BT radio 516 is synchronized with the BT event counter of the Tx BT radio 506, the Rx CPU 512 and / or the Rx UWB radio 514 can know with high accuracy when the UWB beacon 532 will be sent, so the wake-up window of the RX UWB radio 514 can be short. After the wake-up window, the Rx UWB radio 514 can return to a low power mode.

[0118] In some scenarios, subsequent communications may be performed within a similarly short wake-up window, for example, as described in Figure 4 as outlined.

[0119] In various implementations, the BT radio components 506 and 516 can communicate the EC value to their respective CPUs 502 and 512 in any of a variety of ways. For example, the BT radio component can provide the current value of the EC to the respective CPU via a serial or parallel connection, for example, periodically or in response to a request from the CPU. As another example, the BT radio component can have a dedicated output to provide the current EC value, which can be read by the CPU at any time. As another example, the Rx BT radio component 516 can include the current EC value when passing payload data from a BT communication such as the Start UWB command 528 to the Rx CPU 512.

[0120] In some scenarios, Figure 5 The signal flow shown allows comparison between two UWB radio components. Figure 4The signal flow shown is more accurately synchronized. This may allow a narrower wake-up window for UWB communication, resulting in additional power savings. However, in some implementations, customized BT hardware and / or firmware may be required to enable output of the current EC value, which may result in increased hardware costs.

[0121] Figure 6 - Synchronization in BT disconnected state

[0122] Figure 4 and Figure 5 The scenario shown allows synchronization between the Tx UWB radio and the Rx UWB radio based on knowledge of the timing of BT events involved in establishing or maintaining a BT connection. However, in some scenarios, for example, where the Tx device does not have payload data to be transferred via BT, the Tx BT radio may not establish a connection with the Rx BT radio. In this case, BT events may still be used to synchronize the Tx UWB radio and the Rx UWB radio.

[0123] Figure 6 A signal flow diagram for synchronizing BT communication and UWB communication in a BT non-connected scenario according to some embodiments is shown. As shown, the signal flow may include a Tx device 600 and an Rx device 610. The Tx device 600 and the Rx device 610 may each be a wireless communication device (such as any one of the wireless devices 102, 104, 200, or 300), include a wireless communication device, or be included in a wireless communication device. In some scenarios, the Tx device 600 may be similar or identical to the Tx device 400 or the Tx device 500, and the Rx device 610 may be similar or identical to the Rx device 410 or the Rx device 510.

[0124] As shown, the Tx BT radio 606 may send an announcement (or set of announcements) 620. In some scenarios, the Tx BT 606 may send such announcements periodically, for example, at regular intervals. The announcement 620 may include a transmitter address and / or a receiver address (e.g., a transmitter and / or receiver MAC address), authentication information, and / or any other information suitable for identifying the Tx device 600 and / or the Rx device 610 (e.g., identifying the Tx BT radio 606 and / or the Rx BT radio 616).

[0125] exist Figure 6 In the scenario shown, the Rx BT radio 616 may receive the announcement 620 , but may refuse to establish a connection with the Tx BT radio 606 .

[0126] However, Rx BT 616 may provide an announcement notification 624 to Rx UWB radio 614, for example, via a serial interface or other connection. In some scenarios, the announcement notification 624 may include the announcement 620 or some portion thereof, which may include, for example, a transmitter address and / or a receiver address, authentication information, etc. The announcement notification 624 may also include the time T at which the Rx BT radio 616 received the announcement 620. RxA Alternatively or in addition, Rx BT 616 may provide the notification 624 to Rx CPU 612, which may then provide the notification 624, or some portion thereof, to Rx UWB 614.

[0127] In response to receiving the announcement notification 624, the Rx UWB radio component 614 can determine, for example, using the address information included in the announcement notification 624, whether the announcement is addressed to the Rx device 610. If so, the Rx UWB radio component 614 can transition from a low power state (e.g., a sleep state) to a high power state (e.g., a full power state) capable of receiving UWB communications. Specifically, the Rx UWB radio component 614 can perform this state transition when the offset time expires, Figure 6 628. For example, the Rx UWB radio 614 may start a timer from the time indicated in the timestamp of the time when the Rx BT radio component 616 receives the announcement 620 to determine when the UWB acquisition offset 628 has passed. In other words, the Rx UWB radio component 614 may start a timer configured to receive the UWB acquisition offset 628 at a time defined as (T RxA +UWB acquisition offset 628). When the timer has elapsed, the Rx UWB radio component 614 can transition to a high power state within a predetermined time window to receive any available UWB communications, and can then transition back to a low power state after the time window. In some scenarios, the UWB acquisition offset 628 can be predetermined. In some scenarios, the UWB acquisition offset 628 can be transmitted in the announcement 620 and can be delivered in the announcement notification 624.

[0128] When sending the announcement 620, the Tx BT radio component 606 can provide the announcement notification 626 to the Tx UWB radio component 604. In some scenarios, the announcement notification 626 can be similar to the announcement notification 624. For example, the announcement notification 626 can include the announcement 620 or some portion thereof, which can include, for example, a transmitter address and / or a receiver address. The announcement notification 626 can also include the time T at which the Tx BT radio component 606 sent the announcement 620. TxA The timestamp of the

[0129] The Tx CPU 602 may execute an application or other software that attempts to initiate UWB communication (such as UWB ranging). The Tx CPU 602 may therefore transmit instructions or information 630 to the Tx UWB radio component 604 to initiate UWB communication with the Rx device 610 (e.g., with the Rx UWB radio component 614). The connection instruction 630 is shown as appearing after the announcement notification 626, but in some scenarios, the connection instruction may be transmitted before the announcement notification 626 and / or the announcement 620.

[0130] In response to receiving the announcement notification 626, the Tx UWB radio 604 may start a timer starting from the time indicated in the timestamp of the time when the announcement 620 was sent to determine when the UWB acquisition offset 628 has passed. In other words, the Tx UWB radio 604 may start a timer configured to start the timer at a time defined as (T TxA +UWB acquisition offset 628). When the timer has elapsed, if the Tx UWB radio component 604 has not received the connection instruction 630, the Tx UWB radio component 604 may take no further action at that time, for example, until receiving a subsequent announcement notification 626, reporting a subsequent announcement 620 (for example, if the announcements are sent periodically). Specifically, in such a scenario, while the timer is elapsing, the Tx UWB radio component 604 may remain in a low power state and not send any UWB communications. However, when the timer elapses, if the Tx UWB radio component 604 has received the connection instruction 630, such as Figure 6 As shown, the Tx UWB radio 604 may then transition from the low power state to a high power state capable of transmitting UWB communications, and may transmit UWB acquisition information 632. The Tx UWB radio 604 may then return to the low power state.

[0131] The acquisition information 632 may include timing information and any other appropriate information about subsequent UWB communications. For example, subsequent UWB communications may be scheduled at one or more times independent of BT announcements or other BT events. As a specific example, the acquisition information 632 may include a UWB communication offset 634 that indicates an offset time at which a UWB beacon 636 will be sent relative to the time when the acquisition information 632 is sent. In such examples, the Tx UWB radio component 604 may start a timer with a duration matching the UWB communication offset 634 when sending the acquisition information 632. When the timer expires, the Tx UWB radio component 604 may transition to a high power state and send a UWB beacon 636. The Tx UWB radio component 604 may then transition back to a low power state.

[0132] In some implementations, the acquisition information 632 can be addressed to the same receiver address (e.g., MAC address) as the advertisement 620. In some implementations, the acquisition information 632 can include the same transmitter address (e.g., MAC address) as the advertisement 620. In some implementations, the Rx UWB radio 614 can verify one or both of these addresses and / or other identification information included in the acquisition information 632 to determine that the acquisition information 632 is intended for the Rx UWB radio 614, for example, to avoid missynchronization with a third party.

[0133] As described above, Rx UWB radio 614 may transition to a high power state within the time window upon expiration of a timer to measure UWB acquisition offset 628. If Tx UWB radio 604 does not transmit acquisition information 632, RX UWB radio 614 may not receive communications during the time window and may transition back to a low power state and take no further action until a subsequent announcement notification 624 is received. However, if Tx UWB radio 604 does transmit acquisition information 632, Rx UWB radio 614 may receive acquisition information 632 during the time window that Rx UWB radio 614 is in the high power mode.

[0134] In response to receiving the acquisition information 632, the Rx UWB radio 614 may set a timer having a duration matching the UWB communication offset 634 received in the acquisition information 632. Upon expiration of the timer, the Rx UWB radio 614 may transition to a high power state and receive the UWB beacon 636. The Rx UWB radio 614 may then return to a low power state.

[0135] In some scenarios, subsequent communications may be performed within a similarly brief wake-up window, e.g., substantially as described above with reference to Figure 4 as outlined.

[0136] In some implementations, Rx BT radio 616 may operate according to a different (e.g., independent) clock than Rx UWB radio 614. In such implementations, it may be beneficial to synchronize or index the two clocks. For example, in the event that Rx BT radio 616 communicates to Rx UWB radio 614 (e.g., in announcement notification 624) a timestamp indicating the time when Rx BT radio 616 received announcement 620 (where the timestamp would record the time according to the clock of Rx BT radio 616), Rx UWB radio 614 may not be able to identify the corresponding time according to the clock of Rx UWB radio 614 if the two radios are not synchronized or otherwise indexed.

[0137] In some implementations, GPIO or other low latency connections may be used to perform synchronization of clocks associated with the Rx BT radio 616 and the Rx UWB radio 614. For example, the Rx BT radio 616 and the Rx UWB radio 614 may each record the time according to their respective local clocks when a falling edge or rising edge of a signal passes over the GPIO between the two radios. One or both of these radios may then communicate the recorded time to the other and use the two times to determine the offset between the two clocks.

[0138] In some implementations, synchronization of clocks associated with the Tx BT radio 606 and the Tx UWB radio 604 can be performed in a similar manner.

[0139] In addition to the exemplary embodiments described above, more embodiments of the present disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0140] In some embodiments, a non-transitory computer-readable storage medium may be configured such that it stores program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system is caused to perform a method, such as any one of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein or any combination of such subsets.

[0141] In some embodiments, a device (e.g., wireless device 102 or 104) may be configured to include a processor (or a group of processors) and a memory medium, wherein the memory medium stores program instructions, wherein the processor is configured to read and execute the program instructions from the memory medium, wherein the program instructions are executable to implement any of the various method implementations described herein (or any combination of the method implementations described herein, or any subset of any method implementations described herein, or any combination of such subsets). The device may be implemented in any of a variety of forms.

[0142] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.

Claims

1. A wireless communication device, comprising: A processor, the processor being configured to: storing a timestamp indicating a time of receipt of an indication that a Bluetooth (BT) connection has been established between the wireless communication device and a remote device; as well as providing instructions to an ultra-wideband (UWB) radio of the wireless communication device to receive a communication from the remote device at a set time, wherein the set time is determined based at least on adding an offset time received from the remote device to the reception time indicated by the timestamp; and The UWB radio component, the UWB radio component is configured to: transitioning from a low power state to a high power state within the set time in response to receiving the instruction to receive the communication from the remote device; and The communication is received from the remote device.

2. The wireless communication device of claim 1, wherein the indication that the BT connection has been established comprises an indication that a BT radio component of the wireless communication device has sent a connection request message to the remote device in response to an announcement message from the remote device.

3. The wireless communication device of claim 1 , wherein the processor is further configured to: The timestamp is generated based on a local clock of the processor.

4. The wireless communication device of claim 1 , wherein the UWB radio component is further configured to: After receiving the communication from the remote device, transitioning from the high power state to the low power state.

5. The wireless communication device of claim 1 , wherein in providing the instruction to the UWB radio to receive the communication from the remote device at a set time, the processor is configured to: determining when the set time has been reached; and Instructions are provided to the UWB radio to immediately receive the communication from the remote device in response to determining that the set time has been reached.

6. The wireless communication device of claim 1 , wherein in transitioning from a low power state to a high power state at the set time, the UWB radio component is configured to: receiving from the processor an indication of a time remaining until the set time; and Transitioning from the low power state to the high power state is performed in response to expiration of the remaining time.

7. The wireless communication device of claim 1 , wherein the communication from the remote device is a UWB ranging request message, wherein the UWB radio is further configured to: transitioning from the low power state to the high power state at a predetermined time after receiving the UWB ranging request message; sending a UWB ranging response message while operating in the high power state in response to receiving the UWB ranging request message; and After sending the UWB ranging response message, transitioning from the high power state to the low power state.

8. A wireless communication device, comprising: A Bluetooth (BT) radio component, the BT radio component being configured to: maintaining an event counter that is incremented in response to a periodic handshake procedure with a remote wireless device; receiving from the remote wireless device a notification that the remote wireless device will send an ultra-wideband (UWB) communication, wherein the notification indicates a future value of the event counter when the communication will be sent; and A UWB radio component, the UWB radio component being configured to: transitioning from a low power state to a high power state when the event counter reaches the future value indicated in the notification that the remote wireless device will send the UWB communication; and The UWB communication is received while in the high power state.

9. The wireless communication device of claim 8, wherein the BT radio component is further configured to: Prior to receiving the notification that the remote wireless device will transmit the UWB communication, a connection is established with the remote wireless device.

10. The wireless communication device according to claim 8, further comprising a processor, wherein the BT radio component is further configured to: providing the future value of the event counter to the processor; and providing to the processor a current value of the event counter when the BT radio component provides the future value of the event counter to the processor; The processor is configured to: providing instructions to the UWB radio to receive the UWB communication in response to determining that the event counter has reached the future value; and Wherein the UWB radio component transitions from the low power state to the high power state in response to receiving the instruction from the processor.

11. The wireless communication device of claim 10, wherein the BT radio component is further configured to: The current value of the event counter is periodically provided to the processor.

12. The wireless communication device of claim 10, wherein the BT radio component is further configured to: An indication is provided to the processor that the event counter has reached the future value.

13. The wireless communication device of claim 8, wherein the BT radio component is further configured to: providing an indication to the UWB radio that the event counter has reached the future value; Wherein the UWB radio transitions from the low power state to the high power state in response to receiving the indication that the event counter has reached the future value.

14. The wireless communication device of claim 8, wherein the value of the event counter matches a value in a remote event counter maintained by the remote wireless device.

15. An ultra-wideband (UWB) radio component included in a wireless communication device, the UWB radio component comprising: a memory storing software instructions; and a processor circuit configured to execute the software instructions to cause the UWB radio component to: receiving, from a Bluetooth (BT) radio of the wireless communication device, a message including a timestamp indicating a time at which the BT radio received an advertisement message from a remote wireless device; transitioning from a low power state to a high power state within a set time in response to the message from the BT radio component, wherein the set time is determined by adding a first offset time to the time indicated by the timestamp; as well as While operating in the high power state, acquisition information regarding a subsequent UWB communication is received, wherein the subsequent UWB communication is a second offset time after the acquisition information, wherein the acquisition information indicates the second offset time.

16. The UWB radio of claim 15, wherein the processor circuit is further configured to cause the UWB radio to: After receiving the acquisition information, switching from the high power state to the low power state; transitioning from the low power state to the high power state based on the second offset time; while operating in the high power state, receiving the subsequent UWB communication; and After receiving the subsequent UWB communication, transitioning from the high power state to the low power state.

17. The UWB radio of claim 15, wherein the processor circuit is further configured to cause the UWB radio to: The value of the first offset time is received from the BT radio.

18. The UWB radio of claim 15, wherein the first offset time is predetermined.

19. The UWB radio component of claim 15, wherein the message from the BT radio comprises a media access control (MAC) address to which the announcement message is addressed; and Wherein the processor circuit is further configured to cause the UWB radio component to confirm that the acquisition information is also addressed to the MAC address.

20. The UWB radio of claim 15, further comprising a local clock, wherein the processor circuit is further configured to cause the UWB radio to: determining a value of the local clock upon detecting a signal edge on an interface between the BT radio and the UWB radio; receiving a value of a BT radio clock from the BT radio when the BT radio detects the signal edge on the interface between the BT radio and the UWB radio; as well as determining a difference between the value of the local clock and the value of the BT radio clock; Wherein determining the time indicated by the timestamp comprises adjusting the value of the timestamp by the difference between the value of the local clock and the value of the BT radio clock.