Multi-interface transponder device

Abstract

The present disclosure relates to multi-interface transponder devices. A method for performing power management on a multi-interface transponder (MIT) device, such as a location tag device, is disclosed. The MIT device can transition between various power states based on, for example, detected events such as detecting movement of the MIT device, receiving a wake-up signal, receiving an indication of a transport mode transition, and / or detecting that the MIT device may be lost, such as due to a loss of contact with another device for a threshold period of time.

Description

[0001] Priority data

[0002] This application is a divisional application of the invention patent application with Chinese national application number 202010120544.7, application date February 26, 2020, and invention name “Multi-interface transponder device”.

[0003] This patent application claims the benefit of priority to U.S. Provisional Patent Application Serial No. 62 / 810,492, filed on February 26, 2019, and entitled “Multi-Interface Transponder Device,” which is hereby incorporated by reference in its entirety as if fully and entirely set forth herein. Technical Field

[0004] This patent application relates to wireless communications, including techniques for designing and operating multi-interface radio frequency transponder devices (or "tags"). Background Art

[0005] Location tags, such as electronic tracking devices, provide users with many ways to track the location of associated people and / or objects. For example, Global Positioning System (GPS) technology can be used to determine the location of a tagged object associated with a person, and the location can be transmitted to another device. As another example, a location tag can be attached to an important item (e.g., keys, wallets, briefcases, articles of clothing, backpacks, computing devices, identification items, etc.), and via communication with a companion device (e.g., a phone, tablet, laptop, Internet of Things (IoT) device, etc.), the location tag can update the location of the important item and help find the item if it is lost.

[0006] Conventional location tags (or tracking devices) and corresponding systems typically have one or more disadvantages. For example, communicating with a location tag outside of near field communication requires a substantial amount of power relative to the form factor. Consequently, the battery life of the location tag is typically limited. Furthermore, long-range communication for such devices is relatively expensive and often requires complex circuitry for operation in conjunction with associated electronic devices (e.g., mobile devices). Additionally, low-power options for location tags are typically limited to communicating with nearby objects, which may require a user associated with one or more tracking devices to be within proximity (e.g., near field) of the location tag, limiting the usefulness of such devices. Summary of the Invention

[0007] Embodiments described herein relate to multi-interface transponder (MIT) devices, such as, for example, location tag devices. Additionally, embodiments described herein relate to power management of MIT devices and various applications of such devices. Some embodiments relate to a wireless station configured to communicate with a MIT device, for example, to determine and / or update the location of the MIT device using a location server and / or to assist a user of the MIT device in physically locating the device if the MIT device is misplaced and / or lost.

[0008] In some embodiments, the MIT device may be configured to, while operating in a first power state, determine a transition to a second power state based at least in part on the detection of an event. In some embodiments, the event may be detected via one of a first interface or a motion sensing circuit of the MIT device. Furthermore, the MIT device may be configured to, while operating in the second power state, transmit one or more beacons via one of a second interface or a third interface of the MIT device. In some embodiments, the selection of the second interface or the third interface may be based at least in part on the event. In some embodiments, the first interface may be an ultra-low-power radio frequency (RF) interface (e.g., such as a wake-up radio and / or a wake-up receiver), the second interface may be a Bluetooth interface, and the third interface may be an ultra-wideband (UWB) RF interface. In some embodiments, the first power state may be associated with a low-power consumption (e.g., sleep) state, while the second power state may be associated with a higher-power consumption state. For example, the second state may be associated with the transmission of Bluetooth beacons (or signals) at a first rate or a second rate and / or with the transmission of UWB beacons (or signals). In some embodiments, the MIT device may be configured to receive an indication from a neighboring wireless device that a location associated with the MIT device has been updated at a location server, which may be associated with both the neighboring wireless device and the MIT device. The MIT device may be configured to, upon receiving the indication, transition to the first power state based at least in part on the indication.

[0009] In some embodiments, the MIT device may be configured to enter a low-power mode in which the second radio is disabled and receive a wake-up signal from a neighboring wireless device while in low-power mode. In some embodiments, the wake-up signal is received via low-power / ultra-low-power (LP / ULP) communication. The MIT device may be configured to transmit a beacon via the second radio after transitioning to a higher-power mode in response to receiving the wake-up signal. In some embodiments, the wake-up signal may indicate a transmission rate, which may be based at least in part on one or more of a traffic pattern detected by the neighboring wireless device and / or expected medium congestion detected by the neighboring wireless device. In some embodiments, the wake-up signal may indicate a transmission power, which may be based at least in part on one or more of a traffic pattern detected by the neighboring wireless device and / or expected medium congestion detected by the neighboring wireless device. In some embodiments, the second radio may include an ultra-wideband radio.

[0010] In some embodiments, the MIT device may be configured to operate in a low power mode in which an ultra-wideband (UWB) radio component of the MIT device may be disabled. The MIT device may be configured to receive a wake-up signal from a neighboring wireless device and transition out of the low power mode while operating in the low power mode, and enable the UWB radio component in response to receiving the wake-up signal. In some embodiments, the wake-up signal may be received by the ultra-low power radio component, for example, via ULP / LP communication with the neighboring wireless device. The MIT device may be configured to transmit a location beacon to the neighboring wireless device via the UWB radio component. In some embodiments, the wake-up signal may be received via one of a Bluetooth radio component or an ultra-low power radio component (e.g., such as a wake-up radio component and / or a wake-up receiver) that communicates with at least one processor. In some embodiments, the wake-up signal may indicate a transmission rate and a transmission power of the location beacon.

[0011] This summary is intended to provide a brief overview of some of the subject matter described in this document. It should be understood, therefore, that the features described above are merely examples and should not be construed as narrowing the scope or essence of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following detailed description, accompanying drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0013] Figure 1 An example of a wireless communication system according to some embodiments is shown.

[0014] Figure 2AExamples of wireless device communications according to some embodiments are shown.

[0015] Figure 2B An exemplary simplified block diagram of a wireless device according to some embodiments is shown.

[0016] Figure 2C An exemplary WLAN communication system is shown in accordance with some embodiments.

[0017] Figure 3A An exemplary simplified block diagram of a WLAN access point (AP) is shown in accordance with some embodiments.

[0018] Figure 3B An exemplary simplified block diagram of a wireless station (UE) is shown in accordance with some embodiments.

[0019] Figure 3C An exemplary simplified block diagram of a wireless node according to some embodiments is shown.

[0020] Figure 4 An exemplary simplified block diagram of a location tag device is shown in accordance with some embodiments.

[0021] Figure 5 An exemplary state diagram illustrating various power modes of a multiple interface transponder (MIT) device according to some embodiments is shown.

[0022] Figures 6A-6C An example of a MIT device updating location via neighboring devices according to some embodiments is shown.

[0023] Figure 7 A block diagram illustrating an example of a method for power management of a MIT device according to some embodiments is shown.

[0024] Figure 8A An example of a transmission cycle for a multi-interface transponder (MIT) device is shown in accordance with some embodiments.

[0025] Figure 8B An example of transmission power adjustment as a function of time since the last location update is shown in accordance with some embodiments.

[0026] Figure 9 A block diagram illustrating an example of a method for power managing a MIT device based on detected conditions, according to some embodiments.

[0027] Figure 10 A block diagram illustrating an example of a method for power management of a MIT device based on detection of a transport mode transition, according to some embodiments.

[0028] Figure 11-14A block diagram illustrating an example of a method of operating a MIT device according to some embodiments.

[0029] Figure 15 A block diagram illustrating an example of a method of scanning for MIT devices according to some embodiments.

[0030] While 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 herein described in detail. It should be understood, however, that the drawings and detailed description thereof are not intended to limit this disclosure to the specific forms disclosed, but on the contrary, are intended to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims. DETAILED DESCRIPTION

[0031] Acronyms

[0032] Various acronyms are used throughout this application. The definitions of the most prominent acronyms used that may appear throughout this application are as follows:

[0033] UE: User Equipment

[0034] AP: Access Point

[0035] TX: Transmit / Transmit

[0036] RX: Receive / Receive

[0037] WURx: Wake-up Receiver

[0038] UWB: Ultra Wideband

[0039] BT / BLE: Bluetooth TM / Bluetooth TM Low power consumption

[0040] LP / ULP: Low Power / Ultra-Low Power Communications

[0041] LAN: Local Area Network

[0042] WLAN: Wireless Local Area Network

[0043] RAT: Radio Access Technology

[0044] TTL: Time to Live

[0045] SU: Single User

[0046] MU: Multi-User

[0047] the term

[0048] The following is a glossary of terms used in this disclosure:

[0049] Memory medium - 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-ROMs, floppy disks, or tape devices; 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 drives or optical storage devices; registers or other similar types of memory elements, etc. The memory medium may also include other types of non-transitory memory or a combination thereof. In addition, the memory medium may be located in the first computer system that executes the program, or may be located in a different second computer system that is 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 (for example, expressed as a computer program) that can be executed by one or more processors.

[0050] Carrier Medium—storage media as described above, and physical transmission media such as a bus, network, and / or other physical transmission media that transport signals such as electrical, electromagnetic, or digital signals.

[0051] Computer System—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.

[0052] Location Tag (or Tracking Device)—any of various types of computer system devices that are mobile or portable and that perform wireless communications, such as communicating with adjacent or companion devices to share, determine, and / or update the location of the location tag. Wireless communications may be via various protocols, including but not limited to Bluetooth, Bluetooth Low Energy (BLE), Wi-Fi, Ultra-Wideband (UWB), and / or one or more proprietary communication protocols.

[0053] Mobile Device (or Mobile Station)—Any of various types of computer system devices that are mobile or portable and that perform wireless communications using WLAN communications. Examples of mobile devices include mobile phones or smartphones (e.g., iPhone TM , based on Android TMphones), and devices like iPads TM 、Samsung Galaxy TM Various other types of devices also fall into this category if they include Wi-Fi or cellular and Wi-Fi communication capabilities, for example, laptop computers (such as MacBooks TM ), portable gaming devices (e.g., Nintendo DS TM PlayStation Portable TM 、Gameboy Advance TM , iPhone TM ), portable internet devices and other handheld devices, as well as wearable devices such as smart watches, smart glasses, headphones, pendants, earpieces, etc. In general, the term "mobile device" can be broadly defined to cover any electronic, computing and / or telecommunication device (or combination of devices) that can be easily moved by a user and can communicate wirelessly using WLAN or Wi-Fi.

[0054] Wireless device (or wireless station) - any of various types of computer system devices that perform wireless communications using WLAN communications. As used herein, the term "wireless device" can refer to a mobile device as defined above or a stationary device such as a stationary wireless client or wireless base station. For example, a wireless device can be any type of wireless station for an 802.11 system, such as an access point (AP) or a client station (STA or UE). Other examples include televisions, media players (such as Apple TV), and wireless routers. TM , Roku TM , Amazon FireTV TM , Google Chromecast TM etc.), refrigerators, washing machines, thermostats, etc.

[0055] WLAN—The term "WLAN" has the full scope of its ordinary meaning and includes at least a wireless communication network, or RAT, that is served by WLAN access points and provides connectivity to the Internet through those access points. Most modern WLANs are based on the IEEE 802.11 standard and are marketed under the name "Wi-Fi." WLAN networks are distinct from cellular networks.

[0056] Processing Element—refers to various implementations of digital circuitry that performs a function in a computer system. Additionally, a processing element may refer to various implementations of analog or mixed-signal (a combination of analog and digital) circuitry that performs a function (or functions) in a computer or computer system. Processing elements include, for example, circuits such as integrated circuits (ICs), 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 that include multiple processors.

[0057] Automatic—refers to an action or operation being performed by a computer system (e.g., software executed by the computer system) or a device (e.g., a circuit, a programmable hardware element, an ASIC, etc.) without requiring user input to directly specify or execute the action or operation. Thus, the term "automatically" is in contrast to an action being manually performed or specified by a user, where the user provides input to directly perform the action. An automatic process may be initiated by user-provided input, but the subsequent "automatically" performed actions are not specified by the user, e.g., not "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 information, selecting checkboxes, selecting radios, etc.) is not manually filling out the form, even though the computer system must update the form in response to the user's actions. The form may be automatically filled out by a computer system, where the computer system (e.g., software executing on the computer system) analyzes the fields of the form and fills it out without requiring any user input to specify the answers to the fields. As indicated above, a user may invoke the automatic filling of a form without participating in the actual filling out of the form (e.g., the user does not manually specify the answers to the fields; they are automatically completed). This specification provides various examples of operations that are automatically performed in response to actions that a user has taken.

[0058] Concurrency - refers to parallel execution or implementation, where tasks, processes, signaling, messages, or programs are executed in an at least partially overlapping manner. For example, concurrency can be achieved using "strong" or strict parallelism, where tasks are executed (at least partially) in parallel on respective computing elements, or using "weak parallelism," where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0059] Configured to—Various components may be described as being “configured to” perform one or more tasks. In such contexts, “configured to” is a broad statement that generally means “having a structure” to perform 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 contexts, “configured to” can be a broad statement that generally means “having circuitry 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 turned on. Typically, the circuitry that forms the structure corresponding to “configured to” may include hardware circuitry.

[0060] 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." Representing a component as being configured to perform one or more tasks expressly intends that the component not be interpreted under 35 U.S.C. §112(f).

[0061] About—refers to a value that is close to the correct or exact value. For example, about may refer to a value that is within 1% to 10% of the exact (or desired) value. However, it should be noted that the actual threshold value (or tolerance) may depend on the application. For example, in one embodiment, "about" may mean within 0.1% of a specified or desired value, while in various other embodiments, the threshold value may be, for example, 2%, 3%, 5%, etc., depending on the desires or requirements of the particular application.

[0062] Figure 1 —Wireless communication system

[0063] Figure 1 An exemplary wireless communication system according to some embodiments is shown. Note that Figure 1The system is only one example of a possible system, and the embodiments of the present disclosure may be implemented in any of a variety of systems as needed. As shown, the exemplary system 100 includes multiple wireless client stations or devices or user equipment (UE) 106 configured to communicate wirelessly with various components within the system 100, such as an access point (AP) 112, other client stations 106, wireless nodes 107 and / or location tag devices 108. Some specific implementations may include one or more base stations in addition to or instead of AP 112. AP 112 may be a Wi-Fi access point and may include one or more other radio / access technologies (e.g., Bluetooth (BT), ultra-wideband (UWB), etc.) for wireless communication with various components of the system 100. AP 112 can communicate with one or more other electronic devices (not shown) and / or another network (such as the Internet) via wired and / or wireless communication channels. AP 112 can be configured to operate according to any of a variety of communication standards, such as various IEEE 802.11 standards and one or more proprietary communication standards, for example based on broadband, ultra-wideband and / or additional short-range / low-power wireless communication technologies. In some embodiments, at least one client station 106 may be configured to communicate directly with one or more neighboring devices (e.g., other client stations 106, wireless nodes 107, and / or location tag devices 108) without using an access point 112 (e.g., peer-to-peer (P2P) or device-to-device (D2D)). As shown, the wireless node 107 may be implemented as any of a variety of devices, such as a wearable device, a gaming device, etc. In some embodiments, the wireless node 107 may be various Internet of Things (IoT) devices, such as smart appliances (e.g., refrigerators, stoves, ovens, dishwashers, washing machines, clothes dryers, etc.), smart thermostats, and / or other home automation devices (e.g., such as smart power outlets, smart lighting fixtures, etc.).

[0064] As shown, location tag device 108 can communicate with one or more other components within system 100. In some embodiments, location tag device 108 can be associated with a companion device (e.g., client station 106) and can additionally communicate with one or more additional devices (e.g., other client stations 106, wireless nodes 107, AP 112). In some embodiments, communication with the companion device can be via one or more access technologies / protocols, such as Bluetooth. TM (and / or Bluetooth TMIn some embodiments, communication with additional devices may be via BT / BLE and one or more other short-range peer-to-peer wireless communication technologies (e.g., various near field communication (NFC) technologies, RFID, NAN, Wi-Fi Direct, UWB, LT / ULP, etc.). In some embodiments, the location tag device 108 is capable of updating a server with its current location (e.g., determined by the tag device 108 and / or provided to the tag device 108 from another device) via one or more additional devices and via a companion device.

[0065] Figure 2A-2B —Wireless communication system

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

[0067] As shown, the exemplary wireless communication system includes a ("first") wireless device 105 in communication with another ("second") wireless device 108. The first wireless device 105 and the second wireless device 108 may communicate wirelessly using any of a variety of wireless communication technologies.

[0068] As one possibility, the first wireless device 105 and the second wireless device 108 can communicate using wireless local area network (WLAN) communication technology (e.g., communication based on IEEE 802.11 / Wi-Fi) and / or WLAN wireless communication based technology. One or both of the wireless device 105 and the wireless device 108 can also (or alternatively) communicate via one or more additional wireless communication protocols, such as Bluetooth. TM (BT), Bluetooth TM Any of Bluetooth Low Energy (BLE), Near Field Communication (NFC), RFID, UWB, LP / ULP, GSM, UMTS (WCDMA, TDSCDMA), LTE, LTE-Advanced (LTE-A), NR, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-MAX, GPS, etc.

[0069] Wireless device 105 and wireless device 108 can be any of various types of wireless devices. As one possibility, wireless device 105 can be a substantially portable wireless user equipment (UE) device, such as a smartphone, a handheld device, a laptop, a wearable device (such as a smartwatch), a tablet, a motor vehicle, or virtually any type of wireless device. As another possibility, wireless device 105 can be a substantially stationary device, such as a toll booth / collection device, a point-of-sale (POS) terminal, a set-top box, a media player (e.g., an audio or audio-visual device), a game console, a desktop computer, an appliance, a door, an access point, a base station, or any of various other types of devices. Wireless device 108 can be a location tag device, for example, in a standalone form factor, associated with, attached to, and / or otherwise integrated into another computing device, and / or associated with, attached to, and / or integrated into a personal item or device (e.g., a wallet, backpack, luggage, briefcase, wallet, key ring / key chain, personal identification, etc.) and / or a commercial item (e.g., a shipping container, shipping / storage pallet, inventory items, vehicle, etc.).

[0070] Each of the wireless device 105 and the wireless device 108 may include wireless communication circuitry configured to facilitate the performance of wireless communication, which may include various digital and / or analog radio frequency (RF) components, one or more processors configured to execute program instructions stored in memory, one or more programmable hardware elements such as field programmable gate arrays (FPGAs), programmable logic devices (PLDs), application specific integrated circuits (ASICs), and / or any of a variety of other components. The wireless device 105 and / or the wireless device 108 may use any or all of such components to perform any method implementation or operation described herein, or any portion of any method implementation or operation described herein.

[0071] Each of wireless device 105 and wireless device 108 may include one or more antennas and corresponding RF front-end circuitry for communicating using one or more wireless communication protocols. In some cases, one or more portions of a receive chain and / or transmit chain may be shared between multiple wireless communication standards; for example, a device may be configured to communicate using BT / BLE or Wi-Fi while using partially or fully shared wireless communication circuitry (e.g., using a shared radio or one or more shared radio components). The shared communication circuitry may include a single antenna, or may include multiple antennas for performing wireless communication (e.g., for MIMO). Alternatively, a device may include a separate transmit chain and / or receive chain (e.g., including separate antennas and other radio components) for each wireless communication protocol it is configured to communicate using. As another possibility, a device may include one or more radios or radio components shared between multiple wireless communication protocols, as well as one or more radios or radio components used exclusively by a single wireless communication protocol. For example, a device may include a shared radio for communicating using one or more of LTE, CDMA2000 1xRTT, GSM, and / or 5G NR, and one or more independent radios for communicating using Wi-Fi and / or BT / BLE. Other configurations are also possible.

[0072] As mentioned above, it can be combined with Figure 2A For example, a wireless device (e.g., any of the wireless devices 105 or 108) may be configured to implement (and / or facilitate implementation of) the methods described herein.

[0073] Figure 2B An exemplary wireless device 110 (e.g., corresponding to wireless device 105 and / or wireless device 108) that can be configured for use in conjunction with various aspects of the present disclosure is shown. Device 110 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 110 can be a substantially portable device or a substantially stationary device, potentially including any of a variety of types of devices. Device 110 can be configured to perform any of the techniques or features described herein, including those shown and / or described with respect to any or all of the figures.

[0074] As shown, device 110 may include processing element 121. The processing element may include or be coupled to one or more memory elements. For example, device 110 may include one or more storage media (e.g., memory 111), which may include any of various types of memory and may be used for any of a variety of functions. For example, memory 111 may be RAM used as system memory for processing element 121. In addition or alternatively, memory 111 may be ROM used as configuration memory for device 110. Other types and functions of memory are also possible.

[0075] Additionally, device 110 may include wireless communication circuitry 131. 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.

[0076] It should be noted that in some cases, wireless communication circuitry 131 may include its own processing element (e.g., a baseband processor) in addition to processing element 121. For example, processing element 121 may be an "application processor" whose primary function may be to support application layer operations in device 110, while wireless communication circuitry 131 may be a "baseband processor" whose primary function may be to support baseband layer operations in device 110 (e.g., to facilitate wireless communication between device 110 and other devices). In other words, in some cases, device 110 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.

[0077] Depending on the intended functionality of device 110, device 110 may additionally include any of a variety of other components (not shown) for implementing the device functionality, which may also include processing elements and / or memory elements (e.g., audio processing circuitry), one or more power supply 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.

[0078] Components of device 110, such as processing element 121, memory 111 and wireless communication circuit 131, can be operably (or communicatively) coupled via one or more interconnect interfaces, which can include any of a variety of types of interfaces, possibly including a combination of multiple types of interfaces. As an example, a USB high-speed inter-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 inter-integrated circuit (I2C), a system management bus (SMBus) and / or a variety of 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 processing element 121, a peripheral interface for communicating with peripheral components inside or outside device 110, etc.) can also be provided as part of device 110.

[0079] Figure 2C —WLAN system

[0080] Figure 2C An exemplary WLAN system according to some embodiments is shown. As shown, the exemplary WLAN system includes multiple wireless client stations or devices, or user equipment (UE) 106, which are configured to communicate with an access point (AP) 112 via a wireless communication channel 142. In some embodiments, AP 112 can be a Wi-Fi access point. AP 112 can communicate with one or more other electronic devices (not shown) and / or another network 152 (such as the Internet) via a wired and / or wireless communication channel 150. Additional electronic devices, such as remote devices 154, can communicate with components of the WLAN system via network 152. For example, remote device 154 can be another wireless client station. The WLAN system can be configured to operate according to any of a variety of communication standards, such as various IEEE 802.11 standards. In some embodiments, at least one wireless device 106 is configured to communicate directly with one or more adjacent mobile devices (such as location tag device 108) without using access point 112.

[0081] Furthermore, in some embodiments, as further described below, wireless device 106 (which may be an exemplary implementation of device 110 ) may be configured to perform (and / or facilitate performance of) the methods described herein.

[0082] Figure 3A —Access Point Block Diagram

[0083] Figure 3A An exemplary block diagram of an access point (AP) 112 is shown, which may be Figure 2B One possible exemplary implementation of the device 110 is shown. Note that Figure 3A The block diagram of the AP 112 is merely one example of a possible system. As shown, the AP 112 may include one or more processors 204 that may execute program instructions for the AP 112. The one or more processors 204 may also be coupled (directly or indirectly) to a memory management unit (MMU) 240 or other circuit or device that may be configured to receive addresses from the one or more processors 204 and translate those addresses into locations in memory (e.g., memory 260 and read-only memory (ROM) 250).

[0084] AP 112 may include at least one network port 270. Network port 270 may be configured to couple to a wired network and provide access to the Internet for multiple devices, such as mobile device 106. For example, network port 270 (or an additional network port) may be configured to couple to a local network, such as a home network or an enterprise network. For example, port 270 may be an Ethernet port. The local network may provide connectivity to one or more additional networks, such as the Internet.

[0085] AP 112 may include at least one antenna 234 and wireless communication circuitry 230, which may be configured to operate as a wireless transceiver and may be further configured to communicate with mobile device 106 (and location tag device 108). Antenna 234 communicates with wireless communication circuitry 230 via communication chain 232. Communication chain 232 may include one or more receive chains and / or one or more transmit chains. Wireless communication circuitry 230 may be configured to communicate via Wi-Fi or WLAN, such as 802.11. Wireless communication circuitry 230 may also or alternatively be configured to communicate via various other wireless communication technologies, including but not limited to BT / BLE, UWB, and / or LP / ULP. Additionally, in some embodiments, for example, when the AP is co-located with a base station in the case of a small cell, or in other situations where it may be desirable for the AP 112 to communicate via a variety of different wireless communication technologies, the wireless communication circuitry 230 may also or alternatively be configured to communicate via a variety of other wireless communication technologies, including but not limited to Long Term Evolution (LTE), LTE-Advanced (LTE-A), Global System for Mobile (GSM), Wideband Code Division Multiple Access (WCDMA), CDMA2000, and the like.

[0086] Furthermore, in some embodiments, as described further below, AP 112 may be configured to perform (and / or facilitate the performance of) the methods described herein.

[0087] Figure 3B —Client site diagram

[0088] Figure 3B An exemplary simplified block diagram of a client site 106 is shown, which may be Figure 2B One possible exemplary implementation of the device 110 is shown. According to various embodiments, the client site 106 may be a user equipment (UE) device, a mobile device or mobile station and / or a wireless device or wireless station. As shown, the client site 106 may include a system on a chip (SOC) 300, which may include parts for various purposes. The SOC 300 may be coupled to various other circuits of the client site 106. For example, the client site 106 may include various types of memory (e.g., including NAND flash memory 310), a connector interface (I / F) (or docking station) 320 (e.g., for coupling to a computer system, a docking station, a charging station, etc.), a display 360, cellular communication circuitry 330 (such as for LTE, GSM, etc.), medium and short range wireless communication circuitry 329 (e.g., Bluetooth TM The client site 106 may also include one or more smart cards 310 incorporating SIM (Subscriber Identity Module) functionality, such as one or more UICC (Universal Integrated Circuit Card) cards 345. The cellular communication circuitry 330 may be coupled to one or more antennas, such as antennas 335 and 336, as shown. The short- to medium-range wireless communication circuitry 329 may also be coupled to one or more antennas, such as antennas 337 and 338, as shown. The LP / ULP radio 339 may be coupled to one or more antennas, such as antennas 347 and 348, as shown. Additionally, the UWB radio 341 may be coupled to one or more antennas, such as antennas 345 and 346. Alternatively, the radios may share one or more antennas in addition to or in lieu of being coupled to respective antennas or groups of antennas. Any or all of the radios may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, for example, in a multiple-input, multiple-output (MIMO) configuration.

[0089] As shown, the SOC 300 may include one or more processors 302 that may execute program instructions for the client station 106 and display circuitry 304 that may perform graphics processing and provide display signals to a display 360. The SOC 300 may also include motion sensing circuitry 370 that may detect motion of the client station 106 using, for example, a gyroscope, an accelerometer, and / or any of a variety of other motion sensing components. The one or more processors 302 may also be coupled to a memory management unit (MMU) 340 and / or other circuits or devices (such as the display circuitry 304, cellular communication circuitry 330, short-range wireless communication circuitry 329, LP / ULP communication circuitry 339, UWB communication circuitry 341, a connector interface (I / F) 320, and / or a display 360). The MMU may be configured to receive addresses from the one or more processors 302 and translate these addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of one or more processors 302.

[0090] As described above, the client station 106 may be configured to communicate wirelessly directly with one or more neighboring client stations and / or one or more location tag devices 108. The client station 106 may be configured to communicate according to a WLAN RAT used for communicating in a WLAN network, such as Figure 2C Furthermore, in some embodiments, as further described below, the client site 106 can be configured to perform (and / or facilitate the performance of) the methods described herein.

[0091] As described herein, the client site 106 may include hardware and / or software components for implementing the features described herein. For example, the processor 302 of the client site 106 may be configured to implement some or all of the features described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the processor 302 may be configured as a programmable hardware element such as an FPGA (field programmable gate array) or as an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 300, 304, 306, 310, 320, 329, 330, 335, 336, 337, 338, 339, 340, 341, 345, 346, 347, 348, 350, and / or 360, the processor 302 of the UE 106 may be configured to implement some or all of the features described herein.

[0092] Furthermore, as described herein, processor 302 may include one or more processing elements. Thus, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 204.

[0093] Furthermore, as described herein, each of the cellular communication circuitry 330 and the short-range wireless communication circuitry 329 may include one or more processing elements. Thus, each of the cellular communication circuitry 330 and the short-range wireless communication circuitry 329 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuitry 330 and the short-range wireless communication circuitry 329, respectively.

[0094] Figure 3C —Wireless node block diagram

[0095] Figure 3C shows a possible block diagram of a wireless node 107, which may be Figure 2B . As shown, the wireless node 107 may include a system-on-chip (SOC) 301, which may include components for various purposes. For example, as shown, the SOC 301 may include one or more processors 303, which may execute program instructions for the wireless node 107, and display circuitry 305, which may perform graphics processing and provide display signals to a display 361. The SOC 301 may also include motion sensing circuitry 371, which may detect motion of the wireless node 107 using, for example, a gyroscope, an accelerometer, and / or any of various other motion sensing components. The processor 303 may also be coupled to a memory management unit (MMU) 341, which may be configured to receive addresses from the one or more processors 303 and convert these addresses to locations in a memory (e.g., memory 307, read-only memory (ROM) 351, flash memory 311). The MMU 341 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 341 may be included as part of one or more processors 303.

[0096] As shown, the SOC 301 may be coupled to various other circuits of the wireless node 107. For example, the wireless node 107 may include various types of memory (e.g., including NAND flash memory 311), a connector interface 321 (e.g., for coupling to a computer system, a docking station, a charging station, etc.), a display 361, and wireless communication circuitry (radio) 381 (e.g., for LTE, LTE-A, CDMA2000, Bluetooth, Wi-Fi, NFC, GPS, UWB, LP / ULP, etc.).

[0097] The wireless node 107 may include at least one antenna, and in some embodiments, may include multiple antennas 387 and 388 for performing wireless communications with base stations and / or other devices. For example, the wireless node 107 may perform wireless communications using antennas 387 and 388. As described above, the wireless node 107 may, in some embodiments, be configured to perform wireless communications using multiple wireless communication standards or radio access technologies (RATs).

[0098] Wireless communication circuitry (radio) 381 may include Wi-Fi logic 382, ​​a cellular modem 383, BT / BLE logic 384, UWB logic 385, and LP / ULP logic 386. Wi-Fi logic 382 is used to enable wireless node 107 to perform Wi-Fi communications over, for example, an 802.11 network and / or via peer-to-peer communications (e.g., NAN). BT / BLE logic 384 is used to enable wireless node 107 to perform Bluetooth communications. Cellular modem 383 may be capable of performing cellular communications based on one or more cellular communication technologies. UWB logic 385 is used to enable wireless node 107 to perform UWB communications. LP / ULP logic 386 is used to enable wireless node 107 to perform LP / ULP communications. Some or all of the components of wireless communication circuitry 381 may be used to communicate with location tag device 108.

[0099] As described herein, the wireless node 107 may include hardware components and software components for implementing embodiments of the present disclosure. For example, one or more components of the wireless communication circuitry 381 of the wireless node 107 may be configured to implement some or all of the methods described herein, such as by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), by 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). For example, in some embodiments, as further described below, the wireless node 107 may be configured to perform (and / or facilitate the performance of) the methods described herein.

[0100] Figure 4 :Location tag device

[0101] Figure 4 An exemplary simplified block diagram of a location tag device 108 is shown, which may be Figure 2B One possible exemplary implementation of the device 110 is shown. Depending on the embodiment, the location tag device 108 may include a system on a chip (SOC) 400, which may include one or more parts for performing one or more purposes (or functions or operations). The SOC 400 may be coupled to one or more other circuits of the location tag device 108. For example, the location tag device 108 may include various types of memory (e.g., including NAND flash memory 410), a connector interface (I / F) 420 (e.g., for coupling to a computer system, a docking station, a charging station, a light (e.g., for visual output), a speaker (e.g., for auditory output), etc.), a power supply 425 (which may be non-removable, removable and replaceable, and / or rechargeable), and communication circuitry (radio components) 451 (e.g., BT / BLE, WLAN, LP / ULP, UWB).

[0102] The location tag device 108 may include at least one antenna, and in some embodiments, may include multiple antennas 457 and 458 for wireless communication with companion devices (e.g., client station 106, wireless node 107, AP 112, etc.) and other wireless devices (e.g., client station 106, wireless node 107, AP 112, other location tag devices 108, etc.). In some embodiments, one or more antennas may be dedicated for use with a single radio component and / or radio protocol. In some other embodiments, one or more antennas may be shared between two or more radio components and / or radio protocols. The wireless communication circuitry 451 may include any / all of the UWB logic component 452, the LP / ULP logic component 453, and / or the BT / BLE logic component 454. In some embodiments, the wireless communication circuitry may optionally include logic components for any other protocols, such as Wi-Fi logic components and / or cellular (e.g., License Assisted Access (LAA)) logic components. The BT / BLE logic component 454 is used to enable the location tag device 108 to perform Bluetooth communications. The UWB logic component 452 is used to enable the location tag device 108 to perform UWB communication. The LP / ULP logic component 453 is used to enable the location tag device 108 to perform LP / ULP communication. In some embodiments, the wireless communication circuit 451 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input multiple-output (MIMO) configuration. The UWB logic component 452, the LP / ULP logic component 453, and the BT / BLE logic component 454 can each be independently configured to perform unidirectional or bidirectional communication.

[0103] As shown, the SOC 400 may include one or more processors 402 that may execute program instructions for the location tag device 108. The SOC 400 may also include motion sensing circuitry 470 that may be configured to detect motion of the location tag device 108 using, for example, a gyroscope, an accelerometer, and / or any of a variety of other motion sensing components. In some embodiments, a GPS receiver and associated circuitry may be used in addition to or in lieu of other motion sensing circuitry. The one or more processors 402 may also be coupled (directly or indirectly) to a memory management unit (MMU) 440 and / or other circuitry or devices that may be configured to receive addresses from the one or more processors 402 and translate those addresses into locations in memory (e.g., memory 406, read-only memory (ROM) 450, NAND flash memory 410), such as wireless communication circuitry 451. The MMU 440 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 440 may be included as part of the one or more processors 402.

[0104] As described above, the location tag device 108 can be configured to communicate wirelessly with one or more adjacent wireless devices. In some embodiments, as further described below, the location tag device 108 can be configured to perform (and / or facilitate the performance of) the methods described herein.

[0105] Location tag power management

[0106] In some embodiments, a multi-interface transponder (MIT) device, such as location tag device 108, may include multiple power levels and / or power modes. For example, Figure 5An exemplary state diagram illustrating various power modes of a MIT device according to some embodiments is shown. As shown, the MIT device can operate in any of a plurality of power modes, such as low power mode 502, ultra-low power mode 504, high power mode 506, and / or ultra-high power mode 508. Furthermore, as shown, the MIT device can transition (or switch) between any of the various modes. Transitions between modes can be based on any factor or combination of factors, including one or more received signals, sensor data, timing data, environmental data, activity data, location data, and the like. Furthermore, the MIT device can be configured to transition directly from a current mode to any other available mode. However, in some implementations, transitions can include sequentially transitioning through one or more intermediate modes. For example, the MIT device can transition between low power mode 502 and any of ultra-low power mode 504 (e.g., via transition 510), higher power mode 506 (e.g., via transition 516), and / or ultra-high power mode 508 (e.g., via transition 518). As another example, the MIT device can transition between the ultra-low power mode 504 and any of the low power mode 502 (e.g., via transition 510), the higher power mode 506 (e.g., via transition 512), and / or the ultra-high power mode 508 (e.g., via transition 514). Similarly, the MIT device can transition between the high power mode 506 and any of the low power mode 502 (e.g., via transition 516), the ultra-low power mode 504 (e.g., via transition 512), and / or the ultra-high power mode 508 (e.g., via transition 520). Additionally, the MIT device can transition between the ultra-high power mode 508 and any of the low power mode 502 (e.g., via transition 518), the ultra-low power mode 504 (e.g., via transition 514), and / or the high power mode 506 (e.g., via transition 520).

[0107] In some embodiments, the ultra-low power mode 504 can be associated with an LP / ULP interface and / or LP / ULP logic, e.g., as described above with reference to the location tag device 108. In some embodiments, the MIT device can remain in the ultra-low power mode 504 until a triggering event occurs. In some embodiments, the triggering event can cause the MIT device to transition to a higher power operating mode (e.g., any of the low power mode 508, the high power mode 504, and / or the ultra-high power mode 508).

[0108] In some embodiments, the triggering event may be a signal / beacon received from a neighboring device. In some embodiments, the wake-up signal / beacon may be specific to the MIT device, or may be a general signal / beacon, for example, applicable to a group of MIT devices or all MIT devices. In other words, the MIT device may receive a wake-up signal / beacon from a neighboring device that wishes to wake up the MIT device, or the MIT device may receive a wake-up signal / beacon from a neighboring device that wishes to wake up any MIT device (or any device of a particular type of MIT device) within reception range of the wake-up signal / beacon. In some embodiments, the wake-up signal may be received via LP / ULP communication. In some embodiments, the wake-up signal may be received by an ultra-low power radio component, for example, via ULP / LP communication with a neighboring wireless device. In some embodiments, the wake-up signal / beacon may cause the MIT device to transition to a higher power operating mode (e.g., any of the low power mode 502, high power mode 504, and / or ultra-high power mode 508). In some embodiments, the transition from ultra-low power mode 504 can be slowed (or delayed) based at least in part on one or more factors, such as the current location area of ​​the MIT device and / or movement of the accompanying device.

[0109] For example, if the MIT device determines that its current location is within a safe area (e.g., such as the user's home, the user's workplace, the user's car, and / or a frequently visited location, such as a friend's or relative's home), the MIT device may delay or not invoke a transition to a higher power mode. As another example, if the MIT device determines that the movement of the companion device is similar to the movement of the MIT device, the MIT device may determine a constant motion state and delay or may not invoke a transition to a higher power state.

[0110] Conversely, in some embodiments, the transition from the ultra-low power mode 504 can be accelerated based at least in part on one or more factors, such as the current location or location area of ​​the MIT device and / or the current mode of transportation. For example, if the MIT device determines (or is notified) that a transportation transition (e.g., exiting a train, plane, ferry, taxi and / or boarding a train, plane, ferry, taxi) is occurring or is about to occur, the MIT device can accelerate the transition to the higher power mode (e.g., even in the absence of another triggering condition, such as separation from a companion device).

[0111] In some embodiments, the triggering event may be sensing movement of the MIT device. For example, the MIT device may monitor movement, such as via motion sensing circuitry, and transition from ultra-low power mode 504 to a higher power mode based at least in part on the movement of the MIT device. In some embodiments, the triggering event may be based at least in part on the time elapsed between location updates of the MIT device. In some embodiments, the time elapsed between location updates may be based at least in part on the location mode of the MIT device (e.g., safe area mode, dangerous area mode, lost mode, etc.).

[0112] For example, based on a triggering event, the MIT device may transition to low-power mode 502 and begin transmitting beacons and / or scanning at a first rate via the low-power interface. In some embodiments, the periodicity of beacon transmissions may be approximately 1 to 2 seconds. In some other embodiments, the periodicity of beacon transmissions may be less than 1 second, 1-5 seconds, or greater than 5 seconds. In some embodiments, beacons may be transmitted via a BLE interface or via BLE logic. In some embodiments, the transmission power of the beacons may be based at least in part on the location mode of the MIT device and / or the time since the last location update. For example, in a safe area mode, the MIT device may transmit beacons less frequently and at a lower power level upon wakeup than in a hazardous area mode, where the MIT device may transmit beacons more frequently and / or at a higher power level upon wakeup. In some embodiments, once the updated location is confirmed, the MIT device may transition back to ultra-low-power mode 504. In some embodiments, prior to transitioning to the ultra-low power mode 504, the MIT device may transition to one of the high power mode 506 and / or the ultra-high power mode 508 based on various criteria (e.g., detection of entry into a hazardous area, receipt of a command from a companion device, detection of movement, increased separation from a companion device, etc.).

[0113] As another example, based on a triggering event, the MIT device may transition to high power mode 506 and begin transmitting and / or receiving beacons at a second rate via the low power interface. In some embodiments, the periodicity of beacon transmissions may be approximately 1 to 10 milliseconds. In some other embodiments, the periodicity may be less than 1 millisecond, tens of milliseconds, or hundreds of milliseconds. In some embodiments, beacons may be transmitted via a BLE interface or via BLE logic. In some embodiments, the transmission power of the beacons may be based at least in part on the location mode of the MIT device and / or the time since the last location update. For example, in a safe area mode, the MIT device may transmit beacons at a lower frequency and / or a lower power level upon wakeup compared to a hazardous area mode, where the MIT device may transmit beacons at a higher frequency and / or a higher power level upon wakeup. In some embodiments, once the updated location is confirmed, the MIT device may transition back to ultra-low power mode 504. In some embodiments, prior to transitioning to the ultra-low power mode 504, the MIT device may transition to one of the low power mode 502 and / or the ultra-high power mode 508 based on various criteria (e.g., detection of entry into a hazardous area, receipt of a command from a companion device, detection of movement, separation from a companion device, etc.).

[0114] As another example, the MIT device may transition to ultra-high power mode 508 and begin transmitting beacons at a first rate over the high power interface. In some embodiments, the beacons may be transmitted via the UWB interface or via the UWB logic component. In some embodiments, ultra-high power mode 508 may be initiated while the companion device is searching for (e.g., attempting to accurately locate) the MIT device. In some embodiments, once the updated location is confirmed, the MIT device may transition back to ultra-low power mode 504. In some embodiments, before transitioning to ultra-low power mode 504, the MIT device may transition to one of low power mode 502 and / or ultra-high power mode 508 based on various criteria (e.g., detection of entry into a hazardous area, receipt of a command from a companion device, detection of movement, etc.).

[0115] Figures 6A-6CAn example of a MIT device updating its location via a neighboring device according to some embodiments is shown. As shown, the MIT device 608 may be within range of one or more neighboring devices, such as a companion (or trusted) device 602 (e.g., a device associated with the MIT device, such as a device used to register the MIT device with a location server (such as location server 614)) and / or non-companion devices 604a and 604n (e.g., devices associated with a location server (such as location server 614) but not associated with the MIT device). The MIT device 608 may detect / sense a triggering event, such as triggering event 620, 630, or 640. In response to the triggering event, the MIT device 608 may transition from an ultra-low power operating mode to a higher power operating mode and begin transmitting a beacon / signal 610. Note that the periodicity, power, and type of the beacon / signal transmitted by the MIT device 608 may be based at least in part on the power mode of the MIT device. Thus, in some embodiments, the beacon / signal 610 may be a lower power beacon / signal (e.g., a BLE beacon / signal) transmitted at a low rate (e.g., approximately every 1 to 2 seconds), a lower power beacon / signal transmitted at a high rate (e.g., approximately every 1 to 10 milliseconds), and / or a higher power beacon / signal (e.g., a UWB beacon / signal).

[0116] For example, Figure 6A As shown, after a triggering event 620, the MIT device 608 may transmit one or more beacons 610. At least one of the beacons 610 may be received by the companion device 602. Upon receiving at least one beacon 610, the companion device 602 may exchange communications 622 with the MIT device 608. Based on the communications 622, the companion device 602 may update the location server 614 with the updated location of the MIT device 608 via communications 624 and 626. In some embodiments, the communications 624 and 626 may be transmitted via a push notification connection with the location server 614. Once the location server 614 confirms the updated location of the MIT device 608, the companion device 602 may exchange one or more confirmation messages 628 with the MIT device 608. At 629, the MIT device 608 may transition back to ultra-low power mode and / or one or more other power modes, for example, as described above.

[0117] For example, Figure 6BAs shown, after a triggering event 630, the MIT device 608 may transmit one or more beacons 610. At least one of the beacons 610 may be received by the non-companion device 604a. Upon receiving at least one beacon 610, the non-companion device 604a may exchange communications 632 with the MIT device 608. Based on the communications 632, the non-companion device 604a may update the location server 614 with the updated location of the MIT device 608 via communications 634 and 636. In some embodiments, the communications 634 and 636 may be transmitted via a push notification connection with the location server 614. Once the location server 614 confirms the updated location of the MIT device 608, the non-companion device 604a may exchange one or more confirmation messages 638 with the MIT device 608. At 639, the MIT device 608 may transition back to ultra-low power mode and / or one or more other power modes, for example, as described above.

[0118] For example, Figure 6C As shown, after a triggering event 640, the MIT device 608 may transmit one or more beacons 610. At least one of the beacons 610 may be received by the non-companion device 604n. Upon receiving at least one beacon 610, the non-companion device 604n may exchange communications 642 with the MIT device 608. Based on the communications 642, the non-companion device 604n may update the location server 614 with the updated location of the MIT device 608 via communications 644 and 646. In some embodiments, the communications 644 and 646 may be transmitted via a push notification connection with the location server 614. Once the location server 614 confirms the updated location of the MIT device 608, the non-companion device 604n may exchange one or more confirmation messages 648 with the MIT device 608. At 649, the MIT device 608 may transition back to ultra-low power mode and / or one or more other power modes, for example, as described above.

[0119] Figure 7 A block diagram illustrating an example method for power management of a multi-interface transponder (MIT) device according to some embodiments. Figure 7 The method shown can be used in conjunction with any of the systems or devices shown in the accompanying drawings. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown in the figure, the method can be operated as follows.

[0120] At 702, while in a first power state, the MIT device may determine to transition to a second power state based at least in part on detecting an event. In some embodiments, the event may be detected via an interface (e.g., a first interface) and / or sensing circuitry (e.g., motion sensing circuitry) of the MIT device. For example, in some embodiments, the event may include receiving a wake-up indication via the first interface (from a companion device, such as client station 106 and / or wireless node 107). In some embodiments, the first interface may be an ultra-low power radio frequency (RF) interface (e.g., such as a wake-up radio and / or a wake-up receiver). In some embodiments, the event may include detecting movement (and / or a change in movement) of the MIT device, e.g., greater than a threshold. Note that in some embodiments, the MIT device may ignore movement detected by the motion circuitry, e.g., if the companion device indicates that the movement is associated with a transport mode.

[0121] At 704, the MIT device may transition to a second power state. In some embodiments, transitioning to the second power state may include activating a second interface of the MIT device. In some embodiments, the second interface may be one of a Bluetooth interface and / or an ultra-wideband (UWB) interface. In some embodiments, the MIT device may determine which interface to activate based at least in part on the detected event.

[0122] At 706, while in the second power state, the MIT device may transmit one or more beacons via the selected interface based at least in part on the detected event. For example, when the event includes receiving a wake-up indication, the wake-up indication may include instructions for activating a particular interface. Furthermore, in some embodiments, the instructions may include one or more transmission intervals and / or transmission powers. For example, the instructions may indicate activation of a Bluetooth interface. Furthermore, the instructions may indicate a transmission rate (e.g., a lower rate of approximately every one to two seconds, or a higher rate of approximately 1 to 10 milliseconds). Furthermore, the instructions may indicate a transmission power (e.g., based on congestion). As another example, the instructions may indicate activation of an ultra-wideband interface and associated transmission frequency and / or transmission power information.

[0123] At 708, while in the second power state, the MIT device may receive an indication regarding a location update from a neighboring wireless device. In some embodiments, the neighboring wireless device may be a companion device (e.g., a device that has a secure connection / security relationship with the MIT device). In some embodiments, the companion device may be a wireless station, such as wireless station 106. In some embodiments, the companion device may be a wireless node, such as wireless node 107. Note that a companion device may also include a device that assists the MIT device in registering with a location server. In some embodiments, a companion device may support multiple MIT devices. In some embodiments, the neighboring wireless device may be a non-companion device associated with a location server (e.g., a device that does not have a secure connection / security relationship with the MIT device). For example, a non-companion device may communicate with a location server and may be configured to update the location of a MIT device that is not associated with the non-companion device. Thus, the non-companion device may assist in updating the location of the MIT device, for example, when (or if) the MIT device becomes separated from the companion device (or out of communication range).

[0124] At 710, the MIT device may transition from the second power state to a third power state based at least in part on the indication. For example, in some embodiments, the indication may cause (or instruct) the MIT device to transition back to an ultra-low power state (e.g., such as ultra-low power mode 504). Alternatively, the indication may cause (or instruct) the MIT device to transition from a low transmission rate to a higher transmission rate (e.g., from a low power state such as low power mode 502 to a higher power state such as high power mode 506). In some embodiments, the indication may cause activation and / or deactivation of another interface. For example, the second power state may include activation of a Bluetooth interface, and transitioning to the third power state may result in activation of an ultra-wideband interface. Additionally, in some implementations, transitioning to the third power state may result in deactivation of a Bluetooth interface. For another example, the second power state may include activation of a Bluetooth or ultra-wideband interface, and transitioning to the third power state may include deactivation of the activated interface.

[0125] In some embodiments, power management of a multi-interface transponder (MIT) device (such as device 108) may be based at least in part on the geographic location and / or location pattern of the MIT device. For example, the MIT device may change its power mode based at least in part on a determination that the MIT device is lost (e.g., separated from a companion device for more than a specified period of time). As another example, the MIT device may change its power mode based at least in part on a determination that the MIT device is in (or within) a dangerous area during a transportation mode transition (such as a train stop, a car stop, an airplane landing, a ferry docking, etc.). As another example, the MIT device may consider multiple factors, such as companionship and location factors, with respect to changing its power mode. As yet another example, the MIT device may change its power mode based at least in part on a determination that the MIT device is in (or within) a safe area, such as a user's home, a place the user frequently visits (e.g., a friend's or relative's home, a workplace, etc.).

[0126] For example, in some embodiments, a multi-interface transponder (MIT) device (e.g., such as location tag device 108) may determine that it is lost based, for example, on a duration of time since the last communication with a companion device. In some embodiments, the determination may also be based, at least in part, on a duration of time since a location update and / or a signal was received from the device associated with a location server. In such cases, the MIT device may transition to a power state (or power mode) associated with a lost mode of operation. In some embodiments, operating in lost mode may include the MIT device changing and / or adjusting the transmit power and / or transmit rate to further conserve battery power and increase the probability of discovery. For example, the transmit rate may be based, at least in part, on the time of day, such as Figure 8A As shown, the MIT device may transmit beacons at a higher rate during certain parts of the day, for example, when it is more likely to encounter neighboring devices. In addition, in some embodiments, the MIT device may aggregate transmissions into short periods of time (e.g., transmission bursts) and not transmit (e.g., sleep) for most of the 24-hour period to further conserve battery power. For another example, Figure 8B As shown, the MIT device may adjust the transmission power based at least in part on the duration since the signal was received from the device associated with the location server. For example, the MIT device may increase the transmission power (e.g., to increase the transmission range) as the duration increases and / or during certain parts of the day. In some embodiments, the increase in transmission power may be offset by a decrease in the transmission periodicity and / or transmission period to preserve battery power, e.g., as Figure 8A Additionally, in some embodiments, the transmission power may be increased incrementally as the duration (e.g., since the last location update) increases, as shown in FIG. Figure 8BAs shown. In some embodiments, after a time period, the transmission power may be incrementally reduced to further conserve battery power. Note that as the time period (time since last contact) increases, the transmission decisions of the MIT device (e.g., transmission rate, transmission frequency, transmission power, etc.) may be changed to extend the battery life of the MIT device. In other words, when the time period is in the range of hours, the MIT device may adopt a different transmission mode (e.g., the most aggressive transmission mode, with less consideration for battery conservation) than when the time period is in the range of days (aggressive transmission mode, but with some consideration for battery conservation) or weeks (less aggressive transmission mode, with more consideration for battery endurance) or even months (most aggressive battery conservation, highly conservative transmission mode).

[0127] Figure 9 A block diagram illustrating another example of a method for power management of a multi-interface transponder (MIT) device according to some embodiments is shown. Figure 9 The method shown can be used in conjunction with any of the systems or devices shown in the accompanying drawings. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown in the figure, the method can be operated as follows.

[0128] At 902, a MIT device, such as device 108, may determine a status of the MIT device. In some embodiments, the status may be based at least in part on a duration since communication with a companion device.

[0129] In some embodiments, the condition may also be based at least in part on a duration since the MIT device received an indication that a location associated with the MIT device has been updated at the location server.

[0130] In some embodiments, the condition may also be based at least in part on a duration since the MIT device received a signal from a neighboring wireless device (e.g., such as wireless station 106, wireless node 107, and / or AP 112). In some embodiments, the condition may be associated with a determination that the MIT device has been lost (e.g., separated from a companion device).

[0131] At 904, the MIT device may transition to a first operating mode based at least in part on the condition.

[0132] In some embodiments, this operating mode may be associated with the lost operating mode and may be configured to extend the operating life of the MIT device. For example, in some embodiments, the first operating mode may include a long period of power conservation (e.g., sleep) followed by short bursts of beacon transmissions. In other words, the MIT device may transmit beacons at a high rate over a first interface (such as a Bluetooth interface) for a first portion of time (e.g., the first portion of a 24-hour period) and spend the remaining portion of time in a power-saving state. In some embodiments, the first portion of time may correspond at least in part to daylight hours (e.g., as sensed by a light sensor of the MIT device or to time kept by the MIT device) to increase the probability of discovery. In some embodiments, as the duration since the last location update increases, the MIT device may increase transmission power to increase the discovery range. Note that in some embodiments, because increasing transmission power can adversely affect power consumption, the MIT device may mitigate the increased power consumption by reducing the number of beacons transmitted in a period of time. Additionally, in some embodiments, the MIT device may vary the transmission frequency (or transmission cluster) in an attempt to discover neighboring wireless devices.

[0133] As another example, the MIT device may change its power mode based at least in part on determining that the MIT device is in (or within) a danger zone during a transportation mode transition (such as a train stop, a car stop, an airplane landing, a ferry docking, etc.). In some embodiments, a companion device, such as the client station 106 and / or the wireless node 107, may determine the transportation mode (e.g., vehicle, airplane, train, ship, etc.). In addition, the companion device may monitor movement to detect a transition in transportation mode (e.g., a vehicle stop, an airplane landing, a train slowing down, a ship docking, etc.) or a transition in location along a route (e.g., approaching a known transition point or destination). Upon detecting a transition in transportation mode, the companion device may notify the MIT device of the transition or signal a mode change. In some embodiments, the MIT device may then change its power mode to transmit at a higher rate and / or at a higher transmission power.

[0134] For example, re-referencing Figure 5During transport, the MIT device may be in ultra-low power mode 504 and may transition to high power mode 506 upon notification. In some embodiments, the MIT device may activate a Bluetooth interface and transmit beacons at a higher rate (e.g., approximately every 1 to 10 milliseconds). In some embodiments, if the distance between the MIT device and the companion device increases beyond approximately 1 meter (e.g., 2 to 3 feet), an alert or notification (e.g., visual, audible, and / or tactile) may be output from the companion device. Additionally, the companion device may send instructions to the MIT device to transition from high power mode 506 to a higher power mode, such as ultra-high power mode 508. In some embodiments, the MIT device may activate an ultra-wideband interface to improve the accuracy of location detection. In some embodiments, the MIT device may also deactivate the Bluetooth interface. Additionally, in areas with greater (e.g., higher than average) access medium congestion (interference) (e.g., hazardous areas), the companion device may transmit instructions to supported MIT devices to further increase the location update rate (e.g., in addition to increasing the transmission rate and / or transmission power). In some embodiments, the companion device may increase the scan window length and / or scan window frequency to mitigate increased congestion (and / or interference caused by increased access medium communications). Note that in some embodiments, the companion device may support multiple MIT devices. Therefore, in some embodiments, the companion device may filter out beacons from unsupported MIT devices.

[0135] Figure 10 A block diagram illustrating another example method for power mode switching of a multi-interface transponder (MIT) device based on geographic regions according to some embodiments is shown. Figure 10 The method shown can be used in conjunction with any of the systems or devices shown in the accompanying drawings. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown in the figure, the method can be operated as follows.

[0136] At 1002, a MIT device, such as device 108, may receive an indication of a transport mode transition. The indication may be received from a companion device via a first interface. The companion device may be a UE device, such as client station 106, a wearable device, such as wireless node 107, and / or an access point device, such as AP 112. The first interface may correspond to a first power state. Additionally, the first interface may be an ultra-low power radio frequency interface (e.g., such as a wake-up radio and / or a wake-up receiver). In some embodiments, the transport mode may include or indicate at least one mode of transport, such as a vehicle, a train, a vessel, or an airplane.

[0137] At 1004, in response to the indication, the MIT device may transition to a second power state. In some embodiments, the second power state may be associated with activation of a second interface. The second interface may consume more power than the first interface. In some embodiments, the second interface may be one of a Bluetooth interface or an ultra-wideband interface.

[0138] At 1006, the MIT device may transmit one or more beacons to the companion device via the second interface at a first transmission rate and a first transmission power. In some embodiments, the MIT device may receive an indication from the companion device that the transport mode transition has ended. In response, the MIT device may transition back to the first power state. In some cases, the MIT device may receive an indication from the companion device that the companion device has moved beyond a threshold distance from the MIT device. In response, the MIT device may increase the first transmission rate of the one or more beacons to a second transmission rate. In some embodiments, the threshold distance may be approximately 1 meter (e.g., between 2 feet and 3 feet). In some embodiments, the MIT device may receive an indication from the companion device to increase the transmission power. In some embodiments, the indication may be based at least in part on determining the presence of a high level of congestion (e.g., above average).

[0139] In some embodiments, a companion device, such as wireless station 106 and / or wireless node 107, can use the last location of a multi-interface transponder (MIT) device (such as device 108) to help a user physically find the MIT device, for example, even when the MIT device is not broadcasting to the companion device. For example, the companion device can send one or more signals to wake up the MIT device and determine the location of the MIT device (relative to the companion device) via ultra-wideband communication. Once the location of the MIT device is determined, the MIT device can interrupt transmission (e.g., transition to ultra-low power mode 504). For example, the MIT device's sensors can detect that it has been located, such as through motion. Additionally, as part of finding the MIT, the companion device can display a map view and / or augmented reality (AR) view indicating the location of the MIT device. In some embodiments, when the companion device is moved, the map view / AR view can be updated based on the movement of the companion device. In other words, the location of the MIT device relative to the companion device can be updated based at least in part on the movement of the companion device.

[0140] Figure 11-14 A block diagram illustrating an example of a method of operating MIT according to some embodiments is shown. Figure 11-14The methods shown can be used in conjunction with any of the systems or devices shown in the accompanying drawings. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown in the figures, these methods can be operated as follows.

[0141] Go to Figure 11 At 1102, a MIT device (such as the MIT device 108) having any / all low-power radio interfaces (e.g., wake-up radio components and / or wake-up receivers), medium-power radio interfaces (e.g., Bluetooth (BT) and / or Bluetooth Low Energy (BLE)), and / or high-power radio interfaces (e.g., UWB, 60 GHz)) may be in a low-power operating mode (e.g., operating in a low-power operating mode). In the low-power mode, the MIT device may periodically scan for messages addressed to the MIT device (e.g., beacons, polls, probes, etc.) via the low-power radio interfaces, which may signal the MIT device to activate a higher-power radio interface. Messages may be received from associated devices (e.g., paired devices or devices associated with the same or related user accounts, such as the wireless station 106, wireless node 107, and / or AP 112) or from unassociated devices (e.g., devices associated with different user accounts). In some embodiments, while in the low-power mode, the MIT device may transmit irregularly (e.g., continuously or periodically) to conserve battery power. Furthermore, the scanning window period (e.g., the width of the window) and the interval (e.g., the period between intervals) can be set or dynamically adjustable, for example, in response to one or more factors, such as battery level, congestion / interference, time of day, sensor data, etc. Furthermore, the MIT device can respond to messages uniquely addressed to the MIT device, addressed to a group (or set) including the MIT device, or addressed to all MIT devices. The MIT device can also ignore messages not addressed to the MIT device, such as messages uniquely addressed to a different MIT device or addressed to a group to which the MIT device does not belong.

[0142] At 1104, during the scanning window, a message addressed to the MIT device may be received from the wireless device via the low-power interface. At 1106, in response, the MIT device may activate at least one higher-power interface, such as a BT or BLE interface, and may establish communication with the wireless device, for example, by transmitting a response. At 1108, through the communication, the MIT device may receive updated location information and / or one or more commands, such as a command to activate a high-power interface and / or output one or more signals (e.g., auditory, visual, tactile).

[0143] At 1110, the MIT device may determine whether any remaining operations are to be performed via the medium power interface or the high power interface. If there are no remaining operations to be performed, the MIT device may deactivate all interfaces except the low power interface and may resume monitoring through the scan window.

[0144] Go to Figure 12 At 1202, a MIT device (such as the MIT device 108) having any / all low-power radio interfaces (e.g., wake-up radio components and / or wake-up receivers), medium-power radio interfaces (e.g., Bluetooth (BT) and / or Bluetooth Low Energy (BLE)), and / or high-power radio interfaces (e.g., UWB, 60 GHz)) may be in a low-power operating mode (e.g., operating in a low-power operating mode). In the low-power mode, the MIT device may periodically scan for messages addressed to the MIT device (e.g., beacons, polls, probes, etc.) via the low-power radio interfaces, which may signal the MIT device to activate a higher-power radio interface. Messages may be received from associated devices (e.g., paired devices or devices associated with the same or related user accounts, such as the wireless station 106, wireless node 107, and / or AP 112) or from unassociated devices (e.g., devices associated with different user accounts). In some embodiments, while in the low-power mode, the MIT device may transmit irregularly (e.g., continuously or periodically) to conserve battery power. Furthermore, the scanning window period (e.g., the width of the window) and the interval (e.g., the period between intervals) can be set or dynamically adjustable, for example, in response to one or more factors, such as battery level, congestion / interference, time of day, sensor data, etc. Furthermore, the MIT device can respond to messages uniquely addressed to the MIT device, addressed to a group (or set) including the MIT device, or addressed to all MIT devices. The MIT device can also ignore messages not addressed to the MIT device, such as messages uniquely addressed to a different MIT device or addressed to a group to which the MIT device does not belong.

[0145] At 1204, the MIT device can detect motion via sensor data (e.g., from an accelerometer or gyroscope). In some implementations, at 1206, the MIT device can activate another interface (e.g., BT / BLE) in response to the motion and can periodically output beacons. The periodicity and number of beacons can depend on various factors, including location, type of motion, duration of motion, proximity of associated devices, etc.

[0146] At 1208, the MIT device may determine that the motion has ended and that the MIT device has performed a location update operation with another device (eg, an associated device). The MIT device may then return to low power mode and resume monitoring through the scan window.

[0147] Go to Figure 13 At 1302, a MIT device (such as the MIT device 108) having any / all low-power radio interfaces (e.g., wake-up radio components and / or wake-up receivers), medium-power radio interfaces (e.g., Bluetooth (BT) and / or Bluetooth Low Energy (BLE)), and / or high-power radio interfaces (e.g., UWB, 60 GHz)) may be in a low-power operating mode (e.g., operating in a low-power operating mode). In the low-power mode, the MIT device may periodically scan for messages (e.g., beacons, polls, probes, etc.) addressed to the MIT device via the low-power radio interface, which may signal the MIT device to activate a higher-power radio interface. Messages may be received from associated devices (e.g., paired devices or devices associated with the same or related user accounts, such as the wireless station 106, wireless node 107, and / or AP 112) or from unassociated devices (e.g., devices associated with different user accounts). In some embodiments, while in the low-power mode, the MIT device may transmit irregularly (e.g., continuously or periodically) to conserve battery power. Furthermore, the scanning window period (e.g., the width of the window) and the interval (e.g., the period between intervals) can be set or dynamically adjustable, for example, in response to one or more factors, such as battery level, congestion / interference, time of day, sensor data, etc. Furthermore, the MIT device can respond to messages uniquely addressed to the MIT device, addressed to a group (or set) including the MIT device, or addressed to all MIT devices. The MIT device can also ignore messages not addressed to the MIT device, such as messages uniquely addressed to a different MIT device or addressed to a group to which the MIT device does not belong.

[0148] At 1304, the MIT device may activate at least one higher power interface, for example, based on detected motion and / or messages received during the scan window. At 1306, the MIT device may determine whether its current location corresponds to a safe zone, a risk zone, or some other defined area. A zone (or region) may be any defined or restricted space (e.g., a geofenced area). At 1308, the MIT device may adjust its behavior based on the determined zone. For example, when the MIT device determines that it is located in a safe zone, the MIT device may enter a low power mode and select a scan window setting that will allow the MIT device to enhance power conservation. In some implementations, the MIT device operating settings may be dynamically adjusted to achieve a target operating duration, such as 6 months, 9 months, 12 months, 18 months, 24 months, 36 months, and so forth. For another example, when the MIT device determines that it is in a risk (or dangerous) area, such as in a traffic scenario, the MIT device may select a scan window setting that will allow the MIT device to more quickly identify messages (e.g., a longer, more frequent scan window), and may optionally activate a higher power interface (e.g., BT / BLE) to actively transmit beacons. The risk area MIT device setting may be maintained until the MIT device determines an exit event, such as leaving the risk area, entering a safe area, or determining that it is lost (e.g., after not contacting another device for a threshold period of time and / or being outside a known area).

[0149] At 1310, once a trigger condition is met, the MIT device may return to the low power mode. For example, the MIT device may return to the lower power operating mode after establishing contact with another device, after performing a successful location update operation, after returning to a safe area, when movement stops, after detecting an associated device nearby, etc.

[0150] Go to Figure 14At 1402, a MIT device (such as the MIT device 108) having any / all low-power radio interfaces (e.g., wake-up radio components and / or wake-up receivers), medium-power radio interfaces (e.g., Bluetooth (BT) and / or Bluetooth Low Energy (BLE)), and / or high-power radio interfaces (e.g., UWB, 60 GHz)) may be in a low-power operating mode (e.g., operating in a low-power operating mode). In the low-power mode, the MIT device may periodically scan for messages addressed to the MIT device (e.g., beacons, polls, probes, etc.) via the low-power radio interfaces, which may signal the MIT device to activate a higher-power radio interface. Messages may be received from associated devices (e.g., paired devices or devices associated with the same or related user accounts, such as the wireless station 106, wireless node 107, and / or AP 112) or from unassociated devices (e.g., devices associated with different user accounts). In some embodiments, while in the low-power mode, the MIT device may transmit irregularly (e.g., continuously or periodically) to conserve battery power. Furthermore, the scanning window period (e.g., the width of the window) and the interval (e.g., the period between intervals) can be set or dynamically adjustable, for example, in response to one or more factors, such as battery level, congestion / interference, time of day, sensor data, etc. Furthermore, the MIT device can respond to messages uniquely addressed to the MIT device, addressed to a group (or set) including the MIT device, or addressed to all MIT devices. The MIT device can also ignore messages not addressed to the MIT device, such as messages uniquely addressed to a different MIT device or addressed to a group to which the MIT device does not belong.

[0151] At 1404, the MIT device may activate at least one higher-power interface, for example, based on detected motion and / or messages received during a scanning window. At 1406, the MIT device may determine that it has been lost (e.g., is in a lost condition). For example, the MIT device may determine that it has not been in contact with another device for a threshold duration and / or is outside a known area. At 1408, in response to determining that it is lost, the MIT device may transition to a mode in which at least one higher-power interface is periodically activated (e.g., to adjust behavior based on the lost condition). For example, the MIT device may activate a medium-power interface (e.g., BT / BLE) and may periodically transmit one or more beacons. The beacon period, beacon interval, and number of beacons transmitted may be selected to conserve power, increase the probability of discovery, or both. Furthermore, the transmit power of one or more beacons may be varied. For example, the beacon transmit power may be periodically varied (e.g., -25 dBm, -10 dBm, 0 dBm, +4 dBm) to cover various ranges. Any number of different transmit power values ​​may be used, and the powers shown are exemplary only.

[0152] Additionally, the amount and value of transmission power used, as well as the timing, can vary based on a variety of factors, such as remaining battery power, time of day, amount of light, length of time since last contact with another device, and the like. For example, more aggressive beacon transmissions can be performed while battery power is still sufficiently high (e.g., above 50%, between 50% and 20%, above 10%, and the like). More aggressive beacon transmissions can also be performed at times when the presence of humans is more likely (e.g., based on the MIT device's clock, embedded light sensors, detected RF signals, and the like). Similarly, the MIT device can switch to more conservative beacon transmissions during periods when the presence of humans is less likely, such as when battery power drops below a predetermined level.

[0153] At 1410, once a trigger condition is met, the MIT device may return to the low power mode. For example, the MIT device may return to the lower power operating mode after establishing contact with another device, after performing a successful location update operation, after returning to a safe area, when movement stops, after detecting an associated device nearby, etc.

[0154] Figure 15 An example method of scanning for MIT devices is shown, according to some embodiments. Figure 15 The method shown can be used in conjunction with any of the systems or devices shown in the accompanying drawings. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown in the figure, the method can be operated as follows.

[0155] At 1502, a wireless device (such as wireless station 106, wireless node 107, and / or AP 112) may transmit a message to one or more MIT devices (or tags, transponders, etc., such as MIT device 108). The wireless device may be associated with one or more of the MIT devices. For example, the device may be a companion device (e.g., a phone or mobile computing device) associated with a user account that is also associated with one or more MIT devices (a public user account), or previously paired with a MIT device. The wireless device may address the message to a specific MIT device (e.g., associated with an object to be located), a group of MIT devices (e.g., of a common type or connected by association), or generally to all MIT devices. In addition, the message may be transmitted using an interface that can be accommodated by a low-power interface (e.g., a wake-up radio component and / or a wake-up receiver) of the MIT device.

[0156] At 1504, the wireless device may establish communication with a particular MIT device from among the one or more MIT devices via a medium-power interface. Note that in some embodiments, upon receiving the message, the MIT device may activate a medium-power (and range) interface, such as a Bluetooth (BT) interface or a BT Low Energy (BLE) interface. In some cases, the wireless device may utilize communication via the medium-power interface to locate the MIT device. For example, the wireless device may instruct the MIT device to output one or more signals, such as an auditory signal, a visual signal (e.g., light), and / or a tactile signal. Additionally or alternatively, the wireless device and the MIT device may utilize signal information (e.g., signal strength measurement (RSSI)) to perform location operations. In other cases, the wireless device may instruct the MIT device to activate a high-power interface (e.g., a UWB interface) to provide more accurate location information (e.g., compared to other methods of determining the location of the MIT device). In some embodiments, the wireless device and the MIT device may utilize a single interface or multiple interfaces for location operations.

[0157] At 1506, the wireless device may present a positioning interface, for example, on a display. The positioning interface may be a real-time image (e.g., a camera feed) or a rendering (e.g., a map, a blank screen, etc.), and may also include one or more location indicators corresponding to the location of the MIT device. For example, one or more arrows, dots, circles, or other such indicators. In addition, the one or more location indicators may vary in size, color, shape, and / or intensity, for example, to provide more information about the location of the MIT device. In some embodiments, the wireless device may present the positioning interface only when the high-power interface is active.

[0158] At 1508, once the location of the MIT device is determined (e.g., via the high-power interface), the wireless device may send one or more messages instructing the MIT device to deactivate the high-power interface, e.g., to reduce battery consumption. Additionally, the wireless device may instruct the MIT device to deactivate one or more other interfaces and / or terminate one or more (e.g., auditory, visual, tactile) outputs. Furthermore, the instructions may instruct the MIT device to return to a lower power operating mode, e.g., periodically scanning for a wake-up signal via the low-power interface (e.g., waking up the radio and / or waking up the receiver).

[0159] Implementation plan for using MIT equipment

[0160] In some embodiments, a multi-interface transponder (MIT) device, such as MIT device 108, can be used as a monetary device, e.g., for money transfers and / or as a payment device. For example, a MIT device can be used to transfer funds, acting as a stored-value or cash card, such as a prepaid transit card, gift card, or other such card implementation. For example, in addition to communication circuitry, one or more sensors, a processor, memory, a power supply, etc., a MIT device can include a secure processor and / or secure storage. In such embodiments, the MIT device can operate in a standalone mode (or as a standalone device), e.g., without a companion device. In some embodiments, the MIT device can be associated with an account (e.g., a bank account, such as a credit card, debit card, checking, and / or savings account) or a money pool (e.g., a pre-funded account hosted by a service but not directly linked to a bank account). In some embodiments, the MIT device can be enabled to perform a "tap to pay" operation using an ultra-wideband interface, thereby allowing for a high level of transaction security. In some embodiments, the MIT device can be implemented as a lending device, e.g., enabling it to lend money via a third-party service (such as Venmo, PayPal, Apple Pay, etc.).

[0161] As another example, an MIT device can be attached to (or associated with) items to be shared among a group of users, such as neighbors in a neighborhood and / or members of a social group. In some embodiments, the MIT device can assist in tracking items (e.g., last user, last and / or current location) and maintaining information associated with the items (e.g., user, location, usage, etc.). Similarly, the MIT device can be implemented for inventory tracking of companies, sports teams, communities, etc. (e.g., attached / associated with items that are typically assigned to or shared with users).

[0162] In some embodiments, a multi-interface transponder (MIT) device, such as MIT device 108, can be used as a form of identification, for example, for authenticating visitors. For example, in some embodiments, a MIT device can become a digital representation of a person's identity. In some embodiments, the MIT device can store authentication information, such as a token, in secure storage. Furthermore, the authentication information can be encrypted in a manner that allows for secure decryption and authentication. The representation can include a description, image, current location, and / or expected location of the person. In some embodiments, a user can scan for the MIT device and determine its location and the person's identity. For example, upon scanning for the MIT device (e.g., via a wireless device, such as AP 112, wireless station 106, and / or wireless node 107), the user can be provided with information confirming the person's identity, such as a photograph identifying the person, a sign indicating the person's expected location, and the like. In some embodiments, the scan can be implemented by a home security system, for example, to confirm identity and / or authorize entry, or conversely, to deny entry and notify security. For another example, a MIT device can be implemented as part of a chain of trust, for example, to allow in-store pickup of online orders, signature verification of received shipments, and the like.

[0163] Other implementation plans

[0164] In some embodiments, for example, as described herein, a multi-interface transponder device (MIT) may include one or more radio components (e.g., to support interfaces), at least one antenna, memory, and one or more processors (e.g., processing circuitry, processing elements, etc.). In some embodiments, the one or more radio components may include one or more of a Bluetooth (BT) radio component (e.g., any radio component supporting various forms of Bluetooth, including Bluetooth low energy), an ultra-wideband (UWB) radio component, and / or an ultra-low power radio component (e.g., such as a wake-up radio component and / or a wake-up receiver). Additionally, in some embodiments, the MIT device may include motion sensing circuitry (e.g., a gyroscope, an accelerometer, and / or any of various other motion sensing components).

[0165] In some embodiments, a MIT device may be configured to:

[0166] entering a low power mode disabling the second radio;

[0167] While in the low power mode, receiving a wake-up signal from a neighboring wireless device; and

[0168] After transitioning to a higher power mode in response to receiving the wake-up signal, a beacon is transmitted via the second radio component, wherein the second radio component is enabled in the higher power mode. In some embodiments, the wake-up signal can be received by an ultra-low power radio component, for example, via ULP / LP communication with the neighboring wireless device.

[0169] In some embodiments, the neighboring wireless device may include a companion device. In some embodiments, the companion device may have helped the MIT device register with the location server. In some embodiments, the companion device and the MIT device may be associated with the location server. In some embodiments, the MIT may be configured to:

[0170] receiving an indication from the neighboring wireless device that a location associated with the MIT device has been updated at the location server; and

[0171] Transitioning to the low power mode is based at least in part on the indication.

[0172] In some embodiments, the wake-up signal may indicate a transmission rate. In some embodiments, the transmission rate may be based at least in part on one or more of a traffic pattern detected by a neighboring wireless device and / or expected medium congestion detected by the neighboring wireless device. In some embodiments, the wake-up signal may indicate a transmission power. In some embodiments, the transmission power may be based at least in part on one or more of a traffic pattern detected by a neighboring wireless device and / or expected medium congestion detected by the neighboring wireless device.

[0173] In some embodiments, the second radio may include an ultra-wideband radio.

[0174] In some embodiments, the neighboring wireless devices may include non-companion devices. In some embodiments, the non-companion devices and the MIT devices may be associated with a location server.

[0175] In some embodiments, the wake-up signal may be received via a first radio component. In some embodiments, the first radio component may include one of a Bluetooth radio component and / or an ultra-low power radio component (e.g., such as a wake-up radio component and / or a wake-up receiver).

[0176] In some embodiments, the MIT device may be further configured to determine a first condition of the MIT device based at least in part on a duration since communicating with the companion device, and to transition to a lost mode of operation based on the first condition. In some embodiments, the companion device may have facilitated registration of the MIT device with a location server. In some embodiments, the companion device and the MIT device may be associated with a location server. In some embodiments, while in the lost mode of operation, the MIT device may be configured to transmit beacons via the first radio at a first periodic interval during a first portion of a day, and to transmit beacons via the first radio at a second periodic interval during a second portion of a day. In some embodiments, the first portion of a day may correspond at least in part to daytime hours, and the second portion of a day may correspond at least in part to non-daytime hours. In some embodiments, the second periodic interval may be longer than the first periodic interval. In some embodiments, the MIT device may be configured to increase the transmission power of beacons transmitted via the first radio based at least in part on one of the duration or the time of day. In some embodiments, the first radio may include a Bluetooth radio. In some embodiments, the first condition of the MIT device may be further based at least in part on a duration since a location update indication or a signal was received from a neighboring wireless device.

[0177] In some embodiments, a MIT device may be configured to:

[0178] operating in a low power mode, wherein in the low power mode an ultra-wideband (UWB) radio in communication with the at least one processor is disabled;

[0179] while operating in the low power mode, receiving a wake-up signal from a neighboring wireless device;

[0180] generating instructions to transition out of the low power mode and enable the UWB radio in response to receiving the wake-up signal; and

[0181] Instructions are generated to transmit a location beacon to the neighboring wireless device via the UWB radio.In some embodiments, the wake-up signal may be received by an ultra low power radio, such as via ULP / LP communication with the neighboring wireless device.

[0182] In some implementations, the wake-up signal may be received via one of a Bluetooth radio or an ultra-low power radio (eg, such as a wake-up radio and / or a wake-up receiver) in communication with the at least one processor.

[0183] In some embodiments, the wake-up signal may indicate the transmission rate and transmission power of the location beacon.

[0184] In some embodiments, the MIT device may be further configured to:

[0185] receiving an indication from a neighboring wireless device that a location associated with the MIT device has been updated at a location server; and

[0186] Instructions are generated to transition to the low power mode and disable the UWB radio.

[0187] In some embodiments, the wake-up signal may indicate a transmission rate and a transmission power of the location beacon. In some embodiments, each of the transmission rate and the transmission power may be based at least in part on one or more of traffic patterns detected by neighboring wireless devices and / or expected medium congestion detected by neighboring wireless devices.

[0188] In some embodiments, a MIT device may be configured to:

[0189] broadcasting a location beacon at a first transmission rate and a first transmission power;

[0190] In response to detecting a trigger condition, increasing the first transmission rate to a second transmission rate;

[0191] as well as

[0192] The location beacon is broadcast at a second transmission rate and a first transmission power.

[0193] In some embodiments, the triggering condition may include receiving an indication that the companion device has been moved beyond a threshold distance from the MIT device. In some embodiments, the indication may be received via the first radio component, and a location beacon may be transmitted via the second radio component. In some embodiments, the threshold distance may be approximately 1 meter.

[0194] In some embodiments, a MIT device may be configured to:

[0195] receiving an indication from the companion device to increase the transmission power to a second transmission power, wherein the indication is based at least in part on medium congestion; and

[0196] The location beacon is transmitted to the companion device at a second transmission power.

[0197] In some embodiments, prior to broadcasting a location beacon at a first transmission rate and a first transmission power, the MIT device may be configured to:

[0198] while operating in the low power mode, receiving an indication of a transport mode transition from the companion device, wherein the second radio is disabled in the low power mode; and

[0199] A transition is made to a higher power mode based on the indication, wherein the second radio is enabled in the higher power mode.

[0200] In some embodiments, a MIT device may be configured to:

[0201] receiving an indication from the companion device that the transport mode transition is complete; and

[0202] Transitioning back to the low power state is performed in response to the indication.

[0203] In some embodiments, the triggering condition may include detecting a transition in transport mode. The transition may include stopping the transport mode. In some embodiments, the determination may be based on a change in the speed of the MIT device.

[0204] In some embodiments, a MIT device may be configured to:

[0205] while in the first power state, determining to transition to a second power state based at least in part on detecting an event detectable via one of a first interface (e.g., supported by a first radio of the one or more radios) of the MIT device and / or a motion sensing circuit;

[0206] transitioning from a first power state to a second power state;

[0207] while in the second power state, transmitting one or more beacons via one of a second interface (e.g., supported by a second radio of the one or more radios) or a third interface (e.g., supported by a third radio of the one or more radios) of the MIT device;

[0208] receiving, while in the second power state, from a neighboring wireless device, an indication that a location associated with the MIT device has been updated at a location server; and

[0209] A determination is made to transition to a third power state based at least in part on the indication.

[0210] In some embodiments, selection of the second interface or the third interface may be based at least in part on the detected event.In some embodiments, the neighboring wireless device and the MIT device may both be associated with a location server.

[0211] In some embodiments, the first interface may be an ultra-low power radio frequency (RF) interface (e.g., such as a wake-up radio and / or a wake-up receiver). In other words, in some embodiments, the first radio may be an ultra-low power radio. In some embodiments, the first interface may be a Bluetooth (BT) interface. Thus, in such embodiments, the first radio may be a Bluetooth radio.

[0212] In some embodiments, the second interface may be one of a Bluetooth interface and an ultra-wideband (UWB) radio frequency (RF) interface, and the third interface may be one of a Bluetooth (BT) interface and a UWB RF interface. In other words, in some embodiments, the second radio component and the third radio component may be one of a BT radio component and / or a UWB radio component.

[0213] In some embodiments, the event detectable via the first interface may include receiving a wake-up signal from the companion device. In some embodiments, the wake-up signal may include instructions for transitioning to the second power state. In some embodiments, the instructions may instruct the MIT device to activate the third interface, for example, when the third interface includes a UWB RF interface. In some embodiments, the instructions may instruct the MIT device to activate the second interface, for example, when the second interface includes a BT interface.

[0214] In some embodiments, the instruction may indicate a transmission rate. In some embodiments, the transmission rate may be based at least in part on a traffic pattern detected by the companion device. In some embodiments, the transmission rate may be based at least in part on expected medium congestion detected by the companion device.

[0215] In some embodiments, the instruction may indicate a transmission power. In some embodiments, the transmission power may be based at least in part on a traffic pattern detected by the companion device. In some embodiments, the transmission power may be based at least in part on (and / or further based on) expected medium congestion detected by the companion device.

[0216] In some embodiments, the neighboring wireless device may be a companion device that may have assisted the MIT device in registering with the location server.In some embodiments, the neighboring wireless device may be a non-companion device that may be associated with the location server.

[0217] In some embodiments, a MIT device may be configured to:

[0218] determining a first condition of the MIT device based at least in part on a duration of time since communicating with the companion device; and

[0219] Transitioning to a first operating mode is performed based on a first condition.

[0220] In some embodiments, the first mode of operation may include any, any combination, and / or all of the following: transmitting a beacon via the first interface at a first periodic interval during a first portion of the day, transmitting a beacon via the first interface at a second periodic interval during a second portion of the day, and / or increasing the transmission power of the beacon based at least in part on one of a duration and / or a time of day. In some embodiments, the first portion of the day may correspond at least in part to daytime hours. In some embodiments, the second portion of the day may correspond at least in part to non-daytime hours. In some embodiments, the second periodic interval may be longer than the first periodic interval.

[0221] In some embodiments, the first condition of the MIT device may be further based at least in part on a duration since a location update indication and / or a signal was received from a neighboring device.

[0222] In some implementations, the first periodic interval may be adjusted based at least in part on the transmission power.

[0223] In some embodiments, the MIT device may be further configured to:

[0224] receiving signals from neighboring wireless devices; and

[0225] The transmission frequency and / or transmission power is increased in response to receiving the signal.

[0226] In some embodiments, the first operating mode may further include a power saving period. In some embodiments, the power saving period may be at least 10 times longer than the first or second portion of the day. In some embodiments, the power saving period may be at least 100 times longer than the first or second portion of the day. In some embodiments, the power saving period may be at least 1000 times longer than the first or second portion of the day.

[0227] In some embodiments, the first interface may be a Bluetooth interface.

[0228] In some embodiments, a MIT device may be configured to:

[0229] receiving an indication of a transport mode transition from a companion device via the first interface and while in the first power state;

[0230] transitioning to a second low power state in response to the indication; and

[0231] One or more beacons are transmitted to the companion device via the second interface at a first transmission rate and a first transmission power.

[0232] In some embodiments, transitioning to the second power state can activate the second interface. In some embodiments, the second interface can consume more power than the first interface.

[0233] In some embodiments, the first interface may be an ultra-low power wake-up radio frequency interface. In some embodiments, the second interface may be one of a Bluetooth interface or an ultra-wideband RF interface.

[0234] In some embodiments, the MIT device may be further configured to:

[0235] receiving an indication from the companion device that the transport mode transition is complete; and

[0236] Transitioning back to the first power state is performed in response to the indication.

[0237] In some embodiments, the MIT device may be further configured to:

[0238] receiving an indication from the companion device that the companion device has moved beyond a threshold distance from the MIT device; and

[0239] A transmission rate of the one or more beacons is increased in response to the indication.

[0240] In some embodiments, the threshold distance may be approximately 1 meter. In some embodiments, the threshold distance may be greater than 2 feet but less than 3 feet.

[0241] In some embodiments, the MIT device may be further configured to receive an indication from the companion device to increase transmission power, wherein the indication is based at least in part on medium congestion.

[0242] In some implementations, the companion device may be at least one of a user equipment device or a wearable device.

[0243] In some embodiments, the mode of transportation may include at least one of a vehicle, a train, a boat, or an airplane.

[0244] In some embodiments, for example, a wireless device as described herein (such as a client station and / or wireless node) may be configured as a companion device to a multi-interface transponder (MIT) device as described herein. The wireless device may include one or more radio components (e.g., to support one or more interfaces), at least one antenna, a memory, and one or more processors (e.g., processing circuitry, processing elements, etc.). In some embodiments, the one or more radio components may include one or more of a Bluetooth (BT) radio component (e.g., any radio component supporting various forms of Bluetooth, including Bluetooth low energy), an ultra-wideband (UWB) radio component, an ultra-low power radio component (e.g., such as a wake-up radio component and / or a wake-up receiver), and / or a cellular radio component. Additionally, in some embodiments, the wireless device may include motion sensing circuitry (e.g., a gyroscope, an accelerometer, and / or any of various other motion sensing components).

[0245] In some embodiments, the wireless device may be configured to:

[0246] Transmitting an instruction to activate the ultra-wideband interface to the MIT device;

[0247] receiving one or more signals from a MIT device via ultra-wideband communication;

[0248] determining a location of the MIT device relative to the wireless device based on the received one or more signals;

[0249] displaying, via the user interface, an indication of the location of the MIT device relative to the wireless device; and

[0250] The position of the MIT device relative to the wireless device is updated based on the movement of the wireless device.

[0251] In some embodiments, the instructions may be transmitted via an ultra-low power radio frequency signal.

[0252] In some embodiments, the indication may be displayed via a map displayed on a display of the wireless device.

[0253] In some embodiments, the indication may include rendering an augmented reality of the location of the MIT device relative to the wireless device.

[0254] In some embodiments, the wireless device may be further configured to transmit an instruction to the MIT device in response to determining the location of the MIT device to deactivate the ultra-wideband interface of the MIT device. In some embodiments, the wireless device may be further configured to transmit a location update message to a location server in response to determining the location of the MIT device.

[0255] As described above, one aspect of the present technology is to collect and use data obtained from specific and legitimate sources to track and / or update the location of a multi-interface transponder (MIT) device. The present disclosure contemplates that, in some instances, the collected data may include personal information data that uniquely identifies or can be used to identify a specific person. Such personal information data may include demographic data, location-based data, online identifiers, phone numbers, email addresses, home addresses, data or records related to a user's health or fitness level (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other personal information.

[0256] The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit users. For example, tracking and / or updating the location of MIT devices can help users keep track of various important items (such as keys, luggage, music equipment, sports equipment, backpacks, briefcases, etc.).

[0257] This disclosure contemplates that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information will adhere to established privacy policies and / or practices. Specifically, such entities are expected to implement and consistently apply privacy practices generally recognized as meeting or exceeding industry or government requirements for safeguarding user privacy. Such information regarding the use of personal data should be prominently displayed and easily accessible to users and updated as the collection and / or use of data changes. Users' personal information should be collected only for lawful uses. Furthermore, such collection / sharing should occur only after receiving user consent or other lawful basis as provided in applicable law. Furthermore, such entities should consider taking any necessary steps to safeguard and secure access to such personal information and ensure that others with access to such personal information adhere to their privacy policies and procedures. Furthermore, such entities may subject themselves to third-party assessments to demonstrate compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be tailored to the specific types of personal information being collected and / or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations that may impose higher standards. For example, in the United States, the collection or access 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.

[0258] Regardless of the foregoing, the present disclosure also contemplates implementations in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates providing hardware components and / or software components to prevent or block access to such personal information data.

[0259] Furthermore, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use. Risk can be minimized by limiting data collection and deleting data once it is no longer needed. 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 where appropriate by removing identifiers, controlling the amount or specificity of stored data (e.g., collecting location data at a city level rather than an address level), controlling how data is stored (e.g., aggregating data across users), and / or other methods such as differential privacy.

[0260] 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 various embodiments may be implemented without access to such personal information data. That is, various embodiments of the present technology will not be unable to function properly due to the lack of all or part of such personal information data. For example, content may be selected and delivered to users based on aggregated non-personal information data or an absolute minimum amount of personal information, such as content processed only on the user's device or other non-personal information that may be used for content delivery services.

[0261] The 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.

[0262] In some embodiments, a non-transitory computer-readable storage medium may be configured such that it stores program instructions and / or data, wherein the program instructions, if executed by a computer system, cause the computer system 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.

[0263] In some embodiments, a wireless device 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 cause the wireless device to implement any of the various method implementations described herein (or any combination of the method implementations described herein, or any subset of any of the method implementations described herein, or any combination of such subsets). The device may be implemented in any of various forms.

[0264] 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 method for operating a multi-interface transponder (MIT) device, comprising: The MIT device, setting a scan window period and interval based on one or more factors, wherein the MIT device listens via a first radio component for messages addressed to the MIT device or to a group of devices including the MIT device during a scan window based on the scan window period and interval; receiving, via the first radio component supporting at least a first radio access technology (RAT) and operating in a low power mode, an indication from a second device; transitioning to a higher power mode based on the indication, wherein a second radio supporting at least a second RAT is enabled; and One or more beacons are transmitted via the second RAT via the second radio component, wherein the one or more beacons include location data associated with the MIT device.

2. The method according to claim 1, The second radio component does not communicate in the low power mode.

3. The method according to claim 1, The second device is a companion device.

4. The method according to claim 3, Wherein the indication indicates that the companion device has moved beyond a threshold distance from the MIT device.

5. The method according to claim 4, The threshold distance is approximately 1 meter.

6. The method according to claim 1, further comprising: The MIT device, receiving an instruction from the second device to increase the transmission power to a second transmission power; as well as A location beacon is transmitted to the second device at the second transmission power.

7. The method according to claim 6, Wherein the indication is based at least in part on medium congestion.

8. The method according to claim 1, The indication indicates the start of a transport mode switch.

9. The method according to claim 8, further comprising: The MIT device, receiving an indication from the second device that the transport mode transition is complete; as well as Transitioning back to the low power mode is performed in response to the indication.

10. The method according to claim 1, further comprising: The MIT device, In response to receipt of the indication, identification data is provided to the second device.

11. The method according to claim 10, Wherein the identification data is stored in a secure portion of a memory of the MIT device.

12. The method according to claim 1, Wherein the first radio component is at least one of an ultra low power radio component, a low power radio component or a Bluetooth radio component.

13. The method according to claim 1, The second radio component includes at least one of a Bluetooth radio component, a wideband radio component, or an ultra-wideband radio component.

14. The method according to claim 1, Wherein the first radio component is deactivated in the higher power mode.

15. The method according to claim 1, Wherein the first radio component operates at a lower power than the second radio component.

16. The method according to claim 1, Wherein the second radio component operates at a higher power than the first radio component.

17. A multi-interface transponder (MIT) device, comprising: a first radio component comprising circuitry supporting at least a first radio access technology (RAT); a second radio comprising circuitry supporting at least a second RAT; as well as one or more processors coupled to the first radio and the second radio; and The one or more processors are configured to cause the MIT device to perform the method according to any one of claims 1 to 16.

18. An apparatus comprising: Memory; as well as at least one processor in communication with the memory; Wherein the at least one processor is configured to perform the method according to any one of claims 1 to 16.

19. A non-transitory computer-readable memory medium storing program instructions, the program instructions being executable by a processing circuit of a multi-interface transponder (MIT) device to perform the method according to any one of claims 1 to 16.

Images