Scanning of beacon transmissions from devices with wireless energy charging capabilities

Abstract

Techniques for asset tracking are disclosed. In an aspect, an asset tracking coordination component estimates a time of beacon transmission from a wireless energy charging capable device coupled to an asset within a threshold proximity of a scanning device based on an estimated distance between the asset tracking coordination device and the scanning device and timing information associated with the wireless energy transmission, and schedule a beacon scan window for the scanning device to scan the beacon transmission based on the estimated time. In further aspects, a scanning device may not only provide wireless energy transmissions but also scan beacon transmissions from a device with wireless energy charging capability during a beacon scan window.

Description

Background Art 1. Technical Field

[0002] Aspects of the present disclosure relate generally to wireless communications.

[0003] 2. Description of related technologies

[0004] Inventory (or asset) tracking systems can be used to track assets at various stages of distribution. For example, asset tracking systems can be deployed in warehouses, retail store spaces, etc. For example, pallets including cases and boxes can be assembled at a distribution center and then dispatched to a specific retail store. Once at the retail store, the pallets are broken down into cases and boxes, which can be immediately moved to the store floor for horizontal placement of items on shelves or restocking. Cases and boxes can also be stored in a back room for later dispatch.

[0005] Real-time tracking of asset locations (e.g., from a pallet at a distribution center to a pallet at a retail store to a shelf at a retail store, etc.) is difficult in current asset tracking systems. Specifically, the ability of retailers to accurately (or with a given degree of accuracy, such as knowledge of the count or amount of assets, etc.) determine the inventory currently available to physical customers ("brick and mortar" stores) is an elusive goal. Providing this information to retailers can be very valuable. For example, real-time tracking of asset counts can help facilitate dynamic, on-demand or periodic updates of inventory to improve logistics, develop additional revenue streams, reduce waste and improve "just-in-time" methods, resulting in the avoidance of empty shelves and unnecessary consumption of real estate in back-room storage.

[0006] In addition to quantitative information about which products are in the store, knowledge of asset placement throughout the space and the accuracy of the intended deployment (the proposed planogram) versus reality (the actual planogram) is also important and valuable information to supply to any retailer. For example, identifying items that are “displaced” by the store (e.g., a customer picks up items and moves them from a basket to somewhere else in the store) allows retailers to recover and reorganize. Summary of the invention

[0007] The following presents a simplified summary of the invention related to one or more aspects disclosed herein. Therefore, the following summary of the invention should neither be considered as an exhaustive overview related to all conceived aspects, nor should it be considered to identify key or decisive elements related to all conceived aspects or to delineate the scope associated with any particular aspect. Therefore, the sole purpose of the following summary of the invention is to present certain concepts related to one or more aspects of the mechanisms disclosed herein in a brief form before the detailed embodiments presented below.

[0008] In one aspect, a method of operating an asset tracking coordination component includes: estimating a distance between a wireless energy source and a scanning device; determining timing information associated with a wireless energy transmission from the wireless energy source; estimating a time of a beacon transmission from a device with wireless energy charging capability coupled to an asset within a threshold proximity of the scanning device based on the estimated distance and the timing information; and scheduling a beacon scan window for the scanning device to scan for the beacon transmission based on the estimated time.

[0009] In one aspect, a method of operating a scanning device includes: receiving a request from an asset tracking coordination component to perform an asset scan in conjunction with wireless energy transmissions from the scanning device; performing the wireless energy transmissions in response to the request; monitoring one or more beacon transmissions from one or more wireless energy charging-capable devices of one or more assets coupled to the scanning device within a threshold proximity in response to the request during a beacon scanning window based on the wireless energy transmissions; and sending scan result information to the asset tracking coordination component based on the monitoring.

[0010] In one aspect, a method of operating an asset tracking coordination component includes: sending a request to a scanning device to perform an asset scan in conjunction with wireless energy transmissions from the scanning device, the asset scan including monitoring one or more beacon transmissions from one or more wireless energy charging-capable devices of one or more assets within a threshold proximity coupled to a wireless energy source during a beacon scan window based on the wireless energy transmissions; and receiving scan result information from the wireless energy source based on the monitoring.

[0011] In one aspect, an asset tracking coordination component includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: estimate a distance between a wireless energy source and a scanning device; determine timing information associated with a wireless energy transmission from the wireless energy source; estimate a time of a beacon transmission from a device with wireless energy charging capability of an asset within a threshold proximity coupled to the scanning device based on the estimated distance and the timing information; and schedule a beacon scan window for the scanning device to scan for the beacon transmission based on the estimated time.

[0012] In one aspect, a scanning device includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive a request from an asset tracking coordination component via the at least one transceiver to perform an asset scan in conjunction with wireless energy transmissions from the scanning device; perform the wireless energy transmissions in response to the request; monitor one or more beacon transmissions from one or more devices with wireless energy charging capabilities of one or more assets within a threshold proximity coupled to the scanning device in response to the request during a beacon scanning window based on the wireless energy transmissions; and send scan result information to the asset tracking coordination component based on the monitoring via the at least one transceiver.

[0013] In one aspect, an asset tracking coordination component includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: send a request to a scanning device via the at least one transceiver to perform an asset scan in conjunction with wireless energy transmissions from the scanning device, the asset scan comprising monitoring one or more beacon transmissions from one or more devices with wireless energy charging capabilities of one or more assets within a threshold proximity coupled to a wireless energy source during a beacon scanning window based on the wireless energy transmissions; and receive scan result information from the wireless energy source based on the monitoring via the at least one transceiver.

[0014] In one aspect, an asset tracking coordination component includes: a component for estimating a distance between a wireless energy source and a scanning device; a component for determining timing information associated with wireless energy transmissions from the wireless energy source; a component for estimating a time of a beacon transmission from a device with wireless energy charging capabilities coupled to an asset within a threshold proximity of the scanning device based on the estimated distance and the timing information; and a component for scheduling a beacon scan window for the scanning device to scan for the beacon transmission based on the estimated time.

[0015] In one aspect, a scanning device includes: a component for receiving a request from an asset tracking coordination component to perform an asset scan in conjunction with a wireless energy transmission from the scanning device; a component for performing the wireless energy transmission in response to the request; a component for monitoring one or more beacon transmissions from one or more devices with wireless energy charging capabilities of one or more assets coupled to the scanning device within a threshold proximity in response to the request during a beacon scanning window based on the wireless energy transmission; and a component for sending scan result information to the asset tracking coordination component based on the monitoring.

[0016] In one aspect, an asset tracking coordination component includes: a component for sending a request to a scanning device to perform an asset scan in conjunction with a wireless energy transmission from the scanning device, the asset scan including monitoring one or more beacon transmissions from one or more wireless energy charging capable devices of one or more assets within a threshold proximity coupled to a wireless energy source during a beacon scan window based on the wireless energy transmission; and a component for receiving scan result information from the wireless energy source based on the monitoring.

[0017] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by an asset tracking coordination component, cause the asset tracking coordination component to: estimate a distance between a wireless energy source and a scanning device; determine timing information associated with a wireless energy transmission from the wireless energy source; estimate a time of a beacon transmission from a device with wireless energy charging capability coupled to an asset within a threshold proximity of the scanning device based on the estimated distance and the timing information; and schedule a beacon scan window for the scanning device to scan for the beacon transmission based on the estimated time.

[0018] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a scanning device, cause the scanning device to: receive a request from an asset tracking coordination component to perform an asset scan in conjunction with wireless energy transmissions from the scanning device; perform the wireless energy transmissions in response to the request; monitor for one or more beacon transmissions from one or more wireless energy charging-capable devices of one or more assets coupled to the scanning device within a threshold proximity in response to the request during a beacon scanning window based on the wireless energy transmissions; and send scan result information to the asset tracking coordination component based on the monitoring.

[0019] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by an asset tracking coordination component, cause the asset tracking coordination component to: send a request to a scanning device to perform an asset scan in conjunction with wireless energy transmissions from the scanning device, the asset scan comprising monitoring one or more beacon transmissions from one or more wireless energy charging-capable devices of one or more assets within a threshold proximity coupled to a wireless energy source during a beacon scan window based on the wireless energy transmissions; and receive scan result information from the wireless energy source based on the monitoring.

[0020] Other objects and advantages associated with the various aspects disclosed herein will be apparent to those skilled in the art based on the drawings and detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The accompanying drawings are presented to aid in describing various aspects of the present disclosure and are provided solely for illustration and not limitation of the various aspects.

[0022] FIG. 1 illustrates an example wireless communication system in accordance with aspects of the present disclosure.

[0023] 2A , 2B and 2C illustrate example wireless network structures according to aspects of the present disclosure.

[0024] 3A , 3B and 3C are simplified block diagrams of several sample aspects of components that may be employed in a user equipment (UE), a base station and a network entity, respectively, and configured to support communications as taught herein.

[0025] FIG. 4 illustrates a device having wireless energy charging capabilities according to an aspect of the present disclosure.

[0026] FIG5 illustrates an in-store portion of an electronic tag system according to aspects of the present disclosure.

[0027] FIG6 illustrates an electronic shelf label (ESL) system infrastructure in accordance with aspects of the present disclosure.

[0028] FIG. 7 illustrates an exemplary process according to aspects of the present disclosure.

[0029] FIG. 8 illustrates an example ESL system infrastructure based on the process of FIG. 7 , according to aspects of the present disclosure.

[0030] FIG. 9 illustrates an example implementation of the process of FIG. 7 in accordance with aspects of the present disclosure.

[0031] FIG. 10 illustrates an exemplary process according to aspects of the present disclosure.

[0032] FIG. 11 illustrates an exemplary process according to aspects of the present disclosure.

[0033] 12 illustrates an example ESL system infrastructure based on the processes of FIGS. 10-11 , respectively, according to aspects of the present disclosure. DETAILED DESCRIPTION

[0034] Various aspects of the present disclosure are provided in the following description and related drawings for various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of the present disclosure. In addition, well-known elements of the present disclosure will not be described in detail or will be omitted to avoid making the relevant details of the present disclosure difficult to understand.

[0035] The words "exemplary" and / or "example" are used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" and / or "example" is not necessarily to be construed as preferred or advantageous over other aspects. Likewise, the term "aspects of the disclosure" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation.

[0036] Those skilled in the art will appreciate that any of a variety of different techniques and methods may be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the following description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof, which depends in part on the specific application, in part on the desired design, in part on the corresponding technology, and so on.

[0037] In addition, many aspects are described in terms of a sequence of actions to be performed by, for example, elements of a computing device. It will be appreciated that the various actions described herein may be performed by a specific circuit (e.g., an application specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of the two. In addition, the sequence of actions described herein may be considered to be fully embodied in any form of non-transitory computer-readable storage medium, in which a corresponding computer instruction set is stored, which, when executed, will cause or command the associated processor of the device to perform the functions described herein. Therefore, various aspects of the present disclosure may be embodied in a variety of different forms, all of which have been contemplated to be within the scope of the claimed subject matter. In addition, for each of the various aspects described herein, the corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions."

[0038] As used herein, unless otherwise specified, the terms "user equipment" (UE) and "base station" are not intended to be specific or otherwise limited to any specific radio access technology (RAT). In general, a UE may be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a consumer asset location device, a wearable device (e.g., a smart watch, glasses, an augmented reality (AR) / virtual reality (VR) head-mounted device, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. A UE may be mobile or (e.g., at certain times) may be stationary and may communicate with a radio access network (RAN). As used herein, the term "UE" may be interchangeably referred to as an "access terminal" or "AT", "client device", "wireless device", "subscriber equipment", "subscriber terminal", "subscriber station", "user terminal" or "UT", "mobile device", "mobile terminal", "mobile station" or variations thereof. In general, a UE may communicate with a core network via a RAN, and through the core network, the UE may connect to external networks such as the Internet and to other UEs. Of course, other mechanisms are also possible for the UE to connect to the core network and / or the Internet, such as through a wired access network, a wireless local area network (WLAN) network (eg, based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.), etc.

[0039] A base station may operate according to one of several RATs to communicate with a UE, depending on the network in which the base station is deployed, and may alternatively be referred to as an access point (AP), a network node, a Node B, an evolved Node B (eNB), a next generation eNB (ng-eNB), a new radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be primarily used to support wireless access for UEs, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, a base station may only provide edge node signaling functions, while in other systems, it may provide additional control and / or network management functions. The communication link by which a UE may transmit a signal to a base station is referred to as an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). The communication link by which a base station may transmit a signal to a UE is referred to as a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term "traffic channel (TCH)" may refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0040] The term "base station" may refer to a single physical transmit-receive point (TRP) or multiple physical TRPs that may or may not be co-located. For example, where the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term "base station" refers to multiple co-located physical TRPs, the physical TRP may be an antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRP may be a serving base station that receives measurement reports from a UE and a neighboring base station whose reference radio frequency (RF) signal the UE is measuring. Because, as used herein, a TRP is a point by which a base station transmits and receives wireless signals, references to transmitting from a base station or receiving at a base station should be understood to refer to a specific TRP of a base station.

[0041] In some implementations of supporting UE positioning, a base station may not support wireless access by the UE (e.g., may not support data, voice, and / or signaling connections for the UE), but may instead send a reference signal to be measured by the UE and / or may receive and measure a signal sent by the UE. Such a base station may be referred to as a positioning beacon (e.g., in the case of sending a signal to the UE) and / or as a position measurement unit (e.g., in the case of receiving and measuring a signal from the UE).

[0042] An "RF signal" includes an electromagnetic wave of a given frequency that transmits information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal" or simply a "signal" where it is clear from the context that the term "signal" refers to a wireless signal or an RF signal.

[0043] FIG. 1 illustrates an example wireless communication system 100 according to various aspects of the present disclosure. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled as “BS”) and various UEs 104. The base stations 102 may include macro cell base stations (high power cellular base stations) and / or small cell base stations (low power cellular base stations). In one aspect, the macro cell base stations may include eNBs and / or ng-eNBs (where the wireless communication system 100 corresponds to an LTE network), or gNBs (where the wireless communication system 100 corresponds to an NR network), or a combination of the two, and the small cell base stations may include femto cells, pico cells, micro cells, etc.

[0044] The base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through a backhaul link 122, and interface with one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)) through the core network 170. The location server 172 may be part of the core network 170 or may be external to the core network 170. The location server 172 may be integrated with the base station 102. The UE 104 may communicate with the location server 172 directly or indirectly. For example, the UE 104 may communicate with the location server 172 via the base station 102 currently serving the UE 104. The UE 104 may also communicate with the location server 172 via another path, such as via an application server (not shown), via another network, such as via a wireless local area network (WLAN) access point (AP) (e.g., the AP 150 described below), etc. For signaling purposes, communications between UE 104 and location server 172 may be represented as an indirect connection (e.g., through core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), with intermediate nodes (if any) omitted from the signaling diagram for clarity.

[0045] Among other functions, the base station 102 may perform functions related to one or more of the following: delivering user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through EPC / 5GC) over a backhaul link 134, which may be wired or wireless.

[0046] Base station 102 may communicate wirelessly with UE 104. Each of base stations 102 may provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells may be supported by base station 102 in each geographic coverage area 110. A "cell" is a logical communication entity used to communicate with a base station (e.g., on a certain frequency resource, which is referred to as a carrier frequency, component carrier, carrier, frequency band, etc.), and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) used to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types) that may provide access to different types of UEs. Because a cell is supported by a specific base station, the term "cell" may refer to either or both of the logical communication entity and the base station supporting it, depending on the context. In addition, because the TRP is generally the physical transmission point of the cell, the terms "cell" and "TRP" may be used interchangeably. In some cases, the term "cell" may also refer to a geographic coverage area (e.g., a sector) of a base station, as long as a carrier frequency can be detected and used for communications within a portion of the geographic coverage area 110.

[0047] Although the geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in a handover area), some of the geographic coverage areas 110 may substantially overlap with the larger geographic coverage areas 110. For example, a small cell base station 102' (labeled "SC" for "small cell") may have a geographic coverage area 110' that substantially overlaps with the geographic coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB), which may provide services to a restricted group called a closed subscriber group (CSG).

[0048] The communication link 120 between the base station 102 and the UE 104 may include uplink (also referred to as reverse link) transmissions from the UE 104 to the base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be over one or more carrier frequencies. The allocation of carriers may be asymmetric for the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink than to the uplink).

[0049] The wireless communication system 100 may also include a WLAN access point (AP) 150 that communicates with a wireless local area network (WLAN) station (STA) 152 in an unlicensed spectrum (e.g., 5 GHz) via a communication link 154. When communicating in the unlicensed spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or a listen before talk (LBT) procedure prior to communication to determine whether a channel is available.

[0050] The small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell base station 102' can adopt LTE or NR technology and use the same 5GHz unlicensed spectrum used by the WLAN AP 150. The small cell base station 102' using LTE / 5G in the unlicensed spectrum can improve the coverage of the access network and / or increase the capacity of the access network. NR in the unlicensed spectrum can be referred to as NR-U. LTE in the unlicensed spectrum can be referred to as LTE-U, Licensed Assisted Access (LAA), or MulteFire.

[0051] The wireless communication system 100 may also include a millimeter wave (mmW) base station 180, which may operate at mmW frequencies and / or near mmW frequencies to communicate with UE 182. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz, with a wavelength between 1 mm and 10 mm. Radio waves in this band may be referred to as millimeter waves. Near mmW may extend down to a frequency of 3 GHz, with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, and is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands have high path loss and relatively short distances. The mmW base station 180 and the UE 182 may utilize beamforming (transmitting and / or receiving) on ​​the mmW communication link 184 to compensate for the extremely high path loss and short distance. In addition, it should be understood that in an alternative configuration, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.

[0052] The wireless communication system 100 may also include a UE 164, which may communicate with the macrocell base station 102 via a communication link 120 and / or communicate with the mmW base station 180 via a mmW communication link 184. For example, the macrocell base station 102 may support a PCell and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

[0053] In some cases, UE 164 and UE 182 are capable of sidelink communication. A UE with sidelink capability (SL-UE) can communicate with base station 102 via communication link 120 using a Uu interface (i.e., an air interface between a UE and a base station). SL-UEs (e.g., UE 164, UE 182) can also communicate directly with each other via a wireless sidelink 160 using a PC5 interface (i.e., an air interface between UEs with sidelink capability). A wireless sidelink (or just "sidelink") is an adaptation of a core cellular network (e.g., LTE, NR) standard that allows direct communication between two or more UEs without communicating through a base station. Sidelink communications can be unicast or multicast and can be used for device-to-device (D2D) media sharing, vehicle-to-vehicle (V2V) communications, vehicle-to-vehicle (V2X) communications (e.g., cellular V2X (cV2X) communications, enhanced V2X (eV2X) communications, etc.), emergency rescue applications, etc. One or more SL-UEs in a group of SL-UEs utilizing sidelink communications may be located within the geographic coverage area 110 of the base station 102. Other SL-UEs in such a group may be outside the geographic coverage area 110 of the base station 102, or may be unable to receive transmissions from the base station 102 for other reasons. In some cases, groups of SL-UEs communicating via sidelink communications may utilize a one-to-many (1:M) system, in which each SL-UE transmits to each other SL-UE in the group. In some cases, the base station 102 facilitates the scheduling of resources for sidelink communications. In other cases, sidelink communications are performed between the SL-UEs without involving the base station 102.

[0054] In one aspect, the sidelink 160 may operate on an interesting wireless communication medium that may be shared with other vehicles and / or infrastructure access points and other wireless communications between other RATs. A "medium" may include one or more time, frequency, and / or spatial communication resources associated with wireless communications between one or more transmitter / receiver pairs (e.g., covering one or more channels across one or more carriers). In one aspect, the interesting medium may correspond to at least a portion of an unlicensed band shared between various RATs. Although different licensed bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC) in the United States), these systems (particularly those that employ small cell access points) have recently expanded operations into unlicensed bands such as the unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technology (most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi"). Example systems of this type include different variants of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single carrier FDMA (SC-FDMA) systems, and the like.

[0055] In the example of FIG. 1 , any of the illustrated UEs (shown as a single UE 104 in FIG. 1 for simplicity) may receive a signal 124 from one or more earth orbiting space vehicles (SVs) 112 (e.g., satellites). In one aspect, the SVs 112 may be part of a satellite positioning system that the UEs 104 may use as an independent source of location information. A satellite positioning system typically includes a transmitter system (e.g., SVs 112) positioned to enable a receiver (e.g., UE 104) to determine its position on or above the earth based at least in part on a positioning signal (e.g., signal 124) received from the transmitter. Such transmitters typically transmit a signal that is marked with a repeating pseudo-random noise (PN) code of a set number of chips. Although typically located in the SVs 112, the transmitters may sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. The UEs 104 may include one or more dedicated receivers that are specifically designed to receive the signal 124 in order to derive geographic location information from the SVs 112.

[0056] In a satellite positioning system, the use of signal 124 may be enhanced by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems. For example, SBAS may include augmentation systems that provide integrity information, differential corrections, etc., such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multifunction Satellite Augmentation System (MSAS), Global Positioning System (GPS) Assisted Geographic Augmented Navigation or GPS and Geographic Augmented Navigation System (GAGAN), etc. Thus, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.

[0057] In one aspect, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, SV 112 is connected to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as an improved base station 102 (without a ground antenna) or a network node in a 5GC. This element in turn will provide access to other elements in the 5G network, and ultimately provide access to entities outside the 5G network (such as Internet web servers and other user devices). In this way, instead of or in addition to communication signals from a ground base station 102, a UE 104 can receive communication signals (e.g., signal 124) from a SV 112.

[0058] The wireless communication system 100 may also include one or more UEs, such as UE 190, which are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as "side links"). In the example of FIG. 1 , UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of base stations 102 (e.g., UE 190 may indirectly obtain cellular connectivity via the D2D P2P link), and has a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (UE 190 may indirectly obtain WLAN-based Internet connectivity via the D2D P2P link). In an example, the D2D P2P links 192 and 194 may be supported by any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth, or the like. ® wait.

[0059] FIG. 2A illustrates an example wireless network structure 200. For example, 5GC 210 (also referred to as Next Generation Core (NGC)) can be functionally viewed as control plane (C-plane) functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane (U-plane) functions 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.), which operate in conjunction to form a core network. A user plane interface (NG-U) 213 and a control plane interface (NG-C) 215 connect gNB 222 to 5GC 210, and specifically to user plane functions 212 and control plane functions 214, respectively. In additional configurations, ng-eNB 224 can also connect to 5GC 210 via NG-C 215 to control plane functions 214 and NG-U 213 to user plane functions 212. In addition, ng-eNB 224 can communicate directly with gNB 222 via backhaul connection 223. In some configurations, a next generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of ng-eNBs 224 and gNBs 222. Either gNB 222 or ng-eNB 224 (or both) may communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0060] Another optional aspect may include a location server 230 that can communicate with the 5GC 210 to provide location assistance for the UE 204. The location server 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively may each correspond to a single server. The location server 230 may be configured to support one or more location services for the UE 204 that may be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). In addition, the location server 230 may be integrated into a component of the core network, or alternatively may be external to the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

[0061] FIG2B illustrates another example wireless network structure 240. 5GC 260 (which may correspond to 5GC 210 in FIG2A) may be functionally viewed as a control plane function provided by an access and mobility management function (AMF) 264, and a user plane function provided by a user plane function (UPF) 262, which operate in conjunction to form a core network (i.e., 5GC 260). The functions of AMF 264 include: registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between one or more UEs 204 (e.g., any UE described herein) and a session management function (SMF) 266, a transparent proxy service for routing SM messages, access authentication and access authorization, transmission of short message service (SMS) messages between UE 204 and a short message service function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204, and receives intermediate keys established as a result of the UE 204 authentication process. In the case of authentication based on a UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), the AMF 264 retrieves security materials from the AUSF. The functions of the AMF 264 also include security context management (SCM). The SCM receives keys from the SEAF, which it uses to derive access network-specific keys. The functionality of the AMF 264 also includes location service management for regulatory services, for the transmission of location service messages between the UE 204 and the location management function (LMF) 270 (which acts as a location server 230), for the transmission of location service messages between the NG-RAN 220 and the LMF 270, for the allocation of Evolved Packet System (EPS) bearer identifiers for interoperation with EPS, and UE 204 mobility event notifications. In addition, the AMF 264 also supports functionality for non-3GPP (Third Generation Partnership Project) access networks.

[0062] The functions of UPF 262 include: acting as an anchor point for intra-RAT / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, user plane quality of service (QoS) handling (e.g., uplink / downlink rate enforcement, reflective QoS marking in downlink), uplink traffic verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering and downlink data notification triggering, and transmitting and forwarding one or more "end markers" to the source RAN node. UPF 262 may also support the delivery of location service messages between UE 204 and a location server (such as SLP 272) on the user plane.

[0063] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, traffic steering configuration for routing traffic to the correct destination at UPF 262, partial control of policy enforcement and QoS, and downlink data notification. The interface through which SMF 266 communicates with AMF 264 is called the N11 interface.

[0064] Another optional aspect may include an LMF 270 that can communicate with the 5GC 260 to provide location assistance for the UE 204. The LMF 270 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively can each correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can be connected to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not illustrated). SLP 272 may support similar functionality as LMF 270, but LMF 270 may communicate with AMF 264, NG-RAN 220, and UE 204 on a control plane (e.g., using interfaces and protocols intended to carry signaling messages rather than voice or data), and SLP 272 may communicate with UE 204 and external clients (e.g., third-party servers 274) on a user plane (e.g., using protocols intended to carry voice and / or data, such as Transmission Control Protocol (TCP) and / or IP).

[0065] Yet another optional aspect may include a third-party server 274 that may communicate with the LMF 270, the SLP 272, the 5GC 260 (e.g., via the AMF 264 and / or the UPF 262), the NG-RAN 220, and / or the UE 204 to obtain location information (e.g., a location estimate) of the UE 204. Thus, in some cases, the third-party server 274 may be referred to as a location service (LCS) client or an external client. The third-party server 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively may each correspond to a single server.

[0066] The user plane interface 263 and the control plane interface 265 connect the 5GC 260, and specifically the UPF 262 and the AMF 264, respectively, to one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220. The interface between the gNB 222 and / or ng-eNB 224 and the AMF 264 is referred to as the "N2" interface, and the interface between the gNB 222 and / or ng-eNB 224 and the UPF 262 is referred to as the "N3" interface. The gNBs 222 and / or ng-eNBs 224 of the NG-RAN 220 may communicate directly with each other via a backhaul connection 223 referred to as an "Xn-C" interface. One or more of the gNBs 222 and / or ng-eNBs 224 may communicate with one or more UEs 204 via a wireless interface referred to as a "Uu" interface.

[0067] The functionality of the gNB 222 may be divided between a gNB central unit (gNB-CU) 226, one or more gNB distributed units (gNB-DU) 228, and one or more gNB radio units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions other than those specifically assigned to the gNB-DU 228, including delivery of user data, mobility control, radio access network sharing, positioning, session management, and the like. More specifically, the gNB-CU 226 generally hosts the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that generally hosts the radio link control (RLC) and medium access control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 may support one or more cells, and one cell is supported by only one gNB-DU 228. The interface 232 between the gNB-CU 226 and one or more gNB-DUs 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of the gNB 222 is typically hosted by one or more independent gNB-RUs 229, which perform functions such as power amplification and signal transmission / reception. The interface between the gNB-DU 228 and the gNB-RU 229 is referred to as the "Fx" interface. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC layer, the SDAP layer, and the PDCP layer, communicates with the gNB-DU 228 via the RLC layer and the MAC layer, and communicates with the gNB-RU 229 via the PHY layer.

[0068] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element or a network equipment (such as a base station or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5GNB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also known as a stand-alone base station or a single-chip base station) or a decomposed base station.

[0069] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0070] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0071] FIG2C illustrates an example disaggregated base station architecture 250 in accordance with aspects of the present disclosure. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CUs 226) that may communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the core network 267 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 259 via an E2 link or a non-real-time (non-RT) RIC 257 associated with a service management and orchestration (SMO) framework 255, or both. The CU 280 may communicate with one or more distributed units (DUs) 285 (e.g., gNB-DUs 228) via respective midhaul links, such as an F1 interface. The DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via respective fronthaul links. The RU 287 can communicate with a corresponding UE 204 via one or more radio frequency (RF) access links. In some implementations, a UE 204 can be served by multiple RUs 287 simultaneously.

[0072] Each of the units (i.e., CU 280, DU 285, RU 287, and near-RT RIC 259, non-RT RIC 257, and SMO framework 255) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0073] In some aspects, CU 280 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 280. CU 280 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 280 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 280 may be implemented to communicate with DU 285 for network control and signaling.

[0074] DU 285 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 287. In some aspects, DU 285 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as that defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 285 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 285 or with control functions hosted by CU 280.

[0075] The lower layer functionality may be implemented by one or more RUs 287. In some deployments, the RU 287 controlled by the DU 285 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 287 may be implemented to handle over-the-air (OTA) communications with one or more UEs 204. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 287 may be controlled by the corresponding DU 285. In some scenarios, this configuration may enable the implementation of the DU 285 and the CU 280 in a cloud-based RAN architecture (such as a vRAN architecture).

[0076] The SMO framework 255 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 255 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 255 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 269) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 280, DU 285, RU 287, and near-RT RIC 259. In some specific implementations, the SMO framework 255 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 261) via the O1 interface. Additionally, in some specific implementations, the SMO framework 255 may communicate directly with one or more RUs 287 via the O1 interface. The SMO framework 255 may also include a non-RT RIC 257 configured to support the functionality of the SMO framework 255 .

[0077] The non-RT RIC 257 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 259. The non-RT RIC 257 may be coupled to or in communication with the near-RT RIC 259 (such as via an A1 interface). The near-RT RIC 259 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 280, one or more DUs 285, or both, and the O-eNB with the near-RT RIC 259.

[0078] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 259, the non-RT RIC 257 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 259 and may be received from a non-network data source or from a network function at the SMO framework 255 or the non-RT RIC 257. In some examples, the non-RT RIC 257 or the near-RT RIC 259 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 257 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 255 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0079] 3A, 3B, and 3C illustrate several example components (represented by corresponding boxes) that may be incorporated into a UE 302 (which may correspond to any UE described herein), a base station 304 (which may correspond to any base station described herein), and a network entity 306 (which may correspond to or embody any network function described herein, including a location server 230 and an LMF 270, or alternatively may be independent of the NG-RAN 220 and / or 5GC 210 / 260 infrastructure depicted in FIG. 2A and FIG. 2B, such as a dedicated network) to support operations as described herein. It should be understood that these components may be implemented in different types of devices with different specific implementations (e.g., in an ASIC, in a system on a chip (SoC), etc.). The illustrated components may also be incorporated into other devices in a communication system. For example, other devices in the system may include components similar to those described as providing similar functions. In addition, a given device may include one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0080] UE 302 and base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, which provide means (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for preventing transmitting, etc.) for communicating via one or more wireless communication networks (not shown), such as NR networks, LTE networks, GSM networks, etc. WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes (such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc.) via at least one designated RAT (e.g., NR, LTE, GSM, etc.) on a wireless communication medium of interest (e.g., a set of time / frequency resources in a particular spectrum). The WWAN transceivers 310 and 350 can be configured in different ways to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, the WWAN transceivers 310 and 350 include: one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.

[0081] At least in some cases, UE 302 and base station 304 each further include one or more short-range wireless transceivers 320 and 360, respectively. Short-range wireless transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide for communicating over the wireless communication medium of interest via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth ® 、Zigbee ® 、Z-Wave ®, PC5, dedicated short-range communication (DSRC), wireless access for vehicle environments (WAVE), near field communication (NFC), ultra-wideband (UWB), etc.) to communicate with other network nodes (such as other UEs, access points, base stations, etc.) (e.g., components for sending, components for receiving, components for measuring, components for tuning, components for preventing sending, etc.). The short-range wireless transceivers 320 and 360 can be configured in different ways to send and encode signals 328 and 368 (e.g., messages, indications, information, etc.) according to the specified RAT, and conversely, receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, the short-range wireless transceivers 320 and 360 respectively include: one or more transmitters 324 and 364 for sending and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively. As specific examples, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Bluetooth ® Transceiver, Zigbee ® and / or Z-Wave ® transceiver, NFC transceiver UWB transceiver or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceiver.

[0082] At least in some cases, the UE 302 and the base station 304 also include satellite signal receivers 330 and 370. The satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide means for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. In the case where the satellite signal receivers 330 and 370 are satellite positioning system receivers, the satellite positioning / communication signals 338 and 378 may be global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian regional navigation satellite system (NAVIC), quasi-zenith satellite system (QZSS), etc. In the case where the satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, the satellite positioning / communication signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network. The satellite signal receivers 330 and 370 may include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request appropriate information and operations from other systems and, at least in some cases, perform calculations using measurements obtained by any suitable satellite positioning system algorithm to determine the positions of UE 302 and base station 304, respectively.

[0083] The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, which provide means (e.g., means for transmitting, means for receiving, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 may employ one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. As another example, the network entity 306 may employ one or more network transceivers 390 to communicate with one or more base stations 304 via one or more wired or wireless backhaul links, or communicate with other network entities 306 via one or more wired or wireless core network interfaces.

[0084] The transceiver may be configured to communicate over a wired or wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes a transmitter circuit (e.g., transmitters 314, 324, 354, 364) and a receiver circuit (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., implementing the transmitter circuit and the receiver circuit in a single device), in some implementations may include separate transmitter circuits and separate receiver circuits, or may be implemented in other ways in other implementations. The transmitter circuit and the receiver circuit of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) may be coupled to one or more wired network interface ports. The wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform transmit "beamforming", as described herein. Similarly, the wireless receiver circuitry (e.g., receiver 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter circuitry and the receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 366) so that the corresponding device can only receive or only transmit at a given time, rather than both receive and transmit at the same time. The wireless transceivers (eg, WWAN transceivers 310 and 350 , short-range wireless transceivers 320 and 360 ) may also include a network listening module (NLM) or the like for performing various measurements.

[0085] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360 in some implementations, and network transceivers 380 and 390) and wired transceivers (e.g., network transceivers 380 and 390 in some implementations) may be generally characterized as a "transceiver," "at least one transceiver," or "one or more transceivers." Thus, whether a particular transceiver is a wired or wireless transceiver may be inferred based on the type of communication being performed. For example, backhaul communications between network devices or servers typically involve signaling via a wired transceiver, while wireless communications between a UE (e.g., UE 302) and a base station (e.g., base station 304) will typically involve signaling via a wireless transceiver.

[0086] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with the operations disclosed herein. UE 302, base station 304, and network entity 306 include one or more processors 332, 384, and 394, respectively, for providing functionality related to, for example, wireless communication, and for providing other processing functionality. Thus, processors 332, 384, and 394 can provide means for processing, such as means for determining, means for calculating, means for receiving, means for sending, means for indicating, etc. In one aspect, processors 332, 384, and 394 can include, for example, one or more general-purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), other programmable logic devices or processing circuits, or various combinations thereof.

[0087] UE 302, base station 304, and network entity 306 include memory circuitry implementing memory 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Thus, memory 340, 386, and 396 may provide means for storing, means for retrieving, means for maintaining, etc. In some cases, UE 302, base station 304, and network entity 306 may include beacon scanning components 342, 388, and 398, respectively. Beacon scanning components 342, 388, and 398 may be hardware circuits that are part of or coupled to processors 332, 384, and 394, respectively, which, when executed, cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, the beacon scanning components 342, 388, and 398 can be external to the processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the beacon scanning components 342, 388, and 398 can be memory modules stored in the memories 340, 386, and 396, respectively, which when executed by the processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. FIG. 3A illustrates possible locations for the beacon scanning component 342, which can be, for example, part of one or more WWAN transceivers 310, the memory 340, the one or more processors 332, or any combination thereof, or can be a standalone component. 3B illustrates possible locations for beacon scanning component 388, which may be, for example, part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a separate component. FIG. 3C illustrates possible locations for beacon scanning component 398, which may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a separate component.

[0088] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide a means for sensing or detecting movement and / or orientation information that is independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. As an example, sensor 344 may include an accelerometer (e.g., a microelectromechanical system (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of motion detection sensor. In addition, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate positioning in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.

[0089] In addition, the UE 302 includes a user interface 346 that provides means for providing indications to a user (e.g., audible and / or visual indications) and / or for receiving user input (e.g., when a user actuates a sensing device such as a keypad, touch screen, microphone, etc.). Although not shown, the base station 304 and the network entity 306 may also include a user interface.

[0090] Referring to the one or more processors 384 in more detail, in a downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functionality for an RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. One or more processors 384 may provide: RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0091] The transmitter 354 and the receiver 352 may implement layer 1 (L1) functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include: error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The transmitter 354 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially pre-decoded to generate multiple spatial streams. The channel estimate from the channel estimator can be used to determine the coding and modulation scheme and for spatial processing. The channel estimate can be derived based on a reference signal and / or channel condition feedback sent by the UE 302. Each spatial stream can then be provided to one or more different antennas 356. The transmitter 354 can modulate the RF carrier with the corresponding spatial stream for transmission.

[0092] At the UE 302, the receiver 312 receives the signal through its corresponding antenna 316. The receiver 312 recovers the information modulated onto the RF carrier and provides the information to one or more processors 332. The transmitter 314 and the receiver 312 implement layer 1 functionality associated with various signal processing functions. The receiver 312 may perform spatial processing on the information to recover any spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they may be combined into a single OFDM symbol stream by the receiver 312. The receiver 312 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point most likely to be sent by the base station 304. These soft decisions may be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent by the base station 304 on the physical channel. The data and control signals are then provided to one or more processors 332, which implement layer 3 (L3) and layer 2 (L2) functionality.

[0093] In the downlink, one or more processors 332 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the core network. One or more processors 332 are also responsible for error detection.

[0094] Similar to the functionality described in conjunction with downlink transmissions performed by the base station 304, the one or more processors 332 provide: RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

[0095] Channel estimates derived by the channel estimator from a reference signal or feedback sent by the base station 304 may be used by the transmitter 314 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the transmitter 314 may be provided to different antennas 316. The transmitter 314 may modulate an RF carrier with a corresponding spatial stream for transmission.

[0096] The uplink transmissions are processed at the base station 304 in a manner similar to that described in conjunction with the receiver functionality at the UE 302. The receiver 352 receives the signal through its respective antenna 356. The receiver 352 recovers the information modulated onto the RF carrier and provides the information to one or more processors 384.

[0097] In the uplink, one or more processors 384 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from UE 302. IP packets from one or more processors 384 may be provided to the core network. One or more processors 384 are also responsible for error detection.

[0098] For convenience, UE 302, base station 304 and / or network entity 306 are shown in FIG. 3A, FIG. 3B and FIG. 3C as including various components that can be configured according to various examples described herein. However, it should be understood that the illustrated components may have different functionality in different designs. Specifically, the various components in FIG. 3A to FIG. 3C are optional in alternative configurations, and various aspects include configurations that may vary due to design choices, costs, use of equipment, or other considerations. For example, in the case of FIG. 3A, a specific implementation of UE 302 may omit WWAN transceiver 310 (e.g., a wearable device or tablet computer or PC or laptop computer may have Wi-Fi and / or Bluetooth capabilities without cellular capabilities), may also omit short-range wireless transceiver 320 (e.g., only cellular, etc.), may also omit satellite signal receiver 330, may also omit sensor 344, etc. In another example, in the case of FIG. 3B , a particular implementation of the base station 304 may omit the WWAN transceiver 350 (e.g., a Wi-Fi “hotspot” access point without cellular capabilities), or may omit the short-range wireless transceiver 360 (e.g., cellular only, etc.), or may omit the satellite signal receiver 370, etc. For the sake of brevity, illustrations of various alternative configurations are not provided herein, but will be readily apparent to those skilled in the art.

[0099] Various components of the UE 302, base station 304, and network entity 306 may be communicatively coupled to one another via data buses 334, 382, ​​and 392, respectively. In an aspect, the data buses 334, 382, ​​and 392 may form or be part of a communication interface for the UE 302, base station 304, and network entity 306, respectively. For example, where different logical entities are embodied in the same device (e.g., gNB and location server functionality incorporated into the same base station 304), the data buses 334, 382, ​​and 392 may provide for communication between the different logical entities.

[0100] The components of FIG. 3A, FIG. 3B, and FIG. 3C may be implemented in various ways. In some specific implementations, the components of FIG. 3A, FIG. 3B, and FIG. 3C may be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or combine at least one memory component for storing information or executable code used by the circuit to provide the function. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by the processor and memory component of UE 302 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by the processor and memory component of base station 304 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). Moreover, some or all of the functionality represented by blocks 390 to 398 may be implemented by the processor and memory component of network entity 306 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). For simplicity, various operations, actions and / or functions are described herein as being performed “by a UE,” “by a base station,” “by a network entity,” etc. However, as will be appreciated, such operations, actions and / or functions may actually be performed by a specific component or combination of components of the UE 302, base station 304, network entity 306, etc., such as processors 332, 384, 394, transceivers 310, 320, 350, and 360, memories 340, 386, and 396, beacon scanning components 342, 388, and 398, etc.

[0101] In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be operated separately from a network operator or a cellular network infrastructure (e.g., NG RAN 220 and / or 5GC 210 / 260). For example, the network entity 306 may be a component of a dedicated network that may be configured to communicate with the UE 302 via the base station 304 or independently of the base station 304 (e.g., via a non-cellular communication link such as WiFi).

[0102] Various types of wireless energy charging capabilities are implemented on UEs (e.g., electromagnetic charging such as Qi wireless charging, wind-based charging, solar-based charging, vibration-based charging, etc.). Another type of wireless charging is radio frequency for energy harvesting (RF-EH). An RF source can provide a controllable and substantially constant energy transfer to a UE with wireless energy charging capabilities over a certain distance. In a fixed wireless energy charging network, due to the fixed distance, the harvested energy is predictable and relatively stable over time.

[0103] FIG. 4 illustrates a device 400 having wireless energy charging capabilities (eg, having RF-EH capabilities) according to an aspect of the present disclosure.

[0104] In some designs, the device 400 having wireless energy charging capabilities may correspond to a passive device (eg, a device that is temporarily turned on when wireless energy is being provided and then transitions to a passive state or a sleep state when wireless energy is not being provided).

[0105] The device 400 with wireless energy charging capability includes an energy storage unit 402 (e.g., a battery, a capacitor, etc.), a power management module 404 (e.g., which decides whether to store the power obtained from the wireless energy source or use the power immediately for information transmission), a wireless energy charging / capture circuit 406 (e.g., to collect RF signals and convert them into power), antennas 408-410, a lower power RF transceiver 412 (e.g., for information transmission or reception), a lower power microcontroller 414 (e.g., to process data), and an application 416. The wireless energy charging / capture circuit 406 includes a capacitor 406-1, a voltage multiplier 406-2, and an impedance matching module 406-3. In general, modules 402-408 are associated with wireless energy charging / capture, while modules 410-416 are associated with communication. The device 400 with wireless energy charging capability constitutes an example of a separate receiver architecture, whereby the antenna 408 is dedicated to the wireless energy charging / capture circuit 406, while the antenna 410 is dedicated to the communication circuit (e.g., without antenna reuse, or switching or power splitting the wireless energy charging / capture circuit and the communication circuit). In some designs, the modules 402-408 are associated with wireless energy charging / capture, and may also include a clock component for calibrating an internal oscillator rather than a time transfer function (e.g., so that the device 400 with wireless energy charging capability may be able to trigger the transmission of a signal (such as a beacon) at a later stage). In other designs, the modules 402-408 may include a clock component for calibration and a time transfer component to facilitate the time transfer function. For example, in addition to supplying a clock (which itself may also be collected from other sources), the wireless energy source may also send a schedule that will drive the beacon transmission - and therefore may also help supply a beacon scanning window, as will be described in more detail below. Thus, in one aspect, the device 400 with wireless energy charging capability may (in addition to providing wireless energy) be able to provide (via wireless energy transmission) clock transfer, time transfer (e.g., via a communication protocol), or both for OSC calibration purposes. In some designs, the wireless energy charging rate is offset by the wireless energy leakage rate (e.g., a 2 mAh / second charging rate minus a 0.1 mAh / second leakage rate results in a net charging rate of 1.9 mAh / second). In other designs, the wireless energy charging rate and the wireless energy leakage rate may be separate parameters, with the leakage rate also factored into the time estimate of the beacon transmission.

[0106] An example implementation of the communication system is an inventory (or asset) tracking system. For example, the asset tracking system may be deployed in a warehouse, a retail store space, etc. For example, a pallet including cases and boxes may be assembled at a distribution center and then dispatched to a particular retail store. Once at the retail store, the pallet is broken down into cases and boxes, which may be immediately moved to the store floor for horizontal placement of items on shelves or restocking. Cases and boxes may also be stored in a back room for later dispatch. As used herein, "asset" is intended to be interpreted broadly and may correspond to a separate or single product, a crate containing multiple products (e.g., before being packaged at a warehouse or distribution center), etc.

[0107] Real-time tracking of asset locations (e.g., from a pallet at a distribution center to a pallet at a retail store to a shelf at a retail store, etc.) is difficult in current asset tracking systems. Specifically, the ability of retailers to accurately (or with a given degree of accuracy, such as knowledge of the count or amount of assets, etc.) determine the inventory currently available to physical customers ("brick and mortar" stores) is an elusive goal. Providing this information to retailers can be very valuable. For example, real-time tracking of asset counts can help facilitate dynamic, on-demand or periodic updates of inventory to improve logistics, develop additional revenue streams, reduce waste and improve "just-in-time" methods, resulting in the avoidance of empty shelves and unnecessary consumption of real estate in back-room storage.

[0108] In addition to quantitative information about which products are in the store, knowledge of asset placement throughout the space and the accuracy of the intended deployment (the proposed planogram) versus reality (the actual planogram) is also important and valuable information to supply to any retailer. For example, identifying items that are “displaced” by the store (e.g., a customer picks up items and moves them from a basket to somewhere else in the store) allows retailers to recover and reorganize.

[0109] Furthermore, in addition to location, state information may also be retrieved (e.g., relating to any device state information, including location, but potentially including other state information such as battery state in the case of an active BLE tag, any other type of device health information, sensor information, etc.). For example, an asset may be equipped with sensors that measure parameters such as freshness (e.g., for food items, based on the detection of noxious gases that indicate the progression of decay or ripening), history sensors (e.g., for frozen foods, such sensors may measure the amount of time the asset has been kept in an environment that exceeds a temperature threshold), etc.

[0110] One example of an asset tracking system may rely on an electronic shelf label (ESL) infrastructure. FIG. 5 illustrates an in-store portion 500 of an ESL system according to aspects of the present disclosure. In FIG. 5 , the in-store portion 500 of the ESL system includes a shelf 510 having track displays 512 , 514 , and 516 . In some designs, the track displays (referred to herein as ESLs, which may present information via displays such as liquid crystal displays (LCDs), electronic ink, etc.) 512 , 514 , and 516 may be coupled to a controller (not shown) that controls the ESLs 512 , 514 , and 516 . ESL 512 is proximate to a shelf location where a bottle 522 having a BLE tag 524 is stored, ESL 514 is proximate to a shelf location where a box 526 having a BLE tag 528 is stored, and ESL 516 is proximate to a shelf location where a box 530 having a BLE tag 532 is stored. In FIG. 5 , the in-store portion 500 of the ESL system also includes a shelf 540 having ESLs 542 , 544 , and 546 . In some designs, ESLs 542, 544, and 546 may be coupled to a controller (not shown) that controls ESLs 542, 544, and 546. ESL 542 is proximate to a shelf location that stores bins 552 and 556 having BLE tags 554 and 558, respectively, ESL 544 is proximate to a shelf location that stores box 560 having BLE tag 562, and ESL 546 is proximate to a shelf location that stores box 564 having BLE tag 566.

[0111] In some designs, ESLs 512, 514, 516, 542, 544, and 546 may be implemented as "true" ESLs (e.g., controlled via RF elements incorporated within and associated with a battery) that are communicatively coupled to a track display (e.g., limited to a small microcontroller unit (MCU) for purposes of processing commands / control issued by a track controller, without radio components for communication purposes, and without a battery). In such designs, the ESLs and associated track displays are typically not used as asset scanning devices or wireless energy sources.

[0112] In some designs, a BLE "tag" may be printed or otherwise made as part of the asset packaging. In some designs, a BLE tag may correspond to a battery-free (or passive) BLE device equipped with a wireless energy harvester and a BLE radio component, or a battery-powered (or active) BLE device equipped with a small battery (e.g., 50 mAh) and a BLE radio component. A passive BLE device may function similarly to an RFID tag / label, but a passive BLE device may further support the BLE protocol, limited processing capabilities, and limited communication capabilities while harvesting wireless energy.

[0113] In some designs, the controller can be part of an ESL system whereby the controller is coupled to a serial interface capable of establishing a wired connection with a plurality of track displays (electronic ink) attached to the tracks of the shelf. In some designs, the battery capacity available at the controller (e.g., 3500 mAh) can be significantly greater than the battery capacity of the ESL (e.g., 345 mAh for the radio component).

[0114] 6 illustrates an ESL system infrastructure 600 according to aspects of the present disclosure. The ESL system infrastructure 600 includes a management entity 610, a scanning device controller 620, an ESL 630, a wireless energy source 640, a battery-less (or passive) BLE device 650, and a battery-powered (active) BLE device 660.

[0115] Referring to FIG. 6 , in some designs, the management entity 610 may be a cloud-based server that manages an ESL group (such as ESL 630) via a scanning device controller (such as scanning device controller 620). In some designs, the scanning device controller 620 provides a communication link between the management entity 610 and the ESL 630 (e.g., the management entity 610 may send commands to the ESL 630 via the scanning device controller 620). For example, the scanning device controller 620 may periodically send data packets or announcements (e.g., once every 12.5ms for 625us) and wait for a response. In some designs, the scanning device controller 620 may concurrently establish connections with up to a certain number (e.g., three) of ESLs. In some designs, the scanning device controller 620 may be used for BLE broadcasts (beacons) sporadically and in a timely manner. In other aspects, the scanning device controller 620 may act as a translation point between Internet-based communication protocols (such as TCP / IP, HTTP, etc.) and specific BLE-based solutions (e.g., ESL protocols). The scanning device controller 620 will in turn be connected to the ME 610 which is responsible for the overall management of the various terminal entities (eg, ESL).

[0116] Referring to FIG6 , in some designs, the ESL 630 may output customer prices / information related to products that are co-located with those products (e.g., see discussion above regarding FIG5 ). In some designs, the ESL 630 may be equipped with a BLE radio capable of receiving commands from the management entity 610 via a scanning device controller 620 and sending responses to the management entity 610 via the scanning device controller 620. Additionally, in some designs, the ESL 630 may have the ability to scan for beacons from BLE tags via active scanning. A variation on this is a track controller whereby one radio is shared among many displays.

[0117] 6, a battery-free (or passive) BLE device 650 can be implemented as a battery-free tag that will harvest "ambient" energy from such solar energy, light, vibration, temperature gradient, radio frequency. However, the battery-free (or passive) BLE device 650 can also harvest "dedicated" energy from a wireless energy source. In contrast, a battery-powered (or active) BLE device 660 has a limited battery capacity (e.g., in a printable format).

[0118] 6, a battery powered (or active) BLE device 660 is configured to be in a dormant state in order to conserve energy, and can be activated using a specific wake-up radio signal from a target scanning device controller (such as scanning device controller 620). In some designs, the wake-up radio signal can be linked to a wireless energy source (e.g., this does not have to be co-located with the scanning device controller, but can be co-located with the battery-free BLE device). Active BLE devices are generally well known and frequently used in ESL tracking infrastructure.

[0119] For example, an active BLE device may transmit a beacon that is captured by a scanner (e.g., ESL) at a known location in order to establish a proximity determination. For example, a wake-up radio configuration may reduce or remove latency requirements (e.g., the strength of the received wake-up radio signal (in terms of energy captured over a given amount of time) may be used to tune (in time) the provided response, which may result in behavior equivalent to a battery-less BLE device). In some designs, the scheduling of transmissions may be achieved through an internal timer or detection of an external signal monitored by the active BLE device itself. In one aspect, an active BLE device supporting the ESL protocol brings multiple benefits:

[0120] • Active BLE devices consume energy only to track and scan device controller signals,

[0121] • Active BLE devices may be directed by a management entity to begin beaconing and / or scanning (eg, as needed) to further extend battery life,

[0122] • A scanning device controller may report active BLE devices beaconing and therefore infer proximity to the scanning device controller,

[0123] • The management entity and / or scanning device controller may instruct active BLE devices to beacon or scan in a synchronized manner, and

[0124] • Active BLE device scanning will provide other active BLE devices and / or ESL proximity, allowing for more refined location.

[0125] Various aspects of the present disclosure relate to scheduling beacon scan windows based on a time estimate of when a device with wireless energy charging capability coupled to an asset is expected to transmit a beacon. In certain aspects, the time estimate may be based on a distance between a wireless energy source and a scanning device in proximity to the device with wireless energy charging capability. Such aspects may provide various technical advantages, such as reducing power consumption at a scanning device (e.g., more focused scanning based on beacon transmission timing estimates), reducing power consumption at a battery-powered (active) BLE device (e.g., transmitting with reduced power to reach a nearby ESL rather than a more distant AP), improving detection of beacons in an asset tracking system, etc.

[0126] 7 illustrates an exemplary process 700 according to aspects of the present disclosure. In one aspect, process 700 may be performed by an asset tracking coordination component (e.g., UE 302, a BS or gNB such as BS 304, or an O-RAN component such as RU, DU, or CU, a server such as network entity 306, etc.). In another example, the asset tracking coordination component may correspond to a scanning device controller such as scanning device controller 620 or a management entity such as management entity 610.

[0127] 7 , at 710 , an asset tracking coordination component (e.g., processor 332 or 384 or 394 , beacon scanning component 342 or 388 or 398 , etc.) estimates a distance between a wireless energy source and a scanning device. In one aspect, the asset tracking coordination component may include (or correspond to) a scanning device. In another aspect, the asset tracking coordination component and the scanning device may be implemented as different components (e.g., a scanning device controller and an ESL). In one example, the asset tracking coordination component corresponds to an electronic shelf label (ESL) scanning device controller, and the device having wireless energy charging capability corresponds to a passive Bluetooth low energy (BLE) tag.

[0128] 7 , at 720 , an asset tracking coordination component (e.g., processor 332 or 384 or 394 , beacon scanning component 342 or 388 or 398 , etc.) determines timing information associated with wireless energy transmissions from a wireless energy source. For example, the timing information may correspond to a schedule for when the wireless energy source is expected to provide wireless energy in proximity to a device with wireless energy charging capabilities that is coupled to an asset within a threshold proximity of a scanning device. In some designs, the timing information may be scheduled (or coordinated) by the asset tracking coordination component. In other designs, the timing information may be scheduled (or coordinated) by different components that then report the timing information to the asset tracking coordination component.

[0129] 7 , at 730, an asset tracking coordination component (e.g., processor 332 or 384 or 394, beacon scanning component 342 or 388 or 398, etc.) estimates a time of beacon transmission from a device with wireless energy charging capability coupled to an asset within a threshold proximity of the scanning device based on the estimated distance and timing information. For example, the time estimate of 720 may be based on an expectation of when the device with wireless energy charging capability is expected to be sufficiently charged to transmit a beacon.

[0130] 7 , at 740 , an asset tracking coordination component (e.g., processor 332 or 384 or 394 , beacon scanning component 342 or 388 or 398 , etc., transmitter 314 or 324 or 354 or 364 , network transceiver 380 or 390 ) schedules a beacon scanning window for a scanning device to scan for beacons based on an estimated time.

[0131] FIG8 illustrates an example ESL system infrastructure 800 based on the process 700 of FIG7 according to aspects of the present disclosure. The ESL system infrastructure 800 includes a management entity 810, a scanning device controller 820, an ESL 830, a wireless energy source 840, and a battery-free (or passive) BLE device 850. Although not explicitly depicted, similar to FIG6, a battery-powered (active) BLE device may also be part of the ESL system infrastructure 800.

[0132] 8, unlike the ESL system infrastructure 600 of FIG6, the wireless energy source 840 includes an ESL function 845 that facilitates ESL coordination via a BLE communication link 870. In one aspect, such coordination can facilitate the asset tracking coordination component to determine timing information associated with wireless energy transmissions from the wireless energy source at 720 of FIG7. In other designs, the wireless energy source 840 can be onboard with the scanning device controller 820, and the scanning device controller 820 can direct the wireless energy source 840 regarding a schedule for powering up via a BLE communication link 875.

[0133] FIG. 9 illustrates an example implementation 900 of the process of FIG. 7 according to aspects of the present disclosure. In FIG. 9 , the estimated distance between the wireless energy source 840 and the ESL 830 (e.g., the scanning device) is represented as a plurality of zones, which are referred to as Zone 0, Zone 1, and Zone 2. In general, the farther the scanning device is from the wireless energy source, the longer it will take for the approaching battery-free (passive) BLE device to send its corresponding beacon. In FIG. 9 , the battery-free (passive) BLE devices 850A-850B are arranged in Zone 2 with the ESL 830.

[0134] For example, it is assumed that each battery-less (passive) BLE device will transmit a beacon once a sufficient amount of energy has been harvested. Synchronization between the wireless energy source 840 and the scanning device controller 820 also allows the associated ESL (with the same AP) to schedule scans based on the distance between the ESL and the wireless energy source 840 - for example, so that only battery-less (passive) BLE devices in its vicinity are collected (e.g., note that in some designs this is not strictly true, as any attachment placed at an equal distance from the wireless charging source 840 may transmit its respective beacon at a similar time - however, the signal strength of such beacons as received by the ESL 830 will provide some proximity information).

[0135] In some designs, the scanning device controller 820 may control when the wireless energy source 840 (and therefore the scanning window of the ESL) is occupied (e.g., the arrival time relative to the power-on start beacon may determine a rough indication of the distance between the battery-less BLE devices 850A-850B and the wireless energy source 840 - observations at multiple points in the system will allow some very rough trilateration estimates). In some designs, the proximal placement of the ESL used for scanning relative to the battery-less (passive) BLE devices provides the following technical advantages: reduced power consumption at the battery-less (passive) BLE devices (e.g., the battery-less (passive) BLE devices only need to transmit to the closest ESL near their respective shelf locations, rather than the scanning device controller, which may be very far away). In some designs, although not explicitly shown in FIG. 9, the proximity between the ESL and the battery-less (passive) BLE device may be further exploited, where the ESL is used as a wireless energy source, time-division multiplexed with scanning, or scanning is performed in conjunction with other nearby ESLs.

[0136] Referring to FIG. 9 , in the example, it is assumed that a battery-free (passive) BLE device in zone 0 is expected to i The battery-free (passive) BLE device in zone 1 is expected to send a beacon at t j t , and the battery-free (passive) BLE device in zone 1 sends a beacon at t k Send a beacon at i < t j < t k The scanning devices in zone 0, zone 1, and zone 2 may therefore have different scanning windows based on these timing estimates (eg, the scanning window for zone 0 may be defined as t i Adding / subtracting an offset, the scan window for zone 0 can be defined as t j plus / minus offset, and the scan window for zone 0 can be defined as t ik plus / minus offset).

[0137] 7, in some designs, the asset tracking coordination component corresponds to an electronic shelf label (ESL) scanning device controller, and the device with wireless energy charging capability corresponds to a passive BLE tag.

[0138] Referring to FIG. 7 , in some designs, the asset tracking coordination component may further determine the expected wireless energy charging rate associated with the device with wireless energy charging capability in the candidate location area based on the distance, the power of the wireless energy transmission, and the frequency associated with the wireless energy transmission. The asset tracking coordination component may further determine the energy charging level at which the device with wireless energy charging capability is triggered to transmit the beacon transmission. In this case, the estimated time at 730 is based on the expected wireless energy charging rate (e.g., in some designs, based on the radio frequency of the wireless energy, the pulse (time) of the frequency, the pulse duration and / or the transmission power) and the energy charging level. As described above, this aspect is depicted in FIG. 9 . In one aspect, the frequency of the wireless energy transmission may determine the spacing between the energy bursts and will enter into the calculation of the time required for data accumulation (e.g., the spacing of these pulses may be taken into account with respect to leakage of battery-free BLE devices).

[0139] 7, in some designs, a scanning device may include an asset tracking coordination component. In other words, the scanning device may be a physical component of an asset tracking coordination component (eg, ESL).

[0140] 7, in some designs, the scanning device is distinct from the asset tracking coordination component. In this case, in one aspect, the scanning device is closer to the device having wireless energy charging capability than the asset tracking coordination component. For example, the asset tracking coordination component may correspond to a scanning device controller, and the scanning device may correspond to an ESL that is close to an asset having a passive BLE tag on a nearby shelf. Additionally, in this case, the scheduling at 740 may include sending an indication of a beacon scan window to the scanning device.

[0141] 7 , in some designs, the scanning device is separated from the wireless energy source, as shown in FIG. 9 as an example.

[0142] Various aspects of the present disclosure further relate to a scanning device that not only scans for beacons from battery-powered (active) BLE devices, but is also configured as a wireless energy source that provides energy to trigger the corresponding beacons. Such aspects can provide various technical advantages, such as more localized wireless energy charging (e.g., charging can be performed via a nearby ESL rather than a more distant AP, etc.), which can result in reduced power consumption, more certainty in beacon transmission timing (e.g., this can reduce the scan window duration and thereby also reduce power consumption) and / or more certainty in scan window intervals (e.g., no need to move back and forth between power-on and scanning to the asset tracking coordination component, so no more local timing estimates are needed), etc.

[0143] 10 illustrates an exemplary process 1000 in accordance with aspects of the present disclosure. In one aspect, process 1000 may be performed by a scanning device (e.g., a UE such as UE 302, a network component such as a gNB or BS 304, etc.). In further examples, the asset tracking coordination component may correspond to a scanning device controller such as scanning device controller 620 or scanning device controller 820 or an ESL (e.g., ESL 512, 514, etc.).

[0144] 10 , at 1010 , a scanning device (eg, receiver 312 or 322 or 352 or 362 , network transceiver 380 , etc.) receives a request from an asset tracking coordination component to perform an asset scan in conjunction with wireless energy transmission from the scanning device.

[0145] 10 , at 1020 , the scanning device (e.g., transmitter 314 or 324 or 354 or 364, beacon scanning component 342 or 388, etc.) performs wireless energy transmission in response to the request. For example, the wireless energy transmission may be performed at a specific time, within a specific duration, at a specific transmission power level, at a specific frequency, etc. as specified by the request.

[0146] 10 , at 1030 , a scanning device (e.g., receiver 312 or 322 or 352 or 362 , processor 332 or 384 , beacon scanning component 342 or 388 , etc.) monitors one or more beacon transmissions from one or more wireless energy charging-capable devices coupled to one or more assets within a threshold proximity of the scanning device in response to a request during a beacon scanning window based on wireless energy transmissions.

[0147] 10 , at 1040 , a scanning device (eg, transmitter 314 or 324 or 354 or 364 , beacon scanning component 342 or 388 , network transceiver 380 , etc.) transmits scan result information to an asset tracking coordination component based on monitoring.

[0148] FIG11 illustrates an exemplary process 1100 according to aspects of the present disclosure. In one aspect, process 1100 may be performed by an asset tracking coordination component (e.g., UE 302, a BS or gNB such as BS 304, or an O-RAN component such as RU, DU, or CU, a server such as network entity 306, etc.). In another example, the asset tracking coordination component may correspond to a scanning device controller such as scanning device controller 620 or a management entity such as management entity 610.

[0149] 11 , at 1110, an asset tracking coordination component (e.g., transmitter 314 or 324 or 354 or 364, network transceiver 380 or 390, beacon scanning component 342 or 388 or 398, etc.) sends a request to a scanning device to perform an asset scan in conjunction with wireless energy transmissions from the scanning device, the asset scan comprising monitoring one or more beacon transmissions from one or more devices with wireless energy charging capabilities of one or more assets within a threshold proximity coupled to a wireless energy source during a beacon scanning window based on the wireless energy transmissions.

[0150] 11 , at 1120 , an asset tracking coordination component (eg, receiver 312 or 322 or 352 or 362 , network transceiver 380 or 390 , beacon scanning component 342 or 388 or 398 , etc.) receives scan result information from a wireless energy source based on monitoring.

[0151] 10-11 , in some designs, the asset tracking coordination component corresponds to an electronic shelf label (ESL) scanning device controller, and the one or more devices with wireless energy charging capability correspond to one or more passive Bluetooth low energy (BLE) tags.

[0152] 10-11, in some designs, the scanning device may include (or may correspond to) an asset tracking coordination component. In this case, the sending / receiving operations described with reference to FIG. 10-11 may be internal communications across the corresponding data bus.

[0153] 10-11, in some designs, the scanning device is remote from the asset tracking coordination component. In this case, on the one hand, the scanning device is closer to one or more devices with wireless energy charging capabilities than the asset tracking coordination component (e.g., this can result in reduced power consumption at the scanning device and / or the device with wireless energy charging capabilities, as described above).

[0154] 10-11 , in some designs, the scanning device may further receive (and the asset tracking coordination component may further send) an indication of a beacon scan window. In one aspect, in an example, the beacon scan window may be determined as described above with respect to FIG.

[0155] FIG12 illustrates an example ESL system infrastructure 1200 based on the processes 1000-1100 of FIG10-11, respectively, according to aspects of the present disclosure. The ESL system infrastructure 1200 includes a management entity 1210, a scanning device controller 1220, an ESL 1230A, an ESL 1230B, and a battery-free (or passive) BLE device 1250. Although not explicitly depicted, similar to FIG6, a battery-powered (active) BLE device may also be part of the ESL system infrastructure 1200.

[0156] Referring to FIG. 12 , unlike the ESL system infrastructure 800 of FIG. 6 , a “dedicated” wireless energy source is not depicted in FIG. 12 . Instead, ESL 1230A acts as both a wireless energy source and a scanning device that monitors beacons from battery-free (or passive) BLE devices 1250 (e.g., although ESL 1230A may have this dual capability, sometimes, ESL 1230A may operate in only scanner mode or only energy source mode). In contrast, ESL 1230B operates similarly to ESL 830 of FIG. 8 , whereby ESL 1230B performs only scanning functions. Therefore, in some designs, some ESLs may be arranged as wireless energy sources, while other ESLs are not arranged as wireless energy sources. In yet other designs, each ESL may be configured as both a wireless energy source and a scanning device.

[0157] In one aspect, ESL 1230A may modify its "normal" RF mode to generate wireless energy packets via link 1270 (e.g., calibrate clock signal plus energy). In some designs, scanning may be time-division multiplexed with these wireless energy packets from ESL 1230A. As described above, in some designs, scanning by ESLs 1230A-1230B may be coordinated by a common or shared scanning device controller that controls both ESLs 1230A-1230B.

[0158] In the above specific embodiments, it can be seen that different features are grouped together in each example. This disclosure should not be understood as an intention that the example clauses have more features than the features explicitly mentioned in each clause. On the contrary, various aspects of the present disclosure may include less than all the features of the disclosed individual example clauses. Therefore, the following clauses should be considered to be incorporated into the description accordingly, where each clause itself can be used as a separate example. Although each subordinate clause may refer to a specific combination of one clause with other clauses in a clause, the aspects of the subordinate clause are not limited to a specific combination. It should be understood that other example clauses may also include a combination of the subject matter of the subordinate clause aspect with any other subordinate clause or independent clause or any feature with other subordinate clauses and independent clauses. The various aspects disclosed herein explicitly include these combinations, unless it is clearly expressed or can be easily inferred that a specific combination is not intended to be used (for example, contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). In addition, it is also expected that various aspects of the clause may be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

[0159] Specific implementation examples are described in the following numbered clauses:

[0160] Clause 1. A method of operating an asset tracking coordination component, comprising: estimating a distance between a wireless energy source and a scanning device; determining timing information associated with a wireless energy transmission from the wireless energy source; estimating a time of a beacon transmission from a device with wireless energy charging capability coupled to an asset within a threshold proximity of the scanning device based on the estimated distance and the timing information; and scheduling a beacon scanning window for the scanning device to scan for the beacon transmission based on the estimated time.

[0161] Clause 2. The method of clause 1, wherein the asset tracking coordination component corresponds to an electronic shelf label (ESL) scanning device controller, and wherein the device having wireless energy charging capability corresponds to a passive Bluetooth Low Energy (BLE) tag.

[0162] Clause 3. The method according to any one of clauses 1 to 2 further includes: determining an expected wireless energy charging rate associated with the device with wireless energy charging capability in the candidate location area based on the distance, the power of the wireless energy transmission, and the frequency associated with the wireless energy transmission; and determining the energy charging level at which the device with wireless energy charging capability is triggered to send the beacon, wherein the estimated time is based on the expected wireless energy charging rate and the energy charging level.

[0163] Clause 4. The method of any one of clauses 1 to 3, wherein the scanning device comprises the asset tracking coordination component.

[0164] Clause 5. The method of any one of clauses 1 to 4, wherein the scanning device is distinct from the asset tracking coordination component.

[0165] Clause 6. The method of clause 5, wherein the scanning device is closer to the wireless energy charging capable device than the asset tracking coordination component.

[0166] Clause 7. The method of any one of clauses 5 to 6, wherein the scheduling comprises sending an indication of the beacon scanning window to the scanning device.

[0167] Clause 8. The method of any one of clauses 1 to 7, wherein the scanning device is separate from the wireless energy source.

[0168] Item 9. A method for operating a scanning device, comprising: receiving a request from an asset tracking coordination component to perform an asset scan in conjunction with wireless energy transmissions from the scanning device; performing the wireless energy transmissions in response to the request; monitoring one or more beacon transmissions from one or more devices with wireless energy charging capabilities of one or more assets coupled to the scanning device within a threshold proximity in response to the request during a beacon scanning window based on the wireless energy transmissions; and sending scan result information to the asset tracking coordination component based on the monitoring.

[0169] Clause 10. The method of clause 9, wherein the asset tracking coordination component corresponds to an electronic shelf label (ESL) scanning device controller, and wherein the one or more devices having wireless energy charging capabilities correspond to one or more passive Bluetooth Low Energy (BLE) tags.

[0170] Clause 11. The method of any of clauses 9 to 10, wherein the scanning device comprises the asset tracking coordination component.

[0171] Clause 12. The method of any of clauses 9 to 11, wherein the scanning device is distinct from the asset tracking coordination component.

[0172] Clause 13. The method of clause 12, wherein the scanning device is closer to the one or more wireless energy charging capable devices than the asset tracking coordination component.

[0173] Clause 14. The method of any of clauses 12-13, further comprising: receiving an indication of the beacon scan window from the asset tracking coordination component.

[0174] Item 15. A method for operating an asset tracking coordination component comprises: sending a request to a scanning device to perform an asset scan in combination with wireless energy transmissions from the scanning device, the asset scan comprising monitoring one or more beacon transmissions from one or more devices with wireless energy charging capabilities of one or more assets within a threshold proximity coupled to a wireless energy source during a beacon scanning window based on the wireless energy transmissions; and receiving scan result information from the wireless energy source based on the monitoring.

[0175] Clause 16. The method of Clause 15, wherein the beacon scan window is determined based on one or more estimated times of one or more beacon transmissions from the one or more wireless energy charging capable devices.

[0176] Clause 17. A method according to any one of clauses 15 to 16, wherein the asset tracking coordination component corresponds to an electronic shelf label (ESL) scanning device controller, and wherein the one or more devices with wireless energy charging capabilities correspond to one or more passive Bluetooth low energy (BLE) tags.

[0177] Clause 18. The method of any one of clauses 15 to 17, wherein the scanning device comprises the asset tracking coordination component.

[0178] Clause 19. The method of any one of clauses 15 to 18, wherein the scanning device is remote from the asset tracking coordination assembly.

[0179] Clause 20. The method of clause 19, wherein the scanning device is closer to the one or more wireless energy charging capable devices than the asset tracking coordination component.

[0180] Clause 21. The method of clause 20, further comprising: sending an indication of the beacon scan window to the scanning device.

[0181] Item 22. An asset tracking coordination component comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: estimate a distance between a wireless energy source and a scanning device; determine timing information associated with a wireless energy transmission from the wireless energy source; estimate a time of a beacon transmission from a device with wireless energy charging capability of an asset within a threshold proximity coupled to the scanning device based on the estimated distance and the timing information; and schedule a beacon scanning window for the scanning device to scan for the beacon transmission based on the estimated time.

[0182] Clause 23. The asset tracking coordination component of clause 22, wherein the asset tracking coordination component corresponds to an electronic shelf label (ESL) scanning device controller, and wherein the device having wireless energy charging capability corresponds to a passive Bluetooth Low Energy (BLE) tag.

[0183] Clause 24. An asset tracking coordination component according to any one of clauses 22 to 23, wherein the at least one processor is further configured to: determine an expected wireless energy charging rate associated with the device with wireless energy charging capability in the candidate location area based on the distance, the power of the wireless energy transmission, and the frequency associated with the wireless energy transmission; determine the energy charging level at which the device with wireless energy charging capability is triggered to send the beacon, wherein the estimated time is based on the expected wireless energy charging rate and the energy charging level.

[0184] Clause 25. The asset tracking coordination assembly of any of Clauses 22 to 24, wherein the scanning device comprises the asset tracking coordination assembly.

[0185] Clause 26. The asset tracking coordination assembly of any of Clauses 22 to 25, wherein the scanning device is distinct from the asset tracking coordination assembly.

[0186] Clause 27. The asset tracking coordination assembly of Clause 26, wherein the scanning device is closer to the wireless energy charging capable device than the asset tracking coordination assembly.

[0187] Clause 28. The asset tracking coordination component of any of clauses 26-27, wherein the scheduling comprises sending an indication of the beacon scanning window to the scanning device.

[0188] Clause 29. The asset tracking coordination assembly of any of clauses 22 to 28, wherein the scanning device is separate from the wireless energy source.

[0189] Item 30. A scanning device, comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive a request from an asset tracking coordination component via the at least one transceiver to perform an asset scan in conjunction with a wireless energy transmission from the scanning device; perform the wireless energy transmission in response to the request; monitor one or more beacon transmissions from one or more devices with wireless energy charging capabilities of one or more assets within a threshold proximity coupled to the scanning device in response to the request during a beacon scanning window based on the wireless energy transmission; and send scanning result information to the asset tracking coordination component based on the monitoring via the at least one transceiver.

[0190] Clause 31. A scanning device as described in clause 30, wherein the asset tracking coordination component corresponds to an electronic shelf label (ESL) scanning device controller, and wherein the one or more devices with wireless energy charging capabilities correspond to one or more passive Bluetooth low energy (BLE) tags.

[0191] Clause 32. The scanning device of any one of clauses 30 to 31, wherein the scanning device comprises the asset tracking coordination component.

[0192] Clause 33. The scanning device of any of clauses 30 to 32, wherein the scanning device is distinct from the asset tracking coordination component.

[0193] Clause 34. The scanning device of clause 33, wherein the scanning device is closer to the one or more wireless energy charging capable devices than the asset tracking coordination component.

[0194] Clause 35. The scanning device of any of clauses 33 to 34, wherein the at least one processor is further configured to: receive an indication of the beacon scanning window from the asset tracking coordination component via the at least one transceiver.

[0195] Item 36. An asset tracking coordination component, comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: send a request to a scanning device via the at least one transceiver to perform an asset scan in combination with wireless energy transmissions from the scanning device, the asset scan comprising monitoring one or more beacon transmissions from one or more devices with wireless energy charging capabilities of one or more assets within a threshold proximity coupled to a wireless energy source during a beacon scanning window based on the wireless energy transmissions; and receive scanning result information from the wireless energy source based on the monitoring via the at least one transceiver.

[0196] Clause 37. The asset tracking coordination component of Clause 36, wherein the beacon scan window is determined based on one or more estimated times of one or more beacon transmissions from the one or more wireless energy charging capable devices.

[0197] Clause 38. An asset tracking coordination component as described in any of clauses 36 to 37, wherein the asset tracking coordination component corresponds to an electronic shelf label (ESL) scanning device controller, and wherein the one or more devices with wireless energy charging capabilities correspond to one or more passive Bluetooth low energy (BLE) tags.

[0198] Clause 39. The asset tracking coordination assembly of any of clauses 36 to 38, wherein the scanning device comprises the asset tracking coordination assembly.

[0199] Clause 40. The asset tracking coordination assembly of any of Clauses 36 to 39, wherein the scanning device is remote from the asset tracking coordination assembly.

[0200] Clause 41. The asset tracking coordination assembly of clause 40, wherein the scanning device is closer to the one or more wireless energy charging capable devices than the asset tracking coordination assembly.

[0201] Clause 42. The asset tracking coordination component of Clause 41, wherein the at least one processor is further configured to: send an indication of the beacon scanning window to the scanning device via the at least one transceiver.

[0202] Item 43. An asset tracking coordination component comprising: a component for estimating a distance between a wireless energy source and a scanning device; a component for determining timing information associated with wireless energy transmissions from the wireless energy source; a component for estimating the time of a beacon transmission from a device with wireless energy charging capability coupled to an asset within a threshold proximity of the scanning device based on the estimated distance and the timing information; and a component for scheduling a beacon scanning window for the scanning device to scan for the beacon transmission based on the estimated time.

[0203] Clause 44. The asset tracking coordination component of clause 43, wherein the asset tracking coordination component corresponds to an electronic shelf label (ESL) scanning device controller, and wherein the device having wireless energy charging capability corresponds to a passive Bluetooth Low Energy (BLE) tag.

[0204] Clause 45. An asset tracking coordination component according to any one of clauses 43 to 44, further comprising: a component for determining an expected wireless energy charging rate associated with the device with wireless energy charging capability in a candidate location area based on the distance, the power of the wireless energy transmission, and the frequency associated with the wireless energy transmission; and a component for determining an energy charging level at which the device with wireless energy charging capability is triggered to send the beacon transmission, wherein the estimated time is based on the expected wireless energy charging rate and the energy charging level.

[0205] Clause 46. The asset tracking coordination assembly of any of clauses 43 to 45, wherein the scanning device comprises the asset tracking coordination assembly.

[0206] Clause 47. The asset tracking coordination assembly of any of Clauses 43 to 46, wherein the scanning device is distinct from the asset tracking coordination assembly.

[0207] Clause 48. The asset tracking coordination assembly of Clause 47, wherein the scanning device is closer to the wireless energy charging capable device than the asset tracking coordination assembly.

[0208] Clause 49. The asset tracking coordination component of any of clauses 47-48, wherein the scheduling comprises sending an indication of the beacon scanning window to the scanning device.

[0209] Clause 50. The asset tracking coordination assembly of any of clauses 43 to 49, wherein the scanning device is separate from the wireless energy source.

[0210] Item 51. A scanning device comprising: a component for receiving a request from an asset tracking coordination component to perform an asset scan in conjunction with a wireless energy transmission from the scanning device; a component for performing the wireless energy transmission in response to the request; a component for monitoring one or more beacon transmissions from one or more devices with wireless energy charging capabilities of one or more assets coupled to the scanning device within a threshold proximity in response to the request during a beacon scanning window based on the wireless energy transmission; and a component for sending scan result information to the asset tracking coordination component based on the monitoring.

[0211] Clause 52. A scanning device as described in clause 51, wherein the asset tracking coordination component corresponds to an electronic shelf label (ESL) scanning device controller, and wherein the one or more devices with wireless energy charging capabilities correspond to one or more passive Bluetooth low energy (BLE) tags.

[0212] Clause 53. The scanning device of any one of clauses 51 to 52, wherein the scanning device comprises the asset tracking coordination component.

[0213] Clause 54. The scanning device of any of clauses 51 to 53, wherein the scanning device is distinct from the asset tracking coordination component.

[0214] Clause 55. The scanning device of clause 54, wherein the scanning device is closer to the one or more wireless energy charging capable devices than the asset tracking coordination component.

[0215] Clause 56. The scanning device of any of clauses 54 to 55, further comprising means for receiving an indication of the beacon scan window from the asset tracking coordination component.

[0216] Item 57. An asset tracking coordination component, comprising: a component for sending a request to a scanning device to perform an asset scan in combination with wireless energy transmissions from the scanning device, the asset scan comprising monitoring one or more beacon transmissions from one or more wireless energy charging capable devices of one or more assets within a threshold proximity coupled to a wireless energy source during a beacon scanning window based on the wireless energy transmissions; and a component for receiving scan result information from the wireless energy source based on the monitoring.

[0217] Clause 58. The asset tracking coordination component of Clause 57, wherein the beacon scan window is determined based on one or more estimated times of one or more beacon transmissions from the one or more wireless energy charging capable devices.

[0218] Clause 59. An asset tracking coordination component as described in any of clauses 57 to 58, wherein the asset tracking coordination component corresponds to an electronic shelf label (ESL) scanning device controller, and wherein the one or more devices with wireless energy charging capabilities correspond to one or more passive Bluetooth low energy (BLE) tags.

[0219] Clause 60. The asset tracking coordination assembly of any of Clauses 57 to 59, wherein the scanning device comprises the asset tracking coordination assembly.

[0220] Clause 61. The asset tracking coordination assembly of any of clauses 57 to 60, wherein the scanning device is remote from the asset tracking coordination assembly.

[0221] Clause 62. The asset tracking coordination assembly of clause 61, wherein the scanning device is closer to the one or more wireless energy charging capable devices than the asset tracking coordination assembly.

[0222] Clause 63. The asset tracking coordination assembly of Clause 62, further comprising: means for sending an indication of the beacon scanning window to the scanning device.

[0223] Item 64. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by an asset tracking coordination component, cause the asset tracking coordination component to: estimate a distance between a wireless energy source and a scanning device; determine timing information associated with a wireless energy transmission from the wireless energy source; estimate a time of a beacon transmission from a device with wireless energy charging capability that is coupled to an asset within a threshold proximity of the scanning device based on the estimated distance and the timing information; and schedule a beacon scanning window for the scanning device to scan for the beacon transmission based on the estimated time.

[0224] Clause 65. The non-transitory computer-readable medium of clause 64, wherein the asset tracking coordination component corresponds to an electronic shelf label (ESL) scanning device controller, and wherein the device having wireless energy charging capability corresponds to a passive Bluetooth Low Energy (BLE) tag.

[0225] Clause 66. The non-transitory computer-readable medium of any one of clauses 64 to 65 further includes: computer executable instructions which, when executed by the asset tracking coordination component, cause the asset tracking coordination component to: determine an expected wireless energy charging rate associated with the wireless energy charging capable device in the candidate location area based on the distance, the power of the wireless energy transmission, and the frequency associated with the wireless energy transmission; determine an energy charging level at which the wireless energy charging capable device is triggered to send the beacon, wherein the estimated time is based on the expected wireless energy charging rate and the energy charging level.

[0226] Clause 67. The non-transitory computer-readable medium of any one of clauses 64 to 66, wherein the scanning device comprises the asset tracking coordination component.

[0227] Clause 68. The non-transitory computer-readable medium of any one of clauses 64 to 67, wherein the scanning device is distinct from the asset tracking coordination component.

[0228] Clause 69. The non-transitory computer-readable medium of Clause 68, wherein the scanning device is closer to the wireless energy charging capable device than the asset tracking coordination component.

[0229] Clause 70. The non-transitory computer-readable medium of any one of Clauses 68 to 69, wherein the scheduling comprises sending an indication of the beacon scanning window to the scanning device.

[0230] Clause 71. The non-transitory computer-readable medium of any one of clauses 64 to 70, wherein the scanning device is separate from the wireless energy source.

[0231] Item 72. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a scanning device, cause the scanning device to: receive a request from an asset tracking coordination component to perform an asset scan in conjunction with wireless energy transmissions from the scanning device; perform the wireless energy transmissions in response to the request; monitor one or more beacon transmissions from one or more devices with wireless energy charging capabilities of one or more assets coupled to the scanning device within a threshold proximity in response to the request during a beacon scanning window based on the wireless energy transmissions; and send scan result information to the asset tracking coordination component based on the monitoring.

[0232] Clause 73. A non-transitory computer-readable medium as described in clause 72, wherein the asset tracking coordination component corresponds to an electronic shelf label (ESL) scanning device controller, and wherein the one or more devices with wireless energy charging capabilities correspond to one or more passive Bluetooth low energy (BLE) tags.

[0233] Clause 74. The non-transitory computer-readable medium of any one of clauses 72 to 73, wherein the scanning device comprises the asset tracking coordination component.

[0234] Clause 75. The non-transitory computer-readable medium of any one of clauses 72 to 74, wherein the scanning device is distinct from the asset tracking coordination component.

[0235] Clause 76. The non-transitory computer-readable medium of Clause 75, wherein the scanning device is closer to the one or more wireless energy charging capable devices than the asset tracking coordination component.

[0236] Clause 77. The non-transitory computer-readable medium of any one of clauses 75 to 76, further comprising: computer-executable instructions that, when executed by the scanning device, cause the scanning device to: receive an indication of the beacon scan window from the asset tracking coordination component.

[0237] Item 78. A non-transitory computer-readable medium storing computer-executable instructions which, when executed by an asset tracking coordination component, cause the asset tracking coordination component to: send a request to a scanning device to perform an asset scan in conjunction with wireless energy transmissions from the scanning device, the asset scan comprising monitoring one or more beacon transmissions from one or more wireless energy charging-capable devices of one or more assets within a threshold proximity coupled to a wireless energy source during a beacon scanning window based on the wireless energy transmissions; and receive scan result information from the wireless energy source based on the monitoring.

[0238] Clause 79. The non-transitory computer-readable medium of Clause 78, wherein the beacon scan window is determined based on one or more estimated times of one or more beacon transmissions from the one or more wireless energy charging capable devices.

[0239] Clause 80. A non-transitory computer-readable medium as described in any of clauses 78 to 79, wherein the asset tracking coordination component corresponds to an electronic shelf label (ESL) scanning device controller, and wherein the one or more devices with wireless energy charging capabilities correspond to one or more passive Bluetooth low energy (BLE) tags.

[0240] Clause 81. The non-transitory computer-readable medium of any of Clauses 78 to 80, wherein the scanning device comprises the asset tracking coordination component.

[0241] Clause 82. The non-transitory computer-readable medium of any one of clauses 78 to 81, wherein the scanning device is remote from the asset tracking coordination component.

[0242] Clause 83. The non-transitory computer-readable medium of clause 82, wherein the scanning device is closer to the one or more wireless energy charging capable devices than the asset tracking coordination component.

[0243] Clause 84. The non-transitory computer-readable medium of Clause 83, further comprising: computer-executable instructions that, when executed by the asset tracking coordination component, cause the asset tracking coordination component to: send an indication of the beacon scan window to the scanning device.

[0244] Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0245] In addition, it will be appreciated by those skilled in the art that the various exemplary logic blocks, modules, circuits and algorithmic steps described in conjunction with the various aspects disclosed herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various exemplary components, frames, modules, circuits and steps have been generally described above in terms of their functions. Whether such functions are implemented as hardware or software depends on the specific application and the design constraints proposed to the entire system. Those skilled in the art can implement the described functions in different ways for each specific application, but such specific implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0246] The various illustrative logical blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.

[0247] The methods, sequences and / or algorithms described in conjunction with the various aspects disclosed herein may be directly embodied in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a random access memory (RAM), a flash memory, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium may be integral with the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). In an alternative, the processor and the storage medium may reside in a user terminal as discrete components.

[0248] In one or more example aspects, the function may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the function may be stored on a computer-readable medium or sent via a computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. The storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM, or other optical disk storage devices, disk storage devices, or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer. Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of the medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0249] Although the foregoing disclosure illustrates exemplary aspects of the present disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the present disclosure as defined by the appended claims. In addition, the functions, steps and / or actions of the method claims according to the various aspects of the present disclosure described herein do not need to be performed in any particular order. In addition, although the elements of the present disclosure may be described or claimed in the singular, the plural form may also be considered unless explicitly stated to be limited to the singular.

Claims

1. A method of operating an asset tracking coordination component, comprising: estimating the distance between the wireless energy source and the scanning device; determining timing information associated with transmission of wireless energy from the wireless energy source; estimating a time of beacon transmission from a device having wireless energy charging capability coupled to an asset within a threshold proximity of the scanning device based on the estimated distance and the timing information; as well as A beacon scanning window is scheduled for the scanning device to scan for the beacon transmission based on the estimated time.

2. The method according to claim 1, wherein the asset tracking coordination component corresponds to an electronic shelf label (ESL) scanning device controller, and The device having wireless energy charging capability corresponds to a passive Bluetooth Low Energy (BLE) tag.

3. The method according to claim 1, further comprising: determining an expected wireless energy charging rate associated with the wireless energy charging capable device in a candidate location area based on the distance, the power of the wireless energy transmission, and a frequency associated with the wireless energy transmission; as well as determining an energy charging level at which the wireless energy charging capable device is triggered to send the beacon, Wherein the estimated time is based on the expected wireless energy charging rate and the energy charging level. The method of claim 1 , wherein the scanning device comprises the asset tracking coordination component. The method of claim 1 , wherein the scanning device is distinct from the asset tracking coordination component.

6. The method of claim 5, wherein the scanning device is closer to the wireless energy charging capable device than the asset tracking coordination component.

7. The method of claim 5, wherein the scheduling comprises sending an indication of the beacon scanning window to the scanning device. The method of claim 1 , wherein the scanning device is separate from the wireless energy source.

9. A method of operating a scanning device, comprising: receiving, from the asset tracking coordination component, a request to perform an asset scan in conjunction with wireless energy transmission from the scanning device; performing the wireless energy transmission in response to the request; monitoring, in response to the request during a beacon scanning window based on the wireless energy transmission, one or more beacon transmissions from one or more wireless energy charging capable devices coupled to one or more assets within a threshold proximity of the scanning device; as well as Scan result information is sent to the asset tracking coordination component based on the monitoring.

10. The method according to claim 9, wherein the asset tracking coordination component corresponds to an electronic shelf label (ESL) scanning device controller, and The one or more devices having wireless energy charging capability correspond to one or more passive Bluetooth Low Energy (BLE) tags.

11. The method of claim 9, wherein the scanning device comprises the asset tracking coordination component.

12. The method of claim 9, wherein the scanning device is distinct from the asset tracking coordination component.

13. The method of claim 12, wherein the scanning device is closer to the one or more wireless energy charging capable devices than the asset tracking coordination component.

14. The method according to claim 12, further comprising: An indication of the beacon scan window is received from the asset tracking coordination component.

15. A method of operating an asset tracking coordination component, comprising: sending a request to a scanning device to perform an asset scan in conjunction with wireless energy transmissions from the scanning device, the asset scan comprising monitoring one or more beacon transmissions from one or more wireless energy charging capable devices of one or more assets coupled to a threshold proximity of a wireless energy source during a beacon scan window based on the wireless energy transmissions; as well as Scan result information is received from the wireless energy source based on the monitoring.

16. The method of claim 15, wherein the beacon scan window is determined based on one or more estimated times of one or more beacon transmissions from the one or more wireless energy charging capable devices.

17. The method according to claim 15, wherein the asset tracking coordination component corresponds to an electronic shelf label (ESL) scanning device controller, and The one or more devices having wireless energy charging capability correspond to one or more passive Bluetooth Low Energy (BLE) tags.

18. The method of claim 15, wherein the scanning device comprises the asset tracking coordination component.

19. The method of claim 15, wherein the scanning device is remote from the asset tracking coordination component.

20. The method of claim 19, wherein the scanning device is closer to the one or more wireless energy charging capable devices than the asset tracking coordination component.

21. The method according to claim 20, further comprising: An indication of the beacon scan window is sent to the scanning device.

22. An asset tracking coordination component comprising: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: estimating the distance between the wireless energy source and the scanning device; determining timing information associated with transmission of wireless energy from the wireless energy source; estimating a time of beacon transmission from a device having wireless energy charging capability coupled to an asset within a threshold proximity of the scanning device based on the estimated distance and the timing information; as well as A beacon scanning window is scheduled for the scanning device to scan for the beacon transmission based on the estimated time.

23. The asset tracking coordination component of claim 22, wherein the asset tracking coordination component corresponds to an electronic shelf label (ESL) scanning device controller, and The device having wireless energy charging capability corresponds to a passive Bluetooth Low Energy (BLE) tag.

24. The asset tracking coordination component of claim 22, wherein the at least one processor is further configured to: determining an expected wireless energy charging rate associated with the wireless energy charging capable device in a candidate location area based on the distance, the power of the wireless energy transmission, and the frequency associated with the wireless energy transmission; and determining an energy charging level at which the wireless energy charging capable device is triggered to send the beacon, Wherein the estimated time is based on the expected wireless energy charging rate and the energy charging level.

25. The asset tracking coordination assembly of claim 22, wherein the scanning device comprises the asset tracking coordination assembly.

26. The asset tracking coordination assembly of claim 22, wherein the scanning device is distinct from the asset tracking coordination assembly.

27. The asset tracking coordination assembly of claim 26, wherein the scanning device is closer to the wireless energy charging capable device than the asset tracking coordination assembly.

28. The asset tracking coordination component of claim 26, wherein the scheduling includes sending an indication of the beacon scanning window to the scanning device.

29. The asset tracking coordination assembly of claim 22, wherein the scanning device is separate from the wireless energy source.

Images