Wireless power transmission system encoding beacon signals in a wireless power delivery environment

Abstract

A wireless power transmission system is provided for encoding (462, 526) a beacon signal in a wireless power delivery environment. The wireless power transmission system is used to encode a beacon signal to isolate a client device (546) for wireless (550) power delivery in a wireless power delivery environment. The beacon signal can be encoded or modulated (462) with a transmission code provided (524) to a selected client in the wireless power delivery environment. In this way, the beacon signal from the selected client can be identified and the corresponding client device is isolated for wireless power delivery (544, 546). In some embodiments, the transmission code can be a pseudo-random sequence used by the wireless power delivery client to encode the transmitted beacon signal.

Description

[0001] This application is a divisional application of the application patent application entitled "Techniques for Encoding Beacon Signals in Wireless Power Delivery Environments" having application number 201580075112.6 and filing date December 2, 2015.

[0002] Cross Reference to Related Applications

[0003] This application claims priority to and the benefit of U.S. Provisional Patent Application Serial No. 62 / 086,481 entitled "TECHNIQUES FOR IDENTIFYING CLIENTS AND CHARGERS IN WIRELESS POWER ENVIRONMENTS" and filed on December 2, 2014, which is expressly incorporated by reference herein. BACKGROUND

[0004] Signaling between wireless chargers and client devices in a wireless power delivery environment can be challenging. For example, a client device can periodically transmit a beacon signal or other signaling to a wireless charger so that the wireless charger can explicitly direct wireless power to the client device. Unfortunately, when multiple client devices are present in the same environment, the wireless charger can inadvertently direct power to an unauthorized or incorrect wireless device. That is, the wireless charger can inadvertently lock onto an unauthorized transmission source (e.g., another wireless device or other transmitter) that is transmitting at the same frequency as the wireless device, causing wireless power to be directed to the unauthorized transmission source instead of the intended wireless device.

[0005] Accordingly, there is a need for techniques that overcome the above-mentioned problems, as well as techniques that provide additional benefits. Some embodiments of existing or related systems provided herein and their associated limitations are intended to be illustrative and not exclusive. Other limitations of the current or existing systems will become apparent to those of skill in the art upon reading the following Detailed Description. BRIEF DESCRIPTION OF DRAWINGS

[0006] One or more embodiments of the application, together with modifications and alternative forms thereof, are shown by way of example in the accompanying drawings, in which like reference numerals indicate similar elements, and in which:

[0007] Figure 1 A block diagram illustrating an example wireless power delivery environment is depicted, depicting isolated wireless power delivery from one or more wireless chargers to different wireless devices within the wireless power delivery environment.

[0008] Figure 2A sequence diagram illustrating example operations for initiating isolated wireless power delivery between a wireless charger and a wireless receiver device, according to some implementation schemes, is depicted.

[0009] Figure 3 A block diagram illustrating example components of a wireless power transmitter (charger or wireless power delivery system) according to some embodiments is depicted.

[0010] Figure 4 A block diagram illustrating example components of a wireless power receiver (client) according to some implementation schemes is depicted.

[0011] Figures 5A to 5C A flowchart illustrating an example process for encoding beacon signals for isolating power receiver clients from wireless power delivery, according to some implementations, is depicted.

[0012] Figure 6 and Figure 7 This is a signaling diagram illustrating example transport scheduling according to some implementation schemes.

[0013] Figure 8 A block diagram is depicting example components of a representative mobile device or tablet computer in the form of a mobile (or smartphone) or tablet computer device having a wireless power receiver or client, according to some embodiments.

[0014] Figure 9 The illustration depicts a machine of an example form of a computer system, in which a set of instructions can be executed to cause the machine to perform any or more of the methods discussed herein. Detailed Implementation

[0015] The following description and figures are illustrative and should not be construed as limiting. Numerous specific details are described to provide a thorough understanding of this disclosure. However, in some cases, well-known or conventional details have not been described to avoid obscuring the specification. Reference to one or more embodiments of this disclosure may, but is not necessarily, to the same embodiment; and such reference indicates at least one of the embodiments.

[0016] In this specification, references to "an embodiment" or "an implementation" mean that a specific feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment of this disclosure. The phrase "in an embodiment" appearing in different places in the specification does not necessarily refer to the same embodiment in all cases, nor is it a single or alternative embodiment that is mutually exclusive with other embodiments. Furthermore, various features that may be exhibited by some embodiments but not by other embodiments are described. Similarly, different requirements that may be required by some embodiments but not by other embodiments are described.

[0017] The terms used in this specification generally have their ordinary meanings in the context of the present disclosure and in the context of the specific terms used in the particular circumstances. Some terms are discussed below or elsewhere in the specification to provide additional guidance to the practitioner regarding the descriptions of the present disclosure. Certain terms are highlighted as, for example, boldface type and / or quotation marks for the convenience of the reader. The use of highlighting and / or quotation marks has no influence on the scope and meaning of a term. The scope and meaning of a term should be understood consistent with the context of its usage and the relevant art, and any terms in the description that seem singular or specifically plural are understood to include the singular and / or plural aspect, as appropriate. It will be further understood that like terms can be expressed differently depending on the particular context.

[0018] Accordingly, alternative language and synonyms can be used for any one or more of the terms discussed herein, and no special significance should be placed upon whether or not a term is recited or discussed in particular source, or not. Synonyms for certain terms are provided. A recital of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification, including examples of any terms discussed herein, is illustrative only, and in no way limits the scope and meaning of the disclosure or of any exemplified term. Likewise, the disclosure is not limited to various embodiments given in this specification.

[0019] Without intent to limit the scope of the disclosure, examples of instruments, apparatus, methods and their related results according to the embodiments of the present disclosure are given below. Note that these examples are only representative and are not intended to limit or restrict the scope of the disclosure in any way. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. In case of conflict, the present document, including definitions, will control.

[0020] Embodiments of the present disclosure describe techniques for encoding beacon signals in a wireless power delivery environment. More specifically, techniques are disclosed for encoding beacon signals to isolate a client device for wireless power delivery in a wireless power delivery environment. The beacon signal can be encoded or modulated with a transmission code that is provided to a selected client in the wireless power delivery environment. In this way, the beacon signal from the selected client can be identified and the corresponding client device is isolated for wireless power delivery. In some embodiments, the transmission code can be a pseudo-random sequence used by the wireless power delivery client to encode the transmitted beacon signal.

[0021] In some embodiments, the same transmission code is used for all clients (the transmission code is unique to the charger). In other embodiments, a different transmission code is provided to each client or communication path. As discussed with reference to Figure 7 As discussed in greater detail, different transmission codes for each client can facilitate the clients transmitting beacon signaling at or near the same time in a wireless power delivery environment, further ensuring that only authorized (selected) clients are "locked" by the wireless power delivery system.

[0022] In some embodiments, among other things, the techniques illustrated herein enable precise identification and tracking (e.g., "locking") of clients by a charger in a wireless power delivery environment. This precise identification prevents locking to an unauthorized source.

[0023] By way of example and not limitation, the beacon coding techniques described herein can be used in various industrial applications, military applications, counter-terrorism applications, energy conservation applications, environmental quality and medical applications, etc. that can require more than one charger to deliver power in the same environment without interference and to identify many authorized wireless devices.

[0024] Figure 1 is a diagram illustrating an example wireless power delivery environment 100 depicting isolated wireless power delivery from one or more wireless chargers 101 to different wireless devices 102 within the wireless power delivery environment 100. More specifically, Figure 1 An example wireless power delivery environment 100 is illustrated in which wireless power and / or data can be delivered to available wireless devices 102.1-102.n having one or more power receiver clients 103.1-103.n (also referred to herein as "wireless power receivers" or "wireless power clients"). The wireless power receivers are configured to receive isolated wireless power from one or more wireless chargers 101.

[0025] As shown in the embodiments of Figure 1 Wireless devices 102.1-102.n are mobile phone devices 102.2 and 102.n and a wireless game controller 102.1, respectively, however wireless devices 102.1-102.n can be any (smart or non-smart) wireless device or system that requires power and is capable of receiving wireless power via one or more integrated power receiver clients 103.1-103.n. As discussed herein, the one or more integrated power receiver clients or "wireless power receivers" receive and process power from one or more transmitters / chargers 101.a-101.n and provide power for operation of wireless devices 102.1-102.n.

[0026] Each charger 101 (also referred to herein as a "transmitter," "antenna array," or "antenna array system") can include a plurality of antennas 104, e.g., an antenna array including hundreds or thousands of antennas, capable of delivering wireless power to a wireless device 102. In some embodiments, the antennas are adaptive phased radio frequency antennas. The charger 101 is capable of determining the appropriate phases to deliver a coherent power transmission signal to the power receiver client 103. The array is configured to emit a signal (e.g., a continuous wave or pulsed power transmission signal) from a plurality of antennas that are at a particular phase relative to each other. It is to be understood that the use of the term "array" does not necessarily limit the antenna array to any particular array structure. That is, the antenna array need not be constructed in a particular "array" form or geometry. Furthermore, the term "array" or "array system" as used herein can include associated and peripheral circuitry for signal generation, reception, and transmission, such as radios, digital logic, and modems. In some embodiments, the charger 101 can have an embedded Wi-Fi hub.

[0027] The wireless device 102 can include one or more receive power clients 103. As shown in the embodiment of FIG. 1, power delivery antennas 104a and data communication antennas 104b are shown. The power delivery antennas 104a are configured to provide delivery of wireless radio frequency power in a wireless power delivery environment. The data communication antennas are configured to transmit and receive data communications to and from the power receiver clients 103.1-103.n and / or the wireless device 102.1-102.n. In some embodiments, the data communication antennas can communicate via Bluetooth, Wi-Fi, Zigbee, etc. Figure 1

[0028] Each power receiver client 103.1-103.n includes one or more antennas (not shown) for receiving signals from the charger 101. Likewise, each charger 101.a-101.n includes an antenna array having one or more antennas and / or groups of antennas capable of emitting a continuous wave signal at a particular phase relative to each other. As discussed above, each array is capable of determining the appropriate phase for delivering a coherent signal to the power receiver client 102.1-102.n. For example, the coherent signal can be determined by calculating the complex conjugate of a beacon signal received at each antenna of the array such that the phase of the coherent signal is appropriately adjusted for the particular power receiver client that sent the beacon signal.

[0029] ​Although not shown, each component of the environment, such as the wireless power receivers, chargers, etc., can include a control and synchronization mechanism, such as a data communication synchronization module. The chargers 101.a-101.n can be connected to a power source, such as, for example, a power outlet or power source that connects the charger to a standard or main alternating current (AC) power supply in a building. Alternatively or additionally, one or more of the chargers 101.a-101.n can be powered by a battery or via other mechanisms.

[0030] In some embodiments, the power receiver clients 102.1-102.n and / or the chargers 101.a-101.n utilize a reflective object 106, such as, for example, a wall or other RF-reflective obstacle, that is within range of transmitting beacon signals and / or receiving wireless power and / or data within the wireless power delivery environment. The reflective object 106 can be used for multi-directional signal communication, regardless of whether an obstructing object is within line of sight between the charger and the power receiver client.

[0031] As described herein, each wireless device 102.1-102.n can be any system and / or device, and / or any combination of devices / systems, that can establish a connection with another device, server, and / or other system within the example environment 100. In some embodiments, the wireless devices 102.1-102.n include a display function or other output function that presents data to a user, and / or an input function that receives data from a user. For example, the wireless devices 102 can be, but are not limited to, a video game controller; a server workstation; a desktop computer; a computer cluster; a mobile computing device, such as a notebook, laptop, handheld computer, mobile phone, smart phone, PDA, Blackberry device, Treo, and / or iPhone, etc. The wireless devices 102 can also be any wearable device, such as a watch, necklace, ring, or even a device embedded on or within a consumer's body. Other examples of wireless devices 102 include, but are not limited to, a security (e.g., fire or carbon monoxide) sensor, an electric toothbrush, an electronic door lock / handle, an electric light switch controller, an electric shaver, etc.

[0032] Although not shown in the embodiment of Figure 1 Each of the chargers 101 and the power receiver clients 103.1-103.n can include a data communication module for communicating via a data channel, although not shown in the embodiment of

[0033] Figure 2is a sequence diagram 200 showing example operations between a wireless charger 101 and a power receiver client 103 for starting isolated wireless power delivery according to an embodiment. First, communication is established between the charger 101 and the power receiver client 103. The charger 101 then sends beacon scheduling information and a transmission code to the power receiver client 103 to facilitate the power receiver client 103 encoding a beacon signal for subsequent isolated wireless power delivery by the charger. The charger 101 can also send power transmission scheduling information so that the power receiver client 103 knows when to expect wireless power from the charger. As discussed herein, the power receiver client 103 generates an encoded beacon signal using the transmission code and broadcasts the encoded beacon during a beacon transmission allocation indicated by the beacon scheduling information, e.g., a BBS period.

[0034] As shown, the charger 101 receives the beacon from the power receiver client 103 and decodes the encoded beacon signal using the transmission code provided to the client 103 to ensure that the client 103 is an authorized or selected client. The charger 101 also detects the phase (or direction) in which the beacon signal was received and, once the charger determines that the client is authorized, delivers wireless power and / or data to the power receiver client 103 based on the phase (or direction) of the received beacon. In some embodiments, the charger 101 can determine the complex conjugate of the phase and use the complex conjugate to deliver wireless power to the power receiver client 103 in the same direction (or phase) in which the beacon signal was received from the receiver client 103 and / or otherwise direct the wireless power to the power receiver client 103.

[0035] In some embodiments, the charger 101 includes a number of antennas; one or more of these antennas are used to deliver power to the power receiver client 103. The charger 101 can detect the phase in which the beacon signal is received at each antenna. The number of antennas can result in different encoded beacon signals being received at each antenna of the charger 101. The charger can then determine the complex conjugate of the beacon signal received at each antenna. Using the complex conjugate, the one or more antennas can emit a signal that takes into account the effects of the number of antennas in the charger 101. In other words, the charger 101 emits a signal from the one or more antennas in such a way that the aggregate signal created from the one or more antennas approximately reproduces the waveform of the beacon in the opposite direction.

[0036] As discussed herein, wireless power can be delivered in a power period defined by the power scheduling information. Referring now to Figure 3 More detailed embodiments of the signaling required to start wireless power delivery are described.

[0037] Figure 3is a block diagram showing example components of a wireless charger 300 according to an embodiment. As shown in Figure 3 As shown in embodiments of the present disclosure, the wireless charger 300 includes a master bus controller (MBC) board and multiple mezzanine boards that collectively make up an antenna array. The MBC includes control logic 310, an external power interface (I / F) 320, a communication block 330, and a proxy 340. The mezzanines (or antenna array boards 350) each include multiple antennas 360a-360n. Some or all of the above components can be omitted in some embodiments. Additional components are also possible.

[0038] The control logic 310 is configured to provide control and intelligence to the array components. The control logic 310 can include one or more processors, FPGAs, memory units, etc., and can direct and control various data and power communications. The communication block 330 can direct data communications on a data carrier frequency, such as a base signal clock for clock synchronization. The data communications can be Bluetooth, Wi-Fi, Purple Peak, etc. Likewise, the proxy 340 can communicate with clients via data communications as discussed herein. The data communications can be Bluetooth, Wi-Fi, Purple Peak, etc. The external power interface 320 is configured to receive external power and provide power to the various components. In some embodiments, the external power interface 320 can be configured to receive a standard external 24 volt power supply. Alternative configurations are also possible.

[0039] An embodiment of a system power cycle is now described. In this embodiment, the master bus controller (MBC) that controls the charger array first receives power from a power supply and is enabled. The MBC then enables the proxy antenna elements on the charger array and the proxy antenna elements enter a default “discovery” mode to identify available wireless receiver clients within range of the charger array. When a client is found, the antenna elements on the charger array are powered on, computed, and (optionally) calibrated.

[0040] Next, the MBC generates beacon transmission schedule information and power transmission schedule information during a scheduling process. The scheduling process includes selecting power receiver clients. For example, the MBC can select power receiver clients for power transmission and generate a beacon beat schedule (BBS) cycle and a power schedule (PS) for the selected wireless power receiver clients. Regarding Figure 6 and Figure 7 Graphical signaling representations of example BBS and PS are shown and discussed in more detail. As discussed herein, the power receiver clients can be selected based on corresponding properties and / or needs of the power receiver clients.

[0041] In some embodiments, the MBC can also identify and / or otherwise select available clients to query their status in a client query table (CQT). The clients listed in the CQT are those that are "on standby," e.g., clients that have not received a charge. The BBS and PS are computed based on important information about the clients, such as, for example, battery status, current activity / use, how long the client has until its power is depleted, priority in terms of use, etc.

[0042] The proxy AE broadcasts the BBS to all clients. As discussed herein, the BBS indicates when each client should send a beacon. Likewise, the PS indicates when and to which clients the array should send power. In accordance with the BBS and PS, each client begins to propagate its beacon and receive power from the array. The proxy can simultaneously query the client query table to check the status of other available clients. A client can exist in either the BBS or the CQT (e.g., wait list), but not both. In some embodiments, a limited number of clients (e.g., 32) can be served on the BBS and PS. Likewise, the CQT can also be limited to a number of clients (e.g., 32). Thus, for example, if more than 64 clients are within range of the charger, some of these clients will not be valid in either the BBS or the CQT. The information gathered in the previous step continuously and / or periodically updates the BBS and / or PS.

[0043] Figure 4 is a block diagram illustrating example components of a wireless power receiver (client) in accordance with some embodiments. As Figure 4 As shown in the embodiment of FIG. 4, the receiver 400 includes control logic 410, a battery 420, a communication block 430 and associated antenna 470, a power meter 440, a rectifier 450, a combiner 455, a beacon signal generator 460, a beacon encoding unit 462 and associated antenna 480, and a switch 465 connecting the rectifier 450 or the beacon signal generator 460 to one or more associated antennas 490a-n. Some or all of the above components can be omitted in some embodiments. For example, in some embodiments, the wireless power receiver client does not include its own antenna, but rather utilizes and / or otherwise shares one or more antennas of the wireless device in which it is embedded (e.g., a Wi-Fi antenna). Additional components are also possible.

[0044] In the case where the receiver 400 has more than one antenna, a combiner 455 receives and combines the power transfer signals received from the power transmitter. The combiner can be any combiner or divider circuit configured to achieve isolation between output ports while maintaining matching conditions. For example, the combiner 455 can be a Wilkinson power divider circuit. The rectifier 450 receives the combined power transfer signal, if any, from the combiner 455, which is fed through the power meter 440 to the battery 420 for charging. The power meter 440 measures the received power signal strength and provides this measurement to the control logic 410.

[0045] The control logic 410 can also receive the battery power level from the battery 420 itself. The control logic 410 can also send / receive data signals via the communication block 430 on a data carrier frequency, such as a base signal clock used for clock synchronization. The beacon signal generator 460 generates a beacon signal or calibration signal, which is transmitted using the antenna 480 or 490 after the beacon signal is encoded.

[0046] It can be noted that while the battery 420 is shown as being charged and providing power to the receiver 400, the receiver can also receive power directly from the rectifier 450. This can be in addition to the rectifier 450 providing a charging current to the battery 420, or as an alternative to providing charging. Also, it can be noted that the use of multiple antennas is one implementation, and the structure can be reduced to one shared antenna.

[0047] In some embodiments, the client identifier (ID) module 415 stores a client ID that can uniquely identify a power receiver client in a wireless power delivery environment. For example, the ID can be transmitted to one or more chargers when a communication is established. In some embodiments, the power receiver client is also able to receive and identify other power receiver clients in the wireless power delivery environment based on the client ID.

[0048] Optional motion sensor 495 can detect motion and signal control logic 410 to act accordingly. For example, when a device is receiving high frequency power, e.g., above 500 MHz, its location can become a (incoming) hotspot of radiation. Thus, when the device is on a person, e.g., embedded in a mobile device, the radiation level can exceed the acceptable radiation level set by the Federal Communications Commission (FCC) or other medical / industry agency. To avoid any potential radiation issues, the device can integrate a motion detection mechanism, such as an accelerometer or equivalent mechanism. Once the device detects that the device is in motion, it can be assumed that the device is being held by a user and a signal to the array will be triggered to stop transmitting power to the device or to reduce the received power to an acceptable power fraction. In cases where the device is used in a moving environment, such as a car, train, or airplane, etc., it can only be possible to transmit power intermittently or at a reduced level unless the device is close to losing all available power.

[0049] Figures 5A to 5C A flowchart illustrating an example process 500 for encoding a beacon signal to isolate a power receiver client for wireless power delivery in accordance with some embodiments is depicted. Among other functions, a wireless device with an embedded wireless power receiver client and a wireless power delivery system can perform corresponding steps of the example process 500. The wireless power delivery system can be a wireless charger or a component of a wireless charger, such as Figure 1 the wireless charger 101 of Figure 3 the wireless charger 300 of Figure 3 and / or a control logic, such as the control logic 310 of Figure 1 the wireless power receiver 103 of Figure 4 the wireless power receiver client 400 of

[0050] First, at step 510A and step 510B, communication is established between the wireless power receiver client and the wireless power delivery system. As discussed above, in some embodiments, the wireless power delivery system can enter a default "discovery" mode to identify available wireless power receiver clients within range of the charger. When a client is found, the antenna elements on the charger array are powered on, computed, and (optionally) calibrated. Communication with the wireless power receiver client can be on one or more of the multiple antennas of the wireless power delivery system. In some embodiments, a single antenna is used to establish communication with the wireless power receiver client.

[0051] Once communication is established between the wireless power receiver client and the wireless power delivery system, at step 512, the wireless power receiver client collects client-specific information and sends it to the wireless power delivery system. As discussed above, the client-specific information can include various properties and / or requirements corresponding to the power receiver client or the wireless device in which the power receiver client is embedded. For example, the client-specific information can include, but is not limited to, a battery level of the wireless device in which the power receiver client is embedded, a battery level of the power receiver client, battery usage information, temperature information, etc. As discussed herein, the temperature information can include a current temperature of the wireless device or the wireless power receiver, or an ambient temperature of the wireless device or the wireless power receiver.

[0052] At step 514, the wireless power delivery system (e.g., charger) receives the client-specific information of the available wireless power receiver clients within the range of the wireless power delivery system. Once the client-specific information is received, at step 516, the wireless power delivery system determines and / or otherwise identifies additional information about the wireless power receiver clients. The additional information can be any information that the wireless power delivery system can gather or otherwise obtain from the clients. For example, the wireless power delivery system can determine a distance or range between the clients and the wireless power delivery system based on a received signal strength indication (RSSI). The RSSI can be measured by the wireless power delivery system or measured and received from the clients. The RSSI can also be an indicator of efficiency. Other distance determination methods are also possible. Further, it is to be understood that the additional information can include other information obtained by the wireless power delivery system.

[0053] At step 518, the wireless power delivery system generates the transmission schedule information based on various predetermined priorities that can be factored into the client-specific information, as well as other information gathered by the wireless power delivery system, such as the distance from the wireless power delivery system. As discussed above, generating the transmission schedule information can include selecting a set of available wireless power receiver clients (or a subset thereof) within the range of the wireless power delivery system, and generating the beacon transmission schedule information and the power delivery schedule information for the selected set of wireless power receiver clients. The beacon transmission schedule information can include a BBS period. The power delivery schedule information can include a power schedule (PS) for the selected wireless power receiver clients.

[0054] At step 520, the wireless power delivery system identifies and / or otherwise selects a transmission code information. In some embodiments, the transmission code can comprise a pseudo-random sequence that is used by the client to modulate the beacon signal such that the wireless power delivery system can identify and / or otherwise isolate the client device for wireless power delivery. As discussed herein, a unique transmission code can be selected for each wireless device that is scheduled to receive wireless power. Alternatively, a transmission code that is unique to a particular wireless power delivery system can be selected. Once selected, at step 522, the wireless power delivery system transmits the transmission schedule information and the transmission code to the wireless power receiver client.

[0055] At step 524, the wireless power receiver client receives the transmission schedule information and the transmission code, and at step 526, the wireless power receiver client encodes the beacon signal based on the transmission code. It is to be understood that various modulation schemes can be used to encode the beacon signal, such schemes including, but not limited to, frequency shift keying, amplitude shift keying, phase shift keying, quadrature modulation schemes, multi-ary modulation schemes, and the like. For purposes of illustration, the embodiments described herein primarily discuss encoding the beacon signal using phase shift keying or other phase modulation techniques. Phase shift keying is a digital modulation scheme that transmits data by changing or modulating the phase of a reference signal (carrier). In some embodiments, the beacon signal is changed or modulated based on a pseudo-random sequence (or transmission code).

[0056] For example, the sequence can comprise binary numbers, where each "1" in the sequence corresponds to a certain predetermined degree of phase shift. The predetermined degree of phase shift can be defined by the wireless power delivery system and communicated to the wireless power receiver client during initial communication. Alternatively, the predetermined degree of phase shift can be otherwise predefined and / or hard-coded in the device or embedded power receiver client. Likewise, in this embodiment, each "0" in the sequence can correspond to a zero degree phase shift of that particular portion of the signal. For example, if the pseudo-random sequence is "101010110...1", the wireless power receiver client can phase shift the beacon that the wireless power receiver client broadcasts in a manner that matches the sequence. This allows the charger to identify the client and proceed with wireless power delivery as shown in the following sections.

[0057] In some embodiments, encoding the beacon signal comprises phase modulating or phase shifting the beacon signal. Phase modulation is a modulation pattern that encodes information as a change in the instantaneous phase of a carrier wave. For example, after receiving the pseudo-random sequence sent by the charger, the selected wireless receiver can phase modulate the beacon signal based on the pseudo-random sequence.

[0058] For example, if the pseudo-random sequence (referred to as the modulation or message signal) is represented by m(t), and the carrier wave onto which the signal is modulated is c(t) = Ac sin(ω c t+φ c ), then the modulated signal can be represented as y(t) = A c sin(ω c t+m(t)+φ c ).

[0059] As discussed above, various modulation or encoding schemes - including combinations or variations thereof - can be used to encode the beacon signal.

[0060] At step 528, the wireless power receiver client processes the transmission schedule information to identify the beacon transmission allocation assigned to the wireless power receiver client, and at decision step 532, the wireless power receiver client monitors for the assigned beacon period. If the beacon period is detected, at step 534, the wireless power receiver client transmits the encoded beacon signal to the wireless power transmission system, and at decision step 538, the wireless power receiver client monitors for the assigned power period. If the client device determines that its power period is due, the client device will listen or otherwise wait to receive power during that period. In some embodiments, the client device can conserve power by only "listening" during its prescribed power period.

[0061] At step 540, the wireless power delivery system receives the encoded beacon signal, and at step 542, the wireless power delivery system decodes the beacon signal. For example, if the beacon signal is phase modulated, the beacon signal is demodulated at step 542. At step 544, the wireless power delivery system measures the phase of the received beacon signal. For example,

[0062] At step 546, the wireless power delivery system determines the relative location of the power receiver client within the wireless power delivery environment based at least in part on the measured phase. As discussed herein, the power receiver client can be tracked by the wireless power delivery environment based on the beacon signal transmitted periodically on a BBS basis. Authorized clients embed a transmission code into their beacon such that the wireless power delivery system does not confuse them with unauthorized devices, such as illegal devices transmitting at the same frequency as the authorized client devices but not currently selected for wireless power delivery, or interferers such as another charger, Wi-Fi router, etc. Additionally, in some embodiments, if authorized clients embed a code on their beacon, the wireless power delivery system can identify the location of interferers such as unauthorized transmitters and avoid locking to these interferers. In some embodiments, the charger can track the location of interferers to ensure that they are not confused with authorized transmitters.

[0063] At decision step 548, the wireless power delivery system determines whether the power period for a particular wireless power receiver client is valid, and if so, at step 550, the wireless power delivery system transmits a coherent power signal to the wireless power delivery client during the power period as described herein. Finally, at step 552, the wireless power receiver client receives the power signal, and at step 554, processes the power to charge one or more batteries as described herein.

[0064] Figure 6 is a signaling diagram illustrating an example transmission schedule 600 for a plurality of power receiver clients #1-N and a wireless power delivery system in a wireless power delivery environment, according to some embodiments. The example transmission schedule 600 involves the use of a single pseudo-random sequence. While a single charger is illustrated in the embodiment of Figure 6 While a single charger is illustrated in the embodiment of

[0065] As illustrated in the embodiment of Figure 6 As illustrated in the embodiment of

[0066] As discussed above, communication is first established between a wireless power delivery system ("charger") and individual power receiver clients #1-#N in a wireless power delivery environment. The wireless power delivery system then generates transmission schedule information, which can include beacon schedule information and power schedule information. The beacon schedule information can include a "beacon beat frequency schedule." The BBS schedules and organizes power delivery / beacon broadcasting between the charger and clients in the environment. As discussed herein, if there are more than a threshold number of devices (e.g., thirty) in the wireless power delivery environment, the generation of the transmission schedule can include a selection of devices. Additionally, one or more devices can be listed on a "waiting list."

[0067] Once the transmission schedule information is generated, the wireless power delivery system provides the transmission schedule information and a transmission code, e.g., a pseudo-random sequence, to the power receiver clients in the wireless power delivery environment. In some embodiments, only relevant schedule information (e.g., scheduling or allocation information for a particular power receiver client) can be provided to a particular power receiver client. Alternatively, all or only a portion of the schedule information can be provided to the power receiver clients.

[0068] As discussed above, the transmission schedule information can be provided to the power receiver clients in a variety of ways. For example, the transmission schedule information can be provided to the power receiver clients via a wireless communication channel, e.g., a Bluetooth® communication channel. In some embodiments, the transmission schedule information can be provided to the power receiver clients via a wired communication channel, e.g., a USB communication channel. Figure 6In embodiments of the'1 1 1 application, the wireless power delivery system uses only one unique pseudo-random sequence, the wireless power delivery system schedules each client, e.g., #1 -#N, to broadcast the client's encoded, e.g., phase modulated, beacon at different times. This scheduling guarantees power delivery to the clients. However, when many clients, e.g., thirty or more, have to share a limited number of cycles per second, e.g., 100 cycles per second, the clients can end up with a limited number of beacons per second (in a system with 100 cycles per second, thirty clients end up with approximately three beacons per second). The limited number of cycles can potentially limit the amount of wireless power received by the devices by having the power receiver clients leave their power delivery focus for relatively long periods of time. In addition, tracking the movement of clients with fewer beacons per second can potentially result in "locking" to an unauthorized source due to the reduced granularity of the movement of the device. It should be appreciated that each system can have more or less than 100 cycles per second.

[0069] Figure 7 is another signaling diagram illustrating an example transmission schedule 700 for a plurality of power receiver clients #1 -N and a wireless power delivery system in a wireless power delivery environment, according to some embodiments. The example transmission schedule 700 involves the use of multiple pseudo-random sequences. While in the'1 1 1 application, a single charger was illustrated, it should be appreciated that a wireless power delivery environment can include multiple wireless power receiver clients. Figure 7 In embodiments of the'1 1 1 application, the wireless power delivery system uses only one unique pseudo-random sequence, the wireless power delivery system schedules each client, e.g., #1 -#N, to broadcast the client's encoded, e.g., phase modulated, beacon at different times. This scheduling guarantees power delivery to the clients. However, when many clients, e.g., thirty or more, have to share a limited number of cycles per second, e.g., 100 cycles per second, the clients can end up with a limited number of beacons per second (in a system with 100 cycles per second, thirty clients end up with approximately three beacons per second). The limited number of cycles can potentially limit the amount of wireless power received by the devices by having the power receiver clients leave their power delivery focus for relatively long periods of time. In addition, tracking the movement of clients with fewer beacons per second can potentially result in "locking" to an unauthorized source due to the reduced granularity of the movement of the device. It should be appreciated that each system can have more or less than 100 cycles per second.

[0070] Figure 7 Embodiments of the'1 1 1 application are similar to embodiments of the'1 1 1 application, except that the wireless power delivery system, e.g., the charger, issues and / or otherwise assigns a different transmission code, e.g., pseudo-random sequence, to each client to use as the client's beacon encoding scheme and its scheduled time slot to broadcast the modulated beacon. Advantageously, when a unique transmission code is used for each client, the beacon transmission schedule can direct the clients to send their encoded beacons at or near the same time. This scheme can increase the number of beacons per second that a device sends to the charger, which reduces the likelihood that the charger will inadvertently lock to an unauthorized source. Figure 6

[0071] ​Clients broadcast encoded beacons, e.g., phase-modulated beacons, with a provided transmission code (pseudo-random sequence). A wireless power delivery system, e.g., a charger, detects the phase-modulated beacons based on the assigned transmission code (e.g., pseudo-random sequence) and schedules power delivery based on a predefined power schedule that can also be provided to the clients as discussed herein. In this embodiment, the charger has a phase detection mode before each power cycle. As shown, the phase detection mode (also referred to as an encoded beacon detection mode) can be divided into chunks corresponding to individual clients. Alternatively, in some implementations, the phase can be detected by the charger simultaneously.

[0072] In some implementations, the embodiments described herein assume a precise clock alignment to within a range of parts per billion or parts per billion (ppb) variation. In some implementations, a power receiving client can therefore adjust an internal clock to align with the power delivery cycles of a charger for efficient power transmission. Alternatively or additionally, since a client transmits a tone (as part of a beacon signal) for a known duration and at a desired rate, a charger can determine whether a client's clock is fast or slow by measuring the received actual tone signal. The charger can then send an adjustment value for the client to apply to the client's system clock.

[0073] In the embodiments discussed herein, implementations can include a data communication module that can be used to coordinate events. Additionally, in some implementations, the beacon signal, which is primarily referred to herein as a continuous waveform, can alternatively or additionally take the form of a modulated signal.

[0074] Figure 8 A block diagram illustrating example components of a representative mobile device or tablet 800 in the form of a mobile (or smart) phone or tablet computer device having a wireless power receiver or client, according to an implementation, is depicted. Referring to Figure 8 Various interfaces and modules are shown, however, a mobile device or tablet need not have all of the modules or functionality to perform the functions described herein. It is understood that in many implementations, various components and / or various components are not included in the controller and / or are not necessary for the operation of the above-described class controller. For example, components such as a GPS radio, cellular radio, and accelerometer can not be included in the controller to reduce cost and / or complexity. Additionally, components such as a Bluetooth® radio and RFID transceiver and antenna can populate a printed circuit board.

[0075] A wireless power receiver client can be Figure 1 a power receiver client 103 of the class ofFigure 1 The charger 101 receives power and / or data signals.

[0076] Figure 9 FIG. 1 illustrates an example form of a machine in which an instance of the instructions to cause the machine to perform any one or more of the methodologies discussed herein can be executed.

[0077] In Figure 9 In an embodiment of the application, a computer system includes a processor, a memory, a non-volatile memory, and an interface device. Various common components (e.g., cache(s)) are omitted for simplicity. The computer system 900 is intended to illustrate a hardware device on which any of the components (and any other components described in this specification) depicted in the embodiments of the application can be implemented. For example, the computer system can be any radiating object or antenna array system. The computer system can be of any applicable known or convenient type. The components of the computer system can be coupled together via a bus or through some other known or convenient device. Figure 1 In an embodiment of the application, a computer system includes a processor, a memory, a non-volatile memory, and an interface device. Various common components (e.g., cache(s)) are omitted for simplicity. The computer system 900 is intended to illustrate a hardware device on which any of the components (and any other components described in this specification) depicted in the embodiments of the application can be implemented. For example, the computer system can be any radiating object or antenna array system. The computer system can be of any applicable known or convenient type. The components of the computer system can be coupled together via a bus or through some other known or convenient device.

[0078] The processor can be, for example, a conventional microprocessor such as an Intel Pentium microprocessor or Motorola power PC microprocessor. Those skilled in the relevant art will appreciate that the term "machine-readable (storage) medium" or "computer-readable (storage) medium" includes any type of device that is accessible by a processor.

[0079] The memory is coupled to the processor by, for example, a bus. The memory can include, for example, without limitation, a random access memory (RAM) such as dynamic RAM (DRAM) and static RAM (SRAM). The memory can be local, remote, or distributed.

[0080] The bus also couples the processor to the non-volatile storage, which can be a magnetic floppy or hard disk, a magnetic or optical disk, a CD-ROM, an EPROM, a magnetic or optical card, or another form of storage for large amounts of data. Some of this data is often written, by a direct memory access procedure, into the memory during execution of software in the computer 900. The non-volatile storage can be local, remote, or distributed. The non-volatile storage is optional because all of the available suitable data in the memory can be used to create the system. A typical computer system will usually include at least a processor, a memory, and a device that couples the memory to the processor (e.g., a bus).

[0081] Software is typically stored in non-volatile memory and / or drive units. Indeed, for large programs, even the main memory can have a large capacity. However, it is understood that any software that is loaded into the main memory is in an executable form with a form of a software program or piece of code that is ultimately loaded from or controlled by a non-transitory computer-readable medium such as storage medium. It is further understood that the software cannot be presented for loading and execution until it is received in a computer- readable medium that is loaded by a computer system. Thus, a computer-readable medium that is a software distribution package, a memory or a record on a storage medium can represent a tangible computer-readable medium that is a physical, tangible computer-readable medium.

[0082] The bus also couples the processor to a network interface device. The interface can include one or more modems or network interface cards. It will be appreciated that a modem or network interface card can be considered a part of the computer system. The interface can include an analog modem, isdn modem, cable modem, token ring interface, satellite transmission interface (e.g., "direct PC"), or other interfaces for coupling a computer system to other computer systems. The interface can include one or more input and / or output devices. Input and / or output devices can include, for example but not limited to, a keyboard, mouse or other pointing device, disk drives, printers, scanners, and other input and / or output devices, including a display device. The display device can include, for example but not limited to, a cathode ray tube (CRT), liquid crystal display (LCD), or some other applicable known or convenient display device. For simplicity, it is assumed that no interface is present between the processor and the display device. Figure 9 The controller of any of the devices described in the embodiments resides in the interface.

[0083] In operation, computer system 900 can be controlled by operating system software including a file management system, such as a disk operating system. An example of operating system software with associated file management software is the family of operating systems known as Windows® from the Microsoft Corporation of Redmond, Washington, and their associated file management systems. Another example of operating system software with associated file management software is the Linux operating system and their associated file management system. The file management system is typically stored in the non-volatile memory and / or drive unit and makes a processor execute the various acts required by the operating system to input and output data and to store data in the memory, including storing files on the non-volatile memory and / or drive unit.

[0084] ​Some portions of the detailed description can be presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, is conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

[0085] It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout the description, discussions utilizing terms such as "processing" or "computing" or "calculating" or "determining" or "displaying" or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system memories into other data similarly represented as physical quantities within the computer system memories or

[0086] The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems can be used with programs in accordance with the teachings herein, or it can prove convenient to construct more specialized apparatus to perform the methods of some embodiments. The required structure for a variety of these systems will appear from the description below. In addition, the techniques are not described with reference to any particular programming language; various embodiments can be implemented in a variety of programming languages.

[0087] In alternative embodiments, the machine operates as a standalone device or can be connected (e.g., networked) to other machines. In a networked deployment, the machine can operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.

[0088] The machine can be a server computer, a client computer, a personal computer (PC), a tablet PC, a laptop computer, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, an iPhone, a Blackberry, a processor, a telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.

[0089] Although the machine-readable medium or machine-readable storage medium is shown in the example implementation(s) as a single medium, the terms "machine-readable medium" and "machine-readable storage medium" should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) that store the one or more sets of instructions. The terms "machine-readable medium" and "machine-readable storage medium" shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by a machine and that cause the machine to perform any one or more of the methodologies of the presently disclosed technology and innovation.

[0090] Generally, routines executed to implement embodiments of the present disclosure can be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as "computer programs." The computer programs typically comprise one or more sets of instructions that when read and executed by one or more processing units or processors in a computer, cause the computer to perform operations to execute elements involving the various aspects of the present disclosure.

[0091] Furthermore, although embodiments have been described in the context of fully functioning computers and computer systems, those skilled in the art will appreciate that the various embodiments are capable of being distributed as a program product in a variety of forms, and that the present disclosure applies equally regardless of the particular type of machine or computer-readable media used to actually effect the distribution.

[0092] Other examples of machine-readable storage media, machine-readable media, or computer readable (storage) media include, but are not limited to: a recordable type medium such as a volatile memory device, and non-volatile memory device, floppy disks and other removable disks, hard disk drives, optical disks (e.g., Compact Disk Read Only Memory (CD ROMS), Digital Versatile Disks (DVDs), etc.), and transmission type media such as digital and analog communication links.

[0093] Unless the context clearly requires otherwise, throughout the description and the claims, the words "comprise," "comprising," and the like are to be construed in an inclusive sense as opposed to an exclusive or exhaustive sense; that is to say, in the sense of "including, but not limited to." As used herein, the terms "connected," "coupled," or any variant thereof, means any connection or coupling, either direct or indirect, between two or more elements; the coupling or connection between the elements can be physical, logical, or a combination thereof. Additionally, the terms "herein," "above," "below," and words of similar effect, when used in this application, refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number can also include the plural or singular number respectively. The word "or" in reference to a list of two or more items should be construed to cover all possible combinations of those items, individually, and in combination with each other.

[0094] The above detailed description of embodiments of the disclosure is not intended to be exhaustive or to limit the teachings to the precise form disclosed above. While specific embodiments and examples of the disclosure are described above for illustrative purposes, various equivalent modifications are possible within the scope of the disclosure, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative implementations can perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks can be deleted, moved, added, subdivided, combined, and / or modified to provide alternative or subcombinations. Each of these processes or blocks can be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks can instead be performed in parallel, or can be performed at different times. Further, any specific numbers noted herein are merely meant to be illustrative: alternative implementations can employ different values or ranges.

[0095] The teachings of the disclosure provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various implementations described above can be combined to provide other implementations.

[0096] Any patents, applications, and other references noted above, including any accompanying documents filed with the application, are incorporated by reference herein. Aspects of the disclosure can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further implementations of the disclosure.

[0097] These and other changes can be made to the disclosure in light of the above Detailed Description. While the above description describes certain embodiments of the disclosure, and describes the best mode contemplated, no matter how detailed the above appears in text, the teachings can be practiced in many ways. Details of the system can vary considerably in its implementation details, yet still be encompassed by the subject matter disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the disclosure should not be taken to indicate that the terminology is being redefined herein to be restricted to the specific features or aspects described. No aspect of the disclosure is related or limited to the use of such terms. The use of terminology can describe a certain feature as described and claimed by the disclosure, but such use does not imply that this terminology is the only manner of referring to such feature nor does it imply that all of the claims that employ such terminology are interchangeable. Unless otherwise expressly provided herein, single processor units also can employ multiple components and circuitry and conversely, multiple processor units can be consolidates into a single unit. Thus, the actual scope of the disclosure is not limited to only the embodiments described herein.

[0098] While certain aspects of the disclosure are presented in the form of certain claims, the inventors contemplate aspects of the disclosure in any number of claim forms. For example, while only one aspect of the disclosure is presented in the form of a means plus function claim under 35 U.S.C. § 112, f., other aspects can equally well be embodied in a means plus function claim, or in other forms, such as in the form of a computer readable medium. Any claim that is dependent on another claim under 35 U.S.C. § 112, f., will start with the word "means." Accordingly, the Applicant reserves the right to add other additional claims after filing the application to pursue such additional claim forms for other aspects of the disclosure.

[0099] ​The detailed description provided herein can be applied to other systems, not necessarily only the system described above. The elements and acts of the various embodiments described above can be combined to provide further implementations of the application. Alternative implementations of the application can also include not only additional elements to those implementations noted above, but also can include fewer elements. These and other changes can be made to the application in light of the above Detailed Description. While the above description defines certain embodiments of the application and describes the best mode contemplated, no person skilled in the art will, on the basis of the scope of the preceding detailed description, claim that the described application can not include other implementations. The system can be significantly changed in its specific implementation, yet still be encompassed by the application disclosed herein. As described above, particular terminology used when describing certain features or aspects of the application should not be taken to imply that the terminology is being redefined herein to be restricted to the specific characteristics, features or aspects of the application with which that terminology is associated. The scope of the technology should therefore be measured not by the terminology used in the description, but by the inherent properties of the technology itself. The terminology used in the appended claims should not be interpreted as limiting the described technology to the specific implementations or examples disclosed herein.

Claims

1. A wireless power delivery system, comprising: means for establishing a wireless communication link with a client device in a multipath wireless power delivery environment; means for processing client-specific information received from the client device to select a group of client devices in the multipath wireless power delivery environment for receiving a radio frequency (RF) wireless power signal and to generate transmission scheduling information for the selected group of client devices, wherein the transmission scheduling information includes power transmission scheduling information and beacon transmission scheduling information, wherein the client-specific information includes at least one of a battery level, battery usage information, temperature information of the client device, and wherein the beacon transmission scheduling information indicates when each of the selected group of client devices transmits its respective beacon signal, the beacon signal used to enable the wireless power delivery system to determine a location of the at least one client device; means for transmitting a transmission code to each of the selected group of client devices, wherein the transmission code is used to encode the beacon signal transmitted by each of the selected group of client devices to isolate the signals transmitted from the selected group of client devices; and means for directing the radio frequency wireless power signal based on the power transmission scheduling information and the encoded beacon signal transmission to a determined location of at least one client device in the selected group in the multipath in the wireless power delivery environment, wherein the transmission code is unique to each of the selected group of client devices.

2. The wireless power transfer system of claim 1, wherein, The wireless power delivery system further comprises means for selecting a unique transmission code for each of the selected group of client devices.

3. The wireless power transfer system of claim 1, wherein, The transmission code is unique to the wireless power delivery system.

4. The wireless power transfer system of claim 1, wherein, The transmission code comprises a pseudo-random sequence.

5. The wireless power transfer system of claim 1, wherein, The wireless power delivery system further comprises means for decoding the encoded beacon signal received from a particular client device to determine whether the particular client device is authorized to receive the radio frequency wireless power signal from the wireless power delivery system, wherein the authorized devices are included in the selected group of client devices.

6. The wireless power transfer system of claim 5, wherein, The wireless power delivery system further comprises: means for measuring a phase at which the encoded beacon signal is received at one or more of a plurality of antennas, wherein the one or more of the plurality of antennas are radio frequency adaptive phased antennas that can be configured to direct the radio frequency wireless power signal to individual client devices in the multipath wireless power delivery environment; means for determining or updating location information corresponding to the particular client device based on the measured phase; and means for adjusting the adaptive phased antennas to direct wireless power to the particular client device.

7. The wireless power transfer system of claim 1, wherein, Further comprising: means for processing the client-specific information received from the client device to generate power transmission scheduling information; and means for transmitting the power transmission scheduling information to the selected group of client devices.

8. The wireless power transfer system of claim 1, wherein, The wireless power transfer system further comprises means for generating beacon transmission schedule information, and wherein the beacon transmission schedule information comprises a beacon transmission schedule assignment for the selected set of client devices.

9. A wireless power transfer system comprising: an adaptive phased antenna array comprising a plurality of antennas; and control circuitry operatively coupled to the plurality of antennas and adapted to: detect, at one or more of the plurality of antennas, a beacon signal broadcast by a wireless power receiver client device in a multipath wireless power transfer environment, wherein at least one of the beacon signals is encoded using a transmission code that isolates the at least one beacon signal from other beacon signals transmitted by the wireless power receiver client devices in the multipath wireless power transfer environment; decode the at least one beacon signal to: identify the wireless power receiver client device that transmitted the at least one beacon signal and determine a location of the wireless power receiver client device in the multipath wireless power transfer environment, and determine that the wireless power receiver client device that transmitted the at least one beacon signal is authorized to receive a radio frequency (RF) wireless power signal from the wireless power transfer system; and based on the determined location and authorization status of the wireless power receiver client device, direct one or more of the plurality of antennas of the adaptive phased antenna array to transmit the RF wireless power signal directed to the determined location of the wireless power receiver client device in the multipath wireless power transfer environment, wherein the control circuitry is further adapted to: process client-specific information received from one or more wireless power receiver client devices to select a set of wireless power receiver client devices for receiving the RF wireless power signal from the wireless power transfer system, and direct at least one of the plurality of antennas to transmit a transmission code to each of the selected set of wireless power receiver client devices; wherein the client-specific information comprises at least one of a battery level, battery usage information, temperature information of the client devices; and the transmission code is unique to each of the selected set of wireless power receiver client devices.

10. The wireless power transfer system of claim 9, wherein, The control circuitry is further adapted to: establish a wireless communication link with one or more wireless power receiver client devices in the multipath wireless power transfer environment via at least one of the plurality of antennas.

11. The wireless power transfer system of claim 10, wherein, The control circuitry is further adapted to: generate a beacon transmission schedule comprising a beacon transmission schedule assignment for the selected set of wireless power receiver client devices; and direct at least one of the plurality of antennas to transmit the beacon transmission schedule to each of the selected set of wireless power receiver client devices.

12. The wireless power transfer system of claim 10, wherein, The wireless power receiver client device is authorized to receive the radio frequency wireless power signal from the wireless power transmission system when the wireless power receiver client device transmitting the at least one beacon signal belongs to the selected group of wireless power receiver client devices.

13. The wireless power transfer system of claim 10, wherein, The control circuit is further adapted to select a unique transmission code for each of the selected group of wireless power receiver client devices.

14. The wireless power transfer system of claim 9, wherein, The transmission code uniquely identifies the wireless power transmission system.

15. The wireless power transfer system of claim 9, wherein, The transmission code comprises a pseudo-random sequence.

16. The wireless power transmission system of claim 9, the encoded beacon signal being phase modulated based on the transmission code.

17. A wireless power transmission system, comprising: an adaptive phased antenna array comprising a plurality of antennas; a control circuit operatively coupled to the plurality of antennas and adapted to: detect, at one or more of the plurality of antennas, a reception of a beacon signal broadcasted by a first wireless power receiver device of a group of wireless power receiver devices selected for receiving a radio frequency (RF) wireless power signal from the wireless power transmission system in a multipath wireless power delivery environment, wherein the beacon signal is encoded using a transmission code; decode the beacon signal to isolate the first wireless power receiver device and determine a location of the first wireless power receiver device in the multipath wireless power delivery environment; and in response to the reception of the beacon signal and the determined location of the first wireless power receiver device, direct one or more of the plurality of antennas of the adaptive phased antenna array to transmit the radio frequency wireless power signal directed to the determined location of the first wireless power receiver device in the multipath wireless power delivery environment, wherein the transmission code is unique to each of the wireless power receiver devices.

18. The wireless power transfer system of claim 17, wherein, The control circuit is further adapted to determine, based on the transmission code, that the first wireless power receiver device is authorized to receive the radio frequency wireless power signal from the wireless power transmission system.

19. The wireless power transfer system of claim 17, wherein, The control circuit is further adapted to select a unique transmission code for each of the group of wireless power receiver devices.

20. The wireless power transfer system of claim 17, wherein, The transmission code uniquely identifies the wireless power transmission system in the multipath wireless power delivery environment. The transmission code comprises a pseudo-random sequence.

Images